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

     Python 3.8.11, 6月 29, 2021

     unknown

     Copyright © 2001-2021, 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 2.4.4.


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

Python
******

     Python 3.8.11, 6月 29, 2021

     unknown

     Copyright © 2001-2021, Python Software Foundation

* Menu:

* Python 有什麼新功能？::
* Python 教學::
* Python Setup and Usage::
* The Python Language Reference::
* Python 標準函式庫 (Standard Library): Python 標準函式庫 Standard Library.
* Extending and Embedding the Python Interpreter::
* Python / C API 參考手冊::
* 發布 Python 模組::
* 安裝 Python 模組::
* Python HOWTOs::
* Python 常見問題::
* Glossary::
* 關於這些說明文件::
* 處理 Bug::
* 版權宣告::
* 歷史與授權::
* 發布 Python 模組（舊版）::
* 安裝 Python 模組（舊版）::
* Python 模組索引::
* 索引::

 — The Detailed Node Listing —

Python 有什麼新功能？

* What’s New In Python 3.8: What's New In Python 3 8.
* What’s New In Python 3.7: What's New In Python 3 7.
* What’s New In Python 3.6: What's New In Python 3 6.
* Python 3.5 有什麼新功能: Python 3 5 有什麼新功能.
* What’s New In Python 3.4: What's New In Python 3 4.
* What’s New In Python 3.3: What's New In Python 3 3.
* What’s New In Python 3.2: What's New In Python 3 2.
* What’s New In Python 3.1: What's New In Python 3 1.
* What’s New In Python 3.0: What's New In Python 3 0.
* What’s New in Python 2.7: What's New in Python 2 7.
* What’s New in Python 2.6: What's New in Python 2 6.
* What’s New in Python 2.5: What's New in Python 2 5.
* What’s New in Python 2.4: What's New in Python 2 4.
* What’s New in Python 2.3: What's New in Python 2 3.
* What’s New in Python 2.2: What's New in Python 2 2.
* What’s New in Python 2.1: What's New in Python 2 1.
* What’s New in Python 2.0: What's New in Python 2 0.
* Changelog（更動日誌）::

What’s New In Python 3.8

* Summary: Summary -- Release highlights. Release highlights
* New Features::
* Other Language Changes::
* New Modules::
* Improved Modules::
* Optimizations::
* Build and C API Changes::
* Deprecated::
* API and Feature Removals::
* Porting to Python 3.8: Porting to Python 3 8.
* Notable changes in Python 3.8.1: Notable changes in Python 3 8 1.
* Notable changes in Python 3.8.2: Notable changes in Python 3 8 2.
* Notable changes in Python 3.8.3: Notable changes in Python 3 8 3.
* Notable changes in Python 3.8.8: Notable changes in Python 3 8 8.
* Notable changes in Python 3.8.9: Notable changes in Python 3 8 9.
* Notable changes in Python 3.8.10: Notable changes in Python 3 8 10.
* Notable changes in Python 3.8.10: Notable changes in Python 3 8 10<2>.

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.
* Vectorcall; a fast calling protocol for CPython: Vectorcall a fast calling protocol for CPython.
* Pickle protocol 5 with out-of-band data buffers::

Improved Modules

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

Porting to Python 3.8

* Changes in Python behavior::
* Changes in the Python API::
* Changes in the C API::
* CPython bytecode changes::
* Demos and Tools::

Notable changes in Python 3.8.10

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

Notable changes in Python 3.8.10

* urllib.parse: urllib parse.

What’s New In Python 3.7

* Summary: Summary -- Release Highlights. Release Highlights
* New Features: New Features<2>.
* Other Language Changes: Other Language Changes<2>.
* New Modules: New Modules<2>.
* Improved Modules: Improved Modules<2>.
* C API Changes::
* Build Changes::
* Optimizations: Optimizations<2>.
* 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.
* Notable changes in Python 3.7.1: Notable changes in Python 3 7 1.
* Notable changes in Python 3.7.2: Notable changes in Python 3 7 2.
* Notable changes in Python 3.7.6: Notable changes in Python 3 7 6.
* Notable changes in Python 3.7.10: Notable changes in Python 3 7 10.

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 Documentation Translations: PEP 545 Python Documentation Translations.
* Development Runtime Mode; -X dev: Development Runtime Mode -X dev.

New Modules

* contextvars::
* dataclasses::
* importlib.resources: importlib resources.

Improved Modules

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

Deprecated Python modules, functions and methods

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

Porting to Python 3.7

* Changes in Python Behavior::
* Changes in the Python API: Changes in the Python API<2>.
* Changes in the C API: Changes in the C API<2>.
* CPython bytecode changes: CPython bytecode changes<2>.
* Windows-only Changes: Windows-only Changes<2>.
* Other CPython implementation changes::

What’s New In Python 3.6

* Summary: Summary -- Release highlights<2>. Release highlights
* New Features: New Features<3>.
* Other Language Changes: Other Language Changes<3>.
* New Modules: New Modules<3>.
* Improved Modules: Improved Modules<3>.
* Optimizations: Optimizations<3>.
* Build and C API Changes: Build and C API Changes<2>.
* Other Improvements::
* Deprecated: Deprecated<2>.
* Removed::
* Porting to Python 3.6: Porting to Python 3 6.
* Notable changes in Python 3.6.2: Notable changes in Python 3 6 2.
* Notable changes in Python 3.6.4: Notable changes in Python 3 6 4.
* Notable changes in Python 3.6.5: Notable changes in Python 3 6 5.
* Notable changes in Python 3.6.7: Notable changes in Python 3 6 7.
* Notable changes in Python 3.6.10: Notable changes in Python 3 6 10.
* Notable changes in Python 3.6.13: Notable changes in Python 3 6 13.

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::

New Modules

* secrets::

Improved Modules

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

Deprecated

* New Keywords::
* Deprecated Python behavior::
* Deprecated Python modules, functions and methods: Deprecated Python modules functions and methods<2>.
* 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<3>.
* distutils: distutils<3>.
* grp::
* importlib: importlib<4>.
* os: os<4>.
* re: re<3>.
* ssl: ssl<5>.
* tkinter: tkinter<4>.
* venv: venv<3>.

Removed

* 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<3>.
* Changes in the C API: Changes in the C API<3>.
* CPython bytecode changes: CPython bytecode changes<3>.

Notable changes in Python 3.6.2

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

Python 3.5 有什麼新功能

* Summary: Summary -- Release highlights<3>. Release highlights
* New Features: New Features<4>.
* Other Language Changes: Other Language Changes<4>.
* New Modules: New Modules<4>.
* Improved Modules: Improved Modules<4>.
* Other module-level changes::
* Optimizations: Optimizations<4>.
* Build and C API Changes: Build and C API Changes<3>.
* Deprecated: Deprecated<3>.
* Removed: Removed<2>.
* Porting to Python 3.5: Porting to Python 3 5.
* Notable changes in Python 3.5.4: Notable changes in 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.

New Modules

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

Improved Modules

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

ssl

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

Deprecated

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

Removed

* 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<4>.
* Changes in the C API: Changes in the C API<4>.

Notable changes in 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>.

What’s New In Python 3.4

* Summary: Summary -- Release Highlights<2>. Release Highlights
* New Features: New Features<5>.
* New Modules: New Modules<5>.
* Improved Modules: Improved Modules<5>.
* CPython Implementation Changes::
* Deprecated: Deprecated<4>.
* Removed: Removed<3>.
* Porting to Python 3.4: Porting to Python 3 4.
* Changed in 3.4.3: Changed in 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.
* Other Language Changes: Other Language Changes<5>.

PEP 453: Explicit Bootstrapping of PIP in Python Installations

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

New Modules

* asyncio: asyncio<6>.
* ensurepip::
* enum: enum<5>.
* pathlib: pathlib<5>.
* selectors: selectors<2>.
* statistics: statistics<3>.
* tracemalloc: tracemalloc<3>.

Improved Modules

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

CPython Implementation Changes

* 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>.
* Significant Optimizations::

Deprecated

* Deprecations in the Python API::
* Deprecated Features::

Removed

* Operating Systems No Longer Supported::
* API and Feature Removals: API and Feature Removals<5>.
* Code Cleanups::

Porting to Python 3.4

* Changes in ’python’ Command Behavior: Changes in 'python' Command Behavior<2>.
* Changes in the Python API: Changes in the Python API<5>.
* Changes in the C API: Changes in the C API<5>.

Changed in 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.

What’s New In Python 3.3

* Summary: Summary -- Release highlights<4>. Release highlights
* PEP 405; Virtual Environments: PEP 405 Virtual Environments.
* 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; Python Launcher for Windows: PEP 397 Python Launcher for Windows.
* 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; Function Signature Object: PEP 362 Function Signature Object.
* PEP 421; Adding sys.implementation: PEP 421 Adding sys implementation.
* Using importlib as the Implementation of Import::
* Other Language Changes: Other Language Changes<6>.
* A Finer-Grained Import Lock::
* Builtin functions and types::
* New Modules: New Modules<6>.
* Improved Modules: Improved Modules<6>.
* Optimizations: Optimizations<5>.
* Build and C API Changes: Build and C API Changes<4>.
* Deprecated: Deprecated<5>.
* Porting to Python 3.3: Porting to Python 3 3.

PEP 3118: New memoryview implementation and buffer protocol documentation

* Features::
* API changes::

PEP 393: Flexible String Representation

* Functionality::
* Performance and resource usage::

PEP 421: Adding sys.implementation

* SimpleNamespace::

Using importlib as the Implementation of Import

* New APIs::
* Visible Changes::

New Modules

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

Improved Modules

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

decimal

* Features: Features<2>.
* API changes: API changes<2>.

email

* Policy Framework::
* Provisional Policy with New Header API::
* Other API Changes::

Deprecated

* Unsupported Operating Systems: Unsupported Operating Systems<2>.
* Deprecated Python modules, functions and methods: Deprecated Python modules functions and methods<4>.
* Deprecated functions and types of the C API: Deprecated functions and types of the C API<3>.
* Deprecated features::

Porting to Python 3.3

* Porting Python code::
* Porting C code::
* Building C extensions::
* Command Line Switch Changes::

What’s New In Python 3.2

* PEP 384; Defining a Stable ABI: PEP 384 Defining a Stable ABI.
* PEP 389; Argparse Command Line Parsing Module: PEP 389 Argparse Command Line Parsing Module.
* PEP 391; Dictionary Based Configuration for Logging: PEP 391 Dictionary Based Configuration for Logging.
* PEP 3148; The concurrent.futures module: PEP 3148 The concurrent futures module.
* 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.
* Other Language Changes: Other Language Changes<7>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules.
* Multi-threading::
* Optimizations: Optimizations<6>.
* Unicode::
* Codecs::
* Documentation::
* IDLE::
* Code Repository::
* Build and C API Changes: Build and C API Changes<5>.
* Porting to Python 3.2: Porting to Python 3 2.

New, Improved, and Deprecated Modules

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

What’s New In Python 3.1

* PEP 372; Ordered Dictionaries: PEP 372 Ordered Dictionaries.
* PEP 378; Format Specifier for Thousands Separator: PEP 378 Format Specifier for Thousands Separator.
* Other Language Changes: Other Language Changes<8>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules<2>.
* Optimizations: Optimizations<7>.
* IDLE: IDLE<2>.
* Build and C API Changes: Build and C API Changes<6>.
* Porting to Python 3.1: Porting to Python 3 1.

What’s New In Python 3.0

* Common Stumbling Blocks::
* Overview Of Syntax Changes::
* Changes Already Present In Python 2.6: Changes Already Present In Python 2 6.
* Library Changes::
* 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<7>.
* 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::
* Integers::
* Text Vs. Data Instead Of Unicode Vs. 8-bit: Text Vs Data Instead Of Unicode Vs 8-bit.

Overview Of Syntax Changes

* New Syntax::
* Changed Syntax::
* Removed Syntax::

Miscellaneous Other Changes

* Operators And Special Methods::
* Builtins::

What’s New in Python 2.7

* The Future for Python 2.x: The Future for 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.
* Other Language Changes: Other Language Changes<9>.
* New and Improved Modules::
* Build and C API Changes: Build and C API Changes<8>.
* 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.
* Acknowledgements::

Other Language Changes

* Interpreter Changes::
* Optimizations: Optimizations<8>.

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>.

What’s New in 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; Revised Buffer Protocol: PEP 3118 Revised Buffer Protocol.
* 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.
* Other Language Changes: Other Language Changes<10>.
* New and Improved Modules: New and Improved Modules<2>.
* Deprecations and Removals::
* Build and C API Changes: Build and C API Changes<9>.
* Porting to Python 2.6: Porting to Python 2 6.
* Acknowledgements: Acknowledgements<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::
* The contextlib module::

PEP 3141: A Type Hierarchy for Numbers

* The fractions Module::

Other Language Changes

* Optimizations: Optimizations<9>.
* Interpreter Changes: Interpreter Changes<2>.

New and Improved Modules

* The ast module::
* The future_builtins module::
* 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.

What’s New in 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; The ’with’ statement: PEP 343 The 'with' statement<2>.
* 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.
* Other Language Changes: Other Language Changes<11>.
* New, Improved, and Removed Modules: New Improved and Removed Modules.
* Build and C API Changes: Build and C API Changes<10>.
* Porting to Python 2.5: Porting to Python 2 5.
* Acknowledgements: Acknowledgements<3>.

PEP 343: The ’with’ statement

* Writing Context Managers: Writing Context Managers<2>.
* The contextlib module: The contextlib module<2>.

Other Language Changes

* Interactive Interpreter Changes::
* Optimizations: Optimizations<10>.

New, Improved, and Removed Modules

* The ctypes package::
* The ElementTree package::
* The hashlib package::
* The sqlite3 package::
* The wsgiref package::

Build and C API Changes

* Port-Specific Changes::

What’s New in 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.
* Other Language Changes: Other Language Changes<12>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules<3>.
* Build and C API Changes: Build and C API Changes<11>.
* Porting to Python 2.4: Porting to Python 2 4.
* Acknowledgements: Acknowledgements<4>.

PEP 327: Decimal Data Type

* Why is Decimal needed?::
* The Decimal type::
* The Context type::

Other Language Changes

* Optimizations: Optimizations<11>.

New, Improved, and Deprecated Modules

* cookielib::
* doctest: doctest<3>.

Build and C API Changes

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

What’s New in 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::
* Other Language Changes: Other Language Changes<13>.
* 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<12>.
* Other Changes and Fixes: Other Changes and Fixes<2>.
* Porting to Python 2.3: Porting to Python 2 3.
* Acknowledgements: Acknowledgements<5>.

Other Language Changes

* String Changes::
* Optimizations: Optimizations<12>.

New, Improved, and Deprecated Modules

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

Build and C API Changes

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

What’s New in Python 2.2

* 簡介::
* PEPs 252 and 253; Type and Class Changes: PEPs 252 and 253 Type and Class Changes.
* PEP 234; Iterators: PEP 234 Iterators.
* 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 Changes::
* PEP 227; Nested Scopes: PEP 227 Nested Scopes.
* New and Improved Modules: New and Improved Modules<3>.
* Interpreter Changes and Fixes::
* Other Changes and Fixes: Other Changes and Fixes<3>.
* Acknowledgements: Acknowledgements<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::
* Related Links::

What’s New in 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<4>.
* Acknowledgements: Acknowledgements<7>.

What’s New in 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 Modules::
* Module changes::
* New modules::
* IDLE Improvements::
* Deleted and Deprecated Modules::
* Acknowledgements: Acknowledgements<8>.

Other Core Changes

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

XML Modules

* SAX2 Support::
* DOM Support::
* Relationship to PyXML::

Changelog（更動日誌）

* Python 3.8.11 final: Python 3 8 11 final.
* Python 3.8.10 final: Python 3 8 10 final.
* Python 3.8.9 final: Python 3 8 9 final.
* Python 3.8.8 final: Python 3 8 8 final.
* Python 3.8.8 release candidate 1: Python 3 8 8 release candidate 1.
* Python 3.8.7 final: Python 3 8 7 final.
* Python 3.8.7 release candidate 1: Python 3 8 7 release candidate 1.
* Python 3.8.6 final: Python 3 8 6 final.
* Python 3.8.6 release candidate 1: Python 3 8 6 release candidate 1.
* Python 3.8.5 final: Python 3 8 5 final.
* Python 3.8.4 final: Python 3 8 4 final.
* Python 3.8.4 release candidate 1: Python 3 8 4 release candidate 1.
* Python 3.8.3 final: Python 3 8 3 final.
* Python 3.8.3 release candidate 1: Python 3 8 3 release candidate 1.
* Python 3.8.2 final: Python 3 8 2 final.
* Python 3.8.2 release candidate 2: Python 3 8 2 release candidate 2.
* Python 3.8.2 release candidate 1: Python 3 8 2 release candidate 1.
* Python 3.8.1 final: Python 3 8 1 final.
* Python 3.8.1 release candidate 1: Python 3 8 1 release candidate 1.
* Python 3.8.0 final: Python 3 8 0 final.
* Python 3.8.0 release candidate 1: Python 3 8 0 release candidate 1.
* Python 3.8.0 beta 4: Python 3 8 0 beta 4.
* Python 3.8.0 beta 3: Python 3 8 0 beta 3.
* Python 3.8.0 beta 2: Python 3 8 0 beta 2.
* 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 3.8.11 final

* Security::
* Core and Builtins::
* Library::

Python 3.8.10 final

* Security: Security<2>.
* Core and Builtins: Core and Builtins<2>.
* Library: Library<2>.
* Documentation: Documentation<2>.
* Tests::
* Windows::
* macOS::
* IDLE: IDLE<3>.
* C API::

Python 3.8.9 final

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

Python 3.8.8 release candidate 1

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

Python 3.8.7 final

* Core and Builtins: Core and Builtins<5>.
* Library: Library<5>.
* Documentation: Documentation<5>.
* Build: Build<3>.
* Tools/Demos: Tools/Demos<2>.

Python 3.8.7 release candidate 1

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

Python 3.8.6 final

* Core and Builtins: Core and Builtins<7>.
* Library: Library<7>.
* Documentation: Documentation<7>.
* Tests: Tests<5>.
* Windows: Windows<4>.
* IDLE: IDLE<7>.

Python 3.8.6 release candidate 1

* Core and Builtins: Core and Builtins<8>.
* Library: Library<8>.
* Documentation: Documentation<8>.
* Windows: Windows<5>.
* IDLE: IDLE<8>.
* C API: C API<4>.

Python 3.8.5 final

* Security: Security<6>.
* Core and Builtins: Core and Builtins<9>.
* Library: Library<9>.
* Documentation: Documentation<9>.
* Build: Build<5>.
* macOS: macOS<5>.
* IDLE: IDLE<9>.

Python 3.8.4 final

* Security: Security<7>.
* Core and Builtins: Core and Builtins<10>.
* Library: Library<10>.
* IDLE: IDLE<10>.

Python 3.8.4 release candidate 1

* Security: Security<8>.
* Core and Builtins: Core and Builtins<11>.
* Library: Library<11>.
* Tests: Tests<6>.
* Build: Build<6>.
* Windows: Windows<6>.
* macOS: macOS<6>.
* IDLE: IDLE<11>.
* Tools/Demos: Tools/Demos<3>.

Python 3.8.3 final

* Core and Builtins: Core and Builtins<12>.
* Library: Library<12>.
* Documentation: Documentation<10>.
* Windows: Windows<7>.
* C API: C API<5>.

Python 3.8.3 release candidate 1

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

Python 3.8.2 final

* Core and Builtins: Core and Builtins<14>.
* Library: Library<14>.
* Documentation: Documentation<12>.
* IDLE: IDLE<13>.

Python 3.8.2 release candidate 2

* Security: Security<10>.
* Core and Builtins: Core and Builtins<15>.
* Library: Library<15>.
* IDLE: IDLE<14>.

Python 3.8.2 release candidate 1

* Security: Security<11>.
* Core and Builtins: Core and Builtins<16>.
* Library: Library<16>.
* Documentation: Documentation<13>.
* Tests: Tests<8>.
* Build: Build<8>.
* Windows: Windows<9>.
* IDLE: IDLE<15>.

Python 3.8.1 final

* Core and Builtins: Core and Builtins<17>.
* Library: Library<17>.
* Tests: Tests<9>.
* Windows: Windows<10>.
* macOS: macOS<8>.
* IDLE: IDLE<16>.

Python 3.8.1 release candidate 1

* Security: Security<12>.
* Core and Builtins: Core and Builtins<18>.
* Library: Library<18>.
* Documentation: Documentation<14>.
* Tests: Tests<10>.
* Build: Build<9>.
* Windows: Windows<11>.
* macOS: macOS<9>.
* IDLE: IDLE<17>.
* C API: C API<7>.

Python 3.8.0 final

* Core and Builtins: Core and Builtins<19>.
* Library: Library<19>.
* Documentation: Documentation<15>.
* Tests: Tests<11>.
* Windows: Windows<12>.
* IDLE: IDLE<18>.
* Tools/Demos: Tools/Demos<5>.
* C API: C API<8>.

Python 3.8.0 release candidate 1

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

Python 3.8.0 beta 4

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

Python 3.8.0 beta 3

* Security: Security<15>.
* Core and Builtins: Core and Builtins<22>.
* Library: Library<22>.
* Documentation: Documentation<18>.
* Tests: Tests<14>.
* Build: Build<12>.
* Windows: Windows<15>.
* IDLE: IDLE<21>.
* Tools/Demos: Tools/Demos<8>.

Python 3.8.0 beta 2

* Security: Security<16>.
* Core and Builtins: Core and Builtins<23>.
* Library: Library<23>.
* Documentation: Documentation<19>.
* Tests: Tests<15>.
* Build: Build<13>.
* Windows: Windows<16>.
* macOS: macOS<12>.
* IDLE: IDLE<22>.
* C API: C API<11>.

Python 3.8.0 beta 1

* Security: Security<17>.
* Core and Builtins: Core and Builtins<24>.
* Library: Library<24>.
* Documentation: Documentation<20>.
* Tests: Tests<16>.
* Build: Build<14>.
* Windows: Windows<17>.
* macOS: macOS<13>.
* IDLE: IDLE<23>.
* Tools/Demos: Tools/Demos<9>.
* C API: C API<12>.

Python 3.8.0 alpha 4

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

Python 3.8.0 alpha 3

* Security: Security<19>.
* Core and Builtins: Core and Builtins<26>.
* Library: Library<26>.
* Documentation: Documentation<22>.
* Tests: Tests<18>.
* Build: Build<16>.
* Windows: Windows<19>.
* IDLE: IDLE<25>.
* Tools/Demos: Tools/Demos<11>.
* C API: C API<14>.

Python 3.8.0 alpha 2

* Core and Builtins: Core and Builtins<27>.
* Library: Library<27>.
* Documentation: Documentation<23>.
* Tests: Tests<19>.
* Windows: Windows<20>.
* IDLE: IDLE<26>.

Python 3.8.0 alpha 1

* Security: Security<20>.
* Core and Builtins: Core and Builtins<28>.
* Library: Library<28>.
* Documentation: Documentation<24>.
* Tests: Tests<20>.
* Build: Build<17>.
* Windows: Windows<21>.
* macOS: macOS<15>.
* IDLE: IDLE<27>.
* Tools/Demos: Tools/Demos<12>.
* C API: C API<15>.

Python 3.7.0 final

* Library: Library<29>.
* C API: C API<16>.

Python 3.7.0 release candidate 1

* Core and Builtins: Core and Builtins<29>.
* Library: Library<30>.
* Documentation: Documentation<25>.
* Build: Build<18>.
* Windows: Windows<22>.
* IDLE: IDLE<28>.

Python 3.7.0 beta 5

* Core and Builtins: Core and Builtins<30>.
* Library: Library<31>.
* Documentation: Documentation<26>.
* Tests: Tests<21>.
* Build: Build<19>.
* macOS: macOS<16>.
* IDLE: IDLE<29>.

Python 3.7.0 beta 4

* Core and Builtins: Core and Builtins<31>.
* Library: Library<32>.
* Documentation: Documentation<27>.
* Tests: Tests<22>.
* Build: Build<20>.
* Windows: Windows<23>.
* macOS: macOS<17>.
* IDLE: IDLE<30>.
* Tools/Demos: Tools/Demos<13>.

Python 3.7.0 beta 3

* Security: Security<21>.
* Core and Builtins: Core and Builtins<32>.
* Library: Library<33>.
* Documentation: Documentation<28>.
* Tests: Tests<23>.
* Build: Build<21>.
* Windows: Windows<24>.
* macOS: macOS<18>.
* IDLE: IDLE<31>.
* Tools/Demos: Tools/Demos<14>.
* C API: C API<17>.

Python 3.7.0 beta 2

* Security: Security<22>.
* Core and Builtins: Core and Builtins<33>.
* Library: Library<34>.
* Documentation: Documentation<29>.
* Tests: Tests<24>.
* Build: Build<22>.
* Windows: Windows<25>.
* macOS: macOS<19>.
* IDLE: IDLE<32>.
* Tools/Demos: Tools/Demos<15>.

Python 3.7.0 beta 1

* Core and Builtins: Core and Builtins<34>.
* Library: Library<35>.
* Documentation: Documentation<30>.
* Tests: Tests<25>.
* Build: Build<23>.
* Windows: Windows<26>.
* macOS: macOS<20>.
* C API: C API<18>.

Python 3.7.0 alpha 4

* Core and Builtins: Core and Builtins<35>.
* Library: Library<36>.
* Documentation: Documentation<31>.
* Tests: Tests<26>.
* Windows: Windows<27>.
* Tools/Demos: Tools/Demos<16>.
* C API: C API<19>.

Python 3.7.0 alpha 3

* Core and Builtins: Core and Builtins<36>.
* Library: Library<37>.
* Documentation: Documentation<32>.
* Tests: Tests<27>.
* Build: Build<24>.
* Windows: Windows<28>.
* macOS: macOS<21>.
* IDLE: IDLE<33>.
* Tools/Demos: Tools/Demos<17>.
* C API: C API<20>.

Python 3.7.0 alpha 2

* Core and Builtins: Core and Builtins<37>.
* Library: Library<38>.
* Documentation: Documentation<33>.
* Build: Build<25>.
* IDLE: IDLE<34>.
* C API: C API<21>.

Python 3.7.0 alpha 1

* Security: Security<23>.
* Core and Builtins: Core and Builtins<38>.
* Library: Library<39>.
* Documentation: Documentation<34>.
* Tests: Tests<28>.
* Build: Build<26>.
* Windows: Windows<29>.
* IDLE: IDLE<35>.
* Tools/Demos: Tools/Demos<18>.
* C API: C API<22>.

Python 3.6.6 release candidate 1

* Core and Builtins: Core and Builtins<39>.
* Library: Library<40>.
* Documentation: Documentation<35>.
* Tests: Tests<29>.
* Build: Build<27>.
* Windows: Windows<30>.
* macOS: macOS<22>.
* IDLE: IDLE<36>.
* Tools/Demos: Tools/Demos<19>.
* C API: C API<23>.

Python 3.6.5 final

* Tests: Tests<30>.
* Build: Build<28>.

Python 3.6.5 release candidate 1

* Security: Security<24>.
* Core and Builtins: Core and Builtins<40>.
* Library: Library<41>.
* Documentation: Documentation<36>.
* Tests: Tests<31>.
* Build: Build<29>.
* Windows: Windows<31>.
* macOS: macOS<23>.
* IDLE: IDLE<37>.
* Tools/Demos: Tools/Demos<20>.
* C API: C API<24>.

Python 3.6.4 release candidate 1

* Core and Builtins: Core and Builtins<41>.
* Library: Library<42>.
* Documentation: Documentation<37>.
* Tests: Tests<32>.
* Build: Build<30>.
* Windows: Windows<32>.
* macOS: macOS<24>.
* IDLE: IDLE<38>.
* Tools/Demos: Tools/Demos<21>.
* C API: C API<25>.

Python 3.6.3 final

* Library: Library<43>.
* Build: Build<31>.

Python 3.6.3 release candidate 1

* Security: Security<25>.
* Core and Builtins: Core and Builtins<42>.
* Library: Library<44>.
* Documentation: Documentation<38>.
* Tests: Tests<33>.
* Build: Build<32>.
* Windows: Windows<33>.
* IDLE: IDLE<39>.
* Tools/Demos: Tools/Demos<22>.

Python 3.6.2 release candidate 2

* Security: Security<26>.

Python 3.6.2 release candidate 1

* Core and Builtins: Core and Builtins<43>.
* Library: Library<45>.
* Security: Security<27>.
* Library: Library<46>.
* IDLE: IDLE<40>.
* C API: C API<26>.
* Build: Build<33>.
* Documentation: Documentation<39>.
* Tools/Demos: Tools/Demos<23>.
* Tests: Tests<34>.
* Windows: Windows<34>.

Python 3.6.1 final

* Core and Builtins: Core and Builtins<44>.
* Build: Build<34>.

Python 3.6.1 release candidate 1

* Core and Builtins: Core and Builtins<45>.
* Library: Library<47>.
* IDLE: IDLE<41>.
* Windows: Windows<35>.
* C API: C API<27>.
* Documentation: Documentation<40>.
* Tests: Tests<35>.
* Build: Build<35>.

Python 3.6.0 release candidate 2

* Core and Builtins: Core and Builtins<46>.
* Tools/Demos: Tools/Demos<24>.
* Windows: Windows<36>.
* Build: Build<36>.

Python 3.6.0 release candidate 1

* Core and Builtins: Core and Builtins<47>.
* Library: Library<48>.
* C API: C API<28>.
* Documentation: Documentation<41>.
* Tools/Demos: Tools/Demos<25>.

Python 3.6.0 beta 4

* Core and Builtins: Core and Builtins<48>.
* Library: Library<49>.
* Documentation: Documentation<42>.
* Tests: Tests<36>.
* Build: Build<37>.

Python 3.6.0 beta 3

* Core and Builtins: Core and Builtins<49>.
* Library: Library<50>.
* Windows: Windows<37>.
* Build: Build<38>.
* Tests: Tests<37>.

Python 3.6.0 beta 2

* Core and Builtins: Core and Builtins<50>.
* Library: Library<51>.
* Windows: Windows<38>.
* C API: C API<29>.
* Build: Build<39>.
* Tests: Tests<38>.

Python 3.6.0 beta 1

* Core and Builtins: Core and Builtins<51>.
* Library: Library<52>.
* IDLE: IDLE<42>.
* C API: C API<30>.
* Tests: Tests<39>.
* Build: Build<40>.
* Tools/Demos: Tools/Demos<26>.
* Windows: Windows<39>.

Python 3.6.0 alpha 4

* Core and Builtins: Core and Builtins<52>.
* Library: Library<53>.
* IDLE: IDLE<43>.
* Tests: Tests<40>.
* Windows: Windows<40>.
* Build: Build<41>.

Python 3.6.0 alpha 3

* Core and Builtins: Core and Builtins<53>.
* Library: Library<54>.
* Security: Security<28>.
* Library: Library<55>.
* Security: Security<29>.
* Library: Library<56>.
* IDLE: IDLE<44>.
* C API: C API<31>.
* Build: Build<42>.
* Tools/Demos: Tools/Demos<27>.
* Documentation: Documentation<43>.
* Tests: Tests<41>.

Python 3.6.0 alpha 2

* Core and Builtins: Core and Builtins<54>.
* Library: Library<57>.
* Security: Security<30>.
* Library: Library<58>.
* Security: Security<31>.
* Library: Library<59>.
* IDLE: IDLE<45>.
* Documentation: Documentation<44>.
* Tests: Tests<42>.
* Windows: Windows<41>.
* Build: Build<43>.
* Windows: Windows<42>.
* C API: C API<32>.
* Tools/Demos: Tools/Demos<28>.

Python 3.6.0 alpha 1

* Core and Builtins: Core and Builtins<55>.
* Library: Library<60>.
* Security: Security<32>.
* Library: Library<61>.
* Security: Security<33>.
* Library: Library<62>.
* Security: Security<34>.
* Library: Library<63>.
* IDLE: IDLE<46>.
* Documentation: Documentation<45>.
* Tests: Tests<43>.
* Build: Build<44>.
* Windows: Windows<43>.
* Tools/Demos: Tools/Demos<29>.
* C API: C API<33>.

Python 3.5.5 release candidate 1

* Security: Security<35>.
* Core and Builtins: Core and Builtins<56>.
* Library: Library<64>.

Python 3.5.4 final

* Library: Library<65>.

Python 3.5.4 release candidate 1

* Security: Security<36>.
* Core and Builtins: Core and Builtins<57>.
* Library: Library<66>.
* Documentation: Documentation<46>.
* Tests: Tests<44>.
* Build: Build<45>.
* Windows: Windows<44>.
* C API: C API<34>.

Python 3.5.3 release candidate 1

* Core and Builtins: Core and Builtins<58>.
* Library: Library<67>.
* Security: Security<37>.
* Library: Library<68>.
* Security: Security<38>.
* Library: Library<69>.
* IDLE: IDLE<47>.
* C API: C API<35>.
* Documentation: Documentation<47>.
* Tests: Tests<45>.
* Tools/Demos: Tools/Demos<30>.
* Windows: Windows<45>.
* Build: Build<46>.

Python 3.5.2 final

* Core and Builtins: Core and Builtins<59>.
* Tests: Tests<46>.
* IDLE: IDLE<48>.

Python 3.5.2 release candidate 1

* Core and Builtins: Core and Builtins<60>.
* Security: Security<39>.
* Library: Library<70>.
* Security: Security<40>.
* Library: Library<71>.
* Security: Security<41>.
* Library: Library<72>.
* Security: Security<42>.
* Library: Library<73>.
* Security: Security<43>.
* Library: Library<74>.
* IDLE: IDLE<49>.
* Documentation: Documentation<48>.
* Tests: Tests<47>.
* Build: Build<47>.
* Windows: Windows<46>.
* Tools/Demos: Tools/Demos<31>.
* Windows: Windows<47>.

Python 3.5.1 final

* Core and Builtins: Core and Builtins<61>.
* Windows: Windows<48>.

Python 3.5.1 release candidate 1

* Core and Builtins: Core and Builtins<62>.
* Library: Library<75>.
* IDLE: IDLE<50>.
* Documentation: Documentation<49>.
* Tests: Tests<48>.
* Build: Build<48>.
* Windows: Windows<49>.
* Tools/Demos: Tools/Demos<32>.

Python 3.5.0 final

* Build: Build<49>.

Python 3.5.0 release candidate 4

* Library: Library<76>.
* Build: Build<50>.

Python 3.5.0 release candidate 3

* Core and Builtins: Core and Builtins<63>.
* Library: Library<77>.

Python 3.5.0 release candidate 2

* Core and Builtins: Core and Builtins<64>.
* Library: Library<78>.

Python 3.5.0 release candidate 1

* Core and Builtins: Core and Builtins<65>.
* Library: Library<79>.
* IDLE: IDLE<51>.
* Documentation: Documentation<50>.
* Tests: Tests<49>.

Python 3.5.0 beta 4

* Core and Builtins: Core and Builtins<66>.
* Library: Library<80>.
* Build: Build<51>.

Python 3.5.0 beta 3

* Core and Builtins: Core and Builtins<67>.
* Library: Library<81>.
* Tests: Tests<50>.
* Documentation: Documentation<51>.
* Build: Build<52>.

Python 3.5.0 beta 2

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

Python 3.5.0 beta 1

* Core and Builtins: Core and Builtins<69>.
* Library: Library<83>.
* IDLE: IDLE<52>.
* Tests: Tests<51>.
* Documentation: Documentation<52>.
* Tools/Demos: Tools/Demos<33>.

Python 3.5.0 alpha 4

* Core and Builtins: Core and Builtins<70>.
* Library: Library<84>.
* Build: Build<53>.
* Tests: Tests<52>.
* Tools/Demos: Tools/Demos<34>.
* C API: C API<36>.

Python 3.5.0 alpha 3

* Core and Builtins: Core and Builtins<71>.
* Library: Library<85>.
* Build: Build<54>.
* Tests: Tests<53>.
* Tools/Demos: Tools/Demos<35>.

Python 3.5.0 alpha 2

* Core and Builtins: Core and Builtins<72>.
* Library: Library<86>.
* Build: Build<55>.
* C API: C API<37>.
* Windows: Windows<50>.

Python 3.5.0 alpha 1

* Core and Builtins: Core and Builtins<73>.
* Library: Library<87>.
* IDLE: IDLE<53>.
* Build: Build<56>.
* C API: C API<38>.
* Documentation: Documentation<53>.
* Tests: Tests<54>.
* Tools/Demos: Tools/Demos<36>.
* Windows: Windows<51>.

Python 教學

* 淺嘗滋味::
* 使用 Python 直譯器::
* 一個非正式的 Python 簡介::
* 深入了解流程控制::
* 資料結構::
* 模組::
* 輸入和輸出::
* 錯誤和例外::
* Classes::
* Python 標準函式庫概覽::
* Brief Tour of the Standard Library: Brief Tour of the Standard Library --- Part II. Part II
* 虛擬環境與套件::
* 現在可以來學習些什麼？::
* Interactive Input Editing and History Substitution::
* 浮點數運算：問題與限制::
* 附錄::

使用 Python 直譯器

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

啟動直譯器

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

直譯器與它的環境

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

一個非正式的 Python 簡介

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

把 Python 當作計算機使用

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

深入了解流程控制

* if Statements::
* for Statements::
* range() 函式: range 函式.
* break and continue Statements, and else Clauses on Loops: break and continue Statements and else Clauses on Loops.
* pass Statements::
* 定義函式 (function): 定義函式 function.
* More on Defining Functions::
* Intermezzo; Coding Style: Intermezzo Coding Style.

More on Defining Functions

* Default Argument Values::
* Keyword Arguments::
* Special parameters::
* Arbitrary Argument Lists::
* Unpacking Argument Lists::
* Lambda Expressions::
* 說明文件字串::
* Function Annotations::

Special parameters

* Positional-or-Keyword Arguments::
* Positional-Only Parameters::
* Keyword-Only Arguments::
* Function Examples::
* Recap::

資料結構

* 進一步了解 List（串列）::
* The del statement::
* Tuples 和序列 (Sequences): Tuples 和序列 Sequences.
* 集合 (Sets): 集合 Sets.
* 字典（Dictionary）::
* 迴圈技巧::
* 更多條件式主題::
* 序列和其他資料結構之比較::

進一步了解 List（串列）

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

模組

* More on Modules::
* Standard Modules::
* The dir() Function: The dir Function.
* Packages::

More on Modules

* Executing modules as scripts::
* The Module Search Path::
* "Compiled" Python files::

Packages

* Importing * From a Package::
* Intra-package References::
* Packages in Multiple Directories::

輸入和輸出

* 更華麗的輸出格式::
* Reading and Writing Files::

更華麗的輸出格式

* 格式化的字串文本 (Formatted String Literals): 格式化的字串文本 Formatted String Literals.
* The String format() Method: The String format Method.
* Manual String Formatting::
* Old string formatting::

Reading and Writing Files

* Methods of File Objects::
* Saving structured data with json::

錯誤和例外

* 語法錯誤::
* 例外::
* 處理例外::
* Raising Exceptions::
* User-defined Exceptions::
* Defining Clean-up Actions::
* Predefined Clean-up Actions::

Classes

* A Word About Names and Objects::
* Python Scopes and Namespaces::
* A First Look at Classes::
* Random Remarks::
* Inheritance::
* Private Variables::
* Odds and Ends::
* Iterators::
* Generators::
* Generator Expressions::

Python Scopes and Namespaces

* Scopes and Namespaces Example::

A First Look at Classes

* Class Definition Syntax::
* Class Objects::
* Instance Objects::
* Method Objects::
* Class and Instance Variables::

Inheritance

* Multiple Inheritance::

Python 標準函式庫概覽

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

Brief Tour of the Standard Library — Part II

* Output Formatting::
* Templating::
* Working with Binary Data Record Layouts::
* Multi-threading: Multi-threading<2>.
* Logging::
* Weak References::
* Tools for Working with Lists::
* Decimal Floating Point Arithmetic::

虛擬環境與套件

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

Interactive Input Editing and History Substitution

* Tab Completion and History Editing::
* Alternatives to the Interactive Interpreter::

浮點數運算：問題與限制

* Representation Error::

附錄

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

互動模式

* Error Handling::
* Executable Python Scripts::
* The Interactive Startup File::
* The Customization Modules::

Python Setup and Usage

* Command line and environment::
* Using Python on Unix platforms::
* 在 Windows 上使用 Python::
* 在麥金塔系統使用Python::
* Editors and IDEs::

Command line and environment

* Command line::
* Environment variables::

Command line

* Interface options::
* Generic options::
* Miscellaneous options::
* Options you shouldn't use::

Environment variables

* Debug-mode variables::

Using Python on Unix platforms

* Getting and installing the latest version of Python::
* Building Python::
* Python-related paths and files::
* Miscellaneous::

Getting and installing the latest version of Python

* On Linux::
* On FreeBSD and OpenBSD::
* On OpenSolaris::

在 Windows 上使用 Python

* The full installer::
* The Microsoft Store package::
* The nuget.org packages: The nuget org packages.
* The embeddable package::
* Alternative bundles::
* 設定 Python::
* UTF-8 mode::
* Python Launcher for Windows::
* Finding modules::
* Additional modules::
* 編譯 Python 在 Windows::
* 其他平台::

The full installer

* Installation steps::
* Removing the MAX_PATH Limitation::
* 安裝排除使用者介面::
* 當安裝時不下載::
* Modifying an install::

The Microsoft Store package

* Known Issues::

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::

開始

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

Customization

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

Additional modules

* PyWin32::
* cx_Freeze::
* WConio::

在麥金塔系統使用Python

* 取得和安裝MacPython::
* 整合化開發工具::
* Installing Additional Python Packages::
* 圖形化使用者介面(GUI) 程式開發於Mac: 圖形化使用者介面 GUI 程式開發於Mac.
* 貢獻Python應用程式於 Mac::
* 其他資源::

取得和安裝MacPython

* 如何執行Python腳本::
* 透過使用者圖形介面執行腳本::
* 設定::

The Python Language Reference

* 簡介: 簡介<5>.
* Lexical analysis::
* Data model::
* Execution model::
* The import system::
* Expressions::
* Simple statements::
* Compound statements::
* Top-level components::
* 完整的語法規格書::

簡介

* Alternate Implementations::
* Notation::

Lexical analysis

* 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

* Keywords::
* Reserved classes of identifiers::

Literals

* String and Bytes literals::
* String literal concatenation::
* Formatted string literals::
* Numeric literals::
* Integer literals::
* Floating point literals::
* Imaginary literals::

Data model

* Objects, values and types: Objects values and types.
* The standard type hierarchy::
* Special method names::
* Coroutines::

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::
* Special method lookup::

Customizing attribute access

* Customizing module attribute access::
* Implementing Descriptors::
* Invoking Descriptors::
* __slots__::

__slots__

* Notes on using __slots__::

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::

Coroutines

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

Execution model

* Structure of a program::
* Naming and binding::
* Exceptions::

Naming and binding

* Binding of names::
* Resolution of names::
* Builtins and restricted execution::
* Interaction with dynamic features::

The import system

* importlib: importlib<7>.
* Packages: Packages<2>.
* Searching::
* Loading::
* The Path Based Finder::
* Replacing the standard import system::
* Package Relative Imports::
* Special considerations for __main__::
* Open issues::
* References::

Packages

* Regular packages::
* Namespace packages::

Searching

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

Loading

* Loaders::
* Submodules::
* 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__.

Expressions

* 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::

Yield expressions

* Generator-iterator methods::
* Examples::
* Asynchronous generator functions::
* Asynchronous generator-iterator methods::

Primaries

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

Comparisons

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

Simple statements

* Expression statements::
* Assignment statements::
* The assert statement::
* The pass statement::
* The del statement: The del statement<2>.
* The return statement::
* The yield statement::
* The raise statement::
* The break statement::
* The continue statement::
* The import statement::
* The global statement::
* The nonlocal statement::

Assignment statements

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

The import statement

* Future statements::

Compound statements

* The if statement::
* The while statement::
* The for statement::
* The try statement::
* The with statement::
* Function definitions::
* Class definitions::
* Coroutines: Coroutines<2>.

Coroutines

* Coroutine function definition::
* The async for statement::
* The async with statement::

Top-level components

* Complete Python programs::
* File input::
* Interactive input::
* Expression input::

Python 標準函式庫 (Standard Library)

* 簡介: 簡介<6>.
* 內建函式::
* 內建常數::
* 內建型態::
* 內建的例外::
* Text Processing Services::
* Binary Data Services::
* Data Types::
* 數值與數學模組::
* 函式編程模組::
* 檔案與目錄存取::
* Data Persistence::
* 資料壓縮與保存::
* 檔案格式::
* Cryptographic Services::
* Generic Operating System Services::
* Concurrent Execution::
* Networking and Interprocess Communication::
* Internet Data Handling::
* Structured Markup Processing Tools::
* Internet Protocols and Support::
* Multimedia Services::
* 國際化::
* 程式框架::
* 以 Tk 打造 GUI::
* 開發工具::
* Debugging and Profiling::
* 軟體封裝與發布::
* Python Runtime Services::
* Custom Python Interpreters::
* 匯入模組::
* Python Language Services::
* Miscellaneous Services::
* MS Windows Specific Services::
* Unix Specific Services::
* Superseded Modules::
* Undocumented Modules::

簡介

* Notes on availability::

內建常數

* Constants added by the site module::

內建型態

* Truth Value Testing::
* Boolean Operations: Boolean Operations --- and or not. and, or, not
* Comparisons: Comparisons<2>.
* Numeric Types: Numeric Types --- int float complex. int, float, complex
* Iterator Types::
* 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
* Context Manager Types::
* Other Built-in Types::
* Special Attributes::

Numeric Types — int, float, complex

* Bitwise Operations on Integer Types::
* Additional Methods on Integer Types::
* Additional Methods on Float::
* Hashing of numeric types::

Iterator Types

* 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

* Dictionary view objects::

Other Built-in Types

* Modules::
* Classes and Class Instances::
* Functions::
* Methods::
* Code Objects::
* Type Objects::
* The Null Object::
* The Ellipsis Object::
* The NotImplemented Object::
* Boolean Values::
* Internal Objects::

內建的例外

* Base classes::
* Concrete exceptions::
* Warnings::
* Exception hierarchy::

Concrete exceptions

* OS exceptions::

Text Processing Services

* string: string --- Common string operations. Common string operations
* re: re --- Regular expression operations. Regular expression operations
* difflib: difflib --- Helpers for computing deltas. Helpers for computing deltas
* textwrap: textwrap --- Text wrapping and filling. Text wrapping and filling
* unicodedata: unicodedata --- Unicode Database. Unicode Database
* stringprep: stringprep --- Internet String Preparation. Internet String Preparation
* readline: readline --- GNU readline interface. GNU readline interface
* rlcompleter: rlcompleter --- Completion function for GNU readline. Completion function for GNU readline

string — Common string operations

* String constants::
* Custom String Formatting::
* Format String Syntax::
* Template strings::
* Helper functions::

Format String Syntax

* Format Specification Mini-Language::
* Format examples::

re — Regular expression operations

* Regular Expression Syntax::
* Module Contents::
* Regular Expression Objects::
* Match Objects::
* Regular Expression Examples::

Regular Expression Examples

* Checking for a Pair::
* Simulating scanf(): Simulating 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 — Helpers for computing deltas

* SequenceMatcher Objects::
* SequenceMatcher Examples::
* Differ Objects::
* Differ Example::
* A command-line interface to difflib::

readline — GNU readline interface

* Init file::
* Line buffer::
* History file::
* History list::
* Startup hooks::
* Completion::
* Example::

rlcompleter — Completion function for GNU readline

* Completer Objects::

Binary Data Services

* struct: struct --- Interpret bytes as packed binary data. Interpret bytes as packed binary data
* codecs: codecs --- Codec registry and base classes. Codec registry and base classes

struct — Interpret bytes as packed binary data

* Functions and Exceptions::
* Format Strings::
* Classes: Classes<2>.

Format Strings

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

codecs — Codec registry and base classes

* 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 Objects::
* IncrementalDecoder Objects::

Stream Encoding and Decoding

* StreamWriter Objects::
* StreamReader Objects::
* StreamReaderWriter Objects::
* StreamRecoder Objects::

Python Specific Encodings

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

Data Types

* datetime: datetime --- Basic date and time types. Basic date and time types
* calendar: calendar --- General calendar-related functions. General calendar-related functions
* collections: collections --- 容器資料型態. 容器資料型態
* collections.abc: collections abc --- Abstract Base Classes for Containers. Abstract Base Classes for Containers
* heapq: heapq --- 堆積佇列 heap queue 演算法. 堆積佇列 (heap queue) 演算法
* bisect: bisect --- 陣列二分演算法 Array bisection algorithm. 陣列二分演算法 (Array bisection algorithm)
* array: array --- 高效率的數值型態陣列. 高效率的數值型態陣列
* weakref: weakref --- Weak references. Weak references
* types: types --- Dynamic type creation and names for built-in types. Dynamic type creation and names for built-in types
* copy: copy --- Shallow and deep copy operations. Shallow and deep copy operations
* pprint: pprint --- Data pretty printer. Data pretty printer
* reprlib: reprlib --- Alternate repr implementation. Alternate repr() implementation
* enum: enum --- Support for enumerations. Support for enumerations

datetime — Basic date and time types

* Aware and Naive Objects::
* Constants::
* Available Types::
* timedelta Objects::
* date Objects::
* datetime Objects::
* time Objects::
* tzinfo Objects::
* timezone Objects::
* strftime() and strptime() Behavior: strftime and strptime Behavior.

Available Types

* Common Properties::
* Determining if an Object is Aware or Naive::

timedelta Objects

* Examples of usage; timedelta: Examples of usage timedelta.

date Objects

* Examples of Usage; date: Examples of Usage date.

datetime Objects

* Examples of Usage; datetime: Examples of Usage datetime.

time Objects

* Examples of Usage; time: Examples of Usage time.

strftime() and strptime() Behavior

* strftime() and strptime() Format Codes: strftime and strptime Format Codes.
* Technical Detail::

collections — 容器資料型態

* ChainMap objects::
* Counter 物件::
* deque objects::
* defaultdict objects::
* namedtuple() Factory Function for Tuples with Named Fields: namedtuple Factory Function for Tuples with Named Fields.
* OrderedDict objects::
* UserDict objects::
* UserList objects::
* UserString objects::

ChainMap objects

* ChainMap Examples and Recipes::

deque objects

* deque Recipes::

defaultdict objects

* defaultdict Examples::

OrderedDict objects

* OrderedDict Examples and Recipes::

collections.abc — Abstract Base Classes for Containers

* Collections Abstract Base Classes::

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

* 基礎範例::
* 優先佇列 (Priority Queue) 實作細節: 優先佇列 Priority Queue 實作細節.
* 原理::

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

* Searching Sorted Lists::
* Other Examples::

weakref — Weak references

* Weak Reference Objects::
* Example: Example<2>.
* Finalizer Objects::
* Comparing finalizers with __del__() methods: Comparing finalizers with __del__ methods.

types — Dynamic type creation and names for built-in types

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

pprint — Data pretty printer

* PrettyPrinter Objects::
* Example: Example<3>.

reprlib — Alternate repr() implementation

* Repr Objects::
* Subclassing Repr Objects::

enum — Support for enumerations

* Module Contents: Module Contents<2>.
* Creating an Enum::
* Programmatic access to enumeration members and their attributes::
* Duplicating enum members and values::
* Ensuring unique enumeration values::
* Using automatic values::
* Iteration::
* Comparisons: Comparisons<3>.
* Allowed members and attributes of enumerations::
* Restricted Enum subclassing::
* Pickling::
* Functional API::
* Derived Enumerations::
* When to use __new__() vs. __init__(): When to use __new__ vs __init__.
* Interesting examples::
* How are Enums different?::

Derived Enumerations

* IntEnum::
* IntFlag::
* Flag::
* Others::

Interesting examples

* Omitting values::
* OrderedEnum::
* DuplicateFreeEnum::
* Planet::
* TimePeriod::

Omitting values

* Using auto::
* Using object::
* Using a descriptive string::
* Using a custom __new__(): Using a custom __new__.

How are Enums different?

* Enum Classes::
* Enum Members (aka instances): Enum Members aka instances.
* Finer Points::

Finer Points

* Supported __dunder__ names::
* Supported _sunder_ names::
* Enum member type::
* Boolean value of Enum classes and members::
* Enum classes with methods::
* Combining members of Flag::

數值與數學模組

* numbers: numbers --- Numeric abstract base classes. Numeric abstract base classes
* math: math --- Mathematical functions. Mathematical functions
* cmath: cmath --- Mathematical functions for complex numbers. Mathematical functions for complex numbers
* decimal: decimal --- Decimal fixed point and floating point arithmetic. Decimal fixed point and floating point arithmetic
* fractions: fractions --- Rational numbers. Rational numbers
* random: random --- Generate pseudo-random numbers. Generate pseudo-random numbers
* statistics: statistics --- 數學統計函式. 數學統計函式

numbers — Numeric abstract base classes

* The numeric tower::
* Notes for type implementors::

Notes for type implementors

* Adding More Numeric ABCs::
* Implementing the arithmetic operations::

math — Mathematical functions

* Number-theoretic and representation functions::
* Power and logarithmic functions::
* Trigonometric functions::
* Angular conversion::
* Hyperbolic functions::
* Special functions::
* Constants: Constants<2>.

cmath — Mathematical functions for complex numbers

* Conversions to and from polar coordinates::
* Power and logarithmic functions: Power and logarithmic functions<2>.
* Trigonometric functions: Trigonometric functions<2>.
* Hyperbolic functions: Hyperbolic functions<2>.
* Classification functions::
* Constants: Constants<3>.

decimal — Decimal fixed point and floating point arithmetic

* Quick-start Tutorial::
* Decimal objects::
* Context objects::
* Constants: Constants<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::
* Special values::

random — Generate pseudo-random numbers

* Bookkeeping functions::
* Functions for integers::
* Functions for sequences::
* Real-valued distributions::
* Alternative Generator::
* Notes on Reproducibility::
* Examples and Recipes::

statistics — 數學統計函式

* 平均值與中央位置量數::
* 離度 (spread) 的測量: 離度 spread 的測量.
* 函式細節::
* Exceptions: Exceptions<2>.
* NormalDist objects::

NormalDist objects

* NormalDist Examples and Recipes::

函式編程模組

* itertools: itertools --- Functions creating iterators for efficient looping. Functions creating iterators for efficient looping
* functools: functools --- Higher-order functions and operations on callable objects. Higher-order functions and operations on callable
                        objects
* operator: operator --- Standard operators as functions. Standard operators as functions

itertools — Functions creating iterators for efficient looping

* Itertool functions::
* Itertools Recipes::

functools — Higher-order functions and operations on callable objects

* partial Objects::

operator — Standard operators as functions

* Mapping Operators to Functions::
* In-place Operators::

檔案與目錄存取

* pathlib: pathlib --- Object-oriented filesystem paths. Object-oriented filesystem paths
* os.path: os path --- Common pathname manipulations. Common pathname manipulations
* fileinput: fileinput --- Iterate over lines from multiple input streams. Iterate over lines from multiple input streams
* stat: stat --- Interpreting stat results. Interpreting stat() results
* filecmp: filecmp --- File and Directory Comparisons. File and Directory Comparisons
* tempfile: tempfile --- Generate temporary files and directories. Generate temporary files and directories
* glob: glob --- Unix style pathname pattern expansion. Unix style pathname pattern expansion
* fnmatch: fnmatch --- Unix filename pattern matching. Unix filename pattern matching
* linecache: linecache --- Random access to text lines. Random access to text lines
* shutil: shutil --- High-level file operations. High-level file operations

pathlib — Object-oriented filesystem paths

* Basic use::
* Pure paths::
* Concrete paths::
* Correspondence to tools in the os module::

Pure paths

* General properties::
* Operators: Operators<2>.
* Accessing individual parts::
* Methods and properties::

Concrete paths

* Methods: Methods<2>.

filecmp — File and Directory Comparisons

* The dircmp class::

tempfile — Generate temporary files and directories

* Examples: Examples<3>.
* Deprecated functions and variables::

shutil — High-level file operations

* 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 example::

Archiving operations

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

Data Persistence

* pickle: pickle --- Python object serialization. Python object serialization
* copyreg: copyreg --- Register pickle support functions. Register pickle support functions
* shelve: shelve --- Python object persistence. Python object persistence
* marshal: marshal --- Internal Python object serialization. Internal Python object serialization
* dbm: dbm --- Interfaces to Unix "databases". Interfaces to Unix "databases"
* sqlite3: sqlite3 --- DB-API 2 0 interface for SQLite databases. DB-API 2.0 interface for SQLite databases

pickle — Python object serialization

* Relationship to other Python modules::
* Data stream format::
* Module Interface::
* 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>.
* Examples: Examples<4>.

Relationship to other Python modules

* Comparison with marshal::
* Comparison with json::

Pickling Class Instances

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

Out-of-band Buffers

* Provider API::
* Consumer API::
* Example: Example<4>.

copyreg — Register pickle support functions

* Example: Example<5>.

shelve — Python object persistence

* Restrictions::
* Example: Example<6>.

dbm — Interfaces to Unix "databases"

* dbm.gnu: dbm gnu --- GNU's reinterpretation of dbm. GNU’s reinterpretation of dbm
* dbm.ndbm: dbm ndbm --- Interface based on ndbm. Interface based on ndbm
* dbm.dumb: dbm dumb --- Portable DBM implementation. Portable DBM implementation

sqlite3 — DB-API 2.0 interface for SQLite databases

* Module functions and constants::
* Connection Objects::
* Cursor Objects::
* Row Objects::
* Exceptions: Exceptions<3>.
* SQLite and Python types::
* Controlling Transactions::
* Using sqlite3 efficiently::

SQLite and Python types

* 簡介: 簡介<7>.
* Using adapters to store additional Python types in SQLite databases::
* Converting SQLite values to custom Python types::
* Default adapters and converters::

Using adapters to store additional Python types in SQLite databases

* Letting your object adapt itself::
* Registering an adapter callable::

Using sqlite3 efficiently

* Using shortcut methods::
* Accessing columns by name instead of by index::
* Using the connection as a context manager::

資料壓縮與保存

* zlib: zlib --- Compression compatible with gzip. Compression compatible with gzip
* gzip: gzip --- Support for gzip files. Support for gzip files
* bz2: bz2 --- Support for bzip2 compression. Support for bzip2 compression
* lzma: lzma --- Compression using the LZMA algorithm. Compression using the LZMA algorithm
* zipfile: zipfile --- Work with ZIP archives. Work with ZIP archives
* tarfile: tarfile --- Read and write tar archive files. Read and write tar archive files

gzip — Support for gzip files

* Examples of usage::
* Command Line Interface::

Command Line Interface

* Command line options::

bz2 — Support for bzip2 compression

* (De)compression of files: De compression of files.
* Incremental (de)compression: Incremental de compression.
* One-shot (de)compression: One-shot de compression.
* Examples of usage: Examples of usage<2>.

lzma — Compression using the LZMA algorithm

* Reading and writing compressed files::
* Compressing and decompressing data in memory::
* Miscellaneous: Miscellaneous<2>.
* Specifying custom filter chains::
* Examples: Examples<5>.

zipfile — Work with ZIP archives

* ZipFile Objects::
* Path Objects::
* PyZipFile Objects::
* ZipInfo Objects::
* 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 — Read and write tar archive files

* TarFile Objects::
* TarInfo Objects::
* Command-Line Interface: Command-Line Interface<2>.
* Examples: Examples<6>.
* Supported tar formats::
* Unicode issues::

Command-Line Interface

* Command-line options: Command-line options<2>.

檔案格式

* csv: csv --- CSV File Reading and Writing. CSV File Reading and Writing
* configparser: configparser --- Configuration file parser. Configuration file parser
* netrc: netrc --- netrc file processing. netrc file processing
* xdrlib: xdrlib --- Encode and decode XDR data. Encode and decode XDR data
* plistlib: plistlib --- Generate and parse Mac OS X plist files. Generate and parse Mac OS X .plist files

csv — CSV File Reading and Writing

* Module Contents: Module Contents<3>.
* Dialects and Formatting Parameters::
* Reader Objects::
* Writer Objects::
* Examples: Examples<7>.

configparser — Configuration file parser

* Quick Start::
* Supported Datatypes::
* Fallback Values::
* Supported INI File Structure::
* Interpolation of values::
* Mapping Protocol Access::
* Customizing Parser Behaviour::
* Legacy API Examples::
* ConfigParser Objects::
* RawConfigParser Objects::
* Exceptions: Exceptions<4>.

netrc — netrc file processing

* netrc Objects::

xdrlib — Encode and decode XDR data

* Packer Objects::
* Unpacker Objects::
* Exceptions: Exceptions<5>.

plistlib — Generate and parse Mac OS X .plist files

* Examples: Examples<8>.

Cryptographic Services

* hashlib: hashlib --- Secure hashes and message digests. Secure hashes and message digests
* hmac: hmac --- Keyed-Hashing for Message Authentication. Keyed-Hashing for Message Authentication
* secrets: secrets --- Generate secure random numbers for managing secrets. Generate secure random numbers for managing secrets

hashlib — Secure hashes and message digests

* Hash algorithms::
* SHAKE variable length digests::
* Key derivation::
* BLAKE2::

BLAKE2

* Creating hash objects::
* Constants: Constants<5>.
* Examples: Examples<9>.
* Credits::

Examples

* Simple hashing::
* Using different digest sizes::
* Keyed hashing::
* Randomized hashing::
* Personalization::
* Tree mode::

secrets — Generate secure random numbers for managing secrets

* Random numbers::
* Generating tokens::
* Other functions::
* Recipes and best practices::

Generating tokens

* How many bytes should tokens use?::

Generic Operating System Services

* os: os --- Miscellaneous operating system interfaces. Miscellaneous operating system interfaces
* io: io --- Core tools for working with streams. Core tools for working with streams
* time: time --- Time access and conversions. Time access and conversions
* argparse: argparse --- Parser for command-line options arguments and sub-commands. Parser for command-line options, arguments and sub-
                        commands
* getopt: getopt --- C-style parser for command line options. C-style parser for command line options
* logging: logging --- Logging facility for Python. Logging facility for Python
* logging.config: logging config --- Logging configuration. Logging configuration
* logging.handlers: logging handlers --- Logging handlers. Logging handlers
* getpass: getpass --- Portable password input. Portable password input
* curses: curses --- Terminal handling for character-cell displays. Terminal handling for character-cell displays
* curses.textpad: curses textpad --- Text input widget for curses programs. Text input widget for curses programs
* curses.ascii: curses ascii --- Utilities for ASCII characters. Utilities for ASCII characters
* curses.panel: curses panel --- A panel stack extension for curses. A panel stack extension for curses
* platform: platform --- Access to underlying platform's identifying data. Access to underlying platform’s identifying data
* errno: errno --- Standard errno system symbols. Standard errno system symbols
* ctypes: ctypes --- A foreign function library for Python. A foreign function library for Python

os — Miscellaneous operating system interfaces

* File Names, Command Line Arguments, and Environment Variables: File Names Command Line Arguments and Environment Variables.
* Process Parameters::
* File Object Creation::
* File Descriptor Operations::
* Files and Directories::
* Process Management::
* Interface to the scheduler::
* Miscellaneous System Information::
* Random numbers: Random numbers<2>.

File Descriptor Operations

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

Files and Directories

* Linux extended attributes::

io — Core tools for working with streams

* 總覽::
* High-level Module Interface::
* Class hierarchy::
* Performance: Performance<3>.

總覽

* Text I/O::
* Binary I/O::
* Raw I/O::

Class hierarchy

* I/O Base Classes::
* Raw File I/O::
* Buffered Streams::
* Text I/O: Text I/O<2>.

Performance

* Binary I/O: Binary I/O<2>.
* Text I/O: Text I/O<3>.
* Multi-threading: Multi-threading<3>.
* Reentrancy::

time — Time access and conversions

* Functions: Functions<2>.
* Clock ID Constants::
* Timezone Constants::

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

* Example: Example<7>.
* ArgumentParser objects::
* The add_argument() method: The add_argument method.
* The parse_args() method: The parse_args method.
* Other utilities::
* Upgrading optparse code::

Example

* Creating a parser::
* Adding arguments::
* Parsing arguments::

ArgumentParser objects

* prog::
* usage::
* description::
* epilog::
* parents::
* formatter_class::
* prefix_chars::
* fromfile_prefix_chars::
* argument_default::
* allow_abbrev::
* conflict_handler::
* add_help::

The add_argument() method

* name or flags::
* action::
* nargs::
* const::
* default::
* type::
* choices::
* required::
* help::
* metavar::
* dest::
* 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 objects::
* Argument groups::
* Mutual exclusion::
* Parser defaults::
* Printing help::
* Partial parsing::
* Customizing file parsing::
* Exiting methods::
* Intermixed parsing::

logging — Logging facility for Python

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

logging.config — Logging configuration

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

Configuration dictionary schema

* Dictionary Schema Details::
* Incremental Configuration::
* Object connections::
* User-defined objects::
* Access to external objects::
* Access to internal objects::
* Import resolution and custom importers::

logging.handlers — Logging handlers

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

curses — Terminal handling for character-cell displays

* Functions: Functions<3>.
* Window Objects::
* Constants: Constants<6>.

curses.textpad — Text input widget for curses programs

* Textbox objects::

curses.panel — A panel stack extension for curses

* Functions: Functions<4>.
* Panel Objects::

platform —  Access to underlying platform’s identifying data

* Cross Platform::
* Java Platform::
* Windows Platform::
* Mac OS Platform::
* Unix Platforms::

ctypes — A foreign function library for Python

* ctypes tutorial::
* ctypes reference::

ctypes tutorial

* Loading dynamic link libraries::
* Accessing functions from loaded dlls::
* Calling functions::
* Fundamental data types::
* Calling functions, continued: Calling functions continued.
* 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::
* Callback functions::
* 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 --- Thread-based parallelism. Thread-based parallelism
* multiprocessing: multiprocessing --- Process-based parallelism. Process-based parallelism
* multiprocessing.shared_memory: multiprocessing shared_memory --- Provides shared memory for direct access across processes. Provides shared memory for direct access
                                 across processes
* The concurrent package::
* concurrent.futures: concurrent futures --- Launching parallel tasks. Launching parallel tasks
* subprocess: subprocess --- Subprocess management. Subprocess management
* sched: sched --- Event scheduler. Event scheduler
* queue: queue --- A synchronized queue class. A synchronized queue class
* contextvars: contextvars --- Context Variables. Context Variables
* _thread: _thread --- Low-level threading API. Low-level threading API
* _dummy_thread: _dummy_thread --- Drop-in replacement for the _thread module. Drop-in replacement for the _thread module
* dummy_threading: dummy_threading --- Drop-in replacement for the threading module. Drop-in replacement for the threading module

threading — Thread-based parallelism

* Thread-Local Data::
* Thread Objects::
* Lock Objects::
* RLock Objects::
* 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 Example::

multiprocessing — Process-based parallelism

* 簡介: 簡介<8>.
* Reference::
* Programming guidelines::
* Examples: Examples<10>.

簡介

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

Reference

* Process and exceptions::
* Pipes and Queues::
* Miscellaneous: Miscellaneous<3>.
* Connection Objects: Connection Objects<2>.
* Synchronization primitives::
* Shared ctypes Objects::
* Managers::
* Proxy Objects::
* Process Pools::
* Listeners and Clients::
* Authentication keys::
* Logging: Logging<2>.
* The multiprocessing.dummy module: The multiprocessing dummy module.

Shared ctypes Objects

* The multiprocessing.sharedctypes module: The multiprocessing sharedctypes module.

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 — Launching parallel tasks

* Executor Objects::
* ThreadPoolExecutor::
* ProcessPoolExecutor::
* Future Objects::
* Module Functions::
* Exception classes::

ThreadPoolExecutor

* ThreadPoolExecutor Example::

ProcessPoolExecutor

* ProcessPoolExecutor Example::

subprocess — Subprocess management

* Using the subprocess Module::
* Security Considerations::
* 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::
* Exceptions: Exceptions<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::

sched — Event scheduler

* Scheduler Objects::

queue — A synchronized queue class

* Queue Objects::
* SimpleQueue Objects::

contextvars — Context Variables

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

Networking and Interprocess Communication

* asyncio: asyncio --- Asynchronous I/O. Asynchronous I/O
* socket: socket --- Low-level networking interface. Low-level networking interface
* ssl: ssl --- TLS/SSL wrapper for socket objects. TLS/SSL wrapper for socket objects
* select: select --- Waiting for I/O completion. Waiting for I/O completion
* selectors: selectors --- High-level I/O multiplexing. High-level I/O multiplexing
* asyncore: asyncore --- Asynchronous socket handler. Asynchronous socket handler
* asynchat: asynchat --- Asynchronous socket command/response handler. Asynchronous socket command/response handler
* signal: signal --- Set handlers for asynchronous events. Set handlers for asynchronous events
* mmap: mmap --- Memory-mapped file support. Memory-mapped file support

asyncio — Asynchronous I/O

* Coroutines and Tasks::
* Streams::
* Synchronization Primitives::
* Subprocesses::
* Queues::
* Exceptions: Exceptions<8>.
* Event Loop::
* Futures::
* Transports and Protocols::
* Policies::
* Platform Support::
* High-level API Index::
* Low-level API Index::
* Developing with asyncio::

Coroutines and Tasks

* Coroutines: Coroutines<3>.
* Awaitables::
* Running an asyncio Program::
* Creating Tasks::
* Sleeping::
* Running Tasks Concurrently::
* Shielding From Cancellation::
* Timeouts::
* Waiting Primitives::
* Scheduling From Other Threads::
* Introspection::
* Task Object::
* Generator-based Coroutines::

Streams

* StreamReader::
* StreamWriter::
* Examples: Examples<11>.

Examples

* TCP echo client using streams::
* TCP echo server using streams::
* Get HTTP headers::
* Register an open socket to wait for data using streams::

Synchronization Primitives

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

Subprocesses

* Creating Subprocesses::
* Constants: Constants<7>.
* Interacting with Subprocesses::

Interacting with Subprocesses

* Subprocess and Threads::
* Examples: Examples<12>.

Queues

* Queue::
* Priority Queue::
* LIFO Queue::
* Exceptions: Exceptions<7>.
* Examples: Examples<13>.

Event Loop

* Event Loop Methods::
* Callback Handles::
* Server Objects::
* Event Loop Implementations::
* Examples: Examples<14>.

Event Loop Methods

* Running and stopping the loop::
* Scheduling callbacks::
* Scheduling delayed callbacks::
* Creating Futures and Tasks::
* Opening network connections::
* Creating network servers::
* Transferring files::
* TLS Upgrade::
* Watching file descriptors::
* Working with socket objects directly::
* DNS::
* Working with pipes::
* Unix signals::
* Executing code in thread or process pools::
* Error Handling API::
* Enabling debug mode::
* Running Subprocesses::

Examples

* Hello World with call_soon(): Hello World with call_soon.
* Display the current date with call_later(): Display the current date with call_later.
* Watch a file descriptor for read events::
* Set signal handlers for SIGINT and SIGTERM::

Futures

* Future Functions::
* Future Object::

Transports and Protocols

* Transports::
* Protocols::
* Examples: Examples<15>.

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::

Examples

* 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::

Platform Support

* All Platforms::
* Windows: Windows<52>.
* macOS: macOS<25>.

Windows

* Subprocess Support on Windows::

High-level API Index

* Tasks::
* Queues: Queues<2>.
* Subprocesses: Subprocesses<2>.
* Streams: Streams<2>.
* Synchronization::
* Exceptions: Exceptions<9>.

Low-level API Index

* Obtaining the Event Loop::
* Event Loop Methods: Event Loop Methods<2>.
* Transports: Transports<2>.
* Protocols: Protocols<2>.
* Event Loop Policies::

Developing with asyncio

* Debug Mode::
* Concurrency and Multithreading::
* Running Blocking Code::
* Logging: Logging<3>.
* Detect never-awaited coroutines::
* Detect never-retrieved exceptions::

socket — Low-level networking interface

* Socket families::
* Module contents::
* Socket Objects::
* Notes on socket timeouts::
* Example: Example<8>.

Module contents

* Exceptions: Exceptions<10>.
* Constants: Constants<8>.
* Functions: Functions<5>.

Functions

* Creating sockets::
* Other functions: Other functions<2>.

Notes on socket timeouts

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

ssl — TLS/SSL wrapper for socket objects

* Functions, Constants, and Exceptions: Functions Constants and Exceptions.
* SSL Sockets::
* SSL Contexts::
* Certificates::
* Examples: Examples<16>.
* Notes on non-blocking sockets::
* Memory BIO Support: Memory BIO Support<2>.
* SSL session::
* Security considerations::
* TLS 1.3: TLS 1 3.
* LibreSSL support::

Functions, Constants, and Exceptions

* Socket creation::
* Context creation::
* Exceptions: Exceptions<11>.
* Random generation::
* Certificate handling::
* Constants: Constants<9>.

Certificates

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

Examples

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

Security considerations

* Best defaults::
* Manual settings::
* Multi-processing::

Manual settings

* Verifying certificates::
* Protocol versions::
* Cipher selection::

select — Waiting for I/O completion

* /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 — High-level I/O multiplexing

* 簡介: 簡介<9>.
* Classes: Classes<3>.
* Examples: Examples<17>.

asyncore — Asynchronous socket handler

* asyncore Example basic HTTP client::
* asyncore Example basic echo server::

asynchat — Asynchronous socket command/response handler

* asynchat Example::

signal — Set handlers for asynchronous events

* General rules::
* Module contents: Module contents<2>.
* Example: Example<9>.
* Note on SIGPIPE::

General rules

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

mmap — Memory-mapped file support

* MADV_* Constants::

Internet Data Handling

* email: email --- An email and MIME handling package. An email and MIME handling package
* json: json --- JSON encoder and decoder. JSON encoder and decoder
* mailcap: mailcap --- Mailcap file handling. Mailcap file handling
* mailbox: mailbox --- Manipulate mailboxes in various formats. Manipulate mailboxes in various formats
* mimetypes: mimetypes --- Map filenames to MIME types. Map filenames to MIME types
* base64 —— Base16、Base32、Base64、Base85 資料編碼::
* binhex: binhex --- Encode and decode binhex4 files. Encode and decode binhex4 files
* binascii: binascii --- Convert between binary and ASCII. Convert between binary and ASCII
* quopri: quopri --- Encode and decode MIME quoted-printable data. Encode and decode MIME quoted-printable data
* uu: uu --- Encode and decode uuencode files. Encode and decode uuencode files

email — An email and MIME handling package

* email.message; Representing an email message: email message Representing an email message.
* email.parser; Parsing email messages: email parser Parsing email messages.
* email.generator; Generating MIME documents: email generator Generating MIME documents.
* email.policy; Policy Objects: email policy Policy Objects.
* email.errors; Exception and Defect classes: email errors Exception and Defect classes.
* email.headerregistry; Custom Header Objects: email headerregistry Custom Header Objects.
* email.contentmanager; Managing MIME Content: email contentmanager Managing MIME Content.
* email; Examples: email Examples.
* email.message.Message; Representing an email message using the compat32 API: email message Message Representing an email message using the compat32 API.
* email.mime; Creating email and MIME objects from scratch: email mime Creating email and MIME objects from scratch.
* email.header; Internationalized headers: email header Internationalized headers.
* email.charset; Representing character sets: email charset Representing character sets.
* email.encoders; Encoders: email encoders Encoders.
* email.utils; Miscellaneous utilities: email utils Miscellaneous utilities.
* email.iterators; Iterators: email iterators Iterators.

email.parser: Parsing email messages

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

email.contentmanager: Managing MIME Content

* Content Manager Instances::

json — JSON encoder and decoder

* Basic Usage::
* Encoders and Decoders::
* 例外: 例外<2>.
* Standard Compliance and Interoperability::
* Command Line Interface: Command Line Interface<2>.

Standard Compliance and Interoperability

* Character Encodings::
* Infinite and NaN Number Values::
* Repeated Names Within an Object::
* Top-level Non-Object, Non-Array Values: Top-level Non-Object Non-Array Values.
* Implementation Limitations::

Command Line Interface

* Command line options: Command line options<2>.

mailbox — Manipulate mailboxes in various formats

* Mailbox objects::
* Message objects::
* Exceptions: Exceptions<12>.
* Examples: Examples<18>.

Mailbox objects

* Maildir::
* mbox::
* MH::
* Babyl::
* MMDF::

Message objects

* MaildirMessage::
* mboxMessage::
* MHMessage::
* BabylMessage::
* MMDFMessage::

mimetypes — Map filenames to MIME types

* MimeTypes Objects::

binhex — Encode and decode binhex4 files

* 註解: 註解<2>.

Structured Markup Processing Tools

* html: html --- HyperText Markup Language support. HyperText Markup Language support
* html.parser: html parser --- Simple HTML and XHTML parser. Simple HTML and XHTML parser
* html.entities: html entities --- Definitions of HTML general entities. Definitions of HTML general entities
* XML 處理模組::
* xml.etree.ElementTree: xml etree ElementTree --- The ElementTree XML API. The ElementTree XML API
* xml.dom: xml dom --- The Document Object Model API. The Document Object Model API
* xml.dom.minidom: xml dom minidom --- Minimal DOM implementation. Minimal DOM implementation
* xml.dom.pulldom: xml dom pulldom --- Support for building partial DOM trees. Support for building partial DOM trees
* xml.sax: xml sax --- Support for SAX2 parsers. Support for SAX2 parsers
* xml.sax.handler: xml sax handler --- Base classes for SAX handlers. Base classes for SAX handlers
* xml.sax.saxutils: xml sax saxutils --- SAX Utilities. SAX Utilities
* xml.sax.xmlreader: xml sax xmlreader --- Interface for XML parsers. Interface for XML parsers
* xml.parsers.expat: xml parsers expat --- Fast XML parsing using Expat. Fast XML parsing using Expat

html.parser — Simple HTML and XHTML parser

* Example HTML Parser Application::
* HTMLParser Methods::
* Examples: Examples<19>.

XML 處理模組

* XML vulnerabilities::
* The defusedxml Package::

xml.etree.ElementTree — The ElementTree XML API

* Tutorial::
* XPath support::
* Reference: Reference<2>.
* XInclude support::
* Reference: Reference<3>.

Tutorial

* XML tree and elements::
* Parsing XML::
* Pull API for non-blocking parsing::
* Finding interesting elements::
* Modifying an XML File::
* Building XML documents::
* Parsing XML with Namespaces::
* Additional resources::

XPath support

* Example: Example<10>.
* Supported XPath syntax::

Reference

* Functions: Functions<6>.

XInclude support

* Example: Example<11>.

Reference

* Functions: Functions<7>.
* Element Objects::
* ElementTree Objects::
* QName Objects::
* TreeBuilder Objects::
* XMLParser Objects::
* XMLPullParser Objects::
* Exceptions: Exceptions<13>.

xml.dom — The Document Object Model API

* Module Contents: Module Contents<4>.
* Objects in the DOM::
* Conformance::

Objects in the DOM

* DOMImplementation Objects::
* Node Objects::
* NodeList Objects::
* DocumentType Objects::
* Document Objects::
* Element Objects: Element Objects<2>.
* Attr Objects::
* NamedNodeMap Objects::
* Comment Objects::
* Text and CDATASection Objects::
* ProcessingInstruction Objects::
* Exceptions: Exceptions<14>.

Conformance

* Type Mapping::
* Accessor Methods::

xml.dom.minidom — Minimal DOM implementation

* DOM Objects::
* DOM Example::
* minidom and the DOM standard::

xml.dom.pulldom — Support for building partial DOM trees

* DOMEventStream Objects::

xml.sax — Support for SAX2 parsers

* SAXException Objects::

xml.sax.handler — Base classes for SAX handlers

* ContentHandler Objects::
* DTDHandler Objects::
* EntityResolver Objects::
* ErrorHandler Objects::

xml.sax.xmlreader — Interface for XML parsers

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

xml.parsers.expat — Fast XML parsing using Expat

* XMLParser Objects: XMLParser Objects<2>.
* ExpatError Exceptions::
* Example: Example<12>.
* Content Model Descriptions::
* Expat error constants::

Internet Protocols and Support

* webbrowser: webbrowser --- Convenient Web-browser controller. Convenient Web-browser controller
* cgi: cgi --- Common Gateway Interface support. Common Gateway Interface support
* cgitb: cgitb --- Traceback manager for CGI scripts. Traceback manager for CGI scripts
* wsgiref: wsgiref --- WSGI Utilities and Reference Implementation. WSGI Utilities and Reference Implementation
* urllib: urllib --- URL handling modules. URL handling modules
* urllib.request: urllib request --- Extensible library for opening URLs. Extensible library for opening URLs
* urllib.response: urllib response --- Response classes used by urllib. Response classes used by urllib
* urllib.parse: urllib parse --- Parse URLs into components. Parse URLs into components
* urllib.error: urllib error --- Exception classes raised by urllib request. Exception classes raised by urllib.request
* urllib.robotparser: urllib robotparser --- Parser for robots txt. Parser for robots.txt
* http: http --- HTTP modules. HTTP modules
* http.client: http client --- HTTP protocol client. HTTP protocol client
* ftplib: ftplib --- FTP protocol client. FTP protocol client
* poplib: poplib --- POP3 protocol client. POP3 protocol client
* imaplib: imaplib --- IMAP4 protocol client. IMAP4 protocol client
* nntplib: nntplib --- NNTP protocol client. NNTP protocol client
* smtplib: smtplib --- SMTP protocol client. SMTP protocol client
* smtpd: smtpd --- SMTP Server. SMTP Server
* telnetlib: telnetlib --- Telnet client. Telnet client
* uuid: uuid --- UUID objects according to RFC 4122. UUID objects according to RFC 4122
* socketserver: socketserver --- A framework for network servers. A framework for network servers
* http.server: http server --- HTTP servers. HTTP servers
* http.cookies: http cookies --- HTTP state management. HTTP state management
* http.cookiejar: http cookiejar --- Cookie handling for HTTP clients. Cookie handling for HTTP clients
* xmlrpc: xmlrpc --- XMLRPC server and client modules. XMLRPC server and client modules
* xmlrpc.client: xmlrpc client --- XML-RPC client access. XML-RPC client access
* xmlrpc.server: xmlrpc server --- Basic XML-RPC servers. Basic XML-RPC servers
* ipaddress: ipaddress --- IPv4/IPv6 manipulation library. IPv4/IPv6 manipulation library

webbrowser — Convenient Web-browser controller

* Browser Controller Objects::

cgi — Common Gateway Interface support

* 簡介: 簡介<10>.
* Using the cgi module::
* Higher Level Interface::
* Functions: Functions<8>.
* Caring about security::
* Installing your CGI script on a Unix system::
* Testing your CGI script::
* Debugging CGI scripts::
* Common problems and solutions::

wsgiref — WSGI Utilities and Reference Implementation

* wsgiref.util: wsgiref util -- WSGI environment utilities. WSGI environment utilities
* wsgiref.headers: wsgiref headers -- WSGI response header tools. WSGI response header tools
* wsgiref.simple_server: wsgiref simple_server -- a simple WSGI HTTP server. a simple WSGI HTTP server
* wsgiref.validate: wsgiref validate --- WSGI conformance checker. WSGI conformance checker
* wsgiref.handlers: wsgiref handlers -- server/gateway base classes. server/gateway base classes
* Examples: Examples<20>.

urllib.request — Extensible library for opening URLs

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

urllib.parse — Parse URLs into components

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

http — HTTP modules

* HTTP status codes::

http.client — HTTP protocol client

* HTTPConnection Objects::
* HTTPResponse Objects::
* Examples: Examples<22>.
* HTTPMessage Objects::

ftplib — FTP protocol client

* FTP Objects::
* FTP_TLS Objects::

poplib — POP3 protocol client

* POP3 Objects::
* POP3 Example::

imaplib — IMAP4 protocol client

* IMAP4 Objects::
* IMAP4 Example::

nntplib — NNTP protocol client

* NNTP Objects::
* Utility functions: Utility functions<2>.

NNTP Objects

* Attributes::
* Methods: Methods<3>.

smtplib — SMTP protocol client

* SMTP Objects::
* SMTP Example::

smtpd — SMTP Server

* SMTPServer Objects::
* DebuggingServer Objects::
* PureProxy Objects::
* MailmanProxy Objects::
* SMTPChannel Objects::

telnetlib — Telnet client

* Telnet Objects::
* Telnet Example::

uuid — UUID objects according to RFC 4122

* Example: Example<13>.

socketserver — A framework for network servers

* Server Creation Notes::
* Server Objects: Server Objects<2>.
* Request Handler Objects::
* Examples: Examples<23>.

Examples

* socketserver.TCPServer Example: socketserver TCPServer Example.
* socketserver.UDPServer Example: socketserver UDPServer Example.
* Asynchronous Mixins::

http.cookies — HTTP state management

* Cookie Objects::
* Morsel Objects::
* Example: Example<14>.

http.cookiejar — Cookie handling for HTTP clients

* CookieJar and FileCookieJar Objects::
* FileCookieJar subclasses and co-operation with web browsers::
* CookiePolicy Objects::
* DefaultCookiePolicy Objects::
* Cookie Objects: Cookie Objects<2>.
* Examples: Examples<24>.

xmlrpc.client — XML-RPC client access

* ServerProxy Objects::
* 日期時間物件::
* Binary Objects::
* Fault Objects::
* ProtocolError Objects::
* MultiCall Objects::
* Convenience Functions::
* Example of Client Usage::
* Example of Client and Server Usage::

xmlrpc.server — Basic XML-RPC servers

* SimpleXMLRPCServer Objects::
* CGIXMLRPCRequestHandler::
* Documenting XMLRPC server::
* DocXMLRPCServer Objects::
* DocCGIXMLRPCRequestHandler::

SimpleXMLRPCServer Objects

* SimpleXMLRPCServer Example::

ipaddress — IPv4/IPv6 manipulation library

* 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<3>.

Operators

* Comparison operators::
* Arithmetic operators::

IP Network definitions

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

Operators

* Logical operators::
* Iteration: Iteration<2>.
* Networks as containers of addresses::

Interface objects

* Operators: Operators<5>.

Operators

* Logical operators: Logical operators<2>.

Multimedia Services

* audioop: audioop --- Manipulate raw audio data. Manipulate raw audio data
* aifc: aifc --- Read and write AIFF and AIFC files. Read and write AIFF and AIFC files
* sunau: sunau --- Read and write Sun AU files. Read and write Sun AU files
* wave: wave --- Read and write WAV files. Read and write WAV files
* chunk: chunk --- Read IFF chunked data. Read IFF chunked data
* colorsys: colorsys --- Conversions between color systems. Conversions between color systems
* imghdr: imghdr --- Determine the type of an image. Determine the type of an image
* sndhdr: sndhdr --- Determine type of sound file. Determine type of sound file
* ossaudiodev: ossaudiodev --- Access to OSS-compatible audio devices. Access to OSS-compatible audio devices

sunau — Read and write Sun AU files

* AU_read Objects::
* AU_write Objects::

wave — Read and write WAV files

* Wave_read Objects::
* Wave_write Objects::

ossaudiodev — Access to OSS-compatible audio devices

* Audio Device Objects::
* Mixer Device Objects::

國際化

* gettext: gettext --- Multilingual internationalization services. Multilingual internationalization services
* locale: locale --- Internationalization services. Internationalization services

gettext — Multilingual internationalization services

* GNU gettext API::
* Class-based API::
* Internationalizing your programs and modules::
* Acknowledgements: Acknowledgements<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 — Internationalization services

* 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 --- 龜圖學. 龜圖學
* cmd: cmd --- Support for line-oriented command interpreters. Support for line-oriented command interpreters
* shlex: shlex --- Simple lexical analysis. Simple lexical analysis

turtle — 龜圖學

* 介紹::
* Overview of available Turtle and Screen methods::
* Methods of RawTurtle/Turtle and corresponding functions::
* Methods of TurtleScreen/Screen and corresponding functions::
* Public classes::
* 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.

Overview of available Turtle and Screen methods

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

Methods of RawTurtle/Turtle and corresponding functions

* Turtle motion::
* Tell Turtle's state::
* Settings for measurement::
* Pen control::
* 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 — Support for line-oriented command interpreters

* Cmd Objects::
* Cmd Example::

shlex — Simple lexical analysis

* shlex Objects::
* Parsing Rules::
* Improved Compatibility with Shells::

以 Tk 打造 GUI

* tkinter: tkinter --- Python interface to Tcl/Tk. Python interface to Tcl/Tk
* tkinter.ttk: tkinter ttk --- Tk themed widgets. Tk themed widgets
* tkinter.tix: tkinter tix --- Extension widgets for Tk. Extension widgets for Tk
* tkinter.scrolledtext: tkinter scrolledtext --- Scrolled Text Widget. Scrolled Text Widget
* IDLE: IDLE<54>.
* 其它的 GUI::

tkinter — Python interface to Tcl/Tk

* Tkinter Modules::
* Tkinter Life Preserver::
* A (Very) Quick Look at Tcl/Tk: A Very Quick Look at Tcl/Tk.
* Mapping Basic Tk into Tkinter::
* How Tk and Tkinter are Related::
* Handy Reference::
* File Handlers::

Tkinter Life Preserver

* How To Use This Section::
* A Simple Hello World Program::

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.ttk — Tk themed widgets

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

Widget

* Standard Options::
* Scrollable Widget Options::
* Label Options::
* Compatibility Options::
* Widget States::
* ttk.Widget: ttk Widget.

Combobox

* Options::
* Virtual events::
* ttk.Combobox: ttk Combobox.

Spinbox

* Options: Options<2>.
* Virtual events: Virtual events<2>.
* ttk.Spinbox: ttk Spinbox.

Notebook

* Options: Options<3>.
* Tab Options::
* Tab Identifiers::
* Virtual Events::
* ttk.Notebook: ttk Notebook.

Progressbar

* Options: Options<4>.
* ttk.Progressbar: ttk Progressbar.

Separator

* Options: Options<5>.

Sizegrip

* Platform-specific notes::
* Bugs::

Treeview

* Options: Options<6>.
* Item Options::
* Tag Options::
* Column Identifiers::
* Virtual Events: Virtual Events<2>.
* ttk.Treeview: ttk Treeview.

Ttk Styling

* Layouts::

tkinter.tix — Extension widgets for Tk

* Using Tix::
* Tix Widgets::
* Tix Commands::

Tix Widgets

* Basic Widgets::
* File Selectors::
* Hierarchical ListBox::
* Tabular ListBox::
* Manager Widgets::
* Image Types::
* Miscellaneous Widgets::
* Form Geometry Manager::

IDLE

* Menus::
* Editing and navigation::
* Startup and code execution::
* Help and preferences::

Menus

* 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::
* Completions::
* Calltips::
* Code Context::
* Python Shell window::
* Text colors::

Startup and code execution

* Command line usage::
* 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 --- Support for type hints. Support for type hints
* pydoc: pydoc --- Documentation generator and online help system. Documentation generator and online help system
* doctest: doctest --- Test interactive Python examples. Test interactive Python examples
* unittest: unittest --- 單元測試框架. 單元測試框架
* unittest.mock: unittest mock --- mock object library. mock object library
* unittest.mock: unittest mock --- getting started. getting started
* 2to3 - 自動將 Python 2的程式碼轉成 Python 3::
* test: test --- Regression tests package for Python. Regression tests package for Python
* test.support: test support --- Utilities for the Python test suite. Utilities for the Python test suite
* test.support.script_helper: test support script_helper --- Utilities for the Python execution tests. Utilities for the Python execution tests

typing — Support for type hints

* Type aliases::
* NewType::
* Callable::
* Generics::
* User-defined generic types::
* The Any type::
* Nominal vs structural subtyping::
* Classes, functions, and decorators: Classes functions and decorators.

doctest — Test interactive Python examples

* 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::
* Basic 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?::
* Option Flags::
* Directives::
* Warnings: Warnings<2>.

Advanced API

* DocTest Objects::
* Example Objects::
* DocTestFinder objects::
* DocTestParser objects::
* DocTestRunner objects::
* OutputChecker objects::

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::

Test cases

* Deprecated aliases::

Loading and running tests

* load_tests Protocol::

Class and Module Fixtures

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

unittest.mock — mock object library

* Quick Guide::
* The Mock Class::
* The patchers::
* MagicMock and magic method support::
* Helpers::

The Mock Class

* Calling::
* Deleting Attributes::
* Mock names and the name attribute::
* Attaching Mocks as Attributes::

The patchers

* patch::
* patch.object: patch object.
* patch.dict: patch dict.
* patch.multiple: patch multiple.
* patch methods; start and stop: patch methods start and stop.
* patch builtins::
* TEST_PREFIX::
* Nesting Patch Decorators::
* Where to patch::
* Patching Descriptors and Proxy Objects::

MagicMock and magic method support

* Mocking Magic Methods::
* Magic Mock::

Helpers

* sentinel::
* DEFAULT::
* call::
* create_autospec::
* ANY::
* FILTER_DIR::
* mock_open::
* Autospeccing::
* Sealing mocks::

unittest.mock — getting started

* Using Mock::
* Patch Decorators::
* Further Examples::

Using Mock

* Mock Patching Methods::
* Mock for Method Calls on an Object::
* Mocking Classes::
* Naming your mocks::
* Tracking all Calls::
* Setting Return Values and Attributes::
* Raising exceptions with mocks::
* Side effect functions and iterables::
* Mocking asynchronous iterators::
* Mocking asynchronous context manager::
* Creating a Mock from an Existing Object::

Further Examples

* Mocking chained calls::
* Partial mocking::
* Mocking a Generator Method::
* Applying the same patch to every test method::
* Mocking Unbound Methods::
* Checking multiple calls with mock::
* Coping with mutable arguments::
* Nesting Patches::
* Mocking a dictionary with MagicMock::
* Mock subclasses and their attributes::
* Mocking imports with patch.dict: Mocking imports with patch dict.
* Tracking order of calls and less verbose call assertions::
* More complex argument matching::

2to3 - 自動將 Python 2的程式碼轉成 Python 3

* 使用 2to3::
* Fixers::
* lib2to3 - 2to3's library::

test — Regression tests package for Python

* Writing Unit Tests for the test package::
* Running tests using the command-line interface::

Debugging and Profiling

* Audit events table::
* bdb: bdb --- Debugger framework. Debugger framework
* faulthandler: faulthandler --- Dump the Python traceback. Dump the Python traceback
* pdb: pdb --- The Python Debugger. The Python Debugger
* The Python Profilers::
* timeit: timeit --- Measure execution time of small code snippets. Measure execution time of small code snippets
* trace: trace --- Trace or track Python statement execution. Trace or track Python statement execution
* tracemalloc: tracemalloc --- Trace memory allocations. Trace memory allocations

faulthandler — Dump the Python traceback

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

pdb — The Python Debugger

* Debugger Commands::

The Python Profilers

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

timeit — Measure execution time of small code snippets

* 基礎範例: 基礎範例<2>.
* Python Interface::
* 命令執行列介面::
* Examples: Examples<25>.

trace — Trace or track Python statement execution

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

Command-Line Usage

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

tracemalloc — Trace memory allocations

* Examples: Examples<26>.
* API::

Examples

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

API

* Functions: Functions<9>.
* DomainFilter::
* Filter::
* Frame::
* Snapshot::
* Statistic::
* StatisticDiff::
* Trace::
* Traceback::

軟體封裝與發布

* distutils: distutils --- Building and installing Python modules. Building and installing Python modules
* ensurepip: ensurepip --- Bootstrapping the pip installer. Bootstrapping the pip installer
* venv: venv --- Creation of virtual environments. Creation of virtual environments
* zipapp: zipapp --- Manage executable Python zip archives. Manage executable Python zip archives

ensurepip — Bootstrapping the pip installer

* Command line interface::
* Module API::

venv — Creation of virtual environments

* Creating virtual environments::
* API: API<2>.
* An example of extending EnvBuilder::

zipapp — Manage executable Python zip archives

* Basic Example::
* 命令執行列介面: 命令執行列介面<2>.
* Python API::
* Examples: Examples<27>.
* Specifying the Interpreter::
* Creating Standalone Applications with zipapp::
* The Python Zip Application Archive Format::

Creating Standalone Applications with zipapp

* Making a Windows executable::
* Caveats::

Python Runtime Services

* sys: sys --- System-specific parameters and functions. System-specific parameters and functions
* sysconfig: sysconfig --- Provide access to Python's configuration information. Provide access to Python’s configuration information
* builtins: builtins --- Built-in objects. Built-in objects
* __main__: __main__ --- Top-level script environment. Top-level script environment
* warnings: warnings --- Warning control. Warning control
* dataclasses: dataclasses --- Data Classes. Data Classes
* contextlib: contextlib --- Utilities for with-statement contexts. Utilities for with-statement contexts
* abc: abc --- Abstract Base Classes. Abstract Base Classes
* atexit: atexit --- Exit handlers. Exit handlers
* traceback: traceback --- Print or retrieve a stack traceback. Print or retrieve a stack traceback
* __future__: __future__ --- Future statement definitions. Future statement definitions
* gc: gc --- Garbage Collector interface. Garbage Collector interface
* inspect: inspect --- Inspect live objects. Inspect live objects
* site: site --- Site-specific configuration hook. Site-specific configuration hook

sysconfig — Provide access to Python’s configuration information

* Configuration variables::
* Installation paths::
* Other functions: Other functions<3>.
* Using sysconfig as a script::

warnings — Warning control

* 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

* Module-level decorators, classes, and functions: Module-level decorators classes and functions.
* Post-init processing::
* Class variables::
* Init-only variables::
* Frozen instances::
* Inheritance: Inheritance<2>.
* Default factory functions::
* Mutable default values::
* Exceptions: Exceptions<15>.

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 — Exit handlers

* atexit Example::

traceback — Print or retrieve a stack traceback

* TracebackException Objects::
* StackSummary Objects::
* FrameSummary Objects::
* Traceback Examples::

inspect — Inspect live objects

* Types and members::
* Retrieving source code::
* Introspecting callables with the Signature object::
* Classes and functions: Classes and functions<2>.
* The interpreter stack::
* Fetching attributes statically::
* Current State of Generators and Coroutines::
* Code Objects Bit Flags::
* Command Line Interface: Command Line Interface<3>.

site — Site-specific configuration hook

* Readline configuration::
* Module contents: Module contents<3>.
* Command Line Interface: Command Line Interface<4>.

Custom Python Interpreters

* code: code --- Interpreter base classes. Interpreter base classes
* codeop: codeop --- Compile Python code. Compile Python code

code — Interpreter base classes

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

匯入模組

* zipimport: zipimport --- Import modules from Zip archives. Import modules from Zip archives
* pkgutil: pkgutil --- Package extension utility. Package extension utility
* modulefinder: modulefinder --- Find modules used by a script. Find modules used by a script
* runpy: runpy --- Locating and executing Python modules. Locating and executing Python modules
* importlib: importlib --- The implementation of import. The implementation of import
* Using importlib.metadata: Using importlib metadata.

zipimport — Import modules from Zip archives

* zipimporter Objects::
* Examples: Examples<28>.

modulefinder — Find modules used by a script

* Example usage of ModuleFinder::

importlib — The implementation of import

* 簡介: 簡介<11>.
* Functions: Functions<10>.
* importlib.abc: importlib abc -- Abstract base classes related to import. Abstract base classes related to import
* importlib.resources: importlib resources -- Resources. Resources
* importlib.machinery: importlib machinery -- Importers and path hooks. Importers and path hooks
* importlib.util: importlib util -- Utility code for importers. Utility code for importers
* Examples: Examples<29>.

Examples

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

Using importlib.metadata

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

Functional API

* Entry points::
* Distribution metadata::
* Distribution versions::
* Distribution files::
* Distribution requirements::

Python Language Services

* parser: parser --- Access Python parse trees. Access Python parse trees
* ast: ast --- Abstract Syntax Trees. Abstract Syntax Trees
* symtable: symtable --- Access to the compiler's symbol tables. Access to the compiler’s symbol tables
* symbol: symbol --- Constants used with Python parse trees. Constants used with Python parse trees
* token: token --- Constants used with Python parse trees. Constants used with Python parse trees
* keyword: keyword --- Testing for Python keywords. Testing for Python keywords
* tokenize: tokenize --- Tokenizer for Python source. Tokenizer for Python source
* tabnanny: tabnanny --- Detection of ambiguous indentation. Detection of ambiguous indentation
* pyclbr: pyclbr --- Python module browser support. Python module browser support
* py_compile: py_compile --- Compile Python source files. Compile Python source files
* compileall: compileall --- Byte-compile Python libraries. Byte-compile Python libraries
* dis: dis --- Python bytecode的反組譯器. Python bytecode的反組譯器
* pickletools: pickletools --- Tools for pickle developers. Tools for pickle developers

parser — Access Python parse trees

* Creating ST Objects::
* Converting ST Objects::
* Queries on ST Objects::
* Exceptions and Error Handling::
* ST Objects::
* Example; Emulation of compile(): Example Emulation of compile.

ast — Abstract Syntax Trees

* Node classes::
* Abstract Grammar::
* ast Helpers::

symtable — Access to the compiler’s symbol tables

* Generating Symbol Tables::
* Examining Symbol Tables::

tokenize — Tokenizer for Python source

* Tokenizing Input::
* Command-Line Usage: Command-Line Usage<2>.
* Examples: Examples<30>.

pyclbr — Python module browser support

* 函式物件::
* Class Objects: Class Objects<2>.

compileall — Byte-compile Python libraries

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

dis — Python bytecode的反組譯器

* Bytecode analysis::
* Analysis functions::
* Python Bytecode Instructions::
* Opcode collections::

pickletools — Tools for pickle developers

* Command line usage: Command line usage<2>.
* Programmatic Interface: Programmatic Interface<2>.

Command line usage

* Command line options: Command line options<3>.

Miscellaneous Services

* formatter: formatter --- Generic output formatting. Generic output formatting

formatter — Generic output formatting

* The Formatter Interface::
* Formatter Implementations::
* The Writer Interface::
* Writer Implementations::

MS Windows Specific Services

* msilib: msilib --- Read and write Microsoft Installer files. Read and write Microsoft Installer files
* msvcrt: msvcrt --- Useful routines from the MS VC++ runtime. Useful routines from the MS VC++ runtime
* winreg: winreg --- Windows registry access. Windows registry access
* winsound: winsound --- Sound-playing interface for Windows. Sound-playing interface for Windows

msilib — Read and write Microsoft Installer files

* Database Objects::
* View Objects::
* Summary Information Objects::
* Record Objects::
* Errors::
* CAB Objects::
* Directory Objects::
* Features: Features<3>.
* GUI classes::
* Precomputed tables::

msvcrt — Useful routines from the MS VC++ runtime

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

winreg — Windows registry access

* Functions: Functions<11>.
* Constants: Constants<10>.
* Registry Handle Objects::

Constants

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

Access Rights

* 64-bit Specific::

Unix Specific Services

* posix: posix --- The most common POSIX system calls. The most common POSIX system calls
* pwd: pwd --- The password database. The password database
* spwd: spwd --- The shadow password database. The shadow password database
* grp: grp --- The group database. The group database
* crypt: crypt --- Function to check Unix passwords. Function to check Unix passwords
* termios: termios --- POSIX style tty control. POSIX style tty control
* tty: tty --- Terminal control functions. Terminal control functions
* pty: pty --- Pseudo-terminal utilities. Pseudo-terminal utilities
* fcntl: fcntl --- The fcntl and ioctl system calls. The fcntl and ioctl system calls
* pipes: pipes --- Interface to shell pipelines. Interface to shell pipelines
* resource: resource --- Resource usage information. Resource usage information
* nis: nis --- Interface to Sun's NIS Yellow Pages. Interface to Sun’s NIS (Yellow Pages)
* syslog: syslog --- Unix syslog library routines. Unix syslog library routines

posix — The most common POSIX system calls

* Large File Support::
* Notable Module Contents::

crypt — Function to check Unix passwords

* Hashing Methods::
* Module Attributes::
* Module Functions: Module Functions<2>.
* Examples: Examples<31>.

termios — POSIX style tty control

* Example: Example<16>.

pty — Pseudo-terminal utilities

* Example: Example<17>.

pipes — Interface to shell pipelines

* Template Objects::

resource — Resource usage information

* Resource Limits::
* Resource Usage::

syslog — Unix syslog library routines

* Examples: Examples<32>.

Examples

* Simple example::

Superseded Modules

* optparse: optparse --- Parser for command line options. Parser for command line options
* imp: imp --- Access the import internals. Access the import internals

optparse — Parser for command line options

* Background::
* Tutorial: Tutorial<2>.
* Reference Guide::
* Option Callbacks::
* Extending optparse::

Background

* Terminology::
* What are options for?::
* What are positional arguments for?::

Tutorial

* 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::
* Parsing arguments: Parsing arguments<2>.
* Querying and manipulating your option parser::
* Conflicts between options::
* Cleanup: Cleanup<2>.
* Other methods::

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::

imp — Access the import internals

* Examples: Examples<33>.

Undocumented Modules

* Platform specific modules::

Extending and Embedding the Python Interpreter

* Recommended third party tools::
* Creating extensions without third party tools::
* Embedding the CPython runtime in a larger application::

Creating extensions without third party tools

* 以 C 或 C++ 擴充 Python::
* Defining Extension Types; Tutorial: Defining Extension Types Tutorial.
* Defining Extension Types; Assorted Topics: Defining Extension Types Assorted Topics.
* Building C and C++ Extensions::
* Building C and C++ Extensions on Windows::

以 C 或 C++ 擴充 Python

* A Simple Example::
* Intermezzo; Errors and Exceptions: Intermezzo Errors and Exceptions.
* Back to the Example::
* 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 Pointers::

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::

Building C and C++ Extensions

* Building C and C++ Extensions with distutils::
* Distributing your extension modules::

Building C and C++ Extensions on Windows

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

Embedding the CPython runtime in a larger application

* 在其它 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 參考手冊

* 簡介: 簡介<12>.
* Stable Application Binary Interface::
* The Very High Level Layer::
* 參照計數::
* 例外處理::
* 工具::
* 抽象物件層::
* Concrete Objects Layer::
* Initialization, Finalization, and Threads: Initialization Finalization and Threads.
* Python Initialization Configuration::
* 記憶體管理::
* Object Implementation Support::
* API and ABI Versioning::

簡介

* Coding standards::
* Include Files::
* Useful macros::
* Objects, Types and Reference Counts: Objects Types and Reference Counts.
* Exceptions: Exceptions<16>.
* 嵌入式Python::
* Debugging Builds::

Objects, Types and Reference Counts

* Reference Counts: Reference Counts<2>.
* Types::

Reference Counts

* Reference Count Details::

例外處理

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

工具

* 作業系統工具::
* 系統函式::
* 行程（Process）控制::
* 匯入模組: 匯入模組<2>.
* Data marshalling support::
* Parsing arguments and building values::
* 字串轉換與格式化::
* Reflection::
* Codec registry and support functions::

Parsing arguments and building values

* Parsing arguments: Parsing arguments<3>.
* Building values::

Parsing arguments

* Strings and buffers::
* 數字::
* Other objects::
* API Functions::

Codec registry and support functions

* Codec lookup API::
* Registry API for Unicode encoding error handlers::

抽象物件層

* Object Protocol::
* Number Protocol::
* Sequence Protocol::
* Mapping Protocol::
* Iterator Protocol::
* Buffer Protocol::
* Old Buffer Protocol::

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.

Concrete Objects Layer

* Fundamental Objects::
* Numeric Objects::
* Sequence Objects::
* Container Objects::
* 函式物件: 函式物件<2>.
* Other Objects::

Fundamental Objects

* Type Objects: Type Objects<2>.
* The None Object::

Type Objects

* Creating Heap-Allocated Types::

Numeric Objects

* 整數物件::
* 布林物件::
* 浮點數（Floating Point）物件::
* Complex Number Objects::

Complex Number Objects

* Complex Numbers as C Structures::
* Complex Numbers as Python Objects::

Sequence Objects

* Bytes Objects: Bytes Objects<2>.
* Byte Array Objects::
* Unicode物件與編碼::
* 元組（Tuple）物件::
* Struct Sequence Objects::
* List（串列）物件::

Byte Array Objects

* Type check macros::
* Direct API functions::
* Macros::

Unicode物件與編碼

* Unicode Objects::
* Built-in Codecs::
* Methods and Slot Functions::

Unicode Objects

* Unicode Type::
* Unicode Character Properties::
* Creating and accessing Unicode strings::
* Deprecated Py_UNICODE APIs::
* Locale Encoding::
* File System Encoding::
* wchar_t Support::

Built-in Codecs

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

Container Objects

* 字典物件::
* Set Objects::

函式物件

* 函式（Function）物件::
* 實體方法物件::
* Method Objects: Method Objects<2>.
* Cell 物件::
* Code Objects: Code Objects<2>.

Other Objects

* 檔案（File）物件::
* 模組物件模組::
* 迭代器（Iterator）物件::
* 修飾器物件::
* 切片物件::
* Ellipsis Object::
* MemoryView objects::
* 弱參照物件::
* Capsules: Capsules<2>.
* 產生器物件::
* Coroutine Objects: Coroutine Objects<2>.
* Context Variables Objects::
* DateTime 物件::

模組物件模組

* Initializing C modules::
* Module lookup::

Initializing C modules

* Single-phase initialization::
* Multi-phase initialization::
* Low-level module creation functions::
* Support functions::

Initialization, Finalization, and Threads

* Before Python Initialization::
* 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::
* Advanced Debugger Support::
* Thread Local Storage Support::

Thread State and the Global Interpreter Lock

* Releasing the GIL from extension code::
* Non-Python created threads::
* Cautions about fork(): Cautions about fork.
* High-level API::
* Low-level API::

Sub-interpreter support

* 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::
* Methods: Methods<4>.

Python Initialization Configuration

* PyWideStringList::
* PyStatus::
* PyPreConfig::
* Preinitialization with PyPreConfig::
* PyConfig::
* Initialization with PyConfig::
* Isolated Configuration::
* Python Configuration::
* Path Configuration::
* Py_RunMain(): Py_RunMain.
* Multi-Phase Initialization Private Provisional API::

記憶體管理

* 總覽: 總覽<2>.
* Raw Memory Interface::
* Memory Interface::
* Object allocators::
* Default Memory Allocators::
* Customize Memory Allocators::
* The pymalloc allocator::
* tracemalloc C API::
* Examples: Examples<34>.

The pymalloc allocator

* Customize pymalloc Arena Allocator::

Object Implementation Support

* Allocating Objects on the Heap::
* 通用物件結構::
* Type Objects: Type Objects<3>.
* Number Object Structures::
* Mapping Object Structures::
* Sequence Object Structures::
* Buffer Object Structures::
* Async Object Structures::
* Slot Type typedefs::
* Examples: Examples<35>.
* Supporting Cyclic Garbage Collection::

Type Objects

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

Quick Reference

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

發布 Python 模組

* Key terms::
* Open source licensing and collaboration::
* Installing the tools::
* Reading the Python Packaging User Guide::
* How do I...?: How do I ?.

How do I...?

* ... choose a name for my project?: choose a name for my project?.
* ... create and distribute binary extensions?: create and distribute binary extensions?.

安裝 Python 模組

* Key terms: Key terms<2>.
* Basic usage::
* How do I ...?: How do I ?<2>.
* Common installation issues::

How do I ...?

* ... install pip in versions of Python prior to Python 3.4?: install pip in versions of Python prior to Python 3 4?.
* ... install packages just for the current user?: install packages just for the current user?.
* ... install scientific Python packages?: install scientific Python packages?.
* ... work with multiple versions of Python installed in parallel?: work with multiple versions of Python installed in parallel?.

Common installation issues

* Installing into the system Python on Linux::
* Pip not installed::
* Installing binary extensions::

Python HOWTOs

* Python 2 的程式碼移植到Python 3::
* 遷移延伸模組到 Python 3::
* Curses Programming with Python::
* 修飾器 HowTo 指南::
* 函式編程 HOWTO::
* 如何使用 Logging 模組::
* Logging Cookbook::
* 如何使用正規表達式::
* Socket Programming HOWTO::
* 如何排序::
* Unicode HOWTO::
* 如何使用urllib套件取得網路資源::
* Argparse 教學::
* ipaddress模組介紹::
* Argument Clinic How-To::
* Instrumenting CPython with DTrace and SystemTap::

Python 2 的程式碼移植到Python 3

* 簡短的說明::
* 詳細的::

詳細的

* 向下支援Python 2.6和更舊的版本: 向下支援Python 2 6和更舊的版本.
* Make sure you specify the proper version support in your setup.py file: Make sure you specify the proper version support in your setup py file.
* 有好的測試覆蓋率::
* 瞭解Python 2 & 3的差異::
* 更新你的程式碼::
* Prevent compatibility regressions::
* Check which dependencies block your transition::
* Update your setup.py file to denote Python 3 compatibility: Update your setup py file to denote Python 3 compatibility.
* Use continuous integration to stay compatible::
* Consider using optional static type checking::

更新你的程式碼

* Division::
* Text versus binary data::
* Use feature detection instead of version detection::

Curses Programming with Python

* What is curses?::
* Starting and ending a curses application::
* Windows and Pads::
* Displaying Text::
* User Input::
* For More Information::

What is curses?

* The Python curses module::

Displaying Text

* Attributes and Color::

修飾器 HowTo 指南

* 摘要::
* Definition and Introduction::
* Descriptor Protocol::
* Invoking Descriptors: Invoking Descriptors<2>.
* Descriptor Example::
* Properties::
* Functions and Methods::
* Static Methods and Class Methods::

函式編程 HOWTO

* 簡介: 簡介<13>.
* Iterators: Iterators<2>.
* Generator expressions and list comprehensions::
* Generators: Generators<2>.
* Built-in functions::
* The itertools module::
* The functools module::
* 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::

The itertools module

* Creating new iterators::
* Calling functions on elements::
* Selecting elements::
* Combinatoric functions::
* Grouping elements::

The functools module

* The operator module::

References

* General::
* Python-specific::
* Python documentation::

如何使用 Logging 模組

* 基礎 Logging 指南::
* Advanced Logging Tutorial::
* Logging Levels: Logging Levels<2>.
* Useful Handlers::
* Exceptions raised during logging::
* Using arbitrary objects as messages::
* Optimization::

基礎 Logging 指南

* 什麼時候使用 logging::
* A simple example::
* Logging to a file::
* Logging from multiple modules::
* 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::
* Configuration server example::
* Dealing with handlers that block::
* Sending and receiving logging events across a network::
* Adding contextual information to your logging output::
* Logging to a single file from multiple processes::
* Using file rotation::
* Use of alternative formatting styles::
* Customizing LogRecord::
* Subclassing QueueHandler - a ZeroMQ example::
* Subclassing QueueListener - a ZeroMQ 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::
* 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::

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.

Using particular formatting styles throughout your application

* Using LogRecord factories::
* Using custom message objects::

如何使用正規表達式

* 簡介: 簡介<14>.
* 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::

Common Problems

* Use String Methods::
* match() versus search(): match versus search.
* Greedy versus Non-Greedy::
* Using re.VERBOSE: Using re VERBOSE.

Socket Programming HOWTO

* Sockets::
* Creating a Socket::
* Using a Socket::
* Disconnecting::
* Non-blocking Sockets::

Sockets

* History::

Creating a Socket

* IPC::

Using a Socket

* Binary Data::

Disconnecting

* When Sockets Die::

如何排序

* 排序 基本::
* Key Functions::
* Operator Module Functions::
* 升冪與降冪::
* Sort Stability and Complex Sorts::
* The Old Way Using Decorate-Sort-Undecorate::
* The Old Way Using the cmp Parameter::
* Odd and Ends::

Unicode HOWTO

* Introduction to Unicode::
* Python's Unicode Support::
* Reading and Writing Unicode Data::
* Acknowledgements: Acknowledgements<10>.

Introduction to Unicode

* Definitions::
* 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套件取得網路資源

* 簡介: 簡介<15>.
* 從URL取得資源::
* Handling Exceptions::
* info and geturl::
* Openers and Handlers::
* Basic Authentication::
* Proxies::
* Sockets and Layers::
* 註解: 註解<3>.

從URL取得資源

* Data::
* Headers::

Handling Exceptions

* URLError::
* HTTPError::
* Wrapping it Up::

HTTPError

* Error Codes::

Wrapping it Up

* Number 1::
* Number 2::

Argparse 教學

* 概念::
* 基本用法::
* 介紹位置參數::
* 介紹選項參數::
* 現在結合位置與選項參數::
* Getting a little more advanced::
* 結論::

介紹選項參數

* Short options::

Getting a little more advanced

* Conflicting options::

ipaddress模組介紹

* Creating Address/Network/Interface objects::
* Inspecting Address/Network/Interface Objects::
* Networks as lists of Addresses::
* Comparisons: Comparisons<4>.
* 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::
* Defining Networks::
* Host Interfaces::

Argument Clinic How-To

* The Goals Of Argument Clinic::
* Basic Concepts And Usage::
* Converting Your First Function::
* Advanced Topics::

Advanced Topics

* Symbolic default values::
* Renaming the C functions and variables generated by Argument Clinic::
* Converting functions using PyArg_UnpackTuple::
* Optional Groups::
* Using real Argument Clinic converters, instead of "legacy converters": Using real Argument Clinic converters instead of "legacy converters".
* Py_buffer::
* Advanced converters::
* Parameter default values::
* The NULL default value::
* Expressions specified as default values::
* Using a return converter::
* Cloning existing functions::
* Calling Python code::
* Using a "self converter"::
* Writing a custom converter::
* Writing a custom return converter::
* METH_O and METH_NOARGS::
* tp_new and tp_init functions::
* Changing and redirecting Clinic's output::
* The #ifdef trick::
* Using Argument Clinic in Python files::

Instrumenting CPython with DTrace and SystemTap

* Enabling the static markers::
* Static DTrace probes::
* Static SystemTap markers::
* Available static markers::
* SystemTap Tapsets::
* Examples: Examples<36>.

Python 常見問題

* 常見Python問答集::
* 程式開發常見問答集::
* Design and History FAQ::
* 函式庫和擴充功能的常見問題::
* Extending/Embedding FAQ::
* FAQ：在 Windows 使用 Python::
* 圖形化使用者界面常見問答集::
* 為什麼Python被安裝在我的機器上?常見問答集::

常見Python問答集

* 常見資訊::
* Python在真實世界::

常見資訊

* 什麼是Python?::
* 什麼是Python軟體基金會?::
* 當使用Python時有任何版權限制嗎?::
* 為什麼Python被創造出來::
* 什麼是Python擅長的事情::
* How does the Python version numbering scheme work?::
* 我如何拿到Python的原始碼::
* 如何取得Python的相關文件::
* 我從來沒寫過程式，有沒有Python的教學::
* 有沒有新手的群組或是郵件群組討論Python::
* How do I get a beta test version of Python?::
* How do I submit bug reports and patches for Python?::
* Are there any published articles about Python that I can reference?::
* 有沒有關於Python的書::
* www.python.org 這個非營利組織位於哪裡: www python org 這個非營利組織位於哪裡.
* 為什麼要取名為Python::
* 我需要喜歡蒙提·派森的飛行馬戲團這個節目嗎::

Python在真實世界

* Python穩定性如何::
* 有多少人使用Python::
* 有沒有任何重要的案子使用Python完成開發::
* 對於程式開發者Python對於未來有什麼期待::
* Is it reasonable to propose incompatible changes to Python?::
* Python對於入門的程式設計者而言是否為好的程式語言::

程式開發常見問答集

* 常見問題::
* Core Language::
* Numbers and strings::
* Performance: Performance<4>.
* Sequences (Tuples/Lists): Sequences Tuples/Lists.
* Objects::
* Modules: Modules<2>.

常見問題

* 是否有可以使用在程式碼階段,具有中斷點,步驟執行等功能的除錯器？: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？.
* Are there tools to help find bugs or perform static analysis?::
* How can I create a stand-alone binary from a Python script?::
* Are there coding standards or a style guide for Python programs?::

Core Language

* 為什麼當變數有值時我得到錯誤訊息 UnboundLocalError::
* Python 的區域變數和全域變數有什麼規則？::
* Why do lambdas defined in a loop with different values all return the same result?::
* How do I share global variables across modules?::
* 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?::
* What is the difference between arguments and parameters?::
* Why did changing list 'y' also change 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?::
* How do I copy an object in Python?::
* How can I find the methods or attributes of an object?::
* How can my code discover the name of an object?::
* What's up with the comma operator's precedence?::
* Is there an equivalent of C’s "?;" ternary operator?: Is there an equivalent of C's "? " ternary operator?.
* 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?.

Numbers and strings

* How do I specify hexadecimal and octal integers?::
* Why does -22 // 10 return -3?::
* How do I convert a string to a number?::
* How do I convert a number to a string?::
* 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?.
* What does 'UnicodeDecodeError' or 'UnicodeEncodeError' error mean?::

Performance

* My program is too slow. How do I speed it up?: My program is too slow How do I speed it up?.
* 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 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?::

Objects

* What is a class?::
* What is a 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 overrides 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?.

Modules

* How do I create a .pyc file?: How do I create a pyc file?.
* How do I find the current module name?::
* How can I have modules that mutually import each other?::
* __import__(’x.y.z’) returns <module ’x’>; how do I get z?: __import__ 'x y z' returns <module 'x'>; how do I get z?.
* When I edit an imported module and reimport it, the changes don’t show up. Why does this happen?: When I edit an imported module and reimport it the changes don't show up Why does this happen?.

Design and History FAQ

* Why does Python use indentation for grouping of statements?::
* Why am I getting strange results with simple arithmetic operations?::
* 為何浮點數運算如此不精確?::
* 為何Python字串為不可變動::
* Why must 'self' be used explicitly in method definitions and calls?::
* Why can't I use an assignment in an expression?::
* Why does Python use methods for some functionality (e.g. list.index()) but functions for other (e.g. len(list))?: Why does Python use methods for some functionality e g list index but functions for other e g len list ?.
* Why is join() a string method instead of a list or tuple method?: Why is join a string method instead of a list or tuple method?.
* How fast are exceptions?::
* Why isn't there a switch or case statement in Python?::
* Can't you emulate threads in the interpreter instead of relying on an OS-specific thread implementation?::
* 為何lambda表示式不能包含在敘述內::
* Python可以被編譯成機器語言或C語言或其他種語言嗎?::
* Python如何管理記憶體?::
* 為何CPython不使用更多傳統的垃圾回收機制?::
* 當CPython結束時，為何所有的記憶體不會被釋放?::
* Why are there separate tuple and list data types?::
* How are lists implemented in CPython?::
* How are dictionaries implemented in CPython?::
* Why must dictionary keys be immutable?::
* 為何list.sort()不是回傳排序過的串列?: 為何list sort 不是回傳排序過的串列?.
* How do you specify and enforce an interface spec in Python?::
* 為何沒有goto語法?::
* Why can’t raw strings (r-strings) end with a backslash?: Why can't raw strings r-strings end with a backslash?.
* Why doesn't Python have a "with" statement for attribute assignments?::
* Why are colons required for the if/while/def/class statements?::
* Why does Python allow commas at the end of lists and tuples?::

函式庫和擴充功能的常見問題

* 常見函式問題::
* 一般性的工作::
* Threads::
* Input and Output::
* Network/Internet Programming::
* Databases::
* Mathematics and Numerics::

常見函式問題

* How do I find a module or application to perform task X?::
* 哪裡可以找到math.py (socket.py, regex.py, 等...) 原始檔案: 哪裡可以找到math py socket py regex py 等 原始檔案.
* 我如何使Python script 執行在Unix ?::
* Is there a curses/termcap package for Python?::
* Is there an equivalent to C’s onexit() in Python?: Is there an equivalent to C's onexit in Python?.
* Why don't my signal handlers work?::

一般性的工作

* 我如何測試Python程式::
* How do I create documentation from doc strings?::
* How do I get a single keypress at a time?::

Threads

* How do I program using threads?::
* None of my threads seem to run; why?: None of my threads seem to run why?.
* How do I parcel out work among a bunch of worker threads?::
* What kinds of global value mutation are thread-safe?::
* Can't we get rid of the Global Interpreter Lock?::

Input and Output

* How do I delete a file? (And other file questions...): How do I delete a file? And other file questions.
* How do I copy a file?::
* How do I read (or write) binary data?: How do I read or write binary data?.
* 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?.
* How do I access the serial (RS232) port?: How do I access the serial RS232 port?.
* Why doesn’t closing sys.stdout (stdin, stderr) really close it?: Why doesn't closing sys stdout stdin stderr really close it?.

Network/Internet Programming

* What WWW tools are there for Python?::
* How can I mimic CGI form submission (METHOD=POST)?: How can I mimic CGI form submission METHOD=POST ?.
* What module should I use to help with generating HTML?::
* How do I send mail from a Python script?::
* How do I avoid blocking in the connect() method of a socket?: How do I avoid blocking in the connect method of a socket?.

Databases

* Are there any interfaces to database packages in Python?::
* How do you implement persistent objects in Python?::

Mathematics and Numerics

* How do I generate random numbers in Python?::

Extending/Embedding FAQ

* Can I create my own functions in C?::
* Can I create my own functions in C++?::
* Writing C is hard; are there any alternatives?::
* How can I execute arbitrary Python statements from C?::
* How can I evaluate an arbitrary Python expression from C?::
* How do I extract C values from a Python object?::
* How do I use Py_BuildValue() to create a tuple of arbitrary length?: How do I use Py_BuildValue to create a tuple of arbitrary length?.
* How do I call an object's method from C?::
* How do I catch the output from PyErr_Print() (or anything that prints to stdout/stderr)?: How do I catch the output from PyErr_Print or anything that prints to stdout/stderr ?.
* How do I access a module written in Python from C?::
* How do I interface to C++ objects from Python?::
* I added a module using the Setup file and the make fails; why?::
* How do I debug an extension?::
* I want to compile a Python module on my Linux system, but some files are missing. Why?: I want to compile a Python module on my Linux system but some files are missing Why?.
* How do I tell "incomplete input" from "invalid input"?::
* How do I find undefined g++ symbols __builtin_new or __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 ?.

FAQ：在 Windows 使用 Python

* 在 Windows 作業系統裡我想執行 Python 程式，要怎麼做？::
* How do I make Python scripts executable?::
* Why does Python sometimes take so long to start?::
* How do I make an executable from a Python script?::
* Is a *.pyd file the same as a DLL?: Is a * pyd file the same as a DLL?.
* How can I embed Python into a Windows application?::
* How do I keep editors from inserting tabs into my Python source?::
* How do I check for a keypress without blocking?::

圖形化使用者界面常見問答集

* 常見圖形化使用者界面(GUI) 問題: 常見圖形化使用者界面 GUI 問題.
* What platform-independent GUI toolkits exist for Python?::
* What platform-specific GUI toolkits exist for Python?::
* Tkinter questions::

What platform-independent GUI toolkits exist for Python?

* Tkinter::
* wxWidgets::
* Qt::
* Gtk+::
* Kivy::
* FLTK::
* 開放圖形庫(OpenGL): 開放圖形庫 OpenGL.

Tkinter questions

* How do I freeze Tkinter applications?::
* Can I have Tk events handled while waiting for I/O?::
* I can’t get key bindings to work in Tkinter; why?: I can't get key bindings to work in Tkinter why?.

為什麼Python被安裝在我的機器上?常見問答集

* 什麼是Python?: 什麼是Python?<2>.
* 為什麼Python被安裝在我的機器上?::
* 我能夠自行刪除Python嗎?::

關於這些說明文件

* Python 文件的貢獻者們::

處理 Bug

* 說明文件錯誤::
* 使用 Python 議題追蹤::
* 開始讓自己貢獻 Python::

歷史與授權

* History of the software::
* Terms and conditions for accessing or otherwise using Python::
* Licenses and Acknowledgements for Incorporated Software::

Terms and conditions for accessing or otherwise using Python

* PSF LICENSE AGREEMENT FOR PYTHON 3.8.11: PSF LICENSE AGREEMENT FOR PYTHON 3 8 11.
* BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0: BEOPEN COM LICENSE AGREEMENT FOR PYTHON 2 0.
* CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1: CNRI LICENSE AGREEMENT FOR PYTHON 1 6 1.
* CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2: CWI LICENSE AGREEMENT FOR PYTHON 0 9 0 THROUGH 1 2.
* ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON 3.8.11 DOCUMENTATION: ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON 3 8 11 DOCUMENTATION.

Licenses and Acknowledgements for Incorporated Software

* Mersenne Twister::
* Sockets: Sockets<2>.
* Asynchronous socket services::
* Cookie management::
* Execution tracing::
* UUencode and UUdecode functions::
* XML Remote Procedure Calls::
* test_epoll::
* Select kqueue::
* SipHash24::
* strtod and dtoa::
* OpenSSL::
* expat::
* libffi::
* zlib: zlib<3>.
* cfuhash::
* libmpdec::
* W3C C14N test suite::

發布 Python 模組（舊版）

* An Introduction to Distutils::
* Writing the Setup Script::
* Writing the Setup Configuration File::
* Creating a Source Distribution::
* Creating Built Distributions::
* Distutils Examples::
* Extending Distutils::
* 指令參照::
* API參照::

An Introduction to Distutils

* Concepts & Terminology::
* A Simple Example: A Simple Example<2>.
* General Python terminology::
* Distutils-specific terminology::

Writing the Setup Script

* Listing whole packages::
* Listing individual modules::
* Describing extension modules::
* Relationships between Distributions and Packages::
* Installing Scripts::
* Installing Package Data::
* Installing Additional Files::
* Additional meta-data::
* Debugging the setup script::

Describing extension modules

* Extension names and packages::
* Extension source files::
* Preprocessor options::
* Library options::
* Other options::

Creating a Source Distribution

* Specifying the files to distribute::
* Manifest-related options::

Creating Built Distributions

* Creating RPM packages::
* Creating Windows Installers::
* Cross-compiling on Windows::
* Vista User Access Control (UAC): Vista User Access Control UAC.

Cross-compiling on Windows

* The Postinstallation script::

Distutils Examples

* Pure Python distribution (by module): Pure Python distribution by module.
* Pure Python distribution (by package): Pure Python distribution by package.
* Single extension module::
* Checking a package::
* Reading the metadata::

Extending Distutils

* Integrating new commands::
* Adding new distribution types::

指令參照

* Installing modules; the install command family: Installing modules the install command family.
* Creating a source distribution; the sdist command: Creating a source distribution the sdist command.

Installing modules: the install command family

* install_data::
* install_scripts::

API參照

* distutils.core: distutils core --- Core Distutils functionality. Core Distutils functionality
* distutils.ccompiler: distutils ccompiler --- CCompiler base class. CCompiler base class
* distutils.unixccompiler: distutils unixccompiler --- Unix C Compiler. Unix C Compiler
* distutils.msvccompiler: distutils msvccompiler --- Microsoft Compiler. Microsoft Compiler
* distutils.bcppcompiler: distutils bcppcompiler --- Borland Compiler. Borland Compiler
* distutils.cygwincompiler: distutils cygwincompiler --- Cygwin Compiler. Cygwin Compiler
* distutils.archive_util: distutils archive_util --- Archiving utilities. Archiving utilities
* distutils.dep_util: distutils dep_util --- Dependency checking. Dependency checking
* distutils.dir_util: distutils dir_util --- Directory tree operations. Directory tree operations
* distutils.file_util: distutils file_util --- Single file operations. Single file operations
* distutils.util: distutils util --- Miscellaneous other utility functions. Miscellaneous other utility functions
* distutils.dist: distutils dist --- The Distribution class. The Distribution class
* distutils.extension: distutils extension --- The Extension class. The Extension class
* distutils.debug: distutils debug --- Distutils debug mode. Distutils debug mode
* distutils.errors: distutils errors --- Distutils exceptions. Distutils exceptions
* distutils.fancy_getopt: distutils fancy_getopt --- Wrapper around the standard getopt module. Wrapper around the standard getopt module
* distutils.filelist: distutils filelist --- The FileList class. The FileList class
* distutils.log: distutils log --- Simple PEP 282-style logging. Simple PEP 282-style logging
* distutils.spawn: distutils spawn --- Spawn a sub-process. Spawn a sub-process
* distutils.sysconfig: distutils sysconfig --- System configuration information. System configuration information
* distutils.text_file: distutils text_file --- The TextFile class. The TextFile class
* distutils.version: distutils version --- Version number classes. Version number classes
* distutils.cmd: distutils cmd --- Abstract base class for Distutils commands. Abstract base class for Distutils commands
* Creating a new Distutils command::
* distutils.command: distutils command --- Individual Distutils commands. Individual Distutils commands
* distutils.command.bdist: distutils command bdist --- Build a binary installer. Build a binary installer
* distutils.command.bdist_packager: distutils command bdist_packager --- Abstract base class for packagers. Abstract base class for packagers
* distutils.command.bdist_dumb: distutils command bdist_dumb --- Build a "dumb" installer. Build a "dumb" installer
* distutils.command.bdist_msi: distutils command bdist_msi --- Build a Microsoft Installer binary package. Build a Microsoft Installer binary package
* distutils.command.bdist_rpm: distutils command bdist_rpm --- Build a binary distribution as a Redhat RPM and SRPM. Build a binary distribution as a Redhat RPM and
                               SRPM
* distutils.command.bdist_wininst: distutils command bdist_wininst --- Build a Windows installer. Build a Windows installer
* distutils.command.sdist: distutils command sdist --- Build a source distribution. Build a source distribution
* distutils.command.build: distutils command build --- Build all files of a package. Build all files of a package
* distutils.command.build_clib: distutils command build_clib --- Build any C libraries in a package. Build any C libraries in a package
* distutils.command.build_ext: distutils command build_ext --- Build any extensions in a package. Build any extensions in a package
* distutils.command.build_py: distutils command build_py --- Build the py/ pyc files of a package. Build the .py/.pyc files of a package
* distutils.command.build_scripts: distutils command build_scripts --- Build the scripts of a package. Build the scripts of a package
* distutils.command.clean: distutils command clean --- Clean a package build area. Clean a package build area
* distutils.command.config: distutils command config --- Perform package configuration. Perform package configuration
* distutils.command.install: distutils command install --- Install a package. Install a package
* distutils.command.install_data: distutils command install_data --- Install data files from a package. Install data files from a package
* distutils.command.install_headers: distutils command install_headers --- Install C/C++ header files from a package. Install C/C++ header files from a package
* distutils.command.install_lib: distutils command install_lib --- Install library files from a package. Install library files from a package
* distutils.command.install_scripts: distutils command install_scripts --- Install script files from a package. Install script files from a package
* distutils.command.register: distutils command register --- Register a module with the Python Package Index. Register a module with the Python Package Index
* distutils.command.check: distutils command check --- Check the meta-data of a package. Check the meta-data of a package

安裝 Python 模組（舊版）

* 簡介: 簡介<16>.
* Standard Build and Install::
* Alternate Installation::
* Custom Installation::
* Distutils Configuration Files::
* Building Extensions; Tips and Tricks: Building Extensions Tips and Tricks.

簡介

* Distutils based source distributions::

Standard Build and Install

* Platform variations::
* Splitting the job up::
* How building works::
* How installation works::

Alternate Installation

* Alternate installation; the user scheme: Alternate installation the user scheme.
* Alternate installation; the home scheme: Alternate installation the home scheme.
* Alternate installation; Unix (the prefix scheme): Alternate installation Unix the prefix scheme.
* Alternate installation; Windows (the prefix scheme): Alternate installation Windows the prefix scheme.

Custom Installation

* Modifying Python's Search Path::

Distutils Configuration Files

* Location and names of config files::
* Syntax of config files::

Building Extensions: Tips and Tricks

* Tweaking compiler/linker flags::
* Using non-Microsoft compilers on Windows::

Using non-Microsoft compilers on Windows

* Borland/CodeGear C++::
* GNU C / Cygwin / MinGW::

GNU C / Cygwin / MinGW

* Older Versions of Python and MinGW::



File: python.info,  Node: Python 有什麼新功能？,  Next: Python 教學,  Prev: Top,  Up: Top

1 Python 有什麼新功能？
***********************

「Python 有什麼新功能」這系列的說明是讓使用者知道 Python 各個主要更新版
本之間的重大改變的地方。這些說明歸類為每位使用者「必讀」的等級，並希望每
位使用者在新版本釋出時立即了解其中版本差別。

* Menu:

* What’s New In Python 3.8: What's New In Python 3 8.
* What’s New In Python 3.7: What's New In Python 3 7.
* What’s New In Python 3.6: What's New In Python 3 6.
* Python 3.5 有什麼新功能: Python 3 5 有什麼新功能.
* What’s New In Python 3.4: What's New In Python 3 4.
* What’s New In Python 3.3: What's New In Python 3 3.
* What’s New In Python 3.2: What's New In Python 3 2.
* What’s New In Python 3.1: What's New In Python 3 1.
* What’s New In Python 3.0: What's New In Python 3 0.
* What’s New in Python 2.7: What's New in Python 2 7.
* What’s New in Python 2.6: What's New in Python 2 6.
* What’s New in Python 2.5: What's New in Python 2 5.
* What’s New in Python 2.4: What's New in Python 2 4.
* What’s New in Python 2.3: What's New in Python 2 3.
* What’s New in Python 2.2: What's New in Python 2 2.
* What’s New in Python 2.1: What's New in Python 2 1.
* What’s New in Python 2.0: What's New in Python 2 0.
* Changelog（更動日誌）::


File: python.info,  Node: What's New In Python 3 8,  Next: What's New In Python 3 7,  Up: Python 有什麼新功能？

1.1 What’s New In Python 3.8
============================


Editor: Raymond Hettinger

This article explains the new features in Python 3.8, compared to 3.7.
For full details, see the *note changelog: 14d.

Python 3.8 was released on October 14th, 2019.

* Menu:

* Summary: Summary -- Release highlights. Release highlights
* New Features::
* Other Language Changes::
* New Modules::
* Improved Modules::
* Optimizations::
* Build and C API Changes::
* Deprecated::
* API and Feature Removals::
* Porting to Python 3.8: Porting to Python 3 8.
* Notable changes in Python 3.8.1: Notable changes in Python 3 8 1.
* Notable changes in Python 3.8.2: Notable changes in Python 3 8 2.
* Notable changes in Python 3.8.3: Notable changes in Python 3 8 3.
* Notable changes in Python 3.8.8: Notable changes in Python 3 8 8.
* Notable changes in Python 3.8.9: Notable changes in Python 3 8 9.
* Notable changes in Python 3.8.10: Notable changes in Python 3 8 10.
* Notable changes in Python 3.8.10: Notable changes in Python 3 8 10<2>.


File: python.info,  Node: Summary -- Release highlights,  Next: New Features,  Up: What's New In Python 3 8

1.1.1 Summary – Release highlights
----------------------------------


File: python.info,  Node: New Features,  Next: Other Language Changes,  Prev: Summary -- Release highlights,  Up: What's New In Python 3 8

1.1.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.
* Vectorcall; a fast calling protocol for CPython: 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

1.1.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(): 151. 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.

See PEP 572(2) for a full description.

(Contributed by Emily Morehouse in bpo-35224(3).)

   ---------- Footnotes ----------

   (1) 
https://en.wikipedia.org/wiki/Walrus#/media/File:Pacific_Walrus_-_Bull_(8247646168).jpg

   (2) https://www.python.org/dev/peps/pep-0572

   (3) https://bugs.python.org/issue35224


File: python.info,  Node: Positional-only parameters,  Next: Parallel filesystem cache for compiled bytecode files,  Prev: Assignment expressions,  Up: New Features

1.1.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(): 153. 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(): 151.
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: f6. 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: 1e. module:

     class Counter(dict):

         def __init__(self, iterable=None, /, **kwds):
             # Note "iterable" is a possible keyword argument

See PEP 570(2) for a full description.

(Contributed by Pablo Galindo in bpo-36540(3).)

   ---------- Footnotes ----------

   (1) https://docs.python.org/3/howto/clinic.html

   (2) https://www.python.org/dev/peps/pep-0570

   (3) https://bugs.python.org/issue36540


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

1.1.2.3 Parallel filesystem cache for compiled bytecode files
.............................................................

The new *note PYTHONPYCACHEPREFIX: 155. setting (also available as *note
-X: 156. ‘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: 157.
(*note None: 158. indicates the default location in ‘__pycache__’
subdirectories).

(Contributed by Carl Meyer in bpo-33499(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33499


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

1.1.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 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:
15a. environment variable, can be set using the new ‘./configure
--with-trace-refs’ 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/issue36465

   (2) https://bugs.python.org/issue21536

   (3) https://bugs.python.org/issue36722

   (4) https://bugs.python.org/issue36721


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

1.1.2.5 f-strings support ‘=’ for self-documenting expressions and debugging
............................................................................

Added an ‘=’ specifier to *note f-string: 15c.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: 15d. 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

(Contributed by Eric V. Smith and Larry Hastings in bpo-36817(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36817


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

1.1.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.

See PEP 578(1) for full details.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0578


File: python.info,  Node: PEP 587 Python Initialization Configuration,  Next: Vectorcall a fast calling protocol for CPython,  Prev: PEP 578 Python Runtime Audit Hooks,  Up: New Features

1.1.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: 160.

   * *note PyPreConfig: 161.

   * *note PyStatus: 162.

   * *note PyWideStringList: 163.

New functions:

   * *note PyConfig_Clear(): 164.

   * *note PyConfig_InitIsolatedConfig(): 165.

   * *note PyConfig_InitPythonConfig(): 166.

   * *note PyConfig_Read(): 167.

   * *note PyConfig_SetArgv(): 168.

   * *note PyConfig_SetBytesArgv(): 169.

   * *note PyConfig_SetBytesString(): 16a.

   * *note PyConfig_SetString(): 16b.

   * *note PyPreConfig_InitIsolatedConfig(): 16c.

   * *note PyPreConfig_InitPythonConfig(): 16d.

   * *note PyStatus_Error(): 16e.

   * *note PyStatus_Exception(): 16f.

   * *note PyStatus_Exit(): 170.

   * *note PyStatus_IsError(): 171.

   * *note PyStatus_IsExit(): 172.

   * *note PyStatus_NoMemory(): 173.

   * *note PyStatus_Ok(): 174.

   * *note PyWideStringList_Append(): 175.

   * *note PyWideStringList_Insert(): 176.

   * *note Py_BytesMain(): 177.

   * *note Py_ExitStatusException(): 178.

   * *note Py_InitializeFromConfig(): 179.

   * *note Py_PreInitialize(): 17a.

   * *note Py_PreInitializeFromArgs(): 17b.

   * *note Py_PreInitializeFromBytesArgs(): 17c.

   * *note Py_RunMain(): 17d.

This PEP also adds ‘_PyRuntimeState.preconfig’ (*note PyPreConfig: 161.
type) and ‘PyInterpreterState.config’ (*note PyConfig: 160. 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: 17e. for the
documentation.

See PEP 587(2) for a full description.

(Contributed by Victor Stinner in bpo-36763(3).)

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0587

   (2) https://www.python.org/dev/peps/pep-0587

   (3) https://bugs.python.org/issue36763


File: python.info,  Node: 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

1.1.2.8 Vectorcall: a fast calling protocol for CPython
.......................................................

The "vectorcall" protocol is added to the Python/C API. It is meant to
formalize existing optimizations which were already done for various
classes.  Any extension type implementing a callable can use this
protocol.

This is currently provisional.  The aim is to make it fully public in
Python 3.9.

See PEP 590(1) for a full description.

(Contributed by Jeroen Demeyer and Mark Shannon in bpo-36974(2).)

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0590

   (2) https://bugs.python.org/issue36974


File: python.info,  Node: Pickle protocol 5 with out-of-band data buffers,  Prev: Vectorcall a fast calling protocol for CPython,  Up: New Features

1.1.2.9 Pickle protocol 5 with out-of-band data buffers
.......................................................

When *note pickle: cb. 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: cb. 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.

See PEP 574(2) for a full description.

(Contributed by Antoine Pitrou in bpo-36785(3).)

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3118

   (2) https://www.python.org/dev/peps/pep-0574

   (3) https://bugs.python.org/issue36785


File: python.info,  Node: Other Language Changes,  Next: New Modules,  Prev: New Features,  Up: What's New In Python 3 8

1.1.3 Other Language Changes
----------------------------

   * A *note continue: 182. statement was illegal in the *note finally:
     183. 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: 184, *note int: 185, and *note fractions.Fraction:
     186. types now have an *note as_integer_ratio(): 187. method like
     that found in *note float: 188. and *note decimal.Decimal: 189.
     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: 185, *note float: 188. and *note
     complex: 18a. will now use the *note __index__(): 18b. special
     method, if available and the corresponding method *note __int__():
     18c, *note __float__(): 18d. or *note __complex__(): 18e. is not
     available.  (Contributed by Serhiy Storchaka in bpo-20092(4).)

   * Added support of ‘\N{name}’ escapes in *note regular expressions:
     de.:

          >>> notice = 'Copyright © 2019'
          >>> copyright_year_pattern = re.compile(r'\N{copyright sign}\s*(\d{4})')
          >>> int(copyright_year_pattern.search(notice).group(1))
          2019

     (Contributed by Jonathan Eunice and Serhiy Storchaka in
     bpo-30688(5).)

   * Dict and dictviews are now iterable in reversed insertion order
     using *note reversed(): 18f.  (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: 190. and *note
     return: 191. 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 sally')
          ('SIMPSONS', 'homer', 'marge', 'bart', 'lisa', 'sally')

     (Contributed by David Cuthbert and Jordan Chapman in bpo-32117(8).)

   * When a comma is missed in code such as ‘[(10, 20) (30, 40)]’, the
     compiler displays a *note SyntaxWarning: 192. with a helpful
     suggestion.  This improves on just having a *note TypeError: 193.
     indicating that the first tuple was not callable.  (Contributed by
     Serhiy Storchaka in bpo-15248(9).)

   * Arithmetic operations between subclasses of *note datetime.date:
     194. or *note datetime.datetime: 195. and *note datetime.timedelta:
     196. 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: 196. arithmetic, such as *note astimezone():
     197.  (Contributed by Paul Ganssle in bpo-32417(10).)

   * When the Python interpreter is interrupted by Ctrl-C (SIGINT) and
     the resulting *note KeyboardInterrupt: 198. 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: 199. 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(): 19a.
     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'

     (Contributed by Victor Stinner in bpo-37032(12).)

   * For integers, the three-argument form of the *note pow(): 19b.
     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

     (Contributed by Mark Dickinson in 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'}

     (Contributed by Jörn Heissler in bpo-35224(16).)

   * The *note object.__reduce__(): 19c. 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 *note __setstate__(): 19d. method.
     (Contributed by Pierre Glaser and Olivier Grisel in bpo-35900(17).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32489

   (2) https://bugs.python.org/issue33073

   (3) https://bugs.python.org/issue37819

   (4) https://bugs.python.org/issue20092

   (5) https://bugs.python.org/issue30688

   (6) https://bugs.python.org/issue33462

   (7) https://bugs.python.org/issue34641

   (8) https://bugs.python.org/issue32117

   (9) https://bugs.python.org/issue15248

   (10) https://bugs.python.org/issue32417

   (11) https://bugs.python.org/issue1054041

   (12) https://bugs.python.org/issue37032

   (13) https://en.wikipedia.org/wiki/Modular_multiplicative_inverse

   (14) https://en.wikipedia.org/wiki/Diophantine_equation

   (15) https://bugs.python.org/issue36027

   (16) https://bugs.python.org/issue35224

   (17) https://bugs.python.org/issue35900


File: python.info,  Node: New Modules,  Next: Improved Modules,  Prev: Other Language Changes,  Up: What's New In Python 3 8

1.1.4 New Modules
-----------------

   * The new *note importlib.metadata: 9e. 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')]

     (Contributed by Barry Warsaw and Jason R. Coombs in bpo-34632(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue34632


File: python.info,  Node: Improved Modules,  Next: Optimizations,  Prev: New Modules,  Up: What's New In Python 3 8

1.1.5 Improved Modules
----------------------

* Menu:

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


File: python.info,  Node: ast,  Next: asyncio,  Up: Improved Modules

1.1.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(): 1a1. returns the source
code for a specific AST node.

(Contributed by Ivan Levkivskyi in bpo-33416(1).)

The *note ast.parse(): 1a2. 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: 1a3. and *note await: 1a4. as non-reserved words.

(Contributed by Guido van Rossum in bpo-35766(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33416

   (2) https://www.python.org/dev/peps/pep-0484

   (3) https://www.python.org/dev/peps/pep-0526

   (4) https://www.python.org/dev/peps/pep-0484

   (5) https://bugs.python.org/issue35766


File: python.info,  Node: asyncio,  Next: builtins,  Prev: ast,  Up: Improved Modules

1.1.5.2 asyncio
...............

*note asyncio.run(): 1a6. has graduated from the provisional to stable
API. This function can be used to execute a *note coroutine: 1a7. 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())

This is `roughly' equivalent to:

     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(): 1a6. should be the preferred way of running asyncio
programs.

(Contributed by Yury Selivanov in 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: 1a4.
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

(Contributed by Yury Selivanov in bpo-37028(2).)

The exception *note asyncio.CancelledError: 1a8. now inherits from *note
BaseException: 1a9. rather than *note Exception: 1aa. and no longer
inherits from *note concurrent.futures.CancelledError: 1ab.
(Contributed by Yury Selivanov in bpo-32528(3).)

On Windows, the default event loop is now *note ProactorEventLoop: 1ac.
(Contributed by Victor Stinner in bpo-34687(4).)

*note ProactorEventLoop: 1ac. now also supports UDP. (Contributed by
Adam Meily and Andrew Svetlov in bpo-29883(5).)

*note ProactorEventLoop: 1ac. can now be interrupted by *note
KeyboardInterrupt: 198. ("CTRL+C"). (Contributed by Vladimir Matveev in
bpo-23057(6).)

Added *note asyncio.Task.get_coro(): 1ad. for getting the wrapped
coroutine within an *note asyncio.Task: 1ae.  (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(): 1af. or the *note
create_task(): 1b0. event loop method, or by calling the *note
set_name(): 1b1. method on the task object.  The task name is visible in
the ‘repr()’ output of *note asyncio.Task: 1ae. and can also be
retrieved using the *note get_name(): 1b2. method.  (Contributed by Alex
Grönholm in bpo-34270(8).)

Added support for Happy Eyeballs(9) to *note
asyncio.loop.create_connection(): 1b3.  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/issue32314

   (2) https://bugs.python.org/issue37028

   (3) https://bugs.python.org/issue32528

   (4) https://bugs.python.org/issue34687

   (5) https://bugs.python.org/issue29883

   (6) https://bugs.python.org/issue23057

   (7) https://bugs.python.org/issue36999

   (8) https://bugs.python.org/issue34270

   (9) https://en.wikipedia.org/wiki/Happy_Eyeballs

   (10) https://bugs.python.org/issue33530


File: python.info,  Node: builtins,  Next: collections,  Prev: asyncio,  Up: Improved Modules

1.1.5.3 builtins
................

The *note compile(): 1b5. built-in has been improved to accept the
‘ast.PyCF_ALLOW_TOP_LEVEL_AWAIT’ flag.  With this new flag passed, *note
compile(): 1b5. 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/issue34616


File: python.info,  Node: collections,  Next: cProfile,  Prev: builtins,  Up: Improved Modules

1.1.5.4 collections
...................

The *note _asdict(): 1b7. method for *note collections.namedtuple():
1b8. now returns a *note dict: 1b9. instead of a *note
collections.OrderedDict: 1ba.  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/issue35864


File: python.info,  Node: cProfile,  Next: csv,  Prev: collections,  Up: Improved Modules

1.1.5.5 cProfile
................

The *note cProfile.Profile: 1bc. 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
           ...

(Contributed by Scott Sanderson in bpo-29235(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue29235


File: python.info,  Node: csv,  Next: curses,  Prev: cProfile,  Up: Improved Modules

1.1.5.6 csv
...........

The *note csv.DictReader: 1be. now returns instances of *note dict: 1b9.
instead of a *note collections.OrderedDict: 1ba.  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/issue34003


File: python.info,  Node: curses,  Next: ctypes,  Prev: csv,  Up: Improved Modules

1.1.5.7 curses
..............

Added a new variable holding structured version information for the
underlying ncurses library: *note ncurses_version: 1c0.  (Contributed by
Serhiy Storchaka in bpo-31680(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31680


File: python.info,  Node: ctypes,  Next: datetime,  Prev: curses,  Up: Improved Modules

1.1.5.8 ctypes
..............

On Windows, *note CDLL: 1c2. 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(): 1c3.  (Contributed by Steve Dower in bpo-36085(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36085


File: python.info,  Node: datetime,  Next: functools,  Prev: ctypes,  Up: Improved Modules

1.1.5.9 datetime
................

Added new alternate constructors *note datetime.date.fromisocalendar():
1c5. and *note datetime.datetime.fromisocalendar(): 1c6, which construct
‘date’ and *note datetime: 31. 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/issue36004


File: python.info,  Node: functools,  Next: gc,  Prev: datetime,  Up: Improved Modules

1.1.5.10 functools
..................

*note functools.lru_cache(): 1c8. 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):
         ...

(Contributed by Raymond Hettinger in bpo-36772(1).)

Added a new *note functools.cached_property(): 1c9. 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)

(Contributed by Carl Meyer in bpo-21145(2))

Added a new *note functools.singledispatchmethod(): 1ca. decorator that
converts methods into *note generic functions: 1cb. using *note single
dispatch: 1cc.:

     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]

(Contributed by Ethan Smith in bpo-32380(3))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36772

   (2) https://bugs.python.org/issue21145

   (3) https://bugs.python.org/issue32380


File: python.info,  Node: gc,  Next: gettext,  Prev: functools,  Up: Improved Modules

1.1.5.11 gc
...........

*note get_objects(): 1ce. 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/issue36016


File: python.info,  Node: gettext,  Next: gzip,  Prev: gc,  Up: Improved Modules

1.1.5.12 gettext
................

Added *note pgettext(): 1d0. and its variants.  (Contributed by Franz
Glasner, Éric Araujo, and Cheryl Sabella in bpo-2504(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue2504


File: python.info,  Node: gzip,  Next: IDLE and idlelib,  Prev: gettext,  Up: Improved Modules

1.1.5.13 gzip
.............

Added the `mtime' parameter to *note gzip.compress(): 1d2. for
reproducible output.  (Contributed by Guo Ci Teo in bpo-34898(1).)

A *note BadGzipFile: 1d3. exception is now raised instead of *note
OSError: 1d4. 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/issue34898

   (2) https://bugs.python.org/issue6584


File: python.info,  Node: IDLE and idlelib,  Next: inspect,  Prev: gzip,  Up: Improved Modules

1.1.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/issue1529353

   (2) https://bugs.python.org/issue5680

   (3) https://bugs.python.org/issue37627

   (4) https://bugs.python.org/issue17535

   (5) https://bugs.python.org/issue13153

   (6) https://bugs.python.org/issue4603

   (7) https://bugs.python.org/issue38944

   (8) https://bugs.python.org/issue37765


File: python.info,  Node: inspect,  Next: io,  Prev: IDLE and idlelib,  Up: Improved Modules

1.1.5.15 inspect
................

The *note inspect.getdoc(): 1d7. function can now find docstrings for
‘__slots__’ if that attribute is a *note dict: 1b9. where the values are
docstrings.  This provides documentation options similar to what we
already have for *note property(): 1d8, *note classmethod(): 1d9, and
*note staticmethod(): 1da.:

     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)

(Contributed by Raymond Hettinger in bpo-36326(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36326


File: python.info,  Node: io,  Next: itertools,  Prev: inspect,  Up: Improved Modules

1.1.5.16 io
...........

In development mode (*note -X: 156. ‘env’) and in debug build, the *note
io.IOBase: 1dc. 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/issue18748


File: python.info,  Node: itertools,  Next: json tool,  Prev: io,  Up: Improved Modules

1.1.5.17 itertools
..................

The *note itertools.accumulate(): 1de. 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]

(Contributed by Lisa Roach in bpo-34659(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue34659


File: python.info,  Node: json tool,  Next: logging,  Prev: itertools,  Up: Improved Modules

1.1.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/issue31553


File: python.info,  Node: logging,  Next: math,  Prev: json tool,  Up: Improved Modules

1.1.5.19 logging
................

Added a `force' keyword argument to *note logging.basicConfig(): 1e1.
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 Dong-hee Na, and
reviewed by Vinay Sajip in bpo-33897(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33897


File: python.info,  Node: math,  Next: mmap,  Prev: logging,  Up: Improved Modules

1.1.5.20 math
.............

Added new function *note math.dist(): 1e3. for computing Euclidean
distance between two points.  (Contributed by Raymond Hettinger in
bpo-33089(1).)

Expanded the *note math.hypot(): 1e4. 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(): 1e5, as analogous function to
*note sum(): 1e6. 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

(Contributed by Pablo Galindo in bpo-35606(3).)

Added two new combinatoric functions *note math.perm(): 1e7. and *note
math.comb(): 1e8.:

     >>> 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

(Contributed by Yash Aggarwal, Keller Fuchs, Serhiy Storchaka, and
Raymond Hettinger in bpo-37128(4), bpo-37178(5), and bpo-35431(6).)

Added a new function *note math.isqrt(): 1e9. 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(): 1ea.:

     >>> r = 650320427
     >>> s = r ** 2
     >>> isqrt(s - 1)         # correct
     650320426
     >>> floor(sqrt(s - 1))   # incorrect
     650320427

(Contributed by Mark Dickinson in bpo-36887(7).)

The function *note math.factorial(): 1eb. no longer accepts arguments
that are not int-like.  (Contributed by Pablo Galindo in bpo-33083(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33089

   (2) https://bugs.python.org/issue33089

   (3) https://bugs.python.org/issue35606

   (4) https://bugs.python.org/issue37128

   (5) https://bugs.python.org/issue37178

   (6) https://bugs.python.org/issue35431

   (7) https://bugs.python.org/issue36887

   (8) https://bugs.python.org/issue33083


File: python.info,  Node: mmap,  Next: multiprocessing,  Prev: math,  Up: Improved Modules

1.1.5.21 mmap
.............

The *note mmap.mmap: 1ed. class now has an *note madvise(): 1ee. method
to access the ‘madvise()’ system call.  (Contributed by Zackery Spytz in
bpo-32941(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32941


File: python.info,  Node: multiprocessing,  Next: os,  Prev: mmap,  Up: Improved Modules

1.1.5.22 multiprocessing
........................

Added new *note multiprocessing.shared_memory: bd. 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/issue35813

   (2) https://bugs.python.org/issue33725


File: python.info,  Node: os,  Next: os path,  Prev: multiprocessing,  Up: Improved Modules

1.1.5.23 os
...........

Added new function *note add_dll_directory(): 1c3. on Windows for
providing additional search paths for native dependencies when importing
extension modules or loading DLLs using *note ctypes: 2b.  (Contributed
by Steve Dower in bpo-36085(1).)

A new *note os.memfd_create(): 1f1. 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(): 1f2. will now traverse
anything supported by the operating system, while *note os.lstat(): 1f3.
will only open reparse points that identify as "name surrogates" while
others are opened as for *note os.stat(): 1f2.  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(): 1f4. is now able to read directory
junctions.  Note that *note islink(): 1f5. 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(): 1f4. may now treat junctions as links.

(Contributed by Steve Dower in bpo-37834(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36085

   (2) https://bugs.python.org/issue26836

   (3) https://bugs.python.org/issue37834


File: python.info,  Node: os path,  Next: pathlib,  Prev: os,  Up: Improved Modules

1.1.5.24 os.path
................

*note os.path: c6. functions that return a boolean result like *note
exists(): 1f7, *note lexists(): 1f8, *note isdir(): 1f9, *note isfile():
1fa, *note islink(): 1f5, and *note ismount(): 1fb. now return ‘False’
instead of raising *note ValueError: 1fc. or its subclasses *note
UnicodeEncodeError: 1fd. and *note UnicodeDecodeError: 1fe. for paths
that contain characters or bytes unrepresentable at the OS level.
(Contributed by Serhiy Storchaka in bpo-33721(1).)

*note expanduser(): 1ff. 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(): 1f9. on Windows no longer returns ‘True’ for a link to a
non-existent directory.

*note realpath(): 200. on Windows now resolves reparse points, including
symlinks and directory junctions.

(Contributed by Steve Dower in bpo-37834(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33721

   (2) https://bugs.python.org/issue36264

   (3) https://bugs.python.org/issue37834


File: python.info,  Node: pathlib,  Next: pickle,  Prev: os path,  Up: Improved Modules

1.1.5.25 pathlib
................

*note pathlib.Path: 202. methods that return a boolean result like *note
exists(): 203, *note is_dir(): 204, *note is_file(): 205, *note
is_mount(): 206, *note is_symlink(): 207, *note is_block_device(): 208,
*note is_char_device(): 209, *note is_fifo(): 20a, *note is_socket():
20b. now return ‘False’ instead of raising *note ValueError: 1fc. or its
subclass *note UnicodeEncodeError: 1fd. for paths that contain
characters unrepresentable at the OS level.  (Contributed by Serhiy
Storchaka in bpo-33721(1).)

Added *note pathlib.Path.link_to(): 20c. which creates a hard link
pointing to a path.  (Contributed by Joannah Nanjekye in bpo-26978(2))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33721

   (2) https://bugs.python.org/issue26978


File: python.info,  Node: pickle,  Next: plistlib,  Prev: pathlib,  Up: Improved Modules

1.1.5.26 pickle
...............

*note pickle: cb. extensions subclassing the C-optimized *note Pickler:
20e. can now override the pickling logic of functions and classes by
defining the special *note reducer_override(): 20f. method.
(Contributed by Pierre Glaser and Olivier Grisel in bpo-35900(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35900


File: python.info,  Node: plistlib,  Next: pprint,  Prev: pickle,  Up: Improved Modules

1.1.5.27 plistlib
.................

Added new *note plistlib.UID: 211. 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/issue26707


File: python.info,  Node: pprint,  Next: py_compile,  Prev: plistlib,  Up: Improved Modules

1.1.5.28 pprint
...............

The *note pprint: d3. 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():
213. that is like *note pprint.pprint(): 214. 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'}

(Contributed by Rémi Lapeyre in bpo-30670(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue30670


File: python.info,  Node: py_compile,  Next: shlex,  Prev: pprint,  Up: Improved Modules

1.1.5.29 py_compile
...................

*note py_compile.compile(): 216. now supports silent mode.  (Contributed
by Joannah Nanjekye in bpo-22640(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22640


File: python.info,  Node: shlex,  Next: shutil,  Prev: py_compile,  Up: Improved Modules

1.1.5.30 shlex
..............

The new *note shlex.join(): 218. function acts as the inverse of *note
shlex.split(): 219.  (Contributed by Bo Bayles in bpo-32102(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32102


File: python.info,  Node: shutil,  Next: socket,  Prev: shlex,  Up: Improved Modules

1.1.5.31 shutil
...............

*note shutil.copytree(): 21b. now accepts a new ‘dirs_exist_ok’ keyword
argument.  (Contributed by Josh Bronson in bpo-20849(1).)

*note shutil.make_archive(): 21c. 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: 102. module.  (Contributed by C.A.M. Gerlach in
bpo-30661(2).)

*note shutil.rmtree(): 21d. 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/issue20849

   (2) https://bugs.python.org/issue30661

   (3) https://bugs.python.org/issue37834


File: python.info,  Node: socket,  Next: ssl,  Prev: shutil,  Up: Improved Modules

1.1.5.32 socket
...............

Added *note create_server(): 21f. and *note has_dualstack_ipv6(): 220.
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(): 221, *note socket.if_nametoindex():
222, and *note socket.if_indextoname(): 223. functions have been
implemented on Windows.  (Contributed by Zackery Spytz in bpo-37007(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17561

   (2) https://bugs.python.org/issue37007


File: python.info,  Node: ssl,  Next: statistics,  Prev: socket,  Up: Improved Modules

1.1.5.33 ssl
............

Added *note post_handshake_auth: 225. to enable and *note
verify_client_post_handshake(): 226. to initiate TLS 1.3 post-handshake
authentication.  (Contributed by Christian Heimes in bpo-34670(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue34670


File: python.info,  Node: statistics,  Next: sys,  Prev: ssl,  Up: Improved Modules

1.1.5.34 statistics
...................

Added *note statistics.fmean(): 228. as a faster, floating point variant
of *note statistics.mean(): 19a.  (Contributed by Raymond Hettinger and
Steven D’Aprano in bpo-35904(1).)

Added *note statistics.geometric_mean(): 229. (Contributed by Raymond
Hettinger in bpo-27181(2).)

Added *note statistics.multimode(): 22a. that returns a list of the most
common values.  (Contributed by Raymond Hettinger in bpo-35892(3).)

Added *note statistics.quantiles(): 22b. 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: 22c, 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/issue35904

   (2) https://bugs.python.org/issue27181

   (3) https://bugs.python.org/issue35892

   (4) https://bugs.python.org/issue36546

   (5) https://bugs.python.org/issue36018


File: python.info,  Node: sys,  Next: tarfile,  Prev: statistics,  Up: Improved Modules

1.1.5.35 sys
............

Add new *note sys.unraisablehook(): 22e. 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(): 22f.).  (Contributed by Victor
Stinner in bpo-36829(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36829


File: python.info,  Node: tarfile,  Next: threading,  Prev: sys,  Up: Improved Modules

1.1.5.36 tarfile
................

The *note tarfile: 102. 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/issue36268


File: python.info,  Node: threading,  Next: tokenize,  Prev: tarfile,  Up: Improved Modules

1.1.5.37 threading
..................

Add a new *note threading.excepthook(): 232. function which handles
uncaught *note threading.Thread.run(): 233. exception.  It can be
overridden to control how uncaught *note threading.Thread.run(): 233.
exceptions are handled.  (Contributed by Victor Stinner in
bpo-1230540(1).)

Add a new *note threading.get_native_id(): 234. function and a *note
native_id: 235. attribute to the *note threading.Thread: 236. 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: 234. for more information.
(Contributed by Jake Tesler in bpo-36084(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue1230540

   (2) https://bugs.python.org/issue36084


File: python.info,  Node: tokenize,  Next: tkinter,  Prev: threading,  Up: Improved Modules

1.1.5.38 tokenize
.................

The *note tokenize: 112. 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/issue33899


File: python.info,  Node: tkinter,  Next: time,  Prev: tokenize,  Up: Improved Modules

1.1.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/issue34829

   (2) https://bugs.python.org/issue23831

   (3) https://bugs.python.org/issue25451


File: python.info,  Node: time,  Next: typing,  Prev: tkinter,  Up: Improved Modules

1.1.5.40 time
.............

Added new clock *note CLOCK_UPTIME_RAW: 23a. for macOS 10.12.
(Contributed by Joannah Nanjekye in bpo-35702(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35702


File: python.info,  Node: typing,  Next: unicodedata,  Prev: time,  Up: Improved Modules

1.1.5.41 typing
...............

The *note typing: 11a. module incorporates several new features:

   * A dictionary type with per-key types.  See PEP 589(1) and *note
     typing.TypedDict: 23c.  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: 23d.
     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: 23e. and *note typing.final(): 23f.  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: 240.
     and *note typing.runtime_checkable(): 241.  Simple ABCs like *note
     typing.SupportsInt: 242. are now ‘Protocol’ subclasses.

   * New protocol class *note typing.SupportsIndex: 243.

   * New functions *note typing.get_origin(): 244. and *note
     typing.get_args(): 245.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0589

   (2) https://www.python.org/dev/peps/pep-0586

   (3) https://www.python.org/dev/peps/pep-0591

   (4) https://www.python.org/dev/peps/pep-0544


File: python.info,  Node: unicodedata,  Next: unittest,  Prev: typing,  Up: Improved Modules

1.1.5.42 unicodedata
....................

The *note unicodedata: 11b. module has been upgraded to use the Unicode
12.1.0(1) release.

New function *note is_normalized(): 247. 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) http://blog.unicode.org/2019/05/unicode-12-1-en.html

   (2) https://bugs.python.org/issue32285

   (3) https://bugs.python.org/issue37966


File: python.info,  Node: unittest,  Next: venv,  Prev: unicodedata,  Up: Improved Modules

1.1.5.43 unittest
.................

Added *note AsyncMock: 249. to support an asynchronous version of *note
Mock: 24a.  Appropriate new assert functions for testing have been added
as well.  (Contributed by Lisa Roach in bpo-26467(1)).

Added *note addModuleCleanup(): 24b. and *note addClassCleanup(): 24c.
to unittest to support cleanups for ‘setUpModule()’ and *note
setUpClass(): 24d.  (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: 11c. module gained support for coroutines to be used as
test cases with *note unittest.IsolatedAsyncioTestCase: 24e.
(Contributed by Andrew Svetlov in bpo-32972(4).)

Example:

     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/issue26467

   (2) https://bugs.python.org/issue24412

   (3) https://bugs.python.org/issue35047

   (4) https://bugs.python.org/issue32972


File: python.info,  Node: venv,  Next: weakref,  Prev: unittest,  Up: Improved Modules

1.1.5.44 venv
.............

*note venv: 126. 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/issue32718


File: python.info,  Node: weakref,  Next: xml,  Prev: venv,  Up: Improved Modules

1.1.5.45 weakref
................

The proxy objects returned by *note weakref.proxy(): 251. 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/issue36669


File: python.info,  Node: xml,  Next: xmlrpc,  Prev: weakref,  Up: Improved Modules

1.1.5.46 xml
............

As mitigation against DTD and external entity retrieval, the *note
xml.dom.minidom: 136. and *note xml.sax: 13c. 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: 138. 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: 138. 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: 253. can
receive namespace declaration events through the new callback methods
‘start_ns()’ and ‘end_ns()’.  Additionally, the *note
xml.etree.ElementTree.TreeBuilder: 254. 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/issue17239

   (2) https://bugs.python.org/issue28238

   (3) https://bugs.python.org/issue13611

   (4) https://bugs.python.org/issue36676

   (5) https://bugs.python.org/issue36673


File: python.info,  Node: xmlrpc,  Prev: xml,  Up: Improved Modules

1.1.5.47 xmlrpc
...............

*note xmlrpc.client.ServerProxy: 256. 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/issue35153


File: python.info,  Node: Optimizations,  Next: Build and C API Changes,  Prev: Improved Modules,  Up: What's New In Python 3 8

1.1.6 Optimizations
-------------------

   * The *note subprocess: fa. module can now use the *note
     os.posix_spawn(): 258. 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.

     (Contributed by Joannah Nanjekye and Victor Stinner in
     bpo-35537(1).)

   * *note shutil.copyfile(): 259, *note shutil.copy(): 25a, *note
     shutil.copy2(): 25b, *note shutil.copytree(): 21b. and *note
     shutil.move(): 25c. 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():
     259. uses a bigger default buffer size (1 MiB instead of 16 KiB)
     and a *note memoryview(): 25d.-based variant of *note
     shutil.copyfileobj(): 25e. 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:
     25f. section.  (Contributed by Giampaolo Rodolà in bpo-33671(2).)

   * *note shutil.copytree(): 21b. uses *note os.scandir(): 260.
     function and all copy functions depending from it use cached *note
     os.stat(): 1f2. 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(): 1f2.
     syscalls is reduced by 38% making *note shutil.copytree(): 21b.
     especially faster on network filesystems.  (Contributed by
     Giampaolo Rodolà in bpo-33695(3).)

   * The default protocol in the *note pickle: cb. 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 ‘Py_ssize_t’ 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: 261. 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(): 262. 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(): 1b8.  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: 263. 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/issue35537

   (2) https://bugs.python.org/issue33671

   (3) https://bugs.python.org/issue33695

   (4) https://bugs.python.org/issue33597

   (5) https://bugs.python.org/issue30977

   (6) https://bugs.python.org/issue35664

   (7) https://bugs.python.org/issue32492

   (8) https://bugs.python.org/issue33234

   (9) https://bugs.python.org/issue36012

   (10) https://bugs.python.org/issue23867

   (11) https://bugs.python.org/issue35582

   (12) https://bugs.python.org/issue36127

   (13) https://bugs.python.org/issue26219


File: python.info,  Node: Build and C API Changes,  Next: Deprecated,  Prev: Optimizations,  Up: What's New In Python 3 8

1.1.7 Build and C API Changes
-----------------------------

   * Default *note sys.abiflags: 265. 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’.

     (Contributed by Victor Stinner in bpo-35134(2) and bpo-35081(3),
     work initiated by Eric Snow in 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(): 266, *note Py_DECREF(): 267.

        * *note Py_XINCREF(): 268, *note Py_XDECREF(): 269.

        * ‘PyObject_INIT()’, ‘PyObject_INIT_VAR()’

        * Private functions: ‘_PyObject_GC_TRACK()’,
          ‘_PyObject_GC_UNTRACK()’, ‘_Py_Dealloc()’

     (Contributed by Victor Stinner in 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.

     (Contributed by Antoine Pitrou in bpo-32430(7).)

   * Functions that convert Python number to C integer like *note
     PyLong_AsLong(): 26a. and argument parsing functions like *note
     PyArg_ParseTuple(): 26b. with integer converting format units like
     ‘'i'’ will now use the *note __index__(): 18b. special method
     instead of *note __int__(): 18c, if available.  The deprecation
     warning will be emitted for objects with the ‘__int__()’ method but
     without the ‘__index__()’ method (like *note Decimal: 189. and
     *note Fraction: 186.).  *note PyNumber_Check(): 26c. will now
     return ‘1’ for objects implementing ‘__index__()’.  *note
     PyNumber_Long(): 26d, *note PyNumber_Float(): 26e. and *note
     PyFloat_AsDouble(): 26f. 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(): 270. (and its parallel macro
     ‘PyObject_INIT’) instead of in *note PyType_GenericAlloc(): 271.
     Types that modify instance allocation or deallocation may need to
     be adjusted.  (Contributed by Eddie Elizondo in bpo-35810(10).)

   * The new function *note PyCode_NewWithPosOnlyArgs(): 272. allows to
     create code objects like *note PyCode_New(): 273, but with an extra
     `posonlyargcount' parameter for indicating the number of
     positional-only arguments.  (Contributed by Pablo Galindo in
     bpo-37221(11).)

   * *note Py_SetPath(): 274. now sets *note sys.executable: 275. to the
     program full path (*note Py_GetProgramFullPath(): 276.) rather than
     to the program name (*note Py_GetProgramName(): 277.).
     (Contributed by Victor Stinner in bpo-38234(12).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36707

   (2) https://bugs.python.org/issue35134

   (3) https://bugs.python.org/issue35081

   (4) https://bugs.python.org/issue35059

   (5) https://bugs.python.org/issue35713

   (6) https://bugs.python.org/issue33818

   (7) https://bugs.python.org/issue32430

   (8) https://bugs.python.org/issue36048

   (9) https://bugs.python.org/issue20092

   (10) https://bugs.python.org/issue35810

   (11) https://bugs.python.org/issue37221

   (12) https://bugs.python.org/issue38234


File: python.info,  Node: Deprecated,  Next: API and Feature Removals,  Prev: Build and C API Changes,  Up: What's New In Python 3 8

1.1.8 Deprecated
----------------

   * 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: 138. module now emit a *note DeprecationWarning: 279.
     instead of *note PendingDeprecationWarning: 27a.  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: 27b. to *note
     loop.set_default_executor(): 27c. is deprecated and will be
     prohibited in Python 3.9.  (Contributed by Elvis Pranskevichus in
     bpo-34075(3).)

   * The *note __getitem__(): 27d. methods of *note
     xml.dom.pulldom.DOMEventStream: 27e, *note
     wsgiref.util.FileWrapper: 27f. and *note fileinput.FileInput: 280.
     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: 281. 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: 8. classes ‘Num’, ‘Str’, ‘Bytes’, ‘NameConstant’ and
     ‘Ellipsis’ are considered deprecated and will be removed in future
     Python versions.  ‘Constant’ should be used instead.  (Contributed
     by Serhiy Storchaka in bpo-32892(6).)

   * *note ast.NodeVisitor: 282. 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 ‘visit_Constant()’ method to handle all constant nodes.
     (Contributed by Serhiy Storchaka in bpo-36917(7).)

   * The *note asyncio.coroutine(): 283. *note decorator: 284. is
     deprecated and will be removed in version 3.10.  Instead of
     ‘@asyncio.coroutine’, use *note async def: 285. instead.
     (Contributed by Andrew Svetlov in bpo-36921(8).)

   * In *note asyncio: a, the explicit passing of a `loop' argument has
     been deprecated and will be removed in version 3.10 for the
     following: *note asyncio.sleep(): 286, *note asyncio.gather(): 287,
     *note asyncio.shield(): 288, *note asyncio.wait_for(): 289, *note
     asyncio.wait(): 28a, *note asyncio.as_completed(): 28b, *note
     asyncio.Task: 1ae, *note asyncio.Lock: 28c, *note asyncio.Event:
     28d, *note asyncio.Condition: 28e, *note asyncio.Semaphore: 28f,
     *note asyncio.BoundedSemaphore: 290, *note asyncio.Queue: 291,
     *note asyncio.create_subprocess_exec(): 292, and *note
     asyncio.create_subprocess_shell(): 293.

   * The explicit passing of coroutine objects to *note asyncio.wait():
     28a. 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: 89. module: *note lgettext(): 294, *note ldgettext(): 295,
     *note lngettext(): 296. and *note ldngettext(): 297.  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 *note bind_textdomain_codeset(): 298, methods *note
     output_charset(): 299. and *note set_output_charset(): 29a, and the
     `codeset' parameter of functions *note translation(): 29b. and
     *note install(): 29c. 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: 236. has been
     deprecated.  (Contributed by Dong-hee Na in bpo-35283(11).)

   * Many builtin and extension functions that take integer arguments
     will now emit a deprecation warning for *note Decimal: 189.s, *note
     Fraction: 186.s and any other objects that can be converted to
     integers only with a loss (e.g.  that have the *note __int__():
     18c. method but do not have the *note __index__(): 18b. 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(): 29d, *note
          weakref.finalize(): 29e, *note profile.Profile.runcall(): 29f,
          ‘cProfile.Profile.runcall()’, *note bdb.Bdb.runcall(): 2a0,
          *note trace.Trace.runfunc(): 2a1. and *note curses.wrapper():
          2a2.

        - `function' in *note unittest.TestCase.addCleanup(): 2a3.

        - `fn' in the *note submit(): 2a4. method of *note
          concurrent.futures.ThreadPoolExecutor: 27b. and *note
          concurrent.futures.ProcessPoolExecutor: 2a5.

        - `callback' in *note contextlib.ExitStack.callback(): 2a6,
          ‘contextlib.AsyncExitStack.callback()’ and *note
          contextlib.AsyncExitStack.push_async_callback(): 2a7.

        - `c' and `typeid' in the ‘create()’ method of
          ‘multiprocessing.managers.Server’ and
          ‘multiprocessing.managers.SharedMemoryServer’.

        - `obj' in *note weakref.finalize(): 29e.

     In future releases of Python, they will be *note positional-only:
     2a8.  (Contributed by Serhiy Storchaka in bpo-36492(13).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37481

   (2) https://bugs.python.org/issue29209

   (3) https://bugs.python.org/issue34075

   (4) https://bugs.python.org/issue9372

   (5) https://bugs.python.org/issue36320

   (6) https://bugs.python.org/issue32892

   (7) https://bugs.python.org/issue36917

   (8) https://bugs.python.org/issue36921

   (9) https://bugs.python.org/issue34790

   (10) https://bugs.python.org/issue33710

   (11) https://bugs.python.org/issue35283

   (12) https://bugs.python.org/issue36048

   (13) https://bugs.python.org/issue36492


File: python.info,  Node: API and Feature Removals,  Next: Porting to Python 3 8,  Prev: Deprecated,  Up: What's New In Python 3 8

1.1.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:
     1e. was deprecated, and importing should be done from *note
     collections.abc: 1f.  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(): 2aa. 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(): 2ab. or
     *note time.process_time(): 2ac. 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 *note
     cgi: 16. 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: 102. module.
     It is not documented and deprecated since Python 3.3.

   * The *note XMLParser: 253. 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: 2ad.  (Contributed
     by Serhiy Storchaka in bpo-29209(6).)

   * Removed the ‘doctype()’ method of *note XMLParser: 253.
     (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: f3.
     module are not exposed to the user.  (Contributed by Aviv Palivoda
     in bpo-30262(9).)

   * The ‘bufsize’ keyword argument of *note fileinput.input(): 2ae. and
     *note fileinput.FileInput(): 280. 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/issue36952

   (2) https://bugs.python.org/issue35471

   (3) https://bugs.python.org/issue35345

   (4) https://bugs.python.org/issue36895

   (5) https://bugs.python.org/issue25427

   (6) https://bugs.python.org/issue29209

   (7) https://bugs.python.org/issue29209

   (8) https://bugs.python.org/issue36297

   (9) https://bugs.python.org/issue30262

   (10) https://bugs.python.org/issue36952

   (11) https://bugs.python.org/issue36933


File: python.info,  Node: Porting to Python 3 8,  Next: Notable changes in Python 3 8 1,  Prev: API and Feature Removals,  Up: What's New In Python 3 8

1.1.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 C API::
* CPython bytecode changes::
* Demos and Tools::


File: python.info,  Node: Changes in Python behavior,  Next: Changes in the Python API,  Up: Porting to Python 3 8

1.1.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: 192. 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:
     184, *note int: 185, *note float: 188, *note complex: 18a. and few
     classes from the standard library.  They now inherit ‘__str__()’
     from *note object: 2b1.  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: 2b2. 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).)

   * *note PyEval_AcquireLock(): 2b3. and *note PyEval_AcquireThread():
     2b4. now terminate the current thread if called while the
     interpreter is finalizing, making them consistent with *note
     PyEval_RestoreThread(): 2b5, *note Py_END_ALLOW_THREADS(): 2b6, and
     *note PyGILState_Ensure(): 2b7.  If this behavior is not desired,
     guard the call by checking ‘_Py_IsFinalizing()’ or
     ‘sys.is_finalizing()’.  (Contributed by Joannah Nanjekye in
     bpo-36475(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10544

   (2) https://bugs.python.org/issue34850

   (3) https://bugs.python.org/issue35459

   (4) https://bugs.python.org/issue36793

   (5) https://bugs.python.org/issue36588

   (6) https://bugs.python.org/issue36475


File: python.info,  Node: Changes in the Python API,  Next: Changes in the C API,  Prev: Changes in Python behavior,  Up: Porting to Python 3 8

1.1.10.2 Changes in the Python API
..................................

   * The *note os.getcwdb(): 2b9. 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: 2ba. can now use *note os.posix_spawn():
     258. in some cases for better performance.  On Windows Subsystem
     for Linux and QEMU User Emulation, the ‘Popen’ constructor using
     *note os.posix_spawn(): 258. 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: 2ba. is no
     longer compatible with subinterpreters.  The use of the parameter
     in a subinterpreter now raises *note RuntimeError: 2bb.
     (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(): 2aa. instead.
     (Contributed by Victor Stinner in bpo-35345(7).)

   * The *note statistics.mode(): 2bc. 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(): 2bd. method of the *note
     tkinter.ttk.Treeview: 2be. 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():
     2bf. for changing the selection.  (Contributed by Serhiy Storchaka
     in bpo-31508(9).)

   * The ‘writexml()’, ‘toxml()’ and ‘toprettyxml()’ methods of *note
     xml.dom.minidom: 136, 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: 33. database opened with flags ‘'r'’ is now
     read-only.  *note dbm.dumb.open(): 2c0. 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:
     253. will no longer be called and will emit a *note RuntimeWarning:
     2c1. instead of a *note DeprecationWarning: 279.  Define the *note
     doctype(): 2c2. method on a target for handling an XML doctype
     declaration.  (Contributed by Serhiy Storchaka in bpo-29209(12).)

   * A *note RuntimeError: 2bb. is now raised when the custom metaclass
     doesn’t provide the ‘__classcell__’ entry in the namespace passed
     to ‘type.__new__’.  A *note DeprecationWarning: 279. 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(): 259, *note shutil.copy(): 25a, *note
     shutil.copy2(): 25b, *note shutil.copytree(): 21b. and *note
     shutil.move(): 25c. use platform-specific "fast-copy" syscalls (see
     *note Platform-dependent efficient copy operations: 25f. section).

   * *note shutil.copyfile(): 259. 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: 2c3. 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(): 2c4. 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: 136. and *note xml.sax: 13c. 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: 32. database (*note
     dbm.dumb: 33, *note dbm.gnu: 34. or *note dbm.ndbm: 35.) raises
     ‘error’ (*note dbm.dumb.error: 2c5, *note dbm.gnu.error: 2c6. or
     *note dbm.ndbm.error: 2c7.) instead of *note KeyError: 2c8.
     (Contributed by Xiang Zhang in bpo-33106(19).)

   * Simplified AST for literals.  All constants will be represented as
     ‘ast.Constant’ 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(): 1ff. 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: 1a8. now inherits from
     *note BaseException: 1a9. rather than *note Exception: 1aa. and no
     longer inherits from *note concurrent.futures.CancelledError: 1ab.
     (Contributed by Yury Selivanov in bpo-32528(22).)

   * The function *note asyncio.wait_for(): 289. now correctly waits for
     cancellation when using an instance of *note asyncio.Task: 1ae.
     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(): 2c9. 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: 2ca. has graduated to the stable
     API.

   * DLL dependencies for extension modules and DLLs loaded with *note
     ctypes: 2b. 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(): 1c3. 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(): 1c3. 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: 199. 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: 199. can be used to
     make the code future-proof.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0529

   (2) https://bugs.python.org/issue37412

   (3) https://bugs.python.org/issue35537

   (4) https://bugs.python.org/issue34651

   (5) https://bugs.python.org/issue37951

   (6) https://bugs.python.org/issue36348

   (7) https://bugs.python.org/issue35345

   (8) https://bugs.python.org/issue35892

   (9) https://bugs.python.org/issue31508

   (10) https://bugs.python.org/issue34160

   (11) https://bugs.python.org/issue32749

   (12) https://bugs.python.org/issue29209

   (13) https://bugs.python.org/issue23722

   (14) https://bugs.python.org/issue29235

   (15) https://bugs.python.org/issue33597

   (16) https://bugs.python.org/issue35886

   (17) https://bugs.python.org/issue2122

   (18) https://bugs.python.org/issue17239

   (19) https://bugs.python.org/issue33106

   (20) https://bugs.python.org/issue32892

   (21) https://bugs.python.org/issue36264

   (22) https://bugs.python.org/issue32528

   (23) https://bugs.python.org/issue32751

   (24) https://bugs.python.org/issue37027

   (25) https://bugs.python.org/issue36085

   (26) https://bugs.python.org/issue36623

   (27) https://www.python.org/dev/peps/pep-0570


File: python.info,  Node: Changes in the C API,  Next: CPython bytecode changes,  Prev: Changes in the Python API,  Up: Porting to Python 3 8

1.1.10.3 Changes in the C API
.............................

   * The *note PyCompilerFlags: 2cd. 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(): 2ce. 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(): 26b, *note Py_BuildValue(): 2cf, *note
     PyObject_CallFunction(): 2d0, etc.)  without ‘PY_SSIZE_T_CLEAN’
     defined raises ‘DeprecationWarning’ now.  It will be removed in
     3.10 or 4.0.  Read *note Parsing arguments and building values:
     2d1. for detail.  (Contributed by Inada Naoki in bpo-36381(4).)

   * Instances of heap-allocated types (such as those created with *note
     PyType_FromSpec(): 2d2.) hold a reference to their type object.
     Increasing the reference count of these type objects has been moved
     from *note PyType_GenericAlloc(): 271. to the more low-level
     functions, *note PyObject_Init(): 270. and ‘PyObject_INIT()’.  This
     makes types created through *note PyType_FromSpec(): 2d2. behave
     like other classes in managed code.

     Statically allocated types 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: 266. on the type object after
          allocating an instance - if any.  This may happen after
          calling *note PyObject_New(): 2d3, *note PyObject_NewVar():
          2d4, *note PyObject_GC_New(): 2d5, *note PyObject_GC_NewVar():
          2d6, or any other custom allocator that uses *note
          PyObject_Init(): 270. or ‘PyObject_INIT()’.

          Example:

               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.

          Example:

               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
               }

     (Contributed by Eddie Elizondo in bpo-35810(5).)

   * The ‘Py_DEPRECATED()’ macro has been implemented for MSVC. The
     macro now must be placed before the symbol name.

     Example:

          Py_DEPRECATED(3.8) PyAPI_FUNC(int) Py_OldFunction(void);

     (Contributed by Zackery Spytz in bpo-33407(6).)

   * The interpreter does not pretend to support binary compatibility of
     extension types across feature releases, anymore.  A *note
     PyTypeObject: 2d7. exported by a third-party extension module is
     supposed to have all the slots expected in the current Python
     version, including *note tp_finalize: 2d8. (*note
     Py_TPFLAGS_HAVE_FINALIZE: 2d9. is not checked anymore before
     reading *note tp_finalize: 2d8.).

     (Contributed by Antoine Pitrou in 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: 2da. 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.

     (Contributed by Steve Dower in bpo-37351(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35766

   (2) https://bugs.python.org/issue36728

   (3) https://bugs.python.org/issue21536

   (4) https://bugs.python.org/issue36381

   (5) https://bugs.python.org/issue35810

   (6) https://bugs.python.org/issue33407

   (7) https://bugs.python.org/issue32388

   (8) https://bugs.python.org/issue37351


File: python.info,  Node: CPython bytecode changes,  Next: Demos and Tools,  Prev: Changes in the C API,  Up: Porting to Python 3 8

1.1.10.4 CPython bytecode changes
.................................

   * 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: 2dc, *note
     continue: 182. and *note return: 191.

     Removed opcodes ‘BREAK_LOOP’, ‘CONTINUE_LOOP’, ‘SETUP_LOOP’ and
     ‘SETUP_EXCEPT’.  Added new opcodes *note ROT_FOUR: 2dd, *note
     BEGIN_FINALLY: 2de, *note CALL_FINALLY: 2df. and *note POP_FINALLY:
     2e0.  Changed the behavior of *note END_FINALLY: 2e1. and *note
     WITH_CLEANUP_START: 2e2.

     (Contributed by Mark Shannon, Antoine Pitrou and Serhiy Storchaka
     in bpo-17611(1).)

   * Added new opcode *note END_ASYNC_FOR: 2e3. for handling exceptions
     raised when awaiting a next item in an *note async for: 2e4. loop.
     (Contributed by Serhiy Storchaka in bpo-33041(2).)

   * The *note MAP_ADD: 2e5. 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/issue17611

   (2) https://bugs.python.org/issue33041

   (3) https://www.python.org/dev/peps/pep-0572

   (4) https://bugs.python.org/issue35224


File: python.info,  Node: Demos and Tools,  Prev: CPython bytecode changes,  Up: Porting to Python 3 8

1.1.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/issue35884

   (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/mac-osx/


File: python.info,  Node: Notable changes in Python 3 8 1,  Next: Notable changes in Python 3 8 2,  Prev: Porting to Python 3 8,  Up: What's New In Python 3 8

1.1.11 Notable changes in Python 3.8.1
--------------------------------------

Due to significant security concerns, the `reuse_address' parameter of
*note asyncio.loop.create_datagram_endpoint(): 2e8. 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/issue37228


File: python.info,  Node: Notable changes in Python 3 8 2,  Next: Notable changes in Python 3 8 3,  Prev: Notable changes in Python 3 8 1,  Up: What's New In Python 3 8

1.1.12 Notable changes in Python 3.8.2
--------------------------------------

Fixed a regression with the ‘ignore’ callback of *note
shutil.copytree(): 21b.  The argument types are now str and List[str]
again.  (Contributed by Manuel Barkhau and Giampaolo Rodola in
bpo-39390(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39390


File: python.info,  Node: Notable changes in Python 3 8 3,  Next: Notable changes in Python 3 8 8,  Prev: Notable changes in Python 3 8 2,  Up: What's New In Python 3 8

1.1.13 Notable changes in 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 bpo-39562(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39562


File: python.info,  Node: Notable changes in Python 3 8 8,  Next: Notable changes in Python 3 8 9,  Prev: Notable changes in Python 3 8 3,  Up: What's New In Python 3 8

1.1.14 Notable changes in Python 3.8.8
--------------------------------------

Earlier Python versions allowed using both ‘;’ and ‘&’ as query
parameter separators in *note urllib.parse.parse_qs(): 2ec. and *note
urllib.parse.parse_qsl(): 2ed.  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
*note cgi.parse(): 2ee. and *note cgi.parse_multipart(): 2ef. 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/issue42967


File: python.info,  Node: Notable changes in Python 3 8 9,  Next: Notable changes in Python 3 8 10,  Prev: Notable changes in Python 3 8 8,  Up: What's New In Python 3 8

1.1.15 Notable changes in Python 3.8.9
--------------------------------------

A security fix alters the *note ftplib.FTP: 2f1. 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 bpo-43285(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43285


File: python.info,  Node: Notable changes in Python 3 8 10,  Next: Notable changes in Python 3 8 10<2>,  Prev: Notable changes in Python 3 8 9,  Up: What's New In Python 3 8

1.1.16 Notable changes in 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.


File: python.info,  Node: macOS 11 0 Big Sur and Apple Silicon Mac support,  Up: Notable changes in Python 3 8 10

1.1.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
bpo-41100(1), with fixes by FX Coudert and Eli Rykoff, and backported to
3.8 by Maxime Bélanger and Ned Deily)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41100


File: python.info,  Node: Notable changes in Python 3 8 10<2>,  Prev: Notable changes in Python 3 8 10,  Up: What's New In Python 3 8

1.1.17 Notable changes in Python 3.8.10
---------------------------------------

* Menu:

* urllib.parse: urllib parse.


File: python.info,  Node: urllib parse,  Up: Notable changes in Python 3 8 10<2>

1.1.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: 120.
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://tools.ietf.org/html/rfc3986.html

   (2) https://bugs.python.org/issue43882


File: python.info,  Node: What's New In Python 3 7,  Next: What's New In Python 3 6,  Prev: What's New In Python 3 8,  Up: Python 有什麼新功能？

1.2 What’s New In Python 3.7
============================


Editor: 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: 14d.

* Menu:

* Summary: Summary -- Release Highlights. Release Highlights
* New Features: New Features<2>.
* Other Language Changes: Other Language Changes<2>.
* New Modules: New Modules<2>.
* Improved Modules: Improved Modules<2>.
* C API Changes::
* Build Changes::
* Optimizations: Optimizations<2>.
* 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.
* Notable changes in Python 3.7.1: Notable changes in Python 3 7 1.
* Notable changes in Python 3.7.2: Notable changes in Python 3 7 2.
* Notable changes in Python 3.7.6: Notable changes in Python 3 7 6.
* Notable changes in Python 3.7.10: Notable changes in Python 3 7 10.


File: python.info,  Node: Summary -- Release Highlights,  Next: New Features<2>,  Up: What's New In Python 3 7

1.2.1 Summary – Release Highlights
----------------------------------

New syntax features:

   * *note PEP 563: 2f9, postponed evaluation of type annotations.

Backwards incompatible syntax changes:

   * *note async: 1a3. and *note await: 1a4. are now reserved keywords.

New library modules:

   * *note contextvars: 25.: *note PEP 567 – Context Variables: 2fa.

   * *note dataclasses: 30.: *note PEP 557 – Data Classes: 2fb.

   * *note importlib.resources: 2fc.

New built-in features:

   * *note PEP 553: 2fd, the new *note breakpoint(): 2fe. function.

Python data model improvements:

   * *note PEP 562: 2ff, customization of access to module attributes.

   * *note PEP 560: 300, core support for typing module and generic
     types.

   * the insertion-order preservation nature of *note dict: 301. objects
     has been declared(1) to be an official part of the Python language
     spec.

Significant improvements in the standard library:

   * The *note asyncio: a. module has received new features, significant
     *note usability and performance improvements: 302.

   * The *note time: 10b. module gained support for *note functions with
     nanosecond resolution: 303.

CPython implementation improvements:

   * Avoiding the use of ASCII as a default text encoding:

        * *note PEP 538: 304, legacy C locale coercion

        * *note PEP 540: 305, forced UTF-8 runtime mode

   * *note PEP 552: 306, deterministic .pycs

   * *note the new development runtime mode: 307.

   * *note PEP 565: 308, improved *note DeprecationWarning: 279.
     handling

C API improvements:

   * *note PEP 539: 309, new C API for thread-local storage

Documentation improvements:

   * *note PEP 545: 30a, Python documentation translations

   * New documentation translations: Japanese(2), French(3), and
     Korean(4).

This release features notable performance improvements in many areas.
The *note Optimizations: 30b. 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: 30c. 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<2>,  Next: Other Language Changes<2>,  Prev: Summary -- Release Highlights,  Up: What's New In Python 3 7

1.2.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 Documentation Translations: PEP 545 Python Documentation Translations.
* Development Runtime Mode; -X dev: Development Runtime Mode -X dev.


File: python.info,  Node: PEP 563 Postponed Evaluation of Annotations,  Next: PEP 538 Legacy C Locale Coercion,  Up: New Features<2>

1.2.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(): 30f.  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://www.python.org/dev/peps/pep-3107

   (2) https://www.python.org/dev/peps/pep-0526

   (3) https://www.python.org/dev/peps/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<2>

1.2.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:
311. environment variable.  Automatically setting ‘LC_CTYPE’ this way
means that both the core interpreter and locale-aware C extensions (such
as *note readline: df.) 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: 312.
and *note stdout: 313. 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: 314. 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: 314.) 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: 305.

也參考
......

PEP 538(4) – Coercing the legacy C locale to a UTF-8 based locale

     PEP written and implemented by Nick Coghlan.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0538

   (2) https://www.python.org/dev/peps/pep-0011

   (3) https://www.python.org/dev/peps/pep-0538

   (4) https://www.python.org/dev/peps/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<2>

1.2.2.3 PEP 540: Forced UTF-8 Runtime Mode
..........................................

The new *note -X: 156. ‘utf8’ command line option and *note PYTHONUTF8:
316. environment variable can be used to enable the CPython `UTF-8
mode'.

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: 312.
and *note sys.stdout: 313. 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: 305.).

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

     PEP written and implemented by Victor Stinner

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0540

   (2) https://www.python.org/dev/peps/pep-0538

   (3) https://www.python.org/dev/peps/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<2>

1.2.2.4 PEP 553: Built-in ‘breakpoint()’
........................................

Python 3.7 includes the new built-in *note breakpoint(): 2fe. function
as an easy and consistent way to enter the Python debugger.

Built-in ‘breakpoint()’ calls *note sys.breakpointhook(): 318.  By
default, the latter imports *note pdb: ca. 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: 319. 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()

     PEP written and implemented by Barry Warsaw

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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<2>

1.2.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: 31b. 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: 31c. 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: 31d. 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 written by Erik M. Bray; implementation by Masayuki Yamamoto.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0539

   (2) https://www.python.org/dev/peps/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<2>

1.2.2.6 PEP 562: Customization of Access to Module Attributes
.............................................................

Python 3.7 allows defining *note __getattr__(): 31f. on modules and will
call it whenever a module attribute is otherwise not found.  Defining
*note __dir__(): 320. 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) – Module ‘__getattr__’ and ‘__dir__’

     PEP written and implemented by Ivan Levkivskyi

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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<2>

1.2.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():
322. 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: 10b. module:

   * *note time.clock_gettime_ns(): 323.

   * *note time.clock_settime_ns(): 324.

   * *note time.monotonic_ns(): 325.

   * *note time.perf_counter_ns(): 326.

   * *note time.process_time_ns(): 327.

   * *note time.time_ns(): 328.

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(): 328. is approximately 3 times better than that of *note
time.time(): 322.

也參考
......

PEP 564(3) – Add new time functions with nanosecond resolution

     PEP written and implemented by Victor Stinner

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0564

   (2) 
https://www.python.org/dev/peps/pep-0564/#annex-clocks-resolution-in-python

   (3) https://www.python.org/dev/peps/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<2>

1.2.2.8 PEP 565: Show DeprecationWarning in ‘__main__’
......................................................

The default handling of *note DeprecationWarning: 279. 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: 32a.: always displayed by default, recommended
     for warnings intended to be seen by application end users (e.g.
     for deprecated application configuration settings).

   * *note DeprecationWarning: 279.: 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: 27a.: displayed by default only
     when running tests, intended for cases where a future version
     upgrade will change the warning category to *note
     DeprecationWarning: 279. or *note FutureWarning: 32a.

Previously both *note DeprecationWarning: 279. and *note
PendingDeprecationWarning: 27a. 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__’

     PEP written and implemented by Nick Coghlan

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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<2>

1.2.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: 11a. module are extensively used by the community,
so this restriction is removed.  The PEP introduces two special methods
*note __class_getitem__(): 32c. and ‘__mro_entries__’, these methods are
now used by most classes and special constructs in *note typing: 11a.
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: 11a. module are fixed.

也參考
......

PEP 560(2) – Core support for typing module and generic types

     PEP written and implemented by Ivan Levkivskyi

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0484

   (2) https://www.python.org/dev/peps/pep-0560


File: python.info,  Node: PEP 552 Hash-based pyc Files,  Next: PEP 545 Python Documentation Translations,  Prev: PEP 560 Core Support for typing module and Generic Types,  Up: New Features<2>

1.2.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: d8. or *note compileall: 21.

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.

See *note Cached bytecode invalidation: 32e. for more information.

也參考
......

PEP 552(3) – Deterministic pycs

     PEP written and implemented by Benjamin Peterson

   ---------- Footnotes ----------

   (1) https://reproducible-builds.org/

   (2) https://www.python.org/dev/peps/pep-0552

   (3) https://www.python.org/dev/peps/pep-0552


File: python.info,  Node: PEP 545 Python Documentation Translations,  Next: Development Runtime Mode -X dev,  Prev: PEP 552 Hash-based pyc Files,  Up: New Features<2>

1.2.2.11 PEP 545: Python Documentation Translations
...................................................

PEP 545(1) describes the process of creating and maintaining Python
documentation translations.

Three new translations have been added:

   - Japanese: ‘https://docs.python.org/ja/’

   - French: ‘https://docs.python.org/fr/’

   - Korean: ‘https://docs.python.org/ko/’

也參考
......

PEP 545(2) – Python Documentation Translations

     PEP written and implemented by Julien Palard, Inada Naoki, and
     Victor Stinner.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0545

   (2) https://www.python.org/dev/peps/pep-0545


File: python.info,  Node: Development Runtime Mode -X dev,  Prev: PEP 545 Python Documentation Translations,  Up: New Features<2>

1.2.2.12 Development Runtime Mode: -X dev
.........................................

The new *note -X: 156. ‘dev’ command line option or the new *note
PYTHONDEVMODE: 331. environment variable can be used to enable CPython’s
`development mode'.  When in development mode, CPython performs
additional runtime checks that are too expensive to be enabled by
default.  See *note -X: 156. ‘dev’ documentation for the full
description of the effects of this mode.


File: python.info,  Node: Other Language Changes<2>,  Next: New Modules<2>,  Prev: New Features<2>,  Up: What's New In Python 3 7

1.2.3 Other Language Changes
----------------------------

   * An *note await: 1a4. expression and comprehensions containing an
     *note async for: 2e4. clause were illegal in the expressions in
     *note formatted string literals: 15d. 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(): 333. and *note bytearray.fromhex(): 334. now
     ignore all ASCII whitespace, not only spaces.  (Contributed by
     Robert Xiao in bpo-28927(3).)

   * *note str: 335, *note bytes: 336, and *note bytearray: 337. gained
     support for the new *note isascii(): 338. 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: 339. 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: 33a. can now be instantiated from Python code,
     and the ‘tb_next’ attribute on *note tracebacks: 33b. is now
     writable.  (Contributed by Nathaniel J. Smith in bpo-30579(8).)

   * When using the *note -m: 33c. 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: 156. ‘importtime’ option or the *note
     PYTHONPROFILEIMPORTTIME: 33d. environment variable can be used to
     show the timing of each module import.  (Contributed by Victor
     Stinner in bpo-31415(10).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue12844

   (2) https://bugs.python.org/issue18896

   (3) https://bugs.python.org/issue28927

   (4) https://bugs.python.org/issue32677

   (5) https://bugs.python.org/issue29546

   (6) https://bugs.python.org/issue30024

   (7) https://bugs.python.org/issue28974

   (8) https://bugs.python.org/issue30579

   (9) https://bugs.python.org/issue33053

   (10) https://bugs.python.org/issue31415


File: python.info,  Node: New Modules<2>,  Next: Improved Modules<2>,  Prev: Other Language Changes<2>,  Up: What's New In Python 3 7

1.2.4 New Modules
-----------------

* Menu:

* contextvars::
* dataclasses::
* importlib.resources: importlib resources.


File: python.info,  Node: contextvars,  Next: dataclasses,  Up: New Modules<2>

1.2.4.1 contextvars
...................

The new *note contextvars: 25. module and a set of *note new C APIs:
340. 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: a. and *note decimal: 36. 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

     PEP written and implemented by Yury Selivanov

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0567


File: python.info,  Node: dataclasses,  Next: importlib resources,  Prev: contextvars,  Up: New Modules<2>

1.2.4.2 dataclasses
...................

The new *note dataclass(): 342. 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__(): 343, *note __eq__(): 344, and *note __hash__(): 345.
are generated automatically.

Example:

     @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

     PEP written and implemented by Eric V. Smith

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0557


File: python.info,  Node: importlib resources,  Prev: dataclasses,  Up: New Modules<2>

1.2.4.3 importlib.resources
...........................

The new *note importlib.resources: 9f. 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: 347. 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/issue32248

   (2) http://importlib-resources.readthedocs.io/en/latest/


File: python.info,  Node: Improved Modules<2>,  Next: C API Changes,  Prev: New Modules<2>,  Up: What's New In Python 3 7

1.2.5 Improved Modules
----------------------

* Menu:

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


File: python.info,  Node: argparse,  Next: asyncio<2>,  Up: Improved Modules<2>

1.2.5.1 argparse
................

The new *note ArgumentParser.parse_intermixed_args(): 34a. method allows
intermixing options and positional arguments.  (Contributed by paul.j3
in bpo-14191(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14191


File: python.info,  Node: asyncio<2>,  Next: binascii,  Prev: argparse,  Up: Improved Modules<2>

1.2.5.2 asyncio
...............

The *note asyncio: a. module has received many new features, usability
and *note performance improvements: 34c.  Notable changes include:

   * The new *note provisional: 34d. *note asyncio.run(): 1a6. 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: 25.  *note
     loop.call_soon(): 34e, *note loop.call_soon_threadsafe(): 34f,
     *note loop.call_later(): 350, *note loop.call_at(): 351, and *note
     Future.add_done_callback(): 352. have a new optional keyword-only
     `context' parameter.  *note Tasks: 1ae. 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(): 1af. 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(): 353. 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(): 354. 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(): 355. function returns the
     currently running *note Task: 1ae. instance, and the new *note
     asyncio.all_tasks(): 356. function returns a set of all existing
     ‘Task’ instances in a given loop.  The *note Task.current_task():
     357. and *note Task.all_tasks(): 358. methods have been deprecated.
     (Contributed by Andrew Svetlov in bpo-32250(7).)

   * The new `provisional' *note BufferedProtocol: 2ca. 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(): 359. function returns the
     currently running loop, and raises a *note RuntimeError: 2bb. if no
     loop is running.  This is in contrast with *note
     asyncio.get_event_loop(): 35a, 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(): 35b. coroutine method
     allows waiting until the stream writer is closed.  The new *note
     StreamWriter.is_closing(): 35c. 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(): 35d. coroutine method allows
     sending files using *note os.sendfile: 35e. when possible.
     (Contributed by Andrew Svetlov in bpo-32410(11).)

   * The new *note Future.get_loop(): 35f. and ‘Task.get_loop()’ methods
     return the instance of the loop on which a task or a future were
     created.  *note Server.get_loop(): 360. allows doing the same for
     *note asyncio.Server: 361. 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: 361. begin serving.  Previously, the server would
     start serving immediately when created.  The new `start_serving'
     keyword argument to *note loop.create_server(): 362. and *note
     loop.create_unix_server(): 363, as well as *note
     Server.start_serving(): 364, and *note Server.serve_forever(): 365.
     can be used to decouple server instantiation and serving.  The new
     *note Server.is_serving(): 366. method returns ‘True’ if the server
     is serving.  *note Server: 361. 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.

     (Contributed by Yury Selivanov in bpo-32662(14).)

   * Callback objects returned by *note loop.call_later(): 350. gained
     the new *note when(): 367. method which returns an absolute
     scheduled callback timestamp.  (Contributed by Andrew Svetlov in
     bpo-32741(15).)

   * The *note loop.create_datagram_endpoint(): 2e8. method gained
     support for Unix sockets.  (Contributed by Quentin Dawans in
     bpo-31245(16).)

   * The *note asyncio.open_connection(): 368, *note
     asyncio.start_server(): 369. functions, *note
     loop.create_connection(): 1b3, *note loop.create_server(): 362,
     *note loop.create_accepted_socket(): 36a. 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(): 36b. 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:
     1a3./*note await: 1a4. syntax.  (Contributed by Andrew Svetlov in
     bpo-32193(19).)

   * The new *note ReadTransport.is_reading(): 36c. method can be used
     to determine the reading state of the transport.  Additionally,
     calls to *note ReadTransport.resume_reading(): 36d. and *note
     ReadTransport.pause_reading(): 36e. are now idempotent.
     (Contributed by Yury Selivanov in bpo-32356(20).)

   * Loop methods which accept socket paths now support passing *note
     path-like objects: 36f.  (Contributed by Yury Selivanov in
     bpo-32066(21).)

   * In *note asyncio: a. 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: 370.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32314

   (2) https://www.python.org/dev/peps/pep-0567

   (3) https://bugs.python.org/issue32436

   (4) https://bugs.python.org/issue32311

   (5) https://bugs.python.org/issue23749

   (6) https://bugs.python.org/issue31819

   (7) https://bugs.python.org/issue32250

   (8) https://bugs.python.org/issue32251

   (9) https://bugs.python.org/issue32269

   (10) https://bugs.python.org/issue32391

   (11) https://bugs.python.org/issue32410

   (12) https://bugs.python.org/issue32415

   (13) https://bugs.python.org/issue32418

   (14) https://bugs.python.org/issue32662

   (15) https://bugs.python.org/issue32741

   (16) https://bugs.python.org/issue31245

   (17) https://bugs.python.org/issue29970

   (18) https://bugs.python.org/issue31943

   (19) https://bugs.python.org/issue32193

   (20) https://bugs.python.org/issue32356

   (21) https://bugs.python.org/issue32066

   (22) https://bugs.python.org/issue27456

   (23) https://bugs.python.org/issue30508

   (24) https://bugs.python.org/issue33792


File: python.info,  Node: binascii,  Next: calendar,  Prev: asyncio<2>,  Up: Improved Modules<2>

1.2.5.3 binascii
................

The *note b2a_uu(): 372. 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/issue30103


File: python.info,  Node: calendar,  Next: collections<2>,  Prev: binascii,  Up: Improved Modules<2>

1.2.5.4 calendar
................

The *note HTMLCalendar: 374. 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/issue30095


File: python.info,  Node: collections<2>,  Next: compileall,  Prev: calendar,  Up: Improved Modules<2>

1.2.5.5 collections
...................

‘collections.namedtuple()’ now supports default values.  (Contributed by
Raymond Hettinger in bpo-32320(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32320


File: python.info,  Node: compileall,  Next: concurrent futures,  Prev: collections<2>,  Up: Improved Modules<2>

1.2.5.6 compileall
..................

*note compileall.compile_dir(): 377. learned the new `invalidation_mode'
parameter, which can be used to enable *note hash-based .pyc
invalidation: 306.  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/issue31650


File: python.info,  Node: concurrent futures,  Next: contextlib,  Prev: compileall,  Up: Improved Modules<2>

1.2.5.7 concurrent.futures
..........................

*note ProcessPoolExecutor: 2a5. and *note ThreadPoolExecutor: 27b. now
support the new `initializer' and `initargs' constructor arguments.
(Contributed by Antoine Pitrou in bpo-21423(1).)

The *note ProcessPoolExecutor: 2a5. 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/issue21423

   (2) https://bugs.python.org/issue31540


File: python.info,  Node: contextlib,  Next: cProfile<2>,  Prev: concurrent futures,  Up: Improved Modules<2>

1.2.5.8 contextlib
..................

The new *note nullcontext(): 37a. is a simpler and faster no-op context
manager than *note ExitStack: 37b.  (Contributed by Jesse-Bakker in
bpo-10049(1).)

The new *note asynccontextmanager(): 37c, *note
AbstractAsyncContextManager: 37d, and *note AsyncExitStack: 37e. 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/issue10049

   (2) https://bugs.python.org/issue29679

   (3) https://bugs.python.org/issue30241

   (4) https://bugs.python.org/issue29302


File: python.info,  Node: cProfile<2>,  Next: crypt,  Prev: contextlib,  Up: Improved Modules<2>

1.2.5.9 cProfile
................

The *note cProfile: 28. 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/issue21862


File: python.info,  Node: crypt,  Next: datetime<2>,  Prev: cProfile<2>,  Up: Improved Modules<2>

1.2.5.10 crypt
..............

The *note crypt: 29. module now supports the Blowfish hashing method.
(Contributed by Serhiy Storchaka in bpo-31664(1).)

The *note mksalt(): 381. function now allows specifying the number of
rounds for hashing.  (Contributed by Serhiy Storchaka in bpo-31702(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31664

   (2) https://bugs.python.org/issue31702


File: python.info,  Node: datetime<2>,  Next: dbm,  Prev: crypt,  Up: Improved Modules<2>

1.2.5.11 datetime
.................

The new *note datetime.fromisoformat(): 383. method constructs a *note
datetime: 195. object from a string in one of the formats output by
*note datetime.isoformat(): 384.  (Contributed by Paul Ganssle in
bpo-15873(1).)

The *note tzinfo: 385. class now supports sub-minute offsets.
(Contributed by Alexander Belopolsky in bpo-5288(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue15873

   (2) https://bugs.python.org/issue5288


File: python.info,  Node: dbm,  Next: decimal,  Prev: datetime<2>,  Up: Improved Modules<2>

1.2.5.12 dbm
............

*note dbm.dumb: 33. 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,  Prev: dbm,  Up: Improved Modules<2>

1.2.5.13 decimal
................

The *note decimal: 36. module now uses *note context variables: 2fa. to
store the decimal context.  (Contributed by Yury Selivanov in
bpo-32630(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32630


File: python.info,  Node: dis,  Next: distutils,  Prev: decimal,  Up: Improved Modules<2>

1.2.5.14 dis
............

The *note dis(): 389. 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/issue11822


File: python.info,  Node: distutils,  Next: enum,  Prev: dis,  Up: Improved Modules<2>

1.2.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/issue11913


File: python.info,  Node: enum,  Next: functools<2>,  Prev: distutils,  Up: Improved Modules<2>

1.2.5.16 enum
.............

The *note Enum: 38c. 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: 193. (e.g.  ‘1 in Color’);
similarly, attempting to check for non-Flag objects in a ‘Flag’ member
will raise *note TypeError: 193. (e.g.  ‘1 in Perm.RW’); currently, both
operations return *note False: 38d. instead and are deprecated.
(Contributed by Ethan Furman in bpo-33217(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31801

   (2) https://bugs.python.org/issue33217


File: python.info,  Node: functools<2>,  Next: gc<2>,  Prev: enum,  Up: Improved Modules<2>

1.2.5.17 functools
..................

*note functools.singledispatch(): 38f. now supports registering
implementations using type annotations.  (Contributed by Łukasz Langa in
bpo-32227(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32227


File: python.info,  Node: gc<2>,  Next: hmac,  Prev: functools<2>,  Up: Improved Modules<2>

1.2.5.18 gc
...........

The new *note gc.freeze(): 391. 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(): 392. functions reverses this operation.  Additionally,
*note gc.get_freeze_count(): 393. can be used to obtain the number of
frozen objects.  (Contributed by Li Zekun in bpo-31558(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31558


File: python.info,  Node: hmac,  Next: http client,  Prev: gc<2>,  Up: Improved Modules<2>

1.2.5.19 hmac
.............

The *note hmac: 8f. module now has an optimized one-shot *note digest():
395. function, which is up to three times faster than ‘HMAC()’.
(Contributed by Christian Heimes in bpo-32433(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32433


File: python.info,  Node: http client,  Next: http server,  Prev: hmac,  Up: Improved Modules<2>

1.2.5.20 http.client
....................

*note HTTPConnection: 397. and *note HTTPSConnection: 398. now support
the new `blocksize' argument for improved upload throughput.
(Contributed by Nir Soffer in bpo-31945(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31945


File: python.info,  Node: http server,  Next: idlelib and IDLE,  Prev: http client,  Up: Improved Modules<2>

1.2.5.21 http.server
....................

*note SimpleHTTPRequestHandler: 39a. 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: 39a. 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: 39b. 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/issue29654

   (2) https://bugs.python.org/issue28707

   (3) https://bugs.python.org/issue31639


File: python.info,  Node: idlelib and IDLE,  Next: importlib,  Prev: http server,  Up: Improved Modules<2>

1.2.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/issue15786

   (2) https://bugs.python.org/issue1612262

   (3) https://bugs.python.org/issue13802

   (4) https://bugs.python.org/issue31860

   (5) https://bugs.python.org/issue27099

   (6) https://bugs.python.org/issue33642

   (7) https://bugs.python.org/issue33768

   (8) https://bugs.python.org/issue33679

   (9) https://bugs.python.org/issue33656

   (10) https://bugs.python.org/issue1529353

   (11) https://bugs.python.org/issue5680

   (12) https://bugs.python.org/issue37627

   (13) https://bugs.python.org/issue17535


File: python.info,  Node: importlib,  Next: io<2>,  Prev: idlelib and IDLE,  Up: Improved Modules<2>

1.2.5.23 importlib
..................

The *note importlib.abc.ResourceReader: 347. ABC was introduced to
support the loading of resources from packages.  See also *note
importlib.resources: 2fc.  (Contributed by Barry Warsaw, Brett Cannon in
bpo-32248(1).)

*note importlib.reload(): 39e. now raises *note ModuleNotFoundError:
39f. if the module lacks a spec.  (Contributed by Garvit Khatri in
bpo-29851(2).)

‘importlib.find_spec()’ now raises *note ModuleNotFoundError: 39f.
instead of *note AttributeError: 3a0. 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: 306. embeds the value
returned by this function.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32248

   (2) https://bugs.python.org/issue29851

   (3) https://bugs.python.org/issue30436


File: python.info,  Node: io<2>,  Next: ipaddress,  Prev: importlib,  Up: Improved Modules<2>

1.2.5.24 io
...........

The new *note TextIOWrapper.reconfigure(): 3a2. 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/issue30526

   (2) https://bugs.python.org/issue15216


File: python.info,  Node: ipaddress,  Next: itertools<2>,  Prev: io<2>,  Up: Improved Modules<2>

1.2.5.25 ipaddress
..................

The new ‘subnet_of()’ and ‘supernet_of()’ methods of *note
ipaddress.IPv6Network: 3a4. and *note ipaddress.IPv4Network: 3a5. can be
used for network containment tests.  (Contributed by Michel Albert and
Cheryl Sabella in bpo-20825(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20825


File: python.info,  Node: itertools<2>,  Next: locale,  Prev: ipaddress,  Up: Improved Modules<2>

1.2.5.26 itertools
..................

*note itertools.islice(): 3a7. now accepts *note integer-like objects:
18b. as start, stop, and slice arguments.  (Contributed by Will Roberts
in bpo-30537(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue30537


File: python.info,  Node: locale,  Next: logging<2>,  Prev: itertools<2>,  Up: Improved Modules<2>

1.2.5.27 locale
...............

The new `monetary' argument to *note locale.format_string(): 3a9. 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(): 3aa. function now always
returns ‘'UTF-8'’ on Android or when in the *note forced UTF-8 mode:
305.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10379


File: python.info,  Node: logging<2>,  Next: math<2>,  Prev: locale,  Up: Improved Modules<2>

1.2.5.28 logging
................

*note Logger: 3ac. instances can now be pickled.  (Contributed by Vinay
Sajip in bpo-30520(1).)

The new *note StreamHandler.setStream(): 3ad. 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(): 3ae.
(Contributed by Preston Landers in bpo-31080(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue30520

   (2) https://bugs.python.org/issue30522

   (3) https://bugs.python.org/issue31080


File: python.info,  Node: math<2>,  Next: mimetypes,  Prev: logging<2>,  Up: Improved Modules<2>

1.2.5.29 math
.............

The new *note math.remainder(): 3b0. function implements the IEEE
754-style remainder operation.  (Contributed by Mark Dickinson in
bpo-29962(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue29962


File: python.info,  Node: mimetypes,  Next: msilib,  Prev: math<2>,  Up: Improved Modules<2>

1.2.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/issue22589


File: python.info,  Node: msilib,  Next: multiprocessing<2>,  Prev: mimetypes,  Up: Improved Modules<2>

1.2.5.31 msilib
...............

The new *note Database.Close(): 3b3. method can be used to close the MSI
(last-in, first-out) database.  (Contributed by Berker Peksag in
bpo-20486(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20486


File: python.info,  Node: multiprocessing<2>,  Next: os<2>,  Prev: msilib,  Up: Improved Modules<2>

1.2.5.32 multiprocessing
........................

The new *note Process.close(): 3b5. method explicitly closes the process
object and releases all resources associated with it.  *note ValueError:
1fc. is raised if the underlying process is still running.  (Contributed
by Antoine Pitrou in bpo-30596(1).)

The new *note Process.kill(): 3b6. 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: 3b7. are now joined on
process exit.  (Contributed by Antoine Pitrou in bpo-18966(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue30596

   (2) https://bugs.python.org/issue30794

   (3) https://bugs.python.org/issue18966


File: python.info,  Node: os<2>,  Next: pathlib<2>,  Prev: multiprocessing<2>,  Up: Improved Modules<2>

1.2.5.33 os
...........

*note os.fwalk(): 3b9. now accepts the `path' argument as *note bytes:
336.  (Contributed by Serhiy Storchaka in bpo-28682(1).)

*note os.scandir(): 260. gained support for *note file descriptors: 3ba.
(Contributed by Serhiy Storchaka in bpo-25996(2).)

The new *note register_at_fork(): 3bb. function allows registering
Python callbacks to be executed at process fork.  (Contributed by
Antoine Pitrou in bpo-16500(3).)

Added *note os.preadv(): 3bc. (combine the functionality of *note
os.readv(): 3bd. and *note os.pread(): 3be.) and *note os.pwritev():
3bf. functions (combine the functionality of *note os.writev(): 3c0. and
*note os.pwrite(): 3c1.).  (Contributed by Pablo Galindo in
bpo-31368(4).)

The mode argument of *note os.makedirs(): 3c2. no longer affects the
file permission bits of newly-created intermediate-level directories.
(Contributed by Serhiy Storchaka in bpo-19930(5).)

*note os.dup2(): 3c3. 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(): 1f2. now contains the *note
st_fstype: 3c4. attribute on Solaris and its derivatives.  (Contributed
by Jesús Cea Avión in bpo-32659(7).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28682

   (2) https://bugs.python.org/issue25996

   (3) https://bugs.python.org/issue16500

   (4) https://bugs.python.org/issue31368

   (5) https://bugs.python.org/issue19930

   (6) https://bugs.python.org/issue32441

   (7) https://bugs.python.org/issue32659


File: python.info,  Node: pathlib<2>,  Next: pdb,  Prev: os<2>,  Up: Improved Modules<2>

1.2.5.34 pathlib
................

The new *note Path.is_mount(): 206. 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/issue30897


File: python.info,  Node: pdb,  Next: py_compile<2>,  Prev: pathlib<2>,  Up: Improved Modules<2>

1.2.5.35 pdb
............

*note pdb.set_trace(): 3c7. 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: ca. 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/issue31389

   (2) https://bugs.python.org/issue32206


File: python.info,  Node: py_compile<2>,  Next: pydoc,  Prev: pdb,  Up: Improved Modules<2>

1.2.5.36 py_compile
...................

*note py_compile.compile(): 216. – and by extension, *note compileall:
21. – 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/issue29708


File: python.info,  Node: pydoc,  Next: queue,  Prev: py_compile<2>,  Up: Improved Modules<2>

1.2.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/issue31128


File: python.info,  Node: queue,  Next: re,  Prev: pydoc,  Up: Improved Modules<2>

1.2.5.38 queue
..............

The new *note SimpleQueue: 3cb. class is an unbounded FIFO (last-in,
first-out) queue.  (Contributed by Antoine Pitrou in bpo-14976(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14976


File: python.info,  Node: re,  Next: signal,  Prev: queue,  Up: Improved Modules<2>

1.2.5.39 re
...........

The flags *note re.ASCII: 3cd, *note re.LOCALE: 3ce. and ‘re.UNICODE’
can be set within the scope of a group.  (Contributed by Serhiy
Storchaka in bpo-31690(1).)

*note re.split(): 3cf. 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: 3ce. 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: 32a. 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(): 3d0. and *note copy.deepcopy(): 3d1.  (Contributed by
Serhiy Storchaka in bpo-10076(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31690

   (2) https://bugs.python.org/issue25054

   (3) https://bugs.python.org/issue30215

   (4) https://bugs.python.org/issue30349

   (5) https://bugs.python.org/issue10076


File: python.info,  Node: signal,  Next: socket<2>,  Prev: re,  Up: Improved Modules<2>

1.2.5.40 signal
...............

The new `warn_on_full_buffer' argument to the *note
signal.set_wakeup_fd(): 3d3. 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/issue30050


File: python.info,  Node: socket<2>,  Next: socketserver,  Prev: signal,  Up: Improved Modules<2>

1.2.5.41 socket
...............

The new *note socket.getblocking(): 3d5. 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(): 3d6. function closes the passed socket
file descriptor.  This function should be used instead of *note
os.close(): 3d7. for better compatibility across platforms.
(Contributed by Christian Heimes in bpo-32454(2).)

The *note socket: f0. 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: 3d8. 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/issue32373

   (2) https://bugs.python.org/issue32454

   (3) https://bugs.python.org/issue26273

   (4) https://bugs.python.org/issue29728

   (5) https://bugs.python.org/issue27584

   (6) https://bugs.python.org/issue28134


File: python.info,  Node: socketserver,  Next: sqlite3,  Prev: socket<2>,  Up: Improved Modules<2>

1.2.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: 3da. and *note
socketserver.ThreadingMixIn: 3db. classes.  Set the class attribute to
‘False’ to get the pre-3.7 behaviour.


File: python.info,  Node: sqlite3,  Next: ssl<2>,  Prev: socketserver,  Up: Improved Modules<2>

1.2.5.43 sqlite3
................

*note sqlite3.Connection: 3dd. now exposes the *note backup(): 3de.
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(): 3df. now accepts any
*note path-like object: 36f, instead of just a string.  (Contributed by
Anders Lorentsen in bpo-31843(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27645

   (2) https://bugs.python.org/issue31843


File: python.info,  Node: ssl<2>,  Next: string,  Prev: sqlite3,  Up: Improved Modules<2>

1.2.5.44 ssl
............

The *note ssl: f4. module now uses OpenSSL’s builtin API instead of
*note match_hostname(): 3e1. 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: 3e2. 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: 3e3.  (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: 3e4. 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).)

*note match_hostname(): 3e1. 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: 3e5. 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: 3e6.  (Contributed by Christian Heimes
in bpo-32947(7), bpo-20995(8), bpo-29136(9), bpo-30622(10) and
bpo-33618(11))

*note SSLSocket: 3e7. and *note SSLObject: 3e8. no longer have a public
constructor.  Direct instantiation was never a documented and supported
feature.  Instances must be created with *note SSLContext: 3e9. methods
*note wrap_socket(): 3ea. and *note wrap_bio(): 3eb.  (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: 3ec. and
*note SSLContext.maximum_version: 3ed.  Supported protocols are
indicated by several new flags, such as *note HAS_TLSv1_1: 3ee.
(Contributed by Christian Heimes in bpo-32609(13).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31399

   (2) https://bugs.python.org/issue32185

   (3) https://bugs.python.org/issue23033

   (4) https://bugs.python.org/issue31399

   (5) https://bugs.python.org/issue31429

   (6) https://bugs.python.org/issue28414

   (7) https://bugs.python.org/issue32947

   (8) https://bugs.python.org/issue20995

   (9) https://bugs.python.org/issue29136

   (10) https://bugs.python.org/issue30622

   (11) https://bugs.python.org/issue33618

   (12) https://bugs.python.org/issue32951

   (13) https://bugs.python.org/issue32609


File: python.info,  Node: string,  Next: subprocess,  Prev: ssl<2>,  Up: Improved Modules<2>

1.2.5.45 string
...............

*note string.Template: 3f0. 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/issue1198569


File: python.info,  Node: subprocess,  Next: sys<2>,  Prev: string,  Up: Improved Modules<2>

1.2.5.46 subprocess
...................

The *note subprocess.run(): 3f2. function accepts the new
`capture_output' keyword argument.  When true, stdout and stderr will be
captured.  This is equivalent to passing *note subprocess.PIPE: 3f3. as
`stdout' and `stderr' arguments.  (Contributed by Bo Bayles in
bpo-32102(1).)

The ‘subprocess.run’ function and the *note subprocess.Popen: 2ba.
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: 2ba.  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: 198. during *note subprocess.call(): 3f4, *note
subprocess.run(): 3f2, or in a *note Popen: 2ba. 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/issue32102

   (2) https://bugs.python.org/issue31756

   (3) https://bugs.python.org/issue19764

   (4) https://bugs.python.org/issue25942


File: python.info,  Node: sys<2>,  Next: time<2>,  Prev: subprocess,  Up: Improved Modules<2>

1.2.5.47 sys
............

The new *note sys.breakpointhook(): 318. hook function is called by the
built-in *note breakpoint(): 2fe.  (Contributed by Barry Warsaw in
bpo-31353(1).)

On Android, the new *note sys.getandroidapilevel(): 3f6. returns the
build-time Android API version.  (Contributed by Victor Stinner in
bpo-28740(2).)

The new *note sys.get_coroutine_origin_tracking_depth(): 3f7. function
returns the current coroutine origin tracking depth, as set by the new
*note sys.set_coroutine_origin_tracking_depth(): 3f8.  *note asyncio: a.
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/issue31353

   (2) https://bugs.python.org/issue28740

   (3) https://bugs.python.org/issue32591


File: python.info,  Node: time<2>,  Next: tkinter<2>,  Prev: sys<2>,  Up: Improved Modules<2>

1.2.5.48 time
.............

PEP 564(1) adds six new functions with nanosecond resolution to the
*note time: 10b. module:

   * *note time.clock_gettime_ns(): 323.

   * *note time.clock_settime_ns(): 324.

   * *note time.monotonic_ns(): 325.

   * *note time.perf_counter_ns(): 326.

   * *note time.process_time_ns(): 327.

   * *note time.time_ns(): 328.

New clock identifiers have been added:

   * *note time.CLOCK_BOOTTIME: 3fa. (Linux): Identical to *note
     time.CLOCK_MONOTONIC: 3fb, except it also includes any time that
     the system is suspended.

   * *note time.CLOCK_PROF: 3fc. (FreeBSD, NetBSD and OpenBSD):
     High-resolution per-process CPU timer.

   * *note time.CLOCK_UPTIME: 3fd. (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(): 3fe. and *note time.thread_time_ns():
3ff. 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(): 400. function returns the
clock ID of the thread-specific CPU-time clock.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0564

   (2) https://bugs.python.org/issue32025


File: python.info,  Node: tkinter<2>,  Next: tracemalloc,  Prev: time<2>,  Up: Improved Modules<2>

1.2.5.49 tkinter
................

The new *note tkinter.ttk.Spinbox: 402. class is now available.
(Contributed by Alan Moore in bpo-32585(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32585


File: python.info,  Node: tracemalloc,  Next: types,  Prev: tkinter<2>,  Up: Improved Modules<2>

1.2.5.50 tracemalloc
....................

*note tracemalloc.Traceback: 404. behaves more like regular tracebacks,
sorting the frames from oldest to most recent.  *note
Traceback.format(): 405. 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/issue32121


File: python.info,  Node: types,  Next: unicodedata<2>,  Prev: tracemalloc,  Up: Improved Modules<2>

1.2.5.51 types
..............

The new *note WrapperDescriptorType: 407, *note MethodWrapperType: 408,
*note MethodDescriptorType: 409, and *note ClassMethodDescriptorType:
40a. 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(): 40b. 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/issue29377

   (2) https://bugs.python.org/issue32265

   (3) https://www.python.org/dev/peps/pep-0560

   (4) https://bugs.python.org/issue32717


File: python.info,  Node: unicodedata<2>,  Next: unittest<2>,  Prev: types,  Up: Improved Modules<2>

1.2.5.52 unicodedata
....................

The internal *note unicodedata: 11b. database has been upgraded to use
Unicode 11(1).  (Contributed by Benjamin Peterson.)

   ---------- Footnotes ----------

   (1) http://www.unicode.org/versions/Unicode11.0.0/


File: python.info,  Node: unittest<2>,  Next: unittest mock,  Prev: unicodedata<2>,  Up: Improved Modules<2>

1.2.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/issue32071


File: python.info,  Node: unittest mock,  Next: urllib parse<2>,  Prev: unittest<2>,  Up: Improved Modules<2>

1.2.5.54 unittest.mock
......................

The *note sentinel: 40f. attributes now preserve their identity when
they are *note copied: 26. or *note pickled: cb.  (Contributed by Serhiy
Storchaka in bpo-20804(1).)

The new *note seal(): 410. function allows sealing *note Mock: 24a.
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/issue20804

   (2) https://bugs.python.org/issue30541


File: python.info,  Node: urllib parse<2>,  Next: uu,  Prev: unittest mock,  Up: Improved Modules<2>

1.2.5.55 urllib.parse
.....................

*note urllib.parse.quote(): 412. 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://tools.ietf.org/html/rfc2396.html

   (2) https://tools.ietf.org/html/rfc3986.html

   (3) https://bugs.python.org/issue16285


File: python.info,  Node: uu,  Next: uuid,  Prev: urllib parse<2>,  Up: Improved Modules<2>

1.2.5.56 uu
...........

The *note uu.encode(): 414. 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/issue30103


File: python.info,  Node: uuid,  Next: warnings,  Prev: uu,  Up: Improved Modules<2>

1.2.5.57 uuid
.............

The new *note UUID.is_safe: 416. 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(): 417. 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(): 418.  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/issue22807

   (2) https://bugs.python.org/issue32107


File: python.info,  Node: warnings,  Next: xml etree,  Prev: uuid,  Up: Improved Modules<2>

1.2.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: 41a. and the new CPython-specific *note -X: 156. ‘dev’
     option) are always passed to the warnings machinery via the *note
     sys.warnoptions: 41b. attribute.

   * warnings filters enabled via the command line or the environment
     now have the following order of precedence:

             * the ‘BytesWarning’ filter for *note -b: 41a. (or ‘-bb’)

             * any filters specified with the *note -W: 41c. option

             * any filters specified with the *note PYTHONWARNINGS: 41d.
               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 CPython debug builds, all warnings are now displayed by default
     (the implicit filter list is empty)

(Contributed by Nick Coghlan and Victor Stinner in bpo-20361(1),
bpo-32043(2), and 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__: 308. for details.  (Contributed by Nick
Coghlan in bpo-31975(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20361

   (2) https://bugs.python.org/issue32043

   (3) https://bugs.python.org/issue32230

   (4) https://bugs.python.org/issue31975


File: python.info,  Node: xml etree,  Next: xmlrpc server,  Prev: warnings,  Up: Improved Modules<2>

1.2.5.59 xml.etree
..................

*note ElementPath: 41f. 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/issue31648


File: python.info,  Node: xmlrpc server,  Next: zipapp,  Prev: xml etree,  Up: Improved Modules<2>

1.2.5.60 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/issue7769


File: python.info,  Node: zipapp,  Next: zipfile,  Prev: xmlrpc server,  Up: Improved Modules<2>

1.2.5.61 zipapp
...............

Function *note create_archive(): 422. 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(): 422. 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/issue31072

   (2) https://bugs.python.org/issue31638


File: python.info,  Node: zipfile,  Prev: zipapp,  Up: Improved Modules<2>

1.2.5.62 zipfile
................

*note ZipFile: 424. 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/issue21417

   (2) https://bugs.python.org/issue30693


File: python.info,  Node: C API Changes,  Next: Build Changes,  Prev: Improved Modules<2>,  Up: What's New In Python 3 7

1.2.6 C API Changes
-------------------

A new API for thread-local storage has been implemented.  See *note PEP
539; New C API for Thread-Local Storage: 309. for an overview and *note
Thread Specific Storage (TSS) API: 31c. for a complete reference.
(Contributed by Masayuki Yamamoto in bpo-25658(1).)

The new *note context variables: 2fa. functionality exposes a number of
*note new C APIs: 340.

The new *note PyImport_GetModule(): 426. function returns the previously
imported module with the given name.  (Contributed by Eric Snow in
bpo-28411(2).)

The new *note Py_RETURN_RICHCOMPARE: 427. macro eases writing rich
comparison functions.  (Contributed by Petr Victorin in bpo-23699(3).)

The new *note Py_UNREACHABLE: 428. macro can be used to mark unreachable
code paths.  (Contributed by Barry Warsaw in bpo-31338(4).)

The *note tracemalloc: 115. now exposes a C API through the new *note
PyTraceMalloc_Track(): 429. and *note PyTraceMalloc_Untrack(): 42a.
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: 42b, *note
PyGetSetDef: 42c, *note PyStructSequence_Field: 42d, *note
PyStructSequence_Desc: 42e, 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(): 42f. and *note
PyUnicode_AsUTF8(): 430. is now of type ‘const char *’ rather of ‘char
*’.  (Contributed by Serhiy Storchaka in bpo-28769(8).)

The result of *note PyMapping_Keys(): 431, *note PyMapping_Values():
432. and *note PyMapping_Items(): 433. 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(): 434. and *note
PySlice_AdjustIndices(): 435.  (Contributed by Serhiy Storchaka in
bpo-27867(10).)

*note PyOS_AfterFork(): 436. is deprecated in favour of the new
functions *note PyOS_BeforeFork(): 437, *note PyOS_AfterFork_Parent():
438. and *note PyOS_AfterFork_Child(): 2ce.  (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(): 439. and *note PyTimeZone_FromOffsetAndName():
43a, and access to the UTC singleton with *note PyDateTime_TimeZone_UTC:
43b.  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(): 43c. changed from ‘long’ to ‘unsigned
long’.  (Contributed by Serhiy Storchaka in bpo-6532(15).)

*note PyUnicode_AsWideCharString(): 43d. now raises a *note ValueError:
1fc. 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(): 43e. 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: 30c.
section in this document and the *note Before Python Initialization:
43f. section in the C API documentation for more details.

The new *note PyInterpreterState_GetID(): 440. returns the unique ID for
a given interpreter.  (Contributed by Eric Snow in bpo-29102(17).)

*note Py_DecodeLocale(): 441, *note Py_EncodeLocale(): 442. now use the
UTF-8 encoding when the *note UTF-8 mode: 305. is enabled.  (Contributed
by Victor Stinner in bpo-29240(18).)

*note PyUnicode_DecodeLocaleAndSize(): 443. and *note
PyUnicode_EncodeLocale(): 444. 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(): 445. are
now adjusted to behave like string slices.  (Contributed by Xiang Zhang
in bpo-28822(20).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25658

   (2) https://bugs.python.org/issue28411

   (3) https://bugs.python.org/issue23699

   (4) https://bugs.python.org/issue31338

   (5) https://bugs.python.org/issue30054

   (6) https://bugs.python.org/issue31574

   (7) https://bugs.python.org/issue28761

   (8) https://bugs.python.org/issue28769

   (9) https://bugs.python.org/issue28280

   (10) https://bugs.python.org/issue27867

   (11) https://bugs.python.org/issue16500

   (12) https://bugs.python.org/issue22898

   (13) https://bugs.python.org/issue30697

   (14) https://bugs.python.org/issue10381

   (15) https://bugs.python.org/issue6532

   (16) https://bugs.python.org/issue30708

   (17) https://bugs.python.org/issue29102

   (18) https://bugs.python.org/issue29240

   (19) https://bugs.python.org/issue29240

   (20) https://bugs.python.org/issue28822


File: python.info,  Node: Build Changes,  Next: Optimizations<2>,  Prev: C API Changes,  Up: What's New In Python 3 7

1.2.7 Build Changes
-------------------

Support for building ‘--without-threads’ has been removed.  The *note
threading: 10a. 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: 2b. 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: f4. 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/issue31370

   (2) https://bugs.python.org/issue27979

   (3) https://bugs.python.org/issue30450


File: python.info,  Node: Optimizations<2>,  Next: Other CPython Implementation Changes,  Prev: Build Changes,  Up: What's New In Python 3 7

1.2.8 Optimizations
-------------------

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: a. module received
a number of notable optimizations for commonly used functions:

   * The *note asyncio.get_event_loop(): 35a. 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: 448. callback management has been optimized.
     (Contributed by Yury Selivanov in bpo-32348(9).)

   * *note asyncio.gather(): 287. is now up to 15% faster.  (Contributed
     by Yury Selivanov in bpo-32355(10).)

   * *note asyncio.sleep(): 286. 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: 300, the import time of *note typing:
11a. 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(): 449. and *note list.sort(): 44a. have been optimized for
common cases to be up to 40-75% faster.  (Contributed by Elliot
Gorokhovsky in bpo-28685(14).)

*note dict.copy(): 44b. is now up to 5.5 times faster.  (Contributed by
Yury Selivanov in bpo-31179(15).)

*note hasattr(): 44c. and *note getattr(): 44d. are now about 4 times
faster when `name' is not found and `obj' does not override *note
object.__getattr__(): 31f. or *note object.__getattribute__(): 44e.
(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(): 1b8. 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(): 3b9. function is now up to 2 times faster thanks
to the use of *note os.scandir(): 260.  (Contributed by Serhiy Storchaka
in bpo-25996(20).)

The speed of the *note shutil.rmtree(): 21d. function has been improved
by 20–40% thanks to the use of the *note os.scandir(): 260. function.
(Contributed by Serhiy Storchaka in bpo-28564(21).)

Optimized case-insensitive matching and searching of *note regular
expressions: de.  Searching some patterns can now be up to 20 times
faster.  (Contributed by Serhiy Storchaka in bpo-30285(22).)

*note re.compile(): 44f. 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(): 450. methods of classes *note
selectors.EpollSelector: 451, *note selectors.PollSelector: 452. and
*note selectors.DevpollSelector: 453. 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(): 454. and *note issubclass(): 455. 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: 194. and *note datetime.datetime: 195. 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: 456. 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(): 457. and *note math.erfc(): 458. 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/issue29300

   (2) https://bugs.python.org/issue29507

   (3) https://bugs.python.org/issue29452

   (4) https://bugs.python.org/issue29286

   (5) https://bugs.python.org/issue29585

   (6) https://bugs.python.org/issue31333

   (7) https://bugs.python.org/issue26110

   (8) https://bugs.python.org/issue32296

   (9) https://bugs.python.org/issue32348

   (10) https://bugs.python.org/issue32355

   (11) https://bugs.python.org/issue32351

   (12) https://bugs.python.org/issue31970

   (13) https://bugs.python.org/issue32226

   (14) https://bugs.python.org/issue28685

   (15) https://bugs.python.org/issue31179

   (16) https://bugs.python.org/issue32544

   (17) https://bugs.python.org/issue24821

   (18) https://bugs.python.org/issue28638

   (19) https://bugs.python.org/issue32403

   (20) https://bugs.python.org/issue25996

   (21) https://bugs.python.org/issue28564

   (22) https://bugs.python.org/issue30285

   (23) https://bugs.python.org/issue31671

   (24) https://bugs.python.org/issue30014

   (25) https://bugs.python.org/issue29469

   (26) https://bugs.python.org/issue11549

   (27) https://bugs.python.org/issue31333

   (28) https://bugs.python.org/issue32403

   (29) https://bugs.python.org/issue24700

   (30) https://bugs.python.org/issue26121


File: python.info,  Node: Other CPython Implementation Changes,  Next: Deprecated Python Behavior,  Prev: Optimizations<2>,  Up: What's New In Python 3 7

1.2.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 ‘f_trace_lines’ and ‘f_trace_opcodes’ 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(): 45a. 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 *note distutils: 39. ‘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/issue31344

   (2) https://bugs.python.org/issue32305

   (3) https://bugs.python.org/issue32303

   (4) https://bugs.python.org/issue32690

   (5) https://bugs.python.org/issue32304


File: python.info,  Node: Deprecated Python Behavior,  Next: Deprecated Python modules functions and methods,  Prev: Other CPython Implementation Changes,  Up: What's New In Python 3 7

1.2.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: 45c.
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: 279. when
compiled, in Python 3.8 this will be a *note SyntaxError: 45d.
(Contributed by Serhiy Storchaka in bpo-10544(1).)

Returning a subclass of *note complex: 18a. from *note
object.__complex__(): 18e. is deprecated and will be an error in future
Python versions.  This makes ‘__complex__()’ consistent with *note
object.__int__(): 18c. and *note object.__float__(): 18d.  (Contributed
by Serhiy Storchaka in bpo-28894(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10544

   (2) https://bugs.python.org/issue28894


File: python.info,  Node: Deprecated Python modules functions and methods,  Next: Deprecated functions and types of the C API,  Prev: Deprecated Python Behavior,  Up: What's New In Python 3 7

1.2.11 Deprecated Python modules, functions and methods
-------------------------------------------------------

* Menu:

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


File: python.info,  Node: aifc,  Next: asyncio<3>,  Up: Deprecated Python modules functions and methods

1.2.11.1 aifc
.............

‘aifc.openfp()’ has been deprecated and will be removed in Python 3.9.
Use *note aifc.open(): 460. instead.  (Contributed by Brian Curtin in
bpo-31985(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31985


File: python.info,  Node: asyncio<3>,  Next: collections<3>,  Prev: aifc,  Up: Deprecated Python modules functions and methods

1.2.11.2 asyncio
................

Support for directly ‘await’-ing instances of *note asyncio.Lock: 28c.
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 *note asyncio.Task.current_task(): 357. and *note
asyncio.Task.all_tasks(): 358. methods have been deprecated.
(Contributed by Andrew Svetlov in bpo-32250(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32253

   (2) https://bugs.python.org/issue32250


File: python.info,  Node: collections<3>,  Next: dbm<2>,  Prev: asyncio<3>,  Up: Deprecated Python modules functions and methods

1.2.11.3 collections
....................

In Python 3.8, the abstract base classes in *note collections.abc: 1f.
will no longer be exposed in the regular *note collections: 1e. 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/issue25988


File: python.info,  Node: dbm<2>,  Next: enum<2>,  Prev: collections<3>,  Up: Deprecated Python modules functions and methods

1.2.11.4 dbm
............

*note dbm.dumb: 33. 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/issue28847


File: python.info,  Node: enum<2>,  Next: gettext<2>,  Prev: dbm<2>,  Up: Deprecated Python modules functions and methods

1.2.11.5 enum
.............

In Python 3.8, attempting to check for non-Enum objects in ‘Enum’
classes will raise a *note TypeError: 193. (e.g.  ‘1 in Color’);
similarly, attempting to check for non-Flag objects in a ‘Flag’ member
will raise *note TypeError: 193. (e.g.  ‘1 in Perm.RW’); currently, both
operations return *note False: 38d. instead.  (Contributed by Ethan
Furman in bpo-33217(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33217


File: python.info,  Node: gettext<2>,  Next: importlib<2>,  Prev: enum<2>,  Up: Deprecated Python modules functions and methods

1.2.11.6 gettext
................

Using non-integer value for selecting a plural form in *note gettext:
89. is now deprecated.  It never correctly worked.  (Contributed by
Serhiy Storchaka in bpo-28692(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28692


File: python.info,  Node: importlib<2>,  Next: locale<2>,  Prev: gettext<2>,  Up: Deprecated Python modules functions and methods

1.2.11.7 importlib
..................

Methods *note MetaPathFinder.find_module(): 467. (replaced by *note
MetaPathFinder.find_spec(): 468.) and *note
PathEntryFinder.find_loader(): 469. (replaced by *note
PathEntryFinder.find_spec(): 46a.) both deprecated in Python 3.4 now
emit *note DeprecationWarning: 279.  (Contributed by Matthias Bussonnier
in bpo-29576(1))

The *note importlib.abc.ResourceLoader: 46b. ABC has been deprecated in
favour of *note importlib.abc.ResourceReader: 347.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue29576


File: python.info,  Node: locale<2>,  Next: macpath,  Prev: importlib<2>,  Up: Deprecated Python modules functions and methods

1.2.11.8 locale
...............

*note locale.format(): 46d. has been deprecated, use *note
locale.format_string(): 3a9. instead.  (Contributed by Garvit in
bpo-10379(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10379


File: python.info,  Node: macpath,  Next: threading<2>,  Prev: locale<2>,  Up: Deprecated Python modules functions and methods

1.2.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/issue9850


File: python.info,  Node: threading<2>,  Next: socket<3>,  Prev: macpath,  Up: Deprecated Python modules functions and methods

1.2.11.10 threading
...................

*note dummy_threading: 68. and *note _dummy_thread: 2. have been
deprecated.  It is no longer possible to build Python with threading
disabled.  Use *note threading: 10a. instead.  (Contributed by Antoine
Pitrou in bpo-31370(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31370


File: python.info,  Node: socket<3>,  Next: ssl<3>,  Prev: threading<2>,  Up: Deprecated Python modules functions and methods

1.2.11.11 socket
................

The silent argument value truncation in *note socket.htons(): 471. and
*note socket.ntohs(): 472. 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/issue28332


File: python.info,  Node: ssl<3>,  Next: sunau,  Prev: socket<3>,  Up: Deprecated Python modules functions and methods

1.2.11.12 ssl
.............

*note ssl.wrap_socket(): 474. is deprecated.  Use *note
ssl.SSLContext.wrap_socket(): 3ea. instead.  (Contributed by Christian
Heimes in bpo-28124(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28124


File: python.info,  Node: sunau,  Next: sys<3>,  Prev: ssl<3>,  Up: Deprecated Python modules functions and methods

1.2.11.13 sunau
...............

*note sunau.openfp(): 476. has been deprecated and will be removed in
Python 3.9.  Use *note sunau.open(): 477. instead.  (Contributed by
Brian Curtin in bpo-31985(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31985


File: python.info,  Node: sys<3>,  Next: wave,  Prev: sunau,  Up: Deprecated Python modules functions and methods

1.2.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/issue28799


File: python.info,  Node: wave,  Prev: sys<3>,  Up: Deprecated Python modules functions and methods

1.2.11.15 wave
..............

*note wave.openfp(): 47a. has been deprecated and will be removed in
Python 3.9.  Use *note wave.open(): 47b. instead.  (Contributed by Brian
Curtin in bpo-31985(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31985


File: python.info,  Node: Deprecated functions and types of the C API,  Next: Platform Support Removals,  Prev: Deprecated Python modules functions and methods,  Up: What's New In Python 3 7

1.2.12 Deprecated functions and types of the C API
--------------------------------------------------

Function *note PySlice_GetIndicesEx(): 47d. 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(): 436. has been deprecated.  Use *note
PyOS_BeforeFork(): 437, *note PyOS_AfterFork_Parent(): 438. or *note
PyOS_AfterFork_Child(): 2ce. instead.  (Contributed by Antoine Pitrou in
bpo-16500(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27867

   (2) https://bugs.python.org/issue16500


File: python.info,  Node: Platform Support Removals,  Next: API and Feature Removals<2>,  Prev: Deprecated functions and types of the C API,  Up: What's New In Python 3 7

1.2.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/tree/3.8/.travis.yml

   (2) 
https://github.com/python/cpython/tree/3.8/Tools/ssl/multissltests.py


File: python.info,  Node: API and Feature Removals<2>,  Next: Module Removals,  Prev: Platform Support Removals,  Up: What's New In Python 3 7

1.2.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(): 480. were deprecated in
     Python 3.5, and will now cause an error.

   * Removed support of the `exclude' argument in *note
     tarfile.TarFile.add(): 481.  It was deprecated in Python 2.7 and
     3.2.  Use the `filter' argument instead.

   * The ‘splitunc()’ function in the ‘ntpath’ module was deprecated in
     Python 3.1, and has now been removed.  Use the *note splitdrive():
     482. function instead.

   * *note collections.namedtuple(): 1b8. 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(): 184, *note float(): 188, *note list(): 263.
     and *note tuple(): 483. no longer take keyword arguments.  The
     first argument of *note int(): 185. can now be passed only as
     positional argument.

   * Removed previously deprecated in Python 2.4 classes ‘Plist’, ‘Dict’
     and ‘_InternalDict’ in the *note plistlib: d0. module.  Dict values
     in the result of functions *note readPlist(): 484. and *note
     readPlistFromBytes(): 485. 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(): 486. 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: a. no longer exports the *note selectors: e7. and
     ‘_overlapped’ modules as ‘asyncio.selectors’ and
     ‘asyncio._overlapped’.  Replace ‘from asyncio import selectors’
     with ‘import selectors’.

   * Direct instantiation of *note ssl.SSLSocket: 3e7. and *note
     ssl.SSLObject: 3e8. objects is now prohibited.  The constructors
     were never documented, tested, or designed as public constructors.
     Users were supposed to use *note ssl.wrap_socket(): 474. or *note
     ssl.SSLContext: 3e9.  (Contributed by Christian Heimes in
     bpo-32951(2).)

   * The unused *note distutils: 39. ‘install_misc’ command has been
     removed.  (Contributed by Eric N. Vander Weele in bpo-29218(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28638

   (2) https://bugs.python.org/issue32951

   (3) https://bugs.python.org/issue29218


File: python.info,  Node: Module Removals,  Next: Windows-only Changes,  Prev: API and Feature Removals<2>,  Up: What's New In Python 3 7

1.2.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/issue29137


File: python.info,  Node: Windows-only Changes,  Next: Porting to Python 3 7,  Prev: Module Removals,  Up: What's New In Python 3 7

1.2.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/issue30291

   (2) https://bugs.python.org/issue30362


File: python.info,  Node: Porting to Python 3 7,  Next: Notable changes in Python 3 7 1,  Prev: Windows-only Changes,  Up: What's New In Python 3 7

1.2.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<2>.
* Changes in the C API: Changes in the C API<2>.
* CPython bytecode changes: CPython bytecode changes<2>.
* 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<2>,  Up: Porting to Python 3 7

1.2.17.1 Changes in Python Behavior
...................................

   * *note async: 1a3. and *note await: 1a4. names are now reserved
     keywords.  Code using these names as identifiers will now raise a
     *note SyntaxError: 45d.  (Contributed by Jelle Zijlstra in
     bpo-30406(1).)

   * PEP 479(2) is enabled for all code in Python 3.7, meaning that
     *note StopIteration: 48b. exceptions raised directly or indirectly
     in coroutines and generators are transformed into *note
     RuntimeError: 2bb. exceptions.  (Contributed by Yury Selivanov in
     bpo-32670(3).)

   * *note object.__aiter__(): 48c. 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: 45d, 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: 33c. switch, the initial working directory
     is now added to *note sys.path: 48d, 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/issue30406

   (2) https://www.python.org/dev/peps/pep-0479

   (3) https://bugs.python.org/issue32670

   (4) https://bugs.python.org/issue31709

   (5) https://bugs.python.org/issue32012

   (6) https://bugs.python.org/issue32023


File: python.info,  Node: Changes in the Python API<2>,  Next: Changes in the C API<2>,  Prev: Changes in Python Behavior,  Up: Porting to Python 3 7

1.2.17.2 Changes in the Python API
..................................

   * ‘socketserver.ThreadingMixIn.server_close()’ now waits until all
     non-daemon threads complete.  Set the new
     ‘socketserver.ThreadingMixIn.block_on_close’ 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(): 48f. 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(): 490. now raises a *note ValueError:
     1fc. 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(): 491.
     is now *note positional-only: 2a8.  Passing it as a keyword
     argument was deprecated in Python 3.5.  (Contributed by Serhiy
     Storchaka in bpo-29193(7).)

   * Attributes *note key: 492, *note value: 493. and *note coded_value:
     494. of class *note http.cookies.Morsel: 495. are now read-only.
     Assigning to them was deprecated in Python 3.5.  Use the *note
     set(): 496. method for setting them.  (Contributed by Serhiy
     Storchaka in bpo-29192(8).)

   * The `mode' argument of *note os.makedirs(): 3c2. 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: 497. type is now *note str: 335.
     instead of *note bytes: 336.  (Contributed by Victor Stinner in
     bpo-21071(10).)

   * *note parse_multipart(): 2ef. 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: f0, calling *note
     socket.fromshare(): 498. on a socket created by *note socket.share:
     499. in older Python versions is not supported.

   * ‘repr’ for *note BaseException: 1a9. 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: 196. has changed to include
     the keyword arguments in the output.  (Contributed by Utkarsh
     Upadhyay in bpo-30302(13).)

   * Because *note shutil.rmtree(): 21d. is now implemented using the
     *note os.scandir(): 260. 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: 32a. 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: de.
     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: 32a. 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(): 480. 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’).

     (Contributed by Serhiy Storchaka in bpo-25054(16) and
     bpo-32308(17).)

   * Change *note re.escape(): 49a. 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: 404. frames are now sorted from oldest
     to most recent to be more consistent with *note traceback: 114.
     (Contributed by Jesse Bakker in bpo-32121(19).)

   * On OSes that support *note socket.SOCK_NONBLOCK: 49b. or *note
     socket.SOCK_CLOEXEC: 49c. bit flags, the *note socket.type: 49d. 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: 2ba. was changed from *note False: 38d. to *note
     True: 49e. when redirecting the standard handles.  If you
     previously depended on handles being inherited when using *note
     subprocess.Popen: 2ba. with standard io redirection, you will have
     to pass ‘close_fds=False’ to preserve the previous behaviour, or
     use *note STARTUPINFO.lpAttributeList: 49f.

   * *note importlib.machinery.PathFinder.invalidate_caches(): 4a0. –
     which implicitly affects *note importlib.invalidate_caches(): 4a1.
     – now deletes entries in *note sys.path_importer_cache: 4a2. which
     are set to ‘None’.  (Contributed by Brett Cannon in bpo-33169(21).)

   * In *note asyncio: a, *note loop.sock_recv(): 4a3, *note
     loop.sock_sendall(): 4a4, *note loop.sock_accept(): 4a5, *note
     loop.getaddrinfo(): 4a6, *note loop.getnameinfo(): 4a7. have been
     changed to be proper coroutine methods to match their
     documentation.  Previously, these methods returned *note
     asyncio.Future: 448. instances.  (Contributed by Yury Selivanov in
     bpo-32327(22).)

   * *note asyncio.Server.sockets: 4a8. 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: 497. is now a *note str: 335. instance instead
     of a *note bytes: 336. instance.  (Contributed by Victor Stinner in
     bpo-21071(24).)

   * *note argparse: 6. subparsers can now be made mandatory by passing
     ‘required=True’ to *note ArgumentParser.add_subparsers(): 4a9.
     (Contributed by Anthony Sottile in bpo-26510(25).)

   * *note ast.literal_eval(): 4aa. is now stricter.  Addition and
     subtraction of arbitrary numbers are no longer allowed.
     (Contributed by Serhiy Storchaka in bpo-31778(26).)

   * *note Calendar.itermonthdates: 4ab. 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: 4ac. and
     *note Calendar.itermonthdays4: 4ad. can be used.  The new methods
     return tuples and are not restricted by the range supported by
     *note datetime.date: 194.  (Contributed by Alexander Belopolsky in
     bpo-28292(27).)

   * *note collections.ChainMap: 4ae. now preserves the order of the
     underlying mappings.  (Contributed by Raymond Hettinger in
     bpo-32792(28).)

   * The ‘submit()’ method of *note
     concurrent.futures.ThreadPoolExecutor: 27b. and *note
     concurrent.futures.ProcessPoolExecutor: 2a5. now raises a *note
     RuntimeError: 2bb. if called during interpreter shutdown.
     (Contributed by Mark Nemec in bpo-33097(29).)

   * The *note configparser.ConfigParser: 4af. 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/issue31233

   (2) https://bugs.python.org/issue33540

   (3) https://bugs.python.org/issue31151

   (4) https://bugs.python.org/issue33540

   (5) https://bugs.python.org/issue31900

   (6) https://bugs.python.org/issue24744

   (7) https://bugs.python.org/issue29193

   (8) https://bugs.python.org/issue29192

   (9) https://bugs.python.org/issue19930

   (10) https://bugs.python.org/issue21071

   (11) https://bugs.python.org/issue29979

   (12) https://bugs.python.org/issue30399

   (13) https://bugs.python.org/issue30302

   (14) https://unicode.org/reports/tr18/

   (15) https://bugs.python.org/issue30349

   (16) https://bugs.python.org/issue25054

   (17) https://bugs.python.org/issue32308

   (18) https://bugs.python.org/issue29995

   (19) https://bugs.python.org/issue32121

   (20) https://bugs.python.org/issue32331

   (21) https://bugs.python.org/issue33169

   (22) https://bugs.python.org/issue32327

   (23) https://bugs.python.org/issue32662

   (24) https://bugs.python.org/issue21071

   (25) https://bugs.python.org/issue26510

   (26) https://bugs.python.org/issue31778

   (27) https://bugs.python.org/issue28292

   (28) https://bugs.python.org/issue32792

   (29) https://bugs.python.org/issue33097

   (30) https://bugs.python.org/issue23835


File: python.info,  Node: Changes in the C API<2>,  Next: CPython bytecode changes<2>,  Prev: Changes in the Python API<2>,  Up: Porting to Python 3 7

1.2.17.3 Changes in the C API
.............................

The function *note PySlice_GetIndicesEx(): 47d. is considered unsafe for
resizable sequences.  If the slice indices are not instances of *note
int: 185, 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(): 434. and *note
PySlice_AdjustIndices(): 435.  (Contributed by Serhiy Storchaka in
bpo-27867(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27867


File: python.info,  Node: CPython bytecode changes<2>,  Next: Windows-only Changes<2>,  Prev: Changes in the C API<2>,  Up: Porting to Python 3 7

1.2.17.4 CPython bytecode changes
.................................

There are two new opcodes: *note LOAD_METHOD: 4b2. and *note
CALL_METHOD: 4b3.  (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/issue26110

   (2) https://bugs.python.org/issue32550


File: python.info,  Node: Windows-only Changes<2>,  Next: Other CPython implementation changes,  Prev: CPython bytecode changes<2>,  Up: Porting to Python 3 7

1.2.17.5 Windows-only Changes
.............................

The file used to override *note sys.path: 48d. is now called
‘<python-executable>._pth’ instead of ‘'sys.path'’.  See *note Finding
modules: 4b5. for more information.  (Contributed by Steve Dower in
bpo-28137(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28137


File: python.info,  Node: Other CPython implementation changes,  Prev: Windows-only Changes<2>,  Up: Porting to Python 3 7

1.2.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:

   * *note PySys_AddWarnOptionUnicode(): 4b7. is not currently usable by
     embedding applications due to the requirement to create a Unicode
     object prior to calling ‘Py_Initialize’.  Use *note
     PySys_AddWarnOption(): 4b8. instead.

   * warnings filters added by an embedding application with *note
     PySys_AddWarnOption(): 4b8. 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: 4b9. to a value greater than one is
no longer sufficient to both emit *note BytesWarning: 4ba. 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://www.python.org/dev/peps/pep-0432

   (2) https://bugs.python.org/issue22257

   (3) https://bugs.python.org/issue25612


File: python.info,  Node: Notable changes in Python 3 7 1,  Next: Notable changes in Python 3 7 2,  Prev: Porting to Python 3 7,  Up: What's New In Python 3 7

1.2.18 Notable changes in Python 3.7.1
--------------------------------------

Starting in 3.7.1, *note Py_Initialize(): 43e. now consistently reads
and respects all of the same environment settings as *note Py_Main():
4bc. (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: 4bd. to 1 before calling *note
Py_Initialize(): 43e.

In 3.7.1 the C API for Context Variables *note was updated: 4be. to use
*note PyObject: 4bf. pointers.  See also bpo-34762(2).

In 3.7.1 the *note tokenize: 112. 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/issue34247

   (2) https://bugs.python.org/issue34762

   (3) https://bugs.python.org/issue33899


File: python.info,  Node: Notable changes in Python 3 7 2,  Next: Notable changes in Python 3 7 6,  Prev: Notable changes in Python 3 7 1,  Up: What's New In Python 3 7

1.2.19 Notable changes in Python 3.7.2
--------------------------------------

In 3.7.2, *note venv: 126. 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: Notable changes in Python 3 7 6,  Next: Notable changes in Python 3 7 10,  Prev: Notable changes in Python 3 7 2,  Up: What's New In Python 3 7

1.2.20 Notable changes in Python 3.7.6
--------------------------------------

Due to significant security concerns, the `reuse_address' parameter of
*note asyncio.loop.create_datagram_endpoint(): 2e8. 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/issue37228


File: python.info,  Node: Notable changes in Python 3 7 10,  Prev: Notable changes in Python 3 7 6,  Up: What's New In Python 3 7

1.2.21 Notable changes in Python 3.7.10
---------------------------------------

Earlier Python versions allowed using both ‘;’ and ‘&’ as query
parameter separators in *note urllib.parse.parse_qs(): 2ec. and *note
urllib.parse.parse_qsl(): 2ed.  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
*note cgi.parse(): 2ee. and *note cgi.parse_multipart(): 2ef. 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/issue42967


File: python.info,  Node: What's New In Python 3 6,  Next: Python 3 5 有什麼新功能,  Prev: What's New In Python 3 7,  Up: Python 有什麼新功能？

1.3 What’s New In Python 3.6
============================


Editors: 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<2>. Release highlights
* New Features: New Features<3>.
* Other Language Changes: Other Language Changes<3>.
* New Modules: New Modules<3>.
* Improved Modules: Improved Modules<3>.
* Optimizations: Optimizations<3>.
* Build and C API Changes: Build and C API Changes<2>.
* Other Improvements::
* Deprecated: Deprecated<2>.
* Removed::
* Porting to Python 3.6: Porting to Python 3 6.
* Notable changes in Python 3.6.2: Notable changes in Python 3 6 2.
* Notable changes in Python 3.6.4: Notable changes in Python 3 6 4.
* Notable changes in Python 3.6.5: Notable changes in Python 3 6 5.
* Notable changes in Python 3.6.7: Notable changes in Python 3 6 7.
* Notable changes in Python 3.6.10: Notable changes in Python 3 6 10.
* Notable changes in Python 3.6.13: Notable changes in Python 3 6 13.

   ---------- Footnotes ----------

   (1) https://docs.python.org/3.6/whatsnew/changelog.html

   (2) https://www.python.org/dev/peps/pep-0494


File: python.info,  Node: Summary -- Release highlights<2>,  Next: New Features<3>,  Up: What's New In Python 3 6

1.3.1 Summary – Release highlights
----------------------------------

New syntax features:

   * *note PEP 498: 4c6, formatted string literals.

   * *note PEP 515: 4c7, underscores in numeric literals.

   * *note PEP 526: 4c8, syntax for variable annotations.

   * *note PEP 525: 4c9, asynchronous generators.

   * *note PEP 530: 4ca.: asynchronous comprehensions.

New library modules:

   * *note secrets: e5.: *note PEP 506 – Adding A Secrets Module To The
     Standard Library: 4cb.

CPython implementation improvements:

   * The *note dict: 301. type has been reimplemented to use a *note
     more compact representation: 4cc. 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: 4cd.

   * The class attribute definition order is *note now preserved: 4ce.

   * The order of elements in ‘**kwargs’ now *note corresponds to the
     order: 4cf. in which keyword arguments were passed to the function.

   * DTrace and SystemTap *note probing support: 4d0. has been added.

   * The new *note PYTHONMALLOC: 4d1. environment variable can now be
     used to debug the interpreter memory allocation and access errors.

Significant improvements in the standard library:

   * The *note asyncio: a. 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: 4d2. has been implemented to
     support *note path-like objects: 36f.  All standard library
     functions operating on paths have been updated to work with the new
     protocol.

   * The *note datetime: 31. module has gained support for *note Local
     Time Disambiguation: 4d3.

   * The *note typing: 11a. module received a number of *note
     improvements: 4d4.

   * The *note tracemalloc: 115. module has been significantly reworked
     and is now used to provide better output for *note ResourceWarning:
     4d5. as well as provide better diagnostics for memory allocation
     errors.  See the *note PYTHONMALLOC section: 4d1. for more
     information.

Security improvements:

   * The new *note secrets: e5. 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(): 4d6. 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: 8d. and *note ssl: f4. modules now support
     OpenSSL 1.1.0.

   * The default settings and feature set of the *note ssl: f4. module
     have been improved.

   * The *note hashlib: 8d. module received support for the BLAKE2,
     SHA-3 and SHAKE hash algorithms and the *note scrypt(): 4d7. key
     derivation function.

Windows improvements:

   * *note PEP 528: 4d8. and *note PEP 529: 4d9, 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: 4da. 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: 4b5. for more information.

   * A ‘python36.zip’ file now works as a landmark to infer *note
     PYTHONHOME: 4db.  See *note the documentation: 4b5. 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://www.python.org/dev/peps/pep-0524


File: python.info,  Node: New Features<3>,  Next: Other Language Changes<3>,  Prev: Summary -- Release highlights<2>,  Up: What's New In Python 3 6

1.3.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<3>

1.3.2.1 PEP 498: Formatted string literals
..........................................

PEP 498(1) introduces a new kind of string literals: `f-strings', or
*note formatted string literals: 15d.

Formatted string literals are prefixed with ‘'f'’ and are similar to the
format strings accepted by *note str.format(): 4df.  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(): 4e0. 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.

     PEP written and implemented by Eric V. Smith.

*note Feature documentation: 15d.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0498

   (2) https://www.python.org/dev/peps/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<3>

1.3.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://www.python.org/dev/peps/pep-0484

   (2) https://www.python.org/dev/peps/pep-0526

   (3) http://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<3>

1.3.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: 4e3. 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

     PEP written by Georg Brandl and Serhiy Storchaka.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0515

   (2) https://www.python.org/dev/peps/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<3>

1.3.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

     PEP written and implemented by Yury Selivanov.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0492

   (2) https://www.python.org/dev/peps/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<3>

1.3.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

     PEP written and implemented by Yury Selivanov.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0530

   (2) https://www.python.org/dev/peps/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<3>

1.3.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(): 4e7. calls to work
correctly from *note __init_subclass__(): 4e8. implementations, custom
metaclasses must ensure that the new ‘__classcell__’ namespace entry is
propagated to ‘type.__new__’ (as described in *note Creating the class
object: 4e9.).

也參考
......

PEP 487(1) – Simpler customization of class creation

     PEP written and implemented by Martin Teichmann.

*note Feature documentation: 4ea.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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<3>

1.3.2.7 PEP 487: Descriptor Protocol Enhancements
.................................................

PEP 487(1) extends the descriptor protocol to include the new optional
*note __set_name__(): 4ed. 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

     PEP written and implemented by Martin Teichmann.

*note Feature documentation: 4ee.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0487

   (2) https://www.python.org/dev/peps/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<3>

1.3.2.8 PEP 519: Adding a file system path protocol
...................................................

File system paths have historically been represented as *note str: 335.
or *note bytes: 336. 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: 185. 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: c9. from working with pre-existing
code, including Python’s standard library.

To fix this situation, a new interface represented by *note os.PathLike:
4f0. has been defined.  By implementing the *note __fspath__(): 4f1.
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:
335. or *note bytes: 336. object.  This means an object is considered
*note path-like: 36f. if it implements *note os.PathLike: 4f0. or is a
*note str: 335. or *note bytes: 336. object which represents a file
system path.  Code can use *note os.fspath(): 4f2, *note os.fsdecode():
4f3, or *note os.fsencode(): 4f4. to explicitly get a *note str: 335.
and/or *note bytes: 336. representation of a path-like object.

The built-in *note open(): 4f5. function has been updated to accept
*note os.PathLike: 4f0. objects, as have all relevant functions in the
*note os: c5. and *note os.path: c6. modules, and most other functions
and classes in the standard library.  The *note os.DirEntry: 4f6. class
and relevant classes in *note pathlib: c9. have also been updated to
implement *note os.PathLike: 4f0.

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: 36f. without any code changes, or at least
very minimal ones (e.g.  calling *note os.fspath(): 4f2. 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: 202. 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

     PEP written by Brett Cannon and Koos Zevenhoven.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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<3>

1.3.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: 195. and *note datetime.time: 4f8. 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: 4f9. 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://www.python.org/dev/peps/pep-0495

   (2) https://www.python.org/dev/peps/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<3>

1.3.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(): 4fb, which now defaults
to ‘'utf-8'’.

Applications that do not use str to represent paths should use *note
os.fsencode(): 4f4. and *note os.fsdecode(): 4f3. to ensure their bytes
are correctly encoded.  To revert to the previous behaviour, set *note
PYTHONLEGACYWINDOWSFSENCODING: 4fc. or call *note
sys._enablelegacywindowsfsencoding(): 4fd.

See PEP 529(1) for more information and discussion of code modifications
that may be required.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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<3>

1.3.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: 4ff.

也參考
......

PEP 528(1) – Change Windows console encoding to UTF-8

     PEP written and implemented by Steve Dower.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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<3>

1.3.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__: 501. attribute.

Also, the effective default class `execution' namespace (returned from
*note type.__prepare__(): 502.) is now an insertion-order-preserving
mapping.

也參考
......

PEP 520(1) – Preserving Class Attribute Definition Order

     PEP written and implemented by Eric Snow.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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<3>

1.3.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

     PEP written and implemented by Eric Snow.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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<3>

1.3.2.14 New dict implementation
................................

The *note dict: 301. 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(): 1b9. 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/issue27350

   (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<3>

1.3.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

     PEP written by Brett Cannon and Dino Viehland.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0523

   (2) https://www.python.org/dev/peps/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<3>

1.3.2.16 PYTHONMALLOC environment variable
..........................................

The new *note PYTHONMALLOC: 508. 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(): 509. called on a memory block allocated by
     *note PyMem_Malloc(): 50a.

   * 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: 50b. is held when allocator functions of
     *note PYMEM_DOMAIN_OBJ: 50c. (ex: *note PyObject_Malloc(): 50d.)
     and *note PYMEM_DOMAIN_MEM: 50e. (ex: *note PyMem_Malloc(): 50a.)
     domains are called.

Checking if the GIL is held is also a new feature of Python 3.6.

See the *note PyMem_SetupDebugHooks(): 50f. 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: 115. 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__
       ...

(Contributed by Victor Stinner in bpo-26516(1) and bpo-26564(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26516

   (2) https://bugs.python.org/issue26564


File: python.info,  Node: DTrace and SystemTap probing support,  Prev: PYTHONMALLOC environment variable,  Up: New Features<3>

1.3.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 debug builds or providing
application-specific profiling/debugging code.

More details in *note Instrumenting CPython with DTrace and SystemTap:
511.

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/issue21590


File: python.info,  Node: Other Language Changes<3>,  Next: New Modules<3>,  Prev: New Features<3>,  Up: What's New In Python 3 6

1.3.3 Other Language Changes
----------------------------

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: 192.

   * It is now possible to set a *note special method: 513. to ‘None’ to
     indicate that the corresponding operation is not available.  For
     example, if a class sets *note __iter__(): 514. 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: 515. for an example).  (Contributed by Emanuel Barry in
     bpo-26823(2).)

   * Import now raises the new exception *note ModuleNotFoundError: 39f.
     (subclass of *note ImportError: 339.) 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/issue25958

   (2) https://bugs.python.org/issue26823

   (3) https://bugs.python.org/issue15767

   (4) https://bugs.python.org/issue23722


File: python.info,  Node: New Modules<3>,  Next: Improved Modules<3>,  Prev: Other Language Changes<3>,  Up: What's New In Python 3 6

1.3.4 New Modules
-----------------

* Menu:

* secrets::


File: python.info,  Node: secrets,  Up: New Modules<3>

1.3.4.1 secrets
...............

The main purpose of the new *note secrets: e5. 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:
     dd. module should `NOT' be used for security purposes.  Use *note
     secrets: e5. on Python 3.6+ and *note os.urandom(): 4d6. on Python
     3.5 and earlier.

也參考
......

PEP 506(1) – Adding A Secrets Module To The Standard Library

     PEP written and implemented by Steven D’Aprano.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0506


File: python.info,  Node: Improved Modules<3>,  Next: Optimizations<3>,  Prev: New Modules<3>,  Up: What's New In Python 3 6

1.3.5 Improved Modules
----------------------

* Menu:

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


File: python.info,  Node: array,  Next: ast<2>,  Up: Improved Modules<3>

1.3.5.1 array
.............

Exhausted iterators of *note array.array: 456. 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/issue26492


File: python.info,  Node: ast<2>,  Next: asyncio<4>,  Prev: array,  Up: Improved Modules<3>

1.3.5.2 ast
...........

The new ‘ast.Constant’ 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/issue26146


File: python.info,  Node: asyncio<4>,  Next: binascii<2>,  Prev: ast<2>,  Up: Improved Modules<3>

1.3.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: a. module since Python 3.5.0 (all
backported to 3.5.x due to the provisional status):

   * The *note get_event_loop(): 35a. 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(): 51c. function and all functions that use
     it, such as *note loop.run_until_complete(): 51d, now accept all
     kinds of *note awaitable objects: 51e.  (Contributed by Yury
     Selivanov.)

   * New *note run_coroutine_threadsafe(): 51f. function to submit
     coroutines to event loops from other threads.  (Contributed by
     Vincent Michel.)

   * New *note Transport.is_closing(): 520. method to check if the
     transport is closing or closed.  (Contributed by Yury Selivanov.)

   * The *note loop.create_server(): 362. method can now accept a list
     of hosts.  (Contributed by Yann Sionneau.)

   * New *note loop.create_future(): 521. method to create Future
     objects.  This allows alternative event loop implementations, such
     as uvloop(2), to provide a faster *note asyncio.Future: 448.
     implementation.  (Contributed by Yury Selivanov in bpo-27041(3).)

   * New *note loop.get_exception_handler(): 522. method to get the
     current exception handler.  (Contributed by Yury Selivanov in
     bpo-27040(4).)

   * New *note StreamReader.readuntil(): 523. method to read data from
     the stream until a separator bytes sequence appears.  (Contributed
     by Mark Korenberg.)

   * The performance of *note StreamReader.readexactly(): 524. has been
     improved.  (Contributed by Mark Korenberg in bpo-28370(5).)

   * The *note loop.getaddrinfo(): 4a6. 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(): 525. 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: 193. when
     passed an instance of the *note StopIteration: 48b. exception.
     (Contributed by Chris Angelico in bpo-26221(7).)

   * New *note loop.connect_accepted_socket(): 36a. 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(): 526. to properly close pending
     asynchronous generators before closing the loop.  (Contributed by
     Yury Selivanov in bpo-28003(10).)

   * *note Future: 448. and *note Task: 1ae. 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/issue28613

   (2) https://github.com/MagicStack/uvloop

   (3) https://bugs.python.org/issue27041

   (4) https://bugs.python.org/issue27040

   (5) https://bugs.python.org/issue28370

   (6) https://bugs.python.org/issue25593

   (7) https://bugs.python.org/issue26221

   (8) https://bugs.python.org/issue27392

   (9) https://bugs.python.org/issue27456

   (10) https://bugs.python.org/issue28003

   (11) https://bugs.python.org/issue26081

   (12) https://bugs.python.org/issue28544


File: python.info,  Node: binascii<2>,  Next: cmath,  Prev: asyncio<4>,  Up: Improved Modules<3>

1.3.5.4 binascii
................

The *note b2a_base64(): 528. 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/issue25357


File: python.info,  Node: cmath,  Next: collections<4>,  Prev: binascii<2>,  Up: Improved Modules<3>

1.3.5.5 cmath
.............

The new *note cmath.tau: 52a. (`τ') constant has been added.
(Contributed by Lisa Roach in bpo-12345(1), see PEP 628(2) for details.)

New constants: *note cmath.inf: 52b. and *note cmath.nan: 52c. to match
*note math.inf: 52d. and *note math.nan: 52e, and also *note cmath.infj:
52f. and *note cmath.nanj: 530. to match the format used by complex
repr.  (Contributed by Mark Dickinson in bpo-23229(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue12345

   (2) https://www.python.org/dev/peps/pep-0628

   (3) https://bugs.python.org/issue23229


File: python.info,  Node: collections<4>,  Next: concurrent futures<2>,  Prev: cmath,  Up: Improved Modules<3>

1.3.5.6 collections
...................

The new *note Collection: 532. 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: 533. abstract base class represents iterable
classes that also provide the *note __reversed__(): 534. method.
(Contributed by Ivan Levkivskyi in bpo-25987(2).)

The new *note AsyncGenerator: 535. abstract base class represents
asynchronous generators.  (Contributed by Yury Selivanov in
bpo-28720(3).)

The *note namedtuple(): 1b8. 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(): 1b8. are
now keyword-only.  (Contributed by Raymond Hettinger in bpo-25628(5).)

Recursive *note collections.deque: 536. instances can now be pickled.
(Contributed by Serhiy Storchaka in bpo-26482(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27598

   (2) https://bugs.python.org/issue25987

   (3) https://bugs.python.org/issue28720

   (4) https://bugs.python.org/issue17941

   (5) https://bugs.python.org/issue25628

   (6) https://bugs.python.org/issue26482


File: python.info,  Node: concurrent futures<2>,  Next: contextlib<2>,  Prev: collections<4>,  Up: Improved Modules<3>

1.3.5.7 concurrent.futures
..........................

The *note ThreadPoolExecutor: 27b. 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/issue27664


File: python.info,  Node: contextlib<2>,  Next: datetime<3>,  Prev: concurrent futures<2>,  Up: Improved Modules<3>

1.3.5.8 contextlib
..................

The *note contextlib.AbstractContextManager: 539. 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: 11a. module as *note typing.ContextManager:
53a.  (Contributed by Brett Cannon in bpo-25609(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25609


File: python.info,  Node: datetime<3>,  Next: decimal<2>,  Prev: contextlib<2>,  Up: Improved Modules<3>

1.3.5.9 datetime
................

The *note datetime: 195. and *note time: 4f8. classes have the new
‘fold’ attribute used to disambiguate local time when necessary.  Many
functions in the *note datetime: 31. have been updated to support local
time disambiguation.  See *note Local Time Disambiguation: 4d3. section
for more information.  (Contributed by Alexander Belopolsky in
bpo-24773(1).)

The *note datetime.strftime(): 53c. and *note date.strftime(): 53d.
methods now support ISO 8601 date directives ‘%G’, ‘%u’ and ‘%V’.
(Contributed by Ashley Anderson in bpo-12006(2).)

The *note datetime.isoformat(): 384. 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(): 53e. now accepts an optional `tzinfo'
argument.  (Contributed by Alexander Belopolsky in bpo-27661(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue24773

   (2) https://bugs.python.org/issue12006

   (3) https://bugs.python.org/issue19475

   (4) https://bugs.python.org/issue27661


File: python.info,  Node: decimal<2>,  Next: distutils<2>,  Prev: datetime<3>,  Up: Improved Modules<3>

1.3.5.10 decimal
................

New *note Decimal.as_integer_ratio(): 540. method that returns a pair
‘(n, d)’ of integers that represent the given *note Decimal: 189.
instance as a fraction, in lowest terms and with a positive denominator:

     >>> Decimal('-3.14').as_integer_ratio()
     (-157, 50)

(Contributed by Stefan Krah amd Mark Dickinson in bpo-25928(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25928


File: python.info,  Node: distutils<2>,  Next: email,  Prev: decimal<2>,  Up: Improved Modules<3>

1.3.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/issue27819


File: python.info,  Node: email,  Next: encodings,  Prev: distutils<2>,  Up: Improved Modules<3>

1.3.5.12 email
..............

The new email API, enabled via the `policy' keyword to various
constructors, is no longer provisional.  The *note email: 69.
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: 73. classes now all accept an optional `policy'
keyword.  (Contributed by Berker Peksag in bpo-27331(2).)

The *note DecodedGenerator: 543. now supports the `policy' keyword.

There is a new *note policy: 75. attribute, *note message_factory: 544,
that controls what class is used by default when the parser creates new
message objects.  For the *note email.policy.compat32: 545. policy this
is *note Message: 546, for the new policies it is *note EmailMessage:
547.  (Contributed by R. David Murray in bpo-20476(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue24277

   (2) https://bugs.python.org/issue27331

   (3) https://bugs.python.org/issue20476


File: python.info,  Node: encodings,  Next: enum<3>,  Prev: email,  Up: Improved Modules<3>

1.3.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/issue27959


File: python.info,  Node: enum<3>,  Next: faulthandler,  Prev: encodings,  Up: Improved Modules<3>

1.3.5.14 enum
.............

Two new enumeration base classes have been added to the *note enum: 7b.
module: *note Flag: 54a. 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: 54b. 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/issue23591


File: python.info,  Node: faulthandler,  Next: fileinput,  Prev: enum<3>,  Up: Improved Modules<3>

1.3.5.15 faulthandler
.....................

On Windows, the *note faulthandler: 7d. module now installs a handler
for Windows exceptions: see *note faulthandler.enable(): 54d.
(Contributed by Victor Stinner in bpo-23848(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23848


File: python.info,  Node: fileinput,  Next: hashlib,  Prev: faulthandler,  Up: Improved Modules<3>

1.3.5.16 fileinput
..................

*note hook_encoded(): 54f. now supports the `errors' argument.
(Contributed by Joseph Hackman in bpo-25788(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25788


File: python.info,  Node: hashlib,  Next: http client<2>,  Prev: fileinput,  Up: Improved Modules<3>

1.3.5.17 hashlib
................

*note hashlib: 8d. 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(): 551.
and *note blake2s(): 552. 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 ‘sha3_224()’, ‘sha3_256()’, ‘sha3_384()’,
‘sha3_512()’, and SHAKE hash functions ‘shake_128()’ and ‘shake_256()’
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(): 4d7. is now
available with OpenSSL 1.1.0 and newer.  (Contributed by Christian
Heimes in bpo-27928(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26470

   (2) https://bugs.python.org/issue26798

   (3) https://bugs.python.org/issue16113

   (4) https://bugs.python.org/issue27928


File: python.info,  Node: http client<2>,  Next: idlelib and IDLE<2>,  Prev: hashlib,  Up: Improved Modules<3>

1.3.5.18 http.client
....................

*note HTTPConnection.request(): 554. and *note endheaders(): 555. both
now support chunked encoding request bodies.  (Contributed by Demian
Brecht and Rolf Krahl in bpo-12319(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue12319


File: python.info,  Node: idlelib and IDLE<2>,  Next: importlib<3>,  Prev: http client<2>,  Up: Improved Modules<3>

1.3.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/issue24225

   (2) https://bugs.python.org/issue15786

   (3) https://bugs.python.org/issue1612262

   (4) https://bugs.python.org/issue27099

   (5) https://bugs.python.org/issue13802

   (6) https://bugs.python.org/issue31860

   (7) https://bugs.python.org/issue33642

   (8) https://bugs.python.org/issue33768

   (9) https://bugs.python.org/issue33679

   (10) https://bugs.python.org/issue33656

   (11) https://bugs.python.org/issue1529353


File: python.info,  Node: importlib<3>,  Next: inspect<2>,  Prev: idlelib and IDLE<2>,  Up: Improved Modules<3>

1.3.5.20 importlib
..................

Import now raises the new exception *note ModuleNotFoundError: 39f.
(subclass of *note ImportError: 339.) 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: 558. now calls *note create_module():
559. on the wrapped loader, removing the restriction that *note
importlib.machinery.BuiltinImporter: 55a. and *note
importlib.machinery.ExtensionFileLoader: 55b. couldn’t be used with
*note importlib.util.LazyLoader: 558.

*note importlib.util.cache_from_source(): 55c, *note
importlib.util.source_from_cache(): 55d, and *note
importlib.util.spec_from_file_location(): 55e. now accept a *note
path-like object: 36f.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue15767


File: python.info,  Node: inspect<2>,  Next: json,  Prev: importlib<3>,  Up: Improved Modules<3>

1.3.5.21 inspect
................

The *note inspect.signature(): 560. 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 *note
inspect.getargspec(): 561. API, the previously documented deprecation of
*note inspect.getfullargspec(): 562. has been reversed.  While this
function is convenient for single/source Python 2/3 code bases, the
richer *note inspect.signature(): 560. interface remains the recommended
approach for new code.  (Contributed by Nick Coghlan in bpo-27172(2))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue19611

   (2) https://bugs.python.org/issue27172


File: python.info,  Node: json,  Next: logging<3>,  Prev: inspect<2>,  Up: Improved Modules<3>

1.3.5.22 json
.............

*note json.load(): 564. and *note json.loads(): 565. 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/issue17909


File: python.info,  Node: logging<3>,  Next: math<3>,  Prev: json,  Up: Improved Modules<3>

1.3.5.23 logging
................

The new *note WatchedFileHandler.reopenIfNeeded(): 567. 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/issue24884


File: python.info,  Node: math<3>,  Next: multiprocessing<3>,  Prev: logging<3>,  Up: Improved Modules<3>

1.3.5.24 math
.............

The tau (`τ') constant has been added to the *note math: b2. and *note
cmath: 19. modules.  (Contributed by Lisa Roach in bpo-12345(1), see PEP
628(2) for details.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue12345

   (2) https://www.python.org/dev/peps/pep-0628


File: python.info,  Node: multiprocessing<3>,  Next: os<3>,  Prev: math<3>,  Up: Improved Modules<3>

1.3.5.25 multiprocessing
........................

*note Proxy Objects: 56a. returned by ‘multiprocessing.Manager()’ can
now be nested.  (Contributed by Davin Potts in bpo-6766(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue6766


File: python.info,  Node: os<3>,  Next: pathlib<3>,  Prev: multiprocessing<3>,  Up: Improved Modules<3>

1.3.5.26 os
...........

See the summary of *note PEP 519: 4d2. for details on how the *note os:
c5. and *note os.path: c6. modules now support *note path-like objects:
36f.

*note scandir(): 260. now supports *note bytes: 336. paths on Windows.

A new *note close(): 56c. method allows explicitly closing a *note
scandir(): 260. iterator.  The *note scandir(): 260. iterator now
supports the *note context manager: 56d. protocol.  If a ‘scandir()’
iterator is neither exhausted nor explicitly closed a *note
ResourceWarning: 4d5. will be emitted in its destructor.  (Contributed
by Serhiy Storchaka in bpo-25994(1).)

On Linux, *note os.urandom(): 4d6. 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(): 56e. function.  (Contributed by Victor
Stinner, part of the PEP 524(3))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25994

   (2) https://www.python.org/dev/peps/pep-0524

   (3) https://www.python.org/dev/peps/pep-0524


File: python.info,  Node: pathlib<3>,  Next: pdb<2>,  Prev: os<3>,  Up: Improved Modules<3>

1.3.5.27 pathlib
................

*note pathlib: c9. now supports *note path-like objects: 36f.
(Contributed by Brett Cannon in bpo-27186(1).)

See the summary of *note PEP 519: 4d2. for details.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27186


File: python.info,  Node: pdb<2>,  Next: pickle<2>,  Prev: pathlib<3>,  Up: Improved Modules<3>

1.3.5.28 pdb
............

The *note Pdb: 571. 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<2>,  Up: Improved Modules<3>

1.3.5.29 pickle
...............

Objects that need ‘__new__’ called with keyword arguments can now be
pickled using *note pickle protocols: 573. 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/issue24164


File: python.info,  Node: pickletools,  Next: pydoc<2>,  Prev: pickle<2>,  Up: Improved Modules<3>

1.3.5.30 pickletools
....................

*note pickletools.dis(): 575. now outputs the implicit memo index for
the ‘MEMOIZE’ opcode.  (Contributed by Serhiy Storchaka in
bpo-25382(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25382


File: python.info,  Node: pydoc<2>,  Next: random,  Prev: pickletools,  Up: Improved Modules<3>

1.3.5.31 pydoc
..............

The *note pydoc: da. module has learned to respect the ‘MANPAGER’
environment variable.  (Contributed by Matthias Klose in bpo-8637(1).)

*note help(): 577. and *note pydoc: da. 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/issue8637

   (2) https://bugs.python.org/issue24879


File: python.info,  Node: random,  Next: re<2>,  Prev: pydoc<2>,  Up: Improved Modules<3>

1.3.5.32 random
...............

The new *note choices(): 579. 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/issue18844


File: python.info,  Node: re<2>,  Next: readline,  Prev: random,  Up: Improved Modules<3>

1.3.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).)

‘Match’ objects now support *note index-like objects: 18b. as group
indices.  (Contributed by Jeroen Demeyer and Xiang Zhang in
bpo-27177(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue433028

   (2) https://bugs.python.org/issue24454

   (3) https://bugs.python.org/issue27177


File: python.info,  Node: readline,  Next: rlcompleter,  Prev: re<2>,  Up: Improved Modules<3>

1.3.5.34 readline
.................

Added *note set_auto_history(): 57c. 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/issue26870


File: python.info,  Node: rlcompleter,  Next: shlex<2>,  Prev: readline,  Up: Improved Modules<3>

1.3.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/issue25011

   (2) https://bugs.python.org/issue25209


File: python.info,  Node: shlex<2>,  Next: site,  Prev: rlcompleter,  Up: Improved Modules<3>

1.3.5.36 shlex
..............

The *note shlex: 57f. has much *note improved shell compatibility: 580.
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/issue1521950


File: python.info,  Node: site,  Next: sqlite3<2>,  Prev: shlex<2>,  Up: Improved Modules<3>

1.3.5.37 site
.............

When specifying paths to add to *note sys.path: 48d. 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/issue26587


File: python.info,  Node: sqlite3<2>,  Next: socket<4>,  Prev: site,  Up: Improved Modules<3>

1.3.5.38 sqlite3
................

*note sqlite3.Cursor.lastrowid: 583. now supports the ‘REPLACE’
statement.  (Contributed by Alex LordThorsen in bpo-16864(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16864


File: python.info,  Node: socket<4>,  Next: socketserver<2>,  Prev: sqlite3<2>,  Up: Improved Modules<3>

1.3.5.39 socket
...............

The *note ioctl(): 585. function now supports the *note
SIO_LOOPBACK_FAST_PATH: 586. control code.  (Contributed by Daniel
Stokes in bpo-26536(1).)

The *note getsockopt(): 587. constants ‘SO_DOMAIN’, ‘SO_PROTOCOL’,
‘SO_PEERSEC’, and ‘SO_PASSSEC’ are now supported.  (Contributed by
Christian Heimes in bpo-26907(2).)

The *note setsockopt(): 588. 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: 589. to
interface with Linux Kernel crypto API. ‘ALG_*’, ‘SOL_ALG’ and *note
sendmsg_afalg(): 58a. 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, issue:‘26273’).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26536

   (2) https://bugs.python.org/issue26907

   (3) https://bugs.python.org/issue27744

   (4) https://bugs.python.org/issue27744


File: python.info,  Node: socketserver<2>,  Next: ssl<4>,  Prev: socket<4>,  Up: Improved Modules<3>

1.3.5.40 socketserver
.....................

Servers based on the *note socketserver: f1. module, including those
defined in *note http.server: 97, *note xmlrpc.server: 141. and *note
wsgiref.simple_server: 130, now support the *note context manager: 56d.
protocol.  (Contributed by Aviv Palivoda in bpo-26404(1).)

The ‘wfile’ attribute of *note StreamRequestHandler: 58c. classes now
implements the *note io.BufferedIOBase: 58d. writable interface.  In
particular, calling *note write(): 58e. is now guaranteed to send the
data in full.  (Contributed by Martin Panter in bpo-26721(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26404

   (2) https://bugs.python.org/issue26721


File: python.info,  Node: ssl<4>,  Next: statistics<2>,  Prev: socketserver<2>,  Up: Improved Modules<3>

1.3.5.41 ssl
............

*note ssl: f4. 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: 3e9. 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: 590. 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(): 591. 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: 592. and
‘IntFlags’.  (Contributed by Christian Heimes in bpo-28025(6).)

Server and client-side specific TLS protocols for *note SSLContext: 3e9.
were added.  (Contributed by Christian Heimes in bpo-28085(7).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26470

   (2) https://bugs.python.org/issue27850

   (3) https://bugs.python.org/issue27766

   (4) https://bugs.python.org/issue28043

   (5) https://bugs.python.org/issue19500

   (6) https://bugs.python.org/issue28025

   (7) https://bugs.python.org/issue28085


File: python.info,  Node: statistics<2>,  Next: struct,  Prev: ssl<4>,  Up: Improved Modules<3>

1.3.5.42 statistics
...................

A new *note harmonic_mean(): 594. function has been added.  (Contributed
by Steven D’Aprano in bpo-27181(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27181


File: python.info,  Node: struct,  Next: subprocess<2>,  Prev: statistics<2>,  Up: Improved Modules<3>

1.3.5.43 struct
...............

*note struct: f9. 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/issue11734


File: python.info,  Node: subprocess<2>,  Next: sys<4>,  Prev: struct,  Up: Improved Modules<3>

1.3.5.44 subprocess
...................

*note subprocess.Popen: 2ba. destructor now emits a *note
ResourceWarning: 4d5. warning if the child process is still running.
Use the context manager protocol (‘with proc: ...’) or explicitly call
the *note wait(): 597. method to read the exit status of the child
process.  (Contributed by Victor Stinner in bpo-26741(1).)

The *note subprocess.Popen: 2ba. 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/issue26741

   (2) https://bugs.python.org/issue6135


File: python.info,  Node: sys<4>,  Next: telnetlib,  Prev: subprocess<2>,  Up: Improved Modules<3>

1.3.5.45 sys
............

The new *note getfilesystemencodeerrors(): 599. 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(): 59a.
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/issue27781

   (2) https://bugs.python.org/issue27932


File: python.info,  Node: telnetlib,  Next: time<3>,  Prev: sys<4>,  Up: Improved Modules<3>

1.3.5.46 telnetlib
..................

*note Telnet: 59c. is now a context manager (contributed by Stéphane
Wirtel in bpo-25485(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25485


File: python.info,  Node: time<3>,  Next: timeit,  Prev: telnetlib,  Up: Improved Modules<3>

1.3.5.47 time
.............

The *note struct_time: 59e. attributes ‘tm_gmtoff’ and ‘tm_zone’ are now
available on all platforms.


File: python.info,  Node: timeit,  Next: tkinter<3>,  Prev: time<3>,  Up: Improved Modules<3>

1.3.5.48 timeit
...............

The new *note Timer.autorange(): 5a0. convenience method has been added
to call *note Timer.timeit(): 5a1. 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: 10c. 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/issue6422

   (2) https://bugs.python.org/issue23552


File: python.info,  Node: tkinter<3>,  Next: traceback,  Prev: timeit,  Up: Improved Modules<3>

1.3.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/issue22115


File: python.info,  Node: traceback,  Next: tracemalloc<2>,  Prev: tkinter<3>,  Up: Improved Modules<3>

1.3.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

(Contributed by Emanuel Barry in bpo-26823(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26823


File: python.info,  Node: tracemalloc<2>,  Next: typing<2>,  Prev: traceback,  Up: Improved Modules<3>

1.3.5.51 tracemalloc
....................

The *note tracemalloc: 115. module now supports tracing memory
allocations in multiple different address spaces.

The new *note DomainFilter: 5a5. filter class has been added to filter
block traces by their address space (domain).

(Contributed by Victor Stinner in bpo-26588(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26588


File: python.info,  Node: typing<2>,  Next: unicodedata<3>,  Prev: tracemalloc<2>,  Up: Improved Modules<3>

1.3.5.52 typing
...............

Since the *note typing: 11a. module is *note provisional: 34d, all
changes introduced in Python 3.6 have also been backported to Python
3.5.x.

The *note typing: 11a. 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: 53a. class has been added for
representing *note contextlib.AbstractContextManager: 539.  (Contributed
by Brett Cannon in bpo-25609(2).)

The *note typing.Collection: 5a7. class has been added for representing
*note collections.abc.Collection: 532.  (Contributed by Ivan Levkivskyi
in bpo-27598(3).)

The *note typing.ClassVar: 5a8. 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: 5a9. 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(): 5aa. 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/issue25609

   (3) https://bugs.python.org/issue27598

   (4) https://www.python.org/dev/peps/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<3>,  Next: unittest mock<2>,  Prev: typing<2>,  Up: Improved Modules<3>

1.3.5.53 unicodedata
....................

The *note unicodedata: 11b. module now uses data from Unicode 9.0.0(1).
(Contributed by Benjamin Peterson.)

   ---------- Footnotes ----------

   (1) http://unicode.org/versions/Unicode9.0.0/


File: python.info,  Node: unittest mock<2>,  Next: urllib request,  Prev: unicodedata<3>,  Up: Improved Modules<3>

1.3.5.54 unittest.mock
......................

The *note Mock: 24a. class has the following improvements:

   * Two new methods, *note Mock.assert_called(): 5ad. and *note
     Mock.assert_called_once(): 5ae. to check if the mock object was
     called.  (Contributed by Amit Saha in bpo-26323(1).)

   * The *note Mock.reset_mock(): 5af. 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/issue26323

   (2) https://bugs.python.org/issue21271


File: python.info,  Node: urllib request,  Next: urllib robotparser,  Prev: unittest mock<2>,  Up: Improved Modules<3>

1.3.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/issue12319


File: python.info,  Node: urllib robotparser,  Next: venv<2>,  Prev: urllib request,  Up: Improved Modules<3>

1.3.5.56 urllib.robotparser
...........................

*note RobotFileParser: 5b2. now supports the ‘Crawl-delay’ and
‘Request-rate’ extensions.  (Contributed by Nikolay Bogoychev in
bpo-16099(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16099


File: python.info,  Node: venv<2>,  Next: warnings<2>,  Prev: urllib robotparser,  Up: Improved Modules<3>

1.3.5.57 venv
.............

*note venv: 126. 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/issue22829


File: python.info,  Node: warnings<2>,  Next: winreg,  Prev: venv<2>,  Up: Improved Modules<3>

1.3.5.58 warnings
.................

A new optional `source' parameter has been added to the *note
warnings.warn_explicit(): 5b5. function: the destroyed object which
emitted a *note ResourceWarning: 4d5.  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: 4d5. warning is logged, the *note
tracemalloc: 115. 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: 115. is tracing Python memory allocations and if the
*note warnings: 127. module was already imported.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26568

   (2) https://bugs.python.org/issue26567


File: python.info,  Node: winreg,  Next: winsound,  Prev: warnings<2>,  Up: Improved Modules<3>

1.3.5.59 winreg
...............

Added the 64-bit integer type *note REG_QWORD: 5b7.  (Contributed by
Clement Rouault in bpo-23026(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23026


File: python.info,  Node: winsound,  Next: xmlrpc client,  Prev: winreg,  Up: Improved Modules<3>

1.3.5.60 winsound
.................

Allowed keyword arguments to be passed to *note Beep: 5b9, *note
MessageBeep: 5ba, and *note PlaySound: 5bb. (bpo-27982(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27982


File: python.info,  Node: xmlrpc client,  Next: zipfile<2>,  Prev: winsound,  Up: Improved Modules<3>

1.3.5.61 xmlrpc.client
......................

The *note xmlrpc.client: 140. 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/issue26885


File: python.info,  Node: zipfile<2>,  Next: zlib,  Prev: xmlrpc client,  Up: Improved Modules<3>

1.3.5.62 zipfile
................

A new *note ZipInfo.from_file(): 5be. class method allows making a *note
ZipInfo: 5bf. instance from a filesystem file.  A new *note
ZipInfo.is_dir(): 5c0. method can be used to check if the *note ZipInfo:
5bf. instance represents a directory.  (Contributed by Thomas Kluyver in
bpo-26039(1).)

The *note ZipFile.open(): 5c1. 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/issue26039

   (2) https://bugs.python.org/issue26039


File: python.info,  Node: zlib,  Prev: zipfile<2>,  Up: Improved Modules<3>

1.3.5.63 zlib
.............

The *note compress(): 5c3. and *note decompress(): 5c4. 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/issue26243

   (2) https://bugs.python.org/issue16764


File: python.info,  Node: Optimizations<3>,  Next: Build and C API Changes<2>,  Prev: Improved Modules<3>,  Up: What's New In Python 3 6

1.3.6 Optimizations
-------------------

   * 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: 448. class now has an optimized C
     implementation.  (Contributed by Yury Selivanov and INADA Naoki in
     bpo-26081(3).)

   * The *note asyncio.Task: 1ae. class now has an optimized C
     implementation.  (Contributed by Yury Selivanov in bpo-28544(4).)

   * Various implementation improvements in the *note typing: 11a.
     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(): 333. and *note bytearray.fromhex():
     334.: 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(): 50a. domain (*note
     PYMEM_DOMAIN_MEM: 50e.) now use the *note pymalloc memory
     allocator: 5c6. 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(): 5c7. and *note pickle.loads(): 5c8. are now up
     to 10% faster when deserializing many small objects (Contributed by
     Victor Stinner in bpo-27056(14)).

   * Passing *note keyword arguments: 5c9. to a function has an overhead
     in comparison with passing *note positional arguments: 5ca.  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(): 5cb. and *note iglob(): 5cc. functions in
     the *note glob: 8a. module; they are now about 3–6 times faster.
     (Contributed by Serhiy Storchaka in bpo-25596(16)).

   * Optimized globbing in *note pathlib: c9. by using *note
     os.scandir(): 260.; it is now about 1.5–4 times faster.
     (Contributed by Serhiy Storchaka in bpo-26032(17)).

   * *note xml.etree.ElementTree: 138. 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: 186. 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/issue26647

   (2) https://bugs.python.org/issue28050

   (3) https://bugs.python.org/issue26081

   (4) https://bugs.python.org/issue28544

   (5) https://bugs.python.org/issue24870

   (6) https://bugs.python.org/issue25227

   (7) https://bugs.python.org/issue25267

   (8) https://bugs.python.org/issue25301

   (9) https://bugs.python.org/issue25349

   (10) https://bugs.python.org/issue25399

   (11) https://bugs.python.org/issue25401

   (12) https://bugs.python.org/issue26574

   (13) https://bugs.python.org/issue26249

   (14) https://bugs.python.org/issue27056

   (15) https://bugs.python.org/issue27574

   (16) https://bugs.python.org/issue25596

   (17) https://bugs.python.org/issue26032

   (18) https://bugs.python.org/issue25638

   (19) https://bugs.python.org/issue25873

   (20) https://bugs.python.org/issue25869

   (21) https://bugs.python.org/issue25971


File: python.info,  Node: Build and C API Changes<2>,  Next: Other Improvements,  Prev: Optimizations<3>,  Up: What's New In Python 3 6

1.3.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: 50b. must now be held when allocator functions of
     *note PYMEM_DOMAIN_OBJ: 50c. (ex: *note PyObject_Malloc(): 50d.)
     and *note PYMEM_DOMAIN_MEM: 50e. (ex: *note PyMem_Malloc(): 50a.)
     domains are called.

   * New *note Py_FinalizeEx(): 5ce. API which indicates if flushing
     buffered data failed.  (Contributed by Martin Panter in
     bpo-5319(5).)

   * *note PyArg_ParseTupleAndKeywords(): 5cf. now supports *note
     positional-only parameters: 2a8.  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(): 5d0. function allows
     for specifying a subclass of *note ImportError: 339. to raise.
     (Contributed by Eric Snow in bpo-15767(8).)

   * The new *note PyErr_ResourceWarning(): 5d1. function can be used to
     generate a *note ResourceWarning: 4d5. providing the source of the
     resource allocation.  (Contributed by Victor Stinner in
     bpo-26567(9).)

   * The new *note PyOS_FSPath(): 5d2. function returns the file system
     representation of a *note path-like object: 36f.  (Contributed by
     Brett Cannon in bpo-27186(10).)

   * The *note PyUnicode_FSConverter(): 5d3. and *note
     PyUnicode_FSDecoder(): 5d4. functions will now accept *note
     path-like objects: 36f.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0007

   (2) https://bugs.python.org/issue17884

   (3) https://bugs.python.org/issue26865

   (4) https://bugs.python.org/issue26359

   (5) https://bugs.python.org/issue5319

   (6) https://bugs.python.org/issue26282

   (7) https://bugs.python.org/issue26823

   (8) https://bugs.python.org/issue15767

   (9) https://bugs.python.org/issue26567

   (10) https://bugs.python.org/issue27186


File: python.info,  Node: Other Improvements,  Next: Deprecated<2>,  Prev: Build and C API Changes<2>,  Up: What's New In Python 3 6

1.3.8 Other Improvements
------------------------

   * When *note –version: 5d6. (short form: *note -V: 5d7.) is supplied
     twice, Python prints *note sys.version: 5d8. 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: Deprecated<2>,  Next: Removed,  Prev: Other Improvements,  Up: What's New In Python 3 6

1.3.9 Deprecated
----------------

* Menu:

* New Keywords::
* Deprecated Python behavior::
* Deprecated Python modules, functions and methods: Deprecated Python modules functions and methods<2>.
* Deprecated functions and types of the C API: Deprecated functions and types of the C API<2>.
* Deprecated Build Options::


File: python.info,  Node: New Keywords,  Next: Deprecated Python behavior,  Up: Deprecated<2>

1.3.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.  Starting in Python 3.6, the
use of ‘async’ or ‘await’ as names will generate a *note
DeprecationWarning: 279.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0492


File: python.info,  Node: Deprecated Python behavior,  Next: Deprecated Python modules functions and methods<2>,  Prev: New Keywords,  Up: Deprecated<2>

1.3.9.2 Deprecated Python behavior
..................................

Raising the *note StopIteration: 48b. exception inside a generator will
now generate a *note DeprecationWarning: 279, and will trigger a *note
RuntimeError: 2bb. in Python 3.7.  See *note PEP 479; Change
StopIteration handling inside generators: 5dc. for details.

The *note __aiter__(): 48c. 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:
279.  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: 279.  Although this will
eventually become a *note SyntaxError: 45d, 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: 5dd.  (Contributed by
Rose Ames in bpo-25791(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27243

   (2) https://bugs.python.org/issue27364

   (3) https://bugs.python.org/issue25791


File: python.info,  Node: Deprecated Python modules functions and methods<2>,  Next: Deprecated functions and types of the C API<2>,  Prev: Deprecated Python behavior,  Up: Deprecated<2>

1.3.9.3 Deprecated Python modules, functions and methods
........................................................

* Menu:

* asynchat::
* asyncore::
* dbm: dbm<3>.
* distutils: distutils<3>.
* grp::
* importlib: importlib<4>.
* os: os<4>.
* re: re<3>.
* ssl: ssl<5>.
* tkinter: tkinter<4>.
* venv: venv<3>.


File: python.info,  Node: asynchat,  Next: asyncore,  Up: Deprecated Python modules functions and methods<2>

1.3.9.4 asynchat
................

The *note asynchat: 9. has been deprecated in favor of *note asyncio: a.
(Contributed by Mariatta in bpo-25002(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25002


File: python.info,  Node: asyncore,  Next: dbm<3>,  Prev: asynchat,  Up: Deprecated Python modules functions and methods<2>

1.3.9.5 asyncore
................

The *note asyncore: b. has been deprecated in favor of *note asyncio: a.
(Contributed by Mariatta in bpo-25002(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25002


File: python.info,  Node: dbm<3>,  Next: distutils<3>,  Prev: asyncore,  Up: Deprecated Python modules functions and methods<2>

1.3.9.6 dbm
...........

Unlike other *note dbm: 32. implementations, the *note dbm.dumb: 33.
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/issue21708


File: python.info,  Node: distutils<3>,  Next: grp,  Prev: dbm<3>,  Up: Deprecated Python modules functions and methods<2>

1.3.9.7 distutils
.................

The undocumented ‘extra_path’ argument to the ‘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/issue27919


File: python.info,  Node: grp,  Next: importlib<4>,  Prev: distutils<3>,  Up: Deprecated Python modules functions and methods<2>

1.3.9.8 grp
...........

The support of non-integer arguments in *note getgrgid(): 5e4. has been
deprecated.  (Contributed by Serhiy Storchaka in bpo-26129(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26129


File: python.info,  Node: importlib<4>,  Next: os<4>,  Prev: grp,  Up: Deprecated Python modules functions and methods<2>

1.3.9.9 importlib
.................

The *note importlib.machinery.SourceFileLoader.load_module(): 5e6. and
*note importlib.machinery.SourcelessFileLoader.load_module(): 5e7.
methods are now deprecated.  They were the only remaining
implementations of *note importlib.abc.Loader.load_module(): 5e8. in
*note importlib: 9b. that had not been deprecated in previous versions
of Python in favour of *note importlib.abc.Loader.exec_module(): 5e9.

The *note importlib.machinery.WindowsRegistryFinder: 5ea. class is now
deprecated.  As of 3.6.0, it is still added to *note sys.meta_path: 5eb.
by default (on Windows), but this may change in future releases.


File: python.info,  Node: os<4>,  Next: re<3>,  Prev: importlib<4>,  Up: Deprecated Python modules functions and methods<2>

1.3.9.10 os
...........

Undocumented support of general *note bytes-like objects: 5ed. as paths
in *note os: c5. functions, *note compile(): 1b5. and similar functions
is now deprecated.  (Contributed by Serhiy Storchaka in bpo-25791(1) and
bpo-26754(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25791

   (2) https://bugs.python.org/issue26754


File: python.info,  Node: re<3>,  Next: ssl<5>,  Prev: os<4>,  Up: Deprecated Python modules functions and methods<2>

1.3.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/issue22493


File: python.info,  Node: ssl<5>,  Next: tkinter<4>,  Prev: re<3>,  Up: Deprecated Python modules functions and methods<2>

1.3.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: f4. 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: 84, *note http.client: 94, *note imaplib: 98, *note
poplib: d1, and *note smtplib: ee. 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: f4. 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/issue28022

   (2) https://bugs.python.org/issue28022

   (3) https://bugs.python.org/issue26470


File: python.info,  Node: tkinter<4>,  Next: venv<3>,  Prev: ssl<5>,  Up: Deprecated Python modules functions and methods<2>

1.3.9.13 tkinter
................

The *note tkinter.tix: 10f. module is now deprecated.  *note tkinter:
10d. users should use *note tkinter.ttk: 110. instead.


File: python.info,  Node: venv<3>,  Prev: tkinter<4>,  Up: Deprecated Python modules functions and methods<2>

1.3.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/issue25154


File: python.info,  Node: Deprecated functions and types of the C API<2>,  Next: Deprecated Build Options,  Prev: Deprecated Python modules functions and methods<2>,  Up: Deprecated<2>

1.3.9.15 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: 5f3. instead.


File: python.info,  Node: Deprecated Build Options,  Prev: Deprecated functions and types of the C API<2>,  Up: Deprecated<2>

1.3.9.16 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: Removed,  Next: Porting to Python 3 6,  Prev: Deprecated<2>,  Up: What's New In Python 3 6

1.3.10 Removed
--------------

* Menu:

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


File: python.info,  Node: API and Feature Removals<3>,  Up: Removed

1.3.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(): 480. they are still allowed, but deprecated.  The
     *note re.LOCALE: 3ce. flag can now only be used with binary
     patterns.

   * ‘inspect.getmoduleinfo()’ was removed (was deprecated since CPython
     3.3).  *note inspect.getmodulename(): 5f7. 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: 114. 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: 10d. widget classes were removed (corresponding Tk
     commands were obsolete since Tk 4.0).

   * The *note open(): 5c1. method of the *note zipfile.ZipFile: 424.
     class no longer supports the ‘'U'’ mode (was deprecated since
     Python 3.4).  Use *note io.TextIOWrapper: 5f8. for reading
     compressed text files in *note universal newlines: 5f9. 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/issue13248

   (2) https://github.com/python/cpython/tree/3.8/Tools/scripts/h2py.py


File: python.info,  Node: Porting to Python 3 6,  Next: Notable changes in Python 3 6 2,  Prev: Removed,  Up: What's New In Python 3 6

1.3.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<3>.
* Changes in the C API: Changes in the C API<3>.
* CPython bytecode changes: CPython bytecode changes<3>.


File: python.info,  Node: Changes in 'python' Command Behavior,  Next: Changes in the Python API<3>,  Up: Porting to Python 3 6

1.3.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/issue23034


File: python.info,  Node: Changes in the Python API<3>,  Next: Changes in the C API<3>,  Prev: Changes in 'python' Command Behavior,  Up: Porting to Python 3 6

1.3.11.2 Changes in the Python API
..................................

   * *note open(): 4f5. will no longer allow combining the ‘'U'’ mode
     flag with ‘'+'’.  (Contributed by Jeff Balogh and John O’Connor in
     bpo-2091(1).)

   * *note sqlite3: f3. no longer implicitly commits an open transaction
     before DDL statements.

   * On Linux, *note os.urandom(): 4d6. now blocks until the system
     urandom entropy pool is initialized to increase the security.

   * When *note importlib.abc.Loader.exec_module(): 5e9. is defined,
     *note importlib.abc.Loader.create_module(): 559. must also be
     defined.

   * *note PyErr_SetImportError(): 5fd. now sets *note TypeError: 193.
     when its `msg' argument is not set.  Previously only ‘NULL’ was
     returned.

   * The format of the ‘co_lnotab’ 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
     ‘frame.f_lineno’, ‘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: 21. 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(): 5fe.
     and *note urlparse(): 5ff. results now raises *note ValueError:
     1fc. for out-of-range values, rather than returning *note None:
     158.  See bpo-20059(4).

   * The *note imp: 9a. module now raises a *note DeprecationWarning:
     279. instead of *note PendingDeprecationWarning: 27a.

   * The following modules have had missing APIs added to their
     ‘__all__’ attributes to match the documented APIs: *note calendar:
     15, *note cgi: 16, *note csv: 2a, *note ElementTree: 138, *note
     enum: 7b, *note fileinput: 80, *note ftplib: 84, *note logging: ab,
     *note mailbox: af, *note mimetypes: b3, *note optparse: c4, *note
     plistlib: d0, *note smtpd: ed, *note subprocess: fa, *note tarfile:
     102, *note threading: 10a. and *note wave: 128.  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: 5dd.
     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: 339. will be raised.  Previously, *note
     SystemError: 600. could be raised.  (Contributed by Brett Cannon in
     bpo-18018(7).)

   * Servers based on the *note socketserver: f1. module, including
     those defined in *note http.server: 97, *note xmlrpc.server: 141.
     and *note wsgiref.simple_server: 130, now only catch exceptions
     derived from *note Exception: 1aa.  Therefore if a request handler
     raises an exception like *note SystemExit: 601. or *note
     KeyboardInterrupt: 198, *note handle_error(): 602. is no longer
     called, and the exception will stop a single-threaded server.
     (Contributed by Martin Panter in bpo-23430(8).)

   * *note spwd.getspnam(): 603. now raises a *note PermissionError:
     604. instead of *note KeyError: 2c8. if the user doesn’t have
     privileges.

   * The *note socket.socket.close(): 605. 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 *note smtpd.SMTPChannel: 606.
     and *note smtpd.SMTPServer: 607. constructors is now ‘False’ by
     default.  This means that the argument passed to *note
     process_message(): 608. 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(): 609, *note dumps():
     60a, *note load(): 564. and *note loads(): 565. functions and *note
     JSONEncoder: 60b. and *note JSONDecoder: 60c. class constructors in
     the *note json: a5. module are now *note keyword-only: 2ad.
     (Contributed by Serhiy Storchaka in bpo-18726(10).)

   * Subclasses of *note type: 60d. 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: 60d. (other than the metaclass hint, ‘metaclass’) is
     now consistently delegated to *note object.__init_subclass__():
     4e8.  This means that ‘type.__new__()’ and ‘type.__init__()’ both
     now accept arbitrary keyword arguments, but *note
     object.__init_subclass__(): 4e8. (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: 4e7.)
     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: 121. module and the *note
     http.client.HTTPConnection.request(): 554. 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: 1be. now returns rows of type *note
     OrderedDict: 1ba.  (Contributed by Steve Holden in bpo-27842(13).)

   * The *note crypt.METHOD_CRYPT: 60e. 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(): 1b8.
     are now keyword-only.  (Contributed by Raymond Hettinger in
     bpo-25628(15).)

   * On Linux, *note ctypes.util.find_library(): 60f. now looks in
     ‘LD_LIBRARY_PATH’ for shared libraries.  (Contributed by Vinay
     Sajip in bpo-9998(16).)

   * The *note imaplib.IMAP4: 610. 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(): 611. and *note
     pkgutil.walk_packages(): 490. functions now return *note
     ModuleInfo: 612. named tuples.  (Contributed by Ramchandra Apte in
     bpo-17211(19).)

   * *note re.sub(): 480. 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: 424. will now raise *note
     NotImplementedError: 613. for unrecognized compression values.
     Previously a plain *note RuntimeError: 2bb. was raised.
     Additionally, calling *note ZipFile: 424. methods on a closed
     ZipFile or calling the *note write(): 614. method on a ZipFile
     created with mode ‘'r'’ will raise a *note ValueError: 1fc.
     Previously, a *note RuntimeError: 2bb. was raised in those
     scenarios.

   * when custom metaclasses are combined with zero-argument *note
     super(): 4e7. 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: 279. in Python 3.6 and a *note RuntimeError:
     2bb. in Python 3.8.

   * With the introduction of *note ModuleNotFoundError: 39f, import
     system consumers may start expecting import system replacements to
     raise that more specific exception when appropriate, rather than
     the less-specific *note ImportError: 339.  To provide future
     compatibility with such consumers, implementors of alternative
     import systems that completely replace *note __import__(): 615.
     will need to update their implementations to raise the new subclass
     when a module can’t be found at all.  Implementors 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/issue2091

   (2) https://www.python.org/dev/peps/pep-0511

   (3) https://bugs.python.org/issue25768

   (4) https://bugs.python.org/issue20059

   (5) https://bugs.python.org/issue23883

   (6) https://bugs.python.org/issue25791

   (7) https://bugs.python.org/issue18018

   (8) https://bugs.python.org/issue23430

   (9) https://bugs.python.org/issue26685

   (10) https://bugs.python.org/issue18726

   (11) https://www.python.org/dev/peps/pep-0487

   (12) https://bugs.python.org/issue12319

   (13) https://bugs.python.org/issue27842

   (14) https://bugs.python.org/issue25287

   (15) https://bugs.python.org/issue25628

   (16) https://bugs.python.org/issue9998

   (17) https://bugs.python.org/issue21815

   (18) https://bugs.python.org/issue26335

   (19) https://bugs.python.org/issue17211

   (20) https://bugs.python.org/issue25953


File: python.info,  Node: Changes in the C API<3>,  Next: CPython bytecode changes<3>,  Prev: Changes in the Python API<3>,  Up: Porting to Python 3 6

1.3.11.3 Changes in the C API
.............................

   * The *note PyMem_Malloc(): 50a. allocator family now uses the *note
     pymalloc allocator: 5c6. rather than the system ‘malloc()’.
     Applications calling *note PyMem_Malloc(): 50a. without holding the
     GIL can now crash.  Set the *note PYTHONMALLOC: 508. environment
     variable to ‘debug’ to validate the usage of memory allocators in
     your application.  See bpo-26249(1).

   * *note Py_Exit(): 617. (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/issue26249

   (2) https://bugs.python.org/issue5319


File: python.info,  Node: CPython bytecode changes<3>,  Prev: Changes in the C API<3>,  Up: Porting to Python 3 6

1.3.11.4 CPython bytecode changes
.................................

There have been several major changes to the *note bytecode: 619. 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 *note FORMAT_VALUE: 61a. and *note BUILD_STRING: 61b.
     opcodes as part of the *note formatted string literal: 4c6.
     implementation.  (Contributed by Eric Smith in bpo-25483(3) and
     Serhiy Storchaka in bpo-27078(4).)

   * The new *note BUILD_CONST_KEY_MAP: 61c. 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:
     61d, *note CALL_FUNCTION: 61e, *note CALL_FUNCTION_KW: 61f. and
     *note BUILD_MAP_UNPACK_WITH_CALL: 620. opcodes have been modified,
     the new *note CALL_FUNCTION_EX: 621. and *note
     BUILD_TUPLE_UNPACK_WITH_CALL: 622. 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: 623. and ‘STORE_ANNOTATION’
     opcodes have been added to support the new *note variable
     annotation: 624. syntax.  (Contributed by Ivan Levkivskyi in
     bpo-27985(9).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26647

   (2) https://bugs.python.org/issue28050

   (3) https://bugs.python.org/issue25483

   (4) https://bugs.python.org/issue27078

   (5) https://bugs.python.org/issue27140

   (6) https://bugs.python.org/issue27095

   (7) https://bugs.python.org/issue27213

   (8) https://bugs.python.org/issue28257

   (9) https://bugs.python.org/issue27985


File: python.info,  Node: Notable changes in Python 3 6 2,  Next: Notable changes in Python 3 6 4,  Prev: Porting to Python 3 6,  Up: What's New In Python 3 6

1.3.12 Notable changes in 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: Notable changes in Python 3 6 2

1.3.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.

(Contributed by Victor Stinner in bpo-23404(2).)

3.6.2 版新加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Makefile.pre.in

   (2) https://bugs.python.org/issue23404


File: python.info,  Node: Removal of make touch build target,  Prev: New make regen-all build target,  Up: Notable changes in Python 3 6 2

1.3.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.

(Contributed by Victor Stinner in bpo-23404(1).)

3.6.2 版更變.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23404


File: python.info,  Node: Notable changes in Python 3 6 4,  Next: Notable changes in Python 3 6 5,  Prev: Notable changes in Python 3 6 2,  Up: What's New In Python 3 6

1.3.13 Notable changes in 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/issue22898

   (2) https://bugs.python.org/issue30697


File: python.info,  Node: Notable changes in Python 3 6 5,  Next: Notable changes in Python 3 6 7,  Prev: Notable changes in Python 3 6 4,  Up: What's New In Python 3 6

1.3.14 Notable changes in Python 3.6.5
--------------------------------------

The *note locale.localeconv(): 48f. 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/issue31900


File: python.info,  Node: Notable changes in Python 3 6 7,  Next: Notable changes in Python 3 6 10,  Prev: Notable changes in Python 3 6 5,  Up: What's New In Python 3 6

1.3.15 Notable changes in Python 3.6.7
--------------------------------------

In 3.6.7 the *note tokenize: 112. 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/issue33899


File: python.info,  Node: Notable changes in Python 3 6 10,  Next: Notable changes in Python 3 6 13,  Prev: Notable changes in Python 3 6 7,  Up: What's New In Python 3 6

1.3.16 Notable changes in Python 3.6.10
---------------------------------------

Due to significant security concerns, the `reuse_address' parameter of
*note asyncio.loop.create_datagram_endpoint(): 2e8. 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/issue37228


File: python.info,  Node: Notable changes in Python 3 6 13,  Prev: Notable changes in Python 3 6 10,  Up: What's New In Python 3 6

1.3.17 Notable changes in Python 3.6.13
---------------------------------------

Earlier Python versions allowed using both ‘;’ and ‘&’ as query
parameter separators in *note urllib.parse.parse_qs(): 2ec. and *note
urllib.parse.parse_qsl(): 2ed.  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
*note cgi.parse(): 2ee. and *note cgi.parse_multipart(): 2ef. 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/issue42967


File: python.info,  Node: Python 3 5 有什麼新功能,  Next: What's New In Python 3 4,  Prev: What's New In Python 3 6,  Up: Python 有什麼新功能？

1.4 Python 3.5 有什麼新功能
===========================


Editors: 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<3>. Release highlights
* New Features: New Features<4>.
* Other Language Changes: Other Language Changes<4>.
* New Modules: New Modules<4>.
* Improved Modules: Improved Modules<4>.
* Other module-level changes::
* Optimizations: Optimizations<4>.
* Build and C API Changes: Build and C API Changes<3>.
* Deprecated: Deprecated<3>.
* Removed: Removed<2>.
* Porting to Python 3.5: Porting to Python 3 5.
* Notable changes in Python 3.5.4: Notable changes in Python 3 5 4.

   ---------- Footnotes ----------

   (1) https://docs.python.org/3.5/whatsnew/changelog.html

   (2) https://www.python.org/dev/peps/pep-0478


File: python.info,  Node: Summary -- Release highlights<3>,  Next: New Features<4>,  Up: Python 3 5 有什麼新功能

1.4.1 Summary – Release highlights
----------------------------------

New syntax features:

   * *note PEP 492: 630, coroutines with async and await syntax.

   * *note PEP 465: 631, a new matrix multiplication operator: ‘a @ b’.

   * *note PEP 448: 632, additional unpacking generalizations.

New library modules:

   * *note typing: 11a.: *note PEP 484 – Type Hints: 633.

   * *note zipapp: 142.: *note PEP 441 Improving Python ZIP Application
     Support: 634.

New built-in features:

   * ‘bytes % args’, ‘bytearray % args’: *note PEP 461: 635. – Adding
     ‘%’ formatting to bytes and bytearray.

   * New *note bytes.hex(): 636, *note bytearray.hex(): 637. and *note
     memoryview.hex(): 638. methods.  (Contributed by Arnon Yaari in
     bpo-9951(1).)

   * *note memoryview: 25d. 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: 639. exception is now raised when
     maximum recursion depth is reached.  (Contributed by Georg Brandl
     in bpo-19235(4).)

CPython implementation improvements:

   * When the ‘LC_TYPE’ locale is the POSIX locale (‘C’ locale), *note
     sys.stdin: 312. and *note sys.stdout: 313. 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: 63a.)

   * 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: 63b.)

Significant improvements in the standard library:

   * *note collections.OrderedDict: 1ba. is now *note implemented in C:
     63c, which makes it 4 to 100 times faster.

   * The *note ssl: f4. module gained *note support for Memory BIO: 63d,
     which decouples SSL protocol handling from network IO.

   * The new *note os.scandir(): 260. function provides a *note better
     and significantly faster way: 63e. of directory traversal.

   * *note functools.lru_cache(): 1c8. has been mostly *note
     reimplemented in C: 63f, yielding much better performance.

   * The new *note subprocess.run(): 3f2. function provides a *note
     streamlined way to run subprocesses: 640.

   * The *note traceback: 114. module has been significantly *note
     enhanced: 641. for improved performance and developer convenience.

Security improvements:

   * SSLv3 is now disabled throughout the standard library.  It can
     still be enabled by instantiating a *note ssl.SSLContext: 3e9.
     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: 2da. 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/issue9951

   (2) https://bugs.python.org/issue23632

   (3) https://bugs.python.org/issue24450

   (4) https://bugs.python.org/issue19235

   (5) https://bugs.python.org/issue19977

   (6) https://bugs.python.org/issue22638

   (7) https://bugs.python.org/issue22796


File: python.info,  Node: New Features<4>,  Next: Other Language Changes<4>,  Prev: Summary -- Release highlights<3>,  Up: Python 3 5 有什麼新功能

1.4.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<4>

1.4.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: 51e, *note coroutine
functions: 644, *note asynchronous iteration: 645, and *note
asynchronous context managers: 646.

Coroutine functions are declared using the new *note async def: 285.
syntax:

     >>> async def coro():
     ...     return 'spam'

Inside a coroutine function, the new *note await: 1a4. 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:
51e. protocol by defining the *note __await__(): 647. method.

PEP 492 also adds *note async for: 2e4. 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: 2e4. and *note async with: 648. can only
be used inside a coroutine function declared with *note async def: 285.

Coroutine functions are intended to be run inside a compatible event
loop, such as the *note asyncio loop: 649.

     備註: 
     3.5.2 版更變: Starting with CPython 3.5.2, ‘__aiter__’ can directly
     return *note asynchronous iterators: 64a.  Returning an *note
     awaitable: 51e. object will result in a *note
     PendingDeprecationWarning: 27a.

     See more details in the *note Asynchronous Iterators: 64b.
     documentation section.

也參考
......

PEP 492(2) – Coroutines with async and await syntax

     PEP written and implemented by Yury Selivanov.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0492

   (2) https://www.python.org/dev/peps/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<4>

1.4.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 *note __matmul__(): 64d, *note
__rmatmul__(): 64e, and *note __imatmul__(): 64f. 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

     PEP written by Nathaniel J. Smith; implemented by Benjamin
     Peterson.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0465

   (2) https://www.python.org/dev/peps/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<4>

1.4.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: 651.:

     >>> 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: 652. and *note Dictionary
displays: 653.):

     >>> *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://www.python.org/dev/peps/pep-0448

   (2) https://www.python.org/dev/peps/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<4>

1.4.2.4 PEP 461 - percent formatting support for bytes and bytearray
....................................................................

PEP 461(1) adds support for the ‘%’ *note interpolation operator: 655.
to *note bytes: 336. and *note bytearray: 337.

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.

Examples:

     >>> 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://www.python.org/dev/peps/pep-0461

   (2) https://www.python.org/dev/peps/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<4>

1.4.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: 34d. 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: 657. which is consistent with (i.e.  assignable to and from)
all types.

也參考
......

   * *note typing: 11a. module documentation

   * 
     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

          PEP written by Guido van Rossum

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3107

   (2) https://www.python.org/dev/peps/pep-0484

   (3) http://mypy-lang.org

   (4) https://www.python.org/dev/peps/pep-0484

   (5) https://www.python.org/dev/peps/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<4>

1.4.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():
260, to the standard library.  Additionally, *note os.walk(): 659. 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(): 1f2. 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(): 260. to
display all the files (excluding directories) in the given `path' that
don’t start with ‘'.'’.  The *note entry.is_file(): 65a. 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

     PEP written and implemented by Ben Hoyt with the help of Victor
     Stinner.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0471

   (2) https://www.python.org/dev/peps/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<4>

1.4.2.7 PEP 475: Retry system calls failing with EINTR
......................................................

An *note errno.EINTR: 65d. 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: 65e. 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")

and:

     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:
65e. 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(): 4f5. and *note io.open(): 65f.;

   * functions of the *note faulthandler: 7d. module;

   * *note os: c5. functions: *note fchdir(): 660, *note fchmod(): 661,
     *note fchown(): 662, *note fdatasync(): 663, *note fstat(): 664,
     *note fstatvfs(): 665, *note fsync(): 666, *note ftruncate(): 667,
     *note mkfifo(): 668, *note mknod(): 669, *note open(): 66a, *note
     posix_fadvise(): 66b, *note posix_fallocate(): 66c, *note pread():
     3be, *note pwrite(): 3c1, *note read(): 66d, *note readv(): 3bd,
     *note sendfile(): 35e, *note wait3(): 66e, *note wait4(): 66f,
     *note wait(): 670, *note waitid(): 671, *note waitpid(): 672, *note
     write(): 673, *note writev(): 3c0.;

   * special cases: *note os.close(): 3d7. and *note os.dup2(): 3c3. now
     ignore *note EINTR: 65d. errors; the syscall is not retried (see
     the PEP for the rationale);

   * *note select: e6. functions: *note devpoll.poll(): 674, *note
     epoll.poll(): 675, *note kqueue.control(): 676, *note poll.poll():
     677, *note select(): 678.;

   * methods of the *note socket: 679. class: *note accept(): 67a, *note
     connect(): 67b. (except for non-blocking sockets), *note recv():
     67c, *note recvfrom(): 67d, *note recvmsg(): 67e, *note send():
     67f, *note sendall(): 680, *note sendmsg(): 681, *note sendto():
     682.;

   * *note signal.sigtimedwait(): 683. and *note signal.sigwaitinfo():
     684.;

   * *note time.sleep(): 685.

也參考
......

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://www.python.org/dev/peps/pep-0475

   (2) https://www.python.org/dev/peps/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<4>

1.4.2.8 PEP 479: Change StopIteration handling inside generators
................................................................

The interaction of generators and *note StopIteration: 48b. 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: 2bb. before it exits the generator frame.  The main goal
of this change is to ease debugging in the situation where an unguarded
*note next(): 687. 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__: 688. 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: 27a.
will be raised whenever a *note StopIteration: 48b. 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://www.python.org/dev/peps/pep-0479

   (2) https://www.python.org/dev/peps/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<4>

1.4.2.9 PEP 485: A function for testing approximate equality
............................................................

PEP 485(1) adds the *note math.isclose(): 68b. and *note
cmath.isclose(): 68c. 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://www.python.org/dev/peps/pep-0485

   (2) https://www.python.org/dev/peps/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<4>

1.4.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

     PEP written and implemented by Paul Moore.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0486

   (2) https://www.python.org/dev/peps/pep-0397

   (3) https://www.python.org/dev/peps/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<4>

1.4.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: 690. or *note -OO: 691.
Consequently, bytecode files generated from *note -O: 690, and *note
-OO: 691. may now exist simultaneously.  *note
importlib.util.cache_from_source(): 55c. has an updated API to help with
this change.

也參考
......

PEP 488(2) – Elimination of PYO files

     PEP written and implemented by Brett Cannon.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0488

   (2) https://www.python.org/dev/peps/pep-0488


File: python.info,  Node: PEP 489 Multi-phase extension module initialization,  Prev: PEP 488 Elimination of PYO files,  Up: New Features<4>

1.4.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://www.python.org/dev/peps/pep-0489

   (2) https://www.python.org/dev/peps/pep-0451

   (3) https://www.python.org/dev/peps/pep-0489


File: python.info,  Node: Other Language Changes<4>,  Next: New Modules<4>,  Prev: New Features<4>,  Up: Python 3 5 有什麼新功能

1.4.3 Other Language Changes
----------------------------

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: 41a. option now affects comparisons of *note bytes:
     336. with *note int: 185.  (Contributed by Serhiy Storchaka in
     bpo-23681(3).)

   * New Kazakh ‘kz1048’ and Tajik ‘koi8_t’ *note codecs: 694.
     (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(): 1b8. 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/issue19676

   (2) https://bugs.python.org/issue22286

   (3) https://bugs.python.org/issue23681

   (4) https://bugs.python.org/issue22682

   (5) https://bugs.python.org/issue22681

   (6) https://bugs.python.org/issue24064

   (7) https://bugs.python.org/issue17636


File: python.info,  Node: New Modules<4>,  Next: Improved Modules<4>,  Prev: Other Language Changes<4>,  Up: Python 3 5 有什麼新功能

1.4.4 New Modules
-----------------

* Menu:

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


File: python.info,  Node: typing<3>,  Next: zipapp<2>,  Up: New Modules<4>

1.4.4.1 typing
..............

The new *note typing: 11a. *note provisional: 34d. module provides
standard definitions and tools for function type annotations.  See *note
Type Hints: 633. for more information.


File: python.info,  Node: zipapp<2>,  Prev: typing<3>,  Up: New Modules<4>

1.4.4.2 zipapp
..............

The new *note zipapp: 142. 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://www.python.org/dev/peps/pep-0441

   (2) https://bugs.python.org/issue1739468

   (3) https://bugs.python.org/issue23491

   (4) https://www.python.org/dev/peps/pep-0441


File: python.info,  Node: Improved Modules<4>,  Next: Other module-level changes,  Prev: New Modules<4>,  Up: Python 3 5 有什麼新功能

1.4.5 Improved Modules
----------------------

* Menu:

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


File: python.info,  Node: argparse<2>,  Next: asyncio<5>,  Up: Improved Modules<4>

1.4.5.1 argparse
................

The *note ArgumentParser: 69a. class now allows disabling *note
abbreviated usage: 69b. of long options by setting *note allow_abbrev:
69c. to ‘False’.  (Contributed by Jonathan Paugh, Steven Bethard, paul
j3 and Daniel Eriksson in bpo-14910(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14910


File: python.info,  Node: asyncio<5>,  Next: bz2,  Prev: argparse<2>,  Up: Improved Modules<4>

1.4.5.2 asyncio
...............

Since the *note asyncio: a. module is *note provisional: 34d, all
changes introduced in Python 3.5 have also been backported to Python
3.4.x.

Notable changes in the *note asyncio: a. module since Python 3.4.0:

   * New debugging APIs: *note loop.set_debug(): 69e. and *note
     loop.get_debug(): 69f. 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(): 6a0. method to check if the event
     loop is closed.  (Contributed by Victor Stinner in bpo-21326(2).)

   * A new *note loop.create_task(): 1b0. to conveniently create and
     schedule a new *note Task: 1ae. for a coroutine.  The ‘create_task’
     method is also used by all asyncio functions that wrap coroutines
     into tasks, such as *note asyncio.wait(): 28a, *note
     asyncio.gather(): 287, etc.  (Contributed by Victor Stinner.)

   * A new *note transport.get_write_buffer_limits(): 6a1. 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(): 51c.  (Contributed by Yury Selivanov.)

   * New *note loop.set_task_factory(): 6a2. and *note
     loop.get_task_factory(): 6a3. methods to customize the task factory
     that *note loop.create_task(): 1b0. method uses.  (Contributed by
     Yury Selivanov.)

   * New *note Queue.join(): 6a4. and *note Queue.task_done(): 6a5.
     queue methods.  (Contributed by Victor Stinner.)

   * The ‘JoinableQueue’ class was removed, in favor of the *note
     asyncio.Queue: 291. class.  (Contributed by Victor Stinner.)

Updates in 3.5.1:

   * The *note ensure_future(): 51c. function and all functions that use
     it, such as *note loop.run_until_complete(): 51d, now accept all
     kinds of *note awaitable objects: 51e.  (Contributed by Yury
     Selivanov.)

   * New *note run_coroutine_threadsafe(): 51f. function to submit
     coroutines to event loops from other threads.  (Contributed by
     Vincent Michel.)

   * New *note Transport.is_closing(): 520. method to check if the
     transport is closing or closed.  (Contributed by Yury Selivanov.)

   * The *note loop.create_server(): 362. method can now accept a list
     of hosts.  (Contributed by Yann Sionneau.)

Updates in 3.5.2:

   * New *note loop.create_future(): 521. method to create Future
     objects.  This allows alternative event loop implementations, such
     as uvloop(3), to provide a faster *note asyncio.Future: 448.
     implementation.  (Contributed by Yury Selivanov.)

   * New *note loop.get_exception_handler(): 522. method to get the
     current exception handler.  (Contributed by Yury Selivanov.)

   * New *note StreamReader.readuntil(): 523. method to read data from
     the stream until a separator bytes sequence appears.  (Contributed
     by Mark Korenberg.)

   * The *note loop.create_connection(): 1b3. and *note
     loop.create_server(): 362. 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): 6a6. no longer requires
     the `address' to be resolved prior to the call.  (Contributed by A.
     Jesse Jiryu Davis.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22560

   (2) https://bugs.python.org/issue21326

   (3) https://github.com/MagicStack/uvloop


File: python.info,  Node: bz2,  Next: cgi,  Prev: asyncio<5>,  Up: Improved Modules<4>

1.4.5.3 bz2
...........

The *note BZ2Decompressor.decompress: 6a8. 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/issue15955


File: python.info,  Node: cgi,  Next: cmath<2>,  Prev: bz2,  Up: Improved Modules<4>

1.4.5.4 cgi
...........

The ‘FieldStorage’ class now supports the *note context manager: 56d.
protocol.  (Contributed by Berker Peksag in bpo-20289(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20289


File: python.info,  Node: cmath<2>,  Next: code,  Prev: cgi,  Up: Improved Modules<4>

1.4.5.5 cmath
.............

A new function *note isclose(): 68c. 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/issue24270


File: python.info,  Node: code,  Next: collections<5>,  Prev: cmath<2>,  Up: Improved Modules<4>

1.4.5.6 code
............

The *note InteractiveInterpreter.showtraceback(): 6ac. 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/issue17442


File: python.info,  Node: collections<5>,  Next: collections abc,  Prev: code,  Up: Improved Modules<4>

1.4.5.7 collections
...................

The *note OrderedDict: 1ba. 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(): 18f. iteration.  (Contributed by
Serhiy Storchaka in bpo-19505(2).)

The *note deque: 536. class now defines *note index(): 6ae, *note
insert(): 6af, and *note copy(): 6b0, and supports the ‘+’ and ‘*’
operators.  This allows deques to be recognized as a *note
MutableSequence: 6b1. and improves their substitutability for lists.
(Contributed by Raymond Hettinger in bpo-23704(3).)

Docstrings produced by *note namedtuple(): 1b8. can now be updated:

     Point = namedtuple('Point', ['x', 'y'])
     Point.__doc__ += ': Cartesian coodinate'
     Point.x.__doc__ = 'abscissa'
     Point.y.__doc__ = 'ordinate'

(Contributed by Berker Peksag in bpo-24064(4).)

The *note UserString: 6b2. class now implements the *note
__getnewargs__(): 6b3, *note __rmod__(): 6b4, *note casefold(): 6b5,
*note format_map(): 6b6, *note isprintable(): 6b7, and *note
maketrans(): 6b8. methods to match the corresponding methods of *note
str: 335.  (Contributed by Joe Jevnik in bpo-22189(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16991

   (2) https://bugs.python.org/issue19505

   (3) https://bugs.python.org/issue23704

   (4) https://bugs.python.org/issue24064

   (5) https://bugs.python.org/issue22189


File: python.info,  Node: collections abc,  Next: compileall<2>,  Prev: collections<5>,  Up: Improved Modules<4>

1.4.5.8 collections.abc
.......................

The ‘Sequence.index()’ method now accepts `start' and `stop' arguments
to match the corresponding methods of *note tuple: 483, *note list: 263,
etc.  (Contributed by Devin Jeanpierre in bpo-23086(1).)

A new *note Generator: 6ba. abstract base class.  (Contributed by Stefan
Behnel in bpo-24018(2).)

New *note Awaitable: 6bb, *note Coroutine: 6bc, *note AsyncIterator:
6bd, and *note AsyncIterable: 6be. 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/issue23086

   (2) https://bugs.python.org/issue24018

   (3) https://bugs.python.org/issue24184

   (4) https://pypi.org/project/backports_abc


File: python.info,  Node: compileall<2>,  Next: concurrent futures<3>,  Prev: collections abc,  Up: Improved Modules<4>

1.4.5.9 compileall
..................

A new *note compileall: 21. option, ‘-j `N'’, allows running `N' workers
simultaneously to perform parallel bytecode compilation.  The *note
compile_dir(): 377. 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(): 377, *note
compile_file(): 6c0, and *note compile_path(): 6c1. 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/issue16104

   (2) https://bugs.python.org/issue19628

   (3) https://bugs.python.org/issue21338


File: python.info,  Node: concurrent futures<3>,  Next: configparser,  Prev: compileall<2>,  Up: Improved Modules<4>

1.4.5.10 concurrent.futures
...........................

The *note Executor.map(): 6c3. method now accepts a `chunksize' argument
to allow batching of tasks to improve performance when *note
ProcessPoolExecutor(): 2a5. is used.  (Contributed by Dan O’Reilly in
bpo-11271(1).)

The number of workers in the *note ThreadPoolExecutor: 27b. 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/issue11271

   (2) https://bugs.python.org/issue21527


File: python.info,  Node: configparser,  Next: contextlib<3>,  Prev: concurrent futures<3>,  Up: Improved Modules<4>

1.4.5.11 configparser
.....................

*note configparser: 23. now provides a way to customize the conversion
of values by specifying a dictionary of converters in the *note
ConfigParser: 4af. constructor, or by defining them as methods in
‘ConfigParser’ subclasses.  Converters defined in a parser instance are
inherited by its section proxies.

Example:

     >>> 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']

(Contributed by Łukasz Langa in bpo-18159(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue18159


File: python.info,  Node: contextlib<3>,  Next: csv<2>,  Prev: configparser,  Up: Improved Modules<4>

1.4.5.12 contextlib
...................

The new *note redirect_stderr(): 6c6. *note context manager: 56d.
(similar to *note redirect_stdout(): 6c7.) makes it easier for utility
scripts to handle inflexible APIs that write their output to *note
sys.stderr: 314. 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'

(Contributed by Berker Peksag in bpo-22389(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22389


File: python.info,  Node: csv<2>,  Next: curses<2>,  Prev: contextlib<3>,  Up: Improved Modules<4>

1.4.5.13 csv
............

The *note writerow(): 6c9. method now supports arbitrary iterables, not
just sequences.  (Contributed by Serhiy Storchaka in bpo-23171(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23171


File: python.info,  Node: curses<2>,  Next: dbm<4>,  Prev: csv<2>,  Up: Improved Modules<4>

1.4.5.14 curses
...............

The new *note update_lines_cols(): 6cb. function updates the ‘LINES’ and
‘COLS’ environment variables.  This is useful for detecting manual
screen resizing.  (Contributed by Arnon Yaari in bpo-4254(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue4254


File: python.info,  Node: dbm<4>,  Next: difflib,  Prev: curses<2>,  Up: Improved Modules<4>

1.4.5.15 dbm
............

*note dumb.open: 2c0. 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/issue18039


File: python.info,  Node: difflib,  Next: distutils<4>,  Prev: dbm<4>,  Up: Improved Modules<4>

1.4.5.16 difflib
................

The charset of HTML documents generated by *note HtmlDiff.make_file():
6ce. 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(): 6cf. 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/issue2052

   (2) https://bugs.python.org/issue17445


File: python.info,  Node: distutils<4>,  Next: doctest,  Prev: difflib,  Up: Improved Modules<4>

1.4.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 *note distutils: 39. 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/issue5309

   (2) https://bugs.python.org/issue16314


File: python.info,  Node: doctest,  Next: email<2>,  Prev: distutils<4>,  Up: Improved Modules<4>

1.4.5.18 doctest
................

The *note DocTestSuite(): 6d2. function returns an empty *note
unittest.TestSuite: 6d3. if `module' contains no docstrings, instead of
raising *note ValueError: 1fc.  (Contributed by Glenn Jones in
bpo-15916(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue15916


File: python.info,  Node: email<2>,  Next: enum<4>,  Prev: doctest,  Up: Improved Modules<4>

1.4.5.19 email
..............

A new policy option *note Policy.mangle_from_: 6d5. 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: 545. and ‘False’ for all other policies.  (Contributed by
Milan Oberkirch in bpo-20098(1).)

A new *note Message.get_content_disposition(): 6d6. 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: 6d7. 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: 6d8. constructor now accepts a *note
charset.Charset: 6d9. instance.  (Contributed by Claude Paroz and Berker
Peksag in bpo-16324(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20098

   (2) https://bugs.python.org/issue21083

   (3) https://tools.ietf.org/html/rfc6532.html

   (4) https://tools.ietf.org/html/rfc6531.html

   (5) https://bugs.python.org/issue24211

   (6) https://bugs.python.org/issue16324


File: python.info,  Node: enum<4>,  Next: faulthandler<2>,  Prev: email<2>,  Up: Improved Modules<4>

1.4.5.20 enum
.............

The *note Enum: 38c. 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>

(Contributed by Ethan Furman in bpo-21706(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue21706


File: python.info,  Node: faulthandler<2>,  Next: functools<3>,  Prev: enum<4>,  Up: Improved Modules<4>

1.4.5.21 faulthandler
.....................

The *note enable(): 54d, *note register(): 6dc, *note dump_traceback():
6dd. and *note dump_traceback_later(): 6de. 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/issue23566


File: python.info,  Node: functools<3>,  Next: glob,  Prev: faulthandler<2>,  Up: Improved Modules<4>

1.4.5.22 functools
..................

Most of the *note lru_cache(): 1c8. 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/issue14373


File: python.info,  Node: glob,  Next: gzip<2>,  Prev: functools<3>,  Up: Improved Modules<4>

1.4.5.23 glob
.............

The *note iglob(): 5cc. and *note glob(): 5cb. functions now support
recursive search in subdirectories, using the ‘"**"’ pattern.
(Contributed by Serhiy Storchaka in bpo-13968(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue13968


File: python.info,  Node: gzip<2>,  Next: heapq,  Prev: glob,  Up: Improved Modules<4>

1.4.5.24 gzip
.............

The `mode' argument of the *note GzipFile: 6e2. constructor now accepts
‘"x"’ to request exclusive creation.  (Contributed by Tim Heaney in
bpo-19222(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue19222


File: python.info,  Node: heapq,  Next: http,  Prev: gzip<2>,  Up: Improved Modules<4>

1.4.5.25 heapq
..............

Element comparison in *note merge(): 6e4. can now be customized by
passing a *note key function: 6e5. 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']

(Contributed by Raymond Hettinger in bpo-13742(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue13742


File: python.info,  Node: http,  Next: http client<3>,  Prev: heapq,  Up: Improved Modules<4>

1.4.5.26 http
.............

A new *note HTTPStatus: 6e7. 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/issue21793


File: python.info,  Node: http client<3>,  Next: idlelib and IDLE<3>,  Prev: http,  Up: Improved Modules<4>

1.4.5.27 http.client
....................

*note HTTPConnection.getresponse(): 6e9. now raises a *note
RemoteDisconnected: 6ea. exception when a remote server connection is
closed unexpectedly.  Additionally, if a *note ConnectionError: 6eb. (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

(Contributed by Martin Panter in bpo-3566(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue3566


File: python.info,  Node: idlelib and IDLE<3>,  Next: imaplib,  Prev: http client<3>,  Up: Improved Modules<4>

1.4.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,  Next: imghdr,  Prev: idlelib and IDLE<3>,  Up: Improved Modules<4>

1.4.5.29 imaplib
................

The *note IMAP4: 610. class now supports the *note context manager: 56d.
protocol.  When used in a *note with: 6ee. 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: 98. module now supports RFC 5161(2) (ENABLE
Extension) and RFC 6855(3) (UTF-8 Support) via the *note IMAP4.enable():
6ef. method.  A new *note IMAP4.utf8_enabled: 6f0. 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: 98. 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/issue4972

   (2) https://tools.ietf.org/html/rfc5161.html

   (3) https://tools.ietf.org/html/rfc6855.html

   (4) https://tools.ietf.org/html/rfc6855.html

   (5) https://bugs.python.org/issue21800

   (6) https://bugs.python.org/issue21800


File: python.info,  Node: imghdr,  Next: importlib<5>,  Prev: imaplib,  Up: Improved Modules<4>

1.4.5.30 imghdr
...............

The *note what(): 6f2. 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) http://www.openexr.com

   (2) https://bugs.python.org/issue20295

   (3) https://en.wikipedia.org/wiki/WebP

   (4) https://bugs.python.org/issue20197


File: python.info,  Node: importlib<5>,  Next: inspect<3>,  Prev: imghdr,  Up: Improved Modules<4>

1.4.5.31 importlib
..................

The *note util.LazyLoader: 558. 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(): 6f4. 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(): 6f5. function is now the
preferred way to create a new module.  As opposed to creating a *note
types.ModuleType: 6f6. 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/issue17621

   (2) https://bugs.python.org/issue21156

   (3) https://bugs.python.org/issue20383


File: python.info,  Node: inspect<3>,  Next: io<3>,  Prev: importlib<5>,  Up: Improved Modules<4>

1.4.5.32 inspect
................

Both the *note Signature: 6f8. and *note Parameter: 6f9. classes are now
picklable and hashable.  (Contributed by Yury Selivanov in bpo-20726(1)
and bpo-20334(2).)

A new *note BoundArguments.apply_defaults(): 6fa. 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', ())])

(Contributed by Yury Selivanov in bpo-24190(3).)

A new class method *note Signature.from_callable(): 6fb. makes
subclassing of *note Signature: 6f8. easier.  (Contributed by Yury
Selivanov and Eric Snow in bpo-17373(4).)

The *note signature(): 560. 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: 644. and
*note coroutine objects: 1a7. has been added: *note iscoroutine(): 6fc,
*note iscoroutinefunction(): 6fd, *note isawaitable(): 6fe, *note
getcoroutinelocals(): 6ff, and *note getcoroutinestate(): 700.
(Contributed by Yury Selivanov in bpo-24017(6) and bpo-24400(7).)

The *note stack(): 701, *note trace(): 702, *note getouterframes(): 703,
and *note getinnerframes(): 704. functions now return a list of named
tuples.  (Contributed by Daniel Shahaf in bpo-16808(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20726

   (2) https://bugs.python.org/issue20334

   (3) https://bugs.python.org/issue24190

   (4) https://bugs.python.org/issue17373

   (5) https://bugs.python.org/issue20691

   (6) https://bugs.python.org/issue24017

   (7) https://bugs.python.org/issue24400

   (8) https://bugs.python.org/issue16808


File: python.info,  Node: io<3>,  Next: ipaddress<2>,  Prev: inspect<3>,  Up: Improved Modules<4>

1.4.5.33 io
...........

A new *note BufferedIOBase.readinto1(): 706. method, that uses at most
one call to the underlying raw stream’s *note RawIOBase.read(): 707. or
*note RawIOBase.readinto(): 708. methods.  (Contributed by Nikolaus Rath
in bpo-20578(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20578


File: python.info,  Node: ipaddress<2>,  Next: json<2>,  Prev: io<3>,  Up: Improved Modules<4>

1.4.5.34 ipaddress
..................

Both the *note IPv4Network: 3a5. and *note IPv6Network: 3a4. 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')

(Contributed by Peter Moody and Antoine Pitrou in bpo-16531(1).)

A new ‘reverse_pointer’ attribute for the *note IPv4Network: 3a5. and
*note IPv6Network: 3a4. 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'

(Contributed by Leon Weber in bpo-20480(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16531

   (2) https://bugs.python.org/issue20480


File: python.info,  Node: json<2>,  Next: linecache,  Prev: ipaddress<2>,  Up: Improved Modules<4>

1.4.5.35 json
.............

The *note json.tool: a6. 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: 70b. instead of *note
ValueError: 1fc. to provide better context information about the error.
(Contributed by Serhiy Storchaka in bpo-19361(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue21650

   (2) https://bugs.python.org/issue19361


File: python.info,  Node: linecache,  Next: locale<3>,  Prev: json<2>,  Up: Improved Modules<4>

1.4.5.36 linecache
..................

A new *note lazycache(): 70d. function can be used to capture
information about a non-file-based module to permit getting its lines
later via *note getline(): 70e.  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/issue17911


File: python.info,  Node: locale<3>,  Next: logging<4>,  Prev: linecache,  Up: Improved Modules<4>

1.4.5.37 locale
...............

A new *note delocalize(): 710. 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'

(Contributed by Cédric Krier in bpo-13918(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue13918


File: python.info,  Node: logging<4>,  Next: lzma,  Prev: locale<3>,  Up: Improved Modules<4>

1.4.5.38 logging
................

All logging methods (*note Logger: 3ac. *note log(): 712, *note
exception(): 713, *note critical(): 714, *note debug(): 715, 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

(Contributed by Yury Selivanov in bpo-20537(1).)

The *note handlers.HTTPHandler: 716. class now accepts an optional *note
ssl.SSLContext: 3e9. instance to configure SSL settings used in an HTTP
connection.  (Contributed by Alex Gaynor in bpo-22788(2).)

The *note handlers.QueueListener: 717. 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/issue20537

   (2) https://bugs.python.org/issue22788


File: python.info,  Node: lzma,  Next: math<4>,  Prev: logging<4>,  Up: Improved Modules<4>

1.4.5.39 lzma
.............

The *note LZMADecompressor.decompress(): 719. 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/issue15955


File: python.info,  Node: math<4>,  Next: multiprocessing<4>,  Prev: lzma,  Up: Improved Modules<4>

1.4.5.40 math
.............

Two new constants have been added to the *note math: b2. module: *note
inf: 52d. and *note nan: 52e.  (Contributed by Mark Dickinson in
bpo-23185(1).)

A new function *note isclose(): 68b. provides a way to test for
approximate equality.  (Contributed by Chris Barker and Tal Einat in
bpo-24270(2).)

A new *note gcd(): 71b. function has been added.  The *note
fractions.gcd(): 71c. function is now deprecated.  (Contributed by Mark
Dickinson and Serhiy Storchaka in bpo-22486(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23185

   (2) https://bugs.python.org/issue24270

   (3) https://bugs.python.org/issue22486


File: python.info,  Node: multiprocessing<4>,  Next: operator,  Prev: math<4>,  Up: Improved Modules<4>

1.4.5.41 multiprocessing
........................

*note sharedctypes.synchronized(): 71e. objects now support the *note
context manager: 56d. protocol.  (Contributed by Charles-François Natali
in bpo-21565(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue21565


File: python.info,  Node: operator,  Next: os<5>,  Prev: multiprocessing<4>,  Up: Improved Modules<4>

1.4.5.42 operator
.................

*note attrgetter(): 720, *note itemgetter(): 262, and *note
methodcaller(): 721. objects now support pickling.  (Contributed by Josh
Rosenberg and Serhiy Storchaka in bpo-22955(1).)

New *note matmul(): 722. and *note imatmul(): 723. functions to perform
matrix multiplication.  (Contributed by Benjamin Peterson in
bpo-21176(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22955

   (2) https://bugs.python.org/issue21176


File: python.info,  Node: os<5>,  Next: pathlib<4>,  Prev: operator,  Up: Improved Modules<4>

1.4.5.43 os
...........

The new *note scandir(): 260. function returning an iterator of *note
DirEntry: 4f6. objects has been added.  If possible, *note scandir():
260. 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: 725. 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(): 4d6. 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(): 726. and *note set_blocking(): 727. functions
allow getting and setting a file descriptor’s blocking mode (*note
O_NONBLOCK: 728.)  (Contributed by Victor Stinner in bpo-22054(4).)

The *note truncate(): 729. and *note ftruncate(): 667. functions are now
supported on Windows.  (Contributed by Steve Dower in bpo-23668(5).)

There is a new *note os.path.commonpath(): 72a. function returning the
longest common sub-path of each passed pathname.  Unlike the *note
os.path.commonprefix(): 72b. 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'

(Contributed by Rafik Draoui and Serhiy Storchaka in bpo-10395(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22524

   (2) https://bugs.python.org/issue21719

   (3) https://bugs.python.org/issue22181

   (4) https://bugs.python.org/issue22054

   (5) https://bugs.python.org/issue23668

   (6) https://bugs.python.org/issue10395


File: python.info,  Node: pathlib<4>,  Next: pickle<3>,  Prev: os<5>,  Up: Improved Modules<4>

1.4.5.44 pathlib
................

The new *note Path.samefile(): 72d. method can be used to check whether
the path points to the same file as another path, which can be either
another *note Path: 202. object, or a string:

     >>> import pathlib
     >>> p1 = pathlib.Path('/etc/hosts')
     >>> p2 = pathlib.Path('/etc/../etc/hosts')
     >>> p1.samefile(p2)
     True

(Contributed by Vajrasky Kok and Antoine Pitrou in bpo-19775(1).)

The *note Path.mkdir(): 72e. method now accepts a new optional
`exist_ok' argument to match ‘mkdir -p’ and *note os.makedirs(): 3c2.
functionality.  (Contributed by Berker Peksag in bpo-21539(2).)

There is a new *note Path.expanduser(): 72f. method to expand ‘~’ and
‘~user’ prefixes.  (Contributed by Serhiy Storchaka and Claudiu Popa in
bpo-19776(3).)

A new *note Path.home(): 730. class method can be used to get a *note
Path: 202. instance representing the user’s home directory.
(Contributed by Victor Salgado and Mayank Tripathi in bpo-19777(4).)

New *note Path.write_text(): 731, *note Path.read_text(): 732, *note
Path.write_bytes(): 733, *note Path.read_bytes(): 734. 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

(Contributed by Christopher Welborn in bpo-20218(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue19775

   (2) https://bugs.python.org/issue21539

   (3) https://bugs.python.org/issue19776

   (4) https://bugs.python.org/issue19777

   (5) https://bugs.python.org/issue20218


File: python.info,  Node: pickle<3>,  Next: poplib,  Prev: pathlib<4>,  Up: Improved Modules<4>

1.4.5.45 pickle
...............

Nested objects, such as unbound methods or nested classes, can now be
pickled using *note pickle protocols: 573. 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/issue23611


File: python.info,  Node: poplib,  Next: re<4>,  Prev: pickle<3>,  Up: Improved Modules<4>

1.4.5.46 poplib
...............

A new *note POP3.utf8(): 737. 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://tools.ietf.org/html/rfc6856.html

   (2) https://bugs.python.org/issue21804


File: python.info,  Node: re<4>,  Next: readline<2>,  Prev: poplib,  Up: Improved Modules<4>

1.4.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'>

(Contributed by Serhiy Storchaka in 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(): 480. and *note subn(): 739. functions now replace
unmatched groups with empty strings instead of raising an exception.
(Contributed by Serhiy Storchaka in bpo-1519638(3).)

The *note re.error: 73a. exceptions have new attributes, *note msg: 73b,
*note pattern: 73c, *note pos: 73d, *note lineno: 73e, and *note colno:
73f, 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)

(Contributed by Serhiy Storchaka in bpo-22578(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue9179

   (2) https://bugs.python.org/issue22437

   (3) https://bugs.python.org/issue1519638

   (4) https://bugs.python.org/issue22578


File: python.info,  Node: readline<2>,  Next: selectors,  Prev: re<4>,  Up: Improved Modules<4>

1.4.5.48 readline
.................

A new *note append_history_file(): 741. 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/issue22940


File: python.info,  Node: selectors,  Next: shutil<2>,  Prev: readline<2>,  Up: Improved Modules<4>

1.4.5.49 selectors
..................

The new *note DevpollSelector: 453. supports efficient ‘/dev/poll’
polling on Solaris.  (Contributed by Giampaolo Rodola’ in bpo-18931(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue18931


File: python.info,  Node: shutil<2>,  Next: signal<2>,  Prev: selectors,  Up: Improved Modules<4>

1.4.5.50 shutil
...............

The *note move(): 25c. function now accepts a `copy_function' argument,
allowing, for example, the *note copy(): 25a. function to be used
instead of the default *note copy2(): 25b. if there is a need to ignore
file metadata when moving.  (Contributed by Claudiu Popa in
bpo-19840(1).)

The *note make_archive(): 21c. function now supports the `xztar' format.
(Contributed by Serhiy Storchaka in bpo-5411(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue19840

   (2) https://bugs.python.org/issue5411


File: python.info,  Node: signal<2>,  Next: smtpd,  Prev: shutil<2>,  Up: Improved Modules<4>

1.4.5.51 signal
...............

On Windows, the *note set_wakeup_fd(): 3d3. function now also supports
socket handles.  (Contributed by Victor Stinner in bpo-22018(1).)

Various ‘SIG*’ constants in the *note signal: eb. module have been
converted into *note Enums: 7b.  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/issue22018

   (2) https://bugs.python.org/issue21076


File: python.info,  Node: smtpd,  Next: smtplib,  Prev: signal<2>,  Up: Improved Modules<4>

1.4.5.52 smtpd
..............

Both the *note SMTPServer: 607. and *note SMTPChannel: 606. 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 *note SMTPServer.process_message(): 608.
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 *note SMTPServer: 607. 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 *note
SMTPServer.process_message(): 608. via the `mail_options' keyword.
(Contributed by Milan Oberkirch and R. David Murray in bpo-21795(3).)

The *note SMTPServer: 607. 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 *note SMTPServer.process_message(): 608. 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 *note SMTPServer: 607. constructor, and have it
successfully connect.  (Contributed by Milan Oberkirch in bpo-14758(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue19662

   (2) https://tools.ietf.org/html/rfc6152.html

   (3) https://bugs.python.org/issue21795

   (4) https://tools.ietf.org/html/rfc6531.html

   (5) https://bugs.python.org/issue21725

   (6) https://bugs.python.org/issue14758


File: python.info,  Node: smtplib,  Next: sndhdr,  Prev: smtpd,  Up: Improved Modules<4>

1.4.5.53 smtplib
................

A new *note SMTP.auth(): 747. method provides a convenient way to
implement custom authentication mechanisms.  (Contributed by Milan
Oberkirch in bpo-15014(1).)

The *note SMTP.set_debuglevel(): 748. 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(): 749. and *note SMTP.send_message(): 74a.
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/issue15014

   (2) https://bugs.python.org/issue16914

   (3) https://tools.ietf.org/html/rfc6531.html

   (4) https://bugs.python.org/issue22027


File: python.info,  Node: sndhdr,  Next: socket<5>,  Prev: smtplib,  Up: Improved Modules<4>

1.4.5.54 sndhdr
...............

The *note what(): 74c. and *note whathdr(): 74d. functions now return a
*note namedtuple(): 1b8.  (Contributed by Claudiu Popa in bpo-18615(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue18615


File: python.info,  Node: socket<5>,  Next: ssl<6>,  Prev: sndhdr,  Up: Improved Modules<4>

1.4.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(): 74f. method allows sending a file over a
socket by using the high-performance *note os.sendfile(): 35e. function
on UNIX, resulting in uploads being from 2 to 3 times faster than when
using plain *note socket.send(): 67f.  (Contributed by Giampaolo Rodola’
in bpo-17552(2).)

The *note socket.sendall(): 680. 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(): 750. method is now
optional.  By default it is set to *note SOMAXCONN: 751. or to ‘128’,
whichever is less.  (Contributed by Charles-François Natali in
bpo-21455(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22043

   (2) https://bugs.python.org/issue17552

   (3) https://bugs.python.org/issue23853

   (4) https://bugs.python.org/issue21455


File: python.info,  Node: ssl<6>,  Next: sqlite3<3>,  Prev: socket<5>,  Up: Improved Modules<4>

1.4.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<6>

1.4.5.57 Memory BIO Support
...........................

(Contributed by Geert Jansen in bpo-21965(1).)

The new *note SSLObject: 3e8. class has been added to provide SSL
protocol support for cases when the network I/O capabilities of *note
SSLSocket: 3e7. 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: 754. 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:
3e7.’s readiness model ("select/poll") is inefficient.

A new *note SSLContext.wrap_bio(): 3eb. method can be used to create a
new ‘SSLObject’ instance.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue21965


File: python.info,  Node: Application-Layer Protocol Negotiation Support,  Next: Other Changes,  Prev: Memory BIO Support,  Up: ssl<6>

1.4.5.58 Application-Layer Protocol Negotiation Support
.......................................................

(Contributed by Benjamin Peterson in bpo-20188(1).)

Where OpenSSL support is present, the *note ssl: f4. module now
implements the `Application-Layer Protocol Negotiation' TLS extension as
described in RFC 7301(2).

The new *note SSLContext.set_alpn_protocols(): 756. can be used to
specify which protocols a socket should advertise during the TLS
handshake.

The new *note SSLSocket.selected_alpn_protocol(): 757. returns the
protocol that was selected during the TLS handshake.  The *note
HAS_ALPN: 758. flag indicates whether ALPN support is present.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20188

   (2) https://tools.ietf.org/html/rfc7301.html


File: python.info,  Node: Other Changes,  Prev: Application-Layer Protocol Negotiation Support,  Up: ssl<6>

1.4.5.59 Other Changes
......................

There is a new *note SSLSocket.version(): 75a. method to query the
actual protocol version in use.  (Contributed by Antoine Pitrou in
bpo-20421(1).)

The *note SSLSocket: 3e7. 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: 75b. or *note ssl.SSLWantWriteError: 75c.
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(): 75d. 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: 185.  (Contributed by Akira Li in
bpo-19940(5).)

New ‘SSLObject.shared_ciphers()’ and *note SSLSocket.shared_ciphers():
75e. 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(): 75f, *note SSLSocket.read(): 760,
‘SSLSocket.shutdown()’, and *note SSLSocket.write(): 761. methods of the
*note SSLSocket: 3e7. 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 *note match_hostname(): 3e1. function now supports matching of IP
addresses.  (Contributed by Antoine Pitrou in bpo-23239(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20421

   (2) https://bugs.python.org/issue17552

   (3) https://bugs.python.org/issue20951

   (4) https://tools.ietf.org/html/rfc5280.html

   (5) https://bugs.python.org/issue19940

   (6) https://bugs.python.org/issue23186

   (7) https://bugs.python.org/issue23853

   (8) https://bugs.python.org/issue23239


File: python.info,  Node: sqlite3<3>,  Next: subprocess<3>,  Prev: ssl<6>,  Up: Improved Modules<4>

1.4.5.60 sqlite3
................

The *note Row: 763. class now fully supports the sequence protocol, in
particular *note reversed(): 18f. 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/issue10203

   (2) https://bugs.python.org/issue13583


File: python.info,  Node: subprocess<3>,  Next: sys<5>,  Prev: sqlite3<3>,  Up: Improved Modules<4>

1.4.5.61 subprocess
...................

The new *note run(): 3f2. function has been added.  It runs the
specified command and returns a *note CompletedProcess: 765. 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).)

Examples:

     >>> subprocess.run(["ls", "-l"])  # doesn't capture output
     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/issue23342


File: python.info,  Node: sys<5>,  Next: sysconfig,  Prev: subprocess<3>,  Up: Improved Modules<4>

1.4.5.62 sys
............

A new ‘set_coroutine_wrapper()’ function allows setting a global hook
that will be called whenever a *note coroutine object: 1a7. is created
by an *note async def: 285. function.  A corresponding
‘get_coroutine_wrapper()’ can be used to obtain a currently set wrapper.
Both functions are *note provisional: 34d, and are intended for
debugging purposes only.  (Contributed by Yury Selivanov in
bpo-24017(1).)

A new *note is_finalizing(): 767. function can be used to check if the
Python interpreter is *note shutting down: 768.  (Contributed by Antoine
Pitrou in bpo-22696(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue24017

   (2) https://bugs.python.org/issue22696


File: python.info,  Node: sysconfig,  Next: tarfile<2>,  Prev: sys<5>,  Up: Improved Modules<4>

1.4.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/issue23437


File: python.info,  Node: tarfile<2>,  Next: threading<3>,  Prev: sysconfig,  Up: Improved Modules<4>

1.4.5.64 tarfile
................

The `mode' argument of the *note open(): 76b. function now accepts ‘"x"’
to request exclusive creation.  (Contributed by Berker Peksag in
bpo-21717(1).)

The *note TarFile.extractall(): 76c. and *note TarFile.extract(): 76d.
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(): 76e. now accepts an optional `members' keyword
argument that can be set to a subset of the list returned by *note
TarFile.getmembers(): 76f.  (Contributed by Serhiy Storchaka in
bpo-21549(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue21717

   (2) https://bugs.python.org/issue23193

   (3) https://bugs.python.org/issue21549


File: python.info,  Node: threading<3>,  Next: time<4>,  Prev: tarfile<2>,  Up: Improved Modules<4>

1.4.5.65 threading
..................

Both the *note Lock.acquire(): 771. and *note RLock.acquire(): 772.
methods now use a monotonic clock for timeout management.  (Contributed
by Victor Stinner in bpo-22043(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22043


File: python.info,  Node: time<4>,  Next: timeit<2>,  Prev: threading<3>,  Up: Improved Modules<4>

1.4.5.66 time
.............

The *note monotonic(): 774. function is now always available.
(Contributed by Victor Stinner in bpo-22043(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22043


File: python.info,  Node: timeit<2>,  Next: tkinter<5>,  Prev: time<4>,  Up: Improved Modules<4>

1.4.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(): 776. 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/issue18983

   (2) https://bugs.python.org/issue2527


File: python.info,  Node: tkinter<5>,  Next: traceback<2>,  Prev: timeit<2>,  Up: Improved Modules<4>

1.4.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/issue20035


File: python.info,  Node: traceback<2>,  Next: types<2>,  Prev: tkinter<5>,  Up: Improved Modules<4>

1.4.5.69 traceback
..................

New *note walk_stack(): 779. and *note walk_tb(): 77a. functions to
conveniently traverse frame and traceback objects.  (Contributed by
Robert Collins in bpo-17911(1).)

New lightweight classes: *note TracebackException: 77b, *note
StackSummary: 77c, and *note FrameSummary: 77d.  (Contributed by Robert
Collins in bpo-17911(2).)

Both the *note print_tb(): 77e. and *note print_stack(): 77f. functions
now support negative values for the `limit' argument.  (Contributed by
Dmitry Kazakov in bpo-22619(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17911

   (2) https://bugs.python.org/issue17911

   (3) https://bugs.python.org/issue22619


File: python.info,  Node: types<2>,  Next: unicodedata<4>,  Prev: traceback<2>,  Up: Improved Modules<4>

1.4.5.70 types
..............

A new *note coroutine(): 781. function to transform *note generator:
45c. and *note generator-like: 6ba. objects into *note awaitables: 51e.
(Contributed by Yury Selivanov in bpo-24017(1).)

A new type called *note CoroutineType: 782, which is used for *note
coroutine: 1a7. objects created by *note async def: 285. functions.
(Contributed by Yury Selivanov in bpo-24400(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue24017

   (2) https://bugs.python.org/issue24400


File: python.info,  Node: unicodedata<4>,  Next: unittest<3>,  Prev: types<2>,  Up: Improved Modules<4>

1.4.5.71 unicodedata
....................

The *note unicodedata: 11b. module now uses data from Unicode 8.0.0(1).

   ---------- Footnotes ----------

   (1) http://unicode.org/versions/Unicode8.0.0/


File: python.info,  Node: unittest<3>,  Next: unittest mock<3>,  Prev: unicodedata<4>,  Up: Improved Modules<4>

1.4.5.72 unittest
.................

The *note TestLoader.loadTestsFromModule(): 785. 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: 786. attribute of the *note TestLoader: 787.
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/issue16662

   (2) https://bugs.python.org/issue19746

   (3) https://bugs.python.org/issue22936


File: python.info,  Node: unittest mock<3>,  Next: urllib,  Prev: unittest<3>,  Up: Improved Modules<4>

1.4.5.73 unittest.mock
......................

The *note Mock: 24a. class has the following improvements:

   * The class constructor has a new `unsafe' parameter, which causes
     mock objects to raise *note AttributeError: 3a0. on attribute names
     starting with ‘"assert"’.  (Contributed by Kushal Das in
     bpo-21238(1).)

   * A new *note Mock.assert_not_called(): 789. method to check if the
     mock object was called.  (Contributed by Kushal Das in
     bpo-21262(2).)

The *note MagicMock: 78a. class now supports *note __truediv__(): 78b,
*note __divmod__(): 78c. and *note __matmul__(): 64d. 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(): 78d. function when patching builtin names.  (Contributed by
Kushal Das in bpo-17660(6).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue21238

   (2) https://bugs.python.org/issue21262

   (3) https://bugs.python.org/issue20968

   (4) https://bugs.python.org/issue23581

   (5) https://bugs.python.org/issue23568

   (6) https://bugs.python.org/issue17660


File: python.info,  Node: urllib,  Next: wsgiref,  Prev: unittest mock<3>,  Up: Improved Modules<4>

1.4.5.74 urllib
...............

A new *note request.HTTPPasswordMgrWithPriorAuth: 78f. 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(): 790.
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(): 791. function accepts an *note
ssl.SSLContext: 3e9. 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(): 792. 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/issue19494

   (2) https://bugs.python.org/issue7159

   (3) https://bugs.python.org/issue13866

   (4) https://bugs.python.org/issue22366

   (5) https://tools.ietf.org/html/rfc3986.html

   (6) https://tools.ietf.org/html/rfc1808.html

   (7) https://tools.ietf.org/html/rfc2396.html

   (8) https://bugs.python.org/issue22118


File: python.info,  Node: wsgiref,  Next: xmlrpc<2>,  Prev: urllib,  Up: Improved Modules<4>

1.4.5.75 wsgiref
................

The `headers' argument of the *note headers.Headers: 794. class
constructor is now optional.  (Contributed by Pablo Torres Navarrete and
SilentGhost in bpo-5800(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue5800


File: python.info,  Node: xmlrpc<2>,  Next: xml sax,  Prev: wsgiref,  Up: Improved Modules<4>

1.4.5.76 xmlrpc
...............

The *note client.ServerProxy: 256. class now supports the *note context
manager: 56d. protocol.  (Contributed by Claudiu Popa in bpo-20627(1).)

The *note client.ServerProxy: 256. constructor now accepts an optional
*note ssl.SSLContext: 3e9. instance.  (Contributed by Alex Gaynor in
bpo-22960(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20627

   (2) https://bugs.python.org/issue22960


File: python.info,  Node: xml sax,  Next: zipfile<3>,  Prev: xmlrpc<2>,  Up: Improved Modules<4>

1.4.5.77 xml.sax
................

SAX parsers now support a character stream of the *note
xmlreader.InputSource: 797. object.  (Contributed by Serhiy Storchaka in
bpo-2175(1).)

*note parseString(): 798. now accepts a *note str: 335. instance.
(Contributed by Serhiy Storchaka in bpo-10590(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue2175

   (2) https://bugs.python.org/issue10590


File: python.info,  Node: zipfile<3>,  Prev: xml sax,  Up: Improved Modules<4>

1.4.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(): 5c1. method now accepts
‘"x"’ to request exclusive creation.  (Contributed by Serhiy Storchaka
in bpo-21717(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23252

   (2) https://bugs.python.org/issue21717


File: python.info,  Node: Other module-level changes,  Next: Optimizations<4>,  Prev: Improved Modules<4>,  Up: Python 3 5 有什麼新功能

1.4.6 Other module-level changes
--------------------------------

Many functions in the *note mmap: b4, *note ossaudiodev: c7, *note
socket: f0, *note ssl: f4, and *note codecs: 1c. modules now accept
writable *note bytes-like objects: 5ed.  (Contributed by Serhiy
Storchaka in bpo-23001(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23001


File: python.info,  Node: Optimizations<4>,  Next: Build and C API Changes<3>,  Prev: Other module-level changes,  Up: Python 3 5 有什麼新功能

1.4.7 Optimizations
-------------------

The *note os.walk(): 659. 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(): 260. 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: a3. *note IPv4Network: 3a5. and
*note IPv6Network: 3a4. have been massively sped up, such as *note
subnets(): 79c, *note supernet(): 79d, *note summarize_address_range():
79e, *note collapse_addresses(): 79f.  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: a3. objects was optimized to produce
significantly smaller output.  (Contributed by Serhiy Storchaka in
bpo-23133(7).)

Many operations on *note io.BytesIO: 7a0. 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(): 7a1. 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(): 60a. 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(): 7a2. and *note PyObject_IsSubclass():
7a3. functions have been sped up in the common case that the second
argument has *note type: 60d. 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: dd. module now use 50% less memory on
64-bit builds.  (Contributed by Serhiy Storchaka in bpo-23488(17).)

The *note property(): 1d8. getter calls are up to 25% faster.
(Contributed by Joe Jevnik in bpo-23910(18).)

Instantiation of *note fractions.Fraction: 186. is now up to 30% faster.
(Contributed by Stefan Behnel in bpo-22464(19).)

String methods *note find(): 7a4, *note rfind(): 7a5, *note split():
7a6, *note partition(): 7a7. and the *note in: 7a8. 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/issue23605

   (2) https://bugs.python.org/issue21233

   (3) https://bugs.python.org/issue21486

   (4) https://bugs.python.org/issue21487

   (5) https://bugs.python.org/issue20826

   (6) https://bugs.python.org/issue23266

   (7) https://bugs.python.org/issue23133

   (8) https://bugs.python.org/issue15381

   (9) https://bugs.python.org/issue22003

   (10) https://bugs.python.org/issue20416

   (11) https://bugs.python.org/issue23344

   (12) https://bugs.python.org/issue15027

   (13) https://bugs.python.org/issue19380

   (14) https://bugs.python.org/issue23206

   (15) https://bugs.python.org/issue22540

   (16) https://bugs.python.org/issue22847

   (17) https://bugs.python.org/issue23488

   (18) https://bugs.python.org/issue23910

   (19) https://bugs.python.org/issue22464

   (20) https://bugs.python.org/issue23573


File: python.info,  Node: Build and C API Changes<3>,  Next: Deprecated<3>,  Prev: Optimizations<4>,  Up: Python 3 5 有什麼新功能

1.4.8 Build and C API Changes
-----------------------------

New ‘calloc’ functions were added:

   * *note PyMem_RawCalloc(): 7aa,

   * *note PyMem_Calloc(): 7ab,

   * *note PyObject_Calloc(): 7ac.

(Contributed by Victor Stinner in bpo-21233(1).)

New encoding/decoding helper functions:

   * *note Py_DecodeLocale(): 441. (replaced ‘_Py_char2wchar()’),

   * *note Py_EncodeLocale(): 442. (replaced ‘_Py_wchar2char()’).

(Contributed by Victor Stinner in bpo-18395(2).)

A new *note PyCodec_NameReplaceErrors(): 7ad. function to replace the
unicode encode error with ‘\N{...}’ escapes.  (Contributed by Serhiy
Storchaka in bpo-19676(3).)

A new *note PyErr_FormatV(): 7ae. function similar to *note
PyErr_Format(): 7af, 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(): 7b0, *note
PyModule_FromDefAndSpec2(): 7b1, and *note PyModule_ExecDef(): 7b2.
functions introduced by PEP 489(6) – multi-phase extension module
initialization.  (Contributed by Petr Viktorin in bpo-24268(7).)

New *note PyNumber_MatrixMultiply(): 7b3. and *note
PyNumber_InPlaceMatrixMultiply(): 7b4. 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: 2d8. 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/issue21233

   (2) https://bugs.python.org/issue18395

   (3) https://bugs.python.org/issue19676

   (4) https://bugs.python.org/issue18711

   (5) https://bugs.python.org/issue19235

   (6) https://www.python.org/dev/peps/pep-0489

   (7) https://bugs.python.org/issue24268

   (8) https://bugs.python.org/issue21176

   (9) https://www.python.org/dev/peps/pep-0465

   (10) https://www.visualstudio.com/


File: python.info,  Node: Deprecated<3>,  Next: Removed<2>,  Prev: Build and C API Changes<3>,  Up: Python 3 5 有什麼新功能

1.4.9 Deprecated
----------------

* Menu:

* New Keywords: New Keywords<2>.
* 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<2>,  Next: Deprecated Python Behavior<2>,  Up: Deprecated<3>

1.4.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://www.python.org/dev/peps/pep-0492


File: python.info,  Node: Deprecated Python Behavior<2>,  Next: Unsupported Operating Systems,  Prev: New Keywords<2>,  Up: Deprecated<3>

1.4.9.2 Deprecated Python Behavior
..................................

Raising the *note StopIteration: 48b. exception inside a generator will
now generate a silent *note PendingDeprecationWarning: 27a, which will
become a non-silent deprecation warning in Python 3.6 and will trigger a
*note RuntimeError: 2bb. in Python 3.7.  See *note PEP 479; Change
StopIteration handling inside generators: 5dc. for details.


File: python.info,  Node: Unsupported Operating Systems,  Next: Deprecated Python modules functions and methods<3>,  Prev: Deprecated Python Behavior<2>,  Up: Deprecated<3>

1.4.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://www.python.org/dev/peps/pep-0011


File: python.info,  Node: Deprecated Python modules functions and methods<3>,  Prev: Unsupported Operating Systems,  Up: Deprecated<3>

1.4.9.4 Deprecated Python modules, functions and methods
........................................................

The *note formatter: 82. 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(): 51c.

The *note smtpd: ed. 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 *note SMTPServer: 607.
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: 492, *note value: 493. and
*note coded_value: 494. of *note http.cookies.Morsel: 495. objects is
deprecated.  Use the *note set(): 496. method instead.  In addition, the
undocumented `LegalChars' parameter of *note set(): 496. is deprecated,
and is now ignored.

Passing a format string as keyword argument `format_string' to the *note
format(): 491. method of the *note string.Formatter: 7ba. 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: 6f8. are deprecated.  Use the new *note
Signature.from_callable(): 6fb. method instead.  (Contributed by Yury
Selivanov in bpo-24248(3).)

The *note inspect.getargspec(): 561. function is deprecated and
scheduled to be removed in Python 3.6.  (See bpo-20438(4) for details.)

The *note inspect: a1. *note getfullargspec(): 562, *note getcallargs():
7bb, and *note formatargspec(): 7bc. functions are deprecated in favor
of the *note inspect.signature(): 560. API. (Contributed by Yury
Selivanov in bpo-20438(5).)

*note getargvalues(): 7bd. and *note formatargvalues(): 7be. functions
were inadvertently marked as deprecated with the release of Python
3.5.0.

Use of *note re.LOCALE: 3ce. flag with str patterns or *note re.ASCII:
3cd. 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(): 785. method now is
deprecated and ignored.  (Contributed by Robert Collins and Barry A.
Warsaw in bpo-16662(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23671

   (2) https://bugs.python.org/issue1322

   (3) https://bugs.python.org/issue24248

   (4) https://bugs.python.org/issue20438

   (5) https://bugs.python.org/issue20438

   (6) https://bugs.python.org/issue22407

   (7) https://bugs.python.org/issue23622

   (8) https://bugs.python.org/issue16662


File: python.info,  Node: Removed<2>,  Next: Porting to Python 3 5,  Prev: Deprecated<3>,  Up: Python 3 5 有什麼新功能

1.4.10 Removed
--------------

* Menu:

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


File: python.info,  Node: API and Feature Removals<4>,  Up: Removed<2>

1.4.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: 84. 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: a. 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/issue6623

   (2) https://bugs.python.org/issue23464


File: python.info,  Node: Porting to Python 3 5,  Next: Notable changes in Python 3 5 4,  Prev: Removed<2>,  Up: Python 3 5 有什麼新功能

1.4.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<4>.
* Changes in the C API: Changes in the C API<4>.


File: python.info,  Node: Changes in Python behavior<2>,  Next: Changes in the Python API<4>,  Up: Porting to Python 3 5

1.4.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: 45d, 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<4>,  Next: Changes in the C API<4>,  Prev: Changes in Python behavior<2>,  Up: Porting to Python 3 5

1.4.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: 65e. if the
     Python signal handler does not raise an exception.

   * Before Python 3.5, a *note datetime.time: 4f8. 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: 75b. or *note ssl.SSLWantWriteError: 75c. 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: 7c4,
     ‘HTMLParser.error()’, and the ‘HTMLParserError’ exception have been
     removed.  (Contributed by Ezio Melotti in bpo-15114(5).)  The
     `convert_charrefs' argument of *note HTMLParser: 7c4. 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: 5ed. 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: 7c5. will no longer be raised
     and instead *note find_spec(): 7c6. will return ‘None’ `without'
     caching ‘None’ in *note sys.path_importer_cache: 4a2, which is
     different than the typical case (bpo-22834(8)).

   * HTTP status code and messages from *note http.client: 94. and *note
     http.server: 97. were refactored into a common *note HTTPStatus:
     6e7. enum.  The values in *note http.client: 94. and *note
     http.server: 97. 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:
     279. now, will be an error in Python 3.6).  If the loader inherits
     from *note importlib.abc.Loader: 7c7. 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(): 3cf. 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(): 3cf. 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: 495. dict-like interface has been
     made self consistent: morsel comparison now takes the *note key:
     492. and *note value: 493. into account, *note copy(): 7c8. now
     results in a *note Morsel: 495. instance rather than a *note dict:
     1b9, and *note update(): 7c9. 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(): 496. 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(): 55c. 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: f0. module now exports the *note
     CAN_RAW_FD_FRAMES: 7ca. constant on linux 3.6 and greater.

   * The *note ssl.cert_time_to_seconds(): 75d. 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: 185.
     (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: ee. module now uses *note sys.stderr: 314.
     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(): 7cb. and *note str.endswith(): 7cc.
     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(): 1d7. 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: da. module and the *note
     help(): 577. function.  (Contributed by Serhiy Storchaka in
     bpo-15582(17).)

   * Nested *note functools.partial(): 7cd. calls are now flattened.  If
     you were relying on the previous behavior, you can now either add
     an attribute to a *note functools.partial(): 7cd. object or you can
     create a subclass of *note functools.partial(): 7cd.  (Contributed
     by Alexander Belopolsky in bpo-7830(18).)

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0475

   (2) https://bugs.python.org/issue13936

   (3) https://bugs.python.org/issue20951

   (4) https://bugs.python.org/issue21205

   (5) https://bugs.python.org/issue15114

   (6) https://bugs.python.org/issue21047

   (7) https://bugs.python.org/issue16518

   (8) https://bugs.python.org/issue22834

   (9) https://bugs.python.org/issue21793

   (10) https://bugs.python.org/issue23014

   (11) https://bugs.python.org/issue22818

   (12) https://bugs.python.org/issue2211

   (13) https://www.python.org/dev/peps/pep-0488

   (14) https://tools.ietf.org/html/rfc5280.html

   (15) https://bugs.python.org/issue19940

   (16) https://bugs.python.org/issue24284

   (17) https://bugs.python.org/issue15582

   (18) https://bugs.python.org/issue7830


File: python.info,  Node: Changes in the C API<4>,  Prev: Changes in the Python API<4>,  Up: Porting to Python 3 5

1.4.11.3 Changes in the 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: 7cf. and a new ‘calloc’ field was added.

   * Removed non-documented macro ‘PyObject_REPR’ which leaked
     references.  Use format character ‘%R’ in *note
     PyUnicode_FromFormat(): 7d0.-like functions to format the *note
     repr(): 7d1. 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: 2d7. was replaced with a ‘tp_as_async’ slot.
     Refer to *note Coroutine Objects: 7d2. for new types, structures
     and functions.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22453

   (2) https://bugs.python.org/issue20204

   (3) https://www.python.org/dev/peps/pep-0492


File: python.info,  Node: Notable changes in Python 3 5 4,  Prev: Porting to Python 3 5,  Up: Python 3 5 有什麼新功能

1.4.12 Notable changes in 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: Notable changes in Python 3 5 4

1.4.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.

(Contributed by Victor Stinner in bpo-23404(2).)

3.5.4 版新加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Makefile.pre.in

   (2) https://bugs.python.org/issue23404


File: python.info,  Node: Removal of make touch build target<2>,  Prev: New make regen-all build target<2>,  Up: Notable changes in Python 3 5 4

1.4.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.

(Contributed by Victor Stinner in bpo-23404(1).)

3.5.4 版更變.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23404


File: python.info,  Node: What's New In Python 3 4,  Next: What's New In Python 3 3,  Prev: Python 3 5 有什麼新功能,  Up: Python 有什麼新功能？

1.5 What’s New In Python 3.4
============================


Author: R. David Murray <<rdmurray@bitdance.com>> (Editor)

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<2>. Release Highlights
* New Features: New Features<5>.
* New Modules: New Modules<5>.
* Improved Modules: Improved Modules<5>.
* CPython Implementation Changes::
* Deprecated: Deprecated<4>.
* Removed: Removed<3>.
* Porting to Python 3.4: Porting to Python 3 4.
* Changed in 3.4.3: Changed in 3 4 3.

   ---------- Footnotes ----------

   (1) https://docs.python.org/3.4/whatsnew/changelog.html

   (2) https://www.python.org/dev/peps/pep-0429


File: python.info,  Node: Summary -- Release Highlights<2>,  Next: New Features<5>,  Up: What's New In Python 3 4

1.5.1 Summary – Release Highlights
----------------------------------

New syntax features:

   * No new syntax features were added in Python 3.4.

Other new features:

   * *note pip should always be available: 7d9. ( PEP 453(1)).

   * *note Newly created file descriptors are non-inheritable: 7da. (
     PEP 446(2)).

   * command line option for *note isolated mode: 7db. (bpo-16499(3)).

   * *note improvements in the handling of codecs: 7dc. that are not
     text encodings (multiple issues).

   * *note A ModuleSpec Type: 7dd. for the Import System ( PEP 451(4)).
     (Affects importer authors.)

   * The *note marshal: b1. format has been made *note more compact and
     efficient: 7de. (bpo-16475(5)).

New library modules:

   * *note asyncio: a.: *note New provisional API for asynchronous IO:
     7df. ( PEP 3156(6)).

   * *note ensurepip: 7a.: *note Bootstrapping the pip installer: 7e0. (
     PEP 453(7)).

   * *note enum: 7b.: *note Support for enumeration types: 7e1. ( PEP
     435(8)).

   * *note pathlib: c9.: *note Object-oriented filesystem paths: 7e2. (
     PEP 428(9)).

   * *note selectors: e7.: *note High-level and efficient I/O
     multiplexing: 7e3, built upon the *note select: e6. module
     primitives (part of PEP 3156(10)).

   * *note statistics: f6.: A basic *note numerically stable statistics
     library: 7e4. ( PEP 450(11)).

   * *note tracemalloc: 115.: *note Trace Python memory allocations:
     7e5. ( PEP 454(12)).

Significantly improved library modules:

   * *note Single-dispatch generic functions: 7e6. in *note functools:
     85. ( PEP 443(13)).

   * New *note pickle: cb. *note protocol 4: 7e7. ( PEP 3154(14)).

   * *note multiprocessing: b8. now has *note an option to avoid using
     os.fork on Unix: 7e8. (bpo-8713(15)).

   * *note email: 69. has a new submodule, *note contentmanager: 6b, and
     a new *note Message: 546. subclass (‘EmailMessage’) that *note
     simplify MIME handling: 7e9. (bpo-18891(16)).

   * The *note inspect: a1. and *note pydoc: da. modules are now capable
     of correct introspection of a much wider variety of callable
     objects, which improves the output of the Python *note help(): 577.
     system.

   * The *note ipaddress: a3. module API has been declared stable

Security improvements:

   * *note Secure and interchangeable hash algorithm: 7ea. ( PEP
     456(17)).

   * *note Make newly created file descriptors non-inheritable: 7da. (
     PEP 446(18)) to avoid leaking file descriptors to child processes.

   * New command line option for *note isolated mode: 7db,
     (bpo-16499(19)).

   * *note multiprocessing: b8. now has *note an option to avoid using
     os.fork on Unix: 7e8.  `spawn' and `forkserver' are more secure
     because they avoid sharing data with child processes.

   * *note multiprocessing: b8. child processes on Windows no longer
     inherit all of the parent’s inheritable handles, only the necessary
     ones.

   * A new *note hashlib.pbkdf2_hmac(): 7eb. function provides the
     PKCS#5 password-based key derivation function 2(20).

   * *note TLSv1.1 and TLSv1.2 support: 7ec. for *note ssl: f4.

   * *note Retrieving certificates from the Windows system cert store
     support: 7ed. for *note ssl: f4.

   * *note Server-side SNI (Server Name Indication) support: 7ee. for
     *note ssl: f4.

   * The *note ssl.SSLContext: 3e9. class has a *note lot of
     improvements: 7ef.

   * All modules in the standard library that support SSL now support
     server certificate verification, including hostname matching (*note
     ssl.match_hostname(): 3e1.) and CRLs (Certificate Revocation lists,
     see *note ssl.SSLContext.load_verify_locations(): 7f0.).

CPython implementation improvements:

   * *note Safe object finalization: 7f1. ( PEP 442(21)).

   * Leveraging PEP 442(22), in most cases *note module globals are no
     longer set to None during finalization: 7f1. (bpo-18214(23)).

   * *note Configurable memory allocators: 7f2. ( PEP 445(24)).

   * *note Argument Clinic: 7f3. ( 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://www.python.org/dev/peps/pep-0453

   (2) https://www.python.org/dev/peps/pep-0446

   (3) https://bugs.python.org/issue16499

   (4) https://www.python.org/dev/peps/pep-0451

   (5) https://bugs.python.org/issue16475

   (6) https://www.python.org/dev/peps/pep-3156

   (7) https://www.python.org/dev/peps/pep-0453

   (8) https://www.python.org/dev/peps/pep-0435

   (9) https://www.python.org/dev/peps/pep-0428

   (10) https://www.python.org/dev/peps/pep-3156

   (11) https://www.python.org/dev/peps/pep-0450

   (12) https://www.python.org/dev/peps/pep-0454

   (13) https://www.python.org/dev/peps/pep-0443

   (14) https://www.python.org/dev/peps/pep-3154

   (15) https://bugs.python.org/issue8713

   (16) https://bugs.python.org/issue18891

   (17) https://www.python.org/dev/peps/pep-0456

   (18) https://www.python.org/dev/peps/pep-0446

   (19) https://bugs.python.org/issue16499

   (20) https://en.wikipedia.org/wiki/PBKDF2

   (21) https://www.python.org/dev/peps/pep-0442

   (22) https://www.python.org/dev/peps/pep-0442

   (23) https://bugs.python.org/issue18214

   (24) https://www.python.org/dev/peps/pep-0445

   (25) https://www.python.org/dev/peps/pep-0436


File: python.info,  Node: New Features<5>,  Next: New Modules<5>,  Prev: Summary -- Release Highlights<2>,  Up: What's New In Python 3 4

1.5.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.
* Other Language Changes: Other Language Changes<5>.


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<5>

1.5.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.5.2.2 Bootstrapping pip By Default
....................................

The new *note ensurepip: 7a. 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: 126. module make
use of the *note ensurepip: 7a. 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: 126. module *note
API: 7f7. installation of ‘pip’ must be requested explicitly.

For CPython *note source builds on POSIX systems: 7f8, 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://www.python.org/dev/peps/pep-0453

   (2) 
https://www.python.org/dev/peps/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.5.2.3 Documentation Changes
.............................

As part of this change, the *note 安裝 Python 模組: 7fa. and *note 發布
Python 模組: 7fb. 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 安裝 Python
模組（舊版）: 7fc. and *note 發布 Python 模組（舊版）: 7fd.

也參考
......

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://www.python.org/dev/peps/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<5>

1.5.2.4 PEP 446: Newly Created File Descriptors Are Non-Inheritable
...................................................................

PEP 446(1) makes newly created file descriptors *note non-inheritable:
7ff.  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(): 800, *note os.set_inheritable(): 801.

   * *note os.get_handle_inheritable(): 802, *note
     os.set_handle_inheritable(): 803.

   * *note socket.socket.get_inheritable(): 804, *note
     socket.socket.set_inheritable(): 805.

也參考
......

PEP 446(2) – Make newly created file descriptors non-inheritable

     PEP written and implemented by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0446

   (2) https://www.python.org/dev/peps/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<5>

1.5.2.5 Improvements to Codec Handling
......................................

Since it was first introduced, the *note codecs: 1c. 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: 335, *note bytes: 336. and *note bytearray: 337. types, has
historically obscured that fact.

As a key step in clarifying the situation, the *note codecs.encode():
807. and *note codecs.decode(): 808. convenience functions are now
properly documented in Python 2.7, 3.3 and 3.4.  These functions have
existed in the *note codecs: 1c. 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: 335, *note bytes: 336. and
*note bytearray: 337, the *note codecs: 1c. 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: 809. and *note Text Transforms:
80a.

(Contributed by Nick Coghlan in bpo-7475(1), bpo-17827(2), bpo-17828(3)
and bpo-19619(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue7475

   (2) https://bugs.python.org/issue17827

   (3) https://bugs.python.org/issue17828

   (4) https://bugs.python.org/issue19619


File: python.info,  Node: PEP 451 A ModuleSpec Type for the Import System,  Next: Other Language Changes<5>,  Prev: Improvements to Codec Handling,  Up: New Features<5>

1.5.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 Deprecated: 80c. section for a list of
methods that should be replaced and their replacements.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0451

   (2) 
https://mail.python.org/pipermail/python-dev/2013-November/130111.html


File: python.info,  Node: Other Language Changes<5>,  Prev: PEP 451 A ModuleSpec Type for the Import System,  Up: New Features<5>

1.5.2.7 Other Language Changes
..............................

Some smaller changes made to the core Python language are:

   * Unicode database updated to UCD version 6.3.

   * *note min(): 80e. and *note max(): 80f. 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 weakref: 129.’able.

   * 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: 694. ‘cp273’.  (Contributed by
     Michael Bierenfeld and Andrew Kuchling in bpo-1097797(4).)

   * New Ukrainian *note codec: 694. ‘cp1125’.  (Contributed by Serhiy
     Storchaka in bpo-19668(5).)

   * *note bytes: 336.join() and *note bytearray: 337.join() now accept
     arbitrary buffer objects as arguments.  (Contributed by Antoine
     Pitrou in bpo-15958(6).)

   * The *note int: 185. 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(): 810. method that clears all
     references to local variables from the frame.  (Contributed by
     Antoine Pitrou in bpo-17934(8).)

   * *note memoryview: 25d. is now registered as a *note Sequence: 1f,
     and supports the *note reversed(): 18f. builtin.  (Contributed by
     Nick Coghlan and Claudiu Popa in bpo-18690(9) and bpo-19078(10).)

   * Signatures reported by *note help(): 577. have been modified and
     improved in several cases as a result of the introduction of
     Argument Clinic and other changes to the *note inspect: a1. and
     *note pydoc: da. modules.

   * *note __length_hint__(): 811. 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/issue18111

   (2) https://bugs.python.org/issue18416

   (3) https://bugs.python.org/issue12892

   (4) https://bugs.python.org/issue1097797

   (5) https://bugs.python.org/issue19668

   (6) https://bugs.python.org/issue15958

   (7) https://bugs.python.org/issue16772

   (8) https://bugs.python.org/issue17934

   (9) https://bugs.python.org/issue18690

   (10) https://bugs.python.org/issue19078

   (11) https://www.python.org/dev/peps/pep-0424

   (12) https://bugs.python.org/issue16148


File: python.info,  Node: New Modules<5>,  Next: Improved Modules<5>,  Prev: New Features<5>,  Up: What's New In Python 3 4

1.5.3 New Modules
-----------------

* Menu:

* asyncio: asyncio<6>.
* ensurepip::
* enum: enum<5>.
* pathlib: pathlib<5>.
* selectors: selectors<2>.
* statistics: statistics<3>.
* tracemalloc: tracemalloc<3>.


File: python.info,  Node: asyncio<6>,  Next: ensurepip,  Up: New Modules<5>

1.5.3.1 asyncio
...............

The new *note asyncio: a. 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: 34d.

也參考
......

PEP 3156(2) – Asynchronous IO Support Rebooted: the "asyncio" Module

     PEP written and implementation led by Guido van Rossum.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3156

   (2) https://www.python.org/dev/peps/pep-3156


File: python.info,  Node: ensurepip,  Next: enum<5>,  Prev: asyncio<6>,  Up: New Modules<5>

1.5.3.2 ensurepip
.................

The new *note ensurepip: 7a. 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: 7a. 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://www.python.org/dev/peps/pep-0453


File: python.info,  Node: enum<5>,  Next: pathlib<5>,  Prev: ensurepip,  Up: New Modules<5>

1.5.3.3 enum
............

The new *note enum: 7b. module (defined in PEP 435(1)) provides a
standard implementation of enumeration types, allowing other modules
(such as *note socket: f0.) 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://www.python.org/dev/peps/pep-0435

   (2) https://www.python.org/dev/peps/pep-0435


File: python.info,  Node: pathlib<5>,  Next: selectors<2>,  Prev: enum<5>,  Up: New Modules<5>

1.5.3.4 pathlib
...............

The new *note pathlib: c9. 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: 34d.

也參考
......

PEP 428(1) – The pathlib module – object-oriented filesystem paths

     PEP written and implemented by Antoine Pitrou.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0428


File: python.info,  Node: selectors<2>,  Next: statistics<3>,  Prev: pathlib<5>,  Up: New Modules<5>

1.5.3.5 selectors
.................

The new *note selectors: e7. module (created as part of implementing PEP
3156(1)) allows high-level and efficient I/O multiplexing, built upon
the *note select: e6. module primitives.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3156


File: python.info,  Node: statistics<3>,  Next: tracemalloc<3>,  Prev: selectors<2>,  Up: New Modules<5>

1.5.3.6 statistics
..................

The new *note statistics: f6. 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

     PEP written and implemented by Steven D’Aprano

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0450

   (2) https://www.python.org/dev/peps/pep-0450


File: python.info,  Node: tracemalloc<3>,  Prev: statistics<3>,  Up: New Modules<5>

1.5.3.7 tracemalloc
...................

The new *note tracemalloc: 115. 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

     PEP written and implemented by Victor Stinner

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0454

   (2) https://www.python.org/dev/peps/pep-0454


File: python.info,  Node: Improved Modules<5>,  Next: CPython Implementation Changes,  Prev: New Modules<5>,  Up: What's New In Python 3 4

1.5.4 Improved Modules
----------------------

* Menu:

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


File: python.info,  Node: abc,  Next: aifc<2>,  Up: Improved Modules<5>

1.5.4.1 abc
...........

New function *note abc.get_cache_token(): 81c. 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: 81d. has *note ABCMeta: 81e. 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/issue16832

   (2) https://bugs.python.org/issue16049


File: python.info,  Node: aifc<2>,  Next: argparse<3>,  Prev: abc,  Up: Improved Modules<5>

1.5.4.2 aifc
............

The *note getparams(): 820. method now returns a namedtuple rather than
a plain tuple.  (Contributed by Claudiu Popa in bpo-17818(1).)

*note aifc.open(): 460. now supports the context management protocol:
when used in a *note with: 6ee. block, the *note close(): 821. method of
the returned object will be called automatically at the end of the
block.  (Contributed by Serhiy Storchacha in bpo-16486(2).)

The *note writeframesraw(): 822. and *note writeframes(): 823. methods
now accept any *note bytes-like object: 5ed.  (Contributed by Serhiy
Storchaka in bpo-8311(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17818

   (2) https://bugs.python.org/issue16486

   (3) https://bugs.python.org/issue8311


File: python.info,  Node: argparse<3>,  Next: audioop,  Prev: aifc<2>,  Up: Improved Modules<5>

1.5.4.3 argparse
................

The *note FileType: 825. class now accepts `encoding' and `errors'
arguments, which are passed through to *note open(): 4f5.  (Contributed
by Lucas Maystre in bpo-11175(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue11175


File: python.info,  Node: audioop,  Next: base64,  Prev: argparse<3>,  Up: Improved Modules<5>

1.5.4.4 audioop
...............

*note audioop: d. now supports 24-bit samples.  (Contributed by Serhiy
Storchaka in bpo-12866(1).)

New *note byteswap(): 827. function converts big-endian samples to
little-endian and vice versa.  (Contributed by Serhiy Storchaka in
bpo-19641(2).)

All *note audioop: d. functions now accept any *note bytes-like object:
5ed.  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/issue12866

   (2) https://bugs.python.org/issue19641

   (3) https://bugs.python.org/issue16685


File: python.info,  Node: base64,  Next: collections<6>,  Prev: audioop,  Up: Improved Modules<5>

1.5.4.5 base64
..............

The encoding and decoding functions in *note base64: e. now accept any
*note bytes-like object: 5ed. in cases where it previously required a
*note bytes: 336. or *note bytearray: 337. instance.  (Contributed by
Nick Coghlan in bpo-17839(1).)

New functions *note a85encode(): 829, *note a85decode(): 82a, *note
b85encode(): 82b, and *note b85decode(): 82c. 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/issue17839

   (2) https://bugs.python.org/issue17618


File: python.info,  Node: collections<6>,  Next: colorsys,  Prev: base64,  Up: Improved Modules<5>

1.5.4.6 collections
...................

The *note ChainMap.new_child(): 82e. 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/issue16613


File: python.info,  Node: colorsys,  Next: contextlib<4>,  Prev: collections<6>,  Up: Improved Modules<5>

1.5.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/issue14323


File: python.info,  Node: contextlib<4>,  Next: dbm<5>,  Prev: colorsys,  Up: Improved Modules<5>

1.5.4.8 contextlib
..................

The new *note contextlib.suppress: 831. 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(): 6c7. context manager makes
it easier for utility scripts to handle inflexible APIs that write their
output to *note sys.stdout: 313. and don’t provide any options to
redirect it.  Using the context manager, the *note sys.stdout: 313.
output can be redirected to any other stream or, in conjunction with
*note io.StringIO: 832, 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:
313.  (Contributed by Raymond Hettinger in bpo-15805(3).)

The *note contextlib: 24. documentation has also been updated to include
a *note discussion: 833. of the differences between single use, reusable
and reentrant context managers.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue15806

   (2) https://bugs.python.org/issue19266

   (3) https://bugs.python.org/issue15805


File: python.info,  Node: dbm<5>,  Next: dis<2>,  Prev: contextlib<4>,  Up: Improved Modules<5>

1.5.4.9 dbm
...........

*note dbm.open(): 835. objects now support the context management
protocol.  When used in a *note with: 6ee. 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/issue19282


File: python.info,  Node: dis<2>,  Next: doctest<2>,  Prev: dbm<5>,  Up: Improved Modules<5>

1.5.4.10 dis
............

Functions *note show_code(): 837, *note dis(): 389, *note distb(): 838,
and *note disassemble(): 839. now accept a keyword-only `file' argument
that controls where they write their output.

The *note dis: 38. module is now built around an *note Instruction: 83a.
class that provides object oriented access to the details of each
individual bytecode operation.

A new method, *note get_instructions(): 83b, 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:
38. 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: 38. module have been
rewritten to use these new components.

In addition, a new application-friendly class *note Bytecode: 83c.
provides an object-oriented API for inspecting bytecode in both in
human-readable form and for iterating over instructions.  The *note
Bytecode: 83c. 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: 83a.
objects.  But it also has a *note dis: 83d. method, equivalent to
calling *note dis: 389. 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: 83c. also has a class method, *note from_traceback():
83e, that provides the ability to manipulate a traceback (that is,
‘print(Bytecode.from_traceback(tb).dis())’ is equivalent to
‘distb(tb)’).

(Contributed by Nick Coghlan, Ryan Kelly and Thomas Kluyver in
bpo-11816(1) and Claudiu Popa in bpo-17916(2).)

New function *note stack_effect(): 83f. 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/issue11816

   (2) https://bugs.python.org/issue17916

   (3) https://bugs.python.org/issue19722


File: python.info,  Node: doctest<2>,  Next: email<3>,  Prev: dis<2>,  Up: Improved Modules<5>

1.5.4.11 doctest
................

A new *note option flag: 841, *note FAIL_FAST: 842, 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: 67. command line interface now uses *note argparse:
6, and has two new options, ‘-o’ and ‘-f’.  ‘-o’ allows *note doctest
options: 841. 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: 11c. CLI). (Contributed by R. David Murray in
bpo-11390(2).)

*note doctest: 67. will now find doctests in extension module ‘__doc__’
strings.  (Contributed by Zachary Ware in bpo-3158(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16522

   (2) https://bugs.python.org/issue11390

   (3) https://bugs.python.org/issue3158


File: python.info,  Node: email<3>,  Next: filecmp,  Prev: doctest<2>,  Up: Improved Modules<5>

1.5.4.12 email
..............

*note as_string(): 844. 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: 6e. in order to
pass formatting parameters to its ‘flatten’ method.  (Contributed by R.
David Murray in bpo-18600(1).)

New method *note as_bytes(): 845. 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: 546. *note __bytes__(): 846. 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(): 847. 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: 546. have
been added (*note EmailMessage: 547. and *note MIMEPart: 848.), along
with a new sub-module, *note contentmanager: 6b. and a new *note policy:
75. attribute *note content_manager: 849.  All documentation is
currently in the new module, which is being added as part of email’s new
*note provisional API: 34d.  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:
6b. documentation and the *note email; Examples: 84a.  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/issue18600

   (2) https://bugs.python.org/issue18600

   (3) https://bugs.python.org/issue18891

   (4) https://bugs.python.org/issue18891


File: python.info,  Node: filecmp,  Next: functools<4>,  Prev: email<3>,  Up: Improved Modules<5>

1.5.4.13 filecmp
................

A new *note clear_cache(): 84c. function provides the ability to clear
the *note filecmp: 7f. comparison cache, which uses *note os.stat():
1f2. 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: 84d. provides the list of
directories that are used as the default value for the `ignore'
parameter of the *note dircmp(): 84e. function.  (Contributed by Eli
Bendersky in bpo-15442(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue18149

   (2) https://bugs.python.org/issue15442


File: python.info,  Node: functools<4>,  Next: gc<3>,  Prev: filecmp,  Up: Improved Modules<5>

1.5.4.14 functools
..................

The new *note partialmethod(): 29d. descriptor brings partial argument
application to descriptors, just as *note partial(): 7cd. provides for
normal callables.  The new descriptor also makes it easier to get
arbitrary callables (including *note partial(): 7cd. 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(): 38f. 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

     PEP written and implemented by Łukasz Langa.

*note total_ordering(): 850. now supports a return value of *note
NotImplemented: 851. from the underlying comparison function.
(Contributed by Katie Miller in bpo-10042(3).)

A pure-python version of the *note partial(): 7cd. 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/issue4331

   (2) https://www.python.org/dev/peps/pep-0443

   (3) https://bugs.python.org/issue10042

   (4) https://bugs.python.org/issue12428


File: python.info,  Node: gc<3>,  Next: glob<2>,  Prev: functools<4>,  Up: Improved Modules<5>

1.5.4.15 gc
...........

New function *note get_stats(): 853. 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/issue16351


File: python.info,  Node: glob<2>,  Next: hashlib<2>,  Prev: gc<3>,  Up: Improved Modules<5>

1.5.4.16 glob
.............

A new function *note escape(): 855. 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/issue8402


File: python.info,  Node: hashlib<2>,  Next: hmac<2>,  Prev: glob<2>,  Up: Improved Modules<5>

1.5.4.17 hashlib
................

A new *note hashlib.pbkdf2_hmac(): 7eb. function provides the PKCS#5
password-based key derivation function 2(1).  (Contributed by Christian
Heimes in bpo-18582(2).)

The *note name: 857. attribute of *note hashlib: 8d. hash objects is now
a formally supported interface.  It has always existed in CPython’s
*note hashlib: 8d. (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/issue18582

   (3) https://bugs.python.org/issue18532


File: python.info,  Node: hmac<2>,  Next: html,  Prev: hashlib<2>,  Up: Improved Modules<5>

1.5.4.18 hmac
.............

*note hmac: 8f. now accepts ‘bytearray’ as well as ‘bytes’ for the `key'
argument to the *note new(): 859. function, and the `msg' parameter to
both the *note new(): 859. function and the *note update(): 85a. method
now accepts any type supported by the *note hashlib: 8d. module.
(Contributed by Jonas Borgström in bpo-18240(1).)

The `digestmod' argument to the *note hmac.new(): 859. function may now
be any hash digest name recognized by *note hashlib: 8d.  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: 85b. and *note name: 85c.
attributes (and the formal documentation of the *note digest_size: 85d.
attribute), the *note hmac: 8f. module now conforms fully to the PEP
247(3) API. (Contributed by Christian Heimes in bpo-18775(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue18240

   (2) https://bugs.python.org/issue17276

   (3) https://www.python.org/dev/peps/pep-0247

   (4) https://bugs.python.org/issue18775


File: python.info,  Node: html,  Next: http<2>,  Prev: hmac<2>,  Up: Improved Modules<5>

1.5.4.19 html
.............

New function *note unescape(): 85f. function converts HTML5 character
references to the corresponding Unicode characters.  (Contributed by
Ezio Melotti in bpo-2927(1).)

*note HTMLParser: 7c4. 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: 7c4. is now deprecated.
(Contributed by Ezio Melotti in bpo-15114(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue2927

   (2) https://bugs.python.org/issue13633

   (3) https://bugs.python.org/issue15114


File: python.info,  Node: http<2>,  Next: idlelib and IDLE<4>,  Prev: html,  Up: Improved Modules<5>

1.5.4.20 http
.............

*note send_error(): 861. 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: 97. *note command line interface: 862. 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/issue12921

   (2) https://bugs.python.org/issue17764


File: python.info,  Node: idlelib and IDLE<4>,  Next: importlib<6>,  Prev: http<2>,  Up: Improved Modules<5>

1.5.4.21 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.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<6>,  Next: inspect<4>,  Prev: idlelib and IDLE<4>,  Up: Improved Modules<5>

1.5.4.22 importlib
..................

The *note InspectLoader: 865. ABC defines a new method, *note
source_to_code(): 6f4. 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: 865. also now has a default implementation for the
*note get_code(): 866. 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(): 39e. function has been moved from *note imp: 9a. to
*note importlib: 9b. as part of the *note imp: 9a. module deprecation.
(Contributed by Berker Peksag in bpo-18193(3).)

*note importlib.util: a0. now has a *note MAGIC_NUMBER: 867. attribute
providing access to the bytecode version number.  This replaces the
*note get_magic(): 868. function in the deprecated *note imp: 9a.
module.  (Contributed by Brett Cannon in bpo-18192(4).)

New *note importlib.util: a0. functions *note cache_from_source(): 55c.
and *note source_from_cache(): 55d. replace the same-named functions in
the deprecated *note imp: 9a. module.  (Contributed by Brett Cannon in
bpo-18194(5).)

The *note importlib: 9b. bootstrap ‘NamespaceLoader’ now conforms to the
*note InspectLoader: 865. 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: a0. has a new function *note decode_source(): 869.
that decodes source from bytes using universal newline processing.  This
is useful for implementing *note InspectLoader.get_source(): 86a.
methods.

*note importlib.machinery.ExtensionFileLoader: 55b. now has a *note
get_filename(): 86b. method.  This was inadvertently omitted in the
original implementation.  (Contributed by Eric Snow in bpo-19152(7).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue15627

   (2) https://bugs.python.org/issue18072

   (3) https://bugs.python.org/issue18193

   (4) https://bugs.python.org/issue18192

   (5) https://bugs.python.org/issue18194

   (6) https://bugs.python.org/issue18058

   (7) https://bugs.python.org/issue19152


File: python.info,  Node: inspect<4>,  Next: ipaddress<3>,  Prev: importlib<6>,  Up: Improved Modules<5>

1.5.4.23 inspect
................

The *note inspect: a1. module now offers a basic *note command line
interface: 86d. 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(): 86e. makes it easy to unravel wrapper function chains
created by *note functools.wraps(): 86f. (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: 7b. module, the
*note inspect: a1. 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(): 562. and *note getargspec(): 561. now use the
*note signature(): 560. 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(): 7cd. objects and more.  Note that, unlike *note
signature(): 560, 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(): 560.
directly if those features are desired.  (Contributed by Yury Selivanov
in bpo-17481(5).)

*note signature(): 560. 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/issue18626

   (2) https://bugs.python.org/issue13266

   (3) https://bugs.python.org/issue18929

   (4) https://bugs.python.org/issue19030

   (5) https://bugs.python.org/issue17481

   (6) https://bugs.python.org/issue17159


File: python.info,  Node: ipaddress<3>,  Next: logging<5>,  Prev: inspect<4>,  Up: Improved Modules<5>

1.5.4.24 ipaddress
..................

*note ipaddress: a3. was added to the standard library in Python 3.3 as
a *note provisional API: 34d.  With the release of Python 3.4, this
qualification has been removed: *note ipaddress: a3. is now considered a
stable API, covered by the normal standard library requirements to
maintain backwards compatibility.

A new *note is_global: 871. property is ‘True’ if an address is globally
routeable.  (Contributed by Peter Moody in bpo-17400(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17400


File: python.info,  Node: logging<5>,  Next: marshal,  Prev: ipaddress<3>,  Up: Improved Modules<5>

1.5.4.25 logging
................

The *note TimedRotatingFileHandler: 873. 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: 874. and *note DatagramHandler: 875. now support
Unix domain sockets (by setting `port' to ‘None’).  (Contributed by
Vinay Sajip in commit ce46195b56a9.)

*note fileConfig(): 3ae. now accepts a *note
configparser.RawConfigParser: 876. 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(): 3ae.  (Contributed by Vinay Sajip in bpo-16110(2).)

Logging configuration data received from a socket via the *note
logging.config.listen(): 877. 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/issue9556

   (2) https://bugs.python.org/issue16110

   (3) https://bugs.python.org/issue15452


File: python.info,  Node: marshal,  Next: mmap<2>,  Prev: logging<5>,  Up: Improved Modules<5>

1.5.4.26 marshal
................

The default *note marshal: b1. 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/issue16475

   (2) https://bugs.python.org/issue19219


File: python.info,  Node: mmap<2>,  Next: multiprocessing<5>,  Prev: marshal,  Up: Improved Modules<5>

1.5.4.27 mmap
.............

mmap objects can now be *note weakref: 129.ed.  (Contributed by Valerie
Lambert in bpo-4885(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue4885


File: python.info,  Node: multiprocessing<5>,  Next: operator<2>,  Prev: mmap<2>,  Up: Improved Modules<5>

1.5.4.28 multiprocessing
........................

On Unix two new *note start methods: 87b, ‘spawn’ and ‘forkserver’, have
been added for starting processes using *note multiprocessing: b8.
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(): 87c.
reports all start methods available on the platform, *note
get_start_method(): 87d. reports the current start method, and *note
set_start_method(): 87e. sets the start method.  (Contributed by Richard
Oudkerk in bpo-8713(1).)

*note multiprocessing: b8. also now has the concept of a ‘context’,
which determines how child processes are created.  New function *note
get_context(): 87f. returns a context that uses a specified start
method.  It has the same API as the *note multiprocessing: b8. module
itself, so you can use it to create *note Pool: 880.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: b8. now relies on *note runpy: e3. (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/issue8713

   (2) https://bugs.python.org/issue18999

   (3) https://bugs.python.org/issue8713

   (4) https://bugs.python.org/issue19946


File: python.info,  Node: operator<2>,  Next: os<6>,  Prev: multiprocessing<5>,  Up: Improved Modules<5>

1.5.4.29 operator
.................

New function *note length_hint(): 882. provides an implementation of the
specification for how the *note __length_hint__(): 811. 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: c3. module
available for reference and for use by alternate implementations of
Python.  (Contributed by Zachary Ware in bpo-16694(3).)

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0424

   (2) https://bugs.python.org/issue16148

   (3) https://bugs.python.org/issue16694


File: python.info,  Node: os<6>,  Next: pdb<3>,  Prev: operator<2>,  Up: Improved Modules<5>

1.5.4.30 os
...........

There are new functions to get and set the *note inheritable flag: 7ff.
of a file descriptor (*note os.get_inheritable(): 800, *note
os.set_inheritable(): 801.) or a Windows handle (*note
os.get_handle_inheritable(): 802, *note os.set_handle_inheritable():
803.).

New function *note cpu_count(): 884. 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(): 885.
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(): 886. is now available on the Windows platform
(and the *note os.path.samefile(): 887. implementation is now shared
between Unix and Windows).  (Contributed by Brian Curtin in
bpo-11939(2).)

*note os.path.ismount(): 1fb. now recognizes volumes mounted below a
drive root on Windows.  (Contributed by Tim Golden in bpo-9035(3).)

*note os.open(): 66a. supports two new flags on platforms that provide
them, *note O_PATH: 888. (un-opened file descriptor), and *note
O_TMPFILE: 889. (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/issue17914

   (2) https://bugs.python.org/issue11939

   (3) https://bugs.python.org/issue9035

   (4) https://bugs.python.org/issue18673


File: python.info,  Node: pdb<3>,  Next: pickle<4>,  Prev: os<6>,  Up: Improved Modules<5>

1.5.4.31 pdb
............

*note pdb: ca. has been enhanced to handle generators, *note yield: 190,
and ‘yield from’ in a more useful fashion.  This is especially helpful
when debugging *note asyncio: a. based programs.  (Contributed by Andrew
Svetlov and Xavier de Gaye in bpo-16596(1).)

The ‘print’ command has been removed from *note pdb: ca, restoring
access to the Python *note print(): 88b. 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: 88c. 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/issue16596

   (2) https://bugs.python.org/issue18764


File: python.info,  Node: pickle<4>,  Next: plistlib<2>,  Prev: pdb<3>,  Up: Improved Modules<5>

1.5.4.32 pickle
...............

*note pickle: cb. 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 *note __new__(): 88e. method takes keyword-only arguments.
It also provides some efficiency improvements.

也參考
......

PEP 3154(1) – Pickle protocol 4

     PEP written by Antoine Pitrou and implemented by Alexandre
     Vassalotti.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3154


File: python.info,  Node: plistlib<2>,  Next: poplib<2>,  Prev: pickle<4>,  Up: Improved Modules<5>

1.5.4.33 plistlib
.................

*note plistlib: d0. now has an API that is similar to the standard
pattern for stdlib serialization protocols, with new *note load(): 890,
*note dump(): 891, *note loads(): 892, and *note dumps(): 893.
functions.  (The older API is now deprecated.)  In addition to the
already supported XML plist format (*note FMT_XML: 894.), it also now
supports the binary plist format (*note FMT_BINARY: 895.).  (Contributed
by Ronald Oussoren and others in bpo-14455(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14455


File: python.info,  Node: poplib<2>,  Next: pprint<2>,  Prev: plistlib<2>,  Up: Improved Modules<5>

1.5.4.34 poplib
...............

Two new methods have been added to *note poplib: d1.: *note capa(): 897,
which returns the list of capabilities advertised by the POP server, and
*note stls(): 898, 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/issue4473


File: python.info,  Node: pprint<2>,  Next: pty,  Prev: poplib<2>,  Up: Improved Modules<5>

1.5.4.35 pprint
...............

The *note pprint: d3. module’s *note PrettyPrinter: 89a. class and its
*note pformat(): 89b, and *note pprint(): 214. 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/issue19132

   (2) https://bugs.python.org/issue17150


File: python.info,  Node: pty,  Next: pydoc<3>,  Prev: pprint<2>,  Up: Improved Modules<5>

1.5.4.36 pty
............

*note pty.spawn(): 89d. now returns the status value from *note
os.waitpid(): 672. on the child process, instead of ‘None’.
(Contributed by Gregory P. Smith.)


File: python.info,  Node: pydoc<3>,  Next: re<5>,  Prev: pty,  Up: Improved Modules<5>

1.5.4.37 pydoc
..............

The *note pydoc: da. module is now based directly on the *note
inspect.signature(): 560. 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: da. 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: da.
directly, its handling of custom ‘__dir__’ methods and various
descriptor behaviours has also been improved substantially by the
underlying changes in the *note inspect: a1. module.

As the *note help(): 577. builtin is based on *note pydoc: da, the above
changes also affect the behaviour of *note help(): 577.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue19674

   (2) https://bugs.python.org/issue20710


File: python.info,  Node: re<5>,  Next: resource,  Prev: pydoc<3>,  Up: Improved Modules<5>

1.5.4.38 re
...........

New *note fullmatch(): 8a0. 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: 8a1. now includes the pattern and the
flags; the repr of *note match objects: 8a2. 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/issue16203

   (2) https://bugs.python.org/issue13592

   (3) https://bugs.python.org/issue17087


File: python.info,  Node: resource,  Next: select,  Prev: re<5>,  Up: Improved Modules<5>

1.5.4.39 resource
.................

New *note prlimit(): 8a4. 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: 8a5, *note RLIMIT_NICE: 8a6,
*note RLIMIT_RTPRIO: 8a7, *note RLIMIT_RTTIME: 8a8, and *note
RLIMIT_SIGPENDING: 8a9.  (Contributed by Christian Heimes in
bpo-19324(2).)

On FreeBSD version 9 and later, there some new FreeBSD specific
constants: *note RLIMIT_SBSIZE: 8aa, *note RLIMIT_SWAP: 8ab, and *note
RLIMIT_NPTS: 8ac.  (Contributed by Claudiu Popa in bpo-19343(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16595

   (2) https://bugs.python.org/issue19324

   (3) https://bugs.python.org/issue19343


File: python.info,  Node: select,  Next: shelve,  Prev: resource,  Up: Improved Modules<5>

1.5.4.40 select
...............

*note epoll: 8ae. objects now support the context management protocol.
When used in a *note with: 6ee. statement, the *note close(): 8af.
method will be called automatically at the end of the block.
(Contributed by Serhiy Storchaka in bpo-16488(1).)

*note devpoll: 8b0. objects now have *note fileno(): 8b1. and *note
close(): 8b2. methods, as well as a new attribute *note closed: 8b3.
(Contributed by Victor Stinner in bpo-18794(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16488

   (2) https://bugs.python.org/issue18794


File: python.info,  Node: shelve,  Next: shutil<3>,  Prev: select,  Up: Improved Modules<5>

1.5.4.41 shelve
...............

*note Shelf: 8b5. instances may now be used in *note with: 6ee.
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/issue13896


File: python.info,  Node: shutil<3>,  Next: smtpd<2>,  Prev: shelve,  Up: Improved Modules<5>

1.5.4.42 shutil
...............

*note copyfile(): 259. now raises a specific *note Error: 8b7. subclass,
*note SameFileError: 8b8, 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/issue1492704


File: python.info,  Node: smtpd<2>,  Next: smtplib<2>,  Prev: shutil<3>,  Up: Improved Modules<5>

1.5.4.43 smtpd
..............

The *note SMTPServer: 607. and *note SMTPChannel: 606. classes now
accept a `map' keyword argument which, if specified, is passed in to
*note asynchat.async_chat: 8ba. 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/issue11959


File: python.info,  Node: smtplib<2>,  Next: socket<6>,  Prev: smtpd<2>,  Up: Improved Modules<5>

1.5.4.44 smtplib
................

*note SMTPException: 8bc. is now a subclass of *note OSError: 1d4, 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/issue2118


File: python.info,  Node: socket<6>,  Next: sqlite3<4>,  Prev: smtplib<2>,  Up: Improved Modules<5>

1.5.4.45 socket
...............

The socket module now supports the *note CAN_BCM: 8be. 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: 7ff, *note get_inheritable(): 804. and *note set_inheritable():
805.

The ‘socket.AF_*’ and ‘socket.SOCK_*’ constants are now enumeration
values using the new *note enum: 7b. module.  This allows meaningful
names to be printed during debugging, instead of integer "magic
numbers".

The *note AF_LINK: 8bf. constant is now available on BSD and OSX.

*note inet_pton(): 8c0. and *note inet_ntop(): 8c1. are now supported on
Windows.  (Contributed by Atsuo Ishimoto in bpo-7171(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue15359

   (2) https://bugs.python.org/issue7171


File: python.info,  Node: sqlite3<4>,  Next: ssl<7>,  Prev: socket<6>,  Up: Improved Modules<5>

1.5.4.46 sqlite3
................

A new boolean parameter to the *note connect(): 3df. 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/issue13773


File: python.info,  Node: ssl<7>,  Next: stat,  Prev: sqlite3<4>,  Up: Improved Modules<5>

1.5.4.47 ssl
............

*note PROTOCOL_TLSv1_1: 8c4. and *note PROTOCOL_TLSv1_2: 8c5. (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(): 8c6. provides a standard way to
obtain an *note SSLContext: 3e9. 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:
3e9. 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(): 8c6. to obtain an *note
SSLContext: 3e9. 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: 3e9. method *note load_verify_locations(): 7f0.
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(): 8c7. returns a named
tuple of the paths and environment variables that the *note
set_default_verify_paths(): 8c8. 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: 3e9. has a new method, *note cert_store_stats(): 8c9,
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(): 8ca. 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: 3e9. has a new
attribute *note verify_flags: 8cb. that can be used to control the
certificate verification process by setting it to some combination of
the new constants *note VERIFY_DEFAULT: 8cc, *note
VERIFY_CRL_CHECK_LEAF: 8cd, *note VERIFY_CRL_CHECK_CHAIN: 8ce, or *note
VERIFY_X509_STRICT: 8cf.  OpenSSL does not do any CRL verification by
default.  (Contributed by Christien Heimes in bpo-8813(6).)

New *note SSLContext: 3e9. method *note load_default_certs(): 8d0. 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: 8d1.) for a client to use to verify a server, and
certificates for a server to use in verifying client certificates
(‘purpose=’*note CLIENT_AUTH: 8d2.).  (Contributed by Christian Heimes
in bpo-19292(7).)  Two new windows-only functions, *note
enum_certificates(): 8d3. and *note enum_crls(): 8d4. 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(): 8d5.
method.  (Contributed by Daniel Black in bpo-8109(9).)

The dictionary returned by *note SSLSocket.getpeercert(): 8d6. contains
additional ‘X509v3’ extension items: ‘crlDistributionPoints’,
‘calIssuers’, and ‘OCSP’ URIs.  (Contributed by Christian Heimes in
bpo-18379(10).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16692

   (2) https://bugs.python.org/issue19689

   (3) https://bugs.python.org/issue18138

   (4) https://bugs.python.org/issue18143

   (5) https://bugs.python.org/issue18147

   (6) https://bugs.python.org/issue8813

   (7) https://bugs.python.org/issue19292

   (8) https://bugs.python.org/issue17134

   (9) https://bugs.python.org/issue8109

   (10) https://bugs.python.org/issue18379


File: python.info,  Node: stat,  Next: struct<2>,  Prev: ssl<7>,  Up: Improved Modules<5>

1.5.4.48 stat
.............

The *note stat: f5. 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: 8d8. flags, *note S_IFDOOR: 8d9,
*note S_IFPORT: 8da, and *note S_IFWHT: 8db.  (Contributed by Christian
Hiemes in bpo-11016(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue11016

   (2) https://bugs.python.org/issue11016


File: python.info,  Node: struct<2>,  Next: subprocess<4>,  Prev: stat,  Up: Improved Modules<5>

1.5.4.49 struct
...............

New function *note iter_unpack: 8dd. and a new *note
struct.Struct.iter_unpack(): 8de. 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/issue17804


File: python.info,  Node: subprocess<4>,  Next: sunau<2>,  Prev: struct<2>,  Up: Improved Modules<5>

1.5.4.50 subprocess
...................

*note check_output(): 8e0. 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(): 8e1. 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/issue16624

   (2) https://bugs.python.org/issue10197


File: python.info,  Node: sunau<2>,  Next: sys<6>,  Prev: subprocess<4>,  Up: Improved Modules<5>

1.5.4.51 sunau
..............

The ‘getparams()’ method now returns a namedtuple rather than a plain
tuple.  (Contributed by Claudiu Popa in bpo-18901(1).)

*note sunau.open(): 477. now supports the context management protocol:
when used in a *note with: 6ee. 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).)

*note AU_write.setsampwidth(): 8e3. now supports 24 bit samples, thus
adding support for writing 24 sample using the module.  (Contributed by
Serhiy Storchaka in bpo-19261(3).)

The *note writeframesraw(): 8e4. and *note writeframes(): 8e5. methods
now accept any *note bytes-like object: 5ed.  (Contributed by Serhiy
Storchaka in bpo-8311(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue18901

   (2) https://bugs.python.org/issue18878

   (3) https://bugs.python.org/issue19261

   (4) https://bugs.python.org/issue8311


File: python.info,  Node: sys<6>,  Next: tarfile<3>,  Prev: sunau<2>,  Up: Improved Modules<5>

1.5.4.52 sys
............

New function *note sys.getallocatedblocks(): 8e7. 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(): 50d. 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: 8e8, it
checks for an *note __interactivehook__: 8e9. attribute on the *note
sys: fe. 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: 8ea. file is read, so it can be set
there.  The *note site: ec. module *note sets it: 8eb. to a function
that enables tab completion and history saving (in ‘~/.python-history’)
if the platform supports *note readline: df.  If you do not want this
(new) behavior, you can override it in *note PYTHONSTARTUP: 8ea,
‘sitecustomize’, or ‘usercustomize’ by deleting this attribute from
*note sys: fe. (or setting it to some other callable).  (Contributed by
Éric Araujo and Antoine Pitrou in bpo-5845(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue13390

   (2) https://bugs.python.org/issue5845


File: python.info,  Node: tarfile<3>,  Next: textwrap,  Prev: sys<6>,  Up: Improved Modules<5>

1.5.4.53 tarfile
................

The *note tarfile: 102. module now supports a simple *note Command-Line
Interface: 8ed. 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/issue13477


File: python.info,  Node: textwrap,  Next: threading<4>,  Prev: tarfile<3>,  Up: Improved Modules<5>

1.5.4.54 textwrap
.................

The *note TextWrapper: 8ef. class has two new attributes/constructor
arguments: *note max_lines: 8f0, which limits the number of lines in the
output, and *note placeholder: 8f1, 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(): 8f2. 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/issue18585

   (2) https://bugs.python.org/issue18725


File: python.info,  Node: threading<4>,  Next: traceback<3>,  Prev: textwrap,  Up: Improved Modules<5>

1.5.4.55 threading
..................

The *note Thread: 236. object representing the main thread can be
obtained from the new *note main_thread(): 8f4. 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/issue18882


File: python.info,  Node: traceback<3>,  Next: types<3>,  Prev: threading<4>,  Up: Improved Modules<5>

1.5.4.56 traceback
..................

A new *note traceback.clear_frames(): 8f6. 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/issue1565525


File: python.info,  Node: types<3>,  Next: urllib<2>,  Prev: traceback<3>,  Up: Improved Modules<5>

1.5.4.57 types
..............

A new *note DynamicClassAttribute(): 8f8. 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/issue19030


File: python.info,  Node: urllib<2>,  Next: unittest<4>,  Prev: types<3>,  Up: Improved Modules<5>

1.5.4.58 urllib
...............

*note urllib.request: 121. now supports ‘data:’ URLs via the *note
DataHandler: 8fa. class.  (Contributed by Mathias Panzenböck in
bpo-16423(1).)

The http method that will be used by a *note Request: 8fb. class can now
be specified by setting a *note method: 8fc. class attribute on the
subclass.  (Contributed by Jason R Coombs in bpo-18978(2).)

*note Request: 8fb. objects are now reusable: if the *note full_url:
8fd. or *note data: 8fe. attributes are modified, all relevant internal
properties are updated.  This means, for example, that it is now
possible to use the same *note Request: 8fb. object in more than one
*note OpenerDirector.open(): 8ff. call with different `data' arguments,
or to modify a *note Request: 8fb.’s ‘url’ rather than recomputing it
from scratch.  There is also a new *note remove_header(): 900. method
that can be used to remove headers from a *note Request: 8fb.
(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: 901. objects now have a *note headers: 902. 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/issue16423

   (2) https://bugs.python.org/issue18978

   (3) https://bugs.python.org/issue16464

   (4) https://bugs.python.org/issue17485

   (5) https://bugs.python.org/issue17272

   (6) https://bugs.python.org/issue15701


File: python.info,  Node: unittest<4>,  Next: venv<4>,  Prev: urllib<2>,  Up: Improved Modules<5>

1.5.4.59 unittest
.................

The *note TestCase: 904. class has a new method, *note subTest(): 905,
that produces a context manager whose *note with: 6ee. 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: 906. for the full version of this
example.  (Contributed by Antoine Pitrou in bpo-16997(1).)

*note unittest.main(): 907. 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: 908. 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(): 909. now sorts the discovered files to provide
consistent test ordering.  (Contributed by Martin Melin and Jeff Ramnani
in bpo-16709(4).)

*note TestSuite: 6d3. 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: 6d3. 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(): 90a, will
ensure that a given block of code emits a log message using the *note
logging: ab. 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: 90b.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: 11d. 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/issue16997

   (2) https://bugs.python.org/issue15132

   (3) https://bugs.python.org/issue16935

   (4) https://bugs.python.org/issue16709

   (5) https://bugs.python.org/issue11798

   (6) https://bugs.python.org/issue18937

   (7) https://bugs.python.org/issue17457

   (8) https://bugs.python.org/issue17015

   (9) https://bugs.python.org/issue17467


File: python.info,  Node: venv<4>,  Next: wave<2>,  Prev: unittest<4>,  Up: Improved Modules<5>

1.5.4.60 venv
.............

*note venv: 126. now includes activation scripts for the ‘csh’ and
‘fish’ shells.  (Contributed by Andrew Svetlov in bpo-15417(1).)

*note EnvBuilder: 90d. and the *note create(): 90e. convenience function
take a new keyword argument `with_pip', which defaults to ‘False’, that
controls whether or not *note EnvBuilder: 90d. 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/issue15417

   (2) https://bugs.python.org/issue19552

   (3) https://www.python.org/dev/peps/pep-0453


File: python.info,  Node: wave<2>,  Next: weakref<2>,  Prev: venv<4>,  Up: Improved Modules<5>

1.5.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(): 47b. now supports the context management protocol.
(Contributed by Claudiu Popa in bpo-17616(2).)

*note wave: 128. can now *note write output to unseekable files: 910.
(Contributed by David Jones, Guilherme Polo, and Serhiy Storchaka in
bpo-5202(3).)

The *note writeframesraw(): 911. and *note writeframes(): 912. methods
now accept any *note bytes-like object: 5ed.  (Contributed by Serhiy
Storchaka in bpo-8311(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17487

   (2) https://bugs.python.org/issue17616

   (3) https://bugs.python.org/issue5202

   (4) https://bugs.python.org/issue8311


File: python.info,  Node: weakref<2>,  Next: xml etree<2>,  Prev: wave<2>,  Up: Improved Modules<5>

1.5.4.62 weakref
................

New *note WeakMethod: 914. class simulates weak references to bound
methods.  (Contributed by Antoine Pitrou in bpo-14631(1).)

New *note finalize: 29e. 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: 915. is now exposed
via the *note __callback__: 916. attribute.  (Contributed by Mark
Dickinson in bpo-17643(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14631

   (2) https://bugs.python.org/issue15528

   (3) https://bugs.python.org/issue17643


File: python.info,  Node: xml etree<2>,  Next: zipfile<4>,  Prev: weakref<2>,  Up: Improved Modules<5>

1.5.4.63 xml.etree
..................

A new parser, *note XMLPullParser: 918, allows a non-blocking
applications to parse XML documents.  An example can be seen at *note
Pull API for non-blocking parsing: 919.  (Contributed by Antoine Pitrou
in bpo-17741(1).)

The *note xml.etree.ElementTree: 138. *note tostring(): 91a. and *note
tostringlist(): 91b. functions, and the *note ElementTree: 91c. *note
write(): 91d. method, now have a `short_empty_elements' *note
keyword-only parameter: 2ad. 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/issue17741

   (2) https://bugs.python.org/issue14377


File: python.info,  Node: zipfile<4>,  Prev: xml etree<2>,  Up: Improved Modules<5>

1.5.4.64 zipfile
................

The *note writepy(): 91f. method of the *note PyZipFile: 920. 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: 424. and ‘PyZipfile’ is now
‘True’ by default.  (Contributed by William Mallard in bpo-17201(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue19274

   (2) https://bugs.python.org/issue17201


File: python.info,  Node: CPython Implementation Changes,  Next: Deprecated<4>,  Prev: Improved Modules<5>,  Up: What's New In Python 3 4

1.5.5 CPython Implementation Changes
------------------------------------

* 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>.
* Significant Optimizations::


File: python.info,  Node: PEP 445 Customization of CPython Memory Allocators,  Next: PEP 442 Safe Object Finalization,  Up: CPython Implementation Changes

1.5.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

     PEP written and implemented by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0445

   (2) https://www.python.org/dev/peps/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 Implementation Changes

1.5.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 *note __del__(): 924.
methods, as well as generators with *note finally: 183. 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: 158. 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

     PEP written and implemented by Antoine Pitrou.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0442

   (2) https://www.python.org/dev/peps/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 Implementation Changes

1.5.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: 926. 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://www.python.org/dev/peps/pep-0456

   (2) https://bugs.python.org/issue14621


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 Implementation Changes

1.5.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: da. and *note inspect:
a1. 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

     PEP written and implemented by Larry Hastings.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0436

   (2) https://www.python.org/dev/peps/pep-0436


File: python.info,  Node: Other Build and C API Changes,  Next: Other Improvements<2>,  Prev: PEP 436 Argument Clinic,  Up: CPython Implementation Changes

1.5.5.5 Other Build and C API Changes
.....................................

   * The new *note PyType_GetSlot(): 929. 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 *note Py_SetStandardStreamEncoding(): 92a.
     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(): 7d0. 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(): 92b. supplements
     the existing *note PyStructSequence_InitType(): 92c. 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(): 92d. is the C API
     equivalent of *note operator.length_hint(): 882.  (Contributed by
     Armin Ronacher in bpo-16148(9).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17162

   (2) https://bugs.python.org/issue16129

   (3) https://bugs.python.org/issue1772673

   (4) https://bugs.python.org/issue7330

   (5) https://bugs.python.org/issue18596

   (6) https://en.wikipedia.org/wiki/Address_space_layout_randomization

   (7) https://en.wikipedia.org/wiki/Data_Execution_Prevention

   (8) https://bugs.python.org/issue16632

   (9) https://bugs.python.org/issue16148


File: python.info,  Node: Other Improvements<2>,  Next: Significant Optimizations,  Prev: Other Build and C API Changes,  Up: CPython Implementation Changes

1.5.5.6 Other Improvements
..........................

   * The *note python: 930. command has a new *note option: 931, ‘-I’,
     which causes it to run in "isolated mode", which means that *note
     sys.path: 48d. 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: df.  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: 6.
     (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: 932. now
     also checks for memory allocation leaks, using *note
     sys.getallocatedblocks(): 8e7.  (Contributed by Antoine Pitrou in
     bpo-13390(9).)

   * ‘python -m’ now works with namespace packages.

   * The *note stat: f5. 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, *note LOAD_CLASSDEREF: 933, 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__: 502.  (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: 934. 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: 14, *note lzma: ae, and *note gzip: 8c. 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/issue16499

   (2) https://bugs.python.org/issue5845

   (3) https://bugs.python.org/issue18338

   (4) https://bugs.python.org/issue18920

   (5) https://bugs.python.org/issue18922

   (6) https://bugs.python.org/issue18569

   (7) 
https://devguide.python.org/coverage/#measuring-coverage-of-c-code-with-gcov-and-lcov

   (8) http://ltp.sourceforge.net/coverage/lcov.php

   (9) https://bugs.python.org/issue13390

   (10) https://bugs.python.org/issue16421

   (11) https://bugs.python.org/issue17853

   (12) https://www.python.org/dev/peps/pep-0445

   (13) https://bugs.python.org/issue18408

   (14) https://bugs.python.org/issue18520

   (15) https://bugs.python.org/issue18807

   (16) https://bugs.python.org/issue19552

   (17) https://www.python.org/dev/peps/pep-0453

   (18) https://bugs.python.org/issue18818

   (19) https://bugs.python.org/issue19201

   (20) https://bugs.python.org/issue19222

   (21) https://bugs.python.org/issue19223


File: python.info,  Node: Significant Optimizations,  Prev: Other Improvements<2>,  Up: CPython Implementation Changes

1.5.5.7 Significant Optimizations
.................................

   * 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: de, *note collections: 1e. and *note locale:
     aa. 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: 936. is now as fast or faster than the Python2
     version for most cases.  *note lzma.LZMAFile: 937. has also been
     optimized.  (Contributed by Serhiy Storchaka and Nadeem Vawda in
     bpo-16034(8).)

   * *note random.getrandbits(): 938. 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: fa.
     (Contributed by Richard Oudkerk in bpo-15758(11).)

   * *note html.escape(): 939. 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(): 4d6. 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/issue14625

   (2) https://bugs.python.org/issue18771

   (3) https://bugs.python.org/issue19219

   (4) https://bugs.python.org/issue19218

   (5) https://bugs.python.org/issue19209

   (6) https://bugs.python.org/issue19205

   (7) https://bugs.python.org/issue9548

   (8) https://bugs.python.org/issue16034

   (9) https://bugs.python.org/issue16674

   (10) https://bugs.python.org/issue15596

   (11) https://bugs.python.org/issue15758

   (12) https://bugs.python.org/issue18020

   (13) https://bugs.python.org/issue18756


File: python.info,  Node: Deprecated<4>,  Next: Removed<3>,  Prev: CPython Implementation Changes,  Up: What's New In Python 3 4

1.5.6 Deprecated
----------------

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: 279. when the interpreter is run with
deprecation warnings enabled (for example, by using ‘-Wd’).

* Menu:

* Deprecations in the Python API::
* Deprecated Features::


File: python.info,  Node: Deprecations in the Python API,  Next: Deprecated Features,  Up: Deprecated<4>

1.5.6.1 Deprecations in the Python API
......................................

   * As mentioned in *note PEP 451; A ModuleSpec Type for the Import
     System: 7dd, a number of *note importlib: 9b. methods and functions
     are deprecated: *note importlib.find_loader(): 93c. is replaced by
     *note importlib.util.find_spec(): 93d.; *note
     importlib.machinery.PathFinder.find_module(): 93e. is replaced by
     *note importlib.machinery.PathFinder.find_spec(): 93f.; *note
     importlib.abc.MetaPathFinder.find_module(): 467. is replaced by
     *note importlib.abc.MetaPathFinder.find_spec(): 468.; *note
     importlib.abc.PathEntryFinder.find_loader(): 469. and *note
     find_module(): 940. are replaced by *note
     importlib.abc.PathEntryFinder.find_spec(): 46a.; all of the
     ‘xxxLoader’ ABC ‘load_module’ methods (*note
     importlib.abc.Loader.load_module(): 5e8, *note
     importlib.abc.InspectLoader.load_module(): 941, *note
     importlib.abc.FileLoader.load_module(): 942, *note
     importlib.abc.SourceLoader.load_module(): 943.) should no longer be
     implemented, instead loaders should implement an ‘exec_module’
     method (*note importlib.abc.Loader.exec_module(): 5e9, *note
     importlib.abc.InspectLoader.exec_module(): 944. *note
     importlib.abc.SourceLoader.exec_module(): 945.) and let the import
     system take care of the rest; and *note
     importlib.abc.Loader.module_repr(): 946, *note
     importlib.util.module_for_loader(): 947, *note
     importlib.util.set_loader(): 948, and *note
     importlib.util.set_package(): 949. are no longer needed because
     their functions are now handled automatically by the import system.

   * The *note imp: 9a. module is pending deprecation.  To keep
     compatibility with Python 2/3 code bases, the module’s removal is
     currently not scheduled.

   * The *note formatter: 82. module is pending deprecation and is
     slated for removal in Python 3.6.

   * ‘MD5’ as the default `digestmod' for the *note hmac.new(): 859.
     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: 84. module has been
     documented as deprecated in its docstring for quite some time.  It
     now emits a *note DeprecationWarning: 279. and will be removed
     completely in Python 3.5.

   * The undocumented `endtime' argument to *note
     subprocess.Popen.wait(): 597. 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: 7c4. is deprecated.

   * The *note plistlib: d0. *note readPlist(): 484, *note writePlist():
     94a, *note readPlistFromBytes(): 485, and *note
     writePlistToBytes(): 94b. functions are deprecated in favor of the
     corresponding new functions *note load(): 890, *note dump(): 891,
     *note loads(): 892, and *note dumps(): 893.  *note Data(): 94c. is
     deprecated in favor of just using the *note bytes: 336.
     constructor.

   * The *note sysconfig: ff. 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: 5f8. (if needed) and
     its `newline' argument.

   * The `parser' argument of *note xml.etree.ElementTree.iterparse():
     94d. has been deprecated, as has the `html' argument of *note
     XMLParser(): 253.  To prepare for the removal of the latter, all
     arguments to ‘XMLParser’ should be passed by keyword.


File: python.info,  Node: Deprecated Features,  Prev: Deprecations in the Python API,  Up: Deprecated<4>

1.5.6.2 Deprecated Features
...........................

   * Running *note IDLE: 94f. 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/issue18823

   (2) https://bugs.python.org/issue19375


File: python.info,  Node: Removed<3>,  Next: Porting to Python 3 4,  Prev: Deprecated<4>,  Up: What's New In Python 3 4

1.5.7 Removed
-------------

* Menu:

* Operating Systems No Longer Supported::
* API and Feature Removals: API and Feature Removals<5>.
* Code Cleanups::


File: python.info,  Node: Operating Systems No Longer Supported,  Next: API and Feature Removals<5>,  Up: Removed<3>

1.5.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/issue16135

   (2) https://bugs.python.org/issue14470

   (3) https://bugs.python.org/issue16136


File: python.info,  Node: API and Feature Removals<5>,  Next: Code Cleanups,  Prev: Operating Systems No Longer Supported,  Up: Removed<3>

1.5.7.2 API and Feature Removals
................................

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: 9b.  (Contributed by Taras Lyapun in bpo-15641(4).)

   * The `strict' argument to *note HTTPConnection: 397. and *note
     HTTPSConnection: 398. has been removed.  HTTP 0.9-style "Simple
     Responses" are no longer supported.

   * The deprecated *note urllib.request.Request: 8fb. 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: b1.  (Contributed by Dan Riti in bpo-15480(5).)

   * *note inspect.Signature: 6f8.: positional-only parameters are now
     required to have a valid name.

   * *note object.__format__(): 953. no longer accepts non-empty format
     strings, it now raises a *note TypeError: 193. 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: 193. 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: 954. object (bpo-13248(7)).

   ---------- Footnotes ----------

   (1) https://devguide.python.org

   (2) https://bugs.python.org/issue16754

   (3) https://bugs.python.org/issue19199

   (4) https://bugs.python.org/issue15641

   (5) https://bugs.python.org/issue15480

   (6) https://bugs.python.org/issue7994

   (7) https://bugs.python.org/issue13248


File: python.info,  Node: Code Cleanups,  Prev: API and Feature Removals<5>,  Up: Removed<3>

1.5.7.3 Code Cleanups
.....................

   * The unused and undocumented internal ‘Scanner’ class has been
     removed from the *note pydoc: da. module.

   * The private and effectively unused ‘_gestalt’ module has been
     removed, along with the private *note platform: cf. 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: f5. constants that were
     included in the *note tarfile: 102. module namespace have been
     removed.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue18393


File: python.info,  Node: Porting to Python 3 4,  Next: Changed in 3 4 3,  Prev: Removed<3>,  Up: What's New In Python 3 4

1.5.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>.
* Changes in the Python API: Changes in the Python API<5>.
* Changes in the C API: Changes in the C API<5>.


File: python.info,  Node: Changes in 'python' Command Behavior<2>,  Next: Changes in the Python API<5>,  Up: Porting to Python 3 4

1.5.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: 958. to an empty value was `not'
     equivalent to not setting it at all: setting *note PYTHONPATH: 958.
     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: 6.) now output ‘--version’ information to ‘stdout’
     instead of ‘stderr’ (for issue list see *note Other Improvements:
     92f. above).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17323


File: python.info,  Node: Changes in the Python API<5>,  Next: Changes in the C API<5>,  Prev: Changes in 'python' Command Behavior<2>,  Up: Porting to Python 3 4

1.5.8.2 Changes in the Python API
.................................

   * The ABCs defined in *note importlib.abc: 9c. now either raise the
     appropriate exception or return a default value instead of raising
     *note NotImplementedError: 613. blindly.  This will only affect
     code calling *note super(): 4e7. and falling through all the way to
     the ABCs.  For compatibility, catch both *note NotImplementedError:
     613. or the appropriate exception as needed.

   * The module type now initializes the *note __package__: 95a. and
     *note __loader__: 95b. 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).)

   * *note importlib.util.module_for_loader(): 947. 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:
     95c, or if Python 2 compatibility is necessary you can use
     ‘imp.is_frozen()’.

   * *note py_compile.compile(): 216. now raises *note FileExistsError:
     95d. 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(): 95e. no longer
     raises *note ImportError: 339. when the source code being loaded
     triggers a *note SyntaxError: 45d. or *note UnicodeDecodeError:
     1fe.  As *note ImportError: 339. 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(): 95f. and *note functools.wraps():
     86f. 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(): 86e. to access the
     first function in the chain that has no ‘__wrapped__’ attribute.

   * *note inspect.getfullargspec(): 562. has been reimplemented on top
     of *note inspect.signature(): 560. 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():
     562. will fail on non-Python callables may need to be adjusted
     accordingly.

   * *note importlib.machinery.PathFinder: 960. now passes on the
     current working directory to objects in *note sys.path_hooks: 961.
     for the empty string.  This results in *note
     sys.path_importer_cache: 4a2. never containing ‘''’, thus iterating
     through *note sys.path_importer_cache: 4a2. based on *note
     sys.path: 48d. 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: 397.
     and *note HTTPSConnection: 398. 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: 45d.  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(): 8d6. and *note
     ssl.SSLSocket.do_handshake(): 75f. now raise an *note OSError: 1d4.
     with ‘ENOTCONN’ when the ‘SSLSocket’ is not connected, instead of
     the previous behavior of raising an *note AttributeError: 3a0.  In
     addition, *note getpeercert(): 8d6. will raise a *note ValueError:
     1fc. if the handshake has not yet been done.

   * *note base64.b32decode(): 962. now raises a *note binascii.Error:
     963. when the input string contains non-b32-alphabet characters,
     instead of a *note TypeError: 193.  This particular *note
     TypeError: 193. was missed when the other *note TypeError: 193.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: 1fc. rather than the previous more
     mysterious *note AttributeError: 3a0. (bpo-9177(8)).

   * *note slice.indices(): 964. no longer produces an *note
     OverflowError: 965. for huge values.  As a consequence of this fix,
     *note slice.indices(): 964. now raises a *note ValueError: 1fc. if
     given a negative length; previously it returned nonsense values
     (bpo-14794(9)).

   * The *note complex: 18a. constructor, unlike the *note cmath: 19.
     functions, was incorrectly accepting *note float: 188. values if an
     object’s ‘__complex__’ special method returned one.  This now
     raises a *note TypeError: 193.  (bpo-16290(10).)

   * The *note int: 185. constructor in 3.2 and 3.3 erroneously accepts
     *note float: 188. values for the `base' parameter.  It is unlikely
     anyone was doing this, but if so, it will now raise a *note
     TypeError: 193. (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(): 966.  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 ‘__kwdefaults__’.  (Contributed by Yury
     Selivanov in bpo-20625(14).)

   * *note hashlib.hash.name: 857. 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: 6d3. now drops references to
     tests after they are run, test harnesses that re-use a *note
     TestSuite: 6d3. 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: 11c. is designed to provide.  However, if the lack of
     isolation is considered acceptable, the old behavior can be
     restored by creating a *note TestSuite: 6d3. subclass that defines
     a ‘_removeTestAtIndex’ method that does nothing (see *note
     TestSuite.__iter__(): 967.) (bpo-11798(16)).

   * *note unittest: 11c. now uses *note argparse: 6. 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(): 3cf, *note re.findall(): 968, and *note
     re.sub(): 480. 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: 5ed.  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.

   * *note audioop: d. 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: 7c4.
     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: 7c4. calls in your code (bpo-13633(18)).

   * Since the `digestmod' argument to the *note hmac.new(): 859.
     function will in the future have no default, all calls to *note
     hmac.new(): 859. should be changed to explicitly specify a
     `digestmod' (bpo-17276(19)).

   * Calling *note sysconfig.get_config_var(): 969. with the ‘SO’ key,
     or looking ‘SO’ up in the results of a call to *note
     sysconfig.get_config_vars(): 96a. 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: 5f8. 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(): 609. and *note
     json.dumps(): 60a. 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: 67. 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: 1f. 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:
     1e. automatically imports *note collections.abc: 1f.  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/issue17115

   (2) https://bugs.python.org/issue19413

   (3) https://bugs.python.org/issue18065

   (4) https://bugs.python.org/issue18416

   (5) https://bugs.python.org/issue18416

   (6) https://bugs.python.org/issue17434

   (7) https://bugs.python.org/issue18011

   (8) https://bugs.python.org/issue9177

   (9) https://bugs.python.org/issue14794

   (10) https://bugs.python.org/issue16290

   (11) https://bugs.python.org/issue16772

   (12) https://bugs.python.org/issue16967

   (13) https://bugs.python.org/issue17094

   (14) https://bugs.python.org/issue20625

   (15) https://bugs.python.org/issue18532

   (16) https://bugs.python.org/issue11798

   (17) https://bugs.python.org/issue16685

   (18) https://bugs.python.org/issue13633

   (19) https://bugs.python.org/issue17276

   (20) https://bugs.python.org/issue19555

   (21) https://bugs.python.org/issue15204

   (22) https://bugs.python.org/issue16333

   (23) https://bugs.python.org/issue3158

   (24) https://bugs.python.org/issue20784


File: python.info,  Node: Changes in the C API<5>,  Prev: Changes in the Python API<5>,  Up: Porting to Python 3 4

1.5.8.3 Changes in the C API
............................

   * *note PyEval_EvalFrameEx(): 96c, *note PyObject_Repr(): 96d, and
     *note PyObject_Str(): 96e, 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(): 96f. or is being
     deliberately replaced with a different exception), an explicit
     *note PyErr_Clear(): 970. 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(): 5fd. now sets *note TypeError: 193.
     when its `msg' argument is not set.  Previously only ‘NULL’ was
     returned with no exception set.

   * The result of the *note PyOS_ReadlineFunctionPointer: 971. callback
     must now be a string allocated by *note PyMem_RawMalloc(): 972. or
     *note PyMem_RawRealloc(): 973, or ‘NULL’ if an error occurred,
     instead of a string allocated by *note PyMem_Malloc(): 50a. or
     *note PyMem_Realloc(): 974. (bpo-16742(1))

   * *note PyThread_set_key_value(): 975. 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:
     976. structure has been removed to fix a bug: see bpo-14432(2) for
     the rationale.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16742

   (2) https://bugs.python.org/issue14432


File: python.info,  Node: Changed in 3 4 3,  Prev: Porting to Python 3 4,  Up: What's New In Python 3 4

1.5.9 Changed in 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: Changed in 3 4 3

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

*note http.client: 94. and modules which use it, such as *note
urllib.request: 121. and *note xmlrpc.client: 140, 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: What's New In Python 3 3,  Next: What's New In Python 3 2,  Prev: What's New In Python 3 4,  Up: Python 有什麼新功能？

1.6 What’s New In 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 Release Schedule

* Menu:

* Summary: Summary -- Release highlights<4>. Release highlights
* PEP 405; Virtual Environments: PEP 405 Virtual Environments.
* 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; Python Launcher for Windows: PEP 397 Python Launcher for Windows.
* 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; Function Signature Object: PEP 362 Function Signature Object.
* PEP 421; Adding sys.implementation: PEP 421 Adding sys implementation.
* Using importlib as the Implementation of Import::
* Other Language Changes: Other Language Changes<6>.
* A Finer-Grained Import Lock::
* Builtin functions and types::
* New Modules: New Modules<6>.
* Improved Modules: Improved Modules<6>.
* Optimizations: Optimizations<5>.
* Build and C API Changes: Build and C API Changes<4>.
* Deprecated: Deprecated<5>.
* Porting to Python 3.3: Porting to Python 3 3.

   ---------- Footnotes ----------

   (1) https://docs.python.org/3.3/whatsnew/changelog.html

   (2) https://www.python.org/dev/peps/pep-0398


File: python.info,  Node: Summary -- Release highlights<4>,  Next: PEP 405 Virtual Environments,  Up: What's New In Python 3 3

1.6.1 Summary – Release highlights
----------------------------------

New syntax features:

   * New ‘yield from’ expression for *note generator delegation: 97d.

   * The ‘u'unicode'’ syntax is accepted again for *note str: 335.
     objects.

New library modules:

   * *note faulthandler: 7d. (helps debugging low-level crashes)

   * *note ipaddress: a3. (high-level objects representing IP addresses
     and masks)

   * *note lzma: ae. (compress data using the XZ / LZMA algorithm)

   * *note unittest.mock: 11d. (replace parts of your system under test
     with mock objects)

   * *note venv: 126. (Python *note virtual environments: 97e, as in the
     popular ‘virtualenv’ package)

New built-in features:

   * Reworked *note I/O exception hierarchy: 97f.

Implementation improvements:

   * Rewritten *note import machinery: 980. based on *note importlib:
     9b.

   * More compact *note unicode strings: 981.

   * More compact *note attribute dictionaries: 982.

Significantly Improved Library Modules:

   * C Accelerator for the *note decimal: 983. module.

   * Better unicode handling in the *note email: 984. module (*note
     provisional: 985.).

Security improvements:

   * Hash randomization is switched on by default.

Please read on for a comprehensive list of user-facing changes.


File: python.info,  Node: PEP 405 Virtual Environments,  Next: PEP 420 Implicit Namespace Packages,  Prev: Summary -- Release highlights<4>,  Up: What's New In Python 3 3

1.6.2 PEP 405: Virtual Environments
-----------------------------------

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: 126. 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 Virtual Environments

     PEP written by Carl Meyer; implementation by Carl Meyer and Vinay
     Sajip

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0405


File: python.info,  Node: PEP 420 Implicit Namespace Packages,  Next: PEP 3118 New memoryview implementation and buffer protocol documentation,  Prev: PEP 405 Virtual Environments,  Up: What's New In Python 3 3

1.6.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

     PEP written by Eric V. Smith; implementation by Eric V. Smith and
     Barry Warsaw

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0420

   (2) https://www.python.org/dev/peps/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: What's New In Python 3 3

1.6.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:

* Features::
* API changes::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3118


File: python.info,  Node: Features,  Next: API changes,  Up: PEP 3118 New memoryview implementation and buffer protocol documentation

1.6.4.1 Features
................

   * 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/issue13411


File: python.info,  Node: API changes,  Prev: Features,  Up: PEP 3118 New memoryview implementation and buffer protocol documentation

1.6.4.2 API changes
...................

   * 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: 98c. and
     *note Porting C code: 98d.

(Contributed by Stefan Krah in bpo-10181(1).)

也參考
......

PEP 3118(2) - Revising the Buffer Protocol

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10181

   (2) https://www.python.org/dev/peps/pep-3118


File: python.info,  Node: PEP 393 Flexible String Representation,  Next: PEP 397 Python Launcher for Windows,  Prev: PEP 3118 New memoryview implementation and buffer protocol documentation,  Up: What's New In Python 3 3

1.6.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:

* Functionality::
* Performance and resource usage::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0393


File: python.info,  Node: Functionality,  Next: Performance and resource usage,  Up: PEP 393 Flexible String Representation

1.6.5.1 Functionality
.....................

Changes introduced by PEP 393(1) are the following:

   * 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(): 151. 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: 990. 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)).

   * The ‘./configure’ flag ‘--with-wide-unicode’ has been removed.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0393

   (2) https://bugs.python.org/issue13054


File: python.info,  Node: Performance and resource usage,  Prev: Functionality,  Up: PEP 393 Flexible String Representation

1.6.5.2 Performance and resource usage
......................................

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 written by Martin von Löwis; implementation by Torsten Becker
     and Martin von Löwis.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0393


File: python.info,  Node: PEP 397 Python Launcher for Windows,  Next: PEP 3151 Reworking the OS and IO exception hierarchy,  Prev: PEP 393 Flexible String Representation,  Up: What's New In Python 3 3

1.6.6 PEP 397: Python Launcher for Windows
------------------------------------------

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) - Python Launcher for Windows

     PEP written by Mark Hammond and Martin v.  Löwis; implementation by
     Vinay Sajip.

Launcher documentation: *note Python Launcher for Windows: 994.

Installer PATH modification: *note Finding the Python executable: 995.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue3561

   (2) https://www.python.org/dev/peps/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 Python Launcher for Windows,  Up: What's New In Python 3 3

1.6.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: 1d4, *note IOError: 997, *note
EnvironmentError: 998, *note WindowsError: 999, ‘mmap.error’, *note
socket.error: 99a. or *note select.error: 99b.  All these exception
types are now only one: *note OSError: 1d4.  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: 7c. module, you can catch the adequate
*note OSError: 1d4. subclass.  The available subclasses are the
following:

   * *note BlockingIOError: 99c.

   * *note ChildProcessError: 99d.

   * *note ConnectionError: 6eb.

   * *note FileExistsError: 95d.

   * *note FileNotFoundError: 7c5.

   * *note InterruptedError: 65e.

   * *note IsADirectoryError: 99e.

   * *note NotADirectoryError: 99f.

   * *note PermissionError: 604.

   * *note ProcessLookupError: 9a0.

   * *note TimeoutError: 9a1.

And the *note ConnectionError: 6eb. itself has finer-grained subclasses:

   * *note BrokenPipeError: 9a2.

   * *note ConnectionAbortedError: 9a3.

   * *note ConnectionRefusedError: 9a4.

   * *note ConnectionResetError: 9a5.

Thanks to the new exceptions, common usages of the *note errno: 7c. 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: 7c. 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

     PEP written and implemented by Antoine Pitrou

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: What's New In Python 3 3

1.6.8 PEP 380: Syntax for Delegating to a Subgenerator
------------------------------------------------------

PEP 380 adds the ‘yield from’ expression, allowing a *note generator:
9a7. to delegate part of its operations to another generator.  This
allows a section of code containing *note yield: 190. 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://www.python.org/dev/peps/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: What's New In Python 3 3

1.6.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://www.python.org/dev/peps/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: What's New In Python 3 3

1.6.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

     PEP written by Armin Ronacher.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: What's New In Python 3 3

1.6.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'

Example with nested classes:

     >>> 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'

Example with nested functions:

     >>> 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

     PEP written and implemented by Antoine Pitrou.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3155


File: python.info,  Node: PEP 412 Key-Sharing Dictionary,  Next: PEP 362 Function Signature Object,  Prev: PEP 3155 Qualified name for classes and functions,  Up: What's New In Python 3 3

1.6.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) - Key-Sharing Dictionary

     PEP written and implemented by Mark Shannon.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0412


File: python.info,  Node: PEP 362 Function Signature Object,  Next: PEP 421 Adding sys implementation,  Prev: PEP 412 Key-Sharing Dictionary,  Up: What's New In Python 3 3

1.6.13 PEP 362: Function Signature Object
-----------------------------------------

A new function *note inspect.signature(): 560. 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(): 7cd. objects.  New classes *note inspect.Signature:
6f8, *note inspect.Parameter: 6f9. and *note inspect.BoundArguments:
9ad. 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): - Function Signature Object

     PEP written by Brett Cannon, Yury Selivanov, Larry Hastings, Jiwon
     Seo; implemented by Yury Selivanov.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0362


File: python.info,  Node: PEP 421 Adding sys implementation,  Next: Using importlib as the Implementation of Import,  Prev: PEP 362 Function Signature Object,  Up: What's New In Python 3 3

1.6.14 PEP 421: Adding sys.implementation
-----------------------------------------

A new attribute on the *note sys: fe. module exposes details specific to
the implementation of the currently running interpreter.  The initial
set of attributes on *note sys.implementation: 9af. 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: 9b. 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://www.python.org/dev/peps/pep-3147


File: python.info,  Node: SimpleNamespace,  Up: PEP 421 Adding sys implementation

1.6.14.1 SimpleNamespace
........................

The implementation of ‘sys.implementation’ also introduces a new type to
Python: *note types.SimpleNamespace: 9b1.  In contrast to a
mapping-based namespace, like *note dict: 1b9, ‘SimpleNamespace’ is
attribute-based, like *note object: 2b1.  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) - Adding sys.implementation

     PEP written and implemented by Eric Snow.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0421


File: python.info,  Node: Using importlib as the Implementation of Import,  Next: Other Language Changes<6>,  Prev: PEP 421 Adding sys implementation,  Up: What's New In Python 3 3

1.6.15 Using importlib as the Implementation of Import
------------------------------------------------------

bpo-2377(1) - Replace __import__ w/ importlib.__import__ bpo-13959(2) -
Re-implement parts of *note imp: 9a. in pure Python bpo-14605(3) - Make
import machinery explicit bpo-14646(4) - Require loaders set __loader__
and __package__

The *note __import__(): 615. function is now powered by *note
importlib.__import__(): 9b3.  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: 9b4. section of this document.

* Menu:

* New APIs::
* Visible Changes::

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue2377

   (2) https://bugs.python.org/issue13959

   (3) https://bugs.python.org/issue14605

   (4) https://bugs.python.org/issue14646

   (5) https://www.python.org/dev/peps/pep-0302


File: python.info,  Node: New APIs,  Next: Visible Changes,  Up: Using importlib as the Implementation of Import

1.6.15.1 New APIs
.................

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:
9b. package.

The abstract base classes defined in *note importlib.abc: 9c. have been
expanded to properly delineate between *note meta path finders: 9b6. and
*note path entry finders: 9b7. by introducing *note
importlib.abc.MetaPathFinder: 9b8. and *note
importlib.abc.PathEntryFinder: 9b9, respectively.  The old ABC of *note
importlib.abc.Finder: 9ba. is now only provided for
backwards-compatibility and does not enforce any method requirements.

In terms of finders, *note importlib.machinery.FileFinder: 9bb. 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:
961.

For loaders, the new abstract base class *note importlib.abc.FileLoader:
9bc. 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: 9bd.), sourceless bytecode files
(*note importlib.machinery.SourcelessFileLoader: 9be.), and extension
modules (*note importlib.machinery.ExtensionFileLoader: 55b.) are now
available for direct use.

*note ImportError: 339. 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(): 4a1. function will now call the
method with the same name on all finders cached in *note
sys.path_importer_cache: 4a2. to help clean up any stored state as
necessary.


File: python.info,  Node: Visible Changes,  Prev: New APIs,  Up: Using importlib as the Implementation of Import

1.6.15.2 Visible Changes
........................

For potential required changes to code, see the *note Porting Python
code: 9b4. section.

Beyond the expanse of what *note importlib: 9b. now exposes, there are
other visible changes to import.  The biggest is that *note
sys.meta_path: 5eb. and *note sys.path_hooks: 961. 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: 9b. and import itself is setting the
attribute post-load.

‘None’ is now inserted into *note sys.path_importer_cache: 4a2. when no
finder can be found on *note sys.path_hooks: 961.  Since *note
imp.NullImporter: 9c0. is not directly exposed on *note sys.path_hooks:
961. 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: 9b4. section of this document.

(Implementation by Brett Cannon)

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0302

   (2) https://www.python.org/dev/peps/pep-0366


File: python.info,  Node: Other Language Changes<6>,  Next: A Finer-Grained Import Lock,  Prev: Using importlib as the Implementation of Import,  Up: What's New In Python 3 3

1.6.16 Other Language Changes
-----------------------------

Some smaller changes made to the core Python language are:

   * Added support for Unicode name aliases and named sequences.  Both
     *note unicodedata.lookup(): 9c2. and ‘'\N{...}'’ now resolve name
     aliases, and *note unicodedata.lookup(): 9c2. resolves named
     sequences too.

     (Contributed by Ezio Melotti in bpo-12753(1).)

   * Unicode database updated to UCD version 6.1.0

   * Equality comparisons on *note range(): 9c3. 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: 336. and *note bytearray: 337. objects now
     accept an integer between 0 and 255 as their first argument.

     (Contributed by Petri Lehtinen in bpo-12170(3).)

   * The ‘rjust()’, ‘ljust()’, and ‘center()’ methods of *note bytes:
     336. and *note bytearray: 337. now accept a *note bytearray: 337.
     for the ‘fill’ argument.  (Contributed by Petri Lehtinen in
     bpo-12380(4).)

   * New methods have been added to *note list: 263. and *note
     bytearray: 337.: ‘copy()’ and ‘clear()’ (bpo-10516(5)).
     Consequently, *note MutableSequence: 6b1. now also defines a
     ‘clear()’ method (bpo-11388(6)).

   * Raw bytes literals can now be written ‘rb"..."’ as well as
     ‘br"..."’.

     (Contributed by Antoine Pitrou in bpo-13748(7).)

   * *note dict.setdefault(): 9c4. now does only one lookup for the
     given key, making it atomic when used with built-in types.

     (Contributed by Filip Gruszczyński in bpo-13521(8).)

   * The error messages produced when a function call does not match the
     function signature have been significantly improved.

     (Contributed by Benjamin Peterson.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue12753

   (2) https://bugs.python.org/issue13201

   (3) https://bugs.python.org/issue12170

   (4) https://bugs.python.org/issue12380

   (5) https://bugs.python.org/issue10516

   (6) https://bugs.python.org/issue11388

   (7) https://bugs.python.org/issue13748

   (8) https://bugs.python.org/issue13521


File: python.info,  Node: A Finer-Grained Import Lock,  Next: Builtin functions and types,  Prev: Other Language Changes<6>,  Up: What's New In Python 3 3

1.6.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(): 9c6. 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.

(Contributed by Antoine Pitrou in bpo-9260(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue9260


File: python.info,  Node: Builtin functions and types,  Next: New Modules<6>,  Prev: A Finer-Grained Import Lock,  Up: What's New In Python 3 3

1.6.18 Builtin functions and types
----------------------------------

   * *note open(): 4f5. 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: 9c8. for example.  The ‘'x'’ mode
     was added: open for exclusive creation, failing if the file already
     exists.

   * *note print(): 88b.: added the `flush' keyword argument.  If the
     `flush' keyword argument is true, the stream is forcibly flushed.

   * *note hash(): 9c9.: hash randomization is enabled by default, see
     *note object.__hash__(): 345. and *note PYTHONHASHSEED: 9ca.

   * The *note str: 335. type gets a new *note casefold(): 6b5. 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/issue4966


File: python.info,  Node: New Modules<6>,  Next: Improved Modules<6>,  Prev: Builtin functions and types,  Up: What's New In Python 3 3

1.6.19 New Modules
------------------

* Menu:

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


File: python.info,  Node: faulthandler<3>,  Next: ipaddress<4>,  Up: New Modules<6>

1.6.19.1 faulthandler
.....................

This new debug module *note faulthandler: 7d. 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(): 54d. 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: 9cd.
environment variable or by using *note -X: 156. ‘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<4>,  Next: lzma<2>,  Prev: faulthandler<3>,  Up: New Modules<6>

1.6.19.2 ipaddress
..................

The new *note ipaddress: a3. 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).

(Contributed by Google and Peter Moody in PEP 3144(1).)

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3144


File: python.info,  Node: lzma<2>,  Prev: ipaddress<4>,  Up: New Modules<6>

1.6.19.3 lzma
.............

The newly-added *note lzma: ae. module provides data compression and
decompression using the LZMA algorithm, including support for the ‘.xz’
and ‘.lzma’ file formats.

(Contributed by Nadeem Vawda and Per Øyvind Karlsen in bpo-6715(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue6715


File: python.info,  Node: Improved Modules<6>,  Next: Optimizations<5>,  Prev: New Modules<6>,  Up: What's New In Python 3 3

1.6.20 Improved Modules
-----------------------

* Menu:

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


File: python.info,  Node: abc<2>,  Next: array<2>,  Up: Improved Modules<6>

1.6.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: 9d2. has been deprecated, use
          *note property: 1d8. with *note abc.abstractmethod(): 9d3.
          instead.

        * *note abc.abstractclassmethod: 9d4. has been deprecated, use
          *note classmethod: 1d9. with *note abc.abstractmethod(): 9d3.
          instead.

        * *note abc.abstractstaticmethod: 9d5. has been deprecated, use
          *note staticmethod: 1da. with *note abc.abstractmethod(): 9d3.
          instead.

(Contributed by Darren Dale in bpo-11610(1).)

*note abc.ABCMeta.register(): 9d6. 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/issue11610

   (2) https://bugs.python.org/issue10868


File: python.info,  Node: array<2>,  Next: base64<2>,  Prev: abc<2>,  Up: Improved Modules<6>

1.6.20.2 array
..............

The *note array: 7. module supports the ‘long long’ type using ‘q’ and
‘Q’ type codes.

(Contributed by Oren Tirosh and Hirokazu Yamamoto in bpo-1172711(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue1172711


File: python.info,  Node: base64<2>,  Next: binascii<3>,  Prev: array<2>,  Up: Improved Modules<6>

1.6.20.3 base64
...............

ASCII-only Unicode strings are now accepted by the decoding functions of
the *note base64: e. modern interface.  For example,
‘base64.b64decode('YWJj')’ returns ‘b'abc'’.  (Contributed by Catalin
Iacob in bpo-13641(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue13641


File: python.info,  Node: binascii<3>,  Next: bz2<2>,  Prev: base64<2>,  Up: Improved Modules<6>

1.6.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/issue13637


File: python.info,  Node: bz2<2>,  Next: codecs,  Prev: binascii<3>,  Up: Improved Modules<6>

1.6.20.5 bz2
............

The *note bz2: 14. module has been rewritten from scratch.  In the
process, several new features have been added:

   * New *note bz2.open(): 9db. function: open a bzip2-compressed file
     in binary or text mode.

   * *note bz2.BZ2File: 936. can now read from and write to arbitrary
     file-like objects, by means of its constructor’s `fileobj'
     argument.

     (Contributed by Nadeem Vawda in bpo-5863(1).)

   * *note bz2.BZ2File: 936. and *note bz2.decompress(): 9dc. can now
     decompress multi-stream inputs (such as those produced by the
     ‘pbzip2’ tool).  *note bz2.BZ2File: 936. can now also be used to
     create this type of file, using the ‘'a'’ (append) mode.

     (Contributed by Nir Aides in bpo-1625(2).)

   * *note bz2.BZ2File: 936. now implements all of the *note
     io.BufferedIOBase: 58d. API, except for the ‘detach()’ and
     ‘truncate()’ methods.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue5863

   (2) https://bugs.python.org/issue1625


File: python.info,  Node: codecs,  Next: collections<7>,  Prev: bz2<2>,  Up: Improved Modules<6>

1.6.20.6 codecs
...............

The *note mbcs: 78. codec has been rewritten to handle correctly
‘replace’ and ‘ignore’ error handlers on all Windows versions.  The
*note mbcs: 78. 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))

The ‘unicode_internal’ codec has been deprecated.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue13216

   (2) https://bugs.python.org/issue12016

   (3) https://bugs.python.org/issue12100


File: python.info,  Node: collections<7>,  Next: contextlib<5>,  Prev: codecs,  Up: Improved Modules<6>

1.6.20.7 collections
....................

Addition of a new *note ChainMap: 4ae. 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: 1f. module, to better differentiate between the
abstract and the concrete collections classes.  Aliases for ABCs are
still present in the *note collections: 1e. module to preserve existing
imports.  (bpo-11085(3))

The *note Counter: 9df. 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/issue11089

   (2) https://bugs.python.org/issue11297

   (3) https://bugs.python.org/issue11085

   (4) https://bugs.python.org/issue13121


File: python.info,  Node: contextlib<5>,  Next: crypt<2>,  Prev: collections<7>,  Up: Improved Modules<6>

1.6.20.8 contextlib
...................

*note ExitStack: 37b. 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: 10a. module).

(bpo-13585(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue13585


File: python.info,  Node: crypt<2>,  Next: curses<3>,  Prev: contextlib<5>,  Up: Improved Modules<6>

1.6.20.9 crypt
..............

Addition of salt and modular crypt format (hashing method) and the *note
mksalt(): 381. function to the *note crypt: 29. module.

(bpo-10924(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10924


File: python.info,  Node: curses<3>,  Next: datetime<4>,  Prev: crypt<2>,  Up: Improved Modules<6>

1.6.20.10 curses
................

        * If the *note curses: 2c. 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’ has a new *note curses.window.encoding: 9e3.
          attribute.

        * The ‘curses.window’ class has a new *note get_wch(): 9e4.
          method to get a wide character

        * The *note curses: 2c. module has a new *note unget_wch(): 9e5.
          function to push a wide character so the next *note get_wch():
          9e4. will return it

(Contributed by Iñigo Serna in bpo-6755(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue6755


File: python.info,  Node: datetime<4>,  Next: decimal<3>,  Prev: curses<3>,  Up: Improved Modules<6>

1.6.20.11 datetime
..................

        * Equality comparisons between naive and aware *note datetime:
          195. instances now return *note False: 38d. instead of raising
          *note TypeError: 193. (bpo-15006(1)).

        * New *note datetime.datetime.timestamp(): 9e7. method: Return
          POSIX timestamp corresponding to the *note datetime: 195.
          instance.

        * The *note datetime.datetime.strftime(): 53c. method supports
          formatting years older than 1000.

        * The *note datetime.datetime.astimezone(): 197. method can now
          be called without arguments to convert datetime instance to
          the system timezone.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue15006


File: python.info,  Node: decimal<3>,  Next: email<4>,  Prev: datetime<4>,  Up: Improved Modules<6>

1.6.20.12 decimal
.................

bpo-7652(1) - integrate fast native decimal arithmetic.

     C-module and libmpdec written by Stefan Krah.

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 ‘http://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:

* Features: Features<2>.
* API changes: API changes<2>.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue7652


File: python.info,  Node: Features<2>,  Next: API changes<2>,  Up: decimal<3>

1.6.20.13 Features
..................

   * The *note FloatOperation: 9ea. 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: 9eb. is set to ‘False’.


File: python.info,  Node: API changes<2>,  Prev: Features<2>,  Up: decimal<3>

1.6.20.14 API changes
.....................

   * The C module has the following context limits, depending on the
     machine architecture:

                                  32-bit                    64-bit
                                                            
          -------------------------------------------------------------------------------------
                                                            
          ‘MAX_PREC’              ‘425000000’               ‘999999999999999999’
                                                            
                                                            
          ‘MAX_EMAX’              ‘425000000’               ‘999999999999999999’
                                                            
                                                            
          ‘MIN_EMIN’              ‘-425000000’              ‘-999999999999999999’
                                                            

   * In the context templates (*note DefaultContext: 9ed, *note
     BasicContext: 9ee. and *note ExtendedContext: 9ef.) the magnitude
     of ‘Emax’ and ‘Emin’ has changed to ‘999999’.

   * The *note Decimal: 189. 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: 9f0. is raised and the
     result is NaN. In the latter case it is always possible to use
     *note create_decimal(): 9f1. 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(): 9f2. and *note ln(): 9f3. 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: 9f4.  For speed reasons, ‘flags’ and
     ‘traps’ always refer to the same *note MutableMapping: 9f4. 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: 9f5. 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: 9f5. constructor has
     been changed to match the order displayed by *note repr(): 7d1.

   * The ‘watchexp’ parameter in the *note quantize(): 9f6. method is
     deprecated.


File: python.info,  Node: email<4>,  Next: ftplib,  Prev: decimal<3>,  Up: Improved Modules<6>

1.6.20.15 email
...............

* Menu:

* Policy Framework::
* Provisional Policy with New Header API::
* Other API Changes::


File: python.info,  Node: Policy Framework,  Next: Provisional Policy with New Header API,  Up: email<4>

1.6.20.16 Policy Framework
..........................

The email package now has a *note policy: 75. framework.  A *note
Policy: 9f9. 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: 9fa. 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: 74, or when
a *note Message: 546. object is created, or when an email is serialized
using a *note generator: 6e.  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: 545.

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(): 9fb. 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: Other API Changes,  Prev: Policy Framework,  Up: email<4>

1.6.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: 985.
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: 9fd, and add the
following additional controls:

     refold_source       Controls whether or not headers parsed by a
                         *note parser: 74. are refolded by the
                         *note generator: 6e.  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: 6f. *note decode_header():
9fe. or *note make_header(): 9ff. 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>

Decoding to unicode is done automatically:

     >>> 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: Other API Changes,  Prev: Provisional Policy with New Header API,  Up: email<4>

1.6.20.18 Other API Changes
...........................

New *note BytesHeaderParser: a01, added to the *note parser: 74. module
to complement *note HeaderParser: a02. and complete the Bytes API.

New utility functions:

        * *note format_datetime(): a03.: given a *note datetime: 195,
          produce a string formatted for use in an email header.

        * *note parsedate_to_datetime(): a04.: given a date string from
          an email header, convert it into an aware *note datetime: 195,
          or a naive *note datetime: 195. if the offset is ‘-0000’.

        * *note localtime(): a05.: With no argument, returns the current
          local time as an aware *note datetime: 195. using the local
          *note timezone: a06.  Given an aware *note datetime: 195,
          converts it into an aware *note datetime: 195. using the local
          *note timezone: a06.


File: python.info,  Node: ftplib,  Next: functools<5>,  Prev: email<4>,  Up: Improved Modules<6>

1.6.20.19 ftplib
................

   * *note ftplib.FTP: 2f1. 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: a08. class now provides a new *note ccc(): a09.
     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(): a0a. method which provides a
     parsable directory listing format and deprecates *note
     ftplib.FTP.nlst(): a0b. and *note ftplib.FTP.dir(): a0c.
     (Contributed by Giampaolo Rodolà in bpo-11072(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue8594

   (2) https://bugs.python.org/issue12139

   (3) https://bugs.python.org/issue11072


File: python.info,  Node: functools<5>,  Next: gc<4>,  Prev: ftplib,  Up: Improved Modules<6>

1.6.20.20 functools
...................

The *note functools.lru_cache(): 1c8. 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/issue13227


File: python.info,  Node: gc<4>,  Next: hmac<3>,  Prev: functools<5>,  Up: Improved Modules<6>

1.6.20.21 gc
............

It is now possible to register callbacks invoked by the garbage
collector before and after collection using the new *note callbacks:
a0f. list.


File: python.info,  Node: hmac<3>,  Next: http<3>,  Prev: gc<4>,  Up: Improved Modules<6>

1.6.20.22 hmac
..............

A new *note compare_digest(): a11. 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/issue15061


File: python.info,  Node: http<3>,  Next: html<2>,  Prev: hmac<3>,  Up: Improved Modules<6>

1.6.20.23 http
..............

*note http.server.BaseHTTPRequestHandler: a13. now buffers the headers
and writes them all at once when *note end_headers(): a14. is called.  A
new method *note flush_headers(): a15. can be used to directly manage
when the accumulated headers are sent.  (Contributed by Andrew Schaaf in
bpo-3709(1).)

*note http.server: 97. now produces valid ‘HTML 4.01 strict’ output.
(Contributed by Ezio Melotti in bpo-13295(2).)

*note http.client.HTTPResponse: a16. now has a *note readinto(): a17.
method, which means it can be used as an *note io.RawIOBase: a18. class.
(Contributed by John Kuhn in bpo-13464(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue3709

   (2) https://bugs.python.org/issue13295

   (3) https://bugs.python.org/issue13464


File: python.info,  Node: html<2>,  Next: imaplib<2>,  Prev: http<3>,  Up: Improved Modules<6>

1.6.20.24 html
..............

*note html.parser.HTMLParser: 7c4. 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: a1a. 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: 91. module.  The
dictionary is now also used by *note HTMLParser: 7c4.  (Contributed by
Ezio Melotti in bpo-11113(15) and bpo-15156(16).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue15114

   (2) https://bugs.python.org/issue14538

   (3) https://bugs.python.org/issue13993

   (4) https://bugs.python.org/issue13960

   (5) https://bugs.python.org/issue13358

   (6) https://bugs.python.org/issue1745761

   (7) https://bugs.python.org/issue755670

   (8) https://bugs.python.org/issue13357

   (9) https://bugs.python.org/issue12629

   (10) https://bugs.python.org/issue1200313

   (11) https://bugs.python.org/issue670664

   (12) https://bugs.python.org/issue13273

   (13) https://bugs.python.org/issue12888

   (14) https://bugs.python.org/issue7311

   (15) https://bugs.python.org/issue11113

   (16) https://bugs.python.org/issue15156


File: python.info,  Node: imaplib<2>,  Next: inspect<5>,  Prev: html<2>,  Up: Improved Modules<6>

1.6.20.25 imaplib
.................

The *note IMAP4_SSL: a1c. constructor now accepts an SSLContext
parameter to control parameters of the secure channel.

(Contributed by Sijin Joseph in bpo-8808(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue8808


File: python.info,  Node: inspect<5>,  Next: io<4>,  Prev: imaplib<2>,  Up: Improved Modules<6>

1.6.20.26 inspect
.................

A new *note getclosurevars(): a1e. 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.

(Contributed by Meador Inge and Nick Coghlan in bpo-13062(1).)

A new *note getgeneratorlocals(): a1f. 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.

(Contributed by Meador Inge in bpo-15153(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue13062

   (2) https://bugs.python.org/issue15153


File: python.info,  Node: io<4>,  Next: itertools<3>,  Prev: inspect<5>,  Up: Improved Modules<6>

1.6.20.27 io
............

The *note open(): 65f. function has a new ‘'x'’ mode that can be used to
exclusively create a new file, and raise a *note FileExistsError: 95d.
if the file already exists.  It is based on the C11 ’x’ mode to fopen().

(Contributed by David Townshend in bpo-12760(1).)

The constructor of the *note TextIOWrapper: 5f8. 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: 5f8. object is immediately handled to its
underlying binary buffer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue12760


File: python.info,  Node: itertools<3>,  Next: logging<6>,  Prev: io<4>,  Up: Improved Modules<6>

1.6.20.28 itertools
...................

*note accumulate(): 1de. now takes an optional ‘func’ argument for
providing a user-supplied binary function.


File: python.info,  Node: logging<6>,  Next: math<5>,  Prev: itertools<3>,  Up: Improved Modules<6>

1.6.20.29 logging
.................

The *note basicConfig(): 1e1. 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: a23. 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<5>,  Next: mmap<3>,  Prev: logging<6>,  Up: Improved Modules<6>

1.6.20.30 math
..............

The *note math: b2. module has a new function, *note log2(): a25, which
returns the base-2 logarithm of `x'.

(Written by Mark Dickinson in bpo-11888(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue11888


File: python.info,  Node: mmap<3>,  Next: multiprocessing<6>,  Prev: math<5>,  Up: Improved Modules<6>

1.6.20.31 mmap
..............

The *note read(): a27. 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/issue12021


File: python.info,  Node: multiprocessing<6>,  Next: nntplib,  Prev: mmap<3>,  Up: Improved Modules<6>

1.6.20.32 multiprocessing
.........................

The new *note multiprocessing.connection.wait(): a29. 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: 3b7. 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: a2a. allows a
program to wait on multiple *note Process: 3b7. objects at one time
using the appropriate OS primitives (for example, *note select: e6. on
posix systems).

New methods *note multiprocessing.pool.Pool.starmap(): a2b. and *note
starmap_async(): a2c. provide *note itertools.starmap(): a2d.
equivalents to the existing *note multiprocessing.pool.Pool.map(): a2e.
and *note map_async(): a2f. functions.  (Contributed by Hynek Schlawack
in bpo-12708(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue12328

   (2) https://bugs.python.org/issue4892

   (3) https://bugs.python.org/issue6064

   (4) https://bugs.python.org/issue12708


File: python.info,  Node: nntplib,  Next: os<7>,  Prev: multiprocessing<6>,  Up: Improved Modules<6>

1.6.20.33 nntplib
.................

The *note nntplib.NNTP: a31. class now supports the context management
protocol to unconditionally consume *note socket.error: 99a. 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')
     >>>

(Contributed by Giampaolo Rodolà in bpo-9795(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue9795


File: python.info,  Node: os<7>,  Next: pdb<4>,  Prev: nntplib,  Up: Improved Modules<6>

1.6.20.34 os
............

   * The *note os: c5. module has a new *note pipe2(): a33. function
     that makes it possible to create a pipe with *note O_CLOEXEC: 9c8.
     or *note O_NONBLOCK: 728. flags set atomically.  This is especially
     useful to avoid race conditions in multi-threaded programs.

   * The *note os: c5. module has a new *note sendfile(): 35e. 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(): 35e. can be used to
     efficiently copy data from a file on disk to a network socket, e.g.
     for downloading a file.

     (Patch submitted by Ross Lagerwall and Giampaolo Rodolà in
     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: c5. module has a new *note fwalk(): 3b9.
          function similar to *note walk(): 659. 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: a34.) and/or
          `follow_symlinks' (*note not following symlinks: a35.): *note
          access(): a36, *note chflags(): a37, *note chmod(): a38, *note
          chown(): a39, *note link(): a3a, *note lstat(): 1f3, *note
          mkdir(): a3b, *note mkfifo(): 668, *note mknod(): 669, *note
          open(): 66a, *note readlink(): 1f4, *note remove(): a3c, *note
          rename(): a3d, *note replace(): a3e, *note rmdir(): a3f, *note
          stat(): 1f2, *note symlink(): a40, *note unlink(): a41, *note
          utime(): a42.  Platform support for using these parameters can
          be checked via the sets *note os.supports_dir_fd: a43. and
          ‘os.supports_follows_symlinks’.

        - The following functions now support a file descriptor for
          their path argument: *note chdir(): a44, *note chmod(): a38,
          *note chown(): a39, *note execve(): a45, *note listdir(): a46,
          *note pathconf(): a47, *note exists(): 1f7, *note stat(): 1f2,
          *note statvfs(): a48, *note utime(): a42.  Platform support
          for this can be checked via the *note os.supports_fd: a49.
          set.

   * *note access(): a36. 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: a4a. set.

   * The *note os: c5. module has two new functions: *note
     getpriority(): a4b. and *note setpriority(): a4c.  They can be used
     to get or set process niceness/priority in a fashion similar to
     *note os.nice(): a4d. but extended to all processes instead of just
     the current one.

     (Patch submitted by Giampaolo Rodolà in bpo-10784(5).)

   * The new *note os.replace(): a3e. function allows cross-platform
     renaming of a file with overwriting the destination.  With *note
     os.rename(): a3d, 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(): 1f2, *note fstat():
     664, and *note lstat(): 1f3.) now support reading a file’s
     timestamps with nanosecond precision.  Symmetrically, *note
     utime(): a42. can now write file timestamps with nanosecond
     precision.  (Contributed by Larry Hastings in bpo-14127(7).)

   * The new *note os.get_terminal_size(): a4e. function queries the
     size of the terminal attached to a file descriptor.  See also *note
     shutil.get_terminal_size(): a4f.  (Contributed by Zbigniew
     Jędrzejewski-Szmek in bpo-13609(8).)

   * New functions to support Linux extended attributes (bpo-12720(9)):
     *note getxattr(): a50, *note listxattr(): a51, *note removexattr():
     a52, *note setxattr(): a53.

   * 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(): a54, *note
     sched_get_priority_min(): a55, *note sched_getaffinity(): a56,
     *note sched_getparam(): a57, *note sched_getscheduler(): a58, *note
     sched_rr_get_interval(): a59, *note sched_setaffinity(): a5a, *note
     sched_setparam(): a5b, *note sched_setscheduler(): a5c, *note
     sched_yield(): a5d,

   * New functions to control the file system:

        * *note posix_fadvise(): 66b.: Announces an intention to access
          data in a specific pattern thus allowing the kernel to make
          optimizations.

        * *note posix_fallocate(): 66c.: Ensures that enough disk space
          is allocated for a file.

        * *note sync(): a5e.: Force write of everything to disk.

   * Additional new posix functions:

        * *note lockf(): a5f.: Apply, test or remove a POSIX lock on an
          open file descriptor.

        * *note pread(): 3be.: Read from a file descriptor at an offset,
          the file offset remains unchanged.

        * *note pwrite(): 3c1.: Write to a file descriptor from an
          offset, leaving the file offset unchanged.

        * *note readv(): 3bd.: Read from a file descriptor into a number
          of writable buffers.

        * *note truncate(): 729.: Truncate the file corresponding to
          `path', so that it is at most `length' bytes in size.

        * *note waitid(): 671.: Wait for the completion of one or more
          child processes.

        * *note writev(): 3c0.: Write the contents of `buffers' to a
          file descriptor, where `buffers' is an arbitrary sequence of
          buffers.

        * *note getgrouplist(): a60. (bpo-9344(10)): Return list of
          group ids that specified user belongs to.

   * *note times(): a61. and *note uname(): a62.: Return type changed
     from a tuple to a tuple-like object with named attributes.

   * Some platforms now support additional constants for the *note
     lseek(): a63. function, such as ‘os.SEEK_HOLE’ and ‘os.SEEK_DATA’.

   * New constants *note RTLD_LAZY: a64, *note RTLD_NOW: a65, *note
     RTLD_GLOBAL: a66, *note RTLD_LOCAL: a67, *note RTLD_NODELETE: a68,
     *note RTLD_NOLOAD: a69, and *note RTLD_DEEPBIND: a6a. are available
     on platforms that support them.  These are for use with the *note
     sys.setdlopenflags(): a6b. function, and supersede the similar
     constants defined in *note ctypes: 2b. and ‘DLFCN’.  (Contributed
     by Victor Stinner in bpo-13226(11).)

   * *note os.symlink(): a40. 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/issue10882

   (2) https://bugs.python.org/issue4761

   (3) https://bugs.python.org/issue10755

   (4) https://bugs.python.org/issue14626

   (5) https://bugs.python.org/issue10784

   (6) https://bugs.python.org/issue8828

   (7) https://bugs.python.org/issue14127

   (8) https://bugs.python.org/issue13609

   (9) https://bugs.python.org/issue12720

   (10) https://bugs.python.org/issue9344

   (11) https://bugs.python.org/issue13226


File: python.info,  Node: pdb<4>,  Next: pickle<5>,  Prev: os<7>,  Up: Improved Modules<6>

1.6.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.

(Contributed by Georg Brandl in bpo-14210(1))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14210


File: python.info,  Node: pickle<5>,  Next: pydoc<4>,  Prev: pdb<4>,  Up: Improved Modules<6>

1.6.20.36 pickle
................

*note pickle.Pickler: 20e. objects now have an optional *note
dispatch_table: a6e. attribute allowing per-pickler reduction functions
to be set.

(Contributed by Richard Oudkerk in bpo-14166(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14166


File: python.info,  Node: pydoc<4>,  Next: re<6>,  Prev: pickle<5>,  Up: Improved Modules<6>

1.6.20.37 pydoc
...............

The Tk GUI and the ‘serve()’ function have been removed from the *note
pydoc: da. module: ‘pydoc -g’ and ‘serve()’ have been deprecated in
Python 3.2.


File: python.info,  Node: re<6>,  Next: sched,  Prev: pydoc<4>,  Up: Improved Modules<6>

1.6.20.38 re
............

*note str: 335. regular expressions now support ‘\u’ and ‘\U’ escapes.

(Contributed by Serhiy Storchaka in bpo-3665(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue3665


File: python.info,  Node: sched,  Next: select<2>,  Prev: re<6>,  Up: Improved Modules<6>

1.6.20.39 sched
...............

   * *note run(): a72. 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: a73. in
     non-blocking applications.  (Contributed by Giampaolo Rodolà in
     bpo-13449(1).)

   * *note scheduler: a73. 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: a73.
     class constructor are now optional and defaults to *note
     time.time(): 322. and *note time.sleep(): 685. respectively.
     (Contributed by Chris Clark in bpo-13245(3).)

   * *note enter(): a74. and *note enterabs(): a75. `argument' parameter
     is now optional.  (Contributed by Chris Clark in bpo-13245(4).)

   * *note enter(): a74. and *note enterabs(): a75. now accept a
     `kwargs' parameter.  (Contributed by Chris Clark in bpo-13245(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue13449

   (2) https://bugs.python.org/issue8684

   (3) https://bugs.python.org/issue13245

   (4) https://bugs.python.org/issue13245

   (5) https://bugs.python.org/issue13245


File: python.info,  Node: select<2>,  Next: shlex<3>,  Prev: sched,  Up: Improved Modules<6>

1.6.20.40 select
................

Solaris and derivative platforms have a new class *note select.devpoll:
8b0. 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/issue6397


File: python.info,  Node: shlex<3>,  Next: shutil<4>,  Prev: select<2>,  Up: Improved Modules<6>

1.6.20.41 shlex
...............

The previously undocumented helper function ‘quote’ from the *note
pipes: cd. modules has been moved to the *note shlex: e9. module and
documented.  *note quote(): a78. properly escapes all characters in a
string that might be otherwise given special meaning by the shell.


File: python.info,  Node: shutil<4>,  Next: signal<3>,  Prev: shlex<3>,  Up: Improved Modules<6>

1.6.20.42 shutil
................

   * New functions:

        * *note disk_usage(): a7a.: provides total, used and free disk
          space statistics.  (Contributed by Giampaolo Rodolà in
          bpo-12442(1).)

        * *note chown(): a7b.: 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(): a4f.: 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(): 25b. and *note copystat(): a7c. 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(): 25c.
     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(): 25c. now also returns the ‘dst’ argument as its result.

   * *note rmtree(): 21d. is now resistant to symlink attacks on
     platforms which support the new ‘dir_fd’ parameter in *note
     os.open(): 66a. and *note os.unlink(): a41.  (Contributed by Martin
     von Löwis and Hynek Schlawack in bpo-4489(8).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue12442

   (2) https://bugs.python.org/issue12191

   (3) https://bugs.python.org/issue13609

   (4) https://bugs.python.org/issue14127

   (5) https://bugs.python.org/issue15238

   (6) https://bugs.python.org/issue12715

   (7) https://bugs.python.org/issue9993

   (8) https://bugs.python.org/issue4489


File: python.info,  Node: signal<3>,  Next: smtpd<3>,  Prev: shutil<4>,  Up: Improved Modules<6>

1.6.20.43 signal
................

   * The *note signal: eb. module has new functions:

        * *note pthread_sigmask(): a7e.: fetch and/or change the signal
          mask of the calling thread (Contributed by Jean-Paul Calderone
          in bpo-8407(1));

        * *note pthread_kill(): a7f.: send a signal to a thread;

        * *note sigpending(): a80.: examine pending functions;

        * *note sigwait(): a81.: wait a signal;

        * *note sigwaitinfo(): 684.: wait for a signal, returning
          detailed information about it;

        * *note sigtimedwait(): 683.: like *note sigwaitinfo(): 684. but
          with a timeout.

   * 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(): a82. and *note signal.siginterrupt(): a83.
     raise an OSError, instead of a RuntimeError: OSError has an errno
     attribute.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue8407


File: python.info,  Node: smtpd<3>,  Next: smtplib<3>,  Prev: signal<3>,  Up: Improved Modules<6>

1.6.20.44 smtpd
...............

The *note smtpd: ed. 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://tools.ietf.org/html/rfc5321.html

   (2) https://tools.ietf.org/html/rfc1870.html

   (3) https://bugs.python.org/issue8739


File: python.info,  Node: smtplib<3>,  Next: socket<7>,  Prev: smtpd<3>,  Up: Improved Modules<6>

1.6.20.45 smtplib
.................

The *note SMTP: a86, *note SMTP_SSL: a87, and *note LMTP: a88. 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: a86. now supports the context management protocol, allowing
an ‘SMTP’ instance to be used in a ‘with’ statement.  (Contributed by
Giampaolo Rodolà in bpo-11289(2).)

The *note SMTP_SSL: a87. constructor and the *note starttls(): a89.
method now accept an SSLContext parameter to control parameters of the
secure channel.  (Contributed by Kasun Herath in bpo-8809(3).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue11281

   (2) https://bugs.python.org/issue11289

   (3) https://bugs.python.org/issue8809


File: python.info,  Node: socket<7>,  Next: socketserver<3>,  Prev: smtplib<3>,  Up: Improved Modules<6>

1.6.20.46 socket
................

   * The *note socket: 679. class now exposes additional methods to
     process ancillary data when supported by the underlying platform:

        * *note sendmsg(): 681.

        * *note recvmsg(): 67e.

        * *note recvmsg_into(): a8b.

     (Contributed by David Watson in bpo-6560(1), based on an earlier
     patch by Heiko Wundram)

   * The *note socket: 679. class now supports the PF_CAN protocol
     family (‘https://en.wikipedia.org/wiki/Socketcan’), on Linux
     (‘https://lwn.net/Articles/253425’).

     (Contributed by Matthias Fuchs, updated by Tiago Gonçalves in
     bpo-10141(2).)

   * The *note socket: 679. class now supports the PF_RDS protocol
     family (‘https://en.wikipedia.org/wiki/Reliable_Datagram_Sockets’
     and ‘https://oss.oracle.com/projects/rds/’).

   * The *note socket: 679. class now supports the ‘PF_SYSTEM’ protocol
     family on OS X. (Contributed by Michael Goderbauer in
     bpo-13777(3).)

   * New function *note sethostname(): a8c. allows the hostname to be
     set on unix systems if the calling process has sufficient
     privileges.  (Contributed by Ross Lagerwall in bpo-10866(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue6560

   (2) https://bugs.python.org/issue10141

   (3) https://bugs.python.org/issue13777

   (4) https://bugs.python.org/issue10866


File: python.info,  Node: socketserver<3>,  Next: sqlite3<5>,  Prev: socket<7>,  Up: Improved Modules<6>

1.6.20.47 socketserver
......................

*note BaseServer: a8e. now has an overridable method *note
service_actions(): a8f. that is called by the *note serve_forever():
a90. method in the service loop.  *note ForkingMixIn: 3da. now uses this
to clean up zombie child processes.  (Contributed by Justin Warkentin in
bpo-11109(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue11109


File: python.info,  Node: sqlite3<5>,  Next: ssl<8>,  Prev: socketserver<3>,  Up: Improved Modules<6>

1.6.20.48 sqlite3
.................

New *note sqlite3.Connection: 3dd. method *note set_trace_callback():
a92. 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/issue11688


File: python.info,  Node: ssl<8>,  Next: stat<2>,  Prev: sqlite3<5>,  Up: Improved Modules<6>

1.6.20.49 ssl
.............

   * The *note ssl: f4. module has two new random generation functions:

        * *note RAND_bytes(): a94.: generate cryptographically strong
          pseudo-random bytes.

        * *note RAND_pseudo_bytes(): a95.: generate pseudo-random bytes.

     (Contributed by Victor Stinner in bpo-12049(1).)

   * The *note ssl: f4. 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(): a96. 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(): a97. and *note
     set_ecdh_curve(): a98. methods.  (Contributed by Antoine Pitrou in
     bpo-13626(4) and bpo-13627(5).)

   * SSL sockets have a new *note get_channel_binding(): a99. 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(): a9a. method.  The new
     attribute *note OP_NO_COMPRESSION: a9b. 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(): a9c. method.
     (Contributed by Colin Marc in bpo-14204(8).)

   * SSL errors can now be introspected more easily thanks to *note
     library: a9d. and *note reason: a9e. attributes.  (Contributed by
     Antoine Pitrou in bpo-14837(9).)

   * The *note get_server_certificate(): a9f. function now supports
     IPv6.  (Contributed by Charles-François Natali in bpo-11811(10).)

   * New attribute *note OP_CIPHER_SERVER_PREFERENCE: aa0. 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/issue12049

   (2) https://bugs.python.org/issue11183

   (3) https://bugs.python.org/issue12803

   (4) https://bugs.python.org/issue13626

   (5) https://bugs.python.org/issue13627

   (6) https://bugs.python.org/issue12551

   (7) https://bugs.python.org/issue13634

   (8) https://bugs.python.org/issue14204

   (9) https://bugs.python.org/issue14837

   (10) https://bugs.python.org/issue11811

   (11) https://bugs.python.org/issue13635


File: python.info,  Node: stat<2>,  Next: struct<3>,  Prev: ssl<8>,  Up: Improved Modules<6>

1.6.20.50 stat
..............

The undocumented tarfile.filemode function has been moved to *note
stat.filemode(): aa2.  It can be used to convert a file’s mode to a
string of the form ’-rwxrwxrwx’.

(Contributed by Giampaolo Rodolà in bpo-14807(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14807


File: python.info,  Node: struct<3>,  Next: subprocess<5>,  Prev: stat<2>,  Up: Improved Modules<6>

1.6.20.51 struct
................

The *note struct: f9. 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/issue3163


File: python.info,  Node: subprocess<5>,  Next: sys<7>,  Prev: struct<3>,  Up: Improved Modules<6>

1.6.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: aa5. allows suppressing output in a
platform-independent fashion.  (Contributed by Ross Lagerwall in
bpo-5870(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue8513

   (2) https://bugs.python.org/issue5870


File: python.info,  Node: sys<7>,  Next: tarfile<4>,  Prev: subprocess<5>,  Up: Improved Modules<6>

1.6.20.53 sys
.............

The *note sys: fe. module has a new *note thread_info: aa7. *note named
tuple: aa8. holding information about the thread implementation
(bpo-11223(1)).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue11223


File: python.info,  Node: tarfile<4>,  Next: tempfile,  Prev: sys<7>,  Up: Improved Modules<6>

1.6.20.54 tarfile
.................

*note tarfile: 102. now supports ‘lzma’ encoding via the *note lzma: ae.
module.  (Contributed by Lars Gustäbel in bpo-5689(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue5689


File: python.info,  Node: tempfile,  Next: textwrap<2>,  Prev: tarfile<4>,  Up: Improved Modules<6>

1.6.20.55 tempfile
..................

*note tempfile.SpooledTemporaryFile: aab.’s ‘truncate()’ method now
accepts a ‘size’ parameter.  (Contributed by Ryan Kelly in bpo-9957(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue9957


File: python.info,  Node: textwrap<2>,  Next: threading<5>,  Prev: tempfile,  Up: Improved Modules<6>

1.6.20.56 textwrap
..................

The *note textwrap: 109. module has a new *note indent(): aad. 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/issue13857


File: python.info,  Node: threading<5>,  Next: time<5>,  Prev: textwrap<2>,  Up: Improved Modules<6>

1.6.20.57 threading
...................

*note threading.Condition: aaf, *note threading.Semaphore: ab0, *note
threading.BoundedSemaphore: ab1, *note threading.Event: ab2, and *note
threading.Timer: ab3, 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: 236. 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(): ab4.  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/issue10968

   (2) https://bugs.python.org/issue6064


File: python.info,  Node: time<5>,  Next: types<4>,  Prev: threading<5>,  Up: Improved Modules<6>

1.6.20.58 time
..............

The PEP 418(1) added new functions to the *note time: 10b. module:

   * *note get_clock_info(): ab6.: Get information on a clock.

   * *note monotonic(): 774.: Monotonic clock (cannot go backward), not
     affected by system clock updates.

   * *note perf_counter(): 2ab.: Performance counter with the highest
     available resolution to measure a short duration.

   * *note process_time(): 2ac.: Sum of the system and user CPU time of
     the current process.

Other new functions:

   * *note clock_getres(): ab7, *note clock_gettime(): ab8. and *note
     clock_settime(): ab9. functions with ‘CLOCK_xxx’ constants.
     (Contributed by Victor Stinner in bpo-10278(2).)

To improve cross platform consistency, *note sleep(): 685. now raises a
*note ValueError: 1fc. when passed a negative sleep value.  Previously
this was an error on posix, but produced an infinite sleep on Windows.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0418

   (2) https://bugs.python.org/issue10278


File: python.info,  Node: types<4>,  Next: unittest<5>,  Prev: time<5>,  Up: Improved Modules<6>

1.6.20.59 types
...............

Add a new *note types.MappingProxyType: abb. class: Read-only proxy of a
mapping.  (bpo-14386(1))

The new functions *note types.new_class(): abc. and *note
types.prepare_class(): abd. provide support for PEP 3115(2) compliant
dynamic type creation.  (bpo-14588(3))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14386

   (2) https://www.python.org/dev/peps/pep-3115

   (3) https://bugs.python.org/issue14588


File: python.info,  Node: unittest<5>,  Next: urllib<3>,  Prev: types<4>,  Up: Improved Modules<6>

1.6.20.60 unittest
..................

*note assertRaises(): abf, *note assertRaisesRegex(): ac0, *note
assertWarns(): ac1, and *note assertWarnsRegex(): ac2. 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(): ac3. now returns the *note TestResult:
ac4. object.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10775


File: python.info,  Node: urllib<3>,  Next: webbrowser,  Prev: unittest<5>,  Up: Improved Modules<6>

1.6.20.61 urllib
................

The *note Request: 8fb. class, now accepts a `method' argument used by
*note get_method(): ac6. 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/issue1673007


File: python.info,  Node: webbrowser,  Next: xml etree ElementTree,  Prev: urllib<3>,  Up: Improved Modules<6>

1.6.20.62 webbrowser
....................

The *note webbrowser: 12a. 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/issue13620

   (2) https://bugs.python.org/issue14493


File: python.info,  Node: xml etree ElementTree,  Next: zlib<2>,  Prev: webbrowser,  Up: Improved Modules<6>

1.6.20.63 xml.etree.ElementTree
...............................

The *note xml.etree.ElementTree: 138. 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: ac9. 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,  Up: Improved Modules<6>

1.6.20.64 zlib
..............

New attribute *note zlib.Decompress.eof: acb. 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: acc. 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/issue12646

   (2) https://bugs.python.org/issue12306


File: python.info,  Node: Optimizations<5>,  Next: Build and C API Changes<4>,  Prev: Improved Modules<6>,  Up: What's New In Python 3 3

1.6.21 Optimizations
--------------------

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.

     (Contributed by Serhiy Storchaka, bpo-14624(2), bpo-14738(3) and
     bpo-15026(4).)

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0393

   (2) https://bugs.python.org/issue14624

   (3) https://bugs.python.org/issue14738

   (4) https://bugs.python.org/issue15026


File: python.info,  Node: Build and C API Changes<4>,  Next: Deprecated<5>,  Prev: Optimizations<5>,  Up: What's New In Python 3 3

1.6.22 Build and C API Changes
------------------------------

Changes to Python’s build process and to the C API include:

   * New PEP 3118(1) related function:

        * *note PyMemoryView_FromMemory(): ace.

   * PEP 393(2) added new Unicode types, macros and functions:

        * High-level API:

             * *note PyUnicode_CopyCharacters(): acf.

             * *note PyUnicode_FindChar(): 445.

             * *note PyUnicode_GetLength(): ad0, *note
               PyUnicode_GET_LENGTH: ad1.

             * *note PyUnicode_New(): ad2.

             * *note PyUnicode_Substring(): ad3.

             * *note PyUnicode_ReadChar(): ad4, *note
               PyUnicode_WriteChar(): ad5.

        * Low-level API:

             * *note Py_UCS1: ad6, *note Py_UCS2: ad7, *note Py_UCS4:
               ad8. types

             * *note PyASCIIObject: ad9. and *note
               PyCompactUnicodeObject: ada. structures

             * *note PyUnicode_READY: adb.

             * *note PyUnicode_FromKindAndData(): adc.

             * *note PyUnicode_AsUCS4(): add, *note
               PyUnicode_AsUCS4Copy(): ade.

             * *note PyUnicode_DATA: adf, *note PyUnicode_1BYTE_DATA:
               ae0, *note PyUnicode_2BYTE_DATA: ae1, *note
               PyUnicode_4BYTE_DATA: ae2.

             * *note PyUnicode_KIND: ae3. with ‘PyUnicode_Kind’ enum:
               *note PyUnicode_WCHAR_KIND: ae4, *note
               PyUnicode_1BYTE_KIND: ae5, *note PyUnicode_2BYTE_KIND:
               ae6, *note PyUnicode_4BYTE_KIND: ae7.

             * *note PyUnicode_READ: ae8, *note PyUnicode_READ_CHAR:
               ae9, *note PyUnicode_WRITE: aea.

             * *note PyUnicode_MAX_CHAR_VALUE: aeb.

   * *note PyArg_ParseTuple: 26b. now accepts a *note bytearray: 337.
     for the ‘c’ format (bpo-12380(3)).

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3118

   (2) https://www.python.org/dev/peps/pep-0393

   (3) https://bugs.python.org/issue12380


File: python.info,  Node: Deprecated<5>,  Next: Porting to Python 3 3,  Prev: Build and C API Changes<4>,  Up: What's New In Python 3 3

1.6.23 Deprecated
-----------------

* Menu:

* Unsupported Operating Systems: Unsupported Operating Systems<2>.
* Deprecated Python modules, functions and methods: Deprecated Python modules functions and methods<4>.
* Deprecated functions and types of the C API: Deprecated functions and types of the C API<3>.
* Deprecated features::


File: python.info,  Node: Unsupported Operating Systems<2>,  Next: Deprecated Python modules functions and methods<4>,  Up: Deprecated<5>

1.6.23.1 Unsupported Operating Systems
......................................

OS/2 and VMS are no longer supported due to the lack of a maintainer.

Windows 2000 and Windows platforms which set ‘COMSPEC’ to ‘command.com’
are no longer supported due to maintenance burden.

OSF support, which was deprecated in 3.2, has been completely removed.


File: python.info,  Node: Deprecated Python modules functions and methods<4>,  Next: Deprecated functions and types of the C API<3>,  Prev: Unsupported Operating Systems<2>,  Up: Deprecated<5>

1.6.23.2 Deprecated Python modules, functions and methods
.........................................................

   * Passing a non-empty string to ‘object.__format__()’ is deprecated,
     and will produce a *note TypeError: 193. 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(): a0b. and *note ftplib.FTP.dir(): a0c.: use
     *note ftplib.FTP.mlsd(): a0a.

   * ‘platform.popen()’: use the *note subprocess: fa. module.  Check
     especially the *note Replacing Older Functions with the subprocess
     Module: aef. section (bpo-11377(3)).

   * bpo-13374(4): The Windows bytes API has been deprecated in the
     *note os: c5. 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(): 2ab. or *note time.process_time():
     2ac. function instead, depending on your requirements, to have a
     well defined behaviour.

   * The ‘os.stat_float_times()’ function is deprecated.

   * *note abc: 4. module:

        * *note abc.abstractproperty: 9d2. has been deprecated, use
          *note property: 1d8. with *note abc.abstractmethod(): 9d3.
          instead.

        * *note abc.abstractclassmethod: 9d4. has been deprecated, use
          *note classmethod: 1d9. with *note abc.abstractmethod(): 9d3.
          instead.

        * *note abc.abstractstaticmethod: 9d5. has been deprecated, use
          *note staticmethod: 1da. with *note abc.abstractmethod(): 9d3.
          instead.

   * *note importlib: 9b. package:

        * *note importlib.abc.SourceLoader.path_mtime(): af0. is now
          deprecated in favour of *note
          importlib.abc.SourceLoader.path_stats(): af1. 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/issue9856

   (2) https://www.python.org/dev/peps/pep-0393

   (3) https://bugs.python.org/issue11377

   (4) https://bugs.python.org/issue13374

   (5) https://bugs.python.org/issue13988


File: python.info,  Node: Deprecated functions and types of the C API<3>,  Next: Deprecated features,  Prev: Deprecated Python modules functions and methods<4>,  Up: Deprecated<5>

1.6.23.3 Deprecated functions and types of the C API
....................................................

The *note Py_UNICODE: af3. has been deprecated by PEP 393(1) and will be
removed in Python 4.  All functions using this type are deprecated:

Unicode functions and methods using *note Py_UNICODE: af3. and *note
Py_UNICODE*: af3. types:

   * *note PyUnicode_FromUnicode: af4.: use *note
     PyUnicode_FromWideChar(): af5. or *note
     PyUnicode_FromKindAndData(): adc.

   * *note PyUnicode_AS_UNICODE: af6, *note PyUnicode_AsUnicode(): af7,
     *note PyUnicode_AsUnicodeAndSize(): af8.: use *note
     PyUnicode_AsWideCharString(): 43d.

   * *note PyUnicode_AS_DATA: af9.: use *note PyUnicode_DATA: adf. with
     *note PyUnicode_READ: ae8. and *note PyUnicode_WRITE: aea.

   * *note PyUnicode_GET_SIZE: afa, *note PyUnicode_GetSize(): afb.: use
     *note PyUnicode_GET_LENGTH: ad1. or *note PyUnicode_GetLength():
     ad0.

   * *note PyUnicode_GET_DATA_SIZE: afc.: use ‘PyUnicode_GET_LENGTH(str)
     * PyUnicode_KIND(str)’ (only work on ready strings)

   * *note PyUnicode_AsUnicodeCopy(): afd.: use *note
     PyUnicode_AsUCS4Copy(): ade. or *note PyUnicode_AsWideCharString():
     43d.

   * ‘PyUnicode_GetMax()’

Functions and macros manipulating Py_UNICODE* strings:

   * ‘Py_UNICODE_strlen’: use *note PyUnicode_GetLength(): ad0. or *note
     PyUnicode_GET_LENGTH: ad1.

   * ‘Py_UNICODE_strcat’: use *note PyUnicode_CopyCharacters(): acf. or
     *note PyUnicode_FromFormat(): 7d0.

   * ‘Py_UNICODE_strcpy’, ‘Py_UNICODE_strncpy’, ‘Py_UNICODE_COPY’: use
     *note PyUnicode_CopyCharacters(): acf. or *note
     PyUnicode_Substring(): ad3.

   * ‘Py_UNICODE_strcmp’: use *note PyUnicode_Compare(): afe.

   * ‘Py_UNICODE_strncmp’: use *note PyUnicode_Tailmatch(): aff.

   * ‘Py_UNICODE_strchr’, ‘Py_UNICODE_strrchr’: use *note
     PyUnicode_FindChar(): 445.

   * ‘Py_UNICODE_FILL’: use *note PyUnicode_Fill(): b00.

   * ‘Py_UNICODE_MATCH’

Encoders:

   * *note PyUnicode_Encode(): b01.: use ‘PyUnicode_AsEncodedObject()’

   * *note PyUnicode_EncodeUTF7(): b02.

   * *note PyUnicode_EncodeUTF8(): b03.: use *note PyUnicode_AsUTF8():
     430. or *note PyUnicode_AsUTF8String(): b04.

   * *note PyUnicode_EncodeUTF32(): b05.

   * *note PyUnicode_EncodeUTF16(): b06.

   * *note PyUnicode_EncodeUnicodeEscape(): b07. use *note
     PyUnicode_AsUnicodeEscapeString(): b08.

   * *note PyUnicode_EncodeRawUnicodeEscape(): b09. use *note
     PyUnicode_AsRawUnicodeEscapeString(): b0a.

   * *note PyUnicode_EncodeLatin1(): b0b.: use *note
     PyUnicode_AsLatin1String(): b0c.

   * *note PyUnicode_EncodeASCII(): b0d.: use *note
     PyUnicode_AsASCIIString(): b0e.

   * *note PyUnicode_EncodeCharmap(): b0f.

   * *note PyUnicode_TranslateCharmap(): b10.

   * *note PyUnicode_EncodeMBCS(): b11.: use *note
     PyUnicode_AsMBCSString(): b12. or *note PyUnicode_EncodeCodePage():
     b13. (with ‘CP_ACP’ code_page)

   * ‘PyUnicode_EncodeDecimal()’, *note
     PyUnicode_TransformDecimalToASCII(): b14.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0393


File: python.info,  Node: Deprecated features,  Prev: Deprecated functions and types of the C API<3>,  Up: Deprecated<5>

1.6.23.4 Deprecated features
............................

The *note array: 7. module’s ‘'u'’ format code is now deprecated and
will be removed in Python 4 together with the rest of the (*note
Py_UNICODE: af3.) API.


File: python.info,  Node: Porting to Python 3 3,  Prev: Deprecated<5>,  Up: What's New In Python 3 3

1.6.24 Porting to Python 3.3
----------------------------

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

* Menu:

* Porting Python code::
* Porting C code::
* Building C extensions::
* Command Line Switch Changes::


File: python.info,  Node: Porting Python code,  Next: Porting C code,  Up: Porting to Python 3 3

1.6.24.1 Porting Python code
............................

   * Hash randomization is enabled by default.  Set the *note
     PYTHONHASHSEED: 9ca. environment variable to ‘0’ to disable hash
     randomization.  See also the *note object.__hash__(): 345. 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: 10b. and *note datetime:
     31.: *note OverflowError: 965. is now raised instead of *note
     ValueError: 1fc. if a timestamp is out of range.  *note OSError:
     1d4. 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(): 4a1. to clear out the cache for the
     finders to notice the new file.

   * *note ImportError: 339. 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__(): 615. 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(): b18. rather than call *note
     __import__(): 615. directly.

   * *note __import__(): 615. 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: 5eb. and *note sys.path_hooks: 961.
     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:
     4a2, 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' *note imp.NullImporter: 9c0. 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: 4a2. where it represents the use of
     implicit finders, but semantically it should not change anything.

   * *note importlib.abc.Finder: 9ba. 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: 9b7.

   * *note pkgutil: ce. has been converted to use *note importlib: 9b.
     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(): b19. and *note pkgutil.walk_packages():
     490. 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(): 9fe. 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(): b1a. 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(): b1b. may now raise protocol errors like
     all other ‘poplib’ methods.  Code that assumes ‘quit’ does not
     raise *note poplib.error_proto: b1c. errors may need to be changed
     if errors on ‘quit’ are encountered by a particular application
     (bpo-11291(8)).

   * The ‘strict’ argument to *note email.parser.Parser: b1d, deprecated
     since Python 2.4, has finally been removed.

   * The deprecated method ‘unittest.TestCase.assertSameElements’ has
     been removed.

   * The deprecated variable ‘time.accept2dyear’ has been removed.

   * The deprecated ‘Context._clamp’ attribute has been removed from the
     *note decimal: 36. 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: ee, since its functionality has long
     been provided directly by *note socket.socket.makefile(): b1e.

   * Passing a negative value to *note time.sleep(): 685. 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: b1f. to make the decision.

   * Code that used to work around the fact that the *note threading:
     10a. 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/issue12326

   (2) https://bugs.python.org/issue13847

   (3) https://bugs.python.org/issue14180

   (4) https://www.python.org/dev/peps/pep-0328

   (5) https://www.python.org/dev/peps/pep-0302

   (6) https://bugs.python.org/issue1079

   (7) https://bugs.python.org/issue1690608

   (8) https://bugs.python.org/issue11291

   (9) https://bugs.python.org/issue8540

   (10) https://bugs.python.org/issue13550


File: python.info,  Node: Porting C code,  Next: Building C extensions,  Prev: Porting Python code,  Up: Porting to Python 3 3

1.6.24.2 Porting C code
.......................

   * In the course of changes to the buffer API the undocumented
     ‘smalltable’ member of the *note Py_buffer: b20. 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: 981, the *note Py_UNICODE: af3. 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: b21.

     However, if you only have been using high-level functions such as
     *note PyUnicode_Concat(): b22, *note PyUnicode_Join(): b23. or
     *note PyUnicode_FromFormat(): 7d0, your code will automatically
     take advantage of the new unicode representations.

   * *note PyImport_GetMagicNumber(): b24. now returns ‘-1’ upon
     failure.

   * As a negative value for the `level' argument to *note __import__():
     615. is no longer valid, the same now holds for *note
     PyImport_ImportModuleLevel(): b25.  This also means that the value
     of `level' used by *note PyImport_ImportModuleEx(): b26. is now ‘0’
     instead of ‘-1’.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0393


File: python.info,  Node: Building C extensions,  Next: Command Line Switch Changes,  Prev: Porting C code,  Up: Porting to Python 3 3

1.6.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).

     (implemented in bpo-14040(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14040


File: python.info,  Node: Command Line Switch Changes,  Prev: Building C extensions,  Up: Porting to Python 3 3

1.6.24.4 Command Line Switch Changes
....................................

   * The -Q command-line flag and related artifacts have been removed.
     Code checking sys.flags.division_warning will need updating.

     (bpo-10998(1), contributed by Éric Araujo.)

   * When ‘python’ is started with *note -S: b29, ‘import site’ will no
     longer add site-specific paths to the module search paths.  In
     previous versions, it did.

     (bpo-11591(2), contributed by Carl Meyer with editions by Éric
     Araujo.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10998

   (2) https://bugs.python.org/issue11591


File: python.info,  Node: What's New In Python 3 2,  Next: What's New In Python 3 1,  Prev: What's New In Python 3 3,  Up: Python 有什麼新功能？

1.7 What’s New In Python 3.2
============================


Author: Raymond Hettinger

This article explains the new features in Python 3.2 as compared to 3.1.
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 Command Line Parsing Module: PEP 389 Argparse Command Line Parsing Module.
* PEP 391; Dictionary Based Configuration for Logging: PEP 391 Dictionary Based Configuration for Logging.
* PEP 3148; The concurrent.futures module: PEP 3148 The concurrent futures module.
* 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.
* Other Language Changes: Other Language Changes<7>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules.
* Multi-threading::
* Optimizations: Optimizations<6>.
* Unicode::
* Codecs::
* Documentation::
* IDLE::
* Code Repository::
* Build and C API Changes: Build and C API Changes<5>.
* Porting to Python 3.2: Porting to Python 3 2.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/blob/076ca6c3c8df3030307e548d9be792ce3c1c6eea/Misc/NEWS

   (2) https://www.python.org/dev/peps/pep-0392


File: python.info,  Node: PEP 384 Defining a Stable ABI,  Next: PEP 389 Argparse Command Line Parsing Module,  Up: What's New In Python 3 2

1.7.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) - Defining a Stable ABI

     PEP written by Martin von Löwis.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0384


File: python.info,  Node: PEP 389 Argparse Command Line Parsing Module,  Next: PEP 391 Dictionary Based Configuration for Logging,  Prev: PEP 384 Defining a Stable ABI,  Up: What's New In Python 3 2

1.7.2 PEP 389: Argparse Command Line Parsing Module
---------------------------------------------------

A new module for command line parsing, *note argparse: 6, was introduced
to overcome the limitations of *note optparse: c4. 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: 6. 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: 6. 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) - New Command Line Parsing Module

     PEP written by Steven Bethard.

*note Upgrading optparse code: b2e. for details on the differences from
*note optparse: c4.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0389


File: python.info,  Node: PEP 391 Dictionary Based Configuration for Logging,  Next: PEP 3148 The concurrent futures module,  Prev: PEP 389 Argparse Command Line Parsing Module,  Up: What's New In Python 3 2

1.7.3 PEP 391: Dictionary Based Configuration for Logging
---------------------------------------------------------

The *note logging: ab. 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 ‘ConfigParser’ 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(): b30. 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

     PEP written by Vinay Sajip.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0391


File: python.info,  Node: PEP 3148 The concurrent futures module,  Next: PEP 3147 PYC Repository Directories,  Prev: PEP 391 Dictionary Based Configuration for Logging,  Up: What's New In Python 3 2

1.7.4 PEP 3148: The ‘concurrent.futures’ module
-----------------------------------------------

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: 22. was inspired by the
`java.util.concurrent' package.  In that model, a running call and its
result are represented by a *note Future: b32. 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(): 2a4. for scheduling a callable and returning a *note Future:
b32. object; *note map(): 6c3. for scheduling many asynchronous calls at
a time, and *note shutdown(): b33. for freeing resources.  The class is
a *note context manager: 56d. and can be used in a *note with: 6ee.
statement to assure that resources are automatically released when
currently pending futures are done executing.

A simple of example of *note ThreadPoolExecutor: 27b. 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

     PEP written by Brian Quinlan.

*note Code for Threaded Parallel URL reads: b34, an example using
threads to fetch multiple web pages in parallel.

*note Code for computing prime numbers in parallel: b35, an example
demonstrating *note ProcessPoolExecutor: 2a5.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3148


File: python.info,  Node: PEP 3147 PYC Repository Directories,  Next: PEP 3149 ABI Version Tagged so Files,  Prev: PEP 3148 The concurrent futures module,  Up: What's New In Python 3 2

1.7.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__: b37. 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
     *note imp: 9a. 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 *note imp: 9a. 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: d8. and *note compileall: 21. 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: 9c. module has been updated with new *note
     abstract base classes: b38. 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

     PEP written by Barry Warsaw.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: What's New In Python 3 2

1.7.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: ff. 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

     PEP written by Barry Warsaw.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3149


File: python.info,  Node: PEP 3333 Python Web Server Gateway Interface v1 0 1,  Next: Other Language Changes<7>,  Prev: PEP 3149 ABI Version Tagged so Files,  Up: What's New In Python 3 2

1.7.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: 335. 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: 335. 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: 12d. module has a
new function, *note wsgiref.handlers.read_environ(): b3b. for
transcoding CGI variables from *note os.environ: b3c. into native
strings and returning a new dictionary.

也參考
......

PEP 3333(3) - Python Web Server Gateway Interface v1.0.1

     PEP written by Phillip Eby.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2616.html

   (2) https://tools.ietf.org/html/rfc2047.html

   (3) https://www.python.org/dev/peps/pep-3333


File: python.info,  Node: Other Language Changes<7>,  Next: New Improved and Deprecated Modules,  Prev: PEP 3333 Python Web Server Gateway Interface v1 0 1,  Up: What's New In Python 3 2

1.7.8 Other Language Changes
----------------------------

Some smaller changes made to the core Python language are:

   * String formatting for *note format(): 4e0. and *note str.format():
     4df. 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(): 6b6. method that
     extends the capabilities of the existing *note str.format(): 4df.
     method by accepting arbitrary *note mapping: b3e. objects.  This
     new method makes it possible to use string formatting with any of
     Python’s many dictionary-like objects such as *note defaultdict:
     b3f, *note Shelf: 8b5, *note ConfigParser: 4af, or *note dbm: 32.
     It is also useful with custom *note dict: 1b9. subclasses that
     normalize keys before look-up or that supply a *note __missing__():
     b40. 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: b41. 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)

     (Contributed by Marcin Wojdyr in bpo-1772833(3)).

   * The *note hasattr(): 44c. function works by calling *note
     getattr(): 44d. and detecting whether an exception is raised.  This
     technique allows it to detect methods created dynamically by *note
     __getattr__(): 31f. or *note __getattribute__(): 44e. 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:
     3a0. 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(): 335. of a float or complex number is now the same
     as its *note repr(): 7d1.  Previously, the *note str(): 335. form
     was shorter but that just caused confusion and is no longer needed
     now that the shortest possible *note repr(): 7d1. 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: 25d. objects now have a *note release(): b42.
     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:
     b43. clause is cleared, so this code which used to work with Python
     2.6, raised a *note SyntaxError: 45d. 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

     (See bpo-4617(7).)

   * The internal ‘structsequence’ tool now creates subclasses of tuple.
     This means that C structures like those returned by *note
     os.stat(): 1f2, *note time.gmtime(): b44, and *note
     sys.version_info: b1f. now work like a *note named tuple: aa8. 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:
     41d. 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: 4d5, 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: 127. module, or on the command line.

     A *note ResourceWarning: 4d5. is issued at interpreter shutdown if
     the *note gc.garbage: b45. list isn’t empty, and if *note
     gc.DEBUG_UNCOLLECTABLE: b46. 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: 4d5. is also issued when a *note file
     object: b47. 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: 9c3. objects now support `index' and `count' methods.
     This is part of an effort to make more objects fully implement the
     ‘collections.Sequence’ *note abstract base class: b38.  As a
     result, the language will have a more uniform API. In addition,
     *note range: 9c3. objects now support slicing and negative indices,
     even with values larger than *note sys.maxsize: b48.  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)

     (Contributed by Daniel Stutzbach in bpo-9213(12), by Alexander
     Belopolsky in bpo-2690(13), and by Nick Coghlan in bpo-10889(14).)

   * The *note callable(): b49. builtin function from Py2.x was
     resurrected.  It provides a concise, readable alternative to using
     an *note abstract base class: b38. in an expression like
     ‘isinstance(x, collections.Callable)’:

          >>> callable(max)
          True
          >>> callable(20)
          False

     (See 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/issue7094

   (2) https://bugs.python.org/issue6081

   (3) https://bugs.python.org/issue1772833

   (4) https://bugs.python.org/issue9666

   (5) https://bugs.python.org/issue9337

   (6) https://bugs.python.org/issue9757

   (7) https://bugs.python.org/issue4617

   (8) https://bugs.python.org/issue8413

   (9) https://bugs.python.org/issue7301

   (10) https://bugs.python.org/issue10093

   (11) https://bugs.python.org/issue477863

   (12) https://bugs.python.org/issue9213

   (13) https://bugs.python.org/issue2690

   (14) https://bugs.python.org/issue10889

   (15) https://bugs.python.org/issue10518

   (16) https://bugs.python.org/issue9425


File: python.info,  Node: New Improved and Deprecated Modules,  Next: Multi-threading,  Prev: Other Language Changes<7>,  Up: What's New In Python 3 2

1.7.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: 69. package,
*note mailbox: af. module, and *note nntplib: c1. 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: 56d. to
support convenient and reliable resource clean-up using a *note with:
6ee. statement.

* Menu:

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


File: python.info,  Node: email<5>,  Next: elementtree,  Up: New Improved and Deprecated Modules

1.7.9.1 email
.............

The usability of the *note email: 69. 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: 336. rather than *note str: 335. 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(): b4c. and *note
     message_from_binary_file(): b4d, and new classes *note
     BytesFeedParser: b4e. and *note BytesParser: b4f. allow binary
     message data to be parsed into model objects.

   * Given bytes input to the model, *note get_payload(): b50. 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: b51. 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: b52. 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: ee. *note SMTP: a86. class now accepts a byte
     string for the `msg' argument to the *note sendmail(): 749. method,
     and a new method, *note send_message(): 74a. accepts a *note
     Message: 546. 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://tools.ietf.org/html/rfc2047.html

   (2) https://bugs.python.org/issue4661

   (3) https://bugs.python.org/issue10321


File: python.info,  Node: elementtree,  Next: functools<6>,  Prev: email<5>,  Up: New Improved and Deprecated Modules

1.7.9.2 elementtree
...................

The *note xml.etree.ElementTree: 138. 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(): b54. which builds an
     XML document from a sequence of fragments

   * *note xml.etree.ElementTree.register_namespace(): b55. for
     registering a global namespace prefix

   * *note xml.etree.ElementTree.tostringlist(): 91b. for string
     representation including all sublists

   * *note xml.etree.ElementTree.Element.extend(): b56. for appending a
     sequence of zero or more elements

   * *note xml.etree.ElementTree.Element.iterfind(): b57. searches an
     element and subelements

   * *note xml.etree.ElementTree.Element.itertext(): b58. creates a text
     iterator over an element and its subelements

   * *note xml.etree.ElementTree.TreeBuilder.end(): b59. closes the
     current element

   * *note xml.etree.ElementTree.TreeBuilder.doctype(): 2c2. handles a
     doctype declaration

Two methods have been deprecated:

   * ‘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.

(Contributed by Florent Xicluna and Fredrik Lundh, bpo-6472(2).)

   ---------- Footnotes ----------

   (1) http://effbot.org/zone/elementtree-13-intro.htm

   (2) https://bugs.python.org/issue6472


File: python.info,  Node: functools<6>,  Next: itertools<4>,  Prev: elementtree,  Up: New Improved and Deprecated Modules

1.7.9.3 functools
.................

   * The *note functools: 85. module includes a new decorator for
     caching function calls.  *note functools.lru_cache(): 1c8. 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(): 86f. decorator now adds a
     ‘__wrapped__’ attribute pointing to the original callable function.
     This allows wrapped functions to be introspected.  It also copies
     ‘__annotations__’ if defined.  And now it also gracefully skips
     over missing attributes such as ‘__doc__’ 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(): 850. will use existing equality
     and inequality methods to fill in the remaining methods.

     For example, supplying `__eq__' and `__lt__' will enable *note
     total_ordering(): 850. 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.

     (Contributed by Raymond Hettinger.)

   * To aid in porting programs from Python 2, the *note
     functools.cmp_to_key(): b5b. function converts an old-style
     comparison function to modern *note key function: 6e5.:

          >>> # 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.

     (Contributed by Raymond Hettinger.)

   ---------- Footnotes ----------

   (1) https://code.activestate.com/recipes/498245

   (2) https://code.activestate.com/recipes/577479

   (3) https://bugs.python.org/issue10586

   (4) https://bugs.python.org/issue10593

   (5) https://bugs.python.org/issue9567

   (6) https://bugs.python.org/issue3445

   (7) https://bugs.python.org/issue8814

   (8) https://wiki.python.org/moin/HowTo/Sorting/


File: python.info,  Node: itertools<4>,  Next: collections<8>,  Prev: functools<6>,  Up: New Improved and Deprecated Modules

1.7.9.4 itertools
.................

   * The *note itertools: a4. module has a new *note accumulate(): 1de.
     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(): 1de, see the *note
     examples for the random module: b5d.

     (Contributed by Raymond Hettinger and incorporating design
     suggestions from Mark Dickinson.)


File: python.info,  Node: collections<8>,  Next: threading<6>,  Prev: itertools<4>,  Up: New Improved and Deprecated Modules

1.7.9.5 collections
...................

   * The *note collections.Counter: 9df. class now has two forms of
     in-place subtraction, the existing `-=' operator for saturating
     subtraction(1) and the new *note subtract(): b5f. 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})

     (Contributed by Raymond Hettinger.)

   * The *note collections.OrderedDict: 1ba. class has a new method
     *note move_to_end(): b60. 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']

     (Contributed by Raymond Hettinger.)

   * The *note collections.deque: 536. class grew two new methods *note
     count(): b61. and *note reverse(): b62. that make them more
     substitutable for *note list: 263. 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'])

     (Contributed by Raymond Hettinger.)

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Saturation_arithmetic

   (2) https://en.wikipedia.org/wiki/Multiset


File: python.info,  Node: threading<6>,  Next: datetime and time,  Prev: collections<8>,  Up: New Improved and Deprecated Modules

1.7.9.6 threading
.................

The *note threading: 10a. module has a new *note Barrier: b64.
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: b64. 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(): b65, 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: b66.
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'.

(Contributed by Kristján Valur Jónsson with an API review by Jeffrey
Yasskin in bpo-8777(4).)

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Synchronous_rendezvous

   (2) 
http://osl.cs.illinois.edu/media/papers/karmani-2009-barrier_synchronization_pattern.pdf

   (3) https://greenteapress.com/semaphores/LittleBookOfSemaphores.pdf

   (4) https://bugs.python.org/issue8777


File: python.info,  Node: datetime and time,  Next: math<6>,  Prev: threading<6>,  Up: New Improved and Deprecated Modules

1.7.9.7 datetime and time
.........................

   * The *note datetime: 31. module has a new type *note timezone: a06.
     that implements the *note tzinfo: 385. 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: 196. objects can now be multiplied by *note
     float: 188. and divided by *note float: 188. and *note int: 185.
     objects.  And *note timedelta: 196. objects can now divide one
     another.

   * The *note datetime.date.strftime(): 53d. 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: 279.  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(): b68.
     function will accept any year that fits in a C int, while the *note
     time.mktime(): b69. and *note time.strftime(): b6a. functions will
     accept the full range supported by the corresponding operating
     system functions.

(Contributed by Alexander Belopolsky and Victor Stinner in
bpo-1289118(1), bpo-5094(2), bpo-6641(3), bpo-2706(4), bpo-1777412(5),
bpo-8013(6), and bpo-10827(7).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue1289118

   (2) https://bugs.python.org/issue5094

   (3) https://bugs.python.org/issue6641

   (4) https://bugs.python.org/issue2706

   (5) https://bugs.python.org/issue1777412

   (6) https://bugs.python.org/issue8013

   (7) https://bugs.python.org/issue10827


File: python.info,  Node: math<6>,  Next: abc<3>,  Prev: datetime and time,  Up: New Improved and Deprecated Modules

1.7.9.8 math
............

The *note math: b2. module has been updated with six new functions
inspired by the C99 standard.

The *note isfinite(): b6c. 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(): b6d. 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(): 457. function computes a probability integral or
Gaussian error function(1).  The complementary error function, *note
erfc(): 458, 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(): b6e. 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():
b6f. 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

(Contributed by Mark Dickinson.)

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Error_function


File: python.info,  Node: abc<3>,  Next: io<5>,  Prev: math<6>,  Up: New Improved and Deprecated Modules

1.7.9.9 abc
...........

The *note abc: 4. module now supports *note abstractclassmethod(): 9d4.
and *note abstractstaticmethod(): 9d5.

These tools make it possible to define an *note abstract base class:
b38. that requires a particular *note classmethod(): 1d9. or *note
staticmethod(): 1da. 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/issue5867


File: python.info,  Node: io<5>,  Next: reprlib,  Prev: abc<3>,  Up: New Improved and Deprecated Modules

1.7.9.10 io
...........

The *note io.BytesIO: 7a0. has a new method, *note getbuffer(): b72,
which provides functionality similar to *note memoryview(): 25d.  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'

(Contributed by Antoine Pitrou in bpo-5506(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue5506


File: python.info,  Node: reprlib,  Next: logging<7>,  Prev: io<5>,  Up: New Improved and Deprecated Modules

1.7.9.11 reprlib
................

When writing a *note __repr__(): 343. 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: 263. and
*note set: b74. handle self-reference by displaying "..."  in the
recursive part of the representation string.

To help write such *note __repr__(): 343. methods, the *note reprlib:
e0. module has a new decorator, *note recursive_repr(): b75, for
detecting recursive calls to *note __repr__(): 343. 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'>

(Contributed by Raymond Hettinger in bpo-9826(1) and bpo-9840(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue9826

   (2) https://bugs.python.org/issue9840


File: python.info,  Node: logging<7>,  Next: csv<3>,  Prev: reprlib,  Up: New Improved and Deprecated Modules

1.7.9.12 logging
................

In addition to dictionary-based configuration described above, the *note
logging: ab. package has many other improvements.

The logging documentation has been augmented by a *note basic tutorial:
b77, an *note advanced tutorial: b78, and a *note cookbook: b79. of
logging recipes.  These documents are the fastest way to learn about
logging.

The *note logging.basicConfig(): 1e1. 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(): 4df. style, or can be set to "$" for the
shell-style formatting provided by *note string.Template: 3f0.  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: b7a. directed
to *note sys.stderr: 314. 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 ‘logging.raiseExceptions’.  The new default handler is stored
in *note logging.lastResort: b7b.

The use of filters has been simplified.  Instead of creating a *note
Filter: b7c. 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<3>,  Next: contextlib<6>,  Prev: logging<7>,  Up: New Improved and Deprecated Modules

1.7.9.13 csv
............

The *note csv: 2a. module now supports a new dialect, *note
unix_dialect: b7e, 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: b7f. has a new method, *note writeheader():
b80. 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/issue5975

   (2) https://bugs.python.org/issue1537721


File: python.info,  Node: contextlib<6>,  Next: decimal and fractions,  Prev: csv<3>,  Up: New Improved and Deprecated Modules

1.7.9.14 contextlib
...................

There is a new and slightly mind-blowing tool *note ContextDecorator:
b82. that is helpful for creating a *note context manager: 56d. that
does double duty as a function decorator.

As a convenience, this new functionality is used by *note
contextmanager(): b83. 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: 6ee. 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(): b83. 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: 6ee. 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.

(Contributed by Michael Foord in bpo-9110(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue9110


File: python.info,  Node: decimal and fractions,  Next: ftp,  Prev: contextlib<6>,  Up: New Improved and Deprecated Modules

1.7.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: 926, 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 inter-operability 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: 189. constructor now accepts *note
     float: 188. objects directly so there in no longer a need to use
     the *note from_float(): b85. method (bpo-8257(2)).

   * Mixed type comparisons are now fully supported so that *note
     Decimal: 189. objects can be directly compared with *note float:
     188. and *note fractions.Fraction: 186. (bpo-2531(3) and
     bpo-8188(4)).

Similar changes were made to *note fractions.Fraction: 186. so that the
*note from_float(): b86. and *note from_decimal(): b87. 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: 36. 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)).

(Contributed by Mark Dickinson and Raymond Hettinger.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue8188

   (2) https://bugs.python.org/issue8257

   (3) https://bugs.python.org/issue2531

   (4) https://bugs.python.org/issue8188

   (5) https://bugs.python.org/issue8294

   (6) https://bugs.python.org/issue8540


File: python.info,  Node: ftp,  Next: popen,  Prev: decimal and fractions,  Up: New Improved and Deprecated Modules

1.7.9.16 ftp
............

The *note ftplib.FTP: 2f1. class now supports the context management
protocol to unconditionally consume *note socket.error: 99a. 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: 1ed. and *note
fileinput.input(): 2ae. also grew auto-closing context managers:

     with fileinput.input(files=('log1.txt', 'log2.txt')) as f:
         for line in f:
             process(line)

(Contributed by Tarek Ziadé and Giampaolo Rodolà in bpo-4972(1), and by
Georg Brandl in bpo-8046(2) and bpo-1286(3).)

The *note FTP_TLS: a08. class now accepts a `context' parameter, which
is a *note ssl.SSLContext: 3e9. object allowing bundling SSL
configuration options, certificates and private keys into a single
(potentially long-lived) structure.

(Contributed by Giampaolo Rodolà; bpo-8806(4).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue4972

   (2) https://bugs.python.org/issue8046

   (3) https://bugs.python.org/issue1286

   (4) https://bugs.python.org/issue8806


File: python.info,  Node: popen,  Next: select<3>,  Prev: ftp,  Up: New Improved and Deprecated Modules

1.7.9.17 popen
..............

The *note os.popen(): 2aa. and *note subprocess.Popen(): 2ba. functions
now support *note with: 6ee. statements for auto-closing of the file
descriptors.

(Contributed by Antoine Pitrou and Brian Curtin in bpo-7461(1) and
bpo-10554(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue7461

   (2) https://bugs.python.org/issue10554


File: python.info,  Node: select<3>,  Next: gzip and zipfile,  Prev: popen,  Up: New Improved and Deprecated Modules

1.7.9.18 select
...............

The *note select: e6. module now exposes a new, constant attribute,
*note PIPE_BUF: b8b, which gives the minimum number of bytes which are
guaranteed not to block when *note select.select(): 678. 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/issue9862


File: python.info,  Node: gzip and zipfile,  Next: tarfile<5>,  Prev: select<3>,  Up: New Improved and Deprecated Modules

1.7.9.19 gzip and zipfile
.........................

*note gzip.GzipFile: 6e2. now implements the *note io.BufferedIOBase:
58d. *note abstract base class: b38. (except for ‘truncate()’).  It also
has a *note peek(): b8d. method and supports unseekable as well as
zero-padded file objects.

The *note gzip: 8c. module also gains the *note compress(): 1d2. and
*note decompress(): b8e. functions for easier in-memory compression and
decompression.  Keep in mind that text needs to be encoded as *note
bytes: 336. 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'

(Contributed by Anand B. Pillai in bpo-3488(1); and by Antoine Pitrou,
Nir Aides and Brian Curtin in bpo-9962(2), bpo-1675951(3), bpo-7471(4)
and bpo-2846(5).)

Also, the ‘zipfile.ZipExtFile’ 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:
b8f. 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/issue3488

   (2) https://bugs.python.org/issue9962

   (3) https://bugs.python.org/issue1675951

   (4) https://bugs.python.org/issue7471

   (5) https://bugs.python.org/issue2846

   (6) https://bugs.python.org/issue7610


File: python.info,  Node: tarfile<5>,  Next: hashlib<3>,  Prev: gzip and zipfile,  Up: New Improved and Deprecated Modules

1.7.9.20 tarfile
................

The *note TarFile: b91. class can now be used as a context manager.  In
addition, its *note add(): 481. 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: 5c9.  The user-supplied
filter function accepts a *note TarInfo: b92. object and returns an
updated *note TarInfo: b92. 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

(Proposed by Tarek Ziadé and implemented by Lars Gustäbel in
bpo-6856(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue6856


File: python.info,  Node: hashlib<3>,  Next: ast<3>,  Prev: tarfile<5>,  Up: New Improved and Deprecated Modules

1.7.9.21 hashlib
................

The *note hashlib: 8d. 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'}

(Suggested by Carl Chenet in bpo-7418(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue7418


File: python.info,  Node: ast<3>,  Next: os<8>,  Prev: hashlib<3>,  Up: New Improved and Deprecated Modules

1.7.9.22 ast
............

The *note ast: 8. module has a wonderful a general-purpose tool for
safely evaluating expression strings using the Python literal syntax.
The *note ast.literal_eval(): 4aa. function serves as a secure
alternative to the builtin *note eval(): b95. function which is easily
abused.  Python 3.2 adds *note bytes: 336. and *note set: b74. 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>

(Implemented by Benjamin Peterson and Georg Brandl.)


File: python.info,  Node: os<8>,  Next: shutil<5>,  Prev: ast<3>,  Up: New Improved and Deprecated Modules

1.7.9.23 os
...........

Different operating systems use various encodings for filenames and
environment variables.  The *note os: c5. module provides two new
functions, *note fsencode(): 4f4. and *note fsdecode(): 4f3, 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: b97. constant
will be true.

For direct access to encoded environment variables (if available), use
the new *note os.getenvb(): b98. function or use *note os.environb: b99.
which is a bytes version of *note os.environ: b3c.

(Contributed by Victor Stinner.)


File: python.info,  Node: shutil<5>,  Next: sqlite3<6>,  Prev: os<8>,  Up: New Improved and Deprecated Modules

1.7.9.24 shutil
...............

The *note shutil.copytree(): 21b. 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(): 25b. is used by default.

(Contributed by Tarek Ziadé.)

In addition, the *note shutil: ea. module now supports *note archiving
operations: b9b. 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(): 21c. and *note
unpack_archive(): b9c.  By default, both operate on the current
directory (which can be set by *note os.chdir(): a44.) 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'
     ... )

(Contributed by Tarek Ziadé.)


File: python.info,  Node: sqlite3<6>,  Next: html<3>,  Prev: shutil<5>,  Up: New Improved and Deprecated Modules

1.7.9.25 sqlite3
................

The *note sqlite3: f3. 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(): b9e. and
     *note sqlite3.Connection.load_extension(): b9f. methods allows you
     to load SQLite extensions from ".so" files.  One well-known
     extension is the fulltext-search extension distributed with SQLite.

(Contributed by R. David Murray and Shashwat Anand; bpo-8845(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue8845


File: python.info,  Node: html<3>,  Next: socket<8>,  Prev: sqlite3<6>,  Up: New Improved and Deprecated Modules

1.7.9.26 html
.............

A new *note html: 90. module was introduced with only a single function,
*note escape(): 939, 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<8>,  Next: ssl<9>,  Prev: html<3>,  Up: New Improved and Deprecated Modules

1.7.9.27 socket
...............

The *note socket: f0. module has two new improvements.

   * Socket objects now have a *note detach(): ba2. 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(): ba3. now supports the context
     management protocol to unconditionally consume *note socket.error:
     99a. exceptions and to close the socket when done.  (Contributed by
     Giampaolo Rodolà; bpo-9794(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue8524

   (2) https://bugs.python.org/issue9794


File: python.info,  Node: ssl<9>,  Next: nntp,  Prev: socket<8>,  Up: New Improved and Deprecated Modules

1.7.9.28 ssl
............

The *note ssl: f4. module added a number of features to satisfy common
requirements for secure (encrypted, authenticated) internet connections:

   * A new class, *note SSLContext: 3e9, 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(): 3ea. for creating an SSL socket from an SSL context.

   * A new function, *note ssl.match_hostname(): 3e1, 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(): 474. 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: f4.
     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(): 3ea.

   * Various options have been added to the *note ssl: f4. module, such
     as *note OP_NO_SSLv2: ba5. 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: ba6. (a string), *note
     ssl.OPENSSL_VERSION_INFO: ba7. (a 5-tuple), and *note
     ssl.OPENSSL_VERSION_NUMBER: ba8. (an integer).

(Contributed by Antoine Pitrou in bpo-8850(3), bpo-1589(4), bpo-8322(5),
bpo-5639(6), bpo-4870(7), bpo-8484(8), and bpo-8321(9).)

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2818.html

   (2) 
https://www.openssl.org/docs/manmaster/man1/ciphers.html#CIPHER-LIST-FORMAT

   (3) https://bugs.python.org/issue8850

   (4) https://bugs.python.org/issue1589

   (5) https://bugs.python.org/issue8322

   (6) https://bugs.python.org/issue5639

   (7) https://bugs.python.org/issue4870

   (8) https://bugs.python.org/issue8484

   (9) https://bugs.python.org/issue8321


File: python.info,  Node: nntp,  Next: certificates,  Prev: ssl<9>,  Up: New Improved and Deprecated Modules

1.7.9.29 nntp
.............

The *note nntplib: c1. 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 *note
nntplib.NNTP_SSL: baa.) and explicit (using *note
nntplib.NNTP.starttls(): bab.) TLS has also been added.

(Contributed by Antoine Pitrou in bpo-9360(1) and Andrew Vant in
bpo-1926(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue9360

   (2) https://bugs.python.org/issue1926


File: python.info,  Node: certificates,  Next: imaplib<3>,  Prev: nntp,  Up: New Improved and Deprecated Modules

1.7.9.30 certificates
.....................

*note http.client.HTTPSConnection: 398, *note
urllib.request.HTTPSHandler: bad. and *note urllib.request.urlopen():
791. 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/issue9003


File: python.info,  Node: imaplib<3>,  Next: http client<4>,  Prev: certificates,  Up: New Improved and Deprecated Modules

1.7.9.31 imaplib
................

Support for explicit TLS on standard IMAP4 connections has been added
through the new *note imaplib.IMAP4.starttls: baf. method.

(Contributed by Lorenzo M. Catucci and Antoine Pitrou, bpo-4471(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue4471


File: python.info,  Node: http client<4>,  Next: unittest<6>,  Prev: imaplib<3>,  Up: New Improved and Deprecated Modules

1.7.9.32 http.client
....................

There were a number of small API improvements in the *note http.client:
94. 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: 397. and *note HTTPSConnection: 398. 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: 398.

The *note request(): 554. method on connection objects allowed an
optional `body' argument so that a *note file object: b47. could be used
to supply the content of the request.  Conveniently, the `body' argument
now also accepts an *note iterable: bb1. 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(): bb2. method that sets the host and port for HTTP
Connect tunneling.

To match the behavior of *note http.server: 97, 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/issue10980


File: python.info,  Node: unittest<6>,  Next: random<2>,  Prev: http client<4>,  Up: New Improved and Deprecated Modules

1.7.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

     (Contributed by Michael Foord.)

   * Experimentation at the interactive prompt is now easier because the
     ‘unittest.case.TestCase’ class can now be instantiated without
     arguments:

          >>> from unittest import TestCase
          >>> TestCase().assertEqual(pow(2, 3), 8)

     (Contributed by Michael Foord.)

   * The *note unittest: 11c. module has two new methods, *note
     assertWarns(): ac1. and *note assertWarnsRegex(): ac2. to verify
     that a given warning type is triggered by the code under test:

          with self.assertWarns(DeprecationWarning):
              legacy_function('XYZ')

     (Contributed by Antoine Pitrou, bpo-9754(2).)

     Another new method, *note assertCountEqual(): bb4. 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')

     (Contributed by 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: bb5. 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(): bb6. is the new name for
     ‘assertRegexpMatches()’ which was misnamed because the test uses
     *note re.search(): bb7, not *note re.match(): bb8.  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: de. module, and it has unambiguous camel-casing.

     (Contributed by Raymond Hettinger and implemented by Ezio Melotti.)

   * To improve consistency, some long-standing method aliases are being
     deprecated in favor of the preferred names:

          Old Name                            Preferred Name
                                              
          -----------------------------------------------------------------------
                                              
          ‘assert_()’                         *note assertTrue(): bb9.
                                              
                                              
          ‘assertEquals()’                    *note assertEqual(): bba.
                                              
                                              
          ‘assertNotEquals()’                 *note assertNotEqual(): bbb.
                                              
                                              
          ‘assertAlmostEquals()’              *note assertAlmostEqual(): bbc.
                                              
                                              
          ‘assertNotAlmostEquals()’           *note assertNotAlmostEqual(): bbd.
                                              

     Likewise, the ‘TestCase.fail*’ methods deprecated in Python 3.1 are
     expected to be removed in Python 3.3.  Also see the *note
     Deprecated aliases: bbe. section in the *note unittest: 11c.
     documentation.

     (Contributed by 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.

     (Contributed by Raymond Hettinger.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10620

   (2) https://bugs.python.org/issue9754

   (3) https://bugs.python.org/issue9424


File: python.info,  Node: random<2>,  Next: poplib<3>,  Prev: unittest<6>,  Up: New Improved and Deprecated Modules

1.7.9.34 random
...............

The integer methods in the *note random: dd. 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(): bc0, *note randint(): bc1, *note choice(): bc2, *note
shuffle(): bc3. and *note sample(): bc4.

(Contributed by Raymond Hettinger; bpo-9025(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue9025


File: python.info,  Node: poplib<3>,  Next: asyncore<2>,  Prev: random<2>,  Up: New Improved and Deprecated Modules

1.7.9.35 poplib
...............

*note POP3_SSL: bc6. class now accepts a `context' parameter, which is a
*note ssl.SSLContext: 3e9. object allowing bundling SSL configuration
options, certificates and private keys into a single (potentially
long-lived) structure.

(Contributed by Giampaolo Rodolà; bpo-8807(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue8807


File: python.info,  Node: asyncore<2>,  Next: tempfile<2>,  Prev: poplib<3>,  Up: New Improved and Deprecated Modules

1.7.9.36 asyncore
.................

*note asyncore.dispatcher: bc8. now provides a *note handle_accepted():
bc9. 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 *note
handle_accept(): bca. and avoids the user to call *note accept(): bcb.
directly.

(Contributed by Giampaolo Rodolà; bpo-6706(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue6706


File: python.info,  Node: tempfile<2>,  Next: inspect<6>,  Prev: asyncore<2>,  Up: New Improved and Deprecated Modules

1.7.9.37 tempfile
.................

The *note tempfile: 104. module has a new context manager, *note
TemporaryDirectory: bcd. which provides easy deterministic cleanup of
temporary directories:

     with tempfile.TemporaryDirectory() as tmpdirname:
         print('created temporary dir:', tmpdirname)

(Contributed by Neil Schemenauer and Nick Coghlan; bpo-5178(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue5178


File: python.info,  Node: inspect<6>,  Next: pydoc<5>,  Prev: tempfile<2>,  Up: New Improved and Deprecated Modules

1.7.9.38 inspect
................

   * The *note inspect: a1. module has a new function *note
     getgeneratorstate(): bcf. 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'

     (Contributed by Rodolpho Eckhardt and Nick Coghlan, bpo-10220(1).)

   * To support lookups without the possibility of activating a dynamic
     attribute, the *note inspect: a1. module has a new function, *note
     getattr_static(): bd0.  Unlike *note hasattr(): 44c, 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>

     (Contributed by Michael Foord.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10220


File: python.info,  Node: pydoc<5>,  Next: dis<3>,  Prev: inspect<6>,  Up: New Improved and Deprecated Modules

1.7.9.39 pydoc
..............

The *note pydoc: da. 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

(Contributed by Ron Adam; bpo-2001(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue2001


File: python.info,  Node: dis<3>,  Next: dbm<6>,  Prev: pydoc<5>,  Up: New Improved and Deprecated Modules

1.7.9.40 dis
............

The *note dis: 38. module gained two new functions for inspecting code,
*note code_info(): bd3. and *note show_code(): 837.  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(): 389. 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.

(Contributed by Nick Coghlan in bpo-9147(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue9147


File: python.info,  Node: dbm<6>,  Next: ctypes<2>,  Prev: dis<3>,  Up: New Improved and Deprecated Modules

1.7.9.41 dbm
............

All database modules now support the ‘get()’ and ‘setdefault()’ methods.

(Suggested by Ray Allen in bpo-9523(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue9523


File: python.info,  Node: ctypes<2>,  Next: site<2>,  Prev: dbm<6>,  Up: New Improved and Deprecated Modules

1.7.9.42 ctypes
...............

A new type, *note ctypes.c_ssize_t: bd6. represents the C ‘ssize_t’
datatype.


File: python.info,  Node: site<2>,  Next: sysconfig<2>,  Prev: ctypes<2>,  Up: New Improved and Deprecated Modules

1.7.9.43 site
.............

The *note site: ec. module has three new functions useful for reporting
on the details of a given Python installation.

   * *note getsitepackages(): bd8. lists all global site-packages
     directories.

   * *note getuserbase(): bd9. reports on the user’s base directory
     where data can be stored.

   * *note getusersitepackages(): bda. 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

(Contributed by Tarek Ziadé in bpo-6693(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue6693


File: python.info,  Node: sysconfig<2>,  Next: pdb<5>,  Prev: site<2>,  Up: New Improved and Deprecated Modules

1.7.9.44 sysconfig
..................

The new *note sysconfig: ff. 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(): bdc. returning values like `linux-i586' or
     `macosx-10.6-ppc'.

   * *note get_python_version(): bdd. 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 *note distutils: 39.  Those include
`posix_prefix', `posix_home', `posix_user', `nt', `nt_user', `os2',
`os2_home':

   * *note get_paths(): bde. makes a dictionary containing installation
     paths for the current installation scheme.

   * *note get_config_vars(): 96a. 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<5>,  Next: configparser<2>,  Prev: sysconfig<2>,  Up: New Improved and Deprecated Modules

1.7.9.45 pdb
............

The *note pdb: ca. 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.

   * The ‘Pdb’ class constructor now accepts a `nosigint' argument.

   * 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.

(Contributed by Georg Brandl, Antonio Cuni and Ilya Sandler.)


File: python.info,  Node: configparser<2>,  Next: urllib parse<3>,  Prev: pdb<5>,  Up: New Improved and Deprecated Modules

1.7.9.46 configparser
.....................

The *note configparser: 23. 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: 4af.  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: be1.:

     >>> 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<3>,  Next: mailbox,  Prev: configparser<2>,  Up: New Improved and Deprecated Modules

1.7.9.47 urllib.parse
.....................

A number of usability improvements were made for the *note urllib.parse:
120. module.

The *note urlparse(): 5ff. 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(): be3. function now returns a *note named tuple:
aa8.:

     >>> 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(): 790. 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(): be4. 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: be5, all the *note
urllib.parse: 120. 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://tools.ietf.org/html/rfc2732.html

   (3) https://bugs.python.org/issue2987

   (4) https://bugs.python.org/issue5468

   (5) https://bugs.python.org/issue9873


File: python.info,  Node: mailbox,  Next: turtledemo,  Prev: urllib parse<3>,  Up: New Improved and Deprecated Modules

1.7.9.48 mailbox
................

Thanks to a concerted effort by R. David Murray, the *note mailbox: af.
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: 336. because various parts of a
message may have different encodings.

The solution harnessed the *note email: 69. package’s binary support for
parsing arbitrary email messages.  In addition, the solution required a
number of API changes.

As expected, the *note add(): be7. method for *note mailbox.Mailbox:
be8. objects now accepts binary input.

*note StringIO: 832. 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(): be9.
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(): bea. method that returns a *note bytes: 336. 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(): beb. method, but that approach is not very useful.
Instead, it is best to extract messages from a *note Message: bec.
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/issue9124


File: python.info,  Node: turtledemo,  Prev: mailbox,  Up: New Improved and Deprecated Modules

1.7.9.49 turtledemo
...................

The demonstration code for the *note turtle: 117. 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: 48d, 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/issue10199


File: python.info,  Node: Multi-threading,  Next: Optimizations<6>,  Prev: New Improved and Deprecated Modules,  Up: What's New In Python 3 2

1.7.10 Multi-threading
----------------------

   * The mechanism for serializing execution of concurrently running
     Python threads (generally known as the *note GIL: bef. 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(): bf0.
     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).

     (Contributed by Antoine Pitrou.)

   * Regular and recursive locks now accept an optional `timeout'
     argument to their *note acquire(): 771. method.  (Contributed by
     Antoine Pitrou; bpo-7316(2).)

   * Similarly, *note threading.Semaphore.acquire(): bf1. 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/issue7316

   (3) https://bugs.python.org/issue850728

   (4) https://bugs.python.org/issue8844


File: python.info,  Node: Optimizations<6>,  Next: Unicode,  Prev: Multi-threading,  Up: What's New In Python 3 2

1.7.11 Optimizations
--------------------

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: b74. as a *note frozenset: bf3.
     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: cb.
     module is now several times faster.

     (Contributed by Alexandre Vassalotti, Antoine Pitrou and the
     Unladen Swallow team in bpo-9410(2) and bpo-3873(3).)

   * The Timsort algorithm(4) used in *note list.sort(): 44a. and *note
     sorted(): 449. now runs faster and uses less memory when called
     with a *note key function: 6e5.  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.

     (Contributed by Antoine Pitrou in bpo-7451(6) and by Raymond
     Hettinger and Antoine Pitrou in bpo-10314(7).)

   * Recursive locks (created with the *note threading.RLock(): bf4.
     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.

     (Contributed by Antoine Pitrou; bpo-3001(8).)

   * The fast-search algorithm in stringlib is now used by the
     ‘split()’, ‘rsplit()’, ‘splitlines()’ and ‘replace()’ methods on
     *note bytes: 336, *note bytearray: 337. and *note str: 335.
     objects.  Likewise, the algorithm is also used by ‘rfind()’,
     ‘rindex()’, ‘rsplit()’ and ‘rpartition()’.

     (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
‘BaseHTTPRequestHandler’ has more efficient buffering (bpo-3709(14) by
Andrew Schaaf).  The *note operator.attrgetter(): 720. function has been
sped-up (bpo-10160(15) by Christos Georgiou).  And ‘ConfigParser’ loads
multi-line arguments a bit faster (bpo-7113(16) by Łukasz Langa).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue6690

   (2) https://bugs.python.org/issue9410

   (3) https://bugs.python.org/issue3873

   (4) https://en.wikipedia.org/wiki/Timsort

   (5) https://bugs.python.org/issue9915

   (6) https://bugs.python.org/issue7451

   (7) https://bugs.python.org/issue10314

   (8) https://bugs.python.org/issue3001

   (9) https://bugs.python.org/issue7622

   (10) https://bugs.python.org/issue7462

   (11) https://bugs.python.org/issue6713

   (12) https://bugs.python.org/issue8685

   (13) https://bugs.python.org/issue1569291

   (14) https://bugs.python.org/issue3709

   (15) https://bugs.python.org/issue10160

   (16) https://bugs.python.org/issue7113


File: python.info,  Node: Unicode,  Next: Codecs,  Prev: Optimizations<6>,  Up: What's New In Python 3 2

1.7.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) http://unicode.org/versions/Unicode6.0.0/

   (2) https://en.wikipedia.org/wiki/Emoji

   (3) http://www.unicode.org/versions/Unicode6.0.0/#Database_Changes


File: python.info,  Node: Codecs,  Next: Documentation,  Prev: Unicode,  Up: What's New In Python 3 2

1.7.13 Codecs
-------------

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: 1fe. when it
encounters an undecodable byte sequence and an *note UnicodeEncodeError:
1fd. 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: 102. uses ‘'utf-8'’ encoding on Windows
(instead of ‘'mbcs'’) and the ‘'surrogateescape'’ error handler on all
operating systems.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue1616979


File: python.info,  Node: Documentation,  Next: IDLE,  Prev: Codecs,  Up: What's New In Python 3 2

1.7.14 Documentation
--------------------

The documentation continues to be improved.

   * A table of quick links has been added to the top of lengthy
     sections such as *note 內建函式: bf8.  In the case of *note
     itertools: a4, 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: 85. 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: de. module has an extensive section, *note Regular
     Expression Examples: bf9.  Likewise, the *note itertools: a4.
     module continues to be updated with new *note Itertools Recipes:
     bfa.

   * The *note datetime: 31. module now has an auxiliary implementation
     in pure Python.  No functionality was changed.  This just provides
     an easier-to-read alternate implementation.

     (Contributed by Alexander Belopolsky in 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.

     (Contributed by Georg Brandl in bpo-7962(4).)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/functools.py

   (2) 
https://rhettinger.wordpress.com/2011/01/28/open-your-source-more/

   (3) https://bugs.python.org/issue9528

   (4) https://bugs.python.org/issue7962


File: python.info,  Node: IDLE,  Next: Code Repository,  Prev: Documentation,  Up: What's New In Python 3 2

1.7.15 IDLE
-----------

   * The format menu now has an option to clean source files by
     stripping trailing whitespace.

     (Contributed by Raymond Hettinger; bpo-5150(1).)

   * IDLE on Mac OS X now works with both Carbon AquaTk and Cocoa
     AquaTk.

     (Contributed by Kevin Walzer, Ned Deily, and Ronald Oussoren;
     bpo-6075(2).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue5150

   (2) https://bugs.python.org/issue6075


File: python.info,  Node: Code Repository,  Next: Build and C API Changes<5>,  Prev: IDLE,  Up: What's New In Python 3 2

1.7.16 Code Repository
----------------------

In addition to the existing Subversion code repository at
‘http://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://www.python.org/dev/peps/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<5>,  Next: Porting to Python 3 2,  Prev: Code Repository,  Up: What's New In Python 3 2

1.7.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(): bfe. now returns the correct value for large
     code points, and *note repr(): 7d1. 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’.

     (Contributed by Antoine Pitrou; bpo-9203(3).)

   * The option ‘--with-wctype-functions’ was removed.  The built-in
     unicode database is now used for all functions.

     (Contributed by Amaury Forgeot D’Arc; bpo-9210(4).)

   * Hash values are now values of a new type, ‘Py_hash_t’, 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: b74. and *note
     dict: 1b9. 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).

     (Suggested by Raymond Hettinger and implemented by 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 *note PySys_SetArgvEx(): bff. allows an
     embedded interpreter to set *note sys.argv: c00. without also
     modifying *note sys.path: 48d. (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(): c01.
     which is analogous to *note PyLong_AsLongAndOverflow(): c02.  They
     both serve to convert Python *note int: 185. into a native
     fixed-width type while providing detection of cases where the
     conversion won’t fit (bpo-7767(9)).

   * The *note PyUnicode_CompareWithASCIIString(): c03. function now
     returns `not equal' if the Python string is `NUL' terminated.

   * There is a new function *note PyErr_NewExceptionWithDoc(): c04.
     that is like *note PyErr_NewException(): c05. 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/issue10679

   (2) https://bugs.python.org/issue5127

   (3) https://bugs.python.org/issue9203

   (4) https://bugs.python.org/issue9210

   (5) https://bugs.python.org/issue9778

   (6) https://bugs.python.org/issue2443

   (7) https://bugs.python.org/issue5753

   (8) https://bugs.python.org/issue8276

   (9) https://bugs.python.org/issue7767

   (10) https://bugs.python.org/issue7033

   (11) https://bugs.python.org/issue2422

   (12) https://bugs.python.org/issue8837

   (13) https://github.com/python/cpython/tree/3.8/Misc/NEWS

   (14) 
https://github.com/python/cpython/tree/3.8/Mac/BuildScript/README.txt

   (15) https://www.activestate.com/activetcl/downloads


File: python.info,  Node: Porting to Python 3 2,  Prev: Build and C API Changes<5>,  Up: What's New In Python 3 2

1.7.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: 23. 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(): c07.
          and *note set(): c08. 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(): c08. and *note add_section(): c09. 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: c0a. or *note
          DuplicateOptionError: c0b.  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 *note nntplib: c1. module was reworked extensively, meaning
     that its APIs are often incompatible with the 3.1 APIs.

   * *note bytearray: 337. objects can no longer be used as filenames;
     instead, they should be converted to *note bytes: 336.

   * The ‘array.tostring()’ and ‘array.fromstring()’ have been renamed
     to ‘array.tobytes()’ and ‘array.frombytes()’ 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: c0c. 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(): c0d. 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():
     c0e. and *note bytearray.maketrans(): c0f.  This change solves the
     confusion around which types were supported by the *note string:
     f7. module.  Now, *note str: 335, *note bytes: 336, and *note
     bytearray: 337. each have their own `maketrans' and `translate'
     methods with intermediate translation tables of the appropriate
     type.

     (Contributed by Georg Brandl; bpo-5675(2).)

   * The previously deprecated ‘contextlib.nested()’ function has been
     removed in favor of a plain *note with: 6ee. 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)

     (Contributed by Georg Brandl and Mattias Brändström; appspot issue
     53094(3).)

   * *note struct.pack(): c10. 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: 138. class now raises an *note
     xml.etree.ElementTree.ParseError: c11. when a parse fails.
     Previously it raised an *note xml.parsers.expat.ExpatError: c12.

   * The new, longer *note str(): 335. value on floats may break
     doctests which rely on the old output format.

   * In *note subprocess.Popen: 2ba, 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: 121. and *note http.client: 94.  Such support is
     still present on the server side (in *note http.server: 97.).

     (Contributed by Antoine Pitrou, bpo-10711(5).)

   * SSL sockets in timeout mode now raise *note socket.timeout: c13.
     when a timeout occurs, rather than a generic *note SSLError: c14.

     (Contributed by Antoine Pitrou, bpo-10272(6).)

   * The misleading functions *note PyEval_AcquireLock(): 2b3. and *note
     PyEval_ReleaseLock(): c15. have been officially deprecated.  The
     thread-state aware APIs (such as *note PyEval_SaveThread(): c16.
     and *note PyEval_RestoreThread(): 2b5.) 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.

     (Contributed by Giampaolo Rodola in bpo-6706(7).)

   * Due to the new *note GIL: bef. implementation, *note
     PyEval_InitThreads(): c17. cannot be called before *note
     Py_Initialize(): 43e. anymore.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue8990

   (2) https://bugs.python.org/issue5675

   (3) https://codereview.appspot.com/53094

   (4) https://bugs.python.org/issue10783

   (5) https://bugs.python.org/issue10711

   (6) https://bugs.python.org/issue10272

   (7) https://bugs.python.org/issue6706


File: python.info,  Node: What's New In Python 3 1,  Next: What's New In Python 3 0,  Prev: What's New In Python 3 2,  Up: Python 有什麼新功能？

1.8 What’s New In Python 3.1
============================


Author: Raymond Hettinger

This article explains the new features in Python 3.1, compared to 3.0.

* Menu:

* PEP 372; Ordered Dictionaries: PEP 372 Ordered Dictionaries.
* PEP 378; Format Specifier for Thousands Separator: PEP 378 Format Specifier for Thousands Separator.
* Other Language Changes: Other Language Changes<8>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules<2>.
* Optimizations: Optimizations<7>.
* IDLE: IDLE<2>.
* Build and C API Changes: Build and C API Changes<6>.
* Porting to Python 3.1: Porting to Python 3 1.


File: python.info,  Node: PEP 372 Ordered Dictionaries,  Next: PEP 378 Format Specifier for Thousands Separator,  Up: What's New In Python 3 1

1.8.1 PEP 372: Ordered Dictionaries
-----------------------------------

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: 1ba. 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: 23. 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(): 1b8. now returns an ordered dictionary with
the values appearing in the same order as the underlying tuple indices.
The *note json: a5. 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) - Ordered Dictionaries

     PEP written by Armin Ronacher and Raymond Hettinger.
     Implementation written by Raymond Hettinger.

   ---------- Footnotes ----------

   (1) http://pyyaml.org/

   (2) https://www.python.org/dev/peps/pep-0372


File: python.info,  Node: PEP 378 Format Specifier for Thousands Separator,  Next: Other Language Changes<8>,  Prev: PEP 372 Ordered Dictionaries,  Up: What's New In Python 3 1

1.8.2 PEP 378: Format Specifier for Thousands Separator
-------------------------------------------------------

The built-in *note format(): 4e0. function and the *note str.format():
4df. 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: 185, *note float: 188, *note complex:
18a. and *note decimal.Decimal: 189.

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://www.python.org/dev/peps/pep-0378


File: python.info,  Node: Other Language Changes<8>,  Next: New Improved and Deprecated Modules<2>,  Prev: PEP 378 Format Specifier for Thousands Separator,  Up: What's New In Python 3 1

1.8.3 Other Language Changes
----------------------------

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(): 185. 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

     (Contributed by Fredrik Johansson, Victor Stinner, Raymond
     Hettinger, and Mark Dickinson; bpo-3439(2).)

   * The fields in *note format(): 4e0. 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}'’.

     (Contributed by Eric Smith; bpo-5237(3).)

   * The ‘string.maketrans()’ function is deprecated and is replaced by
     new static methods, *note bytes.maketrans(): c0e. and *note
     bytearray.maketrans(): c0f.  This change solves the confusion
     around which types were supported by the *note string: f7. module.
     Now, *note str: 335, *note bytes: 336, and *note bytearray: 337.
     each have their own `maketrans' and `translate' methods with
     intermediate translation tables of the appropriate type.

     (Contributed by Georg Brandl; bpo-5675(4).)

   * The syntax of the *note with: 6ee. 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.

     (Contributed by Georg Brandl and Mattias Brändström; appspot issue
     53094(5).)

   * ‘round(x, n)’ now returns an integer if `x' is an integer.
     Previously it returned a float:

          >>> round(1123, -2)
          1100

     (Contributed by 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.

     (Contributed by Eric Smith and Mark Dickinson; bpo-1580(7))

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue1739468

   (2) https://bugs.python.org/issue3439

   (3) https://bugs.python.org/issue5237

   (4) https://bugs.python.org/issue5675

   (5) https://codereview.appspot.com/53094

   (6) https://bugs.python.org/issue4707

   (7) https://bugs.python.org/issue1580


File: python.info,  Node: New Improved and Deprecated Modules<2>,  Next: Optimizations<7>,  Prev: Other Language Changes<8>,  Up: What's New In Python 3 1

1.8.4 New, Improved, and Deprecated Modules
-------------------------------------------

   * Added a *note collections.Counter: 9df. 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})

     (Contributed by Raymond Hettinger; bpo-1696199(1).)

   * Added a new module, *note tkinter.ttk: 110. 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.

     (Contributed by Guilherme Polo; bpo-2983(2).)

   * The *note gzip.GzipFile: 6e2. and *note bz2.BZ2File: 936. classes
     now support the context management protocol:

          >>> # Automatically close file after writing
          >>> with gzip.GzipFile(filename, "wb") as f:
          ...     f.write(b"xxx")

     (Contributed by Antoine Pitrou.)

   * The *note decimal: 36. module now supports methods for creating a
     decimal object from a binary *note float: 188.  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.

     (Contributed by Raymond Hettinger and Mark Dickinson.)

   * The *note itertools: a4. module grew two new functions.  The *note
     itertools.combinations_with_replacement(): c1e. function is one of
     four for generating combinatorics including permutations and
     Cartesian products.  The *note itertools.compress(): c1f. function
     mimics its namesake from APL. Also, the existing *note
     itertools.count(): c20. function now has an optional `step'
     argument and can accept any type of counting sequence including
     *note fractions.Fraction: 186. and *note decimal.Decimal: 189.:

          >>> [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)]

     (Contributed by Raymond Hettinger.)

   * *note collections.namedtuple(): 1b8. 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)]

     (Contributed by Raymond Hettinger; bpo-1818(3).)

   * The *note re.sub(): 480, *note re.subn(): 739. and *note
     re.split(): 3cf. functions now accept a flags parameter.

     (Contributed by Gregory Smith.)

   * The *note logging: ab. module now implements a simple *note
     logging.NullHandler: c21. 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)

     (Contributed by Vinay Sajip; bpo-4384(4)).

   * The *note runpy: e3. 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.

     (Contributed by Andi Vajda; bpo-4195(5).)

   * The *note pdb: ca. module can now access and display source code
     loaded via *note zipimport: 144. (or any other conformant PEP
     302(6) loader).

     (Contributed by Alexander Belopolsky; bpo-4201(7).)

   * *note functools.partial: 7cd. objects can now be pickled.

     (Suggested by Antoine Pitrou and Jesse Noller.  Implemented by Jack
     Diederich; bpo-5228(8).)

   * Add *note pydoc: da. help topics for symbols so that ‘help('@')’
     works as expected in the interactive environment.

     (Contributed by David Laban; bpo-4739(9).)

   * The *note unittest: 11c. 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: 6ee. statement:

          def test_division_by_zero(self):
              with self.assertRaises(ZeroDivisionError):
                  x / 0

     In addition, several new assertion methods were added including
     ‘assertSetEqual()’, ‘assertDictEqual()’,
     ‘assertDictContainsSubset()’, ‘assertListEqual()’,
     ‘assertTupleEqual()’, ‘assertSequenceEqual()’,
     ‘assertRaisesRegexp()’, ‘assertIsNone()’, and ‘assertIsNotNone()’.

     (Contributed by Benjamin Peterson and Antoine Pitrou.)

   * The *note io: a2. module has three new constants for the ‘seek()’
     method ‘SEEK_SET’, ‘SEEK_CUR’, and ‘SEEK_END’.

   * The *note sys.version_info: b1f. tuple is now a named tuple:

          >>> sys.version_info
          sys.version_info(major=3, minor=1, micro=0, releaselevel='alpha', serial=2)

     (Contributed by Ross Light; bpo-4285(10).)

   * The *note nntplib: c1. and *note imaplib: 98. modules now support
     IPv6.

     (Contributed by Derek Morr; bpo-1655(11) and bpo-1664(12).)

   * The *note pickle: cb. 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.

     (Contributed by Alexandre Vassalotti and Antoine Pitrou,
     bpo-6137(13).)

   * A new module, *note importlib: 9b. was added.  It provides a
     complete, portable, pure Python reference implementation of the
     *note import: c22. statement and its counterpart, the *note
     __import__(): 615. function.  It represents a substantial step
     forward in documenting and defining the actions that take place
     during imports.

     (Contributed by Brett Cannon.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue1696199

   (2) https://bugs.python.org/issue2983

   (3) https://bugs.python.org/issue1818

   (4) https://bugs.python.org/issue4384

   (5) https://bugs.python.org/issue4195

   (6) https://www.python.org/dev/peps/pep-0302

   (7) https://bugs.python.org/issue4201

   (8) https://bugs.python.org/issue5228

   (9) https://bugs.python.org/issue4739

   (10) https://bugs.python.org/issue4285

   (11) https://bugs.python.org/issue1655

   (12) https://bugs.python.org/issue1664

   (13) https://bugs.python.org/issue6137


File: python.info,  Node: Optimizations<7>,  Next: IDLE<2>,  Prev: New Improved and Deprecated Modules<2>,  Up: What's New In Python 3 1

1.8.5 Optimizations
-------------------

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.

     (Contributed by Amaury Forgeot d’Arc and 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.

     (Contributed by 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.

     (Contributed by Antoine Pitrou along with a number of other
     participants, bpo-4753(3)).

   * The decoding of UTF-8, UTF-16 and LATIN-1 is now two to four times
     faster.

     (Contributed by Antoine Pitrou and Amaury Forgeot d’Arc,
     bpo-4868(4).)

   * The *note json: a5. 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: 335, not with *note bytes: 336.
     That change makes the module closely match the JSON
     specification(5) which is defined in terms of Unicode.

     (Contributed by Bob Ippolito and converted to Py3.1 by Antoine
     Pitrou and Benjamin Peterson; bpo-4136(6).)

   * Unpickling now interns the attribute names of pickled objects.
     This saves memory and allows pickles to be smaller.

     (Contributed by Jake McGuire and Antoine Pitrou; bpo-5084(7).)

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3116

   (2) https://bugs.python.org/issue4688

   (3) https://bugs.python.org/issue4753

   (4) https://bugs.python.org/issue4868

   (5) http://json.org/

   (6) https://bugs.python.org/issue4136

   (7) https://bugs.python.org/issue5084


File: python.info,  Node: IDLE<2>,  Next: Build and C API Changes<6>,  Prev: Optimizations<7>,  Up: What's New In Python 3 1

1.8.6 IDLE
----------

   * IDLE’s format menu now provides an option to strip trailing
     whitespace from a source file.

     (Contributed by Roger D. Serwy; bpo-5150(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue5150


File: python.info,  Node: Build and C API Changes<6>,  Next: Porting to Python 3 1,  Prev: IDLE<2>,  Up: What's New In Python 3 1

1.8.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: c26. 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)

     (Contributed by Mark Dickinson; bpo-4258(1).)

   * The *note PyLong_AsUnsignedLongLong(): c27. function now handles a
     negative `pylong' by raising *note OverflowError: 965. instead of
     *note TypeError: 193.

     (Contributed by Mark Dickinson and Lisandro Dalcrin; bpo-5175(2).)

   * Deprecated ‘PyNumber_Int()’.  Use *note PyNumber_Long(): 26d.
     instead.

     (Contributed by Mark Dickinson; bpo-4910(3).)

   * Added a new *note PyOS_string_to_double(): c28. function to replace
     the deprecated functions ‘PyOS_ascii_strtod()’ and
     ‘PyOS_ascii_atof()’.

     (Contributed by Mark Dickinson; bpo-5914(4).)

   * Added *note PyCapsule: c0c. 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.

     (Contributed by Larry Hastings; bpo-5630(5).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue4258

   (2) https://bugs.python.org/issue5175

   (3) https://bugs.python.org/issue4910

   (4) https://bugs.python.org/issue5914

   (5) https://bugs.python.org/issue5630


File: python.info,  Node: Porting to Python 3 1,  Prev: Build and C API Changes<6>,  Up: What's New In Python 3 1

1.8.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: What's New In Python 3 0,  Next: What's New in Python 2 7,  Prev: What's New In Python 3 1,  Up: Python 有什麼新功能？

1.9 What’s New In Python 3.0
============================


Author: 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.  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::
* Overview Of Syntax Changes::
* Changes Already Present In Python 2.6: Changes Already Present In Python 2 6.
* Library Changes::
* 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<7>.
* Performance::
* Porting To Python 3.0: Porting To Python 3 0.


File: python.info,  Node: Common Stumbling Blocks,  Next: Overview Of Syntax Changes,  Up: What's New In Python 3 0

1.9.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::
* Integers::
* 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.9.1.1 Print Is A Function
...........................

The ‘print’ statement has been replaced with a *note print(): 88b.
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(): 88b. 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(): 88b.
     function calls, so this is mostly a non-issue for larger projects.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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.9.1.2 Views And Iterators Instead Of Lists
............................................

Some well-known APIs no longer return lists:

   * *note dict: 1b9. methods *note dict.keys(): c2f, *note
     dict.items(): c30. and *note dict.values(): c31. 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(): c32. and *note filter(): c33. 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(): c32. in *note list():
     263, e.g.  ‘list(map(...))’, but a better fix is often to use a
     list comprehension (especially when the original code uses *note
     lambda: c34.), or rewriting the code so it doesn’t need a list at
     all.  Particularly tricky is *note map(): c32. invoked for the side
     effects of the function; the correct transformation is to use a
     regular *note for: c35. loop (since creating a list would just be
     wasteful).

     If the input sequences are not of equal length, *note map(): c32.
     will stop at the termination of the shortest of the sequences.  For
     full compatibility with *note map(): c32. from Python 2.x, also
     wrap the sequences in *note itertools.zip_longest(): c36, e.g.
     ‘map(func, *sequences)’ becomes ‘list(map(func,
     itertools.zip_longest(*sequences)))’.

   * *note range(): 9c3. now behaves like ‘xrange()’ used to behave,
     except it works with values of arbitrary size.  The latter no
     longer exists.

   * *note zip(): c37. now returns an iterator.


File: python.info,  Node: Ordering Comparisons,  Next: Integers,  Prev: Views And Iterators Instead Of Lists,  Up: Common Stumbling Blocks

1.9.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: 193. 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(): 44a. 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 *note __lt__(): c39.
     for sorting, *note __eq__(): 344. with *note __hash__(): 345, 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: Integers,  Next: Text Vs Data Instead Of Unicode Vs 8-bit,  Prev: Ordering Comparisons,  Up: Common Stumbling Blocks

1.9.1.4 Integers
................

   * PEP 237(1): Essentially, ‘long’ renamed to *note int: 185.  That
     is, there is only one built-in integral type, named *note int:
     185.; 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: b48.
     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(): 7d1. 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():
     335. instead.)

   * Octal literals are no longer of the form ‘0720’; use ‘0o720’
     instead.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0237

   (2) https://www.python.org/dev/peps/pep-0238


File: python.info,  Node: Text Vs Data Instead Of Unicode Vs 8-bit,  Prev: Integers,  Up: Common Stumbling Blocks

1.9.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: 335, the type used to hold data is *note
     bytes: 336.  The biggest difference with the 2.x situation is that
     any attempt to mix text and data in Python 3.0 raises *note
     TypeError: 193, 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: 1fe. 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: 335. 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: 335. and *note bytes: 336. types cannot be mixed,
     you must always explicitly convert between them.  Use *note
     str.encode(): c3c. to go from *note str: 335. to *note bytes: 336,
     and *note bytes.decode(): c3d. to go from *note bytes: 336. to
     *note str: 335.  You can also use ‘bytes(s, encoding=...)’ and
     ‘str(b, encoding=...)’, respectively.

   * Like *note str: 335, the *note bytes: 336. type is immutable.
     There is a separate `mutable' type to hold buffered binary data,
     *note bytearray: 337.  Nearly all APIs that accept *note bytes:
     336. also accept *note bytearray: 337.  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: 335. instead.  The *note str: 335. and *note bytes: 336. 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: 335.

   * Files opened as text files (still the default mode for *note
     open(): 4f5.) 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: 1c. module.

   * The initial values of *note sys.stdin: 312, *note sys.stdout: 313.
     and *note sys.stderr: 314. are now unicode-only text files (i.e.,
     they are instances of *note io.TextIOBase: c3e.).  To read and
     write bytes data with these streams, you need to use their *note
     io.TextIOBase.buffer: c3f. 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(): 4f5. and many functions
     in the *note os: c5. module) that take filenames accept *note
     bytes: 336. objects as well as strings, and a few APIs have a way
     to ask for a *note bytes: 336. return value.  Thus, *note
     os.listdir(): a46. returns a list of *note bytes: 336. instances if
     the argument is a *note bytes: 336. instance, and *note
     os.getcwdb(): 2b9. returns the current working directory as a *note
     bytes: 336. instance.  Note that when *note os.listdir(): a46.
     returns a list of strings, filenames that cannot be decoded
     properly are omitted rather than raising *note UnicodeError: c40.

   * Some system APIs like *note os.environ: b3c. and *note sys.argv:
     c00. 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(): 7d1. 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: a2. module and use *note io.StringIO: 832. or *note
     io.BytesIO: 7a0. for text and data respectively.

   * See also the *note Unicode HOWTO: c41, which was updated for Python
     3.0.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3138

   (2) https://www.python.org/dev/peps/pep-3120

   (3) https://www.python.org/dev/peps/pep-3131


File: python.info,  Node: Overview Of Syntax Changes,  Next: Changes Already Present In Python 2 6,  Prev: Common Stumbling Blocks,  Up: What's New In Python 3 0

1.9.2 Overview Of Syntax Changes
--------------------------------

This section gives a brief overview of every `syntactic' change in
Python 3.0.

* Menu:

* New Syntax::
* Changed Syntax::
* Removed Syntax::


File: python.info,  Node: New Syntax,  Next: Changed Syntax,  Up: Overview Of Syntax Changes

1.9.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: c44. 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(): c45.

   * Bytes literals are introduced with a leading ‘b’ or ‘B’, and there
     is a new corresponding built-in function, *note bytes(): 336.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3107

   (2) https://www.python.org/dev/peps/pep-3102

   (3) https://www.python.org/dev/peps/pep-3104

   (4) https://www.python.org/dev/peps/pep-3132

   (5) https://www.python.org/dev/peps/pep-0274


File: python.info,  Node: Changed Syntax,  Next: Removed Syntax,  Prev: New Syntax,  Up: Overview Of Syntax Changes

1.9.2.2 Changed Syntax
......................

   * PEP 3109(1) and PEP 3134(2): new *note raise: c47. statement
     syntax: ‘raise [`expr' [from `expr']]’.  See below.

   * ‘as’ and *note with: 6ee. 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: b43. `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: 2b1.)

   * 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(): 263. 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://www.python.org/dev/peps/pep-3109

   (2) https://www.python.org/dev/peps/pep-3134

   (3) https://www.python.org/dev/peps/pep-3110

   (4) https://www.python.org/dev/peps/pep-3115


File: python.info,  Node: Removed Syntax,  Prev: Changed Syntax,  Up: Overview Of Syntax Changes

1.9.2.3 Removed Syntax
......................

   * 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(): 7d1. instead).

   * Removed ‘<>’ (use ‘!=’ instead).

   * Removed keyword: *note exec(): c49. 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(): c49. 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: c4a. `module' *note import: c22. ‘*’ 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: c22. forms not
     starting with ‘.’ are interpreted as absolute imports.  ( PEP
     328(2))

   * Classic classes are gone.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3113

   (2) https://www.python.org/dev/peps/pep-0328


File: python.info,  Node: Changes Already Present In Python 2 6,  Next: Library Changes,  Prev: Overview Of Syntax Changes,  Up: What's New In Python 3 0

1.9.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 What’s New in Python 2.6: c4c.
should be consulted for longer descriptions.

   * *note PEP 343; The ’with’ statement: c4d.  The *note with: 6ee.
     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: c4e. and *note The contextlib module:
     c4f.

   * *note PEP 366; Explicit Relative Imports From a Main Module: c50.
     This enhances the usefulness of the *note -m: 33c. option when the
     referenced module lives in a package.

   * *note PEP 370; Per-user site-packages Directory: c51.

   * *note PEP 371; The multiprocessing Package: c52.

   * *note PEP 3101; Advanced String Formatting: c53.  Note: the 2.6
     description mentions the *note format(): 4e0. method for both 8-bit
     and Unicode strings.  In 3.0, only the *note str: 335. type (text
     strings with Unicode support) supports this method; the *note
     bytes: 336. 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: c54.  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: c55.  The *note except:
     b43. `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: c56.  The ‘b"..."’ string literal
     notation (and its variants like ‘b'...'’, ‘b"""..."""’, and
     ‘br"..."’) now produces a literal of type *note bytes: 336.

   * *note PEP 3116; New I/O Library: c57.  The *note io: a2. module is
     now the standard way of doing file I/O. The built-in *note open():
     4f5. function is now an alias for *note io.open(): 65f. and has
     additional keyword arguments `encoding', `errors', `newline' and
     `closefd'.  Also note that an invalid `mode' argument now raises
     *note ValueError: 1fc, not *note IOError: 997.  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; Revised Buffer Protocol: c58.  The old builtin
     ‘buffer()’ is now really gone; the new builtin *note memoryview():
     25d. provides (mostly) similar functionality.

   * *note PEP 3119; Abstract Base Classes: c59.  The *note abc: 4.
     module and the ABCs defined in the *note collections: 1e. module
     plays a somewhat more prominent role in the language now, and
     built-in collection types like *note dict: 1b9. and *note list:
     263. conform to the ‘collections.MutableMapping’ and
     ‘collections.MutableSequence’ ABCs, respectively.

   * *note PEP 3127; Integer Literal Support and Syntax: c5a.  As
     mentioned above, the new octal literal notation is the only one
     supported, and binary literals have been added.

   * *note PEP 3129; Class Decorators: c5b.

   * *note PEP 3141; A Type Hierarchy for Numbers: c5c.  The *note
     numbers: c2. module is another new use of ABCs, defining Python’s
     "numeric tower".  Also note the new *note fractions: 83. module
     which implements *note numbers.Rational: c5d.


File: python.info,  Node: Library Changes,  Next: PEP 3101 A New Approach To String Formatting,  Prev: Changes Already Present In Python 2 6,  Up: What's New In Python 3 0

1.9.4 Library Changes
---------------------

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: 8d.), 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’.

   * Some modules were renamed because their old name disobeyed PEP
     8(5), or for various other reasons.  Here’s the list:

     Old Name                    New Name
                                 
     --------------------------------------------------------
                                 
     _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: cb. 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: cb. / ‘cPickle’ pair received this
     treatment.  The *note profile: d4. module is on the list for 3.1.
     The ‘StringIO’ module has been turned into a class in the *note io:
     a2. module.

   * Some related modules have been grouped into packages, and usually
     the submodule names have been simplified.  The resulting new
     packages are:

        * *note dbm: 32. (‘anydbm’, ‘dbhash’, *note dbm: 32, ‘dumbdbm’,
          ‘gdbm’, ‘whichdb’).

        * *note html: 90. (‘HTMLParser’, ‘htmlentitydefs’).

        * *note http: 93. (‘httplib’, ‘BaseHTTPServer’, ‘CGIHTTPServer’,
          ‘SimpleHTTPServer’, ‘Cookie’, ‘cookielib’).

        * *note tkinter: 10d. (all ‘Tkinter’-related modules except
          *note turtle: 117.).  The target audience of *note turtle:
          117. doesn’t really care about *note tkinter: 10d.  Also note
          that as of Python 2.6, the functionality of *note turtle: 117.
          has been greatly enhanced.

        * *note urllib: 11e. (*note urllib: 11e, ‘urllib2’, ‘urlparse’,
          ‘robotparse’).

        * ‘xmlrpc’ (‘xmlrpclib’, ‘DocXMLRPCServer’,
          ‘SimpleXMLRPCServer’).

Some other changes to standard library modules, not covered by PEP
3108(6):

   * Killed ‘sets’.  Use the built-in *note set(): b74. class.

   * Cleanup of the *note sys: fe. module: removed ‘sys.exitfunc()’,
     ‘sys.exc_clear()’, ‘sys.exc_type’, ‘sys.exc_value’,
     ‘sys.exc_traceback’.  (Note that *note sys.last_type: c5f. etc.
     remain.)

   * Cleanup of the *note array.array: 456. 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: c3. module: removed
     ‘sequenceIncludes()’ and ‘isCallable()’.

   * Cleanup of the ‘thread’ module: ‘acquire_lock()’ and
     ‘release_lock()’ are gone; use ‘acquire()’ and ‘release()’ instead.

   * Cleanup of the *note random: dd. module: removed the ‘jumpahead()’
     API.

   * The ‘new’ module is gone.

   * The functions ‘os.tmpnam()’, ‘os.tempnam()’ and ‘os.tmpfile()’ have
     been removed in favor of the *note tempfile: 104. module.

   * The *note tokenize: 112. module has been changed to work with
     bytes.  The main entry point is now *note tokenize.tokenize(): c60,
     instead of generate_tokens.

   * ‘string.letters’ and its friends (‘string.lowercase’ and
     ‘string.uppercase’) are gone.  Use *note string.ascii_letters: c61.
     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: 13. (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: 13, not ‘__builtins__’!

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3108

   (2) https://www.python.org/dev/peps/pep-0004

   (3) https://www.python.org/dev/peps/pep-0011

   (4) https://www.python.org/dev/peps/pep-3108

   (5) https://www.python.org/dev/peps/pep-0008

   (6) https://www.python.org/dev/peps/pep-3108


File: python.info,  Node: PEP 3101 A New Approach To String Formatting,  Next: Changes To Exceptions,  Prev: Library Changes,  Up: What's New In Python 3 0

1.9.5 `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://www.python.org/dev/peps/pep-3101


File: python.info,  Node: Changes To Exceptions,  Next: Miscellaneous Other Changes,  Prev: PEP 3101 A New Approach To String Formatting,  Up: What's New In Python 3 0

1.9.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: 1a9.  This is the root of the exception
     hierarchy.  This is not new as a recommendation, but the
     `requirement' to inherit from *note BaseException: 1a9. 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:
     1aa.; *note BaseException: 1a9. should only be used as a base class
     for exceptions that should only be handled at the top level, such
     as *note SystemExit: 601. or *note KeyboardInterrupt: 198.  The
     recommended idiom for handling all exceptions except for this
     latter category is to use *note except: b43. *note Exception: 1aa.

   * ‘StandardError’ was removed.

   * 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
     ‘__traceback__’ 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: b43. 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: b43. or *note finally: 183.
     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
     ‘__context__’ 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
     ‘__cause__’ attribute of the secondary exception.  The traceback
     printed when an unhandled exception occurs walks the chain of
     ‘__cause__’ and ‘__context__’ 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
     ‘__traceback__’ 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(): c64. (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://www.python.org/dev/peps/pep-0352

   (2) https://www.python.org/dev/peps/pep-3109

   (3) https://www.python.org/dev/peps/pep-3110

   (4) https://www.python.org/dev/peps/pep-3134

   (5) https://www.python.org/dev/peps/pep-3134


File: python.info,  Node: Miscellaneous Other Changes,  Next: Build and C API Changes<7>,  Prev: Changes To Exceptions,  Up: What's New In Python 3 0

1.9.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.9.7.1 Operators And Special Methods
.....................................

   * ‘!=’ now returns the opposite of ‘==’, unless ‘==’ returns *note
     NotImplemented: 851.

   * 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 *note __setitem__(): c67. or *note
     __delitem__(): c68, when used as an assignment or deletion target,
     respectively).

   * PEP 3114(1): the standard *note next(): 687. method has been
     renamed to *note __next__(): c69.

   * The ‘__oct__()’ and ‘__hex__()’ special methods are removed – *note
     oct(): c6a. and *note hex(): c6b. use *note __index__(): 18b. now
     to convert the argument to an integer.

   * Removed support for ‘__members__’ and ‘__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 ‘__closure__’,
     ‘__code__’, ‘__defaults__’, *note __dict__: 501, ‘__doc__’,
     ‘__globals__’, *note __name__: c6c, respectively.

   * ‘__nonzero__()’ is now *note __bool__(): c6d.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3114


File: python.info,  Node: Builtins,  Prev: Operators And Special Methods,  Up: Miscellaneous Other Changes

1.9.7.2 Builtins
................

   * PEP 3135(1): New *note super(): 4e7.  You can now invoke *note
     super(): 4e7. without arguments and (assuming this is in a regular
     instance method defined inside a *note class: c6f. statement) the
     right class and instance will automatically be chosen.  With
     arguments, the behavior of *note super(): 4e7. is unchanged.

   * PEP 3111(2): ‘raw_input()’ was renamed to *note input(): c70.  That
     is, the new *note input(): c70. function reads a line from *note
     sys.stdin: 312. and returns it with the trailing newline stripped.
     It raises *note EOFError: c71. if the input is terminated
     prematurely.  To get the old behavior of *note input(): c70, use
     ‘eval(input())’.

   * A new built-in function *note next(): 687. was added to call the
     *note __next__(): c69. method on an object.

   * The *note round(): c72. 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(): c73.

   * Removed: ‘apply()’.  Instead of ‘apply(f, args)’ use ‘f(*args)’.

   * Removed *note callable(): b49.  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.

   * Removed ‘execfile()’.  Instead of ‘execfile(fn)’ use
     ‘exec(open(fn).read())’.

   * Removed the ‘file’ type.  Use *note open(): 4f5.  There are now
     several different kinds of streams that open can return in the
     *note io: a2. module.

   * Removed ‘reduce()’.  Use *note functools.reduce(): c74. if you
     really need it; however, 99 percent of the time an explicit *note
     for: c35. loop is more readable.

   * Removed ‘reload()’.  Use *note imp.reload(): c75.

   * Removed.  ‘dict.has_key()’ – use the *note in: 7a8. operator
     instead.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3135

   (2) https://www.python.org/dev/peps/pep-3111


File: python.info,  Node: Build and C API Changes<7>,  Next: Performance,  Prev: Miscellaneous Other Changes,  Up: What's New In Python 3 0

1.9.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): New Buffer API.

   * PEP 3121(2): Extension Module Initialization & Finalization.

   * PEP 3123(3): Making *note PyObject_HEAD: c77. 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(): 9c6, works like
     *note PyImport_ImportModule(): c78. 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’.

   * Removed ‘METH_OLDARGS’ and ‘WITH_CYCLE_GC’ from the C API.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3118

   (2) https://www.python.org/dev/peps/pep-3121

   (3) https://www.python.org/dev/peps/pep-3123


File: python.info,  Node: Performance,  Next: Porting To Python 3 0,  Prev: Build and C API Changes<7>,  Up: What's New In Python 3 0

1.9.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: What's New In Python 3 0

1.9.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.  (See *note 2to3 - 自動將 Python 2的程式碼轉成 Python 3: c7b.
     for more on this tool.)  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: c7c.


File: python.info,  Node: What's New in Python 2 7,  Next: What's New in Python 2 6,  Prev: What's New In Python 3 0,  Up: Python 有什麼新功能？

1.10 What’s New in Python 2.7
=============================


Author: 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: 189. class.  There are some useful
additions to the standard library, such as a greatly enhanced *note
unittest: 11c. module, the *note argparse: 6. module for parsing
command-line options, convenient *note OrderedDict: 1ba. and *note
Counter: 9df. classes in the *note collections: 1e. 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:

* The Future for Python 2.x: The Future for 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.
* Other Language Changes: Other Language Changes<9>.
* New and Improved Modules::
* Build and C API Changes: Build and C API Changes<8>.
* 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.
* Acknowledgements::


File: python.info,  Node: The Future for Python 2 x,  Next: Changes to the Handling of Deprecation Warnings,  Up: What's New in Python 2 7

1.10.1 The Future for 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: c81. 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 *note Python 2
的程式碼移植到Python 3: c82. HOWTO guide.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0373

   (2) https://packaging.python.org


File: python.info,  Node: Changes to the Handling of Deprecation Warnings,  Next: Python 3 1 Features,  Prev: The Future for Python 2 x,  Up: What's New in Python 2 7

1.10.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: 279. 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: 279. 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: 279. 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: 279. messages by
running Python with the *note -Wdefault: 41c. (short form: *note -Wd:
41c.) switch, or by setting the *note PYTHONWARNINGS: 41d. 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/issue7319


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: What's New in Python 2 7

1.10.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: 6ee. statement.

   * A new version of the *note io: a2. library, rewritten in C for
     performance.

   * The ordered-dictionary type described in *note PEP 372; Adding an
     Ordered Dictionary to collections: c85.

   * The new ‘","’ format specifier described in *note PEP 378; Format
     Specifier for Thousands Separator: c86.

   * The *note memoryview: 25d. object.

   * A small subset of the *note importlib: 9b. module, *note described
     below: c87.

   * The *note repr(): 7d1. 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(): c72. function is also now correctly
     rounded.

   * The *note PyCapsule: c0c. type, used to provide a C API for
     extension modules.

   * The *note PyLong_AsLongAndOverflow(): c02. C API function.

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: What's New in Python 2 7

1.10.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: 1ba. class in the *note collections:
1e. module.

The *note OrderedDict: 1ba. 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(): c89. 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: 1ba. with a regular dictionary ignores
the insertion order and just compares the keys and values.

How does the *note OrderedDict: 1ba. 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 ‘ConfigParser’ 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(): 1b7. method for *note
     collections.namedtuple(): 1b8. now returns an ordered dictionary
     with the values appearing in the same order as the underlying tuple
     indices.

   * The *note json: a5. module’s *note JSONDecoder: 60c. 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) http://pyyaml.org/

   (2) https://www.python.org/dev/peps/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: What's New in Python 2 7

1.10.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: aa.
module, which can use different separators ("," in North America, "."
in Europe) and different grouping sizes, but *note locale: aa. 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(): 4df. 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: aa.
module, but it’s easier to use.

也參考
......

PEP 378(1) - Format Specifier for Thousands Separator

     PEP written by Raymond Hettinger; implemented by Eric Smith.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: What's New in Python 2 7

1.10.6 PEP 389: The argparse Module for Parsing Command Lines
-------------------------------------------------------------

The *note argparse: 6. module for parsing command-line arguments was
added as a more powerful replacement for the *note optparse: c4. module.

This means Python now supports three different modules for parsing
command-line arguments: *note getopt: 87, *note optparse: c4, and *note
argparse: 6.  The *note getopt: 87. 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:
c4. 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: 6. API consistent with *note
optparse: c4.’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: 6.
instead of *note optparse: c4.

Here’s an example:

     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: c4, 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: 6. has much fancier validation than *note optparse: c4.;
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: 825, which will automatically open files for you and
understands that ‘'-'’ means standard input or output.

也參考
......

*note argparse: 6. documentation

     The documentation page of the argparse module.

*note Upgrading optparse code: b2e.

     Part of the Python documentation, describing how to convert code
     that uses *note optparse: c4.

PEP 389(1) - argparse - New Command Line Parsing Module

     PEP written and implemented by Steven Bethard.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: What's New in Python 2 7

1.10.7 PEP 391: Dictionary-Based Configuration For Logging
----------------------------------------------------------

The *note logging: ab. 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: ab.
also supports a ‘fileConfig()’ 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 ‘dictConfig()’ 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: c8d.

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: ab. module, all
implemented by Vinay Sajip, are:

   * The *note SysLogHandler: a23. class now supports syslogging over
     TCP. The constructor has a `socktype' parameter giving the type of
     socket to use, either *note socket.SOCK_DGRAM: c8e. for UDP or
     *note socket.SOCK_STREAM: c8f. for TCP. The default protocol
     remains UDP.

   * *note Logger: 3ac. instances gained a *note getChild(): c90. 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: c91. class gained an ‘isEnabledFor()’
     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

     PEP written and implemented by Vinay Sajip.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: What's New in Python 2 7

1.10.8 PEP 3106: Dictionary Views
---------------------------------

The dictionary methods *note keys(): c2f, *note values(): c31, and *note
items(): c30. 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(): c2f,
*note values(): c31, and *note items(): c30. 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(): c2f, *note values(): c31,
and *note items(): c30. 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://www.python.org/dev/peps/pep-3106

   (2) https://bugs.python.org/issue1967


File: python.info,  Node: PEP 3137 The memoryview Object,  Next: Other Language Changes<9>,  Prev: PEP 3106 Dictionary Views,  Up: What's New in Python 2 7

1.10.9 PEP 3137: The memoryview Object
--------------------------------------

The *note memoryview: 25d. object provides a view of another object’s
memory content that matches the *note bytes: 336. 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: 25d. 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://www.python.org/dev/peps/pep-3137

   (2) https://bugs.python.org/issue2396


File: python.info,  Node: Other Language Changes<9>,  Next: New and Improved Modules,  Prev: PEP 3137 The memoryview Object,  Up: What's New in Python 2 7

1.10.10 Other Language Changes
------------------------------

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: 6ee. 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(): 335. on floats and complex
     numbers; the *note float: 188. and *note complex: 18a.
     constructors; numeric formatting; serializing and deserializing
     floats and complex numbers using the *note marshal: b1, *note
     pickle: cb. and *note json: a5. modules; parsing of float and
     imaginary literals in Python code; and *note Decimal: 189.-to-float
     conversion.

     Related to this, the *note repr(): 7d1. 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: c95, 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

     (Implemented by 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(): 4df. method now supports automatic
     numbering of the replacement fields.  This makes using *note
     str.format(): 4df. 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(): 4df, 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():
     4e0, 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__(): 953. method now
     triggers a *note PendingDeprecationWarning: 27a. if it’s passed a
     format string, because the *note __format__(): 953. method for
     *note object: 2b1. 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(): 185. 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

     (Contributed by Fredrik Johansson and Victor Stinner;
     bpo-3439(12).)

   * The *note import: c22. 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: 337. type’s *note translate(): c96. method now
     accepts ‘None’ as its first argument.  (Fixed by Georg Brandl;
     bpo-4759(15).)

   * When using ‘@classmethod’ and ‘@staticmethod’ to wrap methods as
     class or static methods, the wrapper object now exposes the wrapped
     function as their ‘__func__’ 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:
     3a0. 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: 997. 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(): 1b5. 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::
* Optimizations: Optimizations<8>.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue2335

   (2) https://bugs.python.org/issue2333

   (3) https://bugs.python.org/issue7117

   (4) https://bugs.python.org/issue3166

   (5) https://bugs.python.org/issue1811

   (6) https://bugs.python.org/issue5211

   (7) https://bugs.python.org/issue5237

   (8) https://bugs.python.org/issue1588

   (9) https://bugs.python.org/issue7988

   (10) https://bugs.python.org/issue3382

   (11) https://bugs.python.org/issue7994

   (12) https://bugs.python.org/issue3439

   (13) https://bugs.python.org/issue7902

   (14) https://bugs.python.org/issue1583863

   (15) https://bugs.python.org/issue4759

   (16) https://bugs.python.org/issue5982

   (17) https://bugs.python.org/issue7604

   (18) https://bugs.python.org/issue1616979

   (19) https://bugs.python.org/issue8016

   (20) https://bugs.python.org/issue4764

   (21) https://bugs.python.org/issue5677

   (22) https://bugs.python.org/issue7362

   (23) https://bugs.python.org/issue8268

   (24) https://bugs.python.org/issue7140


File: python.info,  Node: Interpreter Changes,  Next: Optimizations<8>,  Up: Other Language Changes<9>

1.10.10.1 Interpreter Changes
.............................

A new environment variable, *note PYTHONWARNINGS: 41d, allows
controlling warnings.  It should be set to a string containing warning
settings, equivalent to those used with the *note -W: 41c. 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 ‘Cookie’ 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/issue7301


File: python.info,  Node: Optimizations<8>,  Prev: Interpreter Changes,  Up: Other Language Changes<9>

1.10.10.2 Optimizations
.......................

Several performance enhancements have been added:

   * A new opcode was added to perform the initial setup for *note with:
     6ee. statements, looking up the *note __enter__(): c9a. and *note
     __exit__(): c9b. 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)

     (Contributed by 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: 337. 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: cb. 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/issue4074

   (2) https://bugs.python.org/issue4688

   (3) https://bugs.python.org/issue4258

   (4) https://bugs.python.org/issue5260

   (5) https://bugs.python.org/issue5512

   (6) https://bugs.python.org/issue1087418

   (7) https://bugs.python.org/issue5176

   (8) https://bugs.python.org/issue4715

   (9) https://bugs.python.org/issue6713

   (10) https://bugs.python.org/issue7462

   (11) https://bugs.python.org/issue7622

   (12) https://bugs.python.org/issue5084

   (13) https://bugs.python.org/issue5670


File: python.info,  Node: New and Improved Modules,  Next: Build and C API Changes<8>,  Prev: Other Language Changes<9>,  Up: What's New in Python 2 7

1.10.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: f. module’s base debugging class *note Bdb: c9d.
     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: 10. module now supports the buffer API, so it
     can be used with *note memoryview: 25d. 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 ‘http://hg.jcea.es/pybsddb/file/tip/ChangeLog’.)

   * The *note bz2: 14. module’s *note BZ2File: 936. 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: 9df. class in the *note collections:
     1e. module is useful for tallying data.  *note Counter: 9df.
     instances behave mostly like dictionaries but return zero for
     missing keys instead of raising a *note KeyError: 2c8.:

          >>> 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: 9df. methods.  *note
     most_common(): c9e. returns the N most common elements and their
     counts.  *note elements(): c9f. returns an iterator over the
     contained elements, repeating each element as many times as its
     count.  *note subtract(): b5f. 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: 1ba. is described in the earlier
     section *note PEP 372; Adding an Ordered Dictionary to collections:
     c85.

     New method: The *note deque: 536. data type now has a *note
     count(): b61. method that returns the number of contained elements
     equal to the supplied argument `x', and a *note reverse(): b62.
     method that reverses the elements of the deque in-place.  *note
     deque: 536. also exposes its maximum length as the read-only *note
     maxlen: ca0. attribute.  (Both features added by Raymond
     Hettinger.)

     The *note namedtuple: 1b8. 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 ‘Mapping’ abstract base class now returns *note
     NotImplemented: 851. 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 ‘ConfigParser’ 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'

     (Contributed by Mats Kindahl; bpo-7005(9).)

   * Deprecated function: ‘contextlib.nested()’, which allows handling
     more than one context manager with a single *note with: 6ee.
     statement, has been deprecated, because the ‘with’ statement now
     supports multiple context managers.

   * The ‘cookielib’ 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: 26. module’s *note deepcopy(): 3d1. function will
     now correctly copy bound instance methods.  (Implemented by Robert
     Collins; bpo-1515(11).)

   * The *note ctypes: 2b. 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: 31. module’s *note timedelta: 196.
     class gained a *note total_seconds(): ca1. method that returns the
     number of seconds in the duration.  (Contributed by Brian Quinlan;
     bpo-5788(15).)

   * New method: the *note Decimal: 189. class gained a *note
     from_float(): b85. class method that performs an exact conversion
     of a floating-point number to a *note Decimal: 189.  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: 189. 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 *note Decimal: 189.  (Fixed by Mark Dickinson;
     bpo-2531(17).)

     The constructor for *note Decimal: 189. 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: 9f5. class now accept
     integers as well as *note Decimal: 189. instances; the only
     exceptions are the *note canonical(): ca2. and *note
     is_canonical(): ca3. methods.  (Patch by Juan José Conti;
     bpo-7633(20).)

     When using *note Decimal: 189. instances with a string’s *note
     format(): 4df. 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
     ‘InvalidOperation’ 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: 37. 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: 67. module’s ‘IGNORE_EXCEPTION_DETAIL’ flag will
     now ignore the name of the module containing the exception being
     tested.  (Patch by Lennart Regebro; bpo-7490(25).)

   * The *note email: 69. module’s *note Message: 546. 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: 186. class now accepts a single float or *note
     Decimal: 189. 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: 193.  This fixes an
     oversight, making the *note Fraction: 186. match the other numeric
     types.

   * New class: *note FTP_TLS: a08. in the *note ftplib: 84. 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(): ca4. 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(): 850. in the *note
     functools: 85. module takes a class that defines an *note __eq__():
     344. method and one of *note __lt__(): c39, *note __le__(): ca5,
     *note __gt__(): ca6, or *note __ge__(): ca7, 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(): b5b. 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(): 449, *note min(): 80e. and *note max(): 80f,
     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: 86. module’s *note is_tracked(): ca8.
     returns true if a given instance is tracked by the garbage
     collector, false otherwise.  (Contributed by Antoine Pitrou;
     bpo-4688(32).)

   * The *note gzip: 8c. module’s *note GzipFile: 6e2. 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:
     58d. ABC, so you can wrap it with *note io.BufferedReader: b8f. 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: 8c. module will now consume these trailing bytes.
     (Fixed by Tadek Pietraszek and Brian Curtin; bpo-2846(36).)

   * New attribute: the *note hashlib: 8d. 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 ‘HTTPResponse’ class used by the ‘httplib’ module now
     supports buffering, resulting in much faster reading of HTTP
     responses.  (Contributed by Kristján Valur Jónsson; bpo-4879(38).)

     The ‘HTTPConnection’ and ‘HTTPSConnection’ 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: 98. module now supports IPv6 addresses.
     (Contributed by Derek Morr; bpo-1655(40).)

   * New function: the *note inspect: a1. module’s *note getcallargs():
     7bb. 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: a2. 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: c3e. class now
     has an ‘errors’ attribute giving the error setting used for
     encoding and decoding errors (one of ‘'strict'’, ‘'replace'’,
     ‘'ignore'’).

     The *note io.FileIO: ca9. class now raises an *note OSError: 1d4.
     when passed an invalid file descriptor.  (Implemented by Benjamin
     Peterson; bpo-4991(42).)  The *note truncate(): caa. 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(): cab, 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(): c20. function now has a `step'
     argument that allows incrementing by values other than 1.  *note
     count(): c20. also now allows keyword arguments, and using
     non-integer values such as floats or *note Decimal: 189. instances.
     (Implemented by Raymond Hettinger; bpo-5032(44).)

     *note itertools.combinations(): cab. and *note itertools.product():
     cac. previously raised *note ValueError: 1fc. 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: a5. 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: 1ba. type, *note
     json.load(): 564. 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: af. module’s *note Maildir: cad. 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: b2. module gained *note erf(): 457.
     and *note erfc(): 458. for the error function and the complementary
     error function, *note expm1(): b6d. which computes ‘e**x - 1’ with
     more precision than using *note exp(): cae. and subtracting 1,
     *note gamma(): b6e. for the Gamma function, and *note lgamma():
     b6f. for the natural log of the Gamma function.  (Contributed by
     Mark Dickinson and nirinA raseliarison; bpo-3366(50).)

   * The *note multiprocessing: b8. 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 ‘Pool’ 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 *note nntplib: c1. module now supports IPv6 addresses.
     (Contributed by Derek Morr; bpo-1664(53).)

   * New functions: the *note os: c5. module wraps the following POSIX
     system calls: *note getresgid(): caf. and *note getresuid(): cb0,
     which return the real, effective, and saved GIDs and UIDs; *note
     setresgid(): cb1. and *note setresuid(): cb2, which set real,
     effective, and saved GIDs and UIDs to new values; *note
     initgroups(): cb3, 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(): 966. function now re-initializes the import
     lock in the child process; this fixes problems on Solaris when
     *note fork(): 966. is called from a thread.  (Fixed by Zsolt
     Cserna; bpo-7242(56).)

   * In the *note os.path: c6. module, the *note normpath(): cb4. and
     *note abspath(): cb5. functions now preserve Unicode; if their
     input path is a Unicode string, the return value is also a Unicode
     string.  (*note normpath(): cb4. fixed by Matt Giuca in
     bpo-5827(57); *note abspath(): cb5. fixed by Ezio Melotti in
     bpo-3426(58).)

   * The *note pydoc: da. 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: de. module’s *note split(): 3cf, *note sub(): 480,
     and *note subn(): 739. 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(): cb6. in the *note runpy: e3. 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: e3.
     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: ea. module, *note
     make_archive(): 21c. 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: ea.’s *note copyfile(): 259. and *note copytree():
     21b. 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: eb. 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: ec. module, three new functions
     return various site- and user-specific paths.  *note
     getsitepackages(): bd8. returns a list containing all global
     site-packages directories, *note getusersitepackages(): bda.
     returns the path of the user’s site-packages directory, and *note
     getuserbase(): bd9. returns the value of the ‘USER_BASE’
     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: ec. module now reports exceptions occurring when
     the ‘sitecustomize’ module is imported, and will no longer catch
     and swallow the *note KeyboardInterrupt: 198. exception.  (Fixed by
     Victor Stinner; bpo-3137(64).)

   * The *note create_connection(): ba3. 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(): cb7. and *note recvfrom_into(): cb8. methods
     will now write into objects that support the buffer API, most
     usefully the *note bytearray: 337. and *note memoryview: 25d.
     objects.  (Implemented by Antoine Pitrou; bpo-8104(66).)

   * The ‘SocketServer’ module’s ‘TCPServer’ 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 ‘timeout’ class attribute can hold a
     timeout in seconds that will be applied to the request socket; if
     no request is received within that time, ‘handle_timeout()’ will be
     called and ‘handle_request()’ will return.  (Contributed by
     Kristján Valur Jónsson; bpo-6192(67) and bpo-6267(68).)

   * Updated module: the *note sqlite3: f3. 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(): b9f. to load a particular shared
     library.  (Updated by Gerhard Häring.)

   * The *note ssl: f4. module’s *note SSLSocket: 3e7. 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 ssl.wrap_socket(): 474. 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: ba6. (a string), *note
     ssl.OPENSSL_VERSION_INFO: ba7. (a 5-tuple), and *note
     ssl.OPENSSL_VERSION_NUMBER: ba8. (an integer).  (Added by Antoine
     Pitrou; bpo-8321(75).)

   * The *note struct: f9. 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: cb9. exception.  (Changed by Mark Dickinson;
     bpo-1523(76).)  The *note pack(): c10. function will also attempt
     to use *note __index__(): 18b. to convert and pack non-integers
     before trying the *note __int__(): 18c. method or reporting an
     error.  (Changed by Mark Dickinson; bpo-8300(77).)

   * New function: the *note subprocess: fa. module’s *note
     check_output(): 8e0. 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:
     cba. 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

     (Contributed by Gregory P. Smith.)

     The *note subprocess: fa. module will now retry its internal system
     calls on receiving an ‘EINTR’ signal.  (Reported by several people;
     final patch by Gregory P. Smith in bpo-1068268(78).)

   * New function: *note is_declared_global(): cbb. in the *note
     symtable: fd. 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: 100. 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 ‘sys.version_info’ 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(): 59a. also returns a named tuple,
     with attributes named ‘major’, ‘minor’, ‘build’, *note platform:
     cf, ‘service_pack’, ‘service_pack_major’, ‘service_pack_minor’,
     ‘suite_mask’, and ‘product_type’.  (Contributed by Brian Curtin;
     bpo-7766(81).)

   * The *note tarfile: 102. 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: 102. now supports filtering the *note TarInfo: b92.
     objects being added to a tar file.  When you call *note add(): 481,
     you may supply an optional `filter' argument that’s a callable.
     The `filter' callable will be passed the *note TarInfo: b92. 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: b91. class also
     now supports the context management protocol.  (Added by Lars
     Gustäbel; bpo-7232(84).)

   * The *note wait(): cbc. method of the *note threading.Event: ab2.
     class now returns the internal flag on exit.  This means the method
     will usually return true because *note wait(): cbc. 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: 11b. 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 ‘urlparse’ module’s ‘urlsplit()’ 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 ‘urlparse’ 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: cbd. class in the *note weakref: 129.
     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 ElementTree library, ‘xml.etree’, 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 ‘xmlrpclib’ and
     ‘SimpleXMLRPCServer’ 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
     ‘SimpleXMLRPCRequestHandler’, 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: 143. module’s *note ZipFile: 424. now supports
     the context management protocol, so you can write ‘with
     zipfile.ZipFile(...) as f:’.  (Contributed by Brian Curtin;
     bpo-5511(93).)

     *note zipfile: 143. 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(): cbe. and ‘readline()’ now works
     correctly.  (Contributed by Nir Aides; bpo-7610(95).)

     The *note is_zipfile(): cbf. 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(): cc0. method now has an optional
     `compress_type' parameter that lets you override the default
     compression method specified in the *note ZipFile: 424.
     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/issue5142

   (2) https://bugs.python.org/issue7703

   (3) https://www.jcea.es/programacion/pybsddb.htm

   (4) https://bugs.python.org/issue8156

   (5) https://bugs.python.org/issue3860

   (6) https://bugs.python.org/issue1696199

   (7) https://bugs.python.org/issue1818

   (8) https://bugs.python.org/issue8729

   (9) https://bugs.python.org/issue7005

   (10) https://bugs.python.org/issue3924

   (11) https://bugs.python.org/issue1515

   (12) https://bugs.python.org/issue4606

   (13) https://sourceware.org/libffi/

   (14) https://bugs.python.org/issue8142

   (15) https://bugs.python.org/issue5788

   (16) https://bugs.python.org/issue4796

   (17) https://bugs.python.org/issue2531

   (18) https://bugs.python.org/issue8257

   (19) https://bugs.python.org/issue6595

   (20) https://bugs.python.org/issue7633

   (21) https://bugs.python.org/issue6857

   (22) https://bugs.python.org/issue7279

   (23) https://bugs.python.org/issue7585

   (24) https://bugs.python.org/issue8688

   (25) https://bugs.python.org/issue7490

   (26) https://bugs.python.org/issue1368247

   (27) https://bugs.python.org/issue5812

   (28) https://bugs.python.org/issue8294

   (29) https://bugs.python.org/issue2054

   (30) https://bugs.python.org/issue6845

   (31) https://bugs.python.org/issue5479

   (32) https://bugs.python.org/issue4688

   (33) https://bugs.python.org/issue3860

   (34) https://bugs.python.org/issue7471

   (35) https://bugs.python.org/issue4272

   (36) https://bugs.python.org/issue2846

   (37) https://bugs.python.org/issue7418

   (38) https://bugs.python.org/issue4879

   (39) https://bugs.python.org/issue3972

   (40) https://bugs.python.org/issue1655

   (41) https://bugs.python.org/issue3135

   (42) https://bugs.python.org/issue4991

   (43) https://bugs.python.org/issue6939

   (44) https://bugs.python.org/issue5032

   (45) https://bugs.python.org/issue4816

   (46) https://bugs.python.org/issue4136

   (47) https://bugs.python.org/issue5381

   (48) https://bugs.python.org/issue1607951

   (49) https://bugs.python.org/issue6896

   (50) https://bugs.python.org/issue3366

   (51) https://bugs.python.org/issue5585

   (52) https://bugs.python.org/issue6963

   (53) https://bugs.python.org/issue1664

   (54) https://bugs.python.org/issue6508

   (55) https://bugs.python.org/issue7333

   (56) https://bugs.python.org/issue7242

   (57) https://bugs.python.org/issue5827

   (58) https://bugs.python.org/issue3426

   (59) https://bugs.python.org/issue4739

   (60) https://bugs.python.org/issue6816

   (61) https://bugs.python.org/issue3002

   (62) https://bugs.python.org/issue8354

   (63) https://bugs.python.org/issue6693

   (64) https://bugs.python.org/issue3137

   (65) https://bugs.python.org/issue3972

   (66) https://bugs.python.org/issue8104

   (67) https://bugs.python.org/issue6192

   (68) https://bugs.python.org/issue6267

   (69) https://github.com/ghaering/pysqlite

   (70) https://bugs.python.org/issue7133

   (71) https://bugs.python.org/issue8222

   (72) 
https://www.openssl.org/docs/manmaster/man1/ciphers.html#CIPHER-LIST-FORMAT

   (73) https://bugs.python.org/issue8322

   (74) https://bugs.python.org/issue8484

   (75) https://bugs.python.org/issue8321

   (76) https://bugs.python.org/issue1523

   (77) https://bugs.python.org/issue8300

   (78) https://bugs.python.org/issue1068268

   (79) https://bugs.python.org/issue8451

   (80) https://bugs.python.org/issue4285

   (81) https://bugs.python.org/issue7766

   (82) https://bugs.python.org/issue7357

   (83) https://bugs.python.org/issue6856

   (84) https://bugs.python.org/issue7232

   (85) https://bugs.python.org/issue1674032

   (86) https://bugs.python.org/issue1571184

   (87) https://bugs.python.org/issue8024

   (88) https://tools.ietf.org/html/rfc3986.html

   (89) https://tools.ietf.org/html/rfc2732.html

   (90) https://bugs.python.org/issue2987

   (91) https://bugs.python.org/issue2746

   (92) https://bugs.python.org/issue6267

   (93) https://bugs.python.org/issue5511

   (94) https://bugs.python.org/issue4710

   (95) https://bugs.python.org/issue7610

   (96) https://bugs.python.org/issue4756

   (97) https://bugs.python.org/issue6003


File: python.info,  Node: New module importlib,  Next: New module sysconfig,  Up: New and Improved Modules

1.10.11.1 New module: importlib
...............................

Python 3.1 includes the *note importlib: 9b. package, a
re-implementation of the logic underlying Python’s *note import: c22.
statement.  *note importlib: 9b. is useful for implementors 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: 9b. package, but instead has a tiny subset
that contains a single function, *note import_module(): b18.

‘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(): b18. both
inserts the imported module into ‘sys.modules’ and returns the module
object.

Here are some examples:

     >>> 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: 9b. 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.10.11.2 New module: sysconfig
...............................

The *note sysconfig: ff. module has been pulled out of the Distutils
package, becoming a new top-level module in its own right.  *note
sysconfig: ff. 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(): 969. returns variables from Python’s
     Makefile and the ‘pyconfig.h’ file.

   * *note get_config_vars(): 96a. returns a dictionary containing all
     of the configuration variables.

   * *note get_path(): cc3. returns the configured path for a particular
     type of module: the standard library, site-specific modules,
     platform-specific modules, etc.

   * *note is_python_build(): cc4. returns true if you’re running a
     binary from a Python source tree, and false otherwise.

Consult the *note sysconfig: ff. documentation for more details and for
a complete list of functions.

The Distutils package and *note sysconfig: ff. 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.10.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 ‘ttk’ 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.htm’.  Some
screenshots of the Python/Ttk code in use are at
‘https://code.google.com/archive/p/python-ttk/wikis/Screenshots.wiki’.

The ‘ttk’ 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/issue2983

   (2) https://bugs.python.org/issue2618


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.10.11.4 Updated module: unittest
..................................

The *note unittest: 11c. 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
‘https://pypi.org/project/unittest2’.

When used from the command line, the module can automatically discover
tests.  It’s not as fancy as py.test(1) or nose(2), 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: 11c. module documentation for more details.
(Developed in bpo-6001(3).)

The *note main(): 907. function supports some other new options:

   * *note -b: cc8. 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: cc9. 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(): cca. decorator that can be used to mark tests that
     should have the control-C handling disabled.

   * *note -f: ccb. 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(4).)

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: 908. exception to skip a test
(bpo-1034053(5)).

The error messages for *note assertEqual(): bba, *note assertTrue():
bb9, and *note assertFalse(): ccc. failures now provide more
information.  If you set the *note longMessage: ccd. attribute of your
*note TestCase: 904. 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(6).)

The *note assertRaises(): abf. 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']

(Implemented by Antoine Pitrou; bpo-4444(7).)

Module- and class-level setup and teardown fixtures are now supported.
Modules can contain ‘setUpModule()’ and ‘tearDownModule()’ functions.
Classes can have *note setUpClass(): 24d. and *note tearDownClass():
cce. 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(): 2a3. and *note doCleanups(): ccf. were
added.  *note addCleanup(): 2a3. lets you add cleanup functions that
will be called unconditionally (after *note setUp(): cd0. if *note
setUp(): cd0. fails, otherwise after *note tearDown(): cd1.).  This
allows for much simpler resource allocation and deallocation during
tests (bpo-5679(8)).

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: 11c.

   * *note assertIsNone(): cd2. and *note assertIsNotNone(): cd3. take
     one expression and verify that the result is or is not ‘None’.

   * *note assertIs(): cd4. and *note assertIsNot(): cd5. take two
     values and check whether the two values evaluate to the same object
     or not.  (Added by Michael Foord; bpo-2578(9).)

   * *note assertIsInstance(): cd6. and *note assertNotIsInstance():
     cd7. 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(10).)

   * *note assertGreater(): cd8, *note assertGreaterEqual(): cd9, *note
     assertLess(): cda, and *note assertLessEqual(): cdb. compare two
     quantities.

   * *note assertMultiLineEqual(): cdc. 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():
     bba.

   * ‘assertRegexpMatches()’ and ‘assertNotRegexpMatches()’ checks
     whether the first argument is a string matching or not matching the
     regular expression provided as the second argument (bpo-8038(11)).

   * ‘assertRaisesRegexp()’ 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(): cdd. and *note assertNotIn(): cde. tests whether
     `first' is or is not in `second'.

   * ‘assertItemsEqual()’ tests whether two provided sequences contain
     the same elements.

   * *note assertSetEqual(): cdf. compares whether two sets are equal,
     and only reports the differences between the sets in case of error.

   * Similarly, *note assertListEqual(): ce0. and *note
     assertTupleEqual(): ce1. 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(): bba.  More generally, *note
     assertSequenceEqual(): ce2. compares two sequences and can
     optionally check whether both sequences are of a particular type.

   * *note assertDictEqual(): ce3. compares two dictionaries and reports
     the differences; it’s now used by default when you compare two
     dictionaries using *note assertEqual(): bba.
     ‘assertDictContainsSubset()’ checks whether all of the key/value
     pairs in `first' are found in `second'.

   * *note assertAlmostEqual(): bbc. and *note assertNotAlmostEqual():
     bbd. 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(): ce4. properly honors the *note
     suiteClass: ce5. attribute of the *note TestLoader: 787.  (Fixed by
     Mark Roddy; bpo-6866(12).)

   * A new hook lets you extend the *note assertEqual(): bba. method to
     handle new data types.  The *note addTypeEqualityFunc(): ce6.
     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(): 907. now takes an optional ‘exit’ argument.  If
false, *note main(): 907. doesn’t call *note sys.exit(): ce7, allowing
*note main(): 907. to be used from the interactive interpreter.
(Contributed by J. Pablo Fernández; bpo-3379(13).)

*note TestResult: ac4. has new *note startTestRun(): ce8. and *note
stopTestRun(): ce9. methods that are called immediately before and after
a test run.  (Contributed by Robert Collins; bpo-5728(14).)

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.

也參考
......

‘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) http://pytest.org

   (2) https://nose.readthedocs.io/

   (3) https://bugs.python.org/issue6001

   (4) https://bugs.python.org/issue8074

   (5) https://bugs.python.org/issue1034053

   (6) https://bugs.python.org/issue5663

   (7) https://bugs.python.org/issue4444

   (8) https://bugs.python.org/issue5679

   (9) https://bugs.python.org/issue2578

   (10) https://bugs.python.org/issue7031

   (11) https://bugs.python.org/issue8038

   (12) https://bugs.python.org/issue6866

   (13) https://bugs.python.org/issue3379

   (14) https://bugs.python.org/issue5728


File: python.info,  Node: Updated module ElementTree 1 3,  Prev: Updated module unittest,  Up: New and Improved Modules

1.10.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: 253. 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 ‘ParseError’ 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(): 91d. 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
     ‘tag’ 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(): b55.  In XML
     mode, you can use the true/false `xml_declaration' parameter to
     suppress the XML declaration.

   * New *note Element: ac9. method: *note extend(): b56. 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 ‘Element’ method: *note iter(): cec. 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 ‘Element’ method: *note itertext(): b58. 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: 32a.  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
‘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/issue6472


File: python.info,  Node: Build and C API Changes<8>,  Next: Other Changes and Fixes,  Prev: New and Improved Modules,  Up: What's New in Python 2 7

1.10.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(): cee. 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(): cef. 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 *note PyCode_New(): 273, which had many
     more arguments.  (Added by Jeffrey Yasskin.)

   * New function: *note PyErr_NewExceptionWithDoc(): c04. creates a new
     exception class, just as the existing *note PyErr_NewException():
     c05. 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(): cf0. 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(): c02. and *note
     PyLong_AsLongLongAndOverflow(): c01. 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(): c28. function was
     added.  The old ‘PyOS_ascii_strtod()’ and ‘PyOS_ascii_atof()’
     functions are now deprecated.

   * New function: *note PySys_SetArgvEx(): bff. 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, *note PySys_SetArgv(): cf1,
     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 *note PySys_SetArgv(): cf1. and carefully
     consider whether the application should be using *note
     PySys_SetArgvEx(): bff. 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 ‘PyFormat_FromString()’,
     ‘PyFormat_FromStringV()’, and *note PyErr_Format(): 7af. 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(): 966. might fail because the child is created with only a
     single thread running, the thread performing the *note os.fork():
     966.  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(): 966, and will also clean up any locks created using the
     *note threading: 10a. 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(): cf2. 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: 42b. 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: 2b. 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 ‘pyexpat’ 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://sourceware.org/gdb/current/onlinedocs/gdb/Python.html

   (2) https://bugs.python.org/issue8032

   (3) https://bugs.python.org/issue3632

   (4) https://bugs.python.org/issue4293

   (5) https://bugs.python.org/issue7033

   (6) https://bugs.python.org/issue7528

   (7) https://bugs.python.org/issue7767

   (8) https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5983

   (9) https://bugs.python.org/issue5753

   (10) https://bugs.python.org/issue5793

   (11) https://bugs.python.org/issue8276

   (12) https://bugs.python.org/issue7228

   (13) https://bugs.python.org/issue1590864

   (14) https://bugs.python.org/issue1722344

   (15) https://bugs.python.org/issue3102

   (16) https://bugs.python.org/issue7609

   (17) https://bugs.python.org/issue2422

   (18) https://bugs.python.org/issue6491

   (19) https://bugs.python.org/issue2937

   (20) https://bugs.python.org/issue1222585

   (21) https://bugs.python.org/issue3585

   (22) https://bugs.python.org/issue6094


File: python.info,  Node: Capsules,  Next: Port-Specific Changes Windows,  Up: Build and C API Changes<8>

1.10.12.1 Capsules
..................

Python 3.1 adds a new C datatype, *note PyCapsule: c0c, 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: f0. module’s API is exposed as ‘socket.CAPI’,
and *note unicodedata: 11b. 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(): cf5. would
detect the mismatched name and return false.  Refer to *note Providing a
C API for an Extension Module: cf6. 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
‘CObject’ interface.  Use of ‘PyCObject_AsVoidPtr()’ will signal a *note
PendingDeprecationWarning: 27a, 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/issue5630


File: python.info,  Node: Port-Specific Changes Windows,  Next: Port-Specific Changes Mac OS X,  Prev: Capsules,  Up: Build and C API Changes<8>

1.10.12.2 Port-Specific Changes: Windows
........................................

   * The *note msvcrt: b7. module now contains some constants from the
     ‘crtassem.h’ header file: ‘CRT_ASSEMBLY_VERSION’,
     ‘VC_ASSEMBLY_PUBLICKEYTOKEN’, and ‘LIBRARIES_ASSEMBLY_NAME_PREFIX’.
     (Contributed by David Cournapeau; bpo-4365(1).)

   * The ‘_winreg’ module for accessing the registry now implements the
     ‘CreateKeyEx()’ and ‘DeleteKeyEx()’ functions, extended versions of
     previously-supported functions that take several extra arguments.
     The ‘DisableReflectionKey()’, ‘EnableReflectionKey()’, and
     ‘QueryReflectionKey()’ 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(): cf8. function now works on Windows.  The
     signal value can be the constants ‘CTRL_C_EVENT’,
     ‘CTRL_BREAK_EVENT’, 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(): a46. function now correctly fails for an
     empty path.  (Fixed by Hirokazu Yamamoto; bpo-5913(5).)

   * The ‘mimelib’ 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/issue4365

   (2) https://bugs.python.org/issue7347

   (3) https://bugs.python.org/issue3582

   (4) https://bugs.python.org/issue1220212

   (5) https://bugs.python.org/issue5913

   (6) https://bugs.python.org/issue4969


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<8>

1.10.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/issue4865

   (2) https://bugs.python.org/issue28440


File: python.info,  Node: Port-Specific Changes FreeBSD,  Prev: Port-Specific Changes Mac OS X,  Up: Build and C API Changes<8>

1.10.12.4 Port-Specific Changes: FreeBSD
........................................

   * FreeBSD 7.1’s ‘SO_SETFIB’ constant, used with
     ‘getsockopt()’/‘setsockopt()’ to select an alternate routing table,
     is now available in the *note socket: f0. module.  (Added by Kyle
     VanderBeek; bpo-8235(1).)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue8235


File: python.info,  Node: Other Changes and Fixes,  Next: Porting to Python 2 7,  Prev: Build and C API Changes<8>,  Up: What's New in Python 2 7

1.10.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(): 4f5. 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 ‘co_filename’ 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/issue5464

   (2) https://bugs.python.org/issue1180193

   (3) https://bugs.python.org/issue6152

   (4) https://bugs.python.org/issue7312

   (5) https://bugs.python.org/issue8233


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: What's New in Python 2 7

1.10.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(): 9c3. function processes its arguments more
     consistently; it will now call *note __int__(): 18c. on non-float,
     non-integer arguments that are supplied to it.  (Fixed by Alexander
     Belopolsky; bpo-1533(1).)

   * The string *note format(): 4e0. 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(): 335.  (Changed by Eric Smith; bpo-5920(2).)

   * Because of an optimization for the *note with: 6ee. statement, the
     special methods *note __enter__(): c9a. and *note __exit__(): c9b.
     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: 2b1.) and C extension types.  (bpo-6101(3).)

   * Due to a bug in Python 2.6, the `exc_value' parameter to *note
     __exit__(): c9b. 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:
     3a0. as you would expect.  Fixed by Benjamin Peterson;
     bpo-7604(5).)

In the standard library:

   * Operations with *note datetime: 195. instances that resulted in a
     year falling outside the supported range didn’t always raise *note
     OverflowError: 965.  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: 189. instances with a string’s *note
     format(): 4e0. 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: 9f0. 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 ElementTree library, ‘xml.etree’, 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 ‘StringIO’ objects now does nothing when
     a negative length is requested, as other file-like objects do.
     (bpo-7348(10)).

   * The *note syslog: 100. 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: 102. 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 ‘urlparse’ module’s ‘urlsplit()’ 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: 193.
     exception instead of triggering a *note DeprecationWarning: 279.
     (bpo-5080(14)).

   * Use the new *note PyOS_string_to_double(): c28. function instead of
     the old ‘PyOS_ascii_strtod()’ and ‘PyOS_ascii_atof()’ functions,
     which are now deprecated.

For applications that embed Python:

   * The *note PySys_SetArgvEx(): bff. function was added, letting
     applications close a security hole when the existing *note
     PySys_SetArgv(): cf1. function was used.  Check whether you’re
     calling *note PySys_SetArgv(): cf1. and carefully consider whether
     the application should be using *note PySys_SetArgvEx(): bff. with
     `updatepath' set to false.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue1533

   (2) https://bugs.python.org/issue5920

   (3) https://bugs.python.org/issue6101

   (4) https://bugs.python.org/issue7853

   (5) https://bugs.python.org/issue7604

   (6) https://bugs.python.org/issue7150

   (7) https://bugs.python.org/issue6857

   (8) https://bugs.python.org/issue7279

   (9) https://bugs.python.org/issue2746

   (10) https://bugs.python.org/issue7348

   (11) https://bugs.python.org/issue8451

   (12) https://bugs.python.org/issue7357

   (13) https://tools.ietf.org/html/rfc3986.html

   (14) https://bugs.python.org/issue5080


File: python.info,  Node: New Features Added to Python 2 7 Maintenance Releases,  Next: Acknowledgements,  Prev: Porting to Python 2 7,  Up: What's New in Python 2 7

1.10.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.10.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/issue31733

   (2) https://bugs.python.org/issue31692


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.10.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://www.python.org/dev/peps/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.10.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(): a11. 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(): 7eb. 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)

PEP 466(8) related features added in Python 2.7.9:

   * Most of Python 3.4’s *note ssl: f4. module was backported.  This
     means *note ssl: f4. now supports Server Name Indication, TLS1.x
     settings, access to the platform certificate store, the *note
     SSLContext: 3e9. class, and other features.  (Contributed by Alex
     Gaynor and David Reid; bpo-21308(9).)

     Refer to the "Version added: 2.7.9" notes in the module
     documentation for specific details.

   * *note os.urandom(): 4d6. was changed to cache a file descriptor to
     ‘/dev/urandom’ instead of reopening ‘/dev/urandom’ on every call.
     (Contributed by Alex Gaynor; bpo-21305(10).)

   * *note hashlib.algorithms_guaranteed: d01. and *note
     hashlib.algorithms_available: d02. 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(11))

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0466

   (2) https://www.python.org/dev/peps/pep-0466

   (3) https://bugs.python.org/issue21306

   (4) https://bugs.python.org/issue21462

   (5) https://www.python.org/dev/peps/pep-0466

   (6) https://bugs.python.org/issue21304

   (7) https://bugs.python.org/issue21671

   (8) https://www.python.org/dev/peps/pep-0466

   (9) https://bugs.python.org/issue21308

   (10) https://bugs.python.org/issue21305

   (11) https://bugs.python.org/issue21307


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.10.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://www.python.org/dev/peps/pep-0477

   (2) https://www.python.org/dev/peps/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.10.15.5 Bootstrapping pip By Default
......................................

The new *note ensurepip: 7a. 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: 7f8, 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://www.python.org/dev/peps/pep-0453

   (2) 
https://www.python.org/dev/peps/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.10.15.6 Documentation Changes
...............................

As part of this change, the *note 安裝 Python 模組: 7fa. and *note 發布
Python 模組: 7fb. 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 安裝 Python
模組（舊版）: 7fc. and *note 發布 Python 模組（舊版）: 7fd.

也參考
......

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) http://packaging.python.org

   (2) https://www.python.org/dev/peps/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.10.15.7 PEP 476: Enabling certificate verification by default for stdlib http clients
.......................................................................................

PEP 476(1) updated ‘httplib’ and modules which use it, such as ‘urllib2’
and ‘xmlrpclib’, 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://www.python.org/dev/peps/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.10.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://www.python.org/dev/peps/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.10.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.

(Contributed by Victor Stinner in bpo-23404(2).)

2.7.14 版新加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Makefile.pre.in

   (2) https://bugs.python.org/issue23404


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.10.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.

(Contributed by Victor Stinner in bpo-23404(1).)

2.7.14 版更變.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23404


File: python.info,  Node: Acknowledgements,  Prev: New Features Added to Python 2 7 Maintenance Releases,  Up: What's New in Python 2 7

1.10.16 Acknowledgements
------------------------

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: What's New in Python 2 6,  Next: What's New in Python 2 5,  Prev: What's New in Python 2 7,  Up: Python 有什麼新功能？

1.11 What’s New in Python 2.6
=============================


Author: 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: b8. and *note json: a5. 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; Revised Buffer Protocol: PEP 3118 Revised Buffer Protocol.
* 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.
* Other Language Changes: Other Language Changes<10>.
* New and Improved Modules: New and Improved Modules<2>.
* Deprecations and Removals::
* Build and C API Changes: Build and C API Changes<9>.
* Porting to Python 2.6: Porting to Python 2 6.
* Acknowledgements: Acknowledgements<2>.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0361


File: python.info,  Node: Python 3 0,  Next: Changes to the Development Process,  Up: What's New in Python 2 6

1.11.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 *note __complex__(): 18e. method for converting objects to a
     complex number.

   * Alternate syntax for catching exceptions: ‘except TypeError as
     exc’.

   * The addition of *note functools.reduce(): c74. 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(): c45. 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 3xxx 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://www.python.org/dev/peps/pep-3000

   (2) https://www.python.org/dev/peps/pep-3100


File: python.info,  Node: Changes to the Development Process,  Next: PEP 343 The 'with' statement,  Prev: Python 3 0,  Up: What's New in Python 2 6

1.11.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.11.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
‘http://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.

‘http://bugs.jython.org’:

     The Jython bug tracker.

‘http://roundup.sourceforge.net/’

     Roundup downloads and documentation.

‘http://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) http://roundup.sourceforge.net/

   (4) https://trac.edgewall.org/

   (5) http://www.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.11.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
‘http://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) http://sphinx-doc.org/

   (4) http://docutils.sourceforge.net


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: What's New in Python 2 6

1.11.3 PEP 343: The ’with’ statement
------------------------------------

The previous version, Python 2.5, added the ’*note with: 6ee.’ 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: 6ee.’ 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: 6ee.’ 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__(): c9a. and *note __exit__(): c9b. methods).

The object’s *note __enter__(): c9a. 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__(): c9b. 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: 6ee.’ 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: c35. loop raised an
exception part-way through the block.

     備註: In this case, `f' is the same object created by *note open():
     4f5, because ‘file.__enter__()’ returns `self'.

The *note threading: 10a. module’s locks and condition variables also
support the ’*note with: 6ee.’ 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: 36. 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::
* The contextlib module::


File: python.info,  Node: Writing Context Managers,  Next: The contextlib module,  Up: PEP 343 The 'with' statement

1.11.3.1 Writing Context Managers
.................................

Under the hood, the ’*note with: 6ee.’ 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__(): c9a. and *note __exit__(): c9b. methods.

   * The context manager’s *note __enter__(): c9a. 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__(): c9b. method is called with three arguments, the
     exception details (‘type, value, traceback’, the same values
     returned by *note sys.exc_info(): c64, 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: 6ee.’ statement will never realize
     anything went wrong.

   * If `BLOCK' didn’t raise an exception, the *note __exit__(): c9b.
     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__(): c9a. 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: 6ee.’ 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__(): c9b. 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: 191. 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: The contextlib module,  Prev: Writing Context Managers,  Up: PEP 343 The 'with' statement

1.11.3.2 The contextlib module
..............................

The *note contextlib: 24. module provides some functions and a decorator
that are useful when writing objects for use with the ’*note with: 6ee.’
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: 190.
will be executed as the *note __enter__(): c9a. method, and the value
yielded will be the method’s return value that will get bound to the
variable in the ’*note with: 6ee.’ statement’s ‘as’ clause, if any.  The
code after the ‘yield’ will be executed in the *note __exit__(): c9b.
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: 24. 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: 6ee.’ 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: 6ee.’ statement, which can be
     helpful in learning how the statement works.

The documentation for the *note contextlib: 24. module.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: What's New in Python 2 6

1.11.4 PEP 366: Explicit Relative Imports From a Main Module
------------------------------------------------------------

Python’s *note -m: 33c. 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__: 95a. attribute to
modules.  When this attribute is present, relative imports will be
relative to the value of this attribute instead of the *note __name__:
d17. attribute.

PEP 302-style importers can then set *note __package__: 95a. as
necessary.  The *note runpy: e3. module that implements the *note -m:
33c. 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: What's New in Python 2 6

1.11.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: d19. 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: d1a. option or setting the *note PYTHONNOUSERSITE: d1b. environment
variable.

也參考
......

PEP 370(1) - Per-user ‘site-packages’ Directory

     PEP written and implemented by Christian Heimes.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: What's New in Python 2 6

1.11.6 PEP 371: The ‘multiprocessing’ Package
---------------------------------------------

The new *note multiprocessing: b8. 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: b8. module started out as an exact emulation
of the *note threading: 10a. 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: d1d. is used to communicate the result of the factorial.
The *note Queue: d1d. 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: d1d, 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(): c32. 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(): 1b9. 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...

也參考
......

The documentation for the *note multiprocessing: b8. module.

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://www.python.org/dev/peps/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: What's New in Python 2 6

1.11.7 PEP 3101: Advanced String Formatting
-------------------------------------------

In Python 3.0, the ‘%’ operator is supplemented by a more powerful
string formatting method, *note format(): 4e0.  Support for the *note
str.format(): 4df. 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: d1f.; 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 *note __format__(): 953. 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(): 4e0. builtin that will format a single
value.  It calls the type’s *note __format__(): 953. method with the
provided specifier:

     >>> format(75.6564, '.2f')
     '75.66'

也參考
......

*note Format String Syntax: d1f.

     The reference documentation for format fields.

PEP 3101(1) - Advanced String Formatting

     PEP written by Talin.  Implemented by Eric Smith.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: What's New in Python 2 6

1.11.8 PEP 3105: ‘print’ As a Function
--------------------------------------

The ‘print’ statement becomes the *note print(): 88b. function in Python
3.0.  Making *note print(): 88b. 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

     PEP written by Georg Brandl.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3105


File: python.info,  Node: PEP 3110 Exception-Handling Changes,  Next: PEP 3112 Byte Literals,  Prev: PEP 3105 print As a Function,  Up: What's New in Python 2 6

1.11.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: 193. and
*note ValueError: 1fc. exceptions, but this code actually does something
different: it will catch *note TypeError: 193. and bind the resulting
exception object to the local name ‘"ValueError"’.  The *note
ValueError: 1fc. 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

     PEP written and implemented by Collin Winter.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3110


File: python.info,  Node: PEP 3112 Byte Literals,  Next: PEP 3116 New I/O Library,  Prev: PEP 3110 Exception-Handling Changes,  Up: What's New in Python 2 6

1.11.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: 336. constructor.  For future compatibility, Python 2.6
adds *note bytes: 336. as a synonym for the *note str: 335. type, and it
also supports the ‘b''’ notation.

The 2.6 *note str: 335. differs from 3.0’s *note bytes: 336. 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(): 335. of the list.

The primary use of *note bytes: 336. 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:
336. or *note str: 335. 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: d23.
Python 2.6 uses ‘#define’ to support using the names *note
PyBytesObject(): d23, *note PyBytes_Check(): d24, *note
PyBytes_FromStringAndSize(): d25, and all the other functions and macros
used with strings.

Instances of the *note bytes: 336. type are immutable just as strings
are.  A new *note bytearray: 337. 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():
d26, *note PyByteArray_FromStringAndSize(): d27, 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://www.python.org/dev/peps/pep-3112


File: python.info,  Node: PEP 3116 New I/O Library,  Next: PEP 3118 Revised Buffer Protocol,  Prev: PEP 3112 Byte Literals,  Up: What's New in Python 2 6

1.11.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(): df, for example.  Python 3.0 introduces a
layered I/O library in the *note io: a2. 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: a2. 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: 5f9.  ‘TextIOBase’ defines the *note
     readline(): df. 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: 832. 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: a2. 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: a2. 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://www.python.org/dev/peps/pep-3116


File: python.info,  Node: PEP 3118 Revised Buffer Protocol,  Next: PEP 3119 Abstract Base Classes,  Prev: PEP 3116 New I/O Library,  Up: What's New in Python 2 6

1.11.12 PEP 3118: Revised Buffer Protocol
-----------------------------------------

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: de. 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(): d2a. specifies
constraints upon the memory returned.  Some examples are:

        * ‘PyBUF_WRITABLE’ indicates that the memory must be writable.

        * ‘PyBUF_LOCK’ requests a read-only or exclusive lock on the
          memory.

        * ‘PyBUF_C_CONTIGUOUS’ and ‘PyBUF_F_CONTIGUOUS’ 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(): 26b, ‘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://www.python.org/dev/peps/pep-3118


File: python.info,  Node: PEP 3119 Abstract Base Classes,  Next: PEP 3127 Integer Literal Support and Syntax,  Prev: PEP 3118 Revised Buffer Protocol,  Up: What's New in Python 2 6

1.11.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(): 454. and *note issubclass(): 455.
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(): 26. and ‘update()’?  Iterating over the object with *note
iter(): d2c.?

The Python 2.6 *note collections: 1e. module includes a number of
different ABCs that represent these distinctions.  ‘Iterable’ indicates
that a class defines *note __iter__(): 514, and ‘Container’ means the
class defines a *note __contains__(): d2d. 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://www.python.org/dev/peps/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: What's New in Python 2 6

1.11.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(): c6a. builtin still returns numbers prefixed with a
leading zero, and a new *note bin(): c45. builtin returns the binary
representation for a number:

     >>> oct(42)
     '052'
     >>> future_builtins.oct(42)
     '0o52'
     >>> bin(173)
     '0b10101101'

The *note int(): 185. 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://www.python.org/dev/peps/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: What's New in Python 2 6

1.11.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

     PEP written by Collin Winter.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3129


File: python.info,  Node: PEP 3141 A Type Hierarchy for Numbers,  Next: Other Language Changes<10>,  Prev: PEP 3129 Class Decorators,  Up: What's New in Python 2 6

1.11.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: c2. 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:
83. module.  (It’s called ‘Fraction’ instead of ‘Rational’ to avoid a
name clash with *note numbers.Rational: c5d.)

‘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(): c72, *note math.floor(): d31, *note math.ceil(): d32, and adds
a new one, *note math.trunc(): d33, that’s been backported to Python
2.6.  *note math.trunc(): d33. rounds toward zero, returning the closest
‘Integral’ that’s between the function’s argument and zero.

也參考
......

PEP 3141(1) - A Type Hierarchy for Numbers

     PEP written by Jeffrey Yasskin.

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://www.python.org/dev/peps/pep-3141

   (2) 
https://www.gnu.org/software/guile/manual/html_node/Numerical-Tower.html#Numerical-Tower

   (3) 
http://schemers.org/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.11.16.1 The ‘fractions’ Module
................................

To fill out the hierarchy of numeric types, the *note fractions: 83.
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: 83. 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: Other Language Changes<10>,  Next: New and Improved Modules<2>,  Prev: PEP 3141 A Type Hierarchy for Numbers,  Up: What's New in Python 2 6

1.11.17 Other Language Changes
------------------------------

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(): 44c. function was catching and ignoring all
     errors, under the assumption that they meant a *note __getattr__():
     31f. method was failing somehow and the return value of *note
     hasattr(): 44c. would therefore be ‘False’.  This logic shouldn’t
     be applied to *note KeyboardInterrupt: 198. and *note SystemExit:
     601, however; Python 2.6 will no longer discard such exceptions
     when *note hasattr(): 44c. 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']

     (Contributed by 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: 48b. 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

     (Contributed by 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'])

     (Contributed by Raymond Hettinger.)

   * Many floating-point features were added.  The *note float(): 188.
     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: b2. 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(): c6b. 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(): 18a. constructor will now preserve the sign of the zero.
     (Fixed by Mark T. Dickinson; bpo-1507(9).)

   * Classes that inherit a *note __hash__(): 345. 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: 193.
     and the class will not be indicated as implementing the ‘Hashable’
     ABC.

     You should do this when you’ve defined a ‘__cmp__()’ or *note
     __eq__(): 344. 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
     *note __hash__(): 345. 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(): d36.  (Fixed by Nick Coghlan and
     Amaury Forgeot d’Arc; bpo-2235(10).)

   * The *note GeneratorExit: d37. exception now subclasses *note
     BaseException: 1a9. instead of *note Exception: 1aa.  This means
     that an exception handler that does ‘except Exception:’ will not
     inadvertently catch *note GeneratorExit: d37.  (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(): 1b5. built-in function now accepts keyword
     arguments as well as positional parameters.  (Contributed by Thomas
     Wouters; bpo-1444529(13).)

   * The *note complex(): 18a. 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(): d38. function now checks for a *note
     __dir__(): 320. 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(): d38. produces.  Objects that have *note
     __getattr__(): 31f. or *note __getattribute__(): 44e. 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
     ‘__self__’, and ‘im_func’ is also available as ‘__func__’.  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(): 45a. function
     inside a *note class: c6f. 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:

* Optimizations: Optimizations<9>.
* Interpreter Changes: Interpreter Changes<2>.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue1739468

   (2) https://bugs.python.org/issue2196

   (3) https://bugs.python.org/issue1686487

   (4) https://bugs.python.org/issue3473

   (5) https://bugs.python.org/issue2719

   (6) https://bugs.python.org/issue1635

   (7) https://bugs.python.org/issue1640

   (8) https://bugs.python.org/issue3008

   (9) https://bugs.python.org/issue1507

   (10) https://bugs.python.org/issue2235

   (11) https://bugs.python.org/issue1537

   (12) https://bugs.python.org/issue1473257

   (13) https://bugs.python.org/issue1444529

   (14) https://bugs.python.org/issue1491866

   (15) https://bugs.python.org/issue1193128

   (16) https://bugs.python.org/issue1591665


File: python.info,  Node: Optimizations<9>,  Next: Interpreter Changes<2>,  Up: Other Language Changes<10>

1.11.17.1 Optimizations
.......................

   * The *note warnings: 127. 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: f9. 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__(): c9b. 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/issue1631171

   (2) https://bugs.python.org/issue1700288

   (3) https://bugs.python.org/issue1878

   (4) https://bugs.python.org/issue1819


File: python.info,  Node: Interpreter Changes<2>,  Prev: Optimizations<9>,  Up: Other Language Changes<10>

1.11.17.2 Interpreter Changes
.............................

Two command-line options have been reserved for use by other Python
implementations.  The *note -J: d3c. switch has been reserved for use by
Jython for Jython-specific options, such as switches that are passed to
the underlying JVM. *note -X: 156. 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: d3d. switch to the Python interpreter, or by
setting the *note PYTHONDONTWRITEBYTECODE: d3e. 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: 934. 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: Other Language Changes<10>,  Up: What's New in Python 2 6

1.11.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 *note asyncore: b. and *note asynchat: 9. 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 *note cgi: 16. 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 *note cgi: 16. module to the ‘urlparse’ module.  The
     versions still available in the *note cgi: 16. module will trigger
     *note PendingDeprecationWarning: 27a. messages in 2.6
     (bpo-600362(4)).

   * The *note cmath: 19. 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: 19. 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: 19. 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: 1e. 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.

     (Contributed by Raymond Hettinger.)

   * Another change to the *note collections: 1e. 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)

     (Contributed by Raymond Hettinger.)

   * The ‘Cookie’ module’s ‘Morsel’ objects now support an ‘httponly’
     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: 2c. 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: 2f. 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: 31. 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: 36. 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: 37. 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: 2f1. 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: 85. module.  In Python 3.0, the builtin has been dropped
     and ‘reduce()’ is only available from *note functools: 85.;
     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: 88. 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(): 5cb. 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: 8e. 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: 8e. is now implemented to only use less-than
     comparison, instead of the less-than-or-equal comparison it
     previously used.  This makes *note heapq: 8e.’s usage of a type
     match the *note list.sort(): 44a. method.  (Contributed by Raymond
     Hettinger.)

   * An optional ‘timeout’ parameter, specifying a timeout measured in
     seconds, was added to the ‘httplib.HTTPConnection’ and
     ‘HTTPSConnection’ class constructors.  (Added by Facundo Batista.)

   * Most of the *note inspect: a1. 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: a4. 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: a4. 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: ab. 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: b2. module:

        * *note isinf(): d40. and *note isnan(): d41. determine whether
          a given float is a (positive or negative) infinity or a NaN
          (Not a Number), respectively.

        * *note copysign(): d42. 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(): 1eb. computes the factorial of a number.
          (Contributed by Raymond Hettinger; bpo-2138(12).)

        * *note fsum(): d43. 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(): d44, *note asinh(): d45. and *note atanh():
          d46. compute the inverse hyperbolic functions.

        * *note log1p(): d47. 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: c5c.

   * The *note math: b2. 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: 1fc. 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: 1fc.  Where Annex ’F’ of the C99 standard recommends
     signaling ’overflow’, Python will raise *note OverflowError: 965.
     (See bpo-711019(14) and bpo-1640(15).)

     (Contributed by Christian Heimes and Mark Dickinson.)

   * *note mmap: 1ed. 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: c3. 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'

     (Contributed by Georg Brandl, after a suggestion by Gregory
     Petrosyan.)

     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'

     (Contributed by Georg Brandl, after a suggestion by Barry Warsaw.)

   * The *note os: c5. 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:
     f5. 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: fa.
     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(): d48. in addition
     to clearing the object’s keys.  (Contributed by Martin Horcicka;
     bpo-1181(17).)

   * The *note os.walk(): 659. 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: c6. 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(): d49. 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: ca. 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(): d4a. function, used to begin debugging
     a traceback, will now use the traceback returned by *note
     sys.exc_info(): c64. if no traceback is supplied.  (Contributed by
     Facundo Batista; bpo-1106316(23).)

   * The *note pickletools: cc. 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: ce. 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
           ...

     (Contributed by 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: dd. 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: de.
     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: e2. module’s ‘Completer.complete()’ method
     will now ignore exceptions triggered while evaluating a name.
     (Fixed by Lorenz Quack; bpo-2250(30).)

   * The *note sched: e4. module’s ‘scheduler’ instances now have a
     read-only *note queue: db. 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: e6. 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(): 21b. 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: ea. 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'))

     (Contributed by 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: eb.
     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(): d4b,
     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.

     (Contributed by 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: ee. 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: f0. module now supports TIPC
     (‘http://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 ‘SocketServer’ module now support calling a
     ‘handle_timeout()’ method after a span of inactivity specified by
     the server’s ‘timeout’ attribute.  (Contributed by Michael
     Pomraning.)  The ‘serve_forever()’ 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: f3. 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: f9. module now supports the C99 ‘_Bool’ type,
     using the format character ‘'?'’.  (Contributed by David Remahl.)

   * The ‘Popen’ objects provided by the *note subprocess: fa. module
     now have ‘terminate()’, ‘kill()’, and ‘send_signal()’ methods.  On
     Windows, ‘send_signal()’ only supports the ‘SIGTERM’ signal, and
     all these methods are aliases for the Win32 API function
     ‘TerminateProcess()’.  (Contributed by Christian Heimes.)

   * A new variable in the *note sys: fe. 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:
     d3d. switch to the Python interpreter, or by setting the *note
     PYTHONDONTWRITEBYTECODE: d3e. 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(): d4c. and *note
     sys.gettrace(): d4d.  (Contributed by Georg Brandl; bpo-1648(45).)

   * The *note tarfile: 102. 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 *note
     telnetlib.Telnet: 59c. class constructor, specifying a timeout
     measured in seconds.  (Added by Facundo Batista.)

   * The *note tempfile.NamedTemporaryFile: d4e. 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 ‘test.test_support’ module gained a number of context managers
     useful for writing tests.  ‘EnvironmentVarGuard()’ 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"

     (Contributed by Brett Cannon.)

   * The *note textwrap: 109. 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.
          >>>

     (Contributed by Dwayne Bailey; bpo-1581073(49).)

   * The *note threading: 10a. 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: 10a. 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: 10c. 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: 117. 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 ‘urllib.urlopen()’
     function and the ‘urllib.ftpwrapper’ class constructor, as well as
     the ‘urllib2.urlopen()’ 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: 11b. module
     has been updated to version 5.1.0.  (Updated by Martin von Löwis;
     bpo-3811(54).)

   * The *note warnings: 127. 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:
     127. 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 ‘SimpleXMLRPCServer’ and ‘DocXMLRPCServer’ 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 ‘xmlrpclib’ module no longer automatically converts *note
     datetime.date: 194. and *note datetime.time: 4f8. to the
     ‘xmlrpclib.DateTime’ type; the conversion semantics were not
     necessarily correct for all applications.  Code using ‘xmlrpclib’
     should convert ‘date’ and *note time: 4f8. 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: 143. 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()

     (Contributed by Alan McIntyre; bpo-467924(61).)

     The *note open(): 4f5, ‘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: 143. now supports using Unicode filenames
     for archived files.  (Contributed by Alexey Borzenkov;
     bpo-1734346(63).)

* Menu:

* The ast module::
* The future_builtins module::
* 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/issue1736190

   (2) https://www.jcea.es/programacion/pybsddb.htm

   (3) https://bugs.python.org/issue1817

   (4) https://bugs.python.org/issue600362

   (5) https://bugs.python.org/issue1381

   (6) https://bugs.python.org/issue1638033

   (7) https://bugs.python.org/issue1158

   (8) http://speleotrove.com/decimal/decarith.html

   (9) https://bugs.python.org/issue1221598

   (10) https://bugs.python.org/issue1739906

   (11) https://bugs.python.org/issue1001604

   (12) https://bugs.python.org/issue2138

   (13) https://bugs.python.org/issue2819

   (14) https://bugs.python.org/issue711019

   (15) https://bugs.python.org/issue1640

   (16) https://bugs.python.org/issue1663329

   (17) https://bugs.python.org/issue1181

   (18) https://bugs.python.org/issue1273829

   (19) https://bugs.python.org/issue1115886

   (20) https://bugs.python.org/issue1339796

   (21) https://bugs.python.org/issue957650

   (22) https://bugs.python.org/issue1393667

   (23) https://bugs.python.org/issue1106316

   (24) https://bugs.python.org/issue2439

   (25) https://bugs.python.org/issue1137

   (26) https://bugs.python.org/issue1727780

   (27) https://bugs.python.org/issue1681432

   (28) https://bugs.python.org/issue846388

   (29) https://bugs.python.org/issue3487

   (30) https://bugs.python.org/issue2250

   (31) https://bugs.python.org/issue1861

   (32) https://bugs.python.org/issue1657

   (33) https://bugs.python.org/issue2663

   (34) https://bugs.python.org/issue1583

   (35) https://bugs.python.org/issue2240

   (36) https://tools.ietf.org/html/rfc2033.html

   (37) https://bugs.python.org/issue957003

   (38) https://tools.ietf.org/html/rfc3207.html

   (39) https://bugs.python.org/issue829951

   (40) https://bugs.python.org/issue1646

   (41) https://bugs.python.org/issue742598

   (42) https://bugs.python.org/issue1193577

   (43) https://bugs.python.org/issue1534

   (44) https://bugs.python.org/issue2898

   (45) https://bugs.python.org/issue1648

   (46) https://bugs.python.org/issue1537850

   (47) https://bugs.python.org/issue2021

   (48) https://bugs.python.org/issue3781

   (49) https://bugs.python.org/issue1581073

   (50) https://bugs.python.org/issue2871

   (51) https://bugs.python.org/issue1533909

   (52) https://bugs.python.org/issue2906

   (53) https://bugs.python.org/issue1513695

   (54) https://bugs.python.org/issue3811

   (55) https://bugs.python.org/issue1631171

   (56) https://bugs.python.org/issue3781

   (57) https://bugs.python.org/issue1599845

   (58) https://bugs.python.org/issue1330538

   (59) https://bugs.python.org/issue2014

   (60) https://bugs.python.org/issue2985

   (61) https://bugs.python.org/issue467924

   (62) https://bugs.python.org/issue1775025

   (63) https://bugs.python.org/issue1734346


File: python.info,  Node: The ast module,  Next: The future_builtins module,  Up: New and Improved Modules<2>

1.11.18.1 The ‘ast’ module
..........................

The *note ast: 8. 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(): b95. 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: The future_builtins module,  Next: The json module JavaScript Object Notation,  Prev: The ast module,  Up: New and Improved Modules<2>

1.11.18.2 The ‘future_builtins’ module
......................................

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(): 7d1.  In Python 3.0,
     *note repr(): 7d1. will return a Unicode string, while *note
     ascii(): d51. 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 *note
     __index__(): 18b. method and convert the result to hexadecimal or
     octal.  *note oct(): c6a. 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: The future_builtins module,  Up: New and Improved Modules<2>

1.11.18.3 The ‘json’ module: JavaScript Object Notation
.......................................................

The new *note json: a5. 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: a5. 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: a5. (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.11.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: d0. 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.11.18.5 ctypes Enhancements
.............................

Thomas Heller continued to maintain and enhance the *note ctypes: 2b.
module.

*note ctypes: 2b. now supports a ‘c_bool’ datatype that represents the
C99 ‘bool’ type.  (Contributed by David Remahl; bpo-1649190(1).)

The *note ctypes: 2b. 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: 2b. 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: 2b. 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/issue1649190

   (2) https://bugs.python.org/issue1798


File: python.info,  Node: Improved SSL Support,  Prev: ctypes Enhancements,  Up: New and Improved Modules<2>

1.11.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: f4, 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: f0. 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 *note ssl.wrap_socket(): 474.
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: f4. module.

   ---------- Footnotes ----------

   (1) https://www.openssl.org/


File: python.info,  Node: Deprecations and Removals,  Next: Build and C API Changes<9>,  Prev: New and Improved Modules<2>,  Up: What's New in Python 2 6

1.11.19 Deprecations and Removals
---------------------------------

   * String exceptions have been removed.  Attempting to use them raises
     a *note TypeError: 193.

   * Changes to the *note Exception: 1aa. interface as dictated by PEP
     352(1) continue to be made.  For 2.6, the ‘message’ attribute is
     being deprecated in favor of the ‘args’ 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: 69. package instead.

   * The ‘md5’ module has been deprecated; use the *note hashlib: 8d.
     module instead.

   * The ‘posixfile’ module has been deprecated; *note fcntl.lockf():
     d57. provides better locking.

   * The ‘popen2’ module has been deprecated; use the *note subprocess:
     fa. module.

   * The ‘rgbimg’ module has been removed.

   * The ‘sets’ module has been deprecated; it’s better to use the
     built-in *note set: b74. and *note frozenset: bf3. types.

   * The ‘sha’ module has been deprecated; use the *note hashlib: 8d.
     module instead.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0352


File: python.info,  Node: Build and C API Changes<9>,  Next: Porting to Python 2 6,  Prev: Deprecations and Removals,  Up: What's New in Python 2 6

1.11.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.)

   * 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: d29, adds *note PyObject_GetBuffer(): d2a. and *note
     PyBuffer_Release(): d59, 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: 339.  A new API
     function, *note PyImport_ImportModuleNoBlock(): 9c6, 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: 339. is raised.  (Contributed by
     Christian Heimes.)

   * Several functions return information about the platform’s
     floating-point support.  *note PyFloat_GetMax(): d5a. returns the
     maximum representable floating point value, and *note
     PyFloat_GetMin(): d5b. returns the minimum positive value.  *note
     PyFloat_GetInfo(): d5c. 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(1).)

   * C functions and methods that use *note PyComplex_AsCComplex(): d5d.
     will now accept arguments that have a *note __complex__(): 18e.
     method.  In particular, the functions in the *note cmath: 19.
     module will now accept objects with this method.  This is a
     backport of a Python 3.0 change.  (Contributed by Mark Dickinson;
     bpo-1675423(2).)

   * 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(3).)

   * 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: d5e. and
     ‘PyModule_AddIntMacro()’.  (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
     ‘Py_SIZE()’, ‘Py_Type()’ became ‘Py_TYPE()’, and ‘Py_Refcnt()’
     became ‘Py_REFCNT()’.  The mixed-case macros are still available in
     Python 2.6 for backward compatibility.  (bpo-1629(4))

   * 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(5).)

   * 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://bugs.python.org/issue1534

   (2) https://bugs.python.org/issue1675423

   (3) https://bugs.python.org/issue1635

   (4) https://bugs.python.org/issue1629

   (5) https://bugs.python.org/issue1530959


File: python.info,  Node: Port-Specific Changes Windows<2>,  Next: Port-Specific Changes Mac OS X<2>,  Up: Build and C API Changes<9>

1.11.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: b7. module now supports both the normal and wide
     char variants of the console I/O API. The ‘getwch()’ function reads
     a keypress and returns a Unicode value, as does the ‘getwche()’
     function.  The ‘putwch()’ function takes a Unicode character and
     writes it to the console.  (Contributed by Christian Heimes.)

   * *note os.path.expandvars(): d49. 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: f0. module’s socket objects now have an ‘ioctl()’
     method that provides a limited interface to the ‘WSAIoctl()’ system
     interface.

   * The ‘_winreg’ module now has a function,
     ‘ExpandEnvironmentStrings()’, 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: 6ee. statements.  (Contributed by
     Christian Heimes.)

     ‘_winreg’ also has better support for x64 systems, exposing the
     ‘DisableReflectionKey()’, ‘EnableReflectionKey()’, and
     ‘QueryReflectionKey()’ functions, which enable and disable registry
     reflection for 32-bit processes running on 64-bit systems.
     (bpo-1753245(2))

   * The *note msilib: b6. 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/issue957650

   (2) https://bugs.python.org/issue1753245

   (3) https://bugs.python.org/issue2125


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<9>

1.11.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/issue1490190


File: python.info,  Node: Port-Specific Changes IRIX,  Prev: Port-Specific Changes Mac OS X<2>,  Up: Build and C API Changes<9>

1.11.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: Acknowledgements<2>,  Prev: Build and C API Changes<9>,  Up: What's New in Python 2 6

1.11.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: 193.

   * The *note __init__(): d63. method of *note collections.deque: 536.
     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__(): d63. 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:
     193.  This will affect *note __init__(): d63. methods that end up
     calling the corresponding method on *note object: 2b1. (perhaps
     through using *note super(): 4e7.).  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__(): 615. 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: 339.

   * C API: the *note PyImport_Import(): d64. and *note
     PyImport_ImportModule(): c78. 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():
     d36.

   * The *note socket: f0. module exception *note socket.error: 99a. now
     inherits from *note IOError: 997.  Previously it wasn’t a subclass
     of ‘StandardError’ but now it is, through *note IOError: 997.
     (Implemented by Gregory P. Smith; bpo-1706815(2).)

   * The ‘xmlrpclib’ module no longer automatically converts *note
     datetime.date: 194. and *note datetime.time: 4f8. to the
     ‘xmlrpclib.DateTime’ type; the conversion semantics were not
     necessarily correct for all applications.  Code using ‘xmlrpclib’
     should convert ‘date’ and *note time: 4f8. instances.
     (bpo-1330538(3))

   * (3.0-warning mode) The *note Exception: 1aa. class now warns when
     accessed using slicing or index access; having *note Exception:
     1aa. 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue1683368

   (2) https://bugs.python.org/issue1706815

   (3) https://bugs.python.org/issue1330538


File: python.info,  Node: Acknowledgements<2>,  Prev: Porting to Python 2 6,  Up: What's New in Python 2 6

1.11.22 Acknowledgements
------------------------

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: What's New in Python 2 5,  Next: What's New in Python 2 4,  Prev: What's New in Python 2 6,  Up: Python 有什麼新功能？

1.12 What’s New in Python 2.5
=============================


Author: 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.

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: 2b. 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: d69.  The new ’*note with: 6ee.’ statement will make
writing cleanup code easier (section *note PEP 343; The ’with’
statement: d6a.).  Values can now be passed into generators (section
*note PEP 342; New Generator Features: d6b.).  Imports are now visible
as either absolute or relative (section *note PEP 328; Absolute and
Relative Imports: d6c.).  Some corner cases of exception handling are
handled better (section *note PEP 341; Unified try/except/finally:
d6d.).  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; The ’with’ statement: PEP 343 The 'with' statement<2>.
* 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.
* Other Language Changes: Other Language Changes<11>.
* New, Improved, and Removed Modules: New Improved and Removed Modules.
* Build and C API Changes: Build and C API Changes<10>.
* Porting to Python 2.5: Porting to Python 2 5.
* Acknowledgements: Acknowledgements<3>.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0356


File: python.info,  Node: PEP 308 Conditional Expressions,  Next: PEP 309 Partial Function Application,  Up: What's New in Python 2 5

1.12.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://www.python.org/dev/peps/pep-0308

   (2) https://www.python.org/dev/peps/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: What's New in Python 2 5

1.12.2 PEP 309: Partial Function Application
--------------------------------------------

The *note functools: 85. 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: 85. 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://www.python.org/dev/peps/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: What's New in Python 2 5

1.12.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://www.python.org/dev/peps/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: What's New in Python 2 5

1.12.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: f7. 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: f7.
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: c22.’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: f7. 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                 # Imports A.B.D
     from .. import E                # Imports A.E
     from ..F import G               # Imports 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

     PEP written by Aahz; implemented by Thomas Wouters.

‘https://pylib.readthedocs.io/’

     The py library by Holger Krekel, which contains the ‘py.std’
     package.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0328

   (2) https://www.python.org/dev/peps/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: What's New in Python 2 5

1.12.5 PEP 338: Executing Modules as Scripts
--------------------------------------------

The *note -m: 33c. 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: e3.

The *note runpy: e3. 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: 144. module.  This means you can
add a .zip archive’s path to ‘sys.path’ and then use the *note -m: 33c.
switch to execute code from the archive.

也參考
......

PEP 338(1) - Executing modules as scripts

     PEP written and implemented by Nick Coghlan.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: What's New in Python 2 5

1.12.6 PEP 341: Unified try/except/finally
------------------------------------------

Until Python 2.5, the *note try: d77. statement came in two flavours.
You could use a *note finally: 183. block to ensure that code is always
executed, or one or more *note except: b43. 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: b43. blocks and a *note
finally: 183. 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: b43. 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

     PEP written by Georg Brandl; implementation by Thomas Lee.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0341


File: python.info,  Node: PEP 342 New Generator Features,  Next: PEP 343 The 'with' statement<2>,  Prev: PEP 341 Unified try/except/finally,  Up: What's New in Python 2 5

1.12.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: 190. 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(): 687. method, picking up
after the ‘yield’ statement.

In Python 2.3, *note yield: 190. 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: 190.
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:
190.-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: 190.
expression returns the specified `value'.  If the regular *note next():
687. method is called, the ‘yield’ returns *note None: 158.

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: 190. will usually return *note None: 158, 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: 190. expression where the generator’s execution is
     paused.

   * ‘close()’ raises a new *note GeneratorExit: d37. exception inside
     the generator to terminate the iteration.  On receiving this
     exception, the generator’s code must either raise *note
     GeneratorExit: d37. or *note StopIteration: 48b.  Catching the
     *note GeneratorExit: d37. exception and returning a value is
     illegal and will trigger a *note RuntimeError: 2bb.; 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: d37.
     occurs, I suggest using a ‘try: ... finally:’ suite instead of
     catching *note GeneratorExit: d37.

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: 191. statement), but
coroutines can be entered, exited, and resumed at many different points
(the *note yield: 190. 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: 183. clause will now always get a chance to run.  The syntactic
restriction that you couldn’t mix *note yield: 190. 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: 6ee.
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.

‘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://www.python.org/dev/peps/pep-0342

   (2) https://www.python.org/dev/peps/pep-0343

   (3) https://www.python.org/dev/peps/pep-0342

   (4) https://www.python.org/dev/peps/pep-0288

   (5) https://www.python.org/dev/peps/pep-0325


File: python.info,  Node: PEP 343 The 'with' statement<2>,  Next: PEP 352 Exceptions as New-Style Classes,  Prev: PEP 342 New Generator Features,  Up: What's New in Python 2 5

1.12.8 PEP 343: The ’with’ statement
------------------------------------

The ’*note with: 6ee.’ 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: 6ee.’ 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__(): c9a. and *note __exit__(): c9b. methods.

The object’s *note __enter__(): c9a. 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__(): c9b. 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: 6ee.’ 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: c35. loop raised an
exception part-way through the block.

     備註: In this case, `f' is the same object created by *note open():
     4f5, because ‘file.__enter__()’ returns `self'.

The *note threading: 10a. module’s locks and condition variables also
support the ’*note with: 6ee.’ 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: 36. 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>.
* The contextlib module: The contextlib module<2>.


File: python.info,  Node: Writing Context Managers<2>,  Next: The contextlib module<2>,  Up: PEP 343 The 'with' statement<2>

1.12.8.1 Writing Context Managers
.................................

Under the hood, the ’*note with: 6ee.’ 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__(): c9a. and *note __exit__(): c9b. methods.

   * The context manager’s *note __enter__(): c9a. 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(): c64.  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: 6ee.’
     statement will never realize anything went wrong.

   * If `BLOCK' didn’t raise an exception, the *note __exit__(): c9b.
     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__(): c9a. 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: 6ee.’ 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__(): c9b. 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: 191. 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: The contextlib module<2>,  Prev: Writing Context Managers<2>,  Up: PEP 343 The 'with' statement<2>

1.12.8.2 The contextlib module
..............................

The new *note contextlib: 24. module provides some functions and a
decorator that are useful for writing objects for use with the ’*note
with: 6ee.’ 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: 190.
will be executed as the *note __enter__(): c9a. method, and the value
yielded will be the method’s return value that will get bound to the
variable in the ’*note with: 6ee.’ statement’s ‘as’ clause, if any.  The
code after the *note yield: 190. will be executed in the *note
__exit__(): c9b. 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: 24. 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: 6ee.’ 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: 6ee.’ statement, which can be
     helpful in learning how the statement works.

The documentation for the *note contextlib: 24. module.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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 The 'with' statement<2>,  Up: What's New in Python 2 5

1.12.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: 1aa. class and all the
standard built-in exceptions (*note NameError: d80, *note ValueError:
1fc, 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: 198.
and *note SystemExit: 601. aren’t errors, though, and usually represent
an explicit action such as the user hitting ‘Control-C’ or code calling
*note sys.exit(): ce7.  A bare ‘except:’ will catch all exceptions, so
you commonly need to list *note KeyboardInterrupt: 198. and *note
SystemExit: 601. 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: 198. and *note SystemExit: 601. 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: 1a9. or some descendant of *note
BaseException: 1a9, 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: 1aa. 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://www.python.org/dev/peps/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: What's New in Python 2 5

1.12.10 PEP 353: Using ssize_t as the index type
------------------------------------------------

A wide-ranging change to Python’s C API, using a new ‘Py_ssize_t’ 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
‘http://www.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: 4bf. 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
‘Py_ssize_t’ to store their size.  Functions such as *note
PyList_Size(): d83. now return ‘Py_ssize_t’.  Code in extension modules
may therefore need to have some variables changed to ‘Py_ssize_t’.

The *note PyArg_ParseTuple(): 26b. and *note Py_BuildValue(): 2cf.
functions have a new conversion code, ‘n’, for ‘Py_ssize_t’.  *note
PyArg_ParseTuple(): 26b.’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 ‘Py_ssize_t’.

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

     PEP written and implemented by Martin von Löwis.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0353

   (2) https://www.python.org/dev/peps/pep-0353


File: python.info,  Node: PEP 357 The '__index__' method,  Next: Other Language Changes<11>,  Prev: PEP 353 Using ssize_t as the index type,  Up: What's New in Python 2 5

1.12.11 PEP 357: The ’__index__’ method
---------------------------------------

The NumPy developers had a problem that could only be solved by adding a
new special method, *note __index__(): 18b.  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 *note __int__(): 18c. method because
that method is also used to implement coercion to integers.  If slicing
used *note __int__(): 18c, floating-point numbers would also become
legal slice indexes and that’s clearly an undesirable behaviour.

Instead, a new special method called *note __index__(): 18b. 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: 193. if this requirement isn’t met.

A corresponding ‘nb_index’ slot was added to the C-level *note
PyNumberMethods: d86. structure to let C extensions implement this
protocol.  ‘PyNumber_Index(obj)’ can be used in extension code to call
the *note __index__(): 18b. function and retrieve its result.

也參考
......

PEP 357(1) - Allowing Any Object to be Used for Slicing

     PEP written and implemented by Travis Oliphant.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0357


File: python.info,  Node: Other Language Changes<11>,  Next: New Improved and Removed Modules,  Prev: PEP 357 The '__index__' method,  Up: What's New in Python 2 5

1.12.12 Other Language Changes
------------------------------

Here are all of the changes that Python 2.5 makes to the core Python
language.

   * The *note dict: 1b9. 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: 1e.
     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]   # Prints 1, 2
          print d[3], d[4]   # Prints 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'))

     (Implemented by Georg Brandl following a suggestion by Tom Lynn.)

   * The *note min(): 80e. and *note max(): 80f. 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(): 80e./*note max(): 80f. 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)

     (Contributed by Steven Bethard and Raymond Hettinger.)

   * Two new built-in functions, *note any(): d89. and *note all(): d8a,
     evaluate whether an iterator contains any true or false values.
     *note any(): d89. returns *note True: 49e. if any value returned by
     the iterator is true; otherwise it will return *note False: 38d.
     *note all(): d8a. returns *note True: 49e. 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 *note __hash__(): 345. 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(): d8b. built-in was changed to always return non-negative
     numbers, and users often seem to use ‘id(self)’ in *note
     __hash__(): 345. 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: d8c, 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: 1fe.
     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: 1fe. 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:
     d8c. was introduced.

     (Implemented by 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: d8d. switch to log all the paths searched.  In
     Python 2.5, a new *note ImportWarning: 5dd. 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: 41c. 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

     (Implemented by Brett Cannon.)

* Menu:

* Interactive Interpreter Changes::
* Optimizations: Optimizations<10>.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0263


File: python.info,  Node: Interactive Interpreter Changes,  Next: Optimizations<10>,  Up: Other Language Changes<11>

1.12.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:
d90. and *note –version: 5d6.; on Windows, it also accepts the *note /?:
d91. option for displaying a help message.  (Implemented by Georg
Brandl.)


File: python.info,  Node: Optimizations<10>,  Prev: Interactive Interpreter Changes,  Up: Other Language Changes<11>

1.12.12.2 Optimizations
.......................

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:
     b74. and *note frozenset: bf3. 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():
     df./‘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: 1fc. from the ‘read*()’ method.  (Implemented
     by Thomas Wouters.)

   * The *note struct: f9. 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: de. 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<10>,  Prev: Other Language Changes<11>,  Up: What's New in Python 2 5

1.12.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 *note audioop: d. module now supports the a-LAW encoding, and
     the code for u-LAW encoding has been improved.  (Contributed by
     Lars Immisch.)

   * The *note codecs: 1c. 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: 1c. module documentation for details.  (Designed
     and implemented by Walter Dörwald.)

   * The *note collections: 1e. module gained a new type, ‘defaultdict’,
     that subclasses the standard *note dict: 1b9. 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(): 263. or *note
     int(): 185.  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']}

     (Contributed by Guido van Rossum.)

   * The ‘deque’ double-ended queue type supplied by the *note
     collections: 1e. module now has a ‘remove(value)’ method that
     removes the first occurrence of `value' in the queue, raising *note
     ValueError: 1fc. if the value isn’t found.  (Contributed by Raymond
     Hettinger.)

   * New module: The *note contextlib: 24. module contains helper
     functions for use with the new ’*note with: 6ee.’ statement.  See
     section *note The contextlib module: d7c. for more about this
     module.

   * New module: The *note cProfile: 28. module is a C implementation of
     the existing *note profile: d4. module that has much lower
     overhead.  The module’s interface is the same as *note profile:
     d4.: 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: d4. module’s interface, will continue to be
     maintained in future versions of Python.  (Contributed by Armin
     Rigo.)

     Also, the *note pstats: d5. 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: 2a. 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.

     (Contributed by Skip Montanaro and Andrew McNamara.)

   * The *note datetime: 195. class in the *note datetime: 31. 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(): d96. and *note
     time.strftime(): b6a.:

          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: 37. 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: 67. 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: 69. package has been updated to version 4.0.
     (Contributed by Barry Warsaw.)

   * The *note fileinput: 80. module was made more flexible.  Unicode
     filenames are now supported, and a `mode' parameter that defaults
     to ‘"r"’ was added to the *note input(): c70. function to allow
     opening files in binary or *note universal newlines: 5f9. mode.
     Another new parameter, `openhook', lets you use a function other
     than *note open(): 4f5. to open the input files.  Once you’re
     iterating over the set of files, the ‘FileInput’ object’s new
     ‘fileno()’ returns the file descriptor for the currently opened
     file.  (Contributed by Georg Brandl.)

   * In the *note gc: 86. 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():
     22f. 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:
     8e. module now support a ‘key’ keyword parameter similar to the one
     provided by the *note min(): 80e./*note max(): 80f. 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']

     (Contributed by Raymond Hettinger.)

   * The *note itertools.islice(): 3a7. 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)

     (Contributed by Raymond Hettinger.)

   * The *note format(): 4e0. function in the *note locale: aa. module
     has been modified and two new functions were added,
     ‘format_string()’ and ‘currency()’.

     The *note format(): 4e0. 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(): 4e0. 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.

     (Contributed by Georg Brandl.)

   * The *note mailbox: af. 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 *note msilib: b6. 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 *note nis: c0. module now supports accessing domains other than
     the system default domain by supplying a `domain' argument to the
     *note nis.match(): d97. and *note nis.maps(): d98. functions.
     (Contributed by Ben Bell.)

   * The *note operator: c3. 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: c4. 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: c5. module underwent several changes.  The
     ‘stat_float_times’ variable now defaults to true, meaning that
     *note os.stat(): 1f2. will now return time values as floats.  (This
     doesn’t necessarily mean that *note os.stat(): 1f2. will return
     times that are precise to fractions of a second; not all systems
     support such precision.)

     Constants named *note os.SEEK_SET: d99, *note os.SEEK_CUR: d9a, and
     *note os.SEEK_END: d9b. have been added; these are the parameters
     to the *note os.lseek(): a63. function.  Two new constants for
     locking are *note os.O_SHLOCK: d9c. and *note os.O_EXLOCK: d9d.

     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(): d9e. function.  ‘wait4(pid)’ does take a
     process ID. (Contributed by Chad J. Schroeder.)

     On FreeBSD, the *note os.stat(): 1f2. 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: ca. 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: cb. and ‘cPickle’ modules no longer accept a
     return value of ‘None’ from the *note __reduce__(): 19c. 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: ce. 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: d1d. 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: e2. module is no longer dependent on
     importing the *note readline: df. module and therefore now works on
     non-Unix platforms.  (Patch from Robert Kiendl.)

   * The ‘SimpleXMLRPCServer’ and ‘DocXMLRPCServer’ 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: f0. 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 *note spwd: f2. module provides functions for
     accessing the shadow password database on systems that support
     shadow passwords.

   * The *note struct: f9. is now faster because it compiles format
     strings into ‘Struct’ objects with ‘pack()’ and ‘unpack()’ methods.
     This is similar to how the *note re: de. 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(): d9f. 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(): da0, 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: 102. 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: 10a. 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: 11b. 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: da1.

   * New module: the *note uuid: 125. 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')

     (Contributed by Ka-Ping Yee.)

   * The *note weakref: 129. 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: 12a. 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(): 4f5. 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 ‘xmlrpclib’ module now supports returning *note datetime: 195.
     objects for the XML-RPC date type.  Supply ‘use_datetime=True’ to
     the ‘loads()’ function or the ‘Unmarshaller’ class to enable this
     feature.  (Contributed by Skip Montanaro.)

   * The *note zipfile: 143. 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: 145. module’s ‘Compress’ and ‘Decompress’ objects
     now support a *note copy(): 26. method that makes a copy of the
     object’s internal state and returns a new ‘Compress’ or
     ‘Decompress’ object.  (Contributed by Chris AtLee.)

* Menu:

* The ctypes package::
* The ElementTree package::
* The hashlib package::
* The sqlite3 package::
* The wsgiref package::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0302

   (2) https://tools.ietf.org/html/rfc4122.html

   (3) https://tools.ietf.org/html/rfc4122.html


File: python.info,  Node: The ctypes package,  Next: The ElementTree package,  Up: New Improved and Removed Modules

1.12.13.1 The ctypes package
............................

The *note ctypes: 2b. package, written by Thomas Heller, has been added
to the standard library.  *note ctypes: 2b. 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: 2b. 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: 2b. 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 ‘py_object()’
type constructor that will create a *note PyObject *: 4bf. pointer.  A
simple usage:

     import ctypes

     d = {}
     ctypes.pythonapi.PyObject_SetItem(ctypes.py_object(d),
               ctypes.py_object("abc"),  ctypes.py_object(1))
     # d is now {'abc', 1}.

Don’t forget to use ‘py_object()’; if it’s omitted you end up with a
segmentation fault.

*note ctypes: 2b. has been around for a while, but people still write
and distribution hand-coded extension modules because you can’t rely on
*note ctypes: 2b. being present.  Perhaps developers will begin to write
Python wrappers atop a library accessed through *note ctypes: 2b.
instead of extension modules, now that *note ctypes: 2b. is included
with core Python.

也參考
......

‘http://starship.python.net/crew/theller/ctypes/’

     The ctypes web page, with a tutorial, reference, and FAQ.

The documentation for the *note ctypes: 2b. module.


File: python.info,  Node: The ElementTree package,  Next: The hashlib package,  Prev: The ctypes package,  Up: New Improved and Removed Modules

1.12.13.2 The ElementTree package
.................................

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
‘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.

Operation                           Result
                                    
-------------------------------------------------------------------------------------
                                    
‘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.

也參考
......

‘http://effbot.org/zone/element-index.htm’

     Official documentation for ElementTree.


File: python.info,  Node: The hashlib package,  Next: The sqlite3 package,  Prev: The ElementTree package,  Up: New Improved and Removed Modules

1.12.13.3 The hashlib package
.............................

A new *note hashlib: 8d. module, written by Gregory P. Smith, has been
added to replace the ‘md5’ and ‘sha’ modules.  *note hashlib: 8d. 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(): 26. returns a new
hashing object with the same digest state.

也參考
......

The documentation for the *note hashlib: 8d. module.


File: python.info,  Node: The sqlite3 package,  Next: The wsgiref package,  Prev: The hashlib package,  Up: New Improved and Removed Modules

1.12.13.4 The sqlite3 package
.............................

The pysqlite module (‘http://www.pysqlite.org’), a wrapper for the
SQLite embedded database, has been added to the standard library under
the package name *note sqlite3: f3.

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’.

也參考
......

‘http://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.

The documentation for the *note sqlite3: f3. module.

PEP 249(2) - Database API Specification 2.0

     PEP written by Marc-André Lemburg.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0249

   (2) https://www.python.org/dev/peps/pep-0249


File: python.info,  Node: The wsgiref package,  Prev: The sqlite3 package,  Up: New Improved and Removed Modules

1.12.13.5 The wsgiref package
.............................

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: 12d. 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()

也參考
......

‘http://www.wsgi.org’

     A central web site for WSGI-related resources.

PEP 333(2) - Python Web Server Gateway Interface v1.0

     PEP written by Phillip J. Eby.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0333

   (2) https://www.python.org/dev/peps/pep-0333


File: python.info,  Node: Build and C API Changes<10>,  Next: Porting to Python 2 5,  Prev: New Improved and Removed Modules,  Up: What's New in Python 2 5

1.12.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 ‘Py_ssize_t’ type definition
     instead of ‘int’.  See the earlier section *note PEP 353; Using
     ssize_t as the index type: d81. 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(): 1b5. 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(): 50a, *note PyMem_Realloc(): 974, and *note
     PyMem_Free(): dae. are one family that allocates raw memory, while
     *note PyObject_Malloc(): 50d, *note PyObject_Realloc(): daf, and
     *note PyObject_Free(): 509. 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 *note PyObject(): 4bf. 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(): db0. and *note PyFrozenSet_New(): db1. to create a new
     set, *note PySet_Add(): db2. and *note PySet_Discard(): db3. to add
     and remove elements, and *note PySet_Contains(): db4. and *note
     PySet_Size(): db5. 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(): d9f.
     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 ‘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(): db6, 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://www.python.org/dev/peps/pep-0347

   (2) https://www.python.org/dev/peps/pep-0353

   (3) https://www.python.org/dev/peps/pep-0339


File: python.info,  Node: Port-Specific Changes,  Up: Build and C API Changes<10>

1.12.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/issue2573


File: python.info,  Node: Porting to Python 2 5,  Next: Acknowledgements<3>,  Prev: Build and C API Changes<10>,  Up: What's New in Python 2 5

1.12.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: d6b, it’s now
     possible for ‘gi_frame’ to be ‘None’.

   * A new warning, *note UnicodeWarning: d8c, 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:
     1fe. exception.

   * Library: the *note csv: 2a. 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: aa. module’s *note format(): 4e0.
     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: cb. and ‘cPickle’ modules no longer
     accept a return value of ‘None’ from the *note __reduce__(): 19c.
     method; the method must return a tuple of arguments instead.  The
     modules also no longer accept the deprecated `bin' keyword
     parameter.

   * Library: The ‘SimpleXMLRPCServer’ and ‘DocXMLRPCServer’ 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 ‘Py_ssize_t’ 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: d81. 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://www.python.org/dev/peps/pep-0342


File: python.info,  Node: Acknowledgements<3>,  Prev: Porting to Python 2 5,  Up: What's New in Python 2 5

1.12.16 Acknowledgements
------------------------

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: What's New in Python 2 4,  Next: What's New in Python 2 3,  Prev: What's New in Python 2 5,  Up: Python 有什麼新功能？

1.13 What’s New in Python 2.4
=============================


Author: 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.
* Other Language Changes: Other Language Changes<12>.
* New, Improved, and Deprecated Modules: New Improved and Deprecated Modules<3>.
* Build and C API Changes: Build and C API Changes<11>.
* Porting to Python 2.4: Porting to Python 2 4.
* Acknowledgements: Acknowledgements<4>.


File: python.info,  Node: PEP 218 Built-In Set Objects,  Next: PEP 237 Unifying Long Integers and Integers,  Up: What's New in Python 2 4

1.13.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(): bf3. type is an immutable version of *note set():
b74.  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://www.python.org/dev/peps/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: What's New in Python 2 4

1.13.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: 32a. 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://www.python.org/dev/peps/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: What's New in Python 2 4

1.13.3 PEP 289: Generator Expressions
-------------------------------------

The iterator feature introduced in Python 2.2 and the *note itertools:
a4. 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://www.python.org/dev/peps/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: What's New in Python 2 4

1.13.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: 1fc, 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: f7. 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: 2c8.  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://www.python.org/dev/peps/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: What's New in Python 2 4

1.13.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: dc3. statement in the usual way, and pass the resulting
method to a *note staticmethod(): 1da. or *note classmethod(): 1d9.
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(): 1d9. 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(): 1d9, *note staticmethod(): 1da, 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 ‘func_name’ 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://www.python.org/dev/peps/pep-0318

   (2) https://www.python.org/dev/peps/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: What's New in Python 2 4

1.13.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(): 18f. is easier to read, runs faster, and uses substantially
less memory.

Note that *note reversed(): 18f. only accepts sequences, not arbitrary
iterators.  If you want to reverse an iterator, first convert it to a
list with *note list(): 263.

     >>> 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://www.python.org/dev/peps/pep-0322


File: python.info,  Node: PEP 324 New subprocess Module,  Next: PEP 327 Decimal Data Type,  Prev: PEP 322 Reverse Iteration,  Up: What's New in Python 2 4

1.13.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: fa.
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: fa.
contains a single class called ‘Popen’ 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(): dc6. 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: 5f9. 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(): dc6.:

     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: fa.
Reading this section of the PEP is highly recommended.

也參考
......

PEP 324(1) - subprocess - New process module

     Written and implemented by Peter Åstrand, with assistance from
     Fredrik Lundh and others.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0324


File: python.info,  Node: PEP 327 Decimal Data Type,  Next: PEP 328 Multi-line Imports,  Prev: PEP 324 New subprocess Module,  Up: What's New in Python 2 4

1.13.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?::
* The Decimal type::
* The Context type::


File: python.info,  Node: Why is Decimal needed?,  Next: The Decimal type,  Up: PEP 327 Decimal Data Type

1.13.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: The Decimal type,  Next: The Context type,  Prev: Why is Decimal needed?,  Up: PEP 327 Decimal Data Type

1.13.8.2 The ‘Decimal’ type
...........................

A new module, *note decimal: 36, 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: b2. and *note cmath:
19. 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: The Context type,  Prev: The Decimal type,  Up: PEP 327 Decimal Data Type

1.13.8.3 The ‘Context’ type
...........................

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: 36.
     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: 36.
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://www.python.org/dev/peps/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: What's New in Python 2 4

1.13.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: c22. 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://www.python.org/dev/peps/pep-0328


File: python.info,  Node: PEP 331 Locale-Independent Float/String Conversions,  Next: Other Language Changes<12>,  Prev: PEP 328 Multi-line Imports,  Up: What's New in Python 2 4

1.13.10 PEP 331: Locale-Independent Float/String Conversions
------------------------------------------------------------

The *note locale: aa. 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.gnome.org/glib/stable/’), whose developers kindly
relicensed the relevant functions and donated them to the Python
Software Foundation.  The *note locale: aa. 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://www.python.org/dev/peps/pep-0331


File: python.info,  Node: Other Language Changes<12>,  Next: New Improved and Deprecated Modules<3>,  Prev: PEP 331 Locale-Independent Float/String Conversions,  Up: What's New in Python 2 4

1.13.11 Other Language Changes
------------------------------

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(): b74. and *note frozenset(): bf3. 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(): dce. method now accepts the same argument
     forms as the *note dict: 1b9. 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: c34. 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(): 44a. 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

     (Contributed by 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: 33c, 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(): c37. built-in function and ‘itertools.izip()’ now
     return an empty list if called with no arguments.  Previously they
     raised a *note TypeError: 193. 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([])
          []

     (Contributed by 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: 158. is now a constant; code that binds a new value to
     the name ‘None’ is now a syntax error.  (Contributed by Raymond
     Hettinger.)

* Menu:

* Optimizations: Optimizations<11>.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0318

   (2) https://www.python.org/dev/peps/pep-0218

   (3) https://www.python.org/dev/peps/pep-0322

   (4) https://www.python.org/dev/peps/pep-0289

   (5) https://www.python.org/dev/peps/pep-0237

   (6) https://www.python.org/dev/peps/pep-0328


File: python.info,  Node: Optimizations<11>,  Up: Other Language Changes<12>

1.13.11.1 Optimizations
.......................

   * 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(): 263, *note tuple(): 483, *note map(): c32, *note
     filter(): c33, and *note zip(): c37. now run several times faster
     with non-sequence arguments that supply a *note __len__(): dd0.
     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<11>,  Prev: Other Language Changes<12>,  Up: What's New in Python 2 4

1.13.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 *note asyncore: b. 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: e. 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: 12. 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: 1e. 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: 10a.
     modules, now take advantage of *note collections.deque: 536. for
     improved performance.  (Contributed by Raymond Hettinger.)

   * The ‘ConfigParser’ classes have been enhanced slightly.  The
     ‘read()’ method now returns a list of the files that were
     successfully parsed, and the *note set(): b74. method raises *note
     TypeError: 193. if passed a `value' argument that isn’t a string.
     (Contributed by John Belmonte and David Goodger.)

   * The *note curses: 2c. 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: 37. 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: 69. 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: 8e. 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 ‘httplib’ 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: 98. module now supports IMAP’s THREAD command
     (contributed by Yves Dionne) and new ‘deleteacl()’ and ‘myrights()’
     methods (contributed by Arnaud Mazin).

   * The *note itertools: a4. 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)]

     (Contributed by Hye-Shik Chang.)

   * *note itertools: a4. 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():
     263. 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: aa. 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: ab.
     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: ab. 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: b1. 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 *note nntplib: c1. 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: c3. 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(): c32. or *note sorted(): 449.  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)]

     (Contributed by Raymond Hettinger.)

   * The *note optparse: c4. module was updated in various ways.  The
     module now passes its messages through *note gettext.gettext():
     dd2, 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: 69. package.  To
     this end, the ‘email.Utils.formatdate()’ 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: c5. 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: d2. module
     that underlies the *note os: c5. module.  (Contributed by J.
     Raynor.)

   * The *note poplib: d1. module now supports POP over SSL.
     (Contributed by Hector Urtubia.)

   * The *note profile: d4. module can now profile C extension
     functions.  (Contributed by Nick Bastin.)

   * The *note random: dd. 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: de.
     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: de. 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: 2bb. 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: eb. module now performs tighter error-checking on
     the parameters to the *note signal.signal(): a82. 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: 2bb. exception.

   * Two new functions were added to the *note socket: f0. 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: c. module, which correctly handles
     calling multiple exit functions.  Eventually ‘sys.exitfunc()’ will
     become a purely internal interface, accessed only by *note atexit:
     c.

   * The *note tarfile: 102. module now generates GNU-format tar files
     by default.  (Contributed by Lars Gustäbel.)

   * The *note threading: 10a. 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: 10c. 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: 129. 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 ‘xmlrpclib’ 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<3>.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc3548.html


File: python.info,  Node: cookielib,  Next: doctest<3>,  Up: New Improved and Deprecated Modules<3>

1.13.12.1 cookielib
...................

The ‘cookielib’ library supports client-side handling for HTTP cookies,
mirroring the ‘Cookie’ 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.

‘urllib2’ has been changed to interact with ‘cookielib’:
‘HTTPCookieProcessor’ manages a cookie jar that is used when accessing
URLs.

This module was contributed by John J. Lee.


File: python.info,  Node: doctest<3>,  Prev: cookielib,  Up: New Improved and Deprecated Modules<3>

1.13.12.2 doctest
.................

The *note doctest: 67. module underwent considerable refactoring thanks
to Edward Loper and Tim Peters.  Testing can still be as simple as
running *note doctest.testmod(): dd5, 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: dd6. 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: dd7. (unified diffs),
*note doctest.REPORT_CDIFF: dd8. (context diffs), or *note
doctest.REPORT_NDIFF: dd9. (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: dd7.
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<11>,  Next: Porting to Python 2 4,  Prev: New Improved and Deprecated Modules<3>,  Up: What's New in Python 2 4

1.13.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: ddb, *note
     Py_RETURN_TRUE: ddc, and *note Py_RETURN_FALSE: ddd.  (Contributed
     by Brett Cannon.)

   * Another new macro, ‘Py_CLEAR(obj)’, 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 *note
     PyEval_ThreadsInitialized(): dde. 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(): ddf, is the
     same as *note PyArg_ParseTupleAndKeywords(): 5cf. but takes a
     ‘va_list’ instead of a number of arguments.  (Contributed by Greg
     Chapman.)

   * A new method flag, ‘METH_COEXISTS’, allows a function defined in
     slots to co-exist with a *note PyCFunction: de0. 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<11>

1.13.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: Acknowledgements<4>,  Prev: Build and C API Changes<11>,  Up: What's New in Python 2 4

1.13.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: 32a. 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(): c37. built-in function and ‘itertools.izip()’ now
     return an empty list instead of raising a *note TypeError: 193.
     exception if called with no arguments.

   * You can no longer compare the ‘date’ and *note datetime: 195.
     instances provided by the *note datetime: 31. module.  Two
     instances of different classes will now always be unequal, and
     relative comparisons (‘<’, ‘>’) will raise a *note TypeError: 193.

   * ‘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(): de3. now warns if the `mutate' argument is
     omitted and relevant.

   * The *note tarfile: 102. 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: 158. 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:
     2bb. 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: Acknowledgements<4>,  Prev: Porting to Python 2 4,  Up: What's New in Python 2 4

1.13.15 Acknowledgements
------------------------

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: What's New in Python 2 3,  Next: What's New in Python 2 2,  Prev: What's New in Python 2 4,  Up: Python 有什麼新功能？

1.14 What’s New in Python 2.3
=============================


Author: 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(): 1e6. and *note enumerate(): de8.  The
*note in: 7a8. operator can now be used for substring searches (e.g.
‘"ab" in "abc"’ returns *note True: 49e.).

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::
* Other Language Changes: Other Language Changes<13>.
* 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<12>.
* Other Changes and Fixes: Other Changes and Fixes<2>.
* Porting to Python 2.3: Porting to Python 2 3.
* Acknowledgements: Acknowledgements<5>.


File: python.info,  Node: PEP 218 A Standard Set Datatype,  Next: PEP 255 Simple Generators,  Up: What's New in Python 2 3

1.14.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.

Here’s a simple example:

     >>> 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 ‘union()’
and ‘intersection()’ methods; an alternative notation uses the bitwise
operators ‘&’ and ‘|’.  Mutable sets also have in-place versions of
these methods, ‘union_update()’ and ‘intersection_update()’.

     >>> 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
‘symmetric_difference_update()’.

     >>> 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://www.python.org/dev/peps/pep-0218


File: python.info,  Node: PEP 255 Simple Generators,  Next: PEP 263 Source Code Encodings,  Prev: PEP 218 A Standard Set Datatype,  Up: What's New in Python 2 3

1.14.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: 190. 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: 191.
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: 190, 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: 190. statement, the generator
outputs the value of ‘i’, similar to a *note return: 191. 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: d77. 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: 191. 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: 48b. 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(): 687. 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://www.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://www.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: dec. 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://www.python.org/dev/peps/pep-0255

   (2) https://www.python.org/dev/peps/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: What's New in Python 2 3

1.14.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: 279. 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://www.python.org/dev/peps/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: What's New in Python 2 3

1.14.4 PEP 273: Importing Modules from ZIP Archives
---------------------------------------------------

The new *note zipimport: 144. 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: df0. for a description of the new import hooks.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0273

   (2) https://www.python.org/dev/peps/pep-0273

   (3) https://www.python.org/dev/peps/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: What's New in Python 2 3

1.14.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(): 4f5. built-in function.  If a
Unicode string is passed to *note os.listdir(): a46, 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: c40. to be raised.  Applications can test whether
arbitrary Unicode strings are supported as file names by checking *note
os.path.supports_unicode_filenames: df2, a Boolean value.

Under MacOS, *note os.listdir(): a46. 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://www.python.org/dev/peps/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: What's New in Python 2 3

1.14.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: 5f9. 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 *note readline(): df.

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://www.python.org/dev/peps/pep-0278


File: python.info,  Node: PEP 279 enumerate,  Next: PEP 282 The logging Package,  Prev: PEP 278 Universal Newline Support,  Up: What's New in Python 2 3

1.14.7 PEP 279: enumerate()
---------------------------

A new built-in function, *note enumerate(): de8, 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(): de8. 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://www.python.org/dev/peps/pep-0279


File: python.info,  Node: PEP 282 The logging Package,  Next: PEP 285 A Boolean Type,  Prev: PEP 279 enumerate,  Up: What's New in Python 2 3

1.14.8 PEP 282: The logging Package
-----------------------------------

A standard package for writing logs, *note logging: ab, 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 ‘Logger’ class is the primary class.  Most application code will
deal with one or more ‘Logger’ objects, each one used by a particular
subsystem of the application.  Each ‘Logger’ is identified by a name,
and names are organized into a hierarchy using ‘.’ as the component
separator.  For example, you might have ‘Logger’ 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 ‘Logger’ that’s the parent of
all other loggers.

For simple uses, the *note logging: ab. 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
‘setLevel()’ method on the root logger.

Notice the ‘warning()’ 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 ‘exception()’ 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 ‘Logger’ can
prevent this by setting its ‘propagate’ attribute to *note False: 38d.

There are more classes provided by the *note logging: ab. package that
can be customized.  When a ‘Logger’ instance is told to log a message,
it creates a ‘LogRecord’ instance that is sent to any number of
different ‘Handler’ instances.  Loggers and handlers can also have an
attached list of filters, and each filter can cause the ‘LogRecord’ to
be ignored or can modify the record before passing it along.  When
they’re finally output, ‘LogRecord’ instances are converted to text by a
‘Formatter’ class.  All of these classes can be replaced by your own
specially-written classes.

With all of these features the *note logging: ab. 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://www.python.org/dev/peps/pep-0282

   (2) https://www.python.org/dev/peps/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: What's New in Python 2 3

1.14.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: 49e. and *note False: 38d.  (*note
True: 49e. and *note False: 38d. 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: 184.; the
constructor for it takes any Python value and converts it to *note True:
49e. or *note False: 38d.

     >>> 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: dec. 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: 185. 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: 49e. and *note False: 38d. in a sentence: they’re
alternative ways to spell the integer values 1 and 0, with the single
difference that *note str(): 335. and *note repr(): 7d1. 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://www.python.org/dev/peps/pep-0285

   (2) https://www.python.org/dev/peps/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: What's New in Python 2 3

1.14.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:
c40.), "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(): dfa, and codecs then can access the error
handler with *note codecs.lookup_error(): dfb.  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://www.python.org/dev/peps/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: What's New in Python 2 3

1.14.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://www.python.org/dev/peps/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: What's New in Python 2 3

1.14.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: fe.
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: 339. 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://www.python.org/dev/peps/pep-0302

   (2) https://www.python.org/dev/peps/pep-0302

   (3) https://www.python.org/dev/peps/pep-0302


File: python.info,  Node: PEP 305 Comma-separated Files,  Next: PEP 307 Pickle Enhancements,  Prev: PEP 302 New Import Hooks,  Up: What's New in Python 2 3

1.14.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: 2a. package is much simpler:

     import csv

     input = open('datafile', 'rb')
     reader = csv.reader(input)
     for line in reader:
         print line

The ‘reader()’ 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: e01. class will generate
comma-separated files from a succession of tuples or lists, quoting
strings that contain the delimiter.

也參考
......

PEP 305(1) - CSV File API

     Written and implemented by Kevin Altis, Dave Cole, Andrew McNamara,
     Skip Montanaro, Cliff Wells.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0305


File: python.info,  Node: PEP 307 Pickle Enhancements,  Next: Extended Slices,  Prev: PEP 305 Comma-separated Files,  Up: What's New in Python 2 3

1.14.14 PEP 307: Pickle Enhancements
------------------------------------

The *note pickle: cb. 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(): e04. 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: e05, can be used to select the fanciest
protocol available.

Unpickling is no longer considered a safe operation.  2.2’s *note
pickle: cb. 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__(): e06, *note __setstate__(): 19d, and *note
__getnewargs__(): 6b3.  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://www.python.org/dev/peps/pep-0307

   (2) https://www.python.org/dev/peps/pep-0307

   (3) https://www.python.org/dev/peps/pep-0307


File: python.info,  Node: Extended Slices,  Next: Other Language Changes<13>,  Prev: PEP 307 Pickle Enhancements,  Up: What's New in Python 2 3

1.14.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: 193. 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__(): 27d.
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(): 9c3.  ‘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: e09.
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: 185,
*note str: 335, etc., underwent the same change.


File: python.info,  Node: Other Language Changes<13>,  Next: New Improved and Deprecated Modules<4>,  Prev: Extended Slices,  Up: What's New in Python 2 3

1.14.16 Other Language Changes
------------------------------

Here are all of the changes that Python 2.3 makes to the core Python
language.

   * The *note yield: 190. statement is now always a keyword, as
     described in section *note PEP 255; Simple Generators: deb. of this
     document.

   * A new built-in function *note enumerate(): de8. was added, as
     described in section *note PEP 279; enumerate(): df5. of this
     document.

   * Two new constants, *note True: 49e. and *note False: 38d. were
     added along with the built-in *note bool: 184. type, as described
     in section *note PEP 285; A Boolean Type: df8. of this document.

   * The *note int(): 185. type constructor will now return a long
     integer instead of raising an *note OverflowError: 965. 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: e08. 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(): 1e6. 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: 2c8. 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(): 1b9. 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}

     (Contributed by Just van Rossum.)

   * The *note assert: e0b. statement no longer checks the ‘__debug__’
     flag, so you can no longer disable assertions by assigning to
     ‘__debug__’.  Running Python with the *note -O: 690. 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: 119. 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: 27a. 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;;: 41c. on the command line or
     use *note warnings.filterwarnings(): e0c.

   * The process of deprecating string-based exceptions, as in ‘raise
     "Error occurred"’, has begun.  Raising a string will now trigger
     *note PendingDeprecationWarning: 27a.

   * Using ‘None’ as a variable name will now result in a *note
     SyntaxWarning: 192. 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 "Python 2.3 Method Resolution Order"(2), 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 *note sys.getcheckinterval(): e0d. 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__:
     c6c. and *note __bases__: e0e. attributes of new-style classes.
     There are some restrictions on what can be assigned to *note
     __bases__: e0e. along the lines of those relating to assigning to
     an instance’s *note __class__: e0f. attribute.

* Menu:

* String Changes::
* Optimizations: Optimizations<12>.

   ---------- Footnotes ----------

   (1) http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.19.3910

   (2) http://www.phyast.pitt.edu/~micheles/mro.html


File: python.info,  Node: String Changes,  Next: Optimizations<12>,  Up: Other Language Changes<13>

1.14.16.1 String Changes
........................

   * The *note in: 7a8. 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:
     49e. if `X' is a substring of `Y'. If `X' is the empty string, the
     result is always *note True: 49e.

          >>> '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 ‘find()’ string method.

   * The ‘strip()’, ‘lstrip()’, and ‘rstrip()’ 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 ‘startswith()’ and ‘endswith()’ string methods now accept
     negative numbers for the `start' and `end' parameters.

   * Another new string method is ‘zfill()’, originally a function in
     the *note string: f7. module.  ‘zfill()’ 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 ‘zfill()’.

          >>> '45'.zfill(4)
          '0045'
          >>> '12345'.zfill(4)
          '12345'
          >>> 'goofy'.zfill(6)
          '0goofy'

     (Contributed by 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: 49e. 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: Optimizations<12>,  Prev: String Changes,  Up: Other Language Changes<13>

1.14.16.2 Optimizations
.......................

   * The creation of new-style class instances has been made much
     faster; they’re now faster than classic classes!

   * The ‘sort()’ 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*n) 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: e12. 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: Other Language Changes<13>,  Up: What's New in Python 2 3

1.14.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: 7. 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: 14. module is an interface to the bz2 data
     compression library.  bz2-compressed data is usually smaller than
     corresponding *note zlib: 145.-compressed data.  (Contributed by
     Gustavo Niemeyer.)

   * A set of standard date/time types has been added in the new *note
     datetime: 31. 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 ‘CC’,
     ‘CFLAGS’, ‘CPP’, ‘LDFLAGS’, and ‘CPPFLAGS’ environment variables,
     using them to override the settings in Python’s configuration
     (contributed by Robert Weber).

   * Previously the *note doctest: 67. module would only search the
     docstrings of public methods and functions for test cases, but it
     now also examines private ones as well.  The ‘DocTestSuite()’
     function creates a *note unittest.TestSuite: 6d3. object from a set
     of *note doctest: 67. tests.

   * The new ‘gc.get_referents(object)’ function returns a list of all
     the objects referenced by `object'.

   * The *note getopt: 87. module gained a new function, ‘gnu_getopt()’,
     that supports the same arguments as the existing *note getopt():
     87. function but uses GNU-style scanning mode.  The existing *note
     getopt(): 87. 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'])

     (Contributed by Peter Åstrand.)

   * The *note grp: 8b, *note pwd: d7, and *note resource: e1. modules
     now return enhanced tuples:

          >>> import grp
          >>> g = grp.getgrnam('amk')
          >>> g.gr_name, g.gr_gid
          ('amk', 500)

   * The *note gzip: 8c. module can now handle files exceeding 2 GiB.

   * The new *note heapq: 8e. 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(lg n).  (See
     ‘https://xlinux.nist.gov/dads//HTML/priorityque.html’ for more
     information about the priority queue data structure.)

     The *note heapq: 8e. module provides ‘heappush()’ and ‘heappop()’
     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]

     (Contributed by Kevin O’Connor.)

   * The IDLE integrated development environment has been updated using
     the code from the IDLEfork project
     (‘http://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 ‘idlelib’ package.

   * The *note imaplib: 98. module now supports IMAP over SSL.
     (Contributed by Piers Lauder and Tino Lange.)

   * The *note itertools: a4. 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: 49e, 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: b2. module, ‘degrees(rads)’
     and ‘radians(degs)’, convert between radians and degrees.  Other
     functions in the *note math: b2. module such as *note math.sin():
     e14. and *note math.cos(): e15. have always required input values
     measured in radians.  Also, an optional `base' argument was added
     to *note math.log(): e16. 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: d2. module that underlies the *note os:
     c5. module.  (Contributed by Gustavo Niemeyer, Geert Jansen, and
     Denis S. Otkidach.)

   * In the *note os: c5. 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(): 322.

     During testing, it was found that some applications will break if
     time stamps are floats.  For compatibility, when using the tuple
     interface of the ‘stat_result’ 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: c4. 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 *note ossaudiodev: c7. 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: cf. 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 ‘pyexpat’ 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 ‘buffer_text’ attribute to *note True: 49e.
     will enable buffering.

   * The ‘sample(population, k)’ function was added to the *note random:
     dd. module.  `population' is a sequence or ‘xrange’ object
     containing the elements of a population, and ‘sample()’ 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: dd. 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: df. module also gained a number of new
     functions: ‘get_history_item()’, ‘get_current_history_length()’,
     and ‘redisplay()’.

   * The ‘rexec’ and ‘Bastion’ modules have been declared dead, and
     attempts to import them will fail with a *note RuntimeError: 2bb.
     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: ea. 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: eb. but then removed again as it proved impossible to
     make it work reliably across platforms.

   * The *note socket: f0. 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: c13. exception.

     The original timeout implementation was by Tim O’Malley.  Michael
     Gilfix integrated it into the Python *note socket: f0. 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: f0. 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: 102. module allows reading from and writing
     to ‘tar’-format archive files.  (Contributed by Lars Gustäbel.)

   * The new *note textwrap: 109. 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, ‘fill()’
     is built on top of ‘wrap()’.  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 ‘TextWrapper’ class that actually
     implements the text wrapping strategy.  Both the ‘TextWrapper’
     class and the ‘wrap()’ and ‘fill()’ 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: 10a. modules now have companion
     modules, ‘dummy_thread’ and *note dummy_threading: 68, 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: 10a. module.  Code can call functions and use
     classes in ‘_threading’ whether or not threads are supported,
     avoiding an *note if: dec. 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: 10b. module’s ‘strptime()’ function has long been
     an annoyance because it uses the platform C library’s ‘strptime()’
     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: 10c. 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 ‘Timer’ 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: e8. module.

     Adding the mix-in as a superclass provides the full dictionary
     interface whenever the class defines *note __getitem__(): 27d,
     *note __setitem__(): c67, *note __delitem__(): c68, 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']

     (Contributed by Raymond Hettinger.)

   * The DOM implementation in *note xml.dom.minidom: 136. can now
     generate XML output in a particular encoding by providing an
     optional encoding argument to the ‘toxml()’ and ‘toprettyxml()’
     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: f0. 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: 84.) also support Unicode host
     names; ‘httplib’ also sends HTTP ‘Host’ headers using the ACE
     version of the domain name.  *note urllib: 11e. 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: f8. module, the
     ‘mkstringprep’ tool and the ‘punycode’ encoding have been added.

* Menu:

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

   ---------- Footnotes ----------

   (1) http://pybsddb.sourceforge.net


File: python.info,  Node: Date/Time Type,  Next: The optparse Module,  Up: New Improved and Deprecated Modules<4>

1.14.17.1 Date/Time Type
........................

Date and time types suitable for expressing timestamps were added as the
*note datetime: 31. 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: ‘date’, representing a day, month, and
year; *note time: 4f8, consisting of hour, minute, and second; and *note
datetime: 195, which contains all the attributes of both ‘date’ and
*note time: 4f8.  There’s also a ‘timedelta’ class representing
differences between two points in time, and time zone logic is
implemented by classes inheriting from the abstract ‘tzinfo’ class.

You can create instances of ‘date’ and *note time: 4f8. 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 ‘date.today()’ 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 ‘replace()’ method allows modifying one or more fields of a ‘date’
or *note datetime: 195. 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 ‘isoformat()’).  ‘date’ and *note datetime: 195.
instances can be subtracted from each other, and added to ‘timedelta’
instances.  The largest missing feature is that there’s no standard
library support for parsing strings and getting back a ‘date’ or *note
datetime: 195.

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.14.17.2 The optparse Module
.............................

The *note getopt: 87. module provides simple parsing of command-line
arguments.  The new *note optparse: c4. 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 ‘OptionParser’ 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 ‘parse_args()’
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
     $

See the module’s documentation for more details.

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<12>,  Prev: New Improved and Deprecated Modules<4>,  Up: What's New in Python 2 3

1.14.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(): 50d, it
has to be freed using *note PyObject_Free(): 509, 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(): 50a, *note
     PyMem_Realloc(): 974, and *note PyMem_Free(): dae.

   * 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(): 50d, *note
     PyObject_Realloc(): daf, and *note PyObject_Free(): 509.

   * To allocate and free Python objects, use the "object" family *note
     PyObject_New(): 2d3, *note PyObject_NewVar(): 2d4, and *note
     PyObject_Del(): e1b.

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<12>,  Next: Other Changes and Fixes<2>,  Prev: Pymalloc A Specialized Object Allocator,  Up: What's New in Python 2 3

1.14.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 ‘PyMODINIT_FUNC’, 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: e1d. 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: e1d.

   * *note PyArg_ParseTuple(): 26b. 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: e1e. or
     *note METH_STATIC: e1f. flags in a method’s *note PyMethodDef: e20.
     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__: c6c. 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<12>

1.14.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(): 7e. 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<12>,  Up: What's New in Python 2 3

1.14.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: e23. 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:
     e24. 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: ca.).  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: 690.

     C extensions that access the ‘f_lineno’ 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
     ‘f_lineno’ attribute of frame objects, changing the line that will
     be executed next.  A ‘jump’ command has been added to the *note
     pdb: ca. debugger taking advantage of this new feature.
     (Implemented by Richie Hindle.)


File: python.info,  Node: Porting to Python 2 3,  Next: Acknowledgements<5>,  Prev: Other Changes and Fixes<2>,  Up: What's New in Python 2 3

1.14.21 Porting to Python 2.3
-----------------------------

This section lists previously described changes that may require changes
to your code:

   * *note yield: 190. 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(): 185. type constructor will now return a long
     integer instead of raising an *note OverflowError: 965. 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: dee. 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: 32a.  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: 192. 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: Acknowledgements<5>,  Prev: Porting to Python 2 3,  Up: What's New in Python 2 3

1.14.22 Acknowledgements
------------------------

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: What's New in Python 2 2,  Next: What's New in Python 2 1,  Prev: What's New in Python 2 3,  Up: Python 有什麼新功能？

1.15 What’s New in Python 2.2
=============================


Author: A.M. Kuchling

* Menu:

* 簡介::
* PEPs 252 and 253; Type and Class Changes: PEPs 252 and 253 Type and Class Changes.
* PEP 234; Iterators: PEP 234 Iterators.
* 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 Changes::
* PEP 227; Nested Scopes: PEP 227 Nested Scopes.
* New and Improved Modules: New and Improved Modules<3>.
* Interpreter Changes and Fixes::
* Other Changes and Fixes: Other Changes and Fixes<3>.
* Acknowledgements: Acknowledgements<6>.


File: python.info,  Node: 簡介,  Next: PEPs 252 and 253 Type and Class Changes,  Up: What's New in Python 2 2

1.15.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 Iterators,  Prev: 簡介,  Up: What's New in Python 2 2

1.15.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 ‘UserList’ 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__(): 31f. 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 Related
Links: e2c, "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::
* Related Links::


File: python.info,  Node: Old and New Classes,  Next: Descriptors,  Up: PEPs 252 and 253 Type and Class Changes

1.15.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: 2b1, 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: 2b1.:

     class C(object):
         def __init__ (self):
             ...
         ...

This means that *note class: c6f. 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: 2b1.)

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(): 185, *note float(): 188, and *note str(): 335.  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(): 1b9. 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://www.python.org/dev/peps/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.15.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__: 501. of an object, but
when class inheritance or an arbitrary *note __getattr__(): 31f. 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__: c6c. is the attribute’s name.

   * ‘__doc__’ is the attribute’s 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(): 1da. 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.15.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():
4e7, 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(): 4e7. 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://www.python.org/dev/peps/pep-0253


File: python.info,  Node: Attribute Access,  Next: Related Links,  Prev: Multiple Inheritance The Diamond Rule,  Up: PEPs 252 and 253 Type and Class Changes

1.15.2.4 Attribute Access
.........................

A fair number of sophisticated Python classes define hooks for attribute
access using *note __getattr__(): 31f.; 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__(): 44e. is `always' called whenever any
attribute is accessed, while the old *note __getattr__(): 31f. 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 *note __getattr__(): 31f.
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__: 501.  *note __getattr__(): 31f. methods also
end up being called by Python when it checks for other methods such as
*note __repr__(): 343. 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: 1d8. 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 *note
__getattr__(): 31f./*note __setattr__(): e31. methods that check for the
‘size’ attribute and handle it specially while retrieving all other
attributes from the instance’s *note __dict__: 501.  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__: e32. 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__: e32. 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: 3a0. on the attempt to assign
to an attribute not listed in *note __slots__: e32.


File: python.info,  Node: Related Links,  Prev: Attribute Access,  Up: PEPs 252 and 253 Type and Class Changes

1.15.2.5 Related Links
......................

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?

‘https://docs.python.org/dev/howto/descriptor.html’ 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://www.python.org/dev/peps/pep-0252

   (2) https://www.python.org/dev/peps/pep-0253

   (3) https://www.python.org/dev/peps/pep-0252

   (4) https://www.python.org/dev/peps/pep-0253

   (5) https://www.python.org/dev/peps/pep-0253


File: python.info,  Node: PEP 234 Iterators,  Next: PEP 255 Simple Generators<2>,  Prev: PEPs 252 and 253 Type and Class Changes,  Up: What's New in Python 2 2

1.15.3 PEP 234: Iterators
-------------------------

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__(): 27d. method that looks
something like this:

     def __getitem__(self, index):
         return <next item>

*note __getitem__(): 27d. 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: c35. 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__(): 27d. calls will be made with `index' incrementing by one
each time.  In other words, the presence of the *note __getitem__():
27d. 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__(): 27d. 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 *note __iter__(): 514. 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: e35. function in order
to return an iterator, and extension types that want to behave as
iterators can define a *note tp_iternext: e36. function.

So, after all this, what do iterators actually do?  They have one
required method, *note next(): 687, which takes no arguments and returns
the next value.  When there are no more values to be returned, calling
*note next(): 687. should raise the *note StopIteration: 48b. 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: c35. statement no longer expects a sequence;
it expects something for which *note iter(): d2c. will return an
iterator.  For backward compatibility and convenience, an iterator is
automatically constructed for sequences that don’t implement *note
__iter__(): 514. or a *note tp_iter: e35. 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(): d2c. 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: 7a8. 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(): df.
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(): 687. method.

也參考
......

PEP 234(1) - Iterators

     Written by Ka-Ping Yee and GvR; implemented by the Python Labs
     crew, mostly by GvR and Tim Peters.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0234


File: python.info,  Node: PEP 255 Simple Generators<2>,  Next: PEP 237 Unifying Long Integers and Integers<2>,  Prev: PEP 234 Iterators,  Up: What's New in Python 2 2

1.15.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: 191.
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: 190, 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: 190. statement, the generator
outputs the value of ‘i’, similar to a *note return: 191. 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: d77...*note
finally: 183. 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: 191. 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: 48b. 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(): 687. 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://www.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://www.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: dec. 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://www.python.org/dev/peps/pep-0255

   (2) https://www.python.org/dev/peps/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: What's New in Python 2 2

1.15.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: 193. 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: 965. 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(): 60d.
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://www.python.org/dev/peps/pep-0237


File: python.info,  Node: PEP 238 Changing the Division Operator,  Next: Unicode Changes,  Prev: PEP 237 Unifying Long Integers and Integers<2>,  Up: What's New in Python 2 2

1.15.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__(): 78b. and
     *note __floordiv__(): e3a. to overload the two division operators.
     At the C level, there are also slots in the *note PyNumberMethods:
     d86. 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://www.python.org/dev/peps/pep-0238

   (2) https://www.python.org/dev/peps/pep-0238

   (3) https://www.python.org/dev/peps/pep-0238


File: python.info,  Node: Unicode Changes,  Next: PEP 227 Nested Scopes,  Prev: PEP 238 Changing the Division Operator,  Up: What's New in Python 2 2

1.15.7 Unicode Changes
----------------------

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: 1fc.
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: 145. 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 *note __str__(): e3c.

‘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) - Support for ’wide’ Unicode characters

     Written by Paul Prescod.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0261

   (2) https://www.python.org/dev/peps/pep-0261


File: python.info,  Node: PEP 227 Nested Scopes,  Next: New and Improved Modules<3>,  Prev: Unicode Changes,  Up: What's New in Python 2 2

1.15.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: d80. 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: c34. 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: dc3, *note class: c6f, or
*note import: c22. 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: c34. expressions with
free variables, the compiler will flag this by raising a *note
SyntaxError: 45d. 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://www.python.org/dev/peps/pep-0227


File: python.info,  Node: New and Improved Modules<3>,  Next: Interpreter Changes and Fixes,  Prev: PEP 227 Nested Scopes,  Up: What's New in Python 2 2

1.15.9 New and Improved Modules
-------------------------------

   * The ‘xmlrpclib’ 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 ‘SimpleXMLRPCServer’ 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: 8f. 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 ‘tm_year’.  The
     enhanced functions include *note stat(): f5, ‘fstat()’,
     ‘statvfs()’, and ‘fstatvfs()’ in the *note os: c5. module, and
     ‘localtime()’, ‘gmtime()’, and ‘strptime()’ in the *note time: 10b.
     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: f0. 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: f9.
     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(): 577. that uses the *note pydoc: da. module
     introduced in Python 2.1 to provide interactive help.
     ‘help(object)’ displays any available help text about `object'.
     *note help(): 577. 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: da. module.)

   * Various bugfixes and performance improvements have been made to the
     SRE engine underlying the *note re: de. module.  For example, the
     *note re.sub(): 480. and *note re.split(): 3cf. functions have been
     rewritten in C. Another contributed patch speeds up certain Unicode
     character ranges by a factor of two, and a new ‘finditer()’ 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: ee. 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: ee. also supports SMTP authentication.
     (Contributed by Gerhard Häring.)

   * The *note imaplib: 98. 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: 69, 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: 37. 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: f7. 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: b3. module now makes it easier to use
     alternative MIME-type databases by the addition of a ‘MimeTypes’
     class, which takes a list of filenames to be parsed.  (Contributed
     by Fred L. Drake, Jr.)

   * A ‘Timer’ class was added to the *note threading: 10a. module that
     allows scheduling an activity to happen at some future time.
     (Contributed by Itamar Shtull-Trauring.)

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2104.html

   (2) https://tools.ietf.org/html/rfc2487.html

   (3) https://tools.ietf.org/html/rfc2342.html

   (4) https://tools.ietf.org/html/rfc2822.html

   (5) https://tools.ietf.org/html/rfc822.html


File: python.info,  Node: Interpreter Changes and Fixes,  Next: Other Changes and Fixes<3>,  Prev: New and Improved Modules<3>,  Up: What's New in Python 2 2

1.15.10 Interpreter Changes and Fixes
-------------------------------------

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(): e40. and *note PyEval_SetTrace(): e41.  The
     existing *note sys.setprofile(): e42. and *note sys.settrace():
     e43. 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 implementors of
     Python debuggers and development tools, was added.  *note
     PyInterpreterState_Head(): e44. and *note
     PyInterpreterState_Next(): e45. let a caller walk through all the
     existing interpreter objects; *note
     PyInterpreterState_ThreadHead(): e46. and *note
     PyThreadState_Next(): e47. 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:

   * Rename ‘Py_TPFLAGS_GC()’ to ‘PyTPFLAGS_HAVE_GC()’.

   * 
     Use *note PyObject_GC_New(): 2d5. or *note PyObject_GC_NewVar(): 2d6. to allocate

          objects, and *note PyObject_GC_Del(): e48. to deallocate them.

   * 
     Rename ‘PyObject_GC_Init()’ to *note PyObject_GC_Track(): e49. and

          ‘PyObject_GC_Fini()’ to *note PyObject_GC_UnTrack(): e4a.

   * 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():
     26b.; ‘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():
     e4b, 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*: 4bf. variables that will be filled in with
     argument values.

   * Two new flags *note METH_NOARGS: e1d. and *note METH_O: e4c. 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: e4d.  Also, the old ‘METH_OLDARGS’
     style of writing C methods is now officially deprecated.

   * Two new wrapper functions, *note PyOS_snprintf(): e4e. and *note
     PyOS_vsnprintf(): e4f. 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(): e50. 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: Other Changes and Fixes<3>,  Next: Acknowledgements<6>,  Prev: Interpreter Changes and Fixes,  Up: What's New in Python 2 2

1.15.11 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 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.

Some of the more notable changes are:

   * 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: 193. 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: e52. exception has
     therefore moved from the *note weakref: 129. 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(): 1b5, 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: 7a8. 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(): e53. and *note
     sys.setdlopenflags(): a6b. functions.  (Contributed by Bram Stolk.)

   * The *note pow(): 19b. 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: 193. exception.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0264


File: python.info,  Node: Acknowledgements<6>,  Prev: Other Changes and Fixes<3>,  Up: What's New in Python 2 2

1.15.12 Acknowledgements
------------------------

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: What's New in Python 2 1,  Next: What's New in Python 2 0,  Prev: What's New in Python 2 2,  Up: Python 有什麼新功能？

1.16 What’s New in Python 2.1
=============================


Author: 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<4>.
* Acknowledgements: Acknowledgements<7>.


File: python.info,  Node: 簡介<2>,  Next: PEP 227 Nested Scopes<2>,  Up: What's New in Python 2 1

1.16.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: What's New in Python 2 1

1.16.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: d80. 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: c34. expression
clumsier, and this was a problem in practice.  In code which uses *note
lambda: c34. 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: dc3, *note class: c6f, or
*note import: c22. 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: c34. expressions with
free variables, the compiler will flag this by raising a *note
SyntaxError: 45d. 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://www.python.org/dev/peps/pep-0236

   (2) https://www.python.org/dev/peps/pep-0236

   (3) https://www.python.org/dev/peps/pep-0227


File: python.info,  Node: PEP 236 __future__ Directives,  Next: PEP 207 Rich Comparisons,  Prev: PEP 227 Nested Scopes<2>,  Up: What's New in Python 2 1

1.16.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: c22. 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://www.python.org/dev/peps/pep-0236


File: python.info,  Node: PEP 207 Rich Comparisons,  Next: PEP 230 Warning Framework,  Prev: PEP 236 __future__ Directives,  Up: What's New in Python 2 1

1.16.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:

Operation       Method name
                
-------------------------------------
                
‘<’             *note __lt__(): c39.
                
                
‘<=’            *note __le__(): ca5.
                
                
‘>’             *note __gt__(): ca6.
                
                
‘>=’            *note __ge__(): ca7.
                
                
‘==’            *note __eq__(): 344.
                
                
‘!=’            *note __ne__(): e5b.
                

(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://www.python.org/dev/peps/pep-0207

   (2) https://www.python.org/dev/peps/pep-0207


File: python.info,  Node: PEP 230 Warning Framework,  Next: PEP 229 New Build System,  Prev: PEP 207 Rich Comparisons,  Up: What's New in Python 2 1

1.16.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: 127. 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(): e5d.
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: de. 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: 279. 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://www.python.org/dev/peps/pep-0005

   (2) https://www.python.org/dev/peps/pep-0230


File: python.info,  Node: PEP 229 New Build System,  Next: PEP 205 Weak References,  Prev: PEP 230 Warning Framework,  Up: What's New in Python 2 1

1.16.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://www.python.org/dev/peps/pep-0229


File: python.info,  Node: PEP 205 Weak References,  Next: PEP 232 Function Attributes,  Prev: PEP 229 New Build System,  Up: What's New in Python 2 1

1.16.7 PEP 205: Weak References
-------------------------------

Weak references, available through the *note weakref: 129. 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: 129. 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://www.python.org/dev/peps/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: What's New in Python 2 1

1.16.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 ‘__doc__’ 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__: 501.  Unlike the *note __dict__: 501. attribute of class
instances, in functions you can actually assign a new dictionary to
*note __dict__: 501, 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://www.python.org/dev/peps/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: What's New in Python 2 1

1.16.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: c22. 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: 339. 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: e62. 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: What's New in Python 2 1

1.16.10 PEP 217: Interactive Display Hook
-----------------------------------------

When using the Python interpreter interactively, the output of commands
is displayed using the built-in *note repr(): 7d1. function.  In Python
2.1, the variable *note sys.displayhook(): e64. can be set to a callable
object which will be called instead of *note repr(): 7d1.  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://www.python.org/dev/peps/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: What's New in Python 2 1

1.16.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: 193. 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: 193, 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://www.python.org/dev/peps/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: What's New in Python 2 1

1.16.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 ‘http://www.vex.net/parnassus/’ are the largest catalog of
Python modules, but registering software at the Vaults is optional, and
many people don’t 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(1)
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(2), 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(3) - Metadata for Python Software Packages

     Written and implemented by A.M. Kuchling.

PEP 243(4) - 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://www.python.org/dev/peps/pep-0241

   (2) https://www.python.org/dev/peps/pep-0241

   (3) https://www.python.org/dev/peps/pep-0241

   (4) https://www.python.org/dev/peps/pep-0243


File: python.info,  Node: New and Improved Modules<4>,  Next: Other Changes and Fixes<4>,  Prev: PEP 241 Metadata in Python Packages,  Up: What's New in Python 2 1

1.16.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: 67. 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 ‘http://pyunit.sourceforge.net/’
     for more information about PyUnit.

   * The *note difflib: 37. module contains a class, ‘SequenceMatcher’,
     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: 2e, 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: 134.
     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(): e68. can be set to a callable
     object.  When an exception isn’t caught by any *note try:
     d77...*note except: b43. blocks, the exception will be passed to
     *note sys.excepthook(): e68, 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: 10b. module, such as
     ‘asctime()’ and ‘localtime()’, 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: 84. 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: 84. 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:
     f0. module, contributed by Grant Edwards.

   * The *note pstats: d5. 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(): e69. 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<4>,  Next: Acknowledgements<7>,  Prev: New and Improved Modules<4>,  Up: What's New in Python 2 1

1.16.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 ‘PyMem_New()’, it
     has to be freed using ‘PyMem_Del()’, 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(): df.
     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, ‘popitem()’, 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: fe. or *note
     string: f7, ‘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(): 7d1. 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
     ‘PyImport_ImportModule()’, 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: Acknowledgements<7>,  Prev: Other Changes and Fixes<4>,  Up: What's New in Python 2 1

1.16.15 Acknowledgements
------------------------

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: What's New in Python 2 0,  Next: Changelog（更動日誌）,  Prev: What's New in Python 2 1,  Up: Python 有什麼新功能？

1.17 What’s New in Python 2.0
=============================


Author: A.M. Kuchling and 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 Modules::
* Module changes::
* New modules::
* IDLE Improvements::
* Deleted and Deprecated Modules::
* Acknowledgements: Acknowledgements<8>.


File: python.info,  Node: 簡介<3>,  Next: What About Python 1 6?,  Up: What's New in Python 2 0

1.17.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: What's New in Python 2 0

1.17.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: What's New in Python 2 0

1.17.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://www.python.org/dev/peps/’.  As of
September 2000, there are 25 PEPS, ranging from PEP 201(3), "Lockstep
Iteration", to PEP 225, "Elementwise/Objectwise Operators".

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0001

   (2) https://www.python.org/dev/peps/pep-0001

   (3) https://www.python.org/dev/peps/pep-0201


File: python.info,  Node: Unicode<2>,  Next: 串列綜合運算（List Comprehension）,  Prev: New Development Process,  Up: What's New in Python 2 0

1.17.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 ‘\xHHHH’ 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: 11b, 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: 1c. 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()’, *note readline(): df, 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:
de. 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://www.python.org/dev/peps/pep-0100


File: python.info,  Node: 串列綜合運算（List Comprehension）,  Next: Augmented Assignment,  Prev: Unicode<2>,  Up: What's New in Python 2 0

1.17.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(): c32. and *note filter(): c33. 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: c34. 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:

     # Syntax error
     [ x,y for x in seq1 for y in seq2]
     # Correct
     [ (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: What's New in Python 2 0

1.17.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 *note __iadd__(): e74, *note __isub__(): e75, 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 *note __iadd__(): e74. 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: What's New in Python 2 0

1.17.7 String Methods
---------------------

Until now string-manipulation functionality was in the *note string: f7.
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: f7. 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: f7. 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: What's New in Python 2 0

1.17.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: 86. 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: What's New in Python 2 0

1.17.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.17.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(): 7d1. 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(): 335. 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: 7a8. 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: e7a. is encountered.  Moshe Zadka
contributed a patch which adds a *note __contains__(): d2d. 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
‘http://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: d80. 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: d80. exception is
raised, while 2.0 raises a new *note UnboundLocalError: e7b. exception.
*note UnboundLocalError: e7b. is a subclass of *note NameError: d80, so
any existing code that expects *note NameError: d80. to be raised should
still work.

     def f():
         print "i=",i
         i = i + 1
     f()

Two new exceptions, *note TabError: e7c. and *note IndentationError:
e7d, have been introduced.  They’re both subclasses of *note
SyntaxError: 45d, 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.17.9.2 Changes to Built-in Functions
......................................

A new built-in, ‘zip(seq1, seq2, ...)’, has been added.  *note zip():
c37. returns a list of tuples where each tuple contains the i-th element
from each of the argument sequences.  The difference between *note
zip(): c37. and ‘map(None, seq1, seq2)’ is that *note map(): c32. pads
the sequences with ‘None’ if the sequences aren’t all of the same
length, while *note zip(): c37. truncates the returned list to the
length of the shortest argument sequence.

The *note int(): 185. 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: 193. 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: fe. 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(): e7f. and *note sys.setrecursionlimit(): e80.
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: What's New in Python 2 0

1.17.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: 193. 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 ‘PyArg_ParseTuple()’, 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: f0. 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.
‘socket.connect_ex()’ and ‘socket.bind()’ 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: f0.
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: 3a0. and *note NameError: d80. 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: 193.  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(): 335. of
a long integer no longer has a trailing ’L’ character, though *note
repr(): 7d1. 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(): 7d1. of a float now uses a different formatting
precision than *note str(): 335.  *note repr(): 7d1. uses ‘%.17g’ format
string for C’s ‘sprintf()’, while *note str(): 335. uses ‘%.12g’ as
before.  The effect is that *note repr(): 7d1. may occasionally show
more decimal places than *note str(): 335, 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: What's New in Python 2 0

1.17.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(): 454. and *note issubclass(): 455.  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:
‘PyModule_AddObject()’, ‘PyModule_AddIntConstant()’, and
‘PyModule_AddStringConstant()’.  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.  ‘PyOS_getsig()’
gets a signal handler and ‘PyOS_setsig()’ will set a new handler.


File: python.info,  Node: Distutils Making Modules Easy to Install,  Next: XML Modules,  Prev: Extending/Embedding Changes,  Up: What's New in Python 2 0

1.17.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 *note distutils: 39. 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 Modules,  Next: Module changes,  Prev: Distutils Making Modules Easy to Install,  Up: What's New in Python 2 0

1.17.13 XML Modules
-------------------

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: 134. 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 Support::
* DOM Support::
* Relationship to PyXML::


File: python.info,  Node: SAX2 Support,  Next: DOM Support,  Up: XML Modules

1.17.13.1 SAX2 Support
......................

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 ‘startElement()’ and
‘endElement()’ methods are called for every starting and end tag
encountered by the parser, the ‘characters()’ 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 ‘http://pyxml.sourceforge.net/topics/howto/xml-howto.html’.


File: python.info,  Node: DOM Support,  Next: Relationship to PyXML,  Prev: SAX2 Support,  Up: XML Modules

1.17.13.2 DOM Support
.....................

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: 136. 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 Support,  Up: XML Modules

1.17.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: 134. package.

The answer is that Python 2.0’s *note xml: 134. 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: 134. 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: Module changes,  Next: New modules,  Prev: XML Modules,  Up: What's New in Python 2 0

1.17.14 Module changes
----------------------

Lots of improvements and bugfixes were made to Python’s extensive
standard library; some of the affected modules include *note readline:
df, ‘ConfigParser’, *note cgi: 16, *note calendar: 15, *note posix: d2,
*note readline: df, ‘xmllib’, *note aifc: 5, ‘chunk, wave’, *note
random: dd, *note shelve: e8, and *note nntplib: c1.  Consult the CVS
logs for the exact patch-by-patch details.

Brian Gallew contributed OpenSSL support for the *note socket: f0.
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: f0. module: ‘socket.ssl(socket,
keyfile, certfile)’, which takes a socket object and returns an SSL
socket.  The ‘httplib’ and *note urllib: 11e. modules were also changed
to support ‘https://’ URLs, though no one has implemented FTP or SMTP
over SSL.

The ‘httplib’ 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: 2c. 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: de. 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: New modules,  Next: IDLE Improvements,  Prev: Module changes,  Up: What's New in Python 2 0

1.17.15 New modules
-------------------

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: c.: 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: c. module
     instead, importing *note atexit: c. and calling *note
     atexit.register(): e8a. with the function to be called on exit.
     (Contributed by Skip Montanaro.)

   * *note codecs: 1c, ‘encodings’, *note unicodedata: 11b.: Added as
     part of the new Unicode support.

   * *note filecmp: 7f.: Supersedes the old ‘cmp’, ‘cmpcache’ and
     ‘dircmp’ modules, which have now become deprecated.  (Contributed
     by Gordon MacMillan and Moshe Zadka.)

   * *note gettext: 89.: 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: b4.: 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: de.
     module.  (Contributed by Sam Rushing, with some extensions by A.M.
     Kuchling.)

   * ‘pyexpat’: An interface to the Expat XML parser.  (Contributed by
     Paul Prescod.)

   * ‘robotparser’: 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: 101.: 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: 12a.: 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: 11e. 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.)

   * ‘_winreg’: 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: 143.: 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: 8c. 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: New modules,  Up: What's New in Python 2 0

1.17.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: Acknowledgements<8>,  Prev: IDLE Improvements,  Up: What's New in Python 2 0

1.17.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: Acknowledgements<8>,  Prev: Deleted and Deprecated Modules,  Up: What's New in Python 2 0

1.17.18 Acknowledgements
------------------------

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.

The "Changelog" is an HTML version of the file built(1) from the
contents of the Misc/NEWS.d(2) directory tree, which contains `all'
nontrivial changes to Python for the current version.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/blurb

   (2) https://github.com/python/cpython/tree/3.8/Misc/NEWS.d


File: python.info,  Node: Changelog（更動日誌）,  Prev: What's New in Python 2 0,  Up: Python 有什麼新功能？

1.18 Changelog（更動日誌）
==========================

* Menu:

* Python 3.8.11 final: Python 3 8 11 final.
* Python 3.8.10 final: Python 3 8 10 final.
* Python 3.8.9 final: Python 3 8 9 final.
* Python 3.8.8 final: Python 3 8 8 final.
* Python 3.8.8 release candidate 1: Python 3 8 8 release candidate 1.
* Python 3.8.7 final: Python 3 8 7 final.
* Python 3.8.7 release candidate 1: Python 3 8 7 release candidate 1.
* Python 3.8.6 final: Python 3 8 6 final.
* Python 3.8.6 release candidate 1: Python 3 8 6 release candidate 1.
* Python 3.8.5 final: Python 3 8 5 final.
* Python 3.8.4 final: Python 3 8 4 final.
* Python 3.8.4 release candidate 1: Python 3 8 4 release candidate 1.
* Python 3.8.3 final: Python 3 8 3 final.
* Python 3.8.3 release candidate 1: Python 3 8 3 release candidate 1.
* Python 3.8.2 final: Python 3 8 2 final.
* Python 3.8.2 release candidate 2: Python 3 8 2 release candidate 2.
* Python 3.8.2 release candidate 1: Python 3 8 2 release candidate 1.
* Python 3.8.1 final: Python 3 8 1 final.
* Python 3.8.1 release candidate 1: Python 3 8 1 release candidate 1.
* Python 3.8.0 final: Python 3 8 0 final.
* Python 3.8.0 release candidate 1: Python 3 8 0 release candidate 1.
* Python 3.8.0 beta 4: Python 3 8 0 beta 4.
* Python 3.8.0 beta 3: Python 3 8 0 beta 3.
* Python 3.8.0 beta 2: Python 3 8 0 beta 2.
* 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 3 8 11 final,  Next: Python 3 8 10 final,  Up: Changelog（更動日誌）

1.18.1 Python 3.8.11 final
--------------------------

`Release date: 2021-06-28'

* Menu:

* Security::
* Core and Builtins::
* Library::


File: python.info,  Node: Security,  Next: Core and Builtins,  Up: Python 3 8 11 final

1.18.1.1 Security
.................

   - bpo-44022(1): mod:*note http.client: 94. now avoids infinitely
     reading potential HTTP headers after a ‘100 Continue’ status
     response from the server.

   - bpo-43882(2): 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(): 120. now removes ASCII newlines and tabs from
     URLs, preventing such attacks.

   - bpo-42800(3): Audit hooks are now fired for frame.f_code,
     traceback.tb_frame, and generator code/frame attribute access.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue44022

   (2) https://bugs.python.org/issue43882

   (3) https://bugs.python.org/issue42800


File: python.info,  Node: Core and Builtins,  Next: Library,  Prev: Security,  Up: Python 3 8 11 final

1.18.1.2 Core and Builtins
..........................

   - bpo-44070(1): No longer eagerly makes import filenames absolute,
     except for extension modules, which was introduced in 3.8.10.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue44070


File: python.info,  Node: Library,  Prev: Core and Builtins,  Up: Python 3 8 11 final

1.18.1.3 Library
................

   - bpo-44061(1): Fix regression in previous release when calling *note
     pkgutil.iter_modules(): 611. with a list of *note pathlib.Path:
     202. objects

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue44061


File: python.info,  Node: Python 3 8 10 final,  Next: Python 3 8 9 final,  Prev: Python 3 8 11 final,  Up: Changelog（更動日誌）

1.18.2 Python 3.8.10 final
--------------------------

`Release date: 2021-05-03'

* Menu:

* Security: Security<2>.
* Core and Builtins: Core and Builtins<2>.
* Library: Library<2>.
* Documentation: Documentation<2>.
* Tests::
* Windows::
* macOS::
* IDLE: IDLE<3>.
* C API::


File: python.info,  Node: Security<2>,  Next: Core and Builtins<2>,  Up: Python 3 8 10 final

1.18.2.1 Security
.................

   - bpo-43434(1): Creating a *note sqlite3.Connection: 3dd. object now
     also produces a ‘sqlite3.connect’ *note auditing event: e96.
     Previously this event was only produced by *note sqlite3.connect():
     3df. calls.  Patch by Erlend E. Aasland.

   - bpo-43472(2): Ensures interpreter-level audit hooks receive the
     ‘cpython.PyInterpreterState_New’ event when called through the
     ‘_xxsubinterpreters’ module.

   - bpo-43075(3): Fix Regular Expression Denial of Service (ReDoS)
     vulnerability in *note urllib.request.AbstractBasicAuthHandler:
     e97.  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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43434

   (2) https://bugs.python.org/issue43472

   (3) https://bugs.python.org/issue43075


File: python.info,  Node: Core and Builtins<2>,  Next: Library<2>,  Prev: Security<2>,  Up: Python 3 8 10 final

1.18.2.2 Core and Builtins
..........................

   - bpo-43105(1): Importlib now resolves relative paths when creating
     module spec objects from file locations.

   - bpo-42924(2): 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).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43105

   (2) https://bugs.python.org/issue42924


File: python.info,  Node: Library<2>,  Next: Documentation<2>,  Prev: Core and Builtins<2>,  Up: Python 3 8 10 final

1.18.2.3 Library
................

   - bpo-43993(1): Update bundled pip to 21.1.1.

   - bpo-43937(2): Fixed the *note turtle: 117. module working with
     non-default root window.

   - bpo-43930(3): Update bundled pip to 21.1 and setuptools to 56.0.0

   - bpo-43920(4): OpenSSL 3.0.0: *note load_verify_locations(): 7f0.
     now returns a consistent error message when cadata contains no
     valid certificate.

   - bpo-43607(5): *note urllib: 11e. can now convert Windows paths with
     ‘\\?\’ prefixes into URL paths.

   - bpo-43284(6): 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-42248(7): [Enum] ensure exceptions raised in ‘_missing__’ are
     released

   - bpo-43799(8): OpenSSL 3.0.0: define ‘OPENSSL_API_COMPAT’ 1.1.1 to
     suppress deprecation warnings.  Python requires OpenSSL 1.1.1 APIs.

   - bpo-43794(9): Add *note ssl.OP_IGNORE_UNEXPECTED_EOF: e9a.
     constants (OpenSSL 3.0.0)

   - bpo-43789(10): OpenSSL 3.0.0: Don’t call the password callback
     function a second time when first call has signaled an error
     condition.

   - bpo-43788(11): The header files for *note ssl: f4. 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-43655(12): *note tkinter: 10d. dialog windows are now
     recognized as dialogs by window managers on macOS and X Window.

   - bpo-43534(13): *note turtle.textinput(): e9b. and *note
     turtle.numinput(): e9c. create now a transient window working on
     behalf of the canvas window.

   - bpo-43522(14): Fix problem with *note hostname_checks_common_name:
     3e3.  OpenSSL does not copy hostflags from `struct SSL_CTX' to
     `struct SSL'.

   - bpo-42967(15): Allow *note bytes: 336. ‘separator’ argument in
     ‘urllib.parse.parse_qs’ and ‘urllib.parse.parse_qsl’ when parsing
     *note str: 335. query strings.  Previously, this raised a
     ‘TypeError’.

   - bpo-43176(16): Fixed processing of a dataclass that inherits from a
     frozen dataclass with no fields.  It is now correctly detected as
     an error.

   - bpo-34463(17): Fixed discrepancy between *note traceback: 114. and
     the interpreter in formatting of SyntaxError with lineno not set
     (*note traceback: 114. was changed to match interpreter).

   - bpo-41735(18): Fix thread locks in zlib module may go wrong in rare
     case.  Patch by Ma Lin.

   - bpo-26053(19): Fixed bug where the *note pdb: ca. interactive run
     command echoed the args from the shell command line, even if those
     have been overridden at the pdb prompt.

   - bpo-36470(20): Fix dataclasses with ‘InitVar’s and *note replace():
     e9d.  Patch by Claudiu Popa.

   - bpo-28577(21): 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-32745(22): Fix a regression in the handling of ctypes’ *note
     ctypes.c_wchar_p: e9e. type: embedded null characters would cause a
     *note ValueError: 1fc. to be raised.  Patch by Zackery Spytz.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43993

   (2) https://bugs.python.org/issue43937

   (3) https://bugs.python.org/issue43930

   (4) https://bugs.python.org/issue43920

   (5) https://bugs.python.org/issue43607

   (6) https://bugs.python.org/issue43284

   (7) https://bugs.python.org/issue42248

   (8) https://bugs.python.org/issue43799

   (9) https://bugs.python.org/issue43794

   (10) https://bugs.python.org/issue43789

   (11) https://bugs.python.org/issue43788

   (12) https://bugs.python.org/issue43655

   (13) https://bugs.python.org/issue43534

   (14) https://bugs.python.org/issue43522

   (15) https://bugs.python.org/issue42967

   (16) https://bugs.python.org/issue43176

   (17) https://bugs.python.org/issue34463

   (18) https://bugs.python.org/issue41735

   (19) https://bugs.python.org/issue26053

   (20) https://bugs.python.org/issue36470

   (21) https://bugs.python.org/issue28577

   (22) https://bugs.python.org/issue32745


File: python.info,  Node: Documentation<2>,  Next: Tests,  Prev: Library<2>,  Up: Python 3 8 10 final

1.18.2.4 Documentation
......................

   - bpo-43959(1): The documentation on the PyContextVar C-API was
     clarified.

   - bpo-43938(2): Update dataclasses documentation to express that
     FrozenInstanceError is derived from AttributeError.

   - bpo-43739(3): 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/issue43959

   (2) https://bugs.python.org/issue43938

   (3) https://bugs.python.org/issue43739


File: python.info,  Node: Tests,  Next: Windows,  Prev: Documentation<2>,  Up: Python 3 8 10 final

1.18.2.5 Tests
..............

   - bpo-43842(1): 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-43811(2): Tests multiple OpenSSL versions on GitHub Actions.
     Use ccache to speed up testing.

   - bpo-43791(3): 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/issue43842

   (2) https://bugs.python.org/issue43811

   (3) https://bugs.python.org/issue43791


File: python.info,  Node: Windows,  Next: macOS,  Prev: Tests,  Up: Python 3 8 10 final

1.18.2.6 Windows
................

   - bpo-35306(1): Avoid raising errors from *note
     pathlib.Path.exists(): 203. when passed an invalid filename.

   - bpo-38822(2): Fixed *note os.stat(): 1f2. 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(): 1f7. and *note os.path.isdir(): 1f9.

   - bpo-26227(3): Fixed decoding of host names in *note
     socket.gethostbyaddr(): ea2. and *note socket.gethostbyname_ex():
     ea3.

   - bpo-43745(4): Actually updates Windows release to OpenSSL 1.1.1k.
     Earlier releases were mislabelled and actually included 1.1.1i
     again.

   - bpo-43492(5): Upgrade Windows installer to use SQLite 3.35.5.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35306

   (2) https://bugs.python.org/issue38822

   (3) https://bugs.python.org/issue26227

   (4) https://bugs.python.org/issue43745

   (5) https://bugs.python.org/issue43492


File: python.info,  Node: macOS,  Next: IDLE<3>,  Prev: Windows,  Up: Python 3 8 10 final

1.18.2.7 macOS
..............

   - bpo-44009(1): 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-41100(2): 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 also available to natively support both ‘ARM64’
     and ‘Intel 64’ in one set of executables.  This backport from
     Python 3.9 does not include support for "weaklinking"; to support a
     range of macOS versions, continue to target for and build on the
     oldest version in the range; for 3.8.x, the ‘universal2’ variant is
     only useful on macOS 11 or later.

   - bpo-43492(3): Update macOS installer to use SQLite 3.35.4.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue44009

   (2) https://bugs.python.org/issue41100

   (3) https://bugs.python.org/issue43492


File: python.info,  Node: IDLE<3>,  Next: C API,  Prev: macOS,  Up: Python 3 8 10 final

1.18.2.8 IDLE
.............

   - bpo-43655(1): IDLE dialog windows are now recognized as dialogs by
     window managers on macOS and X Window.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43655


File: python.info,  Node: C API,  Prev: IDLE<3>,  Up: Python 3 8 10 final

1.18.2.9 C API
..............

   - bpo-43962(1): _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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43962


File: python.info,  Node: Python 3 8 9 final,  Next: Python 3 8 8 final,  Prev: Python 3 8 10 final,  Up: Changelog（更動日誌）

1.18.3 Python 3.8.9 final
-------------------------

`Release date: 2021-04-02'

* Menu:

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


File: python.info,  Node: Security<3>,  Next: Core and Builtins<3>,  Up: Python 3 8 9 final

1.18.3.1 Security
.................

   - bpo-42988(1): CVE-2021-3426: Remove the ‘getfile’ feature of the
     *note pydoc: da. 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(2): *note ftplib: 84. 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: 2f1. instances to ‘True’ to re-enable it.

   - bpo-43439(3): Add audit hooks for *note gc.get_objects(): 1ce,
     *note gc.get_referrers(): ea9. and *note gc.get_referents(): eaa.
     Patch by Pablo Galindo.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42988

   (2) https://bugs.python.org/issue43285

   (3) https://bugs.python.org/issue43439


File: python.info,  Node: Core and Builtins<3>,  Next: Library<3>,  Prev: Security<3>,  Up: Python 3 8 9 final

1.18.3.2 Core and Builtins
..........................

   - bpo-43660(1): 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-35883(2): Python no longer fails at startup with a fatal error
     if a command line argument contains an invalid Unicode character.
     The *note Py_DecodeLocale(): 441. function now escapes byte
     sequences which would be decoded as Unicode characters outside the
     [U+0000; U+10ffff] range.

   - bpo-43406(3): Fix a possible race condition where
     ‘PyErr_CheckSignals’ tries to execute a non-Python signal handler.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43660

   (2) https://bugs.python.org/issue35883

   (3) https://bugs.python.org/issue43406


File: python.info,  Node: Library<3>,  Next: Documentation<3>,  Prev: Core and Builtins<3>,  Up: Python 3 8 9 final

1.18.3.3 Library
................

   - bpo-35930(1): Raising an exception raised in a "future" instance
     will create reference cycles.

   - bpo-43577(2): Fix deadlock when using *note ssl.SSLContext: 3e9.
     debug callback with *note ssl.SSLContext.sni_callback(): ead.

   - bpo-43423(3): ‘subprocess.communicate()’ no longer raises an
     IndexError when there is an empty stdout or stderr IO buffer during
     a timeout on Windows.

   - bpo-27820(4): 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-43399(5): Fix ‘ElementTree.extend’ not working on iterators
     when using the Python implementation

   - bpo-43316(6): 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-43260(7): Fix TextIOWrapper can not flush internal buffer
     forever after very large text is written.

   - bpo-42782(8): Fail fast in *note shutil.move(): 25c. to avoid
     creating destination directories on failure.

   - bpo-37193(9): Fixed memory leak in ‘socketserver.ThreadingMixIn’
     introduced in Python 3.7.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35930

   (2) https://bugs.python.org/issue43577

   (3) https://bugs.python.org/issue43423

   (4) https://bugs.python.org/issue27820

   (5) https://bugs.python.org/issue43399

   (6) https://bugs.python.org/issue43316

   (7) https://bugs.python.org/issue43260

   (8) https://bugs.python.org/issue42782

   (9) https://bugs.python.org/issue37193


File: python.info,  Node: Documentation<3>,  Next: Tests<2>,  Prev: Library<3>,  Up: Python 3 8 9 final

1.18.3.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():
     774, *note time.perf_counter(): 2ab, *note time.process_time():
     2ac, or *note time.thread_time(): 3fe. can be compared with the
     result from any following call to the same function - not just the
     next immediate call.

   - bpo-27646(3): Clarify that ’yield from <expr>’ works with any
     iterable, not just iterators.

   - bpo-36346(4): Update some deprecated unicode APIs which are
     documented as "will be removed in 4.0" to "3.12".  See PEP 623(5)
     for detail.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43199

   (2) https://bugs.python.org/issue43407

   (3) https://bugs.python.org/issue27646

   (4) https://bugs.python.org/issue36346

   (5) https://www.python.org/dev/peps/pep-0623


File: python.info,  Node: Tests<2>,  Next: Build,  Prev: Documentation<3>,  Up: Python 3 8 9 final

1.18.3.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/issue37945

   (2) https://bugs.python.org/issue41561


File: python.info,  Node: Build,  Next: macOS<2>,  Prev: Tests<2>,  Up: Python 3 8 9 final

1.18.3.6 Build
..............

   - bpo-43631(1): Update macOS, Windows, and CI to OpenSSL 1.1.1k.

   - bpo-43617(2): Improve configure.ac: Check for presence of
     autoconf-archive package and remove our copies of M4 macros.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43631

   (2) https://bugs.python.org/issue43617


File: python.info,  Node: macOS<2>,  Next: IDLE<4>,  Prev: Build,  Up: Python 3 8 9 final

1.18.3.7 macOS
..............

   - bpo-41837(1): Update macOS installer build to use OpenSSL 1.1.1j.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41837


File: python.info,  Node: IDLE<4>,  Prev: macOS<2>,  Up: Python 3 8 9 final

1.18.3.8 IDLE
.............

   - bpo-42225(1): Document that IDLE can fail on Unix either from
     misconfigured IP masquerage rules or failure displaying complex
     colored (non-ascii) characters.

   - bpo-43283(2): 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/issue42225

   (2) https://bugs.python.org/issue43283


File: python.info,  Node: Python 3 8 8 final,  Next: Python 3 8 8 release candidate 1,  Prev: Python 3 8 9 final,  Up: Changelog（更動日誌）

1.18.4 Python 3.8.8 final
-------------------------

`Release date: 2021-02-19'

There were no new changes in version 3.8.8.


File: python.info,  Node: Python 3 8 8 release candidate 1,  Next: Python 3 8 7 final,  Prev: Python 3 8 8 final,  Up: Changelog（更動日誌）

1.18.5 Python 3.8.8 release candidate 1
---------------------------------------

`Release date: 2021-02-16'

* Menu:

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


File: python.info,  Node: Security<4>,  Next: Core and Builtins<4>,  Up: Python 3 8 8 release candidate 1

1.18.5.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.

   - bpo-42938(2): Avoid static buffers when computing the repr of *note
     ctypes.c_double: eb6. and *note ctypes.c_longdouble: eb7. values.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42967

   (2) https://bugs.python.org/issue42938


File: python.info,  Node: Core and Builtins<4>,  Next: Library<4>,  Prev: Security<4>,  Up: Python 3 8 8 release candidate 1

1.18.5.2 Core and Builtins
..........................

   - bpo-42819(1): *note readline: df.: 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42819


File: python.info,  Node: Library<4>,  Next: Documentation<4>,  Prev: Core and Builtins<4>,  Up: Python 3 8 8 release candidate 1

1.18.5.3 Library
................

   - bpo-43108(1): Fixed a reference leak in the *note curses: 2c.
     module.  Patch by Pablo Galindo

   - bpo-42780(2): Fix os.set_inheritable() for O_PATH file descriptors
     on Linux.

   - bpo-41748(3): Fix HTMLParser parsing rules for element attributes
     containing commas with spaces.  Patch by Karl Dubost.

   - bpo-42759(4): Fixed equality comparison of ‘tkinter.Variable’ and
     ‘tkinter.font.Font’.  Objects which belong to different Tcl
     interpreters are now always different, even if they have the same
     name.

   - bpo-23328(5): Allow / character in username, password fields on
     _PROXY envars.

   - bpo-42681(6): Fixed range checks for color and pair numbers in
     *note curses: 2c.

   - bpo-42531(7): *note importlib.resources.path(): eba. now works for
     *note package: ebb.s missing the optional *note __file__: ebc.
     attribute (more specifically, packages whose *note __spec__:
     ebd.‘.’*note origin: ebe. *note is: ebf. *note None: 158.).

   - bpo-42388(8): Fix subprocess.check_output(..., input=None) behavior
     when text=True to be consistent with that of the documentation and
     universal_newlines=True.

   - bpo-42384(9): Make pdb populate sys.path[0] exactly the same as
     regular python execution.

   - bpo-42383(10): 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-42318(11): Fixed support of non-BMP characters in *note
     tkinter: 10d. on macOS.

   - bpo-42005(12): Fix CLI of *note cProfile: 28. and *note profile:
     d4. to catch *note BrokenPipeError: 9a2.

   - bpo-41604(13): Don’t decrement the reference count of the previous
     user_ptr when set_panel_userptr fails.

   - bpo-26407(14): Unexpected errors in calling the ‘__iter__’ method
     are no longer masked by ‘TypeError’ in *note csv.reader(): ec0,
     ‘csv.writer.writerow()’ and ‘csv.writer.writerows()’.

   - bpo-39068(15): Fix initialization race condition in ‘a85encode()’
     and ‘b85encode()’ in *note base64: e.  Patch by Brandon Stansbury.

   - bpo-36589(16): The *note curses.update_lines_cols(): 6cb. function
     now returns ‘None’ instead of ‘1’ on success.

   - bpo-33289(17): Correct call to ‘tkinter.colorchooser’ to return RGB
     triplet of ints instead of floats.  Patch by Cheryl Sabella.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43108

   (2) https://bugs.python.org/issue42780

   (3) https://bugs.python.org/issue41748

   (4) https://bugs.python.org/issue42759

   (5) https://bugs.python.org/issue23328

   (6) https://bugs.python.org/issue42681

   (7) https://bugs.python.org/issue42531

   (8) https://bugs.python.org/issue42388

   (9) https://bugs.python.org/issue42384

   (10) https://bugs.python.org/issue42383

   (11) https://bugs.python.org/issue42318

   (12) https://bugs.python.org/issue42005

   (13) https://bugs.python.org/issue41604

   (14) https://bugs.python.org/issue26407

   (15) https://bugs.python.org/issue39068

   (16) https://bugs.python.org/issue36589

   (17) https://bugs.python.org/issue33289


File: python.info,  Node: Documentation<4>,  Next: Tests<3>,  Prev: Library<4>,  Up: Python 3 8 8 release candidate 1

1.18.5.4 Documentation
......................

   - bpo-40304(1): Fix doc for type(name, bases, dict).  Patch by Boris
     Verkhovskiy and Éric Araujo.

   - bpo-42811(2): Updated importlib.utils.resolve_name() doc to use
     __spec__.parent instead of __package__.  (Thanks Yair Frid.)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40304

   (2) https://bugs.python.org/issue42811


File: python.info,  Node: Tests<3>,  Next: Build<2>,  Prev: Documentation<4>,  Up: Python 3 8 8 release candidate 1

1.18.5.5 Tests
..............

   - bpo-42794(1): Update test_nntplib to use offical group name of
     news.aioe.org for testing.  Patch by Dong-hee Na.

   - bpo-40810(2): In *note sqlite3: f3, fix ‘CheckTraceCallbackContent’
     for SQLite pre 3.7.15.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42794

   (2) https://bugs.python.org/issue40810


File: python.info,  Node: Build<2>,  Next: Windows<2>,  Prev: Tests<3>,  Up: Python 3 8 8 release candidate 1

1.18.5.6 Build
..............

   - bpo-29076(1): Add fish shell support to macOS installer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue29076


File: python.info,  Node: Windows<2>,  Next: macOS<3>,  Prev: Build<2>,  Up: Python 3 8 8 release candidate 1

1.18.5.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/issue41837

   (2) https://bugs.python.org/issue42584


File: python.info,  Node: macOS<3>,  Next: IDLE<5>,  Prev: Windows<2>,  Up: Python 3 8 8 release candidate 1

1.18.5.8 macOS
..............

   - bpo-41837(1): Update macOS installer build to use OpenSSL 1.1.1i.

   - bpo-42584(2): Update macOS installer to use SQLite 3.34.0.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41837

   (2) https://bugs.python.org/issue42584


File: python.info,  Node: IDLE<5>,  Next: Tools/Demos,  Prev: macOS<3>,  Up: Python 3 8 8 release candidate 1

1.18.5.9 IDLE
.............

   - bpo-43008(1): Make IDLE invoke *note sys.excepthook(): e68. in
     normal, 2-process mode.  Patch by Ken Hilton.

   - bpo-33065(2): Fix problem debugging user classes with __repr__
     method.

   - bpo-42508(3): Keep IDLE running on macOS. Remove obsolete
     workaround that prevented running files with shortcuts when using
     new universal2 installers built on macOS 11.

   - bpo-23544(4): Disable Debug=>Stack Viewer when user code is running
     or Debugger is active, to prevent hang or crash.  Patch by Zackery
     Spytz.

   - bpo-32631(5): Finish zzdummy example extension module: make menu
     entries work; add docstrings and tests with 100% coverage.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue43008

   (2) https://bugs.python.org/issue33065

   (3) https://bugs.python.org/issue42508

   (4) https://bugs.python.org/issue23544

   (5) https://bugs.python.org/issue32631


File: python.info,  Node: Tools/Demos,  Next: C API<2>,  Prev: IDLE<5>,  Up: Python 3 8 8 release candidate 1

1.18.5.10 Tools/Demos
.....................

   - bpo-42726(1): Fixed Python 3 compatibility issue with
     gdb/libpython.py handling of attribute dictionaries.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42726


File: python.info,  Node: C API<2>,  Prev: Tools/Demos,  Up: Python 3 8 8 release candidate 1

1.18.5.11 C API
...............

   - bpo-43030(1): Fixed a compiler warning in *note
     Py_UNICODE_ISSPACE(): ec9. on platforms with signed ‘wchar_t’.

   - bpo-40052(2): 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/issue43030

   (2) https://bugs.python.org/issue40052


File: python.info,  Node: Python 3 8 7 final,  Next: Python 3 8 7 release candidate 1,  Prev: Python 3 8 8 release candidate 1,  Up: Changelog（更動日誌）

1.18.6 Python 3.8.7 final
-------------------------

`Release date: 2020-12-21'

* Menu:

* Core and Builtins: Core and Builtins<5>.
* Library: Library<5>.
* Documentation: Documentation<5>.
* Build: Build<3>.
* Tools/Demos: Tools/Demos<2>.


File: python.info,  Node: Core and Builtins<5>,  Next: Library<5>,  Up: Python 3 8 7 final

1.18.6.1 Core and Builtins
..........................

   - bpo-32381(1): Fix encoding name when running a ‘.pyc’ file on
     Windows: *note PyRun_SimpleFileExFlags(): ecc. now uses the correct
     encoding to decode the filename.

   - 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: ecd.:

        - *note collections.OrderedDict.items(): 1ba.

        - *note dict.items(): c30.

        - *note enumerate(): de8.

        - *note functools.reduce(): c74.

        - *note itertools.combinations(): cab.

        - *note itertools.combinations_with_replacement(): c1e.

        - *note itertools.permutations(): ece.

        - *note itertools.product(): cac.

        - *note itertools.zip_longest(): c36.

        - *note zip(): c37.

     Previously, they could have become untracked by a prior garbage
     collection.  Patch by Brandt Bucher.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32381

   (2) https://bugs.python.org/issue42536


File: python.info,  Node: Library<5>,  Next: Documentation<5>,  Prev: Core and Builtins<5>,  Up: Python 3 8 7 final

1.18.6.2 Library
................

   - bpo-42630(1): *note tkinter: 10d. functions and constructors which
     need a default root window raise now *note RuntimeError: 2bb. with
     descriptive message instead of obscure *note AttributeError: 3a0.
     or *note NameError: d80. if it is not created yet or cannot be
     created automatically.

   - bpo-42644(2): *note logging.disable: ed0. will now validate the
     types and value of its parameter.  It also now accepts strings
     representing the levels (as does ‘loging.setLevel’) instead of only
     the numerical values.

   - bpo-36541(3): Fixed lib2to3.pgen2 to be able to parse PEP-570
     positional only argument syntax.

   - bpo-42375(4): subprocess module update for DragonFlyBSD support.

   - bpo-39825(5): 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-39101(6): Fixed tests using IsolatedAsyncioTestCase from
     hanging on BaseExceptions.

   - bpo-41907(7): fix *note format(): 4e0. behavior for ‘IntFlag’

   - bpo-41889(8): Enum: fix regression involving inheriting a
     multiply-inherited enum

   - bpo-41891(9): Ensure asyncio.wait_for waits for task completion

   - bpo-40219(10): Lowered ‘tkinter.ttk.LabeledScale’ dummy widget to
     prevent hiding part of the content label.

   - bpo-40084(11): Fix ‘Enum.__dir__’: dir(Enum.member) now includes
     attributes as well as methods.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42630

   (2) https://bugs.python.org/issue42644

   (3) https://bugs.python.org/issue36541

   (4) https://bugs.python.org/issue42375

   (5) https://bugs.python.org/issue39825

   (6) https://bugs.python.org/issue39101

   (7) https://bugs.python.org/issue41907

   (8) https://bugs.python.org/issue41889

   (9) https://bugs.python.org/issue41891

   (10) https://bugs.python.org/issue40219

   (11) https://bugs.python.org/issue40084


File: python.info,  Node: Documentation<5>,  Next: Build<3>,  Prev: Library<5>,  Up: Python 3 8 7 final

1.18.6.3 Documentation
......................

   - bpo-17140(1): Add documentation for the *note
     multiprocessing.pool.ThreadPool: ed2. class.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17140


File: python.info,  Node: Build<3>,  Next: Tools/Demos<2>,  Prev: Documentation<5>,  Up: Python 3 8 7 final

1.18.6.4 Build
..............

   - bpo-42604(1): 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").
     Previosuly only Linux, Mac and VxWorks were using a value for
     "EXT_SUFFIX" that included "SOABI".

   - bpo-42598(2): Fix implicit function declarations in configure which
     could have resulted in incorrect configuration checks.  Patch
     contributed by Joshua Root.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42604

   (2) https://bugs.python.org/issue42598


File: python.info,  Node: Tools/Demos<2>,  Prev: Build<3>,  Up: Python 3 8 7 final

1.18.6.5 Tools/Demos
....................

   - bpo-42613(1): Fix ‘freeze.py’ tool to use the prope config and
     library directories.  Patch by Victor Stinner.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42613


File: python.info,  Node: Python 3 8 7 release candidate 1,  Next: Python 3 8 6 final,  Prev: Python 3 8 7 final,  Up: Changelog（更動日誌）

1.18.7 Python 3.8.7 release candidate 1
---------------------------------------

`Release date: 2020-12-07'

* Menu:

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


File: python.info,  Node: Security<5>,  Next: Core and Builtins<6>,  Up: Python 3 8 7 release candidate 1

1.18.7.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: d0. 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.

   - bpo-40791(3): Add ‘volatile’ to the accumulator variable in
     ‘hmac.compare_digest’, making constant-time-defeating optimizations
     less likely.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42103

   (2) https://bugs.python.org/issue42051

   (3) https://bugs.python.org/issue40791


File: python.info,  Node: Core and Builtins<6>,  Next: Library<6>,  Prev: Security<5>,  Up: Python 3 8 7 release candidate 1

1.18.7.2 Core and Builtins
..........................

   - bpo-41686(1): 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: ed8. equals to 0, or
     ‘Py_InitializeEx(0)’).

   - bpo-42143(2): Fix handling of errors during creation of
     ‘PyFunctionObject’, which resulted in operations on uninitialized
     memory.  Patch by Yonatan Goldschmidt.

   - bpo-41984(3): The garbage collector now tracks all user-defined
     classes.  Patch by Brandt Bucher.

   - bpo-41909(4): Fixed stack overflow in *note issubclass(): 455. and
     *note isinstance(): 454. when getting the ‘__bases__’ attribute
     leads to infinite recursion.

   - bpo-41894(5): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41686

   (2) https://bugs.python.org/issue42143

   (3) https://bugs.python.org/issue41984

   (4) https://bugs.python.org/issue41909

   (5) https://bugs.python.org/issue41894


File: python.info,  Node: Library<6>,  Next: Documentation<6>,  Prev: Core and Builtins<6>,  Up: Python 3 8 7 release candidate 1

1.18.7.3 Library
................

   - bpo-17735(1): ‘inspect.findsource()’ now raises *note OSError: 1d4.
     instead of *note IndexError: e7a. 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(2): Fix handling of trailing comments by *note
     inspect.getsource(): eda.

   - bpo-42482(3): *note TracebackException: 77b. 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-42406(4): We fixed an issue in ‘pickle.whichmodule’ in which
     importing *note multiprocessing: b8. could change the how pickle
     identifies which module an object belongs to, potentially breaking
     the unpickling of those objects.

   - bpo-42328(5): Fixed *note tkinter.ttk.Style.map(): edb.  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-42014(6): The ‘onerror’ callback from ‘shutil.rmtree’ now
     receives correct function when ‘os.open’ fails.

   - bpo-42237(7): Fix *note os.sendfile(): 35e. on illumos.

   - bpo-42249(8): Fixed writing binary Plist files larger than 4 GiB.

   - bpo-35455(9): On Solaris, *note thread_time(): 3fe. is now
     implemented with ‘gethrvtime()’ because
     ‘clock_gettime(CLOCK_THREAD_CPUTIME_ID)’ is not always available.
     Patch by Jakub Kulik.

   - bpo-41754(10): webbrowser: Ignore `NotADirectoryError' when calling
     ‘xdg-settings’.

   - bpo-29566(11): ‘binhex.binhex()’ consisently writes macOS 9 line
     endings.

   - bpo-42183(12): 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-42103(13): ‘InvalidFileException’ and *note RecursionError:
     639. are now the only errors caused by loading malformed binary
     Plist file (previously ValueError and TypeError could be raised in
     some specific cases).

   - bpo-41491(14): plistlib: fix parsing XML plists with hexadecimal
     integer values

   - bpo-32498(15): Clearer exception message when passing an argument
     of type bytes to *note urllib.parse.unquote(): edc.  This is only
     for 3.8; in 3.9 and later this function accepts bytes inputs as
     well.  PR by Irit Katriel.

   - bpo-42065(16): 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(17): Fix pickling pure Python *note datetime.time: 4f8.
     subclasses.  Patch by Dean Inwood.

   - bpo-41976(18): Fixed a bug that was causing *note
     ctypes.util.find_library(): 60f. 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-41900(19): C14N 2.0 serialisation in xml.etree.ElementTree
     failed for unprefixed attributes when a default namespace was
     defined.

   - bpo-41855(20): In ‘importlib.metadata’, fix issue where multiple
     children can be returned from ‘FastPath.zip_children()’.  Backport
     of python-devs/importlib_metadata#117(21).

   - bpo-41840(22): Fix a bug in the *note symtable: fd. module that was
     causing module-scope global variables to not be reported as both
     local and global.  Patch by Pablo Galindo.

   - bpo-41831(23): ‘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-41662(24): No longer override exceptions raised in ‘__len__()’
     of a sequence of parameters in *note sqlite3: f3. with *note
     ProgrammingError: edd.

   - bpo-41662(25): Fixed crash when mutate list of parameters during
     iteration in *note sqlite3: f3.

   - bpo-34215(26): Clarify the error message for *note
     asyncio.IncompleteReadError: ede. when ‘expected’ is ‘None’.

   - bpo-41316(27): Fix the *note tarfile: 102. module to write only
     basename of TAR file to GZIP compression header.

   - bpo-12800(28): 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-16936(29): Allow ‘ctypes.wintypes’ to be imported on
     non-Windows systems.

   - bpo-40592(30): *note shutil.which(): edf. now ignores empty entries
     in ‘PATHEXT’ instead of treating them as a match.

   - bpo-40492(31): Fix ‘--outfile’ for *note cProfile: 28. / *note
     profile: d4. not writing the output file in the original directory
     when the program being profiled changes the working directory.  PR
     by Anthony Sottile.

   - bpo-40105(32): ZipFile truncates files to avoid corruption when a
     shorter comment is provided in append ("a") mode.  Patch by Jan
     Mazur.

   - bpo-27321(33): Fixed KeyError exception when flattening an email to
     a string attempts to replace a non-existent
     Content-Transfer-Encoding header.

   - bpo-32793(34): Fix a duplicated debug message when *note
     smtplib.SMTP.connect(): ee0. is called.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17735

   (2) https://bugs.python.org/issue42116

   (3) https://bugs.python.org/issue42482

   (4) https://bugs.python.org/issue42406

   (5) https://bugs.python.org/issue42328

   (6) https://bugs.python.org/issue42014

   (7) https://bugs.python.org/issue42237

   (8) https://bugs.python.org/issue42249

   (9) https://bugs.python.org/issue35455

   (10) https://bugs.python.org/issue41754

   (11) https://bugs.python.org/issue29566

   (12) https://bugs.python.org/issue42183

   (13) https://bugs.python.org/issue42103

   (14) https://bugs.python.org/issue41491

   (15) https://bugs.python.org/issue32498

   (16) https://bugs.python.org/issue42065

   (17) https://bugs.python.org/issue41966

   (18) https://bugs.python.org/issue41976

   (19) https://bugs.python.org/issue41900

   (20) https://bugs.python.org/issue41855

   (21) https://gitlab.com/python-devs/importlib_metadata/-/issues/117

   (22) https://bugs.python.org/issue41840

   (23) https://bugs.python.org/issue41831

   (24) https://bugs.python.org/issue41662

   (25) https://bugs.python.org/issue41662

   (26) https://bugs.python.org/issue34215

   (27) https://bugs.python.org/issue41316

   (28) https://bugs.python.org/issue12800

   (29) https://bugs.python.org/issue16936

   (30) https://bugs.python.org/issue40592

   (31) https://bugs.python.org/issue40492

   (32) https://bugs.python.org/issue40105

   (33) https://bugs.python.org/issue27321

   (34) https://bugs.python.org/issue32793


File: python.info,  Node: Documentation<6>,  Next: Tests<4>,  Prev: Library<6>,  Up: Python 3 8 7 release candidate 1

1.18.7.4 Documentation
......................

   - bpo-42153(1): Fix the URL for the IMAP protocol documents.

   - bpo-41910(2): Document the default implementation of *note
     object.__eq__: 344.

   - bpo-41774(3): In Programming FAQ "Sequences (Tuples/Lists)"
     section, add "How do you remove multiple items from a list".

   - bpo-39416(4): Document some restrictions on the default string
     representations of numeric classes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42153

   (2) https://bugs.python.org/issue41910

   (3) https://bugs.python.org/issue41774

   (4) https://bugs.python.org/issue39416


File: python.info,  Node: Tests<4>,  Next: Build<4>,  Prev: Documentation<6>,  Up: Python 3 8 7 release candidate 1

1.18.7.5 Tests
..............

   - bpo-41473(1): Reenable 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-40754(3): Include ‘_testinternalcapi’ module in Windows
     installer for test suite

   - bpo-41739(4): Fix
     test_logging.test_race_between_set_target_and_flush(): the test now
     waits until all threads complete to avoid leaking running threads.

   - bpo-41944(5): Tests for CJK codecs no longer call ‘eval()’ on
     content received via HTTP.

   - bpo-41939(6): Fix test_site.test_license_exists_at_url(): call
     ‘urllib.request.urlcleanup()’ to reset the global
     ‘urllib.request._opener’.  Patch by Victor Stinner.

   - bpo-41561(7): test_ssl: skip test_min_max_version_mismatch when TLS
     1.0 is not available

   - bpo-41602(8): Add tests for SIGINT handling in the runpy module.

   - bpo-41306(9): 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/issue41473

   (2) https://bugs.python.org/issue42553

   (3) https://bugs.python.org/issue40754

   (4) https://bugs.python.org/issue41739

   (5) https://bugs.python.org/issue41944

   (6) https://bugs.python.org/issue41939

   (7) https://bugs.python.org/issue41561

   (8) https://bugs.python.org/issue41602

   (9) https://bugs.python.org/issue41306


File: python.info,  Node: Build<4>,  Next: Windows<3>,  Prev: Tests<4>,  Up: Python 3 8 7 release candidate 1

1.18.7.6 Build
..............

   - bpo-42398(1): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42398


File: python.info,  Node: Windows<3>,  Next: macOS<4>,  Prev: Build<4>,  Up: Python 3 8 7 release candidate 1

1.18.7.7 Windows
................

   - bpo-42120(1): Remove macro definition of ‘copysign’ (to
     ‘_copysign’) in headers.

   - bpo-38439(2): Updates the icons for IDLE in the Windows Store
     package.

   - bpo-41557(3): Update Windows installer to use SQLite 3.33.0.

   - bpo-38324(4): Avoid Unicode errors when accessing certain locale
     data on Windows.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue42120

   (2) https://bugs.python.org/issue38439

   (3) https://bugs.python.org/issue41557

   (4) https://bugs.python.org/issue38324


File: python.info,  Node: macOS<4>,  Next: IDLE<6>,  Prev: Windows<3>,  Up: Python 3 8 7 release candidate 1

1.18.7.8 macOS
..............

   - bpo-38443(1): The ‘--enable-universalsdk’ and
     ‘--with-universal-archs’ options for the configure script now check
     that the specified architectures can be used.

   - bpo-41471(2): Ignore invalid prefix lengths in system proxy
     excludes.

   - bpo-41557(3): Update macOS installer to use SQLite 3.33.0.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38443

   (2) https://bugs.python.org/issue41471

   (3) https://bugs.python.org/issue41557


File: python.info,  Node: IDLE<6>,  Next: C API<3>,  Prev: macOS<4>,  Up: Python 3 8 7 release candidate 1

1.18.7.9 IDLE
.............

   - bpo-42426(1): Fix reporting offset of the RE error in searchengine.

   - bpo-42415(2): Get docstrings for IDLE calltips more often by using
     inspect.getdoc.

   - bpo-33987(3): Mostly finish using ttk widgets, mainly for editor,
     settings, and searches.  Some patches by Mark Roseman.

   - bpo-41775(4): Use ’IDLE Shell’ as shell title

   - bpo-40511(5): 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(6): 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/issue42426

   (2) https://bugs.python.org/issue42415

   (3) https://bugs.python.org/issue33987

   (4) https://bugs.python.org/issue41775

   (5) https://bugs.python.org/issue40511

   (6) https://bugs.python.org/issue38439


File: python.info,  Node: C API<3>,  Prev: IDLE<6>,  Up: Python 3 8 7 release candidate 1

1.18.7.10 C API
...............

   - bpo-41986(1): ‘Py_FileSystemDefaultEncodeErrors’ and ‘Py_UTF8Mode’
     are available again in limited API.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41986


File: python.info,  Node: Python 3 8 6 final,  Next: Python 3 8 6 release candidate 1,  Prev: Python 3 8 7 release candidate 1,  Up: Changelog（更動日誌）

1.18.8 Python 3.8.6 final
-------------------------

`Release date: 2020-09-23'

* Menu:

* Core and Builtins: Core and Builtins<7>.
* Library: Library<7>.
* Documentation: Documentation<7>.
* Tests: Tests<5>.
* Windows: Windows<4>.
* IDLE: IDLE<7>.


File: python.info,  Node: Core and Builtins<7>,  Next: Library<7>,  Up: Python 3 8 6 final

1.18.8.1 Core and Builtins
..........................

   - bpo-41525(1): The output of ‘python --help’ contains now only ASCII
     characters.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41525


File: python.info,  Node: Library<7>,  Next: Documentation<7>,  Prev: Core and Builtins<7>,  Up: Python 3 8 6 final

1.18.8.2 Library
................

   - bpo-41817(1): fix ‘tkinter.EventType’ Enum so all members are
     strings, and none are tuples

   - bpo-41815(2): Fix SQLite3 segfault when backing up closed database.
     Patch contributed by Peter David McCormick.

   - bpo-41517(3): fix bug allowing Enums to be extended via multiple
     inheritance

   - bpo-39587(4): use the correct mix-in data type when constructing
     Enums

   - bpo-41789(5): Honor *note object: 2b1. overrides in ‘Enum’ class
     creation (specifically, ‘__str__’, ‘__repr__’, ‘__format__’, and
     ‘__reduce_ex__’).

   - bpo-39651(6): Fix a race condition in the ‘call_soon_threadsafe()’
     method of ‘asyncio.ProactorEventLoop’: do nothing if the self-pipe
     socket has been closed.

   - bpo-41720(7): Fixed ‘turtle.Vec2D.__rmul__()’ for arguments which
     are not int or float.

   - bpo-39728(8): fix default ‘_missing_’ so a duplicate *note
     ValueError: 1fc. is not set as the ‘__context__’ of the original
     *note ValueError: 1fc.

   - bpo-37479(9): When ‘Enum.__str__’ is overridden in a derived class,
     the override will be used by ‘Enum.__format__’ regardless of
     whether mixin classes are present.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41817

   (2) https://bugs.python.org/issue41815

   (3) https://bugs.python.org/issue41517

   (4) https://bugs.python.org/issue39587

   (5) https://bugs.python.org/issue41789

   (6) https://bugs.python.org/issue39651

   (7) https://bugs.python.org/issue41720

   (8) https://bugs.python.org/issue39728

   (9) https://bugs.python.org/issue37479


File: python.info,  Node: Documentation<7>,  Next: Tests<5>,  Prev: Library<7>,  Up: Python 3 8 6 final

1.18.8.3 Documentation
......................

   - bpo-35293(1): Fix RemovedInSphinx40Warning when building the
     documentation.  Patch by Dong-hee Na.

   - bpo-37149(2): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35293

   (2) https://bugs.python.org/issue37149


File: python.info,  Node: Tests<5>,  Next: Windows<4>,  Prev: Documentation<7>,  Up: Python 3 8 6 final

1.18.8.4 Tests
..............

   - bpo-41731(1): Make test_cmd_line_script pass with option ’-vv’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41731


File: python.info,  Node: Windows<4>,  Next: IDLE<7>,  Prev: Tests<5>,  Up: Python 3 8 6 final

1.18.8.5 Windows
................

   - bpo-41744(1): Fixes automatic import of props file when using the
     Nuget package.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41744


File: python.info,  Node: IDLE<7>,  Prev: Windows<4>,  Up: Python 3 8 6 final

1.18.8.6 IDLE
.............

   - bpo-35764(1): Rewrite the Calltips doc section.

   - bpo-40181(2): In calltips, stop reminding that ’/’ marks the end of
     positional-only arguments.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35764

   (2) https://bugs.python.org/issue40181


File: python.info,  Node: Python 3 8 6 release candidate 1,  Next: Python 3 8 5 final,  Prev: Python 3 8 6 final,  Up: Changelog（更動日誌）

1.18.9 Python 3.8.6 release candidate 1
---------------------------------------

`Release date: 2020-09-07'

* Menu:

* Core and Builtins: Core and Builtins<8>.
* Library: Library<8>.
* Documentation: Documentation<8>.
* Windows: Windows<5>.
* IDLE: IDLE<8>.
* C API: C API<4>.


File: python.info,  Node: Core and Builtins<8>,  Next: Library<8>,  Up: Python 3 8 6 release candidate 1

1.18.9.1 Core and Builtins
..........................

   - bpo-41654(1): Fix a crash that occurred when destroying subclasses
     of *note MemoryError: ef1.  Patch by Pablo Galindo.

   - bpo-41533(2): Free the stack allocated in ‘va_build_stack’ if
     ‘do_mkstack’ fails and the stack is not a ‘small_stack’.

   - bpo-38156(3): Handle interrupts that come after EOF correctly in
     ‘PyOS_StdioReadline’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41654

   (2) https://bugs.python.org/issue41533

   (3) https://bugs.python.org/issue38156


File: python.info,  Node: Library<8>,  Next: Documentation<8>,  Prev: Core and Builtins<8>,  Up: Python 3 8 6 release candidate 1

1.18.9.2 Library
................

   - bpo-41696(1): Fix handling of debug mode in *note asyncio.run():
     1a6.  This allows setting ‘PYTHONASYNCIODEBUG’ or ‘-X dev’ to
     enable asyncio debug mode when using *note asyncio.run(): 1a6.

   - bpo-39010(2): Restarting a ‘ProactorEventLoop’ on Windows no longer
     logs spurious ‘ConnectionResetErrors’.

   - bpo-41609(3): The pdb whatis command correctly reports instance
     methods as ’Method’ rather than ’Function’.

   - bpo-32751(4): When cancelling the task due to a timeout, *note
     asyncio.wait_for(): 289. will now wait until the cancellation is
     complete also in the case when `timeout' is <= 0, like it does with
     positive timeouts.

   - bpo-37658(5): *note asyncio.wait_for(): 289. now properly handles
     races between cancellation of itself and the completion of the
     wrapped awaitable.

   - bpo-40782(6): Change the method
     asyncio.AbstractEventLoop.run_in_executor to not be a coroutine.

   - bpo-41520(7): Fix *note codeop: 1d. regression that prevented
     turning compile warnings into errors.

   - bpo-41503(8): Fixed a race between setTarget and flush in
     logging.handlers.MemoryHandler.

   - bpo-41497(9): Fix potential UnicodeDecodeError in dis module.

   - bpo-41490(10): Update *note ensurepip: 7a. to install pip 20.2.1
     and setuptools 49.2.1.

   - bpo-41467(11): On Windows, fix asyncio ‘recv_into()’ return value
     when the socket/pipe is closed (*note BrokenPipeError: 9a2.):
     return ‘0’ rather than an empty byte string (‘b''’).

   - bpo-41425(12): Make tkinter doc example runnable.

   - bpo-41384(13): Raise TclError instead of TypeError when an unknown
     option is passed to tkinter.OptionMenu.

   - bpo-38731(14): Fix *note NameError: d80. in command-line interface
     of *note py_compile: d8.

   - bpo-41364(15): Reduce import overhead of *note uuid: 125.

   - bpo-41344(16): Prevent creating ‘shared_memory.SharedMemory’
     objects with ‘size=0’.

   - bpo-40726(17): Handle cases where the ‘end_lineno’ is ‘None’ on
     *note ast.increment_lineno(): ef3.

   - bpo-31122(18): ssl.wrap_socket() now raises ssl.SSLEOFError rather
     than OSError when peer closes connection during TLS negotiation

   - bpo-33660(19): Fix pathlib.PosixPath to resolve a relative path
     located on the root directory properly.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41696

   (2) https://bugs.python.org/issue39010

   (3) https://bugs.python.org/issue41609

   (4) https://bugs.python.org/issue32751

   (5) https://bugs.python.org/issue37658

   (6) https://bugs.python.org/issue40782

   (7) https://bugs.python.org/issue41520

   (8) https://bugs.python.org/issue41503

   (9) https://bugs.python.org/issue41497

   (10) https://bugs.python.org/issue41490

   (11) https://bugs.python.org/issue41467

   (12) https://bugs.python.org/issue41425

   (13) https://bugs.python.org/issue41384

   (14) https://bugs.python.org/issue38731

   (15) https://bugs.python.org/issue41364

   (16) https://bugs.python.org/issue41344

   (17) https://bugs.python.org/issue40726

   (18) https://bugs.python.org/issue31122

   (19) https://bugs.python.org/issue33660


File: python.info,  Node: Documentation<8>,  Next: Windows<5>,  Prev: Library<8>,  Up: Python 3 8 6 release candidate 1

1.18.9.3 Documentation
......................

   - bpo-41624(1): Fix the signature of *note typing.Coroutine: ef5.

   - bpo-40204(2): 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(3): Add documentation for debug feature of f-strings.

   - bpo-41314(4): Changed the release when ‘from __future__ import
     annotations’ becomes the default from ‘4.0’ to ‘3.10’ (following a
     change in PEP 563).

   - bpo-39883(5): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41624

   (2) https://bugs.python.org/issue40204

   (3) https://bugs.python.org/issue41045

   (4) https://bugs.python.org/issue41314

   (5) https://bugs.python.org/issue39883


File: python.info,  Node: Windows<5>,  Next: IDLE<8>,  Prev: Documentation<8>,  Up: Python 3 8 6 release candidate 1

1.18.9.4 Windows
................

   - bpo-41492(1): Fixes the description that appears in UAC prompts.

   - bpo-40741(2): Update Windows release to include SQLite 3.32.3.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41492

   (2) https://bugs.python.org/issue40741


File: python.info,  Node: IDLE<8>,  Next: C API<4>,  Prev: Windows<5>,  Up: Python 3 8 6 release candidate 1

1.18.9.5 IDLE
.............

   - bpo-41468(1): Improve IDLE run crash error message (which users
     should never see).

   - bpo-41373(2): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41468

   (2) https://bugs.python.org/issue41373


File: python.info,  Node: C API<4>,  Prev: IDLE<8>,  Up: Python 3 8 6 release candidate 1

1.18.9.6 C API
..............

   - bpo-41524(1): Fix bug in PyOS_mystrnicmp and PyOS_mystricmp that
     incremented pointers beyond the end of a string.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41524


File: python.info,  Node: Python 3 8 5 final,  Next: Python 3 8 4 final,  Prev: Python 3 8 6 release candidate 1,  Up: Changelog（更動日誌）

1.18.10 Python 3.8.5 final
--------------------------

`Release date: 2020-07-20'

* Menu:

* Security: Security<6>.
* Core and Builtins: Core and Builtins<9>.
* Library: Library<9>.
* Documentation: Documentation<9>.
* Build: Build<5>.
* macOS: macOS<5>.
* IDLE: IDLE<9>.


File: python.info,  Node: Security<6>,  Next: Core and Builtins<9>,  Up: Python 3 8 5 final

1.18.10.1 Security
..................

   - bpo-41304(1): Fixes ‘python3x._pth’ being ignored on Windows,
     caused by the fix for bpo-29778(2) (CVE-2020-15801).

   - bpo-39603(3): Prevent http header injection by rejecting control
     characters in http.client.putrequest(...).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41304

   (2) https://bugs.python.org/issue29778

   (3) https://bugs.python.org/issue39603


File: python.info,  Node: Core and Builtins<9>,  Next: Library<9>,  Prev: Security<6>,  Up: Python 3 8 5 final

1.18.10.2 Core and Builtins
...........................

   - bpo-41295(1): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41295


File: python.info,  Node: Library<9>,  Next: Documentation<9>,  Prev: Core and Builtins<9>,  Up: Python 3 8 5 final

1.18.10.3 Library
.................

   - bpo-41288(1): Unpickling invalid NEWOBJ_EX opcode with the C
     implementation raises now UnpicklingError instead of crashing.

   - bpo-39017(2): Avoid infinite loop when reading specially crafted
     TAR files using the tarfile module (CVE-2019-20907).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41288

   (2) https://bugs.python.org/issue39017


File: python.info,  Node: Documentation<9>,  Next: Build<5>,  Prev: Library<9>,  Up: Python 3 8 5 final

1.18.10.4 Documentation
.......................

   - bpo-37703(1): Updated Documentation to comprehensively elaborate on
     the behaviour of gather.cancel()

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37703


File: python.info,  Node: Build<5>,  Next: macOS<5>,  Prev: Documentation<9>,  Up: Python 3 8 5 final

1.18.10.5 Build
...............

   - bpo-41302(1): Enable building Python 3.8 with libmpdec-2.5.0 to
     ease maintenance for Linux distributions.  Patch by Felix Yan.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41302


File: python.info,  Node: macOS<5>,  Next: IDLE<9>,  Prev: Build<5>,  Up: Python 3 8 5 final

1.18.10.6 macOS
...............

   - bpo-40741(1): Update macOS installer to use SQLite 3.32.3.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40741


File: python.info,  Node: IDLE<9>,  Prev: macOS<5>,  Up: Python 3 8 5 final

1.18.10.7 IDLE
..............

   - bpo-41300(1): Save files with non-ascii chars.  Fix regression
     released in 3.9.0b4 and 3.8.4.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41300


File: python.info,  Node: Python 3 8 4 final,  Next: Python 3 8 4 release candidate 1,  Prev: Python 3 8 5 final,  Up: Changelog（更動日誌）

1.18.11 Python 3.8.4 final
--------------------------

`Release date: 2020-07-13'

* Menu:

* Security: Security<7>.
* Core and Builtins: Core and Builtins<10>.
* Library: Library<10>.
* IDLE: IDLE<10>.


File: python.info,  Node: Security<7>,  Next: Core and Builtins<10>,  Up: Python 3 8 4 final

1.18.11.1 Security
..................

   - bpo-41162(1): Audit hooks are now cleared later during finalization
     to avoid missing events.

   - bpo-29778(2): Ensure ‘python3.dll’ is loaded from correct locations
     when Python is embedded (CVE-2020-15523).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41162

   (2) https://bugs.python.org/issue29778


File: python.info,  Node: Core and Builtins<10>,  Next: Library<10>,  Prev: Security<7>,  Up: Python 3 8 4 final

1.18.11.2 Core and Builtins
...........................

   - bpo-41247(1): Always cache the running loop holder when running
     ‘asyncio.set_running_loop’.

   - bpo-41252(2): Fix incorrect refcounting in _ssl.c’s
     ‘_servername_callback()’.

   - bpo-41218(3): 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-41175(4): Guard against a NULL pointer dereference within
     bytearrayobject triggered by the ‘bytearray() + bytearray()’
     operation.

   - bpo-39960(5): The "hackcheck" that prevents sneaking around a
     type’s __setattr__() by calling the superclass method was rewritten
     to allow C implemented heap types.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41247

   (2) https://bugs.python.org/issue41252

   (3) https://bugs.python.org/issue41218

   (4) https://bugs.python.org/issue41175

   (5) https://bugs.python.org/issue39960


File: python.info,  Node: Library<10>,  Next: IDLE<10>,  Prev: Core and Builtins<10>,  Up: Python 3 8 4 final

1.18.11.3 Library
.................

   - bpo-41235(1): Fix the error handling in *note
     ssl.SSLContext.load_dh_params(): a97.

   - bpo-41193(2): The ‘write_history()’ atexit function of the readline
     completer now ignores any *note OSError: 1d4. to ignore error if
     the filesystem is read-only, instead of only ignoring *note
     FileNotFoundError: 7c5. and *note PermissionError: 604.

   - bpo-41043(3): Fixed the use of *note glob(): 5cb. in the stdlib:
     literal part of the path is now always correctly escaped.

   - bpo-39384(4): Fixed email.contentmanager to allow set_content() to
     set a null string.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41235

   (2) https://bugs.python.org/issue41193

   (3) https://bugs.python.org/issue41043

   (4) https://bugs.python.org/issue39384


File: python.info,  Node: IDLE<10>,  Prev: Library<10>,  Up: Python 3 8 4 final

1.18.11.4 IDLE
..............

   - bpo-37765(1): Add keywords to module name completion list.  Rewrite
     Completions section of IDLE doc.

   - bpo-41152(2): The encoding of ‘stdin’, ‘stdout’ and ‘stderr’ in
     IDLE is now always UTF-8.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37765

   (2) https://bugs.python.org/issue41152


File: python.info,  Node: Python 3 8 4 release candidate 1,  Next: Python 3 8 3 final,  Prev: Python 3 8 4 final,  Up: Changelog（更動日誌）

1.18.12 Python 3.8.4 release candidate 1
----------------------------------------

`Release date: 2020-06-29'

* Menu:

* Security: Security<8>.
* Core and Builtins: Core and Builtins<11>.
* Library: Library<11>.
* Tests: Tests<6>.
* Build: Build<6>.
* Windows: Windows<6>.
* macOS: macOS<6>.
* IDLE: IDLE<11>.
* Tools/Demos: Tools/Demos<3>.


File: python.info,  Node: Security<8>,  Next: Core and Builtins<11>,  Up: Python 3 8 4 release candidate 1

1.18.12.1 Security
..................

   - bpo-41004(1): 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-39073(2): Disallow CR or LF in email.headerregistry.Address
     arguments to guard against header injection attacks.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41004

   (2) https://bugs.python.org/issue39073


File: python.info,  Node: Core and Builtins<11>,  Next: Library<11>,  Prev: Security<8>,  Up: Python 3 8 4 release candidate 1

1.18.12.2 Core and Builtins
...........................

   - bpo-41094(1): Fix decoding errors with audit when open files with
     non-ASCII names on non-UTF-8 locale.

   - bpo-41056(2): 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-35975(3): 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-40957(4): Fix refleak in _Py_fopen_obj() when PySys_Audit()
     fails

   - bpo-40870(5): Raise *note ValueError: 1fc. when validating custom
     AST’s where the constants ‘True’, ‘False’ and ‘None’ are used
     within a ‘ast.Name’ node.

   - bpo-40826(6): 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-40824(7): Unexpected errors in calling the ‘__iter__’ method
     are no longer masked by ‘TypeError’ in the *note in: 7a8. operator
     and functions *note contains(): f09, *note indexOf(): f0a. and
     *note countOf(): f0b. of the *note operator: c3. module.

   - bpo-40663(8): Correctly generate annotations where parentheses are
     omitted but required (e.g: ‘Type[(str, int, *other))]’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41094

   (2) https://bugs.python.org/issue41056

   (3) https://bugs.python.org/issue35975

   (4) https://bugs.python.org/issue40957

   (5) https://bugs.python.org/issue40870

   (6) https://bugs.python.org/issue40826

   (7) https://bugs.python.org/issue40824

   (8) https://bugs.python.org/issue40663


File: python.info,  Node: Library<11>,  Next: Tests<6>,  Prev: Core and Builtins<11>,  Up: Python 3 8 4 release candidate 1

1.18.12.3 Library
.................

   - bpo-41138(1): Fixed the *note trace: 113. module CLI for Python
     source files with non-UTF-8 encoding.

   - bpo-31938(2): Fix default-value signatures of several functions in
     the *note select: e6. module - by Anthony Sottile.

   - bpo-41068(3): Fixed reading files with non-ASCII names from ZIP
     archive directly after writing them.

   - bpo-41058(4): ‘pdb.find_function()’ now correctly determines the
     source file encoding.

   - bpo-41056(5): Fix a NULL pointer dereference within the ssl module
     during a MemoryError in the keylog callback.  (discovered by
     Coverity)

   - bpo-41048(6): *note mimetypes.read_mime_types(): f0d. function
     reads the rule file using UTF-8 encoding, not the locale encoding.
     Patch by Srinivas Reddy Thatiparthy.

   - bpo-40448(7): *note ensurepip: 7a. now disables the use of ‘pip’
     cache when installing the bundled versions of ‘pip’ and
     ‘setuptools’.  Patch by Krzysztof Konopko.

   - bpo-40855(8): The standard deviation and variance functions in the
     statistics module were ignoring their mu and xbar arguments.

   - bpo-40807(9): Stop codeop._maybe_compile, used by
     code.InteractiveInterpreter (and IDLE). from from emitting each
     warning three times.

   - bpo-40834(10): Fix truncate when sending str object
     with_xxsubinterpreters.channel_send.

   - bpo-38488(11): Update ensurepip to install pip 20.1.1 and
     setuptools 47.1.0.

   - bpo-40767(12): *note webbrowser: 12a. 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-40795(13): *note ctypes: 2b. 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(): f0e.

   - bpo-30008(14): Fix *note ssl: f4. code to be compatible with
     OpenSSL 1.1.x builds that use ‘no-deprecated’ and ‘--api=1.1.0’.

   - bpo-40614(15): *note ast.parse(): 1a2. will not parse self
     documenting expressions in f-strings when passed ‘feature_version’
     is less than ‘(3, 8)’.

   - bpo-40626(16): 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-25872(17): *note linecache: a9. could crash with a *note
     KeyError: 2c8. when accessed from multiple threads.  Fix by Michael
     Graczyk.

   - bpo-40597(18): If text content lines are longer than
     policy.max_line_length, always use a content-encoding to make sure
     they are wrapped.

   - bpo-40515(19): The *note ssl: f4. and *note hashlib: 8d. 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-13097(20): ‘ctypes’ now raises an ‘ArgumentError’ when a
     callback is invoked with more than 1024 arguments.

   - bpo-40457(21): The ssl module now support OpenSSL builds without
     TLS 1.0 and 1.1 methods.

   - bpo-39830(22): Add *note zipfile.Path: f0f. to ‘__all__’ in the
     *note zipfile: 143. module.

   - bpo-40025(23): Raise TypeError when _generate_next_value_ is
     defined after members.  Patch by Ethan Onstott.

   - bpo-39244(24): Fixed
     ‘multiprocessing.context.get_all_start_methods’ to properly return
     the default method first on macOS.

   - bpo-39040(25): Fix parsing of invalid mime headers parameters by
     collapsing whitespace between encoded words in a bare-quote-string.

   - bpo-35714(26): *note struct.error: cb9. is now raised if there is a
     null character in a *note struct: f9. format string.

   - bpo-36290(27): AST nodes are now raising *note TypeError: 193. on
     conflicting keyword arguments.  Patch contributed by Rémi Lapeyre.

   - bpo-29620(28): *note assertWarns(): ac1. 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-34226(29): Fix *note cgi.parse_multipart: 2ef. without
     content_length.  Patch by Roger Duran

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41138

   (2) https://bugs.python.org/issue31938

   (3) https://bugs.python.org/issue41068

   (4) https://bugs.python.org/issue41058

   (5) https://bugs.python.org/issue41056

   (6) https://bugs.python.org/issue41048

   (7) https://bugs.python.org/issue40448

   (8) https://bugs.python.org/issue40855

   (9) https://bugs.python.org/issue40807

   (10) https://bugs.python.org/issue40834

   (11) https://bugs.python.org/issue38488

   (12) https://bugs.python.org/issue40767

   (13) https://bugs.python.org/issue40795

   (14) https://bugs.python.org/issue30008

   (15) https://bugs.python.org/issue40614

   (16) https://bugs.python.org/issue40626

   (17) https://bugs.python.org/issue25872

   (18) https://bugs.python.org/issue40597

   (19) https://bugs.python.org/issue40515

   (20) https://bugs.python.org/issue13097

   (21) https://bugs.python.org/issue40457

   (22) https://bugs.python.org/issue39830

   (23) https://bugs.python.org/issue40025

   (24) https://bugs.python.org/issue39244

   (25) https://bugs.python.org/issue39040

   (26) https://bugs.python.org/issue35714

   (27) https://bugs.python.org/issue36290

   (28) https://bugs.python.org/issue29620

   (29) https://bugs.python.org/issue34226


File: python.info,  Node: Tests<6>,  Next: Build<6>,  Prev: Library<11>,  Up: Python 3 8 4 release candidate 1

1.18.12.4 Tests
...............

   - bpo-41085(1): Fix integer overflow in the *note
     array.array.index(): f11. method on 64-bit Windows for index larger
     than ‘2**31’.

   - bpo-38377(2): On Linux, skip tests using multiprocessing if the
     current user cannot create a file in ‘/dev/shm/’ directory.  Add
     the ‘skip_if_broken_multiprocessing_synchronize()’ function to the
     *note test.support: 107. module.

   - bpo-41009(3): Fix use of
     ‘support.require_{linux|mac|freebsd}_version()’ decorators as class
     decorator.

   - bpo-41003(4): 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(5): Disable remote *note imaplib: 98. tests, host
     cyrus.andrew.cmu.edu is blocking incoming connections.

   - bpo-40055(6): 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-34401(7): Make test_gdb properly run on HP-UX. Patch by Michael
     Osipov.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41085

   (2) https://bugs.python.org/issue38377

   (3) https://bugs.python.org/issue41009

   (4) https://bugs.python.org/issue41003

   (5) https://bugs.python.org/issue40964

   (6) https://bugs.python.org/issue40055

   (7) https://bugs.python.org/issue34401


File: python.info,  Node: Build<6>,  Next: Windows<6>,  Prev: Tests<6>,  Up: Python 3 8 4 release candidate 1

1.18.12.5 Build
...............

   - bpo-40204(1): Pin Sphinx version to 2.3.1 in ‘Doc/Makefile’.

   - bpo-40653(2): Move _dirnameW out of HAVE_SYMLINK to fix a potential
     compiling issue.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40204

   (2) https://bugs.python.org/issue40653


File: python.info,  Node: Windows<6>,  Next: macOS<6>,  Prev: Build<6>,  Up: Python 3 8 4 release candidate 1

1.18.12.6 Windows
.................

   - bpo-41074(1): Fixed support of non-ASCII names in functions *note
     msilib.OpenDatabase(): f14. and *note msilib.init_database(): f15.
     and non-ASCII SQL in method *note msilib.Database.OpenView(): f16.

   - bpo-40164(2): Updates Windows OpenSSL to 1.1.1g

   - bpo-39631(3): Changes the registered MIME type for ‘.py’ files on
     Windows to ‘text/x-python’ instead of ‘text/plain’.

   - bpo-40677(4): Manually define IO_REPARSE_TAG_APPEXECLINK in case
     some old Windows SDK doesn’t have it.

   - bpo-40650(5): Include winsock2.h in pytime.c for timeval.

   - bpo-39148(6): Add IPv6 support to *note asyncio: a. 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/issue41074

   (2) https://bugs.python.org/issue40164

   (3) https://bugs.python.org/issue39631

   (4) https://bugs.python.org/issue40677

   (5) https://bugs.python.org/issue40650

   (6) https://bugs.python.org/issue39148


File: python.info,  Node: macOS<6>,  Next: IDLE<11>,  Prev: Windows<6>,  Up: Python 3 8 4 release candidate 1

1.18.12.7 macOS
...............

   - bpo-39580(1): Avoid opening Finder window if running installer from
     the command line.  Patch contributed by Rick Heil.

   - bpo-41100(2): 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-41005(3): fixed an XDG settings issue not allowing macos to
     open browser in webbrowser.py

   - bpo-40741(4): Update macOS installer to use SQLite 3.32.2.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39580

   (2) https://bugs.python.org/issue41100

   (3) https://bugs.python.org/issue41005

   (4) https://bugs.python.org/issue40741


File: python.info,  Node: IDLE<11>,  Next: Tools/Demos<3>,  Prev: macOS<6>,  Up: Python 3 8 4 release candidate 1

1.18.12.8 IDLE
..............

   - bpo-41144(1): Make Open Module open a special module such as
     os.path.

   - bpo-39885(2): Make context menu Cut and Copy work again when
     right-clicking within a selection.

   - bpo-40723(3): Make test_idle pass when run after import.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue41144

   (2) https://bugs.python.org/issue39885

   (3) https://bugs.python.org/issue40723


File: python.info,  Node: Tools/Demos<3>,  Prev: IDLE<11>,  Up: Python 3 8 4 release candidate 1

1.18.12.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-40163(2): 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/issue40479

   (2) https://bugs.python.org/issue40163


File: python.info,  Node: Python 3 8 3 final,  Next: Python 3 8 3 release candidate 1,  Prev: Python 3 8 4 release candidate 1,  Up: Changelog（更動日誌）

1.18.13 Python 3.8.3 final
--------------------------

`Release date: 2020-05-13'

* Menu:

* Core and Builtins: Core and Builtins<12>.
* Library: Library<12>.
* Documentation: Documentation<10>.
* Windows: Windows<7>.
* C API: C API<5>.


File: python.info,  Node: Core and Builtins<12>,  Next: Library<12>,  Up: Python 3 8 3 final

1.18.13.1 Core and Builtins
...........................

   - bpo-40527(1): Fix command line argument parsing: no longer write
     errors multiple times into stderr.

   - bpo-40417(2): Fix imp module deprecation warning when
     PyImport_ReloadModule is called.  Patch by Robert Rouhani.

   - bpo-39562(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’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40527

   (2) https://bugs.python.org/issue40417

   (3) https://bugs.python.org/issue39562


File: python.info,  Node: Library<12>,  Next: Documentation<10>,  Prev: Core and Builtins<12>,  Up: Python 3 8 3 final

1.18.13.2 Library
.................

   - bpo-40559(1): Fix possible memory leak in the C implementation of
     *note asyncio.Task: 1ae.

   - bpo-40355(2): Improve error reporting in *note ast.literal_eval():
     4aa. in the presence of malformed ‘ast.Dict’ nodes instead of
     silently ignoring any non-conforming elements.  Patch by Curtis
     Bucher.

   - bpo-40459(3): *note platform.win32_ver(): f1d. now produces correct
     `ptype' strings instead of empty strings.

   - bpo-40398(4): *note typing.get_args(): 245. now always returns an
     empty tuple for special generic aliases.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40559

   (2) https://bugs.python.org/issue40355

   (3) https://bugs.python.org/issue40459

   (4) https://bugs.python.org/issue40398


File: python.info,  Node: Documentation<10>,  Next: Windows<7>,  Prev: Library<12>,  Up: Python 3 8 3 final

1.18.13.3 Documentation
.......................

   - bpo-40561(1): Provide docstrings for webbrowser open functions.

   - bpo-39435(2): Fix an incorrect signature for *note pickle.loads():
     5c8. in the docs

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40561

   (2) https://bugs.python.org/issue39435


File: python.info,  Node: Windows<7>,  Next: C API<5>,  Prev: Documentation<10>,  Up: Python 3 8 3 final

1.18.13.4 Windows
.................

   - bpo-40458(1): Increase reserved stack space to prevent overflow
     crash on Windows.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40458


File: python.info,  Node: C API<5>,  Prev: Windows<7>,  Up: Python 3 8 3 final

1.18.13.5 C API
...............

   - bpo-40412(1): Nullify inittab_copy during finalization, preventing
     future interpreter initializations in an embedded situation from
     crashing.  Patch by Gregory Szorc.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40412


File: python.info,  Node: Python 3 8 3 release candidate 1,  Next: Python 3 8 2 final,  Prev: Python 3 8 3 final,  Up: Changelog（更動日誌）

1.18.14 Python 3.8.3 release candidate 1
----------------------------------------

`Release date: 2020-04-29'

* Menu:

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


File: python.info,  Node: Security<9>,  Next: Core and Builtins<13>,  Up: Python 3 8 3 release candidate 1

1.18.14.1 Security
..................

   - bpo-40121(1): Fixes audit events raised on creating a new socket.

   - bpo-38576(2): Disallow control characters in hostnames in
     http.client, addressing CVE-2019-18348.  Such potentially malicious
     header injection URLs now cause a InvalidURL to be raised.

   - bpo-39503(3): CVE-2020-8492: The *note AbstractBasicAuthHandler:
     e97. class of the *note urllib.request: 121. 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/issue40121

   (2) https://bugs.python.org/issue38576

   (3) https://bugs.python.org/issue39503


File: python.info,  Node: Core and Builtins<13>,  Next: Library<13>,  Prev: Security<9>,  Up: Python 3 8 3 release candidate 1

1.18.14.2 Core and Builtins
...........................

   - bpo-20526(1): Fix *note PyThreadState_Clear(): f24.
     ‘PyThreadState.frame’ is a borrowed reference, not a strong
     reference: ‘PyThreadState_Clear()’ must not call
     ‘Py_CLEAR(tstate->frame)’.

   - bpo-39965(2): 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(3): Allow executing asynchronous comprehensions on the
     top level when the ‘PyCF_ALLOW_TOP_LEVEL_AWAIT’ flag is given.
     Patch by Batuhan Taskaya.

   - bpo-38894(4): 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-39871(5): Fix a possible *note SystemError: 600. in
     ‘math.{atan2,copysign,remainder}()’ when the first argument cannot
     be converted to a *note float: 188.  Patch by Zackery Spytz.

   - bpo-39776(6): 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(7): Fixed a crash due to incorrect handling of weak
     references in ‘collections.OrderedDict’ classes.  Patch by Pablo
     Galindo.

   - bpo-39520(8): Fix unparsing of ext slices with no items
     (‘foo[:,]’).  Patch by Batuhan Taskaya.

   - bpo-22490(9): Don’t leak environment variable ‘__PYVENV_LAUNCHER__’
     into the interpreter session on macOS.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20526

   (2) https://bugs.python.org/issue39965

   (3) https://bugs.python.org/issue39562

   (4) https://bugs.python.org/issue38894

   (5) https://bugs.python.org/issue39871

   (6) https://bugs.python.org/issue39776

   (7) https://bugs.python.org/issue39778

   (8) https://bugs.python.org/issue39520

   (9) https://bugs.python.org/issue22490


File: python.info,  Node: Library<13>,  Next: Documentation<11>,  Prev: Core and Builtins<13>,  Up: Python 3 8 3 release candidate 1

1.18.14.3 Library
.................

   - bpo-40138(1): Fix the Windows implementation of *note os.waitpid():
     672. for exit code larger than ‘INT_MAX >> 8’.  The exit status is
     now interpreted as an unsigned number.

   - bpo-39942(2): Set "__main__" as the default module name when
     "__name__" is missing in *note typing.TypeVar: f26.  Patch by
     Weipeng Hong.

   - bpo-40330(3): In ‘ShareableList.__setitem__()’, check the size of a
     new string item after encoding it to utf-8, not before.

   - bpo-40287(4): Fixed ‘SpooledTemporaryFile.seek()’ to return the
     position.

   - bpo-40260(5): Ensure *note modulefinder: b5. uses *note
     io.open_code(): f27. and respects coding comments.

   - bpo-40196(6): Fix a bug in the *note symtable: fd. module that was
     causing incorrectly report global variables as local.  Patch by
     Pablo Galindo.

   - bpo-40126(7): 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-40089(8): 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-39503(9): *note AbstractBasicAuthHandler: e97. of *note
     urllib.request: 121. now parses all WWW-Authenticate HTTP headers
     and accepts multiple challenges per header: use the realm of the
     first Basic challenge.

   - bpo-40014(10): 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-40016(11): In re docstring, clarify the relationship between
     inline and argument compile flags.

   - bpo-39953(12): Update internal table of OpenSSL error codes in the
     ‘ssl’ module.

   - bpo-39360(13): 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-39652(14): The column name found in
     ‘sqlite3.Cursor.description’ is now truncated on the first ’[’ only
     if the PARSE_COLNAMES option is set.

   - bpo-39915(15): Ensure *note
     unittest.mock.AsyncMock.await_args_list: f28. has call objects in
     the order of awaited arguments instead of using *note
     unittest.mock.Mock.call_args: f29. which has the last value of the
     call.  Patch by Karthikeyan Singaravelan.

   - bpo-38662(16): 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-39916(17): More reliable use of ‘os.scandir()’ in
     ‘Path.glob()’.  It no longer emits a ResourceWarning when
     interrupted.

   - bpo-39850(18): *note multiprocessing: b8. now supports abstract
     socket addresses (if abstract sockets are supported in the running
     platform).  Patch by Pablo Galindo.

   - bpo-39828(19): Fix *note json.tool: a6. to catch *note
     BrokenPipeError: 9a2.  Patch by Dong-hee Na.

   - bpo-13487(20): Avoid a possible `"RuntimeError: dictionary changed
     size during iteration"' from *note inspect.getmodule(): f2a. when
     it tried to loop through *note sys.modules: f2b.

   - bpo-39794(21): Add –without-decimal-contextvar build option.  This
     enables a thread-local rather than a coroutine local context.

   - bpo-39769(22): The *note compileall.compile_dir(): 377. 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-39517(23): Fix runpy.run_path() when using pathlike objects

   - bpo-39764(24): Fix AttributeError when calling get_stack on a
     PyAsyncGenObject Task

   - bpo-30566(25): Fix *note IndexError: e7a. when trying to decode an
     invalid string with punycode codec.

   - bpo-39667(26): Correct performance degradation in ‘zipfile.Path’ as
     found in zipp 3.0.  While retaining compatibility, this change
     discourages the use of ‘zipfile.Path.open’ due to the signature
     change in Python 3.9.  For compatibility across Python 3.8 and
     later versions, consider using ‘zipp.Path’ on Python 3.8.x and
     earlier.

   - bpo-39548(27): Fix handling of header in *note
     urllib.request.AbstractDigestAuthHandler: f2c. when the optional
     ‘qop’ parameter is not present.

   - bpo-38971(28): 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-38410(29): Properly handle *note sys.audit(): f2d. failures in
     *note sys.set_asyncgen_hooks(): f2e.  Based on patch by Zackery
     Spytz.

   - bpo-36541(30): lib2to3 now recognizes named assignment expressions
     (the walrus operator, ‘:=’)

   - bpo-31758(31): Prevent crashes when using an uninitialized
     ‘_elementtree.XMLParser’ object.  Patch by Oren Milman.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40138

   (2) https://bugs.python.org/issue39942

   (3) https://bugs.python.org/issue40330

   (4) https://bugs.python.org/issue40287

   (5) https://bugs.python.org/issue40260

   (6) https://bugs.python.org/issue40196

   (7) https://bugs.python.org/issue40126

   (8) https://bugs.python.org/issue40089

   (9) https://bugs.python.org/issue39503

   (10) https://bugs.python.org/issue40014

   (11) https://bugs.python.org/issue40016

   (12) https://bugs.python.org/issue39953

   (13) https://bugs.python.org/issue39360

   (14) https://bugs.python.org/issue39652

   (15) https://bugs.python.org/issue39915

   (16) https://bugs.python.org/issue38662

   (17) https://bugs.python.org/issue39916

   (18) https://bugs.python.org/issue39850

   (19) https://bugs.python.org/issue39828

   (20) https://bugs.python.org/issue13487

   (21) https://bugs.python.org/issue39794

   (22) https://bugs.python.org/issue39769

   (23) https://bugs.python.org/issue39517

   (24) https://bugs.python.org/issue39764

   (25) https://bugs.python.org/issue30566

   (26) https://bugs.python.org/issue39667

   (27) https://bugs.python.org/issue39548

   (28) https://bugs.python.org/issue38971

   (29) https://bugs.python.org/issue38410

   (30) https://bugs.python.org/issue36541

   (31) https://bugs.python.org/issue31758


File: python.info,  Node: Documentation<11>,  Next: Tests<7>,  Prev: Library<13>,  Up: Python 3 8 3 release candidate 1

1.18.14.4 Documentation
.......................

   - bpo-27635(1): The pickle documentation incorrectly claimed that
     ‘__new__’ isn’t called by default when unpickling.

   - bpo-39879(2): Updated *note Data model: f30. docs to include *note
     dict(): 1b9. insertion order preservation.  Patch by Furkan Onder
     and Samy Lahfa.

   - bpo-39868(3): Updated the Language Reference for PEP 572(4).

   - bpo-13790(5): Change ’string’ to ’specification’ in format doc.

   - bpo-17422(6): The language reference no longer restricts default
     class namespaces to dicts only.

   - bpo-39530(7): Fix misleading documentation about mixed-type numeric
     comparisons.

   - bpo-39718(8): Update *note token: 111. documentation to reflect
     additions in Python 3.8

   - bpo-39677(9): Changed operand name of `MAKE_FUNCTION' from `argc'
     to `flags' for module *note dis: 38.

   - bpo-38387(10): Document *note PyDoc_STRVAR: f31. macro in the C-API
     reference.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27635

   (2) https://bugs.python.org/issue39879

   (3) https://bugs.python.org/issue39868

   (4) https://www.python.org/dev/peps/pep-0572

   (5) https://bugs.python.org/issue13790

   (6) https://bugs.python.org/issue17422

   (7) https://bugs.python.org/issue39530

   (8) https://bugs.python.org/issue39718

   (9) https://bugs.python.org/issue39677

   (10) https://bugs.python.org/issue38387


File: python.info,  Node: Tests<7>,  Next: Build<7>,  Prev: Documentation<11>,  Up: Python 3 8 3 release candidate 1

1.18.14.5 Tests
...............

   - bpo-40436(1): test_gdb and test.pythoninfo now check gdb command
     exit code.

   - 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-40019(4): test_gdb now skips tests if it detects that gdb
     failed to read debug information because the Python binary is
     optimized.

   - bpo-27807(5): ‘test_site.test_startup_imports()’ is now skipped if
     a path of *note sys.path: 48d. contains a ‘.pth’ file.

   - bpo-39793(6): Use the same domain when testing ‘make_msgid’.  Patch
     by Batuhan Taskaya.

   - bpo-1812(7): Fix newline handling in doctest.testfile when loading
     from a package whose loader has a get_data method.  Patch by Peter
     Donis.

   - bpo-37957(8): 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.

   - bpo-38502(9): test.regrtest now uses process groups in the
     multiprocessing mode (-jN command line option) if process groups
     are available: if *note os.setsid(): f33. and *note os.killpg():
     f34. functions are available.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40436

   (2) https://bugs.python.org/issue40162

   (3) https://bugs.python.org/issue40146

   (4) https://bugs.python.org/issue40019

   (5) https://bugs.python.org/issue27807

   (6) https://bugs.python.org/issue39793

   (7) https://bugs.python.org/issue1812

   (8) https://bugs.python.org/issue37957

   (9) https://bugs.python.org/issue38502


File: python.info,  Node: Build<7>,  Next: Windows<8>,  Prev: Tests<7>,  Up: Python 3 8 3 release candidate 1

1.18.14.6 Build
...............

   - bpo-38360(1): Support single-argument form of macOS -isysroot flag.

   - bpo-40204(2): Pin Sphinx version to 1.8.2 in ‘Doc/Makefile’.

   - bpo-40158(3): Fix CPython MSBuild Properties in NuGet Package
     (build/native/python.props)

   - bpo-38527(4): 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/issue38360

   (2) https://bugs.python.org/issue40204

   (3) https://bugs.python.org/issue40158

   (4) https://bugs.python.org/issue38527


File: python.info,  Node: Windows<8>,  Next: macOS<7>,  Prev: Build<7>,  Up: Python 3 8 3 release candidate 1

1.18.14.7 Windows
.................

   - bpo-40164(1): Updates Windows to OpenSSL 1.1.1f

   - bpo-39930(2): Ensures the required ‘vcruntime140.dll’ is included
     in install packages.

   - bpo-39847(3): Avoid hang when computer is hibernated whilst waiting
     for a mutex (for lock-related objects from *note threading: 10a.)
     around 49-day uptime.

   - bpo-38597(4): *note distutils: 39. 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(5): Update Windows builds to use SQLite 3.31.1

   - bpo-39789(6): Update Windows release build machines to Visual
     Studio 2019 (MSVC 14.2).

   - bpo-34803(7): Package for nuget.org now includes repository
     reference and bundled icon image.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40164

   (2) https://bugs.python.org/issue39930

   (3) https://bugs.python.org/issue39847

   (4) https://bugs.python.org/issue38597

   (5) https://bugs.python.org/issue38380

   (6) https://bugs.python.org/issue39789

   (7) https://bugs.python.org/issue34803


File: python.info,  Node: macOS<7>,  Next: IDLE<12>,  Prev: Windows<8>,  Up: Python 3 8 3 release candidate 1

1.18.14.8 macOS
...............

   - bpo-40164(1): Update macOS installer builds to use OpenSSL 1.1.1g.

   - bpo-38380(2): Update macOS builds to use SQLite 3.31.1

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40164

   (2) https://bugs.python.org/issue38380


File: python.info,  Node: IDLE<12>,  Next: Tools/Demos<4>,  Prev: macOS<7>,  Up: Python 3 8 3 release candidate 1

1.18.14.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.

   - bpo-38439(5): 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(6): IDLE will no longer freeze when inspect.signature
     fails when fetching a calltip.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27115

   (2) https://bugs.python.org/issue39885

   (3) https://bugs.python.org/issue39852

   (4) https://bugs.python.org/issue39781

   (5) https://bugs.python.org/issue38439

   (6) https://bugs.python.org/issue38689


File: python.info,  Node: Tools/Demos<4>,  Next: C API<6>,  Prev: IDLE<12>,  Up: Python 3 8 3 release candidate 1

1.18.14.10 Tools/Demos
......................

   - bpo-40179(1): Fixed translation of ‘#elif’ in Argument Clinic.

   - bpo-36184(2): 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-39889(3): Fixed ‘unparse.py’ 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]’).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue40179

   (2) https://bugs.python.org/issue36184

   (3) https://bugs.python.org/issue39889


File: python.info,  Node: C API<6>,  Prev: Tools/Demos<4>,  Up: Python 3 8 3 release candidate 1

1.18.14.11 C API
................

   - bpo-35370(1): If *note PySys_Audit(): f3b. fails in *note
     PyEval_SetProfile(): e40. or *note PyEval_SetTrace(): e41, log the
     error as an unraisable exception.

   - bpo-39884(2): *note PyDescr_NewMethod(): f3c. and
     ‘PyCFunction_NewEx()’ now include the method name in the
     SystemError "bad call flags" error message to ease debug.

   - bpo-38643(3): *note PyNumber_ToBase(): f3d. now raises a *note
     SystemError: 600. instead of crashing when called with invalid
     base.

   - bpo-38913(4): Fixed segfault in ‘Py_BuildValue()’ called with a
     format containing "#" and undefined PY_SSIZE_T_CLEAN whwn an
     exception is set.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35370

   (2) https://bugs.python.org/issue39884

   (3) https://bugs.python.org/issue38643

   (4) https://bugs.python.org/issue38913


File: python.info,  Node: Python 3 8 2 final,  Next: Python 3 8 2 release candidate 2,  Prev: Python 3 8 3 release candidate 1,  Up: Changelog（更動日誌）

1.18.15 Python 3.8.2 final
--------------------------

`Release date: 2020-02-24'

* Menu:

* Core and Builtins: Core and Builtins<14>.
* Library: Library<14>.
* Documentation: Documentation<12>.
* IDLE: IDLE<13>.


File: python.info,  Node: Core and Builtins<14>,  Next: Library<14>,  Up: Python 3 8 2 final

1.18.15.1 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-39427(2): Document all possibilities for the ‘-X’ options in
     the command line help section.  Patch by Pablo Galindo.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39382

   (2) https://bugs.python.org/issue39427


File: python.info,  Node: Library<14>,  Next: Documentation<12>,  Prev: Core and Builtins<14>,  Up: Python 3 8 2 final

1.18.15.2 Library
.................

   - bpo-39649(1): Remove obsolete check for ‘__args__’ in
     bdb.Bdb.format_stack_entry.

   - bpo-39681(2): 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-39546(3): Fix a regression in *note ArgumentParser: 69a. where
     ‘allow_abbrev=False’ was ignored for long options that used a
     prefix character other than "-".

   - bpo-39432(4): Implement PEP-489 algorithm for non-ascii
     "PyInit_..."  symbol names in distutils to make it export the
     correct init symbol also on Windows.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39649

   (2) https://bugs.python.org/issue39681

   (3) https://bugs.python.org/issue39546

   (4) https://bugs.python.org/issue39432


File: python.info,  Node: Documentation<12>,  Next: IDLE<13>,  Prev: Library<14>,  Up: Python 3 8 2 final

1.18.15.3 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 TypeDict.

   - bpo-39654(3): In pyclbr doc, update ’class’ to ’module’ where
     appropriate and add readmodule comment.  Patch by Hakan Çelik.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17422

   (2) https://bugs.python.org/issue39572

   (3) https://bugs.python.org/issue39654


File: python.info,  Node: IDLE<13>,  Prev: Documentation<12>,  Up: Python 3 8 2 final

1.18.15.4 IDLE
..............

   - bpo-39663(1): Add tests for pyparse find_good_parse_start().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39663


File: python.info,  Node: Python 3 8 2 release candidate 2,  Next: Python 3 8 2 release candidate 1,  Prev: Python 3 8 2 final,  Up: Changelog（更動日誌）

1.18.16 Python 3.8.2 release candidate 2
----------------------------------------

`Release date: 2020-02-17'

* Menu:

* Security: Security<10>.
* Core and Builtins: Core and Builtins<15>.
* Library: Library<15>.
* IDLE: IDLE<14>.


File: python.info,  Node: Security<10>,  Next: Core and Builtins<15>,  Up: Python 3 8 2 release candidate 2

1.18.16.1 Security
..................

   - bpo-39184(1): Add audit events to functions in *note fcntl: 7e,
     *note msvcrt: b7, *note os: c5, *note resource: e1, *note shutil:
     ea, *note signal: eb. and *note syslog: 100.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39184


File: python.info,  Node: Core and Builtins<15>,  Next: Library<15>,  Prev: Security<10>,  Up: Python 3 8 2 release candidate 2

1.18.16.2 Core and Builtins
...........................

   - bpo-39619(1): Enable use of *note os.chroot(): f46. on HP-UX
     systems.

   - bpo-39606(2): Fix regression caused by fix for bpo-39386(3), that
     prevented calling ‘aclose’ on an async generator that had already
     been closed or exhausted.

   - bpo-39453(4): Fixed a possible crash in ‘list.__contains__()’ when
     a list is changed during comparing items.  Patch by Dong-hee Na.

   - bpo-39219(5): Syntax errors raised in the tokenizer now always set
     correct "text" and "offset" attributes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39619

   (2) https://bugs.python.org/issue39606

   (3) https://bugs.python.org/issue39386

   (4) https://bugs.python.org/issue39453

   (5) https://bugs.python.org/issue39219


File: python.info,  Node: Library<15>,  Next: IDLE<14>,  Prev: Core and Builtins<15>,  Up: Python 3 8 2 release candidate 2

1.18.16.3 Library
.................

   - bpo-27657(1): The original fix for bpo-27657(2), "Fix urlparse()
     with numeric paths" (GH-16839) included in 3.8.1, inadvertently
     introduced a behavior change that broke several third-party
     packages relying on the original undefined parsing behavior.  The
     change is reverted in 3.8.2, restoring the behavior of 3.8.0 and
     earlier releases.

   - bpo-39474(3): Fixed starting position of AST for expressions like
     ‘(a)(b)’, ‘(a)[b]’ and ‘(a).b’.

   - bpo-21016(4): The *note pydoc: da. and *note trace: 113. modules
     now use the *note sysconfig: ff. 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-39595(5): 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(6).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27657

   (2) https://bugs.python.org/issue27657

   (3) https://bugs.python.org/issue39474

   (4) https://bugs.python.org/issue21016

   (5) https://bugs.python.org/issue39595

   (6) 
https://importlib-metadata.readthedocs.io/en/latest/changelog%20(links).html#v1-5-0


File: python.info,  Node: IDLE<14>,  Prev: Library<15>,  Up: Python 3 8 2 release candidate 2

1.18.16.4 IDLE
..............

   - bpo-39600(1): In the font configuration window, remove duplicated
     font names.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39600


File: python.info,  Node: Python 3 8 2 release candidate 1,  Next: Python 3 8 1 final,  Prev: Python 3 8 2 release candidate 2,  Up: Changelog（更動日誌）

1.18.17 Python 3.8.2 release candidate 1
----------------------------------------

`Release date: 2020-02-10'

* Menu:

* Security: Security<11>.
* Core and Builtins: Core and Builtins<16>.
* Library: Library<16>.
* Documentation: Documentation<13>.
* Tests: Tests<8>.
* Build: Build<8>.
* Windows: Windows<9>.
* IDLE: IDLE<15>.


File: python.info,  Node: Security<11>,  Next: Core and Builtins<16>,  Up: Python 3 8 2 release candidate 1

1.18.17.1 Security
..................

   - bpo-39401(1): Avoid unsafe load of
     ‘api-ms-win-core-path-l1-1-0.dll’ at startup on Windows 7.

   - bpo-39184(2): Add audit events to command execution functions in os
     and pty modules.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39401

   (2) https://bugs.python.org/issue39184


File: python.info,  Node: Core and Builtins<16>,  Next: Library<16>,  Prev: Security<11>,  Up: Python 3 8 2 release candidate 1

1.18.17.2 Core and Builtins
...........................

   - bpo-39579(1): 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-39510(2): Fix segfault in ‘readinto()’ method on closed
     BufferedReader.

   - bpo-39492(3): Fix a reference cycle in the C Pickler that was
     preventing the garbage collection of deleted, pickled objects.

   - bpo-39421(4): Fix possible crashes when operating with the
     functions in the *note heapq: 8e. module and custom comparison
     operators.

   - bpo-39386(5): Prevent double awaiting of async iterator.

   - bpo-39235(6): Fix AST end location for lone generator expression in
     function call, e.g.  f(i for i in a).

   - bpo-39209(7): Correctly handle multi-line tokens in interactive
     mode.  Patch by Pablo Galindo.

   - bpo-39216(8): Fix constant folding optimization for positional only
     arguments - by Anthony Sottile.

   - bpo-39215(9): Fix ‘SystemError’ when nested function has annotation
     on positional-only argument - by Anthony Sottile.

   - bpo-38588(10): Fix possible crashes in dict and list when calling
     *note PyObject_RichCompareBool(): f4c.

   - bpo-38610(11): Fix possible crashes in several list methods by
     holding strong references to list elements when calling *note
     PyObject_RichCompareBool(): f4c.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39579

   (2) https://bugs.python.org/issue39510

   (3) https://bugs.python.org/issue39492

   (4) https://bugs.python.org/issue39421

   (5) https://bugs.python.org/issue39386

   (6) https://bugs.python.org/issue39235

   (7) https://bugs.python.org/issue39209

   (8) https://bugs.python.org/issue39216

   (9) https://bugs.python.org/issue39215

   (10) https://bugs.python.org/issue38588

   (11) https://bugs.python.org/issue38610


File: python.info,  Node: Library<16>,  Next: Documentation<13>,  Prev: Core and Builtins<16>,  Up: Python 3 8 2 release candidate 1

1.18.17.3 Library
.................

   - bpo-39590(1): Collections.deque now holds strong references during
     deque.__contains__ and deque.count, fixing crashes.

   - bpo-38149(2): *note sys.audit(): f2d. is now called only once per
     call of *note glob.glob(): 5cb. and *note glob.iglob(): 5cc.

   - bpo-39450(3): Striped whitespace from docstring before returning it
     from ‘unittest.case.shortDescription()’.

   - bpo-39493(4): Mark ‘typing.IO.closed’ as a property

   - bpo-39485(5): Fix a bug in *note unittest.mock.create_autospec():
     f4e. that would complain about the wrong number of arguments for
     custom descriptors defined in an extension module returning
     functions.

   - bpo-39082(6): Allow AsyncMock to correctly patch static/class
     methods

   - bpo-39430(7): Fixed race condition in lazy imports in *note
     tarfile: 102.

   - bpo-39390(8): Fixed a regression with the ‘ignore’ callback of
     *note shutil.copytree(): 21b.  The argument types are now str and
     List[str] again.

   - bpo-39389(9): Write accurate compression level metadata in *note
     gzip: 8c. archives, rather than always signaling maximum
     compression.

   - bpo-39274(10): ‘bool(fraction.Fraction)’ now returns a boolean even
     if (numerator != 0) does not return a boolean (ex: numpy number).

   - bpo-39297(11): Improved performance of importlib.metadata
     distribution discovery and resilients to inaccessible sys.path
     entries (importlib_metadata v1.4.0).

   - bpo-39242(12): Updated the Gmane domain from news.gmane.org to
     news.gmane.io which is used for examples of *note NNTP: a31. news
     reader server and nntplib tests.

   - bpo-38907(13): In http.server script, restore binding to IPv4 on
     Windows.

   - bpo-39152(14): Fix ttk.Scale.configure([name]) to return
     configuration tuple for name or all options.  Giovanni Lombardo
     contributed part of the patch.

   - bpo-39198(15): If an exception were to be thrown in
     ‘Logger.isEnabledFor’ (say, by asyncio timeouts or stopit) , the
     *note logging: ab. 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(16): 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(17): Correctly parenthesize filter-based statements that
     contain lambda expressions in mod:*note lib2to3: a8.  Patch by
     Dong-hee Na.

   - bpo-39142(18): 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-39129(19): Fix import path for ‘asyncio.TimeoutError’

   - bpo-39057(20): ‘urllib.request.proxy_bypass_environment()’ now
     ignores leading dots and no longer ignores a trailing newline.

   - bpo-39056(21): Fixed handling invalid warning category in the -W
     option.  No longer import the re module if it is not needed.

   - bpo-39055(22): *note base64.b64decode(): f4f. with ‘validate=True’
     raises now a binascii.Error if the input ends with a single ‘\n’.

   - bpo-39033(23): Fix *note NameError: d80. in *note zipimport: 144.
     Patch by Karthikeyan Singaravelan.

   - bpo-38878(24): Fixed __subclasshook__ of *note os.PathLike: 4f0. to
     return a correct result upon inheritence.  Patch by Bar Harel.

   - bpo-35182(25): 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-38473(26): Use signature from inner mock for autospecced
     methods attached with ‘unittest.mock.attach_mock()’.  Patch by
     Karthikeyan Singaravelan.

   - bpo-38293(27): Add *note copy.copy(): 3d0. and *note
     copy.deepcopy(): 3d1. support to *note property(): 1d8. objects.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39590

   (2) https://bugs.python.org/issue38149

   (3) https://bugs.python.org/issue39450

   (4) https://bugs.python.org/issue39493

   (5) https://bugs.python.org/issue39485

   (6) https://bugs.python.org/issue39082

   (7) https://bugs.python.org/issue39430

   (8) https://bugs.python.org/issue39390

   (9) https://bugs.python.org/issue39389

   (10) https://bugs.python.org/issue39274

   (11) https://bugs.python.org/issue39297

   (12) https://bugs.python.org/issue39242

   (13) https://bugs.python.org/issue38907

   (14) https://bugs.python.org/issue39152

   (15) https://bugs.python.org/issue39198

   (16) https://bugs.python.org/issue39191

   (17) https://bugs.python.org/issue38871

   (18) https://bugs.python.org/issue39142

   (19) https://bugs.python.org/issue39129

   (20) https://bugs.python.org/issue39057

   (21) https://bugs.python.org/issue39056

   (22) https://bugs.python.org/issue39055

   (23) https://bugs.python.org/issue39033

   (24) https://bugs.python.org/issue38878

   (25) https://bugs.python.org/issue35182

   (26) https://bugs.python.org/issue38473

   (27) https://bugs.python.org/issue38293


File: python.info,  Node: Documentation<13>,  Next: Tests<8>,  Prev: Library<16>,  Up: Python 3 8 2 release candidate 1

1.18.17.4 Documentation
.......................

   - bpo-39153(1): Clarify refcounting semantics for the following
     functions: - PyObject_SetItem - PyMapping_SetItemString -
     PyDict_SetItem - PyDict_SetItemString

   - bpo-39392(2): Explain that when filling with turtle, overlap
     regions may be left unfilled.

   - bpo-39381(3): Mention in docs that *note asyncio.get_event_loop():
     35a. implicitly creates new event loop only if called from the main
     thread.

   - bpo-38918(4): Add an entry for ‘__module__’ in the "function" &
     "method" sections of the inspect docs types and members table(5)

   - bpo-3530(6): In the *note ast: 8. 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/issue39153

   (2) https://bugs.python.org/issue39392

   (3) https://bugs.python.org/issue39381

   (4) https://bugs.python.org/issue38918

   (5) https://docs.python.org/3/library/inspect.html#types-and-members

   (6) https://bugs.python.org/issue3530


File: python.info,  Node: Tests<8>,  Next: Build<8>,  Prev: Documentation<13>,  Up: Python 3 8 2 release candidate 1

1.18.17.5 Tests
...............

   - bpo-39502(1): Skip test_zipfile.test_add_file_after_2107() if *note
     time.localtime(): f52. fails with *note OverflowError: 965.  It is
     the case on AIX 6.1 for example.

   - bpo-38546(2): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39502

   (2) https://bugs.python.org/issue38546


File: python.info,  Node: Build<8>,  Next: Windows<9>,  Prev: Tests<8>,  Up: Python 3 8 2 release candidate 1

1.18.17.6 Build
...............

   - bpo-39144(1): The ctags and etags build targets both include
     Modules/_ctypes and Python standard library source files.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39144


File: python.info,  Node: Windows<9>,  Next: IDLE<15>,  Prev: Build<8>,  Up: Python 3 8 2 release candidate 1

1.18.17.7 Windows
.................

   - bpo-39439(1): Honor the Python path when a virtualenv is active on
     Windows.

   - bpo-39393(2): Improve the error message when attempting to load a
     DLL with unresolved dependencies.

   - bpo-38883(3): *note home(): 730. and *note expanduser(): 72f. 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(): 1ff, which was changed to
     ignore ‘HOME’ in 3.8, see bpo-36264(4).

   - bpo-39185(5): The build.bat script has additional options for
     very-quiet output (-q) and very-verbose output (-vv)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39439

   (2) https://bugs.python.org/issue39393

   (3) https://bugs.python.org/issue38883

   (4) https://bugs.python.org/issue36264

   (5) https://bugs.python.org/issue39185


File: python.info,  Node: IDLE<15>,  Prev: Windows<9>,  Up: Python 3 8 2 release candidate 1

1.18.17.8 IDLE
..............

   - bpo-30780(1): Add remaining configdialog tests for buttons and
     highlights and keys tabs.

   - bpo-39388(2): IDLE Settings Cancel button now cancels pending
     changes

   - bpo-39050(3): Make IDLE Settings dialog Help button work again.

   - bpo-34118(4): Tag memoryview, range, and tuple as classes, the same
     as list, etcetera, in the library manual built-in functions list.

   - bpo-38792(5): Close an IDLE shell calltip if a *note
     KeyboardInterrupt: 198. or shell restart occurs.  Patch by Zackery
     Spytz.

   - bpo-32989(6): 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/issue30780

   (2) https://bugs.python.org/issue39388

   (3) https://bugs.python.org/issue39050

   (4) https://bugs.python.org/issue34118

   (5) https://bugs.python.org/issue38792

   (6) https://bugs.python.org/issue32989


File: python.info,  Node: Python 3 8 1 final,  Next: Python 3 8 1 release candidate 1,  Prev: Python 3 8 2 release candidate 1,  Up: Changelog（更動日誌）

1.18.18 Python 3.8.1 final
--------------------------

`Release date: 2019-12-18'

* Menu:

* Core and Builtins: Core and Builtins<17>.
* Library: Library<17>.
* Tests: Tests<9>.
* Windows: Windows<10>.
* macOS: macOS<8>.
* IDLE: IDLE<16>.


File: python.info,  Node: Core and Builtins<17>,  Next: Library<17>,  Up: Python 3 8 1 final

1.18.18.1 Core and Builtins
...........................

   - bpo-39080(1): 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(2): 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-39008(3): *note PySys_Audit(): f3b. 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39080

   (2) https://bugs.python.org/issue39031

   (3) https://bugs.python.org/issue39008


File: python.info,  Node: Library<17>,  Next: Tests<9>,  Prev: Core and Builtins<17>,  Up: Python 3 8 1 final

1.18.18.2 Library
.................

   - bpo-39022(1): Update importlib.metadata to include improvements
     from importlib_metadata 1.3 including better serialization of
     EntryPoints and improved documentation for custom finders.

   - bpo-38811(2): Fix an unhandled exception in *note pathlib: c9. when
     *note os.link(): a3a. is missing.  Patch by Toke Høiland-Jørgensen.

   - bpo-36406(3): Handle namespace packages in *note doctest: 67.
     Patch by Karthikeyan Singaravelan.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39022

   (2) https://bugs.python.org/issue38811

   (3) https://bugs.python.org/issue36406


File: python.info,  Node: Tests<9>,  Next: Windows<10>,  Prev: Library<17>,  Up: Python 3 8 1 final

1.18.18.3 Tests
...............

   - bpo-38546(1): Multiprocessing and concurrent.futures tests now stop
     the resource tracker process when tests complete.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38546


File: python.info,  Node: Windows<10>,  Next: macOS<8>,  Prev: Tests<9>,  Up: Python 3 8 1 final

1.18.18.4 Windows
.................

   - bpo-39007(1): Add auditing events to functions in *note winreg:
     12b.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39007


File: python.info,  Node: macOS<8>,  Next: IDLE<16>,  Prev: Windows<10>,  Up: Python 3 8 1 final

1.18.18.5 macOS
...............

   - bpo-38295(1): Prevent failure of test_relative_path in
     test_py_compile on macOS Catalina.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38295


File: python.info,  Node: IDLE<16>,  Prev: macOS<8>,  Up: Python 3 8 1 final

1.18.18.6 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38944

   (2) https://bugs.python.org/issue38943


File: python.info,  Node: Python 3 8 1 release candidate 1,  Next: Python 3 8 0 final,  Prev: Python 3 8 1 final,  Up: Changelog（更動日誌）

1.18.19 Python 3.8.1 release candidate 1
----------------------------------------

`Release date: 2019-12-09'

* Menu:

* Security: Security<12>.
* Core and Builtins: Core and Builtins<18>.
* Library: Library<18>.
* Documentation: Documentation<14>.
* Tests: Tests<10>.
* Build: Build<9>.
* Windows: Windows<11>.
* macOS: macOS<9>.
* IDLE: IDLE<17>.
* C API: C API<7>.


File: python.info,  Node: Security<12>,  Next: Core and Builtins<18>,  Up: Python 3 8 1 release candidate 1

1.18.19.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(): 2e8. 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-38722(4): *note runpy: e3. now uses *note io.open_code(): f27.
     to open code files.  Patch by Jason Killen.

   - bpo-38804(5): Fixes a ReDoS vulnerability in *note http.cookiejar:
     95.  Patch by Ben Caller.

   - bpo-38622(6): Add additional audit events for the *note ctypes: 2b.
     module.

   - bpo-38418(7): Fixes audit event for *note os.system(): dc6. to be
     named ‘os.system’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38945

   (2) https://bugs.python.org/issue37228

   (3) https://bugs.python.org/issue37228

   (4) https://bugs.python.org/issue38722

   (5) https://bugs.python.org/issue38804

   (6) https://bugs.python.org/issue38622

   (7) https://bugs.python.org/issue38418


File: python.info,  Node: Core and Builtins<18>,  Next: Library<18>,  Prev: Security<12>,  Up: Python 3 8 1 release candidate 1

1.18.19.2 Core and Builtins
...........................

   - bpo-38673(1): 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(2): Calling ‘replace’ on a code object now raises the
     ‘code.__new__’ audit event.

   - bpo-38920(3): Add audit hooks for when *note sys.excepthook(): e68.
     and *note sys.unraisablehook(): 22e. are invoked

   - bpo-38892(4): Improve documentation for audit events table and
     functions.

   - bpo-38707(5): ‘MainThread.native_id’ is now correctly reset in
     child processes spawned using *note multiprocessing.Process: 3b7,
     instead of retaining the parent’s value.

   - bpo-38640(6): 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-38535(7): Fixed line numbers and column offsets for AST nodes
     for calls without arguments in decorators.

   - bpo-38525(8): Fix a segmentation fault when using reverse iterators
     of empty ‘dict’ objects.  Patch by Dong-hee Na and Inada Naoki.

   - bpo-35409(9): Ignore GeneratorExit exceptions when throwing an
     exception into the aclose coroutine of an asynchronous generator.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38673

   (2) https://bugs.python.org/issue38922

   (3) https://bugs.python.org/issue38920

   (4) https://bugs.python.org/issue38892

   (5) https://bugs.python.org/issue38707

   (6) https://bugs.python.org/issue38640

   (7) https://bugs.python.org/issue38535

   (8) https://bugs.python.org/issue38525

   (9) https://bugs.python.org/issue35409


File: python.info,  Node: Library<18>,  Next: Documentation<14>,  Prev: Core and Builtins<18>,  Up: Python 3 8 1 release candidate 1

1.18.19.3 Library
.................

   - bpo-39006(1): Fix asyncio when the ssl module is missing: only
     check for ssl.SSLSocket instance if the ssl module is available.

   - bpo-38708(2): Fix a potential IndexError in email parser when
     parsing an empty msg-id.

   - bpo-38698(3): 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-38979(4): Return class from ‘ContextVar.__class_getitem__’ to
     simplify subclassing.

   - bpo-38986(5): Make repr of C accelerated TaskWakeupMethWrapper the
     same as of pure Python version.

   - bpo-38529(6): Drop too noisy asyncio warning about deletion of a
     stream without explicit ‘.close()’ call.

   - bpo-38634(7): The *note readline: df. module now detects if Python
     is linked to libedit at runtime on all platforms.  Previously, the
     check was only done on macOS.

   - bpo-33684(8): Fix ‘json.tool’ failed to read a JSON file with
     non-ASCII characters when locale encoding is not UTF-8.

   - bpo-38698(9): 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 *note UnboundLocalError: e7b.
     on parsing an invalid value.  Patch by Claudiu Popa.

   - bpo-26730(10): Fix ‘SpooledTemporaryFile.rollover()’ might corrupt
     the file when it is in text mode.  Patch by Serhiy Storchaka.

   - bpo-38668(11): Calling func:*note shutil.copytree: 21b. 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-37838(12): *note typing.get_type_hints(): 30f. properly handles
     functions decorated with *note functools.wraps(): 86f.

   - bpo-38859(13): AsyncMock now returns StopAsyncIteration on the
     exaustion of a side_effects iterable.  Since PEP-479 its Impossible
     to raise a StopIteration exception from a coroutine.

   - bpo-38857(14): AsyncMock fix for return values that are awaitable
     types.  This also covers side_effect iterable values that happend
     to be awaitable, and wraps callables that return an awaitable type.
     Before these awaitables were being awaited instead of being
     returned as is.

   - bpo-38821(15): Fix unhandled exceptions in *note argparse: 6. when
     internationalizing error messages for arguments with ‘nargs’ set to
     special (non-integer) values.  Patch by Federico Bond.

   - bpo-38820(16): Make Python compatible with OpenSSL 3.0.0.  *note
     ssl.SSLSocket.getpeercert(): 8d6. no longer returns IPv6 addresses
     with a trailing new line.

   - bpo-38807(17): Update *note TypeError: 193. messages for *note
     os.path.join(): f61. to include *note os.PathLike: 4f0. objects as
     acceptable input types.

   - bpo-38785(18): Prevent asyncio from crashing if parent ‘__init__’
     is not called from a constructor of object derived from
     ‘asyncio.Future’.

   - bpo-38723(19): *note pdb: ca. now uses *note io.open_code(): f27.
     to trigger auditing events.

   - bpo-27805(20): Allow opening pipes and other non-seekable files in
     append mode with *note open(): 4f5.

   - bpo-38686(21): Added support for multiple ‘qop’ values in *note
     urllib.request.AbstractDigestAuthHandler: f2c.

   - bpo-38334(22): Fixed seeking backward on an encrypted
     ‘zipfile.ZipExtFile’.

   - bpo-34679(23): asynci.ProactorEventLoop.close() now only calls
     signal.set_wakeup_fd() in the main thread.

   - bpo-31202(24): The case the result of ‘pathlib.WindowsPath.glob()’
     matches now the case of the pattern for literal parts.

   - bpo-38521(25): Fixed erroneous equality comparison in
     statistics.NormalDist().

   - bpo-38478(26): 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(27): Fixed *note hmac.new: 859. 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-38422(28): Clarify docstrings of pathlib suffix(es)

   - bpo-36993(29): Improve error reporting for corrupt zip files with
     bad zip64 extra data.  Patch by Daniel Hillier.

   - bpo-36820(30): 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-34776(31): Fix dataclasses to support forward references in
     type annotations

   - bpo-33348(32): lib2to3 now recognizes expressions after ‘*’ and
     ‘**’ like in ‘f(*[] or [])’.

   - bpo-27657(33): 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").

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue39006

   (2) https://bugs.python.org/issue38708

   (3) https://bugs.python.org/issue38698

   (4) https://bugs.python.org/issue38979

   (5) https://bugs.python.org/issue38986

   (6) https://bugs.python.org/issue38529

   (7) https://bugs.python.org/issue38634

   (8) https://bugs.python.org/issue33684

   (9) https://bugs.python.org/issue38698

   (10) https://bugs.python.org/issue26730

   (11) https://bugs.python.org/issue38668

   (12) https://bugs.python.org/issue37838

   (13) https://bugs.python.org/issue38859

   (14) https://bugs.python.org/issue38857

   (15) https://bugs.python.org/issue38821

   (16) https://bugs.python.org/issue38820

   (17) https://bugs.python.org/issue38807

   (18) https://bugs.python.org/issue38785

   (19) https://bugs.python.org/issue38723

   (20) https://bugs.python.org/issue27805

   (21) https://bugs.python.org/issue38686

   (22) https://bugs.python.org/issue38334

   (23) https://bugs.python.org/issue34679

   (24) https://bugs.python.org/issue31202

   (25) https://bugs.python.org/issue38521

   (26) https://bugs.python.org/issue38478

   (27) https://bugs.python.org/issue33604

   (28) https://bugs.python.org/issue38422

   (29) https://bugs.python.org/issue36993

   (30) https://bugs.python.org/issue36820

   (31) https://bugs.python.org/issue34776

   (32) https://bugs.python.org/issue33348

   (33) https://bugs.python.org/issue27657


File: python.info,  Node: Documentation<14>,  Next: Tests<10>,  Prev: Library<18>,  Up: Python 3 8 1 release candidate 1

1.18.19.4 Documentation
.......................

   - bpo-38816(1): 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(2): Modernize *note email: 69. examples from %-formatting
     to f-strings.

   - bpo-38778(3): Document the fact that *note RuntimeError: 2bb. is
     raised if *note os.fork(): 966. is called in a subinterpreter.

   - bpo-38592(4): Add Brazilian Portuguese to the language switcher at
     Python Documentation website.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38816

   (2) https://bugs.python.org/issue38351

   (3) https://bugs.python.org/issue38778

   (4) https://bugs.python.org/issue38592


File: python.info,  Node: Tests<10>,  Next: Build<9>,  Prev: Documentation<14>,  Up: Python 3 8 1 release candidate 1

1.18.19.5 Tests
...............

   - bpo-38547(1): 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(2): Fix a test for *note math.fsum(): d43. that was
     failing due to constant folding.

   - bpo-38965(3): 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(4): test_capi: trashcan tests now require the test "cpu"
     resource.

   - bpo-38841(5): Skip asyncio
     test_create_datagram_endpoint_existing_sock_unix on platforms
     lacking a functional bind() for named unix domain sockets.

   - bpo-38669(6): Raise *note TypeError: 193. when passing target as a
     string with *note unittest.mock.patch.object(): f64.

   - bpo-35998(7): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38547

   (2) https://bugs.python.org/issue38992

   (3) https://bugs.python.org/issue38965

   (4) https://bugs.python.org/issue38875

   (5) https://bugs.python.org/issue38841

   (6) https://bugs.python.org/issue38669

   (7) https://bugs.python.org/issue35998


File: python.info,  Node: Build<9>,  Next: Windows<11>,  Prev: Tests<10>,  Up: Python 3 8 1 release candidate 1

1.18.19.6 Build
...............

   - bpo-37404(1): *note asyncio: a. now raises ‘TyperError’ when
     calling incompatible methods with an *note ssl.SSLSocket: 3e7.
     socket.  Patch by Ido Michael.

   - bpo-38809(2): On Windows, build scripts will now recognize and use
     python.exe from an active virtual env.

   - bpo-38684(3): Fix _hashlib build when Blake2 is disabled, but
     OpenSSL supports it.

   - bpo-37415(4): Fix stdatomic.h header check for ICC compiler: the
     ICC implementation lacks atomic_uintptr_t type which is needed by
     Python.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37404

   (2) https://bugs.python.org/issue38809

   (3) https://bugs.python.org/issue38684

   (4) https://bugs.python.org/issue37415


File: python.info,  Node: Windows<11>,  Next: macOS<9>,  Prev: Build<9>,  Up: Python 3 8 1 release candidate 1

1.18.19.7 Windows
.................

   - bpo-33125(1): Add support for building and releasing Windows ARM64
     packages.

   - bpo-38589(2): Fixes HTML Help shortcut when Windows is not
     installed to C drive

   - bpo-38453(3): Ensure ntpath.realpath() correctly resolves relative
     paths.

   - bpo-38519(4): Restores the internal C headers that were missing
     from the nuget.org and Microsoft Store packages.

   - bpo-38492(5): Remove ‘pythonw.exe’ dependency on the Microsoft C++
     runtime.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33125

   (2) https://bugs.python.org/issue38589

   (3) https://bugs.python.org/issue38453

   (4) https://bugs.python.org/issue38519

   (5) https://bugs.python.org/issue38492


File: python.info,  Node: macOS<9>,  Next: IDLE<17>,  Prev: Windows<11>,  Up: Python 3 8 1 release candidate 1

1.18.19.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/issue37931


File: python.info,  Node: IDLE<17>,  Next: C API<7>,  Prev: macOS<9>,  Up: Python 3 8 1 release candidate 1

1.18.19.9 IDLE
..............

   - bpo-38862(1): ’Strip Trailing Whitespace’ on the Format menu
     removes extra newlines at the end of non-shell files.

   - bpo-26353(2): Stop adding newline when saving an IDLE shell window.

   - bpo-38636(3): 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.

   - bpo-4630(4): 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(5): Do not try to compile IDLE shell or output windows

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38862

   (2) https://bugs.python.org/issue26353

   (3) https://bugs.python.org/issue38636

   (4) https://bugs.python.org/issue4630

   (5) https://bugs.python.org/issue38598


File: python.info,  Node: C API<7>,  Prev: IDLE<17>,  Up: Python 3 8 1 release candidate 1

1.18.19.10 C API
................

   - bpo-37633(1): Re-export some function compatibility wrappers for
     macros in ‘pythonrun.h’.

   - bpo-38540(2): Fixed possible leak in *note PyArg_Parse(): f6a. and
     similar functions for format units ‘"es#"’ and ‘"et#"’ when the
     macro ‘PY_SSIZE_T_CLEAN’ is not defined.

   - bpo-36389(3): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37633

   (2) https://bugs.python.org/issue38540

   (3) https://bugs.python.org/issue36389


File: python.info,  Node: Python 3 8 0 final,  Next: Python 3 8 0 release candidate 1,  Prev: Python 3 8 1 release candidate 1,  Up: Changelog（更動日誌）

1.18.20 Python 3.8.0 final
--------------------------

`Release date: 2019-10-14'

* Menu:

* Core and Builtins: Core and Builtins<19>.
* Library: Library<19>.
* Documentation: Documentation<15>.
* Tests: Tests<11>.
* Windows: Windows<12>.
* IDLE: IDLE<18>.
* Tools/Demos: Tools/Demos<5>.
* C API: C API<8>.


File: python.info,  Node: Core and Builtins<19>,  Next: Library<19>,  Up: Python 3 8 0 final

1.18.20.1 Core and Builtins
...........................

   - bpo-38469(1): 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-38379(2): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38469

   (2) https://bugs.python.org/issue38379


File: python.info,  Node: Library<19>,  Next: Documentation<15>,  Prev: Core and Builtins<19>,  Up: Python 3 8 0 final

1.18.20.2 Library
.................

   - bpo-38449(1): Revert GH-15522, which introduces a regression in
     *note mimetypes.guess_type(): f6e. due to improper handling of
     filenames as urls.

   - bpo-38431(2): Fix ‘__repr__’ method for ‘dataclasses.InitVar’ to
     support typing objects, patch by Samuel Colvin.

   - bpo-38109(3): Add missing *note stat.S_IFDOOR: 8d9, *note
     stat.S_IFPORT: 8da, *note stat.S_IFWHT: 8db, *note stat.S_ISDOOR():
     f6f, *note stat.S_ISPORT(): f70, and *note stat.S_ISWHT(): f71.
     values to the Python implementation of *note stat: f5.

   - bpo-38405(4): Nested subclasses of *note typing.NamedTuple: 281.
     are now pickleable.

   - bpo-38332(5): Prevent *note KeyError: 2c8. 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-38341(6): Add *note smtplib.SMTPNotSupportedError: f72. to the
     *note smtplib: ee. exported names.

   - bpo-13153(7): 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).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38449

   (2) https://bugs.python.org/issue38431

   (3) https://bugs.python.org/issue38109

   (4) https://bugs.python.org/issue38405

   (5) https://bugs.python.org/issue38332

   (6) https://bugs.python.org/issue38341

   (7) https://bugs.python.org/issue13153


File: python.info,  Node: Documentation<15>,  Next: Tests<11>,  Prev: Library<19>,  Up: Python 3 8 0 final

1.18.20.3 Documentation
.......................

   - bpo-38294(1): Add list of no-longer-escaped chars to re.escape
     documentation.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38294


File: python.info,  Node: Tests<11>,  Next: Windows<12>,  Prev: Documentation<15>,  Up: Python 3 8 0 final

1.18.20.4 Tests
...............

   - bpo-37531(1): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37531


File: python.info,  Node: Windows<12>,  Next: IDLE<18>,  Prev: Tests<11>,  Up: Python 3 8 0 final

1.18.20.5 Windows
.................

   - bpo-38344(1): Fix error message in activate.bat.

   - bpo-38359(2): Ensures ‘pyw.exe’ launcher reads correct registry
     key.

   - bpo-38355(3): Fixes ‘ntpath.realpath’ failing on ‘sys.executable’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38344

   (2) https://bugs.python.org/issue38359

   (3) https://bugs.python.org/issue38355


File: python.info,  Node: IDLE<18>,  Next: Tools/Demos<5>,  Prev: Windows<12>,  Up: Python 3 8 0 final

1.18.20.6 IDLE
..............

   - bpo-36698(1): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36698


File: python.info,  Node: Tools/Demos<5>,  Next: C API<8>,  Prev: IDLE<18>,  Up: Python 3 8 0 final

1.18.20.7 Tools/Demos
.....................

   - bpo-38118(1): Update Valgrind suppression file to ignore a false
     alarm in *note PyUnicode_Decode(): f78. when using GCC builtin
     strcmp().

   - bpo-38347(2): pathfix.py: Assume all files that end on ’.py’ are
     Python scripts when working recursively.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38118

   (2) https://bugs.python.org/issue38347


File: python.info,  Node: C API<8>,  Prev: Tools/Demos<5>,  Up: Python 3 8 0 final

1.18.20.8 C API
...............

   - bpo-38395(1): Fix a crash in *note weakref.proxy: 251. 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38395


File: python.info,  Node: Python 3 8 0 release candidate 1,  Next: Python 3 8 0 beta 4,  Prev: Python 3 8 0 final,  Up: Changelog（更動日誌）

1.18.21 Python 3.8.0 release candidate 1
----------------------------------------

`Release date: 2019-10-01'

* Menu:

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


File: python.info,  Node: Security<13>,  Next: Core and Builtins<20>,  Up: Python 3 8 0 release candidate 1

1.18.21.1 Security
..................

   - bpo-38243(1): Escape the server title of *note
     xmlrpc.server.DocXMLRPCServer: f7c. when rendering the document
     page as HTML. (Contributed by Dong-hee Na in bpo-38243(2).)

   - bpo-38174(3): Update vendorized expat library version to 2.2.8,
     which resolves CVE-2019-15903.

   - bpo-37764(4): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38243

   (2) https://bugs.python.org/issue38243

   (3) https://bugs.python.org/issue38174

   (4) https://bugs.python.org/issue37764


File: python.info,  Node: Core and Builtins<20>,  Next: Library<20>,  Prev: Security<13>,  Up: Python 3 8 0 release candidate 1

1.18.21.2 Core and Builtins
...........................

   - bpo-38006(1): 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(2): Fix warnings options priority: ‘PyConfig.warnoptions’
     has the highest priority, as stated in the PEP 587(3).

   - bpo-36871(4): 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-38236(5): Python now dumps path configuration if it fails to
     import the Python codecs of the filesystem and stdio encodings.

   - bpo-38013(6): 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(): 1a6. call.

   - bpo-38124(7): Fix an off-by-one error in PyState_AddModule that
     could cause out-of-bounds memory access.

   - bpo-38005(8): Fixed comparing and creating of InterpreterID and
     ChannelID.

   - bpo-37994(9): Fixed silencing arbitrary errors if an attribute
     lookup fails in several sites.  Only AttributeError should be
     silenced.

   - bpo-37990(10): Fix elapsed time in gc stats was not printed
     correctly.  This bug was a regression in 3.8b4.

   - bpo-37966(11): The implementation of *note is_normalized(): 247.
     has been greatly sped up on strings that aren’t normalized, by
     implementing the full normalization-quick-check algorithm from the
     Unicode standard.

   - bpo-20490(12): Improve import error message for partially
     initialized module on circular ‘from’ imports - by Anthony Sottile.

   - bpo-37409(13): 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-37619(14): 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-30773(15): 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/issue38006

   (2) https://bugs.python.org/issue38317

   (3) https://www.python.org/dev/peps/pep-0587

   (4) https://bugs.python.org/issue36871

   (5) https://bugs.python.org/issue38236

   (6) https://bugs.python.org/issue38013

   (7) https://bugs.python.org/issue38124

   (8) https://bugs.python.org/issue38005

   (9) https://bugs.python.org/issue37994

   (10) https://bugs.python.org/issue37990

   (11) https://bugs.python.org/issue37966

   (12) https://bugs.python.org/issue20490

   (13) https://bugs.python.org/issue37409

   (14) https://bugs.python.org/issue37619

   (15) https://bugs.python.org/issue30773


File: python.info,  Node: Library<20>,  Next: Documentation<16>,  Prev: Core and Builtins<20>,  Up: Python 3 8 0 release candidate 1

1.18.21.3 Library
.................

   - bpo-38319(1): sendfile() used in socket and shutil modules was
     raising OverflowError for files >= 2GiB on 32-bit architectures.
     (patch by Giampaolo Rodola)

   - bpo-38242(2): Revert the new asyncio Streams API

   - bpo-38019(3): Correctly handle pause/resume reading of closed
     asyncio unix pipe.

   - bpo-38163(4): 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(5): Removes _AwaitEvent from AsyncMock.

   - bpo-38216(6): Allow the rare code that wants to send invalid http
     requests from the *note http.client: 94. library a way to do so.
     The fixes for bpo-30458(7) led to breakage for some projects that
     were relying on this ability to test their own behavior in the face
     of bad requests.

   - bpo-38108(8): Any synchronous magic methods on an AsyncMock now
     return a MagicMock.  Any asynchronous magic methods on a MagicMock
     now return an AsyncMock.

   - bpo-38248(9): asyncio: Fix inconsistent immediate Task cancellation

   - bpo-38237(10): The arguments for the builtin pow function are more
     descriptive.  They can now also be passed in as keywords.

   - bpo-38191(11): Constructors of *note NamedTuple: 281. and *note
     TypedDict: 23c. types now accept arbitrary keyword argument names,
     including "cls", "self", "typename", "_typename", "fields" and
     "_fields".  Passing positional arguments by keyword is deprecated.

   - bpo-38185(12): Fixed case-insensitive string comparison in *note
     sqlite3.Row: 763. indexing.

   - bpo-38136(13): 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(14): Fix default mock name in *note
     unittest.mock.Mock.assert_called(): 5ad. exceptions.  Patch by
     Abraham Toriz Cruz.

   - bpo-38175(15): Fix a memory leak in comparison of *note
     sqlite3.Row: 763. objects.

   - bpo-33936(16): _hashlib no longer calls obsolete OpenSSL
     initialization function with OpenSSL 1.1.0+.

   - bpo-34706(17): Preserve subclassing in
     inspect.Signature.from_callable.

   - bpo-38153(18): Names of hashing algorithms frome 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(19): 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(20): Add slots to *note asyncio: a. transport classes,
     which can reduce memory usage.

   - bpo-36991(21): Fixes a potential incorrect AttributeError exception
     escaping ZipFile.extract() in some unsupported input error
     situations.

   - bpo-38134(22): Remove obsolete copy of PBKDF2_HMAC_fast.  All
     supported OpenSSL versions contain a fast implementation.

   - bpo-38132(23): 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(24): 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: 1f. module

   - bpo-37405(25): 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(26): Update parameter names on functions in
     importlib.metadata matching the changes in the 0.22 release of
     importlib_metadata.

   - bpo-38110(27): The os.closewalk() implementation now uses the libc
     fdwalk() API on platforms where it is available.

   - bpo-38093(28): Fixes AsyncMock so it doesn’t crash when used with
     AsyncContextManagers or AsyncIterators.

   - bpo-37488(29): Add warning to ‘datetime.utctimetuple()’,
     ‘datetime.utcnow()’ and ‘datetime.utcfromtimestamp()’ .

   - bpo-38086(30): Update importlib.metadata with changes from
     importlib_metadata 0.21(31).

   - bpo-37251(32): 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(33): Fix reference counters in the *note signal: eb.
     module.

   - bpo-38066(34): Hide internal asyncio.Stream methods: feed_eof(),
     feed_data(), set_exception() and set_transport().

   - bpo-38059(35): inspect.py now uses sys.exit() instead of exit()

   - bpo-37953(36): In *note typing: 11a, improved the ‘__hash__’ and
     ‘__eq__’ methods for ‘ForwardReferences’.

   - bpo-38026(37): Fixed *note inspect.getattr_static(): bd0. used
     ‘isinstance’ while it should avoid dynamic lookup.

   - bpo-38010(38): 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(39): 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-34410(40): Fixed a crash in the ‘tee()’ iterator when re-enter
     it.  RuntimeError is now raised in this case.

   - bpo-37140(41): 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-37972(42): Subscripts to the *note unittest.mock.call: f7f.
     objects now receive the same chaining mechanism as any other custom
     attributes, so that the following usage no longer raises a *note
     TypeError: 193.:

     call().foo().__getitem__(’bar’)

     Patch by blhsing

   - bpo-22347(43): Update mimetypes.guess_type to allow proper parsing
     of URLs with only a host name.  Patch by Dong-hee Na.

   - bpo-37885(44): venv: Don’t generate unset variable warning on
     deactivate.

   - bpo-37785(45): Fix xgettext warnings in *note argparse: 6.

   - bpo-11953(46): Completing WSA* error codes in *note socket: f0.

   - bpo-37424(47): Fixes a possible hang when using a timeout on *note
     subprocess.run(): 3f2. 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-37212(48): *note unittest.mock.call(): f7f. now preserves the
     order of keyword arguments in repr output.  Patch by Karthikeyan
     Singaravelan.

   - bpo-37305(49): Add .webmanifest -> application/manifest+json to
     list of recognized file types and content type headers

   - bpo-21872(50): Fix *note lzma: ae.: 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-37206(51): Default values which cannot be represented as Python
     objects no longer improperly represented as ‘None’ in function
     signatures.

   - bpo-12144(52): Ensure cookies with ‘expires’ attribute are handled
     in ‘CookieJar.make_cookies()’.

   - bpo-31163(53): pathlib.Path instance’s rename and replace methods
     now return the new Path instance.

   - bpo-25068(54): *note urllib.request.ProxyHandler: f80. now
     lowercases the keys of the passed dictionary.

   - bpo-21315(55): 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-36250(56): Ignore ‘ValueError’ from ‘signal’ with ‘interaction’
     in non-main thread.

   - bpo-35168(57): *note shlex.shlex.punctuation_chars: f81. is now a
     read-only property.

   - bpo-20504(58): Fixes a bug in *note cgi: 16. module when a
     multipart/form-data request has no ‘Content-Length’ header.

   - bpo-34519(59): Add additional aliases for HP Roman 8.  Patch by
     Michael Osipov.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38319

   (2) https://bugs.python.org/issue38242

   (3) https://bugs.python.org/issue38019

   (4) https://bugs.python.org/issue38163

   (5) https://bugs.python.org/issue38161

   (6) https://bugs.python.org/issue38216

   (7) https://bugs.python.org/issue30458

   (8) https://bugs.python.org/issue38108

   (9) https://bugs.python.org/issue38248

   (10) https://bugs.python.org/issue38237

   (11) https://bugs.python.org/issue38191

   (12) https://bugs.python.org/issue38185

   (13) https://bugs.python.org/issue38136

   (14) https://bugs.python.org/issue37828

   (15) https://bugs.python.org/issue38175

   (16) https://bugs.python.org/issue33936

   (17) https://bugs.python.org/issue34706

   (18) https://bugs.python.org/issue38153

   (19) https://bugs.python.org/issue38115

   (20) https://bugs.python.org/issue38148

   (21) https://bugs.python.org/issue36991

   (22) https://bugs.python.org/issue38134

   (23) https://bugs.python.org/issue38132

   (24) https://bugs.python.org/issue38008

   (25) https://bugs.python.org/issue37405

   (26) https://bugs.python.org/issue38121

   (27) https://bugs.python.org/issue38110

   (28) https://bugs.python.org/issue38093

   (29) https://bugs.python.org/issue37488

   (30) https://bugs.python.org/issue38086

   (31) 
https://gitlab.com/python-devs/importlib_metadata/blob/0.21/importlib_metadata/docs/changelog.rst

   (32) https://bugs.python.org/issue37251

   (33) https://bugs.python.org/issue38037

   (34) https://bugs.python.org/issue38066

   (35) https://bugs.python.org/issue38059

   (36) https://bugs.python.org/issue37953

   (37) https://bugs.python.org/issue38026

   (38) https://bugs.python.org/issue38010

   (39) https://bugs.python.org/issue38006

   (40) https://bugs.python.org/issue34410

   (41) https://bugs.python.org/issue37140

   (42) https://bugs.python.org/issue37972

   (43) https://bugs.python.org/issue22347

   (44) https://bugs.python.org/issue37885

   (45) https://bugs.python.org/issue37785

   (46) https://bugs.python.org/issue11953

   (47) https://bugs.python.org/issue37424

   (48) https://bugs.python.org/issue37212

   (49) https://bugs.python.org/issue37305

   (50) https://bugs.python.org/issue21872

   (51) https://bugs.python.org/issue37206

   (52) https://bugs.python.org/issue12144

   (53) https://bugs.python.org/issue31163

   (54) https://bugs.python.org/issue25068

   (55) https://bugs.python.org/issue21315

   (56) https://bugs.python.org/issue36250

   (57) https://bugs.python.org/issue35168

   (58) https://bugs.python.org/issue20504

   (59) https://bugs.python.org/issue34519


File: python.info,  Node: Documentation<16>,  Next: Tests<12>,  Prev: Library<20>,  Up: Python 3 8 0 release candidate 1

1.18.21.4 Documentation
.......................

   - bpo-26868(1): Fix example usage of *note PyModule_AddObject(): f83.
     to properly handle errors.

   - bpo-36797(2): Fix a dead link in the distutils API Reference.

   - bpo-37977(3): Warn more strongly and clearly about pickle
     insecurity

   - bpo-37937(4): Mention ‘frame.f_trace’ in *note sys.settrace(): e43.
     docs.

   - bpo-36260(5): Add decompression pitfalls to zipfile module
     documentation.

   - bpo-36960(6): Restructured the *note datetime: 31. docs in the
     interest of making them more user-friendly and improving
     readability.  Patch by Brad Solomon.

   - bpo-23460(7): 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(8): Document and test that ‘tempfile’ functions may
     accept a *note path-like object: 36f. for the ‘dir’ argument.
     Patch by Anthony Sottile.

   - bpo-33944(9): Added a note about the intended use of code in .pth
     files.

   - bpo-34293(10): Fix the Doc/Makefile regarding PAPER environment
     variable and PDF builds

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26868

   (2) https://bugs.python.org/issue36797

   (3) https://bugs.python.org/issue37977

   (4) https://bugs.python.org/issue37937

   (5) https://bugs.python.org/issue36260

   (6) https://bugs.python.org/issue36960

   (7) https://bugs.python.org/issue23460

   (8) https://bugs.python.org/issue35803

   (9) https://bugs.python.org/issue33944

   (10) https://bugs.python.org/issue34293


File: python.info,  Node: Tests<12>,  Next: Build<10>,  Prev: Documentation<16>,  Up: Python 3 8 0 release candidate 1

1.18.21.5 Tests
...............

   - bpo-38239(1): Fix test_gdb for Link Time Optimization (LTO) builds.

   - bpo-38275(2): 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(3): 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(4): test.support now has a helper function to check for
     availibility 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(5): 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(6): Multiprocessing tests: increase
     test_queue_feeder_donot_stop_onexc() timeout from 1 to 60 seconds.

   - bpo-38117(7): Test with OpenSSL 1.1.1d

   - bpo-37531(8): 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(9): Add tests for ROT-13 codec.

   - bpo-37252(10): Fix assertions in ‘test_close’ and
     ‘test_events_mask_overflow’ devpoll tests.

   - bpo-34001(11): Make test_ssl pass with LibreSSL. LibreSSL handles
     minimum and maximum TLS version differently than OpenSSL.

   - bpo-36919(12): Make ‘test_source_encoding.test_issue2301’
     implementation independent.  The test will work now for both
     CPython and IronPython.

   - bpo-34596(13): Fallback to a default reason when *note
     unittest.skip(): f85. is uncalled.  Patch by Naitree Zhu.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38239

   (2) https://bugs.python.org/issue38275

   (3) https://bugs.python.org/issue38271

   (4) https://bugs.python.org/issue38270

   (5) https://bugs.python.org/issue37123

   (6) https://bugs.python.org/issue38212

   (7) https://bugs.python.org/issue38117

   (8) https://bugs.python.org/issue37531

   (9) https://bugs.python.org/issue37876

   (10) https://bugs.python.org/issue37252

   (11) https://bugs.python.org/issue34001

   (12) https://bugs.python.org/issue36919

   (13) https://bugs.python.org/issue34596


File: python.info,  Node: Build<10>,  Next: Windows<13>,  Prev: Tests<12>,  Up: Python 3 8 0 release candidate 1

1.18.21.6 Build
...............

   - bpo-38301(1): In Solaris family, we must be sure to use
     ‘-D_REENTRANT’.  Patch by Jesús Cea Avión.

   - bpo-36210(2): 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

   - bpo-36002(3): Locate ‘llvm-profdata’ and ‘llvm-ar’ binaries using
     ‘AC_PATH_TOOL’ rather than ‘AC_PATH_TARGET_TOOL’.

   - bpo-37936(4): 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-37936(5): The ‘.gitignore’ file no longer applies to any files
     that are in fact tracked in the Git repository.  Patch by Greg
     Price.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38301

   (2) https://bugs.python.org/issue36210

   (3) https://bugs.python.org/issue36002

   (4) https://bugs.python.org/issue37936

   (5) https://bugs.python.org/issue37936


File: python.info,  Node: Windows<13>,  Next: macOS<10>,  Prev: Build<10>,  Up: Python 3 8 0 release candidate 1

1.18.21.7 Windows
.................

   - bpo-38117(1): Update bundled OpenSSL to 1.1.1d

   - bpo-38092(2): Reduce overhead when using multiprocessing in a
     Windows virtual environment.

   - bpo-38133(3): Allow py.exe launcher to locate installations from
     the Microsoft Store and improve display of active virtual
     environments.

   - bpo-38114(4): The ‘pip.ini’ is no longer included in the Nuget
     package.

   - bpo-36634(5): *note os.cpu_count(): 884. now returns active
     processors rather than maximum processors.

   - bpo-36634(6): venv activate.bat now works when the existing
     variables contain double quote characters.

   - bpo-38081(7): Prevent error calling *note os.path.realpath(): 200.
     on ‘'NUL'’.

   - bpo-38087(8): Fix case sensitivity in test_pathlib and test_ntpath.

   - bpo-38088(9): Fixes distutils not finding vcruntime140.dll with
     only the v142 toolset installed.

   - bpo-37283(10): Ensure command-line and unattend.xml setting
     override previously detected states in Windows installer.

   - bpo-38030(11): Fixes *note os.stat(): 1f2. failing for block
     devices on Windows

   - bpo-38020(12): Fixes potential crash when calling *note
     os.readlink(): 1f4. (or indirectly through *note realpath(): 200.)
     on a file that is not a supported link.

   - bpo-37705(13): Improve the implementation of ‘winerror_to_errno()’.

   - bpo-37702(14): Fix memory leak on Windows in creating an SSLContext
     object or running urllib.request.urlopen(’‘https://’...’).

   - bpo-37445(15): Include the ‘FORMAT_MESSAGE_IGNORE_INSERTS’ flag in
     ‘FormatMessageW()’ calls.

   - bpo-37380(16): Don’t collect unfinished processes with
     ‘subprocess._active’ on Windows to cleanup later.  Patch by Ruslan
     Kuprieiev.

   - bpo-32587(17): Make *note winreg.REG_MULTI_SZ: f88. support
     zero-length strings.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38117

   (2) https://bugs.python.org/issue38092

   (3) https://bugs.python.org/issue38133

   (4) https://bugs.python.org/issue38114

   (5) https://bugs.python.org/issue36634

   (6) https://bugs.python.org/issue36634

   (7) https://bugs.python.org/issue38081

   (8) https://bugs.python.org/issue38087

   (9) https://bugs.python.org/issue38088

   (10) https://bugs.python.org/issue37283

   (11) https://bugs.python.org/issue38030

   (12) https://bugs.python.org/issue38020

   (13) https://bugs.python.org/issue37705

   (14) https://bugs.python.org/issue37702

   (15) https://bugs.python.org/issue37445

   (16) https://bugs.python.org/issue37380

   (17) https://bugs.python.org/issue32587


File: python.info,  Node: macOS<10>,  Next: IDLE<19>,  Prev: Windows<13>,  Up: Python 3 8 0 release candidate 1

1.18.21.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

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38117

   (2) https://bugs.python.org/issue38089


File: python.info,  Node: IDLE<19>,  Next: Tools/Demos<6>,  Prev: macOS<10>,  Up: Python 3 8 0 release candidate 1

1.18.21.9 IDLE
..............

   - bpo-35379(1): 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(2): 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(3): 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(4): 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(5): To avoid occasional spurious test_idle failures on
     slower machines, increase the ‘hover_delay’ in test_tooltip.

   - bpo-37902(6): Add mousewheel scrolling for IDLE module, path, and
     stack browsers.  Patch by George Zhang.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35379

   (2) https://bugs.python.org/issue38183

   (3) https://bugs.python.org/issue38077

   (4) https://bugs.python.org/issue38041

   (5) https://bugs.python.org/issue35771

   (6) https://bugs.python.org/issue37902


File: python.info,  Node: Tools/Demos<6>,  Next: C API<9>,  Prev: IDLE<19>,  Up: Python 3 8 0 release candidate 1

1.18.21.10 Tools/Demos
......................

   - bpo-37803(1): pdb’s ‘--help’ and ‘--version’ long options now work.

   - bpo-37064(2): 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/issue37803

   (2) https://bugs.python.org/issue37064


File: python.info,  Node: C API<9>,  Prev: Tools/Demos<6>,  Up: Python 3 8 0 release candidate 1

1.18.21.11 C API
................

   - bpo-38234(1): *note Py_SetPath(): 274. now sets *note
     sys.executable: 275. to the program full path (*note
     Py_GetProgramFullPath(): 276.) rather than to the program name
     (*note Py_GetProgramName(): 277.).

   - bpo-38234(2): Python ignored arguments passed to *note
     Py_SetPath(): 274, *note Py_SetPythonHome(): f8d. and *note
     Py_SetProgramName(): f8e.: fix Python initialization to use
     specified arguments.

   - bpo-38205(3): The *note Py_UNREACHABLE(): 428. macro now calls
     *note Py_FatalError(): f8f.

   - bpo-37879(4): Fix subtype_dealloc to suppress the type decref when
     the base type is a C heap type

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue38234

   (2) https://bugs.python.org/issue38234

   (3) https://bugs.python.org/issue38205

   (4) https://bugs.python.org/issue37879


File: python.info,  Node: Python 3 8 0 beta 4,  Next: Python 3 8 0 beta 3,  Prev: Python 3 8 0 release candidate 1,  Up: Changelog（更動日誌）

1.18.22 Python 3.8.0 beta 4
---------------------------

`Release date: 2019-08-29'

* Menu:

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


File: python.info,  Node: Security<14>,  Next: Core and Builtins<21>,  Up: Python 3 8 0 beta 4

1.18.22.1 Security
..................

   - bpo-34155(1): 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/issue34155


File: python.info,  Node: Core and Builtins<21>,  Next: Library<21>,  Prev: Security<14>,  Up: Python 3 8 0 beta 4

1.18.22.2 Core and Builtins
...........................

   - bpo-37947(1): Adjust correctly the recursion level in the symtable
     generation for named expressions.  Patch by Pablo Galindo.

   - bpo-37830(2): Fixed compilation of *note break: 2dc. and *note
     continue: 182. in the *note finally: 183. block when the
     corresponding *note try: d77. block contains *note return: 191.
     with a non-constant value.

   - bpo-32912(3): Reverted bpo-32912(4): emitting *note SyntaxWarning:
     192. instead of *note DeprecationWarning: 279. for invalid escape
     sequences in string and bytes literals.

   - bpo-37757(5): PEP 572(6): As described in the PEP, assignment
     expressions now raise *note SyntaxError: 45d. 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-36311(7): Decoding bytes objects larger than 2GiB is faster and
     no longer fails when a multibyte characters spans a chunk boundary.

   - bpo-37433(8): Fix ‘SyntaxError’ indicator printing too many spaces
     for multi-line strings - by Anthony Sottile.

   - bpo-20523(9): ‘pdb.Pdb’ supports ~/.pdbrc in Windows 7.  Patch by
     Tim Hopper and Dan Lidral-Porter.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37947

   (2) https://bugs.python.org/issue37830

   (3) https://bugs.python.org/issue32912

   (4) https://bugs.python.org/issue32912

   (5) https://bugs.python.org/issue37757

   (6) https://www.python.org/dev/peps/pep-0572

   (7) https://bugs.python.org/issue36311

   (8) https://bugs.python.org/issue37433

   (9) https://bugs.python.org/issue20523


File: python.info,  Node: Library<21>,  Next: Documentation<17>,  Prev: Core and Builtins<21>,  Up: Python 3 8 0 beta 4

1.18.22.3 Library
.................

   - bpo-37834(1): Prevent shutil.rmtree exception when built on
     non-Windows system without fd system call support, like older
     versions of macOS.

   - bpo-37965(2): Fix C compiler warning caused by
     distutils.ccompiler.CCompiler.has_function.

   - bpo-37960(3): ‘repr()’ of buffered and text streams now silences
     only expected exceptions when get the value of "name" and "mode"
     attributes.

   - bpo-37951(4): Most features of the subprocess module now work again
     in subinterpreters.  Only `preexec_fn' is restricted in
     subinterpreters.

   - bpo-36205(5): Fix the rusage implementation of time.process_time()
     to correctly report the sum of the system and user CPU time.

   - bpo-37950(6): Fix *note ast.dump(): f94. when call with
     incompletely initialized node.

   - bpo-34679(7): Restores instantiation of Windows IOCP event loops
     from the non-main thread.

   - bpo-36917(8): Add default implementation of the
     ‘ast.NodeVisitor.visit_Constant()’ method which emits a deprecation
     warning and calls corresponding methody ‘visit_Num()’,
     ‘visit_Str()’, etc.

   - bpo-37798(9): Update test_statistics.py to verify that the
     statistics module works well for both C and Python implementations.
     Patch by Dong-hee Na

   - bpo-26589(10): Added a new status code to the http module: 451
     UNAVAILABLE_FOR_LEGAL_REASONS

   - bpo-37915(11): Fix a segmentation fault that appeared when
     comparing instances of ‘datetime.timezone’ and ‘datetime.tzinfo’
     objects.  Patch by Pablo Galindo.

   - bpo-37868(12): 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(13): 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-21131(14): 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(15): Add C fastpath for statistics.NormalDist.inv_cdf()
     Patch by Dong-hee Na

   - bpo-37819(16): Add Fraction.as_integer_ratio() to match the
     corresponding methods in bool, int, float, and decimal.

   - bpo-37810(17): Fix *note difflib: 37. ‘?’ hint in diff output when
     dealing with tabs.  Patch by Anthony Sottile.

   - bpo-37772(18): In ‘zipfile.Path’, when adding implicit dirs, ensure
     that ancestral directories are added and that duplicates are
     excluded.

   - bpo-28292(19): 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(20): 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-37738(21): 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(22): Fix performance regression on regular expression
     parsing with huge character sets.  Patch by Yann Vaginay.

   - bpo-32178(23): Fix IndexError in *note email: 69. package when
     trying to parse invalid address fields starting with ‘:’.

   - bpo-37685(24): Fixed comparisons of *note datetime.timedelta: 196.
     and *note datetime.timezone: a06.

   - bpo-37695(25): Correct *note curses.unget_wch(): 9e5. error
     message.  Patch by Anthony Sottile.

   - bpo-37354(26): Make Activate.ps1 Powershell script static to allow
     for signing it.

   - bpo-37664(27): Update wheels bundled with ensurepip (pip 19.2.3 and
     setuptools 41.2.0)

   - bpo-37642(28): Allowed the pure Python implementation of *note
     datetime.timezone: a06. 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-16970(29): Adding a value error when an invalid value in passed
     to nargs Patch by Robert Leenders

   - bpo-37587(30): Make json.loads faster for long strings.  (Patch by
     Marco Paolini)

   - bpo-18378(31): Recognize "UTF-8" as a valid value for LC_CTYPE in
     locale._parse_localename.

   - bpo-37531(32): "python3 -m test -jN –timeout=TIMEOUT" now kills a
     worker process if it runs longer than `TIMEOUT' seconds.

   - bpo-37482(33): Fix serialization of display name in originator or
     destination address fields with both encoded words and special
     chars.

   - bpo-37372(34): Fix error unpickling datetime.time objects from
     Python 2 with seconds>=24.  Patch by Justin Blanchard.

   - bpo-37085(35): 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-36871(36): Ensure method signature is used instead of
     constructor signature of a class while asserting mock object
     against method calls.  Patch by Karthikeyan Singaravelan.

   - bpo-36582(37): Fix ‘UserString.encode()’ to correctly return
     ‘bytes’ rather than a ‘UserString’ instance.

   - bpo-34775(38): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37834

   (2) https://bugs.python.org/issue37965

   (3) https://bugs.python.org/issue37960

   (4) https://bugs.python.org/issue37951

   (5) https://bugs.python.org/issue36205

   (6) https://bugs.python.org/issue37950

   (7) https://bugs.python.org/issue34679

   (8) https://bugs.python.org/issue36917

   (9) https://bugs.python.org/issue37798

   (10) https://bugs.python.org/issue26589

   (11) https://bugs.python.org/issue37915

   (12) https://bugs.python.org/issue37868

   (13) https://bugs.python.org/issue37811

   (14) https://bugs.python.org/issue21131

   (15) https://bugs.python.org/issue37798

   (16) https://bugs.python.org/issue37819

   (17) https://bugs.python.org/issue37810

   (18) https://bugs.python.org/issue37772

   (19) https://bugs.python.org/issue28292

   (20) https://bugs.python.org/issue18049

   (21) https://bugs.python.org/issue37738

   (22) https://bugs.python.org/issue37723

   (23) https://bugs.python.org/issue32178

   (24) https://bugs.python.org/issue37685

   (25) https://bugs.python.org/issue37695

   (26) https://bugs.python.org/issue37354

   (27) https://bugs.python.org/issue37664

   (28) https://bugs.python.org/issue37642

   (29) https://bugs.python.org/issue16970

   (30) https://bugs.python.org/issue37587

   (31) https://bugs.python.org/issue18378

   (32) https://bugs.python.org/issue37531

   (33) https://bugs.python.org/issue37482

   (34) https://bugs.python.org/issue37372

   (35) https://bugs.python.org/issue37085

   (36) https://bugs.python.org/issue36871

   (37) https://bugs.python.org/issue36582

   (38) https://bugs.python.org/issue34775


File: python.info,  Node: Documentation<17>,  Next: Tests<13>,  Prev: Library<21>,  Up: Python 3 8 0 beta 4

1.18.22.4 Documentation
.......................

   - bpo-37979(1): Added a link to dateutil.parser.isoparse in the
     datetime.fromisoformat documentation.  Patch by Paul Ganssle

   - bpo-37759(2): Beginning edits to Whatsnew 3.8

   - bpo-37726(3): Stop recommending getopt in the tutorial for command
     line argument parsing and promote argparse.

   - bpo-37256(4): Fix wording of arguments for ‘Request’ in *note
     urllib.request: 121.

   - bpo-37004(5): 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-36487(6): Make C-API docs clear about what the "main"
     interpreter is.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37979

   (2) https://bugs.python.org/issue37759

   (3) https://bugs.python.org/issue37726

   (4) https://bugs.python.org/issue37256

   (5) https://bugs.python.org/issue37004

   (6) https://bugs.python.org/issue36487


File: python.info,  Node: Tests<13>,  Next: Build<11>,  Prev: Documentation<17>,  Up: Python 3 8 0 beta 4

1.18.22.5 Tests
...............

   - bpo-37805(1): Add tests for json.dump(..., skipkeys=True).  Patch
     by Dong-hee Na.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37805


File: python.info,  Node: Build<11>,  Next: Windows<14>,  Prev: Tests<13>,  Up: Python 3 8 0 beta 4

1.18.22.6 Build
...............

   - bpo-37707(1): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37707


File: python.info,  Node: Windows<14>,  Next: macOS<11>,  Prev: Build<11>,  Up: Python 3 8 0 beta 4

1.18.22.7 Windows
.................

   - bpo-37549(1): *note os.dup(): f99. no longer fails for standard
     streams on Windows 7.

   - bpo-1311(2): The ‘nul’ file on Windows now returns True from *note
     exists(): 1f7. and a valid result from *note os.stat(): 1f2. with
     ‘S_IFCHR’ set.

   - bpo-9949(3): Enable support for following symlinks in
     ‘os.realpath()’.

   - bpo-37834(4): Treat all name surrogate reparse points on Windows in
     *note os.lstat(): 1f3. and other reparse points as regular files in
     *note os.stat(): 1f2.

   - bpo-36266(5): 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(6): Trying to import the *note crypt: 29. module on
     Windows will result in an *note ImportError: 339. 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(7): Fixes the icons used for file associations to the
     Microsoft Store package.

   - bpo-37734(8): Fix use of registry values to launch Python from
     Microsoft Store app.

   - bpo-28269(9): Replace use of ‘strcasecmp()’ for the system function
     ‘_stricmp()’.  Patch by Minmin Gong.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37549

   (2) https://bugs.python.org/issue1311

   (3) https://bugs.python.org/issue9949

   (4) https://bugs.python.org/issue37834

   (5) https://bugs.python.org/issue36266

   (6) https://bugs.python.org/issue25172

   (7) https://bugs.python.org/issue37778

   (8) https://bugs.python.org/issue37734

   (9) https://bugs.python.org/issue28269


File: python.info,  Node: macOS<11>,  Next: IDLE<20>,  Prev: Windows<14>,  Up: Python 3 8 0 beta 4

1.18.22.8 macOS
...............

   - bpo-18049(1): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue18049


File: python.info,  Node: IDLE<20>,  Next: Tools/Demos<7>,  Prev: macOS<11>,  Up: Python 3 8 0 beta 4

1.18.22.9 IDLE
..............

   - bpo-37824(1): Properly handle user input warnings in IDLE shell.
     Cease turning SyntaxWarnings into SyntaxErrors.

   - bpo-37929(2): IDLE Settings dialog now closes properly when there
     is no shell window.

   - bpo-37849(3): Fixed completions list appearing too high or low when
     shown above the current line.

   - bpo-36419(4): Refactor IDLE autocomplete and improve testing.

   - bpo-37748(5): Reorder the Run menu.  Put the most common choice,
     Run Module, at the top.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37824

   (2) https://bugs.python.org/issue37929

   (3) https://bugs.python.org/issue37849

   (4) https://bugs.python.org/issue36419

   (5) https://bugs.python.org/issue37748


File: python.info,  Node: Tools/Demos<7>,  Next: C API<10>,  Prev: IDLE<20>,  Up: Python 3 8 0 beta 4

1.18.22.10 Tools/Demos
......................

   - bpo-37942(1): Improve ArgumentClinic converter for floats.

   - bpo-37034(2): Argument Clinic now uses the argument name on errors
     with keyword-only argument instead of their position.  Patch
     contributed by Rémi Lapeyre.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37942

   (2) https://bugs.python.org/issue37034


File: python.info,  Node: C API<10>,  Prev: Tools/Demos<7>,  Up: Python 3 8 0 beta 4

1.18.22.11 C API
................

   - bpo-36763(1): Options added by ‘PySys_AddXOption()’ are now handled
     the same way than ‘PyConfig.xoptions’ and command line ‘-X’
     options.

   - bpo-37926(2): Fix a crash in ‘PySys_SetArgvEx(0, NULL, 0)’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36763

   (2) https://bugs.python.org/issue37926


File: python.info,  Node: Python 3 8 0 beta 3,  Next: Python 3 8 0 beta 2,  Prev: Python 3 8 0 beta 4,  Up: Changelog（更動日誌）

1.18.23 Python 3.8.0 beta 3
---------------------------

`Release date: 2019-07-29'

* Menu:

* Security: Security<15>.
* Core and Builtins: Core and Builtins<22>.
* Library: Library<22>.
* Documentation: Documentation<18>.
* Tests: Tests<14>.
* Build: Build<12>.
* Windows: Windows<15>.
* IDLE: IDLE<21>.
* Tools/Demos: Tools/Demos<8>.


File: python.info,  Node: Security<15>,  Next: Core and Builtins<22>,  Up: Python 3 8 0 beta 3

1.18.23.1 Security
..................

   - bpo-37461(1): Fix an infinite loop when parsing specially crafted
     email headers.  Patch by Abhilash Raj.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37461


File: python.info,  Node: Core and Builtins<22>,  Next: Library<22>,  Prev: Security<15>,  Up: Python 3 8 0 beta 3

1.18.23.2 Core and Builtins
...........................

   - bpo-37593(1): Swap the positions of the `posonlyargs' and `args'
     parameters in the constructor of ‘ast.parameters’ nodes.

   - bpo-36974(2): Implemented separate vectorcall functions for every
     calling convention of builtin functions and methods.  This improves
     performance for calls.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37593

   (2) https://bugs.python.org/issue36974


File: python.info,  Node: Library<22>,  Next: Documentation<18>,  Prev: Core and Builtins<22>,  Up: Python 3 8 0 beta 3

1.18.23.3 Library
.................

   - bpo-37697(1): Syncronize ‘importlib.metadata’ with
     importlib_metadata 0.19(2), improving handling of EGG-INFO files
     and fixing a crash when entry point names contained colons.

   - bpo-37691(3): Let math.dist() accept coordinates as sequences (or
     iterables) rather than just tuples.

   - bpo-37664(4): Update wheels bundled with ensurepip (pip 19.2.1 and
     setuptools 41.0.1)

   - bpo-36324(5): Make internal attributes for statistics.NormalDist()
     private.

   - bpo-37491(6): Fix ‘IndexError’ when parsing email headers with
     unexpectedly ending bare-quoted string value.  Patch by Abhilash
     Raj.

   - bpo-37579(7): Return *note NotImplemented: 851. in Python
     implementation of ‘__eq__’ for *note timedelta: 196. and *note
     time: 4f8. when the other object being compared is not of the same
     type to match C implementation.  Patch by Karthikeyan Singaravelan.

   - bpo-21478(8): Record calls to parent when autospecced object is
     attached to a mock using ‘unittest.mock.attach_mock()’.  Patch by
     Karthikeyan Singaravelan.

   - bpo-37502(9): pickle.loads() no longer raises TypeError when the
     buffers argument is set to None

   - bpo-37520(10): Correct behavior for zipfile.Path.parent when the
     path object identifies a subdirectory.

   - bpo-18374(11): Fix the ‘.col_offset’ attribute of nested
     ‘ast.BinOp’ instances which had a too large value in some
     situations.

   - bpo-37421(12): 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(13): The distutils ‘bdist_wininst’ command is deprecated
     in Python 3.8, use ‘bdist_wheel’ (wheel packages) instead.

   - bpo-26967(14): An *note ArgumentParser: 69a. 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-37347(15): *note sqlite3.Connection.create_aggregate(): fa2,
     *note sqlite3.Connection.create_function(): fa3, *note
     sqlite3.Connection.set_authorizer(): fa4, *note
     sqlite3.Connection.set_progress_handler(): fa5. *note
     sqlite3.Connection.set_trace_callback(): a92. 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-36564(16): 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

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37697

   (2) https://gitlab.com/python-devs/importlib_metadata/-/milestones/20

   (3) https://bugs.python.org/issue37691

   (4) https://bugs.python.org/issue37664

   (5) https://bugs.python.org/issue36324

   (6) https://bugs.python.org/issue37491

   (7) https://bugs.python.org/issue37579

   (8) https://bugs.python.org/issue21478

   (9) https://bugs.python.org/issue37502

   (10) https://bugs.python.org/issue37520

   (11) https://bugs.python.org/issue18374

   (12) https://bugs.python.org/issue37421

   (13) https://bugs.python.org/issue37481

   (14) https://bugs.python.org/issue26967

   (15) https://bugs.python.org/issue37347

   (16) https://bugs.python.org/issue36564


File: python.info,  Node: Documentation<18>,  Next: Tests<14>,  Prev: Library<22>,  Up: Python 3 8 0 beta 3

1.18.23.4 Documentation
.......................

   - bpo-32910(1): Remove implementation-specific behaviour of how
     venv’s Deactivate works.

   - bpo-37284(2): Add a brief note to indicate that any new
     ‘sys.implementation’ required attributes must go through the PEP
     process.

   - bpo-30088(3): Documented that *note mailbox.Maildir: cad.
     constructor doesn’t attempt to verify the maildir folder layout
     correctness.  Patch by Sviatoslav Sydorenko.

   - bpo-37521(4): Fix *note importlib: 9b. 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(5): Slash (’/’) is now part of syntax.

   - bpo-37487(6): Fix PyList_GetItem index description to include 0.

   - bpo-37149(7): 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(8): Added possible exceptions to the description of
     os.chdir().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32910

   (2) https://bugs.python.org/issue37284

   (3) https://bugs.python.org/issue30088

   (4) https://bugs.python.org/issue37521

   (5) https://bugs.python.org/issue37456

   (6) https://bugs.python.org/issue37487

   (7) https://bugs.python.org/issue37149

   (8) https://bugs.python.org/issue37478


File: python.info,  Node: Tests<14>,  Next: Build<12>,  Prev: Documentation<18>,  Up: Python 3 8 0 beta 3

1.18.23.5 Tests
...............

   - bpo-37558(1): Fix
     test_shared_memory_cleaned_after_process_termination name handling

   - bpo-37526(2): Add *note test.support.catch_threading_exception():
     fa8.: context manager catching *note threading.Thread: 236.
     exception using *note threading.excepthook(): 232.

   - bpo-37421(3): test_concurrent_futures now explicitly stops the
     ForkServer instance if it’s running.

   - bpo-37421(4): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37558

   (2) https://bugs.python.org/issue37526

   (3) https://bugs.python.org/issue37421

   (4) https://bugs.python.org/issue37421


File: python.info,  Node: Build<12>,  Next: Windows<15>,  Prev: Tests<14>,  Up: Python 3 8 0 beta 3

1.18.23.6 Build
...............

   - bpo-36044(1): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36044


File: python.info,  Node: Windows<15>,  Next: IDLE<21>,  Prev: Build<12>,  Up: Python 3 8 0 beta 3

1.18.23.7 Windows
.................

   - bpo-37672(1): Switch Windows Store package’s pip to use bundled
     ‘pip.ini’ instead of ‘PIP_USER’ variable.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37672


File: python.info,  Node: IDLE<21>,  Next: Tools/Demos<8>,  Prev: Windows<15>,  Up: Python 3 8 0 beta 3

1.18.23.8 IDLE
..............

   - bpo-37692(1): Improve highlight config sample with example shell
     interaction and better labels for shell elements.

   - bpo-37628(2): Settings dialog no longer expands with font size.

   - bpo-37627(3): Initialize the Customize Run dialog with the command
     line arguments most recently entered before.  The user can
     optionally edit before submitting them.

   - bpo-33610(4): Fix code context not showing the correct context when
     first toggled on.

   - bpo-37530(5): 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(6): Cleanup ‘config.py’ by inlining ‘RemoveFile’ and
     simplifying the handling of ‘file’ in ‘CreateConfigHandlers’.

   - bpo-17535(7): 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(8): 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-36390(9): Gather Format menu functions into format.py.  Combine
     paragraph.py, rstrip.py, and format methods from editor.py.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37692

   (2) https://bugs.python.org/issue37628

   (3) https://bugs.python.org/issue37627

   (4) https://bugs.python.org/issue33610

   (5) https://bugs.python.org/issue37530

   (6) https://bugs.python.org/issue27452

   (7) https://bugs.python.org/issue17535

   (8) https://bugs.python.org/issue26806

   (9) https://bugs.python.org/issue36390


File: python.info,  Node: Tools/Demos<8>,  Prev: IDLE<21>,  Up: Python 3 8 0 beta 3

1.18.23.9 Tools/Demos
.....................

   - bpo-37675(1): 2to3 now works when run from a zipped standard
     library.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37675


File: python.info,  Node: Python 3 8 0 beta 2,  Next: Python 3 8 0 beta 1,  Prev: Python 3 8 0 beta 3,  Up: Changelog（更動日誌）

1.18.24 Python 3.8.0 beta 2
---------------------------

`Release date: 2019-07-04'

* Menu:

* Security: Security<16>.
* Core and Builtins: Core and Builtins<23>.
* Library: Library<23>.
* Documentation: Documentation<19>.
* Tests: Tests<15>.
* Build: Build<13>.
* Windows: Windows<16>.
* macOS: macOS<12>.
* IDLE: IDLE<22>.
* C API: C API<11>.


File: python.info,  Node: Security<16>,  Next: Core and Builtins<23>,  Up: Python 3 8 0 beta 2

1.18.24.1 Security
..................

   - bpo-37363(1): Adds audit events for the range of supported run
     commands (see *note Command line and environment: faf.).

   - bpo-37463(2): 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(3): Adds audit events for *note ensurepip: 7a, *note
     ftplib: 84, *note glob: 8a, *note imaplib: 98, *note nntplib: c1,
     *note pdb: ca, *note poplib: d1, *note shutil: ea, *note smtplib:
     ee, *note sqlite3: f3, *note subprocess: fa, *note telnetlib: 103,
     *note tempfile: 104. and *note webbrowser: 12a, as well as *note
     os.listdir(): a46, *note os.scandir(): 260. and *note breakpoint():
     2fe.

   - bpo-37364(4): *note io.open_code(): f27. is now used when reading
     ‘.pth’ files.

   - bpo-34631(5): Updated OpenSSL to 1.1.1c in Windows installer

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37363

   (2) https://bugs.python.org/issue37463

   (3) https://bugs.python.org/issue37363

   (4) https://bugs.python.org/issue37364

   (5) https://bugs.python.org/issue34631


File: python.info,  Node: Core and Builtins<23>,  Next: Library<23>,  Prev: Security<16>,  Up: Python 3 8 0 beta 2

1.18.24.2 Core and Builtins
...........................

   - bpo-37467(1): Fix *note sys.excepthook(): e68. 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-37417(2): ‘bytearray.extend()’ now correctly handles errors
     that arise during iteration.  Patch by Brandt Bucher.

   - bpo-24214(3): Improved support of the surrogatepass error handler
     in the UTF-8 and UTF-16 incremental decoders.

   - bpo-35224(4): 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(5): Fix the *note PySys_Audit(): f3b. call in *note
     mmap.mmap: 1ed.

   - bpo-37269(6): Fix a bug in the peephole optimizer that was not
     treating correctly constant conditions with binary operators.
     Patch by Pablo Galindo.

   - bpo-37213(7): Handle correctly negative line offsets in the
     peephole optimizer.  Patch by Pablo Galindo.

   - bpo-37219(8): Remove errorneous optimization for empty set
     differences.

   - bpo-36922(9): Slot functions optimize any callable with
     ‘Py_TPFLAGS_METHOD_DESCRIPTOR’ instead of only instances of
     ‘function’.

   - bpo-36974(10): The slot ‘tp_vectorcall_offset’ is inherited
     unconditionally to support ‘super().__call__()’ when the base class
     uses vectorcall.

   - bpo-37160(11): *note threading.get_native_id(): 234. now also
     supports NetBSD.

   - bpo-37077(12): Add *note threading.get_native_id(): 234. support
     for AIX. Patch by M. Felt

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37467

   (2) https://bugs.python.org/issue37417

   (3) https://bugs.python.org/issue24214

   (4) https://bugs.python.org/issue35224

   (5) https://bugs.python.org/issue37316

   (6) https://bugs.python.org/issue37269

   (7) https://bugs.python.org/issue37213

   (8) https://bugs.python.org/issue37219

   (9) https://bugs.python.org/issue36922

   (10) https://bugs.python.org/issue36974

   (11) https://bugs.python.org/issue37160

   (12) https://bugs.python.org/issue37077


File: python.info,  Node: Library<23>,  Next: Documentation<19>,  Prev: Core and Builtins<23>,  Up: Python 3 8 0 beta 2

1.18.24.3 Library
.................

   - bpo-37440(1): http.client now enables TLS 1.3 post-handshake
     authentication for default context or if a cert_file is passed to
     HTTPSConnection.

   - bpo-37437(2): Update vendorized expat version to 2.2.7.

   - bpo-37428(3): 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(4): *note os.sched_setaffinity(): a5a. now correctly
     handles errors that arise during iteration over its ‘mask’
     argument.  Patch by Brandt Bucher.

   - bpo-37412(5): The *note os.getcwdb(): 2b9. function now uses the
     UTF-8 encoding on Windows, rather than the ANSI code page: see PEP
     529(6) for the rationale.  The function is no longer deprecated on
     Windows.

   - bpo-29412(7): Fix IndexError in parsing a header value ending
     unexpectedly.  Patch by Abhilash Raj.

   - bpo-36546(8): 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(9): Fix a bug that was causing the *note queue: db.
     module to fail if the accelerator module was not available.  Patch
     by Pablo Galindo.

   - bpo-33972(10): Email with single part but content-type set to
     ‘multipart/*’ doesn’t raise AttributeError anymore.

   - bpo-37280(11): Use threadpool for reading from file for sendfile
     fallback mode.

   - bpo-37279(12): Fix asyncio sendfile support when sendfile sends
     extra data in fallback mode.

   - bpo-19865(13): *note ctypes.create_unicode_buffer(): fb2. now also
     supports non-BMP characters on platforms with 16-bit ‘wchar_t’ (for
     example, Windows and AIX).

   - bpo-37210(14): Allow pure Python implementation of *note pickle:
     cb. to work even when the C ‘_pickle’ module is unavailable.

   - bpo-35922(15): Fix ‘RobotFileParser.crawl_delay()’ and
     ‘RobotFileParser.request_rate()’ to return ‘None’ rather than raise
     *note AttributeError: 3a0. when no relevant rule is defined in the
     robots.txt file.  Patch by Rémi Lapeyre.

   - bpo-35766(16): Change the format of feature_version to be a (major,
     minor) tuple.

   - bpo-36607(17): Eliminate *note RuntimeError: 2bb. raised by *note
     asyncio.all_tasks(): 356. if internal tasks weak set is changed by
     another thread during iteration.

   - bpo-18748(18): ‘_pyio.IOBase’ destructor now does nothing if
     getting the ‘closed’ attribute fails to better mimick ‘_io.IOBase’
     finalizer.

   - bpo-36402(19): 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-34886(20): Fix an unintended ValueError from *note
     subprocess.run(): 3f2. when checking for conflicting *note input:
     c70. and ‘stdin’ or ‘capture_output’ and ‘stdout’ or ‘stderr’ args
     when they were explicitly provided but with *note None: 158. values
     within a passed in ‘**kwargs’ dict rather than as passed directly
     by name.  Patch contributed by Rémi Lapeyre.

   - bpo-37173(21): The exception message for ‘inspect.getfile()’ now
     correctly reports the passed class rather than the builtins module.

   - bpo-37178(22): Give math.perm() a one argument form that means the
     same as math.factorial().

   - bpo-37178(23): For math.perm(n, k), let k default to n, giving the
     same result as factorial.

   - bpo-37163(24): Deprecated passing ‘obj’ argument of *note
     dataclasses.replace(): e9d. as keyword argument.

   - bpo-37165(25): Converted _collections._count_elements to use the
     Argument Clinic.

   - bpo-34767(26): Do not always create a *note collections.deque: 536.
     in *note asyncio.Lock: 28c.

   - bpo-37158(27): Speed-up statistics.fmean() by switching from a
     function to a generator.

   - bpo-37150(28): ‘argparse._ActionsContainer.add_argument’ now throws
     error, if someone accidentally pass FileType class object instead
     of instance of FileType as *note type: 60d. argument

   - bpo-35621(29): Support running asyncio subprocesses when execution
     event loop in a thread on UNIX.

   - bpo-36520(30): Lengthy email headers with UTF-8 characters are now
     properly encoded when they are folded.  Patch by Jeffrey Kintscher.

   - bpo-30835(31): 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-35805(32): 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-35070(33): posix.getgrouplist() now works correctly when the
     user belongs to NGROUPS_MAX supplemental groups.  Patch by Jeffrey
     Kintscher.

   - bpo-32627(34): Fix compile error when ‘_uuid’ headers conflicting
     included.

   - bpo-11122(35): Distutils won’t check for rpmbuild in specified
     paths only.

   - bpo-4963(36): Fixed non-deterministic behavior related to mimetypes
     extension mapping and module reinitialization.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37440

   (2) https://bugs.python.org/issue37437

   (3) https://bugs.python.org/issue37428

   (4) https://bugs.python.org/issue37420

   (5) https://bugs.python.org/issue37412

   (6) https://www.python.org/dev/peps/pep-0529

   (7) https://bugs.python.org/issue29412

   (8) https://bugs.python.org/issue36546

   (9) https://bugs.python.org/issue37394

   (10) https://bugs.python.org/issue33972

   (11) https://bugs.python.org/issue37280

   (12) https://bugs.python.org/issue37279

   (13) https://bugs.python.org/issue19865

   (14) https://bugs.python.org/issue37210

   (15) https://bugs.python.org/issue35922

   (16) https://bugs.python.org/issue35766

   (17) https://bugs.python.org/issue36607

   (18) https://bugs.python.org/issue18748

   (19) https://bugs.python.org/issue36402

   (20) https://bugs.python.org/issue34886

   (21) https://bugs.python.org/issue37173

   (22) https://bugs.python.org/issue37178

   (23) https://bugs.python.org/issue37178

   (24) https://bugs.python.org/issue37163

   (25) https://bugs.python.org/issue37165

   (26) https://bugs.python.org/issue34767

   (27) https://bugs.python.org/issue37158

   (28) https://bugs.python.org/issue37150

   (29) https://bugs.python.org/issue35621

   (30) https://bugs.python.org/issue36520

   (31) https://bugs.python.org/issue30835

   (32) https://bugs.python.org/issue35805

   (33) https://bugs.python.org/issue35070

   (34) https://bugs.python.org/issue32627

   (35) https://bugs.python.org/issue11122

   (36) https://bugs.python.org/issue4963


File: python.info,  Node: Documentation<19>,  Next: Tests<15>,  Prev: Library<23>,  Up: Python 3 8 0 beta 2

1.18.24.4 Documentation
.......................

   - bpo-34903(1): Documented that in *note
     datetime.datetime.strptime(): fb4, the leading zero in some
     two-digit formats is optional.  Patch by Mike Gleen.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue34903


File: python.info,  Node: Tests<15>,  Next: Build<13>,  Prev: Documentation<19>,  Up: Python 3 8 0 beta 2

1.18.24.5 Tests
...............

   - bpo-37421(1): 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(2): test_concurrent_futures now cleans up multiprocessing
     to remove immediately temporary directories created by
     multiprocessing.util.get_temp_dir().

   - bpo-37421(3): test_winconsoleio doesn’t leak a temporary file
     anymore: use tempfile.TemporaryFile() to remove it when the test
     completes.

   - bpo-37421(4): multiprocessing tests now explicitly call
     ‘_run_finalizers()’ to immediately remove temporary directories
     created by tests.

   - bpo-37199(5): Fix test failures when IPv6 is unavailable or
     disabled.

   - bpo-37335(6): Remove no longer necessary code from c locale
     coercion tests

   - bpo-37421(7): Fix test_shutil to no longer leak temporary files.

   - bpo-37411(8): Fix test_wsgiref.testEnviron() to no longer depend on
     the environment variables (don’t fail if "X" variable is set).

   - bpo-37400(9): 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(10): 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(11): 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(12): Avoid TimeoutError in test_asyncio:
     test_start_tls_server_1()

   - bpo-37278(13): Fix test_asyncio ProactorLoopCtrlC: join the thread
     to prevent leaking a running thread and leaking a reference.

   - bpo-37261(14): Fix *note test.support.catch_unraisable_exception():
     fb6.: its __exit__() method now ignores unraisable exception raised
     when clearing its ‘unraisable’ attribute.

   - bpo-37169(15): Rewrite ‘_PyObject_IsFreed()’ unit tests.

   - bpo-37153(16): ‘test_venv.test_mutiprocessing()’ now explicitly
     calls ‘pool.terminate()’ to wait until the pool completes.

   - bpo-28009(17): 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

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37421

   (2) https://bugs.python.org/issue37421

   (3) https://bugs.python.org/issue37421

   (4) https://bugs.python.org/issue37421

   (5) https://bugs.python.org/issue37199

   (6) https://bugs.python.org/issue37335

   (7) https://bugs.python.org/issue37421

   (8) https://bugs.python.org/issue37411

   (9) https://bugs.python.org/issue37400

   (10) https://bugs.python.org/issue37359

   (11) https://bugs.python.org/issue37362

   (12) https://bugs.python.org/issue35998

   (13) https://bugs.python.org/issue37278

   (14) https://bugs.python.org/issue37261

   (15) https://bugs.python.org/issue37169

   (16) https://bugs.python.org/issue37153

   (17) https://bugs.python.org/issue28009


File: python.info,  Node: Build<13>,  Next: Windows<16>,  Prev: Tests<15>,  Up: Python 3 8 0 beta 2

1.18.24.6 Build
...............

   - bpo-37189(1): Many ‘PyRun_XXX()’ functions like *note
     PyRun_String(): fb8. were no longer exported in ‘libpython38.dll’
     by mistake.  Export them again to fix the ABI compatibiliy.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37189


File: python.info,  Node: Windows<16>,  Next: macOS<12>,  Prev: Build<13>,  Up: Python 3 8 0 beta 2

1.18.24.7 Windows
.................

   - bpo-10945(1): Officially drop support for creating bdist_wininst
     installers on non-Windows systems.

   - bpo-37369(2): Fixes path for *note sys.executable: 275. when
     running from the Microsoft Store.

   - bpo-37351(3): Removes libpython38.a from standard Windows
     distribution.

   - bpo-35360(4): Update Windows builds to use SQLite 3.28.0.

   - bpo-37267(5): On Windows, *note os.dup(): f99. no longer creates an
     inheritable fd when handling a character file.

   - bpo-36779(6): Ensure ‘time.tzname’ is correct on Windows when the
     active code page is set to CP_UTF7 or CP_UTF8.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue10945

   (2) https://bugs.python.org/issue37369

   (3) https://bugs.python.org/issue37351

   (4) https://bugs.python.org/issue35360

   (5) https://bugs.python.org/issue37267

   (6) https://bugs.python.org/issue36779


File: python.info,  Node: macOS<12>,  Next: IDLE<22>,  Prev: Windows<16>,  Up: Python 3 8 0 beta 2

1.18.24.8 macOS
...............

   - bpo-34602(1): 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(2): Update macOS installer to use SQLite 3.28.0.

   - bpo-34631(3): Updated OpenSSL to 1.1.1c in macOS installer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue34602

   (2) https://bugs.python.org/issue35360

   (3) https://bugs.python.org/issue34631


File: python.info,  Node: IDLE<22>,  Next: C API<11>,  Prev: macOS<12>,  Up: Python 3 8 0 beta 2

1.18.24.9 IDLE
..............

   - bpo-37325(1): Fix tab focus traversal order for help source and
     custom run dialogs.

   - bpo-37321(2): Both subprocess connection error messages now refer
     to the ’Startup failure’ section of the IDLE doc.

   - bpo-37177(3): 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(4): Adjust "Zoom Height" to individual screens by
     momemtarily 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(5): Make calltip reminder about ’/’ meaning
     positional-only less obtrusive by only adding it when there is room
     on the first line.

   - bpo-5680(6): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue37325

   (2) https://bugs.python.org/issue37321

   (3) https://bugs.python.org/issue37177

   (4) https://bugs.python.org/issue37039

   (5) https://bugs.python.org/issue35763

   (6) https://bugs.python.org/issue5680


File: python.info,  Node: C API<11>,  Prev: IDLE<22>,  Up: Python 3 8 0 beta 2

1.18.24.10 C API
................

   - bpo-36763(1): Add ‘PyConfig_SetWideStringList()’ function.

   - bpo-28805(2): The *note METH_FASTCALL: fbd. calling convention has
     been documented.

   - bpo-37221(3): ‘tp_print’ is put back at the end of the
     ‘PyTypeObject’ structure to restore support for old code (in
     particular generated by Cython) setting ‘tp_print = 0’.  Note that
     ‘tp_print’ will be removed entirely in Python 3.9.

   - bpo-37221(4): The new function *note PyCode_NewWithPosOnlyArgs():
     272. allows to create code objects like *note PyCode_New(): 273,
     but with an extra `posonlyargcount' parameter for indicating the
     number of positonal-only arguments.

   - bpo-37215(5): Fix dtrace issue introduce by bpo-36842(6)

   - bpo-37191(7): Python.h does not need compiler support for
     intermingled declarations (GCC’s ‘-Wdeclaration-after-statement’),
     which were added in 3.8.0 Beta 1.  Note that in Python 3.9,
     intermingled declarations will be needed again.

   - bpo-37170(8): Fix the cast on error in *note
     PyLong_AsUnsignedLongLongMask(): fbe.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36763

   (2) https://bugs.python.org/issue28805

   (3) https://bugs.python.org/issue37221

   (4) https://bugs.python.org/issue37221

   (5) https://bugs.python.org/issue37215

   (6) https://bugs.python.org/issue36842

   (7) https://bugs.python.org/issue37191

   (8) https://bugs.python.org/issue37170


File: python.info,  Node: Python 3 8 0 beta 1,  Next: Python 3 8 0 alpha 4,  Prev: Python 3 8 0 beta 2,  Up: Changelog（更動日誌）

1.18.25 Python 3.8.0 beta 1
---------------------------

`Release date: 2019-06-04'

* Menu:

* Security: Security<17>.
* Core and Builtins: Core and Builtins<24>.
* Library: Library<24>.
* Documentation: Documentation<20>.
* Tests: Tests<16>.
* Build: Build<14>.
* Windows: Windows<17>.
* macOS: macOS<13>.
* IDLE: IDLE<23>.
* Tools/Demos: Tools/Demos<9>.
* C API: C API<12>.


File: python.info,  Node: Security<17>,  Next: Core and Builtins<24>,  Up: Python 3 8 0 beta 1

1.18.25.1 Security
..................

   - bpo-35907(1): CVE-2019-9948: Avoid file reading by disallowing
     ‘local-file://’ and ‘local_file://’ URL schemes in
     ‘URLopener().open()’ and ‘URLopener().retrieve()’ of *note
     urllib.request: 121.

   - bpo-33529(2): 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(3): Updated blake2 implementation which uses secure
     memset implementation provided by platform.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35907

   (2) https://bugs.python.org/issue33529

   (3) https://bugs.python.org/issue33164


File: python.info,  Node: Core and Builtins<24>,  Next: Library<24>,  Prev: Security<17>,  Up: Python 3 8 0 beta 1

1.18.25.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: 185, *note float: 188. and
     *note complex: 18a. will now use the *note __index__(): 18b.
     special method, if available and the corresponding method *note
     __int__(): 18c, *note __float__(): 18d. or *note __complex__():
     18e. 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 *note bytes.hex: 636, *note bytearray.hex: 637,
     and *note memoryview.hex: 638. methods as well as the *note
     binascii.hexlify: fc2. 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(): 1f1.

   - bpo-37032(13): Added new ‘replace()’ method to the code type (*note
     types.CodeType: 199.).

   - bpo-37007(14): Implement *note socket.if_nameindex(): 221, *note
     socket.if_nametoindex(): 222, and *note socket.if_indextoname():
     223. on Windows.

   - bpo-36829(15): *note PyErr_WriteUnraisable(): fc3. now creates a
     traceback object if there is no current traceback.  Moreover, call
     *note PyErr_NormalizeException(): fc4. and *note
     PyException_SetTraceback(): fc5. 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: 45d. 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: 184, *note int: 185, *note float: 188, *note complex:
     18a. and few classes from the standard library.  They now inherit
     ‘__str__()’ from *note object: 2b1.

   - 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: b41. and *note
     sys.float_info: fc6. during shutdown.  Patch by Zackery Spytz.

   - bpo-26826(42): Expose ‘copy_file_range()’ as a low level API in the
     *note os: c5. 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/issue35814

   (2) https://bugs.python.org/issue37126

   (3) https://bugs.python.org/issue37122

   (4) https://bugs.python.org/issue20092

   (5) https://bugs.python.org/issue37087

   (6) https://bugs.python.org/issue26219

   (7) https://bugs.python.org/issue37072

   (8) https://bugs.python.org/issue37029

   (9) https://bugs.python.org/issue26423

   (10) https://bugs.python.org/issue37050

   (11) https://bugs.python.org/issue22385

   (12) https://bugs.python.org/issue26836

   (13) https://bugs.python.org/issue37032

   (14) https://bugs.python.org/issue37007

   (15) https://bugs.python.org/issue36829

   (16) https://bugs.python.org/issue36878

   (17) https://bugs.python.org/issue36878

   (18) https://bugs.python.org/issue2180

   (19) https://bugs.python.org/issue36907

   (20) https://bugs.python.org/issue36946

   (21) https://bugs.python.org/issue36826

   (22) https://bugs.python.org/issue1875

   (23) https://bugs.python.org/issue36027

   (24) https://bugs.python.org/issue36861

   (25) https://bugs.python.org/issue28866

   (26) https://bugs.python.org/issue36851

   (27) https://bugs.python.org/issue34616

   (28) https://bugs.python.org/issue36842

   (29) https://bugs.python.org/issue27639

   (30) https://bugs.python.org/issue36737

   (31) https://bugs.python.org/issue36793

   (32) https://bugs.python.org/issue36817

   (33) https://bugs.python.org/issue24048

   (34) https://bugs.python.org/issue27987

   (35) https://bugs.python.org/issue36601

   (36) https://bugs.python.org/issue36594

   (37) https://bugs.python.org/issue36045

   (38) https://bugs.python.org/issue36084

   (39) https://bugs.python.org/issue36035

   (40) https://bugs.python.org/issue35983

   (41) https://bugs.python.org/issue20602

   (42) https://bugs.python.org/issue26826

   (43) https://bugs.python.org/issue32388

   (44) https://bugs.python.org/issue31862


File: python.info,  Node: Library<24>,  Next: Documentation<20>,  Prev: Core and Builtins<24>,  Up: Python 3 8 0 beta 1

1.18.25.3 Library
.................

   - bpo-37128(1): Added *note math.perm(): 1e7.

   - bpo-37120(2): Add SSLContext.num_tickets to control the number of
     TLSv1.3 session tickets.

   - bpo-12202(3): Fix the error handling in *note
     msilib.SummaryInformation.GetProperty(): fc8.  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): *note msilib.Directory.start_component(): fc9. 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(): 292.
     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(): fca. now logs
     uncaught exception raised by the function using *note
     sys.unraisablehook(): 22e, rather than *note sys.excepthook(): e68,
     so the hook gets access to the function which raised the exception.

   - bpo-33725(11): On macOS, the *note multiprocessing: b8. 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: 249. setup for autospeccing.  Document
     newly implemented async methods in *note unittest.mock.MagicMock:
     78a.

   - 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(): fcb. now accepts the same
     input types for source code as the built-in *note compile(): 1b5.
     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(): 232.
     function which handles uncaught *note threading.Thread.run(): 233.
     exception.  It can be overridden to control how uncaught *note
     threading.Thread.run(): 233. exceptions are handled.

   - bpo-36996(25): Handle *note unittest.mock.patch(): 78d. used as a
     decorator on async functions.

   - bpo-37008(26): Add support for calling *note next(): 687. with the
     mock resulting from *note unittest.mock.mock_open(): fcc.

   - 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 *note
     hex(): c6b, *note oct(): c6a. and *note bin(): c45.

   - bpo-32972(32): Implement ‘unittest.IsolatedAsyncioTestCase’ to help
     testing asyncio-based code.

   - bpo-36952(33): *note fileinput.input(): 2ae. and *note
     fileinput.FileInput: 280. `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: 1e. is deprecated, and import should be done from
     *note collections.abc: 1f.  Still being able to import from *note
     collections: 1e. 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: d80. in *note
     urllib.request.URLopener.retrieve(): fcd.  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(): a7c. now ignores *note
     errno.EINVAL: fce. on *note os.setxattr(): a53. 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: fcf. and *note asyncio.StreamWriter: fd0.
     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(): 293. and *note
     asyncio.create_subprocess_exec(): 292. to use ‘asyncio.Stream’
     instead of deprecated ‘StreamReader’ and ‘StreamWriter’.  Deprecate
     *note asyncio.StreamReader: fcf. and *note asyncio.StreamWriter:
     fd0.  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(): 1e9. 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 *note ast.parse:
     1a2, 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: f3. module are not exposed to the user.  Patch by Aviv
     Palivoda.

   - bpo-24538(56): In *note shutil.copystat(): a7c, 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(): 22e. 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(): 22f.).

   - 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: 717. 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: 1d3. exception to the *note
     gzip: 8c. 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(): 216. now supports silent
     mode.  Patch by Joannah Nanjekye

   - bpo-29183(72): Fix double exceptions in *note
     wsgiref.handlers.BaseHandler: fd1. 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(): b80. 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(): fcc. results now
     respects the argument of read([size]).  Patch contributed by Rémi
     Lapeyre.

   - bpo-35431(88): Implement *note math.comb(): 1e8. 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:
     bcd. 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(): c74. is
     slightly improved.  Patch by Sergey Fedoseev.

   - bpo-33361(95): Fix a bug in *note codecs.StreamRecoder: fd2. where
     seeking might leave old data in a buffer and break subsequent read
     calls.  Patch by Ammar Askar.

   - bpo-22454(96): The *note shlex: e9. module now exposes *note
     shlex.join(): 218, the inverse of *note shlex.split(): 219.  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(): 2ba. on Windows.  The `args' parameter
     now accepts a *note path-like object: 36f. 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: 36f.  The `cwd' parameter now accepts a bytes object.
     Based on patch by Anders Lorentsen.

   - bpo-33123(100): *note pathlib.Path.unlink: fd3. now accepts a
     `missing_ok' parameter to avoid a *note FileNotFoundError: 7c5.
     from being raised.  Patch by Robert Buchholz.

   - bpo-32941(101): Allow *note mmap.mmap: 1ed. objects to access the
     madvise() system call (through *note mmap.mmap.madvise(): 1ee.).

   - 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(): fd4. 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/issue37128

   (2) https://bugs.python.org/issue37120

   (3) https://bugs.python.org/issue12202

   (4) https://bugs.python.org/issue26835

   (5) https://bugs.python.org/issue29262

   (6) https://bugs.python.org/issue12639

   (7) https://bugs.python.org/issue36999

   (8) https://bugs.python.org/issue35246

   (9) https://bugs.python.org/issue35279

   (10) https://bugs.python.org/issue37076

   (11) https://bugs.python.org/issue33725

   (12) https://bugs.python.org/issue37054

   (13) https://bugs.python.org/issue37058

   (14) https://bugs.python.org/issue36933

   (15) https://bugs.python.org/issue37047

   (16) https://bugs.python.org/issue37049

   (17) https://bugs.python.org/issue37046

   (18) https://bugs.python.org/issue37045

   (19) https://bugs.python.org/issue37035

   (20) https://bugs.python.org/issue37001

   (21) https://bugs.python.org/issue37028

   (22) https://bugs.python.org/issue37027

   (23) https://bugs.python.org/issue32528

   (24) https://bugs.python.org/issue1230540

   (25) https://bugs.python.org/issue36996

   (26) https://bugs.python.org/issue37008

   (27) https://bugs.python.org/issue27737

   (28) https://bugs.python.org/issue36969

   (29) https://bugs.python.org/issue36969

   (30) https://bugs.python.org/issue36983

   (31) https://bugs.python.org/issue36972

   (32) https://bugs.python.org/issue32972

   (33) https://bugs.python.org/issue36952

   (34) https://bugs.python.org/issue36952

   (35) https://bugs.python.org/issue36949

   (36) https://bugs.python.org/issue36948

   (37) https://bugs.python.org/issue33524

   (38) https://bugs.python.org/issue24564

   (39) https://bugs.python.org/issue36888

   (40) https://bugs.python.org/issue36921

   (41) https://bugs.python.org/issue25652

   (42) https://bugs.python.org/issue36916

   (43) https://bugs.python.org/issue36889

   (44) https://bugs.python.org/issue36845

   (45) https://bugs.python.org/issue23378

   (46) https://bugs.python.org/issue36867

   (47) https://bugs.python.org/issue23896

   (48) https://bugs.python.org/issue36895

   (49) https://bugs.python.org/issue35545

   (50) https://bugs.python.org/issue36887

   (51) https://bugs.python.org/issue34632

   (52) https://bugs.python.org/issue36878

   (53) https://bugs.python.org/issue36778

   (54) https://bugs.python.org/issue36867

   (55) https://bugs.python.org/issue30262

   (56) https://bugs.python.org/issue24538

   (57) https://bugs.python.org/issue36829

   (58) https://bugs.python.org/issue36832

   (59) https://bugs.python.org/issue36814

   (60) https://bugs.python.org/issue33110

   (61) https://bugs.python.org/issue26903

   (62) https://bugs.python.org/issue36813

   (63) https://bugs.python.org/issue36806

   (64) https://bugs.python.org/issue36802

   (65) https://bugs.python.org/issue36801

   (66) https://bugs.python.org/issue36785

   (67) https://bugs.python.org/issue36772

   (68) https://bugs.python.org/issue6584

   (69) https://bugs.python.org/issue36748

   (70) https://bugs.python.org/issue8138

   (71) https://bugs.python.org/issue22640

   (72) https://bugs.python.org/issue29183

   (73) https://bugs.python.org/issue36548

   (74) https://bugs.python.org/issue36542

   (75) https://bugs.python.org/issue36533

   (76) https://bugs.python.org/issue35252

   (77) https://bugs.python.org/issue35900

   (78) https://bugs.python.org/issue35900

   (79) https://bugs.python.org/issue36368

   (80) https://bugs.python.org/issue31904

   (81) https://bugs.python.org/issue27497

   (82) https://bugs.python.org/issue36239

   (83) https://bugs.python.org/issue26707

   (84) https://bugs.python.org/issue31904

   (85) https://bugs.python.org/issue35125

   (86) https://bugs.python.org/issue35721

   (87) https://bugs.python.org/issue31855

   (88) https://bugs.python.org/issue35431

   (89) https://bugs.python.org/issue26660

   (90) https://bugs.python.org/issue34271

   (91) https://bugs.python.org/issue26467

   (92) https://bugs.python.org/issue33569

   (93) https://bugs.python.org/issue34424

   (94) https://bugs.python.org/issue34303

   (95) https://bugs.python.org/issue33361

   (96) https://bugs.python.org/issue22454

   (97) https://bugs.python.org/issue31922

   (98) https://bugs.python.org/issue24882

   (99) https://bugs.python.org/issue31961

   (100) https://bugs.python.org/issue33123

   (101) https://bugs.python.org/issue32941

   (102) https://bugs.python.org/issue22102

   (103) https://bugs.python.org/issue32515

   (104) https://bugs.python.org/issue32299

   (105) https://bugs.python.org/issue27141

   (106) https://bugs.python.org/issue31829

   (107) https://bugs.python.org/issue23395


File: python.info,  Node: Documentation<20>,  Next: Tests<16>,  Prev: Library<24>,  Up: Python 3 8 0 beta 1

1.18.25.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 *note
     pty.spawn: 89d. 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 *note copy(): 26. 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/issue36896

   (2) https://bugs.python.org/issue36686

   (3) https://bugs.python.org/issue36984

   (4) https://bugs.python.org/issue36868

   (5) https://bugs.python.org/issue35924

   (6) https://bugs.python.org/issue36783

   (7) https://bugs.python.org/issue36797

   (8) https://bugs.python.org/issue22865

   (9) https://bugs.python.org/issue35397

   (10) https://bugs.python.org/issue32995

   (11) https://bugs.python.org/issue33519

   (12) https://bugs.python.org/issue33482

   (13) https://bugs.python.org/issue25735

   (14) https://bugs.python.org/issue20285


File: python.info,  Node: Tests<16>,  Next: Build<14>,  Prev: Documentation<20>,  Up: Python 3 8 0 beta 1

1.18.25.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(): fb6. rather than
     *note test.support.captured_stderr(): fd7.

   - 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():
     fb6.: context manager catching unraisable exception using *note
     sys.unraisablehook(): 22e.

   - 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: 31. 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/issue37069

   (2) https://bugs.python.org/issue37098

   (3) https://bugs.python.org/issue37081

   (4) https://bugs.python.org/issue36829

   (5) https://bugs.python.org/issue36915

   (6) https://bugs.python.org/issue36719

   (7) https://bugs.python.org/issue36816

   (8) https://bugs.python.org/issue35925

   (9) https://bugs.python.org/issue36782

   (10) https://bugs.python.org/issue36342


File: python.info,  Node: Build<14>,  Next: Windows<17>,  Prev: Tests<16>,  Up: Python 3 8 0 beta 1

1.18.25.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/issue36721

   (2) https://bugs.python.org/issue36786


File: python.info,  Node: Windows<17>,  Next: macOS<13>,  Prev: Build<14>,  Up: Python 3 8 0 beta 1

1.18.25.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 ‘Py_DEPRECATED()’ macro has been implemented for
     MSVC.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36965

   (2) https://bugs.python.org/issue35926

   (3) https://bugs.python.org/issue29883

   (4) https://bugs.python.org/issue33407


File: python.info,  Node: macOS<13>,  Next: IDLE<23>,  Prev: Windows<17>,  Up: Python 3 8 0 beta 1

1.18.25.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/issue36231


File: python.info,  Node: IDLE<23>,  Next: Tools/Demos<9>,  Prev: macOS<13>,  Up: Python 3 8 0 beta 1

1.18.25.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/issue35610

   (2) https://bugs.python.org/issue31858

   (3) https://bugs.python.org/issue37038

   (4) https://bugs.python.org/issue36958

   (5) https://bugs.python.org/issue36807

   (6) https://bugs.python.org/issue32411


File: python.info,  Node: Tools/Demos<9>,  Next: C API<12>,  Prev: IDLE<23>,  Up: Python 3 8 0 beta 1

1.18.25.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/issue37053


File: python.info,  Node: C API<12>,  Prev: Tools/Demos<9>,  Up: Python 3 8 0 beta 1

1.18.25.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(): fde. 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(): 2ce. instead.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36763

   (2) https://www.python.org/dev/peps/pep-0587

   (3) https://bugs.python.org/issue36379

   (4) https://bugs.python.org/issue37107

   (5) https://bugs.python.org/issue36974

   (6) https://www.python.org/dev/peps/pep-0590

   (7) https://bugs.python.org/issue36763

   (8) https://bugs.python.org/issue36922

   (9) https://bugs.python.org/issue36728


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.18.26 Python 3.8.0 alpha 4
----------------------------

`Release date: 2019-05-06'

* Menu:

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


File: python.info,  Node: Security<18>,  Next: Core and Builtins<25>,  Up: Python 3 8 0 alpha 4

1.18.26.1 Security
..................

   - bpo-36742(1): Fixes mishandling of pre-normalization characters in
     urlsplit().

   - bpo-30458(2): Address CVE-2019-9740 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(3): *note shutil.which(): edf. 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(): edf. and the
     *note subprocess: fa. module no longer search the executable in the
     current directory if the ‘PATH’ environment variable is not set.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36742

   (2) https://bugs.python.org/issue30458

   (3) https://bugs.python.org/issue35755


File: python.info,  Node: Core and Builtins<25>,  Next: Library<25>,  Prev: Security<18>,  Up: Python 3 8 0 alpha 4

1.18.26.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: 115. 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: 2b2. 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): *note PyEval_AcquireLock(): 2b3. and *note
     PyEval_AcquireThread(): 2b4. now terminate the current thread if
     called while the interpreter is finalizing, making them consistent
     with *note PyEval_RestoreThread(): 2b5, *note
     Py_END_ALLOW_THREADS(): 2b6, and *note PyGILState_Ensure(): 2b7.

   - 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 *note RuntimeError: 2bb. 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(): c20.

   - bpo-36440(18): Include node names in ‘ParserError’ messages,
     instead of numeric IDs.  Patch by A. Skrobov.

   - bpo-36143(19): Regenerate *note keyword: a7. from the Grammar and
     Tokens file using pgen.  Patch by Pablo Galindo.

   - bpo-18372(20): Add missing *note PyObject_GC_Track(): e49. calls in
     the *note pickle: cb. module.  Patch by Zackery Spytz.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36722

   (2) https://bugs.python.org/issue32849

   (3) https://bugs.python.org/issue36623

   (4) https://bugs.python.org/issue20180

   (5) https://bugs.python.org/issue36611

   (6) https://bugs.python.org/issue36588

   (7) https://bugs.python.org/issue36549

   (8) https://bugs.python.org/issue36540

   (9) https://www.python.org/dev/peps/pep-0570

   (10) https://bugs.python.org/issue36475

   (11) https://bugs.python.org/issue36504

   (12) https://bugs.python.org/issue20844

   (13) https://bugs.python.org/issue24214

   (14) https://bugs.python.org/issue36452

   (15) https://bugs.python.org/issue36459

   (16) https://bugs.python.org/issue36433

   (17) https://bugs.python.org/issue36430

   (18) https://bugs.python.org/issue36440

   (19) https://bugs.python.org/issue36143

   (20) https://bugs.python.org/issue18372


File: python.info,  Node: Library<25>,  Next: Documentation<21>,  Prev: Core and Builtins<25>,  Up: Python 3 8 0 alpha 4

1.18.26.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: 280. 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 *note distutils.sysconfig: 62. if *note
     sys.executable: 275. is ‘None’ or an empty string: use *note
     os.getcwd(): fe3. to initialize ‘project_base’.  Fix also the
     distutils build command: don’t use *note sys.executable: 275. if it
     is ‘None’ or an empty string.

   - bpo-35755(12): *note shutil.which(): edf. and
     ‘distutils.spawn.find_executable()’ now use ‘os.confstr("CS_PATH")’
     if available instead of *note os.defpath: fe4, if the ‘PATH’
     environment variable is not set.  Moreover, don’t use
     ‘os.confstr("CS_PATH")’ nor *note os.defpath: fe4. 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: a. 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: 156. ‘dev’) and in
     debug build, the *note io.IOBase: 1dc. 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(): b69. 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:
     94, 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(): 78d. object will now return *note None: 158.
     instead of raising *note RuntimeError: 2bb, 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 faiures
     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(): 1c5. and *note
     datetime.datetime.fromisocalendar(): 1c6, 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: b5. no longer depends on the
     deprecated *note imp: 9a. module, and the initializer for *note
     modulefinder.ModuleFinder: fe5. now has immutable default
     arguments.  Patch by Brandt Bucher.

   - bpo-35376(40): *note modulefinder: b5. correctly handles modules
     that have the same name as a bad package.  Patch by Brandt Bucher.

   - bpo-17396(41): *note modulefinder: b5. no longer crashes when
     encountering syntax errors in followed imports.  Patch by Brandt
     Bucher.

   - bpo-35934(42): Added *note create_server(): 21f. and *note
     has_dualstack_ipv6(): 220. 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(): 1d9. and *note
     staticmethod(): 1da. to *note unittest.mock.create_autospec(): f4e.
     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: 24a.

   - bpo-34547(48): *note wsgiref.handlers.BaseHandler: fd1. now handles
     abrupt client connection terminations gracefully.  Patch by Petter
     Strandmark.

   - bpo-31658(49): *note xml.sax.parse(): fe6. now supports *note
     path-like: 36f.  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/issue35952

   (2) https://bugs.python.org/issue28238

   (3) https://bugs.python.org/issue26978

   (4) https://bugs.python.org/issue1613500

   (5) https://bugs.python.org/issue36734

   (6) https://bugs.python.org/issue13611

   (7) https://bugs.python.org/issue36669

   (8) https://bugs.python.org/issue36676

   (9) https://bugs.python.org/issue36673

   (10) https://bugs.python.org/issue36650

   (11) https://bugs.python.org/issue28552

   (12) https://bugs.python.org/issue35755

   (13) https://bugs.python.org/issue25430

   (14) https://bugs.python.org/issue30485

   (15) https://bugs.python.org/issue36613

   (16) https://bugs.python.org/issue36598

   (17) https://bugs.python.org/issue18748

   (18) https://bugs.python.org/issue36575

   (19) https://bugs.python.org/issue33461

   (20) https://bugs.python.org/issue36559

   (21) https://bugs.python.org/issue17561

   (22) https://bugs.python.org/issue34373

   (23) https://bugs.python.org/issue36232

   (24) https://bugs.python.org/issue36546

   (25) https://bugs.python.org/issue36050

   (26) https://bugs.python.org/issue36522

   (27) https://bugs.python.org/issue36492

   (28) https://bugs.python.org/issue27181

   (29) https://bugs.python.org/issue30427

   (30) https://bugs.python.org/issue36385

   (31) https://bugs.python.org/issue36434

   (32) https://bugs.python.org/issue36407

   (33) https://bugs.python.org/issue36326

   (34) https://bugs.python.org/issue36366

   (35) https://bugs.python.org/issue36348

   (36) https://bugs.python.org/issue31904

   (37) https://bugs.python.org/issue36227

   (38) https://bugs.python.org/issue36004

   (39) https://bugs.python.org/issue35936

   (40) https://bugs.python.org/issue35376

   (41) https://bugs.python.org/issue17396

   (42) https://bugs.python.org/issue35934

   (43) https://bugs.python.org/issue17561

   (44) https://bugs.python.org/issue23078

   (45) https://bugs.python.org/issue35416

   (46) https://bugs.python.org/issue25451

   (47) https://bugs.python.org/issue35082

   (48) https://bugs.python.org/issue34547

   (49) https://bugs.python.org/issue31658

   (50) https://bugs.python.org/issue34139

   (51) https://bugs.python.org/issue33530

   (52) https://bugs.python.org/issue33291

   (53) https://bugs.python.org/issue31310

   (54) https://bugs.python.org/issue31292


File: python.info,  Node: Documentation<21>,  Next: Tests<17>,  Prev: Library<25>,  Up: Python 3 8 0 alpha 4

1.18.26.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: 12d.  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: 12d. documentation.
     Contributed by Stéphane Wirtel.

   - bpo-36157(8): Added Documention 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/issue36625

   (2) https://bugs.python.org/issue30840

   (3) https://bugs.python.org/issue36523

   (4) https://bugs.python.org/issue36425

   (5) https://docs.python.org/zh-cn/

   (6) https://bugs.python.org/issue36345

   (7) https://bugs.python.org/issue36345

   (8) https://bugs.python.org/issue36157

   (9) https://bugs.python.org/issue33043

   (10) https://bugs.python.org/issue35581

   (11) https://bugs.python.org/issue33832

   (12) https://bugs.python.org/issue32913


File: python.info,  Node: Tests<17>,  Next: Build<15>,  Prev: Documentation<21>,  Up: Python 3 8 0 alpha 4

1.18.26.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 mulitprocessing 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: fe9. error.

   - bpo-36611(8): Fix ‘test_sys.test_getallocatedblocks()’ when *note
     tracemalloc: 115. 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/issue36719

   (2) https://bugs.python.org/issue36725

   (3) https://bugs.python.org/issue36454

   (4) https://bugs.python.org/issue32424

   (5) https://bugs.python.org/issue32424

   (6) https://bugs.python.org/issue36635

   (7) https://bugs.python.org/issue36629

   (8) https://bugs.python.org/issue36611

   (9) https://bugs.python.org/issue36560

   (10) https://bugs.python.org/issue36565

   (11) https://bugs.python.org/issue31904

   (12) https://bugs.python.org/issue31904

   (13) https://bugs.python.org/issue36436

   (14) https://bugs.python.org/issue31904

   (15) https://bugs.python.org/issue36341


File: python.info,  Node: Build<15>,  Next: Windows<18>,  Prev: Tests<17>,  Up: Python 3 8 0 alpha 4

1.18.26.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: 15a.
     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/issue36747

   (2) https://bugs.python.org/issue21536

   (3) https://bugs.python.org/issue36707

   (4) https://bugs.python.org/issue36635

   (5) https://bugs.python.org/issue31904

   (6) https://bugs.python.org/issue36618

   (7) https://bugs.python.org/issue36605

   (8) https://bugs.python.org/issue36465

   (9) https://bugs.python.org/issue36577

   (10) https://bugs.python.org/issue36544

   (11) https://bugs.python.org/issue36146

   (12) https://bugs.python.org/issue36508

   (13) https://bugs.python.org/issue36503


File: python.info,  Node: Windows<18>,  Next: macOS<14>,  Prev: Build<15>,  Up: Python 3 8 0 alpha 4

1.18.26.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(): 1c3.

   - 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/issue35920

   (2) https://bugs.python.org/issue36649

   (3) https://bugs.python.org/issue34144

   (4) https://bugs.python.org/issue36509

   (5) https://bugs.python.org/issue35941

   (6) https://bugs.python.org/issue36441

   (7) https://bugs.python.org/issue36085

   (8) https://bugs.python.org/issue36010

   (9) https://bugs.python.org/issue29515

   (10) https://bugs.python.org/issue35947

   (11) https://bugs.python.org/issue34060

   (12) https://bugs.python.org/issue31512


File: python.info,  Node: macOS<14>,  Next: IDLE<24>,  Prev: Windows<18>,  Up: Python 3 8 0 alpha 4

1.18.26.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/issue34602

   (2) https://bugs.python.org/issue18075


File: python.info,  Node: IDLE<24>,  Next: Tools/Demos<10>,  Prev: macOS<14>,  Up: Python 3 8 0 alpha 4

1.18.26.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/issue36429


File: python.info,  Node: Tools/Demos<10>,  Next: C API<13>,  Prev: IDLE<24>,  Up: Python 3 8 0 alpha 4

1.18.26.10 Tools/Demos
......................

   - bpo-14546(1): Fix the argument handling in Tools/scripts/lll.py.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue14546


File: python.info,  Node: C API<13>,  Prev: Tools/Demos<10>,  Up: Python 3 8 0 alpha 4

1.18.26.11 C API
................

   - bpo-36763(1): Fix memory leak in *note
     Py_SetStandardStreamEncoding(): 92a.: release memory if the
     function is called twice.

   - bpo-36641(2): ‘PyDoc_VAR(name)’ and ‘PyDoc_STRVAR(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(): 50f. 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():
     441. before *note Py_Initialize(): 43e. 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(): ff0.
     function were incorrectly interpreted as a single timestamp rather
     than an arguments tuple, which causes existing code to start
     raising *note TypeError: 193.  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/issue36763

   (2) https://bugs.python.org/issue36641

   (3) https://bugs.python.org/issue36389

   (4) https://bugs.python.org/issue36443

   (5) https://bugs.python.org/issue36025

   (6) https://bugs.python.org/issue35810


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.18.27 Python 3.8.0 alpha 3
----------------------------

`Release date: 2019-03-25'

* Menu:

* Security: Security<19>.
* Core and Builtins: Core and Builtins<26>.
* Library: Library<26>.
* Documentation: Documentation<22>.
* Tests: Tests<18>.
* Build: Build<16>.
* Windows: Windows<19>.
* IDLE: IDLE<25>.
* Tools/Demos: Tools/Demos<11>.
* C API: C API<14>.


File: python.info,  Node: Security<19>,  Next: Core and Builtins<26>,  Up: Python 3 8 0 alpha 3

1.18.27.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: ff3. policy.  Patch by
     Karthikeyan Singaravelan.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36216

   (2) https://bugs.python.org/issue35121


File: python.info,  Node: Core and Builtins<26>,  Next: Library<26>,  Prev: Security<19>,  Up: Python 3 8 0 alpha 3

1.18.27.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: 48d. 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(): 1b5. 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(): 5c7, *note
     marshal.load(): ff5, 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__(): 18b. special method will be
     used instead of *note __int__(): 18c. 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/issue36421

   (2) https://bugs.python.org/issue36412

   (3) https://bugs.python.org/issue36398

   (4) https://bugs.python.org/issue36256

   (5) https://bugs.python.org/issue36365

   (6) https://bugs.python.org/issue36374

   (7) https://bugs.python.org/issue36236

   (8) https://bugs.python.org/issue36352

   (9) https://bugs.python.org/issue36301

   (10) https://bugs.python.org/issue36333

   (11) https://bugs.python.org/issue36332

   (12) https://bugs.python.org/issue36282

   (13) https://bugs.python.org/issue30040

   (14) https://bugs.python.org/issue36262

   (15) https://bugs.python.org/issue36252

   (16) https://bugs.python.org/issue36218

   (17) https://bugs.python.org/issue36188

   (18) https://bugs.python.org/issue36124

   (19) https://bugs.python.org/issue35975

   (20) https://bugs.python.org/issue31904

   (21) https://bugs.python.org/issue36048

   (22) https://bugs.python.org/issue35808


File: python.info,  Node: Library<26>,  Next: Documentation<22>,  Prev: Core and Builtins<26>,  Up: Python 3 8 0 alpha 3

1.18.27.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: a. 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
     mod:*note tarfile: 102. 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: ab. 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: ca. ‘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: 1ed. 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(): ff7.
     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:
     36f.  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): *note pprint.pp: 213. 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 *note
     pprint.pprint: 214, *note pprint.pformat: 89b. and *note
     pprint.PrettyPrinter: 89a.  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(): a29.
     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(): f4e. should propagate to the
     parent.  Patch by Karthikeyan Singaravelan.

   - bpo-35198(37): Fix C++ extension compilation on AIX

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36401

   (2) https://bugs.python.org/issue36320

   (3) https://bugs.python.org/issue34745

   (4) https://bugs.python.org/issue36324

   (5) https://bugs.python.org/issue36321

   (6) https://bugs.python.org/issue36297

   (7) https://bugs.python.org/issue36298

   (8) https://bugs.python.org/issue36268

   (9) https://bugs.python.org/issue36285

   (10) https://bugs.python.org/issue31904

   (11) https://bugs.python.org/issue36272

   (12) https://bugs.python.org/issue36280

   (13) https://bugs.python.org/issue35931

   (14) https://bugs.python.org/issue36251

   (15) https://bugs.python.org/issue36235

   (16) https://bugs.python.org/issue35807

   (17) https://bugs.python.org/issue36139

   (18) https://bugs.python.org/issue36179

   (19) https://bugs.python.org/issue36169

   (20) https://bugs.python.org/issue36103

   (21) https://bugs.python.org/issue36130

   (22) https://bugs.python.org/issue35652

   (23) https://bugs.python.org/issue35178

   (24) https://bugs.python.org/issue36106

   (25) https://bugs.python.org/issue36091

   (26) https://bugs.python.org/issue36043

   (27) https://bugs.python.org/issue35899

   (28) https://bugs.python.org/issue21269

   (29) https://bugs.python.org/issue30670

   (30) https://bugs.python.org/issue35843

   (31) https://bugs.python.org/issue35802

   (32) https://bugs.python.org/issue35715

   (33) https://bugs.python.org/issue35493

   (34) https://bugs.python.org/issue35661

   (35) https://bugs.python.org/issue35121

   (36) https://bugs.python.org/issue21478

   (37) https://bugs.python.org/issue35198


File: python.info,  Node: Documentation<22>,  Next: Tests<18>,  Prev: Library<26>,  Up: Python 3 8 0 alpha 3

1.18.27.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/issue36329

   (2) https://bugs.python.org/issue36138

   (3) https://bugs.python.org/issue21314


File: python.info,  Node: Tests<18>,  Next: Build<16>,  Prev: Documentation<22>,  Up: Python 3 8 0 alpha 3

1.18.27.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/issue36234

   (2) https://bugs.python.org/issue29571

   (3) https://bugs.python.org/issue36123


File: python.info,  Node: Build<16>,  Next: Windows<19>,  Prev: Tests<18>,  Up: Python 3 8 0 alpha 3

1.18.27.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/issue36356

   (2) https://bugs.python.org/issue36146

   (3) https://bugs.python.org/issue36146

   (4) https://bugs.python.org/issue31904


File: python.info,  Node: Windows<19>,  Next: IDLE<25>,  Prev: Build<16>,  Up: Python 3 8 0 alpha 3

1.18.27.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/issue36312

   (2) https://bugs.python.org/issue36264

   (3) https://bugs.python.org/issue24643


File: python.info,  Node: IDLE<25>,  Next: Tools/Demos<11>,  Prev: Windows<19>,  Up: Python 3 8 0 alpha 3

1.18.27.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/issue36405

   (2) https://bugs.python.org/issue36396

   (3) https://bugs.python.org/issue36176

   (4) https://bugs.python.org/issue23205

   (5) https://bugs.python.org/issue23216

   (6) https://bugs.python.org/issue36152

   (7) https://bugs.python.org/issue32129

   (8) https://bugs.python.org/issue36096

   (9) https://bugs.python.org/issue30348


File: python.info,  Node: Tools/Demos<11>,  Next: C API<14>,  Prev: IDLE<25>,  Up: Python 3 8 0 alpha 3

1.18.27.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/issue35132

   (2) https://bugs.python.org/issue32217


File: python.info,  Node: C API<14>,  Prev: Tools/Demos<11>,  Up: Python 3 8 0 alpha 3

1.18.27.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/issue36381

   (2) https://bugs.python.org/issue36142


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.18.28 Python 3.8.0 alpha 2
----------------------------

`Release date: 2019-02-25'

* Menu:

* Core and Builtins: Core and Builtins<27>.
* Library: Library<27>.
* Documentation: Documentation<23>.
* Tests: Tests<19>.
* Windows: Windows<20>.
* IDLE: IDLE<26>.


File: python.info,  Node: Core and Builtins<27>,  Next: Library<27>,  Up: Python 3 8 0 alpha 2

1.18.28.1 Core and Builtins
...........................

   - bpo-36052(1): Raise a *note SyntaxError: 45d. when assigning a
     value to *note __debug__: 1001. 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: 4f0. 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(): 44a. when
     sorting objects with ‘ob_type->tp_richcompare == NULL’.  Patch by
     Zackery Spytz.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue36052

   (2) https://bugs.python.org/issue36012

   (3) https://bugs.python.org/issue35942

   (4) https://bugs.python.org/issue36016

   (5) https://bugs.python.org/issue1054041

   (6) https://bugs.python.org/issue35992

   (7) https://bugs.python.org/issue35993

   (8) https://bugs.python.org/issue35991

   (9) https://bugs.python.org/issue35961

   (10) https://bugs.python.org/issue35911

   (11) https://bugs.python.org/issue12822

   (12) https://bugs.python.org/issue15248

   (13) https://bugs.python.org/issue35886

   (14) https://bugs.python.org/issue31506

   (15) https://bugs.python.org/issue35724

   (16) https://bugs.python.org/issue33608

   (17) https://bugs.python.org/issue33989


File: python.info,  Node: Library<27>,  Next: Documentation<23>,  Prev: Core and Builtins<27>,  Up: Python 3 8 0 alpha 2

1.18.28.2 Library
.................

   - bpo-35512(1): *note unittest.mock.patch.dict(): fd4. 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(): edf.

   - bpo-35960(6): Fix *note dataclasses.field(): 1003. 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(): 1004.
     assertion errors.  Contributed by Susan Su.

   - bpo-35931(8): The *note pdb: ca. ‘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(): bb7, *note re.findall(): 968, *note re.sub():
     480. 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: 129.: 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(): 1e5. as analogous
     function to *note sum(): 1e6. 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: 195. subclasses and *note datetime.timedelta:
     196. now returns an object of the same type as the *note
     datetime.datetime: 195. subclass.  As a result, *note
     datetime.datetime.astimezone(): 197. and alternate constructors
     like *note datetime.datetime.now(): 1005. 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: 256, ‘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/issue35512

   (2) https://bugs.python.org/issue36018

   (3) https://bugs.python.org/issue35904

   (4) https://bugs.python.org/issue35918

   (5) https://bugs.python.org/issue18283

   (6) https://bugs.python.org/issue35960

   (7) https://bugs.python.org/issue35500

   (8) https://bugs.python.org/issue35931

   (9) https://bugs.python.org/issue24209

   (10) https://bugs.python.org/issue35321

   (11) https://bugs.python.org/issue35378

   (12) https://bugs.python.org/issue34294

   (13) https://bugs.python.org/issue35615

   (14) https://bugs.python.org/issue35606

   (15) https://bugs.python.org/issue32417

   (16) https://bugs.python.org/issue35153

   (17) https://bugs.python.org/issue34572


File: python.info,  Node: Documentation<23>,  Next: Tests<19>,  Prev: Library<27>,  Up: Python 3 8 0 alpha 2

1.18.28.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/issue36083

   (2) https://bugs.python.org/issue36007

   (3) https://bugs.python.org/issue22062


File: python.info,  Node: Tests<19>,  Next: Windows<20>,  Prev: Documentation<23>,  Up: Python 3 8 0 alpha 2

1.18.28.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 *note test.support.check_syntax_warning():
     1008.

   - 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/issue27313

   (2) https://bugs.python.org/issue36019

   (3) https://bugs.python.org/issue36037

   (4) https://bugs.python.org/issue35798

   (5) https://bugs.python.org/issue35505

   (6) https://bugs.python.org/issue35917

   (7) https://bugs.python.org/issue35704

   (8) https://bugs.python.org/issue34720


File: python.info,  Node: Windows<20>,  Next: IDLE<26>,  Prev: Tests<19>,  Up: Python 3 8 0 alpha 2

1.18.28.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/issue35976

   (2) https://bugs.python.org/issue35692

   (3) https://bugs.python.org/issue35872

   (4) https://bugs.python.org/issue35873

   (5) https://bugs.python.org/issue35299


File: python.info,  Node: IDLE<26>,  Prev: Windows<20>,  Up: Python 3 8 0 alpha 2

1.18.28.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/issue24310

   (2) https://bugs.python.org/issue35833

   (3) https://bugs.python.org/issue35689


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.18.29 Python 3.8.0 alpha 1
----------------------------

`Release date: 2019-02-03'

* Menu:

* Security: Security<20>.
* Core and Builtins: Core and Builtins<28>.
* Library: Library<28>.
* Documentation: Documentation<24>.
* Tests: Tests<20>.
* Build: Build<17>.
* Windows: Windows<21>.
* macOS: macOS<15>.
* IDLE: IDLE<27>.
* Tools/Demos: Tools/Demos<12>.
* C API: C API<15>.


File: python.info,  Node: Security<20>,  Next: Core and Builtins<28>,  Up: Python 3 8 0 alpha 1

1.18.29.1 Security
..................

   - bpo-35746(1): [CVE-2019-5010] 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(2): The *note -I: 100d. command line option (run Python
     in isolated mode) is now also copied by the *note multiprocessing:
     b8. and *note distutils: 39. modules when spawning child processes.
     Previously, only *note -E: 100e. and *note -s: d1a. options
     (enabled by *note -I: 100d.) were copied.

   - bpo-34791(3): 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(4): 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(5): CVE-2018-14647: The C accelerated _elementtree module
     now initializes hash randomization salt from _Py_HashSecret instead
     of libexpat’s default CSPRNG.

   - bpo-34405(6): Updated to OpenSSL 1.1.0i for Windows builds.

   - bpo-33871(7): Fixed sending the part of the file in *note
     os.sendfile(): 35e. on macOS. Using the `trailers' argument could
     cause sending more bytes from the input file than was specified.

   - bpo-32533(8): Fixed thread-safety of error handling in _ssl.

   - bpo-33136(9): Harden ssl module against LibreSSL CVE-2018-8970.
     X509_VERIFY_PARAM_set1_host() is called with an explicit namelen.
     A new test ensures that NULL bytes are not allowed.

   - bpo-33001(10): Minimal fix to prevent buffer overrun in os.symlink
     on Windows

   - bpo-32981(11): 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 and CVE-2018-1061.  Patch by Jamie Davis.

   - bpo-28414(12): The ssl module now allows users to perform their own
     IDN en/decoding when using SNI.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35746

   (2) https://bugs.python.org/issue34812

   (3) https://bugs.python.org/issue34791

   (4) https://bugs.python.org/issue17239

   (5) https://bugs.python.org/issue34623

   (6) https://bugs.python.org/issue34405

   (7) https://bugs.python.org/issue33871

   (8) https://bugs.python.org/issue32533

   (9) https://bugs.python.org/issue33136

   (10) https://bugs.python.org/issue33001

   (11) https://bugs.python.org/issue32981

   (12) https://bugs.python.org/issue28414


File: python.info,  Node: Core and Builtins<28>,  Next: Library<28>,  Prev: Security<20>,  Up: Python 3 8 0 alpha 1

1.18.29.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(): 4e0. 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(): 7d0. and ‘%s’ in *note
     PyBytes_FromFormat(): 1010. no longer read memory past the limit if
     `precision' is specified.

   - bpo-35504(12): Fix segfaults and *note SystemError: 600.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(): 4df, ‘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: 144.  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: c5. methods
     that path-like objects are also accepted as input parameters.

   - bpo-35050(34): *note socket: f0.: Fix off-by-one bug in length
     check for ‘AF_ALG’ name and type.

   - bpo-29743(35): Raise *note ValueError: 1fc. instead of *note
     OverflowError: 965. in case of a negative ‘_length_’ in a *note
     ctypes.Array: 1011. subclass.  Also raise *note TypeError: 193.
     instead of *note AttributeError: 3a0. 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: 192. raised as an exception at
     code generation time will be now replaced with a *note SyntaxError:
     45d. for better error reporting.

   - bpo-34983(38): Expose *note symtable.Symbol.is_nonlocal(): 1012. in
     the symtable module.  Patch by Pablo Galindo.

   - bpo-34974(39): *note bytes: 336. and *note bytearray: 337.
     constructors no longer convert unexpected exceptions (e.g.  *note
     MemoryError: ef1. and *note KeyboardInterrupt: 198.) to *note
     TypeError: 193.

   - 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(): 336. when the *note
     list: 263. 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: 192. is now emitted instead
     of a *note DeprecationWarning: 279. 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:
     192. 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(): 4f5. 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 *note
     stat.filemode(): aa2. 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: 3a0. 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(): 1013, ensure that the
     *note closed: 1014. 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(): ecc. before calling *note PyErr_Print():
     f0e.  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(): 1015, *note
     PyIndex_Check(): 1016. 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: b45. list.  ‘PyGC_Collect()’ 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: 2bb. is now raised when the
     custom metaclass doesn’t provide the ‘__classcell__’ entry in the
     namespace passed to ‘type.__new__’.  A *note DeprecationWarning:
     279. was emitted in Python 3.6–3.7.

   - bpo-33499(108): Add *note PYTHONPYCACHEPREFIX: 155. environment
     variable and *note -X: 156. ‘pycache_prefix’ command-line option to
     set an alternate root directory for writing module bytecode cache
     files.

   - bpo-25711(109): The *note zipimport: 144. 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: 2e3. and
     fixes the following issues:

        * Setting global *note StopAsyncIteration: 1017. 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: 182. statement is now allowed in
     the *note finally: 183. 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: 2dc, *note
     continue: 182. and *note return: 191.

     Removed opcodes ‘BREAK_LOOP’, ‘CONTINUE_LOOP’, ‘SETUP_LOOP’ and
     ‘SETUP_EXCEPT’.  Added new opcodes *note ROT_FOUR: 2dd, *note
     BEGIN_FINALLY: 2de. and *note CALL_FINALLY: 2df. and *note
     POP_FINALLY: 2e0.  Changed the behavior of *note END_FINALLY: 2e1.
     and *note WITH_CLEANUP_START: 2e2.

   - 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 *note ctypes.cast(): 1018. 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 *note os.utime(): a42. 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/issue35877

   (2) https://bugs.python.org/issue35814

   (3) https://bugs.python.org/issue35766

   (4) https://bugs.python.org/issue35713

   (5) https://bugs.python.org/issue33416

   (6) https://bugs.python.org/issue35720

   (7) https://bugs.python.org/issue35634

   (8) https://bugs.python.org/issue35623

   (9) https://bugs.python.org/issue35214

   (10) https://bugs.python.org/issue35560

   (11) https://bugs.python.org/issue35552

   (12) https://bugs.python.org/issue35504

   (13) https://bugs.python.org/issue35504

   (14) https://bugs.python.org/issue35494

   (15) https://bugs.python.org/issue35444

   (16) https://bugs.python.org/issue35436

   (17) https://bugs.python.org/issue35423

   (18) https://bugs.python.org/issue35357

   (19) https://bugs.python.org/issue35372

   (20) https://bugs.python.org/issue35336

   (21) https://bugs.python.org/issue31241

   (22) https://bugs.python.org/issue33954

   (23) https://bugs.python.org/issue35269

   (24) https://bugs.python.org/issue35224

   (25) https://www.python.org/dev/peps/pep-0572

   (26) https://bugs.python.org/issue32492

   (27) https://bugs.python.org/issue35214

   (28) https://bugs.python.org/issue35214

   (29) https://bugs.python.org/issue35193

   (30) https://bugs.python.org/issue35169

   (31) https://bugs.python.org/issue34022

   (32) https://bugs.python.org/issue28401

   (33) https://bugs.python.org/issue29341

   (34) https://bugs.python.org/issue35050

   (35) https://bugs.python.org/issue29743

   (36) https://bugs.python.org/issue16806

   (37) https://bugs.python.org/issue35029

   (38) https://bugs.python.org/issue34983

   (39) https://bugs.python.org/issue34974

   (40) https://bugs.python.org/issue34939

   (41) https://bugs.python.org/issue34973

   (42) https://bugs.python.org/issue34876

   (43) https://bugs.python.org/issue34879

   (44) https://bugs.python.org/issue34784

   (45) https://bugs.python.org/issue32912

   (46) https://bugs.python.org/issue34854

   (47) https://bugs.python.org/issue34850

   (48) https://bugs.python.org/issue34824

   (49) https://bugs.python.org/issue30156

   (50) https://bugs.python.org/issue34762

   (51) https://bugs.python.org/issue34751

   (52) https://bugs.python.org/issue34735

   (53) https://bugs.python.org/issue34683

   (54) https://bugs.python.org/issue34651

   (55) https://bugs.python.org/issue34653

   (56) https://bugs.python.org/issue32236

   (57) https://bugs.python.org/issue34641

   (58) https://bugs.python.org/issue34637

   (59) https://bugs.python.org/issue1621

   (60) https://bugs.python.org/issue34588

   (61) https://bugs.python.org/issue34485

   (62) https://bugs.python.org/issue34485

   (63) https://bugs.python.org/issue34485

   (64) https://bugs.python.org/issue34485

   (65) https://bugs.python.org/issue34527

   (66) https://bugs.python.org/issue34527

   (67) https://bugs.python.org/issue34403

   (68) https://bugs.python.org/issue34523

   (69) https://bugs.python.org/issue12458

   (70) https://bugs.python.org/issue34408

   (71) https://bugs.python.org/issue34400

   (72) https://bugs.python.org/issue33073

   (73) https://bugs.python.org/issue34377

   (74) https://bugs.python.org/issue34353

   (75) https://bugs.python.org/issue34320

   (76) https://bugs.python.org/issue34113

   (77) https://bugs.python.org/issue34100

   (78) https://bugs.python.org/issue34151

   (79) https://bugs.python.org/issue34170

   (80) https://bugs.python.org/issue33237

   (81) https://bugs.python.org/issue34149

   (82) https://bugs.python.org/issue34125

   (83) https://bugs.python.org/issue34141

   (84) https://bugs.python.org/issue34126

   (85) https://bugs.python.org/issue24618

   (86) https://bugs.python.org/issue34068

   (87) https://bugs.python.org/issue34087

   (88) https://bugs.python.org/issue34080

   (89) https://bugs.python.org/issue34066

   (90) https://bugs.python.org/issue34042

   (91) https://bugs.python.org/issue33418

   (92) https://bugs.python.org/issue33985

   (93) https://bugs.python.org/issue33956

   (94) https://bugs.python.org/issue24596

   (95) https://bugs.python.org/issue33451

   (96) https://bugs.python.org/issue1617161

   (97) https://bugs.python.org/issue33824

   (98) https://bugs.python.org/issue33803

   (99) https://bugs.python.org/issue33738

   (100) https://bugs.python.org/issue33786

   (101) https://bugs.python.org/issue30167

   (102) https://bugs.python.org/issue33706

   (103) https://bugs.python.org/issue33597

   (104) https://bugs.python.org/issue30654

   (105) https://bugs.python.org/issue33622

   (106) https://bugs.python.org/issue33462

   (107) https://bugs.python.org/issue23722

   (108) https://bugs.python.org/issue33499

   (109) https://bugs.python.org/issue25711

   (110) https://bugs.python.org/issue33509

   (111) https://bugs.python.org/issue31849

   (112) https://bugs.python.org/issue33475

   (113) https://bugs.python.org/issue20104

   (114) https://bugs.python.org/issue33391

   (115) https://bugs.python.org/issue33363

   (116) https://bugs.python.org/issue28055

   (117) https://bugs.python.org/issue33128

   (118) https://bugs.python.org/issue33331

   (119) https://bugs.python.org/issue33312

   (120) https://bugs.python.org/issue33305

   (121) https://bugs.python.org/issue33306

   (122) https://bugs.python.org/issue33234

   (123) https://bugs.python.org/issue33270

   (124) https://bugs.python.org/issue30455

   (125) https://bugs.python.org/issue33176

   (126) https://bugs.python.org/issue33231

   (127) https://bugs.python.org/issue33205

   (128) https://bugs.python.org/issue29922

   (129) https://bugs.python.org/issue33199

   (130) https://bugs.python.org/issue33053

   (131) https://bugs.python.org/issue33138

   (132) https://bugs.python.org/issue33018

   (133) https://bugs.python.org/issue33083

   (134) https://bugs.python.org/issue33041

   (135) https://bugs.python.org/issue25750

   (136) https://bugs.python.org/issue33041

   (137) https://bugs.python.org/issue33026

   (138) https://bugs.python.org/issue33005

   (139) https://bugs.python.org/issue32911

   (140) https://bugs.python.org/issue29463

   (141) https://bugs.python.org/issue17288

   (142) https://bugs.python.org/issue32946

   (143) https://bugs.python.org/issue32932

   (144) https://bugs.python.org/issue32925

   (145) https://bugs.python.org/issue32889

   (146) https://bugs.python.org/issue32836

   (147) https://bugs.python.org/issue31356

   (148) https://bugs.python.org/issue31356

   (149) https://bugs.python.org/issue32305

   (150) https://bugs.python.org/issue32303

   (151) https://bugs.python.org/issue32711

   (152) https://bugs.python.org/issue32583

   (153) https://bugs.python.org/issue32489

   (154) https://bugs.python.org/issue17611

   (155) https://bugs.python.org/issue32285

   (156) https://bugs.python.org/issue10544

   (157) https://bugs.python.org/issue32117

   (158) https://bugs.python.org/issue31902

   (159) https://bugs.python.org/issue25862

   (160) https://bugs.python.org/issue21983

   (161) https://bugs.python.org/issue31577

   (162) https://bugs.python.org/issue29832


File: python.info,  Node: Library<28>,  Next: Documentation<24>,  Prev: Core and Builtins<28>,  Up: Python 3 8 0 alpha 1

1.18.29.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(): 258. and *note
     os.posix_spawnp(): 101a. now have a `setsid' parameter.

   - bpo-23846(8): *note asyncio.ProactorEventLoop: 1ac. now catches and
     logs send errors when the self-pipe is full.

   - bpo-34323(9): *note asyncio: a.: 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(): 101a. 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: b2. 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: 23a. 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 Dong-hee 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(): 577. and *note pydoc: da.

   - bpo-28503(24): The *note crypt: 29. module now internally uses the
     ‘crypt_r()’ library function instead of *note crypt(): 29. 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(): 153. function on *note fractions.Fraction: 186.
     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 synchonizes 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: fa. module can now use the
     *note os.posix_spawn(): 258. 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: 2b. callback workaround: no
     longer create a callback at startup.  Avoid SELinux alert on
     ‘import ctypes’ and ‘import uuid’.

   - bpo-31784(33): *note uuid.uuid1(): 418. now calls *note
     time.time_ns(): 328. rather than ‘int(time.time() * 1e9)’.

   - bpo-35513(34): ‘TextTestRunner’ of ‘unittest.runner’ now uses *note
     time.perf_counter(): 2ab. rather than *note time.time(): 322. to
     measure the execution time of a test: *note time.time(): 322. can
     go backwards, whereas *note time.perf_counter(): 2ab. is monotonic.

   - bpo-35502(35): Fixed reference leaks in *note
     xml.etree.ElementTree.TreeBuilder: 254. 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(): 101b. 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: b8.: 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: 24a. attributes.  Patch by Pablo Galindo.

   - bpo-17185(44): Set ‘__signature__’ on mock for *note inspect: a1.
     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: 4d5. 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: cf. 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: 2c8. on calling *note pwd.getpwuid(): 101c.: 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: ec. 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(): 101d. 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(): 678. 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(): 678. 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(): 101e. now redirects ‘stderr’
     to *note os.devnull: 101f. 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(): 2aa.
     instead.

   - bpo-35344(61): On macOS, *note platform.platform(): 1020. now uses
     *note platform.mac_ver(): 1021, 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(): 48f. 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: f7f. 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
     ‘_io.IncrementalNewlineDecoder’’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: 89. 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(): a90.
     now exits immediately if it’s *note shutdown(): 1022. method is
     called while it is polling for new events.

   - bpo-35024(80): *note importlib: 9b. no longer logs ‘wrote’
     redundantly after ‘(created|could not create)’ 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: 78a. now supports the
     ‘__fspath__’ method (from *note os.PathLike: 4f0.).

   - bpo-35008(88): Fixed references leaks when call the
     ‘__setstate__()’ method of *note xml.etree.ElementTree.Element:
     ac9. 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(): 6fd, *note
     inspect.isgeneratorfunction(): 1023. and *note
     inspect.isasyncgenfunction(): 1024. work with *note
     functools.partial(): 7cd.  Patch by Pablo Galindo.

   - bpo-34521(92): Use *note socket.CMSG_SPACE(): 1025. to calculate
     ancillary data size instead of *note socket.CMSG_LEN(): 1026. 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 *note 2to3: 1027. *note execfile: 1028. fixer
     now opens the file with mode ‘'rb'’.  Patch by Zackery Spytz.

   - bpo-34966(98): *note pydoc: da. 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(): 1029. now
     accepts *note path-like object: 36f. 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: 138. module
     are now able to find children which are instances of ‘Element’
     subclasses.

   - bpo-32680(102): *note smtplib.SMTP: a86. 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(): 102a.
     and *note hexdigest(): 102b. methods for the SHAKE algorithm in the
     *note hashlib: 8d. module.

   - bpo-34925(108): 25% speedup in argument parsing for the functions
     in the bisect module.

   - bpo-34900(109): Fixed *note unittest.TestCase.debug(): 102c. 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 *note gzip.compress: 1d2.
     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(): 216, 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(): 102d. 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: 144.

   - bpo-32892(126): The parser now represents all constants as
     ‘ast.Constant’ 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: *note asyncio.sleep: 286, *note asyncio.wait: 28a. and
     *note asyncio.wait_for: 289.

   - bpo-34738(128): ZIP files created by *note distutils: 39. 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: 5af.
     on mock instances with deleted attributes

   - bpo-34672(134): Add a workaround, so the ‘'Z'’ *note
     time.strftime(): b6a. 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(): 102e. 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 *note ValueError: 1fc. if
     None returned and *note TypeError: 193. 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(): 24b. and *note
     addClassCleanup(): 24c. to unittest to support cleanups for
     ‘setUpModule()’ and *note setUpClass(): 24d.  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:
     fa. 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 *note
     pwd.getpwnam: 102f. and *note grp.getgrnam: 1030. 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: fa. 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: fe4. 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: 1fc. is
     now raised by *note multiprocessing.Queue.put(): 1031. and *note
     multiprocessing.Queue.get(): 1032. instead of *note AssertionError:
     1033. and *note OSError: 1d4, respectively.  Patch by Zackery
     Spytz.

   - bpo-34515(160): Fix parsing non-ASCII identifiers in
     ‘lib2to3.pgen2.tokenize’ (PEP 3131).

   - bpo-13312(161): 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(162): Improved compatibility for streamed files in *note
     zipfile: 143.  Previously an optional signature was not being
     written and certain ZIP applications were not supported.  Patch by
     Silas Sewell.

   - bpo-34454(163): 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(164): Fix inspect.getsourcelines for module level
     frames/tracebacks.  Patch by Vladimir Matveev.

   - bpo-34171(165): Running the *note trace: 113. module no longer
     creates the ‘trace.cover’ file.

   - bpo-34441(166): Fix crash when an ‘ABC’-derived class with invalid
     ‘__subclasses__’ is passed as the second argument to *note
     issubclass(): 455.  Patch by Alexey Izbyshev.

   - bpo-34427(167): Fix infinite loop in ‘a.extend(a)’ for
     ‘MutableSequence’ subclasses.

   - bpo-34412(168): Make *note signal.strsignal(): 1034. work on HP-UX.
     Patch by Michael Osipov.

   - bpo-20849(169): shutil.copytree now accepts a new ‘dirs_exist_ok’
     keyword argument.  Patch by Josh Bronson.

   - bpo-31715(170): Associate ‘.mjs’ file extension with
     ‘application/javascript’ MIME Type.

   - bpo-34384(171): *note os.readlink(): 1f4. now accepts *note
     path-like: 36f. and *note bytes: 336. objects on Windows.

   - bpo-22602(172): The UTF-7 decoder now raises *note
     UnicodeDecodeError: 1fe. for ill-formed sequences starting with "+"
     (as specified in RFC 2152).  Patch by Zackery Spytz.

   - bpo-2122(173): The *note mmap.flush(): 2c4. method now returns
     ‘None’ on success, raises an exception on error under all
     platforms.

   - bpo-34341(174): Appending to the ZIP archive with the ZIP64
     extension no longer grows the size of extra fields of existing
     entries.

   - bpo-34333(175): Fix %-formatting in *note
     pathlib.PurePath.with_suffix(): 1035. when formatting an error
     message.

   - bpo-18540(176): The *note imaplib.IMAP4: 610. and *note
     imaplib.IMAP4_SSL: a1c. classes now resolve to the local host IP
     correctly when the default value of `host' parameter (‘''’) is
     used.

   - bpo-26502(177): Implement ‘traceback.FrameSummary.__len__()’ method
     to preserve compatibility with the old tuple API.

   - bpo-34318(178): *note assertRaises(): abf, *note
     assertRaisesRegex(): ac0, *note assertWarns(): ac1. and *note
     assertWarnsRegex(): ac2. 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(179): Deprecate *note __getitem__(): 27d. methods of *note
     xml.dom.pulldom.DOMEventStream: 27e, *note
     wsgiref.util.FileWrapper: 27f. and *note fileinput.FileInput: 280.

   - bpo-33613(180): Fix a race condition in
     ‘multiprocessing.semaphore_tracker’ when the tracker receives
     SIGINT before it can register signal handlers for ignoring it.

   - bpo-34248(181): Report filename in the exception raised when the
     database file cannot be opened by *note dbm.gnu.open(): 1036. and
     *note dbm.ndbm.open(): 1037. due to OS-related error.  Patch by
     Zsolt Cserna.

   - bpo-33089(182): Add math.dist() to compute the Euclidean distance
     between two points.

   - bpo-34246(183): *note smtplib.SMTP.send_message(): 74a. no longer
     modifies the content of the `mail_options' argument.  Patch by
     Pablo S. Blum de Aguiar.

   - bpo-31047(184): Fix ‘ntpath.abspath’ for invalid paths on windows.
     Patch by Franz Woellert.

   - bpo-32321(185): Add pure Python fallback for functools.reduce.
     Patch by Robert Wright.

   - bpo-34270(186): The default asyncio task class now always has a
     name which can be get or set using two new methods (*note
     get_name(): 1b2. and *note set_name(): 1b1.) and is visible in the
     *note repr(): 7d1. output.  An initial name can also be set using
     the new ‘name’ keyword argument to *note asyncio.create_task():
     1af. 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(187): asyncio’s event loop will not pass timeouts longer
     than one day to epoll/select etc.

   - bpo-34035(188): Fix several AttributeError in zipfile seek()
     methods.  Patch by Mickaël Schoentgen.

   - bpo-32215(189): Fix performance regression in *note sqlite3: f3.
     when a DML statement appeared in a different line than the rest of
     the SQL query.

   - bpo-34075(190): Deprecate passing non-ThreadPoolExecutor instances
     to ‘AbstractEventLoop.set_default_executor()’.

   - bpo-34251(191): Restore ‘msilib.Win64’ to preserve backwards
     compatibility since it’s already used by *note distutils: 39.’
     ‘bdist_msi’ command.

   - bpo-19891(192): Ignore errors caused by missing / non-writable
     homedir while writing history during exit of an interactive
     session.  Patch by Anthony Sottile.

   - bpo-33089(193): Enhanced math.hypot() to support more than two
     dimensions.

   - bpo-34228(194): tracemalloc: PYTHONTRACEMALLOC=0 environment
     variable and -X tracemalloc=0 command line option are now allowed
     to disable explicitly tracemalloc at startup.

   - bpo-13041(195): Use *note shutil.get_terminal_size(): a4f. to
     calculate the terminal width correctly in the
     ‘argparse.HelpFormatter’ class.  Initial patch by Zbyszek
     Jędrzejewski-Szmek.

   - bpo-34213(196): Allow frozen dataclasses to have a field named
     "object".  Previously this conflicted with an internal use of
     "object".

   - bpo-34052(197): *note sqlite3.Connection.create_aggregate(): fa2,
     *note sqlite3.Connection.create_function(): fa3, *note
     sqlite3.Connection.set_authorizer(): fa4, *note
     sqlite3.Connection.set_progress_handler(): fa5. 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(198): Attributes `skipinitialspace', `doublequote' and
     `strict' of the `dialect' attribute of the *note csv: 2a. reader
     are now *note bool: 184. instances instead of integers 0 or 1.

   - bpo-32788(199): Errors other than *note TypeError: 193. raised in
     methods ‘__adapt__()’ and ‘__conform__()’ in the *note sqlite3: f3.
     module are now propagated to the user.

   - bpo-21446(200): The *note reload: 1038. fixer now uses *note
     importlib.reload(): 39e. instead of deprecated *note imp.reload():
     c75.

   - bpo-940286(201): pydoc’s ‘Helper.showtopic()’ method now prints the
     cross references of a topic correctly.

   - bpo-34164(202): *note base64.b32decode(): 962. could raise
     UnboundLocalError or OverflowError for incorrect padding.  Now it
     always raises ‘base64.Error’ in these cases.

   - bpo-33729(203): Fixed issues with arguments parsing in *note
     hashlib: 8d.

   - bpo-34097(204): 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(205): Remove extraneous CR in 2to3 refactor.

   - bpo-34070(206): Make sure to only check if the handle is a tty,
     when opening a file with ‘buffering=-1’.

   - bpo-27494(207): Reverted bpo-27494(208).  2to3 rejects now a
     trailing comma in generator expressions.

   - bpo-33967(209): functools.singledispatch now raises TypeError
     instead of IndexError when no positional arguments are passed.

   - bpo-34041(210): Add the parameter `deterministic' to the *note
     sqlite3.Connection.create_function(): fa3. method.  Patch by Sergey
     Fedoseev.

   - bpo-34056(211): 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(212) hash-based pycs.

   - bpo-34054(213): The multiprocessing module now uses the monotonic
     clock *note time.monotonic(): 774. instead of the system clock
     *note time.time(): 322. to implement timeout.

   - bpo-34043(214): Optimize tarfile uncompress performance about 15%
     when gzip is used.

   - bpo-34044(215): ‘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(216): 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(217): webbrowser: Correct the arguments passed to Opera
     Browser when opening a new URL using the ‘webbrowser’ module.
     Patch by Bumsik Kim.

   - bpo-34003(218): csv.DictReader now creates dicts instead of
     OrderedDicts.  Patch by Michael Selik.

   - bpo-33978(219): Closed existing logging handlers before
     reconfiguration via fileConfig and dictConfig.  Patch by
     Karthikeyan Singaravelan.

   - bpo-14117(220): 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(221): Fixed passing lists and tuples of strings
     containing special characters ‘"’, ‘\’, ‘{’, ‘}’ and ‘\n’ as
     options to *note ttk: 110. widgets.

   - bpo-27500(222): Fix getaddrinfo to resolve IPv6 addresses
     correctly.

   - bpo-24567(223): Improve random.choices() to handle subnormal input
     weights that could occasionally trigger an IndexError.

   - bpo-33871(224): Fixed integer overflow in *note os.readv(): 3bd,
     *note os.writev(): 3c0, *note os.preadv(): 3bc. and *note
     os.pwritev(): 3bf. and in *note os.sendfile(): 35e. with `headers'
     or `trailers' arguments (on BSD-based OSes and macOS).

   - bpo-25007(225): Add *note copy.copy(): 3d0. and *note
     copy.deepcopy(): 3d1. support to zlib compressors and
     decompressors.  Patch by Zackery Spytz.

   - bpo-33929(226): 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(227): 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(228): Added a ’force’ keyword argument to
     logging.basicConfig().

   - bpo-33695(229): *note shutil.copytree(): 21b. uses *note
     os.scandir(): 260. function and all copy functions depending from
     it use cached *note os.stat(): 1f2. 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(): 1f2. syscalls is reduced by 38% making *note
     shutil.copytree(): 21b. especially faster on network filesystems.
     (Contributed by Giampaolo Rodola’ in bpo-33695(230).)

   - bpo-33916(231): bz2 and lzma: When Decompressor.__init__() is
     called twice, free the old lock to not leak memory.

   - bpo-32568(232): Make select.epoll() and its documentation
     consistent regarding `sizehint' and `flags'.

   - bpo-33833(233): Fixed bug in asyncio where ProactorSocketTransport
     logs AssertionError if force closed during write.

   - bpo-33663(234): Convert content length to string before putting to
     header.

   - bpo-33721(235): *note os.path: c6. functions that return a boolean
     result like *note exists(): 1f7, *note lexists(): 1f8, *note
     isdir(): 1f9, *note isfile(): 1fa, *note islink(): 1f5, and *note
     ismount(): 1fb, and *note pathlib.Path: 202. methods that return a
     boolean result like *note exists(): 203, *note is_dir(): 204, *note
     is_file(): 205, *note is_mount(): 206, *note is_symlink(): 207,
     *note is_block_device(): 208, *note is_char_device(): 209, *note
     is_fifo(): 20a, *note is_socket(): 20b. now return ‘False’ instead
     of raising *note ValueError: 1fc. or its subclasses *note
     UnicodeEncodeError: 1fd. and *note UnicodeDecodeError: 1fe. for
     paths that contain characters or bytes unrepresentable at the OS
     level.

   - bpo-26544(236): Fixed implementation of *note platform.libc_ver():
     101d.  It almost always returned version ’2.9’ for glibc.

   - bpo-33843(237): Remove deprecated ‘cgi.escape’, ‘cgi.parse_qs’ and
     ‘cgi.parse_qsl’.

   - bpo-33842(238): Remove ‘tarfile.filemode’ which is deprecated since
     Python 3.3.

   - bpo-30167(239): Prevent site.main() exception if PYTHONSTARTUP is
     set.  Patch by Steve Weber.

   - bpo-33805(240): Improve error message of dataclasses.replace() when
     an InitVar is not specified

   - bpo-33687(241): Fix the call to ‘os.chmod()’ for ‘uu.decode()’ if a
     mode is given or decoded.  Patch by Timo Furrer.

   - bpo-33812(242): 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(243): In configparser, don’t clear section when it is
     assigned to itself.

   - bpo-27397(244): Make email module properly handle invalid-length
     base64 strings.

   - bpo-33578(245): Implement multibyte encoder/decoder state methods

   - bpo-30805(246): Avoid race condition with debug logging

   - bpo-33476(247): Fix _header_value_parser.py when address group is
     missing final ’;’.  Contributed by Enrique Perez-Terron

   - bpo-33694(248): asyncio: Fix a race condition causing data loss on
     pause_reading()/resume_reading() when using the ProactorEventLoop.

   - bpo-32493(249): Correct test for ‘uuid_enc_be’ availability in
     ‘configure.ac’.  Patch by Michael Felt.

   - bpo-33792(250): Add asyncio.WindowsSelectorEventLoopPolicy and
     asyncio.WindowsProactorEventLoopPolicy.

   - bpo-33274(251): 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(252): Update ‘unicodedata’’s database to Unicode version
     11.0.0.

   - bpo-33165(253): Added a stacklevel parameter to logging calls to
     allow use of wrapper/helper functions for logging APIs.

   - bpo-33770(254): improve base64 exception message for encoded inputs
     of invalid length

   - bpo-33769(255): asyncio/start_tls: Fix error message; cancel
     callbacks in case of an unhandled error; mark SSLTransport as
     closed if it is aborted.

   - bpo-33767(256): The concatenation (‘+’) and repetition (‘*’)
     sequence operations now raise *note TypeError: 193. instead of
     *note SystemError: 600. when performed on *note mmap.mmap: 1ed.
     objects.  Patch by Zackery Spytz.

   - bpo-33734(257): asyncio/ssl: Fix AttributeError, increase default
     handshake timeout

   - bpo-31014(258): Fixed creating a controller for *note webbrowser:
     12a. when a user specifies a path to an entry in the BROWSER
     environment variable.  Based on patch by John Still.

   - bpo-2504(259): Add gettext.pgettext() and variants.

   - bpo-33197(260): Add description property for _ParameterKind

   - bpo-32751(261): When cancelling the task due to a timeout, *note
     asyncio.wait_for(): 289. will now wait until the cancellation is
     complete.

   - bpo-32684(262): Fix gather to propagate cancellation of itself even
     with return_exceptions.

   - bpo-33654(263): Support protocol type switching in
     SSLTransport.set_protocol().

   - bpo-33674(264): Pause the transport as early as possible to further
     reduce the risk of data_received() being called before
     connection_made().

   - bpo-33671(265): *note shutil.copyfile(): 259, *note shutil.copy():
     25a, *note shutil.copy2(): 25b, *note shutil.copytree(): 21b. and
     *note shutil.move(): 25c. use platform-specific fast-copy syscalls
     on Linux and macOS in order to copy the file more efficiently.  On
     Windows *note shutil.copyfile(): 259. uses a bigger default buffer
     size (1 MiB instead of 16 KiB) and a *note memoryview(): 25d.-based
     variant of *note shutil.copyfileobj(): 25e. 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(266).)

   - bpo-33674(267): 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(268): Fixed bug where calling write_eof() on a
     _SelectorSocketTransport after it’s already closed raises
     AttributeError.

   - bpo-32610(269): Make asyncio.all_tasks() return only pending tasks.

   - bpo-32410(270): Avoid blocking on file IO in sendfile fallback code

   - bpo-33469(271): Fix RuntimeError after closing loop that used
     run_in_executor

   - bpo-33672(272): Fix Task.__repr__ crash with Cython’s bogus
     coroutines

   - bpo-33654(273): Fix transport.set_protocol() to support switching
     between asyncio.Protocol and asyncio.BufferedProtocol.  Fix
     loop.start_tls() to work with asyncio.BufferedProtocols.

   - bpo-33652(274): Pickles of type variables and subscripted generics
     are now future-proof and compatible with older Python versions.

   - bpo-32493(275): Fixed *note uuid.uuid1(): 418. on FreeBSD.

   - bpo-33238(276): Add ‘InvalidStateError’ to *note
     concurrent.futures: 22.  ‘Future.set_result’ and
     ‘Future.set_exception’ now raise ‘InvalidStateError’ if the futures
     are not pending or running.  Patch by Jason Haydaman.

   - bpo-33618(277): Finalize and document preliminary and experimental
     TLS 1.3 support with OpenSSL 1.1.1

   - bpo-33625(278): Release GIL on *note grp.getgrnam: 1030, *note
     grp.getgrgid: 5e4, *note pwd.getpwnam: 102f. and *note
     pwd.getpwuid: 101c. if reentrant variants of these functions are
     available.  Patch by William Grzybowski.

   - bpo-33623(279): Fix possible SIGSGV when asyncio.Future is created
     in __del__

   - bpo-11874(280): Use a better regex when breaking usage into
     wrappable parts.  Avoids bogus assertion errors from custom metavar
     strings.

   - bpo-30877(281): 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(282): Remove HMAC default to md5 marked for removal in
     3.8 (removal originally planned in 3.6, bump to 3.8 in gh-7062).

   - bpo-33582(283): Emit a deprecation warning for
     inspect.formatargspec

   - bpo-21145(284): Add ‘functools.cached_property’ decorator, for
     computed properties cached for the life of the instance.

   - bpo-33570(285): 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(286): Do not simplify arguments to *note typing.Union:
     1039.  Now ‘Union[Manager, Employee]’ is not simplified to
     ‘Employee’ at runtime.  Such simplification previously caused
     several bugs and limited possibilities for introspection.

   - bpo-12486(287): *note tokenize.generate_tokens(): 103a. is now
     documented as a public API to tokenize unicode strings.  It was
     previously present but undocumented.

   - bpo-33540(288): Add a new ‘block_on_close’ class attribute to
     ‘ForkingMixIn’ and ‘ThreadingMixIn’ classes of *note socketserver:
     f1.

   - bpo-33548(289): tempfile._candidate_tempdir_list should consider
     common TEMP locations

   - bpo-33109(290): argparse subparsers are once again not required by
     default, reverting the change in behavior introduced by
     bpo-26510(291) in 3.7.0a2.

   - bpo-33541(292): Remove unused private method
     ‘_strptime.LocaleTime.__pad’ (a.k.a.  ‘_LocaleTime__pad’).

   - bpo-33536(293): dataclasses.make_dataclass now checks for invalid
     field names and duplicate fields.  Also, added a check for invalid
     field specifications.

   - bpo-33542(294): Prevent ‘uuid.get_node’ from using a DUID instead
     of a MAC on Windows.  Patch by Zvi Effron

   - bpo-26819(295): Fix race condition with
     ‘ReadTransport.resume_reading’ in Windows proactor event loop.

   - Fix failure in *note typing.get_type_hints(): 30f. when ClassVar
     was provided as a string forward reference.

   - bpo-33516(296): *note unittest.mock.MagicMock: 78a. now supports
     the ‘__round__’ magic method.

   - bpo-28612(297): Added support for Site Maps to urllib’s
     ‘RobotFileParser’ as *note RobotFileParser.site_maps(): 103b.
     Patch by Lady Red, based on patch by Peter Wirtz.

   - bpo-28167(298): Remove platform.linux_distribution, which was
     deprecated since 3.5.

   - bpo-33504(299): Switch the default dictionary implementation for
     *note configparser: 23. from *note collections.OrderedDict: 1ba. to
     the standard *note dict: 1b9. type.

   - bpo-33505(300): Optimize asyncio.ensure_future() by reordering if
     checks: 1.17x faster.

   - bpo-33497(301): 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(302): The ‘cProfile.Profile’ class can now be used as a
     context manager.  Patch by Scott Sanderson.

   - bpo-33495(303): 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(304): Correct ‘inspect.isdatadescriptor’ to look for
     ‘__set__’ or ‘__delete__’.  Patch by Aaron Hall.

   - bpo-29209(305): Removed the ‘doctype()’ method and the `html'
     parameter of the constructor of *note XMLParser: 253.  The
     ‘doctype()’ method defined in a subclass will no longer be called.
     Deprecated methods ‘getchildren()’ and ‘getiterator()’ in the *note
     ElementTree: 138. module emit now a *note DeprecationWarning: 279.
     instead of *note PendingDeprecationWarning: 27a.

   - bpo-33453(306): 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(307): 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(308): Print the header values besides the header keys
     instead just the header keys if `debuglevel' is set to >0 in *note
     http.client: 94.  Patch by Marco Strigl.

   - bpo-20087(309): Updated alias mapping with glibc 2.27 supported
     locales.

   - bpo-33422(310): Fix trailing quotation marks getting deleted when
     looking up byte/string literals on pydoc.  Patch by Andrés Delfino.

   - bpo-28167(311): The function ‘platform.linux_distribution’ and
     ‘platform.dist’ now trigger a ‘DeprecationWarning’ and have been
     marked for removal in Python 3.8

   - bpo-33281(312): Fix ctypes.util.find_library regression on macOS.

   - bpo-33311(313): 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(314): The file classes in `tempfile' now accept an
     `errors' parameter that complements the already existing
     `encoding'.  Patch by Stephan Hohe.

   - bpo-32933(315): *note unittest.mock.mock_open(): fcc. now supports
     iteration over the file contents.  Patch by Tony Flury.

   - bpo-33217(316): Raise *note TypeError: 193. when looking up
     non-Enum objects in Enum classes and Enum members.

   - bpo-33197(317): Update error message when constructing invalid
     inspect.Parameters Patch by Dong-hee Na.

   - bpo-33383(318): Fixed crash in the get() method of the *note
     dbm.ndbm: 35. database object when it is called with a single
     argument.

   - bpo-33375(319): 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(320): ‘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(321): Added `jump' parameter to *note dis.stack_effect():
     83f.

   - bpo-27485(322): Rename and deprecate undocumented functions in
     *note urllib.parse(): 120.

   - bpo-33332(323): Add ‘signal.valid_signals()’ to expose the POSIX
     sigfillset() functionality.

   - bpo-33251(324): ‘ConfigParser.items()’ was fixed so that key-value
     pairs passed in via *note vars: 103c. are not included in the
     resulting output.

   - bpo-33329(325): Fix multiprocessing regression on newer glibcs

   - bpo-33334(326): *note dis.stack_effect(): 83f. now supports all
     defined opcodes including NOP and EXTENDED_ARG.

   - bpo-991266(327): Fix quoting of the ‘Comment’ attribute of *note
     http.cookies.SimpleCookie: 103d.

   - bpo-33131(328): Upgrade bundled version of pip to 10.0.1.

   - bpo-33308(329): Fixed a crash in the *note parser: c8. module when
     converting an ST object to a tree of tuples or lists with
     ‘line_info=False’ and ‘col_info=True’.

   - bpo-23403(330): lib2to3 now uses pickle protocol 4 for pre-computed
     grammars.

   - bpo-33266(331): lib2to3 now recognizes ‘rf'...'’ strings.

   - bpo-11594(332): Ensure line-endings are respected when using
     lib2to3.

   - bpo-33254(333): Have *note importlib.resources.contents(): 103e.
     and *note importlib.abc.ResourceReader.contents(): 103f. return an
     *note iterable: bb1. instead of an *note iterator: 1040.

   - bpo-33265(334): ‘contextlib.ExitStack’ and
     ‘contextlib.AsyncExitStack’ now use a method instead of a wrapper
     function for exit callbacks.

   - bpo-33263(335): Fix FD leak in ‘_SelectorSocketTransport’ Patch by
     Vlad Starostin.

   - bpo-33256(336): Fix display of ‘<module>’ call in the html produced
     by ‘cgitb.html()’.  Patch by Stéphane Blondon.

   - bpo-33144(337): ‘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(338): Fixed regression when running pydoc with the *note
     -m: 33c. switch.  (The regression was introduced in 3.7.0b3 by the
     resolution of bpo-33053(339))

     This fix also changed pydoc to add ‘os.getcwd()’ to *note sys.path:
     48d. when necessary, rather than adding ‘"."’.

   - bpo-29613(340): Added support for the ‘SameSite’ cookie flag to the
     ‘http.cookies’ module.

   - bpo-33169(341): Delete entries of ‘None’ in *note
     sys.path_importer_cache: 4a2. when
     ‘importlib.machinery.invalidate_caches()’ is called.

   - bpo-33203(342): ‘random.Random.choice()’ now raises ‘IndexError’
     for empty sequences consistently even when called from subclasses
     without a ‘getrandbits()’ implementation.

   - bpo-33224(343): Update difflib.mdiff() for PEP 479(344).  Convert
     an uncaught StopIteration in a generator into a return-statement.

   - bpo-33209(345): End framing at the end of C implementation of *note
     pickle.Pickler.dump(): 1041.

   - bpo-32861(346): 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(347): ‘DEFAULT_PROTOCOL’ in *note pickle: cb. was bumped
     to 4.  Protocol 4 is described in PEP 3154(348) and available since
     Python 3.4.  It offers better performance and smaller size compared
     to protocol 3 introduced in Python 3.0.

   - bpo-20104(349): Improved error handling and fixed a reference leak
     in *note os.posix_spawn(): 258.

   - bpo-33106(350): Deleting a key from a read-only dbm database raises
     module specific error instead of KeyError.

   - bpo-33175(351): 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(352): Create functools.singledispatchmethod to support
     generic single dispatch on descriptors and methods.

   - bpo-33141(353): Have Field objects pass through __set_name__ to
     their default values, if they have their own __set_name__.

   - bpo-33096(354): 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(355): 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(356): 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(357): The ssl module now compiles with LibreSSL 2.7.1.

   - bpo-32505(358): Raise TypeError if a member variable of a dataclass
     is of type Field, but doesn’t have a type annotation.

   - bpo-33078(359): Fix the failure on OSX caused by the tests relying
     on sem_getvalue

   - bpo-33116(360): Add ’Field’ to dataclasses.__all__.

   - bpo-32896(361): Fix an error where subclassing a dataclass with a
     field that uses a default_factory would generate an incorrect
     class.

   - bpo-33100(362): 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(363): 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(364): Raise RuntimeError when ‘executor.submit’ is called
     during interpreter shutdown.

   - bpo-32968(365): Modulo and floor division involving Fraction and
     float should return float.

   - bpo-33061(366): Add missing ‘NoReturn’ to ‘__all__’ in typing.py

   - bpo-33078(367): Fix the size handling in multiprocessing.Queue when
     a pickling error occurs.

   - bpo-33064(368): lib2to3 now properly supports trailing commas after
     ‘*args’ and ‘**kwargs’ in function signatures.

   - bpo-33056(369): FIX properly close leaking fds in
     concurrent.futures.ProcessPoolExecutor.

   - bpo-33021(370): 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(371): Avoid failing in multiprocessing.Process if the
     standard streams are closed or None at exit.

   - bpo-33034(372): 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(373): Improve struct.unpack_from() exception messages for
     problems with the buffer size and offset.

   - bpo-33037(374): Skip sending/receiving data after SSL transport
     closing.

   - bpo-27683(375): Fix a regression in *note ipaddress: a3. 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(376): Add the strsignal() function in the signal module
     that returns the system description of the given signal, as
     returned by strsignal(3).

   - bpo-32999(377): Fix C implementation of ‘ABC.__subclasscheck__(cls,
     subclass)’ crashed when ‘subclass’ is not a type object.

   - bpo-33009(378): Fix inspect.signature() for single-parameter
     partialmethods.

   - bpo-32969(379): Expose several missing constants in zlib and fix
     corresponding documentation.

   - bpo-32056(380): Improved exceptions raised for invalid number of
     channels and sample width when read an audio file in modules *note
     aifc: 5, *note wave: 128. and *note sunau: fb.

   - bpo-32970(381): Improved disassembly of the MAKE_FUNCTION
     instruction.

   - bpo-32844(382): Fix wrong redirection of a low descriptor (0 or 1)
     to stderr in subprocess if another low descriptor is closed.

   - bpo-32960(383): 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(384): Fixed tarfile.itn handling of out-of-bounds float
     values.  Patch by Joffrey Fuhrer.

   - bpo-32257(385): The ssl module now contains OP_NO_RENEGOTIATION
     constant, available with OpenSSL 1.1.0h or 1.1.1.

   - bpo-32951(386): 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(387): 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(388): Add OP_ENABLE_MIDDLEBOX_COMPAT and test workaround
     for TLSv1.3 for future compatibility with OpenSSL 1.1.1.

   - bpo-32146(389): Document the interaction between frozen executables
     and the spawn and forkserver start methods in multiprocessing.

   - bpo-30622(390): The ssl module now detects missing NPN support in
     LibreSSL.

   - bpo-32922(391): dbm.open() now encodes filename with the filesystem
     encoding rather than default encoding.

   - bpo-32759(392): Free unused arenas in multiprocessing.heap.

   - bpo-32859(393): In ‘os.dup2’, don’t check every call whether the
     ‘dup3’ syscall exists or not.

   - bpo-32556(394): nt._getfinalpathname, nt._getvolumepathname and
     nt._getdiskusage now correctly convert from bytes.

   - bpo-21060(395): 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(396): In *note tkinter: 10d, ‘after_cancel(None)’ now
     raises a *note ValueError: 1fc. instead of canceling the first
     scheduled function.  Patch by Cheryl Sabella.

   - bpo-32852(397): Make sure sys.argv remains as a list when running
     trace.

   - bpo-31333(398): ‘_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(399): Fixed *note asyncio.Condition: 28e. issue which
     silently ignored cancellation after notifying and cancelling a
     conditional lock.  Patch by Bar Harel.

   - bpo-32819(400): 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(401): ‘multiprocessing.Pool’ no longer leaks processes if
     its initialization fails.

   - bpo-32394(402): socket: Remove
     TCP_FASTOPEN,TCP_KEEPCNT,TCP_KEEPIDLE,TCP_KEEPINTVL flags on older
     version Windows during run-time.

   - bpo-31787(403): Fixed refleaks of ‘__init__()’ methods in various
     modules.  (Contributed by Oren Milman)

   - bpo-30157(404): Fixed guessing quote and delimiter in
     csv.Sniffer.sniff() when only the last field is quoted.  Patch by
     Jake Davis.

   - bpo-30688(405): Added support of ‘\N{name}’ escapes in regular
     expressions.  Based on patch by Jonathan Eunice.

   - bpo-32792(406): collections.ChainMap() preserves the order of the
     underlying mappings.

   - bpo-32775(407): *note fnmatch.translate(): 1042. 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(408): Implement native fast sendfile for Windows proactor
     event loop.

   - bpo-32777(409): 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(410): 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(411): A *note dbm.dumb: 33. database opened with flags
     ’r’ is now read-only.  *note dbm.dumb.open(): 2c0. with flags ’r’
     and ’w’ no longer creates a database if it does not exist.

   - bpo-32741(412): Implement ‘asyncio.TimerHandle.when()’ method.

   - bpo-32691(413): Use mod_spec.parent when running modules with pdb

   - bpo-32734(414): 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(415): Do not include name field in SMTP envelope from
     address.  Patch by Stéphane Wirtel

   - bpo-31453(416): Add TLSVersion constants and
     SSLContext.maximum_version / minimum_version attributes.  The new
     API wraps OpenSSL 1.1
     ‘https://www.openssl.org/docs/man1.1.0/ssl/SSL_CTX_set_min_proto_version.html’
     feature.

   - bpo-24334(417): 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(418): Fix the error handling in Aifc_read.initfp() when
     the SSND chunk is not found.  Patch by Zackery Spytz.

   - bpo-32585(419): Add Ttk spinbox widget to *note tkinter.ttk: 110.
     Patch by Alan D Moore.

   - bpo-32512(420): *note profile: d4. CLI accepts ‘-m module_name’ as
     an alternative to script path.

   - bpo-8525(421): 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(422): 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(423): compileall: import ProcessPoolExecutor only when
     needed, preventing hangs on low resource platforms

   - bpo-32221(424): 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(425): *note binascii.unhexlify(): 1043. is now up to 2
     times faster.  Patch by Sergey Fedoseev.

   - bpo-30693(426): The TarFile class now recurses directories in a
     reproducible way.

   - bpo-30693(427): The ZipFile class now recurses directories in a
     reproducible way.

   - bpo-31680(428): Added *note curses.ncurses_version: 1c0.

   - bpo-31908(429): 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(430): Raise a ‘TypeError’ instead of crashing if a
     ‘collections.deque’ subclass returns a non-deque from ‘__new__’.
     Patch by Oren Milman.

   - bpo-31425(431): 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(432): Implemented unpickling instances of *note datetime:
     195, *note date: 194. and *note time: 4f8. pickled by Python 2.
     ‘encoding='latin1'’ should be used for successful decoding.

   - bpo-27645(433): *note sqlite3.Connection: 3dd. now exposes a *note
     backup: 3de. method, if the underlying SQLite library is at version
     3.6.11 or higher.  Patch by Lele Gaifax.

   - bpo-16865(434): Support arrays >=2GiB in *note ctypes: 2b.  Patch
     by Segev Finer.

   - bpo-31508(435): Removed support of arguments in *note
     tkinter.ttk.Treeview.selection: 2bd.  It was deprecated in 3.6.
     Use specialized methods like ‘selection_set’ for changing the
     selection.

   - bpo-29456(436): Fix bugs in hangul normalization: u1176, u11a7 and
     u11c3

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35845

   (2) https://bugs.python.org/issue35864

   (3) https://bugs.python.org/issue35537

   (4) https://bugs.python.org/issue35847

   (5) https://bugs.python.org/issue35813

   (6) https://bugs.python.org/issue35780

   (7) https://bugs.python.org/issue35537

   (8) https://bugs.python.org/issue23846

   (9) https://bugs.python.org/issue34323

   (10) https://bugs.python.org/issue35674

   (11) https://bugs.python.org/issue35733

   (12) https://bugs.python.org/issue35726

   (13) https://bugs.python.org/issue35719

   (14) https://bugs.python.org/issue35717

   (15) https://bugs.python.org/issue35699

   (16) https://bugs.python.org/issue32710

   (17) https://bugs.python.org/issue35702

   (18) https://bugs.python.org/issue32710

   (19) https://bugs.python.org/issue35682

   (20) https://bugs.python.org/issue35283

   (21) https://bugs.python.org/issue35664

   (22) https://bugs.python.org/issue35643

   (23) https://bugs.python.org/issue35619

   (24) https://bugs.python.org/issue28503

   (25) https://bugs.python.org/issue35614

   (26) https://bugs.python.org/issue35568

   (27) https://bugs.python.org/issue35588

   (28) https://bugs.python.org/issue35585

   (29) https://bugs.python.org/issue30561

   (30) https://bugs.python.org/issue35537

   (31) https://bugs.python.org/issue35526

   (32) https://bugs.python.org/issue35523

   (33) https://bugs.python.org/issue31784

   (34) https://bugs.python.org/issue35513

   (35) https://bugs.python.org/issue35502

   (36) https://bugs.python.org/issue35348

   (37) https://bugs.python.org/issue35491

   (38) https://bugs.python.org/issue35477

   (39) https://bugs.python.org/issue31446

   (40) https://bugs.python.org/issue35471

   (41) https://bugs.python.org/issue23057

   (42) https://bugs.python.org/issue35052

   (43) https://bugs.python.org/issue20239

   (44) https://bugs.python.org/issue17185

   (45) https://bugs.python.org/issue35445

   (46) https://bugs.python.org/issue35415

   (47) https://bugs.python.org/issue35424

   (48) https://bugs.python.org/issue35330

   (49) https://bugs.python.org/issue35346

   (50) https://bugs.python.org/issue10496

   (51) https://bugs.python.org/issue10496

   (52) https://bugs.python.org/issue35389

   (53) https://bugs.python.org/issue35394

   (54) https://bugs.python.org/issue35310

   (55) https://bugs.python.org/issue35380

   (56) https://bugs.python.org/issue35341

   (57) https://bugs.python.org/issue35371

   (58) https://bugs.python.org/issue35346

   (59) https://bugs.python.org/issue35066

   (60) https://bugs.python.org/issue35345

   (61) https://bugs.python.org/issue35344

   (62) https://bugs.python.org/issue35312

   (63) https://bugs.python.org/issue35308

   (64) https://bugs.python.org/issue24746

   (65) https://bugs.python.org/issue28604

   (66) https://bugs.python.org/issue35277

   (67) https://bugs.python.org/issue24209

   (68) https://bugs.python.org/issue35226

   (69) https://bugs.python.org/issue29564

   (70) https://bugs.python.org/issue35189

   (71) https://bugs.python.org/issue30064

   (72) https://bugs.python.org/issue35186

   (73) https://bugs.python.org/issue35152

   (74) https://bugs.python.org/issue35062

   (75) https://bugs.python.org/issue35065

   (76) https://bugs.python.org/issue34160

   (77) https://bugs.python.org/issue35079

   (78) https://bugs.python.org/issue33710

   (79) https://bugs.python.org/issue35017

   (80) https://bugs.python.org/issue35024

   (81) https://bugs.python.org/issue35047

   (82) https://bugs.python.org/issue31047

   (83) https://bugs.python.org/issue35053

   (84) https://bugs.python.org/issue31553

   (85) https://bugs.python.org/issue34794

   (86) https://bugs.python.org/issue34909

   (87) https://bugs.python.org/issue35022

   (88) https://bugs.python.org/issue35008

   (89) https://bugs.python.org/issue23420

   (90) https://bugs.python.org/issue33947

   (91) https://bugs.python.org/issue34890

   (92) https://bugs.python.org/issue34521

   (93) https://tools.ietf.org/html/rfc3542.html

   (94) https://bugs.python.org/issue31522

   (95) https://bugs.python.org/issue34970

   (96) https://bugs.python.org/issue34969

   (97) https://bugs.python.org/issue16965

   (98) https://bugs.python.org/issue34966

   (99) https://bugs.python.org/issue34926

   (100) https://bugs.python.org/issue23831

   (101) https://bugs.python.org/issue34941

   (102) https://bugs.python.org/issue32680

   (103) https://bugs.python.org/issue34769

   (104) https://bugs.python.org/issue34936

   (105) https://bugs.python.org/issue34829

   (106) https://bugs.python.org/issue34911

   (107) https://bugs.python.org/issue34922

   (108) https://bugs.python.org/issue34925

   (109) https://bugs.python.org/issue34900

   (110) https://bugs.python.org/issue34844

   (111) https://bugs.python.org/issue34897

   (112) https://bugs.python.org/issue34871

   (113) https://bugs.python.org/issue34898

   (114) https://bugs.python.org/issue28441

   (115) https://bugs.python.org/issue34866

   (116) https://bugs.python.org/issue34711

   (117) https://bugs.python.org/issue34872

   (118) https://bugs.python.org/issue34849

   (119) https://bugs.python.org/issue34022

   (120) https://bugs.python.org/issue34819

   (121) https://bugs.python.org/issue34758

   (122) https://bugs.python.org/issue34789

   (123) https://bugs.python.org/issue34334

   (124) https://bugs.python.org/issue34687

   (125) https://bugs.python.org/issue5950

   (126) https://bugs.python.org/issue32892

   (127) https://bugs.python.org/issue34728

   (128) https://bugs.python.org/issue34738

   (129) https://bugs.python.org/issue34659

   (130) https://bugs.python.org/issue29577

   (131) https://bugs.python.org/issue34670

   (132) https://bugs.python.org/issue32718

   (133) https://bugs.python.org/issue31177

   (134) https://bugs.python.org/issue34672

   (135) https://bugs.python.org/issue34666

   (136) https://bugs.python.org/issue6721

   (137) https://bugs.python.org/issue34658

   (138) https://bugs.python.org/issue34652

   (139) https://bugs.python.org/issue34638

   (140) https://bugs.python.org/issue34536

   (141) https://bugs.python.org/issue34636

   (142) https://bugs.python.org/issue24412

   (143) https://bugs.python.org/issue34630

   (144) https://bugs.python.org/issue32490

   (145) https://bugs.python.org/issue34363

   (146) https://bugs.python.org/issue34625

   (147) https://bugs.python.org/issue32270

   (148) https://bugs.python.org/issue34622

   (149) https://bugs.python.org/issue34610

   (150) https://bugs.python.org/issue34421

   (151) https://bugs.python.org/issue34604

   (152) https://bugs.python.org/issue30977

   (153) https://bugs.python.org/issue34574

   (154) https://bugs.python.org/issue8110

   (155) https://bugs.python.org/issue34530

   (156) https://bugs.python.org/issue34563

   (157) https://bugs.python.org/issue34558

   (158) https://bugs.python.org/issue34282

   (159) https://bugs.python.org/issue22872

   (160) https://bugs.python.org/issue34515

   (161) https://bugs.python.org/issue13312

   (162) https://bugs.python.org/issue34472

   (163) https://bugs.python.org/issue34454

   (164) https://bugs.python.org/issue6700

   (165) https://bugs.python.org/issue34171

   (166) https://bugs.python.org/issue34441

   (167) https://bugs.python.org/issue34427

   (168) https://bugs.python.org/issue34412

   (169) https://bugs.python.org/issue20849

   (170) https://bugs.python.org/issue31715

   (171) https://bugs.python.org/issue34384

   (172) https://bugs.python.org/issue22602

   (173) https://bugs.python.org/issue2122

   (174) https://bugs.python.org/issue34341

   (175) https://bugs.python.org/issue34333

   (176) https://bugs.python.org/issue18540

   (177) https://bugs.python.org/issue26502

   (178) https://bugs.python.org/issue34318

   (179) https://bugs.python.org/issue9372

   (180) https://bugs.python.org/issue33613

   (181) https://bugs.python.org/issue34248

   (182) https://bugs.python.org/issue33089

   (183) https://bugs.python.org/issue34246

   (184) https://bugs.python.org/issue31047

   (185) https://bugs.python.org/issue32321

   (186) https://bugs.python.org/issue34270

   (187) https://bugs.python.org/issue34263

   (188) https://bugs.python.org/issue34035

   (189) https://bugs.python.org/issue32215

   (190) https://bugs.python.org/issue34075

   (191) https://bugs.python.org/issue34251

   (192) https://bugs.python.org/issue19891

   (193) https://bugs.python.org/issue33089

   (194) https://bugs.python.org/issue34228

   (195) https://bugs.python.org/issue13041

   (196) https://bugs.python.org/issue34213

   (197) https://bugs.python.org/issue34052

   (198) https://bugs.python.org/issue34197

   (199) https://bugs.python.org/issue32788

   (200) https://bugs.python.org/issue21446

   (201) https://bugs.python.org/issue940286

   (202) https://bugs.python.org/issue34164

   (203) https://bugs.python.org/issue33729

   (204) https://bugs.python.org/issue34097

   (205) https://bugs.python.org/issue34108

   (206) https://bugs.python.org/issue34070

   (207) https://bugs.python.org/issue27494

   (208) https://bugs.python.org/issue27494

   (209) https://bugs.python.org/issue33967

   (210) https://bugs.python.org/issue34041

   (211) https://bugs.python.org/issue34056

   (212) https://www.python.org/dev/peps/pep-0552

   (213) https://bugs.python.org/issue34054

   (214) https://bugs.python.org/issue34043

   (215) https://bugs.python.org/issue34044

   (216) https://bugs.python.org/issue34010

   (217) https://bugs.python.org/issue34019

   (218) https://bugs.python.org/issue34003

   (219) https://bugs.python.org/issue33978

   (220) https://bugs.python.org/issue14117

   (221) https://bugs.python.org/issue33974

   (222) https://bugs.python.org/issue27500

   (223) https://bugs.python.org/issue24567

   (224) https://bugs.python.org/issue33871

   (225) https://bugs.python.org/issue25007

   (226) https://bugs.python.org/issue33929

   (227) https://bugs.python.org/issue33899

   (228) https://bugs.python.org/issue33897

   (229) https://bugs.python.org/issue33695

   (230) https://bugs.python.org/issue33695

   (231) https://bugs.python.org/issue33916

   (232) https://bugs.python.org/issue32568

   (233) https://bugs.python.org/issue33833

   (234) https://bugs.python.org/issue33663

   (235) https://bugs.python.org/issue33721

   (236) https://bugs.python.org/issue26544

   (237) https://bugs.python.org/issue33843

   (238) https://bugs.python.org/issue33842

   (239) https://bugs.python.org/issue30167

   (240) https://bugs.python.org/issue33805

   (241) https://bugs.python.org/issue33687

   (242) https://bugs.python.org/issue33812

   (243) https://bugs.python.org/issue32108

   (244) https://bugs.python.org/issue27397

   (245) https://bugs.python.org/issue33578

   (246) https://bugs.python.org/issue30805

   (247) https://bugs.python.org/issue33476

   (248) https://bugs.python.org/issue33694

   (249) https://bugs.python.org/issue32493

   (250) https://bugs.python.org/issue33792

   (251) https://bugs.python.org/issue33274

   (252) https://bugs.python.org/issue33778

   (253) https://bugs.python.org/issue33165

   (254) https://bugs.python.org/issue33770

   (255) https://bugs.python.org/issue33769

   (256) https://bugs.python.org/issue33767

   (257) https://bugs.python.org/issue33734

   (258) https://bugs.python.org/issue31014

   (259) https://bugs.python.org/issue2504

   (260) https://bugs.python.org/issue33197

   (261) https://bugs.python.org/issue32751

   (262) https://bugs.python.org/issue32684

   (263) https://bugs.python.org/issue33654

   (264) https://bugs.python.org/issue33674

   (265) https://bugs.python.org/issue33671

   (266) https://bugs.python.org/issue25427

   (267) https://bugs.python.org/issue33674

   (268) https://bugs.python.org/issue31647

   (269) https://bugs.python.org/issue32610

   (270) https://bugs.python.org/issue32410

   (271) https://bugs.python.org/issue33469

   (272) https://bugs.python.org/issue33672

   (273) https://bugs.python.org/issue33654

   (274) https://bugs.python.org/issue33652

   (275) https://bugs.python.org/issue32493

   (276) https://bugs.python.org/issue33238

   (277) https://bugs.python.org/issue33618

   (278) https://bugs.python.org/issue33625

   (279) https://bugs.python.org/issue33623

   (280) https://bugs.python.org/issue11874

   (281) https://bugs.python.org/issue30877

   (282) https://bugs.python.org/issue33604

   (283) https://bugs.python.org/issue33582

   (284) https://bugs.python.org/issue21145

   (285) https://bugs.python.org/issue33570

   (286) https://bugs.python.org/issue28556

   (287) https://bugs.python.org/issue12486

   (288) https://bugs.python.org/issue33540

   (289) https://bugs.python.org/issue33548

   (290) https://bugs.python.org/issue33109

   (291) https://bugs.python.org/issue26510

   (292) https://bugs.python.org/issue33541

   (293) https://bugs.python.org/issue33536

   (294) https://bugs.python.org/issue33542

   (295) https://bugs.python.org/issue26819

   (296) https://bugs.python.org/issue33516

   (297) https://bugs.python.org/issue28612

   (298) https://bugs.python.org/issue28167

   (299) https://bugs.python.org/issue33504

   (300) https://bugs.python.org/issue33505

   (301) https://bugs.python.org/issue33497

   (302) https://bugs.python.org/issue29235

   (303) https://bugs.python.org/issue33495

   (304) https://bugs.python.org/issue26103

   (305) https://bugs.python.org/issue29209

   (306) https://bugs.python.org/issue33453

   (307) https://bugs.python.org/issue28556

   (308) https://bugs.python.org/issue33365

   (309) https://bugs.python.org/issue20087

   (310) https://bugs.python.org/issue33422

   (311) https://bugs.python.org/issue28167

   (312) https://bugs.python.org/issue33281

   (313) https://bugs.python.org/issue33311

   (314) https://bugs.python.org/issue27300

   (315) https://bugs.python.org/issue32933

   (316) https://bugs.python.org/issue33217

   (317) https://bugs.python.org/issue33197

   (318) https://bugs.python.org/issue33383

   (319) https://bugs.python.org/issue33375

   (320) https://bugs.python.org/issue33336

   (321) https://bugs.python.org/issue32455

   (322) https://bugs.python.org/issue27485

   (323) https://bugs.python.org/issue33332

   (324) https://bugs.python.org/issue33251

   (325) https://bugs.python.org/issue33329

   (326) https://bugs.python.org/issue33334

   (327) https://bugs.python.org/issue991266

   (328) https://bugs.python.org/issue33131

   (329) https://bugs.python.org/issue33308

   (330) https://bugs.python.org/issue23403

   (331) https://bugs.python.org/issue33266

   (332) https://bugs.python.org/issue11594

   (333) https://bugs.python.org/issue33254

   (334) https://bugs.python.org/issue33265

   (335) https://bugs.python.org/issue33263

   (336) https://bugs.python.org/issue33256

   (337) https://bugs.python.org/issue33144

   (338) https://bugs.python.org/issue33185

   (339) https://bugs.python.org/issue33053

   (340) https://bugs.python.org/issue29613

   (341) https://bugs.python.org/issue33169

   (342) https://bugs.python.org/issue33203

   (343) https://bugs.python.org/issue33224

   (344) https://www.python.org/dev/peps/pep-0479

   (345) https://bugs.python.org/issue33209

   (346) https://bugs.python.org/issue32861

   (347) https://bugs.python.org/issue23403

   (348) https://www.python.org/dev/peps/pep-3154

   (349) https://bugs.python.org/issue20104

   (350) https://bugs.python.org/issue33106

   (351) https://bugs.python.org/issue33175

   (352) https://bugs.python.org/issue32380

   (353) https://bugs.python.org/issue33141

   (354) https://bugs.python.org/issue33096

   (355) https://bugs.python.org/issue32873

   (356) https://bugs.python.org/issue33134

   (357) https://bugs.python.org/issue33127

   (358) https://bugs.python.org/issue32505

   (359) https://bugs.python.org/issue33078

   (360) https://bugs.python.org/issue33116

   (361) https://bugs.python.org/issue32896

   (362) https://bugs.python.org/issue33100

   (363) https://bugs.python.org/issue32953

   (364) https://bugs.python.org/issue33097

   (365) https://bugs.python.org/issue32968

   (366) https://bugs.python.org/issue33061

   (367) https://bugs.python.org/issue33078

   (368) https://bugs.python.org/issue33064

   (369) https://bugs.python.org/issue33056

   (370) https://bugs.python.org/issue33021

   (371) https://bugs.python.org/issue31804

   (372) https://bugs.python.org/issue33034

   (373) https://bugs.python.org/issue30249

   (374) https://bugs.python.org/issue33037

   (375) https://bugs.python.org/issue27683

   (376) https://bugs.python.org/issue22674

   (377) https://bugs.python.org/issue32999

   (378) https://bugs.python.org/issue33009

   (379) https://bugs.python.org/issue32969

   (380) https://bugs.python.org/issue32056

   (381) https://bugs.python.org/issue32970

   (382) https://bugs.python.org/issue32844

   (383) https://bugs.python.org/issue32960

   (384) https://bugs.python.org/issue32713

   (385) https://bugs.python.org/issue32257

   (386) https://bugs.python.org/issue32951

   (387) https://bugs.python.org/issue32929

   (388) https://bugs.python.org/issue32947

   (389) https://bugs.python.org/issue32146

   (390) https://bugs.python.org/issue30622

   (391) https://bugs.python.org/issue32922

   (392) https://bugs.python.org/issue32759

   (393) https://bugs.python.org/issue32859

   (394) https://bugs.python.org/issue32556

   (395) https://bugs.python.org/issue21060

   (396) https://bugs.python.org/issue32857

   (397) https://bugs.python.org/issue32852

   (398) https://bugs.python.org/issue31333

   (399) https://bugs.python.org/issue32841

   (400) https://bugs.python.org/issue32819

   (401) https://bugs.python.org/issue19675

   (402) https://bugs.python.org/issue32394

   (403) https://bugs.python.org/issue31787

   (404) https://bugs.python.org/issue30157

   (405) https://bugs.python.org/issue30688

   (406) https://bugs.python.org/issue32792

   (407) https://bugs.python.org/issue32775

   (408) https://bugs.python.org/issue32622

   (409) https://bugs.python.org/issue32777

   (410) https://bugs.python.org/issue32647

   (411) https://bugs.python.org/issue32749

   (412) https://bugs.python.org/issue32741

   (413) https://bugs.python.org/issue32691

   (414) https://bugs.python.org/issue32734

   (415) https://bugs.python.org/issue32727

   (416) https://bugs.python.org/issue31453

   (417) https://bugs.python.org/issue24334

   (418) https://bugs.python.org/issue31848

   (419) https://bugs.python.org/issue32585

   (420) https://bugs.python.org/issue32512

   (421) https://bugs.python.org/issue8525

   (422) https://bugs.python.org/issue31639

   (423) https://bugs.python.org/issue29877

   (424) https://bugs.python.org/issue32221

   (425) https://bugs.python.org/issue32147

   (426) https://bugs.python.org/issue30693

   (427) https://bugs.python.org/issue30693

   (428) https://bugs.python.org/issue31680

   (429) https://bugs.python.org/issue31908

   (430) https://bugs.python.org/issue31608

   (431) https://bugs.python.org/issue31425

   (432) https://bugs.python.org/issue22005

   (433) https://bugs.python.org/issue27645

   (434) https://bugs.python.org/issue16865

   (435) https://bugs.python.org/issue31508

   (436) https://bugs.python.org/issue29456


File: python.info,  Node: Documentation<24>,  Next: Tests<20>,  Prev: Library<28>,  Up: Python 3 8 0 alpha 1

1.18.29.4 Documentation
.......................

   - bpo-21257(1): Document *note http.client.parse_headers(): 1045.

   - 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: 76. 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 charaters 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(): 368, *note asyncio.start_server(): 369.
     and their UNIX socket counterparts.

   - bpo-23859(27): Document that *note asyncio.wait(): 28a. 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: 142. 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: 107. documentation.

   - bpo-32613(49): Update the faq/windows.html to use the py command
     from PEP 397 instead of python.

   - bpo-8722(50): Document *note __getattr__(): 31f. behavior when
     property ‘get()’ method raises *note AttributeError: 3a0.

   - bpo-32614(51): Modify RE examples in documentation to use raw
     strings to prevent *note DeprecationWarning: 279. 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 *note pathlib.PurePath: 1046.
     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: f0.
     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/issue21257

   (2) https://bugs.python.org/issue34764

   (3) https://bugs.python.org/issue35564

   (4) https://bugs.python.org/issue35511

   (5) https://bugs.python.org/issue10536

   (6) https://bugs.python.org/issue35089

   (7) https://bugs.python.org/issue35038

   (8) https://bugs.python.org/issue35042

   (9) https://bugs.python.org/issue35044

   (10) https://bugs.python.org/issue35035

   (11) https://bugs.python.org/issue34967

   (12) https://bugs.python.org/issue34913

   (13) https://bugs.python.org/issue32174

   (14) https://bugs.python.org/issue11233

   (15) https://bugs.python.org/issue34790

   (16) https://bugs.python.org/issue34552

   (17) https://bugs.python.org/issue28617

   (18) https://bugs.python.org/issue20177

   (19) https://bugs.python.org/issue34065

   (20) https://bugs.python.org/issue33460

   (21) https://bugs.python.org/issue33847

   (22) https://bugs.python.org/issue33409

   (23) https://www.python.org/dev/peps/pep-0538

   (24) https://bugs.python.org/issue33197

   (25) https://bugs.python.org/issue17045

   (26) https://bugs.python.org/issue33736

   (27) https://bugs.python.org/issue23859

   (28) https://bugs.python.org/issue32436

   (29) https://www.python.org/dev/peps/pep-0567

   (30) https://bugs.python.org/issue33604

   (31) https://bugs.python.org/issue33594

   (32) https://bugs.python.org/issue33503

   (33) https://bugs.python.org/issue33421

   (34) https://bugs.python.org/issue33487

   (35) https://bugs.python.org/issue33378

   (36) https://bugs.python.org/issue33276

   (37) https://bugs.python.org/issue33201

   (38) https://bugs.python.org/issue33195

   (39) https://bugs.python.org/issue33126

   (40) https://bugs.python.org/issue27212

   (41) https://bugs.python.org/issue28247

   (42) https://bugs.python.org/issue18802

   (43) https://bugs.python.org/issue27428

   (44) https://bugs.python.org/issue28124

   (45) https://bugs.python.org/issue17232

   (46) https://bugs.python.org/issue32436

   (47) https://bugs.python.org/issue32800

   (48) https://bugs.python.org/issue11015

   (49) https://bugs.python.org/issue32613

   (50) https://bugs.python.org/issue8722

   (51) https://bugs.python.org/issue32614

   (52) https://bugs.python.org/issue20709

   (53) https://bugs.python.org/issue32722

   (54) https://bugs.python.org/issue31972

   (55) https://bugs.python.org/issue30607

   (56) https://bugs.python.org/issue8243

   (57) https://bugs.python.org/issue32337

   (58) https://bugs.python.org/issue25041

   (59) https://bugs.python.org/issue31432


File: python.info,  Node: Tests<20>,  Next: Build<17>,  Prev: Documentation<24>,  Up: Python 3 8 0 alpha 1

1.18.29.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: 12. module when running directly
     a test like ‘./python Lib/test/test_xmlrpc.py’.

   - bpo-35513(9): Replace *note time.time(): 322. with *note
     time.monotonic(): 774. in tests to measure time delta.

   - bpo-34279(10): *note test.support.run_unittest(): 1048. 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/issue35772

   (2) https://bugs.python.org/issue35045

   (3) https://bugs.python.org/issue32710

   (4) https://bugs.python.org/issue33717

   (5) https://bugs.python.org/issue35488

   (6) https://bugs.python.org/issue31731

   (7) https://bugs.python.org/issue35424

   (8) https://bugs.python.org/issue35519

   (9) https://bugs.python.org/issue35513

   (10) https://bugs.python.org/issue34279

   (11) https://bugs.python.org/issue35412

   (12) https://bugs.python.org/issue26704

   (13) https://bugs.python.org/issue33725

   (14) https://bugs.python.org/issue35352

   (15) https://bugs.python.org/issue35317

   (16) https://bugs.python.org/issue21263

   (17) https://bugs.python.org/issue34279

   (18) https://bugs.python.org/issue34962

   (19) https://bugs.python.org/issue23596

   (20) https://bugs.python.org/issue34537

   (21) https://bugs.python.org/issue34587

   (22) https://bugs.python.org/issue34661

   (23) https://bugs.python.org/issue34200

   (24) https://bugs.python.org/issue34569

   (25) https://bugs.python.org/issue34594

   (26) https://bugs.python.org/issue34579

   (27) https://bugs.python.org/issue34542

   (28) https://bugs.python.org/issue11193

   (29) https://bugs.python.org/issue34347

   (30) https://bugs.python.org/issue34490

   (31) https://bugs.python.org/issue34391

   (32) https://bugs.python.org/issue11192

   (33) https://bugs.python.org/issue34399

   (34) https://bugs.python.org/issue34373

   (35) https://bugs.python.org/issue11191

   (36) https://bugs.python.org/issue33746

   (37) https://bugs.python.org/issue33901

   (38) https://bugs.python.org/issue33873

   (39) https://bugs.python.org/issue33562

   (40) https://bugs.python.org/issue33655

   (41) https://bugs.python.org/issue32962

   (42) https://bugs.python.org/issue33358

   (43) https://bugs.python.org/issue32872

   (44) https://bugs.python.org/issue32517

   (45) https://bugs.python.org/issue32663

   (46) https://bugs.python.org/issue27643

   (47) https://bugs.python.org/issue19417

   (48) https://bugs.python.org/issue31809


File: python.info,  Node: Build<17>,  Next: Windows<21>,  Prev: Tests<20>,  Up: Python 3 8 0 alpha 1

1.18.29.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/issue34691

   (2) https://bugs.python.org/issue35683

   (3) https://bugs.python.org/issue35642

   (4) https://bugs.python.org/issue35550

   (5) https://bugs.python.org/issue35499

   (6) https://bugs.python.org/issue35257

   (7) https://bugs.python.org/issue35351

   (8) https://bugs.python.org/issue35139

   (9) https://bugs.python.org/issue35059

   (10) https://bugs.python.org/issue35011

   (11) https://bugs.python.org/issue28015

   (12) https://bugs.python.org/issue34765

   (13) https://bugs.python.org/issue34585

   (14) https://bugs.python.org/issue34710

   (15) https://bugs.python.org/issue34582

   (16) https://bugs.python.org/issue34081

   (17) https://bugs.python.org/issue34555

   (18) https://bugs.python.org/issue33015

   (19) https://bugs.python.org/issue34245

   (20) https://bugs.python.org/issue34121

   (21) https://bugs.python.org/issue32430

   (22) https://bugs.python.org/issue30345

   (23) https://bugs.python.org/issue5755

   (24) https://bugs.python.org/issue33614

   (25) https://bugs.python.org/issue33648

   (26) https://bugs.python.org/issue33522

   (27) https://bugs.python.org/issue33512

   (28) https://bugs.python.org/issue33483

   (29) https://bugs.python.org/issue33394

   (30) https://bugs.python.org/issue33393

   (31) https://bugs.python.org/issue33377

   (32) https://bugs.python.org/issue32232

   (33) https://bugs.python.org/issue33182

   (34) https://bugs.python.org/issue33163

   (35) https://bugs.python.org/issue33012

   (36) https://bugs.python.org/issue32898

   (37) https://bugs.python.org/issue29442


File: python.info,  Node: Windows<21>,  Next: macOS<15>,  Prev: Build<17>,  Up: Python 3 8 0 alpha 1

1.18.29.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: 1d4. 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(): 1f4. 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/issue35890

   (2) https://bugs.python.org/issue32560

   (3) https://bugs.python.org/issue35854

   (4) https://bugs.python.org/issue35811

   (5) https://bugs.python.org/issue35797

   (6) https://bugs.python.org/issue35758

   (7) https://bugs.python.org/issue29734

   (8) https://bugs.python.org/issue35596

   (9) https://bugs.python.org/issue35596

   (10) https://bugs.python.org/issue35402

   (11) https://bugs.python.org/issue35401

   (12) https://bugs.python.org/issue34977

   (13) https://bugs.python.org/issue34977

   (14) https://bugs.python.org/issue35067

   (15) https://bugs.python.org/issue32557

   (16) https://bugs.python.org/issue34770

   (17) https://bugs.python.org/issue34603

   (18) https://bugs.python.org/issue34581

   (19) https://bugs.python.org/issue34532

   (20) https://bugs.python.org/issue34062

   (21) https://bugs.python.org/issue34225

   (22) https://bugs.python.org/issue34011

   (23) https://bugs.python.org/issue34006

   (24) https://bugs.python.org/issue31546

   (25) https://bugs.python.org/issue30237

   (26) https://bugs.python.org/issue33895

   (27) https://bugs.python.org/issue33720

   (28) https://bugs.python.org/issue29097

   (29) https://bugs.python.org/issue33316

   (30) https://bugs.python.org/issue33184

   (31) https://bugs.python.org/issue32890

   (32) https://bugs.python.org/issue33016

   (33) https://bugs.python.org/issue32903

   (34) https://bugs.python.org/issue32901

   (35) https://bugs.python.org/issue31966

   (36) https://bugs.python.org/issue32409

   (37) https://bugs.python.org/issue32457

   (38) https://bugs.python.org/issue32370

   (39) https://bugs.python.org/issue29248

   (40) https://bugs.python.org/issue1104


File: python.info,  Node: macOS<15>,  Next: IDLE<27>,  Prev: Windows<21>,  Up: Python 3 8 0 alpha 1

1.18.29.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/issue35401

   (2) https://bugs.python.org/issue35025

   (3) https://bugs.python.org/issue24658

   (4) https://bugs.python.org/issue34405

   (5) https://bugs.python.org/issue33635

   (6) https://bugs.python.org/issue13631

   (7) https://bugs.python.org/issue33184

   (8) https://bugs.python.org/issue32726

   (9) https://bugs.python.org/issue32901

   (10) https://bugs.python.org/issue31903


File: python.info,  Node: IDLE<27>,  Next: Tools/Demos<12>,  Prev: macOS<15>,  Up: Python 3 8 0 alpha 1

1.18.29.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: 8ea.; ‘-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/issue35770

   (2) https://bugs.python.org/issue35769

   (3) https://bugs.python.org/issue35660

   (4) https://bugs.python.org/issue35641

   (5) https://bugs.python.org/issue33987

   (6) https://bugs.python.org/issue34055

   (7) https://bugs.python.org/issue35591

   (8) https://bugs.python.org/issue35196

   (9) https://bugs.python.org/issue35598

   (10) https://bugs.python.org/issue28097

   (11) https://bugs.python.org/issue35208

   (12) https://bugs.python.org/issue35555

   (13) https://bugs.python.org/issue35521

   (14) https://bugs.python.org/issue22703

   (15) https://bugs.python.org/issue35213

   (16) https://bugs.python.org/issue34864

   (17) https://bugs.python.org/issue34864

   (18) https://bugs.python.org/issue35202

   (19) https://bugs.python.org/issue33000

   (20) https://bugs.python.org/issue23220

   (21) https://bugs.python.org/issue35099

   (22) https://bugs.python.org/issue35097

   (23) https://bugs.python.org/issue35093

   (24) https://bugs.python.org/issue35088

   (25) https://bugs.python.org/issue35087

   (26) https://bugs.python.org/issue34548

   (27) https://bugs.python.org/issue1529353

   (28) https://bugs.python.org/issue34047

   (29) https://bugs.python.org/issue34275

   (30) https://bugs.python.org/issue34120

   (31) https://bugs.python.org/issue33975

   (32) https://bugs.python.org/issue33905

   (33) https://bugs.python.org/issue33924

   (34) https://bugs.python.org/issue33906

   (35) https://bugs.python.org/issue33917

   (36) https://bugs.python.org/issue33904

   (37) https://bugs.python.org/issue33907

   (38) https://bugs.python.org/issue33856

   (39) https://bugs.python.org/issue33839

   (40) https://bugs.python.org/issue33855

   (41) https://bugs.python.org/issue33656

   (42) https://bugs.python.org/issue33768

   (43) https://bugs.python.org/issue33763

   (44) https://bugs.python.org/issue33664

   (45) https://bugs.python.org/issue33679

   (46) https://bugs.python.org/issue33642

   (47) https://bugs.python.org/issue33628

   (48) https://bugs.python.org/issue33564

   (49) https://bugs.python.org/issue21474

   (50) https://bugs.python.org/issue33204

   (51) https://bugs.python.org/issue32984

   (52) https://bugs.python.org/issue32940

   (53) https://bugs.python.org/issue32916

   (54) https://bugs.python.org/issue32905

   (55) https://bugs.python.org/issue32874

   (56) https://bugs.python.org/issue32837

   (57) https://bugs.python.org/issue32826

   (58) https://bugs.python.org/issue32831

   (59) https://bugs.python.org/issue32765


File: python.info,  Node: Tools/Demos<12>,  Next: C API<15>,  Prev: IDLE<27>,  Up: Python 3 8 0 alpha 1

1.18.29.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/issue35884

   (2) https://bugs.python.org/issue34989

   (3) https://bugs.python.org/issue20260

   (4) https://bugs.python.org/issue32962

   (5) https://bugs.python.org/issue32962

   (6) https://bugs.python.org/issue33189

   (7) https://bugs.python.org/issue31920

   (8) https://bugs.python.org/issue29673

   (9) https://bugs.python.org/issue25427

   (10) https://bugs.python.org/issue32885

   (11) https://bugs.python.org/issue32222

   (12) https://bugs.python.org/issue31583


File: python.info,  Node: C API<15>,  Prev: Tools/Demos<12>,  Up: Python 3 8 0 alpha 1

1.18.29.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(): 104f. for empty bytes
     objects.

   - bpo-35322(3): Fix memory leak in *note PyUnicode_EncodeLocale():
     444. and *note PyUnicode_EncodeFSDefault(): 1050. on error
     handling.

   - bpo-35059(4): The following C macros have been converted to static
     inline functions: *note Py_INCREF(): 266, *note Py_DECREF(): 267,
     *note Py_XINCREF(): 268, *note Py_XDECREF(): 269,
     ‘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(): 5ce.
     (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(): 1051. 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: 600. in *note
     PyArg_ParseTupleAndKeywords(): 5cf. 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():
     1052, *note PySequence_GetItem(): 1053, *note PySequence_SetItem():
     1054. and *note PySequence_DelItem(): 1055. called with a mapping
     and *note PyMapping_Size(): 1056. 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(): 1057. and *note
     PyUnicode_AsWideCharString(): 43d. no longer cache the ‘wchar_t*’
     representation of string objects.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35713

   (2) https://bugs.python.org/issue33817

   (3) https://bugs.python.org/issue35322

   (4) https://bugs.python.org/issue35059

   (5) https://bugs.python.org/issue35296

   (6) https://bugs.python.org/issue35081

   (7) https://bugs.python.org/issue35259

   (8) https://bugs.python.org/issue35081

   (9) https://bugs.python.org/issue35134

   (10) https://bugs.python.org/issue34725

   (11) https://bugs.python.org/issue34910

   (12) https://bugs.python.org/issue34523

   (13) https://bugs.python.org/issue34193

   (14) https://bugs.python.org/issue34127

   (15) https://bugs.python.org/issue23927

   (16) https://bugs.python.org/issue32455

   (17) https://bugs.python.org/issue34008

   (18) https://bugs.python.org/issue32500

   (19) https://bugs.python.org/issue33818

   (20) https://bugs.python.org/issue33042

   (21) https://bugs.python.org/issue32374

   (22) https://bugs.python.org/issue30863


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.18.30 Python 3.7.0 final
--------------------------

`Release date: 2018-06-27'

* Menu:

* Library: Library<29>.
* C API: C API<16>.


File: python.info,  Node: Library<29>,  Next: C API<16>,  Up: Python 3 7 0 final

1.18.30.1 Library
.................

   - bpo-33851(1): Fix *note ast.get_docstring(): 105a. for a node that
     lacks a docstring.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33851


File: python.info,  Node: C API<16>,  Prev: Library<29>,  Up: Python 3 7 0 final

1.18.30.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/issue33932


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.18.31 Python 3.7.0 release candidate 1
----------------------------------------

`Release date: 2018-06-12'

* Menu:

* Core and Builtins: Core and Builtins<29>.
* Library: Library<30>.
* Documentation: Documentation<25>.
* Build: Build<18>.
* Windows: Windows<22>.
* IDLE: IDLE<28>.


File: python.info,  Node: Core and Builtins<29>,  Next: Library<30>,  Up: Python 3 7 0 release candidate 1

1.18.31.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/issue33803

   (2) https://bugs.python.org/issue33706

   (3) https://bugs.python.org/issue30654

   (4) https://bugs.python.org/issue31849


File: python.info,  Node: Library<30>,  Next: Documentation<25>,  Prev: Core and Builtins<29>,  Up: Python 3 7 0 release candidate 1

1.18.31.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: 193. instead of
     *note SystemError: 600. when performed on *note mmap.mmap: 1ed.
     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/issue30167

   (2) https://bugs.python.org/issue33812

   (3) https://bugs.python.org/issue30805

   (4) https://bugs.python.org/issue33694

   (5) https://bugs.python.org/issue32493

   (6) https://bugs.python.org/issue33792

   (7) https://bugs.python.org/issue33778

   (8) https://bugs.python.org/issue33770

   (9) https://bugs.python.org/issue33769

   (10) https://bugs.python.org/issue33767

   (11) https://bugs.python.org/issue33734

   (12) https://bugs.python.org/issue11874

   (13) https://bugs.python.org/issue33582


File: python.info,  Node: Documentation<25>,  Next: Build<18>,  Prev: Library<30>,  Up: Python 3 7 0 release candidate 1

1.18.31.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(): 368, *note asyncio.start_server(): 369.
     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/issue33409

   (2) https://www.python.org/dev/peps/pep-0538

   (3) https://bugs.python.org/issue33736

   (4) https://bugs.python.org/issue31432


File: python.info,  Node: Build<18>,  Next: Windows<22>,  Prev: Documentation<25>,  Up: Python 3 7 0 release candidate 1

1.18.31.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/issue5755


File: python.info,  Node: Windows<22>,  Next: IDLE<28>,  Prev: Build<18>,  Up: Python 3 7 0 release candidate 1

1.18.31.5 Windows
.................

   - bpo-33720(1): Reduces maximum marshal recursion depth on release
     builds.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33720


File: python.info,  Node: IDLE<28>,  Prev: Windows<22>,  Up: Python 3 7 0 release candidate 1

1.18.31.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/issue33656

   (2) https://bugs.python.org/issue33768

   (3) https://bugs.python.org/issue33763

   (4) https://bugs.python.org/issue33664

   (5) https://bugs.python.org/issue33679

   (6) https://bugs.python.org/issue33642


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.18.32 Python 3.7.0 beta 5
---------------------------

`Release date: 2018-05-30'

* Menu:

* Core and Builtins: Core and Builtins<30>.
* Library: Library<31>.
* Documentation: Documentation<26>.
* Tests: Tests<21>.
* Build: Build<19>.
* macOS: macOS<16>.
* IDLE: IDLE<29>.


File: python.info,  Node: Core and Builtins<30>,  Next: Library<31>,  Up: Python 3 7 0 beta 5

1.18.32.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: b45. list.  ‘PyGC_Collect()’ 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 *note os.posix_spawn: 258. 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 *note ctypes.cast(): 1018. in case the
     type argument is a ctypes structured data type.  Patch by Eryk Sun
     and Oren Milman.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33622

   (2) https://bugs.python.org/issue33509

   (3) https://bugs.python.org/issue20104

   (4) https://bugs.python.org/issue33475

   (5) https://bugs.python.org/issue33391

   (6) https://bugs.python.org/issue28055

   (7) https://bugs.python.org/issue32911

   (8) https://bugs.python.org/issue29463

   (9) https://bugs.python.org/issue21983


File: python.info,  Node: Library<31>,  Next: Documentation<26>,  Prev: Core and Builtins<30>,  Up: Python 3 7 0 beta 5

1.18.32.2 Library
.................

   - bpo-32751(1): When cancelling the task due to a timeout, *note
     asyncio.wait_for(): 289. 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(): 418. 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 *note typing.Union:
     1039.  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:
     f1.

   - 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 *note typing.get_type_hints(): 30f. 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 Dong-hee 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: 2b.  Patch by
     Segev Finer.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32751

   (2) https://bugs.python.org/issue32684

   (3) https://bugs.python.org/issue33654

   (4) https://bugs.python.org/issue33674

   (5) https://bugs.python.org/issue33674

   (6) https://bugs.python.org/issue31647

   (7) https://bugs.python.org/issue32610

   (8) https://bugs.python.org/issue32410

   (9) https://bugs.python.org/issue33469

   (10) https://bugs.python.org/issue33672

   (11) https://bugs.python.org/issue33654

   (12) https://bugs.python.org/issue33652

   (13) https://bugs.python.org/issue32493

   (14) https://bugs.python.org/issue33618

   (15) https://bugs.python.org/issue33623

   (16) https://bugs.python.org/issue30877

   (17) https://bugs.python.org/issue33570

   (18) https://bugs.python.org/issue28556

   (19) https://bugs.python.org/issue33540

   (20) https://bugs.python.org/issue33548

   (21) https://bugs.python.org/issue33109

   (22) https://bugs.python.org/issue26510

   (23) https://bugs.python.org/issue33536

   (24) https://bugs.python.org/issue33542

   (25) https://bugs.python.org/issue26819

   (26) https://bugs.python.org/issue33505

   (27) https://bugs.python.org/issue33497

   (28) https://bugs.python.org/issue33495

   (29) https://bugs.python.org/issue33453

   (30) https://bugs.python.org/issue28556

   (31) https://bugs.python.org/issue20087

   (32) https://bugs.python.org/issue33422

   (33) https://bugs.python.org/issue28167

   (34) https://bugs.python.org/issue33197

   (35) https://bugs.python.org/issue33263

   (36) https://bugs.python.org/issue32861

   (37) https://bugs.python.org/issue32257

   (38) https://bugs.python.org/issue16865


File: python.info,  Node: Documentation<26>,  Next: Tests<21>,  Prev: Library<31>,  Up: Python 3 7 0 beta 5

1.18.32.3 Documentation
.......................

   - bpo-23859(1): Document that *note asyncio.wait(): 28a. 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/issue23859

   (2) https://bugs.python.org/issue32436

   (3) https://www.python.org/dev/peps/pep-0567

   (4) https://bugs.python.org/issue33604

   (5) https://bugs.python.org/issue33503

   (6) https://bugs.python.org/issue33421


File: python.info,  Node: Tests<21>,  Next: Build<19>,  Prev: Documentation<26>,  Up: Python 3 7 0 beta 5

1.18.32.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/issue33655

   (2) https://bugs.python.org/issue32604


File: python.info,  Node: Build<19>,  Next: macOS<16>,  Prev: Tests<21>,  Up: Python 3 7 0 beta 5

1.18.32.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/issue33614

   (2) https://bugs.python.org/issue33522

   (3) https://bugs.python.org/issue33012


File: python.info,  Node: macOS<16>,  Next: IDLE<29>,  Prev: Build<19>,  Up: Python 3 7 0 beta 5

1.18.32.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/issue13631


File: python.info,  Node: IDLE<29>,  Prev: macOS<16>,  Up: Python 3 7 0 beta 5

1.18.32.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/issue33628

   (2) https://bugs.python.org/issue33564

   (3) https://bugs.python.org/issue32831


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.18.33 Python 3.7.0 beta 4
---------------------------

`Release date: 2018-05-02'

* Menu:

* Core and Builtins: Core and Builtins<31>.
* Library: Library<32>.
* Documentation: Documentation<27>.
* Tests: Tests<22>.
* Build: Build<20>.
* Windows: Windows<23>.
* macOS: macOS<17>.
* IDLE: IDLE<30>.
* Tools/Demos: Tools/Demos<13>.


File: python.info,  Node: Core and Builtins<31>,  Next: Library<32>,  Up: Python 3 7 0 beta 4

1.18.33.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/issue33363

   (2) https://bugs.python.org/issue33128

   (3) https://bugs.python.org/issue33312

   (4) https://bugs.python.org/issue33231

   (5) https://bugs.python.org/issue33205

   (6) https://bugs.python.org/issue29922

   (7) https://bugs.python.org/issue33199


File: python.info,  Node: Library<32>,  Next: Documentation<27>,  Prev: Core and Builtins<31>,  Up: Python 3 7 0 beta 4

1.18.33.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: 35. 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: 103d.

   - bpo-33131(5): Upgrade bundled version of pip to 10.0.1.

   - bpo-33308(6): Fixed a crash in the *note parser: c8. 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(): 103e. and
     *note importlib.abc.ResourceReader.contents(): 103f. return an
     *note iterable: bb1. instead of an *note iterator: 1040.

   - 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: 33c. 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: 48d. when necessary, rather than
     adding ‘"."’.

   - bpo-33169(13): Delete entries of ‘None’ in *note
     sys.path_importer_cache: 4a2. 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: 193. 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(): 1041.

   - bpo-20104(19): Improved error handling and fixed a reference leak
     in *note os.posix_spawn(): 258.

   - 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/issue33281

   (2) https://bugs.python.org/issue33383

   (3) https://bugs.python.org/issue33329

   (4) https://bugs.python.org/issue991266

   (5) https://bugs.python.org/issue33131

   (6) https://bugs.python.org/issue33308

   (7) https://bugs.python.org/issue33266

   (8) https://bugs.python.org/issue11594

   (9) https://bugs.python.org/issue33254

   (10) https://bugs.python.org/issue33256

   (11) https://bugs.python.org/issue33185

   (12) https://bugs.python.org/issue33053

   (13) https://bugs.python.org/issue33169

   (14) https://bugs.python.org/issue33217

   (15) https://bugs.python.org/issue33203

   (16) https://bugs.python.org/issue33224

   (17) https://www.python.org/dev/peps/pep-0479

   (18) https://bugs.python.org/issue33209

   (19) https://bugs.python.org/issue20104

   (20) https://bugs.python.org/issue33175

   (21) https://bugs.python.org/issue33097

   (22) https://bugs.python.org/issue31908


File: python.info,  Node: Documentation<27>,  Next: Tests<22>,  Prev: Library<32>,  Up: Python 3 7 0 beta 4

1.18.33.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/issue33378

   (2) https://bugs.python.org/issue33276

   (3) https://bugs.python.org/issue33201

   (4) https://bugs.python.org/issue33195

   (5) https://bugs.python.org/issue8243

   (6) https://bugs.python.org/issue32337


File: python.info,  Node: Tests<22>,  Next: Build<20>,  Prev: Documentation<27>,  Up: Python 3 7 0 beta 4

1.18.33.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/issue33358


File: python.info,  Node: Build<20>,  Next: Windows<23>,  Prev: Tests<22>,  Up: Python 3 7 0 beta 4

1.18.33.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/issue33394

   (2) https://bugs.python.org/issue33393

   (3) https://bugs.python.org/issue33377

   (4) https://bugs.python.org/issue32232

   (5) https://bugs.python.org/issue33182


File: python.info,  Node: Windows<23>,  Next: macOS<17>,  Prev: Build<20>,  Up: Python 3 7 0 beta 4

1.18.33.6 Windows
.................

   - bpo-33184(1): Update Windows installer to use OpenSSL 1.1.0h.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33184


File: python.info,  Node: macOS<17>,  Next: IDLE<30>,  Prev: Windows<23>,  Up: Python 3 7 0 beta 4

1.18.33.7 macOS
...............

   - bpo-33184(1): Update macOS installer build to use OpenSSL 1.1.0h.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33184


File: python.info,  Node: IDLE<30>,  Next: Tools/Demos<13>,  Prev: macOS<17>,  Up: Python 3 7 0 beta 4

1.18.33.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/issue21474

   (2) https://bugs.python.org/issue33204


File: python.info,  Node: Tools/Demos<13>,  Prev: IDLE<30>,  Up: Python 3 7 0 beta 4

1.18.33.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/issue33189

   (2) https://bugs.python.org/issue31920

   (3) https://bugs.python.org/issue29673

   (4) https://bugs.python.org/issue31583


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.18.34 Python 3.7.0 beta 3
---------------------------

`Release date: 2018-03-29'

* Menu:

* Security: Security<21>.
* Core and Builtins: Core and Builtins<32>.
* Library: Library<33>.
* Documentation: Documentation<28>.
* Tests: Tests<23>.
* Build: Build<21>.
* Windows: Windows<24>.
* macOS: macOS<18>.
* IDLE: IDLE<31>.
* Tools/Demos: Tools/Demos<14>.
* C API: C API<17>.


File: python.info,  Node: Security<21>,  Next: Core and Builtins<32>,  Up: Python 3 7 0 beta 3

1.18.34.1 Security
..................

   - bpo-33136(1): Harden ssl module against LibreSSL CVE-2018-8970.
     X509_VERIFY_PARAM_set1_host() is called with an explicit namelen.
     A new test ensures that NULL bytes are not allowed.

   - bpo-33001(2): Minimal fix to prevent buffer overrun in os.symlink
     on Windows

   - bpo-32981(3): 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 and CVE-2018-1061.  Patch by Jamie Davis.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33136

   (2) https://bugs.python.org/issue33001

   (3) https://bugs.python.org/issue32981


File: python.info,  Node: Core and Builtins<32>,  Next: Library<33>,  Prev: Security<21>,  Up: Python 3 7 0 beta 3

1.18.34.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/issue33053

   (2) https://bugs.python.org/issue33018

   (3) https://bugs.python.org/issue33041

   (4) https://bugs.python.org/issue33026

   (5) https://bugs.python.org/issue33005

   (6) https://bugs.python.org/issue17288

   (7) https://bugs.python.org/issue32836


File: python.info,  Node: Library<33>,  Next: Documentation<28>,  Prev: Core and Builtins<32>,  Up: Python 3 7 0 beta 3

1.18.34.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: a3. 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 *note
     aifc: 5, *note wave: 128. and *note sunau: fb.

   - 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: 10d, ‘after_cancel(None)’ now
     raises a *note ValueError: 1fc. 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: 3dd. now exposes a *note
     backup: 3de. method, if the underlying SQLite library is at version
     3.6.11 or higher.  Patch by Lele Gaifax.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33141

   (2) https://bugs.python.org/issue33096

   (3) https://bugs.python.org/issue32873

   (4) https://bugs.python.org/issue33134

   (5) https://bugs.python.org/issue33127

   (6) https://bugs.python.org/issue32505

   (7) https://bugs.python.org/issue33078

   (8) https://bugs.python.org/issue33116

   (9) https://bugs.python.org/issue32896

   (10) https://bugs.python.org/issue33100

   (11) https://bugs.python.org/issue32953

   (12) https://bugs.python.org/issue33061

   (13) https://bugs.python.org/issue33078

   (14) https://bugs.python.org/issue33064

   (15) https://bugs.python.org/issue33056

   (16) https://bugs.python.org/issue33021

   (17) https://bugs.python.org/issue31804

   (18) https://bugs.python.org/issue33037

   (19) https://bugs.python.org/issue27683

   (20) https://bugs.python.org/issue32999

   (21) https://bugs.python.org/issue33009

   (22) https://bugs.python.org/issue32969

   (23) https://bugs.python.org/issue32056

   (24) https://bugs.python.org/issue32844

   (25) https://bugs.python.org/issue32857

   (26) https://bugs.python.org/issue31639

   (27) https://bugs.python.org/issue27645


File: python.info,  Node: Documentation<28>,  Next: Tests<23>,  Prev: Library<33>,  Up: Python 3 7 0 beta 3

1.18.34.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: 142. 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/issue33126

   (2) https://bugs.python.org/issue27212

   (3) https://bugs.python.org/issue28247

   (4) https://bugs.python.org/issue18802

   (5) https://bugs.python.org/issue27428


File: python.info,  Node: Tests<23>,  Next: Build<21>,  Prev: Documentation<28>,  Up: Python 3 7 0 beta 3

1.18.34.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/issue32872

   (2) https://bugs.python.org/issue32517

   (3) https://bugs.python.org/issue19417


File: python.info,  Node: Build<21>,  Next: Windows<24>,  Prev: Tests<23>,  Up: Python 3 7 0 beta 3

1.18.34.6 Build
...............

   - bpo-33163(1): Upgrade pip to 9.0.3 and setuptools to v39.0.1.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33163


File: python.info,  Node: Windows<24>,  Next: macOS<18>,  Prev: Build<21>,  Up: Python 3 7 0 beta 3

1.18.34.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/issue33016

   (2) https://bugs.python.org/issue32903


File: python.info,  Node: macOS<18>,  Next: IDLE<31>,  Prev: Windows<24>,  Up: Python 3 7 0 beta 3

1.18.34.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/issue32726


File: python.info,  Node: IDLE<31>,  Next: Tools/Demos<14>,  Prev: macOS<18>,  Up: Python 3 7 0 beta 3

1.18.34.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: 8ea.; ‘-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/issue32984

   (2) https://bugs.python.org/issue32940


File: python.info,  Node: Tools/Demos<14>,  Next: C API<17>,  Prev: IDLE<31>,  Up: Python 3 7 0 beta 3

1.18.34.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/issue32885


File: python.info,  Node: C API<17>,  Prev: Tools/Demos<14>,  Up: Python 3 7 0 beta 3

1.18.34.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/issue33042

   (2) https://bugs.python.org/issue32374


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.18.35 Python 3.7.0 beta 2
---------------------------

`Release date: 2018-02-27'

* Menu:

* Security: Security<22>.
* Core and Builtins: Core and Builtins<33>.
* Library: Library<34>.
* Documentation: Documentation<29>.
* Tests: Tests<24>.
* Build: Build<22>.
* Windows: Windows<25>.
* macOS: macOS<19>.
* IDLE: IDLE<32>.
* Tools/Demos: Tools/Demos<15>.


File: python.info,  Node: Security<22>,  Next: Core and Builtins<33>,  Up: Python 3 7 0 beta 2

1.18.35.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/issue28414


File: python.info,  Node: Core and Builtins<33>,  Next: Library<34>,  Prev: Security<22>,  Up: Python 3 7 0 beta 2

1.18.35.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/issue32889

   (2) https://bugs.python.org/issue31356

   (3) https://bugs.python.org/issue31356

   (4) https://bugs.python.org/issue32305

   (5) https://bugs.python.org/issue32303

   (6) https://bugs.python.org/issue32711

   (7) https://bugs.python.org/issue32583


File: python.info,  Node: Library<34>,  Next: Documentation<29>,  Prev: Core and Builtins<33>,  Up: Python 3 7 0 beta 2

1.18.35.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: 279. when using or
     importing an ABC directly from *note collections: 1e. rather than
     from *note collections.abc: 1f.

   - 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 *note asyncio.Condition: 28e. 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(): 1042. 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://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: 110.
     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/issue32960

   (2) https://bugs.python.org/issue32713

   (3) https://bugs.python.org/issue32951

   (4) https://bugs.python.org/issue32929

   (5) https://bugs.python.org/issue32947

   (6) https://bugs.python.org/issue30622

   (7) https://bugs.python.org/issue32922

   (8) https://bugs.python.org/issue32859

   (9) https://bugs.python.org/issue32556

   (10) https://bugs.python.org/issue25988

   (11) https://bugs.python.org/issue21060

   (12) https://bugs.python.org/issue32852

   (13) https://bugs.python.org/issue31333

   (14) https://bugs.python.org/issue32841

   (15) https://bugs.python.org/issue32819

   (16) https://bugs.python.org/issue32394

   (17) https://bugs.python.org/issue31787

   (18) https://bugs.python.org/issue30157

   (19) https://bugs.python.org/issue32792

   (20) https://bugs.python.org/issue32775

   (21) https://bugs.python.org/issue32622

   (22) https://bugs.python.org/issue32777

   (23) https://bugs.python.org/issue32647

   (24) https://bugs.python.org/issue32741

   (25) https://bugs.python.org/issue32691

   (26) https://bugs.python.org/issue32734

   (27) https://bugs.python.org/issue32727

   (28) https://bugs.python.org/issue31453

   (29) https://bugs.python.org/issue24334

   (30) https://bugs.python.org/issue31848

   (31) https://bugs.python.org/issue32585

   (32) https://bugs.python.org/issue32221

   (33) https://bugs.python.org/issue30693

   (34) https://bugs.python.org/issue30693


File: python.info,  Node: Documentation<29>,  Next: Tests<24>,  Prev: Library<34>,  Up: Python 3 7 0 beta 2

1.18.35.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: 107. documentation.

   - bpo-8722(6): Document *note __getattr__(): 31f. behavior when
     property ‘get()’ method raises *note AttributeError: 3a0.

   - bpo-32614(7): Modify RE examples in documentation to use raw
     strings to prevent *note DeprecationWarning: 279. and add text to
     REGEX HOWTO to highlight the deprecation.

   - bpo-31972(8): Improve docstrings for *note pathlib.PurePath: 1046.
     subclasses.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28124

   (2) https://bugs.python.org/issue17232

   (3) https://bugs.python.org/issue32436

   (4) https://bugs.python.org/issue32800

   (5) https://bugs.python.org/issue11015

   (6) https://bugs.python.org/issue8722

   (7) https://bugs.python.org/issue32614

   (8) https://bugs.python.org/issue31972


File: python.info,  Node: Tests<24>,  Next: Build<22>,  Prev: Documentation<29>,  Up: Python 3 7 0 beta 2

1.18.35.5 Tests
...............

   - bpo-31809(1): Add tests to verify connection with secp ECDH curves.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31809


File: python.info,  Node: Build<22>,  Next: Windows<25>,  Prev: Tests<24>,  Up: Python 3 7 0 beta 2

1.18.35.6 Build
...............

   - bpo-32898(1): Fix the python debug build when using COUNT_ALLOCS.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32898


File: python.info,  Node: Windows<25>,  Next: macOS<19>,  Prev: Build<22>,  Up: Python 3 7 0 beta 2

1.18.35.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(): 1f4. 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/issue32901

   (2) https://bugs.python.org/issue31966

   (3) https://bugs.python.org/issue32409

   (4) https://bugs.python.org/issue32457

   (5) https://bugs.python.org/issue32370

   (6) https://bugs.python.org/issue29248


File: python.info,  Node: macOS<19>,  Next: IDLE<32>,  Prev: Windows<25>,  Up: Python 3 7 0 beta 2

1.18.35.8 macOS
...............

   - bpo-32901(1): Update macOS 10.9+ installer to Tcl/Tk 8.6.8.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32901


File: python.info,  Node: IDLE<32>,  Next: Tools/Demos<15>,  Prev: macOS<19>,  Up: Python 3 7 0 beta 2

1.18.35.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/issue32916

   (2) https://bugs.python.org/issue32905

   (3) https://bugs.python.org/issue32874

   (4) https://bugs.python.org/issue32837

   (5) https://bugs.python.org/issue32826

   (6) https://bugs.python.org/issue32765


File: python.info,  Node: Tools/Demos<15>,  Prev: IDLE<32>,  Up: Python 3 7 0 beta 2

1.18.35.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/issue32222


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.18.36 Python 3.7.0 beta 1
---------------------------

`Release date: 2018-01-30'

* Menu:

* Core and Builtins: Core and Builtins<34>.
* Library: Library<35>.
* Documentation: Documentation<30>.
* Tests: Tests<25>.
* Build: Build<23>.
* Windows: Windows<26>.
* macOS: macOS<20>.
* C API: C API<18>.


File: python.info,  Node: Core and Builtins<34>,  Next: Library<35>,  Up: Python 3 7 0 beta 1

1.18.36.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/issue32703

   (2) https://bugs.python.org/issue32650

   (3) https://bugs.python.org/issue28685

   (4) https://bugs.python.org/issue32685

   (5) https://bugs.python.org/issue32697

   (6) https://bugs.python.org/issue32690

   (7) https://bugs.python.org/issue32677

   (8) https://bugs.python.org/issue32670

   (9) https://www.python.org/dev/peps/pep-0479

   (10) https://bugs.python.org/issue32591

   (11) https://bugs.python.org/issue31368

   (12) https://bugs.python.org/issue32544

   (13) https://bugs.python.org/issue26163

   (14) https://bugs.python.org/issue32550

   (15) https://bugs.python.org/issue20104

   (16) https://bugs.python.org/issue24340

   (17) https://bugs.python.org/issue32436

   (18) https://www.python.org/dev/peps/pep-0567

   (19) https://bugs.python.org/issue18533

   (20) https://bugs.python.org/issue20891

   (21) https://bugs.python.org/issue32028

   (22) https://bugs.python.org/issue31179

   (23) https://bugs.python.org/issue31113


File: python.info,  Node: Library<35>,  Next: Documentation<30>,  Prev: Core and Builtins<34>,  Up: Python 3 7 0 beta 1

1.18.36.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: 105. 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:
     108f. 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():
     35b. and *note asyncio.StreamWriter.is_closing(): 35c. 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(): 1090. did not call __new__ in
     *note datetime.datetime: 195. subclasses.

   - bpo-32403(35): Improved speed of *note datetime.date: 194. and
     *note datetime.datetime: 195. 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: 9f. and *note
     importlib.abc.ResourceReader: 347. 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: 46b. 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: 36f.  If
     `args' is given as a sequence, it’s first element can now be a
     *note path-like object: 36f. as well.

   - bpo-31900(44): The *note locale.localeconv(): 48f. 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():
     4df. method when formatting a number (*note int: 185, *note float:
     188, *note float: 188. 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/issue25988

   (2) https://bugs.python.org/issue31429

   (3) https://bugs.python.org/issue30306

   (4) https://bugs.python.org/issue21417

   (5) https://bugs.python.org/issue32251

   (6) https://bugs.python.org/issue32513

   (7) https://bugs.python.org/issue32660

   (8) https://bugs.python.org/issue27931

   (9) https://bugs.python.org/issue32659

   (10) https://bugs.python.org/issue32662

   (11) https://bugs.python.org/issue32391

   (12) https://bugs.python.org/issue32643

   (13) https://bugs.python.org/issue32630

   (14) https://bugs.python.org/issue32622

   (15) https://bugs.python.org/issue32304

   (16) https://bugs.python.org/issue32502

   (17) https://bugs.python.org/issue32596

   (18) https://www.python.org/dev/peps/pep-0562

   (19) https://bugs.python.org/issue31801

   (20) https://bugs.python.org/issue32576

   (21) https://bugs.python.org/issue32574

   (22) https://bugs.python.org/issue32521

   (23) https://bugs.python.org/issue32467

   (24) https://bugs.python.org/issue32473

   (25) https://bugs.python.org/issue32102

   (26) https://bugs.python.org/issue32521

   (27) https://bugs.python.org/issue32493

   (28) https://bugs.python.org/issue32503

   (29) https://bugs.python.org/issue29237

   (30) https://bugs.python.org/issue32454

   (31) https://bugs.python.org/issue25942

   (32) https://bugs.python.org/issue32433

   (33) https://bugs.python.org/issue28134

   (34) https://bugs.python.org/issue32404

   (35) https://bugs.python.org/issue32403

   (36) https://bugs.python.org/issue32228

   (37) https://bugs.python.org/issue32410

   (38) https://bugs.python.org/issue22908

   (39) https://bugs.python.org/issue32373

   (40) https://bugs.python.org/issue32248

   (41) https://bugs.python.org/issue32320

   (42) https://bugs.python.org/issue29302

   (43) https://bugs.python.org/issue31961

   (44) https://bugs.python.org/issue31900

   (45) https://bugs.python.org/issue31853

   (46) https://bugs.python.org/issue31399

   (47) https://bugs.python.org/issue14976


File: python.info,  Node: Documentation<30>,  Next: Tests<25>,  Prev: Library<35>,  Up: Python 3 7 0 beta 1

1.18.36.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/issue32724

   (2) https://bugs.python.org/issue32649

   (3) https://bugs.python.org/issue17799


File: python.info,  Node: Tests<25>,  Next: Build<23>,  Prev: Documentation<30>,  Up: Python 3 7 0 beta 1

1.18.36.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/issue32721

   (2) https://bugs.python.org/issue28414

   (3) https://bugs.python.org/issue31399

   (4) https://bugs.python.org/issue32604

   (5) https://bugs.python.org/issue32602

   (6) https://bugs.python.org/issue32549


File: python.info,  Node: Build<23>,  Next: Windows<26>,  Prev: Tests<25>,  Up: Python 3 7 0 beta 1

1.18.36.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: d8. will always create hash-based ‘.pyc’
     files.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32635

   (2) https://bugs.python.org/issue32598

   (3) https://bugs.python.org/issue32593

   (4) https://bugs.python.org/issue29708


File: python.info,  Node: Windows<26>,  Next: macOS<20>,  Prev: Build<23>,  Up: Python 3 7 0 beta 1

1.18.36.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/issue32588

   (2) https://bugs.python.org/issue29911

   (3) https://bugs.python.org/issue32507


File: python.info,  Node: macOS<20>,  Next: C API<18>,  Prev: Windows<26>,  Up: Python 3 7 0 beta 1

1.18.36.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/issue32726

   (2) https://bugs.python.org/issue28440


File: python.info,  Node: C API<18>,  Prev: macOS<20>,  Up: Python 3 7 0 beta 1

1.18.36.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/issue32681

   (2) https://bugs.python.org/issue10381


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.18.37 Python 3.7.0 alpha 4
----------------------------

`Release date: 2018-01-08'

* Menu:

* Core and Builtins: Core and Builtins<35>.
* Library: Library<36>.
* Documentation: Documentation<31>.
* Tests: Tests<26>.
* Windows: Windows<27>.
* Tools/Demos: Tools/Demos<16>.
* C API: C API<19>.


File: python.info,  Node: Core and Builtins<35>,  Next: Library<36>,  Up: Python 3 7 0 alpha 4

1.18.37.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: 1099. option now turns on hash
     randomization when the *note PYTHONHASHSEED: 9ca. 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 *note atexit: c. 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/issue31975

   (2) https://bugs.python.org/issue32226

   (3) https://bugs.python.org/issue32399

   (4) https://bugs.python.org/issue32390

   (5) https://bugs.python.org/issue32143

   (6) https://bugs.python.org/issue32379

   (7) https://bugs.python.org/issue32259

   (8) https://bugs.python.org/issue27169

   (9) https://bugs.python.org/issue22091

   (10) https://bugs.python.org/issue32329

   (11) https://bugs.python.org/issue30416

   (12) https://bugs.python.org/issue32282

   (13) https://bugs.python.org/issue30579

   (14) https://bugs.python.org/issue32260

   (15) https://bugs.python.org/issue31506

   (16) https://bugs.python.org/issue20361

   (17) https://bugs.python.org/issue32230

   (18) https://bugs.python.org/issue29240

   (19) https://www.python.org/dev/peps/pep-0540

   (20) https://bugs.python.org/issue32226

   (21) https://www.python.org/dev/peps/pep-0560

   (22) https://bugs.python.org/issue32225

   (23) https://www.python.org/dev/peps/pep-0562

   (24) https://bugs.python.org/issue31901

   (25) https://bugs.python.org/issue31650

   (26) https://www.python.org/dev/peps/pep-0552

   (27) https://bugs.python.org/issue29469


File: python.info,  Node: Library<36>,  Next: Documentation<31>,  Prev: Core and Builtins<35>,  Up: Python 3 7 0 alpha 4

1.18.37.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: 347. as an
     ABC for loaders to provide a unified API for reading resources
     contained within packages.  Also add *note importlib.resources: 9f.
     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(): 5fe. 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(): 480. now replaces empty matches
     adjacent to a previous non-empty match.

   - bpo-29970(26): Abort asyncio SSLProtocol connection if handshake
     not complete within 10s

   - 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(): 383, *note
     datetime.time.fromisoformat(): 109b. and *note
     datetime.date.fromisoformat(): 109c. 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: 2a5. 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/issue32506

   (2) https://bugs.python.org/issue32279

   (3) https://bugs.python.org/issue32278

   (4) https://bugs.python.org/issue32499

   (5) https://bugs.python.org/issue32468

   (6) https://bugs.python.org/issue23749

   (7) https://bugs.python.org/issue32441

   (8) https://bugs.python.org/issue32422

   (9) https://bugs.python.org/issue31721

   (10) https://bugs.python.org/issue32415

   (11) https://bugs.python.org/issue26133

   (12) https://bugs.python.org/issue32363

   (13) https://bugs.python.org/issue32357

   (14) https://bugs.python.org/issue32356

   (15) https://bugs.python.org/issue32355

   (16) https://bugs.python.org/issue32351

   (17) https://bugs.python.org/issue32348

   (18) https://bugs.python.org/issue32331

   (19) https://bugs.python.org/issue32248

   (20) https://bugs.python.org/issue32311

   (21) https://bugs.python.org/issue32327

   (22) https://bugs.python.org/issue32323

   (23) https://bugs.python.org/issue32302

   (24) https://bugs.python.org/issue29711

   (25) https://bugs.python.org/issue32308

   (26) https://bugs.python.org/issue29970

   (27) https://bugs.python.org/issue32314

   (28) https://bugs.python.org/issue17852

   (29) https://bugs.python.org/issue32296

   (30) https://bugs.python.org/issue32250

   (31) https://bugs.python.org/issue32255

   (32) https://bugs.python.org/issue32277

   (33) https://bugs.python.org/issue30050

   (34) https://bugs.python.org/issue29137

   (35) https://bugs.python.org/issue32273

   (36) https://bugs.python.org/issue32272

   (37) https://bugs.python.org/issue32269

   (38) https://bugs.python.org/issue32265

   (39) https://bugs.python.org/issue32253

   (40) https://bugs.python.org/issue22589

   (41) https://bugs.python.org/issue32193

   (42) https://bugs.python.org/issue32206

   (43) https://bugs.python.org/issue32227

   (44) https://bugs.python.org/issue15873

   (45) https://bugs.python.org/issue32199

   (46) https://bugs.python.org/issue32143

   (47) https://bugs.python.org/issue26439

   (48) https://bugs.python.org/issue31993

   (49) https://bugs.python.org/issue27456

   (50) https://bugs.python.org/issue31778

   (51) https://bugs.python.org/issue31802

   (52) https://bugs.python.org/issue30241

   (53) https://bugs.python.org/issue31699

   (54) https://bugs.python.org/issue15216


File: python.info,  Node: Documentation<31>,  Next: Tests<26>,  Prev: Library<36>,  Up: Python 3 7 0 alpha 4

1.18.37.3 Documentation
.......................

   - bpo-32418(1): Add get_loop() method to Server and AbstractServer
     classes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32418


File: python.info,  Node: Tests<26>,  Next: Windows<27>,  Prev: Documentation<31>,  Up: Python 3 7 0 alpha 4

1.18.37.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/issue32252

   (2) https://bugs.python.org/issue32002


File: python.info,  Node: Windows<27>,  Next: Tools/Demos<16>,  Prev: Tests<26>,  Up: Python 3 7 0 alpha 4

1.18.37.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/issue19764


File: python.info,  Node: Tools/Demos<16>,  Next: C API<19>,  Prev: Windows<27>,  Up: Python 3 7 0 alpha 4

1.18.37.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/issue24960


File: python.info,  Node: C API<19>,  Prev: Tools/Demos<16>,  Up: Python 3 7 0 alpha 4

1.18.37.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): *note Py_SetProgramName(): f8e. and *note
     Py_SetPythonHome(): f8d. now take the ‘const wchar *’ arguments
     instead of ‘wchar *’.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32030

   (2) https://bugs.python.org/issue29084

   (3) https://bugs.python.org/issue32264

   (4) https://bugs.python.org/issue32241


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.18.38 Python 3.7.0 alpha 3
----------------------------

`Release date: 2017-12-05'

* Menu:

* Core and Builtins: Core and Builtins<36>.
* Library: Library<37>.
* Documentation: Documentation<32>.
* Tests: Tests<27>.
* Build: Build<24>.
* Windows: Windows<28>.
* macOS: macOS<21>.
* IDLE: IDLE<33>.
* Tools/Demos: Tools/Demos<17>.
* C API: C API<20>.


File: python.info,  Node: Core and Builtins<36>,  Next: Library<37>,  Up: Python 3 7 0 alpha 3

1.18.38.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/issue32176

   (2) https://bugs.python.org/issue10544

   (3) https://bugs.python.org/issue32137

   (4) https://bugs.python.org/issue32096

   (5) https://bugs.python.org/issue32043

   (6) https://bugs.python.org/issue32023

   (7) https://bugs.python.org/issue32012

   (8) https://bugs.python.org/issue28180

   (9) https://bugs.python.org/issue31949

   (10) https://bugs.python.org/issue30696

   (11) https://bugs.python.org/issue20047

   (12) https://bugs.python.org/issue21720

   (13) https://bugs.python.org/issue31845

   (14) https://bugs.python.org/issue28936

   (15) https://bugs.python.org/issue31825

   (16) https://bugs.python.org/issue31618

   (17) https://bugs.python.org/issue28603

   (18) https://bugs.python.org/issue31786

   (19) https://bugs.python.org/issue31781

   (20) https://bugs.python.org/issue30399

   (21) https://bugs.python.org/issue31626

   (22) https://bugs.python.org/issue30817


File: python.info,  Node: Library<37>,  Next: Documentation<32>,  Prev: Core and Builtins<36>,  Up: Python 3 7 0 alpha 3

1.18.38.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-321010(8): Add ‘sys.flags.dev_mode’ flag

   - bpo-32154(9): The ‘asyncio.windows_utils.socketpair()’ function has
     been removed: use directly *note socket.socketpair(): 486. 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 *note ssl.match_hostname(): 3e1.  Patch by Mandeep
     Singh.

   - bpo-12239(13): Make *note msilib.SummaryInformation.GetProperty():
     fc8. return ‘None’ when the value of property is ‘VT_EMPTY’.
     Initial patch by Mark Mc Mahon.

   - bpo-28334(14): Use *note os.path.expanduser(): 1ff. to find the
     ‘~/.netrc’ file in *note netrc.netrc: 10a5.  If it does not exist,
     *note FileNotFoundError: 7c5. 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():
     1b8. in the *note RobotFileParser.parse(): 10a6. method.  Initial
     patch by Robin Wellner.

   - bpo-12382(17): *note msilib.OpenDatabase(): f14. 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: 279, *note
     PendingDeprecationWarning: 27a. and *note ImportWarning: 5dd.
     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 Dong-hee Na.

   - bpo-32018(31): inspect.signature should follow PEP 8(32), if the
     parameter has an annotation and a default value.  Patch by Dong-hee
     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: 36f, 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:
     10a7.  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: 3fa, *note time.CLOCK_PROF: 3fc. and *note
     time.CLOCK_UPTIME: 3fd.

   - 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(): 10a8. 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: 3a4. and *note
     ipaddress.IPv4Network: 3a5.  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 *note subprocess: fa. 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: 10b. module: *note
     clock_gettime_ns(): 323, *note clock_settime_ns(): 324, *note
     monotonic_ns(): 325, *note perf_counter_ns(): 326, *note
     process_time_ns(): 327, *note time_ns(): 328.

   - 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(): 10a9.  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: 6e7.  Patch by Vitor Pereira.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28556

   (2) https://bugs.python.org/issue32214

   (3) https://bugs.python.org/issue27240

   (4) https://bugs.python.org/issue30788

   (5) https://bugs.python.org/issue31831

   (6) https://bugs.python.org/issue32182

   (7) https://bugs.python.org/issue32186

   (8) https://bugs.python.org/issue321010

   (9) https://bugs.python.org/issue32154

   (10) https://bugs.python.org/issue32089

   (11) https://bugs.python.org/issue32107

   (12) https://bugs.python.org/issue23033

   (13) https://bugs.python.org/issue12239

   (14) https://bugs.python.org/issue28334

   (15) https://bugs.python.org/issue32121

   (16) https://bugs.python.org/issue31325

   (17) https://bugs.python.org/issue12382

   (18) https://bugs.python.org/issue19610

   (19) https://bugs.python.org/issue32071

   (20) https://bugs.python.org/issue10049

   (21) https://bugs.python.org/issue28684

   (22) https://bugs.python.org/issue32110

   (23) https://bugs.python.org/issue27535

   (24) https://bugs.python.org/issue32088

   (25) https://bugs.python.org/issue1647489

   (26) https://bugs.python.org/issue25054

   (27) https://bugs.python.org/issue32072

   (28) https://bugs.python.org/issue32069

   (29) https://bugs.python.org/issue32066

   (30) https://bugs.python.org/issue32046

   (31) https://bugs.python.org/issue32018

   (32) https://www.python.org/dev/peps/pep-0008

   (33) https://bugs.python.org/issue32025

   (34) https://bugs.python.org/issue32037

   (35) https://bugs.python.org/issue32034

   (36) https://bugs.python.org/issue32015

   (37) https://bugs.python.org/issue32011

   (38) https://bugs.python.org/issue28369

   (39) https://bugs.python.org/issue31976

   (40) https://bugs.python.org/issue31985

   (41) https://bugs.python.org/issue21862

   (42) https://bugs.python.org/issue31970

   (43) https://bugs.python.org/issue31843

   (44) https://bugs.python.org/issue31945

   (45) https://bugs.python.org/issue31943

   (46) https://bugs.python.org/issue9678

   (47) https://bugs.python.org/issue30057

   (48) https://bugs.python.org/issue31933

   (49) https://bugs.python.org/issue21423

   (50) https://bugs.python.org/issue31927

   (51) https://bugs.python.org/issue27666

   (52) https://bugs.python.org/issue31917

   (53) https://bugs.python.org/issue31897

   (54) https://bugs.python.org/issue25720

   (55) https://bugs.python.org/issue31893

   (56) https://bugs.python.org/issue31891

   (57) https://bugs.python.org/issue31884

   (58) https://bugs.python.org/issue28281

   (59) https://bugs.python.org/issue31702

   (60) https://bugs.python.org/issue30639

   (61) https://bugs.python.org/issue30768

   (62) https://www.python.org/dev/peps/pep-0475

   (63) https://bugs.python.org/issue31854

   (64) https://bugs.python.org/issue31834

   (65) https://bugs.python.org/issue28292

   (66) https://bugs.python.org/issue28564

   (67) https://bugs.python.org/issue28416

   (68) https://bugs.python.org/issue31653

   (69) https://bugs.python.org/issue28326

   (70) https://bugs.python.org/issue20825

   (71) https://bugs.python.org/issue31827

   (72) https://bugs.python.org/issue31756

   (73) https://bugs.python.org/issue31819

   (74) https://bugs.python.org/issue31457

   (75) https://bugs.python.org/issue31457

   (76) https://bugs.python.org/issue31806

   (77) https://bugs.python.org/issue31803

   (78) https://bugs.python.org/issue31800

   (79) https://bugs.python.org/issue28603

   (80) https://bugs.python.org/issue30541

   (81) https://bugs.python.org/issue31784

   (82) https://www.python.org/dev/peps/pep-0564

   (83) https://bugs.python.org/issue30143

   (84) https://bugs.python.org/issue31770

   (85) https://bugs.python.org/issue31764

   (86) https://bugs.python.org/issue31752

   (87) https://bugs.python.org/issue31620

   (88) https://bugs.python.org/issue31690

   (89) https://bugs.python.org/issue30349

   (90) https://bugs.python.org/issue31664

   (91) https://bugs.python.org/issue31632

   (92) https://bugs.python.org/issue15037

   (93) https://bugs.python.org/issue31307

   (94) https://bugs.python.org/issue31334

   (95) https://bugs.python.org/issue31310

   (96) https://bugs.python.org/issue31308

   (97) https://bugs.python.org/issue31245

   (98) https://bugs.python.org/issue30553


File: python.info,  Node: Documentation<32>,  Next: Tests<27>,  Prev: Library<37>,  Up: Python 3 7 0 alpha 3

1.18.38.3 Documentation
.......................

   - bpo-32105(1): Added asyncio.BaseEventLoop.connect_accepted_socket
     versionadded marker.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32105


File: python.info,  Node: Tests<27>,  Next: Build<24>,  Prev: Documentation<32>,  Up: Python 3 7 0 alpha 3

1.18.38.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/issue31380

   (2) https://bugs.python.org/issue31705

   (3) https://bugs.python.org/issue32138

   (4) https://bugs.python.org/issue32136

   (5) https://bugs.python.org/issue28668

   (6) https://bugs.python.org/issue32126

   (7) https://bugs.python.org/issue31174


File: python.info,  Node: Build<24>,  Next: Windows<28>,  Prev: Tests<27>,  Up: Python 3 7 0 alpha 3

1.18.38.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/issue28538

   (2) https://bugs.python.org/issue28762

   (3) https://bugs.python.org/issue29040

   (4) https://bugs.python.org/issue32059

   (5) https://bugs.python.org/issue31957

   (6) https://bugs.python.org/issue31609

   (7) https://bugs.python.org/issue31934

   (8) https://bugs.python.org/issue31926

   (9) https://bugs.python.org/issue28791

   (10) https://bugs.python.org/issue28791

   (11) https://bugs.python.org/issue28643

   (12) https://bugs.python.org/issue31866


File: python.info,  Node: Windows<28>,  Next: macOS<21>,  Prev: Build<24>,  Up: Python 3 7 0 alpha 3

1.18.38.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/issue1102

   (2) https://bugs.python.org/issue31944

   (3) https://bugs.python.org/issue20486

   (4) https://bugs.python.org/issue31857


File: python.info,  Node: macOS<21>,  Next: IDLE<33>,  Prev: Windows<28>,  Up: Python 3 7 0 alpha 3

1.18.38.7 macOS
...............

   - bpo-31392(1): Update macOS installer to use OpenSSL 1.0.2m

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31392


File: python.info,  Node: IDLE<33>,  Next: Tools/Demos<17>,  Prev: macOS<21>,  Up: Python 3 7 0 alpha 3

1.18.38.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/issue32207

   (2) https://bugs.python.org/issue32164

   (3) https://bugs.python.org/issue32100

   (4) https://bugs.python.org/issue31858

   (5) https://bugs.python.org/issue31860

   (6) https://bugs.python.org/issue31836

   (7) https://bugs.python.org/issue28603

   (8) https://bugs.python.org/issue13802


File: python.info,  Node: Tools/Demos<17>,  Next: C API<20>,  Prev: IDLE<33>,  Up: Python 3 7 0 alpha 3

1.18.38.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/issue32159

   (2) https://bugs.python.org/issue30722


File: python.info,  Node: C API<20>,  Prev: Tools/Demos<17>,  Up: Python 3 7 0 alpha 3

1.18.38.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/issue20891

   (2) https://bugs.python.org/issue32125

   (3) https://bugs.python.org/issue25612

   (4) https://bugs.python.org/issue23699

   (5) https://bugs.python.org/issue30697

   (6) https://bugs.python.org/issue22898


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.18.39 Python 3.7.0 alpha 2
----------------------------

`Release date: 2017-10-16'

* Menu:

* Core and Builtins: Core and Builtins<37>.
* Library: Library<38>.
* Documentation: Documentation<33>.
* Build: Build<25>.
* IDLE: IDLE<34>.
* C API: C API<21>.


File: python.info,  Node: Core and Builtins<37>,  Next: Library<38>,  Up: Python 3 7 0 alpha 2

1.18.39.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 *note
     zlib.decompress(): 5c4.  Patch by Oren Milman.

   - bpo-31592(8): Fixed an assertion failure in Python parser in case
     of a bad *note unicodedata.normalize(): 10b4.  Patch by Oren
     Milman.

   - bpo-31588(9): Raise a *note TypeError: 193. 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 *note json: a5, 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: 33d. 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 *note
     ctypes._CData: 10b5, 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 *note
     warnings.warn_explicit: 5b5, 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/issue31558

   (2) https://bugs.python.org/issue31642

   (3) https://bugs.python.org/issue31708

   (4) https://bugs.python.org/issue31709

   (5) https://bugs.python.org/issue30404

   (6) https://bugs.python.org/issue31619

   (7) https://bugs.python.org/issue31602

   (8) https://bugs.python.org/issue31592

   (9) https://bugs.python.org/issue31588

   (10) https://bugs.python.org/issue31574

   (11) https://bugs.python.org/issue31566

   (12) https://bugs.python.org/issue31506

   (13) https://bugs.python.org/issue31505

   (14) https://bugs.python.org/issue31492

   (15) https://bugs.python.org/issue31478

   (16) https://bugs.python.org/issue31336

   (17) https://bugs.python.org/issue31415

   (18) https://bugs.python.org/issue31410

   (19) https://bugs.python.org/issue31353

   (20) https://www.python.org/dev/peps/pep-0553

   (21) https://bugs.python.org/issue17852

   (22) https://bugs.python.org/issue31315

   (23) https://bugs.python.org/issue31311

   (24) https://bugs.python.org/issue31293

   (25) https://bugs.python.org/issue31285

   (26) https://bugs.python.org/issue30406

   (27) https://www.python.org/dev/peps/pep-0492


File: python.info,  Node: Library<38>,  Next: Documentation<33>,  Prev: Core and Builtins<37>,  Up: Python 3 7 0 alpha 2

1.18.39.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: 2a5. constructor.  Also,
     free job resources in *note concurrent.futures.ProcessPoolExecutor:
     2a5. 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 (*note bytearray: 337, *note array.array: 456, *note
     collections.deque: 536, *note collections.defaultdict: b3f, *note
     itertools.count: c20, *note itertools.repeat: 10b7.) now contain
     actual type name insteads of hardcoded name 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/issue30058

   (2) https://bugs.python.org/issue31672

   (3) https://bugs.python.org/issue31701

   (4) https://bugs.python.org/issue31728

   (5) https://bugs.python.org/issue31671

   (6) https://bugs.python.org/issue30397

   (7) https://bugs.python.org/issue31675

   (8) https://bugs.python.org/issue31673

   (9) https://bugs.python.org/issue31648

   (10) https://bugs.python.org/issue30806

   (11) https://bugs.python.org/issue31638

   (12) https://bugs.python.org/issue25351

   (13) https://bugs.python.org/issue20519

   (14) https://bugs.python.org/issue28293

   (15) https://bugs.python.org/issue31596

   (16) https://bugs.python.org/issue27494

   (17) https://bugs.python.org/issue30347

   (18) https://bugs.python.org/issue30346

   (19) https://bugs.python.org/issue31556

   (20) https://bugs.python.org/issue31540

   (21) https://bugs.python.org/issue31516

   (22) https://bugs.python.org/issue31525

   (23) https://bugs.python.org/issue26510

   (24) https://bugs.python.org/issue27541

   (25) https://bugs.python.org/issue31351

   (26) https://bugs.python.org/issue31389


File: python.info,  Node: Documentation<33>,  Next: Build<25>,  Prev: Library<38>,  Up: Python 3 7 0 alpha 2

1.18.39.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/issue31537

   (2) https://bugs.python.org/issue30085


File: python.info,  Node: Build<25>,  Next: IDLE<34>,  Prev: Documentation<33>,  Up: Python 3 7 0 alpha 2

1.18.39.4 Build
...............

   - bpo-31696(1): Improve compiler version information in *note
     sys.version: 5d8. 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/issue31696

   (2) https://bugs.python.org/issue31625

   (3) https://bugs.python.org/issue31624

   (4) https://bugs.python.org/issue22140

   (5) https://bugs.python.org/issue31569

   (6) https://bugs.python.org/issue31536


File: python.info,  Node: IDLE<34>,  Next: C API<21>,  Prev: Build<25>,  Up: Python 3 7 0 alpha 2

1.18.39.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/issue31460

   (2) https://bugs.python.org/issue31649

   (3) https://bugs.python.org/issue31559

   (4) https://bugs.python.org/issue31459

   (5) https://bugs.python.org/issue31500

   (6) https://bugs.python.org/issue1612262


File: python.info,  Node: C API<21>,  Prev: IDLE<34>,  Up: Python 3 7 0 alpha 2

1.18.39.6 C API
...............

   - bpo-28280(1): Make ‘PyMapping_Keys()’, ‘PyMapping_Values()’ and
     ‘PyMapping_Items()’ always return a *note list: 263. (rather than a
     *note list: 263. or a *note tuple: 483.).  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/issue28280

   (2) https://bugs.python.org/issue31532

   (3) https://bugs.python.org/issue25658

   (4) https://www.python.org/dev/peps/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.18.40 Python 3.7.0 alpha 1
----------------------------

`Release date: 2017-09-19'

* Menu:

* Security: Security<23>.
* Core and Builtins: Core and Builtins<38>.
* Library: Library<39>.
* Documentation: Documentation<34>.
* Tests: Tests<28>.
* Build: Build<26>.
* Windows: Windows<29>.
* IDLE: IDLE<35>.
* Tools/Demos: Tools/Demos<18>.
* C API: C API<22>.


File: python.info,  Node: Security<23>,  Next: Core and Builtins<38>,  Up: Python 3 7 0 alpha 1

1.18.40.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
     (External entity infinite loop DoS), CVE-2016-9063 (Integer
     overflow, re-fix), CVE-2016-0718 (Fix regression bugs from 2.2.0’s
     fix to CVE-2016-0718) and CVE-2012-0876 (Counter hash flooding with
     SipHash).  Note: the CVE-2016-5300 (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(6): 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(7): Update expat copy from 2.1.1 to 2.2.0 to get fixes of
     CVE-2016-0718 and CVE-2016-4472.  See
     ‘https://sourceforge.net/p/expat/bugs/537/’ for more information.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue29781

   (2) https://bugs.python.org/issue29505

   (3) https://bugs.python.org/issue30947

   (4) https://bugs.python.org/issue30730

   (5) https://bugs.python.org/issue30694

   (6) https://bugs.python.org/issue30500

   (7) https://bugs.python.org/issue29591


File: python.info,  Node: Core and Builtins<38>,  Next: Library<39>,  Prev: Security<23>,  Up: Python 3 7 0 alpha 1

1.18.40.2 Core and Builtins
...........................

   - bpo-31490(1): Fix an assertion failure in *note ctypes: 2b. 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 *note subprocess.Popen():
     2ba. 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 *note
     zipimport.zipimporter.get_data: 10bf. 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
     *note io.TextIOWrapper: 5f8, when the encoder doesn’t return a
     bytes object.  Patch by Oren Milman.

   - bpo-31243(16): Fix a crash in some methods of *note
     io.TextIOWrapper: 5f8, 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 Dong-hee 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: 965.

   - 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(): e42. function, *note cProfile: 28. or *note
     profile: d4. 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/issue31490

   (2) https://bugs.python.org/issue31471

   (3) https://bugs.python.org/issue31418

   (4) https://bugs.python.org/issue31416

   (5) https://bugs.python.org/issue28411

   (6) https://bugs.python.org/issue28411

   (7) https://bugs.python.org/issue31411

   (8) https://bugs.python.org/issue31344

   (9) https://bugs.python.org/issue31373

   (10) https://bugs.python.org/issue30465

   (11) https://bugs.python.org/issue30860

   (12) https://bugs.python.org/issue31347

   (13) https://bugs.python.org/issue31343

   (14) https://bugs.python.org/issue31291

   (15) https://bugs.python.org/issue31271

   (16) https://bugs.python.org/issue31243

   (17) https://bugs.python.org/issue30721

   (18) https://bugs.python.org/issue31070

   (19) https://bugs.python.org/issue30747

   (20) https://bugs.python.org/issue31095

   (21) https://bugs.python.org/issue31071

   (22) https://bugs.python.org/issue30978

   (23) https://bugs.python.org/issue30808

   (24) https://bugs.python.org/issue30876

   (25) https://bugs.python.org/issue30703

   (26) https://bugs.python.org/issue30765

   (27) https://bugs.python.org/issue31161

   (28) https://bugs.python.org/issue30814

   (29) https://bugs.python.org/issue30736

   (30) https://bugs.python.org/issue30604

   (31) https://bugs.python.org/issue30597

   (32) https://bugs.python.org/issue30682

   (33) https://bugs.python.org/issue30501

   (34) https://bugs.python.org/issue28180

   (35) https://www.python.org/dev/peps/pep-0538

   (36) https://bugs.python.org/issue30486

   (37) https://bugs.python.org/issue30537

   (38) https://bugs.python.org/issue25324

   (39) https://bugs.python.org/issue29104

   (40) https://bugs.python.org/issue27945

   (41) https://bugs.python.org/issue25794

   (42) https://bugs.python.org/issue30039

   (43) https://bugs.python.org/issue28974

   (44) https://bugs.python.org/issue30024

   (45) https://bugs.python.org/issue12414

   (46) https://bugs.python.org/issue29839

   (47) https://bugs.python.org/issue11913

   (48) https://bugs.python.org/issue29914

   (49) https://bugs.python.org/issue29949

   (50) https://bugs.python.org/issue29935

   (51) https://bugs.python.org/issue29816

   (52) https://bugs.python.org/issue24821

   (53) https://bugs.python.org/issue29102

   (54) https://bugs.python.org/issue29894

   (55) https://bugs.python.org/issue29859

   (56) https://bugs.python.org/issue29849

   (57) https://bugs.python.org/issue28856

   (58) https://bugs.python.org/issue29723

   (59) https://bugs.python.org/issue29139

   (60) https://bugs.python.org/issue29568

   (61) https://bugs.python.org/issue29714

   (62) https://bugs.python.org/issue29695

   (63) https://bugs.python.org/issue28893

   (64) https://bugs.python.org/issue28876

   (65) https://bugs.python.org/issue29683

   (66) https://bugs.python.org/issue29684

   (67) https://bugs.python.org/issue28598

   (68) https://bugs.python.org/issue29607

   (69) https://bugs.python.org/issue29602

   (70) https://bugs.python.org/issue29347

   (71) https://bugs.python.org/issue29463

   (72) https://bugs.python.org/issue32911

   (73) https://bugs.python.org/issue29438

   (74) https://bugs.python.org/issue29546

   (75) https://bugs.python.org/issue29546

   (76) https://bugs.python.org/issue29478

   (77) https://bugs.python.org/issue29319

   (78) https://bugs.python.org/issue29337

   (79) https://bugs.python.org/issue29327

   (80) https://bugs.python.org/issue29034

   (81) https://bugs.python.org/issue29159

   (82) https://bugs.python.org/issue29049

   (83) https://bugs.python.org/issue28927

   (84) https://bugs.python.org/issue28932

   (85) https://bugs.python.org/issue25677

   (86) https://bugs.python.org/issue29000

   (87) https://bugs.python.org/issue18896

   (88) https://bugs.python.org/issue28596

   (89) https://bugs.python.org/issue22257

   (90) https://www.python.org/dev/peps/pep-0432

   (91) https://bugs.python.org/issue26919

   (92) https://bugs.python.org/issue28991

   (93) https://bugs.python.org/issue28147

   (94) https://bugs.python.org/issue28739

   (95) https://bugs.python.org/issue28512

   (96) https://bugs.python.org/issue28918

   (97) https://bugs.python.org/issue23722

   (98) https://bugs.python.org/issue28797

   (99) https://bugs.python.org/issue28799

   (100) https://bugs.python.org/issue12844

   (101) https://bugs.python.org/issue28782

   (102) https://bugs.python.org/issue26647

   (103) https://bugs.python.org/issue28774

   (104) https://bugs.python.org/issue28731

   (105) https://bugs.python.org/issue28532

   (106) https://bugs.python.org/issue27100

   (107) https://bugs.python.org/issue28746

   (108) https://bugs.python.org/issue26920

   (109) https://bugs.python.org/issue28648

   (110) https://bugs.python.org/issue28665

   (111) https://bugs.python.org/issue19398

   (112) https://bugs.python.org/issue28621

   (113) https://bugs.python.org/issue28580

   (114) https://bugs.python.org/issue28583

   (115) https://bugs.python.org/issue28128

   (116) https://bugs.python.org/issue28509

   (117) https://bugs.python.org/issue28426

   (118) https://bugs.python.org/issue28517

   (119) https://bugs.python.org/issue28214

   (120) https://bugs.python.org/issue23782

   (121) https://bugs.python.org/issue28183

   (122) https://bugs.python.org/issue26081

   (123) https://bugs.python.org/issue28379

   (124) https://bugs.python.org/issue28376

   (125) https://bugs.python.org/issue28376

   (126) https://bugs.python.org/issue26906

   (127) https://bugs.python.org/issue18287

   (128) https://bugs.python.org/issue24098

   (129) https://bugs.python.org/issue28201

   (130) https://bugs.python.org/issue28350

   (131) https://bugs.python.org/issue26617

   (132) https://bugs.python.org/issue27942

   (133) https://bugs.python.org/issue28289

   (134) https://bugs.python.org/issue21578

   (135) https://bugs.python.org/issue28203

   (136) https://bugs.python.org/issue28086

   (137) https://bugs.python.org/issue28214

   (138) https://bugs.python.org/issue27955

   (139) https://bugs.python.org/issue28192

   (140) https://bugs.python.org/issue27441

   (141) https://bugs.python.org/issue27222

   (142) https://bugs.python.org/issue28131

   (143) https://bugs.python.org/issue28126

   (144) https://bugs.python.org/issue28120

   (145) https://bugs.python.org/issue26182

   (146) https://bugs.python.org/issue26182

   (147) https://bugs.python.org/issue28721

   (148) https://bugs.python.org/issue26110


File: python.info,  Node: Library<39>,  Next: Documentation<34>,  Prev: Core and Builtins<38>,  Up: Python 3 7 0 alpha 1

1.18.40.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 *note multiprocessing: b8. 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): *note dis: 38. 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
     *note multiprocessing: b8. 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 *note logging.config.fileConfig: 3ae. 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 Dong-hee 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: 335.
     instead of *note bytes: 336.

   - 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 Dong-hee 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
     Dong-hee 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 correspondintly).  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 falsy 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/issue31499

   (2) https://bugs.python.org/issue31482

   (3) https://bugs.python.org/issue28556

   (4) https://bugs.python.org/issue28556

   (5) https://bugs.python.org/issue31544

   (6) https://bugs.python.org/issue31234

   (7) https://bugs.python.org/issue31457

   (8) https://bugs.python.org/issue31431

   (9) https://bugs.python.org/issue31233

   (10) https://bugs.python.org/issue28638

   (11) https://bugs.python.org/issue31400

   (12) https://bugs.python.org/issue27629

   (13) https://bugs.python.org/issue28958

   (14) https://bugs.python.org/issue28182

   (15) https://bugs.python.org/issue27340

   (16) https://bugs.python.org/issue14191

   (17) https://bugs.python.org/issue31178

   (18) https://bugs.python.org/issue31350

   (19) https://bugs.python.org/issue31170

   (20) https://bugs.python.org/issue29136

   (21) https://bugs.python.org/issue1198569

   (22) https://bugs.python.org/issue31326

   (23) https://bugs.python.org/issue27144

   (24) https://bugs.python.org/issue31281

   (25) https://bugs.python.org/issue10746

   (26) https://www.python.org/dev/peps/pep-3118

   (27) https://bugs.python.org/issue27584

   (28) https://bugs.python.org/issue22536

   (29) https://bugs.python.org/issue29741

   (30) https://bugs.python.org/issue31249

   (31) https://bugs.python.org/issue31247

   (32) https://bugs.python.org/issue23835

   (33) https://bugs.python.org/issue31238

   (34) https://bugs.python.org/issue5001

   (35) https://bugs.python.org/issue31109

   (36) https://bugs.python.org/issue30102

   (37) https://bugs.python.org/issue18966

   (38) https://bugs.python.org/issue31183

   (39) https://bugs.python.org/issue5001

   (40) https://bugs.python.org/issue31185

   (41) https://bugs.python.org/issue31151

   (42) https://bugs.python.org/issue31072

   (43) https://bugs.python.org/issue24700

   (44) https://bugs.python.org/issue31135

   (45) https://bugs.python.org/issue31107

   (46) https://bugs.python.org/issue31080

   (47) https://bugs.python.org/issue30897

   (48) https://bugs.python.org/issue31061

   (49) https://bugs.python.org/issue30987

   (50) https://bugs.python.org/issue30522

   (51) https://bugs.python.org/issue30502

   (52) https://bugs.python.org/issue5288

   (53) https://bugs.python.org/issue30919

   (54) https://bugs.python.org/issue26732

   (55) https://bugs.python.org/issue29403

   (56) https://bugs.python.org/issue30961

   (57) https://bugs.python.org/issue19896

   (58) https://bugs.python.org/issue30946

   (59) https://bugs.python.org/issue25684

   (60) https://bugs.python.org/issue30886

   (61) https://bugs.python.org/issue29854

   (62) https://bugs.python.org/issue30794

   (63) https://bugs.python.org/issue30319

   (64) https://bugs.python.org/issue30828

   (65) https://bugs.python.org/issue30302

   (66) https://bugs.python.org/issue30807

   (67) https://bugs.python.org/issue30441

   (68) https://bugs.python.org/issue29585

   (69) https://bugs.python.org/issue29293

   (70) https://bugs.python.org/issue30532

   (71) https://bugs.python.org/issue30596

   (72) https://bugs.python.org/issue9146

   (73) https://bugs.python.org/issue29169

   (74) https://bugs.python.org/issue30119

   (75) https://bugs.python.org/issue30879

   (76) https://bugs.python.org/issue30746

   (77) https://bugs.python.org/issue30664

   (78) https://bugs.python.org/issue21071

   (79) https://bugs.python.org/issue29212

   (80) https://bugs.python.org/issue29755

   (81) https://bugs.python.org/issue30616

   (82) https://bugs.python.org/issue30038

   (83) https://bugs.python.org/issue23894

   (84) https://bugs.python.org/issue24744

   (85) https://bugs.python.org/issue24484

   (86) https://bugs.python.org/issue30589

   (87) https://bugs.python.org/issue28994

   (88) https://bugs.python.org/issue30508

   (89) https://bugs.python.org/issue30645

   (90) https://bugs.python.org/issue11822

   (91) https://bugs.python.org/issue30624

   (92) https://bugs.python.org/issue30595

   (93) https://bugs.python.org/issue28556

   (94) https://bugs.python.org/issue30605

   (95) https://bugs.python.org/issue29870

   (96) https://bugs.python.org/issue29743

   (97) https://bugs.python.org/issue27585

   (98) https://bugs.python.org/issue30014

   (99) https://bugs.python.org/issue30418

   (100) https://bugs.python.org/issue30463

   (101) https://bugs.python.org/issue30520

   (102) https://bugs.python.org/issue30557

   (103) https://bugs.python.org/issue30526

   (104) https://bugs.python.org/issue30245

   (105) https://bugs.python.org/issue30378

   (106) https://bugs.python.org/issue16500

   (107) https://bugs.python.org/issue30470

   (108) https://bugs.python.org/issue30414

   (109) https://bugs.python.org/issue30003

   (110) https://bugs.python.org/issue30149

   (111) https://bugs.python.org/issue30436

   (112) https://bugs.python.org/issue30301

   (113) https://bugs.python.org/issue30375

   (114) https://bugs.python.org/issue30329

   (115) https://bugs.python.org/issue29196

   (116) https://bugs.python.org/issue9850

   (117) https://bugs.python.org/issue30299

   (118) https://bugs.python.org/issue30048

   (119) https://bugs.python.org/issue30266

   (120) https://bugs.python.org/issue25958

   (121) https://bugs.python.org/issue30340

   (122) https://bugs.python.org/issue30298

   (123) https://bugs.python.org/issue30285

   (124) https://bugs.python.org/issue29990

   (125) https://bugs.python.org/issue29979

   (126) https://bugs.python.org/issue30243

   (127) https://bugs.python.org/issue30215

   (128) https://bugs.python.org/issue30185

   (129) https://bugs.python.org/issue30103

   (130) https://bugs.python.org/issue28556

   (131) https://bugs.python.org/issue30205

   (132) https://bugs.python.org/issue30228

   (133) https://bugs.python.org/issue30190

   (134) https://bugs.python.org/issue30101

   (135) https://bugs.python.org/issue29822

   (136) https://bugs.python.org/issue29960

   (137) https://bugs.python.org/issue30070

   (138) https://bugs.python.org/issue22352

   (139) https://bugs.python.org/issue30061

   (140) https://bugs.python.org/issue30218

   (141) https://bugs.python.org/issue10076

   (142) https://bugs.python.org/issue30068

   (143) https://bugs.python.org/issue29694

   (144) https://bugs.python.org/issue29692

   (145) https://bugs.python.org/issue26187

   (146) https://bugs.python.org/issue9303

   (147) https://bugs.python.org/issue30017

   (148) https://bugs.python.org/issue29998

   (149) https://bugs.python.org/issue29995

   (150) https://bugs.python.org/issue29962

   (151) https://bugs.python.org/issue29649

   (152) https://bugs.python.org/issue29654

   (153) https://bugs.python.org/issue29931

   (154) https://bugs.python.org/issue29953

   (155) https://bugs.python.org/issue29942

   (156) https://bugs.python.org/issue10030

   (157) https://bugs.python.org/issue29204

   (158) https://bugs.python.org/issue27863

   (159) https://bugs.python.org/issue25996

   (160) https://bugs.python.org/issue28699

   (161) https://bugs.python.org/issue23890

   (162) https://bugs.python.org/issue29901

   (163) https://bugs.python.org/issue25803

   (164) https://bugs.python.org/issue29861

   (165) https://bugs.python.org/issue19930

   (166) https://bugs.python.org/issue29884

   (167) https://bugs.python.org/issue25455

   (168) https://bugs.python.org/issue29800

   (169) https://bugs.python.org/issue8256

   (170) https://bugs.python.org/issue28692

   (171) https://bugs.python.org/issue26121

   (172) https://bugs.python.org/issue29619

   (173) https://bugs.python.org/issue28298

   (174) https://bugs.python.org/issue29645

   (175) https://bugs.python.org/issue28231

   (176) https://bugs.python.org/issue26915

   (177) https://bugs.python.org/issue28682

   (178) https://bugs.python.org/issue29728

   (179) https://bugs.python.org/issue29623

   (180) https://bugs.python.org/issue9303

   (181) https://bugs.python.org/issue28963

   (182) https://bugs.python.org/issue29704

   (183) https://bugs.python.org/issue29271

   (184) https://bugs.python.org/issue29703

   (185) https://bugs.python.org/issue29615

   (186) https://bugs.python.org/issue7769

   (187) https://bugs.python.org/issue29376

   (188) https://bugs.python.org/issue28624

   (189) https://bugs.python.org/issue28518

   (190) https://bugs.python.org/issue29742

   (191) https://bugs.python.org/issue16285

   (192) https://bugs.python.org/issue29532

   (193) https://bugs.python.org/issue29110

   (194) https://bugs.python.org/issue22807

   (195) https://bugs.python.org/issue29576

   (196) https://bugs.python.org/issue29534

   (197) https://bugs.python.org/issue10379

   (198) https://bugs.python.org/issue29851

   (199) https://bugs.python.org/issue28556

   (200) https://bugs.python.org/issue29100

   (201) https://bugs.python.org/issue29416

   (202) https://bugs.python.org/issue29444

   (203) https://bugs.python.org/issue29377

   (204) https://bugs.python.org/issue29218

   (205) https://bugs.python.org/issue29368

   (206) https://bugs.python.org/issue29338

   (207) https://bugs.python.org/issue29335

   (208) https://bugs.python.org/issue29290

   (209) https://bugs.python.org/issue28735

   (210) https://bugs.python.org/issue29197

   (211) https://bugs.python.org/issue29210

   (212) https://bugs.python.org/issue29219

   (213) https://bugs.python.org/issue29192

   (214) https://bugs.python.org/issue29193

   (215) https://bugs.python.org/issue29195

   (216) https://bugs.python.org/issue28969

   (217) https://bugs.python.org/issue20804

   (218) https://bugs.python.org/issue29142

   (219) https://bugs.python.org/issue28961

   (220) https://bugs.python.org/issue15812

   (221) https://bugs.python.org/issue28985

   (222) https://bugs.python.org/issue29079

   (223) https://bugs.python.org/issue13051

   (224) https://bugs.python.org/issue9770

   (225) https://bugs.python.org/issue28427

   (226) https://bugs.python.org/issue28923

   (227) https://bugs.python.org/issue28871

   (228) https://bugs.python.org/issue19542

   (229) https://bugs.python.org/issue20191

   (230) https://bugs.python.org/issue16255

   (231) https://bugs.python.org/issue28779

   (232) https://bugs.python.org/issue26937

   (233) https://bugs.python.org/issue28847

   (234) https://bugs.python.org/issue27030

   (235) https://bugs.python.org/issue28835

   (236) https://bugs.python.org/issue27172

   (237) https://bugs.python.org/issue28740

   (238) https://bugs.python.org/issue26273

   (239) https://bugs.python.org/issue28752

   (240) https://bugs.python.org/issue28727

   (241) https://bugs.python.org/issue18383

   (242) https://bugs.python.org/issue20572

   (243) https://bugs.python.org/issue25659

   (244) https://bugs.python.org/issue28548

   (245) https://bugs.python.org/issue19717

   (246) https://bugs.python.org/issue28563

   (247) https://bugs.python.org/issue28387

   (248) https://bugs.python.org/issue27517

   (249) https://bugs.python.org/issue28549

   (250) https://bugs.python.org/issue28449

   (251) https://bugs.python.org/issue23262

   (252) https://bugs.python.org/issue24241

   (253) https://bugs.python.org/issue27939

   (254) https://bugs.python.org/issue28255

   (255) https://bugs.python.org/issue28255

   (256) https://bugs.python.org/issue20491

   (257) https://bugs.python.org/issue28353

   (258) https://bugs.python.org/issue28430

   (259) https://bugs.python.org/issue27025

   (260) https://bugs.python.org/issue25464

   (261) https://bugs.python.org/issue28488

   (262) https://bugs.python.org/issue25953

   (263) https://bugs.python.org/issue28469

   (264) https://bugs.python.org/issue28115

   (265) https://bugs.python.org/issue18219

   (266) https://bugs.python.org/issue28448

   (267) https://bugs.python.org/issue23214

   (268) https://bugs.python.org/issue28480

   (269) https://bugs.python.org/issue28240

   (270) https://bugs.python.org/issue28240

   (271) https://bugs.python.org/issue28240

   (272) https://github.com/pypa/setuptools/issues/100

   (273) https://bugs.python.org/issue24452

   (274) https://bugs.python.org/issue20766

   (275) https://bugs.python.org/issue27998

   (276) https://bugs.python.org/issue28317

   (277) https://bugs.python.org/issue28380

   (278) https://bugs.python.org/issue28229

   (279) https://bugs.python.org/issue28321

   (280) https://bugs.python.org/issue28225

   (281) https://bugs.python.org/issue28227

   (282) https://bugs.python.org/issue28332

   (283) https://bugs.python.org/issue27358

   (284) https://bugs.python.org/issue28257

   (285) https://bugs.python.org/issue28322

   (286) https://bugs.python.org/issue28228

   (287) https://bugs.python.org/issue28226

   (288) https://bugs.python.org/issue28314

   (289) https://bugs.python.org/issue28148

   (290) https://bugs.python.org/issue28253

   (291) https://bugs.python.org/issue28275

   (292) https://bugs.python.org/issue27897

   (293) https://bugs.python.org/issue18844

   (294) https://bugs.python.org/issue18893

   (295) https://bugs.python.org/issue27611

   (296) https://bugs.python.org/issue27348

   (297) https://bugs.python.org/issue25651

   (298) https://bugs.python.org/issue27778

   (299) https://bugs.python.org/issue28200

   (300) https://bugs.python.org/issue25400

   (301) https://bugs.python.org/issue27932

   (302) https://bugs.python.org/issue28075

   (303) https://bugs.python.org/issue22493

   (304) https://bugs.python.org/issue25270

   (305) https://bugs.python.org/issue28181

   (306) https://bugs.python.org/issue25895

   (307) https://bugs.python.org/issue28114

   (308) https://bugs.python.org/issue27599

   (309) https://bugs.python.org/issue27906

   (310) https://bugs.python.org/issue28174

   (311) https://bugs.python.org/issue26654

   (312) https://bugs.python.org/issue26909

   (313) https://bugs.python.org/issue28176

   (314) https://bugs.python.org/issue27759

   (315) https://bugs.python.org/issue28325

   (316) https://bugs.python.org/issue28368

   (317) https://bugs.python.org/issue28369

   (318) https://bugs.python.org/issue28370

   (319) https://bugs.python.org/issue28371

   (320) https://bugs.python.org/issue28372

   (321) https://bugs.python.org/issue28399

   (322) https://bugs.python.org/issue27972

   (323) https://bugs.python.org/issue24142

   (324) https://bugs.python.org/issue29581

   (325) https://bugs.python.org/issue25532

   (326) https://bugs.python.org/issue30177


File: python.info,  Node: Documentation<34>,  Next: Tests<28>,  Prev: Library<39>,  Up: Python 3 7 0 alpha 1

1.18.40.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(): 336. and *note
     bytearray(): 337. are now their respective type definitions, rather
     than the corresponding builtin function entries.  Use *note bytes:
     10c2. and *note bytearray: 10c3. 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/issue31294

   (2) https://bugs.python.org/issue21649

   (3) https://bugs.python.org/issue31128

   (4) https://bugs.python.org/issue30803

   (5) https://bugs.python.org/issue30176

   (6) https://bugs.python.org/issue30052

   (7) https://bugs.python.org/issue26985

   (8) https://bugs.python.org/issue19824

   (9) https://bugs.python.org/issue20314

   (10) https://bugs.python.org/issue12518

   (11) https://bugs.python.org/issue28929

   (12) https://bugs.python.org/issue25008

   (13) https://bugs.python.org/issue26355

   (14) https://bugs.python.org/issue29349

   (15) https://bugs.python.org/issue23722

   (16) https://www.python.org/dev/peps/pep-0487

   (17) https://bugs.python.org/issue28513


File: python.info,  Node: Tests<28>,  Next: Build<26>,  Prev: Documentation<34>,  Up: Python 3 7 0 alpha 1

1.18.40.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/issue29639

   (2) https://bugs.python.org/issue31320

   (3) https://bugs.python.org/issue31346

   (4) https://bugs.python.org/issue25674

   (5) https://bugs.python.org/issue30715

   (6) https://bugs.python.org/issue30822

   (7) https://bugs.python.org/issue30695

   (8) https://bugs.python.org/issue30357

   (9) https://bugs.python.org/issue30197

   (10) https://bugs.python.org/issue24932

   (11) https://bugs.python.org/issue28950

   (12) https://bugs.python.org/issue28683

   (13) https://bugs.python.org/issue26936

   (14) https://bugs.python.org/issue28666

   (15) https://bugs.python.org/issue23839

   (16) https://bugs.python.org/issue26944

   (17) https://bugs.python.org/issue28409

   (18) https://bugs.python.org/issue28217

   (19) https://bugs.python.org/issue26939


File: python.info,  Node: Build<26>,  Next: Windows<29>,  Prev: Tests<28>,  Up: Python 3 7 0 alpha 1

1.18.40.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/issue31354

   (2) https://bugs.python.org/issue31370

   (3) https://bugs.python.org/issue31341

   (4) https://www.python.org/dev/peps/pep-0011

   (5) https://bugs.python.org/issue30854

   (6) https://bugs.python.org/issue30687

   (7) https://bugs.python.org/issue20210

   (8) https://bugs.python.org/issue29941

   (9) https://bugs.python.org/issue28787

   (10) https://bugs.python.org/issue29243

   (11) https://bugs.python.org/issue23404

   (12) https://bugs.python.org/issue29643

   (13) https://bugs.python.org/issue27593

   (14) https://bugs.python.org/issue29572

   (15) https://bugs.python.org/issue27659

   (16) https://bugs.python.org/issue29384

   (17) https://bugs.python.org/issue26851

   (18) https://bugs.python.org/issue28768

   (19) https://bugs.python.org/issue29080

   (20) https://bugs.python.org/issue23903

   (21) https://bugs.python.org/issue28762

   (22) https://bugs.python.org/issue28538

   (23) https://bugs.python.org/issue20211

   (24) https://bugs.python.org/issue28849

   (25) https://bugs.python.org/issue10656

   (26) https://bugs.python.org/issue26359

   (27) https://bugs.python.org/issue28444

   (28) https://bugs.python.org/issue28208

   (29) https://bugs.python.org/issue28248

   (30) https://bugs.python.org/issue21124

   (31) https://bugs.python.org/issue13756

   (32) https://bugs.python.org/issue21085

   (33) https://bugs.python.org/issue28258

   (34) https://bugs.python.org/issue26661

   (35) https://bugs.python.org/issue27979

   (36) https://bugs.python.org/issue15819

   (37) https://bugs.python.org/issue28676


File: python.info,  Node: Windows<29>,  Next: IDLE<35>,  Prev: Build<26>,  Up: Python 3 7 0 alpha 1

1.18.40.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/issue31392

   (2) https://bugs.python.org/issue30389

   (3) https://bugs.python.org/issue31358

   (4) https://bugs.python.org/issue31340

   (5) https://bugs.python.org/issue30581

   (6) https://bugs.python.org/issue30916

   (7) https://bugs.python.org/issue30731

   (8) https://bugs.python.org/issue30291

   (9) https://bugs.python.org/issue30362

   (10) https://bugs.python.org/issue23451

   (11) https://bugs.python.org/issue30450

   (12) https://bugs.python.org/issue29579

   (13) https://bugs.python.org/issue25778

   (14) https://bugs.python.org/issue28896

   (15) https://bugs.python.org/issue28522

   (16) https://bugs.python.org/issue28402

   (17) https://bugs.python.org/issue28333

   (18) https://bugs.python.org/issue28251

   (19) https://bugs.python.org/issue28110

   (20) https://bugs.python.org/issue28161

   (21) https://bugs.python.org/issue28162

   (22) https://bugs.python.org/issue28163

   (23) https://bugs.python.org/issue28164

   (24) https://bugs.python.org/issue28137

   (25) https://bugs.python.org/issue28138


File: python.info,  Node: IDLE<35>,  Next: Tools/Demos<18>,  Prev: Windows<29>,  Up: Python 3 7 0 alpha 1

1.18.40.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 *note inspect.signature: 560.
     instead of *note inspect.getfullargspec: 562.  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/issue31493

   (2) https://bugs.python.org/issue31488

   (3) https://bugs.python.org/issue31477

   (4) https://bugs.python.org/issue31480

   (5) https://bugs.python.org/issue31421

   (6) https://bugs.python.org/issue31414

   (7) https://bugs.python.org/issue31051

   (8) https://bugs.python.org/issue30617

   (9) https://bugs.python.org/issue31287

   (10) https://bugs.python.org/issue27099

   (11) https://bugs.python.org/issue31206

   (12) https://bugs.python.org/issue31001

   (13) https://bugs.python.org/issue31205

   (14) https://bugs.python.org/issue31130

   (15) https://bugs.python.org/issue31002

   (16) https://bugs.python.org/issue19903

   (17) https://bugs.python.org/issue31083

   (18) https://bugs.python.org/issue31050

   (19) https://bugs.python.org/issue31004

   (20) https://bugs.python.org/issue30781

   (21) https://bugs.python.org/issue31060

   (22) https://bugs.python.org/issue30853

   (23) https://bugs.python.org/issue31003

   (24) https://bugs.python.org/issue30993

   (25) https://bugs.python.org/issue30981

   (26) https://bugs.python.org/issue28523

   (27) https://bugs.python.org/issue30917

   (28) https://bugs.python.org/issue30934

   (29) https://bugs.python.org/issue30913

   (30) https://bugs.python.org/issue30899

   (31) https://bugs.python.org/issue30881

   (32) https://bugs.python.org/issue30851

   (33) https://bugs.python.org/issue30870

   (34) https://bugs.python.org/issue8231

   (35) https://bugs.python.org/issue30779

   (36) https://bugs.python.org/issue30777

   (37) https://bugs.python.org/issue30495

   (38) https://bugs.python.org/issue30723

   (39) https://bugs.python.org/issue30674

   (40) https://bugs.python.org/issue21519

   (41) https://bugs.python.org/issue29910

   (42) https://bugs.python.org/issue30728

   (43) https://bugs.python.org/issue6739

   (44) https://bugs.python.org/issue15786

   (45) https://bugs.python.org/issue25514

   (46) https://bugs.python.org/issue30642

   (47) https://bugs.python.org/issue30495

   (48) https://bugs.python.org/issue30290

   (49) https://bugs.python.org/issue30303

   (50) https://bugs.python.org/issue29071

   (51) https://bugs.python.org/issue28572


File: python.info,  Node: Tools/Demos<18>,  Next: C API<22>,  Prev: IDLE<35>,  Up: Python 3 7 0 alpha 1

1.18.40.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 *note int: 185. for semantical
     booleans.  This avoids repeating the default value for Python and C
     and will help in converting to *note bool: 184. 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/performance’ 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/issue30983

   (2) https://www.python.org/dev/peps/pep-0523

   (3) https://bugs.python.org/issue29748

   (4) https://bugs.python.org/issue24037

   (5) https://bugs.python.org/issue29367

   (6) https://bugs.python.org/issue28023

   (7) https://bugs.python.org/issue15369

   (8) https://bugs.python.org/issue28102


File: python.info,  Node: C API<22>,  Prev: Tools/Demos<18>,  Up: Python 3 7 0 alpha 1

1.18.40.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/issue31338

   (2) https://bugs.python.org/issue30832

   (3) https://bugs.python.org/issue30708

   (4) https://bugs.python.org/issue16500

   (5) https://bugs.python.org/issue6532

   (6) https://bugs.python.org/issue27867

   (7) https://bugs.python.org/issue29083

   (8) https://bugs.python.org/issue28769

   (9) https://bugs.python.org/issue29058

   (10) https://bugs.python.org/issue28822

   (11) https://bugs.python.org/issue28808

   (12) https://bugs.python.org/issue28761

   (13) https://bugs.python.org/issue28748

   (14) https://bugs.python.org/issue19569

   (15) https://bugs.python.org/issue28426


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.18.41 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.18.42 Python 3.6.6 release candidate 1
----------------------------------------

`Release date: 2018-06-11'

* Menu:

* Core and Builtins: Core and Builtins<39>.
* Library: Library<40>.
* Documentation: Documentation<35>.
* Tests: Tests<29>.
* Build: Build<27>.
* Windows: Windows<30>.
* macOS: macOS<22>.
* IDLE: IDLE<36>.
* Tools/Demos: Tools/Demos<19>.
* C API: C API<23>.


File: python.info,  Node: Core and Builtins<39>,  Next: Library<40>,  Up: Python 3 6 6 release candidate 1

1.18.42.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: b45. list.  ‘PyGC_Collect()’ 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 *note ctypes.cast(): 1018. in case
     the type argument is a ctypes structured data type.  Patch by Eryk
     Sun and Oren Milman.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33786

   (2) https://bugs.python.org/issue30654

   (3) https://bugs.python.org/issue33622

   (4) https://bugs.python.org/issue31849

   (5) https://bugs.python.org/issue33391

   (6) https://bugs.python.org/issue28055

   (7) https://bugs.python.org/issue33231

   (8) https://bugs.python.org/issue29922

   (9) https://bugs.python.org/issue33199

   (10) https://bugs.python.org/issue33041

   (11) https://bugs.python.org/issue32282

   (12) https://bugs.python.org/issue21983


File: python.info,  Node: Library<40>,  Next: Documentation<35>,  Prev: Core and Builtins<39>,  Up: Python 3 6 6 release candidate 1

1.18.42.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: 193. instead of *note
     SystemError: 600. when performed on *note mmap.mmap: 1ed. 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 Dong-hee Na.

   - bpo-33383(19): Fixed crash in the get() method of the *note
     dbm.ndbm: 35. 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: 103d.

   - bpo-33131(22): Upgrade bundled version of pip to 10.0.1.

   - bpo-33308(23): Fixed a crash in the *note parser: c8. 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(): 1041.

   - 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: a3. 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: 2b.  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/issue30167

   (2) https://bugs.python.org/issue33812

   (3) https://bugs.python.org/issue30805

   (4) https://bugs.python.org/issue33767

   (5) https://bugs.python.org/issue32684

   (6) https://bugs.python.org/issue33674

   (7) https://bugs.python.org/issue31647

   (8) https://bugs.python.org/issue33672

   (9) https://bugs.python.org/issue33469

   (10) https://bugs.python.org/issue11874

   (11) https://bugs.python.org/issue30877

   (12) https://bugs.python.org/issue33548

   (13) https://bugs.python.org/issue33542

   (14) https://bugs.python.org/issue26819

   (15) https://bugs.python.org/issue28556

   (16) https://bugs.python.org/issue20087

   (17) https://bugs.python.org/issue33422

   (18) https://bugs.python.org/issue33197

   (19) https://bugs.python.org/issue33383

   (20) https://bugs.python.org/issue33329

   (21) https://bugs.python.org/issue991266

   (22) https://bugs.python.org/issue33131

   (23) https://bugs.python.org/issue33308

   (24) https://bugs.python.org/issue33263

   (25) https://bugs.python.org/issue33256

   (26) https://bugs.python.org/issue33203

   (27) https://bugs.python.org/issue33224

   (28) https://www.python.org/dev/peps/pep-0479

   (29) https://bugs.python.org/issue33209

   (30) https://bugs.python.org/issue32861

   (31) https://bugs.python.org/issue33096

   (32) https://bugs.python.org/issue33127

   (33) https://bugs.python.org/issue33021

   (34) https://bugs.python.org/issue27683

   (35) https://bugs.python.org/issue32844

   (36) https://bugs.python.org/issue31908

   (37) https://bugs.python.org/issue31457

   (38) https://bugs.python.org/issue16865

   (39) https://bugs.python.org/issue31238


File: python.info,  Node: Documentation<35>,  Next: Tests<29>,  Prev: Library<40>,  Up: Python 3 6 6 release candidate 1

1.18.42.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: 142. 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/issue33503

   (2) https://bugs.python.org/issue33421

   (3) https://bugs.python.org/issue33378

   (4) https://bugs.python.org/issue33276

   (5) https://bugs.python.org/issue33201

   (6) https://bugs.python.org/issue33195

   (7) https://bugs.python.org/issue33126

   (8) https://bugs.python.org/issue27212

   (9) https://bugs.python.org/issue28247

   (10) https://bugs.python.org/issue18802

   (11) https://bugs.python.org/issue27428

   (12) https://bugs.python.org/issue8243

   (13) https://bugs.python.org/issue31432


File: python.info,  Node: Tests<29>,  Next: Build<27>,  Prev: Documentation<35>,  Up: Python 3 6 6 release candidate 1

1.18.42.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/issue33655

   (2) https://bugs.python.org/issue19417


File: python.info,  Node: Build<27>,  Next: Windows<30>,  Prev: Tests<29>,  Up: Python 3 6 6 release candidate 1

1.18.42.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/issue5755

   (2) https://bugs.python.org/issue33614

   (3) https://bugs.python.org/issue33522

   (4) https://bugs.python.org/issue33012

   (5) https://bugs.python.org/issue33394


File: python.info,  Node: Windows<30>,  Next: macOS<22>,  Prev: Build<27>,  Up: Python 3 6 6 release candidate 1

1.18.42.6 Windows
.................

   - bpo-33184(1): Update Windows installer to OpenSSL 1.0.2o.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33184


File: python.info,  Node: macOS<22>,  Next: IDLE<36>,  Prev: Windows<30>,  Up: Python 3 6 6 release candidate 1

1.18.42.7 macOS
...............

   - bpo-33184(1): Update macOS installer build to use OpenSSL 1.0.2o.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33184


File: python.info,  Node: IDLE<36>,  Next: Tools/Demos<19>,  Prev: macOS<22>,  Up: Python 3 6 6 release candidate 1

1.18.42.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/issue33656

   (2) https://bugs.python.org/issue33768

   (3) https://bugs.python.org/issue33763

   (4) https://bugs.python.org/issue33664

   (5) https://bugs.python.org/issue33679

   (6) https://bugs.python.org/issue33642

   (7) https://bugs.python.org/issue33628

   (8) https://bugs.python.org/issue33564

   (9) https://bugs.python.org/issue29706

   (10) https://bugs.python.org/issue21474

   (11) https://bugs.python.org/issue33204

   (12) https://bugs.python.org/issue32831


File: python.info,  Node: Tools/Demos<19>,  Next: C API<23>,  Prev: IDLE<36>,  Up: Python 3 6 6 release candidate 1

1.18.42.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/issue33189

   (2) https://bugs.python.org/issue31920

   (3) https://bugs.python.org/issue29673

   (4) https://bugs.python.org/issue32885

   (5) https://bugs.python.org/issue31583


File: python.info,  Node: C API<23>,  Prev: Tools/Demos<19>,  Up: Python 3 6 6 release candidate 1

1.18.42.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/issue32374


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.18.43 Python 3.6.5 final
--------------------------

`Release date: 2018-03-28'

* Menu:

* Tests: Tests<30>.
* Build: Build<28>.


File: python.info,  Node: Tests<30>,  Next: Build<28>,  Up: Python 3 6 5 final

1.18.43.1 Tests
...............

   - bpo-32872(1): Avoid regrtest compatibility issue with namespace
     packages.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32872


File: python.info,  Node: Build<28>,  Prev: Tests<30>,  Up: Python 3 6 5 final

1.18.43.2 Build
...............

   - bpo-33163(1): Upgrade pip to 9.0.3 and setuptools to v39.0.1.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33163


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.18.44 Python 3.6.5 release candidate 1
----------------------------------------

`Release date: 2018-03-13'

* Menu:

* Security: Security<24>.
* Core and Builtins: Core and Builtins<40>.
* Library: Library<41>.
* Documentation: Documentation<36>.
* Tests: Tests<31>.
* Build: Build<29>.
* Windows: Windows<31>.
* macOS: macOS<23>.
* IDLE: IDLE<37>.
* Tools/Demos: Tools/Demos<20>.
* C API: C API<24>.


File: python.info,  Node: Security<24>,  Next: Core and Builtins<40>,  Up: Python 3 6 5 release candidate 1

1.18.44.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 and CVE-2018-1061.  Patch by Jamie Davis.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33001

   (2) https://bugs.python.org/issue32981


File: python.info,  Node: Core and Builtins<40>,  Next: Library<41>,  Prev: Security<24>,  Up: Python 3 6 5 release candidate 1

1.18.44.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/issue33026

   (2) https://bugs.python.org/issue17288

   (3) https://bugs.python.org/issue32889

   (4) https://bugs.python.org/issue32650

   (5) https://bugs.python.org/issue32685

   (6) https://bugs.python.org/issue32583

   (7) https://bugs.python.org/issue26163

   (8) https://bugs.python.org/issue27169

   (9) https://bugs.python.org/issue22091

   (10) https://bugs.python.org/issue32329

   (11) https://bugs.python.org/issue30416

   (12) https://bugs.python.org/issue18533

   (13) https://bugs.python.org/issue32028

   (14) https://bugs.python.org/issue32137


File: python.info,  Node: Library<41>,  Next: Documentation<36>,  Prev: Core and Builtins<40>,  Up: Python 3 6 5 release candidate 1

1.18.44.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: 10d, ‘after_cancel(None)’ now
     raises a *note ValueError: 1fc. 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 *note asyncio.Condition: 28e. 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(): 5fe. 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(): 48f. 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():
     4df. method when formatting a number (*note int: 185, *note float:
     188, *note float: 188. 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/issue33064

   (2) https://bugs.python.org/issue31804

   (3) https://bugs.python.org/issue33037

   (4) https://bugs.python.org/issue30353

   (5) https://bugs.python.org/issue33009

   (6) https://bugs.python.org/issue32969

   (7) https://bugs.python.org/issue32713

   (8) https://bugs.python.org/issue30622

   (9) https://bugs.python.org/issue32922

   (10) https://bugs.python.org/issue32859

   (11) https://bugs.python.org/issue21060

   (12) https://bugs.python.org/issue32857

   (13) https://bugs.python.org/issue32852

   (14) https://bugs.python.org/issue32841

   (15) https://bugs.python.org/issue31787

   (16) https://bugs.python.org/issue30157

   (17) https://bugs.python.org/issue32394

   (18) https://bugs.python.org/issue32777

   (19) https://bugs.python.org/issue32647

   (20) https://bugs.python.org/issue32734

   (21) https://bugs.python.org/issue32727

   (22) https://bugs.python.org/issue27931

   (23) https://bugs.python.org/issue32304

   (24) https://bugs.python.org/issue32502

   (25) https://bugs.python.org/issue31848

   (26) https://bugs.python.org/issue32555

   (27) https://bugs.python.org/issue32521

   (28) https://bugs.python.org/issue32473

   (29) https://bugs.python.org/issue32521

   (30) https://bugs.python.org/issue32228

   (31) https://bugs.python.org/issue26133

   (32) https://bugs.python.org/issue32185

   (33) https://bugs.python.org/issue32323

   (34) https://bugs.python.org/issue32302

   (35) https://bugs.python.org/issue32255

   (36) https://bugs.python.org/issue32277

   (37) https://bugs.python.org/issue32199

   (38) https://bugs.python.org/issue27456

   (39) https://bugs.python.org/issue31900

   (40) https://bugs.python.org/issue31802


File: python.info,  Node: Documentation<36>,  Next: Tests<31>,  Prev: Library<41>,  Up: Python 3 6 5 release candidate 1

1.18.44.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 *note __getattr__(): 31f. behavior when
     property ‘get()’ method raises *note AttributeError: 3a0.

   - bpo-32614(4): Modify RE examples in documentation to use raw
     strings to prevent *note DeprecationWarning: 279. and add text to
     REGEX HOWTO to highlight the deprecation.

   - bpo-31972(5): Improve docstrings for *note pathlib.PurePath: 1046.
     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/issue17232

   (2) https://bugs.python.org/issue32800

   (3) https://bugs.python.org/issue8722

   (4) https://bugs.python.org/issue32614

   (5) https://bugs.python.org/issue31972

   (6) https://bugs.python.org/issue17799


File: python.info,  Node: Tests<31>,  Next: Build<29>,  Prev: Documentation<36>,  Up: Python 3 6 5 release candidate 1

1.18.44.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/issue32517

   (2) https://bugs.python.org/issue32721

   (3) https://bugs.python.org/issue32252

   (4) https://bugs.python.org/issue31518


File: python.info,  Node: Build<29>,  Next: Windows<31>,  Prev: Tests<31>,  Up: Python 3 6 5 release candidate 1

1.18.44.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/issue32635


File: python.info,  Node: Windows<31>,  Next: macOS<23>,  Prev: Build<29>,  Up: Python 3 6 5 release candidate 1

1.18.44.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(): 1f4. 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/issue33016

   (2) https://bugs.python.org/issue32903

   (3) https://bugs.python.org/issue31966

   (4) https://bugs.python.org/issue32409

   (5) https://bugs.python.org/issue32457

   (6) https://bugs.python.org/issue32370

   (7) https://bugs.python.org/issue29248

   (8) https://bugs.python.org/issue32588


File: python.info,  Node: macOS<23>,  Next: IDLE<37>,  Prev: Windows<31>,  Up: Python 3 6 5 release candidate 1

1.18.44.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/issue32726


File: python.info,  Node: IDLE<37>,  Next: Tools/Demos<20>,  Prev: macOS<23>,  Up: Python 3 6 5 release candidate 1

1.18.44.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: 8ea.; ‘-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/issue32984

   (2) https://bugs.python.org/issue32940

   (3) https://bugs.python.org/issue32916

   (4) https://bugs.python.org/issue32905

   (5) https://bugs.python.org/issue32874

   (6) https://bugs.python.org/issue32837

   (7) https://bugs.python.org/issue32826

   (8) https://bugs.python.org/issue32765


File: python.info,  Node: Tools/Demos<20>,  Next: C API<24>,  Prev: IDLE<37>,  Up: Python 3 6 5 release candidate 1

1.18.44.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/issue24960

   (2) https://bugs.python.org/issue32222


File: python.info,  Node: C API<24>,  Prev: Tools/Demos<20>,  Up: Python 3 6 5 release candidate 1

1.18.44.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/issue29084


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.18.45 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.18.46 Python 3.6.4 release candidate 1
----------------------------------------

`Release date: 2017-12-05'

* Menu:

* Core and Builtins: Core and Builtins<41>.
* Library: Library<42>.
* Documentation: Documentation<37>.
* Tests: Tests<32>.
* Build: Build<30>.
* Windows: Windows<32>.
* macOS: macOS<24>.
* IDLE: IDLE<38>.
* Tools/Demos: Tools/Demos<21>.
* C API: C API<25>.


File: python.info,  Node: Core and Builtins<41>,  Next: Library<42>,  Up: Python 3 6 4 release candidate 1

1.18.46.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 *note unicodedata.normalize(): 10b4.  Patch by Oren
     Milman.

   - bpo-31588(14): Raise a *note TypeError: 193. 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 *note json: a5, 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 *note ctypes: 2b. 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 *note
     ctypes._CData: 10b5, 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 *note
     warnings.warn_explicit: 5b5, 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/issue32176

   (2) https://bugs.python.org/issue31949

   (3) https://bugs.python.org/issue30696

   (4) https://bugs.python.org/issue20047

   (5) https://bugs.python.org/issue31852

   (6) https://bugs.python.org/issue21720

   (7) https://bugs.python.org/issue31825

   (8) https://bugs.python.org/issue28603

   (9) https://bugs.python.org/issue31786

   (10) https://bugs.python.org/issue31642

   (11) https://bugs.python.org/issue31626

   (12) https://bugs.python.org/issue31619

   (13) https://bugs.python.org/issue31592

   (14) https://bugs.python.org/issue31588

   (15) https://bugs.python.org/issue31566

   (16) https://bugs.python.org/issue31505

   (17) https://bugs.python.org/issue31492

   (18) https://bugs.python.org/issue31490

   (19) https://bugs.python.org/issue31478

   (20) https://bugs.python.org/issue31315

   (21) https://bugs.python.org/issue31311

   (22) https://bugs.python.org/issue31293

   (23) https://bugs.python.org/issue31285

   (24) https://bugs.python.org/issue30817


File: python.info,  Node: Library<42>,  Next: Documentation<37>,  Prev: Core and Builtins<41>,  Up: Python 3 6 4 release candidate 1

1.18.46.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 *note msilib.SummaryInformation.GetProperty():
     fc8. 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():
     1b8. in the *note RobotFileParser.parse(): 10a6. method.  Initial
     patch by Robin Wellner.

   - bpo-12382(9): *note msilib.OpenDatabase(): f14. 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/issue28556

   (2) https://bugs.python.org/issue27240

   (3) https://bugs.python.org/issue30788

   (4) https://bugs.python.org/issue31831

   (5) https://bugs.python.org/issue32182

   (6) https://bugs.python.org/issue32186

   (7) https://bugs.python.org/issue12239

   (8) https://bugs.python.org/issue31325

   (9) https://bugs.python.org/issue12382

   (10) https://bugs.python.org/issue32110

   (11) https://bugs.python.org/issue32072

   (12) https://bugs.python.org/issue32034

   (13) https://bugs.python.org/issue32015

   (14) https://bugs.python.org/issue32011

   (15) https://bugs.python.org/issue31970

   (16) https://bugs.python.org/issue9678

   (17) https://bugs.python.org/issue30057

   (18) https://bugs.python.org/issue31933

   (19) https://bugs.python.org/issue31927

   (20) https://bugs.python.org/issue27666

   (21) https://bugs.python.org/issue31897

   (22) https://bugs.python.org/issue25720

   (23) https://bugs.python.org/issue31893

   (24) https://bugs.python.org/issue31891

   (25) https://bugs.python.org/issue28416

   (26) https://bugs.python.org/issue28326

   (27) https://bugs.python.org/issue31457

   (28) https://bugs.python.org/issue31457

   (29) https://bugs.python.org/issue31806

   (30) https://bugs.python.org/issue28603

   (31) https://bugs.python.org/issue30058

   (32) https://bugs.python.org/issue31770

   (33) https://bugs.python.org/issue31672

   (34) https://bugs.python.org/issue31764

   (35) https://bugs.python.org/issue31752

   (36) https://bugs.python.org/issue31701

   (37) https://bugs.python.org/issue31728

   (38) https://bugs.python.org/issue31620

   (39) https://bugs.python.org/issue31632

   (40) https://bugs.python.org/issue31675

   (41) https://bugs.python.org/issue31673

   (42) https://bugs.python.org/issue30806

   (43) https://bugs.python.org/issue15037

   (44) https://bugs.python.org/issue25351

   (45) https://bugs.python.org/issue25532

   (46) https://bugs.python.org/issue30347

   (47) https://bugs.python.org/issue31516

   (48) https://bugs.python.org/issue31351

   (49) https://bugs.python.org/issue31482

   (50) https://bugs.python.org/issue31334

   (51) https://bugs.python.org/issue31310

   (52) https://bugs.python.org/issue31308


File: python.info,  Node: Documentation<37>,  Next: Tests<32>,  Prev: Library<42>,  Up: Python 3 6 4 release candidate 1

1.18.46.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/issue32105

   (2) https://bugs.python.org/issue31537

   (3) https://bugs.python.org/issue30085


File: python.info,  Node: Tests<32>,  Next: Build<30>,  Prev: Documentation<37>,  Up: Python 3 6 4 release candidate 1

1.18.46.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/issue31380

   (2) https://bugs.python.org/issue31705

   (3) https://bugs.python.org/issue31174

   (4) https://bugs.python.org/issue30695


File: python.info,  Node: Build<30>,  Next: Windows<32>,  Prev: Tests<32>,  Up: Python 3 6 4 release candidate 1

1.18.46.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/issue32059

   (2) https://bugs.python.org/issue31957

   (3) https://bugs.python.org/issue31609

   (4) https://bugs.python.org/issue31934

   (5) https://bugs.python.org/issue31926

   (6) https://bugs.python.org/issue28791

   (7) https://bugs.python.org/issue28791

   (8) https://bugs.python.org/issue22140

   (9) https://bugs.python.org/issue31536


File: python.info,  Node: Windows<32>,  Next: macOS<24>,  Prev: Build<30>,  Up: Python 3 6 4 release candidate 1

1.18.46.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/issue1102

   (2) https://bugs.python.org/issue31944


File: python.info,  Node: macOS<24>,  Next: IDLE<38>,  Prev: Windows<32>,  Up: Python 3 6 4 release candidate 1

1.18.46.7 macOS
...............

   - bpo-31392(1): Update macOS installer to use OpenSSL 1.0.2m

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31392


File: python.info,  Node: IDLE<38>,  Next: Tools/Demos<21>,  Prev: macOS<24>,  Up: Python 3 6 4 release candidate 1

1.18.46.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/issue32207

   (2) https://bugs.python.org/issue32164

   (3) https://bugs.python.org/issue32100

   (4) https://bugs.python.org/issue31858

   (5) https://bugs.python.org/issue31860

   (6) https://bugs.python.org/issue31836

   (7) https://bugs.python.org/issue28603

   (8) https://bugs.python.org/issue13802

   (9) https://bugs.python.org/issue31460

   (10) https://bugs.python.org/issue31649

   (11) https://bugs.python.org/issue31559

   (12) https://bugs.python.org/issue31459

   (13) https://bugs.python.org/issue31500

   (14) https://bugs.python.org/issue1612262


File: python.info,  Node: Tools/Demos<21>,  Next: C API<25>,  Prev: IDLE<38>,  Up: Python 3 6 4 release candidate 1

1.18.46.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/issue30722


File: python.info,  Node: C API<25>,  Prev: Tools/Demos<21>,  Up: Python 3 6 4 release candidate 1

1.18.46.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/issue20891

   (2) https://bugs.python.org/issue31532

   (3) https://bugs.python.org/issue30697

   (4) https://bugs.python.org/issue22898


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.18.47 Python 3.6.3 final
--------------------------

`Release date: 2017-10-03'

* Menu:

* Library: Library<43>.
* Build: Build<31>.


File: python.info,  Node: Library<43>,  Next: Build<31>,  Up: Python 3 6 3 final

1.18.47.1 Library
.................

   - bpo-31641(1): Re-allow arbitrary iterables in *note
     concurrent.futures.as_completed(): 10f3.  Fixes regression in
     3.6.3rc1.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue31641


File: python.info,  Node: Build<31>,  Prev: Library<43>,  Up: Python 3 6 3 final

1.18.47.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/issue31662

   (2) https://bugs.python.org/issue31423


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.18.48 Python 3.6.3 release candidate 1
----------------------------------------

`Release date: 2017-09-18'

* Menu:

* Security: Security<25>.
* Core and Builtins: Core and Builtins<42>.
* Library: Library<44>.
* Documentation: Documentation<38>.
* Tests: Tests<33>.
* Build: Build<32>.
* Windows: Windows<33>.
* IDLE: IDLE<39>.
* Tools/Demos: Tools/Demos<22>.


File: python.info,  Node: Security<25>,  Next: Core and Builtins<42>,  Up: Python 3 6 3 release candidate 1

1.18.48.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/issue29781

   (2) https://bugs.python.org/issue30947


File: python.info,  Node: Core and Builtins<42>,  Next: Library<44>,  Prev: Security<25>,  Up: Python 3 6 3 release candidate 1

1.18.48.2 Core and Builtins
...........................

   - bpo-31471(1): Fix an assertion failure in *note subprocess.Popen():
     2ba. 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 *note
     zipimport.zipimporter.get_data: 10bf. 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
     *note io.TextIOWrapper: 5f8, when the encoder doesn’t return a
     bytes object.  Patch by Oren Milman.

   - bpo-31243(10): Fix a crash in some methods of *note
     io.TextIOWrapper: 5f8, 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/issue31471

   (2) https://bugs.python.org/issue31418

   (3) https://bugs.python.org/issue31416

   (4) https://bugs.python.org/issue31411

   (5) https://bugs.python.org/issue31373

   (6) https://bugs.python.org/issue30465

   (7) https://bugs.python.org/issue31343

   (8) https://bugs.python.org/issue31291

   (9) https://bugs.python.org/issue31271

   (10) https://bugs.python.org/issue31243

   (11) https://bugs.python.org/issue30721

   (12) https://bugs.python.org/issue31070

   (13) https://bugs.python.org/issue31095

   (14) https://bugs.python.org/issue31071

   (15) https://bugs.python.org/issue30978

   (16) https://bugs.python.org/issue30808

   (17) https://bugs.python.org/issue30876

   (18) https://bugs.python.org/issue30703

   (19) https://bugs.python.org/issue30765

   (20) https://bugs.python.org/issue31161

   (21) https://bugs.python.org/issue30814

   (22) https://bugs.python.org/issue30597


File: python.info,  Node: Library<44>,  Next: Documentation<38>,  Prev: Core and Builtins<42>,  Up: Python 3 6 3 release candidate 1

1.18.48.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 Dong-hee 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/issue31499

   (2) https://bugs.python.org/issue28556

   (3) https://bugs.python.org/issue28556

   (4) https://bugs.python.org/issue31544

   (5) https://bugs.python.org/issue31234

   (6) https://bugs.python.org/issue31457

   (7) https://bugs.python.org/issue31400

   (8) https://bugs.python.org/issue28958

   (9) https://bugs.python.org/issue27340

   (10) https://bugs.python.org/issue31178

   (11) https://bugs.python.org/issue31350

   (12) https://bugs.python.org/issue31170

   (13) https://bugs.python.org/issue29136

   (14) https://bugs.python.org/issue29212

   (15) https://bugs.python.org/issue9146

   (16) https://bugs.python.org/issue27144

   (17) https://bugs.python.org/issue10746

   (18) https://www.python.org/dev/peps/pep-3118

   (19) https://bugs.python.org/issue22536

   (20) https://bugs.python.org/issue31249

   (21) https://bugs.python.org/issue31247

   (22) https://bugs.python.org/issue30102

   (23) https://bugs.python.org/issue31185

   (24) https://bugs.python.org/issue31135

   (25) https://bugs.python.org/issue31107

   (26) https://bugs.python.org/issue31061

   (27) https://bugs.python.org/issue30502

   (28) https://bugs.python.org/issue30119

   (29) https://bugs.python.org/issue30595

   (30) https://bugs.python.org/issue29403

   (31) https://bugs.python.org/issue30961

   (32) https://bugs.python.org/issue25684

   (33) https://bugs.python.org/issue30886

   (34) https://bugs.python.org/issue29854

   (35) https://bugs.python.org/issue30319

   (36) https://bugs.python.org/issue30828

   (37) https://bugs.python.org/issue30807

   (38) https://bugs.python.org/issue30441

   (39) https://bugs.python.org/issue30532

   (40) https://bugs.python.org/issue30879

   (41) https://bugs.python.org/issue30746

   (42) https://bugs.python.org/issue29755


File: python.info,  Node: Documentation<38>,  Next: Tests<33>,  Prev: Library<44>,  Up: Python 3 6 3 release candidate 1

1.18.48.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/issue31294

   (2) https://bugs.python.org/issue21649

   (3) https://bugs.python.org/issue30803


File: python.info,  Node: Tests<33>,  Next: Build<32>,  Prev: Documentation<38>,  Up: Python 3 6 3 release candidate 1

1.18.48.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/issue31320

   (2) https://bugs.python.org/issue25674

   (3) https://bugs.python.org/issue30715

   (4) https://bugs.python.org/issue30822


File: python.info,  Node: Build<32>,  Next: Windows<33>,  Prev: Tests<33>,  Up: Python 3 6 3 release candidate 1

1.18.48.6 Build
...............

   - bpo-30854(1): Fix compile error when compiling –without-threads.
     Patch by Masayuki Yamamoto.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue30854


File: python.info,  Node: Windows<33>,  Next: IDLE<39>,  Prev: Build<32>,  Up: Python 3 6 3 release candidate 1

1.18.48.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/issue30389

   (2) https://bugs.python.org/issue31340

   (3) https://bugs.python.org/issue30581

   (4) https://bugs.python.org/issue30731


File: python.info,  Node: IDLE<39>,  Next: Tools/Demos<22>,  Prev: Windows<33>,  Up: Python 3 6 3 release candidate 1

1.18.48.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 *note inspect.signature: 560.
     instead of *note inspect.getfullargspec: 562.  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/issue31493

   (2) https://bugs.python.org/issue31488

   (3) https://bugs.python.org/issue31477

   (4) https://bugs.python.org/issue31480

   (5) https://bugs.python.org/issue31421

   (6) https://bugs.python.org/issue31414

   (7) https://bugs.python.org/issue31051

   (8) https://bugs.python.org/issue30617

   (9) https://bugs.python.org/issue31287

   (10) https://bugs.python.org/issue27099

   (11) https://bugs.python.org/issue31206

   (12) https://bugs.python.org/issue31001

   (13) https://bugs.python.org/issue31205

   (14) https://bugs.python.org/issue31130

   (15) https://bugs.python.org/issue31002

   (16) https://bugs.python.org/issue19903

   (17) https://bugs.python.org/issue31083

   (18) https://bugs.python.org/issue31050

   (19) https://bugs.python.org/issue31004

   (20) https://bugs.python.org/issue30781

   (21) https://bugs.python.org/issue31060

   (22) https://bugs.python.org/issue30853

   (23) https://bugs.python.org/issue31003

   (24) https://bugs.python.org/issue30993

   (25) https://bugs.python.org/issue30981

   (26) https://bugs.python.org/issue28523

   (27) https://bugs.python.org/issue30917

   (28) https://bugs.python.org/issue30934

   (29) https://bugs.python.org/issue30913

   (30) https://bugs.python.org/issue30899

   (31) https://bugs.python.org/issue30881

   (32) https://bugs.python.org/issue30851

   (33) https://bugs.python.org/issue30870

   (34) https://bugs.python.org/issue8231

   (35) https://bugs.python.org/issue30779

   (36) https://bugs.python.org/issue30777

   (37) https://bugs.python.org/issue30495

   (38) https://bugs.python.org/issue30723

   (39) https://bugs.python.org/issue30674

   (40) https://bugs.python.org/issue21519

   (41) https://bugs.python.org/issue29910

   (42) https://bugs.python.org/issue30728

   (43) https://bugs.python.org/issue6739


File: python.info,  Node: Tools/Demos<22>,  Prev: IDLE<39>,  Up: Python 3 6 3 release candidate 1

1.18.48.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/issue30983

   (2) https://www.python.org/dev/peps/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.18.49 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.18.50 Python 3.6.2 release candidate 2
----------------------------------------

`Release date: 2017-07-07'

* Menu:

* Security: Security<26>.


File: python.info,  Node: Security<26>,  Up: Python 3 6 2 release candidate 2

1.18.50.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
     (External entity infinite loop DoS), CVE-2016-9063 (Integer
     overflow, re-fix), CVE-2016-0718 (Fix regression bugs from 2.2.0’s
     fix to CVE-2016-0718) and CVE-2012-0876 (Counter hash flooding with
     SipHash).  Note: the CVE-2016-5300 (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(3): 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/issue30730

   (2) https://bugs.python.org/issue30694

   (3) https://bugs.python.org/issue30500


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.18.51 Python 3.6.2 release candidate 1
----------------------------------------

`Release date: 2017-06-17'

* Menu:

* Core and Builtins: Core and Builtins<43>.
* Library: Library<45>.
* Security: Security<27>.
* Library: Library<46>.
* IDLE: IDLE<40>.
* C API: C API<26>.
* Build: Build<33>.
* Documentation: Documentation<39>.
* Tools/Demos: Tools/Demos<23>.
* Tests: Tests<34>.
* Windows: Windows<34>.


File: python.info,  Node: Core and Builtins<43>,  Next: Library<45>,  Up: Python 3 6 2 release candidate 1

1.18.51.1 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 Dong-hee 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: 965.

   - 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/issue30682

   (2) https://bugs.python.org/issue30604

   (3) https://bugs.python.org/issue29104

   (4) https://bugs.python.org/issue27945

   (5) https://bugs.python.org/issue25794

   (6) https://bugs.python.org/issue30039

   (7) https://bugs.python.org/issue12414

   (8) https://bugs.python.org/issue29949

   (9) https://bugs.python.org/issue29935

   (10) https://bugs.python.org/issue29859

   (11) https://bugs.python.org/issue28876

   (12) https://bugs.python.org/issue29600

   (13) https://bugs.python.org/issue28856

   (14) https://bugs.python.org/issue29714

   (15) https://bugs.python.org/issue29478


File: python.info,  Node: Library<45>,  Next: Security<27>,  Prev: Core and Builtins<43>,  Up: Python 3 6 2 release candidate 1

1.18.51.2 Library
.................

   - bpo-30616(1): Functional API of enum allows to create empty enums.
     Patched by Dong-hee 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
     Dong-hee 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue30616

   (2) https://bugs.python.org/issue30038

   (3) https://bugs.python.org/issue23894

   (4) https://bugs.python.org/issue23890

   (5) https://bugs.python.org/issue30149

   (6) https://bugs.python.org/issue30645

   (7) https://bugs.python.org/issue29931

   (8) https://bugs.python.org/issue30605


File: python.info,  Node: Security<27>,  Next: Library<46>,  Prev: Library<45>,  Up: Python 3 6 2 release candidate 1

1.18.51.3 Security
..................

   - bpo-29591(1): Update expat copy from 2.1.1 to 2.2.0 to get fixes of
     CVE-2016-0718 and CVE-2016-4472.  See
     ‘https://sourceforge.net/p/expat/bugs/537/’ for more information.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue29591


File: python.info,  Node: Library<46>,  Next: IDLE<40>,  Prev: Security<27>,  Up: Python 3 6 2 release candidate 1

1.18.51.4 Library
.................

   - bpo-24484(1): Avoid race condition in multiprocessing cleanup
     (#2159)

   - bpo-28994(2): The traceback no longer displayed for SystemExit
     raised in a callback registered by atexit.

   - bpo-30508(3): Don’t log exceptions if Task/Future "cancel()" method
     was called.

   - bpo-28556(4): Updates to typing module: Add generic
     AsyncContextManager, add support for ContextManager on all
     versions.  Original PRs by Jelle Zijlstra and Ivan Levkivskyi

   - bpo-29870(5): Fix ssl sockets leaks when connection is aborted in
     asyncio/ssl implementation.  Patch by Michaël Sghaïer.

   - bpo-29743(6): Closing transport during handshake process leaks open
     socket.  Patch by Nikolay Kim

   - bpo-27585(7): Fix waiter cancellation in asyncio.Lock.  Patch by
     Mathieu Sornay.

   - bpo-30418(8): 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(9): inspect.isabstract() now works during
     __init_subclass__.  Patch by Nate Soares.

   - bpo-29581(10): ABCMeta.__new__ now accepts ‘**kwargs’, allowing
     abstract base classes to use keyword parameters in
     __init_subclass__.  Patch by Nate Soares.

   - bpo-30557(11): faulthandler now correctly filters and displays
     exception codes on Windows

   - bpo-30378(12): Fix the problem that logging.handlers.SysLogHandler
     cannot handle IPv6 addresses.

   - bpo-29960(13): Preserve generator state when
     _random.Random.setstate() raises an exception.  Patch by Bryan
     Olson.

   - bpo-30414(14): multiprocessing.Queue._feed background running
     thread do not break from main loop on exception.

   - bpo-30003(15): Fix handling escape characters in HZ codec.  Based
     on patch by Ma Lin.

   - bpo-30301(16): Fix AttributeError when using SimpleQueue.empty()
     under `spawn' and `forkserver' start methods.

   - bpo-30329(17): 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(18): 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(19): Fixed ‘Task.cancel()’ can be ignored when the task
     is running coroutine and the coroutine returned without any more
     ‘await’.

   - bpo-30266(20): contextlib.AbstractContextManager now supports
     anti-registration by setting __enter__ = None or __exit__ = None,
     following the pattern introduced in bpo-25958(21).  Patch by Jelle
     Zijlstra.

   - bpo-30298(22): 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(23): Fix range checking in GB18030 decoder.  Original
     patch by Ma Lin.

   - bpo-26293(24): Change resulted because of zipfile breakage.  (See
     also: bpo-29094(25))

   - bpo-30243(26): 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(27): Avoid KeyboardInterrupt tracebacks in forkserver
     helper process when Ctrl-C is received.

   - bpo-28556(28): 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(29): Fix getsockname() for unbound AF_UNIX sockets on
     Linux.

   - bpo-30070(30): Fixed leaks and crashes in errors handling in the
     parser module.

   - bpo-30061(31): 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(32): 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(33): _io._IOBase.readlines will check if it’s closed
     first when hint is present.

   - bpo-29694(34): Fixed race condition in pathlib mkdir with flags
     parents=True.  Patch by Armin Rigo.

   - bpo-29692(35): Fixed arbitrary unchaining of RuntimeError
     exceptions in contextlib.contextmanager.  Patch by Siddharth
     Velankar.

   - bpo-29998(36): Pickling and copying ImportError now preserves name
     and path attributes.

   - bpo-29953(37): Fixed memory leaks in the replace() method of
     datetime and time objects when pass out of bound fold argument.

   - bpo-29942(38): Fix a crash in itertools.chain.from_iterable when
     encountering long runs of empty iterables.

   - bpo-27863(39): Fixed multiple crashes in ElementTree caused by race
     conditions and wrong types.

   - bpo-28699(40): 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(41): Avoid incorrect errors raised by
     Path.mkdir(exist_ok=True) when the OS gives priority to errors such
     as EACCES over EEXIST.

   - bpo-29861(42): Release references to tasks, their arguments and
     their results as soon as they are finished in multiprocessing.Pool.

   - bpo-29884(43): faulthandler: Restore the old sigaltstack during
     teardown.  Patch by Christophe Zeitouny.

   - bpo-25455(44): Fixed crashes in repr of recursive buffered
     file-like objects.

   - bpo-29800(45): Fix crashes in partial.__repr__ if the keys of
     partial.keywords are not strings.  Patch by Michael Seifert.

   - bpo-29742(46): get_extra_info() raises exception if get called on
     closed ssl transport.  Patch by Nikolay Kim.

   - bpo-8256(47): 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(48): 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(49): The zipfile module now accepts path-like objects for
     external paths.

   - bpo-26915(50): index() and count() methods of
     collections.abc.Sequence now check identity before checking
     equality when do comparisons.

   - bpo-29615(51): SimpleXMLRPCDispatcher no longer chains KeyError (or
     any other exception) to exception(s) raised in the dispatched
     methods.  Patch by Petr Motejlek.

   - bpo-30177(52): 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/issue24484

   (2) https://bugs.python.org/issue28994

   (3) https://bugs.python.org/issue30508

   (4) https://bugs.python.org/issue28556

   (5) https://bugs.python.org/issue29870

   (6) https://bugs.python.org/issue29743

   (7) https://bugs.python.org/issue27585

   (8) https://bugs.python.org/issue30418

   (9) https://bugs.python.org/issue29822

   (10) https://bugs.python.org/issue29581

   (11) https://bugs.python.org/issue30557

   (12) https://bugs.python.org/issue30378

   (13) https://bugs.python.org/issue29960

   (14) https://bugs.python.org/issue30414

   (15) https://bugs.python.org/issue30003

   (16) https://bugs.python.org/issue30301

   (17) https://bugs.python.org/issue30329

   (18) https://bugs.python.org/issue30375

   (19) https://bugs.python.org/issue30048

   (20) https://bugs.python.org/issue30266

   (21) https://bugs.python.org/issue25958

   (22) https://bugs.python.org/issue30298

   (23) https://bugs.python.org/issue29990

   (24) https://bugs.python.org/issue26293

   (25) https://bugs.python.org/issue29094

   (26) https://bugs.python.org/issue30243

   (27) https://bugs.python.org/issue30185

   (28) https://bugs.python.org/issue28556

   (29) https://bugs.python.org/issue30205

   (30) https://bugs.python.org/issue30070

   (31) https://bugs.python.org/issue30061

   (32) https://bugs.python.org/issue30017

   (33) https://bugs.python.org/issue30068

   (34) https://bugs.python.org/issue29694

   (35) https://bugs.python.org/issue29692

   (36) https://bugs.python.org/issue29998

   (37) https://bugs.python.org/issue29953

   (38) https://bugs.python.org/issue29942

   (39) https://bugs.python.org/issue27863

   (40) https://bugs.python.org/issue28699

   (41) https://bugs.python.org/issue25803

   (42) https://bugs.python.org/issue29861

   (43) https://bugs.python.org/issue29884

   (44) https://bugs.python.org/issue25455

   (45) https://bugs.python.org/issue29800

   (46) https://bugs.python.org/issue29742

   (47) https://bugs.python.org/issue8256

   (48) https://bugs.python.org/issue28298

   (49) https://bugs.python.org/issue28231

   (50) https://bugs.python.org/issue26915

   (51) https://bugs.python.org/issue29615

   (52) https://bugs.python.org/issue30177


File: python.info,  Node: IDLE<40>,  Next: C API<26>,  Prev: Library<46>,  Up: Python 3 6 2 release candidate 1

1.18.51.5 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/issue15786

   (2) https://bugs.python.org/issue25514

   (3) https://bugs.python.org/issue30642

   (4) https://bugs.python.org/issue30495

   (5) https://bugs.python.org/issue30290

   (6) https://bugs.python.org/issue30303


File: python.info,  Node: C API<26>,  Next: Build<33>,  Prev: IDLE<40>,  Up: Python 3 6 2 release candidate 1

1.18.51.6 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/issue27867


File: python.info,  Node: Build<33>,  Next: Documentation<39>,  Prev: C API<26>,  Up: Python 3 6 2 release candidate 1

1.18.51.7 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/issue29941

   (2) https://bugs.python.org/issue28787

   (3) https://bugs.python.org/issue29243

   (4) https://bugs.python.org/issue23404

   (5) https://bugs.python.org/issue29643


File: python.info,  Node: Documentation<39>,  Next: Tools/Demos<23>,  Prev: Build<33>,  Up: Python 3 6 2 release candidate 1

1.18.51.8 Documentation
.......................

   - bpo-30176(1): Add missing attribute related constants in curses
     documentation.

   - bpo-30052(2): the link targets for *note bytes(): 336. and *note
     bytearray(): 337. are now their respective type definitions, rather
     than the corresponding builtin function entries.  Use *note bytes:
     10c2. and *note bytearray: 10c3. 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/issue30176

   (2) https://bugs.python.org/issue30052

   (3) https://bugs.python.org/issue26985


File: python.info,  Node: Tools/Demos<23>,  Next: Tests<34>,  Prev: Documentation<39>,  Up: Python 3 6 2 release candidate 1

1.18.51.9 Tools/Demos
.....................

   - bpo-29367(1): python-gdb.py now supports also ‘method-wrapper’
     (‘wrapperobject’) objects.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue29367


File: python.info,  Node: Tests<34>,  Next: Windows<34>,  Prev: Tools/Demos<23>,  Up: Python 3 6 2 release candidate 1

1.18.51.10 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/issue30357

   (2) https://bugs.python.org/issue30197


File: python.info,  Node: Windows<34>,  Prev: Tests<34>,  Up: Python 3 6 2 release candidate 1

1.18.51.11 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/issue30687

   (2) https://bugs.python.org/issue30450


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.18.52 Python 3.6.1 final
--------------------------

`Release date: 2017-03-21'

* Menu:

* Core and Builtins: Core and Builtins<44>.
* Build: Build<34>.


File: python.info,  Node: Core and Builtins<44>,  Next: Build<34>,  Up: Python 3 6 1 final

1.18.52.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/issue29723

   (2) https://bugs.python.org/issue29139


File: python.info,  Node: Build<34>,  Prev: Core and Builtins<44>,  Up: Python 3 6 1 final

1.18.52.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/issue27593


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.18.53 Python 3.6.1 release candidate 1
----------------------------------------

`Release date: 2017-03-04'

* Menu:

* Core and Builtins: Core and Builtins<45>.
* Library: Library<47>.
* IDLE: IDLE<41>.
* Windows: Windows<35>.
* C API: C API<27>.
* Documentation: Documentation<40>.
* Tests: Tests<35>.
* Build: Build<35>.


File: python.info,  Node: Core and Builtins<45>,  Next: Library<47>,  Up: Python 3 6 1 release candidate 1

1.18.53.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/issue28893

   (2) https://bugs.python.org/issue29683

   (3) https://bugs.python.org/issue29684

   (4) https://bugs.python.org/issue28598

   (5) https://bugs.python.org/issue29607

   (6) https://bugs.python.org/issue29602

   (7) https://bugs.python.org/issue29347

   (8) https://bugs.python.org/issue29438

   (9) https://bugs.python.org/issue29319

   (10) https://bugs.python.org/issue29337

   (11) https://bugs.python.org/issue29327

   (12) https://bugs.python.org/issue29034

   (13) https://bugs.python.org/issue29159

   (14) https://bugs.python.org/issue28932

   (15) https://bugs.python.org/issue25677

   (16) https://bugs.python.org/issue29000

   (17) https://bugs.python.org/issue26919

   (18) https://bugs.python.org/issue28991

   (19) https://bugs.python.org/issue28739

   (20) https://bugs.python.org/issue28512

   (21) https://bugs.python.org/issue28918

   (22) https://bugs.python.org/issue28731


File: python.info,  Node: Library<47>,  Next: IDLE<41>,  Prev: Core and Builtins<45>,  Up: Python 3 6 1 release candidate 1

1.18.53.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/issue29169

   (2) https://bugs.python.org/issue29623

   (3) https://bugs.python.org/issue28963

   (4) https://bugs.python.org/issue29704

   (5) https://bugs.python.org/issue29271

   (6) https://bugs.python.org/issue29703

   (7) https://bugs.python.org/issue29376

   (8) https://bugs.python.org/issue28624

   (9) https://bugs.python.org/issue28518

   (10) https://bugs.python.org/issue29532

   (11) https://bugs.python.org/issue29110

   (12) https://bugs.python.org/issue28556

   (13) https://bugs.python.org/issue29100

   (14) https://bugs.python.org/issue29519

   (15) https://bugs.python.org/issue29416

   (16) https://bugs.python.org/issue29444

   (17) https://bugs.python.org/issue29335

   (18) https://bugs.python.org/issue29290

   (19) https://bugs.python.org/issue28735

   (20) https://bugs.python.org/issue29316

   (21) https://bugs.python.org/issue29219

   (22) https://bugs.python.org/issue29011

   (23) https://bugs.python.org/issue28969

   (24) https://bugs.python.org/issue29142

   (25) https://bugs.python.org/issue28961

   (26) https://bugs.python.org/issue29203

   (27) https://www.python.org/dev/peps/pep-0468

   (28) https://bugs.python.org/issue15812

   (29) https://bugs.python.org/issue29094

   (30) https://bugs.python.org/issue29085

   (31) https://bugs.python.org/issue29061

   (32) https://bugs.python.org/issue29079

   (33) https://bugs.python.org/issue13051

   (34) https://bugs.python.org/issue29119

   (35) https://bugs.python.org/issue9770

   (36) https://bugs.python.org/issue28427

   (37) https://bugs.python.org/issue28923

   (38) https://bugs.python.org/issue29055

   (39) https://bugs.python.org/issue28871

   (40) https://bugs.python.org/issue19542

   (41) https://bugs.python.org/issue20191

   (42) https://bugs.python.org/issue28779

   (43) https://bugs.python.org/issue28847

   (44) https://bugs.python.org/issue26937


File: python.info,  Node: IDLE<41>,  Next: Windows<35>,  Prev: Library<47>,  Up: Python 3 6 1 release candidate 1

1.18.53.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/issue29071

   (2) https://bugs.python.org/issue28572


File: python.info,  Node: Windows<35>,  Next: C API<27>,  Prev: IDLE<41>,  Up: Python 3 6 1 release candidate 1

1.18.53.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/issue29579

   (2) https://bugs.python.org/issue29326

   (3) https://bugs.python.org/issue28164

   (4) https://bugs.python.org/issue29409

   (5) https://www.python.org/dev/peps/pep-0529

   (6) https://bugs.python.org/issue29392

   (7) https://bugs.python.org/issue25778

   (8) https://bugs.python.org/issue28896


File: python.info,  Node: C API<27>,  Next: Documentation<40>,  Prev: Windows<35>,  Up: Python 3 6 1 release candidate 1

1.18.53.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/issue27867

   (2) https://bugs.python.org/issue29083

   (3) https://bugs.python.org/issue29058


File: python.info,  Node: Documentation<40>,  Next: Tests<35>,  Prev: C API<27>,  Up: Python 3 6 1 release candidate 1

1.18.53.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/issue28929

   (2) https://bugs.python.org/issue25008

   (3) https://bugs.python.org/issue26355

   (4) https://bugs.python.org/issue29349


File: python.info,  Node: Tests<35>,  Next: Build<35>,  Prev: Documentation<40>,  Up: Python 3 6 1 release candidate 1

1.18.53.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/issue28087

   (2) https://bugs.python.org/issue29571

   (3) https://bugs.python.org/issue28950

   (4) https://bugs.python.org/issue28683

   (5) https://bugs.python.org/issue26939


File: python.info,  Node: Build<35>,  Prev: Tests<35>,  Up: Python 3 6 1 release candidate 1

1.18.53.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/issue27593

   (2) https://bugs.python.org/issue29572

   (3) https://bugs.python.org/issue26851

   (4) https://bugs.python.org/issue28768

   (5) https://bugs.python.org/issue29080

   (6) https://bugs.python.org/issue23903

   (7) https://bugs.python.org/issue28762

   (8) https://bugs.python.org/issue28538

   (9) https://bugs.python.org/issue20211

   (10) https://bugs.python.org/issue28849


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.18.54 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.18.55 Python 3.6.0 release candidate 2
----------------------------------------

`Release date: 2016-12-16'

* Menu:

* Core and Builtins: Core and Builtins<46>.
* Tools/Demos: Tools/Demos<24>.
* Windows: Windows<36>.
* Build: Build<36>.


File: python.info,  Node: Core and Builtins<46>,  Next: Tools/Demos<24>,  Up: Python 3 6 0 release candidate 2

1.18.55.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/issue28147

   (2) https://bugs.python.org/issue28990


File: python.info,  Node: Tools/Demos<24>,  Next: Windows<36>,  Prev: Core and Builtins<46>,  Up: Python 3 6 0 release candidate 2

1.18.55.2 Tools/Demos
.....................

   - bpo-28770(1): Fix python-gdb.py for fastcalls.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28770


File: python.info,  Node: Windows<36>,  Next: Build<36>,  Prev: Tools/Demos<24>,  Up: Python 3 6 0 release candidate 2

1.18.55.3 Windows
.................

   - bpo-28896(1): Deprecate WindowsRegistryFinder.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28896


File: python.info,  Node: Build<36>,  Prev: Windows<36>,  Up: Python 3 6 0 release candidate 2

1.18.55.4 Build
...............

   - bpo-28898(1): Prevent gdb build errors due to HAVE_LONG_LONG
     redefinition.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28898


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.18.56 Python 3.6.0 release candidate 1
----------------------------------------

`Release date: 2016-12-06'

* Menu:

* Core and Builtins: Core and Builtins<47>.
* Library: Library<48>.
* C API: C API<28>.
* Documentation: Documentation<41>.
* Tools/Demos: Tools/Demos<25>.


File: python.info,  Node: Core and Builtins<47>,  Next: Library<48>,  Up: Python 3 6 0 release candidate 1

1.18.56.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/issue23722

   (2) https://bugs.python.org/issue28797

   (3) https://bugs.python.org/issue28782

   (4) https://bugs.python.org/issue26647


File: python.info,  Node: Library<48>,  Next: C API<28>,  Prev: Core and Builtins<47>,  Up: Python 3 6 0 release candidate 1

1.18.56.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/issue27030

   (2) https://bugs.python.org/issue28835

   (3) https://bugs.python.org/issue27172

   (4) https://bugs.python.org/issue26273

   (5) https://bugs.python.org/issue24142

   (6) https://bugs.python.org/issue28843


File: python.info,  Node: C API<28>,  Next: Documentation<41>,  Prev: Library<48>,  Up: Python 3 6 0 release candidate 1

1.18.56.3 C API
...............

   - bpo-28808(1): PyUnicode_CompareWithASCIIString() now never raises
     exceptions.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28808


File: python.info,  Node: Documentation<41>,  Next: Tools/Demos<25>,  Prev: C API<28>,  Up: Python 3 6 0 release candidate 1

1.18.56.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/issue23722

   (2) https://www.python.org/dev/peps/pep-0487


File: python.info,  Node: Tools/Demos<25>,  Prev: Documentation<41>,  Up: Python 3 6 0 release candidate 1

1.18.56.5 Tools/Demos
.....................

   - bpo-28023(1): Fix python-gdb.py didn’t support new dict
     implementation.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28023


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.18.57 Python 3.6.0 beta 4
---------------------------

`Release date: 2016-11-21'

* Menu:

* Core and Builtins: Core and Builtins<48>.
* Library: Library<49>.
* Documentation: Documentation<42>.
* Tests: Tests<36>.
* Build: Build<37>.


File: python.info,  Node: Core and Builtins<48>,  Next: Library<49>,  Up: Python 3 6 0 beta 4

1.18.57.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/issue28532

   (2) https://bugs.python.org/issue27100

   (3) https://bugs.python.org/issue28746

   (4) https://bugs.python.org/issue26920

   (5) https://bugs.python.org/issue28648

   (6) https://bugs.python.org/issue19398

   (7) https://bugs.python.org/issue28665

   (8) https://bugs.python.org/issue28583

   (9) https://bugs.python.org/issue27243

   (10) https://bugs.python.org/issue26182

   (11) https://bugs.python.org/issue28721


File: python.info,  Node: Library<49>,  Next: Documentation<42>,  Prev: Core and Builtins<48>,  Up: Python 3 6 0 beta 4

1.18.57.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/issue28752

   (2) https://bugs.python.org/issue28727

   (3) https://bugs.python.org/issue18383

   (4) https://bugs.python.org/issue20572

   (5) https://bugs.python.org/issue25659

   (6) https://bugs.python.org/issue19717

   (7) https://bugs.python.org/issue28563

   (8) https://bugs.python.org/issue28387

   (9) https://bugs.python.org/issue28600

   (10) https://bugs.python.org/issue28613

   (11) https://bugs.python.org/issue28634

   (12) https://bugs.python.org/issue26081

   (13) https://bugs.python.org/issue28639

   (14) https://bugs.python.org/issue28652

   (15) https://bugs.python.org/issue28653

   (16) https://bugs.python.org/issue28703

   (17) https://bugs.python.org/issue28704

   (18) https://bugs.python.org/issue28720


File: python.info,  Node: Documentation<42>,  Next: Tests<36>,  Prev: Library<49>,  Up: Python 3 6 0 beta 4

1.18.57.3 Documentation
.......................

   - bpo-28513(1): Documented command-line interface of zipfile.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28513


File: python.info,  Node: Tests<36>,  Next: Build<37>,  Prev: Documentation<42>,  Up: Python 3 6 0 beta 4

1.18.57.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/issue28666

   (2) https://bugs.python.org/issue23839


File: python.info,  Node: Build<37>,  Prev: Tests<36>,  Up: Python 3 6 0 beta 4

1.18.57.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/issue10656

   (2) https://bugs.python.org/issue26359

   (3) https://bugs.python.org/issue28676


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.18.58 Python 3.6.0 beta 3
---------------------------

`Release date: 2016-10-31'

* Menu:

* Core and Builtins: Core and Builtins<49>.
* Library: Library<50>.
* Windows: Windows<37>.
* Build: Build<38>.
* Tests: Tests<37>.


File: python.info,  Node: Core and Builtins<49>,  Next: Library<50>,  Up: Python 3 6 0 beta 3

1.18.58.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/issue28128

   (2) https://bugs.python.org/issue28509

   (3) https://bugs.python.org/issue28426

   (4) https://bugs.python.org/issue28517

   (5) https://bugs.python.org/issue28214

   (6) https://bugs.python.org/issue23782

   (7) https://bugs.python.org/issue28471


File: python.info,  Node: Library<50>,  Next: Windows<37>,  Prev: Core and Builtins<49>,  Up: Python 3 6 0 beta 3

1.18.58.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/issue27517

   (2) https://bugs.python.org/issue28549

   (3) https://bugs.python.org/issue28449

   (4) https://bugs.python.org/issue23262

   (5) https://bugs.python.org/issue27939

   (6) https://bugs.python.org/issue18844

   (7) https://bugs.python.org/issue28255

   (8) https://bugs.python.org/issue20491

   (9) https://bugs.python.org/issue28353

   (10) https://bugs.python.org/issue28430

   (11) https://bugs.python.org/issue27025

   (12) https://bugs.python.org/issue25464

   (13) https://bugs.python.org/issue28488

   (14) https://bugs.python.org/issue25953

   (15) https://bugs.python.org/issue18219

   (16) https://bugs.python.org/issue28448

   (17) https://bugs.python.org/issue28480

   (18) https://bugs.python.org/issue24452

   (19) https://bugs.python.org/issue20766

   (20) https://bugs.python.org/issue28492

   (21) https://bugs.python.org/issue28500

   (22) https://bugs.python.org/issue26923

   (23) https://bugs.python.org/issue26796

   (24) https://bugs.python.org/issue28544


File: python.info,  Node: Windows<37>,  Next: Build<38>,  Prev: Library<50>,  Up: Python 3 6 0 beta 3

1.18.58.3 Windows
.................

   - bpo-28522(1): Fixes mishandled buffer reallocation in getpathp.c

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28522


File: python.info,  Node: Build<38>,  Next: Tests<37>,  Prev: Windows<37>,  Up: Python 3 6 0 beta 3

1.18.58.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/issue28444

   (2) https://bugs.python.org/issue28208

   (3) https://bugs.python.org/issue28248


File: python.info,  Node: Tests<37>,  Prev: Build<38>,  Up: Python 3 6 0 beta 3

1.18.58.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/issue26944

   (2) https://bugs.python.org/issue28409


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.18.59 Python 3.6.0 beta 2
---------------------------

`Release date: 2016-10-10'

* Menu:

* Core and Builtins: Core and Builtins<50>.
* Library: Library<51>.
* Windows: Windows<38>.
* C API: C API<29>.
* Build: Build<39>.
* Tests: Tests<38>.


File: python.info,  Node: Core and Builtins<50>,  Next: Library<51>,  Up: Python 3 6 0 beta 2

1.18.59.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/issue28183

   (2) https://bugs.python.org/issue26081

   (3) https://bugs.python.org/issue28379

   (4) https://bugs.python.org/issue28376

   (5) https://bugs.python.org/issue28376

   (6) https://bugs.python.org/issue28376

   (7) https://bugs.python.org/issue26906

   (8) https://bugs.python.org/issue18287

   (9) https://bugs.python.org/issue24098

   (10) https://bugs.python.org/issue28201

   (11) https://bugs.python.org/issue28350

   (12) https://bugs.python.org/issue26617

   (13) https://bugs.python.org/issue27942

   (14) https://bugs.python.org/issue21578

   (15) https://bugs.python.org/issue28203

   (16) https://bugs.python.org/issue28086

   (17) https://bugs.python.org/issue28214

   (18) https://bugs.python.org/issue27955

   (19) https://bugs.python.org/issue28192

   (20) https://bugs.python.org/issue28131

   (21) https://bugs.python.org/issue28126

   (22) https://bugs.python.org/issue28120

   (23) https://bugs.python.org/issue26182


File: python.info,  Node: Library<51>,  Next: Windows<38>,  Prev: Core and Builtins<50>,  Up: Python 3 6 0 beta 2

1.18.59.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 falsy 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/issue27998

   (2) https://bugs.python.org/issue28317

   (3) https://bugs.python.org/issue26293

   (4) https://bugs.python.org/issue28380

   (5) https://bugs.python.org/issue27181

   (6) https://bugs.python.org/issue28229

   (7) https://bugs.python.org/issue28321

   (8) https://bugs.python.org/issue28225

   (9) https://bugs.python.org/issue28227

   (10) https://bugs.python.org/issue27358

   (11) https://bugs.python.org/issue28257

   (12) https://bugs.python.org/issue28322

   (13) https://bugs.python.org/issue28228

   (14) https://bugs.python.org/issue28226

   (15) https://bugs.python.org/issue28314

   (16) https://bugs.python.org/issue28148

   (17) https://bugs.python.org/issue28253

   (18) https://bugs.python.org/issue28275

   (19) https://bugs.python.org/issue27897

   (20) https://bugs.python.org/issue18844

   (21) https://bugs.python.org/issue18893

   (22) https://bugs.python.org/issue27611

   (23) https://bugs.python.org/issue27348

   (24) https://bugs.python.org/issue25651

   (25) https://bugs.python.org/issue27778

   (26) https://bugs.python.org/issue28200

   (27) https://bugs.python.org/issue25400

   (28) https://bugs.python.org/issue27932

   (29) https://bugs.python.org/issue28075

   (30) https://bugs.python.org/issue22493

   (31) https://bugs.python.org/issue25270

   (32) https://bugs.python.org/issue28181

   (33) https://bugs.python.org/issue25895

   (34) https://bugs.python.org/issue28114

   (35) https://bugs.python.org/issue27599

   (36) https://bugs.python.org/issue27906

   (37) https://bugs.python.org/issue28174

   (38) https://bugs.python.org/issue26654

   (39) https://bugs.python.org/issue26909

   (40) https://bugs.python.org/issue28176

   (41) https://bugs.python.org/issue27759

   (42) https://bugs.python.org/issue28368

   (43) https://bugs.python.org/issue28369

   (44) https://bugs.python.org/issue28370

   (45) https://bugs.python.org/issue28371

   (46) https://bugs.python.org/issue28372

   (47) https://bugs.python.org/issue28399

   (48) https://bugs.python.org/issue27972


File: python.info,  Node: Windows<38>,  Next: C API<29>,  Prev: Library<51>,  Up: Python 3 6 0 beta 2

1.18.59.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/issue28402

   (2) https://bugs.python.org/issue28333

   (3) https://bugs.python.org/issue28251

   (4) https://bugs.python.org/issue28110

   (5) https://bugs.python.org/issue28161

   (6) https://bugs.python.org/issue28162

   (7) https://bugs.python.org/issue28163

   (8) https://bugs.python.org/issue28164

   (9) https://bugs.python.org/issue28137

   (10) https://bugs.python.org/issue28138


File: python.info,  Node: C API<29>,  Next: Build<39>,  Prev: Windows<38>,  Up: Python 3 6 0 beta 2

1.18.59.4 C API
...............

   - bpo-28426(1): Deprecated undocumented functions
     PyUnicode_AsEncodedObject(), PyUnicode_AsDecodedObject(),
     PyUnicode_AsDecodedUnicode() and PyUnicode_AsEncodedUnicode().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28426


File: python.info,  Node: Build<39>,  Next: Tests<38>,  Prev: C API<29>,  Up: Python 3 6 0 beta 2

1.18.59.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/issue28258

   (2) https://bugs.python.org/issue26661

   (3) https://bugs.python.org/issue15819


File: python.info,  Node: Tests<38>,  Prev: Build<39>,  Up: Python 3 6 0 beta 2

1.18.59.6 Tests
...............

   - bpo-28217(1): Adds _testconsole module to test console input.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28217


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.18.60 Python 3.6.0 beta 1
---------------------------

`Release date: 2016-09-12'

* Menu:

* Core and Builtins: Core and Builtins<51>.
* Library: Library<52>.
* IDLE: IDLE<42>.
* C API: C API<30>.
* Tests: Tests<39>.
* Build: Build<40>.
* Tools/Demos: Tools/Demos<26>.
* Windows: Windows<39>.


File: python.info,  Node: Core and Builtins<51>,  Next: Library<52>,  Up: Python 3 6 0 beta 1

1.18.60.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): *note dict: 1b9. 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/issue23722

   (2) https://bugs.python.org/issue25221

   (3) https://bugs.python.org/issue27080

   (4) https://www.python.org/dev/peps/pep-0515

   (5) https://bugs.python.org/issue27199

   (6) https://bugs.python.org/issue27948

   (7) https://bugs.python.org/issue28046

   (8) https://bugs.python.org/issue28071

   (9) https://bugs.python.org/issue25758

   (10) https://bugs.python.org/issue25856

   (11) https://bugs.python.org/issue27213

   (12) https://bugs.python.org/issue26331

   (13) https://www.python.org/dev/peps/pep-0515

   (14) https://bugs.python.org/issue27999

   (15) https://bugs.python.org/issue28003

   (16) https://www.python.org/dev/peps/pep-0525

   (17) https://bugs.python.org/issue27985

   (18) https://www.python.org/dev/peps/pep-0526

   (19) https://bugs.python.org/issue26058

   (20) https://bugs.python.org/issue27364

   (21) https://bugs.python.org/issue27350

   (22) https://bugs.python.org/issue27911

   (23) https://bugs.python.org/issue27078

   (24) https://bugs.python.org/issue17884

   (25) https://bugs.python.org/issue27961

   (26) https://bugs.python.org/issue27355

   (27) https://www.python.org/dev/peps/pep-0523

   (28) https://bugs.python.org/issue27870

   (29) https://bugs.python.org/issue25402

   (30) https://bugs.python.org/issue27214

   (31) https://bugs.python.org/issue27506

   (32) https://bugs.python.org/issue27812

   (33) https://bugs.python.org/issue27811

   (34) https://bugs.python.org/issue27587

   (35) https://bugs.python.org/issue27792

   (36) https://bugs.python.org/issue26984

   (37) https://bugs.python.org/issue25604

   (38) https://bugs.python.org/issue24254

   (39) https://bugs.python.org/issue27662

   (40) https://bugs.python.org/issue27782

   (41) https://bugs.python.org/issue27936

   (42) https://bugs.python.org/issue27487

   (43) https://bugs.python.org/issue27157

   (44) https://bugs.python.org/issue27558

   (45) https://bugs.python.org/issue28008

   (46) https://www.python.org/dev/peps/pep-0530

   (47) https://bugs.python.org/issue27942


File: python.info,  Node: Library<52>,  Next: IDLE<42>,  Prev: Core and Builtins<51>,  Up: Python 3 6 0 beta 1

1.18.60.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(): 4d6. 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(): 56e. 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).

   - bpo-27766(53): Add ChaCha20 Poly1305 to ssl module’s default cipher
     list.  (Required OpenSSL 1.1.0 or LibreSSL).

   - bpo-25387(54): Check return value of winsound.MessageBeep.

   - bpo-27866(55): Add SSLContext.get_ciphers() method to get a list of
     all enabled ciphers.

   - bpo-27744(56): Add AF_ALG (Linux Kernel crypto) to socket module.

   - bpo-26470(57): Port ssl and hashlib module to OpenSSL 1.1.0.

   - bpo-11620(58): Fix support for SND_MEMORY in winsound.PlaySound.
     Based on a patch by Tim Lesher.

   - bpo-11734(59): Add support for IEEE 754 half-precision floats to
     the struct module.  Based on a patch by Eli Stevens.

   - bpo-27919(60): Deprecated ‘extra_path’ distribution option in
     distutils packaging.

   - bpo-23229(61): 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(62): 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(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.

   - bpo-12319(69): 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(70)) - 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(71): Make ‘_normalize’ parameter to ‘Fraction’
     constructor keyword-only, so that ‘Fraction(2, 3, 4)’ now raises
     ‘TypeError’.

   - bpo-27539(72): Fix unnormalised ‘Fraction.__pow__’ result in the
     case of negative exponent and negative base.

   - bpo-21718(73): cursor.description is now available for queries
     using CTEs.

   - bpo-27819(74): In distutils sdists, simply produce the "gztar"
     (gzipped tar format) distributions on all platforms unless
     "formats" is supplied.

   - bpo-2466(75): posixpath.ismount now correctly recognizes mount
     points which the user does not have permission to access.

   - bpo-9998(76): On Linux, ctypes.util.find_library now looks in
     LD_LIBRARY_PATH for shared libraries.

   - bpo-27573(77): exit message for code.interact is now configurable.

   - bpo-27930(78): Improved behaviour of
     logging.handlers.QueueListener.  Thanks to Paulo Andrade and Petr
     Viktorin for the analysis and patch.

   - bpo-6766(79): Distributed reference counting added to
     multiprocessing to support nesting of shared values / proxy
     objects.

   - bpo-21201(80): Improves readability of multiprocessing error
     message.  Thanks to Wojciech Walczak for patch.

   - asyncio: Add set_protocol / get_protocol to Transports.

   - bpo-27456(81): asyncio: Set TCP_NODELAY by default.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28732

   (2) https://bugs.python.org/issue28485

   (3) https://bugs.python.org/issue28037

   (4) https://bugs.python.org/issue25283

   (5) https://bugs.python.org/issue24454

   (6) https://bugs.python.org/issue10740

   (7) https://bugs.python.org/issue17941

   (8) https://bugs.python.org/issue22493

   (9) https://bugs.python.org/issue26885

   (10) https://bugs.python.org/issue28070

   (11) https://bugs.python.org/issue19500

   (12) https://bugs.python.org/issue28022

   (13) https://bugs.python.org/issue28043

   (14) https://bugs.python.org/issue24693

   (15) https://bugs.python.org/issue17909

   (16) https://bugs.python.org/issue27137

   (17) https://bugs.python.org/issue1703178

   (18) https://bugs.python.org/issue28019

   (19) https://bugs.python.org/issue18401

   (20) https://bugs.python.org/issue25969

   (21) https://bugs.python.org/issue14977

   (22) https://bugs.python.org/issue28082

   (23) https://bugs.python.org/issue28025

   (24) https://bugs.python.org/issue23591

   (25) https://bugs.python.org/issue433028

   (26) https://bugs.python.org/issue24594

   (27) https://bugs.python.org/issue17582

   (28) https://bugs.python.org/issue28047

   (29) https://bugs.python.org/issue27576

   (30) https://bugs.python.org/issue28027

   (31) https://bugs.python.org/issue27445

   (32) https://bugs.python.org/issue24277

   (33) https://bugs.python.org/issue22450

   (34) https://bugs.python.org/issue28005

   (35) https://bugs.python.org/issue26667

   (36) https://bugs.python.org/issue27570

   (37) https://bugs.python.org/issue22233

   (38) https://bugs.python.org/issue27331

   (39) https://bugs.python.org/issue27988

   (40) https://bugs.python.org/issue16113

   (41) https://bugs.python.org/issue27776

   (42) https://www.python.org/dev/peps/pep-0524

   (43) https://bugs.python.org/issue27778

   (44) https://www.python.org/dev/peps/pep-0524

   (45) https://bugs.python.org/issue27691

   (46) https://bugs.python.org/issue18844

   (47) https://bugs.python.org/issue25761

   (48) https://bugs.python.org/issue26798

   (49) https://bugs.python.org/issue26032

   (50) https://bugs.python.org/issue25596

   (51) https://bugs.python.org/issue27928

   (52) https://bugs.python.org/issue27850

   (53) https://bugs.python.org/issue27766

   (54) https://bugs.python.org/issue25387

   (55) https://bugs.python.org/issue27866

   (56) https://bugs.python.org/issue27744

   (57) https://bugs.python.org/issue26470

   (58) https://bugs.python.org/issue11620

   (59) https://bugs.python.org/issue11734

   (60) https://bugs.python.org/issue27919

   (61) https://bugs.python.org/issue23229

   (62) https://bugs.python.org/issue27842

   (63) https://bugs.python.org/issue12885

   (64) https://bugs.python.org/issue27881

   (65) https://bugs.python.org/issue27861

   (66) https://bugs.python.org/issue19884

   (67) https://bugs.python.org/issue27706

   (68) https://bugs.python.org/issue10513

   (69) https://bugs.python.org/issue12319

   (70) https://bugs.python.org/issue27598

   (71) https://bugs.python.org/issue27832

   (72) https://bugs.python.org/issue27539

   (73) https://bugs.python.org/issue21718

   (74) https://bugs.python.org/issue27819

   (75) https://bugs.python.org/issue2466

   (76) https://bugs.python.org/issue9998

   (77) https://bugs.python.org/issue27573

   (78) https://bugs.python.org/issue27930

   (79) https://bugs.python.org/issue6766

   (80) https://bugs.python.org/issue21201

   (81) https://bugs.python.org/issue27456


File: python.info,  Node: IDLE<42>,  Next: C API<30>,  Prev: Library<52>,  Up: Python 3 6 0 beta 1

1.18.60.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/issue15308

   (2) https://bugs.python.org/issue27922

   (3) https://bugs.python.org/issue27891

   (4) https://bugs.python.org/issue17642

   (5) https://bugs.python.org/issue25564

   (6) https://bugs.python.org/issue27821


File: python.info,  Node: C API<30>,  Next: Tests<39>,  Prev: IDLE<42>,  Up: Python 3 6 0 beta 1

1.18.60.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/issue26900

   (2) https://bugs.python.org/issue26027


File: python.info,  Node: Tests<39>,  Next: Build<40>,  Prev: C API<30>,  Up: Python 3 6 0 beta 1

1.18.60.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/issue27427

   (2) https://bugs.python.org/issue27953

   (3) https://bugs.python.org/issue26040

   (4) https://bugs.python.org/issue27787


File: python.info,  Node: Build<40>,  Next: Tools/Demos<26>,  Prev: Tests<39>,  Up: Python 3 6 0 beta 1

1.18.60.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/issue27566

   (2) https://bugs.python.org/issue27705

   (3) https://bugs.python.org/issue27976

   (4) https://bugs.python.org/issue27983

   (5) https://bugs.python.org/issue21590

   (6) https://bugs.python.org/issue26307

   (7) https://bugs.python.org/issue26359

   (8) https://bugs.python.org/issue27917

   (9) https://bugs.python.org/issue25825

   (10) https://bugs.python.org/issue21122

   (11) https://bugs.python.org/issue17128


File: python.info,  Node: Tools/Demos<26>,  Next: Windows<39>,  Prev: Build<40>,  Up: Python 3 6 0 beta 1

1.18.60.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/issue27952


File: python.info,  Node: Windows<39>,  Prev: Tools/Demos<26>,  Up: Python 3 6 0 beta 1

1.18.60.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/issue28065

   (2) https://bugs.python.org/issue25144

   (3) https://bugs.python.org/issue1602

   (4) https://bugs.python.org/issue27781

   (5) https://bugs.python.org/issue27731

   (6) https://bugs.python.org/issue6135

   (7) https://bugs.python.org/issue27959

   (8) https://bugs.python.org/issue27982

   (9) https://bugs.python.org/issue20366

   (10) https://bugs.python.org/issue27756

   (11) https://bugs.python.org/issue27883


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.18.61 Python 3.6.0 alpha 4
----------------------------

`Release date: 2016-08-15'

* Menu:

* Core and Builtins: Core and Builtins<52>.
* Library: Library<53>.
* IDLE: IDLE<43>.
* Tests: Tests<40>.
* Windows: Windows<40>.
* Build: Build<41>.


File: python.info,  Node: Core and Builtins<52>,  Next: Library<53>,  Up: Python 3 6 0 alpha 4

1.18.61.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/issue27704

   (2) https://bugs.python.org/issue26823

   (3) https://bugs.python.org/issue27574

   (4) https://bugs.python.org/issue22557

   (5) https://bugs.python.org/issue17596

   (6) https://bugs.python.org/issue17599

   (7) https://bugs.python.org/issue27507

   (8) https://bugs.python.org/issue27581

   (9) https://bugs.python.org/issue1621

   (10) https://bugs.python.org/issue27419

   (11) https://bugs.python.org/issue27083

   (12) https://bugs.python.org/issue27514

   (13) https://bugs.python.org/issue27366

   (14) https://www.python.org/dev/peps/pep-0487


File: python.info,  Node: Library<53>,  Next: IDLE<43>,  Prev: Core and Builtins<52>,  Up: Python 3 6 0 alpha 4

1.18.61.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).  Ignore
     the HTTP_PROXY variable when REQUEST_METHOD environment is set,
     which indicates that the script is in CGI mode.

   - bpo-7063(28): Remove dead code from the "array" module’s slice
     handling.  Patch by Chuck.

   - bpo-27656(29): Do not assume sched.h defines any SCHED_* constants.

   - bpo-27130(30): 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(31): Implemented PEP 495(32) (Local Time Disambiguation).

   - Expose the EPOLLEXCLUSIVE constant (when it is defined) in the
     select module.

   - bpo-27567(33): Expose the EPOLLRDHUP and POLLRDHUP constants in the
     select module.

   - bpo-1621(34): Avoid signed int negation overflow in the "audioop"
     module.

   - bpo-27533(35): Release GIL in nt._isdir

   - bpo-17711(36): Fixed unpickling by the persistent ID with protocol
     0.  Original patch by Alexandre Vassalotti.

   - bpo-27522(37): Avoid an unintentional reference cycle in
     email.feedparser.

   - bpo-27512(38): Fix a segfault when os.fspath() called an
     __fspath__() method that raised an exception.  Patch by Xiang
     Zhang.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26027

   (2) https://www.python.org/dev/peps/pep-0519

   (3) https://bugs.python.org/issue27524

   (4) https://bugs.python.org/issue27598

   (5) https://bugs.python.org/issue25958

   (6) https://bugs.python.org/issue16764

   (7) https://bugs.python.org/issue27736

   (8) https://bugs.python.org/issue27038

   (9) https://bugs.python.org/issue25628

   (10) https://bugs.python.org/issue12345

   (11) https://www.python.org/dev/peps/pep-0628

   (12) https://bugs.python.org/issue26823

   (13) https://bugs.python.org/issue27664

   (14) https://bugs.python.org/issue27181

   (15) https://bugs.python.org/issue27573

   (16) https://bugs.python.org/issue6422

   (17) https://bugs.python.org/issue27773

   (18) https://bugs.python.org/issue26750

   (19) https://bugs.python.org/issue26754

   (20) https://bugs.python.org/issue26800

   (21) https://bugs.python.org/issue26981

   (22) https://bugs.python.org/issue27661

   (23) https://bugs.python.org/issue27783

   (24) https://bugs.python.org/issue27774

   (25) https://bugs.python.org/issue27760

   (26) https://bugs.python.org/issue27758

   (27) https://bugs.python.org/issue27568

   (28) https://bugs.python.org/issue7063

   (29) https://bugs.python.org/issue27656

   (30) https://bugs.python.org/issue27130

   (31) https://bugs.python.org/issue24773

   (32) https://www.python.org/dev/peps/pep-0495

   (33) https://bugs.python.org/issue27567

   (34) https://bugs.python.org/issue1621

   (35) https://bugs.python.org/issue27533

   (36) https://bugs.python.org/issue17711

   (37) https://bugs.python.org/issue27522

   (38) https://bugs.python.org/issue27512


File: python.info,  Node: IDLE<43>,  Next: Tests<40>,  Prev: Library<53>,  Up: Python 3 6 0 alpha 4

1.18.61.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/issue27714

   (2) https://bugs.python.org/issue27621

   (3) https://bugs.python.org/issue27620

   (4) https://bugs.python.org/issue27609

   (5) https://bugs.python.org/issue27609

   (6) https://bugs.python.org/issue25507

   (7) https://bugs.python.org/issue27173

   (8) https://bugs.python.org/issue27452


File: python.info,  Node: Tests<40>,  Next: Windows<40>,  Prev: IDLE<43>,  Up: Python 3 6 0 alpha 4

1.18.61.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/issue25805

   (2) https://bugs.python.org/issue27472

   (3) https://bugs.python.org/issue27369

   (4) https://bugs.python.org/issue27594


File: python.info,  Node: Windows<40>,  Next: Build<41>,  Prev: Tests<40>,  Up: Python 3 6 0 alpha 4

1.18.61.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/issue27647

   (2) https://bugs.python.org/issue27610

   (3) https://www.python.org/dev/peps/pep-0514

   (4) https://bugs.python.org/issue27469

   (5) https://bugs.python.org/issue27309


File: python.info,  Node: Build<41>,  Prev: Windows<40>,  Up: Python 3 6 0 alpha 4

1.18.61.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/issue27713

   (2) https://bugs.python.org/issue25825

   (3) https://bugs.python.org/issue27453

   (4) https://bugs.python.org/issue27641

   (5) https://bugs.python.org/issue26662

   (6) https://bugs.python.org/issue10910


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.18.62 Python 3.6.0 alpha 3
----------------------------

`Release date: 2016-07-11'

* Menu:

* Core and Builtins: Core and Builtins<53>.
* Library: Library<54>.
* Security: Security<28>.
* Library: Library<55>.
* Security: Security<29>.
* Library: Library<56>.
* IDLE: IDLE<44>.
* C API: C API<31>.
* Build: Build<42>.
* Tools/Demos: Tools/Demos<27>.
* Documentation: Documentation<43>.
* Tests: Tests<41>.


File: python.info,  Node: Core and Builtins<53>,  Next: Library<54>,  Up: Python 3 6 0 alpha 3

1.18.62.1 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/issue27473

   (2) https://bugs.python.org/issue23034

   (3) https://bugs.python.org/issue27443

   (4) https://bugs.python.org/issue27007


File: python.info,  Node: Library<54>,  Next: Security<28>,  Prev: Core and Builtins<53>,  Up: Python 3 6 0 alpha 3

1.18.62.2 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26844

   (2) https://bugs.python.org/issue23804

   (3) https://bugs.python.org/issue27466

   (4) https://bugs.python.org/issue21708

   (5) https://bugs.python.org/issue26721

   (6) https://bugs.python.org/issue22115

   (7) https://bugs.python.org/issue26243

   (8) https://bugs.python.org/issue27038

   (9) https://bugs.python.org/issue27186

   (10) https://bugs.python.org/issue18726

   (11) https://bugs.python.org/issue27319

   (12) https://bugs.python.org/issue27079

   (13) https://bugs.python.org/issue27294

   (14) https://bugs.python.org/issue27177

   (15) https://bugs.python.org/issue26754

   (16) https://bugs.python.org/issue26536

   (17) https://bugs.python.org/issue27048

   (18) https://bugs.python.org/issue27330

   (19) https://bugs.python.org/issue27238

   (20) https://bugs.python.org/issue27122

   (21) https://www.python.org/dev/peps/pep-0479


File: python.info,  Node: Security<28>,  Next: Library<55>,  Prev: Library<54>,  Up: Python 3 6 0 alpha 3

1.18.62.3 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27278


File: python.info,  Node: Library<55>,  Next: Security<29>,  Prev: Security<28>,  Up: Python 3 6 0 alpha 3

1.18.62.4 Library
.................

   - bpo-16864(1): sqlite3.Cursor.lastrowid now supports REPLACE
     statement.  Initial patch by Alex LordThorsen.

   - bpo-26386(2): Fixed ttk.TreeView selection operations with item
     id’s containing spaces.

   - bpo-8637(3): Honor a pager set by the env var MANPAGER (in
     preference to one set by the env var PAGER).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16864

   (2) https://bugs.python.org/issue26386

   (3) https://bugs.python.org/issue8637


File: python.info,  Node: Security<29>,  Next: Library<56>,  Prev: Library<55>,  Up: Python 3 6 0 alpha 3

1.18.62.5 Security
..................

   - bpo-22636(1): Avoid shell injection problems with
     ctypes.util.find_library().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22636


File: python.info,  Node: Library<56>,  Next: IDLE<44>,  Prev: Security<29>,  Up: Python 3 6 0 alpha 3

1.18.62.6 Library
.................

   - bpo-16182(1): 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(2): Add loop.connect_accepted_socket().  Patch by Jim
     Fulton.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16182

   (2) https://bugs.python.org/issue27392


File: python.info,  Node: IDLE<44>,  Next: C API<31>,  Prev: Library<56>,  Up: Python 3 6 0 alpha 3

1.18.62.7 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/issue27477

   (2) https://bugs.python.org/issue27173

   (3) https://bugs.python.org/issue27452

   (4) https://bugs.python.org/issue27452

   (5) https://bugs.python.org/issue27380

   (6) https://bugs.python.org/issue27372

   (7) https://bugs.python.org/issue27365

   (8) https://bugs.python.org/issue27245

   (9) https://bugs.python.org/issue24137

   (10) https://bugs.python.org/issue27310


File: python.info,  Node: C API<31>,  Next: Build<42>,  Prev: IDLE<44>,  Up: Python 3 6 0 alpha 3

1.18.62.8 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/issue26754


File: python.info,  Node: Build<42>,  Next: Tools/Demos<27>,  Prev: C API<31>,  Up: Python 3 6 0 alpha 3

1.18.62.9 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/issue28066

   (2) https://bugs.python.org/issue27442

   (3) https://bugs.python.org/issue27434

   (4) https://bugs.python.org/issue26930

   (5) https://bugs.python.org/issue23968


File: python.info,  Node: Tools/Demos<27>,  Next: Documentation<43>,  Prev: Build<42>,  Up: Python 3 6 0 alpha 3

1.18.62.10 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/issue27332

   (2) https://bugs.python.org/issue27418


File: python.info,  Node: Documentation<43>,  Next: Tests<41>,  Prev: Tools/Demos<27>,  Up: Python 3 6 0 alpha 3

1.18.62.11 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/issue19489

   (2) https://bugs.python.org/issue27285


File: python.info,  Node: Tests<41>,  Prev: Documentation<43>,  Up: Python 3 6 0 alpha 3

1.18.62.12 Tests
................

   - bpo-27027(1): Added test.support.is_android that is True when this
     is an Android build.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27027


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.18.63 Python 3.6.0 alpha 2
----------------------------

`Release date: 2016-06-13'

* Menu:

* Core and Builtins: Core and Builtins<54>.
* Library: Library<57>.
* Security: Security<30>.
* Library: Library<58>.
* Security: Security<31>.
* Library: Library<59>.
* IDLE: IDLE<45>.
* Documentation: Documentation<44>.
* Tests: Tests<42>.
* Windows: Windows<41>.
* Build: Build<43>.
* Windows: Windows<42>.
* C API: C API<32>.
* Tools/Demos: Tools/Demos<28>.


File: python.info,  Node: Core and Builtins<54>,  Next: Library<57>,  Up: Python 3 6 0 alpha 2

1.18.63.1 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/issue27095

   (2) https://bugs.python.org/issue27190

   (3) https://bugs.python.org/issue27286

   (4) https://bugs.python.org/issue27140

   (5) https://bugs.python.org/issue27186

   (6) https://www.python.org/dev/peps/pep-0519

   (7) https://bugs.python.org/issue27066

   (8) https://bugs.python.org/issue26983

   (9) https://bugs.python.org/issue27097

   (10) https://bugs.python.org/issue26647

   (11) https://bugs.python.org/issue23275

   (12) https://bugs.python.org/issue27243


File: python.info,  Node: Library<57>,  Next: Security<30>,  Prev: Core and Builtins<54>,  Up: Python 3 6 0 alpha 2

1.18.63.2 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27025

   (2) https://bugs.python.org/issue25455

   (3) https://bugs.python.org/issue27294

   (4) https://bugs.python.org/issue20508


File: python.info,  Node: Security<30>,  Next: Library<58>,  Prev: Library<57>,  Up: Python 3 6 0 alpha 2

1.18.63.3 Security
..................

   - bpo-26556(1): Update expat to 2.1.1, fixes CVE-2015-1283.

   - Fix TLS stripping vulnerability in smtplib, CVE-2016-0772.
     Reported by Team Oststrom.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26556


File: python.info,  Node: Library<58>,  Next: Security<31>,  Prev: Security<30>,  Up: Python 3 6 0 alpha 2

1.18.63.4 Library
.................

   - bpo-21386(1): Implement missing IPv4Address.is_global property.  It
     was documented since 07a5610bae9d.  Initial patch by Roger Luethi.

   - bpo-27029(2): Removed deprecated support of universal newlines mode
     from ZipFile.open().

   - bpo-27030(3): 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(4): Add os.PathLike support to DirEntry (part of PEP
     519(5)).  Initial patch by Jelle Zijlstra.

   - bpo-20900(6): distutils register command now decodes HTTP responses
     correctly.  Initial patch by ingrid.

   - bpo-27186(7): Add os.PathLike support to pathlib, removing its
     provisional status (part of PEP 519).  Initial patch by Dusty
     Phillips.

   - bpo-27186(8): Add support for os.PathLike objects to os.fsencode()
     and os.fsdecode() (part of PEP 519(9)).

   - bpo-27186(10): Introduce os.PathLike and os.fspath() (part of PEP
     519(11)).

   - 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(12)
     (Awaitable, AsyncIterable, AsyncIterator) have been added (in fact
     they made it into 3.5.1 but were never mentioned).

   - bpo-25738(13): 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(14): Fix the "platform" module to tolerate when
     sys.version contains truncated build information.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue21386

   (2) https://bugs.python.org/issue27029

   (3) https://bugs.python.org/issue27030

   (4) https://bugs.python.org/issue27186

   (5) https://www.python.org/dev/peps/pep-0519

   (6) https://bugs.python.org/issue20900

   (7) https://bugs.python.org/issue27186

   (8) https://bugs.python.org/issue27186

   (9) https://www.python.org/dev/peps/pep-0519

   (10) https://bugs.python.org/issue27186

   (11) https://www.python.org/dev/peps/pep-0519

   (12) https://www.python.org/dev/peps/pep-0492

   (13) https://bugs.python.org/issue25738

   (14) https://bugs.python.org/issue21313


File: python.info,  Node: Security<31>,  Next: Library<59>,  Prev: Library<58>,  Up: Python 3 6 0 alpha 2

1.18.63.5 Security
..................

   - bpo-26839(1): On Linux, *note os.urandom(): 4d6. 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/issue26839


File: python.info,  Node: Library<59>,  Next: IDLE<45>,  Prev: Security<31>,  Up: Python 3 6 0 alpha 2

1.18.63.6 Library
.................

   - bpo-23883(1): 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(2): In the zlib module, allow decompressing raw Deflate
     streams with a predefined zdict.  Based on patch by Xiang Zhang.

   - bpo-24291(3): 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(4): Use _sysconfigdata.py to initialize
     distutils.sysconfig.

   - bpo-19611(5): *note inspect: a1. 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(6): Add ‘__all__’ to *note string: f7.  Patch by Emanuel
     Barry.

   - bpo-26373(7): 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(8): Clarify the subprocess.CalledProcessError error
     message text when the child process died due to a signal.

   - bpo-25931(9): Don’t define socketserver.Forking* names on platforms
     such as Windows that do not support os.fork().

   - bpo-21776(10): distutils.upload now correctly handles HTTPError.
     Initial patch by Claudiu Popa.

   - bpo-26526(11): Replace custom parse tree validation in the parser
     module with a simple DFA validator.

   - bpo-27114(12): Fix SSLContext._load_windows_store_certs fails with
     PermissionError

   - bpo-18383(13): Avoid creating duplicate filters when using
     filterwarnings and simplefilter.  Based on patch by Alex Shkop.

   - bpo-23026(14): winreg.QueryValueEx() now return an integer for
     REG_QWORD type.

   - bpo-26741(15): subprocess.Popen destructor now emits a
     ResourceWarning warning if the child process is still running.

   - bpo-27056(16): Optimize pickle.load() and pickle.loads(), up to 10%
     faster to deserialize a lot of small objects.

   - bpo-21271(17): New keyword only parameters in reset_mock call.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23883

   (2) https://bugs.python.org/issue27164

   (3) https://bugs.python.org/issue24291

   (4) https://bugs.python.org/issue21272

   (5) https://bugs.python.org/issue19611

   (6) https://bugs.python.org/issue26809

   (7) https://bugs.python.org/issue26373

   (8) https://bugs.python.org/issue27167

   (9) https://bugs.python.org/issue25931

   (10) https://bugs.python.org/issue21776

   (11) https://bugs.python.org/issue26526

   (12) https://bugs.python.org/issue27114

   (13) https://bugs.python.org/issue18383

   (14) https://bugs.python.org/issue23026

   (15) https://bugs.python.org/issue26741

   (16) https://bugs.python.org/issue27056

   (17) https://bugs.python.org/issue21271


File: python.info,  Node: IDLE<45>,  Next: Documentation<44>,  Prev: Library<59>,  Up: Python 3 6 0 alpha 2

1.18.63.7 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/issue5124

   (2) https://bugs.python.org/issue24750

   (3) https://bugs.python.org/issue24759

   (4) https://bugs.python.org/issue27239

   (5) https://bugs.python.org/issue27262

   (6) https://bugs.python.org/issue24759

   (7) https://bugs.python.org/issue27196

   (8) https://bugs.python.org/issue20567

   (9) https://bugs.python.org/issue24225

   (10) https://bugs.python.org/issue27156

   (11) https://bugs.python.org/issue27117

   (12) https://bugs.python.org/issue24225

   (13) https://bugs.python.org/issue26673

   (14) https://bugs.python.org/issue21939

   (15) https://bugs.python.org/issue21676

   (16) https://bugs.python.org/issue18410

   (17) https://bugs.python.org/issue21703

   (18) https://bugs.python.org/issue27044

   (19) https://bugs.python.org/issue23977


File: python.info,  Node: Documentation<44>,  Next: Tests<42>,  Prev: IDLE<45>,  Up: Python 3 6 0 alpha 2

1.18.63.8 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/issue16484

   (2) https://bugs.python.org/issue24136

   (3) https://www.python.org/dev/peps/pep-0448

   (4) https://bugs.python.org/issue22558


File: python.info,  Node: Tests<42>,  Next: Windows<41>,  Prev: Documentation<44>,  Up: Python 3 6 0 alpha 2

1.18.63.9 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/issue25285

   (2) https://bugs.python.org/issue25285


File: python.info,  Node: Windows<41>,  Next: Build<43>,  Prev: Tests<42>,  Up: Python 3 6 0 alpha 2

1.18.63.10 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27064


File: python.info,  Node: Build<43>,  Next: Windows<42>,  Prev: Windows<41>,  Up: Python 3 6 0 alpha 2

1.18.63.11 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/issue27229

   (2) https://bugs.python.org/issue26930


File: python.info,  Node: Windows<42>,  Next: C API<32>,  Prev: Build<43>,  Up: Python 3 6 0 alpha 2

1.18.63.12 Windows
..................

   - bpo-17500(1): Remove unused and outdated icons.  (See also:
     ‘https://github.com/python/pythondotorg/issues/945’)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17500


File: python.info,  Node: C API<32>,  Next: Tools/Demos<28>,  Prev: Windows<42>,  Up: Python 3 6 0 alpha 2

1.18.63.13 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/issue27186

   (2) https://www.python.org/dev/peps/pep-0519

   (3) https://bugs.python.org/issue26282


File: python.info,  Node: Tools/Demos<28>,  Prev: C API<32>,  Up: Python 3 6 0 alpha 2

1.18.63.14 Tools/Demos
......................

   - bpo-26282(1): Argument Clinic now supports positional-only and
     keyword parameters in the same function.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26282


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.18.64 Python 3.6.0 alpha 1
----------------------------

`Release date: 2016-05-16'

* Menu:

* Core and Builtins: Core and Builtins<55>.
* Library: Library<60>.
* Security: Security<32>.
* Library: Library<61>.
* Security: Security<33>.
* Library: Library<62>.
* Security: Security<34>.
* Library: Library<63>.
* IDLE: IDLE<46>.
* Documentation: Documentation<45>.
* Tests: Tests<43>.
* Build: Build<44>.
* Windows: Windows<43>.
* Tools/Demos: Tools/Demos<29>.
* C API: C API<33>.


File: python.info,  Node: Core and Builtins<55>,  Next: Library<60>,  Up: Python 3 6 0 alpha 1

1.18.64.1 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(): 50a.
     domain (*note PYMEM_DOMAIN_MEM: 50e.) now use the *note pymalloc
     allocator: 5c6. rather than system ‘malloc()’.  Applications
     calling *note PyMem_Malloc(): 50a. 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(): 50a. family
     are called without holding the GIL.

   - bpo-26564(25): On error, the debug hooks on Python memory
     allocators now use the *note tracemalloc: 115. module to get the
     traceback where a memory block was allocated.

   - bpo-26558(26): The debug hooks on Python memory allocator *note
     PyObject_Malloc(): 50d. now detect when functions are called
     without holding the GIL.

   - bpo-26516(27): Add *note PYTHONMALLOC: 508. environment variable to
     set the Python memory allocators and/or install debug hooks.

   - bpo-26516(28): The *note PyMem_SetupDebugHooks(): 50f. function can
     now also be used on Python compiled in release mode.

   - bpo-26516(29): The *note PYTHONMALLOCSTATS: 1167. 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/issue20041

   (2) https://bugs.python.org/issue26168

   (3) https://bugs.python.org/issue26991

   (4) https://bugs.python.org/issue27039

   (5) https://bugs.python.org/issue23640

   (6) https://bugs.python.org/issue27005

   (7) https://bugs.python.org/issue18531

   (8) https://bugs.python.org/issue26811

   (9) https://bugs.python.org/issue20120

   (10) https://bugs.python.org/issue26249

   (11) https://bugs.python.org/issue26802

   (12) https://bugs.python.org/issue26659

   (13) https://bugs.python.org/issue26718

   (14) https://bugs.python.org/issue27138

   (15) https://bugs.python.org/issue27147

   (16) https://www.python.org/dev/peps/pep-0420

   (17) https://bugs.python.org/issue25339

   (18) https://bugs.python.org/issue26494

   (19) https://bugs.python.org/issue26574

   (20) https://bugs.python.org/issue26581

   (21) https://bugs.python.org/issue19711

   (22) https://bugs.python.org/issue21099

   (23) https://www.python.org/dev/peps/pep-0451

   (24) https://bugs.python.org/issue26563

   (25) https://bugs.python.org/issue26564

   (26) https://bugs.python.org/issue26558

   (27) https://bugs.python.org/issue26516

   (28) https://bugs.python.org/issue26516

   (29) https://bugs.python.org/issue26516

   (30) https://bugs.python.org/issue26516

   (31) https://bugs.python.org/issue26464

   (32) https://bugs.python.org/issue22836

   (33) https://bugs.python.org/issue26302

   (34) https://bugs.python.org/issue26136

   (35) https://bugs.python.org/issue26204

   (36) https://bugs.python.org/issue4806

   (37) https://bugs.python.org/issue26146

   (38) https://bugs.python.org/issue23601

   (39) https://bugs.python.org/issue18018

   (40) https://bugs.python.org/issue25843

   (41) https://bugs.python.org/issue26107

   (42) https://bugs.python.org/issue26154

   (43) https://bugs.python.org/issue25791

   (44) https://bugs.python.org/issue22995

   (45) https://bugs.python.org/issue25961

   (46) https://bugs.python.org/issue25973

   (47) https://bugs.python.org/issue22995

   (48) https://bugs.python.org/issue20440

   (49) https://bugs.python.org/issue25766

   (50) https://bugs.python.org/issue25421

   (51) https://bugs.python.org/issue25709

   (52) https://bugs.python.org/issue5319

   (53) https://bugs.python.org/issue25485

   (54) https://bugs.python.org/issue24097

   (55) https://bugs.python.org/issue24731

   (56) https://bugs.python.org/issue25630

   (57) https://bugs.python.org/issue23564

   (58) https://bugs.python.org/issue25388

   (59) https://bugs.python.org/issue25462

   (60) https://bugs.python.org/issue22995

   (61) https://bugs.python.org/issue24802

   (62) https://bugs.python.org/issue25555

   (63) https://bugs.python.org/issue24726

   (64) https://bugs.python.org/issue25449

   (65) https://bugs.python.org/issue25395

   (66) https://bugs.python.org/issue25401

   (67) https://bugs.python.org/issue25399

   (68) https://bugs.python.org/issue25274

   (69) https://bugs.python.org/issue24402

   (70) https://bugs.python.org/issue25349

   (71) https://bugs.python.org/issue24806

   (72) https://bugs.python.org/issue25301

   (73) https://bugs.python.org/issue24848

   (74) https://bugs.python.org/issue25267

   (75) https://bugs.python.org/issue25280

   (76) https://bugs.python.org/issue25227

   (77) https://bugs.python.org/issue25003

   (78) https://bugs.python.org/issue9232

   (79) https://bugs.python.org/issue24965

   (80) https://www.python.org/dev/peps/pep-0498

   (81) https://bugs.python.org/issue26478

   (82) https://bugs.python.org/issue26171

   (83) https://bugs.python.org/issue25660

   (84) https://bugs.python.org/issue26288

   (85) https://bugs.python.org/issue26289

   (86) https://bugs.python.org/issue26315

   (87) https://bugs.python.org/issue25887


File: python.info,  Node: Library<60>,  Next: Security<32>,  Prev: Core and Builtins<55>,  Up: Python 3 6 0 alpha 1

1.18.64.2 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(): a4f, catch *note AttributeError: 3a0.
     instead of *note NameError: d80.  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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27057

   (2) https://bugs.python.org/issue27014

   (3) https://bugs.python.org/issue27031

   (4) https://bugs.python.org/issue14132

   (5) https://bugs.python.org/issue17214

   (6) https://bugs.python.org/issue27033

   (7) https://bugs.python.org/issue27034

   (8) https://bugs.python.org/issue26870

   (9) https://bugs.python.org/issue26039

   (10) https://bugs.python.org/issue26892

   (11) https://bugs.python.org/issue22274

   (12) https://bugs.python.org/issue26807

   (13) https://bugs.python.org/issue25745

   (14) https://bugs.python.org/issue26977

   (15) https://bugs.python.org/issue26002

   (16) https://bugs.python.org/issue25974

   (17) https://bugs.python.org/issue26996

   (18) https://www.python.org/dev/peps/pep-0506

   (19) https://bugs.python.org/issue26881

   (20) https://bugs.python.org/issue23815

   (21) https://bugs.python.org/issue17765

   (22) https://bugs.python.org/issue26873

   (23) https://bugs.python.org/issue26915

   (24) https://bugs.python.org/issue26711

   (25) https://bugs.python.org/issue24114

   (26) https://bugs.python.org/issue26864

   (27) https://bugs.python.org/issue24902

   (28) https://bugs.python.org/issue25788

   (29) https://bugs.python.org/issue26634

   (30) https://bugs.python.org/issue26804

   (31) https://bugs.python.org/issue26837

   (32) https://bugs.python.org/issue26041

   (33) https://bugs.python.org/issue26822

   (34) https://bugs.python.org/issue26733

   (35) https://bugs.python.org/issue26801

   (36) https://bugs.python.org/issue24838


File: python.info,  Node: Security<32>,  Next: Library<61>,  Prev: Library<60>,  Up: Python 3 6 0 alpha 1

1.18.64.3 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26657


File: python.info,  Node: Library<61>,  Next: Security<33>,  Prev: Security<32>,  Up: Python 3 6 0 alpha 1

1.18.64.4 Library
.................

   - bpo-26717(1): Stop encoding Latin-1-ized WSGI paths with UTF-8.
     Patch by Anthony Sottile.

   - bpo-26782(2): Add STARTUPINFO to subprocess.__all__ on Windows.

   - bpo-26404(3): Add context manager to socketserver.  Patch by Aviv
     Palivoda.

   - bpo-26735(4): Fix *note os.urandom(): 4d6. 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(5): Eliminate http.server._quote_html() and use
     html.escape(quote=False).  Patch by Xiang Zhang.

   - bpo-26685(6): Raise OSError if closing a socket fails.

   - bpo-16329(7): Add .webm to mimetypes.types_map.  Patch by Giampaolo
     Rodola’.

   - bpo-13952(8): Add .csv to mimetypes.types_map.  Patch by Geoff
     Wilson.

   - bpo-26587(9): the site module now allows .pth files to specify
     files to be added to sys.path (e.g.  zip files).

   - bpo-25609(10): Introduce contextlib.AbstractContextManager and
     typing.ContextManager.

   - bpo-26709(11): Fixed Y2038 problem in loading binary PLists.

   - bpo-23735(12): Handle terminal resizing with Readline 6.3+ by
     installing our own SIGWINCH handler.  Patch by Eric Price.

   - bpo-25951(13): Change SSLSocket.sendall() to return None, as
     explicitly documented for plain socket objects.  Patch by Aviv
     Palivoda.

   - bpo-26586(14): 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(15): Added missing XMLPullParser to ElementTree.__all__.

   - bpo-22854(16): Change BufferedReader.writable() and
     BufferedWriter.readable() to always return False.

   - bpo-26492(17): 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(18): doctest.DocFileTest and doctest.testfile() now
     support packages (module splitted into multiple directories) for
     the package parameter.

   - bpo-25195(19): 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(20): Raise ValueError rather than SystemError when a
     negative length is passed to SSLSocket.recv() or read().

   - bpo-23804(21): Fix SSL recv(0) and read(0) methods to return zero
     bytes instead of up to 1024.

   - bpo-26616(22): Fixed a bug in datetime.astimezone() method.

   - bpo-26637(23): The *note importlib: 9b. module now emits an *note
     ImportError: 339. rather than a *note TypeError: 193. if *note
     __import__(): 615. is tried during the Python shutdown process but
     *note sys.path: 48d. is already cleared (set to ‘None’).

   - bpo-21925(24): *note warnings.formatwarning(): ff7. now catches
     exceptions when calling *note linecache.getline(): 70e. and *note
     tracemalloc.get_object_traceback(): 116b. to be able to log *note
     ResourceWarning: 4d5. emitted late during the Python shutdown
     process.

   - bpo-23848(25): 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(26): Add C functions ‘_PyTraceMalloc_Track()’ and
     ‘_PyTraceMalloc_Untrack()’ to track memory blocks using the *note
     tracemalloc: 115. module.  Add ‘_PyTraceMalloc_GetTraceback()’ to
     get the traceback of an object.

   - bpo-26588(27): The _tracemalloc now supports tracing memory
     allocations of multiple address spaces (domains).

   - bpo-24266(28): Ctrl+C during Readline history search now cancels
     the search mode when compiled with Readline 7.

   - bpo-26590(29): Implement a safe finalizer for the _socket.socket
     type.  It now releases the GIL to close the socket.

   - bpo-18787(30): spwd.getspnam() now raises a PermissionError if the
     user doesn’t have privileges.

   - bpo-26560(31): Avoid potential ValueError in
     BaseHandler.start_response.  Initial patch by Peter Inglesby.

   - bpo-26567(32): Add a new function *note PyErr_ResourceWarning():
     5d1. 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26717

   (2) https://bugs.python.org/issue26782

   (3) https://bugs.python.org/issue26404

   (4) https://bugs.python.org/issue26735

   (5) https://bugs.python.org/issue26585

   (6) https://bugs.python.org/issue26685

   (7) https://bugs.python.org/issue16329

   (8) https://bugs.python.org/issue13952

   (9) https://bugs.python.org/issue26587

   (10) https://bugs.python.org/issue25609

   (11) https://bugs.python.org/issue26709

   (12) https://bugs.python.org/issue23735

   (13) https://bugs.python.org/issue25951

   (14) https://bugs.python.org/issue26586

   (15) https://bugs.python.org/issue26676

   (16) https://bugs.python.org/issue22854

   (17) https://bugs.python.org/issue26492

   (18) https://bugs.python.org/issue26641

   (19) https://bugs.python.org/issue25195

   (20) https://bugs.python.org/issue26644

   (21) https://bugs.python.org/issue23804

   (22) https://bugs.python.org/issue26616

   (23) https://bugs.python.org/issue26637

   (24) https://bugs.python.org/issue21925

   (25) https://bugs.python.org/issue23848

   (26) https://bugs.python.org/issue26530

   (27) https://bugs.python.org/issue26588

   (28) https://bugs.python.org/issue24266

   (29) https://bugs.python.org/issue26590

   (30) https://bugs.python.org/issue18787

   (31) https://bugs.python.org/issue26560

   (32) https://bugs.python.org/issue26567


File: python.info,  Node: Security<33>,  Next: Library<62>,  Prev: Library<61>,  Up: Python 3 6 0 alpha 1

1.18.64.5 Security
..................

   - bpo-26313(1): ssl.py _load_windows_store_certs fails if windows
     cert store is empty.  Patch by Baji.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26313


File: python.info,  Node: Library<62>,  Next: Security<34>,  Prev: Security<33>,  Up: Python 3 6 0 alpha 1

1.18.64.6 Library
.................

   - bpo-26569(1): Fix *note pyclbr.readmodule(): 116e. and *note
     pyclbr.readmodule_ex(): 116f. to support importing packages.

   - bpo-26499(2): 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(3): Handle sockets in directories unittest discovery is
     scanning.  Patch from Victor van den Elzen.

   - bpo-16181(4): cookiejar.http2time() now returns None if year is
     higher than datetime.MAXYEAR.

   - bpo-26513(5): Fixes platform module detection of Windows Server

   - bpo-23718(6): Fixed parsing time in week 0 before Jan 1.  Original
     patch by Tamás Bence Gedai.

   - bpo-26323(7): Add Mock.assert_called() and
     Mock.assert_called_once() methods to unittest.mock.  Patch written
     by Amit Saha.

   - bpo-20589(8): Invoking Path.owner() and Path.group() on Windows now
     raise NotImplementedError instead of ImportError.

   - bpo-26177(9): Fixed the keys() method for Canvas and Scrollbar
     widgets.

   - bpo-15068(10): Got rid of excessive buffering in fileinput.  The
     bufsize parameter is now deprecated and ignored.

   - bpo-19475(11): Added an optional argument timespec to the datetime
     isoformat() method to choose the precision of the time component.

   - bpo-2202(12): Fix UnboundLocalError in
     AbstractDigestAuthHandler.get_algorithm_impls.  Initial patch by
     Mathieu Dupuy.

   - bpo-26167(13): Minimized overhead in copy.copy() and
     copy.deepcopy().  Optimized copying and deepcopying bytearrays,
     NotImplemented, slices, short lists, tuples, dicts, sets.

   - bpo-25718(14): Fixed pickling and copying the accumulate() iterator
     with total is None.

   - bpo-26475(15): Fixed debugging output for regular expressions with
     the (?x) flag.

   - bpo-26482(16): Allowed pickling recursive dequeues.

   - bpo-26335(17): Make mmap.write() return the number of bytes written
     like other write methods.  Patch by Jakub Stasiak.

   - bpo-26457(18): 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(19): Remove the file if the internal open() call in
     NamedTemporaryFile() fails.  Patch by Silent Ghost.

   - bpo-26402(20): 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(21): Leading ‘<~’ is optional now in base64.a85decode()
     with adobe=True.  Patch by Swati Jaiswal.

   - bpo-26186(22): Remove an invalid type check in
     importlib.util.LazyLoader.

   - bpo-26367(23): importlib.__import__() raises ImportError like
     builtins.__import__() when ‘level’ is specified but without an
     accompanying package specified.

   - bpo-26309(24): In the "socketserver" module, shut down the request
     (closing the connected socket) when verify_request() returns false.
     Patch by Aviv Palivoda.

   - bpo-23430(25): 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26569

   (2) https://bugs.python.org/issue26499

   (3) https://bugs.python.org/issue25320

   (4) https://bugs.python.org/issue16181

   (5) https://bugs.python.org/issue26513

   (6) https://bugs.python.org/issue23718

   (7) https://bugs.python.org/issue26323

   (8) https://bugs.python.org/issue20589

   (9) https://bugs.python.org/issue26177

   (10) https://bugs.python.org/issue15068

   (11) https://bugs.python.org/issue19475

   (12) https://bugs.python.org/issue2202

   (13) https://bugs.python.org/issue26167

   (14) https://bugs.python.org/issue25718

   (15) https://bugs.python.org/issue26475

   (16) https://bugs.python.org/issue26482

   (17) https://bugs.python.org/issue26335

   (18) https://bugs.python.org/issue26457

   (19) https://bugs.python.org/issue26385

   (20) https://bugs.python.org/issue26402

   (21) https://bugs.python.org/issue25913

   (22) https://bugs.python.org/issue26186

   (23) https://bugs.python.org/issue26367

   (24) https://bugs.python.org/issue26309

   (25) https://bugs.python.org/issue23430


File: python.info,  Node: Security<34>,  Next: Library<63>,  Prev: Library<62>,  Up: Python 3 6 0 alpha 1

1.18.64.7 Security
..................

   - bpo-25939(1): On Windows open the cert store readonly in
     ssl.enum_certificates.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25939


File: python.info,  Node: Library<63>,  Next: IDLE<46>,  Prev: Security<34>,  Up: Python 3 6 0 alpha 1

1.18.64.8 Library
.................

   - bpo-25995(1): os.walk() no longer uses FDs proportional to the tree
     depth.

   - bpo-25994(2): Added the close() method and the support of the
     context manager protocol for the os.scandir() iterator.

   - bpo-23992(3): multiprocessing: make MapResult not fail-fast upon
     exception.

   - bpo-26243(4): Support keyword arguments to zlib.compress().  Patch
     by Aviv Palivoda.

   - bpo-26117(5): The os.scandir() iterator now closes file descriptor
     not only when the iteration is finished, but when it was failed
     with error.

   - bpo-25949(6): __dict__ for an OrderedDict instance is now created
     only when needed.

   - bpo-25911(7): Restored support of bytes paths in os.walk() on
     Windows.

   - bpo-26045(8): Add UTF-8 suggestion to error message when posting a
     non-Latin-1 string with http.client.

   - bpo-26039(9): Added zipfile.ZipInfo.from_file() and
     zipinfo.ZipInfo.is_dir().  Patch by Thomas Kluyver.

   - bpo-12923(10): Reset FancyURLopener’s redirect counter even if
     there is an exception.  Based on patches by Brian Brazil and Daniel
     Rocco.

   - bpo-25945(11): 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(12): copy.deepcopy() now correctly copies range() objects
     with non-atomic attributes.

   - bpo-23076(13): Path.glob() now raises a ValueError if it’s called
     with an invalid pattern.  Patch by Thomas Nyberg.

   - bpo-19883(14): Fixed possible integer overflows in zipimport.

   - bpo-26227(15): 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(16): 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(17): xmlrpc now works with strings not encodable with
     used non-UTF-8 encoding.

   - bpo-25935(18): Garbage collector now breaks reference loops with
     OrderedDict.

   - bpo-16620(19): Fixed AttributeError in msilib.Directory.glob().

   - bpo-26013(20): Added compatibility with broken protocol 2 pickles
     created in old Python 3 versions (3.4.3 and lower).

   - bpo-26129(21): Deprecated accepting non-integers in grp.getgrgid().

   - bpo-25850(22): Use cross-compilation by default for 64-bit Windows.

   - bpo-25822(23): Add docstrings to the fields of urllib.parse
     results.  Patch contributed by Swati Jaiswal.

   - bpo-22642(24): Convert trace module option parsing mechanism to
     argparse.  Patch contributed by SilentGhost.

   - bpo-24705(25): Fix sysconfig._parse_makefile not expanding ${} vars
     appearing before $() vars.

   - bpo-26069(26): Remove the deprecated apis in the trace module.

   - bpo-22138(27): Fix mock.patch behavior when patching descriptors.
     Restore original values after patching.  Patch contributed by Sean
     McCully.

   - bpo-25672(28): In the ssl module, enable the
     SSL_MODE_RELEASE_BUFFERS mode option if it is safe to do so.

   - bpo-26012(29): Don’t traverse into symlinks for ‘**’ pattern in
     pathlib.Path.[r]glob().

   - bpo-24120(30): Ignore PermissionError when traversing a tree with
     pathlib.Path.[r]glob().  Patch by Ulrich Petri.

   - bpo-21815(31): 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(32): fileinput now uses sys.stdin as-is if it does not
     have a buffer attribute (restores backward compatibility).

   - bpo-25971(33): Optimized creating Fractions from floats by 2 times
     and from Decimals by 3 times.

   - bpo-25802(34): Document as deprecated the remaining implementations
     of importlib.abc.Loader.load_module().

   - bpo-25928(35): Add Decimal.as_integer_ratio().

   - bpo-25447(36): 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(37): Have the functions in compileall return booleans
     instead of ints and add proper documentation and tests for the
     return values.

   - bpo-24103(38): Fixed possible use after free in
     ElementTree.XMLPullParser.

   - bpo-25860(39): os.fwalk() no longer skips remaining directories
     when error occurs.  Original patch by Samson Lee.

   - bpo-25914(40): Fixed and simplified OrderedDict.__sizeof__.

   - bpo-25869(41): Optimized deepcopying ElementTree; it is now 20
     times faster.

   - bpo-25873(42): 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(43): Fixed various refcount issues in ElementTree
     iteration.

   - bpo-22227(44): The TarFile iterator is reimplemented using
     generator.  This implementation is simpler that using class.

   - bpo-25638(45): Optimized ElementTree.iterparse(); it is now 2x
     faster.  Optimized ElementTree parsing; it is now 10% faster.

   - bpo-25761(46): Improved detecting errors in broken pickle data.

   - bpo-25717(47): 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(48): 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(49): In the subprocess module, preserve any exception
     caused by fork() failure when preexec_fn is used.

   - bpo-25771(50): Tweak the exception message for
     importlib.util.resolve_name() when ’package’ isn’t specified but
     necessary.

   - bpo-6478(51): _strptime’s regexp cache now is reset after changing
     timezone with time.tzset().

   - bpo-14285(52): 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(53): 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(54): 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(55): Fixed copying object with state with boolean value
     is false.

   - bpo-10131(56): Fixed deep copying of minidom documents.  Based on
     patch by Marian Ganisin.

   - bpo-7990(57): dir() on ElementTree.Element now lists properties:
     "tag", "text", "tail" and "attrib".  Original patch by Santoso
     Wijaya.

   - bpo-25725(58): Fixed a reference leak in pickle.loads() when
     unpickling invalid data including tuple instructions.

   - bpo-25663(59): In the Readline completer, avoid listing duplicate
     global names, and search the global namespace before searching
     builtins.

   - bpo-25688(60): Fixed file leak in ElementTree.iterparse() raising
     an error.

   - bpo-23914(61): Fixed SystemError raised by unpickler on broken
     pickle data.

   - bpo-25691(62): Fixed crash on deleting ElementTree.Element
     attributes.

   - bpo-25624(63): ZipFile now always writes a ZIP_STORED header for
     directory entries.  Patch by Dingyuan Wang.

   - bpo-25626(64): 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(65): Avoid incorrect errors raised by
     os.makedirs(exist_ok=True) when the OS gives priority to errors
     such as EACCES over EEXIST.

   - bpo-25593(66): Change semantics of EventLoop.stop() in asyncio.

   - bpo-6973(67): 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(68): 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(69): 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(70): 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(71): Added "escape" to the __all__ list in the glob
     module.

   - bpo-25584(72): Fixed recursive glob() with patterns starting with
     ‘**’.

   - bpo-25446(73): Fix regression in smtplib’s AUTH LOGIN support.

   - bpo-18010(74): Fix the pydoc web server’s module search function to
     handle exceptions from importing packages.

   - bpo-25554(75): Got rid of circular references in regular expression
     parsing.

   - bpo-18973(76): Command-line interface of the calendar module now
     uses argparse instead of optparse.

   - bpo-25510(77): 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(78): Fixed inspect.getdoc() for inherited docstrings of
     properties.  Original patch by John Mark Vandenberg.

   - bpo-25515(79): Always use os.urandom as a source of randomness in
     uuid.uuid4.

   - bpo-21827(80): 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(81): The lru_cache() wrapper objects now can be copied
     and pickled (by returning the original object unchanged).

   - bpo-25390(82): typing: Don’t crash on Union[str, Pattern].

   - bpo-25441(83): asyncio: Raise error from drain() when socket is
     closed.

   - bpo-25410(84): Cleaned up and fixed minor bugs in C implementation
     of OrderedDict.

   - bpo-25411(85): 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(86): Remove mentions of the formatter module being
     removed in Python 3.6.

   - bpo-25406(87): 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(88): pickletools.dis() now outputs implicit memo index
     for the MEMOIZE opcode.

   - bpo-25357(89): Add an optional newline parameter to
     binascii.b2a_base64().  base64.b64encode() uses it to avoid a
     memory copy.

   - bpo-24164(90): Objects that need calling ‘__new__’ with keyword
     arguments, can now be pickled using pickle protocols older than
     protocol version 4.

   - bpo-25364(91): zipfile now works in threads disabled builds.

   - bpo-25328(92): smtpd’s SMTPChannel now correctly raises a
     ValueError if both decode_data and enable_SMTPUTF8 are set to true.

   - bpo-16099(93): RobotFileParser now supports Crawl-delay and
     Request-rate extensions.  Patch by Nikolay Bogoychev.

   - bpo-25316(94): distutils raises OSError instead of
     DistutilsPlatformError when MSVC is not installed.

   - bpo-25380(95): Fixed protocol for the STACK_GLOBAL opcode in
     pickletools.opcodes.

   - bpo-23972(96): 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(97): 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(98): Fix CGIRequestHandler to split the query from the
     URL at the first question mark (?)  rather than the last.  Patch
     from Xiang Zhang.

   - bpo-24657(99): Prevent CGIRequestHandler from collapsing slashes in
     the query part of the URL as if it were a path.  Patch from Xiang
     Zhang.

   - bpo-25287(100): 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(101): Default implementation of tzinfo.fromutc() was
     returning wrong results in some cases.

   - bpo-25203(102): Failed readline.set_completer_delims() no longer
     left the module in inconsistent state.

   - bpo-25011(103): rlcompleter now omits private and special attribute
     names unless the prefix starts with underscores.

   - bpo-25209(104): rlcompleter now can add a space or a colon after
     completed keyword.

   - bpo-22241(105): timezone.utc name is now plain ’UTC’, not
     ’UTC-00:00’.

   - bpo-23517(106): 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(107): Timeit now warns when there is substantial (4x)
     variance between best and worst times.  Patch from Serhiy
     Storchaka.

   - bpo-24633(108): site-packages/README -> README.txt.

   - bpo-24879(109): 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(110): 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(111): urllib.parse raises ValueError on all invalid
     ports.  Patch by Martin Panter.

   - bpo-24360(112): Improve __repr__ of argparse.Namespace() for
     invalid identifiers.  Patch by Matthias Bussonnier.

   - bpo-23426(113): run_setup was broken in distutils.  Patch from
     Alexander Belopolsky.

   - bpo-13938(114): 2to3 converts StringTypes to a tuple.  Patch from
     Mark Hammond.

   - bpo-2091(115): 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(116): improved tests for zipimporter2.  Patch from Mark
     Lawrence.

   - bpo-18622(117): unittest.mock.mock_open().reset_mock would recurse
     infinitely.  Patch from Nicola Palumbo and Laurent De Buyst.

   - bpo-24426(118): 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(119): unittest.mock side_effects can now be exceptions
     again.  This was a regression vs Python 3.4.  Patch from Ignacio
     Rossi

   - bpo-13248(120): Remove deprecated inspect.getmoduleinfo function.

   - bpo-25578(121): Fix (another) memory leak in
     SSLSocket.getpeercer().

   - bpo-25530(122): Disable the vulnerable SSLv3 protocol by default
     when creating ssl.SSLContext.

   - bpo-25569(123): Fix memory leak in SSLSocket.getpeercert().

   - bpo-25471(124): Sockets returned from accept() shouldn’t appear to
     be nonblocking.

   - bpo-25319(125): 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(126): Add asyncio.StreamReader.readuntil() method.  Patch
     by Марк Коренберг.

   - bpo-25924(127): Avoid unnecessary serialization of getaddrinfo(3)
     calls on OS X versions 10.5 or higher.  Original patch by A. Jesse
     Jiryu Davis.

   - bpo-26406(128): Avoid unnecessary serialization of getaddrinfo(3)
     calls on current versions of OpenBSD and NetBSD. Patch by A. Jesse
     Jiryu Davis.

   - bpo-26848(129): Fix asyncio/subprocess.communicate() to handle
     empty input.  Patch by Jack O’Connor.

   - bpo-27040(130): Add loop.get_exception_handler method

   - bpo-27041(131): asyncio: Add loop.create_future method

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25995

   (2) https://bugs.python.org/issue25994

   (3) https://bugs.python.org/issue23992

   (4) https://bugs.python.org/issue26243

   (5) https://bugs.python.org/issue26117

   (6) https://bugs.python.org/issue25949

   (7) https://bugs.python.org/issue25911

   (8) https://bugs.python.org/issue26045

   (9) https://bugs.python.org/issue26039

   (10) https://bugs.python.org/issue12923

   (11) https://bugs.python.org/issue25945

   (12) https://bugs.python.org/issue26202

   (13) https://bugs.python.org/issue23076

   (14) https://bugs.python.org/issue19883

   (15) https://bugs.python.org/issue26227

   (16) https://bugs.python.org/issue26099

   (17) https://bugs.python.org/issue26147

   (18) https://bugs.python.org/issue25935

   (19) https://bugs.python.org/issue16620

   (20) https://bugs.python.org/issue26013

   (21) https://bugs.python.org/issue26129

   (22) https://bugs.python.org/issue25850

   (23) https://bugs.python.org/issue25822

   (24) https://bugs.python.org/issue22642

   (25) https://bugs.python.org/issue24705

   (26) https://bugs.python.org/issue26069

   (27) https://bugs.python.org/issue22138

   (28) https://bugs.python.org/issue25672

   (29) https://bugs.python.org/issue26012

   (30) https://bugs.python.org/issue24120

   (31) https://bugs.python.org/issue21815

   (32) https://bugs.python.org/issue25447

   (33) https://bugs.python.org/issue25971

   (34) https://bugs.python.org/issue25802

   (35) https://bugs.python.org/issue25928

   (36) https://bugs.python.org/issue25447

   (37) https://bugs.python.org/issue25768

   (38) https://bugs.python.org/issue24103

   (39) https://bugs.python.org/issue25860

   (40) https://bugs.python.org/issue25914

   (41) https://bugs.python.org/issue25869

   (42) https://bugs.python.org/issue25873

   (43) https://bugs.python.org/issue25902

   (44) https://bugs.python.org/issue22227

   (45) https://bugs.python.org/issue25638

   (46) https://bugs.python.org/issue25761

   (47) https://bugs.python.org/issue25717

   (48) https://bugs.python.org/issue24903

   (49) https://bugs.python.org/issue25764

   (50) https://bugs.python.org/issue25771

   (51) https://bugs.python.org/issue6478

   (52) https://bugs.python.org/issue14285

   (53) https://bugs.python.org/issue19771

   (54) https://bugs.python.org/issue25177

   (55) https://bugs.python.org/issue25718

   (56) https://bugs.python.org/issue10131

   (57) https://bugs.python.org/issue7990

   (58) https://bugs.python.org/issue25725

   (59) https://bugs.python.org/issue25663

   (60) https://bugs.python.org/issue25688

   (61) https://bugs.python.org/issue23914

   (62) https://bugs.python.org/issue25691

   (63) https://bugs.python.org/issue25624

   (64) https://bugs.python.org/issue25626

   (65) https://bugs.python.org/issue25583

   (66) https://bugs.python.org/issue25593

   (67) https://bugs.python.org/issue6973

   (68) https://bugs.python.org/issue23883

   (69) https://bugs.python.org/issue25590

   (70) https://bugs.python.org/issue25498

   (71) https://bugs.python.org/issue25584

   (72) https://bugs.python.org/issue25584

   (73) https://bugs.python.org/issue25446

   (74) https://bugs.python.org/issue18010

   (75) https://bugs.python.org/issue25554

   (76) https://bugs.python.org/issue18973

   (77) https://bugs.python.org/issue25510

   (78) https://bugs.python.org/issue25503

   (79) https://bugs.python.org/issue25515

   (80) https://bugs.python.org/issue21827

   (81) https://bugs.python.org/issue25447

   (82) https://bugs.python.org/issue25390

   (83) https://bugs.python.org/issue25441

   (84) https://bugs.python.org/issue25410

   (85) https://bugs.python.org/issue25411

   (86) https://bugs.python.org/issue25407

   (87) https://bugs.python.org/issue25406

   (88) https://bugs.python.org/issue25382

   (89) https://bugs.python.org/issue25357

   (90) https://bugs.python.org/issue24164

   (91) https://bugs.python.org/issue25364

   (92) https://bugs.python.org/issue25328

   (93) https://bugs.python.org/issue16099

   (94) https://bugs.python.org/issue25316

   (95) https://bugs.python.org/issue25380

   (96) https://bugs.python.org/issue23972

   (97) https://bugs.python.org/issue25304

   (98) https://bugs.python.org/issue25232

   (99) https://bugs.python.org/issue24657

   (100) https://bugs.python.org/issue25287

   (101) https://bugs.python.org/issue23600

   (102) https://bugs.python.org/issue25203

   (103) https://bugs.python.org/issue25011

   (104) https://bugs.python.org/issue25209

   (105) https://bugs.python.org/issue22241

   (106) https://bugs.python.org/issue23517

   (107) https://bugs.python.org/issue23552

   (108) https://bugs.python.org/issue24633

   (109) https://bugs.python.org/issue24879

   (110) https://bugs.python.org/issue24874

   (111) https://bugs.python.org/issue20059

   (112) https://bugs.python.org/issue24360

   (113) https://bugs.python.org/issue23426

   (114) https://bugs.python.org/issue13938

   (115) https://bugs.python.org/issue2091

   (116) https://bugs.python.org/issue8585

   (117) https://bugs.python.org/issue18622

   (118) https://bugs.python.org/issue24426

   (119) https://bugs.python.org/issue23661

   (120) https://bugs.python.org/issue13248

   (121) https://bugs.python.org/issue25578

   (122) https://bugs.python.org/issue25530

   (123) https://bugs.python.org/issue25569

   (124) https://bugs.python.org/issue25471

   (125) https://bugs.python.org/issue25319

   (126) https://bugs.python.org/issue26050

   (127) https://bugs.python.org/issue25924

   (128) https://bugs.python.org/issue26406

   (129) https://bugs.python.org/issue26848

   (130) https://bugs.python.org/issue27040

   (131) https://bugs.python.org/issue27041


File: python.info,  Node: IDLE<46>,  Next: Documentation<45>,  Prev: Library<63>,  Up: Python 3 6 0 alpha 1

1.18.64.9 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/issue20640

   (2) https://bugs.python.org/issue25507

   (3) https://bugs.python.org/issue25905

   (4) https://bugs.python.org/issue15348

   (5) https://bugs.python.org/issue24455

   (6) https://bugs.python.org/issue24750

   (7) https://bugs.python.org/issue25313

   (8) https://bugs.python.org/issue24782

   (9) https://bugs.python.org/issue22726

   (10) https://bugs.python.org/issue24820

   (11) https://bugs.python.org/issue25224

   (12) https://bugs.python.org/issue24820

   (13) https://bugs.python.org/issue24972

   (14) https://bugs.python.org/issue24570

   (15) https://bugs.python.org/issue24988

   (16) https://bugs.python.org/issue24801

   (17) https://bugs.python.org/issue25173

   (18) https://bugs.python.org/issue25198

   (19) https://bugs.python.org/issue25225

   (20) https://bugs.python.org/issue21995

   (21) https://bugs.python.org/issue22820

   (22) https://bugs.python.org/issue25224

   (23) https://bugs.python.org/issue25219

   (24) https://bugs.python.org/issue24861

   (25) https://bugs.python.org/issue25199

   (26) https://bugs.python.org/issue16893

   (27) https://bugs.python.org/issue24199

   (28) https://bugs.python.org/issue24790


File: python.info,  Node: Documentation<45>,  Next: Tests<43>,  Prev: IDLE<46>,  Up: Python 3 6 0 alpha 1

1.18.64.10 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/issue26736

   (2) https://bugs.python.org/issue6953

   (3) https://bugs.python.org/issue23606

   (4) https://bugs.python.org/issue24952

   (5) https://bugs.python.org/issue26014


File: python.info,  Node: Tests<43>,  Next: Build<44>,  Prev: Documentation<45>,  Up: Python 3 6 0 alpha 1

1.18.64.11 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/issue21916

   (2) https://bugs.python.org/issue26295

   (3) https://bugs.python.org/issue26523

   (4) https://bugs.python.org/issue26015

   (5) https://bugs.python.org/issue26325

   (6) https://bugs.python.org/issue25940

   (7) https://bugs.python.org/issue25616

   (8) https://bugs.python.org/issue25449

   (9) https://bugs.python.org/issue25188

   (10) https://bugs.python.org/issue22806

   (11) https://bugs.python.org/issue18174

   (12) https://bugs.python.org/issue25260

   (13) https://bugs.python.org/issue26583


File: python.info,  Node: Build<44>,  Next: Windows<43>,  Prev: Tests<43>,  Up: Python 3 6 0 alpha 1

1.18.64.12 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/issue21277

   (2) https://bugs.python.org/issue26884

   (3) https://bugs.python.org/issue26932

   (4) https://bugs.python.org/issue22359

   (5) https://bugs.python.org/issue21668

   (6) https://bugs.python.org/issue25702

   (7) https://bugs.python.org/issue26624

   (8) https://bugs.python.org/issue17603

   (9) https://bugs.python.org/issue26079

   (10) https://bugs.python.org/issue26465

   (11) https://bugs.python.org/issue25348

   (12) https://bugs.python.org/issue25827

   (13) https://bugs.python.org/issue25696

   (14) https://bugs.python.org/issue24986

   (15) https://bugs.python.org/issue24421

   (16) https://bugs.python.org/issue26465

   (17) https://bugs.python.org/issue26268

   (18) https://bugs.python.org/issue25136

   (19) https://bugs.python.org/issue24324


File: python.info,  Node: Windows<43>,  Next: Tools/Demos<29>,  Prev: Build<44>,  Up: Python 3 6 0 alpha 1

1.18.64.13 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/issue27053

   (2) https://bugs.python.org/issue26268

   (3) https://bugs.python.org/issue26071

   (4) https://bugs.python.org/issue26073

   (5) https://bugs.python.org/issue26065

   (6) https://bugs.python.org/issue25022


File: python.info,  Node: Tools/Demos<29>,  Next: C API<33>,  Prev: Windows<43>,  Up: Python 3 6 0 alpha 1

1.18.64.14 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/issue26799

   (2) https://bugs.python.org/issue26271

   (3) https://bugs.python.org/issue26489

   (4) https://bugs.python.org/issue26316

   (5) https://bugs.python.org/issue25440

   (6) https://bugs.python.org/issue25154


File: python.info,  Node: C API<33>,  Prev: Tools/Demos<29>,  Up: Python 3 6 0 alpha 1

1.18.64.15 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/issue26312

   (2) https://bugs.python.org/issue26198


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.18.65 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.18.66 Python 3.5.5 release candidate 1
----------------------------------------

`Release date: 2018-01-23'

* Menu:

* Security: Security<35>.
* Core and Builtins: Core and Builtins<56>.
* Library: Library<64>.


File: python.info,  Node: Security<35>,  Next: Core and Builtins<56>,  Up: Python 3 5 5 release candidate 1

1.18.66.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.  Original patch by Jay
     Bosamiya; rebased to Python 3 by Miro Hrončok.

   - bpo-30947(5): Upgrade libexpat embedded copy from version 2.2.1 to
     2.2.3 to get security fixes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue32551

   (2) https://bugs.python.org/issue29139

   (3) https://bugs.python.org/issue29723

   (4) https://bugs.python.org/issue30657

   (5) https://bugs.python.org/issue30947


File: python.info,  Node: Core and Builtins<56>,  Next: Library<64>,  Prev: Security<35>,  Up: Python 3 5 5 release candidate 1

1.18.66.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/issue31095


File: python.info,  Node: Library<64>,  Prev: Core and Builtins<56>,  Up: Python 3 5 5 release candidate 1

1.18.66.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/issue32072

   (2) https://bugs.python.org/issue31170


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.18.67 Python 3.5.4 final
--------------------------

`Release date: 2017-08-07'

* Menu:

* Library: Library<65>.


File: python.info,  Node: Library<65>,  Up: Python 3 5 4 final

1.18.67.1 Library
.................

   - bpo-30119(1): ftplib.FTP.putline() now throws ValueError on
     commands that contains CR or LF. Patch by Dong-hee Na.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue30119


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.18.68 Python 3.5.4 release candidate 1
----------------------------------------

`Release date: 2017-07-23'

* Menu:

* Security: Security<36>.
* Core and Builtins: Core and Builtins<57>.
* Library: Library<66>.
* Documentation: Documentation<46>.
* Tests: Tests<44>.
* Build: Build<45>.
* Windows: Windows<44>.
* C API: C API<34>.


File: python.info,  Node: Security<36>,  Next: Core and Builtins<57>,  Up: Python 3 5 4 release candidate 1

1.18.68.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
     (External entity infinite loop DoS), CVE-2016-9063 (Integer
     overflow, re-fix), CVE-2016-0718 (Fix regression bugs from 2.2.0’s
     fix to CVE-2016-0718) and CVE-2012-0876 (Counter hash flooding with
     SipHash).  Note: the CVE-2016-5300 (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(3): 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(4): Update expat copy from 2.1.1 to 2.2.0 to get fixes of
     CVE-2016-0718 and CVE-2016-4472.  See
     ‘https://sourceforge.net/p/expat/bugs/537/’ for more information.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue30730

   (2) https://bugs.python.org/issue30694

   (3) https://bugs.python.org/issue30500

   (4) https://bugs.python.org/issue29591


File: python.info,  Node: Core and Builtins<57>,  Next: Library<66>,  Prev: Security<36>,  Up: Python 3 5 4 release candidate 1

1.18.68.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: 965.

   - 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/issue30876

   (2) https://bugs.python.org/issue30765

   (3) https://bugs.python.org/issue27945

   (4) https://bugs.python.org/issue25794

   (5) https://bugs.python.org/issue29935

   (6) https://bugs.python.org/issue28876

   (7) https://bugs.python.org/issue29600

   (8) https://bugs.python.org/issue29537

   (9) https://bugs.python.org/issue28598

   (10) https://bugs.python.org/issue29602

   (11) https://bugs.python.org/issue29347

   (12) https://bugs.python.org/issue29438

   (13) https://bugs.python.org/issue29319

   (14) https://bugs.python.org/issue29337

   (15) https://bugs.python.org/issue29478


File: python.info,  Node: Library<66>,  Next: Documentation<46>,  Prev: Core and Builtins<57>,  Up: Python 3 5 4 release candidate 1

1.18.68.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
     Dong-hee 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/issue29403

   (2) https://bugs.python.org/issue30961

   (3) https://bugs.python.org/issue30886

   (4) https://bugs.python.org/issue29854

   (5) https://bugs.python.org/issue30807

   (6) https://bugs.python.org/issue30441

   (7) https://bugs.python.org/issue30532

   (8) https://bugs.python.org/issue29169

   (9) https://bugs.python.org/issue30879

   (10) https://bugs.python.org/issue30746

   (11) https://bugs.python.org/issue29755

   (12) https://bugs.python.org/issue30645

   (13) https://bugs.python.org/issue23890

   (14) https://bugs.python.org/issue30149

   (15) https://bugs.python.org/issue29931

   (16) https://bugs.python.org/issue24484

   (17) https://bugs.python.org/issue28994

   (18) https://bugs.python.org/issue30508

   (19) https://bugs.python.org/issue28556

   (20) https://bugs.python.org/issue29870

   (21) https://bugs.python.org/issue29743

   (22) https://bugs.python.org/issue27585

   (23) https://bugs.python.org/issue30418

   (24) https://bugs.python.org/issue30378

   (25) https://bugs.python.org/issue29960

   (26) https://bugs.python.org/issue30414

   (27) https://bugs.python.org/issue30003

   (28) https://bugs.python.org/issue30301

   (29) https://bugs.python.org/issue30329

   (30) https://bugs.python.org/issue30375

   (31) https://bugs.python.org/issue30048

   (32) https://bugs.python.org/issue29990

   (33) https://bugs.python.org/issue26293

   (34) https://bugs.python.org/issue29094

   (35) https://bugs.python.org/issue30243

   (36) https://bugs.python.org/issue30185

   (37) https://bugs.python.org/issue28556

   (38) https://bugs.python.org/issue30205

   (39) https://bugs.python.org/issue30070

   (40) https://bugs.python.org/issue30061

   (41) https://bugs.python.org/issue30068

   (42) https://bugs.python.org/issue29694

   (43) https://bugs.python.org/issue29692

   (44) https://bugs.python.org/issue29998

   (45) https://bugs.python.org/issue29942

   (46) https://bugs.python.org/issue27863

   (47) https://bugs.python.org/issue28699

   (48) https://bugs.python.org/issue25803

   (49) https://bugs.python.org/issue29861

   (50) https://bugs.python.org/issue29884

   (51) https://bugs.python.org/issue25455

   (52) https://bugs.python.org/issue29800

   (53) https://bugs.python.org/issue29742

   (54) https://bugs.python.org/issue8256

   (55) https://bugs.python.org/issue28298

   (56) https://bugs.python.org/issue29615

   (57) https://bugs.python.org/issue29704

   (58) https://bugs.python.org/issue29703

   (59) https://bugs.python.org/issue29376

   (60) https://bugs.python.org/issue29110

   (61) https://bugs.python.org/issue28961

   (62) https://bugs.python.org/issue29532

   (63) https://bugs.python.org/issue28556

   (64) https://bugs.python.org/issue29100

   (65) https://bugs.python.org/issue29519

   (66) https://bugs.python.org/issue29416

   (67) https://bugs.python.org/issue29444

   (68) https://bugs.python.org/issue29335

   (69) https://bugs.python.org/issue29290

   (70) https://bugs.python.org/issue28735

   (71) https://bugs.python.org/issue29011

   (72) https://bugs.python.org/issue29219

   (73) https://bugs.python.org/issue28969

   (74) https://bugs.python.org/issue29142


File: python.info,  Node: Documentation<46>,  Next: Tests<44>,  Prev: Library<66>,  Up: Python 3 5 4 release candidate 1

1.18.68.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/issue30176

   (2) https://bugs.python.org/issue26985

   (3) https://bugs.python.org/issue28929

   (4) https://bugs.python.org/issue25008

   (5) https://bugs.python.org/issue26355

   (6) https://bugs.python.org/issue29349


File: python.info,  Node: Tests<44>,  Next: Build<45>,  Prev: Documentation<46>,  Up: Python 3 5 4 release candidate 1

1.18.68.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/issue30822

   (2) https://bugs.python.org/issue30383

   (3) https://bugs.python.org/issue30523

   (4) https://bugs.python.org/issue30540

   (5) https://bugs.python.org/issue30675

   (6) https://bugs.python.org/issue30357

   (7) https://bugs.python.org/issue28087

   (8) https://bugs.python.org/issue30197

   (9) https://bugs.python.org/issue29571


File: python.info,  Node: Build<45>,  Next: Windows<44>,  Prev: Tests<44>,  Up: Python 3 5 4 release candidate 1

1.18.68.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/issue29243

   (2) https://bugs.python.org/issue23404

   (3) https://bugs.python.org/issue29643


File: python.info,  Node: Windows<44>,  Next: C API<34>,  Prev: Build<45>,  Up: Python 3 5 4 release candidate 1

1.18.68.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/issue30687

   (2) https://bugs.python.org/issue29392


File: python.info,  Node: C API<34>,  Prev: Windows<44>,  Up: Python 3 5 4 release candidate 1

1.18.68.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/issue27867

   (2) https://bugs.python.org/issue29083


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.18.69 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.18.70 Python 3.5.3 release candidate 1
----------------------------------------

`Release date: 2017-01-02'

* Menu:

* Core and Builtins: Core and Builtins<58>.
* Library: Library<67>.
* Security: Security<37>.
* Library: Library<68>.
* Security: Security<38>.
* Library: Library<69>.
* IDLE: IDLE<47>.
* C API: C API<35>.
* Documentation: Documentation<47>.
* Tests: Tests<45>.
* Tools/Demos: Tools/Demos<30>.
* Windows: Windows<45>.
* Build: Build<46>.


File: python.info,  Node: Core and Builtins<58>,  Next: Library<67>,  Up: Python 3 5 3 release candidate 1

1.18.70.1 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/issue29073

   (2) https://bugs.python.org/issue28932

   (3) https://bugs.python.org/issue28147

   (4) https://bugs.python.org/issue25677

   (5) https://bugs.python.org/issue29000

   (6) https://bugs.python.org/issue28512

   (7) https://bugs.python.org/issue28991

   (8) https://bugs.python.org/issue28648

   (9) https://bugs.python.org/issue19398

   (10) https://bugs.python.org/issue28426

   (11) https://bugs.python.org/issue23782

   (12) https://bugs.python.org/issue28379

   (13) https://bugs.python.org/issue28376

   (14) https://bugs.python.org/issue28376

   (15) https://bugs.python.org/issue26906

   (16) https://bugs.python.org/issue18287

   (17) https://bugs.python.org/issue24098

   (18) https://bugs.python.org/issue28350

   (19) https://bugs.python.org/issue26617

   (20) https://bugs.python.org/issue27942

   (21) https://bugs.python.org/issue21578

   (22) https://bugs.python.org/issue28203

   (23) https://bugs.python.org/issue27955

   (24) https://bugs.python.org/issue28131

   (25) https://bugs.python.org/issue25221

   (26) https://bugs.python.org/issue25758

   (27) https://bugs.python.org/issue28189

   (28) https://bugs.python.org/issue27812

   (29) https://bugs.python.org/issue27811

   (30) https://bugs.python.org/issue27587

   (31) https://bugs.python.org/issue26020

   (32) https://bugs.python.org/issue27782

   (33) https://bugs.python.org/issue27936

   (34) https://bugs.python.org/issue27487

   (35) https://bugs.python.org/issue27558

   (36) https://bugs.python.org/issue27419

   (37) https://bugs.python.org/issue27083

   (38) https://bugs.python.org/issue27514

   (39) https://bugs.python.org/issue27473

   (40) https://bugs.python.org/issue27507

   (41) https://bugs.python.org/issue27581

   (42) https://bugs.python.org/issue27443

   (43) https://bugs.python.org/issue27942


File: python.info,  Node: Library<67>,  Next: Security<37>,  Prev: Core and Builtins<58>,  Up: Python 3 5 3 release candidate 1

1.18.70.2 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 falsy 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).

   - bpo-27766(60): Add ChaCha20 Poly1305 to ssl module’s default cipher
     list.  (Required OpenSSL 1.1.0 or LibreSSL).

   - bpo-26470(61): 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(62): Fix error when distutils encounters symlink.

   - bpo-27881(63): Fixed possible bugs when setting
     sqlite3.Connection.isolation_level.  Based on patch by Xiang Zhang.

   - bpo-27861(64): Fixed a crash in sqlite3.Connection.cursor() when a
     factory creates not a cursor.  Patch by Xiang Zhang.

   - bpo-19884(65): Avoid spurious output on OS X with Gnu Readline.

   - bpo-27706(66): 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(67): 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(68)).  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(69): Fix unnormalised ‘Fraction.__pow__’ result in the
     case of negative exponent and negative base.

   - bpo-21718(70): cursor.description is now available for queries
     using CTEs.

   - bpo-2466(71): posixpath.ismount now correctly recognizes mount
     points which the user does not have permission to access.

   - bpo-27773(72): Correct some memory management errors
     server_hostname in _ssl.wrap_socket().

   - bpo-26750(73): 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(74): Fix possible usage of uninitialized memory in
     operator.methodcaller.

   - bpo-27774(75): Fix possible Py_DECREF on unowned object in _sre.

   - bpo-27760(76): Fix possible integer overflow in binascii.b2a_qp.

   - bpo-27758(77): Fix possible integer overflow in the _csv module for
     large record lengths.

   - bpo-27568(78): Prevent HTTPoxy attack (CVE-2016-1000110).  Ignore
     the HTTP_PROXY variable when REQUEST_METHOD environment is set,
     which indicates that the script is in CGI mode.

   - bpo-27656(79): Do not assume sched.h defines any SCHED_* constants.

   - bpo-27130(80): 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(81): Release GIL in nt._isdir

   - bpo-17711(82): Fixed unpickling by the persistent ID with protocol
     0.  Original patch by Alexandre Vassalotti.

   - bpo-27522(83): Avoid an unintentional reference cycle in
     email.feedparser.

   - bpo-26844(84): Fix error message for imp.find_module() to refer to
     ’path’ instead of ’name’.  Patch by Lev Maximov.

   - bpo-23804(85): Fix SSL zero-length recv() calls to not block and
     not raise an error about unclean EOF.

   - bpo-27466(86): Change time format returned by
     http.cookie.time2netscape, confirming the netscape cookie format
     and making it consistent with documentation.

   - bpo-26664(87): Fix activate.fish by removing mis-use of ‘$’.

   - bpo-22115(88): 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(89): Fixed curses.ascii functions isblank(), iscntrl()
     and ispunct().

   - bpo-26754(90): 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(91): Prevents distutils failing on Windows when
     environment variables contain non-ASCII characters

   - bpo-27330(92): Fixed possible leaks in the ctypes module.

   - bpo-27238(93): Got rid of bare excepts in the turtle module.
     Original patch by Jelle Zijlstra.

   - bpo-27122(94): 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(95) bug described in issue25782.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue15812

   (2) https://bugs.python.org/issue29094

   (3) https://bugs.python.org/issue13051

   (4) https://bugs.python.org/issue29119

   (5) https://bugs.python.org/issue9770

   (6) https://bugs.python.org/issue28427

   (7) https://bugs.python.org/issue28923

   (8) https://bugs.python.org/issue28871

   (9) https://bugs.python.org/issue19542

   (10) https://bugs.python.org/issue20191

   (11) https://bugs.python.org/issue28779

   (12) https://bugs.python.org/issue28847

   (13) https://bugs.python.org/issue25659

   (14) https://bugs.python.org/issue28732

   (15) https://bugs.python.org/issue28485

   (16) https://bugs.python.org/issue28387

   (17) https://bugs.python.org/issue27517

   (18) https://bugs.python.org/issue28549

   (19) https://bugs.python.org/issue28449

   (20) https://bugs.python.org/issue23262

   (21) https://bugs.python.org/issue27939

   (22) https://bugs.python.org/issue28255

   (23) https://bugs.python.org/issue20491

   (24) https://bugs.python.org/issue28353

   (25) https://bugs.python.org/issue25464

   (26) https://bugs.python.org/issue28488

   (27) https://bugs.python.org/issue24452

   (28) https://bugs.python.org/issue20766

   (29) https://bugs.python.org/issue26293

   (30) https://bugs.python.org/issue28321

   (31) https://bugs.python.org/issue28322

   (32) https://bugs.python.org/issue1703178

   (33) https://bugs.python.org/issue28253

   (34) https://bugs.python.org/issue28275

   (35) https://bugs.python.org/issue27897

   (36) https://bugs.python.org/issue18893

   (37) https://bugs.python.org/issue27611

   (38) https://bugs.python.org/issue27348

   (39) https://bugs.python.org/issue25651

   (40) https://bugs.python.org/issue27932

   (41) https://bugs.python.org/issue28075

   (42) https://bugs.python.org/issue25270

   (43) https://bugs.python.org/issue28181

   (44) https://bugs.python.org/issue25895

   (45) https://bugs.python.org/issue27599

   (46) https://bugs.python.org/issue19003

   (47) https://bugs.python.org/issue28019

   (48) https://bugs.python.org/issue25969

   (49) https://bugs.python.org/issue14977

   (50) https://bugs.python.org/issue24594

   (51) https://bugs.python.org/issue17582

   (52) https://bugs.python.org/issue28047

   (53) https://bugs.python.org/issue27445

   (54) https://bugs.python.org/issue22450

   (55) https://bugs.python.org/issue27570

   (56) https://bugs.python.org/issue22233

   (57) https://bugs.python.org/issue27988

   (58) https://bugs.python.org/issue27691

   (59) https://bugs.python.org/issue27850

   (60) https://bugs.python.org/issue27766

   (61) https://bugs.python.org/issue26470

   (62) https://bugs.python.org/issue12885

   (63) https://bugs.python.org/issue27881

   (64) https://bugs.python.org/issue27861

   (65) https://bugs.python.org/issue19884

   (66) https://bugs.python.org/issue27706

   (67) https://bugs.python.org/issue10513

   (68) https://bugs.python.org/issue27598

   (69) https://bugs.python.org/issue27539

   (70) https://bugs.python.org/issue21718

   (71) https://bugs.python.org/issue2466

   (72) https://bugs.python.org/issue27773

   (73) https://bugs.python.org/issue26750

   (74) https://bugs.python.org/issue27783

   (75) https://bugs.python.org/issue27774

   (76) https://bugs.python.org/issue27760

   (77) https://bugs.python.org/issue27758

   (78) https://bugs.python.org/issue27568

   (79) https://bugs.python.org/issue27656

   (80) https://bugs.python.org/issue27130

   (81) https://bugs.python.org/issue27533

   (82) https://bugs.python.org/issue17711

   (83) https://bugs.python.org/issue27522

   (84) https://bugs.python.org/issue26844

   (85) https://bugs.python.org/issue23804

   (86) https://bugs.python.org/issue27466

   (87) https://bugs.python.org/issue26664

   (88) https://bugs.python.org/issue22115

   (89) https://bugs.python.org/issue27079

   (90) https://bugs.python.org/issue26754

   (91) https://bugs.python.org/issue27048

   (92) https://bugs.python.org/issue27330

   (93) https://bugs.python.org/issue27238

   (94) https://bugs.python.org/issue27122

   (95) https://www.python.org/dev/peps/pep-0479


File: python.info,  Node: Security<37>,  Next: Library<68>,  Prev: Library<67>,  Up: Python 3 5 3 release candidate 1

1.18.70.3 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27278


File: python.info,  Node: Library<68>,  Next: Security<38>,  Prev: Security<37>,  Up: Python 3 5 3 release candidate 1

1.18.70.4 Library
.................

   - bpo-26386(1): Fixed ttk.TreeView selection operations with item
     id’s containing spaces.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26386


File: python.info,  Node: Security<38>,  Next: Library<69>,  Prev: Library<68>,  Up: Python 3 5 3 release candidate 1

1.18.70.5 Security
..................

   - bpo-22636(1): Avoid shell injection problems with
     ctypes.util.find_library().

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue22636


File: python.info,  Node: Library<69>,  Next: IDLE<47>,  Prev: Security<38>,  Up: Python 3 5 3 release candidate 1

1.18.70.6 Library
.................

   - bpo-16182(1): 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(2): Add loop.connect_accepted_socket().  Patch by Jim
     Fulton.

   - bpo-27930(3): Improved behaviour of logging.handlers.QueueListener.
     Thanks to Paulo Andrade and Petr Viktorin for the analysis and
     patch.

   - bpo-21201(4): Improves readability of multiprocessing error
     message.  Thanks to Wojciech Walczak for patch.

   - bpo-27456(5): asyncio: Set TCP_NODELAY by default.

   - bpo-27906(6): Fix socket accept exhaustion during high TCP traffic.
     Patch by Kevin Conway.

   - bpo-28174(7): Handle when SO_REUSEPORT isn’t properly supported.
     Patch by Seth Michael Larson.

   - bpo-26654(8): Inspect functools.partial in asyncio.Handle.__repr__.
     Patch by iceboy.

   - bpo-26909(9): Fix slow pipes IO in asyncio.  Patch by INADA Naoki.

   - bpo-28176(10): Fix callbacks race in
     asyncio.SelectorLoop.sock_connect.

   - bpo-27759(11): Fix selectors incorrectly retain invalid file
     descriptors.  Patch by Mark Williams.

   - bpo-28368(12): Refuse monitoring processes if the child watcher has
     no loop attached.  Patch by Vincent Michel.

   - bpo-28369(13): Raise RuntimeError when transport’s FD is used with
     add_reader, add_writer, etc.

   - bpo-28370(14): Speedup asyncio.StreamReader.readexactly.  Patch by
     Коренберг Марк.

   - bpo-28371(15): Deprecate passing asyncio.Handles to
     run_in_executor.

   - bpo-28372(16): Fix asyncio to support formatting of non-python
     coroutines.

   - bpo-28399(17): Remove UNIX socket from FS before binding.  Patch by
     Коренберг Марк.

   - bpo-27972(18): Prohibit Tasks to await on themselves.

   - bpo-26923(19): Fix asyncio.Gather to refuse being cancelled once
     all children are done.  Patch by Johannes Ebke.

   - bpo-26796(20): Don’t configure the number of workers for default
     threadpool executor.  Initial patch by Hans Lawrenz.

   - bpo-28600(21): Optimize loop.call_soon().

   - bpo-28613(22): Fix get_event_loop() return the current loop if
     called from coroutines/callbacks.

   - bpo-28639(23): Fix inspect.isawaitable to always return bool Patch
     by Justin Mayfield.

   - bpo-28652(24): Make loop methods reject socket kinds they do not
     support.

   - bpo-28653(25): Fix a refleak in functools.lru_cache.

   - bpo-28703(26): Fix asyncio.iscoroutinefunction to handle Mock
     objects.

   - bpo-24142(27): Reading a corrupt config file left the parser in an
     invalid state.  Original patch by Florian Höch.

   - bpo-28990(28): Fix SSL hanging if connection is closed before
     handshake completed.  (Patch by HoHo-Ho)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue16182

   (2) https://bugs.python.org/issue27392

   (3) https://bugs.python.org/issue27930

   (4) https://bugs.python.org/issue21201

   (5) https://bugs.python.org/issue27456

   (6) https://bugs.python.org/issue27906

   (7) https://bugs.python.org/issue28174

   (8) https://bugs.python.org/issue26654

   (9) https://bugs.python.org/issue26909

   (10) https://bugs.python.org/issue28176

   (11) https://bugs.python.org/issue27759

   (12) https://bugs.python.org/issue28368

   (13) https://bugs.python.org/issue28369

   (14) https://bugs.python.org/issue28370

   (15) https://bugs.python.org/issue28371

   (16) https://bugs.python.org/issue28372

   (17) https://bugs.python.org/issue28399

   (18) https://bugs.python.org/issue27972

   (19) https://bugs.python.org/issue26923

   (20) https://bugs.python.org/issue26796

   (21) https://bugs.python.org/issue28600

   (22) https://bugs.python.org/issue28613

   (23) https://bugs.python.org/issue28639

   (24) https://bugs.python.org/issue28652

   (25) https://bugs.python.org/issue28653

   (26) https://bugs.python.org/issue28703

   (27) https://bugs.python.org/issue24142

   (28) https://bugs.python.org/issue28990


File: python.info,  Node: IDLE<47>,  Next: C API<35>,  Prev: Library<69>,  Up: Python 3 5 3 release candidate 1

1.18.70.7 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/issue15308

   (2) https://bugs.python.org/issue27922

   (3) https://bugs.python.org/issue25564

   (4) https://bugs.python.org/issue27714

   (5) https://bugs.python.org/issue25507

   (6) https://bugs.python.org/issue27452

   (7) https://bugs.python.org/issue27365

   (8) https://bugs.python.org/issue27245


File: python.info,  Node: C API<35>,  Next: Documentation<47>,  Prev: IDLE<47>,  Up: Python 3 5 3 release candidate 1

1.18.70.8 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/issue28808

   (2) https://bugs.python.org/issue26754


File: python.info,  Node: Documentation<47>,  Next: Tests<45>,  Prev: C API<35>,  Up: Python 3 5 3 release candidate 1

1.18.70.9 Documentation
.......................

   - bpo-28513(1): Documented command-line interface of zipfile.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28513


File: python.info,  Node: Tests<45>,  Next: Tools/Demos<30>,  Prev: Documentation<47>,  Up: Python 3 5 3 release candidate 1

1.18.70.10 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/issue28950

   (2) https://bugs.python.org/issue28666

   (3) https://bugs.python.org/issue23839

   (4) https://bugs.python.org/issue28409

   (5) https://bugs.python.org/issue27787

   (6) https://bugs.python.org/issue27369


File: python.info,  Node: Tools/Demos<30>,  Next: Windows<45>,  Prev: Tests<45>,  Up: Python 3 5 3 release candidate 1

1.18.70.11 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/issue27952

   (2) https://bugs.python.org/issue27332

   (3) https://bugs.python.org/issue27418


File: python.info,  Node: Windows<45>,  Next: Build<46>,  Prev: Tools/Demos<30>,  Up: Python 3 5 3 release candidate 1

1.18.70.12 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/issue28251

   (2) https://bugs.python.org/issue28110

   (3) https://bugs.python.org/issue25144

   (4) https://bugs.python.org/issue27469

   (5) https://bugs.python.org/issue27309


File: python.info,  Node: Build<46>,  Prev: Windows<45>,  Up: Python 3 5 3 release candidate 1

1.18.70.13 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/issue29080

   (2) https://bugs.python.org/issue23903

   (3) https://bugs.python.org/issue10656

   (4) https://bugs.python.org/issue26359

   (5) https://bugs.python.org/issue28444

   (6) https://bugs.python.org/issue28248

   (7) https://bugs.python.org/issue28258

   (8) https://bugs.python.org/issue26661

   (9) https://bugs.python.org/issue28066

   (10) https://bugs.python.org/issue15819

   (11) https://bugs.python.org/issue27566

   (12) https://bugs.python.org/issue27705

   (13) https://bugs.python.org/issue27983

   (14) https://bugs.python.org/issue26307

   (15) https://bugs.python.org/issue26359

   (16) https://bugs.python.org/issue27713

   (17) https://bugs.python.org/issue25825

   (18) https://bugs.python.org/issue27453

   (19) https://bugs.python.org/issue27641

   (20) https://bugs.python.org/issue26662

   (21) https://bugs.python.org/issue10910

   (22) https://bugs.python.org/issue28676


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.18.71 Python 3.5.2 final
--------------------------

`Release date: 2016-06-26'

* Menu:

* Core and Builtins: Core and Builtins<59>.
* Tests: Tests<46>.
* IDLE: IDLE<48>.


File: python.info,  Node: Core and Builtins<59>,  Next: Tests<46>,  Up: Python 3 5 2 final

1.18.71.1 Core and Builtins
...........................

   - bpo-26930(1): Update Windows builds to use OpenSSL 1.0.2h.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26930


File: python.info,  Node: Tests<46>,  Next: IDLE<48>,  Prev: Core and Builtins<59>,  Up: Python 3 5 2 final

1.18.71.2 Tests
...............

   - bpo-26867(1): Ubuntu’s openssl OP_NO_SSLv3 is forced on by default;
     fix test.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26867


File: python.info,  Node: IDLE<48>,  Prev: Tests<46>,  Up: Python 3 5 2 final

1.18.71.3 IDLE
..............

   - bpo-27365(1): Allow non-ascii in idlelib/NEWS.txt - minimal part
     for 3.5.2.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27365


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.18.72 Python 3.5.2 release candidate 1
----------------------------------------

`Release date: 2016-06-12'

* Menu:

* Core and Builtins: Core and Builtins<60>.
* Security: Security<39>.
* Library: Library<70>.
* Security: Security<40>.
* Library: Library<71>.
* Security: Security<41>.
* Library: Library<72>.
* Security: Security<42>.
* Library: Library<73>.
* Security: Security<43>.
* Library: Library<74>.
* IDLE: IDLE<49>.
* Documentation: Documentation<48>.
* Tests: Tests<47>.
* Build: Build<47>.
* Windows: Windows<46>.
* Tools/Demos: Tools/Demos<31>.
* Windows: Windows<47>.


File: python.info,  Node: Core and Builtins<60>,  Next: Security<39>,  Up: Python 3 5 2 release candidate 1

1.18.72.1 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/issue27066

   (2) https://bugs.python.org/issue20041

   (3) https://bugs.python.org/issue26168

   (4) https://bugs.python.org/issue26991

   (5) https://bugs.python.org/issue27039

   (6) https://bugs.python.org/issue23640

   (7) https://bugs.python.org/issue26811

   (8) https://bugs.python.org/issue20120

   (9) https://bugs.python.org/issue26659

   (10) https://bugs.python.org/issue26718

   (11) https://bugs.python.org/issue25339

   (12) https://bugs.python.org/issue26494

   (13) https://bugs.python.org/issue26581

   (14) https://bugs.python.org/issue26464

   (15) https://bugs.python.org/issue22836

   (16) https://bugs.python.org/issue26302

   (17) https://bugs.python.org/issue4806

   (18) https://bugs.python.org/issue27138

   (19) https://bugs.python.org/issue26154

   (20) https://bugs.python.org/issue26194

   (21) https://bugs.python.org/issue25843

   (22) https://bugs.python.org/issue22995

   (23) https://bugs.python.org/issue25961

   (24) https://bugs.python.org/issue25973

   (25) https://bugs.python.org/issue22995

   (26) https://bugs.python.org/issue20440

   (27) https://bugs.python.org/issue25766

   (28) https://bugs.python.org/issue25421

   (29) https://bugs.python.org/issue25709

   (30) https://bugs.python.org/issue27147

   (31) https://www.python.org/dev/peps/pep-0420

   (32) https://bugs.python.org/issue24097

   (33) https://bugs.python.org/issue24731

   (34) https://bugs.python.org/issue26478

   (35) https://bugs.python.org/issue26171

   (36) https://bugs.python.org/issue25660

   (37) https://bugs.python.org/issue25887

   (38) https://bugs.python.org/issue27243


File: python.info,  Node: Security<39>,  Next: Library<70>,  Prev: Core and Builtins<60>,  Up: Python 3 5 2 release candidate 1

1.18.72.2 Security
..................

   - bpo-26556(1): Update expat to 2.1.1, fixes CVE-2015-1283.

   - Fix TLS stripping vulnerability in smtplib, CVE-2016-0772.
     Reported by Team Oststrom

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26556


File: python.info,  Node: Library<70>,  Next: Security<40>,  Prev: Security<39>,  Up: Python 3 5 2 release candidate 1

1.18.72.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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue21386

   (2) https://bugs.python.org/issue20900

   (3) https://www.python.org/dev/peps/pep-0492

   (4) https://bugs.python.org/issue25738

   (5) https://bugs.python.org/issue21313


File: python.info,  Node: Security<40>,  Next: Library<71>,  Prev: Library<70>,  Up: Python 3 5 2 release candidate 1

1.18.72.4 Security
..................

   - bpo-26839(1): On Linux, *note os.urandom(): 4d6. 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/issue26839


File: python.info,  Node: Library<71>,  Next: Security<41>,  Prev: Security<40>,  Up: Python 3 5 2 release candidate 1

1.18.72.5 Library
.................

   - bpo-27164(1): In the zlib module, allow decompressing raw Deflate
     streams with a predefined zdict.  Based on patch by Xiang Zhang.

   - bpo-24291(2): 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(3): Add ‘__all__’ to *note string: f7.  Patch by Emanuel
     Barry.

   - bpo-26373(4): subprocess.Popen.communicate now correctly ignores
     BrokenPipeError when the child process dies before .communicate()
     is called in more/all circumstances.

   - bpo-21776(5): distutils.upload now correctly handles HTTPError.
     Initial patch by Claudiu Popa.

   - bpo-27114(6): Fix SSLContext._load_windows_store_certs fails with
     PermissionError

   - bpo-18383(7): Avoid creating duplicate filters when using
     filterwarnings and simplefilter.  Based on patch by Alex Shkop.

   - bpo-27057(8): 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(9): Fix infinite recursion using typing.py.  Thanks to
     Kalle Tuure!

   - bpo-14132(10): Fix urllib.request redirect handling when the target
     only has a query string.  Original fix by Ján Janech.

   - bpo-17214(11): 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(12): Honor debuglevel flag in urllib.request.HTTPHandler.
     Patch contributed by Chi Hsuan Yen.

   - bpo-22274(13): In the subprocess module, allow stderr to be
     redirected to stdout even when stdout is not redirected.  Patch by
     Akira Li.

   - bpo-26807(14): mock_open ’files’ no longer error on readline at end
     of file.  Patch from Yolanda Robla.

   - bpo-25745(15): Fixed leaking a userptr in curses panel destructor.

   - bpo-26977(16): Removed unnecessary, and ignored, call to sum of
     squares helper in statistics.pvariance.

   - bpo-26881(17): The modulefinder module now supports extended opcode
     arguments.

   - bpo-23815(18): Fixed crashes related to directly created instances
     of types in _tkinter and curses.panel modules.

   - bpo-17765(19): weakref.ref() no longer silently ignores keyword
     arguments.  Patch by Georg Brandl.

   - bpo-26873(20): xmlrpc now raises ResponseError on unsupported type
     tags instead of silently return incorrect result.

   - bpo-26711(21): Fixed the comparison of plistlib.Data with other
     types.

   - bpo-24114(22): 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(23): 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(24): recursive_repr() now sets __qualname__ of wrapper.
     Patch by Xiang Zhang.

   - bpo-26804(25): urllib.request will prefer lower_case proxy
     environment variables over UPPER_CASE or Mixed_Case ones.  Patch
     contributed by Hans-Peter Jansen.

   - bpo-26837(26): assertSequenceEqual() now correctly outputs
     non-stringified differing items (like bytes in the -b mode).  This
     affects assertListEqual() and assertTupleEqual().

   - bpo-26041(27): 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(28): itemgetter, attrgetter and methodcaller objects no
     longer silently ignore keyword arguments.

   - bpo-26733(29): Disassembling a class now disassembles class and
     static methods.  Patch by Xiang Zhang.

   - bpo-26801(30): Fix error handling in *note
     shutil.get_terminal_size(): a4f, catch *note AttributeError: 3a0.
     instead of *note NameError: d80.  Patch written by Emanuel Barry.

   - bpo-24838(31): tarfile’s ustar and gnu formats now correctly
     calculate name and link field limits for multibyte character
     encodings like utf-8.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27164

   (2) https://bugs.python.org/issue24291

   (3) https://bugs.python.org/issue26809

   (4) https://bugs.python.org/issue26373

   (5) https://bugs.python.org/issue21776

   (6) https://bugs.python.org/issue27114

   (7) https://bugs.python.org/issue18383

   (8) https://bugs.python.org/issue27057

   (9) https://bugs.python.org/issue27014

   (10) https://bugs.python.org/issue14132

   (11) https://bugs.python.org/issue17214

   (12) https://bugs.python.org/issue26892

   (13) https://bugs.python.org/issue22274

   (14) https://bugs.python.org/issue26807

   (15) https://bugs.python.org/issue25745

   (16) https://bugs.python.org/issue26977

   (17) https://bugs.python.org/issue26881

   (18) https://bugs.python.org/issue23815

   (19) https://bugs.python.org/issue17765

   (20) https://bugs.python.org/issue26873

   (21) https://bugs.python.org/issue26711

   (22) https://bugs.python.org/issue24114

   (23) https://bugs.python.org/issue26864

   (24) https://bugs.python.org/issue26634

   (25) https://bugs.python.org/issue26804

   (26) https://bugs.python.org/issue26837

   (27) https://bugs.python.org/issue26041

   (28) https://bugs.python.org/issue26822

   (29) https://bugs.python.org/issue26733

   (30) https://bugs.python.org/issue26801

   (31) https://bugs.python.org/issue24838


File: python.info,  Node: Security<41>,  Next: Library<72>,  Prev: Library<71>,  Up: Python 3 5 2 release candidate 1

1.18.72.6 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26657


File: python.info,  Node: Library<72>,  Next: Security<42>,  Prev: Security<41>,  Up: Python 3 5 2 release candidate 1

1.18.72.7 Library
.................

   - bpo-26717(1): Stop encoding Latin-1-ized WSGI paths with UTF-8.
     Patch by Anthony Sottile.

   - bpo-26735(2): Fix *note os.urandom(): 4d6. 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(3): Add .webm to mimetypes.types_map.  Patch by Giampaolo
     Rodola’.

   - bpo-13952(4): Add .csv to mimetypes.types_map.  Patch by Geoff
     Wilson.

   - bpo-26709(5): Fixed Y2038 problem in loading binary PLists.

   - bpo-23735(6): Handle terminal resizing with Readline 6.3+ by
     installing our own SIGWINCH handler.  Patch by Eric Price.

   - bpo-26586(7): 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(8): Change BufferedReader.writable() and
     BufferedWriter.readable() to always return False.

   - bpo-25195(9): 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(10): Raise ValueError rather than SystemError when a
     negative length is passed to SSLSocket.recv() or read().

   - bpo-23804(11): Fix SSL recv(0) and read(0) methods to return zero
     bytes instead of up to 1024.

   - bpo-26616(12): Fixed a bug in datetime.astimezone() method.

   - bpo-21925(13): *note warnings.formatwarning(): ff7. now catches
     exceptions on ‘linecache.getline(...)’ to be able to log *note
     ResourceWarning: 4d5. emitted late during the Python shutdown
     process.

   - bpo-24266(14): Ctrl+C during Readline history search now cancels
     the search mode when compiled with Readline 7.

   - bpo-26560(15): Avoid potential ValueError in
     BaseHandler.start_response.  Initial patch by Peter Inglesby.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26717

   (2) https://bugs.python.org/issue26735

   (3) https://bugs.python.org/issue16329

   (4) https://bugs.python.org/issue13952

   (5) https://bugs.python.org/issue26709

   (6) https://bugs.python.org/issue23735

   (7) https://bugs.python.org/issue26586

   (8) https://bugs.python.org/issue22854

   (9) https://bugs.python.org/issue25195

   (10) https://bugs.python.org/issue26644

   (11) https://bugs.python.org/issue23804

   (12) https://bugs.python.org/issue26616

   (13) https://bugs.python.org/issue21925

   (14) https://bugs.python.org/issue24266

   (15) https://bugs.python.org/issue26560


File: python.info,  Node: Security<42>,  Next: Library<73>,  Prev: Library<72>,  Up: Python 3 5 2 release candidate 1

1.18.72.8 Security
..................

   - bpo-26313(1): ssl.py _load_windows_store_certs fails if windows
     cert store is empty.  Patch by Baji.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26313


File: python.info,  Node: Library<73>,  Next: Security<43>,  Prev: Security<42>,  Up: Python 3 5 2 release candidate 1

1.18.72.9 Library
.................

   - bpo-26569(1): Fix *note pyclbr.readmodule(): 116e. and *note
     pyclbr.readmodule_ex(): 116f. to support importing packages.

   - bpo-26499(2): 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(3): Handle sockets in directories unittest discovery is
     scanning.  Patch from Victor van den Elzen.

   - bpo-16181(4): cookiejar.http2time() now returns None if year is
     higher than datetime.MAXYEAR.

   - bpo-26513(5): Fixes platform module detection of Windows Server

   - bpo-23718(6): Fixed parsing time in week 0 before Jan 1.  Original
     patch by Tamás Bence Gedai.

   - bpo-20589(7): Invoking Path.owner() and Path.group() on Windows now
     raise NotImplementedError instead of ImportError.

   - bpo-26177(8): Fixed the keys() method for Canvas and Scrollbar
     widgets.

   - bpo-15068(9): Got rid of excessive buffering in the fileinput
     module.  The bufsize parameter is no longer used.

   - bpo-2202(10): Fix UnboundLocalError in
     AbstractDigestAuthHandler.get_algorithm_impls.  Initial patch by
     Mathieu Dupuy.

   - bpo-25718(11): Fixed pickling and copying the accumulate() iterator
     with total is None.

   - bpo-26475(12): Fixed debugging output for regular expressions with
     the (?x) flag.

   - bpo-26457(13): 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(14): Remove the file if the internal open() call in
     NamedTemporaryFile() fails.  Patch by Silent Ghost.

   - bpo-26402(15): 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(16): Leading ‘<~’ is optional now in base64.a85decode()
     with adobe=True.  Patch by Swati Jaiswal.

   - bpo-26186(17): Remove an invalid type check in
     importlib.util.LazyLoader.

   - bpo-26367(18): importlib.__import__() raises SystemError like
     builtins.__import__() when ‘level’ is specified but without an
     accompanying package specified.

   - bpo-26309(19): In the "socketserver" module, shut down the request
     (closing the connected socket) when verify_request() returns false.
     Patch by Aviv Palivoda.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue26569

   (2) https://bugs.python.org/issue26499

   (3) https://bugs.python.org/issue25320

   (4) https://bugs.python.org/issue16181

   (5) https://bugs.python.org/issue26513

   (6) https://bugs.python.org/issue23718

   (7) https://bugs.python.org/issue20589

   (8) https://bugs.python.org/issue26177

   (9) https://bugs.python.org/issue15068

   (10) https://bugs.python.org/issue2202

   (11) https://bugs.python.org/issue25718

   (12) https://bugs.python.org/issue26475

   (13) https://bugs.python.org/issue26457

   (14) https://bugs.python.org/issue26385

   (15) https://bugs.python.org/issue26402

   (16) https://bugs.python.org/issue25913

   (17) https://bugs.python.org/issue26186

   (18) https://bugs.python.org/issue26367

   (19) https://bugs.python.org/issue26309


File: python.info,  Node: Security<43>,  Next: Library<74>,  Prev: Library<73>,  Up: Python 3 5 2 release candidate 1

1.18.72.10 Security
...................

   - bpo-25939(1): On Windows open the cert store readonly in
     ssl.enum_certificates.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25939


File: python.info,  Node: Library<74>,  Next: IDLE<49>,  Prev: Security<43>,  Up: Python 3 5 2 release candidate 1

1.18.72.11 Library
..................

   - bpo-25995(1): os.walk() no longer uses FDs proportional to the tree
     depth.

   - bpo-26117(2): The os.scandir() iterator now closes file descriptor
     not only when the iteration is finished, but when it was failed
     with error.

   - bpo-25911(3): Restored support of bytes paths in os.walk() on
     Windows.

   - bpo-26045(4): Add UTF-8 suggestion to error message when posting a
     non-Latin-1 string with http.client.

   - bpo-12923(5): Reset FancyURLopener’s redirect counter even if there
     is an exception.  Based on patches by Brian Brazil and Daniel
     Rocco.

   - bpo-25945(6): 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(7): copy.deepcopy() now correctly copies range() objects
     with non-atomic attributes.

   - bpo-23076(8): Path.glob() now raises a ValueError if it’s called
     with an invalid pattern.  Patch by Thomas Nyberg.

   - bpo-19883(9): Fixed possible integer overflows in zipimport.

   - bpo-26227(10): 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(11): xmlrpc now works with strings not encodable with
     used non-UTF-8 encoding.

   - bpo-25935(12): Garbage collector now breaks reference loops with
     OrderedDict.

   - bpo-16620(13): Fixed AttributeError in msilib.Directory.glob().

   - bpo-26013(14): Added compatibility with broken protocol 2 pickles
     created in old Python 3 versions (3.4.3 and lower).

   - bpo-25850(15): Use cross-compilation by default for 64-bit Windows.

   - bpo-17633(16): Improve zipimport’s support for namespace packages.

   - bpo-24705(17): Fix sysconfig._parse_makefile not expanding ${} vars
     appearing before $() vars.

   - bpo-22138(18): Fix mock.patch behavior when patching descriptors.
     Restore original values after patching.  Patch contributed by Sean
     McCully.

   - bpo-25672(19): In the ssl module, enable the
     SSL_MODE_RELEASE_BUFFERS mode option if it is safe to do so.

   - bpo-26012(20): Don’t traverse into symlinks for ‘**’ pattern in
     pathlib.Path.[r]glob().

   - bpo-24120(21): Ignore PermissionError when traversing a tree with
     pathlib.Path.[r]glob().  Patch by Ulrich Petri.

   - bpo-25447(22): fileinput now uses sys.stdin as-is if it does not
     have a buffer attribute (restores backward compatibility).

   - bpo-25447(23): 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(24): Fixed possible use after free in
     ElementTree.XMLPullParser.

   - bpo-25860(25): os.fwalk() no longer skips remaining directories
     when error occurs.  Original patch by Samson Lee.

   - bpo-25914(26): Fixed and simplified OrderedDict.__sizeof__.

   - bpo-25902(27): Fixed various refcount issues in ElementTree
     iteration.

   - bpo-25717(28): 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(29): 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(30): In the subprocess module, preserve any exception
     caused by fork() failure when preexec_fn is used.

   - bpo-6478(31): _strptime’s regexp cache now is reset after changing
     timezone with time.tzset().

   - bpo-14285(32): 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(33): 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(34): 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(35): Fixed copying object with state with boolean value
     is false.

   - bpo-10131(36): Fixed deep copying of minidom documents.  Based on
     patch by Marian Ganisin.

   - bpo-25725(37): Fixed a reference leak in pickle.loads() when
     unpickling invalid data including tuple instructions.

   - bpo-25663(38): In the Readline completer, avoid listing duplicate
     global names, and search the global namespace before searching
     builtins.

   - bpo-25688(39): Fixed file leak in ElementTree.iterparse() raising
     an error.

   - bpo-23914(40): Fixed SystemError raised by unpickler on broken
     pickle data.

   - bpo-25691(41): Fixed crash on deleting ElementTree.Element
     attributes.

   - bpo-25624(42): 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(43): Add asyncio.StreamReader.readuntil() method.  Patch
     by Марк Коренберг.

   - bpo-25924(44): Avoid unnecessary serialization of getaddrinfo(3)
     calls on OS X versions 10.5 or higher.  Original patch by A. Jesse
     Jiryu Davis.

   - bpo-26406(45): Avoid unnecessary serialization of getaddrinfo(3)
     calls on current versions of OpenBSD and NetBSD. Patch by A. Jesse
     Jiryu Davis.

   - bpo-26848(46): Fix asyncio/subprocess.communicate() to handle empty
     input.  Patch by Jack O’Connor.

   - bpo-27040(47): Add loop.get_exception_handler method

   - bpo-27041(48): asyncio: Add loop.create_future method

   - bpo-27223(49): asyncio: Fix _read_ready and _write_ready to respect
     _conn_lost.  Patch by Łukasz Langa.

   - bpo-22970(50): asyncio: Fix inconsistency cancelling
     Condition.wait.  Patch by David Coles.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25995

   (2) https://bugs.python.org/issue26117

   (3) https://bugs.python.org/issue25911

   (4) https://bugs.python.org/issue26045

   (5) https://bugs.python.org/issue12923

   (6) https://bugs.python.org/issue25945

   (7) https://bugs.python.org/issue26202

   (8) https://bugs.python.org/issue23076

   (9) https://bugs.python.org/issue19883

   (10) https://bugs.python.org/issue26227

   (11) https://bugs.python.org/issue26147

   (12) https://bugs.python.org/issue25935

   (13) https://bugs.python.org/issue16620

   (14) https://bugs.python.org/issue26013

   (15) https://bugs.python.org/issue25850

   (16) https://bugs.python.org/issue17633

   (17) https://bugs.python.org/issue24705

   (18) https://bugs.python.org/issue22138

   (19) https://bugs.python.org/issue25672

   (20) https://bugs.python.org/issue26012

   (21) https://bugs.python.org/issue24120

   (22) https://bugs.python.org/issue25447

   (23) https://bugs.python.org/issue25447

   (24) https://bugs.python.org/issue24103

   (25) https://bugs.python.org/issue25860

   (26) https://bugs.python.org/issue25914

   (27) https://bugs.python.org/issue25902

   (28) https://bugs.python.org/issue25717

   (29) https://bugs.python.org/issue24903

   (30) https://bugs.python.org/issue25764

   (31) https://bugs.python.org/issue6478

   (32) https://bugs.python.org/issue14285

   (33) https://bugs.python.org/issue19771

   (34) https://bugs.python.org/issue25177

   (35) https://bugs.python.org/issue25718

   (36) https://bugs.python.org/issue10131

   (37) https://bugs.python.org/issue25725

   (38) https://bugs.python.org/issue25663

   (39) https://bugs.python.org/issue25688

   (40) https://bugs.python.org/issue23914

   (41) https://bugs.python.org/issue25691

   (42) https://bugs.python.org/issue25624

   (43) https://bugs.python.org/issue26050

   (44) https://bugs.python.org/issue25924

   (45) https://bugs.python.org/issue26406

   (46) https://bugs.python.org/issue26848

   (47) https://bugs.python.org/issue27040

   (48) https://bugs.python.org/issue27041

   (49) https://bugs.python.org/issue27223

   (50) https://bugs.python.org/issue22970


File: python.info,  Node: IDLE<49>,  Next: Documentation<48>,  Prev: Library<74>,  Up: Python 3 5 2 release candidate 1

1.18.72.12 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/issue5124

   (2) https://bugs.python.org/issue24759

   (3) https://bugs.python.org/issue27196

   (4) https://bugs.python.org/issue20567

   (5) https://bugs.python.org/issue27117

   (6) https://bugs.python.org/issue26673

   (7) https://bugs.python.org/issue21939

   (8) https://bugs.python.org/issue21676

   (9) https://bugs.python.org/issue18410

   (10) https://bugs.python.org/issue21703

   (11) https://bugs.python.org/issue27044

   (12) https://bugs.python.org/issue23977

   (13) https://bugs.python.org/issue20640

   (14) https://bugs.python.org/issue25507

   (15) https://bugs.python.org/issue25905


File: python.info,  Node: Documentation<48>,  Next: Tests<47>,  Prev: IDLE<49>,  Up: Python 3 5 2 release candidate 1

1.18.72.13 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/issue19489

   (2) https://bugs.python.org/issue24136

   (3) https://www.python.org/dev/peps/pep-0448

   (4) https://bugs.python.org/issue26736

   (5) https://bugs.python.org/issue6953

   (6) https://bugs.python.org/issue23606

   (7) https://bugs.python.org/issue25500

   (8) https://bugs.python.org/issue26014


File: python.info,  Node: Tests<47>,  Next: Build<47>,  Prev: Documentation<48>,  Up: Python 3 5 2 release candidate 1

1.18.72.14 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/issue21916

   (2) https://bugs.python.org/issue26523

   (3) https://bugs.python.org/issue26015

   (4) https://bugs.python.org/issue26325

   (5) https://bugs.python.org/issue25940

   (6) https://bugs.python.org/issue25616

   (7) https://bugs.python.org/issue26583


File: python.info,  Node: Build<47>,  Next: Windows<46>,  Prev: Tests<47>,  Up: Python 3 5 2 release candidate 1

1.18.72.15 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/issue26884

   (2) https://bugs.python.org/issue22359

   (3) https://bugs.python.org/issue27229

   (4) https://bugs.python.org/issue21668

   (5) https://bugs.python.org/issue25702

   (6) https://bugs.python.org/issue26624

   (7) https://bugs.python.org/issue17603

   (8) https://bugs.python.org/issue26079

   (9) https://bugs.python.org/issue26465

   (10) https://bugs.python.org/issue24421

   (11) https://bugs.python.org/issue25348

   (12) https://bugs.python.org/issue25827

   (13) https://bugs.python.org/issue25696

   (14) https://bugs.python.org/issue26930

   (15) https://bugs.python.org/issue26268

   (16) https://bugs.python.org/issue25136

   (17) https://bugs.python.org/issue24324


File: python.info,  Node: Windows<46>,  Next: Tools/Demos<31>,  Prev: Build<47>,  Up: Python 3 5 2 release candidate 1

1.18.72.16 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.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue27053

   (2) https://bugs.python.org/issue26268

   (3) https://bugs.python.org/issue26071

   (4) https://bugs.python.org/issue26073

   (5) https://bugs.python.org/issue26065


File: python.info,  Node: Tools/Demos<31>,  Next: Windows<47>,  Prev: Windows<46>,  Up: Python 3 5 2 release candidate 1

1.18.72.17 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/issue26799

   (2) https://bugs.python.org/issue26271

   (3) https://bugs.python.org/issue26489

   (4) https://bugs.python.org/issue26316


File: python.info,  Node: Windows<47>,  Prev: Tools/Demos<31>,  Up: Python 3 5 2 release candidate 1

1.18.72.18 Windows
..................

   - bpo-17500(1): Remove unused and outdated icons.  (See also:
     ‘https://github.com/python/pythondotorg/issues/945’)

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue17500


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.18.73 Python 3.5.1 final
--------------------------

`Release date: 2015-12-06'

* Menu:

* Core and Builtins: Core and Builtins<61>.
* Windows: Windows<48>.


File: python.info,  Node: Core and Builtins<61>,  Next: Windows<48>,  Up: Python 3 5 1 final

1.18.73.1 Core and Builtins
...........................

   - bpo-25709(1): Fixed problem with in-place string concatenation and
     utf-8 cache.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25709


File: python.info,  Node: Windows<48>,  Prev: Core and Builtins<61>,  Up: Python 3 5 1 final

1.18.73.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/issue25715


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.18.74 Python 3.5.1 release candidate 1
----------------------------------------

`Release date: 2015-11-22'

* Menu:

* Core and Builtins: Core and Builtins<62>.
* Library: Library<75>.
* IDLE: IDLE<50>.
* Documentation: Documentation<49>.
* Tests: Tests<48>.
* Build: Build<48>.
* Windows: Windows<49>.
* Tools/Demos: Tools/Demos<32>.


File: python.info,  Node: Core and Builtins<62>,  Next: Library<75>,  Up: Python 3 5 1 release candidate 1

1.18.74.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/issue25630

   (2) https://bugs.python.org/issue23564

   (3) https://bugs.python.org/issue25388

   (4) https://bugs.python.org/issue25462

   (5) https://bugs.python.org/issue22995

   (6) https://bugs.python.org/issue25555

   (7) https://bugs.python.org/issue24802

   (8) https://bugs.python.org/issue24726

   (9) https://bugs.python.org/issue25449

   (10) https://bugs.python.org/issue25395

   (11) https://bugs.python.org/issue25274

   (12) https://bugs.python.org/issue24402

   (13) https://bugs.python.org/issue24806

   (14) https://bugs.python.org/issue24848

   (15) https://bugs.python.org/issue25280

   (16) https://bugs.python.org/issue25003

   (17) https://bugs.python.org/issue25182

   (18) https://bugs.python.org/issue25131

   (19) https://bugs.python.org/issue25150


File: python.info,  Node: Library<75>,  Next: IDLE<50>,  Prev: Core and Builtins<62>,  Up: Python 3 5 1 release candidate 1

1.18.74.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 falsy
     metaclasses.  Patch by Ethan Furman.

   - asyncio: ensure_future() now accepts awaitable objects.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25626

   (2) https://bugs.python.org/issue25583

   (3) https://bugs.python.org/issue25593

   (4) https://bugs.python.org/issue6973

   (5) https://bugs.python.org/issue25590

   (6) https://bugs.python.org/issue25498

   (7) https://bugs.python.org/issue25584

   (8) https://bugs.python.org/issue25584

   (9) https://bugs.python.org/issue25446

   (10) https://bugs.python.org/issue18010

   (11) https://bugs.python.org/issue25554

   (12) https://bugs.python.org/issue25510

   (13) https://bugs.python.org/issue25503

   (14) https://bugs.python.org/issue25515

   (15) https://bugs.python.org/issue21827

   (16) https://bugs.python.org/issue25447

   (17) https://bugs.python.org/issue25390

   (18) https://bugs.python.org/issue25441

   (19) https://bugs.python.org/issue25410

   (20) https://bugs.python.org/issue25411

   (21) https://bugs.python.org/issue25407

   (22) https://bugs.python.org/issue25406

   (23) https://bugs.python.org/issue25364

   (24) https://bugs.python.org/issue25328

   (25) https://bugs.python.org/issue25316

   (26) https://bugs.python.org/issue25380

   (27) https://bugs.python.org/issue23972

   (28) https://bugs.python.org/issue25304

   (29) https://bugs.python.org/issue25232

   (30) https://bugs.python.org/issue24657

   (31) https://bugs.python.org/issue24483

   (32) https://bugs.python.org/issue22958

   (33) https://bugs.python.org/issue22609

   (34) https://bugs.python.org/issue25111

   (35) https://bugs.python.org/issue25262

   (36) https://bugs.python.org/issue25034

   (37) https://bugs.python.org/issue25233

   (38) https://bugs.python.org/issue25203

   (39) https://bugs.python.org/issue23600

   (40) https://bugs.python.org/issue23329

   (41) https://bugs.python.org/issue25047

   (42) https://bugs.python.org/issue25135

   (43) https://bugs.python.org/issue19143

   (44) https://bugs.python.org/issue25092

   (45) https://bugs.python.org/issue23517

   (46) https://bugs.python.org/issue25155

   (47) https://bugs.python.org/issue25108

   (48) https://bugs.python.org/issue25118

   (49) https://bugs.python.org/issue24684

   (50) https://bugs.python.org/issue25060

   (51) https://bugs.python.org/issue24857

   (52) https://bugs.python.org/issue23144

   (53) https://bugs.python.org/issue24982

   (54) https://bugs.python.org/issue25019

   (55) https://bugs.python.org/issue16180

   (56) https://bugs.python.org/issue24891

   (57) https://bugs.python.org/issue24992

   (58) https://bugs.python.org/issue24881

   (59) https://bugs.python.org/issue25578

   (60) https://bugs.python.org/issue25530

   (61) https://bugs.python.org/issue25569

   (62) https://bugs.python.org/issue25471

   (63) https://bugs.python.org/issue25319

   (64) https://bugs.python.org/issue21112

   (65) https://bugs.python.org/issue24764

   (66) https://bugs.python.org/issue24913

   (67) https://bugs.python.org/issue24774

   (68) https://bugs.python.org/issue21159

   (69) https://bugs.python.org/issue20362

   (70) https://bugs.python.org/issue23572


File: python.info,  Node: IDLE<50>,  Next: Documentation<49>,  Prev: Library<75>,  Up: Python 3 5 1 release candidate 1

1.18.74.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/issue15348

   (2) https://bugs.python.org/issue24455

   (3) https://bugs.python.org/issue24750

   (4) https://bugs.python.org/issue25313

   (5) https://bugs.python.org/issue24782

   (6) https://bugs.python.org/issue22726

   (7) https://bugs.python.org/issue24820

   (8) https://bugs.python.org/issue25224

   (9) https://bugs.python.org/issue24820

   (10) https://bugs.python.org/issue24972

   (11) https://bugs.python.org/issue24570

   (12) https://bugs.python.org/issue24988

   (13) https://bugs.python.org/issue24801

   (14) https://bugs.python.org/issue25173

   (15) https://bugs.python.org/issue25198

   (16) https://bugs.python.org/issue25225

   (17) https://bugs.python.org/issue21995

   (18) https://bugs.python.org/issue22820

   (19) https://bugs.python.org/issue25224

   (20) https://bugs.python.org/issue25219

   (21) https://bugs.python.org/issue24861

   (22) https://bugs.python.org/issue25199

   (23) https://bugs.python.org/issue16893

   (24) https://bugs.python.org/issue24199

   (25) https://bugs.python.org/issue24790


File: python.info,  Node: Documentation<49>,  Next: Tests<48>,  Prev: IDLE<50>,  Up: Python 3 5 1 release candidate 1

1.18.74.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/issue22558

   (2) https://bugs.python.org/issue12067

   (3) https://bugs.python.org/issue24952

   (4) https://bugs.python.org/issue23725

   (5) https://bugs.python.org/issue24808

   (6) https://bugs.python.org/issue22812


File: python.info,  Node: Tests<48>,  Next: Build<48>,  Prev: Documentation<49>,  Up: Python 3 5 1 release candidate 1

1.18.74.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/issue25449

   (2) https://bugs.python.org/issue25099

   (3) https://bugs.python.org/issue23919


File: python.info,  Node: Build<48>,  Next: Windows<49>,  Prev: Tests<48>,  Up: Python 3 5 1 release candidate 1

1.18.74.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/issue24915

   (2) https://bugs.python.org/issue24910

   (3) https://bugs.python.org/issue24986


File: python.info,  Node: Windows<49>,  Next: Tools/Demos<32>,  Prev: Build<48>,  Up: Python 3 5 1 release candidate 1

1.18.74.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/issue25450

   (2) https://bugs.python.org/issue25164

   (3) https://bugs.python.org/issue25143

   (4) https://bugs.python.org/issue25163

   (5) https://bugs.python.org/issue25361

   (6) https://bugs.python.org/issue25089

   (7) https://bugs.python.org/issue25165

   (8) https://bugs.python.org/issue25112

   (9) https://bugs.python.org/issue25102

   (10) https://bugs.python.org/issue25081

   (11) https://bugs.python.org/issue25091

   (12) https://bugs.python.org/issue25126

   (13) https://bugs.python.org/issue25213

   (14) https://bugs.python.org/issue25022


File: python.info,  Node: Tools/Demos<32>,  Prev: Windows<49>,  Up: Python 3 5 1 release candidate 1

1.18.74.8 Tools/Demos
.....................

   - bpo-25440(1): Fix output of python-config –extension-suffix.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25440


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.18.75 Python 3.5.0 final
--------------------------

`Release date: 2015-09-13'

* Menu:

* Build: Build<49>.


File: python.info,  Node: Build<49>,  Up: Python 3 5 0 final

1.18.75.1 Build
...............

   - bpo-25071(1): Windows installer should not require TargetDir
     parameter when installing quietly.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25071


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.18.76 Python 3.5.0 release candidate 4
----------------------------------------

`Release date: 2015-09-09'

* Menu:

* Library: Library<76>.
* Build: Build<50>.


File: python.info,  Node: Library<76>,  Next: Build<50>,  Up: Python 3 5 0 release candidate 4

1.18.76.1 Library
.................

   - bpo-25029(1): Fixes MemoryError in test_strptime.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25029


File: python.info,  Node: Build<50>,  Prev: Library<76>,  Up: Python 3 5 0 release candidate 4

1.18.76.2 Build
...............

   - bpo-25027(1): Reverts partial-static build options and adds
     vcruntime140.dll to Windows installation.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue25027


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.18.77 Python 3.5.0 release candidate 3
----------------------------------------

`Release date: 2015-09-07'

* Menu:

* Core and Builtins: Core and Builtins<63>.
* Library: Library<77>.


File: python.info,  Node: Core and Builtins<63>,  Next: Library<77>,  Up: Python 3 5 0 release candidate 3

1.18.77.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/issue24305

   (2) https://bugs.python.org/issue24912

   (3) https://bugs.python.org/issue24975

   (4) https://www.python.org/dev/peps/pep-0448


File: python.info,  Node: Library<77>,  Prev: Core and Builtins<63>,  Up: Python 3 5 0 release candidate 3

1.18.77.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/issue24917

   (2) https://bugs.python.org/issue24748

   (3) https://bugs.python.org/issue24635

   (4) https://bugs.python.org/issue24989

   (5) https://bugs.python.org/issue24913


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.18.78 Python 3.5.0 release candidate 2
----------------------------------------

`Release date: 2015-08-25'

* Menu:

* Core and Builtins: Core and Builtins<64>.
* Library: Library<78>.


File: python.info,  Node: Core and Builtins<64>,  Next: Library<78>,  Up: Python 3 5 0 release candidate 2

1.18.78.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/issue24769

   (2) https://bugs.python.org/issue21167

   (3) https://bugs.python.org/issue24492


File: python.info,  Node: Library<78>,  Prev: Core and Builtins<64>,  Up: Python 3 5 0 release candidate 2

1.18.78.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/issue24847

   (2) https://bugs.python.org/issue24839

   (3) https://bugs.python.org/issue24867


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.18.79 Python 3.5.0 release candidate 1
----------------------------------------

`Release date: 2015-08-09'

* Menu:

* Core and Builtins: Core and Builtins<65>.
* Library: Library<79>.
* IDLE: IDLE<51>.
* Documentation: Documentation<50>.
* Tests: Tests<49>.


File: python.info,  Node: Core and Builtins<65>,  Next: Library<79>,  Up: Python 3 5 0 release candidate 1

1.18.79.1 Core and Builtins
...........................

   - bpo-24667(1): Resize odict in all cases that the underlying dict
     resizes.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue24667


File: python.info,  Node: Library<79>,  Next: IDLE<51>,  Prev: Core and Builtins<65>,  Up: Python 3 5 0 release candidate 1

1.18.79.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/issue24824

   (2) https://bugs.python.org/issue24634

   (3) https://bugs.python.org/issue24798

   (4) https://bugs.python.org/issue4395

   (5) https://bugs.python.org/issue23973

   (6) https://bugs.python.org/issue23004

   (7) https://bugs.python.org/issue23888

   (8) https://bugs.python.org/issue23652

   (9) https://bugs.python.org/issue22932

   (10) https://bugs.python.org/issue23779

   (11) https://bugs.python.org/issue23319

   (12) https://bugs.python.org/issue23254

   (13) https://bugs.python.org/issue19450

   (14) https://bugs.python.org/issue17527

   (15) https://bugs.python.org/issue24791


File: python.info,  Node: IDLE<51>,  Next: Documentation<50>,  Prev: Library<79>,  Up: Python 3 5 0 release candidate 1

1.18.79.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/issue23672

   (2) https://bugs.python.org/issue24745

   (3) https://bugs.python.org/issue21192

   (4) https://bugs.python.org/issue13884


File: python.info,  Node: Documentation<50>,  Next: Tests<49>,  Prev: IDLE<51>,  Up: Python 3 5 0 release candidate 1

1.18.79.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/issue24129

   (2) https://bugs.python.org/issue20769

   (3) https://bugs.python.org/issue23589

   (4) https://bugs.python.org/issue24729


File: python.info,  Node: Tests<49>,  Prev: Documentation<50>,  Up: Python 3 5 0 release candidate 1

1.18.79.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/issue24751


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.18.80 Python 3.5.0 beta 4
---------------------------

`Release date: 2015-07-26'

* Menu:

* Core and Builtins: Core and Builtins<66>.
* Library: Library<80>.
* Build: Build<51>.


File: python.info,  Node: Core and Builtins<66>,  Next: Library<80>,  Up: Python 3 5 0 beta 4

1.18.80.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/issue23573

   (2) https://bugs.python.org/issue24569

   (3) https://www.python.org/dev/peps/pep-0448

   (4) https://bugs.python.org/issue24583

   (5) https://bugs.python.org/issue24407

   (6) https://bugs.python.org/issue24619

   (7) https://bugs.python.org/issue24687

   (8) https://bugs.python.org/issue15944


File: python.info,  Node: Library<80>,  Next: Build<51>,  Prev: Core and Builtins<66>,  Up: Python 3 5 0 beta 4

1.18.80.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 *note inspect.getsource:
     eda. 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/issue23441

   (2) https://bugs.python.org/issue24683

   (3) https://bugs.python.org/issue21697

   (4) https://bugs.python.org/issue14373

   (5) https://bugs.python.org/issue24695

   (6) https://bugs.python.org/issue24620

   (7) https://bugs.python.org/issue22485

   (8) https://bugs.python.org/issue22153

   (9) https://bugs.python.org/issue24580

   (10) https://bugs.python.org/issue24206

   (11) https://bugs.python.org/issue24631

   (12) https://bugs.python.org/issue18622

   (13) https://bugs.python.org/issue23661

   (14) https://bugs.python.org/issue24608

   (15) https://bugs.python.org/issue18684

   (16) https://bugs.python.org/issue24259

   (17) https://bugs.python.org/issue15014

   (18) https://bugs.python.org/issue24669

   (19) https://bugs.python.org/issue24688


File: python.info,  Node: Build<51>,  Prev: Library<80>,  Up: Python 3 5 0 beta 4

1.18.80.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/issue24603


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.18.81 Python 3.5.0 beta 3
---------------------------

`Release date: 2015-07-05'

* Menu:

* Core and Builtins: Core and Builtins<67>.
* Library: Library<81>.
* Tests: Tests<50>.
* Documentation: Documentation<51>.
* Build: Build<52>.


File: python.info,  Node: Core and Builtins<67>,  Next: Library<81>,  Up: Python 3 5 0 beta 3

1.18.81.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/issue24467

   (2) https://bugs.python.org/issue24345

   (3) https://bugs.python.org/issue24400

   (4) https://www.python.org/dev/peps/pep-0492

   (5) https://bugs.python.org/issue24450

   (6) https://bugs.python.org/issue19235


File: python.info,  Node: Library<81>,  Next: Tests<50>,  Prev: Core and Builtins<67>,  Up: Python 3 5 0 beta 3

1.18.81.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/issue21750

   (2) https://bugs.python.org/issue24552

   (3) https://bugs.python.org/issue24514

   (4) https://bugs.python.org/issue19176

   (5) https://bugs.python.org/issue20387

   (6) https://bugs.python.org/issue24456

   (7) https://bugs.python.org/issue24336

   (8) https://bugs.python.org/issue24522

   (9) https://bugs.python.org/issue24489

   (10) https://bugs.python.org/issue24408

   (11) https://bugs.python.org/issue14373

   (12) https://bugs.python.org/issue24347

   (13) https://bugs.python.org/issue24348

   (14) https://bugs.python.org/issue24359

   (15) https://bugs.python.org/issue24368

   (16) https://bugs.python.org/issue24362

   (17) https://bugs.python.org/issue24377

   (18) https://bugs.python.org/issue24369


File: python.info,  Node: Tests<50>,  Next: Documentation<51>,  Prev: Library<81>,  Up: Python 3 5 0 beta 3

1.18.81.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/issue24373

   (2) https://bugs.python.org/issue16690


File: python.info,  Node: Documentation<51>,  Next: Build<52>,  Prev: Tests<50>,  Up: Python 3 5 0 beta 3

1.18.81.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/issue24458

   (2) https://bugs.python.org/issue24351


File: python.info,  Node: Build<52>,  Prev: Documentation<51>,  Up: Python 3 5 0 beta 3

1.18.81.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/issue24432


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.18.82 Python 3.5.0 beta 2
---------------------------

`Release date: 2015-05-31'

* Menu:

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


File: python.info,  Node: Core and Builtins<68>,  Next: Library<82>,  Up: Python 3 5 0 beta 2

1.18.82.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/issue24284

   (2) https://bugs.python.org/issue24115

   (3) https://bugs.python.org/issue24328

   (4) https://bugs.python.org/issue11205

   (5) https://bugs.python.org/issue24285


File: python.info,  Node: Library<82>,  Prev: Core and Builtins<68>,  Up: Python 3 5 0 beta 2

1.18.82.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/issue23247

   (2) https://bugs.python.org/issue24270

   (3) https://www.python.org/dev/peps/pep-0485

   (4) https://bugs.python.org/issue5633

   (5) https://bugs.python.org/issue24326

   (6) https://bugs.python.org/issue16991

   (7) https://bugs.python.org/issue23934


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.18.83 Python 3.5.0 beta 1
---------------------------

`Release date: 2015-05-24'

* Menu:

* Core and Builtins: Core and Builtins<69>.
* Library: Library<83>.
* IDLE: IDLE<52>.
* Tests: Tests<51>.
* Documentation: Documentation<52>.
* Tools/Demos: Tools/Demos<33>.


File: python.info,  Node: Core and Builtins<69>,  Next: Library<83>,  Up: Python 3 5 0 beta 1

1.18.83.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/issue24276

   (2) https://bugs.python.org/issue24268

   (3) https://bugs.python.org/issue23955

   (4) https://bugs.python.org/issue24257

   (5) https://bugs.python.org/issue22939

   (6) https://bugs.python.org/issue23985

   (7) https://bugs.python.org/issue24102

   (8) https://bugs.python.org/issue15027

   (9) https://bugs.python.org/issue23290

   (10) https://bugs.python.org/issue2292

   (11) https://bugs.python.org/issue24096

   (12) https://bugs.python.org/issue23996

   (13) https://bugs.python.org/issue23910

   (14) https://bugs.python.org/issue23911

   (15) https://bugs.python.org/issue24192

   (16) https://bugs.python.org/issue24022

   (17) https://bugs.python.org/issue9951

   (18) https://bugs.python.org/issue22906

   (19) https://bugs.python.org/issue24017


File: python.info,  Node: Library<83>,  Next: IDLE<52>,  Prev: Core and Builtins<69>,  Up: Python 3 5 0 beta 1

1.18.83.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/issue14373

   (2) https://bugs.python.org/issue24230

   (3) https://bugs.python.org/issue22189

   (4) https://bugs.python.org/issue24244

   (5) https://bugs.python.org/issue23973

   (6) https://bugs.python.org/issue23086

   (7) https://bugs.python.org/issue20035

   (8) https://bugs.python.org/issue24257

   (9) https://bugs.python.org/issue15836

   (10) https://bugs.python.org/issue9858

   (11) https://bugs.python.org/issue22955

   (12) https://bugs.python.org/issue22107

   (13) https://bugs.python.org/issue23780

   (14) https://bugs.python.org/issue6598

   (15) https://bugs.python.org/issue24091

   (16) https://bugs.python.org/issue21931

   (17) https://bugs.python.org/issue13866

   (18) https://bugs.python.org/issue20098

   (19) https://bugs.python.org/issue24211

   (20) https://bugs.python.org/issue16314

   (21) https://bugs.python.org/issue21804

   (22) https://bugs.python.org/issue18682

   (23) https://bugs.python.org/issue22027

   (24) https://bugs.python.org/issue23488

   (25) https://bugs.python.org/issue1322

   (26) https://bugs.python.org/issue22486

   (27) https://bugs.python.org/issue24064

   (28) https://bugs.python.org/issue22681

   (29) https://bugs.python.org/issue22682

   (30) https://bugs.python.org/issue23796

   (31) https://bugs.python.org/issue21795

   (32) https://bugs.python.org/issue24155

   (33) https://bugs.python.org/issue21800

   (34) https://bugs.python.org/issue20274

   (35) https://bugs.python.org/issue20274

   (36) https://bugs.python.org/issue24134

   (37) https://bugs.python.org/issue24018

   (38) https://bugs.python.org/issue23880

   (39) https://bugs.python.org/issue22619

   (40) https://bugs.python.org/issue24094

   (41) https://bugs.python.org/issue9246

   (42) https://bugs.python.org/issue17445

   (43) https://bugs.python.org/issue23917

   (44) https://bugs.python.org/issue23008

   (45) https://bugs.python.org/issue23908

   (46) https://bugs.python.org/issue23728

   (47) https://bugs.python.org/issue23887

   (48) https://bugs.python.org/issue24178

   (49) https://bugs.python.org/issue24179

   (50) https://bugs.python.org/issue24184

   (51) https://bugs.python.org/issue22547

   (52) https://bugs.python.org/issue24190

   (53) https://bugs.python.org/issue20691

   (54) https://bugs.python.org/issue24248

   (55) https://bugs.python.org/issue23898

   (56) https://bugs.python.org/issue24298


File: python.info,  Node: IDLE<52>,  Next: Tests<51>,  Prev: Library<83>,  Up: Python 3 5 0 beta 1

1.18.83.3 IDLE
..............

   - bpo-23184(1): remove unused names and imports in idlelib.  Initial
     patch by Al Sweigart.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23184


File: python.info,  Node: Tests<51>,  Next: Documentation<52>,  Prev: IDLE<52>,  Up: Python 3 5 0 beta 1

1.18.83.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/issue21520

   (2) https://bugs.python.org/issue9517


File: python.info,  Node: Documentation<52>,  Next: Tools/Demos<33>,  Prev: Tests<51>,  Up: Python 3 5 0 beta 1

1.18.83.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/issue22155

   (2) https://bugs.python.org/issue24029

   (3) https://bugs.python.org/issue24077


File: python.info,  Node: Tools/Demos<33>,  Prev: Documentation<52>,  Up: Python 3 5 0 beta 1

1.18.83.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/issue24000

   (2) https://bugs.python.org/issue24001

   (3) https://bugs.python.org/issue23330

   (4) https://bugs.python.org/issue24031


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.18.84 Python 3.5.0 alpha 4
----------------------------

`Release date: 2015-04-19'

* Menu:

* Core and Builtins: Core and Builtins<70>.
* Library: Library<84>.
* Build: Build<53>.
* Tests: Tests<52>.
* Tools/Demos: Tools/Demos<34>.
* C API: C API<36>.


File: python.info,  Node: Core and Builtins<70>,  Next: Library<84>,  Up: Python 3 5 0 alpha 4

1.18.84.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/issue22980

   (2) https://www.python.org/dev/peps/pep-3149

   (3) https://bugs.python.org/issue22631

   (4) https://bugs.python.org/issue23731

   (5) https://www.python.org/dev/peps/pep-0488

   (6) https://bugs.python.org/issue23726

   (7) https://bugs.python.org/issue23309

   (8) https://bugs.python.org/issue22977

   (9) https://bugs.python.org/issue23466

   (10) https://bugs.python.org/issue24044

   (11) https://bugs.python.org/issue21354


File: python.info,  Node: Library<84>,  Next: Build<53>,  Prev: Core and Builtins<70>,  Up: Python 3 5 0 alpha 4

1.18.84.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(): 680. 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(): 67b. now waits until
     the connection completes instead of raising *note InterruptedError:
     65e. 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(): 67b. still raise *note
     InterruptedError: 65e. 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/issue23840

   (2) https://bugs.python.org/issue16914

   (3) https://bugs.python.org/issue7159

   (4) https://bugs.python.org/issue19494

   (5) https://bugs.python.org/issue23703

   (6) https://bugs.python.org/issue4254

   (7) https://bugs.python.org/issue19933

   (8) https://bugs.python.org/issue23193

   (9) https://bugs.python.org/issue23342

   (10) https://bugs.python.org/issue21217

   (11) https://bugs.python.org/issue24521

   (12) https://bugs.python.org/issue22931

   (13) https://bugs.python.org/issue23811

   (14) https://bugs.python.org/issue21116

   (15) https://bugs.python.org/issue22982

   (16) https://bugs.python.org/issue23464

   (17) https://bugs.python.org/issue23529

   (18) https://bugs.python.org/issue21859

   (19) https://bugs.python.org/issue23865

   (20) https://bugs.python.org/issue23400

   (21) https://bugs.python.org/issue10838

   (22) https://bugs.python.org/issue23411

   (23) https://bugs.python.org/issue23881

   (24) https://bugs.python.org/issue23853

   (25) https://bugs.python.org/issue22721

   (26) https://bugs.python.org/issue15133

   (27) https://bugs.python.org/issue10590

   (28) https://bugs.python.org/issue23338

   (29) https://bugs.python.org/issue15582

   (30) https://bugs.python.org/issue2175

   (31) https://bugs.python.org/issue16840

   (32) https://bugs.python.org/issue23834

   (33) https://bugs.python.org/issue23618

   (34) https://bugs.python.org/issue21526

   (35) https://bugs.python.org/issue23836

   (36) https://bugs.python.org/issue23838

   (37) https://bugs.python.org/issue10395

   (38) https://bugs.python.org/issue23611

   (39) https://bugs.python.org/issue13583

   (40) https://bugs.python.org/issue18473

   (41) https://bugs.python.org/issue23485

   (42) https://www.python.org/dev/peps/pep-0475

   (43) https://bugs.python.org/issue23752

   (44) https://bugs.python.org/issue23704

   (45) https://bugs.python.org/issue23171

   (46) https://bugs.python.org/issue23745

   (47) https://bugs.python.org/issue22117

   (48) https://bugs.python.org/issue23310


File: python.info,  Node: Build<53>,  Next: Tests<52>,  Prev: Library<84>,  Up: Python 3 5 0 alpha 4

1.18.84.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/issue23817

   (2) https://bugs.python.org/issue23501


File: python.info,  Node: Tests<52>,  Next: Tools/Demos<34>,  Prev: Build<53>,  Up: Python 3 5 0 alpha 4

1.18.84.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/issue23799

   (2) https://bugs.python.org/issue22390


File: python.info,  Node: Tools/Demos<34>,  Next: C API<36>,  Prev: Tests<52>,  Up: Python 3 5 0 alpha 4

1.18.84.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/issue18128

   (2) https://bugs.python.org/issue23935

   (3) https://bugs.python.org/issue23944

   (4) https://bugs.python.org/issue20586

   (5) https://bugs.python.org/issue23492

   (6) https://bugs.python.org/issue23500


File: python.info,  Node: C API<36>,  Prev: Tools/Demos<34>,  Up: Python 3 5 0 alpha 4

1.18.84.6 C API
...............

   - bpo-23998(1): PyImport_ReInitLock() now checks for lock allocation
     error

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23998


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.18.85 Python 3.5.0 alpha 3
----------------------------

`Release date: 2015-03-28'

* Menu:

* Core and Builtins: Core and Builtins<71>.
* Library: Library<85>.
* Build: Build<54>.
* Tests: Tests<53>.
* Tools/Demos: Tools/Demos<35>.


File: python.info,  Node: Core and Builtins<71>,  Next: Library<85>,  Up: Python 3 5 0 alpha 3

1.18.85.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/issue23573

   (2) https://bugs.python.org/issue23753

   (3) https://bugs.python.org/issue23681

   (4) https://bugs.python.org/issue23632

   (5) https://bugs.python.org/issue23192

   (6) https://bugs.python.org/issue23629


File: python.info,  Node: Library<85>,  Next: Build<54>,  Prev: Core and Builtins<71>,  Up: Python 3 5 0 alpha 3

1.18.85.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(): 684. and *note
     signal.sigtimedwait(): 683. 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/issue14260

   (2) https://bugs.python.org/issue23792

   (3) https://bugs.python.org/issue23775

   (4) https://bugs.python.org/issue23765

   (5) https://bugs.python.org/issue22364

   (6) https://bugs.python.org/issue23742

   (7) https://bugs.python.org/issue21717

   (8) https://bugs.python.org/issue21802

   (9) https://bugs.python.org/issue23622

   (10) https://bugs.python.org/issue23671

   (11) https://bugs.python.org/issue23502

   (12) https://bugs.python.org/issue17530

   (13) https://bugs.python.org/issue22687

   (14) https://bugs.python.org/issue4727

   (15) https://bugs.python.org/issue23491

   (16) https://bugs.python.org/issue23657

   (17) https://bugs.python.org/issue23688

   (18) https://bugs.python.org/issue23252

   (19) https://bugs.python.org/issue23647

   (20) https://bugs.python.org/issue23539

   (21) https://bugs.python.org/issue22351

   (22) https://bugs.python.org/issue23704

   (23) https://bugs.python.org/issue23715

   (24) https://bugs.python.org/issue23001

   (25) https://bugs.python.org/issue23646

   (26) https://bugs.python.org/issue23136

   (27) https://bugs.python.org/issue23700

   (28) https://bugs.python.org/issue22903

   (29) https://bugs.python.org/issue22181

   (30) https://bugs.python.org/issue2211

   (31) https://bugs.python.org/issue18983

   (32) https://bugs.python.org/issue23631

   (33) https://bugs.python.org/issue23568

   (34) https://bugs.python.org/issue2052

   (35) https://bugs.python.org/issue23668

   (36) https://bugs.python.org/issue23138

   (37) https://bugs.python.org/issue23051

   (38) https://bugs.python.org/issue23581

   (39) https://bugs.python.org/issue23566

   (40) https://bugs.python.org/issue22928

   (41) https://bugs.python.org/issue23615

   (42) https://bugs.python.org/issue23605


File: python.info,  Node: Build<54>,  Next: Tests<53>,  Prev: Library<85>,  Up: Python 3 5 0 alpha 3

1.18.85.3 Build
...............

   - bpo-23585(1): make patchcheck will ensure the interpreter is built.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue23585


File: python.info,  Node: Tests<53>,  Next: Tools/Demos<35>,  Prev: Build<54>,  Up: Python 3 5 0 alpha 3

1.18.85.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/issue23583

   (2) https://bugs.python.org/issue22289


File: python.info,  Node: Tools/Demos<35>,  Prev: Tests<53>,  Up: Python 3 5 0 alpha 3

1.18.85.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/issue22826


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.18.86 Python 3.5.0 alpha 2
----------------------------

`Release date: 2015-03-09'

* Menu:

* Core and Builtins: Core and Builtins<72>.
* Library: Library<86>.
* Build: Build<55>.
* C API: C API<37>.
* Windows: Windows<50>.


File: python.info,  Node: Core and Builtins<72>,  Next: Library<86>,  Up: Python 3 5 0 alpha 2

1.18.86.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/issue23571


File: python.info,  Node: Library<86>,  Next: Build<55>,  Prev: Core and Builtins<72>,  Up: Python 3 5 0 alpha 2

1.18.86.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/issue22524

   (2) https://www.python.org/dev/peps/pep-0471

   (3) https://bugs.python.org/issue23103

   (4) https://bugs.python.org/issue21793

   (5) https://bugs.python.org/issue23476

   (6) https://bugs.python.org/issue23576

   (7) https://bugs.python.org/issue23504

   (8) https://bugs.python.org/issue23563

   (9) https://bugs.python.org/issue7830

   (10) https://bugs.python.org/issue20204

   (11) https://bugs.python.org/issue19980

   (12) https://bugs.python.org/issue23521

   (13) https://bugs.python.org/issue21619

   (14) https://bugs.python.org/issue22936

   (15) https://bugs.python.org/issue15955

   (16) https://bugs.python.org/issue6639

   (17) https://bugs.python.org/issue814253

   (18) https://bugs.python.org/issue9179

   (19) https://bugs.python.org/issue23215

   (20) https://bugs.python.org/issue5700

   (21) https://bugs.python.org/issue23374

   (22) https://bugs.python.org/issue23481

   (23) https://bugs.python.org/issue21548

   (24) https://bugs.python.org/issue22885

   (25) https://bugs.python.org/issue23239

   (26) https://bugs.python.org/issue23146

   (27) https://bugs.python.org/issue23096

   (28) https://bugs.python.org/issue19105

   (29) https://bugs.python.org/issue14910

   (30) https://bugs.python.org/issue21717

   (31) https://bugs.python.org/issue23344

   (32) https://bugs.python.org/issue20416

   (33) https://bugs.python.org/issue23421

   (34) https://bugs.python.org/issue23367

   (35) https://bugs.python.org/issue23361

   (36) https://bugs.python.org/issue19705

   (37) https://bugs.python.org/issue23801


File: python.info,  Node: Build<55>,  Next: C API<37>,  Prev: Library<86>,  Up: Python 3 5 0 alpha 2

1.18.86.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/issue23445

   (2) https://bugs.python.org/issue23686


File: python.info,  Node: C API<37>,  Next: Windows<50>,  Prev: Build<55>,  Up: Python 3 5 0 alpha 2

1.18.86.4 C API
...............

   - bpo-20204(1): Deprecation warning is now raised for builtin types
     without the __module__ attribute.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue20204


File: python.info,  Node: Windows<50>,  Prev: C API<37>,  Up: Python 3 5 0 alpha 2

1.18.86.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/issue23465

   (2) https://www.python.org/dev/peps/pep-0486

   (3) https://bugs.python.org/issue23437


File: python.info,  Node: Python 3 5 0 alpha 1,  Prev: Python 3 5 0 alpha 2,  Up: Changelog（更動日誌）

1.18.87 Python 3.5.0 alpha 1
----------------------------

`Release date: 2015-02-08'

* Menu:

* Core and Builtins: Core and Builtins<73>.
* Library: Library<87>.
* IDLE: IDLE<53>.
* Build: Build<56>.
* C API: C API<38>.
* Documentation: Documentation<53>.
* Tests: Tests<54>.
* Tools/Demos: Tools/Demos<36>.
* Windows: Windows<51>.


File: python.info,  Node: Core and Builtins<73>,  Next: Library<87>,  Up: Python 3 5 0 alpha 1

1.18.87.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 *note type: 60d.

   - 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/issue23285

   (2) https://bugs.python.org/issue22735

   (3) https://bugs.python.org/issue22896

   (4) https://bugs.python.org/issue21295

   (5) https://bugs.python.org/issue16795

   (6) https://bugs.python.org/issue22986

   (7) https://bugs.python.org/issue15859

   (8) https://bugs.python.org/issue21408

   (9) https://bugs.python.org/issue23321

   (10) https://bugs.python.org/issue22286

   (11) https://bugs.python.org/issue23253

   (12) https://bugs.python.org/issue22038

   (13) https://bugs.python.org/issue20284

   (14) https://bugs.python.org/issue23048

   (15) https://bugs.python.org/issue20335

   (16) https://bugs.python.org/issue22834

   (17) https://bugs.python.org/issue22869

   (18) https://bugs.python.org/issue22847

   (19) https://bugs.python.org/issue22335

   (20) https://bugs.python.org/issue22653

   (21) https://bugs.python.org/issue22643

   (22) https://bugs.python.org/issue17636

   (23) https://bugs.python.org/issue22604

   (24) https://bugs.python.org/issue21052

   (25) https://bugs.python.org/issue16518

   (26) https://bugs.python.org/issue22470

   (27) https://bugs.python.org/issue22540

   (28) https://bugs.python.org/issue18711

   (29) https://bugs.python.org/issue22520

   (30) https://bugs.python.org/issue22519

   (31) https://bugs.python.org/issue22518

   (32) https://bugs.python.org/issue16324

   (33) https://bugs.python.org/issue1764286

   (34) https://bugs.python.org/issue18554

   (35) https://bugs.python.org/issue21391

   (36) https://bugs.python.org/issue11471

   (37) https://bugs.python.org/issue22215

   (38) https://bugs.python.org/issue22258

   (39) https://bugs.python.org/issue21389

   (40) https://bugs.python.org/issue22206

   (41) https://bugs.python.org/issue20184

   (42) https://bugs.python.org/issue22116

   (43) https://bugs.python.org/issue22077

   (44) https://bugs.python.org/issue20179

   (45) https://bugs.python.org/issue22082

   (46) https://bugs.python.org/issue21897

   (47) https://bugs.python.org/issue21205

   (48) https://bugs.python.org/issue21669

   (49) https://bugs.python.org/issue21642

   (50) https://bugs.python.org/issue21523

   (51) https://bugs.python.org/issue21418

   (52) https://bugs.python.org/issue21425

   (53) https://bugs.python.org/issue21435

   (54) https://bugs.python.org/issue21377

   (55) https://bugs.python.org/issue20355

   (56) https://bugs.python.org/issue21274

   (57) https://bugs.python.org/issue20904

   (58) https://bugs.python.org/issue21209

   (59) https://bugs.python.org/issue21193

   (60) https://bugs.python.org/issue21176

   (61) https://bugs.python.org/issue21134

   (62) https://bugs.python.org/issue19537

   (63) https://bugs.python.org/issue20929

   (64) https://bugs.python.org/issue20731

   (65) https://bugs.python.org/issue20637

   (66) https://bugs.python.org/issue8297

   (67) https://bugs.python.org/issue19995

   (68) https://bugs.python.org/issue19655

   (69) https://bugs.python.org/issue12546

   (70) https://bugs.python.org/issue20480

   (71) https://bugs.python.org/issue13598

   (72) https://bugs.python.org/issue8931

   (73) https://bugs.python.org/issue23165


File: python.info,  Node: Library<87>,  Next: IDLE<53>,  Prev: Core and Builtins<73>,  Up: Python 3 5 0 alpha 1

1.18.87.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(): 767. 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.

   - bpo-14099(61): 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(62): 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(63): Update turtledemo doc and add module to the index.

   - bpo-21032(64): Fixed socket leak if HTTPConnection.getresponse()
     fails.  Original patch by Martin Panter.

   - bpo-22407(65): Deprecated the use of re.LOCALE flag with str
     patterns or re.ASCII. It was newer worked.

   - bpo-22902(66): The "ip" command is now used on Linux to determine
     MAC address in uuid.getnode().  Pach by Bruno Cauet.

   - bpo-22960(67): Add a context argument to xmlrpclib.ServerProxy
     constructor.

   - bpo-22389(68): Add contextlib.redirect_stderr().

   - bpo-21356(69): 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(70): SAX parser now supports files opened with file
     descriptor or bytes path.

   - bpo-22609(71): Constructors and update methods of mapping classes
     in the collections module now accept the self keyword argument.

   - bpo-22940(72): Add readline.append_history_file.

   - bpo-19676(73): Added the "namereplace" error handler.

   - bpo-22788(74): Add `context' parameter to
     logging.handlers.HTTPHandler.

   - bpo-22921(75): Allow SSLContext to take the `hostname' parameter
     even if OpenSSL doesn’t support SNI.

   - bpo-22894(76): TestCase.subTest() would cause the test suite to be
     stopped when in failfast mode, even in the absence of failures.

   - bpo-22796(77): HTTP cookie parsing is now stricter, in order to
     protect against potential injection attacks.

   - bpo-22370(78): Windows detection in pathlib is now more robust.

   - bpo-22841(79): Reject coroutines in asyncio add_signal_handler().
     Patch by Ludovic.Gasc.

   - bpo-19494(80): Added urllib.request.HTTPBasicPriorAuthHandler.
     Patch by Matej Cepl.

   - bpo-22578(81): Added attributes to the re.error class.

   - bpo-22849(82): Fix possible double free in the io.TextIOWrapper
     constructor.

   - bpo-12728(83): Different Unicode characters having the same
     uppercase but different lowercase are now matched in
     case-insensitive regular expressions.

   - bpo-22821(84): Fixed fcntl() with integer argument on 64-bit
     big-endian platforms.

   - bpo-21650(85): Add an ‘--sort-keys’ option to json.tool CLI.

   - bpo-22824(86): Updated reprlib output format for sets to use set
     literals.  Patch contributed by Berker Peksag.

   - bpo-22824(87): Updated reprlib output format for arrays to display
     empty arrays without an unnecessary empty list.  Suggested by
     Serhiy Storchaka.

   - bpo-22406(88): Fixed the uu_codec codec incorrectly ported to 3.x.
     Based on patch by Martin Panter.

   - bpo-17293(89): uuid.getnode() now determines MAC address on AIX
     using netstat.  Based on patch by Aivars Kalvāns.

   - bpo-22769(90): Fixed ttk.Treeview.tag_has() when called without
     arguments.

   - bpo-22417(91): Verify certificates by default in httplib (PEP 476).

   - bpo-22775(92): Fixed unpickling of http.cookies.SimpleCookie with
     protocol 2 and above.  Patch by Tim Graham.

   - bpo-22776(93): Brought excluded code into the scope of a try block
     in SysLogHandler.emit().

   - bpo-22665(94): Add missing get_terminal_size and SameFileError to
     shutil.__all__.

   - bpo-6623(95): Remove deprecated Netrc class in the ftplib module.
     Patch by Matt Chaput.

   - bpo-17381(96): Fixed handling of case-insensitive ranges in regular
     expressions.

   - bpo-22410(97): Module level functions in the re module now cache
     compiled locale-dependent regular expressions taking into account
     the locale.

   - bpo-22759(98): Query methods on pathlib.Path() (exists(), is_dir(),
     etc.)  now return False when the underlying stat call raises
     NotADirectoryError.

   - bpo-8876(99): 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(100): Implemented reprs of classes in the zipfile module.

   - bpo-22457(101): Honour load_tests in the start_dir of discovery.

   - bpo-18216(102): gettext now raises an error when a .mo file has an
     unsupported major version number.  Patch by Aaron Hill.

   - bpo-13918(103): 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(104): Make the pickling of global objects which don’t
     have a __module__ attribute less slow.

   - bpo-18853(105): Fixed ResourceWarning in shlex.__nain__.

   - bpo-9351(106): Defaults set with set_defaults on an argparse
     subparser are no longer ignored when also set on the parent parser.

   - bpo-7559(107): 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(108): 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(109): 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(110): SSLv3 is now disabled throughout the standard
     library.  It can still be enabled by instantiating a SSLContext
     manually.

   - bpo-22641(111): In asyncio, the default SSL context for client
     connections is now created using ssl.create_default_context(), for
     stronger security.

   - bpo-17401(112): Include closefd in io.FileIO repr.

   - bpo-21338(113): 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(114): Convert the array and cmath modules to Argument
     Clinic.

   - bpo-18643(115): Add socket.socketpair() on Windows.

   - bpo-22435(116): Fix a file descriptor leak when socketserver bind
     fails.

   - bpo-13096(117): Fixed segfault in CTypes POINTER handling of large
     values.

   - bpo-11694(118): Raise ConversionError in xdrlib as documented.
     Patch by Filip Gruszczyński and Claudiu Popa.

   - bpo-19380(119): Optimized parsing of regular expressions.

   - bpo-1519638(120): Now unmatched groups are replaced with empty
     strings in re.sub() and re.subn().

   - bpo-18615(121): sndhdr.what/whathdr now return a namedtuple.

   - bpo-22462(122): Fix pyexpat’s creation of a dummy frame to make it
     appear in exception tracebacks.

   - bpo-21965(123): Add support for in-memory SSL to the ssl module.
     Patch by Geert Jansen.

   - bpo-21173(124): Fix len() on a WeakKeyDictionary when .clear() was
     called with an iterator alive.

   - bpo-11866(125): Eliminated race condition in the computation of
     names for new threads.

   - bpo-21905(126): Avoid RuntimeError in pickle.whichmodule() when
     sys.modules is mutated while iterating.  Patch by Olivier Grisel.

   - bpo-11271(127): 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(128): 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(129): The zipfile module CLI now adds entries for
     directories (including empty directories) in ZIP file.

   - bpo-22449(130): In the ssl.SSLContext.load_default_certs, consult
     the environmental variables SSL_CERT_DIR and SSL_CERT_FILE on
     Windows.

   - bpo-22508(131): 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(132): Added non derived UTF-8 aliases to locale aliases
     table.

   - bpo-20079(133): Added locales supported in glibc 2.18 to locale
     alias table.

   - bpo-20218(134): Added convenience methods read_text/write_text and
     read_bytes/ write_bytes to pathlib.Path objects.

   - bpo-22396(135): 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(136): When an io.BufferedRWPair object is deallocated,
     clear its weakrefs.

   - bpo-22437(137): Number of capturing groups in regular expression is
     no longer limited by 100.

   - bpo-17442(138): InteractiveInterpreter now displays the full
     chained traceback in its showtraceback method, to match the built
     in interactive interpreter.

   - bpo-23392(139): Added tests for marshal C API that works with
     FILE*.

   - bpo-10510(140): distutils register and upload methods now use HTML
     standards compliant CRLF line endings.

   - bpo-9850(141): Fixed macpath.join() for empty first component.
     Patch by Oleg Oshmyan.

   - bpo-5309(142): distutils’ build and build_ext commands now accept a
     ‘-j’ option to enable parallel building of extension modules.

   - bpo-22448(143): Improve canceled timer handles cleanup to prevent
     unbound memory usage.  Patch by Joshua Moore-Oliva.

   - bpo-22427(144): TemporaryDirectory no longer attempts to clean up
     twice when used in the with statement in generator.

   - bpo-22362(145): Forbidden ambiguous octal escapes out of range
     0-0o377 in regular expressions.

   - bpo-20912(146): Now directories added to ZIP file have correct Unix
     and MS-DOS directory attributes.

   - bpo-21866(147): ZipFile.close() no longer writes ZIP64 central
     directory records if allowZip64 is false.

   - bpo-22278(148): Fix urljoin problem with relative urls, a
     regression observed after changes to issue22118 were submitted.

   - bpo-22415(149): Fixed debugging output of the GROUPREF_EXISTS
     opcode in the re module.  Removed trailing spaces in debugging
     output.

   - bpo-22423(150): Unhandled exception in thread no longer causes
     unhandled AttributeError when sys.stderr is None.

   - bpo-21332(151): Ensure that ‘bufsize=1’ in subprocess.Popen()
     selects line buffering, rather than block buffering.  Patch by
     Akira Li.

   - bpo-21091(152): Fix API bug:
     email.message.EmailMessage.is_attachment is now a method.

   - bpo-21079(153): Fix email.message.EmailMessage.is_attachment to
     return the correct result when the header has parameters as well as
     a value.

   - bpo-22247(154): Add NNTPError to nntplib.__all__.

   - bpo-22366(155): 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(156): The warnings registries are now reset when the
     filters are modified.

   - bpo-22419(157): 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(158): 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(159): An exception in Tkinter callback no longer crashes
     the program when it is run with pythonw.exe.

   - bpo-22168(160): Prevent turtle AttributeError with non-default
     Canvas on OS X.

   - bpo-21147(161): sqlite3 now raises an exception if the request
     contains a null character instead of truncating it.  Based on patch
     by Victor Stinner.

   - bpo-13968(162): The glob module now supports recursive search in
     subdirectories using the ‘**’ pattern.

   - bpo-21951(163): Fixed a crash in Tkinter on AIX when called Tcl
     command with empty string or tuple argument.

   - bpo-21951(164): Tkinter now most likely raises MemoryError instead
     of crash if the memory allocation fails.

   - bpo-22338(165): Fix a crash in the json module on memory allocation
     failure.

   - bpo-12410(166): imaplib.IMAP4 now supports the context management
     protocol.  Original patch by Tarek Ziadé.

   - bpo-21270(167): We now override tuple methods in mock.call objects
     so that they can be used as normal call attributes.

   - bpo-16662(168): 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(169): First letter no longer is stripped from the
     "status" key in the result of Treeview.heading().

   - bpo-19524(170): Fixed resource leak in the HTTP connection when an
     invalid response is received.  Patch by Martin Panter.

   - bpo-20421(171): Add a .version() method to SSL sockets exposing the
     actual protocol version in use.

   - bpo-19546(172): configparser exceptions no longer expose
     implementation details.  Chained KeyErrors are removed, which leads
     to cleaner tracebacks.  Patch by Claudiu Popa.

   - bpo-22051(173): 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(174): 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(175): 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(176): Turtledemo buttons no longer disappear when the
     window is shrunk.  Original patches by Jan Kanis and Lita Cho.

   - bpo-22043(177): 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(178): Add a default number of workers to
     ThreadPoolExecutor equal to 5 times the number of CPUs.  Patch by
     Claudiu Popa.

   - bpo-22216(179): 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(180): 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(181): 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(182): 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(183): 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(184): signal.set_wakeup_fd(fd) now raises an exception if
     the file descriptor is in blocking mode.

   - bpo-16808(185): inspect.stack() now returns a named tuple instead
     of a tuple.  Patch by Daniel Shahaf.

   - bpo-22236(186): Fixed Tkinter images copying operations in
     NoDefaultRoot mode.

   - bpo-2527(187): 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(188): 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(189): Added the "members" parameter to TarFile.list().

   - bpo-19628(190): Allow compileall recursion depth to be specified
     with a -r option.

   - bpo-15696(191): Add a __sizeof__ implementation for mmap objects on
     Windows.

   - bpo-22068(192): Avoided reference loops with Variables and Fonts in
     Tkinter.

   - bpo-22165(193): SimpleHTTPRequestHandler now supports undecodable
     file names.

   - bpo-15381(194): Optimized line reading in io.BytesIO.

   - bpo-8797(195): Raise HTTPError on failed Basic Authentication
     immediately.  Initial patch by Sam Bull.

   - bpo-20729(196): Restored the use of lazy
     iterkeys()/itervalues()/iteritems() in the mailbox module.

   - bpo-21448(197): Changed FeedParser feed() to avoid O(N**2) behavior
     when parsing long line.  Original patch by Raymond Hettinger.

   - bpo-22184(198): The functools LRU Cache decorator factory now gives
     an earlier and clearer error message when the user forgets the
     required parameters.

   - bpo-17923(199): glob() patterns ending with a slash no longer match
     non-dirs on AIX. Based on patch by Delhallt.

   - bpo-21725(200): Added support for RFC 6531 (SMTPUTF8) in smtpd.

   - bpo-22176(201): 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(202): Added support for the "xztar" format in the shutil
     module.

   - bpo-21121(203): Don’t force 3rd party C extensions to be built with
     -Werror=declaration-after-statement.

   - bpo-21975(204): 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(205): Convert posixmodule to use Argument Clinic.

   - bpo-21539(206): Add an `exists_ok' argument to ‘Pathlib.mkdir()’ to
     mimic ‘mkdir -p’ and *note os.makedirs(): 3c2. functionality.  When
     true, ignore FileExistsErrors.  Patch by Berker Peksag.

   - bpo-22127(207): Bypass IDNA for pure-ASCII host names in the socket
     module (in particular for numeric IPs).

   - bpo-21047(208): 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(209): the strict mode and argument of HTMLParser,
     HTMLParser.error, and the HTMLParserError exception have been
     removed.

   - bpo-22085(210): Dropped support of Tk 8.3 in Tkinter.

   - bpo-21580(211): Now Tkinter correctly handles bytes arguments
     passed to Tk.  In particular this allows initializing images from
     binary data.

   - bpo-22003(212): 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(213): On Windows, signal.set_wakeup_fd() now also
     supports sockets.  A side effect is that Python depends to the
     WinSock library.

   - bpo-22054(214): 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(215): Make turtledemo start as active on OS X even when
     run with subprocess.  Patch by Lita Cho.

   - bpo-21704(216): Fix build error for _multiprocessing when
     semaphores are not available.  Patch by Arfrever Frehtes Taifersar
     Arahesis.

   - bpo-20173(217): 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(218): Reprs of most Python implemented classes now
     contain actual class name instead of hardcoded one.

   - bpo-21947(219): The dis module can now disassemble
     generator-iterator objects based on their gi_code attribute.  Patch
     by Clement Rouault.

   - bpo-16133(220): The asynchat.async_chat.handle_read() method now
     ignores BlockingIOError exceptions.

   - bpo-22044(221): Fixed premature DECREF in call_tzinfo_method.
     Patch by Tom Flanagan.

   - bpo-19884(222): 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(223): Removed a number of out-of-dated and non-working for
     a long time Tkinter methods.

   - bpo-6167(224): 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(225): Clean up and speed up the ntpath module.

   - bpo-21888(226): plistlib’s load() and loads() now work if the fmt
     parameter is specified.

   - bpo-22032(227): __qualname__ instead of __name__ is now always used
     to format fully qualified class names of Python implemented
     classes.

   - bpo-22031(228): Reprs now always use hexadecimal format with the
     "0x" prefix when contain an id in form " at 0x...".

   - bpo-22018(229): signal.set_wakeup_fd() now raises an OSError
     instead of a ValueError on ‘fstat()’ failure.

   - bpo-21044(230): tarfile.open() now handles fileobj with an integer
     ’name’ attribute.  Based on patch by Antoine Pietri.

   - bpo-21966(231): Respect -q command-line option when code module is
     ran.

   - bpo-19076(232): Don’t pass the redundant ’file’ argument to
     self.error().

   - bpo-16382(233): Improve exception message of warnings.warn() for
     bad category.  Initial patch by Phil Elson.

   - bpo-21932(234): os.read() now uses a ‘Py_ssize_t()’ 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(235): Fixed source file viewing in pydoc’s server mode on
     Windows.

   - bpo-11259(236): asynchat.async_chat().set_terminator() now raises a
     ValueError if the number of received bytes is negative.

   - bpo-12523(237): asynchat.async_chat.push() now raises a TypeError
     if it doesn’t get a bytes string

   - bpo-21707(238): Add missing kwonlyargcount argument to
     ModuleFinder.replace_paths_in_code().

   - bpo-20639(239): calling Path.with_suffix(’’) allows removing the
     suffix again.  Patch by July Tikhonov.

   - bpo-21714(240): Disallow the construction of invalid paths using
     Path.with_name().  Original patch by Antony Lee.

   - bpo-15014(241): Added ’auth’ method to smtplib to make implementing
     auth mechanisms simpler, and used it internally in the login
     method.

   - bpo-21151(242): Fixed a segfault in the winreg module when ‘None’
     is passed as a ‘REG_BINARY’ value to SetValueEx.  Patch by John
     Ehresman.

   - bpo-21090(243): 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(244): headers parameter of wsgiref.headers.Headers is now
     optional.  Initial patch by Pablo Torres Navarrete and SilentGhost.

   - bpo-21781(245): ssl.RAND_add() now supports strings longer than 2
     GB.

   - bpo-21679(246): Prevent extraneous fstat() calls during open().
     Patch by Bohuslav Kabrda.

   - bpo-21863(247): cProfile now displays the module name of C
     extension functions, in addition to their own name.

   - bpo-11453(248): 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(249): Better handling of Python exceptions in the sqlite3
     module.

   - bpo-21476(250): Make sure the email.parser.BytesParser
     TextIOWrapper is discarded after parsing, so the input file isn’t
     unexpectedly closed.

   - bpo-20295(251): imghdr now recognizes OpenEXR format images.

   - bpo-21729(252): Used the "with" statement in the dbm.dumb module to
     ensure files closing.  Patch by Claudiu Popa.

   - bpo-21491(253): socketserver: Fix a race condition in child
     processes reaping.

   - bpo-21719(254): Added the ‘st_file_attributes’ field to
     os.stat_result on Windows.

   - bpo-21832(255): Require named tuple inputs to be exact strings.

   - bpo-21722(256): The distutils "upload" command now exits with a
     non-zero return code when uploading fails.  Patch by Martin
     Dengler.

   - bpo-21723(257): asyncio.Queue: support any type of number (ex:
     float) for the maximum size.  Patch written by Vajrasky Kok.

   - bpo-21711(258): support for "site-python" directories has now been
     removed from the site module (it was deprecated in 3.4).

   - bpo-17552(259): 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(260): dbm.dump.open() now always creates a new database
     when the flag has the value ’n’.  Patch by Claudiu Popa.

   - bpo-21326(261): 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(262): Prevent a security hole in CGIHTTPServer by URL
     unquoting paths before checking for a CGI script at that path.

   - bpo-21310(263): Fixed possible resource leak in failed open().

   - bpo-21256(264): Printout of keyword args should be in deterministic
     order in a mock function call.  This will help to write better
     doctests.

   - bpo-21677(265): Fixed chaining nonnormalized exceptions in io
     close() methods.

   - bpo-11709(266): Fix the pydoc.help function to not fail when
     sys.stdin is not a valid file.

   - bpo-21515(267): tempfile.TemporaryFile now uses os.O_TMPFILE flag
     is available.

   - bpo-13223(268): Fix pydoc.writedoc so that the HTML documentation
     for methods that use ’self’ in the example code is generated
     correctly.

   - bpo-21463(269): In urllib.request, fix pruning of the FTP cache.

   - bpo-21618(270): 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(271): Introduce importlib.util.module_from_spec() as the
     preferred way to create a new module.

   - bpo-21552(272): Fixed possible integer overflow of too long string
     lengths in the tkinter module on 64-bit platforms.

   - bpo-14315(273): 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(274): Added "key" and "reverse" parameters to
     heapq.merge().  (First draft of patch contributed by Simon Sapin.)

   - bpo-21402(275): tkinter.ttk now works when default root window is
     not set.

   - bpo-3015(276): _tkinter.create() now creates tkapp object with
     wantobject=1 by default.

   - bpo-10203(277): sqlite3.Row now truly supports sequence protocol.
     In particular it supports reverse() and negative indices.  Original
     patch by Claudiu Popa.

   - bpo-18807(278): 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(279): Added support for the WebP image type in the imghdr
     module.  Patch by Fabrice Aneche and Claudiu Popa.

   - bpo-21513(280): Speedup some properties of IP addresses
     (IPv4Address, IPv6Address) such as .is_private or .is_multicast.

   - bpo-21137(281): Improve the repr for threading.Lock() and its
     variants by showing the "locked" or "unlocked" status.  Patch by
     Berker Peksag.

   - bpo-21538(282): The plistlib module now supports loading of binary
     plist files when reference or offset size is not a power of two.

   - bpo-21455(283): Add a default backlog to socket.listen().

   - bpo-21525(284): Most Tkinter methods which accepted tuples now
     accept lists too.

   - bpo-22166(285): 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(286): Tkinter tests now don’t reuse default root window.
     New root window is created for every test class.

   - bpo-10744(287): Fix PEP 3118(288) format strings on ctypes objects
     with a nontrivial shape.

   - bpo-20826(289): Optimize ipaddress.collapse_addresses().

   - bpo-21487(290): Optimize ipaddress.summarize_address_range() and
     ipaddress.{IPv4Network,IPv6Network}.subnets().

   - bpo-21486(291): Optimize parsing of netmasks in
     ipaddress.IPv4Network and ipaddress.IPv6Network.

   - bpo-13916(292): Disallowed the surrogatepass error handler for non
     UTF-* encodings.

   - bpo-20998(293): Fixed re.fullmatch() of repeated single character
     pattern with ignore case.  Original patch by Matthew Barnett.

   - bpo-21075(294): fileinput.FileInput now reads bytes from standard
     stream if binary mode is specified.  Patch by Sam Kimbrel.

   - bpo-19775(295): Add a samefile() method to pathlib Path objects.
     Initial patch by Vajrasky Kok.

   - bpo-21226(296): Set up modules properly in
     PyImport_ExecCodeModuleObject (and friends).

   - bpo-21398(297): Fix a unicode error in the pydoc pager when the
     documentation contains characters not encodable to the stdout
     encoding.

   - bpo-16531(298): ipaddress.IPv4Network and ipaddress.IPv6Network now
     accept an (address, netmask) tuple argument, so as to easily
     construct network objects from existing addresses.

   - bpo-21156(299): importlib.abc.InspectLoader.source_to_code() is now
     a staticmethod.

   - bpo-21424(300): Simplified and optimized heaqp.nlargest() and
     nmsmallest() to make fewer tuple comparisons.

   - bpo-21396(301): Fix TextIOWrapper(..., write_through=True) to not
     force a flush() on the underlying binary stream.  Patch by akira.

   - bpo-18314(302): Unlink now removes junctions on Windows.  Patch by
     Kim Gräsman

   - bpo-21088(303): Bugfix for curses.window.addch() regression in
     3.4.0.  In porting to Argument Clinic, the first two arguments were
     reversed.

   - bpo-21407(304): _decimal: The module now supports function
     signatures.

   - bpo-10650(305): 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(306): 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(307): Have the OrderedDict mark deleted links as
     unusable.  This gives an early failure if the link is deleted
     during iteration.

   - bpo-21421(308): Add __slots__ to the MappingViews ABC. Patch by
     Josh Rosenberg.

   - bpo-21101(309): Eliminate double hashing in the C speed-up code for
     collections.Counter().

   - bpo-21321(310): itertools.islice() now releases the reference to
     the source iterator when the slice is exhausted.  Patch by Anton
     Afanasyev.

   - bpo-21057(311): 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(312): 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(313): removed previously deprecated asyncore.dispatcher
     __getattr__ cheap inheritance hack.

   - bpo-9815(314): assertRaises now tries to clear references to local
     variables in the exception’s traceback.

   - bpo-19940(315): 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(316): Calling sys.flags.__new__ would crash the
     interpreter, now it raises a TypeError.

   - bpo-19385(317): Make operations on a closed dbm.dumb database
     always raise the same exception.

   - bpo-21207(318): Detect when the os.urandom cached fd has been
     closed or replaced, and open it anew.

   - bpo-21291(319): 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(320): Path objects can now be instantiated from str
     subclass instances (such as ‘numpy.str_’).

   - bpo-15002(321): 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(322): mindom now raises a custom ValueError indicating it
     doesn’t support spaces in URIs instead of letting a ’split’
     ValueError bubble up.

   - bpo-21068(323): The ssl.PROTOCOL* constants are now enum members.

   - bpo-21276(324): posixmodule: Don’t define USE_XATTRS on KFreeBSD
     and the Hurd.

   - bpo-21262(325): New method assert_not_called for Mock.  It raises
     AssertionError if the mock has been called.

   - bpo-21238(326): New keyword argument ‘unsafe’ to Mock.  It raises
     *note AttributeError: 3a0. incase of an attribute startswith assert
     or assret.

   - bpo-20896(327): ssl.get_server_certificate() now uses
     PROTOCOL_SSLv23, not PROTOCOL_SSLv3, for maximum compatibility.

   - bpo-21239(328): patch.stopall() didn’t work deterministically when
     the same name was patched more than once.

   - bpo-21203(329): Updated fileConfig and dictConfig to remove
     inconsistencies.  Thanks to Jure Koren for the patch.

   - bpo-21222(330): Passing name keyword argument to
     mock.create_autospec now works.

   - bpo-21197(331): Add lib64 -> lib symlink in venvs on 64-bit non-OS
     X POSIX.

   - bpo-17498(332): 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(333): setting an iterable side_effect on a mock function
     created by create_autospec now works.  Patch by Kushal Das.

   - bpo-7776(334): Fix ‘Host:’ header and reconnection when using
     http.client.HTTPConnection.set_tunnel().  Patch by Nikolaus Rath.

   - bpo-20968(335): unittest.mock.MagicMock now supports division.
     Patch by Johannes Baiter.

   - bpo-21529(336): Fix arbitrary memory access in
     JSONDecoder.raw_decode with a negative second parameter.  Bug
     reported by Guido Vranken.  (See also: CVE-2014-4616)

   - bpo-21169(337): getpass now handles non-ascii characters that the
     input stream encoding cannot encode by re-encoding using the
     replace error handler.

   - bpo-21171(338): Fixed undocumented filter API of the rot13 codec.
     Patch by Berker Peksag.

   - bpo-20539(339): Improved math.factorial error message for large
     positive inputs and changed exception type (OverflowError ->
     ValueError) for large negative inputs.

   - bpo-21172(340): isinstance check relaxed from dict to
     collections.Mapping.

   - bpo-21155(341): asyncio.EventLoop.create_unix_server() now raises a
     ValueError if path and sock are specified at the same time.

   - bpo-21136(342): Avoid unnecessary normalization of Fractions
     resulting from power and other operations.  Patch by Raymond
     Hettinger.

   - bpo-17621(343): Introduce importlib.util.LazyLoader.

   - bpo-21076(344): signal module constants were turned into enums.
     Patch by Giampaolo Rodola’.

   - bpo-20636(345): Improved the repr of Tkinter widgets.

   - bpo-19505(346): The items, keys, and values views of OrderedDict
     now support reverse iteration using reversed().

   - bpo-21149(347): Improved thread-safety in logging cleanup during
     interpreter shutdown.  Thanks to Devin Jeanpierre for the patch.

   - bpo-21058(348): Fix a leak of file descriptor in *note
     tempfile.NamedTemporaryFile(): d4e, close the file descriptor if
     *note io.open(): 65f. fails

   - bpo-21200(349): Return None from pkgutil.get_loader() when __spec__
     is missing.

   - bpo-21013(350): Enhance ssl.create_default_context() when used for
     server side sockets to provide better security by default.

   - bpo-20145(351): ‘assertRaisesRegex’ and ‘assertWarnsRegex’ now
     raise a TypeError if the second argument is not a string or
     compiled regex.

   - bpo-20633(352): Replace relative import by absolute import.

   - bpo-20980(353): Stop wrapping exception when using ThreadPool.

   - bpo-21082(354): In os.makedirs, do not set the process-wide umask.
     Note this changes behavior of makedirs when exist_ok=True.

   - bpo-20990(355): Fix issues found by pyflakes for multiprocessing.

   - bpo-21015(356): 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(357): Improve the command-line interface of json.tool.

   - bpo-20995(358): Enhance default ciphers used by the ssl module to
     enable better security and prioritize perfect forward secrecy.

   - bpo-20884(359): Don’t assume that __file__ is defined on
     importlib.__init__.

   - bpo-21499(360): Ignore __builtins__ in several
     test_importlib.test_api tests.

   - bpo-20627(361): xmlrpc.client.ServerProxy is now a context manager.

   - bpo-19165(362): The formatter module now raises DeprecationWarning
     instead of PendingDeprecationWarning.

   - bpo-13936(363): Remove the ability of datetime.time instances to be
     considered false in boolean contexts.

   - bpo-18931(364): selectors module now supports /dev/poll on Solaris.
     Patch by Giampaolo Rodola’.

   - bpo-19977(365): When the ‘LC_TYPE’ locale is the POSIX locale (‘C’
     locale), *note sys.stdin: 312. and *note sys.stdout: 313. are now
     using the ‘surrogateescape’ error handler, instead of the ‘strict’
     error handler.

   - bpo-20574(366): Implement incremental decoder for cp65001 code
     (Windows code page 65001, Microsoft UTF-8).

   - bpo-20879(367): 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(368): Include the broadcast address in the usuable hosts
     for IPv6 in ipaddress.

   - bpo-11599(369): 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(370): distutils should not produce unhelpful "error: None"
     messages anymore.  distutils.util.grok_environment_error is kept
     but doc-deprecated.

   - bpo-20875(371): Prevent possible gzip "’read’ is not defined"
     NameError.  Patch by Claudiu Popa.

   - bpo-11558(372): ‘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(373): RE pattern methods now accept the string keyword
     parameters as documented.  The pattern and source keyword
     parameters are left as deprecated aliases.

   - bpo-20778(374): Fix modulefinder to work with bytecode-only
     modules.

   - bpo-20791(375): copy.copy() now doesn’t make a copy when the input
     is a bytes object.  Initial patch by Peter Otten.

   - bpo-19748(376): On AIX, time.mktime() now raises an OverflowError
     for year outsize range [1902; 2037].

   - bpo-19573(377): inspect.signature: Use enum for parameter kind
     constants.

   - bpo-20726(378): inspect.signature: Make Signature and Parameter
     picklable.

   - bpo-17373(379): Add inspect.Signature.from_callable method.

   - bpo-20378(380): Improve repr of inspect.Signature and
     inspect.Parameter.

   - bpo-20816(381): Fix inspect.getcallargs() to raise correct
     TypeError for missing keyword-only arguments.  Patch by Jeremiah
     Lowin.

   - bpo-20817(382): Fix inspect.getcallargs() to fail correctly if more
     than 3 arguments are missing.  Patch by Jeremiah Lowin.

   - bpo-6676(383): 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(384): 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(385): inspect.Signature and inspect.Parameter are now
     hashable.  Thanks to Antony Lee for bug reports and suggestions.

   - bpo-15916(386): doctest.DocTestSuite returns an empty
     unittest.TestSuite instead of raising ValueError if it finds no
     tests

   - bpo-21209(387): 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(388)).

   - bpo-21311(389): Avoid exception in _osx_support with non-standard
     compiler configurations.  Patch by John Szakmeister.

   - bpo-11571(390): Ensure that the turtle window becomes the topmost
     window when launched on OS X.

   - bpo-21801(391): Validate that __signature__ is None or an instance
     of Signature.

   - bpo-21923(392): Prevent AttributeError in
     distutils.sysconfig.customize_compiler due to possible
     uninitialized _config_vars.

   - bpo-21323(393): Fix http.server to again handle scripts in CGI
     subdirectories, broken by the fix for security bpo-19435(394).
     Patch by Zach Byrne.

   - bpo-22733(395): Fix ffi_prep_args not zero-extending argument
     values correctly on 64-bit Windows.

   - bpo-23302(396): 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/issue23399

   (2) https://bugs.python.org/issue20289

   (3) https://bugs.python.org/issue13128

   (4) https://bugs.python.org/issue15381

   (5) https://bugs.python.org/issue22818

   (6) https://bugs.python.org/issue23099

   (7) https://bugs.python.org/issue23326

   (8) https://bugs.python.org/issue21408

   (9) https://bugs.python.org/issue23363

   (10) https://bugs.python.org/issue23364

   (11) https://bugs.python.org/issue23366

   (12) https://bugs.python.org/issue23369

   (13) https://bugs.python.org/issue23353

   (14) https://bugs.python.org/issue14099

   (15) https://bugs.python.org/issue14099

   (16) https://bugs.python.org/issue19361

   (17) https://bugs.python.org/issue18518

   (18) https://bugs.python.org/issue23094

   (19) https://bugs.python.org/issue23268

   (20) https://bugs.python.org/issue21408

   (21) https://bugs.python.org/issue19996

   (22) https://bugs.python.org/issue20188

   (23) https://bugs.python.org/issue23133

   (24) https://bugs.python.org/issue23248

   (25) https://bugs.python.org/issue23266

   (26) https://bugs.python.org/issue23098

   (27) https://bugs.python.org/issue21817

   (28) https://bugs.python.org/issue15955

   (29) https://bugs.python.org/issue23250

   (30) https://bugs.python.org/issue23063

   (31) https://bugs.python.org/issue23209

   (32) https://bugs.python.org/issue23225

   (33) https://bugs.python.org/issue17911

   (34) https://bugs.python.org/issue17911

   (35) https://bugs.python.org/issue19777

   (36) https://bugs.python.org/issue23206

   (37) https://bugs.python.org/issue23185

   (38) https://bugs.python.org/issue23186

   (39) https://bugs.python.org/issue23143

   (40) https://bugs.python.org/issue23132

   (41) https://bugs.python.org/issue19776

   (42) https://bugs.python.org/issue23112

   (43) https://bugs.python.org/issue21793

   (44) https://bugs.python.org/issue23093

   (45) https://bugs.python.org/issue23111

   (46) https://bugs.python.org/issue22585

   (47) https://bugs.python.org/issue19104

   (48) https://bugs.python.org/issue23071

   (49) https://bugs.python.org/issue22783

   (50) https://bugs.python.org/issue15513

   (51) https://bugs.python.org/issue19858

   (52) https://bugs.python.org/issue22095

   (53) https://bugs.python.org/issue23016

   (54) https://bugs.python.org/issue21775

   (55) https://bugs.python.org/issue1218234

   (56) https://bugs.python.org/issue21740

   (57) https://bugs.python.org/issue23009

   (58) https://bugs.python.org/issue22959

   (59) https://bugs.python.org/issue22696

   (60) https://bugs.python.org/issue16043

   (61) https://bugs.python.org/issue14099

   (62) https://bugs.python.org/issue22966

   (63) https://bugs.python.org/issue21971

   (64) https://bugs.python.org/issue21032

   (65) https://bugs.python.org/issue22407

   (66) https://bugs.python.org/issue22902

   (67) https://bugs.python.org/issue22960

   (68) https://bugs.python.org/issue22389

   (69) https://bugs.python.org/issue21356

   (70) https://bugs.python.org/issue22915

   (71) https://bugs.python.org/issue22609

   (72) https://bugs.python.org/issue22940

   (73) https://bugs.python.org/issue19676

   (74) https://bugs.python.org/issue22788

   (75) https://bugs.python.org/issue22921

   (76) https://bugs.python.org/issue22894

   (77) https://bugs.python.org/issue22796

   (78) https://bugs.python.org/issue22370

   (79) https://bugs.python.org/issue22841

   (80) https://bugs.python.org/issue19494

   (81) https://bugs.python.org/issue22578

   (82) https://bugs.python.org/issue22849

   (83) https://bugs.python.org/issue12728

   (84) https://bugs.python.org/issue22821

   (85) https://bugs.python.org/issue21650

   (86) https://bugs.python.org/issue22824

   (87) https://bugs.python.org/issue22824

   (88) https://bugs.python.org/issue22406

   (89) https://bugs.python.org/issue17293

   (90) https://bugs.python.org/issue22769

   (91) https://bugs.python.org/issue22417

   (92) https://bugs.python.org/issue22775

   (93) https://bugs.python.org/issue22776

   (94) https://bugs.python.org/issue22665

   (95) https://bugs.python.org/issue6623

   (96) https://bugs.python.org/issue17381

   (97) https://bugs.python.org/issue22410

   (98) https://bugs.python.org/issue22759

   (99) https://bugs.python.org/issue8876

   (100) https://bugs.python.org/issue22217

   (101) https://bugs.python.org/issue22457

   (102) https://bugs.python.org/issue18216

   (103) https://bugs.python.org/issue13918

   (104) https://bugs.python.org/issue22676

   (105) https://bugs.python.org/issue18853

   (106) https://bugs.python.org/issue9351

   (107) https://bugs.python.org/issue7559

   (108) https://bugs.python.org/issue19746

   (109) https://bugs.python.org/issue21991

   (110) https://bugs.python.org/issue22638

   (111) https://bugs.python.org/issue22641

   (112) https://bugs.python.org/issue17401

   (113) https://bugs.python.org/issue21338

   (114) https://bugs.python.org/issue20152

   (115) https://bugs.python.org/issue18643

   (116) https://bugs.python.org/issue22435

   (117) https://bugs.python.org/issue13096

   (118) https://bugs.python.org/issue11694

   (119) https://bugs.python.org/issue19380

   (120) https://bugs.python.org/issue1519638

   (121) https://bugs.python.org/issue18615

   (122) https://bugs.python.org/issue22462

   (123) https://bugs.python.org/issue21965

   (124) https://bugs.python.org/issue21173

   (125) https://bugs.python.org/issue11866

   (126) https://bugs.python.org/issue21905

   (127) https://bugs.python.org/issue11271

   (128) https://bugs.python.org/issue21883

   (129) https://bugs.python.org/issue22219

   (130) https://bugs.python.org/issue22449

   (131) https://bugs.python.org/issue22508

   (132) https://bugs.python.org/issue20076

   (133) https://bugs.python.org/issue20079

   (134) https://bugs.python.org/issue20218

   (135) https://bugs.python.org/issue22396

   (136) https://bugs.python.org/issue22517

   (137) https://bugs.python.org/issue22437

   (138) https://bugs.python.org/issue17442

   (139) https://bugs.python.org/issue23392

   (140) https://bugs.python.org/issue10510

   (141) https://bugs.python.org/issue9850

   (142) https://bugs.python.org/issue5309

   (143) https://bugs.python.org/issue22448

   (144) https://bugs.python.org/issue22427

   (145) https://bugs.python.org/issue22362

   (146) https://bugs.python.org/issue20912

   (147) https://bugs.python.org/issue21866

   (148) https://bugs.python.org/issue22278

   (149) https://bugs.python.org/issue22415

   (150) https://bugs.python.org/issue22423

   (151) https://bugs.python.org/issue21332

   (152) https://bugs.python.org/issue21091

   (153) https://bugs.python.org/issue21079

   (154) https://bugs.python.org/issue22247

   (155) https://bugs.python.org/issue22366

   (156) https://bugs.python.org/issue4180

   (157) https://bugs.python.org/issue22419

   (158) https://bugs.python.org/issue20537

   (159) https://bugs.python.org/issue22384

   (160) https://bugs.python.org/issue22168

   (161) https://bugs.python.org/issue21147

   (162) https://bugs.python.org/issue13968

   (163) https://bugs.python.org/issue21951

   (164) https://bugs.python.org/issue21951

   (165) https://bugs.python.org/issue22338

   (166) https://bugs.python.org/issue12410

   (167) https://bugs.python.org/issue21270

   (168) https://bugs.python.org/issue16662

   (169) https://bugs.python.org/issue22226

   (170) https://bugs.python.org/issue19524

   (171) https://bugs.python.org/issue20421

   (172) https://bugs.python.org/issue19546

   (173) https://bugs.python.org/issue22051

   (174) https://bugs.python.org/issue21933

   (175) https://bugs.python.org/issue21597

   (176) https://bugs.python.org/issue18132

   (177) https://bugs.python.org/issue22043

   (178) https://bugs.python.org/issue21527

   (179) https://bugs.python.org/issue22216

   (180) https://bugs.python.org/issue22098

   (181) https://bugs.python.org/issue22185

   (182) https://bugs.python.org/issue22287

   (183) https://bugs.python.org/issue22182

   (184) https://bugs.python.org/issue22042

   (185) https://bugs.python.org/issue16808

   (186) https://bugs.python.org/issue22236

   (187) https://bugs.python.org/issue2527

   (188) https://bugs.python.org/issue22118

   (189) https://bugs.python.org/issue21549

   (190) https://bugs.python.org/issue19628

   (191) https://bugs.python.org/issue15696

   (192) https://bugs.python.org/issue22068

   (193) https://bugs.python.org/issue22165

   (194) https://bugs.python.org/issue15381

   (195) https://bugs.python.org/issue8797

   (196) https://bugs.python.org/issue20729

   (197) https://bugs.python.org/issue21448

   (198) https://bugs.python.org/issue22184

   (199) https://bugs.python.org/issue17923

   (200) https://bugs.python.org/issue21725

   (201) https://bugs.python.org/issue22176

   (202) https://bugs.python.org/issue5411

   (203) https://bugs.python.org/issue21121

   (204) https://bugs.python.org/issue21975

   (205) https://bugs.python.org/issue20170

   (206) https://bugs.python.org/issue21539

   (207) https://bugs.python.org/issue22127

   (208) https://bugs.python.org/issue21047

   (209) https://bugs.python.org/issue15114

   (210) https://bugs.python.org/issue22085

   (211) https://bugs.python.org/issue21580

   (212) https://bugs.python.org/issue22003

   (213) https://bugs.python.org/issue22018

   (214) https://bugs.python.org/issue22054

   (215) https://bugs.python.org/issue17172

   (216) https://bugs.python.org/issue21704

   (217) https://bugs.python.org/issue20173

   (218) https://bugs.python.org/issue22033

   (219) https://bugs.python.org/issue21947

   (220) https://bugs.python.org/issue16133

   (221) https://bugs.python.org/issue22044

   (222) https://bugs.python.org/issue19884

   (223) https://bugs.python.org/issue4350

   (224) https://bugs.python.org/issue6167

   (225) https://bugs.python.org/issue15275

   (226) https://bugs.python.org/issue21888

   (227) https://bugs.python.org/issue22032

   (228) https://bugs.python.org/issue22031

   (229) https://bugs.python.org/issue22018

   (230) https://bugs.python.org/issue21044

   (231) https://bugs.python.org/issue21966

   (232) https://bugs.python.org/issue19076

   (233) https://bugs.python.org/issue16382

   (234) https://bugs.python.org/issue21932

   (235) https://bugs.python.org/issue21942

   (236) https://bugs.python.org/issue11259

   (237) https://bugs.python.org/issue12523

   (238) https://bugs.python.org/issue21707

   (239) https://bugs.python.org/issue20639

   (240) https://bugs.python.org/issue21714

   (241) https://bugs.python.org/issue15014

   (242) https://bugs.python.org/issue21151

   (243) https://bugs.python.org/issue21090

   (244) https://bugs.python.org/issue5800

   (245) https://bugs.python.org/issue21781

   (246) https://bugs.python.org/issue21679

   (247) https://bugs.python.org/issue21863

   (248) https://bugs.python.org/issue11453

   (249) https://bugs.python.org/issue21858

   (250) https://bugs.python.org/issue21476

   (251) https://bugs.python.org/issue20295

   (252) https://bugs.python.org/issue21729

   (253) https://bugs.python.org/issue21491

   (254) https://bugs.python.org/issue21719

   (255) https://bugs.python.org/issue21832

   (256) https://bugs.python.org/issue21722

   (257) https://bugs.python.org/issue21723

   (258) https://bugs.python.org/issue21711

   (259) https://bugs.python.org/issue17552

   (260) https://bugs.python.org/issue18039

   (261) https://bugs.python.org/issue21326

   (262) https://bugs.python.org/issue21766

   (263) https://bugs.python.org/issue21310

   (264) https://bugs.python.org/issue21256

   (265) https://bugs.python.org/issue21677

   (266) https://bugs.python.org/issue11709

   (267) https://bugs.python.org/issue21515

   (268) https://bugs.python.org/issue13223

   (269) https://bugs.python.org/issue21463

   (270) https://bugs.python.org/issue21618

   (271) https://bugs.python.org/issue20383

   (272) https://bugs.python.org/issue21552

   (273) https://bugs.python.org/issue14315

   (274) https://bugs.python.org/issue13742

   (275) https://bugs.python.org/issue21402

   (276) https://bugs.python.org/issue3015

   (277) https://bugs.python.org/issue10203

   (278) https://bugs.python.org/issue18807

   (279) https://bugs.python.org/issue20197

   (280) https://bugs.python.org/issue21513

   (281) https://bugs.python.org/issue21137

   (282) https://bugs.python.org/issue21538

   (283) https://bugs.python.org/issue21455

   (284) https://bugs.python.org/issue21525

   (285) https://bugs.python.org/issue22166

   (286) https://bugs.python.org/issue22236

   (287) https://bugs.python.org/issue10744

   (288) https://www.python.org/dev/peps/pep-3118

   (289) https://bugs.python.org/issue20826

   (290) https://bugs.python.org/issue21487

   (291) https://bugs.python.org/issue21486

   (292) https://bugs.python.org/issue13916

   (293) https://bugs.python.org/issue20998

   (294) https://bugs.python.org/issue21075

   (295) https://bugs.python.org/issue19775

   (296) https://bugs.python.org/issue21226

   (297) https://bugs.python.org/issue21398

   (298) https://bugs.python.org/issue16531

   (299) https://bugs.python.org/issue21156

   (300) https://bugs.python.org/issue21424

   (301) https://bugs.python.org/issue21396

   (302) https://bugs.python.org/issue18314

   (303) https://bugs.python.org/issue21088

   (304) https://bugs.python.org/issue21407

   (305) https://bugs.python.org/issue10650

   (306) https://bugs.python.org/issue21469

   (307) https://bugs.python.org/issue19414

   (308) https://bugs.python.org/issue21421

   (309) https://bugs.python.org/issue21101

   (310) https://bugs.python.org/issue21321

   (311) https://bugs.python.org/issue21057

   (312) https://bugs.python.org/issue20951

   (313) https://bugs.python.org/issue13248

   (314) https://bugs.python.org/issue9815

   (315) https://bugs.python.org/issue19940

   (316) https://bugs.python.org/issue13204

   (317) https://bugs.python.org/issue19385

   (318) https://bugs.python.org/issue21207

   (319) https://bugs.python.org/issue21291

   (320) https://bugs.python.org/issue21127

   (321) https://bugs.python.org/issue15002

   (322) https://bugs.python.org/issue12220

   (323) https://bugs.python.org/issue21068

   (324) https://bugs.python.org/issue21276

   (325) https://bugs.python.org/issue21262

   (326) https://bugs.python.org/issue21238

   (327) https://bugs.python.org/issue20896

   (328) https://bugs.python.org/issue21239

   (329) https://bugs.python.org/issue21203

   (330) https://bugs.python.org/issue21222

   (331) https://bugs.python.org/issue21197

   (332) https://bugs.python.org/issue17498

   (333) https://bugs.python.org/issue17826

   (334) https://bugs.python.org/issue7776

   (335) https://bugs.python.org/issue20968

   (336) https://bugs.python.org/issue21529

   (337) https://bugs.python.org/issue21169

   (338) https://bugs.python.org/issue21171

   (339) https://bugs.python.org/issue20539

   (340) https://bugs.python.org/issue21172

   (341) https://bugs.python.org/issue21155

   (342) https://bugs.python.org/issue21136

   (343) https://bugs.python.org/issue17621

   (344) https://bugs.python.org/issue21076

   (345) https://bugs.python.org/issue20636

   (346) https://bugs.python.org/issue19505

   (347) https://bugs.python.org/issue21149

   (348) https://bugs.python.org/issue21058

   (349) https://bugs.python.org/issue21200

   (350) https://bugs.python.org/issue21013

   (351) https://bugs.python.org/issue20145

   (352) https://bugs.python.org/issue20633

   (353) https://bugs.python.org/issue20980

   (354) https://bugs.python.org/issue21082

   (355) https://bugs.python.org/issue20990

   (356) https://bugs.python.org/issue21015

   (357) https://bugs.python.org/issue21000

   (358) https://bugs.python.org/issue20995

   (359) https://bugs.python.org/issue20884

   (360) https://bugs.python.org/issue21499

   (361) https://bugs.python.org/issue20627

   (362) https://bugs.python.org/issue19165

   (363) https://bugs.python.org/issue13936

   (364) https://bugs.python.org/issue18931

   (365) https://bugs.python.org/issue19977

   (366) https://bugs.python.org/issue20574

   (367) https://bugs.python.org/issue20879

   (368) https://bugs.python.org/issue19157

   (369) https://bugs.python.org/issue11599

   (370) https://bugs.python.org/issue4931

   (371) https://bugs.python.org/issue20875

   (372) https://bugs.python.org/issue11558

   (373) https://bugs.python.org/issue20283

   (374) https://bugs.python.org/issue20778

   (375) https://bugs.python.org/issue20791

   (376) https://bugs.python.org/issue19748

   (377) https://bugs.python.org/issue19573

   (378) https://bugs.python.org/issue20726

   (379) https://bugs.python.org/issue17373

   (380) https://bugs.python.org/issue20378

   (381) https://bugs.python.org/issue20816

   (382) https://bugs.python.org/issue20817

   (383) https://bugs.python.org/issue6676

   (384) https://bugs.python.org/issue21117

   (385) https://bugs.python.org/issue20334

   (386) https://bugs.python.org/issue15916

   (387) https://bugs.python.org/issue21209

   (388) https://bugs.python.org/issue163

   (389) https://bugs.python.org/issue21311

   (390) https://bugs.python.org/issue11571

   (391) https://bugs.python.org/issue21801

   (392) https://bugs.python.org/issue21923

   (393) https://bugs.python.org/issue21323

   (394) https://bugs.python.org/issue19435

   (395) https://bugs.python.org/issue22733

   (396) https://bugs.python.org/issue23302


File: python.info,  Node: IDLE<53>,  Next: Build<56>,  Prev: Library<87>,  Up: Python 3 5 0 alpha 1

1.18.87.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/issue20577

   (2) https://bugs.python.org/issue16893

   (3) https://bugs.python.org/issue3068

   (4) https://bugs.python.org/issue16233

   (5) https://bugs.python.org/issue4832

   (6) https://bugs.python.org/issue21986

   (7) https://bugs.python.org/issue17390

   (8) https://bugs.python.org/issue14105

   (9) https://bugs.python.org/issue17172

   (10) https://bugs.python.org/issue21765

   (11) https://bugs.python.org/issue21940

   (12) https://bugs.python.org/issue18592

   (13) https://bugs.python.org/issue21694

   (14) https://bugs.python.org/issue21686

   (15) https://bugs.python.org/issue12387

   (16) https://bugs.python.org/issue21695

   (17) https://bugs.python.org/issue18910

   (18) https://bugs.python.org/issue18292

   (19) https://bugs.python.org/issue18409

   (20) https://bugs.python.org/issue21477

   (21) https://bugs.python.org/issue18104

   (22) https://bugs.python.org/issue21139

   (23) https://www.python.org/dev/peps/pep-0008

   (24) https://bugs.python.org/issue21284

   (25) https://bugs.python.org/issue17654

   (26) https://bugs.python.org/issue23180


File: python.info,  Node: Build<56>,  Next: C API<38>,  Prev: IDLE<53>,  Up: Python 3 5 0 alpha 1

1.18.87.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 BerkelyDB 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/issue15506

   (2) https://bugs.python.org/issue22935

   (3) https://bugs.python.org/issue22592

   (4) https://bugs.python.org/issue22591

   (5) https://bugs.python.org/issue16537

   (6) https://bugs.python.org/issue22359

   (7) https://bugs.python.org/issue21958

   (8) https://bugs.python.org/issue18093

   (9) https://bugs.python.org/issue15759

   (10) https://bugs.python.org/issue21141

   (11) https://bugs.python.org/issue21037

   (12) https://bugs.python.org/issue19962

   (13) https://bugs.python.org/issue21285

   (14) https://bugs.python.org/issue15234

   (15) https://bugs.python.org/issue17861

   (16) https://bugs.python.org/issue20644

   (17) https://bugs.python.org/issue20022

   (18) https://bugs.python.org/issue15968

   (19) https://bugs.python.org/issue17095

   (20) https://bugs.python.org/issue21811

   (21) https://bugs.python.org/issue21166

   (22) https://bugs.python.org/issue18096

   (23) https://bugs.python.org/issue17219

   (24) https://bugs.python.org/issue22919

   (25) https://bugs.python.org/issue21236

   (26) https://bugs.python.org/issue17128


File: python.info,  Node: C API<38>,  Next: Documentation<53>,  Prev: Build<56>,  Up: Python 3 5 0 alpha 1

1.18.87.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():
     441, rename ‘_Py_wchar2char()’ to *note Py_EncodeLocale(): 442, 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/issue14203

   (2) https://bugs.python.org/issue22445

   (3) https://bugs.python.org/issue22079

   (4) https://bugs.python.org/issue22453

   (5) https://bugs.python.org/issue18395

   (6) https://bugs.python.org/issue21233

   (7) https://bugs.python.org/issue20942


File: python.info,  Node: Documentation<53>,  Next: Tests<54>,  Prev: C API<38>,  Up: Python 3 5 0 alpha 1

1.18.87.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/issue19548

   (2) https://bugs.python.org/issue22394

   (3) https://bugs.python.org/issue21514

   (4) https://bugs.python.org/issue21777

   (5) https://bugs.python.org/issue6916

   (6) https://bugs.python.org/issue17386

   (7) https://bugs.python.org/issue21312

   (8) https://bugs.python.org/issue21043

   (9) https://bugs.python.org/issue20765

   (10) https://bugs.python.org/issue19407

   (11) https://bugs.python.org/issue19697


File: python.info,  Node: Tests<54>,  Next: Tools/Demos<36>,  Prev: Documentation<53>,  Up: Python 3 5 0 alpha 1

1.18.87.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/issue18982

   (2) https://bugs.python.org/issue19548

   (3) https://bugs.python.org/issue22838

   (4) https://bugs.python.org/issue22173

   (5) https://bugs.python.org/issue16000

   (6) https://bugs.python.org/issue21456

   (7) https://bugs.python.org/issue20746

   (8) https://bugs.python.org/issue22060

   (9) https://bugs.python.org/issue22104

   (10) https://bugs.python.org/issue22111

   (11) https://bugs.python.org/issue22002

   (12) https://bugs.python.org/issue21976

   (13) https://bugs.python.org/issue21918

   (14) https://bugs.python.org/issue9554

   (15) https://bugs.python.org/issue20155

   (16) https://bugs.python.org/issue19493

   (17) https://bugs.python.org/issue18492

   (18) https://bugs.python.org/issue21634

   (19) https://bugs.python.org/issue21605

   (20) https://bugs.python.org/issue21493

   (21) https://bugs.python.org/issue19925

   (22) https://bugs.python.org/issue21522

   (23) https://bugs.python.org/issue17756

   (24) https://bugs.python.org/issue17752

   (25) https://bugs.python.org/issue18604

   (26) https://bugs.python.org/issue21275

   (27) https://bugs.python.org/issue21223

   (28) https://bugs.python.org/issue20635

   (29) https://bugs.python.org/issue20743

   (30) https://bugs.python.org/issue21097

   (31) https://bugs.python.org/issue21503

   (32) https://bugs.python.org/issue20939

   (33) https://bugs.python.org/issue20668

   (34) https://bugs.python.org/issue21093

   (35) https://bugs.python.org/issue22770

   (36) https://bugs.python.org/issue23211

   (37) https://bugs.python.org/issue23345


File: python.info,  Node: Tools/Demos<36>,  Next: Windows<51>,  Prev: Tests<54>,  Up: Python 3 5 0 alpha 1

1.18.87.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/issue22314

   (2) https://bugs.python.org/issue22615

   (3) https://bugs.python.org/issue20076

   (4) https://bugs.python.org/issue20079

   (5) https://bugs.python.org/issue22201

   (6) https://bugs.python.org/issue22120

   (7) https://bugs.python.org/issue18974

   (8) https://bugs.python.org/issue21906

   (9) https://bugs.python.org/issue21629

   (10) https://www.python.org/dev/peps/pep-0465

   (11) https://bugs.python.org/issue16047

   (12) https://bugs.python.org/issue11824

   (13) https://bugs.python.org/issue20535


File: python.info,  Node: Windows<51>,  Prev: Tools/Demos<36>,  Up: Python 3 5 0 alpha 1

1.18.87.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/issue23260

   (2) https://bugs.python.org/issue17896

   (3) https://bugs.python.org/issue17717

   (4) https://bugs.python.org/issue21907

   (5) https://bugs.python.org/issue22644

   (6) https://bugs.python.org/issue10747

   (7) https://bugs.python.org/issue22980


File: python.info,  Node: Python 教學,  Next: Python Setup and Usage,  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): 1200.。在 *note The Python Language Reference: 1201.
中，您可以學到 Python 語言更正規的定義。想用 C 或 C++ 寫延伸套件
(extensions) 的讀者，請閱讀 *note Extending and Embedding the Python
Interpreter: 1202. 和 *note Python / C API 參考手冊: 1203. 。此外，市面
上也能找到更深入的 Python 學習書。

這份教學中，我們不會介紹每一個功能，甚至，也不打算介紹完每一個常用功能。
取而代之，我們的重心將放在介紹 Python 中最值得一提的那些功能，幫助您了解
Python 語言的特色與風格。讀完教學後，您將有能力閱讀和撰寫 Python 模組與
程式，也做好進一步學習 *note Python 標準函式庫 (Standard Library): 1200.
中各類型的 Python 函式庫模組的準備。

*note Glossary: 1204. 頁面也值得細讀。

* Menu:

* 淺嘗滋味::
* 使用 Python 直譯器::
* 一個非正式的 Python 簡介::
* 深入了解流程控制::
* 資料結構::
* 模組::
* 輸入和輸出::
* 錯誤和例外::
* Classes::
* Python 標準函式庫概覽::
* Brief Tour of the Standard Library: Brief Tour of the Standard Library --- Part II. Part II
* 虛擬環境與套件::
* 現在可以來學習些什麼？::
* Interactive Input Editing and History Substitution::
* 浮點數運算：問題與限制::
* 附錄::


File: python.info,  Node: 淺嘗滋味,  Next: 使用 Python 直譯器,  Up: Python 教學

2.1 淺嘗滋味
============

如果你經常在電腦上工作，最終總能發現有些工作你會想要自動化。舉例來說，你
會想在很多文字檔案裡做相同的搜尋取代，或者是用個複雜的規則重新命名或整理
一群照片。也有可能你想寫個自己的小資料庫，一個專門的 GUI 應用程式，或一
個小遊戲。

如果你是一個職業軟體開發者，你可能要操作數個 C/C++/Java 程式庫，卻覺得平
常寫程式碼、編譯、測試、再編譯的流程太慢；有可能你正為了一個程式庫撰寫一
套測試集，但發現寫測試單調乏味；也有可能你正在開發一個能使用某一語言擴充
的程式，但並不想要為了這程式特別設計一個全新的擴充語言。

在上述的例子中，Python 正是你合適的語言。

也許你可以為了某些任務而寫個 Unix shell 腳本或者 Windows 批次檔來處理，
但 shell 腳本最適合於搬動檔案或更動文字內容，而不適於圖形應用程式或遊戲
。你可以為此寫個 C/C++/Java 程式，但僅僅是完成個草稿也需要很長的開發時間
。相較而言，Python 更易於使用，並能在 Windows、Mac OSX、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.8’ 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.8

能啟動 Python (1)。因為直譯器存放的目錄是個安裝選項，其他的目錄也是有可
能的；請洽談在地的 Python 達人或者系統管理員。（例如：
‘/usr/local/python’ 是個很常見的另類存放路徑。）

On Windows machines where you have installed Python from the *note
Microsoft Store: 120d, the ‘python3.8’ command will be available.  If
you have the *note py.exe launcher: 994. installed, you can use the ‘py’
command.  See *note Excursus; Setting environment variables: 120e. for
other ways to launch Python.

在主提示符輸入一個 end-of-file 字元（在 Unix 上為 ‘Control-D’；在
Windows 上為 ‘Control-Z’）會使得直譯器以零退出狀況 (zero exit status) 離
開。如果上述的做法沒有效，也可以輸入指令 ‘quit()’ 離開直譯器。

The interpreter’s line-editing features include interactive editing,
history substitution and code completion on systems that support the GNU
Readline(2) library.  Perhaps the quickest check to see whether command
line editing is supported is typing ‘Control-P’ to the first Python
prompt you get.  If it beeps, you have command line editing; see
Appendix *note Interactive Input Editing and History Substitution: 120f.
for an introduction to the keys.  If nothing appears to happen, or if
‘^P’ is echoed, command line editing isn’t available; you’ll only be
able to use backspace to remove characters from the current line.

這個直譯器使用起來像是 Unix shell：如果它被呼叫時連結至一個 tty 裝置，它
會互動式地讀取並執行指令；如果被呼叫時給定檔名為引數或者使用 stdin 傳入
檔案內容，它會將這個檔案視為`腳本'來閱讀。

另一個起動直譯器的方式為 ‘python -c command [arg] ...’，它會執行在
`command' 裡的指令（們），行為如同 shell 的 *note -c: 1210. 選項。因為
Python 的指令包含空白等 shell 用到的特殊字元，通常建議用單引號把
`command' 包起來。

有些 Python 模組使用上如腳本般一樣方便。透過 ‘python -m module [arg]
...’ 可以執行 `module' 模組的原始碼，就如同直接傳入那個模組的完整路徑一
樣的行為。

當要執行一個腳本檔時，有時候會希望在腳本結束時進入互動模式。此時可在執行
腳本的指令加入 *note -i: e24.。

所有指令可用的參數都詳記在*note Command line and environment: faf.。

* Menu:

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

   ---------- Footnotes ----------

   (1) (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: 1210. `command' 時， ‘sys.argv[0]’ 為 ‘'-c'’。
當使用 *note -m: 33c. `module' 時， ‘sys.argv[0]’ 為該模組存在的完整路徑
。其餘非 *note -c: 1210. `command' 或 *note -m: 33c. `module' 的選項不會
被 Python 直譯器吸收掉，而是留在 ‘sys.argv’ 變數中給後續的 command 或
module 使用。


File: python.info,  Node: 互動模式,  Prev: 傳遞引數,  Up: 啟動直譯器

2.2.1.2 互動模式
................

When commands are read from a tty, the interpreter is said to be in
`interactive mode'.  In this mode it prompts for the next command with
the `primary prompt', usually three greater-than signs (‘>>>’); for
continuation lines it prompts with the `secondary prompt', by default
three dots (‘...’).  The interpreter prints a welcome message stating
its version number and a copyright notice before printing the first
prompt:

     $ python3.8
     Python 3.8 (default, Sep 16 2015, 09:25:04)
     [GCC 4.8.2] on linux
     Type "help", "copyright", "credits" or "license" for more information.
     >>>

接續多行的情況出現在需要多行才能建立完整指令時。舉例來說，像是 *note if:
dec. 敘述：

     >>> the_world_is_flat = True
     >>> if the_world_is_flat:
     ...     print("Be careful not to fall off!")
     ...
     Be careful not to fall off!

更多有關互動模式的使用，請見*note 互動模式: 1214.。


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，
並且需要能顯示檔案中所有字元的字型。

To declare an encoding other than the default one, a special comment
line should be added as the `first' line of the file.  The syntax is as
follows:

     # -*- coding: encoding -*-

where `encoding' is one of the valid *note codecs: 1c. supported by
Python.

For example, to declare that Windows-1252 encoding is to be used, the
first line of your source code file should be:

     # -*- coding: cp1252 -*-

One exception to the `first line' rule is when the source code starts
with a *note UNIX "shebang" line: 1219.  In this case, the encoding
declaration should be added as the second line of the file.  For
example:

     #!/usr/bin/env python3
     # -*- coding: cp1252 -*-

註解
....


File: python.info,  Node: 一個非正式的 Python 簡介,  Next: 深入了解流程控制,  Prev: 使用 Python 直譯器,  Up: Python 教學

2.3 一個非正式的 Python 簡介
============================

在下面的例子中，輸入與輸出的區別在於有無提示符（prompt，*note >>>: 121d.
和 *note ...: 121e.）：如果要重做範例，你必須在提示符出現的時候，輸入提
示符後方的所有內容；那些非提示符開始的文字行是直譯器的輸出。注意到在範例
中，若出現單行只有次提示符時，代表該行你必須直接換行；這被使用在多行指令
結束輸入時。

在本手冊中的許多範例中，即便他們為互動式地輸入，仍然包含註解。Python 中
的註解 (comments) 由 hash 字元 ‘#’ 開始一直到該行結束。註解可以從該行之
首、空白後、或程式碼之後開始，但不會出現在字串之中。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.
* 字串 (String): 字串 String.
* List（串列）::


File: python.info,  Node: 數字 Number,  Next: 字串 String,  Up: 把 Python 當作計算機使用

2.3.1.1 數字 (Number)
.....................

直譯器如同一台簡單的計算機：你可以輸入一個 expression（運算式），它會寫
出該式的值。Expression 的語法很使用：運算子 ‘+’、‘-’、‘*’ 和 ‘/’ 的行為
如同大多數的程式語言（例如：Pascal 或 C）；括號 ‘()’ 可以用來分群。例如
：

     >>> 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: 185. 型態，數字有小數點部份的
（即 ‘5.0’、‘1.6’）為 *note float: 188. 型態。我們將在之後的教學中看到更
多數字相關的型態。

除法 (‘/’) 永遠回傳一個 float。如果要做 *note floor division: 1223. 並拿
到整數的結果（即去除所有小數點的部份），你可以使用 ‘//’ 運算子；計算餘數
可以使用 ‘%’：

     >>> 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  # result * 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: 185. 和 *note float: 188.，Python 還支援了其他的數字型態
，包含 *note Decimal: 189. 和 *note Fraction: 186.。Python 亦內建支援
*note 複數 (complex numbers): 1224.，並使用 ‘j’ 和 ‘J’ 後綴來指定虛數的
部份（即 ‘3+5j’）。

   ---------- Footnotes ----------

   (1) (1) 因為 ‘**’ 擁有較 ‘-’ 高的優先次序，‘-3**2’ 會被解釋為
‘-(3**2)’ 並得到 ‘-9’。如果要避免這樣的優先順序以得到 ‘9’，你可以使用
‘(-3)**2’。


File: python.info,  Node: 字串 String,  Next: List（串列）,  Prev: 數字 Number,  Up: 把 Python 當作計算機使用

2.3.1.2 字串 (String)
.....................

除了數字之外，Python 也可以操作字串，而表達字串有數種方式。它們可以用包
含在單引號 (‘'...'’) 或雙引號 (‘"..."’) 之中，兩者會得到相同的結果(1)。
使用 ‘\’ 跳脫出現於字串中的引號：

     >>> 'spam eggs'  # single quotes
     'spam eggs'
     >>> '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.'

在互動式的直譯器中，輸出的字串會被引號包圍且特殊符號會使用反斜線 (‘\’) 跳
脫。雖然這有時會讓它看起來跟輸入的字串不相同（包圍用的引號可能會改變），
輸入和輸出兩字串實為相同。一般來說，字串包含單引號而沒有雙引號時，會使用
雙引號包圍字串。函式 *note print(): 88b. 會產生更易讀的輸出，它會去除掉
包圍的引號，並且直接印出被跳脫的字元和特殊字元：

     >>> '"Isn\'t," they said.'
     '"Isn\'t," they said.'
     >>> print('"Isn\'t," they said.')
     "Isn't," they said.
     >>> s = 'First line.\nSecond line.'  # \n means newline
     >>> s  # without print(), \n is included in the output
     'First line.\nSecond line.'
     >>> print(s)  # with print(), \n produces a 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

字串值可以跨越數行。其中一方式是使用三個重覆引號：‘"""..."""’ 或
‘'''...'''’。此時換行會被自動加入字串值中，但也可以在換行前加入 ‘\’ 來取
消這個行為。在以下的例子中：

     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'

注意到起點永遠被包含，而結尾永遠不被包含。這確保了 ‘s[:i] + s[i:]’ 永遠
等於 ‘s’：

     >>> word[:2] + word[2:]
     'Python'
     >>> word[:4] + word[4:]
     'Python'

切片索引 (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'

這裡有個簡單記住 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: 1227.。因此，嘗試對字串
中某個索引位置賦值會產生錯誤：

     >>> 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(): 151. 回傳一個字串的長度：

     >>> s = 'supercalifragilisticexpialidocious'
     >>> len(s)
     34

也參考
......

*note Text Sequence Type — str: 1228.

     字串是 `sequence 型別'的範例之一，並支援該型別常用的操作。

*note String Methods: 1229.

     字串支援非常多種基本轉換和搜尋的方法。

*note Formatted string literals: 15d.

     包含有表示式的字串值。

*note Format String Syntax: d1f.

     關於透過 *note str.format(): 4df. 字串格式化 (string formatting) 的
     資訊。

*note printf-style String Formatting: 122a.

     在字串為 ‘%’ 的左運算元時，將觸發舊的字串格式化操作，更多的細節在本
     連結中介紹。

   ---------- Footnotes ----------

   (1) (2) 不像其他語言，特殊符號如 ‘\n’ 在單 (‘'...'’) 和雙 (‘"..."’) 括
號中有相同的意思。兩種刮號的唯一差別，在於使用單刮號時，不需要跳脫
(escape) ‘"’（但需要跳脫 ‘\'’），反之亦同。


File: python.info,  Node: List（串列）,  Prev: 字串 String,  Up: 把 Python 當作計算機使用

2.3.1.3 List（串列）
....................

Python 理解數種複合型資料型別，用來組合不同的數值。當中最多樣變化的型別
為 `list'，可以寫成一系列以逗號分隔的數值（稱之元素，即 item），包含在方
括號之中。List 可以包合不同型別的元素，但通常這些元素會有相同的型別：

     >>> squares = [1, 4, 9, 16, 25]
     >>> squares
     [1, 4, 9, 16, 25]

Like strings (and all other built-in *note sequence: 122d. types), lists
can be indexed and sliced:

     >>> squares[0]  # indexing returns the item
     1
     >>> squares[-1]
     25
     >>> squares[-3:]  # slicing returns a new list
     [9, 16, 25]

All slice operations return a new list containing the requested
elements.  This means that the following slice returns a *note shallow
copy: 122e. of the list:

     >>> squares[:]
     [1, 4, 9, 16, 25]

List 對支援如接合 (concatenation) 等操作：

     >>> squares + [36, 49, 64, 81, 100]
     [1, 4, 9, 16, 25, 36, 49, 64, 81, 100]

不同於字串是 *note immutable: 1227.，list 是 *note mutable: 122f. 型別，
即改變 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 的最後加入新元素，透過使用 ‘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]

也可以對 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(): 151. 亦可以作用在 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: 1232. 迴圈只要它的條件為真（此範例：‘a < 10’），將會一
     直重覆執行。在 Python 中如同 C 語言，任何非零的整數值為真 (true)；
     零為假 (false)。條件可以是字串、list、甚至是任何序列型別；任何非零
     長度的序列為真，空的序列即為假。本例子使用的條件是個簡單的比較。標
     準的比較運算子 (comparison operators) 使用如同 C 語言一樣的符號：
     ‘<’（小於）、‘>’（大於）、‘==’（等於）、‘<=’（小於等於）、‘>=’（大
     於等於）以及 ‘!=’（不等於）。

   * 迴圈的主體會`縮排'：縮排在 Python 中用來關連一群陳述式。在互動式提
     示符中，你必須在迴圈內的每一行一開始鍵入 tab 或者（數個）空白來維持
     縮排。實務上，你會先在文字編輯器中準備好比較複雜的輸入；多數編輯器
     都有自動縮排的功能。當一個複合陳述式以互動地方式輸入，必須在結束時
     多加一行空行來代表結束（因為語法解析器無法判斷你何時輸入複合陳述的
     最後一行）。注意在一個縮排段落內的縮排方式與數量必須維持一致。

   * *note print(): 88b. 函式印出它接收到引數（們）的值。不同於先前僅我
     們寫下想要的運算（像是先前的計算機範例），它可以處理複數個引數、浮
     點數數值和字串。印出的字串將不帶有引號，並且不同項目間會插入一個空
     白，因此可以讓你容易格式化輸出，例如：

          >>> 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 深入了解流程控制
====================

Besides the *note while: 1232. statement just introduced, Python uses
the usual flow control statements known from other languages, with some
twists.

* Menu:

* if Statements::
* for Statements::
* range() 函式: range 函式.
* break and continue Statements, and else Clauses on Loops: break and continue Statements and else Clauses on Loops.
* pass Statements::
* 定義函式 (function): 定義函式 function.
* More on Defining Functions::
* Intermezzo; Coding Style: Intermezzo Coding Style.


File: python.info,  Node: if Statements,  Next: for Statements,  Up: 深入了解流程控制

2.4.1 ‘if’ Statements
---------------------

或許最常見的陳述式種類就是 *note if: dec. 了。舉例來說：

     >>> 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

There can be zero or more *note elif: 1238. parts, and the *note else:
1239. part is optional.  The keyword ’‘elif’’ is short for ’else if’,
and is useful to avoid excessive indentation.  An ‘if’ ...  ‘elif’ ...
‘elif’ ...  sequence is a substitute for the ‘switch’ or ‘case’
statements found in other languages.


File: python.info,  Node: for Statements,  Next: range 函式,  Prev: if Statements,  Up: 深入了解流程控制

2.4.2 ‘for’ Statements
----------------------

The *note for: c35. statement in Python differs a bit from what you may
be used to in C or Pascal.  Rather than always iterating over an
arithmetic progression of numbers (like in Pascal), or giving the user
the ability to define both the iteration step and halting condition (as
C), Python’s ‘for’ statement iterates over the items of any sequence (a
list or a string), in the order that they appear in the sequence.  For
example (no pun intended):

     >>> # Measure some strings:
     ... words = ['cat', 'window', 'defenestrate']
     >>> for w in words:
     ...     print(w, len(w))
     ...
     cat 3
     window 6
     defenestrate 12

Code that modifies a collection while iterating over that same
collection can be tricky to get right.  Instead, it is usually more
straight-forward to loop over a copy of the collection or to create a
new collection:

     # 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 and continue Statements and else Clauses on Loops,  Prev: for Statements,  Up: 深入了解流程控制

2.4.3 ‘range()’ 函式
--------------------

如果你需要疊代一個數列的話，使用內建 *note range(): 9c3. 函式就很方便。
它可以生成一等差級數：

     >>> for i in range(5):
     ...     print(i)
     ...
     0
     1
     2
     3
     4

給定的結束值永遠不會出現在生成的序列中；‘range(10)’ 生成的 10 個數值，即
對應存取一個長度為 10 的序列內每一個元素的索引值。也可以讓 range 從其他
數值計數，或者給定不同的級距（甚至為負；有時稱之為 step）：

     range(5, 10)
        5, 6, 7, 8, 9

     range(0, 10, 3)
        0, 3, 6, 9

     range(-10, -100, -30)
       -10, -40, -70

欲疊代一個序列的索引值，你可以搭配使用 *note range(): 9c3. 和 *note
len(): 151. 如下：

     >>> 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(): de8. 函式將更為方便，詳見
*note 迴圈技巧: 123e.。

如果直接印出一個 range 則會出現奇怪的輸出：

     >>> print(range(10))
     range(0, 10)

在很多情況下，由 *note range(): 9c3. 回傳的物件的行為如同一個 list，但實
際上它並不是。它是一個物件在你疊代時會回傳想要的序列的連續元素，並不會真
正建出這個序列的 list，以節省空間。

We say such an object is *note iterable: bb1, that is, suitable as a
target for functions and constructs that expect something from which
they can obtain successive items until the supply is exhausted.  We have
seen that the *note for: c35. statement is such a construct, while an
example of a function that takes an iterable is *note sum(): 1e6.:

     >>> sum(range(4))  # 0 + 1 + 2 + 3
     6

Later we will see more functions that return iterables and take
iterables as arguments.  Lastly, maybe you are curious about how to get
a list from a range.  Here is the solution:

     >>> list(range(4))
     [0, 1, 2, 3]

In chapter *note 資料結構: 123f, we will discuss in more detail about
*note list(): 263.


File: python.info,  Node: break and continue Statements and else Clauses on Loops,  Next: pass Statements,  Prev: range 函式,  Up: 深入了解流程控制

2.4.4 ‘break’ and ‘continue’ Statements, and ‘else’ Clauses on Loops
--------------------------------------------------------------------

*note break: 2dc. 陳述，如同 C 語言，終止包含其最內部的 *note for: c35.
或 *note while: 1232. 迴圈。

Loop statements may have an ‘else’ clause; it is executed when the loop
terminates through exhaustion of the iterable (with *note for: c35.) or
when the condition becomes false (with *note while: 1232.), but not when
the loop is terminated by a *note break: 2dc. statement.  This is
exemplified by the following loop, which searches for prime numbers:

     >>> 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: c35. 迴圈
，`並非' *note if: dec. 陳述。）

When used with a loop, the ‘else’ clause has more in common with the
‘else’ clause of a *note try: d77. statement than it does with that of
*note if: dec. statements: a *note try: d77. statement’s ‘else’ clause
runs when no exception occurs, and a loop’s ‘else’ clause runs when no
‘break’ occurs.  For more on the ‘try’ statement and exceptions, see
*note 處理例外: 1242.

*note continue: 182. 陳述，亦承襲於 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 Statements,  Next: 定義函式 function,  Prev: break and continue Statements and else Clauses on Loops,  Up: 深入了解流程控制

2.4.5 ‘pass’ Statements
-----------------------

*note pass: 1245. 陳述不執行任何動作。它用在語法上需要一個陳述但不需要執
行任何動作的時候。例如：

     >>> while True:
     ...     pass  # Busy-wait for keyboard interrupt (Ctrl+C)
     ...

這經常用於定義一個最簡單的類別：

     >>> class MyEmptyClass:
     ...     pass
     ...

Another place *note pass: 1245. can be used is as a place-holder for a
function or conditional body when you are working on new code, allowing
you to keep thinking at a more abstract level.  The ‘pass’ is silently
ignored:

     >>> def initlog(*args):
     ...     pass   # Remember to implement this!
     ...


File: python.info,  Node: 定義函式 function,  Next: More on Defining Functions,  Prev: pass Statements,  Up: 深入了解流程控制

2.4.6 定義函式 (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: dc3. 帶入一個函式的`定義'。它之後必須連著該函式的名稱
和置於括號之中的參數。自下一行起，所有縮排的陳述成為該函式的主體。

一個函式的第一個陳述可以是一個字串值；此情況該字串值被視為該函式的說明文
件字串，即 `docstring'。（關於 docstring 的細節請參見*note 說明文件字串:
1248.段落。）有些工具可以使用 docstring 來自動產生線上或可列印的文件，或
讓使用者能自由地自原始碼中瀏覽文件。在原始碼中加入 docstring 是個好慣例
，應該養成這樣的習慣。

The `execution' of a function introduces a new symbol table used for the
local variables of the function.  More precisely, all variable
assignments in a function store the value in the local symbol table;
whereas variable references first look in the local symbol table, then
in the local symbol tables of enclosing functions, then in the global
symbol table, and finally in the table of built-in names.  Thus, global
variables and variables of enclosing functions cannot be directly
assigned a value within a function (unless, for global variables, named
in a *note global: 1249. statement, or, for variables of enclosing
functions, named in a *note nonlocal: c44. statement), although they may
be referenced.

The actual parameters (arguments) to a function call are introduced in
the local symbol table of the called function when it is called; thus,
arguments are passed using `call by value' (where the `value' is always
an object `reference', not the value of the object).  (1) When a
function calls another function, or calls itself recursively, a new
local symbol table is created for that call.

A function definition associates the function name with the function
object in the current symbol table.  The interpreter recognizes the
object pointed to by that name as a user-defined function.  Other names
can also point to that same function object and can also be used to
access the 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: 191. 陳述，它亦有一個固定的回傳值。這個值為 ‘None’（它是一個內建
名稱）。在直譯器中單獨使用 ‘None’ 時，通常不會被顯示。你可以使用 *note
print(): 88b. 來看到它：

     >>> 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 特性：

   * The *note return: 191. statement returns with a value from a
     function.  ‘return’ without an expression argument returns ‘None’.
     Falling off the end of a function also returns ‘None’.

   * ‘result.append(a)’ 陳述呼叫了一個 list 物件的 ‘result’ `method（方
     法）'。method 為「屬於」一個物件的函式，命名規則為
     ‘obj.methodname’，其中 ‘obj’ 為某個物件（亦可為一表達式），而
     ‘methodname’ 為該 method 的名稱，並由該物件的型別所定義。不同的型別
     代表不同的 method。不同型別的 method 可以擁有一樣的名稱而不會讓
     Python 混淆。（你可以使用 `class' 定義自己的物件型別和 method，見
     *note Classes: 124a.）這裡 ‘append()’ method 定義在 list 物件中；它
     會加入一個新的元素在該 list 的末端。這個例子等同於 ‘result = result
     + [a]’，但更有效率。

   ---------- Footnotes ----------

   (1) (1) Actually, `call by object reference' would be a better
description, since if a mutable object is passed, the caller will see
any changes the callee makes to it (items inserted into a list).


File: python.info,  Node: More on Defining Functions,  Next: Intermezzo Coding Style,  Prev: 定義函式 function,  Up: 深入了解流程控制

2.4.7 More on Defining Functions
--------------------------------

It is also possible to define functions with a variable number of
arguments.  There are three forms, which can be combined.

* Menu:

* Default Argument Values::
* Keyword Arguments::
* Special parameters::
* Arbitrary Argument Lists::
* Unpacking Argument Lists::
* Lambda Expressions::
* 說明文件字串::
* Function Annotations::


File: python.info,  Node: Default Argument Values,  Next: Keyword Arguments,  Up: More on Defining Functions

2.4.7.1 Default Argument Values
...............................

The most useful form is to specify a default value for one or more
arguments.  This creates a function that can be called with fewer
arguments than it is defined to allow.  For example:

     def ask_ok(prompt, retries=4, reminder='Please try again!'):
         while True:
             ok = input(prompt)
             if ok in ('y', 'ye', 'yes'):
                 return True
             if ok in ('n', 'no', 'nop', 'nope'):
                 return False
             retries = retries - 1
             if retries < 0:
                 raise ValueError('invalid user response')
             print(reminder)

This function can be called in several ways:

   * giving only the mandatory argument: ‘ask_ok('Do you really want to
     quit?')’

   * giving one of the optional arguments: ‘ask_ok('OK to overwrite the
     file?', 2)’

   * or even giving all arguments: ‘ask_ok('OK to overwrite the file?',
     2, 'Come on, only yes or no!')’

This example also introduces the *note in: 7a8. keyword.  This tests
whether or not a sequence contains a certain value.

The default values are evaluated at the point of function definition in
the `defining' scope, so that

     i = 5

     def f(arg=i):
         print(arg)

     i = 6
     f()

will print ‘5’.

`Important warning:' The default value is evaluated only once.  This
makes a difference when the default is a mutable object such as a list,
dictionary, or instances of most classes.  For example, the following
function accumulates the arguments passed to it on subsequent calls:

     def f(a, L=[]):
         L.append(a)
         return L

     print(f(1))
     print(f(2))
     print(f(3))

This will print

     [1]
     [1, 2]
     [1, 2, 3]

If you don’t want the default to be shared between subsequent calls, you
can write the function like this instead:

     def f(a, L=None):
         if L is None:
             L = []
         L.append(a)
         return L


File: python.info,  Node: Keyword Arguments,  Next: Special parameters,  Prev: Default Argument Values,  Up: More on Defining Functions

2.4.7.2 Keyword Arguments
.........................

Functions can also be called using *note keyword arguments: 5c9. of the
form ‘kwarg=value’.  For instance, the following function:

     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, "!")

accepts one required argument (‘voltage’) and three optional arguments
(‘state’, ‘action’, and ‘type’).  This function can be called in any of
the following ways:

     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

but all the following calls would be invalid:

     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

In a function call, keyword arguments must follow positional arguments.
All the keyword arguments passed must match one of the arguments
accepted by the function (e.g.  ‘actor’ is not a valid argument for the
‘parrot’ function), and their order is not important.  This also
includes non-optional arguments (e.g.  ‘parrot(voltage=1000)’ is valid
too).  No argument may receive a value more than once.  Here’s an
example that fails due to this restriction:

     >>> 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 keyword argument 'a'

When a final formal parameter of the form ‘**name’ is present, it
receives a dictionary (see *note Mapping Types — dict: 301.) containing
all keyword arguments except for those corresponding to a formal
parameter.  This may be combined with a formal parameter of the form
‘*name’ (described in the next subsection) which receives a *note tuple:
1251. containing the positional arguments beyond the formal parameter
list.  (‘*name’ must occur before ‘**name’.)  For example, if we define
a function like this:

     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])

It could be called like this:

     cheeseshop("Limburger", "It's very runny, sir.",
                "It's really very, VERY runny, sir.",
                shopkeeper="Michael Palin",
                client="John Cleese",
                sketch="Cheese Shop Sketch")

and of course it would print:

     -- 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

Note that the order in which the keyword arguments are printed is
guaranteed to match the order in which they were provided in the
function call.


File: python.info,  Node: Special parameters,  Next: Arbitrary Argument Lists,  Prev: Keyword Arguments,  Up: More on Defining Functions

2.4.7.3 Special parameters
..........................

By default, arguments may be passed to a Python function either by
position or explicitly by keyword.  For readability and performance, it
makes sense to restrict the way arguments can be passed so that a
developer need only look at the function definition to determine if
items are passed by position, by position or keyword, or by keyword.

A function definition may look like:

     def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2):
           -----------    ----------     ----------
             |             |                  |
             |        Positional or keyword   |
             |                                - Keyword only
              -- Positional only

where ‘/’ and ‘*’ are optional.  If used, these symbols indicate the
kind of parameter by how the arguments may be passed to the function:
positional-only, positional-or-keyword, and keyword-only.  Keyword
parameters are also referred to as named parameters.

* Menu:

* Positional-or-Keyword Arguments::
* Positional-Only Parameters::
* Keyword-Only Arguments::
* Function Examples::
* Recap::


File: python.info,  Node: Positional-or-Keyword Arguments,  Next: Positional-Only Parameters,  Up: Special parameters

2.4.7.4 Positional-or-Keyword Arguments
.......................................

If ‘/’ and ‘*’ are not present in the function definition, arguments may
be passed to a function by position or by keyword.


File: python.info,  Node: Positional-Only Parameters,  Next: Keyword-Only Arguments,  Prev: Positional-or-Keyword Arguments,  Up: Special parameters

2.4.7.5 Positional-Only Parameters
..................................

Looking at this in a bit more detail, it is possible to mark certain
parameters as `positional-only'.  If `positional-only', the parameters’
order matters, and the parameters cannot be passed by keyword.
Positional-only parameters are placed before a ‘/’ (forward-slash).  The
‘/’ is used to logically separate the positional-only parameters from
the rest of the parameters.  If there is no ‘/’ in the function
definition, there are no positional-only parameters.

Parameters following the ‘/’ may be `positional-or-keyword' or
`keyword-only'.


File: python.info,  Node: Keyword-Only Arguments,  Next: Function Examples,  Prev: Positional-Only Parameters,  Up: Special parameters

2.4.7.6 Keyword-Only Arguments
..............................

To mark parameters as `keyword-only', indicating the parameters must be
passed by keyword argument, place an ‘*’ in the arguments list just
before the first `keyword-only' parameter.


File: python.info,  Node: Function Examples,  Next: Recap,  Prev: Keyword-Only Arguments,  Up: Special parameters

2.4.7.7 Function Examples
.........................

Consider the following example function definitions paying close
attention to the markers ‘/’ and ‘*’:

     >>> 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)

The first function definition, ‘standard_arg’, the most familiar form,
places no restrictions on the calling convention and arguments may be
passed by position or keyword:

     >>> standard_arg(2)
     2

     >>> standard_arg(arg=2)
     2

The second function ‘pos_only_arg’ is restricted to only use positional
parameters as there is a ‘/’ in the function definition:

     >>> 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 an unexpected keyword argument 'arg'

The third function ‘kwd_only_args’ only allows keyword arguments as
indicated by a ‘*’ in the function definition:

     >>> 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

And the last uses all three calling conventions in the same function
definition:

     >>> 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 an unexpected keyword argument 'pos_only'

Finally, consider this function definition which has a potential
collision between the positional argument ‘name’ and ‘**kwds’ which has
‘name’ as a key:

     def foo(name, **kwds):
         return 'name' in kwds

There is no possible call that will make it return ‘True’ as the keyword
‘'name'’ will always bind to the first parameter.  For example:

     >>> foo(1, **{'name': 2})
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: foo() got multiple values for argument 'name'
     >>>

But using ‘/’ (positional only arguments), it is possible since it
allows ‘name’ as a positional argument and ‘'name'’ as a key in the
keyword arguments:

     def foo(name, /, **kwds):
         return 'name' in kwds
     >>> foo(1, **{'name': 2})
     True

In other words, the names of positional-only parameters can be used in
‘**kwds’ without ambiguity.


File: python.info,  Node: Recap,  Prev: Function Examples,  Up: Special parameters

2.4.7.8 Recap
.............

The use case will determine which parameters to use in the function
definition:

     def f(pos1, pos2, /, pos_or_kwd, *, kwd1, kwd2):

As guidance:

   * Use positional-only if you want the name of the parameters to not
     be available to the user.  This is useful when parameter names have
     no real meaning, if you want to enforce the order of the arguments
     when the function is called or if you need to take some positional
     parameters and arbitrary keywords.

   * Use keyword-only when names have meaning and the function
     definition is more understandable by being explicit with names or
     you want to prevent users relying on the position of the argument
     being passed.

   * For an API, use positional-only to prevent breaking API changes if
     the parameter’s name is modified in the future.


File: python.info,  Node: Arbitrary Argument Lists,  Next: Unpacking Argument Lists,  Prev: Special parameters,  Up: More on Defining Functions

2.4.7.9 Arbitrary Argument Lists
................................

Finally, the least frequently used option is to specify that a function
can be called with an arbitrary number of arguments.  These arguments
will be wrapped up in a tuple (see *note Tuples 和序列 (Sequences):
1251.).  Before the variable number of arguments, zero or more normal
arguments may occur.

     def write_multiple_items(file, separator, *args):
         file.write(separator.join(args))

Normally, these ‘variadic’ arguments will be last in the list of formal
parameters, because they scoop up all remaining input arguments that are
passed to the function.  Any formal parameters which occur after the
‘*args’ parameter are ’keyword-only’ arguments, meaning that they can
only be used as keywords rather than positional arguments.

     >>> 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 Expressions,  Prev: Arbitrary Argument Lists,  Up: More on Defining Functions

2.4.7.10 Unpacking Argument Lists
.................................

The reverse situation occurs when the arguments are already in a list or
tuple but need to be unpacked for a function call requiring separate
positional arguments.  For instance, the built-in *note range(): 9c3.
function expects separate `start' and `stop' arguments.  If they are not
available separately, write the function call with the ‘*’-operator to
unpack the arguments out of a list or 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]

In the same fashion, dictionaries can deliver keyword arguments with the
‘**’-operator:

     >>> 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 Expressions,  Next: 說明文件字串,  Prev: Unpacking Argument Lists,  Up: More on Defining Functions

2.4.7.11 Lambda Expressions
...........................

Small anonymous functions can be created with the *note lambda: c34.
keyword.  This function returns the sum of its two arguments: ‘lambda a,
b: a+b’.  Lambda functions can be used wherever function objects are
required.  They are syntactically restricted to a single expression.
Semantically, they are just syntactic sugar for a normal function
definition.  Like nested function definitions, lambda functions can
reference variables from the containing scope:

     >>> def make_incrementor(n):
     ...     return lambda x: x + n
     ...
     >>> f = make_incrementor(42)
     >>> f(0)
     42
     >>> f(1)
     43

The above example uses a lambda expression to return a function.
Another use is to pass a small function as an argument:

     >>> 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: 說明文件字串,  Next: Function Annotations,  Prev: Lambda Expressions,  Up: More on Defining Functions

2.4.7.12 說明文件字串
.....................

Here are some conventions about the content and formatting of
documentation strings.

The first line should always be a short, concise summary of the object’s
purpose.  For brevity, it should not explicitly state the object’s name
or type, since these are available by other means (except if the name
happens to be a verb describing a function’s operation).  This line
should begin with a capital letter and end with a period.

If there are more lines in the documentation string, the second line
should be blank, visually separating the summary from the rest of the
description.  The following lines should be one or more paragraphs
describing the object’s calling conventions, its side effects, etc.

The Python parser does not strip indentation from multi-line string
literals in Python, so tools that process documentation have to strip
indentation if desired.  This is done using the following convention.
The first non-blank line `after' the first line of the string determines
the amount of indentation for the entire documentation string.  (We
can’t use the first line since it is generally adjacent to the string’s
opening quotes so its indentation is not apparent in the string
literal.)  Whitespace "equivalent" to this indentation is then stripped
from the start of all lines of the string.  Lines that are indented less
should not occur, but if they occur all their leading whitespace should
be stripped.  Equivalence of whitespace should be tested after expansion
of tabs (to 8 spaces, normally).

Here is an example of a multi-line docstring:

     >>> 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: 說明文件字串,  Up: More on Defining Functions

2.4.7.13 Function Annotations
.............................

*note Function annotations: 1261. are completely optional metadata
information about the types used by user-defined functions (see PEP
3107(1) and PEP 484(2) for more information).

*note Annotations: 1262. are stored in the ‘__annotations__’ attribute
of the function as a dictionary and have no effect on any other part of
the function.  Parameter annotations are defined by a colon after the
parameter name, followed by an expression evaluating to the value of the
annotation.  Return annotations are defined by a literal ‘->’, followed
by an expression, between the parameter list and the colon denoting the
end of the *note def: dc3. statement.  The following example has a
required argument, an optional argument, and the return value annotated:

     >>> 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://www.python.org/dev/peps/pep-3107

   (2) https://www.python.org/dev/peps/pep-0484


File: python.info,  Node: Intermezzo Coding Style,  Prev: More on Defining Functions,  Up: 深入了解流程控制

2.4.8 Intermezzo: Coding Style
------------------------------

Now that you are about to write longer, more complex pieces of Python,
it is a good time to talk about `coding style'.  Most languages can be
written (or more concise, `formatted') in different styles; some are
more readable than others.  Making it easy for others to read your code
is always a good idea, and adopting a nice coding style helps
tremendously for that.

For Python, PEP 8(1) has emerged as the style guide that most projects
adhere to; it promotes a very readable and eye-pleasing coding style.
Every Python developer should read it at some point; here are the most
important points extracted for you:

   * Use 4-space indentation, and no tabs.

     4 spaces are a good compromise between small indentation (allows
     greater nesting depth) and large indentation (easier to read).
     Tabs introduce confusion, and are best left out.

   * Wrap lines so that they don’t exceed 79 characters.

     This helps users with small displays and makes it possible to have
     several code files side-by-side on larger displays.

   * Use blank lines to separate functions and classes, and larger
     blocks of code inside functions.

   * When possible, put comments on a line of their own.

   * Use docstrings.

   * Use spaces around operators and after commas, but not directly
     inside bracketing constructs: ‘a = f(1, 2) + g(3, 4)’.

   * Name your classes and functions consistently; the convention is to
     use ‘UpperCamelCase’ for classes and ‘lowercase_with_underscores’
     for functions and methods.  Always use ‘self’ as the name for the
     first method argument (see *note A First Look at Classes: 1265. for
     more on classes and methods).

   * Don’t use fancy encodings if your code is meant to be used in
     international environments.  Python’s default, UTF-8, or even plain
     ASCII work best in any case.

   * Likewise, don’t use non-ASCII characters in identifiers if there is
     only the slightest chance people speaking a different language will
     read or maintain the code.

註解
....

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0008


File: python.info,  Node: 資料結構,  Next: 模組,  Prev: 深入了解流程控制,  Up: Python 教學

2.5 資料結構
============

這個章節將會更深入的介紹一些你已經學過的東西的細節上，並且加入一些你還沒
有接觸過的部分。

* Menu:

* 進一步了解 List（串列）::
* The del statement::
* Tuples 和序列 (Sequences): Tuples 和序列 Sequences.
* 集合 (Sets): 集合 Sets.
* 字典（Dictionary）::
* 迴圈技巧::
* 更多條件式主題::
* 序列和其他資料結構之比較::


File: python.info,  Node: 進一步了解 List（串列）,  Next: The del statement,  Up: 資料結構

2.5.1 進一步了解 List（串列）
-----------------------------

List（串列）這個資料型態，具有更多操作的方法。下面條列了所有關於 list 的
物件方法：

 -- 成員函式: 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)

     Remove the first item from the list whose value is equal to `x'.
     It raises a *note ValueError: 1fc. if there is no such item.

 -- 成員函式: list.pop ([i])

     移除 list 中給定位置的項目，並回傳它。如果沒有指定位置， ‘a.pop()’
     將會移除 list 中最後的項目並回傳它。（在 `i' 周圍的方括號代表這個參
     數是選用的，並不代表你應該在該位置輸入方括號。你將會常常在 Python 函
     式庫參考指南中看見這個表示法）

 -- 成員函式: list.clear ()

     刪除 list 中所有項目。這等同於 ‘del a[:]’ 。

 -- 成員函式: list.index (x[, start[, end]])

     回傳 list 中第一個值等於 `x' 的項目之索引值（從零開始的索引）。若
     list 中無此項目，則丟出 *note ValueError: 1fc. 錯誤。

     引數 `start' 和 `end' 的定義跟在 slice 表示法中相同，搜尋的動作被這
     兩個引數限定在 list 中特定的子序列。但要注意的是，回傳的索引值是從
     list 的開頭開始算，而不是從 `start' 開始算。

 -- 成員函式: list.count (x)

     回傳數值為 `x' 在 list 中所出現的次數。

 -- 成員函式: list.sort (*, key=None, reverse=False)

     將 list 中的項目排序。（有參數可以使用來進行客製化的排序，請參考
     *note sorted(): 449. 部分的解釋）

 -- 成員函式: 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 a 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 中
所有可變資料結構的設計法則。

Another thing you might notice is that not all data can be sorted or
compared.  For instance, ‘[None, 'hello', 10]’ doesn’t sort because
integers can’t be compared to strings and `None' can’t be compared to
other types.  Also, there are some types that don’t have a defined
ordering relation.  For example, ‘3+4j < 5+7j’ isn’t a valid comparison.

* Menu:

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

   ---------- Footnotes ----------

   (1) (1) 其他語言可能可以回傳可變的物件並允許方法串連，例如
‘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: 536. ，其被設計成能快
速的從頭尾兩端加入和取出。例如：

     >>> 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。常見的
應用是基於一個 list 或 iterable（可列舉物件），將每一個元素經過某個運算
的結果串接起來成為一個新的 list 。或是創建一個 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)]

這樣更簡潔和易讀。

A list comprehension consists of brackets containing an expression
followed by a ‘for’ clause, then zero or more ‘for’ or ‘if’ clauses.
The result will be a new list resulting from evaluating the expression
in the context of the ‘for’ and ‘if’ clauses which follow it.  For
example, this listcomp combines the elements of two lists if they are
not equal:

     >>> [(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: c35. 和 *note if: dec. 在這兩段程式裡的順序是相同的。

如果 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, in <module>
         [x, x**2 for x in range(6)]
                    ^
     SyntaxError: invalid syntax
     >>> # 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 為一個 list
comprehension在 *note for: c35. 之前先被計算，接著再作一次 list
comprehension，所以，這個例子和下者相同：

     >>> 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(): c37. 函式會非常有效率：

     >>> list(zip(*matrix))
     [(1, 5, 9), (2, 6, 10), (3, 7, 11), (4, 8, 12)]

關於星號的更多細節，請參考 *note Unpacking Argument Lists: 125a. 。


File: python.info,  Node: The del statement,  Next: Tuples 和序列 Sequences,  Prev: 進一步了解 List（串列）,  Up: 資料結構

2.5.2 The ‘del’ statement
-------------------------

There is a way to remove an item from a list given its index instead of
its value: the *note del: 1273. statement.  This differs from the
‘pop()’ method which returns a value.  The ‘del’ statement can also be
used to remove slices from a list or clear the entire list (which we did
earlier by assignment of an empty list to the slice).  For example:

     >>> 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: 1273. 也可以用來刪除變數：

     >>> del a

刪除之後，對 ‘a’ 的參照將會造成錯誤（至少在另一個值又被指派到它之前）。
我們將在後面看到更多關於 *note del: 1273. 的其他用法。


File: python.info,  Node: Tuples 和序列 Sequences,  Next: 集合 Sets,  Prev: The del statement,  Up: 資料結構

2.5.3 Tuples 和序列 (Sequences)
-------------------------------

我們看到 lists 和 strings 有許多共同的特性，像是索引操作 (indexing) 以及
切片操作 (slicing) 。他們是 `序列' 資料結構中的兩個例子（請參考 *note
Sequence Types — list, tuple, range: 1275. ）。由於 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 中個別的項是不行的，但是可以在 tuple 中放入含有可變項
的物件，譬如 list 。

雖然 tuple 和 list 看起來很類似，但是他們通常用在不同的情況與不同目的。
tuple 是 *note immutable: 1227. （不可變的），通常儲存異質的序列元素，並
可經由拆解(unpacking) （請參考本節後段）或索引 (indexing) 來存取（或者在
使用 *note namedtuples: 1b8. 的時候藉由屬性 (attribute) 來存取）。 list
是 *note mutable: 122f. （可變的），其元素通常是同質的且可藉由迭代整個串
列來存取。

一個特別的議題是，關於創建一個含有 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 也包含了一種用在集合 (`sets') 的資料結構。一個 set 是一組無序且沒
有重複的元素。基本的使用方式包括了成員測試和消除重複項。 Set 物件也支援
聯集，交集，差集和互斥等數學操作。

大括號或 *note set(): b74. 函式都可以用來創建 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: 126f. 類似，也有 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: 301. ）。 Dictionary 有時被稱為 "關聯記憶體" (associative
memories) 或 "關聯矩陣" (associative arrays) 。不像序列是由一個範圍內的
數字當作索引， dictionary 是由 `key' （鍵）來當索引， key 可以是任何不可
變的型態；字串和數字都可以當作 key 。 Tuple 也可以當作 key 如果他們只含
有字串、數字或 tuple；若一個 tuple 直接或間接地含有任何可變的物件，它就
不能當作 key 。我們無法使用 list 當作 key ，因為 list 可以經由索引操作、
切片操作或是方法像是 ‘append()’ 和 ‘extend()’ 來修改。

思考 dict 最好的方式是把它想成是一組鍵值對 (`key: value' pair) 的集合，
其中 key 在同一個 dictionary（字典）裡必須是獨一無二的。使用一對大括號可
創建一個空的字典 ：‘{}’。將一串由逗號分隔的鍵值對置於大括號則可初始化字
典。這同樣也是字典輸出時的格式。

Dict 主要的操作為藉由鍵來儲存一個值並且可藉由該鍵來取出該值。也可以使用
‘del’ 來刪除鍵值對。如果我們使用用過的鍵來儲存，該鍵所對應的較舊的值會被
覆蓋。使用不存在的鍵來取出值會造成錯誤。

對字典使用 ‘list(d)’ 會得到一個包含該字典所有鍵（key）的 list，其排列順
序為插入時的順序。（若想要排序，則使用 ‘sorted(d)’ 代替即可）。如果想確
認一個鍵是否已存在於字典中，可使用關鍵字 *note in: 7a8. 。

這是個使用一個字典的簡單範例：

     >>> 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(): 1b9. 可直接透過一串鍵值對序列來創建 dict：

     >>> dict([('sape', 4139), ('guido', 4127), ('jack', 4098)])
     {'sape': 4139, 'guido': 4127, 'jack': 4098}

此外， dict comprehensions 也可以透過鍵與值的陳述式來創建 dict ：

     >>> {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: 更多條件式主題,  Prev: 字典（Dictionary）,  Up: 資料結構

2.5.6 迴圈技巧
--------------

當對 dict 作迴圈時，鍵以及其對應的值可以藉由使用 ‘items()’ 方法來同時取
得：

     >>> knights = {'gallahad': 'the pure', 'robin': 'the brave'}
     >>> for k, v in knights.items():
     ...     print(k, v)
     ...
     gallahad the pure
     robin the brave

當對序列作迴圈時，位置索引及其對應的值可以藉由使用 *note enumerate():
de8. 函式來同時取得：

     >>> for i, v in enumerate(['tic', 'tac', 'toe']):
     ...     print(i, v)
     ...
     0 tic
     1 tac
     2 toe

要同時對兩個以上的序列作迴圈，可以將其以成對的方式放入 *note zip(): c37.
函式：

     >>> 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():
18f. 函式：

     >>> for i in reversed(range(1, 10, 2)):
     ...     print(i)
     ...
     9
     7
     5
     3
     1

要以迴圈對序列作排序，使用 *note sorted(): 449. 函式會得到一個新的經排序
過的 list ，但不會改變原本的序列：

     >>> 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: 更多條件式主題,  Next: 序列和其他資料結構之比較,  Prev: 迴圈技巧,  Up: 資料結構

2.5.7 更多條件式主題
--------------------

使用在 ‘while’ 和 ‘if’ 內的陳述式可以包含任何運算子，而不是只有比較運算
子 (comparisons) 。

比較運算子 ‘in’ 和 ‘not in’ 檢查一個數值是否存在（不存在）於一個序列中。
運算子 ‘is’ 和 ‘not is’ 比較兩個物件是否真的是相同的物件；這對可變物件例
如 list 來說很重要。所有的比較運算子優先度都相同且都低於數值運算子。

比較運算是可以串連在一起的。例如， ‘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'

Note that in Python, unlike C, assignment inside expressions must be
done explicitly with the *note walrus operator: 127d. ‘:=’.  This avoids
a common class of problems encountered in C programs: typing ‘=’ in an
expression when ‘==’ was intended.


File: python.info,  Node: 序列和其他資料結構之比較,  Prev: 更多條件式主題,  Up: 資料結構

2.5.8 序列和其他資料結構之比較
------------------------------

Sequence objects typically may be compared to other objects with the
same sequence type.  The comparison uses `lexicographical' ordering:
first the first two items are compared, and if they differ this
determines the outcome of the comparison; if they are equal, the next
two items are compared, and so on, until either sequence is exhausted.
If two items to be compared are themselves sequences of the same type,
the lexicographical comparison is carried out recursively.  If all items
of two sequences compare equal, the sequences are considered equal.  If
one sequence is an initial sub-sequence of the other, the shorter
sequence is the smaller (lesser) one.  Lexicographical ordering for
strings uses the Unicode code point number to order individual
characters.  Some examples of comparisons between sequences of the same
type:

     (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: 193. 錯誤而不是提供
一個任意的排序。

註解
....


File: python.info,  Node: 模組,  Next: 輸入和輸出,  Prev: 資料結構,  Up: Python 教學

2.6 模組
========

如果從 Python 直譯器離開後又再次進入，之前（幫函式或變數）做的定義都會消
失。因此，想要寫一些比較長的程式時，你最好使用編輯器來準備要輸入給直譯器
的內容，並且用該檔案來運行它。這就是一個`腳本（script）'。隨著你的程式越
變越長，你可能會想要把它分開成幾個檔案，讓它比較好維護。你可能也會想用一
個你之前已經在其他程式寫好的函式，但不想要複製該函式的原始定義到所有使用
它的程式裡。

To support this, Python has a way to put definitions in a file and use
them in a script or in an interactive instance of the interpreter.  Such
a file is called a `module'; definitions from a module can be `imported'
into other modules or into the `main' module (the collection of
variables that you have access to in a script executed at the top level
and in calculator mode).

A module is a file containing Python definitions and statements.  The
file name is the module name with the suffix ‘.py’ appended.  Within a
module, the module’s name (as a string) is available as the value of the
global variable ‘__name__’.  For instance, use your favorite text editor
to create a file called ‘fibo.py’ in the current directory with the
following contents:

     # Fibonacci numbers module

     def fib(n):    # write Fibonacci series up to n
         a, b = 0, 1
         while a < n:
             print(a, end=' ')
             a, b = b, a+b
         print()

     def fib2(n):   # return Fibonacci series up to n
         result = []
         a, b = 0, 1
         while a < n:
             result.append(a)
             a, b = b, a+b
         return result

Now enter the Python interpreter and import this module with the
following command:

     >>> import fibo

This does not enter the names of the functions defined in ‘fibo’
directly in the current symbol table; it only enters the module name
‘fibo’ there.  Using the module name you can access the functions:

     >>> 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'

If you intend to use a function often you can assign it to a local name:

     >>> fib = fibo.fib
     >>> fib(500)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377

* Menu:

* More on Modules::
* Standard Modules::
* The dir() Function: The dir Function.
* Packages::


File: python.info,  Node: More on Modules,  Next: Standard Modules,  Up: 模組

2.6.1 More on Modules
---------------------

A module can contain executable statements as well as function
definitions.  These statements are intended to initialize the module.
They are executed only the `first' time the module name is encountered
in an import statement.  (1) (They are also run if the file is executed
as a script.)

Each module has its own private symbol table, which is used as the
global symbol table by all functions defined in the module.  Thus, the
author of a module can use global variables in the module without
worrying about accidental clashes with a user’s global variables.  On
the other hand, if you know what you are doing you can touch a module’s
global variables with the same notation used to refer to its functions,
‘modname.itemname’.

Modules can import other modules.  It is customary but not required to
place all *note import: c22. statements at the beginning of a module (or
script, for that matter).  The imported module names are placed in the
importing module’s global symbol table.

There is a variant of the *note import: c22. statement that imports
names from a module directly into the importing module’s symbol table.
For example:

     >>> from fibo import fib, fib2
     >>> fib(500)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377

This does not introduce the module name from which the imports are taken
in the local symbol table (so in the example, ‘fibo’ is not defined).

There is even a variant to import all names that a module defines:

     >>> from fibo import *
     >>> fib(500)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377

This imports all names except those beginning with an underscore (‘_’).
In most cases Python programmers do not use this facility since it
introduces an unknown set of names into the interpreter, possibly hiding
some things you have already defined.

Note that in general the practice of importing ‘*’ from a module or
package is frowned upon, since it often causes poorly readable code.
However, it is okay to use it to save typing in interactive sessions.

If the module name is followed by ‘as’, then the name following ‘as’ is
bound directly to the imported module.

     >>> import fibo as fib
     >>> fib.fib(500)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377

This is effectively importing the module in the same way that ‘import
fibo’ will do, with the only difference of it being available as ‘fib’.

It can also be used when utilising *note from: c4a. with similar
effects:

     >>> from fibo import fib as fibonacci
     >>> fibonacci(500)
     0 1 1 2 3 5 8 13 21 34 55 89 144 233 377

     備註: For efficiency reasons, each module is only imported once per
     interpreter session.  Therefore, if you change your modules, you
     must restart the interpreter – or, if it’s just one module you want
     to test interactively, use *note importlib.reload(): 39e, e.g.
     ‘import importlib; importlib.reload(modulename)’.

* Menu:

* Executing modules as scripts::
* The Module Search Path::
* "Compiled" Python files::

   ---------- Footnotes ----------

   (1) (1) In fact function definitions are also ’statements’ that are
’executed’; the execution of a module-level function definition enters
the function name in the module’s global symbol table.


File: python.info,  Node: Executing modules as scripts,  Next: The Module Search Path,  Up: More on Modules

2.6.1.1 Executing modules as scripts
....................................

When you run a Python module with

     python fibo.py <arguments>

the code in the module will be executed, just as if you imported it, but
with the ‘__name__’ set to ‘"__main__"’.  That means that by adding this
code at the end of your module:

     if __name__ == "__main__":
         import sys
         fib(int(sys.argv[1]))

you can make the file usable as a script as well as an importable
module, because the code that parses the command line only runs if the
module is executed as the "main" file:

     $ python fibo.py 50
     0 1 1 2 3 5 8 13 21 34

If the module is imported, the code is not run:

     >>> import fibo
     >>>

This is often used either to provide a convenient user interface to a
module, or for testing purposes (running the module as a script executes
a test suite).


File: python.info,  Node: The Module Search Path,  Next: "Compiled" Python files,  Prev: Executing modules as scripts,  Up: More on Modules

2.6.1.2 The Module Search Path
..............................

When a module named ‘spam’ is imported, the interpreter first searches
for a built-in module with that name.  If not found, it then searches
for a file named ‘spam.py’ in a list of directories given by the
variable *note sys.path: 48d.  *note sys.path: 48d. is initialized from
these locations:

   * The directory containing the input script (or the current directory
     when no file is specified).

   * *note PYTHONPATH: 958. (a list of directory names, with the same
     syntax as the shell variable ‘PATH’).

   * The installation-dependent default.

     備註: On file systems which support symlinks, the directory
     containing the input script is calculated after the symlink is
     followed.  In other words the directory containing the symlink is
     `not' added to the module search path.

After initialization, Python programs can modify *note sys.path: 48d.
The directory containing the script being run is placed at the beginning
of the search path, ahead of the standard library path.  This means that
scripts in that directory will be loaded instead of modules of the same
name in the library directory.  This is an error unless the replacement
is intended.  See section *note Standard Modules: 1289. for more
information.


File: python.info,  Node: "Compiled" Python files,  Prev: The Module Search Path,  Up: More on Modules

2.6.1.3 "Compiled" Python files
...............................

To speed up loading modules, Python caches the compiled version of each
module in the ‘__pycache__’ directory under the name
‘module.`version'.pyc’, where the version encodes the format of the
compiled file; it generally contains the Python version number.  For
example, in CPython release 3.3 the compiled version of spam.py would be
cached as ‘__pycache__/spam.cpython-33.pyc’.  This naming convention
allows compiled modules from different releases and different versions
of Python to coexist.

Python checks the modification date of the source against the compiled
version to see if it’s out of date and needs to be recompiled.  This is
a completely automatic process.  Also, the compiled modules are
platform-independent, so the same library can be shared among systems
with different architectures.

Python does not check the cache in two circumstances.  First, it always
recompiles and does not store the result for the module that’s loaded
directly from the command line.  Second, it does not check the cache if
there is no source module.  To support a non-source (compiled only)
distribution, the compiled module must be in the source directory, and
there must not be a source module.

Some tips for experts:

   * You can use the *note -O: 690. or *note -OO: 691. switches on the
     Python command to reduce the size of a compiled module.  The ‘-O’
     switch removes assert statements, the ‘-OO’ switch removes both
     assert statements and __doc__ strings.  Since some programs may
     rely on having these available, you should only use this option if
     you know what you’re doing.  "Optimized" modules have an ‘opt-’ tag
     and are usually smaller.  Future releases may change the effects of
     optimization.

   * A program doesn’t run any faster when it is read from a ‘.pyc’ file
     than when it is read from a ‘.py’ file; the only thing that’s
     faster about ‘.pyc’ files is the speed with which they are loaded.

   * The module *note compileall: 21. can create .pyc files for all
     modules in a directory.

   * There is more detail on this process, including a flow chart of the
     decisions, in PEP 3147(1).

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3147


File: python.info,  Node: Standard Modules,  Next: The dir Function,  Prev: More on Modules,  Up: 模組

2.6.2 Standard Modules
----------------------

Python comes with a library of standard modules, described in a separate
document, the Python Library Reference ("Library Reference" hereafter).
Some modules are built into the interpreter; these provide access to
operations that are not part of the core of the language but are
nevertheless built in, either for efficiency or to provide access to
operating system primitives such as system calls.  The set of such
modules is a configuration option which also depends on the underlying
platform.  For example, the *note winreg: 12b. module is only provided
on Windows systems.  One particular module deserves some attention:
*note sys: fe, which is built into every Python interpreter.  The
variables ‘sys.ps1’ and ‘sys.ps2’ define the strings used as primary and
secondary prompts:

     >>> import sys
     >>> sys.ps1
     '>>> '
     >>> sys.ps2
     '... '
     >>> sys.ps1 = 'C> '
     C> print('Yuck!')
     Yuck!
     C>

These two variables are only defined if the interpreter is in
interactive mode.

The variable ‘sys.path’ is a list of strings that determines the
interpreter’s search path for modules.  It is initialized to a default
path taken from the environment variable *note PYTHONPATH: 958, or from
a built-in default if *note PYTHONPATH: 958. is not set.  You can modify
it using standard list operations:

     >>> import sys
     >>> sys.path.append('/ufs/guido/lib/python')


File: python.info,  Node: The dir Function,  Next: Packages,  Prev: Standard Modules,  Up: 模組

2.6.3 The ‘dir()’ Function
--------------------------

The built-in function *note dir(): d38. is used to find out which names
a module defines.  It returns a sorted list of strings:

     >>> import fibo, sys
     >>> dir(fibo)
     ['__name__', 'fib', 'fib2']
     >>> dir(sys)
     ['__displayhook__', '__doc__', '__excepthook__', '__loader__', '__name__',
      '__package__', '__stderr__', '__stdin__', '__stdout__',
      '_clear_type_cache', '_current_frames', '_debugmallocstats', '_getframe',
      '_home', '_mercurial', '_xoptions', 'abiflags', 'api_version', 'argv',
      'base_exec_prefix', 'base_prefix', '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',
      'getcheckinterval', 'getdefaultencoding', 'getdlopenflags',
      'getfilesystemencoding', 'getobjects', 'getprofile', 'getrecursionlimit',
      'getrefcount', 'getsizeof', 'getswitchinterval', 'gettotalrefcount',
      'gettrace', 'hash_info', 'hexversion', 'implementation', 'int_info',
      'intern', 'maxsize', 'maxunicode', 'meta_path', 'modules', 'path',
      'path_hooks', 'path_importer_cache', 'platform', 'prefix', 'ps1',
      'setcheckinterval', 'setdlopenflags', 'setprofile', 'setrecursionlimit',
      'setswitchinterval', 'settrace', 'stderr', 'stdin', 'stdout',
      'thread_info', 'version', 'version_info', 'warnoptions']

Without arguments, *note dir(): d38. lists the names you have defined
currently:

     >>> a = [1, 2, 3, 4, 5]
     >>> import fibo
     >>> fib = fibo.fib
     >>> dir()
     ['__builtins__', '__name__', 'a', 'fib', 'fibo', 'sys']

Note that it lists all types of names: variables, modules, functions,
etc.

*note dir(): d38. does not list the names of built-in functions and
variables.  If you want a list of those, they are defined in the
standard module *note builtins: 13.:

     >>> 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: Packages,  Prev: The dir Function,  Up: 模組

2.6.4 Packages
--------------

Packages are a way of structuring Python’s module namespace by using
"dotted module names".  For example, the module name ‘A.B’ designates a
submodule named ‘B’ in a package named ‘A’.  Just like the use of
modules saves the authors of different modules from having to worry
about each other’s global variable names, the use of dotted module names
saves the authors of multi-module packages like NumPy or Pillow from
having to worry about each other’s module names.

Suppose you want to design a collection of modules (a "package") for the
uniform handling of sound files and sound data.  There are many
different sound file formats (usually recognized by their extension, for
example: ‘.wav’, ‘.aiff’, ‘.au’), so you may need to create and maintain
a growing collection of modules for the conversion between the various
file formats.  There are also many different operations you might want
to perform on sound data (such as mixing, adding echo, applying an
equalizer function, creating an artificial stereo effect), so in
addition you will be writing a never-ending stream of modules to perform
these operations.  Here’s a possible structure for your package
(expressed in terms of a hierarchical filesystem):

     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
                   ...

When importing the package, Python searches through the directories on
‘sys.path’ looking for the package subdirectory.

The ‘__init__.py’ files are required to make Python treat directories
containing the file as packages.  This prevents directories with a
common name, such as ‘string’, unintentionally hiding valid modules that
occur later on the module search path.  In the simplest case,
‘__init__.py’ can just be an empty file, but it can also execute
initialization code for the package or set the ‘__all__’ variable,
described later.

Users of the package can import individual modules from the package, for
example:

     import sound.effects.echo

This loads the submodule ‘sound.effects.echo’.  It must be referenced
with its full name.

     sound.effects.echo.echofilter(input, output, delay=0.7, atten=4)

An alternative way of importing the submodule is:

     from sound.effects import echo

This also loads the submodule ‘echo’, and makes it available without its
package prefix, so it can be used as follows:

     echo.echofilter(input, output, delay=0.7, atten=4)

Yet another variation is to import the desired function or variable
directly:

     from sound.effects.echo import echofilter

Again, this loads the submodule ‘echo’, but this makes its function
‘echofilter()’ directly available:

     echofilter(input, output, delay=0.7, atten=4)

Note that when using ‘from package import item’, the item can be either
a submodule (or subpackage) of the package, or some other name defined
in the package, like a function, class or variable.  The ‘import’
statement first tests whether the item is defined in the package; if
not, it assumes it is a module and attempts to load it.  If it fails to
find it, an *note ImportError: 339. exception is raised.

Contrarily, when using syntax like ‘import item.subitem.subsubitem’,
each item except for the last must be a package; the last item can be a
module or a package but can’t be a class or function or variable defined
in the previous item.

* Menu:

* Importing * From a Package::
* Intra-package References::
* Packages in Multiple Directories::


File: python.info,  Node: Importing * From a Package,  Next: Intra-package References,  Up: Packages

2.6.4.1 Importing * From a Package
..................................

Now what happens when the user writes ‘from sound.effects import *’?
Ideally, one would hope that this somehow goes out to the filesystem,
finds which submodules are present in the package, and imports them all.
This could take a long time and importing sub-modules might have
unwanted side-effects that should only happen when the sub-module is
explicitly imported.

The only solution is for the package author to provide an explicit index
of the package.  The *note import: c22. statement uses the following
convention: if a package’s ‘__init__.py’ code defines a list named
‘__all__’, it is taken to be the list of module names that should be
imported when ‘from package import *’ is encountered.  It is up to the
package author to keep this list up-to-date when a new version of the
package is released.  Package authors may also decide not to support it,
if they don’t see a use for importing * from their package.  For
example, the file ‘sound/effects/__init__.py’ could contain the
following code:

     __all__ = ["echo", "surround", "reverse"]

This would mean that ‘from sound.effects import *’ would import the
three named submodules of the ‘sound’ package.

If ‘__all__’ is not defined, the statement ‘from sound.effects import *’
does `not' import all submodules from the package ‘sound.effects’ into
the current namespace; it only ensures that the package ‘sound.effects’
has been imported (possibly running any initialization code in
‘__init__.py’) and then imports whatever names are defined in the
package.  This includes any names defined (and submodules explicitly
loaded) by ‘__init__.py’.  It also includes any submodules of the
package that were explicitly loaded by previous *note import: c22.
statements.  Consider this code:

     import sound.effects.echo
     import sound.effects.surround
     from sound.effects import *

In this example, the ‘echo’ and ‘surround’ modules are imported in the
current namespace because they are defined in the ‘sound.effects’
package when the ‘from...import’ statement is executed.  (This also
works when ‘__all__’ is defined.)

Although certain modules are designed to export only names that follow
certain patterns when you use ‘import *’, it is still considered bad
practice in production code.

Remember, there is nothing wrong with using ‘from package import
specific_submodule’!  In fact, this is the recommended notation unless
the importing module needs to use submodules with the same name from
different packages.


File: python.info,  Node: Intra-package References,  Next: Packages in Multiple Directories,  Prev: Importing * From a Package,  Up: Packages

2.6.4.2 Intra-package References
................................

When packages are structured into subpackages (as with the ‘sound’
package in the example), you can use absolute imports to refer to
submodules of siblings packages.  For example, if the module
‘sound.filters.vocoder’ needs to use the ‘echo’ module in the
‘sound.effects’ package, it can use ‘from sound.effects import echo’.

You can also write relative imports, with the ‘from module import name’
form of import statement.  These imports use leading dots to indicate
the current and parent packages involved in the relative import.  From
the ‘surround’ module for example, you might use:

     from . import echo
     from .. import formats
     from ..filters import equalizer

Note that relative imports are based on the name of the current module.
Since the name of the main module is always ‘"__main__"’, modules
intended for use as the main module of a Python application must always
use absolute imports.


File: python.info,  Node: Packages in Multiple Directories,  Prev: Intra-package References,  Up: Packages

2.6.4.3 Packages in Multiple Directories
........................................

Packages support one more special attribute, *note __path__: 1294.  This
is initialized to be a list containing the name of the directory holding
the package’s ‘__init__.py’ before the code in that file is executed.
This variable can be modified; doing so affects future searches for
modules and subpackages contained in the package.

While this feature is not often needed, it can be used to extend the set
of modules found in a package.

註解
....


File: python.info,  Node: 輸入和輸出,  Next: 錯誤和例外,  Prev: 模組,  Up: Python 教學

2.7 輸入和輸出
==============

有數種方式可以顯示程式的輸出；資料可以以人類易讀的形式印出，或是寫入檔案
以供未來所使用。這章節會討論幾種不同的方式。

* Menu:

* 更華麗的輸出格式::
* Reading and Writing Files::


File: python.info,  Node: 更華麗的輸出格式,  Next: Reading and Writing Files,  Up: 輸入和輸出

2.7.1 更華麗的輸出格式
----------------------

目前為止我們已經學過兩種寫值的方式：`表示式陳述 (expression statements)'
與 *note print(): 88b. 函式。（第三種方法是使用檔案物件的 ‘write()’ 方法
；標準輸出的檔案是使用 ‘sys.stdout’ 來達成的。詳細的資訊請參考對應的函示
庫說明。）

通常你會想要對輸出格式有更多地控制；而不是僅列印出以空格隔開的值。以下是
幾種格式化輸出的方式。

   * To use *note formatted string literals: 129a, begin a string with
     ‘f’ or ‘F’ before the opening quotation mark or triple quotation
     mark.  Inside this string, you can write a Python expression
     between ‘{’ and ‘}’ characters that can refer to variables or
     literal values.

          >>> year = 2016
          >>> event = 'Referendum'
          >>> f'Results of the {year} {event}'
          'Results of the 2016 Referendum'

   * The *note str.format(): 4df. method of strings requires more manual
     effort.  You’ll still use ‘{’ and ‘}’ to mark where a variable will
     be substituted and can provide detailed formatting directives, but
     you’ll also need to provide the information to be formatted.

          >>> yes_votes = 42_572_654
          >>> no_votes = 43_132_495
          >>> percentage = yes_votes / (yes_votes + no_votes)
          >>> '{:-9} YES votes  {:2.2%}'.format(yes_votes, percentage)
          ' 42572654 YES votes  49.67%'

   * Finally, you can do all the string handling yourself by using
     string slicing and concatenation operations to create any layout
     you can imagine.  The string type has some methods that perform
     useful operations for padding strings to a given column width.

When you don’t need fancy output but just want a quick display of some
variables for debugging purposes, you can convert any value to a string
with the *note repr(): 7d1. or *note str(): 335. functions.

The *note str(): 335. function is meant to return representations of
values which are fairly human-readable, while *note repr(): 7d1. is
meant to generate representations which can be read by the interpreter
(or will force a *note SyntaxError: 45d. if there is no equivalent
syntax).  For objects which don’t have a particular representation for
human consumption, *note str(): 335. will return the same value as *note
repr(): 7d1.  Many values, such as numbers or structures like lists and
dictionaries, have the same representation using either function.
Strings, in particular, have two distinct representations.

一些範例：

     >>> 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'))"

The *note string: f7. module contains a *note Template: 3f0. class that
offers yet another way to substitute values into strings, using
placeholders like ‘$x’ and replacing them with values from a dictionary,
but offers much less control of the formatting.

* Menu:

* 格式化的字串文本 (Formatted String Literals): 格式化的字串文本 Formatted String Literals.
* The String format() Method: The String format Method.
* Manual String Formatting::
* Old string formatting::


File: python.info,  Node: 格式化的字串文本 Formatted String Literals,  Next: The String format Method,  Up: 更華麗的輸出格式

2.7.1.1 格式化的字串文本 (Formatted String Literals)
....................................................

*note Formatted string literals: 15d. (also called f-strings for short)
let you include the value of Python expressions inside a string by
prefixing the string with ‘f’ or ‘F’ and writing expressions as
‘{expression}’.

An optional format specifier can follow the expression.  This allows
greater control over how the value is formatted.  The following example
rounds pi to three places after the decimal:

     >>> import math
     >>> print(f'The value of pi is approximately {math.pi:.3f}.')
     The value of pi is approximately 3.142.

Passing an integer after the ‘':'’ will cause that field to be a minimum
number of characters wide.  This is useful for making columns line up.

     >>> 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

Other modifiers can be used to convert the value before it is formatted.
‘'!a'’ applies *note ascii(): d51, ‘'!s'’ applies *note str(): 335, and
‘'!r'’ applies *note repr(): 7d1.:

     >>> 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'.

For a reference on these format specifications, see the reference guide
for the *note Format Specification Mini-Language: 4e3.


File: python.info,  Node: The String format Method,  Next: Manual String Formatting,  Prev: 格式化的字串文本 Formatted String Literals,  Up: 更華麗的輸出格式

2.7.1.2 The String format() Method
..................................

Basic usage of the *note str.format(): 4df. method looks like this:

     >>> print('We are the {} who say "{}!"'.format('knights', 'Ni'))
     We are the knights who say "Ni!"

The brackets and characters within them (called format fields) are
replaced with the objects passed into the *note str.format(): 4df.
method.  A number in the brackets can be used to refer to the position
of the object passed into the *note str.format(): 4df. method.

     >>> print('{0} and {1}'.format('spam', 'eggs'))
     spam and eggs
     >>> print('{1} and {0}'.format('spam', 'eggs'))
     eggs and spam

If keyword arguments are used in the *note str.format(): 4df. method,
their values are referred to by using the name of the argument.

     >>> print('This {food} is {adjective}.'.format(
     ...       food='spam', adjective='absolutely horrible'))
     This spam is absolutely horrible.

Positional and keyword arguments can be arbitrarily combined:

     >>> print('The story of {0}, {1}, and {other}.'.format('Bill', 'Manfred',
                                                            other='Georg'))
     The story of Bill, Manfred, and Georg.

If you have a really long format string that you don’t want to split up,
it would be nice if you could reference the variables to be formatted by
name instead of by position.  This can be done by simply passing the
dict and using square brackets ‘'[]'’ to access the keys.

     >>> 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

This could also be done by passing the table as keyword arguments with
the ’**’ notation.

     >>> 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

This is particularly useful in combination with the built-in function
*note vars(): 103c, which returns a dictionary containing all local
variables.

As an example, the following lines produce a tidily-aligned set of
columns giving integers and their squares and cubes:

     >>> 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

For a complete overview of string formatting with *note str.format():
4df, see *note Format String Syntax: d1f.


File: python.info,  Node: Manual String Formatting,  Next: Old string formatting,  Prev: The String format Method,  Up: 更華麗的輸出格式

2.7.1.3 Manual String Formatting
................................

Here’s the same table of squares and cubes, formatted manually:

     >>> for x in range(1, 11):
     ...     print(repr(x).rjust(2), repr(x*x).rjust(3), end=' ')
     ...     # Note use of 'end' on previous line
     ...     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 that the one space between each column was added by the way *note
print(): 88b. works: it always adds spaces between its arguments.)

The *note str.rjust(): 129f. method of string objects right-justifies a
string in a field of a given width by padding it with spaces on the
left.  There are similar methods *note str.ljust(): 12a0. and *note
str.center(): 12a1.  These methods do not write anything, they just
return a new string.  If the input string is too long, they don’t
truncate it, but return it unchanged; this will mess up your column
lay-out but that’s usually better than the alternative, which would be
lying about a value.  (If you really want truncation you can always add
a slice operation, as in ‘x.ljust(n)[:n]’.)

There is another method, *note str.zfill(): 12a2, which pads a numeric
string on the left with zeros.  It understands about plus and minus
signs:

     >>> '12'.zfill(5)
     '00012'
     >>> '-3.14'.zfill(7)
     '-003.14'
     >>> '3.14159265359'.zfill(5)
     '3.14159265359'


File: python.info,  Node: Old string formatting,  Prev: Manual String Formatting,  Up: 更華麗的輸出格式

2.7.1.4 Old string formatting
.............................

The % operator (modulo) can also be used for string formatting.  Given
‘'string' % values’, instances of ‘%’ in ‘string’ are replaced with zero
or more elements of ‘values’.  This operation is commonly known as
string interpolation.  For example:

     >>> import math
     >>> print('The value of pi is approximately %5.3f.' % math.pi)
     The value of pi is approximately 3.142.

More information can be found in the *note printf-style String
Formatting: 122a. section.


File: python.info,  Node: Reading and Writing Files,  Prev: 更華麗的輸出格式,  Up: 輸入和輸出

2.7.2 Reading and Writing Files
-------------------------------

*note open(): 4f5. returns a *note file object: b47, and is most
commonly used with two arguments: ‘open(filename, mode)’.

     >>> f = open('workfile', 'w')

The first argument is a string containing the filename.  The second
argument is another string containing a few characters describing the
way in which the file will be used.  `mode' can be ‘'r'’ when the file
will only be read, ‘'w'’ for only writing (an existing file with the
same name will be erased), and ‘'a'’ opens the file for appending; any
data written to the file is automatically added to the end.  ‘'r+'’
opens the file for both reading and writing.  The `mode' argument is
optional; ‘'r'’ will be assumed if it’s omitted.

Normally, files are opened in `text mode', that means, you read and
write strings from and to the file, which are encoded in a specific
encoding.  If encoding is not specified, the default is platform
dependent (see *note open(): 4f5.).  ‘'b'’ appended to the mode opens
the file in `binary mode': now the data is read and written in the form
of bytes objects.  This mode should be used for all files that don’t
contain text.

In text mode, the default when reading is to convert platform-specific
line endings (‘\n’ on Unix, ‘\r\n’ on Windows) to just ‘\n’.  When
writing in text mode, the default is to convert occurrences of ‘\n’ back
to platform-specific line endings.  This behind-the-scenes modification
to file data is fine for text files, but will corrupt binary data like
that in ‘JPEG’ or ‘EXE’ files.  Be very careful to use binary mode when
reading and writing such files.

It is good practice to use the *note with: 6ee. keyword when dealing
with file objects.  The advantage is that the file is properly closed
after its suite finishes, even if an exception is raised at some point.
Using ‘with’ is also much shorter than writing equivalent *note try:
d77.-*note finally: 183. blocks:

     >>> with open('workfile') as f:
     ...     read_data = f.read()

     >>> # We can check that the file has been automatically closed.
     >>> f.closed
     True

If you’re not using the *note with: 6ee. keyword, then you should call
‘f.close()’ to close the file and immediately free up any system
resources used by it.

     警告: Calling ‘f.write()’ without using the ‘with’ keyword or
     calling ‘f.close()’ `might' result in the arguments of ‘f.write()’
     not being completely written to the disk, even if the program exits
     successfully.

After a file object is closed, either by a *note with: 6ee. statement or
by calling ‘f.close()’, attempts to use the file object will
automatically fail.

     >>> f.close()
     >>> f.read()
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ValueError: I/O operation on closed file.

* Menu:

* Methods of File Objects::
* Saving structured data with json::


File: python.info,  Node: Methods of File Objects,  Next: Saving structured data with json,  Up: Reading and Writing Files

2.7.2.1 Methods of File Objects
...............................

The rest of the examples in this section will assume that a file object
called ‘f’ has already been created.

To read a file’s contents, call ‘f.read(size)’, which reads some
quantity of data and returns it as a string (in text mode) or bytes
object (in binary mode).  `size' is an optional numeric argument.  When
`size' is omitted or negative, the entire contents of the file will be
read and returned; it’s your problem if the file is twice as large as
your machine’s memory.  Otherwise, at most `size' characters (in text
mode) or `size' bytes (in binary mode) are read and returned.  If the
end of the file has been reached, ‘f.read()’ will return an empty string
(‘''’).

     >>> f.read()
     'This is the entire file.\n'
     >>> f.read()
     ''

‘f.readline()’ reads a single line from the file; a newline character
(‘\n’) is left at the end of the string, and is only omitted on the last
line of the file if the file doesn’t end in a newline.  This makes the
return value unambiguous; if ‘f.readline()’ returns an empty string, the
end of the file has been reached, while a blank line is represented by
‘'\n'’, a string containing only a single newline.

     >>> f.readline()
     'This is the first line of the file.\n'
     >>> f.readline()
     'Second line of the file\n'
     >>> f.readline()
     ''

For reading lines from a file, you can loop over the file object.  This
is memory efficient, fast, and leads to simple code:

     >>> for line in f:
     ...     print(line, end='')
     ...
     This is the first line of the file.
     Second line of the file

If you want to read all the lines of a file in a list you can also use
‘list(f)’ or ‘f.readlines()’.

‘f.write(string)’ writes the contents of `string' to the file, returning
the number of characters written.

     >>> f.write('This is a test\n')
     15

Other types of objects need to be converted – either to a string (in
text mode) or a bytes object (in binary mode) – before writing them:

     >>> value = ('the answer', 42)
     >>> s = str(value)  # convert the tuple to string
     >>> f.write(s)
     18

‘f.tell()’ returns an integer giving the file object’s current position
in the file represented as number of bytes from the beginning of the
file when in binary mode and an opaque number when in text mode.

To change the file object’s position, use ‘f.seek(offset, whence)’.  The
position is computed from adding `offset' to a reference point; the
reference point is selected by the `whence' argument.  A `whence' value
of 0 measures from the beginning of the file, 1 uses the current file
position, and 2 uses the end of the file as the reference point.
`whence' can be omitted and defaults to 0, using the beginning of the
file as the reference point.

     >>> f = open('workfile', 'rb+')
     >>> f.write(b'0123456789abcdef')
     16
     >>> f.seek(5)      # Go to the 6th byte in the file
     5
     >>> f.read(1)
     b'5'
     >>> f.seek(-3, 2)  # Go to the 3rd byte before the end
     13
     >>> f.read(1)
     b'd'

In text files (those opened without a ‘b’ in the mode string), only
seeks relative to the beginning of the file are allowed (the exception
being seeking to the very file end with ‘seek(0, 2)’) and the only valid
`offset' values are those returned from the ‘f.tell()’, or zero.  Any
other `offset' value produces undefined behaviour.

File objects have some additional methods, such as ‘isatty()’ and
‘truncate()’ which are less frequently used; consult the Library
Reference for a complete guide to file objects.


File: python.info,  Node: Saving structured data with json,  Prev: Methods of File Objects,  Up: Reading and Writing Files

2.7.2.2 Saving structured data with ‘json’
..........................................

Strings can easily be written to and read from a file.  Numbers take a
bit more effort, since the ‘read()’ method only returns strings, which
will have to be passed to a function like *note int(): 185, which takes
a string like ‘'123'’ and returns its numeric value 123.  When you want
to save more complex data types like nested lists and dictionaries,
parsing and serializing by hand becomes complicated.

Rather than having users constantly writing and debugging code to save
complicated data types to files, Python allows you to use the popular
data interchange format called JSON (JavaScript Object Notation)(1).
The standard module called *note json: a5. can take Python data
hierarchies, and convert them to string representations; this process is
called `serializing'.  Reconstructing the data from the string
representation is called `deserializing'.  Between serializing and
deserializing, the string representing the object may have been stored
in a file or data, or sent over a network connection to some distant
machine.

     備註: The JSON format is commonly used by modern applications to
     allow for data exchange.  Many programmers are already familiar
     with it, which makes it a good choice for interoperability.

If you have an object ‘x’, you can view its JSON string representation
with a simple line of code:

     >>> import json
     >>> json.dumps([1, 'simple', 'list'])
     '[1, "simple", "list"]'

Another variant of the *note dumps(): 60a. function, called *note
dump(): 609, simply serializes the object to a *note text file: 12aa.
So if ‘f’ is a *note text file: 12aa. object opened for writing, we can
do this:

     json.dump(x, f)

To decode the object again, if ‘f’ is a *note text file: 12aa. object
which has been opened for reading:

     x = json.load(f)

This simple serialization technique can handle lists and dictionaries,
but serializing arbitrary class instances in JSON requires a bit of
extra effort.  The reference for the *note json: a5. module contains an
explanation of this.

也參考
......

*note pickle: cb. - the pickle module

Contrary to *note JSON: 12a9, `pickle' is a protocol which allows the
serialization of arbitrarily complex Python objects.  As such, it is
specific to Python and cannot be used to communicate with applications
written in other languages.  It is also insecure by default:
deserializing pickle data coming from an untrusted source can execute
arbitrary code, if the data was crafted by a skilled attacker.

   ---------- Footnotes ----------

   (1) http://json.org


File: python.info,  Node: 錯誤和例外,  Next: Classes,  Prev: 輸入和輸出,  Up: Python 教學

2.8 錯誤和例外
==============

Until now error messages haven’t been more than mentioned, but if you
have tried out the examples you have probably seen some.  There are (at
least) two distinguishable kinds of errors: `syntax errors' and
`exceptions'.

* Menu:

* 語法錯誤::
* 例外::
* 處理例外::
* Raising Exceptions::
* User-defined Exceptions::
* Defining Clean-up Actions::
* Predefined Clean-up Actions::


File: python.info,  Node: 語法錯誤,  Next: 例外,  Up: 錯誤和例外

2.8.1 語法錯誤
--------------

Syntax errors, also known as parsing errors, are perhaps the most common
kind of complaint you get while you are still learning 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 a little ’arrow’
pointing at the earliest point in the line where the error was detected.
The error is caused by (or at least detected at) the token `preceding'
the arrow: in the example, the error is detected at the function *note
print(): 88b, 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: 例外,  Next: 處理例外,  Prev: 語法錯誤,  Up: 錯誤和例外

2.8.2 例外
----------

Even if a statement or expression is syntactically correct, it may cause
an error when an attempt is made to execute it.  Errors detected during
execution are called `exceptions' and are not unconditionally fatal: you
will soon learn how to handle them in Python programs.  Most exceptions
are not handled by programs, however, and result in error messages as
shown here:

     >>> 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't convert 'int' object to str implicitly

The last line of the error message indicates what happened.  Exceptions
come in different types, and the type is printed as part of the message:
the types in the example are *note ZeroDivisionError: 12b2, *note
NameError: d80. and *note TypeError: 193.  The string printed as the
exception type is the name of the built-in exception that occurred.
This is true for all built-in exceptions, but need not be true for
user-defined exceptions (although it is a useful convention).  Standard
exception names are built-in identifiers (not reserved keywords).

The rest of the line provides detail based on the type of exception and
what caused it.

The preceding part of the error message shows the context where the
exception happened, in the form of a stack traceback.  In general it
contains a stack traceback listing source lines; however, it will not
display lines read from standard input.

*note 內建的例外: 12b3. lists the built-in exceptions and their
meanings.


File: python.info,  Node: 處理例外,  Next: Raising Exceptions,  Prev: 例外,  Up: 錯誤和例外

2.8.3 處理例外
--------------

It is possible to write programs that handle selected exceptions.  Look
at the following example, which asks the user for input until a valid
integer has been entered, but allows the user to interrupt the program
(using ‘Control-C’ or whatever the operating system supports); note that
a user-generated interruption is signalled by raising the *note
KeyboardInterrupt: 198. exception.

     >>> while True:
     ...     try:
     ...         x = int(input("Please enter a number: "))
     ...         break
     ...     except ValueError:
     ...         print("Oops!  That was no valid number.  Try again...")
     ...

The *note try: d77. statement works as follows.

   * First, the `try clause' (the statement(s) between the *note try:
     d77. and *note except: b43. keywords) is executed.

   * If no exception occurs, the `except clause' is skipped and
     execution of the *note try: d77. statement is finished.

   * If an exception occurs during execution of the try clause, the rest
     of the clause is skipped.  Then if its type matches the exception
     named after the *note except: b43. keyword, the except clause is
     executed, and then execution continues after the *note try: d77.
     statement.

   * If an exception occurs which does not match the exception named in
     the except clause, it is passed on to outer *note try: d77.
     statements; if no handler is found, it is an `unhandled exception'
     and execution stops with a message as shown above.

A *note try: d77. statement may have more than one except clause, to
specify handlers for different exceptions.  At most one handler will be
executed.  Handlers only handle exceptions that occur in the
corresponding try clause, not in other handlers of the same ‘try’
statement.  An except clause may name multiple exceptions as a
parenthesized tuple, for example:

     ... except (RuntimeError, TypeError, NameError):
     ...     pass

A class in an *note except: b43. clause is compatible with an exception
if it is the same class or a base class thereof (but not the other way
around — an except clause listing a derived class is not compatible with
a base class).  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")

Note that if the except clauses were reversed (with ‘except B’ first),
it would have printed B, B, B — the first matching except clause is
triggered.

The last except clause may omit the exception name(s), to serve as a
wildcard.  Use this with extreme caution, since it is easy to mask a
real programming error in this way!  It can also be used to print an
error message and then re-raise the exception (allowing a caller to
handle the exception as well):

     import sys

     try:
         f = open('myfile.txt')
         s = f.readline()
         i = int(s.strip())
     except OSError as err:
         print("OS error: {0}".format(err))
     except ValueError:
         print("Could not convert data to an integer.")
     except:
         print("Unexpected error:", sys.exc_info()[0])
         raise

The *note try: d77. ...  *note except: b43. statement has an optional
`else clause', which, when present, must follow all except clauses.  It
is useful for code that must be executed if the try clause does not
raise an exception.  For example:

     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()

The use of the ‘else’ clause is better than adding additional code to
the *note try: d77. clause because it avoids accidentally catching an
exception that wasn’t raised by the code being protected by the ‘try’
...  ‘except’ statement.

When an exception occurs, it may have an associated value, also known as
the exception’s `argument'.  The presence and type of the argument
depend on the exception type.

The except clause may specify a variable after the exception name.  The
variable is bound to an exception instance with the arguments stored in
‘instance.args’.  For convenience, the exception instance defines *note
__str__(): e3c. so the arguments can be printed directly without having
to reference ‘.args’.  One may also instantiate an exception first
before raising it and add any attributes to it as desired.

     >>> try:
     ...     raise Exception('spam', 'eggs')
     ... except Exception as inst:
     ...     print(type(inst))    # the exception instance
     ...     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

If an exception has arguments, they are printed as the last part
(’detail’) of the message for unhandled exceptions.

Exception handlers don’t just handle exceptions if they occur
immediately in the try clause, but also if they occur inside functions
that are called (even indirectly) in the try clause.  For example:

     >>> 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: Raising Exceptions,  Next: User-defined Exceptions,  Prev: 處理例外,  Up: 錯誤和例外

2.8.4 Raising Exceptions
------------------------

The *note raise: c47. statement allows the programmer to force a
specified exception to occur.  For example:

     >>> raise NameError('HiThere')
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     NameError: HiThere

The sole argument to *note raise: c47. indicates the exception to be
raised.  This must be either an exception instance or an exception class
(a class that derives from *note Exception: 1aa.).  If an exception
class is passed, it will be implicitly instantiated by calling its
constructor with no arguments:

     raise ValueError  # shorthand for 'raise ValueError()'

If you need to determine whether an exception was raised but don’t
intend to handle it, a simpler form of the *note raise: c47. statement
allows you to re-raise the exception:

     >>> 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: User-defined Exceptions,  Next: Defining Clean-up Actions,  Prev: Raising Exceptions,  Up: 錯誤和例外

2.8.5 User-defined Exceptions
-----------------------------

Programs may name their own exceptions by creating a new exception class
(see *note Classes: 124a. for more about Python classes).  Exceptions
should typically be derived from the *note Exception: 1aa. class, either
directly or indirectly.

Exception classes can be defined which do anything any other class can
do, but are usually kept simple, often only offering a number of
attributes that allow information about the error to be extracted by
handlers for the exception.  When creating a module that can raise
several distinct errors, a common practice is to create a base class for
exceptions defined by that module, and subclass that to create specific
exception classes for different error conditions:

     class Error(Exception):
         """Base class for exceptions in this module."""
         pass

     class InputError(Error):
         """Exception raised for errors in the input.

         Attributes:
             expression -- input expression in which the error occurred
             message -- explanation of the error
         """

         def __init__(self, expression, message):
             self.expression = expression
             self.message = message

     class TransitionError(Error):
         """Raised when an operation attempts a state transition that's not
         allowed.

         Attributes:
             previous -- state at beginning of transition
             next -- attempted new state
             message -- explanation of why the specific transition is not allowed
         """

         def __init__(self, previous, next, message):
             self.previous = previous
             self.next = next
             self.message = message

Most exceptions are defined with names that end in "Error", similar to
the naming of the standard exceptions.

Many standard modules define their own exceptions to report errors that
may occur in functions they define.  More information on classes is
presented in chapter *note Classes: 124a.


File: python.info,  Node: Defining Clean-up Actions,  Next: Predefined Clean-up Actions,  Prev: User-defined Exceptions,  Up: 錯誤和例外

2.8.6 Defining Clean-up Actions
-------------------------------

The *note try: d77. statement has another optional clause which is
intended to define clean-up actions that must be executed under all
circumstances.  For example:

     >>> try:
     ...     raise KeyboardInterrupt
     ... finally:
     ...     print('Goodbye, world!')
     ...
     Goodbye, world!
     Traceback (most recent call last):
       File "<stdin>", line 2, in <module>
     KeyboardInterrupt

If a *note finally: 183. clause is present, the ‘finally’ clause will
execute as the last task before the *note try: d77. statement completes.
The ‘finally’ clause runs whether or not the ‘try’ statement produces an
exception.  The following points discuss more complex cases when an
exception occurs:

   * If an exception occurs during execution of the ‘try’ clause, the
     exception may be handled by an *note except: b43. clause.  If the
     exception is not handled by an ‘except’ clause, the exception is
     re-raised after the ‘finally’ clause has been executed.

   * An exception could occur during execution of an ‘except’ or ‘else’
     clause.  Again, the exception is re-raised after the ‘finally’
     clause has been executed.

   * If the ‘try’ statement reaches a *note break: 2dc, *note continue:
     182. or *note return: 191. statement, the ‘finally’ clause will
     execute just prior to the ‘break’, ‘continue’ or ‘return’
     statement’s execution.

   * If a ‘finally’ clause includes a ‘return’ statement, the returned
     value will be the one from the ‘finally’ clause’s ‘return’
     statement, not the value from the ‘try’ clause’s ‘return’
     statement.

For example:

     >>> def bool_return():
     ...     try:
     ...         return True
     ...     finally:
     ...         return False
     ...
     >>> bool_return()
     False

A more complicated example:

     >>> 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'

As you can see, the *note finally: 183. clause is executed in any event.
The *note TypeError: 193. raised by dividing two strings is not handled
by the *note except: b43. clause and therefore re-raised after the
‘finally’ clause has been executed.

In real world applications, the *note finally: 183. clause is useful for
releasing external resources (such as files or network connections),
regardless of whether the use of the resource was successful.


File: python.info,  Node: Predefined Clean-up Actions,  Prev: Defining Clean-up Actions,  Up: 錯誤和例外

2.8.7 Predefined Clean-up Actions
---------------------------------

Some objects define standard clean-up actions to be undertaken when the
object is no longer needed, regardless of whether or not the operation
using the object succeeded or failed.  Look at the following example,
which tries to open a file and print its contents to the screen.

     for line in open("myfile.txt"):
         print(line, end="")

The problem with this code is that it leaves the file open for an
indeterminate amount of time after this part of the code has finished
executing.  This is not an issue in simple scripts, but can be a problem
for larger applications.  The *note with: 6ee. statement allows objects
like files to be used in a way that ensures they are always cleaned up
promptly and correctly.

     with open("myfile.txt") as f:
         for line in f:
             print(line, end="")

After the statement is executed, the file `f' is always closed, even if
a problem was encountered while processing the lines.  Objects which,
like files, provide predefined clean-up actions will indicate this in
their documentation.


File: python.info,  Node: Classes,  Next: Python 標準函式庫概覽,  Prev: 錯誤和例外,  Up: Python 教學

2.9 Classes
===========

Classes provide a means of bundling data and functionality together.
Creating a new class creates a new `type' of object, allowing new
`instances' of that type to be made.  Each class instance can have
attributes attached to it for maintaining its state.  Class instances
can also have methods (defined by its class) for modifying its state.

Compared with other programming languages, Python’s class mechanism adds
classes with a minimum of new syntax and semantics.  It is a mixture of
the class mechanisms found in C++ and Modula-3.  Python classes provide
all the standard features of Object Oriented Programming: the class
inheritance mechanism allows multiple base classes, a derived class can
override any methods of its base class or classes, and a method can call
the method of a base class with the same name.  Objects can contain
arbitrary amounts and kinds of data.  As is true for modules, classes
partake of the dynamic nature of Python: they are created at runtime,
and can be modified further after creation.

In C++ terminology, normally class members (including the data members)
are `public' (except see below *note Private Variables: 12bf.), and all
member functions are `virtual'.  As in Modula-3, there are no shorthands
for referencing the object’s members from its methods: the method
function is declared with an explicit first argument representing the
object, which is provided implicitly by the call.  As in Smalltalk,
classes themselves are objects.  This provides semantics for importing
and renaming.  Unlike C++ and Modula-3, built-in types can be used as
base classes for extension by the user.  Also, like in C++, most
built-in operators with special syntax (arithmetic operators,
subscripting etc.)  can be redefined for class instances.

(Lacking universally accepted terminology to talk about classes, I will
make occasional use of Smalltalk and C++ terms.  I would use Modula-3
terms, since its object-oriented semantics are closer to those of Python
than C++, but I expect that few readers have heard of it.)

* Menu:

* A Word About Names and Objects::
* Python Scopes and Namespaces::
* A First Look at Classes::
* Random Remarks::
* Inheritance::
* Private Variables::
* Odds and Ends::
* Iterators::
* Generators::
* Generator Expressions::


File: python.info,  Node: A Word About Names and Objects,  Next: Python Scopes and Namespaces,  Up: Classes

2.9.1 A Word About Names and Objects
------------------------------------

Objects have individuality, and multiple names (in multiple scopes) can
be bound to the same object.  This is known as aliasing in other
languages.  This is usually not appreciated on a first glance at Python,
and can be safely ignored when dealing with immutable basic types
(numbers, strings, tuples).  However, aliasing has a possibly surprising
effect on the semantics of Python code involving mutable objects such as
lists, dictionaries, and most other types.  This is usually used to the
benefit of the program, since aliases behave like pointers in some
respects.  For example, passing an object is cheap since only a pointer
is passed by the implementation; and if a function modifies an object
passed as an argument, the caller will see the change — this eliminates
the need for two different argument passing mechanisms as in Pascal.


File: python.info,  Node: Python Scopes and Namespaces,  Next: A First Look at Classes,  Prev: A Word About Names and Objects,  Up: Classes

2.9.2 Python Scopes and Namespaces
----------------------------------

Before introducing classes, I first have to tell you something about
Python’s scope rules.  Class definitions play some neat tricks with
namespaces, and you need to know how scopes and namespaces work to fully
understand what’s going on.  Incidentally, knowledge about this subject
is useful for any advanced Python programmer.

Let’s begin with some definitions.

A `namespace' is a mapping from names to objects.  Most namespaces are
currently implemented as Python dictionaries, but that’s normally not
noticeable in any way (except for performance), and it may change in the
future.  Examples of namespaces are: the set of built-in names
(containing functions such as *note abs(): 12c4, and built-in exception
names); the global names in a module; and the local names in a function
invocation.  In a sense the set of attributes of an object also form a
namespace.  The important thing to know about namespaces is that there
is absolutely no relation between names in different namespaces; for
instance, two different modules may both define a function ‘maximize’
without confusion — users of the modules must prefix it with the module
name.

By the way, I use the word `attribute' for any name following a dot —
for example, in the expression ‘z.real’, ‘real’ is an attribute of the
object ‘z’.  Strictly speaking, references to names in modules are
attribute references: in the expression ‘modname.funcname’, ‘modname’ is
a module object and ‘funcname’ is an attribute of it.  In this case
there happens to be a straightforward mapping between the module’s
attributes and the global names defined in the module: they share the
same namespace!  (1)

Attributes may be read-only or writable.  In the latter case, assignment
to attributes is possible.  Module attributes are writable: you can
write ‘modname.the_answer = 42’.  Writable attributes may also be
deleted with the *note del: 1273. statement.  For example, ‘del
modname.the_answer’ will remove the attribute ‘the_answer’ from the
object named by ‘modname’.

Namespaces are created at different moments and have different
lifetimes.  The namespace containing the built-in names is created when
the Python interpreter starts up, and is never deleted.  The global
namespace for a module is created when the module definition is read in;
normally, module namespaces also last until the interpreter quits.  The
statements executed by the top-level invocation of the interpreter,
either read from a script file or interactively, are considered part of
a module called *note __main__: 1, so they have their own global
namespace.  (The built-in names actually also live in a module; this is
called *note builtins: 13.)

The local namespace for a function is created when the function is
called, and deleted when the function returns or raises an exception
that is not handled within the function.  (Actually, forgetting would be
a better way to describe what actually happens.)  Of course, recursive
invocations each have their own local namespace.

A `scope' is a textual region of a Python program where a namespace is
directly accessible.  "Directly accessible" here means that an
unqualified reference to a name attempts to find the name in the
namespace.

Although scopes are determined statically, they are used dynamically.
At any time during execution, there are 3 or 4 nested scopes whose
namespaces are directly accessible:

   * the innermost scope, which is searched first, contains the local
     names

   * the scopes of any enclosing functions, which are searched starting
     with the nearest enclosing scope, contains non-local, but also
     non-global names

   * the next-to-last scope contains the current module’s global names

   * the outermost scope (searched last) is the namespace containing
     built-in names

If a name is declared global, then all references and assignments go
directly to the middle scope containing the module’s global names.  To
rebind variables found outside of the innermost scope, the *note
nonlocal: c44. statement can be used; if not declared nonlocal, those
variables are read-only (an attempt to write to such a variable will
simply create a `new' local variable in the innermost scope, leaving the
identically named outer variable unchanged).

Usually, the local scope references the local names of the (textually)
current function.  Outside functions, the local scope references the
same namespace as the global scope: the module’s namespace.  Class
definitions place yet another namespace in the local scope.

It is important to realize that scopes are determined textually: the
global scope of a function defined in a module is that module’s
namespace, no matter from where or by what alias the function is called.
On the other hand, the actual search for names is done dynamically, at
run time — however, the language definition is evolving towards static
name resolution, at "compile" time, so don’t rely on dynamic name
resolution!  (In fact, local variables are already determined
statically.)

A special quirk of Python is that – if no *note global: 1249. or *note
nonlocal: c44. statement is in effect – assignments to names always go
into the innermost scope.  Assignments do not copy data — they just bind
names to objects.  The same is true for deletions: the statement ‘del x’
removes the binding of ‘x’ from the namespace referenced by the local
scope.  In fact, all operations that introduce new names use the local
scope: in particular, *note import: c22. statements and function
definitions bind the module or function name in the local scope.

The *note global: 1249. statement can be used to indicate that
particular variables live in the global scope and should be rebound
there; the *note nonlocal: c44. statement indicates that particular
variables live in an enclosing scope and should be rebound there.

* Menu:

* Scopes and Namespaces Example::

   ---------- Footnotes ----------

   (1) (1) Except for one thing.  Module objects have a secret read-only
attribute called *note __dict__: 501. which returns the dictionary used
to implement the module’s namespace; the name *note __dict__: 501. is an
attribute but not a global name.  Obviously, using this violates the
abstraction of namespace implementation, and should be restricted to
things like post-mortem debuggers.


File: python.info,  Node: Scopes and Namespaces Example,  Up: Python Scopes and Namespaces

2.9.2.1 Scopes and Namespaces Example
.....................................

This is an example demonstrating how to reference the different scopes
and namespaces, and how *note global: 1249. and *note nonlocal: c44.
affect variable binding:

     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)

The output of the example code is:

     After local assignment: test spam
     After nonlocal assignment: nonlocal spam
     After global assignment: nonlocal spam
     In global scope: global spam

Note how the `local' assignment (which is default) didn’t change
`scope_test'’s binding of `spam'.  The *note nonlocal: c44. assignment
changed `scope_test'’s binding of `spam', and the *note global: 1249.
assignment changed the module-level binding.

You can also see that there was no previous binding for `spam' before
the *note global: 1249. assignment.


File: python.info,  Node: A First Look at Classes,  Next: Random Remarks,  Prev: Python Scopes and Namespaces,  Up: Classes

2.9.3 A First Look at Classes
-----------------------------

Classes introduce a little bit of new syntax, three new object types,
and some new semantics.

* Menu:

* Class Definition Syntax::
* Class Objects::
* Instance Objects::
* Method Objects::
* Class and Instance Variables::


File: python.info,  Node: Class Definition Syntax,  Next: Class Objects,  Up: A First Look at Classes

2.9.3.1 Class Definition Syntax
...............................

The simplest form of class definition looks like this:

     class ClassName:
         <statement-1>
         .
         .
         .
         <statement-N>

Class definitions, like function definitions (*note def: dc3.
statements) must be executed before they have any effect.  (You could
conceivably place a class definition in a branch of an *note if: dec.
statement, or inside a function.)

In practice, the statements inside a class definition will usually be
function definitions, but other statements are allowed, and sometimes
useful — we’ll come back to this later.  The function definitions inside
a class normally have a peculiar form of argument list, dictated by the
calling conventions for methods — again, this is explained later.

When a class definition is entered, a new namespace is created, and used
as the local scope — thus, all assignments to local variables go into
this new namespace.  In particular, function definitions bind the name
of the new function here.

When a class definition is left normally (via the end), a `class object'
is created.  This is basically a wrapper around the contents of the
namespace created by the class definition; we’ll learn more about class
objects in the next section.  The original local scope (the one in
effect just before the class definition was entered) is reinstated, and
the class object is bound here to the class name given in the class
definition header (‘ClassName’ in the example).


File: python.info,  Node: Class Objects,  Next: Instance Objects,  Prev: Class Definition Syntax,  Up: A First Look at Classes

2.9.3.2 Class Objects
.....................

Class objects support two kinds of operations: attribute references and
instantiation.

`Attribute references' use the standard syntax used for all attribute
references in Python: ‘obj.name’.  Valid attribute names are all the
names that were in the class’s namespace when the class object was
created.  So, if the class definition looked like this:

     class MyClass:
         """A simple example class"""
         i = 12345

         def f(self):
             return 'hello world'

then ‘MyClass.i’ and ‘MyClass.f’ are valid attribute references,
returning an integer and a function object, respectively.  Class
attributes can also be assigned to, so you can change the value of
‘MyClass.i’ by assignment.  ‘__doc__’ is also a valid attribute,
returning the docstring belonging to the class: ‘"A simple example
class"’.

Class `instantiation' uses function notation.  Just pretend that the
class object is a parameterless function that returns a new instance of
the class.  For example (assuming the above class):

     x = MyClass()

creates a new `instance' of the class and assigns this object to the
local variable ‘x’.

The instantiation operation ("calling" a class object) creates an empty
object.  Many classes like to create objects with instances customized
to a specific initial state.  Therefore a class may define a special
method named *note __init__(): d63, like this:

     def __init__(self):
         self.data = []

When a class defines an *note __init__(): d63. method, class
instantiation automatically invokes *note __init__(): d63. for the
newly-created class instance.  So in this example, a new, initialized
instance can be obtained by:

     x = MyClass()

Of course, the *note __init__(): d63. method may have arguments for
greater flexibility.  In that case, arguments given to the class
instantiation operator are passed on to *note __init__(): d63.  For
example,

     >>> 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: Instance Objects,  Next: Method Objects,  Prev: Class Objects,  Up: A First Look at Classes

2.9.3.3 Instance Objects
........................

Now what can we do with instance objects?  The only operations
understood by instance objects are attribute references.  There are two
kinds of valid attribute names: data attributes and methods.

`data attributes' correspond to "instance variables" in Smalltalk, and
to "data members" in C++.  Data attributes need not be declared; like
local variables, they spring into existence when they are first assigned
to.  For example, if ‘x’ is the instance of ‘MyClass’ created above, the
following piece of code will print the value ‘16’, without leaving a
trace:

     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.  (In Python, the term method
is not unique to class instances: other object types can have methods as
well.  For example, list objects have methods called append, insert,
remove, sort, and so on.  However, in the following discussion, we’ll
use the term method exclusively to mean methods of class instance
objects, unless explicitly stated otherwise.)

Valid method names of an instance object depend on its class.  By
definition, all attributes of a class that are function objects define
corresponding methods of its instances.  So in our example, ‘x.f’ is a
valid method reference, since ‘MyClass.f’ is a function, but ‘x.i’ is
not, since ‘MyClass.i’ is not.  But ‘x.f’ is not the same thing as
‘MyClass.f’ — it is a `method object', not a function object.


File: python.info,  Node: Method Objects,  Next: Class and Instance Variables,  Prev: Instance Objects,  Up: A First Look at Classes

2.9.3.4 Method Objects
......................

Usually, a method is called right after it is bound:

     x.f()

In the ‘MyClass’ example, this will return the string ‘'hello world'’.
However, it is not necessary to call a method right away: ‘x.f’ is a
method object, and can be stored away and called at a later time.  For
example:

     xf = x.f
     while True:
         print(xf())

will continue to print ‘hello world’ until the end of time.

What exactly happens when a method is called?  You may have noticed that
‘x.f()’ was called without an argument above, even though the function
definition for ‘f()’ specified an argument.  What happened to the
argument?  Surely Python raises an exception when a function that
requires an argument is called without any — even if the argument isn’t
actually used...

Actually, you may have guessed the answer: the special thing about
methods is that the instance object is passed as the first argument of
the function.  In our example, the call ‘x.f()’ is exactly equivalent to
‘MyClass.f(x)’.  In general, calling a method with a list of `n'
arguments is equivalent to calling the corresponding function with an
argument list that is created by inserting the method’s instance object
before the first argument.

If you still don’t understand how methods work, a look at the
implementation can perhaps clarify matters.  When a non-data attribute
of an instance is referenced, the instance’s class is searched.  If the
name denotes a valid class attribute that is a function object, a method
object is created by packing (pointers to) the instance object and the
function object just found together in an abstract object: this is the
method object.  When the method object is called with an argument list,
a new argument list is constructed from the instance object and the
argument list, and the function object is called with this new argument
list.


File: python.info,  Node: Class and Instance Variables,  Prev: Method Objects,  Up: A First Look at Classes

2.9.3.5 Class and Instance Variables
....................................

Generally speaking, instance variables are for data unique to each
instance and class variables are for attributes and methods shared by
all instances of the class:

     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'

As discussed in *note A Word About Names and Objects: 12c1, shared data
can have possibly surprising effects with involving *note mutable: 122f.
objects such as lists and dictionaries.  For example, the `tricks' list
in the following code should not be used as a class variable because
just a single list would be shared by all `Dog' instances:

     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']

Correct design of the class should use an instance variable instead:

     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: Random Remarks,  Next: Inheritance,  Prev: A First Look at Classes,  Up: Classes

2.9.4 Random Remarks
--------------------

If the same attribute name occurs in both an instance and in a class,
then attribute lookup prioritizes the instance:

     >>> 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

Data attributes may be referenced by methods as well as by ordinary
users ("clients") of an object.  In other words, classes are not usable
to implement pure abstract data types.  In fact, nothing in Python makes
it possible to enforce data hiding — it is all based upon convention.
(On the other hand, the Python implementation, written in C, can
completely hide implementation details and control access to an object
if necessary; this can be used by extensions to Python written in C.)

Clients should use data attributes with care — clients may mess up
invariants maintained by the methods by stamping on their data
attributes.  Note that clients may add data attributes of their own to
an instance object without affecting the validity of the methods, as
long as name conflicts are avoided — again, a naming convention can save
a lot of headaches here.

There is no shorthand for referencing data attributes (or other
methods!)  from within methods.  I find that this actually increases the
readability of methods: there is no chance of confusing local variables
and instance variables when glancing through a method.

Often, the first argument of a method is called ‘self’.  This is nothing
more than a convention: the name ‘self’ has absolutely no special
meaning to Python.  Note, however, that by not following the convention
your code may be less readable to other Python programmers, and it is
also conceivable that a `class browser' program might be written that
relies upon such a convention.

Any function object that is a class attribute defines a method for
instances of that class.  It is not necessary that the function
definition is textually enclosed in the class definition: assigning a
function object to a local variable in the class is also ok.  For
example:

     # 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

Now ‘f’, ‘g’ and ‘h’ are all attributes of class ‘C’ that refer to
function objects, and consequently they are all methods of instances of
‘C’ — ‘h’ being exactly equivalent to ‘g’.  Note that this practice
usually only serves to confuse the reader of a program.

Methods may call other methods by using method attributes of the ‘self’
argument:

     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)

Methods may reference global names in the same way as ordinary
functions.  The global scope associated with a method is the module
containing its definition.  (A class is never used as a global scope.)
While one rarely encounters a good reason for using global data in a
method, there are many legitimate uses of the global scope: for one
thing, functions and modules imported into the global scope can be used
by methods, as well as functions and classes defined in it.  Usually,
the class containing the method is itself defined in this global scope,
and in the next section we’ll find some good reasons why a method would
want to reference its own class.

Each value is an object, and therefore has a `class' (also called its
`type').  It is stored as ‘object.__class__’.


File: python.info,  Node: Inheritance,  Next: Private Variables,  Prev: Random Remarks,  Up: Classes

2.9.5 Inheritance
-----------------

Of course, a language feature would not be worthy of the name "class"
without supporting inheritance.  The syntax for a derived class
definition looks like this:

     class DerivedClassName(BaseClassName):
         <statement-1>
         .
         .
         .
         <statement-N>

The name ‘BaseClassName’ must be defined in a scope containing the
derived class definition.  In place of a base class name, other
arbitrary expressions are also allowed.  This can be useful, for
example, when the base class is defined in another module:

     class DerivedClassName(modname.BaseClassName):

Execution of a derived class definition proceeds the same as for a base
class.  When the class object is constructed, the base class is
remembered.  This is used for resolving attribute references: if a
requested attribute is not found in the class, the search proceeds to
look in the base class.  This rule is applied recursively if the base
class itself is derived from some other class.

There’s nothing special about instantiation of derived classes:
‘DerivedClassName()’ creates a new instance of the class.  Method
references are resolved as follows: the corresponding class attribute is
searched, descending down the chain of base classes if necessary, and
the method reference is valid if this yields a function object.

Derived classes may override methods of their base classes.  Because
methods have no special privileges when calling other methods of the
same object, a method of a base class that calls another method defined
in the same base class may end up calling a method of a derived class
that overrides it.  (For C++ programmers: all methods in Python are
effectively ‘virtual’.)

An overriding method in a derived class may in fact want to extend
rather than simply replace the base class method of the same name.
There is a simple way to call the base class method directly: just call
‘BaseClassName.methodname(self, arguments)’.  This is occasionally
useful to clients as well.  (Note that this only works if the base class
is accessible as ‘BaseClassName’ in the global scope.)

Python has two built-in functions that work with inheritance:

   * Use *note isinstance(): 454. to check an instance’s type:
     ‘isinstance(obj, int)’ will be ‘True’ only if ‘obj.__class__’ is
     *note int: 185. or some class derived from *note int: 185.

   * Use *note issubclass(): 455. to check class inheritance:
     ‘issubclass(bool, int)’ is ‘True’ since *note bool: 184. is a
     subclass of *note int: 185.  However, ‘issubclass(float, int)’ is
     ‘False’ since *note float: 188. is not a subclass of *note int:
     185.

* Menu:

* Multiple Inheritance::


File: python.info,  Node: Multiple Inheritance,  Up: Inheritance

2.9.5.1 Multiple Inheritance
............................

Python supports a form of multiple inheritance as well.  A class
definition with multiple base classes looks like this:

     class DerivedClassName(Base1, Base2, Base3):
         <statement-1>
         .
         .
         .
         <statement-N>

For most purposes, in the simplest cases, you can think of the search
for attributes inherited from a parent class as depth-first,
left-to-right, not searching twice in the same class where there is an
overlap in the hierarchy.  Thus, if an attribute is not found in
‘DerivedClassName’, it is searched for in ‘Base1’, then (recursively) in
the base classes of ‘Base1’, and if it was not found there, it was
searched for in ‘Base2’, and so on.

In fact, it is slightly more complex than that; the method resolution
order changes dynamically to support cooperative calls to *note super():
4e7.  This approach is known in some other multiple-inheritance
languages as call-next-method and is more powerful than the super call
found in single-inheritance languages.

Dynamic ordering is necessary because all cases of multiple inheritance
exhibit one or more diamond relationships (where at least one of the
parent classes can be accessed through multiple paths from the
bottommost class).  For example, all classes inherit from *note object:
2b1, so any case of multiple inheritance provides more than one path to
reach *note object: 2b1.  To keep the base classes from being accessed
more than once, the dynamic algorithm linearizes the search order in a
way that preserves the left-to-right ordering specified in each class,
that calls each parent only once, and that is monotonic (meaning that a
class can be subclassed without affecting the precedence order of its
parents).  Taken together, these properties make it possible to design
reliable and extensible classes with multiple inheritance.  For more
detail, see ‘https://www.python.org/download/releases/2.3/mro/’.


File: python.info,  Node: Private Variables,  Next: Odds and Ends,  Prev: Inheritance,  Up: Classes

2.9.6 Private Variables
-----------------------

"Private" instance variables that cannot be accessed except from inside
an object don’t exist in Python.  However, there is a convention that is
followed by most Python code: a name prefixed with an underscore (e.g.
‘_spam’) should be treated as a non-public part of the API (whether it
is a function, a method or a data member).  It should be considered an
implementation detail and subject to change without notice.

Since there is a valid use-case for class-private members (namely to
avoid name clashes of names with names defined by subclasses), there is
limited support for such a mechanism, called `name mangling'.  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
leading underscore(s) stripped.  This mangling is done without regard to
the syntactic position of the identifier, as long as it occurs within
the definition of a class.

Name mangling is helpful for letting subclasses override methods without
breaking intraclass method calls.  For example:

     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)

The above example would work even if ‘MappingSubclass’ were to introduce
a ‘__update’ identifier since it is replaced with ‘_Mapping__update’ in
the ‘Mapping’ class and ‘_MappingSubclass__update’ in the
‘MappingSubclass’ class respectively.

Note that the mangling rules are designed mostly to avoid accidents; it
still is possible to access or modify a variable that is considered
private.  This can even be useful in special circumstances, such as in
the debugger.

Notice that code passed to ‘exec()’ or ‘eval()’ does not consider the
classname of the invoking class to be the current class; this is similar
to the effect of the ‘global’ statement, the effect of which is likewise
restricted to code that is byte-compiled together.  The same restriction
applies to ‘getattr()’, ‘setattr()’ and ‘delattr()’, as well as when
referencing ‘__dict__’ directly.


File: python.info,  Node: Odds and Ends,  Next: Iterators,  Prev: Private Variables,  Up: Classes

2.9.7 Odds and Ends
-------------------

Sometimes it is useful to have a data type similar to the Pascal
"record" or C "struct", bundling together a few named data items.  An
empty class definition will do nicely:

     class Employee:
         pass

     john = Employee()  # Create an empty employee record

     # Fill the fields of the record
     john.name = 'John Doe'
     john.dept = 'computer lab'
     john.salary = 1000

A piece of Python code that expects a particular abstract data type can
often be passed a class that emulates the methods of that data type
instead.  For instance, if you have a function that formats some data
from a file object, you can define a class with methods ‘read()’ and
‘readline()’ that get the data from a string buffer instead, and pass it
as an argument.

Instance method objects have attributes, too: ‘m.__self__’ is the
instance object with the method ‘m()’, and ‘m.__func__’ is the function
object corresponding to the method.


File: python.info,  Node: Iterators,  Next: Generators,  Prev: Odds and Ends,  Up: Classes

2.9.8 Iterators
---------------

By now you have probably noticed that most container objects can be
looped over using a *note for: c35. statement:

     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='')

This style of access is clear, concise, and convenient.  The use of
iterators pervades and unifies Python.  Behind the scenes, the *note
for: c35. statement calls *note iter(): d2c. on the container object.
The function returns an iterator object that defines the method *note
__next__(): c69. which accesses elements in the container one at a time.
When there are no more elements, *note __next__(): c69. raises a *note
StopIteration: 48b. exception which tells the ‘for’ loop to terminate.
You can call the *note __next__(): c69. method using the *note next():
687. built-in function; this example shows how it all works:

     >>> s = 'abc'
     >>> it = iter(s)
     >>> it
     <iterator object at 0x00A1DB50>
     >>> 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

Having seen the mechanics behind the iterator protocol, it is easy to
add iterator behavior to your classes.  Define an *note __iter__(): 514.
method which returns an object with a *note __next__(): c69. method.  If
the class defines ‘__next__()’, then *note __iter__(): 514. can just
return ‘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: Generators,  Next: Generator Expressions,  Prev: Iterators,  Up: Classes

2.9.9 Generators
----------------

*note Generators: 9a7. are a simple and powerful tool for creating
iterators.  They are written like regular functions but use the *note
yield: 190. statement whenever they want to return data.  Each time
*note next(): 687. is called on it, the generator resumes where it left
off (it remembers all the data values and which statement was last
executed).  An example shows that generators can be trivially easy to
create:

     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

Anything that can be done with generators can also be done with
class-based iterators as described in the previous section.  What makes
generators so compact is that the *note __iter__(): 514. and *note
__next__(): 12df. methods are created automatically.

Another key feature is that the local variables and execution state are
automatically saved between calls.  This made the function easier to
write and much more clear than an approach using instance variables like
‘self.index’ and ‘self.data’.

In addition to automatic method creation and saving program state, when
generators terminate, they automatically raise *note StopIteration: 48b.
In combination, these features make it easy to create iterators with no
more effort than writing a regular function.


File: python.info,  Node: Generator Expressions,  Prev: Generators,  Up: Classes

2.9.10 Generator Expressions
----------------------------

Some simple generators can be coded succinctly as expressions using a
syntax similar to list comprehensions but with parentheses instead of
square brackets.  These expressions are designed for situations where
the generator is used right away by an enclosing function.  Generator
expressions are more compact but less versatile than full generator
definitions and tend to be more memory friendly than equivalent list
comprehensions.

Examples:

     >>> 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: Brief Tour of the Standard Library --- Part II,  Prev: Classes,  Up: Python 教學

2.10 Python 標準函式庫概覽
==========================

* Menu:

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


File: python.info,  Node: 作業系統介面,  Next: 檔案之萬用字元,  Up: Python 標準函式庫概覽

2.10.1 作業系統介面
-------------------

*note os: c5. 模組提供了數十個與作業系統溝通的函式：

     >>> import os
     >>> os.getcwd()      # Return the current working directory
     'C:\\Python38'
     >>> 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(): 66a. 覆蓋內建函式 *note open(): 4f5.。

在使用 *note os: c5. 諸如此類大型模組時搭配內建函式 *note dir(): d38. 和
*note help(): 577. 是非常有用的:

     >>> 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: ea. 模組提供了更容易使用的高
階介面：

     >>> import shutil
     >>> shutil.copyfile('data.db', 'archive.db')
     'archive.db'
     >>> shutil.move('/build/executables', 'installdir')
     'installdir'


File: python.info,  Node: 檔案之萬用字元,  Next: 命令列引數,  Prev: 作業系統介面,  Up: Python 標準函式庫概覽

2.10.2 檔案之萬用字元
---------------------

The *note glob: 8a. module provides a function for making file lists
from directory wildcard searches:

     >>> import glob
     >>> glob.glob('*.py')
     ['primes.py', 'random.py', 'quote.py']


File: python.info,  Node: 命令列引數,  Next: 錯誤輸出重新導向與程式終止,  Prev: 檔案之萬用字元,  Up: Python 標準函式庫概覽

2.10.3 命令列引數
-----------------

通用工具腳本常需要處理命令列引數。這些引數會以串列形式存放在 *note sys:
fe. 模組的 `argv' 此變數中。例如在命令列執行 ‘python demo.py one two
three’ 會有以下輸出結果:

     >>> import sys
     >>> print(sys.argv)
     ['demo.py', 'one', 'two', 'three']

The *note argparse: 6. module provides a more sophisticated mechanism to
process command line arguments.  The following script extracts one or
more filenames and an optional number of lines to be displayed:

     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)

When run at the command line with ‘python top.py --lines=5 alpha.txt
beta.txt’, the script sets ‘args.lines’ to ‘5’ and ‘args.filenames’ to
‘['alpha.txt', 'beta.txt']’.


File: python.info,  Node: 錯誤輸出重新導向與程式終止,  Next: 字串樣式比對,  Prev: 命令列引數,  Up: Python 標準函式庫概覽

2.10.4 錯誤輸出重新導向與程式終止
---------------------------------

*note sys: fe. 模組也有 `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: de. 模組提供正規表示式 (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'

當只需要簡單的字串操作時，因為可讀性以及方便除錯，字串本身的方法是比較建
議的。

     >>> 'tea for too'.replace('too', 'two')
     'tea for two'


File: python.info,  Node: 數學相關,  Next: 網路存取,  Prev: 字串樣式比對,  Up: Python 標準函式庫概覽

2.10.6 數學相關
---------------

*note math: b2. 模組提供了 C 函式庫中底層的浮點數運算的函式。

     >>> import math
     >>> math.cos(math.pi / 4)
     0.70710678118654757
     >>> math.log(1024, 2)
     10.0

*note random: dd. 模組提供了隨機選擇的工具。

     >>> 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
     0.17970987693706186
     >>> random.randrange(6)    # random integer chosen from range(6)
     4

*note statistics: f6. 模組提供了替數值資料計算基本統計量（包括平均、中位
數、變異量數等）的功能。

     >>> 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: 121. 模組可以從網址抓取資料以及 *note smtplib: ee. 可以
用來寄郵件。:

     >>> from urllib.request import urlopen
     >>> with urlopen('http://tycho.usno.navy.mil/cgi-bin/timer.pl') as response:
     ...     for line in response:
     ...         line = line.decode('utf-8')  # Decoding the binary data to text.
     ...         if 'EST' in line or 'EDT' in line:  # look for Eastern Time
     ...             print(line)

     <BR>Nov. 25, 09:43:32 PM EST

     >>> 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: 31. 模組中有許多類別供以操作日期以及時間，從簡單從複雜都
有。模組支援日期與時間的運算，而實作的重點是有效率的成員擷取以達到輸出格
式化以及操作。模組也提供支援時區換算的類別。

     >>> # 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: 145. ， *note
gzip: 8c. ， *note bz2: 14.， *note lzma: ae. ，*note zipfile: 143. 以及
*note tarfile: 102. 。

     >>> 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: 10c. 模組可以迅速地展示效能的進步。

     >>> 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: 10c. 模組提供這麼細的粒度，*note profile: d4. 模組
以及 *note pstats: d5. 模組則提供了一些在大型的程式碼識別關鍵臨界區間（
Critical Section）的工具。


File: python.info,  Node: 品質控管,  Next: 標準模組庫,  Prev: 效能量測,  Up: Python 標準函式庫概覽

2.10.11 品質控管
----------------

達到高品質軟體的一個方法當開發時對每個函式寫測試以及在開發過程中要不斷的
跑這些測試。

*note doctest: 67. 模組提供了一個工具， 掃描模組並根據程式中內嵌的文件字
符串執行測試。測試構造如同簡單的將它的輸出結果剪下並貼上到文件字符串中。
通過用戶提供的例子， 它強化了文件， 允許 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: 11c. 模組不像 *note doctest: 67. 模組這般容易， 但是它提
供了更完整的測試集並且可以整合在不同的檔案間。

     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: 140. 和 *note xmlrpc.server: 141. 模組實
     現遠端控制看似變更為容易。 使用前也不需要先了解相關知識或是掌握 XML
     的技能就能直接透過名稱使用模組。

   * 函式庫 *note email: 69. 套件用來管理 MIME 和其他 RFC 2822(1) 相關電
     子郵件訊息的文件。 相異於其他電子郵件套件 *note smtplib: ee. 和
     *note poplib: d1. 這些實際用來發送與接收訊息， 擁有更完整的工具設置
     提供建置與解析複雜訊息的結構（包含附件檔案）和實現網路傳送之間的解
     碼與標頭協定。

   * 函式庫 *note json: a5. 套件提供 JSON 資料解析強大的交換格式。 *note
     csv: 2a. 模組則提供直接讀寫以逗號分隔值的檔案格式，支援一般資料庫與
     電子表格。 *note xml.etree.ElementTree: 138. ， *note xml.dom: 135.
     與 *note xml.sax: 13c. 套件則支援 XML 流程。 綜觀所有， 這些模組和
     套件都簡化了 Python 應用程式與其他工具之間的資料交換。

   * ‘sqllite3’ 套件作為包覆 SQLite 資料庫的函式庫， 提供一個一致性的資
     料庫用來更新與操作使用些微非標準的 SQL 語法。

   * 有數種支援國際化模組 *note gettext: 89.，*note locale: aa.，和
     *note codecs: 1c. 等套件。

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2822.html


File: python.info,  Node: Brief Tour of the Standard Library --- Part II,  Next: 虛擬環境與套件,  Prev: Python 標準函式庫概覽,  Up: Python 教學

2.11 Brief Tour of the Standard Library — Part II
=================================================

第二部分涵蓋更多支援專業程式設計所需要的進階模組。這些模組很少出現在小腳
本中。

* Menu:

* Output Formatting::
* Templating::
* Working with Binary Data Record Layouts::
* Multi-threading: Multi-threading<2>.
* Logging::
* Weak References::
* Tools for Working with Lists::
* Decimal Floating Point Arithmetic::


File: python.info,  Node: Output Formatting,  Next: Templating,  Up: Brief Tour of the Standard Library --- Part II

2.11.1 Output Formatting
------------------------

The *note reprlib: e0. module provides a version of *note repr(): 7d1.
customized for abbreviated displays of large or deeply nested
containers:

     >>> import reprlib
     >>> reprlib.repr(set('supercalifragilisticexpialidocious'))
     "{'a', 'c', 'd', 'e', 'f', 'g', ...}"

The *note pprint: d3. module offers more sophisticated control over
printing both built-in and user defined objects in a way that is
readable by the interpreter.  When the result is longer than one line,
the "pretty printer" adds line breaks and indentation to more clearly
reveal data structure:

     >>> import pprint
     >>> t = [[[['black', 'cyan'], 'white', ['green', 'red']], [['magenta',
     ...     'yellow'], 'blue']]]
     ...
     >>> pprint.pprint(t, width=30)
     [[[['black', 'cyan'],
        'white',
        ['green', 'red']],
       [['magenta', 'yellow'],
        'blue']]]

The *note textwrap: 109. module formats paragraphs of text to fit a
given screen width:

     >>> 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.

The *note locale: aa. module accesses a database of culture specific
data formats.  The grouping attribute of locale’s format function
provides a direct way of formatting numbers with group separators:

     >>> 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("%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: Working with Binary Data Record Layouts,  Prev: Output Formatting,  Up: Brief Tour of the Standard Library --- Part II

2.11.2 Templating
-----------------

The *note string: f7. module includes a versatile *note Template: 3f0.
class with a simplified syntax suitable for editing by end-users.  This
allows users to customize their applications without having to alter the
application.

The format uses placeholder names formed by ‘$’ with valid Python
identifiers (alphanumeric characters and underscores).  Surrounding the
placeholder with braces allows it to be followed by more alphanumeric
letters with no intervening spaces.  Writing ‘$$’ creates a single
escaped ‘$’:

     >>> 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.'

The *note substitute(): 1304. method raises a *note KeyError: 2c8. when
a placeholder is not supplied in a dictionary or a keyword argument.
For mail-merge style applications, user supplied data may be incomplete
and the *note safe_substitute(): 1305. method may be more appropriate —
it will leave placeholders unchanged if data is missing:

     >>> 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 subclasses can specify a custom delimiter.  For example, a
batch renaming utility for a photo browser may elect to use percent
signs for placeholders such as the current date, image sequence number,
or file format:

     >>> 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

Another application for templating is separating program logic from the
details of multiple output formats.  This makes it possible to
substitute custom templates for XML files, plain text reports, and HTML
web reports.


File: python.info,  Node: Working with Binary Data Record Layouts,  Next: Multi-threading<2>,  Prev: Templating,  Up: Brief Tour of the Standard Library --- Part II

2.11.3 Working with Binary Data Record Layouts
----------------------------------------------

The *note struct: f9. module provides *note pack(): c10. and *note
unpack(): 1308. functions for working with variable length binary record
formats.  The following example shows how to loop through header
information in a ZIP file without using the *note zipfile: 143. module.
Pack codes ‘"H"’ and ‘"I"’ represent two and four byte unsigned numbers
respectively.  The ‘"<"’ indicates that they are standard size and in
little-endian byte order:

     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<2>,  Next: Logging,  Prev: Working with Binary Data Record Layouts,  Up: Brief Tour of the Standard Library --- Part II

2.11.4 Multi-threading
----------------------

Threading is a technique for decoupling tasks which are not sequentially
dependent.  Threads can be used to improve the responsiveness of
applications that accept user input while other tasks run in the
background.  A related use case is running I/O in parallel with
computations in another thread.

The following code shows how the high level *note threading: 10a. module
can run tasks in background while the main program continues to run:

     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()    # Wait for the background task to finish
     print('Main program waited until background was done.')

The principal challenge of multi-threaded applications is coordinating
threads that share data or other resources.  To that end, the threading
module provides a number of synchronization primitives including locks,
events, condition variables, and semaphores.

While those tools are powerful, minor design errors can result in
problems that are difficult to reproduce.  So, the preferred approach to
task coordination is to concentrate all access to a resource in a single
thread and then use the *note queue: db. module to feed that thread with
requests from other threads.  Applications using *note Queue: d1d.
objects for inter-thread communication and coordination are easier to
design, more readable, and more reliable.


File: python.info,  Node: Logging,  Next: Weak References,  Prev: Multi-threading<2>,  Up: Brief Tour of the Standard Library --- Part II

2.11.5 Logging
--------------

The *note logging: ab. module offers a full featured and flexible
logging system.  At its simplest, log messages are sent to a file or to
‘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')

This produces the following output:

     WARNING:root:Warning:config file server.conf not found
     ERROR:root:Error occurred
     CRITICAL:root:Critical error -- shutting down

By default, informational and debugging messages are suppressed and the
output is sent to standard error.  Other output options include routing
messages through email, datagrams, sockets, or to an HTTP Server.  New
filters can select different routing based on message priority: ‘DEBUG’,
‘INFO’, ‘WARNING’, ‘ERROR’, and ‘CRITICAL’.

The logging system can be configured directly from Python or can be
loaded from a user editable configuration file for customized logging
without altering the application.


File: python.info,  Node: Weak References,  Next: Tools for Working with Lists,  Prev: Logging,  Up: Brief Tour of the Standard Library --- Part II

2.11.6 Weak References
----------------------

Python does automatic memory management (reference counting for most
objects and *note garbage collection: ecd. to eliminate cycles).  The
memory is freed shortly after the last reference to it has been
eliminated.

This approach works fine for most applications but occasionally there is
a need to track objects only as long as they are being used by something
else.  Unfortunately, just tracking them creates a reference that makes
them permanent.  The *note weakref: 129. module provides tools for
tracking objects without creating a reference.  When the object is no
longer needed, it is automatically removed from a weakref table and a
callback is triggered for weakref objects.  Typical applications include
caching objects that are expensive to create:

     >>> 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:/python38/lib/weakref.py", line 46, in __getitem__
         o = self.data[key]()
     KeyError: 'primary'


File: python.info,  Node: Tools for Working with Lists,  Next: Decimal Floating Point Arithmetic,  Prev: Weak References,  Up: Brief Tour of the Standard Library --- Part II

2.11.7 Tools for Working with Lists
-----------------------------------

Many data structure needs can be met with the built-in list type.
However, sometimes there is a need for alternative implementations with
different performance trade-offs.

The *note array: 7. module provides an *note array(): 456. object that
is like a list that stores only homogeneous data and stores it more
compactly.  The following example shows an array of numbers stored as
two byte unsigned binary numbers (typecode ‘"H"’) rather than the usual
16 bytes per entry for regular lists of Python int objects:

     >>> from array import array
     >>> a = array('H', [4000, 10, 700, 22222])
     >>> sum(a)
     26932
     >>> a[1:3]
     array('H', [10, 700])

The *note collections: 1e. module provides a *note deque(): 536. object
that is like a list with faster appends and pops from the left side but
slower lookups in the middle.  These objects are well suited for
implementing queues and breadth first tree searches:

     >>> 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)

In addition to alternative list implementations, the library also offers
other tools such as the *note bisect: 12. module with functions for
manipulating sorted lists:

     >>> 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')]

The *note heapq: 8e. module provides functions for implementing heaps
based on regular lists.  The lowest valued entry is always kept at
position zero.  This is useful for applications which repeatedly access
the smallest element but do not want to run a full list sort:

     >>> 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: Tools for Working with Lists,  Up: Brief Tour of the Standard Library --- Part II

2.11.8 Decimal Floating Point Arithmetic
----------------------------------------

The *note decimal: 36. module offers a *note Decimal: 189. datatype for
decimal floating point arithmetic.  Compared to the built-in *note
float: 188. implementation of binary floating point, the class is
especially helpful for

   * financial applications and other uses which require exact decimal
     representation,

   * control over precision,

   * control over rounding to meet legal or regulatory requirements,

   * tracking of significant decimal places, or

   * applications where the user expects the results to match
     calculations done by hand.

For example, calculating a 5% tax on a 70 cent phone charge gives
different results in decimal floating point and binary floating point.
The difference becomes significant if the results are rounded to the
nearest cent:

     >>> from decimal import *
     >>> round(Decimal('0.70') * Decimal('1.05'), 2)
     Decimal('0.74')
     >>> round(.70 * 1.05, 2)
     0.73

The *note Decimal: 189. result keeps a trailing zero, automatically
inferring four place significance from multiplicands with two place
significance.  Decimal reproduces mathematics as done by hand and avoids
issues that can arise when binary floating point cannot exactly
represent decimal quantities.

Exact representation enables the *note Decimal: 189. class to perform
modulo calculations and equality tests that are unsuitable for binary
floating point:

     >>> Decimal('1.00') % Decimal('.10')
     Decimal('0.00')
     >>> 1.00 % 0.10
     0.09999999999999995

     >>> sum([Decimal('0.1')]*10) == Decimal('1.0')
     True
     >>> sum([0.1]*10) == 1.0
     False

The *note decimal: 36. module provides arithmetic with as much precision
as needed:

     >>> getcontext().prec = 36
     >>> Decimal(1) / Decimal(7)
     Decimal('0.142857142857142857142857142857142857')


File: python.info,  Node: 虛擬環境與套件,  Next: 現在可以來學習些什麼？,  Prev: Brief Tour of the Standard Library --- Part II,  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）: 1317.，這是一個
獨立的資料夾，並且裡面裝好了特定版本的 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: 126.。*note venv: 126. 通常
會安裝你能夠取得的最新版本的 Python。要是你的系統有不同版本的 Python，你
可以透過 ‘python3’ 這個指令選擇特定或是任意版本的 Python。

在建立虛擬環境的時候，在你決定要放該虛擬環境的資料夾之後，在 script 中執
行 *note venv: 126. 模組並且給定資料夾 path：

     python3 -m venv tutorial-env

如果 ‘tutorial-env’ 不存在的話，這會建立 ‘tutorial-env’ 資料夾，並且也會
在裡面建立一個有 Python 直譯器的複本、標準函式庫、以及不同的支援檔案的資
料夾。

A common directory location for a virtual environment is ‘.venv’.  This
name keeps the directory typically hidden in your shell and thus out of
the way while giving it a name that explains why the directory exists.
It also prevents clashing with ‘.env’ environment variable definition
files that some tooling supports.

一旦你建立了一個虛擬環境，你可以啟動他。

在 Windows 系統中，使用：

     tutorial-env\Scripts\activate.bat

在 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']
     >>>


File: python.info,  Node: 用 pip 管理套件,  Prev: 建立虛擬環境,  Up: 虛擬環境與套件

2.12.3 用 pip 管理套件
----------------------

You can install, upgrade, and remove packages using a program called
‘pip’.  By default ‘pip’ will install packages from the Python Package
Index, <‘https://pypi.org’>.  You can browse the Python Package Index by
going to it in your web browser.

‘pip’ has a number of subcommands: "install", "uninstall", "freeze",
etc.  (Consult the *note 安裝 Python 模組: 7fa. guide for complete
documentation for ‘pip’.)

你可以透過指定套件名字來安裝最新版本的套件：

     (tutorial-env) $ 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) $ 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’ 會知道該版本已經安裝過，然後什麼也不做。你可
以提供不同的版本號碼來取得該版本，或是可以執行 ‘pip install --upgrade’ 來
把套件升級到最新的版本：

     (tutorial-env) $ 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

‘pip uninstall’ 後面接一個或是多個套件名稱可以從虛擬環境中移除套件。

‘pip show’ 可以顯示一個特定套件的資訊：

     (tutorial-env) $ 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:

‘pip list’ 會顯示虛擬環境中所有已經安裝的套件：

     (tutorial-env) $ pip list
     novas (3.1.1.3)
     numpy (1.9.2)
     pip (7.0.3)
     requests (2.7.0)
     setuptools (16.0)

‘pip freeze’ 可以複製一整個已經安裝的套件清單，但是輸出使用 ‘pip
install’ 可以讀懂的格式。一個常見的慣例是放這整個清單到一個叫做
‘requirements.txt’ 的檔案：

     (tutorial-env) $ 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) $ 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 模組: 7fa.說明書來取得完整
的 ‘pip’ 參考資料。當你撰寫了一個套件並且想要讓它可以在 Python Package
Index 上可以取得的話，可以參考*note 發布 Python 模組: 7fb.說明。


File: python.info,  Node: 現在可以來學習些什麼？,  Next: Interactive Input Editing and History Substitution,  Prev: 虛擬環境與套件,  Up: Python 教學

2.13 現在可以來學習些什麼？
===========================

閱讀本教學可能增強您對於使用 Python 的興趣 — 您應該非常渴望使用 Python 來
解決在現實生活中所遭遇的問題。該從哪裡學習更多呢？

本教學是 Python 文件中的一部分。這份文件集裡頭的其他文件包含：

   * *note Python 標準函式庫 (Standard Library): 1200.：

     你該好好的瀏覽這份手冊，它提供了完整的（但簡潔）參考素材像是型別、
     函式與標準函式庫裡的模組。標準的 Python 發行版本會包含`大量'的附加
     程式碼。有些模組可以讀取 Unix 信箱、通過 HTTP 來檢索文件、產生亂數
     、分析命令列選項、編寫 CGI 程式、壓縮資料、及許多其他任務。瀏覽函式
     庫參考手冊可以讓你了解有哪些模組可以用。

   * *note 安裝 Python 模組: 7fa.：說明與解釋如何安裝其他 Python 使用者
     所編寫的模組。

   * *note The Python Language Reference: 1201.：Python 語法以及語意的詳
     細說明。這份文件閱讀起來會有些吃力，但作為一個語言本身的完整指南是
     非常有用的。

更多 Python 的資源：

   * ‘https://www.python.org’：Python 的主要網站。它包含程式碼、文件以及
     連結到 Python 相關聯的網頁。網站為鏡像的並設置於世界各地，像是歐洲
     、日本以及澳大利亞；鏡像網站也許會比主網站來得更快，不過具體速度則
     還是取決於你所在的地理位置。

   * ‘https://docs.python.org’：快速訪問 Python 的文件。

   * ‘https://pypi.org’: The Python Package Index, previously also
     nicknamed the Cheese Shop (1), is an index of user-created Python
     modules that are available for download.  Once you begin releasing
     code, you can register it here so that others can find it.

   * ‘https://code.activestate.com/recipes/langs/python/’：Python
     Cookbook 是一個相當大的程式碼範例集，大量的模組以及有用的腳本。一些
     值得注意與特別貢獻則被收集在一本名為 Python Cookbook (O’Reilly &
     Associates, ISBN 0-596-00797-3.) 的書籍中。

   * ‘http://www.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 常見問題: 131d.（也被稱 FAQ）這個清
單內。FAQ 會回答出現很多次的問題及解答，有很多問題甚至已經包含解決問題的
方法。

   ---------- Footnotes ----------

   (1) (1) "Cheese Shop" is a Monty Python’s sketch: a customer enters a
cheese shop, but whatever cheese he asks for, the clerk says it’s
missing.


File: python.info,  Node: Interactive Input Editing and History Substitution,  Next: 浮點數運算：問題與限制,  Prev: 現在可以來學習些什麼？,  Up: Python 教學

2.14 Interactive Input Editing and History Substitution
=======================================================

Some versions of the Python interpreter support editing of the current
input line and history substitution, similar to facilities found in the
Korn shell and the GNU Bash shell.  This is implemented using the GNU
Readline(1) library, which supports various styles of editing.  This
library has its own documentation which we won’t duplicate here.

* Menu:

* Tab Completion and History Editing::
* Alternatives to the Interactive Interpreter::

   ---------- Footnotes ----------

   (1) https://tiswww.case.edu/php/chet/readline/rltop.html


File: python.info,  Node: Tab Completion and History Editing,  Next: Alternatives to the Interactive Interpreter,  Up: Interactive Input Editing and History Substitution

2.14.1 Tab Completion and History Editing
-----------------------------------------

Completion of variable and module names is *note automatically enabled:
8eb. at interpreter startup so that the ‘Tab’ key invokes the completion
function; it looks at Python statement names, the current local
variables, and the available module names.  For dotted expressions such
as ‘string.a’, it will evaluate the expression up to the final ‘'.'’ and
then suggest completions from the attributes of the resulting object.
Note that this may execute application-defined code if an object with a
*note __getattr__(): 31f. method is part of the expression.  The default
configuration also saves your history into a file named
‘.python_history’ in your user directory.  The history will be available
again during the next interactive interpreter session.


File: python.info,  Node: Alternatives to the Interactive Interpreter,  Prev: Tab Completion and History Editing,  Up: Interactive Input Editing and History Substitution

2.14.2 Alternatives to the Interactive Interpreter
--------------------------------------------------

This facility is an enormous step forward compared to earlier versions
of the interpreter; however, some wishes are left: It would be nice if
the proper indentation were suggested on continuation lines (the parser
knows if an indent token is required next).  The completion mechanism
might use the interpreter’s symbol table.  A command to check (or even
suggest) matching parentheses, quotes, etc., would also be useful.

One alternative enhanced interactive interpreter that has been around
for quite some time is IPython(1), which features tab completion, object
exploration and advanced history management.  It can also be thoroughly
customized and embedded into other applications.  Another similar
enhanced interactive environment is bpython(2).

   ---------- Footnotes ----------

   (1) https://ipython.org/

   (2) https://www.bpython-interpreter.org/


File: python.info,  Node: 浮點數運算：問題與限制,  Next: 附錄,  Prev: Interactive Input Editing and History Substitution,  Up: Python 教學

2.15 浮點數運算：問題與限制
===========================

在計算機架構中，浮點數透過二進位小數表示。例如說，在十進位小數中：

     0.125

可被分為 1/10 + 2/100 + 5/1000，同樣的道理，二進位小數 ：

     0.001

可被分為 0/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(): 7d1. 函式會選
擇上段說明中有 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：

     >>> .1 + .1 + .1 == .3
     False

同時，因為 0.1 不能再更接近精準的 1/10，還有 0.3 不能再更接近精準的
3/10，預先用 *note round(): c72. 函式捨入並不會有幫助：

     >>> round(.1, 1) + round(.1, 1) + round(.1, 1) == round(.3, 1)
     False

雖然數字不會再更接近他們的精準數值，但 *note round(): c72. 函式可以對事
後的捨入有所幫助，如此一來，不精確的數值就變得可以互相比較：

     >>> round(.1 + .1 + .1, 10) == round(.3, 10)
     True

二進位浮點數架構擁有很多這樣的驚喜。底下的「表示法錯誤」章節，詳細的解釋
了「0.1」的問題。如果想要其他常見驚喜更完整的描述，可以參考 The Perils
of Floating Point（浮點數的風險）(1)。

As that says near the end, "there are no easy answers."  Still, don’t be
unduly wary of floating-point!  The errors in Python float operations
are inherited from the floating-point hardware, and on most machines are
on the order of no more than 1 part in 2**53 per operation.  That’s more
than adequate for most tasks, but you do need to keep in mind that it’s
not decimal arithmetic and that every float operation can suffer a new
rounding error.

While pathological cases do exist, for most casual use of floating-point
arithmetic you’ll see the result you expect in the end if you simply
round the display of your final results to the number of decimal digits
you expect.  *note str(): 335. usually suffices, and for finer control
see the *note str.format(): 4df. method’s format specifiers in *note
Format String Syntax: d1f.

For use cases which require exact decimal representation, try using the
*note decimal: 36. module which implements decimal arithmetic suitable
for accounting applications and high-precision applications.

Another form of exact arithmetic is supported by the *note fractions:
83. module which implements arithmetic based on rational numbers (so the
numbers like 1/3 can be represented exactly).

If you are a heavy user of floating point operations you should take a
look at the Numerical Python package and many other packages for
mathematical and statistical operations supplied by the SciPy project.
See <‘https://scipy.org’>.

Python provides tools that may help on those rare occasions when you
really `do' want to know the exact value of a float.  The *note
float.as_integer_ratio(): 1328. method expresses the value of a float as
a fraction:

     >>> x = 3.14159
     >>> x.as_integer_ratio()
     (3537115888337719, 1125899906842624)

Since the ratio is exact, it can be used to losslessly recreate the
original value:

     >>> x == 3537115888337719 / 1125899906842624
     True

The *note float.hex(): 1329. method expresses a float in hexadecimal
(base 16), again giving the exact value stored by your computer:

     >>> x.hex()
     '0x1.921f9f01b866ep+1'

This precise hexadecimal representation can be used to reconstruct the
float value exactly:

     >>> x == float.fromhex('0x1.921f9f01b866ep+1')
     True

Since the representation is exact, it is useful for reliably porting
values across different versions of Python (platform independence) and
exchanging data with other languages that support the same format (such
as Java and C99).

Another helpful tool is the *note math.fsum(): d43. function which helps
mitigate loss-of-precision during summation.  It tracks "lost digits" as
values are added onto a running total.  That can make a difference in
overall accuracy so that the errors do not accumulate to the point where
they affect the final total:

     >>> sum([0.1] * 10) == 1.0
     False
     >>> math.fsum([0.1] * 10) == 1.0
     True

* Menu:

* Representation Error::

   ---------- Footnotes ----------

   (1) http://www.lahey.com/float.htm


File: python.info,  Node: Representation Error,  Up: 浮點數運算：問題與限制

2.15.1 Representation Error
---------------------------

This section explains the "0.1" example in detail, and shows how you can
perform an exact analysis of cases like this yourself.  Basic
familiarity with binary floating-point representation is assumed.

`Representation error' refers to the fact that some (most, actually)
decimal fractions cannot be represented exactly as binary (base 2)
fractions.  This is the chief reason why Python (or Perl, C, C++, Java,
Fortran, and many others) often won’t display the exact decimal number
you expect.

Why is that?  1/10 is not exactly representable as a binary fraction.
Almost all machines today (November 2000) use IEEE-754 floating point
arithmetic, and almost all platforms map Python floats to IEEE-754
"double precision".  754 doubles contain 53 bits of precision, so on
input the computer strives to convert 0.1 to the closest fraction it can
of the form `J'/2**`N' where `J' is an integer containing exactly 53
bits.  Rewriting

     1 / 10 ~= J / (2**N)

as

     J ~= 2**N / 10

and recalling that `J' has exactly 53 bits (is ‘>= 2**52’ but ‘<
2**53’), the best value for `N' is 56:

     >>> 2**52 <=  2**56 // 10  < 2**53
     True

That is, 56 is the only value for `N' that leaves `J' with exactly 53
bits.  The best possible value for `J' is then that quotient rounded:

     >>> q, r = divmod(2**56, 10)
     >>> r
     6

Since the remainder is more than half of 10, the best approximation is
obtained by rounding up:

     >>> q+1
     7205759403792794

Therefore the best possible approximation to 1/10 in 754 double
precision is:

     7205759403792794 / 2 ** 56

Dividing both the numerator and denominator by two reduces the fraction
to:

     3602879701896397 / 2 ** 55

Note that since we rounded up, this is actually a little bit larger than
1/10; if we had not rounded up, the quotient would have been a little
bit smaller than 1/10.  But in no case can it be `exactly' 1/10!

So the computer never "sees" 1/10: what it sees is the exact fraction
given above, the best 754 double approximation it can get:

     >>> 0.1 * 2 ** 55
     3602879701896397.0

If we multiply that fraction by 10**55, we can see the value out to 55
decimal digits:

     >>> 3602879701896397 * 10 ** 55 // 2 ** 55
     1000000000000000055511151231257827021181583404541015625

meaning that the exact number stored in the computer is equal to the
decimal value 0.1000000000000000055511151231257827021181583404541015625.
Instead of displaying the full decimal value, many languages (including
older versions of Python), round the result to 17 significant digits:

     >>> format(0.1, '.17f')
     '0.10000000000000001'

The *note fractions: 83. and *note decimal: 36. modules make these
calculations easy:

     >>> 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 互動模式
---------------

* Menu:

* Error Handling::
* Executable Python Scripts::
* The Interactive Startup File::
* The Customization Modules::


File: python.info,  Node: Error Handling,  Next: Executable Python Scripts,  Up: 互動模式<2>

2.16.1.1 Error Handling
.......................

When an error occurs, the interpreter prints an error message and a
stack trace.  In interactive mode, it then returns to the primary
prompt; when input came from a file, it exits with a nonzero exit status
after printing the stack trace.  (Exceptions handled by an *note except:
b43. clause in a *note try: d77. statement are not errors in this
context.)  Some errors are unconditionally fatal and cause an exit with
a nonzero exit; this applies to internal inconsistencies and some cases
of running out of memory.  All error messages are written to the
standard error stream; normal output from executed commands is written
to standard output.

Typing the interrupt character (usually ‘Control-C’ or ‘Delete’) to the
primary or secondary prompt cancels the input and returns to the primary
prompt.  (1) Typing an interrupt while a command is executing raises the
*note KeyboardInterrupt: 198. exception, which may be handled by a *note
try: d77. statement.

   ---------- Footnotes ----------

   (1) (1) A problem with the GNU Readline package may prevent this.


File: python.info,  Node: Executable Python Scripts,  Next: The Interactive Startup File,  Prev: Error Handling,  Up: 互動模式<2>

2.16.1.2 Executable Python Scripts
..................................

On BSD’ish Unix systems, Python scripts can be made directly executable,
like shell scripts, by putting the line

     #!/usr/bin/env python3.5

(assuming that the interpreter is on the user’s ‘PATH’) at the beginning
of the script and giving the file an executable mode.  The ‘#!’ must be
the first two characters of the file.  On some platforms, this first
line must end with a Unix-style line ending (‘'\n'’), not a Windows
(‘'\r\n'’) line ending.  Note that the hash, or pound, character, ‘'#'’,
is used to start a comment in Python.

The script can be given an executable mode, or permission, using the
‘chmod’ command.

     $ chmod +x myscript.py

On Windows systems, there is no notion of an "executable mode".  The
Python installer automatically associates ‘.py’ files with ‘python.exe’
so that a double-click on a Python file will run it as a script.  The
extension can also be ‘.pyw’, in that case, the console window that
normally appears is suppressed.


File: python.info,  Node: The Interactive Startup File,  Next: The Customization Modules,  Prev: Executable Python Scripts,  Up: 互動模式<2>

2.16.1.3 The Interactive Startup File
.....................................

When you use Python interactively, it is frequently handy to have some
standard commands executed every time the interpreter is started.  You
can do this by setting an environment variable named *note
PYTHONSTARTUP: 8ea. to the name of a file containing your start-up
commands.  This is similar to the ‘.profile’ feature of the Unix shells.

This file is only read in interactive sessions, not when Python reads
commands from a script, and not when ‘/dev/tty’ is given as the explicit
source of commands (which otherwise behaves like an interactive
session).  It is executed in the same namespace where interactive
commands are executed, so that objects that it defines or imports can be
used without qualification in the interactive session.  You can also
change the prompts ‘sys.ps1’ and ‘sys.ps2’ in this file.

If you want to read an additional start-up file from the current
directory, you can program this in the global start-up file using code
like ‘if os.path.isfile('.pythonrc.py'):
exec(open('.pythonrc.py').read())’.  If you want to use the startup file
in a script, you must do this explicitly in the script:

     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: The Customization Modules,  Prev: The Interactive Startup File,  Up: 互動模式<2>

2.16.1.4 The Customization Modules
..................................

Python provides two hooks to let you customize it: ‘sitecustomize’ and
‘usercustomize’.  To see how it works, you need first to find the
location of your user site-packages directory.  Start Python and run
this code:

     >>> import site
     >>> site.getusersitepackages()
     '/home/user/.local/lib/python3.5/site-packages'

Now you can create a file named ‘usercustomize.py’ in that directory and
put anything you want in it.  It will affect every invocation of Python,
unless it is started with the *note -s: d1a. option to disable the
automatic import.

‘sitecustomize’ works in the same way, but is typically created by an
administrator of the computer in the global site-packages directory, and
is imported before ‘usercustomize’.  See the documentation of the *note
site: ec. module for more details.

註解
....


File: python.info,  Node: Python Setup and Usage,  Next: The Python Language Reference,  Prev: Python 教學,  Up: Top

3 Python Setup and Usage
************************

This part of the documentation is devoted to general information on the
setup of the Python environment on different platforms, the invocation
of the interpreter and things that make working with Python easier.

* Menu:

* Command line and environment::
* Using Python on Unix platforms::
* 在 Windows 上使用 Python::
* 在麥金塔系統使用Python::
* Editors and IDEs::


File: python.info,  Node: Command line and environment,  Next: Using Python on Unix platforms,  Up: Python Setup and Usage

3.1 Command line and environment
================================

The CPython interpreter scans the command line and the environment for
various settings.

`CPython implementation detail:' Other implementations’ command line
schemes may differ.  See *note Alternate Implementations: 133c. for
further resources.

* Menu:

* Command line::
* Environment variables::


File: python.info,  Node: Command line,  Next: Environment variables,  Up: Command line and environment

3.1.1 Command line
------------------

When invoking Python, you may specify any of these options:

     python [-bBdEhiIOqsSuvVWx?] [-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:

* Interface options::
* Generic options::
* Miscellaneous options::
* Options you shouldn't use::


File: python.info,  Node: Interface options,  Next: Generic options,  Up: Command line

3.1.1.1 Interface options
.........................

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.

   * 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:
c00. – note that the first element, subscript zero (‘sys.argv[0]’), is a
string reflecting the program’s source.

 -- 程式選項: -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: c00.
     will be ‘"-c"’ and the current directory will be added to the start
     of *note sys.path: 48d. (allowing modules in that directory to be
     imported as top level modules).

     Raises an *note auditing event: e96. ‘cpython.run_command’ with
     argument ‘command’.

 -- 程式選項: -m <module-name>

     Search *note sys.path: 48d. 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: c00.
     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: 1210. option, the current directory will be added to
     the start of *note sys.path: 48d.

     *note -I: 100d. option can be used to run the script in isolated
     mode where *note sys.path: 48d. 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: 10c.
     module:

          python -m timeit -s 'setup here' 'benchmarked code here'
          python -m timeit -h # for details

     Raises an *note auditing event: e96. ‘cpython.run_module’ with
     argument ‘module-name’.

     也參考
     ......

     *note runpy.run_module(): 1340.

          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: 312.).  If
     standard input is a terminal, *note -i: e24. is implied.

     If this option is given, the first element of *note sys.argv: c00.
     will be ‘"-"’ and the current directory will be added to the start
     of *note sys.path: 48d.

     Raises an *note auditing event: e96. ‘cpython.run_stdin’ with no
     arguments.

 -- 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: c00.
     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: 48d,
     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: 48d. and the
     ‘__main__.py’ file in that location is executed as the *note
     __main__: 1. module.

     *note -I: 100d. option can be used to run the script in isolated
     mode where *note sys.path: 48d. contains neither the script’s
     directory nor the user’s site-packages directory.  All ‘PYTHON*’
     environment variables are ignored, too.

     Raises an *note auditing event: e96. ‘cpython.run_file’ with
     argument ‘filename’.

     也參考
     ......

     *note runpy.run_path(): cb6.

          Equivalent functionality directly available to Python code

If no interface option is given, *note -i: e24. is implied,
‘sys.argv[0]’ is an empty string (‘""’) and the current directory will
be added to the start of *note sys.path: 48d.  Also, tab-completion and
history editing is automatically enabled, if available on your platform
(see *note Readline configuration: 8eb.).

也參考
......

*note 啟動直譯器: 120c.

3.4 版更變: Automatic enabling of tab-completion and history editing.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0338


File: python.info,  Node: Generic options,  Next: Miscellaneous options,  Prev: Interface options,  Up: Command line

3.1.1.2 Generic options
.......................

 -- 程式選項: -?
 -- 程式選項: -h
 -- 程式選項: --help

     Print a short description of all command line options.

 -- 程式選項: -V
 -- 程式選項: --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 版新加入: The ‘-VV’ option.


File: python.info,  Node: Miscellaneous options,  Next: Options you shouldn't use,  Prev: Generic options,  Up: Command line

3.1.1.3 Miscellaneous options
.............................

 -- 程式選項: -b

     Issue a warning when comparing *note bytes: 336. or *note
     bytearray: 337. with *note str: 335. or *note bytes: 336. with
     *note int: 185.  Issue an error when the option is given twice
     (‘-bb’).

     3.5 版更變: Affects comparisons of *note bytes: 336. with *note
     int: 185.

 -- 程式選項: -B

     If given, Python won’t try to write ‘.pyc’ files on the import of
     source modules.  See also *note PYTHONDONTWRITEBYTECODE: d3e.

 -- 程式選項: --check-hash-based-pycs default|always|never

     Control the validation behavior of hash-based ‘.pyc’ files.  See
     *note Cached bytecode invalidation: 32e.  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.

 -- 程式選項: -d

     Turn on parser debugging output (for expert only, depending on
     compilation options).  See also *note PYTHONDEBUG: 1348.

 -- 程式選項: -E

     Ignore all ‘PYTHON*’ environment variables, e.g.  *note PYTHONPATH:
     958. and *note PYTHONHOME: 4db, that might be set.

 -- 程式選項: -i

     When a script is passed as first argument or the *note -c: 1210.
     option is used, enter interactive mode after executing the script
     or the command, even when *note sys.stdin: 312. does not appear to
     be a terminal.  The *note PYTHONSTARTUP: 8ea. 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:
     e23.

 -- 程式選項: -I

     Run Python in isolated mode.  This also implies -E and -s.  In
     isolated mode *note sys.path: 48d. 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 版新加入.

 -- 程式選項: -O

     Remove assert statements and any code conditional on the value of
     *note __debug__: 1001.  Augment the filename for compiled (*note
     bytecode: 619.) files by adding ‘.opt-1’ before the ‘.pyc’
     extension (see PEP 488(1)).  See also *note PYTHONOPTIMIZE: 1349.

     3.5 版更變: Modify ‘.pyc’ filenames according to PEP 488(2).

 -- 程式選項: -OO

     Do *note -O: 690. and also discard docstrings.  Augment the
     filename for compiled (*note bytecode: 619.) files by adding
     ‘.opt-2’ before the ‘.pyc’ extension (see PEP 488(3)).

     3.5 版更變: Modify ‘.pyc’ filenames according to PEP 488(4).

 -- 程式選項: -q

     Don’t display the copyright and version messages even in
     interactive mode.

     3.2 版新加入.

 -- 程式選項: -R

     Turn on hash randomization.  This option only has an effect if the
     *note PYTHONHASHSEED: 9ca. 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__(): 345. 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://www.ocert.org/advisories/ocert-2011-003.html’ for details.

     *note PYTHONHASHSEED: 9ca. allows you to set a fixed value for the
     hash seed secret.

     3.7 版更變: The option is no longer ignored.

     3.2.3 版新加入.

 -- 程式選項: -s

     Don’t add the *note user site-packages directory: 134b. to *note
     sys.path: 48d.

     也參考
     ......

     PEP 370(5) – Per user site-packages directory

 -- 程式選項: -S

     Disable the import of the module *note site: ec. and the
     site-dependent manipulations of *note sys.path: 48d. that it
     entails.  Also disable these manipulations if *note site: ec. is
     explicitly imported later (call *note site.main(): 134c. if you
     want them to be triggered).

 -- 程式選項: -u

     Force the stdout and stderr streams to be unbuffered.  This option
     has no effect on the stdin stream.

     See also *note PYTHONUNBUFFERED: 134e.

     3.7 版更變: The text layer of the stdout and stderr streams now is
     unbuffered.

 -- 程式選項: -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.  See also *note PYTHONVERBOSE: 134f.
 -- 程式選項: -W arg

     Warning control.  Python’s warning machinery by default prints
     warning messages to *note sys.stderr: 314.  A typical warning
     message has the following form:

          file:line: category: message

     By default, each warning is printed once for each source line where
     it occurs.  This option controls how often warnings are printed.

     Multiple *note -W: 41c. options may be given; when a warning
     matches more than one option, the action for the last matching
     option is performed.  Invalid *note -W: 41c. 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:
     41d. environment variable and from within a Python program using
     the *note warnings: 127. module.

     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
          -Wmodule   # Warn once per calling module
          -Wonce     # Warn once per Python process
          -Wignore   # Never warn

     The action names can be abbreviated as desired (e.g.  ‘-Wi’, ‘-Wd’,
     ‘-Wa’, ‘-We’) and the interpreter will resolve them to the
     appropriate action name.

     See *note The Warnings Filter: 1351. and *note Describing Warning
     Filters: 1352. for more details.

 -- 程式選項: -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.

 -- 程式選項: -X

     Reserved for various implementation-specific options.  CPython
     currently defines the following possible values:

        * ‘-X faulthandler’ to enable *note faulthandler: 7d.;

        * ‘-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 debug builds.

        * ‘-X tracemalloc’ to start tracing Python memory allocations
          using the *note tracemalloc: 115. 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 the *note tracemalloc.start():
          1354. for more information.

        * ‘-X showalloccount’ to output the total count of allocated
          objects for each type when the program finishes.  This only
          works when Python was built with ‘COUNT_ALLOCS’ defined.

        * ‘-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: 33d.

        * ‘-X dev’: enable CPython’s "development mode", introducing
          additional runtime checks which are too expensive to be
          enabled by default.  It should not be more verbose than the
          default if the code is correct: new warnings are only emitted
          when an issue is detected.  Effect of the developer mode:

             * Add ‘default’ warning filter, as *note -W: 41c.
               ‘default’.

             * Install debug hooks on memory allocators: see the *note
               PyMem_SetupDebugHooks(): 50f. C function.

             * Enable the *note faulthandler: 7d. module to dump the
               Python traceback on a crash.

             * Enable *note asyncio debug mode: 1355.

             * Set the ‘dev_mode’ attribute of *note sys.flags: b41. to
               ‘True’.

             * *note io.IOBase: 1dc. destructor logs ‘close()’
               exceptions.

        * ‘-X utf8’ enables UTF-8 mode for operating system interfaces,
          overriding the default locale-aware mode.  ‘-X utf8=0’
          explicitly disables UTF-8 mode (even when it would otherwise
          activate automatically).  See *note PYTHONUTF8: 316. for more
          details.

        * ‘-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: 155.

     It also allows passing arbitrary values and retrieving them through
     the *note sys._xoptions: 1356. dictionary.

     3.2 版更變: The *note -X: 156. option was added.

     3.3 版新加入: The ‘-X faulthandler’ option.

     3.4 版新加入: The ‘-X showrefcount’ and ‘-X tracemalloc’ options.

     3.6 版新加入: The ‘-X showalloccount’ option.

     3.7 版新加入: The ‘-X importtime’, ‘-X dev’ and ‘-X utf8’ options.

     3.8 版新加入: The ‘-X pycache_prefix’ option.  The ‘-X dev’ option
     now logs ‘close()’ exceptions in *note io.IOBase: 1dc. destructor.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0488

   (2) https://www.python.org/dev/peps/pep-0488

   (3) https://www.python.org/dev/peps/pep-0488

   (4) https://www.python.org/dev/peps/pep-0488

   (5) https://www.python.org/dev/peps/pep-0370


File: python.info,  Node: Options you shouldn't use,  Prev: Miscellaneous options,  Up: Command line

3.1.1.4 Options you shouldn’t use
.................................

 -- 程式選項: -J

     Reserved for use by Jython(1).

   ---------- Footnotes ----------

   (1) http://www.jython.org/


File: python.info,  Node: Environment variables,  Prev: Command line,  Up: Command line and environment

3.1.2 Environment variables
---------------------------

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: 4db. is set to a single directory, its value
     replaces both ‘`prefix'’ and ‘`exec_prefix'’.  To specify different
     values for these, set *note PYTHONHOME: 4db. 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: 135a. (e.g.  colons on Unix or
     semicolons on Windows).  Non-existent directories are silently
     ignored.

     In addition to normal directories, individual *note PYTHONPATH:
     958. 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:
     4db. above).  It is `always' appended to *note PYTHONPATH: 958.

     An additional directory will be inserted in the search path in
     front of *note PYTHONPATH: 958. as described above under *note
     Interface options: 133f.  The search path can be manipulated from
     within a Python program as the variable *note sys.path: 48d.

 -- 環境變數: 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: 135b. and
     *note sys.ps2: 135c. and the hook *note sys.__interactivehook__:
     8e9. in this file.

     Raises an *note auditing event: e96. ‘cpython.run_startup’ with the
     filename as the argument when called on startup.

 -- 環境變數: PYTHONOPTIMIZE

     If this is set to a non-empty string it is equivalent to specifying
     the *note -O: 690. option.  If set to an integer, it is equivalent
     to specifying *note -O: 690. 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(): 318. which itself is called by built-in *note
     breakpoint(): 2fe.  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(): 318. 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: 1347. option.  If set to an integer, it is equivalent
     to specifying *note -d: 1347. multiple times.

 -- 環境變數: PYTHONINSPECT

     If this is set to a non-empty string it is equivalent to specifying
     the *note -i: e24. option.

     This variable can also be modified by Python code using *note
     os.environ: b3c. to force inspect mode on program termination.

 -- 環境變數: PYTHONUNBUFFERED

     If this is set to a non-empty string it is equivalent to specifying
     the *note -u: 134d. option.

 -- 環境變數: PYTHONVERBOSE

     If this is set to a non-empty string it is equivalent to specifying
     the *note -v: d8d. option.  If set to an integer, it is equivalent
     to specifying *note -v: d8d. multiple times.

 -- 環境變數: PYTHONCASEOK

     If this is set, Python ignores case in *note import: c22.
     statements.  This only works on Windows and OS X.

 -- 環境變數: 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: d3d. 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: 156. ‘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: 9ca. 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 版新加入.

 -- 環境變數: 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(): c3c.

     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: 4ff. 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: 134b. to *note sys.path: 48d.

     也參考
     ......

     PEP 370(1) – Per user site-packages directory

 -- 環境變數: PYTHONUSERBASE

     Defines the *note user base directory: 135d, which is used to
     compute the path of the *note user site-packages directory: 134b.
     and *note Distutils installation paths: 135e. for ‘python setup.py
     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 Mac OS X.

 -- 環境變數: PYTHONWARNINGS

     This is equivalent to the *note -W: 41c. option.  If set to a comma
     separated string, it is equivalent to specifying *note -W: 41c.
     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=module   # Warn once per calling module
          PYTHONWARNINGS=once     # Warn once per Python process
          PYTHONWARNINGS=ignore   # Never warn

     See *note The Warnings Filter: 1351. and *note Describing Warning
     Filters: 1352. for more details.

 -- 環境變數: PYTHONFAULTHANDLER

     If this environment variable is set to a non-empty string, *note
     faulthandler.enable(): 54d. is called at startup: install a handler
     for ‘SIGSEGV’, ‘SIGFPE’, ‘SIGABRT’, ‘SIGBUS’ and ‘SIGILL’ signals
     to dump the Python traceback.  This is equivalent to *note -X: 156.
     ‘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: 115.
     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(): 1354. for more information.

     3.4 版新加入.

 -- 環境變數: PYTHONPROFILEIMPORTTIME

     If this environment variable is set to a non-empty string, Python
     will show how long each import takes.  This is exactly equivalent
     to setting ‘-X importtime’ on the command line.

     3.7 版新加入.

 -- 環境變數: PYTHONASYNCIODEBUG

     If this environment variable is set to a non-empty string, enable
     the *note debug mode: 1355. of the *note asyncio: a. 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: 1362.

        * ‘malloc’: use the ‘malloc()’ function of the C library for all
          domains (*note PYMEM_DOMAIN_RAW: 1363, *note PYMEM_DOMAIN_MEM:
          50e, *note PYMEM_DOMAIN_OBJ: 50c.).

        * ‘pymalloc’: use the *note pymalloc allocator: 5c6. for *note
          PYMEM_DOMAIN_MEM: 50e. and *note PYMEM_DOMAIN_OBJ: 50c.
          domains and use the ‘malloc()’ function for the *note
          PYMEM_DOMAIN_RAW: 1363. domain.

     Install debug hooks:

        * ‘debug’: install debug hooks on top of the *note default
          memory allocators: 1362.

        * ‘malloc_debug’: same as ‘malloc’ but also install debug hooks.

        * ‘pymalloc_debug’: same as ‘pymalloc’ but also install debug
          hooks.

     See the *note default memory allocators: 1362. and the *note
     PyMem_SetupDebugHooks(): 50f. function (install debug hooks on
     Python memory allocators).

     3.7 版更變: Added the ‘"default"’ allocator.

     3.6 版新加入.

 -- 環境變數: PYTHONMALLOCSTATS

     If set to a non-empty string, Python will print statistics of the
     *note pymalloc memory allocator: 5c6. every time a new pymalloc
     object arena is created, and on shutdown.

     This variable is ignored if the *note PYTHONMALLOC: 508.
     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 filesystem encoding and
     errors 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(): 4fd.

     *note Availability: 1364.: Windows.

     3.6 版新加入: See PEP 529(3) for more details.

 -- 環境變數: 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 Availability: 1364.: 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():
     1365.).

     Configuring one of these locales (either explicitly or via the
     above implicit locale coercion) automatically enables the
     ‘surrogateescape’ *note error handler: 1366. for *note sys.stdin:
     312. and *note sys.stdout: 313. (*note sys.stderr: 314. continues
     to use ‘backslashreplace’ as it does in any other locale).  This
     stream handling behavior can be overridden using *note
     PYTHONIOENCODING: 934. 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: 316. 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 Availability: 1364.: *nix.

     3.7 版新加入: See PEP 538(4) for more details.

 -- 環境變數: PYTHONDEVMODE

     If this environment variable is set to a non-empty string, enable
     the CPython "development mode".  See the *note -X: 156. ‘dev’
     option.

     3.7 版新加入.

 -- 環境變數: PYTHONUTF8

     If set to ‘1’, enables the interpreter’s UTF-8 mode, where ‘UTF-8’
     is used as the text encoding for system interfaces, regardless of
     the current locale setting.

     This means that:

             * *note sys.getfilesystemencoding(): 4fb. returns ‘'UTF-8'’
               (the locale encoding is ignored).

             * *note locale.getpreferredencoding(): 3aa. returns
               ‘'UTF-8'’ (the locale encoding is ignored, and the
               function’s ‘do_setlocale’ parameter has no effect).

             * *note sys.stdin: 312, *note sys.stdout: 313, and *note
               sys.stderr: 314. all use UTF-8 as their text encoding,
               with the ‘surrogateescape’ *note error handler: 1366.
               being enabled for *note sys.stdin: 312. and *note
               sys.stdout: 313. (*note sys.stderr: 314. continues to use
               ‘backslashreplace’ as it does 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(): 4f3. and *note os.fsencode(): 4f4.
               use the UTF-8 encoding.

             * *note open(): 4f5, *note io.open(): 65f, and *note
               codecs.open(): 1367. 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.

     Note that the standard stream settings in UTF-8 mode can be
     overridden by *note PYTHONIOENCODING: 934. (just as they can be in
     the default locale-aware mode).

     If set to ‘0’, the interpreter runs in its default locale-aware
     mode.

     Setting any other non-empty string causes an error during
     interpreter initialisation.

     If this 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: 311.), 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.

     Also available as the *note -X: 156. ‘utf8’ option.

     3.7 版新加入: See PEP 540(5) for more details.

* Menu:

* Debug-mode variables::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0370

   (2) https://www.python.org/dev/peps/pep-0370

   (3) https://www.python.org/dev/peps/pep-0529

   (4) https://www.python.org/dev/peps/pep-0538

   (5) https://www.python.org/dev/peps/pep-0540


File: python.info,  Node: Debug-mode variables,  Up: Environment variables

3.1.2.1 Debug-mode variables
............................

Setting these variables only has an effect in a debug build of Python.

 -- 環境變數: PYTHONTHREADDEBUG

     If set, Python will print threading debug info.

     Need Python configured with the ‘--with-pydebug’ build option.

 -- 環境變數: PYTHONDUMPREFS

     If set, Python will dump objects and reference counts still alive
     after shutting down the interpreter.

     Need Python configured with the ‘--with-trace-refs’ build option.


File: python.info,  Node: Using Python on Unix platforms,  Next: 在 Windows 上使用 Python,  Prev: Command line and environment,  Up: Python Setup and Usage

3.2 Using Python on Unix platforms
==================================

* Menu:

* Getting and installing the latest version of Python::
* Building Python::
* Python-related paths and files::
* Miscellaneous::


File: python.info,  Node: Getting and installing the latest version of Python,  Next: Building Python,  Up: Using Python on Unix platforms

3.2.1 Getting and installing the latest version of Python
---------------------------------------------------------

* Menu:

* On Linux::
* On FreeBSD and OpenBSD::
* On OpenSolaris::


File: python.info,  Node: On Linux,  Next: On FreeBSD and OpenBSD,  Up: Getting and installing the latest version of Python

3.2.1.1 On Linux
................

Python comes preinstalled on most Linux distributions, and is available
as a package on all others.  However there are certain features you
might want to use that are not available on your distro’s package.  You
can easily compile the latest version of Python from source.

In the event that Python doesn’t come preinstalled and isn’t in the
repositories as well, you can easily make packages for your own distro.
Have a look at the following links:

也參考
......

‘https://www.debian.org/doc/manuals/maint-guide/first.en.html’

     for Debian users

‘https://en.opensuse.org/Portal:Packaging’

     for OpenSuse users

‘https://docs-old.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/ch-creating-rpms.html’

     for Fedora users

‘http://www.slackbook.org/html/package-management-making-packages.html’

     for Slackware users


File: python.info,  Node: On FreeBSD and OpenBSD,  Next: On OpenSolaris,  Prev: On Linux,  Up: Getting and installing the latest version of Python

3.2.1.2 On FreeBSD and OpenBSD
..............................

   * FreeBSD users, to add the package use:

          pkg install python3

   * OpenBSD users, to add the package use:

          pkg_add -r python

          pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/<insert your architecture here>/python-<version>.tgz

     For example i386 users get the 2.5.1 version of Python using:

          pkg_add ftp://ftp.openbsd.org/pub/OpenBSD/4.2/packages/i386/python-2.5.1p2.tgz


File: python.info,  Node: On OpenSolaris,  Prev: On FreeBSD and OpenBSD,  Up: Getting and installing the latest version of Python

3.2.1.3 On OpenSolaris
......................

You can get Python from OpenCSW(1). Various versions of Python are
available and can be installed with e.g.  ‘pkgutil -i python27’.

   ---------- Footnotes ----------

   (1) https://www.opencsw.org/


File: python.info,  Node: Building Python,  Next: Python-related paths and files,  Prev: Getting and installing the latest version of Python,  Up: Using Python on Unix platforms

3.2.2 Building Python
---------------------

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 clone(2).  (If you want to contribute patches, you
will need a clone.)

The build process consists of the usual commands:

     ./configure
     make
     make install

Configuration options and caveats for specific Unix platforms are
extensively documented in the README.rst(3) file in the root of the
Python source tree.

     警告: ‘make install’ can overwrite or masquerade the ‘python3’
     binary.  ‘make altinstall’ is therefore recommended instead of
     ‘make install’ since it only installs
     ‘`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.8/README.rst


File: python.info,  Node: Python-related paths and files,  Next: Miscellaneous,  Prev: Building Python,  Up: Using Python on Unix platforms

3.2.3 Python-related paths and files
------------------------------------

These are subject to difference depending on local installation
conventions; ‘prefix’ (‘${prefix}’) and ‘exec_prefix’ (‘${exec_prefix}’)
are installation-dependent and should be interpreted as for GNU
software; they may be the same.

For example, on most Linux systems, the default for both is ‘/usr’.

File/directory                                      Meaning
                                                    
---------------------------------------------------------------------------------------------------
                                                    
‘`exec_prefix'/bin/python3’                         Recommended location of the interpreter.
                                                    
                                                    
‘`prefix'/lib/python`version'’,                     Recommended locations of the directories
‘`exec_prefix'/lib/python`version'’                 containing the standard modules.
                                                    
                                                    
‘`prefix'/include/python`version'’,                 Recommended locations of the directories
‘`exec_prefix'/include/python`version'’             containing the include files needed for
                                                    developing Python extensions and embedding
                                                    the interpreter.
                                                    


File: python.info,  Node: Miscellaneous,  Prev: Python-related paths and files,  Up: Using Python on Unix platforms

3.2.4 Miscellaneous
-------------------

To easily use Python scripts on Unix, you need to make them executable,
e.g.  with

     $ chmod +x script

and put an appropriate Shebang line at the top of the script.  A good
choice is usually

     #!/usr/bin/env python3

which searches for the Python interpreter in the whole ‘PATH’.  However,
some Unices may not have the ‘env’ command, so you may need to hardcode
‘/usr/bin/python3’ as the interpreter path.

To use shell commands in your Python scripts, look at the *note
subprocess: fa. module.


File: python.info,  Node: 在 Windows 上使用 Python,  Next: 在麥金塔系統使用Python,  Prev: Using Python on Unix platforms,  Up: Python Setup and Usage

3.3 在 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 (MSI packages) 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.8 supports Windows Vista and newer.  If you
require Windows XP support then please install Python 3.4.

There are a number of different installers available for Windows, each
with certain benefits and downsides.

*note The full installer: 1376. contains all components and is the best
option for developers using Python for any kind of project.

*note The Microsoft Store package: 120d. 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, but can be
safely installed without corrupting other programs.  It also provides
many convenient commands for launching Python and its tools.

*note The nuget.org packages: 1377. 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: 1378. is a minimal package of Python
suitable for embedding into a larger application.

* Menu:

* The full installer::
* The Microsoft Store package::
* The nuget.org packages: The nuget org packages.
* The embeddable package::
* Alternative bundles::
* 設定 Python::
* UTF-8 mode::
* Python Launcher for Windows::
* Finding modules::
* Additional modules::
* 編譯 Python 在 Windows::
* 其他平台::

   ---------- Footnotes ----------

   (1) https://www.python.org/download/releases/

   (2) https://www.python.org/dev/peps/pep-0011


File: python.info,  Node: The full installer,  Next: The Microsoft Store package,  Up: 在 Windows 上使用 Python

3.3.1 The full installer
------------------------

* Menu:

* Installation steps::
* Removing the MAX_PATH Limitation::
* 安裝排除使用者介面::
* 當安裝時不下載::
* Modifying an install::


File: python.info,  Node: Installation steps,  Next: Removing the MAX_PATH Limitation,  Up: The full installer

3.3.1.1 Installation steps
..........................

Four Python 3.8 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 當安裝時不下載:
137b. for other ways to avoid downloading during installation.

After starting the installer, one of two options may be selected:

[python-figures/win_installer]
如果你選擇「馬上安裝」：

   * 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: 994. for all users)

   * Python will be installed into your user directory

   * The *note Python Launcher for Windows: 994. 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: 994. 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: Installation steps,  Up: The full installer

3.3.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(): 4f5. function, the *note os: c5. 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.3.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.

To completely hide the installer UI and install Python silently, pass
the ‘/quiet’ option.  To skip past the user interaction but still
display progress and errors, pass the ‘/passive’ option.  The
‘/uninstall’ option may be passed to immediately begin removing Python -
no prompt will be displayed.

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.

Name                            描述                                       預設
                                                                           
----------------------------------------------------------------------------------------------------------
                                                                           
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                          or
                                                                           ‘%ProgramFiles(x86)%\Python
                                                                           X.Y’
                                                                           
                                                                           
DefaultJustForMeTargetDir       預設安裝目錄給 只有給我 安裝方式           ‘%LocalAppData%\Programs\PythonXY’
                                                                           or
                                                                           ‘%LocalAppData%\Programs\PythonXY-32’
                                                                           or
                                                                           ‘%LocalAppData%\Programs\PythonXY-64’
                                                                           
                                                                           
DefaultCustomTargetDir          The default custom install directory       (empty)
                                displayed in the UI                        
                                
                                                                           
AssociateFiles                  當執行程序也被安裝時創造檔案關聯           1
                                                                           
                                                                           
CompileAll                      編譯所有 ‘.py’ 檔案為 ‘.pyc’。             0
                                                                           
                                                                           
PrependPath                     Add install and Scripts directories to     0
                                ‘PATH’ and ‘.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
                                                                           
                                                                           
Include_exe                     Install ‘python.exe’ and related files     1
                                                                           
                                                                           
Include_launcher                Install                                    1
                                *note Python Launcher for Windows: 994.    
                                
                                                                           
InstallLauncherAllUsers         Installs                                   1
                                *note Python Launcher for Windows: 994.    
                                for all users.
                                
                                                                           
Include_lib                     Install standard library and extension     1
                                modules                                    
                                
                                                                           
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.8.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.8.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.3.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.8.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.8.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,  Prev: 當安裝時不下載,  Up: The full installer

3.3.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: 994, which has its own entry in Programs
and Features.


File: python.info,  Node: The Microsoft Store package,  Next: The nuget org packages,  Prev: The full installer,  Up: 在 Windows 上使用 Python

3.3.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.8".  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.8).
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.3.2.1 Known Issues
....................

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.

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: The nuget org packages,  Next: The embeddable package,  Prev: The Microsoft Store package,  Up: 在 Windows 上使用 Python

3.3.3 The nuget.org packages
----------------------------

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 and
www.nuget.org/packages/pythonx86(3) for the 32-bit version.

   ---------- Footnotes ----------

   (1) https://www.nuget.org/

   (2) https://www.nuget.org/packages/python

   (3) https://www.nuget.org/packages/pythonx86


File: python.info,  Node: The embeddable package,  Next: Alternative bundles,  Prev: The nuget org packages,  Up: 在 Windows 上使用 Python

3.3.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 dependants, 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.

     備註: When running on Windows 7, Python 3.8 requires the KB2533623
     update to be installed.  The embeddable distribution does not
     detect this update, and may fail at runtime.  Later versions of
     Windows include this update.

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://www.microsoft.com/en-us/download/details.aspx?id=48145


File: python.info,  Node: Python Application,  Next: 嵌入 Python,  Up: The embeddable package

3.3.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.3.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.3.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.

Canopy(3)

     A "comprehensive Python analysis environment" with editors and
     other development tools.

WinPython(4)

     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/activepython/

   (2) https://www.anaconda.com/download/

   (3) https://www.enthought.com/product/canopy/

   (4) https://winpython.github.io/


File: python.info,  Node: 設定 Python,  Next: UTF-8 mode,  Prev: Alternative bundles,  Up: 在 Windows 上使用 Python

3.3.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: 994.

* 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.3.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.8;%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: 958. variable is used by all versions of
     Python 2 and Python 3, so you should not permanently configure this
     variable unless it only includes code that is compatible with all
     of your installed Python versions.

也參考
......

‘https://www.microsoft.com/en-us/wdsi/help/folder-variables’

     環境變數於 Windows NT

‘https://technet.microsoft.com/en-us/library/cc754250.aspx’

     The SET command, for temporarily modifying environment variables

‘https://technet.microsoft.com/en-us/library/cc755104.aspx’

     The SETX command, for permanently modifying environment variables

‘https://support.microsoft.com/en-us/help/310519/how-to-manage-environment-variables-in-windows-xp’

     如何管理環境變數於 Windows XP

‘https://www.chem.gla.ac.uk/~louis/software/faq/q1.html’

     設定環境變數－Louis J. Farrugia


File: python.info,  Node: Finding the Python executable,  Prev: Excursus Setting environment variables,  Up: 設定 Python

3.3.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 Command line: 930. 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: 120e.  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.8


File: python.info,  Node: UTF-8 mode,  Next: Python Launcher for Windows,  Prev: 設定 Python,  Up: 在 Windows 上使用 Python

3.3.7 UTF-8 mode
----------------

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.getpreferredencoding(): 3aa.).

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 UTF-8 mode to change the default text encoding to UTF-8.
You can enable UTF-8 mode via the ‘-X utf8’ command line option, or the
‘PYTHONUTF8=1’ environment variable.  See *note PYTHONUTF8: 316. for
enabling UTF-8 mode, and *note Excursus; Setting environment variables:
120e. for how to modify environment variables.

When UTF-8 mode is enabled:

   * *note locale.getpreferredencoding(): 3aa. returns ‘'UTF-8'’ instead
     of the system encoding.  This function is used for the default text
     encoding in many places, including *note open(): 4f5, ‘Popen’,
     ‘Path.read_text()’, etc.

   * *note sys.stdin: 312, *note sys.stdout: 313, and *note sys.stderr:
     314. all use UTF-8 as their text encoding.

   * You can still use the system encoding 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 filesystem encoding (see PEP 529(2) for details).

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0528

   (2) https://www.python.org/dev/peps/pep-0529


File: python.info,  Node: Python Launcher for Windows,  Next: Finding modules,  Prev: UTF-8 mode,  Up: 在 Windows 上使用 Python

3.3.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::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0397


File: python.info,  Node: 開始,  Next: Shebang Lines,  Up: Python Launcher for Windows

3.3.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.3.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., 2.7 and 3.8)
you will have noticed that Python 3.8 was started - to launch Python
2.7, try the command:

     py -2.7

If you want the latest version of Python 2.x you have installed, try the
command:

     py -2

You should find the latest version of Python 2.x starts.

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.

Per-user installations of Python do not add the launcher to ‘PATH’
unless the option was selected on installation.


File: python.info,  Node: 虛擬環境（Virtual environment）,  Next: From a script,  Prev: From the command-line,  Up: 開始

3.3.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:
126. 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.3.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 2.6
installed, try changing the first line to ‘#! python2.6’ and you should
find the 2.6 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.3.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.3.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 python’

   * ‘/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 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/python2.7-32’ will request usage of
the 32-bit python 2.7.

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’).

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.  This
corresponds to the behaviour of the Unix ‘env’ program, which performs a
‘PATH’ search.


File: python.info,  Node: Arguments in shebang lines,  Next: Customization,  Prev: Shebang Lines,  Up: Python Launcher for Windows

3.3.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.3.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.3.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 (i.e.  the directory
returned by calling the Windows function ‘SHGetFolderPath’ with
‘CSIDL_LOCAL_APPDATA’) 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.3.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.

Examples:

   * 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 commands ‘python3.1’ and ‘python2.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.1-32’, the command ‘python’ will use the 32-bit
     implementation of 3.1 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.1’, the commands ‘python’ and
     ‘python3’ will both use specifically 3.1

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.

For example:

   * Setting ‘PY_PYTHON=3.1’ is equivalent to the INI file containing:

     [defaults]
     python=3.1

   * Setting ‘PY_PYTHON=3’ and ‘PY_PYTHON3=3.1’ is equivalent to the INI
     file containing:

     [defaults]
     python=3
     python3=3.1


File: python.info,  Node: Diagnostics,  Prev: Customization,  Up: Python Launcher for Windows

3.3.8.11 Diagnostics
....................

If an environment variable ‘PYLAUNCH_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.


File: python.info,  Node: Finding modules,  Next: Additional modules,  Prev: Python Launcher for Windows,  Up: 在 Windows 上使用 Python

3.3.9 Finding modules
---------------------

Python usually stores its library (and thereby your site-packages
folder) in the installation directory.  So, if you had installed Python
to ‘C:\Python\’, the default library would reside in ‘C:\Python\Lib\’
and third-party modules should be stored in
‘C:\Python\Lib\site-packages\’.

To completely override *note sys.path: 48d, create a ‘._pth’ file with
the same name as the DLL (‘python37._pth’) or the executable
(‘python._pth’) and specify one line for each path to add to *note
sys.path: 48d.  The file based on the DLL 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: ec. 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: ec. module when ‘import site’ has been
specified.

When no ‘._pth’ file is found, this is how *note sys.path: 48d. is
populated on Windows:

   * An empty entry is added at the start, which corresponds to the
     current directory.

   * If the environment variable *note PYTHONPATH: 958. exists, as
     described in *note Environment variables: 1359, 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:
     48d.  (Note that all known installers only use HKLM, so HKCU is
     typically empty.)

   * If the environment variable *note PYTHONHOME: 4db. 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:
     48d. (‘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: 958. 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: 4db. 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: ec.
     unless ‘import site’ is listed.

   * If you are loading ‘python3.dll’ or ‘python37.dll’ in your own
     executable, explicitly call *note Py_SetPath(): 274. or (at least)
     *note Py_SetProgramName(): f8e. before *note Py_Initialize(): 43e.

   * Clear and/or overwrite *note PYTHONPATH: 958. and set *note
     PYTHONHOME: 4db. 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 版更變:

        * Adds ‘._pth’ file support and removes ‘applocal’ option from
          ‘pyvenv.cfg’.

        * Adds ‘pythonXX.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: 5ea.  This finder is
     enabled on Windows in 3.6.0 and earlier, but may need to be
     explicitly added to *note sys.meta_path: 5eb. in the future.


File: python.info,  Node: Additional modules,  Next: 編譯 Python 在 Windows,  Prev: Finding modules,  Up: 在 Windows 上使用 Python

3.3.10 Additional modules
-------------------------

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
Specific Services: 139b.

* Menu:

* PyWin32::
* cx_Freeze::
* WConio::


File: python.info,  Node: PyWin32,  Next: cx_Freeze,  Up: Additional modules

3.3.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 calls

   * 登錄檔（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)

     by Tim Golden

Python and COM(6)

     by David and Paul Boddie

   ---------- Footnotes ----------

   (1) https://pypi.org/project/pywin32

   (2) 
https://docs.microsoft.com/en-us/windows/desktop/com/component-object-model–com–portal

   (3) https://msdn.microsoft.com/en-us/library/fe1cf721%28VS.80%29.aspx

   (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) http://www.boddie.org.uk/python/COM.html


File: python.info,  Node: cx_Freeze,  Next: WConio,  Prev: PyWin32,  Up: Additional modules

3.3.10.2 cx_Freeze
..................

cx_Freeze(1) is a *note distutils: 39. extension (see *note Extending
Distutils: 139e.) which 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: WConio,  Prev: cx_Freeze,  Up: Additional modules

3.3.10.3 WConio
...............

Since Python’s advanced terminal handling layer, *note curses: 2c, is
restricted to Unix-like systems, there is a library exclusive to Windows
as well: Windows Console I/O for Python.

WConio(1) is a wrapper for Turbo-C’s ‘CONIO.H’, used to create text user
interfaces.

   ---------- Footnotes ----------

   (1) http://newcenturycomputers.net/projects/wconio.html


File: python.info,  Node: 編譯 Python 在 Windows,  Next: 其他平台,  Prev: Additional modules,  Up: 在 Windows 上使用 Python

3.3.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 2015, 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 Building C and C++ Extensions on
Windows: 13a1.

也參考
......

Python + Windows + distutils + SWIG + gcc MinGW(3)

     or "Creating Python extensions in C/C++ with SWIG and compiling
     them with MinGW gcc under Windows" or "Installing Python extension
     with distutils and without Microsoft Visual C++" by Sébastien
     Sauvage, 2003

   ---------- Footnotes ----------

   (1) https://www.python.org/downloads/source/

   (2) https://devguide.python.org/setup/#getting-the-source-code

   (3) http://sebsauvage.net/python/mingw.html


File: python.info,  Node: 其他平台,  Prev: 編譯 Python 在 Windows,  Up: 在 Windows 上使用 Python

3.3.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 still supported.

   * The Cygwin(3) installer offers to install the Python interpreter as
     well (cf.  Cygwin package source(4), Maintainer releases(5))

See Python for Windows(6) for detailed information about platforms with
pre-compiled installers.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0011

   (2) http://pythonce.sourceforge.net/

   (3) https://cygwin.com/

   (4) 
ftp://ftp.uni-erlangen.de/pub/pc/gnuwin32/cygwin/mirrors/cygnus/release/python

   (5) http://www.tishler.net/jason/software/python/

   (6) https://www.python.org/downloads/windows/


File: python.info,  Node: 在麥金塔系統使用Python,  Next: Editors and IDEs,  Prev: 在 Windows 上使用 Python,  Up: Python Setup and Usage

3.4 在麥金塔系統使用Python
==========================


Author: Bob Savage <<bobsavage@mac.com>>

Python 執行在麥金塔系統的 Mac OS X 和執行在其他 Unix 平台上原理非常相似
，但有一些值得提出的是在 Mac OS X 上增加其他額外的功能例如 IDE 與 套件管
理。

* Menu:

* 取得和安裝MacPython::
* 整合化開發工具::
* Installing Additional Python Packages::
* 圖形化使用者介面(GUI) 程式開發於Mac: 圖形化使用者介面 GUI 程式開發於Mac.
* 貢獻Python應用程式於 Mac::
* 其他資源::


File: python.info,  Node: 取得和安裝MacPython,  Next: 整合化開發工具,  Up: 在麥金塔系統使用Python

3.4.1 取得和安裝MacPython
-------------------------

Apple 在 Mac OS X 10.8 預設安裝 Python 2.7。但你也可以到 Python website
（‘https://www.python.org’ ）更新至最新的 Python 3。Python 建立在"通用二
進位"上，使 Python 能以本地程序的形式運行在使用英特爾微處理器與 PowerPC
麥金塔電腦上。

在安裝後你必須要做幾件事：

   * A ‘Python 3.8’ folder in your ‘Applications’ folder.  In here you
     find IDLE, the development environment that is a standard part of
     official Python distributions; and PythonLauncher, which handles
     double-clicking Python scripts from the Finder.

   * A framework ‘/Library/Frameworks/Python.framework’, which includes
     the Python executable and libraries.  The installer adds this
     location to your shell path.  To uninstall MacPython, you can
     simply remove these three things.  A symlink to the Python
     executable is placed in /usr/local/bin/.

The Apple-provided build of Python is installed in
‘/System/Library/Frameworks/Python.framework’ and ‘/usr/bin/python’,
respectively.  You should never modify or delete these, as they are
Apple-controlled and are used by Apple- or third-party software.
Remember that if you choose to install a newer Python version from
python.org, you will have two different but functional Python
installations on your computer, so it will be important that your paths
and usages are consistent with what you want to do.

IDLE includes a help menu that allows you to access Python
documentation.  If you are completely new to Python you should start
reading the tutorial introduction in that document.

If you are familiar with Python on other Unix platforms you should read
the section on running Python scripts from the Unix shell.

* Menu:

* 如何執行Python腳本::
* 透過使用者圖形介面執行腳本::
* 設定::


File: python.info,  Node: 如何執行Python腳本,  Next: 透過使用者圖形介面執行腳本,  Up: 取得和安裝MacPython

3.4.1.1 如何執行Python腳本
..........................

Your best way to get started with Python on Mac OS X is through the IDLE
integrated development environment, see section *note 整合化開發工具:
13a9. and use the Help menu when the IDE is running.

If you want to run Python scripts from the Terminal window command line
or from the Finder you first need an editor to create your script.  Mac
OS X comes with a number of standard Unix command line editors, ‘vim’
and ‘emacs’ among them.  If you want a more Mac-like editor, ‘BBEdit’ or
‘TextWrangler’ from Bare Bones Software (see
‘http://www.barebones.com/products/bbedit/index.html’) are good choices,
as is ‘TextMate’ (see ‘https://macromates.com/’).  Other editors include
‘Gvim’ (‘http://macvim-dev.github.io/macvim/’) and ‘Aquamacs’
(‘http://aquamacs.org/’).

To run your script from the Terminal window you must make sure that
‘/usr/local/bin’ is in your shell search path.

從Finder執行你的腳本時，你有兩個選項:

   * Drag it to ‘PythonLauncher’

   * Select ‘PythonLauncher’ as the default application to open your
     script (or any .py script) through the finder Info window and
     double-click it.  ‘PythonLauncher’ has various preferences to
     control how your script is launched.  Option-dragging allows you to
     change these for one invocation, or use its Preferences menu to
     change things globally.


File: python.info,  Node: 透過使用者圖形介面執行腳本,  Next: 設定,  Prev: 如何執行Python腳本,  Up: 取得和安裝MacPython

3.4.1.2 透過使用者圖形介面執行腳本
..................................

With older versions of Python, there is one Mac OS X quirk that you need
to be aware of: programs that talk to the Aqua window manager (in other
words, anything that has a GUI) need to be run in a special way.  Use
‘pythonw’ instead of ‘python’ to start such scripts.

With Python 3.8, you can use either ‘python’ or ‘pythonw’.


File: python.info,  Node: 設定,  Prev: 透過使用者圖形介面執行腳本,  Up: 取得和安裝MacPython

3.4.1.3 設定
............

Python on OS X honors all standard Unix environment variables such as
*note PYTHONPATH: 958, but setting these variables for programs started
from the Finder is non-standard as the Finder does not read your
‘.profile’ or ‘.cshrc’ at startup.  You need to create a file
‘~/.MacOSX/environment.plist’.  See Apple’s Technical Document QA1067
for details.

For more information on installation Python packages in MacPython, see
section *note Installing Additional Python Packages: 13ad.


File: python.info,  Node: 整合化開發工具,  Next: Installing Additional Python Packages,  Prev: 取得和安裝MacPython,  Up: 在麥金塔系統使用Python

3.4.2 整合化開發工具
--------------------

MacPython ships with the standard IDLE development environment.  A good
introduction to using IDLE can be found at
‘http://www.hashcollision.org/hkn/python/idle_intro/index.html’.


File: python.info,  Node: Installing Additional Python Packages,  Next: 圖形化使用者介面 GUI 程式開發於Mac,  Prev: 整合化開發工具,  Up: 在麥金塔系統使用Python

3.4.3 Installing Additional Python Packages
-------------------------------------------

There are several methods to install additional Python packages:

   * Packages can be installed via the standard Python distutils mode
     (‘python setup.py install’).

   * Many packages can also be installed via the ‘setuptools’ extension
     or ‘pip’ wrapper, see ‘https://pip.pypa.io/’.


File: python.info,  Node: 圖形化使用者介面 GUI 程式開發於Mac,  Next: 貢獻Python應用程式於 Mac,  Prev: Installing Additional Python Packages,  Up: 在麥金塔系統使用Python

3.4.4 圖形化使用者介面(GUI) 程式開發於Mac
-----------------------------------------

有許多建立圖形化使用者介面(GUI)應用程式選項使用Python於Mac上

`PyObjC' is a Python binding to Apple’s Objective-C/Cocoa framework,
which is the foundation of most modern Mac development.  Information on
PyObjC is available from ‘https://pypi.org/project/pyobjc/’.

The standard Python GUI toolkit is *note tkinter: 10d, based on the
cross-platform Tk toolkit (‘https://www.tcl.tk’).  An Aqua-native
version of Tk is bundled with OS X by Apple, and the latest version can
be downloaded and installed from ‘https://www.activestate.com’; it can
also be built from source.

`wxPython' is another popular cross-platform GUI toolkit that runs
natively on Mac OS X. Packages and documentation are available from
‘https://www.wxpython.org’.

`PyQt' is another popular cross-platform GUI toolkit that runs natively
on Mac OS X. More information can be found at
‘https://riverbankcomputing.com/software/pyqt/intro’.


File: python.info,  Node: 貢獻Python應用程式於 Mac,  Next: 其他資源,  Prev: 圖形化使用者介面 GUI 程式開發於Mac,  Up: 在麥金塔系統使用Python

3.4.5 貢獻Python應用程式於 Mac
------------------------------

The standard tool for deploying standalone Python applications on the
Mac is ‘py2app’.  More information on installing and using py2app can be
found at ‘http://undefined.org/python/#py2app’.


File: python.info,  Node: 其他資源,  Prev: 貢獻Python應用程式於 Mac,  Up: 在麥金塔系統使用Python

3.4.6 其他資源
--------------

MacPython 郵件清單對於Python使用者和開發者於Mac 上是一個極佳的支援資源

‘https://www.python.org/community/sigs/current/pythonmac-sig/’

其他好用的資源是MacPython wiki:

‘https://wiki.python.org/moin/MacPython’


File: python.info,  Node: Editors and IDEs,  Prev: 在麥金塔系統使用Python,  Up: Python Setup and Usage

3.5 Editors and IDEs
====================

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://www.python.org/dev/peps/pep-0008

   (2) https://wiki.python.org/moin/PythonEditors

   (3) https://wiki.python.org/moin/IntegratedDevelopmentEnvironments


File: python.info,  Node: The Python Language Reference,  Next: Python 標準函式庫 Standard Library,  Prev: Python Setup and Usage,  Up: Top

4 The Python Language Reference
*******************************

This reference manual describes the syntax and "core semantics" of the
language.  It is terse, but attempts to be exact and complete.  The
semantics of non-essential built-in object types and of the built-in
functions and modules are described in *note Python 標準函式庫 (Standard
Library): 1200.  For an informal introduction to the language, see *note
Python 教學: 11ff.  For C or C++ programmers, two additional manuals
exist: *note Extending and Embedding the Python Interpreter: 1202.
describes the high-level picture of how to write a Python extension
module, and the *note Python / C API 參考手冊: 1203. describes the
interfaces available to C/C++ programmers in detail.

* Menu:

* 簡介: 簡介<5>.
* Lexical analysis::
* Data model::
* Execution model::
* The import system::
* Expressions::
* Simple statements::
* Compound statements::
* Top-level components::
* 完整的語法規格書::


File: python.info,  Node: 簡介<5>,  Next: Lexical analysis,  Up: The Python Language Reference

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): 1200.  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) http://www.jython.org/

   (2) https://pythonnet.github.io/

   (3) http://ironpython.net/

   (4) http://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 BNF
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.


File: python.info,  Node: Lexical analysis,  Next: Data model,  Prev: 簡介<5>,  Up: The Python Language Reference

4.2 Lexical analysis
====================

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: 45d. is raised.

* Menu:

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

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3120


File: python.info,  Node: Line structure,  Next: Other tokens,  Up: Lexical analysis

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.  In
addition, if the first bytes of the file are the UTF-8 byte-order mark
(‘b'\xef\xbb\xbf'’), the declared file encoding is UTF-8 (this is
supported, among others, by Microsoft’s ‘notepad’).

If an encoding is declared, the encoding name must be recognized by
Python.  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:   # Looks like a valid date
             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: e7c. 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: Lexical analysis

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: Lexical analysis

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: 11b. 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' - uppercase letters

   * `Ll' - lowercase letters

   * `Lt' - titlecase letters

   * `Lm' - modifier letters

   * `Lo' - other letters

   * `Nl' - letter numbers

   * `Mn' - nonspacing marks

   * `Mc' - spacing combining marks

   * `Nd' - decimal numbers

   * `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 4.1 can be found at
‘https://www.unicode.org/Public/13.0.0/ucd/DerivedCoreProperties.txt’

* Menu:

* Keywords::
* Reserved classes of identifiers::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3131

   (2) https://www.python.org/dev/peps/pep-3131

   (3) http://www.unicode.org/Public/12.1.0/ucd/PropList.txt


File: python.info,  Node: Keywords,  Next: Reserved classes of identifiers,  Up: Identifiers and keywords

4.2.3.1 Keywords
................

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: Reserved classes of identifiers,  Prev: Keywords,  Up: Identifiers and keywords

4.2.3.2 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 *’.  The special identifier ‘_’
     is used in the interactive interpreter to store the result of the
     last evaluation; it is stored in the *note builtins: 13. module.
     When not in interactive mode, ‘_’ has no special meaning and is not
     defined.  See section *note The import statement: c22.

          備註: The name ‘_’ is often used in conjunction with
          internationalization; refer to the documentation for the *note
          gettext: 89. module for more information on this convention.

‘__*__’

     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: 513. 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): 13e4.


File: python.info,  Node: Literals,  Next: Operators,  Prev: Identifiers and keywords,  Up: Lexical analysis

4.2.4 Literals
--------------

Literals are notations for constant values of some built-in types.

* Menu:

* String and Bytes literals::
* String literal concatenation::
* Formatted string literals::
* Numeric literals::
* Integer 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: 13ea. or *note
bytesprefix: 13f3. 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: 13cc.

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 escape characters that otherwise have a special meaning, such
as newline, backslash itself, or the quote character.

Bytes literals are always prefixed with ‘'b'’ or ‘'B'’; they produce an
instance of the *note bytes: 336. type instead of the *note str: 335.
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 strings are called `raw strings' and treat
backslashes as literal characters.  As a result, in string literals,
‘'\U'’ and ‘'\u'’ escapes in raw strings are not treated specially.
Given that Python 2.x’s raw unicode literals behave differently than
Python 3.x’s the ‘'ur'’ syntax is not supported.

3.3 版新加入: The ‘'rb'’ prefix of raw bytes literals has been added as
a synonym of ‘'br'’.

3.3 版新加入: 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 Formatted string literals: 15d.  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 ‘"’.)

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       Meaning                               註解
                                                            
------------------------------------------------------------------------
                                                            
‘\newline’            Backslash and newline ignored
                      
                                                            
‘\\’                  Backslash (‘\’)
                      
                                                            
‘\'’                  Single quote (‘'’)
                      
                                                            
‘\"’                  Double quote (‘"’)
                      
                                                            
‘\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'      (1,3)
                                                            
                                                            
‘\xhh’                Character with hex value `hh'         (2,3)
                                                            

Escape sequences only recognized in string literals are:

Escape Sequence       Meaning                               註解
                                                            
------------------------------------------------------------------------
                                                            
‘\N{name}’            Character named `name' in the         (4)
                      Unicode database                      
                      
                                                            
‘\uxxxx’              Character with 16-bit hex value       (5)
                      `xxxx'                                
                      
                                                            
‘\Uxxxxxxxx’          Character with 32-bit hex value       (6)
                      `xxxxxxxx'                            
                      

註解：

  1. As in Standard C, up to three octal digits are accepted.

  2. Unlike in Standard C, exactly two hex digits are required.

  3. 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.

  4. 
     3.3 版更變: Support for name aliases (2) has been added.

  5. Exactly four hex digits are required.

  6. 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: 279.  In a future Python version they will be a
     *note SyntaxWarning: 192. and eventually a *note SyntaxError: 45d.

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.python.org/dev/peps/pep-0414

   (2) (1) ‘http://www.unicode.org/Public/11.0.0/ucd/NameAliases.txt’


File: python.info,  Node: String literal concatenation,  Next: Formatted string literals,  Prev: String and Bytes literals,  Up: Literals

4.2.4.2 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: Formatted string literals,  Next: Numeric literals,  Prev: String literal concatenation,  Up: Literals

4.2.4.3 Formatted string literals
.................................

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 | NULL | 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: c34. and assignment
expressions ‘:=’ must be surrounded by explicit parentheses.
Replacement expressions can contain line breaks (e.g.  in triple-quoted
strings), but they cannot contain comments.  Each expression is
evaluated in the context where the formatted string literal appears, in
order from left to right.

3.7 版更變: Prior to Python 3.7, an *note await: 1a4. expression and
comprehensions containing an *note async for: 2e4. clause were illegal
in the expressions in formatted string literals due to a problem with
the implementation.

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():
7d1. of the expression to be provided, unless there is a format
specified.  When a format is specified it defaults to the *note str():
335. of the expression unless a conversion ‘'!r'’ is declared.

3.8 版新加入: The equal sign ‘'='’.

If a conversion is specified, the result of evaluating the expression is
converted before formatting.  Conversion ‘'!s'’ calls *note str(): 335.
on the result, ‘'!r'’ calls *note repr(): 7d1, and ‘'!a'’ calls *note
ascii(): d51.

The result is then formatted using the *note format(): 4e0. protocol.
The format specifier is passed to the *note __format__(): 953. 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: 4e3, but may not include more deeply-nested
replacement fields.  The *note format specifier mini-language: 4e3. is
the same as that used by the string .format() 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" '

A consequence of sharing the same syntax as regular string literals is
that characters in the replacement fields must not conflict with the
quoting used in the outer formatted string literal:

     f"abc {a["x"]} def"    # error: outer string literal ended prematurely
     f"abc {a['x']} def"    # workaround: use different quoting

Backslashes are not allowed in format expressions and will raise an
error:

     f"newline: {ord('\n')}"  # raises SyntaxError

To include a value in which a backslash escape is required, create a
temporary variable.

     >>> newline = ord('\n')
     >>> f"newline: {newline}"
     'newline: 10'

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(): 4df, which uses a related format
string mechanism.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0498


File: python.info,  Node: Numeric literals,  Next: Integer literals,  Prev: Formatted string literals,  Up: Literals

4.2.4.4 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.5 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.6 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.

Some examples of floating point literals:

     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.7 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: Lexical analysis

4.2.5 Operators
---------------

The following tokens are operators:

     +       -       *       **      /       //      %      @
     <<      >>      &       |       ^       ~       :=
     <       >       <=      >=      ==      !=


File: python.info,  Node: Delimiters,  Prev: Operators,  Up: Lexical analysis

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: Data model,  Next: Execution model,  Prev: Lexical analysis,  Up: The Python Language Reference

4.3 Data model
==============

* Menu:

* Objects, values and types: Objects values and types.
* The standard type hierarchy::
* Special method names::
* Coroutines::


File: python.info,  Node: Objects values and types,  Next: The standard type hierarchy,  Up: Data model

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: ebf.’ operator
compares the identity of two objects; the *note id(): d8b. function
returns an integer representing its identity.

`CPython implementation detail:' 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(): 60d. 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 implementation detail:' 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: 86. 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: d77...*note
except: b43.’ 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:
d77...*note finally: 183.’ statement and the ’*note with: 6ee.’
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.  E.g., 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, but after ‘c = []; d = []’, ‘c’ and ‘d’ are
guaranteed to refer to two different, unique, newly created empty lists.
(Note that ‘c = d = []’ assigns the same object to both ‘c’ and ‘d’.)

   ---------- Footnotes ----------

   (1) (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: The standard type hierarchy,  Next: Special method names,  Prev: Objects values and types,  Up: Data model

4.3.2 The standard type hierarchy
---------------------------------

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.

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.

NotImplemented

     This type has a single value.  There is a single object with this
     value.  This object is accessed through the built-in name
     ‘NotImplemented’.  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.)  Its truth value is true.

     See *note Implementing the arithmetic operations: 1427. for more
     details.

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.

*note numbers.Number: 1428.

     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__(): 343. and *note __str__(): e3c, 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:

     *note numbers.Integral: 1429.

          These represent elements from the mathematical set of integers
          (positive and negative).

          There are two types of integers:

          Integers (*note int: 185.)

               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: 184.)

               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.

          The rules for integer representation are intended to give the
          most meaningful interpretation of shift and mask operations
          involving negative integers.

     *note numbers.Real: 142a. (*note float: 188.)

          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.

     *note numbers.Complex: 142b. (*note complex: 18a.)

          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’.

Sequences

     These represent finite ordered sets indexed by non-negative
     numbers.  The built-in function *note len(): 151. 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]’.

     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.  This implies
     that the index set is renumbered so that it starts at 0.

     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:

     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(): 142c. converts a code
               point from its string form to an integer in the range ‘0
               - 10FFFF’; *note chr(): 142d. converts an integer in the
               range ‘0 - 10FFFF’ to the corresponding length ‘1’ string
               object.  *note str.encode(): c3c. can be used to convert
               a *note str: 335. to *note bytes: 336. using the given
               text encoding, and *note bytes.decode(): c3d. 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(): 336. constructor can be used to create
               bytes objects.  Also, bytes objects can be decoded to
               strings via the *note decode(): c3d. method.

     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: 1273. (delete) statements.

          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(): 337. constructor.
               Aside from being mutable (and hence unhashable), byte
               arrays otherwise provide the same interface and
               functionality as immutable *note bytes: 336. objects.

          The extension module *note array: 7. provides an additional
          example of a mutable sequence type, as does the *note
          collections: 1e. module.

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(): 151. 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(): b74. 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(): bf3. constructor.  As a frozenset
          is immutable and *note hashable: 142e, it can be used again as
          an element of another set, or as a dictionary key.

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: 1273. statements.  The
     built-in function *note len(): 151. returns the number of items in
     a mapping.

     There is currently a single intrinsic mapping type:

     字典

          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: 653.).

          The extension modules *note dbm.ndbm: 35. and *note dbm.gnu:
          34. provide additional examples of mapping types, as does the
          *note collections: 1e. 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.

Callable types

     These are the types to which the function call operation (see
     section *note Calls: 651.) can be applied:

     User-defined functions

          A user-defined function object is created by a function
          definition (see section *note Function definitions: 1261.).
          It should be called with an argument list containing the same
          number of items as the function’s formal parameter list.

          Special attributes:

          Attribute                     Meaning
                                        
          ----------------------------------------------------------------------------------
                                                                            
          ‘__doc__’                     The function’s documentation        Writable
                                        string, or ‘None’ if unavailable;   
                                        not inherited by subclasses.
                                        
                                                                            
          *note __name__: c6c.          The function’s name.                Writable
                                                                            
                                                                            
          *note __qualname__: 142f.     The function’s                      Writable
                                        *note qualified name: 1430.         
                                        
                                        3.3 版新加入.
                                        
                                                                            
          ‘__module__’                  The name of the module the          Writable
                                        function was defined in, or         
                                        ‘None’ if unavailable.
                                        
                                                                            
          ‘__defaults__’                A tuple containing default          Writable
                                        argument values for those           
                                        arguments that have defaults, or
                                        ‘None’ if no arguments have a
                                        default value.
                                        
                                                                            
          ‘__code__’                    The code object representing the    Writable
                                        compiled function body.             
                                        
                                                                            
          ‘__globals__’                 A reference to the dictionary       Read-only
                                        that holds the function’s global    
                                        variables — the global namespace
                                        of the module in which the
                                        function was defined.
                                        
                                                                            
          *note __dict__: 501.          The namespace supporting            Writable
                                        arbitrary function attributes.      
                                        
                                                                            
          ‘__closure__’                 ‘None’ or a tuple of cells that     Read-only
                                        contain bindings for the            
                                        function’s free variables.  See
                                        below for information on the
                                        ‘cell_contents’ attribute.
                                        
                                                                            
          ‘__annotations__’             A dict containing annotations of    Writable
                                        parameters.  The keys of the dict   
                                        are the parameter names, and
                                        ‘'return'’ for the return
                                        annotation, if provided.
                                        
                                                                            
          ‘__kwdefaults__’              A dict containing defaults for      Writable
                                        keyword-only parameters.            
                                        

          Most of the attributes labelled "Writable" check the type of
          the assigned value.

          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.  `Note that the current
          implementation only supports function attributes on
          user-defined functions.  Function attributes on built-in
          functions may be supported in the future.'

          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.

          Additional information about a function’s definition can be
          retrieved from its code object; see the description of
          internal types below.  The *note cell: 1431. type can be
          accessed in the *note types: 119. module.

     Instance methods

          An instance method object combines a class, a class instance
          and any callable object (normally a user-defined function).

          Special read-only attributes: ‘__self__’ is the class instance
          object, ‘__func__’ is the function object; ‘__doc__’ is the
          method’s documentation (same as ‘__func__.__doc__’); *note
          __name__: c6c. is the method name (same as
          ‘__func__.__name__’); ‘__module__’ is 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 function object.

          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 function object or a class
          method object.

          When an instance method object is created by retrieving a
          user-defined function object from a class via one of its
          instances, its ‘__self__’ attribute is the instance, and the
          method object is said to be bound.  The new method’s
          ‘__func__’ attribute is the original function object.

          When an instance method object is created by retrieving a
          class method object from a class or instance, its ‘__self__’
          attribute is the class itself, and its ‘__func__’ attribute is
          the function object underlying the class method.

          When an instance method object is called, the underlying
          function (‘__func__’) is called, inserting the class instance
          (‘__self__’) 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 class method
          object, the "class instance" stored in ‘__self__’ 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.

          Note that the transformation from function object to instance
          method object happens each time the attribute is retrieved
          from the instance.  In some cases, a fruitful optimization is
          to assign the attribute to a local variable and call that
          local variable.  Also notice that this transformation only
          happens for user-defined functions; other callable objects
          (and all non-callable objects) are retrieved without
          transformation.  It is also 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.

     Generator functions

          A function or method which uses the *note yield: 190.
          statement (see section *note The yield statement: 190.) is
          called a `generator function'.  Such a function, when called,
          always returns an iterator object which can be used to execute
          the body of the function: calling the iterator’s *note
          iterator.__next__(): c69. method will cause the function to
          execute until it provides a value using the ‘yield’ statement.
          When the function executes a *note return: 191. statement or
          falls off the end, a *note StopIteration: 48b. exception is
          raised and the iterator will have reached the end of the set
          of values to be returned.

     Coroutine functions

          A function or method which is defined using *note async def:
          285. is called a `coroutine function'.  Such a function, when
          called, returns a *note coroutine: 1a7. object.  It may
          contain *note await: 1a4. expressions, as well as *note async
          with: 648. and *note async for: 2e4. statements.  See also the
          *note Coroutine Objects: 1432. section.

     Asynchronous generator functions

          A function or method which is defined using *note async def:
          285. and which uses the *note yield: 190. statement is called
          a `asynchronous generator function'.  Such a function, when
          called, returns an asynchronous iterator object which can be
          used in an *note async for: 2e4. statement to execute the body
          of the function.

          Calling the asynchronous iterator’s ‘aiterator.__anext__()’
          method will return an *note awaitable: 51e. which when awaited
          will execute until it provides a value using the *note yield:
          190. expression.  When the function executes an empty *note
          return: 191. statement or falls off the end, a *note
          StopAsyncIteration: 1017. exception is raised and the
          asynchronous iterator will have reached the end of the set of
          values to be yielded.

     Built-in functions

          A built-in function object is a wrapper around a C function.
          Examples of built-in functions are *note len(): 151. and *note
          math.sin(): e14. (*note math: b2. is a standard built-in
          module).  The number and type of the arguments are determined
          by the C function.  Special read-only attributes: ‘__doc__’ is
          the function’s documentation string, or ‘None’ if unavailable;
          *note __name__: c6c. is the function’s name; ‘__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.

     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'.

     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__(): 88e.  The
          arguments of the call are passed to *note __new__(): 88e. and,
          in the typical case, to *note __init__(): d63. to initialize
          the new instance.

     Class Instances

          Instances of arbitrary classes can be made callable by
          defining a *note __call__(): 1433. method in their class.

Modules

     Modules are a basic organizational unit of Python code, and are
     created by the *note import system: 1434. as invoked either by the
     *note import: c22. statement, or by calling functions such as *note
     importlib.import_module(): b18. and built-in *note __import__():
     615.  A module object has a namespace implemented by a dictionary
     object (this is the dictionary referenced by the ‘__globals__’
     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__: d17. is the
     module’s name; ‘__doc__’ is the module’s documentation string, or
     ‘None’ if unavailable; ‘__annotations__’ (optional) is a dictionary
     containing *note variable annotations: 624. collected during module
     body execution; *note __file__: ebc. is the pathname of the file
     from which the module was loaded, if it was loaded from a file.
     The *note __file__: ebc. 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 is the pathname of the shared library file.

     Special read-only attribute: *note __dict__: 501. is the module’s
     namespace as a dictionary object.

     `CPython implementation detail:' 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.

Custom classes

     Custom class types are typically created by class definitions (see
     section *note Class definitions: c6f.).  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 in the
     documentation accompanying the 2.3 release at
     ‘https://www.python.org/download/releases/2.3/mro/’.

     When a class attribute reference (for class ‘C’, say) would yield a
     class method object, it is transformed into an instance method
     object whose ‘__self__’ attribute is ‘C’.  When it would yield a
     static method object, it is transformed into the object wrapped by
     the static method object.  See section *note Implementing
     Descriptors: 4ee. for another way in which attributes retrieved
     from a class may differ from those actually contained in its *note
     __dict__: 501.

     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__: c6c. is the class name;
     ‘__module__’ is the module name in which the class was defined;
     *note __dict__: 501. is the dictionary containing the class’s
     namespace; *note __bases__: e0e. is a tuple containing the base
     classes, in the order of their occurrence in the base class list;
     ‘__doc__’ is the class’s documentation string, or ‘None’ if
     undefined; ‘__annotations__’ (optional) is a dictionary containing
     *note variable annotations: 624. collected during class body
     execution.

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 ‘__self__’ attribute is the instance.  Static method and
     class method objects are also transformed; see above under
     "Classes".  See section *note Implementing Descriptors: 4ee. 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__: 501.  If no class attribute is found, and
     the object’s class has a *note __getattr__(): 31f. 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__(): e31. or *note __delattr__(): 1435. 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: 513.

     Special attributes: *note __dict__: 501. is the attribute
     dictionary; *note __class__: e0f. is the instance’s class.

I/O objects (also known as file objects)

     A *note file object: b47. represents an open file.  Various
     shortcuts are available to create file objects: the *note open():
     4f5. built-in function, and also *note os.popen(): 2aa, *note
     os.fdopen(): 1436, and the *note makefile(): b1e. 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: c3e. abstract class.

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.

     Code objects

          Code objects represent `byte-compiled' executable Python code,
          or *note bytecode: 619.  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.

          Special read-only attributes: ‘co_name’ gives the function
          name; ‘co_argcount’ is the total number of positional
          arguments (including positional-only arguments and arguments
          with default values); ‘co_posonlyargcount’ is the number of
          positional-only arguments (including arguments with default
          values); ‘co_kwonlyargcount’ is the number of keyword-only
          arguments (including arguments with default values);
          ‘co_nlocals’ is the number of local variables used by the
          function (including arguments); ‘co_varnames’ is a tuple
          containing the names of the local variables (starting with the
          argument names); ‘co_cellvars’ is a tuple containing the names
          of local variables that are referenced by nested functions;
          ‘co_freevars’ is a tuple containing the names of free
          variables; ‘co_code’ is a string representing the sequence of
          bytecode instructions; ‘co_consts’ is a tuple containing the
          literals used by the bytecode; ‘co_names’ is a tuple
          containing the names used by the bytecode; ‘co_filename’ is
          the filename from which the code was compiled;
          ‘co_firstlineno’ is the first line number of the function;
          ‘co_lnotab’ is a string encoding the mapping from bytecode
          offsets to line numbers (for details see the source code of
          the interpreter); ‘co_stacksize’ is the required stack size;
          ‘co_flags’ is an integer encoding a number of flags for the
          interpreter.

          The following flag bits are defined for ‘co_flags’: 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.

          Future feature declarations (‘from __future__ import
          division’) also use bits in ‘co_flags’ 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 ‘co_flags’ are reserved for internal use.

          If a code object represents a function, the first item in
          ‘co_consts’ is the documentation string of the function, or
          ‘None’ if undefined.

     Frame objects

          Frame objects represent execution frames.  They may occur in
          traceback objects (see below), and are also passed to
          registered trace functions.

          Special read-only attributes: ‘f_back’ is to the previous
          stack frame (towards the caller), or ‘None’ if this is the
          bottom stack frame; ‘f_code’ is the code object being executed
          in this frame; ‘f_locals’ is the dictionary used to look up
          local variables; ‘f_globals’ is used for global variables;
          ‘f_builtins’ is used for built-in (intrinsic) names; ‘f_lasti’
          gives the precise instruction (this is an index into the
          bytecode string of the code object).

          Accessing ‘f_code’ raises an *note auditing event: e96.
          ‘object.__getattr__’ with arguments ‘obj’ and ‘"f_code"’.

          Special writable attributes: ‘f_trace’, if not ‘None’, is a
          function called for various events during code execution (this
          is used by the debugger).  Normally an event is triggered for
          each new source line - this can be disabled by setting
          ‘f_trace_lines’ to *note False: 38d.

          Implementations `may' allow per-opcode events to be requested
          by setting ‘f_trace_opcodes’ to *note True: 49e.  Note that
          this may lead to undefined interpreter behaviour if exceptions
          raised by the trace function escape to the function being
          traced.

          ‘f_lineno’ is 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 f_lineno.

          Frame objects support one method:

           -- 成員函式: frame.clear ()

               This method clears all references to local variables held
               by the frame.  Also, if the frame belonged to a
               generator, the generator is finalized.  This helps break
               reference cycles involving frame objects (for example
               when catching an exception and storing its traceback for
               later use).

               *note RuntimeError: 2bb. is raised if the frame is
               currently executing.

               3.4 版新加入.

     Traceback objects

          Traceback objects represent a stack trace of an exception.  A
          traceback object is implicitly created when an exception
          occurs, and may also be explicitly created by calling *note
          types.TracebackType: 33a.

          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: d77.)  It is accessible as the third item
          of the tuple returned by ‘sys.exc_info()’, and as the
          ‘__traceback__’ 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 ‘sys.last_traceback’.

          For explicitly created tracebacks, it is up to the creator of
          the traceback to determine how the ‘tb_next’ attributes should
          be linked to form a full stack trace.

          Special read-only attributes: ‘tb_frame’ points to the
          execution frame of the current level; ‘tb_lineno’ gives the
          line number where the exception occurred; ‘tb_lasti’ indicates
          the precise instruction.  The line number and last instruction
          in the traceback may differ from the line number of its frame
          object if the exception occurred in a *note try: d77.
          statement with no matching except clause or with a finally
          clause.

          Accessing ‘tb_frame’ raises an *note auditing event: e96.
          ‘object.__getattr__’ with arguments ‘obj’ and ‘"tb_frame"’.

          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 版更變: Traceback objects can now be explicitly
          instantiated from Python code, and the ‘tb_next’ attribute of
          existing instances can be updated.

     Slice objects

          Slice objects are used to represent slices for *note
          __getitem__(): 27d. methods.  They are also created by the
          built-in *note slice(): e09. function.

          Special read-only attributes: ‘start’ is the lower bound;
          ‘stop’ is the upper bound; ‘step’ 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.

     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 not themselves callable, although the objects they
          wrap usually are.  Static method objects are created by the
          built-in *note staticmethod(): 1da. constructor.

     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 "User-defined methods".  Class method
          objects are created by the built-in *note classmethod(): 1d9.
          constructor.


File: python.info,  Node: Special method names,  Next: Coroutines,  Prev: The standard type hierarchy,  Up: Data model

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__(): 27d, 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: 3a0. or *note TypeError: 193.).

Setting a special method to ‘None’ indicates that the corresponding
operation is not available.  For example, if a class sets *note
__iter__(): 514. to ‘None’, the class is not iterable, so calling *note
iter(): d2c. on its instances will raise a *note TypeError: 193.
(without falling back to *note __getitem__(): 27d.).  (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::
* Special method lookup::

   ---------- Footnotes ----------

   (1) (2) The *note __hash__(): 345, *note __iter__(): 514, *note
__reversed__(): 534, and *note __contains__(): d2d. methods have special
handling for this; others will still raise a *note TypeError: 193, 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__():
     88e. 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__(): 88e. 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__(): 88e. method using
     ‘super().__new__(cls[, ...])’ with appropriate arguments and then
     modifying the newly-created instance as necessary before returning
     it.

     If *note __new__(): 88e. is invoked during object construction and
     it returns an instance or subclass of `cls', then the new
     instance’s *note __init__(): d63. 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__(): 88e. does not return an instance of `cls', then
     the new instance’s *note __init__(): d63. method will not be
     invoked.

     *note __new__(): 88e. 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__():
     88e.), 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__(): d63. method, the derived class’s *note
     __init__(): d63. 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__(): 88e. and *note __init__(): d63. work
     together in constructing objects (*note __new__(): 88e. to create
     it, and *note __init__(): d63. to customize it), no non-‘None’
     value may be returned by *note __init__(): d63.; doing so will
     cause a *note TypeError: 193. 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__(): 924. method, the derived class’s *note
     __del__(): 924. 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__():
     924. 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__(): 924. is called a
     second time when a resurrected object is about to be destroyed; the
     current *note CPython: 143b. implementation only calls it once.

     It is not guaranteed that *note __del__(): 924. methods are called
     for objects that still exist when the interpreter exits.

          備註: ‘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 implementation detail:' 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: ecd.  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: 86. module.

          警告: Due to the precarious circumstances under which *note
          __del__(): 924. methods are invoked, exceptions that occur
          during their execution are ignored, and a warning is printed
          to ‘sys.stderr’ instead.  In particular:

             * *note __del__(): 924. can be invoked when arbitrary code
               is being executed, including from any arbitrary thread.
               If *note __del__(): 924. 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__(): 924.

             * *note __del__(): 924. 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__(): 924.
               method is called.

 -- 成員函式: object.__repr__ (self)

     Called by the *note repr(): 7d1. 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__(): 343. but not *note __str__(): e3c, then *note
     __repr__(): 343. 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): 335. and the built-in functions *note
     format(): 4e0. and *note print(): 88b. to compute the "informal" or
     nicely printable string representation of an object.  The return
     value must be a *note string: 1228. object.

     This method differs from *note object.__repr__(): 343. in that
     there is no expectation that *note __str__(): e3c. 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: 2b1. calls *note object.__repr__(): 343.

 -- 成員函式: object.__bytes__ (self)

     Called by *note bytes: 10c2. to compute a byte-string
     representation of an object.  This should return a *note bytes:
     336. object.

 -- 成員函式: object.__format__ (self, format_spec)

     Called by the *note format(): 4e0. built-in function, and by
     extension, evaluation of *note formatted string literals: 15d. and
     the *note str.format(): 4df. 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__(): 953, 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 Mini-Language: 4e3. 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: 193. if passed any non-empty string.

     3.7 版更變: ‘object.__format__(x, '')’ is now equivalent to
     ‘str(x)’ rather than ‘format(str(self), '')’.

 -- 成員函式: 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 ‘NotImplemented’
     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(): 184. on the value to determine if the result is true
     or false.

     By default, ‘object’ implements *note __eq__(): 344. by using ‘is’,
     returning ‘NotImplemented’ in the case of a false comparison: ‘True
     if x is y else NotImplemented’.  For *note __ne__(): e5b, by
     default it delegates to *note __eq__(): 344. 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(): 850.

     See the paragraph on *note __hash__(): 345. for some important
     notes on creating *note hashable: 142e. 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__(): c39. and *note __gt__():
     ca6. are each other’s reflection, *note __le__(): ca5. and *note
     __ge__(): ca7. are each other’s reflection, and *note __eq__():
     344. and *note __ne__(): e5b. are their own reflection.  If the
     operands are of different types, and 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.

 -- 成員函式: object.__hash__ (self)

     Called by built-in function *note hash(): 9c9. and for operations
     on members of hashed collections including *note set: b74, *note
     frozenset: bf3, and *note dict: 1b9.  *note __hash__(): 345. 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(): 9c9. truncates the value returned from an
          object’s custom *note __hash__(): 345. method to the size of a
          ‘Py_ssize_t’.  This is typically 8 bytes on 64-bit builds and
          4 bytes on 32-bit builds.  If an object’s *note __hash__():
          345. 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__(): 344. method it should
     not define a *note __hash__(): 345. operation either; if it defines
     *note __eq__(): 344. but not *note __hash__(): 345, its instances
     will not be usable as items in hashable collections.  If a class
     defines mutable objects and implements an *note __eq__(): 344.
     method, it should not implement *note __hash__(): 345, since the
     implementation of hashable 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__(): 344. and *note
     __hash__(): 345. 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__(): 344. and does not define
     *note __hash__(): 345. will have its *note __hash__(): 345.
     implicitly set to ‘None’.  When the *note __hash__(): 345. method
     of a class is ‘None’, instances of the class will raise an
     appropriate *note TypeError: 193. 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__(): 344. needs to retain the
     implementation of *note __hash__(): 345. 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__(): 344. wishes to
     suppress hash support, it should include ‘__hash__ = None’ in the
     class definition.  A class which defines its own *note __hash__():
     345. that explicitly raises a *note TypeError: 193. would be
     incorrectly identified as hashable by an ‘isinstance(obj,
     collections.abc.Hashable)’ call.

          備註: By default, the *note __hash__(): 345. 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://www.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).

          See also *note PYTHONHASHSEED: 9ca.

     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__(): dd0. is called, if it is defined, and the
     object is considered true if its result is nonzero.  If a class
     defines neither *note __len__(): dd0. nor *note __bool__(): c6d,
     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: 3a0. (either *note __getattribute__(): 44e. raises
     an *note AttributeError: 3a0. because `name' is not an instance
     attribute or an attribute in the class tree for ‘self’; or *note
     __get__(): 1440. of a `name' property raises *note AttributeError:
     3a0.).  This method should either return the (computed) attribute
     value or raise an *note AttributeError: 3a0. exception.

     Note that if the attribute is found through the normal mechanism,
     *note __getattr__(): 31f. is not called.  (This is an intentional
     asymmetry between *note __getattr__(): 31f. and *note
     __setattr__(): e31.)  This is done both for efficiency reasons and
     because otherwise *note __getattr__(): 31f. would have no way to
     access other attributes of the instance.  Note that at least for
     instance variables, you can fake total control by not inserting any
     values in the instance attribute dictionary (but instead inserting
     them in another object).  See the *note __getattribute__(): 44e.
     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__(): 31f, the latter will not be called unless *note
     __getattribute__(): 44e. either calls it explicitly or raises an
     *note AttributeError: 3a0.  This method should return the
     (computed) attribute value or raise an *note AttributeError: 3a0.
     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 built-in functions.  See *note Special
          method lookup: 1441.

     For certain sensitive attribute accesses, raises an *note auditing
     event: e96. ‘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__(): e31. 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: e96. ‘object.__setattr__’ with arguments ‘obj’,
     ‘name’, ‘value’.

 -- 成員函式: object.__delattr__ (self, name)

     Like *note __setattr__(): e31. 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: e96. ‘object.__delattr__’ with arguments ‘obj’ and ‘name’.

 -- 成員函式: object.__dir__ (self)

     Called when *note dir(): d38. is called on the object.  A sequence
     must be returned.  *note dir(): d38. converts the returned sequence
     to a list and sorts it.

* Menu:

* Customizing module attribute access::
* Implementing Descriptors::
* Invoking Descriptors::
* __slots__::


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: 3a0.  If an
attribute is not found on a module object through the normal lookup,
i.e.  *note object.__getattribute__(): 44e, then ‘__getattr__’ is
searched in the module ‘__dict__’ before raising an *note
AttributeError: 3a0.  If found, it is called with the attribute name and
the result is returned.

The ‘__dir__’ function should accept no arguments, and return a sequence
of strings that represents the names accessible on module.  If present,
this function overrides the standard *note dir(): d38. 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: 6f6.  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) - Module __getattr__ and __dir__

     Describes the ‘__getattr__’ and ‘__dir__’ functions on modules.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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__: 501.

 -- 成員函式: 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: 3a0. exception.

     PEP 252(1) specifies that *note __get__(): 1440. 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__(): 44e. 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__(): 1444. or *note __delete__(): 1445.
     changes the kind of descriptor to a "data descriptor".  See *note
     Invoking Descriptors: 1446. for more details.

 -- 成員函式: object.__delete__ (self, instance)

     Called to delete the attribute on an instance `instance' of the
     owner class.

 -- 成員函式: object.__set_name__ (self, owner, name)

     Called at the time the owning class `owner' is created.  The
     descriptor has been assigned to `name'.

          備註: *note __set_name__(): 4ed. is only called implicitly as
          part of the *note type: 60d. constructor, so it will need to
          be called explicitly with the appropriate parameters when a
          descriptor is added to a class after initial creation:

               class A:
                  pass
               descr = custom_descriptor()
               A.attr = descr
               descr.__set_name__(A, 'attr')

          See *note Creating the class object: 4e9. for more details.

     3.6 版新加入.

The attribute ‘__objclass__’ is interpreted by the *note inspect: a1.
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://www.python.org/dev/peps/pep-0252


File: python.info,  Node: Invoking Descriptors,  Next: __slots__,  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__(): 1440, *note __set__(): 1444, and
*note __delete__(): 1445.  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

     If ‘a’ is an instance of *note super: 4e7, then the binding
     ‘super(B, obj).m()’ searches ‘obj.__class__.__mro__’ for the base
     class ‘A’ immediately preceding ‘B’ and then invokes the descriptor
     with the call: ‘A.__dict__['m'].__get__(obj, obj.__class__)’.

For instance bindings, the precedence of descriptor invocation depends
on which descriptor methods are defined.  A descriptor can define any
combination of *note __get__(): 1440, *note __set__(): 1444. and *note
__delete__(): 1445.  If it does not define *note __get__(): 1440, 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 *note __set__(): 1444. and/or *note __delete__(): 1445, it is a
data descriptor; if it defines neither, it is a non-data descriptor.
Normally, data descriptors define both *note __get__(): 1440. and *note
__set__(): 1444, while non-data descriptors have just the *note
__get__(): 1440. method.  Data descriptors with *note __set__(): 1444.
and *note __get__(): 1440. defined always override a redefinition in an
instance dictionary.  In contrast, non-data descriptors can be
overridden by instances.

Python methods (including *note staticmethod(): 1da. and *note
classmethod(): 1d9.) 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(): 1d8. function is implemented as a data descriptor.
Accordingly, instances cannot override the behavior of a property.


File: python.info,  Node: __slots__,  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 `__dict__' and `__weakref__'
(unless explicitly declared in `__slots__' or available in a parent.)

The space saved over using `__dict__' can be significant.  Attribute
lookup speed can be significantly improved as well.

 -- Data: 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 `__dict__' and `__weakref__' for each
     instance.

* Menu:

* Notes on using __slots__::


File: python.info,  Node: Notes on using __slots__,  Up: __slots__

4.3.3.7 Notes on using `__slots__'
..................................

   * When inheriting from a class without `__slots__', the `__dict__'
     and `__weakref__' attribute of the instances will always be
     accessible.

   * Without a `__dict__' variable, instances cannot be assigned new
     variables not listed in the `__slots__' definition.  Attempts to
     assign to an unlisted variable name raises *note AttributeError:
     3a0.  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 weak references 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
     descriptors (*note Implementing Descriptors: 4ee.) 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 `__dict__'
     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.

   * Nonempty `__slots__' does not work for classes derived from
     "variable-length" built-in types such as *note int: 185, *note
     bytes: 336. and *note tuple: 483.

   * Any non-string iterable may be assigned to `__slots__'.  Mappings
     may also be used; however, in the future, special meaning may be
     assigned to the values corresponding to each key.

   * `__class__' assignment works only if both classes have the same
     `__slots__'.

   * Multiple inheritance 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: 193.

   * If an iterator is used for `__slots__' then a descriptor 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.8 Customizing class creation
..................................

Whenever a class inherits from another class, `__init_subclass__' is
called on that 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’s class ‘__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 版新加入.

* 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.9 Metaclasses
...................

By default, classes are constructed using *note type(): 60d.  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.10 Resolving MRO entries
..............................

If a base that appears in class definition is not an instance of *note
type: 60d, then an ‘__mro_entries__’ method is searched on it.  If
found, it is called with the original bases tuple.  This method must
return a tuple of classes that will be used instead of this base.  The
tuple may be empty, in such case the original base is ignored.

也參考
......

PEP 560(1) - Core support for typing module and generic types

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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.11 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():
     60d. is used;

   * if an explicit metaclass is given and it is `not' an instance of
     *note type(): 60d, then it is used directly as the metaclass;

   * if an instance of *note type(): 60d. 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.12 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(): 1d9.  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://www.python.org/dev/peps/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.13 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():
c49. 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.14 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(): 4e7.  ‘__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(): 4e7. 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 implementation detail:' 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: 2bb. in Python
3.8.

When using the default metaclass *note type: 60d, or any metaclass that
ultimately calls ‘type.__new__’, the following additional customisation
steps are invoked after creating the class object:

   * first, ‘type.__new__’ collects all of the descriptors in the class
     namespace that define a *note __set_name__(): 4ed. method;

   * second, all of these ‘__set_name__’ methods are called with the
     class being defined and the assigned name of that particular
     descriptor;

   * finally, the *note __init_subclass__(): 4e8. 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__: 501. attribute of the class
object.

也參考
......

PEP 3135(1) - New super

     Describes the implicit ‘__class__’ closure reference

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3135


File: python.info,  Node: Uses for metaclasses,  Prev: Creating the class object,  Up: Customizing class creation

4.3.3.15 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.16 Customizing instance and subclass checks
.................................................

The following methods are used to override the default behavior of the
*note isinstance(): 454. and *note issubclass(): 455. built-in
functions.

In particular, the metaclass *note abc.ABCMeta: 81e. 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(): 454.
     and *note issubclass(): 455. behavior through *note
     __instancecheck__(): 1455. and *note __subclasscheck__(): 1456,
     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://www.python.org/dev/peps/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.17 Emulating generic types
................................

One can implement the generic class syntax as specified by PEP 484(1)
(for example ‘List[int]’) by defining a special method:

 -- 成員函式: classmethod object.__class_getitem__ (cls, key)

     Return an object representing the specialization of a generic class
     by type arguments found in `key'.

This method is looked up on the class object itself, and when defined in
the class body, this method is implicitly a class method.  Note, this
mechanism is primarily reserved for use with static type hints, other
usage is discouraged.

也參考
......

PEP 560(2) - Core support for typing module and generic types

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0484

   (2) https://www.python.org/dev/peps/pep-0560


File: python.info,  Node: Emulating callable objects,  Next: Emulating container types,  Prev: Emulating generic types,  Up: Special method names

4.3.3.18 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.19 Emulating container types
..................................

The following methods can be defined to implement container objects.
Containers usually are sequences (such as lists or tuples) or mappings
(like dictionaries), 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 slice 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 dictionary objects.  The *note collections.abc: 1f.
module provides a *note MutableMapping: 9f4. abstract base class to help
create those methods from a base set of *note __getitem__(): 27d, *note
__setitem__(): c67, *note __delitem__(): c68, and ‘keys()’.  Mutable
sequences should provide methods ‘append()’, ‘count()’, ‘index()’,
‘extend()’, ‘insert()’, ‘pop()’, ‘remove()’, ‘reverse()’ and ‘sort()’,
like Python standard list objects.  Finally, sequence types should
implement addition (meaning concatenation) and multiplication (meaning
repetition) by defining the methods *note __add__(): 145c, *note
__radd__(): 145d, *note __iadd__(): e74, *note __mul__(): 145e, *note
__rmul__(): 145f. and *note __imul__(): 1460. described below; they
should not define other numerical operators.  It is recommended that
both mappings and sequences implement the *note __contains__(): d2d.
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__(): 514. method to allow efficient
iteration through the container; for mappings, *note __iter__(): 514.
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(): 151.  Should
     return the length of the object, an integer ‘>=’ 0.  Also, an
     object that doesn’t define a *note __bool__(): c6d. method and
     whose *note __len__(): dd0. method returns zero is considered to be
     false in a Boolean context.

     `CPython implementation detail:' In CPython, the length is required
     to be at most *note sys.maxsize: b48.  If the length is larger than
     ‘sys.maxsize’ some features (such as *note len(): 151.) may raise
     *note OverflowError: 965.  To prevent raising ‘OverflowError’ by
     truth value testing, an object must define a *note __bool__(): c6d.
     method.

 -- 成員函式: object.__length_hint__ (self)

     Called to implement *note operator.length_hint(): 882.  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: 851, 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 sequence types,
     the accepted keys should be integers and slice objects.  Note that
     the special interpretation of negative indexes (if the class wishes
     to emulate a sequence type) is up to the *note __getitem__(): 27d.
     method.  If `key' is of an inappropriate type, *note TypeError:
     193. may be raised; if of a value outside the set of indexes for
     the sequence (after any special interpretation of negative values),
     *note IndexError: e7a. should be raised.  For mapping types, if
     `key' is missing (not in the container), *note KeyError: 2c8.
     should be raised.

          備註: *note for: c35. loops expect that an *note IndexError:
          e7a. will be raised for illegal indexes to allow proper
          detection of the end of the sequence.

 -- 成員函式: object.__setitem__ (self, key, value)

     Called to implement assignment to ‘self[key]’.  Same note as for
     *note __getitem__(): 27d.  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__(): 27d. method.

 -- 成員函式: object.__delitem__ (self, key)

     Called to implement deletion of ‘self[key]’.  Same note as for
     *note __getitem__(): 27d.  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__(): 27d. method.

 -- 成員函式: object.__missing__ (self, key)

     Called by *note dict: 1b9.*note __getitem__(): 27d. to implement
     ‘self[key]’ for dict subclasses when key is not in the dictionary.

 -- 成員函式: object.__iter__ (self)

     This method is called when an iterator 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.

     Iterator objects also need to implement this method; they are
     required to return themselves.  For more information on iterator
     objects, see *note Iterator Types: 1461.

 -- 成員函式: object.__reversed__ (self)

     Called (if present) by the *note reversed(): 18f. 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__(): 534. method is not provided, the *note
     reversed(): 18f. built-in will fall back to using the sequence
     protocol (*note __len__(): dd0. and *note __getitem__(): 27d.).
     Objects that support the sequence protocol should only provide
     *note __reversed__(): 534. if they can provide an implementation
     that is more efficient than the one provided by *note reversed():
     18f.

The membership test operators (*note in: 7a8. and *note not in: 1462.)
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__(): d2d, the
     membership test first tries iteration via *note __iter__(): 514,
     then the old sequence iteration protocol via *note __getitem__():
     27d, see *note this section in the language reference: 1463.


File: python.info,  Node: Emulating numeric types,  Next: With Statement Context Managers,  Prev: Emulating container types,  Up: Special method names

4.3.3.20 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():
     153, *note pow(): 19b, ‘**’, ‘<<’, ‘>>’, ‘&’, ‘^’, ‘|’).  For
     instance, to evaluate the expression ‘x + y’, where `x' is an
     instance of a class that has an *note __add__(): 145c. method,
     ‘x.__add__(y)’ is called.  The *note __divmod__(): 78c. method
     should be the equivalent to using *note __floordiv__(): e3a. and
     *note __mod__(): 1467.; it should not be related to *note
     __truediv__(): 78b.  Note that *note __pow__(): 1468. should be
     defined to accept an optional third argument if the ternary version
     of the built-in *note pow(): 19b. function is to be supported.

     If one of those methods does not support the operation with the
     supplied arguments, it should return ‘NotImplemented’.

 -- 成員函式: 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():
     153, *note pow(): 19b, ‘**’, ‘<<’, ‘>>’, ‘&’, ‘^’, ‘|’) 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__(): 146e. method, ‘y.__rsub__(x)’
     is called if ‘x.__sub__(y)’ returns `NotImplemented'.

     Note that ternary *note pow(): 19b. will not try calling *note
     __rpow__(): 1472. (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, the augmented assignment falls back to the
     normal methods.  For instance, if `x' is an instance of a class
     with an *note __iadd__(): e74. method, ‘x += y’ is equivalent to ‘x
     = x.__iadd__(y)’ .  Otherwise, ‘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?: 1481.), but this behavior is in fact part of
     the data model.

          備註: Due to a bug in the dispatching mechanism for ‘**=’, a
          class that defines *note __ipow__(): 147b. but returns
          ‘NotImplemented’ would fail to fall back to ‘x.__pow__(y)’ and
          ‘y.__rpow__(x)’.  This bug is fixed in Python 3.10.

 -- 成員函式: object.__neg__ (self)
 -- 成員函式: object.__pos__ (self)
 -- 成員函式: object.__abs__ (self)
 -- 成員函式: object.__invert__ (self)

     Called to implement the unary arithmetic operations (‘-’, ‘+’,
     *note abs(): 12c4. and ‘~’).

 -- 成員函式: object.__complex__ (self)
 -- 成員函式: object.__int__ (self)
 -- 成員函式: object.__float__ (self)

     Called to implement the built-in functions *note complex(): 18a,
     *note int(): 185. and *note float(): 188.  Should return a value of
     the appropriate type.

 -- 成員函式: object.__index__ (self)

     Called to implement *note operator.index(): 1486, 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(): c45,
     *note hex(): c6b. and *note oct(): c6a. functions).  Presence of
     this method indicates that the numeric object is an integer type.
     Must return an integer.

     If *note __int__(): 18c, *note __float__(): 18d. and *note
     __complex__(): 18e. are not defined then corresponding built-in
     functions *note int(): 185, *note float(): 188. and *note
     complex(): 18a. fall back to *note __index__(): 18b.

 -- 成員函式: object.__round__ (self[, ndigits])
 -- 成員函式: object.__trunc__ (self)
 -- 成員函式: object.__floor__ (self)
 -- 成員函式: object.__ceil__ (self)

     Called to implement the built-in function *note round(): c72. and
     *note math: b2. functions *note trunc(): d33, *note floor(): d31.
     and *note ceil(): d32.  Unless `ndigits' is passed to ‘__round__()’
     all these methods should return the value of the object truncated
     to an *note Integral: 1429. (typically an *note int: 185.).

     If *note __int__(): 18c. is not defined then the built-in function
     *note int(): 185. falls back to *note __trunc__(): 1488.

   ---------- Footnotes ----------

   (1) (3) "Does not support" here means that the class has no such
method, or the method returns ‘NotImplemented’.  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) (4) For operands of the same type, it is assumed that if the
non-reflected method – such as *note __add__(): 145c. – 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: Special method lookup,  Prev: Emulating numeric types,  Up: Special method names

4.3.3.21 With Statement Context Managers
........................................

A `context manager' is an object that defines the runtime context to be
established when executing a *note with: 6ee. 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: 6ee.), 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 Context Manager
Types: 148d.

 -- 成員函式: object.__enter__ (self)

     Enter the runtime context related to this object.  The *note with:
     6ee. 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: 158.

     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__(): c9b. methods should not reraise the
     passed-in exception; this is the caller’s responsibility.

也參考
......

PEP 343(1) - The "with" statement

     The specification, background, and examples for the Python *note
     with: 6ee. statement.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0343


File: python.info,  Node: Special method lookup,  Prev: With Statement Context Managers,  Up: Special method names

4.3.3.22 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__(): 345. and *note __repr__(): 343. 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__(): 44e. 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__(): 44e. 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: Coroutines,  Prev: Special method names,  Up: Data model

4.3.4 Coroutines
----------------

* Menu:

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


File: python.info,  Node: Awaitable Objects,  Next: Coroutine Objects,  Up: Coroutines

4.3.4.1 Awaitable Objects
.........................

An *note awaitable: 51e. object generally implements an *note
__await__(): 647. method.  *note Coroutine objects: 1a7. returned from
*note async def: 285. functions are awaitable.

     備註: The *note generator iterator: 45c. objects returned from
     generators decorated with *note types.coroutine(): 781. or *note
     asyncio.coroutine(): 283. are also awaitable, but they do not
     implement *note __await__(): 647.

 -- 成員函式: object.__await__ (self)

     Must return an *note iterator: 1040.  Should be used to implement
     *note awaitable: 51e. objects.  For instance, *note asyncio.Future:
     448. implements this method to be compatible with the *note await:
     1a4. expression.

3.5 版新加入.

也參考
......

PEP 492(1) for additional information about awaitable objects.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0492


File: python.info,  Node: Coroutine Objects,  Next: Asynchronous Iterators,  Prev: Awaitable Objects,  Up: Coroutines

4.3.4.2 Coroutine Objects
.........................

*note Coroutine objects: 1a7. are *note awaitable: 51e. objects.  A
coroutine’s execution can be controlled by calling *note __await__():
647. and iterating over the result.  When the coroutine has finished
executing and returns, the iterator raises *note StopIteration: 48b, and
the exception’s ‘value’ 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: 48b.
exceptions.

Coroutines also have the methods listed below, which are analogous to
those of generators (see *note Generator-iterator methods: 1492.).
However, unlike generators, coroutines do not directly support
iteration.

3.5.2 版更變: It is a *note RuntimeError: 2bb. 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__(): 647.  If `value' is not ‘None’, this method
     delegates to the *note send(): 1494. method of the iterator that
     caused the coroutine to suspend.  The result (return value, *note
     StopIteration: 48b, or other exception) is the same as when
     iterating over the *note __await__(): 647. return value, described
     above.

 -- 成員函式: coroutine.throw (type[, value[, traceback]])

     Raises the specified exception in the coroutine.  This method
     delegates to the *note throw(): 1496. 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: 48b, or other exception)
     is the same as when iterating over the *note __await__(): 647.
     return value, described above.  If the exception is not caught in
     the coroutine, it propagates back to the caller.

 -- 成員函式: coroutine.close ()

     Causes the coroutine to clean itself up and exit.  If the coroutine
     is suspended, this method first delegates to the *note close():
     1498. method of the iterator that caused the coroutine to suspend,
     if it has such a method.  Then it raises *note GeneratorExit: d37.
     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: Coroutines

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: 2e4.
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: 1017. 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, ‘__aiter__’ could return an `awaitable'
that would resolve to an *note asynchronous iterator: 64a.

Starting with Python 3.7, ‘__aiter__’ must return an asynchronous
iterator object.  Returning anything else will result in a *note
TypeError: 193. error.


File: python.info,  Node: Asynchronous Context Managers,  Prev: Asynchronous Iterators,  Up: Coroutines

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: 648.
statement.

 -- 成員函式: object.__aenter__ (self)

     Semantically similar to *note __enter__(): c9a, the only difference
     being that it must return an `awaitable'.

 -- 成員函式: object.__aexit__ (self, exc_type, exc_value, traceback)

     Semantically similar to *note __exit__(): c9b, 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: Execution model,  Next: The import system,  Prev: Data model,  Up: The Python Language Reference

4.4 Execution model
===================

* Menu:

* Structure of a program::
* Naming and binding::
* Exceptions::


File: python.info,  Node: Structure of a program,  Next: Naming and binding,  Up: Execution model

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: 1210. option) is a code
block.  The string argument passed to the built-in functions *note
eval(): b95. and *note exec(): c49. 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: Exceptions,  Prev: Structure of a program,  Up: Execution model

4.4.2 Naming and binding
------------------------

* Menu:

* Binding of names::
* Resolution of names::
* 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,
*note import: c22. statements, class and function definitions (these
bind the class or function name in the defining block), and targets that
are identifiers if occurring in an assignment, *note for: c35. loop
header, or after ‘as’ in a *note with: 6ee. statement or *note except:
b43. clause.  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: 1273. 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: c44. or *note global: 1249.  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: Builtins and restricted execution,  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: d80. 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: e7b. exception is
raised.  *note UnboundLocalError: e7b. is a subclass of *note NameError:
d80.

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.

If the *note global: 1249. statement occurs within a block, all uses of
the name specified in the statement refer to the binding of that name 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: 13.  The global namespace is searched first.
If the name is not found there, the builtins namespace is searched.  The
‘global’ statement must precede all uses of the name.

The *note global: 1249. 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: c44. statement causes corresponding names to refer
to previously bound variables in the nearest enclosing function scope.
*note SyntaxError: 45d. is raised at compile time if the given name does
not exist in any enclosing function scope.

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(): c49. and *note
eval(): b95. 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 since
they are implemented using a function scope.  This means that the
following will fail:

     class A:
         a = 42
         b = list(a + i for i in range(10))


File: python.info,  Node: Builtins and restricted execution,  Next: Interaction with dynamic features,  Prev: Resolution of names,  Up: Naming and binding

4.4.2.3 Builtins and restricted execution
.........................................

`CPython implementation detail:' Users should not touch ‘__builtins__’;
it is strictly an implementation detail.  Users wanting to override
values in the builtins namespace should *note import: c22. the *note
builtins: 13. 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: 13.; when in any other module, ‘__builtins__’ is an alias for
the dictionary of the *note builtins: 13. module itself.


File: python.info,  Node: Interaction with dynamic features,  Prev: Builtins and restricted execution,  Up: Naming and binding

4.4.2.4 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(): b95. and *note exec(): c49. 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(): c49. and *note eval(): b95.
functions have optional arguments to override the global and local
namespace.  If only one namespace is specified, it is used for both.

   ---------- Footnotes ----------

   (1) (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: Exceptions,  Prev: Naming and binding,  Up: Execution model

4.4.3 Exceptions
----------------

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: c47. statement.  Exception
handlers are specified with the *note try: d77. ...  *note except: b43.
statement.  The *note finally: 183. 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: 601.

Exceptions are identified by class instances.  The *note except: b43.
clause is selected depending on the class of the instance: it must
reference the class of the instance or a base class 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: d77. statement in section
*note The try statement: d77. and *note raise: c47. statement in section
*note The raise statement: c47.

註解
....


File: python.info,  Node: The import system,  Next: Expressions,  Prev: Execution model,  Up: The Python Language Reference

4.5 The import system
=====================

Python code in one *note module: 14b2. gains access to the code in
another module by the process of *note importing: 14b3. it.  The *note
import: c22. 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(): b18. and built-in *note __import__(): 615.
can also be used to invoke the import machinery.

The *note import: c22. 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__(): 615. function, with the
appropriate arguments.  The return value of *note __import__(): 615. 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__(): 615. 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: f2b.), only
the *note import: c22. statement performs a name binding operation.

When an *note import: c22. statement is executed, the standard builtin
*note __import__(): 615. function is called.  Other mechanisms for
invoking the import system (such as *note importlib.import_module():
b18.) may choose to bypass *note __import__(): 615. 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: 39f. 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: 5eb.  In addition, native namespace package support has
been implemented (see PEP 420(3)).

* Menu:

* importlib: importlib<7>.
* Packages: Packages<2>.
* Searching::
* Loading::
* The Path Based Finder::
* Replacing the standard import system::
* Package Relative Imports::
* Special considerations for __main__::
* Open issues::
* References::

   ---------- Footnotes ----------

   (1) (1) See *note types.ModuleType: 6f6.

   (2) https://www.python.org/dev/peps/pep-0302

   (3) https://www.python.org/dev/peps/pep-0420


File: python.info,  Node: importlib<7>,  Next: Packages<2>,  Up: The import system

4.5.1 ‘importlib’
-----------------

The *note importlib: 9b. module provides a rich API for interacting with
the import system.  For example *note importlib.import_module(): b18.
provides a recommended, simpler API than built-in *note __import__():
615. for invoking the import machinery.  Refer to the *note importlib:
9b. library documentation for additional detail.


File: python.info,  Node: Packages<2>,  Next: Searching,  Prev: importlib<7>,  Up: The import system

4.5.2 Packages
--------------

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: ebb.

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 dots, akin to Python’s standard attribute access
syntax.  Thus you might have a module called *note sys: fe. and a
package called *note email: 69, which in turn has a subpackage called
*note email.mime: 73. and a module within that subpackage called
‘email.mime.text’.

* Menu:

* Regular packages::
* Namespace packages::


File: python.info,  Node: Regular packages,  Next: Namespace packages,  Up: Packages<2>

4.5.2.1 Regular packages
........................

Python defines two types of packages, *note regular packages: 14b7. and
*note namespace packages: 14b8.  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: Packages<2>

4.5.2.2 Namespace packages
..........................

A namespace package is a composite of various *note portions: 14ba,
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: 48d. 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://www.python.org/dev/peps/pep-0420


File: python.info,  Node: Searching,  Next: Loading,  Prev: Packages<2>,  Up: The import system

4.5.3 Searching
---------------

To begin the search, Python needs the *note fully qualified: 1430. 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: c22. statement, or from the
parameters to the *note importlib.import_module(): b18. or *note
__import__(): 615. 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: 39f. 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: f2b.
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: f2b. 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: f2b.
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: 39f. is raised.  If the module name is
missing, Python will continue searching for the module.

*note sys.modules: f2b. 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: 39f.

Beware though, as if you keep a reference to the module object,
invalidate its cache entry in *note sys.modules: f2b, and then re-import
the named module, the two module objects will `not' be the same.  By
contrast, *note importlib.reload(): 39e. 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: f2b, then
Python’s import protocol is invoked to find and load the module.  This
protocol consists of two conceptual objects, *note finders: 14bf. and
*note loaders: 14c0.  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:
14c1. - 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: 14c2. for modules.  The *note import path: 14c2. 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: 14c0. 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: f2b.
cache look up.  This allows meta hooks to override *note sys.path: 48d.
processing, frozen modules, or even built-in modules.  Meta hooks are
registered by adding new finder objects to *note sys.meta_path: 5eb, as
described below.

Import path hooks are called as part of *note sys.path: 48d. (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: 961. 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: f2b, Python
next searches *note sys.meta_path: 5eb, 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(): 468. 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: 5eb. processing reaches the end of its list
without returning a spec, then a *note ModuleNotFoundError: 39f. is
raised.  Any other exceptions raised are simply propagated up, aborting
the import process.

The *note find_spec(): 468. 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: 39f. 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: 5eb. 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: 14c2. (i.e.  the *note path based finder: 14c5.).

3.4 版更變: The *note find_spec(): 468. method of meta path finders
replaced *note find_module(): 467, 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 ‘find_spec()’.


File: python.info,  Node: Loading,  Next: The Path Based Finder,  Prev: Searching,  Up: The import system

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)
         # Set __loader__ and __package__ if missing.
     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: f2b, import will have already returned it.

        * The module will exist in *note sys.modules: f2b. 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: f2b. 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: f2b.  Any module
          already in the *note sys.modules: f2b. 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: f2b.

        * 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: 14c7.

        * 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(): 5e8. method.

* Menu:

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

   ---------- Footnotes ----------

   (1) (2) 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: f2b.  The indirect effect of this is that an
imported module may replace itself in *note sys.modules: f2b.  This is
implementation-specific behavior that is not guaranteed to work in other
Python implementations.


File: python.info,  Node: Loaders,  Next: Submodules,  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(): 5e9. method with a single argument,
the module object to execute.  Any value returned from *note
exec_module(): 5e9. 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: 339, although any other exception raised
          during *note exec_module(): 5e9. will be propagated.

In many cases, the finder and loader can be the same object; in such
cases the *note find_spec(): 468. 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(): 559. 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(): 559. method of loaders.

3.4 版更變: The *note load_module(): 5e8. method was replaced by *note
exec_module(): 5e9. 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: f2b, the loader must use that existing
          module.  (Otherwise, *note importlib.reload(): 39e. will not
          work correctly.)  If the named module does not exist in *note
          sys.modules: f2b, the loader must create a new module object
          and add it to *note sys.modules: f2b.

        * The module `must' exist in *note sys.modules: f2b. 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: f2b, 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: 279. is raised when
‘exec_module()’ is defined but ‘create_module()’ is not.

3.6 版更變: An *note ImportError: 339. is raised when ‘exec_module()’ is
defined but ‘create_module()’ is not.


File: python.info,  Node: Submodules,  Next: Module spec,  Prev: Loaders,  Up: Loading

4.5.4.2 Submodules
..................

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
         bar.py

and ‘spam/__init__.py’ has the following lines in it:

     from .foo import Foo
     from .bar import Bar

then executing the following puts a name binding to ‘foo’ and ‘bar’ in
the ‘spam’ module:

     >>> import spam
     >>> spam.foo
     <module 'spam.foo' from '/tmp/imports/spam/foo.py'>
     >>> spam.bar
     <module 'spam.bar' from '/tmp/imports/spam/bar.py'>

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: Submodules,  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: 14cb. 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.

 -- 屬性: __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.

 -- 屬性: __package__

     The module’s ‘__package__’ attribute must 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
     expected to have the same value as ‘__spec__.parent’.

     3.6 版更變: The value of ‘__package__’ is expected to be the same
     as ‘__spec__.parent’.

 -- 屬性: __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: 14cd.  The one exception is ‘__main__’, where ‘__spec__’
     is *note set to None in some cases: 14ce.

     When ‘__package__’ is not defined, ‘__spec__.parent’ 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: 14cf.

     Non-package modules should not have a ‘__path__’ attribute.

 -- 屬性: __file__

 -- 屬性: __cached__

     ‘__file__’ is optional.  If set, this attribute’s value must be a
     string.  The import system may opt to leave ‘__file__’ unset if it
     has no semantic meaning (e.g.  a module loaded from a database).

     If ‘__file__’ is set, it may also be appropriate to set the
     ‘__cached__’ attribute 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)).

     It is also appropriate to set ‘__cached__’ when ‘__file__’ is not
     set.  However, that scenario is quite atypical.  Ultimately, the
     loader is what makes use of ‘__file__’ and/or ‘__cached__’.  So if
     a loader can load from a cached module but otherwise does not load
     from a file, that atypical scenario may be appropriate.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0366

   (2) https://www.python.org/dev/peps/pep-0366

   (3) https://www.python.org/dev/peps/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: 48d, i.e.  providing a list of locations to search for
modules during import.  However, ‘__path__’ is typically much more
constrained than *note sys.path: 48d.

‘__path__’ must be an iterable of strings, but it may be empty.  The
same rules used for *note sys.path: 48d. also apply to a package’s
‘__path__’, and *note sys.path_hooks: 961. (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://www.python.org/dev/peps/pep-0420

   (2) https://www.python.org/dev/peps/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.4 版更變: Use of *note loader.module_repr(): 946. has been deprecated
and the module spec is now used by the import machinery to generate a
module repr.

For backward compatibility with Python 3.3, the module repr will be
generated by calling the loader’s *note module_repr(): 946. method, if
defined, before trying either approach described above.  However, the
method is deprecated.


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: 1346. 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: The import system

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: 14c5. (*note
PathFinder: 960.), searches an *note import path: 14c2, which contains a
list of *note path entries: 14d4.  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: 144. 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:
9b7. 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: 9b6. and *note path entry finder: 9b7.  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: 5eb. 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: 5eb, 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: 14c5. is responsible for finding and
loading Python modules and packages whose location is specified with a
string *note path entry: 14d4.  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: 14c5. implements the
*note find_spec(): 468. 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: 14c2.

Three variables are used by the *note path based finder: 14c5, *note
sys.path: 48d, *note sys.path_hooks: 961. and *note
sys.path_importer_cache: 4a2.  The ‘__path__’ attributes on package
objects are also used.  These provide additional ways that the import
machinery can be customized.

*note sys.path: 48d. contains a list of strings providing search
locations for modules and packages.  It is initialized from the
‘PYTHONPATH’ environment variable and various other installation- and
implementation-specific defaults.  Entries in *note sys.path: 48d. can
name directories on the file system, zip files, and potentially other
"locations" (see the *note site: ec. module) that should be searched for
modules, such as URLs, or database queries.  Only strings and bytes
should be present on *note sys.path: 48d.; all other data types are
ignored.  The encoding of bytes entries is determined by the individual
*note path entry finders: 9b7.

The *note path based finder: 14c5. is a *note meta path finder: 9b6, so
the import machinery begins the *note import path: 14c2. search by
calling the path based finder’s *note find_spec(): 93f. method as
described previously.  When the ‘path’ argument to *note find_spec():
93f. 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: 48d. 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:
9b7. (*note PathEntryFinder: 9b9.) 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: 4a2. (despite the name, this cache actually
stores finder objects rather than being limited to *note importer: 14c1.
objects).  In this way, the expensive search for a particular *note path
entry: 14d4. location’s *note path entry finder: 9b7. need only be done
once.  User code is free to remove cache entries from *note
sys.path_importer_cache: 4a2. forcing the path based finder to perform
the path entry search again (1).

If the path entry is not present in the cache, the path based finder
iterates over every callable in *note sys.path_hooks: 961.  Each of the
*note path entry hooks: 14d6. 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: 9b7. that can handle the path entry,
or it may raise *note ImportError: 339.  An *note ImportError: 339. is
used by the path based finder to signal that the hook cannot find a
*note path entry finder: 9b7. for that *note path entry: 14d4.  The
exception is ignored and *note import path: 14c2. 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: 339.

If *note sys.path_hooks: 961. iteration ends with no *note path entry
finder: 9b7. being returned, then the path based finder’s *note
find_spec(): 93f. method will store ‘None’ in *note
sys.path_importer_cache: 4a2. (to indicate that there is no finder for
this path entry) and return ‘None’, indicating that this *note meta path
finder: 9b6. could not find the module.

If a *note path entry finder: 9b7. `is' returned by one of the *note
path entry hook: 14d6. callables on *note sys.path_hooks: 961, 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: 48d.  First,
if the current working directory is found to not exist, no value is
stored in *note sys.path_importer_cache: 4a2.  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: 4a2. and
returned by *note importlib.machinery.PathFinder.find_spec(): 93f. will
be the actual current working directory and not the empty string.

   ---------- Footnotes ----------

   (1) (3) In legacy code, it is possible to find instances of *note
imp.NullImporter: 9c0. in the *note sys.path_importer_cache: 4a2.  It is
recommended that code be changed to use ‘None’ instead.  See *note
Porting Python code: b17. for more details.


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(): 46a. method.

*note find_spec(): 46a. 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: 14ba, the path entry finder sets
"submodule_search_locations" to a list containing the portion.

3.4 版更變: *note find_spec(): 46a. replaced *note find_loader(): 469.
and *note find_module(): 940, 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.

*note find_loader(): 469. 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: 14ba.

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()’.


File: python.info,  Node: Replacing the standard import system,  Next: Package Relative Imports,  Prev: The Path Based Finder,  Up: The import system

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: 5eb, 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__(): 615. 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: 39f.
directly from *note find_spec(): 468. 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: The import system

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: Open issues,  Prev: Package Relative Imports,  Up: The import system

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: 14cd, the ‘__main__’ module is
directly initialized at interpreter startup, much like *note sys: fe.
and *note builtins: 13.  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: 33c. 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: 48d. entry.

In *note the remaining cases: 133f. ‘__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: 1210. option

   - 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: 33c. 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: Open issues,  Next: References,  Prev: Special considerations for __main__,  Up: The import system

4.5.9 Open issues
-----------------

XXX It would be really nice to have a diagram.

XXX * (import_machinery.rst) how about a section devoted just to the
attributes of modules and packages, perhaps expanding upon or
supplanting the related entries in the data model reference page?

XXX runpy, pkgutil, et al in the library manual should all get "See
Also" links at the top pointing to the new import system section.

XXX Add more explanation regarding the different ways in which
‘__main__’ is initialized?

XXX Add more info on ‘__main__’ quirks/pitfalls (i.e.  copy from PEP
395(1)).

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0395


File: python.info,  Node: References,  Prev: Open issues,  Up: The import system

4.5.10 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: 5eb. was PEP 302(2),
with subsequent extension in PEP 420(3).

PEP 420(4) introduced *note namespace packages: 14b8. 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://www.python.org/dev/peps/pep-0302

   (3) https://www.python.org/dev/peps/pep-0420

   (4) https://www.python.org/dev/peps/pep-0420

   (5) https://www.python.org/dev/peps/pep-0420

   (6) https://www.python.org/dev/peps/pep-0366

   (7) https://www.python.org/dev/peps/pep-0328

   (8) https://www.python.org/dev/peps/pep-0366

   (9) https://www.python.org/dev/peps/pep-0338

   (10) https://www.python.org/dev/peps/pep-0451


File: python.info,  Node: Expressions,  Next: Simple statements,  Prev: The import system,  Up: The Python Language Reference

4.6 Expressions
===============

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: Expressions

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: Expressions

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: 13d9. for lexical definition and section *note
Naming and binding: 14a4. 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: d80. exception.

`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.  Private names are transformed to a longer form before code
is generated for them.  The transformation inserts the class name, with
leading underscores removed and a single underscore inserted, in front
of the name.  For example, the identifier ‘__spam’ occurring in a class
named ‘Ham’ will be transformed to ‘_Ham__spam’.  This transformation is
independent of the syntactical context in which the identifier is used.
If the transformed name is extremely long (longer than 255 characters),
implementation defined truncation may happen.  If the class name
consists only of underscores, no transformation is done.


File: python.info,  Node: Literals<2>,  Next: Parenthesized forms,  Prev: Identifiers Names,  Up: Atoms

4.6.2.2 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: 13e6. 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.3 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 operator.  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.4 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" expression_nocond [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: 285. function, an ‘async for’
clause may be used to iterate over a *note asynchronous iterator: 64a.
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:
1a4. expressions.  If a comprehension contains either ‘async for’
clauses or ‘await’ expressions 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.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0530


File: python.info,  Node: List displays,  Next: Set displays,  Prev: Displays for lists sets and dictionaries,  Up: Atoms

4.6.2.5 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.6 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.7 Dictionary displays
...........................

A dictionary display is a possibly empty series of key/datum pairs
enclosed in curly braces:

     dict_display       ::= "{" [key_datum_list | dict_comprehension] "}"
     key_datum_list     ::= key_datum ("," key_datum)* [","]
     key_datum          ::= expression ":" expression | "**" or_expr
     dict_comprehension ::= expression ":" expression comp_for

A dictionary display yields a new dictionary object.

If a comma-separated sequence of key/datum pairs 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 datum.  This means that you can specify the same key
multiple times in the key/datum 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: b3e.  Each mapping item is added to the new
dictionary.  Later values replace values already set by earlier
key/datum pairs 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 The standard type hierarchy: 1426.  (To summarize, the key
type should be *note hashable: 142e, which excludes all mutable
objects.)  Clashes between duplicate keys are not detected; the last
datum (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://www.python.org/dev/peps/pep-0448

   (2) https://www.python.org/dev/peps/pep-0572


File: python.info,  Node: Generator expressions,  Next: Yield expressions,  Prev: Dictionary displays,  Up: Atoms

4.6.2.8 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__(): 12df. 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: 651. 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: 1a4. 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: 64b.).

3.6 版新加入: Asynchronous generator expressions were introduced.

3.7 版更變: Prior to Python 3.7, asynchronous generator expressions
could only appear in *note async def: 285. 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.9 Yield expressions
.........................

     yield_atom       ::= "(" yield_expression ")"
     yield_expression ::= "yield" [expression_list | "from" expression]

The yield expression is used when defining a *note generator: 9a7.
function or an *note asynchronous generator: 1508. 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,
and using it in an *note async def: 285. function’s body causes that
coroutine function to be an asynchronous generator.  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: 1509.

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: 150a. to the generator’s caller.  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__(): 12df. is used (typically
via either a *note for: c35. or the *note next(): 687. builtin) then the
result is *note None: 158.  Otherwise, if *note send(): 1494. 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: d77. 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(): 1498. method will be called,
allowing any pending *note finally: 183. 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(): 1494. and any exceptions passed in with
*note throw(): 1496. are passed to the underlying iterator if it has the
appropriate methods.  If this is not the case, then *note send(): 1494.
will raise *note AttributeError: 3a0. or *note TypeError: 193, while
*note throw(): 1496. will just raise the passed in exception
immediately.

When the underlying iterator is complete, the ‘value’ attribute of the
raised *note StopIteration: 48b. instance becomes the value of the yield
expression.  It can be either set explicitly when raising *note
StopIteration: 48b, 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: 190.
     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 ‘yield_from’ 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::
* Examples::
* Asynchronous generator functions::
* Asynchronous generator-iterator methods::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0255

   (2) https://www.python.org/dev/peps/pep-0342

   (3) https://www.python.org/dev/peps/pep-0380

   (4) https://www.python.org/dev/peps/pep-0525

   (5) https://www.python.org/dev/peps/pep-0492


File: python.info,  Node: Generator-iterator methods,  Next: Examples,  Up: Yield expressions

4.6.2.10 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: 1fc. 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__(): 12df. method, the current yield
     expression always evaluates to *note None: 158.  The execution then
     continues to the next yield expression, where the generator is
     suspended again, and the value of the *note expression_list: 150a.
     is returned to *note __next__(): 12df.’s caller.  If the generator
     exits without yielding another value, a *note StopIteration: 48b.
     exception is raised.

     This method is normally called implicitly, e.g.  by a *note for:
     c35. loop, or by the built-in *note next(): 687. 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(): 1494. method returns the next
     value yielded by the generator, or raises *note StopIteration: 48b.
     if the generator exits without yielding another value.  When *note
     send(): 1494. is called to start the generator, it must be called
     with *note None: 158. as the argument, because there is no yield
     expression that could receive the value.

 -- 成員函式: generator.throw (type[, value[, traceback]])

     Raises an exception of type ‘type’ 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: 48b. 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.

 -- 成員函式: generator.close ()

     Raises a *note GeneratorExit: d37. at the point where the generator
     function was paused.  If the generator function then exits
     gracefully, is already closed, or raises *note GeneratorExit: d37.
     (by not catching the exception), close returns to its caller.  If
     the generator yields a value, a *note RuntimeError: 2bb. is raised.
     If the generator raises any other exception, it is propagated to
     the caller.  *note close(): 1498. does nothing if the generator has
     already exited due to an exception or normal exit.


File: python.info,  Node: Examples,  Next: Asynchronous generator functions,  Prev: Generator-iterator methods,  Up: Yield expressions

4.6.2.11 Examples
.................

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: 97d. in "What’s New in Python."


File: python.info,  Node: Asynchronous generator functions,  Next: Asynchronous generator-iterator methods,  Prev: Examples,  Up: Yield expressions

4.6.2.12 Asynchronous generator functions
.........................................

The presence of a yield expression in a function or method defined using
*note async def: 285. further defines the function as an *note
asynchronous generator: 1508. 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:
2e4. statement in a coroutine function analogously to how a generator
object would be used in a *note for: c35. statement.

Calling one of the asynchronous generator’s methods returns an *note
awaitable: 51e. 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: 150a. 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__(): 150e. is used then the result is *note
None: 158.  Otherwise, if *note asend(): 150f. is used, then the result
will be the value passed in to that method.

In an asynchronous generator function, yield expressions are allowed
anywhere in a *note try: d77. 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: 183. 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(): 1510. method and
run the resulting coroutine object, thus allowing any pending ‘finally’
clauses to execute.

To take care of finalization, an event loop should define a `finalizer'
function which takes an asynchronous generator-iterator and presumably
calls *note aclose(): 1510. and executes the coroutine.  This
`finalizer' may be registered by calling *note sys.set_asyncgen_hooks():
f2e.  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.8/Lib/asyncio/base_events.py


File: python.info,  Node: Asynchronous generator-iterator methods,  Prev: Asynchronous generator functions,  Up: Yield expressions

4.6.2.13 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__(): 150e. method, the current yield
     expression always evaluates to *note None: 158. in the returned
     awaitable, which when run will continue to the next yield
     expression.  The value of the *note expression_list: 150a. of the
     yield expression is the value of the *note StopIteration: 48b.
     exception raised by the completing coroutine.  If the asynchronous
     generator exits without yielding another value, the awaitable
     instead raises a *note StopAsyncIteration: 1017. exception,
     signalling that the asynchronous iteration has completed.

     This method is normally called implicitly by a *note async for:
     2e4. loop.

 -- 成員函式: coroutine agen.asend (value)

     Returns an awaitable which when run resumes the execution of the
     asynchronous generator.  As with the *note send(): 1494. 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(): 150f. method will return the next value yielded by the
     generator as the value of the raised *note StopIteration: 48b, or
     raises *note StopAsyncIteration: 1017. if the asynchronous
     generator exits without yielding another value.  When *note
     asend(): 150f. is called to start the asynchronous generator, it
     must be called with *note None: 158. as the argument, because there
     is no yield expression that could receive the 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: 48b. exception.  If the asynchronous
     generator exits without yielding another value, a *note
     StopAsyncIteration: 1017. 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.

 -- 成員函式: coroutine agen.aclose ()

     Returns an awaitable that when run will throw a *note
     GeneratorExit: d37. 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: d37. (by not catching the exception), then the
     returned awaitable will raise a *note StopIteration: 48b.
     exception.  Any further awaitables returned by subsequent calls to
     the asynchronous generator will raise a *note StopAsyncIteration:
     1017. exception.  If the asynchronous generator yields a value, a
     *note RuntimeError: 2bb. 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(): 1510. will return an awaitable that does
     nothing.


File: python.info,  Node: Primaries,  Next: Await expression,  Prev: Atoms,  Up: Expressions

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.  This production can be
customized by overriding the *note __getattr__(): 31f. method.  If this
attribute is not available, the exception *note AttributeError: 3a0. is
raised.  Otherwise, the type and value of the object produced is
determined by the object.  Multiple evaluations of the same attribute
reference may yield different objects.


File: python.info,  Node: Subscriptions,  Next: Slicings,  Prev: Attribute references,  Up: Primaries

4.6.3.2 Subscriptions
.....................

A subscription selects an item of a sequence (string, tuple or list) or
mapping (dictionary) object:

     subscription ::= primary "[" expression_list "]"

The primary must evaluate to an object that supports subscription (lists
or dictionaries for example).  User-defined objects can support
subscription by defining a *note __getitem__(): 27d. method.

For built-in objects, there are two types of objects that support
subscription:

If the primary is a mapping, 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.  (The expression list is a tuple except if it has exactly one
item.)

If the primary is a sequence, the expression list must evaluate to an
integer or a slice (as discussed in the following section).

The formal syntax makes no special provision for negative indices in
sequences; however, built-in sequences all provide a *note
__getitem__(): 27d. method that interprets negative indices by adding
the length of the sequence to the index (so that ‘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__(): 27d. method, subclasses overriding this method will
need to explicitly add that support.

A string’s 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: 1273. 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__(): 27d. 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 The standard type hierarchy: 1426.)
whose ‘start’, ‘stop’ and ‘step’ 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: 1527.) with a
possibly empty series of *note arguments: 1528.:

     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__(): 1433.
method are callable).  All argument expressions are evaluated before the
call is attempted.  Please refer to section *note Function definitions:
1261. for the syntax of formal *note parameter: 1530. 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: 193. exception is raised.  Otherwise, the value of 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: 193. exception is
raised.  Otherwise, the list of filled slots is used as the argument
list for the call.

`CPython implementation detail:' 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(): 26b. to parse their
arguments.

If there are more positional arguments than there are formal parameter
slots, a *note TypeError: 193. 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: 193. 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: bb1.  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 arise.

If the syntax ‘**expression’ appears in the function call, ‘expression’
must evaluate to a *note mapping: b3e, the contents of which are treated
as additional keyword arguments.  If a keyword is already present (as an
explicit keyword argument, or from another unpacking), a *note
TypeError: 193. 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 Function definitions: 1261.  When the code block executes a
     *note return: 191. 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 內建函式: bf8. 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__(): 1433. method; the effect
     is then the same as if that method was called.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0448


File: python.info,  Node: Await expression,  Next: The power operator,  Prev: Primaries,  Up: Expressions

4.6.4 Await expression
----------------------

Suspend the execution of *note coroutine: 1a7. on an *note awaitable:
51e. object.  Can only be used inside a *note coroutine function: 644.

     await_expr ::= "await" primary

3.5 版新加入.


File: python.info,  Node: The power operator,  Next: Unary arithmetic and bitwise operations,  Prev: Await expression,  Up: Expressions

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():
19b. 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:
12b2.  Raising a negative number to a fractional power results in a
*note complex: 18a. number.  (In earlier versions it raised a *note
ValueError: 1fc.)


File: python.info,  Node: Unary arithmetic and bitwise operations,  Next: Binary arithmetic operations,  Prev: The power operator,  Up: Expressions

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 unary ‘+’ (plus) operator yields its numeric argument unchanged.

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.

In all three cases, if the argument does not have the proper type, a
*note TypeError: 193. exception is raised.


File: python.info,  Node: Binary arithmetic operations,  Next: Shifting operations,  Prev: Unary arithmetic and bitwise operations,  Up: Expressions

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.

The ‘@’ (at) operator is intended to be used for matrix multiplication.
No builtin Python types implement this operator.

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: 12b2. exception.

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: 12b2. 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(): 153.: ‘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: 122a.

The floor division operator, the modulo operator, and the *note
divmod(): 153. function are not defined for complex numbers.  Instead,
convert to a floating point number using the *note abs(): 12c4. 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.

The ‘-’ (subtraction) operator yields the difference of its arguments.
The numeric arguments are first converted to a common type.

   ---------- Footnotes ----------

   (1) (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():
153d. 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) (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: Expressions

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.

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: Expressions

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.

The ‘^’ operator yields the bitwise XOR (exclusive OR) of its arguments,
which must be integers.

The ‘|’ operator yields the bitwise (inclusive) OR of its arguments,
which must be integers.


File: python.info,  Node: Comparisons,  Next: Boolean operations,  Prev: Binary bitwise operations,  Up: Expressions

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’.

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: 1423. 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:
2b1, they inherit the default comparison behavior from *note object:
2b1.  Types can customize their comparison behavior by implementing
`rich comparison methods' like *note __lt__(): c39, described in *note
Basic customization: 143a.

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: 193.  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 Numeric Types — int,
     float, complex: 1224.) and of the standard library types *note
     fractions.Fraction: 186. and *note decimal.Decimal: 189. 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 ‘NotImplemented’ 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: 336. or *note
     bytearray: 337.) can be compared within and across their types.
     They compare lexicographically using the numeric values of their
     elements.

   * Strings (instances of *note str: 335.) compare lexicographically
     using the numerical Unicode code points (the result of the built-in
     function *note ord(): 142c.) of their characters.  (2)

     Strings and binary sequences cannot be directly compared.

   * Sequences (instances of *note tuple: 483, *note list: 263, or *note
     range: 9c3.) 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: 193.

     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: 1b9.) 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:
     193.

   * Sets (instances of *note set: b74. or *note frozenset: bf3.) 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(): 80e, *note max(): 80f, and *note
     sorted(): 449. 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’ and ‘y == x’

          ‘x != y’ and ‘y != x’

          ‘x < y’ and ‘y > x’

          ‘x <= y’ and ‘y >= x’

   * Comparison should be transitive.  The following (non-exhaustive)
     examples illustrate that:

          ‘x > y and y > z’ implies ‘x > z’

          ‘x < y and y <= z’ implies ‘x < z’

   * Inverse comparison should result in the boolean negation.  In other
     words, the following expressions should have the same result:

          ‘x == y’ and ‘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(): 850. decorator.

   * The *note hash(): 9c9. 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://www.python.org/dev/peps/pep-0008

   (2) (3) 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(): 10b4.


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: 7a8. and *note not in: 1462. 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__(): d2d.
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__(): d2d.
but do define *note __iter__(): 514, ‘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: 7a8. raised that exception.

Lastly, the old-style iteration protocol is tried: if a class defines
*note __getitem__(): 27d, ‘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: e7a. exception.  (If
any other exception is raised, it is as if *note in: 7a8. raised that
exception).

The operator *note not in: 1462. is defined to have the inverse truth
value of *note in: 7a8.


File: python.info,  Node: Identity comparisons,  Prev: Membership test operations,  Up: Comparisons

4.6.10.3 Identity comparisons
.............................

The operators *note is: ebf. and *note is not: 154d. 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():
d8b. function.  ‘x is not y’ yields the inverse truth value.  (1)

   ---------- Footnotes ----------

   (1) (4) 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: ebf. 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: Expressions

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__():
c6d. method.

The operator *note not: 1552. 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: 154f. nor *note or: 1550. 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:
1552. 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: Expressions

4.6.12 Assignment expressions
-----------------------------

     assignment_expression ::= [identifier ":="] expression

An assignment expression (sometimes also called a "named expression" or
"walrus") assigns an *note expression: 1558. to an *note identifier:
13db, while also returning the value of the *note expression: 1558.

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)

3.8 版新加入: See PEP 572(1) for more details about assignment
expressions.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0572


File: python.info,  Node: Conditional expressions,  Next: Lambdas,  Prev: Assignment expressions<2>,  Up: Expressions

4.6.13 Conditional expressions
------------------------------

     conditional_expression ::= or_test ["if" or_test "else" expression]
     expression             ::= conditional_expression | lambda_expr
     expression_nocond      ::= or_test | lambda_expr_nocond

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://www.python.org/dev/peps/pep-0308


File: python.info,  Node: Lambdas,  Next: Expression lists,  Prev: Conditional expressions,  Up: Expressions

4.6.14 Lambdas
--------------

     lambda_expr        ::= "lambda" [parameter_list] ":" expression
     lambda_expr_nocond ::= "lambda" [parameter_list] ":" expression_nocond

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 Function definitions: 1261. 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: Expressions

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: bb1.  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).

The trailing comma is required only to create a single tuple (a.k.a.  a
`singleton'); 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://www.python.org/dev/peps/pep-0448


File: python.info,  Node: Evaluation order,  Next: Operator precedence,  Prev: Expression lists,  Up: Expressions

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: Expressions

4.6.17 Operator precedence
--------------------------

The following table summarizes the operator precedence in Python, from
lowest precedence (least binding) to highest precedence (most 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, which groups 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: 1546. section.

Operator                                            描述
                                                    
----------------------------------------------------------------------------------------------
                                                    
‘:=’                                                Assignment expression
                                                    
                                                    
*note lambda: c34.                                  Lambda expression
                                                    
                                                    
*note if: 155a. – ‘else’                            Conditional expression
                                                    
                                                    
*note or: 1550.                                     Boolean OR
                                                    
                                                    
*note and: 154f.                                    Boolean AND
                                                    
                                                    
*note not: 1552. ‘x’                                Boolean NOT
                                                    
                                                    
*note in: 7a8, *note not in: 1462, *note is: ebf,   Comparisons, including membership tests
*note is not: 154d, ‘<’, ‘<=’, ‘>’, ‘>=’, ‘!=’,     and identity tests
‘==’                                                

‘|’                                                 Bitwise OR
                                                    
                                                    
‘^’                                                 Bitwise XOR
                                                    
                                                    
‘&’                                                 Bitwise AND
                                                    
                                                    
‘<<’, ‘>>’                                          Shifts
                                                    
                                                    
‘+’, ‘-’                                            Addition and subtraction
                                                    
                                                    
‘*’, ‘@’, ‘/’, ‘//’, ‘%’                            Multiplication, matrix multiplication,
                                                    division, floor division, remainder (1)
                                                    
                                                    
‘+x’, ‘-x’, ‘~x’                                    Positive, negative, bitwise NOT
                                                    
                                                    
‘**’                                                Exponentiation (2)
                                                    
                                                    
*note await: 1a4. ‘x’                               Await expression
                                                    
                                                    
‘x[index]’, ‘x[index:index]’, ‘x(arguments...)’,    Subscription, slicing, call, attribute
‘x.attribute’                                       reference
                                                    
                                                    
‘(expressions...)’,                                 Binding or parenthesized expression,
                                                    list display, dictionary display, set
‘[expressions...]’, ‘{key: value...}’,              display
‘{expressions...}’                                  

註解
....

   ---------- Footnotes ----------

   (1) (5) The ‘%’ operator is also used for string formatting; the same
precedence applies.

   (2) (6) The power operator ‘**’ binds less tightly than an arithmetic
or bitwise unary operator on its right, that is, ‘2**-1’ is ‘0.5’.


File: python.info,  Node: Simple statements,  Next: Compound statements,  Prev: Expressions,  Up: The Python Language Reference

4.7 Simple statements
=====================

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

* Menu:

* Expression statements::
* Assignment statements::
* The assert statement::
* The pass statement::
* The del statement: The del statement<2>.
* The return statement::
* The yield statement::
* The raise statement::
* The break statement::
* The continue statement::
* The import statement::
* The global statement::
* The nonlocal statement::


File: python.info,  Node: Expression statements,  Next: Assignment statements,  Up: Simple statements

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(): 7d1. 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: The assert statement,  Prev: Expression statements,  Up: Simple statements

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: 1515. 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 The standard type hierarchy: 1426.).

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: 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.

        * 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: 1249. or *note
          nonlocal: c44. 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:
          c44, 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:
     193. 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: 3a0.).  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(): 1d8.

   * 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: e7a. 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/datum 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__(): c67. 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 implementation detail:' 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://www.python.org/dev/peps/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: 1515. 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 expression 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: 1575. 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: 624. 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: 1570. is that
only single target is allowed.

For simple names as 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.

For expressions as assignment targets, the annotations are 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__(): c67. or *note __setattr__(): e31. 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: 11a. 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 same expressions in the
right hand side as the regular assignments.  Previously, some
expressions (like un-parenthesized tuple expressions) caused a syntax
error.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0526

   (2) https://www.python.org/dev/peps/pep-0484


File: python.info,  Node: The assert statement,  Next: The pass statement,  Prev: Assignment statements,  Up: Simple statements

4.7.3 The ‘assert’ statement
----------------------------

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__: 1001. and *note
AssertionError: 1033. refer to the built-in variables with those names.
In the current implementation, the built-in variable *note __debug__:
1001. is ‘True’ under normal circumstances, ‘False’ when optimization is
requested (command line option *note -O: 690.).  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__: 1001. are illegal.  The value for the
built-in variable is determined when the interpreter starts.


File: python.info,  Node: The pass statement,  Next: The del statement<2>,  Prev: The assert statement,  Up: Simple statements

4.7.4 The ‘pass’ statement
--------------------------

     pass_stmt ::= "pass"

*note pass: 1245. 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: The del statement<2>,  Next: The return statement,  Prev: The pass statement,  Up: Simple statements

4.7.5 The ‘del’ statement
-------------------------

     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: 1249. statement in the same code block.  If the name is unbound,
a *note NameError: d80. 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: The return statement,  Next: The yield statement,  Prev: The del statement<2>,  Up: Simple statements

4.7.6 The ‘return’ statement
----------------------------

     return_stmt ::= "return" [expression_list]

*note return: 191. 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: 191. leaves the current function call with the expression
list (or ‘None’) as return value.

When *note return: 191. passes control out of a *note try: d77.
statement with a *note finally: 183. clause, that ‘finally’ clause is
executed before really leaving the function.

In a generator function, the *note return: 191. statement indicates that
the generator is done and will cause *note StopIteration: 48b. to be
raised.  The returned value (if any) is used as an argument to construct
*note StopIteration: 48b. and becomes the ‘StopIteration.value’
attribute.

In an asynchronous generator function, an empty *note return: 191.
statement indicates that the asynchronous generator is done and will
cause *note StopAsyncIteration: 1017. to be raised.  A non-empty
‘return’ statement is a syntax error in an asynchronous generator
function.


File: python.info,  Node: The yield statement,  Next: The raise statement,  Prev: The return statement,  Up: Simple statements

4.7.7 The ‘yield’ statement
---------------------------

     yield_stmt ::= yield_expression

A *note yield: 190. statement is semantically equivalent to a *note
yield expression: 1505.  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: 9a7. 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: 190. semantics, refer to the *note
Yield expressions: 1505. section.


File: python.info,  Node: The raise statement,  Next: The break statement,  Prev: The yield statement,  Up: Simple statements

4.7.8 The ‘raise’ statement
---------------------------

     raise_stmt ::= "raise" [expression ["from" expression]]

If no expressions are present, *note raise: c47. re-raises the last
exception that was active in the current scope.  If no exception is
active in the current scope, a *note RuntimeError: 2bb. exception is
raised indicating that this is an error.

Otherwise, *note raise: c47. evaluates the first expression as the
exception object.  It must be either a subclass or an instance of *note
BaseException: 1a9.  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 ‘__traceback__’ attribute, which is
writable.  You can create an exception and set your own traceback in one
step using the ‘with_traceback()’ 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 ‘__cause__’ 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>
     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>
     RuntimeError: Something bad happened

A similar mechanism works implicitly if an exception is raised inside an
exception handler or a *note finally: 183. clause: the previous
exception is then attached as the new exception’s ‘__context__’
attribute:

     >>> try:
     ...     print(1 / 0)
     ... except:
     ...     raise RuntimeError("Something bad happened")
     ...
     Traceback (most recent call last):
       File "<stdin>", line 2, in <module>
     ZeroDivisionError: division by zero

     During handling of the above exception, another exception occurred:

     Traceback (most recent call last):
       File "<stdin>", line 4, in <module>
     RuntimeError: Something bad happened

Exception chaining can be explicitly suppressed by specifying *note
None: 158. 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
Exceptions: 14ae, and information about handling exceptions is in
section *note The try statement: d77.

3.3 版更變: *note None: 158. is now permitted as ‘Y’ in ‘raise X from
Y’.

3.3 版新加入: The ‘__suppress_context__’ attribute to suppress automatic
display of the exception context.


File: python.info,  Node: The break statement,  Next: The continue statement,  Prev: The raise statement,  Up: Simple statements

4.7.9 The ‘break’ statement
---------------------------

     break_stmt ::= "break"

*note break: 2dc. may only occur syntactically nested in a *note for:
c35. or *note while: 1232. 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: c35. loop is terminated by *note break: 2dc, the loop
control target keeps its current value.

When *note break: 2dc. passes control out of a *note try: d77. statement
with a *note finally: 183. clause, that ‘finally’ clause is executed
before really leaving the loop.


File: python.info,  Node: The continue statement,  Next: The import statement,  Prev: The break statement,  Up: Simple statements

4.7.10 The ‘continue’ statement
-------------------------------

     continue_stmt ::= "continue"

*note continue: 182. may only occur syntactically nested in a *note for:
c35. or *note while: 1232. 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: 182. passes control out of a *note try: d77.
statement with a *note finally: 183. clause, that ‘finally’ clause is
executed before really starting the next loop cycle.


File: python.info,  Node: The import statement,  Next: The global statement,  Prev: The continue statement,  Up: Simple statements

4.7.11 The ‘import’ statement
-----------------------------

     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" module "import" "*"
     module          ::= (identifier ".")* identifier
     relative_module ::= "."* module | "."+

The basic import statement (no *note from: c4a. 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: c22. 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: 1434, 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: c4a. form uses a slightly more complex process:

  1. find the module specified in the *note from: c4a. clause, loading
     and initializing it if necessary;

  2. for each of the identifiers specified in the *note import: c22.
     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: 339. 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

Examples:

     import foo                 # foo imported and bound locally
     import foo.bar.baz         # foo.bar.baz imported, foo bound locally
     import foo.bar.baz as fbb  # foo.bar.baz imported and bound as fbb
     from foo.bar import baz    # foo.bar.baz imported and 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: c22. 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: 45d.

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:
c4a. 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: 14da. section.

*note importlib.import_module(): b18. is provided to support
applications that determine dynamically the modules to be loaded.

Raises an *note auditing event: e96. ‘import’ with arguments ‘module’,
‘filename’, ‘sys.path’, ‘sys.meta_path’, ‘sys.path_hooks’.

* Menu:

* Future statements::


File: python.info,  Node: Future statements,  Up: The import statement

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(): c49. and
*note compile(): 1b5. 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(): 1b5. — 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: e24. 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://www.python.org/dev/peps/pep-0563

   (2) https://www.python.org/dev/peps/pep-0236


File: python.info,  Node: The global statement,  Next: The nonlocal statement,  Prev: The import statement,  Up: Simple statements

4.7.12 The ‘global’ statement
-----------------------------

     global_stmt ::= "global" identifier ("," identifier)*

The *note global: 1249. 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: 1249. statement must not be used in the
same code block textually preceding that ‘global’ statement.

Names listed in a *note global: 1249. statement must not be defined as
formal parameters or in a *note for: c35. loop control target, *note
class: c6f. definition, function definition, *note import: c22.
statement, or variable annotation.

`CPython implementation detail:' 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: 1249. 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(): c49. 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(): b95. and *note compile(): 1b5. functions.


File: python.info,  Node: The nonlocal statement,  Prev: The global statement,  Up: Simple statements

4.7.13 The ‘nonlocal’ statement
-------------------------------

     nonlocal_stmt ::= "nonlocal" identifier ("," identifier)*

The *note nonlocal: c44. statement causes the listed identifiers to
refer to previously bound variables in the nearest enclosing scope
excluding globals.  This is important because the default behavior for
binding is to search the local namespace first.  The statement allows
encapsulated code to rebind variables outside of the local scope besides
the global (module) scope.

Names listed in a *note nonlocal: c44. statement, unlike those listed in
a *note global: 1249. statement, must refer to pre-existing bindings in
an enclosing scope (the scope in which a new binding should be created
cannot be determined unambiguously).

Names listed in a *note nonlocal: c44. statement must not collide with
pre-existing bindings in the local scope.

也參考
......

PEP 3104(1) - Access to Names in Outer Scopes

     The specification for the *note nonlocal: c44. statement.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3104


File: python.info,  Node: Compound statements,  Next: Top-level components,  Prev: Simple statements,  Up: The Python Language Reference

4.8 Compound statements
=======================

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: dec, *note while: 1232. and *note for: c35. statements
implement traditional control flow constructs.  *note try: d77.
specifies exception handlers and/or cleanup code for a group of
statements, while the *note with: 6ee. 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: dec. clause a
following *note else: 1239. 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(): 88b. 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
                       | 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: 1239.’ problem is solved in
Python by requiring nested *note if: dec. 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::
* Function definitions::
* Class definitions::
* Coroutines: Coroutines<2>.


File: python.info,  Node: The if statement,  Next: The while statement,  Up: Compound statements

4.8.1 The ‘if’ statement
------------------------

The *note if: dec. 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: 154e. for the definition of true and false); then that suite
is executed (and no other part of the *note if: dec. statement is
executed or evaluated).  If all expressions are false, the suite of the
*note else: 1239. clause, if present, is executed.


File: python.info,  Node: The while statement,  Next: The for statement,  Prev: The if statement,  Up: Compound statements

4.8.2 The ‘while’ statement
---------------------------

The *note while: 1232. 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: 2dc. statement executed in the first suite terminates the
loop without executing the ‘else’ clause’s suite.  A *note continue:
182. 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: Compound statements

4.8.3 The ‘for’ statement
-------------------------

The *note for: c35. 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" expression_list ":" suite
                  ["else" ":" suite]

The expression list is evaluated once; it should yield an iterable
object.  An iterator is created for the result of the ‘expression_list’.
The suite is then executed once for each item provided by the iterator,
in the order returned by the iterator.  Each item in turn is assigned to
the target list using the standard rules for assignments (see *note
Assignment statements: 1570.), and then the suite is executed.  When the
items are exhausted (which is immediately when the sequence is empty or
an iterator raises a *note StopIteration: 48b. exception), the suite in
the ‘else’ clause, if present, is executed, and the loop terminates.

A *note break: 2dc. statement executed in the first suite terminates the
loop without executing the ‘else’ clause’s suite.  A *note continue:
182. 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 function *note range(): 9c3. returns an
iterator of integers suitable to emulate the effect of Pascal’s ‘for i
:= a to b do’; e.g., ‘list(range(3))’ returns the list ‘[0, 1, 2]’.

     備註: 
     There is a subtlety when the sequence is being modified by the loop
     (this can only occur for mutable sequences, e.g.  lists).  An
     internal counter is used to keep track of which item is used next,
     and this is incremented on each iteration.  When this counter has
     reached the length of the sequence the loop terminates.  This means
     that if the suite deletes the current (or a previous) item from the
     sequence, the next item will be skipped (since it gets the index of
     the current item which has already been treated).  Likewise, if the
     suite inserts an item in the sequence before the current item, the
     current item will be treated again the next time through the loop.
     This can lead to nasty bugs that can be avoided by making a
     temporary copy using a slice of the whole sequence, e.g.,

          for x in a[:]:
              if x < 0: a.remove(x)


File: python.info,  Node: The try statement,  Next: The with statement,  Prev: The for statement,  Up: Compound statements

4.8.4 The ‘try’ statement
-------------------------

The *note try: d77. statement specifies exception handlers and/or
cleanup code for a group of statements:

     try_stmt  ::= try1_stmt | try2_stmt
     try1_stmt ::= "try" ":" suite
                   ("except" [expression ["as" identifier]] ":" suite)+
                   ["else" ":" suite]
                   ["finally" ":" suite]
     try2_stmt ::= "try" ":" suite
                   "finally" ":" suite

The *note except: b43. clause(s) specify one or more exception handlers.
When no exception occurs in the *note try: d77. 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, that expression
is evaluated, and the clause matches the exception if the resulting
object is "compatible" with the exception.  An object is compatible with
an exception if it is the class or a base class of the exception object,
or a tuple containing an item that is the class or a base class of the
exception object.

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: d77. 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 try 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, details about the exception
are stored in the *note sys: fe. module and can be accessed via *note
sys.exc_info(): c64.  *note sys.exc_info(): c64. returns a 3-tuple
consisting of the exception class, the exception instance and a
traceback object (see section *note The standard type hierarchy: 1426.)
identifying the point in the program where the exception occurred.
*note sys.exc_info(): c64. values are restored to their previous values
(before the call) when returning from a function that handled an
exception.

The optional ‘else’ clause is executed if the control flow leaves the
*note try: d77. suite, no exception was raised, and no *note return:
191, *note continue: 182, or *note break: 2dc. statement was executed.
Exceptions in the ‘else’ clause are not handled by the preceding *note
except: b43. clauses.

If *note finally: 183. is present, it specifies a ’cleanup’ handler.
The *note try: d77. clause is executed, including any *note except: b43.
and ‘else’ 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: 191, *note
break: 2dc. or *note continue: 182. 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 *note finally: 183. clause.

When a *note return: 191, *note break: 2dc. or *note continue: 182.
statement is executed in the *note try: d77. suite of a
‘try’...‘finally’ statement, the *note finally: 183. clause is also
executed ’on the way out.’

The return value of a function is determined by the last *note return:
191. statement executed.  Since the *note finally: 183. 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'

Additional information on exceptions can be found in section *note
Exceptions: 14ae, and information on using the *note raise: c47.
statement to generate exceptions may be found in section *note The raise
statement: c47.

3.8 版更變: Prior to Python 3.8, a *note continue: 182. statement was
illegal in the *note finally: 183. clause due to a problem with the
implementation.

   ---------- Footnotes ----------

   (1) (1) The exception is propagated to the invocation stack unless
there is a *note finally: 183. clause which happens to raise another
exception.  That new exception causes the old one to be lost.


File: python.info,  Node: The with statement,  Next: Function definitions,  Prev: The try statement,  Up: Compound statements

4.8.5 The ‘with’ statement
--------------------------

The *note with: 6ee. statement is used to wrap the execution of a block
with methods defined by a context manager (see section *note With
Statement Context Managers: 148b.).  This allows common *note try:
d77...*note except: b43...*note finally: 183. usage patterns to be
encapsulated for convenient reuse.

     with_stmt ::= "with" with_item ("," with_item)* ":" suite
     with_item ::= expression ["as" target]

The execution of the *note with: 6ee. statement with one "item" proceeds
as follows:

  1. The context expression (the expression given in the *note
     with_item: 15ae.) is evaluated to obtain a context manager.

  2. The context manager’s *note __enter__(): c9a. is loaded for later
     use.

  3. The context manager’s *note __exit__(): c9b. is loaded for later
     use.

  4. The context manager’s *note __enter__(): c9a. method is invoked.

  5. If a target was included in the *note with: 6ee. statement, the
     return value from *note __enter__(): c9a. is assigned to it.

          備註: The *note with: 6ee. statement guarantees that if the
          *note __enter__(): c9a. method returns without an error, then
          *note __exit__(): c9b. 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 6 below.

  6. The suite is executed.

  7. The context manager’s *note __exit__(): c9b. method is invoked.  If
     an exception caused the suite to be exited, its type, value, and
     traceback are passed as arguments to *note __exit__(): c9b.
     Otherwise, three *note None: 158. arguments are supplied.

     If the suite was exited due to an exception, and the return value
     from the *note __exit__(): c9b. 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: 6ee. statement.

     If the suite was exited for any reason other than an exception, the
     return value from *note __exit__(): c9b. 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: 6ee. statements were nested:

     with A() as a, B() as b:
         SUITE

is semantically equivalent to:

     with A() as a:
         with B() as b:
             SUITE

3.1 版更變: Support for multiple context expressions.

也參考
......

PEP 343(1) - The "with" statement

     The specification, background, and examples for the Python *note
     with: 6ee. statement.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0343


File: python.info,  Node: Function definitions,  Next: Class definitions,  Prev: The with statement,  Up: Compound statements

4.8.6 Function definitions
--------------------------

A function definition defines a user-defined function object (see
section *note The standard type hierarchy: 1426.):

     funcdef                   ::= [decorators] "def" funcname "(" [parameter_list] ")"
                                   ["->" expression] ":" suite
     decorators                ::= decorator+
     decorator                 ::= "@" dotted_name ["(" [argument_list [","]] ")"] NEWLINE
     dotted_name               ::= identifier ("." identifier)*
     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:
284. 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

is roughly equivalent to

     def func(): pass
     func = f1(arg)(f2(func))

except that the original function is not temporarily bound to the name
‘func’.

When one or more *note parameters: 1530. 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:
1528. 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 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 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: 651.  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(2) for details.

Parameters may have an *note annotation: 1262. 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: c34.  Note that the
lambda expression is merely a shorthand for a simplified function
definition; a function defined in a "*note def: dc3." 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: 14a4. for
details.

也參考
......

PEP 3107(3) - Function Annotations

     The original specification for function annotations.

PEP 484(4) - Type Hints

     Definition of a standard meaning for annotations: type hints.

PEP 526(5) - Syntax for Variable Annotations

     Ability to type hint variable declarations, including class
     variables and instance variables

PEP 563(6) - Postponed Evaluation of Annotations

     Support for forward references within annotations by preserving
     annotations in a string form at runtime instead of eager
     evaluation.

   ---------- Footnotes ----------

   (1) (2) A string literal appearing as the first statement in the
function body is transformed into the function’s ‘__doc__’ attribute and
therefore the function’s *note docstring: 15ba.

   (2) https://www.python.org/dev/peps/pep-0570

   (3) https://www.python.org/dev/peps/pep-3107

   (4) https://www.python.org/dev/peps/pep-0484

   (5) https://www.python.org/dev/peps/pep-0526

   (6) https://www.python.org/dev/peps/pep-0563


File: python.info,  Node: Class definitions,  Next: Coroutines<2>,  Prev: Function definitions,  Up: Compound statements

4.8.7 Class definitions
-----------------------

A class definition defines a class object (see section *note The
standard type hierarchy: 1426.):

     classdef    ::= [decorators] "class" classname [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: 144d. 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: 2b1.; 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: 14a4.), 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: 144d.

Classes can also be decorated: just like when decorating functions,

     @f1(arg)
     @f2
     class Foo: pass

is roughly equivalent to

     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.

`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: 4ee. can be used to create
instance variables with different implementation details.

也參考
......

PEP 3115(2) - 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(3) - Class Decorators

     The proposal that added class decorators.  Function and method
     decorators were introduced in PEP 318(4).

   ---------- Footnotes ----------

   (1) (3) 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: 15ba.

   (2) https://www.python.org/dev/peps/pep-3115

   (3) https://www.python.org/dev/peps/pep-3129

   (4) https://www.python.org/dev/peps/pep-0318


File: python.info,  Node: Coroutines<2>,  Prev: Class definitions,  Up: Compound statements

4.8.8 Coroutines
----------------

3.5 版新加入.

* Menu:

* Coroutine function definition::
* The async for statement::
* The async with statement::


File: python.info,  Node: Coroutine function definition,  Next: The async for statement,  Up: Coroutines<2>

4.8.8.1 Coroutine function definition
.....................................

     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: 1a7.).  Inside the body of a coroutine
function, ‘await’ and ‘async’ identifiers become reserved keywords;
*note await: 1a4. expressions, *note async for: 2e4. and *note async
with: 648. can only be used in coroutine function bodies.

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: 45d. to use a ‘yield from’ expression inside
the body of a coroutine function.

An example of a coroutine function:

     async def func(param1, param2):
         do_stuff()
         await some_coroutine()


File: python.info,  Node: The async for statement,  Next: The async with statement,  Prev: Coroutine function definition,  Up: Coroutines<2>

4.8.8.2 The ‘async for’ statement
.................................

     async_for_stmt ::= "async" for_stmt

An *note asynchronous iterable: 645. is able to call asynchronous code
in its `iter' implementation, and *note asynchronous iterator: 64a. can
call asynchronous code in its `next' method.

The ‘async for’ statement allows convenient iteration over asynchronous
iterators.

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

See also *note __aiter__(): 48c. and *note __anext__(): 149a. for
details.

It is a *note SyntaxError: 45d. to use an ‘async for’ statement outside
the body of a coroutine function.


File: python.info,  Node: The async with statement,  Prev: The async for statement,  Up: Coroutines<2>

4.8.8.3 The ‘async with’ statement
..................................

     async_with_stmt ::= "async" with_stmt

An *note asynchronous context manager: 646. is a *note context manager:
56d. 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)
     aexit = type(manager).__aexit__
     aenter = type(manager).__aenter__
     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)

See also *note __aenter__(): 149d. and *note __aexit__(): 149e. for
details.

It is a *note SyntaxError: 45d. 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://www.python.org/dev/peps/pep-0492


File: python.info,  Node: Top-level components,  Next: 完整的語法規格書,  Prev: Compound statements,  Up: The Python Language Reference

4.9 Top-level components
========================

The Python interpreter can get its input from a number of sources: from
a script passed to it as standard input or as program argument, typed in
interactively, from a module source file, etc.  This chapter gives the
syntax used in these cases.

* Menu:

* Complete Python programs::
* File input::
* Interactive input::
* Expression input::


File: python.info,  Node: Complete Python programs,  Next: File input,  Up: Top-level components

4.9.1 Complete Python programs
------------------------------

While a language specification need not prescribe how the language
interpreter is invoked, it is useful to have a notion of a complete
Python program.  A complete Python program is executed in a minimally
initialized environment: all built-in and standard modules are
available, but none have been initialized, except for *note sys: fe.
(various system services), *note builtins: 13. (built-in functions,
exceptions and ‘None’) and *note __main__: 1.  The latter is used to
provide the local and global namespace for execution of the complete
program.

The syntax for a complete Python program is that for file input,
described in the next section.

The interpreter may also be invoked in interactive mode; in this case,
it does not read and execute a complete program but reads and executes
one statement (possibly compound) at a time.  The initial environment is
identical to that of a complete program; each statement is executed in
the namespace of *note __main__: 1.

A complete program can be passed to the interpreter in three forms: with
the *note -c: 1210. `string' command line option, as a file passed as
the first command line argument, or as standard input.  If the file or
standard input is a tty device, the interpreter enters interactive mode;
otherwise, it executes the file as a complete program.


File: python.info,  Node: File input,  Next: Interactive input,  Prev: Complete Python programs,  Up: Top-level components

4.9.2 File input
----------------

All input read from non-interactive files has the same form:

     file_input ::= (NEWLINE | statement)*

This syntax is used in the following situations:

   * when parsing a complete Python program (from a file or from a
     string);

   * when parsing a module;

   * when parsing a string passed to the *note exec(): c49. function;


File: python.info,  Node: Interactive input,  Next: Expression input,  Prev: File input,  Up: Top-level components

4.9.3 Interactive input
-----------------------

Input in interactive mode is parsed using the following grammar:

     interactive_input ::= [stmt_list] NEWLINE | compound_stmt NEWLINE

Note that a (top-level) compound statement must be followed by a blank
line in interactive mode; this is needed to help the parser detect the
end of the input.


File: python.info,  Node: Expression input,  Prev: Interactive input,  Up: Top-level components

4.9.4 Expression input
----------------------

*note eval(): b95. is used for expression input.  It ignores leading
whitespace.  The string argument to *note eval(): b95. must have the
following form:

     eval_input ::= expression_list NEWLINE*


File: python.info,  Node: 完整的語法規格書,  Prev: Top-level components,  Up: The Python Language Reference

4.10 完整的語法規格書
=====================

This is the full Python grammar, as it is read by the parser generator
and used to parse Python source files:

     # Grammar for Python

     # NOTE WELL: You should also follow all the steps listed at
     # https://devguide.python.org/grammar/

     # Start symbols for the grammar:
     #       single_input is a single interactive statement;
     #       file_input is a module or sequence of commands read from an input file;
     #       eval_input is the input for the eval() functions.
     #       func_type_input is a PEP 484 Python 2 function type comment
     # NB: compound_stmt in single_input is followed by extra NEWLINE!
     # NB: due to the way TYPE_COMMENT is tokenized it will always be followed by a NEWLINE
     single_input: NEWLINE | simple_stmt | compound_stmt NEWLINE
     file_input: (NEWLINE | stmt)* ENDMARKER
     eval_input: testlist NEWLINE* ENDMARKER

     decorator: '@' dotted_name [ '(' [arglist] ')' ] NEWLINE
     decorators: decorator+
     decorated: decorators (classdef | funcdef | async_funcdef)

     async_funcdef: ASYNC funcdef
     funcdef: 'def' NAME parameters ['->' test] ':' [TYPE_COMMENT] func_body_suite

     parameters: '(' [typedargslist] ')'

     # The following definition for typedarglist is equivalent to this set of rules:
     #
     #     arguments = argument (',' [TYPE_COMMENT] argument)*
     #     argument = tfpdef ['=' test]
     #     kwargs = '**' tfpdef [','] [TYPE_COMMENT]
     #     args = '*' [tfpdef]
     #     kwonly_kwargs = (',' [TYPE_COMMENT] argument)* (TYPE_COMMENT | [',' [TYPE_COMMENT] [kwargs]])
     #     args_kwonly_kwargs = args kwonly_kwargs | kwargs
     #     poskeyword_args_kwonly_kwargs = arguments ( TYPE_COMMENT | [',' [TYPE_COMMENT] [args_kwonly_kwargs]])
     #     typedargslist_no_posonly  = poskeyword_args_kwonly_kwargs | args_kwonly_kwargs
     #     typedarglist = (arguments ',' [TYPE_COMMENT] '/' [',' [[TYPE_COMMENT] typedargslist_no_posonly]])|(typedargslist_no_posonly)"
     #
     # It needs to be fully expanded to allow our LL(1) parser to work on it.

     typedargslist: (
       (tfpdef ['=' test] (',' [TYPE_COMMENT] tfpdef ['=' test])* ',' [TYPE_COMMENT] '/' [',' [ [TYPE_COMMENT] tfpdef ['=' test] (
             ',' [TYPE_COMMENT] tfpdef ['=' test])* (TYPE_COMMENT | [',' [TYPE_COMMENT] [
             '*' [tfpdef] (',' [TYPE_COMMENT] tfpdef ['=' test])* (TYPE_COMMENT | [',' [TYPE_COMMENT] ['**' tfpdef [','] [TYPE_COMMENT]]])
           | '**' tfpdef [','] [TYPE_COMMENT]]])
       | '*' [tfpdef] (',' [TYPE_COMMENT] tfpdef ['=' test])* (TYPE_COMMENT | [',' [TYPE_COMMENT] ['**' tfpdef [','] [TYPE_COMMENT]]])
       | '**' tfpdef [','] [TYPE_COMMENT]]] )
     |  (tfpdef ['=' test] (',' [TYPE_COMMENT] tfpdef ['=' test])* (TYPE_COMMENT | [',' [TYPE_COMMENT] [
        '*' [tfpdef] (',' [TYPE_COMMENT] tfpdef ['=' test])* (TYPE_COMMENT | [',' [TYPE_COMMENT] ['**' tfpdef [','] [TYPE_COMMENT]]])
       | '**' tfpdef [','] [TYPE_COMMENT]]])
       | '*' [tfpdef] (',' [TYPE_COMMENT] tfpdef ['=' test])* (TYPE_COMMENT | [',' [TYPE_COMMENT] ['**' tfpdef [','] [TYPE_COMMENT]]])
       | '**' tfpdef [','] [TYPE_COMMENT])
     )
     tfpdef: NAME [':' test]

     # The following definition for varargslist is equivalent to this set of rules:
     #
     #     arguments = argument (',' argument )*
     #     argument = vfpdef ['=' test]
     #     kwargs = '**' vfpdef [',']
     #     args = '*' [vfpdef]
     #     kwonly_kwargs = (',' argument )* [',' [kwargs]]
     #     args_kwonly_kwargs = args kwonly_kwargs | kwargs
     #     poskeyword_args_kwonly_kwargs = arguments [',' [args_kwonly_kwargs]]
     #     vararglist_no_posonly = poskeyword_args_kwonly_kwargs | args_kwonly_kwargs
     #     varargslist = arguments ',' '/' [','[(vararglist_no_posonly)]] | (vararglist_no_posonly)
     #
     # It needs to be fully expanded to allow our LL(1) parser to work on it.

     varargslist: vfpdef ['=' test ](',' vfpdef ['=' test])* ',' '/' [',' [ (vfpdef ['=' test] (',' vfpdef ['=' test])* [',' [
             '*' [vfpdef] (',' vfpdef ['=' test])* [',' ['**' vfpdef [',']]]
           | '**' vfpdef [',']]]
       | '*' [vfpdef] (',' vfpdef ['=' test])* [',' ['**' vfpdef [',']]]
       | '**' vfpdef [',']) ]] | (vfpdef ['=' test] (',' vfpdef ['=' test])* [',' [
             '*' [vfpdef] (',' vfpdef ['=' test])* [',' ['**' vfpdef [',']]]
           | '**' vfpdef [',']]]
       | '*' [vfpdef] (',' vfpdef ['=' test])* [',' ['**' vfpdef [',']]]
       | '**' vfpdef [',']
     )
     vfpdef: NAME

     stmt: simple_stmt | compound_stmt
     simple_stmt: small_stmt (';' small_stmt)* [';'] NEWLINE
     small_stmt: (expr_stmt | del_stmt | pass_stmt | flow_stmt |
                  import_stmt | global_stmt | nonlocal_stmt | assert_stmt)
     expr_stmt: testlist_star_expr (annassign | augassign (yield_expr|testlist) |
                          [('=' (yield_expr|testlist_star_expr))+ [TYPE_COMMENT]] )
     annassign: ':' test ['=' (yield_expr|testlist_star_expr)]
     testlist_star_expr: (test|star_expr) (',' (test|star_expr))* [',']
     augassign: ('+=' | '-=' | '*=' | '@=' | '/=' | '%=' | '&=' | '|=' | '^=' |
                 '<<=' | '>>=' | '**=' | '//=')
     # For normal and annotated assignments, additional restrictions enforced by the interpreter
     del_stmt: 'del' exprlist
     pass_stmt: 'pass'
     flow_stmt: break_stmt | continue_stmt | return_stmt | raise_stmt | yield_stmt
     break_stmt: 'break'
     continue_stmt: 'continue'
     return_stmt: 'return' [testlist_star_expr]
     yield_stmt: yield_expr
     raise_stmt: 'raise' [test ['from' test]]
     import_stmt: import_name | import_from
     import_name: 'import' dotted_as_names
     # note below: the ('.' | '...') is necessary because '...' is tokenized as ELLIPSIS
     import_from: ('from' (('.' | '...')* dotted_name | ('.' | '...')+)
                   'import' ('*' | '(' import_as_names ')' | import_as_names))
     import_as_name: NAME ['as' NAME]
     dotted_as_name: dotted_name ['as' NAME]
     import_as_names: import_as_name (',' import_as_name)* [',']
     dotted_as_names: dotted_as_name (',' dotted_as_name)*
     dotted_name: NAME ('.' NAME)*
     global_stmt: 'global' NAME (',' NAME)*
     nonlocal_stmt: 'nonlocal' NAME (',' NAME)*
     assert_stmt: 'assert' test [',' test]

     compound_stmt: if_stmt | while_stmt | for_stmt | try_stmt | with_stmt | funcdef | classdef | decorated | async_stmt
     async_stmt: ASYNC (funcdef | with_stmt | for_stmt)
     if_stmt: 'if' namedexpr_test ':' suite ('elif' namedexpr_test ':' suite)* ['else' ':' suite]
     while_stmt: 'while' namedexpr_test ':' suite ['else' ':' suite]
     for_stmt: 'for' exprlist 'in' testlist ':' [TYPE_COMMENT] suite ['else' ':' suite]
     try_stmt: ('try' ':' suite
                ((except_clause ':' suite)+
                 ['else' ':' suite]
                 ['finally' ':' suite] |
                'finally' ':' suite))
     with_stmt: 'with' with_item (',' with_item)*  ':' [TYPE_COMMENT] suite
     with_item: test ['as' expr]
     # NB compile.c makes sure that the default except clause is last
     except_clause: 'except' [test ['as' NAME]]
     suite: simple_stmt | NEWLINE INDENT stmt+ DEDENT

     namedexpr_test: test [':=' test]
     test: or_test ['if' or_test 'else' test] | lambdef
     test_nocond: or_test | lambdef_nocond
     lambdef: 'lambda' [varargslist] ':' test
     lambdef_nocond: 'lambda' [varargslist] ':' test_nocond
     or_test: and_test ('or' and_test)*
     and_test: not_test ('and' not_test)*
     not_test: 'not' not_test | comparison
     comparison: expr (comp_op expr)*
     # <> isn't actually a valid comparison operator in Python. It's here for the
     # sake of a __future__ import described in PEP 401 (which really works :-)
     comp_op: '<'|'>'|'=='|'>='|'<='|'<>'|'!='|'in'|'not' 'in'|'is'|'is' 'not'
     star_expr: '*' expr
     expr: xor_expr ('|' xor_expr)*
     xor_expr: and_expr ('^' and_expr)*
     and_expr: shift_expr ('&' shift_expr)*
     shift_expr: arith_expr (('<<'|'>>') arith_expr)*
     arith_expr: term (('+'|'-') term)*
     term: factor (('*'|'@'|'/'|'%'|'//') factor)*
     factor: ('+'|'-'|'~') factor | power
     power: atom_expr ['**' factor]
     atom_expr: [AWAIT] atom trailer*
     atom: ('(' [yield_expr|testlist_comp] ')' |
            '[' [testlist_comp] ']' |
            '{' [dictorsetmaker] '}' |
            NAME | NUMBER | STRING+ | '...' | 'None' | 'True' | 'False')
     testlist_comp: (namedexpr_test|star_expr) ( comp_for | (',' (namedexpr_test|star_expr))* [','] )
     trailer: '(' [arglist] ')' | '[' subscriptlist ']' | '.' NAME
     subscriptlist: subscript (',' subscript)* [',']
     subscript: test | [test] ':' [test] [sliceop]
     sliceop: ':' [test]
     exprlist: (expr|star_expr) (',' (expr|star_expr))* [',']
     testlist: test (',' test)* [',']
     dictorsetmaker: ( ((test ':' test | '**' expr)
                        (comp_for | (',' (test ':' test | '**' expr))* [','])) |
                       ((test | star_expr)
                        (comp_for | (',' (test | star_expr))* [','])) )

     classdef: 'class' NAME ['(' [arglist] ')'] ':' suite

     arglist: argument (',' argument)*  [',']

     # The reason that keywords are test nodes instead of NAME is that using NAME
     # results in an ambiguity. ast.c makes sure it's a NAME.
     # "test '=' test" is really "keyword '=' test", but we have no such token.
     # These need to be in a single rule to avoid grammar that is ambiguous
     # to our LL(1) parser. Even though 'test' includes '*expr' in star_expr,
     # we explicitly match '*' here, too, to give it proper precedence.
     # Illegal combinations and orderings are blocked in ast.c:
     # multiple (test comp_for) arguments are blocked; keyword unpackings
     # that precede iterable unpackings are blocked; etc.
     argument: ( test [comp_for] |
                 test ':=' test |
                 test '=' test |
                 '**' test |
                 '*' test )

     comp_iter: comp_for | comp_if
     sync_comp_for: 'for' exprlist 'in' or_test [comp_iter]
     comp_for: [ASYNC] sync_comp_for
     comp_if: 'if' test_nocond [comp_iter]

     # not used in grammar, but may appear in "node" passed from Parser to Compiler
     encoding_decl: NAME

     yield_expr: 'yield' [yield_arg]
     yield_arg: 'from' test | testlist_star_expr

     # the TYPE_COMMENT in suites is only parsed for funcdefs,
     # but can't go elsewhere due to ambiguity
     func_body_suite: simple_stmt | NEWLINE [TYPE_COMMENT NEWLINE] INDENT stmt+ DEDENT

     func_type_input: func_type NEWLINE* ENDMARKER
     func_type: '(' [typelist] ')' '->' test
     # typelist is a modified typedargslist (see above)
     typelist: (test (',' test)* [','
            ['*' [test] (',' test)* [',' '**' test] | '**' test]]
          |  '*' [test] (',' test)* [',' '**' test] | '**' test)


File: python.info,  Node: Python 標準函式庫 Standard Library,  Next: Extending and Embedding the Python Interpreter,  Prev: The Python Language Reference,  Up: Top

5 Python 標準函式庫 (Standard Library)
**************************************

*note The Python Language Reference: 1201. 說明 Python 這門語言確切的文
法及語意，而這份函式庫參考手冊則是說明隨著 Python 一起發佈的標準函式庫，
除此之外，其內容也包含一些時常出現在 Python 發佈版本中的非必要套件。

Python 的標準函式庫是非常龐大的，其提供了如下所述極多且涵蓋用途極廣的許
多模組。包含一些用 C 語言撰寫，可以操作像是檔案讀寫等系統相關功能的內建
模組，當然也有用 Python 撰寫，並使用標準解法解決許多常見問題的模組。其中
有些模組則是特別針對 Python 的可攜性去設計的，為此特地將一些平台特殊相依
性的功能抽象化成可跨平台的 API。

Python 的 Windows 安裝檔基本上包含整個標準函式庫，且通常也包含許多額外套
件；而類 Unix 作業系統方面，Python 則提供一系列的套件，對於某些非必要性
的套件，可能得使用該作業系統提供的套件管理工具來安裝。

In addition to the standard library, there is a growing collection of
several thousand components (from individual programs and modules to
packages and entire application development frameworks), available from
the Python Package Index(1).

* Menu:

* 簡介: 簡介<6>.
* 內建函式::
* 內建常數::
* 內建型態::
* 內建的例外::
* Text Processing Services::
* Binary Data Services::
* Data Types::
* 數值與數學模組::
* 函式編程模組::
* 檔案與目錄存取::
* Data Persistence::
* 資料壓縮與保存::
* 檔案格式::
* Cryptographic Services::
* Generic Operating System Services::
* Concurrent Execution::
* Networking and Interprocess Communication::
* Internet Data Handling::
* Structured Markup Processing Tools::
* Internet Protocols and Support::
* Multimedia Services::
* 國際化::
* 程式框架::
* 以 Tk 打造 GUI::
* 開發工具::
* Debugging and Profiling::
* 軟體封裝與發布::
* Python Runtime Services::
* Custom Python Interpreters::
* 匯入模組::
* Python Language Services::
* Miscellaneous Services::
* MS Windows Specific Services::
* Unix Specific Services::
* Superseded Modules::
* Undocumented Modules::

   ---------- Footnotes ----------

   (1) https://pypi.org


File: python.info,  Node: 簡介<6>,  Next: 內建函式,  Up: Python 標準函式庫 Standard Library

5.1 簡介
========

The "Python library" contains several different kinds of components.

It contains data types that would normally be considered part of the
"core" of a language, such as numbers and lists.  For these types, the
Python language core defines the form of literals and places some
constraints on their semantics, but does not fully define the semantics.
(On the other hand, the language core does define syntactic properties
like the spelling and priorities of operators.)

The library also contains built-in functions and exceptions — objects
that can be used by all Python code without the need of an *note import:
c22. statement.  Some of these are defined by the core language, but
many are not essential for the core semantics and are only described
here.

The bulk of the library, however, consists of a collection of modules.
There are many ways to dissect this collection.  Some modules are
written in C and built in to the Python interpreter; others are written
in Python and imported in source form.  Some modules provide interfaces
that are highly specific to Python, like printing a stack trace; some
provide interfaces that are specific to particular operating systems,
such as access to specific hardware; others provide interfaces that are
specific to a particular application domain, like the World Wide Web.
Some modules are available in all versions and ports of Python; others
are only available when the underlying system supports or requires them;
yet others are available only when a particular configuration option was
chosen at the time when Python was compiled and installed.

This manual is organized "from the inside out:" it first describes the
built-in functions, data types and exceptions, and finally the modules,
grouped in chapters of related modules.

This means that if you start reading this manual from the start, and
skip to the next chapter when you get bored, you will get a reasonable
overview of the available modules and application areas that are
supported by the Python library.  Of course, you don’t `have' to read it
like a novel — you can also browse the table of contents (in front of
the manual), or look for a specific function, module or term in the
index (in the back).  And finally, if you enjoy learning about random
subjects, you choose a random page number (see module *note random: dd.)
and read a section or two.  Regardless of the order in which you read
the sections of this manual, it helps to start with chapter *note
內建函式: bf8, as the remainder of the manual assumes familiarity with
this material.

Let the show begin!

* Menu:

* Notes on availability::


File: python.info,  Node: Notes on availability,  Up: 簡介<6>

5.1.1 Notes on availability
---------------------------

   * An "Availability: Unix" note means that this function is commonly
     found on Unix systems.  It does not make any claims about its
     existence on a specific operating system.

   * If not separately noted, all functions that claim "Availability:
     Unix" are supported on Mac OS X, which builds on a Unix core.


File: python.info,  Node: 內建函式,  Next: 內建常數,  Prev: 簡介<6>,  Up: Python 標準函式庫 Standard Library

5.2 內建函式
============

Python 直譯器有內建數十個函式，隨時都可以使用這些函式。以下按照英文字母
排序列出。

                                              內建函式
                                              
---------------------------------------------------------------------------------------------------------------------
                                                                                            
*note abs(): 12c4.      *note delattr(): 15dd.*note hash(): 9c9.     *note memoryview(): 15de.*note set(): 15df.
                                                                                            
                                                                                            
*note all(): d8a.       *note dict(): 15e0.   *note help(): 577.     *note min(): 80e.      *note setattr(): 15e1.
                                                                                            
                                                                                            
*note any(): d89.       *note dir(): d38.     *note hex(): c6b.      *note next(): 687.     *note slice(): e09.
                                                                                            
                                                                                            
*note ascii(): d51.     *note divmod(): 153.  *note id(): d8b.       *note object(): 2b1.   *note sorted(): 449.
                                                                                            
                                                                                            
*note bin(): c45.       *note enumerate(): de8.*note input(): c70.   *note oct(): c6a.      *note staticmethod(): 1da.
                                                                                            
                                                                                            
*note bool(): 184.      *note eval(): b95.    *note int(): 185.      *note open(): 4f5.     *note str(): 15e2.
                                                                                            
                                                                                            
*note breakpoint(): 2fe.*note exec(): c49.    *note isinstance(): 454.*note ord(): 142c.    *note sum(): 1e6.
                                                                                            
                                                                                            
*note bytearray(): 10c3.*note filter(): c33.  *note issubclass(): 455.*note pow(): 19b.     *note super(): 4e7.
                                                                                            
                                                                                            
*note bytes(): 10c2.    *note float(): 188.   *note iter(): d2c.     *note print(): 88b.    *note tuple(): 15e3.
                                                                                            
                                                                                            
*note callable(): b49.  *note format(): 4e0.  *note len(): 151.      *note property(): 1d8. *note type(): 60d.
                                                                                            
                                                                                            
*note chr(): 142d.      *note frozenset(): 15e4.*note list(): 15e5.  *note range(): 15e6.   *note vars(): 103c.
                                                                                            
                                                                                            
*note classmethod(): 1d9.*note getattr(): 44d.*note locals(): 45a.   *note repr(): 7d1.     *note zip(): c37.
                                                                                            
                                                                                            
*note compile(): 1b5.   *note globals(): 15e7.*note map(): c32.      *note reversed(): 18f. *note __import__(): 615.
                                                                                            
                                                                                            
*note complex(): 18a.   *note hasattr(): 44c. *note max(): 80f.      *note round(): c72.
                                                                     

 -- 函式: abs (x)

     Return the absolute value of a number.  The argument may be an
     integer or a floating point number.  If the argument is a complex
     number, its magnitude is returned.  If `x' defines *note __abs__():
     1484, ‘abs(x)’ returns ‘x.__abs__()’.

 -- 函式: all (iterable)

     Return ‘True’ if all elements of the `iterable' are true (or if the
     iterable is empty).  Equivalent to:

          def all(iterable):
              for element in iterable:
                  if not element:
                      return False
              return True

 -- 函式: any (iterable)

     Return ‘True’ if any element of the `iterable' is true.  If the
     iterable is empty, return ‘False’.  Equivalent to:

          def any(iterable):
              for element in iterable:
                  if element:
                      return True
              return False

 -- 函式: ascii (object)

     As *note repr(): 7d1, return a string containing a printable
     representation of an object, but escape the non-ASCII characters in
     the string returned by *note repr(): 7d1. using ‘\x’, ‘\u’ or ‘\U’
     escapes.  This generates a string similar to that returned by *note
     repr(): 7d1. in Python 2.

 -- 函式: bin (x)

     Convert an integer number to a binary string prefixed with "0b".
     The result is a valid Python expression.  If `x' is not a Python
     *note int: 185. object, it has to define an *note __index__(): 18b.
     method that returns an integer.  Some examples:

          >>> bin(3)
          '0b11'
          >>> bin(-10)
          '-0b1010'

     If prefix "0b" is desired or not, you can use either of the
     following ways.

          >>> format(14, '#b'), format(14, 'b')
          ('0b1110', '1110')
          >>> f'{14:#b}', f'{14:b}'
          ('0b1110', '1110')

     See also *note format(): 4e0. for more information.

 -- 類別: bool ([x])

     Return a Boolean value, i.e.  one of ‘True’ or ‘False’.  `x' is
     converted using the standard *note truth testing procedure: 15e8.
     If `x' is false or omitted, this returns ‘False’; otherwise it
     returns ‘True’.  The *note bool: 184. class is a subclass of *note
     int: 185. (see *note Numeric Types — int, float, complex: 1224.).
     It cannot be subclassed further.  Its only instances are ‘False’
     and ‘True’ (see *note Boolean Values: 15e9.).

     3.7 版更變: `x' is now a positional-only parameter.

 -- 函式: breakpoint (*args, **kws)

     This function drops you into the debugger at the call site.
     Specifically, it calls *note sys.breakpointhook(): 318, passing
     ‘args’ and ‘kws’ straight through.  By default,
     ‘sys.breakpointhook()’ calls *note pdb.set_trace(): 3c7. expecting
     no arguments.  In this case, it is purely a convenience function so
     you don’t have to explicitly import *note pdb: ca. or type as much
     code to enter the debugger.  However, *note sys.breakpointhook():
     318. can be set to some other function and *note breakpoint(): 2fe.
     will automatically call that, allowing you to drop into the
     debugger of choice.

     Raises an *note auditing event: e96. ‘builtins.breakpoint’ with
     argument ‘breakpointhook’.

     3.7 版新加入.

 -- 類別: bytearray ([source[, encoding[, errors]]])

     Return a new array of bytes.  The *note bytearray: 337. class is a
     mutable sequence of integers in the range 0 <= x < 256.  It has
     most of the usual methods of mutable sequences, described in *note
     Mutable Sequence Types: 15ea, as well as most methods that the
     *note bytes: 336. type has, see *note Bytes and Bytearray
     Operations: 15eb.

     The optional `source' parameter can be used to initialize the array
     in a few different ways:

        * If it is a `string', you must also give the `encoding' (and
          optionally, `errors') parameters; *note bytearray(): 337. then
          converts the string to bytes using *note str.encode(): c3c.

        * If it is an `integer', the array will have that size and will
          be initialized with null bytes.

        * If it is an object conforming to the *note buffer interface:
          15ec, a read-only buffer of the object will be used to
          initialize the bytes array.

        * If it is an `iterable', it must be an iterable of integers in
          the range ‘0 <= x < 256’, which are used as the initial
          contents of the array.

     Without an argument, an array of size 0 is created.

     See also *note Binary Sequence Types — bytes, bytearray,
     memoryview: 15ed. and *note Bytearray Objects: 15ee.

 -- 類別: bytes ([source[, encoding[, errors]]])

     Return a new "bytes" object, which is an immutable sequence of
     integers in the range ‘0 <= x < 256’.  *note bytes: 336. is an
     immutable version of *note bytearray: 337. – it has the same
     non-mutating methods and the same indexing and slicing behavior.

     Accordingly, constructor arguments are interpreted as for *note
     bytearray(): 337.

     Bytes objects can also be created with literals, see *note String
     and Bytes literals: 13e8.

     See also *note Binary Sequence Types — bytes, bytearray,
     memoryview: 15ed, *note Bytes Objects: 15ef, and *note Bytes and
     Bytearray Operations: 15eb.

 -- 函式: callable (object)

     Return *note True: 49e. if the `object' argument appears callable,
     *note False: 38d. if not.  If this returns ‘True’, it is still
     possible that a call fails, but if it is ‘False’, calling `object'
     will never succeed.  Note that classes are callable (calling a
     class returns a new instance); instances are callable if their
     class has a *note __call__(): 1433. method.

     3.2 版新加入: This function was first removed in Python 3.0 and
     then brought back in Python 3.2.

 -- 函式: chr (i)

     Return the string representing a character whose Unicode code point
     is the integer `i'.  For example, ‘chr(97)’ returns the string
     ‘'a'’, while ‘chr(8364)’ returns the string ‘'€'’.  This is the
     inverse of *note ord(): 142c.

     The valid range for the argument is from 0 through 1,114,111
     (0x10FFFF in base 16).  *note ValueError: 1fc. will be raised if
     `i' is outside that range.

 -- 函式: @classmethod

     Transform a method into a class method.

     A class method receives the class as implicit first argument, just
     like an instance method receives the instance.  To declare a class
     method, use this idiom:

          class C:
              @classmethod
              def f(cls, arg1, arg2, ...): ...

     The ‘@classmethod’ form is a function *note decorator: 284. – see
     *note Function definitions: 1261. for details.

     A class method can be called either on the class (such as ‘C.f()’)
     or on an instance (such as ‘C().f()’).  The instance is ignored
     except for its class.  If a class method is called for a derived
     class, the derived class object is passed as the implied first
     argument.

     Class methods are different than C++ or Java static methods.  If
     you want those, see *note staticmethod(): 1da.

     For more information on class methods, see *note The standard type
     hierarchy: 1426.

 -- 函式: compile (source, filename, mode, flags=0, dont_inherit=False,
          optimize=-1)

     Compile the `source' into a code or AST object.  Code objects can
     be executed by *note exec(): c49. or *note eval(): b95.  `source'
     can either be a normal string, a byte string, or an AST object.
     Refer to the *note ast: 8. module documentation for information on
     how to work with AST objects.

     The `filename' argument should give the file from which the code
     was read; pass some recognizable value if it wasn’t read from a
     file (‘'<string>'’ is commonly used).

     The `mode' argument specifies what kind of code must be compiled;
     it can be ‘'exec'’ if `source' consists of a sequence of
     statements, ‘'eval'’ if it consists of a single expression, or
     ‘'single'’ if it consists of a single interactive statement (in the
     latter case, expression statements that evaluate to something other
     than ‘None’ will be printed).

     The optional arguments `flags' and `dont_inherit' control which
     *note future statements: 1592. affect the compilation of `source'.
     If neither is present (or both are zero) the code is compiled with
     those future statements that are in effect in the code that is
     calling *note compile(): 1b5.  If the `flags' argument is given and
     `dont_inherit' is not (or is zero) then the future statements
     specified by the `flags' argument are used in addition to those
     that would be used anyway.  If `dont_inherit' is a non-zero integer
     then the `flags' argument is it – the future statements in effect
     around the call to compile are ignored.

     Future statements are specified by bits which can be bitwise ORed
     together to specify multiple statements.  The bitfield required to
     specify a given feature can be found as the ‘compiler_flag’
     attribute on the ‘_Feature’ instance in the *note __future__: 0.
     module.

     The optional argument `flags' also controls whether the compiled
     source is allowed to contain top-level ‘await’, ‘async for’ and
     ‘async with’.  When the bit ‘ast.PyCF_ALLOW_TOP_LEVEL_AWAIT’ is
     set, the return code object has ‘CO_COROUTINE’ set in ‘co_code’,
     and can be interactively executed via ‘await eval(code_object)’.

     The argument `optimize' specifies the optimization level of the
     compiler; the default value of ‘-1’ selects the optimization level
     of the interpreter as given by *note -O: 690. options.  Explicit
     levels are ‘0’ (no optimization; ‘__debug__’ is true), ‘1’ (asserts
     are removed, ‘__debug__’ is false) or ‘2’ (docstrings are removed
     too).

     This function raises *note SyntaxError: 45d. if the compiled source
     is invalid, and *note ValueError: 1fc. if the source contains null
     bytes.

     If you want to parse Python code into its AST representation, see
     *note ast.parse(): 1a2.

     Raises an *note auditing event: e96. ‘compile’ with arguments
     ‘source’ and ‘filename’.  This event may also be raised by implicit
     compilation.

          備註: When compiling a string with multi-line code in
          ‘'single'’ or ‘'eval'’ mode, input must be terminated by at
          least one newline character.  This is to facilitate detection
          of incomplete and complete statements in the *note code: 1b.
          module.

          警告: It is possible to crash the Python interpreter with a
          sufficiently large/complex string when compiling to an AST
          object due to stack depth limitations in Python’s AST
          compiler.

     3.2 版更變: Allowed use of Windows and Mac newlines.  Also input in
     ‘'exec'’ mode does not have to end in a newline anymore.  Added the
     `optimize' parameter.

     3.5 版更變: Previously, *note TypeError: 193. was raised when null
     bytes were encountered in `source'.

     3.8 版新加入: ‘ast.PyCF_ALLOW_TOP_LEVEL_AWAIT’ can now be passed in
     flags to enable support for top-level ‘await’, ‘async for’, and
     ‘async with’.

 -- 類別: complex ([real[, imag]])

     Return a complex number with the value `real' + `imag'*1j or
     convert a string or number to a complex number.  If the first
     parameter is a string, it will be interpreted as a complex number
     and the function must be called without a second parameter.  The
     second parameter can never be a string.  Each argument may be any
     numeric type (including complex).  If `imag' is omitted, it
     defaults to zero and the constructor serves as a numeric conversion
     like *note int: 185. and *note float: 188.  If both arguments are
     omitted, returns ‘0j’.

     For a general Python object ‘x’, ‘complex(x)’ delegates to
     ‘x.__complex__()’.  If ‘__complex__()’ is not defined then it falls
     back to *note __float__(): 18d.  If ‘__float__()’ is not defined
     then it falls back to *note __index__(): 18b.

          備註: When converting from a string, the string must not
          contain whitespace around the central ‘+’ or ‘-’ operator.
          For example, ‘complex('1+2j')’ is fine, but ‘complex('1 +
          2j')’ raises *note ValueError: 1fc.

     The complex type is described in *note Numeric Types — int, float,
     complex: 1224.

     3.6 版更變: Grouping digits with underscores as in code literals is
     allowed.

     3.8 版更變: Falls back to *note __index__(): 18b. if *note
     __complex__(): 18e. and *note __float__(): 18d. are not defined.

 -- 函式: delattr (object, name)

     This is a relative of *note setattr(): 15e1.  The arguments are an
     object and a string.  The string must be the name of one of the
     object’s attributes.  The function deletes the named attribute,
     provided the object allows it.  For example, ‘delattr(x, 'foobar')’
     is equivalent to ‘del x.foobar’.

 -- 類別: dict (**kwarg)

 -- 類別: dict (mapping, **kwarg)

 -- 類別: dict (iterable, **kwarg)

     Create a new dictionary.  The *note dict: 1b9. object is the
     dictionary class.  See *note dict: 1b9. and *note Mapping Types —
     dict: 301. for documentation about this class.

     For other containers see the built-in *note list: 263, *note set:
     b74, and *note tuple: 483. classes, as well as the *note
     collections: 1e. module.

 -- 函式: dir ([object])

     Without arguments, return the list of names in the current local
     scope.  With an argument, attempt to return a list of valid
     attributes for that object.

     If the object has a method named *note __dir__(): 320, this method
     will be called and must return the list of attributes.  This allows
     objects that implement a custom *note __getattr__(): 31f. or *note
     __getattribute__(): 44e. function to customize the way *note dir():
     d38. reports their attributes.

     If the object does not provide *note __dir__(): 320, the function
     tries its best to gather information from the object’s *note
     __dict__: 501. attribute, if defined, and from its type object.
     The resulting list is not necessarily complete, and may be
     inaccurate when the object has a custom *note __getattr__(): 31f.

     The default *note dir(): d38. mechanism behaves differently with
     different types of objects, as it attempts to produce the most
     relevant, rather than complete, information:

        * If the object is a module object, the list contains the names
          of the module’s attributes.

        * If the object is a type or class object, the list contains the
          names of its attributes, and recursively of the attributes of
          its bases.

        * Otherwise, the list contains the object’s attributes’ names,
          the names of its class’s attributes, and recursively of the
          attributes of its class’s base classes.

     The resulting list is sorted alphabetically.  For example:

          >>> 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']

          備註: Because *note dir(): d38. is supplied primarily as a
          convenience for use at an interactive prompt, it tries to
          supply an interesting set of names more than it tries to
          supply a rigorously or consistently defined set of names, and
          its detailed behavior may change across releases.  For
          example, metaclass attributes are not in the result list when
          the argument is a class.

 -- 函式: divmod (a, b)

     Take two (non complex) numbers as arguments and return a pair of
     numbers consisting of their quotient and remainder when using
     integer division.  With mixed operand types, the rules for binary
     arithmetic operators apply.  For integers, the result is the same
     as ‘(a // b, a % b)’.  For floating point numbers the result is
     ‘(q, a % b)’, where `q' is usually ‘math.floor(a / b)’ but may be 1
     less than that.  In any case ‘q * b + a % b’ is very close to `a',
     if ‘a % b’ is non-zero it has the same sign as `b', and ‘0 <= abs(a
     % b) < abs(b)’.

 -- 函式: enumerate (iterable, start=0)

     Return an enumerate object.  `iterable' must be a sequence, an
     *note iterator: 1040, or some other object which supports
     iteration.  The *note __next__(): c69. method of the iterator
     returned by *note enumerate(): de8. returns a tuple containing a
     count (from `start' which defaults to 0) and the values obtained
     from iterating over `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')]

     Equivalent to:

          def enumerate(sequence, start=0):
              n = start
              for elem in sequence:
                  yield n, elem
                  n += 1

 -- 函式: eval (expression[, globals[, locals]])

     The arguments are a string and optional globals and locals.  If
     provided, `globals' must be a dictionary.  If provided, `locals'
     can be any mapping object.

     The `expression' argument is parsed and evaluated as a Python
     expression (technically speaking, a condition list) using the
     `globals' and `locals' dictionaries 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: 13. is inserted under that key
     before `expression' is parsed.  This means that `expression'
     normally has full access to the standard *note builtins: 13. module
     and restricted environments are propagated.  If the `locals'
     dictionary is omitted it defaults to the `globals' dictionary.  If
     both dictionaries are omitted, the expression is executed with the
     `globals' and `locals' in the environment where *note eval(): b95.
     is called.  Note, `eval()' does not have access to the *note nested
     scopes: 15f0. (non-locals) in the enclosing environment.

     The return value is the result of the evaluated expression.  Syntax
     errors are reported as exceptions.  Example:

          >>> x = 1
          >>> eval('x+1')
          2

     This function can also be used to execute arbitrary code objects
     (such as those created by *note compile(): 1b5.).  In this case
     pass a code object instead of a string.  If the code object has
     been compiled with ‘'exec'’ as the `mode' argument, *note eval():
     b95.’s return value will be ‘None’.

     Hints: dynamic execution of statements is supported by the *note
     exec(): c49. function.  The *note globals(): 15e7. and *note
     locals(): 45a. functions returns the current global and local
     dictionary, respectively, which may be useful to pass around for
     use by *note eval(): b95. or *note exec(): c49.

     See *note ast.literal_eval(): 4aa. for a function that can safely
     evaluate strings with expressions containing only literals.

     Raises an *note auditing event: e96. ‘exec’ with the code object as
     the argument.  Code compilation events may also be raised.

 -- 函式: exec (object[, globals[, locals]])

     This function supports dynamic execution of Python code.  `object'
     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
     "File input" in the Reference Manual).  Be aware that the *note
     nonlocal: c44, *note yield: 190, and *note return: 191. statements
     may not be used outside of function definitions even within the
     context of code passed to the *note exec(): c49. 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 module level, globals and locals are the
     same dictionary.  If exec gets two separate objects as `globals'
     and `locals', the code will be executed as if it were embedded in a
     class definition.

     If the `globals' dictionary does not contain a value for the key
     ‘__builtins__’, a reference to the dictionary of the built-in
     module *note builtins: 13. is inserted under that key.  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 exec(): c49.

     Raises an *note auditing event: e96. ‘exec’ with the code object as
     the argument.  Code compilation events may also be raised.

          備註: The built-in functions *note globals(): 15e7. and *note
          locals(): 45a. return the current global and local dictionary,
          respectively, which may be useful to pass around for use as
          the second and third argument to *note exec(): c49.

          備註: The default `locals' act as described for function *note
          locals(): 45a. below: modifications to the default `locals'
          dictionary should not be attempted.  Pass an explicit `locals'
          dictionary if you need to see effects of the code on `locals'
          after function *note exec(): c49. returns.

 -- 函式: filter (function, iterable)

     Construct an iterator from those elements of `iterable' for which
     `function' returns true.  `iterable' may be either a sequence, a
     container which supports iteration, or an iterator.  If `function'
     is ‘None’, the identity function is assumed, that is, all elements
     of `iterable' that are false are removed.

     Note that ‘filter(function, iterable)’ is equivalent to the
     generator expression ‘(item for item in iterable if
     function(item))’ if function is not ‘None’ and ‘(item for item in
     iterable if item)’ if function is ‘None’.

     See *note itertools.filterfalse(): 15f1. for the complementary
     function that returns elements of `iterable' for which `function'
     returns false.

 -- 類別: float ([x])

     Return a floating point number constructed from a number or string
     `x'.

     If the argument is a string, it should contain a decimal number,
     optionally preceded by a sign, and optionally embedded in
     whitespace.  The optional sign may be ‘'+'’ or ‘'-'’; a ‘'+'’ sign
     has no effect on the value produced.  The argument may also be a
     string representing a NaN (not-a-number), or a positive or negative
     infinity.  More precisely, the input must conform to the following
     grammar after leading and trailing whitespace characters are
     removed:

          sign           ::= "+" | "-"
          infinity       ::= "Infinity" | "inf"
          nan            ::= "nan"
          numeric_value  ::= floatnumber | infinity | nan
          numeric_string ::= [sign] numeric_value

     Here ‘floatnumber’ is the form of a Python floating-point literal,
     described in *note Floating point literals: 1412.  Case is not
     significant, so, for example, "inf", "Inf", "INFINITY" and
     "iNfINity" are all acceptable spellings for positive infinity.

     Otherwise, if the argument is an integer or a floating point
     number, a floating point number with the same value (within
     Python’s floating point precision) is returned.  If the argument is
     outside the range of a Python float, an *note OverflowError: 965.
     will be raised.

     For a general Python object ‘x’, ‘float(x)’ delegates to
     ‘x.__float__()’.  If ‘__float__()’ is not defined then it falls
     back to *note __index__(): 18b.

     If no argument is given, ‘0.0’ is returned.

     Examples:

          >>> float('+1.23')
          1.23
          >>> float('   -12345\n')
          -12345.0
          >>> float('1e-003')
          0.001
          >>> float('+1E6')
          1000000.0
          >>> float('-Infinity')
          -inf

     The float type is described in *note Numeric Types — int, float,
     complex: 1224.

     3.6 版更變: Grouping digits with underscores as in code literals is
     allowed.

     3.7 版更變: `x' is now a positional-only parameter.

     3.8 版更變: Falls back to *note __index__(): 18b. if *note
     __float__(): 18d. is not defined.

 -- 函式: format (value[, format_spec])

     Convert a `value' to a "formatted" representation, as controlled by
     `format_spec'.  The interpretation of `format_spec' will depend on
     the type of the `value' argument, however there is a standard
     formatting syntax that is used by most built-in types: *note Format
     Specification Mini-Language: 4e3.

     The default `format_spec' is an empty string which usually gives
     the same effect as calling *note str(value): 335.

     A call to ‘format(value, format_spec)’ is translated to
     ‘type(value).__format__(value, format_spec)’ which bypasses the
     instance dictionary when searching for the value’s *note
     __format__(): 953. method.  A *note TypeError: 193. exception is
     raised if the method search reaches *note object: 2b1. and the
     `format_spec' is non-empty, or if either the `format_spec' or the
     return value are not strings.

     3.4 版更變: ‘object().__format__(format_spec)’ raises *note
     TypeError: 193. if `format_spec' is not an empty string.

 -- 類別: frozenset ([iterable])

     Return a new *note frozenset: bf3. object, optionally with elements
     taken from `iterable'.  ‘frozenset’ is a built-in class.  See *note
     frozenset: bf3. and *note Set Types — set, frozenset: 15f7. for
     documentation about this class.

     For other containers see the built-in *note set: b74, *note list:
     263, *note tuple: 483, and *note dict: 1b9. classes, as well as the
     *note collections: 1e. module.

 -- 函式: getattr (object, name[, default])

     Return the value of the named attribute of `object'.  `name' must
     be a string.  If the string is the name of one of the object’s
     attributes, the result is the value of that attribute.  For
     example, ‘getattr(x, 'foobar')’ is equivalent to ‘x.foobar’.  If
     the named attribute does not exist, `default' is returned if
     provided, otherwise *note AttributeError: 3a0. is raised.

 -- 函式: globals ()

     Return a dictionary representing the current global symbol table.
     This is always the dictionary of the current module (inside a
     function or method, this is the module where it is defined, not the
     module from which it is called).

 -- 函式: hasattr (object, name)

     The arguments are an object and a string.  The result is ‘True’ if
     the string is the name of one of the object’s attributes, ‘False’
     if not.  (This is implemented by calling ‘getattr(object, name)’
     and seeing whether it raises an *note AttributeError: 3a0. or not.)

 -- 函式: hash (object)

     Return the hash value of the object (if it has one).  Hash values
     are integers.  They are used to quickly compare dictionary keys
     during a dictionary lookup.  Numeric values that compare equal have
     the same hash value (even if they are of different types, as is the
     case for 1 and 1.0).

          備註: For objects with custom *note __hash__(): 345. methods,
          note that *note hash(): 9c9. truncates the return value based
          on the bit width of the host machine.  See *note __hash__():
          345. for details.

 -- 函式: help ([object])

     Invoke the built-in help system.  (This function is intended for
     interactive use.)  If no argument is given, the interactive help
     system starts on the interpreter console.  If the argument is a
     string, then the string is looked up as the name of a module,
     function, class, method, keyword, or documentation topic, and a
     help page is printed on the console.  If the argument is any other
     kind of object, a help page on the object is generated.

     Note that if a slash(/) appears in the parameter list of a
     function, when invoking *note help(): 577, it means that the
     parameters prior to the slash are positional-only.  For more info,
     see *note the FAQ entry on positional-only parameters: 15f8.

     This function is added to the built-in namespace by the *note site:
     ec. module.

     3.4 版更變: Changes to *note pydoc: da. and *note inspect: a1. mean
     that the reported signatures for callables are now more
     comprehensive and consistent.

 -- 函式: hex (x)

     Convert an integer number to a lowercase hexadecimal string
     prefixed with "0x".  If `x' is not a Python *note int: 185. object,
     it has to define an *note __index__(): 18b. method that returns an
     integer.  Some examples:

          >>> hex(255)
          '0xff'
          >>> hex(-42)
          '-0x2a'

     If you want to convert an integer number to an uppercase or lower
     hexadecimal string with prefix or not, you can use either of the
     following ways:

          >>> '%#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')

     See also *note format(): 4e0. for more information.

     See also *note int(): 185. for converting a hexadecimal string to
     an integer using a base of 16.

          備註: To obtain a hexadecimal string representation for a
          float, use the *note float.hex(): 1329. method.

 -- 函式: id (object)

     Return the "identity" of an object.  This is an integer which is
     guaranteed to be unique and constant for this object during its
     lifetime.  Two objects with non-overlapping lifetimes may have the
     same *note id(): d8b. value.

     `CPython implementation detail:' This is the address of the object
     in memory.

     Raises an *note auditing event: e96. ‘builtins.id’ with argument
     ‘id’.

 -- 函式: input ([prompt])

     If the `prompt' argument is present, it is written to standard
     output without a trailing newline.  The function then reads a line
     from input, converts it to a string (stripping a trailing newline),
     and returns that.  When EOF is read, *note EOFError: c71. is
     raised.  Example:

          >>> s = input('--> ')
          --> Monty Python's Flying Circus
          >>> s
          "Monty Python's Flying Circus"

     If the *note readline: df. module was loaded, then *note input():
     c70. will use it to provide elaborate line editing and history
     features.

     Raises an *note auditing event: e96. ‘builtins.input’ with argument
     ‘prompt’ before reading input

     Raises an auditing event ‘builtins.input/result’ with the result
     after successfully reading input.

 -- 類別: int ([x])

 -- 類別: int (x, base=10)

     Return an integer object constructed from a number or string `x',
     or return ‘0’ if no arguments are given.  If `x' defines *note
     __int__(): 18c, ‘int(x)’ returns ‘x.__int__()’.  If `x' defines
     *note __index__(): 18b, it returns ‘x.__index__()’.  If `x' defines
     *note __trunc__(): 1488, it returns ‘x.__trunc__()’.  For floating
     point numbers, this truncates towards zero.

     If `x' is not a number or if `base' is given, then `x' must be a
     string, *note bytes: 336, or *note bytearray: 337. instance
     representing an *note integer literal: 1407. in radix `base'.
     Optionally, the literal can be preceded by ‘+’ or ‘-’ (with no
     space in between) and surrounded by whitespace.  A base-n literal
     consists of the digits 0 to n-1, with ‘a’ to ‘z’ (or ‘A’ to ‘Z’)
     having values 10 to 35.  The default `base' is 10.  The allowed
     values are 0 and 2–36.  Base-2, -8, and -16 literals can be
     optionally prefixed with ‘0b’/‘0B’, ‘0o’/‘0O’, or ‘0x’/‘0X’, as
     with integer literals in code.  Base 0 means to interpret exactly
     as a code literal, so that the actual base is 2, 8, 10, or 16, and
     so that ‘int('010', 0)’ is not legal, while ‘int('010')’ is, as
     well as ‘int('010', 8)’.

     The integer type is described in *note Numeric Types — int, float,
     complex: 1224.

     3.4 版更變: If `base' is not an instance of *note int: 185. and the
     `base' object has a *note base.__index__: 18b. method, that method
     is called to obtain an integer for the base.  Previous versions
     used *note base.__int__: 18c. instead of *note base.__index__: 18b.

     3.6 版更變: Grouping digits with underscores as in code literals is
     allowed.

     3.7 版更變: `x' is now a positional-only parameter.

     3.8 版更變: Falls back to *note __index__(): 18b. if *note
     __int__(): 18c. is not defined.

 -- 函式: isinstance (object, classinfo)

     Return ‘True’ if the `object' argument is an instance of the
     `classinfo' argument, or of a (direct, indirect or *note virtual:
     b38.) subclass thereof.  If `object' is not an object of the given
     type, the function always returns ‘False’.  If `classinfo' is a
     tuple of type objects (or recursively, other such tuples), return
     ‘True’ if `object' is an instance of any of the types.  If
     `classinfo' is not a type or tuple of types and such tuples, a
     *note TypeError: 193. exception is raised.

 -- 函式: issubclass (class, classinfo)

     Return ‘True’ if `class' is a subclass (direct, indirect or *note
     virtual: b38.) of `classinfo'.  A class is considered a subclass of
     itself.  `classinfo' may be a tuple of class objects, in which case
     every entry in `classinfo' will be checked.  In any other case, a
     *note TypeError: 193. exception is raised.

 -- 函式: iter (object[, sentinel])

     Return an *note iterator: 1040. object.  The first argument is
     interpreted very differently depending on the presence of the
     second argument.  Without a second argument, `object' must be a
     collection object which supports the iteration protocol (the *note
     __iter__(): 514. method), or it must support the sequence protocol
     (the *note __getitem__(): 27d. method with integer arguments
     starting at ‘0’).  If it does not support either of those
     protocols, *note TypeError: 193. is raised.  If the second
     argument, `sentinel', is given, then `object' must be a callable
     object.  The iterator created in this case will call `object' with
     no arguments for each call to its *note __next__(): c69. method; if
     the value returned is equal to `sentinel', *note StopIteration:
     48b. will be raised, otherwise the value will be returned.

     See also *note Iterator Types: 1461.

     One useful application of the second form of *note iter(): d2c. is
     to build a block-reader.  For example, reading fixed-width blocks
     from a binary database file until the end of file is reached:

          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)

     Return the length (the number of items) of an object.  The argument
     may be a sequence (such as a string, bytes, tuple, list, or range)
     or a collection (such as a dictionary, set, or frozen set).

 -- 類別: list ([iterable])

     Rather than being a function, *note list: 263. is actually a
     mutable sequence type, as documented in *note List（串列）: 15f9.
     and *note Sequence Types — list, tuple, range: 1275.

 -- 函式: locals ()

     Update and return a dictionary representing the current local
     symbol table.  Free variables are returned by *note locals(): 45a.
     when it is called in function blocks, but not in class blocks.
     Note that at the module level, *note locals(): 45a. and *note
     globals(): 15e7. are the same dictionary.

          備註: The contents of this dictionary should not be modified;
          changes may not affect the values of local and free variables
          used by the interpreter.

 -- 函式: map (function, iterable, ...)

     Return an iterator that applies `function' to every item of
     `iterable', yielding the results.  If additional `iterable'
     arguments are passed, `function' must take that many arguments and
     is applied to the items from all iterables in parallel.  With
     multiple iterables, the iterator stops when the shortest iterable
     is exhausted.  For cases where the function inputs are already
     arranged into argument tuples, see *note itertools.starmap(): a2d.

 -- 函式: max (iterable, *[, key, default])

 -- 函式: max (arg1, arg2, *args[, key])

     Return the largest item in an iterable or the largest of two or
     more arguments.

     If one positional argument is provided, it should be an *note
     iterable: bb1.  The largest item in the iterable is returned.  If
     two or more positional arguments are provided, the largest of the
     positional arguments is returned.

     There are two optional keyword-only arguments.  The `key' argument
     specifies a one-argument ordering function like that used for *note
     list.sort(): 44a.  The `default' argument specifies an object to
     return if the provided iterable is empty.  If the iterable is empty
     and `default' is not provided, a *note ValueError: 1fc. is raised.

     If multiple items are maximal, the function returns the first one
     encountered.  This is consistent with other sort-stability
     preserving tools such as ‘sorted(iterable, key=keyfunc,
     reverse=True)[0]’ and ‘heapq.nlargest(1, iterable, key=keyfunc)’.

     3.4 版新加入: The `default' keyword-only argument.

     3.8 版更變: The `key' can be ‘None’.

 -- 類別: memoryview (obj)

     Return a "memory view" object created from the given argument.  See
     *note Memory Views: 15fa. for more information.

 -- 函式: min (iterable, *[, key, default])

 -- 函式: min (arg1, arg2, *args[, key])

     Return the smallest item in an iterable or the smallest of two or
     more arguments.

     If one positional argument is provided, it should be an *note
     iterable: bb1.  The smallest item in the iterable is returned.  If
     two or more positional arguments are provided, the smallest of the
     positional arguments is returned.

     There are two optional keyword-only arguments.  The `key' argument
     specifies a one-argument ordering function like that used for *note
     list.sort(): 44a.  The `default' argument specifies an object to
     return if the provided iterable is empty.  If the iterable is empty
     and `default' is not provided, a *note ValueError: 1fc. is raised.

     If multiple items are minimal, the function returns the first one
     encountered.  This is consistent with other sort-stability
     preserving tools such as ‘sorted(iterable, key=keyfunc)[0]’ and
     ‘heapq.nsmallest(1, iterable, key=keyfunc)’.

     3.4 版新加入: The `default' keyword-only argument.

     3.8 版更變: The `key' can be ‘None’.

 -- 函式: next (iterator[, default])

     Retrieve the next item from the `iterator' by calling its *note
     __next__(): c69. method.  If `default' is given, it is returned if
     the iterator is exhausted, otherwise *note StopIteration: 48b. is
     raised.

 -- 類別: object

     Return a new featureless object.  *note object: 2b1. is a base for
     all classes.  It has the methods that are common to all instances
     of Python classes.  This function does not accept any arguments.

          備註: *note object: 2b1. does `not' have a *note __dict__:
          501, so you can’t assign arbitrary attributes to an instance
          of the *note object: 2b1. class.

 -- 函式: oct (x)

     Convert an integer number to an octal string prefixed with "0o".
     The result is a valid Python expression.  If `x' is not a Python
     *note int: 185. object, it has to define an *note __index__(): 18b.
     method that returns an integer.  For example:

          >>> oct(8)
          '0o10'
          >>> oct(-56)
          '-0o70'

     If you want to convert an integer number to octal string either
     with prefix "0o" or not, you can use either of the following ways.

          >>> '%#o' % 10, '%o' % 10
          ('0o12', '12')
          >>> format(10, '#o'), format(10, 'o')
          ('0o12', '12')
          >>> f'{10:#o}', f'{10:o}'
          ('0o12', '12')

     See also *note format(): 4e0. for more information.

 -- 函式: open (file, mode='r', buffering=-1, encoding=None,
          errors=None, newline=None, closefd=True, opener=None)

     Open `file' and return a corresponding *note file object: b47.  If
     the file cannot be opened, an *note OSError: 1d4. is raised.  See
     *note Reading and Writing Files: 12a5. for more examples of how to
     use this function.

     `file' is a *note path-like object: 36f. giving the pathname
     (absolute or relative to the current working directory) of the file
     to be opened or an integer file descriptor of the file to be
     wrapped.  (If a file descriptor is given, it is closed when the
     returned I/O object is closed, unless `closefd' is set to ‘False’.)

     `mode' is an optional string that specifies the mode in which the
     file is opened.  It defaults to ‘'r'’ which means open for reading
     in text mode.  Other common values are ‘'w'’ for writing
     (truncating the file if it already exists), ‘'x'’ for exclusive
     creation and ‘'a'’ for appending (which on `some' Unix systems,
     means that `all' writes append to the end of the file regardless of
     the current seek position).  In text mode, if `encoding' is not
     specified the encoding used is platform dependent:
     ‘locale.getpreferredencoding(False)’ is called to get the current
     locale encoding.  (For reading and writing raw bytes use binary
     mode and leave `encoding' unspecified.)  The available modes are:

     Character     Meaning
                   
     ----------------------------------------------------------------------------------
                   
     ‘'r'’         open for reading (default)
                   
                   
     ‘'w'’         open for writing, truncating the file first
                   
                   
     ‘'x'’         open for exclusive creation, failing if the file already exists
                   
                   
     ‘'a'’         open for writing, appending to the end of the file if it exists
                   
                   
     ‘'b'’         binary mode
                   
                   
     ‘'t'’         text mode (default)
                   
                   
     ‘'+'’         open for updating (reading and writing)
                   

     The default mode is ‘'r'’ (open for reading text, synonym of
     ‘'rt'’).  Modes ‘'w+'’ and ‘'w+b'’ open and truncate the file.
     Modes ‘'r+'’ and ‘'r+b'’ open the file with no truncation.

     As mentioned in the *note 總覽: 15fc, Python distinguishes between
     binary and text I/O. Files opened in binary mode (including ‘'b'’
     in the `mode' argument) return contents as *note bytes: 336.
     objects without any decoding.  In text mode (the default, or when
     ‘'t'’ is included in the `mode' argument), the contents of the file
     are returned as *note str: 335, the bytes having been first decoded
     using a platform-dependent encoding or using the specified
     `encoding' if given.

     There is an additional mode character permitted, ‘'U'’, which no
     longer has any effect, and is considered deprecated.  It previously
     enabled *note universal newlines: 5f9. in text mode, which became
     the default behaviour in Python 3.0.  Refer to the documentation of
     the *note newline: 15fd. parameter for further details.

          備註: Python doesn’t depend on the underlying operating
          system’s notion of text files; all the processing is done by
          Python itself, and is therefore platform-independent.

     `buffering' is an optional integer used to set the buffering
     policy.  Pass 0 to switch buffering off (only allowed in binary
     mode), 1 to select line buffering (only usable in text mode), and
     an integer > 1 to indicate the size in bytes of a fixed-size chunk
     buffer.  When no `buffering' argument is given, the default
     buffering policy works as follows:

        * Binary files are buffered in fixed-size chunks; the size of
          the buffer is chosen using a heuristic trying to determine the
          underlying device’s "block size" and falling back on *note
          io.DEFAULT_BUFFER_SIZE: 15fe.  On many systems, the buffer
          will typically be 4096 or 8192 bytes long.

        * "Interactive" text files (files for which *note isatty():
          15ff. returns ‘True’) use line buffering.  Other text files
          use the policy described above for binary files.

     `encoding' is the name of the encoding used to decode or encode the
     file.  This should only be used in text mode.  The default encoding
     is platform dependent (whatever *note
     locale.getpreferredencoding(): 3aa. returns), but any *note text
     encoding: 1600. supported by Python can be used.  See the *note
     codecs: 1c. module for the list of supported encodings.

     `errors' is an optional string that specifies how encoding and
     decoding errors are to be handled—this cannot be used in binary
     mode.  A variety of standard error handlers are available (listed
     under *note Error Handlers: 1366.), though any error handling name
     that has been registered with *note codecs.register_error(): dfa.
     is also valid.  The standard names include:

        * ‘'strict'’ to raise a *note ValueError: 1fc. exception if
          there is an encoding error.  The default value of ‘None’ has
          the same effect.

        * ‘'ignore'’ ignores 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.

        * ‘'surrogateescape'’ will represent any incorrect bytes as code
          points in the Unicode Private Use Area ranging from U+DC80 to
          U+DCFF. These private code points will then be turned back
          into the same bytes when the ‘surrogateescape’ error handler
          is used when writing data.  This is useful for processing
          files in an unknown encoding.

        * ‘'xmlcharrefreplace'’ is only supported when writing to a
          file.  Characters not supported by the encoding are replaced
          with the appropriate XML character reference ‘&#nnn;’.

        * ‘'backslashreplace'’ replaces malformed data by Python’s
          backslashed escape sequences.

        * ‘'namereplace'’ (also only supported when writing) replaces
          unsupported characters with ‘\N{...}’ escape sequences.

     `newline' controls how *note universal newlines: 5f9. mode works
     (it only applies to text mode).  It can be ‘None’, ‘''’, ‘'\n'’,
     ‘'\r'’, and ‘'\r\n'’.  It works as follows:

        * When reading input from the stream, if `newline' is ‘None’,
          universal newlines 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 it is
          ‘''’, universal newlines mode is enabled, but line endings are
          returned to the caller untranslated.  If it 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: 1601.  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 `closefd' is ‘False’ and a file descriptor rather than a
     filename was given, the underlying file descriptor will be kept
     open when the file is closed.  If a filename is given `closefd'
     must be ‘True’ (the default) otherwise an error will be raised.

     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 (`file', `flags').  `opener' must return an
     open file descriptor (passing *note os.open: 66a. as `opener'
     results in functionality similar to passing ‘None’).

     The newly created file is *note non-inheritable: 7ff.

     The following example uses the *note dir_fd: a34. parameter of the
     *note os.open(): 66a. function to open a file relative to a given
     directory:

          >>> 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

     The type of *note file object: b47. returned by the *note open():
     4f5. function depends on the mode.  When *note open(): 4f5. is used
     to open a file in a text mode (‘'w'’, ‘'r'’, ‘'wt'’, ‘'rt'’, etc.),
     it returns a subclass of *note io.TextIOBase: c3e. (specifically
     *note io.TextIOWrapper: 5f8.).  When used to open a file in a
     binary mode with buffering, the returned class is a subclass of
     *note io.BufferedIOBase: 58d.  The exact class varies: in read
     binary mode, it returns an *note io.BufferedReader: b8f.; in write
     binary and append binary modes, it returns an *note
     io.BufferedWriter: 1602, and in read/write mode, it returns an
     *note io.BufferedRandom: 1603.  When buffering is disabled, the raw
     stream, a subclass of *note io.RawIOBase: a18, *note io.FileIO:
     ca9, is returned.

     See also the file handling modules, such as, *note fileinput: 80,
     *note io: a2. (where *note open(): 4f5. is declared), *note os: c5,
     *note os.path: c6, *note tempfile: 104, and *note shutil: ea.

     Raises an *note auditing event: e96. ‘open’ with arguments ‘file’,
     ‘mode’, ‘flags’.

     The ‘mode’ and ‘flags’ arguments may have been modified or inferred
     from the original call.

          3.3 版更變:

             * The `opener' parameter was added.

             * The ‘'x'’ mode was added.

             * *note IOError: 997. used to be raised, it is now an alias
               of *note OSError: 1d4.

             * *note FileExistsError: 95d. is now raised if the file
               opened in exclusive creation mode (‘'x'’) already exists.

          3.4 版更變:

             * The file is now non-inheritable.

     Deprecated since version 3.4, will be removed in version 3.9: The
     ‘'U'’ mode.

          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:
               65e. exception (see PEP 475(2) for the rationale).

             * The ‘'namereplace'’ error handler was added.

          3.6 版更變:

             * Support added to accept objects implementing *note
               os.PathLike: 4f0.

             * On Windows, opening a console buffer may return a
               subclass of *note io.RawIOBase: a18. other than *note
               io.FileIO: ca9.

 -- 函式: ord (c)

     Given a string representing one Unicode character, return an
     integer representing the Unicode code point of that character.  For
     example, ‘ord('a')’ returns the integer ‘97’ and ‘ord('€')’ (Euro
     sign) returns ‘8364’.  This is the inverse of *note chr(): 142d.

 -- 函式: pow (base, exp[, mod])

     Return `base' to the power `exp'; if `mod' is present, return
     `base' to the power `exp', modulo `mod' (computed more efficiently
     than ‘pow(base, exp) % mod’).  The two-argument form ‘pow(base,
     exp)’ is equivalent to using the power operator: ‘base**exp’.

     The arguments must have numeric types.  With mixed operand types,
     the coercion rules for binary arithmetic operators apply.  For
     *note int: 185. 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, ‘10**2’ returns ‘100’, but
     ‘10**-2’ returns ‘0.01’.

     For *note int: 185. operands `base' and `exp', if `mod' is present,
     `mod' must also be of integer type and `mod' must be nonzero.  If
     `mod' is present and `exp' is negative, `base' must be relatively
     prime to `mod'.  In that case, ‘pow(inv_base, -exp, mod)’ is
     returned, where `inv_base' is an inverse to `base' modulo `mod'.

     Here’s an example of computing an inverse for ‘38’ modulo ‘97’:

          >>> pow(38, -1, mod=97)
          23
          >>> 23 * 38 % 97 == 1
          True

     3.8 版更變: For *note int: 185. operands, the three-argument form
     of ‘pow’ now allows the second argument to be negative, permitting
     computation of modular inverses.

     3.8 版更變: Allow keyword arguments.  Formerly, only positional
     arguments were supported.

 -- 函式: print (*objects, sep=' ', end='\n', file=sys.stdout,
          flush=False)

     Print `objects' to the text stream `file', separated by `sep' and
     followed by `end'.  `sep', `end', `file' and `flush', if present,
     must be given as keyword arguments.

     All non-keyword arguments are converted to strings like *note
     str(): 335. does and written to the stream, separated by `sep' and
     followed by `end'.  Both `sep' and `end' must be strings; they can
     also be ‘None’, which means to use the default values.  If no
     `objects' are given, *note print(): 88b. will just write `end'.

     The `file' argument must be an object with a ‘write(string)’
     method; if it is not present or ‘None’, *note sys.stdout: 313. will
     be used.  Since printed arguments are converted to text strings,
     *note print(): 88b. cannot be used with binary mode file objects.
     For these, use ‘file.write(...)’ instead.

     Whether output is buffered is usually determined by `file', but if
     the `flush' keyword argument is true, the stream is forcibly
     flushed.

     3.3 版更變: Added the `flush' keyword argument.

 -- 類別: property (fget=None, fset=None, fdel=None, doc=None)

     Return a property attribute.

     `fget' is a function for getting an attribute value.  `fset' is a
     function for setting an attribute value.  `fdel' is a function for
     deleting an attribute value.  And `doc' creates a docstring for the
     attribute.

     A typical use is to define a managed attribute ‘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.")

     If `c' is an instance of `C', ‘c.x’ will invoke the getter, ‘c.x =
     value’ will invoke the setter and ‘del c.x’ the deleter.

     If given, `doc' will be the docstring of the property attribute.
     Otherwise, the property will copy `fget'’s docstring (if it
     exists).  This makes it possible to create read-only properties
     easily using *note property(): 1d8. as a *note decorator: 284.:

          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."

     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.

 -- 類別: range (stop)

 -- 類別: range (start, stop[, step])

     Rather than being a function, *note range: 9c3. is actually an
     immutable sequence type, as documented in *note Ranges: 1604. and
     *note Sequence Types — list, tuple, range: 1275.

 -- 函式: 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(): b95, 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__(): 343.
     method.

 -- 函式: reversed (seq)

     Return a reverse *note iterator: 1040.  `seq' must be an object
     which has a *note __reversed__(): 534. method or supports the
     sequence protocol (the *note __len__(): dd0. method and the *note
     __getitem__(): 27d. method with integer arguments starting at ‘0’).

 -- 函式: round (number[, ndigits])

     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(): c72, 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(): c72. 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
          浮點數運算：問題與限制: 1327. for more information.

 -- 類別: set ([iterable])

     Return a new *note set: b74. object, optionally with elements taken
     from `iterable'.  ‘set’ is a built-in class.  See *note set: b74.
     and *note Set Types — set, frozenset: 15f7. for documentation about
     this class.

     For other containers see the built-in *note frozenset: bf3, *note
     list: 263, *note tuple: 483, and *note dict: 1b9. classes, as well
     as the *note collections: 1e. module.

 -- 函式: setattr (object, name, value)

     This is the counterpart of *note getattr(): 44d.  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’.

 -- 類別: slice (stop)

 -- 類別: slice (start, stop[, step])

     Return a *note slice: 1605. object representing the set of indices
     specified by ‘range(start, stop, step)’.  The `start' and `step'
     arguments default to ‘None’.  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 Numerical Python and other
     third party extensions.  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(): 3a7. for an alternate version that returns an
     iterator.

 -- 函式: 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(): b5b. to convert an old-style
     `cmp' function to a `key' function.

     The built-in *note sorted(): 449. 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).

     For sorting examples and a brief sorting tutorial, see *note
     如何排序: 1606.

 -- 函式: @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, ...): ...

     The ‘@staticmethod’ form is a function *note decorator: 284. – see
     *note Function definitions: 1261. for details.

     A static method can be called either on the class (such as ‘C.f()’)
     or on an instance (such as ‘C().f()’).

     Static methods in Python are similar to those found in Java or C++.
     Also see *note classmethod(): 1d9. 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:

          class C:
              builtin_open = staticmethod(open)

     For more information on static methods, see *note The standard type
     hierarchy: 1426.

 -- 類別: str (object='')

 -- 類別: str (object=b'', encoding='utf-8', errors='strict')

     Return a *note str: 335. version of `object'.  See *note str():
     335. for details.

     ‘str’ is the built-in string *note class: 1607.  For general
     information about strings, see *note Text Sequence Type — str:
     1228.

 -- 函式: 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():
     1e6.  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(): d43.  To
     concatenate a series of iterables, consider using *note
     itertools.chain(): 1608.

     3.8 版更變: The `start' parameter can be specified as a keyword
     argument.

 -- 函式: super ([type[, object-or-type]])

     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:
     1609. to be searched.  The search starts from the class right after
     the `type'.

     For example, if *note __mro__: 160a. of `object-or-type' is ‘D -> B
     -> C -> A -> object’ and the value of `type' is ‘B’, then *note
     super(): 4e7. searches ‘C -> A -> object’.

     The *note __mro__: 160a. attribute of the `object-or-type' lists
     the method resolution search order used by both *note getattr():
     44d. and *note super(): 4e7.  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).

     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(): 4e7. also works for
     attribute lookups.  One possible use case for this is calling *note
     descriptors: 160b. in a parent or sibling class.

     Note that *note super(): 4e7. 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__(): 44e. method for searching classes in a
     predictable order that supports cooperative multiple inheritance.
     Accordingly, *note super(): 4e7. is undefined for implicit lookups
     using statements or operators such as ‘super()[name]’.

     Also note that, aside from the zero argument form, *note super():
     4e7. 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(): 4e7, see guide to using super()(3).

 -- 類別: tuple ([iterable])

     Rather than being a function, *note tuple: 483. is actually an
     immutable sequence type, as documented in *note Tuples: 160c. and
     *note Sequence Types — list, tuple, range: 1275.

 -- 類別: 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__: e0f.

     The *note isinstance(): 454. 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: c6f. statement.  The
     `name' string is the class name and becomes the *note __name__:
     c6c. attribute.  The `bases' tuple contains the base classes and
     becomes the *note __bases__: e0e. attribute; if empty, *note
     object: 2b1, 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__: 501. attribute.  The following two statements create
     identical *note type: 60d. objects:

          >>> class X:
          ...     a = 1
          ...
          >>> X = type('X', (), dict(a=1))

     See also *note Type Objects: 160d.

     Keyword arguments provided to the three argument form are passed to
     the appropriate metaclass machinery (usually *note
     __init_subclass__(): 4e8.) in the same way that keywords in a class
     definition (besides `metaclass') would.

     See also *note Customizing class creation: 4ea.

     3.6 版更變: Subclasses of *note type: 60d. which don’t override
     ‘type.__new__’ may no longer use the one-argument form to get the
     type of an object.

 -- 函式: vars ([object])

     Return the *note __dict__: 501. attribute for a module, class,
     instance, or any other object with a *note __dict__: 501.
     attribute.

     Objects such as modules and instances have an updateable *note
     __dict__: 501. attribute; however, other objects may have write
     restrictions on their *note __dict__: 501. attributes (for example,
     classes use a *note types.MappingProxyType: abb. to prevent direct
     dictionary updates).

     Without an argument, *note vars(): 103c. acts like *note locals():
     45a.  Note, the locals dictionary is only useful for reads since
     updates to the locals dictionary are ignored.

     A *note TypeError: 193. exception is raised if an object is
     specified but it doesn’t have a *note __dict__: 501. attribute (for
     example, if its class defines the *note __slots__: e32. attribute).

 -- 函式: zip (*iterables)

     Make an iterator that aggregates elements from each of the
     iterables.

     Returns an iterator of tuples, where the `i'-th tuple contains the
     `i'-th element from each of the argument sequences or iterables.
     The iterator stops when the shortest input iterable is exhausted.
     With a single iterable argument, it returns an iterator of
     1-tuples.  With no arguments, it returns an empty iterator.
     Equivalent to:

          def zip(*iterables):
              # zip('ABCD', 'xy') --> Ax By
              sentinel = object()
              iterators = [iter(it) for it in iterables]
              while iterators:
                  result = []
                  for it in iterators:
                      elem = next(it, sentinel)
                      if elem is sentinel:
                          return
                      result.append(elem)
                  yield tuple(result)

     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)’.  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(): c37. should only be used with unequal length inputs
     when you don’t care about trailing, unmatched values from the
     longer iterables.  If those values are important, use *note
     itertools.zip_longest(): c36. instead.

     *note zip(): c37. in conjunction with the ‘*’ operator can be used
     to unzip a list:

          >>> x = [1, 2, 3]
          >>> y = [4, 5, 6]
          >>> zipped = zip(x, y)
          >>> list(zipped)
          [(1, 4), (2, 5), (3, 6)]
          >>> x2, y2 = zip(*zip(x, y))
          >>> x == list(x2) and y == list(y2)
          True

 -- 函式: __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(): b18.

     This function is invoked by the *note import: c22. statement.  It
     can be replaced (by importing the *note builtins: 13. 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(4)) 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__(): 615. is also discouraged in favor of *note
     importlib.import_module(): b18.

     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: c22. 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__():
     615. (see PEP 328(5) 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__(): 615. returns the toplevel module here
     because this is the object that is bound to a name by the *note
     import: c22. 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__():
     615.  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(): b18.

     3.3 版更變: Negative values for `level' are no longer supported
     (which also changes the default value to 0).

註解
....

   ---------- Footnotes ----------

   (1) (1) Note that the parser only accepts the Unix-style end of line
convention.  If you are reading the code from a file, make sure to use
newline conversion mode to convert Windows or Mac-style newlines.

   (2) https://www.python.org/dev/peps/pep-0475

   (3) 
https://rhettinger.wordpress.com/2011/05/26/super-considered-super/

   (4) https://www.python.org/dev/peps/pep-0302

   (5) https://www.python.org/dev/peps/pep-0328


File: python.info,  Node: 內建常數,  Next: 內建型態,  Prev: 內建函式,  Up: Python 標準函式庫 Standard Library

5.3 內建常數
============

A small number of constants live in the built-in namespace.  They are:

 -- Data: False

     The false value of the *note bool: 184. type.  Assignments to
     ‘False’ are illegal and raise a *note SyntaxError: 45d.

 -- Data: True

     The true value of the *note bool: 184. type.  Assignments to ‘True’
     are illegal and raise a *note SyntaxError: 45d.

 -- Data: None

     The sole value of the type ‘NoneType’.  ‘None’ is frequently used
     to represent the absence of a value, as when default arguments are
     not passed to a function.  Assignments to ‘None’ are illegal and
     raise a *note SyntaxError: 45d.

 -- Data: NotImplemented

     Special value which should be returned by the binary special
     methods (e.g.  *note __eq__(): 344, *note __lt__(): c39, *note
     __add__(): 145c, *note __rsub__(): 146e, etc.)  to indicate that
     the operation is not implemented with respect to the other type;
     may be returned by the in-place binary special methods (e.g.  *note
     __imul__(): 1460, *note __iand__(): 147e, etc.)  for the same
     purpose.  Its truth value is true.

          備註: When a binary (or in-place) method returns
          ‘NotImplemented’ the interpreter will try the reflected
          operation on the other type (or some other fallback, depending
          on the operator).  If all attempts return ‘NotImplemented’,
          the interpreter will raise an appropriate exception.
          Incorrectly returning ‘NotImplemented’ will result in a
          misleading error message or the ‘NotImplemented’ value being
          returned to Python code.

          See *note Implementing the arithmetic operations: 1427. for
          examples.

          備註: ‘NotImplementedError’ and ‘NotImplemented’ are not
          interchangeable, even though they have similar names and
          purposes.  See *note NotImplementedError: 613. for details on
          when to use it.

 -- Data: Ellipsis

     The same as the ellipsis literal "‘...’".  Special value used
     mostly in conjunction with extended slicing syntax for user-defined
     container data types.

 -- Data: __debug__

     This constant is true if Python was not started with an *note -O:
     690. option.  See also the *note assert: e0b. statement.

     備註: The names *note None: 158, *note False: 38d, *note True: 49e.
     and *note __debug__: 1001. cannot be reassigned (assignments to
     them, even as an attribute name, raise *note SyntaxError: 45d.), so
     they can be considered "true" constants.

* Menu:

* Constants added by the site module::


File: python.info,  Node: Constants added by the site module,  Up: 內建常數

5.3.1 Constants added by the ‘site’ module
------------------------------------------

The *note site: ec. module (which is imported automatically during
startup, except if the *note -S: b29. command-line option is given) adds
several constants to the built-in namespace.  They are useful for the
interactive interpreter shell and should not be used in programs.

 -- Data: quit (code=None)
 -- Data: exit (code=None)

     Objects that when printed, print a message like "Use quit() or
     Ctrl-D (i.e.  EOF) to exit", and when called, raise *note
     SystemExit: 601. with the specified exit code.

 -- Data: copyright
 -- Data: credits

     Objects that when printed or called, print the text of copyright or
     credits, respectively.

 -- Data: license

     Object that when printed, prints the message "Type license() to see
     the full license text", and when called, displays the full license
     text in a pager-like fashion (one screen at a time).


File: python.info,  Node: 內建型態,  Next: 內建的例外,  Prev: 內建常數,  Up: Python 標準函式庫 Standard Library

5.4 內建型態
============

The following sections describe the standard types that are built into
the interpreter.

The principal built-in types are numerics, sequences, mappings, classes,
instances and exceptions.

Some collection classes are mutable.  The methods that add, subtract, or
rearrange their members in place, and don’t return a specific item,
never return the collection instance itself but ‘None’.

Some operations are supported by several object types; in particular,
practically all objects can be compared for equality, tested for truth
value, and converted to a string (with the *note repr(): 7d1. function
or the slightly different *note str(): 335. function).  The latter
function is implicitly used when an object is written by the *note
print(): 88b. function.

* Menu:

* Truth Value Testing::
* Boolean Operations: Boolean Operations --- and or not. and, or, not
* Comparisons: Comparisons<2>.
* Numeric Types: Numeric Types --- int float complex. int, float, complex
* Iterator Types::
* 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
* Context Manager Types::
* Other Built-in Types::
* Special Attributes::


File: python.info,  Node: Truth Value Testing,  Next: Boolean Operations --- and or not,  Up: 內建型態

5.4.1 Truth Value Testing
-------------------------

Any object can be tested for truth value, for use in an *note if: dec.
or *note while: 1232. condition or as operand of the Boolean operations
below.

By default, an object is considered true unless its class defines either
a *note __bool__(): c6d. method that returns ‘False’ or a *note
__len__(): dd0. method that returns zero, when called with the object.
(1) Here are most of the built-in objects considered false:

   * constants defined to be false: ‘None’ and ‘False’.

   * zero of any numeric type: ‘0’, ‘0.0’, ‘0j’, ‘Decimal(0)’,
     ‘Fraction(0, 1)’

   * empty sequences and collections: ‘''’, ‘()’, ‘[]’, ‘{}’, ‘set()’,
     ‘range(0)’

Operations and built-in functions that have a Boolean result always
return ‘0’ or ‘False’ for false and ‘1’ or ‘True’ for true, unless
otherwise stated.  (Important exception: the Boolean operations ‘or’ and
‘and’ always return one of their operands.)

   ---------- Footnotes ----------

   (1) (1) Additional information on these special methods may be found
in the Python Reference Manual (*note Basic customization: 143a.).


File: python.info,  Node: Boolean Operations --- and or not,  Next: Comparisons<2>,  Prev: Truth Value Testing,  Up: 內建型態

5.4.2 Boolean Operations — ‘and’, ‘or’, ‘not’
---------------------------------------------

These are the Boolean operations, ordered by ascending priority:

Operation         Result                                註解
                                                        
--------------------------------------------------------------------
                                                        
‘x or y’          if `x' is false, then `y', else `x'   (1)
                                                        
                                                        
‘x and y’         if `x' is false, then `x', else `y'   (2)
                                                        
                                                        
‘not x’           if `x' is false, then ‘True’, else    (3)
                  ‘False’                               
                  

註解：

  1. This is a short-circuit operator, so it only evaluates the second
     argument if the first one is false.

  2. This is a short-circuit operator, so it only evaluates the second
     argument if the first one is true.

  3. ‘not’ has a lower priority than non-Boolean operators, so ‘not a ==
     b’ is interpreted as ‘not (a == b)’, and ‘a == not b’ is a syntax
     error.


File: python.info,  Node: Comparisons<2>,  Next: Numeric Types --- int float complex,  Prev: Boolean Operations --- and or not,  Up: 內建型態

5.4.3 Comparisons
-----------------

There are eight comparison operations in Python.  They all have the same
priority (which is higher than that of the Boolean operations).
Comparisons can be chained arbitrarily; for example, ‘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).

This table summarizes the comparison operations:

Operation        Meaning
                 
-----------------------------------------------
                 
‘<’              strictly less than
                 
                 
‘<=’             less than or equal
                 
                 
‘>’              strictly greater than
                 
                 
‘>=’             greater than or equal
                 
                 
‘==’             equal
                 
                 
‘!=’             not equal
                 
                 
‘is’             object identity
                 
                 
‘is not’         negated object identity
                 

Objects of different types, except different numeric types, never
compare equal.  The ‘==’ operator is always defined but for some object
types (for example, class objects) is equivalent to *note is: ebf.  The
‘<’, ‘<=’, ‘>’ and ‘>=’ operators are only defined where they make
sense; for example, they raise a *note TypeError: 193. exception when
one of the arguments is a complex number.

Non-identical instances of a class normally compare as non-equal unless
the class defines the *note __eq__(): 344. method.

Instances of a class cannot be ordered with respect to other instances
of the same class, or other types of object, unless the class defines
enough of the methods *note __lt__(): c39, *note __le__(): ca5, *note
__gt__(): ca6, and *note __ge__(): ca7. (in general, *note __lt__():
c39. and *note __eq__(): 344. are sufficient, if you want the
conventional meanings of the comparison operators).

The behavior of the *note is: ebf. and *note is not: 154d. operators
cannot be customized; also they can be applied to any two objects and
never raise an exception.

Two more operations with the same syntactic priority, *note in: 7a8. and
*note not in: 1462, are supported by types that are *note iterable: bb1.
or implement the *note __contains__(): d2d. method.


File: python.info,  Node: Numeric Types --- int float complex,  Next: Iterator Types,  Prev: Comparisons<2>,  Up: 內建型態

5.4.4 Numeric Types — ‘int’, ‘float’, ‘complex’
-----------------------------------------------

There are three distinct numeric types: `integers', `floating point
numbers', and `complex numbers'.  In addition, Booleans are a subtype of
integers.  Integers have unlimited precision.  Floating point numbers
are usually implemented using ‘double’ in C; information about the
precision and internal representation of floating point numbers for the
machine on which your program is running is available in *note
sys.float_info: fc6.  Complex numbers have a real and imaginary part,
which are each a floating point number.  To extract these parts from a
complex number `z', use ‘z.real’ and ‘z.imag’.  (The standard library
includes the additional numeric types *note fractions.Fraction: 186, for
rationals, and *note decimal.Decimal: 189, for floating-point numbers
with user-definable precision.)

Numbers are created by numeric literals or as the result of built-in
functions and operators.  Unadorned integer literals (including hex,
octal and binary numbers) yield integers.  Numeric literals containing a
decimal point or an exponent sign yield floating point numbers.
Appending ‘'j'’ or ‘'J'’ to a numeric literal yields an imaginary number
(a complex number with a zero real part) which you can add to an integer
or float to get a complex number with real and imaginary parts.

Python fully supports mixed arithmetic: when a binary arithmetic
operator has operands of different numeric types, the operand with the
"narrower" type is widened to that of the other, where integer is
narrower than floating point, which is narrower than complex.  A
comparison between numbers of different types behaves as though the
exact values of those numbers were being compared.  (1)

The constructors *note int(): 185, *note float(): 188, and *note
complex(): 18a. can be used to produce numbers of a specific type.

All numeric types (except complex) support the following operations (for
priorities of the operations, see *note Operator precedence: 1568.):

Operation                 Result                                註解          Full documentation
                                                                              
-------------------------------------------------------------------------------------------------------
                                                                              
‘x + y’                   sum of `x' and `y'
                          
                                                                              
‘x - y’                   difference of `x' and `y'
                          
                                                                              
‘x * y’                   product of `x' and `y'
                          
                                                                              
‘x / y’                   quotient of `x' and `y'
                          
                                                                              
‘x // y’                  floored quotient of `x' and `y'       (1)
                                                                
                                                                              
‘x % y’                   remainder of ‘x / y’                  (2)
                                                                
                                                                              
‘-x’                      `x' negated
                          
                                                                              
‘+x’                      `x' unchanged
                          
                                                                              
‘abs(x)’                  absolute value or magnitude of `x'                  *note abs(): 12c4.
                                                                              
                                                                              
‘int(x)’                  `x' converted to integer              (3)(6)        *note int(): 185.
                                                                              
                                                                              
‘float(x)’                `x' converted to floating point       (4)(6)        *note float(): 188.
                                                                              
                                                                              
‘complex(re, im)’         a complex number with real part       (6)           *note complex(): 18a.
                          `re', imaginary part `im'.  `im'                    
                          defaults to zero.
                          
                                                                              
‘c.conjugate()’           conjugate of the complex number `c'
                          
                                                                              
‘divmod(x, y)’            the pair ‘(x // y, x % y)’            (2)           *note divmod(): 153.
                                                                              
                                                                              
‘pow(x, y)’               `x' to the power `y'                  (5)           *note pow(): 19b.
                                                                              
                                                                              
‘x ** y’                  `x' to the power `y'                  (5)
                                                                

註解：

  1. Also referred to as integer division.  The resultant value is a
     whole integer, though the result’s type is not necessarily int.
     The result is always rounded towards minus infinity: ‘1//2’ is ‘0’,
     ‘(-1)//2’ is ‘-1’, ‘1//(-2)’ is ‘-1’, and ‘(-1)//(-2)’ is ‘0’.

  2. Not for complex numbers.  Instead convert to floats using *note
     abs(): 12c4. if appropriate.

  3. 
     Conversion from floating point to integer may round or truncate as
     in C; see functions *note math.floor(): d31. and *note math.ceil():
     d32. for well-defined conversions.

  4. float also accepts the strings "nan" and "inf" with an optional
     prefix "+" or "-" for Not a Number (NaN) and positive or negative
     infinity.

  5. Python defines ‘pow(0, 0)’ and ‘0 ** 0’ to be ‘1’, as is common for
     programming languages.

  6. The numeric literals accepted include the digits ‘0’ to ‘9’ or any
     Unicode equivalent (code points with the ‘Nd’ property).

     See
     ‘http://www.unicode.org/Public/12.1.0/ucd/extracted/DerivedNumericType.txt’
     for a complete list of code points with the ‘Nd’ property.

All *note numbers.Real: 142a. types (*note int: 185. and *note float:
188.) also include the following operations:

Operation                Result
                         
---------------------------------------------------------------------------
                         
*note math.trunc(x): d33.`x' truncated to *note Integral: 1429.
                         
                         
*note round(x[, n]): c72.`x' rounded to `n' digits, rounding half to
                         even.  If `n' is omitted, it defaults to 0.
                         
                         
*note math.floor(x): d31.the greatest *note Integral: 1429. <= `x'
                         
                         
*note math.ceil(x): d32. the least *note Integral: 1429. >= `x'
                         

For additional numeric operations see the *note math: b2. and *note
cmath: 19. modules.

* Menu:

* Bitwise Operations on Integer Types::
* Additional Methods on Integer Types::
* Additional Methods on Float::
* Hashing of numeric types::

   ---------- Footnotes ----------

   (1) (2) As a consequence, the list ‘[1, 2]’ is considered equal to
‘[1.0, 2.0]’, and similarly for tuples.


File: python.info,  Node: Bitwise Operations on Integer Types,  Next: Additional Methods on Integer Types,  Up: Numeric Types --- int float complex

5.4.4.1 Bitwise Operations on Integer Types
...........................................

Bitwise operations only make sense for integers.  The result of bitwise
operations is calculated as though carried out in two’s complement with
an infinite number of sign bits.

The priorities of the binary bitwise operations are all lower than the
numeric operations and higher than the comparisons; the unary operation
‘~’ has the same priority as the other unary numeric operations (‘+’ and
‘-’).

This table lists the bitwise operations sorted in ascending priority:

Operation        Result                               註解
                                                      
---------------------------------------------------------------------
                                                      
‘x | y’          bitwise `or' of `x' and `y'          (4)
                                                      
                                                      
‘x ^ y’          bitwise `exclusive or' of `x' and    (4)
                 `y'                                  
                 
                                                      
‘x & y’          bitwise `and' of `x' and `y'         (4)
                                                      
                                                      
‘x << n’         `x' shifted left by `n' bits         (1)(2)
                                                      
                                                      
‘x >> n’         `x' shifted right by `n' bits        (1)(3)
                                                      
                                                      
‘~x’             the bits of `x' inverted
                 

註解：

  1. Negative shift counts are illegal and cause a *note ValueError:
     1fc. to be raised.

  2. A left shift by `n' bits is equivalent to multiplication by ‘pow(2,
     n)’.

  3. A right shift by `n' bits is equivalent to floor division by
     ‘pow(2, n)’.

  4. Performing these calculations with at least one extra sign
     extension bit in a finite two’s complement representation (a
     working bit-width of ‘1 + max(x.bit_length(), y.bit_length())’ or
     more) is sufficient to get the same result as if there were an
     infinite number of sign bits.


File: python.info,  Node: Additional Methods on Integer Types,  Next: Additional Methods on Float,  Prev: Bitwise Operations on Integer Types,  Up: Numeric Types --- int float complex

5.4.4.2 Additional Methods on Integer Types
...........................................

The int type implements the *note numbers.Integral: 1429. *note abstract
base class: b38.  In addition, it provides a few more methods:

 -- 成員函式: int.bit_length ()

     Return the number of bits necessary to represent an integer in
     binary, excluding the sign and leading zeros:

          >>> n = -37
          >>> bin(n)
          '-0b100101'
          >>> n.bit_length()
          6

     More precisely, if ‘x’ is nonzero, then ‘x.bit_length()’ is the
     unique positive integer ‘k’ such that ‘2**(k-1) <= abs(x) < 2**k’.
     Equivalently, when ‘abs(x)’ is small enough to have a correctly
     rounded logarithm, then ‘k = 1 + int(log(abs(x), 2))’.  If ‘x’ is
     zero, then ‘x.bit_length()’ returns ‘0’.

     Equivalent to:

          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.to_bytes (length, byteorder, *, signed=False)

     Return an array of bytes representing an integer.

          >>> (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'

     The integer is represented using `length' bytes.  An *note
     OverflowError: 965. is raised if the integer is not representable
     with the given number of bytes.

     The `byteorder' argument determines the byte order used to
     represent the integer.  If `byteorder' is ‘"big"’, the most
     significant byte is at the beginning of the byte array.  If
     `byteorder' is ‘"little"’, the most significant byte is at the end
     of the byte array.  To request the native byte order of the host
     system, use *note sys.byteorder: 1626. as the byte order value.

     The `signed' argument determines whether two’s complement is used
     to represent the integer.  If `signed' is ‘False’ and a negative
     integer is given, an *note OverflowError: 965. is raised.  The
     default value for `signed' is ‘False’.

     3.2 版新加入.

 -- 成員函式: classmethod int.from_bytes (bytes, byteorder, *,
          signed=False)

     Return the integer represented by the given array of bytes.

          >>> 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

     The argument `bytes' must either be a *note bytes-like object: 5ed.
     or an iterable producing bytes.

     The `byteorder' argument determines the byte order used to
     represent the integer.  If `byteorder' is ‘"big"’, the most
     significant byte is at the beginning of the byte array.  If
     `byteorder' is ‘"little"’, the most significant byte is at the end
     of the byte array.  To request the native byte order of the host
     system, use *note sys.byteorder: 1626. as the byte order value.

     The `signed' argument indicates whether two’s complement is used to
     represent the integer.

     3.2 版新加入.

 -- 成員函式: int.as_integer_ratio ()

     Return a pair of integers whose ratio is exactly equal to the
     original integer and with a positive denominator.  The integer
     ratio of integers (whole numbers) is always the integer as the
     numerator and ‘1’ as the denominator.

     3.8 版新加入.


File: python.info,  Node: Additional Methods on Float,  Next: Hashing of numeric types,  Prev: Additional Methods on Integer Types,  Up: Numeric Types --- int float complex

5.4.4.3 Additional Methods on Float
...................................

The float type implements the *note numbers.Real: 142a. *note abstract
base class: b38.  float also has the following additional methods.

 -- 成員函式: float.as_integer_ratio ()

     Return a pair of integers whose ratio is exactly equal to the
     original float and with a positive denominator.  Raises *note
     OverflowError: 965. on infinities and a *note ValueError: 1fc. on
     NaNs.

 -- 成員函式: float.is_integer ()

     Return ‘True’ if the float instance is finite with integral value,
     and ‘False’ otherwise:

          >>> (-2.0).is_integer()
          True
          >>> (3.2).is_integer()
          False

Two methods support conversion to and from hexadecimal strings.  Since
Python’s floats are stored internally as binary numbers, converting a
float to or from a `decimal' string usually involves a small rounding
error.  In contrast, hexadecimal strings allow exact representation and
specification of floating-point numbers.  This can be useful when
debugging, and in numerical work.

 -- 成員函式: float.hex ()

     Return a representation of a floating-point number as a hexadecimal
     string.  For finite floating-point numbers, this representation
     will always include a leading ‘0x’ and a trailing ‘p’ and exponent.

 -- 成員函式: classmethod float.fromhex (s)

     Class method to return the float represented by a hexadecimal
     string `s'.  The string `s' may have leading and trailing
     whitespace.

Note that *note float.hex(): 1329. is an instance method, while *note
float.fromhex(): 162a. is a class method.

A hexadecimal string takes the form:

     [sign] ['0x'] integer ['.' fraction] ['p' exponent]

where the optional ‘sign’ may by either ‘+’ or ‘-’, ‘integer’ and
‘fraction’ are strings of hexadecimal digits, and ‘exponent’ is a
decimal integer with an optional leading sign.  Case is not significant,
and there must be at least one hexadecimal digit in either the integer
or the fraction.  This syntax is similar to the syntax specified in
section 6.4.4.2 of the C99 standard, and also to the syntax used in Java
1.5 onwards.  In particular, the output of *note float.hex(): 1329. is
usable as a hexadecimal floating-point literal in C or Java code, and
hexadecimal strings produced by C’s ‘%a’ format character or Java’s
‘Double.toHexString’ are accepted by *note float.fromhex(): 162a.

Note that the exponent is written in decimal rather than hexadecimal,
and that it gives the power of 2 by which to multiply the coefficient.
For example, the hexadecimal string ‘0x3.a7p10’ represents the
floating-point number ‘(3 + 10./16 + 7./16**2) * 2.0**10’, or ‘3740.0’:

     >>> float.fromhex('0x3.a7p10')
     3740.0

Applying the reverse conversion to ‘3740.0’ gives a different
hexadecimal string representing the same number:

     >>> float.hex(3740.0)
     '0x1.d380000000000p+11'


File: python.info,  Node: Hashing of numeric types,  Prev: Additional Methods on Float,  Up: Numeric Types --- int float complex

5.4.4.4 Hashing of numeric types
................................

For numbers ‘x’ and ‘y’, possibly of different types, it’s a requirement
that ‘hash(x) == hash(y)’ whenever ‘x == y’ (see the *note __hash__():
345. method documentation for more details).  For ease of implementation
and efficiency across a variety of numeric types (including *note int:
185, *note float: 188, *note decimal.Decimal: 189. and *note
fractions.Fraction: 186.) Python’s hash for numeric types is based on a
single mathematical function that’s defined for any rational number, and
hence applies to all instances of *note int: 185. and *note
fractions.Fraction: 186, and all finite instances of *note float: 188.
and *note decimal.Decimal: 189.  Essentially, this function is given by
reduction modulo ‘P’ for a fixed prime ‘P’.  The value of ‘P’ is made
available to Python as the ‘modulus’ attribute of *note sys.hash_info:
926.

`CPython implementation detail:' Currently, the prime used is ‘P = 2**31
- 1’ on machines with 32-bit C longs and ‘P = 2**61 - 1’ on machines
with 64-bit C longs.

Here are the rules in detail:

   - If ‘x = m / n’ is a nonnegative rational number and ‘n’ is not
     divisible by ‘P’, define ‘hash(x)’ as ‘m * invmod(n, P) % P’, where
     ‘invmod(n, P)’ gives the inverse of ‘n’ modulo ‘P’.

   - If ‘x = m / n’ is a nonnegative rational number and ‘n’ is
     divisible by ‘P’ (but ‘m’ is not) then ‘n’ has no inverse modulo
     ‘P’ and the rule above doesn’t apply; in this case define ‘hash(x)’
     to be the constant value ‘sys.hash_info.inf’.

   - If ‘x = m / n’ is a negative rational number define ‘hash(x)’ as
     ‘-hash(-x)’.  If the resulting hash is ‘-1’, replace it with ‘-2’.

   - The particular values ‘sys.hash_info.inf’, ‘-sys.hash_info.inf’ and
     ‘sys.hash_info.nan’ are used as hash values for positive infinity,
     negative infinity, or nans (respectively).  (All hashable nans have
     the same hash value.)

   - For a *note complex: 18a. number ‘z’, the hash values of the real
     and imaginary parts are combined by computing ‘hash(z.real) +
     sys.hash_info.imag * hash(z.imag)’, reduced modulo
     ‘2**sys.hash_info.width’ so that it lies in
     ‘range(-2**(sys.hash_info.width - 1), 2**(sys.hash_info.width -
     1))’.  Again, if the result is ‘-1’, it’s replaced with ‘-2’.

To clarify the above rules, here’s some example Python code, equivalent
to the built-in hash, for computing the hash of a rational number, *note
float: 188, or *note complex: 18a.:

     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 sys.hash_info.nan
         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: Iterator Types,  Next: Sequence Types --- list tuple range,  Prev: Numeric Types --- int float complex,  Up: 內建型態

5.4.5 Iterator Types
--------------------

Python supports a concept of iteration over containers.  This is
implemented using two distinct methods; these are used to allow
user-defined classes to support iteration.  Sequences, described below
in more detail, always support the iteration methods.

One method needs to be defined for container objects to provide
iteration support:

 -- 成員函式: container.__iter__ ()

     Return an iterator object.  The object is required to support the
     iterator protocol described below.  If a container supports
     different types of iteration, additional methods can be provided to
     specifically request iterators for those iteration types.  (An
     example of an object supporting multiple forms of iteration would
     be a tree structure which supports both breadth-first and
     depth-first traversal.)  This method corresponds to the *note
     tp_iter: e35. slot of the type structure for Python objects in the
     Python/C API.

The iterator objects themselves are required to support the following
two methods, which together form the `iterator protocol':

 -- 成員函式: iterator.__iter__ ()

     Return the iterator object itself.  This is required to allow both
     containers and iterators to be used with the *note for: c35. and
     *note in: 7a8. statements.  This method corresponds to the *note
     tp_iter: e35. slot of the type structure for Python objects in the
     Python/C API.

 -- 成員函式: iterator.__next__ ()

     Return the next item from the container.  If there are no further
     items, raise the *note StopIteration: 48b. exception.  This method
     corresponds to the *note tp_iternext: e36. slot of the type
     structure for Python objects in the Python/C API.

Python defines several iterator objects to support iteration over
general and specific sequence types, dictionaries, and other more
specialized forms.  The specific types are not important beyond their
implementation of the iterator protocol.

Once an iterator’s *note __next__(): c69. method raises *note
StopIteration: 48b, it must continue to do so on subsequent calls.
Implementations that do not obey this property are deemed broken.

* Menu:

* Generator Types::


File: python.info,  Node: Generator Types,  Up: Iterator Types

5.4.5.1 Generator Types
.......................

Python’s *note generator: 9a7.s provide a convenient way to implement
the iterator protocol.  If a container object’s *note __iter__(): 514.
method is implemented as a generator, it will automatically return an
iterator object (technically, a generator object) supplying the *note
__iter__(): 514. and *note __next__(): 12df. methods.  More information
about generators can be found in *note the documentation for the yield
expression: 1505.


File: python.info,  Node: Sequence Types --- list tuple range,  Next: Text Sequence Type --- str,  Prev: Iterator Types,  Up: 內建型態

5.4.6 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:
15ed. and *note text strings: 1228. 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.6.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:
1635. 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)

Operation                      Result                               註解
                                                                    
-----------------------------------------------------------------------------------
                                                                    
‘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’ or ‘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)’                       length of `s'
                               
                                                                    
‘min(s)’                       smallest item of `s'
                               
                                                                    
‘max(s)’                       largest item of `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: 1546. in
the language reference.)

註解：

  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: 335, *note bytes: 336. and *note bytearray:
     337.) 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?: 1636.

  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: 335. objects, you can build a list
          and use *note str.join(): 1637. at the end or else write to an
          *note io.StringIO: 832. instance and retrieve its value when
          complete

        * if concatenating *note bytes: 336. objects, you can similarly
          use *note bytes.join(): 1638. or *note io.BytesIO: 7a0, or you
          can do in-place concatenation with a *note bytearray: 337.
          object.  *note bytearray: 337. objects are mutable and have an
          efficient overallocation mechanism

        * if concatenating *note tuple: 483. objects, extend a *note
          list: 263. instead

        * for other types, investigate the relevant class documentation

  7. Some sequence types (such as *note range: 9c3.) only support item
     sequences that follow specific patterns, and hence don’t support
     sequence concatenation or repetition.

  8. ‘index’ raises *note ValueError: 1fc. 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) (3) 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.6.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(): 9c9. built-in.

This support allows immutable sequences, such as *note tuple: 483.
instances, to be used as *note dict: 1b9. keys and stored in *note set:
b74. and *note frozenset: bf3. instances.

Attempting to hash an immutable sequence that contains unhashable values
will result in *note TypeError: 193.


File: python.info,  Node: Mutable Sequence Types,  Next: List（串列）<2>,  Prev: Immutable Sequence Types,  Up: Sequence Types --- list tuple range

5.4.6.3 Mutable Sequence Types
..............................

The operations in the following table are defined on mutable sequence
types.  The *note collections.abc.MutableSequence: 6b1. 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: 337.
only accepts integers that meet the value restriction ‘0 <= x <= 255’).

Operation                          Result                               註解
                                                                        
--------------------------------------------------------------------------------------------------
                                                                        
‘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)’ or ‘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([i])’                       retrieves the item at `i' and also   (2)
                                   removes it from `s'                  
                                   
                                                                        
‘s.remove(x)’                      remove the first item from `s'       (3)
                                   where ‘s[i]’ is equal to `x'         
                                   
                                                                        
‘s.reverse()’                      reverses the items of `s' in place   (4)
                                                                        

註解：

  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: 1fc. 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: 1b9. and *note set: b74.).
     ‘copy()’ is not part of the *note collections.abc.MutableSequence:
     6b1. 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__(): 18b.  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: 1634.


File: python.info,  Node: List（串列）<2>,  Next: Tuples,  Prev: Mutable Sequence Types,  Up: Sequence Types --- list tuple range

5.4.6.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(): 449. built-in.

     Lists implement all of the *note common: 1634. and *note mutable:
     15ea. 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(): 44a. accepts two arguments that can only be
          passed by keyword (*note keyword-only arguments: 2ad.):

          `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(): b5b. 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(): 449. to explicitly request a new
          sorted list instance).

          The *note sort(): 44a. 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
          如何排序: 1606.

          `CPython implementation detail:' 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:
          1fc. 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.6.5 Tuples
..............

Tuples are immutable sequences, typically used to store collections of
heterogeneous data (such as the 2-tuples produced by the *note
enumerate(): de8. 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: b74. or *note dict: 1b9. 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(): 483. 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: 1634. sequence
     operations.

For heterogeneous collections of data where access by name is clearer
than access by index, *note collections.namedtuple(): 1b8. 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.6.6 Ranges
..............

The *note range: 9c3. type represents an immutable sequence of numbers
and is commonly used for looping a specific number of times in *note
for: c35. loops.

 -- 類別: range (stop)

 -- 類別: range (start, stop[, step])

     The arguments to the range constructor must be integers (either
     built-in *note int: 185. or any object that implements the
     ‘__index__’ 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: 1fc. 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:
     b48. are permitted but some features (such as *note len(): 151.)
     may raise *note OverflowError: 965.

     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: 1634. 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: 9c3. type over a regular *note list:
263. or *note tuple: 483. is that a *note range: 9c3. 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: 1635. ABC,
and provide features such as containment tests, element index lookup,
slicing and support for negative indices (see *note Sequence Types —
list, tuple, range: 1275.):

     >>> 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: 163f, *note stop:
1640. and *note step: 1641. 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: 185. 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).

3.3 版新加入: The *note start: 163f, *note stop: 1640. and *note step:
1641. attributes.

也參考
......

   * The linspace recipe(1) shows how to implement a lazy version of
     range suitable for floating point applications.

   ---------- Footnotes ----------

   (1) http://code.activestate.com/recipes/579000/


File: python.info,  Node: Text Sequence Type --- str,  Next: Binary Sequence Types --- bytes bytearray memoryview,  Prev: Sequence Types --- list tuple range,  Up: 內建型態

5.4.7 Text Sequence Type — ‘str’
--------------------------------

Textual data in Python is handled with *note str: 335. objects, or
`strings'.  Strings are immutable *note sequences: 1275. 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: 13e8. for more about the various
forms of string literal, including supported escape sequences, and the
‘r’ ("raw") prefix that disables most escape sequence processing.

Strings may also be created from other objects using the *note str: 335.
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(): 1637. or
*note io.StringIO: 832. 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: 1228. 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 object.__str__(): e3c, 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__(): e3c. method, then *note str(): 335. falls back to
     returning *note repr(object): 7d1.

     If at least one of `encoding' or `errors' is given, `object' should
     be a *note bytes-like object: 5ed. (e.g.  *note bytes: 336. or
     *note bytearray: 337.).  In this case, if `object' is a *note
     bytes: 336. (or *note bytearray: 337.) object, then ‘str(bytes,
     encoding, errors)’ is equivalent to *note bytes.decode(encoding,
     errors): c3d.  Otherwise, the bytes object underlying the buffer
     object is obtained before calling *note bytes.decode(): c3d.  See
     *note Binary Sequence Types — bytes, bytearray, memoryview: 15ed.
     and *note Buffer Protocol: 15ec. for information on buffer objects.

     Passing a *note bytes: 336. object to *note str(): 335. without the
     `encoding' or `errors' arguments falls under the first case of
     returning the informal string representation (see also the *note
     -b: 41a. 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: 1228. and the *note String Methods: 1229.
     section below.  To output formatted strings, see the *note
     Formatted string literals: 15d. and *note Format String Syntax:
     d1f. sections.  In addition, see the *note Text Processing
     Services: 1643. 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.7.1 String Methods
......................

Strings implement all of the *note common: 1634. 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():
4df, *note Format String Syntax: d1f. and *note Custom String
Formatting: 1645.) 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: 122a.).

The *note Text Processing Services: 1646. 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:
de. 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(): 1648. would do
     nothing to ‘'ß'’; *note casefold(): 6b5. converts it to ‘"ss"’.

     The casefolding algorithm is described in section 3.13 of the
     Unicode Standard.

     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.

 -- 成員函式: str.encode (encoding="utf-8", errors="strict")

     Return an encoded version of the string as a bytes object.  Default
     encoding is ‘'utf-8'’.  `errors' may be given to set a different
     error handling scheme.  The default for `errors' is ‘'strict'’,
     meaning that encoding errors raise a *note UnicodeError: c40.
     Other possible values are ‘'ignore'’, ‘'replace'’,
     ‘'xmlcharrefreplace'’, ‘'backslashreplace'’ and any other name
     registered via *note codecs.register_error(): dfa, see section
     *note Error Handlers: 1366.  For a list of possible encodings, see
     section *note Standard Encodings: 694.

     3.1 版更變: Support for keyword arguments added.

 -- 成員函式: 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(): 7a4. 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: 7a8. 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 Format String Syntax: d1f. for a description of the
     various formatting options that can be specified in format strings.

          備註: When formatting a number (*note int: 185, *note float:
          188, *note complex: 18a, *note decimal.Decimal: 189. 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: 1b9.  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(): 7a4, but raise *note ValueError: 1fc. 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 Unicode
     Standard.

 -- 成員函式: 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: 13d9.

     Call *note keyword.iskeyword(): 1651. to test whether string ‘s’ is
     a reserved identifier, such as *note def: dc3. and *note class:
     c6f.

     Example:

          >>> from keyword import iskeyword

          >>> 'hello'.isidentifier(), iskeyword('hello')
          True, False
          >>> 'def'.isidentifier(), iskeyword('def')
          True, True

 -- 成員函式: str.islower ()

     Return ‘True’ if all cased characters (1) 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():
     7d1. is invoked on a string.  It has no bearing on the handling of
     strings written to *note sys.stdout: 313. or *note sys.stderr:
     314.)

 -- 成員函式: 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: 11b.), 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 (2) in the string are
     uppercase and there is at least one cased character, ‘False’
     otherwise.

 -- 成員函式: str.join (iterable)

     Return a string which is the concatenation of the strings in
     `iterable'.  A *note TypeError: 193. will be raised if there are
     any non-string values in `iterable', including *note bytes: 336.
     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 (3)
     converted to lowercase.

     The lowercasing algorithm used is described in section 3.13 of the
     Unicode Standard.

 -- 成員函式: 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'

 -- 成員函式: static str.maketrans (x[, y[, z]])

     This static method returns a translation table usable for *note
     str.translate(): 1658.

     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.replace (old, new[, count])

     Return a copy of the string with all occurrences of substring `old'
     replaced by `new'.  If the optional argument `count' is given, only
     the first `count' occurrences are replaced.

 -- 成員函式: 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(): 7a5. but raises *note ValueError: 1fc. 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(): 165c. behaves like *note
     split(): 7a6. 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'

 -- 成員函式: 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 (for example,
     ‘'1<>2<>3'.split('<>')’ returns ‘['1', '2', '3']’).  Splitting an
     empty string with a specified separator returns ‘['']’.

     For example:

          >>> '1,2,3'.split(',')
          ['1', '2', '3']
          >>> '1,2,3'.split(',', maxsplit=1)
          ['1', '2,3']
          >>> '1,2,,3,'.split(',')
          ['1', '2', '', '3', '']

     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 ‘[]’.

     For example:

          >>> '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])

     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: 5f9.

     Representation              描述
                                 
     --------------------------------------------------------------
                                 
     ‘\n’                        Line Feed
                                 
                                 
     ‘\r’                        Carriage Return
                                 
                                 
     ‘\r\n’                      Carriage Return + Line Feed
                                 
                                 
     ‘\v’ or ‘\x0b’              Line Tabulation
                                 
                                 
     ‘\f’ or ‘\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.

     For example:

          >>> '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(): 7a6. 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.

     For example:

          >>> '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"

     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__(): 27d, typically a
     *note mapping: b3e. or *note sequence: 122d.  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:
     1662. exception, to map the character to itself.

     You can use *note str.maketrans(): 6b8. to create a translation map
     from character-to-character mappings in different formats.

     See also the *note codecs: 1c. module for a more flexible approach
     to custom character mappings.

 -- 成員函式: str.upper ()

     Return a copy of the string with all the cased characters (4)
     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 of the
     Unicode Standard.

 -- 成員函式: 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)’.

     For example:

          >>> "42".zfill(5)
          '00042'
          >>> "-42".zfill(5)
          '-0042'

   ---------- Footnotes ----------

   (1) (4) Cased characters are those with general category property
being one of "Lu" (Letter, uppercase), "Ll" (Letter, lowercase), or "Lt"
(Letter, titlecase).

   (2) (4) Cased characters are those with general category property
being one of "Lu" (Letter, uppercase), "Ll" (Letter, lowercase), or "Lt"
(Letter, titlecase).

   (3) (4) Cased characters are those with general category property
being one of "Lu" (Letter, uppercase), "Ll" (Letter, lowercase), or "Lt"
(Letter, titlecase).

   (4) (4) Cased characters are those with general category property
being one of "Lu" (Letter, uppercase), "Ll" (Letter, lowercase), or "Lt"
(Letter, titlecase).


File: python.info,  Node: printf-style String Formatting,  Prev: String Methods<2>,  Up: Text Sequence Type --- str

5.4.7.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: 15d, the *note str.format(): 4df.
     interface, or *note template strings: 1665. 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()’ 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 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          Meaning
              
----------------------------------------------------------------------------------------
              
‘'#'’         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       Meaning                                                   註解
                                                                           
---------------------------------------------------------------------------------------
                                                                           
‘'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(): 7d1.).                                      
                 
                                                                           
‘'s'’            String (converts any Python object using                  (5)
                 *note str(): 335.).                                       
                 
                                                                           
‘'a'’            String (converts any Python object using                  (5)
                 *note ascii(): d51.).                                     
                 
                                                                           
‘'%'’            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. See 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) (5) To format only a tuple you should therefore provide a
singleton tuple whose only element is the tuple to be formatted.

   (2) https://www.python.org/dev/peps/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.8 Binary Sequence Types — ‘bytes’, ‘bytearray’, ‘memoryview’
----------------------------------------------------------------

The core built-in types for manipulating binary data are *note bytes:
336. and *note bytearray: 337.  They are supported by *note memoryview:
25d. which uses the *note buffer protocol: 15ec. to access the memory of
other binary objects without needing to make a copy.

The *note array: 7. 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.8.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: 13e8. 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: 1fc.).  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: 10c2. 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: 336. 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(): 333. 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 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(): 636. 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)’.

     備註: For Python 2.x users: In the Python 2.x series, a variety of
     implicit conversions between 8-bit strings (the closest thing 2.x
     offers to a built-in binary data type) and Unicode strings were
     permitted.  This was a backwards compatibility workaround to
     account for the fact that Python originally only supported 8-bit
     text, and Unicode text was a later addition.  In Python 3.x, those
     implicit conversions are gone - conversions between 8-bit binary
     data and Unicode text must be explicit, and bytes and string
     objects will always compare unequal.


File: python.info,  Node: Bytearray Objects,  Next: Bytes and Bytearray Operations,  Prev: Bytes Objects,  Up: Binary Sequence Types --- bytes bytearray memoryview

5.4.8.2 Bytearray Objects
.........................

*note bytearray: 337. objects are a mutable counterpart to *note bytes:
336. 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:
     15ea. sequence operations in addition to the common bytes and
     bytearray operations described in *note Bytes and Bytearray
     Operations: 15eb.

     Also see the *note bytearray: 10c3. 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: 337. 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(): 334. 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(): 636, *note
          bytearray.hex(): 637. 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.8.3 Bytes and Bytearray Operations
......................................

Both bytes and bytearray objects support the *note common: 1634.
sequence operations.  They interoperate not just with operands of the
same type, but with any *note bytes-like object: 5ed.  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")

     and:

          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:
     5ed. 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.decode (encoding="utf-8", errors="strict")
 -- 成員函式: bytearray.decode (encoding="utf-8", errors="strict")

     Return a string decoded from the given bytes.  Default encoding is
     ‘'utf-8'’.  `errors' may be given to set a different error handling
     scheme.  The default for `errors' is ‘'strict'’, meaning that
     encoding errors raise a *note UnicodeError: c40.  Other possible
     values are ‘'ignore'’, ‘'replace'’ and any other name registered
     via *note codecs.register_error(): dfa, see section *note Error
     Handlers: 1366.  For a list of possible encodings, see section
     *note Standard Encodings: 694.

          備註: Passing the `encoding' argument to *note str: 335.
          allows decoding any *note bytes-like object: 5ed. directly,
          without needing to make a temporary bytes or bytearray object.

     3.1 版更變: Added support for keyword arguments.

 -- 成員函式: 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:
     5ed.

 -- 成員函式: 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:
     5ed. or an integer in the range 0 to 255.

          備註: The *note find(): 166f. 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: 7a8. 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(): 166f, but raise *note ValueError: 1fc. when the
     subsequence is not found.

     The subsequence to search for may be any *note bytes-like object:
     5ed. 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: 193.
     will be raised if there are any values in `iterable' that are not
     *note bytes-like objects: 5ed, including *note str: 335. 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(): 1674. 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: 5ed. 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:
     5ed.

 -- 成員函式: 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: 5ed.

          備註: 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:
     5ed. 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(): 1679. but raises *note ValueError: 1fc. when
     the subsequence `sub' is not found.

     The subsequence to search for may be any *note bytes-like object:
     5ed. 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:
     5ed.

 -- 成員函式: 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:
     5ed.

 -- 成員函式: 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(): c0e. 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: 336. 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: 336. 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: 5ed.

          備註: 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: 336. 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(): 168a. behaves like *note split(): 168b. 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: 5ed.

          備註: 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 (for example,
     ‘b'1<>2<>3'.split(b'<>')’ returns ‘[b'1', b'2', b'3']’).  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: 5ed.

     For example:

          >>> 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'']

     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 ‘[]’.

     For example:

          >>> 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: 5ed.

          備註: 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'’.

     For example:

          >>> 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'’.

     For example:

          >>> 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'’.

     For example:

          >>> 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.

     For example:

          >>> 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(): 16a3.
     for more details on the definition of "titlecase".

     For example:

          >>> 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.

     For example:

          >>> 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.

     For example:

          >>> 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: 5f9. approach to splitting lines.  Line breaks are not
     included in the resulting list unless `keepends' is given and true.

     For example:

          >>> 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(): 168e. 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.

     For example:

          >>> 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(): 1660, 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.

     For example:

          >>> 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.

     For example:

          >>> 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: 336. objects,
     the original sequence is returned if `width' is less than or equal
     to ‘len(seq)’.

     For example:

          >>> 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.8.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          Meaning
              
----------------------------------------------------------------------------------------
              
‘'#'’         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       Meaning                                                   註解
                                                                           
---------------------------------------------------------------------------------------
                                                                           
‘'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: 15ec. or has                       
                 *note __bytes__(): 143c.).
                 
                                                                           
‘'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. See 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) (5) To format only a tuple you should therefore provide a
singleton tuple whose only element is the tuple to be formatted.

   (2) https://www.python.org/dev/peps/pep-0237

   (3) https://www.python.org/dev/peps/pep-0461


File: python.info,  Node: Memory Views,  Prev: printf-style Bytes Formatting,  Up: Binary Sequence Types --- bytes bytearray memoryview

5.4.8.5 Memory Views
....................

*note memoryview: 25d. objects allow Python code to access the internal
data of an object that supports the *note buffer protocol: 15ec. without
copying.

 -- 類別: memoryview (obj)

     Create a *note memoryview: 25d. that references `obj'.  `obj' must
     support the buffer protocol.  Built-in objects that support the
     buffer protocol include *note bytes: 336. and *note bytearray: 337.

     A *note memoryview: 25d. has the notion of an `element', which is
     the atomic memory unit handled by the originating object `obj'.
     For many simple types such as *note bytes: 336. and *note
     bytearray: 337, an element is a single byte, but other types such
     as *note array.array: 456. may have bigger elements.

     ‘len(view)’ is equal to the length of *note tolist: 16b3.  If
     ‘view.ndim = 0’, the length is 1.  If ‘view.ndim = 1’, the length
     is equal to the number of elements in the view.  For higher
     dimensions, the length is equal to the length of the nested list
     representation of the view.  The *note itemsize: 16b4. attribute
     will give you the number of bytes in a single element.

     A *note memoryview: 25d. 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: 16b5. is one of the native format specifiers from
     the *note struct: f9. 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 hashable (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
     hashable.

     3.4 版更變: memoryview is now registered automatically with *note
     collections.abc.Sequence: 1635.

     3.5 版更變: memoryviews can now be indexed with tuple of integers.

     *note memoryview: 25d. 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: f9. syntax.

          For the subset of *note struct: f9. format strings currently
          supported by *note tolist(): 16b3, ‘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:
          f9. 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=None)

          Return the data in the buffer as a bytestring.  This is
          equivalent to calling the *note bytes: 336. 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(): 16b7. supports all format strings, including
          those that are not in *note struct: f9. 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(): 636, *note
          memoryview.hex(): 638. 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(): 16b3. now supports all single
          character native formats in *note struct: f9. 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()
               [89, 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: 337. 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: 1fc. (except *note
          release(): b42. 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: 16ba. and C-contiguous ->
          1D.

          The destination format is restricted to a single element
          native format in *note struct: f9. 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.

          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):
                 File "<stdin>", line 1, in <module>
               ValueError: memoryview: invalid value 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: f9. 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(): 16b3.) 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: 16be. 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: 16be. 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:
          16ba.

          3.3 版新加入.

      -- 屬性: f_contiguous

          A bool indicating whether the memory is Fortran *note
          contiguous: 16ba.

          3.3 版新加入.

      -- 屬性: contiguous

          A bool indicating whether the memory is *note contiguous:
          16ba.

          3.3 版新加入.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3118


File: python.info,  Node: Set Types --- set frozenset,  Next: Mapping Types --- dict,  Prev: Binary Sequence Types --- bytes bytearray memoryview,  Up: 內建型態

5.4.9 Set Types — ‘set’, ‘frozenset’
------------------------------------

A `set' object is an unordered collection of distinct *note hashable:
142e. 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: 1b9, *note list: 263, and
*note tuple: 483. classes, and the *note collections: 1e. 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: b74. and *note
frozenset: bf3.  The *note set: b74. 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: bf3. type is
immutable and *note hashable: 142e. — 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: b74. 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: 142e.
     To represent sets of sets, the inner sets must be *note frozenset:
     bf3. 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: b74. and *note frozenset: bf3. 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(): 16c9, *note
     intersection(): 16ca, *note difference(): 16cb, and *note
     symmetric_difference(): 16cc, *note issubset(): 16c7, and *note
     issuperset(): 16c8. 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: b74. and *note frozenset: bf3. 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: b74. are compared to instances of *note
     frozenset: bf3. 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(): 44a. method is undefined for lists
     of sets.

     Set elements, like dictionary keys, must be *note hashable: 142e.

     Binary operations that mix *note set: b74. instances with *note
     frozenset: bf3. return the type of the first operand.  For example:
     ‘frozenset('ab') | set('bc')’ returns an instance of *note
     frozenset: bf3.

     The following table lists operations available for *note set: b74.
     that do not apply to immutable instances of *note frozenset: bf3.:

      -- 成員函式: 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:
          2c8. 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: 2c8. if the set is empty.

      -- 成員函式: clear ()

          Remove all elements from the set.

     Note, the non-operator versions of the *note update(): 16ce, *note
     intersection_update(): 16cf, *note difference_update(): 16d0, and
     *note symmetric_difference_update(): 16d1. methods will accept any
     iterable as an argument.

     Note, the `elem' argument to the *note __contains__(): d2d, *note
     remove(): 16d3, and *note discard(): 16d4. 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: Context Manager Types,  Prev: Set Types --- set frozenset,  Up: 內建型態

5.4.10 Mapping Types — ‘dict’
-----------------------------

A *note mapping: b3e. object maps *note hashable: 142e. 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: 263, *note set: b74, and *note tuple: 483.
classes, and the *note collections: 1e. module.)

A dictionary’s keys are `almost' arbitrary values.  Values that are not
*note hashable: 142e, 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.  Numeric types used for keys obey the
normal rules for numeric comparison: if two numbers compare equal (such
as ‘1’ and ‘1.0’) then they can be used interchangeably to index the
same dictionary entry.  (Note however, that since computers store
floating-point numbers as approximations it is usually unwise to use
them as dictionary keys.)

Dictionaries can be created by placing a comma-separated list of ‘key:
value’ pairs within braces, for example: ‘{'jack': 4098, 'sjoerd':
4127}’ or ‘{4098: 'jack', 4127: 'sjoerd'}’, or by the *note dict: 1b9.
constructor.

 -- 類別: dict (**kwarg)

 -- 類別: dict (mapping, **kwarg)

 -- 類別: dict (iterable, **kwarg)

     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: bb1. 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})
          >>> a == b == c == d == e
          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: 2c8. if `key' is not in the map.

          If a subclass of dict defines a method *note __missing__():
          b40. 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 *note __missing__(): b40.  If *note
          __missing__(): b40. is not defined, *note KeyError: 2c8. is
          raised.  *note __missing__(): b40. 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: 9df.  A different ‘__missing__’ method is
          used by *note collections.defaultdict: b3f.

      -- Describe: d[key] = value

          Set ‘d[key]’ to `value'.

      -- Describe: del d[key]

          Remove ‘d[key]’ from `d'.  Raises a *note KeyError: 2c8. 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])

          Create a new dictionary with keys from `iterable' and values
          set to `value'.

          *note fromkeys(): 16d9. 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:
          653. instead.

      -- 成員函式: get (key[, default])

          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: 2c8.

      -- 成員函式: items ()

          Return a new view of the dictionary’s items (‘(key, value)’
          pairs).  See the *note documentation of view objects: 16db.

      -- 成員函式: keys ()

          Return a new view of the dictionary’s keys.  See the *note
          documentation of view objects: 16db.

      -- 成員函式: 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: 2c8. 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(): 16dd. is useful to destructively iterate over
          a dictionary, as often used in set algorithms.  If the
          dictionary is empty, calling *note popitem(): 16dd. raises a
          *note KeyError: 2c8.

          3.7 版更變: LIFO order is now guaranteed.  In prior versions,
          *note popitem(): 16dd. 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])

          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(): dce. 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: 16db.

          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

     Dictionaries compare equal if and only if they have the same ‘(key,
     value)’ pairs (regardless of ordering).  Order comparisons (’<’,
     ’<=’, ’>=’, ’>’) raise *note TypeError: 193.

     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: abb. can be used to create a read-only
view of a *note dict: 1b9.

* Menu:

* Dictionary view objects::


File: python.info,  Node: Dictionary view objects,  Up: Mapping Types --- dict

5.4.10.1 Dictionary view objects
................................

The objects returned by *note dict.keys(): c2f, *note dict.values():
c31. and *note dict.items(): c30. 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(): c37.:
     ‘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: 2bb. 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.

Keys views are set-like since their entries are unique and hashable.  If
all values are hashable, so that ‘(key, value)’ pairs are unique and
hashable, then the items view is also set-like.  (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: 16df. are available (for example, ‘==’,
‘<’, or ‘^’).

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'}


File: python.info,  Node: Context Manager Types,  Next: Other Built-in Types,  Prev: Mapping Types --- dict,  Up: 內建型態

5.4.11 Context Manager Types
----------------------------

Python’s *note with: 6ee. statement supports the concept of a runtime
context defined by a context manager.  This is implemented using a pair
of methods that allow user-defined classes to define a runtime context
that is entered before the statement body is executed and exited when
the statement ends:

 -- 成員函式: contextmanager.__enter__ ()

     Enter the runtime context and return either this object or another
     object related to the runtime context.  The value returned by this
     method is bound to the identifier in the ‘as’ clause of *note with:
     6ee. statements using this context manager.

     An example of a context manager that returns itself is a *note file
     object: b47.  File objects return themselves from __enter__() to
     allow *note open(): 4f5. to be used as the context expression in a
     *note with: 6ee. statement.

     An example of a context manager that returns a related object is
     the one returned by *note decimal.localcontext(): 16e2.  These
     managers set the active decimal context to a copy of the original
     decimal context and then return the copy.  This allows changes to
     be made to the current decimal context in the body of the *note
     with: 6ee. statement without affecting code outside the ‘with’
     statement.

 -- 成員函式: contextmanager.__exit__ (exc_type, exc_val, exc_tb)

     Exit the runtime context and return a Boolean flag indicating if
     any exception that occurred should be suppressed.  If an exception
     occurred while executing the body of the *note with: 6ee.
     statement, the arguments contain the exception type, value and
     traceback information.  Otherwise, all three arguments are ‘None’.

     Returning a true value from this method will cause the *note with:
     6ee. statement to suppress the exception and continue execution
     with the statement immediately following the ‘with’ statement.
     Otherwise the exception continues propagating after this method has
     finished executing.  Exceptions that occur during execution of this
     method will replace any exception that occurred in the body of the
     ‘with’ statement.

     The exception passed in should never be reraised explicitly -
     instead, this method should return a false value to indicate that
     the method completed successfully and does not want to suppress the
     raised exception.  This allows context management code to easily
     detect whether or not an *note __exit__(): 16e3. method has
     actually failed.

Python defines several context managers to support easy thread
synchronisation, prompt closure of files or other objects, and simpler
manipulation of the active decimal arithmetic context.  The specific
types are not treated specially beyond their implementation of the
context management protocol.  See the *note contextlib: 24. module for
some examples.

Python’s *note generator: 9a7.s and the *note contextlib.contextmanager:
b83. decorator provide a convenient way to implement these protocols.
If a generator function is decorated with the *note
contextlib.contextmanager: b83. decorator, it will return a context
manager implementing the necessary *note __enter__(): c9a. and *note
__exit__(): c9b. methods, rather than the iterator produced by an
undecorated generator function.

Note that there is no specific slot for any of these methods in the type
structure for Python objects in the Python/C API. Extension types
wanting to define these methods must provide them as a normal Python
accessible method.  Compared to the overhead of setting up the runtime
context, the overhead of a single class dictionary lookup is negligible.


File: python.info,  Node: Other Built-in Types,  Next: Special Attributes,  Prev: Context Manager Types,  Up: 內建型態

5.4.12 Other Built-in Types
---------------------------

The interpreter supports several other kinds of objects.  Most of these
support only one or two operations.

* Menu:

* Modules::
* Classes and Class Instances::
* Functions::
* Methods::
* Code Objects::
* Type Objects::
* The Null Object::
* The Ellipsis Object::
* The NotImplemented Object::
* Boolean Values::
* Internal Objects::


File: python.info,  Node: Modules,  Next: Classes and Class Instances,  Up: Other Built-in Types

5.4.12.1 Modules
................

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: c22. 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__: 501.  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__: 501. 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__: 501. 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: Functions,  Prev: Modules,  Up: Other Built-in Types

5.4.12.2 Classes and Class Instances
....................................

See *note Objects, values and types: 1423. and *note Class definitions:
c6f. for these.


File: python.info,  Node: Functions,  Next: Methods,  Prev: Classes and Class Instances,  Up: Other Built-in Types

5.4.12.3 Functions
..................

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.

See *note Function definitions: 1261. for more information.


File: python.info,  Node: Methods,  Next: Code Objects,  Prev: Functions,  Up: Other Built-in Types

5.4.12.4 Methods
................

Methods are functions that are called using the attribute notation.
There are two flavors: built-in methods (such as ‘append()’ on lists)
and class instance methods.  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
`instance method') object.  When called, it will add the ‘self’ argument
to the argument list.  Bound methods have two special read-only
attributes: ‘m.__self__’ is the object on which the method operates, and
‘m.__func__’ 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 function objects, bound method objects support getting arbitrary
attributes.  However, since method attributes are actually stored on the
underlying function object (‘meth.__func__’), setting method attributes
on bound methods is disallowed.  Attempting to set an attribute on a
method results in an *note AttributeError: 3a0. 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'  # can't set on the 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'

See *note The standard type hierarchy: 1426. for more information.


File: python.info,  Node: Code Objects,  Next: Type Objects,  Prev: Methods,  Up: Other Built-in Types

5.4.12.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(): 1b5. function and can be extracted from
function objects through their ‘__code__’ attribute.  See also the *note
code: 1b. module.

Accessing ‘__code__’ raises an *note auditing event: e96.
‘object.__getattr__’ with arguments ‘obj’ and ‘"__code__"’.

A code object can be executed or evaluated by passing it (instead of a
source string) to the *note exec(): c49. or *note eval(): b95. built-in
functions.

See *note The standard type hierarchy: 1426. for more information.


File: python.info,  Node: Type Objects,  Next: The Null Object,  Prev: Code Objects,  Up: Other Built-in Types

5.4.12.6 Type Objects
.....................

Type objects represent the various object types.  An object’s type is
accessed by the built-in function *note type(): 60d.  There are no
special operations on types.  The standard module *note types: 119.
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.12.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.

It is written as ‘None’.


File: python.info,  Node: The Ellipsis Object,  Next: The NotImplemented Object,  Prev: The Null Object,  Up: Other Built-in Types

5.4.12.8 The Ellipsis Object
............................

This object is commonly used by slicing (see *note Slicings: 151e.).  It
supports no special operations.  There is exactly one ellipsis object,
named *note Ellipsis: 1611. (a built-in name).  ‘type(Ellipsis)()’
produces the *note Ellipsis: 1611. singleton.

It is written as ‘Ellipsis’ or ‘...’.


File: python.info,  Node: The NotImplemented Object,  Next: Boolean Values,  Prev: The Ellipsis Object,  Up: Other Built-in Types

5.4.12.9 The NotImplemented Object
..................................

This object is returned from comparisons and binary operations when they
are asked to operate on types they don’t support.  See *note
Comparisons: 1546. for more information.  There is exactly one
‘NotImplemented’ object.  ‘type(NotImplemented)()’ produces the
singleton instance.

It is written as ‘NotImplemented’.


File: python.info,  Node: Boolean Values,  Next: Internal Objects,  Prev: The NotImplemented Object,  Up: Other Built-in Types

5.4.12.10 Boolean Values
........................

Boolean values are the two constant objects ‘False’ and ‘True’.  They
are used to represent truth values (although other values can also be
considered false or true).  In numeric contexts (for example when used
as the argument to an arithmetic operator), they behave like the
integers 0 and 1, respectively.  The built-in function *note bool():
184. can be used to convert any value to a Boolean, if the value can be
interpreted as a truth value (see section *note Truth Value Testing:
15e8. above).

They are written as ‘False’ and ‘True’, respectively.


File: python.info,  Node: Internal Objects,  Prev: Boolean Values,  Up: Other Built-in Types

5.4.12.11 Internal Objects
..........................

See *note The standard type hierarchy: 1426. for this information.  It
describes stack frame objects, traceback objects, and slice objects.


File: python.info,  Node: Special Attributes,  Prev: Other Built-in Types,  Up: 內建型態

5.4.13 Special Attributes
-------------------------

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(): d38. 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: 1430. of the class, function, method,
     descriptor, or generator instance.

     3.3 版新加入.

 -- 屬性: 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__: 160a.

 -- 成員函式: 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.  Example:

          >>> int.__subclasses__()
          [<class 'bool'>]

註解
....


File: python.info,  Node: 內建的例外,  Next: Text Processing Services,  Prev: 內建型態,  Up: Python 標準函式庫 Standard Library

5.5 內建的例外
==============

In Python, all exceptions must be instances of a class that derives from
*note BaseException: 1a9.  In a *note try: d77. statement with an *note
except: b43. clause that mentions a particular class, that clause also
handles any exception classes derived from that class (but not exception
classes from which `it' is derived).  Two exception classes that are not
related via subclassing are never equivalent, even if they have the same
name.

The built-in exceptions listed below can be generated by the interpreter
or built-in functions.  Except where mentioned, they have an "associated
value" indicating the detailed cause of the error.  This may be a string
or a tuple of several items of information (e.g., an error code and a
string explaining the code).  The associated value is usually passed as
arguments to the exception class’s constructor.

User code can raise built-in exceptions.  This can be used to test an
exception handler or to report an error condition "just like" the
situation in which the interpreter raises the same exception; but beware
that there is nothing to prevent user code from raising an inappropriate
error.

The built-in exception classes can be subclassed to define new
exceptions; programmers are encouraged to derive new exceptions from the
*note Exception: 1aa. class or one of its subclasses, and not from *note
BaseException: 1a9.  More information on defining exceptions is
available in the Python Tutorial under *note User-defined Exceptions:
12b7.

When raising (or re-raising) an exception in an *note except: b43. or
*note finally: 183. clause ‘__context__’ is automatically set to the
last exception caught; if the new exception is not handled the traceback
that is eventually displayed will include the originating exception(s)
and the final exception.

When raising a new exception (rather than using a bare ‘raise’ to
re-raise the exception currently being handled), the implicit exception
context can be supplemented with an explicit cause by using *note from:
c47. with *note raise: c47.:

     raise new_exc from original_exc

The expression following *note from: c47. must be an exception or
‘None’.  It will be set as ‘__cause__’ on the raised exception.  Setting
‘__cause__’ also implicitly sets the ‘__suppress_context__’ attribute to
‘True’, so that using ‘raise new_exc from None’ effectively replaces the
old exception with the new one for display purposes (e.g.  converting
*note KeyError: 2c8. to *note AttributeError: 3a0.), while leaving the
old exception available in ‘__context__’ for introspection when
debugging.

The default traceback display code shows these chained exceptions in
addition to the traceback for the exception itself.  An explicitly
chained exception in ‘__cause__’ is always shown when present.  An
implicitly chained exception in ‘__context__’ is shown only if
‘__cause__’ is *note None: 158. and ‘__suppress_context__’ is false.

In either case, the exception itself is always shown after any chained
exceptions so that the final line of the traceback always shows the last
exception that was raised.

* Menu:

* Base classes::
* Concrete exceptions::
* Warnings::
* Exception hierarchy::


File: python.info,  Node: Base classes,  Next: Concrete exceptions,  Up: 內建的例外

5.5.1 Base classes
------------------

The following exceptions are used mostly as base classes for other
exceptions.

 -- 例外: BaseException

     The base class for all built-in exceptions.  It is not meant to be
     directly inherited by user-defined classes (for that, use *note
     Exception: 1aa.).  If *note str(): 335. is called on an instance of
     this class, the representation of the argument(s) to the instance
     are returned, or the empty string when there were no arguments.

      -- 屬性: args

          The tuple of arguments given to the exception constructor.
          Some built-in exceptions (like *note OSError: 1d4.) expect a
          certain number of arguments and assign a special meaning to
          the elements of this tuple, while others are usually called
          only with a single string giving an error message.

      -- 成員函式: with_traceback (tb)

          This method sets `tb' as the new traceback for the exception
          and returns the exception object.  It is usually used in
          exception handling code like this:

               try:
                   ...
               except SomeException:
                   tb = sys.exc_info()[2]
                   raise OtherException(...).with_traceback(tb)

 -- 例外: Exception

     All built-in, non-system-exiting exceptions are derived from this
     class.  All user-defined exceptions should also be derived from
     this class.

 -- 例外: ArithmeticError

     The base class for those built-in exceptions that are raised for
     various arithmetic errors: *note OverflowError: 965, *note
     ZeroDivisionError: 12b2, *note FloatingPointError: 1704.

 -- 例外: BufferError

     Raised when a *note buffer: 15ec. related operation cannot be
     performed.

 -- 例外: LookupError

     The base class for the exceptions that are raised when a key or
     index used on a mapping or sequence is invalid: *note IndexError:
     e7a, *note KeyError: 2c8.  This can be raised directly by *note
     codecs.lookup(): 1706.


File: python.info,  Node: Concrete exceptions,  Next: Warnings,  Prev: Base classes,  Up: 內建的例外

5.5.2 Concrete exceptions
-------------------------

The following exceptions are the exceptions that are usually raised.

 -- 例外: AssertionError

     Raised when an *note assert: e0b. statement fails.

 -- 例外: AttributeError

     Raised when an attribute reference (see *note Attribute references:
     1517.) or assignment fails.  (When an object does not support
     attribute references or attribute assignments at all, *note
     TypeError: 193. is raised.)

 -- 例外: EOFError

     Raised when the *note input(): c70. function hits an end-of-file
     condition (EOF) without reading any data.  (N.B.: the
     ‘io.IOBase.read()’ and *note io.IOBase.readline(): 1708. methods
     return an empty string when they hit EOF.)

 -- 例外: FloatingPointError

     Not currently used.

 -- 例外: GeneratorExit

     Raised when a *note generator: 9a7. or *note coroutine: 1a7. is
     closed; see *note generator.close(): 1498. and *note
     coroutine.close(): 1497.  It directly inherits from *note
     BaseException: 1a9. instead of *note Exception: 1aa. since it is
     technically not an error.

 -- 例外: ImportError

     Raised when the *note import: c22. statement has troubles trying to
     load a module.  Also raised when the "from list" in ‘from ...
     import’ has a name that cannot be found.

     The ‘name’ and ‘path’ attributes can be set using keyword-only
     arguments to the constructor.  When set they represent the name of
     the module that was attempted to be imported and the path to any
     file which triggered the exception, respectively.

     3.3 版更變: Added the ‘name’ and ‘path’ attributes.

 -- 例外: ModuleNotFoundError

     A subclass of *note ImportError: 339. which is raised by *note
     import: c22. when a module could not be located.  It is also raised
     when ‘None’ is found in *note sys.modules: f2b.

     3.6 版新加入.

 -- 例外: IndexError

     Raised when a sequence subscript is out of range.  (Slice indices
     are silently truncated to fall in the allowed range; if an index is
     not an integer, *note TypeError: 193. is raised.)

 -- 例外: KeyError

     Raised when a mapping (dictionary) key is not found in the set of
     existing keys.

 -- 例外: KeyboardInterrupt

     Raised when the user hits the interrupt key (normally ‘Control-C’
     or ‘Delete’).  During execution, a check for interrupts is made
     regularly.  The exception inherits from *note BaseException: 1a9.
     so as to not be accidentally caught by code that catches *note
     Exception: 1aa. and thus prevent the interpreter from exiting.

 -- 例外: MemoryError

     Raised when an operation runs out of memory but the situation may
     still be rescued (by deleting some objects).  The associated value
     is a string indicating what kind of (internal) operation ran out of
     memory.  Note that because of the underlying memory management
     architecture (C’s ‘malloc()’ function), the interpreter may not
     always be able to completely recover from this situation; it
     nevertheless raises an exception so that a stack traceback can be
     printed, in case a run-away program was the cause.

 -- 例外: NameError

     Raised when a local or global name is not found.  This applies only
     to unqualified names.  The associated value is an error message
     that includes the name that could not be found.

 -- 例外: NotImplementedError

     This exception is derived from *note RuntimeError: 2bb.  In user
     defined base classes, abstract methods should raise this exception
     when they require derived classes to override the method, or while
     the class is being developed to indicate that the real
     implementation still needs to be added.

          備註: It should not be used to indicate that an operator or
          method is not meant to be supported at all – in that case
          either leave the operator / method undefined or, if a
          subclass, set it to *note None: 158.

          備註: ‘NotImplementedError’ and ‘NotImplemented’ are not
          interchangeable, even though they have similar names and
          purposes.  See *note NotImplemented: 851. for details on when
          to use it.

 -- 例外: OSError ([arg])

 -- 例外: OSError (errno, strerror[, filename[, winerror[, filename2]]])

     This exception is raised when a system function returns a
     system-related error, including I/O failures such as "file not
     found" or "disk full" (not for illegal argument types or other
     incidental errors).

     The second form of the constructor sets the corresponding
     attributes, described below.  The attributes default to *note None:
     158. if not specified.  For backwards compatibility, if three
     arguments are passed, the *note args: 1701. attribute contains only
     a 2-tuple of the first two constructor arguments.

     The constructor often actually returns a subclass of *note OSError:
     1d4, as described in *note OS exceptions: 1709. below.  The
     particular subclass depends on the final *note errno: 170a. value.
     This behaviour only occurs when constructing *note OSError: 1d4.
     directly or via an alias, and is not inherited when subclassing.

      -- 屬性: errno

          A numeric error code from the C variable ‘errno’.

      -- 屬性: winerror

          Under Windows, this gives you the native Windows error code.
          The *note errno: 170a. attribute is then an approximate
          translation, in POSIX terms, of that native error code.

          Under Windows, if the `winerror' constructor argument is an
          integer, the *note errno: 170a. attribute is determined from
          the Windows error code, and the `errno' argument is ignored.
          On other platforms, the `winerror' argument is ignored, and
          the *note winerror: 170b. attribute does not exist.

      -- 屬性: strerror

          The corresponding error message, as provided by the operating
          system.  It is formatted by the C functions ‘perror()’ under
          POSIX, and ‘FormatMessage()’ under Windows.

      -- 屬性: filename
      -- 屬性: filename2

          For exceptions that involve a file system path (such as *note
          open(): 4f5. or *note os.unlink(): a41.), *note filename:
          170d. is the file name passed to the function.  For functions
          that involve two file system paths (such as *note os.rename():
          a3d.), *note filename2: 170e. corresponds to the second file
          name passed to the function.

     3.3 版更變: *note EnvironmentError: 998, *note IOError: 997, *note
     WindowsError: 999, *note socket.error: 99a, *note select.error:
     99b. and ‘mmap.error’ have been merged into *note OSError: 1d4, and
     the constructor may return a subclass.

     3.4 版更變: The *note filename: 170d. attribute is now the original
     file name passed to the function, instead of the name encoded to or
     decoded from the filesystem encoding.  Also, the `filename2'
     constructor argument and attribute was added.

 -- 例外: OverflowError

     Raised when the result of an arithmetic operation is too large to
     be represented.  This cannot occur for integers (which would rather
     raise *note MemoryError: ef1. than give up).  However, for
     historical reasons, OverflowError is sometimes raised for integers
     that are outside a required range.  Because of the lack of
     standardization of floating point exception handling in C, most
     floating point operations are not checked.

 -- 例外: RecursionError

     This exception is derived from *note RuntimeError: 2bb.  It is
     raised when the interpreter detects that the maximum recursion
     depth (see *note sys.getrecursionlimit(): e7f.) is exceeded.

     3.5 版新加入: Previously, a plain *note RuntimeError: 2bb. was
     raised.

 -- 例外: ReferenceError

     This exception is raised when a weak reference proxy, created by
     the *note weakref.proxy(): 251. function, is used to access an
     attribute of the referent after it has been garbage collected.  For
     more information on weak references, see the *note weakref: 129.
     module.

 -- 例外: RuntimeError

     Raised when an error is detected that doesn’t fall in any of the
     other categories.  The associated value is a string indicating what
     precisely went wrong.

 -- 例外: StopIteration

     Raised by built-in function *note next(): 687. and an *note
     iterator: 1040.’s *note __next__(): c69. method to signal that
     there are no further items produced by the iterator.

     The exception object has a single attribute ‘value’, which is given
     as an argument when constructing the exception, and defaults to
     *note None: 158.

     When a *note generator: 9a7. or *note coroutine: 1a7. function
     returns, a new *note StopIteration: 48b. instance is raised, and
     the value returned by the function is used as the ‘value’ parameter
     to the constructor of the exception.

     If a generator code directly or indirectly raises *note
     StopIteration: 48b, it is converted into a *note RuntimeError: 2bb.
     (retaining the *note StopIteration: 48b. as the new exception’s
     cause).

     3.3 版更變: Added ‘value’ attribute and the ability for generator
     functions to use it to return a value.

     3.5 版更變: Introduced the RuntimeError transformation via ‘from
     __future__ import generator_stop’, see PEP 479(1).

     3.7 版更變: Enable PEP 479(2) for all code by default: a *note
     StopIteration: 48b. error raised in a generator is transformed into
     a *note RuntimeError: 2bb.

 -- 例外: StopAsyncIteration

     Must be raised by *note __anext__(): 149a. method of an *note
     asynchronous iterator: 64a. object to stop the iteration.

     3.5 版新加入.

 -- 例外: SyntaxError

     Raised when the parser encounters a syntax error.  This may occur
     in an *note import: c22. statement, in a call to the built-in
     functions *note exec(): c49. or *note eval(): b95, or when reading
     the initial script or standard input (also interactively).

     The *note str(): 335. of the exception instance returns only the
     error message.

      -- 屬性: filename

          The name of the file the syntax error occurred in.

      -- 屬性: lineno

          Which line number in the file the error occurred in.  This is
          1-indexed: the first line in the file has a ‘lineno’ of 1.

      -- 屬性: offset

          The column in the line where the error occurred.  This is
          1-indexed: the first character in the line has an ‘offset’ of
          1.

      -- 屬性: text

          The source code text involved in the error.

 -- 例外: IndentationError

     Base class for syntax errors related to incorrect indentation.
     This is a subclass of *note SyntaxError: 45d.

 -- 例外: TabError

     Raised when indentation contains an inconsistent use of tabs and
     spaces.  This is a subclass of *note IndentationError: e7d.

 -- 例外: SystemError

     Raised when the interpreter finds an internal error, but the
     situation does not look so serious to cause it to abandon all hope.
     The associated value is a string indicating what went wrong (in
     low-level terms).

     You should report this to the author or maintainer of your Python
     interpreter.  Be sure to report the version of the Python
     interpreter (‘sys.version’; it is also printed at the start of an
     interactive Python session), the exact error message (the
     exception’s associated value) and if possible the source of the
     program that triggered the error.

 -- 例外: SystemExit

     This exception is raised by the *note sys.exit(): ce7. function.
     It inherits from *note BaseException: 1a9. instead of *note
     Exception: 1aa. so that it is not accidentally caught by code that
     catches *note Exception: 1aa.  This allows the exception to
     properly propagate up and cause the interpreter to exit.  When it
     is not handled, the Python interpreter exits; no stack traceback is
     printed.  The constructor accepts the same optional argument passed
     to *note sys.exit(): ce7.  If the value is an integer, it specifies
     the system exit status (passed to C’s ‘exit()’ function); if it is
     ‘None’, the exit status is zero; if it has another type (such as a
     string), the object’s value is printed and the exit status is one.

     A call to *note sys.exit(): ce7. is translated into an exception so
     that clean-up handlers (*note finally: 183. clauses of *note try:
     d77. statements) can be executed, and so that a debugger can
     execute a script without running the risk of losing control.  The
     *note os._exit(): 1713. function can be used if it is absolutely
     positively necessary to exit immediately (for example, in the child
     process after a call to *note os.fork(): 966.).

      -- 屬性: code

          The exit status or error message that is passed to the
          constructor.  (Defaults to ‘None’.)

 -- 例外: TypeError

     Raised when an operation or function is applied to an object of
     inappropriate type.  The associated value is a string giving
     details about the type mismatch.

     This exception may be raised by user code to indicate that an
     attempted operation on an object is not supported, and is not meant
     to be.  If an object is meant to support a given operation but has
     not yet provided an implementation, *note NotImplementedError: 613.
     is the proper exception to raise.

     Passing arguments of the wrong type (e.g.  passing a *note list:
     263. when an *note int: 185. is expected) should result in a *note
     TypeError: 193, but passing arguments with the wrong value (e.g.  a
     number outside expected boundaries) should result in a *note
     ValueError: 1fc.

 -- 例外: UnboundLocalError

     Raised when a reference is made to a local variable in a function
     or method, but no value has been bound to that variable.  This is a
     subclass of *note NameError: d80.

 -- 例外: UnicodeError

     Raised when a Unicode-related encoding or decoding error occurs.
     It is a subclass of *note ValueError: 1fc.

     *note UnicodeError: c40. has attributes that describe the encoding
     or decoding error.  For example, ‘err.object[err.start:err.end]’
     gives the particular invalid input that the codec failed on.

      -- 屬性: encoding

          The name of the encoding that raised the error.

      -- 屬性: reason

          A string describing the specific codec error.

      -- 屬性: object

          The object the codec was attempting to encode or decode.

      -- 屬性: start

          The first index of invalid data in *note object: 2b1.

      -- 屬性: end

          The index after the last invalid data in *note object: 2b1.

 -- 例外: UnicodeEncodeError

     Raised when a Unicode-related error occurs during encoding.  It is
     a subclass of *note UnicodeError: c40.

 -- 例外: UnicodeDecodeError

     Raised when a Unicode-related error occurs during decoding.  It is
     a subclass of *note UnicodeError: c40.

 -- 例外: UnicodeTranslateError

     Raised when a Unicode-related error occurs during translating.  It
     is a subclass of *note UnicodeError: c40.

 -- 例外: ValueError

     Raised when an operation or function receives an argument that has
     the right type but an inappropriate value, and the situation is not
     described by a more precise exception such as *note IndexError:
     e7a.

 -- 例外: ZeroDivisionError

     Raised when the second argument of a division or modulo operation
     is zero.  The associated value is a string indicating the type of
     the operands and the operation.

The following exceptions are kept for compatibility with previous
versions; starting from Python 3.3, they are aliases of *note OSError:
1d4.

 -- 例外: EnvironmentError

 -- 例外: IOError

 -- 例外: WindowsError

     Only available on Windows.

* Menu:

* OS exceptions::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0479

   (2) https://www.python.org/dev/peps/pep-0479


File: python.info,  Node: OS exceptions,  Up: Concrete exceptions

5.5.2.1 OS exceptions
.....................

The following exceptions are subclasses of *note OSError: 1d4, they get
raised depending on the system error code.

 -- 例外: BlockingIOError

     Raised when an operation would block on an object (e.g.  socket)
     set for non-blocking operation.  Corresponds to ‘errno’ ‘EAGAIN’,
     ‘EALREADY’, ‘EWOULDBLOCK’ and ‘EINPROGRESS’.

     In addition to those of *note OSError: 1d4, *note BlockingIOError:
     99c. can have one more attribute:

      -- 屬性: characters_written

          An integer containing the number of characters written to the
          stream before it blocked.  This attribute is available when
          using the buffered I/O classes from the *note io: a2. module.

 -- 例外: ChildProcessError

     Raised when an operation on a child process failed.  Corresponds to
     ‘errno’ ‘ECHILD’.

 -- 例外: ConnectionError

     A base class for connection-related issues.

     Subclasses are *note BrokenPipeError: 9a2, *note
     ConnectionAbortedError: 9a3, *note ConnectionRefusedError: 9a4. and
     *note ConnectionResetError: 9a5.

 -- 例外: BrokenPipeError

     A subclass of *note ConnectionError: 6eb, raised when trying to
     write on a pipe while the other end has been closed, or trying to
     write on a socket which has been shutdown for writing.  Corresponds
     to ‘errno’ ‘EPIPE’ and ‘ESHUTDOWN’.

 -- 例外: ConnectionAbortedError

     A subclass of *note ConnectionError: 6eb, raised when a connection
     attempt is aborted by the peer.  Corresponds to ‘errno’
     ‘ECONNABORTED’.

 -- 例外: ConnectionRefusedError

     A subclass of *note ConnectionError: 6eb, raised when a connection
     attempt is refused by the peer.  Corresponds to ‘errno’
     ‘ECONNREFUSED’.

 -- 例外: ConnectionResetError

     A subclass of *note ConnectionError: 6eb, raised when a connection
     is reset by the peer.  Corresponds to ‘errno’ ‘ECONNRESET’.

 -- 例外: FileExistsError

     Raised when trying to create a file or directory which already
     exists.  Corresponds to ‘errno’ ‘EEXIST’.

 -- 例外: FileNotFoundError

     Raised when a file or directory is requested but doesn’t exist.
     Corresponds to ‘errno’ ‘ENOENT’.

 -- 例外: InterruptedError

     Raised when a system call is interrupted by an incoming signal.
     Corresponds to ‘errno’ *note EINTR: 65d.

     3.5 版更變: Python now retries system calls when a syscall is
     interrupted by a signal, except if the signal handler raises an
     exception (see PEP 475(1) for the rationale), instead of raising
     *note InterruptedError: 65e.

 -- 例外: IsADirectoryError

     Raised when a file operation (such as *note os.remove(): a3c.) is
     requested on a directory.  Corresponds to ‘errno’ ‘EISDIR’.

 -- 例外: NotADirectoryError

     Raised when a directory operation (such as *note os.listdir():
     a46.) is requested on something which is not a directory.
     Corresponds to ‘errno’ ‘ENOTDIR’.

 -- 例外: PermissionError

     Raised when trying to run an operation without the adequate access
     rights - for example filesystem permissions.  Corresponds to
     ‘errno’ ‘EACCES’ and ‘EPERM’.

 -- 例外: ProcessLookupError

     Raised when a given process doesn’t exist.  Corresponds to ‘errno’
     ‘ESRCH’.

 -- 例外: TimeoutError

     Raised when a system function timed out at the system level.
     Corresponds to ‘errno’ ‘ETIMEDOUT’.

3.3 版新加入: All the above *note OSError: 1d4. subclasses were added.

也參考
......

PEP 3151(2) - Reworking the OS and IO exception hierarchy

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0475

   (2) https://www.python.org/dev/peps/pep-3151


File: python.info,  Node: Warnings,  Next: Exception hierarchy,  Prev: Concrete exceptions,  Up: 內建的例外

5.5.3 Warnings
--------------

The following exceptions are used as warning categories; see the *note
Warning Categories: 171e. documentation for more details.

 -- 例外: Warning

     Base class for warning categories.

 -- 例外: UserWarning

     Base class for warnings generated by user code.

 -- 例外: DeprecationWarning

     Base class for warnings about deprecated features when those
     warnings are intended for other Python developers.

 -- 例外: PendingDeprecationWarning

     Base class for warnings about features which are obsolete and
     expected to be deprecated in the future, but are not deprecated at
     the moment.

     This class is rarely used as emitting a warning about a possible
     upcoming deprecation is unusual, and *note DeprecationWarning: 279.
     is preferred for already active deprecations.

 -- 例外: SyntaxWarning

     Base class for warnings about dubious syntax.

 -- 例外: RuntimeWarning

     Base class for warnings about dubious runtime behavior.

 -- 例外: FutureWarning

     Base class for warnings about deprecated features when those
     warnings are intended for end users of applications that are
     written in Python.

 -- 例外: ImportWarning

     Base class for warnings about probable mistakes in module imports.

 -- 例外: UnicodeWarning

     Base class for warnings related to Unicode.

 -- 例外: BytesWarning

     Base class for warnings related to *note bytes: 336. and *note
     bytearray: 337.

 -- 例外: ResourceWarning

     Base class for warnings related to resource usage.  Ignored by the
     default warning filters.

     3.2 版新加入.


File: python.info,  Node: Exception hierarchy,  Prev: Warnings,  Up: 內建的例外

5.5.4 Exception hierarchy
-------------------------

The class hierarchy for built-in exceptions is:

     BaseException
      +-- SystemExit
      +-- KeyboardInterrupt
      +-- GeneratorExit
      +-- Exception
           +-- StopIteration
           +-- StopAsyncIteration
           +-- ArithmeticError
           |    +-- FloatingPointError
           |    +-- OverflowError
           |    +-- ZeroDivisionError
           +-- AssertionError
           +-- AttributeError
           +-- BufferError
           +-- EOFError
           +-- 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
           |    +-- RecursionError
           +-- SyntaxError
           |    +-- IndentationError
           |         +-- TabError
           +-- SystemError
           +-- TypeError
           +-- ValueError
           |    +-- UnicodeError
           |         +-- UnicodeDecodeError
           |         +-- UnicodeEncodeError
           |         +-- UnicodeTranslateError
           +-- Warning
                +-- DeprecationWarning
                +-- PendingDeprecationWarning
                +-- RuntimeWarning
                +-- SyntaxWarning
                +-- UserWarning
                +-- FutureWarning
                +-- ImportWarning
                +-- UnicodeWarning
                +-- BytesWarning
                +-- ResourceWarning


File: python.info,  Node: Text Processing Services,  Next: Binary Data Services,  Prev: 內建的例外,  Up: Python 標準函式庫 Standard Library

5.6 Text Processing Services
============================

The modules described in this chapter provide a wide range of string
manipulation operations and other text processing services.

The *note codecs: 1c. module described under *note Binary Data Services:
1724. is also highly relevant to text processing.  In addition, see the
documentation for Python’s built-in string type in *note Text Sequence
Type — str: 1228.

* Menu:

* string: string --- Common string operations. Common string operations
* re: re --- Regular expression operations. Regular expression operations
* difflib: difflib --- Helpers for computing deltas. Helpers for computing deltas
* textwrap: textwrap --- Text wrapping and filling. Text wrapping and filling
* unicodedata: unicodedata --- Unicode Database. Unicode Database
* stringprep: stringprep --- Internet String Preparation. Internet String Preparation
* readline: readline --- GNU readline interface. GNU readline interface
* rlcompleter: rlcompleter --- Completion function for GNU readline. Completion function for GNU readline


File: python.info,  Node: string --- Common string operations,  Next: re --- Regular expression operations,  Up: Text Processing Services

5.6.1 ‘string’ — Common string operations
-----------------------------------------

`Source code:' Lib/string.py(1)

__________________________________________________________________

也參考
......

*note Text Sequence Type — str: 1228.

*note String Methods: 1229.

* Menu:

* String constants::
* Custom String Formatting::
* Format String Syntax::
* Template strings::
* Helper functions::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/string.py


File: python.info,  Node: String constants,  Next: Custom String Formatting,  Up: string --- Common string operations

5.6.1.1 String constants
........................

The constants defined in this module are:

 -- Data: string.ascii_letters

     The concatenation of the *note ascii_lowercase: 1728. and *note
     ascii_uppercase: 1729. constants described below.  This value is
     not locale-dependent.

 -- Data: string.ascii_lowercase

     The lowercase letters ‘'abcdefghijklmnopqrstuvwxyz'’.  This value
     is not locale-dependent and will not change.

 -- Data: string.ascii_uppercase

     The uppercase letters ‘'ABCDEFGHIJKLMNOPQRSTUVWXYZ'’.  This value
     is not locale-dependent and will not change.

 -- Data: string.digits

     The string ‘'0123456789'’.

 -- Data: string.hexdigits

     The string ‘'0123456789abcdefABCDEF'’.

 -- Data: string.octdigits

     The string ‘'01234567'’.

 -- Data: string.punctuation

     String of ASCII characters which are considered punctuation
     characters in the ‘C’ locale: ‘!"#$%&'()*+,-./:;<=>?@[\]^_`{|}~’.

 -- Data: string.printable

     String of ASCII characters which are considered printable.  This is
     a combination of *note digits: 172a, *note ascii_letters: c61,
     *note punctuation: 172d, and *note whitespace: 172f.

 -- Data: string.whitespace

     A string containing all ASCII characters that are considered
     whitespace.  This includes the characters space, tab, linefeed,
     return, formfeed, and vertical tab.


File: python.info,  Node: Custom String Formatting,  Next: Format String Syntax,  Prev: String constants,  Up: string --- Common string operations

5.6.1.2 Custom String Formatting
................................

The built-in string class provides the ability to do complex variable
substitutions and value formatting via the *note format(): 4df. method
described in PEP 3101(1).  The *note Formatter: 7ba. class in the *note
string: f7. module allows you to create and customize your own string
formatting behaviors using the same implementation as the built-in *note
format(): 4df. method.

 -- 類別: string.Formatter

     The *note Formatter: 7ba. class has the following public methods:

      -- 成員函式: format (format_string, /, *args, **kwargs)

          The primary API method.  It takes a format string and an
          arbitrary set of positional and keyword arguments.  It is just
          a wrapper that calls *note vformat(): 1731.

          3.7 版更變: A format string argument is now *note
          positional-only: 2a8.

      -- 成員函式: 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():
          1731. 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: 7ba. defines a number of methods
     that are intended to be replaced by subclasses:

      -- 成員函式: parse (format_string)

          Loop over the format_string and return an iterable of tuples
          (`literal_text', `field_name', `format_spec', `conversion').
          This is used by *note vformat(): 1731. to break the string
          into either literal text, or replacement fields.

          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(): 1732. (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(): 1731.  The return value `used_key' has the same
          meaning as the `key' parameter to *note get_value(): 1734.

      -- 成員函式: 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(): 1731, 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(): 1734. to be called with a `key' argument of
          0.  The ‘name’ attribute will be looked up after *note
          get_value(): 1734. returns by calling the built-in *note
          getattr(): 44d. function.

          If the index or keyword refers to an item that does not exist,
          then an *note IndexError: e7a. or *note KeyError: 2c8. 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(): 1735. is assumed to
          raise an exception if the check fails.

      -- 成員函式: format_field (value, format_spec)

          *note format_field(): 1736. simply calls the global *note
          format(): 4e0. built-in.  The method is provided so that
          subclasses can override it.

      -- 成員函式: convert_field (value, conversion)

          Converts the value (returned by *note get_field(): 1733.)
          given a conversion type (as in the tuple returned by the *note
          parse(): 1732. method).  The default version understands ’s’
          (str), ’r’ (repr) and ’a’ (ascii) conversion types.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3101

   (2) https://www.python.org/dev/peps/pep-3101


File: python.info,  Node: Format String Syntax,  Next: Template strings,  Prev: Custom String Formatting,  Up: string --- Common string operations

5.6.1.3 Format String Syntax
............................

The *note str.format(): 4df. method and the *note Formatter: 7ba. class
share the same syntax for format strings (although in the case of *note
Formatter: 7ba, subclasses can define their own format string syntax).
The syntax is related to that of *note formatted string literals: 15d,
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       ::= <described in the next section>

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.

See also the *note Format Specification Mini-Language: 4e3. section.

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.
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(): 44d, while an expression of the
form ‘'[index]'’ does an index lookup using *note __getitem__(): 27d.

3.1 版更變: The positional argument specifiers can be omitted for *note
str.format(): 4df, so ‘'{} {}'.format(a, b)’ is equivalent to ‘'{0}
{1}'.format(a, b)’.

3.4 版更變: The positional argument specifiers can be omitted for *note
Formatter: 7ba.

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__(): 953. 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__(): 953, the normal formatting logic is
bypassed.

Three conversion flags are currently supported: ‘'!s'’ which calls *note
str(): 335. on the value, ‘'!r'’ which calls *note repr(): 7d1. and
‘'!a'’ which calls *note ascii(): d51.

一些範例：

     "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

The `format_spec' field contains a specification of how the value should
be presented, including such details as field width, alignment, padding,
decimal precision and so on.  Each value type can define its own
"formatting mini-language" or interpretation of the `format_spec'.

Most built-in types support a common formatting mini-language, which is
described in the next section.

A `format_spec' field can also include nested replacement fields within
it.  These nested replacement fields may contain a field name,
conversion flag and format specification, but deeper nesting is not
allowed.  The replacement fields within the format_spec are substituted
before the `format_spec' string is interpreted.  This allows the
formatting of a value to be dynamically specified.

See the *note Format examples: 1741. section for some examples.

* Menu:

* Format Specification Mini-Language::
* Format examples::


File: python.info,  Node: Format Specification Mini-Language,  Next: Format examples,  Up: Format String Syntax

5.6.1.4 Format Specification Mini-Language
..........................................

"Format specifications" are used within replacement fields contained
within a format string to define how individual values are presented
(see *note Format String Syntax: d1f. and *note Formatted string
literals: 15d.).  They can also be passed directly to the built-in *note
format(): 4e0. function.  Each formattable type may define how the
format specification is to be interpreted.

Most built-in types implement the following options for format
specifications, although some of the formatting options are only
supported by the numeric types.

A general convention is that an empty format specification produces the
same result as if you had called *note str(): 335. on the value.  A
non-empty format specification typically modifies the result.

The general form of a `standard format specifier' is:

     format_spec     ::= [[fill]align][sign][#][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" | "%"

If a valid `align' value is specified, it can be preceded by a `fill'
character that can be any character and defaults to a space if omitted.
It is not possible to use a literal curly brace ("‘{’" or "‘}’") as the
`fill' character in a *note formatted string literal: 15d. or when using
the *note str.format(): 4df. method.  However, it is possible to insert
a curly brace with a nested replacement field.  This limitation doesn’t
affect the *note format(): 4e0. function.

The meaning of the various alignment options is as follows:

     Option        Meaning
                   
     -----------------------------------------------------------------------------
                   
     ‘'<'’         Forces the field to be left-aligned within the available
                   space (this is the default for most objects).
                   
                   
     ‘'>'’         Forces the field to be right-aligned within the available
                   space (this is the default for numbers).
                   
                   
     ‘'='’         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 when ’0’ immediately
                   precedes the field width.
                   
                   
     ‘'^'’         Forces the field to be centered within the available space.
                   

Note that unless a minimum field width is defined, the field width will
always be the same size as the data to fill it, so that the alignment
option has no meaning in this case.

The `sign' option is only valid for number types, and can be one of the
following:

     Option        Meaning
                   
     -----------------------------------------------------------------------------
                   
     ‘'+'’         indicates that a sign should be used for both positive as
                   well as negative numbers.
                   
                   
     ‘'-'’         indicates that a sign should be used only for negative
                   numbers (this is the default behavior).
                   
                   
     space         indicates that a leading space should be used on positive
                   numbers, and a minus sign on negative numbers.
                   

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 prefix respective ‘'0b'’, ‘'0o'’, 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 版更變: Added the ‘','’ option (see also PEP 378(1)).

The ‘'_'’ option signals 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.  For
other presentation types, specifying this option is an error.

3.6 版更變: Added the ‘'_'’ option (see also PEP 515(2)).

`width' is a decimal integer defining the minimum total field width,
including any prefixes, separators, and other formatting characters.  If
not specified, then the field width will be determined by the content.

When no explicit alignment is given, preceding the `width' field by a
zero (‘'0'’) character enables sign-aware zero-padding for numeric
types.  This is equivalent to a `fill' character of ‘'0'’ with an
`alignment' type of ‘'='’.

The `precision' is a decimal number indicating how many digits should be
displayed after the decimal point for a floating point value formatted
with ‘'f'’ and ‘'F'’, or before and after the decimal point for a
floating point value formatted with ‘'g'’ or ‘'G'’.  For non-number
types the field indicates the maximum field size - in other words, how
many characters will be used from the field content.  The `precision' is
not allowed for integer values.

Finally, the `type' determines how the data should be presented.

The available string presentation types are:

     Type          Meaning
                   
     -----------------------------------------------------------------------------
                   
     ‘'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:

     Type          Meaning
                   
     -----------------------------------------------------------------------------
                   
     ‘'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'’         Hex format.  Outputs the number in base 16, using lower-case
                   letters for the digits above 9.
                   
                   
     ‘'X'’         Hex format.  Outputs the number in base 16, using upper-case
                   letters for the digits above 9.
                   
                   
     ‘'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(): 188. is used to convert the
integer to a floating point number before formatting.

The available presentation types for *note float: 188. and *note
Decimal: 189. values are:

     Type          Meaning
                   
     -----------------------------------------------------------------------------
                   
     ‘'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: 188, and shows all coefficient digits
                   for *note Decimal: 189.  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: 188, and uses a precision large enough to show
                   all coefficient digits for *note Decimal: 189.  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: 189, 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: 188.  For *note Decimal: 189, 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: 188. 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: 189, 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(): 335. as altered by the other format modifiers.
                   

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0378

   (2) https://www.python.org/dev/peps/pep-0515


File: python.info,  Node: Format examples,  Prev: Format Specification Mini-Language,  Up: Format String Syntax

5.6.1.5 Format examples
.......................

This section contains examples of the *note str.format(): 4df. syntax
and comparison with the old ‘%’-formatting.

In most of the cases the syntax is similar to the old ‘%’-formatting,
with the addition of the ‘{}’ and with ‘:’ used instead of ‘%’.  For
example, ‘'%03.2f'’ can be translated to ‘'{:03.2f}'’.

The new format syntax also supports new and different options, shown in
the following examples.

Accessing arguments by position:

     >>> '{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'

Accessing arguments by name:

     >>> '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'

Accessing arguments’ attributes:

     >>> 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)'

Accessing arguments’ items:

     >>> coord = (3, 5)
     >>> 'X: {0[0]};  Y: {0[1]}'.format(coord)
     'X: 3;  Y: 5'

Replacing ‘%s’ and ‘%r’:

     >>> "repr() shows quotes: {!r}; str() doesn't: {!s}".format('test1', 'test2')
     "repr() shows quotes: 'test1'; str() doesn't: test2"

Aligning the text and specifying a width:

     >>> '{:<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***********'

Replacing ‘%+f’, ‘%-f’, and ‘% f’ and specifying a sign:

     >>> '{:+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'

Replacing ‘%x’ and ‘%o’ and converting the value to different bases:

     >>> # 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'

Using the comma as a thousands separator:

     >>> '{:,}'.format(1234567890)
     '1,234,567,890'

Expressing a percentage:

     >>> points = 19
     >>> total = 22
     >>> 'Correct answers: {:.2%}'.format(points/total)
     'Correct answers: 86.36%'

Using type-specific formatting:

     >>> 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'

Nesting arguments and more complex examples:

     >>> 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: Template strings,  Next: Helper functions,  Prev: Format String Syntax,  Up: string --- Common string operations

5.6.1.6 Template strings
........................

Template strings provide simpler string substitutions as described in
PEP 292(1).  A primary use case for template strings is for
internationalization (i18n) since in that context, the simpler syntax
and functionality makes it easier to translate than other built-in
string formatting facilities in Python.  As an example of a library
built on template strings for i18n, see the flufl.i18n(2) package.

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: 1fc. being raised.

The *note string: f7. module provides a *note Template: 3f0. class that
implements these rules.  The methods of *note Template: 3f0. are:

 -- 類別: string.Template (template)

     The constructor takes a single argument which is the template
     string.

      -- 成員函式: substitute (mapping={}, /, **kwds)

          Performs the template substitution, returning a new string.
          `mapping' is any dictionary-like object with keys that match
          the placeholders in the template.  Alternatively, you can
          provide keyword arguments, where the keywords are the
          placeholders.  When both `mapping' and `kwds' are given and
          there are duplicates, the placeholders from `kwds' take
          precedence.

      -- 成員函式: safe_substitute (mapping={}, /, **kwds)

          Like *note substitute(): 1304, except that if placeholders are
          missing from `mapping' and `kwds', instead of raising a *note
          KeyError: 2c8. exception, the original placeholder will appear
          in the resulting string intact.  Also, unlike with *note
          substitute(): 1304, any other appearances of the ‘$’ will
          simply return ‘$’ instead of raising *note ValueError: 1fc.

          While other exceptions may still occur, this method is called
          "safe" because it always tries to return a usable string
          instead of raising an exception.  In another sense, *note
          safe_substitute(): 1305. may be anything other than safe,
          since it will silently ignore malformed templates containing
          dangling delimiters, unmatched braces, or placeholders that
          are not valid Python identifiers.

     *note Template: 3f0. instances also provide one public data
     attribute:

      -- 屬性: template

          This is the object passed to the constructor’s `template'
          argument.  In general, you shouldn’t change it, but read-only
          access is not enforced.

Here is an example of how to use a 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'

Advanced usage: you can derive subclasses of *note Template: 3f0. to
customize the placeholder syntax, delimiter character, or the entire
regular expression used to parse template strings.  To do this, you can
override these class attributes:

   * `delimiter' – This is the literal string describing a placeholder
     introducing delimiter.  The default value is ‘$’.  Note that this
     should `not' be a regular expression, as the implementation will
     call *note re.escape(): 49a. on this string as needed.  Note
     further that you cannot change the delimiter after class creation
     (i.e.  a different delimiter must be set in the subclass’s class
     namespace).

   * `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' – This group matches the escape sequence, e.g.  ‘$$’, in
     the default pattern.

   * `named' – This group matches the unbraced placeholder name; it
     should not include the delimiter in capturing group.

   * `braced' – This group matches the brace enclosed placeholder name;
     it should not include either the delimiter or braces in the
     capturing group.

   * `invalid' – This group matches any other delimiter pattern (usually
     a single delimiter), and it should appear last in the regular
     expression.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0292

   (2) http://flufli18n.readthedocs.io/en/latest/


File: python.info,  Node: Helper functions,  Prev: Template strings,  Up: string --- Common string operations

5.6.1.7 Helper functions
........................

 -- 函式: string.capwords (s, sep=None)

     Split the argument into words using *note str.split(): 7a6,
     capitalize each word using *note str.capitalize(): 1647, and join
     the capitalized words using *note str.join(): 1637.  If the
     optional second argument `sep' is absent or ‘None’, runs of
     whitespace characters are replaced by a single space and leading
     and trailing whitespace are removed, otherwise `sep' is used to
     split and join the words.


File: python.info,  Node: re --- Regular expression operations,  Next: difflib --- Helpers for computing deltas,  Prev: string --- Common string operations,  Up: Text Processing Services

5.6.2 ‘re’ — Regular expression operations
------------------------------------------

`Source code:' Lib/re.py(1)

__________________________________________________________________

This module provides regular expression matching operations similar to
those found in Perl.

Both patterns and strings to be searched can be Unicode strings (*note
str: 335.) as well as 8-bit strings (*note bytes: 336.).  However,
Unicode strings and 8-bit strings cannot be mixed: that is, you cannot
match a Unicode string with a byte pattern or vice-versa; similarly,
when asking for a substitution, the replacement string must be of the
same type as both the pattern and the search string.

Regular expressions use the backslash character (‘'\'’) to indicate
special forms or to allow special characters to be used without invoking
their special meaning.  This collides with Python’s usage of the same
character for the same purpose in string literals; for example, to match
a literal backslash, one might have to write ‘'\\\\'’ as the pattern
string, because the regular expression must be ‘\\’, and each backslash
must be expressed as ‘\\’ inside a regular Python string literal.  Also,
please note that any invalid escape sequences in Python’s usage of the
backslash in string literals now generate a *note DeprecationWarning:
279. and in the future this will become a *note SyntaxError: 45d.  This
behaviour will happen even if it is a valid escape sequence for a
regular expression.

The solution is to use Python’s raw string notation for regular
expression patterns; 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.  Usually patterns will be expressed in
Python code using this raw string notation.

It is important to note that most regular expression operations are
available as module-level functions and methods on *note compiled
regular expressions: 8a1.  The functions are shortcuts that don’t
require you to compile a regex object first, but miss some fine-tuning
parameters.

也參考
......

The third-party regex(2) module, which has an API compatible with the
standard library *note re: de. module, but offers additional
functionality and a more thorough Unicode support.

* Menu:

* Regular Expression Syntax::
* Module Contents::
* Regular Expression Objects::
* Match Objects::
* Regular Expression Examples::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/re.py

   (2) https://pypi.org/project/regex/


File: python.info,  Node: Regular Expression Syntax,  Next: Module Contents,  Up: re --- Regular expression operations

5.6.2.1 Regular Expression Syntax
.................................

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]: 1754, 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
如何使用正規表達式: 1755.

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 qualifiers (‘*’, ‘+’, ‘?’, ‘{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: 1756. flag has been specified, this
     matches any character including a newline.

‘^’

     (Caret.)  Matches the start of the string, and in *note MULTILINE:
     1757. 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: 1757. 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: 1757. 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 ‘'?'’ qualifiers 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
     qualifier 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>'’.

‘{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 qualifier.  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.

‘\’

     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
          depends on whether *note ASCII: 3cd. or *note LOCALE: 3ce.
          mode is in force.

        * 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 both match a
          parenthesis.

        * 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: 32a. 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: 32a. 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: *note re.A: 1758. (ASCII-only
     matching), *note re.I: 1759. (ignore case), *note re.L: 175a.
     (locale dependent), *note re.M: 175b. (multi-line), *note re.S:
     175c. (dot matches all), ‘re.U’ (Unicode matching), and *note re.X:
     175d. (verbose), for the entire regular expression.  (The flags are
     described in *note Module Contents: 175e.)  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():
     44f. function.  Flags should be used first in the expression
     string.

‘(?:...)’

     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: *note re.A: 1758.
     (ASCII-only matching), *note re.I: 1759. (ignore case), *note re.L:
     175a. (locale dependent), *note re.M: 175b. (multi-line), *note
     re.S: 175c. (dot matches all), ‘re.U’ (Unicode matching), and *note
     re.X: 175d. (verbose), for the part of the expression.  (The flags
     are described in *note Module Contents: 175e.)

     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 byte pattern ‘(?L:...)’ switches
     to locale depending 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.

‘(?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 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’
                                                 

‘(?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(): bb7. function rather than
     the *note match(): bb8. 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>'’.

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/end of the string.  This means that ‘r'\bfoo\b'’ matches
     ‘'foo'’, ‘'foo.'’, ‘'(foo)'’, ‘'bar foo baz'’ but not ‘'foobar'’ or
     ‘'foo3'’.

     By default Unicode alphanumerics are the ones used in Unicode
     patterns, but this can be changed by using the *note ASCII: 3cd.
     flag.  Word boundaries are determined by the current locale if the
     *note LOCALE: 3ce. 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'py\B'’ matches
     ‘'python'’, ‘'py3'’, ‘'py2'’, but not ‘'py'’, ‘'py.'’, or ‘'py!'’.
     ‘\B’ is just the opposite of ‘\b’, so word characters in Unicode
     patterns are Unicode alphanumerics or the underscore, although this
     can be changed by using the *note ASCII: 3cd. flag.  Word
     boundaries are determined by the current locale if the *note
     LOCALE: 3ce. flag is used.

‘\d’

     For Unicode (str) patterns:

          Matches any Unicode decimal digit (that is, any character in
          Unicode character category [Nd]).  This includes ‘[0-9]’, and
          also many other digit characters.  If the *note ASCII: 3cd.
          flag is used only ‘[0-9]’ is matched.

     For 8-bit (bytes) patterns:

          Matches any decimal digit; this is equivalent to ‘[0-9]’.

‘\D’

     Matches any character which is not a decimal digit.  This is the
     opposite of ‘\d’.  If the *note ASCII: 3cd. flag is used this
     becomes the equivalent of ‘[^0-9]’.

‘\s’

     For Unicode (str) patterns:

          Matches Unicode whitespace characters (which includes ‘[
          \t\n\r\f\v]’, and also many other characters, for example the
          non-breaking spaces mandated by typography rules in many
          languages).  If the *note ASCII: 3cd. flag is used, only ‘[
          \t\n\r\f\v]’ is matched.

     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’.  If the *note ASCII: 3cd. flag is used this
     becomes the equivalent of ‘[^ \t\n\r\f\v]’.

‘\w’

     For Unicode (str) patterns:

          Matches Unicode word characters; this includes most characters
          that can be part of a word in any language, as well as numbers
          and the underscore.  If the *note ASCII: 3cd. flag is used,
          only ‘[a-zA-Z0-9_]’ is matched.

     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: 3ce. 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’.  If the *note ASCII: 3cd. flag is used this
     becomes the equivalent of ‘[^a-zA-Z0-9_]’.  If the *note LOCALE:
     3ce. 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 standard escapes 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 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/


File: python.info,  Node: Module Contents,  Next: Regular Expression Objects,  Prev: Regular Expression Syntax,  Up: re --- Regular expression operations

5.6.2.2 Module Contents
.......................

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.

3.6 版更變: Flag constants are now instances of ‘RegexFlag’, which is a
subclass of *note enum.IntFlag: 1760.

 -- 函式: re.compile (pattern, flags=0)

     Compile a regular expression pattern into a *note regular
     expression object: 8a1, which can be used for matching using its
     *note match(): 1761, *note search(): 1762. and other methods,
     described below.

     The expression’s behaviour can be modified by specifying a `flags'
     value.  Values can be any of the following variables, combined
     using bitwise OR (the ‘|’ operator).

     The sequence

          prog = re.compile(pattern)
          result = prog.match(string)

     is equivalent to

          result = re.match(pattern, string)

     but using *note re.compile(): 44f. 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(): 44f. 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.

 -- Data: re.A
 -- Data: 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 patterns, and is ignored for byte patterns.
     Corresponds to the inline flag ‘(?a)’.

     Note that for backward compatibility, the ‘re.U’ flag still exists
     (as well as its synonym ‘re.UNICODE’ and its embedded counterpart
     ‘(?u)’), but these are redundant in Python 3 since matches are
     Unicode by default for strings (and Unicode matching isn’t allowed
     for bytes).

 -- Data: re.DEBUG

     Display debug information about compiled expression.  No
     corresponding inline flag.

 -- Data: re.I
 -- Data: 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 re.ASCII: 3cd. flag is
     used to disable non-ASCII matches.  The current locale does not
     change the effect of this flag unless the *note re.LOCALE: 3ce.
     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: 1764. 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: 3cd. flag is
     used, only letters ’a’ to ’z’ and ’A’ to ’Z’ are matched.

 -- Data: re.L
 -- Data: 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.  The use of this flag is discouraged 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.  Corresponds
     to the inline flag ‘(?L)’.

     3.6 版更變: *note re.LOCALE: 3ce. can be used only with bytes
     patterns and is not compatible with *note re.ASCII: 3cd.

     3.7 版更變: Compiled regular expression objects with the *note
     re.LOCALE: 3ce. flag no longer depend on the locale at compile
     time.  Only the locale at matching time affects the result of
     matching.

 -- Data: re.M
 -- Data: 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)’.

 -- Data: re.S
 -- Data: 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)’.

 -- Data: re.X
 -- Data: 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<...>’.  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)’.

 -- 函式: 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 object: 8a2.  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.

 -- 函式: 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
     object: 8a2.  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: 1757. mode, *note re.match():
     bb8. 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(): bb7. instead (see also *note search() vs.  match():
     1766.).

 -- 函式: re.fullmatch (pattern, string, flags=0)

     If the whole `string' matches the regular expression `pattern',
     return a corresponding *note match object: 8a2.  Return ‘None’ if
     the string does not match the pattern; note that this is different
     from a zero-length match.

     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.', 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', '...', '', '', '']

     3.1 版更變: Added the optional flags argument.

     3.7 版更變: Added support of splitting on a pattern that could
     match an empty string.

 -- 函式: re.findall (pattern, string, flags=0)

     Return all non-overlapping matches of `pattern' in `string', as a
     list of strings.  The `string' is scanned left-to-right, and
     matches are returned in the order found.  If one or more groups are
     present in the pattern, return a list of groups; this will be a
     list of tuples if the pattern has more than one group.  Empty
     matches are included in the result.

     3.7 版更變: Non-empty matches can now start just after a previous
     empty match.

 -- 函式: re.finditer (pattern, string, flags=0)

     Return an *note iterator: 1040. yielding *note match objects: 8a2.
     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.

     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
     object: 8a2. 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 object: 8a1.

     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.

     3.1 版更變: Added the optional flags argument.

     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.

     3.7 版更變: Empty matches for the pattern are replaced when
     adjacent to a previous non-empty match.

 -- 函式: re.subn (pattern, repl, string, count=0, flags=0)

     Perform the same operation as *note sub(): 480, but return a tuple
     ‘(new_string, number_of_subs_made)’.

     3.1 版更變: Added the optional flags argument.

     3.5 版更變: Unmatched groups are replaced with an empty string.

 -- 函式: 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('http://www.python.org'))
          http://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(): 480. and *note subn(): 739, 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.

 -- 例外: re.error (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 error 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 版更變: Added additional attributes.


File: python.info,  Node: Regular Expression Objects,  Next: Match Objects,  Prev: Module Contents,  Up: re --- Regular expression operations

5.6.2.3 Regular Expression Objects
..................................

Compiled regular expression objects support the following methods and
attributes:

 -- 成員函式: 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 object: 8a2.  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 object:
     8a2.  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(): 1762. 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(): 1762. instead (see also *note search() vs.  match():
     1766.).

 -- 成員函式: Pattern.fullmatch (string[, pos[, endpos]])

     If the whole `string' matches this regular expression, return a
     corresponding *note match object: 8a2.  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(): 1762. 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(): 3cf. function, using the compiled
     pattern.

 -- 成員函式: Pattern.findall (string[, pos[, endpos]])

     Similar to the *note findall(): 968. function, using the compiled
     pattern, but also accepts optional `pos' and `endpos' parameters
     that limit the search region like for *note search(): bb7.

 -- 成員函式: Pattern.finditer (string[, pos[, endpos]])

     Similar to the *note finditer(): 1767. function, using the compiled
     pattern, but also accepts optional `pos' and `endpos' parameters
     that limit the search region like for *note search(): bb7.

 -- 成員函式: Pattern.sub (repl, string, count=0)

     Identical to the *note sub(): 480. function, using the compiled
     pattern.

 -- 成員函式: Pattern.subn (repl, string, count=0)

     Identical to the *note subn(): 739. function, using the compiled
     pattern.

 -- 屬性: Pattern.flags

     The regex matching flags.  This is a combination of the flags given
     to *note compile(): 44f, any ‘(?...)’ inline flags in the pattern,
     and implicit flags such as ‘UNICODE’ 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(): 3d0. and *note
copy.deepcopy(): 3d1.  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 operations

5.6.2.4 Match Objects
.....................

Match objects always have a boolean value of ‘True’.  Since *note
match(): 1761. and *note search(): 1762. 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)

Match objects support the following methods and attributes:

 -- 成員函式: Match.expand (template)

     Return the string obtained by doing backslash substitution on the
     template string `template', as done by the *note sub(): 176e.
     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.

     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: e7a. 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: e7a. 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'

     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’.

     For example:

          >>> 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:
     e7a. 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(): 1762. or
     *note match(): 1761. method of a *note regex object: 8a1.  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(): 1762.
     or *note match(): 1761. method of a *note regex object: 8a1.  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: 8a1. whose *note match():
     1761. or *note search(): 1762. method produced this match instance.

 -- 屬性: Match.string

     The string passed to *note match(): 1761. or *note search(): 1762.

3.7 版更變: Added support of *note copy.copy(): 3d0. and *note
copy.deepcopy(): 3d1.  Match objects are considered atomic.


File: python.info,  Node: Regular Expression Examples,  Prev: Match Objects,  Up: re --- Regular expression operations

5.6.2.5 Regular Expression Examples
...................................

* Menu:

* Checking for a Pair::
* Simulating scanf(): Simulating 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: Simulating scanf,  Up: Regular Expression Examples

5.6.2.6 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(): 1776. 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: Simulating scanf,  Next: search vs match,  Prev: Checking for a Pair,  Up: Regular Expression Examples

5.6.2.7 Simulating 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: Simulating scanf,  Up: Regular Expression Examples

5.6.2.8 search() vs. match()
............................

Python offers two different primitive operations based on regular
expressions: *note re.match(): bb8. checks for a match only at the
beginning of the string, while *note re.search(): bb7. checks for a
match anywhere in the string (this is what Perl does by default).

For example:

     >>> re.match("c", "abcdef")    # No match
     >>> re.search("c", "abcdef")   # Match
     <re.Match object; span=(2, 3), match='c'>

Regular expressions beginning with ‘'^'’ can be used with *note
search(): bb7. 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: 1757. mode *note match(): bb8.
only matches at the beginning of the string, whereas using *note
search(): bb7. 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.9 Making a Phonebook
..........................

*note split(): 3cf. 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(): 3cf. because the address has spaces, our splitting pattern, in
it:

     >>> [re.split(":? ", entry, 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, 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.10 Text Munging
.....................

*note sub(): 480. replaces every occurrence of a pattern with a string
or the result of a function.  This example demonstrates using *note
sub(): 480. 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.11 Finding all Adverbs
............................

*note findall(): 968. matches `all' occurrences of a pattern, not just
the first one as *note search(): bb7. does.  For example, if a writer
wanted to find all of the adverbs in some text, they might use *note
findall(): 968. in the following manner:

     >>> text = "He was carefully disguised but captured quickly by police."
     >>> re.findall(r"\w+ly", 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.12 Finding all Adverbs and their Positions
................................................

If one wants more information about all matches of a pattern than the
matched text, *note finditer(): 1767. is useful as it provides *note
match objects: 8a2. 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(): 1767. in the
following manner:

     >>> text = "He was carefully disguised but captured quickly by police."
     >>> for m in re.finditer(r"\w+ly", 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.13 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.14 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 --- Helpers for computing deltas,  Next: textwrap --- Text wrapping and filling,  Prev: re --- Regular expression operations,  Up: Text Processing Services

5.6.3 ‘difflib’ — Helpers for computing deltas
----------------------------------------------

`Source code:' 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: 7f. 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: 142e.
     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: 954. 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: 954. 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: 954.

     3.2 版新加入: The `autojunk' parameter.

 -- 類別: difflib.Differ

     This is a class for comparing sequences of lines of text, and
     producing human-readable differences or deltas.  Differ uses *note
     SequenceMatcher: 954. both to compare sequences of lines, and to
     compare sequences of characters within similar (near-matching)
     lines.

     Each line of a *note Differ: 178f. delta begins with a two-letter
     code:

     Code           Meaning
                    
     ---------------------------------------------------------------
                    
     ‘'- '’         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 tab characters.

 -- 類別: 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: 1790.

          `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(): 1792. (used by *note HtmlDiff:
          1790. to generate the side by side HTML differences).  See
          *note ndiff(): 1792. 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(): 6ce. method.

     ‘Tools/scripts/diff.py’ is a command-line front-end to this class
     and contains a good example of its use.

 -- 函式: 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: 9a7. 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(): 1795. result in diffs
     that are suitable for use with *note io.IOBase.writelines(): 1796.
     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.

          >>> 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

     See *note A command-line interface to difflib: 1797. for a more
     detailed example.

 -- 函式: 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:
     178f.-style delta (a *note generator: 9a7. 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(): 1799, which filters out lines without visible
     characters, except for at most one pound character (‘'#'’) –
     however the underlying *note SequenceMatcher: 954. 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(): 179a,
     which filters out whitespace characters (a blank or tab; it’s a bad
     idea to include newline in this!).

     ‘Tools/scripts/ndiff.py’ is a command-line front-end to this
     function.

          >>> 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(): 179c. or
     *note ndiff(): 1792, extract lines originating from file 1 or 2
     (parameter `which'), stripping off line prefixes.

     Example:

          >>> 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: 9a7. 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(): 1795. result in
     diffs that are suitable for use with *note io.IOBase.writelines():
     1796. 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.

          >>> 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

     See *note A command-line interface to difflib: 1797. for a more
     detailed example.

 -- 函式: 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(): 179d. or *note context_diff(): 1794.

     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(): 1792. 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(): 1792.

也參考
......

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 Objects::
* SequenceMatcher Examples::
* Differ Objects::
* Differ Example::
* A command-line interface to difflib::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/difflib.py

   (2) 
http://www.drdobbs.com/database/pattern-matching-the-gestalt-approach/184407970

   (3) http://www.drdobbs.com/


File: python.info,  Node: SequenceMatcher Objects,  Next: SequenceMatcher Examples,  Up: difflib --- Helpers for computing deltas

5.6.3.1 SequenceMatcher Objects
...............................

The *note SequenceMatcher: 954. 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: 142e.

     The optional argument `autojunk' can be used to disable the
     automatic junk heuristic.

     3.2 版新加入: The `autojunk' parameter.

     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(): 17a0. or
     *note set_seq2(): 17a1.

     3.2 版新加入: The `bjunk' and `bpopular' attributes.

     *note SequenceMatcher: 954. objects have the following methods:

      -- 成員函式: set_seqs (a, b)

          Set the two sequences to be compared.

     *note SequenceMatcher: 954. computes and caches detailed
     information about the second sequence, so if you want to compare
     one sequence against many sequences, use *note set_seq2(): 17a1. to
     set the commonly used sequence once and call *note set_seq1():
     17a2. 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, ahi, blo, bhi)

          Find longest matching block in ‘a[alo:ahi]’ and ‘b[blo:bhi]’.

          If `isjunk' was omitted or ‘None’, *note find_longest_match():
          17a3. 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: aa8. ‘Match(a, b,
          size)’.

      -- 成員函式: 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               Meaning
                              
          ----------------------------------------------------------------------
                              
          ‘'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).
                              

          For example:

               >>> 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: 9a7. of groups with up to `n' lines
          of context.

          Starting with the groups returned by *note get_opcodes():
          17a5, 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(): 17a5.

      -- 成員函式: 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():
          17a4. or *note get_opcodes(): 17a5. hasn’t already been
          called, in which case you may want to try *note quick_ratio():
          17a8. or *note real_quick_ratio(): 17a9. first to get an upper
          bound.

               備註: Caution: The result of a *note ratio(): 17a7. 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(): 17a7. relatively
          quickly.

      -- 成員函式: real_quick_ratio ()

          Return an upper bound on *note ratio(): 17a7. 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 ‘quick_ratio()’ and ‘real_quick_ratio()’ are always at least as
large as ‘ratio()’:

     >>> 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 Examples,  Next: Differ Objects,  Prev: SequenceMatcher Objects,  Up: difflib --- Helpers for computing deltas

5.6.3.2 SequenceMatcher Examples
................................

This example compares two strings, considering blanks to be "junk":

     >>> s = SequenceMatcher(lambda x: x == " ",
     ...                     "private Thread currentThread;",
     ...                     "private volatile Thread currentThread;")

‘ratio()’ returns a float in [0, 1], measuring the similarity of the
sequences.  As a rule of thumb, a ‘ratio()’ 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,
‘get_matching_blocks()’ 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 ‘get_matching_blocks()’ 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 ‘get_opcodes()’:

     >>> 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(): 1798. function in this module which
     shows how simple code building on *note SequenceMatcher: 954. can
     be used to do useful work.

   * Simple version control recipe(1) for a small application built with
     *note SequenceMatcher: 954.

   ---------- Footnotes ----------

   (1) https://code.activestate.com/recipes/576729/


File: python.info,  Node: Differ Objects,  Next: Differ Example,  Prev: SequenceMatcher Examples,  Up: difflib --- Helpers for computing deltas

5.6.3.3 Differ Objects
......................

Note that *note Differ: 178f.-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: 178f. 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(): 17a3. method’s `isjunk' parameter for an
     explanation.

     *note Differ: 178f. 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(): 1795. method of file-like objects.  The
          delta generated also consists of newline-terminated strings,
          ready to be printed as-is via the *note writelines(): 1796.
          method of a file-like object.


File: python.info,  Node: Differ Example,  Next: A command-line interface to difflib,  Prev: Differ Objects,  Up: difflib --- Helpers for computing deltas

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 ‘readlines()’ 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: 178f. object we may pass
functions to filter out line and character "junk."  See the *note
Differ(): 178f. 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,  Prev: Differ Example,  Up: difflib --- Helpers for computing deltas

5.6.3.5 A command-line interface to difflib
...........................................

This example shows how to use difflib to create a ‘diff’-like utility.
It is also contained in the Python source distribution, as
‘Tools/scripts/diff.py’.

     #!/usr/bin/env python3
     """ 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: textwrap --- Text wrapping and filling,  Next: unicodedata --- Unicode Database,  Prev: difflib --- Helpers for computing deltas,  Up: Text Processing Services

5.6.4 ‘textwrap’ — Text wrapping and filling
--------------------------------------------

`Source code:' Lib/textwrap.py(1)

__________________________________________________________________

The *note textwrap: 109. module provides some convenience functions, as
well as *note TextWrapper: 8ef, 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: 8ef. for efficiency.

 -- 函式: textwrap.wrap (text, width=70, **kwargs)

     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: 8ef, documented below.  `width' defaults to
     ‘70’.

     See the *note TextWrapper.wrap(): 17b4. method for additional
     details on how *note wrap(): 17b3. behaves.

 -- 函式: textwrap.fill (text, width=70, **kwargs)

     Wraps the single paragraph in `text', and returns a single string
     containing the wrapped paragraph.  *note fill(): 17b5. is shorthand
     for

          "\n".join(wrap(text, ...))

     In particular, *note fill(): 17b5. accepts exactly the same keyword
     arguments as *note wrap(): 17b3.

 -- 函式: textwrap.shorten (text, width, **kwargs)

     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: 8ef, documented below.  Note that the whitespace
     is collapsed before the text is passed to the *note TextWrapper:
     8ef. *note fill(): 17b5. function, so changing the value of *note
     tabsize: 17b6, *note expand_tabs: 17b7, *note drop_whitespace:
     17b8, and *note replace_whitespace: 17b9. 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.

     For example:

          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).

     For example:

          >>> 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(): 17b3, *note fill(): 17b5. and *note shorten(): 8f2. work
by creating a *note TextWrapper: 8ef. instance and calling a single
method on it.  That instance is not reused, so for applications that
process many text strings using *note wrap(): 17b3. and/or *note fill():
17b5, it may be more efficient to create your own *note TextWrapper:
8ef. 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: 17bb. is set to false.

 -- 類別: textwrap.TextWrapper (**kwargs)

     The *note TextWrapper: 8ef. 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 re-use the same *note TextWrapper: 8ef. object many times,
     and you can change any of its options through direct assignment to
     instance attributes between uses.

     The *note TextWrapper: 8ef. 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: 17bc, *note TextWrapper: 8ef. guarantees that no
          output line will be longer than *note width: 17bc. characters.

      -- 屬性: expand_tabs

          (default: ‘True’) If true, then all tab characters in `text'
          will be expanded to spaces using the ‘expandtabs()’ method of
          `text'.

      -- 屬性: tabsize

          (default: ‘8’) If *note expand_tabs: 17b7. 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(): 17b3. 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: 17b7. is false and *note
               replace_whitespace: 17b9. is true, each tab character
               will be replaced by a single space, which is `not' the
               same as tab expansion.

               備註: If *note replace_whitespace: 17b9. 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(): 165e. 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: 8ef. 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 is
          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: 17bf. 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:
          17bc. will be broken in order to ensure that no lines are
          longer than *note width: 17bc.  If it is false, long words
          will not be broken, and some lines may be longer than *note
          width: 17bc.  (Long words will be put on a line by themselves,
          in order to minimize the amount by which *note width: 17bc. 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: 17bb. 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: 8ef. 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: 17bc. characters long.  All wrapping
          options are taken from instance attributes of the *note
          TextWrapper: 8ef. 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.8/Lib/textwrap.py


File: python.info,  Node: unicodedata --- Unicode Database,  Next: stringprep --- Internet String Preparation,  Prev: textwrap --- Text wrapping and filling,  Up: Text Processing Services

5.6.5 ‘unicodedata’ — Unicode Database
--------------------------------------

__________________________________________________________________

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 12.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: 2c8. 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: 1fc. 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: 1fc. 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: 1fc. 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: 1fc. 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:

 -- Data: unicodedata.unidata_version

     The version of the Unicode database used in this module.

 -- Data: 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).

Examples:

     >>> 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) http://www.unicode.org/Public/12.1.0/ucd

   (2) https://www.unicode.org/reports/tr44/

   (3) (1) ‘http://www.unicode.org/Public/12.1.0/ucd/NameAliases.txt’

   (4) (2) ‘http://www.unicode.org/Public/12.1.0/ucd/NamedSequences.txt’


File: python.info,  Node: stringprep --- Internet String Preparation,  Next: readline --- GNU readline interface,  Prev: unicodedata --- Unicode Database,  Up: Text Processing Services

5.6.6 ‘stringprep’ — Internet String Preparation
------------------------------------------------

`Source code:' 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: f8. only exposes the tables from RFC
3454(3).  As these tables would be very large to represent them 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: f8. 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.8/Lib/stringprep.py

   (2) https://tools.ietf.org/html/rfc3454.html

   (3) https://tools.ietf.org/html/rfc3454.html


File: python.info,  Node: readline --- GNU readline interface,  Next: rlcompleter --- Completion function for GNU readline,  Prev: stringprep --- Internet String Preparation,  Up: Text Processing Services

5.6.7 ‘readline’ — GNU readline interface
-----------------------------------------

__________________________________________________________________

The *note readline: df. 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: e2. 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(): c70. 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.

     備註: The underlying Readline library API may be implemented by the
     ‘libedit’ library instead of GNU readline.  On macOS the *note
     readline: df. module detects which library is being used at run
     time.

     The configuration file for ‘libedit’ is different from that of GNU
     readline.  If you programmatically load configuration strings you
     can check for the text "libedit" in ‘readline.__doc__’ to
     differentiate between GNU readline and libedit.

     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

* Menu:

* Init file::
* Line buffer::
* History file::
* History list::
* Startup hooks::
* Completion::
* Example::

   ---------- Footnotes ----------

   (1) https://tiswww.cwru.edu/php/chet/readline/rluserman.html#SEC9


File: python.info,  Node: Init file,  Next: Line buffer,  Up: readline --- GNU readline interface

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 interface

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 interface

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(): 17ee. 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 interface

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(): 17ef, 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 implementation detail:' 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 interface

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: Example,  Prev: Startup hooks,  Up: readline --- GNU readline interface

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: e2. to complete Python
identifiers for the interactive interpreter.  If the *note readline: df.
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.

 -- 函式: 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: Example,  Prev: Completion,  Up: readline --- GNU readline interface

5.6.7.7 Example
...............

The following example demonstrates how to use the *note readline: df.
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: 8ea.
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: 8e8. (see *note Readline configuration: 8eb.).

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: 1806.
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 --- Completion function for GNU readline,  Prev: readline --- GNU readline interface,  Up: Text Processing Services

5.6.8 ‘rlcompleter’ — Completion function for GNU readline
----------------------------------------------------------

`Source code:' Lib/rlcompleter.py(1)

__________________________________________________________________

The *note rlcompleter: e2. module defines a completion function suitable
for the *note readline: df. module by completing valid Python
identifiers and keywords.

When this module is imported on a Unix platform with the *note readline:
df. module available, an instance of the ‘Completer’ class is
automatically created and its ‘complete()’ method is set as the *note
readline: df. completer.

Example:

     >>> 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 *note rlcompleter: e2. module is designed for use with Python’s
*note interactive mode: 8e8.  Unless Python is run with the *note -S:
b29. option, the module is automatically imported and configured (see
*note Readline configuration: 8eb.).

On platforms without *note readline: df, the ‘Completer’ class defined
by this module can still be used for custom purposes.

* Menu:

* Completer Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/rlcompleter.py


File: python.info,  Node: Completer Objects,  Up: rlcompleter --- Completion function for GNU readline

5.6.8.1 Completer Objects
.........................

Completer objects have the following method:

 -- 成員函式: Completer.complete (text, state)

     Return the `state'th completion for `text'.

     If called for `text' that doesn’t include a period character
     (‘'.'’), it will complete from names currently defined in *note
     __main__: 1, *note builtins: 13. and keywords (as defined by the
     *note keyword: a7. 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__(): 31f.) up to the last
     part, and find matches for the rest via the *note dir(): d38.
     function.  Any exception raised during the evaluation of the
     expression is caught, silenced and *note None: 158. is returned.


File: python.info,  Node: Binary Data Services,  Next: Data Types,  Prev: Text Processing Services,  Up: Python 標準函式庫 Standard Library

5.7 Binary Data Services
========================

The modules described in this chapter provide some basic services
operations for manipulation of binary data.  Other operations on binary
data, specifically in relation to file formats and network protocols,
are described in the relevant sections.

Some libraries described under *note Text Processing Services: 1646.
also work with either ASCII-compatible binary formats (for example,
*note re: de.) or all binary data (for example, *note difflib: 37.).

In addition, see the documentation for Python’s built-in binary data
types in *note Binary Sequence Types — bytes, bytearray, memoryview:
15ed.

* Menu:

* struct: struct --- Interpret bytes as packed binary data. Interpret bytes as packed binary data
* codecs: codecs --- Codec registry and base classes. Codec registry and base classes


File: python.info,  Node: struct --- Interpret bytes as packed binary data,  Next: codecs --- Codec registry and base classes,  Up: Binary Data Services

5.7.1 ‘struct’ — Interpret bytes as packed binary data
------------------------------------------------------

`Source code:' Lib/struct.py(1)

__________________________________________________________________

This module performs conversions between Python values and C structs
represented as Python *note bytes: 336. objects.  This can be used in
handling binary data stored in files or from network connections, among
other sources.  It uses *note Format Strings: 1810. as compact
descriptions of the layout of the C structs and the intended conversion
to/from Python values.

     備註: By default, the result of packing a given C struct includes
     pad bytes in order to maintain proper alignment for the C types
     involved; similarly, alignment is taken into account when
     unpacking.  This behavior is chosen so that the bytes of a packed
     struct correspond exactly to the layout in memory of the
     corresponding C struct.  To handle platform-independent data
     formats or omit implicit pad bytes, use ‘standard’ size and
     alignment instead of ‘native’ size and alignment: see *note Byte
     Order, Size, and Alignment: 1811. for details.

Several *note struct: f9. functions (and methods of *note Struct: 1812.)
take a `buffer' argument.  This refers to objects that implement the
*note Buffer Protocol: 15ec. and provide either a readable or
read-writable buffer.  The most common types used for that purpose are
*note bytes: 336. and *note bytearray: 337, 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: 336. object.

* Menu:

* Functions and Exceptions::
* Format Strings::
* Classes: Classes<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/struct.py


File: python.info,  Node: Functions and Exceptions,  Next: Format Strings,  Up: struct --- Interpret bytes as packed binary data

5.7.1.1 Functions and Exceptions
................................

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(): 1815.

 -- 函式: 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(): 1815.

 -- 函式: 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():
     1815.

     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: Classes<2>,  Prev: Functions and Exceptions,  Up: struct --- Interpret bytes as packed binary data

5.7.1.2 Format Strings
......................

Format strings are the mechanism used to specify the expected layout
when packing and unpacking data.  They are built up from *note Format
Characters: 1818, which specify the type of data being packed/unpacked.
In addition, there are special characters for controlling the *note Byte
Order, Size, and Alignment: 1811.

* Menu:

* Byte Order, Size, and Alignment: Byte Order Size and Alignment.
* Format Characters::
* Examples: Examples<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).

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.

Native byte order is big-endian or little-endian, depending on the host
system.  For example, Intel x86 and AMD64 (x86-64) are little-endian;
Motorola 68000 and PowerPC G5 are big-endian; ARM and Intel Itanium
feature switchable endianness (bi-endian).  Use ‘sys.byteorder’ 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: 1818. 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 Examples: 181a.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc1700


File: python.info,  Node: Format Characters,  Next: Examples<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
                                            
                                                                                          
‘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
                                            
                                                                                          
‘p’          ‘char[]’                       bytes
                                            
                                                                                          
‘P’          ‘void *’                       integer                                       (5)
                                                                                          

3.3 版更變: Added support for the ‘'n'’ and ‘'N'’ formats.

3.6 版更變: Added support for the ‘'e'’ format.

註解：

  1. 
     The ‘'?'’ conversion code corresponds to the ‘_Bool’ type defined
     by C99.  If this type is not available, it is simulated using a
     ‘char’.  In standard mode, it is always 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__(): 18b.
     method then that method is called to convert the argument to an
     integer before packing.

     3.2 版更變: Use of the *note __index__(): 18b. method for
     non-integers is new in 3.2.

  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.

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.

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, while ‘'10c'’ means
10 characters.  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).

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: cb9. is
raised.

3.1 版更變: In 3.0, some of the integer formats wrapped out-of-range
values and raised *note DeprecationWarning: 279. instead of *note
struct.error: cb9.

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(): c10. 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():
1308, the ‘'p'’ format character consumes ‘count’ bytes, but that the
string returned can never contain more than 255 bytes.

For the ‘'?'’ format character, the return value is either *note True:
49e. or *note False: 38d.  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_floating_point#IEEE_754-2008

   (2) 
https://en.wikipedia.org/wiki/Half-precision_floating-point_format


File: python.info,  Node: Examples<2>,  Prev: Format Characters,  Up: Format Strings

5.7.1.5 Examples
................

     備註: All examples assume a native byte order, size, and alignment
     with a big-endian machine.

A basic example of packing/unpacking three integers:

     >>> from struct import *
     >>> pack('hhl', 1, 2, 3)
     b'\x00\x01\x00\x02\x00\x00\x00\x03'
     >>> unpack('hhl', b'\x00\x01\x00\x02\x00\x00\x00\x03')
     (1, 2, 3)
     >>> calcsize('hhl')
     8

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 since the
padding needed to satisfy alignment requirements is different:

     >>> pack('ci', b'*', 0x12131415)
     b'*\x00\x00\x00\x12\x13\x14\x15'
     >>> pack('ic', 0x12131415, b'*')
     b'\x12\x13\x14\x15*'
     >>> calcsize('ci')
     8
     >>> calcsize('ic')
     5

The following format ‘'llh0l'’ specifies two pad bytes at the end,
assuming 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'

This only works when native size and alignment are in effect; standard
size and alignment does not enforce any alignment.

也參考
......

Module *note array: 7.

     Packed binary storage of homogeneous data.

模組 *note xdrlib: 133.

     Packing and unpacking of XDR data.


File: python.info,  Node: Classes<2>,  Prev: Format Strings,  Up: struct --- Interpret bytes as packed binary data

5.7.1.6 Classes
...............

The *note struct: f9. 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 the
     *note struct: f9. functions with the same format since the format
     string only needs to be compiled once.

          備註: The compiled versions of the most recent format strings
          passed to *note Struct: 1812. and the module-level functions
          are cached, so programs that use only a few format strings
          needn’t worry about reusing a single *note Struct: 1812.
          instance.

     Compiled Struct objects support the following methods and
     attributes:

      -- 成員函式: pack (v1, v2, ...)

          Identical to the *note pack(): c10. function, using the
          compiled format.  (‘len(result)’ will equal *note size: 1820.)

      -- 成員函式: pack_into (buffer, offset, v1, v2, ...)

          Identical to the *note pack_into(): 1814. function, using the
          compiled format.

      -- 成員函式: unpack (buffer)

          Identical to the *note unpack(): 1308. function, using the
          compiled format.  The buffer’s size in bytes must equal *note
          size: 1820.

      -- 成員函式: unpack_from (buffer, offset=0)

          Identical to the *note unpack_from(): 1816. function, using
          the compiled format.  The buffer’s size in bytes, starting at
          position `offset', must be at least *note size: 1820.

      -- 成員函式: iter_unpack (buffer)

          Identical to the *note iter_unpack(): 8dd. function, using the
          compiled format.  The buffer’s size in bytes must be a
          multiple of *note size: 1820.

          3.4 版新加入.

      -- 屬性: format

          The format string used to construct this Struct object.

          3.7 版更變: The format string type is now *note str: 335.
          instead of *note bytes: 336.

      -- 屬性: size

          The calculated size of the struct (and hence of the bytes
          object produced by the *note pack(): c10. method)
          corresponding to *note format: 4e0.


File: python.info,  Node: codecs --- Codec registry and base classes,  Prev: struct --- Interpret bytes as packed binary data,  Up: Binary Data Services

5.7.2 ‘codecs’ — Codec registry and base classes
------------------------------------------------

`Source code:' 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: 1600, which encode text to
bytes, 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 use specifically with
*note text encodings: 1600, or with codecs that encode to *note bytes:
336.

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: 1fc. (or a more codec specific
     subclass, such as *note UnicodeEncodeError: 1fd.).  Refer to *note
     Codec Base Classes: 1827. 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: 1fc. (or a more codec specific
     subclass, such as *note UnicodeDecodeError: 1fe.).  Refer to *note
     Codec Base Classes: 1827. 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: 1828. 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: 1828. object is found, a *note LookupError: 1662.
     is raised.  Otherwise, the *note CodecInfo: 1828. 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(): 182c. and *note decode(): 182d. methods of
          Codec instances (see *note Codec Interface: 182e.).  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: 1831. and *note
          IncrementalDecoder: 1832, 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: 1835. and *note StreamReader: 1836,
          respectively.  Stream codecs can maintain state.

To simplify access to the various codec components, the module provides
these additional functions which use *note lookup(): 1706. for the codec
lookup:

 -- 函式: codecs.getencoder (encoding)

     Look up the codec for the given encoding and return its encoder
     function.

     Raises a *note LookupError: 1662. 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: 1662. 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: 1662. 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: 1662. 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: 1836. class or factory function.

     Raises a *note LookupError: 1662. in case the encoding cannot be
     found.

 -- 函式: codecs.getwriter (encoding)

     Look up the codec for the given encoding and return its *note
     StreamWriter: 1835. class or factory function.

     Raises a *note LookupError: 1662. 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, and return a *note CodecInfo: 1828. object.  In case a
     search function cannot find a given encoding, it should return
     ‘None’.

          備註: Search function registration is not currently
          reversible, which may cause problems in some cases, such as
          unit testing or module reloading.

While the builtin *note open(): 4f5. and the associated *note io: a2.
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: 183e, providing transparent
     encoding/decoding.  The default file mode is ‘'r'’, meaning to open
     the file in read mode.

          備註: 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(): 4f5. 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: 1fc. to be raised in
     case an encoding error occurs.

     `buffering' has the same meaning as for the built-in *note open():
     4f5. function.  It defaults to -1 which means that the default
     buffer size will be used.

 -- 函式: codecs.EncodedFile (file, data_encoding, file_encoding=None,
          errors='strict')

     Return a *note StreamRecoder: fd2. 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: 1fc. 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: 9a7.
     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: 335.
     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: 9a7.
     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: 336.
     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(): 1840.

The module also provides the following constants which are useful for
reading and writing to platform dependent files:

 -- Data: codecs.BOM
 -- Data: codecs.BOM_BE
 -- Data: codecs.BOM_LE
 -- Data: codecs.BOM_UTF8
 -- Data: codecs.BOM_UTF16
 -- Data: codecs.BOM_UTF16_BE
 -- Data: codecs.BOM_UTF16_LE
 -- Data: codecs.BOM_UTF32
 -- Data: codecs.BOM_UTF32_BE
 -- Data: 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: 1846. is either
     *note BOM_UTF16_BE: 1847. or *note BOM_UTF16_LE: 1848. depending on
     the platform’s native byte order, *note BOM: 1842. is an alias for
     *note BOM_UTF16: 1846, *note BOM_LE: 1844. for *note BOM_UTF16_LE:
     1848. and *note BOM_BE: 1843. for *note BOM_UTF16_BE: 1847.  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.8/Lib/codecs.py


File: python.info,  Node: Codec Base Classes,  Next: Encodings and Unicode,  Up: codecs --- Codec registry and base classes

5.7.2.1 Codec Base Classes
..........................

The *note codecs: 1c. 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.  The following string values are defined and implemented by
all standard Python codecs:

Value                         Meaning
                              
----------------------------------------------------------------------------------
                              
‘'strict'’                    Raise *note UnicodeError: c40. (or a subclass);
                              this is the default.  Implemented in
                              *note strict_errors(): 184f.
                              
                              
‘'ignore'’                    Ignore the malformed data and continue without
                              further notice.  Implemented in
                              *note ignore_errors(): 1850.
                              

The following error handlers are only applicable to *note text
encodings: 1600.:

Value                         Meaning
                              
----------------------------------------------------------------------------------
                              
‘'replace'’                   Replace with a suitable replacement marker;
                              Python will use the official ‘U+FFFD’ REPLACEMENT
                              CHARACTER for the built-in codecs on decoding,
                              and ’?’ on encoding.  Implemented in
                              *note replace_errors(): 1851.
                              
                              
‘'xmlcharrefreplace'’         Replace with the appropriate XML character
                              reference (only for encoding).  Implemented in
                              *note xmlcharrefreplace_errors(): 1852.
                              
                              
‘'backslashreplace'’          Replace with backslashed escape sequences.
                              Implemented in
                              *note backslashreplace_errors(): 1853.
                              
                              
‘'namereplace'’               Replace with ‘\N{...}’ escape sequences (only for
                              encoding).  Implemented in
                              *note namereplace_errors(): 1854.
                              
                              
‘'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.)
                              

In addition, the following error handler is specific to the given
codecs:

Value                   Codecs                       Meaning
                                                     
-----------------------------------------------------------------------------------------------------
                                                     
‘'surrogatepass'’       utf-8, utf-16, utf-32,       Allow encoding and decoding of surrogate
                        utf-16-be, utf-16-le,        codes.  These codecs normally treat the
                        utf-32-be, utf-32-le         presence of surrogates as an error.
                                                     

3.1 版新加入: The ‘'surrogateescape'’ and ‘'surrogatepass'’ error
handlers.

3.4 版更變: The ‘'surrogatepass'’ error handlers now works with utf-16*
and utf-32* codecs.

3.5 版新加入: The ‘'namereplace'’ error handler.

3.5 版更變: The ‘'backslashreplace'’ error handlers 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: 1fd. 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: 335. or
     *note bytes: 336.  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: e7a. will be raised.

     Decoding and translating works similarly, except *note
     UnicodeDecodeError: 1fe. or *note UnicodeTranslateError: 171a. 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: 1662. 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: c40.

 -- 函式: codecs.replace_errors (exception)

     Implements the ‘'replace'’ error handling (for *note text
     encodings: 1600. only): substitutes ‘'?'’ for encoding errors (to
     be encoded by the codec), and ‘'\ufffd'’ (the Unicode replacement
     character) for decoding errors.

 -- 函式: codecs.ignore_errors (exception)

     Implements the ‘'ignore'’ error handling: malformed data is ignored
     and encoding or decoding is continued without further notice.

 -- 函式: codecs.xmlcharrefreplace_errors (exception)

     Implements the ‘'xmlcharrefreplace'’ error handling (for encoding
     with *note text encodings: 1600. only): the unencodable character
     is replaced by an appropriate XML character reference.

 -- 函式: codecs.backslashreplace_errors (exception)

     Implements the ‘'backslashreplace'’ error handling (for *note text
     encodings: 1600. only): malformed data is replaced by a backslashed
     escape sequence.

 -- 函式: codecs.namereplace_errors (exception)

     Implements the ‘'namereplace'’ error handling (for encoding with
     *note text encodings: 1600. only): the unencodable character is
     replaced by a ‘\N{...}’ escape sequence.

     3.5 版新加入.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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 ‘Codec’ class defines these methods which also define the
function interfaces of the stateless encoder and decoder:

 -- 成員函式: Codec.encode (input[, errors])

     Encodes the object `input' and returns a tuple (output object,
     length consumed).  For instance, *note text encoding: 1600.
     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 ‘Codec’ instance.  Use *note
     StreamWriter: 1835. 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.

 -- 成員函式: Codec.decode (input[, errors])

     Decodes the object `input' and returns a tuple (output object,
     length consumed).  For instance, for a *note text encoding: 1600,
     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 ‘Codec’ instance.  Use *note
     StreamReader: 1836. 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: 1831. and *note IncrementalDecoder: 1832.
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(): 1857./*note decode(): 1858. 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(): 1857./*note decode():
1858. 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 Objects::
* IncrementalDecoder Objects::


File: python.info,  Node: IncrementalEncoder Objects,  Next: IncrementalDecoder Objects,  Up: Incremental Encoding and Decoding

5.7.2.5 IncrementalEncoder Objects
..................................

The *note IncrementalEncoder: 1831. 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: 1831. 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: 1831. may implement different error
     handling schemes by providing the `errors' keyword argument.  See
     *note Error Handlers: 1366. 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: 1831. object.

      -- 成員函式: encode (object[, final])

          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(): 807. `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(): 185c.


File: python.info,  Node: IncrementalDecoder Objects,  Prev: IncrementalEncoder Objects,  Up: Incremental Encoding and Decoding

5.7.2.6 IncrementalDecoder Objects
..................................

The *note IncrementalDecoder: 1832. 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: 1832. 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: 1832. may implement different error
     handling schemes by providing the `errors' keyword argument.  See
     *note Error Handlers: 1366. 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: 1832. object.

      -- 成員函式: decode (object[, final])

          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(): 808. `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(): 1861.


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: 1835. and *note StreamReader: 1836. 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 Objects::
* StreamReader Objects::
* StreamReaderWriter Objects::
* StreamRecoder Objects::


File: python.info,  Node: StreamWriter Objects,  Next: StreamReader Objects,  Up: Stream Encoding and Decoding

5.7.2.8 StreamWriter Objects
............................

The *note StreamWriter: 1835. class is a subclass of ‘Codec’ 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: 1835. 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: 1835. may implement different error
     handling schemes by providing the `errors' keyword argument.  See
     *note Error Handlers: 1366. 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: 1835. object.

      -- 成員函式: write (object)

          Writes the object’s contents encoded to the stream.

      -- 成員函式: writelines (list)

          Writes the concatenated list of strings to the stream
          (possibly by reusing the *note write(): 1866. method).  The
          standard bytes-to-bytes codecs do not support this method.

      -- 成員函式: reset ()

          Flushes and resets the codec buffers used for keeping 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: 1835. must
also inherit all other methods and attributes from the underlying
stream.


File: python.info,  Node: StreamReader Objects,  Next: StreamReaderWriter Objects,  Prev: StreamWriter Objects,  Up: Stream Encoding and Decoding

5.7.2.9 StreamReader Objects
............................

The *note StreamReader: 1836. class is a subclass of ‘Codec’ 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: 1836. 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: 1836. may implement different error
     handling schemes by providing the `errors' keyword argument.  See
     *note Error Handlers: 1366. 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: 1836. object.

     The set of allowed values for the `errors' argument can be extended
     with *note register_error(): dfa.

      -- 成員函式: read ([size[, chars[, firstline]]])

          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(): 186b. 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[, keepends]])

          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(): 186b. method.

          If `keepends' is false line-endings will be stripped from the
          lines returned.

      -- 成員函式: readlines ([sizehint[, keepends]])

          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():
          808. 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(): 186b. method.

      -- 成員函式: reset ()

          Resets the codec buffers used for keeping 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: 1836. must
also inherit all other methods and attributes from the underlying
stream.


File: python.info,  Node: StreamReaderWriter Objects,  Next: StreamRecoder Objects,  Prev: StreamReader Objects,  Up: Stream Encoding and Decoding

5.7.2.10 StreamReaderWriter Objects
...................................

The *note StreamReaderWriter: 183e. 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(): 1706. function to construct the instance.

 -- 類別: codecs.StreamReaderWriter (stream, Reader, Writer,
          errors='strict')

     Creates a *note StreamReaderWriter: 183e. instance.  `stream' must
     be a file-like object.  `Reader' and `Writer' must be factory
     functions or classes providing the *note StreamReader: 1836. and
     *note StreamWriter: 1835. interface resp.  Error handling is done
     in the same way as defined for the stream readers and writers.

*note StreamReaderWriter: 183e. instances define the combined interfaces
of *note StreamReader: 1836. and *note StreamWriter: 1835. classes.
They inherit all other methods and attributes from the underlying
stream.


File: python.info,  Node: StreamRecoder Objects,  Prev: StreamReaderWriter Objects,  Up: Stream Encoding and Decoding

5.7.2.11 StreamRecoder Objects
..............................

The *note StreamRecoder: fd2. 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(): 1706. function to construct the instance.

 -- 類別: codecs.StreamRecoder (stream, encode, decode, Reader, Writer,
          errors='strict')

     Creates a *note StreamRecoder: fd2. instance which implements a
     two-way conversion: `encode' and `decode' work on the frontend —
     the data visible to code calling ‘read()’ and ‘write()’, 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 ‘Codec’
     interface.  `Reader' and `Writer' must be factory functions or
     classes providing objects of the *note StreamReader: 1836. and
     *note StreamWriter: 1835. interface respectively.

     Error handling is done in the same way as defined for the stream
     readers and writers.

*note StreamRecoder: fd2. instances define the combined interfaces of
*note StreamReader: 1836. and *note StreamWriter: 1835. 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 --- Codec registry and base classes

5.7.2.12 Encodings and Unicode
..............................

Strings are stored internally as sequences of code points in range
‘0x0’–‘0x10FFFF’.  (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: 1600.

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: 1fd.
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 an ‘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 encoding 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 2.5 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://www.python.org/dev/peps/pep-0393


File: python.info,  Node: Standard Encodings,  Next: Python Specific Encodings,  Prev: Encodings and Unicode,  Up: codecs --- Codec registry and base classes

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 implementation detail:' 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                              Languages
                                                           
------------------------------------------------------------------------------------------------
                                                           
ascii                 646, us-ascii                        English
                                                           
                                                           
big5                  big5-tw, csbig5                      Traditional Chinese
                                                           
                                                           
big5hkscs             big5-hkscs, hkscs                    Traditional Chinese
                                                           
                                                           
cp037                 IBM037, IBM039                       English
                                                           
                                                           
cp273                 273, IBM273, csIBM273                German
                                                           
                                                           3.4 版新加入.
                                                           
                                                           
cp424                 EBCDIC-CP-HE, IBM424                 Hebrew
                                                           
                                                           
cp437                 437, IBM437                          English
                                                           
                                                           
cp500                 EBCDIC-CP-BE, EBCDIC-CP-CH, IBM500   Western Europe
                                                           
                                                           
cp720                                                      Arabic
                                                           
                                                           
cp737                                                      Greek
                                                           
                                                           
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                                                      Hebrew
                                                           
                                                           
cp857                 857, IBM857                          Turkish
                                                           
                                                           
cp858                 858, IBM858                          Western Europe
                                                           
                                                           
cp860                 860, IBM860                          Portuguese
                                                           
                                                           
cp861                 861, CP-IS, IBM861                   Icelandic
                                                           
                                                           
cp862                 862, IBM862                          Hebrew
                                                           
                                                           
cp863                 863, IBM863                          Canadian
                                                           
                                                           
cp864                 IBM864                               Arabic
                                                           
                                                           
cp865                 865, IBM865                          Danish, Norwegian
                                                           
                                                           
cp866                 866, IBM866                          Russian
                                                           
                                                           
cp869                 869, CP-GR, IBM869                   Greek
                                                           
                                                           
cp874                                                      Thai
                                                           
                                                           
cp875                                                      Greek
                                                           
                                                           
cp932                 932, ms932, mskanji, ms-kanji        Japanese
                                                           
                                                           
cp949                 949, ms949, uhc                      Korean
                                                           
                                                           
cp950                 950, ms950                           Traditional Chinese
                                                           
                                                           
cp1006                                                     Urdu
                                                           
                                                           
cp1026                ibm1026                              Turkish
                                                           
                                                           
cp1125                1125, ibm1125, cp866u, ruscii        Ukrainian
                                                           
                                                           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                         Greek
                                                           
                                                           
cp1254                windows-1254                         Turkish
                                                           
                                                           
cp1255                windows-1255                         Hebrew
                                                           
                                                           
cp1256                windows-1256                         Arabic
                                                           
                                                           
cp1257                windows-1257                         Baltic languages
                                                           
                                                           
cp1258                windows-1258                         Vietnamese
                                                           
                                                           
euc_jp                eucjp, ujis, u-jis                   Japanese
                                                           
                                                           
euc_jis_2004          jisx0213, eucjis2004                 Japanese
                                                           
                                                           
euc_jisx0213          eucjisx0213                          Japanese
                                                           
                                                           
euc_kr                euckr, korean, ksc5601, ks_c-5601,   Korean
                      ks_c-5601-1987, ksx1001, ks_x-1001   
                      
                                                           
gb2312                chinese, csiso58gb231280, euc-cn,    Simplified Chinese
                      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              Simplified Chinese
                                                           
                                                           
iso2022_jp            csiso2022jp, iso2022jp,              Japanese
                      iso-2022-jp                          
                      
                                                           
iso2022_jp_1          iso2022jp-1, iso-2022-jp-1           Japanese
                                                           
                                                           
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     Japanese
                                                           
                                                           
iso2022_jp_3          iso2022jp-3, iso-2022-jp-3           Japanese
                                                           
                                                           
iso2022_jp_ext        iso2022jp-ext, iso-2022-jp-ext       Japanese
                                                           
                                                           
iso2022_kr            csiso2022kr, iso2022kr,              Korean
                      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                   Arabic
                                                           
                                                           
iso8859_7             iso-8859-7, greek, greek8            Greek
                                                           
                                                           
iso8859_8             iso-8859-8, hebrew                   Hebrew
                                                           
                                                           
iso8859_9             iso-8859-9, latin5, L5               Turkish
                                                           
                                                           
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                       Korean
                                                           
                                                           
koi8_r                                                     Russian
                                                           
                                                           
koi8_t                                                     Tajik
                                                           
                                                           3.5 版新加入.
                                                           
                                                           
koi8_u                                                     Ukrainian
                                                           
                                                           
kz1048                kz_1048, strk1048_2002, rk1048       Kazakh
                                                           
                                                           3.5 版新加入.
                                                           
                                                           
mac_cyrillic          maccyrillic                          Bulgarian, Byelorussian,
                                                           Macedonian, Russian, Serbian
                                                           
                                                           
mac_greek             macgreek                             Greek
                                                           
                                                           
mac_iceland           maciceland                           Icelandic
                                                           
                                                           
mac_latin2            maclatin2, maccentraleurope          Central and Eastern Europe
                                                           
                                                           
mac_roman             macroman, macintosh                  Western Europe
                                                           
                                                           
mac_turkish           macturkish                           Turkish
                                                           
                                                           
ptcp154               csptcp154, pt154, cp154,             Kazakh
                      cyrillic-asian                       
                      
                                                           
shift_jis             csshiftjis, shiftjis, sjis, s_jis    Japanese
                                                           
                                                           
shift_jis_2004        shiftjis2004, sjis_2004, sjis2004    Japanese
                                                           
                                                           
shift_jisx0213        shiftjisx0213, sjisx0213,            Japanese
                      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 --- Codec registry and base classes

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: 335. to *note bytes: 336.
encoding and *note bytes-like object: 5ed. to *note str: 335. decoding,
similar to the Unicode text encodings.

Codec                    Aliases       Meaning
                                       
-----------------------------------------------------------------------
                                       
idna                                   Implement RFC 3490(1), see
                                       also
                                       *note encodings.idna: 77.
                                       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://tools.ietf.org/html/rfc3490.html

   (2) https://tools.ietf.org/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:
5ed. to *note bytes: 336. mappings.  They are not supported by *note
bytes.decode(): c3d. (which only produces *note str: 335. output).

Codec                      Aliases                Meaning                            Encoder / decoder
                                                                                     
------------------------------------------------------------------------------------------------------------------------
                                                                                     
base64_codec (1)           base64, base_64        Convert the operand to multiline   *note base64.encodebytes(): 1879.
                                                  MIME base64 (the result always     /
                                                  includes a trailing ‘'\n'’).       *note base64.decodebytes(): 187a.
                                                                                     
                                                  3.4 版更變: accepts any
                                                  *note bytes-like object: 5ed. as
                                                  input for encoding and decoding
                                                  
                                                                                     
bz2_codec                  bz2                    Compress the operand using bz2.    *note bz2.compress(): 187b. /
                                                                                     *note bz2.decompress(): 9dc.
                                                                                     
                                                                                     
hex_codec                  hex                    Convert the operand to             *note binascii.b2a_hex(): 187c.
                                                  hexadecimal representation, with   /
                                                  two digits per byte.               *note binascii.a2b_hex(): 187d.
                                                                                     
                                                                                     
quopri_codec               quopri,                Convert the operand to MIME        *note quopri.encode(): 187e.
                           quotedprintable,       quoted printable.                  with ‘quotetabs=True’ /
                           quoted_printable                                          *note quopri.decode(): 187f.
                                                                                     
                                                                                     
uu_codec                   uu                     Convert the operand using          *note uu.encode(): 414. /
                                                  uuencode.                          *note uu.decode(): 1880.
                                                                                     
                                                                                     
zlib_codec                 zip, zlib              Compress the operand using gzip.   *note zlib.compress(): 5c3. /
                                                                                     *note zlib.decompress(): 5c4.
                                                                                     

3.2 版新加入: Restoration of the binary transforms.

3.4 版更變: Restoration of the aliases for the binary transforms.

   ---------- Footnotes ----------

   (1) (1) In addition to *note bytes-like objects: 5ed,
‘'base64_codec'’ also accepts ASCII-only instances of *note str: 335.
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: 335. to
*note str: 335. mapping.  It is not supported by *note str.encode():
c3c. (which only produces *note bytes: 336. output).

Codec                    Aliases       Meaning
                                       
-----------------------------------------------------------------------
                                       
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 --- Codec registry and base classes

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: f8.

If you need the IDNA 2008 standard from RFC 5891(3) and RFC 5895(4), use
the third-party ‘idna module <https://pypi.org/project/idna/>_’.

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(5) 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: f0. 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: 94. and *note ftplib: 84, accept Unicode host names (*note
http.client: 94. 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: 77. 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(6).
     ‘UseSTD3ASCIIRules’ is assumed to be false.

 -- 函式: encodings.idna.ToUnicode (label)

     Convert a label to Unicode, as specified in RFC 3490(7).

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc3490.html

   (2) https://tools.ietf.org/html/rfc3492.html

   (3) https://tools.ietf.org/html/rfc5891.html

   (4) https://tools.ietf.org/html/rfc5895.html

   (5) https://tools.ietf.org/html/rfc3490.html#section-3.1

   (6) https://tools.ietf.org/html/rfc3490.html

   (7) https://tools.ietf.org/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 --- Codec registry and base classes

5.7.2.19 ‘encodings.mbcs’ — Windows ANSI codepage
.................................................

This module implements the ANSI codepage (CP_ACP).

*note Availability: 1364.: Windows only.

3.3 版更變: Support any error handler.

3.2 版更變: Before 3.2, the `errors' argument was ignored; ‘'replace'’
was always used to encode, and ‘'ignore'’ to decode.


File: python.info,  Node: encodings utf_8_sig --- UTF-8 codec with BOM signature,  Prev: encodings mbcs --- Windows ANSI codepage,  Up: codecs --- Codec registry and base classes

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: Data Types,  Next: 數值與數學模組,  Prev: Binary Data Services,  Up: Python 標準函式庫 Standard Library

5.8 Data Types
==============

The modules described in this chapter provide a variety of specialized
data types such as dates and times, fixed-type arrays, heap queues,
double-ended queues, and enumerations.

Python also provides some built-in data types, in particular, *note
dict: 1b9, *note list: 263, *note set: b74. and *note frozenset: bf3,
and *note tuple: 483.  The *note str: 335. class is used to hold Unicode
strings, and the *note bytes: 336. and *note bytearray: 337. classes are
used to hold binary data.

The following modules are documented in this chapter:

* Menu:

* datetime: datetime --- Basic date and time types. Basic date and time types
* calendar: calendar --- General calendar-related functions. General calendar-related functions
* collections: collections --- 容器資料型態. 容器資料型態
* collections.abc: collections abc --- Abstract Base Classes for Containers. Abstract Base Classes for Containers
* heapq: heapq --- 堆積佇列 heap queue 演算法. 堆積佇列 (heap queue) 演算法
* bisect: bisect --- 陣列二分演算法 Array bisection algorithm. 陣列二分演算法 (Array bisection algorithm)
* array: array --- 高效率的數值型態陣列. 高效率的數值型態陣列
* weakref: weakref --- Weak references. Weak references
* types: types --- Dynamic type creation and names for built-in types. Dynamic type creation and names for built-in types
* copy: copy --- Shallow and deep copy operations. Shallow and deep copy operations
* pprint: pprint --- Data pretty printer. Data pretty printer
* reprlib: reprlib --- Alternate repr implementation. Alternate repr() implementation
* enum: enum --- Support for enumerations. Support for enumerations


File: python.info,  Node: datetime --- Basic date and time types,  Next: calendar --- General calendar-related functions,  Up: Data Types

5.8.1 ‘datetime’ — Basic date and time types
--------------------------------------------

`Source code:' Lib/datetime.py(1)

__________________________________________________________________

The *note datetime: 31. module supplies classes for manipulating dates
and times.

While date and time arithmetic is supported, the focus of the
implementation is on efficient attribute extraction for output
formatting and manipulation.

也參考
......

Module *note calendar: 15.

     General calendar related functions.

Module *note time: 10b.

     Time access and conversions.

Package dateutil(2)

     Third-party library with expanded time zone and parsing support.

* Menu:

* Aware and Naive Objects::
* Constants::
* Available Types::
* timedelta Objects::
* date Objects::
* datetime Objects::
* time Objects::
* tzinfo Objects::
* timezone Objects::
* strftime() and strptime() Behavior: strftime and strptime Behavior.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/datetime.py

   (2) https://dateutil.readthedocs.io/en/stable/


File: python.info,  Node: Aware and Naive Objects,  Next: Constants,  Up: datetime --- Basic date and time types

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 timezone 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 timezone 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: 195. and *note
time: 4f8. objects have an optional time zone information attribute,
‘tzinfo’, that can be set to an instance of a subclass of the abstract
*note tzinfo: 385. class.  These *note tzinfo: 385. 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: 385. class, the *note timezone: a06.
class, is supplied by the *note datetime: 31. module.  The *note
timezone: a06. class can represent simple timezones with fixed offsets
from UTC, such as UTC itself or North American EST and EDT timezones.
Supporting timezones 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) (1) If, that is, we ignore the effects of Relativity


File: python.info,  Node: Constants,  Next: Available Types,  Prev: Aware and Naive Objects,  Up: datetime --- Basic date and time types

5.8.1.2 Constants
.................

The *note datetime: 31. module exports the following constants:

 -- Data: datetime.MINYEAR

     The smallest year number allowed in a *note date: 194. or *note
     datetime: 195. object.  *note MINYEAR: 1890. is ‘1’.

 -- Data: datetime.MAXYEAR

     The largest year number allowed in a *note date: 194. or *note
     datetime: 195. object.  *note MAXYEAR: 1891. is ‘9999’.


File: python.info,  Node: Available Types,  Next: timedelta Objects,  Prev: Constants,  Up: datetime --- Basic date and time types

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:
     1893, *note month: 1894, and *note day: 1895.

 -- 類別: 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: 1896, *note minute:
     1897, *note second: 1898, *note microsecond: 1899, and *note
     tzinfo: 189a.

 -- 類別: datetime.datetime

     A combination of a date and a time.  Attributes: *note year: 189b,
     *note month: 189c, *note day: 189d, *note hour: 189e, *note minute:
     189f, *note second: 18a0, *note microsecond: 18a1, and *note
     tzinfo: 18a2.

 -- 類別: datetime.timedelta

     A duration expressing the difference between two *note date: 194,
     *note time: 4f8, or *note datetime: 195. instances to microsecond
     resolution.

 -- 類別: datetime.tzinfo

     An abstract base class for time zone information objects.  These
     are used by the *note datetime: 195. and *note time: 4f8. 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: 385. 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:

* Common Properties::
* Determining if an Object is Aware or Naive::


File: python.info,  Node: Common Properties,  Next: Determining if an Object is Aware or Naive,  Up: Available Types

5.8.1.4 Common Properties
.........................

The *note date: 194, *note datetime: 195, *note time: 4f8, and *note
timezone: a06. types share these common features:

   - Objects of these types are immutable.

   - Objects of these types are hashable, meaning that they can be used
     as dictionary keys.

   - Objects of these types support efficient pickling via the *note
     pickle: cb. module.


File: python.info,  Node: Determining if an Object is Aware or Naive,  Prev: Common Properties,  Up: Available Types

5.8.1.5 Determining if an Object is Aware or Naive
..................................................

Objects of the *note date: 194. type are always naive.

An object of type *note time: 4f8. or *note datetime: 195. may be aware
or naive.

A *note datetime: 195. object `d' is aware if both of the following
hold:

  1. ‘d.tzinfo’ is not ‘None’

  2. ‘d.tzinfo.utcoffset(d)’ does not return ‘None’

Otherwise, `d' is naive.

A *note time: 4f8. object `t' is aware if both of the following hold:

  1. ‘t.tzinfo’ is not ‘None’

  2. ‘t.tzinfo.utcoffset(None)’ does not return ‘None’.

Otherwise, `t' is naive.

The distinction between aware and naive doesn’t apply to *note
timedelta: 196. objects.


File: python.info,  Node: timedelta Objects,  Next: date Objects,  Prev: Available Types,  Up: datetime --- Basic date and time types

5.8.1.6 ‘timedelta’ Objects
...........................

A *note timedelta: 196. object represents a duration, the difference
between two dates or times.

 -- 類別: 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:

        * A millisecond is converted to 1000 microseconds.

        * A minute is converted to 60 seconds.

        * An hour is converted to 3600 seconds.

        * A week is converted to 7 days.

     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: 965. 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)

Class attributes:

 -- 屬性: timedelta.min

     The most negative *note timedelta: 196. object,
     ‘timedelta(-999999999)’.

 -- 屬性: timedelta.max

     The most positive *note timedelta: 196. object,
     ‘timedelta(days=999999999, hours=23, minutes=59, seconds=59,
     microseconds=999999)’.

 -- 屬性: timedelta.resolution

     The smallest possible difference between non-equal *note timedelta:
     196. objects, ‘timedelta(microseconds=1)’.

Note that, because of normalization, ‘timedelta.max’ > ‘-timedelta.min’.
‘-timedelta.max’ is not representable as a *note timedelta: 196. object.

Instance attributes (read-only):

Attribute              Value
                       
------------------------------------------------------------------------
                       
‘days’                 Between -999999999 and 999999999 inclusive
                       
                       
‘seconds’              Between 0 and 86399 inclusive
                       
                       
‘microseconds’         Between 0 and 999999 inclusive
                       

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: 188. 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: 196. 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: 196. object.
                                     
                                     
‘+t1’                                Returns a *note timedelta: 196. object with the
                                     same value.  (2)
                                     
                                     
‘-t1’                                equivalent to *note timedelta: 196.(-`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: 196. object as a constructor
                                     call with canonical attribute values.
                                     

註解：

  1. This is exact but may overflow.

  2. This is exact and cannot overflow.

  3. Division by 0 raises *note ZeroDivisionError: 12b2.

  4. -`timedelta.max' is not representable as a *note timedelta: 196.
     object.

  5. String representations of *note timedelta: 196. 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: 196.
objects support certain additions and subtractions with *note date: 194.
and *note datetime: 195. objects (see below).

3.2 版更變: Floor division and true division of a *note timedelta: 196.
object by another *note timedelta: 196. object are now supported, as are
remainder operations and the *note divmod(): 153. function.  True
division and multiplication of a *note timedelta: 196. object by a *note
float: 188. object are now supported.

Comparisons of *note timedelta: 196. objects are supported, with some
caveats.

The comparisons ‘==’ or ‘!=’ `always' return a *note bool: 184, no
matter the type of the compared object:

     >>> from datetime import timedelta
     >>> delta1 = timedelta(seconds=57)
     >>> delta2 = timedelta(hours=25, seconds=2)
     >>> delta2 != delta1
     True
     >>> delta2 == 5
     False

For all other comparisons (such as ‘<’ and ‘>’), when a *note timedelta:
196. object is compared to an object of a different type, *note
TypeError: 193. is raised:

     >>> delta2 > delta1
     True
     >>> delta2 > 5
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     TypeError: '>' not supported between instances of 'datetime.timedelta' and 'int'

In Boolean contexts, a *note timedelta: 196. object is considered to be
true if and only if it isn’t equal to ‘timedelta(0)’.

Instance methods:

 -- 成員函式: 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:

* Examples of usage; timedelta: Examples of usage timedelta.


File: python.info,  Node: Examples of usage timedelta,  Up: timedelta Objects

5.8.1.7 Examples of usage: ‘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: 196. 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 Objects,  Next: datetime Objects,  Prev: timedelta Objects,  Up: datetime --- Basic date and time types

5.8.1.8 ‘date’ Objects
......................

A *note date: 194. 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:
     1fc. is raised.

Other constructors, all class methods:

 -- 成員函式: classmethod date.today ()

     Return the current local date.

     This is equivalent to ‘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(): 322.

     This may raise *note OverflowError: 965, if the timestamp is out of
     the range of values supported by the platform C ‘localtime()’
     function, and *note OSError: 1d4. 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(): 18ae.

     3.3 版更變: Raise *note OverflowError: 965. instead of *note
     ValueError: 1fc. if the timestamp is out of the range of values
     supported by the platform C ‘localtime()’ function.  Raise *note
     OSError: 1d4. instead of *note ValueError: 1fc. 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: 1fc. 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: 194. corresponding to a `date_string' given in
     the format ‘YYYY-MM-DD’:

          >>> from datetime import date
          >>> date.fromisoformat('2019-12-04')
          datetime.date(2019, 12, 4)

     This is the inverse of *note date.isoformat(): 18b0.  It only
     supports the format ‘YYYY-MM-DD’.

     3.7 版新加入.

 -- 成員函式: classmethod date.fromisocalendar (year, week, day)

     Return a *note date: 194. corresponding to the ISO calendar date
     specified by year, week and day.  This is the inverse of the
     function *note date.isocalendar(): 18b1.

     3.8 版新加入.

Class attributes:

 -- 屬性: 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: 1890. and *note MAXYEAR: 1891. inclusive.

 -- 屬性: date.month

     Between 1 and 12 inclusive.

 -- 屬性: 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' is ‘timedelta.days’ days removed from
                                    `date1'.  (1)
                                    
                                    
‘date2 = date1 - timedelta’         Computes `date2' such that ‘date2 + timedelta ==
                                    date1’.  (2)
                                    
                                    
‘timedelta = date1 - date2’         (3)
                                    
                                    
‘date1 < date2’                     `date1' is considered less than `date2' when
                                    `date1' precedes `date2' in time.  (4)
                                    

註解：

  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: 965. is raised if ‘date2.year’
     would be smaller than *note MINYEAR: 1890. or larger than *note
     MAXYEAR: 1891.

  2. ‘timedelta.seconds’ and ‘timedelta.microseconds’ are ignored.

  3. This is exact, and cannot overflow.  timedelta.seconds and
     timedelta.microseconds are 0, and date2 + timedelta == date1 after.

  4. In other words, ‘date1 < date2’ if and only if ‘date1.toordinal() <
     date2.toordinal()’.  Date comparison raises *note TypeError: 193.
     if the other comparand isn’t also a *note date: 194. object.
     However, ‘NotImplemented’ is returned instead if the other
     comparand has a ‘timetuple()’ attribute.  This hook gives other
     kinds of date objects a chance at implementing mixed-type
     comparison.  If not, when a *note date: 194. object is compared to
     an object of a different type, *note TypeError: 193. is raised
     unless the comparison is ‘==’ or ‘!=’.  The latter cases return
     *note False: 38d. or *note True: 49e, respectively.

In Boolean contexts, all *note date: 194. objects are considered to be
true.

Instance methods:

 -- 成員函式: 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.

     Example:

          >>> from datetime import date
          >>> d = date(2002, 12, 31)
          >>> d.replace(day=26)
          datetime.date(2002, 12, 26)

 -- 成員函式: date.timetuple ()

     Return a *note time.struct_time: 59e. such as returned by *note
     time.localtime(): f52.

     The hours, minutes and seconds are 0, and the DST flag is -1.

     ‘d.timetuple()’ is equivalent to:

          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: 194. object `d',
     ‘date.fromordinal(d.toordinal()) == d’.

 -- 成員函式: date.weekday ()

     Return the day of the week as an integer, where Monday is 0 and
     Sunday is 6.  For example, ‘date(2002, 12, 4).weekday() == 2’, a
     Wednesday.  See also *note isoweekday(): 18b9.

 -- 成員函式: 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(): 18b8, *note isocalendar():
     18b1.

 -- 成員函式: date.isocalendar ()

     Return a 3-tuple, (ISO year, ISO week number, ISO 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()
          (2004, 1, 1)
          >>> date(2004, 1, 4).isocalendar()
          (2004, 1, 7)

 -- 成員函式: date.isoformat ()

     Return a string representing the date in ISO 8601 format,
     ‘YYYY-MM-DD’:

          >>> from datetime import date
          >>> date(2002, 12, 4).isoformat()
          '2002-12-04'

     This is the inverse of *note date.fromisoformat(): 109c.

 -- 成員函式: 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()’ is equivalent to:

          time.ctime(time.mktime(d.timetuple()))

     on platforms where the native C ‘ctime()’ function (which *note
     time.ctime(): 18bc. invokes, but which *note date.ctime(): 18bb.
     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.  For a complete list of formatting directives,
     see *note strftime() and strptime() Behavior: 18bd.

 -- 成員函式: date.__format__ (format)

     Same as *note date.strftime(): 53d.  This makes it possible to
     specify a format string for a *note date: 194. object in *note
     formatted string literals: 15d. and when using *note str.format():
     4df.  For a complete list of formatting directives, see *note
     strftime() and strptime() Behavior: 18bd.

* Menu:

* Examples of Usage; date: Examples of Usage date.

   ---------- Footnotes ----------

   (1) (2) 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) (3) See R. H. van Gent’s guide to the mathematics of the ISO 8601
calendar
(https://www.staff.science.uu.nl/~gent0113/calendar/isocalendar.htm) for
a good explanation.


File: python.info,  Node: Examples of Usage date,  Up: date Objects

5.8.1.9 Examples of Usage: ‘date’
.................................

Example of counting days to an event:

     >>> 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

More examples of working with *note date: 194.:

     >>> 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 Objects,  Next: time Objects,  Prev: date Objects,  Up: datetime --- Basic date and time types

5.8.1.10 ‘datetime’ Objects
...........................

A *note datetime: 195. object is a single object containing all the
information from a *note date: 194. object and a *note time: 4f8.
object.

Like a *note date: 194. object, *note datetime: 195. assumes the current
Gregorian calendar extended in both directions; like a *note time: 4f8.
object, *note datetime: 195. 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: 385. 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:
     1fc. is raised.

     3.6 版新加入: Added the ‘fold’ argument.

Other constructors, all class methods:

 -- 成員函式: classmethod datetime.today ()

     Return the current local datetime, with *note tzinfo: 18a2. ‘None’.

     Equivalent to:

          datetime.fromtimestamp(time.time())

     See also *note now(): 1005, *note fromtimestamp(): 1090.

     This method is functionally equivalent to *note now(): 1005, but
     without a ‘tz’ parameter.

 -- 成員函式: classmethod datetime.now (tz=None)

     Return the current local date and time.

     If optional argument `tz' is ‘None’ or not specified, this is like
     *note today(): 18c2, but, if possible, supplies more precision than
     can be gotten from going through a *note time.time(): 322.
     timestamp (for example, this may be possible on platforms supplying
     the C ‘gettimeofday()’ function).

     If `tz' is not ‘None’, it must be an instance of a *note tzinfo:
     385. subclass, and the current date and time are converted to
     `tz'’s time zone.

     This function is preferred over *note today(): 18c2. and *note
     utcnow(): 18c3.

 -- 成員函式: classmethod datetime.utcnow ()

     Return the current UTC date and time, with *note tzinfo: 18a2.
     ‘None’.

     This is like *note now(): 1005, but returns the current UTC date
     and time, as a naive *note datetime: 195. object.  An aware current
     UTC datetime can be obtained by calling
     ‘datetime.now(timezone.utc)’.  See also *note now(): 1005.

          警告: 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)’.

 -- 成員函式: 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(): 322.  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: 195. object is naive.

     If `tz' is not ‘None’, it must be an instance of a *note tzinfo:
     385. subclass, and the timestamp is converted to `tz'’s time zone.

     *note fromtimestamp(): 1090. may raise *note OverflowError: 965, if
     the timestamp is out of the range of values supported by the
     platform C ‘localtime()’ or ‘gmtime()’ functions, and *note
     OSError: 1d4. 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(): 1090,
     and then it’s possible to have two timestamps differing by a second
     that yield identical *note datetime: 195. objects.  This method is
     preferred over *note utcfromtimestamp(): 18c4.

     3.3 版更變: Raise *note OverflowError: 965. instead of *note
     ValueError: 1fc. if the timestamp is out of the range of values
     supported by the platform C ‘localtime()’ or ‘gmtime()’ functions.
     Raise *note OSError: 1d4. instead of *note ValueError: 1fc. on
     ‘localtime()’ or ‘gmtime()’ failure.

     3.6 版更變: *note fromtimestamp(): 1090. may return instances with
     *note fold: 4f9. set to 1.

 -- 成員函式: classmethod datetime.utcfromtimestamp (timestamp)

     Return the UTC *note datetime: 195. corresponding to the POSIX
     timestamp, with *note tzinfo: 18a2. ‘None’.  (The resulting object
     is naive.)

     This may raise *note OverflowError: 965, if the timestamp is out of
     the range of values supported by the platform C ‘gmtime()’
     function, and *note OSError: 1d4. on ‘gmtime()’ failure.  It’s
     common for this to be restricted to years in 1970 through 2038.

     To get an aware *note datetime: 195. object, call *note
     fromtimestamp(): 1090.:

          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: 1890. and *note MAXYEAR: 1891. 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: 965. instead of *note
     ValueError: 1fc. if the timestamp is out of the range of values
     supported by the platform C ‘gmtime()’ function.  Raise *note
     OSError: 1d4. instead of *note ValueError: 1fc. on ‘gmtime()’
     failure.

 -- 成員函式: classmethod datetime.fromordinal (ordinal)

     Return the *note datetime: 195. corresponding to the proleptic
     Gregorian ordinal, where January 1 of year 1 has ordinal 1.  *note
     ValueError: 1fc. is raised unless ‘1 <= ordinal <=
     datetime.max.toordinal()’.  The hour, minute, second and
     microsecond of the result are all 0, and *note tzinfo: 18a2. is
     ‘None’.

 -- 成員函式: classmethod datetime.combine (date, time,
          tzinfo=self.tzinfo)

     Return a new *note datetime: 195. object whose date components are
     equal to the given *note date: 194. object’s, and whose time
     components are equal to the given *note time: 4f8. object’s.  If
     the `tzinfo' argument is provided, its value is used to set the
     *note tzinfo: 18a2. attribute of the result, otherwise the *note
     tzinfo: 189a. attribute of the `time' argument is used.

     For any *note datetime: 195. object `d', ‘d ==
     datetime.combine(d.date(), d.time(), d.tzinfo)’.  If date is a
     *note datetime: 195. object, its time components and *note tzinfo:
     18a2. attributes are ignored.

     3.6 版更變: Added the `tzinfo' argument.

 -- 成員函式: classmethod datetime.fromisoformat (date_string)

     Return a *note datetime: 195. corresponding to a `date_string' in
     one of the formats emitted by *note date.isoformat(): 18b0. and
     *note datetime.isoformat(): 384.

     Specifically, this function supports strings in the format:

          YYYY-MM-DD[*HH[:MM[:SS[.fff[fff]]]][+HH:MM[:SS[.ffffff]]]]

     where ‘*’ can match any single character.

          警示: This does `not' support parsing arbitrary ISO 8601
          strings - it is only intended as the inverse operation of
          *note datetime.isoformat(): 384.  A more full-featured ISO
          8601 parser, ‘dateutil.parser.isoparse’ is available in the
          third-party package dateutil(1).

     Examples:

          >>> from datetime import datetime
          >>> datetime.fromisoformat('2011-11-04')
          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-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 版新加入.

 -- 成員函式: classmethod datetime.fromisocalendar (year, week, day)

     Return a *note datetime: 195. 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(): 18c6.

     3.8 版新加入.

 -- 成員函式: classmethod datetime.strptime (date_string, format)

     Return a *note datetime: 195. corresponding to `date_string',
     parsed according to `format'.

     This is equivalent to:

          datetime(*(time.strptime(date_string, format)[0:6]))

     *note ValueError: 1fc. is raised if the date_string and format
     can’t be parsed by *note time.strptime(): d96. or if it returns a
     value which isn’t a time tuple.  For a complete list of formatting
     directives, see *note strftime() and strptime() Behavior: 18bd.

Class attributes:

 -- 屬性: datetime.min

     The earliest representable *note datetime: 195, ‘datetime(MINYEAR,
     1, 1, tzinfo=None)’.

 -- 屬性: datetime.max

     The latest representable *note datetime: 195, ‘datetime(MAXYEAR,
     12, 31, 23, 59, 59, 999999, tzinfo=None)’.

 -- 屬性: datetime.resolution

     The smallest possible difference between non-equal *note datetime:
     195. objects, ‘timedelta(microseconds=1)’.

Instance attributes (read-only):

 -- 屬性: datetime.year

     Between *note MINYEAR: 1890. and *note MAXYEAR: 1891. inclusive.

 -- 屬性: datetime.month

     Between 1 and 12 inclusive.

 -- 屬性: 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:
     195. 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 value 0 (1)
     represents the earlier (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’                     Compares *note datetime: 195. to
                                            *note datetime: 195.  (4)
                                            

  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: 18a2.
     attribute as the input datetime, and datetime2 - datetime1 ==
     timedelta after.  *note OverflowError: 965. is raised if
     datetime2.year would be smaller than *note MINYEAR: 1890. or larger
     than *note MAXYEAR: 1891.  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:
     18a2. attribute as the input datetime, and no time zone adjustments
     are done even if the input is aware.

  3. Subtraction of a *note datetime: 195. from a *note datetime: 195.
     is defined only if both operands are naive, or if both are aware.
     If one is aware and the other is naive, *note TypeError: 193. is
     raised.

     If both are naive, or both are aware and have the same *note
     tzinfo: 18a2. attribute, the *note tzinfo: 18a2. attributes are
     ignored, and the result is a *note timedelta: 196. 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: 18a2.
     attributes, ‘a-b’ acts as if `a' and `b' were first converted to
     naive UTC datetimes first.  The result is ‘(a.replace(tzinfo=None)
     - a.utcoffset()) - (b.replace(tzinfo=None) - b.utcoffset())’ except
     that the implementation never overflows.

  4. `datetime1' is considered less than `datetime2' when `datetime1'
     precedes `datetime2' in time.

     If one comparand is naive and the other is aware, *note TypeError:
     193. is raised if an order comparison is attempted.  For equality
     comparisons, naive instances are never equal to aware instances.

     If both comparands are aware, and have the same *note tzinfo: 18a2.
     attribute, the common *note tzinfo: 18a2. attribute is ignored and
     the base datetimes are compared.  If both comparands are aware and
     have different *note tzinfo: 18a2. attributes, the comparands are
     first adjusted by subtracting their UTC offsets (obtained from
     ‘self.utcoffset()’).

     3.3 版更變: Equality comparisons between aware and naive *note
     datetime: 195. instances don’t raise *note TypeError: 193.

          備註: In order to stop comparison from falling back to the
          default scheme of comparing object addresses, datetime
          comparison normally raises *note TypeError: 193. if the other
          comparand isn’t also a *note datetime: 195. object.  However,
          ‘NotImplemented’ is returned instead if the other comparand
          has a ‘timetuple()’ attribute.  This hook gives other kinds of
          date objects a chance at implementing mixed-type comparison.
          If not, when a *note datetime: 195. object is compared to an
          object of a different type, *note TypeError: 193. is raised
          unless the comparison is ‘==’ or ‘!=’.  The latter cases
          return *note False: 38d. or *note True: 49e, respectively.

Instance methods:

 -- 成員函式: datetime.date ()

     Return *note date: 194. object with same year, month and day.

 -- 成員函式: datetime.time ()

     Return *note time: 4f8. object with same hour, minute, second,
     microsecond and fold.  *note tzinfo: 18a2. is ‘None’.  See also
     method *note timetz(): 18cc.

     3.6 版更變: The fold value is copied to the returned *note time:
     4f8. object.

 -- 成員函式: datetime.timetz ()

     Return *note time: 4f8. object with same hour, minute, second,
     microsecond, fold, and tzinfo attributes.  See also method *note
     time(): 10b.

     3.6 版更變: The fold value is copied to the returned *note time:
     4f8. 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.

     3.6 版新加入: Added the ‘fold’ argument.

 -- 成員函式: datetime.astimezone (tz=None)

     Return a *note datetime: 195. object with new *note tzinfo: 18a2.
     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: 385.
     subclass, and its *note utcoffset(): 18ce. and *note dst(): 18cf.
     methods must not return ‘None’.  If `self' is naive, it is presumed
     to represent time in the system timezone.

     If called without arguments (or with ‘tz=None’) the system local
     timezone is assumed for the target timezone.  The ‘.tzinfo’
     attribute of the converted datetime instance will be set to an
     instance of *note timezone: a06. 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 timezone `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 time zone 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 time
     zone 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(): 18d0. method can be
     overridden in a *note tzinfo: 385. subclass to affect the result
     returned by *note astimezone(): 197.  Ignoring error cases, *note
     astimezone(): 197. acts like:

          def astimezone(self, tz):
              if self.tzinfo is tz:
                  return self
              # Convert self to UTC, and attach the new time zone 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(): 197. method can now be called
     on naive instances that are presumed to represent system local
     time.

 -- 成員函式: datetime.utcoffset ()

     If *note tzinfo: 18a2. 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: 196. 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: 18a2. 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: 196. 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: 18a2. 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 ()

     Return a *note time.struct_time: 59e. such as returned by *note
     time.localtime(): f52.

     ‘d.timetuple()’ is equivalent to:

          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 ‘tm_isdst’ flag of the result is set according to
     the *note dst(): 18cf. method: *note tzinfo: 18a2. is ‘None’ or
     *note dst(): 18cf. returns ‘None’, ‘tm_isdst’ is set to ‘-1’; else
     if *note dst(): 18cf. returns a non-zero value, ‘tm_isdst’ is set
     to ‘1’; else ‘tm_isdst’ is set to ‘0’.

 -- 成員函式: datetime.utctimetuple ()

     If *note datetime: 195. instance `d' is naive, this is the same as
     ‘d.timetuple()’ except that ‘tm_isdst’ 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: 59e. for the
     normalized time is returned.  ‘tm_isdst’ is forced to 0.  Note that
     an *note OverflowError: 965. 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
          ‘utcfromtimetuple’ 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(): 18d2.

 -- 成員函式: 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: 195.
     instance.  The return value is a *note float: 188. similar to that
     returned by *note time.time(): 322.

     Naive *note datetime: 195. instances are assumed to represent local
     time and this method relies on the platform C ‘mktime()’ function
     to perform the conversion.  Since *note datetime: 195. supports
     wider range of values than ‘mktime()’ on many platforms, this
     method may raise *note OverflowError: 965. for times far in the
     past or far in the future.

     For aware *note datetime: 195. instances, the return value is
     computed as:

          (dt - datetime(1970, 1, 1, tzinfo=timezone.utc)).total_seconds()

     3.3 版新加入.

     3.6 版更變: The *note timestamp(): 9e7. method uses the *note fold:
     4f9. attribute to disambiguate the times during a repeated
     interval.

          備註: There is no method to obtain the POSIX timestamp
          directly from a naive *note datetime: 195. instance
          representing UTC time.  If your application uses this
          convention and your system timezone 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(): 18d6.

 -- 成員函式: 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(): 18d5, *note isocalendar(): 18c6.

 -- 成員函式: datetime.isocalendar ()

     Return a 3-tuple, (ISO year, ISO week number, ISO 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’, if *note microsecond: 18a1. is
          not 0

        - ‘YYYY-MM-DDTHH:MM:SS’, if *note microsecond: 18a1. is 0

     If *note utcoffset(): 18ce. does not return ‘None’, a string is
     appended, giving the UTC offset:

        - ‘YYYY-MM-DDTHH:MM:SS.ffffff+HH:MM[:SS[.ffffff]]’, if *note
          microsecond: 18a1. is not 0

        - ‘YYYY-MM-DDTHH:MM:SS+HH:MM[:SS[.ffffff]]’, if *note
          microsecond: 18a1. is 0

     Examples:

          >>> 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: 18a1. is
          0, same as ‘'microseconds'’ otherwise.

        - ‘'hours'’: Include the *note hour: 189e. in the two-digit ‘HH’
          format.

        - ‘'minutes'’: Include *note hour: 189e. and *note minute: 189f.
          in ‘HH:MM’ format.

        - ‘'seconds'’: Include *note hour: 189e, *note minute: 189f, and
          *note second: 18a0. 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: 1fc. 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 版新加入: Added the `timespec' argument.

 -- 成員函式: datetime.__str__ ()

     For a *note datetime: 195. 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()’ is equivalent to:

          time.ctime(time.mktime(d.timetuple()))

     on platforms where the native C ‘ctime()’ function (which *note
     time.ctime(): 18bc. invokes, but which *note datetime.ctime():
     18d8. 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.  For a complete list of formatting
     directives, see *note strftime() and strptime() Behavior: 18bd.

 -- 成員函式: datetime.__format__ (format)

     Same as *note datetime.strftime(): 53c.  This makes it possible to
     specify a format string for a *note datetime: 195. object in *note
     formatted string literals: 15d. and when using *note str.format():
     4df.  For a complete list of formatting directives, see *note
     strftime() and strptime() Behavior: 18bd.

* Menu:

* Examples of Usage; datetime: Examples of Usage datetime.

   ---------- Footnotes ----------

   (1) 
https://dateutil.readthedocs.io/en/stable/parser.html#dateutil.parser.isoparse


File: python.info,  Node: Examples of Usage datetime,  Up: datetime Objects

5.8.1.11 Examples of Usage: ‘datetime’
......................................

Examples of working with *note datetime: 195. objects:

     >>> 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: 385. 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 Objects,  Next: tzinfo Objects,  Prev: datetime Objects,  Up: datetime --- Basic date and time types

5.8.1.12 ‘time’ Objects
.......................

A *note time: 10b. object represents a (local) time of day, independent
of any particular day, and subject to adjustment via a *note tzinfo:
385. 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: 385. 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:
     1fc. is raised.  All default to ‘0’ except `tzinfo', which defaults
     to *note None: 158.

Class attributes:

 -- 屬性: time.min

     The earliest representable *note time: 4f8, ‘time(0, 0, 0, 0)’.

 -- 屬性: time.max

     The latest representable *note time: 4f8, ‘time(23, 59, 59,
     999999)’.

 -- 屬性: time.resolution

     The smallest possible difference between non-equal *note time: 4f8.
     objects, ‘timedelta(microseconds=1)’, although note that arithmetic
     on *note time: 4f8. 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: 4f8.
     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 value 0 (1)
     represents the earlier (later) of the two moments with the same
     wall time representation.

     3.6 版新加入.

*note time: 4f8. objects support comparison of *note time: 4f8. to *note
time: 4f8, where `a' is considered less than `b' when `a' precedes `b'
in time.  If one comparand is naive and the other is aware, *note
TypeError: 193. is raised if an order comparison is attempted.  For
equality comparisons, naive instances are never equal to aware
instances.

If both comparands are aware, and have the same *note tzinfo: 189a.
attribute, the common *note tzinfo: 189a. attribute is ignored and the
base times are compared.  If both comparands are aware and have
different *note tzinfo: 189a. attributes, the comparands are first
adjusted by subtracting their UTC offsets (obtained from
‘self.utcoffset()’).  In order to stop mixed-type comparisons from
falling back to the default comparison by object address, when a *note
time: 4f8. object is compared to an object of a different type, *note
TypeError: 193. is raised unless the comparison is ‘==’ or ‘!=’.  The
latter cases return *note False: 38d. or *note True: 49e, respectively.

3.3 版更變: Equality comparisons between aware and naive *note time:
4f8. instances don’t raise *note TypeError: 193.

In Boolean contexts, a *note time: 4f8. object is always considered to
be true.

3.5 版更變: Before Python 3.5, a *note time: 4f8. 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: 4f8. corresponding to a `time_string' in one
     of the formats emitted by *note time.isoformat(): 18e1.
     Specifically, this function supports strings in the format:

          HH[:MM[:SS[.fff[fff]]]][+HH:MM[:SS[.ffffff]]]

          警示: This does `not' support parsing arbitrary ISO 8601
          strings.  It is only intended as the inverse operation of
          *note time.isoformat(): 18e1.

     Examples:

          >>> from datetime import time
          >>> time.fromisoformat('04:23:01')
          datetime.time(4, 23, 1)
          >>> 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)))

     3.7 版新加入.

Instance methods:

 -- 成員函式: time.replace (hour=self.hour, minute=self.minute,
          second=self.second, microsecond=self.microsecond,
          tzinfo=self.tzinfo, *, fold=0)

     Return a *note time: 4f8. 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: 4f8. from an aware *note time: 4f8, without
     conversion of the time data.

     3.6 版新加入: Added the ‘fold’ argument.

 -- 成員函式: time.isoformat (timespec='auto')

     Return a string representing the time in ISO 8601 format, one of:

        - ‘HH:MM:SS.ffffff’, if *note microsecond: 1899. is not 0

        - ‘HH:MM:SS’, if *note microsecond: 1899. is 0

        - ‘HH:MM:SS.ffffff+HH:MM[:SS[.ffffff]]’, if *note utcoffset():
          18e3. does not return ‘None’

        - ‘HH:MM:SS+HH:MM[:SS[.ffffff]]’, if *note microsecond: 1899. is
          0 and *note utcoffset(): 18e3. 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: 1899. is
          0, same as ‘'microseconds'’ otherwise.

        - ‘'hours'’: Include the *note hour: 1896. in the two-digit ‘HH’
          format.

        - ‘'minutes'’: Include *note hour: 1896. and *note minute: 1897.
          in ‘HH:MM’ format.

        - ‘'seconds'’: Include *note hour: 1896, *note minute: 1897, and
          *note second: 1898. 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: 1fc. will be raised on an invalid `timespec'
     argument.

     Example:

          >>> 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 版新加入: Added the `timespec' argument.

 -- 成員函式: 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.  For a complete list of formatting directives, see
     *note strftime() and strptime() Behavior: 18bd.

 -- 成員函式: time.__format__ (format)

     Same as *note time.strftime(): 18e5.  This makes it possible to
     specify a format string for a *note time: 4f8. object in *note
     formatted string literals: 15d. and when using *note str.format():
     4df.  For a complete list of formatting directives, see *note
     strftime() and strptime() Behavior: 18bd.

 -- 成員函式: time.utcoffset ()

     If *note tzinfo: 189a. 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: 196. 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: 189a. 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: 196. 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: 189a. 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:

* Examples of Usage; time: Examples of Usage time.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue13936


File: python.info,  Node: Examples of Usage time,  Up: time Objects

5.8.1.13 Examples of Usage: ‘time’
..................................

Examples of working with a *note time: 4f8. 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 Objects,  Next: timezone Objects,  Prev: time Objects,  Up: datetime --- Basic date and time types

5.8.1.14 ‘tzinfo’ Objects
.........................

 -- 類別: datetime.tzinfo

     This is an abstract base class, meaning that this class should not
     be instantiated directly.  Define a subclass of *note tzinfo: 385.
     to capture information about a particular time zone.

     An instance of (a concrete subclass of) *note tzinfo: 385. can be
     passed to the constructors for *note datetime: 195. and *note time:
     4f8. objects.  The latter objects view their attributes as being in
     local time, and the *note tzinfo: 385. 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: 385. methods needed
     by the *note datetime: 195. methods you use.  The *note datetime:
     31. module provides *note timezone: a06, a simple concrete subclass
     of *note tzinfo: 385. which can represent timezones with fixed
     offset from UTC such as UTC itself or North American EST and EDT.

     Special requirement for pickling: A *note tzinfo: 385. subclass
     must have an *note __init__(): d63. 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: 385. may need to implement the
     following methods.  Exactly which methods are needed depends on the
     uses made of aware *note datetime: 31. objects.  If in doubt,
     simply implement all of them.

 -- 成員函式: tzinfo.utcoffset (dt)

     Return offset of local time from UTC, as a *note timedelta: 196.
     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: 385. object represents both time zone and DST
     adjustments, *note utcoffset(): 18ec. should return their sum.  If
     the UTC offset isn’t known, return ‘None’.  Else the value returned
     must be a *note timedelta: 196. 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(): 18ec. will probably look like one of these two:

          return CONSTANT                 # fixed-offset class
          return CONSTANT + self.dst(dt)  # daylight-aware class

     If *note utcoffset(): 18ec. does not return ‘None’, *note dst():
     18ed. should not return ‘None’ either.

     The default implementation of *note utcoffset(): 18ec. raises *note
     NotImplementedError: 613.

     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: 196. 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: 196. object (see
     *note utcoffset(): 18ec. for details).  Note that DST offset, if
     applicable, has already been added to the UTC offset returned by
     *note utcoffset(): 18ec, so there’s no need to consult *note dst():
     18ed. unless you’re interested in obtaining DST info separately.
     For example, *note datetime.timetuple(): 18d2. calls its *note
     tzinfo: 18a2. attribute’s *note dst(): 18ed. method to determine
     how the ‘tm_isdst’ flag should be set, and *note tzinfo.fromutc():
     18d0. calls *note dst(): 18ed. to account for DST changes when
     crossing time zones.

     An instance `tz' of a *note tzinfo: 385. 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: 195. `dt'
     with ‘dt.tzinfo == tz’ For sane *note tzinfo: 385. 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(): 197.
     relies on this, but cannot detect violations; it’s the programmer’s
     responsibility to ensure it.  If a *note tzinfo: 385. subclass
     cannot guarantee this, it may be able to override the default
     implementation of *note tzinfo.fromutc(): 18d0. to work correctly
     with ‘astimezone()’ regardless.

     Most implementations of *note dst(): 18ed. will probably look like
     one of these two:

          def dst(self, dt):
              # a fixed-offset class:  doesn't account for DST
              return timedelta(0)

     or:

          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(): 18ed. raises *note
     NotImplementedError: 613.

     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: 195.
     object `dt', as a string.  Nothing about string names is defined by
     the *note datetime: 31. 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: 385. subclasses will wish to return different names
     depending on the specific value of `dt' passed, especially if the
     *note tzinfo: 385. class is accounting for daylight time.

     The default implementation of *note tzname(): 18ee. raises *note
     NotImplementedError: 613.

These methods are called by a *note datetime: 195. or *note time: 4f8.
object, in response to their methods of the same names.  A *note
datetime: 195. object passes itself as the argument, and a *note time:
4f8. object passes ‘None’ as the argument.  A *note tzinfo: 385.
subclass’s methods should therefore be prepared to accept a `dt'
argument of ‘None’, or of class *note datetime: 195.

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:
385. 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: 195. object is passed in response to a *note
datetime: 195. method, ‘dt.tzinfo’ is the same object as `self'.  *note
tzinfo: 385. methods can rely on this, unless user code calls *note
tzinfo: 385. methods directly.  The intent is that the *note tzinfo:
385. methods interpret `dt' as being in local time, and not need worry
about objects in other timezones.

There is one more *note tzinfo: 385. method that a subclass may wish to
override:

 -- 成員函式: tzinfo.fromutc (dt)

     This is called from the default *note datetime.astimezone(): 197.
     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(): 18d0. is to adjust the date
     and time data, returning an equivalent datetime in `self'’s local
     time.

     Most *note tzinfo: 385. subclasses should be able to inherit the
     default *note fromutc(): 18d0. 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(): 18d0.
     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 ‘astimezone()’ and *note fromutc(): 18d0. 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(): 18d0.
     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: 385. 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
     # http://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: 385. 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.  ‘astimezone()’ 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: 4f9. 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: 195. instances that differ only by the
value of the *note fold: 4f9. attribute are considered equal in
comparisons.

Applications that can’t bear wall-time ambiguities should explicitly
check the value of the *note fold: 4f9. attribute or avoid using hybrid
*note tzinfo: 385. subclasses; there are no ambiguities when using *note
timezone: a06, or any other fixed-offset *note tzinfo: 385. subclass
(such as a class representing only EST (fixed offset -5 hours), or only
EDT (fixed offset -4 hours)).

也參考
......

dateutil.tz(1)

     The *note datetime: 31. module has a basic *note timezone: a06.
     class (for handling arbitrary fixed offsets from UTC) and its *note
     timezone.utc: 18ef. attribute (a UTC timezone instance).

     `dateutil.tz' library brings the `IANA timezone database' (also
     known as the Olson database) to Python, and its usage is
     recommended.

IANA timezone database(2)

     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://dateutil.readthedocs.io/en/stable/tz.html

   (2) https://www.iana.org/time-zones


File: python.info,  Node: timezone Objects,  Next: strftime and strptime Behavior,  Prev: tzinfo Objects,  Up: datetime --- Basic date and time types

5.8.1.15 ‘timezone’ Objects
...........................

The *note timezone: a06. class is a subclass of *note tzinfo: 385, each
instance of which represents a timezone defined by a fixed offset from
UTC.

Objects of this class cannot be used to represent timezone 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: 196.
     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: 1fc. 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(): 18d1. 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: a06.
     instance is constructed.

     The `dt' argument is ignored.  The return value is a *note
     timedelta: 196. 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: a06.
     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)

     Always returns ‘None’.

 -- 成員函式: timezone.fromutc (dt)

     Return ‘dt + offset’.  The `dt' argument must be an aware *note
     datetime: 195. instance, with ‘tzinfo’ set to ‘self’.

Class attributes:

 -- 屬性: timezone.utc

     The UTC timezone, ‘timezone(timedelta(0))’.


File: python.info,  Node: strftime and strptime Behavior,  Prev: timezone Objects,  Up: datetime --- Basic date and time types

5.8.1.16 ‘strftime()’ and ‘strptime()’ Behavior
...............................................

*note date: 194, *note datetime: 195, and *note time: 4f8. 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(): fb4. class method creates a
*note datetime: 195. object from a string representing a date and time
and a corresponding format string.

The table below provides a high-level comparison of ‘strftime()’ versus
‘strptime()’:

                     ‘strftime’                                                   ‘strptime’
                                                                                  
---------------------------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                  
Usage                Convert object to a string according to a given format       Parse a string into a *note datetime: 195. object given a corresponding format
                                                                                  
                                                                                  
Type of method       Instance method                                              Class method
                                                                                  
                                                                                  
Method of            *note date: 194.; *note datetime: 195.; *note time: 4f8.     *note datetime: 195.
                                                                                  
                                                                                  
Signature            ‘strftime(format)’                                           ‘strptime(date_string, format)’
                                                                                  

* Menu:

* strftime() and strptime() Format Codes: strftime and strptime Format Codes.
* Technical Detail::


File: python.info,  Node: strftime and strptime Format Codes,  Next: Technical Detail,  Up: strftime and strptime Behavior

5.8.1.17 ‘strftime()’ and ‘strptime()’ Format Codes
...................................................

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       Meaning                              Example                      註解
                                                                                  
----------------------------------------------------------------------------------------------
                                                                                  
‘%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’            Month as a zero-padded decimal       01, 02, ..., 12              (9)
                number.                                                           
                
                                                                                  
‘%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 on the left.             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, EST, CST
                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                                   
                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       Meaning                              Example                      註解
                                                                                  
----------------------------------------------------------------------------------------------
                                                                                  
‘%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.
                

These may not be available on all platforms when used with the
‘strftime()’ method.  The ISO 8601 year and ISO 8601 week directives are
not interchangeable with the year and week number directives above.
Calling ‘strptime()’ with incomplete or ambiguous ISO 8601 directives
will raise a *note ValueError: 1fc.

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)’ documentation.

3.6 版新加入: ‘%G’, ‘%u’ and ‘%V’ were added.


File: python.info,  Node: Technical Detail,  Prev: strftime and strptime Format Codes,  Up: strftime and strptime Behavior

5.8.1.18 Technical Detail
.........................

Broadly speaking, ‘d.strftime(fmt)’ acts like the *note time: 10b.
module’s ‘time.strftime(fmt, d.timetuple())’ although not all objects
support a ‘timetuple()’ method.

For the *note datetime.strptime(): fb4. 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 timezone offset
information, which are supported in ‘datetime.strptime’ but are
discarded by ‘time.strptime’.

For *note time: 4f8. objects, the format codes for year, month, and day
should not be used, as *note time: 10b. objects have no such values.  If
they’re used anyway, ‘1900’ is substituted for the year, and ‘1’ for the
month and day.

For *note date: 194. objects, the format codes for hours, minutes,
seconds, and microseconds should not be used, as *note date: 194.
objects have no such values.  If they’re used anyway, ‘0’ is substituted
for them.

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: c40. 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 Unicode characters
     encoded using the locale’s default encoding (for example, if the
     current locale is ‘ja_JP’, the default encoding could be any one of
     ‘eucJP’, ‘SJIS’, or ‘utf-8’; use *note locale.getlocale(): 18f9. to
     determine the current locale’s encoding).

  2. The ‘strptime()’ 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, ‘strftime()’ method was
     restricted to years >= 1900.

     3.3 版更變: In version 3.2, ‘strftime()’ method was restricted to
     years >= 1000.

  3. When used with the ‘strptime()’ 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: 10b. module, the *note datetime: 31. module
     does not support leap seconds.

  5. When used with the ‘strptime()’ 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’ and ‘%Z’ format codes are replaced by
     empty strings.

     For an aware object:

     ‘%z’

          ‘utcoffset()’ 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
          ‘utcoffset()’ 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 ‘strptime()’
     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’

          If ‘tzname()’ returns ‘None’, ‘%Z’ is replaced by an empty
          string.  Otherwise ‘%Z’ is replaced by the returned value,
          which must be a string.

     3.2 版更變: When the ‘%z’ directive is provided to the ‘strptime()’
     method, an aware *note datetime: 195. object will be produced.  The
     ‘tzinfo’ of the result will be set to a *note timezone: a06.
     instance.

  7. When used with the ‘strptime()’ 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
     ‘strptime()’ format string.  Also note that ‘%G’ and ‘%Y’ are not
     interchangeable.

  9. When used with the ‘strptime()’ 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.

註解
....

   ---------- Footnotes ----------

   (1) (4) Passing ‘datetime.strptime('Feb 29', '%b %d')’ will fail
since ‘1900’ is not a leap year.


File: python.info,  Node: calendar --- General calendar-related functions,  Next: collections --- 容器資料型態,  Prev: datetime --- Basic date and time types,  Up: Data Types

5.8.2 ‘calendar’ — General calendar-related functions
-----------------------------------------------------

`Source code:' Lib/calendar.py(1)

__________________________________________________________________

This module allows you to output calendars like the Unix ‘cal’ program,
and provides additional useful functions related to the calendar.  By
default, these calendars have Monday as the first day of the week, and
Sunday as the last (the European convention).  Use *note
setfirstweekday(): 18fc. to set the first day of the week to Sunday (6)
or to any other weekday.  Parameters that specify dates are given as
integers.  For related functionality, see also the *note datetime: 31.
and *note time: 10b. modules.

The functions and classes defined in this module use an idealized
calendar, the current Gregorian calendar extended indefinitely in both
directions.  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.  Zero and negative
years are interpreted as prescribed by the ISO 8601 standard.  Year 0 is
1 BC, year -1 is 2 BC, and so on.

 -- 類別: calendar.Calendar (firstweekday=0)

     Creates a *note Calendar: 18fd. object.  `firstweekday' is an
     integer specifying the first day of the week.  ‘0’ is Monday (the
     default), ‘6’ is Sunday.

     A *note Calendar: 18fd. object provides several methods that can be
     used for preparing the calendar data for formatting.  This class
     doesn’t do any formatting itself.  This is the job of subclasses.

     *note Calendar: 18fd. instances have the following methods:

      -- 成員函式: iterweekdays ()

          Return an iterator for the week day numbers that will be used
          for one week.  The first value from the iterator will be the
          same as the value of the *note firstweekday: 18ff. property.

      -- 成員函式: itermonthdates (year, month)

          Return an iterator for the month `month' (1–12) in the year
          `year'.  This iterator will return all days (as *note
          datetime.date: 194. objects) for the month and all days before
          the start of the month or after the end of the month that are
          required to get a complete week.

      -- 成員函式: itermonthdays (year, month)

          Return an iterator for the month `month' in the year `year'
          similar to *note itermonthdates(): 4ab, but not restricted by
          the *note datetime.date: 194. range.  Days returned will
          simply be day of the month numbers.  For the days outside of
          the specified month, the day number is ‘0’.

      -- 成員函式: itermonthdays2 (year, month)

          Return an iterator for the month `month' in the year `year'
          similar to *note itermonthdates(): 4ab, but not restricted by
          the *note datetime.date: 194. range.  Days returned will be
          tuples consisting of a day of the month number and a week day
          number.

      -- 成員函式: itermonthdays3 (year, month)

          Return an iterator for the month `month' in the year `year'
          similar to *note itermonthdates(): 4ab, but not restricted by
          the *note datetime.date: 194. range.  Days returned will be
          tuples consisting of a year, a month and a day of the month
          numbers.

          3.7 版新加入.

      -- 成員函式: itermonthdays4 (year, month)

          Return an iterator for the month `month' in the year `year'
          similar to *note itermonthdates(): 4ab, but not restricted by
          the *note datetime.date: 194. range.  Days returned will be
          tuples consisting of a year, a month, a day of the month, and
          a day of the week numbers.

          3.7 版新加入.

      -- 成員函式: monthdatescalendar (year, month)

          Return a list of the weeks in the month `month' of the `year'
          as full weeks.  Weeks are lists of seven *note datetime.date:
          194. objects.

      -- 成員函式: monthdays2calendar (year, month)

          Return a list of the weeks in the month `month' of the `year'
          as full weeks.  Weeks are lists of seven tuples of day numbers
          and weekday numbers.

      -- 成員函式: monthdayscalendar (year, month)

          Return a list of the weeks in the month `month' of the `year'
          as full weeks.  Weeks are lists of seven day numbers.

      -- 成員函式: yeardatescalendar (year, width=3)

          Return the data for the specified year ready for formatting.
          The return value is a list of month rows.  Each month row
          contains up to `width' months (defaulting to 3).  Each month
          contains between 4 and 6 weeks and each week contains 1–7
          days.  Days are *note datetime.date: 194. objects.

      -- 成員函式: yeardays2calendar (year, width=3)

          Return the data for the specified year ready for formatting
          (similar to *note yeardatescalendar(): 1905.).  Entries in the
          week lists are tuples of day numbers and weekday numbers.  Day
          numbers outside this month are zero.

      -- 成員函式: yeardayscalendar (year, width=3)

          Return the data for the specified year ready for formatting
          (similar to *note yeardatescalendar(): 1905.).  Entries in the
          week lists are day numbers.  Day numbers outside this month
          are zero.

 -- 類別: calendar.TextCalendar (firstweekday=0)

     This class can be used to generate plain text calendars.

     *note TextCalendar: 1908. instances have the following methods:

      -- 成員函式: formatmonth (theyear, themonth, w=0, l=0)

          Return a month’s calendar in a multi-line string.  If `w' is
          provided, it specifies the width of the date columns, which
          are centered.  If `l' is given, it specifies the number of
          lines that each week will use.  Depends on the first weekday
          as specified in the constructor or set by the *note
          setfirstweekday(): 18fc. method.

      -- 成員函式: prmonth (theyear, themonth, w=0, l=0)

          Print a month’s calendar as returned by *note formatmonth():
          1909.

      -- 成員函式: formatyear (theyear, w=2, l=1, c=6, m=3)

          Return a `m'-column calendar for an entire year as a
          multi-line string.  Optional parameters `w', `l', and `c' are
          for date column width, lines per week, and number of spaces
          between month columns, respectively.  Depends on the first
          weekday as specified in the constructor or set by the *note
          setfirstweekday(): 18fc. method.  The earliest year for which
          a calendar can be generated is platform-dependent.

      -- 成員函式: pryear (theyear, w=2, l=1, c=6, m=3)

          Print the calendar for an entire year as returned by *note
          formatyear(): 190b.

 -- 類別: calendar.HTMLCalendar (firstweekday=0)

     This class can be used to generate HTML calendars.

     ‘HTMLCalendar’ instances have the following methods:

      -- 成員函式: formatmonth (theyear, themonth, withyear=True)

          Return a month’s calendar as an HTML table.  If `withyear' is
          true the year will be included in the header, otherwise just
          the month name will be used.

      -- 成員函式: formatyear (theyear, width=3)

          Return a year’s calendar as an HTML table.  `width'
          (defaulting to 3) specifies the number of months per row.

      -- 成員函式: formatyearpage (theyear, width=3, css='calendar.css',
               encoding=None)

          Return a year’s calendar as a complete HTML page.  `width'
          (defaulting to 3) specifies the number of months per row.
          `css' is the name for the cascading style sheet to be used.
          *note None: 158. can be passed if no style sheet should be
          used.  `encoding' specifies the encoding to be used for the
          output (defaulting to the system default encoding).

     ‘HTMLCalendar’ has the following attributes you can override to
     customize the CSS classes used by the calendar:

      -- 屬性: cssclasses

          A list of CSS classes used for each weekday.  The default
          class list is:

               cssclasses = ["mon", "tue", "wed", "thu", "fri", "sat", "sun"]

          more styles can be added for each day:

               cssclasses = ["mon text-bold", "tue", "wed", "thu", "fri", "sat", "sun red"]

          Note that the length of this list must be seven items.

      -- 屬性: cssclass_noday

          The CSS class for a weekday occurring in the previous or
          coming month.

          3.7 版新加入.

      -- 屬性: cssclasses_weekday_head

          A list of CSS classes used for weekday names in the header
          row.  The default is the same as *note cssclasses: 1910.

          3.7 版新加入.

      -- 屬性: cssclass_month_head

          The month’s head CSS class (used by ‘formatmonthname()’).  The
          default value is ‘"month"’.

          3.7 版新加入.

      -- 屬性: cssclass_month

          The CSS class for the whole month’s table (used by *note
          formatmonth(): 190d.).  The default value is ‘"month"’.

          3.7 版新加入.

      -- 屬性: cssclass_year

          The CSS class for the whole year’s table of tables (used by
          *note formatyear(): 190e.).  The default value is ‘"year"’.

          3.7 版新加入.

      -- 屬性: cssclass_year_head

          The CSS class for the table head for the whole year (used by
          *note formatyear(): 190e.).  The default value is ‘"year"’.

          3.7 版新加入.

     Note that although the naming for the above described class
     attributes is singular (e.g.  ‘cssclass_month’ ‘cssclass_noday’),
     one can replace the single CSS class with a space separated list of
     CSS classes, for example:

          "text-bold text-red"

     Here is an example how ‘HTMLCalendar’ can be customized:

          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)

     This subclass of *note TextCalendar: 1908. can be passed a locale
     name in the constructor and will return month and weekday names in
     the specified locale.  If this locale includes an encoding all
     strings containing month and weekday names will be returned as
     unicode.

 -- 類別: calendar.LocaleHTMLCalendar (firstweekday=0, locale=None)

     This subclass of *note HTMLCalendar: 374. can be passed a locale
     name in the constructor and will return month and weekday names in
     the specified locale.  If this locale includes an encoding all
     strings containing month and weekday names will be returned as
     unicode.

     備註: The ‘formatweekday()’ and ‘formatmonthname()’ methods of
     these two classes temporarily change the current locale to the
     given `locale'.  Because the current locale is a process-wide
     setting, they are not thread-safe.

For simple text calendars this module provides the following functions.

 -- 函式: calendar.setfirstweekday (weekday)

     Sets the weekday (‘0’ is Monday, ‘6’ is Sunday) to start each week.
     The values ‘MONDAY’, ‘TUESDAY’, ‘WEDNESDAY’, ‘THURSDAY’, ‘FRIDAY’,
     ‘SATURDAY’, and ‘SUNDAY’ are provided for convenience.  For
     example, to set the first weekday to Sunday:

          import calendar
          calendar.setfirstweekday(calendar.SUNDAY)

 -- 函式: calendar.firstweekday ()

     Returns the current setting for the weekday to start each week.

 -- 函式: calendar.isleap (year)

     Returns *note True: 49e. if `year' is a leap year, otherwise *note
     False: 38d.

 -- 函式: calendar.leapdays (y1, y2)

     Returns the number of leap years in the range from `y1' to `y2'
     (exclusive), where `y1' and `y2' are years.

     This function works for ranges spanning a century change.

 -- 函式: calendar.weekday (year, month, day)

     Returns the day of the week (‘0’ is Monday) for `year'
     (‘1970’–...), `month' (‘1’–‘12’), `day' (‘1’–‘31’).

 -- 函式: calendar.weekheader (n)

     Return a header containing abbreviated weekday names.  `n'
     specifies the width in characters for one weekday.

 -- 函式: calendar.monthrange (year, month)

     Returns weekday of first day of the month and number of days in
     month, for the specified `year' and `month'.

 -- 函式: calendar.monthcalendar (year, month)

     Returns a matrix representing a month’s calendar.  Each row
     represents a week; days outside of the month are represented by
     zeros.  Each week begins with Monday unless set by *note
     setfirstweekday(): 18fc.

 -- 函式: calendar.prmonth (theyear, themonth, w=0, l=0)

     Prints a month’s calendar as returned by *note month(): 1920.

 -- 函式: calendar.month (theyear, themonth, w=0, l=0)

     Returns a month’s calendar in a multi-line string using the
     ‘formatmonth()’ of the *note TextCalendar: 1908. class.

 -- 函式: calendar.prcal (year, w=0, l=0, c=6, m=3)

     Prints the calendar for an entire year as returned by *note
     calendar(): 15.

 -- 函式: calendar.calendar (year, w=2, l=1, c=6, m=3)

     Returns a 3-column calendar for an entire year as a multi-line
     string using the ‘formatyear()’ of the *note TextCalendar: 1908.
     class.

 -- 函式: calendar.timegm (tuple)

     An unrelated but handy function that takes a time tuple such as
     returned by the *note gmtime(): b44. function in the *note time:
     10b. module, and returns the corresponding Unix timestamp value,
     assuming an epoch of 1970, and the POSIX encoding.  In fact, *note
     time.gmtime(): b44. and *note timegm(): 1923. are each others’
     inverse.

The *note calendar: 15. module exports the following data attributes:

 -- Data: calendar.day_name

     An array that represents the days of the week in the current
     locale.

 -- Data: calendar.day_abbr

     An array that represents the abbreviated days of the week in the
     current locale.

 -- Data: calendar.month_name

     An array that represents the months of the year in the current
     locale.  This follows normal convention of January being month
     number 1, so it has a length of 13 and ‘month_name[0]’ is the empty
     string.

 -- Data: calendar.month_abbr

     An array that represents the abbreviated months of the year in the
     current locale.  This follows normal convention of January being
     month number 1, so it has a length of 13 and ‘month_abbr[0]’ is the
     empty string.

也參考
......

Module *note datetime: 31.

     Object-oriented interface to dates and times with similar
     functionality to the *note time: 10b. module.

Module *note time: 10b.

     Low-level time related functions.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/calendar.py


File: python.info,  Node: collections --- 容器資料型態,  Next: collections abc --- Abstract Base Classes for Containers,  Prev: calendar --- General calendar-related functions,  Up: Data Types

5.8.3 ‘collections’ — 容器資料型態
----------------------------------

`原始碼：' Lib/collections/__init__.py(1)

__________________________________________________________________

這個模組實作了一些特別的容器資料型態，用來替代 Python 一般內建的容器，例
如 *note dict: 1b9. 、 *note list: 263. 、 *note set: b74. 和 *note
tuple: 483. 。

*note namedtuple(): 1b8.  用來建立一個欄位擁有名字的 tuple 子類別的函數
                          
                          
*note deque: 536.         一個類似 list 的容器，可以快速的在頭尾加入元素與取出元素。
                          
                          
*note ChainMap: 4ae.      一個像是 dict 的類別，用來為多個 mapping 建立單一的 view 。
                          
                          
*note Counter: 9df.       dict 的子類別，用來計算可 hash 物件的數量。
                          
                          
*note OrderedDict: 1ba.   dict 的子類別，會記錄物件被加入的順序。
                          
                          
*note defaultdict: b3f.   dict 的子類別，在值不存在 dict 當中時會呼叫一個產生函式。
                          
                          
*note UserDict: 192a.     wrapper around dictionary objects for easier dict subclassing
                          
                          
*note UserList: 192b.     wrapper around list objects for easier list subclassing
                          
                          
*note UserString: 6b2.    wrapper around string objects for easier string subclassing
                          

Deprecated since version 3.3, will be removed in version 3.10: Moved
*note Collections Abstract Base Classes: 192c. to the *note
collections.abc: 1f. module.  For backwards compatibility, they continue
to be visible in this module through Python 3.9.

* Menu:

* ChainMap objects::
* Counter 物件::
* deque objects::
* defaultdict objects::
* namedtuple() Factory Function for Tuples with Named Fields: namedtuple Factory Function for Tuples with Named Fields.
* OrderedDict objects::
* UserDict objects::
* UserList objects::
* UserString objects::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/collections/__init__.py


File: python.info,  Node: ChainMap objects,  Next: Counter 物件,  Up: collections --- 容器資料型態

5.8.3.1 ‘ChainMap’ objects
..........................

3.3 版新加入.

A *note ChainMap: 4ae. class is provided for quickly linking a number of
mappings so they can be treated as a single unit.  It is often much
faster than creating a new dictionary and running multiple *note
update(): dce. calls.

The class can be used to simulate nested scopes and is useful in
templating.

 -- 類別: collections.ChainMap (*maps)

     A *note ChainMap: 4ae. groups multiple dicts or other mappings
     together to create a single, updateable view.  If no `maps' are
     specified, a single empty dictionary is provided so that a new
     chain always has at least one mapping.

     The underlying mappings are stored in a list.  That list is public
     and can be accessed or updated using the `maps' attribute.  There
     is no other state.

     Lookups search the underlying mappings successively until a key is
     found.  In contrast, writes, updates, and deletions only operate on
     the first mapping.

     A *note ChainMap: 4ae. incorporates the underlying mappings by
     reference.  So, if one of the underlying mappings gets updated,
     those changes will be reflected in *note ChainMap: 4ae.

     All of the usual dictionary methods are supported.  In addition,
     there is a `maps' attribute, a method for creating new subcontexts,
     and a property for accessing all but the first mapping:

      -- 屬性: maps

          A user updateable list of mappings.  The list is ordered from
          first-searched to last-searched.  It is the only stored state
          and can be modified to change which mappings are searched.
          The list should always contain at least one mapping.

      -- 成員函式: new_child (m=None)

          Returns a new *note ChainMap: 4ae. containing a new map
          followed by all of the maps in the current instance.  If ‘m’
          is specified, it becomes the new map at the front of the list
          of mappings; if not specified, an empty dict is used, so that
          a call to ‘d.new_child()’ is equivalent to: ‘ChainMap({},
          *d.maps)’.  This method is used for creating subcontexts that
          can be updated without altering values in any of the parent
          mappings.

          3.4 版更變: The optional ‘m’ parameter was added.

      -- 屬性: parents

          Property returning a new *note ChainMap: 4ae. containing all
          of the maps in the current instance except the first one.
          This is useful for skipping the first map in the search.  Use
          cases are similar to those for the *note nonlocal: c44.
          keyword used in *note nested scopes: 15f0.  The use cases also
          parallel those for the built-in *note super(): 4e7. function.
          A reference to ‘d.parents’ is equivalent to:
          ‘ChainMap(*d.maps[1:])’.

     Note, the iteration order of a *note ChainMap(): 4ae. is determined
     by scanning the mappings last to first:

          >>> baseline = {'music': 'bach', 'art': 'rembrandt'}
          >>> adjustments = {'art': 'van gogh', 'opera': 'carmen'}
          >>> list(ChainMap(adjustments, baseline))
          ['music', 'art', 'opera']

     This gives the same ordering as a series of *note dict.update():
     dce. calls starting with the last mapping:

          >>> combined = baseline.copy()
          >>> combined.update(adjustments)
          >>> list(combined)
          ['music', 'art', 'opera']

也參考
......

   * The MultiContext class(1) in the Enthought CodeTools package(2) has
     options to support writing to any mapping in the chain.

   * Django’s Context class(3) for templating is a read-only chain of
     mappings.  It also features pushing and popping of contexts similar
     to the *note new_child(): 82e. method and the *note parents: 192f.
     property.

   * The Nested Contexts recipe(4) has options to control whether writes
     and other mutations apply only to the first mapping or to any
     mapping in the chain.

   * A greatly simplified read-only version of Chainmap(5).

* Menu:

* ChainMap Examples and Recipes::

   ---------- Footnotes ----------

   (1) 
https://github.com/enthought/codetools/blob/4.0.0/codetools/contexts/multi_context.py

   (2) https://github.com/enthought/codetools

   (3) 
https://github.com/django/django/blob/main/django/template/context.py

   (4) https://code.activestate.com/recipes/577434/

   (5) https://code.activestate.com/recipes/305268/


File: python.info,  Node: ChainMap Examples and Recipes,  Up: ChainMap objects

5.8.3.2 ‘ChainMap’ Examples and Recipes
.......................................

This section shows various approaches to working with chained maps.

Example of simulating Python’s internal lookup chain:

     import builtins
     pylookup = ChainMap(locals(), globals(), vars(builtins))

Example of letting user specified command-line arguments take precedence
over environment variables which in turn take precedence over default
values:

     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'])

Example patterns for using the *note ChainMap: 4ae. class to simulate
nested contexts:

     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

The *note ChainMap: 4ae. class only makes updates (writes and deletions)
to the first mapping in the chain while lookups will search the full
chain.  However, if deep writes and deletions are desired, it is easy to
make a subclass that updates keys found deeper in the chain:

     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 objects,  Prev: ChainMap objects,  Up: collections --- 容器資料型態

5.8.3.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])

     A *note Counter: 9df. is a *note dict: 1b9. subclass for counting
     hashable objects.  It is a collection where elements are stored as
     dictionary keys and their counts are stored as dictionary values.
     Counts are allowed to be any integer value including zero or
     negative counts.  The *note Counter: 9df. class is similar to bags
     or multisets in other languages.

     被計數的元素來自一個 `iterable' 或是被其他的 `mapping' (or 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: 2c8. 這點不同。

          >>> 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 版更變: As a *note dict: 1b9. subclass, *note Counter: 9df.
     Inherited the capability to remember insertion order.  Math
     operations on `Counter' objects also preserve order.  Results are
     ordered according to when an element is first encountered in the
     left operand and then by the order encountered in the right
     operand.

     除了字典的方法外，Counter 物件額外支援三個新方法。

      -- 成員函式: elements ()

          Return an iterator over elements repeating each as many times
          as its count.  Elements are returned in the order first
          encountered.  If an element’s count is less than one, *note
          elements(): c9f. will ignore it.

               >>> c = Counter(a=4, b=2, c=0, d=-2)
               >>> sorted(c.elements())
               ['a', 'a', 'a', 'a', 'b', 'b']

      -- 成員函式: most_common ([n])

          Return a list of the `n' most common elements and their counts
          from the most common to the least.  If `n' is omitted or
          ‘None’, *note most_common(): c9e. returns `all' elements in
          the counter.  Elements with equal counts are ordered in the
          order first encountered:

               >>> Counter('abracadabra').most_common(3)
               [('a', 5), ('b', 2), ('r', 2)]

      -- 成員函式: subtract ([iterable-or-mapping])

          Elements are subtracted from an `iterable' or from another
          `mapping' (or counter).  Like *note dict.update(): dce. but
          subtracts counts instead of replacing them.  Both inputs and
          outputs may be zero or negative.

               >>> 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 版新加入.

     The usual dictionary methods are available for *note Counter: 9df.
     objects except for two which work differently for counters.

      -- 成員函式: fromkeys (iterable)

          This class method is not implemented for *note Counter: 9df.
          objects.

      -- 成員函式: update ([iterable-or-mapping])

          Elements are counted from an `iterable' or added-in from
          another `mapping' (or counter).  Like *note dict.update():
          dce. but adds counts instead of replacing them.  Also, the
          `iterable' is expected to be a sequence of elements, not a
          sequence of ‘(key, value)’ pairs.

Common patterns for working with *note Counter: 9df. objects:

     sum(c.values())                 # 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()                       # convert to a list of (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

Several mathematical operations are provided for combining *note
Counter: 9df. objects to produce multisets (counters that have counts
greater than zero).  Addition and subtraction combine counters by adding
or subtracting the counts of corresponding elements.  Intersection and
union return the minimum and maximum of corresponding counts.  Each
operation can accept inputs with signed counts, but the output will
exclude results with counts of zero or less.

     >>> 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})

Unary addition and subtraction are shortcuts for adding an empty counter
or subtracting from an empty counter.

     >>> c = Counter(a=2, b=-4)
     >>> +c
     Counter({'a': 2})
     >>> -c
     Counter({'b': 4})

3.3 版新加入: Added support for unary plus, unary minus, and in-place
multiset operations.

     備註: Counters were primarily designed to work with positive
     integers to represent running counts; however, care was taken to
     not unnecessarily preclude use cases needing other types or
     negative values.  To help with those use cases, this section
     documents the minimum range and type restrictions.

        * The *note Counter: 9df. class itself is a dictionary subclass
          with no restrictions on its keys and values.  The values are
          intended to be numbers representing counts, but you `could'
          store anything in the value field.

        * The *note most_common(): c9e. method requires only that the
          values be orderable.

        * For in-place operations such as ‘c[key] += 1’, the value type
          need only support addition and subtraction.  So fractions,
          floats, and decimals would work and negative values are
          supported.  The same is also true for *note update(): 1933.
          and *note subtract(): b5f. which allow negative and zero
          values for both inputs and outputs.

        * The multiset methods are designed only for use cases with
          positive values.  The inputs may be negative or zero, but only
          outputs with positive values are created.  There are no type
          restrictions, but the value type needs to support addition,
          subtraction, and comparison.

        * The *note elements(): c9f. method requires integer counts.  It
          ignores zero and negative counts.

也參考
......

   * Bag class(1) in Smalltalk.

   * Wikipedia entry for Multisets(2).

   * C++ multisets(3) tutorial with examples.

   * For mathematical operations on multisets and their use cases, see
     `Knuth, Donald.  The Art of Computer Programming Volume II, Section
     4.6.3, Exercise 19'.

   * To enumerate all distinct multisets of a given size over a given
     set of elements, see *note
     itertools.combinations_with_replacement(): c1e.:

          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 objects,  Next: defaultdict objects,  Prev: Counter 物件,  Up: collections --- 容器資料型態

5.8.3.4 ‘deque’ objects
.......................

 -- 類別: collections.deque ([iterable[, maxlen]])

     Returns a new deque object initialized left-to-right (using *note
     append(): 1935.) with data from `iterable'.  If `iterable' is not
     specified, the new deque is empty.

     Deques are a generalization of stacks and queues (the name is
     pronounced "deck" and is short for "double-ended queue").  Deques
     support thread-safe, memory efficient appends and pops from either
     side of the deque with approximately the same O(1) performance in
     either direction.

     Though *note list: 263. objects support similar operations, they
     are optimized for fast fixed-length operations and incur O(n)
     memory movement costs for ‘pop(0)’ and ‘insert(0, v)’ operations
     which change both the size and position of the underlying data
     representation.

     If `maxlen' is not specified or is ‘None’, deques may grow to an
     arbitrary length.  Otherwise, the deque is bounded to the specified
     maximum length.  Once a bounded length deque is full, when new
     items are added, a corresponding number of items are discarded from
     the opposite end.  Bounded length deques provide functionality
     similar to the ‘tail’ filter in Unix.  They are also useful for
     tracking transactions and other pools of data where only the most
     recent activity is of interest.

     Deque objects support the following methods:

      -- 成員函式: append (x)

          Add `x' to the right side of the deque.

      -- 成員函式: appendleft (x)

          Add `x' to the left side of the deque.

      -- 成員函式: clear ()

          Remove all elements from the deque leaving it with length 0.

      -- 成員函式: copy ()

          Create a shallow copy of the deque.

          3.5 版新加入.

      -- 成員函式: count (x)

          Count the number of deque elements equal to `x'.

          3.2 版新加入.

      -- 成員函式: extend (iterable)

          Extend the right side of the deque by appending elements from
          the iterable argument.

      -- 成員函式: extendleft (iterable)

          Extend the left side of the deque by appending elements from
          `iterable'.  Note, the series of left appends results in
          reversing the order of elements in the iterable argument.

      -- 成員函式: index (x[, start[, stop]])

          Return the position of `x' in the deque (at or after index
          `start' and before index `stop').  Returns the first match or
          raises *note ValueError: 1fc. if not found.

          3.5 版新加入.

      -- 成員函式: insert (i, x)

          Insert `x' into the deque at position `i'.

          If the insertion would cause a bounded deque to grow beyond
          `maxlen', an *note IndexError: e7a. is raised.

          3.5 版新加入.

      -- 成員函式: pop ()

          Remove and return an element from the right side of the deque.
          If no elements are present, raises an *note IndexError: e7a.

      -- 成員函式: popleft ()

          Remove and return an element from the left side of the deque.
          If no elements are present, raises an *note IndexError: e7a.

      -- 成員函式: remove (value)

          Remove the first occurrence of `value'.  If not found, raises
          a *note ValueError: 1fc.

      -- 成員函式: reverse ()

          Reverse the elements of the deque in-place and then return
          ‘None’.

          3.2 版新加入.

      -- 成員函式: rotate (n=1)

          Rotate the deque `n' steps to the right.  If `n' is negative,
          rotate to the left.

          When the deque is not empty, rotating one step to the right is
          equivalent to ‘d.appendleft(d.pop())’, and rotating one step
          to the left is equivalent to ‘d.append(d.popleft())’.

     Deque objects also provide one read-only attribute:

      -- 屬性: maxlen

          Maximum size of a deque or ‘None’ if unbounded.

          3.1 版新加入.

In addition to the above, deques support iteration, pickling, ‘len(d)’,
‘reversed(d)’, ‘copy.copy(d)’, ‘copy.deepcopy(d)’, membership testing
with the *note in: 7a8. operator, and subscript references such as
‘d[0]’ to access the first element.  Indexed access is O(1) at both ends
but slows to O(n) in the middle.  For fast random access, use lists
instead.

Starting in version 3.5, deques support ‘__add__()’, ‘__mul__()’, and
‘__imul__()’.

Example:

     >>> 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 Recipes::


File: python.info,  Node: deque Recipes,  Up: deque objects

5.8.3.5 ‘deque’ Recipes
.......................

This section shows various approaches to working with deques.

Bounded length deques provide functionality similar to the ‘tail’ filter
in Unix:

     def tail(filename, n=10):
         'Return the last n lines of a file'
         with open(filename) as f:
             return deque(f, n)

Another approach to using deques is to maintain a sequence of recently
added elements by appending to the right and popping to the left:

     def moving_average(iterable, n=3):
         # moving_average([40, 30, 50, 46, 39, 44]) --> 40.0 42.0 45.0 43.0
         # http://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

A round-robin scheduler(1) can be implemented with input iterators
stored in a *note deque: 536.  Values are yielded from the active
iterator in position zero.  If that iterator is exhausted, it can be
removed with *note popleft(): 193b.; otherwise, it can be cycled back to
the end with the *note rotate(): 193d. method:

     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()

The *note rotate(): 193d. method provides a way to implement *note
deque: 536. slicing and deletion.  For example, a pure Python
implementation of ‘del d[n]’ relies on the ‘rotate()’ method to position
elements to be popped:

     def delete_nth(d, n):
         d.rotate(-n)
         d.popleft()
         d.rotate(n)

To implement *note deque: 536. slicing, use a similar approach applying
*note rotate(): 193d. to bring a target element to the left side of the
deque.  Remove old entries with *note popleft(): 193b, add new entries
with *note extend(): 1938, and then reverse the rotation.  With minor
variations on that approach, it is easy to implement Forth style stack
manipulations such as ‘dup’, ‘drop’, ‘swap’, ‘over’, ‘pick’, ‘rot’, and
‘roll’.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Round-robin_scheduling


File: python.info,  Node: defaultdict objects,  Next: namedtuple Factory Function for Tuples with Named Fields,  Prev: deque objects,  Up: collections --- 容器資料型態

5.8.3.6 ‘defaultdict’ objects
.............................

 -- 類別: collections.defaultdict ([default_factory[, ...]])

     Returns a new dictionary-like object.  *note defaultdict: b3f. is a
     subclass of the built-in *note dict: 1b9. class.  It overrides one
     method and adds one writable instance variable.  The remaining
     functionality is the same as for the *note dict: 1b9. class and is
     not documented here.

     The first argument provides the initial value for the *note
     default_factory: 1940. attribute; it defaults to ‘None’.  All
     remaining arguments are treated the same as if they were passed to
     the *note dict: 1b9. constructor, including keyword arguments.

     *note defaultdict: b3f. objects support the following method in
     addition to the standard *note dict: 1b9. operations:

      -- 成員函式: __missing__ (key)

          If the *note default_factory: 1940. attribute is ‘None’, this
          raises a *note KeyError: 2c8. exception with the `key' as
          argument.

          If *note default_factory: 1940. is not ‘None’, it is called
          without arguments to provide a default value for the given
          `key', this value is inserted in the dictionary for the `key',
          and returned.

          If calling *note default_factory: 1940. raises an exception
          this exception is propagated unchanged.

          This method is called by the *note __getitem__(): 27d. method
          of the *note dict: 1b9. class when the requested key is not
          found; whatever it returns or raises is then returned or
          raised by *note __getitem__(): 27d.

          Note that *note __missing__(): 1941. is `not' called for any
          operations besides *note __getitem__(): 27d.  This means that
          ‘get()’ will, like normal dictionaries, return ‘None’ as a
          default rather than using *note default_factory: 1940.

     *note defaultdict: b3f. objects support the following instance
     variable:

      -- 屬性: default_factory

          This attribute is used by the *note __missing__(): 1941.
          method; it is initialized from the first argument to the
          constructor, if present, or to ‘None’, if absent.

* Menu:

* defaultdict Examples::


File: python.info,  Node: defaultdict Examples,  Up: defaultdict objects

5.8.3.7 ‘defaultdict’ Examples
..............................

Using *note list: 263. as the *note default_factory: 1940, it is easy to
group a sequence of key-value pairs into a dictionary of lists:

     >>> 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])]

When each key is encountered for the first time, it is not already in
the mapping; so an entry is automatically created using the *note
default_factory: 1940. function which returns an empty *note list: 263.
The ‘list.append()’ operation then attaches the value to the new list.
When keys are encountered again, the look-up proceeds normally
(returning the list for that key) and the ‘list.append()’ operation adds
another value to the list.  This technique is simpler and faster than an
equivalent technique using *note dict.setdefault(): 9c4.:

     >>> d = {}
     >>> for k, v in s:
     ...     d.setdefault(k, []).append(v)
     ...
     >>> sorted(d.items())
     [('blue', [2, 4]), ('red', [1]), ('yellow', [1, 3])]

Setting the *note default_factory: 1940. to *note int: 185. makes the
*note defaultdict: b3f. useful for counting (like a bag or multiset in
other languages):

     >>> s = 'mississippi'
     >>> d = defaultdict(int)
     >>> for k in s:
     ...     d[k] += 1
     ...
     >>> sorted(d.items())
     [('i', 4), ('m', 1), ('p', 2), ('s', 4)]

When a letter is first encountered, it is missing from the mapping, so
the *note default_factory: 1940. function calls *note int(): 185. to
supply a default count of zero.  The increment operation then builds up
the count for each letter.

The function *note int(): 185. which always returns zero is just a
special case of constant functions.  A faster and more flexible way to
create constant functions is to use a lambda function which can supply
any constant value (not just zero):

     >>> 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>'

Setting the *note default_factory: 1940. to *note set: b74. makes the
*note defaultdict: b3f. useful for building a dictionary of sets:

     >>> 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 Factory Function for Tuples with Named Fields,  Next: OrderedDict objects,  Prev: defaultdict objects,  Up: collections --- 容器資料型態

5.8.3.8 ‘namedtuple()’ Factory Function for Tuples with Named Fields
....................................................................

Named tuples assign meaning to each position in a tuple and allow for
more readable, self-documenting code.  They can be used wherever regular
tuples are used, and they add the ability to access fields by name
instead of position index.

 -- 函式: collections.namedtuple (typename, field_names, *,
          rename=False, defaults=None, module=None)

     Returns a new tuple subclass named `typename'.  The new subclass is
     used to create tuple-like objects that have fields accessible by
     attribute lookup as well as being indexable and iterable.
     Instances of the subclass also have a helpful docstring (with
     typename and field_names) and a helpful *note __repr__(): 343.
     method which lists the tuple contents in a ‘name=value’ format.

     The `field_names' are a sequence of strings such as ‘['x', 'y']’.
     Alternatively, `field_names' can be a single string with each
     fieldname separated by whitespace and/or commas, for example ‘'x
     y'’ or ‘'x, y'’.

     Any valid Python identifier may be used for a fieldname except for
     names starting with an underscore.  Valid identifiers consist of
     letters, digits, and underscores but do not start with a digit or
     underscore and cannot be a *note keyword: a7. such as `class',
     `for', `return', `global', `pass', or `raise'.

     If `rename' is true, invalid fieldnames are automatically replaced
     with positional names.  For example, ‘['abc', 'def', 'ghi', 'abc']’
     is converted to ‘['abc', '_1', 'ghi', '_3']’, eliminating the
     keyword ‘def’ and the duplicate fieldname ‘abc’.

     `defaults' can be ‘None’ or an *note iterable: bb1. of default
     values.  Since fields with a default value must come after any
     fields without a default, the `defaults' are applied to the
     rightmost parameters.  For example, if the fieldnames are ‘['x',
     'y', 'z']’ and the defaults are ‘(1, 2)’, then ‘x’ will be a
     required argument, ‘y’ will default to ‘1’, and ‘z’ will default to
     ‘2’.

     If `module' is defined, the ‘__module__’ attribute of the named
     tuple is set to that value.

     Named tuple instances do not have per-instance dictionaries, so
     they are lightweight and require no more memory than regular
     tuples.

     3.1 版更變: Added support for `rename'.

     3.6 版更變: The `verbose' and `rename' parameters became *note
     keyword-only arguments: 2ad.

     3.6 版更變: Added the `module' parameter.

     3.7 版更變: Removed the `verbose' parameter and the ‘_source’
     attribute.

     3.7 版更變: Added the `defaults' parameter and the
     ‘_field_defaults’ attribute.

     >>> # 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 tuples are especially useful for assigning field names to result
tuples returned by the *note csv: 2a. or *note sqlite3: f3. modules:

     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)

In addition to the methods inherited from tuples, named tuples support
three additional methods and two attributes.  To prevent conflicts with
field names, the method and attribute names start with an underscore.

 -- 成員函式: classmethod somenamedtuple._make (iterable)

     Class method that makes a new instance from an existing sequence or
     iterable.

          >>> t = [11, 22]
          >>> Point._make(t)
          Point(x=11, y=22)

 -- 成員函式: somenamedtuple._asdict ()

     Return a new *note dict: 1b9. which maps field names to their
     corresponding values:

          >>> p = Point(x=11, y=22)
          >>> p._asdict()
          {'x': 11, 'y': 22}

     3.1 版更變: Returns an *note OrderedDict: 1ba. instead of a regular
     *note dict: 1b9.

     3.8 版更變: Returns a regular *note dict: 1b9. instead of an *note
     OrderedDict: 1ba.  As of Python 3.7, regular dicts are guaranteed
     to be ordered.  If the extra features of *note OrderedDict: 1ba.
     are required, the suggested remediation is to cast the result to
     the desired type: ‘OrderedDict(nt._asdict())’.

 -- 成員函式: somenamedtuple._replace (**kwargs)

     Return a new instance of the named tuple replacing specified fields
     with new values:

          >>> 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())

 -- 屬性: somenamedtuple._fields

     Tuple of strings listing the field names.  Useful for introspection
     and for creating new named tuple types from existing named tuples.

          >>> 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

     Dictionary mapping field names to default values.

          >>> Account = namedtuple('Account', ['type', 'balance'], defaults=[0])
          >>> Account._field_defaults
          {'balance': 0}
          >>> Account('premium')
          Account(type='premium', balance=0)

To retrieve a field whose name is stored in a string, use the *note
getattr(): 44d. function:

     >>> getattr(p, 'x')
     11

To convert a dictionary to a named tuple, use the double-star-operator
(as described in *note Unpacking Argument Lists: 125a.):

     >>> d = {'x': 11, 'y': 22}
     >>> Point(**d)
     Point(x=11, y=22)

Since a named tuple is a regular Python class, it is easy to add or
change functionality with a subclass.  Here is how to add a calculated
field and a fixed-width print format:

     >>> 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

The subclass shown above sets ‘__slots__’ to an empty tuple.  This helps
keep memory requirements low by preventing the creation of instance
dictionaries.

Subclassing is not useful for adding new, stored fields.  Instead,
simply create a new named tuple type from the *note _fields: 1946.
attribute:

     >>> Point3D = namedtuple('Point3D', Point._fields + ('z',))

Docstrings can be customized by making direct assignments to the
‘__doc__’ fields:

     >>> 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 版更變: Property docstrings became writeable.

也參考
......

   * See *note typing.NamedTuple: 281. for a way to add type hints for
     named tuples.  It also provides an elegant notation using the *note
     class: c6f. keyword:

          class Component(NamedTuple):
              part_number: int
              weight: float
              description: Optional[str] = None

   * See *note types.SimpleNamespace(): 9b1. for a mutable namespace
     based on an underlying dictionary instead of a tuple.

   * The *note dataclasses: 30. module provides a decorator and
     functions for automatically adding generated special methods to
     user-defined classes.


File: python.info,  Node: OrderedDict objects,  Next: UserDict objects,  Prev: namedtuple Factory Function for Tuples with Named Fields,  Up: collections --- 容器資料型態

5.8.3.9 ‘OrderedDict’ objects
.............................

Ordered dictionaries are just like regular dictionaries but have some
extra capabilities relating to ordering operations.  They have become
less important now that the built-in *note dict: 1b9. class gained the
ability to remember insertion order (this new behavior became guaranteed
in Python 3.7).

Some differences from *note dict: 1b9. still remain:

   * The regular *note dict: 1b9. was designed to be very good at
     mapping operations.  Tracking insertion order was secondary.

   * The *note OrderedDict: 1ba. was designed to be good at reordering
     operations.  Space efficiency, iteration speed, and the performance
     of update operations were secondary.

   * Algorithmically, *note OrderedDict: 1ba. can handle frequent
     reordering operations better than *note dict: 1b9.  This makes it
     suitable for tracking recent accesses (for example in an LRU
     cache(1)).

   * The equality operation for *note OrderedDict: 1ba. checks for
     matching order.

   * The ‘popitem()’ method of *note OrderedDict: 1ba. has a different
     signature.  It accepts an optional argument to specify which item
     is popped.

   * *note OrderedDict: 1ba. has a ‘move_to_end()’ method to efficiently
     reposition an element to an endpoint.

   * Until Python 3.8, *note dict: 1b9. lacked a *note __reversed__():
     534. method.

 -- 類別: collections.OrderedDict ([items])

     Return an instance of a *note dict: 1b9. subclass that has methods
     specialized for rearranging dictionary order.

     3.1 版新加入.

      -- 成員函式: popitem (last=True)

          The *note popitem(): c89. method for ordered dictionaries
          returns and removes a (key, value) pair.  The pairs are
          returned in LIFO order if `last' is true or FIFO order if
          false.

      -- 成員函式: move_to_end (key, last=True)

          Move an existing `key' to either end of an ordered dictionary.
          The item is moved to the right end if `last' is true (the
          default) or to the beginning if `last' is false.  Raises *note
          KeyError: 2c8. if the `key' does not exist:

               >>> d = OrderedDict.fromkeys('abcde')
               >>> d.move_to_end('b')
               >>> ''.join(d.keys())
               'acdeb'
               >>> d.move_to_end('b', last=False)
               >>> ''.join(d.keys())
               'bacde'

          3.2 版新加入.

In addition to the usual mapping methods, ordered dictionaries also
support reverse iteration using *note reversed(): 18f.

Equality tests between *note OrderedDict: 1ba. objects are
order-sensitive and are implemented as
‘list(od1.items())==list(od2.items())’.  Equality tests between *note
OrderedDict: 1ba. objects and other *note Mapping: 1949. objects are
order-insensitive like regular dictionaries.  This allows *note
OrderedDict: 1ba. objects to be substituted anywhere a regular
dictionary is used.

3.5 版更變: The items, keys, and values *note views: 194a. of *note
OrderedDict: 1ba. now support reverse iteration using *note reversed():
18f.

3.6 版更變: With the acceptance of PEP 468(2), order is retained for
keyword arguments passed to the *note OrderedDict: 1ba. constructor and
its ‘update()’ method.

* Menu:

* OrderedDict Examples and Recipes::

   ---------- Footnotes ----------

   (1) 
https://medium.com/@krishankantsinghal/my-first-blog-on-medium-583159139237

   (2) https://www.python.org/dev/peps/pep-0468


File: python.info,  Node: OrderedDict Examples and Recipes,  Up: OrderedDict objects

5.8.3.10 ‘OrderedDict’ Examples and Recipes
...........................................

It is straightforward to create an ordered dictionary variant that
remembers the order the keys were `last' inserted.  If a new entry
overwrites an existing entry, the original insertion position is changed
and moved to the end:

     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)

An *note OrderedDict: 1ba. would also be useful for implementing
variants of *note functools.lru_cache(): 1c8.:

     class LRU(OrderedDict):
         'Limit size, evicting the least recently looked-up key when full'

         def __init__(self, maxsize=128, /, *args, **kwds):
             self.maxsize = maxsize
             super().__init__(*args, **kwds)

         def __getitem__(self, key):
             value = super().__getitem__(key)
             self.move_to_end(key)
             return value

         def __setitem__(self, key, value):
             if key in self:
                 self.move_to_end(key)
             super().__setitem__(key, value)
             if len(self) > self.maxsize:
                 oldest = next(iter(self))
                 del self[oldest]


File: python.info,  Node: UserDict objects,  Next: UserList objects,  Prev: OrderedDict objects,  Up: collections --- 容器資料型態

5.8.3.11 ‘UserDict’ objects
...........................

The class, *note UserDict: 192a. acts as a wrapper around dictionary
objects.  The need for this class has been partially supplanted by the
ability to subclass directly from *note dict: 1b9.; however, this class
can be easier to work with because the underlying dictionary is
accessible as an attribute.

 -- 類別: collections.UserDict ([initialdata])

     Class that simulates a dictionary.  The instance’s contents are
     kept in a regular dictionary, which is accessible via the *note
     data: 194d. attribute of *note UserDict: 192a. instances.  If
     `initialdata' is provided, *note data: 194d. is initialized with
     its contents; note that a reference to `initialdata' will not be
     kept, allowing it be used for other purposes.

     In addition to supporting the methods and operations of mappings,
     *note UserDict: 192a. instances provide the following attribute:

      -- 屬性: data

          A real dictionary used to store the contents of the *note
          UserDict: 192a. class.


File: python.info,  Node: UserList objects,  Next: UserString objects,  Prev: UserDict objects,  Up: collections --- 容器資料型態

5.8.3.12 ‘UserList’ objects
...........................

This class acts as a wrapper around list objects.  It is a useful base
class for your own list-like classes which can inherit from them and
override existing methods or add new ones.  In this way, one can add new
behaviors to lists.

The need for this class has been partially supplanted by the ability to
subclass directly from *note list: 263.; however, this class can be
easier to work with because the underlying list is accessible as an
attribute.

 -- 類別: collections.UserList ([list])

     Class that simulates a list.  The instance’s contents are kept in a
     regular list, which is accessible via the *note data: 194f.
     attribute of *note UserList: 192b. instances.  The instance’s
     contents are initially set to a copy of `list', defaulting to the
     empty list ‘[]’.  `list' can be any iterable, for example a real
     Python list or a *note UserList: 192b. object.

     In addition to supporting the methods and operations of mutable
     sequences, *note UserList: 192b. instances provide the following
     attribute:

      -- 屬性: data

          A real *note list: 263. object used to store the contents of
          the *note UserList: 192b. class.

`Subclassing requirements:' Subclasses of *note UserList: 192b. are
expected to offer a constructor which can be called with either no
arguments or one argument.  List operations which return a new sequence
attempt to create an instance of the actual implementation class.  To do
so, it assumes that the constructor can be called with a single
parameter, which is a sequence object used as a data source.

If a derived class does not wish to comply with this requirement, all of
the special methods supported by this class will need to be overridden;
please consult the sources for information about the methods which need
to be provided in that case.


File: python.info,  Node: UserString objects,  Prev: UserList objects,  Up: collections --- 容器資料型態

5.8.3.13 ‘UserString’ objects
.............................

The class, *note UserString: 6b2. acts as a wrapper around string
objects.  The need for this class has been partially supplanted by the
ability to subclass directly from *note str: 335.; however, this class
can be easier to work with because the underlying string is accessible
as an attribute.

 -- 類別: collections.UserString (seq)

     Class that simulates a string object.  The instance’s content is
     kept in a regular string object, which is accessible via the *note
     data: 1951. attribute of *note UserString: 6b2. instances.  The
     instance’s contents are initially set to a copy of `seq'.  The
     `seq' argument can be any object which can be converted into a
     string using the built-in *note str(): 335. function.

     In addition to supporting the methods and operations of strings,
     *note UserString: 6b2. instances provide the following attribute:

      -- 屬性: data

          A real *note str: 335. object used to store the contents of
          the *note UserString: 6b2. class.

     3.5 版更變: New methods ‘__getnewargs__’, ‘__rmod__’, ‘casefold’,
     ‘format_map’, ‘isprintable’, and ‘maketrans’.


File: python.info,  Node: collections abc --- Abstract Base Classes for Containers,  Next: heapq --- 堆積佇列 heap queue 演算法,  Prev: collections --- 容器資料型態,  Up: Data Types

5.8.4 ‘collections.abc’ — Abstract Base Classes for Containers
--------------------------------------------------------------

3.3 版新加入: Formerly, this module was part of the *note collections:
1e. module.

`Source code:' Lib/_collections_abc.py(1)

__________________________________________________________________

This module provides *note abstract base classes: b38. that can be used
to test whether a class provides a particular interface; for example,
whether it is hashable or whether it is a mapping.

* Menu:

* Collections Abstract Base Classes::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/_collections_abc.py


File: python.info,  Node: Collections Abstract Base Classes,  Up: collections abc --- Abstract Base Classes for Containers

5.8.4.1 Collections Abstract Base Classes
.........................................

The collections module offers the following *note ABCs: b38.:

ABC                            Inherits from              Abstract Methods            Mixin Methods
                                                                                      
-----------------------------------------------------------------------------------------------------------------------------------------------
                                                                                      
*note Container: 1955.                                    ‘__contains__’
                                                          
                                                                                      
*note Hashable: 1956.                                     ‘__hash__’
                                                          
                                                                                      
*note Iterable: 1957.                                     ‘__iter__’
                                                          
                                                                                      
*note Iterator: 1958.          *note Iterable: 1957.      ‘__next__’                  ‘__iter__’
                                                                                      
                                                                                      
*note Reversible: 533.         *note Iterable: 1957.      ‘__reversed__’
                                                          
                                                                                      
*note Generator: 6ba.          *note Iterator: 1958.      ‘send’, ‘throw’             ‘close’, ‘__iter__’, ‘__next__’
                                                                                      
                                                                                      
*note Sized: 1959.                                        ‘__len__’
                                                          
                                                                                      
*note Callable: 195a.                                     ‘__call__’
                                                          
                                                                                      
*note Collection: 532.         *note Sized: 1959,         ‘__contains__’,
                               *note Iterable: 1957,      ‘__iter__’, ‘__len__’
                               *note Container: 1955.     
                               
                                                                                      
*note Sequence: 1635.          *note Reversible: 533,     ‘__getitem__’, ‘__len__’    ‘__contains__’, ‘__iter__’, ‘__reversed__’, ‘index’,
                               *note Collection: 532.                                 and ‘count’
                                                                                      
                                                                                      
*note MutableSequence: 6b1.    *note Sequence: 1635.      ‘__getitem__’,              Inherited *note Sequence: 1635. methods and ‘append’,
                                                          ‘__setitem__’,              ‘reverse’, ‘extend’, ‘pop’, ‘remove’, and ‘__iadd__’
                                                          ‘__delitem__’, ‘__len__’,   
                                                          ‘insert’
                                                          
                                                                                      
*note ByteString: 195b.        *note Sequence: 1635.      ‘__getitem__’, ‘__len__’    Inherited *note Sequence: 1635. methods
                                                                                      
                                                                                      
*note Set: 16df.               *note Collection: 532.     ‘__contains__’,             ‘__le__’, ‘__lt__’, ‘__eq__’, ‘__ne__’, ‘__gt__’,
                                                          ‘__iter__’, ‘__len__’       ‘__ge__’, ‘__and__’, ‘__or__’, ‘__sub__’, ‘__xor__’,
                                                                                      and ‘isdisjoint’
                                                                                      
                                                                                      
*note MutableSet: 195c.        *note Set: 16df.           ‘__contains__’,             Inherited *note Set: 16df. methods and ‘clear’, ‘pop’,
                                                          ‘__iter__’, ‘__len__’,      ‘remove’, ‘__ior__’, ‘__iand__’, ‘__ixor__’, and
                                                          ‘add’, ‘discard’            ‘__isub__’
                                                                                      
                                                                                      
*note Mapping: 1949.           *note Collection: 532.     ‘__getitem__’,              ‘__contains__’, ‘keys’, ‘items’, ‘values’, ‘get’,
                                                          ‘__iter__’, ‘__len__’       ‘__eq__’, and ‘__ne__’
                                                                                      
                                                                                      
*note MutableMapping: 9f4.     *note Mapping: 1949.       ‘__getitem__’,              Inherited *note Mapping: 1949. methods and ‘pop’,
                                                          ‘__setitem__’,              ‘popitem’, ‘clear’, ‘update’, and ‘setdefault’
                                                          ‘__delitem__’,              
                                                          ‘__iter__’, ‘__len__’
                                                          
                                                                                      
*note MappingView: 195d.       *note Sized: 1959.                                     ‘__len__’
                                                                                      
                                                                                      
*note ItemsView: 195e.         *note MappingView: 195d,                               ‘__contains__’, ‘__iter__’
                               *note Set: 16df.                                       
                               
                                                                                      
*note KeysView: 195f.          *note MappingView: 195d,                               ‘__contains__’, ‘__iter__’
                               *note Set: 16df.                                       
                               
                                                                                      
*note ValuesView: 1960.        *note MappingView: 195d,                               ‘__contains__’, ‘__iter__’
                               *note Collection: 532.                                 
                               
                                                                                      
*note Awaitable: 6bb.                                     ‘__await__’
                                                          
                                                                                      
*note Coroutine: 6bc.          *note Awaitable: 6bb.      ‘send’, ‘throw’             ‘close’
                                                                                      
                                                                                      
*note AsyncIterable: 6be.                                 ‘__aiter__’
                                                          
                                                                                      
*note AsyncIterator: 6bd.      *note AsyncIterable: 6be.  ‘__anext__’                 ‘__aiter__’
                                                                                      
                                                                                      
*note AsyncGenerator: 535.     *note AsyncIterator: 6bd.  ‘asend’, ‘athrow’           ‘aclose’, ‘__aiter__’, ‘__anext__’
                                                                                      

 -- 類別: collections.abc.Container

     ABC for classes that provide the *note __contains__(): d2d. method.

 -- 類別: collections.abc.Hashable

     ABC for classes that provide the *note __hash__(): 345. method.

 -- 類別: collections.abc.Sized

     ABC for classes that provide the *note __len__(): dd0. method.

 -- 類別: collections.abc.Callable

     ABC for classes that provide the *note __call__(): 1433. method.

 -- 類別: collections.abc.Iterable

     ABC for classes that provide the *note __iter__(): 514. method.

     Checking ‘isinstance(obj, Iterable)’ detects classes that are
     registered as *note Iterable: 1957. or that have an *note
     __iter__(): 514. method, but it does not detect classes that
     iterate with the *note __getitem__(): 27d. method.  The only
     reliable way to determine whether an object is *note iterable: bb1.
     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__(): 162f. and *note
     __next__(): c69. methods.  See also the definition of *note
     iterator: 1040.

 -- 類別: collections.abc.Reversible

     ABC for iterable classes that also provide the *note
     __reversed__(): 534. method.

     3.6 版新加入.

 -- 類別: collections.abc.Generator

     ABC for generator classes that implement the protocol defined in
     PEP 342(1) that extends iterators with the *note send(): 1494,
     *note throw(): 1496. and *note close(): 1498. methods.  See also
     the definition of *note generator: 9a7.

     3.5 版新加入.

 -- 類別: collections.abc.Sequence
 -- 類別: collections.abc.MutableSequence
 -- 類別: collections.abc.ByteString

     ABCs for read-only and mutable *note sequences: 122d.

     Implementation note: Some of the mixin methods, such as *note
     __iter__(): 514, *note __reversed__(): 534. and ‘index()’, make
     repeated calls to the underlying *note __getitem__(): 27d. method.
     Consequently, if *note __getitem__(): 27d. 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.

 -- 類別: collections.abc.Set
 -- 類別: collections.abc.MutableSet

     ABCs for read-only and mutable sets.

 -- 類別: collections.abc.Mapping
 -- 類別: collections.abc.MutableMapping

     ABCs for read-only and mutable *note mappings: b3e.

 -- 類別: collections.abc.MappingView
 -- 類別: collections.abc.ItemsView
 -- 類別: collections.abc.KeysView
 -- 類別: collections.abc.ValuesView

     ABCs for mapping, items, keys, and values *note views: 194a.

 -- 類別: collections.abc.Awaitable

     ABC for *note awaitable: 51e. objects, which can be used in *note
     await: 1a4. expressions.  Custom implementations must provide the
     *note __await__(): 647. method.

     *note Coroutine: 1a7. objects and instances of the *note Coroutine:
     6bc. ABC are all instances of this ABC.

          備註: In CPython, generator-based coroutines (generators
          decorated with *note types.coroutine(): 781. or *note
          asyncio.coroutine(): 283.) are `awaitables', even though they
          do not have an *note __await__(): 647. method.  Using
          ‘isinstance(gencoro, Awaitable)’ for them will return ‘False’.
          Use *note inspect.isawaitable(): 6fe. to detect them.

     3.5 版新加入.

 -- 類別: collections.abc.Coroutine

     ABC for coroutine compatible classes.  These implement the
     following methods, defined in *note Coroutine Objects: 1432.: *note
     send(): 1493, *note throw(): 1495, and *note close(): 1497.  Custom
     implementations must also implement *note __await__(): 647.  All
     *note Coroutine: 6bc. instances are also instances of *note
     Awaitable: 6bb.  See also the definition of *note coroutine: 1a7.

          備註: In CPython, generator-based coroutines (generators
          decorated with *note types.coroutine(): 781. or *note
          asyncio.coroutine(): 283.) are `awaitables', even though they
          do not have an *note __await__(): 647. method.  Using
          ‘isinstance(gencoro, Coroutine)’ for them will return ‘False’.
          Use *note inspect.isawaitable(): 6fe. to detect them.

     3.5 版新加入.

 -- 類別: collections.abc.AsyncIterable

     ABC for classes that provide ‘__aiter__’ method.  See also the
     definition of *note asynchronous iterable: 645.

     3.5 版新加入.

 -- 類別: collections.abc.AsyncIterator

     ABC for classes that provide ‘__aiter__’ and ‘__anext__’ methods.
     See also the definition of *note asynchronous iterator: 64a.

     3.5 版新加入.

 -- 類別: collections.abc.AsyncGenerator

     ABC for asynchronous generator classes that implement the protocol
     defined in PEP 525(2) and PEP 492(3).

     3.6 版新加入.

These 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: 16df. API, it is only necessary to
supply the three underlying abstract methods: *note __contains__(): d2d,
*note __iter__(): 514, and *note __len__(): dd0.  The ABC supplies the
remaining methods such as *note __and__(): 146b. and ‘isdisjoint()’:

     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: 16df. and *note MutableSet: 195c. as a mixin:

  1. Since some set operations create new sets, the default mixin
     methods need a way to create new instances from an iterable.  The
     class constructor is assumed to have a signature in the form
     ‘ClassName(iterable)’.  That assumption is factored-out to an
     internal classmethod called ‘_from_iterable()’ which calls
     ‘cls(iterable)’ to produce a new set.  If the *note Set: 16df.
     mixin is being used in a class with a different constructor
     signature, you will need to override ‘_from_iterable()’ with a
     classmethod 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__(): ca5. and *note __ge__(): ca7,
     then the other operations will automatically follow suit.

  3. The *note Set: 16df. mixin provides a ‘_hash()’ method to compute a
     hash value for the set; however, *note __hash__(): 345. is not
     defined because not all sets are hashable or immutable.  To add set
     hashability using mixins, inherit from both *note Set(): 16df. and
     *note Hashable(): 1956, then define ‘__hash__ = Set._hash’.

也參考
......

   * OrderedSet recipe(4) for an example built on *note MutableSet:
     195c.

   * For more about ABCs, see the *note abc: 4. module and PEP 3119(5).

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0342

   (2) https://www.python.org/dev/peps/pep-0525

   (3) https://www.python.org/dev/peps/pep-0492

   (4) https://code.activestate.com/recipes/576694/

   (5) https://www.python.org/dev/peps/pep-3119


File: python.info,  Node: heapq --- 堆積佇列 heap queue 演算法,  Next: bisect --- 陣列二分演算法 Array bisection algorithm,  Prev: collections abc --- Abstract Base Classes for Containers,  Up: Data Types

5.8.5 ‘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():
1963. 將一個已經有元素的 list轉成一個 heap。

此模組提供下面的函式

 -- 函式: heapq.heappush (heap, item)

     把 `item' 放進 `heap'，並保持 heap 性質不變。

 -- 函式: heapq.heappop (heap)

     從 `heap' 取出並回傳最小的元素，同時保持 heap 性質不變。如果 heap 是
     空的會產生 *note IndexError: e7a. 錯誤。只存取最小元素但不取出可以
     使用 ‘heap[0]’ 。

 -- 函式: heapq.heappushpop (heap, item)

     將 `item' 放入 heap ，接著從 `heap' 取出並回傳最小的元素。這個組合
     函式比呼叫 *note heappush(): 1964. 之後呼叫 *note heappop(): 1965.
     更有效率。

 -- 函式: heapq.heapify (x)

     在線性時間內將 list `x' 轉為 heap，且過程不會申請額外記憶體。

 -- 函式: heapq.heapreplace (heap, item)

     從 `heap' 取出並回傳最小的元素，接著將新的 `item' 放進heap。heap 的
     大小不會改變。如果 heap 是空的會產生 *note IndexError: e7a. 錯誤。

     這個一次完成的操作會比呼叫 *note heappop(): 1965. 之後呼叫 *note
     heappush(): 1964. 更有效率，並在維護 heap 的大小不變時更為適當，取
     出/放入的組合函式一定會從 heap 回傳一個元素並用 `item' 取代他。

     函式的回傳值可能會大於被加入的 `item' 。如果這不是你期望發生的，可
     以考慮使用 *note heappushpop(): 1966. 替代，他會回傳 heap 的最小值
     和 `item' 兩個當中比較小的那個，並將大的留在 heap 內。

這個模組也提供三個利用 heap 實作的一般用途函式

 -- 函式: heapq.merge (*iterables, key=None, reverse=False)

     合併多個已排序的輸入並產生單一且已排序的輸出（舉例：合併來自多個
     log 檔中有時間戳記的項目）。回傳一個 *note iterator: 1040. 包含已經
     排序的值。

     和 ‘sorted(itertools.chain(*iterables))’ 類似但回傳值是一個
     iterable ，不會一次把所有資料都放進記憶體中，並且假設每一個輸入都已
     經（由小到大）排序過了。

     有兩個選用參數，指定時必須被當作關鍵字參數指定。

     `key' 參數指定了一個 *note key function: 6e5. 引數，用來從每一個輸
     入的元素中決定一個比較的依據。預設的值是 ‘None’ （直接比較元素）。

     `reverse' is a boolean value.  If set to ‘True’, then the input
     elements are merged as if each comparison were reversed.  To
     achieve behavior similar to ‘sorted(itertools.chain(*iterables),
     reverse=True)’, all iterables must be sorted from largest to
     smallest.

     3.5 版更變: 加入選用參數 `key' 和 `reverse' 。

 -- 函式: heapq.nlargest (n, iterable, key=None)

     Return a list with the `n' largest elements from the dataset
     defined by `iterable'.  `key', if provided, specifies a function of
     one argument that is used to extract a comparison key from each
     element in `iterable' (for example, ‘key=str.lower’).  Equivalent
     to: ‘sorted(iterable, key=key, reverse=True)[:n]’.

 -- 函式: heapq.nsmallest (n, iterable, key=None)

     Return a list with the `n' smallest elements from the dataset
     defined by `iterable'.  `key', if provided, specifies a function of
     one argument that is used to extract a comparison key from each
     element in `iterable' (for example, ‘key=str.lower’).  Equivalent
     to: ‘sorted(iterable, key=key)[:n]’.

後兩個函式在 `n' 值比較小時有最好的表現。對於較大的 `n' 值，只用 *note
sorted(): 449. 函式會更有效率。同樣地，當 ‘n==1’ 時，使用內建函式 *note
min(): 80e. 和 *note max(): 80f. 會有更好的效率。如果需要重複使用這些函
式，可以考慮將 iterable 轉成真正的 heap 。

* Menu:

* 基礎範例::
* 優先佇列 (Priority Queue) 實作細節: 優先佇列 Priority Queue 實作細節.
* 原理::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/heapq.py


File: python.info,  Node: 基礎範例,  Next: 優先佇列 Priority Queue 實作細節,  Up: heapq --- 堆積佇列 heap queue 演算法

5.8.5.1 基礎範例
................

A heapsort(1) can be implemented by pushing all values onto a heap and
then popping off the smallest values one at a time:

     >>> 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(): 449. 不同的是，這個實
作不是 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: 優先佇列 Priority Queue 實作細節,  Next: 原理,  Prev: 基礎範例,  Up: heapq --- 堆積佇列 heap queue 演算法

5.8.5.2 優先佇列 (Priority Queue) 實作細節
..........................................

A priority queue(1) is common use for a heap, and it presents several
implementation challenges:

   * 排序的穩定性：你如何將兩個擁有相同 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 做比較。

Another solution to the problem of non-comparable tasks is to create a
wrapper class that ignores the task item and only compares the priority
field:

     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: 優先佇列 Priority Queue 實作細節,  Up: heapq --- 堆積佇列 heap queue 演算法

5.8.5.3 原理
............

Heap 是一個陣列對於所有從0開始的 index `k' 都存在性質 ‘a[k] <= a[2*k+1]’
和 ‘a[k] <= a[2*k+2]’ 。為了方便比較，不存在的元素被視為無限大。一個有趣
的 heap 性質是 ‘a[0]’ 永遠是最小的元素。

The strange invariant above is meant to be an efficient memory
representation for a tournament.  The numbers below are `k', not ‘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

In the tree above, each cell `k' is topping ‘2*k+1’ and ‘2*k+2’.  In a
usual binary tournament we see in sports, each cell is the winner over
the two cells it tops, and we can trace the winner down the tree to see
all opponents s/he had.  However, in many computer applications of such
tournaments, we do not need to trace the history of a winner.  To be
more memory efficient, when a winner is promoted, we try to replace it
by something else at a lower level, and the rule becomes that a cell and
the two cells it tops contain three different items, but the top cell
"wins" over the two topped cells.

If this heap invariant is protected at all time, index 0 is clearly the
overall winner.  The simplest algorithmic way to remove it and find the
"next" winner is to move some loser (let’s say cell 30 in the diagram
above) into the 0 position, and then percolate this new 0 down the tree,
exchanging values, until the invariant is re-established.  This is
clearly logarithmic on the total number of items in the tree.  By
iterating over all items, you get an O(n log n) sort.

A nice feature of this sort is that you can efficiently insert new items
while the sort is going on, provided that the inserted items are not
"better" than the last 0’th element you extracted.  This is especially
useful in simulation contexts, where the tree holds all incoming events,
and the "win" condition means the smallest scheduled time.  When an
event schedules other events for execution, they are scheduled into the
future, so they can easily go into the heap.  So, a heap is a good
structure for implementing schedulers (this is what I used for my MIDI
sequencer :-).

Various structures for implementing schedulers have been extensively
studied, and heaps are good for this, as they are reasonably speedy, the
speed is almost constant, and the worst case is not much different than
the average case.  However, there are other representations which are
more efficient overall, yet the worst cases might be terrible.

Heaps are also very useful in big disk sorts.  You most probably all
know that a big sort implies producing "runs" (which are pre-sorted
sequences, whose size is usually related to the amount of CPU memory),
followed by a merging passes for these runs, which merging is often very
cleverly organised (1).  It is very important that the initial sort
produces the longest runs possible.  Tournaments are a good way to
achieve that.  If, using all the memory available to hold a tournament,
you replace and percolate items that happen to fit the current run,
you’ll produce runs which are twice the size of the memory for random
input, and much better for input fuzzily ordered.

Moreover, if you output the 0’th item on disk and get an input which may
not fit in the current tournament (because the value "wins" over the
last output value), it cannot fit in the heap, so the size of the heap
decreases.  The freed memory could be cleverly reused immediately for
progressively building a second heap, which grows at exactly the same
rate the first heap is melting.  When the first heap completely
vanishes, you switch heaps and start a new run.  Clever and quite
effective!

In a word, heaps are useful memory structures to know.  I use them in a
few applications, and I think it is good to keep a ’heap’ module around.
:-)

註解
....

   ---------- Footnotes ----------

   (1) (1) The disk balancing algorithms which are current, nowadays,
are more annoying than clever, and this is a consequence of the seeking
capabilities of the disks.  On devices which cannot seek, like big tape
drives, the story was quite different, and one had to be very clever to
ensure (far in advance) that each tape movement will be the most
effective possible (that is, will best participate at "progressing" the
merge).  Some tapes were even able to read backwards, and this was also
used to avoid the rewinding time.  Believe me, real good tape sorts were
quite spectacular to watch!  From all times, sorting has always been a
Great Art!  :-)


File: python.info,  Node: bisect --- 陣列二分演算法 Array bisection algorithm,  Next: array --- 高效率的數值型態陣列,  Prev: heapq --- 堆積佇列 heap queue 演算法,  Up: Data Types

5.8.6 ‘bisect’ — 陣列二分演算法 (Array bisection algorithm)
-----------------------------------------------------------

`原始碼：' Lib/bisect.py(1)

__________________________________________________________________

這個模組維護一個已經排序過的 list ，當我們每次做完插入後不需要再次排序整
個 list 。一個很長的 list 的比較操作很花費時間，為了改進這點，這個模組是
其中一個常用的方法。這個模組被命名為 *note bisect: 12. 來自他使用一個基
礎的 bisection 演算法實作。模組的原始碼是這個演算法的一個完善的實作（邊
界條件已經是正確的了）。

此模組提供下面的函式

 -- 函式: bisect.bisect_left (a, x, lo=0, hi=len(a))

     在 `a' 當中找到一個位置，讓 `x' 插入後 `a' 仍然是排序好的。參數
     `lo' 和 `hi' 用來指定 list 中應該被考慮的子區間，預設是考慮整個
     list 。如果 `a' 裡面已經有 `x' 出現，插入的位置會在所有 `x' 的前面
     （左邊）。回傳值可以被當作 ‘list.insert()’ 的第一個參數，但列表 `a'
     必須先排序過。

     回傳的插入位置 `i' 將陣列 `a' 分為兩半，使得 ‘all(val < x for val
     in a[lo:i])’ 都在左側且 ‘all(val >= x for val in a[i:hi])’ 都在右側
     。

 -- 函式: bisect.bisect_right (a, x, lo=0, hi=len(a))
 -- 函式: bisect.bisect (a, x, lo=0, hi=len(a))

     類似 *note bisect_left(): 196f. ，但回傳的插入位置會在所有 `a' 當中
     的 `x' 的後面（右邊）。

     回傳的插入位置 `i' 將陣列 `a' 分為兩半，使得 ‘all(val <= x for val
     in a[lo:i])’ 都在左側且 ‘all(val > x for val in a[i:hi])’ 都在右側
     。

 -- 函式: bisect.insort_left (a, x, lo=0, hi=len(a))

     不破壞 `a' 的排序下插入 `x' ，這等價於
     ‘a.insert(bisect.bisect_left(a, x, lo, hi), x)’ ，注意 `a' 必須是已
     經排序過的 list 。注意搜尋只需要 O(log n) 時間而插入需要很慢的 O(n)
     時間，這使得插入操作主導了需要的花費時間。

 -- 函式: bisect.insort_right (a, x, lo=0, hi=len(a))
 -- 函式: bisect.insort (a, x, lo=0, hi=len(a))

     類似 *note insort_left(): 1972. ，但插入的位置會在所有 `a' 當中的
     `x' 的後面（右邊）。

也參考
......

SortedCollection recipe(2) that uses bisect to build a full-featured
collection class with straight-forward search methods and support for a
key-function.  The keys are precomputed to save unnecessary calls to the
key function during searches.

* Menu:

* Searching Sorted Lists::
* Other Examples::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/bisect.py

   (2) https://code.activestate.com/recipes/577197-sortedcollection/


File: python.info,  Node: Searching Sorted Lists,  Next: Other Examples,  Up: bisect --- 陣列二分演算法 Array bisection algorithm

5.8.6.1 Searching Sorted Lists
..............................

The above *note bisect(): 12. functions are useful for finding insertion
points but can be tricky or awkward to use for common searching tasks.
The following five functions show how to transform them into the
standard lookups for sorted lists:

     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: Other Examples,  Prev: Searching Sorted Lists,  Up: bisect --- 陣列二分演算法 Array bisection algorithm

5.8.6.2 Other Examples
......................

The *note bisect(): 12. function can be useful for numeric table
lookups.  This example uses *note bisect(): 12. to look up a letter
grade for an exam score (say) based on a set of ordered numeric
breakpoints: 90 and up is an ’A’, 80 to 89 is a ’B’, and so on:

     >>> 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']

Unlike the *note sorted(): 449. function, it does not make sense for the
*note bisect(): 12. functions to have `key' or `reversed' arguments
because that would lead to an inefficient design (successive calls to
bisect functions would not "remember" all of the previous key lookups).

Instead, it is better to search a list of precomputed keys to find the
index of the record in question:

     >>> data = [('red', 5), ('blue', 1), ('yellow', 8), ('black', 0)]
     >>> data.sort(key=lambda r: r[1])
     >>> keys = [r[1] for r in data]         # precomputed 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 --- Weak references,  Prev: bisect --- 陣列二分演算法 Array bisection algorithm,  Up: Data Types

5.8.7 ‘array’ — 高效率的數值型態陣列
------------------------------------

__________________________________________________________________

這個模組定義了一個物件型別，可以簡潔的表達一個包含基本數值的陣列：字元、
整數、浮點數。陣列是一個非常類似 list 的序列型態，除了陣列會限制儲存的物
件型別。在建立陣列時可以使用一個字元的 `type code' 來指定儲存的資料型別
。下面是 type codes 的定義。

Type code       C Type                   Python Type             最小所需的位元組            註解
                                                                                             
---------------------------------------------------------------------------------------------------------
                                                                                             
‘'b'’           signed char              int                     1
                                                                 
                                                                                             
‘'B'’           unsigned char            int                     1
                                                                 
                                                                                             
‘'u'’           Py_UNICODE               Unicode character       2                           (1)
                                                                                             
                                                                                             
‘'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. ‘u’ type code 對應到的是 Python 過去的 unicode 字母（ *note
     Py_UNICODE: af3. 是 ‘wchar_t’ ）。根據平台不同，他有可能是 16 bits
     或 32 bits。

     ‘'u'’ 會跟著 *note Py_UNICODE: af3. API 的停用一起被移除。

     Deprecated since version 3.3, will be removed in version 4.0.

實際上數值的表示方法是被機器的架構所決定（更精準地說，被 C 的實作方法決
定）。實際的大小可以透過 ‘itemsize’ 屬性存取。

這個模組定義了下方的型別：

 -- 類別: array.array (typecode[, initializer])

     一個新的陣列中的元素被 `typecode' 限制，並由選用的 `initializer' 參
     數初始化， `initializer' 必須是一個 list、 *note bytes-like object:
     5ed. 或包含適當型別變數的 iterable 。

     如果指定一個 list 或 string ，新的陣列初始化時會傳入 *note
     fromlist(): 197a. 、 *note frombytes(): 197b. 或 *note
     fromunicode(): 197c. 方法（參照下方）將元素新增到其中。其他型態的變
     數則會傳入 *note extend(): 197d. 方法初始化。

     Raises an *note auditing event: e96. ‘array.__new__’ with arguments
     ‘typecode’, ‘initializer’.

 -- Data: array.typecodes

     一個包含所有可用的 type code 的字串。

Array objects support the ordinary sequence operations of indexing,
slicing, concatenation, and multiplication.  When using slice
assignment, the assigned value must be an array object with the same
type code; in all other cases, *note TypeError: 193. is raised.  Array
objects also implement the buffer interface, and may be used wherever
*note bytes-like objects: 5ed. are supported.

提供下方的資料物件與方法。

 -- 屬性: array.typecode

     typecode 字元被用在建立陣列時。

 -- 屬性: array.itemsize

     陣列當中的一個元素在內部需要的位元組 (bytes) 長度。

 -- 成員函式: array.append (x)

     新增一個元素 `x' 到陣列的最尾端。

 -- 成員函式: array.buffer_info ()

     回傳一個 tuple ‘(address, length)’ 表示當前的記憶體位置和陣列儲存元
     素的緩衝區記憶體長度。緩衝區的長度單位是 bytes ，並可以用
     ‘array.buffer_info()[1] * array.itemsize’ 計算得到。這偶爾會在底層
     操作需要記憶體位置的輸出輸入時很有用，例如 ‘ioctl()’ 指令。只要陣列
     存在且沒有使用任何更改長度的操作時，回傳的數值就有效。

          備註: 當使用來自 C 或 C++ 程式碼（這是唯一使得這個資訊有效的途
          徑） 的陣列物件時，更適當的做法是使用陣列物件支援的緩衝區介面
          。這個方法維護了向後兼容性，並應該在新的程式碼中避免。關於緩衝
          區介面的文件在 *note Buffer Protocol: 15ec. 。

 -- 成員函式: array.byteswap ()

     "Byteswap" 所有陣列中的物件。這只有支援物件長度為 1、2、4 或 8 位元
     組的陣列，其他型別的值會導致 *note RuntimeError: 2bb. 。這在從機器
     讀取位元順序不同的檔案時很有用。

 -- 成員函式: array.count (x)

     回傳 `x' 在陣列中出現了幾次。

 -- 成員函式: array.extend (iterable)

     從 `iterable' 中新增元素到陣列的尾端，如果 `iterable' 是另一個陣列
     ，他必須有完全相同的 type code ，如果不同會產生 *note TypeError:
     193. 。如果 `iterable' 不是一個陣列，他必須可以被迭代 (iterable) 且
     其中的元素必須是可以被加入陣列中的正確型態。

 -- 成員函式: array.frombytes (s)

     從字串中新增元素。讀取時會將字串當作一個陣列，裡面包含了 machine
     value（就像從檔案中使用 *note fromfile(): 1985. 方法讀出的資料）。

     3.2 版新加入: 為了更明確，之前的 *note fromstring(): 1986. 被更名為
     *note frombytes(): 197b. 。

 -- 成員函式: array.fromfile (f, n)

     Read `n' items (as machine values) from the *note file object: b47.
     `f' and append them to the end of the array.  If less than `n'
     items are available, *note EOFError: c71. is raised, but the items
     that were available are still inserted into the array.

 -- 成員函式: array.fromlist (list)

     從 list 中新增元素。這等價於 ‘for x in list: a.append(x)’ ，除了有
     型態錯誤產生時，陣列會保持原狀不會被更改。

 -- 成員函式: array.fromstring ()

     *note frombytes(): 197b. 方法的另一個（已經過時的）名字。

     Deprecated since version 3.2, will be removed in version 3.9.

 -- 成員函式: array.fromunicode (s)

     用給定的 unicode 字串擴展這個陣列。陣列必須是型態 ‘u’ 的陣列；其他
     的型態會產生 *note ValueError: 1fc. 錯誤。使用
     ‘array.frombytes(unicodestring.encode(enc))’ 來新增 Unicode 資料到
     一個其他型態的陣列。

 -- 成員函式: array.index (x)

     回傳最小的 `i' ，使得 `i' 是陣列中第一個 `x' 出現的索引值。

 -- 成員函式: array.insert (i, x)

     在位置 `i' 之前插入一個元素 `x' 。負數的索引值會從陣列尾端開始數。

 -- 成員函式: array.pop ([i])

     移除並回傳陣列索引值 `i' 的元素。選擇性的參數 `i' 預設為 ‘-1’ ，所
     以預設會刪除並回傳最後一個元素。

 -- 成員函式: array.remove (x)

     從陣列中刪除第一個出現的 `x' 。

 -- 成員函式: array.reverse ()

     將整個陣列的元素按照順序逆轉。

 -- 成員函式: array.tobytes ()

     將陣列轉為另一個 machine values 的陣列並回傳他的位元組表示（跟用
     *note tofile(): 198c. 方法寫入檔案時的位元序列相同）。

     3.2 版新加入: 為了明確性，過去的 *note tostring(): 198d. 已更名為
     *note tobytes(): 198b. 。

 -- 成員函式: array.tofile (f)

     將所有元素 （以 machine code 的形式）寫入 *note file object: b47.
     `f' 。

 -- 成員函式: array.tolist ()

     不更改元素，將陣列轉為一般的 list 。

 -- 成員函式: array.tostring ()

     *note tobytes(): 198b. 方法的另一個（已經過時的）名字。

     Deprecated since version 3.2, will be removed in version 3.9.

 -- 成員函式: array.tounicode ()

     將陣列轉為一個字串。陣列的型態必須為 ‘u’ 。其他型態的陣列會產生
     *note ValueError: 1fc. 錯誤。使用 ‘array.tobytes().decode(enc)’ 將
     其他型態的陣列轉為字串。

When an array object is printed or converted to a string, it is
represented as ‘array(typecode, initializer)’.  The `initializer' is
omitted if the array is empty, otherwise it is a string if the
`typecode' is ‘'u'’, otherwise it is a list of numbers.  The string is
guaranteed to be able to be converted back to an array with the same
type and value using *note eval(): b95, so long as the *note array: 456.
class has been imported using ‘from array import array’.  Examples:

     array('l')
     array('u', 'hello \u2641')
     array('l', [1, 2, 3, 4, 5])
     array('d', [1.0, 2.0, 3.14])

也參考
......

模組 *note struct: f9.

     將包含不同資料類型的二進位資料包裝與解開包裝。

模組 *note xdrlib: 133.

     將 External Data Representation (XDR) 的資料包裝與解開包裝，這用在
     一些遠端操作的系統 ( remote procedure call systems ) 。

The Numerical Python Documentation(1)

     Python 數值運算的擴充 (The Numeric Python extension, NumPy) 定義了
     另一個陣列型態，更多關於 Python 的數值運算參考
     ‘http://www.numpy.org/’ 。

   ---------- Footnotes ----------

   (1) https://docs.scipy.org/doc/


File: python.info,  Node: weakref --- Weak references,  Next: types --- Dynamic type creation and names for built-in types,  Prev: array --- 高效率的數值型態陣列,  Up: Data Types

5.8.8 ‘weakref’ — Weak references
---------------------------------

`Source code:' Lib/weakref.py(1)

__________________________________________________________________

The *note weakref: 129. module allows the Python programmer to create
`weak references' to objects.

In the following, the term `referent' means the object which is referred
to by a weak reference.

A weak reference to an object is not enough to keep the object alive:
when the only remaining references to a referent are weak references,
*note garbage collection: ecd. is free to destroy the referent and reuse
its memory for something else.  However, until the object is actually
destroyed the weak reference may return the object even if there are no
strong references to it.

A primary use for weak references is to implement caches or mappings
holding large objects, where it’s desired that a large object not be
kept alive solely because it appears in a cache or mapping.

For example, if you have a number of large binary image objects, you may
wish to associate a name with each.  If you used a Python dictionary to
map names to images, or images to names, the image objects would remain
alive just because they appeared as values or keys in the dictionaries.
The *note WeakKeyDictionary: 1992. and *note WeakValueDictionary: 1993.
classes supplied by the *note weakref: 129. module are an alternative,
using weak references to construct mappings that don’t keep objects
alive solely because they appear in the mapping objects.  If, for
example, an image object is a value in a *note WeakValueDictionary:
1993, then when the last remaining references to that image object are
the weak references held by weak mappings, garbage collection can
reclaim the object, and its corresponding entries in weak mappings are
simply deleted.

*note WeakKeyDictionary: 1992. and *note WeakValueDictionary: 1993. use
weak references in their implementation, setting up callback functions
on the weak references that notify the weak dictionaries when a key or
value has been reclaimed by garbage collection.  *note WeakSet: cbd.
implements the *note set: b74. interface, but keeps weak references to
its elements, just like a *note WeakKeyDictionary: 1992. does.

*note finalize: 29e. provides a straight forward way to register a
cleanup function to be called when an object is garbage collected.  This
is simpler to use than setting up a callback function on a raw weak
reference, since the module automatically ensures that the finalizer
remains alive until the object is collected.

Most programs should find that using one of these weak container types
or *note finalize: 29e. is all they need – it’s not usually necessary to
create your own weak references directly.  The low-level machinery is
exposed by the *note weakref: 129. module for the benefit of advanced
uses.

Not all objects can be weakly referenced; those objects which can
include class instances, functions written in Python (but not in C),
instance methods, sets, frozensets, some *note file objects: b47, *note
generators: 9a7, type objects, sockets, arrays, deques, regular
expression pattern objects, and code objects.

3.2 版更變: Added support for thread.lock, threading.Lock, and code
objects.

Several built-in types such as *note list: 263. and *note dict: 1b9. do
not directly support weak references but can add support through
subclassing:

     class Dict(dict):
         pass

     obj = Dict(red=1, green=2, blue=3)   # this object is weak referenceable

`CPython implementation detail:' Other built-in types such as *note
tuple: 483. and *note int: 185. do not support weak references even when
subclassed.

Extension types can easily be made to support weak references; see *note
Weak Reference Support: 1994.

 -- 類別: weakref.ref (object[, callback])

     Return a weak reference to `object'.  The original object can be
     retrieved by calling the reference object if the referent is still
     alive; if the referent is no longer alive, calling the reference
     object will cause *note None: 158. to be returned.  If `callback'
     is provided and not *note None: 158, and the returned weakref
     object is still alive, the callback will be called when the object
     is about to be finalized; the weak reference object will be passed
     as the only parameter to the callback; the referent will no longer
     be available.

     It is allowable for many weak references to be constructed for the
     same object.  Callbacks registered for each weak reference will be
     called from the most recently registered callback to the oldest
     registered callback.

     Exceptions raised by the callback will be noted on the standard
     error output, but cannot be propagated; they are handled in exactly
     the same way as exceptions raised from an object’s *note __del__():
     924. method.

     Weak references are *note hashable: 142e. if the `object' is
     hashable.  They will maintain their hash value even after the
     `object' was deleted.  If *note hash(): 9c9. is called the first
     time only after the `object' was deleted, the call will raise *note
     TypeError: 193.

     Weak references support tests for equality, but not ordering.  If
     the referents are still alive, two references have the same
     equality relationship as their referents (regardless of the
     `callback').  If either referent has been deleted, the references
     are equal only if the reference objects are the same object.

     This is a subclassable type rather than a factory function.

      -- 屬性: __callback__

          This read-only attribute returns the callback currently
          associated to the weakref.  If there is no callback or if the
          referent of the weakref is no longer alive then this attribute
          will have value ‘None’.

     3.4 版更變: Added the *note __callback__: 916. attribute.

 -- 函式: weakref.proxy (object[, callback])

     Return a proxy to `object' which uses a weak reference.  This
     supports use of the proxy in most contexts instead of requiring the
     explicit dereferencing used with weak reference objects.  The
     returned object will have a type of either ‘ProxyType’ or
     ‘CallableProxyType’, depending on whether `object' is callable.
     Proxy objects are not *note hashable: 142e. regardless of the
     referent; this avoids a number of problems related to their
     fundamentally mutable nature, and prevent their use as dictionary
     keys.  `callback' is the same as the parameter of the same name to
     the *note ref(): 915. function.

     3.8 版更變: Extended the operator support on proxy objects to
     include the matrix multiplication operators ‘@’ and ‘@=’.

 -- 函式: weakref.getweakrefcount (object)

     Return the number of weak references and proxies which refer to
     `object'.

 -- 函式: weakref.getweakrefs (object)

     Return a list of all weak reference and proxy objects which refer
     to `object'.

 -- 類別: weakref.WeakKeyDictionary ([dict])

     Mapping class that references keys weakly.  Entries in the
     dictionary will be discarded when there is no longer a strong
     reference to the key.  This can be used to associate additional
     data with an object owned by other parts of an application without
     adding attributes to those objects.  This can be especially useful
     with objects that override attribute accesses.

*note WeakKeyDictionary: 1992. objects have an additional method that
exposes the internal references directly.  The references are not
guaranteed to be "live" at the time they are used, so the result of
calling the references needs to be checked before being used.  This can
be used to avoid creating references that will cause the garbage
collector to keep the keys around longer than needed.

 -- 成員函式: WeakKeyDictionary.keyrefs ()

     Return an iterable of the weak references to the keys.

 -- 類別: weakref.WeakValueDictionary ([dict])

     Mapping class that references values weakly.  Entries in the
     dictionary will be discarded when no strong reference to the value
     exists any more.

*note WeakValueDictionary: 1993. objects have an additional method that
has the same issues as the ‘keyrefs()’ method of *note
WeakKeyDictionary: 1992. objects.

 -- 成員函式: WeakValueDictionary.valuerefs ()

     Return an iterable of the weak references to the values.

 -- 類別: weakref.WeakSet ([elements])

     Set class that keeps weak references to its elements.  An element
     will be discarded when no strong reference to it exists any more.

 -- 類別: weakref.WeakMethod (method)

     A custom *note ref: 915. subclass which simulates a weak reference
     to a bound method (i.e., a method defined on a class and looked up
     on an instance).  Since a bound method is ephemeral, a standard
     weak reference cannot keep hold of it.  *note WeakMethod: 914. has
     special code to recreate the bound method until either the object
     or the original function dies:

          >>> 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()
          >>>

     3.4 版新加入.

 -- 類別: weakref.finalize (obj, func, *args, **kwargs)

     Return a callable finalizer object which will be called when `obj'
     is garbage collected.  Unlike an ordinary weak reference, a
     finalizer will always survive until the reference object is
     collected, greatly simplifying lifecycle management.

     A finalizer is considered `alive' until it is called (either
     explicitly or at garbage collection), and after that it is `dead'.
     Calling a live finalizer returns the result of evaluating
     ‘func(*arg, **kwargs)’, whereas calling a dead finalizer returns
     *note None: 158.

     Exceptions raised by finalizer callbacks during garbage collection
     will be shown on the standard error output, but cannot be
     propagated.  They are handled in the same way as exceptions raised
     from an object’s *note __del__(): 924. method or a weak reference’s
     callback.

     When the program exits, each remaining live finalizer is called
     unless its *note atexit: c. attribute has been set to false.  They
     are called in reverse order of creation.

     A finalizer will never invoke its callback during the later part of
     the *note interpreter shutdown: 768. when module globals are liable
     to have been replaced by *note None: 158.

      -- 成員函式: __call__ ()

          If `self' is alive then mark it as dead and return the result
          of calling ‘func(*args, **kwargs)’.  If `self' is dead then
          return *note None: 158.

      -- 成員函式: detach ()

          If `self' is alive then mark it as dead and return the tuple
          ‘(obj, func, args, kwargs)’.  If `self' is dead then return
          *note None: 158.

      -- 成員函式: peek ()

          If `self' is alive then return the tuple ‘(obj, func, args,
          kwargs)’.  If `self' is dead then return *note None: 158.

      -- 屬性: alive

          Property which is true if the finalizer is alive, false
          otherwise.

      -- 屬性: atexit

          A writable boolean property which by default is true.  When
          the program exits, it calls all remaining live finalizers for
          which *note atexit: 199d. is true.  They are called in reverse
          order of creation.

          備註: It is important to ensure that `func', `args' and
          `kwargs' do not own any references to `obj', either directly
          or indirectly, since otherwise `obj' will never be garbage
          collected.  In particular, `func' should not be a bound method
          of `obj'.

     3.4 版新加入.

 -- Data: weakref.ReferenceType

     The type object for weak references objects.

 -- Data: weakref.ProxyType

     The type object for proxies of objects which are not callable.

 -- Data: weakref.CallableProxyType

     The type object for proxies of callable objects.

 -- Data: weakref.ProxyTypes

     Sequence containing all the type objects for proxies.  This can
     make it simpler to test if an object is a proxy without being
     dependent on naming both proxy types.

也參考
......

PEP 205(2) - Weak References

     The proposal and rationale for this feature, including links to
     earlier implementations and information about similar features in
     other languages.

* Menu:

* Weak Reference Objects::
* Example: Example<2>.
* Finalizer Objects::
* Comparing finalizers with __del__() methods: Comparing finalizers with __del__ methods.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/weakref.py

   (2) https://www.python.org/dev/peps/pep-0205


File: python.info,  Node: Weak Reference Objects,  Next: Example<2>,  Up: weakref --- Weak references

5.8.8.1 Weak Reference Objects
..............................

Weak reference objects have no methods and no attributes besides *note
ref.__callback__: 916.  A weak reference object allows the referent to
be obtained, if it still exists, by calling it:

     >>> import weakref
     >>> class Object:
     ...     pass
     ...
     >>> o = Object()
     >>> r = weakref.ref(o)
     >>> o2 = r()
     >>> o is o2
     True

If the referent no longer exists, calling the reference object returns
*note None: 158.:

     >>> del o, o2
     >>> print(r())
     None

Testing that a weak reference object is still live should be done using
the expression ‘ref() is not None’.  Normally, application code that
needs to use a reference object should follow this pattern:

     # 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()

Using a separate test for "liveness" creates race conditions in threaded
applications; another thread can cause a weak reference to become
invalidated before the weak reference is called; the idiom shown above
is safe in threaded applications as well as single-threaded
applications.

Specialized versions of *note ref: 915. objects can be created through
subclassing.  This is used in the implementation of the *note
WeakValueDictionary: 1993. to reduce the memory overhead for each entry
in the mapping.  This may be most useful to associate additional
information with a reference, but could also be used to insert
additional processing on calls to retrieve the referent.

This example shows how a subclass of *note ref: 915. can be used to
store additional information about an object and affect the value that’s
returned when the referent is accessed:

     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: Example<2>,  Next: Finalizer Objects,  Prev: Weak Reference Objects,  Up: weakref --- Weak references

5.8.8.2 Example
...............

This simple example shows how an application can use object IDs to
retrieve objects that it has seen before.  The IDs of the objects can
then be used in other data structures without forcing the objects to
remain alive, but the objects can still be retrieved by ID if they do.

     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: Finalizer Objects,  Next: Comparing finalizers with __del__ methods,  Prev: Example<2>,  Up: weakref --- Weak references

5.8.8.3 Finalizer Objects
.........................

The main benefit of using *note finalize: 29e. is that it makes it
simple to register a callback without needing to preserve the returned
finalizer object.  For instance

     >>> 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!

The finalizer can be called directly as well.  However the finalizer
will invoke the callback at most once.

     >>> 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

You can unregister a finalizer using its *note detach(): 199a. method.
This kills the finalizer and returns the arguments passed to the
constructor when it was created.

     >>> 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

Unless you set the *note atexit: 199d. attribute to *note False: 38d, a
finalizer will be called when the program exits if it is still alive.
For instance

     >>> 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: Comparing finalizers with __del__ methods,  Prev: Finalizer Objects,  Up: weakref --- Weak references

5.8.8.4 Comparing finalizers with ‘__del__()’ methods
.....................................................

Suppose we want to create a class whose instances represent temporary
directories.  The directories should be deleted with their contents when
the first of the following events occurs:

   * the object is garbage collected,

   * the object’s ‘remove()’ method is called, or

   * the program exits.

We might try to implement the class using a *note __del__(): 924. method
as follows:

     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()

Starting with Python 3.4, *note __del__(): 924. methods no longer
prevent reference cycles from being garbage collected, and module
globals are no longer forced to *note None: 158. during *note
interpreter shutdown: 768.  So this code should work without any issues
on CPython.

However, handling of *note __del__(): 924. methods is notoriously
implementation specific, since it depends on internal details of the
interpreter’s garbage collector implementation.

A more robust alternative can be to define a finalizer which only
references the specific functions and objects that it needs, rather than
having access to the full state of the object:

     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

Defined like this, our finalizer only receives a reference to the
details it needs to clean up the directory appropriately.  If the object
never gets garbage collected the finalizer will still be called at exit.

The other advantage of weakref based finalizers is that they can be used
to register finalizers for classes where the definition is controlled by
a third party, such as running code when a module is unloaded:

     import weakref, sys
     def unloading_module():
         # implicit reference to the module globals from the function body
     weakref.finalize(sys.modules[__name__], unloading_module)

     備註: If you create a finalizer object in a daemonic thread just as
     the program exits then there is the possibility that the finalizer
     does not get called at exit.  However, in a daemonic thread *note
     atexit.register(): e8a, ‘try: ... finally: ...’ and ‘with: ...’ do
     not guarantee that cleanup occurs either.


File: python.info,  Node: types --- Dynamic type creation and names for built-in types,  Next: copy --- Shallow and deep copy operations,  Prev: weakref --- Weak references,  Up: Data Types

5.8.9 ‘types’ — Dynamic type creation and names for built-in types
------------------------------------------------------------------

`Source code:' 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:
185. or *note str: 335. 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.8/Lib/types.py


File: python.info,  Node: Dynamic Type Creation,  Next: Standard Interpreter Types,  Up: types --- Dynamic type creation and names for built-in types

5.8.9.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: 144d.

     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: 60d, and returns a tuple where each such object that
     has an ‘__mro_entries__’ method is replaced with an unpacked result
     of calling this method.  If a `bases' item is an instance of *note
     type: 60d, or it doesn’t have an ‘__mro_entries__’ method, then it
     is included in the return tuple unchanged.

     3.7 版新加入.

也參考
......

PEP 560(3) - Core support for typing module and generic types

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3115

   (2) https://www.python.org/dev/peps/pep-0560

   (3) https://www.python.org/dev/peps/pep-0560


File: python.info,  Node: Standard Interpreter Types,  Next: Additional Utility Classes and Functions,  Prev: Dynamic Type Creation,  Up: types --- Dynamic type creation and names for built-in types

5.8.9.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(): 454. or *note
issubclass(): 455. checks.

If you instantiate any of these types, note that signatures may vary
between Python versions.

Standard names are defined for the following types:

 -- Data: types.FunctionType
 -- Data: types.LambdaType

     The type of user-defined functions and functions created by *note
     lambda: c34. expressions.

     Raises an *note auditing event: e96. ‘function.__new__’ with
     argument ‘code’.

     The audit event only occurs for direct instantiation of function
     objects, and is not raised for normal compilation.

 -- Data: types.GeneratorType

     The type of *note generator: 9a7.-iterator objects, created by
     generator functions.

 -- Data: types.CoroutineType

     The type of *note coroutine: 1a7. objects, created by *note async
     def: 285. functions.

     3.5 版新加入.

 -- Data: types.AsyncGeneratorType

     The type of *note asynchronous generator: 1508.-iterator objects,
     created by asynchronous generator functions.

     3.6 版新加入.

 -- 類別: types.CodeType (**kwargs)

     The type for code objects such as returned by *note compile(): 1b5.

     Raises an *note auditing event: e96. ‘code.__new__’ with arguments
     ‘code’, ‘filename’, ‘name’, ‘argcount’, ‘posonlyargcount’,
     ‘kwonlyargcount’, ‘nlocals’, ‘stacksize’, ‘flags’.

     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.

      -- 成員函式: replace (**kwargs)

          Return a copy of the code object with new values for the
          specified fields.

          3.8 版新加入.

 -- Data: types.CellType

     The type for cell objects: such objects are used as containers for
     a function’s free variables.

     3.8 版新加入.

 -- Data: types.MethodType

     The type of methods of user-defined class instances.

 -- Data: types.BuiltinFunctionType
 -- Data: types.BuiltinMethodType

     The type of built-in functions like *note len(): 151. or *note
     sys.exit(): ce7, and methods of built-in classes.  (Here, the term
     "built-in" means "written in C".)

 -- Data: types.WrapperDescriptorType

     The type of methods of some built-in data types and base classes
     such as *note object.__init__(): d63. or *note object.__lt__():
     c39.

     3.7 版新加入.

 -- Data: 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 版新加入.

 -- Data: types.MethodDescriptorType

     The type of methods of some built-in data types such as *note
     str.join(): 1637.

     3.7 版新加入.

 -- Data: 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: 14b2.  The constructor takes the name of
     the module to be created and optionally its *note docstring: 15ba.

          備註: Use *note importlib.util.module_from_spec(): 6f5. to
          create a new module if you wish to set the various
          import-controlled attributes.

      -- 屬性: __doc__

          The *note docstring: 15ba. of the module.  Defaults to ‘None’.

      -- 屬性: __loader__

          The *note loader: 14c0. which loaded the module.  Defaults to
          ‘None’.

          This attribute is to match *note
          importlib.machinery.ModuleSpec.loader: 19b7. as stored in the
          attr:‘__spec__’ object.

               備註: A future version of Python may stop setting this
               attribute by default.  To guard against this potential
               change, preferrably read from the *note __spec__: ebd.
               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: 19b9.

      -- 屬性: __package__

          Which *note package: ebb. 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__: d17. if
          the module is a package itself).  Defaults to ‘None’.

          This attribute is to match *note
          importlib.machinery.ModuleSpec.parent: 19bb. as stored in the
          attr:‘__spec__’ object.

               備註: A future version of Python may stop setting this
               attribute by default.  To guard against this potential
               change, preferrably read from the *note __spec__: ebd.
               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 the module’s import-system-related state.
          Expected to be an instance of *note
          importlib.machinery.ModuleSpec: 14cb.

          3.4 版新加入.

 -- 類別: types.TracebackType (tb_next, tb_frame, tb_lasti, tb_lineno)

     The type of traceback objects such as found in ‘sys.exc_info()[2]’.

     See *note the language reference: 33b. for details of the available
     attributes and operations, and guidance on creating tracebacks
     dynamically.

 -- Data: types.FrameType

     The type of frame objects such as found in ‘tb.tb_frame’ if ‘tb’ is
     a traceback object.

     See *note the language reference: 1437. for details of the
     available attributes and operations.

 -- Data: types.GetSetDescriptorType

     The type of objects defined in extension modules with
     ‘PyGetSetDef’, such as ‘FrameType.f_locals’ or
     ‘array.array.typecode’.  This type is used as descriptor for object
     attributes; it has the same purpose as the *note property: 1d8.
     type, but for classes defined in extension modules.

 -- Data: 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: 1d8. type, but for classes defined in extension modules.

     `CPython implementation detail:' 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 版新加入.

      -- 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: 2c8. 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: 2c8.

      -- 成員函式: 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.


File: python.info,  Node: Additional Utility Classes and Functions,  Next: Coroutine Utility Functions,  Prev: Standard Interpreter Types,  Up: types --- Dynamic type creation and names for built-in types

5.8.9.3 Additional Utility Classes and Functions
................................................

 -- 類別: types.SimpleNamespace

     A simple *note object: 2b1. subclass that provides attribute access
     to its namespace, as well as a meaningful repr.

     Unlike *note object: 2b1, with ‘SimpleNamespace’ you can add and
     remove attributes.  If a ‘SimpleNamespace’ object is initialized
     with keyword arguments, those are directly added to the underlying
     namespace.

     The type is roughly equivalent to the following code:

          class SimpleNamespace:
              def __init__(self, /, **kwargs):
                  self.__dict__.update(kwargs)

              def __repr__(self):
                  keys = sorted(self.__dict__)
                  items = ("{}={!r}".format(k, self.__dict__[k]) for k in keys)
                  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(): 1b8. instead.

     3.3 版新加入.

 -- 函式: 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 Enum for an
     example).

     3.4 版新加入.


File: python.info,  Node: Coroutine Utility Functions,  Prev: Additional Utility Classes and Functions,  Up: types --- Dynamic type creation and names for built-in types

5.8.9.4 Coroutine Utility Functions
...................................

 -- 函式: types.coroutine (gen_func)

     This function transforms a *note generator: 9a7. function into a
     *note coroutine function: 644. which returns a generator-based
     coroutine.  The generator-based coroutine is still a *note
     generator iterator: 45c, but is also considered to be a *note
     coroutine: 1a7. object and is *note awaitable: 51e.  However, it
     may not necessarily implement the *note __await__(): 647. 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: 6ba, 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 and deep copy operations,  Next: pprint --- Data pretty printer,  Prev: types --- Dynamic type creation and names for built-in types,  Up: Data Types

5.8.10 ‘copy’ — Shallow and deep copy operations
------------------------------------------------

`Source code:' Lib/copy.py(1)

__________________________________________________________________

Assignment statements in Python do not copy objects, they create
bindings between a target and an object.  For collections that are
mutable or contain mutable items, a copy is sometimes needed so one can
change one copy without changing the other.  This module provides
generic shallow and deep copy operations (explained below).

Interface summary:

 -- 函式: copy.copy (x)

     Return a shallow copy of `x'.

 -- 函式: copy.deepcopy (x[, memo])

     Return a deep copy of `x'.

 -- 例外: copy.Error

     Raised for module specific errors.
The difference between shallow and deep copying is only relevant for
compound objects (objects that contain other objects, like lists or
class instances):

   * A `shallow copy' constructs a new compound object and then (to the
     extent possible) inserts `references' into it to the objects found
     in the original.

   * A `deep copy' constructs a new compound object and then,
     recursively, inserts `copies' into it of the objects found in the
     original.

Two problems often exist with deep copy operations that don’t exist with
shallow copy operations:

   * Recursive objects (compound objects that, directly or indirectly,
     contain a reference to themselves) may cause a recursive loop.

   * Because deep copy copies everything it may copy too much, such as
     data which is intended to be shared between copies.

The *note deepcopy(): 3d1. function avoids these problems by:

   * keeping a ‘memo’ dictionary of objects already copied during the
     current copying pass; and

   * letting user-defined classes override the copying operation or the
     set of components copied.

This module does not copy types like module, method, stack trace, stack
frame, file, socket, window, array, or any similar types.  It does
"copy" functions and classes (shallow and deeply), by returning the
original object unchanged; this is compatible with the way these are
treated by the *note pickle: cb. module.

Shallow copies of dictionaries can be made using *note dict.copy(): 44b,
and of lists by assigning a slice of the entire list, for example,
‘copied_list = original_list[:]’.

Classes can use the same interfaces to control copying that they use to
control pickling.  See the description of module *note pickle: cb. for
information on these methods.  In fact, the *note copy: 26. module uses
the registered pickle functions from the *note copyreg: 27. module.

In order for a class to define its own copy implementation, it can
define special methods ‘__copy__()’ and ‘__deepcopy__()’.  The former is
called to implement the shallow copy operation; no additional arguments
are passed.  The latter is 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(): 3d1. function with the
component as first argument and the memo dictionary as second argument.

也參考
......

Module *note pickle: cb.

     Discussion of the special methods used to support object state
     retrieval and restoration.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/copy.py


File: python.info,  Node: pprint --- Data pretty printer,  Next: reprlib --- Alternate repr implementation,  Prev: copy --- Shallow and deep copy operations,  Up: Data Types

5.8.11 ‘pprint’ — Data pretty printer
-------------------------------------

`Source code:' Lib/pprint.py(1)

__________________________________________________________________

The *note pprint: d3. 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.  Construct *note PrettyPrinter: 89a. objects explicitly if you
need to adjust the width constraint.

Dictionaries are sorted by key before the display is computed.

The *note pprint: d3. module defines one class:

 -- 類別: pprint.PrettyPrinter (indent=1, width=80, depth=None,
          stream=None, *, compact=False, sort_dicts=True)

     Construct a *note PrettyPrinter: 89a. instance.  This constructor
     understands several keyword parameters.  An output stream may be
     set using the `stream' keyword; the only method used on the stream
     object is the file protocol’s ‘write()’ method.  If not specified,
     the *note PrettyPrinter: 89a. adopts ‘sys.stdout’.  The amount of
     indentation added for each recursive level is specified by
     `indent'; the default is one.  Other values can cause output to
     look a little odd, but can make nesting easier to spot.  The number
     of levels which may be printed is controlled by `depth'; if the
     data structure being printed is too deep, the next contained level
     is replaced by ‘...’.  By default, there is no constraint on the
     depth of the objects being formatted.  The desired output width is
     constrained using the `width' parameter; the default is 80
     characters.  If a structure cannot be formatted within the
     constrained width, a best effort will be made.  If `compact' is
     false (the default) each item of a long sequence will be formatted
     on a separate line.  If `compact' is true, as many items as will
     fit within the `width' will be formatted on each output line.  If
     `sort_dicts' is true (the default), dictionaries will be formatted
     with their keys sorted, otherwise they will display in insertion
     order.

     3.4 版更變: Added the `compact' parameter.

     3.8 版更變: Added the `sort_dicts' parameter.

          >>> 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', (...)))))))

The *note pprint: d3. module also provides several shortcut functions:

 -- 函式: pprint.pformat (object, indent=1, width=80, depth=None, *,
          compact=False, sort_dicts=True)

     Return the formatted representation of `object' as a string.
     `indent', `width', `depth', `compact' and `sort_dicts' will be
     passed to the *note PrettyPrinter: 89a. constructor as formatting
     parameters.

     3.4 版更變: Added the `compact' parameter.

     3.8 版更變: Added the `sort_dicts' parameter.

 -- 函式: pprint.pp (object, *args, sort_dicts=False, **kwargs)

     Prints the formatted representation of `object' followed by a
     newline.  If `sort_dicts' is false (the default), dictionaries will
     be displayed with their keys in insertion order, otherwise the dict
     keys will be sorted.  `args' and `kwargs' will be passed to *note
     pprint(): d3. as formatting parameters.

     3.8 版新加入.

 -- 函式: pprint.pprint (object, stream=None, indent=1, width=80,
          depth=None, *, compact=False, sort_dicts=True)

     Prints the formatted representation of `object' on `stream',
     followed by a newline.  If `stream' is ‘None’, ‘sys.stdout’ is
     used.  This may be used in the interactive interpreter instead of
     the *note print(): 88b. function for inspecting values (you can
     even reassign ‘print = pprint.pprint’ for use within a scope).
     `indent', `width', `depth', `compact' and `sort_dicts' will be
     passed to the *note PrettyPrinter: 89a. constructor as formatting
     parameters.

     3.4 版更變: Added the `compact' parameter.

     3.8 版更變: Added the `sort_dicts' parameter.

          >>> import pprint
          >>> stuff = ['spam', 'eggs', 'lumberjack', 'knights', 'ni']
          >>> stuff.insert(0, stuff)
          >>> pprint.pprint(stuff)
          [<Recursion on list with id=...>,
           'spam',
           'eggs',
           'lumberjack',
           'knights',
           'ni']

 -- 函式: pprint.isreadable (object)

     Determine if the formatted representation of `object' is
     "readable", or can be used to reconstruct the value using *note
     eval(): b95.  This always returns ‘False’ for recursive objects.

          >>> pprint.isreadable(stuff)
          False

 -- 函式: pprint.isrecursive (object)

     Determine if `object' requires a recursive representation.

One more support function is also defined:

 -- 函式: pprint.saferepr (object)

     Return a string representation of `object', protected against
     recursive data structures.  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']"

* Menu:

* PrettyPrinter Objects::
* Example: Example<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/pprint.py


File: python.info,  Node: PrettyPrinter Objects,  Next: Example<3>,  Up: pprint --- Data pretty printer

5.8.11.1 PrettyPrinter Objects
..............................

*note PrettyPrinter: 89a. 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: 89a.
     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: 89a. 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(): b95.  Note that this returns ‘False’ for recursive objects.
     If the `depth' parameter of the *note PrettyPrinter: 89a. 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(): 19ce. 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(): d8b. 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(): 19d5. 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: Example<3>,  Prev: PrettyPrinter Objects,  Up: pprint --- Data pretty printer

5.8.11.2 Example
................

To demonstrate several uses of the *note pprint(): d3. 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 pprint(): d3. shows the whole object:

     >>> pprint.pprint(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.pprint(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.pprint(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 --- Alternate repr implementation,  Next: enum --- Support for enumerations,  Prev: pprint --- Data pretty printer,  Up: Data Types

5.8.12 ‘reprlib’ — Alternate ‘repr()’ implementation
----------------------------------------------------

`Source code:' Lib/reprlib.py(1)

__________________________________________________________________

The *note reprlib: e0. 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

     Class which provides formatting services useful in implementing
     functions similar to the built-in *note repr(): 7d1.; size limits
     for different object types are added to avoid the generation of
     representations which are excessively long.

 -- Data: reprlib.aRepr

     This is an instance of *note Repr: 19da. which is used to provide
     the *note repr(): 19dc. function described below.  Changing the
     attributes of this object will affect the size limits used by *note
     repr(): 19dc. and the Python debugger.

 -- 函式: reprlib.repr (obj)

     This is the *note repr(): 19dd. 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__(): 343. and substituting
a placeholder string instead.

 -- 函式: @reprlib.recursive_repr (fillvalue="...")

     Decorator for *note __repr__(): 343. methods to detect recursive
     calls within the same thread.  If a recursive call is made, the
     `fillvalue' is returned, otherwise, the usual *note __repr__():
     343. 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 Objects::
* Subclassing Repr Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/reprlib.py


File: python.info,  Node: Repr Objects,  Next: Subclassing Repr Objects,  Up: reprlib --- Alternate repr implementation

5.8.12.1 Repr Objects
.....................

*note Repr: 19da. 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.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: 19e1, ‘5’ for *note
     maxarray: 19e7, 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: 19da.
     object.  It is applied in a similar manner as *note maxstring:
     19e9.  The default is ‘20’.

 -- 成員函式: Repr.repr (obj)

     The equivalent to the built-in *note repr(): 7d1. that uses the
     formatting imposed by the instance.

 -- 成員函式: Repr.repr1 (obj, level)

     Recursive implementation used by *note repr(): 19dd.  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(): 19eb. 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(): 19eb.  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 Objects,  Up: reprlib --- Alternate repr implementation

5.8.12.2 Subclassing Repr Objects
.................................

The use of dynamic dispatching by *note Repr.repr1(): 19eb. allows
subclasses of *note Repr: 19da. 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))         # prints '<stdin>'


File: python.info,  Node: enum --- Support for enumerations,  Prev: reprlib --- Alternate repr implementation,  Up: Data Types

5.8.13 ‘enum’ — Support for enumerations
----------------------------------------

3.4 版新加入.

`Source code:' Lib/enum.py(1)

__________________________________________________________________

An enumeration is a set of symbolic names (members) bound to unique,
constant values.  Within an enumeration, the members can be compared by
identity, and the enumeration itself can be iterated over.

     備註: Case of Enum Members

     Because Enums are used to represent constants we recommend using
     UPPER_CASE names for enum members, and will be using that style in
     our examples.

* Menu:

* Module Contents: Module Contents<2>.
* Creating an Enum::
* Programmatic access to enumeration members and their attributes::
* Duplicating enum members and values::
* Ensuring unique enumeration values::
* Using automatic values::
* Iteration::
* Comparisons: Comparisons<3>.
* Allowed members and attributes of enumerations::
* Restricted Enum subclassing::
* Pickling::
* Functional API::
* Derived Enumerations::
* When to use __new__() vs. __init__(): When to use __new__ vs __init__.
* Interesting examples::
* How are Enums different?::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/enum.py


File: python.info,  Node: Module Contents<2>,  Next: Creating an Enum,  Up: enum --- Support for enumerations

5.8.13.1 Module Contents
........................

This module defines four enumeration classes that can be used to define
unique sets of names and values: *note Enum: 38c, *note IntEnum: 592,
*note Flag: 54a, and *note IntFlag: 1760.  It also defines one
decorator, *note unique(): 19f1, and one helper, *note auto: 54b.

 -- 類別: enum.Enum

     Base class for creating enumerated constants.  See section *note
     Functional API: 19f2. for an alternate construction syntax.

 -- 類別: enum.IntEnum

     Base class for creating enumerated constants that are also
     subclasses of *note int: 185.

 -- 類別: enum.IntFlag

     Base class for creating enumerated constants that can be combined
     using the bitwise operators without losing their *note IntFlag:
     1760. membership.  *note IntFlag: 1760. members are also subclasses
     of *note int: 185.

 -- 類別: enum.Flag

     Base class for creating enumerated constants that can be combined
     using the bitwise operations without losing their *note Flag: 54a.
     membership.

 -- 函式: enum.unique ()

     Enum class decorator that ensures only one name is bound to any one
     value.

 -- 類別: enum.auto

     Instances are replaced with an appropriate value for Enum members.
     Initial value starts at 1.

3.6 版新加入: ‘Flag’, ‘IntFlag’, ‘auto’


File: python.info,  Node: Creating an Enum,  Next: Programmatic access to enumeration members and their attributes,  Prev: Module Contents<2>,  Up: enum --- Support for enumerations

5.8.13.2 Creating an Enum
.........................

Enumerations are created using the *note class: c6f. syntax, which makes
them easy to read and write.  An alternative creation method is
described in *note Functional API: 19f2.  To define an enumeration,
subclass *note Enum: 38c. as follows:

     >>> from enum import Enum
     >>> class Color(Enum):
     ...     RED = 1
     ...     GREEN = 2
     ...     BLUE = 3
     ...

     備註: Enum member values

     Member values can be anything: *note int: 185, *note str: 335,
     etc..  If the exact value is unimportant you may use *note auto:
     54b. instances and an appropriate value will be chosen for you.
     Care must be taken if you mix *note auto: 54b. with other values.

     備註: Nomenclature

        - The class ‘Color’ is an `enumeration' (or `enum')

        - The attributes ‘Color.RED’, ‘Color.GREEN’, etc., are
          `enumeration members' (or `enum members') and are functionally
          constants.

        - The enum members have `names' and `values' (the name of
          ‘Color.RED’ is ‘RED’, the value of ‘Color.BLUE’ is ‘3’, etc.)

     備註: Even though we use the *note class: c6f. syntax to create
     Enums, Enums are not normal Python classes.  See *note How are
     Enums different?: 19f4. for more details.

Enumeration members have human readable string representations:

     >>> print(Color.RED)
     Color.RED

...while their ‘repr’ has more information:

     >>> print(repr(Color.RED))
     <Color.RED: 1>

The `type' of an enumeration member is the enumeration it belongs to:

     >>> type(Color.RED)
     <enum 'Color'>
     >>> isinstance(Color.GREEN, Color)
     True
     >>>

Enum members also have a property that contains just their item name:

     >>> print(Color.RED.name)
     RED

Enumerations support iteration, in definition order:

     >>> class Shake(Enum):
     ...     VANILLA = 7
     ...     CHOCOLATE = 4
     ...     COOKIES = 9
     ...     MINT = 3
     ...
     >>> for shake in Shake:
     ...     print(shake)
     ...
     Shake.VANILLA
     Shake.CHOCOLATE
     Shake.COOKIES
     Shake.MINT

Enumeration members are hashable, so they can be used in dictionaries
and sets:

     >>> apples = {}
     >>> apples[Color.RED] = 'red delicious'
     >>> apples[Color.GREEN] = 'granny smith'
     >>> apples == {Color.RED: 'red delicious', Color.GREEN: 'granny smith'}
     True


File: python.info,  Node: Programmatic access to enumeration members and their attributes,  Next: Duplicating enum members and values,  Prev: Creating an Enum,  Up: enum --- Support for enumerations

5.8.13.3 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 --- Support for enumerations

5.8.13.4 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: Attempted to reuse key: 'SQUARE'

However, two enum members are allowed to have the same value.  Given two
members A and B with the same value (and A defined first), B is an alias
to A. By-value lookup of the value of A and B will return A. By-name
lookup of B will also return 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 --- Support for enumerations

5.8.13.5 Ensuring unique enumeration values
...........................................

By default, enumerations allow multiple names as aliases for the same
value.  When this behavior isn’t desired, the following decorator can be
used to ensure each value is used only once in the enumeration:

 -- 函式: @enum.unique

A *note class: c6f. decorator specifically for enumerations.  It
searches an enumeration’s ‘__members__’ gathering any aliases it finds;
if any are found *note ValueError: 1fc. is raised with the details:

     >>> 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,  Prev: Ensuring unique enumeration values,  Up: enum --- Support for enumerations

5.8.13.6 Using automatic values
...............................

If the exact value is unimportant you can use *note auto: 54b.:

     >>> 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>]

The values are chosen by ‘_generate_next_value_()’, which can be
overridden:

     >>> class AutoName(Enum):
     ...     def _generate_next_value_(name, start, count, last_values):
     ...         return name
     ...
     >>> class Ordinal(AutoName):
     ...     NORTH = auto()
     ...     SOUTH = auto()
     ...     EAST = auto()
     ...     WEST = auto()
     ...
     >>> list(Ordinal)
     [<Ordinal.NORTH: 'NORTH'>, <Ordinal.SOUTH: 'SOUTH'>, <Ordinal.EAST: 'EAST'>, <Ordinal.WEST: 'WEST'>]

     備註: The goal of the default ‘_generate_next_value_()’ method is
     to provide the next *note int: 185. in sequence with the last *note
     int: 185. provided, but the way it does this is an implementation
     detail and may change.

     備註: The ‘_generate_next_value_()’ method must be defined before
     any members.


File: python.info,  Node: Iteration,  Next: Comparisons<3>,  Prev: Using automatic values,  Up: enum --- Support for enumerations

5.8.13.7 Iteration
..................

Iterating over the members of an enum does not provide the aliases:

     >>> list(Shape)
     [<Shape.SQUARE: 2>, <Shape.DIAMOND: 1>, <Shape.CIRCLE: 3>]

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']


File: python.info,  Node: Comparisons<3>,  Next: Allowed members and attributes of enumerations,  Prev: Iteration,  Up: enum --- Support for enumerations

5.8.13.8 Comparisons
....................

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: 19fb. 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: 592. was explicitly designed to behave
differently, see below):

     >>> Color.BLUE == 2
     False


File: python.info,  Node: Allowed members and attributes of enumerations,  Next: Restricted Enum subclassing,  Prev: Comparisons<3>,  Up: enum --- Support for enumerations

5.8.13.9 Allowed members and attributes of enumerations
.......................................................

The examples above use integers for enumeration values.  Using integers
is short and handy (and provided by default by the *note Functional API:
19f2.), 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 (*note
__str__(): e3c, *note __add__(): 145c, etc.), descriptors (methods are
also descriptors), and variable names listed in ‘_ignore_’.

Note: if your enumeration defines *note __new__(): 88e. and/or *note
__init__(): d63. then whatever value(s) were given to the enum member
will be passed into those methods.  See *note Planet: 19fd. for an
example.


File: python.info,  Node: Restricted Enum subclassing,  Next: Pickling,  Prev: Allowed members and attributes of enumerations,  Up: enum --- Support for enumerations

5.8.13.10 Restricted Enum subclassing
.....................................

A new *note Enum: 38c. class must have one base Enum class, up to one
concrete data type, and as many *note object: 2b1.-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: Cannot extend enumerations

But this is allowed:

     >>> 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: 19ff. for an example.)


File: python.info,  Node: Pickling,  Next: Functional API,  Prev: Restricted Enum subclassing,  Up: enum --- Support for enumerations

5.8.13.11 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 *note __reduce_ex__(): 1a01. in the enumeration class.


File: python.info,  Node: Functional API,  Next: Derived Enumerations,  Prev: Pickling,  Up: enum --- Support for enumerations

5.8.13.12 Functional API
........................

The *note Enum: 38c. class is callable, providing the following
functional API:

     >>> Animal = Enum('Animal', 'ANT BEE CAT DOG')
     >>> Animal
     <enum 'Animal'>
     >>> Animal.ANT
     <Animal.ANT: 1>
     >>> Animal.ANT.value
     1
     >>> list(Animal)
     [<Animal.ANT: 1>, <Animal.BEE: 2>, <Animal.CAT: 3>, <Animal.DOG: 4>]

The semantics of this API resemble *note namedtuple: 1b8.  The first
argument of the call to *note Enum: 38c. 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: 38c. 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 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 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__: 142f. 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,  Up: enum --- Support for enumerations

5.8.13.13 Derived Enumerations
..............................

* Menu:

* IntEnum::
* IntFlag::
* Flag::
* Others::


File: python.info,  Node: IntEnum,  Next: IntFlag,  Up: Derived Enumerations

5.8.13.14 IntEnum
.................

The first variation of *note Enum: 38c. that is provided is also a
subclass of *note int: 185.  Members of an *note IntEnum: 592. 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: 38c.
enumerations:

     >>> class Shape(IntEnum):
     ...     CIRCLE = 1
     ...     SQUARE = 2
     ...
     >>> class Color(Enum):
     ...     RED = 1
     ...     GREEN = 2
     ...
     >>> Shape.CIRCLE == Color.RED
     False

*note IntEnum: 592. 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: IntFlag,  Next: Flag,  Prev: IntEnum,  Up: Derived Enumerations

5.8.13.15 IntFlag
.................

The next variation of *note Enum: 38c. provided, *note IntFlag: 1760, is
also based on *note int: 185.  The difference being *note IntFlag: 1760.
members can be combined using the bitwise operators (&, |, ^, ~) and the
result is still an *note IntFlag: 1760. member.  However, as the name
implies, *note IntFlag: 1760. members also subclass *note int: 185. and
can be used wherever an *note int: 185. is used.  Any operation on an
*note IntFlag: 1760. member besides the bit-wise operations will lose
the *note IntFlag: 1760. membership.

3.6 版新加入.

Sample *note IntFlag: 1760. 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.-8: -8>

Another important difference between *note IntFlag: 1760. and *note
Enum: 38c. is that if no flags are set (the value is 0), its boolean
evaluation is *note False: 38d.:

     >>> Perm.R & Perm.X
     <Perm.0: 0>
     >>> bool(Perm.R & Perm.X)
     False

Because *note IntFlag: 1760. members are also subclasses of *note int:
185. they can be combined with them:

     >>> Perm.X | 8
     <Perm.8|X: 9>


File: python.info,  Node: Flag,  Next: Others,  Prev: IntFlag,  Up: Derived Enumerations

5.8.13.16 Flag
..............

The last variation is *note Flag: 54a.  Like *note IntFlag: 1760, *note
Flag: 54a. members can be combined using the bitwise operators (&, |, ^,
~).  Unlike *note IntFlag: 1760, they cannot be combined with, nor
compared against, any other *note Flag: 54a. enumeration, nor *note int:
185.  While it is possible to specify the values directly it is
recommended to use *note auto: 54b. as the value and let *note Flag:
54a. select an appropriate value.

3.6 版新加入.

Like *note IntFlag: 1760, if a combination of *note Flag: 54a. members
results in no flags being set, the boolean evaluation is *note False:
38d.:

     >>> from enum import Flag, auto
     >>> class Color(Flag):
     ...     RED = auto()
     ...     BLUE = auto()
     ...     GREEN = auto()
     ...
     >>> Color.RED & Color.GREEN
     <Color.0: 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 won’t:

     >>> 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

     備註: For the majority of new code, *note Enum: 38c. and *note
     Flag: 54a. are strongly recommended, since *note IntEnum: 592. and
     *note IntFlag: 1760. break some semantic promises of an enumeration
     (by being comparable to integers, and thus by transitivity to other
     unrelated enumerations).  *note IntEnum: 592. and *note IntFlag:
     1760. should be used only in cases where *note Enum: 38c. and *note
     Flag: 54a. will not do; for example, when integer constants are
     replaced with enumerations, or for interoperability with other
     systems.


File: python.info,  Node: Others,  Prev: Flag,  Up: Derived Enumerations

5.8.13.17 Others
................

While *note IntEnum: 592. is part of the *note enum: 7b. module, it
would be very simple to implement independently:

     class IntEnum(int, Enum):
         pass

This demonstrates how similar derived enumerations can be defined; for
example a ‘StrEnum’ that mixes in *note str: 335. instead of *note int:
185.

Some rules:

  1. When subclassing *note Enum: 38c, mix-in types must appear before
     *note Enum: 38c. itself in the sequence of bases, as in the *note
     IntEnum: 592. example above.

  2. While *note Enum: 38c. 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: 185. above.  This restriction does not apply
     to mix-ins which only add methods and don’t specify another data
     type such as *note int: 185. or *note str: 335.

  3. 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.

  4. %-style formatting: ‘%s’ and ‘%r’ call the *note Enum: 38c. class’s
     *note __str__(): e3c. and *note __repr__(): 343. respectively;
     other codes (such as ‘%i’ or ‘%h’ for IntEnum) treat the enum
     member as its mixed-in type.

  5. *note Formatted string literals: 15d, *note str.format(): 4df, and
     *note format(): 4e0. will use the mixed-in type’s *note
     __format__(): 953. unless *note __str__(): e3c. or *note
     __format__(): 953. is overridden in the subclass, in which case the
     overridden methods or *note Enum: 38c. methods will be used.  Use
     the !s and !r format codes to force usage of the *note Enum: 38c.
     class’s *note __str__(): e3c. and *note __repr__(): 343. methods.


File: python.info,  Node: When to use __new__ vs __init__,  Next: Interesting examples,  Prev: Derived Enumerations,  Up: enum --- Support for enumerations

5.8.13.18 When to use ‘__new__()’ vs. ‘__init__()’
..................................................

*note __new__(): 88e. must be used whenever you want to customize the
actual value of the *note Enum: 38c. member.  Any other modifications
may go in either *note __new__(): 88e. or *note __init__(): d63, with
*note __init__(): d63. 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


File: python.info,  Node: Interesting examples,  Next: How are Enums different?,  Prev: When to use __new__ vs __init__,  Up: enum --- Support for enumerations

5.8.13.19 Interesting examples
..............................

While *note Enum: 38c, *note IntEnum: 592, *note IntFlag: 1760, and
*note Flag: 54a. 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::
* Planet::
* TimePeriod::


File: python.info,  Node: Omitting values,  Next: OrderedEnum,  Up: Interesting examples

5.8.13.20 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: 54b. for the value

   - use instances of *note object: 2b1. as the value

   - use a descriptive string as the value

   - use a tuple as the value and a custom *note __new__(): 88e. to
     replace the tuple with an *note int: 185. 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.

Whichever method you choose, you should provide a *note repr(): 7d1.
that also hides the (unimportant) value:

     >>> class NoValue(Enum):
     ...     def __repr__(self):
     ...         return '<%s.%s>' % (self.__class__.__name__, self.name)
     ...

* Menu:

* Using auto::
* Using object::
* Using a descriptive string::
* Using a custom __new__(): Using a custom __new__.


File: python.info,  Node: Using auto,  Next: Using object,  Up: Omitting values

5.8.13.21 Using ‘auto’
......................

Using *note auto: 54b. would look like:

     >>> class Color(NoValue):
     ...     RED = auto()
     ...     BLUE = auto()
     ...     GREEN = auto()
     ...
     >>> Color.GREEN
     <Color.GREEN>


File: python.info,  Node: Using object,  Next: Using a descriptive string,  Prev: Using auto,  Up: Omitting values

5.8.13.22 Using ‘object’
........................

Using *note object: 2b1. would look like:

     >>> class Color(NoValue):
     ...     RED = object()
     ...     GREEN = object()
     ...     BLUE = object()
     ...
     >>> Color.GREEN
     <Color.GREEN>


File: python.info,  Node: Using a descriptive string,  Next: Using a custom __new__,  Prev: Using object,  Up: Omitting values

5.8.13.23 Using a descriptive string
....................................

Using a string as the value would look like:

     >>> class Color(NoValue):
     ...     RED = 'stop'
     ...     GREEN = 'go'
     ...     BLUE = 'too fast!'
     ...
     >>> Color.GREEN
     <Color.GREEN>
     >>> Color.GREEN.value
     'go'


File: python.info,  Node: Using a custom __new__,  Prev: Using a descriptive string,  Up: Omitting values

5.8.13.24 Using a custom ‘__new__()’
....................................

Using an auto-numbering *note __new__(): 88e. would look like:

     >>> class AutoNumber(NoValue):
     ...     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>
     >>> Color.GREEN.value
     2

To make a more general purpose ‘AutoNumber’, add ‘*args’ to the
signature:

     >>> class AutoNumber(NoValue):
     ...     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 *note __new__(): 88e. method, if defined, is used during
     creation of the Enum members; it is then replaced by Enum’s *note
     __new__(): 88e. which is used after class creation for lookup of
     existing members.


File: python.info,  Node: OrderedEnum,  Next: DuplicateFreeEnum,  Prev: Omitting values,  Up: Interesting examples

5.8.13.25 OrderedEnum
.....................

An ordered enumeration that is not based on *note IntEnum: 592. and so
maintains the normal *note Enum: 38c. 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: Planet,  Prev: OrderedEnum,  Up: Interesting examples

5.8.13.26 DuplicateFreeEnum
...........................

Raises an error if a duplicate member name 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(): 19f1.
     decorator can be used instead.


File: python.info,  Node: Planet,  Next: TimePeriod,  Prev: DuplicateFreeEnum,  Up: Interesting examples

5.8.13.27 Planet
................

If *note __new__(): 88e. or *note __init__(): d63. 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: Interesting examples

5.8.13.28 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: How are Enums different?,  Prev: Interesting examples,  Up: enum --- Support for enumerations

5.8.13.29 How are Enums different?
..................................

Enums have a custom metaclass that affects many aspects of both derived
Enum classes and their instances (members).

* Menu:

* Enum Classes::
* Enum Members (aka instances): Enum Members aka instances.
* Finer Points::


File: python.info,  Node: Enum Classes,  Next: Enum Members aka instances,  Up: How are Enums different?

5.8.13.30 Enum Classes
......................

The ‘EnumMeta’ metaclass is responsible for providing the *note
__contains__(): d2d, *note __dir__(): 320, *note __iter__(): 514. and
other methods that allow one to do things with an *note Enum: 38c. class
that fail on a typical class, such as ‘list(Color)’ or ‘some_enum_var in
Color’.  ‘EnumMeta’ is responsible for ensuring that various other
methods on the final *note Enum: 38c. class are correct (such as *note
__new__(): 88e, *note __getnewargs__(): 6b3, *note __str__(): e3c. and
*note __repr__(): 343.).


File: python.info,  Node: Enum Members aka instances,  Next: Finer Points,  Prev: Enum Classes,  Up: How are Enums different?

5.8.13.31 Enum Members (aka instances)
......................................

The most interesting thing about Enum members is that they are
singletons.  ‘EnumMeta’ creates them all while it is creating the *note
Enum: 38c. class itself, and then puts a custom *note __new__(): 88e. in
place to ensure that no new ones are ever instantiated by returning only
the existing member instances.


File: python.info,  Node: Finer Points,  Prev: Enum Members aka instances,  Up: How are Enums different?

5.8.13.32 Finer Points
......................

* Menu:

* Supported __dunder__ names::
* Supported _sunder_ names::
* Enum member type::
* Boolean value of Enum classes and members::
* Enum classes with methods::
* Combining members of Flag::


File: python.info,  Node: Supported __dunder__ names,  Next: Supported _sunder_ names,  Up: Finer Points

5.8.13.33 Supported ‘__dunder__’ names
......................................

‘__members__’ is a read-only ordered mapping of ‘member_name’:‘member’
items.  It is only available on the class.

*note __new__(): 88e, 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: Enum member type,  Prev: Supported __dunder__ names,  Up: Finer Points

5.8.13.34 Supported ‘_sunder_’ names
....................................

   - ‘_name_’ – name of the member

   - ‘_value_’ – value of the member; can be set / modified in ‘__new__’

   - ‘_missing_’ – a lookup function used when a value is not found; may
     be overridden

   - ‘_ignore_’ – a list of names, either as a *note list(): 263. or a
     *note str(): 335, that will not be transformed into members, and
     will be removed from the final class

   - ‘_order_’ – used in Python 2/3 code to ensure member order is
     consistent (class attribute, removed during class creation)

   - ‘_generate_next_value_’ – used by the *note Functional API: 19f2.
     and by *note auto: 54b. to get an appropriate value for an enum
     member; may be overridden

3.6 版新加入: ‘_missing_’, ‘_order_’, ‘_generate_next_value_’

3.7 版新加入: ‘_ignore_’

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_

     備註: In Python 2 code the ‘_order_’ attribute is necessary as
     definition order is lost before it can be recorded.


File: python.info,  Node: Enum member type,  Next: Boolean value of Enum classes and members,  Prev: Supported _sunder_ names,  Up: Finer Points

5.8.13.35 ‘Enum’ member type
............................

*note Enum: 38c. members are instances of their *note Enum: 38c. class,
and are normally accessed as ‘EnumClass.member’.  Under certain
circumstances they can also be accessed as ‘EnumClass.member.member’,
but you should never do this as that lookup may fail or, worse, return
something besides the *note Enum: 38c. member you are looking for (this
is another good reason to use all-uppercase names for members):

     >>> class FieldTypes(Enum):
     ...     name = 0
     ...     value = 1
     ...     size = 2
     ...
     >>> FieldTypes.value.size
     <FieldTypes.size: 2>
     >>> FieldTypes.size.value
     2

3.5 版更變.


File: python.info,  Node: Boolean value of Enum classes and members,  Next: Enum classes with methods,  Prev: Enum member type,  Up: Finer Points

5.8.13.36 Boolean value of ‘Enum’ classes and members
.....................................................

*note Enum: 38c. members that are mixed with non-*note Enum: 38c. types
(such as *note int: 185, *note str: 335, etc.)  are evaluated according
to the mixed-in type’s rules; otherwise, all members evaluate as *note
True: 49e.  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)

*note Enum: 38c. classes always evaluate as *note True: 49e.


File: python.info,  Node: Enum classes with methods,  Next: Combining members of Flag,  Prev: Boolean value of Enum classes and members,  Up: Finer Points

5.8.13.37 ‘Enum’ classes with methods
.....................................

If you give your *note Enum: 38c. subclass extra methods, like the *note
Planet: 19fd. class above, those methods will show up in a *note dir():
d38. 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__', 'name', 'surface_gravity', 'value']


File: python.info,  Node: Combining members of Flag,  Prev: Enum classes with methods,  Up: Finer Points

5.8.13.38 Combining members of ‘Flag’
.....................................

If a combination of Flag members is not named, the *note repr(): 7d1.
will include all named flags and all named combinations of flags that
are in the value:

     >>> 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.CYAN|MAGENTA|BLUE|YELLOW|GREEN|RED: 7>


File: python.info,  Node: 數值與數學模組,  Next: 函式編程模組,  Prev: Data Types,  Up: Python 標準函式庫 Standard Library

5.9 數值與數學模組
==================

The modules described in this chapter provide numeric and math-related
functions and data types.  The *note numbers: c2. module defines an
abstract hierarchy of numeric types.  The *note math: b2. and *note
cmath: 19. modules contain various mathematical functions for
floating-point and complex numbers.  The *note decimal: 36. module
supports exact representations of decimal numbers, using arbitrary
precision arithmetic.

The following modules are documented in this chapter:

* Menu:

* numbers: numbers --- Numeric abstract base classes. Numeric abstract base classes
* math: math --- Mathematical functions. Mathematical functions
* cmath: cmath --- Mathematical functions for complex numbers. Mathematical functions for complex numbers
* decimal: decimal --- Decimal fixed point and floating point arithmetic. Decimal fixed point and floating point arithmetic
* fractions: fractions --- Rational numbers. Rational numbers
* random: random --- Generate pseudo-random numbers. Generate pseudo-random numbers
* statistics: statistics --- 數學統計函式. 數學統計函式


File: python.info,  Node: numbers --- Numeric abstract base classes,  Next: math --- Mathematical functions,  Up: 數值與數學模組

5.9.1 ‘numbers’ — Numeric abstract base classes
-----------------------------------------------

`Source code:' Lib/numbers.py(1)

__________________________________________________________________

The *note numbers: c2. module ( PEP 3141(2)) defines a hierarchy of
numeric *note abstract base classes: b38. which progressively define
more operations.  None of the types defined in this module can be
instantiated.

 -- 類別: numbers.Number

     The root of the numeric hierarchy.  If you just want to check if an
     argument `x' is a number, without caring what kind, use
     ‘isinstance(x, Number)’.

* Menu:

* The numeric tower::
* Notes for type implementors::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/numbers.py

   (2) https://www.python.org/dev/peps/pep-3141


File: python.info,  Node: The numeric tower,  Next: Notes for type implementors,  Up: numbers --- Numeric abstract base classes

5.9.1.1 The numeric tower
.........................

 -- 類別: numbers.Complex

     Subclasses of this type describe complex numbers and include the
     operations that work on the built-in *note complex: 18a. type.
     These are: conversions to *note complex: 18a. and *note bool: 184,
     *note real: 1a1e, *note imag: 1a1f, ‘+’, ‘-’, ‘*’, ‘/’, *note
     abs(): 12c4, *note conjugate(): 1a20, ‘==’, and ‘!=’.  All except
     ‘-’ and ‘!=’ are abstract.

      -- 屬性: real

          Abstract.  Retrieves the real component of this number.

      -- 屬性: imag

          Abstract.  Retrieves the imaginary component of this number.

      -- 成員函式: abstractmethod conjugate ()

          Abstract.  Returns the complex conjugate.  For example,
          ‘(1+3j).conjugate() == (1-3j)’.

 -- 類別: numbers.Real

     To *note Complex: 142b, *note Real: 142a. adds the operations that
     work on real numbers.

     In short, those are: a conversion to *note float: 188, *note
     math.trunc(): d33, *note round(): c72, *note math.floor(): d31,
     *note math.ceil(): d32, *note divmod(): 153, ‘//’, ‘%’, ‘<’, ‘<=’,
     ‘>’, and ‘>=’.

     Real also provides defaults for *note complex(): 18a, *note real:
     1a1e, *note imag: 1a1f, and *note conjugate(): 1a20.

 -- 類別: numbers.Rational

     Subtypes *note Real: 142a. and adds *note numerator: 1a21. and
     *note denominator: 1a22. properties, which should be in lowest
     terms.  With these, it provides a default for *note float(): 188.

      -- 屬性: numerator

          Abstract.

      -- 屬性: denominator

          Abstract.

 -- 類別: numbers.Integral

     Subtypes *note Rational: c5d. and adds a conversion to *note int:
     185.  Provides defaults for *note float(): 188, *note numerator:
     1a21, and *note denominator: 1a22.  Adds abstract methods for ‘**’
     and bit-string operations: ‘<<’, ‘>>’, ‘&’, ‘^’, ‘|’, ‘~’.


File: python.info,  Node: Notes for type implementors,  Prev: The numeric tower,  Up: numbers --- Numeric abstract base classes

5.9.1.2 Notes for type implementors
...................................

Implementors should be careful to make equal numbers equal and hash them
to the same values.  This may be subtle if there are two different
extensions of the real numbers.  For example, *note fractions.Fraction:
186. implements *note hash(): 9c9. as follows:

     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:

* Adding More Numeric ABCs::
* Implementing the arithmetic operations::


File: python.info,  Node: Adding More Numeric ABCs,  Next: Implementing the arithmetic operations,  Up: Notes for type implementors

5.9.1.3 Adding More Numeric ABCs
................................

There are, of course, more possible ABCs for numbers, and this would be
a poor hierarchy if it precluded the possibility of adding those.  You
can add ‘MyFoo’ between *note Complex: 142b. and *note Real: 142a. with:

     class MyFoo(Complex): ...
     MyFoo.register(Real)


File: python.info,  Node: Implementing the arithmetic operations,  Prev: Adding More Numeric ABCs,  Up: Notes for type implementors

5.9.1.4 Implementing the arithmetic operations
..............................................

We want to implement the arithmetic operations so that mixed-mode
operations either call an implementation whose author knew about the
types of both arguments, or convert both to the nearest built in type
and do the operation there.  For subtypes of *note Integral: 1429, this
means that *note __add__(): 145c. and *note __radd__(): 145d. should be
defined as:

     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

There are 5 different cases for a mixed-type operation on subclasses of
*note Complex: 142b.  I’ll refer to all of the above code that doesn’t
refer to ‘MyIntegral’ and ‘OtherTypeIKnowAbout’ as "boilerplate".  ‘a’
will be an instance of ‘A’, which is a subtype of *note Complex: 142b.
(‘a : A <: Complex’), and ‘b : B <: Complex’.  I’ll consider ‘a + b’:

       1. If ‘A’ defines an *note __add__(): 145c. which accepts ‘b’,
          all is well.

       2. If ‘A’ falls back to the boilerplate code, and it were to
          return a value from *note __add__(): 145c, we’d miss the
          possibility that ‘B’ defines a more intelligent *note
          __radd__(): 145d, so the boilerplate should return *note
          NotImplemented: 851. from *note __add__(): 145c.  (Or ‘A’ may
          not implement *note __add__(): 145c. at all.)

       3. Then ‘B’’s *note __radd__(): 145d. gets a chance.  If it
          accepts ‘a’, all is well.

       4. If it falls back to the boilerplate, there are no more
          possible methods to try, so this is where the default
          implementation should live.

       5. If ‘B <: A’, Python tries ‘B.__radd__’ before ‘A.__add__’.
          This is ok, because it was implemented with knowledge of ‘A’,
          so it can handle those instances before delegating to *note
          Complex: 142b.

If ‘A <: Complex’ and ‘B <: Real’ without sharing any other knowledge,
then the appropriate shared operation is the one involving the built in
*note complex: 18a, and both *note __radd__(): 145d. s land there, so
‘a+b == b+a’.

Because most of the operations on any given type will be very similar,
it can be useful to define a helper function which generates the forward
and reverse instances of any given operator.  For example, *note
fractions.Fraction: 186. uses:

     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):
                 # Includes ints.
                 return monomorphic_operator(a, b)
             elif isinstance(a, numbers.Real):
                 return fallback_operator(float(a), float(b))
             elif isinstance(a, numbers.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 --- Mathematical functions,  Next: cmath --- Mathematical functions for complex numbers,  Prev: numbers --- Numeric abstract base classes,  Up: 數值與數學模組

5.9.2 ‘math’ — Mathematical functions
-------------------------------------

__________________________________________________________________

This module provides access to the mathematical functions defined by the
C standard.

These functions cannot be used with complex numbers; use the functions
of the same name from the *note cmath: 19. module if you require support
for complex numbers.  The distinction between functions which support
complex numbers and those which don’t is made since most users do not
want to learn quite as much mathematics as required to understand
complex numbers.  Receiving an exception instead of a complex result
allows earlier detection of the unexpected complex number used as a
parameter, so that the programmer can determine how and why it was
generated in the first place.

The following functions are provided by this module.  Except when
explicitly noted otherwise, all return values are floats.

* Menu:

* Number-theoretic and representation functions::
* Power and logarithmic functions::
* Trigonometric functions::
* Angular conversion::
* Hyperbolic functions::
* Special functions::
* Constants: Constants<2>.


File: python.info,  Node: Number-theoretic and representation functions,  Next: Power and logarithmic functions,  Up: math --- Mathematical functions

5.9.2.1 Number-theoretic and representation functions
.....................................................

 -- 函式: math.ceil (x)

     Return the ceiling of `x', the smallest integer greater than or
     equal to `x'.  If `x' is not a float, delegates to ‘x.__ceil__()’,
     which should return an *note Integral: 1429. value.

 -- 函式: math.comb (n, k)

     Return the number of ways to choose `k' items from `n' items
     without repetition and without order.

     Evaluates to ‘n! / (k! * (n - k)!)’ when ‘k <= n’ and evaluates to
     zero when ‘k > n’.

     Also called the binomial coefficient because it is equivalent to
     the coefficient of k-th term in polynomial expansion of the
     expression ‘(1 + x) ** n’.

     Raises *note TypeError: 193. if either of the arguments are not
     integers.  Raises *note ValueError: 1fc. if either of the arguments
     are negative.

     3.8 版新加入.

 -- 函式: math.copysign (x, y)

     Return a float with the magnitude (absolute value) of `x' but the
     sign of `y'.  On platforms that support signed zeros,
     ‘copysign(1.0, -0.0)’ returns `-1.0'.

 -- 函式: math.fabs (x)

     Return the absolute value of `x'.

 -- 函式: math.factorial (x)

     Return `x' factorial as an integer.  Raises *note ValueError: 1fc.
     if `x' is not integral or is negative.

 -- 函式: math.floor (x)

     Return the floor of `x', the largest integer less than or equal to
     `x'.  If `x' is not a float, delegates to ‘x.__floor__()’, which
     should return an *note Integral: 1429. value.

 -- 函式: math.fmod (x, y)

     Return ‘fmod(x, y)’, as defined by the platform C library.  Note
     that the Python expression ‘x % y’ may not return the same result.
     The intent of the C standard is that ‘fmod(x, y)’ be exactly
     (mathematically; to infinite precision) equal to ‘x - n*y’ for some
     integer `n' such that the result has the same sign as `x' and
     magnitude less than ‘abs(y)’.  Python’s ‘x % y’ returns a result
     with the sign of `y' instead, and may not be exactly computable for
     float arguments.  For example, ‘fmod(-1e-100, 1e100)’ is ‘-1e-100’,
     but the result of Python’s ‘-1e-100 % 1e100’ is ‘1e100-1e-100’,
     which cannot be represented exactly as a float, and rounds to the
     surprising ‘1e100’.  For this reason, function *note fmod(): 153d.
     is generally preferred when working with floats, while Python’s ‘x
     % y’ is preferred when working with integers.

 -- 函式: math.frexp (x)

     Return the mantissa and exponent of `x' as the pair ‘(m, e)’.  `m'
     is a float and `e' is an integer such that ‘x == m * 2**e’ exactly.
     If `x' is zero, returns ‘(0.0, 0)’, otherwise ‘0.5 <= abs(m) < 1’.
     This is used to "pick apart" the internal representation of a float
     in a portable way.

 -- 函式: math.fsum (iterable)

     Return an accurate floating point sum of values in the iterable.
     Avoids loss of precision by tracking multiple intermediate partial
     sums:

          >>> sum([.1, .1, .1, .1, .1, .1, .1, .1, .1, .1])
          0.9999999999999999
          >>> fsum([.1, .1, .1, .1, .1, .1, .1, .1, .1, .1])
          1.0

     The algorithm’s accuracy depends on IEEE-754 arithmetic guarantees
     and the typical case where the rounding mode is half-even.  On some
     non-Windows builds, the underlying C library uses extended
     precision addition and may occasionally double-round an
     intermediate sum causing it to be off in its least significant bit.

     For further discussion and two alternative approaches, see the ASPN
     cookbook recipes for accurate floating point summation(1).

 -- 函式: math.gcd (a, b)

     Return the greatest common divisor of the integers `a' and `b'.  If
     either `a' or `b' is nonzero, then the value of ‘gcd(a, b)’ is the
     largest positive integer that divides both `a' and `b'.  ‘gcd(0,
     0)’ returns ‘0’.

     3.5 版新加入.

 -- 函式: math.isclose (a, b, *, rel_tol=1e-09, abs_tol=0.0)

     Return ‘True’ if the values `a' and `b' are close to each other and
     ‘False’ otherwise.

     Whether or not two values are considered close is determined
     according to given absolute and relative tolerances.

     `rel_tol' is the relative tolerance – it is the maximum allowed
     difference between `a' and `b', relative to the larger absolute
     value of `a' or `b'.  For example, to set a tolerance of 5%, pass
     ‘rel_tol=0.05’.  The default tolerance is ‘1e-09’, which assures
     that the two values are the same within about 9 decimal digits.
     `rel_tol' must be greater than zero.

     `abs_tol' is the minimum absolute tolerance – useful for
     comparisons near zero.  `abs_tol' must be at least zero.

     If no errors occur, the result will be: ‘abs(a-b) <= max(rel_tol *
     max(abs(a), abs(b)), abs_tol)’.

     The IEEE 754 special values of ‘NaN’, ‘inf’, and ‘-inf’ will be
     handled according to IEEE rules.  Specifically, ‘NaN’ is not
     considered close to any other value, including ‘NaN’.  ‘inf’ and
     ‘-inf’ are only considered close to themselves.

     3.5 版新加入.

     也參考
     ......

     PEP 485(2) – A function for testing approximate equality

 -- 函式: math.isfinite (x)

     Return ‘True’ if `x' is neither an infinity nor a NaN, and ‘False’
     otherwise.  (Note that ‘0.0’ `is' considered finite.)

     3.2 版新加入.

 -- 函式: math.isinf (x)

     Return ‘True’ if `x' is a positive or negative infinity, and
     ‘False’ otherwise.

 -- 函式: math.isnan (x)

     Return ‘True’ if `x' is a NaN (not a number), and ‘False’
     otherwise.

 -- 函式: math.isqrt (n)

     Return the integer square root of the nonnegative integer `n'.
     This is the floor of the exact square root of `n', or equivalently
     the greatest integer `a' such that `a'² ≤ `n'.

     For some applications, it may be more convenient to have the least
     integer `a' such that `n' ≤ `a'², or in other words the ceiling of
     the exact square root of `n'.  For positive `n', this can be
     computed using ‘a = 1 + isqrt(n - 1)’.

     3.8 版新加入.

 -- 函式: math.ldexp (x, i)

     Return ‘x * (2**i)’.  This is essentially the inverse of function
     *note frexp(): 1a2a.

 -- 函式: math.modf (x)

     Return the fractional and integer parts of `x'.  Both results carry
     the sign of `x' and are floats.

 -- 函式: 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!’.

     Raises *note TypeError: 193. if either of the arguments are not
     integers.  Raises *note ValueError: 1fc. if either of the arguments
     are negative.

     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: 1fc. 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.trunc (x)

     Return the *note Real: 142a. value `x' truncated to an *note
     Integral: 1429. (usually an integer).  Delegates to *note
     x.__trunc__(): 1488.

Note that *note frexp(): 1a2a. and *note modf(): 1a2c. 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(): d32, *note floor(): d31, and *note modf(): 1a2c.
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://www.python.org/dev/peps/pep-0485


File: python.info,  Node: Power and logarithmic functions,  Next: Trigonometric functions,  Prev: Number-theoretic and representation functions,  Up: math --- Mathematical functions

5.9.2.2 Power and logarithmic functions
.......................................

 -- 函式: 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.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(): b6d. 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(): 1624. 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 Annex
     ’F’ of the C99 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: 1fc.

     Unlike the built-in ‘**’ operator, *note math.pow(): 1a2f. converts
     both its arguments to type *note float: 188.  Use ‘**’ or the
     built-in *note pow(): 19b. function for computing exact integer
     powers.

 -- 函式: 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 --- Mathematical functions

5.9.2.3 Trigonometric functions
...............................

 -- 函式: math.acos (x)

     Return the arc cosine of `x', in radians.

 -- 函式: math.asin (x)

     Return the arc sine of `x', in radians.

 -- 函式: math.atan (x)

     Return the arc tangent of `x', in radians.

 -- 函式: 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(): 1a34. 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.

 -- 函式: 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 --- Mathematical functions

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 --- Mathematical functions

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_function


File: python.info,  Node: Special functions,  Next: Constants<2>,  Prev: Hyperbolic functions,  Up: math --- Mathematical functions

5.9.2.6 Special functions
.........................

 -- 函式: math.erf (x)

     Return the error function(1) at `x'.

     The *note erf(): 457. 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/Normal_distribution#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: Constants<2>,  Prev: Special functions,  Up: math --- Mathematical functions

5.9.2.7 Constants
.................

 -- Data: math.pi

     The mathematical constant `π' = 3.141592..., to available
     precision.

 -- Data: math.e

     The mathematical constant `e' = 2.718281..., to available
     precision.

 -- Data: 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 版新加入.

 -- Data: math.inf

     A floating-point positive infinity.  (For negative infinity, use
     ‘-math.inf’.)  Equivalent to the output of ‘float('inf')’.

     3.5 版新加入.

 -- Data: math.nan

     A floating-point "not a number" (NaN) value.  Equivalent to the
     output of ‘float('nan')’.

     3.5 版新加入.

`CPython implementation detail:' The *note math: b2. 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:
1fc. 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: 965. 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.

也參考
......

Module *note cmath: 19.

     Complex number versions of many of these functions.

   ---------- Footnotes ----------

   (1) https://www.youtube.com/watch?v=jG7vhMMXagQ

   (2) https://tauday.com/


File: python.info,  Node: cmath --- Mathematical functions for complex numbers,  Next: decimal --- Decimal fixed point and floating point arithmetic,  Prev: math --- Mathematical functions,  Up: 數值與數學模組

5.9.3 ‘cmath’ — Mathematical functions for complex numbers
----------------------------------------------------------

__________________________________________________________________

This module provides access to mathematical functions for complex
numbers.  The functions in this module accept integers, floating-point
numbers or complex numbers as arguments.  They will also accept any
Python object that has either a *note __complex__(): 18e. or a *note
__float__(): 18d. method: these methods are used to convert the object
to a complex or floating-point number, respectively, and the function is
then applied to the result of the conversion.

     備註: On platforms with hardware and system-level support for
     signed zeros, functions involving branch cuts are continuous on
     `both' sides of the branch cut: the sign of the zero distinguishes
     one side of the branch cut from the other.  On platforms that do
     not support signed zeros the continuity is as specified below.

* Menu:

* Conversions to and from polar coordinates::
* Power and logarithmic functions: Power and logarithmic functions<2>.
* Trigonometric functions: Trigonometric functions<2>.
* Hyperbolic functions: Hyperbolic functions<2>.
* Classification functions::
* Constants: Constants<3>.


File: python.info,  Node: Conversions to and from polar coordinates,  Next: Power and logarithmic functions<2>,  Up: cmath --- Mathematical functions for complex numbers

5.9.3.1 Conversions to and from polar coordinates
.................................................

A Python complex number ‘z’ is stored internally using `rectangular' or
`Cartesian' coordinates.  It is completely determined by its `real part'
‘z.real’ and its `imaginary part' ‘z.imag’.  In other words:

     z == z.real + z.imag*1j

`Polar coordinates' give an alternative way to represent a complex
number.  In polar coordinates, a complex number `z' is defined by the
modulus `r' and the phase angle `phi'.  The modulus `r' is the distance
from `z' to the origin, while the phase `phi' is the counterclockwise
angle, measured in radians, from the positive x-axis to the line segment
that joins the origin to `z'.

The following functions can be used to convert from the native
rectangular coordinates to polar coordinates and back.

 -- 函式: cmath.phase (x)

     Return the phase of `x' (also known as the `argument' of `x'), as a
     float.  ‘phase(x)’ is equivalent to ‘math.atan2(x.imag, x.real)’.
     The result lies in the range [-`π', `π'], and the branch cut for
     this operation lies along the negative real axis, continuous from
     above.  On systems with support for signed zeros (which includes
     most systems in current use), this means that the sign of the
     result is the same as the sign of ‘x.imag’, even when ‘x.imag’ is
     zero:

          >>> phase(complex(-1.0, 0.0))
          3.141592653589793
          >>> phase(complex(-1.0, -0.0))
          -3.141592653589793

     備註: The modulus (absolute value) of a complex number `x' can be
     computed using the built-in *note abs(): 12c4. function.  There is
     no separate *note cmath: 19. module function for this operation.

 -- 函式: cmath.polar (x)

     Return the representation of `x' in polar coordinates.  Returns a
     pair ‘(r, phi)’ where `r' is the modulus of `x' and phi is the
     phase of `x'.  ‘polar(x)’ is equivalent to ‘(abs(x), phase(x))’.

 -- 函式: cmath.rect (r, phi)

     Return the complex number `x' with polar coordinates `r' and `phi'.
     Equivalent to ‘r * (math.cos(phi) + math.sin(phi)*1j)’.


File: python.info,  Node: Power and logarithmic functions<2>,  Next: Trigonometric functions<2>,  Prev: Conversions to and from polar coordinates,  Up: cmath --- Mathematical functions for complex numbers

5.9.3.2 Power and logarithmic functions
.......................................

 -- 函式: cmath.exp (x)

     Return `e' raised to the power `x', where `e' is the base of
     natural logarithms.

 -- 函式: cmath.log (x[, base])

     Returns the logarithm of `x' to the given `base'.  If the `base' is
     not specified, returns the natural logarithm of `x'.  There is one
     branch cut, from 0 along the negative real axis to -∞, continuous
     from above.

 -- 函式: cmath.log10 (x)

     Return the base-10 logarithm of `x'.  This has the same branch cut
     as *note log(): 1a4a.

 -- 函式: cmath.sqrt (x)

     Return the square root of `x'.  This has the same branch cut as
     *note log(): 1a4a.


File: python.info,  Node: Trigonometric functions<2>,  Next: Hyperbolic functions<2>,  Prev: Power and logarithmic functions<2>,  Up: cmath --- Mathematical functions for complex numbers

5.9.3.3 Trigonometric functions
...............................

 -- 函式: cmath.acos (x)

     Return the arc cosine of `x'.  There are two branch cuts: One
     extends right from 1 along the real axis to ∞, continuous from
     below.  The other extends left from -1 along the real axis to -∞,
     continuous from above.

 -- 函式: cmath.asin (x)

     Return the arc sine of `x'.  This has the same branch cuts as *note
     acos(): 1a4e.

 -- 函式: cmath.atan (x)

     Return the arc tangent of `x'.  There are two branch cuts: One
     extends from ‘1j’ along the imaginary axis to ‘∞j’, continuous from
     the right.  The other extends from ‘-1j’ along the imaginary axis
     to ‘-∞j’, continuous from the left.

 -- 函式: cmath.cos (x)

     Return the cosine of `x'.

 -- 函式: cmath.sin (x)

     Return the sine of `x'.

 -- 函式: cmath.tan (x)

     Return the tangent of `x'.


File: python.info,  Node: Hyperbolic functions<2>,  Next: Classification functions,  Prev: Trigonometric functions<2>,  Up: cmath --- Mathematical functions for complex numbers

5.9.3.4 Hyperbolic functions
............................

 -- 函式: cmath.acosh (x)

     Return the inverse hyperbolic cosine of `x'.  There is one branch
     cut, extending left from 1 along the real axis to -∞, continuous
     from above.

 -- 函式: cmath.asinh (x)

     Return the inverse hyperbolic sine of `x'.  There are two branch
     cuts: One extends from ‘1j’ along the imaginary axis to ‘∞j’,
     continuous from the right.  The other extends from ‘-1j’ along the
     imaginary axis to ‘-∞j’, continuous from the left.

 -- 函式: cmath.atanh (x)

     Return the inverse hyperbolic tangent of `x'.  There are two branch
     cuts: One extends from ‘1’ along the real axis to ‘∞’, continuous
     from below.  The other extends from ‘-1’ along the real axis to
     ‘-∞’, continuous from above.

 -- 函式: cmath.cosh (x)

     Return the hyperbolic cosine of `x'.

 -- 函式: cmath.sinh (x)

     Return the hyperbolic sine of `x'.

 -- 函式: cmath.tanh (x)

     Return the hyperbolic tangent of `x'.


File: python.info,  Node: Classification functions,  Next: Constants<3>,  Prev: Hyperbolic functions<2>,  Up: cmath --- Mathematical functions for complex numbers

5.9.3.5 Classification functions
................................

 -- 函式: cmath.isfinite (x)

     Return ‘True’ if both the real and imaginary parts of `x' are
     finite, and ‘False’ otherwise.

     3.2 版新加入.

 -- 函式: cmath.isinf (x)

     Return ‘True’ if either the real or the imaginary part of `x' is an
     infinity, and ‘False’ otherwise.

 -- 函式: cmath.isnan (x)

     Return ‘True’ if either the real or the imaginary part of `x' is a
     NaN, and ‘False’ otherwise.

 -- 函式: cmath.isclose (a, b, *, rel_tol=1e-09, abs_tol=0.0)

     Return ‘True’ if the values `a' and `b' are close to each other and
     ‘False’ otherwise.

     Whether or not two values are considered close is determined
     according to given absolute and relative tolerances.

     `rel_tol' is the relative tolerance – it is the maximum allowed
     difference between `a' and `b', relative to the larger absolute
     value of `a' or `b'.  For example, to set a tolerance of 5%, pass
     ‘rel_tol=0.05’.  The default tolerance is ‘1e-09’, which assures
     that the two values are the same within about 9 decimal digits.
     `rel_tol' must be greater than zero.

     `abs_tol' is the minimum absolute tolerance – useful for
     comparisons near zero.  `abs_tol' must be at least zero.

     If no errors occur, the result will be: ‘abs(a-b) <= max(rel_tol *
     max(abs(a), abs(b)), abs_tol)’.

     The IEEE 754 special values of ‘NaN’, ‘inf’, and ‘-inf’ will be
     handled according to IEEE rules.  Specifically, ‘NaN’ is not
     considered close to any other value, including ‘NaN’.  ‘inf’ and
     ‘-inf’ are only considered close to themselves.

     3.5 版新加入.

     也參考
     ......

     PEP 485(1) – A function for testing approximate equality

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0485


File: python.info,  Node: Constants<3>,  Prev: Classification functions,  Up: cmath --- Mathematical functions for complex numbers

5.9.3.6 Constants
.................

 -- Data: cmath.pi

     The mathematical constant `π', as a float.

 -- Data: cmath.e

     The mathematical constant `e', as a float.

 -- Data: cmath.tau

     The mathematical constant `τ', as a float.

     3.6 版新加入.

 -- Data: cmath.inf

     Floating-point positive infinity.  Equivalent to ‘float('inf')’.

     3.6 版新加入.

 -- Data: cmath.infj

     Complex number with zero real part and positive infinity imaginary
     part.  Equivalent to ‘complex(0.0, float('inf'))’.

     3.6 版新加入.

 -- Data: cmath.nan

     A floating-point "not a number" (NaN) value.  Equivalent to
     ‘float('nan')’.

     3.6 版新加入.

 -- Data: cmath.nanj

     Complex number with zero real part and NaN imaginary part.
     Equivalent to ‘complex(0.0, float('nan'))’.

     3.6 版新加入.

Note that the selection of functions is similar, but not identical, to
that in module *note math: b2.  The reason for having two modules is
that some users aren’t interested in complex numbers, and perhaps don’t
even know what they are.  They would rather have ‘math.sqrt(-1)’ raise
an exception than return a complex number.  Also note that the functions
defined in *note cmath: 19. always return a complex number, even if the
answer can be expressed as a real number (in which case the complex
number has an imaginary part of zero).

A note on branch cuts: They are curves along which the given function
fails to be continuous.  They are a necessary feature of many complex
functions.  It is assumed that if you need to compute with complex
functions, you will understand about branch cuts.  Consult almost any
(not too elementary) book on complex variables for enlightenment.  For
information of the proper choice of branch cuts for numerical purposes,
a good reference should be the following:

也參考
......

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 --- Decimal fixed point and floating point arithmetic,  Next: fractions --- Rational numbers,  Prev: cmath --- Mathematical functions for complex numbers,  Up: 數值與數學模組

5.9.4 ‘decimal’ — Decimal fixed point and floating point arithmetic
-------------------------------------------------------------------

`Source code:' Lib/decimal.py(1)

__________________________________________________________________

The *note decimal: 36. module provides support for fast
correctly-rounded decimal floating point arithmetic.  It offers several
advantages over the *note float: 188. 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:
1a64, *note ROUND_DOWN: 1a65, *note ROUND_FLOOR: 1a66, *note
ROUND_HALF_DOWN: 1a67, *note ROUND_HALF_EVEN: 1a68, *note ROUND_HALF_UP:
1a69, *note ROUND_UP: 1a6a, and *note ROUND_05UP: 1a6b.

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: 1a6c, *note
InvalidOperation: 9f0, *note DivisionByZero: 1a6d, *note Inexact: 1a6e,
*note Rounded: 1a6f, *note Subnormal: 1a70, *note Overflow: 1a71, *note
Underflow: 1a72. and *note FloatOperation: 9ea.

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::
* Constants: Constants<4>.
* Rounding modes::
* Signals::
* Floating Point Notes::
* Working with threads::
* Recipes::
* Decimal FAQ::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/decimal.py

   (2) http://speleotrove.com/decimal/decarith.html


File: python.info,  Node: Quick-start Tutorial,  Next: Decimal objects,  Up: decimal --- Decimal fixed point and floating point arithmetic

5.9.4.1 Quick-start Tutorial
............................

The usual start to using decimals is importing the module, viewing the
current context with *note getcontext(): 1a75. 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: 9ea. 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: 9f0.:

     >>> 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 ‘quantize()’ 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(): 1a75. 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(): 1a76. function.

In accordance with the standard, the *note decimal: 36. module provides
two ready to use standard contexts, *note BasicContext: 9ee. and *note
ExtendedContext: 9ef.  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 ‘clear_flags()’ 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’ field 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: 189. 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 --- Decimal fixed point and floating point arithmetic

5.9.4.2 Decimal objects
.......................

 -- 類別: decimal.Decimal (value="0", context=None)

     Construct a new *note Decimal: 189. object based from `value'.

     `value' can be an integer, string, tuple, *note float: 188, or
     another *note Decimal: 189. 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: 483, it should have three components,
     a sign (‘0’ for positive or ‘1’ for negative), a *note tuple: 483.
     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: 188, 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: 9f0, an exception is raised; otherwise, the
     constructor returns a new Decimal with the value of ‘NaN’.

     Once constructed, *note Decimal: 189. objects are immutable.

     3.2 版更變: The argument to the constructor is now permitted to be
     a *note float: 188. instance.

     3.3 版更變: *note float: 188. arguments raise an exception if the
     *note FloatOperation: 9ea. 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: 188. and *note int:
     185.  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: 188. or *note int:
     185.).

     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: 186. in arithmetic
     operations: an attempt to add a *note Decimal: 189. to a *note
     float: 188, for example, will raise a *note TypeError: 193.
     However, it is possible to use Python’s comparison operators to
     compare a *note Decimal: 189. 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: 189.
     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: 189. 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: aa8. representation of the number:
          ‘DecimalTuple(sign, digits, exponent)’.

      -- 成員函式: canonical ()

          Return the canonical encoding of the argument.  Currently, the
          encoding of a *note Decimal: 189. instance is always
          canonical, so this operation returns its argument unchanged.

      -- 成員函式: compare (other, context=None)

          Compare the values of two Decimal instances.  *note compare():
          1a7c. 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(): 1a7c.
          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(): 1a7c. method, but the result gives a total ordering
          on *note Decimal: 189. instances.  Two *note Decimal: 189.
          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(): 1a7e, 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: 1a68. rounding mode.

               >>> Decimal(1).exp()
               Decimal('2.718281828459045235360287471')
               >>> Decimal(321).exp()
               Decimal('2.561702493119680037517373933E+139')

      -- 成員函式: from_float (f)

          Classmethod that converts a float to a decimal number,
          exactly.

          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: 189.
               instance can also be constructed directly from a *note
               float: 188.

               >>> 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: 49e. if the argument is canonical and *note
          False: 38d. otherwise.  Currently, a *note Decimal: 189.
          instance is always canonical, so this operation always returns
          *note True: 49e.

      -- 成員函式: is_finite ()

          Return *note True: 49e. if the argument is a finite number,
          and *note False: 38d. if the argument is an infinity or a NaN.

      -- 成員函式: is_infinite ()

          Return *note True: 49e. if the argument is either positive or
          negative infinity and *note False: 38d. otherwise.

      -- 成員函式: is_nan ()

          Return *note True: 49e. if the argument is a (quiet or
          signaling) NaN and *note False: 38d. otherwise.

      -- 成員函式: is_normal (context=None)

          Return *note True: 49e. if the argument is a `normal' finite
          number.  Return *note False: 38d. if the argument is zero,
          subnormal, infinite or a NaN.

      -- 成員函式: is_qnan ()

          Return *note True: 49e. if the argument is a quiet NaN, and
          *note False: 38d. otherwise.

      -- 成員函式: is_signed ()

          Return *note True: 49e. if the argument has a negative sign
          and *note False: 38d. otherwise.  Note that zeros and NaNs can
          both carry signs.

      -- 成員函式: is_snan ()

          Return *note True: 49e. if the argument is a signaling NaN and
          *note False: 38d. otherwise.

      -- 成員函式: is_subnormal (context=None)

          Return *note True: 49e. if the argument is subnormal, and
          *note False: 38d. otherwise.

      -- 成員函式: is_zero ()

          Return *note True: 49e. if the argument is a (positive or
          negative) zero and *note False: 38d. otherwise.

      -- 成員函式: ln (context=None)

          Return the natural (base e) logarithm of the operand.  The
          result is correctly rounded using the *note ROUND_HALF_EVEN:
          1a68. rounding mode.

      -- 成員函式: log10 (context=None)

          Return the base ten logarithm of the operand.  The result is
          correctly rounded using the *note ROUND_HALF_EVEN: 1a68.
          rounding mode.

      -- 成員函式: logb (context=None)

          For a nonzero number, return the adjusted exponent of its
          operand as a *note Decimal: 189. instance.  If the operand is
          a zero then ‘Decimal('-Infinity')’ is returned and the *note
          DivisionByZero: 1a6d. flag is raised.  If the operand is an
          infinity then ‘Decimal('Infinity')’ is returned.

      -- 成員函式: logical_and (other, context=None)

          *note logical_and(): 1a91. is a logical operation which takes
          two `logical operands' (see *note Logical operands: 1a92.).
          The result is the digit-wise ‘and’ of the two operands.

      -- 成員函式: logical_invert (context=None)

          *note logical_invert(): 1a93. is a logical operation.  The
          result is the digit-wise inversion of the operand.

      -- 成員函式: logical_or (other, context=None)

          *note logical_or(): 1a94. is a logical operation which takes
          two `logical operands' (see *note Logical operands: 1a92.).
          The result is the digit-wise ‘or’ of the two operands.

      -- 成員函式: logical_xor (other, context=None)

          *note logical_xor(): 1a95. is a logical operation which takes
          two `logical operands' (see *note Logical operands: 1a92.).
          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(): 1a96. 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(): 1a98. 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)

          Normalize the number by stripping the rightmost trailing zeros
          and converting any result equal to ‘Decimal('0')’ to
          ‘Decimal('0e0')’.  Used for producing canonical values for
          attributes of an equivalence class.  For example,
          ‘Decimal('32.100')’ and ‘Decimal('0.321000e+2')’ both
          normalize to the equivalent value ‘Decimal('32.1')’.

      -- 成員函式: 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: 9f0. 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 ‘Etiny’.

      -- 成員函式: radix ()

          Return ‘Decimal(10)’, the radix (base) in which the *note
          Decimal: 189. 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(): 1aa8. 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: 1a6e.
          or *note Rounded: 1a6f. 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:
          1a6e. or *note Rounded: 1a6f.  If given, applies `rounding';
          otherwise, uses the rounding method in either the supplied
          `context' or the current context.

* Menu:

* Logical operands::


File: python.info,  Node: Logical operands,  Up: Decimal objects

5.9.4.3 Logical operands
........................

The ‘logical_and()’, ‘logical_invert()’, ‘logical_or()’, and
‘logical_xor()’ methods expect their arguments to be `logical operands'.
A `logical operand' is a *note Decimal: 189. instance whose exponent and
sign are both zero, and whose digits are all either ‘0’ or ‘1’.


File: python.info,  Node: Context objects,  Next: Constants<4>,  Prev: Decimal objects,  Up: decimal --- Decimal fixed point and floating point arithmetic

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(): 1a75. and *note setcontext(): 1a76.
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: 6ee. statement and the *note
localcontext(): 16e2. function to temporarily change the active context.

 -- 函式: decimal.localcontext (ctx=None)

     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.

     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

New contexts can also be created using the *note Context: 9f5.
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: 1a69.  All flags are cleared.  All
     traps are enabled (treated as exceptions) except *note Inexact:
     1a6e, *note Rounded: 1a6f, and *note Subnormal: 1a70.

     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: 1a68.  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: 9f5. 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: 9f5. 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 ‘prec’=‘28’, ‘rounding’=*note
     ROUND_HALF_EVEN: 1a68, and enabled traps for *note Overflow: 1a71,
     *note InvalidOperation: 9f0, and *note DivisionByZero: 1a6d.

In addition to the three supplied contexts, new contexts can be created
with the *note Context: 9f5. 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: 158, the default values are copied from the *note
     DefaultContext: 9ed.  If the `flags' field is not specified or is
     *note None: 158, all flags are cleared.

     `prec' is an integer in the range [‘1’, *note MAX_PREC: 1aad.] 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: 1aae.

     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: 1aaf, ‘0’], `Emax' in the range [‘0’, *note MAX_EMAX:
     1ab0.].

     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: 189. 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: 189. 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: 9f5. 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: 189. methods described above (with the exception of the
     ‘adjusted()’ and ‘as_tuple()’ methods) there is a corresponding
     *note Context: 9f5. method.  For example, for a *note Context: 9f5.
     instance ‘C’ and *note Decimal: 189. instance ‘x’, ‘C.exp(x)’ is
     equivalent to ‘x.exp(context=C)’.  Each *note Context: 9f5. method
     accepts a Python integer (an instance of *note int: 185.) 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: 189. 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(): b85. 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: 1ab6.

      -- 成員函式: Etop ()

          Returns a value equal to ‘Emax - prec + 1’.

     The usual approach to working with decimals is to create *note
     Decimal: 189. 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: 189. 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(): 1ae2. in
          terms of the correctly-rounded *note exp(): 1ac4. and *note
          ln(): 1acf. 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: Constants<4>,  Next: Rounding modes,  Prev: Context objects,  Up: decimal --- Decimal fixed point and floating point arithmetic

5.9.4.5 Constants
.................

The constants in this section are only relevant for the C module.  They
are also included in the pure Python version for compatibility.

                          32-bit                    64-bit
                                                    
----------------------------------------------------------------------------------------
                                                    
 -- Data:                 ‘425000000’               ‘999999999999999999’
          decimal.MAX_PREC                          

 -- Data:                 ‘425000000’               ‘999999999999999999’
          decimal.MAX_EMAX                          

 -- Data:                 ‘-425000000’              ‘-999999999999999999’
          decimal.MIN_EMIN                          

 -- Data:                 ‘-849999999’              ‘-1999999999999999997’
          decimal.MIN_ETINY                         

 -- Data: decimal.HAVE_THREADS

     The value is ‘True’.  Deprecated, because Python now always has
     threads.

3.9 版後已棄用.

 -- Data: decimal.HAVE_CONTEXTVAR

     The default value is ‘True’.  If Python is compiled
     ‘--without-decimal-contextvar’, 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.9 版新加入: backported to 3.7 and 3.8


File: python.info,  Node: Rounding modes,  Next: Signals,  Prev: Constants<4>,  Up: decimal --- Decimal fixed point and floating point arithmetic

5.9.4.6 Rounding modes
......................

 -- Data: decimal.ROUND_CEILING

     Round towards ‘Infinity’.

 -- Data: decimal.ROUND_DOWN

     Round towards zero.

 -- Data: decimal.ROUND_FLOOR

     Round towards ‘-Infinity’.

 -- Data: decimal.ROUND_HALF_DOWN

     Round to nearest with ties going towards zero.

 -- Data: decimal.ROUND_HALF_EVEN

     Round to nearest with ties going to nearest even integer.

 -- Data: decimal.ROUND_HALF_UP

     Round to nearest with ties going away from zero.

 -- Data: decimal.ROUND_UP

     Round away from zero.

 -- Data: 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 --- Decimal fixed point and floating point arithmetic

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: 1a6d. trap is set, then a *note DivisionByZero: 1a6d.
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: 1703.

 -- 類別: 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 ‘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:
     1a6e. and *note Rounded: 1a6f. 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: 1a6e. and *note Subnormal: 1a70. 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: 189. constructor, *note
     create_decimal(): 9f1. and all comparison operators.  Both
     conversion and comparisons are exact.  Any occurrence of a mixed
     operation is silently recorded by setting *note FloatOperation:
     9ea. in the context flags.  Explicit conversions with *note
     from_float(): b85. or *note create_decimal_from_float(): 1ab5. 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: 9ea.

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 --- Decimal fixed point and floating point arithmetic

5.9.4.8 Floating Point Notes
............................

* Menu:

* Mitigating round-off error with increased precision::
* Special values::


File: python.info,  Node: Mitigating round-off error with increased precision,  Next: Special values,  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: 36. 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: Special values,  Prev: Mitigating round-off error with increased precision,  Up: Floating Point Notes

5.9.4.10 Special values
.......................

The number system for the *note decimal: 36. 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: 1a6d. signal is not trapped.  Likewise, when the *note
Overflow: 1a71. 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: 9f0. 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: 38d.
(even when doing ‘Decimal('NaN')==Decimal('NaN')’), while a test for
inequality always returns *note True: 49e.  An attempt to compare two
Decimals using any of the ‘<’, ‘<=’, ‘>’ or ‘>=’ operators will raise
the *note InvalidOperation: 9f0. signal if either operand is a ‘NaN’,
and return *note False: 38d. 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 ‘compare()’ and
‘compare-signal()’ 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 --- Decimal fixed point and floating point arithmetic

5.9.4.11 Working with threads
.............................

The *note getcontext(): 1a75. function accesses a different *note
Context: 9f5. 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(): 1a76. function automatically assigns
its target to the current thread.

If *note setcontext(): 1a76. has not been called before *note
getcontext(): 1a75, then *note getcontext(): 1a75. 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(): 1a75.  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 --- Decimal fixed point and floating point arithmetic

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: 189. 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 --- Decimal fixed point and floating point arithmetic

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 ‘quantize()’ method rounds to a fixed number of decimal places.
If the *note Inexact: 1a6e. 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 ‘quantize()’ 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 ‘quantize()’ 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 ‘normalize()’ 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. 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: 189.?

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(): 9f1. 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.
‘libmpdec’ uses Karatsuba multiplication(2) for medium-sized numbers and
the Number Theoretic Transform(3) for very large numbers.  However, to
realize this performance gain, the context needs to be set for unrounded
calculations.

     >>> c = getcontext()
     >>> c.prec = MAX_PREC
     >>> c.Emax = MAX_EMAX
     >>> c.Emin = MIN_EMIN

3.3 版新加入.

   ---------- Footnotes ----------

   (1) https://www.bytereef.org/mpdecimal/doc/libmpdec/index.html

   (2) https://en.wikipedia.org/wiki/Karatsuba_algorithm

   (3) 
https://en.wikipedia.org/wiki/Discrete_Fourier_transform_(general)#Number-theoretic_transform


File: python.info,  Node: fractions --- Rational numbers,  Next: random --- Generate pseudo-random numbers,  Prev: decimal --- Decimal fixed point and floating point arithmetic,  Up: 數值與數學模組

5.9.5 ‘fractions’ — Rational numbers
------------------------------------

`Source code:' Lib/fractions.py(1)

__________________________________________________________________

The *note fractions: 83. 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: c5d. and returns a new *note
     Fraction: 186. instance with value ‘numerator/denominator’.  If
     `denominator' is ‘0’, it raises a *note ZeroDivisionError: 12b2.
     The second version requires that `other_fraction' is an instance of
     *note numbers.Rational: c5d. and returns a *note Fraction: 186.
     instance with the same value.  The next two versions accept either
     a *note float: 188. or a *note decimal.Decimal: 189. instance, and
     return a *note Fraction: 186. instance with exactly the same value.
     Note that due to the usual issues with binary floating-point (see
     *note 浮點數運算：問題與限制: 1327.), 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(): 1b03. 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.  In
     addition, any string that represents a finite value and is accepted
     by the *note float: 188. constructor is also accepted by the *note
     Fraction: 186. 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: 186. class inherits from the abstract base
     class *note numbers.Rational: c5d, and implements all of the
     methods and operations from that class.  *note Fraction: 186.
     instances are hashable, and should be treated as immutable.  In
     addition, *note Fraction: 186. has the following properties and
     methods:

     3.2 版更變: The *note Fraction: 186. constructor now accepts *note
     float: 188. and *note decimal.Decimal: 189. instances.

      -- 屬性: 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
          Fraction and with a positive denominator.

          3.8 版新加入.

      -- 成員函式: from_float (flt)

          This class method constructs a *note Fraction: 186.
          representing the exact value of `flt', which must be a *note
          float: 188.  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: 186. instance directly from a *note
               float: 188.

      -- 成員函式: from_decimal (dec)

          This class method constructs a *note Fraction: 186.
          representing the exact value of `dec', which must be a *note
          decimal.Decimal: 189. instance.

               備註: From Python 3.2 onwards, you can also construct a
               *note Fraction: 186. instance directly from a *note
               decimal.Decimal: 189. instance.

      -- 成員函式: limit_denominator (max_denominator=1000000)

          Finds and returns the closest *note Fraction: 186. 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: 185. ‘<= self’.  This method
          can also be accessed through the *note math.floor(): d31.
          function:

               >>> from math import floor
               >>> floor(Fraction(355, 113))
               3

      -- 成員函式: __ceil__ ()

          Returns the least *note int: 185. ‘>= self’.  This method can
          also be accessed through the *note math.ceil(): d32. function.

      -- 成員函式: __round__ ()

      -- 成員函式: __round__ (ndigits)

          The first version returns the nearest *note int: 185. 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(): c72. function.

 -- 函式: fractions.gcd (a, b)

     Return the greatest common divisor of the integers `a' and `b'.  If
     either `a' or `b' is nonzero, then the absolute value of ‘gcd(a,
     b)’ is the largest integer that divides both `a' and `b'.
     ‘gcd(a,b)’ has the same sign as `b' if `b' is nonzero; otherwise it
     takes the sign of `a'.  ‘gcd(0, 0)’ returns ‘0’.

     3.5 版後已棄用: Use *note math.gcd(): 71b. instead.

也參考
......

Module *note numbers: c2.

     The abstract base classes making up the numeric tower.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/fractions.py


File: python.info,  Node: random --- Generate pseudo-random numbers,  Next: statistics --- 數學統計函式,  Prev: fractions --- Rational numbers,  Up: 數值與數學模組

5.9.6 ‘random’ — Generate pseudo-random numbers
-----------------------------------------------

`Source code:' Lib/random.py(1)

__________________________________________________________________

This module implements pseudo-random number generators for various
distributions.

For integers, there is uniform selection from a range.  For sequences,
there is uniform selection of a random element, a function to generate a
random permutation of a list in-place, and a function for random
sampling without replacement.

On the real line, there are functions to compute uniform, normal
(Gaussian), lognormal, negative exponential, gamma, and beta
distributions.  For generating distributions of angles, the von Mises
distribution is available.

Almost all module functions depend on the basic function *note random():
1b0c, which generates a random float uniformly in the semi-open range
[0.0, 1.0).  Python uses the Mersenne Twister as the core generator.  It
produces 53-bit precision floats and has a period of 2**19937-1.  The
underlying implementation in C is both fast and threadsafe.  The
Mersenne Twister is one of the most extensively tested random number
generators in existence.  However, being completely deterministic, it is
not suitable for all purposes, and is completely unsuitable for
cryptographic purposes.

The functions supplied by this module are actually bound methods of a
hidden instance of the *note random.Random: 1b0d. class.  You can
instantiate your own instances of *note Random: 1b0d. to get generators
that don’t share state.

Class *note Random: 1b0d. can also be subclassed if you want to use a
different basic generator of your own devising: in that case, override
the ‘random()’, ‘seed()’, ‘getstate()’, and ‘setstate()’ methods.
Optionally, a new generator can supply a ‘getrandbits()’ method — this
allows *note randrange(): bc0. to produce selections over an arbitrarily
large range.

The *note random: dd. module also provides the *note SystemRandom: 1b0e.
class which uses the system function *note os.urandom(): 4d6. to
generate random numbers from sources provided by the operating system.

     警告: The pseudo-random generators of this module should not be
     used for security purposes.  For security or cryptographic uses,
     see the *note secrets: e5. 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 recipe(2) for a compatible alternative
random number generator with a long period and comparatively simple
update operations.

* Menu:

* Bookkeeping functions::
* Functions for integers::
* Functions for sequences::
* Real-valued distributions::
* Alternative Generator::
* Notes on Reproducibility::
* Examples and Recipes::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/random.py

   (2) https://code.activestate.com/recipes/576707/


File: python.info,  Node: Bookkeeping functions,  Next: Functions for integers,  Up: random --- Generate pseudo-random numbers

5.9.6.1 Bookkeeping functions
.............................

 -- 函式: random.seed (a=None, version=2)

     Initialize the random number generator.

     If `a' is omitted or ‘None’, the current system time is used.  If
     randomness sources are provided by the operating system, they are
     used instead of the system time (see the *note os.urandom(): 4d6.
     function for details on availability).

     If `a' is an int, it is used directly.

     With version 2 (the default), a *note str: 335, *note bytes: 336,
     or *note bytearray: 337. object gets converted to an *note int:
     185. and all of its bits are used.

     With version 1 (provided for reproducing random sequences from
     older versions of Python), the algorithm for *note str: 335. and
     *note bytes: 336. generates a narrower range of seeds.

     3.2 版更變: Moved to the version 2 scheme which uses all of the
     bits in a string seed.

 -- 函式: random.getstate ()

     Return an object capturing the current internal state of the
     generator.  This object can be passed to *note setstate(): 1b11. to
     restore the state.

 -- 函式: random.setstate (state)

     `state' should have been obtained from a previous call to *note
     getstate(): 1b10, and *note setstate(): 1b11. restores the internal
     state of the generator to what it was at the time *note getstate():
     1b10. was called.

 -- 函式: random.getrandbits (k)

     Returns a Python integer with `k' random bits.  This method is
     supplied with the Mersenne Twister generator and some other
     generators may also provide it as an optional part of the API. When
     available, *note getrandbits(): 938. enables *note randrange():
     bc0. to handle arbitrarily large ranges.


File: python.info,  Node: Functions for integers,  Next: Functions for sequences,  Prev: Bookkeeping functions,  Up: random --- Generate pseudo-random numbers

5.9.6.2 Functions for integers
..............................

 -- 函式: random.randrange (stop)

 -- 函式: random.randrange (start, stop[, step])

     Return a randomly selected element from ‘range(start, stop, step)’.
     This is equivalent to ‘choice(range(start, stop, step))’, but
     doesn’t actually build a range object.

     The positional argument pattern matches that of *note range(): 9c3.
     Keyword arguments should not be used because the function may use
     them in unexpected ways.

     3.2 版更變: *note randrange(): bc0. is more sophisticated about
     producing equally distributed values.  Formerly it used a style
     like ‘int(random()*n)’ which could produce slightly uneven
     distributions.

 -- 函式: random.randint (a, b)

     Return a random integer `N' such that ‘a <= N <= b’.  Alias for
     ‘randrange(a, b+1)’.


File: python.info,  Node: Functions for sequences,  Next: Real-valued distributions,  Prev: Functions for integers,  Up: random --- Generate pseudo-random numbers

5.9.6.3 Functions for sequences
...............................

 -- 函式: random.choice (seq)

     Return a random element from the non-empty sequence `seq'.  If
     `seq' is empty, raises *note IndexError: e7a.

 -- 函式: random.choices (population, weights=None, *, cum_weights=None,
          k=1)

     Return a `k' sized list of elements chosen from the `population'
     with replacement.  If the `population' is empty, raises *note
     IndexError: e7a.

     If a `weights' sequence is specified, selections are made according
     to the relative weights.  Alternatively, if a `cum_weights'
     sequence is given, the selections are made according to the
     cumulative weights (perhaps computed using *note
     itertools.accumulate(): 1de.).  For example, the relative weights
     ‘[10, 5, 30, 5]’ are equivalent to the cumulative weights ‘[10, 15,
     45, 50]’.  Internally, the relative weights are converted to
     cumulative weights before making selections, so supplying the
     cumulative weights saves work.

     If neither `weights' nor `cum_weights' are specified, selections
     are made with equal probability.  If a weights sequence is
     supplied, it must be the same length as the `population' sequence.
     It is a *note TypeError: 193. to specify both `weights' and
     `cum_weights'.

     The `weights' or `cum_weights' can use any numeric type that
     interoperates with the *note float: 188. values returned by *note
     random(): dd. (that includes integers, floats, and fractions but
     excludes decimals).  Weights are assumed to be non-negative.

     For a given seed, the *note choices(): 579. function with equal
     weighting typically produces a different sequence than repeated
     calls to *note choice(): bc2.  The algorithm used by *note
     choices(): 579. uses floating point arithmetic for internal
     consistency and speed.  The algorithm used by *note choice(): bc2.
     defaults to integer arithmetic with repeated selections to avoid
     small biases from round-off error.

     3.6 版新加入.

 -- 函式: random.shuffle (x[, random])

     Shuffle the sequence `x' in place.

     The optional argument `random' is a 0-argument function returning a
     random float in [0.0, 1.0); by default, this is the function *note
     random(): 1b0c.

     To shuffle an immutable sequence and return a new shuffled list,
     use ‘sample(x, k=len(x))’ instead.

     Note that even for small ‘len(x)’, the total number of permutations
     of `x' can quickly grow larger than the period of most random
     number generators.  This implies that most permutations of a long
     sequence can never be generated.  For example, a sequence of length
     2080 is the largest that can fit within the period of the Mersenne
     Twister random number generator.

 -- 函式: random.sample (population, k)

     Return a `k' length list of unique elements chosen from the
     population sequence or set.  Used for random sampling without
     replacement.

     Returns a new list containing elements from the population while
     leaving the original population unchanged.  The resulting list is
     in selection order so that all sub-slices will also be valid random
     samples.  This allows raffle winners (the sample) to be partitioned
     into grand prize and second place winners (the subslices).

     Members of the population need not be *note hashable: 142e. or
     unique.  If the population contains repeats, then each occurrence
     is a possible selection in the sample.

     To choose a sample from a range of integers, use a *note range():
     9c3. object as an argument.  This is especially fast and space
     efficient for sampling from a large population:
     ‘sample(range(10000000), k=60)’.

     If the sample size is larger than the population size, a *note
     ValueError: 1fc. is raised.


File: python.info,  Node: Real-valued distributions,  Next: Alternative Generator,  Prev: Functions for sequences,  Up: random --- Generate pseudo-random numbers

5.9.6.4 Real-valued distributions
.................................

The following functions generate specific real-valued distributions.
Function parameters are named after the corresponding variables in the
distribution’s equation, as used in common mathematical practice; most
of these equations can be found in any statistics text.

 -- 函式: random.random ()

     Return the next random floating point number in the range [0.0,
     1.0).

 -- 函式: random.uniform (a, b)

     Return a random floating point number `N' such that ‘a <= N <= b’
     for ‘a <= b’ and ‘b <= N <= a’ for ‘b < a’.

     The end-point value ‘b’ may or may not be included in the range
     depending on floating-point rounding in the equation ‘a + (b-a) *
     random()’.

 -- 函式: random.triangular (low, high, mode)

     Return a random floating point number `N' such that ‘low <= N <=
     high’ and with the specified `mode' between those bounds.  The
     `low' and `high' bounds default to zero and one.  The `mode'
     argument defaults to the midpoint between the bounds, giving a
     symmetric distribution.

 -- 函式: random.betavariate (alpha, beta)

     Beta distribution.  Conditions on the parameters are ‘alpha > 0’
     and ‘beta > 0’.  Returned values range between 0 and 1.

 -- 函式: random.expovariate (lambd)

     Exponential distribution.  `lambd' is 1.0 divided by the desired
     mean.  It should be nonzero.  (The parameter would be called
     "lambda", but that is a reserved word in Python.)  Returned values
     range from 0 to positive infinity if `lambd' is positive, and from
     negative infinity to 0 if `lambd' is negative.

 -- 函式: random.gammavariate (alpha, beta)

     Gamma distribution.  (`Not' the gamma function!)  Conditions on the
     parameters are ‘alpha > 0’ and ‘beta > 0’.

     The probability distribution function is:

                    x ** (alpha - 1) * math.exp(-x / beta)
          pdf(x) =  --------------------------------------
                      math.gamma(alpha) * beta ** alpha

 -- 函式: random.gauss (mu, sigma)

     Gaussian distribution.  `mu' is the mean, and `sigma' is the
     standard deviation.  This is slightly faster than the *note
     normalvariate(): 1b1b. function defined below.

 -- 函式: random.lognormvariate (mu, sigma)

     Log normal distribution.  If you take the natural logarithm of this
     distribution, you’ll get a normal distribution with mean `mu' and
     standard deviation `sigma'.  `mu' can have any value, and `sigma'
     must be greater than zero.

 -- 函式: random.normalvariate (mu, sigma)

     Normal distribution.  `mu' is the mean, and `sigma' is the standard
     deviation.

 -- 函式: random.vonmisesvariate (mu, kappa)

     `mu' is the mean angle, expressed in radians between 0 and 2*`pi',
     and `kappa' is the concentration parameter, which must be greater
     than or equal to zero.  If `kappa' is equal to zero, this
     distribution reduces to a uniform random angle over the range 0 to
     2*`pi'.

 -- 函式: random.paretovariate (alpha)

     Pareto distribution.  `alpha' is the shape parameter.

 -- 函式: random.weibullvariate (alpha, beta)

     Weibull distribution.  `alpha' is the scale parameter and `beta' is
     the shape parameter.


File: python.info,  Node: Alternative Generator,  Next: Notes on Reproducibility,  Prev: Real-valued distributions,  Up: random --- Generate pseudo-random numbers

5.9.6.5 Alternative Generator
.............................

 -- 類別: random.Random ([seed])

     Class that implements the default pseudo-random number generator
     used by the *note random: dd. module.

 -- 類別: random.SystemRandom ([seed])

     Class that uses the *note os.urandom(): 4d6. function for
     generating random numbers from sources provided by the operating
     system.  Not available on all systems.  Does not rely on software
     state, and sequences are not reproducible.  Accordingly, the *note
     seed(): c0d. method has no effect and is ignored.  The *note
     getstate(): 1b10. and *note setstate(): 1b11. methods raise *note
     NotImplementedError: 613. if called.


File: python.info,  Node: Notes on Reproducibility,  Next: Examples and Recipes,  Prev: Alternative Generator,  Up: random --- Generate pseudo-random numbers

5.9.6.6 Notes on Reproducibility
................................

Sometimes it is useful to be able to reproduce the sequences given by a
pseudo random number generator.  By re-using a seed value, the same
sequence should be reproducible from run to run as long as multiple
threads are not running.

Most of the random module’s algorithms and seeding functions are subject
to change across Python versions, but two aspects are guaranteed not to
change:

   * If a new seeding method is added, then a backward compatible seeder
     will be offered.

   * The generator’s ‘random()’ method will continue to produce the same
     sequence when the compatible seeder is given the same seed.


File: python.info,  Node: Examples and Recipes,  Prev: Notes on Reproducibility,  Up: random --- Generate pseudo-random numbers

5.9.6.7 Examples and Recipes
............................

Basic examples:

     >>> 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]

Simulations:

     >>> # 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
     >>> # (a ten, jack, queen, or king).
     >>> deck = collections.Counter(tens=16, low_cards=36)
     >>> seen = sample(list(deck.elements()), k=20)
     >>> seen.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.
     >>> def trial():
     ...     return choices('HT', cum_weights=(0.60, 1.00), k=7).count('H') >= 5
     ...
     >>> sum(trial() 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

Example of statistical bootstrapping(1) using resampling with
replacement to estimate a confidence interval for the mean of a sample:

     # http://statistics.about.com/od/Applications/a/Example-Of-Bootstrapping.htm
     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}')

Example of a resampling permutation test(2) to determine the statistical
significance or p-value(3) of an observed difference between the effects
of a drug versus a placebo:

     # 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.')

Simulation of arrival times and service deliveries for a multiserver
queue:

     from heapq import heappush, heappop
     from random import expovariate, gauss
     from statistics import mean, median, stdev

     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
     for i in range(100_000):
         arrival_time += expovariate(1.0 / average_arrival_interval)
         next_server_available = heappop(servers)
         wait = max(0.0, next_server_available - arrival_time)
         waits.append(wait)
         service_duration = gauss(average_service_time, stdev_service_time)
         service_completed = arrival_time + wait + service_duration
         heappush(servers, service_completed)

     print(f'Mean wait: {mean(waits):.1f}.  Stdev wait: {stdev(waits):.1f}.')
     print(f'Median wait: {median(waits):.1f}.  Max wait: {max(waits):.1f}.')

也參考
......

Statistics for Hackers(4) a video tutorial by Jake Vanderplas(5) on
statistical analysis using just a few fundamental concepts including
simulation, sampling, shuffling, and cross-validation.

Economics Simulation(6) a simulation of a marketplace by Peter Norvig(7)
that shows effective use of many of the tools and distributions provided
by this module (gauss, uniform, sample, betavariate, choice, triangular,
and randrange).

A Concrete Introduction to Probability (using Python)(8) a tutorial by
Peter Norvig(9) covering the basics of probability theory, how to write
simulations, and how to perform data analysis using 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) 
http://nbviewer.jupyter.org/url/norvig.com/ipython/Economics.ipynb

   (7) http://norvig.com/bio.html

   (8) 
http://nbviewer.jupyter.org/url/norvig.com/ipython/Probability.ipynb

   (9) http://norvig.com/bio.html


File: python.info,  Node: statistics --- 數學統計函式,  Prev: random --- Generate pseudo-random numbers,  Up: 數值與數學模組

5.9.7 ‘statistics’ — 數學統計函式
---------------------------------

3.4 版新加入.

`Source code:' Lib/statistics.py(1)

__________________________________________________________________

This module provides functions for calculating mathematical statistics
of numeric (*note Real: 142a.-valued) data.

The module is not intended to be a competitor to third-party libraries
such as NumPy(2), SciPy(3), or proprietary full-featured statistics
packages aimed at professional statisticians such as Minitab, SAS and
Matlab.  It is aimed at the level of graphing and scientific
calculators.

Unless explicitly noted, these functions support *note int: 185, *note
float: 188, *note Decimal: 189. and *note Fraction: 186.  Behaviour with
other types (whether in the numeric tower or not) is currently
unsupported.  Collections with a mix of types are also undefined and
implementation-dependent.  If your input data consists of mixed types,
you may be able to use *note map(): c32. to ensure a consistent result,
for example: ‘map(float, input_data)’.

* Menu:

* 平均值與中央位置量數::
* 離度 (spread) 的測量: 離度 spread 的測量.
* 函式細節::
* Exceptions: Exceptions<2>.
* NormalDist objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/statistics.py

   (2) https://numpy.org

   (3) https://www.scipy.org/


File: python.info,  Node: 平均值與中央位置量數,  Next: 離度 spread 的測量,  Up: statistics --- 數學統計函式

5.9.7.1 平均值與中央位置量數
............................

這些函式計算來自一個母體或樣本的平均值或代表值。

*note mean(): 19a.          數據的算術平均（平均值）。
                            
                            
*note fmean(): 228.         Fast, floating point arithmetic mean.
                            
                            
*note geometric_mean(): 229.Geometric mean of data.
                            
                            
*note harmonic_mean(): 594. Harmonic mean of data.
                            
                            
*note median(): 1b26.       數據的中位數（中間值）。
                            
                            
*note median_low(): 1b27.   數據中較小的中位數。
                            
                            
*note median_high(): 1b28.  數據中較大的中位數。
                            
                            
*note median_grouped(): 1b29.分組數據的中位數或50%處。
                            
                            
*note mode(): 2bc.          Single mode (most common value) of discrete or nominal data.
                            
                            
*note multimode(): 22a.     List of modes (most common values) of discrete or nomimal data.
                            
                            
*note quantiles(): 22b.     Divide data into intervals with equal probability.
                            


File: python.info,  Node: 離度 spread 的測量,  Next: 函式細節,  Prev: 平均值與中央位置量數,  Up: statistics --- 數學統計函式

5.9.7.2 離度 (spread) 的測量
............................

這些函式計算母體或樣本偏離平均值的程度。

*note pstdev(): 1b2b.       數據的母體標準差
                            
                            
*note pvariance(): 1b2c.    數據的母體變異數
                            
                            
*note stdev(): 1b2d.        數據的樣本標準差
                            
                            
*note variance(): 1b2e.     數據的樣本變異數
                            


File: python.info,  Node: 函式細節,  Next: Exceptions<2>,  Prev: 離度 spread 的測量,  Up: statistics --- 數學統計函式

5.9.7.3 函式細節
................

Note: The functions do not require the data given to them to be sorted.
However, for reading convenience, most of the examples show sorted
sequences.

 -- 函式: statistics.mean (data)

     Return the sample arithmetic mean of `data' which can be a sequence
     or iterable.

     The arithmetic mean is the sum of the data divided by the number of
     data points.  It is commonly called "the average", although it is
     only one of many different mathematical averages.  It is a measure
     of the central location of the data.

     If `data' is empty, *note StatisticsError: 1b30. will be raised.

     Some examples of use:

          >>> 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')

          備註: The mean is strongly affected by outliers and is not a
          robust estimator for central location: the mean is not
          necessarily a typical example of the data points.  For more
          robust measures of central location, see *note median(): 1b26.
          and *note mode(): 2bc.

          The sample mean gives an unbiased estimate of the true
          population mean, so that when taken on average over all the
          possible samples, ‘mean(sample)’ converges on the true mean of
          the entire population.  If `data' represents the entire
          population rather than a sample, then ‘mean(data)’ is
          equivalent to calculating the true population mean μ.

 -- 函式: statistics.fmean (data)

     Convert `data' to floats and compute the arithmetic mean.

     This runs faster than the *note mean(): 19a. function and it always
     returns a *note float: 188.  The `data' may be a sequence or
     iterable.  If the input dataset is empty, raises a *note
     StatisticsError: 1b30.

          >>> fmean([3.5, 4.0, 5.25])
          4.25

     3.8 版新加入.

 -- 函式: statistics.geometric_mean (data)

     Convert `data' to floats and compute the geometric mean.

     The geometric mean indicates the central tendency or typical value
     of the `data' using the product of the values (as opposed to the
     arithmetic mean which uses their sum).

     Raises a *note StatisticsError: 1b30. if the input dataset is
     empty, if it contains a zero, or if it contains a negative value.
     The `data' may be a sequence or iterable.

     No special efforts are made to achieve exact results.  (However,
     this may change in the future.)

          >>> round(geometric_mean([54, 24, 36]), 1)
          36.0

     3.8 版新加入.

 -- 函式: statistics.harmonic_mean (data)

     Return the harmonic mean of `data', a sequence or iterable of
     real-valued numbers.

     The harmonic mean, sometimes called the subcontrary mean, is the
     reciprocal of the arithmetic *note mean(): 19a. of the reciprocals
     of the data.  For example, the harmonic mean of three values `a',
     `b' and `c' will be equivalent to ‘3/(1/a + 1/b + 1/c)’.  If one of
     the values is zero, the result will be zero.

     The harmonic mean is a type of average, a measure of the central
     location of the data.  It is often appropriate when averaging rates
     or ratios, for example speeds.

     Suppose a car travels 10 km at 40 km/hr, then another 10 km at 60
     km/hr.  What is the average speed?

          >>> harmonic_mean([40, 60])
          48.0

     Suppose an investor purchases an equal value of shares in each of
     three companies, with P/E (price/earning) ratios of 2.5, 3 and 10.
     What is the average P/E ratio for the investor’s portfolio?

          >>> harmonic_mean([2.5, 3, 10])  # For an equal investment portfolio.
          3.6

     *note StatisticsError: 1b30. is raised if `data' is empty, or any
     element is less than zero.

     The current algorithm has an early-out when it encounters a zero in
     the input.  This means that the subsequent inputs are not tested
     for validity.  (This behavior may change in the future.)

     3.6 版新加入.

 -- 函式: statistics.median (data)

     Return the median (middle value) of numeric data, using the common
     "mean of middle two" method.  If `data' is empty, *note
     StatisticsError: 1b30. is raised.  `data' can be a sequence or
     iterable.

     The median is a robust measure of central location and is less
     affected by the presence of outliers.  When the number of data
     points is odd, the middle data point is returned:

          >>> median([1, 3, 5])
          3

     When the number of data points is even, the median is interpolated
     by taking the average of the two middle values:

          >>> median([1, 3, 5, 7])
          4.0

     This is suited for when your data is discrete, and you don’t mind
     that the median may not be an actual data point.

     If the data is ordinal (supports order operations) but not numeric
     (doesn’t support addition), consider using *note median_low():
     1b27. or *note median_high(): 1b28. instead.

 -- 函式: statistics.median_low (data)

     Return the low median of numeric data.  If `data' is empty, *note
     StatisticsError: 1b30. is raised.  `data' can be a sequence or
     iterable.

     The low median is always a member of the data set.  When the number
     of data points is odd, the middle value is returned.  When it is
     even, the smaller of the two middle values is returned.

          >>> median_low([1, 3, 5])
          3
          >>> median_low([1, 3, 5, 7])
          3

     Use the low median when your data are discrete and you prefer the
     median to be an actual data point rather than interpolated.

 -- 函式: statistics.median_high (data)

     Return the high median of data.  If `data' is empty, *note
     StatisticsError: 1b30. is raised.  `data' can be a sequence or
     iterable.

     The high median is always a member of the data set.  When the
     number of data points is odd, the middle value is returned.  When
     it is even, the larger of the two middle values is returned.

          >>> median_high([1, 3, 5])
          3
          >>> median_high([1, 3, 5, 7])
          5

     Use the high median when your data are discrete and you prefer the
     median to be an actual data point rather than interpolated.

 -- 函式: statistics.median_grouped (data, interval=1)

     Return the median of grouped continuous data, calculated as the
     50th percentile, using interpolation.  If `data' is empty, *note
     StatisticsError: 1b30. is raised.  `data' can be a sequence or
     iterable.

          >>> median_grouped([52, 52, 53, 54])
          52.5

     In the following example, the data are rounded, so that each value
     represents the midpoint of data classes, e.g.  1 is the midpoint of
     the class 0.5–1.5, 2 is the midpoint of 1.5–2.5, 3 is the midpoint
     of 2.5–3.5, etc.  With the data given, the middle value falls
     somewhere in the class 3.5–4.5, and interpolation is used to
     estimate it:

          >>> median_grouped([1, 2, 2, 3, 4, 4, 4, 4, 4, 5])
          3.7

     Optional argument `interval' represents the class interval, and
     defaults to 1.  Changing the class interval naturally will change
     the interpolation:

          >>> median_grouped([1, 3, 3, 5, 7], interval=1)
          3.25
          >>> median_grouped([1, 3, 3, 5, 7], interval=2)
          3.5

     This function does not check whether the data points are at least
     `interval' apart.

     `CPython implementation detail:' Under some circumstances, *note
     median_grouped(): 1b29. may coerce data points to floats.  This
     behaviour is likely to change in the future.

     也參考
     ......

        * "Statistics for the Behavioral Sciences", Frederick J
          Gravetter and Larry B Wallnau (8th Edition).

        * The SSMEDIAN(1) function in the Gnome Gnumeric spreadsheet,
          including this discussion(2).

 -- 函式: statistics.mode (data)

     Return the single most common data point from discrete or nominal
     `data'.  The mode (when it exists) is the most typical value and
     serves as a measure of central location.

     If there are multiple modes with the same frequency, returns the
     first one encountered in the `data'.  If the smallest or largest of
     those is desired instead, use ‘min(multimode(data))’ or
     ‘max(multimode(data))’.  If the input `data' is empty, *note
     StatisticsError: 1b30. is raised.

     ‘mode’ assumes discrete data and returns a single value.  This is
     the standard treatment of the mode as commonly taught in schools:

          >>> mode([1, 1, 2, 3, 3, 3, 3, 4])
          3

     The mode is unique in that it is the only statistic in this package
     that also applies to nominal (non-numeric) data:

          >>> mode(["red", "blue", "blue", "red", "green", "red", "red"])
          'red'

     3.8 版更變: Now handles multimodal datasets by returning the first
     mode encountered.  Formerly, it raised *note StatisticsError: 1b30.
     when more than one mode was found.

 -- 函式: statistics.multimode (data)

     Return a list of the most frequently occurring values in the order
     they were first encountered in the `data'.  Will return more than
     one result if there are multiple modes or an empty list if the
     `data' is empty:

          >>> multimode('aabbbbccddddeeffffgg')
          ['b', 'd', 'f']
          >>> multimode('')
          []

     3.8 版新加入.

 -- 函式: statistics.pstdev (data, mu=None)

     Return the population standard deviation (the square root of the
     population variance).  See *note pvariance(): 1b2c. for arguments
     and other details.

          >>> pstdev([1.5, 2.5, 2.5, 2.75, 3.25, 4.75])
          0.986893273527251

 -- 函式: statistics.pvariance (data, mu=None)

     Return the population variance of `data', a non-empty sequence or
     iterable of real-valued numbers.  Variance, or second moment about
     the mean, is a measure of the variability (spread or dispersion) of
     data.  A large variance indicates that the data is spread out; a
     small variance indicates it is clustered closely around the mean.

     If the optional second argument `mu' is given, it is typically the
     mean of the `data'.  It can also be used to compute the second
     moment around a point that is not the mean.  If it is missing or
     ‘None’ (the default), the arithmetic mean is automatically
     calculated.

     Use this function to calculate the variance from the entire
     population.  To estimate the variance from a sample, the *note
     variance(): 1b2e. function is usually a better choice.

     Raises *note StatisticsError: 1b30. if `data' is empty.

     Examples:

          >>> data = [0.0, 0.25, 0.25, 1.25, 1.5, 1.75, 2.75, 3.25]
          >>> pvariance(data)
          1.25

     If you have already calculated the mean of your data, you can pass
     it as the optional second argument `mu' to avoid recalculation:

          >>> mu = mean(data)
          >>> pvariance(data, mu)
          1.25

     Decimals and Fractions are supported:

          >>> 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)

          備註: When called with the entire population, this gives the
          population variance σ².  When called on a sample instead, this
          is the biased sample variance s², also known as variance with
          N degrees of freedom.

          If you somehow know the true population mean μ, you may use
          this function to calculate the variance of a sample, giving
          the known population mean as the second argument.  Provided
          the data points are a random sample of the population, the
          result will be an unbiased estimate of the population
          variance.

 -- 函式: statistics.stdev (data, xbar=None)

     Return the sample standard deviation (the square root of the sample
     variance).  See *note variance(): 1b2e. for arguments and other
     details.

          >>> stdev([1.5, 2.5, 2.5, 2.75, 3.25, 4.75])
          1.0810874155219827

 -- 函式: statistics.variance (data, xbar=None)

     Return the sample variance of `data', an iterable of at least two
     real-valued numbers.  Variance, or second moment about the mean, is
     a measure of the variability (spread or dispersion) of data.  A
     large variance indicates that the data is spread out; a small
     variance indicates it is clustered closely around the mean.

     If the optional second argument `xbar' is given, it should be the
     mean of `data'.  If it is missing or ‘None’ (the default), the mean
     is automatically calculated.

     Use this function when your data is a sample from a population.  To
     calculate the variance from the entire population, see *note
     pvariance(): 1b2c.

     Raises *note StatisticsError: 1b30. if `data' has fewer than two
     values.

     Examples:

          >>> data = [2.75, 1.75, 1.25, 0.25, 0.5, 1.25, 3.5]
          >>> variance(data)
          1.3720238095238095

     If you have already calculated the mean of your data, you can pass
     it as the optional second argument `xbar' to avoid recalculation:

          >>> m = mean(data)
          >>> variance(data, m)
          1.3720238095238095

     This function does not attempt to verify that you have passed the
     actual mean as `xbar'.  Using arbitrary values for `xbar' can lead
     to invalid or impossible results.

     Decimal and Fraction values are supported:

          >>> 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)

          備註: This is the sample variance s² with Bessel’s correction,
          also known as variance with N-1 degrees of freedom.  Provided
          that the data points are representative (e.g.  independent and
          identically distributed), the result should be an unbiased
          estimate of the true population variance.

          If you somehow know the actual population mean μ you should
          pass it to the *note pvariance(): 1b2c. function as the `mu'
          parameter to get the variance of a sample.

 -- 函式: statistics.quantiles (data, *, n=4, method='exclusive')

     Divide `data' into `n' continuous intervals with equal probability.
     Returns a list of ‘n - 1’ cut points separating the intervals.

     Set `n' to 4 for quartiles (the default).  Set `n' to 10 for
     deciles.  Set `n' to 100 for percentiles which gives the 99 cuts
     points that separate `data' into 100 equal sized groups.  Raises
     *note StatisticsError: 1b30. if `n' is not least 1.

     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: 1b30. if there are
     not at least two data points.

     The cut points are linearly interpolated from the two nearest data
     points.  For example, if a cut point falls one-third of the
     distance between two sample values, ‘100’ and ‘112’, the cut-point
     will evaluate to ‘104’.

     The `method' for computing quantiles can be varied depending on
     whether the `data' includes or excludes the lowest and highest
     possible values from the population.

     The default `method' is "exclusive" and is used for data sampled
     from a population that can have more extreme values than found in
     the samples.  The portion of the population falling below the
     `i-th' of `m' sorted data points is computed as ‘i / (m + 1)’.
     Given nine sample values, the method sorts them and assigns the
     following percentiles: 10%, 20%, 30%, 40%, 50%, 60%, 70%, 80%, 90%.

     Setting the `method' to "inclusive" is used for describing
     population data or for samples that are known to include the most
     extreme values from the population.  The minimum value in `data' is
     treated as the 0th percentile and the maximum value is treated as
     the 100th percentile.  The portion of the population falling below
     the `i-th' of `m' sorted data points is computed as ‘(i - 1) / (m -
     1)’.  Given 11 sample values, the method sorts them and assigns the
     following percentiles: 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 版新加入.

   ---------- Footnotes ----------

   (1) 
https://help.gnome.org/users/gnumeric/stable/gnumeric.html#gnumeric-function-SSMEDIAN

   (2) 
https://mail.gnome.org/archives/gnumeric-list/2011-April/msg00018.html


File: python.info,  Node: Exceptions<2>,  Next: NormalDist objects,  Prev: 函式細節,  Up: statistics --- 數學統計函式

5.9.7.4 Exceptions
..................

A single exception is defined:

 -- 例外: statistics.StatisticsError

     Subclass of *note ValueError: 1fc. for statistics-related
     exceptions.


File: python.info,  Node: NormalDist objects,  Prev: Exceptions<2>,  Up: statistics --- 數學統計函式

5.9.7.5 ‘NormalDist’ objects
............................

*note NormalDist: 22c. is a tool for creating and manipulating normal
distributions of a random variable(1).  It is a class that treats the
mean and standard deviation of data measurements as a single entity.

Normal distributions arise from the Central Limit Theorem(2) and have a
wide range of applications in statistics.

 -- 類別: statistics.NormalDist (mu=0.0, sigma=1.0)

     Returns a new `NormalDist' object where `mu' represents the
     arithmetic mean(3) and `sigma' represents the standard
     deviation(4).

     If `sigma' is negative, raises *note StatisticsError: 1b30.

      -- 屬性: mean

          A read-only property for the arithmetic mean(5) of a normal
          distribution.

      -- 屬性: median

          A read-only property for the median(6) of a normal
          distribution.

      -- 屬性: mode

          A read-only property for the mode(7) of a normal distribution.

      -- 屬性: stdev

          A read-only property for the standard deviation(8) of a normal
          distribution.

      -- 屬性: variance

          A read-only property for the variance(9) of a normal
          distribution.  Equal to the square of the standard deviation.

      -- 成員函式: classmethod from_samples (data)

          Makes a normal distribution instance with `mu' and `sigma'
          parameters estimated from the `data' using *note fmean(): 228.
          and *note stdev(): 1b2d.

          The `data' can be any *note iterable: bb1. and should consist
          of values that can be converted to type *note float: 188.  If
          `data' does not contain at least two elements, raises *note
          StatisticsError: 1b30. because it takes at least one point to
          estimate a central value and at least two points to estimate
          dispersion.

      -- 成員函式: samples (n, *, seed=None)

          Generates `n' random samples for a given mean and standard
          deviation.  Returns a *note list: 263. of *note float: 188.
          values.

          If `seed' is given, creates a new instance of the underlying
          random number generator.  This is useful for creating
          reproducible results, even in a multi-threading context.

      -- 成員函式: pdf (x)

          Using a probability density function (pdf)(10), compute the
          relative likelihood that a random variable `X' will be near
          the given value `x'.  Mathematically, it is the limit of the
          ratio ‘P(x <= X < x+dx) / dx’ as `dx' approaches zero.

          The relative likelihood is computed as the probability of a
          sample occurring in a narrow range divided by the width of the
          range (hence the word "density").  Since the likelihood is
          relative to other points, its value can be greater than ‘1.0’.

      -- 成員函式: cdf (x)

          Using a cumulative distribution function (cdf)(11), compute
          the probability that a random variable `X' will be less than
          or equal to `x'.  Mathematically, it is written ‘P(X <= x)’.

      -- 成員函式: inv_cdf (p)

          Compute the inverse cumulative distribution function, also
          known as the quantile function(12) or the percent-point(13)
          function.  Mathematically, it is written ‘x : P(X <= x) = p’.

          Finds the value `x' of the random variable `X' such that the
          probability of the variable being less than or equal to that
          value equals the given probability `p'.

      -- 成員函式: overlap (other)

          Measures the agreement between two normal probability
          distributions.  Returns a value between 0.0 and 1.0 giving the
          overlapping area for the two probability density
          functions(14).

      -- 成員函式: quantiles (n=4)

          Divide the normal distribution into `n' continuous intervals
          with equal probability.  Returns a list of (n - 1) cut points
          separating the intervals.

          Set `n' to 4 for quartiles (the default).  Set `n' to 10 for
          deciles.  Set `n' to 100 for percentiles which gives the 99
          cuts points that separate the normal distribution into 100
          equal sized groups.

     Instances of *note NormalDist: 22c. support addition, subtraction,
     multiplication and division by a constant.  These operations are
     used for translation and scaling.  For example:

          >>> temperature_february = NormalDist(5, 2.5)             # Celsius
          >>> temperature_february * (9/5) + 32                     # Fahrenheit
          NormalDist(mu=41.0, sigma=4.5)

     Dividing a constant by an instance of *note NormalDist: 22c. is not
     supported because the result wouldn’t be normally distributed.

     Since normal distributions arise from additive effects of
     independent variables, it is possible to add and subtract two
     independent normally distributed random variables(15) represented
     as instances of *note NormalDist: 22c.  For example:

          >>> 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 版新加入.

* Menu:

* NormalDist Examples and Recipes::

   ---------- 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://www.statisticshowto.datasciencecentral.com/inverse-distribution-function/

   (14) https://www.rasch.org/rmt/rmt101r.htm

   (15) 
https://en.wikipedia.org/wiki/Sum_of_normally_distributed_random_variables


File: python.info,  Node: NormalDist Examples and Recipes,  Up: NormalDist objects

5.9.7.6 ‘NormalDist’ Examples and Recipes
.........................................

*note NormalDist: 22c. readily solves classic probability problems.

For example, given historical data for SAT exams(1) showing that scores
are normally distributed with a mean of 1060 and a standard deviation of
195, determine the percentage of students with test scores between 1100
and 1200, after rounding to the nearest whole number:

     >>> sat = NormalDist(1060, 195)
     >>> fraction = sat.cdf(1200 + 0.5) - sat.cdf(1100 - 0.5)
     >>> round(fraction * 100.0, 1)
     18.4

Find the quartiles(2) and deciles(3) for the SAT scores:

     >>> list(map(round, sat.quantiles()))
     [928, 1060, 1192]
     >>> list(map(round, sat.quantiles(n=10)))
     [810, 896, 958, 1011, 1060, 1109, 1162, 1224, 1310]

To estimate the distribution for a model than isn’t easy to solve
analytically, *note NormalDist: 22c. can generate input samples for a
Monte Carlo simulation(4):

     >>> 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]

Normal distributions can be used to approximate Binomial
distributions(5) when the sample size is large and when the probability
of a successful trial is near 50%.

For example, an open source conference has 750 attendees and two rooms
with a 500 person capacity.  There is a talk about Python and another
about Ruby.  In previous conferences, 65% of the attendees preferred to
listen to Python talks.  Assuming the population preferences haven’t
changed, what is the probability that the Python room will stay within
its capacity limits?

     >>> 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

     >>> # 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, choices
     >>> seed(8675309)
     >>> def trial():
     ...     return choices(('Python', 'Ruby'), (p, q), k=n).count('Python')
     >>> mean(trial() <= k for i in range(10_000))
     0.8398

Normal distributions commonly arise in machine learning problems.

Wikipedia has a nice example of a Naive Bayesian Classifier(6).  The
challenge is to predict a person’s gender from measurements of normally
distributed features including height, weight, and foot size.

We’re given a training dataset with measurements for eight people.  The
measurements are assumed to be normally distributed, so we summarize the
data with *note NormalDist: 22c.:

     >>> 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])

Next, we encounter a new person whose feature measurements are known but
whose gender is unknown:

     >>> ht = 6.0        # height
     >>> wt = 130        # weight
     >>> fs = 8          # foot size

Starting with a 50% prior probability(7) of being male or female, we
compute the posterior as the prior times the product of likelihoods for
the feature measurements given the gender:

     >>> 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))

The final prediction goes to the largest posterior.  This is known as
the maximum a posteriori(8) or MAP:

     >>> 'male' if posterior_male > posterior_female else 'female'
     'female'

   ---------- 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

   (4) https://en.wikipedia.org/wiki/Monte_Carlo_method

   (5) http://mathworld.wolfram.com/BinomialDistribution.html

   (6) 
https://en.wikipedia.org/wiki/Naive_Bayes_classifier#Sex_classification

   (7) https://en.wikipedia.org/wiki/Prior_probability

   (8) 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.

The following modules are documented in this chapter:

* Menu:

* itertools: itertools --- Functions creating iterators for efficient looping. Functions creating iterators for efficient looping
* functools: functools --- Higher-order functions and operations on callable objects. Higher-order functions and operations on callable
                        objects
* operator: operator --- Standard operators as functions. Standard operators as functions


File: python.info,  Node: itertools --- Functions creating iterators for efficient looping,  Next: functools --- Higher-order functions and operations on callable objects,  Up: 函式編程模組

5.10.1 ‘itertools’ — Functions creating iterators for efficient looping
-----------------------------------------------------------------------

__________________________________________________________________

This module implements a number of *note iterator: 1040. building blocks
inspired by constructs from APL, Haskell, and SML. Each has been recast
in a form suitable for Python.

The module standardizes a core set of fast, memory efficient tools that
are useful by themselves or in combination.  Together, they form an
"iterator algebra" making it possible to construct specialized tools
succinctly and efficiently in pure Python.

For instance, SML provides a tabulation tool: ‘tabulate(f)’ which
produces a sequence ‘f(0), f(1), ...’.  The same effect can be achieved
in Python by combining *note map(): c32. and *note count(): c20. to form
‘map(f, count())’.

These tools and their built-in counterparts also work well with the
high-speed functions in the *note operator: c3. module.  For example,
the multiplication operator can be mapped across two vectors to form an
efficient dot-product: ‘sum(map(operator.mul, vector1, vector2))’.

`Infinite iterators:'

Iterator               Arguments             Results                                               Example
                                                                                                   
-------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                                   
*note count(): c20.    start, [step]         start, start+step, start+2*step, ...                  ‘count(10) --> 10 11 12 13 14 ...’
                                                                                                   
                                                                                                   
*note cycle(): 1b44.   p                     p0, p1, ...  plast, p0, p1, ...                       ‘cycle('ABCD') --> A B C D A B C D ...’
                                                                                                   
                                                                                                   
*note repeat(): 10b7.  elem [,n]             elem, elem, elem, ...  endlessly or up to n times     ‘repeat(10, 3) --> 10 10 10’
                                                                                                   

`Iterators terminating on the shortest input sequence:'

Iterator                         Arguments                        Results                                               Example
                                                                                                                        
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                                                        
*note accumulate(): 1de.         p [,func]                        p0, p0+p1, p0+p1+p2, ...                              ‘accumulate([1,2,3,4,5]) --> 1 3 6 10 15’
                                                                                                                        
                                                                                                                        
*note chain(): 1608.             p, q, ...                        p0, p1, ...  plast, q0, q1, ...                       ‘chain('ABC', 'DEF') --> A B C D E F’
                                                                                                                        
                                                                                                                        
*note chain.from_iterable(): 1b45.iterable                        p0, p1, ...  plast, q0, q1, ...                       ‘chain.from_iterable(['ABC', 'DEF']) --> A B C D E F’
                                                                                                                        
                                                                                                                        
*note compress(): c1f.           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(): 1b46.         pred, seq                        seq[n], seq[n+1], starting when pred fails            ‘dropwhile(lambda x: x<5, [1,4,6,4,1]) --> 6 4 1’
                                                                                                                        
                                                                                                                        
*note filterfalse(): 15f1.       pred, seq                        elements of seq where pred(elem) is false             ‘filterfalse(lambda x: x%2, range(10)) --> 0 2 4 6 8’
                                                                                                                        
                                                                                                                        
*note groupby(): 1b47.           iterable[, key]                  sub-iterators grouped by value of key(v)
                                                                  
                                                                                                                        
*note islice(): 3a7.             seq, [start,] stop [, step]      elements from seq[start:stop:step]                    ‘islice('ABCDEFG', 2, None) --> C D E F G’
                                                                                                                        
                                                                                                                        
*note starmap(): a2d.            func, seq                        func(*seq[0]), func(*seq[1]), ...                     ‘starmap(pow, [(2,5), (3,2), (10,3)]) --> 32 9 1000’
                                                                                                                        
                                                                                                                        
*note takewhile(): 1b48.         pred, seq                        seq[0], seq[1], until pred fails                      ‘takewhile(lambda x: x<5, [1,4,6,4,1]) --> 1 4’
                                                                                                                        
                                                                                                                        
*note tee(): 1b49.               it, n                            it1, it2, ...  itn splits one iterator into n
                                                                  
                                                                                                                        
*note zip_longest(): c36.        p, q, ...                        (p[0], q[0]), (p[1], q[1]), ...                       ‘zip_longest('ABCD', 'xy', fillvalue='-') --> Ax By C- D-’
                                                                                                                        

`Combinatoric iterators:'

Iterator                                           Arguments                Results
                                                                            
----------------------------------------------------------------------------------------------------------------------------------------------
                                                                            
*note product(): cac.                              p, q, ...  [repeat=1]    cartesian product, equivalent to a nested for-loop
                                                                            
                                                                            
*note permutations(): ece.                         p[, r]                   r-length tuples, all possible orderings, no repeated elements
                                                                            
                                                                            
*note combinations(): cab.                         p, r                     r-length tuples, in sorted order, no repeated elements
                                                                            
                                                                            
*note combinations_with_replacement(): c1e.        p, r                     r-length tuples, in sorted order, with repeated elements
                                                                            

Examples                                           Results
                                                   
---------------------------------------------------------------------------------------------------------------------
                                                   
‘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 functions::
* Itertools Recipes::


File: python.info,  Node: Itertool functions,  Next: Itertools Recipes,  Up: itertools --- Functions creating iterators for efficient looping

5.10.1.1 Itertool functions
...........................

The following module functions all construct and return iterators.  Some
provide streams of infinite length, so they should only be accessed by
functions or loops that truncate the stream.

 -- 函式: itertools.accumulate (iterable[, func, *, initial=None])

     Make an iterator that returns accumulated sums, or accumulated
     results of other binary functions (specified via the optional
     `func' argument).

     If `func' is supplied, it should be a function of two arguments.
     Elements of the input `iterable' may be any type that can be
     accepted as arguments to `func'.  (For example, with the default
     operation of addition, elements may be any addable type including
     *note Decimal: 189. or *note Fraction: 186.)

     Usually, the number of elements output matches the input iterable.
     However, if the keyword argument `initial' is provided, the
     accumulation leads off with the `initial' value so that the output
     has one more element than the input iterable.

     Roughly equivalent to:

          def accumulate(iterable, func=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
              it = iter(iterable)
              total = initial
              if initial is None:
                  try:
                      total = next(it)
                  except StopIteration:
                      return
              yield total
              for element in it:
                  total = func(total, element)
                  yield total

     There are a number of uses for the `func' argument.  It can be set
     to *note min(): 80e. for a running minimum, *note max(): 80f. for a
     running maximum, or *note operator.mul(): 1b4c. for a running
     product.  Amortization tables can be built by accumulating interest
     and applying payments.  First-order recurrence relations(1) can be
     modeled by supplying the initial value in the iterable and using
     only the accumulated total in `func' argument:

          >>> data = [3, 4, 6, 2, 1, 9, 0, 7, 5, 8]
          >>> list(accumulate(data, operator.mul))     # running product
          [3, 12, 72, 144, 144, 1296, 0, 0, 0, 0]
          >>> list(accumulate(data, max))              # running maximum
          [3, 4, 6, 6, 6, 9, 9, 9, 9, 9]

          # Amortize a 5% loan of 1000 with 4 annual payments of 90
          >>> cashflows = [1000, -90, -90, -90, -90]
          >>> list(accumulate(cashflows, lambda bal, pmt: bal*1.05 + pmt))
          [1000, 960.0, 918.0, 873.9000000000001, 827.5950000000001]

          # Chaotic recurrence relation https://en.wikipedia.org/wiki/Logistic_map
          >>> logistic_map = lambda x, _:  r * x * (1 - x)
          >>> r = 3.8
          >>> x0 = 0.4
          >>> inputs = repeat(x0, 36)     # only the initial value is used
          >>> [format(x, '.2f') for x in accumulate(inputs, logistic_map)]
          ['0.40', '0.91', '0.30', '0.81', '0.60', '0.92', '0.29', '0.79', '0.63',
           '0.88', '0.39', '0.90', '0.33', '0.84', '0.52', '0.95', '0.18', '0.57',
           '0.93', '0.25', '0.71', '0.79', '0.63', '0.88', '0.39', '0.91', '0.32',
           '0.83', '0.54', '0.95', '0.20', '0.60', '0.91', '0.30', '0.80', '0.60']

     See *note functools.reduce(): c74. for a similar function that
     returns only the final accumulated value.

     3.2 版新加入.

     3.3 版更變: Added the optional `func' parameter.

     3.8 版更變: Added the optional `initial' parameter.

 -- 函式: itertools.chain (*iterables)

     Make an iterator that returns elements from the first iterable
     until it is exhausted, then proceeds to the next iterable, until
     all of the iterables are exhausted.  Used for treating consecutive
     sequences as a single sequence.  Roughly equivalent to:

          def chain(*iterables):
              # chain('ABC', 'DEF') --> A B C D E F
              for it in iterables:
                  for element in it:
                      yield element

 -- 成員函式: classmethod chain.from_iterable (iterable)

     Alternate constructor for *note chain(): 1608.  Gets chained inputs
     from a single iterable argument that is evaluated lazily.  Roughly
     equivalent to:

          def from_iterable(iterables):
              # chain.from_iterable(['ABC', 'DEF']) --> A B C D E F
              for it in iterables:
                  for element in it:
                      yield element

 -- 函式: itertools.combinations (iterable, r)

     Return `r' length subsequences of elements from the input
     `iterable'.

     The combination tuples are emitted in lexicographic ordering
     according to the order of the input `iterable'.  So, if the input
     `iterable' is sorted, the combination tuples will be produced in
     sorted order.

     Elements are treated as unique based on their position, not on
     their value.  So if the input elements are unique, there will be no
     repeat values in each combination.

     Roughly equivalent to:

          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)

     The code for *note combinations(): cab. can be also expressed as a
     subsequence of *note permutations(): ece. after filtering entries
     where the elements are not in sorted order (according to their
     position in the input pool):

          def combinations(iterable, r):
              pool = tuple(iterable)
              n = len(pool)
              for indices in permutations(range(n), r):
                  if sorted(indices) == list(indices):
                      yield tuple(pool[i] for i in indices)

     The number of items returned is ‘n! / r! / (n-r)!’ when ‘0 <= r <=
     n’ or zero when ‘r > n’.

 -- 函式: itertools.combinations_with_replacement (iterable, r)

     Return `r' length subsequences of elements from the input
     `iterable' allowing individual elements to be repeated more than
     once.

     The combination tuples are emitted in lexicographic ordering
     according to the order of the input `iterable'.  So, if the input
     `iterable' is sorted, the combination tuples will be produced in
     sorted order.

     Elements are treated as unique based on their position, not on
     their value.  So if the input elements are unique, the generated
     combinations will also be unique.

     Roughly equivalent to:

          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)

     The code for *note combinations_with_replacement(): c1e. can be
     also expressed as a subsequence of *note product(): cac. after
     filtering entries where the elements are not in sorted order
     (according to their position in the input pool):

          def combinations_with_replacement(iterable, r):
              pool = tuple(iterable)
              n = len(pool)
              for indices in product(range(n), repeat=r):
                  if sorted(indices) == list(indices):
                      yield tuple(pool[i] for i in indices)

     The number of items returned is ‘(n+r-1)! / r! / (n-1)!’ when ‘n >
     0’.

     3.1 版新加入.

 -- 函式: itertools.compress (data, selectors)

     Make an iterator that filters elements from `data' returning only
     those that have a corresponding element in `selectors' that
     evaluates to ‘True’.  Stops when either the `data' or `selectors'
     iterables has been exhausted.  Roughly equivalent to:

          def compress(data, selectors):
              # compress('ABCDEF', [1,0,1,0,1,1]) --> A C E F
              return (d for d, s in zip(data, selectors) if s)

     3.1 版新加入.

 -- 函式: itertools.count (start=0, step=1)

     Make an iterator that returns evenly spaced values starting with
     number `start'.  Often used as an argument to *note map(): c32. to
     generate consecutive data points.  Also, used with *note zip():
     c37. to add sequence numbers.  Roughly equivalent to:

          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

     When counting with floating point numbers, better accuracy can
     sometimes be achieved by substituting multiplicative code such as:
     ‘(start + step * i for i in count())’.

     3.1 版更變: Added `step' argument and allowed non-integer
     arguments.

 -- 函式: itertools.cycle (iterable)

     Make an iterator returning elements from the iterable and saving a
     copy of each.  When the iterable is exhausted, return elements from
     the saved copy.  Repeats indefinitely.  Roughly equivalent to:

          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

     Note, this member of the toolkit may require significant auxiliary
     storage (depending on the length of the iterable).

 -- 函式: itertools.dropwhile (predicate, iterable)

     Make an iterator that drops elements from the iterable as long as
     the predicate is true; afterwards, returns every element.  Note,
     the iterator does not produce `any' output until the predicate
     first becomes false, so it may have a lengthy start-up time.
     Roughly equivalent to:

          def dropwhile(predicate, iterable):
              # dropwhile(lambda x: x<5, [1,4,6,4,1]) --> 6 4 1
              iterable = iter(iterable)
              for x in iterable:
                  if not predicate(x):
                      yield x
                      break
              for x in iterable:
                  yield x

 -- 函式: itertools.filterfalse (predicate, iterable)

     Make an iterator that filters elements from iterable returning only
     those for which the predicate is ‘False’.  If `predicate' is
     ‘None’, return the items that are false.  Roughly equivalent to:

          def filterfalse(predicate, iterable):
              # filterfalse(lambda x: x%2, range(10)) --> 0 2 4 6 8
              if predicate is None:
                  predicate = bool
              for x in iterable:
                  if not predicate(x):
                      yield x

 -- 函式: itertools.groupby (iterable, key=None)

     Make an iterator that returns consecutive keys and groups from the
     `iterable'.  The `key' is a function computing a key value for each
     element.  If not specified or is ‘None’, `key' defaults to an
     identity function and returns the element unchanged.  Generally,
     the iterable needs to already be sorted on the same key function.

     The operation of *note groupby(): 1b47. is similar to the ‘uniq’
     filter in Unix.  It generates a break or new group every time the
     value of the key function changes (which is why it is usually
     necessary to have sorted the data using the same key function).
     That behavior differs from SQL’s GROUP BY which aggregates common
     elements regardless of their input order.

     The returned group is itself an iterator that shares the underlying
     iterable with *note groupby(): 1b47.  Because the source is shared,
     when the *note groupby(): 1b47. object is advanced, the previous
     group is no longer visible.  So, if that data is needed later, it
     should be stored as a list:

          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(): 1b47. is roughly equivalent to:

          class groupby:
              # [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
              def __init__(self, iterable, key=None):
                  if key is None:
                      key = lambda x: x
                  self.keyfunc = key
                  self.it = iter(iterable)
                  self.tgtkey = self.currkey = self.currvalue = object()
              def __iter__(self):
                  return self
              def __next__(self):
                  self.id = object()
                  while self.currkey == self.tgtkey:
                      self.currvalue = next(self.it)    # Exit on StopIteration
                      self.currkey = self.keyfunc(self.currvalue)
                  self.tgtkey = self.currkey
                  return (self.currkey, self._grouper(self.tgtkey, self.id))
              def _grouper(self, tgtkey, id):
                  while self.id is id and self.currkey == tgtkey:
                      yield self.currvalue
                      try:
                          self.currvalue = next(self.it)
                      except StopIteration:
                          return
                      self.currkey = self.keyfunc(self.currvalue)

 -- 函式: itertools.islice (iterable, stop)

 -- 函式: itertools.islice (iterable, start, stop[, step])

     Make an iterator that returns selected elements from the iterable.
     If `start' is non-zero, then elements from the iterable are skipped
     until start is reached.  Afterward, elements are returned
     consecutively unless `step' is set higher than one which results in
     items being skipped.  If `stop' is ‘None’, then iteration continues
     until the iterator is exhausted, if at all; otherwise, it stops at
     the specified position.  Unlike regular slicing, *note islice():
     3a7. does not support negative values for `start', `stop', or
     `step'.  Can be used to extract related fields from data where the
     internal structure has been flattened (for example, a multi-line
     report may list a name field on every third line).  Roughly
     equivalent to:

          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, stop, step = s.start or 0, s.stop or sys.maxsize, s.step or 1
              it = iter(range(start, stop, step))
              try:
                  nexti = next(it)
              except StopIteration:
                  # Consume *iterable* up to the *start* position.
                  for i, element in zip(range(start), iterable):
                      pass
                  return
              try:
                  for i, element in enumerate(iterable):
                      if i == nexti:
                          yield element
                          nexti = next(it)
              except StopIteration:
                  # Consume to *stop*.
                  for i, element in zip(range(i + 1, stop), iterable):
                      pass

     If `start' is ‘None’, then iteration starts at zero.  If `step' is
     ‘None’, then the step defaults to one.

 -- 函式: itertools.permutations (iterable, r=None)

     Return successive `r' length permutations of elements in the
     `iterable'.

     If `r' is not specified or is ‘None’, then `r' defaults to the
     length of the `iterable' and all possible full-length permutations
     are generated.

     The permutation tuples are emitted in lexicographic ordering
     according to the order of the input `iterable'.  So, if the input
     `iterable' is sorted, the combination tuples will be produced in
     sorted order.

     Elements are treated as unique based on their position, not on
     their value.  So if the input elements are unique, there will be no
     repeat values in each permutation.

     Roughly equivalent to:

          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

     The code for *note permutations(): ece. can be also expressed as a
     subsequence of *note product(): cac, filtered to exclude entries
     with repeated elements (those from the same position in the input
     pool):

          def permutations(iterable, r=None):
              pool = tuple(iterable)
              n = len(pool)
              r = n if r is None else r
              for indices in product(range(n), repeat=r):
                  if len(set(indices)) == r:
                      yield tuple(pool[i] for i in indices)

     The number of items returned is ‘n! / (n-r)!’ when ‘0 <= r <= n’ or
     zero when ‘r > n’.

 -- 函式: itertools.product (*iterables, repeat=1)

     Cartesian product of input iterables.

     Roughly equivalent to nested for-loops in a generator expression.
     For example, ‘product(A, B)’ returns the same as ‘((x,y) for x in A
     for y in B)’.

     The nested loops cycle like an odometer with the rightmost element
     advancing on every iteration.  This pattern creates a lexicographic
     ordering so that if the input’s iterables are sorted, the product
     tuples are emitted in sorted order.

     To compute the product of an iterable with itself, specify the
     number of repetitions with the optional `repeat' keyword argument.
     For example, ‘product(A, repeat=4)’ means the same as ‘product(A,
     A, A, A)’.

     This function is roughly equivalent to the following code, except
     that the actual implementation does not build up intermediate
     results in memory:

          def product(*args, 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 args] * repeat
              result = [[]]
              for pool in pools:
                  result = [x+[y] for x in result for y in pool]
              for prod in result:
                  yield tuple(prod)

 -- 函式: itertools.repeat (object[, times])

     Make an iterator that returns `object' over and over again.  Runs
     indefinitely unless the `times' argument is specified.  Used as
     argument to *note map(): c32. for invariant parameters to the
     called function.  Also used with *note zip(): c37. to create an
     invariant part of a tuple record.

     Roughly equivalent to:

          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

     A common use for `repeat' is to supply a stream of constant values
     to `map' or `zip':

          >>> list(map(pow, range(10), repeat(2)))
          [0, 1, 4, 9, 16, 25, 36, 49, 64, 81]

 -- 函式: itertools.starmap (function, iterable)

     Make an iterator that computes the function using arguments
     obtained from the iterable.  Used instead of *note map(): c32. when
     argument parameters are already grouped in tuples from a single
     iterable (the data has been "pre-zipped").  The difference between
     *note map(): c32. and *note starmap(): a2d. parallels the
     distinction between ‘function(a,b)’ and ‘function(*c)’.  Roughly
     equivalent to:

          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)

     Make an iterator that returns elements from the iterable as long as
     the predicate is true.  Roughly equivalent to:

          def takewhile(predicate, iterable):
              # takewhile(lambda x: x<5, [1,4,6,4,1]) --> 1 4
              for x in iterable:
                  if predicate(x):
                      yield x
                  else:
                      break

 -- 函式: itertools.tee (iterable, n=2)

     Return `n' independent iterators from a single iterable.

     The following Python code helps explain what `tee' does (although
     the actual implementation is more complex and uses only a single
     underlying FIFO queue).

     Roughly equivalent to:

          def tee(iterable, n=2):
              it = iter(iterable)
              deques = [collections.deque() for i in range(n)]
              def gen(mydeque):
                  while True:
                      if not mydeque:             # when the local deque is empty
                          try:
                              newval = next(it)   # fetch a new value and
                          except StopIteration:
                              return
                          for d in deques:        # load it to all the deques
                              d.append(newval)
                      yield mydeque.popleft()
              return tuple(gen(d) for d in deques)

     Once *note tee(): 1b49. has made a split, the original `iterable'
     should not be used anywhere else; otherwise, the `iterable' could
     get advanced without the tee objects being informed.

     ‘tee’ iterators are not threadsafe.  A *note RuntimeError: 2bb. may
     be raised when using simultaneously iterators returned by the same
     *note tee(): 1b49. call, even if the original `iterable' is
     threadsafe.

     This itertool may require significant auxiliary storage (depending
     on how much temporary data needs to be stored).  In general, if one
     iterator uses most or all of the data before another iterator
     starts, it is faster to use *note list(): 263. instead of *note
     tee(): 1b49.

 -- 函式: itertools.zip_longest (*iterables, fillvalue=None)

     Make an iterator that aggregates elements from each of the
     iterables.  If the iterables are of uneven length, missing values
     are filled-in with `fillvalue'.  Iteration continues until the
     longest iterable is exhausted.  Roughly equivalent to:

          def zip_longest(*args, fillvalue=None):
              # zip_longest('ABCD', 'xy', fillvalue='-') --> Ax By C- D-
              iterators = [iter(it) for it in args]
              num_active = len(iterators)
              if not num_active:
                  return
              while True:
                  values = []
                  for i, it in enumerate(iterators):
                      try:
                          value = next(it)
                      except StopIteration:
                          num_active -= 1
                          if not num_active:
                              return
                          iterators[i] = repeat(fillvalue)
                          value = fillvalue
                      values.append(value)
                  yield tuple(values)

     If one of the iterables is potentially infinite, then the *note
     zip_longest(): c36. function should be wrapped with something that
     limits the number of calls (for example *note islice(): 3a7. or
     *note takewhile(): 1b48.).  If not specified, `fillvalue' defaults
     to ‘None’.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Recurrence_relation


File: python.info,  Node: Itertools Recipes,  Prev: Itertool functions,  Up: itertools --- Functions creating iterators for efficient looping

5.10.1.2 Itertools Recipes
..........................

This section shows recipes for creating an extended toolset using the
existing itertools as building blocks.

Substantially all of these recipes and many, many others can be
installed from the more-itertools project(1) found on the Python Package
Index:

     pip install more-itertools

The extended tools offer the same high performance as the underlying
toolset.  The superior memory performance is kept by processing elements
one at a time rather than bringing the whole iterable into memory all at
once.  Code volume is kept small by linking the tools together in a
functional style which helps eliminate temporary variables.  High speed
is retained by preferring "vectorized" building blocks over the use of
for-loops and *note generator: 9a7.s which incur interpreter overhead.

     def take(n, iterable):
         "Return first n items of the iterable as a list"
         return list(islice(iterable, n))

     def prepend(value, iterator):
         "Prepend a single value in front of an iterator"
         # prepend(1, [2, 3, 4]) -> 1 2 3 4
         return chain([value], iterator)

     def tabulate(function, start=0):
         "Return function(0), function(1), ..."
         return map(function, count(start))

     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:
             # feed the entire iterator into a zero-length deque
             collections.deque(iterator, maxlen=0)
         else:
             # advance to the empty slice starting at position n
             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 all_equal(iterable):
         "Returns True if all the elements are equal to each other"
         g = groupby(iterable)
         return next(g, True) and not next(g, False)

     def quantify(iterable, pred=bool):
         "Count how many times the predicate is true"
         return sum(map(pred, iterable))

     def padnone(iterable):
         """Returns the sequence elements and then returns None indefinitely.

         Useful for emulating the behavior of the built-in map() function.
         """
         return chain(iterable, repeat(None))

     def ncycles(iterable, n):
         "Returns the sequence elements n times"
         return chain.from_iterable(repeat(tuple(iterable), n))

     def dotproduct(vec1, vec2):
         return sum(map(operator.mul, vec1, vec2))

     def flatten(list_of_lists):
         "Flatten one level of nesting"
         return chain.from_iterable(list_of_lists)

     def repeatfunc(func, times=None, *args):
         """Repeat calls to func with specified arguments.

         Example:  repeatfunc(random.random)
         """
         if times is None:
             return starmap(func, repeat(args))
         return starmap(func, repeat(args, times))

     def pairwise(iterable):
         "s -> (s0,s1), (s1,s2), (s2, s3), ..."
         a, b = tee(iterable)
         next(b, None)
         return zip(a, b)

     def grouper(iterable, n, fillvalue=None):
         "Collect data into fixed-length chunks or blocks"
         # grouper('ABCDEFG', 3, 'x') --> ABC DEF Gxx"
         args = [iter(iterable)] * n
         return zip_longest(*args, fillvalue=fillvalue)

     def roundrobin(*iterables):
         "roundrobin('ABC', 'D', 'EF') --> A D E B F C"
         # Recipe credited to George Sakkis
         num_active = len(iterables)
         nexts = cycle(iter(it).__next__ for it in iterables)
         while num_active:
             try:
                 for next in nexts:
                     yield next()
             except StopIteration:
                 # Remove the iterator we just exhausted from the cycle.
                 num_active -= 1
                 nexts = cycle(islice(nexts, num_active))

     def partition(pred, iterable):
         'Use a predicate to partition entries into false entries and true entries'
         # partition(is_odd, range(10)) --> 0 2 4 6 8   and  1 3 5 7 9
         t1, t2 = tee(iterable)
         return filterfalse(pred, t1), filter(pred, t2)

     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 unique_everseen(iterable, key=None):
         "List unique elements, preserving order. Remember all elements ever seen."
         # unique_everseen('AAAABBBCCDAABBB') --> A B C D
         # unique_everseen('ABBCcAD', str.lower) --> A B C D
         seen = set()
         seen_add = seen.add
         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_justseen(iterable, key=None):
         "List unique elements, preserving order. Remember only the element just seen."
         # unique_justseen('AAAABBBCCDAABBB') --> A B C D A B
         # unique_justseen('ABBCcAD', str.lower) --> A B C A D
         return map(next, map(operator.itemgetter(1), groupby(iterable, key)))

     def iter_except(func, exception, first=None):
         """ Call a function repeatedly until an exception is raised.

         Converts a call-until-exception interface to an iterator interface.
         Like builtins.iter(func, sentinel) but uses an exception instead
         of a sentinel to end the loop.

         Examples:
             iter_except(functools.partial(heappop, h), IndexError)   # priority queue iterator
             iter_except(d.popitem, KeyError)                         # non-blocking dict iterator
             iter_except(d.popleft, IndexError)                       # non-blocking deque iterator
             iter_except(q.get_nowait, Queue.Empty)                   # loop over a producer Queue
             iter_except(s.pop, KeyError)                             # non-blocking set iterator

         """
         try:
             if first is not None:
                 yield first()            # For database APIs needing an initial cast to db.first()
             while True:
                 yield func()
         except exception:
             pass

     def first_true(iterable, default=False, pred=None):
         """Returns the first true value in the iterable.

         If no true value is found, returns *default*

         If *pred* is not None, returns the first item
         for which pred(item) is true.

         """
         # 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(pred, iterable), default)

     def random_product(*args, repeat=1):
         "Random selection from itertools.product(*args, **kwds)"
         pools = [tuple(pool) for pool in args] * repeat
         return tuple(random.choice(pool) for pool in 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):
         "Random selection from itertools.combinations_with_replacement(iterable, r)"
         pool = tuple(iterable)
         n = len(pool)
         indices = sorted(random.randrange(n) for i in range(r))
         return tuple(pool[i] for i in indices)

     def nth_combination(iterable, r, index):
         'Equivalent to list(combinations(iterable, r))[index]'
         pool = tuple(iterable)
         n = len(pool)
         if r < 0 or r > n:
             raise ValueError
         c = 1
         k = min(r, n-r)
         for i in range(1, k+1):
             c = c * (n - k + i) // i
         if index < 0:
             index += c
         if index < 0 or index >= c:
             raise IndexError
         result = []
         while r:
             c, n, r = c*r//n, n-1, r-1
             while index >= c:
                 index -= c
                 c, n = c*(n-r)//n, n-1
             result.append(pool[-1-n])
         return tuple(result)

   ---------- Footnotes ----------

   (1) https://pypi.org/project/more-itertools/


File: python.info,  Node: functools --- Higher-order functions and operations on callable objects,  Next: operator --- Standard operators as functions,  Prev: itertools --- Functions creating iterators for efficient looping,  Up: 函式編程模組

5.10.2 ‘functools’ — Higher-order functions and operations on callable objects
------------------------------------------------------------------------------

`Source code:' Lib/functools.py(1)

__________________________________________________________________

The *note functools: 85. module is for higher-order functions: functions
that act on or return other functions.  In general, any callable object
can be treated as a function for the purposes of this module.

The *note functools: 85. module defines the following functions:

 -- 函式: @functools.cached_property (func)

     Transform a method of a class into a property whose value is
     computed once and then cached as a normal attribute for the life of
     the instance.  Similar to *note property(): 1d8, with the addition
     of caching.  Useful for expensive computed properties of instances
     that are otherwise effectively immutable.

     Example:

          class DataSet:
              def __init__(self, sequence_of_numbers):
                  self._data = sequence_of_numbers

              @cached_property
              def stdev(self):
                  return statistics.stdev(self._data)

              @cached_property
              def variance(self):
                  return statistics.variance(self._data)

     3.8 版新加入.

          備註: This decorator requires that the ‘__dict__’ attribute on
          each instance be a mutable mapping.  This means it will not
          work with some types, such as metaclasses (since the
          ‘__dict__’ attributes on type instances are read-only proxies
          for the class namespace), and those that specify ‘__slots__’
          without including ‘__dict__’ as one of the defined slots (as
          such classes don’t provide a ‘__dict__’ attribute at all).

 -- 函式: functools.cmp_to_key (func)

     Transform an old-style comparison function to a *note key function:
     6e5.  Used with tools that accept key functions (such as *note
     sorted(): 449, *note min(): 80e, *note max(): 80f, *note
     heapq.nlargest(): 1968, *note heapq.nsmallest(): 1969, *note
     itertools.groupby(): 1b47.).  This function is primarily used as a
     transition tool for programs being converted from Python 2 which
     supported the use of comparison functions.

     A comparison function is any callable that accept two arguments,
     compares them, and returns a negative number for less-than, zero
     for equality, or a positive number for greater-than.  A key
     function is a callable that accepts one argument and returns
     another value to be used as the sort key.

     Example:

          sorted(iterable, key=cmp_to_key(locale.strcoll))  # locale-aware sort order

     For sorting examples and a brief sorting tutorial, see *note
     如何排序: 1606.

     3.2 版新加入.

 -- 函式: @functools.lru_cache (user_function)

 -- 函式: @functools.lru_cache (maxsize=128, typed=False)

     Decorator to wrap a function with a memoizing callable that saves
     up to the `maxsize' most recent calls.  It can save time when an
     expensive or I/O bound function is periodically called with the
     same arguments.

     Since a dictionary is used to cache results, the positional and
     keyword arguments to the function must be hashable.

     Distinct argument patterns may be considered to be distinct calls
     with separate cache entries.  For example, ‘f(a=1, b=2)’ and
     ‘f(b=2, a=1)’ differ in their keyword argument order and may have
     two separate cache entries.

     If `user_function' is specified, it must be a callable.  This
     allows the `lru_cache' decorator to be applied directly to a user
     function, leaving the `maxsize' at its default value of 128:

          @lru_cache
          def count_vowels(sentence):
              sentence = sentence.casefold()
              return sum(sentence.count(vowel) for vowel in 'aeiou')

     If `maxsize' is set to ‘None’, the LRU feature is disabled and the
     cache can grow without bound.

     If `typed' is set to true, function arguments of different types
     will be cached separately.  For example, ‘f(3)’ and ‘f(3.0)’ will
     be treated as distinct calls with distinct results.

     To help measure the effectiveness of the cache and tune the
     `maxsize' parameter, the wrapped function is instrumented with a
     ‘cache_info()’ function that returns a *note named tuple: aa8.
     showing `hits', `misses', `maxsize' and `currsize'.  In a
     multi-threaded environment, the hits and misses are approximate.

     The decorator also provides a ‘cache_clear()’ function for clearing
     or invalidating the cache.

     The original underlying function is accessible through the
     ‘__wrapped__’ attribute.  This is useful for introspection, for
     bypassing the cache, or for rewrapping the function with a
     different cache.

     An LRU (least recently used) cache(2) works best when the most
     recent calls are the best predictors of upcoming calls (for
     example, the most popular articles on a news server tend to change
     each day).  The cache’s size limit assures that the cache does not
     grow without bound on long-running processes such as web servers.

     In general, the LRU cache should only be used when you want to
     reuse previously computed values.  Accordingly, it doesn’t make
     sense to cache functions with side-effects, functions that need to
     create distinct mutable objects on each call, or impure functions
     such as time() or random().

     Example of an LRU cache for static web content:

          @lru_cache(maxsize=32)
          def get_pep(num):
              'Retrieve text of a Python Enhancement Proposal'
              resource = 'http://www.python.org/dev/peps/pep-%04d/' % num
              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)

     Example of efficiently computing Fibonacci numbers(3) using a cache
     to implement a dynamic programming(4) technique:

          @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 版更變: Added the `typed' option.

     3.8 版更變: Added the `user_function' option.

 -- 函式: @functools.total_ordering

     Given a class defining one or more rich comparison ordering
     methods, this class decorator supplies the rest.  This simplifies
     the effort involved in specifying all of the possible rich
     comparison operations:

     The class must define one of *note __lt__(): c39, *note __le__():
     ca5, *note __gt__(): ca6, or *note __ge__(): ca7.  In addition, the
     class should supply an *note __eq__(): 344. method.

     For example:

          @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()))

          備註: While this decorator makes it easy to create well
          behaved totally ordered types, it `does' come at the cost of
          slower execution and more complex stack traces for the derived
          comparison methods.  If performance benchmarking indicates
          this is a bottleneck for a given application, implementing all
          six rich comparison methods instead is likely to provide an
          easy speed boost.

     3.2 版新加入.

     3.4 版更變: Returning NotImplemented from the underlying comparison
     function for unrecognised types is now supported.

 -- 函式: functools.partial (func, /, *args, **keywords)

     Return a new *note partial object: 1b50. which when called will
     behave like `func' called with the positional arguments `args' and
     keyword arguments `keywords'.  If more arguments are supplied to
     the call, they are appended to `args'.  If additional keyword
     arguments are supplied, they extend and override `keywords'.
     Roughly equivalent to:

          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

     The *note partial(): 7cd. is used for partial function application
     which "freezes" some portion of a function’s arguments and/or
     keywords resulting in a new object with a simplified signature.
     For example, *note partial(): 7cd. can be used to create a callable
     that behaves like the *note int(): 185. function where the `base'
     argument defaults to two:

          >>> 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)

     Return a new *note partialmethod: 29d. descriptor which behaves
     like *note partial: 7cd. except that it is designed to be used as a
     method definition rather than being directly callable.

     `func' must be a *note descriptor: 160b. or a callable (objects
     which are both, like normal functions, are handled as descriptors).

     When `func' is a descriptor (such as a normal Python function,
     *note classmethod(): 1d9, *note staticmethod(): 1da,
     ‘abstractmethod()’ or another instance of *note partialmethod:
     29d.), calls to ‘__get__’ are delegated to the underlying
     descriptor, and an appropriate *note partial object: 1b50. returned
     as the result.

     When `func' is a non-descriptor callable, an appropriate bound
     method is created dynamically.  This behaves like a normal Python
     function when used as a method: the `self' argument will be
     inserted as the first positional argument, even before the `args'
     and `keywords' supplied to the *note partialmethod: 29d.
     constructor.

     Example:

          >>> class Cell(object):
          ...     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[, initializer])

     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 `initializer' 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 `initializer' is not given and `iterable' contains only one
     item, the first item is returned.

     Roughly equivalent to:

          def reduce(function, iterable, initializer=None):
              it = iter(iterable)
              if initializer is None:
                  value = next(it)
              else:
                  value = initializer
              for element in it:
                  value = function(value, element)
              return value

     See *note itertools.accumulate(): 1de. for an iterator that yields
     all intermediate values.

 -- 函式: @functools.singledispatch

     Transform a function into a *note single-dispatch: 1cc. *note
     generic function: 1cb.

     To define a generic function, decorate it with the
     ‘@singledispatch’ decorator.  Note that the dispatch happens on the
     type of the first argument, create your function accordingly:

          >>> from functools import singledispatch
          >>> @singledispatch
          ... def fun(arg, verbose=False):
          ...     if verbose:
          ...         print("Let me just say,", end=" ")
          ...     print(arg)

     To add overloaded implementations to the function, use the
     ‘register()’ attribute of the generic function.  It is a decorator.
     For functions annotated with types, the decorator will infer the
     type of the first argument automatically:

          >>> @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)

     For code which doesn’t use type annotations, the appropriate type
     argument can be passed explicitly to the decorator itself:

          >>> @fun.register(complex)
          ... def _(arg, verbose=False):
          ...     if verbose:
          ...         print("Better than complicated.", end=" ")
          ...     print(arg.real, arg.imag)
          ...

     To enable registering lambdas and pre-existing functions, the
     ‘register()’ attribute can be used in a functional form:

          >>> def nothing(arg, verbose=False):
          ...     print("Nothing.")
          ...
          >>> fun.register(type(None), nothing)

     The ‘register()’ attribute returns the undecorated function which
     enables decorator stacking, pickling, as well as creating unit
     tests for each variant independently:

          >>> @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

     When called, the generic function dispatches on the type of the
     first argument:

          >>> 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

     Where there is no registered implementation for a specific type,
     its method resolution order is used to find a more generic
     implementation.  The original function decorated with
     ‘@singledispatch’ is registered for the base ‘object’ type, which
     means it is used if no better implementation is found.

     To check which implementation will the generic function choose for
     a given type, use the ‘dispatch()’ attribute:

          >>> fun.dispatch(float)
          <function fun_num at 0x1035a2840>
          >>> fun.dispatch(dict)    # note: default implementation
          <function fun at 0x103fe0000>

     To access all registered implementations, use the read-only
     ‘registry’ attribute:

          >>> 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 版更變: The ‘register()’ attribute supports using type
     annotations.

 -- 類別: functools.singledispatchmethod (func)

     Transform a method into a *note single-dispatch: 1cc. *note generic
     function: 1cb.

     To define a generic method, decorate it with the
     ‘@singledispatchmethod’ decorator.  Note that the dispatch happens
     on the type of the first non-self or non-cls argument, create your
     function accordingly:

          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’ supports nesting with other decorators such
     as ‘@classmethod’.  Note that to allow for ‘dispatcher.register’,
     ‘singledispatchmethod’ must be the `outer most' decorator.  Here is
     the ‘Negator’ class with the ‘neg’ methods being class bound:

          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

     The same pattern can be used for other similar decorators:
     ‘staticmethod’, ‘abstractmethod’, and others.

     3.8 版新加入.

 -- 函式: functools.update_wrapper (wrapper, wrapped,
          assigned=WRAPPER_ASSIGNMENTS, updated=WRAPPER_UPDATES)

     Update a `wrapper' function to look like the `wrapped' function.
     The optional arguments are tuples to specify which attributes of
     the original function are assigned directly to the matching
     attributes on the wrapper function and which attributes of the
     wrapper function are updated with the corresponding attributes from
     the original function.  The default values for these arguments are
     the module level constants ‘WRAPPER_ASSIGNMENTS’ (which assigns to
     the wrapper function’s ‘__module__’, ‘__name__’, ‘__qualname__’,
     ‘__annotations__’ and ‘__doc__’, the documentation string) and
     ‘WRAPPER_UPDATES’ (which updates the wrapper function’s ‘__dict__’,
     i.e.  the instance dictionary).

     To allow access to the original function for introspection and
     other purposes (e.g.  bypassing a caching decorator such as *note
     lru_cache(): 1c8.), this function automatically adds a
     ‘__wrapped__’ attribute to the wrapper that refers to the function
     being wrapped.

     The main intended use for this function is in *note decorator: 284.
     functions which wrap the decorated function and return the wrapper.
     If the wrapper function is not updated, the metadata of the
     returned function will reflect the wrapper definition rather than
     the original function definition, which is typically less than
     helpful.

     *note update_wrapper(): 95f. may be used with callables other than
     functions.  Any attributes named in `assigned' or `updated' that
     are missing from the object being wrapped are ignored (i.e.  this
     function will not attempt to set them on the wrapper function).
     *note AttributeError: 3a0. is still raised if the wrapper function
     itself is missing any attributes named in `updated'.

     3.2 版新加入: Automatic addition of the ‘__wrapped__’ attribute.

     3.2 版新加入: Copying of the ‘__annotations__’ attribute by
     default.

     3.2 版更變: Missing attributes no longer trigger an *note
     AttributeError: 3a0.

     3.4 版更變: The ‘__wrapped__’ attribute now always refers to the
     wrapped function, even if that function defined a ‘__wrapped__’
     attribute.  (see bpo-17482(5))

 -- 函式: @functools.wraps (wrapped, assigned=WRAPPER_ASSIGNMENTS,
          updated=WRAPPER_UPDATES)

     This is a convenience function for invoking *note update_wrapper():
     95f. as a function decorator when defining a wrapper function.  It
     is equivalent to ‘partial(update_wrapper, wrapped=wrapped,
     assigned=assigned, updated=updated)’.  For example:

          >>> 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'

     Without the use of this decorator factory, the name of the example
     function would have been ‘'wrapper'’, and the docstring of the
     original ‘example()’ would have been lost.

* Menu:

* partial Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/functools.py

   (2) https://en.wikipedia.org/wiki/Cache_algorithms#Examples

   (3) https://en.wikipedia.org/wiki/Fibonacci_number

   (4) https://en.wikipedia.org/wiki/Dynamic_programming

   (5) https://bugs.python.org/issue17482


File: python.info,  Node: partial Objects,  Up: functools --- Higher-order functions and operations on callable objects

5.10.2.1 ‘partial’ Objects
..........................

*note partial: 7cd. objects are callable objects created by *note
partial(): 7cd.  They have three read-only attributes:

 -- 屬性: partial.func

     A callable object or function.  Calls to the *note partial: 7cd.
     object will be forwarded to *note func: 1b52. with new arguments
     and keywords.

 -- 屬性: partial.args

     The leftmost positional arguments that will be prepended to the
     positional arguments provided to a *note partial: 7cd. object call.

 -- 屬性: partial.keywords

     The keyword arguments that will be supplied when the *note partial:
     7cd. object is called.

*note partial: 7cd. objects are like ‘function’ objects in that they are
callable, weak referencable, and can have attributes.  There are some
important differences.  For instance, the *note __name__: c6c. and
‘__doc__’ attributes are not created automatically.  Also, *note
partial: 7cd. objects defined in classes behave like static methods and
do not transform into bound methods during instance attribute look-up.


File: python.info,  Node: operator --- Standard operators as functions,  Prev: functools --- Higher-order functions and operations on callable objects,  Up: 函式編程模組

5.10.3 ‘operator’ — Standard operators as functions
---------------------------------------------------

`Source code:' Lib/operator.py(1)

__________________________________________________________________

The *note operator: c3. module exports a set of efficient functions
corresponding to the intrinsic operators of Python.  For example,
‘operator.add(x, y)’ is equivalent to the expression ‘x+y’.  Many
function names are those used for special methods, without the double
underscores.  For backward compatibility, many of these have a variant
with the double underscores kept.  The variants without the double
underscores are preferred for clarity.

The functions fall into categories that perform object comparisons,
logical operations, mathematical operations and sequence operations.

The object comparison functions are useful for all objects, and are
named after the rich comparison operators they support:

 -- 函式: 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)

     Perform "rich comparisons" between `a' and `b'.  Specifically,
     ‘lt(a, b)’ is equivalent to ‘a < b’, ‘le(a, b)’ is equivalent to ‘a
     <= b’, ‘eq(a, b)’ is equivalent to ‘a == b’, ‘ne(a, b)’ is
     equivalent to ‘a != b’, ‘gt(a, b)’ is equivalent to ‘a > b’ and
     ‘ge(a, b)’ is equivalent to ‘a >= b’.  Note that these functions
     can return any value, which may or may not be interpretable as a
     Boolean value.  See *note Comparisons: 1546. for more information
     about rich comparisons.

The logical operations are also generally applicable to all objects, and
support truth tests, identity tests, and boolean operations:

 -- 函式: operator.not_ (obj)
 -- 函式: operator.__not__ (obj)

     Return the outcome of *note not: 1552. `obj'.  (Note that there is
     no *note __not__(): 1b64. method for object instances; only the
     interpreter core defines this operation.  The result is affected by
     the *note __bool__(): c6d. and *note __len__(): dd0. methods.)

 -- 函式: operator.truth (obj)

     Return *note True: 49e. if `obj' is true, and *note False: 38d.
     otherwise.  This is equivalent to using the *note bool: 184.
     constructor.

 -- 函式: operator.is_ (a, b)

     Return ‘a is b’.  Tests object identity.

 -- 函式: operator.is_not (a, b)

     Return ‘a is not b’.  Tests object identity.

The mathematical and bitwise operations are the most numerous:

 -- 函式: operator.abs (obj)
 -- 函式: operator.__abs__ (obj)

     Return the absolute value of `obj'.

 -- 函式: operator.add (a, b)
 -- 函式: operator.__add__ (a, b)

     Return ‘a + b’, for `a' and `b' numbers.

 -- 函式: operator.and_ (a, b)
 -- 函式: operator.__and__ (a, b)

     Return the bitwise and of `a' and `b'.

 -- 函式: operator.floordiv (a, b)
 -- 函式: operator.__floordiv__ (a, b)

     Return ‘a // b’.

 -- 函式: operator.index (a)
 -- 函式: operator.__index__ (a)

     Return `a' converted to an integer.  Equivalent to ‘a.__index__()’.

 -- 函式: operator.inv (obj)
 -- 函式: operator.invert (obj)
 -- 函式: operator.__inv__ (obj)
 -- 函式: operator.__invert__ (obj)

     Return the bitwise inverse of the number `obj'.  This is equivalent
     to ‘~obj’.

 -- 函式: operator.lshift (a, b)
 -- 函式: operator.__lshift__ (a, b)

     Return `a' shifted left by `b'.

 -- 函式: operator.mod (a, b)
 -- 函式: operator.__mod__ (a, b)

     Return ‘a % b’.

 -- 函式: operator.mul (a, b)
 -- 函式: operator.__mul__ (a, b)

     Return ‘a * b’, for `a' and `b' numbers.

 -- 函式: operator.matmul (a, b)
 -- 函式: operator.__matmul__ (a, b)

     Return ‘a @ b’.

     3.5 版新加入.

 -- 函式: operator.neg (obj)
 -- 函式: operator.__neg__ (obj)

     Return `obj' negated (‘-obj’).

 -- 函式: operator.or_ (a, b)
 -- 函式: operator.__or__ (a, b)

     Return the bitwise or of `a' and `b'.

 -- 函式: operator.pos (obj)
 -- 函式: operator.__pos__ (obj)

     Return `obj' positive (‘+obj’).

 -- 函式: operator.pow (a, b)
 -- 函式: operator.__pow__ (a, b)

     Return ‘a ** b’, for `a' and `b' numbers.

 -- 函式: operator.rshift (a, b)
 -- 函式: operator.__rshift__ (a, b)

     Return `a' shifted right by `b'.

 -- 函式: operator.sub (a, b)
 -- 函式: operator.__sub__ (a, b)

     Return ‘a - b’.

 -- 函式: operator.truediv (a, b)
 -- 函式: operator.__truediv__ (a, b)

     Return ‘a / b’ where 2/3 is .66 rather than 0.  This is also known
     as "true" division.

 -- 函式: operator.xor (a, b)
 -- 函式: operator.__xor__ (a, b)

     Return the bitwise exclusive or of `a' and `b'.

Operations which work with sequences (some of them with mappings too)
include:

 -- 函式: operator.concat (a, b)
 -- 函式: operator.__concat__ (a, b)

     Return ‘a + b’ for `a' and `b' sequences.

 -- 函式: operator.contains (a, b)
 -- 函式: operator.__contains__ (a, b)

     Return the outcome of the test ‘b in a’.  Note the reversed
     operands.

 -- 函式: operator.countOf (a, b)

     Return the number of occurrences of `b' in `a'.

 -- 函式: operator.delitem (a, b)
 -- 函式: operator.__delitem__ (a, b)

     Remove the value of `a' at index `b'.

 -- 函式: operator.getitem (a, b)
 -- 函式: operator.__getitem__ (a, b)

     Return the value of `a' at index `b'.

 -- 函式: operator.indexOf (a, b)

     Return the index of the first of occurrence of `b' in `a'.

 -- 函式: operator.setitem (a, b, c)
 -- 函式: operator.__setitem__ (a, b, c)

     Set the value of `a' at index `b' to `c'.

 -- 函式: operator.length_hint (obj, default=0)

     Return an estimated length for the object `o'.  First try to return
     its actual length, then an estimate using *note
     object.__length_hint__(): 811, and finally return the default
     value.

     3.4 版新加入.

The *note operator: c3. module also defines tools for generalized
attribute and item lookups.  These are useful for making fast field
extractors as arguments for *note map(): c32, *note sorted(): 449, *note
itertools.groupby(): 1b47, or other functions that expect a function
argument.

 -- 函式: operator.attrgetter (attr)

 -- 函式: operator.attrgetter (*attrs)

     Return a callable object that fetches `attr' from its operand.  If
     more than one attribute is requested, returns a tuple of
     attributes.  The attribute names can also contain dots.  For
     example:

        * After ‘f = attrgetter('name')’, the call ‘f(b)’ returns
          ‘b.name’.

        * After ‘f = attrgetter('name', 'date')’, the call ‘f(b)’
          returns ‘(b.name, b.date)’.

        * After ‘f = attrgetter('name.first', 'name.last')’, the call
          ‘f(b)’ returns ‘(b.name.first, b.name.last)’.

     Equivalent to:

          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)

     Return a callable object that fetches `item' from its operand using
     the operand’s *note __getitem__(): 1b91. method.  If multiple items
     are specified, returns a tuple of lookup values.  For example:

        * After ‘f = itemgetter(2)’, the call ‘f(r)’ returns ‘r[2]’.

        * After ‘g = itemgetter(2, 5, 3)’, the call ‘g(r)’ returns
          ‘(r[2], r[5], r[3])’.

     Equivalent to:

          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

     The items can be any type accepted by the operand’s *note
     __getitem__(): 1b91. method.  Dictionaries accept any hashable
     value.  Lists, tuples, and strings accept an index or a slice:

          >>> 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'

     Example of using *note itemgetter(): 262. to retrieve specific
     fields from a tuple record:

          >>> 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)

     Return a callable object that calls the method `name' on its
     operand.  If additional arguments and/or keyword arguments are
     given, they will be given to the method as well.  For example:

        * After ‘f = methodcaller('name')’, the call ‘f(b)’ returns
          ‘b.name()’.

        * After ‘f = methodcaller('name', 'foo', bar=1)’, the call
          ‘f(b)’ returns ‘b.name('foo', bar=1)’.

     Equivalent to:

          def methodcaller(name, /, *args, **kwargs):
              def caller(obj):
                  return getattr(obj, name)(*args, **kwargs)
              return caller

* Menu:

* Mapping Operators to Functions::
* In-place Operators::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/operator.py


File: python.info,  Node: Mapping Operators to Functions,  Next: In-place Operators,  Up: operator --- Standard operators as functions

5.10.3.1 Mapping Operators to Functions
.......................................

This table shows how abstract operations correspond to operator symbols
in the Python syntax and the functions in the *note operator: c3.
module.

Operation                   Syntax                        Function
                                                          
------------------------------------------------------------------------------------------------------
                                                          
Addition                    ‘a + b’                       ‘add(a, b)’
                                                          
                                                          
Concatenation               ‘seq1 + seq2’                 ‘concat(seq1, seq2)’
                                                          
                                                          
Containment Test            ‘obj in seq’                  ‘contains(seq, obj)’
                                                          
                                                          
Division                    ‘a / b’                       ‘truediv(a, b)’
                                                          
                                                          
Division                    ‘a // b’                      ‘floordiv(a, b)’
                                                          
                                                          
Bitwise And                 ‘a & b’                       ‘and_(a, b)’
                                                          
                                                          
Bitwise Exclusive Or        ‘a ^ b’                       ‘xor(a, b)’
                                                          
                                                          
Bitwise Inversion           ‘~ a’                         ‘invert(a)’
                                                          
                                                          
Bitwise Or                  ‘a | b’                       ‘or_(a, b)’
                                                          
                                                          
Exponentiation              ‘a ** b’                      ‘pow(a, b)’
                                                          
                                                          
Identity                    ‘a is b’                      ‘is_(a, b)’
                                                          
                                                          
Identity                    ‘a is not b’                  ‘is_not(a, b)’
                                                          
                                                          
Indexed Assignment          ‘obj[k] = v’                  ‘setitem(obj, k, v)’
                                                          
                                                          
Indexed Deletion            ‘del obj[k]’                  ‘delitem(obj, k)’
                                                          
                                                          
Indexing                    ‘obj[k]’                      ‘getitem(obj, k)’
                                                          
                                                          
Left Shift                  ‘a << b’                      ‘lshift(a, b)’
                                                          
                                                          
Modulo                      ‘a % b’                       ‘mod(a, b)’
                                                          
                                                          
Multiplication              ‘a * b’                       ‘mul(a, b)’
                                                          
                                                          
Matrix Multiplication       ‘a @ b’                       ‘matmul(a, b)’
                                                          
                                                          
Negation (Arithmetic)       ‘- a’                         ‘neg(a)’
                                                          
                                                          
Negation (Logical)          ‘not a’                       ‘not_(a)’
                                                          
                                                          
Positive                    ‘+ a’                         ‘pos(a)’
                                                          
                                                          
Right Shift                 ‘a >> b’                      ‘rshift(a, b)’
                                                          
                                                          
Slice Assignment            ‘seq[i:j] = values’           ‘setitem(seq, slice(i, j), values)’
                                                          
                                                          
Slice Deletion              ‘del seq[i:j]’                ‘delitem(seq, slice(i, j))’
                                                          
                                                          
Slicing                     ‘seq[i:j]’                    ‘getitem(seq, slice(i, j))’
                                                          
                                                          
String Formatting           ‘s % obj’                     ‘mod(s, obj)’
                                                          
                                                          
Subtraction                 ‘a - b’                       ‘sub(a, b)’
                                                          
                                                          
Truth Test                  ‘obj’                         ‘truth(obj)’
                                                          
                                                          
Ordering                    ‘a < b’                       ‘lt(a, b)’
                                                          
                                                          
Ordering                    ‘a <= b’                      ‘le(a, b)’
                                                          
                                                          
Equality                    ‘a == b’                      ‘eq(a, b)’
                                                          
                                                          
Difference                  ‘a != b’                      ‘ne(a, b)’
                                                          
                                                          
Ordering                    ‘a >= b’                      ‘ge(a, b)’
                                                          
                                                          
Ordering                    ‘a > b’                       ‘gt(a, b)’
                                                          


File: python.info,  Node: In-place Operators,  Prev: Mapping Operators to Functions,  Up: operator --- Standard operators as functions

5.10.3.2 In-place Operators
...........................

Many operations have an "in-place" version.  Listed below are functions
providing a more primitive access to in-place operators than the usual
syntax does; for example, the *note statement: 1b97. ‘x += y’ is
equivalent to ‘x = operator.iadd(x, y)’.  Another way to put it is to
say that ‘z = operator.iadd(x, y)’ is equivalent to the compound
statement ‘z = x; z += y’.

In those examples, note that when an in-place method is called, the
computation and assignment are performed in two separate steps.  The
in-place functions listed below only do the first step, calling the
in-place method.  The second step, assignment, is not handled.

For immutable targets such as strings, numbers, and tuples, the updated
value is computed, but not assigned back to the input variable:

     >>> a = 'hello'
     >>> iadd(a, ' world')
     'hello world'
     >>> a
     'hello'

For mutable targets such as lists and dictionaries, the in-place method
will perform the update, so no subsequent assignment is necessary:

     >>> 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)’ is equivalent to ‘a += b’.

 -- 函式: operator.iand (a, b)
 -- 函式: operator.__iand__ (a, b)

     ‘a = iand(a, b)’ is equivalent to ‘a &= b’.

 -- 函式: operator.iconcat (a, b)
 -- 函式: operator.__iconcat__ (a, b)

     ‘a = iconcat(a, b)’ is equivalent to ‘a += b’ for `a' and `b'
     sequences.

 -- 函式: operator.ifloordiv (a, b)
 -- 函式: operator.__ifloordiv__ (a, b)

     ‘a = ifloordiv(a, b)’ is equivalent to ‘a //= b’.

 -- 函式: operator.ilshift (a, b)
 -- 函式: operator.__ilshift__ (a, b)

     ‘a = ilshift(a, b)’ is equivalent to ‘a <<= b’.

 -- 函式: operator.imod (a, b)
 -- 函式: operator.__imod__ (a, b)

     ‘a = imod(a, b)’ is equivalent to ‘a %= b’.

 -- 函式: operator.imul (a, b)
 -- 函式: operator.__imul__ (a, b)

     ‘a = imul(a, b)’ is equivalent to ‘a *= b’.

 -- 函式: operator.imatmul (a, b)
 -- 函式: operator.__imatmul__ (a, b)

     ‘a = imatmul(a, b)’ is equivalent to ‘a @= b’.

     3.5 版新加入.

 -- 函式: operator.ior (a, b)
 -- 函式: operator.__ior__ (a, b)

     ‘a = ior(a, b)’ is equivalent to ‘a |= b’.

 -- 函式: operator.ipow (a, b)
 -- 函式: operator.__ipow__ (a, b)

     ‘a = ipow(a, b)’ is equivalent to ‘a **= b’.

 -- 函式: operator.irshift (a, b)
 -- 函式: operator.__irshift__ (a, b)

     ‘a = irshift(a, b)’ is equivalent to ‘a >>= b’.

 -- 函式: operator.isub (a, b)
 -- 函式: operator.__isub__ (a, b)

     ‘a = isub(a, b)’ is equivalent to ‘a -= b’.

 -- 函式: operator.itruediv (a, b)
 -- 函式: operator.__itruediv__ (a, b)

     ‘a = itruediv(a, b)’ is equivalent to ‘a /= b’.

 -- 函式: operator.ixor (a, b)
 -- 函式: operator.__ixor__ (a, b)

     ‘a = ixor(a, b)’ is equivalent to ‘a ^= b’.


File: python.info,  Node: 檔案與目錄存取,  Next: Data Persistence,  Prev: 函式編程模組,  Up: Python 標準函式庫 Standard Library

5.11 檔案與目錄存取
===================

The modules described in this chapter deal with disk files and
directories.  For example, there are modules for reading the properties
of files, manipulating paths in a portable way, and creating temporary
files.  The full list of modules in this chapter is:

* Menu:

* pathlib: pathlib --- Object-oriented filesystem paths. Object-oriented filesystem paths
* os.path: os path --- Common pathname manipulations. Common pathname manipulations
* fileinput: fileinput --- Iterate over lines from multiple input streams. Iterate over lines from multiple input streams
* stat: stat --- Interpreting stat results. Interpreting stat() results
* filecmp: filecmp --- File and Directory Comparisons. File and Directory Comparisons
* tempfile: tempfile --- Generate temporary files and directories. Generate temporary files and directories
* glob: glob --- Unix style pathname pattern expansion. Unix style pathname pattern expansion
* fnmatch: fnmatch --- Unix filename pattern matching. Unix filename pattern matching
* linecache: linecache --- Random access to text lines. Random access to text lines
* shutil: shutil --- High-level file operations. High-level file operations


File: python.info,  Node: pathlib --- Object-oriented filesystem paths,  Next: os path --- Common pathname manipulations,  Up: 檔案與目錄存取

5.11.1 ‘pathlib’ — Object-oriented filesystem paths
---------------------------------------------------

3.4 版新加入.

`Source code:' Lib/pathlib.py(1)

__________________________________________________________________

This module offers classes representing filesystem paths with semantics
appropriate for different operating systems.  Path classes are divided
between *note pure paths: 1bb8, which provide purely computational
operations without I/O, and *note concrete paths: 1bb9, which inherit
from pure paths but also provide I/O operations.

[python-figures/pathlib-inheritance]
If you’ve never used this module before or just aren’t sure which class
is right for your task, *note Path: 202. is most likely what you need.
It instantiates a *note concrete path: 1bb9. for the platform the code
is running on.

Pure paths are useful in some special cases; for example:

  1. If you want to manipulate Windows paths on a Unix machine (or vice
     versa).  You cannot instantiate a *note WindowsPath: 1bba. when
     running on Unix, but you can instantiate *note PureWindowsPath:
     1bbb.

  2. You want to make sure that your code only manipulates paths without
     actually accessing the OS. In this case, instantiating one of the
     pure classes may be useful since those simply don’t have any
     OS-accessing operations.

也參考
......

PEP 428(2): The pathlib module – object-oriented filesystem paths.

也參考
......

For low-level path manipulation on strings, you can also use the *note
os.path: c6. module.

* Menu:

* Basic use::
* Pure paths::
* Concrete paths::
* Correspondence to tools in the os module::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/pathlib.py

   (2) https://www.python.org/dev/peps/pep-0428


File: python.info,  Node: Basic use,  Next: Pure paths,  Up: pathlib --- Object-oriented filesystem paths

5.11.1.1 Basic use
..................

Importing the main class:

     >>> from pathlib import Path

Listing subdirectories:

     >>> p = Path('.')
     >>> [x for x in p.iterdir() if x.is_dir()]
     [PosixPath('.hg'), PosixPath('docs'), PosixPath('dist'),
      PosixPath('__pycache__'), PosixPath('build')]

Listing Python source files in this directory tree:

     >>> list(p.glob('**/*.py'))
     [PosixPath('test_pathlib.py'), PosixPath('setup.py'),
      PosixPath('pathlib.py'), PosixPath('docs/conf.py'),
      PosixPath('build/lib/pathlib.py')]

Navigating inside a directory tree:

     >>> p = Path('/etc')
     >>> q = p / 'init.d' / 'reboot'
     >>> q
     PosixPath('/etc/init.d/reboot')
     >>> q.resolve()
     PosixPath('/etc/rc.d/init.d/halt')

Querying path properties:

     >>> q.exists()
     True
     >>> q.is_dir()
     False

Opening a file:

     >>> with q.open() as f: f.readline()
     ...
     '#!/bin/bash\n'


File: python.info,  Node: Pure paths,  Next: Concrete paths,  Prev: Basic use,  Up: pathlib --- Object-oriented filesystem paths

5.11.1.2 Pure paths
...................

Pure path objects provide path-handling operations which don’t actually
access a filesystem.  There are three ways to access these classes,
which we also call `flavours':

 -- 類別: pathlib.PurePath (*pathsegments)

     A generic class that represents the system’s path flavour
     (instantiating it creates either a *note PurePosixPath: 1bbe. or a
     *note PureWindowsPath: 1bbb.):

          >>> PurePath('setup.py')      # Running on a Unix machine
          PurePosixPath('setup.py')

     Each element of `pathsegments' can be either a string representing
     a path segment, an object implementing the *note os.PathLike: 4f0.
     interface which returns a string, or another path object:

          >>> PurePath('foo', 'some/path', 'bar')
          PurePosixPath('foo/some/path/bar')
          >>> PurePath(Path('foo'), Path('bar'))
          PurePosixPath('foo/bar')

     When `pathsegments' is empty, the current directory is assumed:

          >>> PurePath()
          PurePosixPath('.')

     When several absolute paths are given, the last is taken as an
     anchor (mimicking *note os.path.join(): f61.’s behaviour):

          >>> PurePath('/etc', '/usr', 'lib64')
          PurePosixPath('/usr/lib64')
          >>> PureWindowsPath('c:/Windows', 'd:bar')
          PureWindowsPath('d:bar')

     However, in a Windows path, changing the local root doesn’t discard
     the previous drive setting:

          >>> PureWindowsPath('c:/Windows', '/Program Files')
          PureWindowsPath('c:/Program Files')

     Spurious slashes and single dots are collapsed, but double dots
     (‘'..'’) are not, since this would change the meaning of a path in
     the face of symbolic links:

          >>> PurePath('foo//bar')
          PurePosixPath('foo/bar')
          >>> PurePath('foo/./bar')
          PurePosixPath('foo/bar')
          >>> PurePath('foo/../bar')
          PurePosixPath('foo/../bar')

     (a naïve approach would make ‘PurePosixPath('foo/../bar')’
     equivalent to ‘PurePosixPath('bar')’, which is wrong if ‘foo’ is a
     symbolic link to another directory)

     Pure path objects implement the *note os.PathLike: 4f0. interface,
     allowing them to be used anywhere the interface is accepted.

     3.6 版更變: Added support for the *note os.PathLike: 4f0.
     interface.

 -- 類別: pathlib.PurePosixPath (*pathsegments)

     A subclass of *note PurePath: 1046, this path flavour represents
     non-Windows filesystem paths:

          >>> PurePosixPath('/etc')
          PurePosixPath('/etc')

     `pathsegments' is specified similarly to *note PurePath: 1046.

 -- 類別: pathlib.PureWindowsPath (*pathsegments)

     A subclass of *note PurePath: 1046, this path flavour represents
     Windows filesystem paths:

          >>> PureWindowsPath('c:/Program Files/')
          PureWindowsPath('c:/Program Files')

     `pathsegments' is specified similarly to *note PurePath: 1046.

Regardless of the system you’re running on, you can instantiate all of
these classes, since they don’t provide any operation that does system
calls.

* Menu:

* General properties::
* Operators: Operators<2>.
* Accessing individual parts::
* Methods and properties::


File: python.info,  Node: General properties,  Next: Operators<2>,  Up: Pure paths

5.11.1.3 General properties
...........................

Paths are immutable and hashable.  Paths of a same flavour are
comparable and orderable.  These properties respect the flavour’s
case-folding semantics:

     >>> PurePosixPath('foo') == PurePosixPath('FOO')
     False
     >>> PureWindowsPath('foo') == PureWindowsPath('FOO')
     True
     >>> PureWindowsPath('FOO') in { PureWindowsPath('foo') }
     True
     >>> PureWindowsPath('C:') < PureWindowsPath('d:')
     True

Paths of a different flavour compare unequal and cannot be ordered:

     >>> 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: Operators<2>,  Next: Accessing individual parts,  Prev: General properties,  Up: Pure paths

5.11.1.4 Operators
..................

The slash operator helps create child paths, similarly to *note
os.path.join(): f61.:

     >>> p = PurePath('/etc')
     >>> p
     PurePosixPath('/etc')
     >>> p / 'init.d' / 'apache2'
     PurePosixPath('/etc/init.d/apache2')
     >>> q = PurePath('bin')
     >>> '/usr' / q
     PurePosixPath('/usr/bin')

A path object can be used anywhere an object implementing *note
os.PathLike: 4f0. is accepted:

     >>> import os
     >>> p = PurePath('/etc')
     >>> os.fspath(p)
     '/etc'

The string representation of a path is the raw filesystem path itself
(in native form, e.g.  with backslashes under Windows), which you can
pass to any function taking a file path as a string:

     >>> p = PurePath('/etc')
     >>> str(p)
     '/etc'
     >>> p = PureWindowsPath('c:/Program Files')
     >>> str(p)
     'c:\\Program Files'

Similarly, calling *note bytes: 336. on a path gives the raw filesystem
path as a bytes object, as encoded by *note os.fsencode(): 4f4.:

     >>> bytes(p)
     b'/etc'

     備註: Calling *note bytes: 336. is only recommended under Unix.
     Under Windows, the unicode form is the canonical representation of
     filesystem paths.


File: python.info,  Node: Accessing individual parts,  Next: Methods and properties,  Prev: Operators<2>,  Up: Pure paths

5.11.1.5 Accessing individual parts
...................................

To access the individual "parts" (components) of a path, use the
following property:

 -- Data: PurePath.parts

     A tuple giving access to the path’s various components:

          >>> p = PurePath('/usr/bin/python3')
          >>> p.parts
          ('/', 'usr', 'bin', 'python3')

          >>> p = PureWindowsPath('c:/Program Files/PSF')
          >>> p.parts
          ('c:\\', 'Program Files', 'PSF')

     (note how the drive and local root are regrouped in a single part)


File: python.info,  Node: Methods and properties,  Prev: Accessing individual parts,  Up: Pure paths

5.11.1.6 Methods and properties
...............................

Pure paths provide the following methods and properties:

 -- Data: PurePath.drive

     A string representing the drive letter or name, if any:

          >>> PureWindowsPath('c:/Program Files/').drive
          'c:'
          >>> PureWindowsPath('/Program Files/').drive
          ''
          >>> PurePosixPath('/etc').drive
          ''

     UNC shares are also considered drives:

          >>> PureWindowsPath('//host/share/foo.txt').drive
          '\\\\host\\share'

 -- Data: PurePath.root

     A string representing the (local or global) root, if any:

          >>> PureWindowsPath('c:/Program Files/').root
          '\\'
          >>> PureWindowsPath('c:Program Files/').root
          ''
          >>> PurePosixPath('/etc').root
          '/'

     UNC shares always have a root:

          >>> PureWindowsPath('//host/share').root
          '\\'

 -- Data: PurePath.anchor

     The concatenation of the drive and root:

          >>> PureWindowsPath('c:/Program Files/').anchor
          'c:\\'
          >>> PureWindowsPath('c:Program Files/').anchor
          'c:'
          >>> PurePosixPath('/etc').anchor
          '/'
          >>> PureWindowsPath('//host/share').anchor
          '\\\\host\\share\\'

 -- Data: PurePath.parents

     An immutable sequence providing access to the logical ancestors of
     the path:

          >>> 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:/')

 -- Data: PurePath.parent

     The logical parent of the path:

          >>> p = PurePosixPath('/a/b/c/d')
          >>> p.parent
          PurePosixPath('/a/b/c')

     You cannot go past an anchor, or empty path:

          >>> p = PurePosixPath('/')
          >>> p.parent
          PurePosixPath('/')
          >>> p = PurePosixPath('.')
          >>> p.parent
          PurePosixPath('.')

          備註: This is a purely lexical operation, hence the following
          behaviour:

               >>> p = PurePosixPath('foo/..')
               >>> p.parent
               PurePosixPath('foo')

          If you want to walk an arbitrary filesystem path upwards, it
          is recommended to first call *note Path.resolve(): 1bc9. so as
          to resolve symlinks and eliminate ‘".."’ components.

 -- Data: PurePath.name

     A string representing the final path component, excluding the drive
     and root, if any:

          >>> PurePosixPath('my/library/setup.py').name
          'setup.py'

     UNC drive names are not considered:

          >>> PureWindowsPath('//some/share/setup.py').name
          'setup.py'
          >>> PureWindowsPath('//some/share').name
          ''

 -- Data: PurePath.suffix

     The file extension of the final component, if any:

          >>> PurePosixPath('my/library/setup.py').suffix
          '.py'
          >>> PurePosixPath('my/library.tar.gz').suffix
          '.gz'
          >>> PurePosixPath('my/library').suffix
          ''

 -- Data: PurePath.suffixes

     A list of the path’s file extensions:

          >>> PurePosixPath('my/library.tar.gar').suffixes
          ['.tar', '.gar']
          >>> PurePosixPath('my/library.tar.gz').suffixes
          ['.tar', '.gz']
          >>> PurePosixPath('my/library').suffixes
          []

 -- Data: PurePath.stem

     The final path component, without its suffix:

          >>> PurePosixPath('my/library.tar.gz').stem
          'library.tar'
          >>> PurePosixPath('my/library.tar').stem
          'library'
          >>> PurePosixPath('my/library').stem
          'library'

 -- 成員函式: PurePath.as_posix ()

     Return a string representation of the path with forward slashes
     (‘/’):

          >>> p = PureWindowsPath('c:\\windows')
          >>> str(p)
          'c:\\windows'
          >>> p.as_posix()
          'c:/windows'

 -- 成員函式: PurePath.as_uri ()

     Represent the path as a ‘file’ URI. *note ValueError: 1fc. is
     raised if the path isn’t absolute.

          >>> p = PurePosixPath('/etc/passwd')
          >>> p.as_uri()
          'file:///etc/passwd'
          >>> p = PureWindowsPath('c:/Windows')
          >>> p.as_uri()
          'file:///c:/Windows'

 -- 成員函式: PurePath.is_absolute ()

     Return whether the path is absolute or not.  A path is considered
     absolute if it has both a root and (if the flavour allows) a drive:

          >>> 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_reserved ()

     With *note PureWindowsPath: 1bbb, return ‘True’ if the path is
     considered reserved under Windows, ‘False’ otherwise.  With *note
     PurePosixPath: 1bbe, ‘False’ is always returned.

          >>> PureWindowsPath('nul').is_reserved()
          True
          >>> PurePosixPath('nul').is_reserved()
          False

     File system calls on reserved paths can fail mysteriously or have
     unintended effects.

 -- 成員函式: PurePath.joinpath (*other)

     Calling this method is equivalent to combining the path with each
     of the `other' arguments in turn:

          >>> 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.match (pattern)

     Match this path against the provided glob-style pattern.  Return
     ‘True’ if matching is successful, ‘False’ otherwise.

     If `pattern' is relative, the path can be either relative or
     absolute, and 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

     If `pattern' is absolute, the path must be absolute, and the whole
     path must match:

          >>> PurePath('/a.py').match('/*.py')
          True
          >>> PurePath('a/b.py').match('/*.py')
          False

     As with other methods, case-sensitivity follows platform defaults:

          >>> PurePosixPath('b.py').match('*.PY')
          False
          >>> PureWindowsPath('b.py').match('*.PY')
          True

 -- 成員函式: PurePath.relative_to (*other)

     Compute a version of this path relative to the path represented by
     `other'.  If it’s impossible, ValueError is raised:

          >>> 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 694, in relative_to
              .format(str(self), str(formatted)))
          ValueError: '/etc/passwd' does not start with '/usr'

 -- 成員函式: PurePath.with_name (name)

     Return a new path with the *note name: 1bca. changed.  If the
     original path doesn’t have a name, ValueError is raised:

          >>> 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_suffix (suffix)

     Return a new path with the *note suffix: 1bcb. changed.  If the
     original path doesn’t have a suffix, the new `suffix' is appended
     instead.  If the `suffix' is an empty string, the original suffix
     is removed:

          >>> 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')


File: python.info,  Node: Concrete paths,  Next: Correspondence to tools in the os module,  Prev: Pure paths,  Up: pathlib --- Object-oriented filesystem paths

5.11.1.7 Concrete paths
.......................

Concrete paths are subclasses of the pure path classes.  In addition to
operations provided by the latter, they also provide methods to do
system calls on path objects.  There are three ways to instantiate
concrete paths:

 -- 類別: pathlib.Path (*pathsegments)

     A subclass of *note PurePath: 1046, this class represents concrete
     paths of the system’s path flavour (instantiating it creates either
     a *note PosixPath: 1bd7. or a *note WindowsPath: 1bba.):

          >>> Path('setup.py')
          PosixPath('setup.py')

     `pathsegments' is specified similarly to *note PurePath: 1046.

 -- 類別: pathlib.PosixPath (*pathsegments)

     A subclass of *note Path: 202. and *note PurePosixPath: 1bbe, this
     class represents concrete non-Windows filesystem paths:

          >>> PosixPath('/etc')
          PosixPath('/etc')

     `pathsegments' is specified similarly to *note PurePath: 1046.

 -- 類別: pathlib.WindowsPath (*pathsegments)

     A subclass of *note Path: 202. and *note PureWindowsPath: 1bbb,
     this class represents concrete Windows filesystem paths:

          >>> WindowsPath('c:/Program Files/')
          WindowsPath('c:/Program Files')

     `pathsegments' is specified similarly to *note PurePath: 1046.

You can only instantiate the class flavour that corresponds to your
system (allowing system calls on non-compatible path flavours could lead
to bugs or failures in your application):

     >>> 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__,))
     NotImplementedError: cannot instantiate 'WindowsPath' on your system

* Menu:

* Methods: Methods<2>.


File: python.info,  Node: Methods<2>,  Up: Concrete paths

5.11.1.8 Methods
................

Concrete paths provide the following methods in addition to pure paths
methods.  Many of these methods can raise an *note OSError: 1d4. if a
system call fails (for example because the path doesn’t exist).

3.8 版更變: *note exists(): 203, *note is_dir(): 204, *note is_file():
205, *note is_mount(): 206, *note is_symlink(): 207, *note
is_block_device(): 208, *note is_char_device(): 209, *note is_fifo():
20a, *note is_socket(): 20b. now return ‘False’ instead of raising an
exception for paths that contain characters unrepresentable at the OS
level.

 -- 成員函式: classmethod Path.cwd ()

     Return a new path object representing the current directory (as
     returned by *note os.getcwd(): fe3.):

          >>> Path.cwd()
          PosixPath('/home/antoine/pathlib')

 -- 成員函式: classmethod Path.home ()

     Return a new path object representing the user’s home directory (as
     returned by *note os.path.expanduser(): 1ff. with ‘~’ construct):

          >>> Path.home()
          PosixPath('/home/antoine')

     3.5 版新加入.

 -- 成員函式: Path.stat ()

     Return a *note os.stat_result: 108f. object containing information
     about this path, like *note os.stat(): 1f2.  The result is looked
     up at each call to this method.

          >>> p = Path('setup.py')
          >>> p.stat().st_size
          956
          >>> p.stat().st_mtime
          1327883547.852554

 -- 成員函式: Path.chmod (mode)

     Change the file mode and permissions, like *note os.chmod(): a38.:

          >>> p = Path('setup.py')
          >>> p.stat().st_mode
          33277
          >>> p.chmod(0o444)
          >>> p.stat().st_mode
          33060

 -- 成員函式: Path.exists ()

     Whether the path points to an existing file or directory:

          >>> Path('.').exists()
          True
          >>> Path('setup.py').exists()
          True
          >>> Path('/etc').exists()
          True
          >>> Path('nonexistentfile').exists()
          False

          備註: If the path points to a symlink, *note exists(): 203.
          returns whether the symlink `points to' an existing file or
          directory.

 -- 成員函式: Path.expanduser ()

     Return a new path with expanded ‘~’ and ‘~user’ constructs, as
     returned by *note os.path.expanduser(): 1ff.:

          >>> p = PosixPath('~/films/Monty Python')
          >>> p.expanduser()
          PosixPath('/home/eric/films/Monty Python')

     3.5 版新加入.

 -- 成員函式: Path.glob (pattern)

     Glob the given relative `pattern' in the directory represented by
     this path, yielding all matching files (of any kind):

          >>> sorted(Path('.').glob('*.py'))
          [PosixPath('pathlib.py'), PosixPath('setup.py'), PosixPath('test_pathlib.py')]
          >>> sorted(Path('.').glob('*/*.py'))
          [PosixPath('docs/conf.py')]

     The "‘**’" pattern means "this directory and all subdirectories,
     recursively".  In other words, it enables recursive globbing:

          >>> sorted(Path('.').glob('**/*.py'))
          [PosixPath('build/lib/pathlib.py'),
           PosixPath('docs/conf.py'),
           PosixPath('pathlib.py'),
           PosixPath('setup.py'),
           PosixPath('test_pathlib.py')]

          備註: Using the "‘**’" pattern in large directory trees may
          consume an inordinate amount of time.

 -- 成員函式: Path.group ()

     Return the name of the group owning the file.  *note KeyError: 2c8.
     is raised if the file’s gid isn’t found in the system database.

 -- 成員函式: Path.is_dir ()

     Return ‘True’ if the path points to a directory (or a symbolic link
     pointing to a directory), ‘False’ if it points to another kind of
     file.

     ‘False’ is also returned if the path doesn’t exist or is a broken
     symlink; other errors (such as permission errors) are propagated.

 -- 成員函式: Path.is_file ()

     Return ‘True’ if the path points to a regular file (or a symbolic
     link pointing to a regular file), ‘False’ if it points to another
     kind of file.

     ‘False’ is also returned if the path doesn’t exist or is a broken
     symlink; other errors (such as permission errors) are propagated.

 -- 成員函式: Path.is_mount ()

     Return ‘True’ if the path is a `mount point': a point in a file
     system where a different file system has been mounted.  On POSIX,
     the function checks whether `path'’s parent, ‘path/..’, is on a
     different device than `path', or whether ‘path/..’ and `path' point
     to the same i-node on the same device — this should detect mount
     points for all Unix and POSIX variants.  Not implemented on
     Windows.

     3.7 版新加入.

 -- 成員函式: Path.is_symlink ()

     Return ‘True’ if the path points to a symbolic link, ‘False’
     otherwise.

     ‘False’ is also returned if the path doesn’t exist; other errors
     (such as permission errors) are propagated.

 -- 成員函式: Path.is_socket ()

     Return ‘True’ if the path points to a Unix socket (or a symbolic
     link pointing to a Unix socket), ‘False’ if it points to another
     kind of file.

     ‘False’ is also returned if the path doesn’t exist or is a broken
     symlink; other errors (such as permission errors) are propagated.

 -- 成員函式: Path.is_fifo ()

     Return ‘True’ if the path points to a FIFO (or a symbolic link
     pointing to a FIFO), ‘False’ if it points to another kind of file.

     ‘False’ is also returned if the path doesn’t exist or is a broken
     symlink; other errors (such as permission errors) are propagated.

 -- 成員函式: Path.is_block_device ()

     Return ‘True’ if the path points to a block device (or a symbolic
     link pointing to a block device), ‘False’ if it points to another
     kind of file.

     ‘False’ is also returned if the path doesn’t exist or is a broken
     symlink; other errors (such as permission errors) are propagated.

 -- 成員函式: Path.is_char_device ()

     Return ‘True’ if the path points to a character device (or a
     symbolic link pointing to a character device), ‘False’ if it points
     to another kind of file.

     ‘False’ is also returned if the path doesn’t exist or is a broken
     symlink; other errors (such as permission errors) are propagated.

 -- 成員函式: Path.iterdir ()

     When the path points to a directory, yield path objects of the
     directory contents:

          >>> 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')

     The children 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 path object for that file be included is unspecified.

 -- 成員函式: Path.lchmod (mode)

     Like *note Path.chmod(): 1bdb. but, if the path points to a
     symbolic link, the symbolic link’s mode is changed rather than its
     target’s.

 -- 成員函式: Path.lstat ()

     Like *note Path.stat(): 1bda. but, if the path points to a symbolic
     link, return the symbolic link’s information rather than its
     target’s.

 -- 成員函式: Path.mkdir (mode=0o777, parents=False, exist_ok=False)

     Create a new directory at this given path.  If `mode' is given, it
     is combined with the process’ ‘umask’ value to determine the file
     mode and access flags.  If the path already exists, *note
     FileExistsError: 95d. is raised.

     If `parents' is true, any missing parents of this path are created
     as needed; they are created with the default permissions without
     taking `mode' into account (mimicking the POSIX ‘mkdir -p’
     command).

     If `parents' is false (the default), a missing parent raises *note
     FileNotFoundError: 7c5.

     If `exist_ok' is false (the default), *note FileExistsError: 95d.
     is raised if the target directory already exists.

     If `exist_ok' is true, *note FileExistsError: 95d. exceptions will
     be ignored (same behavior as the POSIX ‘mkdir -p’ command), but
     only if the last path component is not an existing non-directory
     file.

     3.5 版更變: The `exist_ok' parameter was added.

 -- 成員函式: Path.open (mode='r', buffering=-1, encoding=None,
          errors=None, newline=None)

     Open the file pointed to by the path, like the built-in *note
     open(): 4f5. function does:

          >>> p = Path('setup.py')
          >>> with p.open() as f:
          ...     f.readline()
          ...
          '#!/usr/bin/env python3\n'

 -- 成員函式: Path.owner ()

     Return the name of the user owning the file.  *note KeyError: 2c8.
     is raised if the file’s uid isn’t found in the system database.

 -- 成員函式: Path.read_bytes ()

     Return the binary contents of the pointed-to file as a bytes
     object:

          >>> p = Path('my_binary_file')
          >>> p.write_bytes(b'Binary file contents')
          20
          >>> p.read_bytes()
          b'Binary file contents'

     3.5 版新加入.

 -- 成員函式: Path.read_text (encoding=None, errors=None)

     Return the decoded contents of the pointed-to file as a string:

          >>> p = Path('my_text_file')
          >>> p.write_text('Text file contents')
          18
          >>> p.read_text()
          'Text file contents'

     The file is opened and then closed.  The optional parameters have
     the same meaning as in *note open(): 4f5.

     3.5 版新加入.

 -- 成員函式: Path.rename (target)

     Rename this file or directory to the given `target', and return a
     new Path instance pointing to `target'.  On Unix, if `target'
     exists and is a file, it will be replaced silently if the user has
     permission.  `target' can be either a string or another path
     object:

          >>> p = Path('foo')
          >>> p.open('w').write('some text')
          9
          >>> target = Path('bar')
          >>> p.rename(target)
          PosixPath('bar')
          >>> target.open().read()
          'some text'

     The target path may be absolute or relative.  Relative paths are
     interpreted relative to the current working directory, `not' the
     directory of the Path object.

     3.8 版更變: Added return value, return the new Path instance.

 -- 成員函式: Path.replace (target)

     Rename this file or directory to the given `target', and return a
     new Path instance pointing to `target'.  If `target' points to an
     existing file or directory, it will be unconditionally replaced.

     The target path may be absolute or relative.  Relative paths are
     interpreted relative to the current working directory, `not' the
     directory of the Path object.

     3.8 版更變: Added return value, return the new Path instance.

 -- 成員函式: Path.resolve (strict=False)

     Make the path absolute, resolving any symlinks.  A new path object
     is returned:

          >>> p = Path()
          >>> p
          PosixPath('.')
          >>> p.resolve()
          PosixPath('/home/antoine/pathlib')

     "‘..’" components are also eliminated (this is the only method to
     do so):

          >>> p = Path('docs/../setup.py')
          >>> p.resolve()
          PosixPath('/home/antoine/pathlib/setup.py')

     If the path doesn’t exist and `strict' is ‘True’, *note
     FileNotFoundError: 7c5. is raised.  If `strict' is ‘False’, the
     path is resolved as far as possible and any remainder is appended
     without checking whether it exists.  If an infinite loop is
     encountered along the resolution path, *note RuntimeError: 2bb. is
     raised.

     3.6 版新加入: The `strict' argument (pre-3.6 behavior is strict).

 -- 成員函式: Path.rglob (pattern)

     This is like calling *note Path.glob(): 1bdc. with "‘**/’" added in
     front of the given relative `pattern':

          >>> sorted(Path().rglob("*.py"))
          [PosixPath('build/lib/pathlib.py'),
           PosixPath('docs/conf.py'),
           PosixPath('pathlib.py'),
           PosixPath('setup.py'),
           PosixPath('test_pathlib.py')]

 -- 成員函式: Path.rmdir ()

     Remove this directory.  The directory must be empty.

 -- 成員函式: Path.samefile (other_path)

     Return whether this path points to the same file as `other_path',
     which can be either a Path object, or a string.  The semantics are
     similar to *note os.path.samefile(): 887. and *note
     os.path.samestat(): 886.

     An *note OSError: 1d4. can be raised if either file cannot be
     accessed for some reason.

          >>> p = Path('spam')
          >>> q = Path('eggs')
          >>> p.samefile(q)
          False
          >>> p.samefile('spam')
          True

     3.5 版新加入.

 -- 成員函式: Path.symlink_to (target, target_is_directory=False)

     Make this path a symbolic link to `target'.  Under Windows,
     `target_is_directory' must be true (default ‘False’) if the link’s
     target is a directory.  Under POSIX, `target_is_directory'’s value
     is ignored.

          >>> 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

          備註: The order of arguments (link, target) is the reverse of
          *note os.symlink(): a40.’s.

 -- 成員函式: Path.link_to (target)

     Make `target' a hard link to this path.

          警告: This function does not make this path a hard link to
          `target', despite the implication of the function and argument
          names.  The argument order (target, link) is the reverse of
          *note Path.symlink_to(): 1be7, but matches that of *note
          os.link(): a3a.

     3.8 版新加入.

 -- 成員函式: Path.touch (mode=0o666, exist_ok=True)

     Create a file at this given path.  If `mode' is given, it is
     combined with the process’ ‘umask’ value to determine the file mode
     and access flags.  If the file already exists, the function
     succeeds if `exist_ok' is true (and its modification time is
     updated to the current time), otherwise *note FileExistsError: 95d.
     is raised.

 -- 成員函式: Path.unlink (missing_ok=False)

     Remove this file or symbolic link.  If the path points to a
     directory, use *note Path.rmdir(): 1be6. instead.

     If `missing_ok' is false (the default), *note FileNotFoundError:
     7c5. is raised if the path does not exist.

     If `missing_ok' is true, *note FileNotFoundError: 7c5. exceptions
     will be ignored (same behavior as the POSIX ‘rm -f’ command).

     3.8 版更變: The `missing_ok' parameter was added.

 -- 成員函式: Path.write_bytes (data)

     Open the file pointed to in bytes mode, write `data' to it, and
     close the file:

          >>> p = Path('my_binary_file')
          >>> p.write_bytes(b'Binary file contents')
          20
          >>> p.read_bytes()
          b'Binary file contents'

     An existing file of the same name is overwritten.

     3.5 版新加入.

 -- 成員函式: Path.write_text (data, encoding=None, errors=None)

     Open the file pointed to in text mode, write `data' to it, and
     close the file:

          >>> p = Path('my_text_file')
          >>> p.write_text('Text file contents')
          18
          >>> p.read_text()
          'Text file contents'

     An existing file of the same name is overwritten.  The optional
     parameters have the same meaning as in *note open(): 4f5.

     3.5 版新加入.


File: python.info,  Node: Correspondence to tools in the os module,  Prev: Concrete paths,  Up: pathlib --- Object-oriented filesystem paths

5.11.1.9 Correspondence to tools in the ‘os’ module
...................................................

Below is a table mapping various *note os: c5. functions to their
corresponding *note PurePath: 1046./*note Path: 202. equivalent.

     備註: Although *note os.path.relpath(): 1bea. and *note
     PurePath.relative_to(): 1bd4. have some overlapping use-cases,
     their semantics differ enough to warrant not considering them
     equivalent.

os and os.path                           pathlib
                                         
----------------------------------------------------------------------------
                                         
*note os.path.abspath(): cb5.            *note Path.resolve(): 1bc9.
                                         
                                         
*note os.chmod(): a38.                   *note Path.chmod(): 1bdb.
                                         
                                         
*note os.mkdir(): a3b.                   *note Path.mkdir(): 72e.
                                         
                                         
*note os.rename(): a3d.                  *note Path.rename(): 1be3.
                                         
                                         
*note os.replace(): a3e.                 *note Path.replace(): 1be4.
                                         
                                         
*note os.rmdir(): a3f.                   *note Path.rmdir(): 1be6.
                                         
                                         
*note os.remove(): a3c,                  *note Path.unlink(): fd3.
*note os.unlink(): a41.                  

*note os.getcwd(): fe3.                  *note Path.cwd(): 1bd9.
                                         
                                         
*note os.path.exists(): 1f7.             *note Path.exists(): 203.
                                         
                                         
*note os.path.expanduser(): 1ff.         *note Path.expanduser(): 72f.
                                         and *note Path.home(): 730.
                                         
                                         
*note os.listdir(): a46.                 *note Path.iterdir(): 1bde.
                                         
                                         
*note os.path.isdir(): 1f9.              *note Path.is_dir(): 204.
                                         
                                         
*note os.path.isfile(): 1fa.             *note Path.is_file(): 205.
                                         
                                         
*note os.path.islink(): 1f5.             *note Path.is_symlink(): 207.
                                         
                                         
*note os.link(): a3a.                    *note Path.link_to(): 20c.
                                         
                                         
*note os.symlink(): a40.                 *note Path.symlink_to(): 1be7.
                                         
                                         
*note os.stat(): 1f2.                    *note Path.stat(): 1bda,
                                         *note Path.owner(): 1be2,
                                         *note Path.group(): 1bdd.
                                         
                                         
*note os.path.isabs(): 1beb.             *note PurePath.is_absolute(): 1bd0.
                                         
                                         
*note os.path.join(): f61.               *note PurePath.joinpath(): 1bd2.
                                         
                                         
*note os.path.basename(): 1bec.          *note PurePath.name: 1bca.
                                         
                                         
*note os.path.dirname(): 1bed.           *note PurePath.parent: 1bc8.
                                         
                                         
*note os.path.samefile(): 887.           *note Path.samefile(): 72d.
                                         
                                         
*note os.path.splitext(): 1bee.          *note PurePath.suffix: 1bcb.
                                         


File: python.info,  Node: os path --- Common pathname manipulations,  Next: fileinput --- Iterate over lines from multiple input streams,  Prev: pathlib --- Object-oriented filesystem paths,  Up: 檔案與目錄存取

5.11.2 ‘os.path’ — Common pathname manipulations
------------------------------------------------

`Source code:' Lib/posixpath.py(1) (for POSIX) and Lib/ntpath.py(2) (for
Windows NT).

__________________________________________________________________

This module implements some useful functions on pathnames.  To read or
write files see *note open(): 4f5, and for accessing the filesystem see
the *note os: c5. module.  The path parameters can be passed as either
strings, or bytes.  Applications are encouraged to represent file names
as (Unicode) character strings.  Unfortunately, some file names may not
be representable as strings on Unix, so applications that need to
support arbitrary file names on Unix should use bytes objects to
represent path names.  Vice versa, using bytes objects cannot represent
all file names on Windows (in the standard ‘mbcs’ encoding), hence
Windows applications should use string objects to access all files.

Unlike a unix shell, Python does not do any `automatic' path expansions.
Functions such as *note expanduser(): 1ff. and *note expandvars(): d49.
can be invoked explicitly when an application desires shell-like path
expansion.  (See also the *note glob: 8a. module.)

也參考
......

The *note pathlib: c9. module offers high-level path objects.

     備註: All of these functions accept either only bytes or only
     string objects as their parameters.  The result is an object of the
     same type, if a path or file name is returned.

     備註: Since different operating systems have different path name
     conventions, there are several versions of this module in the
     standard library.  The *note os.path: c6. module is always the path
     module suitable for the operating system Python is running on, and
     therefore usable for local paths.  However, you can also import and
     use the individual modules if you want to manipulate a path that is
     `always' in one of the different formats.  They all have the same
     interface:

        * ‘posixpath’ for UNIX-style paths

        * ‘ntpath’ for Windows paths

3.8 版更變: *note exists(): 1f7, *note lexists(): 1f8, *note isdir():
1f9, *note isfile(): 1fa, *note islink(): 1f5, and *note ismount(): 1fb.
now return ‘False’ instead of raising an exception for paths that
contain characters or bytes unrepresentable at the OS level.

 -- 函式: os.path.abspath (path)

     Return a normalized absolutized version of the pathname `path'.  On
     most platforms, this is equivalent to calling the function *note
     normpath(): cb4. as follows: ‘normpath(join(os.getcwd(), path))’.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.basename (path)

     Return the base name of pathname `path'.  This is the second
     element of the pair returned by passing `path' to the function
     *note split(): 1bf1.  Note that the result of this function is
     different from the Unix ‘basename’ program; where ‘basename’ for
     ‘'/foo/bar/'’ returns ‘'bar'’, the *note basename(): 1bec. function
     returns an empty string (‘''’).

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.commonpath (paths)

     Return the longest common sub-path of each pathname in the sequence
     `paths'.  Raise *note ValueError: 1fc. if `paths' contain both
     absolute and relative pathnames, the `paths' are on the different
     drives or if `paths' is empty.  Unlike *note commonprefix(): 72b,
     this returns a valid path.

     *note Availability: 1364.: Unix, Windows.

     3.5 版新加入.

     3.6 版更變: Accepts a sequence of *note path-like objects: 36f.

 -- 函式: os.path.commonprefix (list)

     Return the longest path prefix (taken character-by-character) that
     is a prefix of all paths in `list'.  If `list' is empty, return the
     empty string (‘''’).

          備註: This function may return invalid paths because it works
          a character at a time.  To obtain a valid path, see *note
          commonpath(): 72a.

               >>> os.path.commonprefix(['/usr/lib', '/usr/local/lib'])
               '/usr/l'

               >>> os.path.commonpath(['/usr/lib', '/usr/local/lib'])
               '/usr'

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.dirname (path)

     Return the directory name of pathname `path'.  This is the first
     element of the pair returned by passing `path' to the function
     *note split(): 1bf1.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.exists (path)

     Return ‘True’ if `path' refers to an existing path or an open file
     descriptor.  Returns ‘False’ for broken symbolic links.  On some
     platforms, this function may return ‘False’ if permission is not
     granted to execute *note os.stat(): 1f2. on the requested file,
     even if the `path' physically exists.

     3.3 版更變: `path' can now be an integer: ‘True’ is returned if it
     is an open file descriptor, ‘False’ otherwise.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.lexists (path)

     Return ‘True’ if `path' refers to an existing path.  Returns ‘True’
     for broken symbolic links.  Equivalent to *note exists(): 1f7. on
     platforms lacking *note os.lstat(): 1f3.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.expanduser (path)

     On Unix and Windows, return the argument with an initial component
     of ‘~’ or ‘~user’ replaced by that `user'’s home directory.

     On Unix, an initial ‘~’ is replaced by the environment variable
     ‘HOME’ if it is set; otherwise the current user’s home directory is
     looked up in the password directory through the built-in module
     *note pwd: d7.  An initial ‘~user’ is looked up directly in the
     password directory.

     On Windows, ‘USERPROFILE’ will be used if set, otherwise a
     combination of ‘HOMEPATH’ and ‘HOMEDRIVE’ will be used.  An initial
     ‘~user’ is handled by stripping the last directory component from
     the created user path derived above.

     If the expansion fails or if the path does not begin with a tilde,
     the path is returned unchanged.

     3.6 版更變: Accepts a *note path-like object: 36f.

     3.8 版更變: No longer uses ‘HOME’ on Windows.

 -- 函式: os.path.expandvars (path)

     Return the argument with environment variables expanded.
     Substrings of the form ‘$name’ or ‘${name}’ are replaced by the
     value of environment variable `name'.  Malformed variable names and
     references to non-existing variables are left unchanged.

     On Windows, ‘%name%’ expansions are supported in addition to
     ‘$name’ and ‘${name}’.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.getatime (path)

     Return the time of last access of `path'.  The return value is a
     floating point number giving the number of seconds since the epoch
     (see the *note time: 10b. module).  Raise *note OSError: 1d4. if
     the file does not exist or is inaccessible.

 -- 函式: os.path.getmtime (path)

     Return the time of last modification of `path'.  The return value
     is a floating point number giving the number of seconds since the
     epoch (see the *note time: 10b. module).  Raise *note OSError: 1d4.
     if the file does not exist or is inaccessible.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.getctime (path)

     Return the system’s ctime which, on some systems (like Unix) is the
     time of the last metadata change, and, on others (like Windows), is
     the creation time for `path'.  The return value is a number giving
     the number of seconds since the epoch (see the *note time: 10b.
     module).  Raise *note OSError: 1d4. if the file does not exist or
     is inaccessible.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.getsize (path)

     Return the size, in bytes, of `path'.  Raise *note OSError: 1d4. if
     the file does not exist or is inaccessible.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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 a
     (back)slash after chopping off a potential drive letter.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.isfile (path)

     Return ‘True’ if `path' is an *note existing: 1f7. regular file.
     This follows symbolic links, so both *note islink(): 1f5. and *note
     isfile(): 1fa. can be true for the same path.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.isdir (path)

     Return ‘True’ if `path' is an *note existing: 1f7. directory.  This
     follows symbolic links, so both *note islink(): 1f5. and *note
     isdir(): 1f9. can be true for the same path.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.islink (path)

     Return ‘True’ if `path' refers to an *note existing: 1f7. directory
     entry that is a symbolic link.  Always ‘False’ if symbolic links
     are not supported by the Python runtime.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.ismount (path)

     Return ‘True’ if pathname `path' is a `mount point': a point in a
     file system where a different file system has been mounted.  On
     POSIX, the function checks whether `path'’s parent, ‘`path'/..’, is
     on a different device than `path', or whether ‘`path'/..’ and
     `path' point to the same i-node on the same device — this should
     detect mount points for all Unix and POSIX variants.  It is not
     able to reliably detect bind mounts on the same filesystem.  On
     Windows, a drive letter root and a share UNC are always mount
     points, and for any other path ‘GetVolumePathName’ is called to see
     if it is different from the input path.

     3.4 版新加入: Support for detecting non-root mount points on
     Windows.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.join (path, *paths)

     Join one or more path components intelligently.  The return value
     is the concatenation of `path' and any members of `*paths' with
     exactly one directory separator following each non-empty part
     except the last, meaning that the result will only end in a
     separator if the last part is empty.  If a component is an absolute
     path, all previous components are thrown away and joining continues
     from the absolute path component.

     On Windows, the drive letter is not reset when an absolute path
     component (e.g., ‘r'\foo'’) is encountered.  If a component
     contains a drive letter, all previous components are thrown away
     and the drive letter is reset.  Note that since there is a current
     directory for each drive, ‘os.path.join("c:", "foo")’ represents a
     path relative to the current directory on drive ‘C:’ (‘c:foo’), not
     ‘c:\foo’.

     3.6 版更變: Accepts a *note path-like object: 36f. for `path' and
     `paths'.

 -- 函式: os.path.normcase (path)

     Normalize the case of a pathname.  On Windows, convert all
     characters in the pathname to lowercase, and also convert forward
     slashes to backward slashes.  On other operating systems, return
     the path unchanged.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.normpath (path)

     Normalize a pathname by collapsing redundant separators and
     up-level references so that ‘A//B’, ‘A/B/’, ‘A/./B’ and
     ‘A/foo/../B’ all become ‘A/B’.  This string manipulation may change
     the meaning of a path that contains symbolic links.  On Windows, it
     converts forward slashes to backward slashes.  To normalize case,
     use *note normcase(): 1bf6.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.realpath (path)

     Return the canonical path of the specified filename, eliminating
     any symbolic links encountered in the path (if they are supported
     by the operating system).

          備註: When symbolic link cycles occur, the returned path will
          be one member of the cycle, but no guarantee is made about
          which member that will be.

     3.6 版更變: Accepts a *note path-like object: 36f.

     3.8 版更變: Symbolic links and junctions are now resolved on
     Windows.

 -- 函式: os.path.relpath (path, start=os.curdir)

     Return a relative filepath to `path' either from the current
     directory or from an optional `start' directory.  This is a path
     computation: the filesystem is not accessed to confirm the
     existence or nature of `path' or `start'.  On Windows, *note
     ValueError: 1fc. is raised when `path' and `start' are on different
     drives.

     `start' defaults to *note os.curdir: 1bf7.

     *note Availability: 1364.: Unix, Windows.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.samefile (path1, path2)

     Return ‘True’ if both pathname arguments refer to the same file or
     directory.  This is determined by the device number and i-node
     number and raises an exception if an *note os.stat(): 1f2. call on
     either pathname fails.

     *note Availability: 1364.: Unix, Windows.

     3.2 版更變: Added Windows support.

     3.4 版更變: Windows now uses the same implementation as all other
     platforms.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.sameopenfile (fp1, fp2)

     Return ‘True’ if the file descriptors `fp1' and `fp2' refer to the
     same file.

     *note Availability: 1364.: Unix, Windows.

     3.2 版更變: Added Windows support.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.samestat (stat1, stat2)

     Return ‘True’ if the stat tuples `stat1' and `stat2' refer to the
     same file.  These structures may have been returned by *note
     os.fstat(): 664, *note os.lstat(): 1f3, or *note os.stat(): 1f2.
     This function implements the underlying comparison used by *note
     samefile(): 887. and *note sameopenfile(): 1bf8.

     *note Availability: 1364.: Unix, Windows.

     3.4 版更變: Added Windows support.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.split (path)

     Split the pathname `path' into a pair, ‘(head, tail)’ where `tail'
     is the last pathname component and `head' is everything leading up
     to that.  The `tail' part will never contain a slash; if `path'
     ends in a slash, `tail' will be empty.  If there is no slash in
     `path', `head' will be empty.  If `path' is empty, both `head' and
     `tail' are empty.  Trailing slashes are stripped from `head' unless
     it is the root (one or more slashes only).  In all cases,
     ‘join(head, tail)’ returns a path to the same location as `path'
     (but the strings may differ).  Also see the functions *note
     dirname(): 1bed. and *note basename(): 1bec.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.splitdrive (path)

     Split the pathname `path' into a pair ‘(drive, tail)’ where `drive'
     is either a mount point or the empty string.  On systems which do
     not use drive specifications, `drive' will always be the empty
     string.  In all cases, ‘drive + tail’ will be the same as `path'.

     On Windows, splits a pathname into drive/UNC sharepoint and
     relative path.

     If the path contains a drive letter, drive will contain everything
     up to and including the colon.  e.g.  ‘splitdrive("c:/dir")’
     returns ‘("c:", "/dir")’

     If the path contains a UNC path, drive will contain the host name
     and share, up to but not including the fourth separator.  e.g.
     ‘splitdrive("//host/computer/dir")’ returns ‘("//host/computer",
     "/dir")’

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.path.splitext (path)

     Split the pathname `path' into a pair ‘(root, ext)’ such that ‘root
     + ext == path’, and `ext' is empty or begins with a period and
     contains at most one period.  Leading periods on the basename are
     ignored; ‘splitext('.cshrc')’ returns ‘('.cshrc', '')’.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- Data: os.path.supports_unicode_filenames

     ‘True’ if arbitrary Unicode strings can be used as file names
     (within limitations imposed by the file system).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/posixpath.py

   (2) https://github.com/python/cpython/tree/3.8/Lib/ntpath.py


File: python.info,  Node: fileinput --- Iterate over lines from multiple input streams,  Next: stat --- Interpreting stat results,  Prev: os path --- Common pathname manipulations,  Up: 檔案與目錄存取

5.11.3 ‘fileinput’ — Iterate over lines from multiple input streams
-------------------------------------------------------------------

`Source code:' 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(): 4f5.

The typical use is:

     import fileinput
     for line in fileinput.input():
         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(): 2ae.  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(): 2ae. or
*note FileInput: 280.  If an I/O error occurs during opening or reading
a file, *note OSError: 1d4. is raised.

3.3 版更變: *note IOError: 997. used to be raised; it is now an alias of
*note OSError: 1d4.

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(): 2ae. or *note
FileInput(): 280.  The hook must be a function that takes two arguments,
`filename' and `mode', and returns an accordingly opened file-like
object.  Two useful hooks are already provided by this module.

The following function is the primary interface of this module:

 -- 函式: fileinput.input (files=None, inplace=False, backup='', *,
          mode='r', openhook=None)

     Create an instance of the *note FileInput: 280. 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: 280. class.

     The *note FileInput: 280. instance can be used as a context manager
     in the *note with: 6ee. 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')) 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.

The following functions use the global state created by *note
fileinput.input(): 2ae.; if there is no active state, *note
RuntimeError: 2bb. 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)

     Class *note FileInput: 280. is the implementation; its methods
     *note filename(): 1bfb, *note fileno(): 1bfc, *note lineno(): 1bfd,
     *note filelineno(): 1bfe, *note isfirstline(): 1bff, *note
     isstdin(): 1c00, *note nextfile(): 1c01. and *note close(): 1c02.
     correspond to the functions of the same name in the module.  In
     addition it has a *note readline(): 1c03. method which returns the
     next input line, and a *note __getitem__(): 27d. method which
     implements the sequence behavior.  The sequence must be accessed in
     strictly sequential order; random access and *note readline():
     1c03. cannot be mixed.

     With `mode' you can specify which file mode will be passed to *note
     open(): 4f5.  It must be one of ‘'r'’, ‘'rU'’, ‘'U'’ 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.

     A *note FileInput: 280. instance can be used as a context manager
     in the *note with: 6ee. 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.4 版後已棄用: The ‘'rU'’ and ‘'U'’ modes.

     3.8 版後已棄用: Support for *note __getitem__(): 27d. method is
     deprecated.

     3.8 版更變: The keyword parameter `mode' and `openhook' are now
     keyword-only.

`Optional in-place filtering:' if the keyword argument ‘inplace=True’ is
passed to *note fileinput.input(): 2ae. or to the *note FileInput: 280.
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)

     Transparently opens files compressed with gzip and bzip2
     (recognized by the extensions ‘'.gz'’ and ‘'.bz2'’) using the *note
     gzip: 8c. and *note bz2: 14. modules.  If the filename extension is
     not ‘'.gz'’ or ‘'.bz2'’, the file is opened normally (ie, using
     *note open(): 4f5. without any decompression).

     Usage example: ‘fi =
     fileinput.FileInput(openhook=fileinput.hook_compressed)’

 -- 函式: fileinput.hook_encoded (encoding, errors=None)

     Returns a hook which opens each file with *note open(): 4f5, using
     the given `encoding' and `errors' to read the file.

     Usage example: ‘fi =
     fileinput.FileInput(openhook=fileinput.hook_encoded("utf-8",
     "surrogateescape"))’

     3.6 版更變: Added the optional `errors' parameter.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/fileinput.py


File: python.info,  Node: stat --- Interpreting stat results,  Next: filecmp --- File and Directory Comparisons,  Prev: fileinput --- Iterate over lines from multiple input streams,  Up: 檔案與目錄存取

5.11.4 ‘stat’ — Interpreting ‘stat()’ results
---------------------------------------------

`Source code:' Lib/stat.py(1)

__________________________________________________________________

The *note stat: f5. module defines constants and functions for
interpreting the results of *note os.stat(): 1f2, *note os.fstat(): 664.
and *note os.lstat(): 1f3. (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: f5. 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(): a38.—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: c6,
like the tests for block and character devices.

Example:

     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.stat(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: 8d9, *note
     S_IFPORT: 8da. and *note S_IFWHT: 8db.

All the variables below are simply symbolic indexes into the 10-tuple
returned by *note os.stat(): 1f2, *note os.fstat(): 664. or *note
os.lstat(): 1f3.

 -- Data: stat.ST_MODE

     Inode protection mode.

 -- Data: stat.ST_INO

     Inode number.

 -- Data: stat.ST_DEV

     Device inode resides on.

 -- Data: stat.ST_NLINK

     Number of links to the inode.

 -- Data: stat.ST_UID

     User id of the owner.

 -- Data: stat.ST_GID

     Group id of the owner.

 -- Data: stat.ST_SIZE

     Size in bytes of a plain file; amount of data waiting on some
     special files.

 -- Data: stat.ST_ATIME

     Time of last access.

 -- Data: stat.ST_MTIME

     Time of last modification.

 -- Data: 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(): 1f2, *note os.fstat(): 664, or *note os.lstat():
1f3.; 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: 8d8.
field.

Use of the functions above is more portable than use of the first set of
flags:

 -- Data: stat.S_IFSOCK

     Socket.

 -- Data: stat.S_IFLNK

     Symbolic link.

 -- Data: stat.S_IFREG

     Regular file.

 -- Data: stat.S_IFBLK

     Block device.

 -- Data: stat.S_IFDIR

     Directory.

 -- Data: stat.S_IFCHR

     Character device.

 -- Data: stat.S_IFIFO

     FIFO.

 -- Data: stat.S_IFDOOR

     Door.

     3.4 版新加入.

 -- Data: stat.S_IFPORT

     Event port.

     3.4 版新加入.

 -- Data: stat.S_IFWHT

     Whiteout.

     3.4 版新加入.

     備註: *note S_IFDOOR: 8d9, *note S_IFPORT: 8da. or *note S_IFWHT:
     8db. 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(): a38.:

 -- Data: stat.S_ISUID

     Set UID bit.

 -- Data: 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:
     1c21. bit set.  For a file that does not have the group execution
     bit (*note S_IXGRP: 1c22.) set, the set-group-ID bit indicates
     mandatory file/record locking (see also *note S_ENFMT: 1c23.).

 -- Data: 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.

 -- Data: stat.S_IRWXU

     Mask for file owner permissions.

 -- Data: stat.S_IRUSR

     Owner has read permission.

 -- Data: stat.S_IWUSR

     Owner has write permission.

 -- Data: stat.S_IXUSR

     Owner has execute permission.

 -- Data: stat.S_IRWXG

     Mask for group permissions.

 -- Data: stat.S_IRGRP

     Group has read permission.

 -- Data: stat.S_IWGRP

     Group has write permission.

 -- Data: stat.S_IXGRP

     Group has execute permission.

 -- Data: stat.S_IRWXO

     Mask for permissions for others (not in group).

 -- Data: stat.S_IROTH

     Others have read permission.

 -- Data: stat.S_IWOTH

     Others have write permission.

 -- Data: stat.S_IXOTH

     Others have execute permission.

 -- Data: stat.S_ENFMT

     System V file locking enforcement.  This flag is shared with *note
     S_ISGID: 1c21.: file/record locking is enforced on files that do
     not have the group execution bit (*note S_IXGRP: 1c22.) set.

 -- Data: stat.S_IREAD

     Unix V7 synonym for *note S_IRUSR: 1c26.

 -- Data: stat.S_IWRITE

     Unix V7 synonym for *note S_IWUSR: 1c27.

 -- Data: stat.S_IEXEC

     Unix V7 synonym for *note S_IXUSR: 1c28.

The following flags can be used in the `flags' argument of *note
os.chflags(): a37.:

 -- Data: stat.UF_NODUMP

     Do not dump the file.

 -- Data: stat.UF_IMMUTABLE

     The file may not be changed.

 -- Data: stat.UF_APPEND

     The file may only be appended to.

 -- Data: stat.UF_OPAQUE

     The directory is opaque when viewed through a union stack.

 -- Data: stat.UF_NOUNLINK

     The file may not be renamed or deleted.

 -- Data: stat.UF_COMPRESSED

     The file is stored compressed (Mac OS X 10.6+).

 -- Data: stat.UF_HIDDEN

     The file should not be displayed in a GUI (Mac OS X 10.5+).

 -- Data: stat.SF_ARCHIVED

     The file may be archived.

 -- Data: stat.SF_IMMUTABLE

     The file may not be changed.

 -- Data: stat.SF_APPEND

     The file may only be appended to.

 -- Data: stat.SF_NOUNLINK

     The file may not be renamed or deleted.

 -- Data: stat.SF_SNAPSHOT

     The file is a snapshot file.

See the *BSD or Mac OS systems man page ‘chflags(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(): 1f2.  See the Windows API documentation(2) for more detail on
the meaning of these constants.

 -- Data: stat.FILE_ATTRIBUTE_ARCHIVE
 -- Data: stat.FILE_ATTRIBUTE_COMPRESSED
 -- Data: stat.FILE_ATTRIBUTE_DEVICE
 -- Data: stat.FILE_ATTRIBUTE_DIRECTORY
 -- Data: stat.FILE_ATTRIBUTE_ENCRYPTED
 -- Data: stat.FILE_ATTRIBUTE_HIDDEN
 -- Data: stat.FILE_ATTRIBUTE_INTEGRITY_STREAM
 -- Data: stat.FILE_ATTRIBUTE_NORMAL
 -- Data: stat.FILE_ATTRIBUTE_NOT_CONTENT_INDEXED
 -- Data: stat.FILE_ATTRIBUTE_NO_SCRUB_DATA
 -- Data: stat.FILE_ATTRIBUTE_OFFLINE
 -- Data: stat.FILE_ATTRIBUTE_READONLY
 -- Data: stat.FILE_ATTRIBUTE_REPARSE_POINT
 -- Data: stat.FILE_ATTRIBUTE_SPARSE_FILE
 -- Data: stat.FILE_ATTRIBUTE_SYSTEM
 -- Data: stat.FILE_ATTRIBUTE_TEMPORARY
 -- Data: 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(): 1f3.  These
are well-known constants, but are not an exhaustive list.

 -- Data: stat.IO_REPARSE_TAG_SYMLINK
 -- Data: stat.IO_REPARSE_TAG_MOUNT_POINT
 -- Data: stat.IO_REPARSE_TAG_APPEXECLINK

     3.8 版新加入.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/stat.py

   (2) 
https://msdn.microsoft.com/en-us/library/windows/desktop/gg258117.aspx


File: python.info,  Node: filecmp --- File and Directory Comparisons,  Next: tempfile --- Generate temporary files and directories,  Prev: stat --- Interpreting stat results,  Up: 檔案與目錄存取

5.11.5 ‘filecmp’ — File and Directory Comparisons
-------------------------------------------------

`Source code:' Lib/filecmp.py(1)

__________________________________________________________________

The *note filecmp: 7f. module defines functions to compare files and
directories, with various optional time/correctness trade-offs.  For
comparing files, see also the *note difflib: 37. module.

The *note filecmp: 7f. 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, files with identical *note os.stat(): 1f2.
     signatures are taken to be equal.  Otherwise, the contents of the
     files are compared.

     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(): 1f2.
     information for the file changes.  The entire cache may be cleared
     using *note clear_cache(): 84c.

 -- 函式: 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(): 1c55.

     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.8/Lib/filecmp.py


File: python.info,  Node: The dircmp class,  Up: filecmp --- File and Directory Comparisons

5.11.5.1 The ‘dircmp’ class
...........................

 -- 類別: filecmp.dircmp (a, b, ignore=None, hide=None)

     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: 84d.  `hide' is a
     list of names to hide, and defaults to ‘[os.curdir, os.pardir]’.

     The *note dircmp: 84e. class compares files by doing `shallow'
     comparisons as described for *note filecmp.cmp(): 1c55.

     The *note dircmp: 84e. class provides the following methods:

      -- 成員函式: report ()

          Print (to *note sys.stdout: 313.) 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: 84e. 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__(): 31f. 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(): 1f2.
          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: 1c63. to
          *note dircmp: 84e. objects.

 -- 屬性: filecmp.DEFAULT_IGNORES

     3.4 版新加入.

     List of directories ignored by *note dircmp: 84e. 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 --- Generate temporary files and directories,  Next: glob --- Unix style pathname pattern expansion,  Prev: filecmp --- File and Directory Comparisons,  Up: 檔案與目錄存取

5.11.6 ‘tempfile’ — Generate temporary files and directories
------------------------------------------------------------

`Source code:' Lib/tempfile.py(1)

__________________________________________________________________

This module creates temporary files and directories.  It works on all
supported platforms.  *note TemporaryFile: 1c6c, *note
NamedTemporaryFile: d4e, *note TemporaryDirectory: bcd, and *note
SpooledTemporaryFile: aab. are high-level interfaces which provide
automatic cleanup and can be used as context managers.  *note mkstemp():
1c6d. and *note mkdtemp(): 1c6e. are lower-level functions which require
manual cleanup.

All the user-callable functions and constructors take additional
arguments which allow direct control over the location and name of
temporary files and directories.  Files names used by this module
include a string of random characters which allows those files to be
securely created in shared temporary directories.  To maintain backward
compatibility, the argument order is somewhat odd; it is recommended to
use keyword arguments for clarity.

The module defines the following user-callable items:

 -- 函式: tempfile.TemporaryFile (mode='w+b', buffering=-1,
          encoding=None, newline=None, suffix=None, prefix=None,
          dir=None, *, errors=None)

     Return a *note file-like object: 1c6f. that can be used as a
     temporary storage area.  The file is created securely, using the
     same rules as *note mkstemp(): 1c6d.  It will be destroyed as soon
     as it is closed (including an implicit close when the object is
     garbage collected).  Under Unix, the directory entry for the file
     is either not created at all or is removed immediately after the
     file is created.  Other platforms do not support this; your code
     should not rely on a temporary file created using this function
     having or not having a visible name in the file system.

     The resulting object can be used as a context manager (see *note
     Examples: 1c70.).  On completion of the context or destruction of
     the file object the temporary file will be removed from the
     filesystem.

     The `mode' parameter defaults to ‘'w+b'’ so that the file created
     can be read and written without being closed.  Binary mode is used
     so that it behaves consistently on all platforms without regard for
     the data that is stored.  `buffering', `encoding', `errors' and
     `newline' are interpreted as for *note open(): 4f5.

     The `dir', `prefix' and `suffix' parameters have the same meaning
     and defaults as with *note mkstemp(): 1c6d.

     The returned object is a true file object on POSIX platforms.  On
     other platforms, it is a file-like object whose ‘file’ attribute is
     the underlying true file object.

     The *note os.O_TMPFILE: 889. flag is used if it is available and
     works (Linux-specific, requires Linux kernel 3.11 or later).

     Raises an *note auditing event: e96. ‘tempfile.mkstemp’ with
     argument ‘fullpath’.

     3.5 版更變: The *note os.O_TMPFILE: 889. flag is now used if
     available.

     3.8 版更變: Added `errors' parameter.

 -- 函式: tempfile.NamedTemporaryFile (mode='w+b', buffering=-1,
          encoding=None, newline=None, suffix=None, prefix=None,
          dir=None, delete=True, *, errors=None)

     This function operates exactly as *note TemporaryFile(): 1c6c.
     does, except that the file is guaranteed to have a visible name in
     the file system (on Unix, the directory entry is not unlinked).
     That name can be retrieved from the ‘name’ attribute of the
     returned file-like object.  Whether the name can be used to open
     the file a second time, while the named temporary file is still
     open, varies across platforms (it can be so used on Unix; it cannot
     on Windows NT or later).  If `delete' is true (the default), the
     file is deleted as soon as it is closed.  The returned object is
     always a file-like object whose ‘file’ attribute is the underlying
     true file object.  This file-like object can be used in a *note
     with: 6ee. statement, just like a normal file.

     Raises an *note auditing event: e96. ‘tempfile.mkstemp’ with
     argument ‘fullpath’.

     3.8 版更變: Added `errors' parameter.

 -- 函式: tempfile.SpooledTemporaryFile (max_size=0, mode='w+b',
          buffering=-1, encoding=None, newline=None, suffix=None,
          prefix=None, dir=None, *, errors=None)

     This function operates exactly as *note TemporaryFile(): 1c6c.
     does, except that data is spooled in memory until the file size
     exceeds `max_size', or until the file’s ‘fileno()’ method is
     called, at which point the contents are written to disk and
     operation proceeds as with *note TemporaryFile(): 1c6c.

     The resulting file has one additional method, ‘rollover()’, which
     causes the file to roll over to an on-disk file regardless of its
     size.

     The returned object is a file-like object whose ‘_file’ attribute
     is either an *note io.BytesIO: 7a0. or *note io.TextIOWrapper: 5f8.
     object (depending on whether binary or text `mode' was specified)
     or a true file object, depending on whether ‘rollover()’ has been
     called.  This file-like object can be used in a *note with: 6ee.
     statement, just like a normal file.

     3.3 版更變: the truncate method now accepts a ‘size’ argument.

     3.8 版更變: Added `errors' parameter.

 -- 函式: tempfile.TemporaryDirectory (suffix=None, prefix=None,
          dir=None)

     This function securely creates a temporary directory using the same
     rules as *note mkdtemp(): 1c6e.  The resulting object can be used
     as a context manager (see *note Examples: 1c70.).  On completion of
     the context or destruction of the temporary directory object the
     newly created temporary directory and all its contents are removed
     from the filesystem.

     The directory name can be retrieved from the ‘name’ attribute of
     the returned object.  When the returned object is used as a context
     manager, the ‘name’ will be assigned to the target of the ‘as’
     clause in the *note with: 6ee. statement, if there is one.

     The directory can be explicitly cleaned up by calling the
     ‘cleanup()’ method.

     Raises an *note auditing event: e96. ‘tempfile.mkdtemp’ with
     argument ‘fullpath’.

     3.2 版新加入.

 -- 函式: tempfile.mkstemp (suffix=None, prefix=None, dir=None,
          text=False)

     Creates a temporary file in the most secure manner possible.  There
     are no race conditions in the file’s creation, assuming that the
     platform properly implements the *note os.O_EXCL: 1c71. flag for
     *note os.open(): 66a.  The file is readable and writable only by
     the creating user ID. If the platform uses permission bits to
     indicate whether a file is executable, the file is executable by no
     one.  The file descriptor is not inherited by child processes.

     Unlike *note TemporaryFile(): 1c6c, the user of *note mkstemp():
     1c6d. is responsible for deleting the temporary file when done with
     it.

     If `suffix' is not ‘None’, the file name will end with that suffix,
     otherwise there will be no suffix.  *note mkstemp(): 1c6d. does not
     put a dot between the file name and the suffix; if you need one,
     put it at the beginning of `suffix'.

     If `prefix' is not ‘None’, the file name will begin with that
     prefix; otherwise, a default prefix is used.  The default is the
     return value of *note gettempprefix(): 1c72. or *note
     gettempprefixb(): 1c73, as appropriate.

     If `dir' is not ‘None’, the file will be created in that directory;
     otherwise, a default directory is used.  The default directory is
     chosen from a platform-dependent list, but the user of the
     application can control the directory location by setting the
     `TMPDIR', `TEMP' or `TMP' environment variables.  There is thus no
     guarantee that the generated filename will have any nice
     properties, such as not requiring quoting when passed to external
     commands via ‘os.popen()’.

     If any of `suffix', `prefix', and `dir' are not ‘None’, they must
     be the same type.  If they are bytes, the returned name will be
     bytes instead of str.  If you want to force a bytes return value
     with otherwise default behavior, pass ‘suffix=b''’.

     If `text' is specified and true, the file is opened in text mode.
     Otherwise, (the default) the file is opened in binary mode.

     *note mkstemp(): 1c6d. returns a tuple containing an OS-level
     handle to an open file (as would be returned by *note os.open():
     66a.) and the absolute pathname of that file, in that order.

     Raises an *note auditing event: e96. ‘tempfile.mkstemp’ with
     argument ‘fullpath’.

     3.5 版更變: `suffix', `prefix', and `dir' may now be supplied in
     bytes in order to obtain a bytes return value.  Prior to this, only
     str was allowed.  `suffix' and `prefix' now accept and default to
     ‘None’ to cause an appropriate default value to be used.

     3.6 版更變: The `dir' parameter now accepts a *note path-like
     object: 36f.

 -- 函式: tempfile.mkdtemp (suffix=None, prefix=None, dir=None)

     Creates a temporary directory in the most secure manner possible.
     There are no race conditions in the directory’s creation.  The
     directory is readable, writable, and searchable only by the
     creating user ID.

     The user of *note mkdtemp(): 1c6e. is responsible for deleting the
     temporary directory and its contents when done with it.

     The `prefix', `suffix', and `dir' arguments are the same as for
     *note mkstemp(): 1c6d.

     *note mkdtemp(): 1c6e. returns the absolute pathname of the new
     directory.

     Raises an *note auditing event: e96. ‘tempfile.mkdtemp’ with
     argument ‘fullpath’.

     3.5 版更變: `suffix', `prefix', and `dir' may now be supplied in
     bytes in order to obtain a bytes return value.  Prior to this, only
     str was allowed.  `suffix' and `prefix' now accept and default to
     ‘None’ to cause an appropriate default value to be used.

     3.6 版更變: The `dir' parameter now accepts a *note path-like
     object: 36f.

 -- 函式: tempfile.gettempdir ()

     Return the name of the directory used for temporary files.  This
     defines the default value for the `dir' argument to all functions
     in this module.

     Python searches a standard list of directories to find one which
     the calling user can create files in.  The list is:

       1. The directory named by the ‘TMPDIR’ environment variable.

       2. The directory named by the ‘TEMP’ environment variable.

       3. The directory named by the ‘TMP’ environment variable.

       4. A platform-specific location:

             * On Windows, the directories ‘C:\TEMP’, ‘C:\TMP’, ‘\TEMP’,
               and ‘\TMP’, in that order.

             * On all other platforms, the directories ‘/tmp’,
               ‘/var/tmp’, and ‘/usr/tmp’, in that order.

       5. As a last resort, the current working directory.

     The result of this search is cached, see the description of *note
     tempdir: 1c75. below.

 -- 函式: tempfile.gettempdirb ()

     Same as *note gettempdir(): 1c74. but the return value is in bytes.

     3.5 版新加入.

 -- 函式: tempfile.gettempprefix ()

     Return the filename prefix used to create temporary files.  This
     does not contain the directory component.

 -- 函式: tempfile.gettempprefixb ()

     Same as *note gettempprefix(): 1c72. but the return value is in
     bytes.

     3.5 版新加入.

The module uses a global variable to store the name of the directory
used for temporary files returned by *note gettempdir(): 1c74.  It can
be set directly to override the selection process, but this is
discouraged.  All functions in this module take a `dir' argument which
can be used to specify the directory and this is the recommended
approach.

 -- Data: tempfile.tempdir

     When set to a value other than ‘None’, this variable defines the
     default value for the `dir' argument to the functions defined in
     this module.

     If ‘tempdir’ is ‘None’ (the default) at any call to any of the
     above functions except *note gettempprefix(): 1c72. it is
     initialized following the algorithm described in *note
     gettempdir(): 1c74.

* Menu:

* Examples: Examples<3>.
* Deprecated functions and variables::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/tempfile.py


File: python.info,  Node: Examples<3>,  Next: Deprecated functions and variables,  Up: tempfile --- Generate temporary files and directories

5.11.6.1 Examples
.................

Here are some examples of typical usage of the *note tempfile: 104.
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 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: Deprecated functions and variables,  Prev: Examples<3>,  Up: tempfile --- Generate temporary files and directories

5.11.6.2 Deprecated functions and variables
...........................................

A historical way to create temporary files was to first generate a file
name with the *note mktemp(): 1c79. function and then create a file
using this name.  Unfortunately this is not secure, because a different
process may create a file with this name in the time between the call to
*note mktemp(): 1c79. and the subsequent attempt to create the file by
the first process.  The solution is to combine the two steps and create
the file immediately.  This approach is used by *note mkstemp(): 1c6d.
and the other functions described above.

 -- 函式: tempfile.mktemp (suffix='', prefix='tmp', dir=None)

     2.3 版後已棄用: Use *note mkstemp(): 1c6d. instead.

     Return an absolute pathname of a file that did not exist at the
     time the call is made.  The `prefix', `suffix', and `dir' arguments
     are similar to those of *note mkstemp(): 1c6d, except that bytes
     file names, ‘suffix=None’ and ‘prefix=None’ are not supported.

          警告: Use of this function may introduce a security hole in
          your program.  By the time you get around to doing anything
          with the file name it returns, someone else may have beaten
          you to the punch.  *note mktemp(): 1c79. usage can be replaced
          easily with *note NamedTemporaryFile(): d4e, passing it the
          ‘delete=False’ parameter:

               >>> 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 style pathname pattern expansion,  Next: fnmatch --- Unix filename pattern matching,  Prev: tempfile --- Generate temporary files and directories,  Up: 檔案與目錄存取

5.11.7 ‘glob’ — Unix style pathname pattern expansion
-----------------------------------------------------

`Source code:' Lib/glob.py(1)

__________________________________________________________________

The *note glob: 8a. module finds all the pathnames matching a specified
pattern according to the rules used by the Unix shell, although results
are returned in arbitrary order.  No tilde expansion is done, but ‘*’,
‘?’, and character ranges expressed with ‘[]’ will be correctly matched.
This is done by using the *note os.scandir(): 260. and *note
fnmatch.fnmatch(): 1c7c. functions in concert, and not by actually
invoking a subshell.  Note that unlike *note fnmatch.fnmatch(): 1c7c,
*note glob: 8a. treats filenames beginning with a dot (‘.’) as special
cases.  (For tilde and shell variable expansion, use *note
os.path.expanduser(): 1ff. and *note os.path.expandvars(): d49.)

For a literal match, wrap the meta-characters in brackets.  For example,
‘'[?]'’ matches the character ‘'?'’.

也參考
......

The *note pathlib: c9. module offers high-level path objects.

 -- 函式: glob.glob (pathname, *, recursive=False)

     Return a possibly-empty list of path names that match `pathname',
     which must be a string containing a path specification.  `pathname'
     can be either absolute (like ‘/usr/src/Python-1.5/Makefile’) or
     relative (like ‘../../Tools/*/*.gif’), and can contain shell-style
     wildcards.  Broken symlinks are included in the results (as in the
     shell).  Whether or not the results are sorted depends on the file
     system.  If a file that satisfies conditions is removed or added
     during the call of this function, whether a path name for that file
     be included is unspecified.

     If `recursive' is true, the pattern "‘**’" will match any files and
     zero or more directories, subdirectories and symbolic links to
     directories.  If the pattern is followed by an *note os.sep: 1c7d.
     or *note os.altsep: 1c7e. then files will not match.

     Raises an *note auditing event: e96. ‘glob.glob’ with arguments
     ‘pathname’, ‘recursive’.

          備註: Using the "‘**’" pattern in large directory trees may
          consume an inordinate amount of time.

     3.5 版更變: Support for recursive globs using "‘**’".

 -- 函式: glob.iglob (pathname, *, recursive=False)

     Return an *note iterator: 1040. which yields the same values as
     *note glob(): 8a. without actually storing them all simultaneously.

     Raises an *note auditing event: e96. ‘glob.glob’ with arguments
     ‘pathname’, ‘recursive’.

 -- 函式: glob.escape (pathname)

     Escape all special characters (‘'?'’, ‘'*'’ and ‘'['’).  This is
     useful if you want to match an arbitrary literal string that may
     have special characters in it.  Special characters in drive/UNC
     sharepoints are not escaped, e.g.  on Windows ‘escape('//?/c:/Quo
     vadis?.txt')’ returns ‘'//?/c:/Quo vadis[?].txt'’.

     3.4 版新加入.

For example, 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(): 8a. 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/']

If the directory contains files starting with ‘.’ they won’t be matched
by default.  For example, consider a directory containing ‘card.gif’ and
‘.card.gif’:

     >>> import glob
     >>> glob.glob('*.gif')
     ['card.gif']
     >>> glob.glob('.c*')
     ['.card.gif']

也參考
......

Module *note fnmatch: 81.

     Shell-style filename (not path) expansion

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/glob.py


File: python.info,  Node: fnmatch --- Unix filename pattern matching,  Next: linecache --- Random access to text lines,  Prev: glob --- Unix style pathname pattern expansion,  Up: 檔案與目錄存取

5.11.8 ‘fnmatch’ — Unix filename pattern matching
-------------------------------------------------

`Source code:' 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: de. module).  The special characters used in shell-style wildcards
are:

Pattern          Meaning
                 
----------------------------------------------------------
                 
‘*’              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: 8a. for pathname expansion (*note
glob: 8a. uses *note filter(): 1c81. to match pathname segments).
Similarly, filenames starting with a period are not special for this
module, and are matched by the ‘*’ and ‘?’ patterns.

 -- 函式: fnmatch.fnmatch (filename, pattern)

     Test whether the `filename' string matches the `pattern' string,
     returning *note True: 49e. or *note False: 38d.  Both parameters
     are case-normalized using *note os.path.normcase(): 1bf6.  *note
     fnmatchcase(): 1c82. 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 (filename, pattern)

     Test whether `filename' matches `pattern', returning *note True:
     49e. or *note False: 38d.; the comparison is case-sensitive and
     does not apply *note os.path.normcase(): 1bf6.

 -- 函式: fnmatch.filter (names, pattern)

     Construct a list from those elements of the iterable `names' that
     match `pattern'.  It is the same as ‘[n for n in names if
     fnmatch(n, pattern)]’, but implemented more efficiently.

 -- 函式: fnmatch.translate (pattern)

     Return the shell-style `pattern' converted to a regular expression
     for using with *note re.match(): bb8.

     Example:

          >>> 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'>

也參考
......

Module *note glob: 8a.

     Unix shell-style path expansion.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/fnmatch.py


File: python.info,  Node: linecache --- Random access to text lines,  Next: shutil --- High-level file operations,  Prev: fnmatch --- Unix filename pattern matching,  Up: 檔案與目錄存取

5.11.9 ‘linecache’ — Random access to text lines
------------------------------------------------

`Source code:' Lib/linecache.py(1)

__________________________________________________________________

The *note linecache: a9. 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: 114. module to retrieve source lines for
inclusion in the formatted traceback.

The *note tokenize.open(): 1c85. function is used to open files.  This
function uses *note tokenize.detect_encoding(): 1c86. to get the
encoding of the file; in the absence of an encoding token, the file
encoding defaults to UTF-8.

The *note linecache: a9. 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(): 70e.

 -- 函式: 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(): 70e. 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 版新加入.

Example:

     >>> import linecache
     >>> linecache.getline(linecache.__file__, 8)
     'import sys\n'

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/linecache.py

   (2) https://www.python.org/dev/peps/pep-0302


File: python.info,  Node: shutil --- High-level file operations,  Prev: linecache --- Random access to text lines,  Up: 檔案與目錄存取

5.11.10 ‘shutil’ — High-level file operations
---------------------------------------------

`Source code:' Lib/shutil.py(1)

__________________________________________________________________

The *note shutil: ea. 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: c5. module.

     警告: Even the higher-level file copying functions (*note
     shutil.copy(): 25a, *note shutil.copy2(): 25b.) 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.8/Lib/shutil.py


File: python.info,  Node: Directory and files operations,  Next: Archiving operations,  Up: shutil --- High-level file operations

5.11.10.1 Directory and files operations
........................................

 -- 函式: shutil.copyfileobj (fsrc, fdst[, length])

     Copy the contents of the file-like object `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 path-like objects or path names given as
     strings.

     `dst' must be the complete target file name; look at *note copy():
     25a. for a copy that accepts a target directory path.  If `src' and
     `dst' specify the same file, *note SameFileError: 8b8. is raised.

     The destination location must be writable; otherwise, an *note
     OSError: 1d4. 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.

     Raises an *note auditing event: e96. ‘shutil.copyfile’ with
     arguments ‘src’, ‘dst’.

     3.3 版更變: *note IOError: 997. used to be raised instead of *note
     OSError: 1d4.  Added `follow_symlinks' argument.  Now returns
     `dst'.

     3.4 版更變: Raise *note SameFileError: 8b8. instead of *note Error:
     8b7.  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: 25f. section.

 -- 例外: shutil.SameFileError

     This exception is raised if source and destination in *note
     copyfile(): 259. 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 path-like
     objects or path names given as strings.  If `follow_symlinks' is
     false, and both `src' and `dst' are symbolic links, *note
     copymode(): 1c8d. 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(): a7c. for
     more information.  If *note copymode(): 1c8d. cannot modify
     symbolic links on the local platform, and it is asked to do so, it
     will do nothing and return.

     Raises an *note auditing event: e96. ‘shutil.copymode’ with
     arguments ‘src’, ‘dst’.

     3.3 版更變: Added `follow_symlinks' argument.

 -- 函式: 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(): a7c.
     also copies the "extended attributes" where possible.  The file
     contents, owner, and group are unaffected.  `src' and `dst' are
     path-like objects or path names given as strings.

     If `follow_symlinks' is false, and `src' and `dst' both refer to
     symbolic links, *note copystat(): a7c. 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(): a7c. can modify the permission bits of
               a symbolic link.

             * If ‘os.utime in os.supports_follow_symlinks’ is ‘True’,
               *note copystat(): a7c. can modify the last access and
               modification times of a symbolic link.

             * If ‘os.chflags in os.supports_follow_symlinks’ is ‘True’,
               *note copystat(): a7c. 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(): a7c. will copy everything it can.  *note
          copystat(): a7c. never returns failure.

          Please see *note os.supports_follow_symlinks: 1c8e. for more
          information.

     Raises an *note auditing event: e96. ‘shutil.copystat’ with
     arguments ‘src’, ‘dst’.

     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: 36f. or strings.  If `dst'
     specifies a directory, the file will be copied into `dst' using the
     base filename from `src'.  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(): 25a. copies the file data and the file’s permission
     mode (see *note os.chmod(): a38.).  Other metadata, like the file’s
     creation and modification times, is not preserved.  To preserve all
     file metadata from the original, use *note copy2(): 25b. instead.

     Raises an *note auditing event: e96. ‘shutil.copyfile’ with
     arguments ‘src’, ‘dst’.

     Raises an *note auditing event: e96. ‘shutil.copymode’ with
     arguments ‘src’, ‘dst’.

     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: 25f. section.

 -- 函式: shutil.copy2 (src, dst, *, follow_symlinks=True)

     Identical to *note copy(): 25a. except that *note copy2(): 25b.
     also attempts to preserve file metadata.

     When `follow_symlinks' is false, and `src' is a symbolic link,
     *note copy2(): 25b. 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(): 25b. will preserve all the metadata it can; *note copy2():
     25b. never raises an exception because it cannot preserve file
     metadata.

     *note copy2(): 25b. uses *note copystat(): a7c. to copy the file
     metadata.  Please see *note copystat(): a7c. for more information
     about platform support for modifying symbolic link metadata.

     Raises an *note auditing event: e96. ‘shutil.copyfile’ with
     arguments ‘src’, ‘dst’.

     Raises an *note auditing event: e96. ‘shutil.copystat’ with
     arguments ‘src’, ‘dst’.

     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: 25f. section.

 -- 函式: shutil.ignore_patterns (*patterns)

     This factory function creates a function that can be used as a
     callable for *note copytree(): 21b.’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.
     `dirs_exist_ok' dictates whether to raise an exception in case
     `dst' or any missing parent directory already exists.

     Permissions and times of directories are copied with *note
     copystat(): a7c, individual files are copied using *note copy2():
     25b.

     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 by the symlink
     doesn’t exist, an exception will be added in the list of errors
     raised in an *note Error: 8b7. 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(): a40.

     If `ignore' is given, it must be a callable that will receive as
     its arguments the directory being visited by *note copytree(): 21b,
     and a list of its contents, as returned by *note os.listdir(): a46.
     Since *note copytree(): 21b. 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(): 1c8f. can be used to create such
     a callable that ignores names based on glob-style patterns.

     If exception(s) occur, an *note Error: 8b7. 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(): 25b.
     is used, but any function that supports the same signature (like
     *note copy(): 25a.) can be used.

     Raises an *note auditing event: e96. ‘shutil.copytree’ with
     arguments ‘src’, ‘dst’.

     3.3 版更變: Copy metadata when `symlinks' is false.  Now returns
     `dst'.

     3.2 版更變: Added the `copy_function' argument to be able to
     provide a custom copy function.  Added the
     `ignore_dangling_symlinks' argument to silent dangling symlinks
     errors when `symlinks' is false.

     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: 25f. section.

     3.8 版新加入: The `dirs_exist_ok' parameter.

 -- 函式: shutil.rmtree (path, ignore_errors=False, onerror=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 `onerror' or, if that is omitted, they raise an
     exception.

          備註: On platforms that support the necessary fd-based
          functions a symlink attack resistant version of *note
          rmtree(): 21d. is used by default.  On other platforms, the
          *note rmtree(): 21d. 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: 1c90.
          function attribute to determine which case applies.

     If `onerror' 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', will be the exception
     information returned by *note sys.exc_info(): c64.  Exceptions
     raised by `onerror' will not be caught.

     Raises an *note auditing event: e96. ‘shutil.rmtree’ with argument
     ‘path’.

     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.

      -- 屬性: rmtree.avoids_symlink_attacks

          Indicates whether the current platform and implementation
          provides a symlink attack resistant version of *note rmtree():
          21d.  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
     (`dst') and return the destination.

     If the destination is an existing directory, then `src' is moved
     inside that directory.  If the destination already exists but is
     not a directory, it may be overwritten depending on *note
     os.rename(): a3d. semantics.

     If the destination is on the current filesystem, then *note
     os.rename(): a3d. is used.  Otherwise, `src' is copied to `dst'
     using `copy_function' and then removed.  In case of symlinks, a new
     symlink pointing to the target of `src' will be created in or as
     `dst' and `src' will be removed.

     If `copy_function' is given, it must be a callable that takes two
     arguments `src' and `dst', and will be used to copy `src' to `dst'
     if *note os.rename(): a3d. cannot be used.  If the source is a
     directory, *note copytree(): 21b. is called, passing it the
     ‘copy_function()’.  The default `copy_function' is *note copy2():
     25b.  Using *note copy(): 25a. 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.

     Raises an *note auditing event: e96. ‘shutil.move’ with arguments
     ‘src’, ‘dst’.

     3.3 版更變: Added explicit symlink handling for foreign
     filesystems, thus adapting it to the behavior of GNU’s ‘mv’.  Now
     returns `dst'.

     3.5 版更變: Added the `copy_function' keyword argument.

     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: 25f. section.

 -- 函式: shutil.disk_usage (path)

     Return disk usage statistics about the given path as a *note named
     tuple: aa8. 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.

     3.3 版新加入.

     3.8 版更變: On Windows, `path' can now be a file or directory.

     *note Availability: 1364.: Unix, Windows.

 -- 函式: shutil.chown (path, user=None, group=None)

     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(): a39, the underlying function.

     Raises an *note auditing event: e96. ‘shutil.chown’ with arguments
     ‘path’, ‘user’, ‘group’.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: 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(): a36, by
     default determining if the file exists and executable.

     When no `path' is specified, the results of *note os.environ():
     b3c. are used, returning either the "PATH" value or a fallback of
     *note os.defpath: fe4.

     On Windows, the current directory is always prepended to the `path'
     whether or not you use the default or provide your own, which is
     the behavior the command shell uses when finding executables.
     Additionally, when finding the `cmd' in the `path', the ‘PATHEXT’
     environment variable is checked.  For example, if you call
     ‘shutil.which("python")’, *note which(): edf. 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'

     3.3 版新加入.

     3.8 版更變: The *note bytes: 336. type is now accepted.  If `cmd'
     type is *note bytes: 336, the result type is also *note bytes: 336.

 -- 例外: shutil.Error

     This exception collects exceptions that are raised during a
     multi-file operation.  For *note copytree(): 21b, the exception
     argument is a list of 3-tuples (`srcname', `dstname', `exception').

* Menu:

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


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(): 259, *note copy(): 25a, *note copy2(): 25b, *note
copytree(): 21b, and *note move(): 25c.) 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(): 35e. is used.

On Windows *note shutil.copyfile(): 259. uses a bigger default buffer
size (1 MiB instead of 64 KiB) and a *note memoryview(): 25d.-based
variant of *note shutil.copyfileobj(): 25e. 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(): 25e. function internally.

3.8 版更變.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33671

   (2) http://www.manpagez.com/man/3/copyfile/


File: python.info,  Node: copytree example,  Next: rmtree example,  Prev: Platform-dependent efficient copy operations,  Up: Directory and files operations

5.11.10.3 copytree example
..........................

This example is the implementation of the *note copytree(): 21b.
function, described above, with the docstring omitted.  It demonstrates
many of the other functions provided by this module.

     def copytree(src, dst, symlinks=False):
         names = os.listdir(src)
         os.makedirs(dst)
         errors = []
         for name in names:
             srcname = os.path.join(src, name)
             dstname = os.path.join(dst, name)
             try:
                 if symlinks and os.path.islink(srcname):
                     linkto = os.readlink(srcname)
                     os.symlink(linkto, dstname)
                 elif os.path.isdir(srcname):
                     copytree(srcname, dstname, symlinks)
                 else:
                     copy2(srcname, dstname)
                 # XXX What about devices, sockets etc.?
             except OSError as why:
                 errors.append((srcname, dstname, str(why)))
             # catch the Error from the recursive copytree so that we can
             # continue with other files
             except Error as err:
                 errors.extend(err.args[0])
         try:
             copystat(src, dst)
         except OSError as why:
             # can't copy file access times on Windows
             if why.winerror is None:
                 errors.extend((src, dst, str(why)))
         if errors:
             raise Error(errors)

Another example that uses the *note ignore_patterns(): 1c8f. 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 example,  Prev: copytree example,  Up: Directory and files operations

5.11.10.4 rmtree example
........................

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 onerror 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, onerror=remove_readonly)


File: python.info,  Node: Archiving operations,  Next: Querying the size of the output terminal,  Prev: Directory and files operations,  Up: shutil --- High-level file operations

5.11.10.5 Archiving operations
..............................

3.2 版新加入.

3.5 版更變: Added support for the `xztar' format.

High-level utilities to create and read compressed and archived files
are also provided.  They rely on the *note zipfile: 143. and *note
tarfile: 102. 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: 145. module is available),
     "tar", "gztar" (if the *note zlib: 145. module is available),
     "bztar" (if the *note bz2: 14. module is available), or "xztar" (if
     the *note lzma: ae. 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: 1c97. 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: 3ac.

     The `verbose' argument is unused and deprecated.

     Raises an *note auditing event: e96. ‘shutil.make_archive’ with
     arguments ‘base_name’, ‘format’, ‘root_dir’, ‘base_dir’.

     3.8 版更變: The modern pax (POSIX.1-2001) format is now used
     instead of the legacy GNU format for archives created with
     ‘format="tar"’.

 -- 函式: 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: ea. provides these formats:

        - `zip': ZIP file (if the *note zlib: 145. 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: 145. module is
          available).

        - `bztar': bzip2’ed tar-file (if the *note bz2: 14. module is
          available).

        - `xztar': xz’ed tar-file (if the *note lzma: ae. module is
          available).

     You can register new formats or provide your own archiver for any
     existing formats, by using *note register_archive_format(): 1c99.

 -- 函式: 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:
     1bf7.) to start archiving from.  Further arguments are passed as
     keyword arguments: `owner', `group', `dry_run' and `logger' (as
     passed in *note make_archive(): 21c.).

     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(): 1c98. which
     returns the list of archivers.  Defaults to an empty string.

 -- 函式: shutil.unregister_archive_format (name)

     Remove the archive format `name' from the list of supported
     formats.

 -- 函式: shutil.unpack_archive (filename[, extract_dir[, format]])

     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(): 1c9b.  If not provided, *note
     unpack_archive(): b9c. 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: 1fc. is raised.

     Raises an *note auditing event: e96. ‘shutil.unpack_archive’ with
     arguments ‘filename’, ‘extract_dir’, ‘format’.

     3.7 版更變: Accepts a *note path-like object: 36f. for `filename'
     and `extract_dir'.

 -- 函式: 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, followed by the
     directory the archive must be extracted to.

     When provided, `extra_args' is a sequence of ‘(name, value)’ tuples
     that will be passed as keywords arguments to the callable.

     `description' can be provided to describe the format, and will be
     returned by the *note get_unpack_formats(): 1c9c. 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: ea. 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: 145. module is
          available).

        - `bztar': bzip2’ed tar-file (if the *note bz2: 14. module is
          available).

        - `xztar': xz’ed tar-file (if the *note lzma: ae. module is
          available).

     You can register new formats or provide your own unpacker for any
     existing formats, by using *note register_unpack_format(): 1c9b.

* Menu:

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

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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: 1c9f, we show how to
use *note make_archive(): 21c, 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 --- High-level file operations

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__: 1ca2. is queried by
     invoking *note os.get_terminal_size(): a4e.

     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:
     1ca3.

     See also: The Single UNIX Specification, Version 2, Other
     Environment Variables(1).

     3.3 版新加入.

也參考
......

Module *note os: c5.

     Operating system interfaces, including functions to work with files
     at a lower level than Python *note file objects: b47.

Module *note io: a2.

     Python’s built-in I/O library, including both abstract classes and
     some concrete classes such as file I/O.

Built-in function *note open(): 4f5.

     The standard way to open files for reading and writing with Python.

   ---------- Footnotes ----------

   (1) 
http://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: cb. and *note marshal: b1.
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.

The list of modules described in this chapter is:

* Menu:

* pickle: pickle --- Python object serialization. Python object serialization
* copyreg: copyreg --- Register pickle support functions. Register pickle support functions
* shelve: shelve --- Python object persistence. Python object persistence
* marshal: marshal --- Internal Python object serialization. Internal Python object serialization
* dbm: dbm --- Interfaces to Unix "databases". Interfaces to Unix "databases"
* sqlite3: sqlite3 --- DB-API 2 0 interface for SQLite databases. DB-API 2.0 interface for SQLite databases


File: python.info,  Node: pickle --- Python object serialization,  Next: copyreg --- Register pickle support functions,  Up: Data Persistence

5.12.1 ‘pickle’ — Python object serialization
---------------------------------------------

`Source code:' Lib/pickle.py(1)

__________________________________________________________________

The *note pickle: cb. 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: 1caa. or *note bytes-like object:
5ed.) 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: 8f. if you need to ensure
     that it has not been tampered with.

     Safer serialization formats such as *note json: a5. may be more
     appropriate if you are processing untrusted data.  See *note
     Comparison with json: 1cab.

* Menu:

* Relationship to other Python modules::
* Data stream format::
* Module Interface::
* 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>.
* Examples: Examples<4>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/pickle.py

   (2) (1) Don’t confuse this with the *note marshal: b1. module


File: python.info,  Node: Relationship to other Python modules,  Next: Data stream format,  Up: pickle --- Python object serialization

5.12.1.1 Relationship to other Python modules
.............................................

* Menu:

* Comparison with marshal::
* Comparison with json::


File: python.info,  Node: Comparison with marshal,  Next: Comparison with json,  Up: Relationship to other Python modules

5.12.1.2 Comparison with ‘marshal’
..................................

Python has a more primitive serialization module called *note marshal:
b1, but in general *note pickle: cb. should always be the preferred way
to serialize Python objects.  *note marshal: b1. exists primarily to
support Python’s ‘.pyc’ files.

The *note pickle: cb. module differs from *note marshal: b1. in several
significant ways:

   * The *note pickle: cb. 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: b1. 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: cb. 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: b1. cannot be used to serialize user-defined classes
     and their instances.  *note pickle: cb. 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: b1. 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: cb.
     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: Comparison with json,  Prev: Comparison with marshal,  Up: Relationship to other Python modules

5.12.1.3 Comparison with ‘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 is human-readable, while pickle is not;

   * 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: 1caf.);

   * Unlike pickle, deserializing untrusted JSON does not in itself
     create an arbitrary code execution vulnerability.

也參考
......

The *note json: a5. module: a standard library module allowing JSON
serialization and deserialization.

   ---------- Footnotes ----------

   (1) http://json.org


File: python.info,  Node: Data stream format,  Next: Module Interface,  Prev: Relationship to other Python modules,  Up: pickle --- Python object serialization

5.12.1.4 Data stream format
...........................

The data format used by *note pickle: cb. is Python-specific.  This has
the advantage that there are no restrictions imposed by external
standards such as JSON or XDR (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: cb. data format uses a relatively compact
binary representation.  If you need optimal size characteristics, you
can efficiently *note compress: 1cb1. pickled data.

The module *note pickletools: cc. contains tools for analyzing data
streams generated by *note pickle: cb.  *note pickletools: cc. 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 class: 1cb2.es.  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: 336. 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: cb. 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: cb. 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: e8. module provides a simple
     interface to pickle and unpickle objects on DBM-style database
     files.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0307

   (2) https://www.python.org/dev/peps/pep-3154

   (3) https://www.python.org/dev/peps/pep-0574


File: python.info,  Node: Module Interface,  Next: What can be pickled and unpickled?,  Prev: Data stream format,  Up: pickle --- Python object serialization

5.12.1.5 Module Interface
.........................

To serialize an object hierarchy, you simply call the *note dumps():
e04. function.  Similarly, to de-serialize a data stream, you call the
*note loads(): 5c8. function.  However, if you want more control over
serialization and de-serialization, you can create a *note Pickler: 20e.
or an *note Unpickler: 1cb4. object, respectively.

The *note pickle: cb. module provides the following constants:

 -- Data: pickle.HIGHEST_PROTOCOL

     An integer, the highest *note protocol version: 573. available.
     This value can be passed as a `protocol' value to functions *note
     dump(): 1cb5. and *note dumps(): e04. as well as the *note Pickler:
     20e. constructor.

 -- Data: pickle.DEFAULT_PROTOCOL

     An integer, the default *note protocol version: 573. used for
     pickling.  May be less than *note HIGHEST_PROTOCOL: e05.  Currently
     the default protocol is 4, first introduced in Python 3.4 and
     incompatible with previous versions.

     3.0 版更變: The default protocol is 3.

     3.8 版更變: The default protocol is 4.

The *note pickle: cb. 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: b47. `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: 20e. constructor.

     3.8 版更變: The `buffer_callback' argument was added.

 -- 函式: pickle.dumps (obj, protocol=None, *, fix_imports=True,
          buffer_callback=None)

     Return the pickled representation of the object `obj' as a *note
     bytes: 336. object, instead of writing it to a file.

     Arguments `protocol', `fix_imports' and `buffer_callback' have the
     same meaning as in the *note Pickler: 20e. constructor.

     3.8 版更變: The `buffer_callback' argument was added.

 -- 函式: 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: b47. `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: 1cb4.
     constructor.

     3.8 版更變: The `buffers' argument was added.

 -- 函式: 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: 5ed.

     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: 1cb4.
     constructor.

     3.8 版更變: The `buffers' argument was added.

The *note pickle: cb. module defines three exceptions:

 -- 例外: pickle.PickleError

     Common base class for the other pickling exceptions.  It inherits
     *note Exception: 1aa.

 -- 例外: pickle.PicklingError

     Error raised when an unpicklable object is encountered by *note
     Pickler: 20e.  It inherits *note PickleError: 1cb7.

     Refer to *note What can be pickled and unpickled?: 1cb9. 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 *note
     PickleError: 1cb7.

     Note that other exceptions may also be raised during unpickling,
     including (but not necessarily limited to) AttributeError,
     EOFError, ImportError, and IndexError.

The *note pickle: cb. module exports three classes, *note Pickler: 20e,
*note Unpickler: 1cb4. and *note PickleBuffer: 1cbb.:

 -- 類別: 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: e05.  If not specified, the default is *note
     DEFAULT_PROTOCOL: 1cb6.  If a negative number is specified, *note
     HIGHEST_PROTOCOL: e05. 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: 7a0. 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: 1cbc.;
     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 版更變: The `buffer_callback' argument was added.

      -- 成員函式: 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(): 1cbd. returns ‘None’, `obj' is
          pickled as usual.  Any other value causes *note Pickler: 20e.
          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(): 1cbe.  Note that the value
          returned by *note persistent_id(): 1cbd. cannot itself have a
          persistent ID.

          See *note Persistence of External Objects: 1cbf. for details
          and examples of uses.

      -- 屬性: 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(): 1cc0.  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__():
          19c. method.

          By default, a pickler object will not have a *note
          dispatch_table: a6e. attribute, and it will instead use the
          global dispatch table managed by the *note copyreg: 27.
          module.  However, to customize the pickling for a specific
          pickler object one can set the *note dispatch_table: a6e.
          attribute to a dict-like object.  Alternatively, if a subclass
          of *note Pickler: 20e. has a *note dispatch_table: a6e.
          attribute then this will be used as the default dispatch table
          for instances of that class.

          See *note Dispatch Tables: 1cc1. for usage examples.

          3.3 版新加入.

      -- 成員函式: reducer_override (self, obj)

          Special reducer that can be defined in *note Pickler: 20e.
          subclasses.  This method has priority over any reducer in the
          *note dispatch_table: a6e.  It should conform to the same
          interface as a *note __reduce__(): 19c. method, and can
          optionally return ‘NotImplemented’ to fallback on *note
          dispatch_table: a6e.-registered reducers to pickle ‘obj’.

          For a detailed example, see *note Custom Reduction for Types,
          Functions, and Other Objects: 1cc2.

          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: 20e. to recurse
          infinitely.

          Use *note pickletools.optimize(): 1cc4. 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: 58d. interface.  Thus `file' can be an
     on-disk file opened for binary reading, an *note io.BytesIO: 7a0.
     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: 195, *note date: 194. and *note time:
     4f8. 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:
     20e. was instantiated (or when *note dump(): 1cb5. or *note
     dumps(): e04. 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: 1cbc. buffer view.  Such buffers
     have been given in order to the `buffer_callback' of a Pickler
     object.

     3.8 版更變: The `buffers' argument was added.

      -- 成員函式: 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: 1cba. by default.

          If defined, *note persistent_load(): 1cbe. should return the
          object specified by the persistent ID `pid'.  If an invalid
          persistent ID is encountered, an *note UnpicklingError: 1cba.
          should be raised.

          See *note Persistence of External Objects: 1cbf. for details
          and examples of uses.

      -- 成員函式: 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: 335. objects.  Note, unlike its name suggests,
          *note find_class(): 1cc6. 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: 1cc7. for
          details.

          Raises an *note auditing event: e96. ‘pickle.find_class’ with
          arguments ‘module’, ‘name’.

 -- 類別: pickle.PickleBuffer (buffer)

     A wrapper for a buffer representing picklable data.  `buffer' must
     be a *note buffer-providing: 15ec. object, such as a *note
     bytes-like object: 5ed. or a N-dimensional array.

     *note PickleBuffer: 1cbb. is itself a buffer provider, therefore it
     is possible to pass it to other APIs expecting a buffer-providing
     object, such as *note memoryview: 25d.

     *note PickleBuffer: 1cbb. objects can only be serialized using
     pickle protocol 5 or higher.  They are eligible for *note
     out-of-band serialization: 1cbc.

     3.8 版新加入.

      -- 成員函式: raw ()

          Return a *note memoryview: 25d. of the memory area underlying
          this buffer.  The returned object is a one-dimensional,
          C-contiguous memoryview with format ‘B’ (unsigned bytes).
          *note BufferError: 1705. 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: Module Interface,  Up: pickle --- Python object serialization

5.12.1.6 What can be pickled and unpickled?
...........................................

The following types can be pickled:

   * ‘None’, ‘True’, and ‘False’

   * integers, floating point numbers, complex numbers

   * strings, bytes, bytearrays

   * tuples, lists, sets, and dictionaries containing only picklable
     objects

   * functions defined at the top level of a module (using *note def:
     dc3, not *note lambda: c34.)

   * built-in functions defined at the top level of a module

   * classes that are defined at the top level of a module

   * instances of such classes whose *note __dict__: 501. or the result
     of calling *note __getstate__(): e06. is picklable (see section
     *note Pickling Class Instances: 1caf. for details).

Attempts to pickle unpicklable objects will raise the *note
PicklingError: 1cb8. 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: 639. will be raised in this
case.  You can carefully raise this limit with *note
sys.setrecursionlimit(): e80.

Note that functions (built-in and user-defined) are pickled by "fully
qualified" name reference, not by value.  (1) This means that only the
function name is pickled, along with the name of the module the function
is defined in.  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 named reference, 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 in 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__(): 19d. method.

   ---------- Footnotes ----------

   (1) (2) This is why *note lambda: c34. functions cannot be pickled:
all ‘lambda’ functions share the same name: ‘<lambda>’.

   (2) (3) The exception raised will likely be an *note ImportError:
339. or an *note AttributeError: 3a0. 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 object serialization

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__(): d63. 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 load(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__(): 1ccc. method can dictate the values passed to
     the *note __new__(): 88e. 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__(): 88e. method upon unpickling.

     You should implement this method if the *note __new__(): 88e.
     method of your class requires keyword-only arguments.  Otherwise,
     it is recommended for compatibility to implement *note
     __getnewargs__(): 6b3.

     3.6 版更變: *note __getnewargs_ex__(): 1ccc. is now used in
     protocols 2 and 3.

 -- 成員函式: object.__getnewargs__ ()

     This method serves a similar purpose as *note __getnewargs_ex__():
     1ccc, but supports only positional arguments.  It must return a
     tuple of arguments ‘args’ which will be passed to the *note
     __new__(): 88e. method upon unpickling.

     *note __getnewargs__(): 6b3. will not be called if *note
     __getnewargs_ex__(): 1ccc. is defined.

     3.6 版更變: Before Python 3.6, *note __getnewargs__(): 6b3. was
     called instead of *note __getnewargs_ex__(): 1ccc. in protocols 2
     and 3.

 -- 成員函式: object.__getstate__ ()

     Classes can further influence how their instances are pickled; if
     the class defines the method *note __getstate__(): e06, it is
     called and the returned object is pickled as the contents for the
     instance, instead of the contents of the instance’s dictionary.  If
     the *note __getstate__(): e06. method is absent, the instance’s
     *note __dict__: 501. is pickled as usual.

 -- 成員函式: object.__setstate__ (state)

     Upon unpickling, if the class defines *note __setstate__(): 19d, 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 __getstate__(): e06. returns a false value, the
          *note __setstate__(): 19d. method will not be called upon
          unpickling.

Refer to the section *note Handling Stateful Objects: 1ccd. for more
information about how to use the methods *note __getstate__(): e06. and
*note __setstate__(): 19d.

     備註: At unpickling time, some methods like *note __getattr__():
     31f, *note __getattribute__(): 44e, or *note __setattr__(): e31.
     may be called upon the instance.  In case those methods rely on
     some internal invariant being true, the type should implement *note
     __new__(): 88e. to establish such an invariant, as *note
     __init__(): d63. 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__(): 19c. 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__(): 19c. directly in
your classes is error prone.  For this reason, class designers should
use the high-level interface (i.e., *note __getnewargs_ex__(): 1ccc,
*note __getstate__(): e06. and *note __setstate__(): 19d.) whenever
possible.  We will show, however, cases where using *note __reduce__():
19c. is the only option or leads to more efficient pickling or both.

 -- 成員函式: object.__reduce__ ()

     The interface is currently defined as follows.  The *note
     __reduce__(): 19c. 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__(): 19d. 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__: 501. 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 ‘append()’ and ‘extend()’ methods 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__(): c67.

        * 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__(): 19d. method.  If not
          ‘None’, this callable will have priority over ‘obj’’s *note
          __setstate__(): 19d.

          3.8 版新加入: The optional sixth tuple item, ‘(obj, state)’,
          was added.

 -- 成員函式: object.__reduce_ex__ (protocol)

     Alternatively, a *note __reduce_ex__(): 1a01. 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__(): 19c. method.  In addition,
     *note __reduce__(): 19c. 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) (4) The *note copy: 26. 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: cb. 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: cb. module; it will delegate this resolution to the user-defined
methods on the pickler and unpickler, *note persistent_id(): 1cbd. and
*note persistent_load(): 1cbe. respectively.

To pickle objects that have an external persistent ID, the pickler must
have a custom *note persistent_id(): 1cbd. 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(): 1cbe. 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) (5) The limitation on alphanumeric characters is due to the fact
the persistent IDs, in protocol 0, are delimited by the newline
character.  Therefore if any kind of newline characters occurs in
persistent IDs, the resulting pickle 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: 27. 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.

For example

     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: 20e. 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 same dispatch table.  The equivalent code using the *note copyreg:
27. module is

     copyreg.pickle(SomeClass, reduce_SomeClass)
     f = io.BytesIO()
     p = pickle.Pickler(f)


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 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 *note
__setstate__(): 19d. and *note __getstate__(): e06. 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 object serialization

5.12.1.11 Custom Reduction for Types, Functions, and Other Objects
..................................................................

3.8 版新加入.

Sometimes, *note dispatch_table: a6e. 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: 20e.
class and implement a *note reducer_override(): 20f. method.  This
method can return an arbitrary reduction tuple (see *note __reduce__():
19c.).  It can alternatively return ‘NotImplemented’ to fallback to the
traditional behavior.

If both the *note dispatch_table: a6e. and *note reducer_override():
20f. are defined, then *note reducer_override(): 20f. method takes
priority.

     備註: For performance reasons, *note reducer_override(): 20f. may
     not be called for the following objects: ‘None’, ‘True’, ‘False’,
     and exact instances of *note int: 185, *note float: 188, *note
     bytes: 336, *note str: 335, *note dict: 1b9, *note set: b74, *note
     frozenset: bf3, *note list: 263. and *note tuple: 483.

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 object serialization

5.12.1.12 Out-of-band Buffers
.............................

3.8 版新加入.

In some contexts, the *note pickle: cb. 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: cb. 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::
* Example: Example<4>.


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__(): 1a01. method specialized for protocol 5 and higher,
which returns a *note PickleBuffer: 1cbb. instance (instead of e.g.  a
*note bytes: 336. object) for any large data.

A *note PickleBuffer: 1cbb. 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: cb. module.  However,
consumers can also opt-in to tell *note pickle: cb. that they will
handle those buffers by themselves.


File: python.info,  Node: Consumer API,  Next: Example<4>,  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: 1cbb. objects generated when serializing an object graph.

On the sending side, it needs to pass a `buffer_callback' argument to
*note Pickler: 20e. (or to the *note dump(): 1cb5. or *note dumps():
e04. function), which will be called with each *note PickleBuffer: 1cbb.
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: 1cb4. (or to the *note load(): 5c7. or *note loads(): 5c8.
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: 1cbb. 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: Example<4>,  Prev: Consumer API,  Up: Out-of-band Buffers

5.12.1.15 Example
.................

Here is a trivial example where we implement a *note bytearray: 337.
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: 337. allocates
its own memory: you cannot create a *note bytearray: 337. 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://www.python.org/dev/peps/pep-0574


File: python.info,  Node: Restricting Globals,  Next: Performance<2>,  Prev: Out-of-band Buffers,  Up: pickle --- Python object serialization

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(): dc6.
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(): 1cc6.  Unlike its name
suggests, *note Unpickler.find_class(): 1cc6. 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: 13. 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 has 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: 140. or
third-party solutions.


File: python.info,  Node: Performance<2>,  Next: Examples<4>,  Prev: Restricting Globals,  Up: pickle --- Python object serialization

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: cb. module has a transparent
optimizer written in C.


File: python.info,  Node: Examples<4>,  Prev: Performance<2>,  Up: pickle --- Python object serialization

5.12.1.18 Examples
..................

For the simplest code, use the *note dump(): 1cb5. and *note load():
5c7. functions.

     import pickle

     # An arbitrary collection of objects supported by pickle.
     data = {
         'a': [1, 2.0, 3, 4+6j],
         '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)

也參考
......

Module *note copyreg: 27.

     Pickle interface constructor registration for extension types.

Module *note pickletools: cc.

     Tools for working with and analyzing pickled data.

Module *note shelve: e8.

     Indexed databases of objects; uses *note pickle: cb.

Module *note copy: 26.

     Shallow and deep object copying.

Module *note marshal: b1.

     High-performance serialization of built-in types.

註解
....


File: python.info,  Node: copyreg --- Register pickle support functions,  Next: shelve --- Python object persistence,  Prev: pickle --- Python object serialization,  Up: Data Persistence

5.12.2 ‘copyreg’ — Register ‘pickle’ support functions
------------------------------------------------------

`Source code:' Lib/copyreg.py(1)

__________________________________________________________________

The *note copyreg: 27. module offers a way to define functions used
while pickling specific objects.  The *note pickle: cb. and *note copy:
26. modules use those functions when pickling/copying those objects.
The module provides configuration information about object constructors
which are not classes.  Such constructors may be factory functions or
class instances.

 -- 函式: copyreg.constructor (object)

     Declares `object' to be a valid constructor.  If `object' is not
     callable (and hence not valid as a constructor), raises *note
     TypeError: 193.

 -- 函式: copyreg.pickle (type, function, constructor=None)

     Declares that `function' should be used as a "reduction" function
     for objects of type `type'.  `function' should return either a
     string or a tuple containing two or three elements.

     The optional `constructor' parameter, if provided, is a callable
     object which can be used to reconstruct the object when called with
     the tuple of arguments returned by `function' at pickling time.
     *note TypeError: 193. will be raised if `object' is a class or
     `constructor' is not callable.

     See the *note pickle: cb. module for more details on the interface
     expected of `function' and `constructor'.  Note that the *note
     dispatch_table: a6e. attribute of a pickler object or subclass of
     *note pickle.Pickler: 20e. can also be used for declaring reduction
     functions.

* Menu:

* Example: Example<5>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/copyreg.py


File: python.info,  Node: Example<5>,  Up: copyreg --- Register pickle support functions

5.12.2.1 Example
................

The example below would like to show how to register a pickle function
and how it will be used:

     >>> import copyreg, copy, pickle
     >>> class C(object):
     ...     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 --- Internal Python object serialization,  Prev: copyreg --- Register pickle support functions,  Up: Data Persistence

5.12.3 ‘shelve’ — Python object persistence
-------------------------------------------

`Source code:' 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:
cb. 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(): 835.

     By default, version 3 pickles 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
     Example: 1ce1.).  If the optional `writeback' parameter is set to
     ‘True’, all entries accessed are also cached in memory, and written
     back on *note sync(): 1ce2. and *note close(): 1ce3.; 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).

          備註: Do not rely on the shelf being closed automatically;
          always call *note close(): 1ce3. explicitly when you don’t
          need it any more, or use *note shelve.open(): 1ce0. as a
          context manager:

               with shelve.open('spam') as db:
                   db['eggs'] = 'eggs'

     警告: Because the *note shelve: e8. module is backed by *note
     pickle: cb, it is insecure to load a shelf from an untrusted
     source.  Like with pickle, loading a shelf can execute arbitrary
     code.

Shelf objects support all methods supported by dictionaries.  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: 49e.  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(): 1ce3.

 -- 成員函式: Shelf.close ()

     Synchronize and close the persistent `dict' object.  Operations on
     a closed shelf will fail with a *note ValueError: 1fc.

也參考
......

Persistent dictionary recipe(2) with widely supported storage formats
and having the speed of native dictionaries.

* Menu:

* Restrictions::
* Example: Example<6>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/shelve.py

   (2) https://code.activestate.com/recipes/576642/


File: python.info,  Node: Restrictions,  Next: Example<6>,  Up: shelve --- Python object persistence

5.12.3.1 Restrictions
.....................

   * The choice of which database package will be used (such as *note
     dbm.ndbm: 35. or *note dbm.gnu: 34.) depends on which interface is
     available.  Therefore it is not safe to open the database directly
     using *note dbm: 32.  The database is also (unfortunately) subject
     to the limitations of *note dbm: 32, 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: e8. 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.

 -- 類別: shelve.Shelf (dict, protocol=None, writeback=False,
          keyencoding='utf-8')

     A subclass of *note collections.abc.MutableMapping: 9f4. which
     stores pickled values in the `dict' object.

     By default, version 3 pickles are used to serialize values.  The
     version of the pickle protocol can be specified with the `protocol'
     parameter.  See the *note pickle: cb. 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: 8b5. object can also be used as a context manager,
     in which case it will be automatically closed when the *note with:
     6ee. block ends.

     3.2 版更變: Added the `keyencoding' parameter; previously, keys
     were always encoded in UTF-8.

     3.4 版更變: Added context manager support.

 -- 類別: shelve.BsdDbShelf (dict, protocol=None, writeback=False,
          keyencoding='utf-8')

     A subclass of *note Shelf: 8b5. which exposes ‘first()’, ‘next()’,
     ‘previous()’, ‘last()’ and ‘set_location()’ which 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: 8b5. class.

 -- 類別: shelve.DbfilenameShelf (filename, flag='c', protocol=None,
          writeback=False)

     A subclass of *note Shelf: 8b5. which accepts a `filename' instead
     of a dict-like object.  The underlying file will be opened using
     *note dbm.open(): 835.  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(): 1ce0. function.
     The optional `protocol' and `writeback' parameters have the same
     interpretation as for the *note Shelf: 8b5. class.

   ---------- Footnotes ----------

   (1) https://www.jcea.es/programacion/pybsddb.htm


File: python.info,  Node: Example<6>,  Prev: Restrictions,  Up: shelve --- Python object persistence

5.12.3.2 Example
................

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

也參考
......

Module *note dbm: 32.

     Generic interface to ‘dbm’-style databases.

Module *note pickle: cb.

     Object serialization used by *note shelve: e8.


File: python.info,  Node: marshal --- Internal Python object serialization,  Next: dbm --- Interfaces to Unix "databases",  Prev: shelve --- Python object persistence,  Up: Data Persistence

5.12.4 ‘marshal’ — Internal Python object serialization
-------------------------------------------------------

__________________________________________________________________

This module contains functions that can read and write Python values in
a binary format.  The format is specific to Python, but independent of
machine architecture issues (e.g., you can write a Python value to a
file on a PC, transport the file to a Sun, and read it back there).
Details of the format are undocumented on purpose; it may change between
Python versions (although it rarely does).  (1)

This is not a general "persistence" module.  For general persistence and
transfer of Python objects through RPC calls, see the modules *note
pickle: cb. and *note shelve: e8.  The *note marshal: b1. 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.  If you’re serializing and de-serializing
Python objects, use the *note pickle: cb. module instead – the
performance is comparable, version independence is guaranteed, and
pickle supports a substantially wider range of objects than marshal.

     警告: The *note marshal: b1. module is not intended to be secure
     against erroneous or maliciously constructed data.  Never unmarshal
     data received from an untrusted or unauthenticated source.

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, 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:
158, *note Ellipsis: 1611. and *note StopIteration: 48b. can also be
marshalled and unmarshalled.  For format `version' lower than 3,
recursive lists, sets and dictionaries cannot be written (see below).

There are functions that read/write files as well as functions operating
on bytes-like objects.

The module defines these functions:

 -- 函式: marshal.dump (value, file[, version])

     Write the value on the open file.  The value must be a supported
     type.  The file must be a writeable *note binary file: 1caa.

     If the value has (or contains an object that has) an unsupported
     type, a *note ValueError: 1fc. exception is raised — but garbage
     data will also be written to the file.  The object will not be
     properly read back by *note load(): ff5.

     The `version' argument indicates the data format that ‘dump’ should
     use (see below).

 -- 函式: marshal.load (file)

     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: c71, *note
     ValueError: 1fc. or *note TypeError: 193.  The file must be a
     readable *note binary file: 1caa.

          備註: If an object containing an unsupported type was
          marshalled with *note dump(): 1cea, *note load(): ff5. will
          substitute ‘None’ for the unmarshallable type.

 -- 函式: marshal.dumps (value[, version])

     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: 1fc. exception if value has (or contains an
     object that has) an unsupported type.

     The `version' argument indicates the data format that ‘dumps’
     should use (see below).

 -- 函式: marshal.loads (bytes)

     Convert the *note bytes-like object: 5ed. to a value.  If no valid
     value is found, raise *note EOFError: c71, *note ValueError: 1fc.
     or *note TypeError: 193.  Extra bytes in the input are ignored.

In addition, the following constants are defined:

 -- Data: marshal.version

     Indicates the format that the module uses.  Version 0 is the
     historical format, version 1 shares interned strings and version 2
     uses a binary format for floating point numbers.  Version 3 adds
     support for object instancing and recursion.  The current version
     is 4.

註解
....

   ---------- Footnotes ----------

   (1) (1) The name of this module stems from a bit of terminology used
by the designers of Modula-3 (amongst others), who use the term
"marshalling" for shipping of data around in a self-contained form.
Strictly speaking, "to marshal" means to convert some data from internal
to external form (in an RPC buffer for instance) and "unmarshalling" for
the reverse process.


File: python.info,  Node: dbm --- Interfaces to Unix "databases",  Next: sqlite3 --- DB-API 2 0 interface for SQLite databases,  Prev: marshal --- Internal Python object serialization,  Up: Data Persistence

5.12.5 ‘dbm’ — Interfaces to Unix "databases"
---------------------------------------------

`Source code:' Lib/dbm/__init__.py(1)

__________________________________________________________________

*note dbm: 32. is a generic interface to variants of the DBM database —
*note dbm.gnu: 34. or *note dbm.ndbm: 35.  If none of these modules is
installed, the slow-but-simple implementation in module *note dbm.dumb:
33. will be used.  There is a third party interface(2) to the Oracle
Berkeley DB.

 -- 例外: 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: 1cef. as the first item — the latter is used when *note
     dbm.error: 1cef. is raised.

 -- 函式: dbm.whichdb (filename)

     This function attempts to guess which of the several simple
     database modules available — *note dbm.gnu: 34, *note dbm.ndbm: 35.
     or *note dbm.dumb: 33. — should be used to open a given file.

     Returns one of the following values: ‘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; or a string
     containing the required module name, such as ‘'dbm.ndbm'’ or
     ‘'dbm.gnu'’.

 -- 函式: dbm.open (file, flag='r', mode=0o666)

     Open the database file `file' and return a corresponding object.

     If the database file already exists, the *note whichdb(): 1cf0.
     function is used to determine its type and the appropriate module
     is used; if it does not exist, the first module listed above that
     can be imported is used.

     The optional `flag' argument can be:

     Value         Meaning
                   
     --------------------------------------------------------------
                   
     ‘'r'’         Open existing database for reading only
                   (default)
                   
                   
     ‘'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 optional `mode' argument is the Unix mode of the file, used
     only when the database has to be created.  It defaults to octal
     ‘0o666’ (and will be modified by the prevailing umask).

The object returned by *note open(): 835. supports the same basic
functionality as dictionaries; keys and their corresponding values can
be stored, retrieved, and deleted, and the *note in: 7a8. operator and
the ‘keys()’ method are available, as well as ‘get()’ and
‘setdefault()’.

3.2 版更變: ‘get()’ and ‘setdefault()’ are now available in all database
modules.

3.8 版更變: Deleting a key from a read-only database raises database
module specific error instead of *note KeyError: 2c8.

Key and values are always stored as bytes.  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: 6ee. statement,
which will automatically close them when done.

3.4 版更變: Added native support for the context management protocol to
the objects returned by *note open(): 835.

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.

也參考
......

Module *note shelve: e8.

     Persistence module which stores non-string data.

The individual submodules are described in the following sections.

* Menu:

* dbm.gnu: dbm gnu --- GNU's reinterpretation of dbm. GNU’s reinterpretation of dbm
* dbm.ndbm: dbm ndbm --- Interface based on ndbm. Interface based on ndbm
* dbm.dumb: dbm dumb --- Portable DBM implementation. Portable DBM implementation

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/dbm/__init__.py

   (2) https://www.jcea.es/programacion/pybsddb.htm


File: python.info,  Node: dbm gnu --- GNU's reinterpretation of dbm,  Next: dbm ndbm --- Interface based on ndbm,  Up: dbm --- Interfaces to Unix "databases"

5.12.5.1 ‘dbm.gnu’ — GNU’s reinterpretation of dbm
..................................................

`Source code:' Lib/dbm/gnu.py(1)

__________________________________________________________________

This module is quite similar to the *note dbm: 32. module, but uses the
GNU library ‘gdbm’ instead to provide some additional functionality.
Please note that the file formats created by *note dbm.gnu: 34. and
*note dbm.ndbm: 35. are incompatible.

The *note dbm.gnu: 34. module provides an interface to the GNU DBM
library.  ‘dbm.gnu.gdbm’ objects behave like mappings (dictionaries),
except that keys and values are always converted to bytes before
storing.  Printing a ‘gdbm’ object doesn’t print the keys and values,
and the ‘items()’ and ‘values()’ methods are not supported.

 -- 例外: dbm.gnu.error

     Raised on *note dbm.gnu: 34.-specific errors, such as I/O errors.
     *note KeyError: 2c8. is raised for general mapping errors like
     specifying an incorrect key.

 -- 函式: dbm.gnu.open (filename[, flag[, mode]])

     Open a ‘gdbm’ database and return a ‘gdbm’ object.  The `filename'
     argument is the name of the database file.

     The optional `flag' argument can be:

     Value         Meaning
                   
     --------------------------------------------------------------
                   
     ‘'r'’         Open existing database for reading only
                   (default)
                   
                   
     ‘'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 the flag to
     control how the database is opened:

     Value         Meaning
                   
     ---------------------------------------------------------------
                   
     ‘'f'’         Open the database in fast mode.  Writes to the
                   database will not be synchronized.
                   
                   
     ‘'s'’         Synchronized mode.  This will cause changes to
                   the database to be immediately written to the
                   file.
                   
                   
     ‘'u'’         不要鎖住資料庫
                   

     Not all flags are valid for all versions of ‘gdbm’.  The module
     constant ‘open_flags’ is a string of supported flag characters.
     The exception *note error: 2c6. is raised if an invalid flag is
     specified.

     The optional `mode' argument is the Unix mode of the file, used
     only when the database has to be created.  It defaults to octal
     ‘0o666’.

     In addition to the dictionary-like methods, ‘gdbm’ objects have the
     following methods:

      -- 成員函式: gdbm.firstkey ()

          It’s possible to loop over every key in the database using
          this method and the *note nextkey(): 1cf3. 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 != 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 ()

          Close the ‘gdbm’ database.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/dbm/gnu.py


File: python.info,  Node: dbm ndbm --- Interface based on ndbm,  Next: dbm dumb --- Portable DBM implementation,  Prev: dbm gnu --- GNU's reinterpretation of dbm,  Up: dbm --- Interfaces to Unix "databases"

5.12.5.2 ‘dbm.ndbm’ — Interface based on ndbm
.............................................

`Source code:' Lib/dbm/ndbm.py(1)

__________________________________________________________________

The *note dbm.ndbm: 35. module provides an interface to the Unix
"(n)dbm" library.  Dbm objects behave like mappings (dictionaries),
except that keys and values are always stored as bytes.  Printing a
‘dbm’ object doesn’t print the keys and values, and the ‘items()’ and
‘values()’ methods are not supported.

This module can be used with the "classic" ndbm interface or the GNU
GDBM compatibility interface.  On Unix, the ‘configure’ script will
attempt to locate the appropriate header file to simplify building this
module.

 -- 例外: dbm.ndbm.error

     Raised on *note dbm.ndbm: 35.-specific errors, such as I/O errors.
     *note KeyError: 2c8. is raised for general mapping errors like
     specifying an incorrect key.

 -- Data: dbm.ndbm.library

     Name of the ‘ndbm’ implementation library used.

 -- 函式: dbm.ndbm.open (filename[, flag[, mode]])

     Open a dbm database and return a ‘ndbm’ object.  The `filename'
     argument is the name of the database file (without the ‘.dir’ or
     ‘.pag’ extensions).

     The optional `flag' argument must be one of these values:

     Value         Meaning
                   
     --------------------------------------------------------------
                   
     ‘'r'’         Open existing database for reading only
                   (default)
                   
                   
     ‘'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 optional `mode' argument is the Unix mode of the file, used
     only when the database has to be created.  It defaults to octal
     ‘0o666’ (and will be modified by the prevailing umask).

     In addition to the dictionary-like methods, ‘ndbm’ objects provide
     the following method:

      -- 成員函式: ndbm.close ()

          Close the ‘ndbm’ database.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/dbm/ndbm.py


File: python.info,  Node: dbm dumb --- Portable DBM implementation,  Prev: dbm ndbm --- Interface based on ndbm,  Up: dbm --- Interfaces to Unix "databases"

5.12.5.3 ‘dbm.dumb’ — Portable DBM implementation
.................................................

`Source code:' Lib/dbm/dumb.py(1)

     備註: The *note dbm.dumb: 33. module is intended as a last resort
     fallback for the *note dbm: 32. module when a more robust module is
     not available.  The *note dbm.dumb: 33. module is not written for
     speed and is not nearly as heavily used as the other database
     modules.

__________________________________________________________________

The *note dbm.dumb: 33. module provides a persistent dictionary-like
interface which is written entirely in Python.  Unlike other modules
such as *note dbm.gnu: 34. no external library is required.  As with
other persistent mappings, the keys and values are always stored as
bytes.

The module defines the following:

 -- 例外: dbm.dumb.error

     Raised on *note dbm.dumb: 33.-specific errors, such as I/O errors.
     *note KeyError: 2c8. is raised for general mapping errors like
     specifying an incorrect key.

 -- 函式: dbm.dumb.open (filename[, flag[, mode]])

     Open a ‘dumbdbm’ database and return a dumbdbm object.  The
     `filename' argument is the basename of the database file (without
     any specific extensions).  When a dumbdbm database is created,
     files with ‘.dat’ and ‘.dir’ extensions are created.

     The optional `flag' argument can be:

     Value         Meaning
                   
     --------------------------------------------------------------
                   
     ‘'r'’         Open existing database for reading only
                   (default)
                   
                   
     ‘'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 optional `mode' argument is the Unix mode of the file, used
     only when the database has to be created.  It defaults to octal
     ‘0o666’ (and will be modified by the prevailing umask).

          警告: 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(): 2c0. always creates a new database when
     the flag has the value ‘'n'’.

     3.8 版更變: A database opened with flags ‘'r'’ is now read-only.
     Opening with flags ‘'r'’ and ‘'w'’ no longer creates a database if
     it does not exist.

     In addition to the methods provided by the *note
     collections.abc.MutableMapping: 9f4. class, ‘dumbdbm’ objects
     provide the following methods:

      -- 成員函式: dumbdbm.sync ()

          Synchronize the on-disk directory and data files.  This method
          is called by the ‘Shelve.sync()’ method.

      -- 成員函式: dumbdbm.close ()

          Close the ‘dumbdbm’ database.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/dbm/dumb.py


File: python.info,  Node: sqlite3 --- DB-API 2 0 interface for SQLite databases,  Prev: dbm --- Interfaces to Unix "databases",  Up: Data Persistence

5.12.6 ‘sqlite3’ — DB-API 2.0 interface for SQLite databases
------------------------------------------------------------

`Source code:' 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 a SQL
interface compliant with the DB-API 2.0 specification described by PEP
249(2).

To use the module, you must first create a *note Connection: 3dd. object
that represents the database.  Here the data will be stored in the
‘example.db’ file:

     import sqlite3
     con = sqlite3.connect('example.db')

You can also supply the special name ‘:memory:’ to create a database in
RAM.

Once you have a *note Connection: 3dd, you can create a *note Cursor:
1cff. object and call its *note execute(): 1d00. method to perform SQL
commands:

     cur = con.cursor()

     # Create table
     cur.execute('''CREATE TABLE stocks
                    (date text, trans text, symbol text, qty real, price real)''')

     # Insert a row of data
     cur.execute("INSERT INTO stocks VALUES ('2006-01-05','BUY','RHAT',100,35.14)")

     # Save (commit) the changes
     con.commit()

     # We can also close the connection if we are done with it.
     # Just be sure any changes have been committed or they will be lost.
     con.close()

The data you’ve saved is persistent and is available in subsequent
sessions:

     import sqlite3
     con = sqlite3.connect('example.db')
     cur = con.cursor()

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 (see ‘https://xkcd.com/327/’ for
humorous example of what can go wrong).

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 *note execute(): 1d00.
method.  (Other database modules may use a different placeholder, such
as ‘%s’ or ‘:1’.)  For example:

     # Never do this -- insecure!
     symbol = 'RHAT'
     cur.execute("SELECT * FROM stocks WHERE symbol = '%s'" % symbol)

     # Do this instead
     t = ('RHAT',)
     cur.execute('SELECT * FROM stocks WHERE symbol=?', t)
     print(cur.fetchone())

     # Larger example that inserts many records at a time
     purchases = [('2006-03-28', 'BUY', 'IBM', 1000, 45.00),
                  ('2006-04-05', 'BUY', 'MSFT', 1000, 72.00),
                  ('2006-04-06', 'SELL', 'IBM', 500, 53.00),
                 ]
     cur.executemany('INSERT INTO stocks VALUES (?,?,?,?,?)', purchases)

To retrieve data after executing a SELECT statement, you can either
treat the cursor as an *note iterator: 1040, call the cursor’s *note
fetchone(): 1d01. method to retrieve a single matching row, or call
*note fetchall(): 1d02. to get a list of the matching rows.

This example uses the iterator form:

     >>> for row in cur.execute('SELECT * FROM stocks ORDER BY price'):
             print(row)

     ('2006-01-05', 'BUY', 'RHAT', 100, 35.14)
     ('2006-03-28', 'BUY', 'IBM', 1000, 45.0)
     ('2006-04-06', 'SELL', 'IBM', 500, 53.0)
     ('2006-04-05', 'BUY', 'MSFT', 1000, 72.0)

也參考
......

‘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) - Database API Specification 2.0

     PEP written by Marc-André Lemburg.

* Menu:

* Module functions and constants::
* Connection Objects::
* Cursor Objects::
* Row Objects::
* Exceptions: Exceptions<3>.
* SQLite and Python types::
* Controlling Transactions::
* Using sqlite3 efficiently::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/sqlite3/

   (2) https://www.python.org/dev/peps/pep-0249

   (3) https://www.python.org/dev/peps/pep-0249


File: python.info,  Node: Module functions and constants,  Next: Connection Objects,  Up: sqlite3 --- DB-API 2 0 interface for SQLite databases

5.12.6.1 Module functions and constants
.......................................

 -- Data: sqlite3.version

     The version number of this module, as a string.  This is not the
     version of the SQLite library.

 -- Data: sqlite3.version_info

     The version number of this module, as a tuple of integers.  This is
     not the version of the SQLite library.

 -- Data: sqlite3.sqlite_version

     The version number of the run-time SQLite library, as a string.

 -- Data: sqlite3.sqlite_version_info

     The version number of the run-time SQLite library, as a tuple of
     integers.

 -- Data: sqlite3.PARSE_DECLTYPES

     This constant is meant to be used with the `detect_types' parameter
     of the *note connect(): 3df. function.

     Setting it makes the *note sqlite3: f3. module parse the declared
     type for each column it returns.  It will parse out the first word
     of the declared type, i.  e.  for "integer primary key", it will
     parse out "integer", or for "number(10)" it will parse out
     "number".  Then for that column, it will look into the converters
     dictionary and use the converter function registered for that type
     there.

 -- Data: sqlite3.PARSE_COLNAMES

     This constant is meant to be used with the `detect_types' parameter
     of the *note connect(): 3df. function.

     Setting this makes the SQLite interface parse the column name for
     each column it returns.  It will look for a string formed [mytype]
     in there, and then decide that ’mytype’ is the type of the column.
     It will try to find an entry of ’mytype’ in the converters
     dictionary and then use the converter function found there to
     return the value.  The column name found in *note
     Cursor.description: 1d0b. does not include the type, i.  e.  if you
     use something like ‘'as "Expiration date [datetime]"'’ in your SQL,
     then we will parse out everything until the first ‘'['’ for the
     column name and strip the preceeding space: the column name would
     simply be "Expiration date".

 -- 函式: sqlite3.connect (database[, timeout, detect_types,
          isolation_level, check_same_thread, factory,
          cached_statements, uri])

     Opens a connection to the SQLite database file `database'.  By
     default returns a *note Connection: 3dd. object, unless a custom
     `factory' is given.

     `database' is a *note path-like object: 36f. giving the pathname
     (absolute or relative to the current working directory) of the
     database file to be opened.  You can use ‘":memory:"’ to open a
     database connection to a database that resides in RAM instead of on
     disk.

     When a database is accessed by multiple connections, and one of the
     processes modifies the database, the SQLite database is locked
     until that transaction is committed.  The `timeout' parameter
     specifies how long the connection should wait for the lock to go
     away until raising an exception.  The default for the timeout
     parameter is 5.0 (five seconds).

     For the `isolation_level' parameter, please see the *note
     isolation_level: 1d0c. property of *note Connection: 3dd. objects.

     SQLite natively supports only the types TEXT, INTEGER, REAL, BLOB
     and NULL. If you want to use other types you must add support for
     them yourself.  The `detect_types' parameter and the using custom
     `converters' registered with the module-level *note
     register_converter(): 1d0d. function allow you to easily do that.

     `detect_types' defaults to 0 (i.  e.  off, no type detection), you
     can set it to any combination of *note PARSE_DECLTYPES: 1d09. and
     *note PARSE_COLNAMES: 1d0a. to turn type detection on.  Due to
     SQLite behaviour, types can’t be detected for generated fields (for
     example ‘max(data)’), even when `detect_types' parameter is set.
     In such case, the returned type is *note str: 335.

     By default, `check_same_thread' is *note True: 49e. and only the
     creating thread may use the connection.  If set *note False: 38d,
     the returned connection may be shared across multiple threads.
     When using multiple threads with the same connection writing
     operations should be serialized by the user to avoid data
     corruption.

     By default, the *note sqlite3: f3. module uses its *note
     Connection: 3dd. class for the connect call.  You can, however,
     subclass the *note Connection: 3dd. class and make *note connect():
     3df. use your class instead by providing your class for the
     `factory' parameter.

     Consult the section *note SQLite and Python types: 1d0e. of this
     manual for details.

     The *note sqlite3: f3. module internally uses a statement cache to
     avoid SQL parsing overhead.  If you want to explicitly set the
     number of statements that are cached for the connection, you can
     set the `cached_statements' parameter.  The currently implemented
     default is to cache 100 statements.

     If `uri' is true, `database' is interpreted as a URI. This allows
     you to specify options.  For example, to open a database in
     read-only mode you can use:

          db = sqlite3.connect('file:path/to/database?mode=ro', uri=True)

     More information about this feature, including a list of recognized
     options, can be found in the SQLite URI documentation(1).

     Raises an *note auditing event: e96. ‘sqlite3.connect’ with
     argument ‘database’.

     3.4 版更變: Added the `uri' parameter.

     3.7 版更變: `database' can now also be a *note path-like object:
     36f, not only a string.

 -- 函式: sqlite3.register_converter (typename, callable)

     Registers a callable to convert a bytestring from the database into
     a custom Python type.  The callable will be invoked for all
     database values that are of the type `typename'.  Confer the
     parameter `detect_types' of the *note connect(): 3df. function for
     how the type detection works.  Note that `typename' and the name of
     the type in your query are matched in case-insensitive manner.

 -- 函式: sqlite3.register_adapter (type, callable)

     Registers a callable to convert the custom Python type `type' into
     one of SQLite’s supported types.  The callable `callable' accepts
     as single parameter the Python value, and must return a value of
     the following types: int, float, str or bytes.

 -- 函式: sqlite3.complete_statement (sql)

     Returns *note True: 49e. if the string `sql' contains one or more
     complete SQL statements terminated by semicolons.  It does not
     verify that the SQL is syntactically correct, only that there are
     no unclosed string literals and the statement is terminated by a
     semicolon.

     This can be used to build a shell for SQLite, as in the following
     example:

          # A minimal SQLite shell for experiments

          import sqlite3

          con = sqlite3.connect(":memory:")
          con.isolation_level = None
          cur = con.cursor()

          buffer = ""

          print("Enter your SQL commands to execute in sqlite3.")
          print("Enter a blank line to exit.")

          while True:
              line = input()
              if line == "":
                  break
              buffer += line
              if sqlite3.complete_statement(buffer):
                  try:
                      buffer = buffer.strip()
                      cur.execute(buffer)

                      if buffer.lstrip().upper().startswith("SELECT"):
                          print(cur.fetchall())
                  except sqlite3.Error as e:
                      print("An error occurred:", e.args[0])
                  buffer = ""

          con.close()

 -- 函式: sqlite3.enable_callback_tracebacks (flag)

     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
     ‘sys.stderr’.  Use *note False: 38d. to disable the feature again.

   ---------- Footnotes ----------

   (1) https://www.sqlite.org/uri.html


File: python.info,  Node: Connection Objects,  Next: Cursor Objects,  Prev: Module functions and constants,  Up: sqlite3 --- DB-API 2 0 interface for SQLite databases

5.12.6.2 Connection Objects
...........................

 -- 類別: sqlite3.Connection

     A SQLite database connection has the following attributes and
     methods:

      -- 屬性: isolation_level

          Get or set the current default isolation level.  *note None:
          158. for autocommit mode or one of "DEFERRED", "IMMEDIATE" or
          "EXCLUSIVE". See section *note Controlling Transactions: 1d14.
          for a more detailed explanation.

      -- 屬性: in_transaction

          *note True: 49e. if a transaction is active (there are
          uncommitted changes), *note False: 38d. otherwise.  Read-only
          attribute.

          3.2 版新加入.

      -- 成員函式: cursor (factory=Cursor)

          The cursor method accepts a single optional parameter
          `factory'.  If supplied, this must be a callable returning an
          instance of *note Cursor: 1cff. or its subclasses.

      -- 成員函式: commit ()

          This method commits the current transaction.  If you don’t
          call this method, anything you did since the last call to
          ‘commit()’ is not visible from other database connections.  If
          you wonder why you don’t see the data you’ve written to the
          database, please check you didn’t forget to call this method.

      -- 成員函式: rollback ()

          This method rolls back any changes to the database since the
          last call to *note commit(): 1d17.

      -- 成員函式: close ()

          This closes the database connection.  Note that this does not
          automatically call *note commit(): 1d17.  If you just close
          your database connection without calling *note commit(): 1d17.
          first, your changes will be lost!

      -- 成員函式: execute (sql[, parameters])

          This is a nonstandard shortcut that creates a cursor object by
          calling the *note cursor(): 1d16. method, calls the cursor’s
          *note execute(): 1d00. method with the `parameters' given, and
          returns the cursor.

      -- 成員函式: executemany (sql[, parameters])

          This is a nonstandard shortcut that creates a cursor object by
          calling the *note cursor(): 1d16. method, calls the cursor’s
          *note executemany(): 1d1c. method with the `parameters' given,
          and returns the cursor.

      -- 成員函式: executescript (sql_script)

          This is a nonstandard shortcut that creates a cursor object by
          calling the *note cursor(): 1d16. method, calls the cursor’s
          *note executescript(): 1d1e. method with the given
          `sql_script', and returns the cursor.

      -- 成員函式: create_function (name, num_params, func, *,
               deterministic=False)

          Creates a user-defined function that you can later use from
          within SQL statements under the function name `name'.
          `num_params' is the number of parameters the function accepts
          (if `num_params' is -1, the function may take any number of
          arguments), and `func' is a Python callable that is called as
          the SQL function.  If `deterministic' is true, the created
          function is marked as deterministic(1), which allows SQLite to
          perform additional optimizations.  This flag is supported by
          SQLite 3.8.3 or higher, *note NotSupportedError: 1d1f. will be
          raised if used with older versions.

          The function can return any of the types supported by SQLite:
          bytes, str, int, float and ‘None’.

          3.8 版更變: The `deterministic' parameter was added.

          Example:

               import sqlite3
               import hashlib

               def md5sum(t):
                   return hashlib.md5(t).hexdigest()

               con = sqlite3.connect(":memory:")
               con.create_function("md5", 1, md5sum)
               cur = con.cursor()
               cur.execute("select md5(?)", (b"foo",))
               print(cur.fetchone()[0])

               con.close()

      -- 成員函式: create_aggregate (name, num_params, aggregate_class)

          Creates a user-defined aggregate function.

          The aggregate class must implement a ‘step’ method, which
          accepts the number of parameters `num_params' (if `num_params'
          is -1, the function may take any number of arguments), and a
          ‘finalize’ method which will return the final result of the
          aggregate.

          The ‘finalize’ method can return any of the types supported by
          SQLite: bytes, str, int, float and ‘None’.

          Example:

               import sqlite3

               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.cursor()
               cur.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()

      -- 成員函式: create_collation (name, callable)

          Creates a collation with the specified `name' and `callable'.
          The callable will be passed two string arguments.  It should
          return -1 if the first is ordered lower than the second, 0 if
          they are ordered equal and 1 if the first is ordered higher
          than the second.  Note that this controls sorting (ORDER BY in
          SQL) so your comparisons don’t affect other SQL operations.

          Note that the callable will get its parameters as Python
          bytestrings, which will normally be encoded in UTF-8.

          The following example shows a custom collation that sorts "the
          wrong way":

               import sqlite3

               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.cursor()
               cur.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()

          To remove a collation, call ‘create_collation’ with ‘None’ as
          callable:

               con.create_collation("reverse", None)

      -- 成員函式: interrupt ()

          You can call this method from a different thread to abort any
          queries that might be executing on the connection.  The query
          will then abort and the caller will get an exception.

      -- 成員函式: set_authorizer (authorizer_callback)

          This routine registers a callback.  The callback is invoked
          for each attempt to access a column of a table in the
          database.  The callback should return ‘SQLITE_OK’ if access is
          allowed, ‘SQLITE_DENY’ if the entire SQL statement should be
          aborted with an error and ‘SQLITE_IGNORE’ if the column should
          be treated as a NULL value.  These constants are available in
          the *note sqlite3: f3. module.

          The first argument to the callback signifies what kind of
          operation is to be authorized.  The second and third argument
          will be arguments or *note None: 158. 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 *note None: 158. 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 *note sqlite3: f3. module.

      -- 成員函式: set_progress_handler (handler, n)

          This routine registers a callback.  The callback is 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 *note None: 158. for `handler'.

          Returning a non-zero value from the handler function will
          terminate the currently executing query and cause it to raise
          an *note OperationalError: 1d22. exception.

      -- 成員函式: set_trace_callback (trace_callback)

          Registers `trace_callback' to be called for each SQL statement
          that is actually executed by the SQLite backend.

          The only argument passed to the callback is the statement (as
          string) 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(): 1d00.
          methods.  Other sources include the transaction management of
          the Python module and the execution of triggers defined in the
          current database.

          Passing *note None: 158. as `trace_callback' will disable the
          trace callback.

          3.3 版新加入.

      -- 成員函式: enable_load_extension (enabled)

          This routine allows/disallows the SQLite engine to load SQLite
          extensions from shared libraries.  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.

          Loadable extensions are disabled by default.  See (2).

          3.2 版新加入.

               import sqlite3

               con = sqlite3.connect(":memory:")

               # enable extension loading
               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)

               con.close()

      -- 成員函式: load_extension (path)

          This routine loads a SQLite extension from a shared library.
          You have to enable extension loading with *note
          enable_load_extension(): b9e. before you can use this routine.

          Loadable extensions are disabled by default.  See (3).

          3.2 版新加入.

      -- 屬性: row_factory

          You can change this attribute to a callable that accepts the
          cursor and the original row as a tuple and will return the
          real result row.  This way, you can implement more advanced
          ways of returning results, such as returning an object that
          can also access columns by name.

          Example:

               import sqlite3

               def dict_factory(cursor, row):
                   d = {}
                   for idx, col in enumerate(cursor.description):
                       d[col[0]] = row[idx]
                   return d

               con = sqlite3.connect(":memory:")
               con.row_factory = dict_factory
               cur = con.cursor()
               cur.execute("select 1 as a")
               print(cur.fetchone()["a"])

               con.close()

          If returning a tuple doesn’t suffice and you want name-based
          access to columns, you should consider setting *note
          row_factory: 1d23. to the highly-optimized *note sqlite3.Row:
          763. type.  *note Row: 763. provides both index-based and
          case-insensitive name-based access to columns with almost no
          memory overhead.  It will probably be better than your own
          custom dictionary-based approach or even a db_row based
          solution.

      -- 屬性: text_factory

          Using this attribute you can control what objects are returned
          for the ‘TEXT’ data type.  By default, this attribute is set
          to *note str: 335. and the *note sqlite3: f3. module will
          return Unicode objects for ‘TEXT’.  If you want to return
          bytestrings instead, you can set it to *note bytes: 336.

          You can also set it to any other callable that accepts a
          single bytestring parameter and returns the resulting object.

          See the following example code for illustration:

               import sqlite3

               con = sqlite3.connect(":memory:")
               cur = con.cursor()

               AUSTRIA = "\xd6sterreich"

               # by default, rows are returned as Unicode
               cur.execute("select ?", (AUSTRIA,))
               row = cur.fetchone()
               assert row[0] == AUSTRIA

               # but we can make sqlite3 always return bytestrings ...
               con.text_factory = bytes
               cur.execute("select ?", (AUSTRIA,))
               row = cur.fetchone()
               assert type(row[0]) is bytes
               # the bytestrings will be encoded in UTF-8, unless you stored garbage in the
               # database ...
               assert row[0] == AUSTRIA.encode("utf-8")

               # we can also implement a custom text_factory ...
               # here we implement one that appends "foo" to all strings
               con.text_factory = lambda x: x.decode("utf-8") + "foo"
               cur.execute("select ?", ("bar",))
               row = cur.fetchone()
               assert row[0] == "barfoo"

               con.close()

      -- 屬性: total_changes

          Returns the total number of database rows that have been
          modified, inserted, or deleted since the database connection
          was opened.

      -- 成員函式: iterdump ()

          Returns an iterator to dump the database in an SQL text
          format.  Useful when saving an in-memory database for later
          restoration.  This function provides the same capabilities as
          the ‘.dump’ command in the ‘sqlite3’ shell.

          Example:

               # Convert file existing_db.db to SQL dump file dump.sql
               import sqlite3

               con = sqlite3.connect('existing_db.db')
               with open('dump.sql', 'w') as f:
                   for line in con.iterdump():
                       f.write('%s\n' % line)
               con.close()

      -- 成員函式: backup (target, *, pages=-1, progress=None,
               name="main", sleep=0.250)

          This method makes a backup of a SQLite database even while
          it’s being accessed by other clients, or concurrently by the
          same connection.  The copy will be written into the mandatory
          argument `target', that must be another *note Connection: 3dd.
          instance.

          By default, or when `pages' is either ‘0’ or a negative
          integer, the entire database is copied in a single step;
          otherwise the method performs a loop copying up to `pages'
          pages at a time.

          If `progress' is specified, it must either be ‘None’ or a
          callable object that will be executed at each iteration with
          three integer arguments, respectively the `status' of the last
          iteration, the `remaining' number of pages still to be copied
          and the `total' number of pages.

          The `name' argument specifies the database name that will be
          copied: it must be a string containing either ‘"main"’, the
          default, to indicate the main database, ‘"temp"’ to indicate
          the temporary database or the name specified after the ‘AS’
          keyword in an ‘ATTACH DATABASE’ statement for an attached
          database.

          The `sleep' argument specifies the number of seconds to sleep
          by between successive attempts to backup remaining pages, can
          be specified either as an integer or a floating point value.

          Example 1, copy an existing database into another:

               import sqlite3

               def progress(status, remaining, total):
                   print(f'Copied {total-remaining} of {total} pages...')

               con = sqlite3.connect('existing_db.db')
               bck = sqlite3.connect('backup.db')
               with bck:
                   con.backup(bck, pages=1, progress=progress)
               bck.close()
               con.close()

          Example 2, copy an existing database into a transient copy:

               import sqlite3

               source = sqlite3.connect('existing_db.db')
               dest = sqlite3.connect(':memory:')
               source.backup(dest)

          Availability: SQLite 3.6.11 or higher

          3.7 版新加入.

   ---------- Footnotes ----------

   (1) https://sqlite.org/deterministic.html

   (2) (1) The sqlite3 module is not built with loadable extension
support by default, because some platforms (notably Mac OS X) have
SQLite libraries which are compiled without this feature.  To get
loadable extension support, you must pass
‘--enable-loadable-sqlite-extensions’ to configure.

   (3) (1) The sqlite3 module is not built with loadable extension
support by default, because some platforms (notably Mac OS X) have
SQLite libraries which are compiled without this feature.  To get
loadable extension support, you must pass
‘--enable-loadable-sqlite-extensions’ to configure.


File: python.info,  Node: Cursor Objects,  Next: Row Objects,  Prev: Connection Objects,  Up: sqlite3 --- DB-API 2 0 interface for SQLite databases

5.12.6.3 Cursor Objects
.......................

 -- 類別: sqlite3.Cursor

     A *note Cursor: 1cff. instance has the following attributes and
     methods.

      -- 成員函式: execute (sql[, parameters])

          Executes an SQL statement.  The SQL statement may be
          parameterized (i.  e.  placeholders instead of SQL literals).
          The *note sqlite3: f3. module supports two kinds of
          placeholders: question marks (qmark style) and named
          placeholders (named style).

          Here’s an example of both styles:

               import sqlite3

               con = sqlite3.connect(":memory:")
               cur = con.cursor()
               cur.execute("create table people (name_last, age)")

               who = "Yeltsin"
               age = 72

               # This is the qmark style:
               cur.execute("insert into people values (?, ?)", (who, age))

               # And this is the named style:
               cur.execute("select * from people where name_last=:who and age=:age", {"who": who, "age": age})

               print(cur.fetchone())

               con.close()

          *note execute(): 1d00. will only execute a single SQL
          statement.  If you try to execute more than one statement with
          it, it will raise a *note Warning: 1d29.  Use *note
          executescript(): 1d1e. if you want to execute multiple SQL
          statements with one call.

      -- 成員函式: executemany (sql, seq_of_parameters)

          Executes an SQL command against all parameter sequences or
          mappings found in the sequence `seq_of_parameters'.  The *note
          sqlite3: f3. module also allows using an *note iterator: 1040.
          yielding parameters instead of a sequence.

               import sqlite3

               class IterChars:
                   def __init__(self):
                       self.count = ord('a')

                   def __iter__(self):
                       return self

                   def __next__(self):
                       if self.count > ord('z'):
                           raise StopIteration
                       self.count += 1
                       return (chr(self.count - 1),) # this is a 1-tuple

               con = sqlite3.connect(":memory:")
               cur = con.cursor()
               cur.execute("create table characters(c)")

               theIter = IterChars()
               cur.executemany("insert into characters(c) values (?)", theIter)

               cur.execute("select c from characters")
               print(cur.fetchall())

               con.close()

          Here’s a shorter example using a *note generator: 9a7.:

               import sqlite3
               import string

               def char_generator():
                   for c in string.ascii_lowercase:
                       yield (c,)

               con = sqlite3.connect(":memory:")
               cur = con.cursor()
               cur.execute("create table characters(c)")

               cur.executemany("insert into characters(c) values (?)", char_generator())

               cur.execute("select c from characters")
               print(cur.fetchall())

               con.close()

      -- 成員函式: executescript (sql_script)

          This is a nonstandard convenience method for executing
          multiple SQL statements at once.  It issues a ‘COMMIT’
          statement first, then executes the SQL script it gets as a
          parameter.

          `sql_script' can be an instance of *note str: 335.

          Example:

               import sqlite3

               con = sqlite3.connect(":memory:")
               cur = con.cursor()
               cur.executescript("""
                   create table person(
                       firstname,
                       lastname,
                       age
                   );

                   create table book(
                       title,
                       author,
                       published
                   );

                   insert into book(title, author, published)
                   values (
                       'Dirk Gently''s Holistic Detective Agency',
                       'Douglas Adams',
                       1987
                   );
                   """)
               con.close()

      -- 成員函式: fetchone ()

          Fetches the next row of a query result set, returning a single
          sequence, or *note None: 158. when no more data is available.

      -- 成員函式: fetchmany (size=cursor.arraysize)

          Fetches the next set of rows of a query result, returning a
          list.  An empty list is returned when no more rows are
          available.

          The number of rows to fetch per call is specified by the
          `size' parameter.  If it is not given, the cursor’s arraysize
          determines the number of rows to be fetched.  The method
          should try to fetch as many rows as indicated by the size
          parameter.  If this is not possible due to the specified
          number of rows not being available, fewer rows may be
          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(): 1d2a. call to the next.

      -- 成員函式: fetchall ()

          Fetches all (remaining) rows of a query result, returning a
          list.  Note that the cursor’s arraysize attribute can affect
          the performance of this operation.  An empty list is returned
          when no rows are available.

      -- 成員函式: close ()

          Close the cursor now (rather than whenever ‘__del__’ is
          called).

          The cursor will be unusable from this point forward; a *note
          ProgrammingError: edd. exception will be raised if any
          operation is attempted with the cursor.

      -- 屬性: rowcount

          Although the *note Cursor: 1cff. class of the *note sqlite3:
          f3. module implements this attribute, the database engine’s
          own support for the determination of "rows affected"/"rows
          selected" is quirky.

          For *note executemany(): 1d1c. statements, the number of
          modifications are summed up into *note rowcount: 1d2c.

          As required by the Python DB API Spec, the *note rowcount:
          1d2c. attribute "is -1 in case no ‘executeXX()’ has been
          performed on the cursor or the rowcount of the last operation
          is not determinable by the interface".  This includes ‘SELECT’
          statements because we cannot determine the number of rows a
          query produced until all rows were fetched.

          With SQLite versions before 3.6.5, *note rowcount: 1d2c. is
          set to 0 if you make a ‘DELETE FROM table’ without any
          condition.

      -- 屬性: lastrowid

          This read-only attribute provides the rowid of the last
          modified row.  It is only set if you issued an ‘INSERT’ or a
          ‘REPLACE’ statement using the *note execute(): 1d00. method.
          For operations other than ‘INSERT’ or ‘REPLACE’ or when *note
          executemany(): 1d1c. is called, *note lastrowid: 583. is set
          to *note None: 158.

          If the ‘INSERT’ or ‘REPLACE’ statement failed to insert the
          previous successful rowid is returned.

          3.6 版更變: Added support for the ‘REPLACE’ statement.

      -- 屬性: arraysize

          Read/write attribute that controls the number of rows returned
          by *note fetchmany(): 1d2a.  The default value is 1 which
          means a single row would be fetched per call.

      -- 屬性: description

          This read-only attribute 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 *note None: 158.

          It is set for ‘SELECT’ statements without any matching rows as
          well.

      -- 屬性: connection

          This read-only attribute provides the SQLite database *note
          Connection: 3dd. used by the *note Cursor: 1cff. object.  A
          *note Cursor: 1cff. object created by calling *note
          con.cursor(): 1d16. will have a *note connection: 1d2e.
          attribute that refers to `con':

               >>> con = sqlite3.connect(":memory:")
               >>> cur = con.cursor()
               >>> cur.connection == con
               True


File: python.info,  Node: Row Objects,  Next: Exceptions<3>,  Prev: Cursor Objects,  Up: sqlite3 --- DB-API 2 0 interface for SQLite databases

5.12.6.4 Row Objects
....................

 -- 類別: sqlite3.Row

     A *note Row: 763. instance serves as a highly optimized *note
     row_factory: 1d23. for *note Connection: 3dd. objects.  It tries to
     mimic a tuple in most of its features.

     It supports mapping access by column name and index, iteration,
     representation, equality testing and *note len(): 151.

     If two *note Row: 763. objects have exactly the same columns and
     their members are equal, they compare equal.

      -- 成員函式: keys ()

          This method returns a list of column names.  Immediately after
          a query, it is the first member of each tuple in *note
          Cursor.description: 1d0b.

     3.5 版更變: Added support of slicing.

Let’s assume we initialize a table as in the example given above:

     con = sqlite3.connect(":memory:")
     cur = con.cursor()
     cur.execute('''create table stocks
     (date text, trans text, symbol text,
      qty real, price real)''')
     cur.execute("""insert into stocks
                 values ('2006-01-05','BUY','RHAT',100,35.14)""")
     con.commit()
     cur.close()

Now we plug *note Row: 763. in:

     >>> con.row_factory = sqlite3.Row
     >>> cur = con.cursor()
     >>> cur.execute('select * from stocks')
     <sqlite3.Cursor object at 0x7f4e7dd8fa80>
     >>> r = cur.fetchone()
     >>> type(r)
     <class 'sqlite3.Row'>
     >>> tuple(r)
     ('2006-01-05', 'BUY', 'RHAT', 100.0, 35.14)
     >>> len(r)
     5
     >>> r[2]
     'RHAT'
     >>> r.keys()
     ['date', 'trans', 'symbol', 'qty', 'price']
     >>> r['qty']
     100.0
     >>> for member in r:
     ...     print(member)
     ...
     2006-01-05
     BUY
     RHAT
     100.0
     35.14


File: python.info,  Node: Exceptions<3>,  Next: SQLite and Python types,  Prev: Row Objects,  Up: sqlite3 --- DB-API 2 0 interface for SQLite databases

5.12.6.5 Exceptions
...................

 -- 例外: sqlite3.Warning

     A subclass of *note Exception: 1aa.

 -- 例外: sqlite3.Error

     The base class of the other exceptions in this module.  It is a
     subclass of *note Exception: 1aa.

 -- 例外: sqlite3.DatabaseError

     Exception raised for errors that are related to the database.

 -- 例外: 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: 1d35.

 -- 例外: sqlite3.ProgrammingError

     Exception raised for programming errors, e.g.  table not found or
     already exists, syntax error in the SQL statement, wrong number of
     parameters specified, etc.  It is a subclass of *note
     DatabaseError: 1d35.

 -- 例外: sqlite3.OperationalError

     Exception raised for errors that are related to the database’s
     operation and not necessarily under the control of the programmer,
     e.g.  an unexpected disconnect occurs, the data source name is not
     found, a transaction could not be processed, etc.  It is a subclass
     of *note DatabaseError: 1d35.

 -- 例外: sqlite3.NotSupportedError

     Exception raised in case a method or database API was used which is
     not supported by the database, e.g.  calling the *note rollback():
     1d18. method on a connection that does not support transaction or
     has transactions turned off.  It is a subclass of *note
     DatabaseError: 1d35.


File: python.info,  Node: SQLite and Python types,  Next: Controlling Transactions,  Prev: Exceptions<3>,  Up: sqlite3 --- DB-API 2 0 interface for SQLite databases

5.12.6.6 SQLite and Python types
................................

* Menu:

* 簡介: 簡介<7>.
* Using adapters to store additional Python types in SQLite databases::
* Converting SQLite values to custom Python types::
* Default adapters and converters::


File: python.info,  Node: 簡介<7>,  Next: Using adapters to store additional Python types in SQLite databases,  Up: SQLite and Python types

5.12.6.7 簡介
.............

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
                                    
------------------------------------------------------
                                    
*note None: 158.                    ‘NULL’
                                    
                                    
*note int: 185.                     ‘INTEGER’
                                    
                                    
*note float: 188.                   ‘REAL’
                                    
                                    
*note str: 335.                     ‘TEXT’
                                    
                                    
*note bytes: 336.                   ‘BLOB’
                                    

This is how SQLite types are converted to Python types by default:

SQLite type       Python type
                  
---------------------------------------------------------------------
                  
‘NULL’            *note None: 158.
                  
                  
‘INTEGER’         *note int: 185.
                  
                  
‘REAL’            *note float: 188.
                  
                  
‘TEXT’            depends on *note text_factory: 1d24,
                  *note str: 335. by default
                  
                  
‘BLOB’            *note bytes: 336.
                  

The type system of the *note sqlite3: f3. module is extensible in two
ways: you can store additional Python types in a SQLite database via
object adaptation, and you can let the *note sqlite3: f3. module convert
SQLite types to different Python types via converters.


File: python.info,  Node: Using adapters to store additional Python types in SQLite databases,  Next: Converting SQLite values to custom Python types,  Prev: 簡介<7>,  Up: SQLite and Python types

5.12.6.8 Using adapters to store additional Python types in SQLite databases
............................................................................

As described before, SQLite supports only a limited set of types
natively.  To use other Python types with SQLite, you must `adapt' them
to one of the sqlite3 module’s supported types for SQLite: one of
NoneType, int, float, str, bytes.

There are two ways to enable the *note sqlite3: f3. module to adapt a
custom Python type to one of the supported ones.

* Menu:

* Letting your object adapt itself::
* Registering an adapter callable::


File: python.info,  Node: Letting your object adapt itself,  Next: Registering an adapter callable,  Up: Using adapters to store additional Python types in SQLite databases

5.12.6.9 Letting your object adapt itself
.........................................

This is a good approach if you write the class yourself.  Let’s suppose
you have a class like this:

     class Point:
         def __init__(self, x, y):
             self.x, self.y = x, y

Now you want to store the point in a single SQLite column.  First you’ll
have to choose one of the supported types first to be used for
representing the point.  Let’s just use str and separate the coordinates
using a semicolon.  Then you need to give your class a method
‘__conform__(self, protocol)’ which must return the converted value.
The parameter `protocol' will be ‘PrepareProtocol’.

     import sqlite3

     class Point:
         def __init__(self, x, y):
             self.x, self.y = x, y

         def __conform__(self, protocol):
             if protocol is sqlite3.PrepareProtocol:
                 return "%f;%f" % (self.x, self.y)

     con = sqlite3.connect(":memory:")
     cur = con.cursor()

     p = Point(4.0, -3.2)
     cur.execute("select ?", (p,))
     print(cur.fetchone()[0])

     con.close()


File: python.info,  Node: Registering an adapter callable,  Prev: Letting your object adapt itself,  Up: Using adapters to store additional Python types in SQLite databases

5.12.6.10 Registering an adapter callable
.........................................

The other possibility is to create a function that converts the type to
the string representation and register the function with *note
register_adapter(): 1d0f.

     import sqlite3

     class Point:
         def __init__(self, x, y):
             self.x, self.y = x, y

     def adapt_point(point):
         return "%f;%f" % (point.x, point.y)

     sqlite3.register_adapter(Point, adapt_point)

     con = sqlite3.connect(":memory:")
     cur = con.cursor()

     p = Point(4.0, -3.2)
     cur.execute("select ?", (p,))
     print(cur.fetchone()[0])

     con.close()

The *note sqlite3: f3. module has two default adapters for Python’s
built-in *note datetime.date: 194. and *note datetime.datetime: 195.
types.  Now let’s suppose we want to store *note datetime.datetime: 195.
objects not in ISO representation, but as a Unix timestamp.

     import sqlite3
     import datetime
     import time

     def adapt_datetime(ts):
         return time.mktime(ts.timetuple())

     sqlite3.register_adapter(datetime.datetime, adapt_datetime)

     con = sqlite3.connect(":memory:")
     cur = con.cursor()

     now = datetime.datetime.now()
     cur.execute("select ?", (now,))
     print(cur.fetchone()[0])

     con.close()


File: python.info,  Node: Converting SQLite values to custom Python types,  Next: Default adapters and converters,  Prev: Using adapters to store additional Python types in SQLite databases,  Up: SQLite and Python types

5.12.6.11 Converting SQLite values to custom Python types
.........................................................

Writing an adapter lets you send custom Python types to SQLite.  But to
make it really useful we need to make the Python to SQLite to Python
roundtrip work.

Enter 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 `always' get called with a *note bytes:
     336. object, no matter under which data type you sent the value to
     SQLite.

     def convert_point(s):
         x, y = map(float, s.split(b";"))
         return Point(x, y)

Now you need to make the *note sqlite3: f3. module know that what you
select from the database is actually a point.  There are two ways of
doing this:

   * Implicitly via the declared type

   * Explicitly via the column name

Both ways are described in section *note Module functions and constants:
1d04, in the entries for the constants *note PARSE_DECLTYPES: 1d09. and
*note PARSE_COLNAMES: 1d0a.

The following example illustrates both approaches.

     import sqlite3

     class Point:
         def __init__(self, x, y):
             self.x, self.y = x, y

         def __repr__(self):
             return "(%f;%f)" % (self.x, self.y)

     def adapt_point(point):
         return ("%f;%f" % (point.x, point.y)).encode('ascii')

     def convert_point(s):
         x, y = list(map(float, s.split(b";")))
         return Point(x, y)

     # Register the adapter
     sqlite3.register_adapter(Point, adapt_point)

     # Register the converter
     sqlite3.register_converter("point", convert_point)

     p = Point(4.0, -3.2)

     #########################
     # 1) Using declared types
     con = sqlite3.connect(":memory:", detect_types=sqlite3.PARSE_DECLTYPES)
     cur = con.cursor()
     cur.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()

     #######################
     # 1) Using column names
     con = sqlite3.connect(":memory:", detect_types=sqlite3.PARSE_COLNAMES)
     cur = con.cursor()
     cur.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: Default adapters and converters,  Prev: Converting SQLite values to custom Python types,  Up: SQLite and Python types

5.12.6.12 Default adapters and converters
.........................................

There are default adapters for the date and datetime types in the
datetime module.  They will be sent as ISO dates/ISO timestamps to
SQLite.

The default converters are registered under the name "date" for *note
datetime.date: 194. and under the name "timestamp" for *note
datetime.datetime: 195.

This way, you can use date/timestamps from Python without any additional
fiddling in most cases.  The format of the adapters is also compatible
with the experimental SQLite date/time functions.

The following example demonstrates this.

     import sqlite3
     import datetime

     con = sqlite3.connect(":memory:", detect_types=sqlite3.PARSE_DECLTYPES|sqlite3.PARSE_COLNAMES)
     cur = con.cursor()
     cur.execute("create table test(d date, ts timestamp)")

     today = datetime.date.today()
     now = datetime.datetime.now()

     cur.execute("insert into test(d, ts) values (?, ?)", (today, now))
     cur.execute("select d, ts from test")
     row = cur.fetchone()
     print(today, "=>", row[0], type(row[0]))
     print(now, "=>", row[1], type(row[1]))

     cur.execute('select current_date as "d [date]", current_timestamp as "ts [timestamp]"')
     row = cur.fetchone()
     print("current_date", row[0], type(row[0]))
     print("current_timestamp", row[1], type(row[1]))

     con.close()

If a timestamp stored in SQLite has a fractional part longer than 6
numbers, its value will be truncated to microsecond precision by the
timestamp converter.


File: python.info,  Node: Controlling Transactions,  Next: Using sqlite3 efficiently,  Prev: SQLite and Python types,  Up: sqlite3 --- DB-API 2 0 interface for SQLite databases

5.12.6.13 Controlling Transactions
..................................

The underlying ‘sqlite3’ library operates in ‘autocommit’ mode by
default, but the Python *note sqlite3: f3. module by default does not.

‘autocommit’ mode means that statements that modify the database take
effect immediately.  A ‘BEGIN’ or ‘SAVEPOINT’ statement disables
‘autocommit’ mode, and a ‘COMMIT’, a ‘ROLLBACK’, or a ‘RELEASE’ that
ends the outermost transaction, turns ‘autocommit’ mode back on.

The Python *note sqlite3: f3. module by default issues a ‘BEGIN’
statement implicitly before a Data Modification Language (DML) statement
(i.e.  ‘INSERT’/‘UPDATE’/‘DELETE’/‘REPLACE’).

You can control which kind of ‘BEGIN’ statements *note sqlite3: f3.
implicitly executes via the `isolation_level' parameter to the *note
connect(): 3df. call, or via the ‘isolation_level’ property of
connections.  If you specify no `isolation_level', a plain ‘BEGIN’ is
used, which is equivalent to specifying ‘DEFERRED’.  Other possible
values are ‘IMMEDIATE’ and ‘EXCLUSIVE’.

You can disable the *note sqlite3: f3. module’s implicit transaction
management by setting ‘isolation_level’ to ‘None’.  This will leave the
underlying ‘sqlite3’ library operating in ‘autocommit’ mode.  You can
then completely control the transaction state by explicitly issuing
‘BEGIN’, ‘ROLLBACK’, ‘SAVEPOINT’, and ‘RELEASE’ statements in your code.

3.6 版更變: *note sqlite3: f3. used to implicitly commit an open
transaction before DDL statements.  This is no longer the case.


File: python.info,  Node: Using sqlite3 efficiently,  Prev: Controlling Transactions,  Up: sqlite3 --- DB-API 2 0 interface for SQLite databases

5.12.6.14 Using ‘sqlite3’ efficiently
.....................................

* Menu:

* Using shortcut methods::
* Accessing columns by name instead of by index::
* Using the connection as a context manager::


File: python.info,  Node: Using shortcut methods,  Next: Accessing columns by name instead of by index,  Up: Using sqlite3 efficiently

5.12.6.15 Using shortcut methods
................................

Using the nonstandard ‘execute()’, ‘executemany()’ and ‘executescript()’
methods of the *note Connection: 3dd. object, your code can be written
more concisely because you don’t have to create the (often superfluous)
*note Cursor: 1cff. objects explicitly.  Instead, the *note Cursor:
1cff. 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: 3dd. object.

     import sqlite3

     persons = [
         ("Hugo", "Boss"),
         ("Calvin", "Klein")
         ]

     con = sqlite3.connect(":memory:")

     # Create the table
     con.execute("create table person(firstname, lastname)")

     # Fill the table
     con.executemany("insert into person(firstname, lastname) values (?, ?)", persons)

     # Print the table contents
     for row in con.execute("select firstname, lastname from person"):
         print(row)

     print("I just deleted", con.execute("delete from person").rowcount, "rows")

     # close is not a shortcut method and it's not called automatically,
     # so the connection object should be closed manually
     con.close()


File: python.info,  Node: Accessing columns by name instead of by index,  Next: Using the connection as a context manager,  Prev: Using shortcut methods,  Up: Using sqlite3 efficiently

5.12.6.16 Accessing columns by name instead of by index
.......................................................

One useful feature of the *note sqlite3: f3. module is the built-in
*note sqlite3.Row: 763. class designed to be used as a row factory.

Rows wrapped with this class can be accessed both by index (like tuples)
and case-insensitively by name:

     import sqlite3

     con = sqlite3.connect(":memory:")
     con.row_factory = sqlite3.Row

     cur = con.cursor()
     cur.execute("select 'John' as name, 42 as age")
     for row in cur:
         assert row[0] == row["name"]
         assert row["name"] == row["nAmE"]
         assert row[1] == row["age"]
         assert row[1] == row["AgE"]

     con.close()


File: python.info,  Node: Using the connection as a context manager,  Prev: Accessing columns by name instead of by index,  Up: Using sqlite3 efficiently

5.12.6.17 Using the connection as a context manager
...................................................

Connection objects can be used as context managers that automatically
commit or rollback transactions.  In the event of an exception, the
transaction is rolled back; otherwise, the transaction is committed:

     import sqlite3

     con = sqlite3.connect(":memory:")
     con.execute("create table person (id integer primary key, firstname varchar unique)")

     # Successful, con.commit() is called automatically afterwards
     with con:
         con.execute("insert into person(firstname) values (?)", ("Joe",))

     # 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 person(firstname) values (?)", ("Joe",))
     except sqlite3.IntegrityError:
         print("couldn't add Joe 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: 資料壓縮與保存,  Next: 檔案格式,  Prev: Data Persistence,  Up: Python 標準函式庫 Standard Library

5.13 資料壓縮與保存
===================

The modules described in this chapter support data compression with the
zlib, gzip, bzip2 and lzma algorithms, and the creation of ZIP- and
tar-format archives.  See also *note Archiving operations: b9b. provided
by the *note shutil: ea. module.

* Menu:

* zlib: zlib --- Compression compatible with gzip. Compression compatible with gzip
* gzip: gzip --- Support for gzip files. Support for gzip files
* bz2: bz2 --- Support for bzip2 compression. Support for bzip2 compression
* lzma: lzma --- Compression using the LZMA algorithm. Compression using the LZMA algorithm
* zipfile: zipfile --- Work with ZIP archives. Work with ZIP archives
* tarfile: tarfile --- Read and write tar archive files. Read and write tar archive files


File: python.info,  Node: zlib --- Compression compatible with gzip,  Next: gzip --- Support for gzip files,  Up: 資料壓縮與保存

5.13.1 ‘zlib’ — Compression compatible with ‘gzip’
--------------------------------------------------

__________________________________________________________________

For applications that require data compression, the functions in this
module allow compression and decompression, using the zlib library.  The
zlib library has its own home page at ‘http://www.zlib.net’.  There are
known incompatibilities between the Python module and versions of the
zlib library earlier than 1.1.3; 1.1.3 has a security vulnerability, so
we recommend using 1.1.4 or later.

zlib’s functions have many options and often need to be used in a
particular order.  This documentation doesn’t attempt to cover all of
the permutations; consult the zlib manual at
‘http://www.zlib.net/manual.html’ for authoritative information.

For reading and writing ‘.gz’ files see the *note gzip: 8c. module.

The available exception and functions in this module are:

 -- 例外: zlib.error

     Exception raised on compression and decompression errors.

 -- 函式: zlib.adler32 (data[, value])

     Computes an Adler-32 checksum of `data'.  (An Adler-32 checksum is
     almost as reliable as a CRC32 but can be computed much more
     quickly.)  The result is an unsigned 32-bit integer.  If `value' is
     present, it is used as the starting value of the checksum;
     otherwise, a default value of 1 is used.  Passing in `value' allows
     computing a running checksum over the concatenation of several
     inputs.  The algorithm is not cryptographically strong, and should
     not be used for authentication or digital signatures.  Since the
     algorithm is designed for use as a checksum algorithm, it is not
     suitable for use as a general hash algorithm.

     3.0 版更變: Always returns an unsigned value.  To generate the same
     numeric value across all Python versions and platforms, use
     ‘adler32(data) & 0xffffffff’.

 -- 函式: zlib.compress (data, level=-1)

     Compresses the bytes in `data', returning a bytes object containing
     compressed data.  `level' is an integer from ‘0’ to ‘9’ or ‘-1’
     controlling the level of compression; ‘1’ (Z_BEST_SPEED) is fastest
     and produces the least compression, ‘9’ (Z_BEST_COMPRESSION) is
     slowest and produces the most.  ‘0’ (Z_NO_COMPRESSION) is no
     compression.  The default value is ‘-1’ (Z_DEFAULT_COMPRESSION).
     Z_DEFAULT_COMPRESSION represents a default compromise between speed
     and compression (currently equivalent to level 6).  Raises the
     *note error: 1d47. exception if any error occurs.

     3.6 版更變: `level' can now be used as a keyword parameter.

 -- 函式: zlib.compressobj (level=-1, method=DEFLATED, wbits=MAX_WBITS,
          memLevel=DEF_MEM_LEVEL, strategy=Z_DEFAULT_STRATEGY[, zdict])

     Returns a compression object, to be used for compressing data
     streams that won’t fit into memory at once.

     `level' is the compression level – an integer from ‘0’ to ‘9’ or
     ‘-1’.  A value of ‘1’ (Z_BEST_SPEED) is fastest and produces the
     least compression, while a value of ‘9’ (Z_BEST_COMPRESSION) is
     slowest and produces the most.  ‘0’ (Z_NO_COMPRESSION) is no
     compression.  The default value is ‘-1’ (Z_DEFAULT_COMPRESSION).
     Z_DEFAULT_COMPRESSION represents a default compromise between speed
     and compression (currently equivalent to level 6).

     `method' is the compression algorithm.  Currently, the only
     supported value is ‘DEFLATED’.

     The `wbits' argument controls the size of the history buffer (or
     the "window size") used when compressing data, and whether a header
     and trailer is included in the output.  It can take several ranges
     of values, defaulting to ‘15’ (MAX_WBITS):

        * +9 to +15: The base-two logarithm of the window size, which
          therefore ranges between 512 and 32768.  Larger values produce
          better compression at the expense of greater memory usage.
          The resulting output will include a zlib-specific header and
          trailer.

        * −9 to −15: Uses the absolute value of `wbits' as the window
          size logarithm, while producing a raw output stream with no
          header or trailing checksum.

        * +25 to +31 = 16 + (9 to 15): Uses the low 4 bits of the value
          as the window size logarithm, while including a basic ‘gzip’
          header and trailing checksum in the output.

     The `memLevel' argument controls the amount of memory used for the
     internal compression state.  Valid values range from ‘1’ to ‘9’.
     Higher values use more memory, but are faster and produce smaller
     output.

     `strategy' is used to tune the compression algorithm.  Possible
     values are ‘Z_DEFAULT_STRATEGY’, ‘Z_FILTERED’, ‘Z_HUFFMAN_ONLY’,
     ‘Z_RLE’ (zlib 1.2.0.1) and ‘Z_FIXED’ (zlib 1.2.2.2).

     `zdict' is a predefined compression dictionary.  This is a sequence
     of bytes (such as a *note bytes: 336. object) containing
     subsequences that are expected to occur frequently in the data that
     is to be compressed.  Those subsequences that are expected to be
     most common should come at the end of the dictionary.

     3.3 版更變: Added the `zdict' parameter and keyword argument
     support.

 -- 函式: zlib.crc32 (data[, value])

     Computes a CRC (Cyclic Redundancy Check) checksum of `data'.  The
     result is an unsigned 32-bit integer.  If `value' is present, it is
     used as the starting value of the checksum; otherwise, a default
     value of 0 is used.  Passing in `value' allows computing a running
     checksum over the concatenation of several inputs.  The algorithm
     is not cryptographically strong, and should not be used for
     authentication or digital signatures.  Since the algorithm is
     designed for use as a checksum algorithm, it is not suitable for
     use as a general hash algorithm.

     3.0 版更變: Always returns an unsigned value.  To generate the same
     numeric value across all Python versions and platforms, use
     ‘crc32(data) & 0xffffffff’.

 -- 函式: zlib.decompress (data, wbits=MAX_WBITS, bufsize=DEF_BUF_SIZE)

     Decompresses the bytes in `data', returning a bytes object
     containing the uncompressed data.  The `wbits' parameter depends on
     the format of `data', and is discussed further below.  If `bufsize'
     is given, it is used as the initial size of the output buffer.
     Raises the *note error: 1d47. exception if any error occurs.  The
     `wbits' parameter controls the size of the history buffer (or
     "window size"), and what header and trailer format is expected.  It
     is similar to the parameter for *note compressobj(): 1d49, but
     accepts more ranges of values:

        * +8 to +15: The base-two logarithm of the window size.  The
          input must include a zlib header and trailer.

        * 0: Automatically determine the window size from the zlib
          header.  Only supported since zlib 1.2.3.5.

        * −8 to −15: Uses the absolute value of `wbits' as the window
          size logarithm.  The input must be a raw stream with no header
          or trailer.

        * +24 to +31 = 16 + (8 to 15): Uses the low 4 bits of the value
          as the window size logarithm.  The input must include a gzip
          header and trailer.

        * +40 to +47 = 32 + (8 to 15): Uses the low 4 bits of the value
          as the window size logarithm, and automatically accepts either
          the zlib or gzip format.

     When decompressing a stream, the window size must not be smaller
     than the size originally used to compress the stream; using a
     too-small value may result in an *note error: 1d47. exception.  The
     default `wbits' value corresponds to the largest window size and
     requires a zlib header and trailer to be included.

     `bufsize' is the initial size of the buffer used to hold
     decompressed data.  If more space is required, the buffer size will
     be increased as needed, so you don’t have to get this value exactly
     right; tuning it will only save a few calls to ‘malloc()’.

     3.6 版更變: `wbits' and `bufsize' can be used as keyword arguments.

 -- 函式: zlib.decompressobj (wbits=MAX_WBITS[, zdict])

     Returns a decompression object, to be used for decompressing data
     streams that won’t fit into memory at once.

     The `wbits' parameter controls the size of the history buffer (or
     the "window size"), and what header and trailer format is expected.
     It has the same meaning as *note described for decompress(): 1d4b.

     The `zdict' parameter specifies a predefined compression
     dictionary.  If provided, this must be the same dictionary as was
     used by the compressor that produced the data that is to be
     decompressed.

          備註: If `zdict' is a mutable object (such as a *note
          bytearray: 337.), you must not modify its contents between the
          call to *note decompressobj(): 1d4c. and the first call to the
          decompressor’s ‘decompress()’ method.

     3.3 版更變: Added the `zdict' parameter.

Compression objects support the following methods:

 -- 成員函式: Compress.compress (data)

     Compress `data', returning a bytes object containing compressed
     data for at least part of the data in `data'.  This data should be
     concatenated to the output produced by any preceding calls to the
     *note compress(): 5c3. method.  Some input may be kept in internal
     buffers for later processing.

 -- 成員函式: Compress.flush ([mode])

     All pending input is processed, and a bytes object containing the
     remaining compressed output is returned.  `mode' can be selected
     from the constants ‘Z_NO_FLUSH’, ‘Z_PARTIAL_FLUSH’, ‘Z_SYNC_FLUSH’,
     ‘Z_FULL_FLUSH’, ‘Z_BLOCK’ (zlib 1.2.3.4), or ‘Z_FINISH’, defaulting
     to ‘Z_FINISH’.  Except ‘Z_FINISH’, all constants allow compressing
     further bytestrings of data, while ‘Z_FINISH’ finishes the
     compressed stream and prevents compressing any more data.  After
     calling *note flush(): 1d4e. with `mode' set to ‘Z_FINISH’, the
     *note compress(): 5c3. method cannot be called again; the only
     realistic action is to delete the object.

 -- 成員函式: Compress.copy ()

     Returns a copy of the compression object.  This can be used to
     efficiently compress a set of data that share a common initial
     prefix.

3.8 版更變: Added *note copy.copy(): 3d0. and *note copy.deepcopy():
3d1. support to compression objects.

Decompression objects support the following methods and attributes:

 -- 屬性: Decompress.unused_data

     A bytes object which contains any bytes past the end of the
     compressed data.  That is, this remains ‘b""’ until the last byte
     that contains compression data is available.  If the whole
     bytestring turned out to contain compressed data, this is ‘b""’, an
     empty bytes object.

 -- 屬性: Decompress.unconsumed_tail

     A bytes object that contains any data that was not consumed by the
     last *note decompress(): 5c4. call because it exceeded the limit
     for the uncompressed data buffer.  This data has not yet been seen
     by the zlib machinery, so you must feed it (possibly with further
     data concatenated to it) back to a subsequent *note decompress():
     5c4. method call in order to get correct output.

 -- 屬性: Decompress.eof

     A boolean indicating whether the end of the compressed data stream
     has been reached.

     This makes it possible to distinguish between a properly-formed
     compressed stream, and an incomplete or truncated one.

     3.3 版新加入.

 -- 成員函式: Decompress.decompress (data, max_length=0)

     Decompress `data', returning a bytes object containing the
     uncompressed data corresponding to at least part of the data in
     `string'.  This data should be concatenated to the output produced
     by any preceding calls to the *note decompress(): 5c4. method.
     Some of the input data may be preserved in internal buffers for
     later processing.

     If the optional parameter `max_length' is non-zero then the return
     value will be no longer than `max_length'.  This may mean that not
     all of the compressed input can be processed; and unconsumed data
     will be stored in the attribute *note unconsumed_tail: 1d51.  This
     bytestring must be passed to a subsequent call to *note
     decompress(): 5c4. if decompression is to continue.  If
     `max_length' is zero then the whole input is decompressed, and
     *note unconsumed_tail: 1d51. is empty.

     3.6 版更變: `max_length' can be used as a keyword argument.

 -- 成員函式: Decompress.flush ([length])

     All pending input is processed, and a bytes object containing the
     remaining uncompressed output is returned.  After calling *note
     flush(): 1d53, the *note decompress(): 5c4. method cannot be called
     again; the only realistic action is to delete the object.

     The optional parameter `length' sets the initial size of the output
     buffer.

 -- 成員函式: Decompress.copy ()

     Returns a copy of the decompression object.  This can be used to
     save the state of the decompressor midway through the data stream
     in order to speed up random seeks into the stream at a future
     point.

3.8 版更變: Added *note copy.copy(): 3d0. and *note copy.deepcopy():
3d1. support to decompression objects.

Information about the version of the zlib library in use is available
through the following constants:

 -- Data: zlib.ZLIB_VERSION

     The version string of the zlib library that was used for building
     the module.  This may be different from the zlib library actually
     used at runtime, which is available as *note ZLIB_RUNTIME_VERSION:
     acc.

 -- Data: zlib.ZLIB_RUNTIME_VERSION

     The version string of the zlib library actually loaded by the
     interpreter.

     3.3 版新加入.

也參考
......

Module *note gzip: 8c.

     Reading and writing ‘gzip’-format files.

‘http://www.zlib.net’

     The zlib library home page.

‘http://www.zlib.net/manual.html’

     The zlib manual explains the semantics and usage of the library’s
     many functions.


File: python.info,  Node: gzip --- Support for gzip files,  Next: bz2 --- Support for bzip2 compression,  Prev: zlib --- Compression compatible with gzip,  Up: 資料壓縮與保存

5.13.2 ‘gzip’ — Support for ‘gzip’ files
----------------------------------------

`Source code:' 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: 145. module.

The *note gzip: 8c. module provides the *note GzipFile: 6e2. class, as
well as the *note open(): 1d58, *note compress(): 1d2. and *note
decompress(): b8e. convenience functions.  The *note GzipFile: 6e2.
class reads and writes ‘gzip’-format files, automatically compressing or
decompressing the data so that it looks like an ordinary *note file
object: b47.

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.

The module defines the following items:

 -- 函式: 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: b47.

     The `filename' argument can be an actual filename (a *note str:
     335. or *note bytes: 336. 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: 6e2. constructor.

     For binary mode, this function is equivalent to the *note GzipFile:
     6e2. constructor: ‘GzipFile(filename, mode, compresslevel)’.  In
     this case, the `encoding', `errors' and `newline' arguments must
     not be provided.

     For text mode, a *note GzipFile: 6e2. object is created, and
     wrapped in an *note io.TextIOWrapper: 5f8. 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 版更變: Added support for the ‘'x'’, ‘'xb'’ and ‘'xt'’ modes.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 例外: gzip.BadGzipFile

     An exception raised for invalid gzip files.  It inherits *note
     OSError: 1d4.  *note EOFError: c71. and *note zlib.error: 1d47. 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: 6e2. class, which simulates
     most of the methods of a *note file object: b47, with the exception
     of the ‘truncate()’ 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: 7a0. 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'’.

     Note that the file is always opened in binary mode.  To open a
     compressed file in text mode, use *note open(): 1d58. (or wrap your
     *note GzipFile: 6e2. with an *note io.TextIOWrapper: 5f8.).

     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 `mtime' argument is an optional numeric timestamp to be written
     to the last modification time field in the stream when compressing.
     It should only be provided in compression mode.  If omitted or
     ‘None’, the current time is used.  See the *note mtime: 1d59.
     attribute for more details.

     Calling a *note GzipFile: 6e2. 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: 7a0. object opened for writing as `fileobj', and
     retrieve the resulting memory buffer using the *note io.BytesIO:
     7a0. object’s *note getvalue(): 1d5a. method.

     *note GzipFile: 6e2. supports the *note io.BufferedIOBase: 58d.
     interface, including iteration and the *note with: 6ee. statement.
     Only the ‘truncate()’ method isn’t implemented.

     *note GzipFile: 6e2. also provides the following method and
     attribute:

      -- 成員函式: 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(): b8d. does not change
               the file position of the *note GzipFile: 6e2, it may
               change the position of the underlying file object (e.g.
               if the *note GzipFile: 6e2. was constructed with the
               `fileobj' parameter).

          3.2 版新加入.

      -- 屬性: mtime

          When decompressing, the value of the last modification time
          field in the most recently read header may be read from this
          attribute, as an integer.  The initial value before reading
          any headers is ‘None’.

          All ‘gzip’ compressed streams are required to contain this
          timestamp field.  Some programs, such as ‘gunzip’, make use of
          the timestamp.  The format is the same as the return value of
          *note time.time(): 322. and the *note st_mtime: 1d5b.
          attribute of the object returned by *note os.stat(): 1f2.

     3.1 版更變: Support for the *note with: 6ee. statement was added,
     along with the `mtime' constructor argument and *note mtime: 1d59.
     attribute.

     3.2 版更變: Support for zero-padded and unseekable files was added.

     3.3 版更變: The *note io.BufferedIOBase.read1(): 1d5c. method is
     now implemented.

     3.4 版更變: Added support for the ‘'x'’ and ‘'xb'’ modes.

     3.5 版更變: Added support for writing arbitrary *note bytes-like
     objects: 5ed.  The *note read(): 1d5d. method now accepts an
     argument of ‘None’.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: gzip.compress (data, compresslevel=9, *, mtime=None)

     Compress the `data', returning a *note bytes: 336. object
     containing the compressed data.  `compresslevel' and `mtime' have
     the same meaning as in the *note GzipFile: 6e2. constructor above.

     3.2 版新加入.

     3.8 版更變: Added the `mtime' parameter for reproducible output.

 -- 函式: gzip.decompress (data)

     Decompress the `data', returning a *note bytes: 336. object
     containing the uncompressed data.

     3.2 版新加入.

* Menu:

* Examples of usage::
* Command Line Interface::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/gzip.py


File: python.info,  Node: Examples of usage,  Next: Command Line Interface,  Up: gzip --- Support for gzip files

5.13.2.1 Examples of usage
..........................

Example of how to read a compressed file:

     import gzip
     with gzip.open('/home/joe/file.txt.gz', 'rb') as f:
         file_content = f.read()

Example of how to create a compressed GZIP file:

     import gzip
     content = b"Lots of content here"
     with gzip.open('/home/joe/file.txt.gz', 'wb') as f:
         f.write(content)

Example of how to GZIP compress an existing file:

     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)

Example of how to GZIP compress a binary string:

     import gzip
     s_in = b"Lots of content here"
     s_out = gzip.compress(s_in)

也參考
......

Module *note zlib: 145.

     The basic data compression module needed to support the ‘gzip’ file
     format.


File: python.info,  Node: Command Line Interface,  Prev: Examples of usage,  Up: gzip --- Support for gzip files

5.13.2.2 Command Line Interface
...............................

The *note gzip: 8c. module provides a simple command line interface to
compress or decompress files.

Once executed the *note gzip: 8c. 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:

* Command line options::


File: python.info,  Node: Command line options,  Up: Command Line Interface

5.13.2.3 Command line options
.............................

 -- 程式選項: file

     If `file' is not specified, read from *note sys.stdin: 312.

 -- 程式選項: --fast

     Indicates the fastest compression method (less compression).

 -- 程式選項: --best

     Indicates the slowest compression method (best compression).

 -- 程式選項: -d, --decompress

     Decompress the given file.

 -- 程式選項: -h, --help

     Show the help message.


File: python.info,  Node: bz2 --- Support for bzip2 compression,  Next: lzma --- Compression using the LZMA algorithm,  Prev: gzip --- Support for gzip files,  Up: 資料壓縮與保存

5.13.3 ‘bz2’ — Support for ‘bzip2’ compression
----------------------------------------------

`Source code:' Lib/bz2.py(1)

__________________________________________________________________

This module provides a comprehensive interface for compressing and
decompressing data using the bzip2 compression algorithm.

The *note bz2: 14. module contains:

   * The *note open(): 9db. function and *note BZ2File: 936. class for
     reading and writing compressed files.

   * The *note BZ2Compressor: 1d69. and *note BZ2Decompressor: 1d6a.
     classes for incremental (de)compression.

   * The *note compress(): 187b. and *note decompress(): 9dc. functions
     for one-shot (de)compression.

All of the classes in this module may safely be accessed from multiple
threads.

* Menu:

* (De)compression of files: De compression of files.
* Incremental (de)compression: Incremental de compression.
* One-shot (de)compression: One-shot de compression.
* Examples of usage: Examples of usage<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/bz2.py


File: python.info,  Node: De compression of files,  Next: Incremental de compression,  Up: bz2 --- Support for bzip2 compression

5.13.3.1 (De)compression of files
.................................

 -- 函式: bz2.open (filename, mode='r', compresslevel=9, encoding=None,
          errors=None, newline=None)

     Open a bzip2-compressed file in binary or text mode, returning a
     *note file object: b47.

     As with the constructor for *note BZ2File: 936, the `filename'
     argument can be an actual filename (a *note str: 335. or *note
     bytes: 336. 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: 936. constructor.

     For binary mode, this function is equivalent to the *note BZ2File:
     936. 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: 936. object is created, and wrapped
     in an *note io.TextIOWrapper: 5f8. 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: 36f.

 -- 類別: bz2.BZ2File (filename, mode='r', buffering=None,
          compresslevel=9)

     Open a bzip2-compressed file in binary mode.

     If `filename' is a *note str: 335. or *note bytes: 336. object,
     open the named file directly.  Otherwise, `filename' should be a
     *note file object: b47, 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'’.

     The `buffering' argument is ignored.  Its use is deprecated since
     Python 3.0.

     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: 936. provides all of the members specified by the
     *note io.BufferedIOBase: 58d, except for ‘detach()’ and
     ‘truncate()’.  Iteration and the *note with: 6ee. statement are
     supported.

     *note BZ2File: 936. also provides the following method:

      -- 成員函式: 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(): 1d6c. does not change
               the file position of the *note BZ2File: 936, it may
               change the position of the underlying file object (e.g.
               if the *note BZ2File: 936. was constructed by passing a
               file object for `filename').

          3.3 版新加入.

     3.0 版後已棄用: The keyword argument `buffering' was deprecated and
     is now ignored.

     3.1 版更變: Support for the *note with: 6ee. statement was added.

     3.3 版更變: The ‘fileno()’, ‘readable()’, ‘seekable()’,
     ‘writable()’, ‘read1()’ and ‘readinto()’ methods were added.

     3.3 版更變: Support was added for `filename' being a *note file
     object: b47. instead of an actual filename.

     3.3 版更變: 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(): 1d5d. method now accepts an argument
     of ‘None’.

     3.6 版更變: Accepts a *note path-like object: 36f.


File: python.info,  Node: Incremental de compression,  Next: One-shot de compression,  Prev: De compression of files,  Up: bz2 --- Support for bzip2 compression

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(): 187b. 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(): 1d6f. 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(): 9dc. function instead.

          備註: This class does not transparently handle inputs
          containing multiple compressed streams, unlike *note
          decompress(): 9dc. and *note BZ2File: 936.  If you need to
          decompress a multi-stream input with *note BZ2Decompressor:
          1d6a, you must use a new decompressor for each stream.

      -- 成員函式: decompress (data, max_length=-1)

          Decompress `data' (a *note bytes-like object: 5ed.), returning
          uncompressed data as bytes.  Some of `data' may be buffered
          internally, for use in later calls to *note decompress(): 9dc.
          The returned data should be concatenated with the output of
          any previous calls to *note decompress(): 9dc.

          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: 1d70.
          attribute will be set to ‘False’.  In this case, the next call
          to *note decompress(): 6a8. 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: 1d70.
          attribute will be set to ‘True’.

          Attempting to decompress data after the end of stream is
          reached raises an ‘EOFError’.  Any data found after the end of
          the stream is ignored and saved in the *note unused_data:
          1d71. attribute.

          3.5 版更變: Added the `max_length' parameter.

      -- 屬性: 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(): 6a8. method can provide
          more decompressed data before requiring new uncompressed
          input.

          3.5 版新加入.


File: python.info,  Node: One-shot de compression,  Next: Examples of usage<2>,  Prev: Incremental de compression,  Up: bz2 --- Support for bzip2 compression

5.13.3.3 One-shot (de)compression
.................................

 -- 函式: bz2.compress (data, compresslevel=9)

     Compress `data', a *note bytes-like object: 5ed.

     `compresslevel', if given, must be an integer between ‘1’ and ‘9’.
     The default is ‘9’.

     For incremental compression, use a *note BZ2Compressor: 1d69.
     instead.

 -- 函式: bz2.decompress (data)

     Decompress `data', a *note bytes-like object: 5ed.

     If `data' is the concatenation of multiple compressed streams,
     decompress all of the streams.

     For incremental decompression, use a *note BZ2Decompressor: 1d6a.
     instead.

     3.3 版更變: Support for multi-stream inputs was added.


File: python.info,  Node: Examples of usage<2>,  Prev: One-shot de compression,  Up: bz2 --- Support for bzip2 compression

5.13.3.4 Examples of usage
..........................

Below are some examples of typical usage of the *note bz2: 14. module.

Using *note compress(): 187b. and *note decompress(): 9dc. 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: 1d69. 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 --- Compression using the LZMA algorithm,  Next: zipfile --- Work with ZIP archives,  Prev: bz2 --- Support for bzip2 compression,  Up: 資料壓縮與保存

5.13.4 ‘lzma’ — Compression using the LZMA algorithm
----------------------------------------------------

3.3 版新加入.

`Source code:' 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: 14. module.  However, note that *note LZMAFile: 937. is `not'
thread-safe, unlike *note bz2.BZ2File: 936, so if you need to use a
single *note LZMAFile: 937. 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: Miscellaneous<2>.
* Specifying custom filter chains::
* Examples: Examples<5>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/lzma.py


File: python.info,  Node: Reading and writing compressed files,  Next: Compressing and decompressing data in memory,  Up: lzma --- Compression using the LZMA algorithm

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: b47.

     The `filename' argument can be either an actual file name (given as
     a *note str: 335, *note bytes: 336. or *note path-like: 36f.
     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:
     1d7b.  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: 1d7c.

     For binary mode, this function is equivalent to the *note LZMAFile:
     937. constructor: ‘LZMAFile(filename, mode, ...)’.  In this case,
     the `encoding', `errors' and `newline' arguments must not be
     provided.

     For text mode, a *note LZMAFile: 937. object is created, and
     wrapped in an *note io.TextIOWrapper: 5f8. instance with the
     specified encoding, error handling behavior, and line ending(s).

     3.4 版更變: Added support for the ‘"x"’, ‘"xb"’ and ‘"xt"’ modes.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 類別: 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: 937. can wrap an already-open *note file object:
     b47, 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: 335, *note bytes: 336. or *note path-like:
     36f. object).  When wrapping an existing file object, the wrapped
     file will not be closed when the *note LZMAFile: 937. 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:
     1d7b.  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: 1d7c.

     *note LZMAFile: 937. supports all the members specified by *note
     io.BufferedIOBase: 58d, except for ‘detach()’ and ‘truncate()’.
     Iteration and the *note with: 6ee. statement are supported.

     The following method is 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(): 1d7d. does not change
               the file position of the *note LZMAFile: 937, it may
               change the position of the underlying file object (e.g.
               if the *note LZMAFile: 937. was constructed by passing a
               file object for `filename').

     3.4 版更變: Added support for the ‘"x"’ and ‘"xb"’ modes.

     3.5 版更變: The *note read(): 1d5d. method now accepts an argument
     of ‘None’.

     3.6 版更變: Accepts a *note path-like object: 36f.


File: python.info,  Node: Compressing and decompressing data in memory,  Next: Miscellaneous<2>,  Prev: Reading and writing compressed files,  Up: lzma --- Compression using the LZMA algorithm

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(): 1d7f.

     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: 1d7b.).

     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: 1d78.
     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: 1d7c. 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: 1d80. for
     details.

      -- 成員函式: compress (data)

          Compress `data' (a *note bytes: 336. object), returning a
          *note bytes: 336. 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(): 1d7f.
          and *note flush(): 1d82.  The returned data should be
          concatenated with the output of any previous calls to *note
          compress(): 1d7f.

      -- 成員函式: flush ()

          Finish the compression process, returning a *note bytes: 336.
          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(): 1d83.

     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: 1d78. 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: 1d80. for more
     information about filter chains.

          備註: This class does not transparently handle inputs
          containing multiple compressed streams, unlike *note
          decompress(): 1d83. and *note LZMAFile: 937.  To decompress a
          multi-stream input with *note LZMADecompressor: 1d7b, you must
          create a new decompressor for each stream.

      -- 成員函式: decompress (data, max_length=-1)

          Decompress `data' (a *note bytes-like object: 5ed.), returning
          uncompressed data as bytes.  Some of `data' may be buffered
          internally, for use in later calls to *note decompress():
          1d83.  The returned data should be concatenated with the
          output of any previous calls to *note decompress(): 1d83.

          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: 1d84.
          attribute will be set to ‘False’.  In this case, the next call
          to *note decompress(): 719. 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: 1d84.
          attribute will be set to ‘True’.

          Attempting to decompress data after the end of stream is
          reached raises an ‘EOFError’.  Any data found after the end of
          the stream is ignored and saved in the *note unused_data:
          1d85. attribute.

          3.5 版更變: Added the `max_length' parameter.

      -- 屬性: 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(): 719. 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: 336. object), returning the
     compressed data as a *note bytes: 336. object.

     See *note LZMACompressor: 1d7c. 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: 336. object), returning the
     uncompressed data as a *note bytes: 336. 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: 1d7b. above for a description of the
     `format', `memlimit' and `filters' arguments.


File: python.info,  Node: Miscellaneous<2>,  Next: Specifying custom filter chains,  Prev: Compressing and decompressing data in memory,  Up: lzma --- Compression using the LZMA algorithm

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: Examples<5>,  Prev: Miscellaneous<2>,  Up: lzma --- Compression using the LZMA algorithm

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: Examples<5>,  Prev: Specifying custom filter chains,  Up: lzma --- Compression using the LZMA algorithm

5.13.4.5 Examples
.................

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 --- Work with ZIP archives,  Next: tarfile --- Read and write tar archive files,  Prev: lzma --- Compression using the LZMA algorithm,  Up: 資料壓縮與保存

5.13.5 ‘zipfile’ — Work with ZIP archives
-----------------------------------------

`Source code:' Lib/zipfile.py(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: 1d8e, 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 Objects: 1d91. for constructor details.

 -- 類別: zipfile.Path

     A pathlib-compatible wrapper for zip files.  See section *note Path
     Objects: 1d92. for details.

     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(): 1d93.
     and *note infolist(): 1d94. methods of *note ZipFile: 424. objects.
     Most users of the *note zipfile: 143. 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 Objects: 1d95.

 -- 函式: 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.

 -- Data: zipfile.ZIP_STORED

     The numeric constant for an uncompressed archive member.

 -- Data: zipfile.ZIP_DEFLATED

     The numeric constant for the usual ZIP compression method.  This
     requires the *note zlib: 145. module.

 -- Data: zipfile.ZIP_BZIP2

     The numeric constant for the BZIP2 compression method.  This
     requires the *note bz2: 14. module.

     3.3 版新加入.

 -- Data: zipfile.ZIP_LZMA

     The numeric constant for the LZMA compression method.  This
     requires the *note lzma: ae. 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 Home Page(4)

     Information about the Info-ZIP project’s ZIP archive programs and
     development libraries.

* Menu:

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/zipfile.py

   (2) https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT

   (3) https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT

   (4) http://www.info-zip.org/


File: python.info,  Node: ZipFile Objects,  Next: Path Objects,  Up: zipfile --- Work with ZIP archives

5.13.5.1 ZipFile Objects
........................

 -- 類別: zipfile.ZipFile (file, mode='r', compression=ZIP_STORED,
          allowZip64=True, compresslevel=None, *,
          strict_timestamps=True)

     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: 36f.

     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: 95d. 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: 1d96, *note ZIP_DEFLATED:
     1d97, *note ZIP_BZIP2: 1d98. or *note ZIP_LZMA: 1d99.; unrecognized
     values will cause *note NotImplementedError: 613. to be raised.  If
     *note ZIP_DEFLATED: 1d97, *note ZIP_BZIP2: 1d98. or *note ZIP_LZMA:
     1d99. is specified but the corresponding module (*note zlib: 145,
     *note bz2: 14. or *note lzma: ae.) is not available, *note
     RuntimeError: 2bb. is raised.  The default is *note ZIP_STORED:
     1d96.

     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: 143. 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:
     1d96. or *note ZIP_LZMA: 1d99. it has no effect.  When using *note
     ZIP_DEFLATED: 1d97. integers ‘0’ through ‘9’ are accepted (see
     *note zlib: 1d49. for more information).  When using *note
     ZIP_BZIP2: 1d98. integers ‘1’ through ‘9’ are accepted (see *note
     bz2: 936. 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.

     If the file is created with mode ‘'w'’, ‘'x'’ or ‘'a'’ and then
     *note closed: 1d9b. 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: 6ee. 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')

     3.2 版新加入: Added the ability to use *note ZipFile: 424. as a
     context manager.

     3.3 版更變: Added support for *note bzip2: 14. and *note lzma: ae.
     compression.

     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: 2bb. was raised
     for unrecognized compression values.

     3.6.2 版更變: The `file' parameter accepts a *note path-like
     object: 36f.

     3.7 版更變: Add the `compresslevel' parameter.

     3.8 版新加入: The `strict_timestamps' keyword-only argument

 -- 成員函式: ZipFile.close ()

     Close the archive file.  You must call *note close(): 1d9b. before
     exiting your program or essential records will not be written.

 -- 成員函式: ZipFile.getinfo (name)

     Return a *note ZipInfo: 5bf. object with information about the
     archive member `name'.  Calling *note getinfo(): 1d93. for a name
     not currently contained in the archive will raise a *note KeyError:
     2c8.

 -- 成員函式: ZipFile.infolist ()

     Return a list containing a *note ZipInfo: 5bf. 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: 5bf. object.  The `mode' parameter, if included,
     must be ‘'r'’ (the default) or ‘'w'’.  `pwd' is the password used
     to decrypt encrypted ZIP files.

     *note open(): 5c1. is also a context manager and therefore supports
     the *note with: 6ee. 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(): 1d5d, *note
     readline(): 1708, *note readlines(): 1795, *note seek(): 1d9d,
     *note tell(): 1d9e, *note __iter__(): 514, *note __next__(): c69.
     These objects can operate independently of the ZipFile.

     With ‘mode='w'’, a writable file handle is returned, which supports
     the *note write(): 58e. method.  While a writable file handle is
     open, attempting to read or write other files in the ZIP file will
     raise a *note ValueError: 1fc.

     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: 5bf. object with *note
     file_size: 1d9f. set, and use that as the `name' parameter.

          備註: The *note open(): 5c1, *note read(): cbe. and *note
          extract(): 1da0. methods can take a filename or a *note
          ZipInfo: 5bf. 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: 5f8. for reading compressed text files in *note
     universal newlines: 5f9. mode.

     3.6 版更變: *note open(): 4f5. can now be used to write files into
     the archive with the ‘mode='w'’ option.

     3.6 版更變: Calling *note open(): 5c1. on a closed ZipFile will
     raise a *note ValueError: 1fc.  Previously, a *note RuntimeError:
     2bb. was raised.

 -- 成員函式: 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: 5bf. 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: 5bf. object.  `pwd' is the
     password used for encrypted files.

     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(): 1da0. on a closed ZipFile will
     raise a *note ValueError: 1fc.  Previously, a *note RuntimeError:
     2bb. was raised.

     3.6.2 版更變: The `path' parameter accepts a *note path-like
     object: 36f.

 -- 成員函式: 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(): 1d9c.  `pwd' is the password used for encrypted
     files.

          警告: 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(): 1da0.
          note.

     3.6 版更變: Calling *note extractall(): 1da1. on a closed ZipFile
     will raise a *note ValueError: 1fc.  Previously, a *note
     RuntimeError: 2bb. was raised.

     3.6.2 版更變: The `path' parameter accepts a *note path-like
     object: 36f.

 -- 成員函式: ZipFile.printdir ()

     Print a table of contents for the archive to ‘sys.stdout’.

 -- 成員函式: ZipFile.setpassword (pwd)

     Set `pwd' 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: 5bf. object.
     The archive must be open for read or append.  `pwd' is the password
     used for encrypted files and, if specified, it will override the
     default password set with *note setpassword(): 1da3.  Calling *note
     read(): cbe. on a ZipFile that uses a compression method other than
     *note ZIP_STORED: 1d96, *note ZIP_DEFLATED: 1d97, *note ZIP_BZIP2:
     1d98. or *note ZIP_LZMA: 1d99. will raise a *note
     NotImplementedError: 613.  An error will also be raised if the
     corresponding compression module is not available.

     3.6 版更變: Calling *note read(): cbe. on a closed ZipFile will
     raise a *note ValueError: 1fc.  Previously, a *note RuntimeError:
     2bb. 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(): 1da4. on a closed ZipFile will
     raise a *note ValueError: 1fc.  Previously, a *note RuntimeError:
     2bb. 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'’.

          備註: 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.

     3.6 版更變: Calling *note write(): 614. on a ZipFile created with
     mode ‘'r'’ or a closed ZipFile will raise a *note ValueError: 1fc.
     Previously, a *note RuntimeError: 2bb. 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: 335. or a *note bytes: 336. instance; if it
     is a *note str: 335, 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: 5bf. 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: 5bf. instance).
     Similarly, `compresslevel' will override the constructor if given.

          備註: When passing a *note ZipInfo: 5bf. 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: 5bf. instance.  By default, the *note ZipInfo:
          5bf. constructor sets this member to *note ZIP_STORED: 1d96.

     3.2 版更變: The `compress_type' argument.

     3.6 版更變: Calling *note writestr(): cc0. on a ZipFile created
     with mode ‘'r'’ or a closed ZipFile will raise a *note ValueError:
     1fc.  Previously, a *note RuntimeError: 2bb. was raised.

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: 336.
     object.  If assigning a comment to a *note ZipFile: 424. 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 Objects,  Prev: ZipFile Objects,  Up: zipfile --- Work with ZIP archives

5.13.5.2 Path Objects
.....................

 -- 類別: zipfile.Path (root, at='')

     Construct a Path object from a ‘root’ zipfile (which may be a *note
     ZipFile: 424. instance or ‘file’ suitable for passing to the *note
     ZipFile: 424. 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: 202.
objects:

Path objects are traversable using the ‘/’ operator.

 -- 屬性: Path.name

     The final path component.

 -- 成員函式: Path.open (*, **)

     Invoke *note ZipFile.open(): 5c1. on the current path.  Accepts the
     same arguments as *note ZipFile.open(): 5c1.

          警示: The signature on this function changes in an
          incompatible way in Python 3.9.  For a future-compatible
          version, consider using the third-party zipp.Path package (3.0
          or later).

 -- 成員函式: 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.exists ()

     Return ‘True’ if the current context references a file or directory
     in the zip file.

 -- 成員函式: Path.read_text (*, **)

     Read the current file as unicode text.  Positional and keyword
     arguments are passed through to *note io.TextIOWrapper: 5f8.
     (except ‘buffer’, which is implied by the context).

 -- 成員函式: Path.read_bytes ()

     Read the current file as bytes.


File: python.info,  Node: PyZipFile Objects,  Next: ZipInfo Objects,  Prev: Path Objects,  Up: zipfile --- Work with ZIP archives

5.13.5.3 PyZipFile Objects
..........................

The *note PyZipFile: 920. constructor takes the same parameters as the
*note ZipFile: 424. constructor, and one additional parameter,
`optimize'.

 -- 類別: zipfile.PyZipFile (file, mode='r', compression=ZIP_STORED,
          allowZip64=True, optimize=-1)

     3.2 版新加入: The `optimize' parameter.

     3.4 版更變: ZIP64 extensions are enabled by default.

     Instances have one method in addition to those of *note ZipFile:
     424. 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: 920. was not
          given or ‘-1’, the corresponding file is a ‘*.pyc’ file,
          compiling if necessary.

          If the `optimize' parameter to *note PyZipFile: 920. was ‘0’,
          ‘1’ or ‘2’, only files with that optimization level (see *note
          compile(): 1b5.) 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: 2bb. 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(): 91f. 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 版新加入: The `filterfunc' parameter.

          3.6.2 版更變: The `pathname' parameter accepts a *note
          path-like object: 36f.

          3.7 版更變: Recursion sorts directory entries.


File: python.info,  Node: ZipInfo Objects,  Next: Command-Line Interface,  Prev: PyZipFile Objects,  Up: zipfile --- Work with ZIP archives

5.13.5.4 ZipInfo Objects
........................

Instances of the *note ZipInfo: 5bf. class are returned by the *note
getinfo(): 1d93. and *note infolist(): 1d94. methods of *note ZipFile:
424. objects.  Each object stores information about a single member of
the ZIP archive.

There is one classmethod to make a *note ZipInfo: 5bf. instance for a
filesystem file:

 -- 成員函式: classmethod ZipInfo.from_file (filename, arcname=None, *,
          strict_timestamps=True)

     Construct a *note ZipInfo: 5bf. 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: 36f.

     3.8 版新加入: The `strict_timestamps' keyword-only argument

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: 336.
     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: 336. 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 Objects,  Up: zipfile --- Work with ZIP archives

5.13.5.5 Command-Line Interface
...............................

The *note zipfile: 143. 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: 1dc6. 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: 1dc7. option:

     $ python -m zipfile -e monty.zip target-dir/

For a list of the files in a ZIP archive, use the *note -l: 1dc8.
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
.............................

 -- 程式選項: -l <zipfile>
 -- 程式選項: --list <zipfile>

     List files in a zipfile.

 -- 程式選項: -c <zipfile> <source1> ... <sourceN>
 -- 程式選項: --create <zipfile> <source1> ... <sourceN>

     Create zipfile from source files.

 -- 程式選項: -e <zipfile> <output_dir>
 -- 程式選項: --extract <zipfile> <output_dir>

     Extract zipfile into target directory.

 -- 程式選項: -t <zipfile>
 -- 程式選項: --test <zipfile>

     Test whether the zipfile is valid or not.


File: python.info,  Node: Decompression pitfalls,  Prev: Command-Line Interface,  Up: zipfile --- Work with ZIP archives

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 --- Read and write tar archive files,  Prev: zipfile --- Work with ZIP archives,  Up: 資料壓縮與保存

5.13.6 ‘tarfile’ — Read and write tar archive files
---------------------------------------------------

`Source code:' Lib/tarfile.py(1)

__________________________________________________________________

The *note tarfile: 102. module makes it possible to read and write tar
archives, including those using gzip, bz2 and lzma compression.  Use the
*note zipfile: 143. module to read or write ‘.zip’ files, or the
higher-level functions in *note shutil: b9b.

Some facts and figures:

   * reads and writes *note gzip: 8c, *note bz2: 14. and *note lzma: ae.
     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: ae. compression.

 -- 函式: tarfile.open (name=None, mode='r', fileobj=None,
          bufsize=10240, **kwargs)

     Return a *note TarFile: b91. object for the pathname `name'.  For
     detailed information on *note TarFile: b91. objects and the keyword
     arguments that are allowed, see *note TarFile Objects: 1dd8.

     `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' or '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'’ or ‘'x:'’        Create a tarfile exclusively without
                            compression.  Raise an
                            *note FileExistsError: 95d. exception if it
                            already exists.
                            
                            
     ‘'x:gz'’               Create a tarfile with gzip compression.  Raise
                            an *note FileExistsError: 95d. exception if it
                            already exists.
                            
                            
     ‘'x:bz2'’              Create a tarfile with bzip2 compression.  Raise
                            an *note FileExistsError: 95d. exception if it
                            already exists.
                            
                            
     ‘'x:xz'’               Create a tarfile with lzma compression.  Raise
                            an *note FileExistsError: 95d. exception if it
                            already exists.
                            
                            
     ‘'a' or 'a:'’          Open for appending with no compression.  The
                            file is created if it does not exist.
                            
                            
     ‘'w' or '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: 1dd9. is raised.  Use `mode' ‘'r'’ to
     avoid this.  If a compression method is not supported, *note
     CompressionError: 1dda. is raised.

     If `fileobj' is specified, it is used as an alternative to a *note
     file object: b47. opened in binary mode for `name'.  It is supposed
     to be at position 0.

     For modes ‘'w:gz'’, ‘'r:gz'’, ‘'w:bz2'’, ‘'r:bz2'’, ‘'x:gz'’,
     ‘'x:bz2'’, *note tarfile.open(): 76b. accepts the keyword argument
     `compresslevel' (default ‘9’) to specify the compression level of
     the file.

     For special purposes, there is a second format for `mode':
     ‘'filemode|[compression]'’.  *note tarfile.open(): 76b. will return
     a *note TarFile: b91. 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 ‘read()’ or ‘write()’ method
     (depending on the `mode').  `bufsize' specifies the blocksize and
     defaults to ‘20 * 512’ bytes.  Use this variant in combination with
     e.g.  ‘sys.stdin’, a socket *note file object: b47. or a tape
     device.  However, such a *note TarFile: b91. object is limited in
     that it does not allow random access, see *note Examples: 1ddb.
     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:
     36f.

 -- 類別: tarfile.TarFile

     Class for reading and writing tar archives.  Do not use this class
     directly: use *note tarfile.open(): 76b. instead.  See *note
     TarFile Objects: 1dd8.

 -- 函式: tarfile.is_tarfile (name)

     Return *note True: 49e. if `name' is a tar archive file, that the
     *note tarfile: 102. module can read.

The *note tarfile: 102. module defines the following exceptions:

 -- 例外: tarfile.TarError

     Base class for all *note tarfile: 102. exceptions.

 -- 例外: tarfile.ReadError

     Is raised when a tar archive is opened, that either cannot be
     handled by the *note tarfile: 102. 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: b91. objects.

 -- 例外: tarfile.ExtractError

     Is raised for `non-fatal' errors when using *note
     TarFile.extract(): 76d, but only if ‘TarFile.errorlevel’‘== 2’.

 -- 例外: tarfile.HeaderError

     Is raised by *note TarInfo.frombuf(): 1de1. if the buffer it gets
     is invalid.

The following constants are available at the module level:

 -- Data: tarfile.ENCODING

     The default character encoding: ‘'utf-8'’ on Windows, the value
     returned by *note sys.getfilesystemencoding(): 4fb. otherwise.

Each of the following constants defines a tar archive format that the
*note tarfile: 102. module is able to create.  See section *note
Supported tar formats: 1de3. for details.

 -- Data: tarfile.USTAR_FORMAT

     POSIX.1-1988 (ustar) format.

 -- Data: tarfile.GNU_FORMAT

     GNU tar format.

 -- Data: tarfile.PAX_FORMAT

     POSIX.1-2001 (pax) format.

 -- Data: tarfile.DEFAULT_FORMAT

     The default format for creating archives.  This is currently *note
     PAX_FORMAT: 1de6.

     3.8 版更變: The default format for new archives was changed to
     *note PAX_FORMAT: 1de6. from *note GNU_FORMAT: 1de5.

也參考
......

Module *note zipfile: 143.

     Documentation of the *note zipfile: 143. standard module.

*note Archiving operations: b9b.

     Documentation of the higher-level archiving facilities provided by
     the standard *note shutil: ea. module.

GNU tar manual, Basic Tar Format(2)

     Documentation for tar archive files, including GNU tar extensions.

* Menu:

* TarFile Objects::
* TarInfo Objects::
* Command-Line Interface: Command-Line Interface<2>.
* Examples: Examples<6>.
* Supported tar formats::
* Unicode issues::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/tarfile.py

   (2) https://www.gnu.org/software/tar/manual/html_node/Standard.html


File: python.info,  Node: TarFile Objects,  Next: TarInfo Objects,  Up: tarfile --- Read and write tar archive files

5.13.6.1 TarFile Objects
........................

The *note TarFile: b91. 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: b92. object, see *note TarInfo
Objects: 1de9. for details.

A *note TarFile: b91. object can be used as a context manager in a *note
with: 6ee. 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 Examples: 1ddb. 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=0)

     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: 36f.  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: b91. is
          closed.

     `format' controls the archive format for writing.  It must be one
     of the constants *note USTAR_FORMAT: 1de4, *note GNU_FORMAT: 1de5.
     or *note PAX_FORMAT: 1de6. 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: b92. class with a different one.

     If `dereference' is *note False: 38d, add symbolic and hard links
     to the archive.  If it is *note True: 49e, 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: 38d, treat an empty block as the
     end of the archive.  If it is *note True: 49e, 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’.

     If `errorlevel' is ‘0’, all errors are ignored when using *note
     TarFile.extract(): 76d.  Nevertheless, they appear as error
     messages in the debug output, when debugging is enabled.  If ‘1’,
     all `fatal' errors are raised as *note OSError: 1d4. exceptions.
     If ‘2’, all `non-fatal' errors are raised as *note TarError: 1ddd.
     exceptions as well.

     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: 1dea. 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: 1de6.

     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:
     36f.

 -- 成員函式: classmethod TarFile.open (...)

     Alternative constructor.  The *note tarfile.open(): 76b. function
     is actually a shortcut to this classmethod.

 -- 成員函式: TarFile.getmember (name)

     Return a *note TarInfo: b92. object for member `name'.  If `name'
     can not be found in the archive, *note KeyError: 2c8. 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: b92.
     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(): 76f.

 -- 成員函式: TarFile.list (verbose=True, *, members=None)

     Print a table of contents to ‘sys.stdout’.  If `verbose' is *note
     False: 38d, only the names of the members are printed.  If it is
     *note True: 49e, 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(): 76f.

     3.5 版更變: Added the `members' parameter.

 -- 成員函式: TarFile.next ()

     Return the next member of the archive as a *note TarInfo: b92.
     object, when *note TarFile: b91. is opened for reading.  Return
     *note None: 158. if there is no more available.

 -- 成員函式: TarFile.extractall (path=".", members=None, *,
          numeric_owner=False)

     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(): 76f.
     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: 49e, 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.

          警告: 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 ‘".."’.

     3.5 版更變: Added the `numeric_owner' parameter.

     3.6 版更變: The `path' parameter accepts a *note path-like object:
     36f.

 -- 成員函式: TarFile.extract (member, path="", set_attrs=True, *,
          numeric_owner=False)

     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: b92. object.  You can specify a different directory using
     `path'.  `path' may be a *note path-like object: 36f.  File
     attributes (owner, mtime, mode) are set unless `set_attrs' is
     false.

     If `numeric_owner' is *note True: 49e, 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 *note extract(): 76d. method does not take care of
          several extraction issues.  In most cases you should consider
          using the *note extractall(): 76c. method.

          警告: See the warning for *note extractall(): 76c.

     3.2 版更變: Added the `set_attrs' parameter.

     3.5 版更變: Added the `numeric_owner' parameter.

     3.6 版更變: The `path' parameter accepts a *note path-like object:
     36f.

 -- 成員函式: TarFile.extractfile (member)

     Extract a member from the archive as a file object.  `member' may
     be a filename or a *note TarInfo: b92. object.  If `member' is a
     regular file or a link, an *note io.BufferedReader: b8f. object is
     returned.  Otherwise, *note None: 158. is returned.

     3.3 版更變: Return an *note io.BufferedReader: b8f. object.

 -- 成員函式: 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: 38d.  Recursion adds entries
     in sorted order.  If `filter' is given, it should be a function
     that takes a *note TarInfo: b92. object argument and returns the
     changed *note TarInfo: b92. object.  If it instead returns *note
     None: 158. the *note TarInfo: b92. object will be excluded from the
     archive.  See *note Examples: 1ddb. for an example.

     3.2 版更變: Added the `filter' parameter.

     3.7 版更變: Recursion adds entries in sorted order.

 -- 成員函式: TarFile.addfile (tarinfo, fileobj=None)

     Add the *note TarInfo: b92. object `tarinfo' to the archive.  If
     `fileobj' is given, it should be a *note binary file: 1caa, and
     ‘tarinfo.size’ bytes are read from it and added to the archive.
     You can create *note TarInfo: b92. objects directly, or by using
     *note gettarinfo(): 1df1.

 -- 成員函式: TarFile.gettarinfo (name=None, arcname=None, fileobj=None)

     Create a *note TarInfo: b92. object from the result of *note
     os.stat(): 1f2. or equivalent on an existing file.  The file is
     either named by `name', or specified as a *note file object: b47.
     `fileobj' with a file descriptor.  `name' may be a *note path-like
     object: 36f.  If given, `arcname' specifies an alternative name for
     the file in the archive, otherwise, the name is taken from
     `fileobj'’s *note name: 1df2. attribute, or the `name' argument.
     The name should be a text string.

     You can modify some of the *note TarInfo: b92.’s attributes before
     you add it using *note addfile(): 1df0.  If the file object is not
     an ordinary file object positioned at the beginning of the file,
     attributes such as *note size: 1df3. may need modifying.  This is
     the case for objects such as *note GzipFile: 6e2.  The *note name:
     1df4. may also be modified, in which case `arcname' could be a
     dummy string.

     3.6 版更變: The `name' parameter accepts a *note path-like object:
     36f.

 -- 成員函式: TarFile.close ()

     Close the *note TarFile: b91.  In write mode, two finishing zero
     blocks are appended to the archive.

 -- 屬性: TarFile.pax_headers

     A dictionary containing key-value pairs of pax global headers.


File: python.info,  Node: TarInfo Objects,  Next: Command-Line Interface<2>,  Prev: TarFile Objects,  Up: tarfile --- Read and write tar archive files

5.13.6.2 TarInfo Objects
........................

A *note TarInfo: b92. object represents one member in a *note TarFile:
b91.  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: b92. objects are returned by *note TarFile: b91.’s
methods ‘getmember()’, ‘getmembers()’ and ‘gettarinfo()’.

 -- 類別: tarfile.TarInfo (name="")

     Create a *note TarInfo: b92. object.

 -- 成員函式: classmethod TarInfo.frombuf (buf, encoding, errors)

     Create and return a *note TarInfo: b92. object from string buffer
     `buf'.

     Raises *note HeaderError: 1de0. if the buffer is invalid.

 -- 成員函式: classmethod TarInfo.fromtarfile (tarfile)

     Read the next member from the *note TarFile: b91. object `tarfile'
     and return it as a *note TarInfo: b92. object.

 -- 成員函式: TarInfo.tobuf (format=DEFAULT_FORMAT, encoding=ENCODING,
          errors='surrogateescape')

     Create a string buffer from a *note TarInfo: b92. object.  For
     information on the arguments see the constructor of the *note
     TarFile: b91. class.

     3.2 版更變: Use ‘'surrogateescape'’ as the default for the `errors'
     argument.

A ‘TarInfo’ object has the following public data attributes:

 -- 屬性: TarInfo.name

     Name of the archive member.

 -- 屬性: TarInfo.size

     Size in bytes.

 -- 屬性: TarInfo.mtime

     Time of last modification.

 -- 屬性: TarInfo.mode

     Permission bits.

 -- 屬性: TarInfo.type

     File type.  `type' is usually one of these constants: ‘REGTYPE’,
     ‘AREGTYPE’, ‘LNKTYPE’, ‘SYMTYPE’, ‘DIRTYPE’, ‘FIFOTYPE’,
     ‘CONTTYPE’, ‘CHRTYPE’, ‘BLKTYPE’, ‘GNUTYPE_SPARSE’.  To determine
     the type of a *note TarInfo: b92. object more conveniently, use the
     ‘is*()’ methods below.

 -- 屬性: TarInfo.linkname

     Name of the target file name, which is only present in *note
     TarInfo: b92. objects of type ‘LNKTYPE’ and ‘SYMTYPE’.

 -- 屬性: TarInfo.uid

     User ID of the user who originally stored this member.

 -- 屬性: TarInfo.gid

     Group ID of the user who originally stored this member.

 -- 屬性: TarInfo.uname

     User name.

 -- 屬性: TarInfo.gname

     Group name.

 -- 屬性: TarInfo.pax_headers

     A dictionary containing key-value pairs of an associated pax
     extended header.

A *note TarInfo: b92. object also provides some convenient query
methods:

 -- 成員函式: TarInfo.isfile ()

     Return *note True: 49e. if the ‘Tarinfo’ object is a regular file.

 -- 成員函式: TarInfo.isreg ()

     Same as *note isfile(): 1e03.

 -- 成員函式: TarInfo.isdir ()

     Return *note True: 49e. if it is a directory.

 -- 成員函式: TarInfo.issym ()

     Return *note True: 49e. if it is a symbolic link.

 -- 成員函式: TarInfo.islnk ()

     Return *note True: 49e. if it is a hard link.

 -- 成員函式: TarInfo.ischr ()

     Return *note True: 49e. if it is a character device.

 -- 成員函式: TarInfo.isblk ()

     Return *note True: 49e. if it is a block device.

 -- 成員函式: TarInfo.isfifo ()

     Return *note True: 49e. if it is a FIFO.

 -- 成員函式: TarInfo.isdev ()

     Return *note True: 49e. if it is one of character device, block
     device or FIFO.


File: python.info,  Node: Command-Line Interface<2>,  Next: Examples<6>,  Prev: TarInfo Objects,  Up: tarfile --- Read and write tar archive files

5.13.6.3 Command-Line Interface
...............................

3.4 版新加入.

The *note tarfile: 102. 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: 1e0d. 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: 1e0e. 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: 1e0f.
option:

     $ python -m tarfile -l monty.tar

* Menu:

* Command-line options: Command-line options<2>.


File: python.info,  Node: Command-line options<2>,  Up: Command-Line Interface<2>

5.13.6.4 Command-line options
.............................

 -- 程式選項: -l <tarfile>
 -- 程式選項: --list <tarfile>

     List files in a tarfile.

 -- 程式選項: -c <tarfile> <source1> ... <sourceN>
 -- 程式選項: --create <tarfile> <source1> ... <sourceN>

     Create tarfile from source files.

 -- 程式選項: -e <tarfile> [<output_dir>]
 -- 程式選項: --extract <tarfile> [<output_dir>]

     Extract tarfile into the current directory if `output_dir' is not
     specified.

 -- 程式選項: -t <tarfile>
 -- 程式選項: --test <tarfile>

     Test whether the tarfile is valid or not.

 -- 程式選項: -v, --verbose

     Verbose output.


File: python.info,  Node: Examples<6>,  Next: Supported tar formats,  Prev: Command-Line Interface<2>,  Up: tarfile --- Read and write tar archive files

5.13.6.5 Examples
.................

How to extract an entire tar archive to the current working directory:

     import tarfile
     tar = tarfile.open("sample.tar.gz")
     tar.extractall()
     tar.close()

How to extract a subset of a tar archive with *note
TarFile.extractall(): 76c. 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: 6ee. 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(): 481.:

     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: Examples<6>,  Up: tarfile --- Read and write tar archive files

5.13.6.6 Supported tar formats
..............................

There are three tar formats that can be created with the *note tarfile:
102. module:

   * The POSIX.1-1988 ustar format (*note USTAR_FORMAT: 1de4.).  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: 1de5.).  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:
     102. fully supports the GNU tar extensions for long names, sparse
     file support is read-only.

   * The POSIX.1-2001 pax format (*note PAX_FORMAT: 1de6.).  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 --- Read and write tar archive files

5.13.6.7 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: 102. are
controlled by the `encoding' and `errors' keyword arguments of the *note
TarFile: b91. class.

`encoding' defines the character encoding to use for the metadata in the
archive.  The default value is *note sys.getfilesystemencoding(): 4fb.
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:
1366.  The default scheme is ‘'surrogateescape'’ which Python also uses
for its file system calls, see *note File Names, Command Line Arguments,
and Environment Variables: 1e1a.

For *note PAX_FORMAT: 1de6. 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: Cryptographic Services,  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 File Reading and Writing. CSV File Reading and Writing
* configparser: configparser --- Configuration file parser. Configuration file parser
* netrc: netrc --- netrc file processing. netrc file processing
* xdrlib: xdrlib --- Encode and decode XDR data. Encode and decode XDR data
* plistlib: plistlib --- Generate and parse Mac OS X plist files. Generate and parse Mac OS X .plist files


File: python.info,  Node: csv --- CSV File Reading and Writing,  Next: configparser --- Configuration file parser,  Up: 檔案格式

5.14.1 ‘csv’ — CSV File Reading and Writing
-------------------------------------------

`Source code:' Lib/csv.py(1)

__________________________________________________________________

The so-called CSV (Comma Separated Values) format is the most common
import and export format for spreadsheets and databases.  CSV format was
used for many years prior to attempts to describe the format in a
standardized way in RFC 4180(2).  The lack of a well-defined standard
means that subtle differences often exist in the data produced and
consumed by different applications.  These differences can make it
annoying to process CSV files from multiple sources.  Still, while the
delimiters and quoting characters vary, the overall format is similar
enough that it is possible to write a single module which can
efficiently manipulate such data, hiding the details of reading and
writing the data from the programmer.

The *note csv: 2a. module implements classes to read and write tabular
data in CSV format.  It allows programmers to say, "write this data in
the format preferred by Excel," or "read data from this file which was
generated by Excel," without knowing the precise details of the CSV
format used by Excel.  Programmers can also describe the CSV formats
understood by other applications or define their own special-purpose CSV
formats.

The *note csv: 2a. module’s *note reader: ec0. and *note writer: e01.
objects read and write sequences.  Programmers can also read and write
data in dictionary form using the *note DictReader: 1be. and *note
DictWriter: b7f. classes.

也參考
......

PEP 305(3) - CSV File API

     The Python Enhancement Proposal which proposed this addition to
     Python.

* Menu:

* Module Contents: Module Contents<3>.
* Dialects and Formatting Parameters::
* Reader Objects::
* Writer Objects::
* Examples: Examples<7>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/csv.py

   (2) https://tools.ietf.org/html/rfc4180.html

   (3) https://www.python.org/dev/peps/pep-0305


File: python.info,  Node: Module Contents<3>,  Next: Dialects and Formatting Parameters,  Up: csv --- CSV File Reading and Writing

5.14.1.1 Module Contents
........................

The *note csv: 2a. module defines the following functions:

 -- 函式: csv.reader (csvfile, dialect='excel', **fmtparams)

     Return a reader object which will iterate over lines in the given
     `csvfile'.  `csvfile' can be any object which supports the *note
     iterator: 1040. protocol and returns a string each time its
     ‘__next__()’ method is called — *note file objects: b47. and list
     objects are both suitable.  If `csvfile' is a file object, it
     should be opened with ‘newline=''’.  (1) An optional `dialect'
     parameter can be given which is used to define a set of parameters
     specific to a particular CSV dialect.  It may be an instance of a
     subclass of the *note Dialect: 1e22. class or one of the strings
     returned by the *note list_dialects(): 1e23. function.  The other
     optional `fmtparams' keyword arguments can be given to override
     individual formatting parameters in the current dialect.  For full
     details about the dialect and formatting parameters, see section
     *note Dialects and Formatting Parameters: 1e24.

     Each row read from the csv file is returned as a list of strings.
     No automatic data type conversion is performed unless the
     ‘QUOTE_NONNUMERIC’ format option is specified (in which case
     unquoted fields are transformed into floats).

     A short usage example:

          >>> 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)

     Return a writer object responsible for converting the user’s data
     into delimited strings on the given file-like object.  `csvfile'
     can be any object with a ‘write()’ method.  If `csvfile' is a file
     object, it should be opened with ‘newline=''’ (2).  An optional
     `dialect' parameter can be given which is used to define a set of
     parameters specific to a particular CSV dialect.  It may be an
     instance of a subclass of the *note Dialect: 1e22. class or one of
     the strings returned by the *note list_dialects(): 1e23. function.
     The other optional `fmtparams' keyword arguments can be given to
     override individual formatting parameters in the current dialect.
     For full details about the dialect and formatting parameters, see
     section *note Dialects and Formatting Parameters: 1e24.  To make it
     as easy as possible to interface with modules which implement the
     DB API, the value *note None: 158. is written as the empty string.
     While this isn’t a reversible transformation, it makes it easier to
     dump SQL NULL data values to CSV files without preprocessing the
     data returned from a ‘cursor.fetch*’ call.  All other non-string
     data are stringified with *note str(): 335. before being written.

     A short usage example:

          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]])

     Associate `dialect' with `name'.  `name' must be a string.  The
     dialect can be specified either by passing a sub-class of *note
     Dialect: 1e22, or by `fmtparams' keyword arguments, or both, with
     keyword arguments overriding parameters of the dialect.  For full
     details about the dialect and formatting parameters, see section
     *note Dialects and Formatting Parameters: 1e24.

 -- 函式: csv.unregister_dialect (name)

     Delete the dialect associated with `name' from the dialect
     registry.  An *note Error: 1e27. is raised if `name' is not a
     registered dialect name.

 -- 函式: csv.get_dialect (name)

     Return the dialect associated with `name'.  An *note Error: 1e27.
     is raised if `name' is not a registered dialect name.  This
     function returns an immutable *note Dialect: 1e22.

 -- 函式: csv.list_dialects ()

     Return the names of all registered dialects.

 -- 函式: csv.field_size_limit ([new_limit])

     Returns the current maximum field size allowed by the parser.  If
     `new_limit' is given, this becomes the new limit.

The *note csv: 2a. module defines the following classes:

 -- 類別: csv.DictReader (f, fieldnames=None, restkey=None,
          restval=None, dialect='excel', *args, **kwds)

     Create an object that operates like a regular reader but maps the
     information in each row to a *note dict: 1b9. whose keys are given
     by the optional `fieldnames' parameter.

     The `fieldnames' parameter is a *note sequence: 122d.  If
     `fieldnames' is omitted, the values in the first row of file `f'
     will be used as the fieldnames.  Regardless of how the fieldnames
     are determined, the dictionary preserves their original ordering.

     If a row has more fields than fieldnames, the remaining data is put
     in a list and stored with the fieldname specified by `restkey'
     (which defaults to ‘None’).  If a non-blank row has fewer fields
     than fieldnames, the missing values are filled-in with the value of
     `restval' (which defaults to ‘None’).

     All other optional or keyword arguments are passed to the
     underlying *note reader: ec0. instance.

     3.6 版更變: Returned rows are now of type ‘OrderedDict’.

     3.8 版更變: Returned rows are now of type *note dict: 1b9.

     A short usage example:

          >>> 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)

     Create an object which operates like a regular writer but maps
     dictionaries onto output rows.  The `fieldnames' parameter is a
     *note sequence: 1f. of keys that identify the order in which values
     in the dictionary passed to the ‘writerow()’ method are written to
     file `f'.  The optional `restval' parameter specifies the value to
     be written if the dictionary is missing a key in `fieldnames'.  If
     the dictionary passed to the ‘writerow()’ method contains a key not
     found in `fieldnames', the optional `extrasaction' parameter
     indicates what action to take.  If it is set to ‘'raise'’, the
     default value, a *note ValueError: 1fc. is raised.  If it is set to
     ‘'ignore'’, extra values in the dictionary are ignored.  Any other
     optional or keyword arguments are passed to the underlying *note
     writer: e01. instance.

     Note that unlike the *note DictReader: 1be. class, the `fieldnames'
     parameter of the *note DictWriter: b7f. class is not optional.

     A short usage example:

          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

     The *note Dialect: 1e22. class is a container class relied on
     primarily for its attributes, which are used to define the
     parameters for a specific *note reader: ec0. or *note writer: e01.
     instance.

 -- 類別: csv.excel

     The *note excel: 1e2a. class defines the usual properties of an
     Excel-generated CSV file.  It is registered with the dialect name
     ‘'excel'’.

 -- 類別: csv.excel_tab

     The *note excel_tab: 1e2b. class defines the usual properties of an
     Excel-generated TAB-delimited file.  It is registered with the
     dialect name ‘'excel-tab'’.

 -- 類別: csv.unix_dialect

     The *note unix_dialect: b7e. class defines the usual properties of
     a CSV file generated on UNIX systems, i.e.  using ‘'\n'’ as line
     terminator and quoting all fields.  It is registered with the
     dialect name ‘'unix'’.

     3.2 版新加入.

 -- 類別: csv.Sniffer

     The *note Sniffer: 1e2c. class is used to deduce the format of a
     CSV file.

     The *note Sniffer: 1e2c. class provides two methods:

      -- 成員函式: sniff (sample, delimiters=None)

          Analyze the given `sample' and return a *note Dialect: 1e22.
          subclass reflecting the parameters found.  If the optional
          `delimiters' parameter is given, it is interpreted as a string
          containing possible valid delimiter characters.

      -- 成員函式: has_header (sample)

          Analyze the sample text (presumed to be in CSV format) and
          return *note True: 49e. if the first row appears to be a
          series of column headers.

An example for *note Sniffer: 1e2c. use:

     with open('example.csv', newline='') as csvfile:
         dialect = csv.Sniffer().sniff(csvfile.read(1024))
         csvfile.seek(0)
         reader = csv.reader(csvfile, dialect)
         # ... process CSV file contents here ...

The *note csv: 2a. module defines the following constants:

 -- Data: csv.QUOTE_ALL

     Instructs *note writer: e01. objects to quote all fields.

 -- Data: csv.QUOTE_MINIMAL

     Instructs *note writer: e01. objects to only quote those fields
     which contain special characters such as `delimiter', `quotechar'
     or any of the characters in `lineterminator'.

 -- Data: csv.QUOTE_NONNUMERIC

     Instructs *note writer: e01. objects to quote all non-numeric
     fields.

     Instructs the reader to convert all non-quoted fields to type
     `float'.

 -- Data: csv.QUOTE_NONE

     Instructs *note writer: e01. objects to never quote fields.  When
     the current `delimiter' occurs in output data it is preceded by the
     current `escapechar' character.  If `escapechar' is not set, the
     writer will raise *note Error: 1e27. if any characters that require
     escaping are encountered.

     Instructs *note reader: ec0. to perform no special processing of
     quote characters.

The *note csv: 2a. module defines the following exception:

 -- 例外: csv.Error

     Raised by any of the functions when an error is detected.

   ---------- Footnotes ----------

   (1) (1) If ‘newline=''’ is not specified, newlines embedded inside
quoted fields will not be interpreted correctly, and on platforms that
use ‘\r\n’ linendings on write an extra ‘\r’ will be added.  It should
always be safe to specify ‘newline=''’, since the csv module does its
own (*note universal: 5f9.) newline handling.

   (2) (1) If ‘newline=''’ is not specified, newlines embedded inside
quoted fields will not be interpreted correctly, and on platforms that
use ‘\r\n’ linendings on write an extra ‘\r’ will be added.  It should
always be safe to specify ‘newline=''’, since the csv module does its
own (*note universal: 5f9.) newline handling.


File: python.info,  Node: Dialects and Formatting Parameters,  Next: Reader Objects,  Prev: Module Contents<3>,  Up: csv --- CSV File Reading and Writing

5.14.1.2 Dialects and Formatting Parameters
...........................................

To make it easier to specify the format of input and output records,
specific formatting parameters are grouped together into dialects.  A
dialect is a subclass of the *note Dialect: 1e22. class having a set of
specific methods and a single ‘validate()’ method.  When creating *note
reader: ec0. or *note writer: e01. objects, the programmer can specify a
string or a subclass of the *note Dialect: 1e22. class as the dialect
parameter.  In addition to, or instead of, the `dialect' parameter, the
programmer can also specify individual formatting parameters, which have
the same names as the attributes defined below for the *note Dialect:
1e22. class.

Dialects support the following attributes:

 -- 屬性: Dialect.delimiter

     A one-character string used to separate fields.  It defaults to
     ‘','’.

 -- 屬性: Dialect.doublequote

     Controls how instances of `quotechar' appearing inside a field
     should themselves be quoted.  When *note True: 49e, the character
     is doubled.  When *note False: 38d, the `escapechar' is used as a
     prefix to the `quotechar'.  It defaults to *note True: 49e.

     On output, if `doublequote' is *note False: 38d. and no
     `escapechar' is set, *note Error: 1e27. is raised if a `quotechar'
     is found in a field.

 -- 屬性: Dialect.escapechar

     A one-character string used by the writer to escape the `delimiter'
     if `quoting' is set to *note QUOTE_NONE: 1e32. and the `quotechar'
     if `doublequote' is *note False: 38d.  On reading, the `escapechar'
     removes any special meaning from the following character.  It
     defaults to *note None: 158, which disables escaping.

 -- 屬性: Dialect.lineterminator

     The string used to terminate lines produced by the *note writer:
     e01.  It defaults to ‘'\r\n'’.

          備註: The *note reader: ec0. is hard-coded to recognise either
          ‘'\r'’ or ‘'\n'’ as end-of-line, and ignores `lineterminator'.
          This behavior may change in the future.

 -- 屬性: Dialect.quotechar

     A one-character string used to quote fields containing special
     characters, such as the `delimiter' or `quotechar', or which
     contain new-line characters.  It defaults to ‘'"'’.

 -- 屬性: Dialect.quoting

     Controls when quotes should be generated by the writer and
     recognised by the reader.  It can take on any of the ‘QUOTE_*’
     constants (see section *note Module Contents: 1e20.) and defaults
     to *note QUOTE_MINIMAL: 1e30.

 -- 屬性: Dialect.skipinitialspace

     When *note True: 49e, whitespace immediately following the
     `delimiter' is ignored.  The default is *note False: 38d.

 -- 屬性: Dialect.strict

     When ‘True’, raise exception *note Error: 1e27. on bad CSV input.
     The default is ‘False’.


File: python.info,  Node: Reader Objects,  Next: Writer Objects,  Prev: Dialects and Formatting Parameters,  Up: csv --- CSV File Reading and Writing

5.14.1.3 Reader Objects
.......................

Reader objects (*note DictReader: 1be. instances and objects returned by
the *note reader(): ec0. function) have the following public methods:

 -- 成員函式: csvreader.__next__ ()

     Return the next row of the reader’s iterable object as a list (if
     the object was returned from *note reader(): ec0.) or a dict (if it
     is a *note DictReader: 1be. instance), parsed according to the
     current dialect.  Usually you should call this as ‘next(reader)’.

Reader objects have the following public attributes:

 -- 屬性: csvreader.dialect

     A read-only description of the dialect in use by the parser.

 -- 屬性: csvreader.line_num

     The number of lines read from the source iterator.  This is not the
     same as the number of records returned, as records can span
     multiple lines.

DictReader objects have the following public attribute:

 -- 屬性: csvreader.fieldnames

     If not passed as a parameter when creating the object, this
     attribute is initialized upon first access or when the first record
     is read from the file.


File: python.info,  Node: Writer Objects,  Next: Examples<7>,  Prev: Reader Objects,  Up: csv --- CSV File Reading and Writing

5.14.1.4 Writer Objects
.......................

‘Writer’ objects (*note DictWriter: b7f. instances and objects returned
by the *note writer(): e01. function) have the following public methods.
A `row' must be an iterable of strings or numbers for ‘Writer’ objects
and a dictionary mapping fieldnames to strings or numbers (by passing
them through *note str(): 335. first) for *note DictWriter: b7f.
objects.  Note that complex numbers are written out surrounded by
parens.  This may cause some problems for other programs which read CSV
files (assuming they support complex numbers at all).

 -- 成員函式: csvwriter.writerow (row)

     Write the `row' parameter to the writer’s file object, formatted
     according to the current dialect.  Return the return value of the
     call to the `write' method of the underlying file object.

     3.5 版更變: Added support of arbitrary iterables.

 -- 成員函式: csvwriter.writerows (rows)

     Write all elements in `rows' (an iterable of `row' objects as
     described above) to the writer’s file object, formatted according
     to the current dialect.

Writer objects have the following public attribute:

 -- 屬性: csvwriter.dialect

     A read-only description of the dialect in use by the writer.

DictWriter objects have the following public method:

 -- 成員函式: DictWriter.writeheader ()

     Write a row with the field names (as specified in the constructor)
     to the writer’s file object, formatted according to the current
     dialect.  Return the return value of the *note
     csvwriter.writerow(): 6c9. call used internally.

     3.2 版新加入.

     3.8 版更變: *note writeheader(): b80. now also returns the value
     returned by the *note csvwriter.writerow(): 6c9. method it uses
     internally.


File: python.info,  Node: Examples<7>,  Prev: Writer Objects,  Up: csv --- CSV File Reading and Writing

5.14.1.5 Examples
.................

The simplest example of reading a CSV file:

     import csv
     with open('some.csv', newline='') as f:
         reader = csv.reader(f)
         for row in reader:
             print(row)

Reading a file with an alternate format:

     import csv
     with open('passwd', newline='') as f:
         reader = csv.reader(f, delimiter=':', quoting=csv.QUOTE_NONE)
         for row in reader:
             print(row)

The corresponding simplest possible writing example is:

     import csv
     with open('some.csv', 'w', newline='') as f:
         writer = csv.writer(f)
         writer.writerows(someiterable)

Since *note open(): 4f5. is used to open a CSV file for reading, the
file will by default be decoded into unicode using the system default
encoding (see *note locale.getpreferredencoding(): 3aa.).  To decode a
file using a different encoding, use the ‘encoding’ argument of open:

     import csv
     with open('some.csv', newline='', encoding='utf-8') as f:
         reader = csv.reader(f)
         for row in reader:
             print(row)

The same applies to writing in something other than the system default
encoding: specify the encoding argument when opening the output file.

Registering a new dialect:

     import csv
     csv.register_dialect('unixpwd', delimiter=':', quoting=csv.QUOTE_NONE)
     with open('passwd', newline='') as f:
         reader = csv.reader(f, 'unixpwd')

A slightly more advanced use of the reader — catching and reporting
errors:

     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))

And while the module doesn’t directly support parsing strings, it can
easily be done:

     import csv
     for row in csv.reader(['one,two,three']):
         print(row)

註解
....


File: python.info,  Node: configparser --- Configuration file parser,  Next: netrc --- netrc file processing,  Prev: csv --- CSV File Reading and Writing,  Up: 檔案格式

5.14.2 ‘configparser’ — Configuration file parser
-------------------------------------------------

`Source code:' Lib/configparser.py(1)

__________________________________________________________________

This module provides the *note ConfigParser: 4af. 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.

也參考
......

Module *note shlex: e9.

     Support for creating Unix shell-like mini-languages which can be
     used as an alternate format for application configuration files.

Module *note json: a5.

     The json module implements a subset of JavaScript syntax which can
     also be used for this purpose.

* Menu:

* Quick Start::
* Supported Datatypes::
* Fallback Values::
* Supported INI File Structure::
* Interpolation of values::
* Mapping Protocol Access::
* Customizing Parser Behaviour::
* Legacy API Examples::
* ConfigParser Objects::
* RawConfigParser Objects::
* Exceptions: Exceptions<4>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/configparser.py


File: python.info,  Node: Quick Start,  Next: Supported Datatypes,  Up: configparser --- Configuration file parser

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

     [bitbucket.org]
     User = hg

     [topsecret.server.com]
     Port = 50022
     ForwardX11 = no

The structure of INI files is described *note in the following section:
1e49.  Essentially, the file consists of sections, each of which
contains keys with values.  *note configparser: 23. 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['bitbucket.org'] = {}
     >>> config['bitbucket.org']['User'] = 'hg'
     >>> config['topsecret.server.com'] = {}
     >>> topsecret = config['topsecret.server.com']
     >>> 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: 1e4a, 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()
     ['bitbucket.org', 'topsecret.server.com']
     >>> 'bitbucket.org' in config
     True
     >>> 'bytebong.com' in config
     False
     >>> config['bitbucket.org']['User']
     'hg'
     >>> config['DEFAULT']['Compression']
     'yes'
     >>> topsecret = config['topsecret.server.com']
     >>> topsecret['ForwardX11']
     'no'
     >>> topsecret['Port']
     '50022'
     >>> for key in config['bitbucket.org']:
     ...     print(key)
     user
     compressionlevel
     serveraliveinterval
     compression
     forwardx11
     >>> config['bitbucket.org']['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).

   ---------- Footnotes ----------

   (1) (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: 1e4b. section.

   (2) (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: 1e4b. section.


File: python.info,  Node: Supported Datatypes,  Next: Fallback Values,  Prev: Quick Start,  Up: configparser --- Configuration file parser

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(): 1e4d.  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['bitbucket.org'].getboolean('ForwardX11')
     True
     >>> config.getboolean('bitbucket.org', 'Compression')
     True

Apart from *note getboolean(): 1e4d, config parsers also provide
equivalent *note getint(): 1e4e. and *note getfloat(): 1e4f. methods.
You can register your own converters and customize the provided ones.
(2)

   ---------- Footnotes ----------

   (1) (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: 1e4b. section.

   (2) (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: 1e4b. section.


File: python.info,  Node: Fallback Values,  Next: Supported INI File Structure,  Prev: Supported Datatypes,  Up: configparser --- Configuration file parser

5.14.2.3 Fallback Values
........................

As with a dictionary, you can use a section’s ‘get()’ 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.com'’, 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 ‘get()’ 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('bitbucket.org', 'monster',
     ...            fallback='No such things as monsters')
     'No such things as monsters'

The same ‘fallback’ argument can be used with the *note getint(): 1e4e,
*note getfloat(): 1e4f. and *note getboolean(): 1e4d. 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: Interpolation of values,  Prev: Fallback Values,  Up: configparser --- Configuration file parser

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, 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.

Configuration files may include comments, prefixed by specific
characters (‘#’ and ‘;’ by default (3)).  Comments may appear on their
own on an otherwise empty line, possibly indented.  (4)

For example:

     [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) (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: 1e4b. section.

   (2) (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: 1e4b. section.

   (3) (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: 1e4b. section.

   (4) (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: 1e4b. section.


File: python.info,  Node: Interpolation of values,  Next: Mapping Protocol Access,  Prev: Supported INI File Structure,  Up: configparser --- Configuration file parser

5.14.2.5 Interpolation of values
................................

On top of the core functionality, *note ConfigParser: 4af. supports
interpolation.  This means values can be preprocessed before returning
them from ‘get()’ calls.

 -- 類別: configparser.BasicInterpolation

     The default implementation used by *note ConfigParser: 4af.  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.

     For example:

          [Paths]
          home_dir: /Users
          my_dir: %(home_dir)s/lumberjack
          my_pictures: %(my_dir)s/Pictures

          [Escape]
          gain: 80%%  # use a %% to escape the % sign (% is the only character that needs to be escaped)

     In the example above, *note ConfigParser: 4af. 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]
          cost: $$80  # use a $$ to escape the $ sign ($ is the only character that needs to be escaped)

     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) (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: 1e4b. section.


File: python.info,  Node: Mapping Protocol Access,  Next: Customizing Parser Behaviour,  Prev: Interpolation of values,  Up: configparser --- Configuration file parser

5.14.2.6 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: 23, 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: 23. objects behave as close to actual dictionaries
as possible.  The mapping interface is complete and adheres to the *note
MutableMapping: 9f4. 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:
     2c8.

   * ‘DEFAULTSECT’ cannot be removed from the parser:

        * trying to delete it raises *note ValueError: 1fc,

        * ‘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) (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: 1e4b. section.


File: python.info,  Node: Customizing Parser Behaviour,  Next: Legacy API Examples,  Prev: Mapping Protocol Access,  Up: configparser --- Configuration file parser

5.14.2.7 Customizing Parser Behaviour
.....................................

There are nearly as many INI format variants as there are applications
using it.  *note configparser: 23. 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 *note __init__(): d63. 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 ‘read_dict()’ before you read the actual file.

   * `dict_type', default value: *note dict: 1b9.

     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: 23.  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(): 1e53.

   * `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: 23.
     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
     ‘read_file()’, ‘read_string()’ or ‘read_dict()’).  It is
     recommended to use strict parsers in new applications.

     3.2 版更變: In previous versions of *note configparser: 23.
     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: 1e51.
     *note RawConfigParser: 876. 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(): 1e4e, *note getfloat():
     1e4f, and *note getboolean(): 1e4d. 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(): 1e4d, 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 Objects,  Prev: Customizing Parser Behaviour,  Up: configparser --- Configuration file parser

5.14.2.8 Legacy API Examples
............................

Mainly because of backwards compatibility concerns, *note configparser:
23. 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: 4af.:

     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 Objects,  Next: RawConfigParser Objects,  Prev: Legacy API Examples,  Up: configparser --- Configuration file parser

5.14.2.9 ConfigParser Objects
.............................

 -- 類別: 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:
     c0a. or *note DuplicateOptionError: c0b.  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 on runtime using the ‘default_section’
     instance attribute.

     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: 1e51.

     All option names used in interpolation will be passed through the
     *note optionxform(): 1e59. method just like any other option name
     reference.  For example, using the default implementation of *note
     optionxform(): 1e59. (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.

     3.1 版更變: The default `dict_type' is *note
     collections.OrderedDict: 1ba.

     3.2 版更變: `allow_no_value', `delimiters', `comment_prefixes',
     `strict', `empty_lines_in_values', `default_section' and
     `interpolation' were added.

     3.5 版更變: The `converters' argument was added.

     3.7 版更變: The `defaults' argument is read with *note read_dict():
     1e5a, 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: 1b9, since it
     now preserves insertion order.

      -- 成員函式: 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:
          c0a. is raised.  If the `default section' name is passed,
          *note ValueError: 1fc. is raised.  The name of the section
          must be a string; if not, *note TypeError: 193. is raised.

          3.2 版更變: Non-string section names raise *note TypeError:
          193.

      -- 成員函式: 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: 49e.; otherwise return *note
          False: 38d.  If the specified `section' is *note None: 158. 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: 336. object or a
          *note path-like object: 36f, 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: 4af.
          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(): 1e60.
          before calling *note read(): 10a9. 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 版新加入: The `encoding' parameter.  Previously, all files
          were read using the default encoding for *note open(): 4f5.

          3.6.1 版新加入: The `filenames' parameter accepts a *note
          path-like object: 36f.

          3.7 版新加入: The `filenames' parameter accepts a *note bytes:
          336. 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 版新加入: Replaces *note readfp(): 1e61.

      -- 成員函式: 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(): c07. 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(): c07. 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: 1fc.  See *note get(): c07. 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(): c07. 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: 1e64.
          `option' and `value' must be strings; if not, *note TypeError:
          193. is raised.

      -- 成員函式: write (fileobject, space_around_delimiters=True)

          Write a representation of the configuration to the specified
          *note file object: b47, which must be opened in text mode
          (accepting strings).  This representation can be parsed by a
          future *note read(): 10a9. call.  If `space_around_delimiters'
          is true, delimiters between keys and values are surrounded by
          spaces.

      -- 成員函式: remove_option (section, option)

          Remove the specified `option' from the specified `section'.
          If the section does not exist, raise *note NoSectionError:
          1e64.  If the option existed to be removed, return *note True:
          49e.; otherwise return *note False: 38d.

      -- 成員函式: 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(): 1e59.
          is called.

      -- 成員函式: readfp (fp, filename=None)

          3.2 版後已棄用: Use *note read_file(): 1e60. instead.

          3.2 版更變: *note readfp(): 1e61. now iterates on `fp' instead
          of calling ‘fp.readline()’.

          For existing code calling *note readfp(): 1e61. with arguments
          which don’t support iteration, the following generator may be
          used as a wrapper around the file-like object:

               def readline_generator(fp):
                   line = fp.readline()
                   while line:
                       yield line
                       line = fp.readline()

          Instead of ‘parser.readfp(fp)’ use
          ‘parser.read_file(readline_generator(fp))’.

 -- Data: configparser.MAX_INTERPOLATION_DEPTH

     The maximum depth for recursive interpolation for ‘get()’ when the
     `raw' parameter is false.  This is relevant only when the default
     `interpolation' is used.


File: python.info,  Node: RawConfigParser Objects,  Next: Exceptions<4>,  Prev: ConfigParser Objects,  Up: configparser --- Configuration file parser

5.14.2.10 RawConfigParser Objects
.................................

 -- 類別: 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: 4af.  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: 1b9, since it
     now preserves insertion order.

          備註: Consider using *note ConfigParser: 4af. 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:
          c0a. is raised.  If the `default section' name is passed,
          *note ValueError: 1fc. 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: 1e64.
          While it is possible to use *note RawConfigParser: 876. (or
          *note ConfigParser: 4af. 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: Exceptions<4>,  Prev: RawConfigParser Objects,  Up: configparser --- Configuration file parser

5.14.2.11 Exceptions
....................

 -- 例外: configparser.Error

     Base class for all other *note configparser: 23. exceptions.

 -- 例外: configparser.NoSectionError

     Exception raised when a specified section is not found.

 -- 例外: configparser.DuplicateSectionError

     Exception raised if ‘add_section()’ 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 版新加入: Optional ‘source’ and ‘lineno’ attributes and
     arguments to *note __init__(): d63. were added.

 -- 例外: 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: 1e67.  Subclass of *note
     InterpolationError: 1e6f.

 -- 例外: configparser.InterpolationMissingOptionError

     Exception raised when an option referenced from a value does not
     exist.  Subclass of *note InterpolationError: 1e6f.

 -- 例外: configparser.InterpolationSyntaxError

     Exception raised when the source text into which substitutions are
     made does not conform to the required syntax.  Subclass of *note
     InterpolationError: 1e6f.

 -- 例外: 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.2 版更變: The ‘filename’ attribute and *note __init__(): d63.
     argument were renamed to ‘source’ for consistency.

註解
....


File: python.info,  Node: netrc --- netrc file processing,  Next: xdrlib --- Encode and decode XDR data,  Prev: configparser --- Configuration file parser,  Up: 檔案格式

5.14.3 ‘netrc’ — netrc file processing
--------------------------------------

`Source code:' Lib/netrc.py(1)

__________________________________________________________________

The *note netrc: 10a5. class parses and encapsulates the netrc file
format used by the Unix ‘ftp’ program and other FTP clients.

 -- 類別: netrc.netrc ([file])

     A *note netrc: 10a5. instance or subclass instance encapsulates
     data from a netrc file.  The initialization argument, if present,
     specifies the file to parse.  If no argument is given, the file
     ‘.netrc’ in the user’s home directory – as determined by *note
     os.path.expanduser(): 1ff. – will be read.  Otherwise, a *note
     FileNotFoundError: 7c5. exception will be raised.  Parse errors
     will raise *note NetrcParseError: 1e77. with diagnostic information
     including the file name, line number, and terminating token.  If no
     argument is specified on a POSIX system, the presence of passwords
     in the ‘.netrc’ file will raise a *note NetrcParseError: 1e77. if
     the file ownership or permissions are insecure (owned by a user
     other than the user running the process, or accessible for read or
     write by any other user).  This implements security behavior
     equivalent to that of ftp and other programs that use ‘.netrc’.

     3.4 版更變: Added the POSIX permission check.

     3.7 版更變: *note os.path.expanduser(): 1ff. is used to find the
     location of the ‘.netrc’ file when `file' is not passed as
     argument.

 -- 例外: netrc.NetrcParseError

     Exception raised by the *note netrc: 10a5. class when syntactical
     errors are encountered in source text.  Instances of this exception
     provide three interesting attributes: ‘msg’ is a textual
     explanation of the error, ‘filename’ is the name of the source
     file, and ‘lineno’ gives the line number on which the error was
     found.

* Menu:

* netrc Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/netrc.py


File: python.info,  Node: netrc Objects,  Up: netrc --- netrc file processing

5.14.3.1 netrc Objects
......................

A *note netrc: 10a5. instance has the following methods:

 -- 成員函式: netrc.authenticators (host)

     Return a 3-tuple ‘(login, account, password)’ of authenticators for
     `host'.  If the netrc file did not contain an entry for the given
     host, return the tuple associated with the ’default’ entry.  If
     neither matching host nor default entry is available, return
     ‘None’.

 -- 成員函式: netrc.__repr__ ()

     Dump the class data as a string in the format of a netrc file.
     (This discards comments and may reorder the entries.)

Instances of *note netrc: 10a5. have public instance variables:

 -- 屬性: netrc.hosts

     Dictionary mapping host names to ‘(login, account, password)’
     tuples.  The ’default’ entry, if any, is represented as a
     pseudo-host by that name.

 -- 屬性: netrc.macros

     Dictionary mapping macro names to string lists.

     備註: Passwords are limited to a subset of the ASCII character set.
     All ASCII punctuation is allowed in passwords, however, note that
     whitespace and non-printable characters are not allowed in
     passwords.  This is a limitation of the way the .netrc file is
     parsed and may be removed in the future.


File: python.info,  Node: xdrlib --- Encode and decode XDR data,  Next: plistlib --- Generate and parse Mac OS X plist files,  Prev: netrc --- netrc file processing,  Up: 檔案格式

5.14.4 ‘xdrlib’ — Encode and decode XDR data
--------------------------------------------

`Source code:' Lib/xdrlib.py(1)

__________________________________________________________________

The *note xdrlib: 133. module supports the External Data Representation
Standard as described in RFC 1014(2), written by Sun Microsystems, Inc.
June 1987.  It supports most of the data types described in the RFC.

The *note xdrlib: 133. module defines two classes, one for packing
variables into XDR representation, and another for unpacking from XDR
representation.  There are also two exception classes.

 -- 類別: xdrlib.Packer

     *note Packer: 1e80. is the class for packing data into XDR
     representation.  The *note Packer: 1e80. class is instantiated with
     no arguments.

 -- 類別: xdrlib.Unpacker (data)

     ‘Unpacker’ is the complementary class which unpacks XDR data values
     from a string buffer.  The input buffer is given as `data'.

也參考
......

RFC 1014(3) - XDR: External Data Representation Standard

     This RFC defined the encoding of data which was XDR at the time
     this module was originally written.  It has apparently been
     obsoleted by RFC 1832(4).

RFC 1832(5) - XDR: External Data Representation Standard

     Newer RFC that provides a revised definition of XDR.

* Menu:

* Packer Objects::
* Unpacker Objects::
* Exceptions: Exceptions<5>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/xdrlib.py

   (2) https://tools.ietf.org/html/rfc1014.html

   (3) https://tools.ietf.org/html/rfc1014.html

   (4) https://tools.ietf.org/html/rfc1832.html

   (5) https://tools.ietf.org/html/rfc1832.html


File: python.info,  Node: Packer Objects,  Next: Unpacker Objects,  Up: xdrlib --- Encode and decode XDR data

5.14.4.1 Packer Objects
.......................

*note Packer: 1e80. instances have the following methods:

 -- 成員函式: Packer.get_buffer ()

     Returns the current pack buffer as a string.

 -- 成員函式: Packer.reset ()

     Resets the pack buffer to the empty string.

In general, you can pack any of the most common XDR data types by
calling the appropriate ‘pack_type()’ method.  Each method takes a
single argument, the value to pack.  The following simple data type
packing methods are supported: ‘pack_uint()’, ‘pack_int()’,
‘pack_enum()’, ‘pack_bool()’, ‘pack_uhyper()’, and ‘pack_hyper()’.

 -- 成員函式: Packer.pack_float (value)

     Packs the single-precision floating point number `value'.

 -- 成員函式: Packer.pack_double (value)

     Packs the double-precision floating point number `value'.

The following methods support packing strings, bytes, and opaque data:

 -- 成員函式: Packer.pack_fstring (n, s)

     Packs a fixed length string, `s'.  `n' is the length of the string
     but it is `not' packed into the data buffer.  The string is padded
     with null bytes if necessary to guaranteed 4 byte alignment.

 -- 成員函式: Packer.pack_fopaque (n, data)

     Packs a fixed length opaque data stream, similarly to *note
     pack_fstring(): 1e88.

 -- 成員函式: Packer.pack_string (s)

     Packs a variable length string, `s'.  The length of the string is
     first packed as an unsigned integer, then the string data is packed
     with *note pack_fstring(): 1e88.

 -- 成員函式: Packer.pack_opaque (data)

     Packs a variable length opaque data string, similarly to *note
     pack_string(): 1e8a.

 -- 成員函式: Packer.pack_bytes (bytes)

     Packs a variable length byte stream, similarly to *note
     pack_string(): 1e8a.

The following methods support packing arrays and lists:

 -- 成員函式: Packer.pack_list (list, pack_item)

     Packs a `list' of homogeneous items.  This method is useful for
     lists with an indeterminate size; i.e.  the size is not available
     until the entire list has been walked.  For each item in the list,
     an unsigned integer ‘1’ is packed first, followed by the data value
     from the list.  `pack_item' is the function that is called to pack
     the individual item.  At the end of the list, an unsigned integer
     ‘0’ is packed.

     For example, to pack a list of integers, the code might appear like
     this:

          import xdrlib
          p = xdrlib.Packer()
          p.pack_list([1, 2, 3], p.pack_int)

 -- 成員函式: Packer.pack_farray (n, array, pack_item)

     Packs a fixed length list (`array') of homogeneous items.  `n' is
     the length of the list; it is `not' packed into the buffer, but a
     *note ValueError: 1fc. exception is raised if ‘len(array)’ is not
     equal to `n'.  As above, `pack_item' is the function used to pack
     each element.

 -- 成員函式: Packer.pack_array (list, pack_item)

     Packs a variable length `list' of homogeneous items.  First, the
     length of the list is packed as an unsigned integer, then each
     element is packed as in *note pack_farray(): 1e8e. above.


File: python.info,  Node: Unpacker Objects,  Next: Exceptions<5>,  Prev: Packer Objects,  Up: xdrlib --- Encode and decode XDR data

5.14.4.2 Unpacker Objects
.........................

The *note Unpacker: 1e81. class offers the following methods:

 -- 成員函式: Unpacker.reset (data)

     Resets the string buffer with the given `data'.

 -- 成員函式: Unpacker.get_position ()

     Returns the current unpack position in the data buffer.

 -- 成員函式: Unpacker.set_position (position)

     Sets the data buffer unpack position to `position'.  You should be
     careful about using *note get_position(): 1e93. and *note
     set_position(): 1e94.

 -- 成員函式: Unpacker.get_buffer ()

     Returns the current unpack data buffer as a string.

 -- 成員函式: Unpacker.done ()

     Indicates unpack completion.  Raises an *note Error: 1e97.
     exception if all of the data has not been unpacked.

In addition, every data type that can be packed with a *note Packer:
1e80, can be unpacked with an *note Unpacker: 1e81.  Unpacking methods
are of the form ‘unpack_type()’, and take no arguments.  They return the
unpacked object.

 -- 成員函式: Unpacker.unpack_float ()

     Unpacks a single-precision floating point number.

 -- 成員函式: Unpacker.unpack_double ()

     Unpacks a double-precision floating point number, similarly to
     *note unpack_float(): 1e98.

In addition, the following methods unpack strings, bytes, and opaque
data:

 -- 成員函式: Unpacker.unpack_fstring (n)

     Unpacks and returns a fixed length string.  `n' is the number of
     characters expected.  Padding with null bytes to guaranteed 4 byte
     alignment is assumed.

 -- 成員函式: Unpacker.unpack_fopaque (n)

     Unpacks and returns a fixed length opaque data stream, similarly to
     *note unpack_fstring(): 1e9a.

 -- 成員函式: Unpacker.unpack_string ()

     Unpacks and returns a variable length string.  The length of the
     string is first unpacked as an unsigned integer, then the string
     data is unpacked with *note unpack_fstring(): 1e9a.

 -- 成員函式: Unpacker.unpack_opaque ()

     Unpacks and returns a variable length opaque data string, similarly
     to *note unpack_string(): 1e9c.

 -- 成員函式: Unpacker.unpack_bytes ()

     Unpacks and returns a variable length byte stream, similarly to
     *note unpack_string(): 1e9c.

The following methods support unpacking arrays and lists:

 -- 成員函式: Unpacker.unpack_list (unpack_item)

     Unpacks and returns a list of homogeneous items.  The list is
     unpacked one element at a time by first unpacking an unsigned
     integer flag.  If the flag is ‘1’, then the item is unpacked and
     appended to the list.  A flag of ‘0’ indicates the end of the list.
     `unpack_item' is the function that is called to unpack the items.

 -- 成員函式: Unpacker.unpack_farray (n, unpack_item)

     Unpacks and returns (as a list) a fixed length array of homogeneous
     items.  `n' is number of list elements to expect in the buffer.  As
     above, `unpack_item' is the function used to unpack each element.

 -- 成員函式: Unpacker.unpack_array (unpack_item)

     Unpacks and returns a variable length `list' of homogeneous items.
     First, the length of the list is unpacked as an unsigned integer,
     then each element is unpacked as in *note unpack_farray(): 1ea0.
     above.


File: python.info,  Node: Exceptions<5>,  Prev: Unpacker Objects,  Up: xdrlib --- Encode and decode XDR data

5.14.4.3 Exceptions
...................

Exceptions in this module are coded as class instances:

 -- 例外: xdrlib.Error

     The base exception class.  *note Error: 1e97. has a single public
     attribute ‘msg’ containing the description of the error.

 -- 例外: xdrlib.ConversionError

     Class derived from *note Error: 1e97.  Contains no additional
     instance variables.

Here is an example of how you would catch one of these exceptions:

     import xdrlib
     p = xdrlib.Packer()
     try:
         p.pack_double(8.01)
     except xdrlib.ConversionError as instance:
         print('packing the double failed:', instance.msg)


File: python.info,  Node: plistlib --- Generate and parse Mac OS X plist files,  Prev: xdrlib --- Encode and decode XDR data,  Up: 檔案格式

5.14.5 ‘plistlib’ — Generate and parse Mac OS X ‘.plist’ files
--------------------------------------------------------------

`Source code:' Lib/plistlib.py(1)

__________________________________________________________________

This module provides an interface for reading and writing the "property
list" files used mainly by Mac OS X and 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(): 891. and
*note load(): 890. functions.

To work with plist data in bytes objects, use *note dumps(): 893. and
*note loads(): 892.

Values can be strings, integers, floats, booleans, tuples, lists,
dictionaries (but only with string keys), *note Data: 94c, *note bytes:
336, ‘bytesarray’ or *note datetime.datetime: 195. objects.

3.4 版更變: New API, old API deprecated.  Support for binary format
plists added.

3.8 版更變: Support added for reading and writing *note UID: 211. tokens
in binary plists as used by NSKeyedArchiver and NSKeyedUnarchiver.

也參考
......

PList manual page(2)

     Apple’s documentation of the file format.

This module defines the following functions:

 -- 函式: plistlib.load (fp, *, fmt=None, use_builtin_types=True,
          dict_type=dict)

     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: 158.: Autodetect the file format

        * *note FMT_XML: 894.: XML file format

        * *note FMT_BINARY: 895.: Binary plist format

     If `use_builtin_types' is true (the default) binary data will be
     returned as instances of *note bytes: 336, otherwise it is returned
     as instances of *note Data: 94c.

     The `dict_type' is the type used for dictionaries that are read
     from the plist file.

     XML data for the *note FMT_XML: 894. format is parsed using the
     Expat parser from *note xml.parsers.expat: 139. – 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 版新加入.

 -- 函式: plistlib.loads (data, *, fmt=None, use_builtin_types=True,
          dict_type=dict)

     Load a plist from a bytes object.  See *note load(): 890. for an
     explanation of the keyword arguments.

     3.4 版新加入.

 -- 函式: plistlib.dump (value, fp, *, fmt=FMT_XML, sort_keys=True,
          skipkeys=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: 894.: XML formatted plist file

        * *note FMT_BINARY: 895.: 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: 193. when a key of a dictionary is not a string,
     otherwise such keys are skipped.

     A *note TypeError: 193. will be raised if the object is of an
     unsupported type or a container that contains objects of
     unsupported types.

     An *note OverflowError: 965. will be raised for integer values that
     cannot be represented in (binary) plist files.

     3.4 版新加入.

 -- 函式: plistlib.dumps (value, *, fmt=FMT_XML, sort_keys=True,
          skipkeys=False)

     Return `value' as a plist-formatted bytes object.  See the
     documentation for *note dump(): 891. for an explanation of the
     keyword arguments of this function.

     3.4 版新加入.

The following functions are deprecated:

 -- 函式: plistlib.readPlist (pathOrFile)

     Read a plist file.  `pathOrFile' may be either a file name or a
     (readable and binary) file object.  Returns the unpacked root
     object (which usually is a dictionary).

     This function calls *note load(): 890. to do the actual work, see
     the documentation of *note that function: 890. for an explanation
     of the keyword arguments.

     3.4 版後已棄用: Use *note load(): 890. instead.

     3.7 版更變: Dict values in the result are now normal dicts.  You no
     longer can use attribute access to access items of these
     dictionaries.

 -- 函式: plistlib.writePlist (rootObject, pathOrFile)

     Write `rootObject' to an XML plist file.  `pathOrFile' may be
     either a file name or a (writable and binary) file object

     3.4 版後已棄用: Use *note dump(): 891. instead.

 -- 函式: plistlib.readPlistFromBytes (data)

     Read a plist data from a bytes object.  Return the root object.

     See *note load(): 890. for a description of the keyword arguments.

     3.4 版後已棄用: Use *note loads(): 892. instead.

     3.7 版更變: Dict values in the result are now normal dicts.  You no
     longer can use attribute access to access items of these
     dictionaries.

 -- 函式: plistlib.writePlistToBytes (rootObject)

     Return `rootObject' as an XML plist-formatted bytes object.

     3.4 版後已棄用: Use *note dumps(): 893. instead.

The following classes are available:

 -- 類別: plistlib.Data (data)

     Return a "data" wrapper object around the bytes object `data'.
     This is used in functions converting from/to plists to represent
     the ‘<data>’ type available in plists.

     It has one attribute, ‘data’, that can be used to retrieve the
     Python bytes object stored in it.

     3.4 版後已棄用: Use a *note bytes: 336. object instead.

 -- 類別: plistlib.UID (data)

     Wraps an *note int: 185.  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:

 -- Data: plistlib.FMT_XML

     The XML format for plist files.

     3.4 版新加入.

 -- Data: plistlib.FMT_BINARY

     The binary format for plist files

     3.4 版新加入.

* Menu:

* Examples: Examples<8>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/plistlib.py

   (2) 
https://developer.apple.com/library/content/documentation/Cocoa/Conceptual/PropertyLists/


File: python.info,  Node: Examples<8>,  Up: plistlib --- Generate and parse Mac OS X plist files

5.14.5.1 Examples
.................

Generating a plist:

     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.fromtimestamp(time.mktime(time.gmtime())),
     )
     with open(fileName, 'wb') as fp:
         dump(pl, fp)

Parsing a plist:

     with open(fileName, 'rb') as fp:
         pl = load(fp)
     print(pl["aKey"])


File: python.info,  Node: Cryptographic Services,  Next: Generic Operating System Services,  Prev: 檔案格式,  Up: Python 標準函式庫 Standard Library

5.15 Cryptographic Services
===========================

The modules described in this chapter implement various algorithms of a
cryptographic nature.  They are available at the discretion of the
installation.  On Unix systems, the *note crypt: 29. module may also be
available.  Here’s an overview:

* Menu:

* hashlib: hashlib --- Secure hashes and message digests. Secure hashes and message digests
* hmac: hmac --- Keyed-Hashing for Message Authentication. Keyed-Hashing for Message Authentication
* secrets: secrets --- Generate secure random numbers for managing secrets. Generate secure random numbers for managing secrets


File: python.info,  Node: hashlib --- Secure hashes and message digests,  Next: hmac --- Keyed-Hashing for Message Authentication,  Up: Cryptographic Services

5.15.1 ‘hashlib’ — Secure hashes and message digests
----------------------------------------------------

`Source code:' Lib/hashlib.py(1)

__________________________________________________________________

This module implements a common interface to many different secure hash
and message digest algorithms.  Included are the FIPS secure hash
algorithms SHA1, SHA224, SHA256, SHA384, and SHA512 (defined in FIPS
180-2) as well as RSA’s MD5 algorithm (defined in Internet RFC 1321(2)).
The terms "secure hash" and "message digest" are interchangeable.  Older
algorithms were called message digests.  The modern term is secure hash.

     備註: If you want the adler32 or crc32 hash functions, they are
     available in the *note zlib: 145. module.

     警告: Some algorithms have known hash collision weaknesses, refer
     to the "See also" section at the end.

* Menu:

* Hash algorithms::
* SHAKE variable length digests::
* Key derivation::
* BLAKE2::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/hashlib.py

   (2) https://tools.ietf.org/html/rfc1321.html


File: python.info,  Node: Hash algorithms,  Next: SHAKE variable length digests,  Up: hashlib --- Secure hashes and message digests

5.15.1.1 Hash algorithms
........................

There is one constructor method named for each type of `hash'.  All
return a hash object with the same simple interface.  For example: use
‘sha256()’ to create a SHA-256 hash object.  You can now feed this
object with *note bytes-like objects: 5ed. (normally *note bytes: 336.)
using the ‘update()’ method.  At any point you can ask it for the
`digest' of the concatenation of the data fed to it so far using the
‘digest()’ or ‘hexdigest()’ methods.

     備註: For better multithreading performance, the Python *note GIL:
     bef. is released for data larger than 2047 bytes at object creation
     or on update.

     備註: Feeding string objects into ‘update()’ is not supported, as
     hashes work on bytes, not on characters.

Constructors for hash algorithms that are always present in this module
are ‘sha1()’, ‘sha224()’, ‘sha256()’, ‘sha384()’, ‘sha512()’, *note
blake2b(): 551, and *note blake2s(): 552.  ‘md5()’ is normally available
as well, though it may be missing if you are using a rare "FIPS
compliant" build of Python.  Additional algorithms may also be available
depending upon the OpenSSL library that Python uses on your platform.
On most platforms the ‘sha3_224()’, ‘sha3_256()’, ‘sha3_384()’,
‘sha3_512()’, ‘shake_128()’, ‘shake_256()’ are also available.

3.6 版新加入: SHA3 (Keccak) and SHAKE constructors ‘sha3_224()’,
‘sha3_256()’, ‘sha3_384()’, ‘sha3_512()’, ‘shake_128()’, ‘shake_256()’.

3.6 版新加入: *note blake2b(): 551. and *note blake2s(): 552. were
added.

For example, to obtain the digest of the byte string ‘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.digest_size
     32
     >>> m.block_size
     64

More condensed:

     >>> hashlib.sha224(b"Nobody inspects the spammish repetition").hexdigest()
     'a4337bc45a8fc544c03f52dc550cd6e1e87021bc896588bd79e901e2'

 -- 函式: hashlib.new (name[, data])

     Is a generic constructor that takes the string `name' of the
     desired algorithm as its first parameter.  It also exists to allow
     access to the above listed hashes as well as any other algorithms
     that your OpenSSL library may offer.  The named constructors are
     much faster than *note new(): 1eaf. and should be preferred.

Using *note new(): 1eaf. with an algorithm provided by OpenSSL:

     >>> h = hashlib.new('sha512_256')
     >>> h.update(b"Nobody inspects the spammish repetition")
     >>> h.hexdigest()
     '19197dc4d03829df858011c6c87600f994a858103bbc19005f20987aa19a97e2'

Hashlib provides the following constant attributes:

 -- Data: hashlib.algorithms_guaranteed

     A set containing the names of the hash algorithms guaranteed to be
     supported by this module on all platforms.  Note that ’md5’ is in
     this list despite some upstream vendors offering an odd "FIPS
     compliant" Python build that excludes it.

     3.2 版新加入.

 -- Data: hashlib.algorithms_available

     A set containing the names of the hash algorithms that are
     available in the running Python interpreter.  These names will be
     recognized when passed to *note new(): 1eaf.  *note
     algorithms_guaranteed: d01. will always be a subset.  The same
     algorithm may appear multiple times in this set under different
     names (thanks to OpenSSL).

     3.2 版新加入.

The following values are provided as constant attributes of the hash
objects returned by the constructors:

 -- Data: hash.digest_size

     The size of the resulting hash in bytes.

 -- Data: hash.block_size

     The internal block size of the hash algorithm in bytes.

A hash object has the following attributes:

 -- 屬性: hash.name

     The canonical name of this hash, always lowercase and always
     suitable as a parameter to *note new(): 1eaf. to create another
     hash of this type.

     3.4 版更變: The name attribute has been present in CPython since
     its inception, but until Python 3.4 was not formally specified, so
     may not exist on some platforms.

A hash object has the following methods:

 -- 成員函式: hash.update (data)

     Update the hash object with the *note bytes-like object: 5ed.
     Repeated calls are equivalent to a single call with the
     concatenation of all the arguments: ‘m.update(a); m.update(b)’ is
     equivalent to ‘m.update(a+b)’.

     3.1 版更變: The Python GIL is released to allow other threads to
     run while hash updates on data larger than 2047 bytes is taking
     place when using hash algorithms supplied by OpenSSL.

 -- 成員函式: hash.digest ()

     Return the digest of the data passed to the *note update(): 1eb2.
     method so far.  This is a bytes object of size *note digest_size:
     1eb0. which may contain bytes in the whole range from 0 to 255.

 -- 成員函式: hash.hexdigest ()

     Like *note digest(): 1eb3. except the digest is returned as a
     string object of double length, containing only hexadecimal digits.
     This may be used to exchange the value safely in email or other
     non-binary environments.

 -- 成員函式: hash.copy ()

     Return a copy ("clone") of the hash object.  This can be used to
     efficiently compute the digests of data sharing a common initial
     substring.


File: python.info,  Node: SHAKE variable length digests,  Next: Key derivation,  Prev: Hash algorithms,  Up: hashlib --- Secure hashes and message digests

5.15.1.2 SHAKE variable length digests
......................................

The ‘shake_128()’ and ‘shake_256()’ algorithms provide variable length
digests with length_in_bits//2 up to 128 or 256 bits of security.  As
such, their digest methods require a length.  Maximum length is not
limited by the SHAKE algorithm.

 -- 成員函式: shake.digest (length)

     Return the digest of the data passed to the ‘update()’ method so
     far.  This is a bytes object of size `length' which may contain
     bytes in the whole range from 0 to 255.

 -- 成員函式: shake.hexdigest (length)

     Like *note digest(): 102a. except the digest is returned as a
     string object of double length, containing only hexadecimal digits.
     This may be used to exchange the value safely in email or other
     non-binary environments.


File: python.info,  Node: Key derivation,  Next: BLAKE2,  Prev: SHAKE variable length digests,  Up: hashlib --- Secure hashes and message digests

5.15.1.3 Key derivation
.......................

Key derivation and key stretching algorithms are designed for secure
password hashing.  Naive algorithms such as ‘sha1(password)’ are not
resistant against brute-force attacks.  A good password hashing function
must be tunable, slow, and include a salt(1).

 -- 函式: hashlib.pbkdf2_hmac (hash_name, password, salt, iterations,
          dklen=None)

     The function provides PKCS#5 password-based key derivation function
     2.  It uses HMAC as pseudorandom function.

     The string `hash_name' is the desired name of the hash digest
     algorithm for HMAC, e.g.  ’sha1’ or ’sha256’.  `password' and
     `salt' are interpreted as buffers of bytes.  Applications and
     libraries should limit `password' to a sensible length (e.g.
     1024).  `salt' should be about 16 or more bytes from a proper
     source, e.g.  *note os.urandom(): 4d6.

     The number of `iterations' should be chosen based on the hash
     algorithm and computing power.  As of 2013, at least 100,000
     iterations of SHA-256 are suggested.

     `dklen' is the length of the derived key.  If `dklen' is ‘None’
     then the digest size of the hash algorithm `hash_name' is used,
     e.g.  64 for SHA-512.

          >>> import hashlib
          >>> dk = hashlib.pbkdf2_hmac('sha256', b'password', b'salt', 100000)
          >>> dk.hex()
          '0394a2ede332c9a13eb82e9b24631604c31df978b4e2f0fbd2c549944f9d79a5'

     3.4 版新加入.

          備註: A fast implementation of `pbkdf2_hmac' is available with
          OpenSSL. The Python implementation uses an inline version of
          *note hmac: 8f.  It is about three times slower and doesn’t
          release the GIL.

 -- 函式: hashlib.scrypt (password, *, salt, n, r, p, maxmem=0,
          dklen=64)

     The function provides scrypt password-based key derivation function
     as defined in RFC 7914(2).

     `password' and `salt' must be *note bytes-like objects: 5ed.
     Applications and libraries should limit `password' to a sensible
     length (e.g.  1024).  `salt' should be about 16 or more bytes from
     a proper source, e.g.  *note os.urandom(): 4d6.

     `n' is the CPU/Memory cost factor, `r' the block size, `p'
     parallelization factor and `maxmem' limits memory (OpenSSL 1.1.0
     defaults to 32 MiB). `dklen' is the length of the derived key.

     *note Availability: 1364.: OpenSSL 1.1+.

     3.6 版新加入.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Salt_%28cryptography%29

   (2) https://tools.ietf.org/html/rfc7914.html


File: python.info,  Node: BLAKE2,  Prev: Key derivation,  Up: hashlib --- Secure hashes and message digests

5.15.1.4 BLAKE2
...............

BLAKE2(1) is a cryptographic hash function defined in RFC 7693(2) that
comes in two flavors:

   * `BLAKE2b', optimized for 64-bit platforms and produces digests of
     any size between 1 and 64 bytes,

   * `BLAKE2s', optimized for 8- to 32-bit platforms and produces
     digests of any size between 1 and 32 bytes.

BLAKE2 supports `keyed mode' (a faster and simpler replacement for
HMAC(3)), `salted hashing', `personalization', and `tree hashing'.

Hash objects from this module follow the API of standard library’s *note
hashlib: 8d. objects.

* Menu:

* Creating hash objects::
* Constants: Constants<5>.
* Examples: Examples<9>.
* Credits::

   ---------- Footnotes ----------

   (1) https://blake2.net

   (2) https://tools.ietf.org/html/rfc7693.html

   (3) 
https://en.wikipedia.org/wiki/Hash-based_message_authentication_code


File: python.info,  Node: Creating hash objects,  Next: Constants<5>,  Up: BLAKE2

5.15.1.5 Creating hash objects
..............................

New hash objects are created by calling constructor functions:

 -- 函式: 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)

 -- 函式: 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)

These functions return the corresponding hash objects for calculating
BLAKE2b or BLAKE2s.  They optionally take these general parameters:

   * `data': initial chunk of data to hash, which must be *note
     bytes-like object: 5ed.  It can be passed only as positional
     argument.

   * `digest_size': size of output digest in bytes.

   * `key': key for keyed hashing (up to 64 bytes for BLAKE2b, up to 32
     bytes for BLAKE2s).

   * `salt': salt for randomized hashing (up to 16 bytes for BLAKE2b, up
     to 8 bytes for BLAKE2s).

   * `person': personalization string (up to 16 bytes for BLAKE2b, up to
     8 bytes for BLAKE2s).

The following table shows limits for general parameters (in bytes):

Hash        digest_size     len(key)     len(salt)     len(person)
                                                       
-----------------------------------------------------------------------
                                                       
BLAKE2b     64              64           16            16
                                                       
                                                       
BLAKE2s     32              32           8             8
                                                       

     備註: BLAKE2 specification defines constant lengths for salt and
     personalization parameters, however, for convenience, this
     implementation accepts byte strings of any size up to the specified
     length.  If the length of the parameter is less than specified, it
     is padded with zeros, thus, for example, ‘b'salt'’ and
     ‘b'salt\x00'’ is the same value.  (This is not the case for `key'.)

These sizes are available as module *note constants: 1eba. described
below.

Constructor functions also accept the following tree hashing parameters:

   * `fanout': fanout (0 to 255, 0 if unlimited, 1 in sequential mode).

   * `depth': maximal depth of tree (1 to 255, 255 if unlimited, 1 in
     sequential mode).

   * `leaf_size': maximal byte length of leaf (0 to 2**32-1, 0 if
     unlimited or in sequential mode).

   * `node_offset': node offset (0 to 2**64-1 for BLAKE2b, 0 to 2**48-1
     for BLAKE2s, 0 for the first, leftmost, leaf, or in sequential
     mode).

   * `node_depth': node depth (0 to 255, 0 for leaves, or in sequential
     mode).

   * `inner_size': inner digest size (0 to 64 for BLAKE2b, 0 to 32 for
     BLAKE2s, 0 in sequential mode).

   * `last_node': boolean indicating whether the processed node is the
     last one (‘False’ for sequential mode).

[Explanation of tree mode parameters.]
Figure

See section 2.10 in BLAKE2 specification(1) for comprehensive review of
tree hashing.

   ---------- Footnotes ----------

   (1) https://blake2.net/blake2_20130129.pdf


File: python.info,  Node: Constants<5>,  Next: Examples<9>,  Prev: Creating hash objects,  Up: BLAKE2

5.15.1.6 Constants
..................

 -- Data: blake2b.SALT_SIZE

 -- Data: blake2s.SALT_SIZE

Salt length (maximum length accepted by constructors).

 -- Data: blake2b.PERSON_SIZE

 -- Data: blake2s.PERSON_SIZE

Personalization string length (maximum length accepted by constructors).

 -- Data: blake2b.MAX_KEY_SIZE

 -- Data: blake2s.MAX_KEY_SIZE

Maximum key size.

 -- Data: blake2b.MAX_DIGEST_SIZE

 -- Data: blake2s.MAX_DIGEST_SIZE

Maximum digest size that the hash function can output.


File: python.info,  Node: Examples<9>,  Next: Credits,  Prev: Constants<5>,  Up: BLAKE2

5.15.1.7 Examples
.................

* Menu:

* Simple hashing::
* Using different digest sizes::
* Keyed hashing::
* Randomized hashing::
* Personalization::
* Tree mode::


File: python.info,  Node: Simple hashing,  Next: Using different digest sizes,  Up: Examples<9>

5.15.1.8 Simple hashing
.......................

To calculate hash of some data, you should first construct a hash object
by calling the appropriate constructor function (*note blake2b(): 551.
or *note blake2s(): 552.), then update it with the data by calling
‘update()’ on the object, and, finally, get the digest out of the object
by calling ‘digest()’ (or ‘hexdigest()’ for hex-encoded string).

     >>> from hashlib import blake2b
     >>> h = blake2b()
     >>> h.update(b'Hello world')
     >>> h.hexdigest()
     '6ff843ba685842aa82031d3f53c48b66326df7639a63d128974c5c14f31a0f33343a8c65551134ed1ae0f2b0dd2bb495dc81039e3eeb0aa1bb0388bbeac29183'

As a shortcut, you can pass the first chunk of data to update directly
to the constructor as the positional argument:

     >>> from hashlib import blake2b
     >>> blake2b(b'Hello world').hexdigest()
     '6ff843ba685842aa82031d3f53c48b66326df7639a63d128974c5c14f31a0f33343a8c65551134ed1ae0f2b0dd2bb495dc81039e3eeb0aa1bb0388bbeac29183'

You can call *note hash.update(): 1eb2. as many times as you need to
iteratively update the hash:

     >>> 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: Using different digest sizes,  Next: Keyed hashing,  Prev: Simple hashing,  Up: Examples<9>

5.15.1.9 Using different digest sizes
.....................................

BLAKE2 has configurable size of digests up to 64 bytes for BLAKE2b and
up to 32 bytes for BLAKE2s.  For example, to replace SHA-1 with BLAKE2b
without changing the size of output, we can tell BLAKE2b to produce
20-byte digests:

     >>> 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

Hash objects with different digest sizes have completely different
outputs (shorter hashes are `not' prefixes of longer hashes); BLAKE2b
and BLAKE2s produce different outputs even if the output length is the
same:

     >>> 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: Using different digest sizes,  Up: Examples<9>

5.15.1.10 Keyed hashing
.......................

Keyed hashing can be used for authentication as a faster and simpler
replacement for Hash-based message authentication code(1) (HMAC). BLAKE2
can be securely used in prefix-MAC mode thanks to the
indifferentiability property inherited from BLAKE.

This example shows how to get a (hex-encoded) 128-bit authentication
code for message ‘b'message data'’ with key ‘b'pseudorandom key'’:

     >>> from hashlib import blake2b
     >>> h = blake2b(key=b'pseudorandom key', digest_size=16)
     >>> h.update(b'message data')
     >>> h.hexdigest()
     '3d363ff7401e02026f4a4687d4863ced'

As a practical example, a web application can symmetrically sign cookies
sent to users and later verify them to make sure they weren’t tampered
with:

     >>> 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

Even though there’s a native keyed hashing mode, BLAKE2 can, of course,
be used in HMAC construction with *note hmac: 8f. module:

     >>> import hmac, hashlib
     >>> m = hmac.new(b'secret key', digestmod=hashlib.blake2s)
     >>> m.update(b'message')
     >>> m.hexdigest()
     'e3c8102868d28b5ff85fc35dda07329970d1a01e273c37481326fe0c861c8142'

   ---------- Footnotes ----------

   (1) 
https://en.wikipedia.org/wiki/Hash-based_message_authentication_code


File: python.info,  Node: Randomized hashing,  Next: Personalization,  Prev: Keyed hashing,  Up: Examples<9>

5.15.1.11 Randomized hashing
............................

By setting `salt' parameter users can introduce randomization to the
hash function.  Randomized hashing is useful for protecting against
collision attacks on the hash function used in digital signatures.

     Randomized hashing is designed for situations where one party, the
     message preparer, generates all or part of a message to be signed
     by a second party, the message signer.  If the message preparer is
     able to find cryptographic hash function collisions (i.e., two
     messages producing the same hash value), then they might prepare
     meaningful versions of the message that would produce the same hash
     value and digital signature, but with different results (e.g.,
     transferring $1,000,000 to an account, rather than $10).
     Cryptographic hash functions have been designed with collision
     resistance as a major goal, but the current concentration on
     attacking cryptographic hash functions may result in a given
     cryptographic hash function providing less collision resistance
     than expected.  Randomized hashing offers the signer additional
     protection by reducing the likelihood that a preparer can generate
     two or more messages that ultimately yield the same hash value
     during the digital signature generation process — even if it is
     practical to find collisions for the hash function.  However, the
     use of randomized hashing may reduce the amount of security
     provided by a digital signature when all portions of the message
     are prepared by the signer.

     (NIST SP-800-106 "Randomized Hashing for Digital Signatures"(1))

In BLAKE2 the salt is processed as a one-time input to the hash function
during initialization, rather than as an input to each compression
function.

     警告: `Salted hashing' (or just hashing) with BLAKE2 or any other
     general-purpose cryptographic hash function, such as SHA-256, is
     not suitable for hashing passwords.  See BLAKE2 FAQ(2) for more
     information.

     >>> 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/final

   (2) https://blake2.net/#qa


File: python.info,  Node: Personalization,  Next: Tree mode,  Prev: Randomized hashing,  Up: Examples<9>

5.15.1.12 Personalization
.........................

Sometimes it is useful to force hash function to produce different
digests for the same input for different purposes.  Quoting the authors
of the Skein hash function:

     We recommend that all application designers seriously consider
     doing this; we have seen many protocols where a hash that is
     computed in one part of the protocol can be used in an entirely
     different part because two hash computations were done on similar
     or related data, and the attacker can force the application to make
     the hash inputs the same.  Personalizing each hash function used in
     the protocol summarily stops this type of attack.

     (The Skein Hash Function Family(1), p.  21)

BLAKE2 can be personalized by passing bytes to the `person' argument:

     >>> 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'

Personalization together with the keyed mode can also be used to derive
different keys from a single one.

     >>> 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) http://www.skein-hash.info/sites/default/files/skein1.3.pdf


File: python.info,  Node: Tree mode,  Prev: Personalization,  Up: Examples<9>

5.15.1.13 Tree mode
...................

Here’s an example of hashing a minimal tree with two leaf nodes:

       10
      /  \
     00  01

This example uses 64-byte internal digests, and returns the 32-byte
final digest:

     >>> 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: Credits,  Prev: Examples<9>,  Up: BLAKE2

5.15.1.14 Credits
.................

BLAKE2(1) was designed by `Jean-Philippe Aumasson', `Samuel Neves',
`Zooko Wilcox-O’Hearn', and `Christian Winnerlein' based on SHA-3(2)
finalist BLAKE(3) created by `Jean-Philippe Aumasson', `Luca Henzen',
`Willi Meier', and `Raphael C.-W. Phan'.

It uses core algorithm from ChaCha(4) cipher designed by `Daniel J.
Bernstein'.

The stdlib implementation is based on pyblake2(5) module.  It was
written by `Dmitry Chestnykh' based on C implementation written by
`Samuel Neves'.  The documentation was copied from pyblake2(6) and
written by `Dmitry Chestnykh'.

The C code was partly rewritten for Python by `Christian Heimes'.

The following public domain dedication applies for both C hash function
implementation, extension code, and this documentation:

     To the extent possible under law, the author(s) have dedicated all
     copyright and related and neighboring rights to this software to
     the public domain worldwide.  This software is distributed without
     any warranty.

     You should have received a copy of the CC0 Public Domain Dedication
     along with this software.  If not, see
     ‘https://creativecommons.org/publicdomain/zero/1.0/’.

The following people have helped with development or contributed their
changes to the project and the public domain according to the Creative
Commons Public Domain Dedication 1.0 Universal:

   * `Alexandr Sokolovskiy'

也參考
......

Module *note hmac: 8f.

     A module to generate message authentication codes using hashes.

Module *note base64: e.

     Another way to encode binary hashes for non-binary environments.

‘https://blake2.net’

     Official BLAKE2 website.

‘https://csrc.nist.gov/csrc/media/publications/fips/180/2/archive/2002-08-01/documents/fips180-2.pdf’

     The FIPS 180-2 publication on Secure Hash Algorithms.

‘https://en.wikipedia.org/wiki/Cryptographic_hash_function#Cryptographic_hash_algorithms’

     Wikipedia article with information on which algorithms have known
     issues and what that means regarding their use.

‘https://www.ietf.org/rfc/rfc2898.txt’

     PKCS #5: Password-Based Cryptography Specification Version 2.0

   ---------- Footnotes ----------

   (1) https://blake2.net

   (2) https://en.wikipedia.org/wiki/NIST_hash_function_competition

   (3) 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 --- Keyed-Hashing for Message Authentication,  Next: secrets --- Generate secure random numbers for managing secrets,  Prev: hashlib --- Secure hashes and message digests,  Up: Cryptographic Services

5.15.2 ‘hmac’ — Keyed-Hashing for Message Authentication
--------------------------------------------------------

`Source code:' Lib/hmac.py(1)

__________________________________________________________________

This module implements the HMAC algorithm as described by RFC 2104(2).

 -- 函式: hmac.new (key, msg=None, digestmod='')

     Return a new hmac object.  `key' is a bytes or bytearray object
     giving the secret key.  If `msg' is present, the method call
     ‘update(msg)’ is made.  `digestmod' is the digest name, digest
     constructor or module for the HMAC object to use.  It may be any
     name suitable to *note hashlib.new(): 1eaf.  Despite its argument
     position, it is required.

     3.4 版更變: Parameter `key' can be a bytes or bytearray object.
     Parameter `msg' can be of any type supported by *note hashlib: 8d.
     Parameter `digestmod' can be the name of a hash algorithm.

     Deprecated since version 3.4, removed in version 3.8: MD5 as
     implicit default digest for `digestmod' is deprecated.  The
     digestmod parameter is now required.  Pass it as a keyword argument
     to avoid awkwardness when you do not have an initial msg.

 -- 函式: hmac.digest (key, msg, digest)

     Return digest of `msg' for given secret `key' and `digest'.  The
     function is equivalent to ‘HMAC(key, msg, digest).digest()’, but
     uses an optimized C or inline implementation, which is faster for
     messages that fit into memory.  The parameters `key', `msg', and
     `digest' have the same meaning as in *note new(): 859.

     CPython implementation detail, the optimized C implementation is
     only used when `digest' is a string and name of a digest algorithm,
     which is supported by OpenSSL.

     3.7 版新加入.

An HMAC object has the following methods:

 -- 成員函式: HMAC.update (msg)

     Update the hmac object with `msg'.  Repeated calls are equivalent
     to a single call with the concatenation of all the arguments:
     ‘m.update(a); m.update(b)’ is equivalent to ‘m.update(a + b)’.

     3.4 版更變: Parameter `msg' can be of any type supported by *note
     hashlib: 8d.

 -- 成員函式: HMAC.digest ()

     Return the digest of the bytes passed to the *note update(): 85a.
     method so far.  This bytes object will be the same length as the
     `digest_size' of the digest given to the constructor.  It may
     contain non-ASCII bytes, including NUL bytes.

          警告: When comparing the output of *note digest(): 395. to an
          externally-supplied digest during a verification routine, it
          is recommended to use the *note compare_digest(): a11.
          function instead of the ‘==’ operator to reduce the
          vulnerability to timing attacks.

 -- 成員函式: HMAC.hexdigest ()

     Like *note digest(): 395. except the digest is returned as a string
     twice the length containing only hexadecimal digits.  This may be
     used to exchange the value safely in email or other non-binary
     environments.

          警告: When comparing the output of *note hexdigest(): 1ece. to
          an externally-supplied digest during a verification routine,
          it is recommended to use the *note compare_digest(): a11.
          function instead of the ‘==’ operator to reduce the
          vulnerability to timing attacks.

 -- 成員函式: HMAC.copy ()

     Return a copy ("clone") of the hmac object.  This can be used to
     efficiently compute the digests of strings that share a common
     initial substring.

A hash object has the following attributes:

 -- 屬性: HMAC.digest_size

     The size of the resulting HMAC digest in bytes.

 -- 屬性: HMAC.block_size

     The internal block size of the hash algorithm in bytes.

     3.4 版新加入.

 -- 屬性: HMAC.name

     The canonical name of this HMAC, always lowercase, e.g.
     ‘hmac-md5’.

     3.4 版新加入.

This module also provides the following helper function:

 -- 函式: hmac.compare_digest (a, b)

     Return ‘a == b’.  This function uses an approach designed to
     prevent timing analysis by avoiding content-based short circuiting
     behaviour, making it appropriate for cryptography.  `a' and `b'
     must both be of the same type: either *note str: 335. (ASCII only,
     as e.g.  returned by *note HMAC.hexdigest(): 1ece.), or a *note
     bytes-like object: 5ed.

          備註: If `a' and `b' are of different lengths, or if an error
          occurs, a timing attack could theoretically reveal information
          about the types and lengths of `a' and `b'—but not their
          values.

     3.3 版新加入.

也參考
......

Module *note hashlib: 8d.

     The Python module providing secure hash functions.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/hmac.py

   (2) https://tools.ietf.org/html/rfc2104.html


File: python.info,  Node: secrets --- Generate secure random numbers for managing secrets,  Prev: hmac --- Keyed-Hashing for Message Authentication,  Up: Cryptographic Services

5.15.3 ‘secrets’ — Generate secure random numbers for managing secrets
----------------------------------------------------------------------

3.6 版新加入.

`Source code:' Lib/secrets.py(1)

__________________________________________________________________

The *note secrets: e5. module is used for generating cryptographically
strong random numbers suitable for managing data such as passwords,
account authentication, security tokens, and related secrets.

In particular, *note secrets: e5. should be used in preference to the
default pseudo-random number generator in the *note random: dd. module,
which is designed for modelling and simulation, not security or
cryptography.

也參考
......

PEP 506(2)

* Menu:

* Random numbers::
* Generating tokens::
* Other functions::
* Recipes and best practices::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/secrets.py

   (2) https://www.python.org/dev/peps/pep-0506


File: python.info,  Node: Random numbers,  Next: Generating tokens,  Up: secrets --- Generate secure random numbers for managing secrets

5.15.3.1 Random numbers
.......................

The *note secrets: e5. module provides access to the most secure source
of randomness that your operating system provides.

 -- 類別: secrets.SystemRandom

     A class for generating random numbers using the highest-quality
     sources provided by the operating system.  See *note
     random.SystemRandom: 1b0e. for additional details.

 -- 函式: secrets.choice (sequence)

     Return a randomly-chosen element from a non-empty sequence.

 -- 函式: secrets.randbelow (n)

     Return a random int in the range [0, `n').

 -- 函式: secrets.randbits (k)

     Return an int with `k' random bits.


File: python.info,  Node: Generating tokens,  Next: Other functions,  Prev: Random numbers,  Up: secrets --- Generate secure random numbers for managing secrets

5.15.3.2 Generating tokens
..........................

The *note secrets: e5. module provides functions for generating secure
tokens, suitable for applications such as password resets, hard-to-guess
URLs, and similar.

 -- 函式: secrets.token_bytes ([nbytes=None])

     Return a random byte string containing `nbytes' number of bytes.
     If `nbytes' is ‘None’ or not supplied, a reasonable default is
     used.

          >>> token_bytes(16)
          b'\xebr\x17D*t\xae\xd4\xe3S\xb6\xe2\xebP1\x8b'

 -- 函式: secrets.token_hex ([nbytes=None])

     Return a random text string, in hexadecimal.  The string has
     `nbytes' random bytes, each byte converted to two hex digits.  If
     `nbytes' is ‘None’ or not supplied, a reasonable default is used.

          >>> token_hex(16)
          'f9bf78b9a18ce6d46a0cd2b0b86df9da'

 -- 函式: secrets.token_urlsafe ([nbytes=None])

     Return a random URL-safe text string, containing `nbytes' random
     bytes.  The text is Base64 encoded, so on average each byte results
     in approximately 1.3 characters.  If `nbytes' is ‘None’ or not
     supplied, a reasonable default is used.

          >>> token_urlsafe(16)
          'Drmhze6EPcv0fN_81Bj-nA'

* Menu:

* How many bytes should tokens use?::


File: python.info,  Node: How many bytes should tokens use?,  Up: Generating tokens

5.15.3.3 How many bytes should tokens use?
..........................................

To be secure against brute-force attacks(1), tokens need to have
sufficient randomness.  Unfortunately, what is considered sufficient
will necessarily increase as computers get more powerful and able to
make more guesses in a shorter period.  As of 2015, it is believed that
32 bytes (256 bits) of randomness is sufficient for the typical use-case
expected for the *note secrets: e5. module.

For those who want to manage their own token length, you can explicitly
specify how much randomness is used for tokens by giving an *note int:
185. argument to the various ‘token_*’ functions.  That argument is
taken as the number of bytes of randomness to use.

Otherwise, if no argument is provided, or if the argument is ‘None’, the
‘token_*’ functions will use a reasonable default instead.

     備註: That default is subject to change at any time, including
     during maintenance releases.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Brute-force_attack


File: python.info,  Node: Other functions,  Next: Recipes and best practices,  Prev: Generating tokens,  Up: secrets --- Generate secure random numbers for managing secrets

5.15.3.4 Other functions
........................

 -- 函式: secrets.compare_digest (a, b)

     Return ‘True’ if strings `a' and `b' are equal, otherwise ‘False’,
     in such a way as to reduce the risk of timing attacks(1).  See
     *note hmac.compare_digest(): a11. for additional details.

   ---------- Footnotes ----------

   (1) https://codahale.com/a-lesson-in-timing-attacks/


File: python.info,  Node: Recipes and best practices,  Prev: Other functions,  Up: secrets --- Generate secure random numbers for managing secrets

5.15.3.5 Recipes and best practices
...................................

This section shows recipes and best practices for using *note secrets:
e5. to manage a basic level of security.

Generate an eight-character alphanumeric password:

     import string
     import secrets
     alphabet = string.ascii_letters + string.digits
     password = ''.join(secrets.choice(alphabet) for i in range(8))

     備註: Applications should not store passwords in a recoverable
     format(1), whether plain text or encrypted.  They should be salted
     and hashed using a cryptographically-strong one-way (irreversible)
     hash function.

Generate a ten-character alphanumeric password with at least one
lowercase character, at least one uppercase character, and at least
three digits:

     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

Generate an XKCD-style 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))

Generate a hard-to-guess temporary URL containing a security token
suitable for password recovery applications:

     import secrets
     url = 'https://mydomain.com/reset=' + secrets.token_urlsafe()

   ---------- Footnotes ----------

   (1) http://cwe.mitre.org/data/definitions/257.html

   (2) https://xkcd.com/936/


File: python.info,  Node: Generic Operating System Services,  Next: Concurrent Execution,  Prev: Cryptographic Services,  Up: Python 標準函式庫 Standard Library

5.16 Generic Operating System Services
======================================

The modules described in this chapter provide interfaces to operating
system features that are available on (almost) all operating systems,
such as files and a clock.  The interfaces are generally modeled after
the Unix or C interfaces, but they are available on most other systems
as well.  Here’s an overview:

* Menu:

* os: os --- Miscellaneous operating system interfaces. Miscellaneous operating system interfaces
* io: io --- Core tools for working with streams. Core tools for working with streams
* time: time --- Time access and conversions. Time access and conversions
* argparse: argparse --- Parser for command-line options arguments and sub-commands. Parser for command-line options, arguments and sub-
                        commands
* getopt: getopt --- C-style parser for command line options. C-style parser for command line options
* logging: logging --- Logging facility for Python. Logging facility for Python
* logging.config: logging config --- Logging configuration. Logging configuration
* logging.handlers: logging handlers --- Logging handlers. Logging handlers
* getpass: getpass --- Portable password input. Portable password input
* curses: curses --- Terminal handling for character-cell displays. Terminal handling for character-cell displays
* curses.textpad: curses textpad --- Text input widget for curses programs. Text input widget for curses programs
* curses.ascii: curses ascii --- Utilities for ASCII characters. Utilities for ASCII characters
* curses.panel: curses panel --- A panel stack extension for curses. A panel stack extension for curses
* platform: platform --- Access to underlying platform's identifying data. Access to underlying platform’s identifying data
* errno: errno --- Standard errno system symbols. Standard errno system symbols
* ctypes: ctypes --- A foreign function library for Python. A foreign function library for Python


File: python.info,  Node: os --- Miscellaneous operating system interfaces,  Next: io --- Core tools for working with streams,  Up: Generic Operating System Services

5.16.1 ‘os’ — Miscellaneous operating system interfaces
-------------------------------------------------------

`Source code:' Lib/os.py(1)

__________________________________________________________________

This module provides a portable way of using operating system dependent
functionality.  If you just want to read or write a file see *note
open(): 4f5, if you want to manipulate paths, see the *note os.path: c6.
module, and if you want to read all the lines in all the files on the
command line see the *note fileinput: 80. module.  For creating
temporary files and directories see the *note tempfile: 104. module, and
for high-level file and directory handling see the *note shutil: ea.
module.

Notes on the availability of these functions:

   * The design of all built-in operating system dependent modules of
     Python is such that as long as the same functionality is available,
     it uses the same interface; for example, the function
     ‘os.stat(path)’ returns stat information about `path' in the same
     format (which happens to have originated with the POSIX interface).

   * Extensions peculiar to a particular operating system are also
     available through the *note os: c5. module, but using them is of
     course a threat to portability.

   * All functions accepting path or file names accept both bytes and
     string objects, and result in an object of the same type, if a path
     or file name is returned.

   * On VxWorks, os.fork, os.execv and os.spawn*p* are not supported.

     備註: All functions in this module raise *note OSError: 1d4. (or
     subclasses thereof) in the case of invalid or inaccessible file
     names and paths, or other arguments that have the correct type, but
     are not accepted by the operating system.

 -- 例外: os.error

     An alias for the built-in *note OSError: 1d4. exception.

 -- Data: os.name

     The name of the operating system dependent module imported.  The
     following names have currently been registered: ‘'posix'’, ‘'nt'’,
     ‘'java'’.

     也參考
     ......

     *note sys.platform: 2b2. has a finer granularity.  *note
     os.uname(): a62. gives system-dependent version information.

     The *note platform: cf. 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.
* Process Parameters::
* File Object Creation::
* File Descriptor Operations::
* Files and Directories::
* Process Management::
* Interface to the scheduler::
* Miscellaneous System Information::
* Random numbers: Random numbers<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/os.py


File: python.info,  Node: File Names Command Line Arguments and Environment Variables,  Next: Process Parameters,  Up: os --- Miscellaneous operating system interfaces

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 file system encoding to perform this
conversion (see *note sys.getfilesystemencoding(): 4fb.).

3.1 版更變: On some systems, conversion using the file system encoding
may fail.  In this case, Python uses the *note surrogateescape encoding
error handler: 184d, which means that undecodable bytes are replaced by
a Unicode character U+DCxx on decoding, and these are again translated
to the original byte on encoding.

The file system encoding must guarantee to successfully decode all bytes
below 128.  If the file system encoding fails to provide this guarantee,
API functions may raise UnicodeErrors.


File: python.info,  Node: Process Parameters,  Next: File Object Creation,  Prev: File Names Command Line Arguments and Environment Variables,  Up: os --- Miscellaneous operating system interfaces

5.16.1.2 Process Parameters
...........................

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 Availability: 1364.: Unix.

 -- Data: os.environ

     A *note mapping: b3e. object representing the string 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: c5. 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 ‘os.environ’, except for changes made by modifying
     ‘os.environ’ directly.

     If the platform supports the *note putenv(): 1eeb. function, this
     mapping may be used to modify the environment as well as query the
     environment.  *note putenv(): 1eeb. will be called automatically
     when the mapping is modified.

     On Unix, keys and values use *note sys.getfilesystemencoding():
     4fb. and ‘'surrogateescape'’ error handler.  Use *note environb:
     b99. if you would like to use a different encoding.

          備註: Calling *note putenv(): 1eeb. directly does not change
          ‘os.environ’, so it’s better to modify ‘os.environ’.

          備註: On some platforms, including FreeBSD and Mac OS X,
          setting ‘environ’ may cause memory leaks.  Refer to the system
          documentation for ‘putenv()’.

     If *note putenv(): 1eeb. is not provided, a modified copy of this
     mapping may be passed to the appropriate process-creation functions
     to cause child processes to use a modified environment.

     If the platform supports the *note unsetenv(): d48. function, you
     can delete items in this mapping to unset environment variables.
     *note unsetenv(): d48. will be called automatically when an item is
     deleted from ‘os.environ’, and when one of the ‘pop()’ or ‘clear()’
     methods is called.

 -- Data: os.environb

     Bytes version of *note environ: b3c.: a *note mapping: b3e. object
     representing the environment as byte strings.  *note environ: b3c.
     and *note environb: b99. are synchronized (modify *note environb:
     b99. updates *note environ: b3c, and vice versa).

     *note environb: b99. is only available if *note
     supports_bytes_environ: b97. is ‘True’.

     3.2 版新加入.

 -- 函式: os.chdir (path)

 -- 函式: os.fchdir (fd)

 -- 函式: os.getcwd ()

     These functions are described in *note Files and Directories: 1eec.

 -- 函式: os.fsencode (filename)

     Encode *note path-like: 36f. `filename' to the filesystem encoding
     with ‘'surrogateescape'’ error handler, or ‘'strict'’ on Windows;
     return *note bytes: 336. unchanged.

     *note fsdecode(): 4f3. is the reverse function.

     3.2 版新加入.

     3.6 版更變: Support added to accept objects implementing the *note
     os.PathLike: 4f0. interface.

 -- 函式: os.fsdecode (filename)

     Decode the *note path-like: 36f. `filename' from the filesystem
     encoding with ‘'surrogateescape'’ error handler, or ‘'strict'’ on
     Windows; return *note str: 335. unchanged.

     *note fsencode(): 4f4. is the reverse function.

     3.2 版新加入.

     3.6 版更變: Support added to accept objects implementing the *note
     os.PathLike: 4f0. interface.

 -- 函式: os.fspath (path)

     Return the file system representation of the path.

     If *note str: 335. or *note bytes: 336. is passed in, it is
     returned unchanged.  Otherwise *note __fspath__(): 4f1. is called
     and its value is returned as long as it is a *note str: 335. or
     *note bytes: 336. object.  In all other cases, *note TypeError:
     193. is raised.

     3.6 版新加入.

 -- 類別: os.PathLike

     An *note abstract base class: b38. for objects representing a file
     system path, e.g.  *note pathlib.PurePath: 1046.

     3.6 版新加入.

      -- 成員函式: abstractmethod __fspath__ ()

          Return the file system path representation of the object.

          The method should only return a *note str: 335. or *note
          bytes: 336. object, with the preference being for *note str:
          335.

 -- 函式: os.getenv (key, default=None)

     Return the value of the environment variable `key' if it exists, or
     `default' if it doesn’t.  `key', `default' and the result are str.

     On Unix, keys and values are decoded with *note
     sys.getfilesystemencoding(): 4fb. and ‘'surrogateescape'’ error
     handler.  Use *note os.getenvb(): b98. if you would like to use a
     different encoding.

     *note Availability: 1364.: most flavors of Unix, Windows.

 -- 函式: os.getenvb (key, default=None)

     Return the value of the environment variable `key' if it exists, or
     `default' if it doesn’t.  `key', `default' and the result are
     bytes.

     *note getenvb(): b98. is only available if *note
     supports_bytes_environ: b97. is ‘True’.

     *note Availability: 1364.: most flavors of 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: b3c. 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 Availability: 1364.: Unix.

 -- 函式: os.geteuid ()

     Return the current process’s effective user id.

     *note Availability: 1364.: Unix.

 -- 函式: os.getgid ()

     Return the real group id of the current process.

     *note Availability: 1364.: Unix.

 -- 函式: 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'.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: os.getgroups ()

     Return list of supplemental group ids associated with the current
     process.

     *note Availability: 1364.: Unix.

          備註: On Mac OS X, *note getgroups(): 1ef2. behavior differs
          somewhat from other Unix platforms.  If the Python interpreter
          was built with a deployment target of ‘10.5’ or earlier, *note
          getgroups(): 1ef2. 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(): 1ef3. if suitably
          privileged.  If built with a deployment target greater than
          ‘10.5’, *note getgroups(): 1ef2. 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(): 1ef3, and its length is not limited to 16.  The
          deployment target value, ‘MACOSX_DEPLOYMENT_TARGET’, can be
          obtained with *note sysconfig.get_config_var(): 969.

 -- 函式: 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(): 1ef5. 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: 1364.: Unix, Windows.

 -- 函式: 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 Availability: 1364.: Unix.

 -- 函式: os.getpgrp ()

     Return the id of the current process group.

     *note Availability: 1364.: Unix.

 -- 函式: os.getpid ()

     Return the current process id.

 -- 函式: 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: 1364.: Unix, Windows.

     3.2 版更變: Added support for Windows.

 -- 函式: os.getpriority (which, who)

     Get program scheduling priority.  The value `which' is one of *note
     PRIO_PROCESS: 1efa, *note PRIO_PGRP: 1efb, or *note PRIO_USER:
     1efc, and `who' is interpreted relative to `which' (a process
     identifier for *note PRIO_PROCESS: 1efa, process group identifier
     for *note PRIO_PGRP: 1efb, and a user ID for *note PRIO_USER:
     1efc.).  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 Availability: 1364.: Unix.

     3.3 版新加入.

 -- Data: os.PRIO_PROCESS
 -- Data: os.PRIO_PGRP
 -- Data: os.PRIO_USER

     Parameters for the *note getpriority(): a4b. and *note
     setpriority(): a4c. functions.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: os.getresuid ()

     Return a tuple (ruid, euid, suid) denoting the current process’s
     real, effective, and saved user ids.

     *note Availability: 1364.: Unix.

     3.2 版新加入.

 -- 函式: os.getresgid ()

     Return a tuple (rgid, egid, sgid) denoting the current process’s
     real, effective, and saved group ids.

     *note Availability: 1364.: Unix.

     3.2 版新加入.

 -- 函式: os.getuid ()

     Return the current process’s real user id.

     *note Availability: 1364.: Unix.

 -- 函式: 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 Availability: 1364.: Unix.

     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(): dc6, *note popen(): 2aa. or *note fork(): 966.
     and *note execv(): 1efe.

     *note Availability: 1364.: most flavors of Unix, Windows.

          備註: On some platforms, including FreeBSD and Mac OS X,
          setting ‘environ’ may cause memory leaks.  Refer to the system
          documentation for putenv.

     When *note putenv(): 1eeb. is supported, assignments to items in
     ‘os.environ’ are automatically translated into corresponding calls
     to *note putenv(): 1eeb.; however, calls to *note putenv(): 1eeb.
     don’t update ‘os.environ’, so it is actually preferable to assign
     to items of ‘os.environ’.

     Raises an *note auditing event: e96. ‘os.putenv’ with arguments
     ‘key’, ‘value’.

 -- 函式: os.setegid (egid)

     Set the current process’s effective group id.

     *note Availability: 1364.: Unix.

 -- 函式: os.seteuid (euid)

     Set the current process’s effective user id.

     *note Availability: 1364.: Unix.

 -- 函式: os.setgid (gid)

     Set the current process’ group id.

     *note Availability: 1364.: Unix.

 -- 函式: 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 Availability: 1364.: Unix.

          備註: On Mac OS X, the length of `groups' may not exceed the
          system-defined maximum number of effective group ids,
          typically 16.  See the documentation for *note getgroups():
          1ef2. for cases where it may not return the same group list
          set by calling setgroups().

 -- 函式: 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 Availability: 1364.: Unix.

 -- 函式: 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 Availability: 1364.: Unix.

 -- 函式: os.setpriority (which, who, priority)

     Set program scheduling priority.  The value `which' is one of *note
     PRIO_PROCESS: 1efa, *note PRIO_PGRP: 1efb, or *note PRIO_USER:
     1efc, and `who' is interpreted relative to `which' (a process
     identifier for *note PRIO_PROCESS: 1efa, process group identifier
     for *note PRIO_PGRP: 1efb, and a user ID for *note PRIO_USER:
     1efc.).  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 Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: os.setregid (rgid, egid)

     Set the current process’s real and effective group ids.

     *note Availability: 1364.: Unix.

 -- 函式: os.setresgid (rgid, egid, sgid)

     Set the current process’s real, effective, and saved group ids.

     *note Availability: 1364.: Unix.

     3.2 版新加入.

 -- 函式: os.setresuid (ruid, euid, suid)

     Set the current process’s real, effective, and saved user ids.

     *note Availability: 1364.: Unix.

     3.2 版新加入.

 -- 函式: os.setreuid (ruid, euid)

     Set the current process’s real and effective user ids.

     *note Availability: 1364.: Unix.

 -- 函式: os.getsid (pid)

     Call the system call ‘getsid()’.  See the Unix manual for the
     semantics.

     *note Availability: 1364.: Unix.

 -- 函式: os.setsid ()

     Call the system call ‘setsid()’.  See the Unix manual for the
     semantics.

     *note Availability: 1364.: Unix.

 -- 函式: os.setuid (uid)

     Set the current process’s user id.

     *note Availability: 1364.: Unix.

 -- 函式: 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: 1fc. is raised.

 -- Data: 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.

 -- 函式: os.uname ()

     Returns information identifying the current operating system.  The
     return value is an object with five attributes:

        * ‘sysname’ - operating system name

        * ‘nodename’ - name of machine on network
          (implementation-defined)

        * ‘release’ - operating system release

        * ‘version’ - operating system 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(): 1f0a. or even
     ‘socket.gethostbyaddr(socket.gethostname())’.

     *note Availability: 1364.: recent flavors of 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(): dc6, *note popen(): 2aa. or *note fork(): 966. and
     *note execv(): 1efe.

     When *note unsetenv(): d48. is supported, deletion of items in
     ‘os.environ’ is automatically translated into a corresponding call
     to *note unsetenv(): d48.; however, calls to *note unsetenv(): d48.
     don’t update ‘os.environ’, so it is actually preferable to delete
     items of ‘os.environ’.

     Raises an *note auditing event: e96. ‘os.unsetenv’ with argument
     ‘key’.

     *note Availability: 1364.: most flavors of Unix.


File: python.info,  Node: File Object Creation,  Next: File Descriptor Operations,  Prev: Process Parameters,  Up: os --- Miscellaneous operating system interfaces

5.16.1.3 File Object Creation
.............................

These functions create new *note file objects: b47.  (See also *note
open(): 66a. 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(): 4f5. built-in function and
     accepts the same arguments.  The only difference is that the first
     argument of *note fdopen(): 1436. must always be an integer.


File: python.info,  Node: File Descriptor Operations,  Next: Files and Directories,  Prev: File Object Creation,  Up: os --- Miscellaneous operating system interfaces

5.16.1.4 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(): 1f0f. method can be used to obtain the file
descriptor associated with a *note file object: b47. 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():
          66a. or *note pipe(): 1f10.  To close a "file object" returned
          by the built-in function *note open(): 4f5. or by *note
          popen(): 2aa. or *note fdopen(): 1436, use its *note close():
          1013. 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'.  The files pointed
     by `src' and `dst' must reside in the same filesystem, otherwise an
     *note OSError: 1d4. is raised with *note errno: 170a. set to *note
     errno.EXDEV: 1f13.

     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.

     The return value is the amount of bytes copied.  This could be less
     than the amount requested.

     *note Availability: 1364.: Linux kernel >= 4.5 or 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:
     158.

 -- 函式: os.dup (fd)

     Return a duplicate of file descriptor `fd'.  The new file
     descriptor is *note non-inheritable: 7ff.

     On Windows, when duplicating a standard stream (0: stdin, 1:
     stdout, 2: stderr), the new file descriptor is *note inheritable:
     7ff.

     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: 7ff. by default or non-inheritable if `inheritable' is
     ‘False’.

     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(): a38. for possible values of `mode'.
     As of Python 3.3, this is equivalent to ‘os.chmod(fd, mode)’.

     Raises an *note auditing event: e96. ‘os.chmod’ with arguments
     ‘path’, ‘mode’, ‘dir_fd’.

     *note Availability: 1364.: Unix.

 -- 函式: 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(): a39.  As of Python 3.3, this is
     equivalent to ‘os.chown(fd, uid, gid)’.

     Raises an *note auditing event: e96. ‘os.chown’ with arguments
     ‘path’, ‘uid’, ‘gid’, ‘dir_fd’.

     *note Availability: 1364.: Unix.

 -- 函式: os.fdatasync (fd)

     Force write of file with filedescriptor `fd' to disk.  Does not
     force update of metadata.

     *note Availability: 1364.: 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: 1fc. 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: 1d4. is raised with *note errno.EINVAL: fce. for the error
     number.

     As of Python 3.3, this is equivalent to ‘os.pathconf(fd, name)’.

     *note Availability: 1364.: Unix.

 -- 函式: os.fstat (fd)

     Get the status of the file descriptor `fd'.  Return a *note
     stat_result: 108f. object.

     As of Python 3.3, this is equivalent to ‘os.stat(fd)’.

     也參考
     ......

     The *note stat(): 1f2. function.

 -- 函式: os.fstatvfs (fd)

     Return information about the filesystem containing the file
     associated with file descriptor `fd', like *note statvfs(): a48.
     As of Python 3.3, this is equivalent to ‘os.statvfs(fd)’.

     *note Availability: 1364.: 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: b47.
     `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 Availability: 1364.: 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)’.

     Raises an *note auditing event: e96. ‘os.truncate’ with arguments
     ‘fd’, ‘length’.

     *note Availability: 1364.: Unix, Windows.

     3.5 版更變: Added support for Windows

 -- 函式: os.get_blocking (fd)

     Get the blocking mode of the file descriptor: ‘False’ if the *note
     O_NONBLOCK: 728. flag is set, ‘True’ if the flag is cleared.

     See also *note set_blocking(): 727. and *note
     socket.socket.setblocking(): 1f16.

     *note Availability: 1364.: Unix.

     3.5 版新加入.

 -- 函式: 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: 1f18, *note F_TLOCK: 1f19, *note
     F_ULOCK: 1f1a. or *note F_TEST: 1f1b.  `len' specifies the section
     of the file to lock.

     Raises an *note auditing event: e96. ‘os.lockf’ with arguments
     ‘fd’, ‘cmd’, ‘len’.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- Data: os.F_LOCK
 -- Data: os.F_TLOCK
 -- Data: os.F_ULOCK
 -- Data: os.F_TEST

     Flags that specify what action *note lockf(): a5f. will take.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: os.lseek (fd, pos, how)

     Set the current position of file descriptor `fd' to position `pos',
     modified by `how': *note SEEK_SET: d99. or ‘0’ to set the position
     relative to the beginning of the file; *note SEEK_CUR: d9a. or ‘1’
     to set it relative to the current position; *note SEEK_END: d9b. or
     ‘2’ to set it relative to the end of the file.  Return the new
     cursor position in bytes, starting from the beginning.

 -- Data: os.SEEK_SET
 -- Data: os.SEEK_CUR
 -- Data: os.SEEK_END

     Parameters to the *note lseek(): a63. function.  Their values are
     0, 1, and 2, respectively.

     3.3 版新加入: Some operating systems could support additional
     values, like ‘os.SEEK_HOLE’ or ‘os.SEEK_DATA’.

 -- 函式: 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: 7ff.

     For a description of the flag and mode values, see the C run-time
     documentation; flag constants (like *note O_RDONLY: 1f1c. and *note
     O_WRONLY: 1f1d.) are defined in the *note os: c5. module.  In
     particular, on Windows adding *note O_BINARY: 1f1e. is needed to
     open files in binary mode.

     This function can support *note paths relative to directory
     descriptors: a34. with the `dir_fd' parameter.

     Raises an *note auditing event: e96. ‘open’ with arguments ‘path’,
     ‘mode’, ‘flags’.

     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(): 4f5, which
          returns a *note file object: b47. with ‘read()’ and ‘write()’
          methods (and many more).  To wrap a file descriptor in a file
          object, use *note fdopen(): 1436.

     3.3 版新加入: The `dir_fd' argument.

     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: 65e.
     exception (see PEP 475(1) for the rationale).

     3.6 版更變: Accepts a *note path-like object: 36f.

The following constants are options for the `flags' parameter to the
*note open(): 66a. 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)’ manual
page on Unix or the MSDN(2) on Windows.

 -- Data: os.O_RDONLY
 -- Data: os.O_WRONLY
 -- Data: os.O_RDWR
 -- Data: os.O_APPEND
 -- Data: os.O_CREAT
 -- Data: os.O_EXCL
 -- Data: os.O_TRUNC

     The above constants are available on Unix and Windows.

 -- Data: os.O_DSYNC
 -- Data: os.O_RSYNC
 -- Data: os.O_SYNC
 -- Data: os.O_NDELAY
 -- Data: os.O_NONBLOCK
 -- Data: os.O_NOCTTY
 -- Data: os.O_CLOEXEC

     The above constants are only available on Unix.

     3.3 版更變: Add *note O_CLOEXEC: 9c8. constant.

 -- Data: os.O_BINARY
 -- Data: os.O_NOINHERIT
 -- Data: os.O_SHORT_LIVED
 -- Data: os.O_TEMPORARY
 -- Data: os.O_RANDOM
 -- Data: os.O_SEQUENTIAL
 -- Data: os.O_TEXT

     The above constants are only available on Windows.

 -- Data: os.O_ASYNC
 -- Data: os.O_DIRECT
 -- Data: os.O_DIRECTORY
 -- Data: os.O_NOFOLLOW
 -- Data: os.O_NOATIME
 -- Data: os.O_PATH
 -- Data: os.O_TMPFILE
 -- Data: os.O_SHLOCK
 -- Data: 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: 888. on systems that support it.  Add
     *note O_TMPFILE: 889, 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: 7ff.  For a (slightly)
     more portable approach, use the *note pty: d6. module.

     *note Availability: 1364.: some flavors of Unix.

     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: 7ff.

     *note Availability: 1364.: 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: 728, *note O_CLOEXEC: 9c8.  Return a pair of file
     descriptors ‘(r, w)’ usable for reading and writing, respectively.

     *note Availability: 1364.: some flavors of Unix.

     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 Availability: 1364.: 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: 1f34, *note POSIX_FADV_SEQUENTIAL: 1f35, *note
     POSIX_FADV_RANDOM: 1f36, *note POSIX_FADV_NOREUSE: 1f37, *note
     POSIX_FADV_WILLNEED: 1f38. or *note POSIX_FADV_DONTNEED: 1f39.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- Data: os.POSIX_FADV_NORMAL
 -- Data: os.POSIX_FADV_SEQUENTIAL
 -- Data: os.POSIX_FADV_RANDOM
 -- Data: os.POSIX_FADV_NOREUSE
 -- Data: os.POSIX_FADV_WILLNEED
 -- Data: os.POSIX_FADV_DONTNEED

     Flags that can be used in `advice' in *note posix_fadvise(): 66b.
     that specify the access pattern that is likely to be used.

     *note Availability: 1364.: 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 Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: os.preadv (fd, buffers, offset, flags=0)

     Read from a file descriptor `fd' at a position of `offset' into
     mutable *note bytes-like objects: 5ed. `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: 1f3a.

        - *note RWF_NOWAIT: 1f3b.

     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(): 1f3c. value
     ‘'SC_IOV_MAX'’) on the number of buffers that can be used.

     Combine the functionality of *note os.readv(): 3bd. and *note
     os.pread(): 3be.

     *note Availability: 1364.: Linux 2.6.30 and newer, FreeBSD 6.0 and
     newer, OpenBSD 2.7 and newer.  Using flags requires Linux 4.6 or
     newer.

     3.7 版新加入.

 -- Data: 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: 1f3d.

     *note Availability: 1364.: Linux 4.14 and newer.

     3.7 版新加入.

 -- Data: 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: 1f2f. flag.

     *note Availability: 1364.: Linux 4.6 and newer.

     3.7 版新加入.

 -- 函式: 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 Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: os.pwritev (fd, buffers, offset, flags=0)

     Write the `buffers' contents to file descriptor `fd' at a offset
     `offset', leaving the file offset unchanged.  `buffers' must be a
     sequence of *note bytes-like objects: 5ed.  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: 1f3e.

        - *note RWF_SYNC: 1f3f.

     Return the total number of bytes actually written.

     The operating system may set a limit (*note sysconf(): 1f3c. value
     ‘'SC_IOV_MAX'’) on the number of buffers that can be used.

     Combine the functionality of *note os.writev(): 3c0. and *note
     os.pwrite(): 3c1.

     *note Availability: 1364.: Linux 2.6.30 and newer, FreeBSD 6.0 and
     newer, OpenBSD 2.7 and newer.  Using flags requires Linux 4.7 or
     newer.

     3.7 版新加入.

 -- Data: os.RWF_DSYNC

     Provide a per-write equivalent of the *note O_DSYNC: 1f23.
     ‘open(2)’ flag.  This flag effect applies only to the data range
     written by the system call.

     *note Availability: 1364.: Linux 4.7 and newer.

     3.7 版新加入.

 -- Data: os.RWF_SYNC

     Provide a per-write equivalent of the *note O_SYNC: 1f25. ‘open(2)’
     flag.  This flag effect applies only to the data range written by
     the system call.

     *note Availability: 1364.: Linux 4.7 and newer.

     3.7 版新加入.

 -- 函式: 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():
          66a. or *note pipe(): 1f10.  To read a "file object" returned
          by the built-in function *note open(): 4f5. or by *note
          popen(): 2aa. or *note fdopen(): 1436, or *note sys.stdin:
          312, 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: 65e.
     exception (see PEP 475(3) for the rationale).

 -- 函式: os.sendfile (out, in, offset, count)

 -- 函式: os.sendfile (out, in, offset, count[, headers][, trailers],
          flags=0)

     Copy `count' bytes from file descriptor `in' to file descriptor
     `out' 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(): 35e.

     On Linux, if `offset' is given as ‘None’, the bytes are read from
     the current position of `in' and the position of `in' is updated.

     The second case may be used on Mac OS X and FreeBSD where `headers'
     and `trailers' are arbitrary sequences of buffers that are written
     before and after the data from `in' is written.  It returns the
     same as the first case.

     On Mac OS X and FreeBSD, a value of 0 for `count' specifies to send
     until the end of `in' is reached.

     All platforms support sockets as `out' 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 Availability: 1364.: Unix.

          備註: For a higher-level wrapper of *note sendfile(): 35e, see
          *note socket.socket.sendfile(): 74f.

     3.3 版新加入.

 -- 函式: os.set_blocking (fd, blocking)

     Set the blocking mode of the specified file descriptor.  Set the
     *note O_NONBLOCK: 728. flag if blocking is ‘False’, clear the flag
     otherwise.

     See also *note get_blocking(): 726. and *note
     socket.socket.setblocking(): 1f16.

     *note Availability: 1364.: Unix.

     3.5 版新加入.

 -- Data: os.SF_NODISKIO
 -- Data: os.SF_MNOWAIT
 -- Data: os.SF_SYNC

     Parameters to the *note sendfile(): 35e. function, if the
     implementation supports them.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: os.readv (fd, buffers)

     Read from a file descriptor `fd' into a number of mutable *note
     bytes-like objects: 5ed. `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(): 1f3c. value
     ‘'SC_IOV_MAX'’) on the number of buffers that can be used.

     *note Availability: 1364.: 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(): 66a.).

     *note Availability: 1364.: Unix.

 -- 函式: 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(): 66a.) to
     `pg'.

     *note Availability: 1364.: Unix.

 -- 函式: 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 Availability: 1364.: Unix.

 -- 函式: 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():
          66a. or *note pipe(): 1f10.  To write a "file object" returned
          by the built-in function *note open(): 4f5. or by *note
          popen(): 2aa. or *note fdopen(): 1436, or *note sys.stdout:
          313. or *note sys.stderr: 314, 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: 65e.
     exception (see PEP 475(4) 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: 5ed.  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(): 1f3c. value
     ‘'SC_IOV_MAX'’) on the number of buffers that can be used.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

* Menu:

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

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0475

   (2) https://msdn.microsoft.com/en-us/library/z0kc8e3z.aspx

   (3) https://www.python.org/dev/peps/pep-0475

   (4) https://www.python.org/dev/peps/pep-0475


File: python.info,  Node: Querying the size of a terminal,  Next: Inheritance of File Descriptors,  Up: File Descriptor Operations

5.16.1.5 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: 1ca3.

     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: 1d4. is raised.

     *note shutil.get_terminal_size(): a4f. is the high-level function
     which should normally be used, ‘os.get_terminal_size’ is the
     low-level implementation.

     *note Availability: 1364.: 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.6 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*: 1f4b. functions, all inheritable handles and all inheritable
file descriptors are inherited.  Using the *note subprocess: fa. module,
all file descriptors except standard streams are closed, and inheritable
handles are only inherited if the `close_fds' parameter is ‘False’.

 -- 函式: 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 Availability: 1364.: Windows.

 -- 函式: os.set_handle_inheritable (handle, inheritable)

     Set the "inheritable" flag of the specified handle.

     *note Availability: 1364.: Windows.


File: python.info,  Node: Files and Directories,  Next: Process Management,  Prev: File Descriptor Operations,  Up: os --- Miscellaneous operating system interfaces

5.16.1.7 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: c5. 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: a49.  If this functionality is unavailable, using
     it will raise a *note NotImplementedError: 613.

     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: a43.  If
     it’s unavailable, using it will raise a *note NotImplementedError:
     613.

   * `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: 1c8e.  If it’s unavailable, using it
     will raise a *note NotImplementedError: 613.

 -- 函式: 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:
     1f4d. to test the existence of `path', or it can be the inclusive
     OR of one or more of *note R_OK: 1f4e, *note W_OK: 1f4f, and *note
     X_OK: 1f50. to test permissions.  Return *note True: 49e. if access
     is allowed, *note False: 38d. if not.  See the Unix man page
     ‘access(2)’ for more information.

     This function can support specifying *note paths relative to
     directory descriptors: a34. and *note not following symlinks: a35.

     If `effective_ids' is ‘True’, *note access(): a36. 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: a4a.  If it is unavailable, using it
     will raise a *note NotImplementedError: 613.

          備註: Using *note access(): a36. to check if a user is
          authorized to e.g.  open a file before actually doing so using
          *note open(): 4f5. 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: 1f51. 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(): a36.
          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 版更變: Added the `dir_fd', `effective_ids', and
     `follow_symlinks' parameters.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- Data: os.F_OK
 -- Data: os.R_OK
 -- Data: os.W_OK
 -- Data: os.X_OK

     Values to pass as the `mode' parameter of *note access(): a36. 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: 3ba.
     The descriptor must refer to an opened directory, not an open file.

     This function can raise *note OSError: 1d4. and subclasses such as
     *note FileNotFoundError: 7c5, *note PermissionError: 604, and *note
     NotADirectoryError: 99f.

     Raises an *note auditing event: e96. ‘os.chdir’ with argument
     ‘path’.

     3.3 版新加入: Added support for specifying `path' as a file
     descriptor on some platforms.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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: f5. module):

        * *note stat.UF_NODUMP: 1c33.

        * *note stat.UF_IMMUTABLE: 1c34.

        * *note stat.UF_APPEND: 1c35.

        * *note stat.UF_OPAQUE: 1c36.

        * *note stat.UF_NOUNLINK: 1c37.

        * *note stat.UF_COMPRESSED: 1c38.

        * *note stat.UF_HIDDEN: 1c39.

        * *note stat.SF_ARCHIVED: 1c3a.

        * *note stat.SF_IMMUTABLE: 1c3b.

        * *note stat.SF_APPEND: 1c3c.

        * *note stat.SF_NOUNLINK: 1c3d.

        * *note stat.SF_SNAPSHOT: 1c3e.

     This function can support *note not following symlinks: a35.

     Raises an *note auditing event: e96. ‘os.chflags’ with arguments
     ‘path’, ‘flags’.

     *note Availability: 1364.: Unix.

     3.3 版新加入: The `follow_symlinks' argument.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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: f5.
     module) or bitwise ORed combinations of them:

        * *note stat.S_ISUID: 1c20.

        * *note stat.S_ISGID: 1c21.

        * *note stat.S_ENFMT: 1c23.

        * *note stat.S_ISVTX: 1c24.

        * *note stat.S_IREAD: 1c30.

        * *note stat.S_IWRITE: 1c31.

        * *note stat.S_IEXEC: 1c32.

        * *note stat.S_IRWXU: 1c25.

        * *note stat.S_IRUSR: 1c26.

        * *note stat.S_IWUSR: 1c27.

        * *note stat.S_IXUSR: 1c28.

        * *note stat.S_IRWXG: 1c29.

        * *note stat.S_IRGRP: 1c2a.

        * *note stat.S_IWGRP: 1c2b.

        * *note stat.S_IXGRP: 1c22.

        * *note stat.S_IRWXO: 1c2c.

        * *note stat.S_IROTH: 1c2d.

        * *note stat.S_IWOTH: 1c2e.

        * *note stat.S_IXOTH: 1c2f.

     This function can support *note specifying a file descriptor: 3ba,
     *note paths relative to directory descriptors: a34. and *note not
     following symlinks: a35.

          備註: Although Windows supports *note chmod(): a38, 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.

     Raises an *note auditing event: e96. ‘os.chmod’ with arguments
     ‘path’, ‘mode’, ‘dir_fd’.

     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: 36f.

 -- 函式: 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: 3ba,
     *note paths relative to directory descriptors: a34. and *note not
     following symlinks: a35.

     See *note shutil.chown(): a7b. for a higher-level function that
     accepts names in addition to numeric ids.

     Raises an *note auditing event: e96. ‘os.chown’ with arguments
     ‘path’, ‘uid’, ‘gid’, ‘dir_fd’.

     *note Availability: 1364.: Unix.

     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: 36f.

 -- 函式: os.chroot (path)

     Change the root directory of the current process to `path'.

     *note Availability: 1364.: Unix.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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)’.

     Raises an *note auditing event: e96. ‘os.chdir’ with argument
     ‘path’.

     *note Availability: 1364.: 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(1) 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(): a37, but do not follow symbolic links.  As of Python
     3.3, this is equivalent to ‘os.chflags(path, flags,
     follow_symlinks=False)’.

     Raises an *note auditing event: e96. ‘os.chflags’ with arguments
     ‘path’, ‘flags’.

     *note Availability: 1364.: Unix.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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(): a38. for possible values of `mode'.  As of
     Python 3.3, this is equivalent to ‘os.chmod(path, mode,
     follow_symlinks=False)’.

     Raises an *note auditing event: e96. ‘os.chmod’ with arguments
     ‘path’, ‘mode’, ‘dir_fd’.

     *note Availability: 1364.: Unix.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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)’.

     Raises an *note auditing event: e96. ‘os.chown’ with arguments
     ‘path’, ‘uid’, ‘gid’, ‘dir_fd’.

     *note Availability: 1364.: Unix.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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: a34, and *note not following symlinks: a35.

     Raises an *note auditing event: e96. ‘os.link’ with arguments
     ‘src’, ‘dst’, ‘src_dir_fd’, ‘dst_dir_fd’.

     *note Availability: 1364.: Unix, Windows.

     3.2 版更變: Added Windows support.

     3.3 版新加入: Added the `src_dir_fd', `dst_dir_fd', and
     `follow_symlinks' arguments.

     3.6 版更變: Accepts a *note path-like object: 36f. 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: 36f.  If `path' is of type
     ‘bytes’ (directly or indirectly through the *note PathLike: 4f0.
     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:
     3ba.; the file descriptor must refer to a directory.

     Raises an *note auditing event: e96. ‘os.listdir’ with argument
     ‘path’.

          備註: To encode ‘str’ filenames to ‘bytes’, use *note
          fsencode(): 4f4.

     也參考
     ......

     The *note scandir(): 260. 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: 36f.

 -- 函式: os.lstat (path, *, dir_fd=None)

     Perform the equivalent of an ‘lstat()’ system call on the given
     path.  Similar to *note stat(): 1f2, but does not follow symbolic
     links.  Return a *note stat_result: 108f. object.

     On platforms that do not support symbolic links, this is an alias
     for *note stat(): 1f2.

     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: a34.

     也參考
     ......

     The *note stat(): 1f2. function.

     3.2 版更變: Added support for Windows 6.0 (Vista) symbolic links.

     3.3 版更變: Added the `dir_fd' parameter.

     3.6 版更變: Accepts a *note path-like object: 36f.

     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(): 1f2.

 -- 函式: os.mkdir (path, mode=0o777, *, dir_fd=None)

     Create a directory named `path' with numeric mode `mode'.

     If the directory already exists, *note FileExistsError: 95d. 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(): a38.
     explicitly to set them.

     This function can also support *note paths relative to directory
     descriptors: a34.

     It is also possible to create temporary directories; see the *note
     tempfile: 104. module’s *note tempfile.mkdtemp(): 1c6e. function.

     Raises an *note auditing event: e96. ‘os.mkdir’ with arguments
     ‘path’, ‘mode’, ‘dir_fd’.

     3.3 版新加入: The `dir_fd' argument.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.makedirs (name, mode=0o777, exist_ok=False)

     Recursive directory creation function.  Like *note mkdir(): a3b,
     but makes all intermediate-level directories needed to contain the
     leaf directory.

     The `mode' parameter is passed to *note mkdir(): a3b. for creating
     the leaf directory; see *note the mkdir() description: 1f54. 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(): 3c2.  The file permission bits of
     existing parent directories are not changed.

     If `exist_ok' is ‘False’ (the default), an *note FileExistsError:
     95d. is raised if the target directory already exists.

          備註: *note makedirs(): 3c2. will become confused if the path
          elements to create include *note pardir: 1f55. (eg.  ".."  on
          UNIX systems).

     This function handles UNC paths correctly.

     Raises an *note auditing event: e96. ‘os.mkdir’ with arguments
     ‘path’, ‘mode’, ‘dir_fd’.

     3.2 版新加入: The `exist_ok' parameter.

     3.4.1 版更變: Before Python 3.4.1, if `exist_ok' was ‘True’ and the
     directory existed, *note makedirs(): 3c2. 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(2).

     3.6 版更變: Accepts a *note path-like object: 36f.

     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: a34.

     FIFOs are pipes that can be accessed like regular files.  FIFOs
     exist until they are deleted (for example with *note os.unlink():
     a41.).  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():
     668. doesn’t open the FIFO — it just creates the rendezvous point.

     *note Availability: 1364.: Unix.

     3.3 版新加入: The `dir_fd' argument.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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: f5.).  For
     ‘stat.S_IFCHR’ and ‘stat.S_IFBLK’, `device' defines the newly
     created device special file (probably using *note os.makedev():
     1f56.), otherwise it is ignored.

     This function can also support *note paths relative to directory
     descriptors: a34.

     *note Availability: 1364.: Unix.

     3.3 版新加入: The `dir_fd' argument.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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: 1fc. 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: 1d4. is raised with *note errno.EINVAL: fce. for the error
     number.

     This function can support *note specifying a file descriptor: 3ba.

     *note Availability: 1364.: Unix.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- Data: os.pathconf_names

     Dictionary mapping names accepted by *note pathconf(): a47. and
     *note fpathconf(): 1f15. 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 Availability: 1364.: 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: 4f0. 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: a34.

     When trying to resolve a path that may contain links, use *note
     realpath(): 200. to properly handle recursion and platform
     differences.

     *note Availability: 1364.: Unix, Windows.

     3.2 版更變: Added support for Windows 6.0 (Vista) symbolic links.

     3.3 版新加入: The `dir_fd' argument.

     3.6 版更變: Accepts a *note path-like object: 36f. on Unix.

     3.8 版更變: Accepts a *note path-like object: 36f. and a bytes
     object on Windows.

     3.8 版更變: 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 IsADirectoryError: 99e. is raised.  Use *note rmdir(): a3f.
     to remove directories.  If the file does not exist, a *note
     FileNotFoundError: 7c5. is raised.

     This function can support *note paths relative to directory
     descriptors: a34.

     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(): a41.

     Raises an *note auditing event: e96. ‘os.remove’ with arguments
     ‘path’, ‘dir_fd’.

     3.3 版新加入: The `dir_fd' argument.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.removedirs (name)

     Remove directories recursively.  Works like *note rmdir(): a3f.
     except that, if the leaf directory is successfully removed, *note
     removedirs(): 1f5a. 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: 1d4. if the
     leaf directory could not be successfully removed.

     Raises an *note auditing event: e96. ‘os.remove’ with arguments
     ‘path’, ‘dir_fd’.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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: 1d4. subclass in a
     number of cases:

     On Windows, if `dst' exists a *note FileExistsError: 95d. is always
     raised.

     On Unix, if `src' is a file and `dst' is a directory or vice-versa,
     an *note IsADirectoryError: 99e. or a *note NotADirectoryError:
     99f. 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: 1d4. is raised.  If both are
     files, `dst' it 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: a34.

     If you want cross-platform overwriting of the destination, use
     *note replace(): a3e.

     Raises an *note auditing event: e96. ‘os.rename’ with arguments
     ‘src’, ‘dst’, ‘src_dir_fd’, ‘dst_dir_fd’.

     3.3 版新加入: The `src_dir_fd' and `dst_dir_fd' arguments.

     3.6 版更變: Accepts a *note path-like object: 36f. for `src' and
     `dst'.

 -- 函式: os.renames (old, new)

     Recursive directory or file renaming function.  Works like *note
     rename(): a3d, 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(): 1f5a.

          備註: This function can fail with the new directory structure
          made if you lack permissions needed to remove the leaf
          directory or file.

     Raises an *note auditing event: e96. ‘os.rename’ with arguments
     ‘src’, ‘dst’, ‘src_dir_fd’, ‘dst_dir_fd’.

     3.6 版更變: Accepts a *note path-like object: 36f. 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
     directory, *note OSError: 1d4. 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: a34.

     Raises an *note auditing event: e96. ‘os.rename’ with arguments
     ‘src’, ‘dst’, ‘src_dir_fd’, ‘dst_dir_fd’.

     3.3 版新加入.

     3.6 版更變: Accepts a *note path-like object: 36f. 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, an *note FileNotFoundError: 7c5. or an *note
     OSError: 1d4. is raised respectively.  In order to remove whole
     directory trees, *note shutil.rmtree(): 21d. can be used.

     This function can support *note paths relative to directory
     descriptors: a34.

     Raises an *note auditing event: e96. ‘os.rmdir’ with arguments
     ‘path’, ‘dir_fd’.

     3.3 版新加入: The `dir_fd' parameter.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.scandir (path='.')

     Return an iterator of *note os.DirEntry: 4f6. 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(): 260. instead of *note listdir(): a46. can
     significantly increase the performance of code that also needs file
     type or file attribute information, because *note os.DirEntry: 4f6.
     objects expose this information if the operating system provides it
     when scanning a directory.  All *note os.DirEntry: 4f6. methods may
     perform a system call, but *note is_dir(): 1f5c. and *note
     is_file(): 65a. usually only require a system call for symbolic
     links; *note os.DirEntry.stat(): 1f5d. always requires a system
     call on Unix but only requires one for symbolic links on Windows.

     `path' may be a *note path-like object: 36f.  If `path' is of type
     ‘bytes’ (directly or indirectly through the *note PathLike: 4f0.
     interface), the type of the *note name: 1f5e. and *note path: 1f5f.
     attributes of each *note os.DirEntry: 4f6. will be ‘bytes’; in all
     other circumstances, they will be of type ‘str’.

     This function can also support *note specifying a file descriptor:
     3ba.; the file descriptor must refer to a directory.

     Raises an *note auditing event: e96. ‘os.scandir’ with argument
     ‘path’.

     The *note scandir(): 260. iterator supports the *note context
     manager: 56d. 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: 6ee. statement.

          3.6 版新加入.

     The following example shows a simple use of *note scandir(): 260.
     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(): 260. uses the
          system’s opendir()(3) and readdir()(4) functions.  On Windows,
          it uses the Win32 FindFirstFileW(5) and FindNextFileW(6)
          functions.

     3.5 版新加入.

     3.6 版新加入: Added support for the *note context manager: 56d.
     protocol and the *note close(): 56c. method.  If a *note scandir():
     260. iterator is neither exhausted nor explicitly closed a *note
     ResourceWarning: 4d5. will be emitted in its destructor.

     The function accepts a *note path-like object: 36f.

     3.7 版更變: Added support for *note file descriptors: 3ba. on Unix.

 -- 類別: os.DirEntry

     Object yielded by *note scandir(): 260. to expose the file path and
     other file attributes of a directory entry.

     *note scandir(): 260. 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(): 260, 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: 1d4.  If you need very
     fine-grained control over errors, you can catch *note OSError: 1d4.
     when calling one of the ‘os.DirEntry’ methods and handle as
     appropriate.

     To be directly usable as a *note path-like object: 36f,
     ‘os.DirEntry’ implements the *note PathLike: 4f0. interface.

     Attributes and methods on a ‘os.DirEntry’ instance are as follows:

      -- 屬性: name

          The entry’s base filename, relative to the *note scandir():
          260. `path' argument.

          The *note name: 1ee5. attribute will be ‘bytes’ if the *note
          scandir(): 260. `path' argument is of type ‘bytes’ and ‘str’
          otherwise.  Use *note fsdecode(): 4f3. 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(): 260. `path' argument.  The path is
          only absolute if the *note scandir(): 260. `path' argument was
          absolute.  If the *note scandir(): 260. `path' argument was a
          *note file descriptor: 3ba, the *note path: c6. attribute is
          the same as the *note name: 1ee5. attribute.

          The *note path: c6. attribute will be ‘bytes’ if the *note
          scandir(): 260. `path' argument is of type ‘bytes’ and ‘str’
          otherwise.  Use *note fsdecode(): 4f3. 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(): 1f2. along with *note stat.S_ISDIR(): 1c07.
          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: 1d4, such as *note
          PermissionError: 604, but *note FileNotFoundError: 7c5. 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(): 1f5c.

      -- 成員函式: 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(): 1f5. 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: 1d4, such as *note
          PermissionError: 604, but *note FileNotFoundError: 7c5. is
          caught and not raised.

      -- 成員函式: stat (*, follow_symlinks=True)

          Return a *note stat_result: 108f. 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: 108f. are always set to zero.  Call
          *note os.stat(): 1f2. 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(): 1f2. 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: 202.  In
     particular, the ‘name’ attribute has the same meaning, as do the
     ‘is_dir()’, ‘is_file()’, ‘is_symlink()’ and ‘stat()’ methods.

     3.5 版新加入.

     3.6 版更變: Added support for the *note PathLike: 4f0. interface.
     Added support for *note bytes: 336. paths on Windows.

 -- 函式: 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: 4f0. interface – or as an open file
     descriptor.  Return a *note stat_result: 108f. object.

     This function normally follows symlinks; to stat a symlink add the
     argument ‘follow_symlinks=False’, or use *note lstat(): 1f3.

     This function can support *note specifying a file descriptor: 3ba.
     and *note not following symlinks: a35.

     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(): 200.
     function to resolve the path name as far as possible and call *note
     lstat(): 1f3. on the result.  This does not apply to dangling
     symlinks or junction points, which will raise the usual exceptions.

     Example:

          >>> 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(): 664. and *note lstat(): 1f3. functions.

     3.3 版新加入: Added the `dir_fd' and `follow_symlinks' arguments,
     specifying a file descriptor instead of a path.

     3.6 版更變: Accepts a *note path-like object: 36f.

     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():
     1f2, *note os.fstat(): 664. and *note os.lstat(): 1f3.

     Attributes:

      -- 屬性: 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(7) 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

          Platform dependent:

             * the time of most recent metadata change on Unix,

             * the time of creation on Windows, expressed in seconds.

      -- 屬性: st_atime_ns

          Time of most recent access expressed in nanoseconds as an
          integer.

      -- 屬性: st_mtime_ns

          Time of most recent content modification expressed in
          nanoseconds as an integer.

      -- 屬性: st_ctime_ns

          Platform dependent:

             * the time of most recent metadata change on Unix,

             * the time of creation on Windows, expressed in nanoseconds
               as an integer.

          備註: The exact meaning and resolution of the *note st_atime:
          1f69, *note st_mtime: 1d5b, and *note st_ctime: 1f6a.
          attributes depend on the operating system and the file system.
          For example, on Windows systems using the FAT or FAT32 file
          systems, *note st_mtime: 1d5b. has 2-second resolution, and
          *note st_atime: 1f69. has only 1-day resolution.  See your
          operating system documentation for details.

          Similarly, although *note st_atime_ns: 1f6b, *note
          st_mtime_ns: 1f6c, and *note st_ctime_ns: 1f6d. 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: 1f69, *note st_mtime: 1d5b, and *note st_ctime:
          1f6a. 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: 1f6b, *note st_mtime_ns: 1f6c, and
          *note st_ctime_ns: 1f6d.

     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: 1f68./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.

      -- 屬性: st_birthtime

          Time of file creation.

     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 Mac OS 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_*’
          constants in the *note stat: f5. module.

      -- 屬性: st_reparse_tag

          When *note st_file_attributes: 725. has the
          ‘FILE_ATTRIBUTE_REPARSE_POINT’ set, this field contains the
          tag identifying the type of reparse point.  See the
          ‘IO_REPARSE_TAG_*’ constants in the *note stat: f5. module.

     The standard module *note stat: f5. 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: 108f. 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: 1f62, *note st_ino: 1f63, *note st_dev: 1f64,
     *note st_nlink: 1f65, *note st_uid: 1f66, *note st_gid: 1f67, *note
     st_size: 1f68, *note st_atime: 1f69, *note st_mtime: 1d5b, *note
     st_ctime: 1f6a.  More items may be added at the end by some
     implementations.  For compatibility with older Python versions,
     accessing *note stat_result: 108f. as a tuple always returns
     integers.

     3.3 版新加入: Added the *note st_atime_ns: 1f6b, *note st_mtime_ns:
     1f6c, and *note st_ctime_ns: 1f6d. members.

     3.5 版新加入: Added the *note st_file_attributes: 725. member on
     Windows.

     3.5 版更變: Windows now returns the file index as *note st_ino:
     1f63. when available.

     3.7 版新加入: Added the *note st_fstype: 3c4. member to
     Solaris/derivatives.

     3.8 版新加入: Added the *note st_reparse_tag: 1f77. member on
     Windows.

     3.8 版更變: On Windows, the *note st_mode: 1f62. member now
     identifies special files as ‘S_IFCHR’, ‘S_IFIFO’ or ‘S_IFBLK’ as
     appropriate.

 -- 函式: 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: 3ba.

     *note Availability: 1364.: Unix.

     3.2 版更變: The ‘ST_RDONLY’ and ‘ST_NOSUID’ constants were added.

     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: 36f.

     3.7 版新加入: Added ‘f_fsid’.

 -- Data: os.supports_dir_fd

     A *note set: b74. object indicating which functions in the *note
     os: c5. 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(): 1f2. 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 版新加入.

 -- Data: os.supports_effective_ids

     A *note set: b74. object indicating whether *note os.access(): a36.
     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(): a36.; otherwise it
     will be empty.

     This expression evaluates to ‘True’ if *note os.access(): a36.
     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 版新加入.

 -- Data: os.supports_fd

     A *note set: b74. object indicating which functions in the *note
     os: c5. 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(): a44. accepts open file
     descriptors for `path' on your local platform:

          os.chdir in os.supports_fd

     3.3 版新加入.

 -- Data: os.supports_follow_symlinks

     A *note set: b74. object indicating which functions in the *note
     os: c5. 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(): 1f2. 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: a34.

          備註: 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: 1d4. is raised when the function is called by
          an unprivileged user.

     Raises an *note auditing event: e96. ‘os.symlink’ with arguments
     ‘src’, ‘dst’, ‘dir_fd’.

     *note Availability: 1364.: Unix, Windows.

     3.2 版更變: Added support for Windows 6.0 (Vista) symbolic links.

     3.3 版新加入: Added the `dir_fd' argument, and now allow
     `target_is_directory' on non-Windows platforms.

     3.6 版更變: Accepts a *note path-like object: 36f. 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 Availability: 1364.: 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: 3ba.

     Raises an *note auditing event: e96. ‘os.truncate’ with arguments
     ‘path’, ‘length’.

     *note Availability: 1364.: Unix, Windows.

     3.3 版新加入.

     3.5 版更變: Added support for Windows

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.unlink (path, *, dir_fd=None)

     Remove (delete) the file `path'.  This function is semantically
     identical to *note remove(): a3c.; the ‘unlink’ name is its
     traditional Unix name.  Please see the documentation for *note
     remove(): a3c. for further information.

     Raises an *note auditing event: e96. ‘os.remove’ with arguments
     ‘path’, ‘dir_fd’.

     3.3 版新加入: The `dir_fd' parameter.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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(): a42. 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(): 1f2. call, depending on the resolution
     with which your operating system records access and modification
     times; see *note stat(): 1f2.  The best way to preserve exact times
     is to use the `st_atime_ns' and `st_mtime_ns' fields from the *note
     os.stat(): 1f2. result object with the `ns' parameter to ‘utime’.

     This function can support *note specifying a file descriptor: 3ba,
     *note paths relative to directory descriptors: a34. and *note not
     following symlinks: a35.

     Raises an *note auditing event: e96. ‘os.utime’ with arguments
     ‘path’, ‘times’, ‘ns’, ‘dir_fd’.

     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: 36f.

 -- 函式: 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' (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: 1273. or slice assignment), and
     *note walk(): 659. 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(): 659. about directories the caller creates or renames before
     it resumes *note walk(): 659. 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(): 260. call are ignored.
     If optional argument `onerror' is specified, it should be a
     function; it will be called with one argument, an *note OSError:
     1d4. 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(): 659. 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(): 659. 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():
          659.  *note walk(): 659. 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(): 21d.), walking the tree bottom-up is essential,
     *note rmdir(): a3f. 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))

     3.5 版更變: This function now calls *note os.scandir(): 260.
     instead of *note os.listdir(): a46, making it faster by reducing
     the number of calls to *note os.stat(): 1f2.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os.fwalk (top='.', topdown=True, onerror=None, *,
          follow_symlinks=False, dir_fd=None)

     This behaves exactly like *note walk(): 659, 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(): 659. output, and `dirfd' is a file descriptor referring to
     the directory `dirpath'.

     This function always supports *note paths relative to directory
     descriptors: a34. and *note not following symlinks: a35.  Note
     however that, unlike other functions, the *note fwalk(): 3b9.
     default value for `follow_symlinks' is ‘False’.

          備註: Since *note fwalk(): 3b9. yields file descriptors, those
          are only valid until the next iteration step, so you should
          duplicate them (e.g.  with *note dup(): f99.) 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(): a3f. 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)

     *note Availability: 1364.: Unix.

     3.3 版新加入.

     3.6 版更變: Accepts a *note path-like object: 36f.

     3.7 版更變: Added support for *note bytes: 336. paths.

 -- 函式: 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: 7ff.

     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 Availability: 1364.: Linux 3.17 or newer with glibc 2.27 or
     newer.

     3.8 版新加入.

 -- Data: os.MFD_CLOEXEC
 -- Data: os.MFD_ALLOW_SEALING
 -- Data: os.MFD_HUGETLB
 -- Data: os.MFD_HUGE_SHIFT
 -- Data: os.MFD_HUGE_MASK
 -- Data: os.MFD_HUGE_64KB
 -- Data: os.MFD_HUGE_512KB
 -- Data: os.MFD_HUGE_1MB
 -- Data: os.MFD_HUGE_2MB
 -- Data: os.MFD_HUGE_8MB
 -- Data: os.MFD_HUGE_16MB
 -- Data: os.MFD_HUGE_32MB
 -- Data: os.MFD_HUGE_256MB
 -- Data: os.MFD_HUGE_512MB
 -- Data: os.MFD_HUGE_1GB
 -- Data: os.MFD_HUGE_2GB
 -- Data: os.MFD_HUGE_16GB

     These flags can be passed to *note memfd_create(): 1f1.

     *note Availability: 1364.: Linux 3.17 or newer with glibc 2.27 or
     newer.  The ‘MFD_HUGE*’ flags are only available since Linux 4.14.

     3.8 版新加入.

* Menu:

* Linux extended attributes::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0529

   (2) https://bugs.python.org/issue21082

   (3) 
http://pubs.opengroup.org/onlinepubs/009695399/functions/opendir.html

   (4) 
http://pubs.opengroup.org/onlinepubs/009695399/functions/readdir_r.html

   (5) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa364418(v=vs.85).aspx

   (6) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa364428(v=vs.85).aspx

   (7) https://msdn.microsoft.com/en-us/library/aa363788


File: python.info,  Node: Linux extended attributes,  Up: Files and Directories

5.16.1.8 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: 4f0. interface).  If it is
     str, it is encoded with the filesystem encoding.

     This function can support *note specifying a file descriptor: 3ba.
     and *note not following symlinks: a35.

     Raises an *note auditing event: e96. ‘os.getxattr’ with arguments
     ‘path’, ‘attribute’.

     3.6 版更變: Accepts a *note path-like object: 36f. 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(): a51.
     will examine the current directory.

     This function can support *note specifying a file descriptor: 3ba.
     and *note not following symlinks: a35.

     Raises an *note auditing event: e96. ‘os.listxattr’ with argument
     ‘path’.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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: 4f0. interface).  If it is a string, it is
     encoded with the filesystem encoding.

     This function can support *note specifying a file descriptor: 3ba.
     and *note not following symlinks: a35.

     Raises an *note auditing event: e96. ‘os.removexattr’ with
     arguments ‘path’, ‘attribute’.

     3.6 版更變: Accepts a *note path-like object: 36f. 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: 4f0.
     interface).  If it is a str, it is encoded with the filesystem
     encoding.  `flags' may be *note XATTR_REPLACE: 1f8a. or *note
     XATTR_CREATE: 1f8b.  If *note XATTR_REPLACE: 1f8a. is given and the
     attribute does not exist, ‘ENODATA’ will be raised.  If *note
     XATTR_CREATE: 1f8b. 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: 3ba.
     and *note not following symlinks: a35.

          備註: A bug in Linux kernel versions less than 2.6.39 caused
          the flags argument to be ignored on some filesystems.

     Raises an *note auditing event: e96. ‘os.setxattr’ with arguments
     ‘path’, ‘attribute’, ‘value’, ‘flags’.

     3.6 版更變: Accepts a *note path-like object: 36f. for `path' and
     `attribute'.

 -- Data: os.XATTR_SIZE_MAX

     The maximum size the value of an extended attribute can be.
     Currently, this is 64 KiB on Linux.

 -- Data: os.XATTR_CREATE

     This is a possible value for the flags argument in *note
     setxattr(): a53.  It indicates the operation must create an
     attribute.

 -- Data: os.XATTR_REPLACE

     This is a possible value for the flags argument in *note
     setxattr(): a53.  It indicates the operation must replace an
     existing attribute.


File: python.info,  Node: Process Management,  Next: Interface to the scheduler,  Prev: Files and Directories,  Up: os --- Miscellaneous operating system interfaces

5.16.1.9 Process Management
...........................

These functions may be used to create and manage processes.

The various *note exec*: 1f8f. 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(): a82.

 -- 函式: 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 sys.path),
     and also by *note ctypes: 2b.

     Remove the directory by calling `close()' on the returned object or
     using it in a *note with: 6ee. statement.

     See the Microsoft documentation(1) for more information about how
     DLLs are loaded.

     Raises an *note auditing event: e96. ‘os.add_dll_directory’ with
     argument ‘path’.

     *note Availability: 1364.: 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: 2cb. 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: 1d4. 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(): 666. before calling an *note exec*: 1f8f.
     function.

     The "l" and "v" variants of the *note exec*: 1f8f. 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():
     1f92, *note execlpe(): 1f93, *note execvp(): 1f94, and *note
     execvpe(): 1f95.) will use the ‘PATH’ environment variable to
     locate the program `file'.  When the environment is being replaced
     (using one of the *note exec*e: 1f8f. variants, discussed in the
     next paragraph), the new environment is used as the source of the
     ‘PATH’ variable.  The other variants, *note execl(): 1f8f, *note
     execle(): 1f91, *note execv(): 1efe, and *note execve(): a45, will
     not use the ‘PATH’ variable to locate the executable; `path' must
     contain an appropriate absolute or relative path.

     For *note execle(): 1f91, *note execlpe(): 1f93, *note execve():
     a45, and *note execvpe(): 1f95. (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():
     1f8f, *note execlp(): 1f92, *note execv(): 1efe, and *note
     execvp(): 1f94. all cause the new process to inherit the
     environment of the current process.

     For *note execve(): a45. 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: a49.  If it is unavailable,
     using it will raise a *note NotImplementedError: 613.

     Raises an *note auditing event: e96. ‘os.exec’ with arguments
     ‘path’, ‘args’, ‘env’.

     *note Availability: 1364.: Unix, Windows.

     3.3 版新加入: Added support for specifying `path' as an open file
     descriptor for *note execve(): a45.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: os._exit (n)

     Exit the process with status `n', without calling cleanup handlers,
     flushing stdio buffers, etc.

          備註: The standard way to exit is ‘sys.exit(n)’.  *note
          _exit(): 1713. should normally only be used in the child
          process after a *note fork(): 966.

The following exit codes are defined and can be used with *note _exit():
1713, 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.

 -- Data: os.EX_OK

     Exit code that means no error occurred.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_USAGE

     Exit code that means the command was used incorrectly, such as when
     the wrong number of arguments are given.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_DATAERR

     Exit code that means the input data was incorrect.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_NOINPUT

     Exit code that means an input file did not exist or was not
     readable.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_NOUSER

     Exit code that means a specified user did not exist.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_NOHOST

     Exit code that means a specified host did not exist.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_UNAVAILABLE

     Exit code that means that a required service is unavailable.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_SOFTWARE

     Exit code that means an internal software error was detected.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_OSERR

     Exit code that means an operating system error was detected, such
     as the inability to fork or create a pipe.

     *note Availability: 1364.: Unix.

 -- Data: 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 Availability: 1364.: Unix.

 -- Data: os.EX_CANTCREAT

     Exit code that means a user specified output file could not be
     created.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_IOERR

     Exit code that means that an error occurred while doing I/O on some
     file.

     *note Availability: 1364.: Unix.

 -- Data: 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 Availability: 1364.: Unix.

 -- Data: os.EX_PROTOCOL

     Exit code that means that a protocol exchange was illegal, invalid,
     or not understood.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_NOPERM

     Exit code that means that there were insufficient permissions to
     perform the operation (but not intended for file system problems).

     *note Availability: 1364.: Unix.

 -- Data: os.EX_CONFIG

     Exit code that means that some kind of configuration error
     occurred.

     *note Availability: 1364.: Unix.

 -- Data: os.EX_NOTFOUND

     Exit code that means something like "an entry was not found".

     *note Availability: 1364.: Unix.

 -- 函式: 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: 1d4.
     is raised.

     Note that some platforms including FreeBSD <= 6.3 and Cygwin have
     known issues when using ‘fork()’ from a thread.

     Raises an *note auditing event: e96. ‘os.fork’ with no arguments.

     3.8 版更變: Calling ‘fork()’ in a subinterpreter is no longer
     supported (*note RuntimeError: 2bb. is raised).

          警告: See *note ssl: f4. for applications that use the SSL
          module with fork().

     *note Availability: 1364.: Unix.

 -- 函式: 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:
     d6. module.  If an error occurs *note OSError: 1d4. is raised.

     Raises an *note auditing event: e96. ‘os.forkpty’ with no
     arguments.

     3.8 版更變: Calling ‘forkpty()’ in a subinterpreter is no longer
     supported (*note RuntimeError: 2bb. is raised).

     *note Availability: 1364.: some flavors of Unix.

 -- 函式: 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: eb. module.

     Windows: The *note signal.CTRL_C_EVENT: 1fa8. and *note
     signal.CTRL_BREAK_EVENT: 1fa9. 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(): cf8. additionally takes process
     handles to be killed.

     See also *note signal.pthread_kill(): a7f.

     Raises an *note auditing event: e96. ‘os.kill’ with arguments
     ‘pid’, ‘sig’.

     3.2 版新加入: Windows support.

 -- 函式: os.killpg (pgid, sig)

     Send the signal `sig' to the process group `pgid'.

     Raises an *note auditing event: e96. ‘os.killpg’ with arguments
     ‘pgid’, ‘sig’.

     *note Availability: 1364.: Unix.

 -- 函式: os.nice (increment)

     Add `increment' to the process’s "niceness".  Return the new
     niceness.

     *note Availability: 1364.: Unix.

 -- 函式: os.plock (op)

     Lock program segments into memory.  The value of `op' (defined in
     ‘<sys/lock.h>’) determines which segments are locked.

     *note Availability: 1364.: Unix.

 -- 函式: 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 has the same meaning as the corresponding
     argument to the built-in *note open(): 4f5. function.  The returned
     file object reads or writes text strings rather than bytes.

     The ‘close’ method returns *note None: 158. 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.

     This is implemented using *note subprocess.Popen: 2ba.; see that
     class’s documentation for more powerful ways to manage and
     communicate with subprocesses.

 -- 函式: 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(): 3f2. instead of *note
     posix_spawn(): 258.

     The positional-only arguments `path', `args', and `env' are similar
     to *note execve(): a45.

     The `path' parameter is the path to the executable file.  The
     `path' should contain a directory.  Use *note posix_spawnp(): 101a.
     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:

      -- Data: os.POSIX_SPAWN_OPEN

          (‘os.POSIX_SPAWN_OPEN’, `fd', `path', `flags', `mode')

          Performs ‘os.dup2(os.open(path, flags, mode), fd)’.

      -- Data: os.POSIX_SPAWN_CLOSE

          (‘os.POSIX_SPAWN_CLOSE’, `fd')

          Performs ‘os.close(fd)’.

      -- Data: os.POSIX_SPAWN_DUP2

          (‘os.POSIX_SPAWN_DUP2’, `fd', `new_fd')

          Performs ‘os.dup2(fd, new_fd)’.

     These tuples correspond to the C library
     ‘posix_spawn_file_actions_addopen()’,
     ‘posix_spawn_file_actions_addclose()’, and
     ‘posix_spawn_file_actions_adddup2()’ 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: 613. 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: 1fae. 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.

     Raises an *note auditing event: e96. ‘os.posix_spawn’ with
     arguments ‘path’, ‘argv’, ‘env’.

     3.8 版新加入.

     *note Availability: 1364.: Unix.

 -- 函式: 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(): 258. 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)’).

     Raises an *note auditing event: e96. ‘os.posix_spawn’ with
     arguments ‘path’, ‘argv’, ‘env’.

     3.8 版新加入.

     *note Availability: 1364.: See *note posix_spawn(): 258.
     documentation.

 -- 函式: 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(): 966. 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: fa. 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(): 437, *note PyOS_AfterFork_Parent(): 438. and
     *note PyOS_AfterFork_Child(): 2ce.

     There is no way to unregister a function.

     *note Availability: 1364.: Unix.

     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: fa. 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: aef. section.)

     If `mode' is *note P_NOWAIT: 1fb6, this function returns the
     process id of the new process; if `mode' is *note P_WAIT: 1fb7,
     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(): 672. 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*: 1f4b. 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(): 1fb0, *note spawnlpe(): 1fb1, *note spawnvp(): 1fb4, and
     *note spawnvpe(): 1fb5.) will use the ‘PATH’ environment variable
     to locate the program `file'.  When the environment is being
     replaced (using one of the *note spawn*e: 1f4b. variants, discussed
     in the next paragraph), the new environment is used as the source
     of the ‘PATH’ variable.  The other variants, *note spawnl(): 1f4b,
     *note spawnle(): 1faf, *note spawnv(): 1fb2, and *note spawnve():
     1fb3, will not use the ‘PATH’ variable to locate the executable;
     `path' must contain an appropriate absolute or relative path.

     For *note spawnle(): 1faf, *note spawnlpe(): 1fb1, *note spawnve():
     1fb3, and *note spawnvpe(): 1fb5. (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():
     1f4b, *note spawnlp(): 1fb0, *note spawnv(): 1fb2, and *note
     spawnvp(): 1fb4. 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(): 1fb0. and
     *note spawnvpe(): 1fb5. 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)

     Raises an *note auditing event: e96. ‘os.spawn’ with arguments
     ‘mode’, ‘path’, ‘args’, ‘env’.

     *note Availability: 1364.: Unix, Windows.  *note spawnlp(): 1fb0,
     *note spawnlpe(): 1fb1, *note spawnvp(): 1fb4. and *note
     spawnvpe(): 1fb5. are not available on Windows.  *note spawnle():
     1faf. and *note spawnve(): 1fb3. are not thread-safe on Windows; we
     advise you to use the *note subprocess: fa. module instead.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- Data: os.P_NOWAIT
 -- Data: os.P_NOWAITO

     Possible values for the `mode' parameter to the *note spawn*: 1f4b.
     family of functions.  If either of these values is given, the
     ‘spawn*()’ functions will return as soon as the new process has
     been created, with the process id as the return value.

     *note Availability: 1364.: Unix, Windows.

 -- Data: os.P_WAIT

     Possible value for the `mode' parameter to the *note spawn*: 1f4b.
     family of functions.  If this is given as `mode', the ‘spawn*()’
     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 Availability: 1364.: Unix, Windows.

 -- Data: os.P_DETACH
 -- Data: os.P_OVERLAY

     Possible values for the `mode' parameter to the *note spawn*: 1f4b.
     family of functions.  These are less portable than those listed
     above.  *note P_DETACH: 1fb9. is similar to *note P_NOWAIT: 1fb6,
     but the new process is detached from the console of the calling
     process.  If *note P_OVERLAY: 1fba. is used, the current process
     will be replaced; the *note spawn*: 1f4b. function will not return.

     *note Availability: 1364.: Windows.

 -- 函式: os.startfile (path[, operation])

     Start a file with its associated application.

     When `operation' is not specified or ‘'open'’, 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 ‘'print'’ and ‘'edit'’ (to be used on
     files) as well as ‘'explore'’ and ‘'find'’ (to be used on
     directories).

     *note startfile(): 1fbb. 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.
     If you want to use an absolute path, make sure the first character
     is not a slash (‘'/'’); the underlying Win32 ‘ShellExecute()’
     function doesn’t work if it is.  Use the *note os.path.normpath():
     cb4. function to ensure that the path is 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: 613.
     will be raised.

     Raises an *note auditing event: e96. ‘os.startfile’ with arguments
     ‘path’, ‘operation’.

     *note Availability: 1364.: Windows.

 -- 函式: 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: 312, 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.

     On Unix, the return value is the exit status of the process encoded
     in the format specified for *note wait(): 670.  Note that POSIX
     does not specify the meaning of the return value of the C
     ‘system()’ function, so the return value of the Python function is
     system-dependent.

     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: fa. 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: aef. section
     in the *note subprocess: fa. documentation for some helpful
     recipes.

     Raises an *note auditing event: e96. ‘os.system’ with argument
     ‘command’.

     *note Availability: 1364.: Unix, Windows.

 -- 函式: os.times ()

     Returns the current global process times.  The return value is an
     object with five attributes:

        * ‘user’ - user time

        * *note system: dc6. - system time

        * ‘children_user’ - user time of all child processes

        * ‘children_system’ - system time of all child processes

        * ‘elapsed’ - elapsed real time since a fixed point in the past

     For backwards compatibility, this object also behaves like a
     five-tuple containing ‘user’, *note system: dc6, ‘children_user’,
     ‘children_system’, and ‘elapsed’ in that order.

     See the Unix manual page ‘times(2)’ and ‘times(3)’ manual page on
     Unix or the GetProcessTimes MSDN(2) on Windows.  On Windows, only
     ‘user’ and *note system: dc6. are known; the other attributes are
     zero.

     *note Availability: 1364.: 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.

     *note Availability: 1364.: Unix.

 -- 函式: os.waitid (idtype, id, options)

     Wait for the completion of one or more child processes.  `idtype'
     can be *note P_PID: 1fbc, *note P_PGID: 1fbd. or *note P_ALL: 1fbe.
     `id' specifies the pid to wait on.  `options' is constructed from
     the ORing of one or more of *note WEXITED: 1fbf, *note WSTOPPED:
     1fc0. or *note WCONTINUED: 1fc1. and additionally may be ORed with
     *note WNOHANG: 1fc2. or *note WNOWAIT: 1fc3.  The return value is
     an object representing the data contained in the ‘siginfo_t’
     structure, namely: ‘si_pid’, ‘si_uid’, ‘si_signo’, ‘si_status’,
     ‘si_code’ or ‘None’ if *note WNOHANG: 1fc2. is specified and there
     are no children in a waitable state.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- Data: os.P_PID
 -- Data: os.P_PGID
 -- Data: os.P_ALL

     These are the possible values for `idtype' in *note waitid(): 671.
     They affect how `id' is interpreted.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- Data: os.WEXITED
 -- Data: os.WSTOPPED
 -- Data: os.WNOWAIT

     Flags that can be used in `options' in *note waitid(): 671. that
     specify what child signal to wait for.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- Data: os.CLD_EXITED
 -- Data: os.CLD_DUMPED
 -- Data: os.CLD_TRAPPED
 -- Data: os.CLD_CONTINUED

     These are the possible values for ‘si_code’ in the result returned
     by *note waitid(): 671.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: 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(): 670.).  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(): 672. 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').

     An *note OSError: 1d4. is raised with the value of errno when the
     syscall returns -1.

     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*: 1f4b. functions called with *note P_NOWAIT: 1fb6. return
     suitable process handles.

     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: 65e.
     exception (see PEP 475(3) for the rationale).

 -- 函式: os.wait3 (options)

     Similar to *note waitpid(): 672, 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: e1.*note getrusage(): d9e. for details on
     resource usage information.  The option argument is the same as
     that provided to *note waitpid(): 672. and *note wait4(): 66f.

     *note Availability: 1364.: Unix.

 -- 函式: os.wait4 (pid, options)

     Similar to *note waitpid(): 672, except a 3-element tuple,
     containing the child’s process id, exit status indication, and
     resource usage information is returned.  Refer to *note resource:
     e1.*note getrusage(): d9e. for details on resource usage
     information.  The arguments to *note wait4(): 66f. are the same as
     those provided to *note waitpid(): 672.

     *note Availability: 1364.: Unix.

 -- Data: os.WNOHANG

     The option for *note waitpid(): 672. to return immediately if no
     child process status is available immediately.  The function
     returns ‘(0, 0)’ in this case.

     *note Availability: 1364.: Unix.

 -- Data: os.WCONTINUED

     This option causes child processes to be reported if they have been
     continued from a job control stop since their status was last
     reported.

     *note Availability: 1364.: some Unix systems.

 -- Data: os.WUNTRACED

     This option causes child processes to be reported if they have been
     stopped but their current state has not been reported since they
     were stopped.

     *note Availability: 1364.: Unix.

The following functions take a process status code as returned by *note
system(): dc6, *note wait(): 670, or *note waitpid(): 672. 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(): 1fca.
     is true.

     *note Availability: 1364.: Unix.

 -- 函式: os.WIFCONTINUED (status)

     Return ‘True’ if a stopped child has been resumed by delivery of
     *note SIGCONT: 1fcc. (if the process has been continued from a job
     control stop), otherwise return ‘False’.

     See *note WCONTINUED: 1fc1. option.

     *note Availability: 1364.: Unix.

 -- 函式: os.WIFSTOPPED (status)

     Return ‘True’ if the process was stopped by delivery of a signal,
     otherwise return ‘False’.

     *note WIFSTOPPED(): 1fcd. only returns ‘True’ if the *note
     waitpid(): 672. call was done using *note WUNTRACED: 1fc8. option
     or when the process is being traced (see ‘ptrace(2)’).

     *note Availability: 1364.: Unix.

 -- 函式: os.WIFSIGNALED (status)

     Return ‘True’ if the process was terminated by a signal, otherwise
     return ‘False’.

     *note Availability: 1364.: Unix.

 -- 函式: 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: 1364.: Unix.

 -- 函式: os.WEXITSTATUS (status)

     Return the process exit status.

     This function should be employed only if *note WIFEXITED(): 1fce.
     is true.

     *note Availability: 1364.: Unix.

 -- 函式: os.WSTOPSIG (status)

     Return the signal which caused the process to stop.

     This function should be employed only if *note WIFSTOPPED(): 1fcd.
     is true.

     *note Availability: 1364.: Unix.

 -- 函式: os.WTERMSIG (status)

     Return the number of the signal that caused the process to
     terminate.

     This function should be employed only if *note WIFSIGNALED(): 1fca.
     is true.

     *note Availability: 1364.: Unix.

   ---------- Footnotes ----------

   (1) https://msdn.microsoft.com/44228cf2-6306-466c-8f16-f513cd3ba8b5

   (2) 
https://docs.microsoft.com/windows/win32/api/processthreadsapi/nf-processthreadsapi-getprocesstimes

   (3) https://www.python.org/dev/peps/pep-0475


File: python.info,  Node: Interface to the scheduler,  Next: Miscellaneous System Information,  Prev: Process Management,  Up: os --- Miscellaneous operating system interfaces

5.16.1.10 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.

 -- Data: os.SCHED_OTHER

     The default scheduling policy.

 -- Data: os.SCHED_BATCH

     Scheduling policy for CPU-intensive processes that tries to
     preserve interactivity on the rest of the computer.

 -- Data: os.SCHED_IDLE

     Scheduling policy for extremely low priority background tasks.

 -- Data: os.SCHED_SPORADIC

     Scheduling policy for sporadic server programs.

 -- Data: os.SCHED_FIFO

     A First In First Out scheduling policy.

 -- Data: os.SCHED_RR

     A round-robin scheduling policy.

 -- Data: 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(): a5b, *note sched_setscheduler(): a5c, and *note
     sched_getparam(): a57.  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: 1fae.
     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 a scheduling parameters for the process with PID `pid'.  A
     `pid' of 0 means the calling process.  `param' is a *note
     sched_param: 1fae. instance.

 -- 函式: os.sched_getparam (pid)

     Return the scheduling parameters as a *note sched_param: 1fae.
     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' (or the current
     process if zero) is restricted to.


File: python.info,  Node: Miscellaneous System Information,  Next: Random numbers<2>,  Prev: Interface to the scheduler,  Up: os --- Miscellaneous operating system interfaces

5.16.1.11 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: 1fc. 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: 1d4. is raised with *note errno.EINVAL: fce. for the error
     number.

     *note Availability: 1364.: Unix.

 -- Data: os.confstr_names

     Dictionary mapping names accepted by *note confstr(): 1fdd. 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 Availability: 1364.: Unix.

 -- 函式: os.cpu_count ()

     Return the number of CPUs in the system.  Returns ‘None’ if
     undetermined.

     This number is not equivalent to the number of CPUs the current
     process can use.  The number of usable CPUs can be obtained with
     ‘len(os.sched_getaffinity(0))’

     3.4 版新加入.

 -- 函式: 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: 1d4. if
     the load average was unobtainable.

     *note Availability: 1364.: Unix.

 -- 函式: 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(): 1fdd. apply here as well; the dictionary that provides
     information on the known names is given by ‘sysconf_names’.

     *note Availability: 1364.: Unix.

 -- Data: os.sysconf_names

     Dictionary mapping names accepted by *note sysconf(): 1f3c. 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 Availability: 1364.: Unix.

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:
c6. module.

 -- Data: 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: c6.

 -- Data: 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: c6.

 -- Data: 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(): 1bf1. and *note
     os.path.join(): f61. — but it is occasionally useful.  Also
     available via *note os.path: c6.

 -- Data: 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: c6.

 -- Data: os.extsep

     The character which separates the base filename from the extension;
     for example, the ‘'.'’ in ‘os.py’.  Also available via *note
     os.path: c6.

 -- Data: 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: c6.

 -- Data: os.defpath

     The default search path used by *note exec*p*: 1f8f. and *note
     spawn*p*: 1f4b. if the environment doesn’t have a ‘'PATH'’ key.
     Also available via *note os.path: c6.

 -- Data: 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.

 -- Data: os.devnull

     The file path of the null device.  For example: ‘'/dev/null'’ for
     POSIX, ‘'nul'’ for Windows.  Also available via *note os.path: c6.

 -- Data: os.RTLD_LAZY
 -- Data: os.RTLD_NOW
 -- Data: os.RTLD_GLOBAL
 -- Data: os.RTLD_LOCAL
 -- Data: os.RTLD_NODELETE
 -- Data: os.RTLD_NOLOAD
 -- Data: os.RTLD_DEEPBIND

     Flags for use with the *note setdlopenflags(): a6b. and *note
     getdlopenflags(): e53. functions.  See the Unix manual page
     ‘dlopen(3)’ for what the different flags mean.

     3.3 版新加入.


File: python.info,  Node: Random numbers<2>,  Prev: Miscellaneous System Information,  Up: os --- Miscellaneous operating system interfaces

5.16.1.12 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: 1fe3. and
     *note GRND_NONBLOCK: 1fe4.

     See also the Linux getrandom() manual page(1).

     *note Availability: 1364.: Linux 3.17 and newer.

     3.6 版新加入.

 -- 函式: os.urandom (size)

     Return a string 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():
     56e. function can be used to get random bytes in non-blocking mode
     (using the *note GRND_NONBLOCK: 1fe4. 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: 613.
     exception is raised.

     On Windows, it will use ‘CryptGenRandom()’.

     也參考
     ......

     The *note secrets: e5. 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: 1b0e.

     3.6.0 版更變: On Linux, ‘getrandom()’ is now used in blocking mode
     to increase the security.

     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.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.

 -- Data: os.GRND_NONBLOCK

     By default, when reading from ‘/dev/random’, *note getrandom():
     56e. 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: 1fe4. flag is set, then *note
     getrandom(): 56e. does not block in these cases, but instead
     immediately raises *note BlockingIOError: 99c.

     3.6 版新加入.

 -- Data: 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) http://man7.org/linux/man-pages/man2/getrandom.2.html

   (2) https://www.python.org/dev/peps/pep-0524


File: python.info,  Node: io --- Core tools for working with streams,  Next: time --- Time access and conversions,  Prev: os --- Miscellaneous operating system interfaces,  Up: Generic Operating System Services

5.16.2 ‘io’ — Core tools for working with streams
-------------------------------------------------

`Source code:' Lib/io.py(1)

__________________________________________________________________

* Menu:

* 總覽::
* High-level Module Interface::
* Class hierarchy::
* Performance: Performance<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/io.py


File: python.info,  Node: 總覽,  Next: High-level Module Interface,  Up: io --- Core tools for working with streams

5.16.2.1 總覽
.............

The *note io: a2. module provides Python’s main facilities for dealing
with various types of I/O. There are three main types of I/O: `text
I/O', `binary I/O' and `raw I/O'. These are generic categories, and
various backing stores can be used for each of them.  A concrete object
belonging to any of these categories is called a *note file object: b47.
Other common terms are `stream' and `file-like object'.

Independent of its category, each concrete stream object will also have
various capabilities: it can be read-only, write-only, or read-write.
It can also allow arbitrary random access (seeking forwards or backwards
to any location), or only sequential access (for example in the case of
a socket or pipe).

All streams are careful about the type of data you give to them.  For
example giving a *note str: 335. object to the ‘write()’ method of a
binary stream will raise a *note TypeError: 193.  So will giving a *note
bytes: 336. object to the ‘write()’ method of a text stream.

3.3 版更變: Operations that used to raise *note IOError: 997. now raise
*note OSError: 1d4, since *note IOError: 997. is now an alias of *note
OSError: 1d4.

* Menu:

* Text I/O::
* Binary I/O::
* Raw I/O::


File: python.info,  Node: Text I/O,  Next: Binary I/O,  Up: 總覽

5.16.2.2 Text I/O
.................

Text I/O expects and produces *note str: 335. objects.  This means that
whenever the backing store is natively made of bytes (such as in the
case of a file), encoding and decoding of data is made transparently as
well as optional translation of platform-specific newline characters.

The easiest way to create a text stream is with *note open(): 4f5,
optionally specifying an encoding:

     f = open("myfile.txt", "r", encoding="utf-8")

In-memory text streams are also available as *note StringIO: 832.
objects:

     f = io.StringIO("some initial text data")

The text stream API is described in detail in the documentation of *note
TextIOBase: c3e.


File: python.info,  Node: Binary I/O,  Next: Raw I/O,  Prev: Text I/O,  Up: 總覽

5.16.2.3 Binary I/O
...................

Binary I/O (also called `buffered I/O') expects *note bytes-like
objects: 5ed. and produces *note bytes: 336. objects.  No encoding,
decoding, or newline translation is performed.  This category of streams
can be used for all kinds of non-text data, and also when manual control
over the handling of text data is desired.

The easiest way to create a binary stream is with *note open(): 4f5.
with ‘'b'’ in the mode string:

     f = open("myfile.jpg", "rb")

In-memory binary streams are also available as *note BytesIO: 7a0.
objects:

     f = io.BytesIO(b"some initial binary data: \x00\x01")

The binary stream API is described in detail in the docs of *note
BufferedIOBase: 58d.

Other library modules may provide additional ways to create text or
binary streams.  See *note socket.socket.makefile(): b1e. for example.


File: python.info,  Node: Raw I/O,  Prev: Binary I/O,  Up: 總覽

5.16.2.4 Raw I/O
................

Raw I/O (also called `unbuffered I/O') is generally used as a low-level
building-block for binary and text streams; it is rarely useful to
directly manipulate a raw stream from user code.  Nevertheless, you can
create a raw stream by opening a file in binary mode with buffering
disabled:

     f = open("myfile.jpg", "rb", buffering=0)

The raw stream API is described in detail in the docs of *note
RawIOBase: a18.


File: python.info,  Node: High-level Module Interface,  Next: Class hierarchy,  Prev: 總覽,  Up: io --- Core tools for working with streams

5.16.2.5 High-level Module Interface
....................................

 -- Data: io.DEFAULT_BUFFER_SIZE

     An int containing the default buffer size used by the module’s
     buffered I/O classes.  *note open(): 4f5. uses the file’s blksize
     (as obtained by *note os.stat(): 1f2.) if possible.

 -- 函式: io.open (file, mode='r', buffering=-1, encoding=None,
          errors=None, newline=None, closefd=True, opener=None)

     This is an alias for the builtin *note open(): 4f5. function.

     This function raises an *note auditing event: e96. ‘open’ with
     arguments ‘path’, ‘mode’ and ‘flags’.  The ‘mode’ and ‘flags’
     arguments may have been modified or inferred from the original
     call.

 -- 函式: io.open_code (path)

     Opens the provided file with mode ‘'rb'’.  This function should be
     used when the intent is to treat the contents as executable code.

     ‘path’ should be a *note str: 335. and an absolute path.

     The behavior of this function may be overridden by an earlier call
     to the *note PyFile_SetOpenCodeHook(): 1fec.  However, assuming
     that ‘path’ is a *note str: 335. and an absolute path,
     ‘open_code(path)’ should always behave the same as ‘open(path,
     'rb')’.  Overriding the behavior is intended for additional
     validation or preprocessing of the file.

     3.8 版新加入.

 -- 例外: io.BlockingIOError

     This is a compatibility alias for the builtin *note
     BlockingIOError: 99c. exception.

 -- 例外: io.UnsupportedOperation

     An exception inheriting *note OSError: 1d4. and *note ValueError:
     1fc. that is raised when an unsupported operation is called on a
     stream.

也參考
......

*note sys: fe.

     contains the standard IO streams: *note sys.stdin: 312, *note
     sys.stdout: 313, and *note sys.stderr: 314.


File: python.info,  Node: Class hierarchy,  Next: Performance<3>,  Prev: High-level Module Interface,  Up: io --- Core tools for working with streams

5.16.2.6 Class hierarchy
........................

The implementation of I/O streams is organized as a hierarchy of
classes.  First *note abstract base classes: b38. (ABCs), which are used
to specify the various categories of streams, then concrete classes
providing the standard stream implementations.

          備註: The abstract base classes also provide default
          implementations of some methods in order to help
          implementation of concrete stream classes.  For example, *note
          BufferedIOBase: 58d. provides unoptimized implementations of
          ‘readinto()’ and *note readline(): 1708.

At the top of the I/O hierarchy is the abstract base class *note IOBase:
1dc.  It defines the basic interface to a stream.  Note, however, that
there is no separation between reading and writing to streams;
implementations are allowed to raise *note UnsupportedOperation: 1fee.
if they do not support a given operation.

The *note RawIOBase: a18. ABC extends *note IOBase: 1dc.  It deals with
the reading and writing of bytes to a stream.  *note FileIO: ca9.
subclasses *note RawIOBase: a18. to provide an interface to files in the
machine’s file system.

The *note BufferedIOBase: 58d. ABC deals with buffering on a raw byte
stream (*note RawIOBase: a18.).  Its subclasses, *note BufferedWriter:
1602, *note BufferedReader: b8f, and *note BufferedRWPair: 1ff0. buffer
streams that are readable, writable, and both readable and writable.
*note BufferedRandom: 1603. provides a buffered interface to random
access streams.  Another *note BufferedIOBase: 58d. subclass, *note
BytesIO: 7a0, is a stream of in-memory bytes.

The *note TextIOBase: c3e. ABC, another subclass of *note IOBase: 1dc,
deals with streams whose bytes represent text, and handles encoding and
decoding to and from strings.  *note TextIOWrapper: 5f8, which extends
it, is a buffered text interface to a buffered raw stream (*note
BufferedIOBase: 58d.).  Finally, *note StringIO: 832. is an in-memory
stream for text.

Argument names are not part of the specification, and only the arguments
of *note open(): 4f5. are intended to be used as keyword arguments.

The following table summarizes the ABCs provided by the *note io: a2.
module:

ABC                           Inherits               Stub Methods                 Mixin Methods and Properties
                                                                                  
-----------------------------------------------------------------------------------------------------------------------------------------
                                                                                  
*note IOBase: 1dc.                                   ‘fileno’, ‘seek’, and        ‘close’, ‘closed’, ‘__enter__’, ‘__exit__’, ‘flush’,
                                                     ‘truncate’                   ‘isatty’, ‘__iter__’, ‘__next__’, ‘readable’,
                                                                                  ‘readline’, ‘readlines’, ‘seekable’, ‘tell’,
                                                                                  ‘writable’, and ‘writelines’
                                                                                  
                                                                                  
*note RawIOBase: a18.         *note IOBase: 1dc.     ‘readinto’ and ‘write’       Inherited *note IOBase: 1dc. methods, ‘read’, and
                                                                                  ‘readall’
                                                                                  
                                                                                  
*note BufferedIOBase: 58d.    *note IOBase: 1dc.     ‘detach’, ‘read’, ‘read1’,   Inherited *note IOBase: 1dc. methods, ‘readinto’,
                                                     and ‘write’                  and ‘readinto1’
                                                                                  
                                                                                  
*note TextIOBase: c3e.        *note IOBase: 1dc.     ‘detach’, ‘read’,            Inherited *note IOBase: 1dc. methods, ‘encoding’,
                                                     ‘readline’, and ‘write’      ‘errors’, and ‘newlines’
                                                                                  

* Menu:

* I/O Base Classes::
* Raw File I/O::
* Buffered Streams::
* Text I/O: Text I/O<2>.


File: python.info,  Node: I/O Base Classes,  Next: Raw File I/O,  Up: Class hierarchy

5.16.2.7 I/O Base Classes
.........................

 -- 類別: io.IOBase

     The abstract base class for all I/O classes, acting on streams of
     bytes.  There is no public constructor.

     This class provides empty abstract implementations for many methods
     that derived classes can override selectively; the default
     implementations represent a file that cannot be read, written or
     seeked.

     Even though *note IOBase: 1dc. does not declare ‘read()’ or
     ‘write()’ because their signatures will vary, implementations and
     clients should consider those methods part of the interface.  Also,
     implementations may raise a *note ValueError: 1fc. (or *note
     UnsupportedOperation: 1fee.) when operations they do not support
     are called.

     The basic type used for binary data read from or written to a file
     is *note bytes: 336.  Other *note bytes-like objects: 5ed. are
     accepted as method arguments too.  Text I/O classes work with *note
     str: 335. data.

     Note that calling any method (even inquiries) on a closed stream is
     undefined.  Implementations may raise *note ValueError: 1fc. in
     this case.

     *note IOBase: 1dc. (and its subclasses) supports the iterator
     protocol, meaning that an *note IOBase: 1dc. 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(): 1708. below.

     *note IOBase: 1dc. is also a context manager and therefore supports
     the *note with: 6ee. statement.  In this example, `file' is closed
     after the ‘with’ statement’s suite is finished—even if an exception
     occurs:

          with open('spam.txt', 'w') as file:
              file.write('Spam and eggs!')

     *note IOBase: 1dc. provides these data attributes and methods:

      -- 成員函式: close ()

          Flush and close this stream.  This method has no effect if the
          file is already closed.  Once the file is closed, any
          operation on the file (e.g.  reading or writing) will raise a
          *note ValueError: 1fc.

          As a convenience, it is allowed to call this method more than
          once; only the first call, however, will have an effect.

      -- 屬性: closed

          ‘True’ if the stream is closed.

      -- 成員函式: fileno ()

          Return the underlying file descriptor (an integer) of the
          stream if it exists.  An *note OSError: 1d4. is raised if the
          IO object does not use a file descriptor.

      -- 成員函式: flush ()

          Flush the write buffers of the stream if applicable.  This
          does nothing for read-only and non-blocking streams.

      -- 成員函式: isatty ()

          Return ‘True’ if the stream is interactive (i.e., connected to
          a terminal/tty device).

      -- 成員函式: readable ()

          Return ‘True’ if the stream can be read from.  If ‘False’,
          ‘read()’ will raise *note OSError: 1d4.

      -- 成員函式: readline (size=-1)

          Read and return one line from the stream.  If `size' is
          specified, at most `size' bytes will be read.

          The line terminator is always ‘b'\n'’ for binary files; for
          text files, the `newline' argument to *note open(): 4f5. can
          be used to select the line terminator(s) recognized.

      -- 成員函式: readlines (hint=-1)

          Read and return a list of lines from the stream.  `hint' can
          be specified to control the number of lines read: no more
          lines will be read if the total size (in bytes/characters) of
          all lines so far exceeds `hint'.

          Note that it’s already possible to iterate on file objects
          using ‘for line in file: ...’ without calling
          ‘file.readlines()’.

      -- 成員函式: seek (offset, whence=SEEK_SET)

          Change the stream position to the given byte `offset'.
          `offset' is interpreted relative to the position indicated by
          `whence'.  The default value for `whence' is ‘SEEK_SET’.
          Values for `whence' are:

             * ‘SEEK_SET’ or ‘0’ – start of the stream (the default);
               `offset' should be zero or positive

             * ‘SEEK_CUR’ or ‘1’ – current stream position; `offset' may
               be negative

             * ‘SEEK_END’ or ‘2’ – end of the stream; `offset' is
               usually negative

          Return the new absolute position.

          3.1 版新加入: The ‘SEEK_*’ constants.

          3.3 版新加入: Some operating systems could support additional
          values, like ‘os.SEEK_HOLE’ or ‘os.SEEK_DATA’.  The valid
          values for a file could depend on it being open in text or
          binary mode.

      -- 成員函式: seekable ()

          Return ‘True’ if the stream supports random access.  If
          ‘False’, *note seek(): 1d9d, *note tell(): 1d9e. and *note
          truncate(): caa. will raise *note OSError: 1d4.

      -- 成員函式: tell ()

          Return the current stream position.

      -- 成員函式: truncate (size=None)

          Resize the stream to the given `size' in bytes (or the current
          position if `size' is not specified).  The current stream
          position isn’t changed.  This resizing can extend or reduce
          the current file size.  In case of extension, the contents of
          the new file area depend on the platform (on most systems,
          additional bytes are zero-filled).  The new file size is
          returned.

          3.5 版更變: Windows will now zero-fill files when extending.

      -- 成員函式: writable ()

          Return ‘True’ if the stream supports writing.  If ‘False’,
          ‘write()’ and *note truncate(): caa. will raise *note OSError:
          1d4.

      -- 成員函式: writelines (lines)

          Write a list of lines to the stream.  Line separators are not
          added, so it is usual for each of the lines provided to have a
          line separator at the end.

      -- 成員函式: __del__ ()

          Prepare for object destruction.  *note IOBase: 1dc. provides a
          default implementation of this method that calls the
          instance’s *note close(): 1013. method.

 -- 類別: io.RawIOBase

     Base class for raw binary I/O. It inherits *note IOBase: 1dc.
     There is no public constructor.

     Raw binary I/O typically provides low-level access to an underlying
     OS device or API, and does not try to encapsulate it in high-level
     primitives (this is left to Buffered I/O and Text I/O, described
     later in this page).

     In addition to the attributes and methods from *note IOBase: 1dc,
     *note RawIOBase: a18. provides the following methods:

      -- 成員函式: read (size=-1)

          Read up to `size' bytes from the object and return them.  As a
          convenience, if `size' is unspecified or -1, all bytes until
          EOF are returned.  Otherwise, only one system call is ever
          made.  Fewer than `size' bytes may be returned if the
          operating system call returns fewer than `size' bytes.

          If 0 bytes are returned, and `size' was not 0, this indicates
          end of file.  If the object is in non-blocking mode and no
          bytes are available, ‘None’ is returned.

          The default implementation defers to *note readall(): 1ff7.
          and *note readinto(): 708.

      -- 成員函式: readall ()

          Read and return all the bytes from the stream until EOF, using
          multiple calls to the stream if necessary.

      -- 成員函式: readinto (b)

          Read bytes into a pre-allocated, writable *note bytes-like
          object: 5ed. `b', and return the number of bytes read.  For
          example, `b' might be a *note bytearray: 337.  If the object
          is in non-blocking mode and no bytes are available, ‘None’ is
          returned.

      -- 成員函式: write (b)

          Write the given *note bytes-like object: 5ed, `b', to the
          underlying raw stream, and return the number of bytes written.
          This can be less than the length of `b' in bytes, depending on
          specifics of the underlying raw stream, and especially if it
          is in non-blocking mode.  ‘None’ is returned if the raw stream
          is set not to block and no single byte could be readily
          written to it.  The caller may release or mutate `b' after
          this method returns, so the implementation should only access
          `b' during the method call.

 -- 類別: io.BufferedIOBase

     Base class for binary streams that support some kind of buffering.
     It inherits *note IOBase: 1dc.  There is no public constructor.

     The main difference with *note RawIOBase: a18. is that methods
     *note read(): 1d5d, *note readinto(): 1ff9. and *note write(): 58e.
     will try (respectively) to read as much input as requested or to
     consume all given output, at the expense of making perhaps more
     than one system call.

     In addition, those methods can raise *note BlockingIOError: 99c. if
     the underlying raw stream is in non-blocking mode and cannot take
     or give enough data; unlike their *note RawIOBase: a18.
     counterparts, they will never return ‘None’.

     Besides, the *note read(): 1d5d. method does not have a default
     implementation that defers to *note readinto(): 1ff9.

     A typical *note BufferedIOBase: 58d. implementation should not
     inherit from a *note RawIOBase: a18. implementation, but wrap one,
     like *note BufferedWriter: 1602. and *note BufferedReader: b8f. do.

     *note BufferedIOBase: 58d. provides or overrides these methods and
     attribute in addition to those from *note IOBase: 1dc.:

      -- 屬性: raw

          The underlying raw stream (a *note RawIOBase: a18. instance)
          that *note BufferedIOBase: 58d. deals with.  This is not part
          of the *note BufferedIOBase: 58d. API and may not exist on
          some implementations.

      -- 成員函式: detach ()

          Separate the underlying raw stream from the buffer and return
          it.

          After the raw stream has been detached, the buffer is in an
          unusable state.

          Some buffers, like *note BytesIO: 7a0, do not have the concept
          of a single raw stream to return from this method.  They raise
          *note UnsupportedOperation: 1fee.

          3.1 版新加入.

      -- 成員函式: read (size=-1)

          Read and return up to `size' bytes.  If the argument is
          omitted, ‘None’, or negative, data is read and returned until
          EOF is reached.  An empty *note bytes: 336. object is returned
          if the stream is already at EOF.

          If the argument is positive, and the underlying raw stream is
          not interactive, multiple raw reads may be issued to satisfy
          the byte count (unless EOF is reached first).  But for
          interactive raw streams, at most one raw read will be issued,
          and a short result does not imply that EOF is imminent.

          A *note BlockingIOError: 99c. is raised if the underlying raw
          stream is in non blocking-mode, and has no data available at
          the moment.

      -- 成員函式: read1 ([size])

          Read and return up to `size' bytes, with at most one call to
          the underlying raw stream’s *note read(): 707. (or *note
          readinto(): 708.) method.  This can be useful if you are
          implementing your own buffering on top of a *note
          BufferedIOBase: 58d. object.

          If `size' is ‘-1’ (the default), an arbitrary number of bytes
          are returned (more than zero unless EOF is reached).

      -- 成員函式: readinto (b)

          Read bytes into a pre-allocated, writable *note bytes-like
          object: 5ed. `b' and return the number of bytes read.  For
          example, `b' might be a *note bytearray: 337.

          Like *note read(): 1d5d, multiple reads may be issued to the
          underlying raw stream, unless the latter is interactive.

          A *note BlockingIOError: 99c. is raised if the underlying raw
          stream is in non blocking-mode, and has no data available at
          the moment.

      -- 成員函式: readinto1 (b)

          Read bytes into a pre-allocated, writable *note bytes-like
          object: 5ed. `b', using at most one call to the underlying raw
          stream’s *note read(): 707. (or *note readinto(): 708.)
          method.  Return the number of bytes read.

          A *note BlockingIOError: 99c. is raised if the underlying raw
          stream is in non blocking-mode, and has no data available at
          the moment.

          3.5 版新加入.

      -- 成員函式: write (b)

          Write the given *note bytes-like object: 5ed, `b', and return
          the number of bytes written (always equal to the length of `b'
          in bytes, since if the write fails an *note OSError: 1d4. will
          be raised).  Depending on the actual implementation, these
          bytes may be readily written to the underlying stream, or held
          in a buffer for performance and latency reasons.

          When in non-blocking mode, a *note BlockingIOError: 99c. is
          raised if the data needed to be written to the raw stream but
          it couldn’t accept all the data without blocking.

          The caller may release or mutate `b' after this method
          returns, so the implementation should only access `b' during
          the method call.


File: python.info,  Node: Raw File I/O,  Next: Buffered Streams,  Prev: I/O Base Classes,  Up: Class hierarchy

5.16.2.8 Raw File I/O
.....................

 -- 類別: io.FileIO (name, mode='r', closefd=True, opener=None)

     *note FileIO: ca9. represents an OS-level file containing bytes
     data.  It implements the *note RawIOBase: a18. interface (and
     therefore the *note IOBase: 1dc. interface, too).

     The `name' can be one of two things:

        * a character string or *note bytes: 336. object representing
          the path to the file which will be opened.  In this case
          closefd must be ‘True’ (the default) otherwise an error will
          be raised.

        * an integer representing the number of an existing OS-level
          file descriptor to which the resulting *note FileIO: ca9.
          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: 95d. 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 ‘read()’ (when called with a positive argument), ‘readinto()’
     and ‘write()’ 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: 66a. as `opener'
     results in functionality similar to passing ‘None’).

     The newly created file is *note non-inheritable: 7ff.

     See the *note open(): 4f5. 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.

     In addition to the attributes and methods from *note IOBase: 1dc.
     and *note RawIOBase: a18, *note FileIO: ca9. provides the following
     data attributes:

      -- 屬性: 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: Text I/O<2>,  Prev: Raw File I/O,  Up: Class hierarchy

5.16.2.9 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])

     A stream implementation using an in-memory bytes buffer.  It
     inherits *note BufferedIOBase: 58d.  The buffer is discarded when
     the *note close(): 1013. method is called.

     The optional argument `initial_bytes' is a *note bytes-like object:
     5ed. that contains initial data.

     *note BytesIO: 7a0. provides or overrides these methods in addition
     to those from *note BufferedIOBase: 58d. and *note IOBase: 1dc.:

      -- 成員函式: 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: 7a0.
               object cannot be resized or closed.

          3.2 版新加入.

      -- 成員函式: getvalue ()

          Return *note bytes: 336. containing the entire contents of the
          buffer.

      -- 成員函式: read1 ([size])

          In *note BytesIO: 7a0, this is the same as *note read(): 1d5d.

          3.7 版更變: The `size' argument is now optional.

      -- 成員函式: readinto1 (b)

          In *note BytesIO: 7a0, this is the same as *note readinto():
          1ff9.

          3.5 版新加入.

 -- 類別: io.BufferedReader (raw, buffer_size=DEFAULT_BUFFER_SIZE)

     A buffer providing higher-level access to a readable, sequential
     *note RawIOBase: a18. object.  It inherits *note BufferedIOBase:
     58d.  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: b8f. for the given
     readable `raw' stream and `buffer_size'.  If `buffer_size' is
     omitted, *note DEFAULT_BUFFER_SIZE: 15fe. is used.

     *note BufferedReader: b8f. provides or overrides these methods in
     addition to those from *note BufferedIOBase: 58d. and *note IOBase:
     1dc.:

      -- 成員函式: peek ([size])

          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])

          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])

          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 buffer providing higher-level access to a writeable, sequential
     *note RawIOBase: a18. object.  It inherits *note BufferedIOBase:
     58d.  When writing to this object, data is normally placed into an
     internal buffer.  The buffer will be written out to the underlying
     *note RawIOBase: a18. object under various conditions, including:

        * when the buffer gets too small for all pending data;

        * when *note flush(): 2004. is called;

        * when a ‘seek()’ is requested (for *note BufferedRandom: 1603.
          objects);

        * when the *note BufferedWriter: 1602. object is closed or
          destroyed.

     The constructor creates a *note BufferedWriter: 1602. for the given
     writeable `raw' stream.  If the `buffer_size' is not given, it
     defaults to *note DEFAULT_BUFFER_SIZE: 15fe.

     *note BufferedWriter: 1602. provides or overrides these methods in
     addition to those from *note BufferedIOBase: 58d. and *note IOBase:
     1dc.:

      -- 成員函式: flush ()

          Force bytes held in the buffer into the raw stream.  A *note
          BlockingIOError: 99c. should be raised if the raw stream
          blocks.

      -- 成員函式: write (b)

          Write the *note bytes-like object: 5ed, `b', and return the
          number of bytes written.  When in non-blocking mode, a *note
          BlockingIOError: 99c. 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 interface to random access streams.  It inherits *note
     BufferedReader: b8f. and *note BufferedWriter: 1602.

     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: 15fe.

     *note BufferedRandom: 1603. is capable of anything *note
     BufferedReader: b8f. or *note BufferedWriter: 1602. can do.  In
     addition, ‘seek()’ and ‘tell()’ are guaranteed to be implemented.

 -- 類別: io.BufferedRWPair (reader, writer,
          buffer_size=DEFAULT_BUFFER_SIZE)

     A buffered I/O object combining two unidirectional *note RawIOBase:
     a18. objects – one readable, the other writeable – into a single
     bidirectional endpoint.  It inherits *note BufferedIOBase: 58d.

     `reader' and `writer' are *note RawIOBase: a18. objects that are
     readable and writeable respectively.  If the `buffer_size' is
     omitted it defaults to *note DEFAULT_BUFFER_SIZE: 15fe.

     *note BufferedRWPair: 1ff0. implements all of *note BufferedIOBase:
     58d.’s methods except for *note detach(): 1ffb, which raises *note
     UnsupportedOperation: 1fee.

          警告: *note BufferedRWPair: 1ff0. 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: 1603. instead.


File: python.info,  Node: Text I/O<2>,  Prev: Buffered Streams,  Up: Class hierarchy

5.16.2.10 Text I/O
..................

 -- 類別: io.TextIOBase

     Base class for text streams.  This class provides a character and
     line based interface to stream I/O. It inherits *note IOBase: 1dc.
     There is no public constructor.

     *note TextIOBase: c3e. provides or overrides these data attributes
     and methods in addition to those from *note IOBase: 1dc.:

      -- 屬性: 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: 58d.
          instance) that *note TextIOBase: c3e. deals with.  This is not
          part of the *note TextIOBase: c3e. API and may not exist in
          some implementations.

      -- 成員函式: detach ()

          Separate the underlying binary buffer from the *note
          TextIOBase: c3e. and return it.

          After the underlying buffer has been detached, the *note
          TextIOBase: c3e. is in an unusable state.

          Some *note TextIOBase: c3e. implementations, like *note
          StringIO: 832, may not have the concept of an underlying
          buffer and calling this method will raise *note
          UnsupportedOperation: 1fee.

          3.1 版新加入.

      -- 成員函式: read (size=-1)

          Read and return at most `size' characters from the stream as a
          single *note str: 335.  If `size' is negative or ‘None’, reads
          until EOF.

      -- 成員函式: readline (size=-1)

          Read until newline or EOF and return a single ‘str’.  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(): 200d, 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 版新加入: The ‘SEEK_*’ constants.

      -- 成員函式: 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 over a *note BufferedIOBase: 58d. binary
     stream.  It inherits *note TextIOBase: c3e.

     `encoding' gives the name of the encoding that the stream will be
     decoded or encoded with.  It defaults to *note
     locale.getpreferredencoding(False): 3aa.

     `errors' is an optional string that specifies how encoding and
     decoding errors are to be handled.  Pass ‘'strict'’ to raise a
     *note ValueError: 1fc. 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(): dfa. 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: 5f9. 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 it is ‘''’, universal newlines mode is enabled, but line
          endings are returned to the caller untranslated.  If it 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: 1601.  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’, ‘flush()’ is implied when a call to
     write contains a newline character or a carriage return.

     If `write_through' is ‘True’, calls to ‘write()’ are guaranteed not
     to be buffered: any data written on the *note TextIOWrapper: 5f8.
     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(): 200f, use the current
     locale encoding instead of the user preferred encoding.

     *note TextIOWrapper: 5f8. provides these members in addition to
     those of *note TextIOBase: c3e. and its parents:

      -- 屬性: line_buffering

          Whether line buffering is enabled.

      -- 屬性: write_through

          Whether writes are passed immediately to the underlying binary
          buffer.

          3.7 版新加入.

      -- 成員函式: reconfigure (*[, encoding][, errors][, newline][,
               line_buffering][, write_through])

          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 版新加入.

 -- 類別: io.StringIO (initial_value='', newline='\n')

     An in-memory stream for text I/O. The text buffer is discarded when
     the *note close(): 1013. 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(): 200e.  The stream is positioned
     at the start of the buffer.

     The `newline' argument works like that of *note TextIOWrapper: 5f8.
     The default is to consider only ‘\n’ characters as ends of lines
     and to do no newline translation.  If `newline' is set to ‘None’,
     newlines are written as ‘\n’ on all platforms, but universal
     newline decoding is still performed when reading.

     *note StringIO: 832. provides this method in addition to those from
     *note TextIOBase: c3e. and its parents:

      -- 成員函式: getvalue ()

          Return a ‘str’ containing the entire contents of the buffer.
          Newlines are decoded as if by *note read(): 200b, although the
          stream position is not changed.

     Example usage:

          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:
     5f9. mode.  It inherits *note codecs.IncrementalDecoder: 1832.


File: python.info,  Node: Performance<3>,  Prev: Class hierarchy,  Up: io --- Core tools for working with streams

5.16.2.11 Performance
.....................

This section discusses the performance of the provided concrete I/O
implementations.

* Menu:

* Binary I/O: Binary I/O<2>.
* Text I/O: Text I/O<3>.
* Multi-threading: Multi-threading<3>.
* Reentrancy::


File: python.info,  Node: Binary I/O<2>,  Next: Text I/O<3>,  Up: Performance<3>

5.16.2.12 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: Text I/O<3>,  Next: Multi-threading<3>,  Prev: Binary I/O<2>,  Up: Performance<3>

5.16.2.13 Text 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, ‘TextIOWrapper.tell()’ and ‘TextIOWrapper.seek()’ are both
quite slow due to the reconstruction algorithm used.

*note StringIO: 832, however, is a native in-memory unicode container
and will exhibit similar speed to *note BytesIO: 7a0.


File: python.info,  Node: Multi-threading<3>,  Next: Reentrancy,  Prev: Text I/O<3>,  Up: Performance<3>

5.16.2.14 Multi-threading
.........................

*note FileIO: ca9. objects are thread-safe to the extent that the
operating system calls (such as ‘read(2)’ under Unix) they wrap are
thread-safe too.

Binary buffered objects (instances of *note BufferedReader: b8f, *note
BufferedWriter: 1602, *note BufferedRandom: 1603. and *note
BufferedRWPair: 1ff0.) protect their internal structures using a lock;
it is therefore safe to call them from multiple threads at once.

*note TextIOWrapper: 5f8. objects are not thread-safe.


File: python.info,  Node: Reentrancy,  Prev: Multi-threading<3>,  Up: Performance<3>

5.16.2.15 Reentrancy
....................

Binary buffered objects (instances of *note BufferedReader: b8f, *note
BufferedWriter: 1602, *note BufferedRandom: 1603. and *note
BufferedRWPair: 1ff0.) are not reentrant.  While reentrant calls will
not happen in normal situations, they can arise from doing I/O in a
*note signal: eb. handler.  If a thread tries to re-enter a buffered
object which it is already accessing, a *note RuntimeError: 2bb. 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(): 4f5.
function will wrap a buffered object inside a *note TextIOWrapper: 5f8.
This includes standard streams and therefore affects the built-in
function *note print(): 88b. as well.


File: python.info,  Node: time --- Time access and conversions,  Next: argparse --- Parser for command-line options arguments and sub-commands,  Prev: io --- Core tools for working with streams,  Up: Generic Operating System Services

5.16.3 ‘time’ — Time access and conversions
-------------------------------------------

__________________________________________________________________

This module provides various time-related functions.  For related
functionality, see also the *note datetime: 31. and *note calendar: 15.
modules.

Although this module is always available, not all functions are
available on all platforms.  Most of the functions defined in this
module call platform C library functions with the same name.  It may
sometimes be helpful to consult the platform documentation, because the
semantics of these functions varies among platforms.

An explanation of some terminology and conventions is in order.

   * The `epoch' is the point where the time starts, and is platform
     dependent.  For Unix, the epoch is January 1, 1970, 00:00:00 (UTC).
     To find out what the epoch is on a given platform, look at
     ‘time.gmtime(0)’.

   * The term `seconds since the epoch' refers to the total number of
     elapsed seconds since the epoch, typically excluding leap
     seconds(1).  Leap seconds are excluded from this total on all
     POSIX-compliant platforms.

   * The functions in this module may not handle dates and times before
     the epoch or far in the future.  The cut-off point in the future is
     determined by the C library; for 32-bit systems, it is typically in
     2038.

   * Function *note strptime(): d96. can parse 2-digit years when given
     ‘%y’ format code.  When 2-digit years are parsed, they are
     converted according to the POSIX and ISO C standards: values 69–99
     are mapped to 1969–1999, and values 0–68 are mapped to 2000–2068.

   * UTC is Coordinated Universal Time (formerly known as Greenwich Mean
     Time, or GMT). The acronym UTC is not a mistake but a compromise
     between English and French.

   * DST is Daylight Saving Time, an adjustment of the timezone by
     (usually) one hour during part of the year.  DST rules are magic
     (determined by local law) and can change from year to year.  The C
     library has a table containing the local rules (often it is read
     from a system file for flexibility) and is the only source of True
     Wisdom in this respect.

   * The precision of the various real-time functions may be less than
     suggested by the units in which their value or argument is
     expressed.  E.g.  on most Unix systems, the clock "ticks" only 50
     or 100 times a second.

   * On the other hand, the precision of *note time(): 322. and *note
     sleep(): 685. is better than their Unix equivalents: times are
     expressed as floating point numbers, *note time(): 322. returns the
     most accurate time available (using Unix ‘gettimeofday()’ where
     available), and *note sleep(): 685. will accept a time with a
     nonzero fraction (Unix ‘select()’ is used to implement this, where
     available).

   * The time value as returned by *note gmtime(): b44, *note
     localtime(): f52, and *note strptime(): d96, and accepted by *note
     asctime(): b68, *note mktime(): b69. and *note strftime(): b6a, is
     a sequence of 9 integers.  The return values of *note gmtime():
     b44, *note localtime(): f52, and *note strptime(): d96. also offer
     attribute names for individual fields.

     See *note struct_time: 59e. for a description of these objects.

     3.3 版更變: The *note struct_time: 59e. type was extended to
     provide the ‘tm_gmtoff’ and ‘tm_zone’ attributes when platform
     supports corresponding ‘struct tm’ members.

     3.6 版更變: The *note struct_time: 59e. attributes ‘tm_gmtoff’ and
     ‘tm_zone’ are now available on all platforms.

   * Use the following functions to convert between time
     representations:

     From                          To                            Use
                                                                 
     ------------------------------------------------------------------------------------------
                                                                 
     seconds since the epoch       *note struct_time: 59e. in    *note gmtime(): b44.
                                   UTC                           
                                   
                                                                 
     seconds since the epoch       *note struct_time: 59e. in    *note localtime(): f52.
                                   local time                    
                                   
                                                                 
     *note struct_time: 59e. in    seconds since the epoch       *note calendar.timegm(): 1923.
     UTC                                                         

     *note struct_time: 59e. in    seconds since the epoch       *note mktime(): b69.
     local time                                                  

* Menu:

* Functions: Functions<2>.
* Clock ID Constants::
* Timezone Constants::

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Leap_second


File: python.info,  Node: Functions<2>,  Next: Clock ID Constants,  Up: time --- Time access and conversions

5.16.3.1 Functions
..................

 -- 函式: time.asctime ([t])

     Convert a tuple or *note struct_time: 59e. representing a time as
     returned by *note gmtime(): b44. or *note localtime(): f52. to a
     string of the following form: ‘'Sun Jun 20 23:21:05 1993'’.  The
     day field is two characters long and is space padded if the day is
     a single digit, e.g.: ‘'Wed Jun 9 04:26:40 1993'’.

     If `t' is not provided, the current time as returned by *note
     localtime(): f52. is used.  Locale information is not used by *note
     asctime(): b68.

          備註: Unlike the C function of the same name, *note asctime():
          b68. does not add a trailing newline.

 -- 函式: time.pthread_getcpuclockid (thread_id)

     Return the `clk_id' of the thread-specific CPU-time clock for the
     specified `thread_id'.

     Use *note threading.get_ident(): ab4. or the *note ident: 201e.
     attribute of *note threading.Thread: 236. objects to get a suitable
     value for `thread_id'.

          警告: Passing an invalid or expired `thread_id' may result in
          undefined behavior, such as segmentation fault.

     *note Availability: 1364.: Unix (see the man page for
     ‘pthread_getcpuclockid(3)’ for further information).

     3.7 版新加入.

 -- 函式: time.clock_getres (clk_id)

     Return the resolution (precision) of the specified clock `clk_id'.
     Refer to *note Clock ID Constants: 201f. for a list of accepted
     values for `clk_id'.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: time.clock_gettime (clk_id) -> float

     Return the time of the specified clock `clk_id'.  Refer to *note
     Clock ID Constants: 201f. for a list of accepted values for
     `clk_id'.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: time.clock_gettime_ns (clk_id) -> int

     Similar to *note clock_gettime(): ab8. but return time as
     nanoseconds.

     *note Availability: 1364.: Unix.

     3.7 版新加入.

 -- 函式: time.clock_settime (clk_id, time: float)

     Set the time of the specified clock `clk_id'.  Currently, *note
     CLOCK_REALTIME: 2020. is the only accepted value for `clk_id'.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: time.clock_settime_ns (clk_id, time: int)

     Similar to *note clock_settime(): ab9. but set time with
     nanoseconds.

     *note Availability: 1364.: Unix.

     3.7 版新加入.

 -- 函式: time.ctime ([secs])

     Convert a time expressed in seconds since the epoch to a string of
     a form: ‘'Sun Jun 20 23:21:05 1993'’ representing local time.  The
     day field is two characters long and is space padded if the day is
     a single digit, e.g.: ‘'Wed Jun 9 04:26:40 1993'’.

     If `secs' is not provided or *note None: 158, the current time as
     returned by *note time(): 322. is used.  ‘ctime(secs)’ is
     equivalent to ‘asctime(localtime(secs))’.  Locale information is
     not used by *note ctime(): 18bc.

 -- 函式: time.get_clock_info (name)

     Get information on the specified clock as a namespace object.
     Supported clock names and the corresponding functions to read their
     value are:

        * ‘'monotonic'’: *note time.monotonic(): 774.

        * ‘'perf_counter'’: *note time.perf_counter(): 2ab.

        * ‘'process_time'’: *note time.process_time(): 2ac.

        * ‘'thread_time'’: *note time.thread_time(): 3fe.

        * ‘'time'’: *note time.time(): 322.

     The result has the following attributes:

        - `adjustable': ‘True’ if the clock can be changed automatically
          (e.g.  by a NTP daemon) or manually by the system
          administrator, ‘False’ otherwise

        - `implementation': The name of the underlying C function used
          to get the clock value.  Refer to *note Clock ID Constants:
          201f. for possible values.

        - `monotonic': ‘True’ if the clock cannot go backward, ‘False’
          otherwise

        - `resolution': The resolution of the clock in seconds (*note
          float: 188.)

     3.3 版新加入.

 -- 函式: time.gmtime ([secs])

     Convert a time expressed in seconds since the epoch to a *note
     struct_time: 59e. in UTC in which the dst flag is always zero.  If
     `secs' is not provided or *note None: 158, the current time as
     returned by *note time(): 322. is used.  Fractions of a second are
     ignored.  See above for a description of the *note struct_time:
     59e. object.  See *note calendar.timegm(): 1923. for the inverse of
     this function.

 -- 函式: time.localtime ([secs])

     Like *note gmtime(): b44. but converts to local time.  If `secs' is
     not provided or *note None: 158, the current time as returned by
     *note time(): 322. is used.  The dst flag is set to ‘1’ when DST
     applies to the given time.

 -- 函式: time.mktime (t)

     This is the inverse function of *note localtime(): f52.  Its
     argument is the *note struct_time: 59e. or full 9-tuple (since the
     dst flag is needed; use ‘-1’ as the dst flag if it is unknown)
     which expresses the time in `local' time, not UTC. It returns a
     floating point number, for compatibility with *note time(): 322.
     If the input value cannot be represented as a valid time, either
     *note OverflowError: 965. or *note ValueError: 1fc. will be raised
     (which depends on whether the invalid value is caught by Python or
     the underlying C libraries).  The earliest date for which it can
     generate a time is platform-dependent.

 -- 函式: time.monotonic () -> float

     Return the value (in fractional seconds) of a monotonic clock, i.e.
     a clock that cannot go backwards.  The clock is not affected by
     system clock updates.  The reference point of the returned value is
     undefined, so that only the difference between the results of two
     calls is valid.

     3.3 版新加入.

     3.5 版更變: The function is now always available and always
     system-wide.

 -- 函式: time.monotonic_ns () -> int

     Similar to *note monotonic(): 774, but return time as nanoseconds.

     3.7 版新加入.

 -- 函式: time.perf_counter () -> float

     Return the value (in fractional seconds) of a performance counter,
     i.e.  a clock with the highest available resolution to measure a
     short duration.  It does include time elapsed during sleep and is
     system-wide.  The reference point of the returned value is
     undefined, so that only the difference between the results of two
     calls is valid.

     3.3 版新加入.

 -- 函式: time.perf_counter_ns () -> int

     Similar to *note perf_counter(): 2ab, but return time as
     nanoseconds.

     3.7 版新加入.

 -- 函式: time.process_time () -> float

     Return the value (in fractional seconds) of the sum of the system
     and user CPU time of the current process.  It does not include time
     elapsed during sleep.  It is process-wide by definition.  The
     reference point of the returned value is undefined, so that only
     the difference between the results of two calls is valid.

     3.3 版新加入.

 -- 函式: time.process_time_ns () -> int

     Similar to *note process_time(): 2ac. but return time as
     nanoseconds.

     3.7 版新加入.

 -- 函式: time.sleep (secs)

     Suspend execution of the calling thread for the given number of
     seconds.  The argument may be a floating point number to indicate a
     more precise sleep time.  The actual suspension time may be less
     than that requested because any caught signal will terminate the
     *note sleep(): 685. following execution of that signal’s catching
     routine.  Also, the suspension time may be longer than requested by
     an arbitrary amount because of the scheduling of other activity in
     the system.

     3.5 版更變: The function now sleeps at least `secs' even if the
     sleep is interrupted by a signal, except if the signal handler
     raises an exception (see PEP 475(1) for the rationale).

 -- 函式: time.strftime (format[, t])

     Convert a tuple or *note struct_time: 59e. representing a time as
     returned by *note gmtime(): b44. or *note localtime(): f52. to a
     string as specified by the `format' argument.  If `t' is not
     provided, the current time as returned by *note localtime(): f52.
     is used.  `format' must be a string.  *note ValueError: 1fc. is
     raised if any field in `t' is outside of the allowed range.

     0 is a legal argument for any position in the time tuple; if it is
     normally illegal the value is forced to a correct one.

     The following directives can be embedded in the `format' string.
     They are shown without the optional field width and precision
     specification, and are replaced by the indicated characters in the
     *note strftime(): b6a. result:

     Directive       Meaning                                              註解
                                                                          
     ---------------------------------------------------------------------------------
                                                                          
     ‘%a’            Locale’s abbreviated weekday name.
                     
                                                                          
     ‘%A’            Locale’s full weekday name.
                     
                                                                          
     ‘%b’            Locale’s abbreviated month name.
                     
                                                                          
     ‘%B’            Locale’s full month name.
                     
                                                                          
     ‘%c’            Locale’s appropriate date and time representation.
                     
                                                                          
     ‘%d’            Day of the month as a decimal number [01,31].
                     
                                                                          
     ‘%H’            Hour (24-hour clock) as a decimal number [00,23].
                     
                                                                          
     ‘%I’            Hour (12-hour clock) as a decimal number [01,12].
                     
                                                                          
     ‘%j’            Day of the year as a decimal number [001,366].
                     
                                                                          
     ‘%m’            Month as a decimal number [01,12].
                     
                                                                          
     ‘%M’            Minute as a decimal number [00,59].
                     
                                                                          
     ‘%p’            Locale’s equivalent of either AM or PM.              (1)
                                                                          
                                                                          
     ‘%S’            Second as a decimal number [00,61].                  (2)
                                                                          
                                                                          
     ‘%U’            Week number of the year (Sunday as the first day     (3)
                     of the week) as a decimal number [00,53].  All       
                     days in a new year preceding the first Sunday are
                     considered to be in week 0.
                     
                                                                          
     ‘%w’            Weekday as a decimal number [0(Sunday),6].
                     
                                                                          
     ‘%W’            Week number of the year (Monday as the first day     (3)
                     of the week) as a decimal number [00,53].  All       
                     days in a new year preceding the first Monday are
                     considered to be in week 0.
                     
                                                                          
     ‘%x’            Locale’s appropriate date representation.
                     
                                                                          
     ‘%X’            Locale’s appropriate time representation.
                     
                                                                          
     ‘%y’            Year without century as a decimal number [00,99].
                     
                                                                          
     ‘%Y’            Year with century as a decimal number.
                     
                                                                          
     ‘%z’            Time zone offset indicating a positive or negative
                     time difference from UTC/GMT of the form +HHMM or
                     -HHMM, where H represents decimal hour digits and
                     M represents decimal minute digits [-23:59,
                     +23:59].
                     
                                                                          
     ‘%Z’            Time zone name (no characters if no time zone
                     exists).
                     
                                                                          
     ‘%%’            A literal ‘'%'’ character.
                     

     註解：

       1. When used with the *note strptime(): d96. function, the ‘%p’
          directive only affects the output hour field if the ‘%I’
          directive is used to parse the hour.

       2. The range really is ‘0’ to ‘61’; value ‘60’ is valid in
          timestamps representing leap seconds(2) and value ‘61’ is
          supported for historical reasons.

       3. When used with the *note strptime(): d96. function, ‘%U’ and
          ‘%W’ are only used in calculations when the day of the week
          and the year are specified.

     Here is an example, a format for dates compatible with that
     specified in the RFC 2822(3) Internet email standard.  (4)

          >>> from time import gmtime, strftime
          >>> strftime("%a, %d %b %Y %H:%M:%S +0000", gmtime())
          'Thu, 28 Jun 2001 14:17:15 +0000'

     Additional directives may be supported on certain platforms, but
     only the ones listed here have a meaning standardized by ANSI C. To
     see the full set of format codes supported on your platform,
     consult the ‘strftime(3)’ documentation.

     On some platforms, an optional field width and precision
     specification can immediately follow the initial ‘'%'’ of a
     directive in the following order; this is also not portable.  The
     field width is normally 2 except for ‘%j’ where it is 3.

 -- 函式: time.strptime (string[, format])

     Parse a string representing a time according to a format.  The
     return value is a *note struct_time: 59e. as returned by *note
     gmtime(): b44. or *note localtime(): f52.

     The `format' parameter uses the same directives as those used by
     *note strftime(): b6a.; it defaults to ‘"%a %b %d %H:%M:%S %Y"’
     which matches the formatting returned by *note ctime(): 18bc.  If
     `string' cannot be parsed according to `format', or if it has
     excess data after parsing, *note ValueError: 1fc. is raised.  The
     default values used to fill in any missing data when more accurate
     values cannot be inferred are ‘(1900, 1, 1, 0, 0, 0, 0, 1, -1)’.
     Both `string' and `format' must be strings.

     For example:

          >>> 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)

     Support for the ‘%Z’ directive is based on the values contained in
     ‘tzname’ and whether ‘daylight’ is true.  Because of this, it is
     platform-specific except for recognizing UTC and GMT which are
     always known (and are considered to be non-daylight savings
     timezones).

     Only the directives specified in the documentation are supported.
     Because ‘strftime()’ is implemented per platform it can sometimes
     offer more directives than those listed.  But ‘strptime()’ is
     independent of any platform and thus does not necessarily support
     all directives available that are not documented as supported.

 -- 類別: time.struct_time

     The type of the time value sequence returned by *note gmtime():
     b44, *note localtime(): f52, and *note strptime(): d96.  It is an
     object with a *note named tuple: aa8. interface: values can be
     accessed by index and by attribute name.  The following values are
     present:

     Index       Attribute               Values
                                         
     --------------------------------------------------------------------------
                                         
     0           ‘tm_year’               (for example, 1993)
                                         
                                         
     1           ‘tm_mon’                range [1, 12]
                                         
                                         
     2           ‘tm_mday’               range [1, 31]
                                         
                                         
     3           ‘tm_hour’               range [0, 23]
                                         
                                         
     4           ‘tm_min’                range [0, 59]
                                         
                                         
     5           ‘tm_sec’                range [0, 61]; see `(2)' in
                                         *note strftime(): b6a. description
                                         
                                         
     6           ‘tm_wday’               range [0, 6], Monday is 0
                                         
                                         
     7           ‘tm_yday’               range [1, 366]
                                         
                                         
     8           ‘tm_isdst’              0, 1 or -1; see below
                                         
                                         
     N/A         ‘tm_zone’               abbreviation of timezone name
                                         
                                         
     N/A         ‘tm_gmtoff’             offset east of UTC in seconds
                                         

     Note that unlike the C structure, the month value is a range of [1,
     12], not [0, 11].

     In calls to *note mktime(): b69, ‘tm_isdst’ may be set to 1 when
     daylight savings time is in effect, and 0 when it is not.  A value
     of -1 indicates that this is not known, and will usually result in
     the correct state being filled in.

     When a tuple with an incorrect length is passed to a function
     expecting a *note struct_time: 59e, or having elements of the wrong
     type, a *note TypeError: 193. is raised.

 -- 函式: time.time () -> float

     Return the time in seconds since the *note epoch: 201b. as a
     floating point number.  The specific date of the epoch and the
     handling of leap seconds(5) is platform dependent.  On Windows and
     most Unix systems, the epoch is January 1, 1970, 00:00:00 (UTC) and
     leap seconds are not counted towards the time in seconds since the
     epoch.  This is commonly referred to as Unix time(6).  To find out
     what the epoch is on a given platform, look at ‘gmtime(0)’.

     Note that even though the time is always returned as a floating
     point number, not all systems provide time with a better precision
     than 1 second.  While this function normally returns non-decreasing
     values, it can return a lower value than a previous call if the
     system clock has been set back between the two calls.

     The number returned by *note time(): 322. may be converted into a
     more common time format (i.e.  year, month, day, hour, etc...)  in
     UTC by passing it to *note gmtime(): b44. function or in local time
     by passing it to the *note localtime(): f52. function.  In both
     cases a *note struct_time: 59e. object is returned, from which the
     components of the calendar date may be accessed as attributes.

 -- 函式: 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.

     *note Availability: 1364.: Windows, Linux, Unix systems supporting
     ‘CLOCK_THREAD_CPUTIME_ID’.

     3.7 版新加入.

 -- 函式: time.thread_time_ns () -> int

     Similar to *note thread_time(): 3fe. but return time as
     nanoseconds.

     3.7 版新加入.

 -- 函式: time.time_ns () -> int

     Similar to *note time(): 322. but returns time as an integer number
     of nanoseconds since the *note epoch: 201b.

     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 Availability: 1364.: Unix.

          備註: Although in many cases, changing the ‘TZ’ environment
          variable may affect the output of functions like *note
          localtime(): f52. without calling *note tzset(): 2021, 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’ and ‘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:

          ‘J`n'’

               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.

          ‘M`m'.`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)’)
     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://www.python.org/dev/peps/pep-0475

   (2) https://en.wikipedia.org/wiki/Leap_second

   (3) https://tools.ietf.org/html/rfc2822.html

   (4) (1) 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://tools.ietf.org/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://tools.ietf.org/html/rfc822.html) became obsolete and the
4-digit year has been first recommended by RFC 1123
(https://tools.ietf.org/html/rfc1123.html) and then mandated by RFC 2822
(https://tools.ietf.org/html/rfc2822.html).

   (5) https://en.wikipedia.org/wiki/Leap_second

   (6) https://en.wikipedia.org/wiki/Unix_time


File: python.info,  Node: Clock ID Constants,  Next: Timezone Constants,  Prev: Functions<2>,  Up: time --- Time access and conversions

5.16.3.2 Clock ID Constants
...........................

These constants are used as parameters for *note clock_getres(): ab7.
and *note clock_gettime(): ab8.

 -- Data: time.CLOCK_BOOTTIME

     Identical to *note CLOCK_MONOTONIC: 3fb, 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: 2020, which may have discontinuities if the time is
     changed using ‘settimeofday()’ or similar.

     *note Availability: 1364.: Linux 2.6.39 or later.

     3.7 版新加入.

 -- Data: 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 Availability: 1364.: Solaris.

     3.3 版新加入.

 -- Data: time.CLOCK_MONOTONIC

     Clock that cannot be set and represents monotonic time since some
     unspecified starting point.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- Data: time.CLOCK_MONOTONIC_RAW

     Similar to *note CLOCK_MONOTONIC: 3fb, but provides access to a raw
     hardware-based time that is not subject to NTP adjustments.

     *note Availability: 1364.: Linux 2.6.28 and newer, macOS 10.12 and
     newer.

     3.3 版新加入.

 -- Data: time.CLOCK_PROCESS_CPUTIME_ID

     High-resolution per-process timer from the CPU.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- Data: time.CLOCK_PROF

     High-resolution per-process timer from the CPU.

     *note Availability: 1364.: FreeBSD, NetBSD 7 or later, OpenBSD.

     3.7 版新加入.

 -- Data: time.CLOCK_THREAD_CPUTIME_ID

     Thread-specific CPU-time clock.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- Data: 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 Availability: 1364.: FreeBSD, OpenBSD 5.5 or later.

     3.7 版新加入.

 -- Data: 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 Availability: 1364.: macOS 10.12 and newer.

     3.8 版新加入.

The following constant is the only parameter that can be sent to *note
clock_settime(): ab9.

 -- Data: time.CLOCK_REALTIME

     System-wide real-time clock.  Setting this clock requires
     appropriate privileges.

     *note Availability: 1364.: Unix.

     3.3 版新加入.


File: python.info,  Node: Timezone Constants,  Prev: Clock ID Constants,  Up: time --- Time access and conversions

5.16.3.3 Timezone Constants
...........................

 -- Data: 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.

 -- Data: time.daylight

     Nonzero if a DST timezone is defined.  See note below.

 -- Data: 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.

 -- Data: 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: 2029, *note
     daylight: 202a, *note timezone: 202b, and *note tzname: 202c.), the
     value is determined by the timezone rules in effect at module load
     time or the last time *note tzset(): 2021. is called and may be
     incorrect for times in the past.  It is recommended to use the
     ‘tm_gmtoff’ and ‘tm_zone’ results from *note localtime(): f52. to
     obtain timezone information.

也參考
......

Module *note datetime: 31.

     More object-oriented interface to dates and times.

Module *note locale: aa.

     Internationalization services.  The locale setting affects the
     interpretation of many format specifiers in *note strftime(): b6a.
     and *note strptime(): d96.

Module *note calendar: 15.

     General calendar-related functions.  *note timegm(): 1923. is the
     inverse of *note gmtime(): b44. from this module.

註解
....


File: python.info,  Node: argparse --- Parser for command-line options arguments and sub-commands,  Next: getopt --- C-style parser for command line options,  Prev: time --- Time access and conversions,  Up: Generic Operating System Services

5.16.4 ‘argparse’ — Parser for command-line options, arguments and sub-commands
-------------------------------------------------------------------------------

3.2 版新加入.

`Source code:' Lib/argparse.py(1)

__________________________________________________________________

Tutorial
........

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: 202f.

The *note argparse: 6. module makes it easy to write user-friendly
command-line interfaces.  The program defines what arguments it
requires, and *note argparse: 6. will figure out how to parse those out
of *note sys.argv: c00.  The *note argparse: 6. module also
automatically generates help and usage messages and issues errors when
users give the program invalid arguments.

* Menu:

* Example: Example<7>.
* ArgumentParser objects::
* The add_argument() method: The add_argument method.
* The parse_args() method: The parse_args method.
* Other utilities::
* Upgrading optparse code::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/argparse.py


File: python.info,  Node: Example<7>,  Next: ArgumentParser objects,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.1 Example
................

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 Python code above is saved into a file called ‘prog.py’, it
can be run at the command line and 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

     optional arguments:
      -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, it will issue an error:

     $ 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:

* Creating a parser::
* Adding arguments::
* Parsing arguments::


File: python.info,  Node: Creating a parser,  Next: Adding arguments,  Up: Example<7>

5.16.4.2 Creating a parser
..........................

The first step in using the *note argparse: 6. is creating an *note
ArgumentParser: 69a. object:

     >>> parser = argparse.ArgumentParser(description='Process some integers.')

The *note ArgumentParser: 69a. object will hold all the information
necessary to parse the command line into Python data types.


File: python.info,  Node: Adding arguments,  Next: Parsing arguments,  Prev: Creating a parser,  Up: Example<7>

5.16.4.3 Adding arguments
.........................

Filling an *note ArgumentParser: 69a. with information about program
arguments is done by making calls to the *note add_argument(): 2033.
method.  Generally, these calls tell the *note ArgumentParser: 69a. how
to take the strings on the command line and turn them into objects.
This information is stored and used when *note parse_args(): 2034. 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(): 2034. will return an object with two
attributes, ‘integers’ and ‘accumulate’.  The ‘integers’ attribute will
be a list of one or more ints, and the ‘accumulate’ attribute will be
either the *note sum(): 1e6. function, if ‘--sum’ was specified at the
command line, or the *note max(): 80f. function if it was not.


File: python.info,  Node: Parsing arguments,  Prev: Adding arguments,  Up: Example<7>

5.16.4.4 Parsing arguments
..........................

*note ArgumentParser: 69a. parses arguments through the *note
parse_args(): 2034. 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: 2036.
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(): 2034. will typically be called with no
arguments, and the *note ArgumentParser: 69a. will automatically
determine the command-line arguments from *note sys.argv: c00.


File: python.info,  Node: ArgumentParser objects,  Next: The add_argument method,  Prev: Example<7>,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.5 ArgumentParser objects
...............................

 -- 類別: 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)

     Create a new *note ArgumentParser: 69a. 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: 2038. - The name of the program (default:
          ‘sys.argv[0]’)

        * *note usage: 2039. - The string describing the program usage
          (default: generated from arguments added to parser)

        * *note description: 203a. - Text to display before the argument
          help (default: none)

        * *note epilog: 203b. - Text to display after the argument help
          (default: none)

        * *note parents: 203c. - A list of *note ArgumentParser: 69a.
          objects whose arguments should also be included

        * *note formatter_class: 203d. - A class for customizing the
          help output

        * *note prefix_chars: 203e. - The set of characters that prefix
          optional arguments (default: ’-’)

        * *note fromfile_prefix_chars: 203f. - The set of characters
          that prefix files from which additional arguments should be
          read (default: ‘None’)

        * *note argument_default: 2040. - The global default value for
          arguments (default: ‘None’)

        * *note conflict_handler: 2041. - The strategy for resolving
          conflicting optionals (usually unnecessary)

        * *note add_help: 2042. - Add a ‘-h/--help’ option to the parser
          (default: ‘True’)

        * *note allow_abbrev: 69c. - Allows long options to be
          abbreviated if the abbreviation is unambiguous.  (default:
          ‘True’)

     3.5 版更變: `allow_abbrev' parameter was added.

     3.8 版更變: In previous versions, `allow_abbrev' also disabled
     grouping of short flags such as ‘-vv’ to mean ‘-v -v’.

The following sections describe how each of these are used.

* Menu:

* prog::
* usage::
* description::
* epilog::
* parents::
* formatter_class::
* prefix_chars::
* fromfile_prefix_chars::
* argument_default::
* allow_abbrev::
* conflict_handler::
* add_help::


File: python.info,  Node: prog,  Next: usage,  Up: ArgumentParser objects

5.16.4.6 prog
.............

By default, *note ArgumentParser: 69a. 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]

     optional arguments:
      -h, --help  show this help message and exit
      --foo FOO   foo help
     $ cd ..
     $ python subdir/myprogram.py --help
     usage: myprogram.py [-h] [--foo FOO]

     optional arguments:
      -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: 69a.:

     >>> parser = argparse.ArgumentParser(prog='myprogram')
     >>> parser.print_help()
     usage: myprogram [-h]

     optional arguments:
      -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]

     optional arguments:
      -h, --help  show this help message and exit
      --foo FOO   foo of the myprogram program


File: python.info,  Node: usage,  Next: description,  Prev: prog,  Up: ArgumentParser objects

5.16.4.7 usage
..............

By default, *note ArgumentParser: 69a. 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

     optional arguments:
      -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

     optional arguments:
      -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: description,  Next: epilog,  Prev: usage,  Up: ArgumentParser objects

5.16.4.8 description
....................

Most calls to the *note ArgumentParser: 69a. 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

     optional arguments:
      -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: 203d. argument.


File: python.info,  Node: epilog,  Next: parents,  Prev: description,  Up: ArgumentParser objects

5.16.4.9 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: 69a.:

     >>> 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

     optional arguments:
      -h, --help  show this help message and exit

     And that's how you'd foo a bar

As with the *note description: 203a. argument, the ‘epilog=’ text is by
default line-wrapped, but this behavior can be adjusted with the *note
formatter_class: 203d. argument to *note ArgumentParser: 69a.


File: python.info,  Node: parents,  Next: formatter_class,  Prev: epilog,  Up: ArgumentParser objects

5.16.4.10 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: 69a. can be used.  The ‘parents=’ argument takes a list
of *note ArgumentParser: 69a. objects, collects all the positional and
optional actions from them, and adds these actions to the *note
ArgumentParser: 69a. 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: 69a. 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 objects

5.16.4.11 formatter_class
.........................

*note ArgumentParser: 69a. 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: 2043. and *note RawTextHelpFormatter:
2044. give more control over how textual descriptions are displayed.  By
default, *note ArgumentParser: 69a. objects line-wrap the *note
description: 203a. and *note epilog: 203b. 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

     optional arguments:
      -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: 2043. as ‘formatter_class=’
indicates that *note description: 203a. and *note epilog: 203b. 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

     optional arguments:
      -h, --help  show this help message and exit

*note RawTextHelpFormatter: 2044. 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: 2045. 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 [bar ...]]

     positional arguments:
      bar         BAR! (default: [1, 2, 3])

     optional arguments:
      -h, --help  show this help message and exit
      --foo FOO   FOO! (default: 42)

*note MetavarTypeHelpFormatter: 2046. uses the name of the *note type:
2047. argument for each argument as the display name for its values
(rather than using the *note dest: 2048. 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

     optional arguments:
       -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 objects

5.16.4.12 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 objects

5.16.4.13 fromfile_prefix_chars
...............................

Sometimes, for example when dealing with a particularly long argument
lists, 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: 69a. 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') 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(): 2049.) 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']’.

The ‘fromfile_prefix_chars=’ argument defaults to ‘None’, meaning that
arguments will never be treated as file references.


File: python.info,  Node: argument_default,  Next: allow_abbrev,  Prev: fromfile_prefix_chars,  Up: ArgumentParser objects

5.16.4.14 argument_default
..........................

Generally, argument defaults are specified either by passing a default
to *note add_argument(): 2033. or by calling the *note set_defaults():
204a. 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: 69a.  For example, to globally
suppress attribute creation on *note parse_args(): 2034. 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 objects

5.16.4.15 allow_abbrev
......................

Normally, when you pass an argument list to the *note parse_args():
2034. method of an *note ArgumentParser: 69a, it *note recognizes
abbreviations: 69b. 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 objects

5.16.4.16 conflict_handler
..........................

*note ArgumentParser: 69a. objects do not allow two actions with the
same option string.  By default, *note ArgumentParser: 69a. 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: 203c.) 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: 69a.:

     >>> 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]

     optional arguments:
      -h, --help  show this help message and exit
      -f FOO      old foo help
      --foo FOO   new foo help

Note that *note ArgumentParser: 69a. 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,  Prev: conflict_handler,  Up: ArgumentParser objects

5.16.4.17 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]

     optional arguments:
      -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: 69a.:

     >>> parser = argparse.ArgumentParser(prog='PROG', add_help=False)
     >>> parser.add_argument('--foo', help='foo help')
     >>> parser.print_help()
     usage: PROG [--foo FOO]

     optional arguments:
      --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]

     optional arguments:
       +h, ++help  show this help message and exit


File: python.info,  Node: The add_argument method,  Next: The parse_args method,  Prev: ArgumentParser objects,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.18 The add_argument() method
...................................

 -- 成員函式: ArgumentParser.add_argument (name or flags...[, action][,
          nargs][, const][, default][, type][, choices][, required][,
          help][, metavar][, dest])

     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: 204d. - Either a name or a list of option
          strings, e.g.  ‘foo’ or ‘-f, --foo’.

        * *note action: 204e. - The basic type of action to be taken
          when this argument is encountered at the command line.

        * *note nargs: 204f. - The number of command-line arguments that
          should be consumed.

        * *note const: 2050. - A constant value required by some *note
          action: 204e. and *note nargs: 204f. selections.

        * *note default: 2051. - The value produced if the argument is
          absent from the command line.

        * *note type: 2047. - The type to which the command-line
          argument should be converted.

        * *note choices: 2052. - A container of the allowable values for
          the argument.

        * *note required: 2053. - Whether or not the command-line option
          may be omitted (optionals only).

        * *note help: 2054. - A brief description of what the argument
          does.

        * *note metavar: 2055. - A name for the argument in usage
          messages.

        * *note dest: 2048. - The name of the attribute to be added to
          the object returned by *note parse_args(): 2034.

The following sections describe how each of these are used.

* Menu:

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


File: python.info,  Node: name or flags,  Next: action,  Up: The add_argument method

5.16.4.19 name or flags
.......................

The *note add_argument(): 2033. 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(): 2033. 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(): 2034. 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.20 action
................

*note ArgumentParser: 69a. 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(): 2034.  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: 2050. keyword argument.  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.  This is useful to allow an option to be specified
     multiple times.  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: 2050. keyword argument to the list.
     (Note that the *note const: 2050. 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: 69a.
     for details of how the output is created.

   * ‘'version'’ - This expects a ‘version=’ keyword argument in the
     *note add_argument(): 2033. 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 recommended way
to do this is to extend *note Action: 2056, overriding the ‘__call__’
method and optionally the ‘__init__’ method.

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: 2056.


File: python.info,  Node: nargs,  Next: const,  Prev: action,  Up: The add_argument method

5.16.4.21 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.  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: 2051. 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:
     2050. 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

   * ‘argparse.REMAINDER’.  All the remaining command-line arguments are
     gathered into a list.  This is commonly useful for command line
     utilities that dispatch to other command line utilities:

          >>> parser = argparse.ArgumentParser(prog='PROG')
          >>> parser.add_argument('--foo')
          >>> parser.add_argument('command')
          >>> parser.add_argument('args', nargs=argparse.REMAINDER)
          >>> print(parser.parse_args('--foo B cmd --arg1 XX ZZ'.split()))
          Namespace(args=['--arg1', 'XX', 'ZZ'], command='cmd', foo='B')

If the ‘nargs’ keyword argument is not provided, the number of arguments
consumed is determined by the *note action: 204e.  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.22 const
...............

The ‘const’ argument of *note add_argument(): 2033. is used to hold
constant values that are not read from the command line but are required
for the various *note ArgumentParser: 69a. actions.  The two most common
uses of it are:

   * When *note add_argument(): 2033. 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(): 2034.  See the *note action: 204e.
     description for examples.

   * When *note add_argument(): 2033. 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 instead.  See the *note nargs: 204f.
     description for examples.

With the ‘'store_const'’ and ‘'append_const'’ actions, the ‘const’
keyword argument must be given.  For other actions, it defaults to
‘None’.


File: python.info,  Node: default,  Next: type,  Prev: const,  Up: The add_argument method

5.16.4.23 default
.................

All optional arguments and some positional arguments may be omitted at
the command line.  The ‘default’ keyword argument of *note
add_argument(): 2033, 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 ‘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: 2047. conversion argument, if provided, before setting the
attribute on the *note Namespace: 2036. 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: 204f. 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.24 type
..............

By default, *note ArgumentParser: 69a. objects read command-line
arguments in as simple strings.  However, quite often the command-line
string should instead be interpreted as another type, like a *note
float: 188. or *note int: 185.  The ‘type’ keyword argument of *note
add_argument(): 2033. allows any necessary type-checking and type
conversions to be performed.  Common built-in types and functions can be
used directly as the value of the ‘type’ argument:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('foo', type=int)
     >>> parser.add_argument('bar', type=open)
     >>> parser.parse_args('2 temp.txt'.split())
     Namespace(bar=<_io.TextIOWrapper name='temp.txt' encoding='UTF-8'>, foo=2)

See the section on the *note default: 2051. keyword argument for
information on when the ‘type’ argument is applied to default arguments.

To ease the use of various types of files, the argparse module provides
the factory FileType which takes the ‘mode=’, ‘bufsize=’, ‘encoding=’
and ‘errors=’ arguments of the *note open(): 4f5. function.  For
example, ‘FileType('w')’ can be used to create a writable file:

     >>> parser = argparse.ArgumentParser()
     >>> parser.add_argument('bar', type=argparse.FileType('w'))
     >>> parser.parse_args(['out.txt'])
     Namespace(bar=<_io.TextIOWrapper name='out.txt' encoding='UTF-8'>)

‘type=’ can take any callable that takes a single string argument and
returns the converted value:

     >>> def perfect_square(string):
     ...     value = int(string)
     ...     sqrt = math.sqrt(value)
     ...     if sqrt != int(sqrt):
     ...         msg = "%r is not a perfect square" % string
     ...         raise argparse.ArgumentTypeError(msg)
     ...     return value
     ...
     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('foo', type=perfect_square)
     >>> parser.parse_args(['9'])
     Namespace(foo=9)
     >>> parser.parse_args(['7'])
     usage: PROG [-h] foo
     PROG: error: argument foo: '7' is not a perfect square

The *note choices: 2052. keyword argument may be more convenient for
type checkers that simply check against a range of values:

     >>> parser = argparse.ArgumentParser(prog='PROG')
     >>> parser.add_argument('foo', type=int, choices=range(5, 10))
     >>> parser.parse_args(['7'])
     Namespace(foo=7)
     >>> parser.parse_args(['11'])
     usage: PROG [-h] {5,6,7,8,9}
     PROG: error: argument foo: invalid choice: 11 (choose from 5, 6, 7, 8, 9)

See the *note choices: 2052. section for more details.


File: python.info,  Node: choices,  Next: required,  Prev: type,  Up: The add_argument method

5.16.4.25 choices
.................

Some command-line arguments should be selected from a restricted set of
values.  These can be handled by passing a container object as the
`choices' keyword argument to *note add_argument(): 2033.  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' container is checked after any
*note type: 2047. conversions have been performed, so the type of the
objects in the `choices' container should match the *note type: 2047.
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 container can be passed as the `choices' value, so *note list: 263.
objects, *note set: b74. objects, and custom containers are all
supported.


File: python.info,  Node: required,  Next: help,  Prev: choices,  Up: The add_argument method

5.16.4.26 required
..................

In general, the *note argparse: 6. 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():
2033.:

     >>> 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(): 2034. 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: help,  Next: metavar,  Prev: required,  Up: The add_argument method

5.16.4.27 help
..............

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

     optional arguments:
      -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: 2051.  The available specifiers include the program name,
‘%(prog)s’ and most keyword arguments to *note add_argument(): 2033,
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)

     optional arguments:
      -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: 6. 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]

     optional arguments:
       -h, --help  show this help message and exit


File: python.info,  Node: metavar,  Next: dest,  Prev: help,  Up: The add_argument method

5.16.4.28 metavar
.................

When *note ArgumentParser: 69a. generates help messages, it needs some
way to refer to each expected argument.  By default, ArgumentParser
objects use the *note dest: 2048. value as the "name" of each object.
By default, for positional argument actions, the *note dest: 2048. value
is used directly, and for optional argument actions, the *note dest:
2048. 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

     optional arguments:
      -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

     optional arguments:
      -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(): 2034. object is still determined by
the *note dest: 2048. 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]

     optional arguments:
      -h, --help     show this help message and exit
      -x X X
      --foo bar baz


File: python.info,  Node: dest,  Next: Action classes,  Prev: metavar,  Up: The add_argument method

5.16.4.29 dest
..............

Most *note ArgumentParser: 69a. actions add some value as an attribute
of the object returned by *note parse_args(): 2034.  The name of this
attribute is determined by the ‘dest’ keyword argument of *note
add_argument(): 2033.  For positional argument actions, ‘dest’ is
normally supplied as the first argument to *note add_argument(): 2033.:

     >>> 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: 69a. 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: Action classes,  Prev: dest,  Up: The add_argument method

5.16.4.30 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
‘add_argument()’.

 -- 類別: 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(): 2033. 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: 2036. object that will be
     returned by *note parse_args(): 2034.  Most actions add an
     attribute to this object using *note setattr(): 15e1.

   * ‘values’ - The associated command-line arguments, with any type
     conversions applied.  Type conversions are specified with the *note
     type: 2047. keyword argument to *note add_argument(): 2033.

   * ‘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’.


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.31 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(): 2033. determine exactly
     what objects are created and how they are assigned.  See the
     documentation for *note add_argument(): 2033. for details.

        * *note args: 205a. - List of strings to parse.  The default is
          taken from *note sys.argv: c00.

        * *note namespace: 205b. - An object to take the attributes.
          The default is a new empty *note Namespace: 2036. 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.32 Option value syntax
.............................

The *note parse_args(): 2034. 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.33 Invalid arguments
...........................

While parsing the command line, *note parse_args(): 2034. 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.34 Arguments containing ‘-’
..................................

The *note parse_args(): 2034. 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(): 2034. 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(): 2034. that everything after that is a
positional argument:

     >>> parser.parse_args(['--', '-f'])
     Namespace(foo='-f', one=None)


File: python.info,  Node: Argument abbreviations prefix matching,  Next: Beyond sys argv,  Prev: Arguments containing -,  Up: The parse_args method

5.16.4.35 Argument abbreviations (prefix matching)
..................................................

The *note parse_args(): 2034. method *note by default: 69c. 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:
69c. 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.36 Beyond ‘sys.argv’
...........................

Sometimes it may be useful to have an ArgumentParser parse arguments
other than those of *note sys.argv: c00.  This can be accomplished by
passing a list of strings to *note parse_args(): 2034.  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.37 The Namespace object
..............................

 -- 類別: argparse.Namespace

     Simple class used by default by *note parse_args(): 2034. to create
     an object holding attributes and return it.

This class is deliberately simple, just an *note object: 2b1. 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(): 103c.:

     >>> 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: 69a. assign
attributes to an already existing object, rather than a new *note
Namespace: 2036. 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.38 Other utilities
.........................

* Menu:

* Sub-commands::
* FileType objects::
* 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 objects,  Up: Other utilities

5.16.4.39 Sub-commands
......................

 -- 成員函式: ArgumentParser.add_subparsers ([title][, description][,
          prog][, parser_class][, action][, option_string][, 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:
     69a. supports the creation of such sub-commands with the *note
     add_subparsers(): 4a9. method.  The *note add_subparsers(): 4a9.
     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: 69a.
     constructor arguments, and returns an *note ArgumentParser: 69a.
     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: 204e. - the basic type of action to be taken
          when this argument is encountered at the command line

        * *note dest: 2048. - name of the attribute under which
          sub-command name will be stored; by default ‘None’ and no
          value is stored

        * *note required: 2053. - Whether or not a subcommand must be
          provided, by default ‘False’ (added in 3.7)

        * *note help: 2054. - help for sub-parser group in help output,
          by default ‘None’

        * *note metavar: 2055. - string presenting available
          sub-commands in help; by default it is ‘None’ and presents
          sub-commands in form {cmd1, cmd2, ..}

     Some example usage:

          >>> # 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(): 2034. 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

          optional arguments:
            -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

          optional arguments:
            -h, --help  show this help message and exit

          >>> parser.parse_args(['b', '--help'])
          usage: PROG b [-h] [--baz {X,Y,Z}]

          optional arguments:
            -h, --help     show this help message and exit
            --baz {X,Y,Z}  baz help

     The *note add_subparsers(): 4a9. 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} ...

          optional arguments:
            -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')

     One particularly effective way of handling sub-commands is to
     combine the use of the *note add_subparsers(): 4a9. method with
     calls to *note set_defaults(): 204a. 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()
          >>>
          >>> # 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(): 2034. 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(): 4a9. 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 objects,  Next: Argument groups,  Prev: Sub-commands,  Up: Other utilities

5.16.4.40 FileType objects
..........................

 -- 類別: argparse.FileType (mode='r', bufsize=-1, encoding=None,
          errors=None)

     The *note FileType: 825. factory creates objects that can be passed
     to the type argument of *note ArgumentParser.add_argument(): 2033.
     Arguments that have *note FileType: 825. 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():
     4f5. 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 ‘sys.stdin’ for readable *note
     FileType: 825. objects and ‘sys.stdout’ for writable *note
     FileType: 825. 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 版新加入: The `encodings' and `errors' keyword arguments.


File: python.info,  Node: Argument groups,  Next: Mutual exclusion,  Prev: FileType objects,  Up: Other utilities

5.16.4.41 Argument groups
.........................

 -- 成員函式: ArgumentParser.add_argument_group (title=None,
          description=None)

     By default, *note ArgumentParser: 69a. groups command-line
     arguments into "positional arguments" and "optional arguments" 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(): 2066. 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(): 2066. method returns an argument
     group object which has an *note add_argument(): 2033. method just
     like a regular *note ArgumentParser: 69a.  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(): 2066. 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.


File: python.info,  Node: Mutual exclusion,  Next: Parser defaults,  Prev: Argument groups,  Up: Other utilities

5.16.4.42 Mutual exclusion
..........................

 -- 成員函式: ArgumentParser.add_mutually_exclusive_group
          (required=False)

     Create a mutually exclusive group.  *note argparse: 6. 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(): 2068. 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(): 2066.


File: python.info,  Node: Parser defaults,  Next: Printing help,  Prev: Mutual exclusion,  Up: Other utilities

5.16.4.43 Parser defaults
.........................

 -- 成員函式: ArgumentParser.set_defaults (**kwargs)

     Most of the time, the attributes of the object returned by *note
     parse_args(): 2034. will be fully determined by inspecting the
     command-line arguments and the argument actions.  *note
     set_defaults(): 204a. 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(): 4a9. 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(): 2033. or by *note set_defaults(): 204a.:

          >>> 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.44 Printing help
.......................

In most typical applications, *note parse_args(): 2034. 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: 69a.
     should be invoked on the command line.  If `file' is ‘None’, *note
     sys.stdout: 313. 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: 69a.
     If `file' is ‘None’, *note sys.stdout: 313. 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: 69a. 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: 69a.


File: python.info,  Node: Partial parsing,  Next: Customizing file parsing,  Prev: Printing help,  Up: Other utilities

5.16.4.45 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(): 2071. method can be useful.
It works much like *note parse_args(): 2034. 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: 69b. rules apply to
     ‘parse_known_args()’.  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.46 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: 69a. constructor) are read one argument per line.
     *note convert_arg_line_to_args(): 2049. 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.47 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.48 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(): 34a. and
*note parse_known_intermixed_args(): 2077. 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,
‘argparse.REMAINDER’, and mutually exclusive groups that include both
optionals and positionals are not supported.

The following example shows the difference between *note
parse_known_args(): 2071. and *note parse_intermixed_args(): 34a.: 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(): 2077. returns a two item tuple
containing the populated namespace and the list of remaining argument
strings.  *note parse_intermixed_args(): 34a. raises an error if there
are any remaining unparsed argument strings.

3.7 版新加入.


File: python.info,  Node: Upgrading optparse code,  Prev: Other utilities,  Up: argparse --- Parser for command-line options arguments and sub-commands

5.16.4.49 Upgrading optparse code
.................................

Originally, the *note argparse: 6. module had attempted to maintain
compatibility with *note optparse: c4.  However, *note optparse: c4. 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: c4. had either been
copy-pasted over or monkey-patched, it no longer seemed practical to try
to maintain the backwards compatibility.

The *note argparse: 6. module improves on the standard library *note
optparse: c4. 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: c4. to *note argparse: 6.:

   * Replace all *note optparse.OptionParser.add_option(): 2079. calls
     with *note ArgumentParser.add_argument(): 2033. calls.

   * Replace ‘(options, args) = parser.parse_args()’ with ‘args =
     parser.parse_args()’ and add additional *note
     ArgumentParser.add_argument(): 2033. calls for the positional
     arguments.  Keep in mind that what was previously called ‘options’,
     now in the *note argparse: 6. context is called ‘args’.

   * Replace *note optparse.OptionParser.disable_interspersed_args():
     207a. by using *note parse_intermixed_args(): 34a. instead of *note
     parse_args(): 2034.

   * 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 ‘optparse.Values’ with *note Namespace: 2036. and
     ‘optparse.OptionError’ and ‘optparse.OptionValueError’ with
     ‘ArgumentError’.

   * 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: getopt --- C-style parser for command line options,  Next: logging --- Logging facility for Python,  Prev: argparse --- Parser for command-line options arguments and sub-commands,  Up: Generic Operating System Services

5.16.5 ‘getopt’ — C-style parser for command line options
---------------------------------------------------------

`Source code:' Lib/getopt.py(1)

     備註: The *note getopt: 87. 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: 6. 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: 207e. 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(): 87, except that GNU style
     scanning mode is used by default.  This means that option and
     non-option arguments may be intermixed.  The *note getopt(): 87.
     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: 207e.; 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: 6. 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 ..

也參考
......

Module *note argparse: 6.

     Alternative command line option and argument parsing library.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/getopt.py


File: python.info,  Node: logging --- Logging facility for Python,  Next: logging config --- Logging configuration,  Prev: getopt --- C-style parser for command line options,  Up: Generic Operating System Services

5.16.6 ‘logging’ — Logging facility for Python
----------------------------------------------

`Source code:' Lib/logging/__init__.py(1)

Important
.........

This page contains the API reference information.  For tutorial
information and discussion of more advanced topics, see

   * *note Basic Tutorial: b77.

   * *note Advanced Tutorial: b78.

   * *note Logging Cookbook: b79.

__________________________________________________________________

This module defines functions and classes which implement a flexible
event logging system for applications and libraries.

The key benefit of having the logging API provided by a standard library
module is that all Python modules can participate in logging, so your
application log can include your own messages integrated with messages
from third-party modules.

The module provides a lot of functionality and flexibility.  If you are
unfamiliar with logging, the best way to get to grips with it is to see
the tutorials (see the links on the right).

The basic classes defined by the module, together with their functions,
are listed 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.

   * Formatters specify the layout of log records in the final output.

* Menu:

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

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/logging/__init__.py


File: python.info,  Node: Logger Objects,  Next: Logging Levels,  Up: logging --- Logging facility for Python

5.16.6.1 Logger Objects
.......................

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(): 2085. 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’.  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

      -- 屬性: propagate

          If this attribute evaluates to true, events logged to this
          logger will be passed to the handlers of higher level
          (ancestor) loggers, in addition to any handlers attached to
          this logger.  Messages are passed directly to the ancestor
          loggers’ handlers - neither the level nor filters of the
          ancestor loggers in question are considered.

          If this evaluates to false, logging messages are not passed to
          the handlers of ancestor loggers.

          The constructor sets this attribute to ‘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.

      -- 成員函式: 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'.

          When a logger is created, the level is set to ‘NOTSET’ (which
          causes all messages to be processed when the logger is the
          root logger, or delegation to the parent when the logger is a
          non-root logger).  Note that the root logger is created with
          level ‘WARNING’.

          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.

          See *note Logging Levels: 2088. for a list of levels.

          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 ‘INFO’.  Note, however, that
          levels are internally stored as integers, and methods such as
          e.g.  *note getEffectiveLevel(): 2089. and *note
          isEnabledFor(): 208a. 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():
          2089.

      -- 成員函式: getEffectiveLevel ()

          Indicates the effective level for this logger.  If a value
          other than ‘NOTSET’ has been set using *note setLevel(): 2087,
          it is returned.  Otherwise, the hierarchy is traversed towards
          the root until a value other than ‘NOTSET’ is found, and that
          value is returned.  The value returned is an integer,
          typically one of ‘logging.DEBUG’, ‘logging.INFO’ 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 版新加入.

      -- 成員函式: debug (msg, *args, **kwargs)

          Logs a message with level ‘DEBUG’ 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(): c64.) or an exception instance is provided, it
          is used; otherwise, *note sys.exc_info(): c64. 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: 90b. 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: 127. 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: 90b. 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)-15s %(clientip)s %(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 *note
          Formatter: 208b. documentation 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: 208b. has been set up with a
          format string which expects ’clientip’ and ’user’ in the
          attribute dictionary of the *note LogRecord: 90b.  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: 208b.s would be used with
          particular *note Handler: 208c.s.

          3.2 版更變: The `stack_info' parameter was added.

          3.5 版更變: The `exc_info' parameter can now accept exception
          instances.

          3.8 版更變: The `stacklevel' parameter was added.

      -- 成員函式: info (msg, *args, **kwargs)

          Logs a message with level ‘INFO’ on this logger.  The
          arguments are interpreted as for *note debug(): 208e.

      -- 成員函式: warning (msg, *args, **kwargs)

          Logs a message with level ‘WARNING’ on this logger.  The
          arguments are interpreted as for *note debug(): 208e.

               備註: 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 ‘ERROR’ on this logger.  The
          arguments are interpreted as for *note debug(): 208e.

      -- 成員函式: critical (msg, *args, **kwargs)

          Logs a message with level ‘CRITICAL’ on this logger.  The
          arguments are interpreted as for *note debug(): 208e.

      -- 成員函式: log (level, msg, *args, **kwargs)

          Logs a message with integer level `level' on this logger.  The
          other arguments are interpreted as for *note debug(): 208e.

      -- 成員函式: exception (msg, *args, **kwargs)

          Logs a message with level ‘ERROR’ on this logger.  The
          arguments are interpreted as for *note debug(): 208e.
          Exception info is added to the logging message.  This method
          should only be called from an exception handler.

      -- 成員函式: addFilter (filter)

          Adds the specified filter `filter' to this logger.

      -- 成員函式: removeFilter (filter)

          Removes the specified filter `filter' from this logger.

      -- 成員函式: 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(): 208e. 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(): 2093.

      -- 成員函式: 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: 90b. 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 Objects,  Up: logging --- Logging facility for Python

5.16.6.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
                   
---------------------------------------
                   
‘CRITICAL’         50
                   
                   
‘ERROR’            40
                   
                   
‘WARNING’          30
                   
                   
‘INFO’             20
                   
                   
‘DEBUG’            10
                   
                   
‘NOTSET’           0
                   


File: python.info,  Node: Handler Objects,  Next: Formatter Objects,  Prev: Logging Levels,  Up: logging --- Logging facility for Python

5.16.6.3 Handler Objects
........................

Handlers have the following attributes and methods.  Note that *note
Handler: 208c. is never instantiated directly; this class acts as a base
for more useful subclasses.  However, the *note __init__(): d63. method
in subclasses needs to call *note Handler.__init__(): 209d.

 -- 類別: logging.Handler

      -- 成員函式: __init__ (level=NOTSET)

          Initializes the *note Handler: 208c. instance by setting its
          level, setting the list of filters to the empty list and
          creating a lock (using *note createLock(): 209e.) 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():
          209e.

      -- 成員函式: release ()

          Releases the thread lock acquired with *note acquire(): 209f.

      -- 成員函式: 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 ‘NOTSET’ (which
          causes all messages to be processed).

          See *note Logging Levels: 2088. for a list of levels.

          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 ‘INFO’.

      -- 成員函式: setFormatter (fmt)

          Sets the *note Formatter: 208b. 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(): 20a8. is
          called.  Subclasses should ensure that this gets called from
          overridden *note close(): 20a7. 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(): 20ab. call.  If the
          module-level attribute ‘raiseExceptions’ 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 ‘raiseExceptions’ 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: 613.

For a list of handlers included as standard, see *note logging.handlers:
ad.


File: python.info,  Node: Formatter Objects,  Next: Filter Objects,  Prev: Handler Objects,  Up: logging --- Logging facility for Python

5.16.6.4 Formatter Objects
..........................

*note Formatter: 208b. objects have the following attributes and
methods.  They are responsible for converting a *note LogRecord: 90b. to
(usually) a string which can be interpreted by either a human or an
external system.  The base *note Formatter: 208b. allows a formatting
string to be specified.  If none is supplied, the default value of
‘'%(message)s'’ is used, which just includes the message in the logging
call.  To have additional items of information in the formatted output
(such as a timestamp), keep reading.

A Formatter can be initialized with a format string which makes use of
knowledge of the *note LogRecord: 90b. attributes - such as the default
value mentioned above making use of the fact that the user’s message and
arguments are pre-formatted into a *note LogRecord: 90b.’s `message'
attribute.  This format string contains standard Python %-style mapping
keys.  See section *note printf-style String Formatting: 122a. for more
information on string formatting.

The useful mapping keys in a *note LogRecord: 90b. are given in the
section on *note LogRecord attributes: 20af.

 -- 類別: logging.Formatter (fmt=None, datefmt=None, style='%')

     Returns a new instance of the *note Formatter: 208b. class.  The
     instance is initialized with a format string for the message as a
     whole, as well as a format string for the date/time portion of a
     message.  If no `fmt' is specified, ‘'%(message)s'’ is used.  If no
     `datefmt' is specified, a format is used which is described in the
     *note formatTime(): 20b0. documentation.

     The `style' parameter can be one of ’%’, ’{’ or ’$’ and determines
     how the format string will be merged with its data: using one of
     %-formatting, *note str.format(): 4df. or *note string.Template:
     3f0.  See *note Using particular formatting styles throughout your
     application: 20b1. for more information on using {- and
     $-formatting for log messages.

     3.2 版更變: The `style' parameter was added.

     3.8 版更變: The `validate' parameter was added.  Incorrect or
     mismatched style and fmt will raise a ‘ValueError’.  For example:
     ‘logging.Formatter('%(asctime)s - %(message)s', style='{')’.

      -- 成員函式: 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(): 20b0. is called to
          format the event time.  If there is exception information, it
          is formatted using *note formatException(): 20b3. 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: 208b. subclass which customizes the formatting of
          exception information.  In this case, you will have to clear
          the cached value 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(): 20b4. to
          transform it if necessary.

      -- 成員函式: formatTime (record, datefmt=None)

          This method should be called from *note format(): 4e0. 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(): b6a. 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(): b6a.
          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():
          f52. 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(): f52. or *note
          time.gmtime(): b44.  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).

      -- 成員函式: formatException (exc_info)

          Formats the specified exception information (a standard
          exception tuple as returned by *note sys.exc_info(): c64.) as
          a string.  This default implementation just uses *note
          traceback.print_exception(): 20b5.  The resulting string is
          returned.

      -- 成員函式: formatStack (stack_info)

          Formats the specified stack information (a string as returned
          by *note traceback.print_stack(): 77f, but with the last
          newline removed) as a string.  This default implementation
          just returns the input value.


File: python.info,  Node: Filter Objects,  Next: LogRecord Objects,  Prev: Formatter Objects,  Up: logging --- Logging facility for Python

5.16.6.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: b7c. 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 zero for no,
          nonzero for yes.  If deemed appropriate, the record may be
          modified in-place by this method.

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(): 208e, *note
info(): 20b9, 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(): 20b8. 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(): 20b8.

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: 90b. 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: 20ba.).


File: python.info,  Node: LogRecord Objects,  Next: LogRecord attributes,  Prev: Filter Objects,  Up: logging --- Logging facility for Python

5.16.6.6 LogRecord Objects
..........................

*note LogRecord: 90b. instances are created automatically by the *note
Logger: 3ac. every time something is logged, and can be created manually
via *note makeLogRecord(): 20bd. (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’ field of the
     record.


     參數:

        * ‘name’ – The name of the logger used to log the event
          represented by this LogRecord.  Note that this name will
          always have this value, even though it may be emitted by a
          handler attached to a different (ancestor) logger.

        * ‘level’ – The numeric level of the logging event (one of
          DEBUG, 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’ – The full pathname of the source file where the
          logging call was made.

        * ‘lineno’ – The line number in the source file where the
          logging call was made.

        * ‘msg’ – The event description message, possibly a format
          string with placeholders for variable data.

        * ‘args’ – Variable data to merge into the `msg' argument to
          obtain the event description.

        * ‘exc_info’ – An exception tuple with the current exception
          information, or ‘None’ if no exception information is
          available.

        * ‘func’ – The name of the function or method from which the
          logging call was invoked.

        * ‘sinfo’ – 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: 90b. 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(): 335. 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: 90b. has been made
     more configurable by providing a factory which is used to create
     the record.  The factory can be set using *note
     getLogRecordFactory(): 20bf. and *note setLogRecordFactory(): 20c0.
     (see this for the factory’s signature).

     This functionality can be used to inject your own values into a
     *note LogRecord: 90b. 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 Objects,  Prev: LogRecord Objects,  Up: logging --- Logging facility for Python

5.16.6.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(): 4df.), you can use
‘{attrname}’ as the placeholder in the format string.  If you are using
$-formatting (*note string.Template: 3f0.), 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:03d}’ would format a millisecond
value of ‘4’ as ‘004’.  Refer to the *note str.format(): 4df.
documentation for full details on the options available to you.

Attribute name       Format                        描述
                                                   
-------------------------------------------------------------------------------------------------------
                                                   
args                 You shouldn’t need to         The tuple of arguments merged into ‘msg’ to
                     format this yourself.         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: 90b. 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: 90b. was created
                                                   (as returned by *note time.time(): 322.).
                                                   
                                                   
exc_info             You shouldn’t need to         Exception tuple (à la ‘sys.exc_info’) or, if no
                     format this yourself.         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 (‘DEBUG’,
                                                   ‘INFO’, ‘WARNING’, ‘ERROR’, ‘CRITICAL’).
                                                   
                                                   
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(): 20b2.
                                                   is invoked.
                                                   
                                                   
module               ‘%(module)s’                  Module (name portion of ‘filename’).
                                                   
                                                   
msecs                ‘%(msecs)d’                   Millisecond portion of the time when the
                                                   *note LogRecord: 90b. was created.
                                                   
                                                   
msg                  You shouldn’t need to         The format string passed in the original logging
                     format this yourself.         call.  Merged with ‘args’ to produce ‘message’,
                                                   or an arbitrary object (see
                                                   *note Using arbitrary objects as messages: 20c2.).
                                                   
                                                   
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           You shouldn’t need to         Stack frame information (where available) from
                     format this yourself.         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).
                                                   

3.1 版更變: `processName' was added.


File: python.info,  Node: LoggerAdapter Objects,  Next: Thread Safety,  Prev: LogRecord attributes,  Up: logging --- Logging facility for Python

5.16.6.8 LoggerAdapter Objects
..............................

*note LoggerAdapter: c91. 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:
20c5.

 -- 類別: logging.LoggerAdapter (logger, extra)

     Returns an instance of *note LoggerAdapter: c91. initialized with
     an underlying *note Logger: 3ac. instance and a dict-like object.

      -- 成員函式: 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.

In addition to the above, *note LoggerAdapter: c91. supports the
following methods of *note Logger: 3ac.: *note debug(): 715, *note
info(): 208d, *note warning(): 208f, *note error(): 2090, *note
exception(): 713, *note critical(): 714, *note log(): 712, *note
isEnabledFor(): 208a, *note getEffectiveLevel(): 2089, *note setLevel():
2087. and *note hasHandlers(): 2099.  These methods have the same
signatures as their counterparts in *note Logger: 3ac, so you can use
the two types of instances interchangeably.

3.2 版更變: The *note isEnabledFor(): 208a, *note getEffectiveLevel():
2089, *note setLevel(): 2087. and *note hasHandlers(): 2099. methods
were added to *note LoggerAdapter: c91.  These methods delegate to the
underlying logger.


File: python.info,  Node: Thread Safety,  Next: Module-Level Functions,  Prev: LoggerAdapter Objects,  Up: logging --- Logging facility for Python

5.16.6.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: eb. module, you may not be able to use logging from within such
handlers.  This is because lock implementations in the *note threading:
10a. 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 --- Logging facility for Python

5.16.6.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 a logger which is 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.

     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: 3ac. class, or the last
     class passed to *note setLoggerClass(): 20ca.  This function may be
     called from within a new class definition, to ensure that
     installing a customized *note Logger: 3ac. 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: 90b.

     3.2 版新加入: This function has been provided, along with *note
     setLogRecordFactory(): 20c0, to allow developers more control over
     how the *note LogRecord: 90b. representing a logging event is
     constructed.

     See *note setLogRecordFactory(): 20c0. for more information about
     the how the factory is called.

 -- 函式: logging.debug (msg, *args, **kwargs)

     Logs a message with level ‘DEBUG’ on the root 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.)

     There are three keyword arguments in `kwargs' which are inspected:
     `exc_info' which, if it does not evaluate as false, causes
     exception information to be added to the logging message.  If an
     exception tuple (in the format returned by *note sys.exc_info():
     c64.) or an exception instance is provided, it is used; otherwise,
     *note sys.exc_info(): c64. 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 `extra' which can be used to
     pass a dictionary which is used to populate the __dict__ of the
     LogRecord 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)-15s %(clientip)s %(user)-8s %(message)s'
          logging.basicConfig(format=FORMAT)
          d = {'clientip': '192.168.0.1', 'user': 'fbloggs'}
          logging.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 *note Formatter:
     208b. documentation 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: 208b. has been set up with a format string which
     expects ’clientip’ and ’user’ in the attribute dictionary of the
     LogRecord.  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:
     208b.s would be used with particular *note Handler: 208c.s.

     3.2 版更變: The `stack_info' parameter was added.

 -- 函式: logging.info (msg, *args, **kwargs)

     Logs a message with level ‘INFO’ on the root logger.  The arguments
     are interpreted as for *note debug(): 208e.

 -- 函式: logging.warning (msg, *args, **kwargs)

     Logs a message with level ‘WARNING’ on the root logger.  The
     arguments are interpreted as for *note debug(): 208e.

          備註: 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 ‘ERROR’ on the root logger.  The
     arguments are interpreted as for *note debug(): 208e.

 -- 函式: logging.critical (msg, *args, **kwargs)

     Logs a message with level ‘CRITICAL’ on the root logger.  The
     arguments are interpreted as for *note debug(): 208e.

 -- 函式: logging.exception (msg, *args, **kwargs)

     Logs a message with level ‘ERROR’ on the root logger.  The
     arguments are interpreted as for *note debug(): 208e.  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 other
     arguments are interpreted as for *note debug(): 208e.

          備註: The above module-level convenience functions, which
          delegate to the root logger, call *note basicConfig(): 1e1. to
          ensure that at least one handler is available.  Because of
          this, they should `not' be used in threads, in versions of
          Python earlier than 2.7.1 and 3.2, unless at least one handler
          has been added to the root logger `before' the threads are
          started.  In earlier versions of Python, due to a thread
          safety shortcoming in *note basicConfig(): 1e1, this can
          (under rare circumstances) lead to handlers being added
          multiple times to the root logger, which can in turn lead to
          multiple messages for the same event.

 -- 函式: 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: 208b. 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: 20d1.

 -- 函式: logging.getLevelName (level)

     Returns the textual or numeric representation of logging level
     `level'.

     If `level' is one of the predefined levels ‘CRITICAL’, ‘ERROR’,
     ‘WARNING’, ‘INFO’ or ‘DEBUG’ then you get the corresponding string.
     If you have associated levels with names using *note
     addLevelName(): 20d0. 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: 20af.), 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.makeLogRecord (attrdict)

     Creates and returns a new *note LogRecord: 90b. instance whose
     attributes are defined by `attrdict'.  This function is useful for
     taking a pickled *note LogRecord: 90b. attribute dictionary, sent
     over a socket, and reconstituting it as a *note LogRecord: 90b.
     instance at the receiving end.

 -- 函式: logging.basicConfig (**kwargs)

     Does basic configuration for the logging system by creating a *note
     StreamHandler: b7a. with a default *note Formatter: 208b. and
     adding it to the root logger.  The functions *note debug(): 208e,
     *note info(): 20b9, *note warning(): 20cb, *note error(): 20cc. and
     *note critical(): 20cd. will call *note basicConfig(): 1e1.
     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.

     Format             描述
                        
     ---------------------------------------------------------------------
                        
     `filename'         Specifies that a FileHandler be created, using
                        the specified filename, rather than a
                        StreamHandler.
                        
                        
     `filemode'         If `filename' is specified, open the file in
                        this *note mode: 15fb.  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(): b6a.
                        
                        
     `style'            If `format' is specified, use this style for
                        the format string.  One of ‘'%'’, ‘'{'’ or
                        ‘'$'’ for *note printf-style: 122a,
                        *note str.format(): 4df. or
                        *note string.Template: 3f0. respectively.
                        Defaults to ‘'%'’.
                        
                        
     `level'            Set the root logger level to the specified
                        *note level: 2088.
                        
                        
     `stream'           Use the specified stream to initialize the
                        StreamHandler.  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.
                        

     3.2 版更變: The `style' argument was added.

     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 版更變: The `force' argument was added.

 -- 函式: 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: c.), 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 *note __init__():
     d63. such that only a name argument is required, and the *note
     __init__(): d63. 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():
     2085. API to get your loggers.

 -- 函式: logging.setLogRecordFactory (factory)

     Set a callable which is used to create a *note LogRecord: 90b.


     參數: ‘factory’ – The factory callable to be used to instantiate a
     log record.

     3.2 版新加入: This function has been provided, along with *note
     getLogRecordFactory(): 20bf, to allow developers more control over
     how the *note LogRecord: 90b. 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(): 77f, showing the call hierarchy.


          kwargs: Additional keyword arguments.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue28524


File: python.info,  Node: Module-Level Attributes,  Next: Integration with the warnings module,  Prev: Module-Level Functions,  Up: logging --- Logging facility for Python

5.16.6.11 Module-Level Attributes
.................................

 -- 屬性: logging.lastResort

     A "handler of last resort" is available through this attribute.
     This is a *note StreamHandler: b7a. 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 版新加入.


File: python.info,  Node: Integration with the warnings module,  Prev: Module-Level Attributes,  Up: logging --- Logging facility for Python

5.16.6.12 Integration with the warnings module
..............................................

The *note captureWarnings(): 20d5. function can be used to integrate
*note logging: ab. with the *note warnings: 127. 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: 127.
     module will be redirected to the logging system.  Specifically, a
     warning will be formatted using *note warnings.formatwarning():
     ff7. and the resulting string logged to a logger named
     ‘'py.warnings'’ with a severity of ‘WARNING’.

     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: ac.

     Configuration API for the logging module.

Module *note logging.handlers: ad.

     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: ab. 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: ab. package in the standard library.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0282

   (2) https://www.red-dove.com/python_logging.html


File: python.info,  Node: logging config --- Logging configuration,  Next: logging handlers --- Logging handlers,  Prev: logging --- Logging facility for Python,  Up: Generic Operating System Services

5.16.7 ‘logging.config’ — Logging configuration
-----------------------------------------------

`Source code:' Lib/logging/config.py(1)

Important
.........

This page contains only reference information.  For tutorials, please
see

   * *note Basic Tutorial: b77.

   * *note Advanced Tutorial: b78.

   * *note Logging Cookbook: b79.

__________________________________________________________________

This section describes the API for configuring the logging module.

* Menu:

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/logging/config.py


File: python.info,  Node: Configuration functions,  Next: Configuration dictionary schema,  Up: logging config --- Logging configuration

5.16.7.1 Configuration functions
................................

The following functions configure the logging module.  They are located
in the *note logging.config: ac. 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: ab. itself) and
defining handlers which are declared either in *note logging: ab. or
*note logging.handlers: ad.

 -- 函式: logging.config.dictConfig (config)

     Takes the logging configuration from a dictionary.  The contents of
     this dictionary are described in *note Configuration dictionary
     schema: 20d9. below.

     If an error is encountered during configuration, this function will
     raise a *note ValueError: 1fc, *note TypeError: 193, *note
     AttributeError: 3a0. or *note ImportError: 339. 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: ac. 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(): b30. 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 *note __init__(): d63,
     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(): b30. could be called exactly
     as in the default, uncustomized state.

     3.2 版新加入.

 -- 函式: logging.config.fileConfig (fname, defaults=None,
          disable_existing_loggers=True)

     Reads the logging configuration from a *note configparser:
     23.-format file.  The format of the file should be as described in
     *note Configuration file format: 20da.  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).


     參數:

        * ‘fname’ – A filename, or a file-like object, or an instance
          derived from *note RawConfigParser: 876.  If a
          ‘RawConfigParser’-derived instance is passed, it is used as
          is.  Otherwise, a ‘Configparser’ is instantiated, and the
          configuration read by it from the object passed in ‘fname’.
          If that has a *note readline(): df. method, it is assumed to
          be a file-like object and read using *note read_file(): 1e60.;
          otherwise, it is assumed to be a filename and passed to *note
          read(): 10a9.

        * ‘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.

     3.4 版更變: An instance of a subclass of *note RawConfigParser:
     876. 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’.

 -- 函式: 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():
     b30. or *note fileConfig(): 3ae.  Returns a *note Thread: 236.
     instance on which you can call *note start(): 20db. to start the
     server, and which you can *note join(): b65. when appropriate.  To
     stop the server, call *note stopListening(): 20dc.

     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(): b95, 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(): 877.  Specifically, if the process calling *note
          listen(): 877. 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(): 877. 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():
          877. to prevent unrecognised configurations from being
          applied.

     3.4 版更變: The ‘verify’ argument was added.

          備註: 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(): b30. 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(): 877.  This is typically called before calling ‘join()’ on
     the return value from *note listen(): 877.


File: python.info,  Node: Configuration dictionary schema,  Next: Configuration file format,  Prev: Configuration functions,  Up: logging config --- Logging configuration

5.16.7.2 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: ab. 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: 20de. below.

* Menu:

* Dictionary Schema Details::
* Incremental Configuration::
* Object connections::
* User-defined objects::
* Access to external objects::
* Access to internal objects::
* Import resolution and custom importers::


File: python.info,  Node: Dictionary Schema Details,  Next: Incremental Configuration,  Up: Configuration dictionary schema

5.16.7.3 Dictionary Schema Details
..................................

The dictionary passed to *note dictConfig(): b30. 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: 20e0. 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: 208b. instance.

     The configuring dict is searched for keys ‘format’ and ‘datefmt’
     (with defaults of ‘None’) and these are used to construct a *note
     Formatter: 208b. instance.

     3.8 版更變: a ‘validate’ key (with default of ‘True’) can be added
     into the ‘formatters’ section of the configuring dict, this is to
     validate the format.

   * `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: b7c. 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.

     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: b7a, using ‘sys.stdout’ as the underlying
     stream.  The handler with id ‘file’ is instantiated as a *note
     logging.handlers.RotatingFileHandler: 20e1. 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.

        * ‘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(): 3ae. API.

     If the specified value is ‘True’, the configuration is processed as
     described in the section on *note Incremental Configuration: 20e2.

   * `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(): 3ae.  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.7.4 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.7.5 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: Access to external objects,  Prev: Object connections,  Up: Configuration dictionary schema

5.16.7.6 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: 208b. 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: 208b. initialized with those two format
strings.  Shown in Python source form, the ‘brief’ and ‘default’
formatters have configuration sub-dictionaries:

     {
       'format' : '%(message)s'
     }

and:

     {
       '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: 208b. 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 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.


File: python.info,  Node: Access to external objects,  Next: Access to internal objects,  Prev: User-defined objects,  Up: Configuration dictionary schema

5.16.7.7 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.7.8 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: ab. module.  For example,
consider *note logging.handlers.MemoryHandler: 20ea, 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.  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,  Prev: Access to internal objects,  Up: Configuration dictionary schema

5.16.7.9 Import resolution and custom importers
...............................................

Import resolution, by default, uses the builtin *note __import__(): 615.
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(): 1da.  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(): 1da. if you’re setting
the import callable on a configurator `instance'.


File: python.info,  Node: Configuration file format,  Prev: Configuration dictionary schema,  Up: logging config --- Logging configuration

5.16.7.10 Configuration file format
...................................

The configuration file format understood by *note fileConfig(): 3ae. is
based on *note configparser: 23. 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(): 3ae. API is older than the *note
     dictConfig(): b30. API and does not provide functionality to cover
     certain aspects of logging.  For example, you cannot configure
     *note Filter: b7c. objects, which provide for filtering of messages
     beyond simple integer levels, using *note fileConfig(): 3ae.  If
     you need to have instances of *note Filter: b7c. in your logging
     configuration, you will need to use *note dictConfig(): b30.  Note
     that future enhancements to configuration functionality will be
     added to *note dictConfig(): b30, 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 eval(): b95.uated 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(): b95. 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 eval(): b95.uated 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 eval(): b95.uated 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
     datefmt=
     class=logging.Formatter

The ‘format’ entry is the overall format string, and the ‘datefmt’ entry
is the ‘strftime()’-compatible date/time format string.  If empty, the
package substitutes something which is almost equivalent to specifying
the date format string ‘'%Y-%m-%d %H:%M:%S'’.  This format also
specifies milliseconds, which are appended to the result of using the
above format string, with a comma separator.  An example time in this
format is ‘2003-01-23 00:29:50,411’.

The ‘class’ entry is optional.  It indicates the name of the formatter’s
class (as a dotted module and class name.)  This option is useful for
instantiating a *note Formatter: 208b. subclass.  Subclasses of *note
Formatter: 208b. can present exception tracebacks in an expanded or
condensed format.

     備註: Due to the use of *note eval(): b95. as described above,
     there are potential security risks which result from using the
     *note listen(): 877. 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():
     877. documentation for more information.

也參考
......

Module *note logging: ab.

     API reference for the logging module.

Module *note logging.handlers: ad.

     Useful handlers included with the logging module.


File: python.info,  Node: logging handlers --- Logging handlers,  Next: getpass --- Portable password input,  Prev: logging config --- Logging configuration,  Up: Generic Operating System Services

5.16.8 ‘logging.handlers’ — Logging handlers
--------------------------------------------

`Source code:' Lib/logging/handlers.py(1)

Important
.........

This page contains only reference information.  For tutorials, please
see

   * *note Basic Tutorial: b77.

   * *note Advanced Tutorial: b78.

   * *note Logging Cookbook: b79.

__________________________________________________________________

The following useful handlers are provided in the package.  Note that
three of the handlers (*note StreamHandler: b7a, *note FileHandler:
20f0. and *note NullHandler: c21.) are actually defined in the *note
logging: ab. 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.8/Lib/logging/handlers.py


File: python.info,  Node: StreamHandler,  Next: FileHandler,  Up: logging handlers --- Logging handlers

5.16.8.1 StreamHandler
......................

The *note StreamHandler: b7a. class, located in the core *note logging:
ab. 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: b7a. 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 with a terminator.
          If exception information is present, it is formatted using
          *note traceback.print_exception(): 20b5. and appended to the
          stream.

      -- 成員函式: flush ()

          Flushes the stream by calling its *note flush(): 20f4. method.
          Note that the ‘close()’ method is inherited from *note
          Handler: 208c. and so does no output, so an explicit *note
          flush(): 20f4. 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 版新加入.

3.2 版更變: The ‘StreamHandler’ class now has a ‘terminator’ attribute,
default value ‘'\n'’, which is used as the terminator when writing a
formatted record to a stream.  If you don’t want this newline
termination, you can set the handler instance’s ‘terminator’ attribute
to the empty string.  In earlier versions, the terminator was hardcoded
as ‘'\n'’.


File: python.info,  Node: FileHandler,  Next: NullHandler,  Prev: StreamHandler,  Up: logging handlers --- Logging handlers

5.16.8.2 FileHandler
....................

The *note FileHandler: 20f0. class, located in the core *note logging:
ab. package, sends logging output to a disk file.  It inherits the
output functionality from *note StreamHandler: b7a.

 -- 類別: logging.FileHandler (filename, mode='a', encoding=None,
          delay=False)

     Returns a new instance of the *note FileHandler: 20f0. 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(): 20f7.  By default, the file grows indefinitely.

     3.6 版更變: As well as string values, *note Path: 202. objects are
     also accepted for the `filename' argument.

      -- 成員函式: close ()

          Closes the file.

      -- 成員函式: emit (record)

          Outputs the record to the file.


File: python.info,  Node: NullHandler,  Next: WatchedFileHandler,  Prev: FileHandler,  Up: logging handlers --- Logging handlers

5.16.8.3 NullHandler
....................

3.1 版新加入.

The *note NullHandler: c21. class, located in the core *note logging:
ab. 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: c21. 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: 20fe. for more information
on how to use *note NullHandler: c21.


File: python.info,  Node: WatchedFileHandler,  Next: BaseRotatingHandler,  Prev: NullHandler,  Up: logging handlers --- Logging handlers

5.16.8.4 WatchedFileHandler
...........................

The *note WatchedFileHandler: 2101. class, located in the *note
logging.handlers: ad. 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(): 1f2.
always returns zero for this value.

 -- 類別: logging.handlers.WatchedFileHandler (filename, mode='a',
          encoding=None, delay=False)

     Returns a new instance of the *note WatchedFileHandler: 2101.
     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(): 2102.  By default, the file grows indefinitely.

     3.6 版更變: As well as string values, *note Path: 202. objects are
     also accepted for the `filename' argument.

      -- 成員函式: 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(): 567. to reopen the file if it has changed.


File: python.info,  Node: BaseRotatingHandler,  Next: RotatingFileHandler,  Prev: WatchedFileHandler,  Up: logging handlers --- Logging handlers

5.16.8.5 BaseRotatingHandler
............................

The *note BaseRotatingHandler: 2105. class, located in the *note
logging.handlers: ad. module, is the base class for the rotating file
handlers, *note RotatingFileHandler: 20e1. and *note
TimedRotatingFileHandler: 873.  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)

     The parameters are as for ‘FileHandler’.  The attributes are:

      -- 屬性: namer

          If this attribute is set to a callable, the *note
          rotation_filename(): 2107. method delegates to this callable.
          The parameters passed to the callable are those passed to
          *note rotation_filename(): 2107.

               備註: 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.

          3.3 版新加入.

      -- 屬性: rotator

          If this attribute is set to a callable, the *note rotate():
          2109. method delegates to this callable.  The parameters
          passed to the callable are those passed to *note rotate():
          2109.

          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:
20e1. and *note TimedRotatingFileHandler: 873.  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: 210a.


File: python.info,  Node: RotatingFileHandler,  Next: TimedRotatingFileHandler,  Prev: BaseRotatingHandler,  Up: logging handlers --- Logging handlers

5.16.8.6 RotatingFileHandler
............................

The *note RotatingFileHandler: 20e1. class, located in the *note
logging.handlers: ad. module, supports rotation of disk log files.

 -- 類別: logging.handlers.RotatingFileHandler (filename, mode='a',
          maxBytes=0, backupCount=0, encoding=None, delay=False)

     Returns a new instance of the *note RotatingFileHandler: 20e1.
     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(): 210d.  By default, the file grows indefinitely.

     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: 202. objects are
     also accepted for the `filename' argument.

      -- 成員函式: 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 --- Logging handlers

5.16.8.7 TimedRotatingFileHandler
.................................

The *note TimedRotatingFileHandler: 873. class, located in the *note
logging.handlers: ad. 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)

     Returns a new instance of the *note TimedRotatingFileHandler: 873.
     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(): 2111.

     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.

          備註: 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' parameter was added.

     3.6 版更變: As well as string values, *note Path: 202. objects are
     also accepted for the `filename' argument.

      -- 成員函式: doRollover ()

          Does a rollover, as described above.

      -- 成員函式: emit (record)

          Outputs the record to the file, catering for rollover as
          described above.


File: python.info,  Node: SocketHandler,  Next: DatagramHandler,  Prev: TimedRotatingFileHandler,  Up: logging handlers --- Logging handlers

5.16.8.8 SocketHandler
......................

The *note SocketHandler: 874. class, located in the *note
logging.handlers: ad. 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: 874. 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: 90b,
          use the *note makeLogRecord(): 20bd. function.

      -- 成員函式: handleError ()

          Handles an error which has occurred during *note emit(): 2116.
          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: c8f.).

      -- 成員函式: 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(): 2119.

          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 --- Logging handlers

5.16.8.9 DatagramHandler
........................

The *note DatagramHandler: 875. class, located in the *note
logging.handlers: ad. module, inherits from *note SocketHandler: 874. to
support sending logging messages over UDP sockets.

 -- 類別: logging.handlers.DatagramHandler (host, port)

     Returns a new instance of the *note DatagramHandler: 875. 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 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: 90b, use the *note
          makeLogRecord(): 20bd. function.

      -- 成員函式: makeSocket ()

          The factory method of *note SocketHandler: 874. is here
          overridden to create a UDP socket (*note socket.SOCK_DGRAM:
          c8e.).

      -- 成員函式: 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(): 2119.


File: python.info,  Node: SysLogHandler,  Next: NTEventLogHandler,  Prev: DatagramHandler,  Up: logging handlers --- Logging handlers

5.16.8.10 SysLogHandler
.......................

The *note SysLogHandler: a23. class, located in the *note
logging.handlers: ad. 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: a23. 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:
     c8e. 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: c8f.

     Note that if your server is not listening on UDP port 514, *note
     SysLogHandler: a23. 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.

     3.2 版更變: `socktype' was added.

      -- 成員函式: close ()

          Closes the socket to the remote host.

      -- 成員函式: 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(1).)  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(2)).  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(3).)  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:
          a23. and mirror the values defined in the ‘sys/syslog.h’
          header file.

          `Priorities'

          Name (string)                  Symbolic value
                                         
          ---------------------------------------------------
                                         
          ‘alert’                        LOG_ALERT
                                         
                                         
          ‘crit’ or ‘critical’           LOG_CRIT
                                         
                                         
          ‘debug’                        LOG_DEBUG
                                         
                                         
          ‘emerg’ or ‘panic’             LOG_EMERG
                                         
                                         
          ‘err’ or ‘error’               LOG_ERR
                                         
                                         
          ‘info’                         LOG_INFO
                                         
                                         
          ‘notice’                       LOG_NOTICE
                                         
                                         
          ‘warn’ or ‘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://bugs.python.org/issue12168

   (2) https://tools.ietf.org/html/rfc5424.html

   (3) https://bugs.python.org/issue12419


File: python.info,  Node: NTEventLogHandler,  Next: SMTPHandler,  Prev: SysLogHandler,  Up: logging handlers --- Logging handlers

5.16.8.11 NTEventLogHandler
...........................

The *note NTEventLogHandler: 2129. class, located in the *note
logging.handlers: ad. 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: 2129. 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
          *note __init__(): d63. 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 --- Logging handlers

5.16.8.12 SMTPHandler
.....................

The *note SMTPHandler: 2131. class, located in the *note
logging.handlers: ad. 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: 2131. 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(): a89.
     method.)

     A timeout can be specified for communication with the SMTP server
     using the `timeout' argument.

     3.3 版新加入: The `timeout' argument was added.

      -- 成員函式: 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 --- Logging handlers

5.16.8.13 MemoryHandler
.......................

The *note MemoryHandler: 20ea. class, located in the *note
logging.handlers: ad. 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: 20ea. is a subclass of the more general *note
BufferingHandler: 2136, 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():
          2138. returns true, call *note flush(): 2139. to process the
          buffer.

      -- 成員函式: flush ()

          You can override this to implement custom flushing behavior.
          This version just zaps the buffer to empty.

      -- 成員函式: 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: 20ea. 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(): 213a. 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 版更變: The `flushOnClose' parameter was added.

      -- 成員函式: close ()

          Calls *note flush(): 213c, sets the target to ‘None’ and
          clears the buffer.

      -- 成員函式: flush ()

          For a *note MemoryHandler: 20ea, flushing means just sending
          the buffered records to the target, if there is one.  The
          buffer is also cleared when this happens.  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 --- Logging handlers

5.16.8.14 HTTPHandler
.....................

The *note HTTPHandler: 716. class, located in the *note
logging.handlers: ad. 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: 716. 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: 3e9.
     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 版更變: The `context' parameter was added.

      -- 成員函式: 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:
          90b. 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(): 2140. 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(): 20a2. to specify a *note Formatter: 208b. for
          a *note HTTPHandler: 716. has no effect.  Instead of calling
          *note format(): 20ac, this handler calls *note mapLogRecord():
          2140. and then *note urllib.parse.urlencode(): 790. 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 --- Logging handlers

5.16.8.15 QueueHandler
......................

3.2 版新加入.

The *note QueueHandler: 2144. class, located in the *note
logging.handlers: ad. module, supports sending logging messages to a
queue, such as those implemented in the *note queue: db. or *note
multiprocessing: b8. modules.

Along with the *note QueueListener: 717. class, *note QueueHandler:
2144. 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: 2131.)
are done on a separate thread.

 -- 類別: logging.handlers.QueueHandler (queue)

     Returns a new instance of the *note QueueHandler: 2144. 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(): 2145. 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: 3cb. instances for
     `queue'.

      -- 成員函式: 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(): 20aa. method is called to handle the
          error.  This can result in the record silently being dropped
          (if ‘logging.raiseExceptions’ is ‘False’) or a message printed
          to ‘sys.stderr’ (if ‘logging.raiseExceptions’ 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, and exception information, if present.  It
          also removes unpickleable items from the record in-place.

          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.

      -- 成員函式: 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.


File: python.info,  Node: QueueListener,  Prev: QueueHandler,  Up: logging handlers --- Logging handlers

5.16.8.16 QueueListener
.......................

3.2 版新加入.

The *note QueueListener: 717. class, located in the *note
logging.handlers: ad. module, supports receiving logging messages from a
queue, such as those implemented in the *note queue: db. or *note
multiprocessing: b8. 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: 717. is not itself
a handler, it is documented here because it works hand-in-hand with
*note QueueHandler: 2144.

Along with the *note QueueHandler: 2144. class, *note QueueListener:
717. 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: 2131.) are done on a
separate thread.

 -- 類別: logging.handlers.QueueListener (queue, *handlers,
          respect_handler_level=False)

     Returns a new instance of the *note QueueListener: 717. 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(): 214a. 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: 3cb. instances for `queue'.

     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 版更變: The ‘respect_handler_level’ argument was added.

      -- 成員函式: 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(): 214b.

      -- 成員函式: 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 版新加入.

也參考
......

Module *note logging: ab.

     API reference for the logging module.

Module *note logging.config: ac.

     Configuration API for the logging module.


File: python.info,  Node: getpass --- Portable password input,  Next: curses --- Terminal handling for character-cell displays,  Prev: logging handlers --- Logging handlers,  Up: Generic Operating System Services

5.16.9 ‘getpass’ — Portable password input
------------------------------------------

`Source code:' Lib/getpass.py(1)

__________________________________________________________________

The *note getpass: 88. module provides two functions:

 -- 函式: getpass.getpass (prompt='Password: ', stream=None)

     Prompt the user for a password without echoing.  The user is
     prompted using the string `prompt', which defaults to ‘'Password:
     '’.  On Unix, the prompt is written to the file-like object
     `stream' using the replace error handler if needed.  `stream'
     defaults to the controlling terminal (‘/dev/tty’) or if that is
     unavailable to ‘sys.stderr’ (this argument is ignored on Windows).

     If echo free input is unavailable getpass() falls back to printing
     a warning message to `stream' and reading from ‘sys.stdin’ and
     issuing a *note GetPassWarning: 2153.

          備註: If you call getpass from within IDLE, the input may be
          done in the terminal you launched IDLE from rather than the
          idle window itself.

 -- 例外: getpass.GetPassWarning

     A *note UserWarning: 1720. subclass issued when password input may
     be echoed.

 -- 函式: getpass.getuser ()

     Return the "login name" of the user.

     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: d7. module, otherwise, an exception is
     raised.

     In general, this function should be preferred over *note
     os.getlogin(): 1ef4.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/getpass.py


File: python.info,  Node: curses --- Terminal handling for character-cell displays,  Next: curses textpad --- Text input widget for curses programs,  Prev: getpass --- Portable password input,  Up: Generic Operating System Services

5.16.10 ‘curses’ — Terminal handling for character-cell displays
----------------------------------------------------------------

__________________________________________________________________

The *note curses: 2c. 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.

     備註: 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.

     備註: Since version 5.4, the ncurses library decides how to
     interpret non-ASCII data using the ‘nl_langinfo’ function.  That
     means that you have to call *note locale.setlocale(): 200f. in the
     application and encode Unicode strings using one of the system’s
     available encodings.  This example uses the system’s default
     encoding:

          import locale
          locale.setlocale(locale.LC_ALL, '')
          code = locale.getpreferredencoding()

     Then use `code' as the encoding for *note str.encode(): c3c. calls.

也參考
......

Module *note curses.ascii: 2d.

     Utilities for working with ASCII characters, regardless of your
     locale settings.

Module *note curses.panel: 2e.

     A panel stack extension that adds depth to curses windows.

Module *note curses.textpad: 2f.

     Editable text widget for curses supporting ‘Emacs’-like bindings.

*note Curses Programming with Python: 2156.

     Tutorial material on using curses with Python, by Andrew Kuchling
     and Eric Raymond.

The Tools/demo/(1) directory in the Python source distribution contains
some example programs using the curses bindings provided by this module.

* Menu:

* Functions: Functions<3>.
* Window Objects::
* Constants: Constants<6>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Tools/demo/


File: python.info,  Node: Functions<3>,  Next: Window Objects,  Up: curses --- Terminal handling for character-cell displays

5.16.10.1 Functions
...................

The module *note curses: 2c. 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 ‘A_NORMAL’.

The module *note curses: 2c. 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(): 215e. then *note cbreak(): 215d. 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 ‘A_STANDOUT’, ‘A_REVERSE’, and
     the other ‘A_*’ attributes.  *note pair_number(): 2161. 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(): 2164. 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(): 2166. 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(): 2168. ground updates the physical screen to match
     the virtual screen.

     The virtual screen may be updated by a *note noutrefresh(): 2169.
     call after write operations such as *note addstr(): 216a. have been
     performed on a window.  The normal *note refresh(): 216b. 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(): 216f. routine, if used, must be called before
     *note initscr(): 2170. 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(): 215b.

 -- 函式: 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(): 2174. returns ‘KEY_MOUSE’ 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 4:
     ‘BUTTONn_PRESSED’, ‘BUTTONn_RELEASED’, ‘BUTTONn_CLICKED’,
     ‘BUTTONn_DOUBLE_CLICKED’, ‘BUTTONn_TRIPLE_CLICKED’, ‘BUTTON_SHIFT’,
     ‘BUTTON_CTRL’, ‘BUTTON_ALT’.

 -- 函式: curses.getsyx ()

     Return the current coordinates of the virtual screen cursor as a
     tuple ‘(y, x)’.  If *note leaveok: 2176. is currently ‘True’, then
     return ‘(-1, -1)’.

 -- 函式: curses.getwin (file)

     Read window related data stored in the file by an earlier
     ‘putwin()’ 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_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(): 217d. 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(): 217e. 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(): 215c.
     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(): 2180, ‘-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: 2181. 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(): 2183. would modify the window
     structure, ‘False’ otherwise.

 -- 函式: curses.isendwin ()

     Return ‘True’ if *note endwin(): 216d. 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(): 2170.

 -- 函式: 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
     msec, 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(): 216b. and
     *note noutrefresh(): 2169. 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: 2181, 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(): 2160. 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(): 2194. always goes to standard output.

 -- 函式: curses.qiflush ([flag])

     If `flag' is ‘False’, the effect is the same as calling *note
     noqiflush(): 2191.  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(): 2163.

 -- 函式: curses.reset_shell_mode ()

     Restore the terminal to "shell" mode, as previously saved by *note
     def_shell_mode(): 2165.

 -- 函式: curses.resetty ()

     Restore the state of the terminal modes to what it was at the last
     call to *note savetty(): 2197.

 -- 函式: curses.resize_term (nlines, ncols)

     Backend function used by *note resizeterm(): 2198, performing most
     of the work; when resizing the windows, *note resize_term(): 2183.
     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(): 2196.

 -- 函式: curses.setsyx (y, x)

     Set the virtual screen cursor to `y', `x'.  If `y' and `x' are both
     ‘-1’, then *note leaveok: 2176. 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(): 2170.

     *note start_color(): 219b. initializes eight basic colors (black,
     red, green, yellow, blue, magenta, cyan, and white), and two global
     variables in the *note curses: 2c. module, ‘COLORS’ and
     ‘COLOR_PAIRS’, 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(): 2174. will return it.

          備註: Only one `ch' can be pushed before ‘getch()’ is called.

 -- 函式: curses.update_lines_cols ()

     Update ‘LINES’ and ‘COLS’.  Useful for detecting manual screen
     resize.

     3.5 版新加入.

 -- 函式: curses.unget_wch (ch)

     Push `ch' so the next *note get_wch(): 9e4. 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 ‘KEY_MOUSE’ 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():
     2170. 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, ...)

     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<6>,  Prev: Functions<3>,  Up: curses --- Terminal handling for character-cell displays

5.16.10.2 Window Objects
........................

Window objects, as returned by *note initscr(): 2170. and *note
newwin(): 218d. 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: 2159.  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: 2159.  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(): 216a. with a `str' that has
               embedded newlines.  Instead, call *note addstr(): 216a.
               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:

     Parameter       描述                      Default value
                                               
     ----------------------------------------------------------------------
                                               
     `ls'            Left side                 ‘ACS_VLINE’
                                               
                                               
     `rs'            Right side                ‘ACS_VLINE’
                                               
                                               
     `ts'            Top                       ‘ACS_HLINE’
                                               
                                               
     `bs'            Bottom                    ‘ACS_HLINE’
                                               
                                               
     `tl'            Upper-left corner         ‘ACS_ULCORNER’
                                               
                                               
     `tr'            Upper-right corner        ‘ACS_URCORNER’
                                               
                                               
     `bl'            Bottom-left corner        ‘ACS_LLCORNER’
                                               
                                               
     `br'            Bottom-right corner       ‘ACS_LRCORNER’
                                               

 -- 成員函式: window.box ([vertch, horch])

     Similar to *note border(): 21af, 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(): 21b2. method so that the contents will be
     redisplayed by the next window refresh.

 -- 成員函式: window.clear ()

     Like *note erase(): 21b4, but also cause the whole window to be
     repainted upon next call to *note refresh(): 216b.

 -- 成員函式: window.clearok (flag)

     If `flag' is ‘True’, the next call to *note refresh(): 216b. 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():
     21b7. 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(): 21bb. is the
     same as calling *note subwin(): 21bc, 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(): 216b. 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.

 -- 屬性: 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(): 21bc.  By default, the locale encoding is used
     (see *note locale.getpreferredencoding(): 3aa.).

     3.3 版新加入.

 -- 成員函式: window.erase ()

     Clear the window.

 -- 成員函式: window.getbegyx ()

     Return a tuple ‘(y, x)’ of co-ordinates 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(): 2174. 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: 2c. 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(): 216b. 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(): 21d0. 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(): 216b.; otherwise return ‘False’.  Raise a
     *note curses.error: 2159. 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(): 216b.; 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: 2c.
     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(): 2174. 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(): 2168.

 -- 成員函式: 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(): 21d9. 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(): 21da. 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(): 2177. 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(): 216b. call.

 -- 成員函式: window.redrawwin ()

     Touch the entire window, causing it to be completely redrawn on the
     next *note refresh(): 216b. 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(): 218c.  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(): 21ae.)
     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(): 21c8.

 -- 成員函式: 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():
     216b, so it should almost never be necessary to call it manually.

 -- 成員函式: window.syncok (flag)

     If `flag' is ‘True’, then *note syncup(): 21e7. 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(): 2174. will return ‘-1’ if no input
     is waiting.  If `delay' is positive, then *note getch(): 2174. 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(): 216b.

 -- 成員函式: window.vline (ch, n)

 -- 成員函式: window.vline (y, x, ch, n)

     Display a vertical line starting at ‘(y, x)’ with length `n'
     consisting of the character `ch'.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue35924


File: python.info,  Node: Constants<6>,  Prev: Window Objects,  Up: curses --- Terminal handling for character-cell displays

5.16.10.3 Constants
...................

The *note curses: 2c. module defines the following data members:

 -- Data: curses.ERR

     Some curses routines that return an integer, such as *note getch():
     2174, return *note ERR: 21ed. upon failure.

 -- Data: curses.OK

     Some curses routines that return an integer, such as *note napms():
     218b, return *note OK: 21ee. upon success.

 -- Data: curses.version

     A bytes object representing the current version of the module.
     Also available as ‘__version__’.

 -- Data: 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 版新加入.

Some constants are available to specify character cell attributes.  The
exact constants available are system dependent.

Attribute              Meaning
                       
-----------------------------------------------------------
                       
‘A_ALTCHARSET’         Alternate character set mode
                       
                       
‘A_BLINK’              Blink mode
                       
                       
‘A_BOLD’               Bold mode
                       
                       
‘A_DIM’                Dim mode
                       
                       
‘A_INVIS’              Invisible or blank mode
                       
                       
‘A_ITALIC’             Italic mode
                       
                       
‘A_NORMAL’             Normal attribute
                       
                       
‘A_PROTECT’            Protected mode
                       
                       
‘A_REVERSE’            Reverse background and foreground
                       colors
                       
                       
‘A_STANDOUT’           Standout mode
                       
                       
‘A_UNDERLINE’          Underline mode
                       
                       
‘A_HORIZONTAL’         Horizontal highlight
                       
                       
‘A_LEFT’               Left highlight
                       
                       
‘A_LOW’                Low highlight
                       
                       
‘A_RIGHT’              Right highlight
                       
                       
‘A_TOP’                Top highlight
                       
                       
‘A_VERTICAL’           Vertical highlight
                       
                       
‘A_CHARTEXT’           Bit-mask to extract a character
                       

3.7 版新加入: ‘A_ITALIC’ was added.

Several constants are available to extract corresponding attributes
returned by some methods.

Bit-mask               Meaning
                       
-----------------------------------------------------------
                       
‘A_ATTRIBUTES’         Bit-mask to extract attributes
                       
                       
‘A_CHARTEXT’           Bit-mask to extract a character
                       
                       
‘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
                        
-------------------------------------------------------------------------
                        
‘KEY_MIN’               Minimum key value
                        
                        
‘KEY_BREAK’             Break key (unreliable)
                        
                        
‘KEY_DOWN’              Down-arrow
                        
                        
‘KEY_UP’                Up-arrow
                        
                        
‘KEY_LEFT’              Left-arrow
                        
                        
‘KEY_RIGHT’             Right-arrow
                        
                        
‘KEY_HOME’              Home key (upward+left arrow)
                        
                        
‘KEY_BACKSPACE’         Backspace (unreliable)
                        
                        
‘KEY_F0’                Function keys.  Up to 64 function keys are
                        supported.
                        
                        
‘KEY_Fn’                Value of function key `n'
                        
                        
‘KEY_DL’                Delete line
                        
                        
‘KEY_IL’                Insert line
                        
                        
‘KEY_DC’                Delete character
                        
                        
‘KEY_IC’                Insert char or enter insert mode
                        
                        
‘KEY_EIC’               Exit insert char mode
                        
                        
‘KEY_CLEAR’             Clear screen
                        
                        
‘KEY_EOS’               Clear to end of screen
                        
                        
‘KEY_EOL’               Clear to end of line
                        
                        
‘KEY_SF’                Scroll 1 line forward
                        
                        
‘KEY_SR’                Scroll 1 line backward (reverse)
                        
                        
‘KEY_NPAGE’             Next page
                        
                        
‘KEY_PPAGE’             Previous page
                        
                        
‘KEY_STAB’              Set tab
                        
                        
‘KEY_CTAB’              Clear tab
                        
                        
‘KEY_CATAB’             Clear all tabs
                        
                        
‘KEY_ENTER’             Enter or send (unreliable)
                        
                        
‘KEY_SRESET’            Soft (partial) reset (unreliable)
                        
                        
‘KEY_RESET’             Reset or hard reset (unreliable)
                        
                        
‘KEY_PRINT’             Print
                        
                        
‘KEY_LL’                Home down or bottom (lower left)
                        
                        
‘KEY_A1’                Upper left of keypad
                        
                        
‘KEY_A3’                Upper right of keypad
                        
                        
‘KEY_B2’                Center of keypad
                        
                        
‘KEY_C1’                Lower left of keypad
                        
                        
‘KEY_C3’                Lower right of keypad
                        
                        
‘KEY_BTAB’              Back tab
                        
                        
‘KEY_BEG’               Beg (beginning)
                        
                        
‘KEY_CANCEL’            Cancel
                        
                        
‘KEY_CLOSE’             Close
                        
                        
‘KEY_COMMAND’           Cmd (command)
                        
                        
‘KEY_COPY’              Copy
                        
                        
‘KEY_CREATE’            Create
                        
                        
‘KEY_END’               End
                        
                        
‘KEY_EXIT’              Exit
                        
                        
‘KEY_FIND’              Find
                        
                        
‘KEY_HELP’              Help
                        
                        
‘KEY_MARK’              Mark
                        
                        
‘KEY_MESSAGE’           Message
                        
                        
‘KEY_MOVE’              Move
                        
                        
‘KEY_NEXT’              Next
                        
                        
‘KEY_OPEN’              Open
                        
                        
‘KEY_OPTIONS’           Options
                        
                        
‘KEY_PREVIOUS’          Prev (previous)
                        
                        
‘KEY_REDO’              Redo
                        
                        
‘KEY_REFERENCE’         Ref (reference)
                        
                        
‘KEY_REFRESH’           Refresh
                        
                        
‘KEY_REPLACE’           Replace
                        
                        
‘KEY_RESTART’           Restart
                        
                        
‘KEY_RESUME’            Resume
                        
                        
‘KEY_SAVE’              Save
                        
                        
‘KEY_SBEG’              Shifted Beg (beginning)
                        
                        
‘KEY_SCANCEL’           Shifted Cancel
                        
                        
‘KEY_SCOMMAND’          Shifted Command
                        
                        
‘KEY_SCOPY’             Shifted Copy
                        
                        
‘KEY_SCREATE’           Shifted Create
                        
                        
‘KEY_SDC’               Shifted Delete char
                        
                        
‘KEY_SDL’               Shifted Delete line
                        
                        
‘KEY_SELECT’            Select
                        
                        
‘KEY_SEND’              Shifted End
                        
                        
‘KEY_SEOL’              Shifted Clear line
                        
                        
‘KEY_SEXIT’             Shifted Exit
                        
                        
‘KEY_SFIND’             Shifted Find
                        
                        
‘KEY_SHELP’             Shifted Help
                        
                        
‘KEY_SHOME’             Shifted Home
                        
                        
‘KEY_SIC’               Shifted Input
                        
                        
‘KEY_SLEFT’             Shifted Left arrow
                        
                        
‘KEY_SMESSAGE’          Shifted Message
                        
                        
‘KEY_SMOVE’             Shifted Move
                        
                        
‘KEY_SNEXT’             Shifted Next
                        
                        
‘KEY_SOPTIONS’          Shifted Options
                        
                        
‘KEY_SPREVIOUS’         Shifted Prev
                        
                        
‘KEY_SPRINT’            Shifted Print
                        
                        
‘KEY_SREDO’             Shifted Redo
                        
                        
‘KEY_SREPLACE’          Shifted Replace
                        
                        
‘KEY_SRIGHT’            Shifted Right arrow
                        
                        
‘KEY_SRSUME’            Shifted Resume
                        
                        
‘KEY_SSAVE’             Shifted Save
                        
                        
‘KEY_SSUSPEND’          Shifted Suspend
                        
                        
‘KEY_SUNDO’             Shifted Undo
                        
                        
‘KEY_SUSPEND’           Suspend
                        
                        
‘KEY_UNDO’              Undo
                        
                        
‘KEY_MOUSE’             Mouse event has occurred
                        
                        
‘KEY_RESIZE’            Terminal resize event
                        
                        
‘KEY_MAX’               Maximum key value
                        

On VT100s and their software emulations, such as X terminal emulators,
there are normally at least four function keys (‘KEY_F1’, ‘KEY_F2’,
‘KEY_F3’, ‘KEY_F4’) available, and the arrow keys mapped to ‘KEY_UP’,
‘KEY_DOWN’, ‘KEY_LEFT’ and ‘KEY_RIGHT’ 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(): 2170. has
     been called.

ACS code               Meaning
                       
----------------------------------------------------------------------
                       
‘ACS_BBSS’             alternate name for upper right corner
                       
                       
‘ACS_BLOCK’            solid square block
                       
                       
‘ACS_BOARD’            board of squares
                       
                       
‘ACS_BSBS’             alternate name for horizontal line
                       
                       
‘ACS_BSSB’             alternate name for upper left corner
                       
                       
‘ACS_BSSS’             alternate name for top tee
                       
                       
‘ACS_BTEE’             bottom tee
                       
                       
‘ACS_BULLET’           bullet
                       
                       
‘ACS_CKBOARD’          checker board (stipple)
                       
                       
‘ACS_DARROW’           arrow pointing down
                       
                       
‘ACS_DEGREE’           degree symbol
                       
                       
‘ACS_DIAMOND’          diamond
                       
                       
‘ACS_GEQUAL’           greater-than-or-equal-to
                       
                       
‘ACS_HLINE’            horizontal line
                       
                       
‘ACS_LANTERN’          lantern symbol
                       
                       
‘ACS_LARROW’           left arrow
                       
                       
‘ACS_LEQUAL’           less-than-or-equal-to
                       
                       
‘ACS_LLCORNER’         lower left-hand corner
                       
                       
‘ACS_LRCORNER’         lower right-hand corner
                       
                       
‘ACS_LTEE’             left tee
                       
                       
‘ACS_NEQUAL’           not-equal sign
                       
                       
‘ACS_PI’               letter pi
                       
                       
‘ACS_PLMINUS’          plus-or-minus sign
                       
                       
‘ACS_PLUS’             big plus sign
                       
                       
‘ACS_RARROW’           right arrow
                       
                       
‘ACS_RTEE’             right tee
                       
                       
‘ACS_S1’               scan line 1
                       
                       
‘ACS_S3’               scan line 3
                       
                       
‘ACS_S7’               scan line 7
                       
                       
‘ACS_S9’               scan line 9
                       
                       
‘ACS_SBBS’             alternate name for lower right corner
                       
                       
‘ACS_SBSB’             alternate name for vertical line
                       
                       
‘ACS_SBSS’             alternate name for right tee
                       
                       
‘ACS_SSBB’             alternate name for lower left corner
                       
                       
‘ACS_SSBS’             alternate name for bottom tee
                       
                       
‘ACS_SSSB’             alternate name for left tee
                       
                       
‘ACS_SSSS’             alternate name for crossover or big plus
                       
                       
‘ACS_STERLING’         pound sterling
                       
                       
‘ACS_TTEE’             top tee
                       
                       
‘ACS_UARROW’           up arrow
                       
                       
‘ACS_ULCORNER’         upper left corner
                       
                       
‘ACS_URCORNER’         upper right corner
                       
                       
‘ACS_VLINE’            vertical line
                       

The following table lists the predefined colors:

Constant                Color
                        
---------------------------------------------------------
                        
‘COLOR_BLACK’           Black
                        
                        
‘COLOR_BLUE’            Blue
                        
                        
‘COLOR_CYAN’            Cyan (light greenish blue)
                        
                        
‘COLOR_GREEN’           Green
                        
                        
‘COLOR_MAGENTA’         Magenta (purplish red)
                        
                        
‘COLOR_RED’             Red
                        
                        
‘COLOR_WHITE’           White
                        
                        
‘COLOR_YELLOW’          Yellow
                        


File: python.info,  Node: curses textpad --- Text input widget for curses programs,  Next: curses ascii --- Utilities for ASCII characters,  Prev: curses --- Terminal handling for character-cell displays,  Up: Generic Operating System Services

5.16.11 ‘curses.textpad’ — Text input widget for curses programs
----------------------------------------------------------------

The *note curses.textpad: 2f. module provides a *note Textbox: 21f1.
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: 2f. 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.11.1 Textbox objects
.........................

You can instantiate a *note Textbox: 21f1. object as follows:

 -- 類別: curses.textpad.Textbox (win)

     Return a textbox widget object.  The `win' argument should be a
     curses *note window: 2181. 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: 21f5. flag
     is initially on.

     *note Textbox: 21f1. 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: 21f5. 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
                                       
          ----------------------------------------------------
                                       
          ‘KEY_LEFT’                   ‘Control-B’
                                       
                                       
          ‘KEY_RIGHT’                  ‘Control-F’
                                       
                                       
          ‘KEY_UP’                     ‘Control-P’
                                       
                                       
          ‘KEY_DOWN’                   ‘Control-N’
                                       
                                       
          ‘KEY_BACKSPACE’              ‘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:
          21f5. 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 --- Utilities for ASCII characters,  Next: curses panel --- A panel stack extension for curses,  Prev: curses textpad --- Text input widget for curses programs,  Up: Generic Operating System Services

5.16.12 ‘curses.ascii’ — Utilities for ASCII characters
-------------------------------------------------------

__________________________________________________________________

The *note curses.ascii: 2d. 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:

Name               Meaning
                   
----------------------------------------------------------------------
                   
‘NUL’

‘SOH’              Start of heading, console interrupt
                   
                   
‘STX’              Start of text
                   
                   
‘ETX’              End of text
                   
                   
‘EOT’              End of transmission
                   
                   
‘ENQ’              Enquiry, goes with ‘ACK’ flow control
                   
                   
‘ACK’              Acknowledgement
                   
                   
‘BEL’              Bell
                   
                   
‘BS’               Backspace
                   
                   
‘TAB’              Tab
                   
                   
‘HT’               Alias for ‘TAB’: "Horizontal tab"
                   
                   
‘LF’               Line feed
                   
                   
‘NL’               Alias for ‘LF’: "New line"
                   
                   
‘VT’               Vertical tab
                   
                   
‘FF’               Form feed
                   
                   
‘CR’               Carriage return
                   
                   
‘SO’               Shift-out, begin alternate character set
                   
                   
‘SI’               Shift-in, resume default character set
                   
                   
‘DLE’              Data-link escape
                   
                   
‘DC1’              XON, for flow control
                   
                   
‘DC2’              Device control 2, block-mode flow control
                   
                   
‘DC3’              XOFF, for flow control
                   
                   
‘DC4’              Device control 4
                   
                   
‘NAK’              Negative acknowledgement
                   
                   
‘SYN’              Synchronous idle
                   
                   
‘ETB’              End transmission block
                   
                   
‘CAN’              Cancel
                   
                   
‘EM’               End of medium
                   
                   
‘SUB’              Substitute
                   
                   
‘ESC’              Escape
                   
                   
‘FS’               File separator
                   
                   
‘GS’               Group separator
                   
                   
‘RS’               Record separator, block-mode terminator
                   
                   
‘US’               Unit separator
                   
                   
‘SP’               Space
                   
                   
‘DEL’              Delete
                   

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(): 142c.

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.

 -- Data: 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.


File: python.info,  Node: curses panel --- A panel stack extension for curses,  Next: platform --- Access to underlying platform's identifying data,  Prev: curses ascii --- Utilities for ASCII characters,  Up: Generic Operating System Services

5.16.13 ‘curses.panel’ — A panel stack extension for 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:

* Functions: Functions<4>.
* Panel Objects::


File: python.info,  Node: Functions<4>,  Next: Panel Objects,  Up: curses panel --- A panel stack extension for curses

5.16.13.1 Functions
...................

The module *note curses.panel: 2e. 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(): 2168, so you’ll have to do
     this yourself.


File: python.info,  Node: Panel Objects,  Prev: Functions<4>,  Up: curses panel --- A panel stack extension for curses

5.16.13.2 Panel Objects
.......................

Panel objects, as returned by *note new_panel(): 2214. 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 --- Access to underlying platform's identifying data,  Next: errno --- Standard errno system symbols,  Prev: curses panel --- A panel stack extension for curses,  Up: Generic Operating System Services

5.16.14 ‘platform’ — Access to underlying platform’s identifying data
---------------------------------------------------------------------

`Source code:' Lib/platform.py(1)

__________________________________________________________________

     備註: Specific platforms listed alphabetically, with Linux included
     in the Unix section.

* Menu:

* Cross Platform::
* Java Platform::
* Windows Platform::
* Mac OS Platform::
* Unix Platforms::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/platform.py


File: python.info,  Node: Cross Platform,  Next: Java Platform,  Up: platform --- Access to underlying platform's identifying data

5.16.14.1 Cross Platform
........................

 -- 函式: platform.architecture (executable=sys.executable, bits='',
          linkage='')

     Queries the given executable (defaults to the Python interpreter
     binary) for various architecture information.

     Returns a tuple ‘(bits, linkage)’ which contain information about
     the bit architecture and the linkage format used for the
     executable.  Both values are returned as strings.

     Values that cannot be determined are returned as given by the
     parameter presets.  If bits is given as ‘''’, the ‘sizeof(pointer)’
     (or ‘sizeof(long)’ on Python version < 1.5.2) is used as indicator
     for the supported pointer size.

     The function relies on the system’s ‘file’ command to do the actual
     work.  This is available on most if not all Unix platforms and some
     non-Unix platforms and then only if the executable points to the
     Python interpreter.  Reasonable defaults are used when the above
     needs are not met.

          備註: On Mac OS X (and perhaps other platforms), executable
          files may be universal files containing multiple
          architectures.

          To get at the "64-bitness" of the current interpreter, it is
          more reliable to query the *note sys.maxsize: b48. attribute:

               is_64bits = sys.maxsize > 2**32

 -- 函式: platform.machine ()

     Returns the machine type, e.g.  ‘'i386'’.  An empty string is
     returned if the value cannot be determined.

 -- 函式: platform.node ()

     Returns the computer’s network name (may not be fully qualified!).
     An empty string is returned if the value cannot be determined.

 -- 函式: platform.platform (aliased=0, terse=0)

     Returns a single string identifying the underlying platform with as
     much useful information as possible.

     The output is intended to be `human readable' rather than machine
     parseable.  It may look different on different platforms and this
     is intended.

     If `aliased' is true, the function will use aliases for various
     platforms that report system names which differ from their common
     names, for example SunOS will be reported as Solaris.  The *note
     system_alias(): 222a. function is used to implement this.

     Setting `terse' to true causes the function to return only the
     absolute minimum information needed to identify the platform.

     3.8 版更變: On macOS, the function now uses *note mac_ver(): 1021,
     if it returns a non-empty release string, to get the macOS version
     rather than the darwin version.

 -- 函式: platform.processor ()

     Returns the (real) processor name, e.g.  ‘'amdk6'’.

     An empty string is returned if the value cannot be determined.
     Note that many platforms do not provide this information or simply
     return the same value as for *note machine(): 2228.  NetBSD does
     this.

 -- 函式: platform.python_build ()

     Returns a tuple ‘(buildno, builddate)’ stating the Python build
     number and date as strings.

 -- 函式: platform.python_compiler ()

     Returns a string identifying the compiler used for compiling
     Python.

 -- 函式: platform.python_branch ()

     Returns a string identifying the Python implementation SCM branch.

 -- 函式: platform.python_implementation ()

     Returns a string identifying the Python implementation.  Possible
     return values are: ’CPython’, ’IronPython’, ’Jython’, ’PyPy’.

 -- 函式: platform.python_revision ()

     Returns a string identifying the Python implementation SCM
     revision.

 -- 函式: platform.python_version ()

     Returns the Python version as string ‘'major.minor.patchlevel'’.

     Note that unlike the Python ‘sys.version’, the returned value will
     always include the patchlevel (it defaults to 0).

 -- 函式: platform.python_version_tuple ()

     Returns the Python version as tuple ‘(major, minor, patchlevel)’ of
     strings.

     Note that unlike the Python ‘sys.version’, the returned value will
     always include the patchlevel (it defaults to ‘'0'’).

 -- 函式: platform.release ()

     Returns the system’s release, e.g.  ‘'2.2.0'’ or ‘'NT'’ An empty
     string is returned if the value cannot be determined.

 -- 函式: platform.system ()

     Returns the system/OS name, such as ‘'Linux'’, ‘'Darwin'’,
     ‘'Java'’, ‘'Windows'’.  An empty string is returned if the value
     cannot be determined.

 -- 函式: platform.system_alias (system, release, version)

     Returns ‘(system, release, version)’ aliased to common marketing
     names used for some systems.  It also does some reordering of the
     information in some cases where it would otherwise cause confusion.

 -- 函式: platform.version ()

     Returns the system’s release version, e.g.  ‘'#3 on degas'’.  An
     empty string is returned if the value cannot be determined.

 -- 函式: platform.uname ()

     Fairly portable uname interface.  Returns a *note namedtuple():
     1b8. containing six attributes: *note system: 2234, *note node:
     2229, *note release: 2233, *note version: 2235, *note machine:
     2228, and *note processor: 222b.

     Note that this adds a sixth attribute (*note processor: 222b.) not
     present in the *note os.uname(): a62. result.  Also, the attribute
     names are different for the first two attributes; *note os.uname():
     a62. names them ‘sysname’ and ‘nodename’.

     Entries which cannot be determined are set to ‘''’.

     3.3 版更變: Result changed from a tuple to a namedtuple.


File: python.info,  Node: Java Platform,  Next: Windows Platform,  Prev: Cross Platform,  Up: platform --- Access to underlying platform's identifying data

5.16.14.2 Java Platform
.......................

 -- 函式: platform.java_ver (release='', vendor='', vminfo=('', '', ''),
          osinfo=('', '', ''))

     Version interface for Jython.

     Returns a tuple ‘(release, vendor, vminfo, osinfo)’ with `vminfo'
     being a tuple ‘(vm_name, vm_release, vm_vendor)’ and `osinfo' being
     a tuple ‘(os_name, os_version, os_arch)’.  Values which cannot be
     determined are set to the defaults given as parameters (which all
     default to ‘''’).


File: python.info,  Node: Windows Platform,  Next: Mac OS Platform,  Prev: Java Platform,  Up: platform --- Access to underlying platform's identifying data

5.16.14.3 Windows Platform
..........................

 -- 函式: platform.win32_ver (release='', version='', csd='', ptype='')

     Get additional version information from the Windows Registry and
     return a tuple ‘(release, version, csd, ptype)’ referring to OS
     release, version number, CSD level (service pack) and OS type
     (multi/single processor).

     As a hint: `ptype' is ‘'Uniprocessor Free'’ on single processor NT
     machines and ‘'Multiprocessor Free'’ on multi processor machines.
     The `’Free’' refers to the OS version being free of debugging code.
     It could also state `’Checked’' which means the OS version uses
     debugging code, i.e.  code that checks arguments, ranges, etc.

 -- 函式: platform.win32_edition ()

     Returns a string representing the current Windows edition.
     Possible values include but are not limited to ‘'Enterprise'’,
     ‘'IoTUAP'’, ‘'ServerStandard'’, and ‘'nanoserver'’.

     3.8 版新加入.

 -- 函式: platform.win32_is_iot ()

     Return ‘True’ if the Windows edition returned by *note
     win32_edition(): 2239. is recognized as an IoT edition.

     3.8 版新加入.


File: python.info,  Node: Mac OS Platform,  Next: Unix Platforms,  Prev: Windows Platform,  Up: platform --- Access to underlying platform's identifying data

5.16.14.4 Mac OS Platform
.........................

 -- 函式: platform.mac_ver (release='', versioninfo=('', '', ''),
          machine='')

     Get Mac OS version information and return it as tuple ‘(release,
     versioninfo, machine)’ with `versioninfo' being a tuple ‘(version,
     dev_stage, non_release_version)’.

     Entries which cannot be determined are set to ‘''’.  All tuple
     entries are strings.


File: python.info,  Node: Unix Platforms,  Prev: Mac OS Platform,  Up: platform --- Access to underlying platform's identifying data

5.16.14.5 Unix Platforms
........................

 -- 函式: platform.libc_ver (executable=sys.executable, lib='',
          version='', chunksize=16384)

     Tries to determine the libc version against which the file
     executable (defaults to the Python interpreter) is linked.  Returns
     a tuple of strings ‘(lib, version)’ which default to the given
     parameters in case the lookup fails.

     Note that this function has intimate knowledge of how different
     libc versions add symbols to the executable is probably only usable
     for executables compiled using ‘gcc’.

     The file is read and scanned in chunks of `chunksize' bytes.


File: python.info,  Node: errno --- Standard errno system symbols,  Next: ctypes --- A foreign function library for Python,  Prev: platform --- Access to underlying platform's identifying data,  Up: Generic Operating System Services

5.16.15 ‘errno’ — Standard errno system symbols
-----------------------------------------------

__________________________________________________________________

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
pretty all-inclusive.

 -- Data: 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(): 1f08.

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:

 -- Data: errno.EPERM

     Operation not permitted

 -- Data: errno.ENOENT

     No such file or directory

 -- Data: errno.ESRCH

     No such process

 -- Data: errno.EINTR

     Interrupted system call.

     也參考
     ......

     This error is mapped to the exception *note InterruptedError: 65e.

 -- Data: errno.EIO

     I/O error

 -- Data: errno.ENXIO

     No such device or address

 -- Data: errno.E2BIG

     Arg list too long

 -- Data: errno.ENOEXEC

     Exec format error

 -- Data: errno.EBADF

     Bad file number

 -- Data: errno.ECHILD

     No child processes

 -- Data: errno.EAGAIN

     Try again

 -- Data: errno.ENOMEM

     Out of memory

 -- Data: errno.EACCES

     Permission denied

 -- Data: errno.EFAULT

     Bad address

 -- Data: errno.ENOTBLK

     Block device required

 -- Data: errno.EBUSY

     Device or resource busy

 -- Data: errno.EEXIST

     File exists

 -- Data: errno.EXDEV

     Cross-device link

 -- Data: errno.ENODEV

     No such device

 -- Data: errno.ENOTDIR

     Not a directory

 -- Data: errno.EISDIR

     Is a directory

 -- Data: errno.EINVAL

     Invalid argument

 -- Data: errno.ENFILE

     File table overflow

 -- Data: errno.EMFILE

     Too many open files

 -- Data: errno.ENOTTY

     Not a typewriter

 -- Data: errno.ETXTBSY

     Text file busy

 -- Data: errno.EFBIG

     File too large

 -- Data: errno.ENOSPC

     No space left on device

 -- Data: errno.ESPIPE

     Illegal seek

 -- Data: errno.EROFS

     Read-only file system

 -- Data: errno.EMLINK

     Too many links

 -- Data: errno.EPIPE

     Broken pipe

 -- Data: errno.EDOM

     Math argument out of domain of func

 -- Data: errno.ERANGE

     Math result not representable

 -- Data: errno.EDEADLK

     Resource deadlock would occur

 -- Data: errno.ENAMETOOLONG

     File name too long

 -- Data: errno.ENOLCK

     No record locks available

 -- Data: errno.ENOSYS

     Function not implemented

 -- Data: errno.ENOTEMPTY

     Directory not empty

 -- Data: errno.ELOOP

     Too many symbolic links encountered

 -- Data: errno.EWOULDBLOCK

     Operation would block

 -- Data: errno.ENOMSG

     No message of desired type

 -- Data: errno.EIDRM

     Identifier removed

 -- Data: errno.ECHRNG

     Channel number out of range

 -- Data: errno.EL2NSYNC

     Level 2 not synchronized

 -- Data: errno.EL3HLT

     Level 3 halted

 -- Data: errno.EL3RST

     Level 3 reset

 -- Data: errno.ELNRNG

     Link number out of range

 -- Data: errno.EUNATCH

     Protocol driver not attached

 -- Data: errno.ENOCSI

     No CSI structure available

 -- Data: errno.EL2HLT

     Level 2 halted

 -- Data: errno.EBADE

     Invalid exchange

 -- Data: errno.EBADR

     Invalid request descriptor

 -- Data: errno.EXFULL

     Exchange full

 -- Data: errno.ENOANO

     No anode

 -- Data: errno.EBADRQC

     Invalid request code

 -- Data: errno.EBADSLT

     Invalid slot

 -- Data: errno.EDEADLOCK

     File locking deadlock error

 -- Data: errno.EBFONT

     Bad font file format

 -- Data: errno.ENOSTR

     Device not a stream

 -- Data: errno.ENODATA

     No data available

 -- Data: errno.ETIME

     Timer expired

 -- Data: errno.ENOSR

     Out of streams resources

 -- Data: errno.ENONET

     Machine is not on the network

 -- Data: errno.ENOPKG

     Package not installed

 -- Data: errno.EREMOTE

     Object is remote

 -- Data: errno.ENOLINK

     Link has been severed

 -- Data: errno.EADV

     Advertise error

 -- Data: errno.ESRMNT

     Srmount error

 -- Data: errno.ECOMM

     Communication error on send

 -- Data: errno.EPROTO

     Protocol error

 -- Data: errno.EMULTIHOP

     Multihop attempted

 -- Data: errno.EDOTDOT

     RFS specific error

 -- Data: errno.EBADMSG

     Not a data message

 -- Data: errno.EOVERFLOW

     Value too large for defined data type

 -- Data: errno.ENOTUNIQ

     Name not unique on network

 -- Data: errno.EBADFD

     File descriptor in bad state

 -- Data: errno.EREMCHG

     Remote address changed

 -- Data: errno.ELIBACC

     Can not access a needed shared library

 -- Data: errno.ELIBBAD

     Accessing a corrupted shared library

 -- Data: errno.ELIBSCN

     .lib section in a.out corrupted

 -- Data: errno.ELIBMAX

     Attempting to link in too many shared libraries

 -- Data: errno.ELIBEXEC

     Cannot exec a shared library directly

 -- Data: errno.EILSEQ

     Illegal byte sequence

 -- Data: errno.ERESTART

     Interrupted system call should be restarted

 -- Data: errno.ESTRPIPE

     Streams pipe error

 -- Data: errno.EUSERS

     Too many users

 -- Data: errno.ENOTSOCK

     Socket operation on non-socket

 -- Data: errno.EDESTADDRREQ

     Destination address required

 -- Data: errno.EMSGSIZE

     Message too long

 -- Data: errno.EPROTOTYPE

     Protocol wrong type for socket

 -- Data: errno.ENOPROTOOPT

     Protocol not available

 -- Data: errno.EPROTONOSUPPORT

     Protocol not supported

 -- Data: errno.ESOCKTNOSUPPORT

     Socket type not supported

 -- Data: errno.EOPNOTSUPP

     Operation not supported on transport endpoint

 -- Data: errno.EPFNOSUPPORT

     Protocol family not supported

 -- Data: errno.EAFNOSUPPORT

     Address family not supported by protocol

 -- Data: errno.EADDRINUSE

     Address already in use

 -- Data: errno.EADDRNOTAVAIL

     Cannot assign requested address

 -- Data: errno.ENETDOWN

     Network is down

 -- Data: errno.ENETUNREACH

     Network is unreachable

 -- Data: errno.ENETRESET

     Network dropped connection because of reset

 -- Data: errno.ECONNABORTED

     Software caused connection abort

 -- Data: errno.ECONNRESET

     Connection reset by peer

 -- Data: errno.ENOBUFS

     No buffer space available

 -- Data: errno.EISCONN

     Transport endpoint is already connected

 -- Data: errno.ENOTCONN

     Transport endpoint is not connected

 -- Data: errno.ESHUTDOWN

     Cannot send after transport endpoint shutdown

 -- Data: errno.ETOOMANYREFS

     Too many references: cannot splice

 -- Data: errno.ETIMEDOUT

     Connection timed out

 -- Data: errno.ECONNREFUSED

     Connection refused

 -- Data: errno.EHOSTDOWN

     Host is down

 -- Data: errno.EHOSTUNREACH

     No route to host

 -- Data: errno.EALREADY

     Operation already in progress

 -- Data: errno.EINPROGRESS

     Operation now in progress

 -- Data: errno.ESTALE

     Stale NFS file handle

 -- Data: errno.EUCLEAN

     Structure needs cleaning

 -- Data: errno.ENOTNAM

     Not a XENIX named type file

 -- Data: errno.ENAVAIL

     No XENIX semaphores available

 -- Data: errno.EISNAM

     Is a named type file

 -- Data: errno.EREMOTEIO

     Remote I/O error

 -- Data: errno.EDQUOT

     Quota exceeded


File: python.info,  Node: ctypes --- A foreign function library for Python,  Prev: errno --- Standard errno system symbols,  Up: Generic Operating System Services

5.16.16 ‘ctypes’ — A foreign function library for Python
--------------------------------------------------------

__________________________________________________________________

*note ctypes: 2b. 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 tutorial::
* ctypes reference::


File: python.info,  Node: ctypes tutorial,  Next: ctypes reference,  Up: ctypes --- A foreign function library for Python

5.16.16.1 ctypes tutorial
.........................

Note: The code samples in this tutorial use *note doctest: 67. to make
sure that they actually work.  Since some code samples behave
differently under Linux, Windows, or Mac OS X, they contain doctest
directives in comments.

Note: Some code samples reference the ctypes *note c_int: 22b9. type.
On platforms where ‘sizeof(long) == sizeof(int)’ it is an alias to *note
c_long: 22ba.  So, you should not be confused if *note c_long: 22ba. is
printed if you would expect *note c_int: 22b9. — they are actually the
same type.

* Menu:

* Loading dynamic link libraries::
* Accessing functions from loaded dlls::
* Calling functions::
* Fundamental data types::
* Calling functions, continued: Calling functions continued.
* 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::
* Callback functions::
* 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 tutorial

5.16.16.2 Loading dynamic link libraries
........................................

*note ctypes: 2b. 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:
1d4. exception when the function call fails.

3.3 版更變: Windows errors used to raise *note WindowsError: 999, which
is now an alias of *note OSError: 1d4.

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 ‘LoadLibrary()’ 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: Calling functions,  Prev: Loading dynamic link libraries,  Up: ctypes tutorial

5.16.16.3 Accessing functions from loaded dlls
..............................................

Functions are accessed as attributes of dll objects:

     >>> from ctypes import *
     >>> 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 an ‘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 version */
     HMODULE GetModuleHandleA(LPCSTR lpModuleName);
     /* UNICODE version */
     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(): 44d. 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: Calling functions,  Next: Fundamental data types,  Prev: Accessing functions from loaded dlls,  Up: ctypes tutorial

5.16.16.4 Calling functions
...........................

You can call these functions like any other Python callable.  This
example uses the ‘time()’ function, which returns system time in seconds
since the Unix epoch, and the ‘GetModuleHandleA()’ function, which
returns a win32 module handle.

This example calls both functions with a ‘NULL’ pointer (‘None’ should
be used as the ‘NULL’ pointer):

     >>> print(libc.time(None))
     1150640792
     >>> print(hex(windll.kernel32.GetModuleHandleA(None)))
     0x1d000000
     >>>

*note ValueError: 1fc. 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: 2b. 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: 2b,
so you should be careful anyway.  The *note faulthandler: 7d. 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
platforms 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: 2b. data types.


File: python.info,  Node: Fundamental data types,  Next: Calling functions continued,  Prev: Calling functions,  Up: ctypes tutorial

5.16.16.5 Fundamental data types
................................

*note ctypes: 2b. defines a number of primitive C compatible data types:

ctypes type                C type                                         Python type
                                                                          
-----------------------------------------------------------------------------------------------------------
                                                                          
*note c_bool: 22c3.        ‘_Bool’                                        bool (1)
                                                                          
                                                                          
*note c_char: 22c4.        ‘char’                                         1-character bytes object
                                                                          
                                                                          
*note c_wchar: 22c5.       ‘wchar_t’                                      1-character string
                                                                          
                                                                          
*note c_byte: 22c6.        ‘char’                                         int
                                                                          
                                                                          
*note c_ubyte: 22c7.       ‘unsigned char’                                int
                                                                          
                                                                          
*note c_short: 22c8.       ‘short’                                        int
                                                                          
                                                                          
*note c_ushort: 22c9.      ‘unsigned short’                               int
                                                                          
                                                                          
*note c_int: 22b9.         ‘int’                                          int
                                                                          
                                                                          
*note c_uint: 22ca.        ‘unsigned int’                                 int
                                                                          
                                                                          
*note c_long: 22ba.        ‘long’                                         int
                                                                          
                                                                          
*note c_ulong: 22cb.       ‘unsigned long’                                int
                                                                          
                                                                          
*note c_longlong: 22cc.    ‘__int64’ or ‘long long’                       int
                                                                          
                                                                          
*note c_ulonglong: 22cd.   ‘unsigned __int64’ or ‘unsigned long long’     int
                                                                          
                                                                          
*note c_size_t: 22ce.      ‘size_t’                                       int
                                                                          
                                                                          
*note c_ssize_t: bd6.      ‘ssize_t’ or ‘Py_ssize_t’                      int
                                                                          
                                                                          
*note c_float: 22cf.       ‘float’                                        float
                                                                          
                                                                          
*note c_double: eb6.       ‘double’                                       float
                                                                          
                                                                          
*note c_longdouble: eb7.   ‘long double’                                  float
                                                                          
                                                                          
*note c_char_p: 22d0.      ‘char *’ (NUL terminated)                      bytes object or ‘None’
                                                                          
                                                                          
*note c_wchar_p: e9e.      ‘wchar_t *’ (NUL terminated)                   string or ‘None’
                                                                          
                                                                          
*note c_void_p: 22d1.      ‘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:
22d0, *note c_wchar_p: e9e, and *note c_void_p: 22d1. 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(): 22d2. 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(): 22d2. function replaces the
‘c_buffer()’ function (which is still available as an alias), as well as
the ‘c_string()’ function from earlier ctypes releases.  To create a
mutable memory block containing unicode characters of the C type
‘wchar_t’ use the *note create_unicode_buffer(): fb2. function.


File: python.info,  Node: Calling functions continued,  Next: Calling functions with your own custom data types,  Prev: Fundamental data types,  Up: ctypes tutorial

5.16.16.6 Calling functions, continued
......................................

Note that printf prints to the real standard output channel, `not' to
*note sys.stdout: 313, 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>
     ArgumentError: argument 2: exceptions.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: 2b. 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 functions with your own custom data types,  Next: Specifying the required argument types function prototypes,  Prev: Calling functions continued,  Up: ctypes tutorial

5.16.16.7 Calling functions with your own custom data types
...........................................................

You can also customize *note ctypes: 2b. argument conversion to allow
instances of your own classes be used as function arguments.  *note
ctypes: 2b. looks for an ‘_as_parameter_’ attribute and uses this as the
function argument.  Of course, it must be one of integer, string, or
bytes:

     >>> 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: 1d8. 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 tutorial

5.16.16.8 Specifying the required argument types (function prototypes)
......................................................................

It is possible to specify the required argument types of functions
exported from DLLs by setting the ‘argtypes’ attribute.

‘argtypes’ 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>
     ArgumentError: argument 2: exceptions.TypeError: wrong type
     >>> 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 ‘from_param()’ class method for them to be able
to use them in the ‘argtypes’ sequence.  The ‘from_param()’ 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:
2b. 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 tutorial

5.16.16.9 Return types
......................

By default functions are assumed to return the C ‘int’ type.  Other
return types can be specified by setting the ‘restype’ attribute of the
function object.

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 ‘ord("x")’ calls above, you can set the
‘argtypes’ 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")
     'def'
     >>> strchr(b"abcdef", b"def")
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
     ArgumentError: argument 2: exceptions.TypeError: one character string expected
     >>> print(strchr(b"abcdef", b"x"))
     None
     >>> strchr(b"abcdef", b"d")
     'def'
     >>>

You can also use a callable Python object (a function or a class for
example) as the ‘restype’ 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(): 22db. to retrieve it.

Please note that a much more powerful error checking mechanism is
available through the ‘errcheck’ 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 tutorial

5.16.16.10 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: 2b. exports the *note byref(): 22de. function which is
used to pass parameters by reference.  The same effect can be achieved
with the *note pointer(): 22df. function, although *note pointer():
22df. does a lot more work since it constructs a real pointer object, so
it is faster to use *note byref(): 22de. 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 tutorial

5.16.16.11 Structures and unions
................................

Structures and unions must derive from the *note Structure: 22e2. and
*note Union: 22e3. base classes which are defined in the *note ctypes:
2b. module.  Each subclass must define a ‘_fields_’ 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: 2b. type like *note c_int: 22b9,
or any other derived *note ctypes: 2b. 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: 160b.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: 2b. 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 tutorial

5.16.16.12 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 ‘_pack_’ 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.

*note ctypes: 2b. 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: 22e6, *note LittleEndianStructure: 22e7,
‘BigEndianUnion’, and ‘LittleEndianUnion’ 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 tutorial

5.16.16.13 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 ‘_fields_’ 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 tutorial

5.16.16.14 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 tutorial

5.16.16.15 Pointers
...................

Pointer instances are created by calling the *note pointer(): 22df.
function on a *note ctypes: 2b. type:

     >>> from ctypes import *
     >>> i = c_int(42)
     >>> pi = pointer(i)
     >>>

Pointer instances have a *note contents: 22ee. attribute which returns
the object to which the pointer points, the ‘i’ object above:

     >>> pi.contents
     c_long(42)
     >>>

Note that *note ctypes: 2b. 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: 22b9. 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(): 22df. function does more than
simply create pointer instances, it has to create pointer `types' first.
This is done with the *note POINTER(): 22ef. function, which accepts any
*note ctypes: 2b. 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: 2b. 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 tutorial

5.16.16.16 Type conversions
...........................

Usually, ctypes does strict type checking.  This means, if you have
‘POINTER(c_int)’ in the ‘argtypes’ 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 ‘argtypes’, an object of the
pointed type (‘c_int’ in this case) can be passed to the function.
ctypes will apply the required *note byref(): 22de. 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: 2b. provides a *note cast():
1018. function which can be used in the same way.  The ‘Bar’ structure
defined above accepts ‘POINTER(c_int)’ pointers or *note c_int: 22b9.
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(): 1018. function is handy.

The *note cast(): 1018. function can be used to cast a ctypes instance
into a pointer to a different ctypes data type.  *note cast(): 1018.
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(): 1018. 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: Callback functions,  Prev: Type conversions,  Up: ctypes tutorial

5.16.16.17 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: 2b, we can define the ‘cell’ class and set the
‘_fields_’ 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: Callback functions,  Next: Accessing values exported from dlls,  Prev: Incomplete Types,  Up: ctypes tutorial

5.16.16.18 Callback functions
.............................

*note ctypes: 2b. 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(): 22f6. factory function creates types for callback
functions using the ‘cdecl’ calling convention.  On Windows, the *note
WINFUNCTYPE(): 22f7. 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)
     >>>

The result:

     >>> 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(): 22f6.
     objects as long as they are used from C code.  *note ctypes: 2b.
     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: 22f8. 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: Callback functions,  Up: ctypes tutorial

5.16.16.19 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_OptimizeFlag: 22fb, an integer set to 0, 1, or 2, depending on the
*note -O: 690. or *note -OO: 691. flag given on startup.

*note ctypes: 2b. can access values like this with the ‘in_dll()’ class
methods of the type.  `pythonapi' is a predefined symbol giving access
to the Python C api:

     >>> opt_flag = c_int.in_dll(pythonapi, "Py_OptimizeFlag")
     >>> print(opt_flag)
     c_long(0)
     >>>

If the interpreter would have been started with *note -O: 690, the
sample would have printed ‘c_long(1)’, or ‘c_long(2)’ if *note -OO: 691.
would have been specified.

An extended example which also demonstrates the use of pointers accesses
the *note PyImport_FrozenModules: 22fc. pointer exported by Python.

Quoting the docs for that value:

     This pointer is initialized to point to an array of ‘struct
     _frozen’ 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:
2b.:

     >>> from ctypes import *
     >>>
     >>> class struct_frozen(Structure):
     ...     _fields_ = [("name", c_char_p),
     ...                 ("code", POINTER(c_ubyte)),
     ...                 ("size", c_int)]
     ...
     >>>

We have defined the ‘struct _frozen’ data type, so we can get the
pointer to the table:

     >>> FrozenTable = POINTER(struct_frozen)
     >>> table = FrozenTable.in_dll(pythonapi, "PyImport_FrozenModules")
     >>>

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
     __hello__ 161
     __phello__ -161
     __phello__.spam 161
     >>>

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 tutorial

5.16.16.20 Surprises
....................

There are some edges in *note ctypes: 2b. 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: 22d0. 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: 160b.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 tutorial

5.16.16.21 Variable-sized data types
....................................

*note ctypes: 2b. provides some support for variable-sized arrays and
structures.

The *note resize(): 2301. 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: 1fc. 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: 2b. 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 tutorial,  Up: ctypes --- A foreign function library for Python

5.16.16.22 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.16.23 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 ‘find_library()’ 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.

 -- Data: 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, ‘find_library()’ 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.

Here are some examples:

     >>> 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 OS X, ‘find_library()’ tries several predefined 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, ‘find_library()’ 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: 2b, it `may' be better
to determine the shared library name at development time, and hardcode
that into the wrapper module instead of using ‘find_library()’ 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.16.24 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=0)

     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: 1c2. instance may fail even if
     the DLL name exists.  When a dependent DLL of the loaded DLL is not
     found, a *note OSError: 1d4. 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.

也參考
......

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=0)

     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: 2309. code.  *note HRESULT: 2309. 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: 1d4. is automatically
     raised.

     3.3 版更變: *note WindowsError: 999. used to be raised.

 -- 類別: ctypes.WinDLL (name, mode=DEFAULT_MODE, handle=None,
          use_errno=False, use_last_error=False, winmode=0)

     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.

     On Windows CE only the standard calling convention is used, for
     convenience the *note WinDLL: 230a. and *note OleDLL: 2308. use the
     standard calling convention on this platform.

The Python *note global interpreter lock: 50b. 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: 1c2. 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.

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 platforms ‘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)’ 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: 7c. error number in a safe
way.  *note ctypes: 2b. maintains a thread-local copy of the systems
*note errno: 7c. variable; if you call foreign functions created with
‘use_errno=True’ then the *note errno: 7c. 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(): 230c. returns the value of the
ctypes private copy, and the function *note ctypes.set_errno(): 230d.
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(): 22db. and ‘SetLastError()’ Windows API functions; *note
ctypes.get_last_error(): 230e. and *note ctypes.set_last_error(): 230f.
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 to
avoiding 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 版更變: Added `winmode' parameter.

 -- Data: ctypes.RTLD_GLOBAL

     Flag to use as `mode' parameter.  On platforms where this flag is
     not available, it is defined as the integer zero.

 -- Data: ctypes.RTLD_LOCAL

     Flag to use as `mode' parameter.  On platforms where this is not
     available, it is the same as `RTLD_GLOBAL'.

 -- Data: 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")  # On 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: 2312. class,
either by calling the ‘LoadLibrary()’ 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: 1c2, *note PyDLL: 230b, *note WinDLL: 230a, or *note
     OleDLL: 2308. types.

     *note __getattr__(): 31f. 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:

 -- Data: ctypes.cdll

     Creates *note CDLL: 1c2. instances.

 -- Data: ctypes.windll

     Windows only: Creates *note WinDLL: 230a. instances.

 -- Data: ctypes.oledll

     Windows only: Creates *note OleDLL: 2308. instances.

 -- Data: ctypes.pydll

     Creates *note PyDLL: 230b. instances.

For accessing the C Python api directly, a ready-to-use Python shared
library object is available:

 -- Data: ctypes.pythonapi

     An instance of *note PyDLL: 230b. 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: e96. ‘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


File: python.info,  Node: Foreign functions,  Next: Function prototypes,  Prev: Loading shared libraries,  Up: ctypes reference

5.16.16.25 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 *note restype: 2317. and
          assign a callable to the *note errcheck: 2318. 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 ‘from_param()’ class method of the items in the
          *note argtypes: 2319. tuple, this method allows adapting the
          actual argument to an object that the foreign function
          accepts.  For example, a *note c_char_p: 22d0. item in the
          *note argtypes: 2319. 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 ‘from_param()’ 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.seh_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.16.26 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 Callback
functions: 22f5. 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: 7c. variable is exchanged with the
     real *note errno: 7c. 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, except on Windows CE
     where *note WINFUNCTYPE(): 22f7. is the same as *note CFUNCTYPE():
     22f6.  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 ‘argtypes’.

     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.

This 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: 2b.:

     >>> 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: 2b.:

     >>> 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 ‘errcheck’ 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 ‘errcheck’ function returns the argument tuple it receives
unchanged, *note ctypes: 2b. 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.16.27 Utility functions
............................

 -- 函式: ctypes.addressof (obj)

     Returns the address of the memory buffer as integer.  `obj' must be
     an instance of a ctypes type.

     Raises an *note auditing event: e96. ‘ctypes.addressof’ with
     argument ‘obj’.

 -- 函式: 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: 22c4.

     `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.

     Raises an *note auditing event: e96. ‘ctypes.create_string_buffer’
     with arguments ‘init’, ‘size’.

 -- 函式: 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: 22c5.

     `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.

     Raises an *note auditing event: e96. ‘ctypes.create_unicode_buffer’
     with arguments ‘init’, ‘size’.

 -- 函式: 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: 7c. variable in the calling thread.

     Raises an *note auditing event: e96. ‘ctypes.get_errno’ with no
     arguments.

 -- 函式: ctypes.get_last_error ()

     Windows only: returns the current value of the ctypes-private copy
     of the system ‘LastError’ variable in the calling thread.

     Raises an *note auditing event: e96. ‘ctypes.get_last_error’ with
     no arguments.

 -- 函式: 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)

     This factory function creates and returns 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)

     This function creates 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: 7c. variable in the calling thread to `value' and
     return the previous value.

     Raises an *note auditing event: e96. ‘ctypes.set_errno’ with
     argument ‘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.

     Raises an *note auditing event: e96. ‘ctypes.set_last_error’ with
     argument ‘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 (address, size=-1)

     This function returns the C string starting at memory address
     `address' as a bytes object.  If size is specified, it is used as
     size, otherwise the string is assumed to be zero-terminated.

     Raises an *note auditing event: e96. ‘ctypes.string_at’ with
     arguments ‘address’, ‘size’.

 -- 函式: ctypes.WinError (code=None, descr=None)

     Windows only: this function is probably the worst-named thing in
     ctypes.  It creates an instance of OSError.  If `code' is not
     specified, ‘GetLastError’ is called to determine the error code.
     If `descr' is not specified, *note FormatError(): 2325. is called
     to get a textual description of the error.

     3.3 版更變: An instance of *note WindowsError: 999. used to be
     created.

 -- 函式: ctypes.wstring_at (address, size=-1)

     This function returns the wide character string starting at memory
     address `address' as a string.  If `size' is specified, it is used
     as the number of characters of the string, otherwise the string is
     assumed to be zero-terminated.

     Raises an *note auditing event: e96. ‘ctypes.wstring_at’ with
     arguments ‘address’, ‘size’.


File: python.info,  Node: Data types,  Next: Fundamental data types<2>,  Prev: Utility functions,  Up: ctypes reference

5.16.16.28 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(): 2320. helper function.
     Another instance variable is exposed as *note _objects: 232e.; 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: 232f.):

      -- 成員函式: 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: 1fc. is raised.

          Raises an *note auditing event: e96. ‘ctypes.cdata/buffer’
          with arguments ‘pointer’, ‘size’, ‘offset’.

      -- 成員函式: 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: 1fc. is raised.

          Raises an *note auditing event: e96. ‘ctypes.cdata/buffer’
          with arguments ‘pointer’, ‘size’, ‘offset’.

      -- 成員函式: 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: e96. ‘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 ‘argtypes’ 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_: 2335. 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.16.29 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: 2339. is a subclass of *note _CData: 10b5, 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: 2b. 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 ‘restype’ of *note c_char_p: 22d0, you will
always receive a Python bytes object, `not' a *note c_char_p: 22d0.
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:
22d1, 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: eb6.

 -- 類別: 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: 22ba.

 -- 類別: ctypes.c_int8

     Represents the C 8-bit ‘signed int’ datatype.  Usually an alias for
     *note c_byte: 22c6.

 -- 類別: ctypes.c_int16

     Represents the C 16-bit ‘signed int’ datatype.  Usually an alias
     for *note c_short: 22c8.

 -- 類別: ctypes.c_int32

     Represents the C 32-bit ‘signed int’ datatype.  Usually an alias
     for *note c_int: 22b9.

 -- 類別: ctypes.c_int64

     Represents the C 64-bit ‘signed int’ datatype.  Usually an alias
     for *note c_longlong: 22cc.

 -- 類別: 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_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: 22cb.

 -- 類別: ctypes.c_uint8

     Represents the C 8-bit ‘unsigned int’ datatype.  Usually an alias
     for *note c_ubyte: 22c7.

 -- 類別: ctypes.c_uint16

     Represents the C 16-bit ‘unsigned int’ datatype.  Usually an alias
     for *note c_ushort: 22c9.

 -- 類別: ctypes.c_uint32

     Represents the C 32-bit ‘unsigned int’ datatype.  Usually an alias
     for *note c_uint: 22ca.

 -- 類別: ctypes.c_uint64

     Represents the C 64-bit ‘unsigned int’ datatype.  Usually an alias
     for *note c_ulonglong: 22cd.

 -- 類別: 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 *: 4bf. datatype.  Calling this
     without an argument creates a ‘NULL’ *note PyObject *: 4bf.
     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.16.30 Structured data types
................................

 -- 類別: ctypes.Union (*args, **kw)

     Abstract base class for unions in native byte order.

 -- 類別: 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 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_: 2346.
     class variable.  *note ctypes: 2b. will create *note descriptor:
     160b.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: 22b9, 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_: 2346. 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_: 2346. class variable must, however, be
          defined before the type is first used (an instance is created,
          *note sizeof(): 2328. is called on it, and so on).  Later
          assignments to the *note _fields_: 2346. 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_: 2346. 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_: 2347. must
          already be defined when *note _fields_: 2346. is assigned,
          otherwise it will have no effect.

      -- 屬性: _anonymous_

          An optional sequence that lists the names of unnamed
          (anonymous) fields.  *note _anonymous_: 2348. must be already
          defined when *note _fields_: 2346. is assigned, otherwise it
          will have no effect.

          The fields listed in this variable must be structure or union
          type fields.  *note ctypes: 2b. 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_: 2346. 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_:
     2346.  Keyword arguments in the constructor are interpreted as
     attribute assignments, so they will initialize *note _fields_:
     2346. with the same name, or create new attributes for names not
     present in *note _fields_: 2346.


File: python.info,  Node: Arrays and pointers,  Prev: Structured data types,  Up: ctypes reference

5.16.16.31 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: 2b. data type with a positive
     integer.  Alternatively, you can subclass this type and define
     *note _length_: 234b. and *note _type_: 234c. 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: 1011.

      -- 屬性: _length_

          A positive integer specifying the number of elements in the
          array.  Out-of-range subscripts result in an *note IndexError:
          e7a.  Will be returned by *note len(): 151.

      -- 屬性: _type_

          Specifies the type of each element in the array.

     Array subclass constructors accept positional arguments, used to
     initialize the elements in order.

 -- 類別: ctypes._Pointer

     Private, abstract base class for pointers.

     Concrete pointer types are created by calling *note POINTER():
     22ef. with the type that will be pointed to; this is done
     automatically by *note pointer(): 22df.

     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(): 151. will raise *note
     TypeError: 193.  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: Generic Operating System Services,  Up: Python 標準函式庫 Standard Library

5.17 Concurrent Execution
=========================

The modules described in this chapter provide support for concurrent
execution of code.  The appropriate choice of tool will depend on the
task to be executed (CPU bound vs IO bound) and preferred style of
development (event driven cooperative multitasking vs preemptive
multitasking).  Here’s an overview:

* Menu:

* threading: threading --- Thread-based parallelism. Thread-based parallelism
* multiprocessing: multiprocessing --- Process-based parallelism. Process-based parallelism
* multiprocessing.shared_memory: multiprocessing shared_memory --- Provides shared memory for direct access across processes. Provides shared memory for direct access
                                 across processes
* The concurrent package::
* concurrent.futures: concurrent futures --- Launching parallel tasks. Launching parallel tasks
* subprocess: subprocess --- Subprocess management. Subprocess management
* sched: sched --- Event scheduler. Event scheduler
* queue: queue --- A synchronized queue class. A synchronized queue class
* contextvars: contextvars --- Context Variables. Context Variables
* _thread: _thread --- Low-level threading API. Low-level threading API
* _dummy_thread: _dummy_thread --- Drop-in replacement for the _thread module. Drop-in replacement for the _thread module
* dummy_threading: dummy_threading --- Drop-in replacement for the threading module. Drop-in replacement for the threading module


File: python.info,  Node: threading --- Thread-based parallelism,  Next: multiprocessing --- Process-based parallelism,  Up: Concurrent Execution

5.17.1 ‘threading’ — Thread-based parallelism
---------------------------------------------

`Source code:' Lib/threading.py(1)

__________________________________________________________________

This module constructs higher-level threading interfaces on top of the
lower level *note _thread: 3. module.  See also the *note queue: db.
module.

3.7 版更變: This module used to be optional, it is now always available.

     備註: While they are not listed below, the ‘camelCase’ names used
     for some methods and functions in this module in the Python 2.x
     series are still supported by this module.

`CPython implementation detail:' In CPython, due to the *note Global
Interpreter Lock: 50b, 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: b8. or *note
concurrent.futures.ProcessPoolExecutor: 2a5.  However, threading is
still an appropriate model if you want to run multiple I/O-bound tasks
simultaneously.

This module defines the following functions:

 -- 函式: threading.active_count ()

     Return the number of *note Thread: 236. objects currently alive.
     The returned count is equal to the length of the list returned by
     *note enumerate(): 2355.

 -- 函式: threading.current_thread ()

     Return the current *note Thread: 236. object, corresponding to the
     caller’s thread of control.  If the caller’s thread of control was
     not created through the *note threading: 10a. module, a dummy
     thread object with limited functionality is returned.

 -- 函式: threading.excepthook (args, /)

     Handle uncaught exception raised by *note Thread.run(): 233.

     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: 601, the exception is silently
     ignored.  Otherwise, the exception is printed out on *note
     sys.stderr: 314.

     If this function raises an exception, *note sys.excepthook(): e68.
     is called to handle it.

     *note threading.excepthook(): 232. can be overridden to control how
     uncaught exceptions raised by *note Thread.run(): 233. 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(): e68. handles uncaught exceptions.

     3.8 版新加入.

 -- 函式: 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: 1364.: Windows, FreeBSD, Linux, macOS, OpenBSD,
     NetBSD, AIX.

     3.8 版新加入.

 -- 函式: threading.enumerate ()

     Return a list of all *note Thread: 236. objects currently alive.
     The list includes daemonic threads, dummy thread objects created by
     *note current_thread(): 2356, and the main thread.  It excludes
     terminated threads and threads that have not yet been started.

 -- 函式: threading.main_thread ()

     Return the main *note Thread: 236. 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: 10a. module.  The `func' will be passed to *note
     sys.settrace(): e43. for each thread, before its *note run(): 233.
     method is called.

 -- 函式: threading.setprofile (func)

     Set a profile function for all threads started from the *note
     threading: 10a. module.  The `func' will be passed to *note
     sys.setprofile(): e42. for each thread, before its *note run():
     233. method is called.

 -- 函式: 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: 2bb. is
     raised.  If the specified stack size is invalid, a *note
     ValueError: 1fc. 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 Availability: 1364.: Windows, systems with POSIX threads.

This module also defines the following constant:

 -- Data: threading.TIMEOUT_MAX

     The maximum value allowed for the `timeout' parameter of blocking
     functions (*note Lock.acquire(): 771, *note RLock.acquire(): 772,
     *note Condition.wait(): 235b, etc.).  Specifying a timeout greater
     than this value will raise an *note OverflowError: 965.

     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: 236. 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 Objects::
* 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.8/Lib/threading.py


File: python.info,  Node: Thread-Local Data,  Next: Thread Objects,  Up: threading --- Thread-based parallelism

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: 22f8. (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.


File: python.info,  Node: Thread Objects,  Next: Lock Objects,  Prev: Thread-Local Data,  Up: threading --- Thread-based parallelism

5.17.1.2 Thread Objects
.......................

The *note Thread: 236. 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(): 233. 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(): 233. methods of this
class.

Once a thread object is created, its activity must be started by calling
the thread’s *note start(): 20db. method.  This invokes the *note run():
233. 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(): 233. method terminates –
either normally, or by raising an unhandled exception.  The *note
is_alive(): 235f. method tests whether the thread is alive.

Other threads can call a thread’s *note join(): b65. method.  This
blocks the calling thread until the thread whose *note join(): b65.
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: 2360. attribute.

If the *note run(): 233. method raises an exception, *note
threading.excepthook(): 232. is called to handle it.  By default, *note
threading.excepthook(): 232. ignores silently *note SystemExit: 601.

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: 2361. 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: ab2.

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 join(): b65.ed.  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():
     233. 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.

     `args' is the argument tuple 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 版更變: Added the `daemon' argument.

      -- 成員函式: start ()

          Start the thread’s activity.

          It must be called at most once per thread object.  It arranges
          for the object’s *note run(): 233. method to be invoked in a
          separate thread of control.

          This method will raise a *note RuntimeError: 2bb. 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(): 233. 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.

      -- 成員函式: join (timeout=None)

          Wait until the thread terminates.  This blocks the calling
          thread until the thread whose *note join(): b65. 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():
          b65. always returns ‘None’, you must call *note is_alive():
          235f. after *note join(): b65. to decide whether a timeout
          happened – if the thread is still alive, the *note join():
          b65. call timed out.

          When the `timeout' argument is not present or ‘None’, the
          operation will block until the thread terminates.

          A thread can be *note join(): b65.ed many times.

          *note join(): b65. raises a *note RuntimeError: 2bb. if an
          attempt is made to join the current thread as that would cause
          a deadlock.  It is also an error to *note join(): b65. 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 ()

          Old getter/setter API for *note name: 2360.; use it directly
          as a property instead.

      -- 屬性: 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(): ab4. 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 native integral thread ID of this thread.  This is a
          non-negative integer, or ‘None’ if the thread has not been
          started.  See the *note get_native_id(): 234. function.  This
          represents the Thread ID (‘TID’) as assigned to the thread by
          the OS (kernel).  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).

               備註: 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: 1364.: Requires *note get_native_id():
          234. function.

          3.8 版新加入.

      -- 成員函式: is_alive ()

          Return whether the thread is alive.

          This method returns ‘True’ just before the *note run(): 233.
          method starts until just after the *note run(): 233. method
          terminates.  The module function *note enumerate(): 2355.
          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(): 20db. is called, otherwise *note RuntimeError: 2bb.
          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: 2361. = ‘False’.

          The entire Python program exits when no alive non-daemon
          threads are left.

      -- 成員函式: isDaemon ()
      -- 成員函式: setDaemon ()

          Old getter/setter API for *note daemon: 2361.; use it directly
          as a property instead.


File: python.info,  Node: Lock Objects,  Next: RLock Objects,  Prev: Thread Objects,  Up: threading --- Thread-based parallelism

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: 3. 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(): 771. and *note release(): 2368.  When the state is unlocked,
*note acquire(): 771. changes the state to locked and returns
immediately.  When the state is locked, *note acquire(): 771. blocks
until a call to *note release(): 2368. in another thread changes it to
unlocked, then the *note acquire(): 771. call resets it to locked and
returns.  The *note release(): 2368. 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:
2bb. will be raised.

Locks also support the *note context management protocol: 2369.

When more than one thread is blocked in *note acquire(): 771. waiting
for the state to turn to unlocked, only one thread proceeds when a *note
release(): 2368. 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.

     Note that ‘Lock’ is actually a factory function which returns an
     instance of the most efficient version of the concrete Lock class
     that is supported by the platform.

      -- 成員函式: 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: 2bb.
          is raised.

          There is no return value.

      -- 成員函式: locked ()

          Return true if the lock is acquired.


File: python.info,  Node: RLock Objects,  Next: Condition Objects,  Prev: Lock Objects,  Up: threading --- Thread-based parallelism

5.17.1.4 RLock Objects
......................

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.

To lock the lock, a thread calls its *note acquire(): 772. method; this
returns once the thread owns the lock.  To unlock the lock, a thread
calls its *note release(): 2368. method.  *note acquire(): 771./*note
release(): 2368. call pairs may be nested; only the final *note
release(): 2368. (the *note release(): 2368. of the outermost pair)
resets the lock to unlocked and allows another thread blocked in *note
acquire(): 771. to proceed.

Reentrant locks also support the *note context management protocol:
2369.

 -- 類別: 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.

          When invoked without arguments: if this thread already owns
          the lock, increment the recursion level by one, and return
          immediately.  Otherwise, if another thread owns the lock,
          block until the lock is unlocked.  Once the lock is unlocked
          (not owned by any thread), then grab ownership, set the
          recursion level to one, and return.  If more than one thread
          is blocked waiting until the lock is unlocked, only one at a
          time will be able to grab ownership of the lock.  There is no
          return value in this case.

          When invoked with the `blocking' argument set to true, do the
          same thing as when called without arguments, and return
          ‘True’.

          When invoked with the `blocking' argument 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 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.  Return ‘True’ if the lock has been acquired, false
          if the timeout has elapsed.

          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: 2bb. is raised if this method is called
          when the lock is unlocked.

          There is no return value.


File: python.info,  Node: Condition Objects,  Next: Semaphore Objects,  Prev: RLock Objects,  Up: threading --- Thread-based parallelism

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: 2369.:
using the ‘with’ statement acquires the associated lock for the duration
of the enclosed block.  The *note acquire(): 2371. and *note release():
2372. methods also call the corresponding methods of the associated
lock.

Other methods must be called with the associated lock held.  The *note
wait(): 235b. method releases the lock, and then blocks until another
thread awakens it by calling *note notify(): 2373. or *note
notify_all(): 2374.  Once awakened, *note wait(): 235b. re-acquires the
lock and returns.  It is also possible to specify a timeout.

The *note notify(): 2373. method wakes up one of the threads waiting for
the condition variable, if any are waiting.  The *note notify_all():
2374. method wakes up all threads waiting for the condition variable.

Note: the *note notify(): 2373. and *note notify_all(): 2374. methods
don’t release the lock; this means that the thread or threads awakened
will not return from their *note wait(): 235b. call immediately, but
only when the thread that called *note notify(): 2373. or *note
notify_all(): 2374. 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(): 235b. repeatedly until
they see the desired state, while threads that modify the state call
*note notify(): 2373. or *note notify_all(): 2374. 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(): 235b. can return after an arbitrary long time, and
the condition which prompted the *note notify(): 2373. call may no
longer hold true.  This is inherent to multi-threaded programming.  The
*note wait_for(): 2375. 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(): 2373. and *note notify_all(): 2374,
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: 236a. or *note RLock: bf4. object, and it is used as the
     underlying lock.  Otherwise, a new *note RLock: bf4. 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: 2bb. is raised.

          This method releases the underlying lock, and then blocks
          until it is awakened by a *note notify(): 2373. or *note
          notify_all(): 2374. 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: bf4, it is not
          released using its *note release(): 2372. method, since this
          may not actually unlock the lock when it was acquired multiple
          times recursively.  Instead, an internal interface of the
          *note RLock: bf4. 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(): 235b. 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(): 235b.:
          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: 2bb. 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(): 235b. call until it can reacquire the lock.
          Since *note notify(): 2373. does not release the lock, its
          caller should.

      -- 成員函式: notify_all ()

          Wake up all threads waiting on this condition.  This method
          acts like *note notify(): 2373, 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: 2bb. is raised.


File: python.info,  Node: Semaphore Objects,  Next: Event Objects,  Prev: Condition Objects,  Up: threading --- Thread-based parallelism

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(): bf1. and *note release(): 2378.).

A semaphore manages an internal counter which is decremented by each
*note acquire(): bf1. call and incremented by each *note release():
2378. call.  The counter can never go below zero; when *note acquire():
bf1. finds that it is zero, it blocks, waiting until some other thread
calls *note release(): 2378.

Semaphores also support the *note context management protocol: 2369.

 -- 類別: threading.Semaphore (value=1)

     This class implements semaphore objects.  A semaphore manages an
     atomic counter representing the number of *note release(): 2378.
     calls minus the number of *note acquire(): bf1. calls, plus an
     initial value.  The *note acquire(): bf1. 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: 1fc. 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(): 2378.  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(): 2378.  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 ()

          Release a semaphore, incrementing the internal counter by one.
          When it was zero on entry and another thread is waiting for it
          to become larger than zero again, wake up that thread.

 -- 類別: 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: 1fc. 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 Example::


File: python.info,  Node: Semaphore Example,  Up: Semaphore Objects

5.17.1.7 ‘Semaphore’ Example
............................

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:
             # ... use connection ...
         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 --- Thread-based parallelism

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(): 237d. method and reset to false with the *note clear():
237e. method.  The *note wait(): cbc. 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(): 237d. method and reset to
     false with the *note clear(): 237e. method.  The *note wait(): cbc.
     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.

      -- 成員函式: set ()

          Set the internal flag to true.  All threads waiting for it to
          become true are awakened.  Threads that call *note wait():
          cbc. once the flag is true will not block at all.

      -- 成員函式: clear ()

          Reset the internal flag to false.  Subsequently, threads
          calling *note wait(): cbc. will block until *note set(): 237d.
          is called to set the internal flag to true again.

      -- 成員函式: wait (timeout=None)

          Block until the internal flag is true.  If the internal flag
          is true on entry, return immediately.  Otherwise, block until
          another thread calls *note set(): 237d. to set the flag to
          true, 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).

          This method returns ‘True’ if and only if the internal flag
          has been set to true, either before the wait call or after the
          wait starts, so it will always return ‘True’ except if a
          timeout is given and the operation times out.

          3.1 版更變: Previously, the method always returned ‘None’.


File: python.info,  Node: Timer Objects,  Next: Barrier Objects,  Prev: Event Objects,  Up: threading --- Thread-based parallelism

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: ab3. is a subclass of
*note Thread: 236. and as such also functions as an example of creating
custom threads.

Timers are started, as with threads, by calling their ‘start()’ method.
The timer can be stopped (before its action has begun) by calling the
*note cancel(): 2382. method.  The interval the timer will wait before
executing its action may not be exactly the same as the interval
specified by the user.

For example:

     def hello():
         print("hello, world")

     t = Timer(30.0, hello)
     t.start()  # after 30 seconds, "hello, world" will be printed

 -- 類別: 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 --- Thread-based parallelism

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(): 2384.
method and will block until all of the threads have made their *note
wait(): 2384. 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(): 2384. 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:
                   # Only one thread needs to print this
                   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: b66.
          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: b66.
          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(): 2384. to fail with the *note
          BrokenBarrierError: b66.  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: 2bb, is raised
     when the *note Barrier: b64. object is reset or broken.


File: python.info,  Node: Using locks conditions and semaphores in the with statement,  Prev: Barrier Objects,  Up: threading --- Thread-based parallelism

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:
6ee. 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:
         # do something...

is equivalent to:

     some_lock.acquire()
     try:
         # do something...
     finally:
         some_lock.release()

Currently, *note Lock: 236a, *note RLock: bf4, *note Condition: aaf,
*note Semaphore: ab0, and *note BoundedSemaphore: ab1. objects may be
used as *note with: 6ee. statement context managers.


File: python.info,  Node: multiprocessing --- Process-based parallelism,  Next: multiprocessing shared_memory --- Provides shared memory for direct access across processes,  Prev: threading --- Thread-based parallelism,  Up: Concurrent Execution

5.17.2 ‘multiprocessing’ — Process-based parallelism
----------------------------------------------------

`Source code:' Lib/multiprocessing/(1)

__________________________________________________________________

* Menu:

* 簡介: 簡介<8>.
* Reference::
* Programming guidelines::
* Examples: Examples<10>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/multiprocessing/


File: python.info,  Node: 簡介<8>,  Next: Reference,  Up: multiprocessing --- Process-based parallelism

5.17.2.1 簡介
.............

*note multiprocessing: b8. is a package that supports spawning processes
using an API similar to the *note threading: 10a. module.  The *note
multiprocessing: b8. package offers both local and remote concurrency,
effectively side-stepping the *note Global Interpreter Lock: 50b. by
using subprocesses instead of threads.  Due to this, the *note
multiprocessing: b8. module allows the programmer to fully leverage
multiple processors on a given machine.  It runs on both Unix and
Windows.

The *note multiprocessing: b8. module also introduces APIs which do not
have analogs in the *note threading: 10a. module.  A prime example of
this is the *note Pool: 880. 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:
880,

     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]

* Menu:

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


File: python.info,  Node: The Process class,  Next: Contexts and start methods,  Up: 簡介<8>

5.17.2.2 The ‘Process’ class
............................

In *note multiprocessing: b8, processes are spawned by creating a *note
Process: 3b7. object and then calling its *note start(): 238f. method.
*note Process: 3b7. follows the API of *note threading.Thread: 236.  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: 2390.


File: python.info,  Node: Contexts and start methods,  Next: Exchanging objects between processes,  Prev: The Process class,  Up: 簡介<8>

5.17.2.3 Contexts and start methods
...................................

Depending on the platform, *note multiprocessing: b8. 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(): 2392. 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 Unix and Windows.  The default on Windows and
          macOS.

     `fork'

          The parent process uses *note os.fork(): 966. 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 Unix only.  The default on Unix.

     `forkserver'

          When the program starts and selects the `forkserver' start
          method, a server process is started.  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 so it is safe for it to use
          *note os.fork(): 966.  No unnecessary resources are inherited.

          Available on Unix platforms which support passing file
          descriptors over Unix pipes.

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).

3.4 版更變: `spawn' added on all unix platforms, and `forkserver' added
for some unix platforms.  Child processes no longer inherit all of the
parents inheritable handles on Windows.

On Unix 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: 2393.
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(): 87e. 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(): 87e. should not be used more than once in the
program.

Alternatively, you can use *note get_context(): 87f. 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(): 87f. to avoid interfering with the choice of
the library user.

     警告: The ‘'spawn'’ and ‘'forkserver'’ start methods cannot
     currently be used with "frozen" executables (i.e., binaries
     produced by packages like `PyInstaller' and `cx_Freeze') on Unix.
     The ‘'fork'’ start method does work.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue33725


File: python.info,  Node: Exchanging objects between processes,  Next: Synchronization between processes,  Prev: Contexts and start methods,  Up: 簡介<8>

5.17.2.4 Exchanging objects between processes
.............................................

*note multiprocessing: b8. supports two types of communication channel
between processes:

`Queues'

     The *note Queue: 2395. class is a near clone of *note queue.Queue:
     d1d.  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())    # prints "[42, None, 'hello']"
              p.join()

     Queues are thread and process safe.

`Pipes'

     The *note Pipe(): 2396. 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())   # prints "[42, None, 'hello']"
              p.join()

     The two connection objects returned by *note Pipe(): 2396.
     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.


File: python.info,  Node: Synchronization between processes,  Next: Sharing state between processes,  Prev: Exchanging objects between processes,  Up: 簡介<8>

5.17.2.5 Synchronization between processes
..........................................

*note multiprocessing: b8. contains equivalents of all the
synchronization primitives from *note threading: 10a.  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: 簡介<8>

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: b8. provides a couple of ways of doing so.

`Shared memory'

     Data can be stored in a shared memory map using *note Value: 2399.
     or *note Array: 239a.  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: 7. 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: be. module which supports the
     creation of arbitrary ctypes objects allocated from shared memory.

`Server process'

     A manager object returned by ‘Manager()’ controls a server process
     which holds Python objects and allows other processes to manipulate
     them using proxies.

     A manager returned by ‘Manager()’ will support types *note list:
     263, *note dict: 1b9, *note Namespace: 239b, *note Lock: 239c,
     *note RLock: 239d, *note Semaphore: 239e, *note BoundedSemaphore:
     239f, *note Condition: 23a0, *note Event: 23a1, *note Barrier:
     23a2, *note Queue: 2395, *note Value: 2399. and *note Array: 239a.
     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: 簡介<8>

5.17.2.7 Using a pool of workers
................................

The *note Pool: 880. 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.

For example:

     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 secs
             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: 2390. however it is worth pointing
     out here.  This means that some examples, such as the *note
     multiprocessing.pool.Pool: 880. 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: 'module' object has no attribute 'f'
          AttributeError: 'module' object has no attribute 'f'
          AttributeError: 'module' object has no attribute 'f'

     (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,  Next: Programming guidelines,  Prev: 簡介<8>,  Up: multiprocessing --- Process-based parallelism

5.17.2.8 Reference
..................

The *note multiprocessing: b8. package mostly replicates the API of the
*note threading: 10a. module.

* Menu:

* Process and exceptions::
* Pipes and Queues::
* Miscellaneous: Miscellaneous<3>.
* Connection Objects: Connection Objects<2>.
* Synchronization primitives::
* Shared ctypes Objects::
* Managers::
* Proxy Objects::
* Process Pools::
* Listeners and Clients::
* Authentication keys::
* Logging: Logging<2>.
* The multiprocessing.dummy module: The multiprocessing dummy module.


File: python.info,  Node: Process and exceptions,  Next: Pipes and Queues,  Up: Reference

5.17.2.9 ‘Process’ and exceptions
.................................

 -- 類別: 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: 3b7. class has equivalents of all the
     methods of *note threading.Thread: 236.

     The constructor should always be called with keyword arguments.
     `group' should always be ‘None’; it exists solely for compatibility
     with *note threading.Thread: 236.  `target' is the callable object
     to be invoked by the *note run(): 2392. method.  It defaults to
     ‘None’, meaning nothing is called.  `name' is the process name (see
     *note name: 23a6. 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: 23a7. 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'.

     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 版更變: Added the `daemon' argument.

      -- 成員函式: run ()

          Method representing the process’s activity.

          You may override this method in a subclass.  The standard
          *note run(): 2392. 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.

      -- 成員函式: start ()

          Start the process’s activity.

          This must be called at most once per process object.  It
          arranges for the object’s *note run(): 2392. 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(): 23a8.
          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: 23a9.
          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(): 238f. method returns until the child process
          terminates.

      -- 屬性: daemon

          The process’s daemon flag, a Boolean value.  This must be set
          before *note start(): 238f. 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: 236. API, *note Process:
     3b7. 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.  A negative value `-N' indicates that the
          child was terminated by signal `N'.

      -- 屬性: authkey

          The process’s authentication key (a byte string).

          When *note multiprocessing: b8. is initialized the main
          process is assigned a random string using *note os.urandom():
          4d6.

          When a *note Process: 3b7. object is created, it will inherit
          the authentication key of its parent process, although this
          may be changed by setting *note authkey: 23ac. to another byte
          string.

          See *note Authentication keys: 23ad.

      -- 屬性: 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(): a29.
          Otherwise calling *note join(): 23a8. is simpler.

          On Windows, this is an OS handle usable with the
          ‘WaitForSingleObject’ and ‘WaitForMultipleObjects’ family of
          API calls.  On Unix, this is a file descriptor usable with
          primitives from the *note select: e6. module.

          3.3 版新加入.

      -- 成員函式: terminate ()

          Terminate the process.  On Unix this is done using the
          ‘SIGTERM’ 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(): 23ae. but using the ‘SIGKILL’
          signal on Unix.

          3.7 版新加入.

      -- 成員函式: close ()

          Close the *note Process: 3b7. object, releasing all resources
          associated with it.  *note ValueError: 1fc. is raised if the
          underlying process is still running.  Once *note close(): 3b5.
          returns successfully, most other methods and attributes of the
          *note Process: 3b7. object will raise *note ValueError: 1fc.

          3.7 版新加入.

     Note that the *note start(): 238f, *note join(): 23a8, *note
     is_alive(): 23aa, *note terminate(): 23ae. and *note exitcode:
     23a9. methods should only be called by the process that created the
     process object.

     Example usage of some of the methods of *note Process: 3b7.:

           >>> import multiprocessing, time, signal
           >>> p = multiprocessing.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: b8. 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: 23b0. 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<3>,  Prev: Process and exceptions,  Up: Reference

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(): 2396. (for a connection
between two processes) or a queue (which allows multiple producers and
consumers).

The *note Queue: 2395, *note SimpleQueue: 23b4. and *note JoinableQueue:
23b5. types are multi-producer, multi-consumer FIFO queues modelled on
the *note queue.Queue: d1d. class in the standard library.  They differ
in that *note Queue: 2395. lacks the *note task_done(): 23b6. and *note
join(): 23b7. methods introduced into Python 2.5’s *note queue.Queue:
d1d. class.

If you use *note JoinableQueue: 23b5. then you `must' call *note
JoinableQueue.task_done(): 23b8. 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.

Note that one can also create a shared queue by using a manager object –
see *note Managers: 23b9.

     備註: *note multiprocessing: b8. uses the usual *note queue.Empty:
     23ba. and *note queue.Full: 23bb. exceptions to signal a timeout.
     They are not available in the *note multiprocessing: b8. namespace
     so you need to import them from *note queue: db.

     備註: 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: 23b9.

       1. After putting an object on an empty queue there may be an
          infinitesimal delay before the queue’s *note empty(): 23bc.
          method returns *note False: 38d. and *note get_nowait(): 23bd.
          can return without raising *note queue.Empty: 23ba.

       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(): 23ae.
     or *note os.kill(): cf8. while it is trying to use a *note Queue:
     2395, 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:
     23be.), 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: 2390.

For an example of the usage of queues for interprocess communication see
*note Examples: 23bf.

 -- 函式: multiprocessing.Pipe ([duplex])

     Returns a pair ‘(conn1, conn2)’ of *note Connection: 23c0. 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.

 -- 類別: 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: 23ba. and *note queue.Full: 23bb.
     exceptions from the standard library’s *note queue: db. module are
     raised to signal timeouts.

     *note Queue: 2395. implements all the methods of *note queue.Queue:
     d1d. except for *note task_done(): 23b6. and *note join(): 23b7.

      -- 成員函式: 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: 613. on
          Unix platforms like Mac OS X 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.

      -- 成員函式: 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: 23bb. 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: 23bb.
          exception (`timeout' is ignored in that case).

          3.8 版更變: If the queue is closed, *note ValueError: 1fc. is
          raised instead of *note AssertionError: 1033.

      -- 成員函式: 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: 23ba. 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: 23ba. exception (`timeout' is
          ignored in that case).

          3.8 版更變: If the queue is closed, *note ValueError: 1fc. is
          raised instead of *note OSError: 1d4.

      -- 成員函式: get_nowait ()

          Equivalent to ‘get(False)’.

     *note multiprocessing.Queue: 2395. has a few additional methods not
     found in *note queue.Queue: d1d.  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(): 23c4. 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(): 23be. to make
          *note join_thread(): 23c5. do nothing.

      -- 成員函式: cancel_join_thread ()

          Prevent *note join_thread(): 23c5. from blocking.  In
          particular, this prevents the background thread from being
          joined automatically when the process exits – see *note
          join_thread(): 23c5.

          A better name for this method might be
          ‘allow_exit_without_flush()’.  It is likely to cause enqueued
          data to 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: 2395. will result
          in an *note ImportError: 339.  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: 2395. type, very close to a locked
     *note Pipe: 2396.

      -- 成員函式: empty ()

          Return ‘True’ if the queue is empty, ‘False’ otherwise.

      -- 成員函式: get ()

          Remove and return an item from the queue.

      -- 成員函式: put (item)

          Put `item' into the queue.

 -- 類別: multiprocessing.JoinableQueue ([maxsize])

     *note JoinableQueue: 23b5, a *note Queue: 2395. subclass, is a
     queue which additionally has *note task_done(): 23b8. and *note
     join(): 23c9. methods.

      -- 成員函式: task_done ()

          Indicate that a formerly enqueued task is complete.  Used by
          queue consumers.  For each *note get(): 1032. used to fetch a
          task, a subsequent call to *note task_done(): 23b8. tells the
          queue that the processing on the task is complete.

          If a *note join(): 23b7. is currently blocking, it will resume
          when all items have been processed (meaning that a *note
          task_done(): 23b8. call was received for every item that had
          been *note put(): 1031. into the queue).

          Raises a *note ValueError: 1fc. 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(): 23b8. 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(): 23b7. unblocks.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue3770


File: python.info,  Node: Miscellaneous<3>,  Next: Connection Objects<2>,  Prev: Pipes and Queues,  Up: Reference

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
     ‘len(os.sched_getaffinity(0))’

     May raise *note NotImplementedError: 613.

     也參考
     ......

     *note os.cpu_count(): 884.

 -- 函式: multiprocessing.current_process ()

     Return the *note Process: 3b7. object corresponding to the current
     process.

     An analogue of *note threading.current_thread(): 2356.

 -- 函式: multiprocessing.parent_process ()

     Return the *note Process: 3b7. object corresponding to the parent
     process of the *note current_process(): 23cc.  For the main
     process, ‘parent_process’ will be ‘None’.

     3.8 版新加入.

 -- 函式: multiprocessing.freeze_support ()

     Add support for when a program which uses *note multiprocessing:
     b8. 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: 2bb.

     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'’.  On Windows only ‘'spawn'’ is available.  On
     Unix ‘'fork'’ and ‘'spawn'’ are always supported, with ‘'fork'’
     being the default.

     3.4 版新加入.

 -- 函式: multiprocessing.get_context (method=None)

     Return a context object which has the same attributes as the *note
     multiprocessing: b8. module.

     If `method' is ‘None’ then the default context is returned.
     Otherwise `method' should be ‘'fork'’, ‘'spawn'’, ‘'forkserver'’.
     *note ValueError: 1fc. is raised if the specified start method is
     not available.

     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’.  ‘'fork'’ is the default on Unix, while ‘'spawn'’ is the
     default on Windows.

     3.4 版新加入.

 -- 函式: multiprocessing.set_executable ()

     Sets the path of the Python interpreter to use when starting a
     child process.  (By default *note sys.executable: 275. 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 Unix when the ‘'spawn'’ start method
     is used.

 -- 函式: multiprocessing.set_start_method (method)

     Set the method which should be used to start child processes.
     `method' can be ‘'fork'’, ‘'spawn'’ or ‘'forkserver'’.

     Note that this should be called at most once, and it should be
     protected inside the ‘if __name__ == '__main__'’ clause of the main
     module.

     3.4 版新加入.

     備註: *note multiprocessing: b8. contains no analogues of *note
     threading.active_count(): 2354, *note threading.enumerate(): 2355,
     *note threading.settrace(): 2357, *note threading.setprofile():
     2358, *note threading.Timer: ab3, or *note threading.local: 22f8.


File: python.info,  Node: Connection Objects<2>,  Next: Synchronization primitives,  Prev: Miscellaneous<3>,  Up: Reference

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: 2396. – see
also *note Listeners and Clients: 23d1.

 -- 類別: multiprocessing.connection.Connection

      -- 成員函式: send (obj)

          Send an object to the other end of the connection which should
          be read using *note recv(): 23d3.

          The object must be picklable.  Very large pickles
          (approximately 32 MiB+, though it depends on the OS) may raise
          a *note ValueError: 1fc. exception.

      -- 成員函式: recv ()

          Return an object sent from the other end of the connection
          using *note send(): 23d2.  Blocks until there is something to
          receive.  Raises *note EOFError: c71. 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(): a29.

      -- 成員函式: send_bytes (buffer[, offset[, size]])

          Send byte data from a *note bytes-like object: 5ed. 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:
          1fc. 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: c71. 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: 1d4. is raised and the
          connection will no longer be readable.

          3.3 版更變: This function used to raise *note IOError: 997,
          which is now an alias of *note OSError: 1d4.

      -- 成員函式: 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: c71. if there is nothing left to
          receive and the other end was closed.

          `buffer' must be a writable *note bytes-like object: 5ed.  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(): 23d2. and *note
     Connection.recv(): 23d3.

     3.3 版新加入: Connection objects now support the context management
     protocol – see *note Context Manager Types: 148d.  *note
     __enter__(): 16e1. returns the connection object, and *note
     __exit__(): 16e3. calls *note close(): 23d5.

For example:

     >>> 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(): 23d3. 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(): 23d3. and *note send(): 23d2.
     methods after performing some sort of authentication.  See *note
     Authentication keys: 23ad.

     警告: 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: Shared ctypes Objects,  Prev: Connection Objects<2>,  Up: Reference

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: 10a. module.

Note that one can also create synchronization primitives by using a
manager object – see *note Managers: 23b9.

 -- 類別: multiprocessing.Barrier (parties[, action[, timeout]])

     A barrier object: a clone of *note threading.Barrier: b64.

     3.3 版新加入.

 -- 類別: multiprocessing.BoundedSemaphore ([value])

     A bounded semaphore object: a close analog of *note
     threading.BoundedSemaphore: ab1.

     A solitary difference from its close analog exists: its ‘acquire’
     method’s first argument is named `block', as is consistent with
     *note Lock.acquire(): 23db.

          備註: On Mac OS X, this is indistinguishable from *note
          Semaphore: 239e. because ‘sem_getvalue()’ is not implemented
          on that platform.

 -- 類別: multiprocessing.Condition ([lock])

     A condition variable: an alias for *note threading.Condition: aaf.

     If `lock' is specified then it should be a *note Lock: 239c. or
     *note RLock: 239d. object from *note multiprocessing: b8.

     3.3 版更變: The *note wait_for(): 2375. method was added.

 -- 類別: multiprocessing.Event

     A clone of *note threading.Event: ab2.

 -- 類別: multiprocessing.Lock

     A non-recursive lock object: a close analog of *note
     threading.Lock: 236a.  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: 236a. as
     it applies to threads are replicated here in *note
     multiprocessing.Lock: 239c. as it applies to either processes or
     threads, except as noted.

     Note that *note Lock: 239c. is actually a factory function which
     returns an instance of ‘multiprocessing.synchronize.Lock’
     initialized with a default context.

     *note Lock: 239c. supports the *note context manager: 56d. protocol
     and thus may be used in *note with: 6ee. 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(): 771.

          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(): 771.  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():
          2368. except that when invoked on an unlocked lock, a *note
          ValueError: 1fc. is raised.

 -- 類別: multiprocessing.RLock

     A recursive lock object: a close analog of *note threading.RLock:
     bf4.  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: 239d. is actually a factory function which
     returns an instance of ‘multiprocessing.synchronize.RLock’
     initialized with a default context.

     *note RLock: 239d. supports the *note context manager: 56d.
     protocol and thus may be used in *note with: 6ee. 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(): 772, 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(): 23db.  Note that some of these behaviors
          of `timeout' differ from the implemented behaviors in *note
          threading.RLock.acquire(): 772.

      -- 成員函式: 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: 1033. 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():
          236e.

 -- 類別: multiprocessing.Semaphore ([value])

     A semaphore object: a close analog of *note threading.Semaphore:
     ab0.

     A solitary difference from its close analog exists: its ‘acquire’
     method’s first argument is named `block', as is consistent with
     *note Lock.acquire(): 23db.

     備註: On Mac OS X, ‘sem_timedwait’ is unsupported, so calling
     ‘acquire()’ with a timeout will emulate that function’s behavior
     using a sleeping loop.

     備註: If the SIGINT signal generated by ‘Ctrl-C’ arrives while the
     main thread is blocked by a call to ‘BoundedSemaphore.acquire()’,
     *note Lock.acquire(): 23db, *note RLock.acquire(): 23dd,
     ‘Semaphore.acquire()’, ‘Condition.acquire()’ or ‘Condition.wait()’
     then the call will be immediately interrupted and *note
     KeyboardInterrupt: 198. will be raised.

     This differs from the behaviour of *note threading: 10a. where
     SIGINT will be ignored while the equivalent blocking calls are in
     progress.

     備註: 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: 339.  See bpo-3770(1) for additional information.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue3770


File: python.info,  Node: Shared ctypes Objects,  Next: Managers,  Prev: Synchronization primitives,  Up: Reference

5.17.2.14 Shared ‘ctypes’ Objects
.................................

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: 2b. 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: 2399.

     `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: 7. 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: 239c. or *note RLock: 239d. 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: 7. 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:
     239c. or *note RLock: 239d. 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: 22c4. has `value' and
     `raw' attributes which allow one to use it to store and retrieve
     strings.

* Menu:

* The multiprocessing.sharedctypes module: The multiprocessing sharedctypes module.


File: python.info,  Node: The multiprocessing sharedctypes module,  Up: Shared ctypes Objects

5.17.2.15 The ‘multiprocessing.sharedctypes’ module
...................................................

The *note multiprocessing.sharedctypes: be. module provides functions
for allocating *note ctypes: 2b. 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: 7. 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(): 23e2. 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: 7. 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(): 23e4. instead to make sure that access is
     automatically synchronized using a lock.

     Note that an array of *note ctypes.c_char: 22c4. has ‘value’ and
     ‘raw’ attributes which allow one to use it to store and retrieve
     strings – see documentation for *note ctypes: 2b.

 -- 函式: multiprocessing.sharedctypes.Array (typecode_or_type,
          size_or_initializer, *, lock=True)

     The same as *note RawArray(): 23e1. 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:
     239c. or *note RLock: 239d. 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(): 23e3. 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:
     239c. or *note RLock: 239d. 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: 239d. 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:
     56d. 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: 22e2.)

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: Shared ctypes Objects,  Up: Reference

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: 23e8. 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: bb. module:

 -- 類別: multiprocessing.managers.BaseManager ([address[, authkey]])

     Create a BaseManager object.

     Once created one should call *note start(): 23ea. 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.

      -- 成員函式: 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: 23ec. 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(): 23ea. 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(): 23ed. method, or if the
          `create_method' argument is ‘False’ then this can be left as
          ‘None’.

          `proxytype' is a subclass of *note BaseProxy: 23f0. 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(): 23f1.  (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__(): 1433. 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: 23e9. 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 Context Manager Types: 148d.  *note __enter__(): 16e1.
     starts the server process (if it has not already started) and then
     returns the manager object.  *note __exit__(): 16e3. calls *note
     shutdown(): 23ee.

     In previous versions *note __enter__(): 16e1. did not start the
     manager’s server process if it was not already started.

 -- 類別: multiprocessing.managers.SyncManager

     A subclass of *note BaseManager: 23e9. which can be used for the
     synchronization of processes.  Objects of this type are returned by
     ‘multiprocessing.Manager()’.

     Its methods create and return *note Proxy Objects: 56a. 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: b64. object and
          return a proxy for it.

          3.3 版新加入.

      -- 成員函式: BoundedSemaphore ([value])

          Create a shared *note threading.BoundedSemaphore: ab1. object
          and return a proxy for it.

      -- 成員函式: Condition ([lock])

          Create a shared *note threading.Condition: aaf. object and
          return a proxy for it.

          If `lock' is supplied then it should be a proxy for a *note
          threading.Lock: 236a. or *note threading.RLock: bf4. object.

          3.3 版更變: The *note wait_for(): 2375. method was added.

      -- 成員函式: Event ()

          Create a shared *note threading.Event: ab2. object and return
          a proxy for it.

      -- 成員函式: Lock ()

          Create a shared *note threading.Lock: 236a. object and return
          a proxy for it.

      -- 成員函式: Namespace ()

          Create a shared *note Namespace: 239b. object and return a
          proxy for it.

      -- 成員函式: Queue ([maxsize])

          Create a shared *note queue.Queue: d1d. object and return a
          proxy for it.

      -- 成員函式: RLock ()

          Create a shared *note threading.RLock: bf4. object and return
          a proxy for it.

      -- 成員函式: Semaphore ([value])

          Create a shared *note threading.Semaphore: ab0. 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: 1b9. object and return a proxy for
          it.

      -- 成員函式: list ()

      -- 成員函式: list (sequence)

          Create a shared *note list: 263. 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: 23e8.

 -- 類別: multiprocessing.managers.Namespace

     A type that can register with *note SyncManager: 23e8.

     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:

          >>> manager = multiprocessing.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: 23e9. and uses the *note register(): 23ef. 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))         # prints 7
             print(maths.mul(7, 8))         # prints 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

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:

     >>> from multiprocessing import Manager
     >>> manager = 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(): 335. to a proxy will return the
representation of the referent, whereas applying *note repr(): 7d1. 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: 56a.  This permits nesting of these managed lists, dicts,
and other *note Proxy Objects: 56a.:

     >>> 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: 263. or *note dict: 1b9. 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: 56a. for most use cases but also demonstrates a level of
control over the synchronization.

     備註: The proxy types in *note multiprocessing: b8. 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: 23f0.

      -- 成員函式: _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():
          23ef.

          If an exception is raised by the call, then is re-raised by
          *note _callmethod(): 23f1.  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():
          23f1.

          Note in particular that an exception will be raised if
          `methodname' has not been `exposed'.

          An example of the usage of *note _callmethod(): 23f1.:

               >>> l = manager.list(range(10))
               >>> l._callmethod('__len__')
               10
               >>> l._callmethod('__getitem__', (slice(2, 7),)) # equivalent to l[2:7]
               [2, 3, 4, 5, 6]
               >>> l._callmethod('__getitem__', (20,))          # equivalent to 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

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: 880. 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.cpu_count(): 884. 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(): 880. 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: bc. 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(): 2407. and *note terminate(): 2408. manually.
          Failure to do this can lead to the process hanging on
          finalization.

          Note that is `not correct' to rely on the garbage colletor to
          destroy the pool as CPython does not assure that the finalizer
          of the pool will be called (see *note object.__del__(): 924.
          for more information).

     3.2 版新加入: `maxtasksperchild'

     3.4 版新加入: `context'

          備註: Worker processes within a *note Pool: 880. 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: 880. 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(): 240a. 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(): 2409. method which returns a
          *note AsyncResult: 240b. 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(): c32. built-in
          function (it supports only one `iterable' argument though, for
          multiple iterables see *note starmap(): a2b.).  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(): 240c. or *note
          imap_unordered(): 240d. with explicit `chunksize' option for
          better efficiency.

      -- 成員函式: map_async (func, iterable[, chunksize[, callback[,
               error_callback]]])

          A variant of the *note map(): a2e. method which returns a
          *note AsyncResult: 240b. 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(): a2e.

          The `chunksize' argument is the same as the one used by the
          *note map(): a2e. 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(): 240c. method has an
          optional `timeout' parameter: ‘next(timeout)’ will raise *note
          multiprocessing.TimeoutError: 23b2. if the result cannot be
          returned within `timeout' seconds.

      -- 成員函式: imap_unordered (func, iterable[, chunksize])

          The same as *note imap(): 240c. 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(): c32. 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(): a2b. and *note map_async():
          a2f. 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(): 2408. will be called immediately.

      -- 成員函式: join ()

          Wait for the worker processes to exit.  One must call *note
          close(): 2407. or *note terminate(): 2408. before using *note
          join(): 240e.

     3.3 版新加入: Pool objects now support the context management
     protocol – see *note Context Manager Types: 148d.  *note
     __enter__(): 16e1. returns the pool object, and *note __exit__():
     16e3. calls *note terminate(): 2408.

 -- 類別: multiprocessing.pool.AsyncResult

     The class of the result returned by *note Pool.apply_async(): 240a.
     and *note Pool.map_async(): a2f.

      -- 成員函式: 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: 23b2. is raised.  If the
          remote call raised an exception then that exception will be
          reraised by *note get(): 240f.

      -- 成員函式: 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: 1fc. if the result is
          not ready.

          3.7 版更變: If the result is not ready, *note ValueError: 1fc.
          is raised instead of *note AssertionError: 1033.

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

5.17.2.22 Listeners and Clients
...............................

Usually message passing between processes is done using queues or by
using *note Connection: 23c0. objects returned by *note Pipe(): 2396.

However, the *note multiprocessing.connection: b9. 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: 8f. 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: 23b1. 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: 23b1. 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: 23c0.

     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: 2417.)

     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: 23b1. is raised if authentication fails.  See
     *note Authentication keys: 23ad.

 -- 類別: 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: 2417.  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(): 1c6d.

     If the listener object uses a socket then `backlog' (1 by default)
     is passed to the *note listen(): 750. 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: 23b1. is raised if authentication fails.  See
     *note Authentication keys: 23ad.

      -- 成員函式: accept ()

          Accept a connection on the bound socket or named pipe of the
          listener object and return a *note Connection: 23c0. object.
          If authentication is attempted and fails, then *note
          AuthenticationError: 23b1. 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 Context Manager Types: 148d.  *note
     __enter__(): 16e1. returns the listener object, and *note
     __exit__(): 16e3. calls *note close(): 241a.

 -- 函式: 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 Unix and Windows, an object can appear in `object_list' if
     it is

        * a readable *note Connection: 23c0. object;

        * a connected and readable *note socket.socket: 679. object; or

        * the *note sentinel: a2a. attribute of a *note Process: 3b7.
          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.

     `Unix': ‘wait(object_list, timeout)’ almost equivalent
     ‘select.select(object_list, [], [], timeout)’.  The difference is
     that, if *note select.select(): 678. is interrupted by a signal, it
     can raise *note OSError: 1d4. with an error number of ‘EINTR’,
     whereas *note wait(): a29. 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 ‘fileno()’ 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(): a29. to wait for messages from
multiple processes at once:

     import time, random
     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(): 2416. 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<2>,  Prev: Listeners and Clients,  Up: Reference

5.17.2.24 Authentication keys
.............................

When one uses *note Connection.recv: 23d3, the data received is
automatically unpickled.  Unfortunately unpickling data from an
untrusted source is a security risk.  Therefore *note Listener: 2418.
and *note Client(): 2416. use the *note hmac: 8f. 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: 3b7.).  This value will be automatically inherited by any *note
Process: 3b7. 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(): 4d6.


File: python.info,  Node: Logging<2>,  Next: The multiprocessing dummy module,  Prev: Authentication keys,  Up: Reference

5.17.2.25 Logging
.................

Some support for logging is available.  Note, however, that the *note
logging: ab. 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: b8.  If
     necessary, a new one will be created.

     When first created the logger has level ‘logging.NOTSET’ 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 ()

     This function performs a call to *note get_logger(): 2420. but in
     addition to returning the logger created by get_logger, it adds a
     handler which sends output to *note sys.stderr: 314. using format
     ‘'[%(levelname)s/%(processName)s] %(message)s'’.

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: ab. module.


File: python.info,  Node: The multiprocessing dummy module,  Prev: Logging<2>,  Up: Reference

5.17.2.26 The ‘multiprocessing.dummy’ module
............................................

*note multiprocessing.dummy: ba. replicates the API of *note
multiprocessing: b8. but is no more than a wrapper around the *note
threading: 10a. module.

In particular, the ‘Pool’ function provided by *note
multiprocessing.dummy: ba. returns an instance of *note ThreadPool: ed2,
which is a subclass of *note Pool: 880. 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: ed2. instances are
     fully interface compatible with *note Pool: 880. instances, and
     their resources must also be properly managed, either by using the
     pool as a context manager or by calling *note close(): 2407. and
     *note terminate(): 2408. manually.

     `processes' is the number of worker threads to use.  If `processes'
     is ‘None’ then the number returned by *note os.cpu_count(): 884. is
     used.

     If `initializer' is not ‘None’ then each worker process will call
     ‘initializer(*initargs)’ when it starts.

     Unlike *note Pool: 880, `maxtasksperchild' and `context' cannot be
     provided.

               備註: A *note ThreadPool: ed2. shares the same interface
               as *note Pool: 880, which is designed around a pool of
               processes and predates the introduction of the *note
               concurrent.futures: 22. 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: 240b,
               that is not understood by any other libraries.

               Users should generally prefer to use *note
               concurrent.futures.ThreadPoolExecutor: 27b, which has a
               simpler interface that was designed around threads from
               the start, and which returns *note
               concurrent.futures.Future: b32. instances that are
               compatible with many other libraries, including *note
               asyncio: a.


File: python.info,  Node: Programming guidelines,  Next: Examples<10>,  Prev: Reference,  Up: multiprocessing --- Process-based parallelism

5.17.2.27 Programming guidelines
................................

There are certain guidelines and idioms which should be adhered to when
using *note multiprocessing: b8.

* 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 Unix 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(): 23cb. is called) all
     completed processes which have not yet been joined will be joined.
     Also calling a finished process’s *note Process.is_alive: 23aa.
     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: b8. 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: 23ae. 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: 23ae. 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: 23be. 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 Unix 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: 312. with a "file like object"

     *note multiprocessing: b8. 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():
     312. with a "file-like object" with output buffering.  This danger
     is that if multiple processes call *note close(): 1013. 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/issue5155

   (2) https://bugs.python.org/issue5313

   (3) https://bugs.python.org/issue5331


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 restriction 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: 3b7. then make sure that
     instances will be picklable when the *note Process.start: 238f.
     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: 238f. 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 a
     starting a new process).

     For example, using the `spawn' or `forkserver' start method running
     the following module would fail with a *note RuntimeError: 2bb.:

          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: Examples<10>,  Prev: Programming guidelines,  Up: multiprocessing --- Process-based parallelism

5.17.2.30 Examples
..................

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()

Using *note Pool: 880.:

     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 --- Provides shared memory for direct access across processes,  Next: The concurrent package,  Prev: multiprocessing --- Process-based parallelism,  Up: Concurrent Execution

5.17.3 ‘multiprocessing.shared_memory’ — Provides shared memory for direct access across processes
--------------------------------------------------------------------------------------------------

`Source code:' Lib/multiprocessing/shared_memory.py(1)

3.8 版新加入.

__________________________________________________________________

This module provides a class, *note SharedMemory: 2393, for the
allocation and management of shared memory to be accessed by one or more
processes on a multicore or symmetric multiprocessor (SMP) machine.  To
assist with the life-cycle management of shared memory especially across
distinct processes, a *note BaseManager: 23e9. subclass,
‘SharedMemoryManager’, is also provided in the
‘multiprocessing.managers’ module.

In this module, shared memory refers to "System V style" shared memory
blocks (though is not necessarily implemented explicitly as such) and
does not refer to "distributed shared memory".  This style of shared
memory permits distinct processes to potentially read and write to a
common (or shared) region of volatile memory.  Processes are
conventionally limited to only have access to their own process memory
space but shared memory permits the sharing of data between processes,
avoiding the need to instead send messages between processes containing
that data.  Sharing data directly via memory can provide significant
performance benefits compared to sharing data via disk or socket or
other communications requiring the serialization/deserialization and
copying of data.

 -- 類別: multiprocessing.shared_memory.SharedMemory (name=None,
          create=False, size=0)

     Creates a new shared memory block or attaches to an existing shared
     memory block.  Each shared memory block is assigned a unique name.
     In this way, one process can create a shared memory block with a
     particular name and a different process can attach to that same
     shared memory block using that same name.

     As a resource for sharing data across processes, shared memory
     blocks may outlive the original process that created them.  When
     one process no longer needs access to a shared memory block that
     might still be needed by other processes, the *note close(): 2429.
     method should be called.  When a shared memory block is no longer
     needed by any process, the *note unlink(): 242a. method should be
     called to ensure proper cleanup.

     `name' is the unique name for the requested shared memory,
     specified as a string.  When creating a new shared memory block, if
     ‘None’ (the default) is supplied for the name, a novel name will be
     generated.

     `create' controls whether a new shared memory block is created
     (‘True’) or an existing shared memory block is attached (‘False’).

     `size' specifies the requested number of bytes when creating a new
     shared memory block.  Because some platforms choose to allocate
     chunks of memory based upon that platform’s memory page size, the
     exact size of the shared memory block may be larger or equal to the
     size requested.  When attaching to an existing shared memory block,
     the ‘size’ parameter is ignored.

      -- 成員函式: close ()

          Closes access to the shared memory from this instance.  In
          order to ensure proper cleanup of resources, all instances
          should call ‘close()’ once the instance is no longer needed.
          Note that calling ‘close()’ does not cause the shared memory
          block itself to be destroyed.

      -- 成員函式: unlink ()

          Requests that the underlying shared memory block be destroyed.
          In order to ensure proper cleanup of resources, ‘unlink()’
          should be called once (and only once) across all processes
          which have need for the shared memory block.  After requesting
          its destruction, a shared memory block may or may not be
          immediately destroyed and this behavior may differ across
          platforms.  Attempts to access data inside the shared memory
          block after ‘unlink()’ has been called may result in memory
          access errors.  Note: the last process relinquishing its hold
          on a shared memory block may call ‘unlink()’ and *note
          close(): 2429. in either order.

      -- 屬性: buf

          A memoryview of contents of the shared memory block.

      -- 屬性: name

          Read-only access to the unique name of the shared memory
          block.

      -- 屬性: size

          Read-only access to size in bytes of the shared memory block.

The following example demonstrates low-level use of *note SharedMemory:
2393. instances:

     >>> 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

The following example demonstrates a practical use of the *note
SharedMemory: 2393. class with NumPy arrays(2), accessing the same
‘numpy.ndarray’ from two distinct Python shells:

     >>> # 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]])

     A subclass of *note BaseManager: 23e9. which can be used for the
     management of shared memory blocks across processes.

     A call to *note start(): 23ea. on a *note SharedMemoryManager:
     242e. instance causes a new process to be started.  This new
     process’s sole purpose is to manage the life cycle of all shared
     memory blocks created through it.  To trigger the release of all
     shared memory blocks managed by that process, call *note
     shutdown(): 23ee. on the instance.  This triggers a
     ‘SharedMemory.unlink()’ call on all of the *note SharedMemory:
     242f. objects managed by that process and then stops the process
     itself.  By creating ‘SharedMemory’ instances through a
     ‘SharedMemoryManager’, we avoid the need to manually track and
     trigger the freeing of shared memory resources.

     This class provides methods for creating and returning *note
     SharedMemory: 242f. instances and for creating a list-like object
     (*note ShareableList: 2430.) backed by shared memory.

     Refer to *note multiprocessing.managers.BaseManager: 23e9. for a
     description of the inherited `address' and `authkey' optional input
     arguments and how they may be used to connect to an existing
     ‘SharedMemoryManager’ service from other processes.

      -- 成員函式: SharedMemory (size)

          Create and return a new *note SharedMemory: 242f. object with
          the specified ‘size’ in bytes.

      -- 成員函式: ShareableList (sequence)

          Create and return a new *note ShareableList: 2430. object,
          initialized by the values from the input ‘sequence’.

The following example demonstrates the basic mechanisms of a
‘SharedMemoryManager’:

     >>> 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

The following example depicts a potentially more convenient pattern for
using ‘SharedMemoryManager’ objects via the *note with: 6ee. statement
to ensure that all shared memory blocks are released after they are no
longer needed:

     >>> 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

When using a ‘SharedMemoryManager’ in a *note with: 6ee. statement, the
shared memory blocks created using that manager are all released when
the *note with: 6ee. statement’s code block finishes execution.

 -- 類別: multiprocessing.shared_memory.ShareableList (sequence=None, *,
          name=None)

     Provides a mutable list-like object where all values stored within
     are stored in a shared memory block.  This constrains storable
     values to only the ‘int’, ‘float’, ‘bool’, ‘str’ (less than 10M
     bytes each), ‘bytes’ (less than 10M bytes each), and ‘None’
     built-in data types.  It also notably differs from the built-in
     ‘list’ type in that these lists can not change their overall length
     (i.e.  no append, insert, etc.)  and do not support the dynamic
     creation of new *note ShareableList: 2431. instances via slicing.

     `sequence' is used in populating a new ‘ShareableList’ full of
     values.  Set to ‘None’ to instead attach to an already existing
     ‘ShareableList’ by its unique shared memory name.

     `name' is the unique name for the requested shared memory, as
     described in the definition for *note SharedMemory: 2393.  When
     attaching to an existing ‘ShareableList’, specify its shared memory
     block’s unique name while leaving ‘sequence’ set to ‘None’.

      -- 成員函式: count (value)

          Returns the number of occurrences of ‘value’.

      -- 成員函式: index (value)

          Returns first index position of ‘value’.  Raises *note
          ValueError: 1fc. if ‘value’ is not present.

      -- 屬性: format

          Read-only attribute containing the *note struct: f9. packing
          format used by all currently stored values.

      -- 屬性: shm

          The *note SharedMemory: 2393. instance where the values are
          stored.

The following example demonstrates basic use of a *note ShareableList:
2431. instance:

     >>> 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

The following example depicts how one, two, or many processes may access
the same *note ShareableList: 2431. by supplying the name of the shared
memory block behind it:

     >>> 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()

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/multiprocessing/shared_memory.py

   (2) https://www.numpy.org/


File: python.info,  Node: The concurrent package,  Next: concurrent futures --- Launching parallel tasks,  Prev: multiprocessing shared_memory --- Provides shared memory for direct access across processes,  Up: Concurrent Execution

5.17.4 The ‘concurrent’ package
-------------------------------

Currently, there is only one module in this package:

   * *note concurrent.futures: 22. – Launching parallel tasks


File: python.info,  Node: concurrent futures --- Launching parallel tasks,  Next: subprocess --- Subprocess management,  Prev: The concurrent package,  Up: Concurrent Execution

5.17.5 ‘concurrent.futures’ — Launching parallel tasks
------------------------------------------------------

3.2 版新加入.

`Source code:' Lib/concurrent/futures/thread.py(1) and
Lib/concurrent/futures/process.py(2)

__________________________________________________________________

The *note concurrent.futures: 22. module provides a high-level interface
for asynchronously executing callables.

The asynchronous execution can be performed with threads, using *note
ThreadPoolExecutor: 27b, or separate processes, using *note
ProcessPoolExecutor: 2a5.  Both implement the same interface, which is
defined by the abstract *note Executor: 243a. class.

* Menu:

* Executor Objects::
* ThreadPoolExecutor::
* ProcessPoolExecutor::
* Future Objects::
* Module Functions::
* Exception classes::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/concurrent/futures/thread.py

   (2) 
https://github.com/python/cpython/tree/3.8/Lib/concurrent/futures/process.py


File: python.info,  Node: Executor Objects,  Next: ThreadPoolExecutor,  Up: concurrent futures --- Launching parallel tasks

5.17.5.1 Executor Objects
.........................

 -- 類別: concurrent.futures.Executor

     An abstract class that provides methods to execute calls
     asynchronously.  It should not be used directly, but through its
     concrete subclasses.

           -- 成員函式: submit (fn, *args, **kwargs)

               Schedules the callable, `fn', to be executed as ‘fn(*args
               **kwargs)’ and returns a *note Future: b32. object
               representing the execution of the callable.

                    with ThreadPoolExecutor(max_workers=1) as executor:
                        future = executor.submit(pow, 323, 1235)
                        print(future.result())

           -- 成員函式: map (func, *iterables, timeout=None,
                    chunksize=1)

               Similar to *note map(func, *iterables): c32. except:

                  * the `iterables' are collected immediately rather
                    than lazily;

                  * `func' is executed asynchronously and several calls
                    to `func' may be made concurrently.

               The returned iterator raises a *note
               concurrent.futures.TimeoutError: 243c. if *note
               __next__(): c69. is called and the result isn’t available
               after `timeout' seconds from the original call to *note
               Executor.map(): 6c3.  `timeout' can be an int or a float.
               If `timeout' is not specified or ‘None’, there is no
               limit to the wait time.

               If a `func' call raises an exception, then that exception
               will be raised when its value is retrieved from the
               iterator.

               When using *note ProcessPoolExecutor: 2a5, this method
               chops `iterables' into a number of chunks which it
               submits to the pool as separate tasks.  The (approximate)
               size of these chunks can be specified by setting
               `chunksize' to a positive integer.  For very long
               iterables, using a large value for `chunksize' can
               significantly improve performance compared to the default
               size of 1.  With *note ThreadPoolExecutor: 27b,
               `chunksize' has no effect.

               3.5 版更變: Added the `chunksize' argument.

           -- 成員函式: shutdown (wait=True)

               Signal the executor that it should free any resources
               that it is using when the currently pending futures are
               done executing.  Calls to *note Executor.submit(): 2a4.
               and *note Executor.map(): 6c3. made after shutdown will
               raise *note RuntimeError: 2bb.

               If `wait' is ‘True’ then this method will not return
               until all the pending futures are done executing and the
               resources associated with the executor have been freed.
               If `wait' is ‘False’ then this method will return
               immediately and the resources associated with the
               executor will be freed when all pending futures are done
               executing.  Regardless of the value of `wait', the entire
               Python program will not exit until all pending futures
               are done executing.

               You can avoid having to call this method explicitly if
               you use the *note with: 6ee. statement, which will
               shutdown the *note Executor: 243a. (waiting as if *note
               Executor.shutdown(): b33. were called with `wait' set to
               ‘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')


File: python.info,  Node: ThreadPoolExecutor,  Next: ProcessPoolExecutor,  Prev: Executor Objects,  Up: concurrent futures --- Launching parallel tasks

5.17.5.2 ThreadPoolExecutor
...........................

*note ThreadPoolExecutor: 27b. is an *note Executor: 243a. subclass that
uses a pool of threads to execute calls asynchronously.

Deadlocks can occur when the callable associated with a *note Future:
b32. waits on the results of another *note Future: b32.  For example:

     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)

And:

     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=())

     An *note Executor: 243a. subclass that uses a pool of at most
     `max_workers' threads to execute calls asynchronously.

     `initializer' is an optional callable that is called at the start
     of each worker thread; `initargs' is a tuple of arguments passed to
     the initializer.  Should `initializer' raise an exception, all
     currently pending jobs will raise a *note BrokenThreadPool: 243e,
     as well as any attempt to submit more jobs to the pool.

     3.5 版更變: If `max_workers' is ‘None’ or not given, it will
     default to the number of processors on the machine, multiplied by
     ‘5’, assuming that *note ThreadPoolExecutor: 27b. is often used to
     overlap I/O instead of CPU work and the number of workers should be
     higher than the number of workers for *note ProcessPoolExecutor:
     2a5.

     3.6 版新加入: The `thread_name_prefix' argument was added to allow
     users to control the *note threading.Thread: 236. names for worker
     threads created by the pool for easier debugging.

     3.7 版更變: Added the `initializer' and `initargs' arguments.

     3.8 版更變: Default value of `max_workers' is changed to ‘min(32,
     os.cpu_count() + 4)’.  This default value preserves at least 5
     workers for I/O bound tasks.  It utilizes at most 32 CPU cores for
     CPU bound tasks which release the GIL. And it avoids using very
     large resources implicitly on many-core machines.

     ThreadPoolExecutor now reuses idle worker threads before starting
     `max_workers' worker threads too.

* Menu:

* ThreadPoolExecutor Example::


File: python.info,  Node: ThreadPoolExecutor Example,  Up: ThreadPoolExecutor

5.17.5.3 ThreadPoolExecutor Example
...................................

     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://some-made-up-domain.com/']

     # 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 Objects,  Prev: ThreadPoolExecutor,  Up: concurrent futures --- Launching parallel tasks

5.17.5.4 ProcessPoolExecutor
............................

The *note ProcessPoolExecutor: 2a5. class is an *note Executor: 243a.
subclass that uses a pool of processes to execute calls asynchronously.
*note ProcessPoolExecutor: 2a5. uses the *note multiprocessing: b8.
module, which allows it to side-step the *note Global Interpreter Lock:
50b. but also means that only picklable objects can be executed and
returned.

The ‘__main__’ module must be importable by worker subprocesses.  This
means that *note ProcessPoolExecutor: 2a5. will not work in the
interactive interpreter.

Calling *note Executor: 243a. or *note Future: b32. methods from a
callable submitted to a *note ProcessPoolExecutor: 2a5. will result in
deadlock.

 -- 類別: concurrent.futures.ProcessPoolExecutor (max_workers=None,
          mp_context=None, initializer=None, initargs=())

     An *note Executor: 243a. 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 the number
     of processors on the machine.  If `max_workers' is less than or
     equal to ‘0’, then a *note ValueError: 1fc. will be raised.  On
     Windows, `max_workers' must be less than or equal to ‘61’.  If it
     is not then *note ValueError: 1fc. 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
     multiprocessing context or None.  It will be used to launch the
     workers.  If `mp_context' is ‘None’ or not given, the default
     multiprocessing context is used.

     `initializer' is an optional callable that is called at the start
     of each worker process; `initargs' is a tuple of arguments passed
     to the initializer.  Should `initializer' raise an exception, all
     currently pending jobs will raise a *note BrokenProcessPool: 2441,
     as well as any attempt to submit more jobs to the pool.

     3.3 版更變: When one of the worker processes terminates abruptly, a
     ‘BrokenProcessPool’ error is now raised.  Previously, behaviour was
     undefined but operations on the executor or its futures would often
     freeze or deadlock.

     3.7 版更變: The `mp_context' argument was added to allow users to
     control the start_method for worker processes created by the pool.

     Added the `initializer' and `initargs' arguments.

* Menu:

* ProcessPoolExecutor Example::


File: python.info,  Node: ProcessPoolExecutor Example,  Up: ProcessPoolExecutor

5.17.5.5 ProcessPoolExecutor Example
....................................

     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 Objects,  Next: Module Functions,  Prev: ProcessPoolExecutor,  Up: concurrent futures --- Launching parallel tasks

5.17.5.6 Future Objects
.......................

The *note Future: b32. class encapsulates the asynchronous execution of
a callable.  *note Future: b32. instances are created by *note
Executor.submit(): 2a4.

 -- 類別: concurrent.futures.Future

     Encapsulates the asynchronous execution of a callable.  *note
     Future: b32. instances are created by *note Executor.submit(): 2a4.
     and should not be created directly except for testing.

           -- 成員函式: cancel ()

               Attempt to cancel the call.  If the call is currently
               being executed or finished running and cannot be
               cancelled then the method will return ‘False’, otherwise
               the call will be cancelled and the method will return
               ‘True’.

           -- 成員函式: cancelled ()

               Return ‘True’ if the call was successfully cancelled.

           -- 成員函式: running ()

               Return ‘True’ if the call is currently being executed and
               cannot be cancelled.

           -- 成員函式: done ()

               Return ‘True’ if the call was successfully cancelled or
               finished running.

           -- 成員函式: result (timeout=None)

               Return the value returned by the call.  If the call
               hasn’t yet completed then this method will wait up to
               `timeout' seconds.  If the call hasn’t completed in
               `timeout' seconds, then a *note
               concurrent.futures.TimeoutError: 243c. will be raised.
               `timeout' can be an int or float.  If `timeout' is not
               specified or ‘None’, there is no limit to the wait time.

               If the future is cancelled before completing then *note
               CancelledError: 1ab. will be raised.

               If the call raised, this method will raise the same
               exception.

           -- 成員函式: exception (timeout=None)

               Return the exception raised by the call.  If the call
               hasn’t yet completed then this method will wait up to
               `timeout' seconds.  If the call hasn’t completed in
               `timeout' seconds, then a *note
               concurrent.futures.TimeoutError: 243c. will be raised.
               `timeout' can be an int or float.  If `timeout' is not
               specified or ‘None’, there is no limit to the wait time.

               If the future is cancelled before completing then *note
               CancelledError: 1ab. will be raised.

               If the call completed without raising, ‘None’ is
               returned.

           -- 成員函式: add_done_callback (fn)

               Attaches the callable `fn' to the future.  `fn' will be
               called, with the future as its only argument, when the
               future is cancelled or finishes running.

               Added callables are called in the order that they were
               added and are always called in a thread belonging to the
               process that added them.  If the callable raises an *note
               Exception: 1aa. subclass, it will be logged and ignored.
               If the callable raises a *note BaseException: 1a9.
               subclass, the behavior is undefined.

               If the future has already completed or been cancelled,
               `fn' will be called immediately.

     The following *note Future: b32. methods are meant for use in unit
     tests and *note Executor: 243a. implementations.

           -- 成員函式: set_running_or_notify_cancel ()

               This method should only be called by *note Executor:
               243a. implementations before executing the work
               associated with the *note Future: b32. and by unit tests.

               If the method returns ‘False’ then the *note Future: b32.
               was cancelled, i.e.  *note Future.cancel(): 2444. was
               called and returned ‘True’.  Any threads waiting on the
               *note Future: b32. completing (i.e.  through *note
               as_completed(): 10f3. or *note wait(): 244c.) will be
               woken up.

               If the method returns ‘True’ then the *note Future: b32.
               was not cancelled and has been put in the running state,
               i.e.  calls to *note Future.running(): 2446. will return
               ‘True’.

               This method can only be called once and cannot be called
               after *note Future.set_result(): 244d. or *note
               Future.set_exception(): 244e. have been called.

           -- 成員函式: set_result (result)

               Sets the result of the work associated with the *note
               Future: b32. to `result'.

               This method should only be used by *note Executor: 243a.
               implementations and unit tests.

               3.8 版更變: This method raises *note
               concurrent.futures.InvalidStateError: 244f. if the *note
               Future: b32. is already done.

           -- 成員函式: set_exception (exception)

               Sets the result of the work associated with the *note
               Future: b32. to the *note Exception: 1aa. `exception'.

               This method should only be used by *note Executor: 243a.
               implementations and unit tests.

               3.8 版更變: This method raises *note
               concurrent.futures.InvalidStateError: 244f. if the *note
               Future: b32. is already done.


File: python.info,  Node: Module Functions,  Next: Exception classes,  Prev: Future Objects,  Up: concurrent futures --- Launching parallel tasks

5.17.5.7 Module Functions
.........................

 -- 函式: concurrent.futures.wait (fs, timeout=None,
          return_when=ALL_COMPLETED)

     Wait for the *note Future: b32. instances (possibly created by
     different *note Executor: 243a. instances) given by `fs' to
     complete.  Returns a named 2-tuple of sets.  The first set, named
     ‘done’, contains the futures that completed (finished or cancelled
     futures) before the wait completed.  The second set, named
     ‘not_done’, contains the futures that did not complete (pending or
     running futures).

     `timeout' can be used to control the maximum number of seconds to
     wait before returning.  `timeout' can be an int or float.  If
     `timeout' is not specified or ‘None’, there is no limit to the wait
     time.

     `return_when' indicates when this function should return.  It must
     be one of the following constants:

     Constant                          描述
                                       
     -------------------------------------------------------------------------------
                                       
     ‘FIRST_COMPLETED’                 The function will return when any future
                                       finishes or is cancelled.
                                       
                                       
     ‘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 ‘ALL_COMPLETED’.
                                       
                                       
     ‘ALL_COMPLETED’                   The function will return when all futures
                                       finish or are cancelled.
                                       

 -- 函式: concurrent.futures.as_completed (fs, timeout=None)

     Returns an iterator over the *note Future: b32. instances (possibly
     created by different *note Executor: 243a. instances) given by `fs'
     that yields futures as they complete (finished or cancelled
     futures).  Any futures given by `fs' that are duplicated will be
     returned once.  Any futures that completed before *note
     as_completed(): 10f3. is called will be yielded first.  The
     returned iterator raises a *note concurrent.futures.TimeoutError:
     243c. if *note __next__(): c69. is called and the result isn’t
     available after `timeout' seconds from the original call to *note
     as_completed(): 10f3.  `timeout' can be an int or float.  If
     `timeout' is not specified or ‘None’, there is no limit to the wait
     time.

也參考
......

PEP 3148(1) – futures - execute computations asynchronously

     The proposal which described this feature for inclusion in the
     Python standard library.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3148


File: python.info,  Node: Exception classes,  Prev: Module Functions,  Up: concurrent futures --- Launching parallel tasks

5.17.5.8 Exception classes
..........................

 -- 例外: concurrent.futures.CancelledError

     Raised when a future is cancelled.

 -- 例外: concurrent.futures.TimeoutError

     Raised when a future operation exceeds the given timeout.

 -- 例外: concurrent.futures.BrokenExecutor

     Derived from *note RuntimeError: 2bb, this exception class is
     raised when an executor is broken for some reason, and cannot be
     used to submit or execute new tasks.

     3.7 版新加入.

 -- 例外: concurrent.futures.InvalidStateError

     Raised when an operation is performed on a future that is not
     allowed in the current state.

     3.8 版新加入.

 -- 例外: concurrent.futures.thread.BrokenThreadPool

     Derived from *note BrokenExecutor: 2452, this exception class is
     raised when one of the workers of a ‘ThreadPoolExecutor’ has failed
     initializing.

     3.7 版新加入.

 -- 例外: concurrent.futures.process.BrokenProcessPool

     Derived from *note BrokenExecutor: 2452. (formerly *note
     RuntimeError: 2bb.), this exception class is raised when one of the
     workers of a ‘ProcessPoolExecutor’ has terminated in a non-clean
     fashion (for example, if it was killed from the outside).

     3.3 版新加入.


File: python.info,  Node: subprocess --- Subprocess management,  Next: sched --- Event scheduler,  Prev: concurrent futures --- Launching parallel tasks,  Up: Concurrent Execution

5.17.6 ‘subprocess’ — Subprocess management
-------------------------------------------

`Source code:' Lib/subprocess.py(1)

__________________________________________________________________

The *note subprocess: fa. 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: fa. module can be used to
replace these modules and functions can be found in the following
sections.

也參考
......

PEP 324(2) – PEP proposing the subprocess module

* Menu:

* Using the subprocess Module::
* Security Considerations::
* 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.8/Lib/subprocess.py

   (2) https://www.python.org/dev/peps/pep-0324


File: python.info,  Node: Using the subprocess Module,  Next: Security Considerations,  Up: subprocess --- Subprocess management

5.17.6.1 Using the ‘subprocess’ Module
......................................

The recommended approach to invoking subprocesses is to use the *note
run(): 3f2. function for all use cases it can handle.  For more advanced
use cases, the underlying *note Popen: 2ba. interface can be used
directly.

The *note run(): 3f2. function was added in Python 3.5; if you need to
retain compatibility with older versions, see the *note Older high-level
API: 2456. section.

 -- 函式: 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: 765. instance.

     The arguments shown above are merely the most common ones,
     described below in *note Frequently Used Arguments: 2457. (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: 2ba. 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: 2ba. object is automatically
     created with ‘stdout=PIPE’ and ‘stderr=PIPE’.  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, use ‘stdout=PIPE’ and ‘stderr=STDOUT’ instead of
     `capture_output'.

     The `timeout' argument is passed to *note Popen.communicate():
     2458.  If the timeout expires, the child process will be killed and
     waited for.  The *note TimeoutExpired: 2459. exception will be
     re-raised after the child process has terminated.

     The `input' argument is passed to *note Popen.communicate(): 2458.
     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: 2ba. object
     is automatically created with ‘stdin=PIPE’, 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: cba. 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: 5f8. 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: 2ba.

     Examples:

          >>> subprocess.run(["ls", "-l"])  # doesn't capture output
          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 版更變: Added `encoding' and `errors' parameters

     3.7 版更變: Added the `text' parameter, as a more understandable
     alias of `universal_newlines'.  Added the `capture_output'
     parameter.

 -- 類別: subprocess.CompletedProcess

     The return value from *note run(): 3f2, 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(): 3f2. 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: 245d. will be ‘None’.

      -- 屬性: stderr

          Captured stderr from the child process.  A bytes sequence, or
          a string if *note run(): 3f2. was called with an encoding,
          errors, or text=True.  ‘None’ if stderr was not captured.

      -- 成員函式: check_returncode ()

          If *note returncode: 245b. is non-zero, raise a *note
          CalledProcessError: cba.

     3.5 版新加入.

 -- Data: subprocess.DEVNULL

     Special value that can be used as the `stdin', `stdout' or `stderr'
     argument to *note Popen: 2ba. and indicates that the special file
     *note os.devnull: 101f. will be used.

     3.3 版新加入.

 -- Data: subprocess.PIPE

     Special value that can be used as the `stdin', `stdout' or `stderr'
     argument to *note Popen: 2ba. and indicates that a pipe to the
     standard stream should be opened.  Most useful with *note
     Popen.communicate(): 2458.

 -- Data: subprocess.STDOUT

     Special value that can be used as the `stderr' argument to *note
     Popen: 2ba. 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: 2460, 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():
          3f2. or *note check_output(): 8e0.  Otherwise, ‘None’.

      -- 屬性: stdout

          Alias for output, for symmetry with *note stderr: 2465.

      -- 屬性: stderr

          Stderr output of the child process if it was captured by *note
          run(): 3f2.  Otherwise, ‘None’.

     3.3 版新加入.

     3.5 版更變: `stdout' and `stderr' attributes added

 -- 例外: subprocess.CalledProcessError

     Subclass of *note SubprocessError: 2460, raised when a process run
     by *note check_call(): 2466. or *note check_output(): 8e0. 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():
          3f2. or *note check_output(): 8e0.  Otherwise, ‘None’.

      -- 屬性: stdout

          Alias for output, for symmetry with *note stderr: 246b.

      -- 屬性: stderr

          Stderr output of the child process if it was captured by *note
          run(): 3f2.  Otherwise, ‘None’.

     3.5 版更變: `stdout' and `stderr' attributes added

* Menu:

* Frequently Used Arguments::
* Popen Constructor::
* Exceptions: Exceptions<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: 2ba.
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: 49e. (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 *note PIPE: 3f3, *note DEVNULL:
     aa5, an existing file descriptor (a positive integer), an existing
     file object, and ‘None’.  *note PIPE: 3f3. indicates that a new
     pipe to the child should be created.  *note DEVNULL: aa5. indicates
     that the special file *note os.devnull: 101f. will be used.  With
     the default settings of ‘None’, no redirection will occur; the
     child’s file handles will be inherited from the parent.
     Additionally, `stderr' can be *note STDOUT: 245f, 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: 5f8.

     For `stdin', line ending characters ‘'\n'’ in the input will be
     converted to the default line separator *note os.linesep: 1601.
     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: 5f8. 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 版新加入: Added `encoding' and `errors' parameters.

     3.7 版新加入: Added the `text' parameter as an alias for
     `universal_newlines'.

          備註: The newlines attribute of the file objects *note
          Popen.stdin: 246d, *note Popen.stdout: 246e. and *note
          Popen.stderr: 246f. are not updated by the *note
          Popen.communicate(): 2458. 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: 8a, *note fnmatch:
     81, *note os.walk(): 659, *note os.path.expandvars(): d49, *note
     os.path.expanduser(): 1ff, and *note shutil: ea.).

     3.3 版更變: When `universal_newlines' is ‘True’, the class uses the
     encoding *note locale.getpreferredencoding(False): 3aa. instead of
     ‘locale.getpreferredencoding()’.  See the *note io.TextIOWrapper:
     5f8. class for more information on this change.

          備註: Read the *note Security Considerations: 2470. section
          before using ‘shell=True’.

These options, along with all of the other options, are described in
more detail in the *note Popen: 2ba. constructor documentation.


File: python.info,  Node: Popen Constructor,  Next: Exceptions<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: 2ba. 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=(), *,
          encoding=None, errors=None, text=None)

     Execute a child program in a new process.  On POSIX, the class uses
     *note os.execvp(): 1f94.-like behavior to execute the child
     program.  On Windows, the class uses the Windows ‘CreateProcess()’
     function.  The arguments to *note Popen: 2ba. are as follows.

     `args' should be a sequence of program arguments or else a single
     string or *note path-like object: 36f.  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.

     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(): 219. 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) # Success!

          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: 2472.  This is because the
     underlying ‘CreateProcess()’ operates on strings.

     3.6 版更變: `args' parameter accepts a *note path-like object: 36f.
     if `shell' is ‘False’ and a sequence containing path-like objects
     on POSIX.

     3.8 版更變: `args' parameter accepts a *note path-like object: 36f.
     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: 2ba. 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: 2470. section
          before using ‘shell=True’.

     `bufsize' will be supplied as the corresponding argument to the
     *note open(): 4f5. 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
          ‘universal_newlines=True’ i.e., in a text mode)

        - 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: 36f. on POSIX.

     3.8 版更變: `executable' parameter accepts a bytes and *note
     path-like object: 36f. on Windows.

     `stdin', `stdout' and `stderr' specify the executed program’s
     standard input, standard output and standard error file handles,
     respectively.  Valid values are *note PIPE: 3f3, *note DEVNULL:
     aa5, an existing file descriptor (a positive integer), an existing
     *note file object: b47, and ‘None’.  *note PIPE: 3f3. indicates
     that a new pipe to the child should be created.  *note DEVNULL:
     aa5. indicates that the special file *note os.devnull: 101f. will
     be used.  With the default settings of ‘None’, no redirection will
     occur; the child’s file handles will be inherited from the parent.
     Additionally, `stderr' can be *note STDOUT: 245f, 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 must use it,
          keep it trivial!  Minimize the number of libraries you call
          into.

          備註: 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' parameter can take the place of a
          previously common use of `preexec_fn' to call os.setsid() 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: 2bb.  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: 7ff.

     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: 49f, or
     by standard handle redirection.

     3.2 版更變: The default for `close_fds' was changed from *note
     False: 38d. to what is described above.

     3.7 版更變: On Windows the default for `close_fds' was changed from
     *note False: 38d. to *note True: 49e. when redirecting the standard
     handles.  It’s now possible to set `close_fds' to *note True: 49e.
     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: 49e.  (POSIX only)

     3.2 版更變: The `pass_fds' parameter was added.

     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: 36f. object.  In particular, 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: 36f.
     on POSIX.

     3.7 版更變: `cwd' parameter accepts a *note path-like object: 36f.
     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' was added.

     If `start_new_session' is true the setsid() system call will be
     made in the child process prior to the execution of the subprocess.
     (POSIX only)

     3.2 版更變: `start_new_session' was added.

     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.

          備註: 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: 2457.  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' and `errors' were added.

     3.7 版新加入: `text' was added as a more readable alias for
     `universal_newlines'.

     If given, `startupinfo' will be a *note STARTUPINFO: 2473. object,
     which is passed to the underlying ‘CreateProcess’ function.
     `creationflags', if given, can be one or more of the following
     flags:

             * *note CREATE_NEW_CONSOLE: 2474.

             * *note CREATE_NEW_PROCESS_GROUP: 2475.

             * *note ABOVE_NORMAL_PRIORITY_CLASS: 2476.

             * *note BELOW_NORMAL_PRIORITY_CLASS: 2477.

             * *note HIGH_PRIORITY_CLASS: 2478.

             * *note IDLE_PRIORITY_CLASS: 2479.

             * *note NORMAL_PRIORITY_CLASS: 247a.

             * *note REALTIME_PRIORITY_CLASS: 247b.

             * *note CREATE_NO_WINDOW: 247c.

             * *note DETACHED_PROCESS: 247d.

             * *note CREATE_DEFAULT_ERROR_MODE: 247e.

             * *note CREATE_BREAKAWAY_FROM_JOB: 247f.

     Popen objects are supported as context managers via the *note with:
     6ee. 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: e96. ‘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 版更變: Added context manager support.

     3.6 版更變: Popen destructor now emits a *note ResourceWarning:
     4d5. warning if the child process is still running.

     3.8 版更變: Popen can use *note os.posix_spawn(): 258. in some
     cases for better performance.  On Windows Subsystem for Linux and
     QEMU User Emulation, Popen constructor using *note
     os.posix_spawn(): 258. no longer raise an exception on errors like
     missing program, but the child process fails with a non-zero *note
     returncode: 2480.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Side-by-Side_Assembly


File: python.info,  Node: Exceptions<6>,  Prev: Popen Constructor,  Up: Using the subprocess Module

5.17.6.4 Exceptions
...................

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: 1d4.  This occurs,
for example, when trying to execute a non-existent file.  Applications
should prepare for *note OSError: 1d4. exceptions.

A *note ValueError: 1fc. will be raised if *note Popen: 2ba. is called
with invalid arguments.

*note check_call(): 2466. and *note check_output(): 8e0. will raise
*note CalledProcessError: cba. if the called process returns a non-zero
return code.

All of the functions and methods that accept a `timeout' parameter, such
as *note call(): 3f4. and *note Popen.communicate(): 2458. will raise
*note TimeoutExpired: 2459. if the timeout expires before the process
exits.

Exceptions defined in this module all inherit from *note
SubprocessError: 2460.

     3.3 版新加入: The *note SubprocessError: 2460. base class was
     added.


File: python.info,  Node: Security Considerations,  Next: Popen Objects,  Prev: Using the subprocess Module,  Up: subprocess --- Subprocess management

5.17.6.5 Security Considerations
................................

Unlike some other popen functions, this implementation will never
implicitly 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.

When using ‘shell=True’, the *note shlex.quote(): a78. function can be
used to properly escape whitespace and shell metacharacters in strings
that are going to be used to construct shell commands.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Shell_injection#Shell_injection


File: python.info,  Node: Popen Objects,  Next: Windows Popen Helpers,  Prev: Security Considerations,  Up: subprocess --- Subprocess management

5.17.6.6 Popen Objects
......................

Instances of the *note Popen: 2ba. class have the following methods:

 -- 成員函式: Popen.poll ()

     Check if child process has terminated.  Set and return *note
     returncode: 2480. attribute.  Otherwise, returns ‘None’.

 -- 成員函式: Popen.wait (timeout=None)

     Wait for child process to terminate.  Set and return *note
     returncode: 2480. attribute.

     If the process does not terminate after `timeout' seconds, raise a
     *note TimeoutExpired: 2459. 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(): 2458. when
          using pipes to avoid that.

          備註: The function is implemented using a busy loop
          (non-blocking call and short sleeps).  Use the *note asyncio:
          a. module for an asynchronous wait: see *note
          asyncio.create_subprocess_exec: 292.

     3.3 版更變: `timeout' was added.

 -- 成員函式: 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: 2480. 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(): 2458. 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: 2459. 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' was added.

 -- 成員函式: Popen.send_signal (signal)

     Sends the signal `signal' to the child.

          備註: On Windows, SIGTERM is an alias for *note terminate():
          2485.  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 SIGTERM 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(): 2486. is an alias for *note
     terminate(): 2485.

The following attributes are also available:

 -- 屬性: Popen.args

     The `args' argument as it was passed to *note Popen: 2ba. – a
     sequence of program arguments or else a single string.

     3.3 版新加入.

 -- 屬性: Popen.stdin

     If the `stdin' argument was *note PIPE: 3f3, this attribute is a
     writeable stream object as returned by *note open(): 4f5.  If the
     `encoding' or `errors' arguments were specified or the
     `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: 3f3, this attribute is ‘None’.

 -- 屬性: Popen.stdout

     If the `stdout' argument was *note PIPE: 3f3, this attribute is a
     readable stream object as returned by *note open(): 4f5.  Reading
     from the stream provides output from the child process.  If the
     `encoding' or `errors' arguments were specified or the
     `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: 3f3, this attribute is ‘None’.

 -- 屬性: Popen.stderr

     If the `stderr' argument was *note PIPE: 3f3, this attribute is a
     readable stream object as returned by *note open(): 4f5.  Reading
     from the stream provides error output from the child process.  If
     the `encoding' or `errors' arguments were specified or the
     `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: 3f3, this attribute is ‘None’.

     警告: Use *note communicate(): 2458. rather than *note
     .stdin.write: 246d, *note .stdout.read: 246e. or *note
     .stderr.read: 246f. 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, set by *note poll(): 2483. and *note wait():
     597. (and indirectly by *note communicate(): 2458.).  A ‘None’
     value indicates that the process hasn’t terminated yet.

     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 --- Subprocess management

5.17.6.7 Windows Popen Helpers
..............................

The *note STARTUPINFO: 2473. 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: 2ba. 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:
          2473. attributes are used when the process creates a window.

               si = subprocess.STARTUPINFO()
               si.dwFlags = subprocess.STARTF_USESTDHANDLES | subprocess.STARTF_USESHOWWINDOW

      -- 屬性: hStdInput

          If *note dwFlags: 248a. specifies *note STARTF_USESTDHANDLES:
          248c, this attribute is the standard input handle for the
          process.  If *note STARTF_USESTDHANDLES: 248c. is not
          specified, the default for standard input is the keyboard
          buffer.

      -- 屬性: hStdOutput

          If *note dwFlags: 248a. specifies *note STARTF_USESTDHANDLES:
          248c, 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: 248a. specifies *note STARTF_USESTDHANDLES:
          248c, 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: 248a. specifies *note STARTF_USESHOWWINDOW:
          2490, 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: 2491. is provided for this attribute.  It is
          used when *note Popen: 2ba. 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(): 803. when passed to the
               *note Popen: 2ba. constructor, else *note OSError: 1d4.
               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(): dc6.  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: fa. module exposes the following constants.

 -- Data: subprocess.STD_INPUT_HANDLE

     The standard input device.  Initially, this is the console input
     buffer, ‘CONIN$’.

 -- Data: subprocess.STD_OUTPUT_HANDLE

     The standard output device.  Initially, this is the active console
     screen buffer, ‘CONOUT$’.

 -- Data: subprocess.STD_ERROR_HANDLE

     The standard error device.  Initially, this is the active console
     screen buffer, ‘CONOUT$’.

 -- Data: subprocess.SW_HIDE

     Hides the window.  Another window will be activated.

 -- Data: subprocess.STARTF_USESTDHANDLES

     Specifies that the *note STARTUPINFO.hStdInput: 248b, *note
     STARTUPINFO.hStdOutput: 248d, and *note STARTUPINFO.hStdError:
     248e. attributes contain additional information.

 -- Data: subprocess.STARTF_USESHOWWINDOW

     Specifies that the *note STARTUPINFO.wShowWindow: 248f. attribute
     contains additional information.

 -- Data: subprocess.CREATE_NEW_CONSOLE

     The new process has a new console, instead of inheriting its
     parent’s console (the default).

 -- Data: subprocess.CREATE_NEW_PROCESS_GROUP

     A *note Popen: 2ba. ‘creationflags’ parameter to specify that a new
     process group will be created.  This flag is necessary for using
     *note os.kill(): cf8. on the subprocess.

     This flag is ignored if *note CREATE_NEW_CONSOLE: 2474. is
     specified.

 -- Data: subprocess.ABOVE_NORMAL_PRIORITY_CLASS

     A *note Popen: 2ba. ‘creationflags’ parameter to specify that a new
     process will have an above average priority.

     3.7 版新加入.

 -- Data: subprocess.BELOW_NORMAL_PRIORITY_CLASS

     A *note Popen: 2ba. ‘creationflags’ parameter to specify that a new
     process will have a below average priority.

     3.7 版新加入.

 -- Data: subprocess.HIGH_PRIORITY_CLASS

     A *note Popen: 2ba. ‘creationflags’ parameter to specify that a new
     process will have a high priority.

     3.7 版新加入.

 -- Data: subprocess.IDLE_PRIORITY_CLASS

     A *note Popen: 2ba. ‘creationflags’ parameter to specify that a new
     process will have an idle (lowest) priority.

     3.7 版新加入.

 -- Data: subprocess.NORMAL_PRIORITY_CLASS

     A *note Popen: 2ba. ‘creationflags’ parameter to specify that a new
     process will have an normal priority.  (default)

     3.7 版新加入.

 -- Data: subprocess.REALTIME_PRIORITY_CLASS

     A *note Popen: 2ba. ‘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 版新加入.

 -- Data: subprocess.CREATE_NO_WINDOW

     A *note Popen: 2ba. ‘creationflags’ parameter to specify that a new
     process will not create a window.

     3.7 版新加入.

 -- Data: subprocess.DETACHED_PROCESS

     A *note Popen: 2ba. ‘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 版新加入.

 -- Data: subprocess.CREATE_DEFAULT_ERROR_MODE

     A *note Popen: 2ba. ‘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 版新加入.

 -- Data: subprocess.CREATE_BREAKAWAY_FROM_JOB

     A *note Popen: 2ba. ‘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 --- Subprocess management

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(): 3f2. 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: 2480. attribute.

     Code needing to capture stdout or stderr should use *note run():
     3f2. instead:

          run(...).returncode

     To suppress stdout or stderr, supply a value of *note DEVNULL: aa5.

     The arguments shown above are merely some common ones.  The full
     function signature is the same as that of the *note Popen: 2ba.
     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' was added.

 -- 函式: 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: cba.  The *note CalledProcessError: cba. object
     will have the return code in the *note returncode: 2467. attribute.

     Code needing to capture stdout or stderr should use *note run():
     3f2. instead:

          run(..., check=True)

     To suppress stdout or stderr, supply a value of *note DEVNULL: aa5.

     The arguments shown above are merely some common ones.  The full
     function signature is the same as that of the *note Popen: 2ba.
     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' was added.

 -- 函式: 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: cba.  The *note CalledProcessError: cba. object
     will have the return code in the *note returncode: 2467. attribute
     and any output in the *note output: 2469. attribute.

     This is equivalent to:

          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(): 3f2.
     - most arguments are passed directly through to that interface.
     One API deviation from *note run(): 3f2. 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: 2457. and *note run(): 3f2.

     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' was added.

     3.4 版更變: Support for the `input' keyword argument was added.

     3.6 版更變: `encoding' and `errors' were added.  See *note run():
     3f2. for details.

     3.7 版新加入: `text' was added as a more readable alias for
     `universal_newlines'.


File: python.info,  Node: Replacing Older Functions with the subprocess Module,  Next: Legacy Shell Invocation Functions,  Prev: Older high-level API,  Up: subprocess --- Subprocess management

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: 1d4. instead.

     In addition, the replacements using *note check_output(): 8e0. will
     fail with a *note CalledProcessError: cba. if the requested
     operation produces a non-zero return code.  The output is still
     available as the *note output: 2469. attribute of the raised
     exception.

In the following examples, we assume that the relevant functions have
already been imported from the *note subprocess: fa. 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)

becomes:

     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)

becomes:

     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)

becomes:

     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")
     # becomes
     sts = call("mycmd" + " myarg", shell=True)

註解：

   * Calling the program through the shell is usually not required.

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 example:

     pid = os.spawnlp(os.P_NOWAIT, "/bin/mycmd", "mycmd", "myarg")
     ==>
     pid = Popen(["/bin/mycmd", "myarg"]).pid

P_WAIT example:

     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: 2ba, except that:

   * *note Popen: 2ba. 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: 2ba. 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 --- Subprocess management

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)

     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)’.  The locale encoding is
     used; see the notes on *note Frequently Used Arguments: 2457. 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 Availability: 1364.: POSIX & Windows.

     3.3.4 版更變: Windows support was added.

     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: 2480.

 -- 函式: subprocess.getoutput (cmd)

     Return output (stdout and stderr) of executing `cmd' in a shell.

     Like *note getstatusoutput(): 8e1, 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 Availability: 1364.: POSIX & Windows.

     3.3.4 版更變: Windows support added


File: python.info,  Node: 註解,  Prev: Legacy Shell Invocation Functions,  Up: subprocess --- Subprocess management

5.17.6.18 註解
..............

* Menu:

* Converting an argument sequence to a string on Windows::


File: python.info,  Node: Converting an argument sequence to a string on Windows,  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: e9.

     Module which provides function to parse and escape command lines.


File: python.info,  Node: sched --- Event scheduler,  Next: queue --- A synchronized queue class,  Prev: subprocess --- Subprocess management,  Up: Concurrent Execution

5.17.7 ‘sched’ — Event scheduler
--------------------------------

`Source code:' Lib/sched.py(1)

__________________________________________________________________

The *note sched: e4. module defines a class which implements a general
purpose event scheduler:

 -- 類別: sched.scheduler (timefunc=time.monotonic,
          delayfunc=time.sleep)

     The *note scheduler: a73. class defines a generic interface to
     scheduling events.  It needs two functions to actually deal with
     the "outside world" — `timefunc' should be callable without
     arguments, and return a number (the "time", in any units
     whatsoever).  The `delayfunc' function should be callable with one
     argument, compatible with the output of `timefunc', and should
     delay that many time units.  `delayfunc' will also be called with
     the argument ‘0’ after each event is run to allow other threads an
     opportunity to run in multi-threaded applications.

     3.3 版更變: `timefunc' and `delayfunc' parameters are optional.

     3.3 版更變: *note scheduler: a73. class can be safely used in
     multi-threaded environments.

Example:

     >>> 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',))
     ...     s.enter(5, 1, print_time, kwargs={'a': 'keyword'})
     ...     s.run()
     ...     print(time.time())
     ...
     >>> print_some_times()
     930343690.257
     From print_time 930343695.274 positional
     From print_time 930343695.275 keyword
     From print_time 930343700.273 default
     930343700.276

* Menu:

* Scheduler Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/sched.py


File: python.info,  Node: Scheduler Objects,  Up: sched --- Event scheduler

5.17.7.1 Scheduler Objects
..........................

*note scheduler: a73. instances have the following methods and
attributes:

 -- 成員函式: scheduler.enterabs (time, priority, action, argument=(),
          kwargs={})

     Schedule a new event.  The `time' argument should be a numeric type
     compatible with the return value of the `timefunc' function passed
     to the constructor.  Events scheduled for the same `time' will be
     executed in the order of their `priority'.  A lower number
     represents a higher priority.

     Executing the event means executing ‘action(*argument, **kwargs)’.
     `argument' is a sequence holding the positional arguments for
     `action'.  `kwargs' is a dictionary holding the keyword arguments
     for `action'.

     Return value is an event which may be used for later cancellation
     of the event (see *note cancel(): 24a6.).

     3.3 版更變: `argument' parameter is optional.

     3.3 版更變: `kwargs' parameter was added.

 -- 成員函式: scheduler.enter (delay, priority, action, argument=(),
          kwargs={})

     Schedule an event for `delay' more time units.  Other than the
     relative time, the other arguments, the effect and the return value
     are the same as those for *note enterabs(): a75.

     3.3 版更變: `argument' parameter is optional.

     3.3 版更變: `kwargs' parameter was added.

 -- 成員函式: scheduler.cancel (event)

     Remove the event from the queue.  If `event' is not an event
     currently in the queue, this method will raise a *note ValueError:
     1fc.

 -- 成員函式: scheduler.empty ()

     Return ‘True’ if the event queue is empty.

 -- 成員函式: scheduler.run (blocking=True)

     Run all scheduled events.  This method will wait (using the
     ‘delayfunc()’ function passed to the constructor) for the next
     event, then execute it and so on until there are no more scheduled
     events.

     If `blocking' is false executes the scheduled events due to expire
     soonest (if any) and then return the deadline of the next scheduled
     call in the scheduler (if any).

     Either `action' or `delayfunc' can raise an exception.  In either
     case, the scheduler will maintain a consistent state and propagate
     the exception.  If an exception is raised by `action', the event
     will not be attempted in future calls to *note run(): a72.

     If a sequence of events takes longer to run than the time available
     before the next event, the scheduler will simply fall behind.  No
     events will be dropped; the calling code is responsible for
     canceling events which are no longer pertinent.

     3.3 版更變: `blocking' parameter was added.

 -- 屬性: scheduler.queue

     Read-only attribute returning a list of upcoming events in the
     order they will be run.  Each event is shown as a *note named
     tuple: aa8. with the following fields: time, priority, action,
     argument, kwargs.


File: python.info,  Node: queue --- A synchronized queue class,  Next: contextvars --- Context Variables,  Prev: sched --- Event scheduler,  Up: Concurrent Execution

5.17.8 ‘queue’ — A synchronized queue class
-------------------------------------------

`Source code:' Lib/queue.py(1)

__________________________________________________________________

The *note queue: db. module implements multi-producer, multi-consumer
queues.  It is especially useful in threaded programming when
information must be exchanged safely between multiple threads.  The
*note Queue: d1d. class in this module implements all the required
locking semantics.

The module implements three types of queue, which differ only in the
order in which the entries are retrieved.  In a FIFO queue, the first
tasks added are the first retrieved.  In a LIFO queue, the most recently
added entry is the first retrieved (operating like a stack).  With a
priority queue, the entries are kept sorted (using the *note heapq: 8e.
module) and the lowest valued entry is retrieved first.

Internally, those three types of queues use locks to temporarily block
competing threads; however, they are not designed to handle reentrancy
within a thread.

In addition, the module implements a "simple" FIFO queue type, *note
SimpleQueue: 3cb, whose specific implementation provides additional
guarantees in exchange for the smaller functionality.

The *note queue: db. module defines the following classes and
exceptions:

 -- 類別: queue.Queue (maxsize=0)

     Constructor for a FIFO queue.  `maxsize' is an integer that sets
     the upperbound limit on the number of items that can be placed in
     the queue.  Insertion will block once this size has been reached,
     until queue items are consumed.  If `maxsize' is less than or equal
     to zero, the queue size is infinite.

 -- 類別: queue.LifoQueue (maxsize=0)

     Constructor for a LIFO queue.  `maxsize' is an integer that sets
     the upperbound limit on the number of items that can be placed in
     the queue.  Insertion will block once this size has been reached,
     until queue items are consumed.  If `maxsize' is less than or equal
     to zero, the queue size is infinite.

 -- 類別: queue.PriorityQueue (maxsize=0)

     Constructor for a priority queue.  `maxsize' is an integer that
     sets the upperbound limit on the number of items that can be placed
     in the queue.  Insertion will block once this size has been
     reached, until queue items are consumed.  If `maxsize' is less than
     or equal to zero, the queue size is infinite.

     The lowest valued entries are retrieved first (the lowest valued
     entry is the one returned by ‘sorted(list(entries))[0]’).  A
     typical pattern for entries is a tuple in the form:
     ‘(priority_number, data)’.

     If the `data' elements are not comparable, the data can be wrapped
     in a class that ignores the data item and only compares the
     priority number:

          from dataclasses import dataclass, field
          from typing import Any

          @dataclass(order=True)
          class PrioritizedItem:
              priority: int
              item: Any=field(compare=False)

 -- 類別: queue.SimpleQueue

     Constructor for an unbounded FIFO queue.  Simple queues lack
     advanced functionality such as task tracking.

     3.7 版新加入.

 -- 例外: queue.Empty

     Exception raised when non-blocking *note get(): 24ad. (or *note
     get_nowait(): 24ae.) is called on a *note Queue: d1d. object which
     is empty.

 -- 例外: queue.Full

     Exception raised when non-blocking *note put(): 24af. (or *note
     put_nowait(): 24b0.) is called on a *note Queue: d1d. object which
     is full.

* Menu:

* Queue Objects::
* SimpleQueue Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/queue.py


File: python.info,  Node: Queue Objects,  Next: SimpleQueue Objects,  Up: queue --- A synchronized queue class

5.17.8.1 Queue Objects
......................

Queue objects (*note Queue: d1d, *note LifoQueue: 24ab, or *note
PriorityQueue: 24ac.) provide the public methods described below.

 -- 成員函式: Queue.qsize ()

     Return the approximate size of the queue.  Note, qsize() > 0
     doesn’t guarantee that a subsequent get() will not block, nor will
     qsize() < maxsize guarantee that put() will not block.

 -- 成員函式: Queue.empty ()

     Return ‘True’ if the queue is empty, ‘False’ otherwise.  If empty()
     returns ‘True’ it doesn’t guarantee that a subsequent call to put()
     will not block.  Similarly, if empty() returns ‘False’ it doesn’t
     guarantee that a subsequent call to get() will not block.

 -- 成員函式: Queue.full ()

     Return ‘True’ if the queue is full, ‘False’ otherwise.  If full()
     returns ‘True’ it doesn’t guarantee that a subsequent call to get()
     will not block.  Similarly, if full() returns ‘False’ it doesn’t
     guarantee that a subsequent call to put() will not block.

 -- 成員函式: Queue.put (item, block=True, timeout=None)

     Put `item' into the queue.  If optional args `block' is true 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 Full: 23bb. 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 Full: 23bb. exception (`timeout' is
     ignored in that case).

 -- 成員函式: Queue.put_nowait (item)

     Equivalent to ‘put(item, False)’.

 -- 成員函式: Queue.get (block=True, timeout=None)

     Remove and return an item from the queue.  If optional args `block'
     is true 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 Empty: 23ba.
     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 Empty: 23ba. exception (`timeout' is ignored
     in that case).

     Prior to 3.0 on POSIX systems, and for all versions on Windows, if
     `block' is true and `timeout' is ‘None’, this operation goes into
     an uninterruptible wait on an underlying lock.  This means that no
     exceptions can occur, and in particular a SIGINT will not trigger a
     *note KeyboardInterrupt: 198.

 -- 成員函式: Queue.get_nowait ()

     Equivalent to ‘get(False)’.

Two methods are offered to support tracking whether enqueued tasks have
been fully processed by daemon consumer threads.

 -- 成員函式: Queue.task_done ()

     Indicate that a formerly enqueued task is complete.  Used by queue
     consumer threads.  For each *note get(): 24ad. used to fetch a
     task, a subsequent call to *note task_done(): 23b6. tells the queue
     that the processing on the task is complete.

     If a *note join(): 23b7. is currently blocking, it will resume when
     all items have been processed (meaning that a *note task_done():
     23b6. call was received for every item that had been *note put():
     24af. into the queue).

     Raises a *note ValueError: 1fc. if called more times than there
     were items placed in the queue.

 -- 成員函式: Queue.join ()

     Blocks 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 thread calls
     *note task_done(): 23b6. 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(): 23b7. unblocks.

Example of how to wait for enqueued tasks to be completed:

     import threading, 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)
     print('All task requests sent\n', end='')

     # block until all tasks are done
     q.join()
     print('All work completed')


File: python.info,  Node: SimpleQueue Objects,  Prev: Queue Objects,  Up: queue --- A synchronized queue class

5.17.8.2 SimpleQueue Objects
............................

*note SimpleQueue: 3cb. objects provide the public methods described
below.

 -- 成員函式: SimpleQueue.qsize ()

     Return the approximate size of the queue.  Note, qsize() > 0
     doesn’t guarantee that a subsequent get() will not block.

 -- 成員函式: SimpleQueue.empty ()

     Return ‘True’ if the queue is empty, ‘False’ otherwise.  If empty()
     returns ‘False’ it doesn’t guarantee that a subsequent call to
     get() will not block.

 -- 成員函式: SimpleQueue.put (item, block=True, timeout=None)

     Put `item' into the queue.  The method never blocks and always
     succeeds (except for potential low-level errors such as failure to
     allocate memory).  The optional args `block' and `timeout' are
     ignored and only provided for compatibility with *note Queue.put():
     24af.

     `CPython implementation detail:' This method has a C implementation
     which is reentrant.  That is, a ‘put()’ or ‘get()’ call can be
     interrupted by another ‘put()’ call in the same thread without
     deadlocking or corrupting internal state inside the queue.  This
     makes it appropriate for use in destructors such as ‘__del__’
     methods or *note weakref: 129. callbacks.

 -- 成員函式: SimpleQueue.put_nowait (item)

     Equivalent to ‘put(item)’, provided for compatibility with *note
     Queue.put_nowait(): 24b0.

 -- 成員函式: SimpleQueue.get (block=True, timeout=None)

     Remove and return an item from the queue.  If optional args `block'
     is true 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 Empty: 23ba.
     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 Empty: 23ba. exception (`timeout' is ignored
     in that case).

 -- 成員函式: SimpleQueue.get_nowait ()

     Equivalent to ‘get(False)’.

也參考
......

Class *note multiprocessing.Queue: 2395.

     A queue class for use in a multi-processing (rather than
     multi-threading) context.

*note collections.deque: 536. is an alternative implementation of
unbounded queues with fast atomic *note append(): 1935. and *note
popleft(): 193b. operations that do not require locking and also support
indexing.


File: python.info,  Node: contextvars --- Context Variables,  Next: _thread --- Low-level threading API,  Prev: queue --- A synchronized queue class,  Up: Concurrent Execution

5.17.9 ‘contextvars’ — Context Variables
----------------------------------------

__________________________________________________________________

This module provides APIs to manage, store, and access context-local
state.  The *note ContextVar: 24bf. class is used to declare and work
with `Context Variables'.  The *note copy_context(): 24c0. function and
the *note Context: 24c1. 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(): 22f8. to prevent their state from bleeding to
other code unexpectedly, when used in concurrent code.

See also PEP 567(1) for additional details.

3.7 版新加入.

* Menu:

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

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0567


File: python.info,  Node: Context Variables,  Next: Manual Context Management,  Up: contextvars --- Context Variables

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(): 24c3. 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: 24c1. 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: 1662.

      -- 成員函式: 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: 24c6. object that can be used to
          restore the variable to its previous value via the *note
          ContextVar.reset(): 24c7. method.

      -- 成員函式: reset (token)

          Reset the context variable to the value it had before the
          *note ContextVar.set(): 24c5. that created the `token' was
          used.

          For example:

               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(): 24c5.
     method.  They can be passed to the *note ContextVar.reset(): 24c7.
     method to revert the value of the variable to what it was before
     the corresponding `set'.

      -- 屬性: Token.var

          A read-only property.  Points to the *note ContextVar: 24bf.
          object that created the token.

      -- 屬性: Token.old_value

          A read-only property.  Set to the value the variable had
          before the *note ContextVar.set(): 24c5. method call that
          created the token.  It points to ‘Token.MISSING’ is the
          variable was not set before the call.

      -- 屬性: Token.MISSING

          A marker object used by ‘Token.old_value’.


File: python.info,  Node: Manual Context Management,  Next: asyncio support,  Prev: Context Variables,  Up: contextvars --- Context Variables

5.17.9.2 Manual Context Management
..................................

 -- 函式: contextvars.copy_context ()

     Returns a copy of the current *note Context: 24c1. 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: 24bf. 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(): 24c0.
     function.

     Context implements the *note collections.abc.Mapping: 1949.
     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: 2bb. 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: 24bf.
          variable.  If the variable is not set in the context object, a
          *note KeyError: 2c8. 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 --- Context Variables

5.17.9.3 asyncio support
........................

Context variables are natively supported in *note asyncio: a. 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

The following are support modules for some of the above services:


File: python.info,  Node: _thread --- Low-level threading API,  Next: _dummy_thread --- Drop-in replacement for the _thread module,  Prev: contextvars --- Context Variables,  Up: Concurrent Execution

5.17.10 ‘_thread’ — Low-level threading API
-------------------------------------------

__________________________________________________________________

This module provides low-level primitives for working with multiple
threads (also called `light-weight processes' or `tasks') — multiple
threads of control sharing their global data space.  For
synchronization, simple locks (also called `mutexes' or `binary
semaphores') are provided.  The *note threading: 10a. module provides an
easier to use and higher-level threading API built on top of this
module.

3.7 版更變: This module used to be optional, it is now always available.

This module defines the following constants and functions:

 -- 例外: _thread.error

     Raised on thread-specific errors.

     3.3 版更變: This is now a synonym of the built-in *note
     RuntimeError: 2bb.

 -- Data: _thread.LockType

     This is the type of lock objects.

 -- 函式: _thread.start_new_thread (function, args[, kwargs])

     Start a new thread and return its identifier.  The thread executes
     the function `function' with the argument list `args' (which must
     be a tuple).  The optional `kwargs' argument specifies a dictionary
     of keyword arguments.

     When the function returns, the thread silently exits.

     When the function terminates with an unhandled exception, *note
     sys.unraisablehook(): 22e. is called to handle the exception.  The
     `object' attribute of the hook argument is `function'.  By default,
     a stack trace is printed and then the thread exits (but other
     threads continue to run).

     When the function raises a *note SystemExit: 601. exception, it is
     silently ignored.

     3.8 版更變: *note sys.unraisablehook(): 22e. is now used to handle
     unhandled exceptions.

 -- 函式: _thread.interrupt_main ()

     Simulate the effect of a *note signal.SIGINT: 24d8. signal arriving
     in the main thread.  A thread can use this function to interrupt
     the main thread.

     If *note signal.SIGINT: 24d8. isn’t handled by Python (it was set
     to *note signal.SIG_DFL: 24d9. or *note signal.SIG_IGN: 24da.),
     this function does nothing.

 -- 函式: _thread.exit ()

     Raise the *note SystemExit: 601. exception.  When not caught, this
     will cause the thread to exit silently.

 -- 函式: _thread.allocate_lock ()

     Return a new lock object.  Methods of locks are described below.
     The lock is initially unlocked.

 -- 函式: _thread.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.

 -- 函式: _thread.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: 1364.: Windows, FreeBSD, Linux, macOS, OpenBSD,
     NetBSD, AIX.

     3.8 版新加入.

 -- 函式: _thread.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: 2bb. is
     raised.  If the specified stack size is invalid, a *note
     ValueError: 1fc. 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 Availability: 1364.: Windows, systems with POSIX threads.

 -- Data: _thread.TIMEOUT_MAX

     The maximum value allowed for the `timeout' parameter of
     ‘Lock.acquire()’.  Specifying a timeout greater than this value
     will raise an *note OverflowError: 965.

     3.2 版新加入.

Lock objects have the following methods:

 -- 成員函式: lock.acquire (waitflag=1, timeout=-1)

     Without any optional argument, this method acquires the lock
     unconditionally, if necessary waiting until it is released by
     another thread (only one thread at a time can acquire a lock —
     that’s their reason for existence).

     If the integer `waitflag' argument is present, the action depends
     on its value: if it is zero, the lock is only acquired if it can be
     acquired immediately without waiting, while if it is nonzero, the
     lock is acquired unconditionally as above.

     If the floating-point `timeout' argument is present and positive,
     it specifies the maximum wait time in seconds before returning.  A
     negative `timeout' argument specifies an unbounded wait.  You
     cannot specify a `timeout' if `waitflag' is zero.

     The return value is ‘True’ if the lock is acquired successfully,
     ‘False’ if not.

     3.2 版更變: The `timeout' parameter is new.

     3.2 版更變: Lock acquires can now be interrupted by signals on
     POSIX.

 -- 成員函式: lock.release ()

     Releases the lock.  The lock must have been acquired earlier, but
     not necessarily by the same thread.

 -- 成員函式: lock.locked ()

     Return the status of the lock: ‘True’ if it has been acquired by
     some thread, ‘False’ if not.

In addition to these methods, lock objects can also be used via the
*note with: 6ee. statement, e.g.:

     import _thread

     a_lock = _thread.allocate_lock()

     with a_lock:
         print("a_lock is locked while this executes")

`Caveats:'

   * Threads interact strangely with interrupts: the *note
     KeyboardInterrupt: 198. exception will be received by an arbitrary
     thread.  (When the *note signal: eb. module is available,
     interrupts always go to the main thread.)

   * Calling *note sys.exit(): ce7. or raising the *note SystemExit:
     601. exception is equivalent to calling *note _thread.exit(): 24db.

   * It is not possible to interrupt the ‘acquire()’ method on a lock —
     the *note KeyboardInterrupt: 198. exception will happen after the
     lock has been acquired.

   * When the main thread exits, it is system defined whether the other
     threads survive.  On most systems, they are killed without
     executing *note try: d77. ...  *note finally: 183. clauses or
     executing object destructors.

   * When the main thread exits, it does not do any of its usual cleanup
     (except that *note try: d77. ...  *note finally: 183. clauses are
     honored), and the standard I/O files are not flushed.


File: python.info,  Node: _dummy_thread --- Drop-in replacement for the _thread module,  Next: dummy_threading --- Drop-in replacement for the threading module,  Prev: _thread --- Low-level threading API,  Up: Concurrent Execution

5.17.11 ‘_dummy_thread’ — Drop-in replacement for the ‘_thread’ module
----------------------------------------------------------------------

`Source code:' Lib/_dummy_thread.py(1)

3.7 版後已棄用: Python now always has threading enabled.  Please use
*note _thread: 3. (or, better, *note threading: 10a.) instead.

__________________________________________________________________

This module provides a duplicate interface to the *note _thread: 3.
module.  It was meant to be imported when the *note _thread: 3. module
was not provided on a platform.

Be careful to not use this module where deadlock might occur from a
thread being created that blocks waiting for another thread to be
created.  This often occurs with blocking I/O.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/_dummy_thread.py


File: python.info,  Node: dummy_threading --- Drop-in replacement for the threading module,  Prev: _dummy_thread --- Drop-in replacement for the _thread module,  Up: Concurrent Execution

5.17.12 ‘dummy_threading’ — Drop-in replacement for the ‘threading’ module
--------------------------------------------------------------------------

`Source code:' Lib/dummy_threading.py(1)

3.7 版後已棄用: Python now always has threading enabled.  Please use
*note threading: 10a. instead.

__________________________________________________________________

This module provides a duplicate interface to the *note threading: 10a.
module.  It was meant to be imported when the *note _thread: 3. module
was not provided on a platform.

Be careful to not use this module where deadlock might occur from a
thread being created that blocks waiting for another thread to be
created.  This often occurs with blocking I/O.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/dummy_threading.py


File: python.info,  Node: Networking and Interprocess Communication,  Next: Internet Data Handling,  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: eb. and *note mmap: b4.  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 --- Asynchronous I/O. Asynchronous I/O
* socket: socket --- Low-level networking interface. Low-level networking interface
* ssl: ssl --- TLS/SSL wrapper for socket objects. TLS/SSL wrapper for socket objects
* select: select --- Waiting for I/O completion. Waiting for I/O completion
* selectors: selectors --- High-level I/O multiplexing. High-level I/O multiplexing
* asyncore: asyncore --- Asynchronous socket handler. Asynchronous socket handler
* asynchat: asynchat --- Asynchronous socket command/response handler. Asynchronous socket command/response handler
* signal: signal --- Set handlers for asynchronous events. Set handlers for asynchronous events
* mmap: mmap --- Memory-mapped file support. Memory-mapped file support


File: python.info,  Node: asyncio --- Asynchronous I/O,  Next: socket --- Low-level networking interface,  Up: Networking and Interprocess Communication

5.18.1 ‘asyncio’ — Asynchronous I/O
-----------------------------------

__________________________________________________________________

Hello World!
............

     import asyncio

     async def main():
         print('Hello ...')
         await asyncio.sleep(1)
         print('... World!')

     # Python 3.7+
     asyncio.run(main())

asyncio is a library to write `concurrent' code using the `async/await'
syntax.

asyncio is used as a foundation for multiple Python asynchronous
frameworks that provide high-performance network and web-servers,
database connection libraries, distributed task queues, etc.

asyncio is often a perfect fit for IO-bound and high-level `structured'
network code.

asyncio provides a set of `high-level' APIs to:

   * *note run Python coroutines: 24ed. concurrently and have full
     control over their execution;

   * perform *note network IO and IPC: 24ee.;

   * control *note subprocesses: 24ef.;

   * distribute tasks via *note queues: 24f0.;

   * *note synchronize: 24f1. concurrent code;

Additionally, there are `low-level' APIs for `library and framework
developers' to:

   * create and manage *note event loops: 649, which provide
     asynchronous APIs for *note networking: 362, running *note
     subprocesses: 24f2, handling *note OS signals: 24f3, etc;

   * implement efficient protocols using *note transports: 24f4.;

   * *note bridge: 24f5. callback-based libraries and code with
     async/await syntax.

Reference
.........

* Menu:

* Coroutines and Tasks::
* Streams::
* Synchronization Primitives::
* Subprocesses::
* Queues::
* Exceptions: Exceptions<8>.
* Event Loop::
* Futures::
* Transports and Protocols::
* Policies::
* Platform Support::
* High-level API Index::
* Low-level API Index::
* Developing with asyncio::


File: python.info,  Node: Coroutines and Tasks,  Next: Streams,  Up: asyncio --- Asynchronous I/O

5.18.1.1 Coroutines and Tasks
.............................

This section outlines high-level asyncio APIs to work with coroutines
and Tasks.

* Menu:

* Coroutines: Coroutines<3>.
* Awaitables::
* Running an asyncio Program::
* Creating Tasks::
* Sleeping::
* Running Tasks Concurrently::
* Shielding From Cancellation::
* Timeouts::
* Waiting Primitives::
* Scheduling From Other Threads::
* Introspection::
* Task Object::
* Generator-based Coroutines::


File: python.info,  Node: Coroutines<3>,  Next: Awaitables,  Up: Coroutines and Tasks

5.18.1.2 Coroutines
...................

*note Coroutines: 1a7. declared with the async/await syntax is the
preferred way of writing asyncio applications.  For example, the
following snippet of code (requires Python 3.7+) 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 three main mechanisms:

   * The *note asyncio.run(): 1a6. 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())

     Expected output:

          started at 17:13:52
          hello
          world
          finished at 17:13:55

   * The *note asyncio.create_task(): 1af. function to run coroutines
     concurrently as asyncio *note Tasks: 1ae.

     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


File: python.info,  Node: Awaitables,  Next: Running an asyncio Program,  Prev: Coroutines<3>,  Up: Coroutines and Tasks

5.18.1.3 Awaitables
...................

We say that an object is an `awaitable' object if it can be used in an
*note await: 1a4. expression.  Many asyncio APIs are designed to accept
awaitables.

There are three main types of `awaitable' objects: `coroutines',
`Tasks', and `Futures'.

Coroutines
..........

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: 285. function;

        * a `coroutine object': an object returned by calling a
          `coroutine function'.

asyncio also supports legacy *note generator-based: 24fb. coroutines.

Tasks
.....

`Tasks' are used to schedule coroutines `concurrently'.

When a coroutine is wrapped into a `Task' with functions like *note
asyncio.create_task(): 1af. 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: 448. 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(): 24fc.


File: python.info,  Node: Running an asyncio Program,  Next: Creating Tasks,  Prev: Awaitables,  Up: Coroutines and Tasks

5.18.1.4 Running an asyncio Program
...................................

 -- 函式: asyncio.run (coro, *, debug=False)

     Execute the *note coroutine: 1a7. `coro' and return the result.

     This function runs the passed coroutine, taking care of managing
     the asyncio event loop and `finalizing asynchronous generators'.

     This function cannot be called when another asyncio event loop is
     running in the same thread.

     If `debug' is ‘True’, the event loop will be run in debug mode.

     This function always creates a new event loop and closes it at the
     end.  It should be used as a main entry point for asyncio programs,
     and should ideally only be called once.

     Example:

          async def main():
              await asyncio.sleep(1)
              print('hello')

          asyncio.run(main())

     3.7 版新加入.

          備註: The source code for ‘asyncio.run()’ can be found in
          Lib/asyncio/runners.py(1).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/asyncio/runners.py


File: python.info,  Node: Creating Tasks,  Next: Sleeping,  Prev: Running an asyncio Program,  Up: Coroutines and Tasks

5.18.1.5 Creating Tasks
.......................

 -- 函式: asyncio.create_task (coro, *, name=None)

     Wrap the `coro' *note coroutine: 24ed. into a *note Task: 1ae. 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(): 1b1.

     The task is executed in the loop returned by *note
     get_running_loop(): 359, *note RuntimeError: 2bb. is raised if
     there is no running loop in current thread.

     This function has been `added in Python 3.7'.  Prior to Python 3.7,
     the low-level *note asyncio.ensure_future(): 51c. function can be
     used instead:

          async def coro():
              ...

          # In Python 3.7+
          task = asyncio.create_task(coro())
          ...

          # This works in all Python versions but is less readable
          task = asyncio.ensure_future(coro())
          ...

     3.7 版新加入.

     3.8 版更變: Added the ‘name’ parameter.


File: python.info,  Node: Sleeping,  Next: Running Tasks Concurrently,  Prev: Creating Tasks,  Up: Coroutines and Tasks

5.18.1.6 Sleeping
.................

 -- 函式: coroutine asyncio.sleep (delay, result=None, *, loop=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.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

     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())


File: python.info,  Node: Running Tasks Concurrently,  Next: Shielding From Cancellation,  Prev: Sleeping,  Up: Coroutines and Tasks

5.18.1.7 Running Tasks Concurrently
...................................

 -- 函式: awaitable asyncio.gather (*aws, loop=None,
          return_exceptions=False)

     Run *note awaitable objects: 24f9. 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: 1a8. – 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.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

     Example:

          import asyncio

          async def factorial(name, number):
              f = 1
              for i in range(2, number + 1):
                  print(f"Task {name}: Compute factorial({i})...")
                  await asyncio.sleep(1)
                  f *= i
              print(f"Task {name}: factorial({number}) = {f}")

          async def main():
              # Schedule three calls *concurrently*:
              await asyncio.gather(
                  factorial("A", 2),
                  factorial("B", 3),
                  factorial("C", 4),
              )

          asyncio.run(main())

          # Expected output:
          #
          #     Task A: Compute factorial(2)...
          #     Task B: Compute factorial(2)...
          #     Task C: Compute factorial(2)...
          #     Task A: factorial(2) = 2
          #     Task B: Compute factorial(3)...
          #     Task C: Compute factorial(3)...
          #     Task B: factorial(3) = 6
          #     Task C: Compute factorial(4)...
          #     Task C: factorial(4) = 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'.


File: python.info,  Node: Shielding From Cancellation,  Next: Timeouts,  Prev: Running Tasks Concurrently,  Up: Coroutines and Tasks

5.18.1.8 Shielding From Cancellation
....................................

 -- 函式: awaitable asyncio.shield (aw, *, loop=None)

     Protect an *note awaitable object: 24f9. from being *note
     cancelled: 2504.

     If `aw' is a coroutine it is automatically scheduled as a Task.

     The statement:

          res = await shield(something())

     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: 1a8.

     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:

          try:
              res = await shield(something())
          except CancelledError:
              res = None

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.


File: python.info,  Node: Timeouts,  Next: Waiting Primitives,  Prev: Shielding From Cancellation,  Up: Coroutines and Tasks

5.18.1.9 Timeouts
.................

 -- 函式: coroutine asyncio.wait_for (aw, timeout, *, loop=None)

     Wait for the `aw' *note awaitable: 24f9. 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
     asyncio.TimeoutError: 2506.

     To avoid the task *note cancellation: 2504, wrap it in *note
     shield(): 288.

     The function will wait until the future is actually cancelled, so
     the total wait time may exceed the `timeout'.

     If the wait is cancelled, the future `aw' is also cancelled.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

     Example:

          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 asyncio.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
     asyncio.TimeoutError: 2506. immediately.


File: python.info,  Node: Waiting Primitives,  Next: Scheduling From Other Threads,  Prev: Timeouts,  Up: Coroutines and Tasks

5.18.1.10 Waiting Primitives
............................

 -- 函式: coroutine asyncio.wait (aws, *, loop=None, timeout=None,
          return_when=ALL_COMPLETED)

     Run *note awaitable objects: 24f9. in the `aws' iterable
     concurrently and block until the condition specified by
     `return_when'.

     Returns two sets of Tasks/Futures: ‘(done, pending)’.

     Usage:

          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 asyncio.TimeoutError:
     2506.  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:

     Constant                          描述
                                       
     -------------------------------------------------------------------------------
                                       
     ‘FIRST_COMPLETED’                 The function will return when any future
                                       finishes or is cancelled.
                                       
                                       
     ‘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 ‘ALL_COMPLETED’.
                                       
                                       
     ‘ALL_COMPLETED’                   The function will return when all futures
                                       finish or are cancelled.
                                       

     Unlike *note wait_for(): 289, ‘wait()’ does not cancel the futures
     when a timeout occurs.

     3.8 版後已棄用: If any awaitable in `aws' is a coroutine, it is
     automatically scheduled as a Task.  Passing coroutines objects to
     ‘wait()’ directly is deprecated as it leads to *note confusing
     behavior: 2509.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

          備註: ‘wait()’ schedules coroutines as Tasks automatically and
          later returns those implicitly created Task objects in ‘(done,
          pending)’ sets.  Therefore the following code won’t work as
          expected:

               async def foo():
                   return 42

               coro = foo()
               done, pending = await asyncio.wait({coro})

               if coro in done:
                   # This branch will never be run!

          Here is how the above snippet can be fixed:

               async def foo():
                   return 42

               task = asyncio.create_task(foo())
               done, pending = await asyncio.wait({task})

               if task in done:
                   # Everything will work as expected now.

     3.8 版後已棄用: Passing coroutine objects to ‘wait()’ directly is
     deprecated.

 -- 函式: asyncio.as_completed (aws, *, loop=None, timeout=None)

     Run *note awaitable objects: 24f9. in the `aws' iterable
     concurrently.  Return an iterator of coroutines.  Each coroutine
     returned can be awaited to get the earliest next result from the
     iterable of the remaining awaitables.

     Raises *note asyncio.TimeoutError: 2506. if the timeout occurs
     before all Futures are done.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

     Example:

          for coro in as_completed(aws):
              earliest_result = await coro
              # ...


File: python.info,  Node: Scheduling From Other Threads,  Next: Introspection,  Prev: Waiting Primitives,  Up: Coroutines and Tasks

5.18.1.11 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: b32. 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 asyncio.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: 250b. 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: Coroutines and Tasks

5.18.1.12 Introspection
.......................

 -- 函式: asyncio.current_task (loop=None)

     Return the currently running *note Task: 1ae. instance, or ‘None’
     if no task is running.

     If `loop' is ‘None’ *note get_running_loop(): 359. is used to get
     the current loop.

     3.7 版新加入.

 -- 函式: asyncio.all_tasks (loop=None)

     Return a set of not yet finished *note Task: 1ae. objects run by
     the loop.

     If `loop' is ‘None’, *note get_running_loop(): 359. is used for
     getting current loop.

     3.7 版新加入.


File: python.info,  Node: Task Object,  Next: Generator-based Coroutines,  Prev: Introspection,  Up: Coroutines and Tasks

5.18.1.13 Task Object
.....................

 -- 類別: asyncio.Task (coro, *, loop=None, name=None)

     A *note Future-like: 448. object that runs a Python *note
     coroutine: 24ed.  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(): 1af. function to
     create Tasks, or the low-level *note loop.create_task(): 1b0. or
     *note ensure_future(): 51c. functions.  Manual instantiation of
     Tasks is discouraged.

     To cancel a running Task use the *note cancel(): 2504. method.
     Calling it will cause the Task to throw a *note CancelledError:
     1a8. exception into the wrapped coroutine.  If a coroutine is
     awaiting on a Future object during cancellation, the Future object
     will be cancelled.

     *note cancelled(): 250e. can be used to check if the Task was
     cancelled.  The method returns ‘True’ if the wrapped coroutine did
     not suppress the *note CancelledError: 1a8. exception and was
     actually cancelled.

     *note asyncio.Task: 1ae. inherits from *note Future: 448. all of
     its APIs except *note Future.set_result(): 250f. and *note
     Future.set_exception(): 2510.

     Tasks support the *note contextvars: 25. module.  When a Task is
     created it copies the current context and later runs its coroutine
     in the copied context.

     3.7 版更變: Added support for the *note contextvars: 25. module.

     3.8 版更變: Added the ‘name’ parameter.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

      -- 成員函式: cancel ()

          Request the Task to be cancelled.

          This arranges for a *note CancelledError: 1a8. 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: d77.
          ...  ...  ‘except CancelledError’ ...  *note finally: 183.
          block.  Therefore, unlike *note Future.cancel(): 2511, *note
          Task.cancel(): 2504. does not guarantee that the Task will be
          cancelled, although suppressing cancellation completely is not
          common and is actively discouraged.  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(): 2504. and the wrapped coroutine
          propagated the *note CancelledError: 1a8. exception thrown
          into it.

      -- 成員函式: 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: 1a8. exception.

          If the Task’s result isn’t yet available, this method raises a
          *note InvalidStateError: 2515. 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: 1a8. exception.

          If the Task isn’t `done' yet, this method raises an *note
          InvalidStateError: 2515. 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():
          352. 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():
          2519. 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(): 251a.

          The `limit' argument is passed to *note get_stack(): 251a.
          directly.

          The `file' argument is an I/O stream to which the output is
          written; by default output is written to *note sys.stderr:
          314.

      -- 成員函式: get_coro ()

          Return the coroutine object wrapped by the *note Task: 1ae.

          3.8 版新加入.

      -- 成員函式: 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(): 7d1. output of a task object.

          3.8 版新加入.

      -- 成員函式: classmethod all_tasks (loop=None)

          Return a set of all tasks for an event loop.

          By default all tasks for the current event loop are returned.
          If `loop' is ‘None’, the *note get_event_loop(): 35a. function
          is used to get the current loop.

          Deprecated since version 3.7, will be removed in version 3.9:
          Do not call this as a task method.  Use the *note
          asyncio.all_tasks(): 356. function instead.

      -- 成員函式: classmethod current_task (loop=None)

          Return the currently running task or ‘None’.

          If `loop' is ‘None’, the *note get_event_loop(): 35a. function
          is used to get the current loop.

          Deprecated since version 3.7, will be removed in version 3.9:
          Do not call this as a task method.  Use the *note
          asyncio.current_task(): 355. function instead.


File: python.info,  Node: Generator-based Coroutines,  Prev: Task Object,  Up: Coroutines and Tasks

5.18.1.14 Generator-based Coroutines
....................................

     備註: Support for generator-based coroutines is `deprecated' and is
     scheduled for removal in Python 3.10.

Generator-based coroutines predate async/await syntax.  They are Python
generators that use ‘yield from’ expressions to await on Futures and
other coroutines.

Generator-based coroutines should be decorated with *note
@asyncio.coroutine: 283, although this is not enforced.

 -- 函式: @asyncio.coroutine

     Decorator to mark generator-based coroutines.

     This decorator enables legacy generator-based coroutines to be
     compatible with async/await code:

          @asyncio.coroutine
          def old_style_coroutine():
              yield from asyncio.sleep(1)

          async def main():
              await old_style_coroutine()

     This decorator should not be used for *note async def: 285.
     coroutines.

     Deprecated since version 3.8, will be removed in version 3.10: Use
     *note async def: 285. instead.

 -- 函式: asyncio.iscoroutine (obj)

     Return ‘True’ if `obj' is a *note coroutine object: 24ed.

     This method is different from *note inspect.iscoroutine(): 6fc.
     because it returns ‘True’ for generator-based coroutines.

 -- 函式: asyncio.iscoroutinefunction (func)

     Return ‘True’ if `func' is a *note coroutine function: 24ed.

     This method is different from *note inspect.iscoroutinefunction():
     6fd. because it returns ‘True’ for generator-based coroutine
     functions decorated with *note @coroutine: 283.


File: python.info,  Node: Streams,  Next: Synchronization Primitives,  Prev: Coroutines and Tasks,  Up: asyncio --- Asynchronous I/O

5.18.1.15 Streams
.................

`Source code:' Lib/asyncio/streams.py(1)

__________________________________________________________________

Streams are high-level async/await-ready primitives to work with network
connections.  Streams allow sending and receiving data without using
callbacks or low-level protocols and transports.  Here is an example of
a TCP echo client written using asyncio streams:

     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!'))

See also the *note Examples: 2522. section below.

Stream Functions
................

The following top-level asyncio functions can be used to create and work
with streams:

 -- 函式: coroutine asyncio.open_connection (host=None, port=None, *,
          loop=None, limit=None, ssl=None, family=0, proto=0, flags=0,
          sock=None, local_addr=None, server_hostname=None,
          ssl_handshake_timeout=None)

     Establish a network connection and return a pair of ‘(reader,
     writer)’ objects.

     The returned `reader' and `writer' objects are instances of *note
     StreamReader: fcf. and *note StreamWriter: fd0. classes.

     The `loop' argument is optional and can always be determined
     automatically when this function is awaited from a coroutine.

     `limit' determines the buffer size limit used by the returned *note
     StreamReader: fcf. instance.  By default the `limit' is set to 64
     KiB.

     The rest of the arguments are passed directly to *note
     loop.create_connection(): 1b3.

     3.7 版新加入: The `ssl_handshake_timeout' parameter.

 -- 函式: coroutine asyncio.start_server (client_connected_cb,
          host=None, port=None, *, loop=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, start_serving=True)

     Start a socket server.

     The `client_connected_cb' callback is called whenever a new client
     connection is established.  It receives a ‘(reader, writer)’ pair
     as two arguments, instances of the *note StreamReader: fcf. and
     *note StreamWriter: fd0. classes.

     `client_connected_cb' can be a plain callable or a *note coroutine
     function: 24ed.; if it is a coroutine function, it will be
     automatically scheduled as a *note Task: 1ae.

     The `loop' argument is optional and can always be determined
     automatically when this method is awaited from a coroutine.

     `limit' determines the buffer size limit used by the returned *note
     StreamReader: fcf. instance.  By default the `limit' is set to 64
     KiB.

     The rest of the arguments are passed directly to *note
     loop.create_server(): 362.

     3.7 版新加入: The `ssl_handshake_timeout' and `start_serving'
     parameters.

Unix Sockets
............

 -- 函式: coroutine asyncio.open_unix_connection (path=None, *,
          loop=None, limit=None, ssl=None, sock=None,
          server_hostname=None, ssl_handshake_timeout=None)

     Establish a Unix socket connection and return a pair of ‘(reader,
     writer)’.

     Similar to *note open_connection(): 368. but operates on Unix
     sockets.

     See also the documentation of *note loop.create_unix_connection():
     2524.

     *note Availability: 1364.: Unix.

     3.7 版新加入: The `ssl_handshake_timeout' parameter.

     3.7 版更變: The `path' parameter can now be a *note path-like
     object: 36f.

 -- 函式: coroutine asyncio.start_unix_server (client_connected_cb,
          path=None, *, loop=None, limit=None, sock=None, backlog=100,
          ssl=None, ssl_handshake_timeout=None, start_serving=True)

     Start a Unix socket server.

     Similar to *note start_server(): 369. but works with Unix sockets.

     See also the documentation of *note loop.create_unix_server(): 363.

     *note Availability: 1364.: Unix.

     3.7 版新加入: The `ssl_handshake_timeout' and `start_serving'
     parameters.

     3.7 版更變: The `path' parameter can now be a *note path-like
     object: 36f.

* Menu:

* StreamReader::
* StreamWriter::
* Examples: Examples<11>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/asyncio/streams.py


File: python.info,  Node: StreamReader,  Next: StreamWriter,  Up: Streams

5.18.1.16 StreamReader
......................

 -- 類別: asyncio.StreamReader

     Represents a reader object that provides APIs to read data from the
     IO stream.

     It is not recommended to instantiate `StreamReader' objects
     directly; use *note open_connection(): 368. and *note
     start_server(): 369. instead.

      -- 成員函式: coroutine read (n=-1)

          Read up to `n' bytes.  If `n' is not provided, or set to ‘-1’,
          read until EOF and return all read bytes.

          If EOF was received and the internal buffer is empty, return
          an empty ‘bytes’ object.

      -- 成員函式: coroutine readline ()

          Read one line, where "line" is a sequence of bytes ending with
          ‘\n’.

          If EOF is received and ‘\n’ was not found, the method returns
          partially read data.

          If EOF is received and the internal buffer is empty, return an
          empty ‘bytes’ object.

      -- 成員函式: coroutine readexactly (n)

          Read exactly `n' bytes.

          Raise an *note IncompleteReadError: ede. if EOF is reached
          before `n' can be read.  Use the *note
          IncompleteReadError.partial: 2529. attribute to get the
          partially read data.

      -- 成員函式: coroutine readuntil (separator=b'\n')

          Read data from the stream until `separator' is found.

          On success, the data and separator will be removed from the
          internal buffer (consumed).  Returned data will include the
          separator at the end.

          If the amount of data read exceeds the configured stream
          limit, a *note LimitOverrunError: 252a. exception is raised,
          and the data is left in the internal buffer and can be read
          again.

          If EOF is reached before the complete separator is found, an
          *note IncompleteReadError: ede. exception is raised, and the
          internal buffer is reset.  The *note
          IncompleteReadError.partial: 2529. attribute may contain a
          portion of the separator.

          3.5.2 版新加入.

      -- 成員函式: at_eof ()

          Return ‘True’ if the buffer is empty and ‘feed_eof()’ was
          called.


File: python.info,  Node: StreamWriter,  Next: Examples<11>,  Prev: StreamReader,  Up: Streams

5.18.1.17 StreamWriter
......................

 -- 類別: asyncio.StreamWriter

     Represents a writer object that provides APIs to write data to the
     IO stream.

     It is not recommended to instantiate `StreamWriter' objects
     directly; use *note open_connection(): 368. and *note
     start_server(): 369. instead.

      -- 成員函式: write (data)

          The method attempts to write the `data' to the underlying
          socket immediately.  If that fails, the data is queued in an
          internal write buffer until it can be sent.

          The method should be used along with the ‘drain()’ method:

               stream.write(data)
               await stream.drain()

      -- 成員函式: writelines (data)

          The method writes a list (or any iterable) of bytes to the
          underlying socket immediately.  If that fails, the data is
          queued in an internal write buffer until it can be sent.

          The method should be used along with the ‘drain()’ method:

               stream.writelines(lines)
               await stream.drain()

      -- 成員函式: close ()

          The method closes the stream and the underlying socket.

          The method should be used along with the ‘wait_closed()’
          method:

               stream.close()
               await stream.wait_closed()

      -- 成員函式: can_write_eof ()

          Return ‘True’ if the underlying transport supports the *note
          write_eof(): 2531. method, ‘False’ otherwise.

      -- 成員函式: write_eof ()

          Close the write end of the stream after the buffered write
          data is flushed.

      -- 屬性: transport

          Return the underlying asyncio transport.

      -- 成員函式: get_extra_info (name, default=None)

          Access optional transport information; see *note
          BaseTransport.get_extra_info(): 2c9. for details.

      -- 成員函式: coroutine drain ()

          Wait until it is appropriate to resume writing to the stream.
          Example:

               writer.write(data)
               await writer.drain()

          This is a flow control method that interacts with the
          underlying IO write buffer.  When the size of the buffer
          reaches the high watermark, `drain()' blocks until the size of
          the buffer is drained down to the low watermark and writing
          can be resumed.  When there is nothing to wait for, the *note
          drain(): 2534. returns immediately.

      -- 成員函式: is_closing ()

          Return ‘True’ if the stream is closed or in the process of
          being closed.

          3.7 版新加入.

      -- 成員函式: coroutine wait_closed ()

          Wait until the stream is closed.

          Should be called after *note close(): 252f. to wait until the
          underlying connection is closed.

          3.7 版新加入.


File: python.info,  Node: Examples<11>,  Prev: StreamWriter,  Up: Streams

5.18.1.18 Examples
..................

* Menu:

* TCP echo client using streams::
* TCP echo server using streams::
* Get HTTP headers::
* Register an open socket to wait for data using streams::


File: python.info,  Node: TCP echo client using streams,  Next: TCP echo server using streams,  Up: Examples<11>

5.18.1.19 TCP echo client using streams
.......................................

TCP echo client using the *note asyncio.open_connection(): 368.
function:

     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())

         data = await reader.read(100)
         print(f'Received: {data.decode()!r}')

         print('Close the connection')
         writer.close()

     asyncio.run(tcp_echo_client('Hello World!'))

也參考
......

The *note TCP echo client protocol: 2537. example uses the low-level
*note loop.create_connection(): 1b3. method.


File: python.info,  Node: TCP echo server using streams,  Next: Get HTTP headers,  Prev: TCP echo client using streams,  Up: Examples<11>

5.18.1.20 TCP echo server using streams
.......................................

TCP echo server using the *note asyncio.start_server(): 369. function:

     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()

     async def main():
         server = await asyncio.start_server(
             handle_echo, '127.0.0.1', 8888)

         addr = server.sockets[0].getsockname()
         print(f'Serving on {addr}')

         async with server:
             await server.serve_forever()

     asyncio.run(main())

也參考
......

The *note TCP echo server protocol: 253a. example uses the *note
loop.create_server(): 362. method.


File: python.info,  Node: Get HTTP headers,  Next: Register an open socket to wait for data using streams,  Prev: TCP echo server using streams,  Up: Examples<11>

5.18.1.21 Get HTTP headers
..........................

Simple example querying HTTP headers of the URL passed on the command
line:

     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()

     url = sys.argv[1]
     asyncio.run(print_http_headers(url))

Usage:

     python example.py http://example.com/path/page.html

or with HTTPS:

     python example.py https://example.com/path/page.html


File: python.info,  Node: Register an open socket to wait for data using streams,  Prev: Get HTTP headers,  Up: Examples<11>

5.18.1.22 Register an open socket to wait for data using streams
................................................................

Coroutine waiting until a socket receives data using the *note
open_connection(): 368. function:

     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()

         # Close the second socket
         wsock.close()

     asyncio.run(wait_for_data())

也參考
......

The *note register an open socket to wait for data using a protocol:
253e. example uses a low-level protocol and the *note
loop.create_connection(): 1b3. method.

The *note watch a file descriptor for read events: 253f. example uses
the low-level *note loop.add_reader(): 2540. method to watch a file
descriptor.


File: python.info,  Node: Synchronization Primitives,  Next: Subprocesses,  Prev: Streams,  Up: asyncio --- Asynchronous I/O

5.18.1.23 Synchronization Primitives
....................................

`Source code:' Lib/asyncio/locks.py(1)

__________________________________________________________________

asyncio synchronization primitives are designed to be similar to those
of the *note threading: 10a. module with two important caveats:

   * asyncio primitives are not thread-safe, therefore they should not
     be used for OS thread synchronization (use *note threading: 10a.
     for that);

   * methods of these synchronization primitives do not accept the
     `timeout' argument; use the *note asyncio.wait_for(): 289. function
     to perform operations with timeouts.

asyncio has the following basic synchronization primitives:

   * *note Lock: 28c.

   * *note Event: 28d.

   * *note Condition: 28e.

   * *note Semaphore: 28f.

   * *note BoundedSemaphore: 290.

__________________________________________________________________

* Menu:

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/asyncio/locks.py


File: python.info,  Node: Lock,  Next: Event,  Up: Synchronization Primitives

5.18.1.24 Lock
..............

 -- 類別: asyncio.Lock (*, loop=None)

     Implements a mutex lock for asyncio tasks.  Not thread-safe.

     An asyncio lock can be used to guarantee exclusive access to a
     shared resource.

     The preferred way to use a Lock is an *note async with: 648.
     statement:

          lock = asyncio.Lock()

          # ... later
          async with lock:
              # access shared state

     which is equivalent to:

          lock = asyncio.Lock()

          # ... later
          await lock.acquire()
          try:
              # access shared state
          finally:
              lock.release()

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

      -- 成員函式: coroutine acquire ()

          Acquire the lock.

          This method waits until the lock is `unlocked', sets it to
          `locked' and returns ‘True’.

          When more than one coroutine is blocked in *note acquire():
          2544. waiting for the lock to be unlocked, only one coroutine
          eventually proceeds.

          Acquiring a lock is `fair': the coroutine that proceeds will
          be the first coroutine that started waiting on the lock.

      -- 成員函式: release ()

          Release the lock.

          When the lock is `locked', reset it to `unlocked' and return.

          If the lock is `unlocked', a *note RuntimeError: 2bb. is
          raised.

      -- 成員函式: locked ()

          Return ‘True’ if the lock is `locked'.


File: python.info,  Node: Event,  Next: Condition,  Prev: Lock,  Up: Synchronization Primitives

5.18.1.25 Event
...............

 -- 類別: asyncio.Event (*, loop=None)

     An event object.  Not thread-safe.

     An asyncio event can be used to notify multiple asyncio tasks that
     some event has happened.

     An Event object manages an internal flag that can be set to `true'
     with the *note set(): 2548. method and reset to `false' with the
     *note clear(): 2549. method.  The *note wait(): 254a. method blocks
     until the flag is set to `true'.  The flag is set to `false'
     initially.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

     Example:

          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 ()

          Wait until the event is set.

          If the event is set, return ‘True’ immediately.  Otherwise
          block until another task calls *note set(): 2548.

      -- 成員函式: set ()

          Set the event.

          All tasks waiting for event to be set will be immediately
          awakened.

      -- 成員函式: clear ()

          Clear (unset) the event.

          Tasks awaiting on *note wait(): 254a. will now block until the
          *note set(): 2548. method is called again.

      -- 成員函式: is_set ()

          Return ‘True’ if the event is set.


File: python.info,  Node: Condition,  Next: Semaphore,  Prev: Event,  Up: Synchronization Primitives

5.18.1.26 Condition
...................

 -- 類別: asyncio.Condition (lock=None, *, loop=None)

     A Condition object.  Not thread-safe.

     An asyncio condition primitive can be used by a task to wait for
     some event to happen and then get exclusive access to a shared
     resource.

     In essence, a Condition object combines the functionality of an
     *note Event: 28d. and a *note Lock: 28c.  It is possible to have
     multiple Condition objects share one Lock, which allows
     coordinating exclusive access to a shared resource between
     different tasks interested in particular states of that shared
     resource.

     The optional `lock' argument must be a *note Lock: 28c. object or
     ‘None’.  In the latter case a new Lock object is created
     automatically.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

     The preferred way to use a Condition is an *note async with: 648.
     statement:

          cond = asyncio.Condition()

          # ... later
          async with cond:
              await cond.wait()

     which is equivalent to:

          cond = asyncio.Condition()

          # ... later
          await cond.acquire()
          try:
              await cond.wait()
          finally:
              cond.release()

      -- 成員函式: coroutine acquire ()

          Acquire the underlying lock.

          This method waits until the underlying lock is `unlocked',
          sets it to `locked' and returns ‘True’.

      -- 成員函式: notify (n=1)

          Wake up at most `n' tasks (1 by default) waiting on this
          condition.  The method is no-op if no tasks are waiting.

          The lock must be acquired before this method is called and
          released shortly after.  If called with an `unlocked' lock a
          *note RuntimeError: 2bb. error is raised.

      -- 成員函式: locked ()

          Return ‘True’ if the underlying lock is acquired.

      -- 成員函式: notify_all ()

          Wake up all tasks waiting on this condition.

          This method acts like *note notify(): 254f, but wakes up all
          waiting tasks.

          The lock must be acquired before this method is called and
          released shortly after.  If called with an `unlocked' lock a
          *note RuntimeError: 2bb. error is raised.

      -- 成員函式: release ()

          Release the underlying lock.

          When invoked on an unlocked lock, a *note RuntimeError: 2bb.
          is raised.

      -- 成員函式: coroutine wait ()

          Wait until notified.

          If the calling task has not acquired the lock when this method
          is called, a *note RuntimeError: 2bb. is raised.

          This method releases the underlying lock, and then blocks
          until it is awakened by a *note notify(): 254f. or *note
          notify_all(): 2551. call.  Once awakened, the Condition
          re-acquires its lock and this method returns ‘True’.

      -- 成員函式: coroutine wait_for (predicate)

          Wait until a predicate becomes `true'.

          The predicate must be a callable which result will be
          interpreted as a boolean value.  The final value is the return
          value.


File: python.info,  Node: Semaphore,  Next: BoundedSemaphore,  Prev: Condition,  Up: Synchronization Primitives

5.18.1.27 Semaphore
...................

 -- 類別: asyncio.Semaphore (value=1, *, loop=None)

     A Semaphore object.  Not thread-safe.

     A semaphore manages an internal counter which is decremented by
     each *note acquire(): 2556. call and incremented by each *note
     release(): 2557. call.  The counter can never go below zero; when
     *note acquire(): 2556. finds that it is zero, it blocks, waiting
     until some task calls *note release(): 2557.

     The optional `value' argument gives the initial value for the
     internal counter (‘1’ by default).  If the given value is less than
     ‘0’ a *note ValueError: 1fc. is raised.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

     The preferred way to use a Semaphore is an *note async with: 648.
     statement:

          sem = asyncio.Semaphore(10)

          # ... later
          async with sem:
              # work with shared resource

     which is equivalent to:

          sem = asyncio.Semaphore(10)

          # ... later
          await sem.acquire()
          try:
              # work with shared resource
          finally:
              sem.release()

      -- 成員函式: coroutine acquire ()

          Acquire a semaphore.

          If the internal counter is greater than zero, decrement it by
          one and return ‘True’ immediately.  If it is zero, wait until
          a *note release(): 2557. is called and return ‘True’.

      -- 成員函式: locked ()

          Returns ‘True’ if semaphore can not be acquired immediately.

      -- 成員函式: release ()

          Release a semaphore, incrementing the internal counter by one.
          Can wake up a task waiting to acquire the semaphore.

          Unlike *note BoundedSemaphore: 290, *note Semaphore: 28f.
          allows making more ‘release()’ calls than ‘acquire()’ calls.


File: python.info,  Node: BoundedSemaphore,  Prev: Semaphore,  Up: Synchronization Primitives

5.18.1.28 BoundedSemaphore
..........................

 -- 類別: asyncio.BoundedSemaphore (value=1, *, loop=None)

     A bounded semaphore object.  Not thread-safe.

     Bounded Semaphore is a version of *note Semaphore: 28f. that raises
     a *note ValueError: 1fc. in *note release(): 2557. if it increases
     the internal counter above the initial `value'.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

__________________________________________________________________

3.7 版後已棄用: Acquiring a lock using ‘await lock’ or ‘yield from lock’
and/or *note with: 6ee. statement (‘with await lock’, ‘with (yield from
lock)’) is deprecated.  Use ‘async with lock’ instead.


File: python.info,  Node: Subprocesses,  Next: Queues,  Prev: Synchronization Primitives,  Up: asyncio --- Asynchronous I/O

5.18.1.29 Subprocesses
......................

`Source code:' 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())

See also the *note Examples: 255d. subsection.

* Menu:

* Creating Subprocesses::
* Constants: Constants<7>.
* Interacting with Subprocesses::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/asyncio/subprocess.py

   (2) 
https://github.com/python/cpython/tree/3.8/Lib/asyncio/base_subprocess.py


File: python.info,  Node: Creating Subprocesses,  Next: Constants<7>,  Up: Subprocesses

5.18.1.30 Creating Subprocesses
...............................

 -- 函式: coroutine asyncio.create_subprocess_exec (program, *args,
          stdin=None, stdout=None, stderr=None, loop=None, limit=None,
          **kwds)

     Create a subprocess.

     The `limit' argument sets the buffer limit for *note StreamReader:
     fcf. wrappers for ‘Process.stdout’ and ‘Process.stderr’ (if *note
     subprocess.PIPE: 3f3. is passed to `stdout' and `stderr'
     arguments).

     Return a *note Process: 255f. instance.

     See the documentation of *note loop.subprocess_exec(): 24f2. for
     other parameters.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

 -- 函式: coroutine asyncio.create_subprocess_shell (cmd, stdin=None,
          stdout=None, stderr=None, loop=None, limit=None, **kwds)

     Run the `cmd' shell command.

     The `limit' argument sets the buffer limit for *note StreamReader:
     fcf. wrappers for ‘Process.stdout’ and ‘Process.stderr’ (if *note
     subprocess.PIPE: 3f3. is passed to `stdout' and `stderr'
     arguments).

     Return a *note Process: 255f. instance.

     See the documentation of *note loop.subprocess_shell(): 2560. 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(): a78. function can be used to properly escape
          whitespace and special shell characters in strings that are
          going to be used to construct shell commands.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

     備註: Subprocesses are available for Windows if a *note
     ProactorEventLoop: 1ac. is used.  See *note Subprocess Support on
     Windows: 2561. for details.

也參考
......

asyncio also has the following `low-level' APIs to work with
subprocesses: *note loop.subprocess_exec(): 24f2, *note
loop.subprocess_shell(): 2560, *note loop.connect_read_pipe(): 2562,
*note loop.connect_write_pipe(): 2563, as well as the *note Subprocess
Transports: 2564. and *note Subprocess Protocols: 2565.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Shell_injection#Shell_injection


File: python.info,  Node: Constants<7>,  Next: Interacting with Subprocesses,  Prev: Creating Subprocesses,  Up: Subprocesses

5.18.1.31 Constants
...................

 -- Data: asyncio.subprocess.PIPE

     Can be passed to the `stdin', `stdout' or `stderr' parameters.

     If `PIPE' is passed to `stdin' argument, the *note Process.stdin:
     2568. attribute will point to a *note StreamWriter: fd0. instance.

     If `PIPE' is passed to `stdout' or `stderr' arguments, the *note
     Process.stdout: 2569. and *note Process.stderr: 256a. attributes
     will point to *note StreamReader: fcf. instances.

 -- Data: asyncio.subprocess.STDOUT

     Special value that can be used as the `stderr' argument and
     indicates that standard error should be redirected into standard
     output.

 -- Data: 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: 101f. will be used for the
     corresponding subprocess stream.


File: python.info,  Node: Interacting with Subprocesses,  Prev: Constants<7>,  Up: Subprocesses

5.18.1.32 Interacting with Subprocesses
.......................................

Both *note create_subprocess_exec(): 292. and *note
create_subprocess_shell(): 293. 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 *note
     create_subprocess_exec(): 292. and *note create_subprocess_shell():
     293. functions.

     This class is designed to have a similar API to the *note
     subprocess.Popen: 2ba. class, but there are some notable
     differences:

        * unlike Popen, Process instances do not have an equivalent to
          the *note poll(): 2483. method;

        * the *note communicate(): 256e. and *note wait(): 256f. methods
          don’t have a `timeout' parameter: use the *note wait_for():
          289. function;

        * the *note Process.wait(): 256f. method is asynchronous,
          whereas *note subprocess.Popen.wait(): 597. method is
          implemented as a blocking busy loop;

        * the `universal_newlines' parameter is not supported.

     This class is *note not thread safe: 250b.

     See also the *note Subprocess and Threads: 2570. section.

      -- 成員函式: coroutine wait ()

          Wait for the child process to terminate.

          Set and return the *note returncode: 2571. 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(): 256e.
               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. read data from `stdout' and `stderr', until EOF is
               reached;

            3. wait for process to terminate.

          The optional `input' argument is the data (*note bytes: 336.
          object) that will be sent to the child process.

          Return a tuple ‘(stdout_data, stderr_data)’.

          If either *note BrokenPipeError: 9a2. or *note
          ConnectionResetError: 9a5. 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.

      -- 成員函式: send_signal (signal)

          Sends the signal `signal' to the child process.

               備註: On Windows, ‘SIGTERM’ is an alias for *note
               terminate(): 2573.  ‘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 signal.SIGTERM: 2574.
          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():
          2573.

      -- 屬性: stdin

          Standard input stream (*note StreamWriter: fd0.) or ‘None’ if
          the process was created with ‘stdin=None’.

      -- 屬性: stdout

          Standard output stream (*note StreamReader: fcf.) or ‘None’ if
          the process was created with ‘stdout=None’.

      -- 屬性: stderr

          Standard error stream (*note StreamReader: fcf.) or ‘None’ if
          the process was created with ‘stderr=None’.

          警告: Use the *note communicate(): 256e. method rather than
          *note process.stdin.write(): 2568, *note await
          process.stdout.read(): 2569. or *note await
          process.stderr.read: 256a.  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 *note
          create_subprocess_shell(): 293. 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:

* Subprocess and Threads::
* Examples: Examples<12>.


File: python.info,  Node: Subprocess and Threads,  Next: Examples<12>,  Up: Interacting with Subprocesses

5.18.1.33 Subprocess and Threads
................................

Standard asyncio event loop supports running subprocesses from different
threads by default.

On Windows subprocesses are provided by *note ProactorEventLoop: 1ac.
only (default), *note SelectorEventLoop: 2578. has no subprocess
support.

On UNIX `child watchers' are used for subprocess finish waiting, see
*note Process Watchers: 2579. for more info.

3.8 版更變: UNIX switched to use *note ThreadedChildWatcher: 257a. for
spawning subprocesses from different threads without any limitation.

Spawning a subprocess with `inactive' current child watcher raises *note
RuntimeError: 2bb.

Note that alternative event loop implementations might have own
limitations; please refer to their documentation.

也參考
......

The *note Concurrency and multithreading in asyncio: 250b. section.


File: python.info,  Node: Examples<12>,  Prev: Subprocess and Threads,  Up: Interacting with Subprocesses

5.18.1.34 Examples
..................

An example using the *note Process: 255f. class to control a subprocess
and the *note StreamReader: fcf. class to read from its standard output.
The subprocess is created by the *note create_subprocess_exec(): 292.
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: 257c. written using low-level APIs.


File: python.info,  Node: Queues,  Next: Exceptions<8>,  Prev: Subprocesses,  Up: asyncio --- Asynchronous I/O

5.18.1.35 Queues
................

`Source code:' Lib/asyncio/queues.py(1)

__________________________________________________________________

asyncio queues are designed to be similar to classes of the *note queue:
db. module.  Although asyncio queues are not thread-safe, they are
designed to be used specifically in async/await code.

Note that methods of asyncio queues don’t have a `timeout' parameter;
use *note asyncio.wait_for(): 289. function to do queue operations with
a timeout.

See also the *note Examples: 257f. section below.

* Menu:

* Queue::
* Priority Queue::
* LIFO Queue::
* Exceptions: Exceptions<7>.
* Examples: Examples<13>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/asyncio/queues.py


File: python.info,  Node: Queue,  Next: Priority Queue,  Up: Queues

5.18.1.36 Queue
...............

 -- 類別: asyncio.Queue (maxsize=0, *, loop=None)

     A first in, first out (FIFO) queue.

     If `maxsize' is less than or equal to zero, the queue size is
     infinite.  If it is an integer greater than ‘0’, then ‘await put()’
     blocks when the queue reaches `maxsize' until an item is removed by
     *note get(): 2581.

     Unlike the standard library threading *note queue: db, the size of
     the queue is always known and can be returned by calling the *note
     qsize(): 2582. method.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `loop' parameter.

     This class is *note not thread safe: 250b.

      -- 屬性: maxsize

          Number of items allowed in the queue.

      -- 成員函式: empty ()

          Return ‘True’ if the queue is empty, ‘False’ otherwise.

      -- 成員函式: full ()

          Return ‘True’ if there are *note maxsize: 2583. items in the
          queue.

          If the queue was initialized with ‘maxsize=0’ (the default),
          then *note full(): 2585. never returns ‘True’.

      -- 成員函式: coroutine get ()

          Remove and return an item from the queue.  If queue is empty,
          wait until an item is available.

      -- 成員函式: get_nowait ()

          Return an item if one is immediately available, else raise
          *note QueueEmpty: 2587.

      -- 成員函式: coroutine join ()

          Block until all items in the queue have been received and
          processed.

          The count of unfinished tasks goes up whenever an item is
          added to the queue.  The count goes down whenever a consumer
          coroutine calls *note task_done(): 6a5. 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(): 6a4.
          unblocks.

      -- 成員函式: coroutine put (item)

          Put an item into the queue.  If the queue is full, wait until
          a free slot is available before adding the item.

      -- 成員函式: put_nowait (item)

          Put an item into the queue without blocking.

          If no free slot is immediately available, raise *note
          QueueFull: 258a.

      -- 成員函式: qsize ()

          Return the number of items in the queue.

      -- 成員函式: task_done ()

          Indicate that a formerly enqueued task is complete.

          Used by queue consumers.  For each *note get(): 2581. used to
          fetch a task, a subsequent call to *note task_done(): 6a5.
          tells the queue that the processing on the task is complete.

          If a *note join(): 6a4. is currently blocking, it will resume
          when all items have been processed (meaning that a *note
          task_done(): 6a5. call was received for every item that had
          been *note put(): 2588. into the queue).

          Raises *note ValueError: 1fc. if called more times than there
          were items placed in the queue.


File: python.info,  Node: Priority Queue,  Next: LIFO Queue,  Prev: Queue,  Up: Queues

5.18.1.37 Priority Queue
........................

 -- 類別: asyncio.PriorityQueue

     A variant of *note Queue: 291.; retrieves entries in priority order
     (lowest first).

     Entries are typically tuples of the form ‘(priority_number, data)’.


File: python.info,  Node: LIFO Queue,  Next: Exceptions<7>,  Prev: Priority Queue,  Up: Queues

5.18.1.38 LIFO Queue
....................

 -- 類別: asyncio.LifoQueue

     A variant of *note Queue: 291. that retrieves most recently added
     entries first (last in, first out).


File: python.info,  Node: Exceptions<7>,  Next: Examples<13>,  Prev: LIFO Queue,  Up: Queues

5.18.1.39 Exceptions
....................

 -- 例外: asyncio.QueueEmpty

     This exception is raised when the *note get_nowait(): 2586. method
     is called on an empty queue.

 -- 例外: asyncio.QueueFull

     Exception raised when the *note put_nowait(): 2589. method is
     called on a queue that has reached its `maxsize'.


File: python.info,  Node: Examples<13>,  Prev: Exceptions<7>,  Up: Queues

5.18.1.40 Examples
..................

Queues can be used to distribute workload between several concurrent
tasks:

     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: Exceptions<8>,  Next: Event Loop,  Prev: Queues,  Up: asyncio --- Asynchronous I/O

5.18.1.41 Exceptions
....................

`Source code:' Lib/asyncio/exceptions.py(1)

__________________________________________________________________

 -- 例外: asyncio.TimeoutError

     The operation has exceeded the given deadline.

          重要: This exception is different from the builtin *note
          TimeoutError: 9a1. exception.

 -- 例外: asyncio.CancelledError

     The operation has been cancelled.

     This exception can be caught to perform custom operations when
     asyncio Tasks are cancelled.  In almost all situations the
     exception must be re-raised.

     3.8 版更變: *note CancelledError: 1a8. is now a subclass of *note
     BaseException: 1a9.

 -- 例外: asyncio.InvalidStateError

     Invalid internal state of *note Task: 1ae. or *note Future: 448.

     Can be raised in situations like setting a result value for a
     `Future' object that already has a result value set.

 -- 例外: asyncio.SendfileNotAvailableError

     The "sendfile" syscall is not available for the given socket or
     file type.

     A subclass of *note RuntimeError: 2bb.

 -- 例外: asyncio.IncompleteReadError

     The requested read operation did not complete fully.

     Raised by the *note asyncio stream APIs: 24ee.

     This exception is a subclass of *note EOFError: c71.

      -- 屬性: expected

          The total number (*note int: 185.) of expected bytes.

      -- 屬性: partial

          A string of *note bytes: 336. read before the end of stream
          was reached.

 -- 例外: asyncio.LimitOverrunError

     Reached the buffer size limit while looking for a separator.

     Raised by the *note asyncio stream APIs: 24ee.

      -- 屬性: consumed

          The total number of to be consumed bytes.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/asyncio/exceptions.py


File: python.info,  Node: Event Loop,  Next: Futures,  Prev: Exceptions<8>,  Up: asyncio --- Asynchronous I/O

5.18.1.42 Event Loop
....................

`Source code:' Lib/asyncio/events.py(1), Lib/asyncio/base_events.py(2)

__________________________________________________________________

Preface
.......

The event loop is the core of every asyncio application.  Event loops
run asynchronous tasks and callbacks, perform network IO operations, and
run subprocesses.

Application developers should typically use the high-level asyncio
functions, such as *note asyncio.run(): 1a6, and should rarely need to
reference the loop object or call its methods.  This section is intended
mostly for authors of lower-level code, libraries, and frameworks, who
need finer control over the event loop behavior.

Obtaining the Event Loop
........................

The following low-level functions can be used to get, set, or create an
event loop:

 -- 函式: asyncio.get_running_loop ()

     Return the running event loop in the current OS thread.

     If there is no running event loop a *note RuntimeError: 2bb. is
     raised.  This function can only be called from a coroutine or a
     callback.

     3.7 版新加入.

 -- 函式: asyncio.get_event_loop ()

     Get the current event loop.

     If there is no current event loop set in the current OS thread, the
     OS thread is main, and *note set_event_loop(): 2599. has not yet
     been called, asyncio will create a new event loop and set it as the
     current one.

     Because this function has rather complex behavior (especially when
     custom event loop policies are in use), using the *note
     get_running_loop(): 359. function is preferred to *note
     get_event_loop(): 35a. in coroutines and callbacks.

     Consider also using the *note asyncio.run(): 1a6. function instead
     of using lower level functions to manually create and close an
     event loop.

 -- 函式: asyncio.set_event_loop (loop)

     Set `loop' as a current event loop for the current OS thread.

 -- 函式: asyncio.new_event_loop ()

     Create a new event loop object.

Note that the behaviour of *note get_event_loop(): 35a, *note
set_event_loop(): 2599, and *note new_event_loop(): 259a. functions can
be altered by *note setting a custom event loop policy: 259b.

Contents
........

This documentation page contains the following sections:

   * The *note Event Loop Methods: 259c. section is the reference
     documentation of the event loop APIs;

   * The *note Callback Handles: 259d. section documents the *note
     Handle: 10a7. and *note TimerHandle: 259e. instances which are
     returned from scheduling methods such as *note loop.call_soon():
     34e. and *note loop.call_later(): 350.;

   * The *note Server Objects: 259f. section documents types returned
     from event loop methods like *note loop.create_server(): 362.;

   * The *note Event Loop Implementations: 25a0. section documents the
     *note SelectorEventLoop: 2578. and *note ProactorEventLoop: 1ac.
     classes;

   * The *note Examples: 25a1. section showcases how to work with some
     event loop APIs.

* Menu:

* Event Loop Methods::
* Callback Handles::
* Server Objects::
* Event Loop Implementations::
* Examples: Examples<14>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/asyncio/events.py

   (2) 
https://github.com/python/cpython/tree/3.8/Lib/asyncio/base_events.py


File: python.info,  Node: Event Loop Methods,  Next: Callback Handles,  Up: Event Loop

5.18.1.43 Event Loop Methods
............................

Event loops have `low-level' APIs for the following:

* Menu:

* Running and stopping the loop::
* Scheduling callbacks::
* Scheduling delayed callbacks::
* Creating Futures and Tasks::
* Opening network connections::
* Creating network servers::
* Transferring files::
* TLS Upgrade::
* Watching file descriptors::
* Working with socket objects directly::
* DNS::
* Working with pipes::
* Unix signals::
* Executing code in thread or process pools::
* Error Handling API::
* Enabling debug mode::
* Running Subprocesses::


File: python.info,  Node: Running and stopping the loop,  Next: Scheduling callbacks,  Up: Event Loop Methods

5.18.1.44 Running and stopping the loop
.......................................

 -- 成員函式: loop.run_until_complete (future)

     Run until the `future' (an instance of *note Future: 448.) has
     completed.

     If the argument is a *note coroutine object: 24ed. it is implicitly
     scheduled to run as a *note asyncio.Task: 1ae.

     Return the Future’s result or raise its exception.

 -- 成員函式: loop.run_forever ()

     Run the event loop until *note stop(): 525. is called.

     If *note stop(): 525. is called before *note run_forever(): 25a3.
     is called, the loop will poll the I/O selector once with a timeout
     of zero, run all callbacks scheduled in response to I/O events (and
     those that were already scheduled), and then exit.

     If *note stop(): 525. is called while *note run_forever(): 25a3. is
     running, the loop will run the current batch of callbacks and then
     exit.  Note that new callbacks scheduled by callbacks will not run
     in this case; instead, they will run the next time *note
     run_forever(): 25a3. or *note run_until_complete(): 51d. is called.

 -- 成員函式: loop.stop ()

     Stop the event loop.

 -- 成員函式: loop.is_running ()

     Return ‘True’ if the event loop is currently running.

 -- 成員函式: loop.is_closed ()

     Return ‘True’ if the event loop was closed.

 -- 成員函式: loop.close ()

     Close the event loop.

     The loop must not be running when this function is called.  Any
     pending callbacks will be discarded.

     This method clears all queues and shuts down the executor, but does
     not wait for the executor to finish.

     This method is idempotent and irreversible.  No other methods
     should be called after the event loop is closed.

 -- 成員函式: coroutine loop.shutdown_asyncgens ()

     Schedule all currently open *note asynchronous generator: 1508.
     objects to close with an *note aclose(): 1510. call.  After calling
     this method, the event loop will issue a warning if a new
     asynchronous generator is iterated.  This should be used to
     reliably finalize all scheduled asynchronous generators.

     Note that there is no need to call this function when *note
     asyncio.run(): 1a6. is used.

     Example:

          try:
              loop.run_forever()
          finally:
              loop.run_until_complete(loop.shutdown_asyncgens())
              loop.close()

     3.6 版新加入.


File: python.info,  Node: Scheduling callbacks,  Next: Scheduling delayed callbacks,  Prev: Running and stopping the loop,  Up: Event Loop Methods

5.18.1.45 Scheduling callbacks
..............................

 -- 成員函式: loop.call_soon (callback, *args, context=None)

     Schedule the `callback' *note callback: 25a7. to be called with
     `args' arguments at the next iteration of the event loop.

     Callbacks are called in the order in which they are registered.
     Each callback will be called exactly once.

     An optional keyword-only `context' argument allows specifying a
     custom *note contextvars.Context: 24c1. for the `callback' to run
     in.  The current context is used when no `context' is provided.

     An instance of *note asyncio.Handle: 10a7. is returned, which can
     be used later to cancel the callback.

     This method is not thread-safe.

 -- 成員函式: loop.call_soon_threadsafe (callback, *args, context=None)

     A thread-safe variant of *note call_soon(): 34e.  Must be used to
     schedule callbacks `from another thread'.

     See the *note concurrency and multithreading: 250b. section of the
     documentation.

3.7 版更變: The `context' keyword-only parameter was added.  See PEP
567(1) for more details.

     備註: Most *note asyncio: a. scheduling functions don’t allow
     passing keyword arguments.  To do that, use *note
     functools.partial(): 7cd.:

          # will schedule "print("Hello", flush=True)"
          loop.call_soon(
              functools.partial(print, "Hello", flush=True))

     Using partial objects is usually more convenient than using
     lambdas, as asyncio can render partial objects better in debug and
     error messages.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0567


File: python.info,  Node: Scheduling delayed callbacks,  Next: Creating Futures and Tasks,  Prev: Scheduling callbacks,  Up: Event Loop Methods

5.18.1.46 Scheduling delayed callbacks
......................................

Event loop provides mechanisms to schedule callback functions to be
called at some point in the future.  Event loop uses monotonic clocks to
track time.

 -- 成員函式: loop.call_later (delay, callback, *args, context=None)

     Schedule `callback' to be called after the given `delay' number of
     seconds (can be either an int or a float).

     An instance of *note asyncio.TimerHandle: 259e. is returned which
     can be used to cancel the callback.

     `callback' will be called exactly once.  If two callbacks are
     scheduled for exactly the same time, the order in which they are
     called is undefined.

     The optional positional `args' will be passed to the callback when
     it is called.  If you want the callback to be called with keyword
     arguments use *note functools.partial(): 7cd.

     An optional keyword-only `context' argument allows specifying a
     custom *note contextvars.Context: 24c1. for the `callback' to run
     in.  The current context is used when no `context' is provided.

     3.7 版更變: The `context' keyword-only parameter was added.  See
     PEP 567(1) for more details.

     3.8 版更變: In Python 3.7 and earlier with the default event loop
     implementation, the `delay' could not exceed one day.  This has
     been fixed in Python 3.8.

 -- 成員函式: loop.call_at (when, callback, *args, context=None)

     Schedule `callback' to be called at the given absolute timestamp
     `when' (an int or a float), using the same time reference as *note
     loop.time(): 25ab.

     This method’s behavior is the same as *note call_later(): 350.

     An instance of *note asyncio.TimerHandle: 259e. is returned which
     can be used to cancel the callback.

     3.7 版更變: The `context' keyword-only parameter was added.  See
     PEP 567(2) for more details.

     3.8 版更變: In Python 3.7 and earlier with the default event loop
     implementation, the difference between `when' and the current time
     could not exceed one day.  This has been fixed in Python 3.8.

 -- 成員函式: loop.time ()

     Return the current time, as a *note float: 188. value, according to
     the event loop’s internal monotonic clock.

     備註: 
     3.8 版更變: In Python 3.7 and earlier timeouts (relative `delay' or
     absolute `when') should not exceed one day.  This has been fixed in
     Python 3.8.

也參考
......

The *note asyncio.sleep(): 286. function.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0567

   (2) https://www.python.org/dev/peps/pep-0567


File: python.info,  Node: Creating Futures and Tasks,  Next: Opening network connections,  Prev: Scheduling delayed callbacks,  Up: Event Loop Methods

5.18.1.47 Creating Futures and Tasks
....................................

 -- 成員函式: loop.create_future ()

     Create an *note asyncio.Future: 448. object attached to the event
     loop.

     This is the preferred way to create Futures in asyncio.  This lets
     third-party event loops provide alternative implementations of the
     Future object (with better performance or instrumentation).

     3.5.2 版新加入.

 -- 成員函式: loop.create_task (coro, *, name=None)

     Schedule the execution of a *note Coroutines: 24ed.  Return a *note
     Task: 1ae. object.

     Third-party event loops can use their own subclass of *note Task:
     1ae. for interoperability.  In this case, the result type is a
     subclass of *note Task: 1ae.

     If the `name' argument is provided and not ‘None’, it is set as the
     name of the task using *note Task.set_name(): 1b1.

     3.8 版更變: Added the ‘name’ parameter.

 -- 成員函式: loop.set_task_factory (factory)

     Set a task factory that will be used by *note loop.create_task():
     1b0.

     If `factory' is ‘None’ the default task factory will be set.
     Otherwise, `factory' must be a `callable' with the signature
     matching ‘(loop, coro)’, where `loop' is a reference to the active
     event loop, and `coro' is a coroutine object.  The callable must
     return a *note asyncio.Future: 448.-compatible object.

 -- 成員函式: loop.get_task_factory ()

     Return a task factory or ‘None’ if the default one is in use.


File: python.info,  Node: Opening network connections,  Next: Creating network servers,  Prev: Creating Futures and Tasks,  Up: Event Loop Methods

5.18.1.48 Opening network connections
.....................................

 -- 成員函式: 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, happy_eyeballs_delay=None,
          interleave=None)

     Open a streaming transport connection to a given address specified
     by `host' and `port'.

     The socket family can be either *note AF_INET: 25ae. or *note
     AF_INET6: 25af. depending on `host' (or the `family' argument, if
     provided).

     The socket type will be *note SOCK_STREAM: c8f.

     `protocol_factory' must be a callable returning an *note asyncio
     protocol: 25b0. implementation.

     This method will try to establish the connection in the background.
     When successful, it returns a ‘(transport, protocol)’ pair.

     The chronological synopsis of the underlying operation is as
     follows:

       1. The connection is established and a *note transport: 25b1. is
          created for it.

       2. `protocol_factory' is called without arguments and is expected
          to return a *note protocol: 25b0. instance.

       3. The protocol instance is coupled with the transport by calling
          its *note connection_made(): 25b2. method.

       4. A ‘(transport, protocol)’ tuple is returned on success.

     The created transport is an implementation-dependent bidirectional
     stream.

     Other arguments:

        * `ssl': if given and not false, a SSL/TLS transport is created
          (by default a plain TCP transport is created).  If `ssl' is a
          *note ssl.SSLContext: 3e9. object, this context is used to
          create the transport; if `ssl' is *note True: 49e, a default
          context returned from *note ssl.create_default_context(): 8c6.
          is used.

          也參考
          ......

          *note SSL/TLS security considerations: 25b3.

        * `server_hostname' sets or overrides the hostname that the
          target server’s certificate will be matched against.  Should
          only be passed if `ssl' is not ‘None’.  By default the value
          of the `host' argument is used.  If `host' is empty, there is
          no default and you must pass a value for `server_hostname'.
          If `server_hostname' is an empty string, hostname matching is
          disabled (which is a serious security risk, allowing for
          potential man-in-the-middle attacks).

        * `family', `proto', `flags' are the optional address family,
          protocol and flags to be passed through to getaddrinfo() for
          `host' resolution.  If given, these should all be integers
          from the corresponding *note socket: f0. module constants.

        * `happy_eyeballs_delay', if given, enables Happy Eyeballs for
          this connection.  It should be a floating-point number
          representing the amount of time in seconds to wait for a
          connection attempt to complete, before starting the next
          attempt in parallel.  This is the "Connection Attempt Delay"
          as defined in RFC 8305(1).  A sensible default value
          recommended by the RFC is ‘0.25’ (250 milliseconds).

        * `interleave' controls address reordering when a host name
          resolves to multiple IP addresses.  If ‘0’ or unspecified, no
          reordering is done, and addresses are tried in the order
          returned by *note getaddrinfo(): 4a6.  If a positive integer
          is specified, the addresses are interleaved by address family,
          and the given integer is interpreted as "First Address Family
          Count" as defined in RFC 8305(2).  The default is ‘0’ if
          `happy_eyeballs_delay' is not specified, and ‘1’ if it is.

        * `sock', if given, should be an existing, already connected
          *note socket.socket: 679. object to be used by the transport.
          If `sock' is given, none of `host', `port', `family', `proto',
          `flags', `happy_eyeballs_delay', `interleave' and `local_addr'
          should be specified.

        * `local_addr', if given, is a ‘(local_host, local_port)’ tuple
          used to bind the socket to locally.  The `local_host' and
          `local_port' are looked up using ‘getaddrinfo()’, similarly to
          `host' and `port'.

        * `ssl_handshake_timeout' is (for a TLS connection) the time in
          seconds to wait for the TLS handshake to complete before
          aborting the connection.  ‘60.0’ seconds if ‘None’ (default).

     3.8 版新加入: Added the `happy_eyeballs_delay' and `interleave'
     parameters.

     Happy Eyeballs Algorithm: Success with Dual-Stack Hosts.  When a
     server’s IPv4 path and protocol are working, but the server’s IPv6
     path and protocol are not working, a dual-stack client application
     experiences significant connection delay compared to an IPv4-only
     client.  This is undesirable because it causes the dual- stack
     client to have a worse user experience.  This document specifies
     requirements for algorithms that reduce this user-visible delay and
     provides an algorithm.

     For more information: ‘https://tools.ietf.org/html/rfc6555’

     3.7 版新加入: The `ssl_handshake_timeout' parameter.

     3.6 版更變: The socket option ‘TCP_NODELAY’ is set by default for
     all TCP connections.

     3.5 版更變: Added support for SSL/TLS in *note ProactorEventLoop:
     1ac.

     也參考
     ......

     The *note open_connection(): 368. function is a high-level
     alternative API. It returns a pair of (*note StreamReader: fcf,
     *note StreamWriter: fd0.) that can be used directly in async/await
     code.

 -- 成員函式: coroutine loop.create_datagram_endpoint (protocol_factory,
          local_addr=None, remote_addr=None, *, family=0, proto=0,
          flags=0, reuse_address=None, reuse_port=None,
          allow_broadcast=None, sock=None)

          備註: The parameter `reuse_address' is no longer supported, as
          using ‘SO_REUSEADDR’ poses a significant security concern for
          UDP. Explicitly passing ‘reuse_address=True’ will raise an
          exception.

          When multiple processes with differing UIDs assign sockets to
          an identical UDP socket address with ‘SO_REUSEADDR’, incoming
          packets can become randomly distributed among the sockets.

          For supported platforms, `reuse_port' can be used as a
          replacement for similar functionality.  With `reuse_port',
          ‘SO_REUSEPORT’ is used instead, which specifically prevents
          processes with differing UIDs from assigning sockets to the
          same socket address.

     Create a datagram connection.

     The socket family can be either *note AF_INET: 25ae, *note
     AF_INET6: 25af, or *note AF_UNIX: 25b4, depending on `host' (or the
     `family' argument, if provided).

     The socket type will be *note SOCK_DGRAM: c8e.

     `protocol_factory' must be a callable returning a *note protocol:
     25b0. implementation.

     A tuple of ‘(transport, protocol)’ is returned on success.

     Other arguments:

        * `local_addr', if given, is a ‘(local_host, local_port)’ tuple
          used to bind the socket to locally.  The `local_host' and
          `local_port' are looked up using *note getaddrinfo(): 4a6.

        * `remote_addr', if given, is a ‘(remote_host, remote_port)’
          tuple used to connect the socket to a remote address.  The
          `remote_host' and `remote_port' are looked up using *note
          getaddrinfo(): 4a6.

        * `family', `proto', `flags' are the optional address family,
          protocol and flags to be passed through to *note
          getaddrinfo(): 4a6. for `host' resolution.  If given, these
          should all be integers from the corresponding *note socket:
          f0. module constants.

        * `reuse_port' tells the kernel to allow this endpoint to be
          bound to the same port as other existing endpoints are bound
          to, so long as they all set this flag when being created.
          This option is not supported on Windows and some Unixes.  If
          the ‘SO_REUSEPORT’ constant is not defined then this
          capability is unsupported.

        * `allow_broadcast' tells the kernel to allow this endpoint to
          send messages to the broadcast address.

        * `sock' can optionally be specified in order to use a
          preexisting, already connected, *note socket.socket: 679.
          object to be used by the transport.  If specified,
          `local_addr' and `remote_addr' should be omitted (must be
          *note None: 158.).

     See *note UDP echo client protocol: 25b5. and *note UDP echo server
     protocol: 25b6. examples.

     3.4.4 版更變: The `family', `proto', `flags', `reuse_address',
     `reuse_port, *allow_broadcast', and `sock' parameters were added.

     3.8.1 版更變: The `reuse_address' parameter is no longer supported
     due to security concerns.

     3.8 版更變: Added support for Windows.

 -- 成員函式: coroutine loop.create_unix_connection (protocol_factory,
          path=None, *, ssl=None, sock=None, server_hostname=None,
          ssl_handshake_timeout=None)

     Create a Unix connection.

     The socket family will be *note AF_UNIX: 25b4.; socket type will be
     *note SOCK_STREAM: c8f.

     A tuple of ‘(transport, protocol)’ is returned on success.

     `path' is the name of a Unix domain socket and is required, unless
     a `sock' parameter is specified.  Abstract Unix sockets, *note str:
     335, *note bytes: 336, and *note Path: 202. paths are supported.

     See the documentation of the *note loop.create_connection(): 1b3.
     method for information about arguments to this method.

     *note Availability: 1364.: Unix.

     3.7 版新加入: The `ssl_handshake_timeout' parameter.

     3.7 版更變: The `path' parameter can now be a *note path-like
     object: 36f.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc8305.html

   (2) https://tools.ietf.org/html/rfc8305.html


File: python.info,  Node: Creating network servers,  Next: Transferring files,  Prev: Opening network connections,  Up: Event Loop Methods

5.18.1.49 Creating network servers
..................................

 -- 成員函式: 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,
          ssl_handshake_timeout=None, start_serving=True)

     Create a TCP server (socket type *note SOCK_STREAM: c8f.) listening
     on `port' of the `host' address.

     Returns a *note Server: 361. object.

     Arguments:

        * `protocol_factory' must be a callable returning a *note
          protocol: 25b0. implementation.

        * The `host' parameter can be set to several types which
          determine where the server would be listening:

             - If `host' is a string, the TCP server is bound to a
               single network interface specified by `host'.

             - If `host' is a sequence of strings, the TCP server is
               bound to all network interfaces specified by the
               sequence.

             - If `host' is an empty string or ‘None’, all interfaces
               are assumed and a list of multiple sockets will be
               returned (most likely one for IPv4 and another one for
               IPv6).

        * `family' can be set to either *note socket.AF_INET: 25ae. or
          *note AF_INET6: 25af. to force the socket to use IPv4 or IPv6.
          If not set, the `family' will be determined from host name
          (defaults to ‘AF_UNSPEC’).

        * `flags' is a bitmask for *note getaddrinfo(): 4a6.

        * `sock' can optionally be specified in order to use a
          preexisting socket object.  If specified, `host' and `port'
          must not be specified.

        * `backlog' is the maximum number of queued connections passed
          to *note listen(): 750. (defaults to 100).

        * `ssl' can be set to an *note SSLContext: 3e9. instance to
          enable TLS over the accepted connections.

        * `reuse_address' tells the kernel to reuse a local socket in
          ‘TIME_WAIT’ state, without waiting for its natural timeout to
          expire.  If not specified will automatically be set to ‘True’
          on Unix.

        * `reuse_port' tells the kernel to allow this endpoint to be
          bound to the same port as other existing endpoints are bound
          to, so long as they all set this flag when being created.
          This option is not supported on Windows.

        * `ssl_handshake_timeout' is (for a TLS server) the time in
          seconds to wait for the TLS handshake to complete before
          aborting the connection.  ‘60.0’ seconds if ‘None’ (default).

        * `start_serving' set to ‘True’ (the default) causes the created
          server to start accepting connections immediately.  When set
          to ‘False’, the user should await on *note
          Server.start_serving(): 364. or *note Server.serve_forever():
          365. to make the server to start accepting connections.

     3.7 版新加入: Added `ssl_handshake_timeout' and `start_serving'
     parameters.

     3.6 版更變: The socket option ‘TCP_NODELAY’ is set by default for
     all TCP connections.

     3.5 版更變: Added support for SSL/TLS in *note ProactorEventLoop:
     1ac.

     3.5.1 版更變: The `host' parameter can be a sequence of strings.

     也參考
     ......

     The *note start_server(): 369. function is a higher-level
     alternative API that returns a pair of *note StreamReader: fcf. and
     *note StreamWriter: fd0. that can be used in an async/await code.

 -- 成員函式: coroutine loop.create_unix_server (protocol_factory,
          path=None, *, sock=None, backlog=100, ssl=None,
          ssl_handshake_timeout=None, start_serving=True)

     Similar to *note loop.create_server(): 362. but works with the
     *note AF_UNIX: 25b4. socket family.

     `path' is the name of a Unix domain socket, and is required, unless
     a `sock' argument is provided.  Abstract Unix sockets, *note str:
     335, *note bytes: 336, and *note Path: 202. paths are supported.

     See the documentation of the *note loop.create_server(): 362.
     method for information about arguments to this method.

     *note Availability: 1364.: Unix.

     3.7 版新加入: The `ssl_handshake_timeout' and `start_serving'
     parameters.

     3.7 版更變: The `path' parameter can now be a *note Path: 202.
     object.

 -- 成員函式: coroutine loop.connect_accepted_socket (protocol_factory,
          sock, *, ssl=None, ssl_handshake_timeout=None)

     Wrap an already accepted connection into a transport/protocol pair.

     This method can be used by servers that accept connections outside
     of asyncio but that use asyncio to handle them.

     Parameters:

        * `protocol_factory' must be a callable returning a *note
          protocol: 25b0. implementation.

        * `sock' is a preexisting socket object returned from *note
          socket.accept: 67a.

        * `ssl' can be set to an *note SSLContext: 3e9. to enable SSL
          over the accepted connections.

        * `ssl_handshake_timeout' is (for an SSL connection) the time in
          seconds to wait for the SSL handshake to complete before
          aborting the connection.  ‘60.0’ seconds if ‘None’ (default).

     Returns a ‘(transport, protocol)’ pair.

     3.7 版新加入: The `ssl_handshake_timeout' parameter.

     3.5.3 版新加入.


File: python.info,  Node: Transferring files,  Next: TLS Upgrade,  Prev: Creating network servers,  Up: Event Loop Methods

5.18.1.50 Transferring files
............................

 -- 成員函式: coroutine loop.sendfile (transport, file, offset=0,
          count=None, *, fallback=True)

     Send a `file' over a `transport'.  Return the total number of bytes
     sent.

     The method uses high-performance *note os.sendfile(): 35e. if
     available.

     `file' must be a regular file object opened in binary mode.

     `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 always
     updated, even when this method raises an error, and *note
     file.tell(): 1d9e. can be used to obtain the actual number of bytes
     sent.

     `fallback' set to ‘True’ makes asyncio to manually read and send
     the file when the platform does not support the sendfile system
     call (e.g.  Windows or SSL socket on Unix).

     Raise *note SendfileNotAvailableError: 2594. if the system does not
     support the `sendfile' syscall and `fallback' is ‘False’.

     3.7 版新加入.


File: python.info,  Node: TLS Upgrade,  Next: Watching file descriptors,  Prev: Transferring files,  Up: Event Loop Methods

5.18.1.51 TLS Upgrade
.....................

 -- 成員函式: coroutine loop.start_tls (transport, protocol, sslcontext,
          *, server_side=False, server_hostname=None,
          ssl_handshake_timeout=None)

     Upgrade an existing transport-based connection to TLS.

     Return a new transport instance, that the `protocol' must start
     using immediately after the `await'.  The `transport' instance
     passed to the `start_tls' method should never be used again.

     Parameters:

        * `transport' and `protocol' instances that methods like *note
          create_server(): 362. and *note create_connection(): 1b3.
          return.

        * `sslcontext': a configured instance of *note SSLContext: 3e9.

        * `server_side' pass ‘True’ when a server-side connection is
          being upgraded (like the one created by *note create_server():
          362.).

        * `server_hostname': sets or overrides the host name that the
          target server’s certificate will be matched against.

        * `ssl_handshake_timeout' is (for a TLS connection) the time in
          seconds to wait for the TLS handshake to complete before
          aborting the connection.  ‘60.0’ seconds if ‘None’ (default).

     3.7 版新加入.


File: python.info,  Node: Watching file descriptors,  Next: Working with socket objects directly,  Prev: TLS Upgrade,  Up: Event Loop Methods

5.18.1.52 Watching file descriptors
...................................

 -- 成員函式: loop.add_reader (fd, callback, *args)

     Start monitoring the `fd' file descriptor for read availability and
     invoke `callback' with the specified arguments once `fd' is
     available for reading.

 -- 成員函式: loop.remove_reader (fd)

     Stop monitoring the `fd' file descriptor for read availability.

 -- 成員函式: loop.add_writer (fd, callback, *args)

     Start monitoring the `fd' file descriptor for write availability
     and invoke `callback' with the specified arguments once `fd' is
     available for writing.

     Use *note functools.partial(): 7cd. *note to pass keyword
     arguments: 25a8. to `callback'.

 -- 成員函式: loop.remove_writer (fd)

     Stop monitoring the `fd' file descriptor for write availability.

See also *note Platform Support: 25bf. section for some limitations of
these methods.


File: python.info,  Node: Working with socket objects directly,  Next: DNS,  Prev: Watching file descriptors,  Up: Event Loop Methods

5.18.1.53 Working with socket objects directly
..............................................

In general, protocol implementations that use transport-based APIs such
as *note loop.create_connection(): 1b3. and *note loop.create_server():
362. are faster than implementations that work with sockets directly.
However, there are some use cases when performance is not critical, and
working with *note socket: 679. objects directly is more convenient.

 -- 成員函式: coroutine loop.sock_recv (sock, nbytes)

     Receive up to `nbytes' from `sock'.  Asynchronous version of *note
     socket.recv(): 67c.

     Return the received data as a bytes object.

     `sock' must be a non-blocking socket.

     3.7 版更變: Even though this method was always documented as a
     coroutine method, releases before Python 3.7 returned a *note
     Future: 448.  Since Python 3.7 this is an ‘async def’ method.

 -- 成員函式: coroutine loop.sock_recv_into (sock, buf)

     Receive data from `sock' into the `buf' buffer.  Modeled after the
     blocking *note socket.recv_into(): cb7. method.

     Return the number of bytes written to the buffer.

     `sock' must be a non-blocking socket.

     3.7 版新加入.

 -- 成員函式: coroutine loop.sock_sendall (sock, data)

     Send `data' to the `sock' socket.  Asynchronous version of *note
     socket.sendall(): 680.

     This method continues to send to the socket until either all data
     in `data' has been sent or an error occurs.  ‘None’ is returned on
     success.  On error, an exception is raised.  Additionally, there is
     no way to determine how much data, if any, was successfully
     processed by the receiving end of the connection.

     `sock' must be a non-blocking socket.

     3.7 版更變: Even though the method was always documented as a
     coroutine method, before Python 3.7 it returned an *note Future:
     448.  Since Python 3.7, this is an ‘async def’ method.

 -- 成員函式: coroutine loop.sock_connect (sock, address)

     Connect `sock' to a remote socket at `address'.

     Asynchronous version of *note socket.connect(): 67b.

     `sock' must be a non-blocking socket.

     3.5.2 版更變: ‘address’ no longer needs to be resolved.
     ‘sock_connect’ will try to check if the `address' is already
     resolved by calling *note socket.inet_pton(): 8c0.  If not, *note
     loop.getaddrinfo(): 4a6. will be used to resolve the `address'.

     也參考
     ......

     *note loop.create_connection(): 1b3. and *note
     asyncio.open_connection(): 368.

 -- 成員函式: coroutine loop.sock_accept (sock)

     Accept a connection.  Modeled after the blocking *note
     socket.accept(): 67a. method.

     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.

     `sock' must be a non-blocking socket.

     3.7 版更變: Even though the method was always documented as a
     coroutine method, before Python 3.7 it returned a *note Future:
     448.  Since Python 3.7, this is an ‘async def’ method.

     也參考
     ......

     *note loop.create_server(): 362. and *note start_server(): 369.

 -- 成員函式: coroutine loop.sock_sendfile (sock, file, offset=0,
          count=None, *, fallback=True)

     Send a file using high-performance *note os.sendfile: 35e. if
     possible.  Return the total number of bytes sent.

     Asynchronous version of *note socket.sendfile(): 74f.

     `sock' must be a non-blocking *note socket.SOCK_STREAM: c8f. *note
     socket: 679.

     `file' must be a regular file object open in binary mode.

     `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 always
     updated, even when this method raises an error, and *note
     file.tell(): 1d9e. can be used to obtain the actual number of bytes
     sent.

     `fallback', when set to ‘True’, makes asyncio manually read and
     send the file when the platform does not support the sendfile
     syscall (e.g.  Windows or SSL socket on Unix).

     Raise *note SendfileNotAvailableError: 2594. if the system does not
     support `sendfile' syscall and `fallback' is ‘False’.

     `sock' must be a non-blocking socket.

     3.7 版新加入.


File: python.info,  Node: DNS,  Next: Working with pipes,  Prev: Working with socket objects directly,  Up: Event Loop Methods

5.18.1.54 DNS
.............

 -- 成員函式: coroutine loop.getaddrinfo (host, port, *, family=0,
          type=0, proto=0, flags=0)

     Asynchronous version of *note socket.getaddrinfo(): 25c2.

 -- 成員函式: coroutine loop.getnameinfo (sockaddr, flags=0)

     Asynchronous version of *note socket.getnameinfo(): 25c3.

3.7 版更變: Both `getaddrinfo' and `getnameinfo' methods were always
documented to return a coroutine, but prior to Python 3.7 they were, in
fact, returning *note asyncio.Future: 448. objects.  Starting with
Python 3.7 both methods are coroutines.


File: python.info,  Node: Working with pipes,  Next: Unix signals,  Prev: DNS,  Up: Event Loop Methods

5.18.1.55 Working with pipes
............................

 -- 成員函式: coroutine loop.connect_read_pipe (protocol_factory, pipe)

     Register the read end of `pipe' in the event loop.

     `protocol_factory' must be a callable returning an *note asyncio
     protocol: 25b0. implementation.

     `pipe' is a *note file-like object: b47.

     Return pair ‘(transport, protocol)’, where `transport' supports the
     *note ReadTransport: 25c5. interface and `protocol' is an object
     instantiated by the `protocol_factory'.

     With *note SelectorEventLoop: 2578. event loop, the `pipe' is set
     to non-blocking mode.

 -- 成員函式: coroutine loop.connect_write_pipe (protocol_factory, pipe)

     Register the write end of `pipe' in the event loop.

     `protocol_factory' must be a callable returning an *note asyncio
     protocol: 25b0. implementation.

     `pipe' is *note file-like object: b47.

     Return pair ‘(transport, protocol)’, where `transport' supports
     *note WriteTransport: 25c6. interface and `protocol' is an object
     instantiated by the `protocol_factory'.

     With *note SelectorEventLoop: 2578. event loop, the `pipe' is set
     to non-blocking mode.

     備註: *note SelectorEventLoop: 2578. does not support the above
     methods on Windows.  Use *note ProactorEventLoop: 1ac. instead for
     Windows.

也參考
......

The *note loop.subprocess_exec(): 24f2. and *note
loop.subprocess_shell(): 2560. methods.


File: python.info,  Node: Unix signals,  Next: Executing code in thread or process pools,  Prev: Working with pipes,  Up: Event Loop Methods

5.18.1.56 Unix signals
......................

 -- 成員函式: loop.add_signal_handler (signum, callback, *args)

     Set `callback' as the handler for the `signum' signal.

     The callback will be invoked by `loop', along with other queued
     callbacks and runnable coroutines of that event loop.  Unlike
     signal handlers registered using *note signal.signal(): a82, a
     callback registered with this function is allowed to interact with
     the event loop.

     Raise *note ValueError: 1fc. if the signal number is invalid or
     uncatchable.  Raise *note RuntimeError: 2bb. if there is a problem
     setting up the handler.

     Use *note functools.partial(): 7cd. *note to pass keyword
     arguments: 25a8. to `callback'.

     Like *note signal.signal(): a82, this function must be invoked in
     the main thread.

 -- 成員函式: loop.remove_signal_handler (sig)

     Remove the handler for the `sig' signal.

     Return ‘True’ if the signal handler was removed, or ‘False’ if no
     handler was set for the given signal.

     *note Availability: 1364.: Unix.

也參考
......

The *note signal: eb. module.


File: python.info,  Node: Executing code in thread or process pools,  Next: Error Handling API,  Prev: Unix signals,  Up: Event Loop Methods

5.18.1.57 Executing code in thread or process pools
...................................................

 -- 成員函式: awaitable loop.run_in_executor (executor, func, *args)

     Arrange for `func' to be called in the specified executor.

     The `executor' argument should be an *note
     concurrent.futures.Executor: 243a. instance.  The default executor
     is used if `executor' is ‘None’.

     Example:

          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)

          asyncio.run(main())

     This method returns a *note asyncio.Future: 448. object.

     Use *note functools.partial(): 7cd. *note to pass keyword
     arguments: 25a8. to `func'.

     3.5.3 版更變: *note loop.run_in_executor(): 24fc. no longer
     configures the ‘max_workers’ of the thread pool executor it
     creates, instead leaving it up to the thread pool executor (*note
     ThreadPoolExecutor: 27b.) to set the default.

 -- 成員函式: loop.set_default_executor (executor)

     Set `executor' as the default executor used by *note
     run_in_executor(): 24fc.  `executor' should be an instance of *note
     ThreadPoolExecutor: 27b.

     3.8 版後已棄用: Using an executor that is not an instance of *note
     ThreadPoolExecutor: 27b. is deprecated and will trigger an error in
     Python 3.9.

     `executor' must be an instance of *note
     concurrent.futures.ThreadPoolExecutor: 27b.


File: python.info,  Node: Error Handling API,  Next: Enabling debug mode,  Prev: Executing code in thread or process pools,  Up: Event Loop Methods

5.18.1.58 Error Handling API
............................

Allows customizing how exceptions are handled in the event loop.

 -- 成員函式: loop.set_exception_handler (handler)

     Set `handler' as the new event loop exception handler.

     If `handler' is ‘None’, the default exception handler will be set.
     Otherwise, `handler' must be a callable with the signature matching
     ‘(loop, context)’, where ‘loop’ is a reference to the active event
     loop, and ‘context’ is a ‘dict’ object containing the details of
     the exception (see *note call_exception_handler(): 25cc.
     documentation for details about context).

 -- 成員函式: loop.get_exception_handler ()

     Return the current exception handler, or ‘None’ if no custom
     exception handler was set.

     3.5.2 版新加入.

 -- 成員函式: loop.default_exception_handler (context)

     Default exception handler.

     This is called when an exception occurs and no exception handler is
     set.  This can be called by a custom exception handler that wants
     to defer to the default handler behavior.

     `context' parameter has the same meaning as in *note
     call_exception_handler(): 25cc.

 -- 成員函式: loop.call_exception_handler (context)

     Call the current event loop exception handler.

     `context' is a ‘dict’ object containing the following keys (new
     keys may be introduced in future Python versions):

        * ’message’: Error message;

        * ’exception’ (optional): Exception object;

        * ’future’ (optional): *note asyncio.Future: 448. instance;

        * ’handle’ (optional): *note asyncio.Handle: 10a7. instance;

        * ’protocol’ (optional): *note Protocol: 25b0. instance;

        * ’transport’ (optional): *note Transport: 25b1. instance;

        * ’socket’ (optional): *note socket.socket: 679. instance.

          備註: This method should not be overloaded in subclassed event
          loops.  For custom exception handling, use the *note
          set_exception_handler(): 25cb. method.


File: python.info,  Node: Enabling debug mode,  Next: Running Subprocesses,  Prev: Error Handling API,  Up: Event Loop Methods

5.18.1.59 Enabling debug mode
.............................

 -- 成員函式: loop.get_debug ()

     Get the debug mode (*note bool: 184.) of the event loop.

     The default value is ‘True’ if the environment variable *note
     PYTHONASYNCIODEBUG: 1361. is set to a non-empty string, ‘False’
     otherwise.

 -- 成員函式: loop.set_debug (enabled: bool)

     Set the debug mode of the event loop.

     3.7 版更變: The new ‘-X dev’ command line option can now also be
     used to enable the debug mode.

也參考
......

The *note debug mode of asyncio: 1355.


File: python.info,  Node: Running Subprocesses,  Prev: Enabling debug mode,  Up: Event Loop Methods

5.18.1.60 Running Subprocesses
..............................

Methods described in this subsections are low-level.  In regular
async/await code consider using the high-level *note
asyncio.create_subprocess_shell(): 293. and *note
asyncio.create_subprocess_exec(): 292. convenience functions instead.

     備註: The default asyncio event loop on `Windows' does not support
     subprocesses.  See *note Subprocess Support on Windows: 2561. for
     details.

 -- 成員函式: coroutine loop.subprocess_exec (protocol_factory, *args,
          stdin=subprocess.PIPE, stdout=subprocess.PIPE,
          stderr=subprocess.PIPE, **kwargs)

     Create a subprocess from one or more string arguments specified by
     `args'.

     `args' must be a list of strings represented by:

        * *note str: 335.;

        * or *note bytes: 336, encoded to the *note filesystem encoding:
          1ee7.

     The first string specifies the program executable, and the
     remaining strings specify the arguments.  Together, string
     arguments form the ‘argv’ of the program.

     This is similar to the standard library *note subprocess.Popen:
     2ba. class called with ‘shell=False’ and the list of strings passed
     as the first argument; however, where *note Popen: 2ba. takes a
     single argument which is list of strings, `subprocess_exec' takes
     multiple string arguments.

     The `protocol_factory' must be a callable returning a subclass of
     the *note asyncio.SubprocessProtocol: 25d0. class.

     Other parameters:

        * `stdin' can be any of these:

             * a file-like object representing a pipe to be connected to
               the subprocess’s standard input stream using *note
               connect_write_pipe(): 2563.

             * the *note subprocess.PIPE: 3f3. constant (default) which
               will create a new pipe and connect it,

             * the value ‘None’ which will make the subprocess inherit
               the file descriptor from this process

             * the *note subprocess.DEVNULL: aa5. constant which
               indicates that the special *note os.devnull: 101f. file
               will be used

        * `stdout' can be any of these:

             * a file-like object representing a pipe to be connected to
               the subprocess’s standard output stream using *note
               connect_write_pipe(): 2563.

             * the *note subprocess.PIPE: 3f3. constant (default) which
               will create a new pipe and connect it,

             * the value ‘None’ which will make the subprocess inherit
               the file descriptor from this process

             * the *note subprocess.DEVNULL: aa5. constant which
               indicates that the special *note os.devnull: 101f. file
               will be used

        * `stderr' can be any of these:

             * a file-like object representing a pipe to be connected to
               the subprocess’s standard error stream using *note
               connect_write_pipe(): 2563.

             * the *note subprocess.PIPE: 3f3. constant (default) which
               will create a new pipe and connect it,

             * the value ‘None’ which will make the subprocess inherit
               the file descriptor from this process

             * the *note subprocess.DEVNULL: aa5. constant which
               indicates that the special *note os.devnull: 101f. file
               will be used

             * the *note subprocess.STDOUT: 245f. constant which will
               connect the standard error stream to the process’
               standard output stream

        * All other keyword arguments are passed to *note
          subprocess.Popen: 2ba. without interpretation, except for
          `bufsize', `universal_newlines', `shell', `text', `encoding'
          and `errors', which should not be specified at all.

          The ‘asyncio’ subprocess API does not support decoding the
          streams as text.  *note bytes.decode(): c3d. can be used to
          convert the bytes returned from the stream to text.

     See the constructor of the *note subprocess.Popen: 2ba. class for
     documentation on other arguments.

     Returns a pair of ‘(transport, protocol)’, where `transport'
     conforms to the *note asyncio.SubprocessTransport: 25d1. base class
     and `protocol' is an object instantiated by the `protocol_factory'.

 -- 成員函式: coroutine loop.subprocess_shell (protocol_factory, cmd, *,
          stdin=subprocess.PIPE, stdout=subprocess.PIPE,
          stderr=subprocess.PIPE, **kwargs)

     Create a subprocess from `cmd', which can be a *note str: 335. or a
     *note bytes: 336. string encoded to the *note filesystem encoding:
     1ee7, using the platform’s "shell" syntax.

     This is similar to the standard library *note subprocess.Popen:
     2ba. class called with ‘shell=True’.

     The `protocol_factory' must be a callable returning a subclass of
     the *note SubprocessProtocol: 25d0. class.

     See *note subprocess_exec(): 24f2. for more details about the
     remaining arguments.

     Returns a pair of ‘(transport, protocol)’, where `transport'
     conforms to the *note SubprocessTransport: 25d1. base class and
     `protocol' is an object instantiated by the `protocol_factory'.

     備註: 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(): a78.
     function can be used to properly escape whitespace and special
     characters in strings that are going to be used to construct shell
     commands.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Shell_injection#Shell_injection


File: python.info,  Node: Callback Handles,  Next: Server Objects,  Prev: Event Loop Methods,  Up: Event Loop

5.18.1.61 Callback Handles
..........................

 -- 類別: asyncio.Handle

     A callback wrapper object returned by *note loop.call_soon(): 34e,
     *note loop.call_soon_threadsafe(): 34f.

      -- 成員函式: cancel ()

          Cancel the callback.  If the callback has already been
          canceled or executed, this method has no effect.

      -- 成員函式: cancelled ()

          Return ‘True’ if the callback was cancelled.

          3.7 版新加入.

 -- 類別: asyncio.TimerHandle

     A callback wrapper object returned by *note loop.call_later(): 350,
     and *note loop.call_at(): 351.

     This class is a subclass of *note Handle: 10a7.

      -- 成員函式: when ()

          Return a scheduled callback time as *note float: 188. seconds.

          The time is an absolute timestamp, using the same time
          reference as *note loop.time(): 25ab.

          3.7 版新加入.


File: python.info,  Node: Server Objects,  Next: Event Loop Implementations,  Prev: Callback Handles,  Up: Event Loop

5.18.1.62 Server Objects
........................

Server objects are created by *note loop.create_server(): 362, *note
loop.create_unix_server(): 363, *note start_server(): 369, and *note
start_unix_server(): 2525. functions.

Do not instantiate the class directly.

 -- 類別: asyncio.Server

     `Server' objects are asynchronous context managers.  When used in
     an ‘async with’ statement, it’s guaranteed that the Server object
     is closed and not accepting new connections when the ‘async with’
     statement is completed:

          srv = await loop.create_server(...)

          async with srv:
              # some code

          # At this point, srv is closed and no longer accepts new connections.

     3.7 版更變: Server object is an asynchronous context manager since
     Python 3.7.

      -- 成員函式: close ()

          Stop serving: close listening sockets and set the *note
          sockets: 4a8. attribute to ‘None’.

          The sockets that represent existing incoming client
          connections are left open.

          The server is closed asynchronously, use the *note
          wait_closed(): 25d4. coroutine to wait until the server is
          closed.

      -- 成員函式: get_loop ()

          Return the event loop associated with the server object.

          3.7 版新加入.

      -- 成員函式: coroutine start_serving ()

          Start accepting connections.

          This method is idempotent, so it can be called when the server
          is already being serving.

          The `start_serving' keyword-only parameter to *note
          loop.create_server(): 362. and *note asyncio.start_server():
          369. allows creating a Server object that is not accepting
          connections initially.  In this case ‘Server.start_serving()’,
          or *note Server.serve_forever(): 365. can be used to make the
          Server start accepting connections.

          3.7 版新加入.

      -- 成員函式: coroutine serve_forever ()

          Start accepting connections until the coroutine is cancelled.
          Cancellation of ‘serve_forever’ task causes the server to be
          closed.

          This method can be called if the server is already accepting
          connections.  Only one ‘serve_forever’ task can exist per one
          `Server' object.

          Example:

               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 ()

          Return ‘True’ if the server is accepting new connections.

          3.7 版新加入.

      -- 成員函式: coroutine wait_closed ()

          Wait until the *note close(): 25d3. method completes.

      -- 屬性: sockets

          List of *note socket.socket: 679. objects the server is
          listening on.

          3.7 版更變: Prior to Python 3.7 ‘Server.sockets’ used to
          return an internal list of server sockets directly.  In 3.7 a
          copy of that list is returned.


File: python.info,  Node: Event Loop Implementations,  Next: Examples<14>,  Prev: Server Objects,  Up: Event Loop

5.18.1.63 Event Loop Implementations
....................................

asyncio ships with two different event loop implementations: *note
SelectorEventLoop: 2578. and *note ProactorEventLoop: 1ac.

By default asyncio is configured to use *note SelectorEventLoop: 2578.
on Unix and *note ProactorEventLoop: 1ac. on Windows.

 -- 類別: asyncio.SelectorEventLoop

     An event loop based on the *note selectors: e7. module.

     Uses the most efficient `selector' available for the given
     platform.  It is also possible to manually configure the exact
     selector implementation to be used:

          import asyncio
          import selectors

          selector = selectors.SelectSelector()
          loop = asyncio.SelectorEventLoop(selector)
          asyncio.set_event_loop(loop)

     *note Availability: 1364.: Unix, Windows.

 -- 類別: asyncio.ProactorEventLoop

     An event loop for Windows that uses "I/O Completion Ports" (IOCP).

     *note Availability: 1364.: Windows.

     也參考
     ......

     MSDN documentation on I/O Completion Ports(1).

 -- 類別: asyncio.AbstractEventLoop

     Abstract base class for asyncio-compliant event loops.

     The *note Event Loop Methods: 649. section lists all methods that
     an alternative implementation of ‘AbstractEventLoop’ should have
     defined.

   ---------- Footnotes ----------

   (1) 
https://docs.microsoft.com/en-ca/windows/desktop/FileIO/i-o-completion-ports


File: python.info,  Node: Examples<14>,  Prev: Event Loop Implementations,  Up: Event Loop

5.18.1.64 Examples
..................

Note that all examples in this section `purposefully' show how to use
the low-level event loop APIs, such as *note loop.run_forever(): 25a3.
and *note loop.call_soon(): 34e.  Modern asyncio applications rarely
need to be written this way; consider using the high-level functions
like *note asyncio.run(): 1a6.

* Menu:

* Hello World with call_soon(): Hello World with call_soon.
* Display the current date with call_later(): Display the current date with call_later.
* Watch a file descriptor for read events::
* Set signal handlers for SIGINT and SIGTERM::


File: python.info,  Node: Hello World with call_soon,  Next: Display the current date with call_later,  Up: Examples<14>

5.18.1.65 Hello World with call_soon()
......................................

An example using the *note loop.call_soon(): 34e. method to schedule a
callback.  The callback displays ‘"Hello World"’ and then stops the
event loop:

     import asyncio

     def hello_world(loop):
         """A callback to print 'Hello World' and stop the event loop"""
         print('Hello World')
         loop.stop()

     loop = asyncio.get_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()

也參考
......

A similar *note Hello World: 24ed. example created with a coroutine and
the *note run(): 1a6. function.


File: python.info,  Node: Display the current date with call_later,  Next: Watch a file descriptor for read events,  Prev: Hello World with call_soon,  Up: Examples<14>

5.18.1.66 Display the current date with call_later()
....................................................

An example of a callback displaying the current date every second.  The
callback uses the *note loop.call_later(): 350. method to reschedule
itself after 5 seconds, and then stops the event loop:

     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.get_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()

也參考
......

A similar *note current date: 2500. example created with a coroutine and
the *note run(): 1a6. function.


File: python.info,  Node: Watch a file descriptor for read events,  Next: Set signal handlers for SIGINT and SIGTERM,  Prev: Display the current date with call_later,  Up: Examples<14>

5.18.1.67 Watch a file descriptor for read events
.................................................

Wait until a file descriptor received some data using the *note
loop.add_reader(): 2540. method and then close the event loop:

     import asyncio
     from socket import socketpair

     # Create a pair of connected file descriptors
     rsock, wsock = socketpair()

     loop = asyncio.get_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()

也參考
......

   * A similar *note example: 253e. using transports, protocols, and the
     *note loop.create_connection(): 1b3. method.

   * Another similar *note example: 253c. using the high-level *note
     asyncio.open_connection(): 368. function and streams.


File: python.info,  Node: Set signal handlers for SIGINT and SIGTERM,  Prev: Watch a file descriptor for read events,  Up: Examples<14>

5.18.1.68 Set signal handlers for SIGINT and SIGTERM
....................................................

(This ‘signals’ example only works on Unix.)

Register handlers for signals ‘SIGINT’ and ‘SIGTERM’ using the *note
loop.add_signal_handler(): 24f3. method:

     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: Transports and Protocols,  Prev: Event Loop,  Up: asyncio --- Asynchronous I/O

5.18.1.69 Futures
.................

`Source code:' Lib/asyncio/futures.py(1), Lib/asyncio/base_futures.py(2)

__________________________________________________________________

`Future' objects are used to bridge `low-level callback-based code' with
high-level async/await code.

* Menu:

* Future Functions::
* Future Object::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/asyncio/futures.py

   (2) 
https://github.com/python/cpython/tree/3.8/Lib/asyncio/base_futures.py


File: python.info,  Node: Future Functions,  Next: Future Object,  Up: Futures

5.18.1.70 Future Functions
..........................

 -- 函式: asyncio.isfuture (obj)

     Return ‘True’ if `obj' is either of:

        * an instance of *note asyncio.Future: 448,

        * an instance of *note asyncio.Task: 1ae,

        * a Future-like object with a ‘_asyncio_future_blocking’
          attribute.

     3.5 版新加入.

 -- 函式: asyncio.ensure_future (obj, *, loop=None)

     Return:

        * `obj' argument as is, if `obj' is a *note Future: 448, a *note
          Task: 1ae, or a Future-like object (*note isfuture(): 25e1. is
          used for the test.)

        * a *note Task: 1ae. object wrapping `obj', if `obj' is a
          coroutine (*note iscoroutine(): 251d. is used for the test);
          in this case the coroutine will be scheduled by
          ‘ensure_future()’.

        * a *note Task: 1ae. object that would await on `obj', if `obj'
          is an awaitable (*note inspect.isawaitable(): 6fe. is used for
          the test.)

     If `obj' is neither of the above a *note TypeError: 193. is raised.

          重要: See also the *note create_task(): 1af. function which is
          the preferred way for creating new Tasks.

     3.5.1 版更變: The function accepts any *note awaitable: 51e.
     object.

 -- 函式: asyncio.wrap_future (future, *, loop=None)

     Wrap a *note concurrent.futures.Future: b32. object in a *note
     asyncio.Future: 448. object.


File: python.info,  Node: Future Object,  Prev: Future Functions,  Up: Futures

5.18.1.71 Future Object
.......................

 -- 類別: asyncio.Future (*, loop=None)

     A Future represents an eventual result of an asynchronous
     operation.  Not thread-safe.

     Future is an *note awaitable: 51e. object.  Coroutines can await on
     Future objects until they either have a result or an exception set,
     or until they are cancelled.

     Typically Futures are used to enable low-level callback-based code
     (e.g.  in protocols implemented using asyncio *note transports:
     24f4.) to interoperate with high-level async/await code.

     The rule of thumb is to never expose Future objects in user-facing
     APIs, and the recommended way to create a Future object is to call
     *note loop.create_future(): 521.  This way alternative event loop
     implementations can inject their own optimized implementations of a
     Future object.

     3.7 版更變: Added support for the *note contextvars: 25. module.

      -- 成員函式: result ()

          Return the result of the Future.

          If the Future is `done' and has a result set by the *note
          set_result(): 250f. method, the result value is returned.

          If the Future is `done' and has an exception set by the *note
          set_exception(): 2510. method, this method raises the
          exception.

          If the Future has been `cancelled', this method raises a *note
          CancelledError: 1a8. exception.

          If the Future’s result isn’t yet available, this method raises
          a *note InvalidStateError: 2515. exception.

      -- 成員函式: set_result (result)

          Mark the Future as `done' and set its result.

          Raises a *note InvalidStateError: 2515. error if the Future is
          already `done'.

      -- 成員函式: set_exception (exception)

          Mark the Future as `done' and set an exception.

          Raises a *note InvalidStateError: 2515. error if the Future is
          already `done'.

      -- 成員函式: done ()

          Return ‘True’ if the Future is `done'.

          A Future is `done' if it was `cancelled' or if it has a result
          or an exception set with *note set_result(): 250f. or *note
          set_exception(): 2510. calls.

      -- 成員函式: cancelled ()

          Return ‘True’ if the Future was `cancelled'.

          The method is usually used to check if a Future is not
          `cancelled' before setting a result or an exception for it:

               if not fut.cancelled():
                   fut.set_result(42)

      -- 成員函式: add_done_callback (callback, *, context=None)

          Add a callback to be run when the Future is `done'.

          The `callback' is called with the Future object as its only
          argument.

          If the Future is already `done' when this method is called,
          the callback is scheduled with *note loop.call_soon(): 34e.

          An optional keyword-only `context' argument allows specifying
          a custom *note contextvars.Context: 24c1. for the `callback'
          to run in.  The current context is used when no `context' is
          provided.

          *note functools.partial(): 7cd. can be used to pass parameters
          to the callback, e.g.:

               # Call 'print("Future:", fut)' when "fut" is done.
               fut.add_done_callback(
                   functools.partial(print, "Future:"))

          3.7 版更變: The `context' keyword-only parameter was added.
          See PEP 567(1) for more details.

      -- 成員函式: remove_done_callback (callback)

          Remove `callback' from the callbacks list.

          Returns the number of callbacks removed, which is typically 1,
          unless a callback was added more than once.

      -- 成員函式: cancel ()

          Cancel the Future and schedule callbacks.

          If the Future is already `done' or `cancelled', return
          ‘False’.  Otherwise, change the Future’s state to `cancelled',
          schedule the callbacks, and return ‘True’.

      -- 成員函式: exception ()

          Return the exception that was set on this Future.

          The exception (or ‘None’ if no exception was set) is returned
          only if the Future is `done'.

          If the Future has been `cancelled', this method raises a *note
          CancelledError: 1a8. exception.

          If the Future isn’t `done' yet, this method raises an *note
          InvalidStateError: 2515. exception.

      -- 成員函式: get_loop ()

          Return the event loop the Future object is bound to.

          3.7 版新加入.

This example creates a Future object, creates and schedules an
asynchronous Task to set result for the Future, and waits until the
Future has a result:

     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())

     重要: The Future object was designed to mimic *note
     concurrent.futures.Future: b32.  Key differences include:

        - unlike asyncio Futures, *note concurrent.futures.Future: b32.
          instances cannot be awaited.

        - *note asyncio.Future.result(): 25e4. and *note
          asyncio.Future.exception(): 25e7. do not accept the `timeout'
          argument.

        - *note asyncio.Future.result(): 25e4. and *note
          asyncio.Future.exception(): 25e7. raise an *note
          InvalidStateError: 2515. exception when the Future is not
          `done'.

        - Callbacks registered with *note
          asyncio.Future.add_done_callback(): 352. are not called
          immediately.  They are scheduled with *note loop.call_soon():
          34e. instead.

        - asyncio Future is not compatible with the *note
          concurrent.futures.wait(): 244c. and *note
          concurrent.futures.as_completed(): 10f3. functions.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0567


File: python.info,  Node: Transports and Protocols,  Next: Policies,  Prev: Futures,  Up: asyncio --- Asynchronous I/O

5.18.1.72 Transports and Protocols
..................................

Preface
.......

Transports and Protocols are used by the `low-level' event loop APIs
such as *note loop.create_connection(): 1b3.  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: 25eb. and *note
Protocols: 25ec.

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(): 1b3.) 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)’.

Contents
........

This documentation page contains the following sections:

   * The *note Transports: 25eb. section documents asyncio *note
     BaseTransport: 25ed, *note ReadTransport: 25c5, *note
     WriteTransport: 25c6, *note Transport: 25ee, *note
     DatagramTransport: 25ef, and *note SubprocessTransport: 25d1.
     classes.

   * The *note Protocols: 25ec. section documents asyncio *note
     BaseProtocol: 25f0, *note Protocol: 25f1, *note BufferedProtocol:
     2ca, *note DatagramProtocol: 25f2, and *note SubprocessProtocol:
     25d0. classes.

   * The *note Examples: 25f3. section showcases how to work with
     transports, protocols, and low-level event loop APIs.

* Menu:

* Transports::
* Protocols::
* Examples: Examples<15>.


File: python.info,  Node: Transports,  Next: Protocols,  Up: Transports and Protocols

5.18.1.73 Transports
....................

`Source code:' Lib/asyncio/transports.py(1)

__________________________________________________________________

Transports are classes provided by *note asyncio: a. in order to
abstract various kinds of communication channels.

Transport objects are always instantiated by an *note asyncio event
loop: 649.

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: 250b.

* Menu:

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

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/asyncio/transports.py


File: python.info,  Node: Transports Hierarchy,  Next: Base Transport,  Up: Transports

5.18.1.74 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(): 2563. event loop method and are also
     used by subprocess-related methods like *note
     loop.subprocess_exec(): 24f2.

 -- 類別: asyncio.ReadTransport (BaseTransport)

     A base transport for read-only connections.

     Instances of the `ReadTransport' class are returned from the *note
     loop.connect_read_pipe(): 2562. event loop method and are also used
     by subprocess-related methods like *note loop.subprocess_exec():
     24f2.

 -- 類別: 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(): 1b3, *note
     loop.create_unix_connection(): 2524, *note loop.create_server():
     362, *note loop.sendfile(): 25b9, etc.

 -- 類別: asyncio.DatagramTransport (BaseTransport)

     A transport for datagram (UDP) connections.

     Instances of the `DatagramTransport' class are returned from the
     *note loop.create_datagram_endpoint(): 2e8. 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(): 2560. and *note
     loop.subprocess_exec(): 24f2.


File: python.info,  Node: Base Transport,  Next: Read-only Transports,  Prev: Transports Hierarchy,  Up: Transports

5.18.1.75 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(): 25f7. method will be called with *note
     None: 158. as its argument.

 -- 成員函式: 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():
               25f8. (‘None’ on error)

             - ‘'socket'’: *note socket.socket: 679. instance

             - ‘'sockname'’: the socket’s own address, result of *note
               socket.socket.getsockname(): 25f9.

        * 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(): a9a.

             - ‘'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(): 25fa.

             - ‘'peercert'’: peer certificate; result of *note
               ssl.SSLSocket.getpeercert(): 8d6.

             - ‘'sslcontext'’: *note ssl.SSLContext: 3e9. instance

             - ‘'ssl_object'’: *note ssl.SSLObject: 3e8. or *note
               ssl.SSLSocket: 3e7. instance

        * pipe:

             - ‘'pipe'’: pipe object

        * subprocess:

             - ‘'subprocess'’: *note subprocess.Popen: 2ba. 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.76 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(): 25fe. method
     until *note resume_reading(): 36d. 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(): 25fe. 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.77 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():
     25f7. method will eventually be called with *note None: 158. as its
     argument.

 -- 成員函式: WriteTransport.can_write_eof ()

     Return *note True: 49e. if the transport supports *note
     write_eof(): 2602, *note False: 38d. 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(): 2604. 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(): 2605. and *note
     protocol.resume_writing(): 2606. 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(): 2605. is called when the buffer size becomes
     greater than or equal to the `high' value.  If writing has been
     paused, *note resume_writing(): 2606. 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(): 2605. to be called whenever the
     buffer becomes non-empty.  Setting `low' to zero causes *note
     resume_writing(): 2606. 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(): 6a1. 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(): 2607. 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: 613. 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.78 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: 158,
     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.

 -- 成員函式: 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():
     25f7. method will eventually be called with *note None: 158. as its
     argument.


File: python.info,  Node: Subprocess Transports,  Prev: Datagram Transports,  Up: Transports

5.18.1.79 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: 158. if the subprocess was not
          created with ‘stdin=PIPE’

        * ‘1’: writable streaming transport of the standard output
          (`stdout'), or *note None: 158. if the subprocess was not
          created with ‘stdout=PIPE’

        * ‘2’: writable streaming transport of the standard error
          (`stderr'), or *note None: 158. if the subprocess was not
          created with ‘stderr=PIPE’

        * other `fd': *note None: 158.

 -- 成員函式: SubprocessTransport.get_returncode ()

     Return the subprocess return code as an integer or *note None: 158.
     if it hasn’t returned, which is similar to the *note
     subprocess.Popen.returncode: 2480. 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(): 2611.

     See also *note subprocess.Popen.kill(): 2486.

 -- 成員函式: SubprocessTransport.send_signal (signal)

     Send the `signal' number to the subprocess, as in *note
     subprocess.Popen.send_signal(): 2484.

 -- 成員函式: SubprocessTransport.terminate ()

     Stop the subprocess.

     On POSIX systems, this method sends SIGTERM to the subprocess.  On
     Windows, the Windows API function TerminateProcess() is called to
     stop the subprocess.

     See also *note subprocess.Popen.terminate(): 2485.

 -- 成員函式: SubprocessTransport.close ()

     Kill the subprocess by calling the *note kill(): 2610. method.

     If the subprocess hasn’t returned yet, and close transports of
     `stdin', `stdout', and `stderr' pipes.


File: python.info,  Node: Protocols,  Next: Examples<15>,  Prev: Transports,  Up: Transports and Protocols

5.18.1.80 Protocols
...................

`Source code:' 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: 25b1.

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.8/Lib/asyncio/protocols.py


File: python.info,  Node: Base Protocols,  Next: Base Protocol,  Up: Protocols

5.18.1.81 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.82 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: 158.  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(): 2604.
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():
2605. is not called: the buffer size must go strictly over.

Conversely, *note resume_writing(): 2606. 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.83 Streaming Protocols
.............................

Event methods, such as *note loop.create_server(): 362, *note
loop.create_unix_server(): 363, *note loop.create_connection(): 1b3,
*note loop.create_unix_connection(): 2524, *note
loop.connect_accepted_socket(): 36a, *note loop.connect_read_pipe():
2562, and *note loop.connect_write_pipe(): 2563. 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(): 2617. 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(): 2602, 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.84 Buffered Streaming Protocols
......................................

3.7 版新加入: `Important:' this has been added to asyncio in Python 3.7
`on a provisional basis'!  This is as an experimental API that might be
changed or removed completely in Python 3.8.

Buffered Protocols can be used with any event loop method that supports
*note Streaming Protocols: 2616.

‘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: 2ca.
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: 15ec.

 -- 成員函式: 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(): 2617.
     method.

*note get_buffer(): 2619. can be called an arbitrary number of times
during a connection.  However, *note protocol.eof_received(): 2617. is
called at most once and, if called, *note get_buffer(): 2619. and *note
buffer_updated(): 261a. 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.85 Datagram Protocols
............................

Datagram Protocol instances should be constructed by protocol factories
passed to the *note loop.create_datagram_endpoint(): 2e8. 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: 1d4.  `exc' is the *note OSError: 1d4. 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: 1d4. with ‘errno’ set to *note errno.ENOBUFS:
     22a3. may or may not be raised; if it is raised, it will be
     reported to *note DatagramProtocol.error_received(): 261e. but
     otherwise ignored.


File: python.info,  Node: Subprocess Protocols,  Prev: Datagram Protocols,  Up: Protocols

5.18.1.86 Subprocess Protocols
..............................

Datagram Protocol instances should be constructed by protocol factories
passed to the *note loop.subprocess_exec(): 24f2. and *note
loop.subprocess_shell(): 2560. 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.


File: python.info,  Node: Examples<15>,  Prev: Protocols,  Up: Transports and Protocols

5.18.1.87 Examples
..................

* 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: Examples<15>

5.18.1.88 TCP Echo Server
.........................

Create a TCP echo server using the *note loop.create_server(): 362.
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(
             lambda: EchoServerProtocol(),
             '127.0.0.1', 8888)

         async with server:
             await server.serve_forever()


     asyncio.run(main())

也參考
......

The *note TCP echo server using streams: 2538. example uses the
high-level *note asyncio.start_server(): 369. function.


File: python.info,  Node: TCP Echo Client,  Next: UDP Echo Server,  Prev: TCP Echo Server,  Up: Examples<15>

5.18.1.89 TCP Echo Client
.........................

A TCP echo client using the *note loop.create_connection(): 1b3. 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: 2535. example uses the
high-level *note asyncio.open_connection(): 368. function.


File: python.info,  Node: UDP Echo Server,  Next: UDP Echo Client,  Prev: TCP Echo Client,  Up: Examples<15>

5.18.1.90 UDP Echo Server
.........................

A UDP echo server, using the *note loop.create_datagram_endpoint(): 2e8.
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(
             lambda: 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: Examples<15>

5.18.1.91 UDP Echo Client
.........................

A UDP echo client, using the *note loop.create_datagram_endpoint(): 2e8.
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: Examples<15>

5.18.1.92 Connecting Existing Sockets
.....................................

Wait until a socket receives data using the *note
loop.create_connection(): 1b3. 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: 253f. example uses
the low-level *note loop.add_reader(): 2540. method to register an FD.

The *note register an open socket to wait for data using streams: 253c.
example uses high-level streams created by the *note open_connection():
368. function in a coroutine.


File: python.info,  Node: loop subprocess_exec and SubprocessProtocol,  Prev: Connecting Existing Sockets,  Up: Examples<15>

5.18.1.93 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(): 24f2.
method:

     import asyncio
     import sys

     class DateProtocol(asyncio.SubprocessProtocol):
         def __init__(self, exit_future):
             self.exit_future = exit_future
             self.output = bytearray()

         def pipe_data_received(self, fd, data):
             self.output.extend(data)

         def process_exited(self):
             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: 257b. written using high-level APIs.


File: python.info,  Node: Policies,  Next: Platform Support,  Prev: Transports and Protocols,  Up: asyncio --- Asynchronous I/O

5.18.1.94 Policies
..................

An event loop policy is a global per-process object that controls the
management of the event loop.  Each event loop has a default policy,
which can be changed and customized using the policy API.

A policy defines the notion of `context' and manages a separate event
loop per context.  The default policy defines `context' to be the
current thread.

By using a custom event loop policy, the behavior of *note
get_event_loop(): 35a, *note set_event_loop(): 2599, and *note
new_event_loop(): 259a. functions can be customized.

Policy objects should implement the APIs defined in the *note
AbstractEventLoopPolicy: 262b. 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.95 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.96 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: 25d6. 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: 2634. interface.

          This function is Unix specific.

      -- 成員函式: set_child_watcher (watcher)

          Set the current child process watcher to `watcher'.

          This function is Unix specific.

asyncio ships with the following built-in policies:

 -- 類別: asyncio.DefaultEventLoopPolicy

     The default asyncio policy.  Uses *note SelectorEventLoop: 2578. on
     Unix and *note ProactorEventLoop: 1ac. 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: 1ac. is now used
     by default.

 -- 類別: asyncio.WindowsSelectorEventLoopPolicy

     An alternative event loop policy that uses the *note
     SelectorEventLoop: 2578. event loop implementation.

     *note Availability: 1364.: Windows.

 -- 類別: asyncio.WindowsProactorEventLoopPolicy

     An alternative event loop policy that uses the *note
     ProactorEventLoop: 1ac. event loop implementation.

     *note Availability: 1364.: Windows.


File: python.info,  Node: Process Watchers,  Next: Custom Policies,  Prev: Policy Objects,  Up: Policies

5.18.1.97 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(): 292. and *note loop.subprocess_exec(): 24f2.
functions.

asyncio defines the *note AbstractChildWatcher: 2634. abstract base
class, which child watchers should implement, and has four different
implementations: *note ThreadedChildWatcher: 257a. (configured to be
used by default), *note MultiLoopChildWatcher: 263a, *note
SafeChildWatcher: 263b, and *note FastChildWatcher: 263c.

See also the *note Subprocess and Threads: 2570. 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.

 -- 函式: 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: 2634. base class.

     備註: Third-party event loops implementations might not support
     custom child watchers.  For such event loops, using *note
     set_child_watcher(): 263e. 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: 2bb.

          3.8 版新加入.

      -- 成員函式: close ()

          Close the watcher.

          This method has to be called to ensure that underlying
          resources are cleaned-up.

 -- 類別: 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 版新加入.

 -- 類別: 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:
     2bb. 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: 263a. and
     has the same `O(N)' complexity but requires a running event loop in
     the main thread to work.

 -- 類別: 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: 263b.


File: python.info,  Node: Custom Policies,  Prev: Process Watchers,  Up: Policies

5.18.1.98 Custom Policies
.........................

To implement a new event loop policy, it is recommended to subclass
*note DefaultEventLoopPolicy: 2636. 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: Platform Support,  Next: High-level API Index,  Prev: Policies,  Up: asyncio --- Asynchronous I/O

5.18.1.99 Platform Support
..........................

The *note asyncio: a. module is designed to be portable, but some
platforms have subtle differences and limitations due to the platforms’
underlying architecture and capabilities.

* Menu:

* All Platforms::
* Windows: Windows<52>.
* macOS: macOS<25>.


File: python.info,  Node: All Platforms,  Next: Windows<52>,  Up: Platform Support

5.18.1.100 All Platforms
........................

   * *note loop.add_reader(): 2540. and *note loop.add_writer(): 25bd.
     cannot be used to monitor file I/O.


File: python.info,  Node: Windows<52>,  Next: macOS<25>,  Prev: All Platforms,  Up: Platform Support

5.18.1.101 Windows
..................

`Source code:' Lib/asyncio/proactor_events.py(1),
Lib/asyncio/windows_events.py(2), Lib/asyncio/windows_utils.py(3)

__________________________________________________________________

3.8 版更變: On Windows, *note ProactorEventLoop: 1ac. is now the default
event loop.

All event loops on Windows do not support the following methods:

   * *note loop.create_unix_connection(): 2524. and *note
     loop.create_unix_server(): 363. are not supported.  The *note
     socket.AF_UNIX: 25b4. socket family is specific to Unix.

   * *note loop.add_signal_handler(): 24f3. and *note
     loop.remove_signal_handler(): 25c8. are not supported.

*note SelectorEventLoop: 2578. has the following limitations:

   * *note SelectSelector: 2649. is used to wait on socket events: it
     supports sockets and is limited to 512 sockets.

   * *note loop.add_reader(): 2540. and *note loop.add_writer(): 25bd.
     only accept socket handles (e.g.  pipe file descriptors are not
     supported).

   * Pipes are not supported, so the *note loop.connect_read_pipe():
     2562. and *note loop.connect_write_pipe(): 2563. methods are not
     implemented.

   * *note Subprocesses: 24ef. are not supported, i.e.  *note
     loop.subprocess_exec(): 24f2. and *note loop.subprocess_shell():
     2560. methods are not implemented.

*note ProactorEventLoop: 1ac. has the following limitations:

   * The *note loop.add_reader(): 2540. and *note loop.add_writer():
     25bd. methods are not supported.

The resolution of the monotonic clock on Windows is usually around 15.6
msec.  The best resolution is 0.5 msec.  The resolution depends on the
hardware (availability of HPET(4)) and on the Windows configuration.

* Menu:

* Subprocess Support on Windows::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/asyncio/proactor_events.py

   (2) 
https://github.com/python/cpython/tree/3.8/Lib/asyncio/windows_events.py

   (3) 
https://github.com/python/cpython/tree/3.8/Lib/asyncio/windows_utils.py

   (4) https://en.wikipedia.org/wiki/High_Precision_Event_Timer


File: python.info,  Node: Subprocess Support on Windows,  Up: Windows<52>

5.18.1.102 Subprocess Support on Windows
........................................

On Windows, the default event loop *note ProactorEventLoop: 1ac.
supports subprocesses, whereas *note SelectorEventLoop: 2578. does not.

The *note policy.set_child_watcher(): 2635. function is also not
supported, as *note ProactorEventLoop: 1ac. has a different mechanism to
watch child processes.


File: python.info,  Node: macOS<25>,  Prev: Windows<52>,  Up: Platform Support

5.18.1.103 macOS
................

Modern macOS versions are fully supported.

macOS <= 10.8
.............

On macOS 10.6, 10.7 and 10.8, the default event loop uses *note
selectors.KqueueSelector: 264c, which does not support character devices
on these versions.  The *note SelectorEventLoop: 2578. can be manually
configured to use *note SelectSelector: 2649. or *note PollSelector:
452. to support character devices on these older versions of macOS.
Example:

     import asyncio
     import selectors

     selector = selectors.SelectSelector()
     loop = asyncio.SelectorEventLoop(selector)
     asyncio.set_event_loop(loop)


File: python.info,  Node: High-level API Index,  Next: Low-level API Index,  Prev: Platform Support,  Up: asyncio --- Asynchronous I/O

5.18.1.104 High-level API Index
...............................

This page lists all high-level async/await enabled asyncio APIs.

* Menu:

* Tasks::
* Queues: Queues<2>.
* Subprocesses: Subprocesses<2>.
* Streams: Streams<2>.
* Synchronization::
* Exceptions: Exceptions<9>.


File: python.info,  Node: Tasks,  Next: Queues<2>,  Up: High-level API Index

5.18.1.105 Tasks
................

Utilities to run asyncio programs, create Tasks, and await on multiple
things with timeouts.

*note run(): 1a6.                                      Create event loop, run a coroutine, close the loop.
                                                       
                                                       
*note create_task(): 1af.                              Start an asyncio Task.
                                                       
                                                       
‘await’ *note sleep(): 286.                            Sleep for a number of seconds.
                                                       
                                                       
‘await’ *note gather(): 287.                           Schedule and wait for things concurrently.
                                                       
                                                       
‘await’ *note wait_for(): 289.                         Run with a timeout.
                                                       
                                                       
‘await’ *note shield(): 288.                           Shield from cancellation.
                                                       
                                                       
‘await’ *note wait(): 28a.                             Monitor for completion.
                                                       
                                                       
*note current_task(): 355.                             Return the current Task.
                                                       
                                                       
*note all_tasks(): 356.                                Return all tasks for an event loop.
                                                       
                                                       
*note Task: 1ae.                                       Task object.
                                                       
                                                       
*note run_coroutine_threadsafe(): 51f.                 Schedule a coroutine from another OS thread.
                                                       
                                                       
‘for in’ *note as_completed(): 28b.                    Monitor for completion with a ‘for’ loop.
                                                       

Examples
........

   * *note Using asyncio.gather() to run things in parallel: 2502.

   * *note Using asyncio.wait_for() to enforce a timeout: 2507.

   * *note Cancellation: 2512.

   * *note Using asyncio.sleep(): 2500.

   * See also the main *note Tasks documentation page: 24ed.


File: python.info,  Node: Queues<2>,  Next: Subprocesses<2>,  Prev: Tasks,  Up: High-level API Index

5.18.1.106 Queues
.................

Queues should be used to distribute work amongst multiple asyncio Tasks,
implement connection pools, and pub/sub patterns.

*note Queue: 291.                                      A FIFO queue.
                                                       
                                                       
*note PriorityQueue: 258c.                             A priority queue.
                                                       
                                                       
*note LifoQueue: 258e.                                 A LIFO queue.
                                                       

Examples
........

   * *note Using asyncio.Queue to distribute workload between several
     Tasks: 2590.

   * See also the *note Queues documentation page: 24f0.


File: python.info,  Node: Subprocesses<2>,  Next: Streams<2>,  Prev: Queues<2>,  Up: High-level API Index

5.18.1.107 Subprocesses
.......................

Utilities to spawn subprocesses and run shell commands.

‘await’ *note create_subprocess_exec(): 292.           Create a subprocess.
                                                       
                                                       
‘await’ *note create_subprocess_shell(): 293.          Run a shell command.
                                                       

Examples
........

   * *note Executing a shell command: 255c.

   * See also the *note subprocess APIs: 24ef. documentation.


File: python.info,  Node: Streams<2>,  Next: Synchronization,  Prev: Subprocesses<2>,  Up: High-level API Index

5.18.1.108 Streams
..................

High-level APIs to work with network IO.

‘await’ *note open_connection(): 368.                  Establish a TCP connection.
                                                       
                                                       
‘await’ *note open_unix_connection(): 2523.            Establish a Unix socket connection.
                                                       
                                                       
‘await’ *note start_server(): 369.                     Start a TCP server.
                                                       
                                                       
‘await’ *note start_unix_server(): 2525.               Start a Unix socket server.
                                                       
                                                       
*note StreamReader: fcf.                               High-level async/await object to receive network
                                                       data.
                                                       
                                                       
*note StreamWriter: fd0.                               High-level async/await object to send network data.
                                                       

Examples
........

   * *note Example TCP client: 2521.

   * See also the *note streams APIs: 24ee. documentation.


File: python.info,  Node: Synchronization,  Next: Exceptions<9>,  Prev: Streams<2>,  Up: High-level API Index

5.18.1.109 Synchronization
..........................

Threading-like synchronization primitives that can be used in Tasks.

*note Lock: 28c.                                       A mutex lock.
                                                       
                                                       
*note Event: 28d.                                      An event object.
                                                       
                                                       
*note Condition: 28e.                                  A condition object.
                                                       
                                                       
*note Semaphore: 28f.                                  A semaphore.
                                                       
                                                       
*note BoundedSemaphore: 290.                           A bounded semaphore.
                                                       

Examples
........

   * *note Using asyncio.Event: 254b.

   * See also the documentation of asyncio *note synchronization
     primitives: 24f1.


File: python.info,  Node: Exceptions<9>,  Prev: Synchronization,  Up: High-level API Index

5.18.1.110 Exceptions
.....................

*note asyncio.TimeoutError: 2506.                      Raised on timeout by functions like
                                                       *note wait_for(): 289.  Keep in mind that
                                                       ‘asyncio.TimeoutError’ is `unrelated' to the
                                                       built-in *note TimeoutError: 9a1. exception.
                                                       
                                                       
*note asyncio.CancelledError: 1a8.                     Raised when a Task is cancelled.  See also
                                                       *note Task.cancel(): 2504.
                                                       

Examples
........

   * *note Handling CancelledError to run code on cancellation request:
     2512.

   * See also the full list of *note asyncio-specific exceptions: 2592.


File: python.info,  Node: Low-level API Index,  Next: Developing with asyncio,  Prev: High-level API Index,  Up: asyncio --- Asynchronous I/O

5.18.1.111 Low-level API Index
..............................

This page lists all low-level asyncio APIs.

* Menu:

* Obtaining the Event Loop::
* Event Loop Methods: Event Loop Methods<2>.
* Transports: Transports<2>.
* Protocols: Protocols<2>.
* Event Loop Policies::


File: python.info,  Node: Obtaining the Event Loop,  Next: Event Loop Methods<2>,  Up: Low-level API Index

5.18.1.112 Obtaining the Event Loop
...................................

*note asyncio.get_running_loop(): 359.                 The `preferred' function to get the running event
                                                       loop.
                                                       
                                                       
*note asyncio.get_event_loop(): 35a.                   Get an event loop instance (current or via the
                                                       policy).
                                                       
                                                       
*note asyncio.set_event_loop(): 2599.                  Set the event loop as current via the current
                                                       policy.
                                                       
                                                       
*note asyncio.new_event_loop(): 259a.                  Create a new event loop.
                                                       

Examples
........

   * *note Using asyncio.get_running_loop(): 25e8.


File: python.info,  Node: Event Loop Methods<2>,  Next: Transports<2>,  Prev: Obtaining the Event Loop,  Up: Low-level API Index

5.18.1.113 Event Loop Methods
.............................

See also the main documentation section about the *note event loop
methods: 649.

Lifecycle
.........

*note loop.run_until_complete(): 51d.                  Run a Future/Task/awaitable until complete.
                                                       
                                                       
*note loop.run_forever(): 25a3.                        Run the event loop forever.
                                                       
                                                       
*note loop.stop(): 525.                                Stop the event loop.
                                                       
                                                       
*note loop.close(): 25a5.                              Close the event loop.
                                                       
                                                       
*note loop.is_running(): 25a4.                         Return ‘True’ if the event loop is running.
                                                       
                                                       
*note loop.is_closed(): 6a0.                           Return ‘True’ if the event loop is closed.
                                                       
                                                       
‘await’ *note loop.shutdown_asyncgens(): 526.          Close asynchronous generators.
                                                       

Debugging
.........

*note loop.set_debug(): 69e.                           Enable or disable the debug mode.
                                                       
                                                       
*note loop.get_debug(): 69f.                           Get the current debug mode.
                                                       

Scheduling Callbacks
....................

*note loop.call_soon(): 34e.                           Invoke a callback soon.
                                                       
                                                       
*note loop.call_soon_threadsafe(): 34f.                A thread-safe variant of
                                                       *note loop.call_soon(): 34e.
                                                       
                                                       
*note loop.call_later(): 350.                          Invoke a callback `after' the given time.
                                                       
                                                       
*note loop.call_at(): 351.                             Invoke a callback `at' the given time.
                                                       

Thread/Process Pool
...................

‘await’ *note loop.run_in_executor(): 24fc.            Run a CPU-bound or other blocking function in a
                                                       *note concurrent.futures: 22. executor.
                                                       
                                                       
*note loop.set_default_executor(): 27c.                Set the default executor for
                                                       *note loop.run_in_executor(): 24fc.
                                                       

Tasks and Futures
.................

*note loop.create_future(): 521.                       Create a *note Future: 448. object.
                                                       
                                                       
*note loop.create_task(): 1b0.                         Schedule coroutine as a *note Task: 1ae.
                                                       
                                                       
*note loop.set_task_factory(): 6a2.                    Set a factory used by *note loop.create_task(): 1b0.
                                                       to create *note Tasks: 1ae.
                                                       
                                                       
*note loop.get_task_factory(): 6a3.                    Get the factory *note loop.create_task(): 1b0. uses
                                                       to create *note Tasks: 1ae.
                                                       

DNS
...

‘await’ *note loop.getaddrinfo(): 4a6.                 Asynchronous version of
                                                       *note socket.getaddrinfo(): 25c2.
                                                       
                                                       
‘await’ *note loop.getnameinfo(): 4a7.                 Asynchronous version of
                                                       *note socket.getnameinfo(): 25c3.
                                                       

Networking and IPC
..................

‘await’ *note loop.create_connection(): 1b3.           Open a TCP connection.
                                                       
                                                       
‘await’ *note loop.create_server(): 362.               Create a TCP server.
                                                       
                                                       
‘await’ *note loop.create_unix_connection(): 2524.     Open a Unix socket connection.
                                                       
                                                       
‘await’ *note loop.create_unix_server(): 363.          Create a Unix socket server.
                                                       
                                                       
‘await’ *note loop.connect_accepted_socket(): 36a.     Wrap a *note socket: 679. into a ‘(transport,
                                                       protocol)’ pair.
                                                       
                                                       
‘await’ *note loop.create_datagram_endpoint(): 2e8.    Open a datagram (UDP) connection.
                                                       
                                                       
‘await’ *note loop.sendfile(): 25b9.                   Send a file over a transport.
                                                       
                                                       
‘await’ *note loop.start_tls(): 353.                   Upgrade an existing connection to TLS.
                                                       
                                                       
‘await’ *note loop.connect_read_pipe(): 2562.          Wrap a read end of a pipe into a ‘(transport,
                                                       protocol)’ pair.
                                                       
                                                       
‘await’ *note loop.connect_write_pipe(): 2563.         Wrap a write end of a pipe into a ‘(transport,
                                                       protocol)’ pair.
                                                       

Sockets
.......

‘await’ *note loop.sock_recv(): 4a3.                   Receive data from the *note socket: 679.
                                                       
                                                       
‘await’ *note loop.sock_recv_into(): 354.              Receive data from the *note socket: 679. into a
                                                       buffer.
                                                       
                                                       
‘await’ *note loop.sock_sendall(): 4a4.                Send data to the *note socket: 679.
                                                       
                                                       
‘await’ *note loop.sock_connect(): 6a6.                Connect the *note socket: 679.
                                                       
                                                       
‘await’ *note loop.sock_accept(): 4a5.                 Accept a *note socket: 679. connection.
                                                       
                                                       
‘await’ *note loop.sock_sendfile(): 35d.               Send a file over the *note socket: 679.
                                                       
                                                       
*note loop.add_reader(): 2540.                         Start watching a file descriptor for read
                                                       availability.
                                                       
                                                       
*note loop.remove_reader(): 25bc.                      Stop watching a file descriptor for read
                                                       availability.
                                                       
                                                       
*note loop.add_writer(): 25bd.                         Start watching a file descriptor for write
                                                       availability.
                                                       
                                                       
*note loop.remove_writer(): 25be.                      Stop watching a file descriptor for write
                                                       availability.
                                                       

Unix Signals
............

*note loop.add_signal_handler(): 24f3.                 Add a handler for a *note signal: eb.
                                                       
                                                       
*note loop.remove_signal_handler(): 25c8.              Remove a handler for a *note signal: eb.
                                                       

Subprocesses
............

*note loop.subprocess_exec(): 24f2.                    Spawn a subprocess.
                                                       
                                                       
*note loop.subprocess_shell(): 2560.                   Spawn a subprocess from a shell command.
                                                       

Error Handling
..............

*note loop.call_exception_handler(): 25cc.             Call the exception handler.
                                                       
                                                       
*note loop.set_exception_handler(): 25cb.              Set a new exception handler.
                                                       
                                                       
*note loop.get_exception_handler(): 522.               Get the current exception handler.
                                                       
                                                       
*note loop.default_exception_handler(): 25cd.          The default exception handler implementation.
                                                       

Examples
........

   * *note Using asyncio.get_event_loop() and loop.run_forever(): 25d7.

   * *note Using loop.call_later(): 25d9.

   * Using ‘loop.create_connection()’ to implement *note an echo-client:
     2537.

   * Using ‘loop.create_connection()’ to *note connect a socket: 253e.

   * *note Using add_reader() to watch an FD for read events: 253f.

   * *note Using loop.add_signal_handler(): 25dc.

   * *note Using loop.subprocess_exec(): 257c.


File: python.info,  Node: Transports<2>,  Next: Protocols<2>,  Prev: Event Loop Methods<2>,  Up: Low-level API Index

5.18.1.114 Transports
.....................

All transports implement the following methods:

*note transport.close(): 25f6.                         Close the transport.
                                                       
                                                       
*note transport.is_closing(): 520.                     Return ‘True’ if the transport is closing or is
                                                       closed.
                                                       
                                                       
*note transport.get_extra_info(): 2c9.                 Request for information about the transport.
                                                       
                                                       
*note transport.set_protocol(): 25fb.                  Set a new protocol.
                                                       
                                                       
*note transport.get_protocol(): 25fc.                  Return the current protocol.
                                                       

Transports that can receive data (TCP and Unix connections, pipes, etc).
Returned from methods like *note loop.create_connection(): 1b3, *note
loop.create_unix_connection(): 2524, *note loop.connect_read_pipe():
2562, etc:

Read Transports
...............

*note transport.is_reading(): 36c.                     Return ‘True’ if the transport is receiving.
                                                       
                                                       
*note transport.pause_reading(): 36e.                  Pause receiving.
                                                       
                                                       
*note transport.resume_reading(): 36d.                 Resume receiving.
                                                       

Transports that can Send data (TCP and Unix connections, pipes, etc).
Returned from methods like *note loop.create_connection(): 1b3, *note
loop.create_unix_connection(): 2524, *note loop.connect_write_pipe():
2563, etc:

Write Transports
................

*note transport.write(): 2607.                         Write data to the transport.
                                                       
                                                       
*note transport.writelines(): 2608.                    Write buffers to the transport.
                                                       
                                                       
*note transport.can_write_eof(): 2601.                 Return *note True: 49e. if the transport supports
                                                       sending EOF.
                                                       
                                                       
*note transport.write_eof(): 2602.                     Close and send EOF after flushing buffered data.
                                                       
                                                       
*note transport.abort(): 2600.                         Close the transport immediately.
                                                       
                                                       
*note transport.get_write_buffer_size(): 2603.         Return high and low water marks for write flow
                                                       control.
                                                       
                                                       
*note transport.set_write_buffer_limits(): 2604.       Set new high and low water marks for write flow
                                                       control.
                                                       

Transports returned by *note loop.create_datagram_endpoint(): 2e8.:

Datagram Transports
...................

*note transport.sendto(): 260a.                        Send data to the remote peer.
                                                       
                                                       
*note transport.abort(): 260b.                         Close the transport immediately.
                                                       

Low-level transport abstraction over subprocesses.  Returned by *note
loop.subprocess_exec(): 24f2. and *note loop.subprocess_shell(): 2560.:

Subprocess Transports
.....................

*note transport.get_pid(): 260d.                       Return the subprocess process id.
                                                       
                                                       
*note transport.get_pipe_transport(): 260e.            Return the transport for the requested communication
                                                       pipe (`stdin', `stdout', or `stderr').
                                                       
                                                       
*note transport.get_returncode(): 260f.                Return the subprocess return code.
                                                       
                                                       
*note transport.kill(): 2610.                          Kill the subprocess.
                                                       
                                                       
*note transport.send_signal(): 2612.                   Send a signal to the subprocess.
                                                       
                                                       
*note transport.terminate(): 2611.                     Stop the subprocess.
                                                       
                                                       
*note transport.close(): 2613.                         Kill the subprocess and close all pipes.
                                                       


File: python.info,  Node: Protocols<2>,  Next: Event Loop Policies,  Prev: Transports<2>,  Up: Low-level API Index

5.18.1.115 Protocols
....................

Protocol classes can implement the following `callback methods':

‘callback’ *note connection_made(): 25b2.              Called when a connection is made.
                                                       
                                                       
‘callback’ *note connection_lost(): 25f7.              Called when the connection is lost or closed.
                                                       
                                                       
‘callback’ *note pause_writing(): 2605.                Called when the transport’s buffer goes over the
                                                       high water mark.
                                                       
                                                       
‘callback’ *note resume_writing(): 2606.               Called when the transport’s buffer drains below the
                                                       low water mark.
                                                       

Streaming Protocols (TCP, Unix Sockets, Pipes)
..............................................

‘callback’ *note data_received(): 25fe.                Called when some data is received.
                                                       
                                                       
‘callback’ *note eof_received(): 2617.                 Called when an EOF is received.
                                                       

Buffered Streaming Protocols
............................

‘callback’ *note get_buffer(): 2619.                   Called to allocate a new receive buffer.
                                                       
                                                       
‘callback’ *note buffer_updated(): 261a.               Called when the buffer was updated with the received
                                                       data.
                                                       
                                                       
‘callback’ *note eof_received(): 261b.                 Called when an EOF is received.
                                                       

Datagram Protocols
..................

‘callback’ *note datagram_received(): 261d.            Called when a datagram is received.
                                                       
                                                       
‘callback’ *note error_received(): 261e.               Called when a previous send or receive operation
                                                       raises an *note OSError: 1d4.
                                                       

Subprocess Protocols
....................

‘callback’ *note pipe_data_received(): 2620.           Called when the child process writes data into its
                                                       `stdout' or `stderr' pipe.
                                                       
                                                       
‘callback’ *note pipe_connection_lost(): 2621.         Called when one of the pipes communicating with the
                                                       child process is closed.
                                                       
                                                       
‘callback’ *note process_exited(): 2622.               Called when the child process has exited.
                                                       


File: python.info,  Node: Event Loop Policies,  Prev: Protocols<2>,  Up: Low-level API Index

5.18.1.116 Event Loop Policies
..............................

Policies is a low-level mechanism to alter the behavior of functions
like *note asyncio.get_event_loop(): 35a.  See also the main *note
policies section: 259b. for more details.

Accessing Policies
..................

*note asyncio.get_event_loop_policy(): 262d.           Return the current process-wide policy.
                                                       
                                                       
*note asyncio.set_event_loop_policy(): 262e.           Set a new process-wide policy.
                                                       
                                                       
*note AbstractEventLoopPolicy: 262b.                   Base class for policy objects.
                                                       


File: python.info,  Node: Developing with asyncio,  Prev: Low-level API Index,  Up: asyncio --- Asynchronous I/O

5.18.1.117 Developing with asyncio
..................................

Asynchronous programming is different from classic "sequential"
programming.

This page lists common mistakes and traps and explains how to avoid
them.

* Menu:

* Debug Mode::
* Concurrency and Multithreading::
* Running Blocking Code::
* Logging: Logging<3>.
* Detect never-awaited coroutines::
* Detect never-retrieved exceptions::


File: python.info,  Node: Debug Mode,  Next: Concurrency and Multithreading,  Up: Developing with asyncio

5.18.1.118 Debug Mode
.....................

By default asyncio runs in production mode.  In order to ease the
development asyncio has a `debug mode'.

There are several ways to enable asyncio debug mode:

   * Setting the *note PYTHONASYNCIODEBUG: 1361. environment variable to
     ‘1’.

   * Using the *note -X: 156. ‘dev’ Python command line option.

   * Passing ‘debug=True’ to *note asyncio.run(): 1a6.

   * Calling *note loop.set_debug(): 69e.

In addition to enabling the debug mode, consider also:

   * setting the log level of the *note asyncio logger: 2660. to
     ‘logging.DEBUG’, for example the following snippet of code can be
     run at startup of the application:

          logging.basicConfig(level=logging.DEBUG)

   * configuring the *note warnings: 127. module to display *note
     ResourceWarning: 4d5. warnings.  One way of doing that is by using
     the *note -W: 41c. ‘default’ command line option.

When the debug mode is enabled:

   * asyncio checks for *note coroutines that were not awaited: 2661.
     and logs them; this mitigates the "forgotten await" pitfall.

   * Many non-threadsafe asyncio APIs (such as *note loop.call_soon():
     34e. and *note loop.call_at(): 351. methods) raise an exception if
     they are called from a wrong thread.

   * The execution time of the I/O selector is logged if it takes too
     long to perform an I/O operation.

   * Callbacks taking longer than 100ms are logged.  The
     ‘loop.slow_callback_duration’ attribute can be used to set the
     minimum execution duration in seconds that is considered "slow".


File: python.info,  Node: Concurrency and Multithreading,  Next: Running Blocking Code,  Prev: Debug Mode,  Up: Developing with asyncio

5.18.1.119 Concurrency and Multithreading
.........................................

An event loop runs in a thread (typically the main thread) and executes
all callbacks and Tasks in its thread.  While a Task is running in the
event loop, no other Tasks can run in the same thread.  When a Task
executes an ‘await’ expression, the running Task gets suspended, and the
event loop executes the next Task.

To schedule a *note callback: 25a7. from another OS thread, the *note
loop.call_soon_threadsafe(): 34f. method should be used.  Example:

     loop.call_soon_threadsafe(callback, *args)

Almost all asyncio objects are not thread safe, which is typically not a
problem unless there is code that works with them from outside of a Task
or a callback.  If there’s a need for such code to call a low-level
asyncio API, the *note loop.call_soon_threadsafe(): 34f. method should
be used, e.g.:

     loop.call_soon_threadsafe(fut.cancel)

To schedule a coroutine object from a different OS thread, the *note
run_coroutine_threadsafe(): 51f. function should be used.  It returns a
*note concurrent.futures.Future: b32. to access the result:

     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()

To handle signals and to execute subprocesses, the event loop must be
run in the main thread.

The *note loop.run_in_executor(): 24fc. method can be used with a *note
concurrent.futures.ThreadPoolExecutor: 27b. to execute blocking code in
a different OS thread without blocking the OS thread that the event loop
runs in.

There is currently no way to schedule coroutines or callbacks directly
from a different process (such as one started with *note
multiprocessing: b8.).  The *note Event Loop Methods: 649. section lists
APIs that can read from pipes and watch file descriptors without
blocking the event loop.  In addition, asyncio’s *note Subprocess: 24ef.
APIs provide a way to start a process and communicate with it from the
event loop.  Lastly, the aforementioned *note loop.run_in_executor():
24fc. method can also be used with a *note
concurrent.futures.ProcessPoolExecutor: 2a5. to execute code in a
different process.


File: python.info,  Node: Running Blocking Code,  Next: Logging<3>,  Prev: Concurrency and Multithreading,  Up: Developing with asyncio

5.18.1.120 Running Blocking Code
................................

Blocking (CPU-bound) code should not be called directly.  For example,
if a function performs a CPU-intensive calculation for 1 second, all
concurrent asyncio Tasks and IO operations would be delayed by 1 second.

An executor can be used to run a task in a different thread or even in a
different process to avoid blocking the OS thread with the event loop.
See the *note loop.run_in_executor(): 24fc. method for more details.


File: python.info,  Node: Logging<3>,  Next: Detect never-awaited coroutines,  Prev: Running Blocking Code,  Up: Developing with asyncio

5.18.1.121 Logging
..................

asyncio uses the *note logging: ab. module and all logging is performed
via the ‘"asyncio"’ logger.

The default log level is ‘logging.INFO’, which can be easily adjusted:

     logging.getLogger("asyncio").setLevel(logging.WARNING)


File: python.info,  Node: Detect never-awaited coroutines,  Next: Detect never-retrieved exceptions,  Prev: Logging<3>,  Up: Developing with asyncio

5.18.1.122 Detect never-awaited coroutines
..........................................

When a coroutine function is called, but not awaited (e.g.  ‘coro()’
instead of ‘await coro()’) or the coroutine is not scheduled with *note
asyncio.create_task(): 1af, asyncio will emit a *note RuntimeWarning:
2c1.:

     import asyncio

     async def test():
         print("never scheduled")

     async def main():
         test()

     asyncio.run(main())

Output:

     test.py:7: RuntimeWarning: coroutine 'test' was never awaited
       test()

Output in debug mode:

     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()

The usual fix is to either await the coroutine or call the *note
asyncio.create_task(): 1af. function:

     async def main():
         await test()


File: python.info,  Node: Detect never-retrieved exceptions,  Prev: Detect never-awaited coroutines,  Up: Developing with asyncio

5.18.1.123 Detect never-retrieved exceptions
............................................

If a *note Future.set_exception(): 2510. is called but the Future object
is never awaited on, the exception would never be propagated to the user
code.  In this case, asyncio would emit a log message when the Future
object is garbage collected.

Example of an unhandled exception:

     import asyncio

     async def bug():
         raise Exception("not consumed")

     async def main():
         asyncio.create_task(bug())

     asyncio.run(main())

Output:

     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 Enable the debug mode: 1355. to get the traceback where the task
was created:

     asyncio.run(main(), debug=True)

Output in debug mode:

     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

     備註: The source code for asyncio can be found in Lib/asyncio/(1).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/asyncio/


File: python.info,  Node: socket --- Low-level networking interface,  Next: ssl --- TLS/SSL wrapper for socket objects,  Prev: asyncio --- Asynchronous I/O,  Up: Networking and Interprocess Communication

5.18.2 ‘socket’ — Low-level networking interface
------------------------------------------------

`Source code:' 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.

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(): 679. 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.

也參考
......

Module *note socketserver: f1.

     Classes that simplify writing network servers.

Module *note ssl: f4.

     A TLS/SSL wrapper for socket objects.

* Menu:

* Socket families::
* Module contents::
* Socket Objects::
* Notes on socket timeouts::
* Example: Example<8>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/socket.py


File: python.info,  Node: Socket families,  Next: Module contents,  Up: socket --- Low-level networking interface

5.18.2.1 Socket families
........................

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: 25b4. 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: 5ed. 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: 25b4. socket paths were
     assumed to use UTF-8 encoding.

     3.5 版更變: Writable *note bytes-like object: 5ed. is now accepted.

   - A pair ‘(host, port)’ is used for the *note AF_INET: 25ae. 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: 25af. address family, a four-tuple ‘(host,
     port, flowinfo, scopeid)’ is used, where `flowinfo' and `scopeid'
     represent the ‘sin6_flowinfo’ and ‘sin6_scope_id’ members in
     ‘struct sockaddr_in6’ in C. For *note socket: f0. module methods,
     `flowinfo' and `scopeid' can be omitted just for backward
     compatibility.  Note, however, omission of `scopeid' can cause
     problems in manipulating scoped IPv6 addresses.

     3.7 版更變: For multicast addresses (with `scopeid' meaningful)
     `address' may not contain ‘%scope’ (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: 266c. 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: 266d. 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).

   - 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 and DragonFlyBSD support added.

        - ‘BTPROTO_SCO’ accepts ‘bdaddr’ where ‘bdaddr’ is a *note
          bytes: 336. 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: 589. 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 Availability: 1364.: Linux 2.6.38, some algorithm types
     require more recent Kernels.

     3.6 版新加入.

   - *note AF_VSOCK: 3d8. 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 Availability: 1364.: Linux >= 4.8 QEMU >= 2.8 ESX >= 4.0 ESX
     Workstation >= 6.5.

     3.7 版新加入.

   - *note AF_PACKET: 266e. is a low-level interface directly to network
     devices.  The packets are represented by the tuple ‘(ifname,
     proto[, pkttype[, hatype[, addr]]])’ where:

        - `ifname' - String specifying the device name.

        - `proto' - An in network-byte-order integer specifying the
          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_MULTIHOST’ - 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 AF_QIPCRTR: 266f. 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.

     3.8 版新加入.

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; starting from Python
3.3, errors related to socket or address semantics raise *note OSError:
1d4. or one of its subclasses (they used to raise *note socket.error:
99a.).

Non-blocking mode is supported through *note setblocking(): 1f16.  A
generalization of this based on timeouts is supported through *note
settimeout(): 2670.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0383


File: python.info,  Node: Module contents,  Next: Socket Objects,  Prev: Socket families,  Up: socket --- Low-level networking interface

5.18.2.2 Module contents
........................

The module *note socket: f0. exports the following elements.

* Menu:

* Exceptions: Exceptions<10>.
* Constants: Constants<8>.
* Functions: Functions<5>.


File: python.info,  Node: Exceptions<10>,  Next: Constants<8>,  Up: Module contents

5.18.2.3 Exceptions
...................

 -- 例外: socket.error

     A deprecated alias of *note OSError: 1d4.

     3.3 版更變: Following PEP 3151(1), this class was made an alias of
     *note OSError: 1d4.

 -- 例外: socket.herror

     A subclass of *note OSError: 1d4, 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(): ea3. and *note
     gethostbyaddr(): ea2.  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: 1d4.

 -- 例外: socket.gaierror

     A subclass of *note OSError: 1d4, this exception is raised for
     address-related errors by *note getaddrinfo(): 25c2. and *note
     getnameinfo(): 25c3.  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: 1d4.

 -- 例外: socket.timeout

     A subclass of *note OSError: 1d4, this exception is raised when a
     timeout occurs on a socket which has had timeouts enabled via a
     prior call to *note settimeout(): 2670. (or implicitly through
     *note setdefaulttimeout(): 2675.).  The accompanying value is a
     string whose value is currently always "timed out".

     3.3 版更變: This class was made a subclass of *note OSError: 1d4.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3151


File: python.info,  Node: Constants<8>,  Next: Functions<5>,  Prev: Exceptions<10>,  Up: Module contents

5.18.2.4 Constants
..................

     The AF_* and SOCK_* constants are now ‘AddressFamily’ and
     ‘SocketKind’ *note IntEnum: 592. collections.

     3.4 版新加入.

 -- Data: socket.AF_UNIX
 -- Data: socket.AF_INET
 -- Data: socket.AF_INET6

     These constants represent the address (and protocol) families, used
     for the first argument to *note socket(): 679.  If the *note
     AF_UNIX: 25b4. constant is not defined then this protocol is
     unsupported.  More constants may be available depending on the
     system.

 -- Data: socket.SOCK_STREAM
 -- Data: socket.SOCK_DGRAM
 -- Data: socket.SOCK_RAW
 -- Data: socket.SOCK_RDM
 -- Data: socket.SOCK_SEQPACKET

     These constants represent the socket types, used for the second
     argument to *note socket(): 679.  More constants may be available
     depending on the system.  (Only *note SOCK_STREAM: c8f. and *note
     SOCK_DGRAM: c8e. appear to be generally useful.)

 -- Data: socket.SOCK_CLOEXEC
 -- Data: 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 Availability: 1364.: Linux >= 2.6.27.

     3.2 版新加入.

 -- Data: SO_*
 -- Data: socket.SOMAXCONN

 -- Data: MSG_*

 -- Data: SOL_*

 -- Data: SCM_*

 -- Data: IPPROTO_*

 -- Data: IPPORT_*

 -- Data: INADDR_*

 -- Data: IP_*

 -- Data: IPV6_*

 -- Data: EAI_*

 -- Data: AI_*

 -- Data: NI_*

 -- Data: 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 ‘setsockopt()’
     and ‘getsockopt()’ 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’ was added.

     On Windows, ‘TCP_KEEPIDLE’, ‘TCP_KEEPINTVL’ appear if run-time
     Windows supports.

 -- Data: socket.AF_CAN
 -- Data: socket.PF_CAN

 -- Data: SOL_CAN_*

 -- Data: CAN_*

     Many constants of these forms, documented in the Linux
     documentation, are also defined in the socket module.

     *note Availability: 1364.: Linux >= 2.6.25.

     3.3 版新加入.

 -- Data: socket.CAN_BCM

 -- Data: 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 Availability: 1364.: Linux >= 2.6.25.

          備註: The ‘CAN_BCM_CAN_FD_FRAME’ flag is only available on
          Linux >= 4.8.

     3.4 版新加入.

 -- Data: 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 Availability: 1364.: Linux >= 3.6.

     3.5 版新加入.

 -- Data: 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 Availability: 1364.: Linux >= 2.6.25.

     3.7 版新加入.

 -- Data: socket.AF_PACKET
 -- Data: socket.PF_PACKET

 -- Data: PACKET_*

     Many constants of these forms, documented in the Linux
     documentation, are also defined in the socket module.

     *note Availability: 1364.: Linux >= 2.2.

 -- Data: socket.AF_RDS
 -- Data: socket.PF_RDS
 -- Data: socket.SOL_RDS

 -- Data: RDS_*

     Many constants of these forms, documented in the Linux
     documentation, are also defined in the socket module.

     *note Availability: 1364.: Linux >= 2.6.30.

     3.3 版新加入.

 -- Data: socket.SIO_RCVALL
 -- Data: socket.SIO_KEEPALIVE_VALS
 -- Data: socket.SIO_LOOPBACK_FAST_PATH

 -- Data: RCVALL_*

     Constants for Windows’ WSAIoctl().  The constants are used as
     arguments to the *note ioctl(): 585. method of socket objects.

     3.6 版更變: ‘SIO_LOOPBACK_FAST_PATH’ was added.

 -- Data: TIPC_*

     TIPC related constants, matching the ones exported by the C socket
     API. See the TIPC documentation for more information.

 -- Data: socket.AF_ALG
 -- Data: socket.SOL_ALG

 -- Data: ALG_*

     Constants for Linux Kernel cryptography.

     *note Availability: 1364.: Linux >= 2.6.38.

     3.6 版新加入.

 -- Data: socket.AF_VSOCK
 -- Data: socket.IOCTL_VM_SOCKETS_GET_LOCAL_CID

 -- Data: VMADDR*

 -- Data: SO_VM*

     Constants for Linux host/guest communication.

     *note Availability: 1364.: Linux >= 4.8.

     3.7 版新加入.

 -- Data: socket.AF_LINK

     *note Availability: 1364.: BSD, OSX.

     3.4 版新加入.

 -- Data: socket.has_ipv6

     This constant contains a boolean value which indicates if IPv6 is
     supported on this platform.

 -- Data: socket.BDADDR_ANY
 -- Data: socket.BDADDR_LOCAL

     These are string constants containing Bluetooth addresses with
     special meanings.  For example, *note BDADDR_ANY: 2684. can be used
     to indicate any address when specifying the binding socket with
     ‘BTPROTO_RFCOMM’.

 -- Data: socket.HCI_FILTER
 -- Data: socket.HCI_TIME_STAMP
 -- Data: socket.HCI_DATA_DIR

     For use with ‘BTPROTO_HCI’.  *note HCI_FILTER: 2686. is not
     available for NetBSD or DragonFlyBSD. *note HCI_TIME_STAMP: 2687.
     and *note HCI_DATA_DIR: 2688. are not available for FreeBSD,
     NetBSD, or DragonFlyBSD.

 -- Data: socket.AF_QIPCRTR

     Constant for Qualcomm’s IPC router protocol, used to communicate
     with service providing remote processors.

     *note Availability: 1364.: Linux >= 4.7.

   ---------- Footnotes ----------

   (1) http://udrepper.livejournal.com/20407.html


File: python.info,  Node: Functions<5>,  Prev: Constants<8>,  Up: Module contents

5.18.2.5 Functions
..................

* Menu:

* Creating sockets::
* Other functions: Other functions<2>.


File: python.info,  Node: Creating sockets,  Next: Other functions<2>,  Up: Functions<5>

5.18.2.6 Creating sockets
.........................

The following functions all create *note socket objects: 268b.

 -- 函式: 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: 25ae.
     (the default), *note AF_INET6: 25af, *note AF_UNIX: 25b4, *note
     AF_CAN: 266c, *note AF_PACKET: 266e, or *note AF_RDS: 267c.  The
     socket type should be *note SOCK_STREAM: c8f. (the default), *note
     SOCK_DGRAM: c8e, *note SOCK_RAW: 2677. 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:
     266c. the protocol should be one of ‘CAN_RAW’, *note CAN_BCM: 8be.
     or *note CAN_ISOTP: 266d.

     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(): 25f8. but not the actual OS resource.  Unlike
     *note socket.fromfd(): 268c, `fileno' will return the same socket
     and not a duplicate.  This may help close a detached socket using
     *note socket.close(): 3d6.

     The newly created socket is *note non-inheritable: 7ff.

     Raises an *note auditing event: e96. ‘socket.__new__’ with
     arguments ‘self’, ‘family’, ‘type’, ‘protocol’.

     3.3 版更變: The AF_CAN family was added.  The AF_RDS family was
     added.

     3.4 版更變: The CAN_BCM protocol was added.

     3.4 版更變: The returned socket is now non-inheritable.

     3.7 版更變: The CAN_ISOTP protocol was added.

     3.7 版更變: When *note SOCK_NONBLOCK: 49b. or *note SOCK_CLOEXEC:
     49c. bit flags are applied to `type' they are cleared, and *note
     socket.type: 49d. 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’.

 -- 函式: 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(): 679.
     function above.  The default family is *note AF_UNIX: 25b4. if
     defined on the platform; otherwise, the default is *note AF_INET:
     25ae.

     The newly created sockets are *note non-inheritable: 7ff.

     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 support added.

 -- 函式: socket.create_connection (address[, timeout[,
          source_address]])

     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(): 67b.: if `host'
     is a non-numeric hostname, it will try to resolve it for both *note
     AF_INET: 25ae. and *note AF_INET6: 25af, 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(): 268d. 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.

     3.2 版更變: `source_address' was added.

 -- 函式: 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 return the socket object.

     `family' should be either *note AF_INET: 25ae. or *note AF_INET6:
     25af.  `backlog' is the queue size passed to *note socket.listen():
     750.; when ‘0’ 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: 1fc.  Most POSIX platforms and Windows are
     supposed to support this functionality.  When this functionality is
     enabled the address returned by *note socket.getpeername(): 25f8.
     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(): 220.:

          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 ‘fileno()’ method) and build a socket object from the
     result.  Address family, socket type and protocol number are as for
     the *note socket(): 679. 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: 7ff.

     3.4 版更變: The returned socket is now non-inheritable.

 -- 函式: socket.fromshare (data)

     Instantiate a socket from data obtained from the *note
     socket.share(): 499. method.  The socket is assumed to be in
     blocking mode.

     *note Availability: 1364.: Windows.

     3.3 版新加入.

 -- Data: 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: Other functions<2>,  Prev: Creating sockets,  Up: Functions<5>

5.18.2.7 Other functions
........................

The *note socket: f0. module also offers various network-related
services:

 -- 函式: socket.close (fd)

     Close a socket file descriptor.  This is like *note os.close():
     3d7, but for sockets.  On some platforms (most noticeable Windows)
     *note os.close(): 3d7. 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(): 679. 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: 25ae, a ‘(address,
     port, flow info, scope id)’ 4-tuple for *note AF_INET6: 25af.), and
     is meant to be passed to the *note socket.connect(): 67b. method.

     Raises an *note auditing event: e96. ‘socket.getaddrinfo’ with
     arguments ‘host’, ‘port’, ‘family’, ‘type’, ‘protocol’.

     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)
          [(<AddressFamily.AF_INET6: 10>, <SocketType.SOCK_STREAM: 1>,
           6, '', ('2606:2800:220:1:248:1893:25c8:1946', 80, 0, 0)),
           (<AddressFamily.AF_INET: 2>, <SocketType.SOCK_STREAM: 1>,
           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’ 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(): ea2. 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, the hostname
     as returned by *note gethostname(): 1f0a. 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(): ea3. for a more complete interface.  *note
     gethostbyname(): 2691. does not support IPv6 name resolution, and
     *note getaddrinfo(): 25c2. should be used instead for IPv4/v6 dual
     stack support.

     Raises an *note auditing event: e96. ‘socket.gethostbyname’ with
     argument ‘hostname’.

 -- 函式: socket.gethostbyname_ex (hostname)

     Translate a host name to IPv4 address format, extended interface.
     Return a triple ‘(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
     addresses for the same interface on the same host (often but not
     always a single address).  *note gethostbyname_ex(): ea3. does not
     support IPv6 name resolution, and *note getaddrinfo(): 25c2. should
     be used instead for IPv4/v6 dual stack support.

     Raises an *note auditing event: e96. ‘socket.gethostbyname’ with
     argument ‘hostname’.

 -- 函式: socket.gethostname ()

     Return a string containing the hostname of the machine where the
     Python interpreter is currently executing.

     Raises an *note auditing event: e96. ‘socket.gethostname’ with no
     arguments.

     Note: *note gethostname(): 1f0a. doesn’t always return the fully
     qualified domain name; use *note getfqdn(): 2690. for that.

 -- 函式: socket.gethostbyaddr (ip_address)

     Return a triple ‘(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(): 2690.
     *note gethostbyaddr(): ea2. supports both IPv4 and IPv6.

     Raises an *note auditing event: e96. ‘socket.gethostbyaddr’ with
     argument ‘ip_address’.

 -- 函式: 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’ is appended to the host part if
     `sockaddr' contains meaningful `scopeid'.  Usually this happens for
     multicast addresses.

     For more information about `flags' you can consult
     ‘getnameinfo(3)’.

     Raises an *note auditing event: e96. ‘socket.getnameinfo’ with
     argument ‘sockaddr’.

 -- 函式: 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(): 679. function.  This is usually only needed for
     sockets opened in "raw" mode (*note SOCK_RAW: 2677.); for the
     normal socket modes, the correct protocol is chosen automatically
     if the protocol is omitted or zero.

 -- 函式: 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.

     Raises an *note auditing event: e96. ‘socket.getservbyname’ with
     arguments ‘servicename’, ‘protocolname’.

 -- 函式: 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.

     Raises an *note auditing event: e96. ‘socket.getservbyport’ with
     arguments ‘port’, ‘protocolname’.

 -- 函式: 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.7 版後已棄用: In case `x' does not fit in 16-bit unsigned
     integer, but does fit in a positive C int, it is silently truncated
     to 16-bit unsigned integer.  This silent truncation feature is
     deprecated, and will raise an exception in future versions of
     Python.

 -- 函式: 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.7 版後已棄用: In case `x' does not fit in 16-bit unsigned
     integer, but does fit in a positive C int, it is silently truncated
     to 16-bit unsigned integer.  This silent truncation feature is
     deprecated, and will raise an exception in future versions of
     Python.

 -- 函式: 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 ‘struct in_addr’, which is the C type for the 32-bit packed
     binary this function returns.

     *note inet_aton(): 2697. also accepts strings with less than three
     dots; see the Unix manual page ‘inet(3)’ for details.

     If the IPv4 address string passed to this function is invalid,
     *note OSError: 1d4. will be raised.  Note that exactly what is
     valid depends on the underlying C implementation of ‘inet_aton()’.

     *note inet_aton(): 2697. does not support IPv6, and *note
     inet_pton(): 8c0. 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:
     5ed. 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 ‘struct 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: 1d4. will be raised.  *note inet_ntoa():
     2698. does not support IPv6, and *note inet_ntop(): 8c1. should be
     used instead for IPv4/v6 dual stack support.

     3.5 版更變: Writable *note bytes-like object: 5ed. 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(): 8c0. is useful when a
     library or network protocol calls for an object of type ‘struct
     in_addr’ (similar to *note inet_aton(): 2697.) or ‘struct
     in6_addr’.

     Supported values for `address_family' are currently *note AF_INET:
     25ae. and *note AF_INET6: 25af.  If the IP address string
     `ip_string' is invalid, *note OSError: 1d4. 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 Availability: 1364.: Unix (maybe not all platforms), Windows.

     3.4 版更變: Windows support added

 -- 函式: socket.inet_ntop (address_family, packed_ip)

     Convert a packed IP address (a *note bytes-like object: 5ed. 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(): 8c1. is useful when a library or network
     protocol returns an object of type ‘struct in_addr’ (similar to
     *note inet_ntoa(): 2698.) or ‘struct in6_addr’.

     Supported values for `address_family' are currently *note AF_INET:
     25ae. and *note AF_INET6: 25af.  If the bytes object `packed_ip' is
     not the correct length for the specified address family, *note
     ValueError: 1fc. will be raised.  *note OSError: 1d4. is raised for
     errors from the call to *note inet_ntop(): 8c1.

     *note Availability: 1364.: Unix (maybe not all platforms), Windows.

     3.4 版更變: Windows support added

     3.5 版更變: Writable *note bytes-like object: 5ed. 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(): 67e. to
     receive a single item of ancillary data, but RFC 3542(1) requires
     portable applications to use *note CMSG_SPACE(): 1025. and thus
     include space for padding, even when the item will be the last in
     the buffer.  Raises *note OverflowError: 965. if `length' is
     outside the permissible range of values.

     *note Availability: 1364.: most Unix platforms, possibly others.

     3.3 版新加入.

 -- 函式: socket.CMSG_SPACE (length)

     Return the buffer size needed for *note recvmsg(): 67e. 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(): 1025.
     values for their associated data lengths.  Raises *note
     OverflowError: 965. 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 Availability: 1364.: most Unix platforms, possibly others.

     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(): 2670. for possible values and their
     respective meanings.

 -- 函式: socket.sethostname (name)

     Set the machine’s hostname to `name'.  This will raise an *note
     OSError: 1d4. if you don’t have enough rights.

     Raises an *note auditing event: e96. ‘socket.sethostname’ with
     argument ‘name’.

     *note Availability: 1364.: Unix.

     3.3 版新加入.

 -- 函式: socket.if_nameindex ()

     Return a list of network interface information (index int, name
     string) tuples.  *note OSError: 1d4. if the system call fails.

     *note Availability: 1364.: Unix, Windows.

     3.3 版新加入.

     3.8 版更變: Windows support was added.

          備註: 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: 1d4. if no interface with the given
     name exists.

     *note Availability: 1364.: Unix, Windows.

     3.3 版新加入.

     3.8 版更變: Windows support was added.

     也參考
     ......

     "Interface name" is a name as documented in *note if_nameindex():
     221.

 -- 函式: socket.if_indextoname (if_index)

     Return a network interface name corresponding to an interface index
     number.  *note OSError: 1d4. if no interface with the given index
     exists.

     *note Availability: 1364.: Unix, Windows.

     3.3 版新加入.

     3.8 版更變: Windows support was added.

     也參考
     ......

     "Interface name" is a name as documented in *note if_nameindex():
     221.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc3542.html


File: python.info,  Node: Socket Objects,  Next: Notes on socket timeouts,  Prev: Module contents,  Up: socket --- Low-level networking interface

5.18.2.8 Socket Objects
.......................

Socket objects have the following methods.  Except for *note makefile():
b1e, these correspond to Unix system calls applicable to sockets.

3.2 版更變: Support for the *note context manager: 56d. protocol was
added.  Exiting the context manager is equivalent to calling *note
close(): 3d6.

 -- 成員函式: 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: 7ff.

     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: 65e.
     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.)

     Raises an *note auditing event: e96. ‘socket.bind’ with arguments
     ‘self’, ‘address’.

 -- 成員函式: 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(): b1e. 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(): 3d6. them explicitly, or to
     use a *note with: 6ee. statement around them.

     3.6 版更變: *note OSError: 1d4. is now raised if an error occurs
     when the underlying ‘close()’ call is made.

          備註: *note close(): 3d6. 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(): 269b. before *note
          close(): 3d6.

 -- 成員函式: 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 socket.timeout:
     c13. 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: 65e.
     exception if the connection is interrupted by a signal (or the
     exception raised by the signal handler).

     Raises an *note auditing event: e96. ‘socket.connect’ with
     arguments ‘self’, ‘address’.

     3.5 版更變: The method now waits until the connection completes
     instead of raising an *note InterruptedError: 65e. 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).

 -- 成員函式: 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.

     Raises an *note auditing event: e96. ‘socket.connect’ with
     arguments ‘self’, ‘address’.

 -- 成員函式: 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: 7ff.

     3.4 版更變: The socket is now non-inheritable.

 -- 成員函式: socket.fileno ()

     Return the socket’s file descriptor (a small integer), or -1 on
     failure.  This is useful with *note select.select(): 678.

     Under Windows the small integer returned by this method cannot be
     used where a file descriptor can be used (such as *note
     os.fdopen(): 1436.).  Unix does not have this limitation.

 -- 成員函式: socket.get_inheritable ()

     Get the *note inheritable flag: 7ff. 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)’).  The needed symbolic constants (‘SO_*’ etc.)  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: f9. for a
     way to decode C structures encoded as byte strings).

 -- 成員函式: socket.getblocking ()

     Return ‘True’ if socket is in blocking mode, ‘False’ if in
     non-blocking.

     This is equivalent to checking ‘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(): 1f16. or *note settimeout(): 2670.

 -- 成員函式: socket.ioctl (control, option)


     Platform: Windows

     The *note ioctl(): 585. method is a limited interface to the
     WSAIoctl system interface.  Please refer to the Win32
     documentation(3) for more information.

     On other platforms, the generic *note fcntl.fcntl(): 26a0. and
     *note fcntl.ioctl(): de3. 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’ was added.

 -- 成員函式: 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.

     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: b47. associated with the socket.  The
     exact returned type depends on the arguments given to *note
     makefile(): b1e.  These arguments are interpreted the same way as
     by the built-in *note open(): 4f5. function, except the only
     supported `mode' values are ‘'r'’ (default), ‘'w'’ and ‘'b'’.

     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(): b1e. won’t
     close the original socket unless all other file objects have been
     closed and *note socket.close(): 3d6. has been called on the socket
     object.

          備註: On Windows, the file-like object created by *note
          makefile(): b1e. cannot be used where a file object with a
          file descriptor is expected, such as the stream arguments of
          *note subprocess.Popen(): 2ba.

 -- 成員函式: 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'.  See the Unix manual
     page ‘recv(2)’ 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: 65e.
     exception (see PEP 475(4) 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)’ 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: 65e.
     exception (see PEP 475(5) for the rationale).

     3.7 版更變: For multicast IPv6 address, first item of `address'
     does not contain ‘%scope’ part anymore.  In order to get full IPv6
     address use *note getnameinfo(): 25c3.

 -- 成員函式: 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(): 1025. or *note CMSG_LEN(): 1026, 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(): 67c.

     The return value is a 4-tuple: ‘(data, ancdata, msg_flags,
     address)’.  The `data' item is a *note bytes: 336. 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: 336. 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(): 681. and *note recvmsg(): 67e.
     can be used to pass file descriptors between processes over an
     *note AF_UNIX: 25b4. socket.  When this facility is used (it is
     often restricted to *note SOCK_STREAM: c8f. sockets), *note
     recvmsg(): 67e. will return, in its ancillary data, items of the
     form ‘(socket.SOL_SOCKET, socket.SCM_RIGHTS, fds)’, where `fds' is
     a *note bytes: 336. object representing the new file descriptors as
     a binary array of the native C ‘int’ type.  If *note recvmsg():
     67e. 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(): 67e. will
     issue a *note RuntimeWarning: 2c1, 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(): 681.

          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 Availability: 1364.: most Unix platforms, possibly others.

     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: 65e.
     exception (see PEP 475(6) for the rationale).

 -- 成員函式: socket.recvmsg_into (buffers[, ancbufsize[, flags]])

     Receive normal data and ancillary data from the socket, behaving as
     *note recvmsg(): 67e. 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: 337. 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(): 1f3c. 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():
     67e.

     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(): 67e.

     Example:

          >>> 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 Availability: 1364.: most Unix platforms, possibly others.

     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)’ 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)’ 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(): 67c. 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 Programming
     HOWTO: 26a1.

     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: 65e.
     exception (see PEP 475(7) 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(): 67c. above.  Unlike *note send(): 67f, 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 more 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: 65e.
     exception (see PEP 475(8) 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(): 67c. above.  Return the number of bytes sent.
     (The format of `address' depends on the address family — see
     above.)

     Raises an *note auditing event: e96. ‘socket.sendto’ with arguments
     ‘self’, ‘address’.

     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: 65e.
     exception (see PEP 475(9) 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: 5ed.
     (e.g.  *note bytes: 336. objects); the operating system may set a
     limit (*note sysconf(): 1f3c. 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(): 1025.)
     might support sending only one control message per call.  The
     `flags' argument defaults to 0 and has the same meaning as for
     *note send(): 67f.  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: 25b4. socket, on systems which support the
     ‘SCM_RIGHTS’ mechanism.  See also *note recvmsg(): 67e.

          import socket, array

          def send_fds(sock, msg, fds):
              return sock.sendmsg([msg], [(socket.SOL_SOCKET, socket.SCM_RIGHTS, array.array("i", fds))])

     *note Availability: 1364.: most Unix platforms, possibly others.

     Raises an *note auditing event: e96. ‘socket.sendmsg’ with
     arguments ‘self’, ‘address’.

     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: 65e.
     exception (see PEP 475(10) for the rationale).

 -- 成員函式: socket.sendmsg_afalg ([msg], *, op[, iv[, assoclen[,
          flags]]])

     Specialized version of *note sendmsg(): 681. for *note AF_ALG: 589.
     socket.  Set mode, IV, AEAD associated data length and flags for
     *note AF_ALG: 589. socket.

     *note Availability: 1364.: 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: 35e. 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: 35e. is not available (e.g.  Windows) or
     `file' is not a regular file *note send(): 67f. 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(): 1d9e. can be used to figure out the number of bytes
     which were sent.  The socket must be of *note SOCK_STREAM: c8f.
     type.  Non-blocking sockets are not supported.

     3.5 版新加入.

 -- 成員函式: socket.set_inheritable (inheritable)

     Set the *note inheritable flag: 7ff. 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(): 2670.
     calls:

        * ‘sock.setblocking(True)’ is equivalent to
          ‘sock.settimeout(None)’

        * ‘sock.setblocking(False)’ is equivalent to
          ‘sock.settimeout(0.0)’

     3.7 版更變: The method no longer applies *note SOCK_NONBLOCK: 49b.
     flag on *note socket.type: 49d.

 -- 成員函式: 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: c13. 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: 26a2.

     3.7 版更變: The method no longer toggles *note SOCK_NONBLOCK: 49b.
     flag on *note socket.type: 49d.

 -- 成員函式: 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)’).  The needed symbolic constants are defined in the
     *note socket: f0. module (‘SO_*’ etc.).  The value can be an
     integer, ‘None’ or a *note bytes-like object: 5ed. 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: f9. 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: 5ed. is now accepted.

     3.6 版更變: setsockopt(level, optname, None, optlen: int) form
     added.

 -- 成員函式: socket.shutdown (how)

     Shut down one or both halves of the connection.  If `how' is
     ‘SHUT_RD’, further receives are disallowed.  If `how' is ‘SHUT_WR’,
     further sends are disallowed.  If `how' is ‘SHUT_RDWR’, further
     sends and receives are disallowed.

 -- 成員函式: 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(): 498.  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 Availability: 1364.: Windows.

     3.3 版新加入.

Note that there are no methods ‘read()’ or ‘write()’; use *note recv():
67c. and *note send(): 67f. without `flags' argument instead.

Socket objects also have these (read-only) attributes that correspond to
the values given to the *note socket: 679. constructor.

 -- 屬性: socket.family

     The socket family.

 -- 屬性: socket.type

     The socket type.

 -- 屬性: socket.proto

     The socket protocol.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0475

   (2) https://www.python.org/dev/peps/pep-0475

   (3) https://msdn.microsoft.com/en-us/library/ms741621%28VS.85%29.aspx

   (4) https://www.python.org/dev/peps/pep-0475

   (5) https://www.python.org/dev/peps/pep-0475

   (6) https://www.python.org/dev/peps/pep-0475

   (7) https://www.python.org/dev/peps/pep-0475

   (8) https://www.python.org/dev/peps/pep-0475

   (9) https://www.python.org/dev/peps/pep-0475

   (10) https://www.python.org/dev/peps/pep-0475


File: python.info,  Node: Notes on socket timeouts,  Next: Example<8>,  Prev: Socket Objects,  Up: socket --- Low-level networking interface

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(): 2675.

   * 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: e6. 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: c13. 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(): 269e. 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(): 67b. operation is also subject to the timeout
setting, and in general it is recommended to call *note settimeout():
2670. before calling *note connect(): 67b. or pass a timeout parameter
to *note create_connection(): ba3.  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(): 268d. is not *note None: 158, sockets
returned by the *note accept(): 67a. 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(): 67a. is in `blocking mode';

   * if the listening socket is in `non-blocking mode', whether the
     socket returned by *note accept(): 67a. 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: Example<8>,  Prev: Notes on socket timeouts,  Up: socket --- Low-level networking interface

5.18.2.12 Example
.................

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(): 679, *note bind(): 269a, *note listen(): 750,
*note accept(): 67a. (possibly repeating the *note accept(): 67a. to
service more than one client), while a client only needs the sequence
*note socket(): 679, *note connect(): 67b.  Also note that the server
does not *note sendall(): 680./*note recv(): 67c. on the socket it is
listening on but on the new socket returned by *note accept(): 67a.

The first two examples support IPv4 only.

     # 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 the all 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 packages
     s.ioctl(socket.SIO_RCVALL, socket.RCVALL_ON)

     # receive a package
     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: 8be.) the
socket, you can use the *note socket.send(): 67f, and the *note
socket.recv(): 67c. 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: f0. 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://tools.ietf.org/html/rfc3493.html


File: python.info,  Node: ssl --- TLS/SSL wrapper for socket objects,  Next: select --- Waiting for I/O completion,  Prev: socket --- Low-level networking interface,  Up: Networking and Interprocess Communication

5.18.3 ‘ssl’ — TLS/SSL wrapper for socket objects
-------------------------------------------------

`Source code:' Lib/ssl.py(1)

__________________________________________________________________

This module provides access to Transport Layer Security (often known as
"Secure Sockets Layer") encryption and peer authentication facilities
for network sockets, both client-side and server-side.  This module uses
the OpenSSL library.  It is available on all modern Unix systems,
Windows, Mac OS X, and probably additional platforms, as long as OpenSSL
is installed on that platform.

     備註: Some behavior may be platform dependent, since calls are made
     to the operating system socket APIs.  The installed version of
     OpenSSL may also cause variations in behavior.  For example,
     TLSv1.1 and TLSv1.2 come with openssl version 1.0.1.

     警告: Don’t use this module without reading the *note Security
     considerations: 25b3.  Doing so may lead to a false sense of
     security, as the default settings of the ssl module are not
     necessarily appropriate for your application.

This section documents the objects and functions in the ‘ssl’ module;
for more general information about TLS, SSL, and certificates, the
reader is referred to the documents in the "See Also" section at the
bottom.

This module provides a class, *note ssl.SSLSocket: 3e7, which is derived
from the *note socket.socket: 679. 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, and
‘cipher()’, which retrieves the cipher being used for the secure
connection.

For more sophisticated applications, the *note ssl.SSLContext: 3e9.
class helps manage settings and certificates, which can then be
inherited by SSL sockets created through the *note
SSLContext.wrap_socket(): 3ea. method.

3.5.3 版更變: Updated to support linking with OpenSSL 1.1.0

3.6 版更變: OpenSSL 0.9.8, 1.0.0 and 1.0.1 are deprecated and no longer
supported.  In the future the ssl module will require at least OpenSSL
1.0.2 or 1.1.0.

* Menu:

* Functions, Constants, and Exceptions: Functions Constants and Exceptions.
* SSL Sockets::
* SSL Contexts::
* Certificates::
* Examples: Examples<16>.
* Notes on non-blocking sockets::
* Memory BIO Support: Memory BIO Support<2>.
* SSL session::
* Security considerations::
* TLS 1.3: TLS 1 3.
* LibreSSL support::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/ssl.py


File: python.info,  Node: Functions Constants and Exceptions,  Next: SSL Sockets,  Up: ssl --- TLS/SSL wrapper for socket objects

5.18.3.1 Functions, Constants, and Exceptions
.............................................

* Menu:

* Socket creation::
* Context creation::
* Exceptions: Exceptions<11>.
* Random generation::
* Certificate handling::
* Constants: Constants<9>.


File: python.info,  Node: Socket creation,  Next: Context creation,  Up: Functions Constants and Exceptions

5.18.3.2 Socket creation
........................

Since Python 3.2 and 2.7.9, it is recommended to use the *note
SSLContext.wrap_socket(): 3ea. of an *note SSLContext: 3e9. instance to
wrap sockets as *note SSLSocket: 3e7. objects.  The helper functions
*note create_default_context(): 8c6. returns a new context with secure
default settings.  The old *note wrap_socket(): 474. function is
deprecated since it is both inefficient and has no support for server
name indication (SNI) and hostname matching.

Client socket example with default context and IPv4/IPv6 dual stack:

     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())

Client socket example with custom context and IPv4:

     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())

Server socket example listening on localhost IPv4:

     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: Context creation,  Next: Exceptions<11>,  Prev: Socket creation,  Up: Functions Constants and Exceptions

5.18.3.3 Context creation
.........................

A convenience function helps create *note SSLContext: 3e9. objects for
common purposes.

 -- 函式: ssl.create_default_context (purpose=Purpose.SERVER_AUTH,
          cafile=None, capath=None, cadata=None)

     Return a new *note SSLContext: 3e9. object with default settings
     for the given `purpose'.  The settings are chosen by the *note ssl:
     f4. module, and usually represent a higher security level than when
     calling the *note SSLContext: 3e9. constructor directly.

     `cafile', `capath', `cadata' represent optional CA certificates to
     trust for certificate verification, as in *note
     SSLContext.load_verify_locations(): 7f0.  If all three are *note
     None: 158, this function can choose to trust the system’s default
     CA certificates instead.

     The settings are: *note PROTOCOL_TLS: 26af, *note OP_NO_SSLv2: ba5,
     and *note OP_NO_SSLv3: 26b0. with high encryption cipher suites
     without RC4 and without unauthenticated cipher suites.  Passing
     *note SERVER_AUTH: 8d1. as `purpose' sets *note verify_mode: 26b1.
     to *note CERT_REQUIRED: 26b2. and either loads CA certificates
     (when at least one of `cafile', `capath' or `cadata' is given) or
     uses *note SSLContext.load_default_certs(): 8d0. to load default CA
     certificates.

     When *note keylog_filename: 26b3. is supported and the environment
     variable ‘SSLKEYLOGFILE’ is set, *note create_default_context():
     8c6. enables key logging.

          備註: The protocol, options, cipher and other settings may
          change to more restrictive values anytime without prior
          deprecation.  The values represent a fair balance between
          compatibility and security.

          If your application needs specific settings, you should create
          a *note SSLContext: 3e9. and apply the settings yourself.

          備註: If you find that when certain older clients or servers
          attempt to connect with a *note SSLContext: 3e9. created by
          this function that they get an error stating "Protocol or
          cipher suite mismatch", it may be that they only support
          SSL3.0 which this function excludes using the *note
          OP_NO_SSLv3: 26b0.  SSL3.0 is widely considered to be
          completely broken(1).  If you still wish to continue to use
          this function but still allow SSL 3.0 connections you can
          re-enable them using:

               ctx = ssl.create_default_context(Purpose.CLIENT_AUTH)
               ctx.options &= ~ssl.OP_NO_SSLv3

     3.4 版新加入.

     3.4.4 版更變: RC4 was dropped from the default cipher string.

     3.6 版更變: ChaCha20/Poly1305 was added to the default cipher
     string.

     3DES was dropped from the default cipher string.

     3.8 版更變: Support for key logging to ‘SSLKEYLOGFILE’ was added.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/POODLE


File: python.info,  Node: Exceptions<11>,  Next: Random generation,  Prev: Context creation,  Up: Functions Constants and Exceptions

5.18.3.4 Exceptions
...................

 -- 例外: ssl.SSLError

     Raised to signal an error from the underlying SSL implementation
     (currently provided by the OpenSSL library).  This signifies some
     problem in the higher-level encryption and authentication layer
     that’s superimposed on the underlying network connection.  This
     error is a subtype of *note OSError: 1d4.  The error code and
     message of *note SSLError: c14. instances are provided by the
     OpenSSL library.

     3.3 版更變: *note SSLError: c14. used to be a subtype of *note
     socket.error: 99a.

      -- 屬性: library

          A string mnemonic designating the OpenSSL submodule in which
          the error occurred, such as ‘SSL’, ‘PEM’ or ‘X509’.  The range
          of possible values depends on the OpenSSL version.

          3.3 版新加入.

      -- 屬性: reason

          A string mnemonic designating the reason this error occurred,
          for example ‘CERTIFICATE_VERIFY_FAILED’.  The range of
          possible values depends on the OpenSSL version.

          3.3 版新加入.

 -- 例外: ssl.SSLZeroReturnError

     A subclass of *note SSLError: c14. raised when trying to read or
     write and the SSL connection has been closed cleanly.  Note that
     this doesn’t mean that the underlying transport (read TCP) has been
     closed.

     3.3 版新加入.

 -- 例外: ssl.SSLWantReadError

     A subclass of *note SSLError: c14. raised by a *note non-blocking
     SSL socket: 26b6. when trying to read or write data, but more data
     needs to be received on the underlying TCP transport before the
     request can be fulfilled.

     3.3 版新加入.

 -- 例外: ssl.SSLWantWriteError

     A subclass of *note SSLError: c14. raised by a *note non-blocking
     SSL socket: 26b6. when trying to read or write data, but more data
     needs to be sent on the underlying TCP transport before the request
     can be fulfilled.

     3.3 版新加入.

 -- 例外: ssl.SSLSyscallError

     A subclass of *note SSLError: c14. raised when a system error was
     encountered while trying to fulfill an operation on a SSL socket.
     Unfortunately, there is no easy way to inspect the original errno
     number.

     3.3 版新加入.

 -- 例外: ssl.SSLEOFError

     A subclass of *note SSLError: c14. raised when the SSL connection
     has been terminated abruptly.  Generally, you shouldn’t try to
     reuse the underlying transport when this error is encountered.

     3.3 版新加入.

 -- 例外: ssl.SSLCertVerificationError

     A subclass of *note SSLError: c14. raised when certificate
     validation has failed.

     3.7 版新加入.

      -- 屬性: verify_code

          A numeric error number that denotes the verification error.

      -- 屬性: verify_message

          A human readable string of the verification error.

 -- 例外: ssl.CertificateError

     An alias for *note SSLCertVerificationError: 3e2.

     3.7 版更變: The exception is now an alias for *note
     SSLCertVerificationError: 3e2.


File: python.info,  Node: Random generation,  Next: Certificate handling,  Prev: Exceptions<11>,  Up: Functions Constants and Exceptions

5.18.3.5 Random generation
..........................

 -- 函式: ssl.RAND_bytes (num)

     Return `num' cryptographically strong pseudo-random bytes.  Raises
     an *note SSLError: c14. if the PRNG has not been seeded with enough
     data or if the operation is not supported by the current RAND
     method.  *note RAND_status(): 26bd. can be used to check the status
     of the PRNG and *note RAND_add(): 26be. can be used to seed the
     PRNG.

     For almost all applications *note os.urandom(): 4d6. is preferable.

     Read the Wikipedia article, Cryptographically secure pseudorandom
     number generator (CSPRNG)(1), to get the requirements of a
     cryptographically generator.

     3.3 版新加入.

 -- 函式: ssl.RAND_pseudo_bytes (num)

     Return (bytes, is_cryptographic): bytes are `num' pseudo-random
     bytes, is_cryptographic is ‘True’ if the bytes generated are
     cryptographically strong.  Raises an *note SSLError: c14. if the
     operation is not supported by the current RAND method.

     Generated pseudo-random byte sequences will be unique if they are
     of sufficient length, but are not necessarily unpredictable.  They
     can be used for non-cryptographic purposes and for certain purposes
     in cryptographic protocols, but usually not for key generation etc.

     For almost all applications *note os.urandom(): 4d6. is preferable.

     3.3 版新加入.

     3.6 版後已棄用: OpenSSL has deprecated *note
     ssl.RAND_pseudo_bytes(): a95, use *note ssl.RAND_bytes(): a94.
     instead.

 -- 函式: ssl.RAND_status ()

     Return ‘True’ if the SSL pseudo-random number generator has been
     seeded with ’enough’ randomness, and ‘False’ otherwise.  You can
     use *note ssl.RAND_egd(): 26bf. and *note ssl.RAND_add(): 26be. to
     increase the randomness of the pseudo-random number generator.

 -- 函式: ssl.RAND_egd (path)

     If you are running an entropy-gathering daemon (EGD) somewhere, and
     `path' is the pathname of a socket connection open to it, this will
     read 256 bytes of randomness from the socket, and add it to the SSL
     pseudo-random number generator to increase the security of
     generated secret keys.  This is typically only necessary on systems
     without better sources of randomness.

     See ‘http://egd.sourceforge.net/’ or
     ‘http://prngd.sourceforge.net/’ for sources of entropy-gathering
     daemons.

     *note Availability: 1364.: not available with LibreSSL and OpenSSL
     > 1.1.0.

 -- 函式: ssl.RAND_add (bytes, entropy)

     Mix the given `bytes' into the SSL pseudo-random number generator.
     The parameter `entropy' (a float) is a lower bound on the entropy
     contained in string (so you can always use ‘0.0’).  See RFC 1750(2)
     for more information on sources of entropy.

     3.5 版更變: Writable *note bytes-like object: 5ed. is now accepted.

   ---------- Footnotes ----------

   (1) 
https://en.wikipedia.org/wiki/Cryptographically_secure_pseudorandom_number_generator

   (2) https://tools.ietf.org/html/rfc1750.html


File: python.info,  Node: Certificate handling,  Next: Constants<9>,  Prev: Random generation,  Up: Functions Constants and Exceptions

5.18.3.6 Certificate handling
.............................

 -- 函式: ssl.match_hostname (cert, hostname)

     Verify that `cert' (in decoded format as returned by *note
     SSLSocket.getpeercert(): 8d6.) matches the given `hostname'.  The
     rules applied are those for checking the identity of HTTPS servers
     as outlined in RFC 2818(1), RFC 5280(2) and RFC 6125(3).  In
     addition to HTTPS, this function should be suitable for checking
     the identity of servers in various SSL-based protocols such as
     FTPS, IMAPS, POPS and others.

     *note CertificateError: 26bb. is raised on failure.  On success,
     the function returns nothing:

          >>> cert = {'subject': ((('commonName', 'example.com'),),)}
          >>> ssl.match_hostname(cert, "example.com")
          >>> ssl.match_hostname(cert, "example.org")
          Traceback (most recent call last):
            File "<stdin>", line 1, in <module>
            File "/home/py3k/Lib/ssl.py", line 130, in match_hostname
          ssl.CertificateError: hostname 'example.org' doesn't match 'example.com'

     3.2 版新加入.

     3.3.3 版更變: The function now follows RFC 6125(4), section 6.4.3
     and does neither match multiple wildcards (e.g.  ‘*.*.com’ or
     ‘*a*.example.org’) nor a wildcard inside an internationalized
     domain names (IDN) fragment.  IDN A-labels such as
     ‘www*.xn--pthon-kva.org’ are still supported, but ‘x*.python.org’
     no longer matches ‘xn--tda.python.org’.

     3.5 版更變: Matching of IP addresses, when present in the
     subjectAltName field of the certificate, is now supported.

     3.7 版更變: The function is no longer used to TLS connections.
     Hostname matching is now performed by OpenSSL.

     Allow wildcard when it is the leftmost and the only character in
     that segment.  Partial wildcards like ‘www*.example.com’ are no
     longer supported.

     3.7 版後已棄用.

 -- 函式: ssl.cert_time_to_seconds (cert_time)

     Return the time in seconds since the Epoch, given the ‘cert_time’
     string representing the "notBefore" or "notAfter" date from a
     certificate in ‘"%b %d %H:%M:%S %Y %Z"’ strptime format (C locale).

     Here’s an example:

          >>> 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" or "notAfter" dates must use GMT ( RFC 5280(5)).

     3.5 版更變: Interpret the input time as a time in UTC as specified
     by ’GMT’ timezone in the input string.  Local timezone was used
     previously.  Return an integer (no fractions of a second in the
     input format)

 -- 函式: ssl.get_server_certificate (addr, ssl_version=PROTOCOL_TLS,
          ca_certs=None)

     Given the address ‘addr’ of an SSL-protected server, as a
     (`hostname', `port-number') pair, fetches the server’s certificate,
     and returns it as a PEM-encoded string.  If ‘ssl_version’ is
     specified, uses that version of the SSL protocol to attempt to
     connect to the server.  If ‘ca_certs’ is specified, it should be a
     file containing a list of root certificates, the same format as
     used for the same parameter in *note SSLContext.wrap_socket(): 3ea.
     The call will attempt to validate the server certificate against
     that set of root certificates, and will fail if the validation
     attempt fails.

     3.3 版更變: This function is now IPv6-compatible.

     3.5 版更變: The default `ssl_version' is changed from *note
     PROTOCOL_SSLv3: 26c1. to *note PROTOCOL_TLS: 26af. for maximum
     compatibility with modern servers.

 -- 函式: ssl.DER_cert_to_PEM_cert (DER_cert_bytes)

     Given a certificate as a DER-encoded blob of bytes, returns a
     PEM-encoded string version of the same certificate.

 -- 函式: ssl.PEM_cert_to_DER_cert (PEM_cert_string)

     Given a certificate as an ASCII PEM string, returns a DER-encoded
     sequence of bytes for that same certificate.

 -- 函式: ssl.get_default_verify_paths ()

     Returns a named tuple with paths to OpenSSL’s default cafile and
     capath.  The paths are the same as used by *note
     SSLContext.set_default_verify_paths(): 8c8.  The return value is a
     *note named tuple: aa8. ‘DefaultVerifyPaths’:

        * ‘cafile’ - resolved path to cafile or ‘None’ if the file
          doesn’t exist,

        * ‘capath’ - resolved path to capath or ‘None’ if the directory
          doesn’t exist,

        * ‘openssl_cafile_env’ - OpenSSL’s environment key that points
          to a cafile,

        * ‘openssl_cafile’ - hard coded path to a cafile,

        * ‘openssl_capath_env’ - OpenSSL’s environment key that points
          to a capath,

        * ‘openssl_capath’ - hard coded path to a capath directory

     *note Availability: 1364.: LibreSSL ignores the environment vars
     ‘openssl_cafile_env’ and ‘openssl_capath_env’.

     3.4 版新加入.

 -- 函式: ssl.enum_certificates (store_name)

     Retrieve certificates from Windows’ system cert store.
     `store_name' may be one of ‘CA’, ‘ROOT’ or ‘MY’.  Windows may
     provide additional cert stores, too.

     The function returns a list of (cert_bytes, encoding_type, trust)
     tuples.  The encoding_type specifies the encoding of cert_bytes.
     It is either ‘x509_asn’ for X.509 ASN.1 data or ‘pkcs_7_asn’ for
     PKCS#7 ASN.1 data.  Trust specifies the purpose of the certificate
     as a set of OIDS or exactly ‘True’ if the certificate is
     trustworthy for all purposes.

     Example:

          >>> 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 Availability: 1364.: Windows.

     3.4 版新加入.

 -- 函式: ssl.enum_crls (store_name)

     Retrieve CRLs from Windows’ system cert store.  `store_name' may be
     one of ‘CA’, ‘ROOT’ or ‘MY’.  Windows may provide additional cert
     stores, too.

     The function returns a list of (cert_bytes, encoding_type, trust)
     tuples.  The encoding_type specifies the encoding of cert_bytes.
     It is either ‘x509_asn’ for X.509 ASN.1 data or ‘pkcs_7_asn’ for
     PKCS#7 ASN.1 data.

     *note Availability: 1364.: Windows.

     3.4 版新加入.

 -- 函式: ssl.wrap_socket (sock, keyfile=None, certfile=None,
          server_side=False, cert_reqs=CERT_NONE,
          ssl_version=PROTOCOL_TLS, ca_certs=None,
          do_handshake_on_connect=True, suppress_ragged_eofs=True,
          ciphers=None)

     Takes an instance ‘sock’ of *note socket.socket: 679, and returns
     an instance of *note ssl.SSLSocket: 3e7, a subtype of *note
     socket.socket: 679, which wraps the underlying socket in an SSL
     context.  ‘sock’ must be a *note SOCK_STREAM: c8f. socket; other
     socket types are unsupported.

     Internally, function creates a *note SSLContext: 3e9. with protocol
     `ssl_version' and *note SSLContext.options: 26c4. set to
     `cert_reqs'.  If parameters `keyfile', `certfile', `ca_certs' or
     `ciphers' are set, then the values are passed to *note
     SSLContext.load_cert_chain(): a96, *note
     SSLContext.load_verify_locations(): 7f0, and *note
     SSLContext.set_ciphers(): 26c5.

     The arguments `server_side', `do_handshake_on_connect', and
     `suppress_ragged_eofs' have the same meaning as *note
     SSLContext.wrap_socket(): 3ea.

     3.7 版後已棄用: Since Python 3.2 and 2.7.9, it is recommended to
     use the *note SSLContext.wrap_socket(): 3ea. instead of *note
     wrap_socket(): 474.  The top-level function is limited and creates
     an insecure client socket without server name indication or
     hostname matching.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2818.html

   (2) https://tools.ietf.org/html/rfc5280.html

   (3) https://tools.ietf.org/html/rfc6125.html

   (4) https://tools.ietf.org/html/rfc6125.html

   (5) https://tools.ietf.org/html/rfc5280.html


File: python.info,  Node: Constants<9>,  Prev: Certificate handling,  Up: Functions Constants and Exceptions

5.18.3.7 Constants
..................

     All constants are now *note enum.IntEnum: 592. or *note
     enum.IntFlag: 1760. collections.

     3.6 版新加入.

 -- Data: ssl.CERT_NONE

     Possible value for *note SSLContext.verify_mode: 26b1, or the
     ‘cert_reqs’ parameter to *note wrap_socket(): 474.  Except for
     *note PROTOCOL_TLS_CLIENT: 26c8, it is the default mode.  With
     client-side sockets, just about any cert is accepted.  Validation
     errors, such as untrusted or expired cert, are ignored and do not
     abort the TLS/SSL handshake.

     In server mode, no certificate is requested from the client, so the
     client does not send any for client cert authentication.

     See the discussion of *note Security considerations: 25b3. below.

 -- Data: ssl.CERT_OPTIONAL

     Possible value for *note SSLContext.verify_mode: 26b1, or the
     ‘cert_reqs’ parameter to *note wrap_socket(): 474.  In client mode,
     *note CERT_OPTIONAL: 26c9. has the same meaning as *note
     CERT_REQUIRED: 26b2.  It is recommended to use *note CERT_REQUIRED:
     26b2. for client-side sockets instead.

     In server mode, a client certificate request is sent to the client.
     The client may either ignore the request or send a certificate in
     order perform TLS client cert authentication.  If the client
     chooses to send a certificate, it is verified.  Any verification
     error immediately aborts the TLS handshake.

     Use of this setting requires a valid set of CA certificates to be
     passed, either to *note SSLContext.load_verify_locations(): 7f0. or
     as a value of the ‘ca_certs’ parameter to *note wrap_socket(): 474.

 -- Data: ssl.CERT_REQUIRED

     Possible value for *note SSLContext.verify_mode: 26b1, or the
     ‘cert_reqs’ parameter to *note wrap_socket(): 474.  In this mode,
     certificates are required from the other side of the socket
     connection; an *note SSLError: c14. will be raised if no
     certificate is provided, or if its validation fails.  This mode is
     `not' sufficient to verify a certificate in client mode as it does
     not match hostnames.  *note check_hostname: 26ca. must be enabled
     as well to verify the authenticity of a cert.  *note
     PROTOCOL_TLS_CLIENT: 26c8. uses *note CERT_REQUIRED: 26b2. and
     enables *note check_hostname: 26ca. by default.

     With server socket, this mode provides mandatory TLS client cert
     authentication.  A client certificate request is sent to the client
     and the client must provide a valid and trusted certificate.

     Use of this setting requires a valid set of CA certificates to be
     passed, either to *note SSLContext.load_verify_locations(): 7f0. or
     as a value of the ‘ca_certs’ parameter to *note wrap_socket(): 474.

 -- 類別: ssl.VerifyMode

     *note enum.IntEnum: 592. collection of CERT_* constants.

     3.6 版新加入.

 -- Data: ssl.VERIFY_DEFAULT

     Possible value for *note SSLContext.verify_flags: 8cb.  In this
     mode, certificate revocation lists (CRLs) are not checked.  By
     default OpenSSL does neither require nor verify CRLs.

     3.4 版新加入.

 -- Data: ssl.VERIFY_CRL_CHECK_LEAF

     Possible value for *note SSLContext.verify_flags: 8cb.  In this
     mode, only the peer cert is checked but none of the intermediate CA
     certificates.  The mode requires a valid CRL that is signed by the
     peer cert’s issuer (its direct ancestor CA). If no proper CRL has
     been loaded with *note SSLContext.load_verify_locations: 7f0,
     validation will fail.

     3.4 版新加入.

 -- Data: ssl.VERIFY_CRL_CHECK_CHAIN

     Possible value for *note SSLContext.verify_flags: 8cb.  In this
     mode, CRLs of all certificates in the peer cert chain are checked.

     3.4 版新加入.

 -- Data: ssl.VERIFY_X509_STRICT

     Possible value for *note SSLContext.verify_flags: 8cb. to disable
     workarounds for broken X.509 certificates.

     3.4 版新加入.

 -- Data: ssl.VERIFY_X509_TRUSTED_FIRST

     Possible value for *note SSLContext.verify_flags: 8cb.  It
     instructs OpenSSL to prefer trusted certificates when building the
     trust chain to validate a certificate.  This flag is enabled by
     default.

     3.4.4 版新加入.

 -- 類別: ssl.VerifyFlags

     *note enum.IntFlag: 1760. collection of VERIFY_* constants.

     3.6 版新加入.

 -- Data: ssl.PROTOCOL_TLS

     Selects the highest protocol version that both the client and
     server support.  Despite the name, this option can select both
     "SSL" and "TLS" protocols.

     3.6 版新加入.

 -- Data: ssl.PROTOCOL_TLS_CLIENT

     Auto-negotiate the highest protocol version like *note
     PROTOCOL_TLS: 26af, but only support client-side *note SSLSocket:
     3e7. connections.  The protocol enables *note CERT_REQUIRED: 26b2.
     and *note check_hostname: 26ca. by default.

     3.6 版新加入.

 -- Data: ssl.PROTOCOL_TLS_SERVER

     Auto-negotiate the highest protocol version like *note
     PROTOCOL_TLS: 26af, but only support server-side *note SSLSocket:
     3e7. connections.

     3.6 版新加入.

 -- Data: ssl.PROTOCOL_SSLv23

     Alias for *note PROTOCOL_TLS: 26af.

     3.6 版後已棄用: Use *note PROTOCOL_TLS: 26af. instead.

 -- Data: ssl.PROTOCOL_SSLv2

     Selects SSL version 2 as the channel encryption protocol.

     This protocol is not available if OpenSSL is compiled with the
     ‘OPENSSL_NO_SSL2’ flag.

          警告: SSL version 2 is insecure.  Its use is highly
          discouraged.

     3.6 版後已棄用: OpenSSL has removed support for SSLv2.

 -- Data: ssl.PROTOCOL_SSLv3

     Selects SSL version 3 as the channel encryption protocol.

     This protocol is not be available if OpenSSL is compiled with the
     ‘OPENSSL_NO_SSLv3’ flag.

          警告: SSL version 3 is insecure.  Its use is highly
          discouraged.

     3.6 版後已棄用: OpenSSL has deprecated all version specific
     protocols.  Use the default protocol *note PROTOCOL_TLS: 26af. with
     flags like *note OP_NO_SSLv3: 26b0. instead.

 -- Data: ssl.PROTOCOL_TLSv1

     Selects TLS version 1.0 as the channel encryption protocol.

     3.6 版後已棄用: OpenSSL has deprecated all version specific
     protocols.  Use the default protocol *note PROTOCOL_TLS: 26af. with
     flags like *note OP_NO_SSLv3: 26b0. instead.

 -- Data: ssl.PROTOCOL_TLSv1_1

     Selects TLS version 1.1 as the channel encryption protocol.
     Available only with openssl version 1.0.1+.

     3.4 版新加入.

     3.6 版後已棄用: OpenSSL has deprecated all version specific
     protocols.  Use the default protocol *note PROTOCOL_TLS: 26af. with
     flags like *note OP_NO_SSLv3: 26b0. instead.

 -- Data: ssl.PROTOCOL_TLSv1_2

     Selects TLS version 1.2 as the channel encryption protocol.  This
     is the most modern version, and probably the best choice for
     maximum protection, if both sides can speak it.  Available only
     with openssl version 1.0.1+.

     3.4 版新加入.

     3.6 版後已棄用: OpenSSL has deprecated all version specific
     protocols.  Use the default protocol *note PROTOCOL_TLS: 26af. with
     flags like *note OP_NO_SSLv3: 26b0. instead.

 -- Data: ssl.OP_ALL

     Enables workarounds for various bugs present in other SSL
     implementations.  This option is set by default.  It does not
     necessarily set the same flags as OpenSSL’s ‘SSL_OP_ALL’ constant.

     3.2 版新加入.

 -- Data: ssl.OP_NO_SSLv2

     Prevents an SSLv2 connection.  This option is only applicable in
     conjunction with *note PROTOCOL_TLS: 26af.  It prevents the peers
     from choosing SSLv2 as the protocol version.

     3.2 版新加入.

     3.6 版後已棄用: SSLv2 is deprecated

 -- Data: ssl.OP_NO_SSLv3

     Prevents an SSLv3 connection.  This option is only applicable in
     conjunction with *note PROTOCOL_TLS: 26af.  It prevents the peers
     from choosing SSLv3 as the protocol version.

     3.2 版新加入.

     3.6 版後已棄用: SSLv3 is deprecated

 -- Data: ssl.OP_NO_TLSv1

     Prevents a TLSv1 connection.  This option is only applicable in
     conjunction with *note PROTOCOL_TLS: 26af.  It prevents the peers
     from choosing TLSv1 as the protocol version.

     3.2 版新加入.

     3.7 版後已棄用: The option is deprecated since OpenSSL 1.1.0, use
     the new *note SSLContext.minimum_version: 3ec. and *note
     SSLContext.maximum_version: 3ed. instead.

 -- Data: ssl.OP_NO_TLSv1_1

     Prevents a TLSv1.1 connection.  This option is only applicable in
     conjunction with *note PROTOCOL_TLS: 26af.  It prevents the peers
     from choosing TLSv1.1 as the protocol version.  Available only with
     openssl version 1.0.1+.

     3.4 版新加入.

     3.7 版後已棄用: The option is deprecated since OpenSSL 1.1.0.

 -- Data: ssl.OP_NO_TLSv1_2

     Prevents a TLSv1.2 connection.  This option is only applicable in
     conjunction with *note PROTOCOL_TLS: 26af.  It prevents the peers
     from choosing TLSv1.2 as the protocol version.  Available only with
     openssl version 1.0.1+.

     3.4 版新加入.

     3.7 版後已棄用: The option is deprecated since OpenSSL 1.1.0.

 -- Data: ssl.OP_NO_TLSv1_3

     Prevents a TLSv1.3 connection.  This option is only applicable in
     conjunction with *note PROTOCOL_TLS: 26af.  It prevents the peers
     from choosing TLSv1.3 as the protocol version.  TLS 1.3 is
     available with OpenSSL 1.1.1 or later.  When Python has been
     compiled against an older version of OpenSSL, the flag defaults to
     `0'.

     3.7 版新加入.

     3.7 版後已棄用: The option is deprecated since OpenSSL 1.1.0.  It
     was added to 2.7.15, 3.6.3 and 3.7.0 for backwards compatibility
     with OpenSSL 1.0.2.

 -- Data: ssl.OP_NO_RENEGOTIATION

     Disable all renegotiation in TLSv1.2 and earlier.  Do not send
     HelloRequest messages, and ignore renegotiation requests via
     ClientHello.

     This option is only available with OpenSSL 1.1.0h and later.

     3.7 版新加入.

 -- Data: ssl.OP_CIPHER_SERVER_PREFERENCE

     Use the server’s cipher ordering preference, rather than the
     client’s.  This option has no effect on client sockets and SSLv2
     server sockets.

     3.3 版新加入.

 -- Data: ssl.OP_SINGLE_DH_USE

     Prevents re-use of the same DH key for distinct SSL sessions.  This
     improves forward secrecy but requires more computational resources.
     This option only applies to server sockets.

     3.3 版新加入.

 -- Data: ssl.OP_SINGLE_ECDH_USE

     Prevents re-use of the same ECDH key for distinct SSL sessions.
     This improves forward secrecy but requires more computational
     resources.  This option only applies to server sockets.

     3.3 版新加入.

 -- Data: ssl.OP_ENABLE_MIDDLEBOX_COMPAT

     Send dummy Change Cipher Spec (CCS) messages in TLS 1.3 handshake
     to make a TLS 1.3 connection look more like a TLS 1.2 connection.

     This option is only available with OpenSSL 1.1.1 and later.

     3.8 版新加入.

 -- Data: ssl.OP_NO_COMPRESSION

     Disable compression on the SSL channel.  This is useful if the
     application protocol supports its own compression scheme.

     This option is only available with OpenSSL 1.0.0 and later.

     3.3 版新加入.

 -- 類別: ssl.Options

     *note enum.IntFlag: 1760. collection of OP_* constants.

 -- Data: ssl.OP_NO_TICKET

     Prevent client side from requesting a session ticket.

     3.6 版新加入.

 -- Data: ssl.OP_IGNORE_UNEXPECTED_EOF

     Ignore unexpected shutdown of TLS connections.

     This option is only available with OpenSSL 3.0.0 and later.

     3.10 版新加入.

 -- Data: ssl.HAS_ALPN

     Whether the OpenSSL library has built-in support for the
     `Application-Layer Protocol Negotiation' TLS extension as described
     in RFC 7301(1).

     3.5 版新加入.

 -- Data: ssl.HAS_NEVER_CHECK_COMMON_NAME

     Whether the OpenSSL library has built-in support not checking
     subject common name and *note
     SSLContext.hostname_checks_common_name: 3e3. is writeable.

     3.7 版新加入.

 -- Data: ssl.HAS_ECDH

     Whether the OpenSSL library has built-in support for the Elliptic
     Curve-based Diffie-Hellman key exchange.  This should be true
     unless the feature was explicitly disabled by the distributor.

     3.3 版新加入.

 -- Data: ssl.HAS_SNI

     Whether the OpenSSL library has built-in support for the `Server
     Name Indication' extension (as defined in RFC 6066(2)).

     3.2 版新加入.

 -- Data: ssl.HAS_NPN

     Whether the OpenSSL library has built-in support for the `Next
     Protocol Negotiation' as described in the Application Layer
     Protocol Negotiation(3).  When true, you can use the *note
     SSLContext.set_npn_protocols(): a9c. method to advertise which
     protocols you want to support.

     3.3 版新加入.

 -- Data: ssl.HAS_SSLv2

     Whether the OpenSSL library has built-in support for the SSL 2.0
     protocol.

     3.7 版新加入.

 -- Data: ssl.HAS_SSLv3

     Whether the OpenSSL library has built-in support for the SSL 3.0
     protocol.

     3.7 版新加入.

 -- Data: ssl.HAS_TLSv1

     Whether the OpenSSL library has built-in support for the TLS 1.0
     protocol.

     3.7 版新加入.

 -- Data: ssl.HAS_TLSv1_1

     Whether the OpenSSL library has built-in support for the TLS 1.1
     protocol.

     3.7 版新加入.

 -- Data: ssl.HAS_TLSv1_2

     Whether the OpenSSL library has built-in support for the TLS 1.2
     protocol.

     3.7 版新加入.

 -- Data: ssl.HAS_TLSv1_3

     Whether the OpenSSL library has built-in support for the TLS 1.3
     protocol.

     3.7 版新加入.

 -- Data: ssl.CHANNEL_BINDING_TYPES

     List of supported TLS channel binding types.  Strings in this list
     can be used as arguments to *note SSLSocket.get_channel_binding():
     a99.

     3.3 版新加入.

 -- Data: ssl.OPENSSL_VERSION

     The version string of the OpenSSL library loaded by the
     interpreter:

          >>> ssl.OPENSSL_VERSION
          'OpenSSL 1.0.2k  26 Jan 2017'

     3.2 版新加入.

 -- Data: ssl.OPENSSL_VERSION_INFO

     A tuple of five integers representing version information about the
     OpenSSL library:

          >>> ssl.OPENSSL_VERSION_INFO
          (1, 0, 2, 11, 15)

     3.2 版新加入.

 -- Data: ssl.OPENSSL_VERSION_NUMBER

     The raw version number of the OpenSSL library, as a single integer:

          >>> ssl.OPENSSL_VERSION_NUMBER
          268443839
          >>> hex(ssl.OPENSSL_VERSION_NUMBER)
          '0x100020bf'

     3.2 版新加入.

 -- Data: ssl.ALERT_DESCRIPTION_HANDSHAKE_FAILURE
 -- Data: ssl.ALERT_DESCRIPTION_INTERNAL_ERROR

 -- Data: ALERT_DESCRIPTION_*

     Alert Descriptions from RFC 5246(4) and others.  The IANA TLS Alert
     Registry(5) contains this list and references to the RFCs where
     their meaning is defined.

     Used as the return value of the callback function in *note
     SSLContext.set_servername_callback(): 8d5.

     3.4 版新加入.

 -- 類別: ssl.AlertDescription

     *note enum.IntEnum: 592. collection of ALERT_DESCRIPTION_*
     constants.

     3.6 版新加入.

 -- Data: Purpose.SERVER_AUTH

     Option for *note create_default_context(): 8c6. and *note
     SSLContext.load_default_certs(): 8d0.  This value indicates that
     the context may be used to authenticate Web servers (therefore, it
     will be used to create client-side sockets).

     3.4 版新加入.

 -- Data: Purpose.CLIENT_AUTH

     Option for *note create_default_context(): 8c6. and *note
     SSLContext.load_default_certs(): 8d0.  This value indicates that
     the context may be used to authenticate Web clients (therefore, it
     will be used to create server-side sockets).

     3.4 版新加入.

 -- 類別: ssl.SSLErrorNumber

     *note enum.IntEnum: 592. collection of SSL_ERROR_* constants.

     3.6 版新加入.

 -- 類別: ssl.TLSVersion

     *note enum.IntEnum: 592. collection of SSL and TLS versions for
     *note SSLContext.maximum_version: 3ed. and *note
     SSLContext.minimum_version: 3ec.

     3.7 版新加入.

 -- 屬性: TLSVersion.MINIMUM_SUPPORTED

 -- 屬性: TLSVersion.MAXIMUM_SUPPORTED

     The minimum or maximum supported SSL or TLS version.  These are
     magic constants.  Their values don’t reflect the lowest and highest
     available TLS/SSL versions.

 -- 屬性: TLSVersion.SSLv3

 -- 屬性: TLSVersion.TLSv1

 -- 屬性: TLSVersion.TLSv1_1

 -- 屬性: TLSVersion.TLSv1_2

 -- 屬性: TLSVersion.TLSv1_3

     SSL 3.0 to TLS 1.3.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc7301.html

   (2) https://tools.ietf.org/html/rfc6066.html

   (3) 
https://en.wikipedia.org/wiki/Application-Layer_Protocol_Negotiation

   (4) https://tools.ietf.org/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: Functions Constants and Exceptions,  Up: ssl --- TLS/SSL wrapper for socket objects

5.18.3.8 SSL Sockets
....................

 -- 類別: ssl.SSLSocket (socket.socket)

     SSL sockets provide the following methods of *note Socket Objects:
     268b.:

        - *note accept(): 67a.

        - *note bind(): 269a.

        - *note close(): 605.

        - *note connect(): 67b.

        - *note detach(): ba2.

        - *note fileno(): 269e.

        - *note getpeername(): 25f8, *note getsockname(): 25f9.

        - *note getsockopt(): 587, *note setsockopt(): 588.

        - *note gettimeout(): 269f, *note settimeout(): 2670, *note
          setblocking(): 1f16.

        - *note listen(): 750.

        - *note makefile(): b1e.

        - *note recv(): 67c, *note recv_into(): cb7. (but passing a
          non-zero ‘flags’ argument is not allowed)

        - *note send(): 67f, *note sendall(): 680. (with the same
          limitation)

        - *note sendfile(): 74f. (but *note os.sendfile: 35e. will be
          used for plain-text sockets only, else *note send(): 67f. will
          be used)

        - *note shutdown(): 269b.

     However, since the SSL (and TLS) protocol has its own framing atop
     of TCP, the SSL sockets abstraction can, in certain respects,
     diverge from the specification of normal, OS-level sockets.  See
     especially the *note notes on non-blocking sockets: 26b6.

     Instances of *note SSLSocket: 3e7. must be created using the *note
     SSLContext.wrap_socket(): 3ea. method.

     3.5 版更變: The ‘sendfile()’ method was added.

     3.5 版更變: The ‘shutdown()’ does not reset the socket timeout each
     time bytes are received or sent.  The socket timeout is now to
     maximum total duration of the shutdown.

     3.6 版後已棄用: It is deprecated to create a *note SSLSocket: 3e7.
     instance directly, use *note SSLContext.wrap_socket(): 3ea. to wrap
     a socket.

     3.7 版更變: *note SSLSocket: 3e7. instances must to created with
     *note wrap_socket(): 3ea.  In earlier versions, it was possible to
     create instances directly.  This was never documented or officially
     supported.

SSL sockets also have the following additional methods and attributes:

 -- 成員函式: SSLSocket.read (len=1024, buffer=None)

     Read up to `len' bytes of data from the SSL socket and return the
     result as a ‘bytes’ instance.  If `buffer' is specified, then read
     into the buffer instead, and return the number of bytes read.

     Raise *note SSLWantReadError: 75b. or *note SSLWantWriteError: 75c.
     if the socket is *note non-blocking: 26b6. and the read would
     block.

     As at any time a re-negotiation is possible, a call to *note
     read(): 760. can also cause write operations.

     3.5 版更變: The socket timeout is no more reset each time bytes are
     received or sent.  The socket timeout is now to maximum total
     duration to read up to `len' bytes.

     3.6 版後已棄用: Use ‘recv()’ instead of *note read(): 760.

 -- 成員函式: SSLSocket.write (buf)

     Write `buf' to the SSL socket and return the number of bytes
     written.  The `buf' argument must be an object supporting the
     buffer interface.

     Raise *note SSLWantReadError: 75b. or *note SSLWantWriteError: 75c.
     if the socket is *note non-blocking: 26b6. and the write would
     block.

     As at any time a re-negotiation is possible, a call to *note
     write(): 761. can also cause read operations.

     3.5 版更變: The socket timeout is no more reset each time bytes are
     received or sent.  The socket timeout is now to maximum total
     duration to write `buf'.

     3.6 版後已棄用: Use ‘send()’ instead of *note write(): 761.

     備註: The *note read(): 760. and *note write(): 761. 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():
     26f4. was not called.

     Normally you should use the socket API methods like *note recv():
     67c. and *note send(): 67f. instead of these methods.

 -- 成員函式: SSLSocket.do_handshake ()

     Perform the SSL setup handshake.

     3.4 版更變: The handshake method also performs *note
     match_hostname(): 3e1. when the *note check_hostname: 26ca.
     attribute of the socket’s *note context: 26f5. is true.

     3.5 版更變: The socket timeout is no more reset each time bytes are
     received or sent.  The socket timeout is now to maximum total
     duration of the handshake.

     3.7 版更變: Hostname or IP address is matched by OpenSSL during
     handshake.  The function *note match_hostname(): 3e1. is no longer
     used.  In case OpenSSL refuses a hostname or IP address, the
     handshake is aborted early and a TLS alert message is send 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: 1fc.

     If the ‘binary_form’ parameter is *note False: 38d, and a
     certificate was received from the peer, this method returns a *note
     dict: 1b9. 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}

          備註: To validate a certificate for a particular service, you
          can use the *note match_hostname(): 3e1. function.

     If the ‘binary_form’ parameter is *note True: 49e, and a
     certificate was provided, this method returns the DER-encoded form
     of the entire certificate as a sequence of bytes, or *note None:
     158. 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(): 8d6. will return *note None: 158. if you used
          *note CERT_NONE: 26c7. (rather than *note CERT_OPTIONAL: 26c9.
          or *note CERT_REQUIRED: 26b2.).

     3.2 版更變: The returned dictionary includes additional items such
     as ‘issuer’ and ‘notBefore’.

     3.4 版更變: *note ValueError: 1fc. is raised when the handshake
     isn’t done.  The returned dictionary includes additional X509v3
     extension items such as ‘crlDistributionPoints’, ‘caIssuers’ and
     ‘OCSP’ URIs.

     3.8.1 版更變: IPv6 address strings no longer have a trailing new
     line.

 -- 成員函式: 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 shared by the client during the
     handshake.  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(): 75e. 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: a9b. 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: 26e6. list.  Currently only the ’tls-unique’
     channel binding, defined by RFC 5929(2), is supported.  *note
     ValueError: 1fc. 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(): 756. 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(): a9c.
     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 版新加入.

 -- 成員函式: 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:
     225.

     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: c14. is raised.

          備註: Only available with OpenSSL 1.1.1 and TLS 1.3 enabled.
          Without TLS 1.3 support, the method raises *note
          NotImplementedError: 613.

     3.8 版新加入.

 -- 成員函式: SSLSocket.version ()

     Return the actual SSL protocol version negotiated by the connection
     as a string, or ‘None’ is 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: 3e9. object this SSL socket is tied to.  If
     the SSL socket was created using the deprecated *note
     wrap_socket(): 474. function (rather than *note
     SSLContext.wrap_socket(): 3ea.), this is a custom context object
     created for this SSL socket.

     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: 335. 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: 590. 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(): 75f. has been called to reuse a
     session.

     3.6 版新加入.

 -- 屬性: SSLSocket.session_reused

     3.6 版新加入.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc3280.html

   (2) https://tools.ietf.org/html/rfc5929.html


File: python.info,  Node: SSL Contexts,  Next: Certificates,  Prev: SSL Sockets,  Up: ssl --- TLS/SSL wrapper for socket objects

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=PROTOCOL_TLS)

     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: 26af.; 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(): 8c6. lets the *note ssl: f4. module
     choose security settings for a given purpose.

     3.6 版更變: The context is created with secure default values.  The
     options *note OP_NO_COMPRESSION: a9b, *note
     OP_CIPHER_SERVER_PREFERENCE: aa0, *note OP_SINGLE_DH_USE: 26d8,
     *note OP_SINGLE_ECDH_USE: 26d9, *note OP_NO_SSLv2: ba5. (except for
     *note PROTOCOL_SSLv2: 26d0.), and *note OP_NO_SSLv3: 26b0. (except
     for *note PROTOCOL_SSLv3: 26c1.) are set by default.  The initial
     cipher suite list contains only ‘HIGH’ ciphers, no ‘NULL’ ciphers
     and no ‘MD5’ ciphers (except for *note PROTOCOL_SSLv2: 26d0.).

*note SSLContext: 3e9. 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
     in.  Otherwise the private key will be taken from `certfile' as
     well.  See the discussion of *note Certificates: 26fc. 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: c14. 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 other systems it calls *note
     SSLContext.set_default_verify_paths(): 8c8.  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: 8d1. loads
     certificates, that are flagged and trusted for TLS web server
     authentication (client side sockets).  *note Purpose.CLIENT_AUTH:
     8d2. 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: 26b1. is
     other than *note CERT_NONE: 26c7.  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: 8cb. 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: 26fc. 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: 5ed.
     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: 38d. each list entry
     is a dict like the output of *note SSLSocket.getpeercert(): 8d6.
     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(): 26c5.

     Example:

          >>> ctx = ssl.SSLContext(ssl.PROTOCOL_SSLv23)
          >>> ctx.set_ciphers('ECDHE+AESGCM:!ECDSA')
          >>> ctx.get_ciphers()  # OpenSSL 1.0.x
          [{'alg_bits': 256,
            'description': 'ECDHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=ECDH     Au=RSA  '
                           'Enc=AESGCM(256) Mac=AEAD',
            'id': 50380848,
            'name': 'ECDHE-RSA-AES256-GCM-SHA384',
            'protocol': 'TLSv1/SSLv3',
            'strength_bits': 256},
           {'alg_bits': 128,
            'description': 'ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=ECDH     Au=RSA  '
                           'Enc=AESGCM(128) Mac=AEAD',
            'id': 50380847,
            'name': 'ECDHE-RSA-AES128-GCM-SHA256',
            'protocol': 'TLSv1/SSLv3',
            'strength_bits': 128}]

     On OpenSSL 1.1 and newer the cipher dict contains additional
     fields:

          >>> ctx.get_ciphers()  # OpenSSL 1.1+
          [{'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'}]

     *note Availability: 1364.: OpenSSL 1.0.2+.

     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: c14. will be raised.

          備註: when connected, the *note SSLSocket.cipher(): 25fa.
          method of SSL sockets will give the currently selected cipher.

          OpenSSL 1.1.1 has TLS 1.3 cipher suites enabled by default.
          The suites cannot be disabled with *note set_ciphers(): 26c5.

 -- 成員函式: 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(): 757. method will return the
     agreed-upon protocol.

     This method will raise *note NotImplementedError: 613. if *note
     HAS_ALPN: 758. is ‘False’.

     OpenSSL 1.1.0 to 1.1.0e will abort the handshake and raise *note
     SSLError: c14. when both sides support ALPN but cannot agree on a
     protocol.  1.1.0f+ behaves like 1.0.2, *note
     SSLSocket.selected_alpn_protocol(): 757. returns None.

     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(): 26f6. method will return the
     agreed-upon protocol.

     This method will raise *note NotImplementedError: 613. if *note
     HAS_NPN: 26e0. is ‘False’.

     3.3 版新加入.

 -- 屬性: 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: 3e7, the second is a string
     that represents the server name that the client is intending to
     communicate (or *note None: 158. if the TLS Client Hello does not
     contain a server name) and the third argument is the original *note
     SSLContext: 3e9.  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: 3e7.’s *note SSLSocket.context: 26f5. attribute to a
     new object of type *note SSLContext: 3e9. 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(): 757. and *note
     SSLSocket.context: 26f5.  *note SSLSocket.getpeercert(): 8d6, *note
     SSLSocket.getpeercert(): 8d6, *note SSLSocket.cipher(): 25fa. and
     ‘SSLSocket.compress()’ methods require that the TLS connection has
     progressed beyond the TLS Client Hello and therefore will not
     contain 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_*: 26e8. can be returned.  Other return
     values will result in a TLS fatal error with *note
     ALERT_DESCRIPTION_INTERNAL_ERROR: 26e8.

     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: 26e7.

     This method will raise *note NotImplementedError: 613. 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: ead. 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 an decoding error on the server name, the TLS
     connection will terminate with an *note
     ALERT_DESCRIPTION_INTERNAL_ERROR: 26e8. 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: 26d8. 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: 26d9. option to further improve security.

     This method is not available if *note HAS_ECDH: 26de. 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: 26fd. (default *note SSLSocket:
     3e7.).  The returned SSL socket is tied to the context, its
     settings and certificates.  `sock' must be a *note SOCK_STREAM:
     c8f. 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: c14.

     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: 1fc. 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(): 75f. method.  Calling
     *note SSLSocket.do_handshake(): 75f. 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: 49e. (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: 38d, it will raise the exceptions back to
     the caller.

     `session', see *note session: 26f9.

     3.5 版更變: Always allow a server_hostname to be passed, even if
     OpenSSL does not have SNI.

     3.6 版更變: `session' argument was added.

     3.7 版更變: The method returns on instance of *note
     SSLContext.sslsocket_class: 26fd. instead of hard-coded *note
     SSLSocket: 3e7.

 -- 屬性: SSLContext.sslsocket_class

     The return type of *note SSLContext.wrap_socket(): 3ea, defaults to
     *note SSLSocket: 3e7.  The attribute can be overridden on instance
     of class in order to return a custom subclass of *note SSLSocket:
     3e7.

     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: 26fe. (default *note
     SSLObject: 3e8.).  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(): 3ea.

     3.6 版更變: `session' argument was added.

     3.7 版更變: The method returns on instance of *note
     SSLContext.sslobject_class: 26fe. instead of hard-coded *note
     SSLObject: 3e8.

 -- 屬性: SSLContext.sslobject_class

     The return type of *note SSLContext.wrap_bio(): 3eb, defaults to
     *note SSLObject: 3e8.  The attribute can be overridden on instance
     of class in order to return a custom subclass of *note SSLObject:
     3e8.

     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(): 75f.  The context’s *note verify_mode:
     26b1. must be set to *note CERT_OPTIONAL: 26c9. or *note
     CERT_REQUIRED: 26b2, and you must pass `server_hostname' to *note
     wrap_socket(): 3ea. in order to match the hostname.  Enabling
     hostname checking automatically sets *note verify_mode: 26b1. from
     *note CERT_NONE: 26c7. to *note CERT_REQUIRED: 26b2.  It cannot be
     set back to *note CERT_NONE: 26c7. as long as hostname checking is
     enabled.  The *note PROTOCOL_TLS_CLIENT: 26c8. protocol enables
     hostname checking by default.  With other protocols, hostname
     checking must be enabled explicitly.

     Example:

          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: 26b1. is now automatically changed
     to *note CERT_REQUIRED: 26b2. when hostname checking is enabled and
     *note verify_mode: 26b1. is *note CERT_NONE: 26c7.  Previously the
     same operation would have failed with a *note ValueError: 1fc.

          備註: This features requires OpenSSL 0.9.8f or newer.

 -- 屬性: 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 版新加入.

          備註: This features requires OpenSSL 1.1.1 or newer.

 -- 屬性: SSLContext.maximum_version

     A *note TLSVersion: 26eb. enum member representing the highest
     supported TLS version.  The value defaults to *note
     TLSVersion.MAXIMUM_SUPPORTED: 26ed.  The attribute is read-only for
     protocols other than *note PROTOCOL_TLS: 26af, *note
     PROTOCOL_TLS_CLIENT: 26c8, and *note PROTOCOL_TLS_SERVER: 26ce.

     The attributes *note maximum_version: 3ed, *note minimum_version:
     3ec. and *note SSLContext.options: 26c4. 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: 26d5. in *note options: 26c4. and *note
     maximum_version: 3ed. set to *note TLSVersion.TLSv1_2: 26f1. will
     not be able to establish a TLS 1.2 connection.

          備註: This attribute is not available unless the ssl module is
          compiled with OpenSSL 1.1.0g or newer.

     3.7 版新加入.

 -- 屬性: SSLContext.minimum_version

     Like *note SSLContext.maximum_version: 3ed. except it is the lowest
     supported version or *note TLSVersion.MINIMUM_SUPPORTED: 26ec.

          備註: This attribute is not available unless the ssl module is
          compiled with OpenSSL 1.1.0g or newer.

     3.7 版新加入.

 -- 屬性: SSLContext.num_tickets

     Control the number of TLS 1.3 session tickets of a
     ‘TLS_PROTOCOL_SERVER’ context.  The setting has no impact on TLS
     1.0 to 1.2 connections.

          備註: This attribute is not available unless the ssl module is
          compiled with OpenSSL 1.1.1 or newer.

     3.8 版新加入.

 -- 屬性: SSLContext.options

     An integer representing the set of SSL options enabled on this
     context.  The default value is *note OP_ALL: 26d2, but you can
     specify other options such as *note OP_NO_SSLv2: ba5. by ORing them
     together.

          備註: With versions of OpenSSL older than 0.9.8m, it is only
          possible to set options, not to clear them.  Attempting to
          clear an option (by resetting the corresponding bits) will
          raise a *note ValueError: 1fc.

     3.6 版更變: *note SSLContext.options: 26c4. returns *note Options:
     26db. flags:

          >>> ssl.create_default_context().options
          <Options.OP_ALL|OP_NO_SSLv3|OP_NO_SSLv2|OP_NO_COMPRESSION: 2197947391>

 -- 屬性: 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:
     26b1. must be set to *note CERT_OPTIONAL: 26c9. or *note
     CERT_REQUIRED: 26b2, too.  The actual client cert exchange is
     delayed until *note SSLSocket.verify_client_post_handshake(): 226.
     is called and some I/O is performed.

          備註: Only available with OpenSSL 1.1.1 and TLS 1.3 enabled.
          Without TLS 1.3 support, the property value is None and can’t
          be modified

     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: 26ca. falls back to verify the cert’s
     subject common name in the absence of a subject alternative name
     extension (default: true).

          備註: Only writeable with OpenSSL 1.1.0 or higher.

     3.7 版新加入.

     3.9.3 版更變: The flag had no effect with OpenSSL before version
     1.1.1k.  Python 3.8.9, 3.9.3, and 3.10 include workarounds for
     previous versions.

 -- 屬性: SSLContext.verify_flags

     The flags for certificate verification operations.  You can set
     flags like *note VERIFY_CRL_CHECK_LEAF: 8cd. by ORing them
     together.  By default OpenSSL does neither require nor verify
     certificate revocation lists (CRLs).  Available only with openssl
     version 0.9.8+.

     3.4 版新加入.

     3.6 版更變: *note SSLContext.verify_flags: 8cb. returns *note
     VerifyFlags: 26cd. 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: 26c7, *note CERT_OPTIONAL: 26c9. or *note CERT_REQUIRED:
     26b2.

     3.6 版更變: *note SSLContext.verify_mode: 26b1. returns *note
     VerifyMode: 26cb. enum:

          >>> ssl.create_default_context().verify_mode
          <VerifyMode.CERT_REQUIRED: 2>

   ---------- Footnotes ----------

   (1) (3) TLS 1.3 protocol will be available with *note PROTOCOL_TLS:
26af. in OpenSSL >= 1.1.1.  There is no dedicated PROTOCOL constant for
just TLS 1.3.

   (2) (1) *note SSLContext: 3e9. disables SSLv2 with *note OP_NO_SSLv2:
ba5. by default.

   (3) (2) *note SSLContext: 3e9. disables SSLv3 with *note OP_NO_SSLv3:
26b0. by default.

   (4) (3) TLS 1.3 protocol will be available with *note PROTOCOL_TLS:
26af. in OpenSSL >= 1.1.1.  There is no dedicated PROTOCOL constant for
just TLS 1.3.

   (5) (1) *note SSLContext: 3e9. disables SSLv2 with *note OP_NO_SSLv2:
ba5. by default.

   (6) (2) *note SSLContext: 3e9. disables SSLv3 with *note OP_NO_SSLv3:
26b0. by default.

   (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://tools.ietf.org/html/rfc7301.html

   (10) 
https://en.wikipedia.org/wiki/Application-Layer_Protocol_Negotiation

   (11) https://tools.ietf.org/html/rfc6066.html

   (12) 
https://vincent.bernat.im/en/blog/2011-ssl-perfect-forward-secrecy

   (13) 
https://www.openssl.org/docs/man1.1.0/ssl/SSL_CTX_sess_number.html


File: python.info,  Node: Certificates,  Next: Examples<16>,  Prev: SSL Contexts,  Up: ssl --- TLS/SSL wrapper for socket objects

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://tools.ietf.org/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(): 8d0, this is done automatically with
*note create_default_context(): 8c6.


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(): a96. and *note wrap_socket(): 474. 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: Examples<16>,  Next: Notes on non-blocking sockets,  Prev: Certificates,  Up: ssl --- TLS/SSL wrapper for socket objects

5.18.3.15 Examples
..................

* Menu:

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


File: python.info,  Node: Testing for SSL support,  Next: Client-side operation,  Up: Examples<16>

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: Examples<16>

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: 26c8. protocol configures the context for
cert validation and hostname verification.  *note verify_mode: 26b1. is
set to *note CERT_REQUIRED: 26b2. and *note check_hostname: 26ca. 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:
26b2. and *note check_hostname: 26ca. 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'']

See the discussion of *note Security considerations: 25b3. below.


File: python.info,  Node: Server-side operation,  Prev: Client-side operation,  Up: Examples<16>

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.mydomain.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(): 3ea. 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: 26b6. and use an
event loop).


File: python.info,  Node: Notes on non-blocking sockets,  Next: Memory BIO Support<2>,  Prev: Examples<16>,  Up: ssl --- TLS/SSL wrapper for socket objects

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: 3e7. methods will raise either *note
     SSLWantWriteError: 75c. or *note SSLWantReadError: 75b. instead of
     *note BlockingIOError: 99c. if an I/O operation would block.  *note
     SSLWantReadError: 75b. will be raised if a read operation on the
     underlying socket is necessary, and *note SSLWantWriteError: 75c.
     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:
     75c. or *note SSLWantReadError: 75b.

   - Calling *note select(): 678. 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(): 678.

   - Conversely, since the SSL layer has its own framing, a SSL socket
     may still have data available for reading without *note select():
     678. 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(): 678. call if still necessary.

     (of course, similar provisions apply when using other primitives
     such as *note poll(): 270c, or those in the *note selectors: e7.
     module)

   - The SSL handshake itself will be non-blocking: the *note
     SSLSocket.do_handshake(): 75f. method has to be retried until it
     returns successfully.  Here is a synopsis using *note select():
     678. 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: a. module supports *note non-blocking SSL sockets:
26b6. and provides a higher level API. It polls for events using the
*note selectors: e7. module and handles *note SSLWantWriteError: 75c,
*note SSLWantReadError: 75b. and *note BlockingIOError: 99c. 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 --- TLS/SSL wrapper for socket objects

5.18.3.20 Memory BIO Support
............................

3.5 版新加入.

Ever since the SSL module was introduced in Python 2.6, the *note
SSLSocket: 3e7. 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:
679, from which *note SSLSocket: 3e7. 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: 679. 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: 3e7. called *note SSLObject: 3e8. is provided.

 -- 類別: ssl.SSLObject

     A reduced-scope variant of *note SSLSocket: 3e7. 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: 3e8.
     instance must be created using the *note wrap_bio(): 3eb. method.
     This method will create the *note SSLObject: 3e8. 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: 26f5.

        - *note server_side: 26f8.

        - *note server_hostname: 3e5.

        - *note session: 26f9.

        - *note session_reused: 26fa.

        - *note read(): 760.

        - *note write(): 761.

        - *note getpeercert(): 8d6.

        - *note selected_alpn_protocol(): 757.

        - *note selected_npn_protocol(): 26f6.

        - *note cipher(): 25fa.

        - *note shared_ciphers(): 75e.

        - *note compression(): a9a.

        - *note pending(): 26f7.

        - *note do_handshake(): 75f.

        - *note verify_client_post_handshake(): 226.

        - *note unwrap(): 26f4.

        - *note get_channel_binding(): a99.

        - *note version(): 75a.

     When compared to *note SSLSocket: 3e7, this object lacks the
     following features:

        - Any form of network IO; ‘recv()’ and ‘send()’ read and write
          only to the underlying *note MemoryBIO: 754. buffers.

        - There is no `do_handshake_on_connect' machinery.  You must
          always manually call *note do_handshake(): 75f. 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: 26b8. exception.

        - The method *note unwrap(): 26f4. 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(): 8d5. will get an *note
          SSLObject: 3e8. instance instead of a *note SSLSocket: 3e7.
          instance as its first parameter.

     Some notes related to the use of *note SSLObject: 3e8.:

        - All IO on an *note SSLObject: 3e8. is *note non-blocking:
          26b6.  This means that for example *note read(): 760. will
          raise an *note SSLWantReadError: 75b. if it needs more data
          than the incoming BIO has available.

        - There is no module-level ‘wrap_bio()’ call like there is for
          *note wrap_socket(): 3ea.  An *note SSLObject: 3e8. is always
          created via an *note SSLContext: 3e9.

     3.7 版更變: *note SSLObject: 3e8. instances must to created with
     *note wrap_bio(): 3eb.  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: 754. 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(): 2711.  The
          attribute *note eof: 270f. will become true after all data
          currently in the buffer has been read.


File: python.info,  Node: SSL session,  Next: Security considerations,  Prev: Memory BIO Support<2>,  Up: ssl --- TLS/SSL wrapper for socket objects

5.18.3.21 SSL session
.....................

3.6 版新加入.

 -- 類別: ssl.SSLSession

     Session object used by *note session: 26f9.

      -- 屬性: id

      -- 屬性: time

      -- 屬性: timeout

      -- 屬性: ticket_lifetime_hint

      -- 屬性: has_ticket


File: python.info,  Node: Security considerations,  Next: TLS 1 3,  Prev: SSL session,  Up: ssl --- TLS/SSL wrapper for socket objects

5.18.3.22 Security considerations
.................................

* Menu:

* Best defaults::
* Manual settings::
* Multi-processing::


File: python.info,  Node: Best defaults,  Next: Manual settings,  Up: Security considerations

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(): 8c6. 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: a86.
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(): a96.

By contrast, if you create the SSL context by calling the *note
SSLContext: 3e9. 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: Manual settings,  Next: Multi-processing,  Prev: Best defaults,  Up: Security considerations

5.18.3.24 Manual settings
.........................

* Menu:

* Verifying certificates::
* Protocol versions::
* Cipher selection::


File: python.info,  Node: Verifying certificates,  Next: Protocol versions,  Up: Manual settings

5.18.3.25 Verifying certificates
................................

When calling the *note SSLContext: 3e9. constructor directly, *note
CERT_NONE: 26c7. is the default.  Since it does not authenticate the
other peer, it can be insecure, especially in client mode where most of
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: 26b2.  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(): 8d6, matches the
desired service.  For many protocols and applications, the service can
be identified by the hostname; in this case, the *note match_hostname():
3e1. function can be used.  This common check is automatically performed
when *note SSLContext.check_hostname: 26ca. is enabled.

3.7 版更變: Hostname matchings is now performed by OpenSSL. Python no
longer uses *note match_hostname(): 3e1.

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: 26b2. and similarly
check the client certificate.


File: python.info,  Node: Protocol versions,  Next: Cipher selection,  Prev: Verifying certificates,  Up: Manual settings

5.18.3.26 Protocol versions
...........................

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: 26c8. or *note
PROTOCOL_TLS_SERVER: 26ce. as the protocol version.  SSLv2 and SSLv3 are
disabled by default.

     >>> client_context = ssl.SSLContext(ssl.PROTOCOL_TLS_CLIENT)
     >>> client_context.options |= ssl.OP_NO_TLSv1
     >>> client_context.options |= ssl.OP_NO_TLSv1_1

The SSL context created above will only allow TLSv1.2 and later (if
supported by your system) connections to a server.  *note
PROTOCOL_TLS_CLIENT: 26c8. implies certificate validation and hostname
checks by default.  You have to load certificates into the context.


File: python.info,  Node: Cipher selection,  Prev: Protocol versions,  Up: Manual settings

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(): 26c5. 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(): 591. or the ‘openssl ciphers’ command on your
system.

   ---------- Footnotes ----------

   (1) 
https://www.openssl.org/docs/manmaster/man1/ciphers.html#CIPHER-LIST-FORMAT


File: python.info,  Node: Multi-processing,  Prev: Manual settings,  Up: Security considerations

5.18.3.28 Multi-processing
..........................

If using this module as part of a multi-processed application (using,
for example the *note multiprocessing: b8. or *note concurrent.futures:
22. 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(): 966.  Any successful call of *note RAND_add(): 26be, *note
RAND_bytes(): a94. or *note RAND_pseudo_bytes(): a95. is sufficient.


File: python.info,  Node: TLS 1 3,  Next: LibreSSL support,  Prev: Security considerations,  Up: ssl --- TLS/SSL wrapper for socket objects

5.18.3.29 TLS 1.3
.................

3.7 版新加入.

Python has provisional and experimental support for TLS 1.3 with OpenSSL
1.1.1.  The new 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(): 26c5. cannot enable or disable any TLS
     1.3 ciphers yet, but *note SSLContext.get_ciphers(): 591. returns
     them.

   - Session tickets are no longer sent as part of the initial handshake
     and are handled differently.  *note SSLSocket.session: 26f9. and
     *note SSLSession: 590. 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.


File: python.info,  Node: LibreSSL support,  Prev: TLS 1 3,  Up: ssl --- TLS/SSL wrapper for socket objects

5.18.3.30 LibreSSL support
..........................

LibreSSL is a fork of OpenSSL 1.0.1.  The ssl module has limited support
for LibreSSL. Some features are not available when the ssl module is
compiled with LibreSSL.

   * LibreSSL >= 2.6.1 no longer supports NPN. The methods *note
     SSLContext.set_npn_protocols(): a9c. and *note
     SSLSocket.selected_npn_protocol(): 26f6. are not available.

   * *note SSLContext.set_default_verify_paths(): 8c8. ignores the env
     vars ‘SSL_CERT_FILE’ and ‘SSL_CERT_PATH’ although *note
     get_default_verify_paths(): 8c7. still reports them.

也參考
......

Class *note socket.socket: 679.

     Documentation of underlying *note socket: f0. class

SSL/TLS Strong Encryption: An Introduction(1)

     Intro from the Apache HTTP Server documentation

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://tools.ietf.org/html/rfc1422.html

   (3) https://tools.ietf.org/html/rfc4086.html

   (4) https://tools.ietf.org/html/rfc5280.html

   (5) https://tools.ietf.org/html/rfc5246.html

   (6) https://tools.ietf.org/html/rfc6066.html

   (7) 
https://www.iana.org/assignments/tls-parameters/tls-parameters.xml

   (8) https://tools.ietf.org/html/rfc7525.html

   (9) https://wiki.mozilla.org/Security/Server_Side_TLS


File: python.info,  Node: select --- Waiting for I/O completion,  Next: selectors --- High-level I/O multiplexing,  Prev: ssl --- TLS/SSL wrapper for socket objects,  Up: Networking and Interprocess Communication

5.18.4 ‘select’ — Waiting for I/O completion
--------------------------------------------

__________________________________________________________________

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: e7. module allows high-level and
     efficient I/O multiplexing, built upon the *note select: e6. module
     primitives.  Users are encouraged to use the *note selectors: e7.
     module instead, unless they want precise control over the OS-level
     primitives used.

The module defines the following:

 -- 例外: select.error

     A deprecated alias of *note OSError: 1d4.

     3.3 版更變: Following PEP 3151(1), this class was made an alias of
     *note OSError: 1d4.

 -- 函式: select.devpoll ()

     (Only supported on Solaris and derivatives.)  Returns a ‘/dev/poll’
     polling object; see section *note /dev/poll Polling Objects: 2725.
     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: 7ff.

     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: 2726.
     section below for the methods supported by epolling objects.

     ‘epoll’ objects support the context management protocol: when used
     in a *note with: 6ee. statement, the new file descriptor is
     automatically closed at the end of the block.

     The new file descriptor is *note non-inheritable: 7ff.

     3.3 版更變: Added the `flags' parameter.

     3.4 版更變: Support for the *note with: 6ee. 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(): 801. 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: 2727. below for the methods supported by
     polling objects.

 -- 函式: select.kqueue ()

     (Only supported on BSD.) Returns a kernel queue object; see section
     *note Kqueue Objects: 2729. below for the methods supported by
     kqueue objects.

     The new file descriptor is *note non-inheritable: 7ff.

     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: 272b. 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(): 1f0f. 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: b47. (e.g.  ‘sys.stdin’, or objects returned by *note
     open(): 4f5. or *note os.popen(): 2aa.), socket objects returned by
     *note socket.socket(): 679.  You may also define a `wrapper' class
     yourself, as long as it has an appropriate *note fileno(): 1f0f.
     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: 65e.

 -- 屬性: 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(): 678, *note poll(): 270c. 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 Availability: 1364.: 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://www.python.org/dev/peps/pep-3151

   (2) https://www.python.org/dev/peps/pep-0475


File: python.info,  Node: /dev/poll Polling Objects,  Next: Edge and Level Trigger Polling epoll Objects,  Up: select --- Waiting for I/O completion

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(): 270c. 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(): 1f0f. 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(): 272f. followed by a *note
     register(): 272d.  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(): 272d. method, `fd' can be an integer or
     an object with a *note fileno(): 1f0f. 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: 158, 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: 65e.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0475


File: python.info,  Node: Edge and Level Trigger Polling epoll Objects,  Next: Polling Objects,  Prev: /dev/poll Polling Objects,  Up: select --- Waiting for I/O completion

5.18.4.2 Edge and Level Trigger Polling (epoll) Objects
.......................................................

     ‘https://linux.die.net/man/4/epoll’

     `eventmask'

     Constant                      Meaning
                                   
     ----------------------------------------------------------------------------------
                                   
     ‘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’                 Equivalent to ‘EPOLLIN’
                                   
                                   
     ‘EPOLLRDBAND’                 Priority data band can be read.
                                   
                                   
     ‘EPOLLWRNORM’                 Equivalent to ‘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.

 -- 成員函式: 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: 65e.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0475


File: python.info,  Node: Polling Objects,  Next: Kqueue Objects,  Prev: Edge and Level Trigger Polling epoll Objects,  Up: select --- Waiting for I/O completion

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(): 270c. 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(): 1f0f. 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.

     Constant                Meaning
                             
     -----------------------------------------------------------------------
                             
     ‘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: 1d4. 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(): 2738. method, `fd' can be an integer or
     an object with a *note fileno(): 1f0f. method that returns an
     integer.

     Attempting to remove a file descriptor that was never registered
     causes a *note KeyError: 2c8. 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: 158, 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: 65e.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0475


File: python.info,  Node: Kqueue Objects,  Next: Kevent Objects,  Prev: Polling Objects,  Up: select --- Waiting for I/O completion

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: 65e.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0475


File: python.info,  Node: Kevent Objects,  Prev: Kqueue Objects,  Up: select --- Waiting for I/O completion

5.18.4.5 Kevent Objects
.......................

‘https://www.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(): 1f0f. method.  kevent stores the integer internally.

 -- 屬性: kevent.filter

     Name of the kernel filter.

     Constant                        Meaning
                                     
     ----------------------------------------------------------------------------------
                                     
     ‘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 Mac OS X]
                                     
                                     
     ‘KQ_FILTER_SIGNAL’              Returns whenever the watched signal is
                                     delivered to the process
                                     
                                     
     ‘KQ_FILTER_TIMER’               Establishes an arbitrary timer
                                     

 -- 屬性: kevent.flags

     Filter action.

     Constant                        Meaning
                                     
     ----------------------------------------------------------------------------------
                                     
     ‘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:

     Constant                         Meaning
                                      
     ----------------------------------------------------------------------------------
                                      
     ‘KQ_NOTE_LOWAT’                  low water mark of a socket buffer
                                      

     ‘KQ_FILTER_VNODE’ filter flags:

     Constant                         Meaning
                                      
     ----------------------------------------------------------------------------------
                                      
     ‘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:

     Constant                         Meaning
                                      
     ----------------------------------------------------------------------------------
                                      
     ‘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 Mac OS X):

     Constant                         Meaning
                                      
     ----------------------------------------------------------------------------------
                                      
     ‘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 --- High-level I/O multiplexing,  Next: asyncore --- Asynchronous socket handler,  Prev: select --- Waiting for I/O completion,  Up: Networking and Interprocess Communication

5.18.5 ‘selectors’ — High-level I/O multiplexing
------------------------------------------------

3.4 版新加入.

`Source code:' Lib/selectors.py(1)

__________________________________________________________________

* Menu:

* 簡介: 簡介<9>.
* Classes: Classes<3>.
* Examples: Examples<17>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/selectors.py


File: python.info,  Node: 簡介<9>,  Next: Classes<3>,  Up: selectors --- High-level I/O multiplexing

5.18.5.1 簡介
.............

This module allows high-level and efficient I/O multiplexing, built upon
the *note select: e6. 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: 274a. abstract base class, along with
several concrete implementations (*note KqueueSelector: 264c, *note
EpollSelector: 451...), 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 ‘fileno()’ method, or a raw file descriptor.
See *note file object: b47.

*note DefaultSelector: 274b. 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: e6.

     Low-level I/O multiplexing module.


File: python.info,  Node: Classes<3>,  Next: Examples<17>,  Prev: 簡介<9>,  Up: selectors --- High-level I/O multiplexing

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                    Meaning
                                 
     --------------------------------------------------------------------------------
                                 
     ‘EVENT_READ’                Available for read
                                 
                                 
     ‘EVENT_WRITE’               Available for write
                                 

 -- 類別: selectors.SelectorKey

     A *note SelectorKey: 274d. is a *note namedtuple: 1b8. used to
     associate a file object to its underlying file descriptor, selected
     event mask and attached data.  It is returned by several *note
     BaseSelector: 274a. 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: 274a. 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: 274b. instead,
     or one of *note SelectSelector: 2649, *note KqueueSelector: 264c.
     etc.  if you want to specifically use an implementation, and your
     platform supports it.  *note BaseSelector: 274a. and its concrete
     implementations support the *note context manager: 56d. 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: 274d. instance, or
          raises a *note ValueError: 1fc. in case of invalid event mask
          or file descriptor, or *note KeyError: 2c8. 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: 274d. instance,
          or raises a *note KeyError: 2c8. if `fileobj' is not
          registered.  It will raise *note ValueError: 1fc. 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: 274d. instance, or
          raises a *note ValueError: 1fc. in case of invalid event mask
          or file descriptor, or *note KeyError: 2c8. 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: 274d. 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: 274d. instance associated
          to this file object, or raises *note KeyError: 2c8. if the
          file object is not registered.

      -- 成員函式: abstractmethod get_map ()

          Return a mapping of file objects to selector keys.

          This returns a *note Mapping: 1949. instance mapping
          registered file objects to their associated *note SelectorKey:
          274d. 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(): 678.-based selector.

 -- 類別: selectors.PollSelector

     *note select.poll(): 270c.-based selector.

 -- 類別: selectors.EpollSelector

     *note select.epoll(): 8ae.-based selector.

      -- 成員函式: fileno ()

          This returns the file descriptor used by the underlying *note
          select.epoll(): 8ae. object.

 -- 類別: selectors.DevpollSelector

     *note select.devpoll(): 8b0.-based selector.

      -- 成員函式: fileno ()

          This returns the file descriptor used by the underlying *note
          select.devpoll(): 8b0. object.

     3.5 版新加入.

 -- 類別: selectors.KqueueSelector

     *note select.kqueue(): 2728.-based selector.

      -- 成員函式: fileno ()

          This returns the file descriptor used by the underlying *note
          select.kqueue(): 2728. object.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0475


File: python.info,  Node: Examples<17>,  Prev: Classes<3>,  Up: selectors --- High-level I/O multiplexing

5.18.5.3 Examples
.................

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: asyncore --- Asynchronous socket handler,  Next: asynchat --- Asynchronous socket command/response handler,  Prev: selectors --- High-level I/O multiplexing,  Up: Networking and Interprocess Communication

5.18.6 ‘asyncore’ — Asynchronous socket handler
-----------------------------------------------

`Source code:' Lib/asyncore.py(1)

3.6 版後已棄用: Please use *note asyncio: a. instead.

__________________________________________________________________

     備註: This module exists for backwards compatibility only.  For new
     code we recommend using *note asyncio: a.

This module provides the basic infrastructure for writing asynchronous
socket service clients and servers.

There are only two ways to have a program on a single processor do "more
than one thing at a time."  Multi-threaded programming is the simplest
and most popular way to do it, but there is another very different
technique, that lets you have nearly all the advantages of
multi-threading, without actually using multiple threads.  It’s really
only practical if your program is largely I/O bound.  If your program is
processor bound, then pre-emptive scheduled threads are probably what
you really need.  Network servers are rarely processor bound, however.

If your operating system supports the ‘select()’ system call in its I/O
library (and nearly all do), then you can use it to juggle multiple
communication channels at once; doing other work while your I/O is
taking place in the "background."  Although this strategy can seem
strange and complex, especially at first, it is in many ways easier to
understand and control than multi-threaded programming.  The *note
asyncore: b. module solves many of the difficult problems for you,
making the task of building sophisticated high-performance network
servers and clients a snap.  For "conversational" applications and
protocols the companion *note asynchat: 9. module is invaluable.

The basic idea behind both modules is to create one or more network
`channels', instances of class *note asyncore.dispatcher: bc8. and *note
asynchat.async_chat: 8ba.  Creating the channels adds them to a global
map, used by the *note loop(): 275e. function if you do not provide it
with your own `map'.

Once the initial channel(s) is(are) created, calling the *note loop():
275e. function activates channel service, which continues until the last
channel (including any that have been added to the map during
asynchronous service) is closed.

 -- 函式: asyncore.loop ([timeout[, use_poll[, map[, count]]]])

     Enter a polling loop that terminates after count passes or all open
     channels have been closed.  All arguments are optional.  The
     `count' parameter defaults to ‘None’, resulting in the loop
     terminating only when all channels have been closed.  The `timeout'
     argument sets the timeout parameter for the appropriate *note
     select(): 678. or *note poll(): 270c. call, measured in seconds;
     the default is 30 seconds.  The `use_poll' parameter, if true,
     indicates that *note poll(): 270c. should be used in preference to
     *note select(): 678. (the default is ‘False’).

     The `map' parameter is a dictionary whose items are the channels to
     watch.  As channels are closed they are deleted from their map.  If
     `map' is omitted, a global map is used.  Channels (instances of
     *note asyncore.dispatcher: bc8, *note asynchat.async_chat: 8ba. and
     subclasses thereof) can freely be mixed in the map.

 -- 類別: asyncore.dispatcher

     The *note dispatcher: bc8. class is a thin wrapper around a
     low-level socket object.  To make it more useful, it has a few
     methods for event-handling which are called from the asynchronous
     loop.  Otherwise, it can be treated as a normal non-blocking socket
     object.

     The firing of low-level events at certain times or in certain
     connection states tells the asynchronous loop that certain
     higher-level events have taken place.  For example, if we have
     asked for a socket to connect to another host, we know that the
     connection has been made when the socket becomes writable for the
     first time (at this point you know that you may write to it with
     the expectation of success).  The implied higher-level events are:

     Event                      描述
                                
     ------------------------------------------------------------------------
                                
     ‘handle_connect()’         Implied by the first read or write event
                                
                                
     ‘handle_close()’           Implied by a read event with no data
                                available
                                
                                
     ‘handle_accepted()’        Implied by a read event on a listening
                                socket
                                

     During asynchronous processing, each mapped channel’s *note
     readable(): 275f. and *note writable(): 2760. methods are used to
     determine whether the channel’s socket should be added to the list
     of channels ‘select()’ed or ‘poll()’ed for read and write events.

     Thus, the set of channel events is larger than the basic socket
     events.  The full set of methods that can be overridden in your
     subclass follows:

      -- 成員函式: handle_read ()

          Called when the asynchronous loop detects that a ‘read()’ call
          on the channel’s socket will succeed.

      -- 成員函式: handle_write ()

          Called when the asynchronous loop detects that a writable
          socket can be written.  Often this method will implement the
          necessary buffering for performance.  For example:

               def handle_write(self):
                   sent = self.send(self.buffer)
                   self.buffer = self.buffer[sent:]

      -- 成員函式: handle_expt ()

          Called when there is out of band (OOB) data for a socket
          connection.  This will almost never happen, as OOB is
          tenuously supported and rarely used.

      -- 成員函式: handle_connect ()

          Called when the active opener’s socket actually makes a
          connection.  Might send a "welcome" banner, or initiate a
          protocol negotiation with the remote endpoint, for example.

      -- 成員函式: handle_close ()

          Called when the socket is closed.

      -- 成員函式: handle_error ()

          Called when an exception is raised and not otherwise handled.
          The default version prints a condensed traceback.

      -- 成員函式: handle_accept ()

          Called on listening channels (passive openers) when a
          connection can be established with a new remote endpoint that
          has issued a *note connect(): 2767. call for the local
          endpoint.  Deprecated in version 3.2; use *note
          handle_accepted(): bc9. instead.

          3.2 版後已棄用.

      -- 成員函式: handle_accepted (sock, addr)

          Called on listening channels (passive openers) when a
          connection has been established with a new remote endpoint
          that has issued a *note connect(): 2767. call for the local
          endpoint.  `sock' is a `new' socket object usable to send and
          receive data on the connection, and `addr' is the address
          bound to the socket on the other end of the connection.

          3.2 版新加入.

      -- 成員函式: readable ()

          Called each time around the asynchronous loop to determine
          whether a channel’s socket should be added to the list on
          which read events can occur.  The default method simply
          returns ‘True’, indicating that by default, all channels will
          be interested in read events.

      -- 成員函式: writable ()

          Called each time around the asynchronous loop to determine
          whether a channel’s socket should be added to the list on
          which write events can occur.  The default method simply
          returns ‘True’, indicating that by default, all channels will
          be interested in write events.

     In addition, each channel delegates or extends many of the socket
     methods.  Most of these are nearly identical to their socket
     partners.

      -- 成員函式: create_socket (family=socket.AF_INET,
               type=socket.SOCK_STREAM)

          This is identical to the creation of a normal socket, and will
          use the same options for creation.  Refer to the *note socket:
          f0. documentation for information on creating sockets.

          3.3 版更變: `family' and `type' arguments can be omitted.

      -- 成員函式: connect (address)

          As with the normal socket object, `address' is a tuple with
          the first element the host to connect to, and the second the
          port number.

      -- 成員函式: send (data)

          Send `data' to the remote end-point of the socket.

      -- 成員函式: recv (buffer_size)

          Read at most `buffer_size' bytes from the socket’s remote
          end-point.  An empty bytes object implies that the channel has
          been closed from the other end.

          Note that *note recv(): 276a. may raise *note BlockingIOError:
          99c. , even though *note select.select(): 678. or *note
          select.poll(): 270c. has reported the socket ready for
          reading.

      -- 成員函式: listen (backlog)

          Listen for connections made to the socket.  The `backlog'
          argument specifies the maximum number of queued connections
          and should be at least 1; the maximum value is
          system-dependent (usually 5).

      -- 成員函式: bind (address)

          Bind the socket to `address'.  The socket must not already be
          bound.  (The format of `address' depends on the address family
          — refer to the *note socket: f0. documentation for more
          information.)  To mark the socket as re-usable (setting the
          ‘SO_REUSEADDR’ option), call the *note dispatcher: bc8.
          object’s ‘set_reuse_addr()’ method.

      -- 成員函式: accept ()

          Accept a connection.  The socket must be bound to an address
          and listening for connections.  The return value can be either
          ‘None’ or 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.  When ‘None’ is returned
          it means the connection didn’t take place, in which case the
          server should just ignore this event and keep listening for
          further incoming connections.

      -- 成員函式: close ()

          Close the socket.  All future operations on the socket object
          will fail.  The remote end-point will receive no more data
          (after queued data is flushed).  Sockets are automatically
          closed when they are garbage-collected.

 -- 類別: asyncore.dispatcher_with_send

     A *note dispatcher: bc8. subclass which adds simple buffered output
     capability, useful for simple clients.  For more sophisticated
     usage use *note asynchat.async_chat: 8ba.

 -- 類別: asyncore.file_dispatcher

     A file_dispatcher takes a file descriptor or *note file object:
     b47. along with an optional map argument and wraps it for use with
     the ‘poll()’ or ‘loop()’ functions.  If provided a file object or
     anything with a ‘fileno()’ method, that method will be called and
     passed to the *note file_wrapper: 2770. constructor.

     *note Availability: 1364.: Unix.

 -- 類別: asyncore.file_wrapper

     A file_wrapper takes an integer file descriptor and calls *note
     os.dup(): f99. to duplicate the handle so that the original handle
     may be closed independently of the file_wrapper.  This class
     implements sufficient methods to emulate a socket for use by the
     *note file_dispatcher: 276f. class.

     *note Availability: 1364.: Unix.

* Menu:

* asyncore Example basic HTTP client::
* asyncore Example basic echo server::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/asyncore.py


File: python.info,  Node: asyncore Example basic HTTP client,  Next: asyncore Example basic echo server,  Up: asyncore --- Asynchronous socket handler

5.18.6.1 asyncore Example basic HTTP client
...........................................

Here is a very basic HTTP client that uses the *note dispatcher: bc8.
class to implement its socket handling:

     import asyncore

     class HTTPClient(asyncore.dispatcher):

         def __init__(self, host, path):
             asyncore.dispatcher.__init__(self)
             self.create_socket()
             self.connect( (host, 80) )
             self.buffer = bytes('GET %s HTTP/1.0\r\nHost: %s\r\n\r\n' %
                                 (path, host), 'ascii')

         def handle_connect(self):
             pass

         def handle_close(self):
             self.close()

         def handle_read(self):
             print(self.recv(8192))

         def writable(self):
             return (len(self.buffer) > 0)

         def handle_write(self):
             sent = self.send(self.buffer)
             self.buffer = self.buffer[sent:]


     client = HTTPClient('www.python.org', '/')
     asyncore.loop()


File: python.info,  Node: asyncore Example basic echo server,  Prev: asyncore Example basic HTTP client,  Up: asyncore --- Asynchronous socket handler

5.18.6.2 asyncore Example basic echo server
...........................................

Here is a basic echo server that uses the *note dispatcher: bc8. class
to accept connections and dispatches the incoming connections to a
handler:

     import asyncore

     class EchoHandler(asyncore.dispatcher_with_send):

         def handle_read(self):
             data = self.recv(8192)
             if data:
                 self.send(data)

     class EchoServer(asyncore.dispatcher):

         def __init__(self, host, port):
             asyncore.dispatcher.__init__(self)
             self.create_socket()
             self.set_reuse_addr()
             self.bind((host, port))
             self.listen(5)

         def handle_accepted(self, sock, addr):
             print('Incoming connection from %s' % repr(addr))
             handler = EchoHandler(sock)

     server = EchoServer('localhost', 8080)
     asyncore.loop()


File: python.info,  Node: asynchat --- Asynchronous socket command/response handler,  Next: signal --- Set handlers for asynchronous events,  Prev: asyncore --- Asynchronous socket handler,  Up: Networking and Interprocess Communication

5.18.7 ‘asynchat’ — Asynchronous socket command/response handler
----------------------------------------------------------------

`Source code:' Lib/asynchat.py(1)

3.6 版後已棄用: Please use *note asyncio: a. instead.

__________________________________________________________________

     備註: This module exists for backwards compatibility only.  For new
     code we recommend using *note asyncio: a.

This module builds on the *note asyncore: b. infrastructure, simplifying
asynchronous clients and servers and making it easier to handle
protocols whose elements are terminated by arbitrary strings, or are of
variable length.  *note asynchat: 9. defines the abstract class *note
async_chat: 8ba. that you subclass, providing implementations of the
‘collect_incoming_data()’ and ‘found_terminator()’ methods.  It uses the
same asynchronous loop as *note asyncore: b, and the two types of
channel, *note asyncore.dispatcher: bc8. and *note asynchat.async_chat:
8ba, can freely be mixed in the channel map.  Typically an *note
asyncore.dispatcher: bc8. server channel generates new *note
asynchat.async_chat: 8ba. channel objects as it receives incoming
connection requests.

 -- 類別: asynchat.async_chat

     This class is an abstract subclass of *note asyncore.dispatcher:
     bc8.  To make practical use of the code you must subclass *note
     async_chat: 8ba, providing meaningful *note
     collect_incoming_data(): 2777. and *note found_terminator(): 2778.
     methods.  The *note asyncore.dispatcher: bc8. methods can be used,
     although not all make sense in a message/response context.

     Like *note asyncore.dispatcher: bc8, *note async_chat: 8ba. defines
     a set of events that are generated by an analysis of socket
     conditions after a ‘select()’ call.  Once the polling loop has been
     started the *note async_chat: 8ba. object’s methods are called by
     the event-processing framework with no action on the part of the
     programmer.

     Two class attributes can be modified, to improve performance, or
     possibly even to conserve memory.

      -- Data: ac_in_buffer_size

          The asynchronous input buffer size (default ‘4096’).

      -- Data: ac_out_buffer_size

          The asynchronous output buffer size (default ‘4096’).

     Unlike *note asyncore.dispatcher: bc8, *note async_chat: 8ba.
     allows you to define a FIFO queue of `producers'.  A producer need
     have only one method, ‘more()’, which should return data to be
     transmitted on the channel.  The producer indicates exhaustion
     (`i.e.'  that it contains no more data) by having its ‘more()’
     method return the empty bytes object.  At this point the *note
     async_chat: 8ba. object removes the producer from the queue and
     starts using the next producer, if any.  When the producer queue is
     empty the ‘handle_write()’ method does nothing.  You use the
     channel object’s *note set_terminator(): 277b. method to describe
     how to recognize the end of, or an important breakpoint in, an
     incoming transmission from the remote endpoint.

     To build a functioning *note async_chat: 8ba. subclass your input
     methods *note collect_incoming_data(): 2777. and *note
     found_terminator(): 2778. must handle the data that the channel
     receives asynchronously.  The methods are described below.

 -- 成員函式: async_chat.close_when_done ()

     Pushes a ‘None’ on to the producer queue.  When this producer is
     popped off the queue it causes the channel to be closed.

 -- 成員函式: async_chat.collect_incoming_data (data)

     Called with `data' holding an arbitrary amount of received data.
     The default method, which must be overridden, raises a *note
     NotImplementedError: 613. exception.

 -- 成員函式: async_chat.discard_buffers ()

     In emergencies this method will discard any data held in the input
     and/or output buffers and the producer queue.

 -- 成員函式: async_chat.found_terminator ()

     Called when the incoming data stream matches the termination
     condition set by *note set_terminator(): 277b.  The default method,
     which must be overridden, raises a *note NotImplementedError: 613.
     exception.  The buffered input data should be available via an
     instance attribute.

 -- 成員函式: async_chat.get_terminator ()

     Returns the current terminator for the channel.

 -- 成員函式: async_chat.push (data)

     Pushes data on to the channel’s queue to ensure its transmission.
     This is all you need to do to have the channel write the data out
     to the network, although it is possible to use your own producers
     in more complex schemes to implement encryption and chunking, for
     example.

 -- 成員函式: async_chat.push_with_producer (producer)

     Takes a producer object and adds it to the producer queue
     associated with the channel.  When all currently-pushed producers
     have been exhausted the channel will consume this producer’s data
     by calling its ‘more()’ method and send the data to the remote
     endpoint.

 -- 成員函式: async_chat.set_terminator (term)

     Sets the terminating condition to be recognized on the channel.
     ‘term’ may be any of three types of value, corresponding to three
     different ways to handle incoming protocol data.

     term            描述
                     
     ------------------------------------------------------------------
                     
     `string'        Will call *note found_terminator(): 2778. when
                     the string is found in the input stream
                     
                     
     `integer'       Will call *note found_terminator(): 2778. when
                     the indicated number of characters have been
                     received
                     
                     
     ‘None’          The channel continues to collect data forever
                     

     Note that any data following the terminator will be available for
     reading by the channel after *note found_terminator(): 2778. is
     called.

* Menu:

* asynchat Example::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/asynchat.py


File: python.info,  Node: asynchat Example,  Up: asynchat --- Asynchronous socket command/response handler

5.18.7.1 asynchat Example
.........................

The following partial example shows how HTTP requests can be read with
*note async_chat: 8ba.  A web server might create an
‘http_request_handler’ object for each incoming client connection.
Notice that initially the channel terminator is set to match the blank
line at the end of the HTTP headers, and a flag indicates that the
headers are being read.

Once the headers have been read, if the request is of type POST
(indicating that further data are present in the input stream) then the
‘Content-Length:’ header is used to set a numeric terminator to read the
right amount of data from the channel.

The ‘handle_request()’ method is called once all relevant input has been
marshalled, after setting the channel terminator to ‘None’ to ensure
that any extraneous data sent by the web client are ignored.

     import asynchat

     class http_request_handler(asynchat.async_chat):

         def __init__(self, sock, addr, sessions, log):
             asynchat.async_chat.__init__(self, sock=sock)
             self.addr = addr
             self.sessions = sessions
             self.ibuffer = []
             self.obuffer = b""
             self.set_terminator(b"\r\n\r\n")
             self.reading_headers = True
             self.handling = False
             self.cgi_data = None
             self.log = log

         def collect_incoming_data(self, data):
             """Buffer the data"""
             self.ibuffer.append(data)

         def found_terminator(self):
             if self.reading_headers:
                 self.reading_headers = False
                 self.parse_headers(b"".join(self.ibuffer))
                 self.ibuffer = []
                 if self.op.upper() == b"POST":
                     clen = self.headers.getheader("content-length")
                     self.set_terminator(int(clen))
                 else:
                     self.handling = True
                     self.set_terminator(None)
                     self.handle_request()
             elif not self.handling:
                 self.set_terminator(None)  # browsers sometimes over-send
                 self.cgi_data = parse(self.headers, b"".join(self.ibuffer))
                 self.handling = True
                 self.ibuffer = []
                 self.handle_request()


File: python.info,  Node: signal --- Set handlers for asynchronous events,  Next: mmap --- Memory-mapped file support,  Prev: asynchat --- Asynchronous socket command/response handler,  Up: Networking and Interprocess Communication

5.18.8 ‘signal’ — Set handlers for asynchronous events
------------------------------------------------------

__________________________________________________________________

This module provides mechanisms to use signal handlers in Python.

* Menu:

* General rules::
* Module contents: Module contents<2>.
* Example: Example<9>.
* Note on SIGPIPE::


File: python.info,  Node: General rules,  Next: Module contents<2>,  Up: signal --- Set handlers for asynchronous events

5.18.8.1 General rules
......................

The *note signal.signal(): a82. function allows defining custom handlers
to be executed when a signal is received.  A small number of default
handlers are installed: *note SIGPIPE: 2786. is ignored (so write errors
on pipes and sockets can be reported as ordinary Python exceptions) and
*note SIGINT: 24d8. is translated into a *note KeyboardInterrupt: 198.
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: 2787, which follows the underlying implementation.

* 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.8.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: 2789. to execute the corresponding
Python signal handler at a later point(for example at the next *note
bytecode: 619. instruction).  This has consequences:

   * It makes little sense to catch synchronous errors like *note
     SIGFPE: 278a. or *note SIGSEGV: 278b. 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: 7d. 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.


File: python.info,  Node: Signals and threads,  Prev: Execution of Python signal handlers,  Up: General rules

5.18.8.3 Signals and threads
............................

Python signal handlers are always executed in the main Python thread,
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: 10a. module
instead.

Besides, only the main thread is allowed to set a new signal handler.


File: python.info,  Node: Module contents<2>,  Next: Example<9>,  Prev: General rules,  Up: signal --- Set handlers for asynchronous events

5.18.8.4 Module contents
........................

3.5 版更變: signal (SIG*), handler (*note SIG_DFL: 24d9, *note SIG_IGN:
24da.) and sigmask (*note SIG_BLOCK: 278f, *note SIG_UNBLOCK: 2790,
*note SIG_SETMASK: 2791.) related constants listed below were turned
into *note enums: 592.  *note getsignal(): 2792, *note
pthread_sigmask(): a7e, *note sigpending(): a80. and *note sigwait():
a81. functions return human-readable *note enums: 592.

The variables defined in the *note signal: eb. module are:

 -- Data: 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: 2787. is to simply
     ignore it.

 -- Data: signal.SIG_IGN

     This is another standard signal handler, which will simply ignore
     the given signal.

 -- Data: signal.SIGABRT

     Abort signal from ‘abort(3)’.

 -- Data: signal.SIGALRM

     Timer signal from ‘alarm(2)’.

     *note Availability: 1364.: Unix.

 -- Data: signal.SIGBREAK

     Interrupt from keyboard (CTRL + BREAK).

     *note Availability: 1364.: Windows.

 -- Data: signal.SIGBUS

     Bus error (bad memory access).

     *note Availability: 1364.: Unix.

 -- Data: signal.SIGCHLD

     Child process stopped or terminated.

     *note Availability: 1364.: Unix.

 -- Data: signal.SIGCLD

     Alias to *note SIGCHLD: 2787.

 -- Data: signal.SIGCONT

     Continue the process if it is currently stopped

     *note Availability: 1364.: Unix.

 -- Data: signal.SIGFPE

     Floating-point exception.  For example, division by zero.

     也參考
     ......

     *note ZeroDivisionError: 12b2. is raised when the second argument
     of a division or modulo operation is zero.

 -- Data: signal.SIGHUP

     Hangup detected on controlling terminal or death of controlling
     process.

     *note Availability: 1364.: Unix.

 -- Data: signal.SIGILL

     Illegal instruction.

 -- Data: signal.SIGINT

     Interrupt from keyboard (CTRL + C).

     Default action is to raise *note KeyboardInterrupt: 198.

 -- Data: signal.SIGKILL

     Kill signal.

     It cannot be caught, blocked, or ignored.

     *note Availability: 1364.: Unix.

 -- Data: signal.SIGPIPE

     Broken pipe: write to pipe with no readers.

     Default action is to ignore the signal.

     *note Availability: 1364.: Unix.

 -- Data: signal.SIGSEGV

     Segmentation fault: invalid memory reference.

 -- Data: signal.SIGTERM

     Termination signal.

 -- Data: signal.SIGUSR1

     User-defined signal 1.

     *note Availability: 1364.: Unix.

 -- Data: signal.SIGUSR2

     User-defined signal 2.

     *note Availability: 1364.: Unix.

 -- Data: signal.SIGWINCH

     Window resize signal.

     *note Availability: 1364.: Unix.

 -- Data: SIG*

     All the signal numbers are defined symbolically.  For example, the
     hangup signal is defined as *note signal.SIGHUP: 2798.; 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)’, on
     others the list is in ‘signal(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.

 -- Data: signal.CTRL_C_EVENT

     The signal corresponding to the ‘Ctrl+C’ keystroke event.  This
     signal can only be used with *note os.kill(): cf8.

     *note Availability: 1364.: Windows.

     3.2 版新加入.

 -- Data: signal.CTRL_BREAK_EVENT

     The signal corresponding to the ‘Ctrl+Break’ keystroke event.  This
     signal can only be used with *note os.kill(): cf8.

     *note Availability: 1364.: Windows.

     3.2 版新加入.

 -- Data: signal.NSIG

     One more than the number of the highest signal number.

 -- Data: signal.ITIMER_REAL

     Decrements interval timer in real time, and delivers *note SIGALRM:
     2794. upon expiration.

 -- Data: signal.ITIMER_VIRTUAL

     Decrements interval timer only when the process is executing, and
     delivers SIGVTALRM upon expiration.

 -- Data: 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.

 -- Data: signal.SIG_BLOCK

     A possible value for the `how' parameter to *note
     pthread_sigmask(): a7e. indicating that signals are to be blocked.

     3.3 版新加入.

 -- Data: signal.SIG_UNBLOCK

     A possible value for the `how' parameter to *note
     pthread_sigmask(): a7e. indicating that signals are to be
     unblocked.

     3.3 版新加入.

 -- Data: signal.SIG_SETMASK

     A possible value for the `how' parameter to *note
     pthread_sigmask(): a7e. indicating that the signal mask is to be
     replaced.

     3.3 版新加入.

The *note signal: eb. module defines one exception:

 -- 例外: signal.ItimerError

     Raised to signal an error from the underlying *note setitimer():
     27a3. or *note getitimer(): 27a4. implementation.  Expect this
     error if an invalid interval timer or a negative time is passed to
     *note setitimer(): 27a3.  This error is a subtype of *note OSError:
     1d4.

     3.3 版新加入: This error used to be a subtype of *note IOError:
     997, which is now an alias of *note OSError: 1d4.

The *note signal: eb. module defines the following functions:

 -- 函式: signal.alarm (time)

     If `time' is non-zero, this function requests that a *note SIGALRM:
     2794. 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 Availability: 1364.: Unix.  See the man page ‘alarm(2)’ for
     further information.

 -- 函式: 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: 24da, *note signal.SIG_DFL:
     24d9. or *note None: 158.  Here, *note signal.SIG_IGN: 24da. means
     that the signal was previously ignored, *note signal.SIG_DFL: 24d9.
     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)

     Return the system description of the signal `signalnum', such as
     "Interrupt", "Segmentation fault", etc.  Returns *note None: 158.
     if the signal is not recognized.

     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 Availability: 1364.: Unix.  See the man page ‘signal(2)’ for
     further information.

     See also *note sigwait(): a81, *note sigwaitinfo(): 684, *note
     sigtimedwait(): 683. and *note sigpending(): a80.

 -- 函式: signal.raise_signal (signum)

     Sends a signal to the calling process.  Returns nothing.

     3.8 版新加入.

 -- 函式: 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: 278d.  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: 65e.

     Use *note threading.get_ident(): ab4. or the *note ident: 201e.
     attribute of *note threading.Thread: 236. 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.

     Raises an *note auditing event: e96. ‘signal.pthread_kill’ with
     arguments ‘thread_id’, ‘signalnum’.

     *note Availability: 1364.: Unix.  See the man page
     ‘pthread_kill(3)’ for further information.

     See also *note os.kill(): cf8.

     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: 278f.: The set of blocked signals is the
          union of the current set and the `mask' argument.

        * *note SIG_UNBLOCK: 2790.: 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: 2791.: The set of blocked signals is set to
          the `mask' argument.

     `mask' is a set of signal numbers (e.g.  {*note signal.SIGINT:
     24d8, *note signal.SIGTERM: 2574.}).  Use *note valid_signals():
     27a6. 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: 279a. and ‘SIGSTOP’ cannot be blocked.

     *note Availability: 1364.: Unix.  See the man page ‘sigprocmask(3)’
     and ‘pthread_sigmask(3)’ for further information.

     See also *note pause(): 27a7, *note sigpending(): a80. and *note
     sigwait(): a81.

     3.3 版新加入.

 -- 函式: signal.setitimer (which, seconds, interval=0.0)

     Sets given interval timer (one of *note signal.ITIMER_REAL: 279f,
     *note signal.ITIMER_VIRTUAL: 27a0. or *note signal.ITIMER_PROF:
     27a1.) specified by `which' to fire after `seconds' (float is
     accepted, different from *note alarm(): 27a5.) 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: 279f. will deliver *note SIGALRM: 2794, *note
     signal.ITIMER_VIRTUAL: 27a0. sends ‘SIGVTALRM’, and *note
     signal.ITIMER_PROF: 27a1. 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: 27a2.

     *note Availability: 1364.: Unix.

 -- 函式: signal.getitimer (which)

     Returns current value of a given interval timer specified by
     `which'.

     *note Availability: 1364.: 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 the
     main thread; attempting to call it from other threads will cause a
     *note ValueError: 1fc. 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 版更變: Added ‘warn_on_full_buffer’ parameter.

 -- 函式: signal.siginterrupt (signalnum, flag)

     Change system call restart behaviour: if `flag' is *note False:
     38d, system calls will be restarted when interrupted by signal
     `signalnum', otherwise system calls will be interrupted.  Returns
     nothing.

     *note Availability: 1364.: Unix.  See the man page
     ‘siginterrupt(3)’ for further information.

     Note that installing a signal handler with *note signal(): eb. 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: 24da. or
     *note signal.SIG_DFL: 24d9.  The previous signal handler will be
     returned (see the description of *note getsignal(): 2792. above).
     (See the Unix man page ‘signal(2)’ for further information.)

     When threads are enabled, this function can only be called from the
     main thread; attempting to call it from other threads will cause a
     *note ValueError: 1fc. 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: 1437. or see the attribute descriptions in the *note
     inspect: a1. module).

     On Windows, *note signal(): eb. can only be called with *note
     SIGABRT: 2793, *note SIGFPE: 278a, *note SIGILL: 2799, *note
     SIGINT: 24d8, *note SIGSEGV: 278b, *note SIGTERM: 2574, or *note
     SIGBREAK: 2795.  A *note ValueError: 1fc. will be raised in any
     other case.  Note that not all systems define the same set of
     signal names; an *note AttributeError: 3a0. 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 Availability: 1364.: Unix.  See the man page ‘sigpending(2)’
     for further information.

     See also *note pause(): 27a7, *note pthread_sigmask(): a7e. and
     *note sigwait(): a81.

     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 Availability: 1364.: Unix.  See the man page ‘sigwait(3)’ for
     further information.

     See also *note pause(): 27a7, *note pthread_sigmask(): a7e, *note
     sigpending(): a80, *note sigwaitinfo(): 684. and *note
     sigtimedwait(): 683.

     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: 65e. 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 Availability: 1364.: Unix.  See the man page ‘sigwaitinfo(2)’
     for further information.

     See also *note pause(): 27a7, *note sigwait(): a81. and *note
     sigtimedwait(): 683.

     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(1) for the rationale).

 -- 函式: signal.sigtimedwait (sigset, timeout)

     Like *note sigwaitinfo(): 684, but takes an additional `timeout'
     argument specifying a timeout.  If `timeout' is specified as ‘0’, a
     poll is performed.  Returns *note None: 158. if a timeout occurs.

     *note Availability: 1364.: Unix.  See the man page
     ‘sigtimedwait(2)’ for further information.

     See also *note pause(): 27a7, *note sigwait(): a81. and *note
     sigwaitinfo(): 684.

     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(2) for the
     rationale).

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0475

   (2) https://www.python.org/dev/peps/pep-0475


File: python.info,  Node: Example<9>,  Next: Note on SIGPIPE,  Prev: Module contents<2>,  Up: signal --- Set handlers for asynchronous events

5.18.8.5 Example
................

Here is a minimal example program.  It uses the *note alarm(): 27a5.
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(): 66a. 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):
         print('Signal handler called with signal', 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,  Prev: Example<9>,  Up: signal --- Set handlers for asynchronous events

5.18.8.6 Note on SIGPIPE
........................

Piping output of your program to tools like ‘head(1)’ will cause a *note
SIGPIPE: 2786. 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: 2786.’s disposition to *note SIG_DFL: 24d9. in
order to avoid *note BrokenPipeError: 9a2.  Doing that would cause your
program to exit unexpectedly also whenever any socket connection is
interrupted while your program is still writing to it.


File: python.info,  Node: mmap --- Memory-mapped file support,  Prev: signal --- Set handlers for asynchronous events,  Up: Networking and Interprocess Communication

5.18.9 ‘mmap’ — Memory-mapped file support
------------------------------------------

__________________________________________________________________

Memory-mapped file objects behave like both *note bytearray: 337. and
like *note file objects: b47.  You can use mmap objects in most places
where *note bytearray: 337. are expected; for example, you can use the
*note re: de. 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: 1ed. 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 ‘fileno()’ method to obtain
the correct value for the `fileno' parameter.  Otherwise, you can open
the file using the *note os.open(): 66a. 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(): 1ff2. 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: 193. 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 版更變: Added ‘ACCESS_DEFAULT’ constant.

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])

     `(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 tag 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’.

     Raises an *note auditing event: e96. ‘mmap.__new__’ with arguments
     ‘fileno’, ‘length’, ‘access’, ‘offset’.

 -- 類別: mmap.mmap (fileno, length, flags=MAP_SHARED,
          prot=PROT_WRITE|PROT_READ, access=ACCESS_DEFAULT[, offset])

     `(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: 1ed. is called.

     `flags' specifies the nature of the mapping.  ‘MAP_PRIVATE’ creates
     a private copy-on-write mapping, so changes to the contents of the
     mmap object will be private to this process, and ‘MAP_SHARED’
     creates a mapping that’s shared with all other processes mapping
     the same areas of the file.  The default value is ‘MAP_SHARED’.

     `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.

     To ensure validity of the created memory mapping the file specified
     by the descriptor `fileno' is internally automatically synchronized
     with physical backing store on Mac OS X and OpenVMS.

     This example shows a simple way of using *note mmap: 1ed.:

          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: 1ed. can also be used as a context manager in a *note
     with: 6ee. 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:  # In a child process
              mm.seek(0)
              print(mm.readline())

              mm.close()

     Raises an *note auditing event: e96. ‘mmap.__new__’ with arguments
     ‘fileno’, ‘length’, ‘access’, ‘offset’.

     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: 5ed. 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: 27b1. 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: 193. exception.

      -- 成員函式: read ([n])

          Return a *note bytes: 336. 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.

      -- 成員函式: resize (newsize)

          Resizes the map and the underlying file, if any.  If the mmap
          was created with ‘ACCESS_READ’ or ‘ACCESS_COPY’, resizing the
          map will raise a *note TypeError: 193. exception.

      -- 成員函式: 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: 5ed. 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).

      -- 成員函式: 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: 1fc. 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: 193. exception.

          3.5 版更變: Writable *note bytes-like object: 5ed. 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: 193. exception.

* Menu:

* MADV_* Constants::


File: python.info,  Node: MADV_* Constants,  Up: mmap --- Memory-mapped file support

5.18.9.1 MADV_* Constants
.........................

 -- Data: mmap.MADV_NORMAL
 -- Data: mmap.MADV_RANDOM
 -- Data: mmap.MADV_SEQUENTIAL
 -- Data: mmap.MADV_WILLNEED
 -- Data: mmap.MADV_DONTNEED
 -- Data: mmap.MADV_REMOVE
 -- Data: mmap.MADV_DONTFORK
 -- Data: mmap.MADV_DOFORK
 -- Data: mmap.MADV_HWPOISON
 -- Data: mmap.MADV_MERGEABLE
 -- Data: mmap.MADV_UNMERGEABLE
 -- Data: mmap.MADV_SOFT_OFFLINE
 -- Data: mmap.MADV_HUGEPAGE
 -- Data: mmap.MADV_NOHUGEPAGE
 -- Data: mmap.MADV_DONTDUMP
 -- Data: mmap.MADV_DODUMP
 -- Data: mmap.MADV_FREE
 -- Data: mmap.MADV_NOSYNC
 -- Data: mmap.MADV_AUTOSYNC
 -- Data: mmap.MADV_NOCORE
 -- Data: mmap.MADV_CORE
 -- Data: mmap.MADV_PROTECT

     These options can be passed to *note mmap.madvise(): 1ee.  Not
     every option will be present on every system.

     Availability: Systems with the madvise() system call.

     3.8 版新加入.


File: python.info,  Node: Internet Data Handling,  Next: Structured Markup Processing Tools,  Prev: Networking and Interprocess Communication,  Up: Python 標準函式庫 Standard Library

5.19 Internet Data Handling
===========================

This chapter describes modules which support handling data formats
commonly used on the Internet.

* Menu:

* email: email --- An email and MIME handling package. An email and MIME handling package
* json: json --- JSON encoder and decoder. JSON encoder and decoder
* mailcap: mailcap --- Mailcap file handling. Mailcap file handling
* mailbox: mailbox --- Manipulate mailboxes in various formats. Manipulate mailboxes in various formats
* mimetypes: mimetypes --- Map filenames to MIME types. Map filenames to MIME types
* base64 —— Base16、Base32、Base64、Base85 資料編碼::
* binhex: binhex --- Encode and decode binhex4 files. Encode and decode binhex4 files
* binascii: binascii --- Convert between binary and ASCII. Convert between binary and ASCII
* quopri: quopri --- Encode and decode MIME quoted-printable data. Encode and decode MIME quoted-printable data
* uu: uu --- Encode and decode uuencode files. Encode and decode uuencode files


File: python.info,  Node: email --- An email and MIME handling package,  Next: json --- JSON encoder and decoder,  Up: Internet Data Handling

5.19.1 ‘email’ — An email and MIME handling package
---------------------------------------------------

`Source code:' Lib/email/__init__.py(1)

__________________________________________________________________

The *note email: 69. 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: ee. and *note nntplib: c1.  The *note
email: 69. 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: 72. 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: 547. API.

The other two major components of the package are the *note parser: 74.
and the *note generator: 6e.  The parser takes the serialized version of
an email message (a stream of bytes) and converts it into a tree of
*note EmailMessage: 547. objects.  The generator takes an *note
EmailMessage: 547. 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: 75. module.  Every *note
EmailMessage: 547, every *note generator: 6e, and every *note parser:
74. has an associated *note policy: 75. object that controls its
behavior.  Usually an application only needs to specify the policy when
an *note EmailMessage: 547. is created, either by directly instantiating
an *note EmailMessage: 547. to create a new email, or by parsing an
input stream using a *note parser: 74.  But the policy can be changed
when the message is serialized using a *note generator: 6e.  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:
69. package.  We start with the *note message: 72. object model, which
is the primary interface an application will use, and follow that with
the *note parser: 74. and *note generator: 6e. components.  Then we
cover the *note policy: 75. 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: 74.
may detect.  Then we cover the *note headerregistry: 70. and the *note
contentmanager: 6b. 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: 546.
class, cover the legacy *note compat32: 545. API that deals much more
directly with the details of how email messages are represented.  The
*note compat32: 545. 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: 545. API for
backward compatibility reasons.

3.6 版更變: Docs reorganized and rewritten to promote the new *note
EmailMessage: 547./*note EmailPolicy: 9fd. API.

Contents of the *note email: 69. package documentation:

* Menu:

* email.message; Representing an email message: email message Representing an email message.
* email.parser; Parsing email messages: email parser Parsing email messages.
* email.generator; Generating MIME documents: email generator Generating MIME documents.
* email.policy; Policy Objects: email policy Policy Objects.
* email.errors; Exception and Defect classes: email errors Exception and Defect classes.
* email.headerregistry; Custom Header Objects: email headerregistry Custom Header Objects.
* email.contentmanager; Managing MIME Content: email contentmanager Managing MIME Content.
* email; Examples: email Examples.
* email.message.Message; Representing an email message using the compat32 API: email message Message Representing an email message using the compat32 API.
* email.mime; Creating email and MIME objects from scratch: email mime Creating email and MIME objects from scratch.
* email.header; Internationalized headers: email header Internationalized headers.
* email.charset; Representing character sets: email charset Representing character sets.
* email.encoders; Encoders: email encoders Encoders.
* email.utils; Miscellaneous utilities: email utils Miscellaneous utilities.
* email.iterators; Iterators: email iterators Iterators.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/email/__init__.py

   (2) https://tools.ietf.org/html/rfc2821.html

   (3) https://tools.ietf.org/html/rfc5322.html

   (4) https://tools.ietf.org/html/rfc6532.html

   (5) https://tools.ietf.org/html/rfc2045.html

   (6) https://tools.ietf.org/html/rfc2046.html

   (7) https://tools.ietf.org/html/rfc2047.html

   (8) https://tools.ietf.org/html/rfc2183.html

   (9) https://tools.ietf.org/html/rfc2231.html


File: python.info,  Node: email message Representing an email message,  Next: email parser Parsing email messages,  Up: email --- An email and MIME handling package

5.19.1.1 ‘email.message’: Representing an email message
.......................................................

`Source code:' Lib/email/message.py(1)

__________________________________________________________________

3.6 版新加入: (2)

The central class in the *note email: 69. package is the *note
EmailMessage: 547. class, imported from the *note email.message: 72.
module.  It is the base class for the *note email: 69. object model.
*note EmailMessage: 547. 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: 547. 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: 547. 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.
Unlike a real dict, there is an ordering to the keys, and there can be
duplicate keys.  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: 547. 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: 27db. 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: 75. 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: 546. class
          `maxheaderlen' is accepted, but defaults to ‘None’, which
          means that by default the line length is controlled by the
          ‘max_line_length’ 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: b51.

          Flattening the message may trigger changes to the *note
          EmailMessage: 547. 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: b51. 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: 6d7. 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(): 27dc.

      -- 成員函式: 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: b52.

          Flattening the message may trigger changes to the *note
          EmailMessage: 547. 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: b52. for
          a more flexible API for serializing messages.

      -- 成員函式: __bytes__ ()

          Equivalent to *note as_bytes(): 27de.  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: 547. objects, otherwise return ‘False’.  When
          *note is_multipart(): 27e0. returns ‘False’, the payload
          should be a string object (which might be a CTE encoded binary
          payload).  Note that *note is_multipart(): 27e0. 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: 547. is of type ‘message/rfc822’.

      -- 成員函式: set_unixfrom (unixfrom)

          Set the message’s envelope header to `unixfrom', which should
          be a string.  (See *note mboxMessage: 27e2. 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(): 27e4, but in an *note EmailMessage: 547.
     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: 2c8. 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(): 27e8. 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: 27e9.

      -- 成員函式: __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 ‘policy’ defines certain headers to be unique (as the
          standard policies do), this method may raise a *note
          ValueError: 1fc. 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__(): 27e7. 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__(): 27ea. 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’.

          Here is an example:

               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: 2c8.

      -- 成員函式: 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(): 27f2.  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(): 27f1. 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(): 27f1.

      -- 成員函式: get_content_subtype ()

          Return the message’s sub-content type.  This is the ‘subtype’
          part of the string returned by *note get_content_type(): 27f1.

      -- 成員函式: 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: 547.
          objects is deprecated.

          Note that existing parameter values of headers may be accessed
          through the ‘params’ 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: 547.
          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(): 27f9.

      -- 成員函式: 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(): 27f9.

      -- 成員函式: set_boundary (boundary)

          Set the ‘boundary’ parameter of the ‘Content-Type’ header to
          `boundary'.  *note set_boundary(): 27fb. will always quote
          `boundary' if necessary.  A *note HeaderParseError: 27fc. 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(): 27ef, because *note
          set_boundary(): 27fb. 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(): 2800.

      -- 成員函式: 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(): 2802. 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(): 2802. 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(): 27e0. 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(): 2802.)

      -- 成員函式: get_content (*args, content_manager=None, **kw)

          Call the *note get_content(): 2807. 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: 75.

      -- 成員函式: set_content (*args, content_manager=None, **kw)

          Call the *note set_content(): 2809. 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: 75.

      -- 成員函式: 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():
          2808. method, and *note attach(): 280e. it to the ‘multipart’.
          If the message is a non-‘multipart’, call *note
          make_related(): 280a. and then proceed as above.  If the
          message is any other type of ‘multipart’, raise a *note
          TypeError: 193.  If `content_manager' is not specified, use
          the ‘content_manager’ specified by the current *note policy:
          75.  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(): 2808. method, and *note attach(): 280e. it to
          the ‘multipart’.  If the message is a non-‘multipart’ or
          ‘multipart/related’, call *note make_alternative(): 280b. and
          then proceed as above.  If the message is any other type of
          ‘multipart’, raise a *note TypeError: 193.  If
          `content_manager' is not specified, use the ‘content_manager’
          specified by the current *note policy: 75.

      -- 成員函式: 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():
          2808. method, and *note attach(): 280e. it to the ‘multipart’.
          If the message is a non-‘multipart’, ‘multipart/related’, or
          ‘multipart/alternative’, call *note make_mixed(): 280c. and
          then proceed as above.  If `content_manager' is not specified,
          use the ‘content_manager’ specified by the current *note
          policy: 75.  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: 547. 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: b1d.
          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: b51. 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: 74. and *note
          email.generator: 6e. 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: 2813, 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: 6d.
          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: 547, except that no ‘MIME-Version’ headers
     are added when *note set_content(): 2808. is called, since
     sub-parts do not need their own ‘MIME-Version’ headers.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/email/message.py

   (2) (1) Originally added in 3.4 as a *note provisional module: 985.
Docs for legacy message class moved to *note email.message.Message;
Representing an email message using the compat32 API: 27da.

   (3) https://tools.ietf.org/html/rfc5322.html

   (4) https://tools.ietf.org/html/rfc6532.html

   (5) https://tools.ietf.org/html/rfc5322.html

   (6) https://tools.ietf.org/html/rfc6531.html

   (7) https://tools.ietf.org/html/rfc2231.html

   (8) https://tools.ietf.org/html/rfc2231.html

   (9) https://tools.ietf.org/html/rfc2045.html

   (10) https://tools.ietf.org/html/rfc2045.html

   (11) https://tools.ietf.org/html/rfc2045.html

   (12) https://tools.ietf.org/html/rfc2231.html

   (13) https://tools.ietf.org/html/rfc2183.html


File: python.info,  Node: email parser Parsing email messages,  Next: email generator Generating MIME documents,  Prev: email message Representing an email message,  Up: email --- An email and MIME handling package

5.19.1.2 ‘email.parser’: Parsing email messages
...............................................

`Source code:' 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: 547. object,
adding headers using the dictionary interface, and adding payload(s)
using *note set_content(): 2808. and related methods, or they can be
created by parsing a serialized representation of the email message.

The *note email: 69. 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: 547. 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(): 27e0. method, and the subparts can be accessed via the
payload manipulation methods, such as *note get_body(): 2803, *note
iter_parts(): 2805, and *note walk(): 2802.

There are actually two parser interfaces available for use, the *note
Parser: b1d. API and the incremental *note FeedParser: 2818. API. The
*note Parser: b1d. 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: 2818. 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: 2818. 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: 69. package’s bundled parser and the
*note EmailMessage: 547. class is embodied in the ‘policy’ 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.8/Lib/email/parser.py


File: python.info,  Node: FeedParser API,  Next: Parser API,  Up: email parser Parsing email messages

5.19.1.3 FeedParser API
.......................

The *note BytesFeedParser: b4e, 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: b4e. can of course be used to parse an email
message fully contained in a *note bytes-like object: 5ed, string, or
file, but the *note BytesParser: b4f. API may be more convenient for
such use cases.  The semantics and results of the two parser APIs are
identical.

The *note BytesFeedParser: b4e.’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: b4e. 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: 2815.
attribute with a list of any problems it found in a message.  See the
*note email.errors: 6d. module for the list of defects that it can find.

Here is the API for the *note BytesFeedParser: b4e.:

 -- 類別: email.parser.BytesFeedParser (_factory=None, *,
          policy=policy.compat32)

     Create a *note BytesFeedParser: b4e. instance.  Optional `_factory'
     is a no-argument callable; if not specified use the *note
     message_factory: 544. 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: 9fa. policy, which maintains backward compatibility
     with the Python 3.2 version of the email package and provides *note
     Message: 546. as the default factory.  All other policies provide
     *note EmailMessage: 547. as the default `_factory'.  For more
     information on what else `policy' controls, see the *note policy:
     75. documentation.

     Note: `The policy keyword should always be specified'; The default
     will change to *note email.policy.default: 27db. in a future
     version of Python.

     3.2 版新加入.

     3.3 版更變: Added the `policy' keyword.

     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: 5ed. 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(): 281a. is called after this method has been called.

 -- 類別: email.parser.FeedParser (_factory=None, *,
          policy=policy.compat32)

     Works like *note BytesFeedParser: b4e. except that the input to the
     *note feed(): 281a. 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 版更變: Added the `policy' keyword.


File: python.info,  Node: Parser API,  Next: Additional notes,  Prev: FeedParser API,  Up: email parser Parsing email messages

5.19.1.4 Parser API
...................

The *note BytesParser: b4f. class, imported from the *note email.parser:
74. 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: 5ed. or file.  The *note email.parser: 74. module also provides
*note Parser: b1d. for parsing strings, and header-only parsers, *note
BytesHeaderParser: a01. and *note HeaderParser: a02, which can be used
if you’re only interested in the headers of the message.  *note
BytesHeaderParser: a01. and *note HeaderParser: a02. 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: b4f. instance.  The `_class' and
     `policy' arguments have the same meaning and semantics as the
     `_factory' and `policy' arguments of *note BytesFeedParser: b4e.

     Note: `The policy keyword should always be specified'; The default
     will change to *note email.policy.default: 27db. 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(): 1708. 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(): 281d. method, except it takes a
          *note bytes-like object: 5ed. instead of a file-like object.
          Calling this method on a *note bytes-like object: 5ed. is
          equivalent to wrapping `bytes' in a *note BytesIO: 7a0.
          instance first and calling *note parse(): 281d.

          Optional `headersonly' is as with the *note parse(): 281d.
          method.

     3.2 版新加入.

 -- 類別: email.parser.BytesHeaderParser (_class=None, *,
          policy=policy.compat32)

     Exactly like *note BytesParser: b4f, except that `headersonly'
     defaults to ‘True’.

     3.3 版新加入.

 -- 類別: email.parser.Parser (_class=None, *, policy=policy.compat32)

     This class is parallel to *note BytesParser: b4f, 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(): 1c03. and the
          *note read(): 200b. methods on file-like objects.

          Other than the text mode requirement, this method operates
          like *note BytesParser.parse(): 281d.

      -- 成員函式: parsestr (text, headersonly=False)

          Similar to the *note parse(): 281f. 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: 832. instance first and calling *note parse(): 281f.

          Optional `headersonly' is as with the *note parse(): 281f.
          method.

 -- 類別: email.parser.HeaderParser (_class=None, *,
          policy=policy.compat32)

     Exactly like *note Parser: b1d, 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: 69. package namespace.

 -- 函式: email.message_from_bytes (s, _class=None, *,
          policy=policy.compat32)

     Return a message object structure from a *note bytes-like object:
     5ed.  This is equivalent to ‘BytesParser().parsebytes(s)’.
     Optional `_class' and `policy' are interpreted as with the *note
     BytesParser: b4f. 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: b47.  This is equivalent to ‘BytesParser().parse(fp)’.
     `_class' and `policy' are interpreted as with the *note
     BytesParser: b4f. 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: b1d. 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: b47.  This is equivalent to ‘Parser().parse(fp)’.  `_class'
     and `policy' are interpreted as with the *note Parser: b1d. 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(): b4c.
at an interactive Python prompt:

     >>> import email
     >>> msg = email.message_from_bytes(myBytes)

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc5322.html

   (2) https://tools.ietf.org/html/rfc6532.html


File: python.info,  Node: Additional notes,  Prev: Parser API,  Up: email parser Parsing email messages

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(): 27e0, and *note iter_parts(): 2805. 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(): 27e0, and *note iter_parts(): 2805. 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(): 27e0. method will return ‘True’.  The single
     element yielded by *note iter_parts(): 2805. 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(): 27e0. method may return ‘False’.  If such messages
     were parsed with the *note FeedParser: 2818, they will have an
     instance of the ‘MultipartInvariantViolationDefect’ class in their
     `defects' attribute list.  See *note email.errors: 6d. for details.


File: python.info,  Node: email generator Generating MIME documents,  Next: email policy Policy Objects,  Prev: email parser Parsing email messages,  Up: email --- An email and MIME handling package

5.19.1.6 ‘email.generator’: Generating MIME documents
.....................................................

`Source code:' 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(): 749. or the *note nntplib: c1. module, 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: 74. 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: 75. is used for both.  That is, parsing
the serialized byte stream via the *note BytesParser: b4f. class and
then regenerating the serialized byte stream using *note BytesGenerator:
b52. should produce output identical to the input (2).  (On the other
hand, using the generator on an *note EmailMessage: 547. constructed by
program may result in changes to the *note EmailMessage: 547. object as
defaults are filled in.)

The *note Generator: b51. 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: b51. 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: b52. object that will write any
     message provided to the *note flatten(): 2826. method, or any
     surrogateescape encoded text provided to the *note write(): 2827.
     method, to the *note file-like object: 1c6f. `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_:
     6d5. setting of the `policy' (which is ‘True’ for the *note
     compat32: 545. policy and ‘False’ for all others).  `mangle_from_'
     is intended for use when messages are stored in unix mbox format
     (see *note mailbox: af. 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: 546. or *note EmailMessage: 547.
     object passed to ‘flatten’ to control the message generation.  See
     *note email.policy: 75. for details on what `policy' controls.

     3.2 版新加入.

     3.3 版更變: Added the `policy' keyword.

     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: b52. instance was created.

          If the *note policy: 75. option *note cte_type: 2828. 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: af.)
          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: b52.
          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: b52.’s
          constructor.

As a convenience, *note EmailMessage: 547. provides the methods *note
as_bytes(): 27de. and ‘bytes(aMessage)’ (a.k.a.  *note __bytes__():
27df.), which simplify the generation of a serialized binary
representation of a message object.  For more detail, see *note
email.message: 72.

Because strings cannot represent binary data, the *note Generator: b51.
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: b51. serializing to an I/O
stream that is not "8 bit clean".  In other words, most applications
will want to be using *note BytesGenerator: b52, and not *note
Generator: b51.

 -- 類別: email.generator.Generator (outfp, mangle_from_=None,
          maxheaderlen=None, *, policy=None)

     Return a *note Generator: b51. object that will write any message
     provided to the *note flatten(): 282a. method, or any text provided
     to the *note write(): 282b. method, to the *note file-like object:
     1c6f. `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_:
     6d5. setting of the `policy' (which is ‘True’ for the *note
     compat32: 545. policy and ‘False’ for all others).  `mangle_from_'
     is intended for use when messages are stored in unix mbox format
     (see *note mailbox: af. 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: 546. or *note EmailMessage: 547.
     object passed to ‘flatten’ to control the message generation.  See
     *note email.policy: 75. for details on what `policy' controls.

     3.3 版更變: Added the `policy' keyword.

     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: b51. instance was created.

          If the *note policy: 75. option *note cte_type: 2828. 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: af.)
          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: b51.
          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: b51.’s constructor.  This provides just
          enough file-like API for *note Generator: b51. instances to be
          used in the *note print(): 88b. function.

As a convenience, *note EmailMessage: 547. provides the methods *note
as_string(): 27dc. and ‘str(aMessage)’ (a.k.a.  *note __str__(): 27dd.),
which simplify the generation of a formatted string representation of a
message object.  For more detail, see *note email.message: 72.

The *note email.generator: 6e. module also provides a derived class,
*note DecodedGenerator: 543, which is like the *note Generator: b51.
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: b51, except that for any subpart of the
     message passed to *note Generator.flatten(): 282a, 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: b51. base class.

註解
....

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/email/generator.py

   (2) (1) This statement assumes that you use the appropriate setting
for ‘unixfrom’, and that there are no ‘policy’ settings calling for
automatic adjustments (for example, ‘refold_source’ 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://tools.ietf.org/html/rfc5322.html

   (5) https://www.jwz.org/doc/content-length.html

   (6) https://tools.ietf.org/html/rfc5322.html


File: python.info,  Node: email policy Policy Objects,  Next: email errors Exception and Defect classes,  Prev: email generator Generating MIME documents,  Up: email --- An email and MIME handling package

5.19.1.7 ‘email.policy’: Policy Objects
.......................................

3.3 版新加入.

`Source code:' Lib/email/policy.py(1)

__________________________________________________________________

The *note email: 69. 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: 9f9. object encapsulates a set of attributes and methods
that control the behavior of various components of the email package
during use.  *note Policy: 9f9. 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: 74. classes and the related convenience
functions, and for the *note Message: 546. class, this is the *note
Compat32: 9fa. policy, via its corresponding pre-defined instance *note
compat32: 545.  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: 547.
is the *note EmailPolicy: 9fd. policy, via its pre-defined instance
*note default: 27db.

When a *note Message: 546. or *note EmailMessage: 547. object is
created, it acquires a policy.  If the message is created by a *note
parser: 74, 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: 6e, 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:
74. 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: 74. module.

The first part of this documentation covers the features of *note
Policy: 9f9, an *note abstract base class: b38. that defines the
features that are common to all policy objects, including *note
compat32: 545.  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: 9fd. and *note Compat32: 9fa, which implement
the hooks that provide the standard behavior and the backward compatible
behavior and features, respectively.

*note Policy: 9f9. instances are immutable, but they can be cloned,
accepting the same keyword arguments as the class constructor and
returning a new *note Policy: 9f9. 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: b52. 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(): 845. 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: b38. 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(): 9fb. 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: 158. 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(): 2831. and *note utf8: 6d7. 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: 49e, any defects encountered will be raised as
          errors.  If *note False: 38d. (the default), defects will be
          passed to the *note register_defect(): 2833. method.

      -- 屬性: mangle_from_

          If *note True: 49e, 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: 38d.

          3.5 版新加入: The `mangle_from_' parameter.

      -- 屬性: 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: 546. is used.

          3.6 版新加入.

     The following *note Policy: 9f9. 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: 9f9. 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: 9f9. 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:
          2832. 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(): 2833.

      -- 成員函式: 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: 2834, `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: 547.
          or *note Message: 546. 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: 1fc. 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: 2830. 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(): 2839, 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: 9f9. 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: 544. attribute is
     *note EmailMessage: 547.

     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: 74. (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.
                       

          The default is ‘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: 70.) 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(): 2806. or *note
          set_content(): 2808. method of an *note EmailMessage: 547.
          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: 283c.

          3.4 版新加入.

     The class provides the following concrete implementations of the
     abstract methods of *note Policy: 9f9.:

      -- 成員函式: header_max_count (name)

          Returns the value of the *note max_count: 283e. 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: 283a.
          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():
          165e.  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(): 2842. if *note cte_type: 2828. is
          ‘7bit’, except that the returned value is bytes.

          If *note cte_type: 2828. 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: 9fd. 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.

 -- Data: 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’.

 -- Data: 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.

 -- Data: email.policy.SMTPUTF8

     The same as ‘SMTP’ except that *note utf8: 6d7. 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(): 74a. method handles this
     automatically).

 -- Data: 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).

 -- Data: 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: 9fd, 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: 546. results in that
          header being parsed and a header object created.

        * Fetching a header value from a *note Message: 546. 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: 547. 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: 70.

 -- 類別: email.policy.Compat32 (**kw)

     This concrete *note Policy: 9f9. is the backward compatibility
     policy.  It replicates the behavior of the email package in Python
     3.2.  The *note policy: 75. module also defines an instance of this
     class, *note compat32: 545, 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: 9f9. default:

      -- 屬性: mangle_from_

          The default is ‘True’.

     The class provides the following concrete implementations of the
     abstract methods of *note Policy: 9f9.:

      -- 成員函式: 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: 284c. object using the ‘unknown-8bit’ charset.
          Otherwise it is returned unmodified.

      -- 成員函式: fold (name, value)

          Headers are folded using the *note Header: 284c. 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: 284c. 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.

 -- Data: email.policy.compat32

     An instance of *note Compat32: 9fa, providing backward
     compatibility with the behavior of the email package in Python 3.2.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/email/policy.py

   (2) https://tools.ietf.org/html/rfc5322.html

   (3) https://tools.ietf.org/html/rfc5322.html

   (4) https://tools.ietf.org/html/rfc5322.html

   (5) https://tools.ietf.org/html/rfc2047.html

   (6) https://tools.ietf.org/html/rfc2047.html

   (7) https://tools.ietf.org/html/rfc5322.html

   (8) (1) Originally added in 3.3 as a *note provisional feature: 985.

   (9) https://tools.ietf.org/html/rfc5322.html

   (10) https://tools.ietf.org/html/rfc6532.html

   (11) https://tools.ietf.org/html/rfc6531.html

   (12) https://tools.ietf.org/html/rfc5322.html


File: python.info,  Node: email errors Exception and Defect classes,  Next: email headerregistry Custom Header Objects,  Prev: email policy Policy Objects,  Up: email --- An email and MIME handling package

5.19.1.8 ‘email.errors’: Exception and Defect classes
.....................................................

`Source code:' Lib/email/errors.py(1)

__________________________________________________________________

The following exception classes are defined in the *note email.errors:
6d. module:

 -- 例外: email.errors.MessageError

     This is the base class for all exceptions that the *note email: 69.
     package can raise.  It is derived from the standard *note
     Exception: 1aa. class and defines no additional methods.

 -- 例外: email.errors.MessageParseError

     This is the base class for exceptions raised by the *note Parser:
     b1d. class.  It is derived from *note MessageError: 2851.  This
     class is also used internally by the parser used by *note
     headerregistry: 70.

 -- 例外: 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: 2852.  The *note set_boundary(): 27fb. method
     will raise this error if the content type is unknown when the
     method is called.  *note Header: 284c. 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: 546. 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: 2854. multiply inherits
     from *note MessageError: 2851. and the built-in *note TypeError:
     193.

     Since ‘Message.add_payload()’ is deprecated, this exception is
     rarely raised in practice.  However the exception may also be
     raised if the *note attach(): 280e. method is called on an instance
     of a class derived from *note MIMENonMultipart: 2855. (e.g.  *note
     MIMEImage: 2856.).

Here is the list of the defects that the *note FeedParser: 2818. 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 ‘email.errors.MessageDefect’.

   * ‘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(): 2800. 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.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/email/errors.py

   (2) https://tools.ietf.org/html/rfc5322.html


File: python.info,  Node: email headerregistry Custom Header Objects,  Next: email contentmanager Managing MIME Content,  Prev: email errors Exception and Defect classes,  Up: email --- An email and MIME handling package

5.19.1.9 ‘email.headerregistry’: Custom Header Objects
......................................................

`Source code:' Lib/email/headerregistry.py(1)

__________________________________________________________________

3.6 版新加入: (2)

Headers are represented by customized subclasses of *note str: 335.  The
particular class used to represent a given header is determined by the
*note header_factory: 283b. of the *note policy: 75. 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:
9fd, all headers are produced by *note HeaderRegistry: 2859. and have
*note BaseHeader: 27e9. 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: 285a.
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: 2859.  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: 2859, 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: 283b. 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: 283b. call for `name'; that is, case is
          preserved.

      -- 屬性: defects

          A tuple of ‘HeaderDefect’ instances reporting any RFC
          compliance problems found during parsing.  The email package
          tries to be complete about detecting compliance issues.  See
          the *note errors: 6d. 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: 2830. characters as
          required to correctly fold the header according to `policy'.
          A *note cte_type: 2828. of ‘8bit’ will be treated as if it
          were ‘7bit’, since headers may not contain arbitrary binary
          data.  If *note utf8: 6d7. 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():
     1d9. 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:
          195. 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: 285f. will be a naive *note datetime: 195.  If
          a specific timezone offset is found (including ‘+0000’), then
          *note datetime: 285f. will contain an aware ‘datetime’ that
          uses *note datetime.timezone: a06. 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: 195.
     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(): a05. function
     from the *note utils: 76. 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: 2862. 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: 2863. is ‘None’.

      -- 屬性: addresses

          A tuple of *note Address: 2865. 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: 77. encoded domain names are also
     decoded to unicode.  The ‘decoded’ value is set by *note join:
     1637.ing the *note str: 335. value of the elements of the ‘groups’
     attribute with ‘', '’.

     A list of *note Address: 2865. and *note Group: 2862. 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: 2860. 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: 75.),
          accessing this attribute will result in a *note ValueError:
          1fc.

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: 283e. 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: 286c. 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: 286c. 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: 9fd. 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: 2865. 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.8/Lib/email/headerregistry.py

   (2) (1) Originally added in 3.3 as a *note provisional module: 985.

   (3) https://tools.ietf.org/html/rfc5322.html

   (4) https://tools.ietf.org/html/rfc2047.html

   (5) https://tools.ietf.org/html/rfc5322.html

   (6) https://tools.ietf.org/html/rfc5322.html

   (7) https://tools.ietf.org/html/rfc2047.html

   (8) https://tools.ietf.org/html/rfc5322.html

   (9) https://tools.ietf.org/html/rfc2047.html

   (10) https://tools.ietf.org/html/rfc5322.html

   (11) https://tools.ietf.org/html/rfc5322.html

   (12) https://tools.ietf.org/html/rfc2045.html

   (13) https://tools.ietf.org/html/rfc2045.html

   (14) https://tools.ietf.org/html/rfc5322.html

   (15) https://tools.ietf.org/html/rfc5322.html

   (16) https://tools.ietf.org/html/rfc5321.html

   (17) https://tools.ietf.org/html/rfc5322.html


File: python.info,  Node: email contentmanager Managing MIME Content,  Next: email Examples,  Prev: email headerregistry Custom Header Objects,  Up: email --- An email and MIME handling package

5.19.1.10 ‘email.contentmanager’: Managing MIME Content
.......................................................

`Source code:' 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: 2c8. for the full MIME type.

      -- 成員函式: set_content (msg, obj, *args, **kw)

          If the ‘maintype’ is ‘multipart’, raise a *note TypeError:
          193.; otherwise look up a handler function based on the type
          of `obj' (see next paragraph), call *note clear_content():
          2812. 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: 2883. (‘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: 2c8. for the fully qualified name of the
          type.

          Also add a ‘MIME-Version’ header if one is not present (see
          also *note MIMEPart: 848.).

      -- 成員函式: add_get_handler (key, handler)

          Record the function `handler' as the handler for `key'.  For
          the possible values of `key', see *note get_content(): 2885.

      -- 成員函式: 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():
          2887.  For the possible values of `typekey', see *note
          set_content(): 2887.

* Menu:

* Content Manager Instances::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/email/contentmanager.py

   (2) (1) Originally added in 3.4 as a *note provisional module: 985.


File: python.info,  Node: Content Manager Instances,  Up: email contentmanager Managing MIME Content

5.19.1.11 Content Manager Instances
...................................

Currently the email package provides only one concrete content manager,
*note raw_data_manager: 283c, although more may be added in the future.
*note raw_data_manager: 283c. is the *note content_manager: 849.
provided by *note EmailPolicy: 9fd. and its derivatives.

 -- Data: email.contentmanager.raw_data_manager

     This content manager provides only a minimum interface beyond that
     provided by *note Message: 546. itself: it deals only with text,
     raw byte strings, and *note Message: 546. 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: 547. object (for
          ‘message/rfc822’ parts), or a ‘bytes’ object (for all other
          non-multipart types).  Raise a *note KeyError: 2c8. 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: 193. if they
                    are not specified.

                  * For *note EmailMessage: 547. 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: 1fc.

                  * For ‘str’ objects, if `cte' is not set use
                    heuristics to determine the most compact encoding.

                  * For *note EmailMessage: 547, 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: b52.
               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://tools.ietf.org/html/rfc2046.html


File: python.info,  Node: email Examples,  Next: email message Message Representing an email message using the compat32 API,  Prev: email contentmanager Managing MIME Content,  Up: email --- An email and MIME handling package

5.19.1.12 ‘email’: Examples
...........................

Here are a few examples of how to use the *note email: 69. 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: 74. module:

     # Import the email modules we'll need
     from email.parser import BytesParser, 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

     # And imghdr to find the types of our images
     import imghdr

     # 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.  Use imghdr to figure out the
     # MIME subtype for each specific image.
     for file in pngfiles:
         with open(file, 'rb') as fp:
             img_data = fp.read()
         msg.add_attachment(img_data, maintype='image',
                                      subtype=imghdr.what(None, img_data))

     # 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_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'] = "Ayons asperges pour le déjeuner"
     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!

     Cela ressemble à un excellent recipie[1] déjeuner.

     [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>Cela ressemble à un excellent
             <a href="http://www.yummly.com/recipe/Roasted-Asparagus-Epicurious-203718">
                 recipie
             </a> déjeuner.
         </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

     # An imaginary module that would make this work and be safe.
     from imaginary import magic_html_parser

     # 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:
         # The magic_html_parser has to rewrite the href="cid:...." attributes to
         # point to the filenames in partfiles.  It also has to do a safety-sanitize
         # of the html.  It could be written using html.parser.
         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: Ayons asperges pour le déjeuner

     Salut!

     Cela ressemble à un excellent recipie[1] déjeuner.

Legacy API:

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc822.html

   (2) (1) 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 Creating email and MIME objects from scratch,  Prev: email Examples,  Up: email --- An email and MIME handling package

5.19.1.13 ‘email.message.Message’: Representing an email message using the ‘compat32’ API
.........................................................................................

The *note Message: 546. class is very similar to the *note EmailMessage:
547. 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: 547. 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: 546.) policy *note Compat32: 9fa.  If you are going to use
another policy, you should be using the *note EmailMessage: 547. 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: 546. 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: 546. 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: 546. objects, for
MIME container documents (e.g.  ‘multipart/*’ and ‘message/rfc822’).

Here are the methods of the *note Message: 546. class:

 -- 類別: email.message.Message (policy=compat32)

     If `policy' is specified (it must be an instance of a *note policy:
     75. class) use the rules it specifies to update and serialize the
     representation of the message.  If `policy' is not set, use the
     *note compat32: 9fa. policy, which maintains backward compatibility
     with the Python 3.2 version of the email package.  For more
     information see the *note policy: 75. documentation.

     3.3 版更變: The `policy' keyword argument was added.

      -- 成員函式: 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: 546. 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: b51. instance and
          use its *note flatten(): 282a. 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(): 845. and *note BytesGenerator: b52.)

          3.4 版更變: the `policy' keyword argument was added.

      -- 成員函式: __str__ ()

          Equivalent to *note as_string(): 844.  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: 546. 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: b52. instance
          and use its *note flatten(): 2826. 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(): 845.  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: 546. objects, otherwise return ‘False’.  When *note
          is_multipart(): 2800. returns ‘False’, the payload should be a
          string object (which might be a CTE encoded binary payload).
          (Note that *note is_multipart(): 2800. 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: 546.
          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: 546. objects before the
          call.  After the call, the payload will always be a list of
          *note Message: 546. objects.  If you want to set the payload
          to a scalar object (e.g.  a string), use *note set_payload():
          2890. instead.

          This is a legacy method.  On the ‘EmailMessage’ class its
          functionality is replaced by *note set_content(): 2808. 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: 546. objects when *note is_multipart(): 2800. is
          ‘True’, or a string when *note is_multipart(): 2800. 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(): b50. will
          return the `i'-th element of the payload, counting from zero,
          if *note is_multipart(): 2800. is ‘True’.  An *note
          IndexError: e7a. 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(): 2800.
          is ‘False’) and `i' is given, a *note TypeError: 193. 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(): 2806. and
          *note iter_parts(): 2805.

      -- 成員函式: 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(): 2891. for details.

          This is a legacy method.  On the ‘EmailMessage’ class its
          functionality is replaced by *note set_content(): 2808.

      -- 成員函式: set_charset (charset)

          Set the character set of the payload to `charset', which can
          either be a *note Charset: 6d9. instance (see *note
          email.charset: 6a.), a string naming a character set, or
          ‘None’.  If it is a string, it will be converted to a *note
          Charset: 6d9. 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: 193.

          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: 6d9, 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: 6d9. 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(): 2893, but in a *note
     Message: 546. 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:
     284c. 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: 2c8. 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(): 2897. 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__(): 2896. 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__(): 2898. 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’.

          Here’s an example:

               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:
          2c8. 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(): 28a0. will be
          returned.  Since according to RFC 2045(5), messages always
          have a default type, *note get_content_type(): 289f. 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(): 289f.

      -- 成員函式: get_content_subtype ()

          Return the message’s sub-content type.  This is the ‘subtype’
          part of the string returned by *note get_content_type(): 289f.

      -- 成員函式: 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(): 28a5. 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():
          28a6, passing in the return value from *note get_param():
          28a5.  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: 1fc. 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(): 27f9.

      -- 成員函式: 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(): 27f9.

      -- 成員函式: set_boundary (boundary)

          Set the ‘boundary’ parameter of the ‘Content-Type’ header to
          `boundary'.  *note set_boundary(): 28ab. will always quote
          `boundary' if necessary.  A *note HeaderParseError: 27fc. 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(): 289d, because *note
          set_boundary(): 28ab. 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(): 2892.
          which returns the *note Charset: 6d9. 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(): 28ae. 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(): 28ae. 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(): 2800. 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: 546. 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: b1d.
          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: b51. 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: 74. and *note
          email.generator: 6e. 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: b51. 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: 6d.
          for a detailed description of the possible parsing defects.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc5322.html

   (2) https://tools.ietf.org/html/rfc2822.html

   (3) https://tools.ietf.org/html/rfc2231.html

   (4) https://tools.ietf.org/html/rfc2231.html

   (5) https://tools.ietf.org/html/rfc2045.html

   (6) https://tools.ietf.org/html/rfc2045.html

   (7) https://tools.ietf.org/html/rfc2045.html

   (8) https://tools.ietf.org/html/rfc2231.html

   (9) https://tools.ietf.org/html/rfc2231.html

   (10) https://tools.ietf.org/html/rfc2045.html

   (11) https://tools.ietf.org/html/rfc2231.html

   (12) https://tools.ietf.org/html/rfc2183.html


File: python.info,  Node: email mime Creating email and MIME objects from scratch,  Next: email header Internationalized headers,  Prev: email message Message Representing an email message using the compat32 API,  Up: email --- An email and MIME handling package

5.19.1.14 ‘email.mime’: Creating email and MIME objects from scratch
....................................................................

`Source code:' Lib/email/mime/(1)

__________________________________________________________________

This module is part of the legacy (‘Compat32’) email API. Its
functionality is partially replaced by the *note contentmanager: 6b. 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: 546. objects by hand.  In
fact, you can also take an existing structure and add new *note Message:
546. 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: 546.
instances, adding attachments and all the appropriate headers manually.
For MIME messages though, the *note email: 69. package provides some
convenient subclasses to make things easier.

Here are the classes:

 -- 類別: email.mime.base.MIMEBase (_maintype, _subtype, *,
          policy=compat32, **_params)

     Module: ‘email.mime.base’

     This is the base class for all the MIME-specific subclasses of
     *note Message: 546.  Ordinarily you won’t create instances
     specifically of *note MIMEBase: 28b4, although you could.  *note
     MIMEBase: 28b4. 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: 289d.

     If `policy' is specified, (defaults to the *note compat32: 9fa.
     policy) it will be passed to *note Message: 546.

     The *note MIMEBase: 28b4. 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 版更變: Added `policy' keyword-only parameter.

 -- 類別: email.mime.nonmultipart.MIMENonMultipart

     Module: ‘email.mime.nonmultipart’

     A subclass of *note MIMEBase: 28b4, 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():
     280e. method, which only makes sense for ‘multipart’ messages.  If
     *note attach(): 280e. is called, a *note MultipartConversionError:
     2854. exception is raised.

 -- 類別: email.mime.multipart.MIMEMultipart (_subtype='mixed',
          boundary=None, _subparts=None, *, policy=compat32, **_params)

     Module: ‘email.mime.multipart’

     A subclass of *note MIMEBase: 28b4, 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: 280e. method.

     Optional `policy' argument defaults to *note compat32: 9fa.

     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 版更變: Added `policy' keyword-only parameter.

 -- 類別: email.mime.application.MIMEApplication (_data,
          _subtype='octet-stream',
          _encoder=email.encoders.encode_base64, *, policy=compat32,
          **_params)

     Module: ‘email.mime.application’

     A subclass of *note MIMENonMultipart: 2855, the *note
     MIMEApplication: 28b6. class is used to represent MIME message
     objects of major type ‘application’.  `_data' is a string
     containing the raw byte 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:
     28b6. instance.  It should use *note get_payload(): b50. and *note
     set_payload(): 2890. 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: 6c. module for a list of the built-in
     encoders.

     Optional `policy' argument defaults to *note compat32: 9fa.

     `_params' are passed straight through to the base class
     constructor.

     3.6 版更變: Added `policy' keyword-only parameter.

 -- 類別: email.mime.audio.MIMEAudio (_audiodata, _subtype=None,
          _encoder=email.encoders.encode_base64, *, policy=compat32,
          **_params)

     Module: ‘email.mime.audio’

     A subclass of *note MIMENonMultipart: 2855, the *note MIMEAudio:
     28b7. class is used to create MIME message objects of major type
     ‘audio’.  `_audiodata' is a string containing the raw audio data.
     If this data can be decoded by the standard Python module *note
     sndhdr: ef, 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:
     193. 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: 28b7.
     instance.  It should use *note get_payload(): b50. and *note
     set_payload(): 2890. 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: 6c. module for a list of the built-in
     encoders.

     Optional `policy' argument defaults to *note compat32: 9fa.

     `_params' are passed straight through to the base class
     constructor.

     3.6 版更變: Added `policy' keyword-only parameter.

 -- 類別: email.mime.image.MIMEImage (_imagedata, _subtype=None,
          _encoder=email.encoders.encode_base64, *, policy=compat32,
          **_params)

     Module: ‘email.mime.image’

     A subclass of *note MIMENonMultipart: 2855, the *note MIMEImage:
     2856. class is used to create MIME message objects of major type
     ‘image’.  `_imagedata' is a string containing the raw image data.
     If this data can be decoded by the standard Python module *note
     imghdr: 99, 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:
     193. 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: 2856.
     instance.  It should use *note get_payload(): b50. and *note
     set_payload(): 2890. 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: 6c. module for a list of the built-in
     encoders.

     Optional `policy' argument defaults to *note compat32: 9fa.

     `_params' are passed straight through to the *note MIMEBase: 28b4.
     constructor.

     3.6 版更變: Added `policy' keyword-only parameter.

 -- 類別: email.mime.message.MIMEMessage (_msg, _subtype='rfc822', *,
          policy=compat32)

     Module: ‘email.mime.message’

     A subclass of *note MIMENonMultipart: 2855, the *note MIMEMessage:
     28b8. 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: 546. (or a subclass thereof), otherwise a *note
     TypeError: 193. is raised.

     Optional `_subtype' sets the subtype of the message; it defaults to
     ‘rfc822’.

     Optional `policy' argument defaults to *note compat32: 9fa.

     3.6 版更變: Added `policy' keyword-only parameter.

 -- 類別: email.mime.text.MIMEText (_text, _subtype='plain',
          _charset=None, *, policy=compat32)

     Module: ‘email.mime.text’

     A subclass of *note MIMENonMultipart: 2855, the *note MIMEText:
     6d8. 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: 2855. 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: 6d9. 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: 9fa.

     3.5 版更變: `_charset' also accepts *note Charset: 6d9. instances.

     3.6 版更變: Added `policy' keyword-only parameter.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/email/mime/


File: python.info,  Node: email header Internationalized headers,  Next: email charset Representing character sets,  Prev: email mime Creating email and MIME objects from scratch,  Up: email --- An email and MIME handling package

5.19.1.15 ‘email.header’: Internationalized headers
...................................................

`Source code:' 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: 547. 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:
69. package supports these standards in its *note email.header: 6f. and
*note email.charset: 6a. 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: 284c.
class and assign the field in the *note Message: 546. object to an
instance of *note Header: 284c. instead of using a string for the header
value.  Import the *note Header: 284c. class from the *note
email.header: 6f. 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: 284c. instance and
passing in the character set that the byte string was encoded in.  When
the subsequent *note Message: 546. 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: 284c. 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(): 28bb. method calls.  `s' may be an
     instance of *note bytes: 336. or *note str: 335, but see the *note
     append(): 28bb. documentation for semantics.

     Optional `charset' serves two purposes: it has the same meaning as
     the `charset' argument to the *note append(): 28bb. method.  It
     also sets the default character set for all subsequent *note
     append(): 28bb. 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(): 28bb. 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 76, 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():
     28bb. method.

      -- 成員函式: append (s, charset=None, errors='strict')

          Append the string `s' to the MIME header.

          Optional `charset', if given, should be a *note Charset: 6d9.
          instance (see *note email.charset: 6a.) or the name of a
          character set, which will be converted to a *note Charset:
          6d9. 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: 336. or *note str: 335.
          If it is an instance of *note bytes: 336, then `charset' is
          the encoding of that byte string, and a *note UnicodeError:
          c40. will be raised if the string cannot be decoded with that
          character set.

          If `s' is an instance of *note str: 335, 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 版更變: Added the `linesep' argument.

     The *note Header: 284c. class also provides a number of methods to
     support standard operators and built-in functions.

      -- 成員函式: __str__ ()

          Returns an approximation of the *note Header: 284c. 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: 284c.
          instances for equality.

      -- 成員函式: __ne__ (other)

          This method allows you to compare two *note Header: 284c.
          instances for inequality.

The *note email.header: 6f. 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.

     Here’s an example:

          >>> 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: 284c. instance from a sequence of pairs as
     returned by *note decode_header(): 9fe.

     *note decode_header(): 9fe. 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: 284c. instance.  Optional `maxlinelen',
     `header_name', and `continuation_ws' are as in the *note Header:
     284c. constructor.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/email/header.py

   (2) https://tools.ietf.org/html/rfc2822.html

   (3) https://tools.ietf.org/html/rfc822.html

   (4) https://tools.ietf.org/html/rfc2822.html

   (5) https://tools.ietf.org/html/rfc2822.html

   (6) https://tools.ietf.org/html/rfc2045.html

   (7) https://tools.ietf.org/html/rfc2046.html

   (8) https://tools.ietf.org/html/rfc2047.html

   (9) https://tools.ietf.org/html/rfc2231.html

   (10) https://tools.ietf.org/html/rfc2047.html

   (11) https://tools.ietf.org/html/rfc2822.html

   (12) https://tools.ietf.org/html/rfc2822.html

   (13) https://tools.ietf.org/html/rfc2047.html

   (14) https://tools.ietf.org/html/rfc2822.html

   (15) https://tools.ietf.org/html/rfc2047.html


File: python.info,  Node: email charset Representing character sets,  Next: email encoders Encoders,  Prev: email header Internationalized headers,  Up: email --- An email and MIME handling package

5.19.1.16 ‘email.charset’: Representing character sets
......................................................

`Source code:' Lib/email/charset.py(1)

__________________________________________________________________

This module is part of the legacy (‘Compat32’) email API. In the new API
only the aliases table is used.

The remaining text in this section is the original documentation of the
module.

This module provides a class *note Charset: 6d9. for representing
character sets and character set conversions in email messages, as well
as a character set registry and several convenience methods for
manipulating this registry.  Instances of *note Charset: 6d9. are used
in several other modules within the *note email: 69. package.

Import this class from the *note email.charset: 6a. module.

 -- 類別: 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: 6d9. 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: 6d9. 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(): 28ca. 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: 6d9. 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.
          *note __repr__(): 343. is an alias for *note __str__(): 28cd.

      -- 成員函式: __eq__ (other)

          This method allows you to compare two *note Charset: 6d9.
          instances for equality.

      -- 成員函式: __ne__ (other)

          This method allows you to compare two *note Charset: 6d9.
          instances for inequality.

The *note email.charset: 6a. 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(): 28d1. to add codecs the module does not know about.
     See the *note codecs: 1c. 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: 335.’s *note encode(): c3c. method.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/email/charset.py


File: python.info,  Node: email encoders Encoders,  Next: email utils Miscellaneous utilities,  Prev: email charset Representing character sets,  Up: email --- An email and MIME handling package

5.19.1.17 ‘email.encoders’: Encoders
....................................

`Source code:' Lib/email/encoders.py(1)

__________________________________________________________________

This module is part of the legacy (‘Compat32’) email API. In the new API
the functionality is provided by the `cte' parameter of the *note
set_content(): 2808. method.

This module is deprecated in Python 3.  The functions provided here
should not be called explicitly since the *note MIMEText: 6d8. class
sets the content type and CTE header using the `_subtype' and `_charset'
values passed during the instaniation of that class.

The remaining text in this section is the original documentation of the
module.

When creating *note Message: 546. objects from scratch, you often need
to encode the payloads for transport through compliant mail servers.
This is especially true for ‘image/*’ and ‘text/*’ type messages
containing binary data.

The *note email: 69. package provides some convenient encoders in its
‘encoders’ module.  These encoders are actually used by the *note
MIMEAudio: 28b7. and *note MIMEImage: 2856. class constructors to
provide default encodings.  All encoder functions take exactly one
argument, the message object to encode.  They usually extract the
payload, encode it, and reset the payload to this newly encoded value.
They should also set the ‘Content-Transfer-Encoding’ header as
appropriate.

Note that these functions are not meaningful for a multipart message.
They must be applied to individual subparts instead, and will raise a
*note TypeError: 193. if passed a message whose type is multipart.

Here are the encoding functions provided:

 -- 函式: email.encoders.encode_quopri (msg)

     Encodes the payload into quoted-printable form and sets the
     ‘Content-Transfer-Encoding’ header to ‘quoted-printable’ (2).  This
     is a good encoding to use when most of your payload is normal
     printable data, but contains a few unprintable characters.

 -- 函式: email.encoders.encode_base64 (msg)

     Encodes the payload into base64 form and sets the
     ‘Content-Transfer-Encoding’ header to ‘base64’.  This is a good
     encoding to use when most of your payload is unprintable data since
     it is a more compact form than quoted-printable.  The drawback of
     base64 encoding is that it renders the text non-human readable.

 -- 函式: email.encoders.encode_7or8bit (msg)

     This doesn’t actually modify the message’s payload, but it does set
     the ‘Content-Transfer-Encoding’ header to either ‘7bit’ or ‘8bit’
     as appropriate, based on the payload data.

 -- 函式: email.encoders.encode_noop (msg)

     This does nothing; it doesn’t even set the
     ‘Content-Transfer-Encoding’ header.

註解
....

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/email/encoders.py

   (2) (1) Note that encoding with *note encode_quopri(): 28d5. also
encodes all tabs and space characters in the data.


File: python.info,  Node: email utils Miscellaneous utilities,  Next: email iterators Iterators,  Prev: email encoders Encoders,  Up: email --- An email and MIME handling package

5.19.1.18 ‘email.utils’: Miscellaneous utilities
................................................

`Source code:' Lib/email/utils.py(1)

__________________________________________________________________

There are a couple of useful utilities provided in the *note
email.utils: 76. 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: 195. 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.  In this case, a positive or zero value for `isdst'
     causes ‘localtime’ to presume initially that summer time (for
     example, Daylight Saving Time) is or is not (respectively) in
     effect for the specified time.  A negative value for `isdst' causes
     the ‘localtime’ to attempt to divine whether summer time is in
     effect for the specified time.

     3.3 版新加入.

 -- 函式: 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 版更變: Added the `domain' keyword.

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)

     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.

 -- 函式: email.utils.formataddr (pair, charset='utf-8')

     The inverse of *note parseaddr(): 28dd, 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: 335. or a
     *note Charset: 6d9.  Defaults to ‘utf-8’.

     3.3 版更變: Added the `charset' option.

 -- 函式: email.utils.getaddresses (fieldvalues)

     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: 2897.  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)

 -- 函式: 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(): 28df. 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(): 28df. returns a 9-tuple that can be passed
     directly to *note time.mktime(): b69.; 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(): 28df, 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(): b69, 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(): a03.  Performs the same
     function as *note parsedate(): 28df, but on success returns a *note
     datetime: 195.  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: a06. *note tzinfo: 385.

     3.3 版新加入.

 -- 函式: email.utils.mktime_tz (tuple)

     Turn a 10-tuple as returned by *note parsedate_tz(): 28e0. 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(): b44. and *note time.localtime():
     f52, 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: 31. 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: 28a5. may return a 3-tuple containing the
     character set, language, and value.  *note
     collapse_rfc2231_value(): 28a6. turns this into a unicode string.
     Optional `errors' is passed to the `errors' argument of *note str:
     335.’s *note encode(): c3c. 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(): 28a6. 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.8/Lib/email/utils.py

   (2) https://tools.ietf.org/html/rfc2822.html

   (3) https://tools.ietf.org/html/rfc2047.html

   (4) https://tools.ietf.org/html/rfc2822.html

   (5) https://tools.ietf.org/html/rfc2822.html

   (6) (1) 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://tools.ietf.org/html/rfc2822.html).

   (7) https://tools.ietf.org/html/rfc2822.html

   (8) https://tools.ietf.org/html/rfc2231.html

   (9) https://tools.ietf.org/html/rfc2231.html

   (10) https://tools.ietf.org/html/rfc2231.html

   (11) https://tools.ietf.org/html/rfc2231.html

   (12) https://tools.ietf.org/html/rfc2231.html


File: python.info,  Node: email iterators Iterators,  Prev: email utils Miscellaneous utilities,  Up: email --- An email and MIME handling package

5.19.1.19 ‘email.iterators’: Iterators
......................................

`Source code:' Lib/email/iterators.py(1)

__________________________________________________________________

Iterating over a message object tree is fairly easy with the *note
Message.walk: 28ae. method.  The *note email.iterators: 71. 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(): 1c03, skipping over all the intervening headers.

     Optional `decode' is passed through to *note Message.get_payload:
     b50.

 -- 函式: 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(): 28e9. 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(): 88b. function.
     `level' is used internally.  `include_default', if true, prints the
     default type as well.

也參考
......

Module *note smtplib: ee.

     SMTP (Simple Mail Transport Protocol) client

Module *note poplib: d1.

     POP (Post Office Protocol) client

Module *note imaplib: 98.

     IMAP (Internet Message Access Protocol) client

Module *note nntplib: c1.

     NNTP (Net News Transport Protocol) client

Module *note mailbox: af.

     Tools for creating, reading, and managing collections of messages
     on disk using a variety standard formats.

Module *note smtpd: ed.

     SMTP server framework (primarily useful for testing)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/email/iterators.py


File: python.info,  Node: json --- JSON encoder and decoder,  Next: mailcap --- Mailcap file handling,  Prev: email --- An email and MIME handling package,  Up: Internet Data Handling

5.19.2 ‘json’ — JSON encoder and decoder
----------------------------------------

`Source code:' Lib/json/__init__.py(1)

__________________________________________________________________

JSON (JavaScript Object Notation)(2), specified by RFC 7159(3) (which
obsoletes RFC 4627(4)) and by ECMA-404(5), is a lightweight data
interchange format inspired by JavaScript(6) object literal syntax
(although it is not a strict subset of JavaScript (7) ).

*note json: a5. exposes an API familiar to users of the standard library
*note marshal: b1. and *note pickle: cb. modules.

Encoding basic Python object hierarchies:

     >>> 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"]'

Compact encoding:

     >>> import json
     >>> json.dumps([1, 2, 3, {'4': 5, '6': 7}], separators=(',', ':'))
     '[1,2,3,{"4":5,"6":7}]'

美化輸出：

     >>> import json
     >>> print(json.dumps({'4': 5, '6': 7}, sort_keys=True, indent=4))
     {
         "4": 5,
         "6": 7
     }

Decoding 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']

Specializing JSON object decoding:

     >>> 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')

Extending *note JSONEncoder: 60b.:

     >>> 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 json.JSONEncoder.default(self, 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', ']']

Using *note json.tool: a6. from the shell to validate and pretty-print:

     $ 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)

See *note Command Line Interface: 28ed. for detailed documentation.

     備註: JSON is a subset of YAML(8) 1.2.  The JSON produced by this
     module’s default settings (in particular, the default `separators'
     value) is also a subset of YAML 1.0 and 1.1.  This module can thus
     also be used as a YAML serializer.

     備註: This module’s encoders and decoders preserve input and output
     order by default.  Order is only lost if the underlying containers
     are unordered.

     Prior to Python 3.7, *note dict: 1b9. was not guaranteed to be
     ordered, so inputs and outputs were typically scrambled unless
     *note collections.OrderedDict: 1ba. was specifically requested.
     Starting with Python 3.7, the regular *note dict: 1b9. became order
     preserving, so it is no longer necessary to specify *note
     collections.OrderedDict: 1ba. for JSON generation and parsing.

* Menu:

* Basic Usage::
* Encoders and Decoders::
* 例外: 例外<2>.
* Standard Compliance and Interoperability::
* Command Line Interface: Command Line Interface<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/json/__init__.py

   (2) http://json.org

   (3) https://tools.ietf.org/html/rfc7159.html

   (4) https://tools.ietf.org/html/rfc4627.html

   (5) 
http://www.ecma-international.org/publications/standards/Ecma-404.htm

   (6) https://en.wikipedia.org/wiki/JavaScript

   (7) (1) As noted in the errata for RFC 7159
(https://www.rfc-editor.org/errata_search.php?rfc=7159), JSON permits
literal U+2028 (LINE SEPARATOR) and U+2029 (PARAGRAPH SEPARATOR)
characters in strings, whereas JavaScript (as of ECMAScript Edition 5.1)
does not.

   (8) http://yaml.org/


File: python.info,  Node: Basic Usage,  Next: Encoders and Decoders,  Up: json --- JSON encoder and decoder

5.19.2.1 Basic Usage
....................

 -- 函式: 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)

     Serialize `obj' as a JSON formatted stream to `fp' (a
     ‘.write()’-supporting *note file-like object: 1c6f.) using this
     *note conversion table: 28ef.

     If `skipkeys' is true (default: ‘False’), then dict keys that are
     not of a basic type (*note str: 335, *note int: 185, *note float:
     188, *note bool: 184, ‘None’) will be skipped instead of raising a
     *note TypeError: 193.

     The *note json: a5. module always produces *note str: 335. objects,
     not *note bytes: 336. objects.  Therefore, ‘fp.write()’ must
     support *note str: 335. input.

     If `ensure_ascii' is true (the default), the output is guaranteed
     to have all incoming non-ASCII characters escaped.  If
     `ensure_ascii' is false, these characters will be output as-is.

     If `check_circular' is false (default: ‘True’), then the circular
     reference check for container types will be skipped and a circular
     reference will result in an *note OverflowError: 965. (or worse).

     If `allow_nan' is false (default: ‘True’), then it will be a *note
     ValueError: 1fc. to serialize out of range *note float: 188. values
     (‘nan’, ‘inf’, ‘-inf’) in strict compliance of the JSON
     specification.  If `allow_nan' is true, their JavaScript
     equivalents (‘NaN’, ‘Infinity’, ‘-Infinity’) will be used.

     If `indent' is a non-negative integer or string, then JSON array
     elements and object members will be pretty-printed with that indent
     level.  An indent level of 0, negative, or ‘""’ will only insert
     newlines.  ‘None’ (the default) selects the most compact
     representation.  Using a positive integer indent indents that many
     spaces per level.  If `indent' is a string (such as ‘"\t"’), that
     string is used to indent each level.

     3.2 版更變: Allow strings for `indent' in addition to integers.

     If specified, `separators' should be an ‘(item_separator,
     key_separator)’ tuple.  The default is ‘(', ', ': ')’ if `indent'
     is ‘None’ and ‘(',', ': ')’ otherwise.  To get the most compact
     JSON representation, you should specify ‘(',', ':')’ to eliminate
     whitespace.

     3.4 版更變: Use ‘(',', ': ')’ as default if `indent' is not ‘None’.

     If specified, `default' should be a function that gets called for
     objects that can’t otherwise be serialized.  It should return a
     JSON encodable version of the object or raise a *note TypeError:
     193.  If not specified, *note TypeError: 193. is raised.

     If `sort_keys' is true (default: ‘False’), then the output of
     dictionaries will be sorted by key.

     To use a custom *note JSONEncoder: 60b. subclass (e.g.  one that
     overrides the ‘default()’ method to serialize additional types),
     specify it with the `cls' kwarg; otherwise *note JSONEncoder: 60b.
     is used.

     3.6 版更變: All optional parameters are now *note keyword-only:
     2ad.

          備註: Unlike *note pickle: cb. and *note marshal: b1, JSON is
          not a framed protocol, so trying to serialize multiple objects
          with repeated calls to *note dump(): 609. using the same `fp'
          will result in an invalid JSON file.

 -- 函式: 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)

     Serialize `obj' to a JSON formatted *note str: 335. using this
     *note conversion table: 28ef.  The arguments have the same meaning
     as in *note dump(): 609.

          備註: Keys in key/value pairs of JSON are always of the type
          *note str: 335.  When a dictionary is converted into JSON, all
          the keys of the dictionary are coerced to strings.  As a
          result of this, if a dictionary is converted into JSON and
          then back into a dictionary, the dictionary may not equal the
          original one.  That is, ‘loads(dumps(x)) != x’ if x has
          non-string keys.

 -- 函式: json.load (fp, *, cls=None, object_hook=None,
          parse_float=None, parse_int=None, parse_constant=None,
          object_pairs_hook=None, **kw)

     Deserialize `fp' (a ‘.read()’-supporting *note text file: 12aa. or
     *note binary file: 1caa. containing a JSON document) to a Python
     object using this *note conversion table: 28f0.

     `object_hook' is an optional function that will be called with the
     result of any object literal decoded (a *note dict: 1b9.).  The
     return value of `object_hook' will be used instead of the *note
     dict: 1b9.  This feature can be used to implement custom decoders
     (e.g.  JSON-RPC(1) class hinting).

     `object_pairs_hook' is an optional function that will be called
     with the result of any object literal decoded with an ordered list
     of pairs.  The return value of `object_pairs_hook' will be used
     instead of the *note dict: 1b9.  This feature can be used to
     implement custom decoders.  If `object_hook' is also defined, the
     `object_pairs_hook' takes priority.

     3.1 版更變: Added support for `object_pairs_hook'.

     `parse_float', if specified, will be called with the string of
     every JSON float to be decoded.  By default, this is equivalent to
     ‘float(num_str)’.  This can be used to use another datatype or
     parser for JSON floats (e.g.  *note decimal.Decimal: 189.).

     `parse_int', if specified, will be called with the string of every
     JSON int to be decoded.  By default, this is equivalent to
     ‘int(num_str)’.  This can be used to use another datatype or parser
     for JSON integers (e.g.  *note float: 188.).

     `parse_constant', if specified, will be called with one of the
     following strings: ‘'-Infinity'’, ‘'Infinity'’, ‘'NaN'’.  This can
     be used to raise an exception if invalid JSON numbers are
     encountered.

     3.1 版更變: `parse_constant' doesn’t get called on ’null’, ’true’,
     ’false’ anymore.

     To use a custom *note JSONDecoder: 60c. subclass, specify it with
     the ‘cls’ kwarg; otherwise *note JSONDecoder: 60c. is used.
     Additional keyword arguments will be passed to the constructor of
     the class.

     If the data being deserialized is not a valid JSON document, a
     *note JSONDecodeError: 70b. will be raised.

     3.6 版更變: All optional parameters are now *note keyword-only:
     2ad.

     3.6 版更變: `fp' can now be a *note binary file: 1caa.  The input
     encoding should be UTF-8, UTF-16 or UTF-32.

 -- 函式: json.loads (s, *, cls=None, object_hook=None,
          parse_float=None, parse_int=None, parse_constant=None,
          object_pairs_hook=None, **kw)

     Deserialize `s' (a *note str: 335, *note bytes: 336. or *note
     bytearray: 337. instance containing a JSON document) to a Python
     object using this *note conversion table: 28f0.

     The other arguments have the same meaning as in *note load(): 564,
     except `encoding' which is ignored and deprecated since Python 3.1.

     If the data being deserialized is not a valid JSON document, a
     *note JSONDecodeError: 70b. will be raised.

     Deprecated since version 3.1, will be removed in version 3.9:
     `encoding' keyword argument.

     3.6 版更變: `s' can now be of type *note bytes: 336. or *note
     bytearray: 337.  The input encoding should be UTF-8, UTF-16 or
     UTF-32.

   ---------- Footnotes ----------

   (1) http://www.jsonrpc.org


File: python.info,  Node: Encoders and Decoders,  Next: 例外<2>,  Prev: Basic Usage,  Up: json --- JSON encoder and decoder

5.19.2.2 Encoders and Decoders
..............................

 -- 類別: json.JSONDecoder (*, object_hook=None, parse_float=None,
          parse_int=None, parse_constant=None, strict=True,
          object_pairs_hook=None)

     Simple JSON decoder.

     Performs the following translations in decoding by default:

     JSON                Python
                         
     --------------------------------------------
                         
     object              dict
                         
                         
     array               list
                         
                         
     string              str
                         
                         
     number (int)        int
                         
                         
     number (real)       float
                         
                         
     true                True
                         
                         
     false               False
                         
                         
     null                None
                         

     It also understands ‘NaN’, ‘Infinity’, and ‘-Infinity’ as their
     corresponding ‘float’ values, which is outside the JSON spec.

     `object_hook', if specified, will be called with the result of
     every JSON object decoded and its return value will be used in
     place of the given *note dict: 1b9.  This can be used to provide
     custom deserializations (e.g.  to support JSON-RPC class hinting).

     `object_pairs_hook', if specified 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: 1b9.  This feature can be used to implement custom
     decoders.  If `object_hook' is also defined, the
     `object_pairs_hook' takes priority.

     3.1 版更變: Added support for `object_pairs_hook'.

     `parse_float', if specified, will be called with the string of
     every JSON float to be decoded.  By default, this is equivalent to
     ‘float(num_str)’.  This can be used to use another datatype or
     parser for JSON floats (e.g.  *note decimal.Decimal: 189.).

     `parse_int', if specified, will be called with the string of every
     JSON int to be decoded.  By default, this is equivalent to
     ‘int(num_str)’.  This can be used to use another datatype or parser
     for JSON integers (e.g.  *note float: 188.).

     `parse_constant', if specified, will be called with one of the
     following strings: ‘'-Infinity'’, ‘'Infinity'’, ‘'NaN'’.  This can
     be used to raise an exception if invalid JSON numbers are
     encountered.

     If `strict' is false (‘True’ is the default), then control
     characters will be allowed inside strings.  Control characters in
     this context are those with character codes in the 0–31 range,
     including ‘'\t'’ (tab), ‘'\n'’, ‘'\r'’ and ‘'\0'’.

     If the data being deserialized is not a valid JSON document, a
     *note JSONDecodeError: 70b. will be raised.

     3.6 版更變: All parameters are now *note keyword-only: 2ad.

      -- 成員函式: decode (s)

          Return the Python representation of `s' (a *note str: 335.
          instance containing a JSON document).

          *note JSONDecodeError: 70b. will be raised if the given JSON
          document is not valid.

      -- 成員函式: raw_decode (s)

          Decode a JSON document from `s' (a *note str: 335. beginning
          with a JSON document) and return a 2-tuple of the Python
          representation and the index in `s' where the document ended.

          This can be used to decode a JSON document from a string that
          may have extraneous data at the end.

 -- 類別: json.JSONEncoder (*, skipkeys=False, ensure_ascii=True,
          check_circular=True, allow_nan=True, sort_keys=False,
          indent=None, separators=None, default=None)

     Extensible JSON encoder for Python data structures.

     Supports the following objects and types by default:

     Python                                       JSON
                                                  
     -----------------------------------------------------------------
                                                  
     dict                                         object
                                                  
                                                  
     list, tuple                                  array
                                                  
                                                  
     str                                          string
                                                  
                                                  
     int, float, int- & float-derived Enums       number
                                                  
                                                  
     True                                         true
                                                  
                                                  
     False                                        false
                                                  
                                                  
     None                                         null
                                                  

     3.4 版更變: Added support for int- and float-derived Enum classes.

     To extend this to recognize other objects, subclass and implement a
     *note default(): 28f4. method with another method that returns a
     serializable object for ‘o’ if possible, otherwise it should call
     the superclass implementation (to raise *note TypeError: 193.).

     If `skipkeys' is false (the default), then it is a *note TypeError:
     193. to attempt encoding of keys that are not *note str: 335, *note
     int: 185, *note float: 188. or ‘None’.  If `skipkeys' is true, such
     items are simply skipped.

     If `ensure_ascii' is true (the default), the output is guaranteed
     to have all incoming non-ASCII characters escaped.  If
     `ensure_ascii' is false, these characters will be output as-is.

     If `check_circular' is true (the default), then lists, dicts, and
     custom encoded objects will be checked for circular references
     during encoding to prevent an infinite recursion (which would cause
     an *note OverflowError: 965.).  Otherwise, no such check takes
     place.

     If `allow_nan' is true (the default), then ‘NaN’, ‘Infinity’, and
     ‘-Infinity’ will be encoded as such.  This behavior is not JSON
     specification compliant, but is consistent with most JavaScript
     based encoders and decoders.  Otherwise, it will be a *note
     ValueError: 1fc. to encode such floats.

     If `sort_keys' is true (default: ‘False’), then the output of
     dictionaries will be sorted by key; this is useful for regression
     tests to ensure that JSON serializations can be compared on a
     day-to-day basis.

     If `indent' is a non-negative integer or string, then JSON array
     elements and object members will be pretty-printed with that indent
     level.  An indent level of 0, negative, or ‘""’ will only insert
     newlines.  ‘None’ (the default) selects the most compact
     representation.  Using a positive integer indent indents that many
     spaces per level.  If `indent' is a string (such as ‘"\t"’), that
     string is used to indent each level.

     3.2 版更變: Allow strings for `indent' in addition to integers.

     If specified, `separators' should be an ‘(item_separator,
     key_separator)’ tuple.  The default is ‘(', ', ': ')’ if `indent'
     is ‘None’ and ‘(',', ': ')’ otherwise.  To get the most compact
     JSON representation, you should specify ‘(',', ':')’ to eliminate
     whitespace.

     3.4 版更變: Use ‘(',', ': ')’ as default if `indent' is not ‘None’.

     If specified, `default' should be a function that gets called for
     objects that can’t otherwise be serialized.  It should return a
     JSON encodable version of the object or raise a *note TypeError:
     193.  If not specified, *note TypeError: 193. is raised.

     3.6 版更變: All parameters are now *note keyword-only: 2ad.

      -- 成員函式: default (o)

          Implement this method in a subclass such that it returns a
          serializable object for `o', or calls the base implementation
          (to raise a *note TypeError: 193.).

          For example, to support arbitrary iterators, you could
          implement default like this:

               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 json.JSONEncoder.default(self, o)

      -- 成員函式: encode (o)

          Return a JSON string representation of a Python data
          structure, `o'.  For example:

               >>> json.JSONEncoder().encode({"foo": ["bar", "baz"]})
               '{"foo": ["bar", "baz"]}'

      -- 成員函式: iterencode (o)

          Encode the given object, `o', and yield each string
          representation as available.  For example:

               for chunk in json.JSONEncoder().iterencode(bigobject):
                   mysocket.write(chunk)


File: python.info,  Node: 例外<2>,  Next: Standard Compliance and Interoperability,  Prev: Encoders and Decoders,  Up: json --- JSON encoder and decoder

5.19.2.3 例外
.............

 -- 例外: json.JSONDecodeError (msg, doc, pos)

     Subclass of *note ValueError: 1fc. with the following additional
     attributes:

      -- 屬性: msg

          The unformatted error message.

      -- 屬性: doc

          The JSON document being parsed.

      -- 屬性: pos

          The start index of `doc' where parsing failed.

      -- 屬性: lineno

          The line corresponding to `pos'.

      -- 屬性: colno

          The column corresponding to `pos'.

     3.5 版新加入.


File: python.info,  Node: Standard Compliance and Interoperability,  Next: Command Line Interface<2>,  Prev: 例外<2>,  Up: json --- JSON encoder and decoder

5.19.2.4 Standard Compliance and Interoperability
.................................................

The JSON format is specified by RFC 7159(1) and by ECMA-404(2).  This
section details this module’s level of compliance with the RFC. For
simplicity, *note JSONEncoder: 60b. and *note JSONDecoder: 60c.
subclasses, and parameters other than those explicitly mentioned, are
not considered.

This module does not comply with the RFC in a strict fashion,
implementing some extensions that are valid JavaScript but not valid
JSON. In particular:

   - Infinite and NaN number values are accepted and output;

   - Repeated names within an object are accepted, and only the value of
     the last name-value pair is used.

Since the RFC permits RFC-compliant parsers to accept input texts that
are not RFC-compliant, this module’s deserializer is technically
RFC-compliant under default settings.

* Menu:

* Character Encodings::
* Infinite and NaN Number Values::
* Repeated Names Within an Object::
* Top-level Non-Object, Non-Array Values: Top-level Non-Object Non-Array Values.
* Implementation Limitations::

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc7159.html

   (2) 
http://www.ecma-international.org/publications/standards/Ecma-404.htm


File: python.info,  Node: Character Encodings,  Next: Infinite and NaN Number Values,  Up: Standard Compliance and Interoperability

5.19.2.5 Character Encodings
............................

The RFC requires that JSON be represented using either UTF-8, UTF-16, or
UTF-32, with UTF-8 being the recommended default for maximum
interoperability.

As permitted, though not required, by the RFC, this module’s serializer
sets `ensure_ascii=True' by default, thus escaping the output so that
the resulting strings only contain ASCII characters.

Other than the `ensure_ascii' parameter, this module is defined strictly
in terms of conversion between Python objects and *note Unicode strings:
335, and thus does not otherwise directly address the issue of character
encodings.

The RFC prohibits adding a byte order mark (BOM) to the start of a JSON
text, and this module’s serializer does not add a BOM to its output.
The RFC permits, but does not require, JSON deserializers to ignore an
initial BOM in their input.  This module’s deserializer raises a *note
ValueError: 1fc. when an initial BOM is present.

The RFC does not explicitly forbid JSON strings which contain byte
sequences that don’t correspond to valid Unicode characters (e.g.
unpaired UTF-16 surrogates), but it does note that they may cause
interoperability problems.  By default, this module accepts and outputs
(when present in the original *note str: 335.) code points for such
sequences.


File: python.info,  Node: Infinite and NaN Number Values,  Next: Repeated Names Within an Object,  Prev: Character Encodings,  Up: Standard Compliance and Interoperability

5.19.2.6 Infinite and NaN Number Values
.......................................

The RFC does not permit the representation of infinite or NaN number
values.  Despite that, by default, this module accepts and outputs
‘Infinity’, ‘-Infinity’, and ‘NaN’ as if they were valid JSON number
literal values:

     >>> # 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

In the serializer, the `allow_nan' parameter can be used to alter this
behavior.  In the deserializer, the `parse_constant' parameter can be
used to alter this behavior.


File: python.info,  Node: Repeated Names Within an Object,  Next: Top-level Non-Object Non-Array Values,  Prev: Infinite and NaN Number Values,  Up: Standard Compliance and Interoperability

5.19.2.7 Repeated Names Within an Object
........................................

The RFC specifies that the names within a JSON object should be unique,
but does not mandate how repeated names in JSON objects should be
handled.  By default, this module does not raise an exception; instead,
it ignores all but the last name-value pair for a given name:

     >>> weird_json = '{"x": 1, "x": 2, "x": 3}'
     >>> json.loads(weird_json)
     {'x': 3}

The `object_pairs_hook' parameter can be used to alter this behavior.


File: python.info,  Node: Top-level Non-Object Non-Array Values,  Next: Implementation Limitations,  Prev: Repeated Names Within an Object,  Up: Standard Compliance and Interoperability

5.19.2.8 Top-level Non-Object, Non-Array Values
...............................................

The old version of JSON specified by the obsolete RFC 4627(1) required
that the top-level value of a JSON text must be either a JSON object or
array (Python *note dict: 1b9. or *note list: 263.), and could not be a
JSON null, boolean, number, or string value.  RFC 7159(2) removed that
restriction, and this module does not and has never implemented that
restriction in either its serializer or its deserializer.

Regardless, for maximum interoperability, you may wish to voluntarily
adhere to the restriction yourself.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc4627.html

   (2) https://tools.ietf.org/html/rfc7159.html


File: python.info,  Node: Implementation Limitations,  Prev: Top-level Non-Object Non-Array Values,  Up: Standard Compliance and Interoperability

5.19.2.9 Implementation Limitations
...................................

Some JSON deserializer implementations may set limits on:

   * the size of accepted JSON texts

   * the maximum level of nesting of JSON objects and arrays

   * the range and precision of JSON numbers

   * the content and maximum length of JSON strings

This module does not impose any such limits beyond those of the relevant
Python datatypes themselves or the Python interpreter itself.

When serializing to JSON, beware any such limitations in applications
that may consume your JSON. In particular, it is common for JSON numbers
to be deserialized into IEEE 754 double precision numbers and thus
subject to that representation’s range and precision limitations.  This
is especially relevant when serializing Python *note int: 185. values of
extremely large magnitude, or when serializing instances of "exotic"
numerical types such as *note decimal.Decimal: 189.


File: python.info,  Node: Command Line Interface<2>,  Prev: Standard Compliance and Interoperability,  Up: json --- JSON encoder and decoder

5.19.2.10 Command Line Interface
................................

`Source code:' Lib/json/tool.py(1)

__________________________________________________________________

The *note json.tool: a6. module provides a simple command line interface
to validate and pretty-print JSON objects.

If the optional ‘infile’ and ‘outfile’ arguments are not specified,
*note sys.stdin: 312. and *note sys.stdout: 313. will be used
respectively:

     $ 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 版更變: The output is now in the same order as the input.  Use the
*note –sort-keys: 2904. option to sort the output of dictionaries
alphabetically by key.

* Menu:

* Command line options: Command line options<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/json/tool.py


File: python.info,  Node: Command line options<2>,  Up: Command Line Interface<2>

5.19.2.11 Command line options
..............................

 -- 程式選項: infile

     The JSON file to be validated or pretty-printed:

          $ 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
              }
          ]

     If `infile' is not specified, read from *note sys.stdin: 312.

 -- 程式選項: outfile

     Write the output of the `infile' to the given `outfile'.
     Otherwise, write it to *note sys.stdout: 313.

 -- 程式選項: --sort-keys

     Sort the output of dictionaries alphabetically by key.

     3.5 版新加入.

 -- 程式選項: --json-lines

     Parse every input line as separate JSON object.

     3.8 版新加入.

 -- 程式選項: -h, --help

     Show the help message.

註解
....


File: python.info,  Node: mailcap --- Mailcap file handling,  Next: mailbox --- Manipulate mailboxes in various formats,  Prev: json --- JSON encoder and decoder,  Up: Internet Data Handling

5.19.3 ‘mailcap’ — Mailcap file handling
----------------------------------------

`Source code:' Lib/mailcap.py(1)

__________________________________________________________________

Mailcap files are used to configure how MIME-aware applications such as
mail readers and Web browsers react to files with different MIME types.
(The name "mailcap" is derived from the phrase "mail capability".)  For
example, a mailcap file might contain a line like ‘video/mpeg; xmpeg
%s’.  Then, if the user encounters an email message or Web document with
the MIME type ‘video/mpeg’, ‘%s’ will be replaced by a filename (usually
one belonging to a temporary file) and the ‘xmpeg’ program can be
automatically started to view the file.

The mailcap format is documented in RFC 1524(2), "A User Agent
Configuration Mechanism For Multimedia Mail Format Information", but is
not an Internet standard.  However, mailcap files are supported on most
Unix systems.

 -- 函式: mailcap.findmatch (caps, MIMEtype, key='view',
          filename='/dev/null', plist=[])

     Return a 2-tuple; the first element is a string containing the
     command line to be executed (which can be passed to *note
     os.system(): dc6.), and the second element is the mailcap entry for
     a given MIME type.  If no matching MIME type can be found, ‘(None,
     None)’ is returned.

     `key' is the name of the field desired, which represents the type
     of activity to be performed; the default value is ’view’, since in
     the most common case you simply want to view the body of the
     MIME-typed data.  Other possible values might be ’compose’ and
     ’edit’, if you wanted to create a new body of the given MIME type
     or alter the existing body data.  See RFC 1524(3) for a complete
     list of these fields.

     `filename' is the filename to be substituted for ‘%s’ in the
     command line; the default value is ‘'/dev/null'’ which is almost
     certainly not what you want, so usually you’ll override it by
     specifying a filename.

     `plist' can be a list containing named parameters; the default
     value is simply an empty list.  Each entry in the list must be a
     string containing the parameter name, an equals sign (‘'='’), and
     the parameter’s value.  Mailcap entries can contain named
     parameters like ‘%{foo}’, which will be replaced by the value of
     the parameter named ’foo’.  For example, if the command line
     ‘showpartial %{id} %{number} %{total}’ was in a mailcap file, and
     `plist' was set to ‘['id=1', 'number=2', 'total=3']’, the resulting
     command line would be ‘'showpartial 1 2 3'’.

     In a mailcap file, the "test" field can optionally be specified to
     test some external condition (such as the machine architecture, or
     the window system in use) to determine whether or not the mailcap
     line applies.  *note findmatch(): 290c. will automatically check
     such conditions and skip the entry if the check fails.

 -- 函式: mailcap.getcaps ()

     Returns a dictionary mapping MIME types to a list of mailcap file
     entries.  This dictionary must be passed to the *note findmatch():
     290c. function.  An entry is stored as a list of dictionaries, but
     it shouldn’t be necessary to know the details of this
     representation.

     The information is derived from all of the mailcap files found on
     the system.  Settings in the user’s mailcap file ‘$HOME/.mailcap’
     will override settings in the system mailcap files ‘/etc/mailcap’,
     ‘/usr/etc/mailcap’, and ‘/usr/local/etc/mailcap’.

An example usage:

     >>> import mailcap
     >>> d = mailcap.getcaps()
     >>> mailcap.findmatch(d, 'video/mpeg', filename='tmp1223')
     ('xmpeg tmp1223', {'view': 'xmpeg %s'})

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/mailcap.py

   (2) https://tools.ietf.org/html/rfc1524.html

   (3) https://tools.ietf.org/html/rfc1524.html


File: python.info,  Node: mailbox --- Manipulate mailboxes in various formats,  Next: mimetypes --- Map filenames to MIME types,  Prev: mailcap --- Mailcap file handling,  Up: Internet Data Handling

5.19.4 ‘mailbox’ — Manipulate mailboxes in various formats
----------------------------------------------------------

`Source code:' Lib/mailbox.py(1)

__________________________________________________________________

This module defines two classes, *note Mailbox: be8. and *note Message:
bec, for accessing and manipulating on-disk mailboxes and the messages
they contain.  *note Mailbox: be8. offers a dictionary-like mapping from
keys to messages.  *note Message: bec. extends the *note email.message:
72. module’s *note Message: 546. class with format-specific state and
behavior.  Supported mailbox formats are Maildir, mbox, MH, Babyl, and
MMDF.

也參考
......

Module *note email: 69.

     Represent and manipulate messages.

* Menu:

* Mailbox objects::
* Message objects::
* Exceptions: Exceptions<12>.
* Examples: Examples<18>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/mailbox.py


File: python.info,  Node: Mailbox objects,  Next: Message objects,  Up: mailbox --- Manipulate mailboxes in various formats

5.19.4.1 ‘Mailbox’ objects
..........................

 -- 類別: mailbox.Mailbox

     A mailbox, which may be inspected and modified.

     The *note Mailbox: be8. class defines an interface and is not
     intended to be instantiated.  Instead, format-specific subclasses
     should inherit from *note Mailbox: be8. and your code should
     instantiate a particular subclass.

     The *note Mailbox: be8. interface is dictionary-like, with small
     keys corresponding to messages.  Keys are issued by the *note
     Mailbox: be8. instance with which they will be used and are only
     meaningful to that *note Mailbox: be8. 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 *note Mailbox: be8. instance using the
     set-like method *note add(): be7. and removed using a ‘del’
     statement or the set-like methods *note remove(): 2912. and *note
     discard(): 2913.

     *note Mailbox: be8. interface semantics differ from dictionary
     semantics in some noteworthy ways.  Each time a message is
     requested, a new representation (typically a *note Message: bec.
     instance) is generated based upon the current state of the mailbox.
     Similarly, when a message is added to a *note Mailbox: be8.
     instance, the provided message representation’s contents are
     copied.  In neither case is a reference to the message
     representation kept by the *note Mailbox: be8. instance.

     The default *note Mailbox: be8. iterator iterates over message
     representations, not keys as the default dictionary 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: 2c8. 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 Maildir; try to avoid
          using single-file formats such as mbox for concurrent writing.
          If you’re modifying a mailbox, you `must' lock it by calling
          the *note lock(): 2914. and *note unlock(): 2915. 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.

     *note Mailbox: be8. 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: bec. instance, an
          *note email.message.Message: 546. 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: bec. subclass (e.g., if it’s an
          *note mboxMessage: 27e2. instance and this is an *note mbox:
          2916. 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: 2c8. exception is
          raised if the method was called as *note remove(): 2912. or
          *note __delitem__(): 2917. but no exception is raised if the
          method was called as *note discard(): 2913.  The behavior of
          *note discard(): 2913. 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: 2c8. exception if no message already
          corresponds to `key'.

          As with *note add(): be7, parameter `message' may be a *note
          Message: bec. instance, an *note email.message.Message: 546.
          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:
          bec. subclass (e.g., if it’s an *note mboxMessage: 27e2.
          instance and this is an *note mbox: 2916. instance), its
          format-specific information is used.  Otherwise, the
          format-specific information of the message that currently
          corresponds to `key' is left unchanged.

      -- 成員函式: iterkeys ()
      -- 成員函式: keys ()

          Return an iterator over all keys if called as *note
          iterkeys(): 2919. or return a list of keys if called as *note
          keys(): 291a.

      -- 成員函式: itervalues ()
      -- 成員函式: __iter__ ()
      -- 成員函式: values ()

          Return an iterator over representations of all messages if
          called as *note itervalues(): 291b. or *note __iter__(): 291c.
          or return a list of such representations if called as *note
          values(): 291d.  The messages are represented as instances of
          the appropriate format-specific *note Message: bec. subclass
          unless a custom message factory was specified when the *note
          Mailbox: be8. instance was initialized.

               備註: The behavior of *note __iter__(): 291c. is unlike
               that of dictionaries, which iterate over keys.

      -- 成員函式: iteritems ()
      -- 成員函式: items ()

          Return an iterator over (`key', `message') pairs, where `key'
          is a key and `message' is a message representation, if called
          as *note iteritems(): 291e. or return a list of such pairs if
          called as *note items(): 291f.  The messages are represented
          as instances of the appropriate format-specific *note Message:
          bec. subclass unless a custom message factory was specified
          when the *note Mailbox: be8. instance was initialized.

      -- 成員函式: 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(): 2920. and a *note KeyError: 2c8.
          exception is raised if the method was called as *note
          __getitem__(): 2921.  The message is represented as an
          instance of the appropriate format-specific *note Message:
          bec. subclass unless a custom message factory was specified
          when the *note Mailbox: be8. 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: bec. subclass, or raise a *note KeyError: 2c8.
          exception if no such message exists.

      -- 成員函式: get_bytes (key)

          Return a byte representation of the message corresponding to
          `key', or raise a *note KeyError: 2c8. 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: 2c8. exception if no such
          message exists.  The message is processed through *note
          email.message.Message: 546. to convert it to a 7bit clean
          representation.

      -- 成員函式: get_file (key)

          Return a file-like representation of the message corresponding
          to `key', or raise a *note KeyError: 2c8. 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 binary file;
          previously it was incorrectly returned in text mode.  Also,
          the file-like object now supports the context management
          protocol: you can use a *note with: 6ee. statement to
          automatically close it.

               備註: Unlike other representations of messages, file-like
               representations are not necessarily independent of the
               *note Mailbox: be8. 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: bec. subclass
          unless a custom message factory was specified when the *note
          Mailbox: be8. 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: 2c8. exception.  The message is represented as an
          instance of the appropriate format-specific *note Message:
          bec. subclass unless a custom message factory was specified
          when the *note Mailbox: be8. 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__(): 2918.  As with *note __setitem__(): 2918,
          each `key' must already correspond to a message in the mailbox
          or else a *note KeyError: 2c8. exception will be raised, so in
          general it is incorrect for `arg' to be a *note Mailbox: be8.
          instance.

               備註: Unlike with dictionaries, keyword arguments are not
               supported.

      -- 成員函式: flush ()

          Write any pending changes to the filesystem.  For some *note
          Mailbox: be8. subclasses, changes are always written
          immediately and *note flush(): 2929. 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: 292a. 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 *note Mailbox: be8. subclasses, this method
          does nothing.

* Menu:

* Maildir::
* mbox::
* MH::
* Babyl::
* MMDF::


File: python.info,  Node: Maildir,  Next: mbox,  Up: Mailbox objects

5.19.4.2 ‘Maildir’
..................

 -- 類別: mailbox.Maildir (dirname, factory=None, create=True)

     A subclass of *note Mailbox: be8. 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: 292e. 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 *note Maildir: cad. 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".

          備註: 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.

     *note Maildir: cad. instances have all of the methods of *note
     Mailbox: be8. in addition to the following:

      -- 成員函式: list_folders ()

          Return a list of the names of all folders.

      -- 成員函式: get_folder (folder)

          Return a *note Maildir: cad. instance representing the folder
          whose name is `folder'.  A *note NoSuchMailboxError: 2931.
          exception is raised if the folder does not exist.

      -- 成員函式: add_folder (folder)

          Create a folder whose name is `folder' and return a *note
          Maildir: cad. instance representing it.

      -- 成員函式: remove_folder (folder)

          Delete the folder whose name is `folder'.  If the folder
          contains any messages, a *note NotEmptyError: 2934. 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.

     Some *note Mailbox: be8. methods implemented by *note Maildir: cad.
     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 ()

          *note Maildir: cad. 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) http://www.courier-mta.org/maildir.html

   (2) https://cr.yp.to/proto/maildir.html


File: python.info,  Node: mbox,  Next: MH,  Prev: Maildir,  Up: Mailbox objects

5.19.4.3 ‘mbox’
...............

 -- 類別: mailbox.mbox (path, factory=None, create=True)

     A subclass of *note Mailbox: be8. 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: 27e2. 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,
     *note mbox: 2916. 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: be8. methods implemented by *note mbox: 2916.
     deserve special remarks:

      -- 成員函式: get_file (key)

          Using the file after calling ‘flush()’ or ‘close()’ on the
          *note mbox: 2916. 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 objects

5.19.4.4 ‘MH’
.............

 -- 類別: mailbox.MH (path, factory=None, create=True)

     A subclass of *note Mailbox: be8. 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: 2946. 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 *note MH: 2945. 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.

     *note MH: 2945. instances have all of the methods of *note Mailbox:
     be8. in addition to the following:

      -- 成員函式: list_folders ()

          Return a list of the names of all folders.

      -- 成員函式: get_folder (folder)

          Return an *note MH: 2945. instance representing the folder
          whose name is `folder'.  A *note NoSuchMailboxError: 2931.
          exception is raised if the folder does not exist.

      -- 成員函式: add_folder (folder)

          Create a folder whose name is `folder' and return an *note MH:
          2945. instance representing it.

      -- 成員函式: remove_folder (folder)

          Delete the folder whose name is `folder'.  If the folder
          contains any messages, a *note NotEmptyError: 2934. 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(): 294b.

      -- 成員函式: 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: be8. methods implemented by *note MH: 2945.
     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 ()

          *note MH: 2945. instances do not keep any open files, so this
          method is equivalent to *note unlock(): 2952.

也參考
......

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) http://www.nongnu.org/nmh/

   (2) https://rand-mh.sourceforge.io/book/


File: python.info,  Node: Babyl,  Next: MMDF,  Prev: MH,  Up: Mailbox objects

5.19.4.5 ‘Babyl’
................

 -- 類別: mailbox.Babyl (path, factory=None, create=True)

     A subclass of *note Mailbox: be8. 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: 2959. 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.

     *note Babyl: 2958. instances have all of the methods of *note
     Mailbox: be8. 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: be8. methods implemented by *note Babyl: 2958.
     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: 7a0. 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 objects

5.19.4.6 ‘MMDF’
...............

 -- 類別: mailbox.MMDF (path, factory=None, create=True)

     A subclass of *note Mailbox: be8. 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: 2961. 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: be8. methods implemented by *note MMDF: 2960.
     deserve special remarks:

      -- 成員函式: get_file (key)

          Using the file after calling ‘flush()’ or ‘close()’ on the
          *note MMDF: 2960. 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 objects,  Next: Exceptions<12>,  Prev: Mailbox objects,  Up: mailbox --- Manipulate mailboxes in various formats

5.19.4.7 ‘Message’ objects
..........................

 -- 類別: mailbox.Message (message=None)

     A subclass of the *note email.message: 72. module’s *note Message:
     546.  Subclasses of *note mailbox.Message: bec. 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: 546.
     instance, its contents are copied; furthermore, any format-specific
     information is converted insofar as possible if `message' is a
     *note Message: bec. 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 *note Message: bec. instances be used
     to represent messages retrieved using *note Mailbox: be8.
     instances.  In some situations, the time and memory required to
     generate *note Message: bec. representations might not be
     acceptable.  For such situations, *note Mailbox: be8. instances
     also offer string and file-like representations, and a custom
     message factory may be specified when a *note Mailbox: be8.
     instance is initialized.

* Menu:

* MaildirMessage::
* mboxMessage::
* MHMessage::
* BabylMessage::
* MMDFMessage::

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2822.html


File: python.info,  Node: MaildirMessage,  Next: mboxMessage,  Up: Message objects

5.19.4.8 ‘MaildirMessage’
.........................

 -- 類別: mailbox.MaildirMessage (message=None)

     A message with Maildir-specific behaviors.  Parameter `message' has
     the same meaning as with the *note Message: bec. 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       Meaning       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
                              

     *note MaildirMessage: 292e. 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 is 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 *note MaildirMessage: 292e. instance is created based upon an
*note mboxMessage: 27e2. or *note MMDFMessage: 2961. instance, the
‘Status’ and ‘X-Status’ headers are omitted and the following
conversions take place:

Resulting state          *note mboxMessage: 27e2. or
                         *note MMDFMessage: 2961. state
                         
----------------------------------------------------------------------------
                         
"cur" subdirectory       O flag
                         
                         
F flag                   F flag
                         
                         
R flag                   A flag
                         
                         
S flag                   R flag
                         
                         
T flag                   D flag
                         

When a *note MaildirMessage: 292e. instance is created based upon an
*note MHMessage: 2946. instance, the following conversions take place:

Resulting state                     *note MHMessage: 2946. state
                                    
-------------------------------------------------------------------
                                    
"cur" subdirectory                  "unseen" sequence
                                    
                                    
"cur" subdirectory and S flag       no "unseen" sequence
                                    
                                    
F flag                              "flagged" sequence
                                    
                                    
R flag                              "replied" sequence
                                    

When a *note MaildirMessage: 292e. instance is created based upon a
*note BabylMessage: 2959. instance, the following conversions take
place:

Resulting state                     *note BabylMessage: 2959. 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 objects

5.19.4.9 ‘mboxMessage’
......................

 -- 類別: mailbox.mboxMessage (message=None)

     A message with mbox-specific behaviors.  Parameter `message' has
     the same meaning as with the *note Message: bec. 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       Meaning        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.

     *note mboxMessage: 27e2. 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: 59e.
          instance, a tuple suitable for passing to *note
          time.strftime(): b6a, or ‘True’ (to use *note time.gmtime():
          b44.).

      -- 成員函式: 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 *note mboxMessage: 27e2. instance is created based upon a *note
MaildirMessage: 292e. instance, a "From " line is generated based upon
the *note MaildirMessage: 292e. instance’s delivery date, and the
following conversions take place:

Resulting state       *note MaildirMessage: 292e. state
                      
----------------------------------------------------------
                      
R flag                S flag
                      
                      
O flag                "cur" subdirectory
                      
                      
D flag                T flag
                      
                      
F flag                F flag
                      
                      
A flag                R flag
                      

When an *note mboxMessage: 27e2. instance is created based upon an *note
MHMessage: 2946. instance, the following conversions take place:

Resulting state         *note MHMessage: 2946. state
                        
-------------------------------------------------------
                        
R flag and O flag       no "unseen" sequence
                        
                        
O flag                  "unseen" sequence
                        
                        
F flag                  "flagged" sequence
                        
                        
A flag                  "replied" sequence
                        

When an *note mboxMessage: 27e2. instance is created based upon a *note
BabylMessage: 2959. instance, the following conversions take place:

Resulting state         *note BabylMessage: 2959. state
                        
----------------------------------------------------------
                        
R flag and O flag       no "unseen" label
                        
                        
O flag                  "unseen" label
                        
                        
D flag                  "deleted" label
                        
                        
A flag                  "answered" label
                        

When a *note Message: bec. instance is created based upon an *note
MMDFMessage: 2961. instance, the "From " line is copied and all flags
directly correspond:

Resulting state       *note MMDFMessage: 2961. 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 objects

5.19.4.10 ‘MHMessage’
.....................

 -- 類別: mailbox.MHMessage (message=None)

     A message with MH-specific behaviors.  Parameter `message' has the
     same meaning as with the *note Message: bec. 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
                    

     *note MHMessage: 2946. 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 *note MHMessage: 2946. instance is created based upon a *note
MaildirMessage: 292e. instance, the following conversions take place:

Resulting state          *note MaildirMessage: 292e. state
                         
-------------------------------------------------------------
                         
"unseen" sequence        no S flag
                         
                         
"replied" sequence       R flag
                         
                         
"flagged" sequence       F flag
                         

When an *note MHMessage: 2946. instance is created based upon an *note
mboxMessage: 27e2. or *note MMDFMessage: 2961. instance, the ‘Status’
and ‘X-Status’ headers are omitted and the following conversions take
place:

Resulting state          *note mboxMessage: 27e2. or
                         *note MMDFMessage: 2961. state
                         
----------------------------------------------------------------------------
                         
"unseen" sequence        no R flag
                         
                         
"replied" sequence       A flag
                         
                         
"flagged" sequence       F flag
                         

When an *note MHMessage: 2946. instance is created based upon a *note
BabylMessage: 2959. instance, the following conversions take place:

Resulting state          *note BabylMessage: 2959. state
                         
-----------------------------------------------------------
                         
"unseen" sequence        "unseen" label
                         
                         
"replied" sequence       "answered" label
                         


File: python.info,  Node: BabylMessage,  Next: MMDFMessage,  Prev: MHMessage,  Up: Message objects

5.19.4.11 ‘BabylMessage’
........................

 -- 類別: mailbox.BabylMessage (message=None)

     A message with Babyl-specific behaviors.  Parameter `message' has
     the same meaning as with the *note Message: bec. 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 *note
     BabylMessage: 2959. class, though, uses the original headers
     because they are more complete.  Visible headers may be accessed
     explicitly if desired.

     *note BabylMessage: 2959. 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 an *note Message: bec. 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: bec. instance, an *note email.message.Message: 546.
          instance, a string, or a file-like object (which should be
          open in text mode).

      -- 成員函式: update_visible ()

          When a *note BabylMessage: 2959. 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 *note BabylMessage: 2959. instance is created based upon a *note
MaildirMessage: 292e. instance, the following conversions take place:

Resulting state         *note MaildirMessage: 292e. state
                        
------------------------------------------------------------
                        
"unseen" label          no S flag
                        
                        
"deleted" label         T flag
                        
                        
"answered" label        R flag
                        
                        
"forwarded" label       P flag
                        

When a *note BabylMessage: 2959. instance is created based upon an *note
mboxMessage: 27e2. or *note MMDFMessage: 2961. instance, the ‘Status’
and ‘X-Status’ headers are omitted and the following conversions take
place:

Resulting state        *note mboxMessage: 27e2. or
                       *note MMDFMessage: 2961. state
                       
--------------------------------------------------------------------------
                       
"unseen" label         no R flag
                       
                       
"deleted" label        D flag
                       
                       
"answered" label       A flag
                       

When a *note BabylMessage: 2959. instance is created based upon an *note
MHMessage: 2946. instance, the following conversions take place:

Resulting state        *note MHMessage: 2946. state
                       
------------------------------------------------------
                       
"unseen" label         "unseen" sequence
                       
                       
"answered" label       "replied" sequence
                       


File: python.info,  Node: MMDFMessage,  Prev: BabylMessage,  Up: Message objects

5.19.4.12 ‘MMDFMessage’
.......................

 -- 類別: mailbox.MMDFMessage (message=None)

     A message with MMDF-specific behaviors.  Parameter `message' has
     the same meaning as with the *note Message: bec. 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       Meaning        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.

     *note MMDFMessage: 2961. instances offer the following methods,
     which are identical to those offered by *note mboxMessage: 27e2.:

      -- 成員函式: 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: 59e.
          instance, a tuple suitable for passing to *note
          time.strftime(): b6a, or ‘True’ (to use *note time.gmtime():
          b44.).

      -- 成員函式: 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 *note MMDFMessage: 2961. instance is created based upon a *note
MaildirMessage: 292e. instance, a "From " line is generated based upon
the *note MaildirMessage: 292e. instance’s delivery date, and the
following conversions take place:

Resulting state       *note MaildirMessage: 292e. state
                      
----------------------------------------------------------
                      
R flag                S flag
                      
                      
O flag                "cur" subdirectory
                      
                      
D flag                T flag
                      
                      
F flag                F flag
                      
                      
A flag                R flag
                      

When an *note MMDFMessage: 2961. instance is created based upon an *note
MHMessage: 2946. instance, the following conversions take place:

Resulting state         *note MHMessage: 2946. state
                        
-------------------------------------------------------
                        
R flag and O flag       no "unseen" sequence
                        
                        
O flag                  "unseen" sequence
                        
                        
F flag                  "flagged" sequence
                        
                        
A flag                  "replied" sequence
                        

When an *note MMDFMessage: 2961. instance is created based upon a *note
BabylMessage: 2959. instance, the following conversions take place:

Resulting state         *note BabylMessage: 2959. state
                        
----------------------------------------------------------
                        
R flag and O flag       no "unseen" label
                        
                        
O flag                  "unseen" label
                        
                        
D flag                  "deleted" label
                        
                        
A flag                  "answered" label
                        

When an *note MMDFMessage: 2961. instance is created based upon an *note
mboxMessage: 27e2. instance, the "From " line is copied and all flags
directly correspond:

Resulting state       *note mboxMessage: 27e2. 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: Exceptions<12>,  Next: Examples<18>,  Prev: Message objects,  Up: mailbox --- Manipulate mailboxes in various formats

5.19.4.13 Exceptions
....................

The following exception classes are defined in the *note mailbox: af.
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: be8. 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: 2945. instance attempts to read a corrupted
     ‘.mh_sequences’ file.


File: python.info,  Node: Examples<18>,  Prev: Exceptions<12>,  Up: mailbox --- Manipulate mailboxes in various formats

5.19.4.14 Examples
..................

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']       # Could possibly be 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 --- Map filenames to MIME types,  Next: base64 —— Base16、Base32、Base64、Base85 資料編碼,  Prev: mailbox --- Manipulate mailboxes in various formats,  Up: Internet Data Handling

5.19.5 ‘mimetypes’ — Map filenames to MIME types
------------------------------------------------

`Source code:' Lib/mimetypes.py(1)

__________________________________________________________________

The *note mimetypes: b3. 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(): 2999. if they rely on the information *note init(): 2999. 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: 36f.

     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:
     36f.

 -- 函式: 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(): f6e.

     The optional `strict' argument has the same meaning as with the
     *note guess_type(): f6e. 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(): f6e.  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(): f6e. 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: 299c.; on Windows, the current registry settings
     are loaded.  Each file named in `files' or *note knownfiles: 299c.
     takes precedence over those named before it.  Calling *note init():
     2999. 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.

 -- Data: mimetypes.inited

     Flag indicating whether or not the global data structures have been
     initialized.  This is set to ‘True’ by *note init(): 2999.

 -- Data: 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.

 -- Data: 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.

 -- Data: mimetypes.encodings_map

     Dictionary mapping filename extensions to encoding types.

 -- Data: mimetypes.types_map

     Dictionary mapping filename extensions to MIME types.

 -- Data: mimetypes.common_types

     Dictionary mapping filename extensions to non-standard, but
     commonly found MIME types.

An example usage of the module:

     >>> 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 Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/mimetypes.py

   (2) https://www.iana.org/assignments/media-types/media-types.xhtml


File: python.info,  Node: MimeTypes Objects,  Up: mimetypes --- Map filenames to MIME types

5.19.5.1 MimeTypes Objects
..........................

The *note MimeTypes: 29a5. 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: b3. 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(): 29a6. or *note readfp(): 29a7.
     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: 299f. defined
          in the module.

      -- 屬性: encodings_map

          Dictionary mapping filename extensions to encoding types.
          This is initially a copy of the global *note encodings_map:
          29a0. 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: 29a2. and *note types_map:
          29a1.

      -- 屬性: 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: 29a2. and
          *note types_map: 29a1.

      -- 成員函式: guess_extension (type, strict=True)

          Similar to the *note guess_extension(): 299b. function, using
          the tables stored as part of the object.

      -- 成員函式: guess_type (url, strict=True)

          Similar to the *note guess_type(): f6e. function, using the
          tables stored as part of the object.

      -- 成員函式: guess_all_extensions (type, strict=True)

          Similar to the *note guess_all_extensions(): 299a. 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(): 29a7. 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 Availability: 1364.: 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 版新加入.


File: python.info,  Node: base64 —— Base16、Base32、Base64、Base85 資料編碼,  Next: binhex --- Encode and decode binhex4 files,  Prev: mimetypes --- Map filenames to MIME types,  Up: Internet Data Handling

5.19.6 ‘base64’ —— Base16、Base32、Base64、Base85 資料編碼
----------------------------------------------------------

`Source code:' Lib/base64.py(1)

__________________________________________________________________

這個模組提供將二進位資料編碼成可顯示 ASCII 字元以及解碼回原始資料的功能
，包括了 RFC 3548(2)中的 Base16、Base32、Base64 等編碼方式，以及標準
Ascii85、Base85 編碼等。

RFC 3548(3)標準編碼可以使電子郵件、URL，或是 HTTP POST 內容等傳輸管道安
全地傳遞資料。這些編碼演算法與‘uuencode’ 並不相同。

There are two interfaces provided by this module.  The modern interface
supports encoding *note bytes-like objects: 5ed. to ASCII *note bytes:
336, and decoding *note bytes-like objects: 5ed. or strings containing
ASCII to *note bytes: 336.  Both base-64 alphabets defined in RFC
3548(4) (normal, and URL- and filesystem-safe) are supported.

The legacy interface does not support decoding from strings, but it does
provide functions for encoding and decoding to and from *note file
objects: b47.  It only supports the Base64 standard alphabet, and it
adds newlines every 76 characters as per RFC 2045(5).  Note that if you
are looking for RFC 2045(6) support you probably want to be looking at
the *note email: 69. package instead.

3.3 版更變: ASCII-only Unicode strings are now accepted by the decoding
functions of the modern interface.

3.4 版更變: Any *note bytes-like objects: 5ed. are now accepted by all
encoding and decoding functions in this module.  Ascii85/Base85 support
added.

The modern interface provides:

 -- 函式: base64.b64encode (s, altchars=None)

     Encode the *note bytes-like object: 5ed. `s' using Base64 and
     return the encoded *note bytes: 336.

     Optional `altchars' must be a *note bytes-like object: 5ed. of at
     least length 2 (additional characters are ignored) which specifies
     an alternative alphabet for the ‘+’ and ‘/’ characters.  This
     allows an application to e.g.  generate URL or filesystem safe
     Base64 strings.  The default is ‘None’, for which the standard
     Base64 alphabet is used.

 -- 函式: base64.b64decode (s, altchars=None, validate=False)

     Decode the Base64 encoded *note bytes-like object: 5ed. or ASCII
     string `s' and return the decoded *note bytes: 336.

     Optional `altchars' must be a *note bytes-like object: 5ed. or
     ASCII string of at least length 2 (additional characters are
     ignored) which specifies the alternative alphabet used instead of
     the ‘+’ and ‘/’ characters.

     A *note binascii.Error: 963. exception is raised if `s' is
     incorrectly padded.

     If `validate' is ‘False’ (the default), characters that are neither
     in the normal base-64 alphabet nor the alternative alphabet are
     discarded prior to the padding check.  If `validate' is ‘True’,
     these non-alphabet characters in the input result in a *note
     binascii.Error: 963.

 -- 函式: base64.standard_b64encode (s)

     Encode *note bytes-like object: 5ed. `s' using the standard Base64
     alphabet and return the encoded *note bytes: 336.

 -- 函式: base64.standard_b64decode (s)

     Decode *note bytes-like object: 5ed. or ASCII string `s' using the
     standard Base64 alphabet and return the decoded *note bytes: 336.

 -- 函式: base64.urlsafe_b64encode (s)

     Encode *note bytes-like object: 5ed. `s' using the URL- and
     filesystem-safe alphabet, which substitutes ‘-’ instead of ‘+’ and
     ‘_’ instead of ‘/’ in the standard Base64 alphabet, and return the
     encoded *note bytes: 336.  The result can still contain ‘=’.

 -- 函式: base64.urlsafe_b64decode (s)

     Decode *note bytes-like object: 5ed. or ASCII string `s' using the
     URL- and filesystem-safe alphabet, which substitutes ‘-’ instead of
     ‘+’ and ‘_’ instead of ‘/’ in the standard Base64 alphabet, and
     return the decoded *note bytes: 336.

 -- 函式: base64.b32encode (s)

     Encode the *note bytes-like object: 5ed. `s' using Base32 and
     return the encoded *note bytes: 336.

 -- 函式: base64.b32decode (s, casefold=False, map01=None)

     Decode the Base32 encoded *note bytes-like object: 5ed. or ASCII
     string `s' and return the decoded *note bytes: 336.

     Optional `casefold' is a flag specifying whether a lowercase
     alphabet is acceptable as input.  For security purposes, the
     default is ‘False’.

     RFC 3548(7) allows for optional mapping of the digit 0 (zero) to
     the letter O (oh), and for optional mapping of the digit 1 (one) to
     either the letter I (eye) or letter L (el).  The optional argument
     `map01' when not ‘None’, specifies which letter the digit 1 should
     be mapped to (when `map01' is not ‘None’, the digit 0 is always
     mapped to the letter O). For security purposes the default is
     ‘None’, so that 0 and 1 are not allowed in the input.

     A *note binascii.Error: 963. is raised if `s' is incorrectly padded
     or if there are non-alphabet characters present in the input.

 -- 函式: base64.b16encode (s)

     Encode the *note bytes-like object: 5ed. `s' using Base16 and
     return the encoded *note bytes: 336.

 -- 函式: base64.b16decode (s, casefold=False)

     Decode the Base16 encoded *note bytes-like object: 5ed. or ASCII
     string `s' and return the decoded *note bytes: 336.

     Optional `casefold' is a flag specifying whether a lowercase
     alphabet is acceptable as input.  For security purposes, the
     default is ‘False’.

     A *note binascii.Error: 963. is raised if `s' is incorrectly padded
     or if there are non-alphabet characters present in the input.

 -- 函式: base64.a85encode (b, *, foldspaces=False, wrapcol=0,
          pad=False, adobe=False)

     Encode the *note bytes-like object: 5ed. `b' using Ascii85 and
     return the encoded *note bytes: 336.

     `foldspaces' is an optional flag that uses the special short
     sequence ’y’ instead of 4 consecutive spaces (ASCII 0x20) as
     supported by ’btoa’.  This feature is not supported by the
     "standard" Ascii85 encoding.

     `wrapcol' controls whether the output should have newline (‘b'\n'’)
     characters added to it.  If this is non-zero, each output line will
     be at most this many characters long.

     `pad' controls whether the input is padded to a multiple of 4
     before encoding.  Note that the ‘btoa’ implementation always pads.

     `adobe' controls whether the encoded byte sequence is framed with
     ‘<~’ and ‘~>’, which is used by the Adobe implementation.

     3.4 版新加入.

 -- 函式: base64.a85decode (b, *, foldspaces=False, adobe=False,
          ignorechars=b' \t\n\r\v')

     Decode the Ascii85 encoded *note bytes-like object: 5ed. or ASCII
     string `b' and return the decoded *note bytes: 336.

     `foldspaces' is a flag that specifies whether the ’y’ short
     sequence should be accepted as shorthand for 4 consecutive spaces
     (ASCII 0x20).  This feature is not supported by the "standard"
     Ascii85 encoding.

     `adobe' controls whether the input sequence is in Adobe Ascii85
     format (i.e.  is framed with <~ and ~>).

     `ignorechars' should be a *note bytes-like object: 5ed. or ASCII
     string containing characters to ignore from the input.  This should
     only contain whitespace characters, and by default contains all
     whitespace characters in ASCII.

     3.4 版新加入.

 -- 函式: base64.b85encode (b, pad=False)

     Encode the *note bytes-like object: 5ed. `b' using base85 (as used
     in e.g.  git-style binary diffs) and return the encoded *note
     bytes: 336.

     If `pad' is true, the input is padded with ‘b'\0'’ so its length is
     a multiple of 4 bytes before encoding.

     3.4 版新加入.

 -- 函式: base64.b85decode (b)

     Decode the base85-encoded *note bytes-like object: 5ed. or ASCII
     string `b' and return the decoded *note bytes: 336.  Padding is
     implicitly removed, if necessary.

     3.4 版新加入.

The legacy interface:

 -- 函式: base64.decode (input, output)

     Decode the contents of the binary `input' file and write the
     resulting binary data to the `output' file.  `input' and `output'
     must be *note file objects: b47.  `input' will be read until
     ‘input.readline()’ returns an empty bytes object.

 -- 函式: base64.decodebytes (s)

     Decode the *note bytes-like object: 5ed. `s', which must contain
     one or more lines of base64 encoded data, and return the decoded
     *note bytes: 336.

     3.1 版新加入.

 -- 函式: base64.decodestring (s)

     Deprecated alias of *note decodebytes(): 187a.

     3.1 版後已棄用.

 -- 函式: base64.encode (input, output)

     Encode the contents of the binary `input' file and write the
     resulting base64 encoded data to the `output' file.  `input' and
     `output' must be *note file objects: b47.  `input' will be read
     until ‘input.read()’ returns an empty bytes object.  *note
     encode(): 29bb. inserts a newline character (‘b'\n'’) after every
     76 bytes of the output, as well as ensuring that the output always
     ends with a newline, as per RFC 2045(8) (MIME).

 -- 函式: base64.encodebytes (s)

     Encode the *note bytes-like object: 5ed. `s', which can contain
     arbitrary binary data, and return *note bytes: 336. containing the
     base64-encoded data, with newlines (‘b'\n'’) inserted after every
     76 bytes of output, and ensuring that there is a trailing newline,
     as per RFC 2045(9) (MIME).

     3.1 版新加入.

 -- 函式: base64.encodestring (s)

     Deprecated alias of *note encodebytes(): 1879.

     3.1 版後已棄用.

An example usage of the module:

     >>> import base64
     >>> encoded = base64.b64encode(b'data to be encoded')
     >>> encoded
     b'ZGF0YSB0byBiZSBlbmNvZGVk'
     >>> data = base64.b64decode(encoded)
     >>> data
     b'data to be encoded'

也參考
......

Module *note binascii: 10.

     Support module containing ASCII-to-binary and binary-to-ASCII
     conversions.

RFC 1521(10) - MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies

     Section 5.2, "Base64 Content-Transfer-Encoding," provides the
     definition of the base64 encoding.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/base64.py

   (2) https://tools.ietf.org/html/rfc3548.html

   (3) https://tools.ietf.org/html/rfc3548.html

   (4) https://tools.ietf.org/html/rfc3548.html

   (5) https://tools.ietf.org/html/rfc2045.html

   (6) https://tools.ietf.org/html/rfc2045.html

   (7) https://tools.ietf.org/html/rfc3548.html

   (8) https://tools.ietf.org/html/rfc2045.html

   (9) https://tools.ietf.org/html/rfc2045.html

   (10) https://tools.ietf.org/html/rfc1521.html


File: python.info,  Node: binhex --- Encode and decode binhex4 files,  Next: binascii --- Convert between binary and ASCII,  Prev: base64 —— Base16、Base32、Base64、Base85 資料編碼,  Up: Internet Data Handling

5.19.7 ‘binhex’ — Encode and decode binhex4 files
-------------------------------------------------

`Source code:' Lib/binhex.py(1)

__________________________________________________________________

This module encodes and decodes files in binhex4 format, a format
allowing representation of Macintosh files in ASCII. Only the data fork
is handled.

The *note binhex: 11. module defines the following functions:

 -- 函式: binhex.binhex (input, output)

     Convert a binary file with filename `input' to binhex file
     `output'.  The `output' parameter can either be a filename or a
     file-like object (any object supporting a ‘write()’ and ‘close()’
     method).

 -- 函式: binhex.hexbin (input, output)

     Decode a binhex file `input'.  `input' may be a filename or a
     file-like object supporting ‘read()’ and ‘close()’ methods.  The
     resulting file is written to a file named `output', unless the
     argument is ‘None’ in which case the output filename is read from
     the binhex file.

The following exception is also defined:

 -- 例外: binhex.Error

     Exception raised when something can’t be encoded using the binhex
     format (for example, a filename is too long to fit in the filename
     field), or when input is not properly encoded binhex data.

也參考
......

Module *note binascii: 10.

     Support module containing ASCII-to-binary and binary-to-ASCII
     conversions.

* Menu:

* 註解: 註解<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/binhex.py


File: python.info,  Node: 註解<2>,  Up: binhex --- Encode and decode binhex4 files

5.19.7.1 註解
.............

There is an alternative, more powerful interface to the coder and
decoder, see the source for details.

If you code or decode textfiles on non-Macintosh platforms they will
still use the old Macintosh newline convention (carriage-return as end
of line).


File: python.info,  Node: binascii --- Convert between binary and ASCII,  Next: quopri --- Encode and decode MIME quoted-printable data,  Prev: binhex --- Encode and decode binhex4 files,  Up: Internet Data Handling

5.19.8 ‘binascii’ — Convert between binary and ASCII
----------------------------------------------------

__________________________________________________________________

The *note binascii: 10. 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 uu: 124, *note base64: e, or *note binhex: 11.
instead.  The *note binascii: 10. 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: 5ed. (such as *note bytes: 336, *note bytearray: 337. and
     other objects that support the buffer protocol).

     3.3 版更變: ASCII-only unicode strings are now accepted by the
     ‘a2b_*’ functions.

The *note binascii: 10. 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 版更變: Added the `backtick' parameter.

 -- 函式: binascii.a2b_base64 (string)

     Convert a block of base64 data back to binary and return the binary
     data.  More than one line may be passed at a time.

 -- 函式: 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(1).

     3.6 版更變: Added the `newline' parameter.

 -- 函式: 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(2).  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.a2b_hqx (string)

     Convert binhex4 formatted ASCII data to binary, without doing
     RLE-decompression.  The string should contain a complete number of
     binary bytes, or (in case of the last portion of the binhex4 data)
     have the remaining bits zero.

 -- 函式: binascii.rledecode_hqx (data)

     Perform RLE-decompression on the data, as per the binhex4 standard.
     The algorithm uses ‘0x90’ after a byte as a repeat indicator,
     followed by a count.  A count of ‘0’ specifies a byte value of
     ‘0x90’.  The routine returns the decompressed data, unless data
     input data ends in an orphaned repeat indicator, in which case the
     *note Incomplete: 29cc. exception is raised.

     3.2 版更變: Accept only bytestring or bytearray objects as input.

 -- 函式: binascii.rlecode_hqx (data)

     Perform binhex4 style RLE-compression on `data' and return the
     result.

 -- 函式: binascii.b2a_hqx (data)

     Perform hexbin4 binary-to-ASCII translation and return the
     resulting string.  The argument should already be RLE-coded, and
     have a length divisible by 3 (except possibly the last fragment).

 -- 函式: 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 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.  To generate the same
     numeric value across all Python versions and platforms, use
     ‘crc32(data) & 0xffffffff’.

 -- 函式: 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(): 636. 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 版更變: The `sep' and `bytes_per_sep' parameters were added.

 -- 函式: 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(): 187c.
     `hexstr' must contain an even number of hexadecimal digits (which
     can be upper or lower case), otherwise an *note Error: 963.
     exception is raised.

     Similar functionality (accepting only text string arguments, but
     more liberal towards whitespace) is also accessible using the *note
     bytes.fromhex(): 333. 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.

也參考
......

Module *note base64: e.

     Support for RFC compliant base64-style encoding in base 16, 32, 64,
     and 85.

Module *note binhex: 11.

     Support for the binhex format used on the Macintosh.

Module *note uu: 124.

     Support for UU encoding used on Unix.

Module *note quopri: dc.

     Support for quoted-printable encoding used in MIME email messages.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc3548.html

   (2) https://tools.ietf.org/html/rfc1522.html


File: python.info,  Node: quopri --- Encode and decode MIME quoted-printable data,  Next: uu --- Encode and decode uuencode files,  Prev: binascii --- Convert between binary and ASCII,  Up: Internet Data Handling

5.19.9 ‘quopri’ — Encode and decode MIME quoted-printable data
--------------------------------------------------------------

`Source code:' Lib/quopri.py(1)

__________________________________________________________________

This module performs quoted-printable transport encoding and decoding,
as defined in RFC 1521(2): "MIME (Multipurpose Internet Mail Extensions)
Part One: Mechanisms for Specifying and Describing the Format of
Internet Message Bodies".  The quoted-printable encoding is designed for
data where there are relatively few nonprintable characters; the base64
encoding scheme available via the *note base64: e. module is more
compact if there are many such characters, as when sending a graphics
file.

 -- 函式: quopri.decode (input, output, header=False)

     Decode the contents of the `input' file and write the resulting
     decoded binary data to the `output' file.  `input' and `output'
     must be *note binary file objects: b47.  If the optional argument
     `header' is present and true, underscore will be decoded as space.
     This is used to decode "Q"-encoded headers as described in RFC
     1522(3): "MIME (Multipurpose Internet Mail Extensions) Part Two:
     Message Header Extensions for Non-ASCII Text".

 -- 函式: quopri.encode (input, output, quotetabs, header=False)

     Encode the contents of the `input' file and write the resulting
     quoted-printable data to the `output' file.  `input' and `output'
     must be *note binary file objects: b47.  `quotetabs', a
     non-optional flag which controls whether to encode embedded spaces
     and tabs; when true it encodes such embedded whitespace, and when
     false it leaves them unencoded.  Note that spaces and tabs
     appearing at the end of lines are always encoded, as per RFC
     1521(4).  `header' is a flag which controls if spaces are encoded
     as underscores as per RFC 1522(5).

 -- 函式: quopri.decodestring (s, header=False)

     Like *note decode(): 187f, except that it accepts a source *note
     bytes: 336. and returns the corresponding decoded *note bytes: 336.

 -- 函式: quopri.encodestring (s, quotetabs=False, header=False)

     Like *note encode(): 187e, except that it accepts a source *note
     bytes: 336. and returns the corresponding encoded *note bytes: 336.
     By default, it sends a ‘False’ value to `quotetabs' parameter of
     the *note encode(): 187e. function.

也參考
......

Module *note base64: e.

     Encode and decode MIME base64 data

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/quopri.py

   (2) https://tools.ietf.org/html/rfc1521.html

   (3) https://tools.ietf.org/html/rfc1522.html

   (4) https://tools.ietf.org/html/rfc1521.html

   (5) https://tools.ietf.org/html/rfc1522.html


File: python.info,  Node: uu --- Encode and decode uuencode files,  Prev: quopri --- Encode and decode MIME quoted-printable data,  Up: Internet Data Handling

5.19.10 ‘uu’ — Encode and decode uuencode files
-----------------------------------------------

`Source code:' Lib/uu.py(1)

__________________________________________________________________

This module encodes and decodes files in uuencode format, allowing
arbitrary binary data to be transferred over ASCII-only connections.
Wherever a file argument is expected, the methods accept a file-like
object.  For backwards compatibility, a string containing a pathname is
also accepted, and the corresponding file will be opened for reading and
writing; the pathname ‘'-'’ is understood to mean the standard input or
output.  However, this interface is deprecated; it’s better for the
caller to open the file itself, and be sure that, when required, the
mode is ‘'rb'’ or ‘'wb'’ on Windows.

This code was contributed by Lance Ellinghouse, and modified by Jack
Jansen.

The *note uu: 124. module defines the following functions:

 -- 函式: uu.encode (in_file, out_file, name=None, mode=None, *,
          backtick=False)

     Uuencode file `in_file' into file `out_file'.  The uuencoded file
     will have the header specifying `name' and `mode' as the defaults
     for the results of decoding the file.  The default defaults are
     taken from `in_file', or ‘'-'’ and ‘0o666’ respectively.  If
     `backtick' is true, zeros are represented by ‘'`'’ instead of
     spaces.

     3.7 版更變: Added the `backtick' parameter.

 -- 函式: uu.decode (in_file, out_file=None, mode=None, quiet=False)

     This call decodes uuencoded file `in_file' placing the result on
     file `out_file'.  If `out_file' is a pathname, `mode' is used to
     set the permission bits if the file must be created.  Defaults for
     `out_file' and `mode' are taken from the uuencode header.  However,
     if the file specified in the header already exists, a *note
     uu.Error: 29d7. is raised.

     *note decode(): 1880. may print a warning to standard error if the
     input was produced by an incorrect uuencoder and Python could
     recover from that error.  Setting `quiet' to a true value silences
     this warning.

 -- 例外: uu.Error

     Subclass of *note Exception: 1aa, this can be raised by *note
     uu.decode(): 1880. under various situations, such as described
     above, but also including a badly formatted header, or truncated
     input file.

也參考
......

Module *note binascii: 10.

     Support module containing ASCII-to-binary and binary-to-ASCII
     conversions.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/uu.py


File: python.info,  Node: Structured Markup Processing Tools,  Next: Internet Protocols and Support,  Prev: Internet Data Handling,  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 --- HyperText Markup Language support. HyperText Markup Language support
* html.parser: html parser --- Simple HTML and XHTML parser. Simple HTML and XHTML parser
* html.entities: html entities --- Definitions of HTML general entities. Definitions of HTML general entities
* XML 處理模組::
* xml.etree.ElementTree: xml etree ElementTree --- The ElementTree XML API. The ElementTree XML API
* xml.dom: xml dom --- The Document Object Model API. The Document Object Model API
* xml.dom.minidom: xml dom minidom --- Minimal DOM implementation. Minimal DOM implementation
* xml.dom.pulldom: xml dom pulldom --- Support for building partial DOM trees. Support for building partial DOM trees
* xml.sax: xml sax --- Support for SAX2 parsers. Support for SAX2 parsers
* xml.sax.handler: xml sax handler --- Base classes for SAX handlers. Base classes for SAX handlers
* xml.sax.saxutils: xml sax saxutils --- SAX Utilities. SAX Utilities
* xml.sax.xmlreader: xml sax xmlreader --- Interface for XML parsers. Interface for XML parsers
* xml.parsers.expat: xml parsers expat --- Fast XML parsing using Expat. Fast XML parsing using Expat


File: python.info,  Node: html --- HyperText Markup Language support,  Next: html parser --- Simple HTML and XHTML parser,  Up: Structured Markup Processing Tools

5.20.1 ‘html’ — HyperText Markup Language support
-------------------------------------------------

`Source code:' Lib/html/__init__.py(1)

__________________________________________________________________

This module defines utilities to manipulate HTML.

 -- 函式: html.escape (s, quote=True)

     Convert the characters ‘&’, ‘<’ and ‘>’ in string `s' to HTML-safe
     sequences.  Use this if you need to display text that might contain
     such characters in HTML. If the optional flag `quote' is true, the
     characters (‘"’) and (‘'’) are also translated; this helps for
     inclusion in an HTML attribute value delimited by quotes, as in ‘<a
     href="...">’.

     3.2 版新加入.

 -- 函式: html.unescape (s)

     Convert all named and numeric character references (e.g.  ‘&gt;’,
     ‘&#62;’, ‘&#x3e;’) in the string `s' to the corresponding Unicode
     characters.  This function uses the rules defined by the HTML 5
     standard for both valid and invalid character references, and the
     *note list of HTML 5 named character references: a1a.

     3.4 版新加入.

__________________________________________________________________

Submodules in the ‘html’ package are:

   * *note html.parser: 92. – HTML/XHTML parser with lenient parsing
     mode

   * *note html.entities: 91. – HTML entity definitions

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/html/__init__.py


File: python.info,  Node: html parser --- Simple HTML and XHTML parser,  Next: html entities --- Definitions of HTML general entities,  Prev: html --- HyperText Markup Language support,  Up: Structured Markup Processing Tools

5.20.2 ‘html.parser’ — Simple HTML and XHTML parser
---------------------------------------------------

`Source code:' Lib/html/parser.py(1)

__________________________________________________________________

This module defines a class *note HTMLParser: 7c4. which serves as the
basis for parsing text files formatted in HTML (HyperText Mark-up
Language) and XHTML.

 -- 類別: html.parser.HTMLParser (*, convert_charrefs=True)

     Create a parser instance able to parse invalid markup.

     If `convert_charrefs' is ‘True’ (the default), all character
     references (except the ones in ‘script’/‘style’ elements) are
     automatically converted to the corresponding Unicode characters.

     An *note HTMLParser: 7c4. instance is fed HTML data and calls
     handler methods when start tags, end tags, text, comments, and
     other markup elements are encountered.  The user should subclass
     *note HTMLParser: 7c4. and override its methods to implement the
     desired behavior.

     This parser does not check that end tags match start tags or call
     the end-tag handler for elements which are closed implicitly by
     closing an outer element.

     3.4 版更變: `convert_charrefs' keyword argument added.

     3.5 版更變: The default value for argument `convert_charrefs' is
     now ‘True’.

* Menu:

* Example HTML Parser Application::
* HTMLParser Methods::
* Examples: Examples<19>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/html/parser.py


File: python.info,  Node: Example HTML Parser Application,  Next: HTMLParser Methods,  Up: html parser --- Simple HTML and XHTML parser

5.20.2.1 Example HTML Parser Application
........................................

As a basic example, below is a simple HTML parser that uses the *note
HTMLParser: 7c4. class to print out start tags, end tags, and data as
they are encountered:

     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>')

The output will then be:

     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 Methods,  Next: Examples<19>,  Prev: Example HTML Parser Application,  Up: html parser --- Simple HTML and XHTML parser

5.20.2.2 ‘HTMLParser’ Methods
.............................

*note HTMLParser: 7c4. instances have the following methods:

 -- 成員函式: HTMLParser.feed (data)

     Feed some text to the parser.  It is processed insofar as it
     consists of complete elements; incomplete data is buffered until
     more data is fed or *note close(): 29e2. is called.  `data' must be
     *note str: 335.

 -- 成員函式: HTMLParser.close ()

     Force processing of all buffered data as if it were followed by an
     end-of-file mark.  This method may be redefined by a derived class
     to define additional processing at the end of the input, but the
     redefined version should always call the *note HTMLParser: 7c4.
     base class method *note close(): 29e2.

 -- 成員函式: HTMLParser.reset ()

     Reset the instance.  Loses all unprocessed data.  This is called
     implicitly at instantiation time.

 -- 成員函式: HTMLParser.getpos ()

     Return current line number and offset.

 -- 成員函式: HTMLParser.get_starttag_text ()

     Return the text of the most recently opened start tag.  This should
     not normally be needed for structured processing, but may be useful
     in dealing with HTML "as deployed" or for re-generating input with
     minimal changes (whitespace between attributes can be preserved,
     etc.).

The following methods are called when data or markup elements are
encountered and they are meant to be overridden in a subclass.  The base
class implementations do nothing (except for *note handle_startendtag():
29e6.):

 -- 成員函式: HTMLParser.handle_starttag (tag, attrs)

     This method is called to handle the start of a tag (e.g.  ‘<div
     id="main">’).

     The `tag' argument is the name of the tag converted to lower case.
     The `attrs' argument is a list of ‘(name, value)’ pairs containing
     the attributes found inside the tag’s ‘<>’ brackets.  The `name'
     will be translated to lower case, and quotes in the `value' have
     been removed, and character and entity references have been
     replaced.

     For instance, for the tag ‘<A HREF="https://www.cwi.nl/">’, this
     method would be called as ‘handle_starttag('a', [('href',
     'https://www.cwi.nl/')])’.

     All entity references from *note html.entities: 91. are replaced in
     the attribute values.

 -- 成員函式: HTMLParser.handle_endtag (tag)

     This method is called to handle the end tag of an element (e.g.
     ‘</div>’).

     The `tag' argument is the name of the tag converted to lower case.

 -- 成員函式: HTMLParser.handle_startendtag (tag, attrs)

     Similar to *note handle_starttag(): 29e7, but called when the
     parser encounters an XHTML-style empty tag (‘<img ... />’).  This
     method may be overridden by subclasses which require this
     particular lexical information; the default implementation simply
     calls *note handle_starttag(): 29e7. and *note handle_endtag():
     29e8.

 -- 成員函式: HTMLParser.handle_data (data)

     This method is called to process arbitrary data (e.g.  text nodes
     and the content of ‘<script>...</script>’ and
     ‘<style>...</style>’).

 -- 成員函式: HTMLParser.handle_entityref (name)

     This method is called to process a named character reference of the
     form ‘&name;’ (e.g.  ‘&gt;’), where `name' is a general entity
     reference (e.g.  ‘'gt'’).  This method is never called if
     `convert_charrefs' is ‘True’.

 -- 成員函式: HTMLParser.handle_charref (name)

     This method is called to process decimal and hexadecimal numeric
     character references of the form ‘&#NNN;’ and ‘&#xNNN;’.  For
     example, the decimal equivalent for ‘&gt;’ is ‘&#62;’, whereas the
     hexadecimal is ‘&#x3E;’; in this case the method will receive
     ‘'62'’ or ‘'x3E'’.  This method is never called if
     `convert_charrefs' is ‘True’.

 -- 成員函式: HTMLParser.handle_comment (data)

     This method is called when a comment is encountered (e.g.
     ‘<!--comment-->’).

     For example, the comment ‘<!-- comment -->’ will cause this method
     to be called with the argument ‘' comment '’.

     The content of Internet Explorer conditional comments (condcoms)
     will also be sent to this method, so, for ‘<!--[if IE
     9]>IE9-specific content<![endif]-->’, this method will receive
     ‘'[if IE 9]>IE9-specific content<![endif]'’.

 -- 成員函式: HTMLParser.handle_decl (decl)

     This method is called to handle an HTML doctype declaration (e.g.
     ‘<!DOCTYPE html>’).

     The `decl' parameter will be the entire contents of the declaration
     inside the ‘<!...>’ markup (e.g.  ‘'DOCTYPE html'’).

 -- 成員函式: HTMLParser.handle_pi (data)

     Method called when a processing instruction is encountered.  The
     `data' parameter will contain the entire processing instruction.
     For example, for the processing instruction ‘<?proc color='red'>’,
     this method would be called as ‘handle_pi("proc color='red'")’.  It
     is intended to be overridden by a derived class; the base class
     implementation does nothing.

          備註: The *note HTMLParser: 7c4. class uses the SGML syntactic
          rules for processing instructions.  An XHTML processing
          instruction using the trailing ‘'?'’ will cause the ‘'?'’ to
          be included in `data'.

 -- 成員函式: HTMLParser.unknown_decl (data)

     This method is called when an unrecognized declaration is read by
     the parser.

     The `data' parameter will be the entire contents of the declaration
     inside the ‘<![...]>’ markup.  It is sometimes useful to be
     overridden by a derived class.  The base class implementation does
     nothing.


File: python.info,  Node: Examples<19>,  Prev: HTMLParser Methods,  Up: html parser --- Simple HTML and XHTML parser

5.20.2.3 Examples
.................

The following class implements a parser that will be used to illustrate
more examples:

     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()

Parsing a doctype:

     >>> 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"

Parsing an element with a few attributes and a title:

     >>> 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

The content of ‘script’ and ‘style’ elements is returned as is, without
further parsing:

     >>> 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

Parsing comments:

     >>> parser.feed('<!-- a comment -->'
     ...             '<!--[if IE 9]>IE-specific content<![endif]-->')
     Comment  :  a comment
     Comment  : [if IE 9]>IE-specific content<![endif]

Parsing named and numeric character references and converting them to
the correct char (note: these 3 references are all equivalent to ‘'>'’):

     >>> parser.feed('&gt;&#62;&#x3E;')
     Named ent: >
     Num ent  : >
     Num ent  : >

Feeding incomplete chunks to *note feed(): 29e1. works, but *note
handle_data(): 29e9. might be called more than once (unless
`convert_charrefs' is set to ‘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

Parsing invalid HTML (e.g.  unquoted attributes) also works:

     >>> 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 --- Definitions of HTML general entities,  Next: XML 處理模組,  Prev: html parser --- Simple HTML and XHTML parser,  Up: Structured Markup Processing Tools

5.20.3 ‘html.entities’ — Definitions of HTML general entities
-------------------------------------------------------------

`Source code:' Lib/html/entities.py(1)

__________________________________________________________________

This module defines four dictionaries, *note html5: a1a, *note
name2codepoint: 29f4, *note codepoint2name: 29f5, and *note entitydefs:
29f6.

 -- Data: html.entities.html5

     A dictionary that maps HTML5 named character references (2) to the
     equivalent Unicode character(s), e.g.  ‘html5['gt;'] == '>'’.  Note
     that the trailing semicolon is included in the name (e.g.
     ‘'gt;'’), however some of the names are accepted by the standard
     even without the semicolon: in this case the name is present with
     and without the ‘';'’.  See also *note html.unescape(): 85f.

     3.3 版新加入.

 -- Data: html.entities.entitydefs

     A dictionary mapping XHTML 1.0 entity definitions to their
     replacement text in ISO Latin-1.

 -- Data: html.entities.name2codepoint

     A dictionary that maps HTML entity names to the Unicode code
     points.

 -- Data: html.entities.codepoint2name

     A dictionary that maps Unicode code points to HTML entity names.

註解
....

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/html/entities.py

   (2) (1) See
‘https://www.w3.org/TR/html5/syntax.html#named-character-references’


File: python.info,  Node: XML 處理模組,  Next: xml etree ElementTree --- The ElementTree XML API,  Prev: html entities --- Definitions of HTML general entities,  Up: Structured Markup Processing Tools

5.20.4 XML 處理模組
-------------------

`Source code:' Lib/xml/(1)

__________________________________________________________________

Python’s interfaces for processing XML are grouped in the ‘xml’ package.

     警告: The XML modules are not secure against erroneous or
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see the *note XML vulnerabilities: 29fa. and
     *note The defusedxml Package: 29fb. sections.

It is important to note that modules in the *note xml: 134. package
require that there be at least one SAX-compliant XML parser available.
The Expat parser is included with Python, so the *note
xml.parsers.expat: 139. module will always be available.

The documentation for the *note xml.dom: 135. and *note xml.sax: 13c.
packages are the definition of the Python bindings for the DOM and SAX
interfaces.

The XML handling submodules are:

   * *note xml.etree.ElementTree: 138.: the ElementTree API, a simple
     and lightweight XML processor

   * *note xml.dom: 135.: the DOM API definition

   * *note xml.dom.minidom: 136.: a minimal DOM implementation

   * *note xml.dom.pulldom: 137.: support for building partial DOM trees

   * *note xml.sax: 13c.: SAX2 base classes and convenience functions

   * *note xml.parsers.expat: 139.: the Expat parser binding

* Menu:

* XML vulnerabilities::
* The defusedxml Package::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/xml/


File: python.info,  Node: XML vulnerabilities,  Next: The defusedxml Package,  Up: XML 處理模組

5.20.4.1 XML vulnerabilities
............................

The XML processing modules are not secure against maliciously
constructed data.  An attacker can abuse XML features to carry out
denial of service attacks, access local files, generate network
connections to other machines, or circumvent firewalls.

The following table gives an overview of the known attacks and whether
the various modules are vulnerable to them.

kind                          sax                etree               minidom            pulldom            xmlrpc
                                                                                                           
------------------------------------------------------------------------------------------------------------------------------
                                                                                                           
billion laughs                `Vulnerable'       `Vulnerable'        `Vulnerable'       `Vulnerable'       `Vulnerable'
                                                                                                           
                                                                                                           
quadratic blowup              `Vulnerable'       `Vulnerable'        `Vulnerable'       `Vulnerable'       `Vulnerable'
                                                                                                           
                                                                                                           
external entity expansion     Safe (4)           Safe (1)            Safe (2)           Safe (4)           Safe (3)
                                                                                                           
                                                                                                           
DTD(1) retrieval              Safe (4)           Safe                Safe               Safe (4)           Safe
                                                                                                           
                                                                                                           
decompression bomb            Safe               Safe                Safe               Safe               `Vulnerable'
                                                                                                           

  1. *note xml.etree.ElementTree: 138. doesn’t expand external entities
     and raises a ‘ParserError’ when an entity occurs.

  2. *note xml.dom.minidom: 136. doesn’t expand external entities and
     simply returns the unexpanded entity verbatim.

  3. ‘xmlrpclib’ doesn’t expand external entities and omits them.

  4. Since Python 3.7.1, external general entities are no longer
     processed by default.

billion laughs / exponential entity expansion

     The Billion Laughs(2) attack – also known as exponential entity
     expansion – uses multiple levels of nested entities.  Each entity
     refers to another entity several times, and the final entity
     definition contains a small string.  The exponential expansion
     results in several gigabytes of text and consumes lots of memory
     and CPU time.

quadratic blowup entity expansion

     A quadratic blowup attack is similar to a Billion Laughs(3) attack;
     it abuses entity expansion, too.  Instead of nested entities it
     repeats one large entity with a couple of thousand chars over and
     over again.  The attack isn’t as efficient as the exponential case
     but it avoids triggering parser countermeasures that forbid
     deeply-nested entities.

external entity expansion

     Entity declarations can contain more than just text for
     replacement.  They can also point to external resources or local
     files.  The XML parser accesses the resource and embeds the content
     into the XML document.

DTD(4) retrieval

     Some XML libraries like Python’s *note xml.dom.pulldom: 137.
     retrieve document type definitions from remote or local locations.
     The feature has similar implications as the external entity
     expansion issue.

decompression bomb

     Decompression bombs (aka ZIP bomb(5)) apply to all XML libraries
     that can parse compressed XML streams such as gzipped HTTP streams
     or LZMA-compressed files.  For an attacker it can reduce the amount
     of transmitted data by three magnitudes or more.

The documentation for defusedxml(6) on PyPI has further information
about all known attack vectors with examples and references.

   ---------- 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://pypi.org/project/defusedxml/


File: python.info,  Node: The defusedxml Package,  Prev: XML vulnerabilities,  Up: XML 處理模組

5.20.4.2 The ‘defusedxml’ Package
.................................

defusedxml(1) is a pure Python package with modified subclasses of all
stdlib XML parsers that prevent any potentially malicious operation.
Use of this package is recommended for any server code that parses
untrusted XML data.  The package also ships with example exploits and
extended documentation on more XML exploits such as XPath injection.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/defusedxml/


File: python.info,  Node: xml etree ElementTree --- The ElementTree XML API,  Next: xml dom --- The Document Object Model API,  Prev: XML 處理模組,  Up: Structured Markup Processing Tools

5.20.5 ‘xml.etree.ElementTree’ — The ElementTree XML API
--------------------------------------------------------

`Source code:' Lib/xml/etree/ElementTree.py(1)

__________________________________________________________________

The *note xml.etree.ElementTree: 138. module implements a simple and
efficient API for parsing and creating XML data.

3.3 版更變: This module will use a fast implementation whenever
available.  The ‘xml.etree.cElementTree’ module is deprecated.

     警告: The *note xml.etree.ElementTree: 138. module is not secure
     against maliciously constructed data.  If you need to parse
     untrusted or unauthenticated data see *note XML vulnerabilities:
     29fa.

* Menu:

* Tutorial::
* XPath support::
* Reference: Reference<2>.
* XInclude support::
* Reference: Reference<3>.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/xml/etree/ElementTree.py


File: python.info,  Node: Tutorial,  Next: XPath support,  Up: xml etree ElementTree --- The ElementTree XML API

5.20.5.1 Tutorial
.................

This is a short tutorial for using *note xml.etree.ElementTree: 138.
(‘ET’ in short).  The goal is to demonstrate some of the building blocks
and basic concepts of the module.

* Menu:

* XML tree and elements::
* Parsing XML::
* Pull API for non-blocking parsing::
* Finding interesting elements::
* Modifying an XML File::
* Building XML documents::
* Parsing XML with Namespaces::
* Additional resources::


File: python.info,  Node: XML tree and elements,  Next: Parsing XML,  Up: Tutorial

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: 91c. represents the whole XML document as a tree, and
*note Element: ac9. 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: 91c. level.  Interactions with a single
XML element and its sub-elements are done on the *note Element: ac9.
level.


File: python.info,  Node: Parsing XML,  Next: Pull API for non-blocking parsing,  Prev: XML tree and elements,  Up: Tutorial

5.20.5.3 Parsing XML
....................

We’ll be using the following 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(): 2a05. parses XML from a string directly into an
*note Element: ac9, which is the root element of the parsed tree.  Other
parsing functions may create an *note ElementTree: 91c.  Check the
documentation to be sure.

As an *note Element: ac9, ‘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: 254. instance to the *note XMLParser:
     253. constructor.


File: python.info,  Node: Pull API for non-blocking parsing,  Next: Finding interesting elements,  Prev: Parsing XML,  Up: Tutorial

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: 253. 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: ac9. objects.

The most powerful tool for doing this is *note XMLPullParser: 918.  It
does not require a blocking read to obtain the XML data, and is instead
fed with data incrementally with *note XMLPullParser.feed(): 2a07.
calls.  To get the parsed XML elements, call *note
XMLPullParser.read_events(): 2a08.  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

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: 918. 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(): 94d.  It can be
useful when you’re reading a large XML document and don’t want to hold
it wholly in memory.


File: python.info,  Node: Finding interesting elements,  Next: Modifying an XML File,  Prev: Pull API for non-blocking parsing,  Up: Tutorial

5.20.5.5 Finding interesting elements
.....................................

*note Element: ac9. 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(): cec.:

     >>> 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(): 2a0a. finds only elements with a tag which are
direct children of the current element.  *note Element.find(): 2a0b.
finds the `first' child with a particular tag, and *note Element.text:
2a0c. accesses the element’s text content.  *note Element.get(): 2a0d.
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: 41f.


File: python.info,  Node: Modifying an XML File,  Next: Building XML documents,  Prev: Finding interesting elements,  Up: Tutorial

5.20.5.6 Modifying an XML File
..............................

*note ElementTree: 91c. provides a simple way to build XML documents and
write them to files.  The *note ElementTree.write(): 91d. method serves
this purpose.

Once created, an *note Element: ac9. object may be manipulated by
directly changing its fields (such as *note Element.text: 2a0c.), adding
and modifying attributes (*note Element.set(): 2a0f. method), as well as
adding new children (for example with *note Element.append(): 2a10.).

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')

Our XML now looks like this:

     <?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(): 2a11.  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.

Our XML now looks like this:

     <?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: Modifying an XML File,  Up: Tutorial

5.20.5.7 Building XML documents
...............................

The *note SubElement(): 2a13. 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,  Next: Additional resources,  Prev: Building XML documents,  Up: Tutorial

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(): 2a0b. or
*note findall(): 2a0a.:

     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: Additional resources,  Prev: Parsing XML with Namespaces,  Up: Tutorial

5.20.5.9 Additional resources
.............................

See ‘http://effbot.org/zone/element-index.htm’ for tutorials and links
to other docs.


File: python.info,  Node: XPath support,  Next: Reference<2>,  Prev: Tutorial,  Up: xml etree ElementTree --- The ElementTree XML API

5.20.5.10 XPath support
.......................

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:

* Example: Example<10>.
* Supported XPath syntax::

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/xpath


File: python.info,  Node: Example<10>,  Next: Supported XPath syntax,  Up: XPath support

5.20.5.11 Example
.................

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: 2a03. 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: Example<10>,  Up: XPath support

5.20.5.12 Supported XPath syntax
................................

Syntax                      Meaning
                            
---------------------------------------------------------------------------------------
                            
‘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 版更變: Support for star-wildcards was added.
                            
                            
‘*’                         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]’                 Selects all elements that have the given attribute.
                            
                            
‘[@attrib='value']’         Selects all elements for which the given attribute has
                            the given value.  The value cannot contain quotes.
                            
                            
‘[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 版新加入.
                            
                            
‘[tag='text']’              Selects all elements that have a child named ‘tag’ whose
                            complete text content, including descendants, equals the
                            given ‘text’.
                            
                            
‘[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<2>,  Next: XInclude support,  Prev: XPath support,  Up: xml etree ElementTree --- The ElementTree XML API

5.20.5.13 Reference
...................

* Menu:

* Functions: Functions<6>.


File: python.info,  Node: Functions<6>,  Up: Reference<2>

5.20.5.14 Functions
...................

 -- 函式: 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 reduced
     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: 253. skips over comments in the input
     instead of creating comment objects for them.  An *note
     ElementTree: 91c. will only contain comment nodes if they have been
     inserted into to the tree using one of the *note Element: ac9.
     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(): 2a1e. 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():
     2a1f.  `text' is a string containing XML data.  `parser' is an
     optional parser instance.  If not given, the standard *note
     XMLParser: 253. parser is used.  Returns an *note Element: ac9.
     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: 253. parser is used.  Returns an
     *note Element: ac9. instance.

     3.2 版新加入.

 -- 函式: 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: b47. 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: 253. parser is used.  `parser' must
     be a subclass of *note XMLParser: 253. and can only use the default
     *note TreeBuilder: 254. as a target.  Returns an *note iterator:
     1040. providing ‘(event, elem)’ pairs.

     Note that while *note iterparse(): 94d. 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: 918.

          備註: *note iterparse(): 94d. 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 版後已棄用: The `parser' argument.

     3.8 版更變: The ‘comment’ and ‘pi’ events were added.

 -- 函式: 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: 253. parser
     is used.  Returns an *note ElementTree: 91c. 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: 253. skips over processing instructions
     in the input instead of creating comment objects for them.  An
     *note ElementTree: 91c. will only contain processing instruction
     nodes if they have been inserted into to the tree using one of the
     *note Element: ac9. 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: ac9. 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(): 91d.  Returns an (optionally)
     encoded string containing the XML data.

     3.4 版新加入: The `short_empty_elements' parameter.

     3.8 版新加入: The `xml_declaration' and `default_namespace'
     parameters.

     3.8 版更變: The *note tostring(): 91a. 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: ac9. 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(): 91d.  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 版新加入: The `short_empty_elements' parameter.

     3.8 版新加入: The `xml_declaration' and `default_namespace'
     parameters.

     3.8 版更變: The *note tostringlist(): 91b. 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: 253. parser is used.
     Returns an *note Element: ac9. 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: 253. parser
     is used.  Returns a tuple containing an *note Element: ac9.
     instance and a dictionary.

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/xml-c14n2/

   (2) (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’.

   (3) (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: XInclude support,  Next: Reference<3>,  Prev: Reference<2>,  Up: xml etree ElementTree --- The ElementTree XML API

5.20.5.15 XInclude support
..........................

This module provides limited support for XInclude directives(1), via the
‘xml.etree.ElementInclude’ helper module.  This module can be used to
insert subtrees and text strings into element trees, based on
information in the tree.

* Menu:

* Example: Example<11>.

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/xinclude/


File: python.info,  Node: Example<11>,  Up: XInclude support

5.20.5.16 Example
.................

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: 138. 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<3>,  Prev: XInclude support,  Up: xml etree ElementTree --- The ElementTree XML API

5.20.5.17 Reference
...................

* Menu:

* Functions: Functions<7>.
* Element Objects::
* ElementTree Objects::
* QName Objects::
* TreeBuilder Objects::
* XMLParser Objects::
* XMLPullParser Objects::
* Exceptions: Exceptions<13>.


File: python.info,  Node: Functions<7>,  Next: Element Objects,  Up: Reference<3>

5.20.5.18 Functions
...................

 -- 函式: 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 ElementTree instance.  If the parse
     mode is "text", this is a Unicode string.  If the loader fails, it
     can return None or raise an exception.

 -- 函式: xml.etree.ElementInclude.include (elem, loader=None)

     This function expands XInclude directives.  `elem' is the root
     element.  `loader' is an optional resource loader.  If omitted, it
     defaults to *note default_loader(): 2a2a.  If given, it should be a
     callable that implements the same interface as *note
     default_loader(): 2a2a.  Returns the expanded resource.  If the
     parse mode is ‘"xml"’, this is an ElementTree instance.  If the
     parse mode is "text", this is a Unicode string.  If the loader
     fails, it can return None or raise an exception.


File: python.info,  Node: Element Objects,  Next: ElementTree Objects,  Prev: Functions<7>,  Up: Reference<3>

5.20.5.19 Element Objects
.........................

 -- 類別: 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():
          b58, 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: 193. if
          `subelement' is not an *note Element: ac9.

      -- 成員函式: extend (subelements)

          Appends `subelements' from a sequence object with zero or more
          elements.  Raises *note TypeError: 193. if a subelement is not
          an *note Element: ac9.

          3.2 版新加入.

      -- 成員函式: find (match, namespaces=None)

          Finds the first subelement matching `match'.  `match' may be a
          tag name or a *note path: 41f.  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:
          41f.  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: 41f.  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.

      -- 成員函式: getchildren ()

          Deprecated since version 3.2, will be removed in version 3.9:
          Use ‘list(elem)’ or iteration.

      -- 成員函式: getiterator (tag=None)

          Deprecated since version 3.2, will be removed in version 3.9:
          Use method *note Element.iter(): cec. instead.

      -- 成員函式: insert (index, subelement)

          Inserts `subelement' at the given position in this element.
          Raises *note TypeError: 193. if `subelement' is not an *note
          Element: ac9.

      -- 成員函式: iter (tag=None)

          Creates a tree *note iterator: 1040. 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:
          41f.  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(): 2a13.
          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: ac9. objects also support the following sequence
     type methods for working with subelements: *note __delitem__():
     c68, *note __getitem__(): 27d, *note __setitem__(): c67, *note
     __len__(): dd0.

     Caution: Elements with no subelements will test as ‘False’.  This
     behavior will change in future versions.  Use specific ‘len(elem)’
     or ‘elem is None’ test instead.

          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")

     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(): 2a1c. 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 Objects,  Next: QName Objects,  Prev: Element Objects,  Up: Reference<3>

5.20.5.20 ElementTree Objects
.............................

 -- 類別: 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(): 2a0b, starting at the root of
          the tree.

      -- 成員函式: findall (match, namespaces=None)

          Same as *note Element.findall(): 2a0a, starting at the root of
          the tree.

      -- 成員函式: findtext (match, default=None, namespaces=None)

          Same as *note Element.findtext(): 2a34, starting at the root
          of the tree.

      -- 成員函式: getiterator (tag=None)

          Deprecated since version 3.2, will be removed in version 3.9:
          Use method *note ElementTree.iter(): 2a40. instead.

      -- 成員函式: 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(): b57, 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: b47.  `parser'
          is an optional parser instance.  If not given, the standard
          *note XMLParser: 253. 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: b47. 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: 335.) or binary
          (*note bytes: 336.).  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:
          b47.; make sure you do not try to write a string to a binary
          stream and vice versa.

          3.4 版新加入: The `short_empty_elements' parameter.

          3.8 版更變: The *note write(): 91d. 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) (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 Objects,  Next: TreeBuilder Objects,  Prev: ElementTree Objects,  Up: Reference<3>

5.20.5.21 QName Objects
.......................

 -- 類別: 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: 2a46.
     instances are opaque.


File: python.info,  Node: TreeBuilder Objects,  Next: XMLParser Objects,  Prev: QName Objects,  Up: Reference<3>

5.20.5.22 TreeBuilder Objects
.............................

 -- 類別: 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(): 2a1d. and *note
     ProcessingInstruction(): 2a22. 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: ac9. 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 comment 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: 254. 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: 254. 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(): 2a1c. 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 Objects,  Next: XMLPullParser Objects,  Prev: TreeBuilder Objects,  Up: Reference<3>

5.20.5.23 XMLParser Objects
...........................

 -- 類別: 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: 139. for efficient, event-based parsing of
     XML. It can be fed XML data incrementally with the *note feed():
     2a53. 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: 254. 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: 2ad.  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.

     *note XMLParser.feed(): 2a53. 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:
     254. class.  *note XMLParser.close(): 2a54. calls `target'’s method
     ‘close()’.  *note XMLParser: 253. 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) (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 Objects,  Next: Exceptions<13>,  Prev: XMLParser Objects,  Up: Reference<3>

5.20.5.24 XMLPullParser Objects
...............................

 -- 類別: 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: 253, but
     instead of pushing calls to a callback target, *note XMLPullParser:
     918. 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.

      -- 成員函式: close ()

          Signal the parser that the data stream is terminated.  Unlike
          *note XMLParser.close(): 2a54, this method always returns
          *note None: 158.  Any events not yet retrieved when the parser
          is closed can still be read with *note read_events(): 2a08.

      -- 成員函式: 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: ac9. object, or other context value as follows.

             * ‘start’, ‘end’: the current Element.

             * ‘comment’, ‘pi’: the current comment / processing
               instruction

             * ‘start-ns’: a tuple ‘(prefix, uri)’ naming the declared
               namespace mapping.

             * ‘end-ns’: *note None: 158. (this may change in a future
               version)

          Events provided in a previous call to *note read_events():
          2a08. 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(): 2a08. will have
          unpredictable results.

          備註: *note XMLPullParser: 918. 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 版更變: The ‘comment’ and ‘pi’ events were added.


File: python.info,  Node: Exceptions<13>,  Prev: XMLPullParser Objects,  Up: Reference<3>

5.20.5.25 Exceptions
....................

 -- 類別: 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: 139. 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 --- The Document Object Model API,  Next: xml dom minidom --- Minimal DOM implementation,  Prev: xml etree ElementTree --- The ElementTree XML API,  Up: Structured Markup Processing Tools

5.20.6 ‘xml.dom’ — The Document Object Model API
------------------------------------------------

`Source code:' 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(): 2a5d.  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: 2a5e. 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: 136.

Python Language Mapping Specification(4)

     This specifies the mapping from OMG IDL to Python.

* Menu:

* Module Contents: Module Contents<4>.
* Objects in the DOM::
* Conformance::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/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) http://www.omg.org/cgi-bin/doc?formal/02-11-05.pdf


File: python.info,  Node: Module Contents<4>,  Next: Objects in the DOM,  Up: xml dom --- The Document Object Model API

5.20.6.1 Module Contents
........................

The *note xml.dom: 135. 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: 339.  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:

 -- Data: 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.

 -- Data: xml.dom.XML_NAMESPACE

     The namespace URI associated with the reserved prefix ‘xml’, as
     defined by Namespaces in XML(1) (section 4).

 -- Data: 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).

 -- Data: 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: 135. 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: Module Contents<4>,  Up: xml dom --- The Document Object Model 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 Objects: 2a67.  Interface to the underlying
                                                                             implementation.
                                                                             
                                                                             
‘Node’                               *note Node Objects: 2a68.               Base interface for most objects in
                                                                             a document.
                                                                             
                                                                             
‘NodeList’                           *note NodeList Objects: 2a69.           Interface for a sequence of nodes.
                                                                             
                                                                             
‘DocumentType’                       *note DocumentType Objects: 2a6a.       Information about the declarations
                                                                             needed to process a document.
                                                                             
                                                                             
‘Document’                           *note Document Objects: 2a6b.           Object which represents an entire
                                                                             document.
                                                                             
                                                                             
‘Element’                            *note Element Objects: 2a6c.            Element nodes in the document
                                                                             hierarchy.
                                                                             
                                                                             
‘Attr’                               *note Attr Objects: 2a6d.               Attribute value nodes on element
                                                                             nodes.
                                                                             
                                                                             
‘Comment’                            *note Comment Objects: 2a6e.            Representation of comments in the
                                                                             source document.
                                                                             
                                                                             
‘Text’                               *note Text and CDATASection Objects: 2a6f.Nodes containing textual content
                                                                             from the document.
                                                                             
                                                                             
‘ProcessingInstruction’              *note ProcessingInstruction Objects: 2a70.Processing instruction
                                                                             representation.
                                                                             

An additional section describes the exceptions defined for working with
the DOM in Python.

* Menu:

* DOMImplementation Objects::
* Node Objects::
* NodeList Objects::
* DocumentType Objects::
* Document Objects::
* Element Objects: Element Objects<2>.
* Attr Objects::
* NamedNodeMap Objects::
* Comment Objects::
* Text and CDATASection Objects::
* ProcessingInstruction Objects::
* Exceptions: Exceptions<14>.


File: python.info,  Node: DOMImplementation Objects,  Next: Node Objects,  Up: Objects in the DOM

5.20.6.3 DOMImplementation Objects
..................................

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(): 2a74, 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 Objects,  Prev: DOMImplementation Objects,  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: 2a79.  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: 2a81.  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: 1fc. 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: 1fc. 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: 1fc.
     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 Objects,  Next: DocumentType Objects,  Prev: Node Objects,  Up: Objects in the DOM

5.20.6.5 NodeList Objects
.........................

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__(): dd0. and *note __getitem__(): 27d.; this allows
iteration over the ‘NodeList’ in *note for: c35. statements and proper
support for the *note len(): 151. built-in function.

If a DOM implementation supports modification of the document, the
‘NodeList’ implementation must also support the *note __setitem__():
c67. and *note __delitem__(): c68. methods.


File: python.info,  Node: DocumentType Objects,  Next: Document Objects,  Prev: NodeList Objects,  Up: Objects in the DOM

5.20.6.6 DocumentType Objects
.............................

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<2>,  Prev: DocumentType Objects,  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<2>,  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: 2aac. is raised.

 -- 成員函式: Element.removeAttributeNode (oldAttr)

     Remove and return `oldAttr' from the attribute list, if present.
     If `oldAttr' is not present, *note NotFoundErr: 2aac. 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: 2ab1. 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: 2ab1. 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 Objects,  Prev: Element Objects<2>,  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 Objects,  Next: Comment Objects,  Prev: Attr Objects,  Up: Objects in the DOM

5.20.6.10 NamedNodeMap Objects
..............................

‘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 Objects,  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 Objects,  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 Objects,  Next: Exceptions<14>,  Prev: Text and CDATASection Objects,  Up: Objects in the DOM

5.20.6.13 ProcessingInstruction Objects
.......................................

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: Exceptions<14>,  Prev: ProcessingInstruction Objects,  Up: Objects in the DOM

5.20.6.14 Exceptions
....................

The DOM Level 2 recommendation defines a single exception, *note
DOMException: 2ac6, and a number of constants that allow applications to
determine what sort of error occurred.  *note DOMException: 2ac6.
instances carry a *note code: 1b. 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: 1b. 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:

Constant                                   Exception
                                           
---------------------------------------------------------------------------------
                                           
‘DOMSTRING_SIZE_ERR’                       *note DomstringSizeErr: 2ac7.
                                           
                                           
‘HIERARCHY_REQUEST_ERR’                    *note HierarchyRequestErr: 2ac8.
                                           
                                           
‘INDEX_SIZE_ERR’                           *note IndexSizeErr: 2ac9.
                                           
                                           
‘INUSE_ATTRIBUTE_ERR’                      *note InuseAttributeErr: 2ab1.
                                           
                                           
‘INVALID_ACCESS_ERR’                       *note InvalidAccessErr: 2aca.
                                           
                                           
‘INVALID_CHARACTER_ERR’                    *note InvalidCharacterErr: 2acb.
                                           
                                           
‘INVALID_MODIFICATION_ERR’                 *note InvalidModificationErr: 2acc.
                                           
                                           
‘INVALID_STATE_ERR’                        *note InvalidStateErr: 2acd.
                                           
                                           
‘NAMESPACE_ERR’                            *note NamespaceErr: 2ace.
                                           
                                           
‘NOT_FOUND_ERR’                            *note NotFoundErr: 2aac.
                                           
                                           
‘NOT_SUPPORTED_ERR’                        *note NotSupportedErr: 2acf.
                                           
                                           
‘NO_DATA_ALLOWED_ERR’                      *note NoDataAllowedErr: 2ad0.
                                           
                                           
‘NO_MODIFICATION_ALLOWED_ERR’              *note NoModificationAllowedErr: 2ad1.
                                           
                                           
‘SYNTAX_ERR’                               *note SyntaxErr: 2ad2.
                                           
                                           
‘WRONG_DOCUMENT_ERR’                       *note WrongDocumentErr: 2ad3.
                                           

   ---------- Footnotes ----------

   (1) https://www.w3.org/TR/REC-xml-names/


File: python.info,  Node: Conformance,  Prev: Objects in the DOM,  Up: xml dom --- The Document Object Model 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’ or ‘int’
                       
                       
‘int’                  ‘int’
                       
                       
‘long int’             ‘int’
                       
                       
‘unsigned int’         ‘int’
                       
                       
‘DOMString’            ‘str’ or ‘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: 3a0.

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 --- Minimal DOM implementation,  Next: xml dom pulldom --- Support for building partial DOM trees,  Prev: xml dom --- The Document Object Model API,  Up: Structured Markup Processing Tools

5.20.7 ‘xml.dom.minidom’ — Minimal DOM implementation
-----------------------------------------------------

`Source code:' Lib/xml/dom/minidom.py(1)

__________________________________________________________________

*note xml.dom.minidom: 136. 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: 138. module for their
XML processing instead.

     警告: The *note xml.dom.minidom: 136. module is not secure against
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML vulnerabilities: 29fa.

DOM applications typically start by parsing some XML into a DOM. With
*note xml.dom.minidom: 136, 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(): 2adb. 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(): 2adc.
function instead:

 -- 函式: xml.dom.minidom.parseString (string, parser=None)

     Return a ‘Document’ that represents the `string'.  This method
     creates an *note io.StringIO: 832. object for the string and passes
     that on to *note parse(): 2adb.

Both functions return a ‘Document’ object representing the content of
the document.

What the *note parse(): 2adb. and *note parseString(): 2adc. 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: 135. package or
the *note xml.dom.minidom: 136. 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: 136.-specific
extension to the DOM API that renders the node and its descendants are
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: 136.

* Menu:

* DOM Objects::
* DOM Example::
* minidom and the DOM standard::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/xml/dom/minidom.py

   (2) https://www.w3.org/TR/REC-DOM-Level-1/


File: python.info,  Node: DOM Objects,  Next: DOM Example,  Up: xml dom minidom --- Minimal DOM implementation

5.20.7.1 DOM Objects
....................

The definition of the DOM API for Python is given as part of the *note
xml.dom: 135. module documentation.  This section lists the differences
between the API and *note xml.dom.minidom: 136.

 -- 成員函式: 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: 6ee. 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="")

     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.

     3.8 版更變: The *note writexml(): 2ae0. method now preserves the
     attribute order specified by the user.

 -- 成員函式: Node.toxml (encoding=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.

     3.8 版更變: The *note toxml(): 2ae1. method now preserves the
     attribute order specified by the user.

 -- 成員函式: Node.toprettyxml (indent="\t", newl="\n", encoding=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(): 2ae1.

     3.8 版更變: The *note toprettyxml(): 2ae2. method now preserves the
     attribute order specified by the user.

   ---------- Footnotes ----------

   (1) (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 Example,  Next: minidom and the DOM standard,  Prev: DOM Objects,  Up: xml dom minidom --- Minimal DOM implementation

5.20.7.2 DOM Example
....................

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("<title>%s</title>" % getText(title.childNodes))

     def handleSlideTitle(title):
         print("<h2>%s</h2>" % getText(title.childNodes))

     def handlePoints(points):
         print("<ul>")
         for point in points:
             handlePoint(point)
         print("</ul>")

     def handlePoint(point):
         print("<li>%s</li>" % getText(point.childNodes))

     def handleToc(slides):
         for slide in slides:
             title = slide.getElementsByTagName("title")[0]
             print("<p>%s</p>" % getText(title.childNodes))

     handleSlideshow(dom)


File: python.info,  Node: minidom and the DOM standard,  Prev: DOM Example,  Up: xml dom minidom --- Minimal DOM implementation

5.20.7.3 minidom and the DOM standard
.....................................

The *note xml.dom.minidom: 136. 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:
     7a8. 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: 136. 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:
     136.  Instead, *note xml.dom.minidom: 136. uses standard Python
     exceptions such as *note TypeError: 193. and *note AttributeError:
     3a0.

   * ‘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: 136.:

   * ‘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 --- Support for building partial DOM trees,  Next: xml sax --- Support for SAX2 parsers,  Prev: xml dom minidom --- Minimal DOM implementation,  Up: Structured Markup Processing Tools

5.20.8 ‘xml.dom.pulldom’ — Support for building partial DOM trees
-----------------------------------------------------------------

`Source code:' Lib/xml/dom/pulldom.py(1)

__________________________________________________________________

The *note xml.dom.pulldom: 137. 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: 137. module is not secure against
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML vulnerabilities: 29fa.

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)

Example:

     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(): 2ae9. method and switch to
DOM-related processing.

 -- 類別: xml.dom.pulldom.PullDom (documentFactory=None)

     Subclass of *note xml.sax.handler.ContentHandler: 2aeb.

 -- 類別: xml.dom.pulldom.SAX2DOM (documentFactory=None)

     Subclass of *note xml.sax.handler.ContentHandler: 2aeb.

 -- 函式: xml.dom.pulldom.parse (stream_or_string, parser=None,
          bufsize=None)

     Return a *note DOMEventStream: 27e. 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: 2aee.
     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(): 2aef.
function instead:

 -- 函式: xml.dom.pulldom.parseString (string, parser=None)

     Return a *note DOMEventStream: 27e. that represents the (Unicode)
     `string'.

 -- Data: xml.dom.pulldom.default_bufsize

     Default value for the `bufsize' parameter to *note parse(): 2aed.

     The value of this variable can be changed before calling *note
     parse(): 2aed. and the new value will take effect.

* Menu:

* DOMEventStream Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/xml/dom/pulldom.py


File: python.info,  Node: DOMEventStream Objects,  Up: xml dom pulldom --- Support for building partial DOM trees

5.20.8.1 DOMEventStream Objects
...............................

 -- 類別: xml.dom.pulldom.DOMEventStream (stream, parser, bufsize)

     3.8 版後已棄用: Support for *note sequence protocol: 27d. is
     deprecated.

      -- 成員函式: 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(): 2ae9. 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 --- Support for SAX2 parsers,  Next: xml sax handler --- Base classes for SAX handlers,  Prev: xml dom pulldom --- Support for building partial DOM trees,  Up: Structured Markup Processing Tools

5.20.9 ‘xml.sax’ — Support for SAX2 parsers
-------------------------------------------

`Source code:' Lib/xml/sax/__init__.py(1)

__________________________________________________________________

The *note xml.sax: 13c. 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: 13c. module is not secure against
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML vulnerabilities: 29fa.

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(): 2af7. on the parser object and argument *note
feature_external_ges: 2af8.

The convenience functions are:

 -- 函式: xml.sax.make_parser (parser_list=[])

     Create and return a SAX *note XMLReader: 2aee. 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: 2aeb. instance.  If `error_handler' is given, it
     must be a SAX *note ErrorHandler: 2af9. instance; if omitted, *note
     SAXParseException: 2afa. 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(): fe6, but parses from a buffer `string'
     received as a parameter.  `string' must be a *note str: 335.
     instance or a *note bytes-like object: 5ed.

     3.5 版更變: Added support of *note str: 335. instances.

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: 797, *note Locator:
2afb, ‘Attributes’, ‘AttributesNS’, and *note XMLReader: 2aee.
interfaces are defined in the module *note xml.sax.xmlreader: 13f.  The
handler interfaces are defined in *note xml.sax.handler: 13d.  For
convenience, *note InputSource: 797. (which is often instantiated
directly) and the handler classes are also available from *note xml.sax:
13c.  These interfaces are described below.

In addition to these classes, *note xml.sax: 13c. 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: 2af9. 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: 2afc. raised on parse errors.
     Instances of this class are passed to the methods of the SAX *note
     ErrorHandler: 2af9. interface to provide information about the
     parse error.  This class supports the SAX *note Locator: 2afb.
     interface as well as the *note SAXException: 2afc. interface.

 -- 例外: xml.sax.SAXNotRecognizedException (msg, exception=None)

     Subclass of *note SAXException: 2afc. raised when a SAX *note
     XMLReader: 2aee. 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: 2afc. raised when a SAX *note
     XMLReader: 2aee. 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.

Module *note xml.sax.handler: 13d.

     Definitions of the interfaces for application-provided objects.

Module *note xml.sax.saxutils: 13e.

     Convenience functions for use in SAX applications.

Module *note xml.sax.xmlreader: 13f.

     Definitions of the interfaces for parser-provided objects.

* Menu:

* SAXException Objects::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/xml/sax/__init__.py

   (2) http://www.saxproject.org/


File: python.info,  Node: SAXException Objects,  Up: xml sax --- Support for SAX2 parsers

5.20.9.1 SAXException Objects
.............................

The *note SAXException: 2afc. 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 --- Base classes for SAX handlers,  Next: xml sax saxutils --- SAX Utilities,  Prev: xml sax --- Support for SAX2 parsers,  Up: Structured Markup Processing Tools

5.20.10 ‘xml.sax.handler’ — Base classes for SAX handlers
---------------------------------------------------------

`Source code:' Lib/xml/sax/handler.py(1)

__________________________________________________________________

The SAX API defines four kinds of handlers: content handlers, DTD
handlers, error handlers, and entity resolvers.  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: 13d, 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.

In addition to these classes, *note xml.sax.handler: 13d. provides
symbolic constants for the feature and property names.

 -- Data: 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 

 -- Data: 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 

 -- Data: 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 

 -- Data: 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 

 -- Data: 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 

 -- Data: 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 

 -- Data: xml.sax.handler.all_features

     List of all features.

 -- Data: xml.sax.handler.property_lexical_handler

          value: ‘"http://xml.org/sax/properties/lexical-handler"’ 
          data type: xml.sax.sax2lib.LexicalHandler (not supported in Python 2) 
          description: An optional extension handler for lexical events like comments. 
          access: read/write 

 -- Data: 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 

 -- Data: 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 

 -- Data: xml.sax.handler.property_xml_string

          value: ‘"http://xml.org/sax/properties/xml-string"’ 
          data type: String 
          description: The literal string of characters that was the source for the current event. 
          access: read-only 

 -- Data: xml.sax.handler.all_properties

     List of all known property names.

* Menu:

* ContentHandler Objects::
* DTDHandler Objects::
* EntityResolver Objects::
* ErrorHandler Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/xml/sax/handler.py


File: python.info,  Node: ContentHandler Objects,  Next: DTDHandler Objects,  Up: xml sax handler --- Base classes for SAX handlers

5.20.10.1 ContentHandler Objects
................................

Users are expected to subclass *note ContentHandler: 2aeb. 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(): 2b14.).

 -- 成員函式: 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(): 2b17. and
     *note endPrefixMapping(): 2b18. events supply the information to
     the application to expand prefixes in those contexts itself, if
     necessary.

     Note that *note startPrefixMapping(): 2b17. and *note
     endPrefixMapping(): 2b18. events are not guaranteed to be properly
     nested relative to each-other: all *note startPrefixMapping():
     2b17. events will occur before the corresponding *note
     startElement(): 2b19. event, and all *note endPrefixMapping():
     2b18. events will occur after the corresponding *note endElement():
     2b1a. event, but their order is not guaranteed.

 -- 成員函式: ContentHandler.endPrefixMapping (prefix)

     End the scope of a prefix-URI mapping.

     See *note startPrefixMapping(): 2b17. for details.  This event will
     always occur after the corresponding *note endElement(): 2b1a.
     event, but the order of *note endPrefixMapping(): 2b18. 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: 2b1b.)
     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(): 26. 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(): 2b19. 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: 2b1d.) 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(): 26. 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(): 2b1c. 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 Objects,  Next: EntityResolver Objects,  Prev: ContentHandler Objects,  Up: xml sax handler --- Base classes for SAX handlers

5.20.10.2 DTDHandler Objects
............................

*note DTDHandler: 2b05. 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 Objects,  Next: ErrorHandler Objects,  Prev: DTDHandler Objects,  Up: xml sax handler --- Base classes for SAX handlers

5.20.10.3 EntityResolver Objects
................................

 -- 成員函式: 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 Objects,  Prev: EntityResolver Objects,  Up: xml sax handler --- Base classes for SAX handlers

5.20.10.4 ErrorHandler Objects
..............................

Objects with this interface are used to receive error and warning
information from the *note XMLReader: 2aee.  If you create an object
that implements this interface, then register the object with your *note
XMLReader: 2aee, 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 ‘SAXParseException’ 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: xml sax saxutils --- SAX Utilities,  Next: xml sax xmlreader --- Interface for XML parsers,  Prev: xml sax handler --- Base classes for SAX handlers,  Up: Structured Markup Processing Tools

5.20.11 ‘xml.sax.saxutils’ — SAX Utilities
------------------------------------------

`Source code:' Lib/xml/sax/saxutils.py(1)

__________________________________________________________________

The module *note xml.sax.saxutils: 13e. 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.

 -- 函式: 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(): 2b31, 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(): 2b33. 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: 2aeb. interface by
     writing SAX events back into an XML document.  In other words,
     using an *note XMLGenerator: 2b34. 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 版新加入: The `short_empty_elements' parameter.

 -- 類別: xml.sax.saxutils.XMLFilterBase (base)

     This class is designed to sit between an *note XMLReader: 2aee. 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: 797. object ready for
     reading.  The input source can be given as a string, a file-like
     object, or an *note InputSource: 797. object; parsers will use this
     function to implement the polymorphic `source' argument to their
     ‘parse()’ method.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/xml/sax/saxutils.py


File: python.info,  Node: xml sax xmlreader --- Interface for XML parsers,  Next: xml parsers expat --- Fast XML parsing using Expat,  Prev: xml sax saxutils --- SAX Utilities,  Up: Structured Markup Processing Tools

5.20.12 ‘xml.sax.xmlreader’ — Interface for XML parsers
-------------------------------------------------------

`Source code:' Lib/xml/sax/xmlreader.py(1)

__________________________________________________________________

SAX parsers implement the *note XMLReader: 2aee. 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(): 102d. 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:
     2aee. 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(): 2b3a. method and for returning from
     EntityResolver.resolveEntity.

     An *note InputSource: 797. belongs to the application, the *note
     XMLReader: 2aee. is not allowed to modify *note InputSource: 797.
     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: 2b1b.).  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: 2b3b, which will
     be passed to ‘startElementNS()’.  It is derived from *note
     AttributesImpl: 2b3b, 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: 2b1d.).

* Menu:

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

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/xml/sax/xmlreader.py


File: python.info,  Node: XMLReader Objects,  Next: IncrementalParser Objects,  Up: xml sax xmlreader --- Interface for XML parsers

5.20.12.1 XMLReader Objects
...........................

The *note XMLReader: 2aee. 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: 202. or
     *note path-like: 36f. object, or an *note InputSource: 797. object.
     When *note parse(): 2b3a. returns, the input is completely
     processed, and the parser object can be discarded or reset.

     3.5 版更變: Added support of character streams.

     3.8 版更變: Added support of path-like objects.

 -- 成員函式: XMLReader.getContentHandler ()

     Return the current *note ContentHandler: 2aeb.

 -- 成員函式: XMLReader.setContentHandler (handler)

     Set the current *note ContentHandler: 2aeb.  If no *note
     ContentHandler: 2aeb. is set, content events will be discarded.

 -- 成員函式: XMLReader.getDTDHandler ()

     Return the current *note DTDHandler: 2b05.

 -- 成員函式: XMLReader.setDTDHandler (handler)

     Set the current *note DTDHandler: 2b05.  If no *note DTDHandler:
     2b05. is set, DTD events will be discarded.

 -- 成員函式: XMLReader.getEntityResolver ()

     Return the current *note EntityResolver: 2b06.

 -- 成員函式: XMLReader.setEntityResolver (handler)

     Set the current *note EntityResolver: 2b06.  If no *note
     EntityResolver: 2b06. 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: 2af9.

 -- 成員函式: XMLReader.setErrorHandler (handler)

     Set the current error handler.  If no *note ErrorHandler: 2af9. 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: 13d.

 -- 成員函式: 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: 13d.

 -- 成員函式: 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 Objects,  Next: Locator Objects,  Prev: XMLReader Objects,  Up: xml sax xmlreader --- Interface for XML parsers

5.20.12.2 IncrementalParser Objects
...................................

Instances of *note IncrementalParser: 2b39. 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 Objects,  Prev: IncrementalParser Objects,  Up: xml sax xmlreader --- Interface for XML parsers

5.20.12.3 Locator Objects
.........................

Instances of *note Locator: 2afb. 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 Objects,  Next: The Attributes Interface,  Prev: Locator Objects,  Up: xml sax xmlreader --- Interface for XML parsers

5.20.12.4 InputSource Objects
.............................

 -- 成員函式: InputSource.setPublicId (id)

     Sets the public identifier of this *note InputSource: 797.

 -- 成員函式: InputSource.getPublicId ()

     Returns the public identifier of this *note InputSource: 797.

 -- 成員函式: InputSource.setSystemId (id)

     Sets the system identifier of this *note InputSource: 797.

 -- 成員函式: InputSource.getSystemId ()

     Returns the system identifier of this *note InputSource: 797.

 -- 成員函式: InputSource.setEncoding (encoding)

     Sets the character encoding of this *note InputSource: 797.

     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: 797. is ignored if
     the *note InputSource: 797. 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: 1caa.) 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: 12aa.) 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 Objects,  Up: xml sax xmlreader --- Interface for XML parsers

5.20.12.5 The ‘Attributes’ Interface
....................................

‘Attributes’ objects implement a portion of the *note mapping protocol:
b3e, including the methods ‘copy()’, ‘get()’, *note __contains__(): d2d,
‘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 --- Interface for XML parsers

5.20.12.6 The ‘AttributesNS’ Interface
......................................

This interface is a subtype of the ‘Attributes’ interface (see section
*note The Attributes Interface: 2b1b.).  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 --- Fast XML parsing using Expat,  Prev: xml sax xmlreader --- Interface for XML parsers,  Up: Structured Markup Processing Tools

5.20.13 ‘xml.parsers.expat’ — Fast XML parsing using Expat
----------------------------------------------------------

__________________________________________________________________

     警告: The ‘pyexpat’ module is not secure against maliciously
     constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML vulnerabilities: 29fa.

The *note xml.parsers.expat: 139. 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 Exceptions: 2b6e. for more information on
     interpreting Expat errors.

 -- 例外: xml.parsers.expat.error

     Alias for *note ExpatError: c12.

 -- Data: xml.parsers.expat.XMLParserType

     The type of the return values from the *note ParserCreate(): 2b71.
     function.

The *note xml.parsers.expat: 139. 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: 1fc. 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 Objects: XMLParser Objects<2>.
* ExpatError Exceptions::
* Example: Example<12>.
* Content Model Descriptions::
* Expat error constants::

   ---------- Footnotes ----------

   (1) (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 Objects<2>,  Next: ExpatError Exceptions,  Up: xml parsers expat --- Fast XML parsing using Expat

5.20.13.1 XMLParser Objects
...........................

‘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(): 2b78,
     *note NotationDeclHandler(): 2b79, and *note
     UnparsedEntityDeclHandler(): 2b7a. functions.

 -- 成員函式: xmlparser.GetBase ()

     Returns a string containing the base set by a previous call to
     *note SetBase(): 2b77, or ‘None’ if *note SetBase(): 2b77. 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(): 2b78. handler function, described
     below.  The child parser is created with the *note
     ordered_attributes: 2b7e. and *note specified_attributes: 2b7f. 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: 2b78. with *note
     None: 158. for all arguments to allow an alternate DTD to be
     loaded.  If the document does not contain a document type
     declaration, the *note ExternalEntityRefHandler: 2b78. will still
     be called, but the *note StartDoctypeDeclHandler: 2b82. and *note
     EndDoctypeDeclHandler: 2b83. 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(): 2b75. or
     *note ParseFile(): 2b76. methods are called; calling it after
     either of those have been called causes *note ExpatError: c12. to
     be raised with the *note code: 1b. attribute set to
     ‘errors.codes[errors.XML_ERROR_CANT_CHANGE_FEATURE_ONCE_PARSING]’.

‘xmlparser’ objects have the following attributes:

 -- 屬性: xmlparser.buffer_size

     The size of the buffer used when *note buffer_text: 2b85. 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(): 2b86. 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.

 -- 屬性: xmlparser.buffer_used

     If *note buffer_text: 2b85. 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:
     2b85. 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: c12. 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(): 2b72. 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: 2b7e. is true, this is a
     list (see *note ordered_attributes: 2b7e. 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: 2b95, *note EndCdataSectionHandler: 2b96,
     and *note ElementDeclHandler: 2b90. callbacks to collect the
     required information.

 -- 成員函式: 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: 2b97. 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:
     2b92. 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: 2b98. was called to
     indicate the start of each namespace declaration’s scope.  Calls to
     this handler are made after the corresponding *note
     EndElementHandler: 2b93. 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: 2b96. 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(): 2b9b, 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(): 2b77.  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: 2b9b. callback, if provided.


File: python.info,  Node: ExpatError Exceptions,  Next: Example<12>,  Prev: XMLParser Objects<2>,  Up: xml parsers expat --- Fast XML parsing using Expat

5.20.13.2 ExpatError Exceptions
...............................

*note ExpatError: c12. exceptions have a number of interesting
attributes:

 -- 屬性: ExpatError.code

     Expat’s internal error number for the specific error.  The *note
     errors.messages: 2ba0. 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: 13a. module also provides error message constants
     and a dictionary *note codes: 2ba1. 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: Example<12>,  Next: Content Model Descriptions,  Prev: ExpatError Exceptions,  Up: xml parsers expat --- Fast XML parsing using Expat

5.20.13.3 Example
.................

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: Example<12>,  Up: xml parsers expat --- Fast XML parsing using Expat

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: 13b. 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:

 -- Data: xml.parsers.expat.model.XML_CTYPE_ANY

     The element named by the model name was declared to have a content
     model of ‘ANY’.

 -- Data: 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)’.

 -- Data: xml.parsers.expat.model.XML_CTYPE_EMPTY

     Elements which are declared to be ‘EMPTY’ have this model type.

 -- Data: xml.parsers.expat.model.XML_CTYPE_MIXED

 -- Data: xml.parsers.expat.model.XML_CTYPE_NAME

 -- Data: 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:

 -- Data: xml.parsers.expat.model.XML_CQUANT_NONE

     No modifier is given, so it can appear exactly once, as for ‘A’.

 -- Data: xml.parsers.expat.model.XML_CQUANT_OPT

     The model is optional: it can appear once or not at all, as for
     ‘A?’.

 -- Data: xml.parsers.expat.model.XML_CQUANT_PLUS

     The model must occur one or more times (like ‘A+’).

 -- Data: 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 --- Fast XML parsing using Expat

5.20.13.5 Expat error constants
...............................

The following constants are provided in the *note
xml.parsers.expat.errors: 13a. 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:
1b. attribute with ‘errors.codes[errors.XML_ERROR_`CONSTANT_NAME']’.

The ‘errors’ module has the following attributes:

 -- Data: xml.parsers.expat.errors.codes

     A dictionary mapping string descriptions to their error codes.

     3.2 版新加入.

 -- Data: xml.parsers.expat.errors.messages

     A dictionary mapping numeric error codes to their string
     descriptions.

     3.2 版新加入.

 -- Data: xml.parsers.expat.errors.XML_ERROR_ASYNC_ENTITY

 -- Data:
          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.

 -- Data: 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;’’).

 -- Data: 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.

 -- Data: xml.parsers.expat.errors.XML_ERROR_DUPLICATE_ATTRIBUTE

     An attribute was used more than once in a start tag.

 -- Data: xml.parsers.expat.errors.XML_ERROR_INCORRECT_ENCODING

 -- Data: 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.

 -- Data: xml.parsers.expat.errors.XML_ERROR_JUNK_AFTER_DOC_ELEMENT

     Something other than whitespace occurred after the document
     element.

 -- Data: xml.parsers.expat.errors.XML_ERROR_MISPLACED_XML_PI

     An XML declaration was found somewhere other than the start of the
     input data.

 -- 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)..

 -- Data: xml.parsers.expat.errors.XML_ERROR_NO_MEMORY

     Expat was not able to allocate memory internally.

 -- Data: xml.parsers.expat.errors.XML_ERROR_PARAM_ENTITY_REF

     A parameter entity reference was found where it was not allowed.

 -- Data: xml.parsers.expat.errors.XML_ERROR_PARTIAL_CHAR

     An incomplete character was found in the input.

 -- Data: 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.

 -- Data: xml.parsers.expat.errors.XML_ERROR_SYNTAX

     Some unspecified syntax error was encountered.

 -- Data: xml.parsers.expat.errors.XML_ERROR_TAG_MISMATCH

     An end tag did not match the innermost open start tag.

 -- Data: 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.

 -- Data: xml.parsers.expat.errors.XML_ERROR_UNDEFINED_ENTITY

     A reference was made to an entity which was not defined.

 -- Data: xml.parsers.expat.errors.XML_ERROR_UNKNOWN_ENCODING

     The document encoding is not supported by Expat.

 -- Data: xml.parsers.expat.errors.XML_ERROR_UNCLOSED_CDATA_SECTION

     A CDATA marked section was not closed.

 -- Data: xml.parsers.expat.errors.XML_ERROR_EXTERNAL_ENTITY_HANDLING

 -- Data: 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’.

 -- Data: xml.parsers.expat.errors.XML_ERROR_UNEXPECTED_STATE

 -- Data: xml.parsers.expat.errors.XML_ERROR_ENTITY_DECLARED_IN_PE

 -- Data: 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: 139. module.

 -- Data:
          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()’.

 -- Data: xml.parsers.expat.errors.XML_ERROR_UNBOUND_PREFIX

     An undeclared prefix was found when namespace processing was
     enabled.

 -- Data: xml.parsers.expat.errors.XML_ERROR_UNDECLARING_PREFIX

     The document attempted to remove the namespace declaration
     associated with a prefix.

 -- Data: xml.parsers.expat.errors.XML_ERROR_INCOMPLETE_PE

     A parameter entity contained incomplete markup.

 -- Data: xml.parsers.expat.errors.XML_ERROR_XML_DECL

     The document contained no document element at all.

 -- Data: xml.parsers.expat.errors.XML_ERROR_TEXT_DECL

     There was an error parsing a text declaration in an external
     entity.

 -- Data: xml.parsers.expat.errors.XML_ERROR_PUBLICID

     Characters were found in the public id that are not allowed.

 -- Data: 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.

 -- Data: xml.parsers.expat.errors.XML_ERROR_NOT_SUSPENDED

     An attempt to resume the parser was made when the parser had not
     been suspended.

 -- Data: xml.parsers.expat.errors.XML_ERROR_ABORTED

     This should not be reported to Python applications.

 -- Data: 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.

 -- Data: xml.parsers.expat.errors.XML_ERROR_SUSPEND_PE

註解
....


File: python.info,  Node: Internet Protocols and Support,  Next: Multimedia Services,  Prev: Structured Markup Processing Tools,  Up: Python 標準函式庫 Standard Library

5.21 Internet Protocols and Support
===================================

The modules described in this chapter implement Internet protocols and
support for related technology.  They are all implemented in Python.
Most of these modules require the presence of the system-dependent
module *note socket: f0, which is currently supported on most popular
platforms.  Here is an overview:

* Menu:

* webbrowser: webbrowser --- Convenient Web-browser controller. Convenient Web-browser controller
* cgi: cgi --- Common Gateway Interface support. Common Gateway Interface support
* cgitb: cgitb --- Traceback manager for CGI scripts. Traceback manager for CGI scripts
* wsgiref: wsgiref --- WSGI Utilities and Reference Implementation. WSGI Utilities and Reference Implementation
* urllib: urllib --- URL handling modules. URL handling modules
* urllib.request: urllib request --- Extensible library for opening URLs. Extensible library for opening URLs
* urllib.response: urllib response --- Response classes used by urllib. Response classes used by urllib
* urllib.parse: urllib parse --- Parse URLs into components. Parse URLs into components
* urllib.error: urllib error --- Exception classes raised by urllib request. Exception classes raised by urllib.request
* urllib.robotparser: urllib robotparser --- Parser for robots txt. Parser for robots.txt
* http: http --- HTTP modules. HTTP modules
* http.client: http client --- HTTP protocol client. HTTP protocol client
* ftplib: ftplib --- FTP protocol client. FTP protocol client
* poplib: poplib --- POP3 protocol client. POP3 protocol client
* imaplib: imaplib --- IMAP4 protocol client. IMAP4 protocol client
* nntplib: nntplib --- NNTP protocol client. NNTP protocol client
* smtplib: smtplib --- SMTP protocol client. SMTP protocol client
* smtpd: smtpd --- SMTP Server. SMTP Server
* telnetlib: telnetlib --- Telnet client. Telnet client
* uuid: uuid --- UUID objects according to RFC 4122. UUID objects according to RFC 4122
* socketserver: socketserver --- A framework for network servers. A framework for network servers
* http.server: http server --- HTTP servers. HTTP servers
* http.cookies: http cookies --- HTTP state management. HTTP state management
* http.cookiejar: http cookiejar --- Cookie handling for HTTP clients. Cookie handling for HTTP clients
* xmlrpc: xmlrpc --- XMLRPC server and client modules. XMLRPC server and client modules
* xmlrpc.client: xmlrpc client --- XML-RPC client access. XML-RPC client access
* xmlrpc.server: xmlrpc server --- Basic XML-RPC servers. Basic XML-RPC servers
* ipaddress: ipaddress --- IPv4/IPv6 manipulation library. IPv4/IPv6 manipulation library


File: python.info,  Node: webbrowser --- Convenient Web-browser controller,  Next: cgi --- Common Gateway Interface support,  Up: Internet Protocols and Support

5.21.1 ‘webbrowser’ — Convenient Web-browser controller
-------------------------------------------------------

`Source code:' Lib/webbrowser.py(1)

__________________________________________________________________

The *note webbrowser: 12a. module provides a high-level interface to
allow displaying Web-based documents to users.  Under most
circumstances, simply calling the *note open(): 2bd4. 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: 135a.-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.

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’ opens the URL in a new browser window, if
possible; ‘-t’ opens the URL in a new browser page ("tab").  The options
are, naturally, mutually exclusive.  Usage example:

     python -m webbrowser -t "http://www.python.org"

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).

     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.

     Raises an *note auditing event: e96. ‘webbrowser.open’ with
     argument ‘url’.

 -- 函式: webbrowser.open_new (url)

     Open `url' in a new window of the default browser, if possible,
     otherwise, open `url' in the only browser window.

 -- 函式: webbrowser.open_new_tab (url)

     Open `url' in a new page ("tab") of the default browser, if
     possible, otherwise equivalent to *note open_new(): 2bd6.

 -- 函式: 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(): 2bd8. 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(): 2bd8. call with no argument.  Otherwise, this
     entry point is only useful if you plan to either set the ‘BROWSER’
     variable or call *note get(): 2bd8. 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(): 2bd8. function and the
corresponding instantiations for the controller classes, all defined in
this module.

Type Name                    Class Name                                    註解
                                                                           
---------------------------------------------------------------------------------------
                                                                           
‘'mozilla'’                  ‘Mozilla('mozilla')’
                             
                                                                           
‘'firefox'’                  ‘Mozilla('mozilla')’
                             
                                                                           
‘'netscape'’                 ‘Mozilla('netscape')’
                             
                                                                           
‘'galeon'’                   ‘Galeon('galeon')’
                             
                                                                           
‘'epiphany'’                 ‘Galeon('epiphany')’
                             
                                                                           
‘'skipstone'’                ‘BackgroundBrowser('skipstone')’
                             
                                                                           
‘'kfmclient'’                ‘Konqueror()’                                 (1)
                                                                           
                                                                           
‘'konqueror'’                ‘Konqueror()’                                 (1)
                                                                           
                                                                           
‘'kfm'’                      ‘Konqueror()’                                 (1)
                                                                           
                                                                           
‘'mosaic'’                   ‘BackgroundBrowser('mosaic')’
                             
                                                                           
‘'opera'’                    ‘Opera()’
                             
                                                                           
‘'grail'’                    ‘Grail()’
                             
                                                                           
‘'links'’                    ‘GenericBrowser('links')’
                             
                                                                           
‘'elinks'’                   ‘Elinks('elinks')’
                             
                                                                           
‘'lynx'’                     ‘GenericBrowser('lynx')’
                             
                                                                           
‘'w3m'’                      ‘GenericBrowser('w3m')’
                             
                                                                           
‘'windows-default'’          ‘WindowsDefault’                              (2)
                                                                           
                                                                           
‘'macosx'’                   ‘MacOSX('default')’                           (3)
                                                                           
                                                                           
‘'safari'’                   ‘MacOSX('safari')’                            (3)
                                                                           
                                                                           
‘'google-chrome'’            ‘Chrome('google-chrome')’
                             
                                                                           
‘'chrome'’                   ‘Chrome('chrome')’
                             
                                                                           
‘'chromium'’                 ‘Chromium('chromium')’
                             
                                                                           
‘'chromium-browser'’         ‘Chromium('chromium-browser')’
                             

註解：

  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 Mac OS X platform.

3.3 版新加入: Support for Chrome/Chromium has been added.

Here are some simple examples:

     url = 'http://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.8/Lib/webbrowser.py

   (2) (1) 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 --- Convenient Web-browser controller

5.21.1.1 Browser Controller Objects
...................................

Browser controllers provide these methods which parallel three of the
module-level convenience functions:

 -- 成員函式: 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(): 2bd6.

 -- 成員函式: 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():
     2bd6.

註解
....


File: python.info,  Node: cgi --- Common Gateway Interface support,  Next: cgitb --- Traceback manager for CGI scripts,  Prev: webbrowser --- Convenient Web-browser controller,  Up: Internet Protocols and Support

5.21.2 ‘cgi’ — Common Gateway Interface support
-----------------------------------------------

`Source code:' Lib/cgi.py(1)

__________________________________________________________________

Support module for Common Gateway Interface (CGI) scripts.

This module defines a number of utilities for use by CGI scripts written
in Python.

* Menu:

* 簡介: 簡介<10>.
* Using the cgi module::
* Higher Level Interface::
* Functions: Functions<8>.
* Caring about security::
* Installing your CGI script on a Unix system::
* Testing your CGI script::
* Debugging CGI scripts::
* Common problems and solutions::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/cgi.py


File: python.info,  Node: 簡介<10>,  Next: Using the cgi module,  Up: cgi --- Common Gateway Interface support

5.21.2.1 簡介
.............

A CGI script is invoked by an HTTP server, usually to process user input
submitted through an HTML ‘<FORM>’ or ‘<ISINDEX>’ element.

Most often, CGI scripts live in the server’s special ‘cgi-bin’
directory.  The HTTP server places all sorts of information about the
request (such as the client’s hostname, the requested URL, the query
string, and lots of other goodies) in the script’s shell environment,
executes the script, and sends the script’s output back to the client.

The script’s input is connected to the client too, and sometimes the
form data is read this way; at other times the form data is passed via
the "query string" part of the URL. This module is intended to take care
of the different cases and provide a simpler interface to the Python
script.  It also provides a number of utilities that help in debugging
scripts, and the latest addition is support for file uploads from a form
(if your browser supports it).

The output of a CGI script should consist of two sections, separated by
a blank line.  The first section contains a number of headers, telling
the client what kind of data is following.  Python code to generate a
minimal header section looks like this:

     print("Content-Type: text/html")    # HTML is following
     print()                             # blank line, end of headers

The second section is usually HTML, which allows the client software to
display nicely formatted text with header, in-line images, etc.  Here’s
Python code that prints a simple piece of HTML:

     print("<TITLE>CGI script output</TITLE>")
     print("<H1>This is my first CGI script</H1>")
     print("Hello, world!")


File: python.info,  Node: Using the cgi module,  Next: Higher Level Interface,  Prev: 簡介<10>,  Up: cgi --- Common Gateway Interface support

5.21.2.2 Using the cgi module
.............................

Begin by writing ‘import cgi’.

When you write a new script, consider adding these lines:

     import cgitb
     cgitb.enable()

This activates a special exception handler that will display detailed
reports in the Web browser if any errors occur.  If you’d rather not
show the guts of your program to users of your script, you can have the
reports saved to files instead, with code like this:

     import cgitb
     cgitb.enable(display=0, logdir="/path/to/logdir")

It’s very helpful to use this feature during script development.  The
reports produced by *note cgitb: 17. provide information that can save
you a lot of time in tracking down bugs.  You can always remove the
‘cgitb’ line later when you have tested your script and are confident
that it works correctly.

To get at submitted form data, use the ‘FieldStorage’ class.  If the
form contains non-ASCII characters, use the `encoding' keyword parameter
set to the value of the encoding defined for the document.  It is
usually contained in the META tag in the HEAD section of the HTML
document or by the ‘Content-Type’ header).  This reads the form contents
from the standard input or the environment (depending on the value of
various environment variables set according to the CGI standard).  Since
it may consume standard input, it should be instantiated only once.

The ‘FieldStorage’ instance can be indexed like a Python dictionary.  It
allows membership testing with the *note in: 7a8. operator, and also
supports the standard dictionary method *note keys(): c2f. and the
built-in function *note len(): 151.  Form fields containing empty
strings are ignored and do not appear in the dictionary; to keep such
values, provide a true value for the optional `keep_blank_values'
keyword parameter when creating the ‘FieldStorage’ instance.

For instance, the following code (which assumes that the ‘Content-Type’
header and blank line have already been printed) checks that the fields
‘name’ and ‘addr’ are both set to a non-empty string:

     form = cgi.FieldStorage()
     if "name" not in form or "addr" not in form:
         print("<H1>Error</H1>")
         print("Please fill in the name and addr fields.")
         return
     print("<p>name:", form["name"].value)
     print("<p>addr:", form["addr"].value)
     ...further form processing here...

Here the fields, accessed through ‘form[key]’, are themselves instances
of ‘FieldStorage’ (or ‘MiniFieldStorage’, depending on the form
encoding).  The ‘value’ attribute of the instance yields the string
value of the field.  The ‘getvalue()’ method returns this string value
directly; it also accepts an optional second argument as a default to
return if the requested key is not present.

If the submitted form data contains more than one field with the same
name, the object retrieved by ‘form[key]’ is not a ‘FieldStorage’ or
‘MiniFieldStorage’ instance but a list of such instances.  Similarly, in
this situation, ‘form.getvalue(key)’ would return a list of strings.  If
you expect this possibility (when your HTML form contains multiple
fields with the same name), use the *note getlist(): 2be5. method, which
always returns a list of values (so that you do not need to special-case
the single item case).  For example, this code concatenates any number
of username fields, separated by commas:

     value = form.getlist("username")
     usernames = ",".join(value)

If a field represents an uploaded file, accessing the value via the
‘value’ attribute or the ‘getvalue()’ method reads the entire file in
memory as bytes.  This may not be what you want.  You can test for an
uploaded file by testing either the ‘filename’ attribute or the ‘file’
attribute.  You can then read the data from the ‘file’ attribute before
it is automatically closed as part of the garbage collection of the
‘FieldStorage’ instance (the *note read(): 707. and *note readline():
1708. methods will return bytes):

     fileitem = form["userfile"]
     if fileitem.file:
         # It's an uploaded file; count lines
         linecount = 0
         while True:
             line = fileitem.file.readline()
             if not line: break
             linecount = linecount + 1

‘FieldStorage’ objects also support being used in a *note with: 6ee.
statement, which will automatically close them when done.

If an error is encountered when obtaining the contents of an uploaded
file (for example, when the user interrupts the form submission by
clicking on a Back or Cancel button) the ‘done’ attribute of the object
for the field will be set to the value -1.

The file upload draft standard entertains the possibility of uploading
multiple files from one field (using a recursive ‘multipart/*’
encoding).  When this occurs, the item will be a dictionary-like
‘FieldStorage’ item.  This can be determined by testing its ‘type’
attribute, which should be ‘multipart/form-data’ (or perhaps another
MIME type matching ‘multipart/*’).  In this case, it can be iterated
over recursively just like the top-level form object.

When a form is submitted in the "old" format (as the query string or as
a single data part of type ‘application/x-www-form-urlencoded’), the
items will actually be instances of the class ‘MiniFieldStorage’.  In
this case, the ‘list’, ‘file’, and ‘filename’ attributes are always
‘None’.

A form submitted via POST that also has a query string will contain both
‘FieldStorage’ and ‘MiniFieldStorage’ items.

3.4 版更變: The ‘file’ attribute is automatically closed upon the
garbage collection of the creating ‘FieldStorage’ instance.

3.5 版更變: Added support for the context management protocol to the
‘FieldStorage’ class.


File: python.info,  Node: Higher Level Interface,  Next: Functions<8>,  Prev: Using the cgi module,  Up: cgi --- Common Gateway Interface support

5.21.2.3 Higher Level Interface
...............................

The previous section explains how to read CGI form data using the
‘FieldStorage’ class.  This section describes a higher level interface
which was added to this class to allow one to do it in a more readable
and intuitive way.  The interface doesn’t make the techniques described
in previous sections obsolete — they are still useful to process file
uploads efficiently, for example.

The interface consists of two simple methods.  Using the methods you can
process form data in a generic way, without the need to worry whether
only one or more values were posted under one name.

In the previous section, you learned to write following code anytime you
expected a user to post more than one value under one name:

     item = form.getvalue("item")
     if isinstance(item, list):
         # The user is requesting more than one item.
     else:
         # The user is requesting only one item.

This situation is common for example when a form contains a group of
multiple checkboxes with the same name:

     <input type="checkbox" name="item" value="1" />
     <input type="checkbox" name="item" value="2" />

In most situations, however, there’s only one form control with a
particular name in a form and then you expect and need only one value
associated with this name.  So you write a script containing for example
this code:

     user = form.getvalue("user").upper()

The problem with the code is that you should never expect that a client
will provide valid input to your scripts.  For example, if a curious
user appends another ‘user=foo’ pair to the query string, then the
script would crash, because in this situation the ‘getvalue("user")’
method call returns a list instead of a string.  Calling the *note
upper(): 1663. method on a list is not valid (since lists do not have a
method of this name) and results in an *note AttributeError: 3a0.
exception.

Therefore, the appropriate way to read form data values was to always
use the code which checks whether the obtained value is a single value
or a list of values.  That’s annoying and leads to less readable
scripts.

A more convenient approach is to use the methods *note getfirst(): 2be7.
and *note getlist(): 2be5. provided by this higher level interface.

 -- 成員函式: FieldStorage.getfirst (name, default=None)

     This method always returns only one value associated with form
     field `name'.  The method returns only the first value in case that
     more values were posted under such name.  Please note that the
     order in which the values are received may vary from browser to
     browser and should not be counted on.  (1) If no such form field or
     value exists then the method returns the value specified by the
     optional parameter `default'.  This parameter defaults to ‘None’ if
     not specified.

 -- 成員函式: FieldStorage.getlist (name)

     This method always returns a list of values associated with form
     field `name'.  The method returns an empty list if no such form
     field or value exists for `name'.  It returns a list consisting of
     one item if only one such value exists.

Using these methods you can write nice compact code:

     import cgi
     form = cgi.FieldStorage()
     user = form.getfirst("user", "").upper()    # This way it's safe.
     for item in form.getlist("item"):
         do_something(item)

   ---------- Footnotes ----------

   (1) (1) Note that some recent versions of the HTML specification do
state what order the field values should be supplied in, but knowing
whether a request was received from a conforming browser, or even from a
browser at all, is tedious and error-prone.


File: python.info,  Node: Functions<8>,  Next: Caring about security,  Prev: Higher Level Interface,  Up: cgi --- Common Gateway Interface support

5.21.2.4 Functions
..................

These are useful if you want more control, or if you want to employ some
of the algorithms implemented in this module in other circumstances.

 -- 函式: cgi.parse (fp=None, environ=os.environ,
          keep_blank_values=False, strict_parsing=False, separator="&")

     Parse a query in the environment or from a file (the file defaults
     to ‘sys.stdin’).  The `keep_blank_values', `strict_parsing' and
     `separator' parameters are passed to *note urllib.parse.parse_qs():
     2ec. unchanged.

     3.8.8 版更變: Added the `separator' parameter.

 -- 函式: cgi.parse_multipart (fp, pdict, encoding="utf-8",
          errors="replace", separator="&")

     Parse input of type ‘multipart/form-data’ (for file uploads).
     Arguments are `fp' for the input file, `pdict' for a dictionary
     containing other parameters in the ‘Content-Type’ header, and
     `encoding', the request encoding.

     Returns a dictionary just like *note urllib.parse.parse_qs(): 2ec.:
     keys are the field names, each value is a list of values for that
     field.  For non-file fields, the value is a list of strings.

     This is easy to use but not much good if you are expecting
     megabytes to be uploaded — in that case, use the ‘FieldStorage’
     class instead which is much more flexible.

     3.7 版更變: Added the `encoding' and `errors' parameters.  For
     non-file fields, the value is now a list of strings, not bytes.

     3.8.8 版更變: Added the `separator' parameter.

 -- 函式: cgi.parse_header (string)

     Parse a MIME header (such as ‘Content-Type’) into a main value and
     a dictionary of parameters.

 -- 函式: cgi.test ()

     Robust test CGI script, usable as main program.  Writes minimal
     HTTP headers and formats all information provided to the script in
     HTML form.

 -- 函式: cgi.print_environ ()

     Format the shell environment in HTML.

 -- 函式: cgi.print_form (form)

     Format a form in HTML.

 -- 函式: cgi.print_directory ()

     Format the current directory in HTML.

 -- 函式: cgi.print_environ_usage ()

     Print a list of useful (used by CGI) environment variables in HTML.


File: python.info,  Node: Caring about security,  Next: Installing your CGI script on a Unix system,  Prev: Functions<8>,  Up: cgi --- Common Gateway Interface support

5.21.2.5 Caring about security
..............................

There’s one important rule: if you invoke an external program (via the
*note os.system(): dc6. or *note os.popen(): 2aa. functions.  or others
with similar functionality), make very sure you don’t pass arbitrary
strings received from the client to the shell.  This is a well-known
security hole whereby clever hackers anywhere on the Web can exploit a
gullible CGI script to invoke arbitrary shell commands.  Even parts of
the URL or field names cannot be trusted, since the request doesn’t have
to come from your form!

To be on the safe side, if you must pass a string gotten from a form to
a shell command, you should make sure the string contains only
alphanumeric characters, dashes, underscores, and periods.


File: python.info,  Node: Installing your CGI script on a Unix system,  Next: Testing your CGI script,  Prev: Caring about security,  Up: cgi --- Common Gateway Interface support

5.21.2.6 Installing your CGI script on a Unix system
....................................................

Read the documentation for your HTTP server and check with your local
system administrator to find the directory where CGI scripts should be
installed; usually this is in a directory ‘cgi-bin’ in the server tree.

Make sure that your script is readable and executable by "others"; the
Unix file mode should be ‘0o755’ octal (use ‘chmod 0755 filename’).
Make sure that the first line of the script contains ‘#!’ starting in
column 1 followed by the pathname of the Python interpreter, for
instance:

     #!/usr/local/bin/python

Make sure the Python interpreter exists and is executable by "others".

Make sure that any files your script needs to read or write are readable
or writable, respectively, by "others" — their mode should be ‘0o644’
for readable and ‘0o666’ for writable.  This is because, for security
reasons, the HTTP server executes your script as user "nobody", without
any special privileges.  It can only read (write, execute) files that
everybody can read (write, execute).  The current directory at execution
time is also different (it is usually the server’s cgi-bin directory)
and the set of environment variables is also different from what you get
when you log in.  In particular, don’t count on the shell’s search path
for executables ( ‘PATH’) or the Python module search path ( *note
PYTHONPATH: 958.) to be set to anything interesting.

If you need to load modules from a directory which is not on Python’s
default module search path, you can change the path in your script,
before importing other modules.  For example:

     import sys
     sys.path.insert(0, "/usr/home/joe/lib/python")
     sys.path.insert(0, "/usr/local/lib/python")

(This way, the directory inserted last will be searched first!)

Instructions for non-Unix systems will vary; check your HTTP server’s
documentation (it will usually have a section on CGI scripts).


File: python.info,  Node: Testing your CGI script,  Next: Debugging CGI scripts,  Prev: Installing your CGI script on a Unix system,  Up: cgi --- Common Gateway Interface support

5.21.2.7 Testing your CGI script
................................

Unfortunately, a CGI script will generally not run when you try it from
the command line, and a script that works perfectly from the command
line may fail mysteriously when run from the server.  There’s one reason
why you should still test your script from the command line: if it
contains a syntax error, the Python interpreter won’t execute it at all,
and the HTTP server will most likely send a cryptic error to the client.

Assuming your script has no syntax errors, yet it does not work, you
have no choice but to read the next section.


File: python.info,  Node: Debugging CGI scripts,  Next: Common problems and solutions,  Prev: Testing your CGI script,  Up: cgi --- Common Gateway Interface support

5.21.2.8 Debugging CGI scripts
..............................

First of all, check for trivial installation errors — reading the
section above on installing your CGI script carefully can save you a lot
of time.  If you wonder whether you have understood the installation
procedure correctly, try installing a copy of this module file
(‘cgi.py’) as a CGI script.  When invoked as a script, the file will
dump its environment and the contents of the form in HTML form.  Give it
the right mode etc, and send it a request.  If it’s installed in the
standard ‘cgi-bin’ directory, it should be possible to send it a request
by entering a URL into your browser of the form:

     http://yourhostname/cgi-bin/cgi.py?name=Joe+Blow&addr=At+Home

If this gives an error of type 404, the server cannot find the script –
perhaps you need to install it in a different directory.  If it gives
another error, there’s an installation problem that you should fix
before trying to go any further.  If you get a nicely formatted listing
of the environment and form content (in this example, the fields should
be listed as "addr" with value "At Home" and "name" with value "Joe
Blow"), the ‘cgi.py’ script has been installed correctly.  If you follow
the same procedure for your own script, you should now be able to debug
it.

The next step could be to call the *note cgi: 16. module’s *note test():
106. function from your script: replace its main code with the single
statement

     cgi.test()

This should produce the same results as those gotten from installing the
‘cgi.py’ file itself.

When an ordinary Python script raises an unhandled exception (for
whatever reason: of a typo in a module name, a file that can’t be
opened, etc.), the Python interpreter prints a nice traceback and exits.
While the Python interpreter will still do this when your CGI script
raises an exception, most likely the traceback will end up in one of the
HTTP server’s log files, or be discarded altogether.

Fortunately, once you have managed to get your script to execute `some'
code, you can easily send tracebacks to the Web browser using the *note
cgitb: 17. module.  If you haven’t done so already, just add the lines:

     import cgitb
     cgitb.enable()

to the top of your script.  Then try running it again; when a problem
occurs, you should see a detailed report that will likely make apparent
the cause of the crash.

If you suspect that there may be a problem in importing the *note cgitb:
17. module, you can use an even more robust approach (which only uses
built-in modules):

     import sys
     sys.stderr = sys.stdout
     print("Content-Type: text/plain")
     print()
     ...your code here...

This relies on the Python interpreter to print the traceback.  The
content type of the output is set to plain text, which disables all HTML
processing.  If your script works, the raw HTML will be displayed by
your client.  If it raises an exception, most likely after the first two
lines have been printed, a traceback will be displayed.  Because no HTML
interpretation is going on, the traceback will be readable.


File: python.info,  Node: Common problems and solutions,  Prev: Debugging CGI scripts,  Up: cgi --- Common Gateway Interface support

5.21.2.9 Common problems and solutions
......................................

   * Most HTTP servers buffer the output from CGI scripts until the
     script is completed.  This means that it is not possible to display
     a progress report on the client’s display while the script is
     running.

   * Check the installation instructions above.

   * Check the HTTP server’s log files.  (‘tail -f logfile’ in a
     separate window may be useful!)

   * Always check a script for syntax errors first, by doing something
     like ‘python script.py’.

   * If your script does not have any syntax errors, try adding ‘import
     cgitb; cgitb.enable()’ to the top of the script.

   * When invoking external programs, make sure they can be found.
     Usually, this means using absolute path names — ‘PATH’ is usually
     not set to a very useful value in a CGI script.

   * When reading or writing external files, make sure they can be read
     or written by the userid under which your CGI script will be
     running: this is typically the userid under which the web server is
     running, or some explicitly specified userid for a web server’s
     ‘suexec’ feature.

   * Don’t try to give a CGI script a set-uid mode.  This doesn’t work
     on most systems, and is a security liability as well.

註解
....


File: python.info,  Node: cgitb --- Traceback manager for CGI scripts,  Next: wsgiref --- WSGI Utilities and Reference Implementation,  Prev: cgi --- Common Gateway Interface support,  Up: Internet Protocols and Support

5.21.3 ‘cgitb’ — Traceback manager for CGI scripts
--------------------------------------------------

`Source code:' Lib/cgitb.py(1)

__________________________________________________________________

The *note cgitb: 17. module provides a special exception handler for
Python scripts.  (Its name is a bit misleading.  It was originally
designed to display extensive traceback information in HTML for CGI
scripts.  It was later generalized to also display this information in
plain text.)  After this module is activated, if an uncaught exception
occurs, a detailed, formatted report will be displayed.  The report
includes a traceback showing excerpts of the source code for each level,
as well as the values of the arguments and local variables to currently
running functions, to help you debug the problem.  Optionally, you can
save this information to a file instead of sending it to the browser.

To enable this feature, simply add this to the top of your CGI script:

     import cgitb
     cgitb.enable()

The options to the *note enable(): 2bf8. function control whether the
report is displayed in the browser and whether the report is logged to a
file for later analysis.

 -- 函式: cgitb.enable (display=1, logdir=None, context=5,
          format="html")

     This function causes the *note cgitb: 17. module to take over the
     interpreter’s default handling for exceptions by setting the value
     of *note sys.excepthook: e68.

     The optional argument `display' defaults to ‘1’ and can be set to
     ‘0’ to suppress sending the traceback to the browser.  If the
     argument `logdir' is present, the traceback reports are written to
     files.  The value of `logdir' should be a directory where these
     files will be placed.  The optional argument `context' is the
     number of lines of context to display around the current line of
     source code in the traceback; this defaults to ‘5’.  If the
     optional argument `format' is ‘"html"’, the output is formatted as
     HTML. Any other value forces plain text output.  The default value
     is ‘"html"’.

 -- 函式: cgitb.text (info, context=5)

     This function handles the exception described by `info' (a 3-tuple
     containing the result of *note sys.exc_info(): c64.), formatting
     its traceback as text and returning the result as a string.  The
     optional argument `context' is the number of lines of context to
     display around the current line of source code in the traceback;
     this defaults to ‘5’.

 -- 函式: cgitb.html (info, context=5)

     This function handles the exception described by `info' (a 3-tuple
     containing the result of *note sys.exc_info(): c64.), formatting
     its traceback as HTML and returning the result as a string.  The
     optional argument `context' is the number of lines of context to
     display around the current line of source code in the traceback;
     this defaults to ‘5’.

 -- 函式: cgitb.handler (info=None)

     This function handles an exception using the default settings (that
     is, show a report in the browser, but don’t log to a file).  This
     can be used when you’ve caught an exception and want to report it
     using *note cgitb: 17.  The optional `info' argument should be a
     3-tuple containing an exception type, exception value, and
     traceback object, exactly like the tuple returned by *note
     sys.exc_info(): c64.  If the `info' argument is not supplied, the
     current exception is obtained from *note sys.exc_info(): c64.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/cgitb.py


File: python.info,  Node: wsgiref --- WSGI Utilities and Reference Implementation,  Next: urllib --- URL handling modules,  Prev: cgitb --- Traceback manager for CGI scripts,  Up: Internet Protocols and Support

5.21.4 ‘wsgiref’ — WSGI Utilities and Reference Implementation
--------------------------------------------------------------

__________________________________________________________________

The Web Server Gateway Interface (WSGI) is a standard interface between
web server software and web applications written in Python.  Having a
standard interface makes it easy to use an application that supports
WSGI with a number of different web servers.

Only authors of web servers and programming frameworks need to know
every detail and corner case of the WSGI design.  You don’t need to
understand every detail of WSGI just to install a WSGI application or to
write a web application using an existing framework.

*note wsgiref: 12d. is a reference implementation of the WSGI
specification that can be used to add WSGI support to a web server or
framework.  It provides utilities for manipulating WSGI environment
variables and response headers, base classes for implementing WSGI
servers, a demo HTTP server that serves WSGI applications, and a
validation tool that checks WSGI servers and applications for
conformance to the WSGI specification ( PEP 3333(1)).

See wsgi.readthedocs.io(2) for more information about WSGI, and links to
tutorials and other resources.

* Menu:

* wsgiref.util: wsgiref util -- WSGI environment utilities. WSGI environment utilities
* wsgiref.headers: wsgiref headers -- WSGI response header tools. WSGI response header tools
* wsgiref.simple_server: wsgiref simple_server -- a simple WSGI HTTP server. a simple WSGI HTTP server
* wsgiref.validate: wsgiref validate --- WSGI conformance checker. WSGI conformance checker
* wsgiref.handlers: wsgiref handlers -- server/gateway base classes. server/gateway base classes
* Examples: Examples<20>.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3333

   (2) https://wsgi.readthedocs.io/


File: python.info,  Node: wsgiref util -- WSGI environment utilities,  Next: wsgiref headers -- WSGI response header tools,  Up: wsgiref --- WSGI Utilities and Reference Implementation

5.21.4.1 ‘wsgiref.util’ – WSGI environment utilities
....................................................

This module provides a variety of utility functions for working with
WSGI environments.  A WSGI environment is a dictionary containing HTTP
request variables as described in PEP 3333(1).  All of the functions
taking an `environ' parameter expect a WSGI-compliant dictionary to be
supplied; please see PEP 3333(2) for a detailed specification.

 -- 函式: wsgiref.util.guess_scheme (environ)

     Return a guess for whether ‘wsgi.url_scheme’ should be "http" or
     "https", by checking for a ‘HTTPS’ environment variable in the
     `environ' dictionary.  The return value is a string.

     This function is useful when creating a gateway that wraps CGI or a
     CGI-like protocol such as FastCGI. Typically, servers providing
     such protocols will include a ‘HTTPS’ variable with a value of "1",
     "yes", or "on" when a request is received via SSL. So, this
     function returns "https" if such a value is found, and "http"
     otherwise.

 -- 函式: wsgiref.util.request_uri (environ, include_query=True)

     Return the full request URI, optionally including the query string,
     using the algorithm found in the "URL Reconstruction" section of
     PEP 3333(3).  If `include_query' is false, the query string is not
     included in the resulting URI.

 -- 函式: wsgiref.util.application_uri (environ)

     Similar to *note request_uri(): 2c00, except that the ‘PATH_INFO’
     and ‘QUERY_STRING’ variables are ignored.  The result is the base
     URI of the application object addressed by the request.

 -- 函式: wsgiref.util.shift_path_info (environ)

     Shift a single name from ‘PATH_INFO’ to ‘SCRIPT_NAME’ and return
     the name.  The `environ' dictionary is `modified' in-place; use a
     copy if you need to keep the original ‘PATH_INFO’ or ‘SCRIPT_NAME’
     intact.

     If there are no remaining path segments in ‘PATH_INFO’, ‘None’ is
     returned.

     Typically, this routine is used to process each portion of a
     request URI path, for example to treat the path as a series of
     dictionary keys.  This routine modifies the passed-in environment
     to make it suitable for invoking another WSGI application that is
     located at the target URI. For example, if there is a WSGI
     application at ‘/foo’, and the request URI path is ‘/foo/bar/baz’,
     and the WSGI application at ‘/foo’ calls *note shift_path_info():
     2c02, it will receive the string "bar", and the environment will be
     updated to be suitable for passing to a WSGI application at
     ‘/foo/bar’.  That is, ‘SCRIPT_NAME’ will change from ‘/foo’ to
     ‘/foo/bar’, and ‘PATH_INFO’ will change from ‘/bar/baz’ to ‘/baz’.

     When ‘PATH_INFO’ is just a "/", this routine returns an empty
     string and appends a trailing slash to ‘SCRIPT_NAME’, even though
     empty path segments are normally ignored, and ‘SCRIPT_NAME’ doesn’t
     normally end in a slash.  This is intentional behavior, to ensure
     that an application can tell the difference between URIs ending in
     ‘/x’ from ones ending in ‘/x/’ when using this routine to do object
     traversal.

 -- 函式: wsgiref.util.setup_testing_defaults (environ)

     Update `environ' with trivial defaults for testing purposes.

     This routine adds various parameters required for WSGI, including
     ‘HTTP_HOST’, ‘SERVER_NAME’, ‘SERVER_PORT’, ‘REQUEST_METHOD’,
     ‘SCRIPT_NAME’, ‘PATH_INFO’, and all of the PEP 3333(4)-defined
     ‘wsgi.*’ variables.  It only supplies default values, and does not
     replace any existing settings for these variables.

     This routine is intended to make it easier for unit tests of WSGI
     servers and applications to set up dummy environments.  It should
     NOT be used by actual WSGI servers or applications, since the data
     is fake!

     Example usage:

          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()

In addition to the environment functions above, the *note wsgiref.util:
131. module also provides these miscellaneous utilities:

 -- 函式: wsgiref.util.is_hop_by_hop (header_name)

     Return ‘True’ if ’header_name’ is an HTTP/1.1 "Hop-by-Hop" header,
     as defined by RFC 2616(5).

 -- 類別: wsgiref.util.FileWrapper (filelike, blksize=8192)

     A wrapper to convert a file-like object to an *note iterator: 1040.
     The resulting objects support both *note __getitem__(): 27d. and
     *note __iter__(): 514. iteration styles, for compatibility with
     Python 2.1 and Jython.  As the object is iterated over, the
     optional `blksize' parameter will be repeatedly passed to the
     `filelike' object’s ‘read()’ method to obtain bytestrings to yield.
     When ‘read()’ returns an empty bytestring, iteration is ended and
     is not resumable.

     If `filelike' has a ‘close()’ method, the returned object will also
     have a ‘close()’ method, and it will invoke the `filelike' object’s
     ‘close()’ method when called.

     Example usage:

          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.8 版後已棄用: Support for *note sequence protocol: 27d. is
     deprecated.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3333

   (2) https://www.python.org/dev/peps/pep-3333

   (3) https://www.python.org/dev/peps/pep-3333

   (4) https://www.python.org/dev/peps/pep-3333

   (5) https://tools.ietf.org/html/rfc2616.html


File: python.info,  Node: wsgiref headers -- WSGI response header tools,  Next: wsgiref simple_server -- a simple WSGI HTTP server,  Prev: wsgiref util -- WSGI environment utilities,  Up: wsgiref --- WSGI Utilities and Reference Implementation

5.21.4.2 ‘wsgiref.headers’ – WSGI response header tools
.......................................................

This module provides a single class, *note Headers: 794, for convenient
manipulation of WSGI response headers using a mapping-like interface.

 -- 類別: wsgiref.headers.Headers ([headers])

     Create a mapping-like object wrapping `headers', which must be a
     list of header name/value tuples as described in PEP 3333(1).  The
     default value of `headers' is an empty list.

     *note Headers: 794. objects support typical mapping operations
     including *note __getitem__(): 27d, ‘get()’, *note __setitem__():
     c67, ‘setdefault()’, *note __delitem__(): c68. and *note
     __contains__(): d2d.  For each of these methods, the key is the
     header name (treated case-insensitively), and the value is the
     first value associated with that header name.  Setting a header
     deletes any existing values for that header, then adds a new value
     at the end of the wrapped header list.  Headers’ existing order is
     generally maintained, with new headers added to the end of the
     wrapped list.

     Unlike a dictionary, *note Headers: 794. objects do not raise an
     error when you try to get or delete a key that isn’t in the wrapped
     header list.  Getting a nonexistent header just returns ‘None’, and
     deleting a nonexistent header does nothing.

     *note Headers: 794. objects also support ‘keys()’, ‘values()’, and
     ‘items()’ methods.  The lists returned by ‘keys()’ and ‘items()’
     can include the same key more than once if there is a multi-valued
     header.  The ‘len()’ of a *note Headers: 794. object is the same as
     the length of its ‘items()’, which is the same as the length of the
     wrapped header list.  In fact, the ‘items()’ method just returns a
     copy of the wrapped header list.

     Calling ‘bytes()’ on a *note Headers: 794. object returns a
     formatted bytestring suitable for transmission as HTTP response
     headers.  Each header is placed on a line with its value, separated
     by a colon and a space.  Each line is terminated by a carriage
     return and line feed, and the bytestring is terminated with a blank
     line.

     In addition to their mapping interface and formatting features,
     *note Headers: 794. objects also have the following methods for
     querying and adding multi-valued headers, and for adding headers
     with MIME parameters:

      -- 成員函式: get_all (name)

          Return a list of all the values for the named header.

          The returned list will be sorted in the order they appeared in
          the original header list or were added to this instance, and
          may contain duplicates.  Any fields deleted and re-inserted
          are always appended to the header list.  If no fields exist
          with the given name, returns an empty list.

      -- 成員函式: add_header (name, value, **_params)

          Add a (possibly multi-valued) header, with optional MIME
          parameters specified via keyword arguments.

          `name' is the header field to add.  Keyword arguments can be
          used to set MIME parameters for the header field.  Each
          parameter must be a string or ‘None’.  Underscores in
          parameter names are converted to dashes, since dashes are
          illegal in Python identifiers, but many MIME parameter names
          include dashes.  If the parameter value is a string, it is
          added to the header value parameters in the form
          ‘name="value"’.  If it is ‘None’, only the parameter name is
          added.  (This is used for MIME parameters without a value.)
          Example usage:

               h.add_header('content-disposition', 'attachment', filename='bud.gif')

          The above will add a header that looks like this:

               Content-Disposition: attachment; filename="bud.gif"

     3.5 版更變: `headers' parameter is optional.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3333


File: python.info,  Node: wsgiref simple_server -- a simple WSGI HTTP server,  Next: wsgiref validate --- WSGI conformance checker,  Prev: wsgiref headers -- WSGI response header tools,  Up: wsgiref --- WSGI Utilities and Reference Implementation

5.21.4.3 ‘wsgiref.simple_server’ – a simple WSGI HTTP server
............................................................

This module implements a simple HTTP server (based on *note http.server:
97.) that serves WSGI applications.  Each server instance serves a
single WSGI application on a given host and port.  If you want to serve
multiple applications on a single host and port, you should create a
WSGI application that parses ‘PATH_INFO’ to select which application to
invoke for each request.  (E.g., using the ‘shift_path_info()’ function
from *note wsgiref.util: 131.)

 -- 函式: wsgiref.simple_server.make_server (host, port, app,
          server_class=WSGIServer, handler_class=WSGIRequestHandler)

     Create a new WSGI server listening on `host' and `port', accepting
     connections for `app'.  The return value is an instance of the
     supplied `server_class', and will process requests using the
     specified `handler_class'.  `app' must be a WSGI application
     object, as defined by PEP 3333(1).

     Example usage:

          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)

     This function is a small but complete WSGI application that returns
     a text page containing the message "Hello world!"  and a list of
     the key/value pairs provided in the `environ' parameter.  It’s
     useful for verifying that a WSGI server (such as *note
     wsgiref.simple_server: 130.) is able to run a simple WSGI
     application correctly.

 -- 類別: wsgiref.simple_server.WSGIServer (server_address,
          RequestHandlerClass)

     Create a *note WSGIServer: 2c0b. instance.  `server_address' should
     be a ‘(host,port)’ tuple, and `RequestHandlerClass' should be the
     subclass of *note http.server.BaseHTTPRequestHandler: a13. that
     will be used to process requests.

     You do not normally need to call this constructor, as the *note
     make_server(): 2c09. function can handle all the details for you.

     *note WSGIServer: 2c0b. is a subclass of *note
     http.server.HTTPServer: 2c0c, so all of its methods (such as
     ‘serve_forever()’ and ‘handle_request()’) are available.  *note
     WSGIServer: 2c0b. also provides these WSGI-specific methods:

      -- 成員函式: set_app (application)

          Sets the callable `application' as the WSGI application that
          will receive requests.

      -- 成員函式: get_app ()

          Returns the currently-set application callable.

     Normally, however, you do not need to use these additional methods,
     as *note set_app(): 2c0d. is normally called by *note
     make_server(): 2c09, and the *note get_app(): 2c0e. exists mainly
     for the benefit of request handler instances.

 -- 類別: wsgiref.simple_server.WSGIRequestHandler (request,
          client_address, server)

     Create an HTTP handler for the given `request' (i.e.  a socket),
     `client_address' (a ‘(host,port)’ tuple), and `server' (*note
     WSGIServer: 2c0b. instance).

     You do not need to create instances of this class directly; they
     are automatically created as needed by *note WSGIServer: 2c0b.
     objects.  You can, however, subclass this class and supply it as a
     `handler_class' to the *note make_server(): 2c09. function.  Some
     possibly relevant methods for overriding in subclasses:

      -- 成員函式: get_environ ()

          Returns a dictionary containing the WSGI environment for a
          request.  The default implementation copies the contents of
          the *note WSGIServer: 2c0b. object’s ‘base_environ’ dictionary
          attribute and then adds various headers derived from the HTTP
          request.  Each call to this method should return a new
          dictionary containing all of the relevant CGI environment
          variables as specified in PEP 3333(2).

      -- 成員函式: get_stderr ()

          Return the object that should be used as the ‘wsgi.errors’
          stream.  The default implementation just returns ‘sys.stderr’.

      -- 成員函式: handle ()

          Process the HTTP request.  The default implementation creates
          a handler instance using a *note wsgiref.handlers: 12e. class
          to implement the actual WSGI application interface.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3333

   (2) https://www.python.org/dev/peps/pep-3333


File: python.info,  Node: wsgiref validate --- WSGI conformance checker,  Next: wsgiref handlers -- server/gateway base classes,  Prev: wsgiref simple_server -- a simple WSGI HTTP server,  Up: wsgiref --- WSGI Utilities and Reference Implementation

5.21.4.4 ‘wsgiref.validate’ — WSGI conformance checker
......................................................

When creating new WSGI application objects, frameworks, servers, or
middleware, it can be useful to validate the new code’s conformance
using *note wsgiref.validate: 132.  This module provides a function that
creates WSGI application objects that validate communications between a
WSGI server or gateway and a WSGI application object, to check both
sides for protocol conformance.

Note that this utility does not guarantee complete PEP 3333(1)
compliance; an absence of errors from this module does not necessarily
mean that errors do not exist.  However, if this module does produce an
error, then it is virtually certain that either the server or
application is not 100% compliant.

This module is based on the ‘paste.lint’ module from Ian Bicking’s
"Python Paste" library.

 -- 函式: wsgiref.validate.validator (application)

     Wrap `application' and return a new WSGI application object.  The
     returned application will forward all requests to the original
     `application', and will check that both the `application' and the
     server invoking it are conforming to the WSGI specification and to
     RFC 2616(2).

     Any detected nonconformance results in an *note AssertionError:
     1033. being raised; note, however, that how these errors are
     handled is server-dependent.  For example, *note
     wsgiref.simple_server: 130. and other servers based on *note
     wsgiref.handlers: 12e. (that don’t override the error handling
     methods to do something else) will simply output a message that an
     error has occurred, and dump the traceback to ‘sys.stderr’ or some
     other error stream.

     This wrapper may also generate output using the *note warnings:
     127. module to indicate behaviors that are questionable but which
     may not actually be prohibited by PEP 3333(3).  Unless they are
     suppressed using Python command-line options or the *note warnings:
     127. API, any such warnings will be written to ‘sys.stderr’ (`not'
     ‘wsgi.errors’, unless they happen to be the same object).

     Example usage:

          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://www.python.org/dev/peps/pep-3333

   (2) https://tools.ietf.org/html/rfc2616.html

   (3) https://www.python.org/dev/peps/pep-3333


File: python.info,  Node: wsgiref handlers -- server/gateway base classes,  Next: Examples<20>,  Prev: wsgiref validate --- WSGI conformance checker,  Up: wsgiref --- WSGI Utilities and Reference Implementation

5.21.4.5 ‘wsgiref.handlers’ – server/gateway base classes
.........................................................

This module provides base handler classes for implementing WSGI servers
and gateways.  These base classes handle most of the work of
communicating with a WSGI application, as long as they are given a
CGI-like environment, along with input, output, and error streams.

 -- 類別: wsgiref.handlers.CGIHandler

     CGI-based invocation via ‘sys.stdin’, ‘sys.stdout’, ‘sys.stderr’
     and ‘os.environ’.  This is useful when you have a WSGI application
     and want to run it as a CGI script.  Simply invoke
     ‘CGIHandler().run(app)’, where ‘app’ is the WSGI application object
     you wish to invoke.

     This class is a subclass of *note BaseCGIHandler: 2c17. that sets
     ‘wsgi.run_once’ to true, ‘wsgi.multithread’ to false, and
     ‘wsgi.multiprocess’ to true, and always uses *note sys: fe. and
     *note os: c5. to obtain the necessary CGI streams and environment.

 -- 類別: wsgiref.handlers.IISCGIHandler

     A specialized alternative to *note CGIHandler: 2c16, for use when
     deploying on Microsoft’s IIS web server, without having set the
     config allowPathInfo option (IIS>=7) or metabase
     allowPathInfoForScriptMappings (IIS<7).

     By default, IIS gives a ‘PATH_INFO’ that duplicates the
     ‘SCRIPT_NAME’ at the front, causing problems for WSGI applications
     that wish to implement routing.  This handler strips any such
     duplicated path.

     IIS can be configured to pass the correct ‘PATH_INFO’, but this
     causes another bug where ‘PATH_TRANSLATED’ is wrong.  Luckily this
     variable is rarely used and is not guaranteed by WSGI. On IIS<7,
     though, the setting can only be made on a vhost level, affecting
     all other script mappings, many of which break when exposed to the
     ‘PATH_TRANSLATED’ bug.  For this reason IIS<7 is almost never
     deployed with the fix (Even IIS7 rarely uses it because there is
     still no UI for it.).

     There is no way for CGI code to tell whether the option was set, so
     a separate handler class is provided.  It is used in the same way
     as *note CGIHandler: 2c16, i.e., by calling
     ‘IISCGIHandler().run(app)’, where ‘app’ is the WSGI application
     object you wish to invoke.

     3.2 版新加入.

 -- 類別: wsgiref.handlers.BaseCGIHandler (stdin, stdout, stderr,
          environ, multithread=True, multiprocess=False)

     Similar to *note CGIHandler: 2c16, but instead of using the *note
     sys: fe. and *note os: c5. modules, the CGI environment and I/O
     streams are specified explicitly.  The `multithread' and
     `multiprocess' values are used to set the ‘wsgi.multithread’ and
     ‘wsgi.multiprocess’ flags for any applications run by the handler
     instance.

     This class is a subclass of *note SimpleHandler: 2c19. intended for
     use with software other than HTTP "origin servers".  If you are
     writing a gateway protocol implementation (such as CGI, FastCGI,
     SCGI, etc.)  that uses a ‘Status:’ header to send an HTTP status,
     you probably want to subclass this instead of *note SimpleHandler:
     2c19.

 -- 類別: wsgiref.handlers.SimpleHandler (stdin, stdout, stderr,
          environ, multithread=True, multiprocess=False)

     Similar to *note BaseCGIHandler: 2c17, but designed for use with
     HTTP origin servers.  If you are writing an HTTP server
     implementation, you will probably want to subclass this instead of
     *note BaseCGIHandler: 2c17.

     This class is a subclass of *note BaseHandler: fd1.  It overrides
     the *note __init__(): d63, ‘get_stdin()’, ‘get_stderr()’,
     ‘add_cgi_vars()’, ‘_write()’, and ‘_flush()’ methods to support
     explicitly setting the environment and streams via the constructor.
     The supplied environment and streams are stored in the ‘stdin’,
     ‘stdout’, ‘stderr’, and ‘environ’ attributes.

     The *note write(): 58e. method of `stdout' should write each chunk
     in full, like *note io.BufferedIOBase: 58d.

 -- 類別: wsgiref.handlers.BaseHandler

     This is an abstract base class for running WSGI applications.  Each
     instance will handle a single HTTP request, although in principle
     you could create a subclass that was reusable for multiple
     requests.

     *note BaseHandler: fd1. instances have only one method intended for
     external use:

      -- 成員函式: run (app)

          Run the specified WSGI application, `app'.

     All of the other *note BaseHandler: fd1. methods are invoked by
     this method in the process of running the application, and thus
     exist primarily to allow customizing the process.

     The following methods MUST be overridden in a subclass:

      -- 成員函式: _write (data)

          Buffer the bytes `data' for transmission to the client.  It’s
          okay if this method actually transmits the data; *note
          BaseHandler: fd1. just separates write and flush operations
          for greater efficiency when the underlying system actually has
          such a distinction.

      -- 成員函式: _flush ()

          Force buffered data to be transmitted to the client.  It’s
          okay if this method is a no-op (i.e., if *note _write(): 2c1b.
          actually sends the data).

      -- 成員函式: get_stdin ()

          Return an input stream object suitable for use as the
          ‘wsgi.input’ of the request currently being processed.

      -- 成員函式: get_stderr ()

          Return an output stream object suitable for use as the
          ‘wsgi.errors’ of the request currently being processed.

      -- 成員函式: add_cgi_vars ()

          Insert CGI variables for the current request into the
          ‘environ’ attribute.

     Here are some other methods and attributes you may wish to
     override.  This list is only a summary, however, and does not
     include every method that can be overridden.  You should consult
     the docstrings and source code for additional information before
     attempting to create a customized *note BaseHandler: fd1. subclass.

     Attributes and methods for customizing the WSGI environment:

      -- 屬性: wsgi_multithread

          The value to be used for the ‘wsgi.multithread’ environment
          variable.  It defaults to true in *note BaseHandler: fd1, but
          may have a different default (or be set by the constructor) in
          the other subclasses.

      -- 屬性: wsgi_multiprocess

          The value to be used for the ‘wsgi.multiprocess’ environment
          variable.  It defaults to true in *note BaseHandler: fd1, but
          may have a different default (or be set by the constructor) in
          the other subclasses.

      -- 屬性: wsgi_run_once

          The value to be used for the ‘wsgi.run_once’ environment
          variable.  It defaults to false in *note BaseHandler: fd1, but
          *note CGIHandler: 2c16. sets it to true by default.

      -- 屬性: os_environ

          The default environment variables to be included in every
          request’s WSGI environment.  By default, this is a copy of
          ‘os.environ’ at the time that *note wsgiref.handlers: 12e. was
          imported, but subclasses can either create their own at the
          class or instance level.  Note that the dictionary should be
          considered read-only, since the default value is shared
          between multiple classes and instances.

      -- 屬性: server_software

          If the *note origin_server: 2c25. attribute is set, this
          attribute’s value is used to set the default ‘SERVER_SOFTWARE’
          WSGI environment variable, and also to set a default ‘Server:’
          header in HTTP responses.  It is ignored for handlers (such as
          *note BaseCGIHandler: 2c17. and *note CGIHandler: 2c16.) that
          are not HTTP origin servers.

          3.3 版更變: The term "Python" is replaced with implementation
          specific term like "CPython", "Jython" etc.

      -- 成員函式: get_scheme ()

          Return the URL scheme being used for the current request.  The
          default implementation uses the ‘guess_scheme()’ function from
          *note wsgiref.util: 131. to guess whether the scheme should be
          "http" or "https", based on the current request’s ‘environ’
          variables.

      -- 成員函式: setup_environ ()

          Set the ‘environ’ attribute to a fully-populated WSGI
          environment.  The default implementation uses all of the above
          methods and attributes, plus the *note get_stdin(): 2c1d,
          *note get_stderr(): 2c1e, and *note add_cgi_vars(): 2c1f.
          methods and the *note wsgi_file_wrapper: 2c28. attribute.  It
          also inserts a ‘SERVER_SOFTWARE’ key if not present, as long
          as the *note origin_server: 2c25. attribute is a true value
          and the *note server_software: 2c24. attribute is set.

     Methods and attributes for customizing exception handling:

      -- 成員函式: log_exception (exc_info)

          Log the `exc_info' tuple in the server log.  `exc_info' is a
          ‘(type, value, traceback)’ tuple.  The default implementation
          simply writes the traceback to the request’s ‘wsgi.errors’
          stream and flushes it.  Subclasses can override this method to
          change the format or retarget the output, mail the traceback
          to an administrator, or whatever other action may be deemed
          suitable.

      -- 屬性: traceback_limit

          The maximum number of frames to include in tracebacks output
          by the default *note log_exception(): 2c29. method.  If
          ‘None’, all frames are included.

      -- 成員函式: error_output (environ, start_response)

          This method is a WSGI application to generate an error page
          for the user.  It is only invoked if an error occurs before
          headers are sent to the client.

          This method can access the current error information using
          ‘sys.exc_info()’, and should pass that information to
          `start_response' when calling it (as described in the "Error
          Handling" section of PEP 3333(1)).

          The default implementation just uses the *note error_status:
          2c2c, *note error_headers: 2c2d, and *note error_body: 2c2e.
          attributes to generate an output page.  Subclasses can
          override this to produce more dynamic error output.

          Note, however, that it’s not recommended from a security
          perspective to spit out diagnostics to any old user; ideally,
          you should have to do something special to enable diagnostic
          output, which is why the default implementation doesn’t
          include any.

      -- 屬性: error_status

          The HTTP status used for error responses.  This should be a
          status string as defined in PEP 3333(2); it defaults to a 500
          code and message.

      -- 屬性: error_headers

          The HTTP headers used for error responses.  This should be a
          list of WSGI response headers (‘(name, value)’ tuples), as
          described in PEP 3333(3).  The default list just sets the
          content type to ‘text/plain’.

      -- 屬性: error_body

          The error response body.  This should be an HTTP response body
          bytestring.  It defaults to the plain text, "A server error
          occurred.  Please contact the administrator."

     Methods and attributes for PEP 3333(4)’s "Optional
     Platform-Specific File Handling" feature:

      -- 屬性: wsgi_file_wrapper

          A ‘wsgi.file_wrapper’ factory, or ‘None’.  The default value
          of this attribute is the *note wsgiref.util.FileWrapper: 27f.
          class.

      -- 成員函式: sendfile ()

          Override to implement platform-specific file transmission.
          This method is called only if the application’s return value
          is an instance of the class specified by the *note
          wsgi_file_wrapper: 2c28. attribute.  It should return a true
          value if it was able to successfully transmit the file, so
          that the default transmission code will not be executed.  The
          default implementation of this method just returns a false
          value.

     Miscellaneous methods and attributes:

      -- 屬性: origin_server

          This attribute should be set to a true value if the handler’s
          *note _write(): 2c1b. and *note _flush(): 2c1c. are being used
          to communicate directly to the client, rather than via a
          CGI-like gateway protocol that wants the HTTP status in a
          special ‘Status:’ header.

          This attribute’s default value is true in *note BaseHandler:
          fd1, but false in *note BaseCGIHandler: 2c17. and *note
          CGIHandler: 2c16.

      -- 屬性: http_version

          If *note origin_server: 2c25. is true, this string attribute
          is used to set the HTTP version of the response set to the
          client.  It defaults to ‘"1.0"’.

 -- 函式: wsgiref.handlers.read_environ ()

     Transcode CGI variables from ‘os.environ’ to PEP 3333(5) "bytes in
     unicode" strings, returning a new dictionary.  This function is
     used by *note CGIHandler: 2c16. and *note IISCGIHandler: 2c18. in
     place of directly using ‘os.environ’, which is not necessarily
     WSGI-compliant on all platforms and web servers using Python 3 –
     specifically, ones where the OS’s actual environment is Unicode
     (i.e.  Windows), or ones where the environment is bytes, but the
     system encoding used by Python to decode it is anything other than
     ISO-8859-1 (e.g.  Unix systems using UTF-8).

     If you are implementing a CGI-based handler of your own, you
     probably want to use this routine instead of just copying values
     out of ‘os.environ’ directly.

     3.2 版新加入.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3333

   (2) https://www.python.org/dev/peps/pep-3333

   (3) https://www.python.org/dev/peps/pep-3333

   (4) https://www.python.org/dev/peps/pep-3333

   (5) https://www.python.org/dev/peps/pep-3333


File: python.info,  Node: Examples<20>,  Prev: wsgiref handlers -- server/gateway base classes,  Up: wsgiref --- WSGI Utilities and Reference Implementation

5.21.4.6 Examples
.................

This is a working "Hello World" WSGI application:

     from wsgiref.simple_server import make_server

     # 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.
     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()

Example of a WSGI application serving the current directory, accept
optional directory and port number (default: 8000) on the command line:

     #!/usr/bin/env python3
     '''
     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. Used for the make serve target in Doc.
     '''
     import sys
     import os
     import mimetypes
     from wsgiref import simple_server, util

     def app(environ, respond):

         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')
         type = mimetypes.guess_type(fn)[0]

         if os.path.exists(fn):
             respond('200 OK', [('Content-Type', type)])
             return util.FileWrapper(open(fn, "rb"))
         else:
             respond('404 Not Found', [('Content-Type', 'text/plain')])
             return [b'not found']

     if __name__ == '__main__':
         path = sys.argv[1] if len(sys.argv) > 1 else os.getcwd()
         port = int(sys.argv[2]) if len(sys.argv) > 2 else 8000
         httpd = simple_server.make_server('', port, app)
         print("Serving {} on port {}, control-C to stop".format(path, port))
         try:
             httpd.serve_forever()
         except KeyboardInterrupt:
             print("Shutting down.")
             httpd.server_close()


File: python.info,  Node: urllib --- URL handling modules,  Next: urllib request --- Extensible library for opening URLs,  Prev: wsgiref --- WSGI Utilities and Reference Implementation,  Up: Internet Protocols and Support

5.21.5 ‘urllib’ — URL handling modules
--------------------------------------

`Source code:' Lib/urllib/(1)

__________________________________________________________________

‘urllib’ is a package that collects several modules for working with
URLs:

   * *note urllib.request: 121. for opening and reading URLs

   * *note urllib.error: 11f. containing the exceptions raised by *note
     urllib.request: 121.

   * *note urllib.parse: 120. for parsing URLs

   * *note urllib.robotparser: 123. for parsing ‘robots.txt’ files

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/urllib/


File: python.info,  Node: urllib request --- Extensible library for opening URLs,  Next: urllib response --- Response classes used by urllib,  Prev: urllib --- URL handling modules,  Up: Internet Protocols and Support

5.21.6 ‘urllib.request’ — Extensible library for opening URLs
-------------------------------------------------------------

`Source code:' Lib/urllib/request.py(1)

__________________________________________________________________

The *note urllib.request: 121. module defines functions and classes
which help in opening URLs (mostly HTTP) in a complex world — basic and
digest authentication, redirections, cookies and more.

也參考
......

The Requests package(2) is recommended for a higher-level HTTP client
interface.

The *note urllib.request: 121. module defines the following functions:

 -- 函式: urllib.request.urlopen (url, data=None[, timeout], *,
          cafile=None, capath=None, cadefault=False, context=None)

     Open the URL `url', which can be either a string or a *note
     Request: 8fb. object.

     `data' must be an object specifying additional data to be sent to
     the server, or ‘None’ if no such data is needed.  See *note
     Request: 8fb. for details.

     urllib.request module uses HTTP/1.1 and includes ‘Connection:close’
     header in its HTTP requests.

     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).  This actually
     only works for HTTP, HTTPS and FTP connections.

     If `context' is specified, it must be a *note ssl.SSLContext: 3e9.
     instance describing the various SSL options.  See *note
     HTTPSConnection: 398. for more details.

     The optional `cafile' and `capath' parameters specify a set of
     trusted CA certificates for HTTPS requests.  `cafile' should point
     to a single file containing a bundle of CA certificates, whereas
     `capath' should point to a directory of hashed certificate files.
     More information can be found in *note
     ssl.SSLContext.load_verify_locations(): 7f0.

     The `cadefault' parameter is ignored.

     This function always returns an object which can work as a *note
     context manager: 56d. and has methods such as

        * ‘geturl()’ — return the URL of the resource retrieved,
          commonly used to determine if a redirect was followed

        * ‘info()’ — return the meta-information of the page, such as
          headers, in the form of an *note email.message_from_string():
          2821. instance (see Quick Reference to HTTP Headers(3))

        * ‘getcode()’ – return the HTTP status code of the response.

     For HTTP and HTTPS URLs, this function returns a *note
     http.client.HTTPResponse: a16. object slightly modified.  In
     addition to the three new methods above, the msg attribute contains
     the same information as the *note reason: 2c36. attribute — the
     reason phrase returned by server — instead of the response headers
     as it is specified in the documentation for *note HTTPResponse:
     a16.

     For FTP, file, and data URLs and requests explicitly handled by
     legacy *note URLopener: 2c37. and *note FancyURLopener: 2c38.
     classes, this function returns a ‘urllib.response.addinfourl’
     object.

     Raises *note URLError: 2c39. on protocol errors.

     Note that ‘None’ may be returned if no handler handles the request
     (though the default installed global *note OpenerDirector: 2c3a.
     uses *note UnknownHandler: 2c3b. to ensure this never happens).

     In addition, if proxy settings are detected (for example, when a
     ‘*_proxy’ environment variable like ‘http_proxy’ is set), *note
     ProxyHandler: f80. is default installed and makes sure the requests
     are handled through the proxy.

     The legacy ‘urllib.urlopen’ function from Python 2.6 and earlier
     has been discontinued; *note urllib.request.urlopen(): 791.
     corresponds to the old ‘urllib2.urlopen’.  Proxy handling, which
     was done by passing a dictionary parameter to ‘urllib.urlopen’, can
     be obtained by using *note ProxyHandler: f80. objects.

     The default opener raises an *note auditing event: e96.
     ‘urllib.Request’ with arguments ‘fullurl’, ‘data’, ‘headers’,
     ‘method’ taken from the request object.

     3.2 版更變: `cafile' and `capath' were added.

     3.2 版更變: HTTPS virtual hosts are now supported if possible (that
     is, if *note ssl.HAS_SNI: 26df. is true).

     3.2 版新加入: `data' can be an iterable object.

     3.3 版更變: `cadefault' was added.

     3.4.3 版更變: `context' was added.

     3.6 版後已棄用: `cafile', `capath' and `cadefault' are deprecated
     in favor of `context'.  Please use *note
     ssl.SSLContext.load_cert_chain(): a96. instead, or let *note
     ssl.create_default_context(): 8c6. select the system’s trusted CA
     certificates for you.

 -- 函式: urllib.request.install_opener (opener)

     Install an *note OpenerDirector: 2c3a. instance as the default
     global opener.  Installing an opener is only necessary if you want
     urlopen to use that opener; otherwise, simply call *note
     OpenerDirector.open(): 8ff. instead of *note urlopen(): 791.  The
     code does not check for a real *note OpenerDirector: 2c3a, and any
     class with the appropriate interface will work.

 -- 函式: urllib.request.build_opener ([handler, ...])

     Return an *note OpenerDirector: 2c3a. instance, which chains the
     handlers in the order given.  `handler's can be either instances of
     *note BaseHandler: 2c3e, or subclasses of *note BaseHandler: 2c3e.
     (in which case it must be possible to call the constructor without
     any parameters).  Instances of the following classes will be in
     front of the `handler's, unless the `handler's contain them,
     instances of them or subclasses of them: *note ProxyHandler: f80.
     (if proxy settings are detected), *note UnknownHandler: 2c3b, *note
     HTTPHandler: 2c3f, *note HTTPDefaultErrorHandler: 2c40, *note
     HTTPRedirectHandler: 2c41, *note FTPHandler: 2c42, *note
     FileHandler: 2c43, *note HTTPErrorProcessor: 2c44.

     If the Python installation has SSL support (i.e., if the *note ssl:
     f4. module can be imported), *note HTTPSHandler: bad. will also be
     added.

     A *note BaseHandler: 2c3e. subclass may also change its
     ‘handler_order’ attribute to modify its position in the handlers
     list.

 -- 函式: urllib.request.pathname2url (path)

     Convert the pathname `path' from the local syntax for a path to the
     form used in the path component of a URL. This does not produce a
     complete URL. The return value will already be quoted using the
     *note quote(): 412. function.

 -- 函式: urllib.request.url2pathname (path)

     Convert the path component `path' from a percent-encoded URL to the
     local syntax for a path.  This does not accept a complete URL. This
     function uses *note unquote(): edc. to decode `path'.

 -- 函式: urllib.request.getproxies ()

     This helper function returns a dictionary of scheme to proxy server
     URL mappings.  It scans the environment for variables named
     ‘<scheme>_proxy’, in a case insensitive approach, for all operating
     systems first, and when it cannot find it, looks for proxy
     information from Mac OSX System Configuration for Mac OS X and
     Windows Systems Registry for Windows.  If both lowercase and
     uppercase environment variables exist (and disagree), lowercase is
     preferred.

          備註: If the environment variable ‘REQUEST_METHOD’ is set,
          which usually indicates your script is running in a CGI
          environment, the environment variable ‘HTTP_PROXY’ (uppercase
          ‘_PROXY’) will be ignored.  This is because that variable can
          be injected by a client using the "Proxy:" HTTP header.  If
          you need to use an HTTP proxy in a CGI environment, either use
          ‘ProxyHandler’ explicitly, or make sure the variable name is
          in lowercase (or at least the ‘_proxy’ suffix).

The following classes are provided:

 -- 類別: urllib.request.Request (url, data=None, headers={},
          origin_req_host=None, unverifiable=False, method=None)

     This class is an abstraction of a URL request.

     `url' should be a string containing a valid URL.

     `data' must be an object specifying additional data to send to the
     server, or ‘None’ if no such data is needed.  Currently HTTP
     requests are the only ones that use `data'.  The supported object
     types include bytes, file-like objects, and iterables of bytes-like
     objects.  If no ‘Content-Length’ nor ‘Transfer-Encoding’ header
     field has been provided, *note HTTPHandler: 2c3f. will set these
     headers according to the type of `data'.  ‘Content-Length’ will be
     used to send bytes objects, while ‘Transfer-Encoding: chunked’ as
     specified in RFC 7230(4), Section 3.3.1 will be used to send files
     and other iterables.

     For an HTTP POST request method, `data' should be a buffer in the
     standard ‘application/x-www-form-urlencoded’ format.  The *note
     urllib.parse.urlencode(): 790. function takes a mapping or sequence
     of 2-tuples and returns an ASCII string in this format.  It should
     be encoded to bytes before being used as the `data' parameter.

     `headers' should be a dictionary, and will be treated as if *note
     add_header(): 2c48. was called with each key and value as
     arguments.  This is often used to "spoof" the ‘User-Agent’ header
     value, which is used by a browser to identify itself – some HTTP
     servers only allow requests coming from common browsers as opposed
     to scripts.  For example, Mozilla Firefox may identify itself as
     ‘"Mozilla/5.0 (X11; U; Linux i686) Gecko/20071127
     Firefox/2.0.0.11"’, while *note urllib: 11e.’s default user agent
     string is ‘"Python-urllib/2.6"’ (on Python 2.6).

     An appropriate ‘Content-Type’ header should be included if the
     `data' argument is present.  If this header has not been provided
     and `data' is not None, ‘Content-Type:
     application/x-www-form-urlencoded’ will be added as a default.

     The next two arguments are only of interest for correct handling of
     third-party HTTP cookies:

     `origin_req_host' should be the request-host of the origin
     transaction, as defined by RFC 2965(5).  It defaults to
     ‘http.cookiejar.request_host(self)’.  This is the host name or IP
     address of the original request that was initiated by the user.
     For example, if the request is for an image in an HTML document,
     this should be the request-host of the request for the page
     containing the image.

     `unverifiable' should indicate whether the request is unverifiable,
     as defined by RFC 2965(6).  It defaults to ‘False’.  An
     unverifiable request is one whose URL the user did not have the
     option to approve.  For example, if the request is for an image in
     an HTML document, and the user had no option to approve the
     automatic fetching of the image, this should be true.

     `method' should be a string that indicates the HTTP request method
     that will be used (e.g.  ‘'HEAD'’).  If provided, its value is
     stored in the *note method: 8fc. attribute and is used by *note
     get_method(): ac6.  The default is ‘'GET'’ if `data' is ‘None’ or
     ‘'POST'’ otherwise.  Subclasses may indicate a different default
     method by setting the *note method: 8fc. attribute in the class
     itself.

          備註: The request will not work as expected if the data object
          is unable to deliver its content more than once (e.g.  a file
          or an iterable that can produce the content only once) and the
          request is retried for HTTP redirects or authentication.  The
          `data' is sent to the HTTP server right away after the
          headers.  There is no support for a 100-continue expectation
          in the library.

     3.3 版更變: *note Request.method: 8fc. argument is added to the
     Request class.

     3.4 版更變: Default *note Request.method: 8fc. may be indicated at
     the class level.

     3.6 版更變: Do not raise an error if the ‘Content-Length’ has not
     been provided and `data' is neither ‘None’ nor a bytes object.
     Fall back to use chunked transfer encoding instead.

 -- 類別: urllib.request.OpenerDirector

     The *note OpenerDirector: 2c3a. class opens URLs via *note
     BaseHandler: 2c3e.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: 901. 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 Mac OS X
     environment proxy information is retrieved from the OS X 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(): 2c47.

 -- 類別: 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: 2c4b. 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: 2c4a.;
     refer to section *note HTTPPasswordMgr Objects: 2c4c. for
     information on the interface that must be supported.  If
     `passwd_mgr' also provides ‘is_authenticated’ and
     ‘update_authenticated’ methods (see *note
     HTTPPasswordMgrWithPriorAuth Objects: 2c4d.), 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 版新加入: Added ‘is_authenticated’ support.

 -- 類別: 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: 2c4a.; refer to section *note HTTPPasswordMgr
     Objects: 2c4c. for information on the interface that must be
     supported.  HTTPBasicAuthHandler will raise a *note ValueError:
     1fc. 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:
     2c4a.; refer to section *note HTTPPasswordMgr Objects: 2c4c. 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: 2c4a.;
     refer to section *note HTTPPasswordMgr Objects: 2c4c. 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: 2c4a.; refer to section *note HTTPPasswordMgr
     Objects: 2c4c. 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: 1fc.
     when presented with an authentication scheme other than Digest or
     Basic.

     3.3 版更變: Raise *note ValueError: 1fc. 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:
     2c4a.; refer to section *note HTTPPasswordMgr Objects: 2c4c. 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: 398.

     3.2 版更變: `context' and `check_hostname' were added.

 -- 類別: 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 Objects::
* BaseHandler Objects::
* HTTPRedirectHandler Objects::
* HTTPCookieProcessor Objects::
* ProxyHandler Objects::
* HTTPPasswordMgr Objects::
* HTTPPasswordMgrWithPriorAuth Objects::
* AbstractBasicAuthHandler Objects::
* HTTPBasicAuthHandler Objects::
* ProxyBasicAuthHandler Objects::
* AbstractDigestAuthHandler Objects::
* HTTPDigestAuthHandler Objects::
* ProxyDigestAuthHandler Objects::
* HTTPHandler Objects::
* HTTPSHandler Objects::
* FileHandler Objects::
* DataHandler Objects::
* FTPHandler Objects::
* CacheFTPHandler Objects::
* UnknownHandler Objects::
* HTTPErrorProcessor Objects::
* Examples: Examples<21>.
* Legacy interface::
* urllib.request Restrictions: urllib request Restrictions.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/urllib/request.py

   (2) https://requests.readthedocs.io/en/master/

   (3) http://jkorpela.fi/http.html

   (4) https://tools.ietf.org/html/rfc7230.html

   (5) https://tools.ietf.org/html/rfc2965.html

   (6) https://tools.ietf.org/html/rfc2965.html


File: python.info,  Node: Request Objects,  Next: OpenerDirector Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.1 Request Objects
........................

The following methods describe *note Request: 8fb.’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: 8fd. 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: 8fb. 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: 8fe. 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: 158, which means that *note get_method(): ac6. 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():
     ac6.) either by providing a default value by setting it at the
     class level in a *note Request: 8fb. subclass, or by passing a
     value in to the *note Request: 8fb. 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: 8fc. is not ‘None’, return its value, otherwise
     return ‘'GET'’ if *note Request.data: 8fe. 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: 8fc.

 -- 成員函式: 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.

 -- 成員函式: 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: 8fd.

 -- 成員函式: 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://tools.ietf.org/html/rfc2965.html


File: python.info,  Node: OpenerDirector Objects,  Next: BaseHandler Objects,  Prev: Request Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.2 OpenerDirector Objects
...............................

*note OpenerDirector: 2c3a. instances have the following methods:

 -- 成員函式: OpenerDirector.add_handler (handler)

     `handler' should be an instance of *note BaseHandler: 2c3e.  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.

          See *note BaseHandler.<protocol>_open(): 2c63. for more
          information.

        * ‘http_error_<type>()’ — signal that the handler knows how to
          handle HTTP errors with HTTP error code `type'.

          See *note BaseHandler.http_error_<nnn>(): 2c64. for more
          information.

        * ‘<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.

          See *note BaseHandler.<protocol>_request(): 2c65. for more
          information.

        * ‘<protocol>_response()’ — signal that the handler knows how to
          post-process `protocol' responses.

          See *note BaseHandler.<protocol>_response(): 2c66. for more
          information.

 -- 成員函式: 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(): 791.
     (which simply calls the *note open(): 4f5. method on the currently
     installed global *note OpenerDirector: 2c3a.).  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(): 791.

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: 158. value (ie.  a response), or raises an
     exception (usually *note URLError: 2c39.).  Exceptions are allowed
     to propagate.

     In fact, the above algorithm is first tried for methods named
     ‘default_open()’.  If all such methods return *note None: 158, the
     algorithm is repeated for methods named like ‘<protocol>_open()’.
     If all such methods return *note None: 158, the algorithm is
     repeated for methods named ‘unknown_open()’.

     Note that the implementation of these methods may involve calls of
     the parent *note OpenerDirector: 2c3a. instance’s *note open():
     8ff. and *note error(): 2c67. 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 Objects,  Next: HTTPRedirectHandler Objects,  Prev: OpenerDirector Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.3 BaseHandler Objects
............................

*note BaseHandler: 2c3e. 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: 2c3e.

     備註: 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: 2c3a, 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: 2c3e, but
     subclasses should define it if they want to catch all URLs.

     This method, if implemented, will be called by the parent *note
     OpenerDirector: 2c3a.  It should return a file-like object as
     described in the return value of the *note open(): 4f5. of *note
     OpenerDirector: 2c3a, or ‘None’.  It should raise *note URLError:
     2c39, unless a truly exceptional thing happens (for example, *note
     MemoryError: ef1. should not be mapped to ‘URLError’).

     This method will be called before any protocol-specific open
     method.

 -- 成員函式: BaseHandler.<protocol>_open(req)

     This method is `not' defined in *note BaseHandler: 2c3e, 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: 2c3a.  Return values should be the same as for
     ‘default_open()’.

 -- 成員函式: BaseHandler.unknown_open (req)

     This method is `not' defined in *note BaseHandler: 2c3e, 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:
     2c6c. *note OpenerDirector: 2c3a.  Return values should be the same
     as for *note default_open(): 2c6d.

 -- 成員函式: BaseHandler.http_error_default (req, fp, code, msg, hdrs)

     This method is `not' defined in *note BaseHandler: 2c3e, 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: 2c3a. getting the error,
     and should not normally be called in other circumstances.

     `req' will be a *note Request: 8fb. 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(): 791.

 -- 成員函式: 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: 2c3e, 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 ‘http_error_default()’.

 -- 成員函式: BaseHandler.<protocol>_request(req)

     This method is `not' defined in *note BaseHandler: 2c3e, 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: 2c3a.  `req' will be a *note Request: 8fb. object.
     The return value should be a *note Request: 8fb. object.

 -- 成員函式: BaseHandler.<protocol>_response(req, response)

     This method is `not' defined in *note BaseHandler: 2c3e, 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: 2c3a.  `req' will be a *note Request: 8fb. object.
     `response' will be an object implementing the same interface as the
     return value of *note urlopen(): 791.  The return value should
     implement the same interface as the return value of *note
     urlopen(): 791.


File: python.info,  Node: HTTPRedirectHandler Objects,  Next: HTTPCookieProcessor Objects,  Prev: BaseHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.4 HTTPRedirectHandler Objects
....................................

     備註: Some HTTP redirections require action from this module’s
     client code.  If this is the case, *note HTTPError: 901. is raised.
     See RFC 2616(1) for details of the precise meanings of the various
     redirection codes.

     An ‘HTTPError’ 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: 8fb. 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: 8fb. to allow ‘http_error_30*()’ to perform the redirect
     to `newurl'.  Otherwise, raise *note HTTPError: 901. 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: 2c3a. when getting an HTTP ’moved
     permanently’ response.

 -- 成員函式: HTTPRedirectHandler.http_error_302 (req, fp, code, msg,
          hdrs)

     The same as *note http_error_301(): 2c73, but called for the
     ’found’ response.

 -- 成員函式: HTTPRedirectHandler.http_error_303 (req, fp, code, msg,
          hdrs)

     The same as *note http_error_301(): 2c73, but called for the ’see
     other’ response.

 -- 成員函式: HTTPRedirectHandler.http_error_307 (req, fp, code, msg,
          hdrs)

     The same as *note http_error_301(): 2c73, but called for the
     ’temporary redirect’ response.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2616.html

   (2) https://tools.ietf.org/html/rfc2616.html


File: python.info,  Node: HTTPCookieProcessor Objects,  Next: ProxyHandler Objects,  Prev: HTTPRedirectHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.5 HTTPCookieProcessor Objects
....................................

*note HTTPCookieProcessor: 2c49. instances have one attribute:

 -- 屬性: HTTPCookieProcessor.cookiejar

     The *note http.cookiejar.CookieJar: 2c7a. in which cookies are
     stored.


File: python.info,  Node: ProxyHandler Objects,  Next: HTTPPasswordMgr Objects,  Prev: HTTPCookieProcessor Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.6 ProxyHandler Objects
.............................

 -- 成員函式: ProxyHandler.<protocol>_open(request)

     The *note ProxyHandler: f80. 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 Objects,  Next: HTTPPasswordMgrWithPriorAuth Objects,  Prev: ProxyHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.7 HTTPPasswordMgr Objects
................................

These methods are available on *note HTTPPasswordMgr: 2c4a. and *note
HTTPPasswordMgrWithDefaultRealm: 2c4b. 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: 2c4b. objects, the realm
     ‘None’ will be searched if the given `realm' has no matching
     user/password.


File: python.info,  Node: HTTPPasswordMgrWithPriorAuth Objects,  Next: AbstractBasicAuthHandler Objects,  Prev: HTTPPasswordMgr Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.8 HTTPPasswordMgrWithPriorAuth Objects
.............................................

This password manager extends *note HTTPPasswordMgrWithDefaultRealm:
2c4b. 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(): 2c7e.  `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: 2c4b. 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 Objects,  Next: HTTPBasicAuthHandler Objects,  Prev: HTTPPasswordMgrWithPriorAuth Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.9 AbstractBasicAuthHandler Objects
.........................................

 -- 成員函式: 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: 8fb. 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 Objects,  Next: ProxyBasicAuthHandler Objects,  Prev: AbstractBasicAuthHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.10 HTTPBasicAuthHandler Objects
......................................

 -- 成員函式: HTTPBasicAuthHandler.http_error_401 (req, fp, code, msg,
          hdrs)

     Retry the request with authentication information, if available.


File: python.info,  Node: ProxyBasicAuthHandler Objects,  Next: AbstractDigestAuthHandler Objects,  Prev: HTTPBasicAuthHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.11 ProxyBasicAuthHandler Objects
.......................................

 -- 成員函式: ProxyBasicAuthHandler.http_error_407 (req, fp, code, msg,
          hdrs)

     Retry the request with authentication information, if available.


File: python.info,  Node: AbstractDigestAuthHandler Objects,  Next: HTTPDigestAuthHandler Objects,  Prev: ProxyBasicAuthHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.12 AbstractDigestAuthHandler Objects
...........................................

 -- 成員函式: 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: 8fb. object, and `headers' should be the error headers.


File: python.info,  Node: HTTPDigestAuthHandler Objects,  Next: ProxyDigestAuthHandler Objects,  Prev: AbstractDigestAuthHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.13 HTTPDigestAuthHandler Objects
.......................................

 -- 成員函式: HTTPDigestAuthHandler.http_error_401 (req, fp, code, msg,
          hdrs)

     Retry the request with authentication information, if available.


File: python.info,  Node: ProxyDigestAuthHandler Objects,  Next: HTTPHandler Objects,  Prev: HTTPDigestAuthHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.14 ProxyDigestAuthHandler Objects
........................................

 -- 成員函式: ProxyDigestAuthHandler.http_error_407 (req, fp, code, msg,
          hdrs)

     Retry the request with authentication information, if available.


File: python.info,  Node: HTTPHandler Objects,  Next: HTTPSHandler Objects,  Prev: ProxyDigestAuthHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.15 HTTPHandler Objects
.............................

 -- 成員函式: 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 Objects,  Next: FileHandler Objects,  Prev: HTTPHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.16 HTTPSHandler Objects
..............................

 -- 成員函式: 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 Objects,  Next: DataHandler Objects,  Prev: HTTPSHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.17 FileHandler Objects
.............................

 -- 成員函式: 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, an *note URLError: 2c39. is
     raised.


File: python.info,  Node: DataHandler Objects,  Next: FTPHandler Objects,  Prev: FileHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.18 DataHandler Objects
.............................

 -- 成員函式: 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 an *note ValueError: 1fc. in that case.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2397.html


File: python.info,  Node: FTPHandler Objects,  Next: CacheFTPHandler Objects,  Prev: DataHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.19 FTPHandler Objects
............................

 -- 成員函式: 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 Objects,  Next: UnknownHandler Objects,  Prev: FTPHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.20 CacheFTPHandler Objects
.................................

*note CacheFTPHandler: 2c52. objects are *note FTPHandler: 2c42. 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 Objects,  Next: HTTPErrorProcessor Objects,  Prev: CacheFTPHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.21 UnknownHandler Objects
................................

 -- 成員函式: UnknownHandler.unknown_open ()

     Raise a *note URLError: 2c39. exception.


File: python.info,  Node: HTTPErrorProcessor Objects,  Next: Examples<21>,  Prev: UnknownHandler Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.22 HTTPErrorProcessor Objects
....................................

 -- 成員函式: 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(): 2c67.  Eventually, *note
     HTTPDefaultErrorHandler: 2c40. will raise an *note HTTPError: 901.
     if no other handler handles the error.

 -- 成員函式: HTTPErrorProcessor.https_response (request, response)

     Process HTTPS error responses.

     The behavior is same as *note http_response(): 2caf.


File: python.info,  Node: Examples<21>,  Next: Legacy interface,  Prev: HTTPErrorProcessor Objects,  Up: urllib request --- Extensible library for opening URLs

5.21.6.23 Examples
..................

In addition to the examples below, more examples are given in *note
如何使用urllib套件取得網路資源: 2cb3.

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: 56d. 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: 8fb.:

     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(): 2c3d. provides many handlers by default, including
a *note ProxyHandler: f80.  By default, *note ProxyHandler: f80. 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: f80. with one that
uses programmatically-supplied proxy URLs, and adds proxy authorization
support with *note ProxyBasicAuthHandler: 2c4f.

     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)
     # This time, rather than install the OpenerDirector, we use it directly:
     opener.open('http://www.example.com/login.html')

Adding HTTP headers:

Use the `headers' argument to the *note Request: 8fb. 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: 2c3a. automatically adds a ‘User-Agent’ header to
every *note Request: 8fb.  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: 8fb. is
passed to *note urlopen(): 791. (or *note OpenerDirector.open(): 8ff.).
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: Examples<21>,  Up: urllib request --- Extensible library for opening URLs

5.21.6.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(): 791. returned (for a remote object).
     Exceptions are the same as for *note urlopen(): 791.

     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(): 790. function.

     *note urlretrieve(): 2cb6. will raise ‘ContentTooShortError’ 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(): 2cb6.

 -- 類別: 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: 2c38.

     By default, the *note URLopener: 2c37. class sends a ‘User-Agent’
     header of ‘urllib/VVV’, where `VVV' is the *note urllib: 11e.
     version number.  Applications can define their own ‘User-Agent’
     header by subclassing *note URLopener: 2c37. or *note
     FancyURLopener: 2c38. and setting the class attribute *note
     version: 2cb8. 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(): 791, 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: 2c37. objects will raise an *note OSError: 1d4.
     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(): 2cba. is
          called.  The `data' argument has the same meaning as the
          `data' argument of *note urlopen(): 791.

          This method always quotes `fullurl' using *note quote(): 412.

      -- 成員函式: 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: 546. 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(): 1c79. 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(): 790. function.

      -- 屬性: version

          Variable that specifies the user agent of the opener object.
          To get *note urllib: 11e. 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: 2c38. subclasses *note URLopener: 2c37.
     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 ‘http_error_default()’ 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: 11e. reproduces
          this behaviour.

     The parameters to the constructor are the same as those for *note
     URLopener: 2c37.

          備註: When performing basic authentication, a *note
          FancyURLopener: 2c38. instance calls its *note
          prompt_user_passwd(): 2cbb. 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: 2c38. 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://tools.ietf.org/html/rfc2616.html


File: python.info,  Node: urllib request Restrictions,  Prev: Legacy interface,  Up: urllib request --- Extensible library for opening URLs

5.21.6.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(): 2cb6. 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(): 791. and *note urlretrieve(): 2cb6. 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(): 791. or *note urlretrieve():
     2cb6. 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:
     92. 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: 84. module, subclassing
     *note FancyURLopener: 2c38, or changing `_urlopener' to meet your
     needs.


File: python.info,  Node: urllib response --- Response classes used by urllib,  Next: urllib parse --- Parse URLs into components,  Prev: urllib request --- Extensible library for opening URLs,  Up: Internet Protocols and Support

5.21.7 ‘urllib.response’ — Response classes used by urllib
----------------------------------------------------------

The *note urllib.response: 122. module defines functions and classes
which define a minimal file like interface, including ‘read()’ and
‘readline()’.  The typical response object is an addinfourl instance,
which defines an ‘info()’ method and that returns headers and a
‘geturl()’ method that returns the url.  Functions defined by this
module are used internally by the *note urllib.request: 121. module.


File: python.info,  Node: urllib parse --- Parse URLs into components,  Next: urllib error --- Exception classes raised by urllib request,  Prev: urllib response --- Response classes used by urllib,  Up: Internet Protocols and Support

5.21.8 ‘urllib.parse’ — Parse URLs into components
--------------------------------------------------

`Source code:' 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’, ‘mailto’,
‘mms’, ‘news’, ‘nntp’, ‘prospero’, ‘rsync’, ‘rtsp’, ‘rtspu’, ‘sftp’,
‘shttp’, ‘sip’, ‘sips’, ‘snews’, ‘svn’, ‘svn+ssh’, ‘telnet’, ‘wais’,
‘ws’, ‘wss’.

The *note urllib.parse: 120. module defines functions that fall into two
broad categories: URL parsing and URL quoting.  These are covered in
detail in the following sections.

* Menu:

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/urllib/parse.py


File: python.info,  Node: URL Parsing,  Next: Parsing ASCII Encoded Bytes,  Up: urllib parse --- Parse URLs into components

5.21.8.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: aa8.  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 in
     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
          >>> o = urlparse('http://www.cwi.nl:80/%7Eguido/Python.html')
          >>> o
          ParseResult(scheme='http', netloc='www.cwi.nl:80', path='/%7Eguido/Python.html',
                      params='', query='', fragment='')
          >>> o.scheme
          'http'
          >>> o.port
          80
          >>> o.geturl()
          'http://www.cwi.nl:80/%7Eguido/Python.html'

     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: aa8, which means that its
     items can be accessed by index or as named attributes, which are:

     Attribute              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: 158.
                                                                       
                                                                       
     ‘password’                         Password                       *note None: 158.
                                                                       
                                                                       
     ‘hostname’                         Host name (lower case)         *note None: 158.
                                                                       
                                                                       
     ‘port’                             Port number as integer, if     *note None: 158.
                                        present                        
                                        

     Reading the ‘port’ attribute will raise a *note ValueError: 1fc. if
     an invalid port is specified in the URL. See section *note
     Structured Parse Results: 2cc1. for more information on the result
     object.

     Unmatched square brackets in the ‘netloc’ attribute will raise a
     *note ValueError: 1fc.

     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: 1fc.  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='')

     3.2 版更變: Added IPv6 URL parsing capabilities.

     3.3 版更變: The fragment is now parsed for all URL schemes (unless
     `allow_fragment' is false), in accordance with RFC 3986(2).
     Previously, a whitelist of schemes that support fragments existed.

     3.6 版更變: Out-of-range port numbers now raise *note ValueError:
     1fc, instead of returning *note None: 158.

     3.8 版更變: Characters that affect netloc parsing under NFKC
     normalization will now raise *note ValueError: 1fc.

 -- 函式: 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: 1fc.
     exception.

     The optional `encoding' and `errors' parameters specify how to
     decode percent-encoded sequences into Unicode characters, as
     accepted by the *note bytes.decode(): c3d. method.

     The optional argument `max_num_fields' is the maximum number of
     fields to read.  If set, then throws a *note ValueError: 1fc. 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(): 790. function (with the
     ‘doseq’ parameter set to ‘True’) to convert such dictionaries into
     query strings.

     3.2 版更變: Add `encoding' and `errors' parameters.

     3.8 版更變: Added `max_num_fields' parameter.

     3.8.8 版更變: Added `separator' parameter with the default value of
     ‘&’.  Python versions earlier than Python 3.8.8 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: 1fc.
     exception.

     The optional `encoding' and `errors' parameters specify how to
     decode percent-encoded sequences into Unicode characters, as
     accepted by the *note bytes.decode(): c3d. method.

     The optional argument `max_num_fields' is the maximum number of
     fields to read.  If set, then throws a *note ValueError: 1fc. 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(): 790. function to convert
     such lists of pairs into query strings.

     3.2 版更變: Add `encoding' and `errors' parameters.

     3.8 版更變: Added `max_num_fields' parameter.

     3.8.8 版更變: Added `separator' parameter with the default value of
     ‘&’.  Python versions earlier than Python 3.8.8 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(): 5ff, but does not split the
     params from the URL. This should generally be used instead of *note
     urlparse(): 5ff. 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: aa8.:

          (addressing scheme, network location, path, query, fragment identifier).

     The return value is a *note named tuple: aa8, its items can be
     accessed by index or as named attributes:

     Attribute              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: 158.
                                                                      
                                                                      
     ‘password’                         Password                      *note None: 158.
                                                                      
                                                                      
     ‘hostname’                         Host name (lower case)        *note None: 158.
                                                                      
                                                                      
     ‘port’                             Port number as integer, if    *note None: 158.
                                        present                       
                                        

     Reading the ‘port’ attribute will raise a *note ValueError: 1fc. if
     an invalid port is specified in the URL. See section *note
     Structured Parse Results: 2cc1. for more information on the result
     object.

     Unmatched square brackets in the ‘netloc’ attribute will raise a
     *note ValueError: 1fc.

     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: 1fc.  If the URL is
     decomposed before parsing, no error will be raised.

     Following the WHATWG spec(4) that updates RFC 3986, ASCII newline
     ‘\n’, ‘\r’ and tab ‘\t’ characters are stripped from the URL.

     3.6 版更變: Out-of-range port numbers now raise *note ValueError:
     1fc, instead of returning *note None: 158.

     3.8 版更變: Characters that affect netloc parsing under NFKC
     normalization will now raise *note ValueError: 1fc.

     3.8.10 版更變: ASCII newline and tab characters are stripped from
     the URL.

 -- 函式: urllib.parse.urlunsplit (parts)

     Combine the elements of a tuple as returned by *note urlsplit():
     5fe. 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(): 5ff.

          備註: If `url' is an absolute URL (that is, starting with ‘//’
          or ‘scheme://’), the `url'’s host name 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(): 5fe. and *note urlunsplit(): 2cc3, removing possible
     `scheme' and `netloc' parts.

     3.5 版更變: Behaviour 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: aa8, its items can be
     accessed by index or as named attributes:

     Attribute              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: 2cc1. 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://tools.ietf.org/html/rfc1808.html

   (2) https://tools.ietf.org/html/rfc3986.html

   (3) https://tools.ietf.org/html/rfc2396.html

   (4) https://url.spec.whatwg.org/#concept-basic-url-parser

   (5) https://tools.ietf.org/html/rfc3986.html


File: python.info,  Node: Parsing ASCII Encoded Bytes,  Next: Structured Parse Results,  Prev: URL Parsing,  Up: urllib parse --- Parse URLs into components

5.21.8.2 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: 336. and *note bytearray: 337. objects in addition to *note
str: 335. objects.

If *note str: 335. data is passed in, the result will also contain only
*note str: 335. data.  If *note bytes: 336. or *note bytearray: 337.
data is passed in, the result will contain only *note bytes: 336. data.

Attempting to mix *note str: 335. data with *note bytes: 336. or *note
bytearray: 337. in a single function call will result in a *note
TypeError: 193. being raised, while attempting to pass in non-ASCII byte
values will trigger *note UnicodeDecodeError: 1fe.

To support easier conversion of result objects between *note str: 335.
and *note bytes: 336, all return values from URL parsing functions
provide either an ‘encode()’ method (when the result contains *note str:
335. data) or a ‘decode()’ method (when the result contains *note bytes:
336. data).  The signatures of these methods match those of the
corresponding *note str: 335. and *note bytes: 336. 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: 336.
data (for ‘encode()’ methods) or *note str: 335. 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 --- Parse URLs into components

5.21.8.3 Structured Parse Results
.................................

The result objects from the *note urlparse(): 5ff, *note urlsplit():
5fe. and *note urldefrag(): be3. functions are subclasses of the *note
tuple: 483. 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(): be3. results, only empty fragment
     identifiers will be removed.  For *note urlsplit(): 5fe. and *note
     urlparse(): 5ff. 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: 335. objects:

 -- 類別: urllib.parse.DefragResult (url, fragment)

     Concrete class for *note urldefrag(): be3. results containing *note
     str: 335. data.  The ‘encode()’ method returns a *note
     DefragResultBytes: 2cc9. instance.

     3.2 版新加入.

 -- 類別: urllib.parse.ParseResult (scheme, netloc, path, params, query,
          fragment)

     Concrete class for *note urlparse(): 5ff. results containing *note
     str: 335. data.  The ‘encode()’ method returns a *note
     ParseResultBytes: 2ccb. instance.

 -- 類別: urllib.parse.SplitResult (scheme, netloc, path, query,
          fragment)

     Concrete class for *note urlsplit(): 5fe. results containing *note
     str: 335. data.  The ‘encode()’ method returns a *note
     SplitResultBytes: 2ccd. instance.

The following classes provide the implementations of the parse results
when operating on *note bytes: 336. or *note bytearray: 337. objects:

 -- 類別: urllib.parse.DefragResultBytes (url, fragment)

     Concrete class for *note urldefrag(): be3. results containing *note
     bytes: 336. data.  The ‘decode()’ method returns a *note
     DefragResult: 2cc8. instance.

     3.2 版新加入.

 -- 類別: urllib.parse.ParseResultBytes (scheme, netloc, path, params,
          query, fragment)

     Concrete class for *note urlparse(): 5ff. results containing *note
     bytes: 336. data.  The ‘decode()’ method returns a *note
     ParseResult: 2cca. instance.

     3.2 版新加入.

 -- 類別: urllib.parse.SplitResultBytes (scheme, netloc, path, query,
          fragment)

     Concrete class for *note urlsplit(): 5fe. results containing *note
     bytes: 336. data.  The ‘decode()’ method returns a *note
     SplitResult: 2ccc. instance.

     3.2 版新加入.


File: python.info,  Node: URL Quoting,  Prev: Structured Parse Results,  Up: urllib parse --- Parse URLs into components

5.21.8.4 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
     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: 335. or a *note bytes: 336.

     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():
     c3c. method.  `encoding' defaults to ‘'utf-8'’.  `errors' defaults
     to ‘'strict'’, meaning unsupported characters raise a *note
     UnicodeEncodeError: 1fd.  `encoding' and `errors' must not be
     supplied if `string' is a *note bytes: 336, or a *note TypeError:
     193. 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(): 412, but also replace spaces by 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(): 412, but accepts a *note bytes: 336. object
     rather than a *note str: 335, 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 by 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(): c3d. method.

     `string' must be a *note str: 335.

     `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/'’.

 -- 函式: urllib.parse.unquote_plus (string, encoding='utf-8',
          errors='replace')

     Like *note unquote(): edc, but also replace plus signs by spaces,
     as required for unquoting HTML form values.

     `string' must be a *note str: 335.

     Example: ‘unquote_plus('/El+Ni%C3%B1o/')’ yields ‘'/El Niño/'’.

 -- 函式: urllib.parse.unquote_to_bytes (string)

     Replace ‘%xx’ escapes by their single-octet equivalent, and return
     a *note bytes: 336. object.

     `string' may be either a *note str: 335. or a *note bytes: 336.

     If it is a *note str: 335, 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: 335. or *note bytes: 336. 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():
     791. function, then it should be encoded to bytes, otherwise it
     would result in a *note TypeError: 193.

     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(): be4. 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(): 412, 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' is 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: 335.).

     To reverse this encoding process, *note parse_qs(): 2ec. and *note
     parse_qsl(): 2ed. are provided in this module to parse query
     strings into Python data structures.

     Refer to *note urllib examples: 2cb4. to find out how urlencode
     method can be used for generating query string for a URL or data
     for POST.

     3.2 版更變: Query parameter supports bytes and string objects.

     3.5 版新加入: `quote_via' parameter.

也參考
......

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) - Uniform Resource Locators (URL)

     This specifies the formal syntax and semantics of absolute URLs.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2396.html

   (2) https://tools.ietf.org/html/rfc3986.html

   (3) https://url.spec.whatwg.org/

   (4) https://tools.ietf.org/html/rfc3986.html

   (5) https://tools.ietf.org/html/rfc2732.html

   (6) https://tools.ietf.org/html/rfc2396.html

   (7) https://tools.ietf.org/html/rfc2368.html

   (8) https://tools.ietf.org/html/rfc1808.html

   (9) https://tools.ietf.org/html/rfc1738.html


File: python.info,  Node: urllib error --- Exception classes raised by urllib request,  Next: urllib robotparser --- Parser for robots txt,  Prev: urllib parse --- Parse URLs into components,  Up: Internet Protocols and Support

5.21.9 ‘urllib.error’ — Exception classes raised by urllib.request
------------------------------------------------------------------

`Source code:' Lib/urllib/error.py(1)

__________________________________________________________________

The *note urllib.error: 11f. module defines the exception classes for
exceptions raised by *note urllib.request: 121.  The base exception
class is *note URLError: 2c39.

The following exceptions are raised by *note urllib.error: 11f. as
appropriate:

 -- 例外: urllib.error.URLError

     The handlers raise this exception (or derived exceptions) when they
     run into a problem.  It is a subclass of *note OSError: 1d4.

      -- 屬性: reason

          The reason for this error.  It can be a message string or
          another exception instance.

     3.3 版更變: *note URLError: 2c39. has been made a subclass of *note
     OSError: 1d4. instead of *note IOError: 997.

 -- 例外: urllib.error.HTTPError

     Though being an exception (a subclass of *note URLError: 2c39.), an
     *note HTTPError: 901. can also function as a non-exceptional
     file-like return value (the same thing that *note urlopen(): 791.
     returns).  This is useful when handling exotic HTTP errors, such as
     requests for authentication.

      -- 屬性: code

          An HTTP status code as defined in RFC 2616(2).  This numeric
          value corresponds to a value found in the dictionary of codes
          as found in *note
          http.server.BaseHTTPRequestHandler.responses: 2cd7.

      -- 屬性: reason

          This is usually a string explaining the reason for this error.

      -- 屬性: headers

          The HTTP response headers for the HTTP request that caused the
          *note HTTPError: 901.

          3.4 版新加入.

 -- 例外: urllib.error.ContentTooShortError (msg, content)

     This exception is raised when the *note urlretrieve(): 2cb6.
     function detects that the amount of the downloaded data is less
     than the expected amount (given by the `Content-Length' header).
     The ‘content’ attribute stores the downloaded (and supposedly
     truncated) data.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/urllib/error.py

   (2) https://tools.ietf.org/html/rfc2616.html


File: python.info,  Node: urllib robotparser --- Parser for robots txt,  Next: http --- HTTP modules,  Prev: urllib error --- Exception classes raised by urllib request,  Up: Internet Protocols and Support

5.21.10 ‘urllib.robotparser’ — Parser for robots.txt
----------------------------------------------------

`Source code:' Lib/urllib/robotparser.py(1)

__________________________________________________________________

This module provides a single class, *note RobotFileParser: 5b2, which
answers questions about whether or not a particular user agent can fetch
a URL on the Web site that published the ‘robots.txt’ file.  For more
details on the structure of ‘robots.txt’ files, see
‘http://www.robotstxt.org/orig.html’.

 -- 類別: urllib.robotparser.RobotFileParser (url='')

     This class provides methods to read, parse and answer questions
     about the ‘robots.txt’ file at `url'.

      -- 成員函式: set_url (url)

          Sets the URL referring to a ‘robots.txt’ file.

      -- 成員函式: read ()

          Reads the ‘robots.txt’ URL and feeds it to the parser.

      -- 成員函式: parse (lines)

          Parses the lines argument.

      -- 成員函式: can_fetch (useragent, url)

          Returns ‘True’ if the `useragent' is allowed to fetch the
          `url' according to the rules contained in the parsed
          ‘robots.txt’ file.

      -- 成員函式: mtime ()

          Returns the time the ‘robots.txt’ file was last fetched.  This
          is useful for long-running web spiders that need to check for
          new ‘robots.txt’ files periodically.

      -- 成員函式: modified ()

          Sets the time the ‘robots.txt’ file was last fetched to the
          current time.

      -- 成員函式: crawl_delay (useragent)

          Returns the value of the ‘Crawl-delay’ parameter from
          ‘robots.txt’ for the `useragent' in question.  If there is no
          such parameter or it doesn’t apply to the `useragent'
          specified or the ‘robots.txt’ entry for this parameter has
          invalid syntax, return ‘None’.

          3.6 版新加入.

      -- 成員函式: request_rate (useragent)

          Returns the contents of the ‘Request-rate’ parameter from
          ‘robots.txt’ as a *note named tuple: aa8.
          ‘RequestRate(requests, seconds)’.  If there is no such
          parameter or it doesn’t apply to the `useragent' specified or
          the ‘robots.txt’ entry for this parameter has invalid syntax,
          return ‘None’.

          3.6 版新加入.

      -- 成員函式: site_maps ()

          Returns the contents of the ‘Sitemap’ parameter from
          ‘robots.txt’ in the form of a *note list(): 263.  If there is
          no such parameter or the ‘robots.txt’ entry for this parameter
          has invalid syntax, return ‘None’.

          3.8 版新加入.

The following example demonstrates basic use of the *note
RobotFileParser: 5b2. class:

     >>> 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.8/Lib/urllib/robotparser.py


File: python.info,  Node: http --- HTTP modules,  Next: http client --- HTTP protocol client,  Prev: urllib robotparser --- Parser for robots txt,  Up: Internet Protocols and Support

5.21.11 ‘http’ — HTTP modules
-----------------------------

`Source code:' Lib/http/__init__.py(1)

__________________________________________________________________

*note http: 93. is a package that collects several modules for working
with the HyperText Transfer Protocol:

   * *note http.client: 94. is a low-level HTTP protocol client; for
     high-level URL opening use *note urllib.request: 121.

   * *note http.server: 97. contains basic HTTP server classes based on
     *note socketserver: f1.

   * *note http.cookies: 96. has utilities for implementing state
     management with cookies

   * *note http.cookiejar: 95. provides persistence of cookies

*note http: 93. is also a module that defines a number of HTTP status
codes and associated messages through the *note http.HTTPStatus: 6e7.
enum:

 -- 類別: http.HTTPStatus

     3.5 版新加入.

     A subclass of *note enum.IntEnum: 592. that defines a set of HTTP
     status codes, reason phrases and long descriptions written in
     English.

     Usage:

          >>> from http import HTTPStatus
          >>> HTTPStatus.OK
          <HTTPStatus.OK: 200>
          >>> HTTPStatus.OK == 200
          True
          >>> HTTPStatus.OK.value
          200
          >>> HTTPStatus.OK.phrase
          'OK'
          >>> HTTPStatus.OK.description
          'Request fulfilled, document follows'
          >>> list(HTTPStatus)
          [<HTTPStatus.CONTINUE: 100>, <HTTPStatus.SWITCHING_PROTOCOLS: 101>, ...]

* Menu:

* HTTP status codes::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/http/__init__.py


File: python.info,  Node: HTTP status codes,  Up: http --- HTTP modules

5.21.11.1 HTTP status codes
...........................

Supported, IANA-registered(1) status codes available in *note
http.HTTPStatus: 6e7. are:

Code        Enum Name                               Details
                                                    
----------------------------------------------------------------------------------------------------------------------------------------
                                                    
‘100’       ‘CONTINUE’                              HTTP/1.1 RFC 7231(2), Section 6.2.1
                                                    
                                                    
‘101’       ‘SWITCHING_PROTOCOLS’                   HTTP/1.1 RFC 7231(3), Section 6.2.2
                                                    
                                                    
‘102’       ‘PROCESSING’                            WebDAV RFC 2518(4), Section 10.1
                                                    
                                                    
‘200’       ‘OK’                                    HTTP/1.1 RFC 7231(5), Section 6.3.1
                                                    
                                                    
‘201’       ‘CREATED’                               HTTP/1.1 RFC 7231(6), Section 6.3.2
                                                    
                                                    
‘202’       ‘ACCEPTED’                              HTTP/1.1 RFC 7231(7), Section 6.3.3
                                                    
                                                    
‘203’       ‘NON_AUTHORITATIVE_INFORMATION’         HTTP/1.1 RFC 7231(8), Section 6.3.4
                                                    
                                                    
‘204’       ‘NO_CONTENT’                            HTTP/1.1 RFC 7231(9), Section 6.3.5
                                                    
                                                    
‘205’       ‘RESET_CONTENT’                         HTTP/1.1 RFC 7231(10), Section 6.3.6
                                                    
                                                    
‘206’       ‘PARTIAL_CONTENT’                       HTTP/1.1 RFC 7233(11), Section 4.1
                                                    
                                                    
‘207’       ‘MULTI_STATUS’                          WebDAV RFC 4918(12), Section 11.1
                                                    
                                                    
‘208’       ‘ALREADY_REPORTED’                      WebDAV Binding Extensions RFC 5842(13), Section 7.1 (Experimental)
                                                    
                                                    
‘226’       ‘IM_USED’                               Delta Encoding in HTTP RFC 3229(14), Section 10.4.1
                                                    
                                                    
‘300’       ‘MULTIPLE_CHOICES’                      HTTP/1.1 RFC 7231(15), Section 6.4.1
                                                    
                                                    
‘301’       ‘MOVED_PERMANENTLY’                     HTTP/1.1 RFC 7231(16), Section 6.4.2
                                                    
                                                    
‘302’       ‘FOUND’                                 HTTP/1.1 RFC 7231(17), Section 6.4.3
                                                    
                                                    
‘303’       ‘SEE_OTHER’                             HTTP/1.1 RFC 7231(18), Section 6.4.4
                                                    
                                                    
‘304’       ‘NOT_MODIFIED’                          HTTP/1.1 RFC 7232(19), Section 4.1
                                                    
                                                    
‘305’       ‘USE_PROXY’                             HTTP/1.1 RFC 7231(20), Section 6.4.5
                                                    
                                                    
‘307’       ‘TEMPORARY_REDIRECT’                    HTTP/1.1 RFC 7231(21), Section 6.4.7
                                                    
                                                    
‘308’       ‘PERMANENT_REDIRECT’                    Permanent Redirect RFC 7238(22), Section 3 (Experimental)
                                                    
                                                    
‘400’       ‘BAD_REQUEST’                           HTTP/1.1 RFC 7231(23), Section 6.5.1
                                                    
                                                    
‘401’       ‘UNAUTHORIZED’                          HTTP/1.1 Authentication RFC 7235(24), Section 3.1
                                                    
                                                    
‘402’       ‘PAYMENT_REQUIRED’                      HTTP/1.1 RFC 7231(25), Section 6.5.2
                                                    
                                                    
‘403’       ‘FORBIDDEN’                             HTTP/1.1 RFC 7231(26), Section 6.5.3
                                                    
                                                    
‘404’       ‘NOT_FOUND’                             HTTP/1.1 RFC 7231(27), Section 6.5.4
                                                    
                                                    
‘405’       ‘METHOD_NOT_ALLOWED’                    HTTP/1.1 RFC 7231(28), Section 6.5.5
                                                    
                                                    
‘406’       ‘NOT_ACCEPTABLE’                        HTTP/1.1 RFC 7231(29), Section 6.5.6
                                                    
                                                    
‘407’       ‘PROXY_AUTHENTICATION_REQUIRED’         HTTP/1.1 Authentication RFC 7235(30), Section 3.2
                                                    
                                                    
‘408’       ‘REQUEST_TIMEOUT’                       HTTP/1.1 RFC 7231(31), Section 6.5.7
                                                    
                                                    
‘409’       ‘CONFLICT’                              HTTP/1.1 RFC 7231(32), Section 6.5.8
                                                    
                                                    
‘410’       ‘GONE’                                  HTTP/1.1 RFC 7231(33), Section 6.5.9
                                                    
                                                    
‘411’       ‘LENGTH_REQUIRED’                       HTTP/1.1 RFC 7231(34), Section 6.5.10
                                                    
                                                    
‘412’       ‘PRECONDITION_FAILED’                   HTTP/1.1 RFC 7232(35), Section 4.2
                                                    
                                                    
‘413’       ‘REQUEST_ENTITY_TOO_LARGE’              HTTP/1.1 RFC 7231(36), Section 6.5.11
                                                    
                                                    
‘414’       ‘REQUEST_URI_TOO_LONG’                  HTTP/1.1 RFC 7231(37), Section 6.5.12
                                                    
                                                    
‘415’       ‘UNSUPPORTED_MEDIA_TYPE’                HTTP/1.1 RFC 7231(38), Section 6.5.13
                                                    
                                                    
‘416’       ‘REQUESTED_RANGE_NOT_SATISFIABLE’       HTTP/1.1 Range Requests RFC 7233(39), Section 4.4
                                                    
                                                    
‘417’       ‘EXPECTATION_FAILED’                    HTTP/1.1 RFC 7231(40), Section 6.5.14
                                                    
                                                    
‘421’       ‘MISDIRECTED_REQUEST’                   HTTP/2 RFC 7540(41), Section 9.1.2
                                                    
                                                    
‘422’       ‘UNPROCESSABLE_ENTITY’                  WebDAV RFC 4918(42), Section 11.2
                                                    
                                                    
‘423’       ‘LOCKED’                                WebDAV RFC 4918(43), Section 11.3
                                                    
                                                    
‘424’       ‘FAILED_DEPENDENCY’                     WebDAV RFC 4918(44), Section 11.4
                                                    
                                                    
‘426’       ‘UPGRADE_REQUIRED’                      HTTP/1.1 RFC 7231(45), Section 6.5.15
                                                    
                                                    
‘428’       ‘PRECONDITION_REQUIRED’                 Additional HTTP Status Codes RFC 6585(46)
                                                    
                                                    
‘429’       ‘TOO_MANY_REQUESTS’                     Additional HTTP Status Codes RFC 6585(47)
                                                    
                                                    
‘431’       ‘REQUEST_HEADER_FIELDS_TOO_LARGE’       Additional HTTP Status Codes RFC 6585(48)
                                                    
                                                    
‘451’       ‘UNAVAILABLE_FOR_LEGAL_REASONS’         An HTTP Status Code to Report Legal Obstacles RFC 7725(49)
                                                    
                                                    
‘500’       ‘INTERNAL_SERVER_ERROR’                 HTTP/1.1 RFC 7231(50), Section 6.6.1
                                                    
                                                    
‘501’       ‘NOT_IMPLEMENTED’                       HTTP/1.1 RFC 7231(51), Section 6.6.2
                                                    
                                                    
‘502’       ‘BAD_GATEWAY’                           HTTP/1.1 RFC 7231(52), Section 6.6.3
                                                    
                                                    
‘503’       ‘SERVICE_UNAVAILABLE’                   HTTP/1.1 RFC 7231(53), Section 6.6.4
                                                    
                                                    
‘504’       ‘GATEWAY_TIMEOUT’                       HTTP/1.1 RFC 7231(54), Section 6.6.5
                                                    
                                                    
‘505’       ‘HTTP_VERSION_NOT_SUPPORTED’            HTTP/1.1 RFC 7231(55), Section 6.6.6
                                                    
                                                    
‘506’       ‘VARIANT_ALSO_NEGOTIATES’               Transparent Content Negotiation in HTTP RFC 2295(56), Section 8.1 (Experimental)
                                                    
                                                    
‘507’       ‘INSUFFICIENT_STORAGE’                  WebDAV RFC 4918(57), Section 11.5
                                                    
                                                    
‘508’       ‘LOOP_DETECTED’                         WebDAV Binding Extensions RFC 5842(58), Section 7.2 (Experimental)
                                                    
                                                    
‘510’       ‘NOT_EXTENDED’                          An HTTP Extension Framework RFC 2774(59), Section 7 (Experimental)
                                                    
                                                    
‘511’       ‘NETWORK_AUTHENTICATION_REQUIRED’       Additional HTTP Status Codes RFC 6585(60), Section 6
                                                    

In order to preserve backwards compatibility, enum values are also
present in the *note http.client: 94. module in the form of constants.
The enum name is equal to the constant name (i.e.  ‘http.HTTPStatus.OK’
is also available as ‘http.client.OK’).

3.7 版更變: Added ‘421 MISDIRECTED_REQUEST’ status code.

3.8 版新加入: Added ‘451 UNAVAILABLE_FOR_LEGAL_REASONS’ status code.

   ---------- Footnotes ----------

   (1) 
https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml

   (2) https://tools.ietf.org/html/rfc7231.html

   (3) https://tools.ietf.org/html/rfc7231.html

   (4) https://tools.ietf.org/html/rfc2518.html

   (5) https://tools.ietf.org/html/rfc7231.html

   (6) https://tools.ietf.org/html/rfc7231.html

   (7) https://tools.ietf.org/html/rfc7231.html

   (8) https://tools.ietf.org/html/rfc7231.html

   (9) https://tools.ietf.org/html/rfc7231.html

   (10) https://tools.ietf.org/html/rfc7231.html

   (11) https://tools.ietf.org/html/rfc7233.html

   (12) https://tools.ietf.org/html/rfc4918.html

   (13) https://tools.ietf.org/html/rfc5842.html

   (14) https://tools.ietf.org/html/rfc3229.html

   (15) https://tools.ietf.org/html/rfc7231.html

   (16) https://tools.ietf.org/html/rfc7231.html

   (17) https://tools.ietf.org/html/rfc7231.html

   (18) https://tools.ietf.org/html/rfc7231.html

   (19) https://tools.ietf.org/html/rfc7232.html

   (20) https://tools.ietf.org/html/rfc7231.html

   (21) https://tools.ietf.org/html/rfc7231.html

   (22) https://tools.ietf.org/html/rfc7238.html

   (23) https://tools.ietf.org/html/rfc7231.html

   (24) https://tools.ietf.org/html/rfc7235.html

   (25) https://tools.ietf.org/html/rfc7231.html

   (26) https://tools.ietf.org/html/rfc7231.html

   (27) https://tools.ietf.org/html/rfc7231.html

   (28) https://tools.ietf.org/html/rfc7231.html

   (29) https://tools.ietf.org/html/rfc7231.html

   (30) https://tools.ietf.org/html/rfc7235.html

   (31) https://tools.ietf.org/html/rfc7231.html

   (32) https://tools.ietf.org/html/rfc7231.html

   (33) https://tools.ietf.org/html/rfc7231.html

   (34) https://tools.ietf.org/html/rfc7231.html

   (35) https://tools.ietf.org/html/rfc7232.html

   (36) https://tools.ietf.org/html/rfc7231.html

   (37) https://tools.ietf.org/html/rfc7231.html

   (38) https://tools.ietf.org/html/rfc7231.html

   (39) https://tools.ietf.org/html/rfc7233.html

   (40) https://tools.ietf.org/html/rfc7231.html

   (41) https://tools.ietf.org/html/rfc7540.html

   (42) https://tools.ietf.org/html/rfc4918.html

   (43) https://tools.ietf.org/html/rfc4918.html

   (44) https://tools.ietf.org/html/rfc4918.html

   (45) https://tools.ietf.org/html/rfc7231.html

   (46) https://tools.ietf.org/html/rfc6585.html

   (47) https://tools.ietf.org/html/rfc6585.html

   (48) https://tools.ietf.org/html/rfc6585.html

   (49) https://tools.ietf.org/html/rfc7725.html

   (50) https://tools.ietf.org/html/rfc7231.html

   (51) https://tools.ietf.org/html/rfc7231.html

   (52) https://tools.ietf.org/html/rfc7231.html

   (53) https://tools.ietf.org/html/rfc7231.html

   (54) https://tools.ietf.org/html/rfc7231.html

   (55) https://tools.ietf.org/html/rfc7231.html

   (56) https://tools.ietf.org/html/rfc2295.html

   (57) https://tools.ietf.org/html/rfc4918.html

   (58) https://tools.ietf.org/html/rfc5842.html

   (59) https://tools.ietf.org/html/rfc2774.html

   (60) https://tools.ietf.org/html/rfc6585.html


File: python.info,  Node: http client --- HTTP protocol client,  Next: ftplib --- FTP protocol client,  Prev: http --- HTTP modules,  Up: Internet Protocols and Support

5.21.12 ‘http.client’ — HTTP protocol client
--------------------------------------------

`Source code:' Lib/http/client.py(1)

__________________________________________________________________

This module defines classes which implement the client side of the HTTP
and HTTPS protocols.  It is normally not used directly — the module
*note urllib.request: 121. 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: f4. module).

The module provides the following classes:

 -- 類別: http.client.HTTPConnection (host, port=None[, timeout],
          source_address=None, blocksize=8192)

     An *note HTTPConnection: 397. instance represents one transaction
     with an HTTP server.  It should be instantiated 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' was added.

     3.4 版更變: The `strict' parameter was removed.  HTTP 0.9-style
     "Simple Responses" are not longer supported.

     3.7 版更變: `blocksize' parameter was added.

 -- 類別: http.client.HTTPSConnection (host, port=None, key_file=None,
          cert_file=None[, timeout], source_address=None, *,
          context=None, check_hostname=None, blocksize=8192)

     A subclass of *note HTTPConnection: 397. that uses SSL for
     communication with secure servers.  Default port is ‘443’.  If
     `context' is specified, it must be a *note ssl.SSLContext: 3e9.
     instance describing the various SSL options.

     Please read *note Security considerations: 25b3. for more
     information on best practices.

     3.2 版更變: `source_address', `context' and `check_hostname' were
     added.

     3.2 版更變: This class now supports HTTPS virtual hosts if possible
     (that is, if *note ssl.HAS_SNI: 26df. 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: 225. for the default `context'
     or when `cert_file' is passed with a custom `context'.

     3.6 版後已棄用: `key_file' and `cert_file' are deprecated in favor
     of `context'.  Please use *note ssl.SSLContext.load_cert_chain():
     a96. instead, or let *note ssl.create_default_context(): 8c6.
     select the system’s trusted CA certificates for you.

     The `check_hostname' parameter is also deprecated; the *note
     ssl.SSLContext.check_hostname: 26ca. attribute of `context' should
     be used instead.

 -- 類別: 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 ‘BufferedIOBase’ reader
     (i.e.  not text) and must provide a valid RFC 2822(3) style header.

     This function returns an instance of ‘http.client.HTTPMessage’ that
     holds the header fields, but no payload (the same as *note
     HTTPResponse.msg: 2ce9. and *note
     http.server.BaseHTTPRequestHandler.headers: 2cea.).  After
     returning, the file pointer `fp' is ready to read the HTTP body.

          備註: *note parse_headers(): 1045. 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: 1aa.

 -- 例外: http.client.NotConnected

     A subclass of *note HTTPException: 2ceb.

 -- 例外: http.client.InvalidURL

     A subclass of *note HTTPException: 2ceb, raised if a port is given
     and is either non-numeric or empty.

 -- 例外: http.client.UnknownProtocol

     A subclass of *note HTTPException: 2ceb.

 -- 例外: http.client.UnknownTransferEncoding

     A subclass of *note HTTPException: 2ceb.

 -- 例外: http.client.UnimplementedFileMode

     A subclass of *note HTTPException: 2ceb.

 -- 例外: http.client.IncompleteRead

     A subclass of *note HTTPException: 2ceb.

 -- 例外: http.client.ImproperConnectionState

     A subclass of *note HTTPException: 2ceb.

 -- 例外: http.client.CannotSendRequest

     A subclass of *note ImproperConnectionState: 2cf2.

 -- 例外: http.client.CannotSendHeader

     A subclass of *note ImproperConnectionState: 2cf2.

 -- 例外: http.client.ResponseNotReady

     A subclass of *note ImproperConnectionState: 2cf2.

 -- 例外: http.client.BadStatusLine

     A subclass of *note HTTPException: 2ceb.  Raised if a server
     responds with a HTTP status code that we don’t understand.

 -- 例外: http.client.LineTooLong

     A subclass of *note HTTPException: 2ceb.  Raised if an excessively
     long line is received in the HTTP protocol from the server.

 -- 例外: http.client.RemoteDisconnected

     A subclass of *note ConnectionResetError: 9a5. and *note
     BadStatusLine: 2cf6.  Raised by *note HTTPConnection.getresponse():
     6e9. 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: 2cf6.‘('')’ was
     raised.

The constants defined in this module are:

 -- Data: http.client.HTTP_PORT

     The default port for the HTTP protocol (always ‘80’).

 -- Data: http.client.HTTPS_PORT

     The default port for the HTTPS protocol (always ‘443’).

 -- Data: 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 status codes: 2ce5. for a list of HTTP status codes that
are available in this module as constants.

* Menu:

* HTTPConnection Objects::
* HTTPResponse Objects::
* Examples: Examples<22>.
* HTTPMessage Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/http/client.py

   (2) https://requests.readthedocs.io/en/master/

   (3) https://tools.ietf.org/html/rfc2822.html


File: python.info,  Node: HTTPConnection Objects,  Next: HTTPResponse Objects,  Up: http client --- HTTP protocol client

5.21.12.1 HTTPConnection Objects
................................

*note HTTPConnection: 397. 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 selector `url'.

     If `body' is specified, the specified data is sent after the
     headers are finished.  It may be a *note str: 335, a *note
     bytes-like object: 5ed, an open *note file object: b47, or an
     iterable of *note bytes: 336.  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: b47, 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: c3e, 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.

     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: b47, 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.

          備註: 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: 335. 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: a16. 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: 6eb. or subclass is raised,
     the *note HTTPConnection: 397. 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: a16.
     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.

     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: 398. constructor, and the address of the host that
     we eventually want to reach to the *note set_tunnel(): bb2. method:

          >>> import http.client
          >>> conn = http.client.HTTPSConnection("localhost", 8080)
          >>> conn.set_tunnel("www.python.org")
          >>> conn.request("HEAD","/index.html")

     3.2 版新加入.

 -- 成員函式: 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.

 -- 成員函式: 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 ‘request()’ 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(1)-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(2),
     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: 15ec. the encoding will result in a single chunk.  If
     `message_body' is a *note collections.abc.Iterable: 1957, each
     iteration of `message_body' will result in a chunk.  If
     `message_body' is a *note file object: b47, 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 版新加入: Chunked encoding support.  The `encode_chunked'
     parameter was added.

 -- 成員函式: HTTPConnection.send (data)

     Send data to the server.  This should be used directly only after
     the *note endheaders(): 555. method has been called and before
     *note getresponse(): 6e9. is called.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc822.html

   (2) https://tools.ietf.org/html/rfc7230.html


File: python.info,  Node: HTTPResponse Objects,  Next: Examples<22>,  Prev: HTTPConnection Objects,  Up: http client --- HTTP protocol client

5.21.12.2 HTTPResponse Objects
..............................

An *note HTTPResponse: a16. 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: 58d. 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 ‘http.client.HTTPMessage’ instance containing the response
     headers.  ‘http.client.HTTPMessage’ is a subclass of *note
     email.message.Message: 546.

 -- 屬性: HTTPResponse.version

     HTTP protocol version used by server.  10 for HTTP/1.0, 11 for
     HTTP/1.1.

 -- 屬性: HTTPResponse.status

     Status code returned by server.

 -- 屬性: HTTPResponse.reason

     Reason phrase returned by server.

 -- 屬性: HTTPResponse.debuglevel

     A debugging hook.  If *note debuglevel: 2d0c. 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.


File: python.info,  Node: Examples<22>,  Next: HTTPMessage Objects,  Prev: HTTPResponse Objects,  Up: http client --- HTTP protocol client

5.21.12.3 Examples
..................

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 shows how to ‘POST’ requests:

     >>> 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="http://bugs.python.org/issue12524">http://bugs.python.org/issue12524</a>'
     >>> conn.close()

Client side ‘HTTP PUT’ requests are very similar to ‘POST’ requests.
The difference lies only the server side where HTTP server will allow
resources to be created via ‘PUT’ request.  It should be noted that
custom HTTP methods are also handled in *note urllib.request.Request:
8fb. by setting the appropriate method attribute.  Here is an example
session that shows how to send a ‘PUT’ request using http.client:

     >>> # This creates an HTTP message
     >>> # 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 Objects,  Prev: Examples<22>,  Up: http client --- HTTP protocol client

5.21.12.4 HTTPMessage Objects
.............................

An ‘http.client.HTTPMessage’ instance holds the headers from an HTTP
response.  It is implemented using the *note email.message.Message: 546.
class.


File: python.info,  Node: ftplib --- FTP protocol client,  Next: poplib --- POP3 protocol client,  Prev: http client --- HTTP protocol client,  Up: Internet Protocols and Support

5.21.13 ‘ftplib’ — FTP protocol client
--------------------------------------

`Source code:' Lib/ftplib.py(1)

__________________________________________________________________

This module defines the class *note FTP: 2f1. and a few related items.
The *note FTP: 2f1. class implements the client side of the FTP
protocol.  You can use this to write Python programs that perform a
variety of automated FTP jobs, such as mirroring other FTP servers.  It
is also used by the module *note urllib.request: 121. to handle URLs
that use FTP. For more information on FTP (File Transfer Protocol), see
Internet RFC 959(2).

Here’s a sample session using the *note ftplib: 84. module:

     >>> from ftplib import FTP
     >>> ftp = FTP('ftp.debian.org')     # connect to host, default port
     >>> ftp.login()                     # user anonymous, passwd anonymous@
     '230 Login successful.'
     >>> ftp.cwd('debian')               # change into "debian" directory
     >>> 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()

The module defines the following items:

 -- 類別: ftplib.FTP (host='', user='', passwd='', acct='',
          timeout=None, source_address=None)

     Return a new instance of the *note FTP: 2f1. class.  When `host' is
     given, the method call ‘connect(host)’ is made.  When `user' is
     given, additionally the method call ‘login(user, passwd, acct)’ is
     made (where `passwd' and `acct' default to the empty string when
     not given).  The optional `timeout' parameter specifies a timeout
     in seconds for blocking operations like the connection attempt (if
     is not specified, the global default timeout setting will be used).
     `source_address' is a 2-tuple ‘(host, port)’ for the socket to bind
     to as its source address before connecting.

     The *note FTP: 2f1. class supports the *note with: 6ee. statement,
     e.g.:

          >>> 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 版更變: Support for the *note with: 6ee. statement was added.

     3.3 版更變: `source_address' parameter was added.

 -- 類別: ftplib.FTP_TLS (host='', user='', passwd='', acct='',
          keyfile=None, certfile=None, context=None, timeout=None,
          source_address=None)

     A *note FTP: 2f1. subclass which adds TLS support to FTP as
     described in RFC 4217(3).  Connect as usual to port 21 implicitly
     securing the FTP control connection before authenticating.
     Securing the data connection requires the user to explicitly ask
     for it by calling the *note prot_p(): 2d13. method.  `context' is a
     *note ssl.SSLContext: 3e9. object which allows bundling SSL
     configuration options, certificates and private keys into a single
     (potentially long-lived) structure.  Please read *note Security
     considerations: 25b3. for best practices.

     `keyfile' and `certfile' are a legacy alternative to `context' –
     they can point to PEM-formatted private key and certificate chain
     files (respectively) for the SSL connection.

     3.2 版新加入.

     3.3 版更變: `source_address' parameter was added.

     3.4 版更變: The class now supports hostname check with *note
     ssl.SSLContext.check_hostname: 26ca. and `Server Name Indication'
     (see *note ssl.HAS_SNI: 26df.).

     3.6 版後已棄用: `keyfile' and `certfile' are deprecated in favor of
     `context'.  Please use *note ssl.SSLContext.load_cert_chain(): a96.
     instead, or let *note ssl.create_default_context(): 8c6. select the
     system’s trusted CA certificates for you.

     Here’s a sample session using the *note FTP_TLS: a08. class:

          >>> 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']

 -- 例外: ftplib.error_reply

     Exception raised when an unexpected reply is received from the
     server.

 -- 例外: ftplib.error_temp

     Exception raised when an error code signifying a temporary error
     (response codes in the range 400–499) is received.

 -- 例外: ftplib.error_perm

     Exception raised when an error code signifying a permanent error
     (response codes in the range 500–599) is received.

 -- 例外: ftplib.error_proto

     Exception raised when a reply is received from the server that does
     not fit the response specifications of the File Transfer Protocol,
     i.e.  begin with a digit in the range 1–5.

 -- Data: ftplib.all_errors

     The set of all exceptions (as a tuple) that methods of *note FTP:
     2f1. instances may raise as a result of problems with the FTP
     connection (as opposed to programming errors made by the caller).
     This set includes the four exceptions listed above as well as *note
     OSError: 1d4. and *note EOFError: c71.

也參考
......

Module *note netrc: bf.

     Parser for the ‘.netrc’ file format.  The file ‘.netrc’ is
     typically used by FTP clients to load user authentication
     information before prompting the user.

* Menu:

* FTP Objects::
* FTP_TLS Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/ftplib.py

   (2) https://tools.ietf.org/html/rfc959.html

   (3) https://tools.ietf.org/html/rfc4217.html


File: python.info,  Node: FTP Objects,  Next: FTP_TLS Objects,  Up: ftplib --- FTP protocol client

5.21.13.1 FTP Objects
.....................

Several methods are available in two flavors: one for handling text
files and another for binary files.  These are named for the command
which is used followed by ‘lines’ for the text version or ‘binary’ for
the binary version.

*note FTP: 2f1. instances have the following methods:

 -- 成員函式: FTP.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.

 -- 成員函式: FTP.connect (host='', port=0, timeout=None,
          source_address=None)

     Connect to the given host and port.  The default port number is
     ‘21’, as specified by the FTP protocol specification.  It is rarely
     needed to specify a different port number.  This function should be
     called only once for each instance; it should not be called at all
     if a host was given when the instance was created.  All other
     methods can only be used after a connection has been made.  The
     optional `timeout' parameter specifies a timeout in seconds for the
     connection attempt.  If no `timeout' is passed, the global default
     timeout setting will be used.  `source_address' is a 2-tuple
     ‘(host, port)’ for the socket to bind to as its source address
     before connecting.

     Raises an *note auditing event: e96. ‘ftplib.connect’ with
     arguments ‘self’, ‘host’, ‘port’.

     3.3 版更變: `source_address' parameter was added.

 -- 成員函式: FTP.getwelcome ()

     Return the welcome message sent by the server in reply to the
     initial connection.  (This message sometimes contains disclaimers
     or help information that may be relevant to the user.)

 -- 成員函式: FTP.login (user='anonymous', passwd='', acct='')

     Log in as the given `user'.  The `passwd' and `acct' parameters are
     optional and default to the empty string.  If no `user' is
     specified, it defaults to ‘'anonymous'’.  If `user' is
     ‘'anonymous'’, the default `passwd' is ‘'anonymous@'’.  This
     function should be called only once for each instance, after a
     connection has been established; it should not be called at all if
     a host and user were given when the instance was created.  Most FTP
     commands are only allowed after the client has logged in.  The
     `acct' parameter supplies "accounting information"; few systems
     implement this.

 -- 成員函式: FTP.abort ()

     Abort a file transfer that is in progress.  Using this does not
     always work, but it’s worth a try.

 -- 成員函式: FTP.sendcmd (cmd)

     Send a simple command string to the server and return the response
     string.

     Raises an *note auditing event: e96. ‘ftplib.sendcmd’ with
     arguments ‘self’, ‘cmd’.

 -- 成員函式: FTP.voidcmd (cmd)

     Send a simple command string to the server and handle the response.
     Return nothing if a response code corresponding to success (codes
     in the range 200–299) is received.  Raise *note error_reply: 2d14.
     otherwise.

     Raises an *note auditing event: e96. ‘ftplib.sendcmd’ with
     arguments ‘self’, ‘cmd’.

 -- 成員函式: FTP.retrbinary (cmd, callback, blocksize=8192, rest=None)

     Retrieve a file in binary transfer mode.  `cmd' should be an
     appropriate ‘RETR’ command: ‘'RETR filename'’.  The `callback'
     function is called for each block of data received, with a single
     bytes argument giving the data block.  The optional `blocksize'
     argument specifies the maximum chunk size to read on the low-level
     socket object created to do the actual transfer (which will also be
     the largest size of the data blocks passed to `callback').  A
     reasonable default is chosen.  `rest' means the same thing as in
     the *note transfercmd(): 2d23. method.

 -- 成員函式: FTP.retrlines (cmd, callback=None)

     Retrieve a file or directory listing in ASCII transfer mode.  `cmd'
     should be an appropriate ‘RETR’ command (see *note retrbinary():
     2d22.) or a command such as ‘LIST’ or ‘NLST’ (usually just the
     string ‘'LIST'’).  ‘LIST’ retrieves a list of files and information
     about those files.  ‘NLST’ retrieves a list of file names.  The
     `callback' function is called for each line with a string argument
     containing the line with the trailing CRLF stripped.  The default
     `callback' prints the line to ‘sys.stdout’.

 -- 成員函式: FTP.set_pasv (val)

     Enable "passive" mode if `val' is true, otherwise disable passive
     mode.  Passive mode is on by default.

 -- 成員函式: FTP.storbinary (cmd, fp, blocksize=8192, callback=None,
          rest=None)

     Store a file in binary transfer mode.  `cmd' should be an
     appropriate ‘STOR’ command: ‘"STOR filename"’.  `fp' is a *note
     file object: b47. (opened in binary mode) which is read until EOF
     using its ‘read()’ method in blocks of size `blocksize' to provide
     the data to be stored.  The `blocksize' argument defaults to 8192.
     `callback' is an optional single parameter callable that is called
     on each block of data after it is sent.  `rest' means the same
     thing as in the *note transfercmd(): 2d23. method.

     3.2 版更變: `rest' parameter added.

 -- 成員函式: FTP.storlines (cmd, fp, callback=None)

     Store a file in ASCII transfer mode.  `cmd' should be an
     appropriate ‘STOR’ command (see *note storbinary(): ca4.).  Lines
     are read until EOF from the *note file object: b47. `fp' (opened in
     binary mode) using its *note readline(): 1708. method to provide
     the data to be stored.  `callback' is an optional single parameter
     callable that is called on each line after it is sent.

 -- 成員函式: FTP.transfercmd (cmd, rest=None)

     Initiate a transfer over the data connection.  If the transfer is
     active, send an ‘EPRT’ or ‘PORT’ command and the transfer command
     specified by `cmd', and accept the connection.  If the server is
     passive, send an ‘EPSV’ or ‘PASV’ command, connect to it, and start
     the transfer command.  Either way, return the socket for the
     connection.

     If optional `rest' is given, a ‘REST’ command is sent to the
     server, passing `rest' as an argument.  `rest' is usually a byte
     offset into the requested file, telling the server to restart
     sending the file’s bytes at the requested offset, skipping over the
     initial bytes.  Note however that RFC 959(1) requires only that
     `rest' be a string containing characters in the printable range
     from ASCII code 33 to ASCII code 126.  The *note transfercmd():
     2d23. method, therefore, converts `rest' to a string, but no check
     is performed on the string’s contents.  If the server does not
     recognize the ‘REST’ command, an *note error_reply: 2d14. exception
     will be raised.  If this happens, simply call *note transfercmd():
     2d23. without a `rest' argument.

 -- 成員函式: FTP.ntransfercmd (cmd, rest=None)

     Like *note transfercmd(): 2d23, but returns a tuple of the data
     connection and the expected size of the data.  If the expected size
     could not be computed, ‘None’ will be returned as the expected
     size.  `cmd' and `rest' means the same thing as in *note
     transfercmd(): 2d23.

 -- 成員函式: FTP.mlsd (path="", facts=[])

     List a directory in a standardized format by using ‘MLSD’ command (
     RFC 3659(2)).  If `path' is omitted the current directory is
     assumed.  `facts' is a list of strings representing the type of
     information desired (e.g.  ‘["type", "size", "perm"]’).  Return a
     generator object yielding a tuple of two elements for every file
     found in path.  First element is the file name, the second one is a
     dictionary containing facts about the file name.  Content of this
     dictionary might be limited by the `facts' argument but server is
     not guaranteed to return all requested facts.

     3.3 版新加入.

 -- 成員函式: FTP.nlst (argument[, ...])

     Return a list of file names as returned by the ‘NLST’ command.  The
     optional `argument' is a directory to list (default is the current
     server directory).  Multiple arguments can be used to pass
     non-standard options to the ‘NLST’ command.

          備註: If your server supports the command, *note mlsd(): a0a.
          offers a better API.

 -- 成員函式: FTP.dir (argument[, ...])

     Produce a directory listing as returned by the ‘LIST’ command,
     printing it to standard output.  The optional `argument' is a
     directory to list (default is the current server directory).
     Multiple arguments can be used to pass non-standard options to the
     ‘LIST’ command.  If the last argument is a function, it is used as
     a `callback' function as for *note retrlines(): 2d24.; the default
     prints to ‘sys.stdout’.  This method returns ‘None’.

          備註: If your server supports the command, *note mlsd(): a0a.
          offers a better API.

 -- 成員函式: FTP.rename (fromname, toname)

     Rename file `fromname' on the server to `toname'.

 -- 成員函式: FTP.delete (filename)

     Remove the file named `filename' from the server.  If successful,
     returns the text of the response, otherwise raises *note
     error_perm: 2d16. on permission errors or *note error_reply: 2d14.
     on other errors.

 -- 成員函式: FTP.cwd (pathname)

     Set the current directory on the server.

 -- 成員函式: FTP.mkd (pathname)

     Create a new directory on the server.

 -- 成員函式: FTP.pwd ()

     Return the pathname of the current directory on the server.

 -- 成員函式: FTP.rmd (dirname)

     Remove the directory named `dirname' on the server.

 -- 成員函式: FTP.size (filename)

     Request the size of the file named `filename' on the server.  On
     success, the size of the file is returned as an integer, otherwise
     ‘None’ is returned.  Note that the ‘SIZE’ command is not
     standardized, but is supported by many common server
     implementations.

 -- 成員函式: FTP.quit ()

     Send a ‘QUIT’ command to the server and close the connection.  This
     is the "polite" way to close a connection, but it may raise an
     exception if the server responds with an error to the ‘QUIT’
     command.  This implies a call to the *note close(): 2d30. method
     which renders the *note FTP: 2f1. instance useless for subsequent
     calls (see below).

 -- 成員函式: FTP.close ()

     Close the connection unilaterally.  This should not be applied to
     an already closed connection such as after a successful call to
     *note quit(): 2d2f.  After this call the *note FTP: 2f1. instance
     should not be used any more (after a call to *note close(): 2d30.
     or *note quit(): 2d2f. you cannot reopen the connection by issuing
     another *note login(): 2d1e. method).

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc959.html

   (2) https://tools.ietf.org/html/rfc3659.html


File: python.info,  Node: FTP_TLS Objects,  Prev: FTP Objects,  Up: ftplib --- FTP protocol client

5.21.13.2 FTP_TLS Objects
.........................

*note FTP_TLS: a08. class inherits from *note FTP: 2f1, defining these
additional objects:

 -- 屬性: FTP_TLS.ssl_version

     The SSL version to use (defaults to *note ssl.PROTOCOL_SSLv23:
     26cf.).

 -- 成員函式: FTP_TLS.auth ()

     Set up a secure control connection by using TLS or SSL, depending
     on what is specified in the *note ssl_version: 2d32. attribute.

     3.4 版更變: The method now supports hostname check with *note
     ssl.SSLContext.check_hostname: 26ca. and `Server Name Indication'
     (see *note ssl.HAS_SNI: 26df.).

 -- 成員函式: FTP_TLS.ccc ()

     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.

     3.3 版新加入.

 -- 成員函式: FTP_TLS.prot_p ()

     Set up secure data connection.

 -- 成員函式: FTP_TLS.prot_c ()

     Set up clear text data connection.


File: python.info,  Node: poplib --- POP3 protocol client,  Next: imaplib --- IMAP4 protocol client,  Prev: ftplib --- FTP protocol client,  Up: Internet Protocols and Support

5.21.14 ‘poplib’ — POP3 protocol client
---------------------------------------

`Source code:' Lib/poplib.py(1)

__________________________________________________________________

This module defines a class, *note POP3: 2d37, which encapsulates a
connection to a POP3 server and implements the protocol as defined in
RFC 1939(2).  The *note POP3: 2d37. class supports both the minimal and
optional command sets from RFC 1939(3).  The *note POP3: 2d37. 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: bc6, 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: 610. class, as IMAP servers tend to be
better implemented.

The *note poplib: d1. 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).

     Raises an *note auditing event: e96. ‘poplib.connect’ with
     arguments ‘self’, ‘host’, ‘port’.

     All commands will raise an *note auditing event: e96.
     ‘poplib.putline’ with arguments ‘self’ and ‘line’, where ‘line’ is
     the bytes about to be sent to the remote host.

 -- 類別: poplib.POP3_SSL (host, port=POP3_SSL_PORT, keyfile=None,
          certfile=None, timeout=None, context=None)

     This is a subclass of *note POP3: 2d37. 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: 2d37. constructor.  `context' is an optional *note
     ssl.SSLContext: 3e9. object which allows bundling SSL configuration
     options, certificates and private keys into a single (potentially
     long-lived) structure.  Please read *note Security considerations:
     25b3. for best practices.

     `keyfile' and `certfile' are a legacy alternative to `context' -
     they can point to PEM-formatted private key and certificate chain
     files, respectively, for the SSL connection.

     Raises an *note auditing event: e96. ‘poplib.connect’ with
     arguments ‘self’, ‘host’, ‘port’.

     All commands will raise an *note auditing event: e96.
     ‘poplib.putline’ with arguments ‘self’ and ‘line’, where ‘line’ is
     the bytes about to be sent to the remote host.

     3.2 版更變: `context' parameter added.

     3.4 版更變: The class now supports hostname check with *note
     ssl.SSLContext.check_hostname: 26ca. and `Server Name Indication'
     (see *note ssl.HAS_SNI: 26df.).

     3.6 版後已棄用: `keyfile' and `certfile' are deprecated in favor of
     `context'.  Please use *note ssl.SSLContext.load_cert_chain(): a96.
     instead, or let *note ssl.create_default_context(): 8c6. select the
     system’s trusted CA certificates for you.

One exception is defined as an attribute of the *note poplib: d1.
module:

 -- 例外: poplib.error_proto

     Exception raised on any errors from this module (errors from *note
     socket: f0. module are not caught).  The reason for the exception
     is passed to the constructor as a string.

也參考
......

Module *note imaplib: 98.

     The standard Python IMAP module.

Frequently Asked Questions About 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 Objects::
* POP3 Example::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/poplib.py

   (2) https://tools.ietf.org/html/rfc1939.html

   (3) https://tools.ietf.org/html/rfc1939.html

   (4) https://tools.ietf.org/html/rfc2595.html

   (5) http://www.catb.org/~esr/fetchmail/fetchmail-FAQ.html


File: python.info,  Node: POP3 Objects,  Next: POP3 Example,  Up: poplib --- POP3 protocol client

5.21.14.1 POP3 Objects
......................

All POP3 commands are represented by methods of the same name, in
lower-case; most return the response text sent by the server.

An *note POP3: 2d37. 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 ‘quit()’ 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: b1c. 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: 3e9. object which
     allows bundling SSL configuration options, certificates and private
     keys into a single (potentially long-lived) structure.  Please read
     *note Security considerations: 25b3. for best practices.

     This method supports hostname checking via *note
     ssl.SSLContext.check_hostname: 26ca. and `Server Name Indication'
     (see *note ssl.HAS_SNI: 26df.).

     3.4 版新加入.

Instances of *note POP3_SSL: bc6. have no additional methods.  The
interface of this subclass is identical to its parent.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2449.html

   (2) https://tools.ietf.org/html/rfc6856.html

   (3) https://tools.ietf.org/html/rfc2595.html


File: python.info,  Node: POP3 Example,  Prev: POP3 Objects,  Up: poplib --- POP3 protocol client

5.21.14.2 POP3 Example
......................

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 protocol client,  Next: nntplib --- NNTP protocol client,  Prev: poplib --- POP3 protocol client,  Up: Internet Protocols and Support

5.21.15 ‘imaplib’ — IMAP4 protocol client
-----------------------------------------

`Source code:' Lib/imaplib.py(1)

__________________________________________________________________

This module defines three classes, *note IMAP4: 610, *note IMAP4_SSL:
a1c. and *note IMAP4_stream: 2d4c, 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.

Three classes are provided by the *note imaplib: 98. module, *note
IMAP4: 610. is the base class:

 -- 類別: imaplib.IMAP4 (host='', port=IMAP4_PORT)

     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 *note IMAP4: 610. class supports the *note with: 6ee.
     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: 6ee. statement was added.

Three exceptions are defined as attributes of the *note IMAP4: 610.
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: 2d4d.  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:
     2d4d.  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, keyfile=None,
          certfile=None, ssl_context=None)

     This is a subclass derived from *note IMAP4: 610. 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: 3e9. object which allows bundling SSL
     configuration options, certificates and private keys into a single
     (potentially long-lived) structure.  Please read *note Security
     considerations: 25b3. for best practices.

     `keyfile' and `certfile' are a legacy alternative to `ssl_context'
     - they can point to PEM-formatted private key and certificate chain
     files for the SSL connection.  Note that the `keyfile'/`certfile'
     parameters are mutually exclusive with `ssl_context', a *note
     ValueError: 1fc. is raised if `keyfile'/`certfile' is provided
     along with `ssl_context'.

     3.3 版更變: `ssl_context' parameter added.

     3.4 版更變: The class now supports hostname check with *note
     ssl.SSLContext.check_hostname: 26ca. and `Server Name Indication'
     (see *note ssl.HAS_SNI: 26df.).

     3.6 版後已棄用: `keyfile' and `certfile' are deprecated in favor of
     `ssl_context'.  Please use *note ssl.SSLContext.load_cert_chain():
     a96. instead, or let *note ssl.create_default_context(): 8c6.
     select the system’s trusted CA certificates for you.

The second subclass allows for connections created by a child process:

 -- 類別: imaplib.IMAP4_stream (command)

     This is a subclass derived from *note IMAP4: 610. 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: 59e. 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(): 322.), a 9-tuple representing local
     time an instance of *note time.struct_time: 59e. (as returned by
     *note time.localtime(): f52.), an aware instance of *note
     datetime.datetime: 195, 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 Objects::
* IMAP4 Example::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/imaplib.py

   (2) https://tools.ietf.org/html/rfc2060.html

   (3) https://tools.ietf.org/html/rfc1730.html


File: python.info,  Node: IMAP4 Objects,  Next: IMAP4 Example,  Up: imaplib --- IMAP4 protocol client

5.21.15.1 IMAP4 Objects
.......................

All IMAP4rev1 commands are represented by methods of the same name,
either upper-case or lower-case.

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: 610. 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(): 6ef. 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)

     Opens socket to `port' at `host'.  This method is implicitly called
     by the *note IMAP4: 610. constructor.  The connection objects
     established by this method will be used in the *note IMAP4.read():
     2d6d, *note IMAP4.readline(): 2d6e, *note IMAP4.send(): 2d6f, and
     *note IMAP4.shutdown(): 2d70. methods.  You may override this
     method.

     Raises an *note auditing event: e96. ‘imaplib.open’ with arguments
     ‘self’, ‘host’, ‘port’.

 -- 成員函式: 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(): 6ef. command.

     Example:

          # 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.

     Raises an *note auditing event: e96. ‘imaplib.send’ with arguments
     ‘self’, ‘data’.

 -- 成員函式: 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(): 2d67.  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: 3e9. object.  This will
     enable encryption on the IMAP connection.  Please read *note
     Security considerations: 25b3. for best practices.

     3.2 版新加入.

     3.4 版更變: The method now supports hostname check with *note
     ssl.SSLContext.check_hostname: 26ca. and `Server Name Indication'
     (see *note ssl.HAS_SNI: 26df.).

 -- 成員函式: 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 nonetheless 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.xatom (name[, ...])

     Allow simple extension commands notified by server in ‘CAPABILITY’
     response.

The following attributes are defined on instances of *note IMAP4: 610.:

 -- 屬性: 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(): 6ef. command is successfully issued for the
     ‘UTF8=ACCEPT’ capability.

     3.5 版新加入.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc5161.html

   (2) https://tools.ietf.org/html/rfc6855.html

   (3) https://tools.ietf.org/html/rfc6855.html

   (4) https://tools.ietf.org/html/rfc2342.html

   (5) https://tools.ietf.org/html/rfc2060.html

   (6) https://tools.ietf.org/html/rfc3501.html


File: python.info,  Node: IMAP4 Example,  Prev: IMAP4 Objects,  Up: imaplib --- IMAP4 protocol client

5.21.15.2 IMAP4 Example
.......................

Here is a minimal example (without error checking) that opens a mailbox
and retrieves and prints all messages:

     import getpass, imaplib

     M = imaplib.IMAP4()
     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: nntplib --- NNTP protocol client,  Next: smtplib --- SMTP protocol client,  Prev: imaplib --- IMAP4 protocol client,  Up: Internet Protocols and Support

5.21.16 ‘nntplib’ — NNTP protocol client
----------------------------------------

`Source code:' Lib/nntplib.py(1)

__________________________________________________________________

This module defines the class *note NNTP: a31. which implements the
client side of the Network News Transfer Protocol.  It can be used to
implement a news reader or poster, or automated news processors.  It is
compatible with RFC 3977(2) as well as the older RFC 977(3) and RFC
2980(4).

Here are two small examples of how it can be used.  To list some
statistics about a newsgroup and print the subjects of the last 10
articles:

     >>> s = nntplib.NNTP('news.gmane.io')
     >>> resp, count, first, last, name = s.group('gmane.comp.python.committers')
     >>> print('Group', name, 'has', count, 'articles, range', first, 'to', last)
     Group gmane.comp.python.committers has 1096 articles, range 1 to 1096
     >>> resp, overviews = s.over((last - 9, last))
     >>> for id, over in overviews:
     ...     print(id, nntplib.decode_header(over['subject']))
     ...
     1087 Re: Commit privileges for Łukasz Langa
     1088 Re: 3.2 alpha 2 freeze
     1089 Re: 3.2 alpha 2 freeze
     1090 Re: Commit privileges for Łukasz Langa
     1091 Re: Commit privileges for Łukasz Langa
     1092 Updated ssh key
     1093 Re: Updated ssh key
     1094 Re: Updated ssh key
     1095 Hello fellow committers!
     1096 Re: Hello fellow committers!
     >>> s.quit()
     '205 Bye!'

To post an article from a binary file (this assumes that the article has
valid headers, and that you have right to post on the particular
newsgroup):

     >>> s = nntplib.NNTP('news.gmane.io')
     >>> f = open('article.txt', 'rb')
     >>> s.post(f)
     '240 Article posted successfully.'
     >>> s.quit()
     '205 Bye!'

The module itself defines the following classes:

 -- 類別: nntplib.NNTP (host, port=119, user=None, password=None,
          readermode=None, usenetrc=False[, timeout])

     Return a new *note NNTP: a31. object, representing a connection to
     the NNTP server running on host `host', listening at port `port'.
     An optional `timeout' can be specified for the socket connection.
     If the optional `user' and `password' are provided, or if suitable
     credentials are present in ‘/.netrc’ and the optional flag
     `usenetrc' is true, the ‘AUTHINFO USER’ and ‘AUTHINFO PASS’
     commands are used to identify and authenticate the user to the
     server.  If the optional flag `readermode' is true, then a ‘mode
     reader’ command is sent before authentication is performed.  Reader
     mode is sometimes necessary if you are connecting to an NNTP server
     on the local machine and intend to call reader-specific commands,
     such as ‘group’.  If you get unexpected *note NNTPPermanentError:
     2d8a.s, you might need to set `readermode'.  The *note NNTP: a31.
     class supports the *note with: 6ee. statement to unconditionally
     consume *note OSError: 1d4. exceptions and to close the NNTP
     connection when done, e.g.:

          >>> from nntplib import NNTP
          >>> with NNTP('news.gmane.io') as n:
          ...     n.group('gmane.comp.python.committers')
          ...
          ('211 1755 1 1755 gmane.comp.python.committers', 1755, 1, 1755, 'gmane.comp.python.committers')
          >>>

     Raises an *note auditing event: e96. ‘nntplib.connect’ with
     arguments ‘self’, ‘host’, ‘port’.

     All commands will raise an *note auditing event: e96.
     ‘nntplib.putline’ with arguments ‘self’ and ‘line’, where ‘line’ is
     the bytes about to be sent to the remote host.

     3.2 版更變: `usenetrc' is now ‘False’ by default.

     3.3 版更變: Support for the *note with: 6ee. statement was added.

 -- 類別: nntplib.NNTP_SSL (host, port=563, user=None, password=None,
          ssl_context=None, readermode=None, usenetrc=False[, timeout])

     Return a new *note NNTP_SSL: baa. object, representing an encrypted
     connection to the NNTP server running on host `host', listening at
     port `port'.  *note NNTP_SSL: baa. objects have the same methods as
     *note NNTP: a31. objects.  If `port' is omitted, port 563 (NNTPS)
     is used.  `ssl_context' is also optional, and is a *note
     SSLContext: 3e9. object.  Please read *note Security
     considerations: 25b3. for best practices.  All other parameters
     behave the same as for *note NNTP: a31.

     Note that SSL-on-563 is discouraged per RFC 4642(5), in favor of
     STARTTLS as described below.  However, some servers only support
     the former.

     Raises an *note auditing event: e96. ‘nntplib.connect’ with
     arguments ‘self’, ‘host’, ‘port’.

     All commands will raise an *note auditing event: e96.
     ‘nntplib.putline’ with arguments ‘self’ and ‘line’, where ‘line’ is
     the bytes about to be sent to the remote host.

     3.2 版新加入.

     3.4 版更變: The class now supports hostname check with *note
     ssl.SSLContext.check_hostname: 26ca. and `Server Name Indication'
     (see *note ssl.HAS_SNI: 26df.).

 -- 例外: nntplib.NNTPError

     Derived from the standard exception *note Exception: 1aa, this is
     the base class for all exceptions raised by the *note nntplib: c1.
     module.  Instances of this class have the following attribute:

      -- 屬性: response

          The response of the server if available, as a *note str: 335.
          object.

 -- 例外: nntplib.NNTPReplyError

     Exception raised when an unexpected reply is received from the
     server.

 -- 例外: nntplib.NNTPTemporaryError

     Exception raised when a response code in the range 400–499 is
     received.

 -- 例外: nntplib.NNTPPermanentError

     Exception raised when a response code in the range 500–599 is
     received.

 -- 例外: nntplib.NNTPProtocolError

     Exception raised when a reply is received from the server that does
     not begin with a digit in the range 1–5.

 -- 例外: nntplib.NNTPDataError

     Exception raised when there is some error in the response data.

* Menu:

* NNTP Objects::
* Utility functions: Utility functions<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/nntplib.py

   (2) https://tools.ietf.org/html/rfc3977.html

   (3) https://tools.ietf.org/html/rfc977.html

   (4) https://tools.ietf.org/html/rfc2980.html

   (5) https://tools.ietf.org/html/rfc4642.html


File: python.info,  Node: NNTP Objects,  Next: Utility functions<2>,  Up: nntplib --- NNTP protocol client

5.21.16.1 NNTP Objects
......................

When connected, *note NNTP: a31. and *note NNTP_SSL: baa. objects
support the following methods and attributes.

* Menu:

* Attributes::
* Methods: Methods<3>.


File: python.info,  Node: Attributes,  Next: Methods<3>,  Up: NNTP Objects

5.21.16.2 Attributes
....................

 -- 屬性: NNTP.nntp_version

     An integer representing the version of the NNTP protocol supported
     by the server.  In practice, this should be ‘2’ for servers
     advertising RFC 3977(1) compliance and ‘1’ for others.

     3.2 版新加入.

 -- 屬性: NNTP.nntp_implementation

     A string describing the software name and version of the NNTP
     server, or *note None: 158. if not advertised by the server.

     3.2 版新加入.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc3977.html


File: python.info,  Node: Methods<3>,  Prev: Attributes,  Up: NNTP Objects

5.21.16.3 Methods
.................

The `response' that is returned as the first item in the return tuple of
almost all methods is the server’s response: a string beginning with a
three-digit code.  If the server’s response indicates an error, the
method raises one of the above exceptions.

Many of the following methods take an optional keyword-only argument
`file'.  When the `file' argument is supplied, it must be either a *note
file object: b47. opened for binary writing, or the name of an on-disk
file to be written to.  The method will then write any data returned by
the server (except for the response line and the terminating dot) to the
file; any list of lines, tuples or objects that the method normally
returns will be empty.

3.2 版更變: Many of the following methods have been reworked and fixed,
which makes them incompatible with their 3.1 counterparts.

 -- 成員函式: NNTP.quit ()

     Send a ‘QUIT’ command and close the connection.  Once this method
     has been called, no other methods of the NNTP object should be
     called.

 -- 成員函式: NNTP.getwelcome ()

     Return the welcome message sent by the server in reply to the
     initial connection.  (This message sometimes contains disclaimers
     or help information that may be relevant to the user.)

 -- 成員函式: NNTP.getcapabilities ()

     Return the RFC 3977(1) capabilities advertised by the server, as a
     *note dict: 1b9. instance mapping capability names to (possibly
     empty) lists of values.  On legacy servers which don’t understand
     the ‘CAPABILITIES’ command, an empty dictionary is returned
     instead.

          >>> s = NNTP('news.gmane.io')
          >>> 'POST' in s.getcapabilities()
          True

     3.2 版新加入.

 -- 成員函式: NNTP.login (user=None, password=None, usenetrc=True)

     Send ‘AUTHINFO’ commands with the user name and password.  If
     `user' and `password' are ‘None’ and `usenetrc' is true,
     credentials from ‘~/.netrc’ will be used if possible.

     Unless intentionally delayed, login is normally performed during
     the *note NNTP: a31. object initialization and separately calling
     this function is unnecessary.  To force authentication to be
     delayed, you must not set `user' or `password' when creating the
     object, and must set `usenetrc' to False.

     3.2 版新加入.

 -- 成員函式: NNTP.starttls (context=None)

     Send a ‘STARTTLS’ command.  This will enable encryption on the NNTP
     connection.  The `context' argument is optional and should be a
     *note ssl.SSLContext: 3e9. object.  Please read *note Security
     considerations: 25b3. for best practices.

     Note that this may not be done after authentication information has
     been transmitted, and authentication occurs by default if possible
     during a *note NNTP: a31. object initialization.  See *note
     NNTP.login(): 2d9a. for information on suppressing this behavior.

     3.2 版新加入.

     3.4 版更變: The method now supports hostname check with *note
     ssl.SSLContext.check_hostname: 26ca. and `Server Name Indication'
     (see *note ssl.HAS_SNI: 26df.).

 -- 成員函式: NNTP.newgroups (date, *, file=None)

     Send a ‘NEWGROUPS’ command.  The `date' argument should be a *note
     datetime.date: 194. or *note datetime.datetime: 195. object.
     Return a pair ‘(response, groups)’ where `groups' is a list
     representing the groups that are new since the given `date'.  If
     `file' is supplied, though, then `groups' will be empty.

          >>> from datetime import date, timedelta
          >>> resp, groups = s.newgroups(date.today() - timedelta(days=3))
          >>> len(groups)
          85
          >>> groups[0]
          GroupInfo(group='gmane.network.tor.devel', last='4', first='1', flag='m')

 -- 成員函式: NNTP.newnews (group, date, *, file=None)

     Send a ‘NEWNEWS’ command.  Here, `group' is a group name or ‘'*'’,
     and `date' has the same meaning as for *note newgroups(): 2d9b.
     Return a pair ‘(response, articles)’ where `articles' is a list of
     message ids.

     This command is frequently disabled by NNTP server administrators.

 -- 成員函式: NNTP.list (group_pattern=None, *, file=None)

     Send a ‘LIST’ or ‘LIST ACTIVE’ command.  Return a pair ‘(response,
     list)’ where `list' is a list of tuples representing all the groups
     available from this NNTP server, optionally matching the pattern
     string `group_pattern'.  Each tuple has the form ‘(group, last,
     first, flag)’, where `group' is a group name, `last' and `first'
     are the last and first article numbers, and `flag' usually takes
     one of these values:

        * ‘y’: Local postings and articles from peers are allowed.

        * ‘m’: The group is moderated and all postings must be approved.

        * ‘n’: No local postings are allowed, only articles from peers.

        * ‘j’: Articles from peers are filed in the junk group instead.

        * ‘x’: No local postings, and articles from peers are ignored.

        * ‘=foo.bar’: Articles are filed in the ‘foo.bar’ group instead.

     If `flag' has another value, then the status of the newsgroup
     should be considered unknown.

     This command can return very large results, especially if
     `group_pattern' is not specified.  It is best to cache the results
     offline unless you really need to refresh them.

     3.2 版更變: `group_pattern' was added.

 -- 成員函式: NNTP.descriptions (grouppattern)

     Send a ‘LIST NEWSGROUPS’ command, where `grouppattern' is a wildmat
     string as specified in RFC 3977(2) (it’s essentially the same as
     DOS or UNIX shell wildcard strings).  Return a pair ‘(response,
     descriptions)’, where `descriptions' is a dictionary mapping group
     names to textual descriptions.

          >>> resp, descs = s.descriptions('gmane.comp.python.*')
          >>> len(descs)
          295
          >>> descs.popitem()
          ('gmane.comp.python.bio.general', 'BioPython discussion list (Moderated)')

 -- 成員函式: NNTP.description (group)

     Get a description for a single group `group'.  If more than one
     group matches (if ’group’ is a real wildmat string), return the
     first match.  If no group matches, return an empty string.

     This elides the response code from the server.  If the response
     code is needed, use *note descriptions(): 2d9e.

 -- 成員函式: NNTP.group (name)

     Send a ‘GROUP’ command, where `name' is the group name.  The group
     is selected as the current group, if it exists.  Return a tuple
     ‘(response, count, first, last, name)’ where `count' is the
     (estimated) number of articles in the group, `first' is the first
     article number in the group, `last' is the last article number in
     the group, and `name' is the group name.

 -- 成員函式: NNTP.over (message_spec, *, file=None)

     Send an ‘OVER’ command, or an ‘XOVER’ command on legacy servers.
     `message_spec' can be either a string representing a message id, or
     a ‘(first, last)’ tuple of numbers indicating a range of articles
     in the current group, or a ‘(first, None)’ tuple indicating a range
     of articles starting from `first' to the last article in the
     current group, or *note None: 158. to select the current article in
     the current group.

     Return a pair ‘(response, overviews)’.  `overviews' is a list of
     ‘(article_number, overview)’ tuples, one for each article selected
     by `message_spec'.  Each `overview' is a dictionary with the same
     number of items, but this number depends on the server.  These
     items are either message headers (the key is then the lower-cased
     header name) or metadata items (the key is then the metadata name
     prepended with ‘":"’).  The following items are guaranteed to be
     present by the NNTP specification:

        * the ‘subject’, ‘from’, ‘date’, ‘message-id’ and ‘references’
          headers

        * the ‘:bytes’ metadata: the number of bytes in the entire raw
          article (including headers and body)

        * the ‘:lines’ metadata: the number of lines in the article body

     The value of each item is either a string, or *note None: 158. if
     not present.

     It is advisable to use the *note decode_header(): 2da2. function on
     header values when they may contain non-ASCII characters:

          >>> _, _, first, last, _ = s.group('gmane.comp.python.devel')
          >>> resp, overviews = s.over((last, last))
          >>> art_num, over = overviews[0]
          >>> art_num
          117216
          >>> list(over.keys())
          ['xref', 'from', ':lines', ':bytes', 'references', 'date', 'message-id', 'subject']
          >>> over['from']
          '=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?= <martin@v.loewis.de>'
          >>> nntplib.decode_header(over['from'])
          '"Martin v. Löwis" <martin@v.loewis.de>'

     3.2 版新加入.

 -- 成員函式: NNTP.help (*, file=None)

     Send a ‘HELP’ command.  Return a pair ‘(response, list)’ where
     `list' is a list of help strings.

 -- 成員函式: NNTP.stat (message_spec=None)

     Send a ‘STAT’ command, where `message_spec' is either a message id
     (enclosed in ‘'<'’ and ‘'>'’) or an article number in the current
     group.  If `message_spec' is omitted or *note None: 158, the
     current article in the current group is considered.  Return a
     triple ‘(response, number, id)’ where `number' is the article
     number and `id' is the message id.

          >>> _, _, first, last, _ = s.group('gmane.comp.python.devel')
          >>> resp, number, message_id = s.stat(first)
          >>> number, message_id
          (9099, '<20030112190404.GE29873@epoch.metaslash.com>')

 -- 成員函式: NNTP.next ()

     Send a ‘NEXT’ command.  Return as for *note stat(): 2da4.

 -- 成員函式: NNTP.last ()

     Send a ‘LAST’ command.  Return as for *note stat(): 2da4.

 -- 成員函式: NNTP.article (message_spec=None, *, file=None)

     Send an ‘ARTICLE’ command, where `message_spec' has the same
     meaning as for *note stat(): 2da4.  Return a tuple ‘(response,
     info)’ where `info' is a *note namedtuple: 1b8. with three
     attributes `number', `message_id' and `lines' (in that order).
     `number' is the article number in the group (or 0 if the
     information is not available), `message_id' the message id as a
     string, and `lines' a list of lines (without terminating newlines)
     comprising the raw message including headers and body.

          >>> resp, info = s.article('<20030112190404.GE29873@epoch.metaslash.com>')
          >>> info.number
          0
          >>> info.message_id
          '<20030112190404.GE29873@epoch.metaslash.com>'
          >>> len(info.lines)
          65
          >>> info.lines[0]
          b'Path: main.gmane.org!not-for-mail'
          >>> info.lines[1]
          b'From: Neal Norwitz <neal@metaslash.com>'
          >>> info.lines[-3:]
          [b'There is a patch for 2.3 as well as 2.2.', b'', b'Neal']

 -- 成員函式: NNTP.head (message_spec=None, *, file=None)

     Same as *note article(): 2da7, but sends a ‘HEAD’ command.  The
     `lines' returned (or written to `file') will only contain the
     message headers, not the body.

 -- 成員函式: NNTP.body (message_spec=None, *, file=None)

     Same as *note article(): 2da7, but sends a ‘BODY’ command.  The
     `lines' returned (or written to `file') will only contain the
     message body, not the headers.

 -- 成員函式: NNTP.post (data)

     Post an article using the ‘POST’ command.  The `data' argument is
     either a *note file object: b47. opened for binary reading, or any
     iterable of bytes objects (representing raw lines of the article to
     be posted).  It should represent a well-formed news article,
     including the required headers.  The *note post(): 2daa. method
     automatically escapes lines beginning with ‘.’ and appends the
     termination line.

     If the method succeeds, the server’s response is returned.  If the
     server refuses posting, a *note NNTPReplyError: 2d8d. is raised.

 -- 成員函式: NNTP.ihave (message_id, data)

     Send an ‘IHAVE’ command.  `message_id' is the id of the message to
     send to the server (enclosed in ‘'<'’ and ‘'>'’).  The `data'
     parameter and the return value are the same as for *note post():
     2daa.

 -- 成員函式: NNTP.date ()

     Return a pair ‘(response, date)’.  `date' is a *note datetime: 195.
     object containing the current date and time of the server.

 -- 成員函式: NNTP.slave ()

     Send a ‘SLAVE’ command.  Return the server’s `response'.

 -- 成員函式: NNTP.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 or response.  A value
     of ‘2’ or higher produces the maximum amount of debugging output,
     logging each line sent and received on the connection (including
     message text).

The following are optional NNTP extensions defined in RFC 2980(3).  Some
of them have been superseded by newer commands in RFC 3977(4).

 -- 成員函式: NNTP.xhdr (hdr, str, *, file=None)

     Send an ‘XHDR’ command.  The `hdr' argument is a header keyword,
     e.g.  ‘'subject'’.  The `str' argument should have the form
     ‘'first-last'’ where `first' and `last' are the first and last
     article numbers to search.  Return a pair ‘(response, list)’, where
     `list' is a list of pairs ‘(id, text)’, where `id' is an article
     number (as a string) and `text' is the text of the requested header
     for that article.  If the `file' parameter is supplied, then the
     output of the ‘XHDR’ command is stored in a file.  If `file' is a
     string, then the method will open a file with that name, write to
     it then close it.  If `file' is a *note file object: b47, then it
     will start calling ‘write()’ on it to store the lines of the
     command output.  If `file' is supplied, then the returned `list' is
     an empty list.

 -- 成員函式: NNTP.xover (start, end, *, file=None)

     Send an ‘XOVER’ command.  `start' and `end' are article numbers
     delimiting the range of articles to select.  The return value is
     the same of for *note over(): 2da1.  It is recommended to use *note
     over(): 2da1. instead, since it will automatically use the newer
     ‘OVER’ command if available.

 -- 成員函式: NNTP.xpath (id)

     Return a pair ‘(resp, path)’, where `path' is the directory path to
     the article with message ID `id'.  Most of the time, this extension
     is not enabled by NNTP server administrators.

     3.3 版後已棄用: The XPATH extension is not actively used.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc3977.html

   (2) https://tools.ietf.org/html/rfc3977.html

   (3) https://tools.ietf.org/html/rfc2980.html

   (4) https://tools.ietf.org/html/rfc3977.html


File: python.info,  Node: Utility functions<2>,  Prev: NNTP Objects,  Up: nntplib --- NNTP protocol client

5.21.16.4 Utility functions
...........................

The module also defines the following utility function:

 -- 函式: nntplib.decode_header (header_str)

     Decode a header value, un-escaping any escaped non-ASCII
     characters.  `header_str' must be a *note str: 335. object.  The
     unescaped value is returned.  Using this function is recommended to
     display some headers in a human readable form:

          >>> decode_header("Some subject")
          'Some subject'
          >>> decode_header("=?ISO-8859-15?Q?D=E9buter_en_Python?=")
          'Débuter en Python'
          >>> decode_header("Re: =?UTF-8?B?cHJvYmzDqG1lIGRlIG1hdHJpY2U=?=")
          'Re: problème de matrice'


File: python.info,  Node: smtplib --- SMTP protocol client,  Next: smtpd --- SMTP Server,  Prev: nntplib --- NNTP protocol client,  Up: Internet Protocols and Support

5.21.17 ‘smtplib’ — SMTP protocol client
----------------------------------------

`Source code:' Lib/smtplib.py(1)

__________________________________________________________________

The *note smtplib: ee. 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).

 -- 類別: smtplib.SMTP (host='', port=0, local_hostname=None[, timeout],
          source_address=None)

     An *note SMTP: a86. 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(): ee0. 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(): 2690.  If the *note connect(): ee0. call returns
     anything other than a success code, an *note SMTPConnectError:
     2db5. 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 socket.timeout: c13. 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(): 749, and *note SMTP.quit(): 2db6. methods.  An
     example is included below.

     The *note SMTP: a86. class supports the *note with: 6ee. 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')
          >>>

     All commands will raise an *note auditing event: e96.
     ‘smtplib.SMTP.send’ with arguments ‘self’ and ‘data’, where ‘data’
     is the bytes about to be sent to the remote host.

     3.3 版更變: Support for the *note with: 6ee. statement was added.

     3.3 版更變: source_address argument was added.

     3.5 版新加入: The SMTPUTF8 extension ( RFC 6531(4)) is now
     supported.

 -- 類別: smtplib.SMTP_SSL (host='', port=0, local_hostname=None,
          keyfile=None, certfile=None[, timeout], context=None,
          source_address=None)

     An *note SMTP_SSL: a87. instance behaves exactly the same as
     instances of *note SMTP: a86.  *note SMTP_SSL: a87. 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: a86. class.  `context', also
     optional, can contain a *note SSLContext: 3e9. and allows
     configuring various aspects of the secure connection.  Please read
     *note Security considerations: 25b3. for best practices.

     `keyfile' and `certfile' are a legacy alternative to `context', and
     can point to a PEM formatted private key and certificate chain file
     for the SSL connection.

     3.3 版更變: `context' was added.

     3.3 版更變: source_address argument was added.

     3.4 版更變: The class now supports hostname check with *note
     ssl.SSLContext.check_hostname: 26ca. and `Server Name Indication'
     (see *note ssl.HAS_SNI: 26df.).

     3.6 版後已棄用: `keyfile' and `certfile' are deprecated in favor of
     `context'.  Please use *note ssl.SSLContext.load_cert_chain(): a96.
     instead, or let *note ssl.create_default_context(): 8c6. select the
     system’s trusted CA certificates for you.

 -- 類別: smtplib.LMTP (host='', port=LMTP_PORT, local_hostname=None,
          source_address=None)

     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: a86. 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.

A nice selection of exceptions is defined as well:

 -- 例外: smtplib.SMTPException

     Subclass of *note OSError: 1d4. that is the base exception class
     for all the other exceptions provided by this module.

     3.4 版更變: SMTPException became subclass of *note OSError: 1d4.

 -- 例外: smtplib.SMTPServerDisconnected

     This exception is raised when the server unexpectedly disconnects,
     or when an attempt is made to use the *note SMTP: a86. 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: 2db8. 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(): 749.
     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 Objects::
* SMTP Example::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/smtplib.py

   (2) https://tools.ietf.org/html/rfc821.html

   (3) https://tools.ietf.org/html/rfc1869.html

   (4) https://tools.ietf.org/html/rfc6531.html

   (5) https://tools.ietf.org/html/rfc821.html

   (6) https://tools.ietf.org/html/rfc1869.html


File: python.info,  Node: SMTP Objects,  Next: SMTP Example,  Up: smtplib --- SMTP protocol client

5.21.17.1 SMTP Objects
......................

An *note SMTP: a86. 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: 2db7. 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.

     Raises an *note auditing event: e96. ‘smtplib.connect’ with
     arguments ‘self’, ‘host’, ‘port’.

 -- 成員函式: 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():
     749. 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(): 2dc3.  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(): 2dc3. before sending mail,
     it should not be necessary to call this method explicitly.  It will
     be implicitly called by *note sendmail(): 749. when necessary.

 -- 成員函式: SMTP.ehlo_or_helo_if_needed ()

     This method calls *note ehlo(): 2dc2. and/or *note helo(): 2dc1. if
     there has been no previous ‘EHLO’ or ‘HELO’ command this session.
     It tries ESMTP ‘EHLO’ first.

     *note SMTPHeloError: 2dbc.

          The server didn’t reply properly to the ‘HELO’ greeting.

 -- 成員函式: SMTP.has_extn (name)

     Return *note True: 49e. if `name' is in the set of SMTP service
     extensions returned by the server, *note False: 38d. 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: 2dbc.

          The server didn’t reply properly to the ‘HELO’ greeting.

     *note SMTPAuthenticationError: 2dbd.

          The server didn’t accept the username/password combination.

     *note SMTPNotSupportedError: f72.

          The ‘AUTH’ command is not supported by the server.

     *note SMTPException: 8bc.

          No suitable authentication method was found.

     Each of the authentication methods supported by *note smtplib: ee.
     are tried in turn if they are advertised as supported by the
     server.  See *note auth(): 747. for a list of supported
     authentication methods.  `initial_response_ok' is passed through to
     *note auth(): 747.

     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: f72. 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(): 2dc6. 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: ee.

     3.5 版新加入.

 -- 成員函式: SMTP.starttls (keyfile=None, certfile=None, 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(): 2dc2. again.

     If `keyfile' and `certfile' are provided, they are used to create
     an *note ssl.SSLContext: 3e9.

     Optional `context' parameter is an *note ssl.SSLContext: 3e9.
     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.6 版後已棄用: `keyfile' and `certfile' are deprecated in favor of
     `context'.  Please use *note ssl.SSLContext.load_cert_chain(): a96.
     instead, or let *note ssl.create_default_context(): 8c6. select the
     system’s trusted CA certificates for you.

     *note SMTPHeloError: 2dbc.

          The server didn’t reply properly to the ‘HELO’ greeting.

     *note SMTPNotSupportedError: f72.

          The server does not support the STARTTLS extension.

     *note RuntimeError: 2bb.

          SSL/TLS support is not available to your Python interpreter.

     3.3 版更變: `context' was added.

     3.4 版更變: The method now supports hostname check with
     ‘SSLContext.check_hostname’ and `Server Name Indicator' (see *note
     HAS_SNI: 26df.).

     3.5 版更變: The error raised for lack of STARTTLS support is now
     the *note SMTPNotSupportedError: f72. subclass instead of the base
     *note SMTPException: 8bc.

 -- 成員函式: 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: 2dba.

          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: 2dbc.

          The server didn’t reply properly to the ‘HELO’ greeting.

     *note SMTPSenderRefused: 2db9.

          The server didn’t accept the `from_addr'.

     *note SMTPDataError: 2dbb.

          The server replied with an unexpected error code (other than a
          refusal of a recipient).

     *note SMTPNotSupportedError: f72.

          ‘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: f72. 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(): 749.
     with the message represented by an *note email.message.Message:
     546. object.  The arguments have the same meaning as for *note
     sendmail(): 749, 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: 1fc. is
     raised, since there is no way to unambiguously detect the most
     recent set of ‘Resent-’ headers.

     ‘send_message’ serializes `msg' using *note BytesGenerator: b52.
     with ‘\r\n’ as the `linesep', and calls *note sendmail(): 749. 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: 75. with the *note
     utf8: 6d7. 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://tools.ietf.org/html/rfc822.html

   (2) https://tools.ietf.org/html/rfc4954.html

   (3) https://tools.ietf.org/html/rfc4954.html

   (4) https://tools.ietf.org/html/rfc822.html

   (5) https://tools.ietf.org/html/rfc822.html

   (6) https://tools.ietf.org/html/rfc5322.html


File: python.info,  Node: SMTP Example,  Prev: SMTP Objects,  Up: smtplib --- SMTP protocol client

5.21.17.2 SMTP Example
......................

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(prompt):
         return input(prompt).strip()

     fromaddr = prompt("From: ")
     toaddrs  = prompt("To: ").split()
     print("Enter message, end with ^D (Unix) or ^Z (Windows):")

     # Add the From: and To: headers at the start!
     msg = ("From: %s\r\nTo: %s\r\n\r\n"
            % (fromaddr, ", ".join(toaddrs)))
     while True:
         try:
             line = input()
         except EOFError:
             break
         if not line:
             break
         msg = msg + line

     print("Message length is", len(msg))

     server = smtplib.SMTP('localhost')
     server.set_debuglevel(1)
     server.sendmail(fromaddr, toaddrs, msg)
     server.quit()

     備註: In general, you will want to use the *note email: 69.
     package’s features to construct an email message, which you can
     then send via *note send_message(): 74a.; see *note email;
     Examples: 84a.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc822.html


File: python.info,  Node: smtpd --- SMTP Server,  Next: telnetlib --- Telnet client,  Prev: smtplib --- SMTP protocol client,  Up: Internet Protocols and Support

5.21.18 ‘smtpd’ — SMTP Server
-----------------------------

`Source code:' Lib/smtpd.py(1)

__________________________________________________________________

This module offers several classes to implement SMTP (email) servers.

也參考
......

The aiosmtpd(2) package is a recommended replacement for this module.
It is based on *note asyncio: a. and provides a more straightforward
API. *note smtpd: ed. should be considered deprecated.

Several server implementations are present; one is a generic do-nothing
implementation, which can be overridden, while the other two offer
specific mail-sending strategies.

Additionally the SMTPChannel may be extended to implement very specific
interaction behaviour with SMTP clients.

The code supports RFC 5321(3), plus the RFC 1870(4) SIZE and RFC 6531(5)
SMTPUTF8 extensions.

* Menu:

* SMTPServer Objects::
* DebuggingServer Objects::
* PureProxy Objects::
* MailmanProxy Objects::
* SMTPChannel Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/smtpd.py

   (2) http://aiosmtpd.readthedocs.io/

   (3) https://tools.ietf.org/html/rfc5321.html

   (4) https://tools.ietf.org/html/rfc1870.html

   (5) https://tools.ietf.org/html/rfc6531.html


File: python.info,  Node: SMTPServer Objects,  Next: DebuggingServer Objects,  Up: smtpd --- SMTP Server

5.21.18.1 SMTPServer Objects
............................

 -- 類別: smtpd.SMTPServer (localaddr, remoteaddr,
          data_size_limit=33554432, map=None, enable_SMTPUTF8=False,
          decode_data=False)

     Create a new *note SMTPServer: 607. object, which binds to local
     address `localaddr'.  It will treat `remoteaddr' as an upstream
     SMTP relayer.  Both `localaddr' and `remoteaddr' should be a *note
     (host, port): 266b. tuple.  The object inherits from *note
     asyncore.dispatcher: bc8, and so will insert itself into *note
     asyncore: b.’s event loop on instantiation.

     `data_size_limit' specifies the maximum number of bytes that will
     be accepted in a ‘DATA’ command.  A value of ‘None’ or ‘0’ means no
     limit.

     `map' is the socket map to use for connections (an initially empty
     dictionary is a suitable value).  If not specified the *note
     asyncore: b. global socket map is used.

     `enable_SMTPUTF8' determines whether the ‘SMTPUTF8’ extension (as
     defined in RFC 6531(1)) should be enabled.  The default is ‘False’.
     When ‘True’, ‘SMTPUTF8’ is accepted as a parameter to the ‘MAIL’
     command and when present is passed to *note process_message(): 608.
     in the ‘kwargs['mail_options']’ list.  `decode_data' and
     `enable_SMTPUTF8' cannot be set to ‘True’ at the same time.

     `decode_data' specifies whether the data portion of the SMTP
     transaction should be decoded using UTF-8.  When `decode_data' is
     ‘False’ (the default), the server advertises the ‘8BITMIME’
     extension ( RFC 6152(2)), accepts the ‘BODY=8BITMIME’ parameter to
     the ‘MAIL’ command, and when present passes it to *note
     process_message(): 608. in the ‘kwargs['mail_options']’ list.
     `decode_data' and `enable_SMTPUTF8' cannot be set to ‘True’ at the
     same time.

      -- 成員函式: process_message (peer, mailfrom, rcpttos, data,
               **kwargs)

          Raise a *note NotImplementedError: 613. exception.  Override
          this in subclasses to do something useful with this message.
          Whatever was passed in the constructor as `remoteaddr' will be
          available as the ‘_remoteaddr’ attribute.  `peer' is the
          remote host’s address, `mailfrom' is the envelope originator,
          `rcpttos' are the envelope recipients and `data' is a string
          containing the contents of the e-mail (which should be in RFC
          5321(3) format).

          If the `decode_data' constructor keyword is set to ‘True’, the
          `data' argument will be a unicode string.  If it is set to
          ‘False’, it will be a bytes object.

          `kwargs' is a dictionary containing additional information.
          It is empty if ‘decode_data=True’ was given as an init
          argument, otherwise it contains the following keys:

               `mail_options':

                    a list of all received parameters to the ‘MAIL’
                    command (the elements are uppercase strings;
                    example: ‘['BODY=8BITMIME', 'SMTPUTF8']’).

               `rcpt_options':

                    same as `mail_options' but for the ‘RCPT’ command.
                    Currently no ‘RCPT TO’ options are supported, so for
                    now this will always be an empty list.

          Implementations of ‘process_message’ should use the ‘**kwargs’
          signature to accept arbitrary keyword arguments, since future
          feature enhancements may add keys to the kwargs dictionary.

          Return ‘None’ to request a normal ‘250 Ok’ response; otherwise
          return the desired response string in RFC 5321(4) format.

      -- 屬性: channel_class

          Override this in subclasses to use a custom *note SMTPChannel:
          606. for managing SMTP clients.

     3.4 版新加入: The `map' constructor argument.

     3.5 版更變: `localaddr' and `remoteaddr' may now contain IPv6
     addresses.

     3.5 版新加入: The `decode_data' and `enable_SMTPUTF8' constructor
     parameters, and the `kwargs' parameter to *note process_message():
     608. when `decode_data' is ‘False’.

     3.6 版更變: `decode_data' is now ‘False’ by default.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc6531.html

   (2) https://tools.ietf.org/html/rfc6152.html

   (3) https://tools.ietf.org/html/rfc5321.html

   (4) https://tools.ietf.org/html/rfc5321.html


File: python.info,  Node: DebuggingServer Objects,  Next: PureProxy Objects,  Prev: SMTPServer Objects,  Up: smtpd --- SMTP Server

5.21.18.2 DebuggingServer Objects
.................................

 -- 類別: smtpd.DebuggingServer (localaddr, remoteaddr)

     Create a new debugging server.  Arguments are as per *note
     SMTPServer: 607.  Messages will be discarded, and printed on
     stdout.


File: python.info,  Node: PureProxy Objects,  Next: MailmanProxy Objects,  Prev: DebuggingServer Objects,  Up: smtpd --- SMTP Server

5.21.18.3 PureProxy Objects
...........................

 -- 類別: smtpd.PureProxy (localaddr, remoteaddr)

     Create a new pure proxy server.  Arguments are as per *note
     SMTPServer: 607.  Everything will be relayed to `remoteaddr'.  Note
     that running this has a good chance to make you into an open relay,
     so please be careful.


File: python.info,  Node: MailmanProxy Objects,  Next: SMTPChannel Objects,  Prev: PureProxy Objects,  Up: smtpd --- SMTP Server

5.21.18.4 MailmanProxy Objects
..............................

 -- 類別: smtpd.MailmanProxy (localaddr, remoteaddr)

     Create a new pure proxy server.  Arguments are as per *note
     SMTPServer: 607.  Everything will be relayed to `remoteaddr',
     unless local mailman configurations knows about an address, in
     which case it will be handled via mailman.  Note that running this
     has a good chance to make you into an open relay, so please be
     careful.


File: python.info,  Node: SMTPChannel Objects,  Prev: MailmanProxy Objects,  Up: smtpd --- SMTP Server

5.21.18.5 SMTPChannel Objects
.............................

 -- 類別: smtpd.SMTPChannel (server, conn, addr,
          data_size_limit=33554432, map=None, enable_SMTPUTF8=False,
          decode_data=False)

     Create a new *note SMTPChannel: 606. object which manages the
     communication between the server and a single SMTP client.

     `conn' and `addr' are as per the instance variables described
     below.

     `data_size_limit' specifies the maximum number of bytes that will
     be accepted in a ‘DATA’ command.  A value of ‘None’ or ‘0’ means no
     limit.

     `enable_SMTPUTF8' determines whether the ‘SMTPUTF8’ extension (as
     defined in RFC 6531(1)) should be enabled.  The default is ‘False’.
     `decode_data' and `enable_SMTPUTF8' cannot be set to ‘True’ at the
     same time.

     A dictionary can be specified in `map' to avoid using a global
     socket map.

     `decode_data' specifies whether the data portion of the SMTP
     transaction should be decoded using UTF-8.  The default is ‘False’.
     `decode_data' and `enable_SMTPUTF8' cannot be set to ‘True’ at the
     same time.

     To use a custom SMTPChannel implementation you need to override the
     *note SMTPServer.channel_class: 2dcc. of your *note SMTPServer:
     607.

     3.5 版更變: The `decode_data' and `enable_SMTPUTF8' parameters were
     added.

     3.6 版更變: `decode_data' is now ‘False’ by default.

     The *note SMTPChannel: 606. has the following instance variables:

      -- 屬性: smtp_server

          Holds the *note SMTPServer: 607. that spawned this channel.

      -- 屬性: conn

          Holds the socket object connecting to the client.

      -- 屬性: addr

          Holds the address of the client, the second value returned by
          *note socket.accept: 67a.

      -- 屬性: received_lines

          Holds a list of the line strings (decoded using UTF-8)
          received from the client.  The lines have their ‘"\r\n"’ line
          ending translated to ‘"\n"’.

      -- 屬性: smtp_state

          Holds the current state of the channel.  This will be either
          ‘COMMAND’ initially and then ‘DATA’ after the client sends a
          "DATA" line.

      -- 屬性: seen_greeting

          Holds a string containing the greeting sent by the client in
          its "HELO".

      -- 屬性: mailfrom

          Holds a string containing the address identified in the "MAIL
          FROM:" line from the client.

      -- 屬性: rcpttos

          Holds a list of strings containing the addresses identified in
          the "RCPT TO:" lines from the client.

      -- 屬性: received_data

          Holds a string containing all of the data sent by the client
          during the DATA state, up to but not including the terminating
          ‘"\r\n.\r\n"’.

      -- 屬性: fqdn

          Holds the fully-qualified domain name of the server as
          returned by *note socket.getfqdn(): 2690.

      -- 屬性: peer

          Holds the name of the client peer as returned by
          ‘conn.getpeername()’ where ‘conn’ is *note conn: 2dd5.

     The *note SMTPChannel: 606. operates by invoking methods named
     ‘smtp_<command>’ upon reception of a command line from the client.
     Built into the base *note SMTPChannel: 606. class are methods for
     handling the following commands (and responding to them
     appropriately):

     Command      Action taken
                  
     -------------------------------------------------------------------------------------
                  
     HELO         Accepts the greeting from the client and stores it in
                  *note seen_greeting: 2dd9.  Sets server to base command mode.
                  
                  
     EHLO         Accepts the greeting from the client and stores it in
                  *note seen_greeting: 2dd9.  Sets server to extended command mode.
                  
                  
     NOOP         Takes no action.
                  
                  
     QUIT         Closes the connection cleanly.
                  
                  
     MAIL         Accepts the "MAIL FROM:" syntax and stores the supplied address as
                  *note mailfrom: 2dda.  In extended command mode, accepts the RFC
                  1870(2) SIZE attribute and responds appropriately based on the value
                  of `data_size_limit'.
                  
                  
     RCPT         Accepts the "RCPT TO:" syntax and stores the supplied addresses in
                  the *note rcpttos: 2ddb. list.
                  
                  
     RSET         Resets the *note mailfrom: 2dda, *note rcpttos: 2ddb, and
                  *note received_data: 2ddc, but not the greeting.
                  
                  
     DATA         Sets the internal state to ‘DATA’ and stores remaining lines from the
                  client in *note received_data: 2ddc. until the terminator
                  ‘"\r\n.\r\n"’ is received.
                  
                  
     HELP         Returns minimal information on command syntax
                  
                  
     VRFY         Returns code 252 (the server doesn’t know if the address is valid)
                  
                  
     EXPN         Reports that the command is not implemented.
                  

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc6531.html

   (2) https://tools.ietf.org/html/rfc1870.html


File: python.info,  Node: telnetlib --- Telnet client,  Next: uuid --- UUID objects according to RFC 4122,  Prev: smtpd --- SMTP Server,  Up: Internet Protocols and Support

5.21.19 ‘telnetlib’ — Telnet client
-----------------------------------

`Source code:' Lib/telnetlib.py(1)

__________________________________________________________________

The *note telnetlib: 103. module provides a *note Telnet: 59c. class
that implements the Telnet protocol.  See RFC 854(2) for details about
the protocol.  In addition, it provides symbolic constants for the
protocol characters (see below), and for the telnet options.  The
symbolic names of the telnet options follow the definitions in
‘arpa/telnet.h’, with the leading ‘TELOPT_’ removed.  For symbolic names
of options which are traditionally not included in ‘arpa/telnet.h’, see
the module source itself.

The symbolic constants for the telnet commands are: IAC, DONT, DO, WONT,
WILL, SE (Subnegotiation End), NOP (No Operation), DM (Data Mark), BRK
(Break), IP (Interrupt process), AO (Abort output), AYT (Are You There),
EC (Erase Character), EL (Erase Line), GA (Go Ahead), SB (Subnegotiation
Begin).

 -- 類別: telnetlib.Telnet (host=None, port=0[, timeout])

     *note Telnet: 59c. represents a connection to a Telnet server.  The
     instance is initially not connected by default; the *note open():
     2de1. method must be used to establish a connection.
     Alternatively, the host name and optional port number can be passed
     to the constructor too, in which case the connection to the server
     will be established before the constructor returns.  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).

     Do not reopen an already connected instance.

     This class has many ‘read_*()’ methods.  Note that some of them
     raise *note EOFError: c71. when the end of the connection is read,
     because they can return an empty string for other reasons.  See the
     individual descriptions below.

     A *note Telnet: 59c. object is a context manager and can be used in
     a *note with: 6ee. statement.  When the ‘with’ block ends, the
     *note close(): 2de2. method is called:

          >>> from telnetlib import Telnet
          >>> with Telnet('localhost', 23) as tn:
          ...     tn.interact()
          ...

     3.6 版更變: Context manager support added

也參考
......

RFC 854(3) - Telnet Protocol Specification

     Definition of the Telnet protocol.

* Menu:

* Telnet Objects::
* Telnet Example::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/telnetlib.py

   (2) https://tools.ietf.org/html/rfc854.html

   (3) https://tools.ietf.org/html/rfc854.html


File: python.info,  Node: Telnet Objects,  Next: Telnet Example,  Up: telnetlib --- Telnet client

5.21.19.1 Telnet Objects
........................

*note Telnet: 59c. instances have the following methods:

 -- 成員函式: Telnet.read_until (expected, timeout=None)

     Read until a given byte string, `expected', is encountered or until
     `timeout' seconds have passed.

     When no match is found, return whatever is available instead,
     possibly empty bytes.  Raise *note EOFError: c71. if the connection
     is closed and no cooked data is available.

 -- 成員函式: Telnet.read_all ()

     Read all data until EOF as bytes; block until connection closed.

 -- 成員函式: Telnet.read_some ()

     Read at least one byte of cooked data unless EOF is hit.  Return
     ‘b''’ if EOF is hit.  Block if no data is immediately available.

 -- 成員函式: Telnet.read_very_eager ()

     Read everything that can be without blocking in I/O (eager).

     Raise *note EOFError: c71. if connection closed and no cooked data
     available.  Return ‘b''’ if no cooked data available otherwise.  Do
     not block unless in the midst of an IAC sequence.

 -- 成員函式: Telnet.read_eager ()

     Read readily available data.

     Raise *note EOFError: c71. if connection closed and no cooked data
     available.  Return ‘b''’ if no cooked data available otherwise.  Do
     not block unless in the midst of an IAC sequence.

 -- 成員函式: Telnet.read_lazy ()

     Process and return data already in the queues (lazy).

     Raise *note EOFError: c71. if connection closed and no data
     available.  Return ‘b''’ if no cooked data available otherwise.  Do
     not block unless in the midst of an IAC sequence.

 -- 成員函式: Telnet.read_very_lazy ()

     Return any data available in the cooked queue (very lazy).

     Raise *note EOFError: c71. if connection closed and no data
     available.  Return ‘b''’ if no cooked data available otherwise.
     This method never blocks.

 -- 成員函式: Telnet.read_sb_data ()

     Return the data collected between a SB/SE pair (suboption
     begin/end).  The callback should access these data when it was
     invoked with a ‘SE’ command.  This method never blocks.

 -- 成員函式: Telnet.open (host, port=0[, timeout])

     Connect to a host.  The optional second argument is the port
     number, which defaults to the standard Telnet port (23).  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).

     Do not try to reopen an already connected instance.

     Raises an *note auditing event: e96. ‘telnetlib.Telnet.open’ with
     arguments ‘self’, ‘host’, ‘port’.

 -- 成員函式: Telnet.msg (msg, *args)

     Print a debug message when the debug level is ‘>’ 0.  If extra
     arguments are present, they are substituted in the message using
     the standard string formatting operator.

 -- 成員函式: Telnet.set_debuglevel (debuglevel)

     Set the debug level.  The higher the value of `debuglevel', the
     more debug output you get (on ‘sys.stdout’).

 -- 成員函式: Telnet.close ()

     Close the connection.

 -- 成員函式: Telnet.get_socket ()

     Return the socket object used internally.

 -- 成員函式: Telnet.fileno ()

     Return the file descriptor of the socket object used internally.

 -- 成員函式: Telnet.write (buffer)

     Write a byte string to the socket, doubling any IAC characters.
     This can block if the connection is blocked.  May raise *note
     OSError: 1d4. if the connection is closed.

     Raises an *note auditing event: e96. ‘telnetlib.Telnet.write’ with
     arguments ‘self’, ‘buffer’.

     3.3 版更變: This method used to raise *note socket.error: 99a,
     which is now an alias of *note OSError: 1d4.

 -- 成員函式: Telnet.interact ()

     Interaction function, emulates a very dumb Telnet client.

 -- 成員函式: Telnet.mt_interact ()

     Multithreaded version of *note interact(): 2df2.

 -- 成員函式: Telnet.expect (list, timeout=None)

     Read until one from a list of a regular expressions matches.

     The first argument is a list of regular expressions, either
     compiled (*note regex objects: 8a1.) or uncompiled (byte strings).
     The optional second argument is a timeout, in seconds; the default
     is to block indefinitely.

     Return a tuple of three items: the index in the list of the first
     regular expression that matches; the match object returned; and the
     bytes read up till and including the match.

     If end of file is found and no bytes were read, raise *note
     EOFError: c71.  Otherwise, when nothing matches, return ‘(-1, None,
     data)’ where `data' is the bytes received so far (may be empty
     bytes if a timeout happened).

     If a regular expression ends with a greedy match (such as ‘.*’) or
     if more than one expression can match the same input, the results
     are non-deterministic, and may depend on the I/O timing.

 -- 成員函式: Telnet.set_option_negotiation_callback (callback)

     Each time a telnet option is read on the input flow, this
     `callback' (if set) is called with the following parameters:
     callback(telnet socket, command (DO/DONT/WILL/WONT), option).  No
     other action is done afterwards by telnetlib.


File: python.info,  Node: Telnet Example,  Prev: Telnet Objects,  Up: telnetlib --- Telnet client

5.21.19.2 Telnet Example
........................

A simple example illustrating typical use:

     import getpass
     import telnetlib

     HOST = "localhost"
     user = input("Enter your remote account: ")
     password = getpass.getpass()

     tn = telnetlib.Telnet(HOST)

     tn.read_until(b"login: ")
     tn.write(user.encode('ascii') + b"\n")
     if password:
         tn.read_until(b"Password: ")
         tn.write(password.encode('ascii') + b"\n")

     tn.write(b"ls\n")
     tn.write(b"exit\n")

     print(tn.read_all().decode('ascii'))


File: python.info,  Node: uuid --- UUID objects according to RFC 4122,  Next: socketserver --- A framework for network servers,  Prev: telnetlib --- Telnet client,  Up: Internet Protocols and Support

5.21.20 ‘uuid’ — UUID objects according to `RFC 4122'
-----------------------------------------------------

`Source code:' Lib/uuid.py(1)

__________________________________________________________________

This module provides immutable *note UUID: 261. objects (the *note UUID:
261. class) and the functions *note uuid1(): 418, *note uuid3(): 2dfa,
*note uuid4(): 2dfb, *note uuid5(): 2dfc. for generating version 1, 3,
4, and 5 UUIDs as specified in RFC 4122(2).

If all you want is a unique ID, you should probably call *note uuid1():
418. or *note uuid4(): 2dfb.  Note that *note uuid1(): 418. may
compromise privacy since it creates a UUID containing the computer’s
network address.  *note uuid4(): 2dfb. creates a random UUID.

Depending on support from the underlying platform, *note uuid1(): 418.
may or may not return a "safe" UUID. A safe UUID is one which is
generated using synchronization methods that ensure no two processes can
obtain the same UUID. All instances of *note UUID: 261. have an
‘is_safe’ attribute which relays any information about the UUID’s
safety, using this enumeration:

 -- 類別: uuid.SafeUUID

     3.7 版新加入.

      -- 屬性: safe

          The UUID was generated by the platform in a
          multiprocessing-safe way.

      -- 屬性: unsafe

          The UUID was not generated in a multiprocessing-safe way.

      -- 屬性: unknown

          The platform does not provide information on whether the UUID
          was generated safely or not.

 -- 類別: uuid.UUID (hex=None, bytes=None, bytes_le=None, fields=None,
          int=None, version=None, *, is_safe=SafeUUID.unknown)

     Create a UUID from either a string of 32 hexadecimal digits, a
     string of 16 bytes in big-endian order as the `bytes' argument, a
     string of 16 bytes in little-endian order as the `bytes_le'
     argument, a tuple of six integers (32-bit `time_low', 16-bit
     `time_mid', 16-bit `time_hi_version', 8-bit `clock_seq_hi_variant',
     8-bit `clock_seq_low', 48-bit `node') as the `fields' argument, or
     a single 128-bit integer as the `int' argument.  When a string of
     hex digits is given, curly braces, hyphens, and a URN prefix are
     all optional.  For example, these expressions all yield the same
     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)

     Exactly one of `hex', `bytes', `bytes_le', `fields', or `int' must
     be given.  The `version' argument is optional; if given, the
     resulting UUID will have its variant and version number set
     according to RFC 4122(3), overriding bits in the given `hex',
     `bytes', `bytes_le', `fields', or `int'.

     Comparison of UUID objects are made by way of comparing their *note
     UUID.int: 2e01. attributes.  Comparison with a non-UUID object
     raises a *note TypeError: 193.

     ‘str(uuid)’ returns a string in the form
     ‘12345678-1234-5678-1234-567812345678’ where the 32 hexadecimal
     digits represent the UUID.

*note UUID: 261. instances have these read-only attributes:

 -- 屬性: UUID.bytes

     The UUID as a 16-byte string (containing the six integer fields in
     big-endian byte order).

 -- 屬性: UUID.bytes_le

     The UUID as a 16-byte string (with `time_low', `time_mid', and
     `time_hi_version' in little-endian byte order).

 -- 屬性: UUID.fields

     A tuple of the six integer fields of the UUID, which are also
     available as six individual attributes and two derived attributes:

     Field                              Meaning
                                        
     -----------------------------------------------------------------------
                                        
     ‘time_low’                         the first 32 bits of the UUID
                                        
                                        
     ‘time_mid’                         the next 16 bits of the UUID
                                        
                                        
     ‘time_hi_version’                  the next 16 bits of the UUID
                                        
                                        
     ‘clock_seq_hi_variant’             the next 8 bits of the UUID
                                        
                                        
     ‘clock_seq_low’                    the next 8 bits of the UUID
                                        
                                        
     ‘node’                             the last 48 bits of the UUID
                                        
                                        
     *note time: 10b.                   the 60-bit timestamp
                                        
                                        
     ‘clock_seq’                        the 14-bit sequence number
                                        

 -- 屬性: UUID.hex

     The UUID as a 32-character hexadecimal string.

 -- 屬性: UUID.int

     The UUID as a 128-bit integer.

 -- 屬性: UUID.urn

     The UUID as a URN as specified in RFC 4122(4).

 -- 屬性: UUID.variant

     The UUID variant, which determines the internal layout of the UUID.
     This will be one of the constants *note RESERVED_NCS: 2e08, *note
     RFC_4122: 2e09, *note RESERVED_MICROSOFT: 2e0a, or *note
     RESERVED_FUTURE: 2e0b.

 -- 屬性: UUID.version

     The UUID version number (1 through 5, meaningful only when the
     variant is *note RFC_4122: 2e09.).

 -- 屬性: UUID.is_safe

     An enumeration of *note SafeUUID: 2dfd. which indicates whether the
     platform generated the UUID in a multiprocessing-safe way.

     3.7 版新加入.

The *note uuid: 125. module defines the following functions:

 -- 函式: uuid.getnode ()

     Get the hardware address as a 48-bit positive integer.  The first
     time this runs, it may launch a separate program, which could be
     quite slow.  If all attempts to obtain the hardware address fail,
     we choose a random 48-bit number with the multicast bit (least
     significant bit of the first octet) set to 1 as recommended in RFC
     4122(5).  "Hardware address" means the MAC address of a network
     interface.  On a machine with multiple network interfaces,
     universally administered MAC addresses (i.e.  where the second
     least significant bit of the first octet is `unset') will be
     preferred over locally administered MAC addresses, but with no
     other ordering guarantees.

     3.7 版更變: Universally administered MAC addresses are preferred
     over locally administered MAC addresses, since the former are
     guaranteed to be globally unique, while the latter are not.

 -- 函式: uuid.uuid1 (node=None, clock_seq=None)

     Generate a UUID from a host ID, sequence number, and the current
     time.  If `node' is not given, *note getnode(): 417. is used to
     obtain the hardware address.  If `clock_seq' is given, it is used
     as the sequence number; otherwise a random 14-bit sequence number
     is chosen.

 -- 函式: uuid.uuid3 (namespace, name)

     Generate a UUID based on the MD5 hash of a namespace identifier
     (which is a UUID) and a name (which is a string).

 -- 函式: uuid.uuid4 ()

     Generate a random UUID.

 -- 函式: uuid.uuid5 (namespace, name)

     Generate a UUID based on the SHA-1 hash of a namespace identifier
     (which is a UUID) and a name (which is a string).

The *note uuid: 125. module defines the following namespace identifiers
for use with *note uuid3(): 2dfa. or *note uuid5(): 2dfc.

 -- Data: uuid.NAMESPACE_DNS

     When this namespace is specified, the `name' string is a
     fully-qualified domain name.

 -- Data: uuid.NAMESPACE_URL

     When this namespace is specified, the `name' string is a URL.

 -- Data: uuid.NAMESPACE_OID

     When this namespace is specified, the `name' string is an ISO OID.

 -- Data: uuid.NAMESPACE_X500

     When this namespace is specified, the `name' string is an X.500 DN
     in DER or a text output format.

The *note uuid: 125. module defines the following constants for the
possible values of the ‘variant’ attribute:

 -- Data: uuid.RESERVED_NCS

     Reserved for NCS compatibility.

 -- Data: uuid.RFC_4122

     Specifies the UUID layout given in RFC 4122(6).

 -- Data: uuid.RESERVED_MICROSOFT

     Reserved for Microsoft compatibility.

 -- Data: uuid.RESERVED_FUTURE

     Reserved for future definition.

也參考
......

RFC 4122(7) - A Universally Unique IDentifier (UUID) URN Namespace

     This specification defines a Uniform Resource Name namespace for
     UUIDs, the internal format of UUIDs, and methods of generating
     UUIDs.

* Menu:

* Example: Example<13>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/uuid.py

   (2) https://tools.ietf.org/html/rfc4122.html

   (3) https://tools.ietf.org/html/rfc4122.html

   (4) https://tools.ietf.org/html/rfc4122.html

   (5) https://tools.ietf.org/html/rfc4122.html

   (6) https://tools.ietf.org/html/rfc4122.html

   (7) https://tools.ietf.org/html/rfc4122.html


File: python.info,  Node: Example<13>,  Up: uuid --- UUID objects according to RFC 4122

5.21.20.1 Example
.................

Here are some examples of typical usage of the *note uuid: 125. 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')

     >>> # 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: socketserver --- A framework for network servers,  Next: http server --- HTTP servers,  Prev: uuid --- UUID objects according to RFC 4122,  Up: Internet Protocols and Support

5.21.21 ‘socketserver’ — A framework for network servers
--------------------------------------------------------

`Source code:' Lib/socketserver.py(1)

__________________________________________________________________

The *note socketserver: f1. module simplifies the task of writing
network servers.

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(): 2e16. and *note server_activate():
     2e17.  The other parameters are passed to the *note BaseServer:
     a8e. 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: 2e15.

 -- 類別: 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: 2e15.

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: 3da.
and *note ThreadingMixIn: 3db. 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: 2e1b.
class and overriding its *note handle(): 2e1c. 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: 6ee.
statement.  Then call the *note handle_request(): 2e1d. or *note
serve_forever(): a90. method of the server object to process one or many
requests.  Finally, call *note server_close(): 2e1e. to close the socket
(unless you used a ‘with’ statement).

When inheriting from *note ThreadingMixIn: 3db. for threaded connection
behavior, you should explicitly declare how you want your threads to
behave on an abrupt shutdown.  The *note ThreadingMixIn: 3db. 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: 38d, meaning that Python will not exit until all threads
created by *note ThreadingMixIn: 3db. have exited.

Server classes have the same external methods and attributes, no matter
what network protocol they use.

* Menu:

* Server Creation Notes::
* Server Objects: Server Objects<2>.
* Request Handler Objects::
* Examples: Examples<23>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/socketserver.py


File: python.info,  Node: Server Creation Notes,  Next: Server Objects<2>,  Up: socketserver --- A framework for network servers

5.21.21.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: 2e1a. derives from *note UDPServer:
2e18, not from *note UnixStreamServer: 2e19. — the only difference
between an IP and a Unix stream server is the address family, which is
simply repeated in both Unix server classes.

 -- 類別: 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: 2e20. is created as follows:

          class ThreadingUDPServer(ThreadingMixIn, UDPServer):
              pass

     The mix-in class comes first, since it overrides a method defined
     in *note UDPServer: 2e18.  Setting the various attributes also
     changes the behavior of the underlying server mechanism.

     *note ForkingMixIn: 3da. and the Forking classes mentioned below
     are only available on POSIX platforms that support *note fork():
     966.

     ‘socketserver.ForkingMixIn.server_close()’ waits until all child
     processes complete, except if
     ‘socketserver.ForkingMixIn.block_on_close’ attribute is false.

     ‘socketserver.ThreadingMixIn.server_close()’ waits until all
     non-daemon threads complete, except if
     ‘socketserver.ThreadingMixIn.block_on_close’ attribute is false.
     Use daemonic threads by setting ‘ThreadingMixIn.daemon_threads’ to
     ‘True’ to not wait until threads complete.

     3.7 版更變: ‘socketserver.ForkingMixIn.server_close()’ and
     ‘socketserver.ThreadingMixIn.server_close()’ now waits until all
     child processes and non-daemonic threads complete.  Add a new
     ‘socketserver.ForkingMixIn.block_on_close’ class attribute to
     opt-in for the pre-3.7 behaviour.

 -- 類別: socketserver.ForkingTCPServer
 -- 類別: socketserver.ForkingUDPServer
 -- 類別: socketserver.ThreadingTCPServer
 -- 類別: socketserver.ThreadingUDPServer

     These classes are pre-defined using the mix-in classes.

To implement a service, you must derive a class from *note
BaseRequestHandler: 2e1b. and redefine its *note handle(): 2e1c. 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: 58c.
or *note DatagramRequestHandler: 2e24.

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():
2e1c. method.

Another approach to handling multiple simultaneous requests in an
environment that supports neither threads nor *note fork(): 966. (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: e7. 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).  See *note
asyncore: b. for another way to manage this.


File: python.info,  Node: Server Objects<2>,  Next: Request Handler Objects,  Prev: Server Creation Notes,  Up: socketserver --- A framework for network servers

5.21.21.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: 2e26. and *note
     RequestHandlerClass: 2e27. 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: e7, 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(): 2e29, *note
          verify_request(): 2e2a, and *note process_request(): 2e2b.  If
          the user-provided *note handle(): 2e1c. method of the handler
          class raises an exception, the server’s *note handle_error():
          602. method will be called.  If no request is received within
          *note timeout: 2e2c. seconds, *note handle_timeout(): 2e2d.
          will be called and *note handle_request(): 2e1d. will return.

      -- 成員函式: serve_forever (poll_interval=0.5)

          Handle requests until an explicit *note shutdown(): 1022.
          request.  Poll for shutdown every `poll_interval' seconds.
          Ignores the *note timeout: 2e2c. attribute.  It also calls
          *note service_actions(): a8f, which may be used by a subclass
          or mixin to provide actions specific to a given service.  For
          example, the *note ForkingMixIn: 3da. class uses *note
          service_actions(): a8f. 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(): a90. 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(): a90. loop to stop and wait
          until it does.  *note shutdown(): 1022. must be called while
          *note serve_forever(): a90. 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: 25ae. and *note
          socket.AF_UNIX: 25b4.

      -- 屬性: 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: f0. 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: 38d, 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: 2e31. 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: c8f. and *note socket.SOCK_DGRAM: c8e. are
          two common values.

      -- 屬性: timeout

          Timeout duration, measured in seconds, or *note None: 158. if
          no timeout is desired.  If *note handle_request(): 2e1d.
          receives no incoming requests within the timeout period, the
          *note handle_timeout(): 2e2d. method is called.

     There are various server methods that can be overridden by
     subclasses of base server classes like *note TCPServer: 2e15.;
     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: 2e27. and calling its *note handle():
          2e1c. 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(): 2e1c. method of
          a *note RequestHandlerClass: 2e27. 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: 1aa. class.

      -- 成員函式: handle_timeout ()

          This function is called when the *note timeout: 2e2c.
          attribute has been set to a value other than *note None: 158.
          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(): 2e33. to create an instance of
          the *note RequestHandlerClass: 2e27.  If desired, this
          function can create a new process or thread to handle the
          request; the *note ForkingMixIn: 3da. and *note
          ThreadingMixIn: 3db. 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(): 750. 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: 49e,
          the request will be processed, and if it’s *note False: 38d,
          the request will be denied.  This function can be overridden
          to implement access controls for a server.  The default
          implementation always returns *note True: 49e.

     3.6 版更變: Support for the *note context manager: 56d. protocol
     was added.  Exiting the context manager is equivalent to calling
     *note server_close(): 2e1e.


File: python.info,  Node: Request Handler Objects,  Next: Examples<23>,  Prev: Server Objects<2>,  Up: socketserver --- A framework for network servers

5.21.21.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(): 2e1c. 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(): 2e1c. 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 ‘self.request’; the client address as
          ‘self.client_address’; and the server instance as
          ‘self.server’, in case it needs access to per-server
          information.

          The type of ‘self.request’ is different for datagram or stream
          services.  For stream services, ‘self.request’ is a socket
          object; for datagram services, ‘self.request’ is a pair of
          string and socket.

      -- 成員函式: finish ()

          Called after the *note handle(): 2e1c. method to perform any
          clean-up actions required.  The default implementation does
          nothing.  If *note setup(): 2e35. raises an exception, this
          function will not be called.

 -- 類別: socketserver.StreamRequestHandler
 -- 類別: socketserver.DatagramRequestHandler

     These *note BaseRequestHandler: 2e1b. subclasses override the *note
     setup(): 2e35. and *note finish(): 2e36. methods, and provide
     ‘self.rfile’ and ‘self.wfile’ attributes.  The ‘self.rfile’ and
     ‘self.wfile’ attributes can be read or written, respectively, to
     get the request data or return data to the client.

     The ‘rfile’ attributes of both classes support the *note
     io.BufferedIOBase: 58d. readable interface, and
     ‘DatagramRequestHandler.wfile’ supports the *note
     io.BufferedIOBase: 58d. writable interface.

     3.6 版更變: ‘StreamRequestHandler.wfile’ also supports the *note
     io.BufferedIOBase: 58d. writable interface.


File: python.info,  Node: Examples<23>,  Prev: Request Handler Objects,  Up: socketserver --- A framework for network servers

5.21.21.4 Examples
..................

* Menu:

* socketserver.TCPServer Example: socketserver TCPServer Example.
* socketserver.UDPServer Example: socketserver UDPServer Example.
* Asynchronous Mixins::


File: python.info,  Node: socketserver TCPServer Example,  Next: socketserver UDPServer Example,  Up: Examples<23>

5.21.21.5 ‘socketserver.TCPServer’ Example
..........................................

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("{} wrote:".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 sent from the client in one ‘sendall()’ call.

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 Example,  Next: Asynchronous Mixins,  Prev: socketserver TCPServer Example,  Up: Examples<23>

5.21.21.6 ‘socketserver.UDPServer’ Example
..........................................

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 Example,  Up: Examples<23>

5.21.21.7 Asynchronous Mixins
.............................

To build asynchronous handlers, use the *note ThreadingMixIn: 3db. and
*note ForkingMixIn: 3da. classes.

An example for the *note ThreadingMixIn: 3db. 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: 3da. 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(): 966.


File: python.info,  Node: http server --- HTTP servers,  Next: http cookies --- HTTP state management,  Prev: socketserver --- A framework for network servers,  Up: Internet Protocols and Support

5.21.22 ‘http.server’ — HTTP servers
------------------------------------

`Source code:' Lib/http/server.py(1)

__________________________________________________________________

This module defines classes for implementing HTTP servers (Web servers).

     警告: *note http.server: 97. is not recommended for production.  It
     only implements basic security checks.

One class, *note HTTPServer: 2c0c, is a *note socketserver.TCPServer:
2e15. 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: 2e15. 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: 3db.  This is useful to
     handle web browsers pre-opening sockets, on which *note HTTPServer:
     2c0c. would wait indefinitely.

     3.7 版新加入.

The *note HTTPServer: 2c0c. and *note ThreadingHTTPServer: 39b. 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: a13. 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
     *note __init__(): d63. method.

     *note BaseHTTPRequestHandler: a13. 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():
          2e40. 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(): 2e40.  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: 2e45. class variable.  This instance parses and
          manages the headers in the HTTP request.  The *note
          parse_headers(): 1045. function from *note http.client: 94. 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: 58d. 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: 58d. stream.

     *note BaseHTTPRequestHandler: a13. has the following attributes:

      -- 屬性: 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: 2e4a. method and the *note
          server_version: 2e48. class variable.  For example,
          ‘'Python/1.4'’.

      -- 屬性: error_message_format

          Specifies a format string that should be used by *note
          send_error(): 861. method for building an error response to
          the client.  The string is filled by default with variables
          from *note responses: 2cd7. based on the status code that
          passed to *note send_error(): 861.

      -- 屬性: error_content_type

          Specifies the Content-Type HTTP header of error responses sent
          to the client.  The default value is ‘'text/html'’.

      -- 屬性: protocol_version

          This specifies the HTTP protocol version used in responses.
          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():
          2e4e.) in all of its responses to clients.  For backwards
          compatibility, the setting defaults to ‘'HTTP/1.0'’.

      -- 屬性: MessageClass

          Specifies an *note email.message.Message: 546.-like class to
          parse HTTP headers.  Typically, this is not overridden, and it
          defaults to ‘http.client.HTTPMessage’.

      -- 屬性: 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(): 2e4f. and *note
          send_error(): 861. methods.

     A *note BaseHTTPRequestHandler: a13. instance has the following
     methods:

      -- 成員函式: handle ()

          Calls *note handle_one_request(): 2e40. 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 a HTTP/1.1 compliant 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 chose 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: 2e4b. attribute and
          emitted, after a complete set of headers, as the response
          body.  The *note responses: 2cd7. 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(): 2e4a. and *note date_time_string(): 2e53.
          methods, respectively.  If the server does not intend to send
          any other headers using the *note send_header(): 2e4e. method,
          then *note send_response(): 2e52. should be followed by an
          *note end_headers(): a14. call.

          3.3 版更變: Headers are stored to an internal buffer and *note
          end_headers(): a14. 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():
          a14. or *note flush_headers(): a15. 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(): a14. 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(): a15.

          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(): 2e56, 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(): 2e56.
          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: 2e48. and *note
          sys_version: 2e49. 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(): 322.),
          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 current directory and below,
     directly mapping the directory structure to HTTP requests.

     A lot of the work, such as parsing the request, is done by the base
     class *note BaseHTTPRequestHandler: a13.  This class implements the
     *note do_GET(): 2e59. and *note do_HEAD(): 2e5a. functions.

     The following are defined as class-level attributes of *note
     SimpleHTTPRequestHandler: 39a.:

      -- 屬性: server_version

          This will be ‘"SimpleHTTP/" + __version__’, where
          ‘__version__’ is defined at the module level.

      -- 屬性: extensions_map

          A dictionary mapping suffixes into MIME types.  The default is
          signified by an empty string, and is considered to be
          ‘application/octet-stream’.  The mapping is used
          case-insensitively, and so should contain only lower-cased
          keys.

      -- 屬性: directory

          If not specified, the directory to serve is the current
          working directory.

     The *note SimpleHTTPRequestHandler: 39a. 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(): 2e59. 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(): a46. to scan the directory, and returns a ‘404’
          error response if the *note listdir(): a46. fails.

          If the request was mapped to a file, it is opened.  Any *note
          OSError: 1d4. exception in opening the requested file is
          mapped to a ‘404’, ‘'File not found'’ error.  If there was a
          ‘'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 *note test():
          106. function invocation in the *note http.server: 97. module.

          3.7 版更變: Support of the ‘'If-Modified-Since'’ header.

The *note SimpleHTTPRequestHandler: 39a. 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 http.server: 97. can also be invoked directly using the *note -m:
33c. switch of the interpreter with a ‘port number’ argument.  Similar
to the previous example, this serves files relative to the current
directory:

     python -m http.server 8000

By default, 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 8000 --bind 127.0.0.1

3.4 版新加入: ‘--bind’ argument was introduced.

3.8 版新加入: ‘--bind’ argument enhanced to support IPv6

By default, 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’ specify alternate directory

 -- 類別: 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: 39a.

          備註: CGI scripts run by the *note CGIHTTPRequestHandler:
          2e5e. 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: 2e5e. 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: 2e5e. 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.

*note CGIHTTPRequestHandler: 2e5e. can be enabled in the command line by
passing the ‘--cgi’ option:

     python -m http.server --cgi 8000

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/http/server.py

   (2) https://tools.ietf.org/html/rfc3986.html

   (3) https://tools.ietf.org/html/rfc2822.html


File: python.info,  Node: http cookies --- HTTP state management,  Next: http cookiejar --- Cookie handling for HTTP clients,  Prev: http server --- HTTP servers,  Up: Internet Protocols and Support

5.21.23 ‘http.cookies’ — HTTP state management
----------------------------------------------

`Source code:' Lib/http/cookies.py(1)

__________________________________________________________________

The *note http.cookies: 96. 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 doesn’t follow the character rules outlined in
those specs and also many current day browsers and servers have relaxed
parsing rules when comes to Cookie handling.  As a result, the parsing
rules used are a bit less strict.

The character set, *note string.ascii_letters: c61, *note string.digits:
172a. and ‘!#$%&'*+-.^_`|~:’ denote the set of valid characters allowed
by this module in Cookie name (as *note key: 492.).

3.3 版更變: Allowed ’:’ as a valid Cookie name character.

     備註: On encountering an invalid cookie, *note CookieError: 2e63.
     is raised, so if your cookie data comes from a browser you should
     always prepare for invalid data and catch *note CookieError: 2e63.
     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: 495. instances.  Note that upon
     setting a key to a value, the value is first converted to a *note
     Morsel: 495. containing the key and the value.

     If `input' is given, it is passed to the *note load(): 2e65.
     method.

 -- 類別: http.cookies.SimpleCookie ([input])

     This class derives from *note BaseCookie: 2e64. and overrides
     ‘value_decode()’ and ‘value_encode()’.  SimpleCookie supports
     strings as cookie values.  When setting the value, SimpleCookie
     calls the builtin *note str(): 335. to convert the value to a
     string.  Values received from HTTP are kept as strings.

也參考
......

Module *note http.cookiejar: 95.

     HTTP cookie handling for web `clients'.  The *note http.cookiejar:
     95. and *note http.cookies: 96. 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 Objects::
* Morsel Objects::
* Example: Example<14>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/http/cookies.py

   (2) https://tools.ietf.org/html/rfc2109.html

   (3) https://tools.ietf.org/html/rfc2068.html

   (4) https://tools.ietf.org/html/rfc2109.html

   (5) https://tools.ietf.org/html/rfc2109.html


File: python.info,  Node: Cookie Objects,  Next: Morsel Objects,  Up: http cookies --- HTTP state management

5.21.23.1 Cookie Objects
........................

 -- 成員函式: 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: 2e64. — 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: 2e64. — it exists so
     it can be overridden.

     In general, it should be the case that *note value_encode(): 2e69.
     and *note value_decode(): 2e68. 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: 495.’s *note
     output(): 2e6a. 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(): 2e6a.

 -- 成員函式: BaseCookie.load (rawdata)

     If `rawdata' is a string, parse it as an ‘HTTP_COOKIE’ and add the
     values found there as *note Morsel: 495.s.  If it is a dictionary,
     it is equivalent to:

          for k, v in rawdata.items():
              cookie[k] = v


File: python.info,  Node: Morsel Objects,  Next: Example<14>,  Prev: Cookie Objects,  Up: http cookies --- HTTP state management

5.21.23.2 Morsel Objects
........................

 -- 類別: 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 ‘httponly’ 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 ‘samesite’ 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: 492. and *note value:
     493. into account.

     3.7 版更變: Attributes *note key: 492, *note value: 493. and *note
     coded_value: 494. are read-only.  Use *note set(): 496. for setting
     them.

     3.8 版更變: Added support for the ‘samesite’ attribute.

 -- 屬性: 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: 495.

 -- 成員函式: 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(): 2e6f.

 -- 成員函式: 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(): 2e6f.

 -- 成員函式: 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(): 9c4.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2109.html

   (2) https://tools.ietf.org/html/rfc2109.html

   (3) https://tools.ietf.org/html/rfc2109.html

   (4) https://tools.ietf.org/html/rfc2109.html


File: python.info,  Node: Example<14>,  Prev: Morsel Objects,  Up: http cookies --- HTTP state management

5.21.23.3 Example
.................

The following example demonstrates how to use the *note http.cookies:
96. 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 --- Cookie handling for HTTP clients,  Next: xmlrpc --- XMLRPC server and client modules,  Prev: http cookies --- HTTP state management,  Up: Internet Protocols and Support

5.21.24 ‘http.cookiejar’ — Cookie handling for HTTP clients
-----------------------------------------------------------

`Source code:' Lib/http/cookiejar.py(1)

__________________________________________________________________

The *note http.cookiejar: 95. 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: 95. 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: 2e78. raise this exception on
     failure to load cookies from a file.  *note LoadError: 2e77. is a
     subclass of *note OSError: 1d4.

     3.3 版更變: LoadError was made a subclass of *note OSError: 1d4.
     instead of *note IOError: 997.

The following classes are provided:

 -- 類別: http.cookiejar.CookieJar (policy=None)

     `policy' is an object implementing the *note CookiePolicy: 2e79.
     interface.

     The *note CookieJar: 2c7a. class stores HTTP cookies.  It extracts
     cookies from HTTP requests, and returns them in HTTP responses.
     *note CookieJar: 2c7a. 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, delayload=None,
          policy=None)

     `policy' is an object implementing the *note CookiePolicy: 2e79.
     interface.  For the other arguments, see the documentation for the
     corresponding attributes.

     A *note CookieJar: 2c7a. 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(): 2e7a. or *note revert():
     2e7b. method is called.  Subclasses of this class are documented in
     section *note FileCookieJar subclasses and co-operation with web
     browsers: 2e7c.

     3.8 版更變: The filename parameter supports a *note path-like
     object: 36f.

 -- 類別: 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: 158, 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: 2e79. and *note DefaultCookiePolicy: ff3.
     objects.

     *note DefaultCookiePolicy: ff3. 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: 2e7d. is ‘True’, RFC 2109 cookies are
     ’downgraded’ by the *note CookieJar: 2c7a. instance to Netscape
     cookies, by setting the ‘version’ attribute of the *note Cookie:
     2e7e. instance to 0.  *note DefaultCookiePolicy: ff3. 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:
     95. construct their own *note Cookie: 2e7e. instances.  Instead, if
     necessary, call ‘make_cookies()’ on a *note CookieJar: 2c7a.
     instance.

也參考
......

Module *note urllib.request: 121.

     URL opening with automatic cookie handling.

Module *note http.cookies: 96.

     HTTP cookie classes, principally useful for server-side code.  The
     *note http.cookiejar: 95. and *note http.cookies: 96. modules do
     not depend on each other.

‘https://curl.haxx.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:
     95.) 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 and FileCookieJar Objects::
* FileCookieJar subclasses and co-operation with web browsers::
* CookiePolicy Objects::
* DefaultCookiePolicy Objects::
* Cookie Objects: Cookie Objects<2>.
* Examples: Examples<24>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/http/cookiejar.py

   (2) https://tools.ietf.org/html/rfc2965.html

   (3) https://tools.ietf.org/html/rfc2109.html

   (4) https://tools.ietf.org/html/rfc2965.html

   (5) https://tools.ietf.org/html/rfc2109.html

   (6) https://tools.ietf.org/html/rfc2109.html

   (7) https://tools.ietf.org/html/rfc2965.html

   (8) https://tools.ietf.org/html/rfc2109.html

   (9) https://tools.ietf.org/html/rfc2965.html

   (10) https://tools.ietf.org/html/rfc2965.html

   (11) https://tools.ietf.org/html/rfc2965.html

   (12) https://tools.ietf.org/html/rfc2964.html


File: python.info,  Node: CookieJar and FileCookieJar Objects,  Next: FileCookieJar subclasses and co-operation with web browsers,  Up: http cookiejar --- Cookie handling for HTTP clients

5.21.24.1 CookieJar and FileCookieJar Objects
.............................................

*note CookieJar: 2c7a. objects support the *note iterator: 1040.
protocol for iterating over contained *note Cookie: 2e7e. objects.

*note CookieJar: 2c7a. 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: 2c7a.’s *note CookiePolicy: 2e79. instance
     are true and false respectively), the ‘Cookie2’ header is also
     added when appropriate.

     The `request' object (usually a *note urllib.request.Request: 8fb.
     instance) must support the methods ‘get_full_url()’, ‘get_host()’,
     ‘get_type()’, ‘unverifiable()’, ‘has_header()’, ‘get_header()’,
     ‘header_items()’, ‘add_unredirected_header()’ and ‘origin_req_host’
     attribute as documented by *note urllib.request: 121.

     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: 2c7a, where allowed by policy.

     The *note CookieJar: 2c7a. 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(): 2e83.
     method’s approval).

     The `response' object (usually the result of a call to *note
     urllib.request.urlopen(): 791, or similar) should support an
     ‘info()’ method, which returns an *note email.message.Message: 546.
     instance.

     The `request' object (usually a *note urllib.request.Request: 8fb.
     instance) must support the methods ‘get_full_url()’, ‘get_host()’,
     ‘unverifiable()’, and ‘origin_req_host’ attribute, as documented by
     *note urllib.request: 121.  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: 2e79. instance to be used.

 -- 成員函式: CookieJar.make_cookies (response, request)

     Return sequence of *note Cookie: 2e7e. objects extracted from
     `response' object.

     See the documentation for *note extract_cookies(): 2e82. for the
     interfaces required of the `response' and `request' arguments.

 -- 成員函式: CookieJar.set_cookie_if_ok (cookie, request)

     Set a *note Cookie: 2e7e. if policy says it’s OK to do so.

 -- 成員函式: CookieJar.set_cookie (cookie)

     Set a *note Cookie: 2e7e, 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: 2c8. 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: 2e78. 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: 613.  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: 158, *note ValueError: 1fc. 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(): 2e7a. or *note revert(): 2e7b. 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(): 2e8a.

     The named file must be in the format understood by the class, or
     *note LoadError: 2e77. will be raised.  Also, *note OSError: 1d4.
     may be raised, for example if the file does not exist.

     3.3 版更變: *note IOError: 997. used to be raised, it is now an
     alias of *note OSError: 1d4.

 -- 成員函式: FileCookieJar.revert (filename=None, ignore_discard=False,
          ignore_expires=False)

     Clear all cookies and reload cookies from a saved file.

     *note revert(): 2e7b. can raise the same exceptions as *note
     load(): 2e7a.  If there is a failure, the object’s state will not
     be altered.

*note FileCookieJar: 2e78. 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: 2c7a. object may ignore it.  None of
     the *note FileCookieJar: 2e78. classes included in the standard
     library lazily loads cookies.


File: python.info,  Node: FileCookieJar subclasses and co-operation with web browsers,  Next: CookiePolicy Objects,  Prev: CookieJar and FileCookieJar Objects,  Up: http cookiejar --- Cookie handling for HTTP clients

5.21.24.2 FileCookieJar subclasses and co-operation with web browsers
.....................................................................

The following *note CookieJar: 2c7a. subclasses are provided for reading
and writing.

 -- 類別: http.cookiejar.MozillaCookieJar (filename, delayload=None,
          policy=None)

     A *note FileCookieJar: 2e78. that can load from and save cookies to
     disk in the Mozilla ‘cookies.txt’ file format (which is also used
     by 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, delayload=None,
          policy=None)

     A *note FileCookieJar: 2e78. 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: 36f.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2965.html


File: python.info,  Node: CookiePolicy Objects,  Next: DefaultCookiePolicy Objects,  Prev: FileCookieJar subclasses and co-operation with web browsers,  Up: http cookiejar --- Cookie handling for HTTP clients

5.21.24.3 CookiePolicy Objects
..............................

Objects implementing the *note CookiePolicy: 2e79. 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: 2e7e. instance.  `request' is an object
     implementing the interface defined by the documentation for *note
     CookieJar.extract_cookies(): 2e82.

 -- 成員函式: CookiePolicy.return_ok (cookie, request)

     Return boolean value indicating whether cookie should be returned
     to server.

     `cookie' is a *note Cookie: 2e7e. instance.  `request' is an object
     implementing the interface defined by the documentation for *note
     CookieJar.add_cookie_header(): 2e81.

 -- 成員函式: 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(): 2e93.
     and *note path_return_ok(): 2e94. leaves all the work to *note
     return_ok(): 2e92.

     If *note domain_return_ok(): 2e93. returns true for the cookie
     domain, *note path_return_ok(): 2e94. is called for the cookie
     path.  Otherwise, *note path_return_ok(): 2e94. and *note
     return_ok(): 2e92. are never called for that cookie domain.  If
     *note path_return_ok(): 2e94. returns true, *note return_ok():
     2e92. is called with the *note Cookie: 2e7e. object itself for a
     full check.  Otherwise, *note return_ok(): 2e92. is never called
     for that cookie path.

     Note that *note domain_return_ok(): 2e93. 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(): 2e94.

     The `request' argument is as documented for *note return_ok():
     2e92.

 -- 成員函式: CookiePolicy.path_return_ok (path, request)

     Return ‘False’ if cookies should not be returned, given cookie
     path.

     See the documentation for *note domain_return_ok(): 2e93.

In addition to implementing the methods above, implementations of the
*note CookiePolicy: 2e79. 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: 2e79. class is by
subclassing from *note DefaultCookiePolicy: ff3. and overriding some or
all of the methods above.  *note CookiePolicy: 2e79. 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://tools.ietf.org/html/rfc2965.html

   (2) https://tools.ietf.org/html/rfc2965.html


File: python.info,  Node: DefaultCookiePolicy Objects,  Next: Cookie Objects<2>,  Prev: CookiePolicy Objects,  Up: http cookiejar --- Cookie handling for HTTP clients

5.21.24.4 DefaultCookiePolicy Objects
.....................................

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: 2e79. 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 blacklist and whitelist is provided (both off by default).
Only domains not in the blacklist and present in the whitelist (if the
whitelist 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 a whitelist, you can turn it
off again by setting it to *note None: 158.

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
blacklist 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: ff3. 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 whether `domain' is on the blacklist for setting or
     receiving cookies.

 -- 成員函式: DefaultCookiePolicy.allowed_domains ()

     Return *note None: 158, or the sequence of allowed domains (as a
     tuple).

 -- 成員函式: DefaultCookiePolicy.set_allowed_domains (allowed_domains)

     Set the sequence of allowed domains, or *note None: 158.

 -- 成員函式: DefaultCookiePolicy.is_not_allowed (domain)

     Return whether `domain' is not on the whitelist for setting or
     receiving cookies.

*note DefaultCookiePolicy: ff3. 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: 2c7a. 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: 2e7e. instance
     to 0.  The default value is *note None: 158, 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

     Equivalent to ‘DomainStrictNoDots|DomainStrictNonDomain’.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2965.html

   (2) https://tools.ietf.org/html/rfc2109.html

   (3) https://tools.ietf.org/html/rfc2965.html

   (4) https://tools.ietf.org/html/rfc2965.html

   (5) https://tools.ietf.org/html/rfc2965.html

   (6) https://tools.ietf.org/html/rfc2965.html

   (7) https://tools.ietf.org/html/rfc2965.html


File: python.info,  Node: Cookie Objects<2>,  Next: Examples<24>,  Prev: DefaultCookiePolicy Objects,  Up: http cookiejar --- Cookie handling for HTTP clients

5.21.24.5 Cookie Objects
........................

*note Cookie: 2e7e. 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: 95. 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: 2e79. 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: 158.  Netscape cookies have *note version:
     2eac. 0.  RFC 2965(2) and RFC 2109(3) cookies have a ‘version’
     cookie-attribute of 1.  However, note that *note http.cookiejar:
     95. may ’downgrade’ RFC 2109 cookies to Netscape cookies, in which
     case *note version: 2eac. is 0.

 -- 屬性: Cookie.name

     Cookie name (a string).

 -- 屬性: Cookie.value

     Cookie value (a string), or *note None: 158.

 -- 屬性: Cookie.port

     String representing a port or a set of ports (eg.  ’80’, or
     ’80,8080’), or *note None: 158.

 -- 屬性: 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: 158.
     See also the *note is_expired(): 2eb3. 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: 158.

 -- 屬性: Cookie.comment_url

     URL linking to a comment from the server explaining the function of
     this cookie, or *note None: 158.

 -- 屬性: 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: 95. may ’downgrade’ RFC 2109
     cookies to Netscape cookies, in which case *note version: 2eac. 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: 2e7e. 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://tools.ietf.org/html/rfc2109.html

   (2) https://tools.ietf.org/html/rfc2965.html

   (3) https://tools.ietf.org/html/rfc2109.html

   (4) https://tools.ietf.org/html/rfc2109.html


File: python.info,  Node: Examples<24>,  Prev: Cookie Objects<2>,  Up: http cookiejar --- Cookie handling for HTTP clients

5.21.24.6 Examples
..................

The first example shows the most common usage of *note http.cookiejar:
95.:

     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: ff3.
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://tools.ietf.org/html/rfc2965.html


File: python.info,  Node: xmlrpc --- XMLRPC server and client modules,  Next: xmlrpc client --- XML-RPC client access,  Prev: http cookiejar --- Cookie handling for HTTP clients,  Up: Internet Protocols and Support

5.21.25 ‘xmlrpc’ — XMLRPC server and client modules
---------------------------------------------------

XML-RPC is a Remote Procedure Call method that uses XML passed via HTTP
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.

‘xmlrpc’ is a package that collects server and client modules
implementing XML-RPC. The modules are:

   * *note xmlrpc.client: 140.

   * *note xmlrpc.server: 141.


File: python.info,  Node: xmlrpc client --- XML-RPC client access,  Next: xmlrpc server --- Basic XML-RPC servers,  Prev: xmlrpc --- XMLRPC server and client modules,  Up: Internet Protocols and Support

5.21.26 ‘xmlrpc.client’ — XML-RPC client access
-----------------------------------------------

`Source code:' 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: 140. module is not secure against
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML vulnerabilities: 29fa.

3.5 版更變: For HTTPS URIs, *note xmlrpc.client: 140. now performs all
the necessary certificate and hostname checks by default.

 -- 類別: 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: 256. 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: 193.  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: 195.
     objects and binary data to be presented as *note bytes: 336.
     objects; this flag is false by default.  *note datetime.datetime:
     195, *note bytes: 336. and *note bytearray: 337. 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 版更變: The `use_builtin_types' flag was added.

3.8 版更變: The `headers' parameter was added.

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: 3e9. 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: 184.
                           
                           
‘int’, ‘i1’, ‘i2’, ‘i4’,   *note int: 185. in range from -2147483648 to 2147483647.
‘i8’ or ‘biginteger’       Values get the ‘<int>’ tag.
                           
                           
‘double’ or ‘float’        *note float: 188.  Values get the ‘<double>’ tag.
                           
                           
‘string’                   *note str: 335.
                           
                           
‘array’                    *note list: 263. or *note tuple: 483. containing
                           conformable elements.  Arrays are returned as
                           *note lists: 263.
                           
                           
‘struct’                   *note dict: 1b9.  Keys must be strings, values may be any
                           conformable type.  Objects of user-defined classes can be
                           passed in; only their *note __dict__: 501. attribute is
                           transmitted.
                           
                           
‘dateTime.iso8601’         *note DateTime: 2ec3. or *note datetime.datetime: 195.
                           Returned type depends on values of `use_builtin_types'
                           and `use_datetime' flags.
                           
                           
‘base64’                   *note Binary: 2ec4, *note bytes: 336. or
                           *note bytearray: 337.  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: 189.  Returned type only.
                           

This is the full set of data types supported by XML-RPC. Method calls
may also raise a special *note Fault: 2ec5. instance, used to signal
XML-RPC server errors, or *note ProtocolError: 2ec6. used to signal an
error in the HTTP/HTTPS transport layer.  Both *note Fault: 2ec5. and
*note ProtocolError: 2ec6. 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: 336. or *note bytearray: 337. classes or the *note Binary:
2ec4. wrapper class described below.

‘Server’ is retained as an alias for *note ServerProxy: 256. for
backwards compatibility.  New code should use *note ServerProxy: 256.

3.5 版更變: Added the `context' argument.

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 ‘http://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.

Unofficial XML-RPC Errata(6)

     Fredrik Lundh’s "unofficial errata, intended to clarify certain
     details in the XML-RPC specification, as well as hint at ’best
     practices’ to use when designing your own XML-RPC implementations."

* Menu:

* ServerProxy Objects::
* 日期時間物件::
* Binary Objects::
* Fault Objects::
* ProtocolError Objects::
* MultiCall Objects::
* Convenience Functions::
* Example of Client Usage::
* Example of Client and Server Usage::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/xmlrpc/client.py

   (2) 
https://web.archive.org/web/20130120074804/http://ontosys.com/xml-rpc/extensions.php

   (3) http://www.tldp.org/HOWTO/XML-RPC-HOWTO/index.html

   (4) http://xmlrpc-c.sourceforge.net/introspection.html

   (5) http://xmlrpc.scripting.com/spec.html

   (6) http://effbot.org/zone/xmlrpc-errata.htm


File: python.info,  Node: ServerProxy Objects,  Next: 日期時間物件,  Up: xmlrpc client --- XML-RPC client access

5.21.26.1 ServerProxy Objects
.............................

A *note ServerProxy: 256. 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: 2ec5. or *note
ProtocolError: 2ec6. 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: 256. support the *note
context manager: 56d. 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 Objects,  Up: xmlrpc client --- XML-RPC client access

5.21.26.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:
     195. 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: 2ec3. item
          to the `out' stream object.

     It also supports certain of Python’s built-in operators through
     rich comparison and *note __repr__(): 343. 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()
     # convert the ISO8601 string to a datetime object
     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 client access

5.21.26.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: 2ec4.
     object is provided by an attribute:

      -- 屬性: data

          The binary data encapsulated by the *note Binary: 2ec4.
          instance.  The data is provided as a *note bytes: 336. object.

     *note Binary: 2ec4. objects have the following methods, supported
     mainly for internal use by the marshalling/unmarshalling code:

      -- 成員函式: decode (bytes)

          Accept a base64 *note bytes: 336. 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__(): 344. and *note __ne__(): e5b. 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://tools.ietf.org/html/rfc2045.html#section-6.8


File: python.info,  Node: Fault Objects,  Next: ProtocolError Objects,  Prev: Binary Objects,  Up: xmlrpc client --- XML-RPC client access

5.21.26.4 Fault Objects
.......................

 -- 類別: xmlrpc.client.Fault

     A *note Fault: 2ec5. object encapsulates the content of an XML-RPC
     fault tag.  Fault objects have the following attributes:

      -- 屬性: faultCode

          A string 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: 2ec5. 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 Objects,  Next: MultiCall Objects,  Prev: Fault Objects,  Up: xmlrpc client --- XML-RPC client access

5.21.26.5 ProtocolError Objects
...............................

 -- 類別: xmlrpc.client.ProtocolError

     A *note ProtocolError: 2ec6. 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: 2ec6. 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 Objects,  Next: Convenience Functions,  Prev: ProtocolError Objects,  Up: xmlrpc client --- XML-RPC client access

5.21.26.6 MultiCall Objects
...........................

The *note MultiCall: 2ee0. 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: 2ee0. 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: 9a7.; 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) (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: Convenience Functions,  Next: Example of Client Usage,  Prev: MultiCall Objects,  Up: xmlrpc client --- XML-RPC client access

5.21.26.7 Convenience Functions
...............................

 -- 函式: 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: 2ec5. 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: 158. 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: 2ec5. exception.  The
     `use_builtin_types' flag can be used to cause date/time values to
     be presented as *note datetime.datetime: 195. objects and binary
     data to be presented as *note bytes: 336. 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 版更變: The `use_builtin_types' flag was added.


File: python.info,  Node: Example of Client Usage,  Next: Example of Client and Server Usage,  Prev: Convenience Functions,  Up: xmlrpc client --- XML-RPC client access

5.21.26.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 client access

5.21.26.9 Example of Client and Server Usage
............................................

See *note SimpleXMLRPCServer Example: 2ee7.

註解
....


File: python.info,  Node: xmlrpc server --- Basic XML-RPC servers,  Next: ipaddress --- IPv4/IPv6 manipulation library,  Prev: xmlrpc client --- XML-RPC client access,  Up: Internet Protocols and Support

5.21.27 ‘xmlrpc.server’ — Basic XML-RPC servers
-----------------------------------------------

`Source code:' Lib/xmlrpc/server.py(1)

__________________________________________________________________

The *note xmlrpc.server: 141. module provides a basic server framework
for XML-RPC servers written in Python.  Servers can either be free
standing, using *note SimpleXMLRPCServer: 2eea, or embedded in a CGI
environment, using *note CGIXMLRPCRequestHandler: 2eeb.

     警告: The *note xmlrpc.server: 141. module is not secure against
     maliciously constructed data.  If you need to parse untrusted or
     unauthenticated data see *note XML vulnerabilities: 29fa.

 -- 類別: 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: 2eec.  The `addr' and `requestHandler'
     parameters are passed to the *note socketserver.TCPServer: 2e15.
     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: 140. 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(): 2ee3. 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: 140. and control the XML-RPC responses
     that will be returned from the server.  The `use_builtin_types'
     parameter is passed to the *note loads(): 2ee3. 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: 2eea.
     constructor parameter is honored.

* Menu:

* SimpleXMLRPCServer Objects::
* CGIXMLRPCRequestHandler::
* Documenting XMLRPC server::
* DocXMLRPCServer Objects::
* DocCGIXMLRPCRequestHandler::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/xmlrpc/server.py


File: python.info,  Node: SimpleXMLRPCServer Objects,  Next: CGIXMLRPCRequestHandler,  Up: xmlrpc server --- Basic XML-RPC servers

5.21.27.1 SimpleXMLRPCServer Objects
....................................

The *note SimpleXMLRPCServer: 2eea. class is based on *note
socketserver.TCPServer: 2e15. 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 ‘function.__name__’ 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,
     ‘function.__name__’ will be used.

     3.7 版更變: *note register_function(): 2eef. can be used as a
     decorator.

 -- 成員函式: 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(): 2eef.  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 Example::


File: python.info,  Node: SimpleXMLRPCServer Example,  Up: SimpleXMLRPCServer Objects

5.21.27.2 SimpleXMLRPCServer Example
....................................

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 Objects,  Up: xmlrpc server --- Basic XML-RPC servers

5.21.27.3 CGIXMLRPCRequestHandler
.................................

The *note CGIXMLRPCRequestHandler: 2eeb. 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 ‘function.__name__’ 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,
     ‘function.__name__’ will be used.

     3.7 版更變: *note register_function(): 2ef6. can be used as a
     decorator.

 -- 成員函式: CGIXMLRPCRequestHandler.register_instance (instance)

     Register an object which is used to expose method names which have
     not been registered using *note register_function(): 2ef6.  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.

Example:

     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 Objects,  Prev: CGIXMLRPCRequestHandler,  Up: xmlrpc server --- Basic XML-RPC servers

5.21.27.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: f7c, or embedded in a CGI environment,
using *note DocCGIXMLRPCRequestHandler: 2efc.

 -- 類別: 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: 2eea.; `requestHandler' defaults
     to *note DocXMLRPCRequestHandler: 2efd.

     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: f7c. constructor parameter is honored.


File: python.info,  Node: DocXMLRPCServer Objects,  Next: DocCGIXMLRPCRequestHandler,  Prev: Documenting XMLRPC server,  Up: xmlrpc server --- Basic XML-RPC servers

5.21.27.5 DocXMLRPCServer Objects
.................................

The *note DocXMLRPCServer: f7c. class is derived from *note
SimpleXMLRPCServer: 2eea. 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 Objects,  Up: xmlrpc server --- Basic XML-RPC servers

5.21.27.6 DocCGIXMLRPCRequestHandler
....................................

The *note DocCGIXMLRPCRequestHandler: 2efc. class is derived from *note
CGIXMLRPCRequestHandler: 2eeb. 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 manipulation library,  Prev: xmlrpc server --- Basic XML-RPC servers,  Up: Internet Protocols and Support

5.21.28 ‘ipaddress’ — IPv4/IPv6 manipulation library
----------------------------------------------------

`Source code:' Lib/ipaddress.py(1)

__________________________________________________________________

*note ipaddress: a3. 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模組介紹: 2f09.

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.8/Lib/ipaddress.py


File: python.info,  Node: Convenience factory functions,  Next: IP Addresses,  Up: ipaddress --- IPv4/IPv6 manipulation library

5.21.28.1 Convenience factory functions
.......................................

The *note ipaddress: a3. module provides factory functions to
conveniently create IP addresses, networks and interfaces:

 -- 函式: ipaddress.ip_address (address)

     Return an *note IPv4Address: 2f0c. or *note IPv6Address: 2f0d.
     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: 1fc. 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: 3a5. or *note IPv6Network: 3a4. 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: 3a5. or *note IPv6Network: 3a4. constructor.  A *note
     ValueError: 1fc. 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: 2f10. or *note IPv6Interface: 2f11.
     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: 1fc. 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 manipulation library

5.21.28.2 IP Addresses
......................

* Menu:

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


File: python.info,  Node: Address objects,  Next: Conversion to Strings and Integers,  Up: IP Addresses

5.21.28.3 Address objects
.........................

The *note IPv4Address: 2f0c. and *note IPv6Address: 2f0d. objects share
a lot of common attributes.  Some attributes that are only meaningful
for IPv6 addresses are also implemented by *note IPv4Address: 2f0c.
objects, in order to make it easier to write code that handles both IP
versions correctly.  Address objects are *note hashable: 142e, so they
can be used as keys in dictionaries.

 -- 類別: ipaddress.IPv4Address (address)

     Construct an IPv4 address.  An *note AddressValueError: 2f14. 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 tolerated only for values
          less than 8 (as there is no ambiguity between the decimal and
          octal interpretations of such strings).

       2. An integer that fits into 32 bits.

       3. An integer packed into a *note bytes: 336. 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')

      -- 屬性: 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:
          336. 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 allocated for private networks.  See
          iana-ipv4-special-registry(3) (for IPv4) or
          iana-ipv6-special-registry(4) (for IPv6).

      -- 屬性: is_global

          ‘True’ if the address is allocated for public networks.  See
          iana-ipv4-special-registry(5) (for IPv4) or
          iana-ipv6-special-registry(6) (for IPv6).

          3.4 版新加入.

      -- 屬性: 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).

 -- 類別: ipaddress.IPv6Address (address)

     Construct an IPv6 address.  An *note AddressValueError: 2f14. 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(12) for details.
          For example, ‘"0000:0000:0000:0000:0000:0abc:0007:0def"’ can
          be compressed to ‘"::abc:7:def"’.

       2. An integer that fits into 128 bits.

       3. An integer packed into a *note bytes: 336. object of length
          16, big-endian.

          >>> ipaddress.IPv6Address('2001:db8::1000')
          IPv6Address('2001:db8::1000')

      -- 屬性: 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, see the corresponding documentation
     of the *note IPv4Address: 2f0c. class:

      -- 屬性: packed

      -- 屬性: reverse_pointer

      -- 屬性: version

      -- 屬性: max_prefixlen

      -- 屬性: is_multicast

      -- 屬性: is_private

      -- 屬性: is_global

      -- 屬性: is_unspecified

      -- 屬性: is_reserved

      -- 屬性: is_loopback

      -- 屬性: is_link_local

          3.4 版新加入: is_global

      -- 屬性: 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(13).  Use *note is_private: 2f1c. to test if this address
          is in the space of unique local addresses as defined by RFC
          4193(14).

      -- 屬性: 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’.

      -- 屬性: sixtofour

          For addresses that appear to be 6to4 addresses (starting with
          ‘2002::/16’) as defined by RFC 3056(15), 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(16), this property
          will report the embedded ‘(server, client)’ IP address pair.
          For any other address, this property will be ‘None’.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc3171.html

   (2) https://tools.ietf.org/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://tools.ietf.org/html/rfc5735.html

   (8) https://tools.ietf.org/html/rfc2373.html

   (9) https://tools.ietf.org/html/rfc3330.html

   (10) https://tools.ietf.org/html/rfc2373.html

   (11) https://tools.ietf.org/html/rfc3927.html

   (12) https://tools.ietf.org/html/rfc4291.html

   (13) https://tools.ietf.org/html/rfc3879.html

   (14) https://tools.ietf.org/html/rfc4193.html

   (15) https://tools.ietf.org/html/rfc3056.html

   (16) https://tools.ietf.org/html/rfc4380.html


File: python.info,  Node: Conversion to Strings and Integers,  Next: Operators<3>,  Prev: Address objects,  Up: IP Addresses

5.21.28.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(): 335. and *note int(): 185. 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


File: python.info,  Node: Operators<3>,  Prev: Conversion to Strings and Integers,  Up: IP Addresses

5.21.28.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<3>

5.21.28.6 Comparison operators
..............................

Address objects can be compared with the usual set of comparison
operators.  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


File: python.info,  Node: Arithmetic operators,  Prev: Comparison operators,  Up: Operators<3>

5.21.28.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 manipulation library

5.21.28.8 IP Network definitions
................................

The *note IPv4Network: 3a5. and *note IPv6Network: 3a4. 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<4>.


File: python.info,  Node: Prefix net mask and host mask,  Next: Network objects,  Up: IP Network definitions

5.21.28.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<4>,  Prev: Prefix net mask and host mask,  Up: IP Network definitions

5.21.28.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: 3a5. and
*note IPv6Network: 3a4, so to avoid duplication they are only documented
for *note IPv4Network: 3a5.  Network objects are *note hashable: 142e,
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: 336. 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: 2f14. is raised if `address' is not a
     valid IPv4 address.  A *note NetmaskValueError: 2f39. 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: 1fc. 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: 193. 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: 2f0c.

      -- 屬性: 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: 2f0c. object.

      -- 屬性: netmask

          The net mask, as an *note IPv4Address: 2f0c. 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: 1fc. 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::’ 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: 336. 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: 2f14. is raised if `address' is not a
     valid IPv6 address.  A *note NetmaskValueError: 2f39. 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: 1fc. 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: 3a5.

      -- 屬性: 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<4>,  Prev: Network objects,  Up: IP Network definitions

5.21.28.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: Iteration<2>.
* Networks as containers of addresses::


File: python.info,  Node: Logical operators,  Next: Iteration<2>,  Up: Operators<4>

5.21.28.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<2>,  Next: Networks as containers of addresses,  Prev: Logical operators,  Up: Operators<4>

5.21.28.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(): 2f4d. 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<2>,  Up: Operators<4>

5.21.28.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 manipulation library

5.21.28.15 Interface objects
............................

Interface objects are *note hashable: 142e, 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: 3a5, except that arbitrary host
     addresses are always accepted.

     *note IPv4Interface: 2f10. is a subclass of *note IPv4Address:
     2f0c, so it inherits all the attributes from that class.  In
     addition, the following attributes are available:

      -- 屬性: ip

          The address (*note IPv4Address: 2f0c.) without network
          information.

               >>> interface = IPv4Interface('192.0.2.5/24')
               >>> interface.ip
               IPv4Address('192.0.2.5')

      -- 屬性: network

          The network (*note IPv4Network: 3a5.) 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: 3a4, except that arbitrary host
     addresses are always accepted.

     *note IPv6Interface: 2f11. is a subclass of *note IPv6Address:
     2f0d, 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: 2f10.

* Menu:

* Operators: Operators<5>.


File: python.info,  Node: Operators<5>,  Up: Interface objects

5.21.28.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<5>

5.21.28.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 manipulation library

5.21.28.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: 1fc. 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: 1fc. 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:
     2f0c. or *note IPv6Address: 2f0d. in the range and `last' is the
     last *note IPv4Address: 2f0c. or *note IPv6Address: 2f0d. in the
     range.  A *note TypeError: 193. is raised if `first' or `last' are
     not IP addresses or are not of the same version.  A *note
     ValueError: 1fc. 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: 3a5. or
     *note IPv6Network: 3a4. objects.  `addresses' is an iterator of
     *note IPv4Network: 3a5. or *note IPv6Network: 3a4. objects.  A
     *note TypeError: 193. 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: a3. sort these anyway.  If you need
     to do this, you can use this function as the `key' argument to
     *note sorted(): 449.

     `obj' is either a network or address object.


File: python.info,  Node: Custom Exceptions,  Prev: Other Module Level Functions,  Up: ipaddress --- IPv4/IPv6 manipulation library

5.21.28.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: Multimedia Services,  Next: 國際化,  Prev: Internet Protocols and Support,  Up: Python 標準函式庫 Standard Library

5.22 Multimedia Services
========================

The modules described in this chapter implement various algorithms or
interfaces that are mainly useful for multimedia applications.  They are
available at the discretion of the installation.  Here’s an overview:

* Menu:

* audioop: audioop --- Manipulate raw audio data. Manipulate raw audio data
* aifc: aifc --- Read and write AIFF and AIFC files. Read and write AIFF and AIFC files
* sunau: sunau --- Read and write Sun AU files. Read and write Sun AU files
* wave: wave --- Read and write WAV files. Read and write WAV files
* chunk: chunk --- Read IFF chunked data. Read IFF chunked data
* colorsys: colorsys --- Conversions between color systems. Conversions between color systems
* imghdr: imghdr --- Determine the type of an image. Determine the type of an image
* sndhdr: sndhdr --- Determine type of sound file. Determine type of sound file
* ossaudiodev: ossaudiodev --- Access to OSS-compatible audio devices. Access to OSS-compatible audio devices


File: python.info,  Node: audioop --- Manipulate raw audio data,  Next: aifc --- Read and write AIFF and AIFC files,  Up: Multimedia Services

5.22.1 ‘audioop’ — Manipulate raw audio data
--------------------------------------------

__________________________________________________________________

The *note audioop: d. module contains some useful operations on sound
fragments.  It operates on sound fragments consisting of signed integer
samples 8, 16, 24 or 32 bits wide, stored in *note bytes-like objects:
5ed.  All scalar items are integers, unless specified otherwise.

3.4 版更變: Support for 24-bit samples was added.  All functions now
accept any *note bytes-like object: 5ed.  String input now results in an
immediate error.

This module provides support for a-LAW, u-LAW and Intel/DVI ADPCM
encodings.

A few of the more complicated operations only take 16-bit samples,
otherwise the sample size (in bytes) is always a parameter of the
operation.

The module defines the following variables and functions:

 -- 例外: audioop.error

     This exception is raised on all errors, such as unknown number of
     bytes per sample, etc.

 -- 函式: audioop.add (fragment1, fragment2, width)

     Return a fragment which is the addition of the two samples passed
     as parameters.  `width' is the sample width in bytes, either ‘1’,
     ‘2’, ‘3’ or ‘4’.  Both fragments should have the same length.
     Samples are truncated in case of overflow.

 -- 函式: audioop.adpcm2lin (adpcmfragment, width, state)

     Decode an Intel/DVI ADPCM coded fragment to a linear fragment.  See
     the description of *note lin2adpcm(): 2f8d. for details on ADPCM
     coding.  Return a tuple ‘(sample, newstate)’ where the sample has
     the width specified in `width'.

 -- 函式: audioop.alaw2lin (fragment, width)

     Convert sound fragments in a-LAW encoding to linearly encoded sound
     fragments.  a-LAW encoding always uses 8 bits samples, so `width'
     refers only to the sample width of the output fragment here.

 -- 函式: audioop.avg (fragment, width)

     Return the average over all samples in the fragment.

 -- 函式: audioop.avgpp (fragment, width)

     Return the average peak-peak value over all samples in the
     fragment.  No filtering is done, so the usefulness of this routine
     is questionable.

 -- 函式: audioop.bias (fragment, width, bias)

     Return a fragment that is the original fragment with a bias added
     to each sample.  Samples wrap around in case of overflow.

 -- 函式: audioop.byteswap (fragment, width)

     "Byteswap" all samples in a fragment and returns the modified
     fragment.  Converts big-endian samples to little-endian and vice
     versa.

     3.4 版新加入.

 -- 函式: audioop.cross (fragment, width)

     Return the number of zero crossings in the fragment passed as an
     argument.

 -- 函式: audioop.findfactor (fragment, reference)

     Return a factor `F' such that ‘rms(add(fragment, mul(reference,
     -F)))’ is minimal, i.e., return the factor with which you should
     multiply `reference' to make it match as well as possible to
     `fragment'.  The fragments should both contain 2-byte samples.

     The time taken by this routine is proportional to ‘len(fragment)’.

 -- 函式: audioop.findfit (fragment, reference)

     Try to match `reference' as well as possible to a portion of
     `fragment' (which should be the longer fragment).  This is
     (conceptually) done by taking slices out of `fragment', using *note
     findfactor(): 2f93. to compute the best match, and minimizing the
     result.  The fragments should both contain 2-byte samples.  Return
     a tuple ‘(offset, factor)’ where `offset' is the (integer) offset
     into `fragment' where the optimal match started and `factor' is the
     (floating-point) factor as per *note findfactor(): 2f93.

 -- 函式: audioop.findmax (fragment, length)

     Search `fragment' for a slice of length `length' samples (not
     bytes!)  with maximum energy, i.e., return `i' for which
     ‘rms(fragment[i*2:(i+length)*2])’ is maximal.  The fragments should
     both contain 2-byte samples.

     The routine takes time proportional to ‘len(fragment)’.

 -- 函式: audioop.getsample (fragment, width, index)

     Return the value of sample `index' from the fragment.

 -- 函式: audioop.lin2adpcm (fragment, width, state)

     Convert samples to 4 bit Intel/DVI ADPCM encoding.  ADPCM coding is
     an adaptive coding scheme, whereby each 4 bit number is the
     difference between one sample and the next, divided by a (varying)
     step.  The Intel/DVI ADPCM algorithm has been selected for use by
     the IMA, so it may well become a standard.

     `state' is a tuple containing the state of the coder.  The coder
     returns a tuple ‘(adpcmfrag, newstate)’, and the `newstate' should
     be passed to the next call of *note lin2adpcm(): 2f8d.  In the
     initial call, ‘None’ can be passed as the state.  `adpcmfrag' is
     the ADPCM coded fragment packed 2 4-bit values per byte.

 -- 函式: audioop.lin2alaw (fragment, width)

     Convert samples in the audio fragment to a-LAW encoding and return
     this as a bytes object.  a-LAW is an audio encoding format whereby
     you get a dynamic range of about 13 bits using only 8 bit samples.
     It is used by the Sun audio hardware, among others.

 -- 函式: audioop.lin2lin (fragment, width, newwidth)

     Convert samples between 1-, 2-, 3- and 4-byte formats.

          備註: In some audio formats, such as .WAV files, 16, 24 and 32
          bit samples are signed, but 8 bit samples are unsigned.  So
          when converting to 8 bit wide samples for these formats, you
          need to also add 128 to the result:

               new_frames = audioop.lin2lin(frames, old_width, 1)
               new_frames = audioop.bias(new_frames, 1, 128)

          The same, in reverse, has to be applied when converting from 8
          to 16, 24 or 32 bit width samples.

 -- 函式: audioop.lin2ulaw (fragment, width)

     Convert samples in the audio fragment to u-LAW encoding and return
     this as a bytes object.  u-LAW is an audio encoding format whereby
     you get a dynamic range of about 14 bits using only 8 bit samples.
     It is used by the Sun audio hardware, among others.

 -- 函式: audioop.max (fragment, width)

     Return the maximum of the `absolute value' of all samples in a
     fragment.

 -- 函式: audioop.maxpp (fragment, width)

     Return the maximum peak-peak value in the sound fragment.

 -- 函式: audioop.minmax (fragment, width)

     Return a tuple consisting of the minimum and maximum values of all
     samples in the sound fragment.

 -- 函式: audioop.mul (fragment, width, factor)

     Return a fragment that has all samples in the original fragment
     multiplied by the floating-point value `factor'.  Samples are
     truncated in case of overflow.

 -- 函式: audioop.ratecv (fragment, width, nchannels, inrate, outrate,
          state[, weightA[, weightB]])

     Convert the frame rate of the input fragment.

     `state' is a tuple containing the state of the converter.  The
     converter returns a tuple ‘(newfragment, newstate)’, and `newstate'
     should be passed to the next call of *note ratecv(): 2f9e.  The
     initial call should pass ‘None’ as the state.

     The `weightA' and `weightB' arguments are parameters for a simple
     digital filter and default to ‘1’ and ‘0’ respectively.

 -- 函式: audioop.reverse (fragment, width)

     Reverse the samples in a fragment and returns the modified
     fragment.

 -- 函式: audioop.rms (fragment, width)

     Return the root-mean-square of the fragment, i.e.
     ‘sqrt(sum(S_i^2)/n)’.

     This is a measure of the power in an audio signal.

 -- 函式: audioop.tomono (fragment, width, lfactor, rfactor)

     Convert a stereo fragment to a mono fragment.  The left channel is
     multiplied by `lfactor' and the right channel by `rfactor' before
     adding the two channels to give a mono signal.

 -- 函式: audioop.tostereo (fragment, width, lfactor, rfactor)

     Generate a stereo fragment from a mono fragment.  Each pair of
     samples in the stereo fragment are computed from the mono sample,
     whereby left channel samples are multiplied by `lfactor' and right
     channel samples by `rfactor'.

 -- 函式: audioop.ulaw2lin (fragment, width)

     Convert sound fragments in u-LAW encoding to linearly encoded sound
     fragments.  u-LAW encoding always uses 8 bits samples, so `width'
     refers only to the sample width of the output fragment here.

Note that operations such as *note mul(): 2f9d. or *note max(): 2f9a.
make no distinction between mono and stereo fragments, i.e.  all samples
are treated equal.  If this is a problem the stereo fragment should be
split into two mono fragments first and recombined later.  Here is an
example of how to do that:

     def mul_stereo(sample, width, lfactor, rfactor):
         lsample = audioop.tomono(sample, width, 1, 0)
         rsample = audioop.tomono(sample, width, 0, 1)
         lsample = audioop.mul(lsample, width, lfactor)
         rsample = audioop.mul(rsample, width, rfactor)
         lsample = audioop.tostereo(lsample, width, 1, 0)
         rsample = audioop.tostereo(rsample, width, 0, 1)
         return audioop.add(lsample, rsample, width)

If you use the ADPCM coder to build network packets and you want your
protocol to be stateless (i.e.  to be able to tolerate packet loss) you
should not only transmit the data but also the state.  Note that you
should send the `initial' state (the one you passed to *note
lin2adpcm(): 2f8d.) along to the decoder, not the final state (as
returned by the coder).  If you want to use *note struct.Struct: 1812.
to store the state in binary you can code the first element (the
predicted value) in 16 bits and the second (the delta index) in 8.

The ADPCM coders have never been tried against other ADPCM coders, only
against themselves.  It could well be that I misinterpreted the
standards in which case they will not be interoperable with the
respective standards.

The ‘find*()’ routines might look a bit funny at first sight.  They are
primarily meant to do echo cancellation.  A reasonably fast way to do
this is to pick the most energetic piece of the output sample, locate
that in the input sample and subtract the whole output sample from the
input sample:

     def echocancel(outputdata, inputdata):
         pos = audioop.findmax(outputdata, 800)    # one tenth second
         out_test = outputdata[pos*2:]
         in_test = inputdata[pos*2:]
         ipos, factor = audioop.findfit(in_test, out_test)
         # Optional (for better cancellation):
         # factor = audioop.findfactor(in_test[ipos*2:ipos*2+len(out_test)],
         #              out_test)
         prefill = '\0'*(pos+ipos)*2
         postfill = '\0'*(len(inputdata)-len(prefill)-len(outputdata))
         outputdata = prefill + audioop.mul(outputdata, 2, -factor) + postfill
         return audioop.add(inputdata, outputdata, 2)


File: python.info,  Node: aifc --- Read and write AIFF and AIFC files,  Next: sunau --- Read and write Sun AU files,  Prev: audioop --- Manipulate raw audio data,  Up: Multimedia Services

5.22.2 ‘aifc’ — Read and write AIFF and AIFC files
--------------------------------------------------

`Source code:' Lib/aifc.py(1)

__________________________________________________________________

This module provides support for reading and writing AIFF and AIFF-C
files.  AIFF is Audio Interchange File Format, a format for storing
digital audio samples in a file.  AIFF-C is a newer version of the
format that includes the ability to compress the audio data.

Audio files have a number of parameters that describe the audio data.
The sampling rate or frame rate is the number of times per second the
sound is sampled.  The number of channels indicate if the audio is mono,
stereo, or quadro.  Each frame consists of one sample per channel.  The
sample size is the size in bytes of each sample.  Thus a frame consists
of ‘nchannels * samplesize’ bytes, and a second’s worth of audio
consists of ‘nchannels * samplesize * framerate’ bytes.

For example, CD quality audio has a sample size of two bytes (16 bits),
uses two channels (stereo) and has a frame rate of 44,100 frames/second.
This gives a frame size of 4 bytes (2*2), and a second’s worth occupies
2*2*44100 bytes (176,400 bytes).

Module *note aifc: 5. defines the following function:

 -- 函式: aifc.open (file, mode=None)

     Open an AIFF or AIFF-C file and return an object instance with
     methods that are described below.  The argument `file' is either a
     string naming a file or a *note file object: b47.  `mode' must be
     ‘'r'’ or ‘'rb'’ when the file must be opened for reading, or ‘'w'’
     or ‘'wb'’ when the file must be opened for writing.  If omitted,
     ‘file.mode’ is used if it exists, otherwise ‘'rb'’ is used.  When
     used for writing, the file object should be seekable, unless you
     know ahead of time how many samples you are going to write in total
     and use ‘writeframesraw()’ and ‘setnframes()’.  The *note open():
     460. function may be used in a *note with: 6ee. statement.  When
     the ‘with’ block completes, the *note close(): 821. method is
     called.

     3.4 版更變: Support for the *note with: 6ee. statement was added.

Objects returned by *note open(): 460. when a file is opened for reading
have the following methods:

 -- 成員函式: aifc.getnchannels ()

     Return the number of audio channels (1 for mono, 2 for stereo).

 -- 成員函式: aifc.getsampwidth ()

     Return the size in bytes of individual samples.

 -- 成員函式: aifc.getframerate ()

     Return the sampling rate (number of audio frames per second).

 -- 成員函式: aifc.getnframes ()

     Return the number of audio frames in the file.

 -- 成員函式: aifc.getcomptype ()

     Return a bytes array of length 4 describing the type of compression
     used in the audio file.  For AIFF files, the returned value is
     ‘b'NONE'’.

 -- 成員函式: aifc.getcompname ()

     Return a bytes array convertible to a human-readable description of
     the type of compression used in the audio file.  For AIFF files,
     the returned value is ‘b'not compressed'’.

 -- 成員函式: aifc.getparams ()

     Returns a *note namedtuple(): 1b8. ‘(nchannels, sampwidth,
     framerate, nframes, comptype, compname)’, equivalent to output of
     the ‘get*()’ methods.

 -- 成員函式: aifc.getmarkers ()

     Return a list of markers in the audio file.  A marker consists of a
     tuple of three elements.  The first is the mark ID (an integer),
     the second is the mark position in frames from the beginning of the
     data (an integer), the third is the name of the mark (a string).

 -- 成員函式: aifc.getmark (id)

     Return the tuple as described in *note getmarkers(): 2fac. for the
     mark with the given `id'.

 -- 成員函式: aifc.readframes (nframes)

     Read and return the next `nframes' frames from the audio file.  The
     returned data is a string containing for each frame the
     uncompressed samples of all channels.

 -- 成員函式: aifc.rewind ()

     Rewind the read pointer.  The next *note readframes(): 2fae. will
     start from the beginning.

 -- 成員函式: aifc.setpos (pos)

     Seek to the specified frame number.

 -- 成員函式: aifc.tell ()

     Return the current frame number.

 -- 成員函式: aifc.close ()

     Close the AIFF file.  After calling this method, the object can no
     longer be used.

Objects returned by *note open(): 460. when a file is opened for writing
have all the above methods, except for ‘readframes()’ and ‘setpos()’.
In addition the following methods exist.  The ‘get*()’ methods can only
be called after the corresponding ‘set*()’ methods have been called.
Before the first ‘writeframes()’ or ‘writeframesraw()’, all parameters
except for the number of frames must be filled in.

 -- 成員函式: aifc.aiff ()

     Create an AIFF file.  The default is that an AIFF-C file is
     created, unless the name of the file ends in ‘'.aiff'’ in which
     case the default is an AIFF file.

 -- 成員函式: aifc.aifc ()

     Create an AIFF-C file.  The default is that an AIFF-C file is
     created, unless the name of the file ends in ‘'.aiff'’ in which
     case the default is an AIFF file.

 -- 成員函式: aifc.setnchannels (nchannels)

     Specify the number of channels in the audio file.

 -- 成員函式: aifc.setsampwidth (width)

     Specify the size in bytes of audio samples.

 -- 成員函式: aifc.setframerate (rate)

     Specify the sampling frequency in frames per second.

 -- 成員函式: aifc.setnframes (nframes)

     Specify the number of frames that are to be written to the audio
     file.  If this parameter is not set, or not set correctly, the file
     needs to support seeking.

 -- 成員函式: aifc.setcomptype (type, name)

     Specify the compression type.  If not specified, the audio data
     will not be compressed.  In AIFF files, compression is not
     possible.  The name parameter should be a human-readable
     description of the compression type as a bytes array, the type
     parameter should be a bytes array of length 4.  Currently the
     following compression types are supported: ‘b'NONE'’, ‘b'ULAW'’,
     ‘b'ALAW'’, ‘b'G722'’.

 -- 成員函式: aifc.setparams (nchannels, sampwidth, framerate, comptype,
          compname)

     Set all the above parameters at once.  The argument is a tuple
     consisting of the various parameters.  This means that it is
     possible to use the result of a *note getparams(): 820. call as
     argument to *note setparams(): 2fb9.

 -- 成員函式: aifc.setmark (id, pos, name)

     Add a mark with the given id (larger than 0), and the given name at
     the given position.  This method can be called at any time before
     *note close(): 821.

 -- 成員函式: aifc.tell ()

     Return the current write position in the output file.  Useful in
     combination with *note setmark(): 2fba.

 -- 成員函式: aifc.writeframes (data)

     Write data to the output file.  This method can only be called
     after the audio file parameters have been set.

     3.4 版更變: Any *note bytes-like object: 5ed. is now accepted.

 -- 成員函式: aifc.writeframesraw (data)

     Like *note writeframes(): 823, except that the header of the audio
     file is not updated.

     3.4 版更變: Any *note bytes-like object: 5ed. is now accepted.

 -- 成員函式: aifc.close ()

     Close the AIFF file.  The header of the file is updated to reflect
     the actual size of the audio data.  After calling this method, the
     object can no longer be used.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/aifc.py


File: python.info,  Node: sunau --- Read and write Sun AU files,  Next: wave --- Read and write WAV files,  Prev: aifc --- Read and write AIFF and AIFC files,  Up: Multimedia Services

5.22.3 ‘sunau’ — Read and write Sun AU files
--------------------------------------------

`Source code:' Lib/sunau.py(1)

__________________________________________________________________

The *note sunau: fb. module provides a convenient interface to the Sun
AU sound format.  Note that this module is interface-compatible with the
modules *note aifc: 5. and *note wave: 128.

An audio file consists of a header followed by the data.  The fields of
the header are:

Field               Contents
                    
------------------------------------------------------------------------
                    
magic word          The four bytes ‘.snd’.
                    
                    
header size         Size of the header, including info, in bytes.
                    
                    
data size           Physical size of the data, in bytes.
                    
                    
encoding            Indicates how the audio samples are encoded.
                    
                    
sample rate         The sampling rate.
                    
                    
# of channels       The number of channels in the samples.
                    
                    
info                ASCII string giving a description of the audio
                    file (padded with null bytes).
                    

Apart from the info field, all header fields are 4 bytes in size.  They
are all 32-bit unsigned integers encoded in big-endian byte order.

The *note sunau: fb. module defines the following functions:

 -- 函式: sunau.open (file, mode)

     If `file' is a string, open the file by that name, otherwise treat
     it as a seekable file-like object.  `mode' can be any of

     ‘'r'’

          Read only mode.

     ‘'w'’

          Write only mode.

     Note that it does not allow read/write files.

     A `mode' of ‘'r'’ returns an ‘AU_read’ object, while a `mode' of
     ‘'w'’ or ‘'wb'’ returns an ‘AU_write’ object.

 -- 函式: sunau.openfp (file, mode)

     A synonym for *note open(): 477, maintained for backwards
     compatibility.

     Deprecated since version 3.7, will be removed in version 3.9.

The *note sunau: fb. module defines the following exception:

 -- 例外: sunau.Error

     An error raised when something is impossible because of Sun AU
     specs or implementation deficiency.

The *note sunau: fb. module defines the following data items:

 -- Data: sunau.AUDIO_FILE_MAGIC

     An integer every valid Sun AU file begins with, stored in
     big-endian form.  This is the string ‘.snd’ interpreted as an
     integer.

 -- Data: sunau.AUDIO_FILE_ENCODING_MULAW_8
 -- Data: sunau.AUDIO_FILE_ENCODING_LINEAR_8
 -- Data: sunau.AUDIO_FILE_ENCODING_LINEAR_16
 -- Data: sunau.AUDIO_FILE_ENCODING_LINEAR_24
 -- Data: sunau.AUDIO_FILE_ENCODING_LINEAR_32
 -- Data: sunau.AUDIO_FILE_ENCODING_ALAW_8

     Values of the encoding field from the AU header which are supported
     by this module.

 -- Data: sunau.AUDIO_FILE_ENCODING_FLOAT
 -- Data: sunau.AUDIO_FILE_ENCODING_DOUBLE
 -- Data: sunau.AUDIO_FILE_ENCODING_ADPCM_G721
 -- Data: sunau.AUDIO_FILE_ENCODING_ADPCM_G722
 -- Data: sunau.AUDIO_FILE_ENCODING_ADPCM_G723_3
 -- Data: sunau.AUDIO_FILE_ENCODING_ADPCM_G723_5

     Additional known values of the encoding field from the AU header,
     but which are not supported by this module.

* Menu:

* AU_read Objects::
* AU_write Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/sunau.py


File: python.info,  Node: AU_read Objects,  Next: AU_write Objects,  Up: sunau --- Read and write Sun AU files

5.22.3.1 AU_read Objects
........................

AU_read objects, as returned by *note open(): 477. above, have the
following methods:

 -- 成員函式: AU_read.close ()

     Close the stream, and make the instance unusable.  (This is called
     automatically on deletion.)

 -- 成員函式: AU_read.getnchannels ()

     Returns number of audio channels (1 for mono, 2 for stereo).

 -- 成員函式: AU_read.getsampwidth ()

     Returns sample width in bytes.

 -- 成員函式: AU_read.getframerate ()

     Returns sampling frequency.

 -- 成員函式: AU_read.getnframes ()

     Returns number of audio frames.

 -- 成員函式: AU_read.getcomptype ()

     Returns compression type.  Supported compression types are
     ‘'ULAW'’, ‘'ALAW'’ and ‘'NONE'’.

 -- 成員函式: AU_read.getcompname ()

     Human-readable version of *note getcomptype(): 2fd2.  The supported
     types have the respective names ‘'CCITT G.711 u-law'’, ‘'CCITT
     G.711 A-law'’ and ‘'not compressed'’.

 -- 成員函式: AU_read.getparams ()

     Returns a *note namedtuple(): 1b8. ‘(nchannels, sampwidth,
     framerate, nframes, comptype, compname)’, equivalent to output of
     the ‘get*()’ methods.

 -- 成員函式: AU_read.readframes (n)

     Reads and returns at most `n' frames of audio, as a *note bytes:
     336. object.  The data will be returned in linear format.  If the
     original data is in u-LAW format, it will be converted.

 -- 成員函式: AU_read.rewind ()

     Rewind the file pointer to the beginning of the audio stream.

The following two methods define a term "position" which is compatible
between them, and is otherwise implementation dependent.

 -- 成員函式: AU_read.setpos (pos)

     Set the file pointer to the specified position.  Only values
     returned from *note tell(): 2fd8. should be used for `pos'.

 -- 成員函式: AU_read.tell ()

     Return current file pointer position.  Note that the returned value
     has nothing to do with the actual position in the file.

The following two functions are defined for compatibility with the *note
aifc: 5, and don’t do anything interesting.

 -- 成員函式: AU_read.getmarkers ()

     Returns ‘None’.

 -- 成員函式: AU_read.getmark (id)

     Raise an error.


File: python.info,  Node: AU_write Objects,  Prev: AU_read Objects,  Up: sunau --- Read and write Sun AU files

5.22.3.2 AU_write Objects
.........................

AU_write objects, as returned by *note open(): 477. above, have the
following methods:

 -- 成員函式: AU_write.setnchannels (n)

     Set the number of channels.

 -- 成員函式: AU_write.setsampwidth (n)

     Set the sample width (in bytes.)

     3.4 版更變: Added support for 24-bit samples.

 -- 成員函式: AU_write.setframerate (n)

     Set the frame rate.

 -- 成員函式: AU_write.setnframes (n)

     Set the number of frames.  This can be later changed, when and if
     more frames are written.

 -- 成員函式: AU_write.setcomptype (type, name)

     Set the compression type and description.  Only ‘'NONE'’ and
     ‘'ULAW'’ are supported on output.

 -- 成員函式: AU_write.setparams (tuple)

     The `tuple' should be ‘(nchannels, sampwidth, framerate, nframes,
     comptype, compname)’, with values valid for the ‘set*()’ methods.
     Set all parameters.

 -- 成員函式: AU_write.tell ()

     Return current position in the file, with the same disclaimer for
     the *note AU_read.tell(): 2fd8. and *note AU_read.setpos(): 2fd7.
     methods.

 -- 成員函式: AU_write.writeframesraw (data)

     Write audio frames, without correcting `nframes'.

     3.4 版更變: Any *note bytes-like object: 5ed. is now accepted.

 -- 成員函式: AU_write.writeframes (data)

     Write audio frames and make sure `nframes' is correct.

     3.4 版更變: Any *note bytes-like object: 5ed. is now accepted.

 -- 成員函式: AU_write.close ()

     Make sure `nframes' is correct, and close the file.

     This method is called upon deletion.

Note that it is invalid to set any parameters after calling
‘writeframes()’ or ‘writeframesraw()’.


File: python.info,  Node: wave --- Read and write WAV files,  Next: chunk --- Read IFF chunked data,  Prev: sunau --- Read and write Sun AU files,  Up: Multimedia Services

5.22.4 ‘wave’ — Read and write WAV files
----------------------------------------

`Source code:' Lib/wave.py(1)

__________________________________________________________________

The *note wave: 128. module provides a convenient interface to the WAV
sound format.  It does not support compression/decompression, but it
does support mono/stereo.

The *note wave: 128. module defines the following function and
exception:

 -- 函式: wave.open (file, mode=None)

     If `file' is a string, open the file by that name, otherwise treat
     it as a file-like object.  `mode' can be:

     ‘'rb'’

          Read only mode.

     ‘'wb'’

          Write only mode.

     Note that it does not allow read/write WAV files.

     A `mode' of ‘'rb'’ returns a ‘Wave_read’ object, while a `mode' of
     ‘'wb'’ returns a ‘Wave_write’ object.  If `mode' is omitted and a
     file-like object is passed as `file', ‘file.mode’ is used as the
     default value for `mode'.

     If you pass in a file-like object, the wave object will not close
     it when its ‘close()’ method is called; it is the caller’s
     responsibility to close the file object.

     The *note open(): 47b. function may be used in a *note with: 6ee.
     statement.  When the ‘with’ block completes, the *note
     Wave_read.close(): 2fe6. or *note Wave_write.close(): 2fe7. method
     is called.

     3.4 版更變: Added support for unseekable files.

 -- 函式: wave.openfp (file, mode)

     A synonym for *note open(): 47b, maintained for backwards
     compatibility.

     Deprecated since version 3.7, will be removed in version 3.9.

 -- 例外: wave.Error

     An error raised when something is impossible because it violates
     the WAV specification or hits an implementation deficiency.

* Menu:

* Wave_read Objects::
* Wave_write Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/wave.py


File: python.info,  Node: Wave_read Objects,  Next: Wave_write Objects,  Up: wave --- Read and write WAV files

5.22.4.1 Wave_read Objects
..........................

Wave_read objects, as returned by *note open(): 47b, have the following
methods:

 -- 成員函式: Wave_read.close ()

     Close the stream if it was opened by *note wave: 128, and make the
     instance unusable.  This is called automatically on object
     collection.

 -- 成員函式: Wave_read.getnchannels ()

     Returns number of audio channels (‘1’ for mono, ‘2’ for stereo).

 -- 成員函式: Wave_read.getsampwidth ()

     Returns sample width in bytes.

 -- 成員函式: Wave_read.getframerate ()

     Returns sampling frequency.

 -- 成員函式: Wave_read.getnframes ()

     Returns number of audio frames.

 -- 成員函式: Wave_read.getcomptype ()

     Returns compression type (‘'NONE'’ is the only supported type).

 -- 成員函式: Wave_read.getcompname ()

     Human-readable version of *note getcomptype(): 2fef.  Usually ‘'not
     compressed'’ parallels ‘'NONE'’.

 -- 成員函式: Wave_read.getparams ()

     Returns a *note namedtuple(): 1b8. ‘(nchannels, sampwidth,
     framerate, nframes, comptype, compname)’, equivalent to output of
     the ‘get*()’ methods.

 -- 成員函式: Wave_read.readframes (n)

     Reads and returns at most `n' frames of audio, as a *note bytes:
     336. object.

 -- 成員函式: Wave_read.rewind ()

     Rewind the file pointer to the beginning of the audio stream.

The following two methods are defined for compatibility with the *note
aifc: 5. module, and don’t do anything interesting.

 -- 成員函式: Wave_read.getmarkers ()

     Returns ‘None’.

 -- 成員函式: Wave_read.getmark (id)

     Raise an error.

The following two methods define a term "position" which is compatible
between them, and is otherwise implementation dependent.

 -- 成員函式: Wave_read.setpos (pos)

     Set the file pointer to the specified position.

 -- 成員函式: Wave_read.tell ()

     Return current file pointer position.


File: python.info,  Node: Wave_write Objects,  Prev: Wave_read Objects,  Up: wave --- Read and write WAV files

5.22.4.2 Wave_write Objects
...........................

For seekable output streams, the ‘wave’ header will automatically be
updated to reflect the number of frames actually written.  For
unseekable streams, the `nframes' value must be accurate when the first
frame data is written.  An accurate `nframes' value can be achieved
either by calling *note setnframes(): 2ff9. or *note setparams(): 2ffa.
with the number of frames that will be written before *note close():
2fe7. is called and then using *note writeframesraw(): 911. to write the
frame data, or by calling *note writeframes(): 912. with all of the
frame data to be written.  In the latter case *note writeframes(): 912.
will calculate the number of frames in the data and set `nframes'
accordingly before writing the frame data.

Wave_write objects, as returned by *note open(): 47b, have the following
methods:

3.4 版更變: Added support for unseekable files.

 -- 成員函式: Wave_write.close ()

     Make sure `nframes' is correct, and close the file if it was opened
     by *note wave: 128.  This method is called upon object collection.
     It will raise an exception if the output stream is not seekable and
     `nframes' does not match the number of frames actually written.

 -- 成員函式: Wave_write.setnchannels (n)

     Set the number of channels.

 -- 成員函式: Wave_write.setsampwidth (n)

     Set the sample width to `n' bytes.

 -- 成員函式: Wave_write.setframerate (n)

     Set the frame rate to `n'.

     3.2 版更變: A non-integral input to this method is rounded to the
     nearest integer.

 -- 成員函式: Wave_write.setnframes (n)

     Set the number of frames to `n'.  This will be changed later if the
     number of frames actually written is different (this update attempt
     will raise an error if the output stream is not seekable).

 -- 成員函式: Wave_write.setcomptype (type, name)

     Set the compression type and description.  At the moment, only
     compression type ‘NONE’ is supported, meaning no compression.

 -- 成員函式: Wave_write.setparams (tuple)

     The `tuple' should be ‘(nchannels, sampwidth, framerate, nframes,
     comptype, compname)’, with values valid for the ‘set*()’ methods.
     Sets all parameters.

 -- 成員函式: Wave_write.tell ()

     Return current position in the file, with the same disclaimer for
     the *note Wave_read.tell(): 2ff7. and *note Wave_read.setpos():
     2ff6. methods.

 -- 成員函式: Wave_write.writeframesraw (data)

     Write audio frames, without correcting `nframes'.

     3.4 版更變: Any *note bytes-like object: 5ed. is now accepted.

 -- 成員函式: Wave_write.writeframes (data)

     Write audio frames and make sure `nframes' is correct.  It will
     raise an error if the output stream is not seekable and the total
     number of frames that have been written after `data' has been
     written does not match the previously set value for `nframes'.

     3.4 版更變: Any *note bytes-like object: 5ed. is now accepted.

Note that it is invalid to set any parameters after calling
‘writeframes()’ or ‘writeframesraw()’, and any attempt to do so will
raise *note wave.Error: 2fe8.


File: python.info,  Node: chunk --- Read IFF chunked data,  Next: colorsys --- Conversions between color systems,  Prev: wave --- Read and write WAV files,  Up: Multimedia Services

5.22.5 ‘chunk’ — Read IFF chunked data
--------------------------------------

`Source code:' Lib/chunk.py(1)

__________________________________________________________________

This module provides an interface for reading files that use EA IFF 85
chunks.  (2) This format is used in at least the Audio Interchange File
Format (AIFF/AIFF-C) and the Real Media File Format (RMFF). The WAVE
audio file format is closely related and can also be read using this
module.

A chunk has the following structure:

Offset        Length       Contents
                           
---------------------------------------------------------------
                           
0             4            Chunk ID
                           
                           
4             4            Size of chunk in big-endian byte
                           order, not including the header
                           
                           
8             `n'          Data bytes, where `n' is the size
                           given in the preceding field
                           
                           
8 + `n'       0 or 1       Pad byte needed if `n' is odd and
                           chunk alignment is used
                           

The ID is a 4-byte string which identifies the type of chunk.

The size field (a 32-bit value, encoded using big-endian byte order)
gives the size of the chunk data, not including the 8-byte header.

Usually an IFF-type file consists of one or more chunks.  The proposed
usage of the *note Chunk: 3002. class defined here is to instantiate an
instance at the start of each chunk and read from the instance until it
reaches the end, after which a new instance can be instantiated.  At the
end of the file, creating a new instance will fail with an *note
EOFError: c71. exception.

 -- 類別: chunk.Chunk (file, align=True, bigendian=True,
          inclheader=False)

     Class which represents a chunk.  The `file' argument is expected to
     be a file-like object.  An instance of this class is specifically
     allowed.  The only method that is needed is ‘read()’.  If the
     methods *note seek(): 1d9d. and *note tell(): 1d9e. are present and
     don’t raise an exception, they are also used.  If these methods are
     present and raise an exception, they are expected to not have
     altered the object.  If the optional argument `align' is true,
     chunks are assumed to be aligned on 2-byte boundaries.  If `align'
     is false, no alignment is assumed.  The default value is true.  If
     the optional argument `bigendian' is false, the chunk size is
     assumed to be in little-endian order.  This is needed for WAVE
     audio files.  The default value is true.  If the optional argument
     `inclheader' is true, the size given in the chunk header includes
     the size of the header.  The default value is false.

     A *note Chunk: 3002. object supports the following methods:

      -- 成員函式: getname ()

          Returns the name (ID) of the chunk.  This is the first 4 bytes
          of the chunk.

      -- 成員函式: getsize ()

          Returns the size of the chunk.

      -- 成員函式: close ()

          Close and skip to the end of the chunk.  This does not close
          the underlying file.

     The remaining methods will raise *note OSError: 1d4. if called
     after the *note close(): 3005. method has been called.  Before
     Python 3.3, they used to raise *note IOError: 997, now an alias of
     *note OSError: 1d4.

      -- 成員函式: isatty ()

          Returns ‘False’.

      -- 成員函式: seek (pos, whence=0)

          Set the chunk’s current position.  The `whence' argument is
          optional and defaults to ‘0’ (absolute file positioning);
          other values are ‘1’ (seek relative to the current position)
          and ‘2’ (seek relative to the file’s end).  There is no return
          value.  If the underlying file does not allow seek, only
          forward seeks are allowed.

      -- 成員函式: tell ()

          Return the current position into the chunk.

      -- 成員函式: read (size=-1)

          Read at most `size' bytes from the chunk (less if the read
          hits the end of the chunk before obtaining `size' bytes).  If
          the `size' argument is negative or omitted, read all data
          until the end of the chunk.  An empty bytes object is returned
          when the end of the chunk is encountered immediately.

      -- 成員函式: skip ()

          Skip to the end of the chunk.  All further calls to *note
          read(): 3009. for the chunk will return ‘b''’.  If you are not
          interested in the contents of the chunk, this method should be
          called so that the file points to the start of the next chunk.

註解
....

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/chunk.py

   (2) (1) "EA IFF 85" Standard for Interchange Format Files, Jerry
Morrison, Electronic Arts, January 1985.


File: python.info,  Node: colorsys --- Conversions between color systems,  Next: imghdr --- Determine the type of an image,  Prev: chunk --- Read IFF chunked data,  Up: Multimedia Services

5.22.6 ‘colorsys’ — Conversions between color systems
-----------------------------------------------------

`Source code:' Lib/colorsys.py(1)

__________________________________________________________________

The *note colorsys: 20. module defines bidirectional conversions of
color values between colors expressed in the RGB (Red Green Blue) color
space used in computer monitors and three other coordinate systems: YIQ,
HLS (Hue Lightness Saturation) and HSV (Hue Saturation Value).
Coordinates in all of these color spaces are floating point values.  In
the YIQ space, the Y coordinate is between 0 and 1, but the I and Q
coordinates can be positive or negative.  In all other spaces, the
coordinates are all between 0 and 1.

也參考
......

More information about color spaces can be found at
‘http://poynton.ca/ColorFAQ.html’ and
‘https://www.cambridgeincolour.com/tutorials/color-spaces.htm’.

The *note colorsys: 20. module defines the following functions:

 -- 函式: colorsys.rgb_to_yiq (r, g, b)

     Convert the color from RGB coordinates to YIQ coordinates.

 -- 函式: colorsys.yiq_to_rgb (y, i, q)

     Convert the color from YIQ coordinates to RGB coordinates.

 -- 函式: colorsys.rgb_to_hls (r, g, b)

     Convert the color from RGB coordinates to HLS coordinates.

 -- 函式: colorsys.hls_to_rgb (h, l, s)

     Convert the color from HLS coordinates to RGB coordinates.

 -- 函式: colorsys.rgb_to_hsv (r, g, b)

     Convert the color from RGB coordinates to HSV coordinates.

 -- 函式: colorsys.hsv_to_rgb (h, s, v)

     Convert the color from HSV coordinates to RGB coordinates.

Example:

     >>> 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.8/Lib/colorsys.py


File: python.info,  Node: imghdr --- Determine the type of an image,  Next: sndhdr --- Determine type of sound file,  Prev: colorsys --- Conversions between color systems,  Up: Multimedia Services

5.22.7 ‘imghdr’ — Determine the type of an image
------------------------------------------------

`Source code:' Lib/imghdr.py(1)

__________________________________________________________________

The *note imghdr: 99. module determines the type of image contained in a
file or byte stream.

The *note imghdr: 99. module defines the following function:

 -- 函式: imghdr.what (filename, h=None)

     Tests the image data contained in the file named by `filename', and
     returns a string describing the image type.  If optional `h' is
     provided, the `filename' is ignored and `h' is assumed to contain
     the byte stream to test.

     3.6 版更變: Accepts a *note path-like object: 36f.

The following image types are recognized, as listed below with the
return value from *note what(): 6f2.:

Value            Image format
                 
---------------------------------------------------------
                 
‘'rgb'’          SGI ImgLib Files
                 
                 
‘'gif'’          GIF 87a and 89a Files
                 
                 
‘'pbm'’          Portable Bitmap Files
                 
                 
‘'pgm'’          Portable Graymap Files
                 
                 
‘'ppm'’          Portable Pixmap Files
                 
                 
‘'tiff'’         TIFF Files
                 
                 
‘'rast'’         Sun Raster Files
                 
                 
‘'xbm'’          X Bitmap Files
                 
                 
‘'jpeg'’         JPEG data in JFIF or Exif formats
                 
                 
‘'bmp'’          BMP files
                 
                 
‘'png'’          Portable Network Graphics
                 
                 
‘'webp'’         WebP files
                 
                 
‘'exr'’          OpenEXR Files
                 

3.5 版新加入: The `exr' and `webp' formats were added.

You can extend the list of file types *note imghdr: 99. can recognize by
appending to this variable:

 -- Data: imghdr.tests

     A list of functions performing the individual tests.  Each function
     takes two arguments: the byte-stream and an open file-like object.
     When *note what(): 6f2. is called with a byte-stream, the file-like
     object will be ‘None’.

     The test function should return a string describing the image type
     if the test succeeded, or ‘None’ if it failed.

Example:

     >>> import imghdr
     >>> imghdr.what('bass.gif')
     'gif'

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/imghdr.py


File: python.info,  Node: sndhdr --- Determine type of sound file,  Next: ossaudiodev --- Access to OSS-compatible audio devices,  Prev: imghdr --- Determine the type of an image,  Up: Multimedia Services

5.22.8 ‘sndhdr’ — Determine type of sound file
----------------------------------------------

`Source code:' Lib/sndhdr.py(1)

__________________________________________________________________

The *note sndhdr: ef. provides utility functions which attempt to
determine the type of sound data which is in a file.  When these
functions are able to determine what type of sound data is stored in a
file, they return a *note namedtuple(): 1b8, containing five attributes:
(‘filetype’, ‘framerate’, ‘nchannels’, ‘nframes’, ‘sampwidth’).  The
value for `type' indicates the data type and will be one of the strings
‘'aifc'’, ‘'aiff'’, ‘'au'’, ‘'hcom'’, ‘'sndr'’, ‘'sndt'’, ‘'voc'’,
‘'wav'’, ‘'8svx'’, ‘'sb'’, ‘'ub'’, or ‘'ul'’.  The `sampling_rate' will
be either the actual value or ‘0’ if unknown or difficult to decode.
Similarly, `channels' will be either the number of channels or ‘0’ if it
cannot be determined or if the value is difficult to decode.  The value
for `frames' will be either the number of frames or ‘-1’.  The last item
in the tuple, `bits_per_sample', will either be the sample size in bits
or ‘'A'’ for A-LAW or ‘'U'’ for u-LAW.

 -- 函式: sndhdr.what (filename)

     Determines the type of sound data stored in the file `filename'
     using *note whathdr(): 74d.  If it succeeds, returns a namedtuple
     as described above, otherwise ‘None’ is returned.

     3.5 版更變: Result changed from a tuple to a namedtuple.

 -- 函式: sndhdr.whathdr (filename)

     Determines the type of sound data stored in a file based on the
     file header.  The name of the file is given by `filename'.  This
     function returns a namedtuple as described above on success, or
     ‘None’.

     3.5 版更變: Result changed from a tuple to a namedtuple.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/sndhdr.py


File: python.info,  Node: ossaudiodev --- Access to OSS-compatible audio devices,  Prev: sndhdr --- Determine type of sound file,  Up: Multimedia Services

5.22.9 ‘ossaudiodev’ — Access to OSS-compatible audio devices
-------------------------------------------------------------

__________________________________________________________________

This module allows you to access the OSS (Open Sound System) audio
interface.  OSS is available for a wide range of open-source and
commercial Unices, and is the standard audio interface for Linux and
recent versions of FreeBSD.

3.3 版更變: Operations in this module now raise *note OSError: 1d4.
where *note IOError: 997. was raised.

也參考
......

Open Sound System Programmer’s Guide(1)

     the official documentation for the OSS C API

The module defines a large number of constants supplied by the OSS
device driver; see ‘<sys/soundcard.h>’ on either Linux or FreeBSD for a
listing.

*note ossaudiodev: c7. defines the following variables and functions:

 -- 例外: ossaudiodev.OSSAudioError

     This exception is raised on certain errors.  The argument is a
     string describing what went wrong.

     (If *note ossaudiodev: c7. receives an error from a system call
     such as ‘open()’, ‘write()’, or ‘ioctl()’, it raises *note OSError:
     1d4.  Errors detected directly by *note ossaudiodev: c7. result in
     *note OSSAudioError: 301a.)

     (For backwards compatibility, the exception class is also available
     as ‘ossaudiodev.error’.)

 -- 函式: ossaudiodev.open (mode)

 -- 函式: ossaudiodev.open (device, mode)

     Open an audio device and return an OSS audio device object.  This
     object supports many file-like methods, such as ‘read()’,
     ‘write()’, and ‘fileno()’ (although there are subtle differences
     between conventional Unix read/write semantics and those of OSS
     audio devices).  It also supports a number of audio-specific
     methods; see below for the complete list of methods.

     `device' is the audio device filename to use.  If it is not
     specified, this module first looks in the environment variable
     ‘AUDIODEV’ for a device to use.  If not found, it falls back to
     ‘/dev/dsp’.

     `mode' is one of ‘'r'’ for read-only (record) access, ‘'w'’ for
     write-only (playback) access and ‘'rw'’ for both.  Since many sound
     cards only allow one process to have the recorder or player open at
     a time, it is a good idea to open the device only for the activity
     needed.  Further, some sound cards are half-duplex: they can be
     opened for reading or writing, but not both at once.

     Note the unusual calling syntax: the `first' argument is optional,
     and the second is required.  This is a historical artifact for
     compatibility with the older ‘linuxaudiodev’ module which *note
     ossaudiodev: c7. supersedes.

 -- 函式: ossaudiodev.openmixer ([device])

     Open a mixer device and return an OSS mixer device object.
     `device' is the mixer device filename to use.  If it is not
     specified, this module first looks in the environment variable
     ‘MIXERDEV’ for a device to use.  If not found, it falls back to
     ‘/dev/mixer’.

* Menu:

* Audio Device Objects::
* Mixer Device Objects::

   ---------- Footnotes ----------

   (1) http://www.opensound.com/pguide/oss.pdf


File: python.info,  Node: Audio Device Objects,  Next: Mixer Device Objects,  Up: ossaudiodev --- Access to OSS-compatible audio devices

5.22.9.1 Audio Device Objects
.............................

Before you can write to or read from an audio device, you must call
three methods in the correct order:

  1. ‘setfmt()’ to set the output format

  2. ‘channels()’ to set the number of channels

  3. ‘speed()’ to set the sample rate

Alternately, you can use the ‘setparameters()’ method to set all three
audio parameters at once.  This is more convenient, but may not be as
flexible in all cases.

The audio device objects returned by *note open(): 301b. define the
following methods and (read-only) attributes:

 -- 成員函式: oss_audio_device.close ()

     Explicitly close the audio device.  When you are done writing to or
     reading from an audio device, you should explicitly close it.  A
     closed device cannot be used again.

 -- 成員函式: oss_audio_device.fileno ()

     Return the file descriptor associated with the device.

 -- 成員函式: oss_audio_device.read (size)

     Read `size' bytes from the audio input and return them as a Python
     string.  Unlike most Unix device drivers, OSS audio devices in
     blocking mode (the default) will block *note read(): 3021. until
     the entire requested amount of data is available.

 -- 成員函式: oss_audio_device.write (data)

     Write a *note bytes-like object: 5ed. `data' to the audio device
     and return the number of bytes written.  If the audio device is in
     blocking mode (the default), the entire data is always written
     (again, this is different from usual Unix device semantics).  If
     the device is in non-blocking mode, some data may not be
     written—see *note writeall(): 3023.

     3.5 版更變: Writable *note bytes-like object: 5ed. is now accepted.

 -- 成員函式: oss_audio_device.writeall (data)

     Write a *note bytes-like object: 5ed. `data' to the audio device:
     waits until the audio device is able to accept data, writes as much
     data as it will accept, and repeats until `data' has been
     completely written.  If the device is in blocking mode (the
     default), this has the same effect as *note write(): 3022.; *note
     writeall(): 3023. is only useful in non-blocking mode.  Has no
     return value, since the amount of data written is always equal to
     the amount of data supplied.

     3.5 版更變: Writable *note bytes-like object: 5ed. is now accepted.

3.2 版更變: Audio device objects also support the context management
protocol, i.e.  they can be used in a *note with: 6ee. statement.

The following methods each map to exactly one ‘ioctl()’ system call.
The correspondence is obvious: for example, ‘setfmt()’ corresponds to
the ‘SNDCTL_DSP_SETFMT’ ioctl, and ‘sync()’ to ‘SNDCTL_DSP_SYNC’ (this
can be useful when consulting the OSS documentation).  If the underlying
‘ioctl()’ fails, they all raise *note OSError: 1d4.

 -- 成員函式: oss_audio_device.nonblock ()

     Put the device into non-blocking mode.  Once in non-blocking mode,
     there is no way to return it to blocking mode.

 -- 成員函式: oss_audio_device.getfmts ()

     Return a bitmask of the audio output formats supported by the
     soundcard.  Some of the formats supported by OSS are:

     Format                        描述
                                   
     --------------------------------------------------------------------------------
                                   
     ‘AFMT_MU_LAW’                 a logarithmic encoding (used by Sun ‘.au’ files
                                   and ‘/dev/audio’)
                                   
                                   
     ‘AFMT_A_LAW’                  a logarithmic encoding
                                   
                                   
     ‘AFMT_IMA_ADPCM’              a 4:1 compressed format defined by the
                                   Interactive Multimedia Association
                                   
                                   
     ‘AFMT_U8’                     Unsigned, 8-bit audio
                                   
                                   
     ‘AFMT_S16_LE’                 Signed, 16-bit audio, little-endian byte order
                                   (as used by Intel processors)
                                   
                                   
     ‘AFMT_S16_BE’                 Signed, 16-bit audio, big-endian byte order (as
                                   used by 68k, PowerPC, Sparc)
                                   
                                   
     ‘AFMT_S8’                     Signed, 8 bit audio
                                   
                                   
     ‘AFMT_U16_LE’                 Unsigned, 16-bit little-endian audio
                                   
                                   
     ‘AFMT_U16_BE’                 Unsigned, 16-bit big-endian audio
                                   

     Consult the OSS documentation for a full list of audio formats, and
     note that most devices support only a subset of these formats.
     Some older devices only support ‘AFMT_U8’; the most common format
     used today is ‘AFMT_S16_LE’.

 -- 成員函式: oss_audio_device.setfmt (format)

     Try to set the current audio format to `format'—see *note
     getfmts(): 3025. for a list.  Returns the audio format that the
     device was set to, which may not be the requested format.  May also
     be used to return the current audio format—do this by passing an
     "audio format" of ‘AFMT_QUERY’.

 -- 成員函式: oss_audio_device.channels (nchannels)

     Set the number of output channels to `nchannels'.  A value of 1
     indicates monophonic sound, 2 stereophonic.  Some devices may have
     more than 2 channels, and some high-end devices may not support
     mono.  Returns the number of channels the device was set to.

 -- 成員函式: oss_audio_device.speed (samplerate)

     Try to set the audio sampling rate to `samplerate' samples per
     second.  Returns the rate actually set.  Most sound devices don’t
     support arbitrary sampling rates.  Common rates are:

     Rate        描述
                 
     ------------------------------------------------------------
                 
     8000        default rate for ‘/dev/audio’
                 
                 
     11025       speech recording
                 
                 
     22050

     44100       CD quality audio (at 16 bits/sample and 2
                 channels)
                 
                 
     96000       DVD quality audio (at 24 bits/sample)
                 

 -- 成員函式: oss_audio_device.sync ()

     Wait until the sound device has played every byte in its buffer.
     (This happens implicitly when the device is closed.)  The OSS
     documentation recommends closing and re-opening the device rather
     than using *note sync(): 3029.

 -- 成員函式: oss_audio_device.reset ()

     Immediately stop playing or recording and return the device to a
     state where it can accept commands.  The OSS documentation
     recommends closing and re-opening the device after calling *note
     reset(): 302a.

 -- 成員函式: oss_audio_device.post ()

     Tell the driver that there is likely to be a pause in the output,
     making it possible for the device to handle the pause more
     intelligently.  You might use this after playing a spot sound
     effect, before waiting for user input, or before doing disk I/O.

The following convenience methods combine several ioctls, or one ioctl
and some simple calculations.

 -- 成員函式: oss_audio_device.setparameters (format, nchannels,
          samplerate[, strict=False])

     Set the key audio sampling parameters—sample format, number of
     channels, and sampling rate—in one method call.  `format',
     `nchannels', and `samplerate' should be as specified in the *note
     setfmt(): 3026, *note channels(): 3027, and *note speed(): 3028.
     methods.  If `strict' is true, *note setparameters(): 302c. checks
     to see if each parameter was actually set to the requested value,
     and raises *note OSSAudioError: 301a. if not.  Returns a tuple
     (`format', `nchannels', `samplerate') indicating the parameter
     values that were actually set by the device driver (i.e., the same
     as the return values of *note setfmt(): 3026, *note channels():
     3027, and *note speed(): 3028.).

     For example,

          (fmt, channels, rate) = dsp.setparameters(fmt, channels, rate)

     is equivalent to

          fmt = dsp.setfmt(fmt)
          channels = dsp.channels(channels)
          rate = dsp.rate(rate)

 -- 成員函式: oss_audio_device.bufsize ()

     Returns the size of the hardware buffer, in samples.

 -- 成員函式: oss_audio_device.obufcount ()

     Returns the number of samples that are in the hardware buffer yet
     to be played.

 -- 成員函式: oss_audio_device.obuffree ()

     Returns the number of samples that could be queued into the
     hardware buffer to be played without blocking.

Audio device objects also support several read-only attributes:

 -- 屬性: oss_audio_device.closed

     Boolean indicating whether the device has been closed.

 -- 屬性: oss_audio_device.name

     String containing the name of the device file.

 -- 屬性: oss_audio_device.mode

     The I/O mode for the file, either ‘"r"’, ‘"rw"’, or ‘"w"’.


File: python.info,  Node: Mixer Device Objects,  Prev: Audio Device Objects,  Up: ossaudiodev --- Access to OSS-compatible audio devices

5.22.9.2 Mixer Device Objects
.............................

The mixer object provides two file-like methods:

 -- 成員函式: oss_mixer_device.close ()

     This method closes the open mixer device file.  Any further
     attempts to use the mixer after this file is closed will raise an
     *note OSError: 1d4.

 -- 成員函式: oss_mixer_device.fileno ()

     Returns the file handle number of the open mixer device file.

3.2 版更變: Mixer objects also support the context management protocol.

The remaining methods are specific to audio mixing:

 -- 成員函式: oss_mixer_device.controls ()

     This method returns a bitmask specifying the available mixer
     controls ("Control" being a specific mixable "channel", such as
     ‘SOUND_MIXER_PCM’ or ‘SOUND_MIXER_SYNTH’).  This bitmask indicates
     a subset of all available mixer controls—the ‘SOUND_MIXER_*’
     constants defined at module level.  To determine if, for example,
     the current mixer object supports a PCM mixer, use the following
     Python code:

          mixer=ossaudiodev.openmixer()
          if mixer.controls() & (1 << ossaudiodev.SOUND_MIXER_PCM):
              # PCM is supported
              ... code ...

     For most purposes, the ‘SOUND_MIXER_VOLUME’ (master volume) and
     ‘SOUND_MIXER_PCM’ controls should suffice—but code that uses the
     mixer should be flexible when it comes to choosing mixer controls.
     On the Gravis Ultrasound, for example, ‘SOUND_MIXER_VOLUME’ does
     not exist.

 -- 成員函式: oss_mixer_device.stereocontrols ()

     Returns a bitmask indicating stereo mixer controls.  If a bit is
     set, the corresponding control is stereo; if it is unset, the
     control is either monophonic or not supported by the mixer (use in
     combination with *note controls(): 3037. to determine which).

     See the code example for the *note controls(): 3037. function for
     an example of getting data from a bitmask.

 -- 成員函式: oss_mixer_device.reccontrols ()

     Returns a bitmask specifying the mixer controls that may be used to
     record.  See the code example for *note controls(): 3037. for an
     example of reading from a bitmask.

 -- 成員函式: oss_mixer_device.get (control)

     Returns the volume of a given mixer control.  The returned volume
     is a 2-tuple ‘(left_volume,right_volume)’.  Volumes are specified
     as numbers from 0 (silent) to 100 (full volume).  If the control is
     monophonic, a 2-tuple is still returned, but both volumes are the
     same.

     Raises *note OSSAudioError: 301a. if an invalid control is
     specified, or *note OSError: 1d4. if an unsupported control is
     specified.

 -- 成員函式: oss_mixer_device.set (control, (left, right))

     Sets the volume for a given mixer control to ‘(left,right)’.
     ‘left’ and ‘right’ must be ints and between 0 (silent) and 100
     (full volume).  On success, the new volume is returned as a
     2-tuple.  Note that this may not be exactly the same as the volume
     specified, because of the limited resolution of some soundcard’s
     mixers.

     Raises *note OSSAudioError: 301a. if an invalid mixer control was
     specified, or if the specified volumes were out-of-range.

 -- 成員函式: oss_mixer_device.get_recsrc ()

     This method returns a bitmask indicating which control(s) are
     currently being used as a recording source.

 -- 成員函式: oss_mixer_device.set_recsrc (bitmask)

     Call this function to specify a recording source.  Returns a
     bitmask indicating the new recording source (or sources) if
     successful; raises *note OSError: 1d4. if an invalid source was
     specified.  To set the current recording source to the microphone
     input:

          mixer.setrecsrc (1 << ossaudiodev.SOUND_MIXER_MIC)


File: python.info,  Node: 國際化,  Next: 程式框架,  Prev: Multimedia Services,  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.

The list of modules described in this chapter is:

* Menu:

* gettext: gettext --- Multilingual internationalization services. Multilingual internationalization services
* locale: locale --- Internationalization services. Internationalization services


File: python.info,  Node: gettext --- Multilingual internationalization services,  Next: locale --- Internationalization services,  Up: 國際化

5.23.1 ‘gettext’ — Multilingual internationalization services
-------------------------------------------------------------

`Source code:' Lib/gettext.py(1)

__________________________________________________________________

The *note gettext: 89. 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::
* Acknowledgements: Acknowledgements<9>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/gettext.py


File: python.info,  Node: GNU gettext API,  Next: Class-based API,  Up: gettext --- Multilingual internationalization services

5.23.1.1 GNU ‘gettext’ API
..........................

The *note gettext: 89. 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: 89. 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.bind_textdomain_codeset (domain, codeset=None)

     Bind the `domain' to `codeset', changing the encoding of byte
     strings returned by the *note lgettext(): 294, *note ldgettext():
     295, *note lngettext(): 296. and *note ldngettext(): 297.
     functions.  If `codeset' is omitted, then the current binding is
     returned.

     Deprecated since version 3.8, will be removed in version 3.10.

 -- 函式: 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(): dd2, but look the message up in the specified
     `domain'.

 -- 函式: gettext.ngettext (singular, plural, n)

     Like *note gettext(): dd2, 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(): 3048, 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(): 89, *note dgettext(): 3047, *note
     ngettext(): 3048, *note dngettext(): 3049.), but the translation is
     restricted to the given message `context'.

     3.8 版新加入.

 -- 函式: gettext.lgettext (message)

 -- 函式: gettext.ldgettext (domain, message)

 -- 函式: gettext.lngettext (singular, plural, n)

 -- 函式: gettext.ldngettext (domain, singular, plural, n)

     Equivalent to the corresponding functions without the ‘l’ prefix
     (*note gettext(): dd2, *note dgettext(): 3047, *note ngettext():
     3048. and *note dngettext(): 3049.), but the translation is
     returned as a byte string encoded in the preferred system encoding
     if no other encoding was explicitly set with *note
     bind_textdomain_codeset(): 298.

          警告: These functions should be avoided in Python 3, because
          they return encoded bytes.  It’s much better to use
          alternatives which return Unicode strings instead, since most
          Python applications will want to manipulate human readable
          text as strings instead of bytes.  Further, it’s possible that
          you may get unexpected Unicode-related exceptions if there are
          encoding problems with the translated strings.

     Deprecated since version 3.8, will be removed in version 3.10.

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) (1) The default locale directory is system dependent; for
example, on RedHat Linux it is ‘/usr/share/locale’, but on Solaris it is
‘/usr/lib/locale’.  The *note gettext: 89. module does not try to
support these system dependent defaults; instead its default is
‘`sys.base_prefix'/share/locale’ (see *note sys.base_prefix: 3045.).
For this reason, it is always best to call *note bindtextdomain(): 3044.
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 --- Multilingual internationalization services

5.23.1.2 Class-based API
........................

The class-based API of the *note gettext: 89. 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: 304e. 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(): 3046.
     takes.  Optional `localedir' is as in *note bindtextdomain(): 3044.
     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(): 304f. 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():
     304f.  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, codeset=None)

     Return a ‘*Translations’ instance based on the `domain',
     `localedir', and `languages', which are first passed to *note
     find(): 304f. 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: 304e.  The class’s constructor must take a single
     *note file object: b47. argument.  If provided, `codeset' will
     change the charset used to encode translated strings in the *note
     lgettext(): 3050. and *note lngettext(): 3051. methods.

     If multiple files are found, later files are used as fallbacks for
     earlier ones.  To allow setting the fallback, *note copy.copy():
     3d0. 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: 1d4.
     if `fallback' is false (which is the default), and returns a *note
     NullTranslations: 3052. instance if `fallback' is true.

     3.3 版更變: *note IOError: 997. used to be raised instead of *note
     OSError: 1d4.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `codeset' parameter.

 -- 函式: gettext.install (domain, localedir=None, codeset=None,
          names=None)

     This installs the function ‘_()’ in Python’s builtins namespace,
     based on `domain', `localedir', and `codeset' which are passed to
     the function *note translation(): 29b.

     For the `names' parameter, please see the description of the
     translation object’s *note install(): 3053. 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.

     Deprecated since version 3.8, will be removed in version 3.10: The
     `codeset' parameter.

* Menu:

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

   ---------- Footnotes ----------

   (1) (2) See the footnote for *note bindtextdomain(): 3044. above.


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:
3052.; 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: b47. `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(): 3055.  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(): 1d0. 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(): 304b.
          to the fallback.  Otherwise, return the translated message.
          Overridden in derived classes.

          3.8 版新加入.

      -- 成員函式: lgettext (message)

      -- 成員函式: lngettext (singular, plural, n)

          Equivalent to *note gettext(): 3057. and *note ngettext():
          3058, but the translation is returned as a byte string encoded
          in the preferred system encoding if no encoding was explicitly
          set with *note set_output_charset(): 29a.  Overridden in
          derived classes.

               警告: These methods should be avoided in Python 3.  See
               the warning for the *note lgettext(): 294. function.

          Deprecated since version 3.8, will be removed in version 3.10.

      -- 成員函式: info ()

          Return the "protected" ‘_info’ variable, a dictionary
          containing the metadata found in the message catalog file.

      -- 成員函式: charset ()

          Return the encoding of the message catalog file.

      -- 成員函式: output_charset ()

          Return the encoding used to return translated messages in
          *note lgettext(): 3050. and *note lngettext(): 3051.

          Deprecated since version 3.8, will be removed in version 3.10.

      -- 成員函式: set_output_charset (charset)

          Change the encoding used to return translated messages.

          Deprecated since version 3.8, will be removed in version 3.10.

      -- 成員函式: install (names=None)

          This method installs *note gettext(): 3057. 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'’, ‘'npgettext'’,
          ‘'lgettext'’, and ‘'lngettext'’.

          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 版更變: Added ‘'pgettext'’ and ‘'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 *note gettext: 89. module provides one additional class derived from
*note NullTranslations: 3052.: *note GNUTranslations: 304e.  This class
overrides ‘_parse()’ to enable reading GNU ‘gettext’ format ‘.mo’ files
in both big-endian and little-endian format.

*note GNUTranslations: 304e. 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: 304e. class can raise *note
OSError: 1d4.

 -- 類別: 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(): 3057. 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(): 3058. method.  Otherwise, when `n' is 1 `singular'
          is returned, and `plural' is returned in all other cases.

          Here is an example:

               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(): 1d0. 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(): 304b. method.  Otherwise, when
          `n' is 1 `singular' is returned, and `plural' is returned in
          all other cases.

          3.8 版新加入.

      -- 成員函式: lgettext (message)

      -- 成員函式: lngettext (singular, plural, n)

          Equivalent to *note gettext(): 305e. and *note ngettext():
          305f, but the translation is returned as a byte string encoded
          in the preferred system encoding if no encoding was explicitly
          set with *note set_output_charset(): 29a.

               警告: These methods should be avoided in Python 3.  See
               the warning for the *note lgettext(): 294. function.

          Deprecated since version 3.8, will be removed in version 3.10.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/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: 89. 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(): 29b. 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: Acknowledgements<9>,  Prev: Class-based API,  Up: gettext --- Multilingual internationalization services

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: 89. 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
‘_()’.  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: 89. module for the actual translation
processing at run-time.

How you use the *note gettext: 89. 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) http://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(): 29c. 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:
1273. 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: Acknowledgements<9>,  Prev: Internationalizing your programs and modules,  Up: gettext --- Multilingual internationalization services

5.23.1.12 Acknowledgements
..........................

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 --- Internationalization services,  Prev: gettext --- Multilingual internationalization services,  Up: 國際化

5.23.2 ‘locale’ — Internationalization services
-----------------------------------------------

`Source code:' Lib/locale.py(1)

__________________________________________________________________

The *note locale: aa. 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: aa. module is implemented on top of the ‘_locale’
module, which in turn uses an ANSI C locale implementation if available.

The *note locale: aa. module defines the following exception and
functions:

 -- 例外: locale.Error

     Exception raised when the locale passed to *note setlocale(): 200f.
     is not recognized.

 -- 函式: locale.setlocale (category, locale=None)

     If `locale' is given and not ‘None’, *note setlocale(): 200f.
     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: 306e. 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(): 200f. 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:

     Category                   Key                                       Meaning
                                                                          
     ----------------------------------------------------------------------------------------------------------
                                                                          
     *note LC_NUMERIC: 306f.    ‘'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: 3070, 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: 3071.   ‘'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: 3070. 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 sets temporarily 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 sets temporarily 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(): 3072. function accepts one of the
     following keys.  Most descriptions are taken from the corresponding
     description in the GNU C library.

      -- Data: locale.CODESET

          Get a string with the name of the character encoding used in
          the selected locale.

      -- Data: locale.D_T_FMT

          Get a string that can be used as a format string for *note
          time.strftime(): b6a. to represent date and time in a
          locale-specific way.

      -- Data: locale.D_FMT

          Get a string that can be used as a format string for *note
          time.strftime(): b6a. to represent a date in a locale-specific
          way.

      -- Data: locale.T_FMT

          Get a string that can be used as a format string for *note
          time.strftime(): b6a. to represent a time in a locale-specific
          way.

      -- Data: locale.T_FMT_AMPM

          Get a format string for *note time.strftime(): b6a. to
          represent time in the am/pm format.

      -- Data: DAY_1 ... DAY_7

          Get the name of the n-th day of the week.

               備註: This follows the US convention of ‘DAY_1’ being
               Sunday, not the international convention (ISO 8601) that
               Monday is the first day of the week.

      -- Data: ABDAY_1 ... ABDAY_7

          Get the abbreviated name of the n-th day of the week.

      -- Data: MON_1 ... MON_12

          Get the name of the n-th month.

      -- Data: ABMON_1 ... ABMON_12

          Get the abbreviated name of the n-th month.

      -- Data: locale.RADIXCHAR

          Get the radix character (decimal dot, decimal comma, etc.).

      -- Data: locale.THOUSEP

          Get the separator character for thousands (groups of three
          digits).

      -- Data: locale.YESEXPR

          Get a regular expression that can be used with the regex
          function to recognize a positive response to a yes/no
          question.

               備註: The expression is in the syntax suitable for the
               ‘regex()’ function from the C library, which might differ
               from the syntax used in *note re: de.

      -- Data: 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.

      -- Data: 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.

      -- Data: 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(): b6a. 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.

      -- Data: locale.ERA_D_T_FMT

          Get a format string for *note time.strftime(): b6a. to
          represent date and time in a locale-specific era-based way.

      -- Data: locale.ERA_D_FMT

          Get a format string for *note time.strftime(): b6a. to
          represent a date in a locale-specific era-based way.

      -- Data: locale.ERA_T_FMT

          Get a format string for *note time.strftime(): b6a. to
          represent a time in a locale-specific era-based way.

      -- Data: 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.

 -- 函式: 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: 3082.  It defaults to
     *note LC_CTYPE: 3083.

     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 encoding 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(): 200f.
     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 in the UTF-8 mode (*note -X: 156. ‘utf8’ option),
     always return ‘'UTF-8'’, the locale and the `do_setlocale' argument
     are ignored.

     3.7 版更變: The function now always returns ‘UTF-8’ on Android or
     if the UTF-8 mode is enabled.

 -- 函式: locale.normalize (localename)

     Returns a normalized locale code for the given locale name.  The
     returned locale code is formatted for use with *note setlocale():
     200f.  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():
     200f.

 -- 函式: locale.resetlocale (category=LC_ALL)

     Sets the locale for `category' to the default setting.

     The default setting is determined by calling *note
     getdefaultlocale(): 1365.  `category' defaults to *note LC_ALL:
     3082.

 -- 函式: locale.strcoll (string1, string2)

     Compares two strings according to the current *note LC_COLLATE:
     3087. 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:
     306f. 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.format (format, val, grouping=False, monetary=False)

     Please note that this function works like *note format_string():
     3a9. but will only work for exactly one ‘%char’ specifier.  For
     example, ‘'%f'’ and ‘'%.0f'’ are both valid specifiers, but ‘'%f
     KiB'’ is not.

     For whole format strings, use *note format_string(): 3a9.

     3.7 版後已棄用: Use *note format_string(): 3a9. instead.

 -- 函式: locale.currency (val, symbol=True, grouping=False,
          international=False)

     Formats a number `val' according to the current *note LC_MONETARY:
     3071. 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.

     Note that this function will not work with the ’C’ locale, so you
     have to set a locale via *note setlocale(): 200f. 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: 306f. settings.

     3.5 版新加入.

 -- 函式: locale.atof (string)

     Converts a string to a floating point number, following the *note
     LC_NUMERIC: 306f. settings.

 -- 函式: locale.atoi (string)

     Converts a string to an integer, following the *note LC_NUMERIC:
     306f. conventions.

 -- Data: locale.LC_CTYPE

     Locale category for the character type functions.  Depending on the
     settings of this category, the functions of module *note string:
     f7. dealing with case change their behaviour.

 -- Data: locale.LC_COLLATE

     Locale category for sorting strings.  The functions *note
     strcoll(): 3086. and *note strxfrm(): 3088. of the *note locale:
     aa. module are affected.

 -- Data: locale.LC_TIME

     Locale category for the formatting of time.  The function *note
     time.strftime(): b6a. follows these conventions.

 -- Data: locale.LC_MONETARY

     Locale category for formatting of monetary values.  The available
     options are available from the *note localeconv(): 48f. function.

 -- Data: 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(): 1f08. might be affected by this category.

 -- Data: locale.LC_NUMERIC

     Locale category for formatting numbers.  The functions *note
     format(): 46d, *note atoi(): 308c, *note atof(): 308b. and *note
     str(): 308a. of the *note locale: aa. module are affected by that
     category.  All other numeric formatting operations are not
     affected.

 -- Data: 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.

 -- Data: locale.CHAR_MAX

     This is a symbolic constant used for different values returned by
     *note localeconv(): 48f.

Example:

     >>> 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.8/Lib/locale.py

   (2) https://tools.ietf.org/html/rfc1766.html

   (3) https://tools.ietf.org/html/rfc1766.html


File: python.info,  Node: Background details hints tips and caveats,  Next: For extension writers and programs that embed Python,  Up: locale --- Internationalization services

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 implementation 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: 3083. 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(): 200f. 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(): b6a.), 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(): 308b,
*note atoi(): 308c, *note format(): 46d, *note str(): 308a.

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 --- Internationalization services

5.23.2.2 For extension writers and programs that embed Python
.............................................................

Extension modules should never call *note setlocale(): 200f, 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: aa. 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 --- Internationalization services

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)

The locale module exposes the C library’s gettext interface on systems
that provide this interface.  It consists of the functions ‘gettext()’,
‘dgettext()’, ‘dcgettext()’, ‘textdomain()’, ‘bindtextdomain()’, and
‘bind_textdomain_codeset()’.  These are similar to the same functions in
the *note gettext: 89. 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: 89. instead.  A known exception
to this rule are applications that link with additional C libraries
which internally invoke ‘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 打造 GUI,  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.

The full list of modules described in this chapter is:

* Menu:

* turtle: turtle --- 龜圖學. 龜圖學
* cmd: cmd --- Support for line-oriented command interpreters. Support for line-oriented command interpreters
* shlex: shlex --- Simple lexical analysis. Simple lexical analysis


File: python.info,  Node: turtle --- 龜圖學,  Next: cmd --- Support for line-oriented command interpreters,  Up: 程式框架

5.24.1 ‘turtle’ — 龜圖學
------------------------

`Source code:' Lib/turtle.py(1)

__________________________________________________________________

* Menu:

* 介紹::
* Overview of available Turtle and Screen methods::
* Methods of RawTurtle/Turtle and corresponding functions::
* Methods of TurtleScreen/Screen and corresponding functions::
* Public classes::
* 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.8/Lib/turtle.py


File: python.info,  Node: 介紹,  Next: Overview of available Turtle and Screen methods,  Up: turtle --- 龜圖學

5.24.1.1 介紹
.............

Turtle graphics is a popular way for introducing programming to kids.
It was part of the original Logo programming language developed by Wally
Feurzeig, Seymour Papert and Cynthia Solomon in 1967.

想像一下，一隻機器龜在 x-y 平面上從 (0, 0) 出發。在 ‘import turtle’ 之後
，給它命令 ‘turtle.forward(15)’ ，然後它就會移動 (在螢幕上！) 15 個單位
像素，方向是朝著其正面對的方向。給它命令 ‘turtle.right(25)’ ，它就會在原
地順時針旋轉 25 度。

Turtle star
...........

龜可以使用重複簡單動作之程式來畫出複雜的形狀。

[python-figures/turtle-star]
     from turtle import *
     color('red', 'yellow')
     begin_fill()
     while True:
         forward(200)
         left(170)
         if abs(pos()) < 1:
             break
     end_fill()
     done()

藉由結合這些類似的命令，複雜的形狀和圖形可以輕易被畫出來。

The *note turtle: 117. module is an extended reimplementation of the
same-named module from the Python standard distribution up to version
Python 2.5.

It tries to keep the merits of the old turtle module and to be (nearly)
100% compatible with it.  This means in the first place to enable the
learning programmer to use all the commands, classes and methods
interactively when using the module from within IDLE run with the ‘-n’
switch.

The turtle module provides turtle graphics primitives, in both
object-oriented and procedure-oriented ways.  Because it uses *note
tkinter: 10d. for the underlying graphics, it needs a version of Python
installed with Tk support.

The object-oriented interface uses essentially two+two classes:

  1. The *note TurtleScreen: 309f. class defines graphics windows as a
     playground for the drawing turtles.  Its constructor needs a
     ‘tkinter.Canvas’ or a *note ScrolledCanvas: 30a0. as argument.  It
     should be used when *note turtle: 117. is used as part of some
     application.

     The function *note Screen(): 30a1. returns a singleton object of a
     *note TurtleScreen: 309f. subclass.  This function should be used
     when *note turtle: 117. is used as a standalone tool for doing
     graphics.  As a singleton object, inheriting from its class is not
     possible.

     All methods of TurtleScreen/Screen also exist as functions, i.e.
     as part of the procedure-oriented interface.

  2. *note RawTurtle: 30a2. (alias: *note RawPen: 30a3.) defines Turtle
     objects which draw on a *note TurtleScreen: 309f.  Its constructor
     needs a Canvas, ScrolledCanvas or TurtleScreen as argument, so the
     RawTurtle objects know where to draw.

     Derived from RawTurtle is the subclass *note Turtle: 30a4. (alias:
     ‘Pen’), which draws on "the" *note Screen: 30a1. instance which is
     automatically created, if not already present.

     All methods of RawTurtle/Turtle also exist as functions, i.e.  part
     of the procedure-oriented interface.

The procedural interface provides functions which are derived from the
methods of the classes *note Screen: 30a1. and *note Turtle: 30a4.  They
have the same names as the corresponding methods.  A screen object is
automatically created whenever a function derived from a Screen method
is called.  An (unnamed) turtle object is automatically created whenever
any of the functions derived from a Turtle method is called.

To use multiple turtles on a screen one has to use the object-oriented
interface.

     備註: In the following documentation the argument list for
     functions is given.  Methods, of course, have the additional first
     argument `self' which is omitted here.


File: python.info,  Node: Overview of available Turtle and Screen methods,  Next: Methods of RawTurtle/Turtle and corresponding functions,  Prev: 介紹,  Up: turtle --- 龜圖學

5.24.1.2 Overview of available Turtle and Screen methods
........................................................

* Menu:

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


File: python.info,  Node: Turtle methods,  Next: Methods of TurtleScreen/Screen,  Up: Overview of available Turtle and Screen methods

5.24.1.3 Turtle methods
.......................

Turtle motion

     Move and draw

               *note forward(): 30a7. | *note fd(): 30a8. 
               *note backward(): 30a9. | *note bk(): 30aa. | *note back(): 30ab. 
               *note right(): 30ac. | *note rt(): 30ad. 
               *note left(): 30ae. | *note lt(): 30af. 
               *note goto(): 30b0. | *note setpos(): 30b1. | *note setposition(): 30b2. 
               *note setx(): 30b3. 
               *note sety(): 30b4. 
               *note setheading(): 30b5. | *note seth(): 30b6. 
               *note home(): 30b7. 
               *note circle(): 30b8. 
               *note dot(): 30b9. 
               *note stamp(): 30ba. 
               *note clearstamp(): 30bb. 
               *note clearstamps(): 30bc. 
               *note undo(): 30bd. 
               *note speed(): 30be. 

     Tell Turtle’s state

               *note position(): 30bf. | *note pos(): 30c0. 
               *note towards(): 30c1. 
               *note xcor(): 30c2. 
               *note ycor(): 30c3. 
               *note heading(): 30c4. 
               *note distance(): 30c5. 

     Setting and measurement

               *note degrees(): 30c6. 
               *note radians(): 30c7. 

Pen control

     Drawing state

               *note pendown(): 30c8. | *note pd(): 30c9. | *note down(): 30ca. 
               *note penup(): 30cb. | *note pu(): 30cc. | *note up(): 30cd. 
               *note pensize(): 30ce. | *note width(): 30cf. 
               *note pen(): 30d0. 
               *note isdown(): 30d1. 

     Color control

               *note color(): 30d2. 
               *note pencolor(): 30d3. 
               *note fillcolor(): 30d4. 

     Filling

               *note filling(): 30d5. 
               *note begin_fill(): 30d6. 
               *note end_fill(): 30d7. 

     More drawing control

               *note reset(): 30d8. 
               *note clear(): 30d9. 
               *note write(): 30da. 

Turtle state

     Visibility

               *note showturtle(): 30db. | *note st(): 30dc. 
               *note hideturtle(): 30dd. | *note ht(): 30de. 
               *note isvisible(): 30df. 

     Appearance

               *note shape(): 30e0. 
               *note resizemode(): 30e1. 
               *note shapesize(): 30e2. | *note turtlesize(): 30e3. 
               *note shearfactor(): 30e4. 
               *note settiltangle(): 30e5. 
               *note tiltangle(): 30e6. 
               *note tilt(): 30e7. 
               *note shapetransform(): 30e8. 
               *note get_shapepoly(): 30e9. 

Using events

          *note onclick(): 30ea. 
          *note onrelease(): 30eb. 
          *note ondrag(): 30ec. 

Special Turtle methods

          *note begin_poly(): 30ed. 
          *note end_poly(): 30ee. 
          *note get_poly(): 30ef. 
          *note clone(): 30f0. 
          *note getturtle(): 30f1. | *note getpen(): 30f2. 
          *note getscreen(): 30f3. 
          *note setundobuffer(): 30f4. 
          *note undobufferentries(): 30f5. 


File: python.info,  Node: Methods of TurtleScreen/Screen,  Prev: Turtle methods,  Up: Overview of available Turtle and Screen methods

5.24.1.4 Methods of TurtleScreen/Screen
.......................................

Window control

          *note bgcolor(): 30f7. 
          *note bgpic(): 30f8. 
          *note clear(): 30d9. | *note clearscreen(): 30f9. 
          *note reset(): 30d8. | *note resetscreen(): 30fa. 
          *note screensize(): 30fb. 
          *note setworldcoordinates(): 30fc. 

Animation control

          *note delay(): 30fd. 
          *note tracer(): 30fe. 
          *note update(): 30ff. 

Using screen events

          *note listen(): 3100. 
          *note onkey(): 3101. | *note onkeyrelease(): 3102. 
          *note onkeypress(): 3103. 
          *note onclick(): 30ea. | *note onscreenclick(): 3104. 
          *note ontimer(): 3105. 
          *note mainloop(): 3106. | *note done(): 3107. 

Settings and special methods

          *note mode(): 3108. 
          *note colormode(): 3109. 
          *note getcanvas(): 310a. 
          *note getshapes(): 310b. 
          *note register_shape(): 310c. | *note addshape(): 310d. 
          *note turtles(): 310e. 
          *note window_height(): 310f. 
          *note window_width(): 3110. 

Input methods

          *note textinput(): e9b. 
          *note numinput(): e9c. 

Methods specific to Screen

          *note bye(): 3111. 
          *note exitonclick(): 3112. 
          *note setup(): 3113. 
          *note title(): 3114. 


File: python.info,  Node: Methods of RawTurtle/Turtle and corresponding functions,  Next: Methods of TurtleScreen/Screen and corresponding functions,  Prev: Overview of available Turtle and Screen methods,  Up: turtle --- 龜圖學

5.24.1.5 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::
* 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.6 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(): 30c6. and *note radians():
     30c7. functions.)  Angle orientation depends on the turtle mode,
     see *note mode(): 3108.

          >>> 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(): 30c6. and *note radians():
     30c7. functions.)  Angle orientation depends on the turtle mode,
     see *note mode(): 3108.

          >>> 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: 3117. (e.g.  as returned by *note pos(): 30c0.).

     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.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(): 3108.).

          >>> 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")
          >>> turtle.stamp()
          11
          >>> turtle.fd(50)

 -- 函式: turtle.clearstamp (stampid)


     參數: ‘stampid’ – an integer, must be return value of previous
     *note stamp(): 30ba. 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):
          ...     turtle.stamp(); turtle.fd(30)
          13
          14
          15
          16
          17
          18
          19
          20
          >>> 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.7 Tell Turtle’s state
............................

 -- 函式: turtle.position ()
 -- 函式: turtle.pos ()

     Return the turtle’s current location (x,y) (as a *note Vec2D: 3117.
     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(): 3108.).

          >>> 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,  Prev: Tell Turtle's state,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.8 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,  Next: Turtle state,  Prev: Settings for measurement,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.9 Pen control
....................

* Menu:

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


File: python.info,  Node: Drawing state,  Next: Color control,  Up: Pen control

5.24.1.10 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(): 30d0. 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

5.24.1.11 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(): 3109.).

     ‘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(): 3109.).

     ‘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))  # Integers, not floats
           >>> 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(): 30d3. and *note fillcolor(): 30d4.

     ‘color(colorstring)’, ‘color((r,g,b))’, ‘color(r,g,b)’

          Inputs as in *note pencolor(): 30d3, 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(): 3109.


File: python.info,  Node: Filling,  Next: More drawing control,  Prev: Color control,  Up: Pen control

5.24.1.12 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():
     30d6.

     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

5.24.1.13 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,  Up: Methods of RawTurtle/Turtle and corresponding functions

5.24.1.14 Turtle state
......................

* Menu:

* Visibility::
* Appearance::


File: python.info,  Node: Visibility,  Next: Appearance,  Up: Turtle state

5.24.1.15 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.16 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(): 310c.

          >>> 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(): 30e2.

        - "noresize": no adaption of the turtle’s appearance takes
          place.

     ‘resizemode("user")’ is called by *note shapesize(): 30e2. 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 shapes’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.settiltangle (angle)


     參數: ‘angle’ – a number

     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).

          >>> turtle.reset()
          >>> turtle.shape("circle")
          >>> turtle.shapesize(5,2)
          >>> turtle.settiltangle(45)
          >>> turtle.fd(50)
          >>> turtle.settiltangle(-45)
          >>> turtle.fd(50)

     3.1 版後已棄用.

 -- 函式: 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.17 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.18 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: 309f. 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’ – an integer or ‘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():
     30bd. 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.19 Compound shapes
.........................

To use compound turtle shapes, which consist of several polygons of
different color, you must use the helper class *note Shape: 3126.
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
     ‘addcomponent()’ method.

     For example:

          >>> 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: 3126. class is used internally by the *note
     register_shape(): 310c. 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 --- 龜圖學

5.24.1.20 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.21 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 ()
 -- 函式: 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.

          備註: 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.reset ()
 -- 函式: turtle.resetscreen ()

     Reset all Turtles on the Screen to their initial state.

          備註: 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.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.22 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(): 30fd.).

          >>> 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(): 30be.


File: python.info,  Node: Using screen events,  Next: Input methods,  Prev: Animation control,  Up: Methods of TurtleScreen/Screen and corresponding functions

5.24.1.23 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():
     3100. 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(): 3100.)

          >>> 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(): 3100.)

          >>> 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.24 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.25 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: 117.  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: 3126. 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.26 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: Help and configuration,  Prev: Methods of TurtleScreen/Screen and corresponding functions,  Up: turtle --- 龜圖學

5.24.1.27 Public classes
........................

 -- 類別: turtle.RawTurtle (canvas)
 -- 類別: turtle.RawPen (canvas)


     參數: ‘canvas’ – a ‘tkinter.Canvas’, a *note ScrolledCanvas: 30a0.
     or a *note TurtleScreen: 309f.

     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: 30a1. object created automatically when
     needed for the first time.

 -- 類別: turtle.TurtleScreen (cv)


     參數: ‘cv’ – a ‘tkinter.Canvas’

     Provides screen oriented methods like ‘setbg()’ etc.  that are
     described above.

 -- 類別: turtle.Screen

     Subclass of TurtleScreen, with *note four methods added: 312e.

 -- 類別: 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(): 3130. 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)

          Example:

               >>> 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()

          See *note Compound shapes: 3125.

 -- 類別: 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’ vector addition

        * ‘a - b’ vector subtraction

        * ‘a * b’ inner product

        * ‘k * a’ and ‘a * k’ multiplication with scalar

        * ‘abs(a)’ absolute value of a

        * ‘a.rotate(angle)’ rotation


File: python.info,  Node: Help and configuration,  Next: turtledemo --- Demo scripts,  Prev: Public classes,  Up: turtle --- 龜圖學

5.24.1.28 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.29 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(): 577. 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.30 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: 117. 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.31 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
     ‘Screen.setup()’ method.

   - Line 5 and 6 correspond to the arguments of the method
     ‘Screen.screensize()’.

   - `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 fillcolor (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: 117.

   - 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(): 3112. to enter the mainloop.

There can be a ‘turtle.cfg’ file in the directory where *note turtle:
117. 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 --- 龜圖學

5.24.1.32 ‘turtledemo’ — Demo scripts
.....................................

The *note turtledemo: 118. 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: 118. 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: 117. 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           ‘tracer()’, delay,
                     graphics pattern                   ‘update()’
                                                        
                                                        
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            ‘ondrag()’
                                                        
                                                        
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         ‘onclick()’
                     program                            
                     
                                                        
peace                elementary                         turtle: appearance and
                                                        animation
                                                        
                                                        
penrose              aperiodic tiling with kites and    ‘stamp()’
                     darts                              
                     
                                                        
planet_and_moon      simulation of gravitational        compound shapes, ‘Vec2D’
                     system                             
                     
                                                        
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   ‘clone()’
                     (using generators)                 
                     
                                                        
two_canvases         simple design                      turtles on two canvases
                                                        
                                                        
wikipedia            a pattern from the wikipedia       ‘clone()’, ‘undo()’
                     article on turtle graphics         
                     
                                                        
yinyang              another elementary example         ‘circle()’
                                                        

Have fun!


File: python.info,  Node: Changes since Python 2 6,  Next: Changes since Python 3 0,  Prev: turtledemo --- Demo scripts,  Up: turtle --- 龜圖學

5.24.1.33 Changes since Python 2.6
..................................

   - The methods ‘Turtle.tracer()’, ‘Turtle.window_width()’ and
     ‘Turtle.window_height()’ have been eliminated.  Methods with these
     names and functionality are now available only as methods of
     ‘Screen’.  The functions derived from these remain available.  (In
     fact already in Python 2.6 these methods were merely duplications
     of the corresponding ‘TurtleScreen’/‘Screen’-methods.)

   - The method ‘Turtle.fill()’ has been eliminated.  The behaviour of
     ‘begin_fill()’ and ‘end_fill()’ have changed slightly: now every
     filling-process must be completed with an ‘end_fill()’ call.

   - A method ‘Turtle.filling()’ 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 --- 龜圖學

5.24.1.34 Changes since Python 3.0
..................................

   - The methods ‘Turtle.shearfactor()’, ‘Turtle.shapetransform()’ and
     ‘Turtle.get_shapepoly()’ have been added.  Thus the full range of
     regular linear transforms is now available for transforming turtle
     shapes.  ‘Turtle.tiltangle()’ has been enhanced in functionality:
     it now can be used to get or set the tiltangle.
     ‘Turtle.settiltangle()’ has been deprecated.

   - The method ‘Screen.onkeypress()’ has been added as a complement to
     ‘Screen.onkey()’ which in fact binds actions to the keyrelease
     event.  Accordingly the latter has got an alias:
     ‘Screen.onkeyrelease()’.

   - The method ‘Screen.mainloop()’ has been added.  So when working
     only with Screen and Turtle objects one must not additionally
     import ‘mainloop()’ anymore.

   - Two input methods has been added ‘Screen.textinput()’ and
     ‘Screen.numinput()’.  These popup 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 --- Support for line-oriented command interpreters,  Next: shlex --- Simple lexical analysis,  Prev: turtle --- 龜圖學,  Up: 程式框架

5.24.2 ‘cmd’ — Support for line-oriented command interpreters
-------------------------------------------------------------

`Source code:' Lib/cmd.py(1)

__________________________________________________________________

The *note Cmd: 313b. 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: 313b. instance or subclass instance is a line-oriented
     interpreter framework.  There is no good reason to instantiate
     *note Cmd: 313b. itself; rather, it’s useful as a superclass of an
     interpreter class you define yourself in order to inherit *note
     Cmd: 313b.’s methods and encapsulate action methods.

     The optional argument `completekey' is the *note readline: df. name
     of a completion key; it defaults to ‘Tab’.  If `completekey' is not
     *note None: 158. and *note readline: df. is available, command
     completion is done automatically.

     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: 312. and *note sys.stdout: 313.

     If you want a given `stdin' to be used, make sure to set the
     instance’s *note use_rawinput: 313c. attribute to ‘False’,
     otherwise `stdin' will be ignored.

* Menu:

* Cmd Objects::
* Cmd Example::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/cmd.py


File: python.info,  Node: Cmd Objects,  Next: Cmd Example,  Up: cmd --- Support for line-oriented command interpreters

5.24.2.1 Cmd Objects
....................

A *note Cmd: 313b. 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: 3140.
     class attribute).

     If the *note readline: df. 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
     ‘do_help()’.  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(): 3141. method
     returns a true value.  The `stop' argument to *note postcmd():
     3141. 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.

     All subclasses of *note Cmd: 313b. 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(): 3143. and *note postcmd(): 3141.
     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(): 3144. 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.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: 313b.; it exists to be
     overridden by subclasses.  The return value is used as the command
     which will be executed by the *note onecmd(): 3142. method; the
     *note precmd(): 3143. 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: 313b.; 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(): 3141.; this
     will be the return value of the *note onecmd(): 3142. 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(): 313f. is called.
     This method is a stub in *note Cmd: 313b.; it exists to be
     overridden by subclasses.

 -- 成員函式: Cmd.postloop ()

     Hook method executed once when *note cmdloop(): 313f. is about to
     return.  This method is a stub in *note Cmd: 313b.; it exists to be
     overridden by subclasses.

Instances of *note Cmd: 313b. 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(): 313f. 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(): 313f. 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(): 313f. uses
     *note input(): c70. to display a prompt and read the next command;
     if false, ‘sys.stdout.write()’ and ‘sys.stdin.readline()’ are used.
     (This means that by importing *note readline: df, 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 Objects,  Up: cmd --- Support for line-oriented command interpreters

5.24.2.2 Cmd Example
....................

The *note cmd: 1a. 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: 117. module.

Basic turtle commands such as *note forward(): 30a7. are added to a
*note Cmd: 313b. 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(): 3143. 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 ‘cmdqueue’ 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 --- Simple lexical analysis,  Prev: cmd --- Support for line-oriented command interpreters,  Up: 程式框架

5.24.3 ‘shlex’ — Simple lexical analysis
----------------------------------------

`Source code:' Lib/shlex.py(1)

__________________________________________________________________

The *note shlex: 57f. 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: e9. 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: 38d. (the default), the parsing of comments in the
     given string will be disabled (setting the *note commenters: 3155.
     attribute of the *note shlex: 57f. instance to the empty string).
     This function operates in POSIX mode by default, but uses non-POSIX
     mode if the `posix' argument is false.

          備註: Since the *note split(): 219. function instantiates a
          *note shlex: 57f. instance, passing ‘None’ for `s' will read
          the string to split from standard input.

 -- 函式: shlex.join (split_command)

     Concatenate the tokens of the list `split_command' and return a
     string.  This function is the inverse of *note split(): 219.

          >>> 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(): a78.).

     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.

     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(): a78. 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():
     219.:

          >>> 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: e9. module defines the following class:

 -- 類別: shlex.shlex (instream=None, infile=None, posix=False,
          punctuation_chars=False)

     A *note shlex: 57f. 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(): 200b. and *note
     readline(): 1c03. 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: 3156. 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: 57f. instance will operate in
     compatibility mode.  When operating in POSIX mode, *note shlex:
     57f. 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: 3157. attribute that appear in
     `punctuation_chars' will be removed from *note wordchars: 3157.
     See *note Improved Compatibility with Shells: 580. for more
     information.  `punctuation_chars' can be set only upon *note shlex:
     57f. instance creation and can’t be modified later.

     3.6 版更變: The `punctuation_chars' parameter was added.

也參考
......

Module *note configparser: 23.

     Parser for configuration files similar to the Windows ‘.ini’ files.

* Menu:

* shlex Objects::
* Parsing Rules::
* Improved Compatibility with Shells::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/shlex.py


File: python.info,  Node: shlex Objects,  Next: Parsing Rules,  Up: shlex --- Simple lexical analysis

5.24.3.1 shlex Objects
......................

A *note shlex: 57f. instance has the following methods:

 -- 成員函式: shlex.get_token ()

     Return a token.  If tokens have been stacked using *note
     push_token(): 315b, pop a token off the stack.  Otherwise, read one
     from the input stream.  If reading encounters an immediate
     end-of-file, *note eof: 315c. 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: 57f. detects a source request (see *note source:
     315f. 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():
     4f5. 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(): 1013. method of the sourced
     input stream when it returns EOF.

     For more explicit control of source stacking, use the *note
     push_source(): 3160. and *note pop_source(): 3161. 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(): 315e. 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: e9. users to
     generate error messages in the standard, parseable format
     understood by Emacs and other Unix tools.

Instances of *note shlex: 57f. 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: f81. 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: 3163. 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: 3166. that will interpret escape
     characters defined in *note escape: 3165.  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:
     57f, getting tokens in a similar way to shell arguments.  When used
     in combination with *note punctuation_chars: f81, tokens will be
     split on whitespace in addition to those characters.

     3.8 版更變: The *note punctuation_chars: f81. attribute was made
     compatible with the *note whitespace_split: 3163. 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: 57f. 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(): 1013. 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: 57f.
     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 Objects,  Up: shlex --- Simple lexical analysis

5.24.3.2 Parsing Rules
......................

When operating in non-POSIX mode, *note shlex: 57f. 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: 3163. 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: 57f. 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: 57f. 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: 3167. (e.g.  ‘"'"’) preserve the literal value of
     all characters within the quotes;

   * Enclosing characters in quotes which are part of *note
     escapedquotes: 3167. (e.g.  ‘'"'’) preserves the literal value of
     all characters within the quotes, with the exception of the
     characters mentioned in *note escape: 3165.  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: 158. value;

   * Quoted empty strings (‘''’) are allowed.


File: python.info,  Node: Improved Compatibility with Shells,  Prev: Parsing Rules,  Up: shlex --- Simple lexical analysis

5.24.3.3 Improved Compatibility with Shells
...........................................

3.6 版新加入.

The *note shlex: e9. 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:
     3157. 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: 3163.
     when using *note punctuation_chars: f81, which will negate *note
     wordchars: 3157. entirely.

For best effect, ‘punctuation_chars’ should be set in conjunction with
‘posix=True’.  (Note that ‘posix=False’ is the default for *note shlex:
57f.)


File: python.info,  Node: 以 Tk 打造 GUI,  Next: 開發工具,  Prev: 程式框架,  Up: Python 標準函式庫 Standard Library

5.25 以 Tk 打造 GUI
===================

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: 10d. package, and its extension,
the *note tkinter.tix: 10f. and the *note tkinter.ttk: 110. modules.

The *note tkinter: 10d. package is a thin object-oriented layer on top
of Tcl/Tk.  To use *note tkinter: 10d, you don’t need to write Tcl code,
but you will need to consult the Tk documentation, and occasionally the
Tcl documentation.  *note tkinter: 10d. is a set of wrappers that
implement the Tk widgets as Python classes.  In addition, the internal
module ‘_tkinter’ provides a threadsafe mechanism which allows Python
and Tcl to interact.

*note tkinter: 10d.’s chief virtues are that it is fast, and that it
usually comes bundled with Python.  Although its standard documentation
is weak, good material is available, which includes: references,
tutorials, a book and others.  *note tkinter: 10d. is also famous for
having an outdated look and feel, which has been vastly improved in Tk
8.5.  Nevertheless, there are many other GUI libraries that you could be
interested in.  For more information about alternatives, see the *note
其它的 GUI: 3172. section.

* Menu:

* tkinter: tkinter --- Python interface to Tcl/Tk. Python interface to Tcl/Tk
* tkinter.ttk: tkinter ttk --- Tk themed widgets. Tk themed widgets
* tkinter.tix: tkinter tix --- Extension widgets for Tk. Extension widgets for Tk
* tkinter.scrolledtext: tkinter scrolledtext --- Scrolled Text Widget. Scrolled Text Widget
* IDLE: IDLE<54>.
* 其它的 GUI::


File: python.info,  Node: tkinter --- Python interface to Tcl/Tk,  Next: tkinter ttk --- Tk themed widgets,  Up: 以 Tk 打造 GUI

5.25.1 ‘tkinter’ — Python interface to Tcl/Tk
---------------------------------------------

`Source code:' Lib/tkinter/__init__.py(1)

__________________________________________________________________

The *note tkinter: 10d. package ("Tk interface") is the standard Python
interface to the Tk GUI toolkit.  Both Tk and *note tkinter: 10d. are
available on most Unix platforms, as well as on Windows systems.  (Tk
itself is not part of Python; it is maintained at ActiveState.)

Running ‘python -m tkinter’ from the command line should open a window
demonstrating a simple Tk interface, letting you know that *note
tkinter: 10d. 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 documentation:

Python Tkinter Resources(2)

     The Python Tkinter Topic Guide provides a great deal of information
     on using Tk from Python and links to other sources of information
     on Tk.

TKDocs(3)

     Extensive tutorial plus friendlier widget pages for some of the
     widgets.

Tkinter 8.5 reference: a GUI for Python(4)

     On-line reference material.

Tkinter docs from effbot(5)

     Online reference for tkinter supported by effbot.org.

Programming Python(6)

     Book by Mark Lutz, has excellent coverage of Tkinter.

Modern Tkinter for Busy Python Developers(7)

     Book by Mark Roseman about building attractive and modern graphical
     user interfaces with Python and Tkinter.

Python and Tkinter Programming(8)

     Book by John Grayson (ISBN 1-884777-81-3).

Tcl/Tk documentation:

Tk commands(9)

     Most commands are available as *note tkinter: 10d. or *note
     tkinter.ttk: 110. classes.  Change ’8.6’ to match the version of
     your Tcl/Tk installation.

Tcl/Tk recent man pages(10)

     Recent Tcl/Tk manuals on www.tcl.tk.

ActiveState Tcl Home Page(11)

     The Tk/Tcl development is largely taking place at ActiveState.

Tcl and the Tk Toolkit(12)

     Book by John Ousterhout, the inventor of Tcl.

Practical Programming in Tcl and Tk(13)

     Brent Welch’s encyclopedic book.

* Menu:

* Tkinter Modules::
* Tkinter Life Preserver::
* A (Very) Quick Look at Tcl/Tk: A Very Quick Look at Tcl/Tk.
* Mapping Basic Tk into Tkinter::
* How Tk and Tkinter are Related::
* Handy Reference::
* File Handlers::

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/tkinter/__init__.py

   (2) https://wiki.python.org/moin/TkInter

   (3) http://www.tkdocs.com/

   (4) https://www.tkdocs.com/shipman/

   (5) http://effbot.org/tkinterbook/

   (6) http://learning-python.com/about-pp4e.html

   (7) 
https://www.amazon.com/Modern-Tkinter-Python-Developers-ebook/dp/B0071QDNLO/

   (8) https://www.manning.com/books/python-and-tkinter-programming

   (9) https://www.tcl.tk/man/tcl8.6/TkCmd/contents.htm

   (10) https://www.tcl.tk/doc/

   (11) https://tcl.tk

   (12) https://www.amazon.com/exec/obidos/ASIN/020163337X

   (13) http://www.beedub.com/book/


File: python.info,  Node: Tkinter Modules,  Next: Tkinter Life Preserver,  Up: tkinter --- Python interface to Tcl/Tk

5.25.1.1 Tkinter Modules
........................

Most of the time, *note tkinter: 10d. is all you really need, but a
number of additional modules are available as well.  The Tk interface is
located in a binary module named ‘_tkinter’.  This module contains the
low-level interface to Tk, 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.

In addition to the Tk interface module, *note tkinter: 10d. includes a
number of Python modules, ‘tkinter.constants’ being one of the most
important.  Importing *note tkinter: 10d. will automatically import
‘tkinter.constants’, so, usually, to use Tkinter all you need is a
simple import statement:

     import tkinter

Or, more often:

     from tkinter import *

 -- 類別: tkinter.Tk (screenName=None, baseName=None, className='Tk',
          useTk=1)

     The *note Tk: 3176. class is instantiated without arguments.  This
     creates a toplevel widget of Tk which usually is the main window of
     an application.  Each instance has its own associated Tcl
     interpreter.

 -- 函式: tkinter.Tcl (screenName=None, baseName=None, className='Tk',
          useTk=0)

     The *note Tcl(): 3177. function is a factory function which creates
     an object much like that created by the *note Tk: 3176. 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(): 3177. object can have a
     Toplevel window created (and the Tk subsystem initialized) by
     calling its ‘loadtk()’ method.

Other modules that provide Tk support include:

*note tkinter.scrolledtext: 10e.

     Text widget with a vertical scroll bar built in.

‘tkinter.colorchooser’

     Dialog to let the user choose a color.

‘tkinter.commondialog’

     Base class for the dialogs defined in the other modules listed
     here.

‘tkinter.filedialog’

     Common dialogs to allow the user to specify a file to open or save.

‘tkinter.font’

     Utilities to help work with fonts.

‘tkinter.messagebox’

     Access to standard Tk dialog boxes.

‘tkinter.simpledialog’

     Basic dialogs and convenience functions.

‘tkinter.dnd’

     Drag-and-drop support for *note tkinter: 10d.  This is experimental
     and should become deprecated when it is replaced with the Tk DND.

*note turtle: 117.

     Turtle graphics in a Tk window.


File: python.info,  Node: Tkinter Life Preserver,  Next: A Very Quick Look at Tcl/Tk,  Prev: Tkinter Modules,  Up: tkinter --- Python interface to Tcl/Tk

5.25.1.2 Tkinter Life Preserver
...............................

This section is not designed to be an exhaustive tutorial on either Tk
or Tkinter.  Rather, it is intended as a stop gap, providing some
introductory orientation on the system.

Credits:

   * Tk was written by John Ousterhout while at Berkeley.

   * Tkinter was written by Steen Lumholt and Guido van Rossum.

   * This Life Preserver was written by Matt Conway at the University of
     Virginia.

   * The HTML rendering, and some liberal editing, was produced from a
     FrameMaker version by Ken Manheimer.

   * Fredrik Lundh elaborated and revised the class interface
     descriptions, to get them current with Tk 4.2.

   * Mike Clarkson converted the documentation to LaTeX, and compiled
     the User Interface chapter of the reference manual.

* Menu:

* How To Use This Section::
* A Simple Hello World Program::


File: python.info,  Node: How To Use This Section,  Next: A Simple Hello World Program,  Up: Tkinter Life Preserver

5.25.1.3 How To Use This Section
................................

This section is designed in two parts: the first half (roughly) covers
background material, while the second half can be taken to the keyboard
as a handy reference.

When trying to answer questions of the form "how do I do blah", it is
often best to find out how to do "blah" in straight Tk, and then convert
this back into the corresponding *note tkinter: 10d. call.  Python
programmers can often guess at the correct Python command by looking at
the Tk documentation.  This means that in order to use Tkinter, you will
have to know a little bit about Tk.  This document can’t fulfill that
role, so the best we can do is point you to the best documentation that
exists.  Here are some hints:

   * The authors strongly suggest getting a copy of the Tk man pages.
     Specifically, the man pages in the ‘manN’ directory are most
     useful.  The ‘man3’ man pages describe the C interface to the Tk
     library and thus are not especially helpful for script writers.

   * Addison-Wesley publishes a book called Tcl and the Tk Toolkit by
     John Ousterhout (ISBN 0-201-63337-X) which is a good introduction
     to Tcl and Tk for the novice.  The book is not exhaustive, and for
     many details it defers to the man pages.

   * ‘tkinter/__init__.py’ is a last resort for most, but can be a good
     place to go when nothing else makes sense.


File: python.info,  Node: A Simple Hello World Program,  Prev: How To Use This Section,  Up: Tkinter Life Preserver

5.25.1.4 A Simple Hello World Program
.....................................

     import tkinter as tk

     class Application(tk.Frame):
         def __init__(self, master=None):
             super().__init__(master)
             self.master = master
             self.pack()
             self.create_widgets()

         def create_widgets(self):
             self.hi_there = tk.Button(self)
             self.hi_there["text"] = "Hello World\n(click me)"
             self.hi_there["command"] = self.say_hi
             self.hi_there.pack(side="top")

             self.quit = tk.Button(self, text="QUIT", fg="red",
                                   command=self.master.destroy)
             self.quit.pack(side="bottom")

         def say_hi(self):
             print("hi there, everyone!")

     root = tk.Tk()
     app = Application(master=root)
     app.mainloop()


File: python.info,  Node: A Very Quick Look at Tcl/Tk,  Next: Mapping Basic Tk into Tkinter,  Prev: Tkinter Life Preserver,  Up: tkinter --- Python interface to Tcl/Tk

5.25.1.5 A (Very) Quick Look at Tcl/Tk
......................................

The class hierarchy looks complicated, but in actual practice,
application programmers almost always refer to the classes at the very
bottom of the hierarchy.

註解：

   * These classes are provided for the purposes of organizing certain
     functions under one namespace.  They aren’t meant to be
     instantiated independently.

   * The *note Tk: 3176. class is meant to be instantiated only once in
     an application.  Application programmers need not instantiate one
     explicitly, the system creates one whenever any of the other
     classes are instantiated.

   * The ‘Widget’ class is not meant to be instantiated, it is meant
     only for subclassing to make "real" widgets (in C++, this is called
     an ’abstract class’).

To make use of this reference material, there will be times when you
will need to know how to read short passages of Tk and how to identify
the various parts of a Tk command.  (See section *note Mapping Basic Tk
into Tkinter: 317c. for the *note tkinter: 10d. equivalents of what’s
below.)

Tk scripts are Tcl programs.  Like all Tcl programs, Tk scripts are just
lists of tokens separated by spaces.  A Tk widget is just its `class',
the `options' that help configure it, and the `actions' that make it do
useful things.

To make a widget in Tk, the command is always of the form:

     classCommand newPathname options

`classCommand'

     denotes which kind of widget to make (a button, a label, a menu...)

`newPathname'

     is the new name for this widget.  All names in Tk must be unique.
     To help enforce this, widgets in Tk are named with `pathnames',
     just like files in a file system.  The top level widget, the
     `root', is called ‘.’ (period) and children are delimited by more
     periods.  For example, ‘.myApp.controlPanel.okButton’ might be the
     name of a widget.

`options'

     configure the widget’s appearance and in some cases, its behavior.
     The options come in the form of a list of flags and values.  Flags
     are preceded by a ’-’, like Unix shell command flags, and values
     are put in quotes if they are more than one word.

For example:

     button   .fred   -fg red -text "hi there"
        ^       ^     \______________________/
        |       |                |
      class    new            options
     command  widget  (-opt val -opt val ...)

Once created, the pathname to the widget becomes a new command.  This
new `widget command' is the programmer’s handle for getting the new
widget to perform some `action'.  In C, you’d express this as
someAction(fred, someOptions), in C++, you would express this as
fred.someAction(someOptions), and in Tk, you say:

     .fred someAction someOptions

Note that the object name, ‘.fred’, starts with a dot.

As you’d expect, the legal values for `someAction' will depend on the
widget’s class: ‘.fred disable’ works if fred is a button (fred gets
greyed out), but does not work if fred is a label (disabling of labels
is not supported in Tk).

The legal values of `someOptions' is action dependent.  Some actions,
like ‘disable’, require no arguments, others, like a text-entry box’s
‘delete’ command, would need arguments to specify what range of text to
delete.


File: python.info,  Node: Mapping Basic Tk into Tkinter,  Next: How Tk and Tkinter are Related,  Prev: A Very Quick Look at Tcl/Tk,  Up: tkinter --- Python interface to Tcl/Tk

5.25.1.6 Mapping Basic Tk into Tkinter
......................................

Class commands in Tk correspond to class constructors in Tkinter.

     button .fred                =====>  fred = Button()

The master of an object is implicit in the new name given to it at
creation time.  In Tkinter, masters are specified explicitly.

     button .panel.fred          =====>  fred = Button(panel)

The configuration options in Tk are given in lists of hyphened tags
followed by values.  In Tkinter, options are specified as
keyword-arguments in the instance constructor, and keyword-args for
configure calls or as instance indices, in dictionary style, for
established instances.  See section *note Setting Options: 317e. on
setting options.

     button .fred -fg red        =====>  fred = Button(panel, fg="red")
     .fred configure -fg red     =====>  fred["fg"] = red
                                 OR ==>  fred.config(fg="red")

In Tk, to perform an action on a widget, use the widget name as a
command, and follow it with an action name, possibly with arguments
(options).  In Tkinter, you call methods on the class instance to invoke
actions on the widget.  The actions (methods) that a given widget can
perform are listed in ‘tkinter/__init__.py’.

     .fred invoke                =====>  fred.invoke()

To give a widget to the packer (geometry manager), you call pack with
optional arguments.  In Tkinter, the Pack class holds all this
functionality, and the various forms of the pack command are implemented
as methods.  All widgets in *note tkinter: 10d. are subclassed from the
Packer, and so inherit all the packing methods.  See the *note
tkinter.tix: 10f. module documentation for additional information on the
Form geometry manager.

     pack .fred -side left       =====>  fred.pack(side="left")


File: python.info,  Node: How Tk and Tkinter are Related,  Next: Handy Reference,  Prev: Mapping Basic Tk into Tkinter,  Up: tkinter --- Python interface to Tcl/Tk

5.25.1.7 How Tk and Tkinter are Related
.......................................

From the top down:

Your App Here (Python)

     A Python application makes a *note tkinter: 10d. call.

tkinter (Python Package)

     This call (say, for example, creating a button widget), is
     implemented in the *note tkinter: 10d. package, which is written in
     Python.  This Python function will parse the commands and the
     arguments and convert them into a form that makes them look as if
     they had come from a Tk script instead of a Python script.

_tkinter (C)

     These commands and their arguments will be passed to a C function
     in the ‘_tkinter’ - note the underscore - extension module.

Tk Widgets (C and Tcl)

     This C function is able to make calls into other C modules,
     including the C functions that make up the Tk library.  Tk is
     implemented in C and some Tcl.  The Tcl part of the Tk widgets is
     used to bind certain default behaviors to widgets, and is executed
     once at the point where the Python *note tkinter: 10d. package is
     imported.  (The user never sees this stage).

Tk (C)

     The Tk part of the Tk Widgets implement the final mapping to ...

Xlib (C)

     the Xlib library to draw graphics on the screen.


File: python.info,  Node: Handy Reference,  Next: File Handlers,  Prev: How Tk and Tkinter are Related,  Up: tkinter --- Python interface to Tcl/Tk

5.25.1.8 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.9 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)’ 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       Meaning                               Example
                                                  
---------------------------------------------------------------------
                                                  
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'’
                                                  

Example:

     >>> 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.


File: python.info,  Node: The Packer,  Next: Packer Options,  Prev: Setting Options,  Up: Handy Reference

5.25.1.10 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.11 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.12 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: 10d. 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: 10d.

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.

For example:

     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.13 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: 10d,
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.

Here are some examples of typical usage:

     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.14 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.15 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
     man page and page 201 of John Ousterhout’s book 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.

For example:

     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
                                            


File: python.info,  Node: The index Parameter,  Next: Images,  Prev: Bindings and Events,  Up: Handy Reference

5.25.1.16 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: 10d.
     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.17 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).

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) http://python-pillow.org/


File: python.info,  Node: File Handlers,  Prev: Handy Reference,  Up: tkinter --- Python interface to Tcl/Tk

5.25.1.18 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: 58d. or *note TextIOBase: c3e.
*note read(): 1d5d. or *note readline(): 1708. methods, since these will
insist on reading a predefined number of bytes.  For sockets, the *note
recv(): 67c. or *note recvfrom(): 67d. 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(): 1f0f.
     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.

 -- Data: tkinter.READABLE
 -- Data: tkinter.WRITABLE
 -- Data: tkinter.EXCEPTION

     Constants used in the `mask' arguments.


File: python.info,  Node: tkinter ttk --- Tk themed widgets,  Next: tkinter tix --- Extension widgets for Tk,  Prev: tkinter --- Python interface to Tcl/Tk,  Up: 以 Tk 打造 GUI

5.25.2 ‘tkinter.ttk’ — Tk themed widgets
----------------------------------------

`Source code:' Lib/tkinter/ttk.py(1)

__________________________________________________________________

The *note tkinter.ttk: 110. module provides access to the Tk themed
widget set, introduced in Tk 8.5.  If Python has not been compiled
against Tk 8.5, this module can still be accessed if `Tile' has been
installed.  The former method using Tk 8.5 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: 110. 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:

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/tkinter/ttk.py

   (2) https://core.tcl.tk/tips/doc/trunk/tip/48.md


File: python.info,  Node: Using Ttk,  Next: Ttk Widgets,  Up: tkinter ttk --- Tk themed widgets

5.25.2.1 Using 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: 110. 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) http://tktable.sourceforge.net/tile/doc/converting.txt


File: python.info,  Node: Ttk Widgets,  Next: Widget,  Prev: Using Ttk,  Up: tkinter ttk --- Tk themed widgets

5.25.2.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: 402.  The other six are new: *note Combobox: 3195, *note
Notebook: 3196, *note Progressbar: 3197, ‘Separator’, ‘Sizegrip’ and
*note Treeview: 2be.  And all them are subclasses of *note Widget: 3198.

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: 3199, see the *note Style:
319a. class documentation.


File: python.info,  Node: Widget,  Next: Combobox,  Prev: Ttk Widgets,  Up: tkinter ttk --- Tk themed widgets

5.25.2.3 Widget
...............

‘ttk.Widget’ defines standard options and methods supported by Tk themed
widgets and is not supposed to be directly instantiated.

* Menu:

* Standard Options::
* Scrollable Widget Options::
* Label Options::
* Compatibility Options::
* Widget States::
* ttk.Widget: ttk Widget.


File: python.info,  Node: Standard Options,  Next: Scrollable Widget Options,  Up: Widget

5.25.2.4 Standard Options
.........................

All the ‘ttk’ Widgets accepts the following options:

     Option          描述
                     
     -----------------------------------------------------------------------------------
                     
     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: Standard Options,  Up: Widget

5.25.2.5 Scrollable Widget Options
..................................

The following options are supported by widgets that are controlled by a
scrollbar.

     Option               描述
                          
     -----------------------------------------------------------------------------------
                          
     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: Compatibility Options,  Prev: Scrollable Widget Options,  Up: Widget

5.25.2.6 Label Options
......................

The following options are supported by labels, buttons and other
button-like widgets.

     Option             描述
                        
     -----------------------------------------------------------------------------------
                        
     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(): edb, 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: Compatibility Options,  Next: Widget States,  Prev: Label Options,  Up: Widget

5.25.2.7 Compatibility Options
..............................

     Option       描述
                  
     ----------------------------------------------------------------------------------
                  
     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(): 31a0. method does not
                  affect this option.
                  


File: python.info,  Node: Widget States,  Next: ttk Widget,  Prev: Compatibility Options,  Up: Widget

5.25.2.8 Widget States
......................

The widget state is a bitmap of independent state flags.

     Flag             描述
                      
     -----------------------------------------------------------------------------------
                      
     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.2.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 themed widgets

5.25.2.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: 3198.: ‘Widget.cget()’,
‘Widget.configure()’, *note Widget.identify(): 31a3, *note
Widget.instate(): 31a4. and *note Widget.state(): 31a0, 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:

* Options::
* Virtual events::
* ttk.Combobox: ttk Combobox.


File: python.info,  Node: Options,  Next: Virtual events,  Up: Combobox

5.25.2.11 Options
.................

This widget accepts the following specific options:

     Option                描述
                           
     -----------------------------------------------------------------------------------
                           
     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: Options,  Up: Combobox

5.25.2.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.2.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 themed widgets

5.25.2.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: 3198.: ‘Widget.cget()’,
‘Widget.configure()’, *note Widget.identify(): 31a3, *note
Widget.instate(): 31a4. and *note Widget.state(): 31a0, 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:

* Options: Options<2>.
* Virtual events: Virtual events<2>.
* ttk.Spinbox: ttk Spinbox.


File: python.info,  Node: Options<2>,  Next: Virtual events<2>,  Up: Spinbox

5.25.2.15 Options
.................

This widget accepts the following specific options:

Option                     描述
                           
--------------------------------------------------------------------------------------
                           
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: Options<2>,  Up: Spinbox

5.25.2.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.2.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 themed widgets

5.25.2.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:

* Options: Options<3>.
* Tab Options::
* Tab Identifiers::
* Virtual Events::
* ttk.Notebook: ttk Notebook.


File: python.info,  Node: Options<3>,  Next: Tab Options,  Up: Notebook

5.25.2.19 Options
.................

This widget accepts the following specific options:

     Option        描述
                   
     -----------------------------------------------------------------------------------
                   
     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: Options<3>,  Up: Notebook

5.25.2.20 Tab Options
.....................

There are also specific options for tabs:

     Option          描述
                     
     -----------------------------------------------------------------------------------
                     
     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: 3198.
                     
                     
     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: 319e. 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(): 31b5. is
                     called.
                     


File: python.info,  Node: Tab Identifiers,  Next: Virtual Events,  Prev: Tab Options,  Up: Notebook

5.25.2.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(): 31b7.)


File: python.info,  Node: Virtual Events,  Next: ttk Notebook,  Prev: Tab Identifiers,  Up: Notebook

5.25.2.22 Virtual Events
........................

This widget generates a `<<NotebookTabChanged>>' virtual event after a
new tab is selected.


File: python.info,  Node: ttk Notebook,  Prev: Virtual Events,  Up: Notebook

5.25.2.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.

          See *note Tab Options: 31b4. for the list of available
          options.

      -- 成員函式: 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():
          31ba. 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.

          See *note Tab Options: 31b4. for the list of available
          options.

      -- 成員函式: 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 themed widgets

5.25.2.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:

* Options: Options<4>.
* ttk.Progressbar: ttk Progressbar.


File: python.info,  Node: Options<4>,  Next: ttk Progressbar,  Up: Progressbar

5.25.2.25 Options
.................

This widget accepts the following specific options:

     Option         描述
                    
     -----------------------------------------------------------------------------------
                    
     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           One of "determinate" or "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: Options<4>,  Up: Progressbar

5.25.2.26 ttk.Progressbar
.........................

 -- 類別: tkinter.ttk.Progressbar

      -- 成員函式: start (interval=None)

          Begin autoincrement mode: schedules a recurring timer event
          that calls *note Progressbar.step(): 31c6. 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(): 31c5. for this
          progress bar.


File: python.info,  Node: Separator,  Next: Sizegrip,  Prev: Progressbar,  Up: tkinter ttk --- Tk themed widgets

5.25.2.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:

* Options: Options<5>.


File: python.info,  Node: Options<5>,  Up: Separator

5.25.2.28 Options
.................

This widget accepts the following specific option:

     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 themed widgets

5.25.2.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.2.30 Platform-specific notes
.................................

   * On MacOS X, 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.2.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 themed widgets

5.25.2.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: 31ce.

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:
319d. and the methods *note Treeview.xview(): 31cf. and *note
Treeview.yview(): 31d0.

* Menu:

* Options: Options<6>.
* Item Options::
* Tag Options::
* Column Identifiers::
* Virtual Events: Virtual Events<2>.
* ttk.Treeview: ttk Treeview.


File: python.info,  Node: Options<6>,  Next: Item Options,  Up: Treeview

5.25.2.33 Options
.................

This widget accepts the following specific options:

     Option               描述
                          
     ----------------------------------------------------------------------------------
                          
     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: Options<6>,  Up: Treeview

5.25.2.34 Item Options
......................

The following item options may be specified for items in the insert and
item widget commands.

     Option       描述
                  
     ---------------------------------------------------------------------------------
                  
     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.2.35 Tag Options
.....................

The following options may be specified on tags:

     Option           描述
                      
     ---------------------------------------------------------------------------------
                      
     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: Virtual Events<2>,  Prev: Tag Options,  Up: Treeview

5.25.2.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: Virtual Events<2>,  Next: ttk Treeview,  Prev: Column Identifiers,  Up: Treeview

5.25.2.37 Virtual Events
........................

The Treeview widget generates the following virtual events.

     Event                    描述
                              
     --------------------------------------------------------------------------------
                              
     <<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(): 31d5. and *note Treeview.selection(): 2bd.
methods can be used to determine the affected item or items.


File: python.info,  Node: ttk Treeview,  Prev: Virtual Events<2>,  Up: Treeview

5.25.2.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.

          The valid options/values are:

             * 
               id

                    Returns the column name.  This is a read-only
                    option.

             * 
               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.

          The valid options/values are:

             * 
               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.

          See *note Item Options: 31d2. for the list of available
          points.

      -- 成員函式: 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)

          An alias for *note Treeview.move(): 31e7.

      -- 成員函式: see (item)

          Ensure that `item' is visible.

          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)

          Add `items' to the selection.

          3.6 版更變: `items' can be passed as separate arguments, not
          just as a single tuple.

      -- 成員函式: selection_remove (*items)

          Remove `items' from the selection.

          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 themed widgets

5.25.2.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: 31f8.

          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.6a for Windows
          XP and Vista and is not described here.

          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.

          If "from" is used as the value of `etype', *note
          element_create(): 31f9. 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.

      -- 成員函式: 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(): 31fd.

      -- 成員函式: 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(): 31f5, *note Style.map(): edb,
          *note Style.layout(): 31f7. and *note Style.element_create():
          31f9. 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 ()

          Returns a list of all known themes.

      -- 成員函式: 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) http://tktable.sourceforge.net/tile/tile-tcl2004.pdf


File: python.info,  Node: Layouts,  Up: Ttk Styling

5.25.2.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.  Valid options/values are:

        * 
          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 or 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(): 31a3. 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: 31f8.


File: python.info,  Node: tkinter tix --- Extension widgets for Tk,  Next: tkinter scrolledtext --- Scrolled Text Widget,  Prev: tkinter ttk --- Tk themed widgets,  Up: 以 Tk 打造 GUI

5.25.3 ‘tkinter.tix’ — Extension widgets for Tk
-----------------------------------------------

`Source code:' Lib/tkinter/tix.py(1)

3.6 版後已棄用: This Tk extension is unmaintained and should not be used
in new code.  Use *note tkinter.ttk: 110. instead.

__________________________________________________________________

The *note tkinter.tix: 10f. (Tk Interface Extension) module provides an
additional rich set of widgets.  Although the standard Tk library has
many useful widgets, they are far from complete.  The *note tkinter.tix:
10f. library provides most of the commonly needed widgets that are
missing from standard Tk: *note HList: 3204, *note ComboBox: 3205, *note
Control: 3206. (a.k.a.  SpinBox) and an assortment of scrollable
widgets.  *note tkinter.tix: 10f. also includes many more widgets that
are generally useful in a wide range of applications: *note NoteBook:
3207, *note FileEntry: 3208, *note PanedWindow: 3209, etc; there are
more than 40 of them.

With all these new widgets, you can introduce new interaction techniques
into applications, creating more useful and more intuitive user
interfaces.  You can design your application by choosing the most
appropriate widgets to match the special needs of your application and
users.

也參考
......

Tix Homepage(2)

     The home page for ‘Tix’.  This includes links to additional
     documentation and downloads.

Tix Man Pages(3)

     On-line version of the man pages and reference material.

Tix Programming Guide(4)

     On-line version of the programmer’s reference material.

Tix Development Applications(5)

     Tix applications for development of Tix and Tkinter programs.  Tide
     applications work under Tk or Tkinter, and include ‘TixInspect’, an
     inspector to remotely modify and debug Tix/Tk/Tkinter applications.

* Menu:

* Using Tix::
* Tix Widgets::
* Tix Commands::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/tkinter/tix.py

   (2) http://tix.sourceforge.net/

   (3) http://tix.sourceforge.net/dist/current/man/

   (4) 
http://tix.sourceforge.net/dist/current/docs/tix-book/tix.book.html

   (5) http://tix.sourceforge.net/Tixapps/src/Tide.html


File: python.info,  Node: Using Tix,  Next: Tix Widgets,  Up: tkinter tix --- Extension widgets for Tk

5.25.3.1 Using Tix
..................

 -- 類別: tkinter.tix.Tk (screenName=None, baseName=None,
          className='Tix')

     Toplevel widget of Tix which represents mostly the main window of
     an application.  It has an associated Tcl interpreter.

     Classes in the *note tkinter.tix: 10f. module subclasses the
     classes in the *note tkinter: 10d.  The former imports the latter,
     so to use *note tkinter.tix: 10f. with Tkinter, all you need to do
     is to import one module.  In general, you can just import *note
     tkinter.tix: 10f, and replace the toplevel call to *note
     tkinter.Tk: 3176. with ‘tix.Tk’:

          from tkinter import tix
          from tkinter.constants import *
          root = tix.Tk()

To use *note tkinter.tix: 10f, you must have the Tix widgets installed,
usually alongside your installation of the Tk widgets.  To test your
installation, try the following:

     from tkinter import tix
     root = tix.Tk()
     root.tk.eval('package require Tix')


File: python.info,  Node: Tix Widgets,  Next: Tix Commands,  Prev: Using Tix,  Up: tkinter tix --- Extension widgets for Tk

5.25.3.2 Tix Widgets
....................

Tix(1) introduces over 40 widget classes to the *note tkinter: 10d.
repertoire.

* Menu:

* Basic Widgets::
* File Selectors::
* Hierarchical ListBox::
* Tabular ListBox::
* Manager Widgets::
* Image Types::
* Miscellaneous Widgets::
* Form Geometry Manager::

   ---------- Footnotes ----------

   (1) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/TixIntro.htm


File: python.info,  Node: Basic Widgets,  Next: File Selectors,  Up: Tix Widgets

5.25.3.3 Basic Widgets
......................

 -- 類別: tkinter.tix.Balloon

     A Balloon(1) that pops up over a widget to provide help.  When the
     user moves the cursor inside a widget to which a Balloon widget has
     been bound, a small pop-up window with a descriptive message will
     be shown on the screen.

 -- 類別: tkinter.tix.ButtonBox

     The ButtonBox(2) widget creates a box of buttons, such as is
     commonly used for ‘Ok Cancel’.

 -- 類別: tkinter.tix.ComboBox

     The ComboBox(3) widget is similar to the combo box control in MS
     Windows.  The user can select a choice by either typing in the
     entry subwidget or selecting from the listbox subwidget.

 -- 類別: tkinter.tix.Control

     The Control(4) widget is also known as the ‘SpinBox’ widget.  The
     user can adjust the value by pressing the two arrow buttons or by
     entering the value directly into the entry.  The new value will be
     checked against the user-defined upper and lower limits.

 -- 類別: tkinter.tix.LabelEntry

     The LabelEntry(5) widget packages an entry widget and a label into
     one mega widget.  It can be used to simplify the creation of
     "entry-form" type of interface.

 -- 類別: tkinter.tix.LabelFrame

     The LabelFrame(6) widget packages a frame widget and a label into
     one mega widget.  To create widgets inside a LabelFrame widget, one
     creates the new widgets relative to the ‘frame’ subwidget and
     manage them inside the ‘frame’ subwidget.

 -- 類別: tkinter.tix.Meter

     The Meter(7) widget can be used to show the progress of a
     background job which may take a long time to execute.

 -- 類別: tkinter.tix.OptionMenu

     The OptionMenu(8) creates a menu button of options.

 -- 類別: tkinter.tix.PopupMenu

     The PopupMenu(9) widget can be used as a replacement of the
     ‘tk_popup’ command.  The advantage of the ‘Tix’ *note PopupMenu:
     3214. widget is it requires less application code to manipulate.

 -- 類別: tkinter.tix.Select

     The Select(10) widget is a container of button subwidgets.  It can
     be used to provide radio-box or check-box style of selection
     options for the user.

 -- 類別: tkinter.tix.StdButtonBox

     The StdButtonBox(11) widget is a group of standard buttons for
     Motif-like dialog boxes.

   ---------- Footnotes ----------

   (1) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixBalloon.htm

   (2) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixButtonBox.htm

   (3) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixComboBox.htm

   (4) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixControl.htm

   (5) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixLabelEntry.htm

   (6) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixLabelFrame.htm

   (7) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixMeter.htm

   (8) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixOptionMenu.htm

   (9) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixPopupMenu.htm

   (10) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixSelect.htm

   (11) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixStdButtonBox.htm


File: python.info,  Node: File Selectors,  Next: Hierarchical ListBox,  Prev: Basic Widgets,  Up: Tix Widgets

5.25.3.4 File Selectors
.......................

 -- 類別: tkinter.tix.DirList

     The DirList(1) widget displays a list view of a directory, its
     previous directories and its sub-directories.  The user can choose
     one of the directories displayed in the list or change to another
     directory.

 -- 類別: tkinter.tix.DirTree

     The DirTree(2) widget displays a tree view of a directory, its
     previous directories and its sub-directories.  The user can choose
     one of the directories displayed in the list or change to another
     directory.

 -- 類別: tkinter.tix.DirSelectDialog

     The DirSelectDialog(3) widget presents the directories in the file
     system in a dialog window.  The user can use this dialog window to
     navigate through the file system to select the desired directory.

 -- 類別: tkinter.tix.DirSelectBox

     The *note DirSelectBox: 321b. is similar to the standard Motif(TM)
     directory-selection box.  It is generally used for the user to
     choose a directory.  DirSelectBox stores the directories mostly
     recently selected into a ComboBox widget so that they can be
     quickly selected again.

 -- 類別: tkinter.tix.ExFileSelectBox

     The ExFileSelectBox(4) widget is usually embedded in a
     tixExFileSelectDialog widget.  It provides a convenient method for
     the user to select files.  The style of the *note ExFileSelectBox:
     321c. widget is very similar to the standard file dialog on MS
     Windows 3.1.

 -- 類別: tkinter.tix.FileSelectBox

     The FileSelectBox(5) is similar to the standard Motif(TM)
     file-selection box.  It is generally used for the user to choose a
     file.  FileSelectBox stores the files mostly recently selected into
     a *note ComboBox: 3205. widget so that they can be quickly selected
     again.

 -- 類別: tkinter.tix.FileEntry

     The FileEntry(6) widget can be used to input a filename.  The user
     can type in the filename manually.  Alternatively, the user can
     press the button widget that sits next to the entry, which will
     bring up a file selection dialog.

   ---------- Footnotes ----------

   (1) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixDirList.htm

   (2) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixDirTree.htm

   (3) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixDirSelectDialog.htm

   (4) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixExFileSelectBox.htm

   (5) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixFileSelectBox.htm

   (6) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixFileEntry.htm


File: python.info,  Node: Hierarchical ListBox,  Next: Tabular ListBox,  Prev: File Selectors,  Up: Tix Widgets

5.25.3.5 Hierarchical ListBox
.............................

 -- 類別: tkinter.tix.HList

     The HList(1) widget can be used to display any data that have a
     hierarchical structure, for example, file system directory trees.
     The list entries are indented and connected by branch lines
     according to their places in the hierarchy.

 -- 類別: tkinter.tix.CheckList

     The CheckList(2) widget displays a list of items to be selected by
     the user.  CheckList acts similarly to the Tk checkbutton or
     radiobutton widgets, except it is capable of handling many more
     items than checkbuttons or radiobuttons.

 -- 類別: tkinter.tix.Tree

     The Tree(3) widget can be used to display hierarchical data in a
     tree form.  The user can adjust the view of the tree by opening or
     closing parts of the tree.

   ---------- Footnotes ----------

   (1) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixHList.htm

   (2) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixCheckList.htm

   (3) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixTree.htm


File: python.info,  Node: Tabular ListBox,  Next: Manager Widgets,  Prev: Hierarchical ListBox,  Up: Tix Widgets

5.25.3.6 Tabular ListBox
........................

 -- 類別: tkinter.tix.TList

     The TList(1) widget can be used to display data in a tabular
     format.  The list entries of a *note TList: 3222. widget are
     similar to the entries in the Tk listbox widget.  The main
     differences are (1) the *note TList: 3222. widget can display the
     list entries in a two dimensional format and (2) you can use
     graphical images as well as multiple colors and fonts for the list
     entries.

   ---------- Footnotes ----------

   (1) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixTList.htm


File: python.info,  Node: Manager Widgets,  Next: Image Types,  Prev: Tabular ListBox,  Up: Tix Widgets

5.25.3.7 Manager Widgets
........................

 -- 類別: tkinter.tix.PanedWindow

     The PanedWindow(1) widget allows the user to interactively
     manipulate the sizes of several panes.  The panes can be arranged
     either vertically or horizontally.  The user changes the sizes of
     the panes by dragging the resize handle between two panes.

 -- 類別: tkinter.tix.ListNoteBook

     The ListNoteBook(2) widget is very similar to the ‘TixNoteBook’
     widget: it can be used to display many windows in a limited space
     using a notebook metaphor.  The notebook is divided into a stack of
     pages (windows).  At one time only one of these pages can be shown.
     The user can navigate through these pages by choosing the name of
     the desired page in the ‘hlist’ subwidget.

 -- 類別: tkinter.tix.NoteBook

     The NoteBook(3) widget can be used to display many windows in a
     limited space using a notebook metaphor.  The notebook is divided
     into a stack of pages.  At one time only one of these pages can be
     shown.  The user can navigate through these pages by choosing the
     visual "tabs" at the top of the NoteBook widget.

   ---------- Footnotes ----------

   (1) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixPanedWindow.htm

   (2) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixListNoteBook.htm

   (3) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixNoteBook.htm


File: python.info,  Node: Image Types,  Next: Miscellaneous Widgets,  Prev: Manager Widgets,  Up: Tix Widgets

5.25.3.8 Image Types
....................

The *note tkinter.tix: 10f. module adds:

   * pixmap(1) capabilities to all *note tkinter.tix: 10f. and *note
     tkinter: 10d. widgets to create color images from XPM files.

   * Compound(2) image types can be used to create images that consists
     of multiple horizontal lines; each line is composed of a series of
     items (texts, bitmaps, images or spaces) arranged from left to
     right.  For example, a compound image can be used to display a
     bitmap and a text string simultaneously in a Tk ‘Button’ widget.

   ---------- Footnotes ----------

   (1) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/pixmap.htm

   (2) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/compound.htm


File: python.info,  Node: Miscellaneous Widgets,  Next: Form Geometry Manager,  Prev: Image Types,  Up: Tix Widgets

5.25.3.9 Miscellaneous Widgets
..............................

 -- 類別: tkinter.tix.InputOnly

     The InputOnly(1) widgets are to accept inputs from the user, which
     can be done with the ‘bind’ command (Unix only).

   ---------- Footnotes ----------

   (1) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixInputOnly.htm


File: python.info,  Node: Form Geometry Manager,  Prev: Miscellaneous Widgets,  Up: Tix Widgets

5.25.3.10 Form Geometry Manager
...............................

In addition, *note tkinter.tix: 10f. augments *note tkinter: 10d. by
providing:

 -- 類別: tkinter.tix.Form

     The Form(1) geometry manager based on attachment rules for all Tk
     widgets.

   ---------- Footnotes ----------

   (1) 
http://tix.sourceforge.net/dist/current/man/html/TixCmd/tixForm.htm


File: python.info,  Node: Tix Commands,  Prev: Tix Widgets,  Up: tkinter tix --- Extension widgets for Tk

5.25.3.11 Tix Commands
......................

 -- 類別: tkinter.tix.tixCommand

     The tix commands(1) provide access to miscellaneous elements of
     ‘Tix’’s internal state and the ‘Tix’ application context.  Most of
     the information manipulated by these methods pertains to the
     application as a whole, or to a screen or display, rather than to a
     particular window.

     To view the current settings, the common usage is:

          from tkinter import tix
          root = tix.Tk()
          print(root.tix_configure())

 -- 成員函式: tixCommand.tix_configure (cnf=None, **kw)

     Query or modify the configuration options of the Tix application
     context.  If no option is specified, returns a dictionary all of
     the available options.  If option is specified with no value, then
     the method returns a list describing the one named option (this
     list will be identical to the corresponding sublist of the value
     returned if no option is specified).  If one or more option-value
     pairs are specified, then the method modifies the given option(s)
     to have the given value(s); in this case the method returns an
     empty string.  Option may be any of the configuration options.

 -- 成員函式: tixCommand.tix_cget (option)

     Returns the current value of the configuration option given by
     `option'.  Option may be any of the configuration options.

 -- 成員函式: tixCommand.tix_getbitmap (name)

     Locates a bitmap file of the name ‘name.xpm’ or ‘name’ in one of
     the bitmap directories (see the *note tix_addbitmapdir(): 322f.
     method).  By using *note tix_getbitmap(): 322e, you can avoid hard
     coding the pathnames of the bitmap files in your application.  When
     successful, it returns the complete pathname of the bitmap file,
     prefixed with the character ‘@’.  The returned value can be used to
     configure the ‘bitmap’ option of the Tk and Tix widgets.

 -- 成員函式: tixCommand.tix_addbitmapdir (directory)

     Tix maintains a list of directories under which the *note
     tix_getimage(): 3230. and *note tix_getbitmap(): 322e. methods will
     search for image files.  The standard bitmap directory is
     ‘$TIX_LIBRARY/bitmaps’.  The *note tix_addbitmapdir(): 322f. method
     adds `directory' into this list.  By using this method, the image
     files of an applications can also be located using the *note
     tix_getimage(): 3230. or *note tix_getbitmap(): 322e. method.

 -- 成員函式: tixCommand.tix_filedialog ([dlgclass])

     Returns the file selection dialog that may be shared among
     different calls from this application.  This method will create a
     file selection dialog widget when it is called the first time.
     This dialog will be returned by all subsequent calls to *note
     tix_filedialog(): 3231.  An optional dlgclass parameter can be
     passed as a string to specified what type of file selection dialog
     widget is desired.  Possible options are ‘tix’, ‘FileSelectDialog’
     or ‘tixExFileSelectDialog’.

 -- 成員函式: tixCommand.tix_getimage (self, name)

     Locates an image file of the name ‘name.xpm’, ‘name.xbm’ or
     ‘name.ppm’ in one of the bitmap directories (see the *note
     tix_addbitmapdir(): 322f. method above).  If more than one file
     with the same name (but different extensions) exist, then the image
     type is chosen according to the depth of the X display: xbm images
     are chosen on monochrome displays and color images are chosen on
     color displays.  By using *note tix_getimage(): 3230, you can avoid
     hard coding the pathnames of the image files in your application.
     When successful, this method returns the name of the newly created
     image, which can be used to configure the ‘image’ option of the Tk
     and Tix widgets.

 -- 成員函式: tixCommand.tix_option_get (name)

     Gets the options maintained by the Tix scheme mechanism.

 -- 成員函式: tixCommand.tix_resetoptions (newScheme, newFontSet[,
          newScmPrio])

     Resets the scheme and fontset of the Tix application to `newScheme'
     and `newFontSet', respectively.  This affects only those widgets
     created after this call.  Therefore, it is best to call the
     resetoptions method before the creation of any widgets in a Tix
     application.

     The optional parameter `newScmPrio' can be given to reset the
     priority level of the Tk options set by the Tix schemes.

     Because of the way Tk handles the X option database, after Tix has
     been has imported and inited, it is not possible to reset the color
     schemes and font sets using the ‘tix_config()’ method.  Instead,
     the *note tix_resetoptions(): 3233. method must be used.

   ---------- Footnotes ----------

   (1) http://tix.sourceforge.net/dist/current/man/html/TixCmd/tix.htm


File: python.info,  Node: tkinter scrolledtext --- Scrolled Text Widget,  Next: IDLE<54>,  Prev: tkinter tix --- Extension widgets for Tk,  Up: 以 Tk 打造 GUI

5.25.4 ‘tkinter.scrolledtext’ — Scrolled Text Widget
----------------------------------------------------

`Source code:' Lib/tkinter/scrolledtext.py(1)

__________________________________________________________________

The *note tkinter.scrolledtext: 10e. 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 ‘ScrolledText’ class
is a lot easier than setting up a text widget and scroll bar directly.
The constructor is the same as that of the ‘tkinter.Text’ class.

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 ‘ScrolledText’ widget to be used
directly to achieve most normal geometry management behavior.

Should more specific control be necessary, the following attributes are
available:

 -- 屬性: ScrolledText.frame

     The frame which surrounds the text and scroll bar widgets.

 -- 屬性: ScrolledText.vbar

     The scroll bar widget.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/tkinter/scrolledtext.py


File: python.info,  Node: IDLE<54>,  Next: 其它的 GUI,  Prev: tkinter scrolledtext --- Scrolled Text Widget,  Up: 以 Tk 打造 GUI

5.25.5 IDLE
-----------

`Source code:' Lib/idlelib/(1)

__________________________________________________________________

IDLE is Python’s Integrated Development and Learning Environment.

IDLE has the following features:

   * coded in 100% pure Python, using the *note tkinter: 10d. GUI
     toolkit

   * 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:

* Menus::
* Editing and navigation::
* Startup and code execution::
* Help and preferences::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/idlelib/


File: python.info,  Node: Menus,  Next: Editing and navigation,  Up: IDLE<54>

5.25.5.1 Menus
..............

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: Menus

5.25.5.2 File menu (Shell and Editor)
.....................................

New File

     Create a new file editing window.

Open...

     Open an existing file with an Open dialog.

Recent Files

     Open a list of recent files.  Click one to open it.

Open Module...

     Open an existing module (searches sys.path).

Class 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.

Save Copy As...

     Save the current window to different file without changing the
     associated file.

Print Window

     Print the current window to the default printer.

Close

     Close the current window (ask to save if unsaved).

Exit

     Close all windows and quit IDLE (ask to save unsaved windows).


File: python.info,  Node: Edit menu Shell and Editor,  Next: Format menu Editor window only,  Prev: File menu Shell and Editor,  Up: Menus

5.25.5.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.

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.

Select All

     Select the entire contents of the current window.

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: 323d. 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: 323e. 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: Menus

5.25.5.4 Format menu (Editor window only)
.........................................

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.

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.

Strip trailing whitespace

     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: Menus

5.25.5.5 Run menu (Editor window only)
......................................

Run Module

     Do *note Check Module: 3243.  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: 3242, but run the module with customized
     settings.  `Command Line Arguments' extend *note sys.argv: c00. 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: Menus

5.25.5.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: Menus

5.25.5.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: Menus

5.25.5.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: 3249. 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: 324a. 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: 3249.).

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: Menus

5.25.5.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: Menus

5.25.5.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: 324d. subsection
below for more on Help menu choices.


File: python.info,  Node: Context Menus,  Prev: Help menu Shell and Editor,  Up: Menus

5.25.5.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: Menus,  Up: IDLE<54>

5.25.5.12 Editing and navigation
................................

* Menu:

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


File: python.info,  Node: Editor windows,  Next: Key bindings,  Up: Editing and navigation

5.25.5.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.5.14 Key bindings
......................

In this section, ’C’ refers to the ‘Control’ key on Windows and Unix and
the ‘Command’ key on macOS.

   * ‘Backspace’ deletes to the left; ‘Del’ deletes to the right

   * ‘C-Backspace’ delete word left; ‘C-Del’ delete word to the right

   * Arrow keys and ‘Page Up’/‘Page Down’ to move around

   * ‘C-LeftArrow’ and ‘C-RightArrow’ moves by words

   * ‘Home’/‘End’ go to begin/end of line

   * ‘C-Home’/‘C-End’ go to begin/end of file

   * Some useful Emacs bindings are inherited from Tcl/Tk:

             * ‘C-a’ beginning of line

             * ‘C-e’ end of line

             * ‘C-k’ kill line (but doesn’t put it in clipboard)

             * ‘C-l’ center window around the insertion point

             * ‘C-b’ go backward one character without deleting (usually
               you can also use the cursor key for this)

             * ‘C-f’ go forward one character without deleting (usually
               you can also use the cursor key for this)

             * ‘C-p’ go up one line (usually you can also use the cursor
               key for this)

             * ‘C-d’ delete next character

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: Completions,  Prev: Key bindings,  Up: Editing and navigation

5.25.5.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:
323f.


File: python.info,  Node: Completions,  Next: Calltips,  Prev: Automatic indentation,  Up: Editing and navigation

5.25.5.16 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: 1c7d. or *note os.altsep: 1c7e.
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 intially 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.5.17 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: Python Shell window,  Prev: Calltips,  Up: Editing and navigation

5.25.5.18 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: Python Shell window,  Next: Text colors,  Prev: Code Context,  Up: Editing and navigation

5.25.5.19 Python Shell window
.............................

With IDLE’s Shell, one enters, edits, and recalls complete statements.
Most consoles and terminals only work with a single physical line at a
time.

When one pastes code into Shell, it is not compiled and possibly
executed until one hits ‘Return’.  One may edit pasted code first.  If
one pastes more that one statement into Shell, the result will be a
*note SyntaxError: 45d. when multiple statements are compiled as if they
were one.

The editing features described in previous subsections work when
entering code interactively.  IDLE’s Shell window also responds to the
following keys.

   * ‘C-c’ interrupts executing command

   * ‘C-d’ sends end-of-file; closes window if typed at a ‘>>>’ prompt

   * ‘Alt-/’ (Expand word) is also useful to reduce typing

     Command history

        * ‘Alt-p’ retrieves previous command matching what you have
          typed.  On macOS use ‘C-p’.

        * ‘Alt-n’ retrieves next.  On macOS use ‘C-n’.

        * ‘Return’ while on any previous command retrieves that command


File: python.info,  Node: Text colors,  Prev: Python Shell window,  Up: Editing and navigation

5.25.5.20 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.

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<54>

5.25.5.21 Startup and code execution
....................................

Upon startup with the ‘-s’ option, IDLE will execute the file referenced
by the environment variables ‘IDLESTARTUP’ or *note PYTHONSTARTUP: 8ea.
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:

* Command line usage::
* Startup failure::
* Running user code::
* User output in Shell::
* Developing tkinter applications::
* Running without a subprocess::


File: python.info,  Node: Command line usage,  Next: Startup failure,  Up: Startup and code execution

5.25.5.22 Command line usage
............................

     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: Command line usage,  Up: Startup and code execution

5.25.5.23 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.5.24 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(): 1637. 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.  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.5.25 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.5.26 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.5.27 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,  Prev: Startup and code execution,  Up: IDLE<54>

5.25.5.28 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.5.29 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.5.30 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.5.31 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.5.32 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: 其它的 GUI,  Prev: IDLE<54>,  Up: 以 Tk 打造 GUI

5.25.6 其它的 GUI
-----------------

Major cross-platform (Windows, Mac OS X, Unix-like) GUI toolkits are
available for Python:

也參考
......

PyGObject(1)

     PyGObject provides introspection bindings for C libraries using
     GObject(2).  One of these libraries is the GTK+ 3(3) widget set.
     GTK+ comes with many more widgets than Tkinter provides.  An online
     Python GTK+ 3 Tutorial(4) is available.

PyGTK(5)

     PyGTK provides bindings for an older version of the library, GTK+
     2.  It provides an object oriented interface that is slightly
     higher level than the C one.  There are also bindings to GNOME(6).
     An online tutorial(7) is available.

PyQt(8)

     PyQt is a ‘sip’-wrapped binding to the Qt toolkit.  Qt is an
     extensive C++ GUI application development framework that is
     available for Unix, Windows and Mac OS X. ‘sip’ is a tool for
     generating bindings for C++ libraries as Python classes, and is
     specifically designed for Python.

PySide2(9)

     Also known as the Qt for Python project, PySide2 is a newer binding
     to the Qt toolkit.  It is provided by The Qt Company and aims to
     provide a complete port of PySide to Qt 5.  Compared to PyQt, its
     licensing scheme is friendlier to non-open source applications.

wxPython(10)

     wxPython is a cross-platform GUI toolkit for Python that is built
     around the popular wxWidgets(11) (formerly wxWindows) C++ toolkit.
     It provides a native look and feel for applications on Windows, Mac
     OS X, and Unix systems by using each platform’s native widgets
     where ever possible, (GTK+ on Unix-like systems).  In addition to
     an extensive set of widgets, wxPython provides classes for online
     documentation and context sensitive help, printing, HTML viewing,
     low-level device context drawing, drag and drop, system clipboard
     access, an XML-based resource format and more, including an ever
     growing library of user-contributed modules.

PyGTK, PyQt, PySide2, and wxPython, all have a modern look and feel and
more widgets than Tkinter.  In addition, there are many other GUI
toolkits for Python, both cross-platform, and platform-specific.  See
the GUI Programming(12) page in the Python Wiki for a much more complete
list, and also for links to documents where the different GUI toolkits
are compared.

   ---------- Footnotes ----------

   (1) https://wiki.gnome.org/Projects/PyGObject

   (2) https://developer.gnome.org/gobject/stable/

   (3) https://www.gtk.org/

   (4) https://python-gtk-3-tutorial.readthedocs.io/

   (5) http://www.pygtk.org/

   (6) https://www.gnome.org/

   (7) http://www.pygtk.org/pygtk2tutorial/index.html

   (8) https://riverbankcomputing.com/software/pyqt/intro

   (9) https://doc.qt.io/qtforpython/

   (10) https://www.wxpython.org

   (11) https://www.wxwidgets.org/

   (12) https://wiki.python.org/moin/GuiProgramming


File: python.info,  Node: 開發工具,  Next: Debugging and Profiling,  Prev: 以 Tk 打造 GUI,  Up: Python 標準函式庫 Standard Library

5.26 開發工具
=============

The modules described in this chapter help you write software.  For
example, the *note pydoc: da. module takes a module and generates
documentation based on the module’s contents.  The *note doctest: 67.
and *note unittest: 11c. modules contains frameworks for writing unit
tests that automatically exercise code and verify that the expected
output is produced.  ‘2to3’ can translate Python 2.x source code into
valid Python 3.x code.

The list of modules described in this chapter is:

* Menu:

* typing: typing --- Support for type hints. Support for type hints
* pydoc: pydoc --- Documentation generator and online help system. Documentation generator and online help system
* doctest: doctest --- Test interactive Python examples. Test interactive Python examples
* unittest: unittest --- 單元測試框架. 單元測試框架
* unittest.mock: unittest mock --- mock object library. mock object library
* unittest.mock: unittest mock --- getting started. getting started
* 2to3 - 自動將 Python 2的程式碼轉成 Python 3::
* test: test --- Regression tests package for Python. Regression tests package for Python
* test.support: test support --- Utilities for the Python test suite. Utilities for the Python test suite
* test.support.script_helper: test support script_helper --- Utilities for the Python execution tests. Utilities for the Python execution tests


File: python.info,  Node: typing --- Support for type hints,  Next: pydoc --- Documentation generator and online help system,  Up: 開發工具

5.26.1 ‘typing’ — Support for type hints
----------------------------------------

3.5 版新加入.

`Source code:' Lib/typing.py(1)

     備註: The Python runtime does not enforce function and variable
     type annotations.  They can be used by third party tools such as
     type checkers, IDEs, linters, etc.

__________________________________________________________________

This module provides runtime support for type hints as specified by PEP
484(2), PEP 526(3), PEP 544(4), PEP 586(5), PEP 589(6), and PEP 591(7).
The most fundamental support consists of the types *note Any: 657, *note
Union: 1039, *note Tuple: 326c, *note Callable: 326d, *note TypeVar:
f26, and *note Generic: 326e.  For full specification please see PEP
484(8).  For a simplified introduction to type hints see PEP 483(9).

The function below takes and returns a string and is annotated as
follows:

     def greeting(name: str) -> str:
         return 'Hello ' + name

In the function ‘greeting’, the argument ‘name’ is expected to be of
type *note str: 335. and the return type *note str: 335.  Subtypes are
accepted as arguments.

* Menu:

* Type aliases::
* NewType::
* Callable::
* Generics::
* User-defined generic types::
* The Any type::
* Nominal vs structural subtyping::
* Classes, functions, and decorators: Classes functions and decorators.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/typing.py

   (2) https://www.python.org/dev/peps/pep-0484

   (3) https://www.python.org/dev/peps/pep-0526

   (4) https://www.python.org/dev/peps/pep-0544

   (5) https://www.python.org/dev/peps/pep-0586

   (6) https://www.python.org/dev/peps/pep-0589

   (7) https://www.python.org/dev/peps/pep-0591

   (8) https://www.python.org/dev/peps/pep-0484

   (9) https://www.python.org/dev/peps/pep-0483


File: python.info,  Node: Type aliases,  Next: NewType,  Up: typing --- Support for type hints

5.26.1.1 Type aliases
.....................

A type alias is defined by assigning the type to the alias.  In this
example, ‘Vector’ and ‘List[float]’ will be treated as interchangeable
synonyms:

     from typing import List
     Vector = List[float]

     def scale(scalar: float, vector: Vector) -> Vector:
         return [scalar * num for num in vector]

     # typechecks; a list of floats qualifies as a Vector.
     new_vector = scale(2.0, [1.0, -4.2, 5.4])

Type aliases are useful for simplifying complex type signatures.  For
example:

     from typing import Dict, Tuple, Sequence

     ConnectionOptions = Dict[str, str]
     Address = Tuple[str, int]
     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 that ‘None’ as a type hint is a special case and is replaced by
‘type(None)’.


File: python.info,  Node: NewType,  Next: Callable,  Prev: Type aliases,  Up: typing --- Support for type hints

5.26.1.2 NewType
................

Use the *note NewType(): 5aa. helper function to create distinct types:

     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.  This is useful in helping catch logical errors:

     def get_user_name(user_id: UserId) -> str:
         ...

     # typechecks
     user_a = get_user_name(UserId(42351))

     # does not typecheck; an int is not a UserId
     user_b = get_user_name(-1)

You may still perform all ‘int’ operations on a variable of type
‘UserId’, but the result will always be of type ‘int’.  This lets you
pass in a ‘UserId’ wherever an ‘int’ might be expected, but will prevent
you from accidentally creating a ‘UserId’ in an invalid way:

     # 'output' is of type 'int', not 'UserId'
     output = UserId(23413) + UserId(54341)

Note that these checks are enforced only by the static type checker.  At
runtime, the statement ‘Derived = NewType('Derived', Base)’ will make
‘Derived’ a function that immediately returns whatever parameter you
pass it.  That means the expression ‘Derived(some_value)’ does not
create a new class or introduce any overhead beyond that of a regular
function call.

More precisely, the expression ‘some_value is Derived(some_value)’ is
always true at runtime.

This also means that it is not possible to create a subtype of ‘Derived’
since it is an identity function at runtime, not an actual type:

     from typing import NewType

     UserId = NewType('UserId', int)

     # Fails at runtime and does not typecheck
     class AdminUserId(UserId): pass

However, it is possible to create a *note NewType(): 5aa. based on a
’derived’ ‘NewType’:

     from typing import NewType

     UserId = NewType('UserId', int)

     ProUserId = NewType('ProUserId', UserId)

and typechecking for ‘ProUserId’ will work as expected.

See PEP 484(1) for more details.

     備註: Recall that the use of a type alias declares two types to be
     `equivalent' to one another.  Doing ‘Alias = Original’ will make
     the static type checker treat ‘Alias’ as being `exactly equivalent'
     to ‘Original’ in all cases.  This is useful when you want to
     simplify complex type signatures.

     In contrast, ‘NewType’ declares one type to be a `subtype' of
     another.  Doing ‘Derived = NewType('Derived', Original)’ will make
     the static type checker treat ‘Derived’ as a `subclass' of
     ‘Original’, which means a value of type ‘Original’ cannot be used
     in places where a value of type ‘Derived’ is expected.  This is
     useful when you want to prevent logic errors with minimal runtime
     cost.

3.5.2 版新加入.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0484


File: python.info,  Node: Callable,  Next: Generics,  Prev: NewType,  Up: typing --- Support for type hints

5.26.1.3 Callable
.................

Frameworks expecting callback functions of specific signatures might be
type hinted using ‘Callable[[Arg1Type, Arg2Type], ReturnType]’.

For example:

     from typing import Callable

     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

It is possible to declare the return type of a callable without
specifying the call signature by substituting a literal ellipsis for the
list of arguments in the type hint: ‘Callable[..., ReturnType]’.


File: python.info,  Node: Generics,  Next: User-defined generic types,  Prev: Callable,  Up: typing --- Support for type hints

5.26.1.4 Generics
.................

Since type information about objects kept in containers cannot be
statically inferred in a generic way, abstract base classes have been
extended to support subscription to denote expected types for container
elements.

     from typing import Mapping, Sequence

     def notify_by_email(employees: Sequence[Employee],
                         overrides: Mapping[str, str]) -> None: ...

Generics can be parameterized by using a new factory available in typing
called *note TypeVar: f26.

     from typing import Sequence, TypeVar

     T = TypeVar('T')      # Declare type variable

     def first(l: Sequence[T]) -> T:   # Generic function
         return l[0]


File: python.info,  Node: User-defined generic types,  Next: The Any type,  Prev: Generics,  Up: typing --- Support for type hints

5.26.1.5 User-defined generic types
...................................

A user-defined class can be defined as a generic class.

     from typing import TypeVar, Generic
     from logging import Logger

     T = TypeVar('T')

     class LoggedVar(Generic[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)

‘Generic[T]’ as a base class defines that the class ‘LoggedVar’ takes a
single type parameter ‘T’ .  This also makes ‘T’ valid as a type within
the class body.

The *note Generic: 326e. base class defines *note __class_getitem__():
32c. so that ‘LoggedVar[t]’ is valid as a type:

     from typing import Iterable

     def zero_all_vars(vars: Iterable[LoggedVar[int]]) -> None:
         for var in vars:
             var.set(0)

A generic type can have any number of type variables, and type variables
may be constrained:

     from typing import TypeVar, Generic
     ...

     T = TypeVar('T')
     S = TypeVar('S', int, str)

     class StrangePair(Generic[T, S]):
         ...

Each type variable argument to *note Generic: 326e. must be distinct.
This is thus invalid:

     from typing import TypeVar, Generic
     ...

     T = TypeVar('T')

     class Pair(Generic[T, T]):   # INVALID
         ...

You can use multiple inheritance with *note Generic: 326e.:

     from typing import TypeVar, Generic, Sized

     T = TypeVar('T')

     class LinkedList(Sized, Generic[T]):
         ...

When inheriting from generic classes, some type variables could be
fixed:

     from typing import TypeVar, Mapping

     T = TypeVar('T')

     class MyDict(Mapping[str, T]):
         ...

In this case ‘MyDict’ has a single parameter, ‘T’.

Using a generic class without specifying type parameters assumes *note
Any: 657. for each position.  In the following example, ‘MyIterable’ is
not generic but implicitly inherits from ‘Iterable[Any]’:

     from typing import Iterable

     class MyIterable(Iterable): # Same as Iterable[Any]

User defined generic type aliases are also supported.  Examples:

     from typing import TypeVar, Iterable, Tuple, Union
     S = TypeVar('S')
     Response = Union[Iterable[S], int]

     # Return type here is same as Union[Iterable[str], int]
     def response(query: str) -> Response[str]:
         ...

     T = TypeVar('T', int, float, complex)
     Vec = Iterable[Tuple[T, T]]

     def inproduct(v: Vec[T]) -> T: # Same as Iterable[Tuple[T, T]]
         return sum(x*y for x, y in v)

3.7 版更變: *note Generic: 326e. no longer has a custom metaclass.

A user-defined generic class can have ABCs as base classes without a
metaclass conflict.  Generic metaclasses are not supported.  The outcome
of parameterizing generics is cached, and most types in the typing
module are hashable and comparable for equality.


File: python.info,  Node: The Any type,  Next: Nominal vs structural subtyping,  Prev: User-defined generic types,  Up: typing --- Support for type hints

5.26.1.6 The ‘Any’ type
.......................

A special kind of type is *note Any: 657.  A static type checker will
treat every type as being compatible with *note Any: 657. and *note Any:
657. as being compatible with every type.

This means that it is possible to perform any operation or method call
on a value of type *note Any: 657. and assign it to any variable:

     from typing import Any

     a = None    # type: Any
     a = []      # OK
     a = 2       # OK

     s = ''      # type: str
     s = a       # OK

     def foo(item: Any) -> int:
         # Typechecks; 'item' could be any type,
         # and that type might have a 'bar' method
         item.bar()
         ...

Notice that no typechecking is performed when assigning a value of type
*note Any: 657. to a more precise type.  For example, the static type
checker did not report an error when assigning ‘a’ to ‘s’ even though
‘s’ was declared to be of type *note str: 335. and receives an *note
int: 185. value at runtime!

Furthermore, all functions without a return type or parameter types will
implicitly default to using *note Any: 657.:

     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

This behavior allows *note Any: 657. to be used as an `escape hatch'
when you need to mix dynamically and statically typed code.

Contrast the behavior of *note Any: 657. with the behavior of *note
object: 2b1.  Similar to *note Any: 657, every type is a subtype of
*note object: 2b1.  However, unlike *note Any: 657, the reverse is not
true: *note object: 2b1. is `not' a subtype of every other type.

That means when the type of a value is *note object: 2b1, a type checker
will reject almost all operations on it, and assigning it to a variable
(or using it as a return value) of a more specialized type is a type
error.  For example:

     def hash_a(item: object) -> int:
         # Fails; an object does not have a 'magic' method.
         item.magic()
         ...

     def hash_b(item: Any) -> int:
         # Typechecks
         item.magic()
         ...

     # Typechecks, since ints and strs are subclasses of object
     hash_a(42)
     hash_a("foo")

     # Typechecks, since Any is compatible with all types
     hash_b(42)
     hash_b("foo")

Use *note object: 2b1. to indicate that a value could be any type in a
typesafe manner.  Use *note Any: 657. to indicate that a value is
dynamically typed.


File: python.info,  Node: Nominal vs structural subtyping,  Next: Classes functions and decorators,  Prev: The Any type,  Up: typing --- Support for type hints

5.26.1.7 Nominal vs structural subtyping
........................................

Initially PEP 484(1) defined Python static type system as using `nominal
subtyping'.  This means that a class ‘A’ is allowed where a class ‘B’ is
expected if and only if ‘A’ is a subclass of ‘B’.

This requirement previously also applied to abstract base classes, such
as *note Iterable: 1957.  The problem with this approach is that a class
had to be explicitly marked to support them, which is unpythonic and
unlike what one would normally do in idiomatic dynamically typed Python
code.  For example, this conforms to PEP 484(2):

     from typing import Sized, Iterable, Iterator

     class Bucket(Sized, Iterable[int]):
         ...
         def __len__(self) -> int: ...
         def __iter__(self) -> Iterator[int]: ...

PEP 544(3) allows to solve this problem by allowing users to write the
above code without explicit base classes in the class definition,
allowing ‘Bucket’ to be implicitly considered a subtype of both ‘Sized’
and ‘Iterable[int]’ by static type checkers.  This is known as
`structural subtyping' (or static duck-typing):

     from typing 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

Moreover, by subclassing a special class *note Protocol: 240, a user can
define new custom protocols to fully enjoy structural subtyping (see
examples below).

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0484

   (2) https://www.python.org/dev/peps/pep-0484

   (3) https://www.python.org/dev/peps/pep-0544


File: python.info,  Node: Classes functions and decorators,  Prev: Nominal vs structural subtyping,  Up: typing --- Support for type hints

5.26.1.8 Classes, functions, and decorators
...........................................

The module defines the following classes, functions and decorators:

 -- 類別: typing.TypeVar

     Type variable.

     Usage:

          T = TypeVar('T')  # Can be anything
          A = TypeVar('A', str, bytes)  # Must be 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 definitions.  See class Generic for more
     information on generic types.  Generic functions work as follows:

          def repeat(x: T, n: int) -> Sequence[T]:
              """Return a list containing n references to x."""
              return [x]*n

          def longest(x: A, y: A) -> A:
              """Return the longest of two strings."""
              return x if len(x) >= len(y) else y

     The latter example’s signature is essentially the overloading of
     ‘(str, str) -> str’ and ‘(bytes, bytes) -> bytes’.  Also note that
     if the arguments are instances of some subclass of *note str: 335,
     the return type is still plain *note str: 335.

     At runtime, ‘isinstance(x, T)’ will raise *note TypeError: 193.  In
     general, *note isinstance(): 454. and *note issubclass(): 455.
     should not be used with types.

     Type variables may be marked covariant or contravariant by passing
     ‘covariant=True’ or ‘contravariant=True’.  See PEP 484(1) for more
     details.  By default type variables are invariant.  Alternatively,
     a type variable may specify an upper bound using ‘bound=<type>’.
     This means that an actual type substituted (explicitly or
     implicitly) for the type variable must be a subclass of the
     boundary type, see PEP 484(2).

 -- 類別: typing.Generic

     Abstract base class for generic types.

     A generic type is typically declared by inheriting from an
     instantiation of this class with one or more type variables.  For
     example, a generic mapping type might be defined as:

          class Mapping(Generic[KT, VT]):
              def __getitem__(self, key: KT) -> VT:
                  ...
                  # Etc.

     This class can then be used as follows:

          X = TypeVar('X')
          Y = TypeVar('Y')

          def lookup_name(mapping: Mapping[X, Y], key: X, default: Y) -> Y:
              try:
                  return mapping[key]
              except KeyError:
                  return default

 -- 類別: 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(3) for details.  Protocol classes decorated with *note
     runtime_checkable(): 241. (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(Protocol[T]):
              def meth(self) -> T:
                  ...

     3.8 版新加入.

 -- 類別: typing.Type (Generic[CT_co])

     A variable annotated with ‘C’ may accept a value of type ‘C’.  In
     contrast, a variable annotated with ‘Type[C]’ may accept values
     that are classes themselves – specifically, it will accept the
     `class object' of ‘C’.  For example:

          a = 3         # Has type 'int'
          b = int       # Has type 'Type[int]'
          c = type(a)   # Also has type 'Type[int]'

     Note that ‘Type[C]’ is covariant:

          class User: ...
          class BasicUser(User): ...
          class ProUser(User): ...
          class TeamUser(User): ...

          # Accepts User, BasicUser, ProUser, TeamUser, ...
          def make_new_user(user_class: Type[User]) -> User:
              # ...
              return user_class()

     The fact that ‘Type[C]’ is covariant implies that all subclasses of
     ‘C’ should implement the same constructor signature and class
     method signatures as ‘C’.  The type checker should flag violations
     of this, but should also allow constructor calls in subclasses that
     match the constructor calls in the indicated base class.  How the
     type checker is required to handle this particular case may change
     in future revisions of PEP 484(4).

     The only legal parameters for *note Type: 3279. are classes, *note
     Any: 657, *note type variables: 3273, and unions of any of these
     types.  For example:

          def new_non_team_user(user_class: Type[Union[BasicUser, ProUser]]): ...

     ‘Type[Any]’ is equivalent to ‘Type’ which in turn is equivalent to
     ‘type’, which is the root of Python’s metaclass hierarchy.

     3.5.2 版新加入.

 -- 類別: typing.Iterable (Generic[T_co])

     A generic version of *note collections.abc.Iterable: 1957.

 -- 類別: typing.Iterator (Iterable[T_co])

     A generic version of *note collections.abc.Iterator: 1958.

 -- 類別: typing.Reversible (Iterable[T_co])

     A generic version of *note collections.abc.Reversible: 533.

 -- 類別: typing.SupportsInt

     An ABC with one abstract method ‘__int__’.

 -- 類別: typing.SupportsFloat

     An ABC with one abstract method ‘__float__’.

 -- 類別: typing.SupportsComplex

     An ABC with one abstract method ‘__complex__’.

 -- 類別: typing.SupportsBytes

     An ABC with one abstract method ‘__bytes__’.

 -- 類別: typing.SupportsIndex

     An ABC with one abstract method ‘__index__’.

     3.8 版新加入.

 -- 類別: typing.SupportsAbs

     An ABC with one abstract method ‘__abs__’ that is covariant in its
     return type.

 -- 類別: typing.SupportsRound

     An ABC with one abstract method ‘__round__’ that is covariant in
     its return type.

 -- 類別: typing.Container (Generic[T_co])

     A generic version of *note collections.abc.Container: 1955.

 -- 類別: typing.Hashable

     An alias to *note collections.abc.Hashable: 1956.

 -- 類別: typing.Sized

     An alias to *note collections.abc.Sized: 1959.

 -- 類別: typing.Collection (Sized, Iterable[T_co], Container[T_co])

     A generic version of *note collections.abc.Collection: 532.

     3.6.0 版新加入.

 -- 類別: typing.AbstractSet (Sized, Collection[T_co])

     A generic version of *note collections.abc.Set: 16df.

 -- 類別: typing.MutableSet (AbstractSet[T])

     A generic version of *note collections.abc.MutableSet: 195c.

 -- 類別: typing.Mapping (Sized, Collection[KT], Generic[VT_co])

     A generic version of *note collections.abc.Mapping: 1949.  This
     type can be used as follows:

          def get_position_in_index(word_list: Mapping[str, int], word: str) -> int:
              return word_list[word]

 -- 類別: typing.MutableMapping (Mapping[KT, VT])

     A generic version of *note collections.abc.MutableMapping: 9f4.

 -- 類別: typing.Sequence (Reversible[T_co], Collection[T_co])

     A generic version of *note collections.abc.Sequence: 1635.

 -- 類別: typing.MutableSequence (Sequence[T])

     A generic version of *note collections.abc.MutableSequence: 6b1.

 -- 類別: typing.ByteString (Sequence[int])

     A generic version of *note collections.abc.ByteString: 195b.

     This type represents the types *note bytes: 336, *note bytearray:
     337, and *note memoryview: 25d. of byte sequences.

     As a shorthand for this type, *note bytes: 336. can be used to
     annotate arguments of any of the types mentioned above.

 -- 類別: typing.Deque (deque, MutableSequence[T])

     A generic version of *note collections.deque: 536.

     3.5.4 版新加入.

     3.6.1 版新加入.

 -- 類別: typing.List (list, MutableSequence[T])

     Generic version of *note list: 263.  Useful for annotating return
     types.  To annotate arguments it is preferred to use an abstract
     collection type such as *note Sequence: 3289. or *note Iterable:
     327a.

     This type may be used as follows:

          T = TypeVar('T', int, float)

          def vec2(x: T, y: T) -> List[T]:
              return [x, y]

          def keep_positives(vector: Sequence[T]) -> List[T]:
              return [item for item in vector if item > 0]

 -- 類別: typing.Set (set, MutableSet[T])

     A generic version of *note builtins.set: b74.  Useful for
     annotating return types.  To annotate arguments it is preferred to
     use an abstract collection type such as *note AbstractSet: 3285.

 -- 類別: typing.FrozenSet (frozenset, AbstractSet[T_co])

     A generic version of *note builtins.frozenset: bf3.

 -- 類別: typing.MappingView (Sized, Iterable[T_co])

     A generic version of *note collections.abc.MappingView: 195d.

 -- 類別: typing.KeysView (MappingView[KT_co], AbstractSet[KT_co])

     A generic version of *note collections.abc.KeysView: 195f.

 -- 類別: typing.ItemsView (MappingView, Generic[KT_co, VT_co])

     A generic version of *note collections.abc.ItemsView: 195e.

 -- 類別: typing.ValuesView (MappingView[VT_co])

     A generic version of *note collections.abc.ValuesView: 1960.

 -- 類別: typing.Awaitable (Generic[T_co])

     A generic version of *note collections.abc.Awaitable: 6bb.

     3.5.2 版新加入.

 -- 類別: typing.Coroutine (Awaitable[V_co], Generic[T_co, T_contra,
          V_co])

     A generic version of *note collections.abc.Coroutine: 6bc.  The
     variance and order of type variables correspond to those of *note
     Generator: 3295, for example:

          from typing import List, Coroutine
          c = None # type: Coroutine[List[str], str, int]
          ...
          x = c.send('hi') # type: List[str]
          async def bar() -> None:
              x = await c # type: int

     3.5.3 版新加入.

 -- 類別: typing.AsyncIterable (Generic[T_co])

     A generic version of *note collections.abc.AsyncIterable: 6be.

     3.5.2 版新加入.

 -- 類別: typing.AsyncIterator (AsyncIterable[T_co])

     A generic version of *note collections.abc.AsyncIterator: 6bd.

     3.5.2 版新加入.

 -- 類別: typing.ContextManager (Generic[T_co])

     A generic version of *note contextlib.AbstractContextManager: 539.

     3.5.4 版新加入.

     3.6.0 版新加入.

 -- 類別: typing.AsyncContextManager (Generic[T_co])

     A generic version of *note contextlib.AbstractAsyncContextManager:
     37d.

     3.5.4 版新加入.

     3.6.2 版新加入.

 -- 類別: typing.Dict (dict, MutableMapping[KT, VT])

     A generic version of *note dict: 1b9.  Useful for annotating return
     types.  To annotate arguments it is preferred to use an abstract
     collection type such as *note Mapping: 3287.

     This type can be used as follows:

          def count_words(text: str) -> Dict[str, int]:
              ...

 -- 類別: typing.DefaultDict (collections.defaultdict,
          MutableMapping[KT, VT])

     A generic version of *note collections.defaultdict: b3f.

     3.5.2 版新加入.

 -- 類別: typing.OrderedDict (collections.OrderedDict,
          MutableMapping[KT, VT])

     A generic version of *note collections.OrderedDict: 1ba.

     3.7.2 版新加入.

 -- 類別: typing.Counter (collections.Counter, Dict[T, int])

     A generic version of *note collections.Counter: 9df.

     3.5.4 版新加入.

     3.6.1 版新加入.

 -- 類別: typing.ChainMap (collections.ChainMap, MutableMapping[KT, VT])

     A generic version of *note collections.ChainMap: 4ae.

     3.5.4 版新加入.

     3.6.1 版新加入.

 -- 類別: typing.Generator (Iterator[T_co], Generic[T_co, T_contra,
          V_co])

     A generator can be annotated by the generic type
     ‘Generator[YieldType, SendType, ReturnType]’.  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 generics in the typing module, the
     ‘SendType’ of *note Generator: 3295. behaves contravariantly, not
     covariantly or invariantly.

     If your generator will only yield values, set the ‘SendType’ and
     ‘ReturnType’ to ‘None’:

          def infinite_stream(start: int) -> Generator[int, None, None]:
              while True:
                  yield start
                  start += 1

     Alternatively, annotate your generator as having a return type of
     either ‘Iterable[YieldType]’ or ‘Iterator[YieldType]’:

          def infinite_stream(start: int) -> Iterator[int]:
              while True:
                  yield start
                  start += 1

 -- 類別: typing.AsyncGenerator (AsyncIterator[T_co], Generic[T_co,
          T_contra])

     An async generator can be annotated by the generic type
     ‘AsyncGenerator[YieldType, SendType]’.  For example:

          async def echo_round() -> AsyncGenerator[int, float]:
              sent = yield 0
              while sent >= 0.0:
                  rounded = await round(sent)
                  sent = yield rounded

     Unlike normal generators, async generators cannot return a value,
     so there is no ‘ReturnType’ type parameter.  As with *note
     Generator: 3295, the ‘SendType’ behaves contravariantly.

     If your generator will only yield values, set the ‘SendType’ to
     ‘None’:

          async def infinite_stream(start: int) -> AsyncGenerator[int, None]:
              while True:
                  yield start
                  start = await increment(start)

     Alternatively, annotate your generator as having a return type of
     either ‘AsyncIterable[YieldType]’ or ‘AsyncIterator[YieldType]’:

          async def infinite_stream(start: int) -> AsyncIterator[int]:
              while True:
                  yield start
                  start = await increment(start)

     3.6.1 版新加入.

 -- 類別: typing.Text

     ‘Text’ is an alias for ‘str’.  It 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 版新加入.

 -- 類別: 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(): 4f5.

 -- 類別: typing.Pattern
 -- 類別: typing.Match

     These type aliases correspond to the return types from *note
     re.compile(): 44f. and *note re.match(): bb8.  These types (and the
     corresponding functions) are generic in ‘AnyStr’ and can be made
     specific by writing ‘Pattern[str]’, ‘Pattern[bytes]’, ‘Match[str]’,
     or ‘Match[bytes]’.

 -- 類別: typing.NamedTuple

     Typed version of *note collections.namedtuple(): 1b8.

     Usage:

          class Employee(NamedTuple):
              name: str
              id: int

     This is equivalent to:

          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
     namedtuple 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}>'

     Backward-compatible usage:

          Employee = NamedTuple('Employee', [('name', str), ('id', int)])

     3.6 版更變: Added support for PEP 526(5) variable annotation
     syntax.

     3.6.1 版更變: Added support for default values, methods, and
     docstrings.

     Deprecated since version 3.8, will be removed in version 3.9:
     Deprecated the ‘_field_types’ attribute in favor of the more
     standard ‘__annotations__’ attribute which has the same
     information.

     3.8 版更變: The ‘_field_types’ and ‘__annotations__’ attributes are
     now regular dictionaries instead of instances of ‘OrderedDict’.

 -- 類別: typing.TypedDict (dict)

     A simple typed namespace.  At runtime it is equivalent to a plain
     *note dict: 1b9.

     ‘TypedDict’ creates 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')

     The type info for introspection can be accessed via
     ‘Point2D.__annotations__’ and ‘Point2D.__total__’.  To allow using
     this feature with older versions of Python that do not support PEP
     526(6), ‘TypedDict’ supports two additional equivalent syntactic
     forms:

          Point2D = TypedDict('Point2D', x=int, y=int, label=str)
          Point2D = TypedDict('Point2D', {'x': int, 'y': int, 'label': str})

     By default, all keys must be present in a TypedDict.  It is
     possible to override this by specifying totality.  Usage:

          class point2D(TypedDict, total=False):
              x: int
              y: int

     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 be required.

     See PEP 589(7) for more examples and detailed rules of using
     ‘TypedDict’.

     3.8 版新加入.

 -- 類別: typing.ForwardRef

     A class used for internal typing representation of string forward
     references.  For example, ‘List["SomeClass"]’ is implicitly
     transformed into ‘List[ForwardRef("SomeClass")]’.  This class
     should not be instantiated by a user, but may be used by
     introspection tools.

     3.7.4 版新加入.

 -- 函式: typing.NewType (name, tp)

     A helper function to indicate a distinct type to a typechecker, see
     *note NewType: 3270.  At runtime it returns a function that returns
     its argument.  Usage:

          UserId = NewType('UserId', int)
          first_user = UserId(1)

     3.5.2 版新加入.

 -- 函式: 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.get_type_hints (obj[, globals[, locals]])

     Return a dictionary containing type hints for a function, method,
     module or class object.

     This is often the same as ‘obj.__annotations__’.  In addition,
     forward references encoded as string literals are handled by
     evaluating them in ‘globals’ and ‘locals’ namespaces.  If
     necessary, ‘Optional[t]’ is added for function and method
     annotations if a default value equal to ‘None’ is set.  For a class
     ‘C’, return a dictionary constructed by merging all the
     ‘__annotations__’ along ‘C.__mro__’ in reverse order.

 -- 函式: typing.get_origin (tp)

 -- 函式: typing.get_args (tp)

     Provide basic introspection for generic types and special typing
     forms.

     For a typing object of the form ‘X[Y, Z, ...]’ these functions
     return ‘X’ and ‘(Y, Z, ...)’.  If ‘X’ is a generic alias for a
     builtin or *note collections: 1e. class, it gets normalized to the
     original class.  For unsupported objects return ‘None’ and ‘()’
     correspondingly.  Examples:

          assert get_origin(Dict[str, int]) is dict
          assert get_args(Dict[int, str]) == (int, str)

          assert get_origin(Union[int, str]) is Union
          assert get_args(Union[int, str]) == (int, str)

     3.8 版新加入.

 -- 函式: @typing.overload

     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).  The ‘@overload’-decorated definitions are for
     the benefit of the type checker only, since they will be
     overwritten by the non-‘@overload’-decorated definition, while the
     latter is used at runtime but should be ignored by a type checker.
     At runtime, calling a ‘@overload’-decorated function directly will
     raise *note NotImplementedError: 613.  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>

     See PEP 484(8) for details and comparison with other typing
     semantics.

 -- 函式: @typing.final

     A decorator to indicate to type checkers that the decorated method
     cannot be overridden, and the decorated class cannot be subclassed.
     For example:

          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
              ...

     There is no runtime checking of these properties.  See PEP 591(9)
     for more details.

     3.8 版新加入.

 -- 函式: @typing.no_type_check

     Decorator to indicate that annotations are not type hints.

     This works as class or function *note decorator: 284.  With a
     class, it applies recursively to all methods defined in that class
     (but not to methods defined in its superclasses or subclasses).

     This mutates the function(s) in place.

 -- 函式: @typing.no_type_check_decorator

     Decorator to give another decorator the *note no_type_check():
     32a8. effect.

     This wraps the decorator with something that wraps the decorated
     function in *note no_type_check(): 32a8.

 -- 函式: @typing.type_check_only

     Decorator to mark a class or function to be 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.

 -- 函式: @typing.runtime_checkable

     Mark a protocol class as a runtime protocol.

     Such a protocol can be used with *note isinstance(): 454. and *note
     issubclass(): 455.  This raises *note TypeError: 193. when applied
     to a non-protocol class.  This allows a simple-minded structural
     check, very similar to "one trick ponies" in *note collections.abc:
     1f. such as *note Iterable: 1957.  For example:

          @runtime_checkable
          class Closable(Protocol):
              def close(self): ...

          assert isinstance(open('/some/file'), Closable)

     `Warning:' this will check only the presence of the required
     methods, not their type signatures!

     3.8 版新加入.

 -- Data: typing.Any

     Special type indicating an unconstrained type.

        * Every type is compatible with *note Any: 657.

        * *note Any: 657. is compatible with every type.

 -- Data: typing.NoReturn

     Special type indicating that a function never returns.  For
     example:

          from typing import NoReturn

          def stop() -> NoReturn:
              raise RuntimeError('no way')

     3.5.4 版新加入.

     3.6.2 版新加入.

 -- Data: typing.Union

     Union type; ‘Union[X, Y]’ means either X or Y.

     To define a union, use e.g.  ‘Union[int, str]’.  Details:

        * The arguments must be types and there must be at least one.

        * Unions of unions are flattened, e.g.:

               Union[Union[int, str], float] == Union[int, str, float]

        * Unions of a single argument vanish, e.g.:

               Union[int] == int  # The constructor actually returns int

        * Redundant arguments are skipped, e.g.:

               Union[int, str, int] == Union[int, str]

        * When comparing unions, the argument order is ignored, e.g.:

               Union[int, str] == Union[str, int]

        * You cannot subclass or instantiate a union.

        * You cannot write ‘Union[X][Y]’.

        * You can use ‘Optional[X]’ as a shorthand for ‘Union[X, None]’.

     3.7 版更變: Don’t remove explicit subclasses from unions at
     runtime.

 -- Data: typing.Optional

     Optional type.

     ‘Optional[X]’ is equivalent to ‘Union[X, None]’.

     Note that this is not the same concept as an optional argument,
     which is one that has a default.  An optional argument with a
     default does not require the ‘Optional’ qualifier on its type
     annotation just because it is optional.  For example:

          def foo(arg: int = 0) -> None:
              ...

     On the other hand, if an explicit value of ‘None’ is allowed, the
     use of ‘Optional’ is appropriate, whether the argument is optional
     or not.  For example:

          def foo(arg: Optional[int] = None) -> None:
              ...

 -- Data: typing.Tuple

     Tuple type; ‘Tuple[X, Y]’ is the type of a tuple of two items with
     the first item of type X and the second of type Y. The type of the
     empty tuple can be written as ‘Tuple[()]’.

     Example: ‘Tuple[T1, T2]’ is a tuple of two elements corresponding
     to type variables T1 and T2.  ‘Tuple[int, float, str]’ is a tuple
     of an int, a float and a string.

     To specify a variable-length tuple of homogeneous type, use literal
     ellipsis, e.g.  ‘Tuple[int, ...]’.  A plain *note Tuple: 326c. is
     equivalent to ‘Tuple[Any, ...]’, and in turn to *note tuple: 483.

 -- Data: typing.Callable

     Callable type; ‘Callable[[int], str]’ is a function of (int) ->
     str.

     The subscription syntax must always be used with exactly two
     values: the argument list and the return type.  The argument list
     must be a list of types or an ellipsis; the return type must be a
     single type.

     There is no syntax to indicate optional or keyword arguments; such
     function types are rarely used as callback types.  ‘Callable[...,
     ReturnType]’ (literal ellipsis) can be used to type hint a callable
     taking any number of arguments and returning ‘ReturnType’.  A plain
     *note Callable: 326d. is equivalent to ‘Callable[..., Any]’, and in
     turn to *note collections.abc.Callable: 195a.

 -- Data: typing.Literal

     A type that can be used to indicate to type checkers that the
     corresponding variable or function parameter has a value equivalent
     to the provided literal (or one of several literals).  For example:

          def validate_simple(data: Any) -> Literal[True]:  # always returns True
              ...

          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[...]’ cannot be subclassed.  At runtime, an arbitrary
     value is allowed as type argument to ‘Literal[...]’, but type
     checkers may impose restrictions.  See PEP 586(10) for more details
     about literal types.

     3.8 版新加入.

 -- Data: typing.ClassVar

     Special type construct to mark class variables.

     As introduced in PEP 526(11), 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.
     Usage:

          class Starship:
              stats: ClassVar[Dict[str, int]] = {} # class variable
              damage: int = 10                     # instance variable

     *note ClassVar: 5a8. accepts only types and cannot be further
     subscribed.

     *note ClassVar: 5a8. is not a class itself, and should not be used
     with *note isinstance(): 454. or *note issubclass(): 455.  *note
     ClassVar: 5a8. does not change Python runtime behavior, but it can
     be used by third-party type checkers.  For example, a type checker
     might flag the following code as an error:

          enterprise_d = Starship(3000)
          enterprise_d.stats = {} # Error, setting class variable on instance
          Starship.stats = {}     # This is OK

     3.5.3 版新加入.

 -- Data: typing.Final

     A special typing construct to indicate to type checkers that a name
     cannot be re-assigned or overridden in a subclass.  For example:

          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

     There is no runtime checking of these properties.  See PEP 591(12)
     for more details.

     3.8 版新加入.

 -- Data: typing.AnyStr

     ‘AnyStr’ is a type variable defined as ‘AnyStr = TypeVar('AnyStr',
     str, bytes)’.

     It is meant to be used for functions that may accept any kind of
     string without allowing different kinds of strings to mix.  For
     example:

          def concat(a: AnyStr, b: AnyStr) -> AnyStr:
              return a + b

          concat(u"foo", u"bar")  # Ok, output has type 'unicode'
          concat(b"foo", b"bar")  # Ok, output has type 'bytes'
          concat(u"foo", b"bar")  # Error, cannot mix unicode and bytes

 -- Data: 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()

     Note that 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.

     3.5.2 版新加入.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0484

   (2) https://www.python.org/dev/peps/pep-0484

   (3) https://www.python.org/dev/peps/pep-0544

   (4) https://www.python.org/dev/peps/pep-0484

   (5) https://www.python.org/dev/peps/pep-0526

   (6) https://www.python.org/dev/peps/pep-0526

   (7) https://www.python.org/dev/peps/pep-0589

   (8) https://www.python.org/dev/peps/pep-0484

   (9) https://www.python.org/dev/peps/pep-0591

   (10) https://www.python.org/dev/peps/pep-0586

   (11) https://www.python.org/dev/peps/pep-0526

   (12) https://www.python.org/dev/peps/pep-0591


File: python.info,  Node: pydoc --- Documentation generator and online help system,  Next: doctest --- Test interactive Python examples,  Prev: typing --- Support for type hints,  Up: 開發工具

5.26.2 ‘pydoc’ — Documentation generator and online help system
---------------------------------------------------------------

`Source code:' Lib/pydoc.py(1)

__________________________________________________________________

The *note pydoc: da. 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, *note pydoc: da. 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(): 32b0.).

The built-in function *note help(): 577. invokes the online help system
in the interactive interpreter, which uses *note pydoc: da. 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

     pydoc sys

at a shell prompt will display documentation on the *note sys: fe.
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, *note
     pydoc: da. 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.  ‘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.

‘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.

‘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 版更變: Added the ‘-b’ option.

3.3 版更變: The ‘-g’ command line option was removed.

3.4 版更變: *note pydoc: da. now uses *note inspect.signature(): 560.
rather than *note inspect.getfullargspec(): 562. to extract signature
information from callables.

3.7 版更變: Added the ‘-n’ option.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/pydoc.py


File: python.info,  Node: doctest --- Test interactive Python examples,  Next: unittest --- 單元測試框架,  Prev: pydoc --- Documentation generator and online help system,  Up: 開發工具

5.26.3 ‘doctest’ — Test interactive Python examples
---------------------------------------------------

`Source code:' Lib/doctest.py(1)

__________________________________________________________________

The *note doctest: 67. 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:
67. 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: 67. 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 tests in __main__
        8 tests in __main__.factorial
     9 tests in 2 items.
     9 passed and 0 failed.
     Test passed.
     $

That’s all you need to know to start making productive use of *note
doctest: 67.!  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.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::
* Basic API::
* Unittest API::
* Advanced API::
* Debugging::
* Soapbox::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/doctest.py


File: python.info,  Node: Simple Usage Checking Examples in Docstrings,  Next: Simple Usage Checking Examples in a Text File,  Up: doctest --- Test interactive Python examples

5.26.3.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()

*note doctest: 67. 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():
dd5, or prohibit it by passing ‘verbose=False’.  In either of those
cases, ‘sys.argv’ is not examined by *note testmod(): dd5. (so passing
‘-v’ or not has no effect).

There is also a command line shortcut for running *note testmod(): dd5.
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(): dd5. 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(): dd5, see section *note Basic
API: 32b5.


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 --- Test interactive Python examples

5.26.3.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(): 32b8.
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(): dd5, *note testfile(): 32b8. 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(): dd5.

By default, *note testfile(): 32b8. looks for files in the calling
module’s directory.  See section *note Basic API: 32b5. for a
description of the optional arguments that can be used to tell it to
look for files in other locations.

Like *note testmod(): dd5, *note testfile(): 32b8.’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():
32b8.  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: 67. infers
that it must be run with *note testfile(): 32b8, not *note testmod():
dd5.

For more information on *note testfile(): 32b8, see section *note Basic
API: 32b5.


File: python.info,  Node: How It Works,  Next: Basic API,  Prev: Simple Usage Checking Examples in a Text File,  Up: doctest --- Test interactive Python examples

5.26.3.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?::
* Option Flags::
* Directives::
* Warnings: Warnings<2>.


File: python.info,  Node: Which Docstrings Are Examined?,  Next: How are Docstring Examples Recognized?,  Up: How It Works

5.26.3.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, if ‘M.__test__’ exists and "is true", 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

     <name of M>.__test__.K

Any classes found are recursively searched similarly, to test docstrings
in their contained methods and nested classes.

`CPython implementation detail:' Prior to version 3.4, extension modules
written in C were not fully searched by doctest.


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.3.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.

     >>> # comments are ignored
     >>> 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: 32bf. option or *note directive: 32c0. 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: 32c1. 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.3.6 What’s the Execution Context?
......................................

By default, each time *note doctest: 67. 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(): dd5. or *note testfile(): 32b8.
instead.


File: python.info,  Node: What About Exceptions?,  Next: Option Flags,  Prev: What's the Execution Context?,  Up: How It Works

5.26.3.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.

Simple example:

     >>> [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: 1fc. 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: 1fc.) 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: dd6. 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: 1fc. 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: 32c6. 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: 45d.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: 45d. that omits
     the traceback header, you will need to manually add the traceback
     header line to your test example.

   * For some *note SyntaxError: 45d.s, Python displays the character
     position of the syntax error, using a ‘^’ marker:

          >>> 1 1
            File "<stdin>", line 1
              1 1
                ^
          SyntaxError: invalid syntax

     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 1
          Traceback (most recent call last):
            File "<stdin>", line 1
              1 1
              ^
          SyntaxError: invalid syntax

   ---------- Footnotes ----------

   (1) (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: Option Flags,  Next: Directives,  Prev: What About Exceptions?,  Up: How It Works

5.26.3.8 Option Flags
.....................

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: 1542. together and passed to various functions.
The names can also be used in *note doctest directives: 32c0, 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:

 -- Data: 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: 32c9. 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.

 -- Data: 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: 32ca. is
     specified, this substitution is not allowed.

 -- Data: 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: 32bf. is especially useful when a line of
     expected output is very long, and you want to wrap it across
     multiple lines in your source.

 -- Data: 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.

 -- Data: doctest.IGNORE_EXCEPTION_DETAIL

     When specified, an example that expects an exception passes if an
     exception of the expected type is raised, even if the exception
     detail does not match.  For example, an example expecting
     ‘ValueError: 42’ will pass if the actual exception raised is
     ‘ValueError: 3*14’, but will fail, e.g., if *note TypeError: 193.
     is raised.

     It will also ignore the module name used in Python 3 doctest
     reports.  Hence both of these variations will work with the flag
     specified, regardless of whether the test is run under Python 2.7
     or Python 3.2 (or later versions):

          >>> raise CustomError('message')
          Traceback (most recent call last):
          CustomError: message

          >>> raise CustomError('message')
          Traceback (most recent call last):
          my_module.CustomError: message

     Note that *note ELLIPSIS: dd6. can also be used to ignore the
     details of the exception message, but such a test may still fail
     based on whether or not the module details are printed as part of
     the exception name.  Using *note IGNORE_EXCEPTION_DETAIL: 32c6. and
     the details from Python 2.3 is also the only clear way to write a
     doctest that doesn’t care about the exception detail yet continues
     to pass under Python 2.3 or earlier (those releases do not support
     *note doctest directives: 32c0. and ignore them as irrelevant
     comments).  For example:

          >>> (1, 2)[3] = 'moo'
          Traceback (most recent call last):
            File "<stdin>", line 1, in <module>
          TypeError: object doesn't support item assignment

     passes under Python 2.3 and later Python versions with the flag
     specified, even though the detail changed in Python 2.4 to say
     "does not" instead of "doesn’t".

     3.2 版更變: *note IGNORE_EXCEPTION_DETAIL: 32c6. now also ignores
     any information relating to the module containing the exception
     under test.

 -- Data: 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.

 -- Data: doctest.COMPARISON_FLAGS

     A bitmask or’ing together all the comparison flags above.

The second group of options controls how test failures are reported:

 -- Data: doctest.REPORT_UDIFF

     When specified, failures that involve multi-line expected and
     actual outputs are displayed using a unified diff.

 -- Data: doctest.REPORT_CDIFF

     When specified, failures that involve multi-line expected and
     actual outputs will be displayed using a context diff.

 -- Data: 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.

 -- Data: 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: 32cd. is specified, the remaining
     examples are still run, and still count towards the total number of
     failures reported; only the output is suppressed.

 -- Data: 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 版新加入.

 -- Data: 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: 67. 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(): 32cf. can be
     used when subclassing *note OutputChecker: 32d0. or *note
     DocTestRunner: 32d1. to create new options that are supported by
     your subclasses.  *note register_optionflag(): 32cf. should always
     be called using the following idiom:

          MY_FLAG = register_optionflag('MY_FLAG')


File: python.info,  Node: Directives,  Next: Warnings<2>,  Prev: Option Flags,  Up: How It Works

5.26.3.9 Directives
...................

Doctest directives may be used to modify the *note option flags: 841.
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)))
     [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)))
     [0, 1, ..., 18, 19]

Multiple directives can be used on a single physical line, separated by
commas:

     >>> print(list(range(20)))
     [0,    1, ...,   18,    19]

If multiple directive comments are used for a single example, then they
are combined:

     >>> print(list(range(20)))
     ...
     [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)))
     ...
     [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: Warnings<2>,  Prev: Directives,  Up: How It Works

5.26.3.10 Warnings
..................

*note doctest: 67. 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()
     {"Hermione", "Harry"}

is vulnerable!  One workaround is to do

     >>> foo() == {"Hermione", "Harry"}
     True

instead.  Another is to do

     >>> d = sorted(foo())
     >>> d
     ['Harry', 'Hermione']

     備註: Before Python 3.6, when printing a dict, Python did not
     guarantee that the key-value pairs was printed in any particular
     order.

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
     <__main__.C instance at 0x00AC18F0>

The *note ELLIPSIS: dd6. directive gives a nice approach for the last
example:

     >>> C()
     <__main__.C instance 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: Basic API,  Next: Unittest API,  Prev: How It Works,  Up: doctest --- Test interactive Python examples

5.26.3.11 Basic API
...................

The functions *note testmod(): dd5. and *note testfile(): 32b8. 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: 32b3. and
*note Simple Usage; Checking Examples in a Text File: 32b6.

 -- 函式: 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():
     dce.: 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: 1542. of option flags.  See section *note Option Flags:
     841.

     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: 32c1.
     (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
     and is not ‘None’.  ‘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 ‘doctest.master.summarize()’ in conjunction
     with *note testmod(): dd5. continues to get output for objects with
     no tests.  The `exclude_empty' argument to the newer *note
     DocTestFinder: 32db. constructor defaults to true.

     Optional arguments `extraglobs', `verbose', `report',
     `optionflags', `raise_on_error', and `globs' are the same as for
     function *note testfile(): 32b8. 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(): 32b8. above.


File: python.info,  Node: Unittest API,  Next: Advanced API,  Prev: Basic API,  Up: doctest --- Test interactive Python examples

5.26.3.12 Unittest API
......................

As your collection of doctest’ed modules grows, you’ll want a way to run
all their doctests systematically.  *note doctest: 67. provides two
functions that can be used to create *note unittest: 11c. test suites
from modules and text files containing doctests.  To integrate with
*note unittest: 11c. test discovery, include a ‘load_tests()’ 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: 6d3.
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: 6d3.

     The returned *note unittest.TestSuite: 6d3. 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 ‘failureException’ exception is raised showing the
     name of the file containing the test and a (sometimes approximate)
     line number.

     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: 32e0. 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: 32e0.
     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 Option Flags: 841.  See function *note
     set_unittest_reportflags(): 32e1. below for a better way to set
     reporting options.

     Optional argument `parser' specifies a *note DocTestParser: 32c1.
     (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(): 32df.

 -- 函式: doctest.DocTestSuite (module=None, globs=None,
          extraglobs=None, test_finder=None, setUp=None, tearDown=None,
          checker=None)

     Convert doctest tests for a module to a *note unittest.TestSuite:
     6d3.

     The returned *note unittest.TestSuite: 6d3. 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
     ‘failureException’ exception is raised showing the name of the file
     containing the test and a (sometimes approximate) line number.

     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: 32db.
     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(): 32df. above.

     This function uses the same search technique as *note testmod():
     dd5.

     3.5 版更變: *note DocTestSuite(): 6d2. returns an empty *note
     unittest.TestSuite: 6d3. if `module' contains no docstrings instead
     of raising *note ValueError: 1fc.

Under the covers, *note DocTestSuite(): 6d2. creates a *note
unittest.TestSuite: 6d3. out of ‘doctest.DocTestCase’ instances, and
‘DocTestCase’ is a subclass of *note unittest.TestCase: 904.
‘DocTestCase’ isn’t documented here (it’s an internal detail), but
studying its code can answer questions about the exact details of *note
unittest: 11c. integration.

Similarly, *note DocFileSuite(): 32df. creates a *note
unittest.TestSuite: 6d3. out of ‘doctest.DocFileCase’ instances, and
‘DocFileCase’ is a subclass of ‘DocTestCase’.

So both ways of creating a *note unittest.TestSuite: 6d3. run instances
of ‘DocTestCase’.  This is important for a subtle reason: when you run
*note doctest: 67. functions yourself, you can control the *note
doctest: 67. options in use directly, by passing option flags to *note
doctest: 67. functions.  However, if you’re writing a *note unittest:
11c. framework, *note unittest: 11c. ultimately controls when and how
tests get run.  The framework author typically wants to control *note
doctest: 67. reporting options (perhaps, e.g., specified by command line
options), but there’s no way to pass options through *note unittest:
11c. to *note doctest: 67. test runners.

For this reason, *note doctest: 67. also supports a notion of *note
doctest: 67. reporting flags specific to *note unittest: 11c. support,
via this function:

 -- 函式: doctest.set_unittest_reportflags (flags)

     Set the *note doctest: 67. reporting flags to use.

     Argument `flags' takes the *note bitwise OR: 1542. of option flags.
     See section *note Option Flags: 841.  Only "reporting flags" can be
     used.

     This is a module-global setting, and affects all future doctests
     run by module *note unittest: 11c.: 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),
     *note doctest: 67.’s *note unittest: 11c. reporting flags are *note
     bitwise ORed: 1542. into the option flags, and the option flags so
     augmented are passed to the *note DocTestRunner: 32d1. instance
     created to run the doctest.  If any reporting flags were specified
     when the ‘DocTestCase’ instance was constructed, *note doctest:
     67.’s *note unittest: 11c. reporting flags are ignored.

     The value of the *note unittest: 11c. 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 --- Test interactive Python examples

5.26.3.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: 32e4.: A single Python *note statement: 1b97, paired
     with its expected output.

   * *note DocTest: 32e0.: A collection of *note Example: 32e4.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: 32db.: Finds all docstrings in a given module,
     and uses a *note DocTestParser: 32c1. to create a *note DocTest:
     32e0. from every docstring that contains interactive examples.

   * *note DocTestParser: 32c1.: Creates a *note DocTest: 32e0. object
     from a string (such as an object’s docstring).

   * *note DocTestRunner: 32d1.: Executes the examples in a *note
     DocTest: 32e0, and uses an *note OutputChecker: 32d0. to verify
     their output.

   * *note OutputChecker: 32d0.: 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 Objects::
* Example Objects::
* DocTestFinder objects::
* DocTestParser objects::
* DocTestRunner objects::
* OutputChecker objects::


File: python.info,  Node: DocTest Objects,  Next: Example Objects,  Up: Advanced API

5.26.3.14 DocTest Objects
.........................

 -- 類別: 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: 32e0. defines the following attributes.  They are
     initialized by the constructor, and should not be modified
     directly.

      -- 屬性: examples

          A list of *note Example: 32e4. 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: 32e8. after
          the test is run.

      -- 屬性: name

          A string name identifying the *note DocTest: 32e0.  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: 32e0. was
          extracted from; or ‘None’ if the filename is unknown, or if
          the *note DocTest: 32e0. was not extracted from a file.

      -- 屬性: lineno

          The line number within *note filename: 32ea. where this *note
          DocTest: 32e0. 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 Objects,  Next: DocTestFinder objects,  Prev: DocTest Objects,  Up: Advanced API

5.26.3.15 Example Objects
.........................

 -- 類別: 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: 32e4. 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: 32f0. 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(): 32f2.  *note exc_msg: 32f1.
          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:
          32d1.’s ‘optionflags’).  By default, no options are set.


File: python.info,  Node: DocTestFinder objects,  Next: DocTestParser objects,  Prev: Example Objects,  Up: Advanced API

5.26.3.16 DocTestFinder objects
...............................

 -- 類別: doctest.DocTestFinder (verbose=False, parser=DocTestParser(),
          recurse=True, exclude_empty=True)

     A processing class used to extract the *note DocTest: 32e0.s that
     are relevant to a given object, from its docstring and the
     docstrings of its contained objects.  *note DocTest: 32e0.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:
     32c1. 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(): 32f8. will only examine the given object, and
     not any contained objects.

     If the optional argument `exclude_empty' is false, then *note
     DocTestFinder.find(): 32f8. will include tests for objects with
     empty docstrings.

     *note DocTestFinder: 32db. defines the following method:

      -- 成員函式: find (obj[, name][, module][, globs][, extraglobs])

          Return a list of the *note DocTest: 32e0.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: 32e0.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: 32e0. 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: 32e0.
          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 objects,  Next: DocTestRunner objects,  Prev: DocTestFinder objects,  Up: Advanced API

5.26.3.17 DocTestParser objects
...............................

 -- 類別: doctest.DocTestParser

     A processing class used to extract interactive examples from a
     string, and use them to create a *note DocTest: 32e0. object.

     *note DocTestParser: 32c1. 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: 32e0. object.

          `globs', `name', `filename', and `lineno' are attributes for
          the new *note DocTest: 32e0. object.  See the documentation
          for *note DocTest: 32e0. 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: 32e4. 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: 32e4.s
          and strings.  Line numbers for the *note Example: 32e4.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: DocTestRunner objects,  Next: OutputChecker objects,  Prev: DocTestParser objects,  Up: Advanced API

5.26.3.18 DocTestRunner objects
...............................

 -- 類別: doctest.DocTestRunner (checker=None, verbose=None,
          optionflags=0)

     A processing class used to execute and verify the interactive
     examples in a *note DocTest: 32e0.

     The comparison between expected outputs and actual outputs is done
     by an *note OutputChecker: 32d0.  This comparison may be customized
     with a number of option flags; see section *note Option Flags: 841.
     for more information.  If the option flags are insufficient, then
     the comparison may also be customized by passing a subclass of
     *note OutputChecker: 32d0. to the constructor.

     The test runner’s display output can be controlled in two ways.
     First, an output function can be passed to ‘TestRunner.run()’; 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(): 3300, *note report_success(): 3301, *note
     report_unexpected_exception(): 3302, and *note report_failure():
     3303.

     The optional keyword argument `checker' specifies the *note
     OutputChecker: 32d0. 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: 32d1.’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
     Option Flags: 841.

     *note DocTestParser: 32c1. 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: 32d1. 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(): 3304.

      -- 成員函式: report_success (out, test, example, got)

          Report that the given example ran successfully.  This method
          is provided to allow subclasses of *note DocTestRunner: 32d1.
          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(): 3304.

      -- 成員函式: report_failure (out, test, example, got)

          Report that the given example failed.  This method is provided
          to allow subclasses of *note DocTestRunner: 32d1. 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(): 3304.

      -- 成員函式: 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: 32d1. 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(): c64.).  `test' is the
          test containing `example'.  `out' is the output function that
          was passed to *note DocTestRunner.run(): 3304.

      -- 成員函式: run (test, compileflags=None, out=None,
               clear_globs=True)

          Run the examples in `test' (a *note DocTest: 32e0. object),
          and display the results using the writer function `out'.

          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: 32d1.’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 named tuple: aa8.
          ‘TestResults(failed, attempted)’.

          The optional `verbose' argument controls how detailed the
          summary is.  If the verbosity is not specified, then the *note
          DocTestRunner: 32d1.’s verbosity is used.


File: python.info,  Node: OutputChecker objects,  Prev: DocTestRunner objects,  Up: Advanced API

5.26.3.19 OutputChecker objects
...............................

 -- 類別: doctest.OutputChecker

     A class used to check the whether the actual output from a doctest
     example matches the expected output.  *note OutputChecker: 32d0.
     defines two methods: *note check_output(): 3308, which compares a
     given pair of outputs, and returns ‘True’ if they match; and *note
     output_difference(): 3309, which returns a string describing the
     differences between two outputs.

     *note OutputChecker: 32d0. 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 Option Flags: 841. 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 --- Test interactive Python examples

5.26.3.20 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: ca.

   * The *note DebugRunner: 330c. class is a subclass of *note
     DocTestRunner: 32d1. 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: 11c. cases generated by *note DocTestSuite():
     6d2. support the *note debug(): 330d. method defined by *note
     unittest.TestCase: 904.

   * You can add a call to *note pdb.set_trace(): 3c7. 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(): 330e. 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(): 330f. 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: ca.

     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(): d4a, 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(): c49. call to
     *note pdb.run(): 3310.

 -- 函式: doctest.debug_src (src, pm=False, globs=None)

     Debug the doctests in a string.

     This is like function *note debug(): 330d. 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(): 330d. 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: 330c. 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: 330c.’s docstring (which is a doctest!)  for more details:

 -- 類別: doctest.DebugRunner (checker=None, verbose=None,
          optionflags=0)

     A subclass of *note DocTestRunner: 32d1. that raises an exception
     as soon as a failure is encountered.  If an unexpected exception
     occurs, an *note UnexpectedException: 3312. exception is raised,
     containing the test, the example, and the original exception.  If
     the output doesn’t match, then a *note DocTestFailure: 3313.
     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: 32d1. in section *note
     Advanced API: 32e3.

There are two exceptions that may be raised by *note DebugRunner: 330c.
instances:

 -- 例外: doctest.DocTestFailure (test, example, got)

     An exception raised by *note DocTestRunner: 32d1. 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: 3313. defines the following attributes:

 -- 屬性: DocTestFailure.test

     The *note DocTest: 32e0. object that was being run when the example
     failed.

 -- 屬性: DocTestFailure.example

     The *note Example: 32e4. that failed.

 -- 屬性: DocTestFailure.got

     The example’s actual output.

 -- 例外: doctest.UnexpectedException (test, example, exc_info)

     An exception raised by *note DocTestRunner: 32d1. 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: 3312. defines the following attributes:

 -- 屬性: UnexpectedException.test

     The *note DocTest: 32e0. object that was being run when the example
     failed.

 -- 屬性: UnexpectedException.example

     The *note Example: 32e4. that failed.

 -- 屬性: UnexpectedException.exc_info

     A tuple containing information about the unexpected exception, as
     returned by *note sys.exc_info(): c64.


File: python.info,  Node: Soapbox,  Prev: Debugging,  Up: doctest --- Test interactive Python examples

5.26.3.21 Soapbox
.................

As mentioned in the introduction, *note doctest: 67. 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: 67. 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(): 32b8. or *note
     DocFileSuite(): 32df.  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("{} failures out of {} tests".format(fail, total))

註解
....


File: python.info,  Node: unittest --- 單元測試框架,  Next: unittest mock --- mock object library,  Prev: doctest --- Test interactive Python examples,  Up: 開發工具

5.26.4 ‘unittest’ — 單元測試框架
--------------------------------

`Source code:' Lib/unittest/__init__.py(1)

__________________________________________________________________

（假如你已經熟悉相關基礎的測試概念，你可能會希望跳過以下段落，直接參考
*note assert 方法清單: 331e.。）

*note unittest: 11c. 原生的單元測試框架最初由 JUnit 開發，和其他程式語言
相似有主要的單元測試框架。支援自動化測試，對測試分享安裝與關閉程式碼，集
合所有匯總的測試，並且獨立各個測試報告框架。

*note unittest: 11c. 用來作為實現支援一些重要的物件導向方法的概念。

test fixture

     A `test fixture' represents the preparation needed to perform one
     or more tests, and any associated cleanup actions.  This may
     involve, for example, creating temporary or proxy databases,
     directories, or starting a server process.

test case（測試用例）

     一個 `test case' 是一個獨立的單元測試。這是用來確認一個特定設定的輸
     入的特殊回饋。 *note unittest: 11c. 提供一個基礎類別，類別 *note
     TestCase: 904.，可以用來建立一個新的測試條例。

test suite（測試套件）

     `test suite' 是一個搜集測試條例，測試套件，或是兩者皆有。它需要一起
     被執行並用來匯總測試。

test runner（測試執行器）

     `test runner' 是一個編排測試執行與提供結果給使用者的一個元件。執行
     器可以使用圖形化介面，文字介面或是回傳一個特別值用來標示出執行測試
     的結果。

也參考
......

*note doctest: 67. 模組

     另一個執行測試的模組，但使用不一樣的測試方法與規範。

Simple Smalltalk Testing: With Patterns(2)

     Kent Beck 的原始論文討論使用 *note unittest: 11c. 這樣模式的測試框
     架。

pytest(3)

     Third-party unittest framework with a lighter-weight syntax for
     writing tests.  For example, ‘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) or
Travis-CI(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.8/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://jenkins.io/

   (8) https://travis-ci.com

   (9) https://www.appveyor.com/


File: python.info,  Node: 簡單範例,  Next: 命令執行列介面 Command-Line Interface,  Up: unittest --- 單元測試框架

5.26.4.1 簡單範例
.................

*note unittest: 11c. 模組提供一系列豐富的工具用來建構與執行測試。本節將
展示這一系列工具中一部份，它們已能滿足大部份使用者需求。

這是一段簡短的腳本用來測試 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: 904. 類別來建
立。這裡定義了三個獨立的物件方法，名稱皆以 ‘test’ 開頭。這樣的命名方式能
告知 test runner 哪些物件方法為定義的測試。

每個測試的關鍵為呼叫 *note assertEqual(): bba. 來確認是否為期望的結果；
*note assertTrue(): bb9. 或是 *note assertFalse(): ccc. 用來驗證一個條件
式； *note assertRaises(): abf. 用來驗證是否觸發一個特定的 exception。使
用這些物件方法來取代 *note assert: e0b. 陳述句，將能使 test runner 收集
所有的測試結果並產生一個報表。

The *note setUp(): cd0. and *note tearDown(): cd1. 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: 3321.

最後將顯示一個簡單的方法去執行測試 *note unittest.main(): 907. 提供一個
命令執行列介面測試腳本。當透過命令執行列執行，輸出結果將會像是：

     ...
     ----------------------------------------------------------------------
     Ran 3 tests in 0.000s

     OK

在測試時加入 ‘-v’ 選項將指示 *note unittest.main(): 907. 提高 verbosity
層級，產生以下的輸出：

     test_isupper (__main__.TestStringMethods) ... ok
     test_split (__main__.TestStringMethods) ... ok
     test_upper (__main__.TestStringMethods) ... ok

     ----------------------------------------------------------------------
     Ran 3 tests in 0.001s

     OK

以上的例子顯示大多數使用 *note unittest: 11c. 特徵足以滿足大多數日常測試
的需求。接下來第一部分文件的剩餘部分將繼續探索完整特徵設定。


File: python.info,  Node: 命令執行列介面 Command-Line Interface,  Next: Test Discovery（測試探索）,  Prev: 簡單範例,  Up: unittest --- 單元測試框架

5.26.4.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（測試探索）: 3324.：

     python -m unittest

列出所有命令列選項：

     python -m unittest -h

3.2 版更變: 在早期的版本可以個別執行測試方法和不需要模組或是類別。

* Menu:

* 命令列模式選項::


File: python.info,  Node: 命令列模式選項,  Up: 命令執行列介面 Command-Line Interface

5.26.4.3 命令列模式選項
.......................

‘unittest’ supports these command-line options:

 -- 程式選項: -b, --buffer

     Standard output 與 standard error stream 將在測試執行被緩衝
     (buffer)。這些輸出在測試通過時被丟棄。若是測試錯誤或失則，這些輸出
     將會正常地被印出，並且被加入至錯誤訊息中。

 -- 程式選項: -c, --catch

     ‘Control-C’ 測試執行過程中等待正確的測試結果並回報目前為止所有的測
     試結果。第二個 ‘Control-C’ 拋出一般例外 *note KeyboardInterrupt:
     198.。

     參照 *note Signal Handling: 3326. 針對函式提供的功能。

 -- 程式選項: -f, --failfast

     在第一次錯誤或是失敗停止執行測試。

 -- 程式選項: -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 of the given patterns are included.

     Patterns that contain a wildcard character (‘*’) are matched
     against the test name using *note fnmatch.fnmatchcase(): 1c82.;
     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’.

 -- 程式選項: --locals

     透過 traceback 顯示本地變數。

3.2 版新加入: 增加命令列模式選項 ‘-b’ 、 ‘-c’ 與 ‘-f’。

3.5 版新加入: 命令列選項 ‘--locals’。

3.7 版新加入: The command-line option ‘-k’.

對執行所有的專案或是一個子集合測試，命令列模式可以可以被用來做測試探索。


File: python.info,  Node: Test Discovery（測試探索）,  Next: Organizing test code,  Prev: 命令執行列介面 Command-Line Interface,  Up: unittest --- 單元測試框架

5.26.4.4 Test Discovery（測試探索）
...................................

3.2 版新加入.

單元測試支援簡單的 test discovery（測試探索）。為了相容於測試探索，所有
的測試檔案都要是*note 模組: 1282.或是*note 套件: 128f.（包含 *note
namespace packages: 14b8.），並能從專案的最上層目錄中 import（代表它們的
檔案名稱必須是有效的 *note identifiers: 13d9.）。

Test discovery（測試探索）實作在 *note TestLoader.discover(): 909.，但也
可以被用於命令列模式。基本的命令列模式用法如下：

     cd project_directory
     python -m unittest discover

     備註: ‘python -m unittest’ 作為捷徑，其功能相當於 ‘python -m
     unittest discover’。假如你想傳遞引數至探索測試的話，一定要明確地加
     入 ‘discover’ 子指令。

‘discover’ 子指令有以下幾個選項：

 -- 程式選項: -v, --verbose

     詳細（verbose）輸出

 -- 程式選項: -s, --start-directory directory

     開始尋找的資料夾（預設為 ‘.’）

 -- 程式選項: -p, --pattern pattern

     匹配測試檔案的模式（預設為 ‘test*.py’）

 -- 程式選項: -t, --top-level-directory directory

     專案的最高階層目錄 (defaults to start directory)

*note -s: 332b, *note -p: 332c, 和 *note -t: 332d. 選項依照傳遞位置作為
引數排序順序。以下兩個命令列被視為等價:

     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: 332e.

3.4 版更變: Test discovery supports *note namespace packages: 14b8. for
start directory.  Note that you need to the top level directory too.
(e.g.  ‘python -m unittest discover -s root/namespace -t root’).


File: python.info,  Node: Organizing test code,  Next: Re-using old test code,  Prev: Test Discovery（測試探索）,  Up: unittest --- 單元測試框架

5.26.4.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: 11c, test cases are represented by *note unittest.TestCase:
904. instances.  To make your own test cases you must write subclasses
of *note TestCase: 904. or use *note FunctionTestCase: 3330.

The testing code of a *note TestCase: 904. 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: 904. 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 ‘assert*()’
methods provided by the *note TestCase: 904. base class.  If the test
fails, an exception will be raised with an explanatory message, and
*note unittest: 11c. 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(): cd0, 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(): cd0. 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(): cd1. 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(): cd0. succeeded, *note tearDown(): cd1. 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(): cd0,
*note tearDown(): cd1, 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: 11c.
provides a mechanism for this: the `test suite', represented by *note
unittest: 11c.’s *note TestSuite: 6d3. class.  In most cases, calling
*note unittest.main(): 907. 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.4.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: 11c, without converting every old test
function to a *note TestCase: 904. subclass.

For this reason, *note unittest: 11c. provides a *note FunctionTestCase:
3330. class.  This subclass of *note TestCase: 904. 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: 3330. can be used to
     quickly convert an existing test base over to a *note unittest:
     11c.-based system, this approach is not recommended.  Taking the
     time to set up proper *note TestCase: 904. subclasses will make
     future test refactorings infinitely easier.

In some cases, the existing tests may have been written using the *note
doctest: 67. module.  If so, *note doctest: 67. provides a
‘DocTestSuite’ class that can automatically build *note
unittest.TestSuite: 6d3. instances from the existing *note doctest:
67.-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.4.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: ac4.

Skipping a test is simply a matter of using the *note skip(): f85. *note
decorator: 284. or one of its conditional variants, calling *note
TestCase.skipTest(): 3335. within a *note setUp(): cd0. or test method,
or raising *note SkipTest: 908. 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) ... skipped 'not supported in this library version'
     test_nothing (__main__.MyTestCase) ... skipped 'demonstrating skipping'
     test_maybe_skipped (__main__.MyTestCase) ... skipped 'external resource not available'
     test_windows_support (__main__.MyTestCase) ... 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(): cd0. 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(): 3336. 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(): f85. 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 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(): 3335. or one of the
     skipping decorators instead of raising this directly.

Skipped tests will not have *note setUp(): cd0. or *note tearDown():
cd1. run around them.  Skipped classes will not have *note setUpClass():
24d. or *note tearDownClass(): cce. 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.4.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(): 905. context manager.

For example, the following test:

     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)

will produce the following output:

     ======================================================================
     FAIL: test_even (__main__.NumbersTest) (i=1)
     ----------------------------------------------------------------------
     Traceback (most recent call last):
       File "subtests.py", line 32, in test_even
         self.assertEqual(i % 2, 0)
     AssertionError: 1 != 0

     ======================================================================
     FAIL: test_even (__main__.NumbersTest) (i=3)
     ----------------------------------------------------------------------
     Traceback (most recent call last):
       File "subtests.py", line 32, in test_even
         self.assertEqual(i % 2, 0)
     AssertionError: 1 != 0

     ======================================================================
     FAIL: test_even (__main__.NumbersTest) (i=5)
     ----------------------------------------------------------------------
     Traceback (most recent call last):
       File "subtests.py", line 32, 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)
     ----------------------------------------------------------------------
     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.4.9 Classes and functions
..............................

This section describes in depth the API of *note unittest: 11c.

* Menu:

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


File: python.info,  Node: Test cases,  Next: Grouping tests,  Up: Classes and functions

5.26.4.10 Test cases
....................

 -- 類別: unittest.TestCase (methodName='runTest')

     Instances of the *note TestCase: 904. class represent the logical
     test units in the *note unittest: 11c. 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: 904. will run a single base
     method: the method named `methodName'.  In most uses of *note
     TestCase: 904, you will neither change the `methodName' nor
     reimplement the default ‘runTest()’ method.

     3.2 版更變: *note TestCase: 904. can be instantiated successfully
     without providing a `methodName'.  This makes it easier to
     experiment with *note TestCase: 904. from the interactive
     interpreter.

     *note TestCase: 904. 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: 1033. or *note SkipTest: 908, 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: 1033. or *note SkipTest: 908, 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(): cd0. 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(): 1d9.:

               @classmethod
               def setUpClass(cls):
                   ...

          See *note Class and Module Fixtures: 333e. for more details.

          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(): 1d9.:

               @classmethod
               def tearDownClass(cls):
                   ...

          See *note Class and Module Fixtures: 333e. for more details.

          3.2 版新加入.

      -- 成員函式: run (result=None)

          Run the test, collecting the result into the *note TestResult:
          ac4. object passed as `result'.  If `result' is omitted or
          ‘None’, a temporary result object is created (by calling the
          *note defaultTestResult(): 333f. method) and used.  The result
          object is returned to *note run(): ac3.’s caller.

          The same effect may be had by simply calling the *note
          TestCase: 904. 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(): cd0. skips
          the current test.  See *note Skipping tests and expected
          failures: 3334. 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.

          See *note Distinguishing test iterations using subtests: 906.
          for more information.

          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: 904. 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): bba.                 ‘a == b’
                                                   
                                                                                     
     *note assertNotEqual(a, b): bbb.              ‘a != b’
                                                   
                                                                                     
     *note assertTrue(x): bb9.                     ‘bool(x) is True’
                                                   
                                                                                     
     *note assertFalse(x): ccc.                    ‘bool(x) is False’
                                                   
                                                                                     
     *note assertIs(a, b): cd4.                    ‘a is b’                          3.1
                                                                                     
                                                                                     
     *note assertIsNot(a, b): cd5.                 ‘a is not b’                      3.1
                                                                                     
                                                                                     
     *note assertIsNone(x): cd2.                   ‘x is None’                       3.1
                                                                                     
                                                                                     
     *note assertIsNotNone(x): cd3.                ‘x is not None’                   3.1
                                                                                     
                                                                                     
     *note assertIn(a, b): cdd.                    ‘a in b’                          3.1
                                                                                     
                                                                                     
     *note assertNotIn(a, b): cde.                 ‘a not in b’                      3.1
                                                                                     
                                                                                     
     *note assertIsInstance(a, b): cd6.            ‘isinstance(a, b)’                3.2
                                                                                     
                                                                                     
     *note assertNotIsInstance(a, b): cd7.         ‘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: ccd.).  Note that the `msg' keyword argument can be
     passed to *note assertRaises(): abf, *note assertRaisesRegex():
     ac0, *note assertWarns(): ac1, *note assertWarnsRegex(): ac2. 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(): ce6. 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: 3340.).

          3.1 版更變: Added the automatic calling of type-specific
          equality function.

          3.2 版更變: *note assertMultiLineEqual(): cdc. 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(): 454.).  To check for the exact type, use *note
          assertIs(type(obj), cls): cd4.

          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): abf.             ‘fun(*args, **kwds)’ raises `exc'
                                                                   
                                                                                                              
     *note assertRaisesRegex(exc, r, fun, *args, **kwds): ac0.     ‘fun(*args, **kwds)’ raises `exc' and      3.1
                                                                   the message matches regex `r'              
                                                                   
                                                                                                              
     *note assertWarns(warn, fun, *args, **kwds): ac1.             ‘fun(*args, **kwds)’ raises `warn'         3.2
                                                                                                              
                                                                                                              
     *note assertWarnsRegex(warn, r, fun, *args, **kwds): ac2.     ‘fun(*args, **kwds)’ raises `warn' and     3.2
                                                                   the message matches regex `r'              
                                                                   
                                                                                                              
     *note assertLogs(logger, level): 90a.                         The ‘with’ block logs on `logger' with     3.4
                                                                   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(): abf.  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(): abf.
          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 版更變: Added the ability to use *note assertRaises():
          abf. as a context manager.

          3.2 版更變: Added the ‘exception’ attribute.

          3.3 版更變: Added the `msg' keyword argument when used as a
          context manager.

      -- 成員函式: assertRaisesRegex (exception, regex, callable, *args,
               **kwds)

      -- 成員函式: assertRaisesRegex (exception, regex, *, msg=None)

          Like *note assertRaises(): abf. 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(): bb7.  Examples:

               self.assertRaisesRegex(ValueError, "invalid literal for.*XYZ'$",
                                      int, 'XYZ')

          或是：

               with self.assertRaisesRegex(ValueError, 'literal'):
                  int('XYZ')

          3.1 版新加入: Added under the name ‘assertRaisesRegexp’.

          3.2 版更變: Renamed to *note assertRaisesRegex(): ac0.

          3.3 版更變: Added the `msg' keyword argument when used as a
          context manager.

      -- 成員函式: 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(): ac1.  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(): ac1.
          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 版更變: Added the `msg' keyword argument when used as a
          context manager.

      -- 成員函式: assertWarnsRegex (warning, regex, callable, *args,
               **kwds)

      -- 成員函式: assertWarnsRegex (warning, regex, *, msg=None)

          Like *note assertWarns(): ac1. 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(): bb7.
          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 版更變: Added the `msg' keyword argument when used as a
          context manager.

      -- 成員函式: 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: 3ac.
          object or a *note str: 335. 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
          ‘logging.ERROR’).  The default is ‘logging.INFO’.

          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: 90b. objects of the
               matching log messages.

           -- 屬性: output

               A list of *note str: 335. objects with the formatted
               output of matching messages.

          Example:

               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 版新加入.

     There are also other methods used to perform more specific checks,
     such as:

     Method                                      Checks that                          New in
                                                                                      
     ----------------------------------------------------------------------------------------------------
                                                                                      
     *note assertAlmostEqual(a, b): bbc.         ‘round(a-b, 7) == 0’
                                                 
                                                                                      
     *note assertNotAlmostEqual(a, b): bbd.      ‘round(a-b, 7) != 0’
                                                 
                                                                                      
     *note assertGreater(a, b): cd8.             ‘a > b’                              3.1
                                                                                      
                                                                                      
     *note assertGreaterEqual(a, b): cd9.        ‘a >= b’                             3.1
                                                                                      
                                                                                      
     *note assertLess(a, b): cda.                ‘a < b’                              3.1
                                                                                      
                                                                                      
     *note assertLessEqual(a, b): cdb.           ‘a <= b’                             3.1
                                                                                      
                                                                                      
     *note assertRegex(s, r): bb6.               ‘r.search(s)’                        3.1
                                                                                      
                                                                                      
     *note assertNotRegex(s, r): 3343.           ‘not r.search(s)’                    3.2
                                                                                      
                                                                                      
     *note assertCountEqual(a, b): bb4.          `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(): c72. 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:
          193.

          3.2 版更變: *note assertAlmostEqual(): bbc. automatically
          considers almost equal objects that compare equal.  *note
          assertNotAlmostEqual(): bbd. 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(): bb7.

          3.1 版新加入: Added under the name ‘assertRegexpMatches’.

          3.2 版更變: The method ‘assertRegexpMatches()’ has been
          renamed to *note assertRegex(): bb6.

          3.2 版新加入: *note assertNotRegex(): 3343.

          3.5 版新加入: The name ‘assertNotRegexpMatches’ is a
          deprecated alias for *note assertNotRegex(): 3343.

      -- 成員函式: 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(): bba. 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(): ce6.:

      -- 成員函式: addTypeEqualityFunc (typeobj, function)

          Registers a type-specific method called by *note
          assertEqual(): bba. 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(): bba. does.  It
          must raise *note self.failureException(msg): 3344. 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(): bba. 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): cdc.        strings                           3.1
                                                                                     
                                                                                     
     *note assertSequenceEqual(a, b): ce2.         sequences                         3.1
                                                                                     
                                                                                     
     *note assertListEqual(a, b): ce0.             lists                             3.1
                                                                                     
                                                                                     
     *note assertTupleEqual(a, b): ce1.            tuples                            3.1
                                                                                     
                                                                                     
     *note assertSetEqual(a, b): cdf.              sets or frozensets                3.1
                                                                                     
                                                                                     
     *note assertDictEqual(a, b): ce3.             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(): bba.

          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():
          bba, but it’s used to implement *note assertListEqual(): ce0.
          and *note assertTupleEqual(): ce1.

          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(): bba.

          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(): bba.

          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(): bba.

          3.1 版新加入.

     Finally the *note TestCase: 904. 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: 1033.

      -- 屬性: 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(): ce2. (including all the
          sequence comparison methods that delegate to it), *note
          assertDictEqual(): ce3. and *note assertMultiLineEqual(): cdc.

          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: 904. 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(): ac3. method).

          For *note TestCase: 904. instances, this will always be an
          instance of *note TestResult: ac4.; subclasses of *note
          TestCase: 904. 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:
          334a. in Python 3.2.

      -- 成員函式: addCleanup (function, *args, **kwargs)

          Add a function to be called after *note tearDown(): cd1. 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(): 2a3. when they are added.

          If *note setUp(): cd0. fails, meaning that *note tearDown():
          cd1. is not called, then any cleanup functions added will
          still be called.

          3.1 版新加入.

      -- 成員函式: doCleanups ()

          This method is called unconditionally after *note tearDown():
          cd1, or after *note setUp(): cd0. if *note setUp(): cd0.
          raises an exception.

          It is responsible for calling all the cleanup functions added
          by *note addCleanup(): 2a3.  If you need cleanup functions to
          be called `prior' to *note tearDown(): cd1. then you can call
          *note doCleanups(): ccf. yourself.

          *note doCleanups(): ccf. 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(): cce.
          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(): 24c. when they
          are added.

          If *note setUpClass(): 24d. fails, meaning that *note
          tearDownClass(): cce. is not called, then any cleanup
          functions added will still be called.

          3.8 版新加入.

      -- 成員函式: classmethod doClassCleanups ()

          This method is called unconditionally after *note
          tearDownClass(): cce, or after *note setUpClass(): 24d. if
          *note setUpClass(): 24d. raises an exception.

          It is responsible for calling all the cleanup functions added
          by *note addClassCleanup(): 24c.  If you need cleanup
          functions to be called `prior' to *note tearDownClass(): cce.
          then you can call *note doClassCleanups(): 334b. yourself.

          *note doClassCleanups(): 334b. 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: 904. and also
     accepts coroutines as test functions.

     3.8 版新加入.

      -- 成員函式: 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: 1033. or
          *note SkipTest: 908, 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: 1033. or *note
          SkipTest: 908, 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(): 334c. 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.

      -- 成員函式: run (result=None)

          Sets up a new event loop to run the test, collecting the
          result into the *note TestResult: ac4. 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(): 334f.’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: 904.
     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: 11c.-based test
     framework.

* Menu:

* Deprecated aliases::


File: python.info,  Node: Deprecated aliases,  Up: Test cases

5.26.4.11 Deprecated aliases
............................

For historical reasons, some of the *note TestCase: 904. methods had one
or more aliases that are now deprecated.  The following table lists the
correct names along with their deprecated aliases:

     Method Name                        Deprecated alias           Deprecated alias
                                                                   
     ------------------------------------------------------------------------------------------
                                                                   
     *note assertEqual(): bba.          failUnlessEqual            assertEquals
                                                                   
                                                                   
     *note assertNotEqual(): bbb.       failIfEqual                assertNotEquals
                                                                   
                                                                   
     *note assertTrue(): bb9.           failUnless                 assert_
                                                                   
                                                                   
     *note assertFalse(): ccc.          failIf
                                        
                                                                   
     *note assertRaises(): abf.         failUnlessRaises
                                        
                                                                   
     *note assertAlmostEqual(): bbc.    failUnlessAlmostEqual      assertAlmostEquals
                                                                   
                                                                   
     *note assertNotAlmostEqual(): bbd. failIfAlmostEqual          assertNotAlmostEquals
                                                                   
                                                                   
     *note assertRegex(): bb6.                                     assertRegexpMatches
                                                                   
                                                                   
     *note assertNotRegex(): 3343.                                 assertNotRegexpMatches
                                                                   
                                                                   
     *note assertRaisesRegex(): ac0.                               assertRaisesRegexp
                                                                   

     3.1 版後已棄用: The fail* aliases listed in the second column have
     been deprecated.

     3.2 版後已棄用: The assert* aliases listed in the third column have
     been deprecated.

     3.2 版後已棄用: ‘assertRegexpMatches’ and ‘assertRaisesRegexp’ have
     been renamed to *note assertRegex(): bb6. and *note
     assertRaisesRegex(): ac0.

     3.5 版後已棄用: The ‘assertNotRegexpMatches’ name is deprecated in
     favor of *note assertNotRegex(): 3343.


File: python.info,  Node: Grouping tests,  Next: Loading and running tests,  Prev: Test cases,  Up: Classes and functions

5.26.4.12 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: 6d3. 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: 6d3. objects behave much like *note TestCase: 904.
     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: 6d3. instances:

      -- 成員函式: addTest (test)

          Add a *note TestCase: 904. or *note TestSuite: 6d3. to the
          suite.

      -- 成員函式: addTests (tests)

          Add all the tests from an iterable of *note TestCase: 904. and
          *note TestSuite: 6d3. instances to this test suite.

          This is equivalent to iterating over `tests', calling *note
          addTest(): 3353. for each element.

     *note TestSuite: 6d3. shares the following methods with *note
     TestCase: 904.:

      -- 成員函式: 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(): ac3, *note TestSuite.run():
          3355. 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: 6d3. are always accessed
          by iteration.  Subclasses can lazily provide tests by
          overriding *note __iter__(): 967.  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():
          3355. must be the same for each call iteration.  After *note
          TestSuite.run(): 3355, 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: 6d3.
          accessed tests directly rather than through iteration, so
          overriding *note __iter__(): 967. wasn’t sufficient for
          providing tests.

          3.4 版更變: In earlier versions the *note TestSuite: 6d3. held
          references to each *note TestCase: 904. after *note
          TestSuite.run(): 3355.  Subclasses can restore that behavior
          by overriding ‘TestSuite._removeTestAtIndex()’.

     In the typical usage of a *note TestSuite: 6d3. object, the *note
     run(): 3355. 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.4.13 Loading and running tests
...................................

 -- 類別: unittest.TestLoader

     The *note TestLoader: 787. 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: 11c. module provides an
     instance that can be shared as *note unittest.defaultTestLoader:
     3359.  Using a subclass or instance, however, allows customization
     of some configurable properties.

     *note TestLoader: 787. 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 a 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: 787. objects have the following methods:

      -- 成員函式: loadTestsFromTestCase (testCaseClass)

          Return a suite of all test cases contained in the *note
          TestCase: 904.-derived ‘testCaseClass’.

          A test case instance is created for each method named by *note
          getTestCaseNames(): 335b.  By default these are the method
          names beginning with ‘test’.  If *note getTestCaseNames():
          335b. 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: 904. and creates an instance of the class
          for each test method defined for the class.

               備註: While using a hierarchy of *note TestCase:
               904.-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: 332e.  The
          `pattern' argument is passed as the third argument to
          ‘load_tests’.

          3.2 版更變: Support for ‘load_tests’ added.

          3.5 版更變: The undocumented and unofficial `use_load_tests'
          default argument is deprecated and ignored, although it is
          still accepted for backward compatibility.  The method also
          now accepts a keyword-only argument `pattern' which is passed
          to ‘load_tests’ as the third argument.

      -- 成員函式: 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: 6d3. instance, or a
          callable object which returns a *note TestCase: 904. or *note
          TestSuite: 6d3. 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: 904.-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: 339. or *note
          AttributeError: 3a0. 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(): ce4, 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:
          904.

      -- 成員函式: 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 the top level directory 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: 908. 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 so ‘load_tests’ does not need to
          pass this argument in to ‘loader.discover()’.

          `start_dir' can be a dotted module name as well as a
          directory.

          3.2 版新加入.

          3.4 版更變: Modules that raise *note SkipTest: 908. on import
          are recorded as skips, not errors.

          3.4 版更變: `start_dir' can be a *note namespace packages:
          14b8.

          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.

     The following attributes of a *note TestLoader: 787. 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(): 335b. and all the
          ‘loadTestsFrom*()’ methods.

      -- 屬性: sortTestMethodsUsing

          Function to be used to compare method names when sorting them
          in *note getTestCaseNames(): 335b. 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: 6d3. 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 ‘-v’
          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(): 1c82, so unlike patterns
          passed to the ‘-v’ 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: ac4. object stores the results of a set of
     tests.  The *note TestCase: 904. and *note TestSuite: 6d3. 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: 11c. may want
     access to the *note TestResult: ac4. object generated by running a
     set of tests for reporting purposes; a *note TestResult: ac4.
     instance is returned by the ‘TestRunner.run()’ method for this
     purpose.

     *note TestResult: ac4. 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: 904. 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: 904. instances
          and strings holding formatted tracebacks.  Each tuple
          represents a test where a failure was explicitly signalled
          using the ‘TestCase.assert*()’ methods.

      -- 屬性: skipped

          A list containing 2-tuples of *note TestCase: 904. instances
          and strings holding the reason for skipping the test.

          3.1 版新加入.

      -- 屬性: expectedFailures

          A list containing 2-tuples of *note TestCase: 904. instances
          and strings holding formatted tracebacks.  Each tuple
          represents an expected failure or error of the test case.

      -- 屬性: unexpectedSuccesses

          A list containing *note TestCase: 904. instances that were
          marked as expected failures, but succeeded.

      -- 屬性: shouldStop

          Set to ‘True’ when the execution of tests should stop by *note
          stop(): 3366.

      -- 屬性: 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(): 3369. and *note stopTest():
          336a. 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(): 3366. 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: 3364. from tests marked with the *note
          expectedFailure(): 3336. decorator.

      -- 成員函式: stop ()

          This method can be called to signal that the set of tests
          being run should be aborted by setting the *note shouldStop:
          3365. 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:
          336e. 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: ac4. 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(): c64.: ‘(type, value, traceback)’.

          The default implementation appends a tuple ‘(test,
          formatted_err)’ to the instance’s *note errors: 3360.
          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(): c64.:
          ‘(type, value, traceback)’.

          The default implementation appends a tuple ‘(test,
          formatted_err)’ to the instance’s *note failures: 3361.
          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: 3362. attribute.

      -- 成員函式: addExpectedFailure (test, err)

          Called when the test case `test' fails or errors, but was
          marked with the *note expectedFailure(): 3336. decorator.

          The default implementation appends a tuple ‘(test,
          formatted_err)’ to the instance’s *note expectedFailures:
          3363. 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(): 3336. decorator, but succeeded.

          The default implementation appends the test to the instance’s
          *note unexpectedSuccesses: 3364. 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: 904. instance describing the subtest.

          If `outcome' is *note None: 158, the subtest succeeded.
          Otherwise, it failed with an exception where `outcome' is a
          tuple of the form returned by *note sys.exc_info(): c64.:
          ‘(type, value, traceback)’.

          The default implementation does nothing when the outcome is a
          success, and records subtest failures as normal failures.

          3.4 版新加入.

 -- 類別: unittest.TextTestResult (stream, descriptions, verbosity)

     A concrete implementation of *note TestResult: ac4. used by the
     *note TextTestRunner: 336e.

     3.2 版新加入: This class was previously named ‘_TextTestResult’.
     The old name still exists as an alias but is deprecated.

 -- Data: unittest.defaultTestLoader

     Instance of the *note TestLoader: 787. class intended to be shared.
     If no customization of the *note TestLoader: 787. 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)

     A basic test runner implementation that outputs results to a
     stream.  If `stream' is ‘None’, the default, *note sys.stderr: 314.
     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: 279, *note
     PendingDeprecationWarning: 27a, *note ResourceWarning: 4d5. and
     *note ImportWarning: 5dd. even if they are *note ignored by
     default: 3376.  Deprecation warnings caused by *note deprecated
     unittest methods: bbe. are also special-cased and, when the warning
     filters are ‘'default'’ or ‘'always'’, they will appear only once
     per-module, in order to avoid too many warning messages.  This
     behavior can be overridden using Python’s ‘-Wd’ or ‘-Wa’ options
     (see *note Warning control: 1350.) and leaving `warnings' to
     ‘None’.

     3.2 版更變: Added the ‘warnings’ argument.

     3.2 版更變: The default stream is set to *note sys.stderr: 314. at
     instantiation time rather than import time.

     3.5 版更變: Added the tb_locals parameter.

      -- 成員函式: _makeResult ()

          This method returns the instance of ‘TestResult’ used by *note
          run(): 3378.  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: 334a. 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: 6d3.
          or *note TestCase: 904. instance.  A *note TestResult: ac4. is
          created by calling *note _makeResult(): 3377. 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: c00. 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(): ce7. with an exit code indicating success or failure of
     the tests run.

     The `testLoader' argument has to be a *note TestLoader: 787.
     instance, and defaults to *note defaultTestLoader: 3359.

     ‘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(): ce7.:

          >>> 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: 3325.

     The `warnings' argument specifies the *note warning filter: 1351.
     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: 1350.), otherwise it will be
     set to ‘'default'’.

     Calling ‘main’ actually returns an instance of the ‘TestProgram’
     class.  This stores the result of the tests run as the ‘result’
     attribute.

     3.1 版更變: The `exit' parameter was added.

     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.4.14 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(): 785. 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: 6d3.

`loader' is the instance of *note TestLoader: 787. 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: 904. 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(): 909, 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: 6d3. 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.4.15 Class and Module Fixtures
...................................

Class and module level fixtures are implemented in *note TestSuite: 6d3.
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: 904.) 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.4.16 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: 904. 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: 908. 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.4.17 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: 908. 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(): 24b. when they are added.

     If ‘setUpModule()’ fails, meaning that ‘tearDownModule()’ is not
     called, then any cleanup functions added will still be called.

     3.8 版新加入.

 -- 函式: 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
     ‘addCleanupModule()’.  If you need cleanup functions to be called
     `prior' to ‘tearDownModule()’ then you can call *note
     doModuleCleanups(): 337b. yourself.

     *note doModuleCleanups(): 337b. 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.4.18 Signal Handling
.........................

3.2 版新加入.

The *note -c/–catch: cc9. command-line option to unittest, along with
the ‘catchbreak’ parameter to *note unittest.main(): 907, 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: 198. 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: 24d8. handler.
If the ‘unittest’ handler is called but `isn’t' the installed *note
signal.SIGINT: 24d8. 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(): cca.
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: 24d8.
     is received (usually in response to the user pressing control-c)
     all registered results have *note stop(): 3366. called.

 -- 函式: unittest.registerResult (result)

     Register a *note TestResult: ac4. 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: ac4. 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(): 3366. 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 object library,  Next: unittest mock --- getting started,  Prev: unittest --- 單元測試框架,  Up: 開發工具

5.26.5 ‘unittest.mock’ — mock object library
--------------------------------------------

3.3 版新加入.

`Source code:' Lib/unittest/mock.py(1)

__________________________________________________________________

*note unittest.mock: 11d. is a library for testing in Python.  It allows
you to replace parts of your system under test with mock objects and
make assertions about how they have been used.

*note unittest.mock: 11d. provides a core *note Mock: 24a. class
removing the need to create a host of stubs throughout your test suite.
After performing an action, you can make assertions about which methods
/ attributes were used and arguments they were called with.  You can
also specify return values and set needed attributes in the normal way.

Additionally, mock provides a *note patch(): 78d. decorator that handles
patching module and class level attributes within the scope of a test,
along with *note sentinel: 40f. for creating unique objects.  See the
*note quick guide: 3381. for some examples of how to use *note Mock:
24a, *note MagicMock: 78a. and *note patch(): 78d.

Mock is very easy to use and is designed for use with *note unittest:
11c.  Mock is based on the ’action -> assertion’ pattern instead of
’record -> replay’ used by many mocking frameworks.

There is a backport of *note unittest.mock: 11d. for earlier versions of
Python, available as mock on PyPI(2).

* Menu:

* Quick Guide::
* The Mock Class::
* The patchers::
* MagicMock and magic method support::
* Helpers::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/unittest/mock.py

   (2) https://pypi.org/project/mock


File: python.info,  Node: Quick Guide,  Next: The Mock Class,  Up: unittest mock --- mock object library

5.26.5.1 Quick Guide
....................

*note Mock: 24a. and *note MagicMock: 78a. objects create all attributes
and methods as you access them and store details of how they have been
used.  You can configure them, to specify return values or limit what
attributes are available, and then make assertions about how they have
been used:

     >>> 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’ allows you to perform side effects, including raising an
exception when a mock is called:

     >>> 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 has many other ways you can configure it and control its behaviour.
For example the `spec' argument configures the mock to take its
specification from another object.  Attempting to access attributes or
methods on the mock that don’t exist on the spec will fail with an *note
AttributeError: 3a0.

The *note patch(): 78d. decorator / context manager makes it easy to
mock classes or objects in a module under test.  The object you specify
will be replaced with a mock (or other object) during the test and
restored when the test ends:

     >>> 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()

     備註: When you nest patch decorators the mocks are passed in to the
     decorated function in the same order they applied (the normal
     `Python' order that decorators are applied).  This means from the
     bottom up, so in the example above the mock for ‘module.ClassName1’
     is passed in first.

     With *note patch(): 78d. it matters that you patch objects in the
     namespace where they are looked up.  This is normally
     straightforward, but for a quick guide read *note where to patch:
     3382.

As well as a decorator *note patch(): 78d. can be used as a context
manager in a with statement:

     >>> 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)

There is also *note patch.dict(): fd4. for setting values in a
dictionary just during a scope and restoring the dictionary to its
original state when the test ends:

     >>> foo = {'key': 'value'}
     >>> original = foo.copy()
     >>> with patch.dict(foo, {'newkey': 'newvalue'}, clear=True):
     ...     assert foo == {'newkey': 'newvalue'}
     ...
     >>> assert foo == original

Mock supports the mocking of Python *note magic methods: 3383.  The
easiest way of using magic methods is with the *note MagicMock: 78a.
class.  It allows you to do things like:

     >>> mock = MagicMock()
     >>> mock.__str__.return_value = 'foobarbaz'
     >>> str(mock)
     'foobarbaz'
     >>> mock.__str__.assert_called_with()

Mock allows you to assign functions (or other Mock instances) to magic
methods and they will be called appropriately.  The *note MagicMock:
78a. class is just a Mock variant that has all of the magic methods
pre-created for you (well, all the useful ones anyway).

The following is an example of using magic methods with the ordinary
Mock class:

     >>> mock = Mock()
     >>> mock.__str__ = Mock(return_value='wheeeeee')
     >>> str(mock)
     'wheeeeee'

For ensuring that the mock objects in your tests have the same api as
the objects they are replacing, you can use *note auto-speccing: 3384.
Auto-speccing can be done through the `autospec' argument to patch, or
the *note create_autospec(): f4e. function.  Auto-speccing creates mock
objects that have the same attributes and methods as the objects they
are replacing, and any functions and methods (including constructors)
have the same call signature as the real object.

This ensures that your mocks will fail in the same way as your
production code if they are used incorrectly:

     >>> 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: <lambda>() takes exactly 3 arguments (1 given)

*note create_autospec(): f4e. can also be used on classes, where it
copies the signature of the ‘__init__’ method, and on callable objects
where it copies the signature of the ‘__call__’ method.


File: python.info,  Node: The Mock Class,  Next: The patchers,  Prev: Quick Guide,  Up: unittest mock --- mock object library

5.26.5.2 The Mock Class
.......................

*note Mock: 24a. is a flexible mock object intended to replace the use
of stubs and test doubles throughout your code.  Mocks are callable and
create attributes as new mocks when you access them (1).  Accessing the
same attribute will always return the same mock.  Mocks record how you
use them, allowing you to make assertions about what your code has done
to them.

*note MagicMock: 78a. is a subclass of *note Mock: 24a. with all the
magic methods pre-created and ready to use.  There are also non-callable
variants, useful when you are mocking out objects that aren’t callable:
*note NonCallableMock: 3386. and *note NonCallableMagicMock: 3387.

The *note patch(): 78d. decorators makes it easy to temporarily replace
classes in a particular module with a *note Mock: 24a. object.  By
default *note patch(): 78d. will create a *note MagicMock: 78a. for you.
You can specify an alternative class of *note Mock: 24a. using the
`new_callable' argument to *note patch(): 78d.

 -- 類別: unittest.mock.Mock (spec=None, side_effect=None,
          return_value=DEFAULT, wraps=None, name=None, spec_set=None,
          unsafe=False, **kwargs)

     Create a new *note Mock: 24a. object.  *note Mock: 24a. takes
     several optional arguments that specify the behaviour of the Mock
     object:

        * `spec': This can be either a list of strings or an existing
          object (a class or instance) that acts as the specification
          for the mock object.  If you pass in an object then a list of
          strings is formed by calling dir on the object (excluding
          unsupported magic attributes and methods).  Accessing any
          attribute not in this list will raise an *note AttributeError:
          3a0.

          If `spec' is an object (rather than a list of strings) then
          *note __class__: e0f. returns the class of the spec object.
          This allows mocks to pass *note isinstance(): 454. tests.

        * `spec_set': A stricter variant of `spec'.  If used, attempting
          to `set' or get an attribute on the mock that isn’t on the
          object passed as `spec_set' will raise an *note
          AttributeError: 3a0.

        * `side_effect': A function to be called whenever the Mock is
          called.  See the *note side_effect: 3388. attribute.  Useful
          for raising exceptions or dynamically changing return values.
          The function is called with the same arguments as the mock,
          and unless it returns *note DEFAULT: 3389, the return value of
          this function is used as the return value.

          Alternatively `side_effect' can be an exception class or
          instance.  In this case the exception will be raised when the
          mock is called.

          If `side_effect' is an iterable then each call to the mock
          will return the next value from the iterable.

          A `side_effect' can be cleared by setting it to ‘None’.

        * `return_value': The value returned when the mock is called.
          By default this is a new Mock (created on first access).  See
          the *note return_value: 338a. attribute.

        * `unsafe': By default if any attribute starts with `assert' or
          `assret' will raise an *note AttributeError: 3a0.  Passing
          ‘unsafe=True’ will allow access to these attributes.

          3.5 版新加入.

        * `wraps': Item for the mock object to wrap.  If `wraps' is not
          ‘None’ then calling the Mock will pass the call through to the
          wrapped object (returning the real result).  Attribute access
          on the mock will return a Mock object that wraps the
          corresponding attribute of the wrapped object (so attempting
          to access an attribute that doesn’t exist will raise an *note
          AttributeError: 3a0.).

          If the mock has an explicit `return_value' set then calls are
          not passed to the wrapped object and the `return_value' is
          returned instead.

        * `name': If the mock has a name then it will be used in the
          repr of the mock.  This can be useful for debugging.  The name
          is propagated to child mocks.

     Mocks can also be called with arbitrary keyword arguments.  These
     will be used to set attributes on the mock after it is created.
     See the *note configure_mock(): 338b. method for details.

      -- 成員函式: assert_called ()

          Assert that the mock was called at least once.

               >>> mock = Mock()
               >>> mock.method()
               <Mock name='mock.method()' id='...'>
               >>> mock.method.assert_called()

          3.6 版新加入.

      -- 成員函式: assert_called_once ()

          Assert that the mock was called exactly once.

               >>> 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.

          3.6 版新加入.

      -- 成員函式: assert_called_with (*args, **kwargs)

          This method is a convenient way of asserting that the last
          call has been made in a particular way:

               >>> 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)

          Assert that the mock was called exactly once and that that
          call was with the specified arguments.

               >>> 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.

      -- 成員函式: assert_any_call (*args, **kwargs)

          assert the mock has been called with the specified arguments.

          The assert passes if the mock has `ever' been called, unlike
          *note assert_called_with(): 1004. and *note
          assert_called_once_with(): 338c. that only pass if the call is
          the most recent one, and in the case of *note
          assert_called_once_with(): 338c. it must also be the only
          call.

               >>> 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)

          assert the mock has been called with the specified calls.  The
          *note mock_calls: 338f. list is checked for the calls.

          If `any_order' is false then the calls must be sequential.
          There can be extra calls before or after the specified calls.

          If `any_order' is true then the calls can be in any order, but
          they must all appear in *note mock_calls: 338f.

               >>> 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 ()

          Assert the mock was never called.

               >>> 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.

          3.5 版新加入.

      -- 成員函式: reset_mock (*, return_value=False, side_effect=False)

          The reset_mock method resets all the call attributes on a mock
          object:

               >>> mock = Mock(return_value=None)
               >>> mock('hello')
               >>> mock.called
               True
               >>> mock.reset_mock()
               >>> mock.called
               False

          3.6 版更變: Added two keyword only argument to the reset_mock
          function.

          This can be useful where you want to make a series of
          assertions that reuse the same object.  Note that *note
          reset_mock(): 5af. `doesn’t' clear the return value, *note
          side_effect: 3388. or any child attributes you have set using
          normal assignment by default.  In case you want to reset
          `return_value' or *note side_effect: 3388, then pass the
          corresponding parameter as ‘True’.  Child mocks and the return
          value mock (if any) are reset as well.

               備註: `return_value', and *note side_effect: 3388. are
               keyword only argument.

      -- 成員函式: mock_add_spec (spec, spec_set=False)

          Add a spec to a mock.  `spec' can either be an object or a
          list of strings.  Only attributes on the `spec' can be fetched
          as attributes from the mock.

          If `spec_set' is true then only attributes on the spec can be
          set.

      -- 成員函式: attach_mock (mock, attribute)

          Attach a mock as an attribute of this one, replacing its name
          and parent.  Calls to the attached mock will be recorded in
          the *note method_calls: 3392. and *note mock_calls: 338f.
          attributes of this one.

      -- 成員函式: configure_mock (**kwargs)

          Set attributes on the mock through keyword arguments.

          Attributes plus return values and side effects can be set on
          child mocks using standard dot notation and unpacking a
          dictionary in the method call:

               >>> 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

          The same thing can be achieved in the constructor call to
          mocks:

               >>> 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(): 338b. exists to make it easier to do
          configuration after the mock has been created.

      -- 成員函式: __dir__ ()

          *note Mock: 24a. objects limit the results of ‘dir(some_mock)’
          to useful results.  For mocks with a `spec' this includes all
          the permitted attributes for the mock.

          See *note FILTER_DIR: 3394. for what this filtering does, and
          how to switch it off.

      -- 成員函式: _get_child_mock (**kw)

          Create the child mocks for attributes and return value.  By
          default child mocks will be the same type as the parent.
          Subclasses of Mock may want to override this to customize the
          way child mocks are made.

          For non-callable mocks the callable variant will be used
          (rather than any custom subclass).

      -- 屬性: called

          A boolean representing whether or not the mock object has been
          called:

               >>> mock = Mock(return_value=None)
               >>> mock.called
               False
               >>> mock()
               >>> mock.called
               True

      -- 屬性: call_count

          An integer telling you how many times the mock object has been
          called:

               >>> mock = Mock(return_value=None)
               >>> mock.call_count
               0
               >>> mock()
               >>> mock()
               >>> mock.call_count
               2

      -- 屬性: return_value

          Set this to configure the value returned by calling the mock:

               >>> mock = Mock()
               >>> mock.return_value = 'fish'
               >>> mock()
               'fish'

          The default return value is a mock object and you can
          configure it in the normal way:

               >>> mock = Mock()
               >>> mock.return_value.attribute = sentinel.Attribute
               >>> mock.return_value()
               <Mock name='mock()()' id='...'>
               >>> mock.return_value.assert_called_with()

          *note return_value: 338a. can also be set in the constructor:

               >>> mock = Mock(return_value=3)
               >>> mock.return_value
               3
               >>> mock()
               3

      -- 屬性: side_effect

          This can either be a function to be called when the mock is
          called, an iterable or an exception (class or instance) to be
          raised.

          If you pass in a function it will be called with same
          arguments as the mock and unless the function returns the
          *note DEFAULT: 3389. singleton the call to the mock will then
          return whatever the function returns.  If the function returns
          *note DEFAULT: 3389. then the mock will return its normal
          value (from the *note return_value: 338a.).

          If you pass in an iterable, it is used to retrieve an iterator
          which must yield a value on every call.  This value can either
          be an exception instance to be raised, or a value to be
          returned from the call to the mock (*note DEFAULT: 3389.
          handling is identical to the function case).

          An example of a mock that raises an exception (to test
          exception handling of an API):

               >>> mock = Mock()
               >>> mock.side_effect = Exception('Boom!')
               >>> mock()
               Traceback (most recent call last):
                 ...
               Exception: Boom!

          Using *note side_effect: 3388. to return a sequence of values:

               >>> mock = Mock()
               >>> mock.side_effect = [3, 2, 1]
               >>> mock(), mock(), mock()
               (3, 2, 1)

          Using a callable:

               >>> mock = Mock(return_value=3)
               >>> def side_effect(*args, **kwargs):
               ...     return DEFAULT
               ...
               >>> mock.side_effect = side_effect
               >>> mock()
               3

          *note side_effect: 3388. can be set in the constructor.
          Here’s an example that adds one to the value the mock is
          called with and returns it:

               >>> side_effect = lambda value: value + 1
               >>> mock = Mock(side_effect=side_effect)
               >>> mock(3)
               4
               >>> mock(-8)
               -7

          Setting *note side_effect: 3388. to ‘None’ clears it:

               >>> m = Mock(side_effect=KeyError, return_value=3)
               >>> m()
               Traceback (most recent call last):
                ...
               KeyError
               >>> m.side_effect = None
               >>> m()
               3

      -- 屬性: call_args

          This is either ‘None’ (if the mock hasn’t been called), or the
          arguments that the mock was last called with.  This will be in
          the form of a tuple: the first member, which can also be
          accessed through the ‘args’ property, is any ordered arguments
          the mock was called with (or an empty tuple) and the second
          member, which can also be accessed through the ‘kwargs’
          property, is any keyword arguments (or an empty dictionary).

               >>> 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: f29, along with members of the lists *note
          call_args_list: 3398, *note method_calls: 3392. and *note
          mock_calls: 338f. are *note call: f7f. objects.  These are
          tuples, so they can be unpacked to get at the individual
          arguments and make more complex assertions.  See *note calls
          as tuples: 3399.

          3.8 版更變: Added ‘args’ and ‘kwargs’ properties.

      -- 屬性: call_args_list

          This is a list of all the calls made to the mock object in
          sequence (so the length of the list is the number of times it
          has been called).  Before any calls have been made it is an
          empty list.  The *note call: f7f. object can be used for
          conveniently constructing lists of calls to compare with *note
          call_args_list: 3398.

               >>> 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

          Members of *note call_args_list: 3398. are *note call: f7f.
          objects.  These can be unpacked as tuples to get at the
          individual arguments.  See *note calls as tuples: 3399.

      -- 屬性: method_calls

          As well as tracking calls to themselves, mocks also track
          calls to methods and attributes, and `their' methods and
          attributes:

               >>> 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()]

          Members of *note method_calls: 3392. are *note call: f7f.
          objects.  These can be unpacked as tuples to get at the
          individual arguments.  See *note calls as tuples: 3399.

      -- 屬性: mock_calls

          *note mock_calls: 338f. records `all' calls to the mock
          object, its methods, magic methods `and' return value mocks.

               >>> 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

          Members of *note mock_calls: 338f. are *note call: f7f.
          objects.  These can be unpacked as tuples to get at the
          individual arguments.  See *note calls as tuples: 3399.

               備註: The way *note mock_calls: 338f. are recorded means
               that where nested calls are made, the parameters of
               ancestor calls are not recorded and so will always
               compare equal:

                    >>> 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__

          Normally the *note __class__: 339a. attribute of an object
          will return its type.  For a mock object with a ‘spec’,
          ‘__class__’ returns the spec class instead.  This allows mock
          objects to pass *note isinstance(): 454. tests for the object
          they are replacing / masquerading as:

               >>> mock = Mock(spec=3)
               >>> isinstance(mock, int)
               True

          *note __class__: 339a. is assignable to, this allows a mock to
          pass an *note isinstance(): 454. check without forcing you to
          use a spec:

               >>> mock = Mock()
               >>> mock.__class__ = dict
               >>> isinstance(mock, dict)
               True

 -- 類別: unittest.mock.NonCallableMock (spec=None, wraps=None,
          name=None, spec_set=None, **kwargs)

     A non-callable version of *note Mock: 24a.  The constructor
     parameters have the same meaning of *note Mock: 24a, with the
     exception of `return_value' and `side_effect' which have no meaning
     on a non-callable mock.

Mock objects that use a class or an instance as a ‘spec’ or ‘spec_set’
are able to pass *note isinstance(): 454. tests:

     >>> mock = Mock(spec=SomeClass)
     >>> isinstance(mock, SomeClass)
     True
     >>> mock = Mock(spec_set=SomeClass())
     >>> isinstance(mock, SomeClass)
     True

The *note Mock: 24a. classes have support for mocking magic methods.
See *note magic methods: 3383. for the full details.

The mock classes and the *note patch(): 78d. decorators all take
arbitrary keyword arguments for configuration.  For the *note patch():
78d. decorators the keywords are passed to the constructor of the mock
being created.  The keyword arguments are for configuring attributes of
the mock:

     >>> m = MagicMock(attribute=3, other='fish')
     >>> m.attribute
     3
     >>> m.other
     'fish'

The return value and side effect of child mocks can be set in the same
way, using dotted notation.  As you can’t use dotted names directly in a
call you have to create a dictionary and unpack it using ‘**’:

     >>> 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

A callable mock which was created with a `spec' (or a `spec_set') will
introspect the specification object’s signature when matching calls to
the mock.  Therefore, it can match the actual call’s arguments
regardless of whether they were passed positionally or by name:

     >>> 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)

This applies to *note assert_called_with(): 1004, *note
assert_called_once_with(): 338c, *note assert_has_calls(): 338e. and
*note assert_any_call(): 338d.  When *note Autospeccing: 3384, it will
also apply to method calls on the mock object.

     3.4 版更變: Added signature introspection on specced and
     autospecced mock objects.

 -- 類別: unittest.mock.PropertyMock (*args, **kwargs)

     A mock intended to be used as a property, or other descriptor, on a
     class.  *note PropertyMock: 339b. provides *note __get__(): 1440.
     and *note __set__(): 1444. methods so you can specify a return
     value when it is fetched.

     Fetching a *note PropertyMock: 339b. instance from an object calls
     the mock, with no args.  Setting it calls the mock with the value
     being set.

          >>> 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)]

Because of the way mock attributes are stored you can’t directly attach
a *note PropertyMock: 339b. to a mock object.  Instead you can attach it
to the mock type object:

     >>> m = MagicMock()
     >>> p = PropertyMock(return_value=3)
     >>> type(m).foo = p
     >>> m.foo
     3
     >>> p.assert_called_once_with()

 -- 類別: unittest.mock.AsyncMock (spec=None, side_effect=None,
          return_value=DEFAULT, wraps=None, name=None, spec_set=None,
          unsafe=False, **kwargs)

     An asynchronous version of *note Mock: 24a.  The *note AsyncMock:
     249. object will behave so the object is recognized as an async
     function, and the result of a call is an awaitable.

          >>> mock = AsyncMock()
          >>> asyncio.iscoroutinefunction(mock)
          True
          >>> inspect.isawaitable(mock())
          True

     The result of ‘mock()’ is an async function which will have the
     outcome of ‘side_effect’ or ‘return_value’ after it has been
     awaited:

        - if ‘side_effect’ is a function, the async function will return
          the result of that function,

        - if ‘side_effect’ is an exception, the async function will
          raise the exception,

        - if ‘side_effect’ is an iterable, the async function will
          return the next value of the iterable, however, if the
          sequence of result is exhausted, ‘StopAsyncIteration’ is
          raised immediately,

        - if ‘side_effect’ is not defined, the async function will
          return the value defined by ‘return_value’, hence, by default,
          the async function returns a new *note AsyncMock: 249. object.

     Setting the `spec' of a *note Mock: 24a. or *note MagicMock: 78a.
     to an async function will result in a coroutine object being
     returned after calling.

          >>> async def async_func(): pass
          ...
          >>> mock = MagicMock(async_func)
          >>> mock
          <MagicMock spec='function' id='...'>
          >>> mock()
          <coroutine object AsyncMockMixin._mock_call at ...>

     Setting the `spec' of a *note Mock: 24a, *note MagicMock: 78a, or
     *note AsyncMock: 249. to a class with asynchronous and synchronous
     functions will automatically detect the synchronous functions and
     set them as *note MagicMock: 78a. (if the parent mock is *note
     AsyncMock: 249. or *note MagicMock: 78a.) or *note Mock: 24a. (if
     the parent mock is *note Mock: 24a.).  All asynchronous functions
     will be *note AsyncMock: 249.

          >>> 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 ()

          Assert that the mock was awaited at least once.  Note that
          this is separate from the object having been called, the
          ‘await’ keyword must be used:

               >>> 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 ()

          Assert that the mock was awaited exactly once.

               >>> mock = AsyncMock()
               >>> async def main():
               ...     await mock()
               ...
               >>> asyncio.run(main())
               >>> mock.assert_awaited_once()
               >>> asyncio.run(main())
               >>> mock.method.assert_awaited_once()
               Traceback (most recent call last):
               ...
               AssertionError: Expected mock to have been awaited once. Awaited 2 times.

      -- 成員函式: assert_awaited_with (*args, **kwargs)

          Assert that the last await was with the specified arguments.

               >>> 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 call not found.
               Expected: mock('other')
               Actual: mock('foo', bar='bar')

      -- 成員函式: assert_awaited_once_with (*args, **kwargs)

          Assert that the mock was awaited exactly once and with the
          specified arguments.

               >>> 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)

          Assert the mock has ever been awaited with the specified
          arguments.

               >>> 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)

          Assert the mock has been awaited with the specified calls.
          The *note await_args_list: f28. list is checked for the
          awaits.

          If `any_order' is false then the awaits must be sequential.
          There can be extra calls before or after the specified awaits.

          If `any_order' is true then the awaits can be in any order,
          but they must all appear in *note await_args_list: f28.

               >>> 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 ()

          Assert that the mock was never awaited.

               >>> mock = AsyncMock()
               >>> mock.assert_not_awaited()

      -- 成員函式: reset_mock (*args, **kwargs)

          See *note Mock.reset_mock(): 5af.  Also sets *note
          await_count: 33a4. to 0, *note await_args: 33a5. to None, and
          clears the *note await_args_list: f28.

      -- 屬性: await_count

          An integer keeping track of how many times the mock object has
          been awaited.

               >>> mock = AsyncMock()
               >>> async def main():
               ...     await mock()
               ...
               >>> asyncio.run(main())
               >>> mock.await_count
               1
               >>> asyncio.run(main())
               >>> mock.await_count
               2

      -- 屬性: await_args

          This is either ‘None’ (if the mock hasn’t been awaited), or
          the arguments that the mock was last awaited with.  Functions
          the same as *note Mock.call_args: f29.

               >>> 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

          This is a list of all the awaits made to the mock object in
          sequence (so the length of the list is the number of times it
          has been awaited).  Before any awaits have been made it is an
          empty list.

               >>> 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')]

* Menu:

* Calling::
* Deleting Attributes::
* Mock names and the name attribute::
* Attaching Mocks as Attributes::

   ---------- Footnotes ----------

   (1) (1) The only exceptions are magic methods and attributes (those
that have leading and trailing double underscores).  Mock doesn’t create
these but instead raises an *note AttributeError: 3a0.  This is because
the interpreter will often implicitly request these methods, and gets
`very' confused to get a new Mock object when it expects a magic method.
If you need magic method support see *note magic methods: 3383.


File: python.info,  Node: Calling,  Next: Deleting Attributes,  Up: The Mock Class

5.26.5.3 Calling
................

Mock objects are callable.  The call will return the value set as the
*note return_value: 338a. attribute.  The default return value is a new
Mock object; it is created the first time the return value is accessed
(either explicitly or by calling the Mock) - but it is stored and the
same one returned each time.

Calls made to the object will be recorded in the attributes like *note
call_args: f29. and *note call_args_list: 3398.

If *note side_effect: 3388. is set then it will be called after the call
has been recorded, so if ‘side_effect’ raises an exception the call is
still recorded.

The simplest way to make a mock raise an exception when called is to
make *note side_effect: 3388. an exception class or instance:

     >>> 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')]

If ‘side_effect’ is a function then whatever that function returns is
what calls to the mock return.  The ‘side_effect’ function is called
with the same arguments as the mock.  This allows you to vary the return
value of the call dynamically, based on the input:

     >>> 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)]

If you want the mock to still return the default return value (a new
mock), or any set return value, then there are two ways of doing this.
Either return ‘mock.return_value’ from inside ‘side_effect’, or return
*note DEFAULT: 3389.:

     >>> 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

To remove a ‘side_effect’, and return to the default behaviour, set the
‘side_effect’ to ‘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

The ‘side_effect’ can also be any iterable object.  Repeated calls to
the mock will return values from the iterable (until the iterable is
exhausted and a *note StopIteration: 48b. is raised):

     >>> m = MagicMock(side_effect=[1, 2, 3])
     >>> m()
     1
     >>> m()
     2
     >>> m()
     3
     >>> m()
     Traceback (most recent call last):
       ...
     StopIteration

If any members of the iterable are exceptions they will be raised
instead of returned:

     >>> iterable = (33, ValueError, 66)
     >>> m = MagicMock(side_effect=iterable)
     >>> m()
     33
     >>> m()
     Traceback (most recent call last):
      ...
     ValueError
     >>> m()
     66


File: python.info,  Node: Deleting Attributes,  Next: Mock names and the name attribute,  Prev: Calling,  Up: The Mock Class

5.26.5.4 Deleting Attributes
............................

Mock objects create attributes on demand.  This allows them to pretend
to be objects of any type.

You may want a mock object to return ‘False’ to a *note hasattr(): 44c.
call, or raise an *note AttributeError: 3a0. when an attribute is
fetched.  You can do this by providing an object as a ‘spec’ for a mock,
but that isn’t always convenient.

You "block" attributes by deleting them.  Once deleted, accessing an
attribute will raise an *note AttributeError: 3a0.

     >>> 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 names and the name attribute,  Next: Attaching Mocks as Attributes,  Prev: Deleting Attributes,  Up: The Mock Class

5.26.5.5 Mock names and the name attribute
..........................................

Since "name" is an argument to the *note Mock: 24a. constructor, if you
want your mock object to have a "name" attribute you can’t just pass it
in at creation time.  There are two alternatives.  One option is to use
*note configure_mock(): 338b.:

     >>> mock = MagicMock()
     >>> mock.configure_mock(name='my_name')
     >>> mock.name
     'my_name'

A simpler option is to simply set the "name" attribute after mock
creation:

     >>> mock = MagicMock()
     >>> mock.name = "foo"


File: python.info,  Node: Attaching Mocks as Attributes,  Prev: Mock names and the name attribute,  Up: The Mock Class

5.26.5.6 Attaching Mocks as Attributes
......................................

When you attach a mock as an attribute of another mock (or as the return
value) it becomes a "child" of that mock.  Calls to the child are
recorded in the *note method_calls: 3392. and *note mock_calls: 338f.
attributes of the parent.  This is useful for configuring child mocks
and then attaching them to the parent, or for attaching mocks to a
parent that records all calls to the children and allows you to make
assertions about the order of calls between mocks:

     >>> 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)]

The exception to this is if the mock has a name.  This allows you to
prevent the "parenting" if for some reason you don’t want it to happen.

     >>> 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
     []

Mocks created for you by *note patch(): 78d. are automatically given
names.  To attach mocks that have names to a parent you use the *note
attach_mock(): 3391. method:

     >>> 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: The patchers,  Next: MagicMock and magic method support,  Prev: The Mock Class,  Up: unittest mock --- mock object library

5.26.5.7 The patchers
.....................

The patch decorators are used for patching objects only within the scope
of the function they decorate.  They automatically handle the unpatching
for you, even if exceptions are raised.  All of these functions can also
be used in with statements or as class decorators.

* Menu:

* patch::
* patch.object: patch object.
* patch.dict: patch dict.
* patch.multiple: patch multiple.
* patch methods; start and stop: patch methods start and stop.
* patch builtins::
* TEST_PREFIX::
* Nesting Patch Decorators::
* Where to patch::
* Patching Descriptors and Proxy Objects::


File: python.info,  Node: patch,  Next: patch object,  Up: The patchers

5.26.5.8 patch
..............

     備註: *note patch(): 78d. is straightforward to use.  The key is to
     do the patching in the right namespace.  See the section *note
     where to patch: 33ad.

 -- 函式: unittest.mock.patch (target, new=DEFAULT, spec=None,
          create=False, spec_set=None, autospec=None, new_callable=None,
          **kwargs)

     *note patch(): 78d. acts as a function decorator, class decorator
     or a context manager.  Inside the body of the function or with
     statement, the `target' is patched with a `new' object.  When the
     function/with statement exits the patch is undone.

     If `new' is omitted, then the target is replaced with an *note
     AsyncMock: 249. if the patched object is an async function or a
     *note MagicMock: 78a. otherwise.  If *note patch(): 78d. is used as
     a decorator and `new' is omitted, the created mock is passed in as
     an extra argument to the decorated function.  If *note patch():
     78d. is used as a context manager the created mock is returned by
     the context manager.

     `target' should be a string in the form
     ‘'package.module.ClassName'’.  The `target' is imported and the
     specified object replaced with the `new' object, so the `target'
     must be importable from the environment you are calling *note
     patch(): 78d. from.  The target is imported when the decorated
     function is executed, not at decoration time.

     The `spec' and `spec_set' keyword arguments are passed to the *note
     MagicMock: 78a. if patch is creating one for you.

     In addition you can pass ‘spec=True’ or ‘spec_set=True’, which
     causes patch to pass in the object being mocked as the
     spec/spec_set object.

     `new_callable' allows you to specify a different class, or callable
     object, that will be called to create the `new' object.  By default
     *note AsyncMock: 249. is used for async functions and *note
     MagicMock: 78a. for the rest.

     A more powerful form of `spec' is `autospec'.  If you set
     ‘autospec=True’ then the mock will be created with a spec from the
     object being replaced.  All attributes of the mock will also have
     the spec of the corresponding attribute of the object being
     replaced.  Methods and functions being mocked will have their
     arguments checked and will raise a *note TypeError: 193. if they
     are called with the wrong signature.  For mocks replacing a class,
     their return value (the ’instance’) will have the same spec as the
     class.  See the *note create_autospec(): f4e. function and *note
     Autospeccing: 3384.

     Instead of ‘autospec=True’ you can pass ‘autospec=some_object’ to
     use an arbitrary object as the spec instead of the one being
     replaced.

     By default *note patch(): 78d. will fail to replace attributes that
     don’t exist.  If you pass in ‘create=True’, and the attribute
     doesn’t exist, patch will create the attribute for you when the
     patched function is called, and delete it again after the patched
     function has exited.  This is useful for writing tests against
     attributes that your production code creates at runtime.  It is off
     by default because it can be dangerous.  With it switched on you
     can write passing tests against APIs that don’t actually exist!

          備註: 
          3.5 版更變: If you are patching builtins in a module then you
          don’t need to pass ‘create=True’, it will be added by default.

     Patch can be used as a ‘TestCase’ class decorator.  It works by
     decorating each test method in the class.  This reduces the
     boilerplate code when your test methods share a common patchings
     set.  *note patch(): 78d. finds tests by looking for method names
     that start with ‘patch.TEST_PREFIX’.  By default this is ‘'test'’,
     which matches the way *note unittest: 11c. finds tests.  You can
     specify an alternative prefix by setting ‘patch.TEST_PREFIX’.

     Patch can be used as a context manager, with the with statement.
     Here the patching applies to the indented block after the with
     statement.  If you use "as" then the patched object will be bound
     to the name after the "as"; very useful if *note patch(): 78d. is
     creating a mock object for you.

     *note patch(): 78d. takes arbitrary keyword arguments.  These will
     be passed to the *note Mock: 24a. (or `new_callable') on
     construction.

     ‘patch.dict(...)’, ‘patch.multiple(...)’ and ‘patch.object(...)’
     are available for alternate use-cases.

*note patch(): 78d. as function decorator, creating the mock for you and
passing it into the decorated function:

     >>> @patch('__main__.SomeClass')
     ... def function(normal_argument, mock_class):
     ...     print(mock_class is SomeClass)
     ...
     >>> function(None)
     True

Patching a class replaces the class with a *note MagicMock: 78a.
`instance'.  If the class is instantiated in the code under test then it
will be the *note return_value: 338a. of the mock that will be used.

If the class is instantiated multiple times you could use *note
side_effect: 3388. to return a new mock each time.  Alternatively you
can set the `return_value' to be anything you want.

To configure return values on methods of `instances' on the patched
class you must do this on the ‘return_value’.  For example:

     >>> 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'
     ...

If you use `spec' or `spec_set' and *note patch(): 78d. is replacing a
`class', then the return value of the created mock will have the same
spec.

     >>> Original = Class
     >>> patcher = patch('__main__.Class', spec=True)
     >>> MockClass = patcher.start()
     >>> instance = MockClass()
     >>> assert isinstance(instance, Original)
     >>> patcher.stop()

The `new_callable' argument is useful where you want to use an
alternative class to the default *note MagicMock: 78a. for the created
mock.  For example, if you wanted a *note NonCallableMock: 3386. to be
used:

     >>> 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

Another use case might be to replace an object with an *note
io.StringIO: 832. instance:

     >>> 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()

When *note patch(): 78d. is creating a mock for you, it is common that
the first thing you need to do is to configure the mock.  Some of that
configuration can be done in the call to patch.  Any arbitrary keywords
you pass into the call will be used to set attributes on the created
mock:

     >>> patcher = patch('__main__.thing', first='one', second='two')
     >>> mock_thing = patcher.start()
     >>> mock_thing.first
     'one'
     >>> mock_thing.second
     'two'

As well as attributes on the created mock attributes, like the *note
return_value: 338a. and *note side_effect: 3388, of child mocks can also
be configured.  These aren’t syntactically valid to pass in directly as
keyword arguments, but a dictionary with these as keys can still be
expanded into a *note patch(): 78d. call using ‘**’:

     >>> 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

By default, attempting to patch a function in a module (or a method or
an attribute in a class) that does not exist will fail with *note
AttributeError: 3a0.:

     >>> @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'

but adding ‘create=True’ in the call to *note patch(): 78d. will make
the previous example work as expected:

     >>> @patch('sys.non_existing_attribute', 42, create=True)
     ... def test(mock_stdout):
     ...     assert sys.non_existing_attribute == 42
     ...
     >>> test()

3.8 版更變: *note patch(): 78d. now returns an *note AsyncMock: 249. if
the target is an async function.


File: python.info,  Node: patch object,  Next: patch dict,  Prev: patch,  Up: The patchers

5.26.5.9 patch.object
.....................

 -- 函式: patch.object (target, attribute, new=DEFAULT, spec=None,
          create=False, spec_set=None, autospec=None, new_callable=None,
          **kwargs)

     patch the named member (`attribute') on an object (`target') with a
     mock object.

     *note patch.object(): f64. can be used as a decorator, class
     decorator or a context manager.  Arguments `new', `spec', `create',
     `spec_set', `autospec' and `new_callable' have the same meaning as
     for *note patch(): 78d.  Like *note patch(): 78d, *note
     patch.object(): f64. takes arbitrary keyword arguments for
     configuring the mock object it creates.

     When used as a class decorator *note patch.object(): f64. honours
     ‘patch.TEST_PREFIX’ for choosing which methods to wrap.

You can either call *note patch.object(): f64. with three arguments or
two arguments.  The three argument form takes the object to be patched,
the attribute name and the object to replace the attribute with.

When calling with the two argument form you omit the replacement object,
and a mock is created for you and passed in as an extra argument to the
decorated function:

     >>> @patch.object(SomeClass, 'class_method')
     ... def test(mock_method):
     ...     SomeClass.class_method(3)
     ...     mock_method.assert_called_with(3)
     ...
     >>> test()

`spec', `create' and the other arguments to *note patch.object(): f64.
have the same meaning as they do for *note patch(): 78d.


File: python.info,  Node: patch dict,  Next: patch multiple,  Prev: patch object,  Up: The patchers

5.26.5.10 patch.dict
....................

 -- 函式: patch.dict (in_dict, values=(), clear=False, **kwargs)

     Patch a dictionary, or dictionary like object, and restore the
     dictionary to its original state after the test.

     `in_dict' can be a dictionary or a mapping like container.  If it
     is a mapping then it must at least support getting, setting and
     deleting items plus iterating over keys.

     `in_dict' can also be a string specifying the name of the
     dictionary, which will then be fetched by importing it.

     `values' can be a dictionary of values to set in the dictionary.
     `values' can also be an iterable of ‘(key, value)’ pairs.

     If `clear' is true then the dictionary will be cleared before the
     new values are set.

     *note patch.dict(): fd4. can also be called with arbitrary keyword
     arguments to set values in the dictionary.

     3.8 版更變: *note patch.dict(): fd4. now returns the patched
     dictionary when used as a context manager.

*note patch.dict(): fd4. can be used as a context manager, decorator or
class decorator:

     >>> foo = {}
     >>> @patch.dict(foo, {'newkey': 'newvalue'})
     ... def test():
     ...     assert foo == {'newkey': 'newvalue'}
     >>> test()
     >>> assert foo == {}

When used as a class decorator *note patch.dict(): fd4. honours
‘patch.TEST_PREFIX’ (default to ‘'test'’) for choosing which methods to
wrap:

     >>> 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')

If you want to use a different prefix for your test, you can inform the
patchers of the different prefix by setting ‘patch.TEST_PREFIX’.  For
more details about how to change the value of see *note TEST_PREFIX:
33b0.

*note patch.dict(): fd4. can be used to add members to a dictionary, or
simply let a test change a dictionary, and ensure the dictionary is
restored when the test ends.

     >>> 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

Keywords can be used in the *note patch.dict(): fd4. call to set values
in the dictionary:

     >>> mymodule = MagicMock()
     >>> mymodule.function.return_value = 'fish'
     >>> with patch.dict('sys.modules', mymodule=mymodule):
     ...     import mymodule
     ...     mymodule.function('some', 'args')
     ...
     'fish'

*note patch.dict(): fd4. can be used with dictionary like objects that
aren’t actually dictionaries.  At the very minimum they must support
item getting, setting, deleting and either iteration or membership test.
This corresponds to the magic methods *note __getitem__(): 27d, *note
__setitem__(): c67, *note __delitem__(): c68. and either *note
__iter__(): 514. or *note __contains__(): d2d.

     >>> 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 methods start and stop,  Prev: patch dict,  Up: The patchers

5.26.5.11 patch.multiple
........................

 -- 函式: patch.multiple (target, spec=None, create=False,
          spec_set=None, autospec=None, new_callable=None, **kwargs)

     Perform multiple patches in a single call.  It takes the object to
     be patched (either as an object or a string to fetch the object by
     importing) and keyword arguments for the patches:

          with patch.multiple(settings, FIRST_PATCH='one', SECOND_PATCH='two'):
              ...

     Use *note DEFAULT: 3389. as the value if you want *note
     patch.multiple(): 33b2. to create mocks for you.  In this case the
     created mocks are passed into a decorated function by keyword, and
     a dictionary is returned when *note patch.multiple(): 33b2. is used
     as a context manager.

     *note patch.multiple(): 33b2. can be used as a decorator, class
     decorator or a context manager.  The arguments `spec', `spec_set',
     `create', `autospec' and `new_callable' have the same meaning as
     for *note patch(): 78d.  These arguments will be applied to `all'
     patches done by *note patch.multiple(): 33b2.

     When used as a class decorator *note patch.multiple(): 33b2.
     honours ‘patch.TEST_PREFIX’ for choosing which methods to wrap.

If you want *note patch.multiple(): 33b2. to create mocks for you, then
you can use *note DEFAULT: 3389. as the value.  If you use *note
patch.multiple(): 33b2. as a decorator then the created mocks are passed
into the decorated function by keyword.

     >>> 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(): 33b2. can be nested with other ‘patch’
decorators, but put arguments passed by keyword `after' any of the
standard arguments created by *note patch(): 78d.:

     >>> @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()

If *note patch.multiple(): 33b2. is used as a context manager, the value
returned by the context manager is a dictionary where created mocks are
keyed by name:

     >>> 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 methods start and stop,  Next: patch builtins,  Prev: patch multiple,  Up: The patchers

5.26.5.12 patch methods: start and stop
.......................................

All the patchers have ‘start()’ and ‘stop()’ methods.  These make it
simpler to do patching in ‘setUp’ methods or where you want to do
multiple patches without nesting decorators or with statements.

To use them call *note patch(): 78d, *note patch.object(): f64. or *note
patch.dict(): fd4. as normal and keep a reference to the returned
‘patcher’ object.  You can then call ‘start()’ to put the patch in place
and ‘stop()’ to undo it.

If you are using *note patch(): 78d. to create a mock for you then it
will be returned by the call to ‘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

A typical use case for this might be for doing multiple patches in the
‘setUp’ method of a ‘TestCase’:

     >>> 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()

     警示: If you use this technique you must ensure that the patching
     is "undone" by calling ‘stop’.  This can be fiddlier than you might
     think, because if an exception is raised in the ‘setUp’ then
     ‘tearDown’ is not called.  *note unittest.TestCase.addCleanup():
     2a3. makes this easier:

          >>> 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
          ...

     As an added bonus you no longer need to keep a reference to the
     ‘patcher’ object.

It is also possible to stop all patches which have been started by using
*note patch.stopall(): 33b5.

 -- 函式: patch.stopall ()

     Stop all active patches.  Only stops patches started with ‘start’.


File: python.info,  Node: patch builtins,  Next: TEST_PREFIX,  Prev: patch methods start and stop,  Up: The patchers

5.26.5.13 patch builtins
........................

You can patch any builtins within a module.  The following example
patches builtin *note ord(): 142c.:

     >>> @patch('__main__.ord')
     ... def test(mock_ord):
     ...     mock_ord.return_value = 101
     ...     print(ord('c'))
     ...
     >>> test()
     101


File: python.info,  Node: TEST_PREFIX,  Next: Nesting Patch Decorators,  Prev: patch builtins,  Up: The patchers

5.26.5.14 TEST_PREFIX
.....................

All of the patchers can be used as class decorators.  When used in this
way they wrap every test method on the class.  The patchers recognise
methods that start with ‘'test'’ as being test methods.  This is the
same way that the *note unittest.TestLoader: 787. finds test methods by
default.

It is possible that you want to use a different prefix for your tests.
You can inform the patchers of the different prefix by setting
‘patch.TEST_PREFIX’:

     >>> 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: Nesting Patch Decorators,  Next: Where to patch,  Prev: TEST_PREFIX,  Up: The patchers

5.26.5.15 Nesting Patch Decorators
..................................

If you want to perform multiple patches then you can simply stack up the
decorators.

You can stack up multiple patch decorators using this pattern:

     >>> @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')

Note that the decorators are applied from the bottom upwards.  This is
the standard way that Python applies decorators.  The order of the
created mocks passed into your test function matches this order.


File: python.info,  Node: Where to patch,  Next: Patching Descriptors and Proxy Objects,  Prev: Nesting Patch Decorators,  Up: The patchers

5.26.5.16 Where to patch
........................

*note patch(): 78d. works by (temporarily) changing the object that a
`name' points to with another one.  There can be many names pointing to
any individual object, so for patching to work you must ensure that you
patch the name used by the system under test.

The basic principle is that you patch where an object is `looked up',
which is not necessarily the same place as where it is defined.  A
couple of examples will help to clarify this.

Imagine we have a project that we want to test with the following
structure:

     a.py
         -> Defines SomeClass

     b.py
         -> from a import SomeClass
         -> some_function instantiates SomeClass

Now we want to test ‘some_function’ but we want to mock out ‘SomeClass’
using *note patch(): 78d.  The problem is that when we import module b,
which we will have to do then it imports ‘SomeClass’ from module a.  If
we use *note patch(): 78d. to mock out ‘a.SomeClass’ then it will have
no effect on our test; module b already has a reference to the `real'
‘SomeClass’ and it looks like our patching had no effect.

The key is to patch out ‘SomeClass’ where it is used (or where it is
looked up).  In this case ‘some_function’ will actually look up
‘SomeClass’ in module b, where we have imported it.  The patching should
look like:

     @patch('b.SomeClass')

However, consider the alternative scenario where instead of ‘from a
import SomeClass’ module b does ‘import a’ and ‘some_function’ uses
‘a.SomeClass’.  Both of these import forms are common.  In this case the
class we want to patch is being looked up in the module and so we have
to patch ‘a.SomeClass’ instead:

     @patch('a.SomeClass')


File: python.info,  Node: Patching Descriptors and Proxy Objects,  Prev: Where to patch,  Up: The patchers

5.26.5.17 Patching Descriptors and Proxy Objects
................................................

Both *note patch: 33ac. and *note patch.object: 33ae. correctly patch
and restore descriptors: class methods, static methods and properties.
You should patch these on the `class' rather than an instance.  They
also work with `some' objects that proxy attribute access, like the
django settings object(1).

   ---------- Footnotes ----------

   (1) 
http://www.voidspace.org.uk/python/weblog/arch_d7_2010_12_04.shtml#e1198


File: python.info,  Node: MagicMock and magic method support,  Next: Helpers,  Prev: The patchers,  Up: unittest mock --- mock object library

5.26.5.18 MagicMock and magic method support
............................................

* Menu:

* Mocking Magic Methods::
* Magic Mock::


File: python.info,  Node: Mocking Magic Methods,  Next: Magic Mock,  Up: MagicMock and magic method support

5.26.5.19 Mocking Magic Methods
...............................

*note Mock: 24a. supports mocking the Python protocol methods, also
known as "magic methods".  This allows mock objects to replace
containers or other objects that implement Python protocols.

Because magic methods are looked up differently from normal methods (1),
this support has been specially implemented.  This means that only
specific magic methods are supported.  The supported list includes
`almost' all of them.  If there are any missing that you need please let
us know.

You mock magic methods by setting the method you are interested in to a
function or a mock instance.  If you are using a function then it `must'
take ‘self’ as the first argument (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)
     []

One use case for this is for mocking objects used as context managers in
a *note with: 6ee. statement:

     >>> 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)

Calls to magic methods do not appear in *note method_calls: 3392, but
they are recorded in *note mock_calls: 338f.

     備註: If you use the `spec' keyword argument to create a mock then
     attempting to set a magic method that isn’t in the spec will raise
     an *note AttributeError: 3a0.

The full list of supported magic methods is:

   * ‘__hash__’, ‘__sizeof__’, ‘__repr__’ and ‘__str__’

   * ‘__dir__’, ‘__format__’ and ‘__subclasses__’

   * ‘__round__’, ‘__floor__’, ‘__trunc__’ and ‘__ceil__’

   * Comparisons: ‘__lt__’, ‘__gt__’, ‘__le__’, ‘__ge__’, ‘__eq__’ and
     ‘__ne__’

   * Container methods: ‘__getitem__’, ‘__setitem__’, ‘__delitem__’,
     ‘__contains__’, ‘__len__’, ‘__iter__’, ‘__reversed__’ and
     ‘__missing__’

   * Context manager: ‘__enter__’, ‘__exit__’, ‘__aenter__’ and
     ‘__aexit__’

   * Unary numeric methods: ‘__neg__’, ‘__pos__’ and ‘__invert__’

   * The numeric methods (including right hand and in-place variants):
     ‘__add__’, ‘__sub__’, ‘__mul__’, ‘__matmul__’, ‘__div__’,
     ‘__truediv__’, ‘__floordiv__’, ‘__mod__’, ‘__divmod__’,
     ‘__lshift__’, ‘__rshift__’, ‘__and__’, ‘__xor__’, ‘__or__’, and
     ‘__pow__’

   * Numeric conversion methods: ‘__complex__’, ‘__int__’, ‘__float__’
     and ‘__index__’

   * Descriptor methods: ‘__get__’, ‘__set__’ and ‘__delete__’

   * Pickling: ‘__reduce__’, ‘__reduce_ex__’, ‘__getinitargs__’,
     ‘__getnewargs__’, ‘__getstate__’ and ‘__setstate__’

   * File system path representation: ‘__fspath__’

   * Asynchronous iteration methods: ‘__aiter__’ and ‘__anext__’

3.8 版更變: Added support for *note os.PathLike.__fspath__(): 4f1.

3.8 版更變: Added support for ‘__aenter__’, ‘__aexit__’, ‘__aiter__’ and
‘__anext__’.

The following methods exist but are `not' supported as they are either
in use by mock, can’t be set dynamically, or can cause problems:

   * ‘__getattr__’, ‘__setattr__’, ‘__init__’ and ‘__new__’

   * ‘__prepare__’, ‘__instancecheck__’, ‘__subclasscheck__’, ‘__del__’

   ---------- Footnotes ----------

   (1) (2) Magic methods `should' be looked up on the class rather than
the instance.  Different versions of Python are inconsistent about
applying this rule.  The supported protocol methods should work with all
supported versions of Python.

   (2) (3) The function is basically hooked up to the class, but each
‘Mock’ instance is kept isolated from the others.


File: python.info,  Node: Magic Mock,  Prev: Mocking Magic Methods,  Up: MagicMock and magic method support

5.26.5.20 Magic Mock
....................

There are two ‘MagicMock’ variants: *note MagicMock: 78a. and *note
NonCallableMagicMock: 3387.

 -- 類別: unittest.mock.MagicMock (*args, **kw)

     ‘MagicMock’ is a subclass of *note Mock: 24a. with default
     implementations of most of the magic methods.  You can use
     ‘MagicMock’ without having to configure the magic methods yourself.

     The constructor parameters have the same meaning as for *note Mock:
     24a.

     If you use the `spec' or `spec_set' arguments then `only' magic
     methods that exist in the spec will be created.

 -- 類別: unittest.mock.NonCallableMagicMock (*args, **kw)

     A non-callable version of *note MagicMock: 78a.

     The constructor parameters have the same meaning as for *note
     MagicMock: 78a, with the exception of `return_value' and
     `side_effect' which have no meaning on a non-callable mock.

The magic methods are setup with *note MagicMock: 78a. objects, so you
can configure them and use them in the usual way:

     >>> mock = MagicMock()
     >>> mock[3] = 'fish'
     >>> mock.__setitem__.assert_called_with(3, 'fish')
     >>> mock.__getitem__.return_value = 'result'
     >>> mock[2]
     'result'

By default many of the protocol methods are required to return objects
of a specific type.  These methods are preconfigured with a default
return value, so that they can be used without you having to do anything
if you aren’t interested in the return value.  You can still `set' the
return value manually if you want to change the default.

Methods and their defaults:

   * ‘__lt__’: ‘NotImplemented’

   * ‘__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__’: default hash for the mock

   * ‘__str__’: default str for the mock

   * ‘__sizeof__’: default sizeof for the mock

For example:

     >>> mock = MagicMock()
     >>> int(mock)
     1
     >>> len(mock)
     0
     >>> list(mock)
     []
     >>> object() in mock
     False

The two equality methods, *note __eq__(): 344. and *note __ne__(): e5b,
are special.  They do the default equality comparison on identity, using
the *note side_effect: 3388. attribute, unless you change their return
value to return something else:

     >>> MagicMock() == 3
     False
     >>> MagicMock() != 3
     True
     >>> mock = MagicMock()
     >>> mock.__eq__.return_value = True
     >>> mock == 3
     True

The return value of ‘MagicMock.__iter__()’ can be any iterable object
and isn’t required to be an iterator:

     >>> mock = MagicMock()
     >>> mock.__iter__.return_value = ['a', 'b', 'c']
     >>> list(mock)
     ['a', 'b', 'c']
     >>> list(mock)
     ['a', 'b', 'c']

If the return value `is' an iterator, then iterating over it once will
consume it and subsequent iterations will result in an empty list:

     >>> mock.__iter__.return_value = iter(['a', 'b', 'c'])
     >>> list(mock)
     ['a', 'b', 'c']
     >>> list(mock)
     []

‘MagicMock’ has all of the supported magic methods configured except for
some of the obscure and obsolete ones.  You can still set these up if
you want.

Magic methods that are supported but not setup by default in ‘MagicMock’
are:

   * ‘__subclasses__’

   * ‘__dir__’

   * ‘__format__’

   * ‘__get__’, ‘__set__’ and ‘__delete__’

   * ‘__reversed__’ and ‘__missing__’

   * ‘__reduce__’, ‘__reduce_ex__’, ‘__getinitargs__’, ‘__getnewargs__’,
     ‘__getstate__’ and ‘__setstate__’

   * ‘__getformat__’ and ‘__setformat__’


File: python.info,  Node: Helpers,  Prev: MagicMock and magic method support,  Up: unittest mock --- mock object library

5.26.5.21 Helpers
.................

* Menu:

* sentinel::
* DEFAULT::
* call::
* create_autospec::
* ANY::
* FILTER_DIR::
* mock_open::
* Autospeccing::
* Sealing mocks::


File: python.info,  Node: sentinel,  Next: DEFAULT,  Up: Helpers

5.26.5.22 sentinel
..................

 -- Data: unittest.mock.sentinel

     The ‘sentinel’ object provides a convenient way of providing unique
     objects for your tests.

     Attributes are created on demand when you access them by name.
     Accessing the same attribute will always return the same object.
     The objects returned have a sensible repr so that test failure
     messages are readable.

     3.7 版更變: The ‘sentinel’ attributes now preserve their identity
     when they are *note copied: 26. or *note pickled: cb.

Sometimes when testing you need to test that a specific object is passed
as an argument to another method, or returned.  It can be common to
create named sentinel objects to test this.  *note sentinel: 40f.
provides a convenient way of creating and testing the identity of
objects like this.

In this example we monkey patch ‘method’ to return
‘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
     >>> sentinel.some_object
     sentinel.some_object


File: python.info,  Node: DEFAULT,  Next: call,  Prev: sentinel,  Up: Helpers

5.26.5.23 DEFAULT
.................

 -- Data: unittest.mock.DEFAULT

     The *note DEFAULT: 3389. object is a pre-created sentinel (actually
     ‘sentinel.DEFAULT’).  It can be used by *note side_effect: 3388.
     functions to indicate that the normal return value should be used.


File: python.info,  Node: call,  Next: create_autospec,  Prev: DEFAULT,  Up: Helpers

5.26.5.24 call
..............

 -- 函式: unittest.mock.call (*args, **kwargs)

     *note call(): f7f. is a helper object for making simpler
     assertions, for comparing with *note call_args: f29, *note
     call_args_list: 3398, *note mock_calls: 338f. and *note
     method_calls: 3392.  *note call(): f7f. can also be used with *note
     assert_has_calls(): 338e.

          >>> 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 ()

     For a call object that represents multiple calls, *note
     call_list(): 33c2. returns a list of all the intermediate calls as
     well as the final call.

‘call_list’ is particularly useful for making assertions on "chained
calls".  A chained call is multiple calls on a single line of code.
This results in multiple entries in *note mock_calls: 338f. on a mock.
Manually constructing the sequence of calls can be tedious.

*note call_list(): 33c2. can construct the sequence of calls from the
same chained call:

     >>> 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
A ‘call’ object is either a tuple of (positional args, keyword args) or
(name, positional args, keyword args) depending on how it was
constructed.  When you construct them yourself this isn’t particularly
interesting, but the ‘call’ objects that are in the *note
Mock.call_args: f29, *note Mock.call_args_list: 3398. and *note
Mock.mock_calls: 338f. attributes can be introspected to get at the
individual arguments they contain.

The ‘call’ objects in *note Mock.call_args: f29. and *note
Mock.call_args_list: 3398. are two-tuples of (positional args, keyword
args) whereas the ‘call’ objects in *note Mock.mock_calls: 338f, along
with ones you construct yourself, are three-tuples of (name, positional
args, keyword args).

You can use their "tupleness" to pull out the individual arguments for
more complex introspection and assertions.  The positional arguments are
a tuple (an empty tuple if there are no positional arguments) and the
keyword arguments are a dictionary:

     >>> 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: Helpers

5.26.5.25 create_autospec
.........................

 -- 函式: unittest.mock.create_autospec (spec, spec_set=False,
          instance=False, **kwargs)

     Create a mock object using another object as a spec.  Attributes on
     the mock will use the corresponding attribute on the `spec' object
     as their spec.

     Functions or methods being mocked will have their arguments checked
     to ensure that they are called with the correct signature.

     If `spec_set' is ‘True’ then attempting to set attributes that
     don’t exist on the spec object will raise an *note AttributeError:
     3a0.

     If a class is used as a spec then the return value of the mock (the
     instance of the class) will have the same spec.  You can use a
     class as the spec for an instance object by passing
     ‘instance=True’.  The returned mock will only be callable if
     instances of the mock are callable.

     *note create_autospec(): f4e. also takes arbitrary keyword
     arguments that are passed to the constructor of the created mock.

See *note Autospeccing: 3384. for examples of how to use auto-speccing
with *note create_autospec(): f4e. and the `autospec' argument to *note
patch(): 78d.

3.8 版更變: *note create_autospec(): f4e. now returns an *note
AsyncMock: 249. if the target is an async function.


File: python.info,  Node: ANY,  Next: FILTER_DIR,  Prev: create_autospec,  Up: Helpers

5.26.5.26 ANY
.............

 -- Data: unittest.mock.ANY

Sometimes you may need to make assertions about `some' of the arguments
in a call to mock, but either not care about some of the arguments or
want to pull them individually out of *note call_args: f29. and make
more complex assertions on them.

To ignore certain arguments you can pass in objects that compare equal
to `everything'.  Calls to *note assert_called_with(): 1004. and *note
assert_called_once_with(): 338c. will then succeed no matter what was
passed in.

     >>> mock = Mock(return_value=None)
     >>> mock('foo', bar=object())
     >>> mock.assert_called_once_with('foo', bar=ANY)

*note ANY: 33c5. can also be used in comparisons with call lists like
*note mock_calls: 338f.:

     >>> m = MagicMock(return_value=None)
     >>> m(1)
     >>> m(1, 2)
     >>> m(object())
     >>> m.mock_calls == [call(1), call(1, 2), ANY]
     True


File: python.info,  Node: FILTER_DIR,  Next: mock_open,  Prev: ANY,  Up: Helpers

5.26.5.27 FILTER_DIR
....................

 -- Data: unittest.mock.FILTER_DIR

*note FILTER_DIR: 3394. is a module level variable that controls the way
mock objects respond to *note dir(): d38. (only for Python 2.6 or more
recent).  The default is ‘True’, which uses the filtering described
below, to only show useful members.  If you dislike this filtering, or
need to switch it off for diagnostic purposes, then set ‘mock.FILTER_DIR
= False’.

With filtering on, ‘dir(some_mock)’ shows only useful attributes and
will include any dynamically created attributes that wouldn’t normally
be shown.  If the mock was created with a `spec' (or `autospec' of
course) then all the attributes from the original are shown, even if
they haven’t been accessed yet:

     >>> 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',
      ...

Many of the not-very-useful (private to *note Mock: 24a. rather than the
thing being mocked) underscore and double underscore prefixed attributes
have been filtered from the result of calling *note dir(): d38. on a
*note Mock: 24a.  If you dislike this behaviour you can switch it off by
setting the module level switch *note FILTER_DIR: 3394.:

     >>> 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__',
      ...

Alternatively you can just use ‘vars(my_mock)’ (instance members) and
‘dir(type(my_mock))’ (type members) to bypass the filtering irrespective
of ‘mock.FILTER_DIR’.


File: python.info,  Node: mock_open,  Next: Autospeccing,  Prev: FILTER_DIR,  Up: Helpers

5.26.5.28 mock_open
...................

 -- 函式: unittest.mock.mock_open (mock=None, read_data=None)

     A helper function to create a mock to replace the use of *note
     open(): 4f5.  It works for *note open(): 4f5. called directly or
     used as a context manager.

     The `mock' argument is the mock object to configure.  If ‘None’
     (the default) then a *note MagicMock: 78a. will be created for you,
     with the API limited to methods or attributes available on standard
     file handles.

     `read_data' is a string for the ‘read()’, *note readline(): 1708,
     and *note readlines(): 1795. methods of the file handle to return.
     Calls to those methods will take data from `read_data' until it is
     depleted.  The mock of these methods is pretty simplistic: every
     time the `mock' is called, the `read_data' is rewound to the start.
     If you need more control over the data that you are feeding to the
     tested code you will need to customize this mock for yourself.
     When that is insufficient, one of the in-memory filesystem packages
     on PyPI(1) can offer a realistic filesystem for testing.

     3.4 版更變: Added *note readline(): 1708. and *note readlines():
     1795. support.  The mock of ‘read()’ changed to consume `read_data'
     rather than returning it on each call.

     3.5 版更變: `read_data' is now reset on each call to the `mock'.

     3.8 版更變: Added *note __iter__(): 514. to implementation so that
     iteration (such as in for loops) correctly consumes `read_data'.

Using *note open(): 4f5. as a context manager is a great way to ensure
your file handles are closed properly and is becoming common:

     with open('/some/path', 'w') as f:
         f.write('something')

The issue is that even if you mock out the call to *note open(): 4f5. it
is the `returned object' that is used as a context manager (and has
*note __enter__(): c9a. and *note __exit__(): c9b. called).

Mocking context managers with a *note MagicMock: 78a. is common enough
and fiddly enough that a helper function is useful.

     >>> 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')

And for reading files:

     >>> 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: Sealing mocks,  Prev: mock_open,  Up: Helpers

5.26.5.29 Autospeccing
......................

Autospeccing is based on the existing ‘spec’ feature of mock.  It limits
the api of mocks to the api of an original object (the spec), but it is
recursive (implemented lazily) so that attributes of mocks only have the
same api as the attributes of the spec.  In addition mocked functions /
methods have the same call signature as the original so they raise a
*note TypeError: 193. if they are called incorrectly.

Before I explain how auto-speccing works, here’s why it is needed.

*note Mock: 24a. is a very powerful and flexible object, but it suffers
from two flaws when used to mock out objects from a system under test.
One of these flaws is specific to the *note Mock: 24a. api and the other
is a more general problem with using mock objects.

First the problem specific to *note Mock: 24a.  *note Mock: 24a. has two
assert methods that are extremely handy: *note assert_called_with():
1004. and *note assert_called_once_with(): 338c.

     >>> mock = Mock(name='Thing', return_value=None)
     >>> mock(1, 2, 3)
     >>> mock.assert_called_once_with(1, 2, 3)
     >>> mock(1, 2, 3)
     >>> mock.assert_called_once_with(1, 2, 3)
     Traceback (most recent call last):
      ...
     AssertionError: Expected 'mock' to be called once. Called 2 times.

Because mocks auto-create attributes on demand, and allow you to call
them with arbitrary arguments, if you misspell one of these assert
methods then your assertion is gone:

     >>> mock = Mock(name='Thing', return_value=None)
     >>> mock(1, 2, 3)
     >>> mock.assret_called_once_with(4, 5, 6)

Your tests can pass silently and incorrectly because of the typo.

The second issue is more general to mocking.  If you refactor some of
your code, rename members and so on, any tests for code that is still
using the `old api' but uses mocks instead of the real objects will
still pass.  This means your tests can all pass even though your code is
broken.

Note that this is another reason why you need integration tests as well
as unit tests.  Testing everything in isolation is all fine and dandy,
but if you don’t test how your units are "wired together" there is still
lots of room for bugs that tests might have caught.

‘mock’ already provides a feature to help with this, called speccing.
If you use a class or instance as the ‘spec’ for a mock then you can
only access attributes on the mock that exist on the real class:

     >>> from urllib import request
     >>> mock = Mock(spec=request.Request)
     >>> mock.assret_called_with
     Traceback (most recent call last):
      ...
     AttributeError: Mock object has no attribute 'assret_called_with'

The spec only applies to the mock itself, so we still have the same
issue with any methods on the mock:

     >>> mock.has_data()
     <mock.Mock object at 0x...>
     >>> mock.has_data.assret_called_with()

Auto-speccing solves this problem.  You can either pass ‘autospec=True’
to *note patch(): 78d. / *note patch.object(): f64. or use the *note
create_autospec(): f4e. function to create a mock with a spec.  If you
use the ‘autospec=True’ argument to *note patch(): 78d. then the object
that is being replaced will be used as the spec object.  Because the
speccing is done "lazily" (the spec is created as attributes on the mock
are accessed) you can use it with very complex or deeply nested objects
(like modules that import modules that import modules) without a big
performance hit.

Here’s an example of it in use:

     >>> 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='...'>

You can see that ‘request.Request’ has a spec.  ‘request.Request’ takes
two arguments in the constructor (one of which is `self').  Here’s what
happens if we try to call it incorrectly:

     >>> req = request.Request()
     Traceback (most recent call last):
      ...
     TypeError: <lambda>() takes at least 2 arguments (1 given)

The spec also applies to instantiated classes (i.e.  the return value of
specced mocks):

     >>> req = request.Request('foo')
     >>> req
     <NonCallableMagicMock name='request.Request()' spec='Request' id='...'>

‘Request’ objects are not callable, so the return value of instantiating
our mocked out ‘request.Request’ is a non-callable mock.  With the spec
in place any typos in our asserts will raise the correct error:

     >>> req.add_header('spam', 'eggs')
     <MagicMock name='request.Request().add_header()' id='...'>
     >>> req.add_header.assret_called_with
     Traceback (most recent call last):
      ...
     AttributeError: Mock object has no attribute 'assret_called_with'
     >>> req.add_header.assert_called_with('spam', 'eggs')

In many cases you will just be able to add ‘autospec=True’ to your
existing *note patch(): 78d. calls and then be protected against bugs
due to typos and api changes.

As well as using `autospec' through *note patch(): 78d. there is a *note
create_autospec(): f4e. for creating autospecced mocks directly:

     >>> from urllib import request
     >>> mock_request = create_autospec(request)
     >>> mock_request.Request('foo', 'bar')
     <NonCallableMagicMock name='mock.Request()' spec='Request' id='...'>

This isn’t without caveats and limitations however, which is why it is
not the default behaviour.  In order to know what attributes are
available on the spec object, autospec has to introspect (access
attributes) the spec.  As you traverse attributes on the mock a
corresponding traversal of the original object is happening under the
hood.  If any of your specced objects have properties or descriptors
that can trigger code execution then you may not be able to use
autospec.  On the other hand it is much better to design your objects so
that introspection is safe (1).

A more serious problem is that it is common for instance attributes to
be created in the *note __init__(): d63. method and not to exist on the
class at all.  `autospec' can’t know about any dynamically created
attributes and restricts the api to visible attributes.

     >>> 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'

There are a few different ways of resolving this problem.  The easiest,
but not necessarily the least annoying, way is to simply set the
required attributes on the mock after creation.  Just because `autospec'
doesn’t allow you to fetch attributes that don’t exist on the spec it
doesn’t prevent you setting them:

     >>> with patch('__main__.Something', autospec=True):
     ...   thing = Something()
     ...   thing.a = 33
     ...

There is a more aggressive version of both `spec' and `autospec' that
`does' prevent you setting non-existent attributes.  This is useful if
you want to ensure your code only `sets' valid attributes too, but
obviously it prevents this particular scenario:

     >>> 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'

Probably the best way of solving the problem is to add class attributes
as default values for instance members initialised in *note __init__():
d63.  Note that if you are only setting default attributes in *note
__init__(): d63. then providing them via class attributes (shared
between instances of course) is faster too.  e.g.

     class Something:
         a = 33

This brings up another issue.  It is relatively common to provide a
default value of ‘None’ for members that will later be an object of a
different type.  ‘None’ would be useless as a spec because it wouldn’t
let you access `any' attributes or methods on it.  As ‘None’ is `never'
going to be useful as a spec, and probably indicates a member that will
normally of some other type, autospec doesn’t use a spec for members
that are set to ‘None’.  These will just be ordinary mocks (well -
MagicMocks):

     >>> class Something:
     ...     member = None
     ...
     >>> mock = create_autospec(Something)
     >>> mock.member.foo.bar.baz()
     <MagicMock name='mock.member.foo.bar.baz()' id='...'>

If modifying your production classes to add defaults isn’t to your
liking then there are more options.  One of these is simply to use an
instance as the spec rather than the class.  The other is to create a
subclass of the production class and add the defaults to the subclass
without affecting the production class.  Both of these require you to
use an alternative object as the spec.  Thankfully *note patch(): 78d.
supports this - you can simply pass the alternative object as the
`autospec' argument:

     >>> 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) (4) This only applies to classes or already instantiated objects.
Calling a mocked class to create a mock instance `does not' create a
real instance.  It is only attribute lookups - along with calls to *note
dir(): d38. - that are done.


File: python.info,  Node: Sealing mocks,  Prev: Autospeccing,  Up: Helpers

5.26.5.30 Sealing mocks
.......................

 -- 函式: unittest.mock.seal (mock)

     Seal will disable the automatic creation of mocks when accessing an
     attribute of the mock being sealed or any of its attributes that
     are already mocks recursively.

     If a mock instance with a name or a spec is assigned to an
     attribute it won’t be considered in the sealing chain.  This allows
     one to prevent seal from fixing part of the mock object.

          >>> 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: unittest mock --- getting started,  Next: 2to3 - 自動將 Python 2的程式碼轉成 Python 3,  Prev: unittest mock --- mock object library,  Up: 開發工具

5.26.6 ‘unittest.mock’ — getting started
----------------------------------------

3.3 版新加入.

* Menu:

* Using Mock::
* Patch Decorators::
* Further Examples::


File: python.info,  Node: Using Mock,  Next: Patch Decorators,  Up: unittest mock --- getting started

5.26.6.1 Using Mock
...................

* Menu:

* Mock Patching Methods::
* Mock for Method Calls on an Object::
* Mocking Classes::
* Naming your mocks::
* Tracking all Calls::
* Setting Return Values and Attributes::
* Raising exceptions with mocks::
* Side effect functions and iterables::
* Mocking asynchronous iterators::
* Mocking asynchronous context manager::
* Creating a Mock from an Existing Object::


File: python.info,  Node: Mock Patching Methods,  Next: Mock for Method Calls on an Object,  Up: Using Mock

5.26.6.2 Mock Patching Methods
..............................

Common uses for *note Mock: 24a. objects include:

   * Patching methods

   * Recording method calls on objects

You might want to replace a method on an object to check that it is
called with the correct arguments by another part of the system:

     >>> real = SomeClass()
     >>> real.method = MagicMock(name='method')
     >>> real.method(3, 4, 5, key='value')
     <MagicMock name='method()' id='...'>

Once our mock has been used (‘real.method’ in this example) it has
methods and attributes that allow you to make assertions about how it
has been used.

     備註: In most of these examples the *note Mock: 24a. and *note
     MagicMock: 78a. classes are interchangeable.  As the ‘MagicMock’ is
     the more capable class it makes a sensible one to use by default.

Once the mock has been called its *note called: 3396. attribute is set
to ‘True’.  More importantly we can use the *note assert_called_with():
1004. or *note assert_called_once_with(): 338c. method to check that it
was called with the correct arguments.

This example tests that calling ‘ProductionClass().method’ results in a
call to the ‘something’ method:

     >>> 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 for Method Calls on an Object,  Next: Mocking Classes,  Prev: Mock Patching Methods,  Up: Using Mock

5.26.6.3 Mock for Method Calls on an Object
...........................................

In the last example we patched a method directly on an object to check
that it was called correctly.  Another common use case is to pass an
object into a method (or some part of the system under test) and then
check that it is used in the correct way.

The simple ‘ProductionClass’ below has a ‘closer’ method.  If it is
called with an object then it calls ‘close’ on it.

     >>> class ProductionClass:
     ...     def closer(self, something):
     ...         something.close()
     ...

So to test it we need to pass in an object with a ‘close’ method and
check that it was called correctly.

     >>> real = ProductionClass()
     >>> mock = Mock()
     >>> real.closer(mock)
     >>> mock.close.assert_called_with()

We don’t have to do any work to provide the ’close’ method on our mock.
Accessing close creates it.  So, if ’close’ hasn’t already been called
then accessing it in the test will create it, but *note
assert_called_with(): 1004. will raise a failure exception.


File: python.info,  Node: Mocking Classes,  Next: Naming your mocks,  Prev: Mock for Method Calls on an Object,  Up: Using Mock

5.26.6.4 Mocking Classes
........................

A common use case is to mock out classes instantiated by your code under
test.  When you patch a class, then that class is replaced with a mock.
Instances are created by `calling the class'.  This means you access the
"mock instance" by looking at the return value of the mocked class.

In the example below we have a function ‘some_function’ that
instantiates ‘Foo’ and calls a method on it.  The call to *note patch():
78d. replaces the class ‘Foo’ with a mock.  The ‘Foo’ instance is the
result of calling the mock, so it is configured by modifying the mock
*note return_value: 338a.

     >>> 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: Naming your mocks,  Next: Tracking all Calls,  Prev: Mocking Classes,  Up: Using Mock

5.26.6.5 Naming your mocks
..........................

It can be useful to give your mocks a name.  The name is shown in the
repr of the mock and can be helpful when the mock appears in test
failure messages.  The name is also propagated to attributes or methods
of the mock:

     >>> mock = MagicMock(name='foo')
     >>> mock
     <MagicMock name='foo' id='...'>
     >>> mock.method
     <MagicMock name='foo.method' id='...'>


File: python.info,  Node: Tracking all Calls,  Next: Setting Return Values and Attributes,  Prev: Naming your mocks,  Up: Using Mock

5.26.6.6 Tracking all Calls
...........................

Often you want to track more than a single call to a method.  The *note
mock_calls: 338f. attribute records all calls to child attributes of the
mock - and also to their children.

     >>> 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)]

If you make an assertion about ‘mock_calls’ and any unexpected methods
have been called, then the assertion will fail.  This is useful because
as well as asserting that the calls you expected have been made, you are
also checking that they were made in the right order and with no
additional calls:

You use the *note call: f7f. object to construct lists for comparing
with ‘mock_calls’:

     >>> expected = [call.method(), call.attribute.method(10, x=53)]
     >>> mock.mock_calls == expected
     True

However, parameters to calls that return mocks are not recorded, which
means it is not possible to track nested calls where the parameters used
to create ancestors are 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: Setting Return Values and Attributes,  Next: Raising exceptions with mocks,  Prev: Tracking all Calls,  Up: Using Mock

5.26.6.7 Setting Return Values and Attributes
.............................................

Setting the return values on a mock object is trivially easy:

     >>> mock = Mock()
     >>> mock.return_value = 3
     >>> mock()
     3

Of course you can do the same for methods on the mock:

     >>> mock = Mock()
     >>> mock.method.return_value = 3
     >>> mock.method()
     3

The return value can also be set in the constructor:

     >>> mock = Mock(return_value=3)
     >>> mock()
     3

If you need an attribute setting on your mock, just do it:

     >>> mock = Mock()
     >>> mock.x = 3
     >>> mock.x
     3

Sometimes you want to mock up a more complex situation, like for example
‘mock.connection.cursor().execute("SELECT 1")’.  If we wanted this call
to return a list, then we have to configure the result of the nested
call.

We can use *note call: f7f. to construct the set of calls in a "chained
call" like this for easy assertion afterwards:

     >>> 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

It is the call to ‘.call_list()’ that turns our call object into a list
of calls representing the chained calls.


File: python.info,  Node: Raising exceptions with mocks,  Next: Side effect functions and iterables,  Prev: Setting Return Values and Attributes,  Up: Using Mock

5.26.6.8 Raising exceptions with mocks
......................................

A useful attribute is *note side_effect: 3388.  If you set this to an
exception class or instance then the exception will be raised when the
mock is called.

     >>> mock = Mock(side_effect=Exception('Boom!'))
     >>> mock()
     Traceback (most recent call last):
       ...
     Exception: Boom!


File: python.info,  Node: Side effect functions and iterables,  Next: Mocking asynchronous iterators,  Prev: Raising exceptions with mocks,  Up: Using Mock

5.26.6.9 Side effect functions and iterables
............................................

‘side_effect’ can also be set to a function or an iterable.  The use
case for ‘side_effect’ as an iterable is where your mock is going to be
called several times, and you want each call to return a different
value.  When you set ‘side_effect’ to an iterable every call to the mock
returns the next value from the iterable:

     >>> mock = MagicMock(side_effect=[4, 5, 6])
     >>> mock()
     4
     >>> mock()
     5
     >>> mock()
     6

For more advanced use cases, like dynamically varying the return values
depending on what the mock is called with, ‘side_effect’ can be a
function.  The function will be called with the same arguments as the
mock.  Whatever the function returns is what the call returns:

     >>> 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: Mocking asynchronous iterators,  Next: Mocking asynchronous context manager,  Prev: Side effect functions and iterables,  Up: Using Mock

5.26.6.10 Mocking asynchronous iterators
........................................

Since Python 3.8, ‘AsyncMock’ and ‘MagicMock’ have support to mock *note
Asynchronous Iterators: 64b. through ‘__aiter__’.  The *note
return_value: 338a. attribute of ‘__aiter__’ can be used to set the
return values to be used for iteration.

     >>> 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: Mocking asynchronous context manager,  Next: Creating a Mock from an Existing Object,  Prev: Mocking asynchronous iterators,  Up: Using Mock

5.26.6.11 Mocking asynchronous context manager
..............................................

Since Python 3.8, ‘AsyncMock’ and ‘MagicMock’ have support to mock *note
Asynchronous Context Managers: 149b. through ‘__aenter__’ and
‘__aexit__’.  By default, ‘__aenter__’ and ‘__aexit__’ are ‘AsyncMock’
instances that return an async function.

     >>> 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: Creating a Mock from an Existing Object,  Prev: Mocking asynchronous context manager,  Up: Using Mock

5.26.6.12 Creating a Mock from an Existing Object
.................................................

One problem with over use of mocking is that it couples your tests to
the implementation of your mocks rather than your real code.  Suppose
you have a class that implements ‘some_method’.  In a test for another
class, you provide a mock of this object that `also' provides
‘some_method’.  If later you refactor the first class, so that it no
longer has ‘some_method’ - then your tests will continue to pass even
though your code is now broken!

*note Mock: 24a. allows you to provide an object as a specification for
the mock, using the `spec' keyword argument.  Accessing methods /
attributes on the mock that don’t exist on your specification object
will immediately raise an attribute error.  If you change the
implementation of your specification, then tests that use that class
will start failing immediately without you having to instantiate the
class in those tests.

     >>> mock = Mock(spec=SomeClass)
     >>> mock.old_method()
     Traceback (most recent call last):
        ...
     AttributeError: object has no attribute 'old_method'

Using a specification also enables a smarter matching of calls made to
the mock, regardless of whether some parameters were passed as
positional or named arguments:

     >>> 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)

If you want this smarter matching to also work with method calls on the
mock, you can use *note auto-speccing: 3384.

If you want a stronger form of specification that prevents the setting
of arbitrary attributes as well as the getting of them then you can use
`spec_set' instead of `spec'.


File: python.info,  Node: Patch Decorators,  Next: Further Examples,  Prev: Using Mock,  Up: unittest mock --- getting started

5.26.6.13 Patch Decorators
..........................

     備註: With *note patch(): 78d. it matters that you patch objects in
     the namespace where they are looked up.  This is normally
     straightforward, but for a quick guide read *note where to patch:
     3382.

A common need in tests is to patch a class attribute or a module
attribute, for example patching a builtin or patching a class in a
module to test that it is instantiated.  Modules and classes are
effectively global, so patching on them has to be undone after the test
or the patch will persist into other tests and cause hard to diagnose
problems.

mock provides three convenient decorators for this: *note patch(): 78d,
*note patch.object(): f64. and *note patch.dict(): fd4.  ‘patch’ takes a
single string, of the form ‘package.module.Class.attribute’ to specify
the attribute you are patching.  It also optionally takes a value that
you want the attribute (or class or whatever) to be replaced with.
’patch.object’ takes an object and the name of the attribute you would
like patched, plus optionally the value to patch it with.

‘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()

If you are patching a module (including *note builtins: 13.) then use
*note patch(): 78d. instead of *note patch.object(): f64.:

     >>> 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"

The module name can be ’dotted’, in the form ‘package.module’ if needed:

     >>> @patch('package.module.ClassName.attribute', sentinel.attribute)
     ... def test():
     ...     from package.module import ClassName
     ...     assert ClassName.attribute == sentinel.attribute
     ...
     >>> test()

A nice pattern is to actually decorate test methods themselves:

     >>> 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

If you want to patch with a Mock, you can use *note patch(): 78d. with
only one argument (or *note patch.object(): f64. with two arguments).
The mock will be created for you and passed into the test function /
method:

     >>> 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()

You can stack up multiple patch decorators using this pattern:

     >>> 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()

When you nest patch decorators the mocks are passed in to the decorated
function in the same order they applied (the normal `Python' order that
decorators are applied).  This means from the bottom up, so in the
example above the mock for ‘test_module.ClassName2’ is passed in first.

There is also *note patch.dict(): fd4. for setting values in a
dictionary just during a scope and restoring the dictionary to its
original state when the test ends:

     >>> foo = {'key': 'value'}
     >>> original = foo.copy()
     >>> with patch.dict(foo, {'newkey': 'newvalue'}, clear=True):
     ...     assert foo == {'newkey': 'newvalue'}
     ...
     >>> assert foo == original

‘patch’, ‘patch.object’ and ‘patch.dict’ can all be used as context
managers.

Where you use *note patch(): 78d. to create a mock for you, you can get
a reference to the mock using the "as" form of the with statement:

     >>> 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)

As an alternative ‘patch’, ‘patch.object’ and ‘patch.dict’ can be used
as class decorators.  When used in this way it is the same as applying
the decorator individually to every method whose name starts with
"test".


File: python.info,  Node: Further Examples,  Prev: Patch Decorators,  Up: unittest mock --- getting started

5.26.6.14 Further Examples
..........................

Here are some more examples for some slightly more advanced scenarios.

* Menu:

* Mocking chained calls::
* Partial mocking::
* Mocking a Generator Method::
* Applying the same patch to every test method::
* Mocking Unbound Methods::
* Checking multiple calls with mock::
* Coping with mutable arguments::
* Nesting Patches::
* Mocking a dictionary with MagicMock::
* Mock subclasses and their attributes::
* Mocking imports with patch.dict: Mocking imports with patch dict.
* Tracking order of calls and less verbose call assertions::
* More complex argument matching::


File: python.info,  Node: Mocking chained calls,  Next: Partial mocking,  Up: Further Examples

5.26.6.15 Mocking chained calls
...............................

Mocking chained calls is actually straightforward with mock once you
understand the *note return_value: 338a. attribute.  When a mock is
called for the first time, or you fetch its ‘return_value’ before it has
been called, a new *note Mock: 24a. is created.

This means that you can see how the object returned from a call to a
mocked object has been used by interrogating the ‘return_value’ 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)

From here it is a simple step to configure and then make assertions
about chained calls.  Of course another alternative is writing your code
in a more testable way in the first place...

So, suppose we have some code that looks a little bit like this:

     >>> 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

Assuming that ‘BackendProvider’ is already well tested, how do we test
‘method()’?  Specifically, we want to test that the code section ‘# more
code’ uses the response object in the correct way.

As this chain of calls is made from an instance attribute we can monkey
patch the ‘backend’ attribute on a ‘Something’ instance.  In this
particular case we are only interested in the return value from the
final call to ‘start_call’ so we don’t have much configuration to do.
Let’s assume the object it returns is ’file-like’, so we’ll ensure that
our response object uses the builtin *note open(): 4f5. as its ‘spec’.

To do this we create a mock instance as our mock backend and create a
mock response object for it.  To set the response as the return value
for that final ‘start_call’ we could do this:

     mock_backend.get_endpoint.return_value.create_call.return_value.start_call.return_value = mock_response

We can do that in a slightly nicer way using the *note configure_mock():
338b. method to directly set the return value for us:

     >>> 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)

With these we monkey patch the "mock backend" in place and can make the
real call:

     >>> something.backend = mock_backend
     >>> something.method()

Using *note mock_calls: 338f. we can check the chained call with a
single assert.  A chained call is several calls in one line of code, so
there will be several entries in ‘mock_calls’.  We can use *note
call.call_list(): 33c2. to create this list of calls for us:

     >>> 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: Partial mocking,  Next: Mocking a Generator Method,  Prev: Mocking chained calls,  Up: Further Examples

5.26.6.16 Partial mocking
.........................

In some tests I wanted to mock out a call to *note
datetime.date.today(): 18ad. to return a known date, but I didn’t want
to prevent the code under test from creating new date objects.
Unfortunately *note datetime.date: 194. is written in C, and so I
couldn’t just monkey-patch out the static ‘date.today()’ method.

I found a simple way of doing this that involved effectively wrapping
the date class with a mock, but passing through calls to the constructor
to the real class (and returning real instances).

The *note patch decorator: 78d. is used here to mock out the ‘date’
class in the module under test.  The ‘side_effect’ attribute on the mock
date class is then set to a lambda function that returns a real date.
When the mock date class is called a real date will be constructed and
returned by ‘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)

Note that we don’t patch *note datetime.date: 194. globally, we patch
‘date’ in the module that `uses' it.  See *note where to patch: 3382.

When ‘date.today()’ is called a known date is returned, but calls to the
‘date(...)’ constructor still return normal dates.  Without this you can
find yourself having to calculate an expected result using exactly the
same algorithm as the code under test, which is a classic testing
anti-pattern.

Calls to the date constructor are recorded in the ‘mock_date’ attributes
(‘call_count’ and friends) which may also be useful for your tests.

An alternative way of dealing with mocking dates, or other builtin
classes, is discussed in this blog entry(1).

   ---------- Footnotes ----------

   (1) 
https://williambert.online/2011/07/how-to-unit-testing-in-django-with-mocking-and-patching/


File: python.info,  Node: Mocking a Generator Method,  Next: Applying the same patch to every test method,  Prev: Partial mocking,  Up: Further Examples

5.26.6.17 Mocking a Generator Method
....................................

A Python generator is a function or method that uses the *note yield:
190. statement to return a series of values when iterated over (1).

A generator method / function is called to return the generator object.
It is the generator object that is then iterated over.  The protocol
method for iteration is *note __iter__(): 162e, so we can mock this
using a *note MagicMock: 78a.

Here’s an example class with an "iter" method implemented as a
generator:

     >>> class Foo:
     ...     def iter(self):
     ...         for i in [1, 2, 3]:
     ...             yield i
     ...
     >>> foo = Foo()
     >>> list(foo.iter())
     [1, 2, 3]

How would we mock this class, and in particular its "iter" method?

To configure the values returned from the iteration (implicit in the
call to *note list: 263.), we need to configure the object returned by
the call to ‘foo.iter()’.

     >>> mock_foo = MagicMock()
     >>> mock_foo.iter.return_value = iter([1, 2, 3])
     >>> list(mock_foo.iter())
     [1, 2, 3]

   ---------- Footnotes ----------

   (1) (1) There are also generator expressions and more advanced uses
(http://www.dabeaz.com/coroutines/index.html) of generators, but we
aren’t concerned about them here.  A very good introduction to
generators and how powerful they are is: Generator Tricks for Systems
Programmers (http://www.dabeaz.com/generators/).


File: python.info,  Node: Applying the same patch to every test method,  Next: Mocking Unbound Methods,  Prev: Mocking a Generator Method,  Up: Further Examples

5.26.6.18 Applying the same patch to every test method
......................................................

If you want several patches in place for multiple test methods the
obvious way is to apply the patch decorators to every method.  This can
feel like unnecessary repetition.  For Python 2.6 or more recent you can
use *note patch(): 78d. (in all its various forms) as a class decorator.
This applies the patches to all test methods on the class.  A test
method is identified by methods whose names start with ‘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'

An alternative way of managing patches is to use the *note patch
methods; start and stop: 33b4.  These allow you to move the patching
into your ‘setUp’ and ‘tearDown’ methods.

     >>> 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()

If you use this technique you must ensure that the patching is "undone"
by calling ‘stop’.  This can be fiddlier than you might think, because
if an exception is raised in the setUp then tearDown is not called.
*note unittest.TestCase.addCleanup(): 2a3. makes this easier:

     >>> 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: Mocking Unbound Methods,  Next: Checking multiple calls with mock,  Prev: Applying the same patch to every test method,  Up: Further Examples

5.26.6.19 Mocking Unbound Methods
.................................

Whilst writing tests today I needed to patch an `unbound method'
(patching the method on the class rather than on the instance).  I
needed self to be passed in as the first argument because I want to make
asserts about which objects were calling this particular method.  The
issue is that you can’t patch with a mock for this, because if you
replace an unbound method with a mock it doesn’t become a bound method
when fetched from the instance, and so it doesn’t get self passed in.
The workaround is to patch the unbound method with a real function
instead.  The *note patch(): 78d. decorator makes it so simple to patch
out methods with a mock that having to create a real function becomes a
nuisance.

If you pass ‘autospec=True’ to patch then it does the patching with a
`real' function object.  This function object has the same signature as
the one it is replacing, but delegates to a mock under the hood.  You
still get your mock auto-created in exactly the same way as before.
What it means though, is that if you use it to patch out an unbound
method on a class the mocked function will be turned into a bound method
if it is fetched from an instance.  It will have ‘self’ passed in as the
first argument, which is exactly what I wanted:

     >>> 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)

If we don’t use ‘autospec=True’ then the unbound method is patched out
with a Mock instance instead, and isn’t called with ‘self’.


File: python.info,  Node: Checking multiple calls with mock,  Next: Coping with mutable arguments,  Prev: Mocking Unbound Methods,  Up: Further Examples

5.26.6.20 Checking multiple calls with mock
...........................................

mock has a nice API for making assertions about how your mock objects
are used.

     >>> mock = Mock()
     >>> mock.foo_bar.return_value = None
     >>> mock.foo_bar('baz', spam='eggs')
     >>> mock.foo_bar.assert_called_with('baz', spam='eggs')

If your mock is only being called once you can use the
‘assert_called_once_with()’ method that also asserts that the
‘call_count’ is one.

     >>> 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 to be called once. Called 2 times.

Both ‘assert_called_with’ and ‘assert_called_once_with’ make assertions
about the `most recent' call.  If your mock is going to be called
several times, and you want to make assertions about `all' those calls
you can use *note call_args_list: 3398.:

     >>> 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()]

The *note call: f7f. helper makes it easy to make assertions about these
calls.  You can build up a list of expected calls and compare it to
‘call_args_list’.  This looks remarkably similar to the repr of the
‘call_args_list’:

     >>> expected = [call(1, 2, 3), call(4, 5, 6), call()]
     >>> mock.call_args_list == expected
     True


File: python.info,  Node: Coping with mutable arguments,  Next: Nesting Patches,  Prev: Checking multiple calls with mock,  Up: Further Examples

5.26.6.21 Coping with mutable arguments
.......................................

Another situation is rare, but can bite you, is when your mock is called
with mutable arguments.  ‘call_args’ and ‘call_args_list’ store
`references' to the arguments.  If the arguments are mutated by the code
under test then you can no longer make assertions about what the values
were when the mock was called.

Here’s some example code that shows the problem.  Imagine the following
functions defined in ’mymodule’:

     def frob(val):
         pass

     def grob(val):
         "First frob and then clear val"
         frob(val)
         val.clear()

When we try to test that ‘grob’ calls ‘frob’ with the correct argument
look what happens:

     >>> 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(),), {})

One possibility would be for mock to copy the arguments you pass in.
This could then cause problems if you do assertions that rely on object
identity for equality.

Here’s one solution that uses the ‘side_effect’ functionality.  If you
provide a ‘side_effect’ function for a mock then ‘side_effect’ will be
called with the same args as the mock.  This gives us an opportunity to
copy the arguments and store them for later assertions.  In this example
I’m using `another' mock to store the arguments so that I can use the
mock methods for doing the assertion.  Again a helper function sets this
up for me.

     >>> 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’ is called with the mock that will be called.  It
returns a new mock that we do the assertion on.  The ‘side_effect’
function makes a copy of the args and calls our ‘new_mock’ with the
copy.

     備註: If your mock is only going to be used once there is an easier
     way of checking arguments at the point they are called.  You can
     simply do the checking inside a ‘side_effect’ function.

          >>> def side_effect(arg):
          ...     assert arg == {6}
          ...
          >>> mock = Mock(side_effect=side_effect)
          >>> mock({6})
          >>> mock(set())
          Traceback (most recent call last):
              ...
          AssertionError

An alternative approach is to create a subclass of *note Mock: 24a. or
*note MagicMock: 78a. that copies (using *note copy.deepcopy(): 3d1.)
the arguments.  Here’s an example implementation:

     >>> 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: mock({1})
     Actual call: mock(set())
     >>> c.foo
     <CopyingMock name='mock.foo' id='...'>

When you subclass ‘Mock’ or ‘MagicMock’ all dynamically created
attributes, and the ‘return_value’ will use your subclass automatically.
That means all children of a ‘CopyingMock’ will also have the type
‘CopyingMock’.


File: python.info,  Node: Nesting Patches,  Next: Mocking a dictionary with MagicMock,  Prev: Coping with mutable arguments,  Up: Further Examples

5.26.6.22 Nesting Patches
.........................

Using patch as a context manager is nice, but if you do multiple patches
you can end up with nested with statements indenting further and further
to the right:

     >>> 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

With unittest ‘cleanup’ functions and the *note patch methods; start and
stop: 33b4. we can achieve the same effect without the nested
indentation.  A simple helper method, ‘create_patch’, puts the patch in
place and returns the created mock for us:

     >>> 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: Mocking a dictionary with MagicMock,  Next: Mock subclasses and their attributes,  Prev: Nesting Patches,  Up: Further Examples

5.26.6.23 Mocking a dictionary with MagicMock
.............................................

You may want to mock a dictionary, or other container object, recording
all access to it whilst having it still behave like a dictionary.

We can do this with *note MagicMock: 78a, which will behave like a
dictionary, and using *note side_effect: 3388. to delegate dictionary
access to a real underlying dictionary that is under our control.

When the *note __getitem__(): 27d. and *note __setitem__(): c67. methods
of our ‘MagicMock’ are called (normal dictionary access) then
‘side_effect’ is called with the key (and in the case of ‘__setitem__’
the value too).  We can also control what is returned.

After the ‘MagicMock’ has been used we can use attributes like *note
call_args_list: 3398. to assert about how the dictionary was used:

     >>> 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

     備註: An alternative to using ‘MagicMock’ is to use ‘Mock’ and
     `only' provide the magic methods you specifically want:

          >>> mock = Mock()
          >>> mock.__getitem__ = Mock(side_effect=getitem)
          >>> mock.__setitem__ = Mock(side_effect=setitem)

     A `third' option is to use ‘MagicMock’ but passing in ‘dict’ as the
     `spec' (or `spec_set') argument so that the ‘MagicMock’ created
     only has dictionary magic methods available:

          >>> mock = MagicMock(spec_set=dict)
          >>> mock.__getitem__.side_effect = getitem
          >>> mock.__setitem__.side_effect = setitem

With these side effect functions in place, the ‘mock’ will behave like a
normal dictionary but recording the access.  It even raises a *note
KeyError: 2c8. if you try to access a key that doesn’t exist.

     >>> 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'

After it has been used you can make assertions about the access using
the normal mock methods and attributes:

     >>> 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 subclasses and their attributes,  Next: Mocking imports with patch dict,  Prev: Mocking a dictionary with MagicMock,  Up: Further Examples

5.26.6.24 Mock subclasses and their attributes
..............................................

There are various reasons why you might want to subclass *note Mock:
24a.  One reason might be to add helper methods.  Here’s a silly
example:

     >>> 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

The standard behaviour for ‘Mock’ instances is that attributes and the
return value mocks are of the same type as the mock they are accessed
on.  This ensures that ‘Mock’ attributes are ‘Mocks’ and ‘MagicMock’
attributes are ‘MagicMocks’ (1).  So if you’re subclassing to add helper
methods then they’ll also be available on the attributes and return
value mock of instances of your subclass.

     >>> 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

Sometimes this is inconvenient.  For example, one user(2) is subclassing
mock to created a Twisted adaptor(3).  Having this applied to attributes
too actually causes errors.

‘Mock’ (in all its flavours) uses a method called ‘_get_child_mock’ to
create these "sub-mocks" for attributes and return values.  You can
prevent your subclass being used for attributes by overriding this
method.  The signature is that it takes arbitrary keyword arguments
(‘**kwargs’) which are then passed onto the mock constructor:

     >>> 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) (2) An exception to this rule are the non-callable mocks.
Attributes use the callable variant because otherwise non-callable mocks
couldn’t have callable methods.

   (2) https://code.google.com/archive/p/mock/issues/105

   (3) 
https://twistedmatrix.com/documents/11.0.0/api/twisted.python.components.html


File: python.info,  Node: Mocking imports with patch dict,  Next: Tracking order of calls and less verbose call assertions,  Prev: Mock subclasses and their attributes,  Up: Further Examples

5.26.6.25 Mocking imports with patch.dict
.........................................

One situation where mocking can be hard is where you have a local import
inside a function.  These are harder to mock because they aren’t using
an object from the module namespace that we can patch out.

Generally local imports are to be avoided.  They are sometimes done to
prevent circular dependencies, for which there is `usually' a much
better way to solve the problem (refactor the code) or to prevent "up
front costs" by delaying the import.  This can also be solved in better
ways than an unconditional local import (store the module as a class or
module attribute and only do the import on first use).

That aside there is a way to use ‘mock’ to affect the results of an
import.  Importing fetches an `object' from the *note sys.modules: f2b.
dictionary.  Note that it fetches an `object', which need not be a
module.  Importing a module for the first time results in a module
object being put in ‘sys.modules’, so usually when you import something
you get a module back.  This need not be the case however.

This means you can use *note patch.dict(): fd4. to `temporarily' put a
mock in place in *note sys.modules: f2b.  Any imports whilst this patch
is active will fetch the mock.  When the patch is complete (the
decorated function exits, the with statement body is complete or
‘patcher.stop()’ is called) then whatever was there previously will be
restored safely.

Here’s an example that mocks out the ’fooble’ module.

     >>> 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()

As you can see the ‘import fooble’ succeeds, but on exit there is no
’fooble’ left in *note sys.modules: f2b.

This also works for the ‘from module import name’ form:

     >>> 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()

With slightly more work you can also mock package imports:

     >>> 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: Tracking order of calls and less verbose call assertions,  Next: More complex argument matching,  Prev: Mocking imports with patch dict,  Up: Further Examples

5.26.6.26 Tracking order of calls and less verbose call assertions
..................................................................

The *note Mock: 24a. class allows you to track the `order' of method
calls on your mock objects through the *note method_calls: 3392.
attribute.  This doesn’t allow you to track the order of calls between
separate mock objects, however we can use *note mock_calls: 338f. to
achieve the same effect.

Because mocks track calls to child mocks in ‘mock_calls’, and accessing
an arbitrary attribute of a mock creates a child mock, we can create our
separate mocks from a parent one.  Calls to those child mock will then
all be recorded, in order, in the ‘mock_calls’ of the parent:

     >>> 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()]

We can then assert about the calls, including the order, by comparing
with the ‘mock_calls’ attribute on the manager mock:

     >>> expected_calls = [call.foo.something(), call.bar.other.thing()]
     >>> manager.mock_calls == expected_calls
     True

If ‘patch’ is creating, and putting in place, your mocks then you can
attach them to a manager mock using the *note attach_mock(): 3391.
method.  After attaching calls will be recorded in ‘mock_calls’ of the
manager.

     >>> 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()]

If many calls have been made, but you’re only interested in a particular
sequence of them then an alternative is to use the *note
assert_has_calls(): 338e. method.  This takes a list of calls
(constructed with the *note call: f7f. object).  If that sequence of
calls are in *note mock_calls: 338f. then the assert succeeds.

     >>> 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)

Even though the chained call ‘m.one().two().three()’ aren’t the only
calls that have been made to the mock, the assert still succeeds.

Sometimes a mock may have several calls made to it, and you are only
interested in asserting about `some' of those calls.  You may not even
care about the order.  In this case you can pass ‘any_order=True’ to
‘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: More complex argument matching,  Prev: Tracking order of calls and less verbose call assertions,  Up: Further Examples

5.26.6.27 More complex argument matching
........................................

Using the same basic concept as *note ANY: 33c5. we can implement
matchers to do more complex assertions on objects used as arguments to
mocks.

Suppose we expect some object to be passed to a mock that by default
compares equal based on object identity (which is the Python default for
user defined classes).  To use *note assert_called_with(): 1004. we
would need to pass in the exact same object.  If we are only interested
in some of the attributes of this object then we can create a matcher
that will check these attributes for us.

You can see in this example how a ’standard’ call to
‘assert_called_with’ isn’t sufficient:

     >>> 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(<__main__.Foo object at 0x...>)
     Actual call: call(<__main__.Foo object at 0x...>)

A comparison function for our ‘Foo’ class might look something like
this:

     >>> 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
     ...

And a matcher object that can use comparison functions like this for its
equality operation would look something like this:

     >>> 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)
     ...

Putting all this together:

     >>> match_foo = Matcher(compare, Foo(1, 2))
     >>> mock.assert_called_with(match_foo)

The ‘Matcher’ is instantiated with our compare function and the ‘Foo’
object we want to compare against.  In ‘assert_called_with’ the
‘Matcher’ equality method will be called, which compares the object the
mock was called with against the one we created our matcher with.  If
they match then ‘assert_called_with’ passes, and if they don’t an *note
AssertionError: 1033. is raised:

     >>> 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...>,), {})

With a bit of tweaking you could have the comparison function raise the
*note AssertionError: 1033. directly and provide a more useful failure
message.

As of version 1.5, the Python testing library PyHamcrest(1) provides
similar functionality, that may be useful here, in the form of its
equality matcher (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: 2to3 - 自動將 Python 2的程式碼轉成 Python 3,  Next: test --- Regression tests package for Python,  Prev: unittest mock --- getting started,  Up: 開發工具

5.26.7 2to3 - 自動將 Python 2的程式碼轉成 Python 3
--------------------------------------------------

2to3 is a Python program that reads Python 2.x source code and applies a
series of `fixers' to transform it into valid Python 3.x code.  The
standard library contains a rich set of fixers that will handle almost
all code.  2to3 supporting library *note lib2to3: a8. is, however, a
flexible and generic library, so it is possible to write your own fixers
for 2to3.  *note lib2to3: a8. could also be adapted to custom
applications in which Python code needs to be edited automatically.

* Menu:

* 使用 2to3::
* Fixers::
* lib2to3 - 2to3's library::


File: python.info,  Node: 使用 2to3,  Next: Fixers,  Up: 2to3 - 自動將 Python 2的程式碼轉成 Python 3

5.26.7.1 使用 2to3
..................

2to3 will usually be installed with the Python interpreter as a script.
It is also located in the ‘Tools/scripts’ directory of the Python root.

2to3’s basic arguments are a list of files or directories to transform.
The directories are recursively traversed for Python sources.

這邊有簡單的 Python 2的原始檔案 ‘example.py’:

     def greet(name):
         print "Hello, {0}!".format(name)
     print "What's your name?"
     name = raw_input()
     greet(name)

It can be converted to Python 3.x code via 2to3 on the command line:

     $ 2to3 example.py

A diff against the original source file is printed.  2to3 can also write
the needed modifications right back to the source file.  (A backup of
the original file is made unless ‘-n’ is also given.)  Writing the
changes back is enabled with the ‘-w’ flag:

     $ 2to3 -w example.py

After transformation, ‘example.py’ looks like this:

     def greet(name):
         print("Hello, {0}!".format(name))
     print("What's your name?")
     name = input()
     greet(name)

Comments and exact indentation are preserved throughout the translation
process.

By default, 2to3 runs a set of *note predefined fixers: 33ed.  The ‘-l’
flag lists all available fixers.  An explicit set of fixers to run can
be given with ‘-f’.  Likewise the ‘-x’ explicitly disables a fixer.  The
following example runs only the ‘imports’ and ‘has_key’ fixers:

     $ 2to3 -f imports -f has_key example.py

This command runs every fixer except the ‘apply’ fixer:

     $ 2to3 -x apply example.py

Some fixers are `explicit', meaning they aren’t run by default and must
be listed on the command line to be run.  Here, in addition to the
default fixers, the ‘idioms’ fixer is run:

     $ 2to3 -f all -f idioms example.py

Notice how passing ‘all’ enables all default fixers.

Sometimes 2to3 will find a place in your source code that needs to be
changed, but 2to3 cannot fix automatically.  In this case, 2to3 will
print a warning beneath the diff for a file.  You should address the
warning in order to have compliant 3.x code.

2to3 can also refactor doctests.  To enable this mode, use the ‘-d’
flag.  Note that `only' doctests will be refactored.  This also doesn’t
require the module to be valid Python.  For example, doctest like
examples in a reST document could also be refactored with this option.

The ‘-v’ option enables output of more information on the translation
process.

Since some print statements can be parsed as function calls or
statements, 2to3 cannot always read files containing the print function.
When 2to3 detects the presence of the ‘from __future__ import
print_function’ compiler directive, it modifies its internal grammar to
interpret *note print(): 88b. as a function.  This change can also be
enabled manually with the ‘-p’ flag.  Use ‘-p’ to run fixers on code
that already has had its print statements converted.

The ‘-o’ or ‘--output-dir’ option allows specification of an alternate
directory for processed output files to be written to.  The ‘-n’ flag is
required when using this as backup files do not make sense when not
overwriting the input files.

3.2.3 版新加入: The ‘-o’ option was added.

The ‘-W’ or ‘--write-unchanged-files’ flag tells 2to3 to always write
output files even if no changes were required to the file.  This is most
useful with ‘-o’ so that an entire Python source tree is copied with
translation from one directory to another.  This option implies the ‘-w’
flag as it would not make sense otherwise.

3.2.3 版新加入: The ‘-W’ flag was added.

The ‘--add-suffix’ option specifies a string to append to all output
filenames.  The ‘-n’ flag is required when specifying this as backups
are not necessary when writing to different filenames.  Example:

     $ 2to3 -n -W --add-suffix=3 example.py

Will cause a converted file named ‘example.py3’ to be written.

3.2.3 版新加入: The ‘--add-suffix’ option was added.

To translate an entire project from one directory tree to another use:

     $ 2to3 --output-dir=python3-version/mycode -W -n python2-version/mycode


File: python.info,  Node: Fixers,  Next: lib2to3 - 2to3's library,  Prev: 使用 2to3,  Up: 2to3 - 自動將 Python 2的程式碼轉成 Python 3

5.26.7.2 Fixers
...............

Each step of transforming code is encapsulated in a fixer.  The command
‘2to3 -l’ lists them.  As *note documented above: 33eb, each can be
turned on and off individually.  They are described here in more detail.

 -- 2to3fixer: apply

     Removes usage of ‘apply()’.  For example ‘apply(function, *args,
     **kwargs)’ is converted to ‘function(*args, **kwargs)’.

 -- 2to3fixer: asserts

     Replaces deprecated *note unittest: 11c. method names with the
     correct ones.

     從                                   到
                                          
     ------------------------------------------------------------------------------------
                                          
     ‘failUnlessEqual(a, b)’              *note assertEqual(a, b): bba.
                                          
                                          
     ‘assertEquals(a, b)’                 *note assertEqual(a, b): bba.
                                          
                                          
     ‘failIfEqual(a, b)’                  *note assertNotEqual(a, b): bbb.
                                          
                                          
     ‘assertNotEquals(a, b)’              *note assertNotEqual(a, b): bbb.
                                          
                                          
     ‘failUnless(a)’                      *note assertTrue(a): bb9.
                                          
                                          
     ‘assert_(a)’                         *note assertTrue(a): bb9.
                                          
                                          
     ‘failIf(a)’                          *note assertFalse(a): ccc.
                                          
                                          
     ‘failUnlessRaises(exc, cal)’         *note assertRaises(exc, cal): abf.
                                          
                                          
     ‘failUnlessAlmostEqual(a, b)’        *note assertAlmostEqual(a, b): bbc.
                                          
                                          
     ‘assertAlmostEquals(a, b)’           *note assertAlmostEqual(a, b): bbc.
                                          
                                          
     ‘failIfAlmostEqual(a, b)’            *note assertNotAlmostEqual(a, b): bbd.
                                          
                                          
     ‘assertNotAlmostEquals(a, b)’        *note assertNotAlmostEqual(a, b): bbd.
                                          

 -- 2to3fixer: basestring

     Converts ‘basestring’ to *note str: 335.

 -- 2to3fixer: buffer

     Converts ‘buffer’ to *note memoryview: 25d.  This fixer is optional
     because the *note memoryview: 25d. API is similar but not exactly
     the same as that of ‘buffer’.

 -- 2to3fixer: dict

     Fixes dictionary iteration methods.  ‘dict.iteritems()’ is
     converted to *note dict.items(): c30, ‘dict.iterkeys()’ to *note
     dict.keys(): c2f, and ‘dict.itervalues()’ to *note dict.values():
     c31.  Similarly, ‘dict.viewitems()’, ‘dict.viewkeys()’ and
     ‘dict.viewvalues()’ are converted respectively to *note
     dict.items(): c30, *note dict.keys(): c2f. and *note dict.values():
     c31.  It also wraps existing usages of *note dict.items(): c30,
     *note dict.keys(): c2f, and *note dict.values(): c31. in a call to
     *note list: 263.

 -- 2to3fixer: except

     Converts ‘except X, T’ to ‘except X as T’.

 -- 2to3fixer: exec

     Converts the ‘exec’ statement to the *note exec(): c49. function.

 -- 2to3fixer: execfile

     Removes usage of ‘execfile()’.  The argument to ‘execfile()’ is
     wrapped in calls to *note open(): 4f5, *note compile(): 1b5, and
     *note exec(): c49.

 -- 2to3fixer: exitfunc

     Changes assignment of ‘sys.exitfunc’ to use of the *note atexit: c.
     module.

 -- 2to3fixer: filter

     Wraps *note filter(): c33. usage in a *note list: 263. call.

 -- 2to3fixer: funcattrs

     Fixes function attributes that have been renamed.  For example,
     ‘my_function.func_closure’ is converted to
     ‘my_function.__closure__’.

 -- 2to3fixer: future

     Removes ‘from __future__ import new_feature’ statements.

 -- 2to3fixer: getcwdu

     Renames ‘os.getcwdu()’ to *note os.getcwd(): fe3.

 -- 2to3fixer: has_key

     Changes ‘dict.has_key(key)’ to ‘key in dict’.

 -- 2to3fixer: idioms

     This optional fixer performs several transformations that make
     Python code more idiomatic.  Type comparisons like ‘type(x) is
     SomeClass’ and ‘type(x) == SomeClass’ are converted to
     ‘isinstance(x, SomeClass)’.  ‘while 1’ becomes ‘while True’.  This
     fixer also tries to make use of *note sorted(): 449. in appropriate
     places.  For example, this block

          L = list(some_iterable)
          L.sort()

     is changed to

          L = sorted(some_iterable)

 -- 2to3fixer: import

     Detects sibling imports and converts them to relative imports.

 -- 2to3fixer: imports

     Handles module renames in the standard library.

 -- 2to3fixer: imports2

     Handles other modules renames in the standard library.  It is
     separate from the *note imports: 33fe. fixer only because of
     technical limitations.

 -- 2to3fixer: input

     Converts ‘input(prompt)’ to ‘eval(input(prompt))’.

 -- 2to3fixer: intern

     Converts ‘intern()’ to *note sys.intern(): c73.

 -- 2to3fixer: isinstance

     Fixes duplicate types in the second argument of *note isinstance():
     454.  For example, ‘isinstance(x, (int, int))’ is converted to
     ‘isinstance(x, int)’ and ‘isinstance(x, (int, float, int))’ is
     converted to ‘isinstance(x, (int, float))’.

 -- 2to3fixer: itertools_imports

     Removes imports of ‘itertools.ifilter()’, ‘itertools.izip()’, and
     ‘itertools.imap()’.  Imports of ‘itertools.ifilterfalse()’ are also
     changed to *note itertools.filterfalse(): 15f1.

 -- 2to3fixer: itertools

     Changes usage of ‘itertools.ifilter()’, ‘itertools.izip()’, and
     ‘itertools.imap()’ to their built-in equivalents.
     ‘itertools.ifilterfalse()’ is changed to *note
     itertools.filterfalse(): 15f1.

 -- 2to3fixer: long

     Renames ‘long’ to *note int: 185.

 -- 2to3fixer: map

     Wraps *note map(): c32. in a *note list: 263. call.  It also
     changes ‘map(None, x)’ to ‘list(x)’.  Using ‘from future_builtins
     import map’ disables this fixer.

 -- 2to3fixer: metaclass

     Converts the old metaclass syntax (‘__metaclass__ = Meta’ in the
     class body) to the new (‘class X(metaclass=Meta)’).

 -- 2to3fixer: methodattrs

     Fixes old method attribute names.  For example, ‘meth.im_func’ is
     converted to ‘meth.__func__’.

 -- 2to3fixer: ne

     Converts the old not-equal syntax, ‘<>’, to ‘!=’.

 -- 2to3fixer: next

     Converts the use of iterator’s ‘next()’ methods to the *note
     next(): 687. function.  It also renames *note next(): 687. methods
     to *note __next__(): c69.

 -- 2to3fixer: nonzero

     Renames ‘__nonzero__()’ to *note __bool__(): c6d.

 -- 2to3fixer: numliterals

     Converts octal literals into the new syntax.

 -- 2to3fixer: operator

     Converts calls to various functions in the *note operator: c3.
     module to other, but equivalent, function calls.  When needed, the
     appropriate ‘import’ statements are added, e.g.  ‘import
     collections.abc’.  The following mapping are made:

     從                                     到
                                            
     -----------------------------------------------------------------------------------------
                                            
     ‘operator.isCallable(obj)’             ‘callable(obj)’
                                            
                                            
     ‘operator.sequenceIncludes(obj)’       ‘operator.contains(obj)’
                                            
                                            
     ‘operator.isSequenceType(obj)’         ‘isinstance(obj, collections.abc.Sequence)’
                                            
                                            
     ‘operator.isMappingType(obj)’          ‘isinstance(obj, collections.abc.Mapping)’
                                            
                                            
     ‘operator.isNumberType(obj)’           ‘isinstance(obj, numbers.Number)’
                                            
                                            
     ‘operator.repeat(obj, n)’              ‘operator.mul(obj, n)’
                                            
                                            
     ‘operator.irepeat(obj, n)’             ‘operator.imul(obj, n)’
                                            

 -- 2to3fixer: paren

     Add extra parenthesis where they are required in list
     comprehensions.  For example, ‘[x for x in 1, 2]’ becomes ‘[x for x
     in (1, 2)]’.

 -- 2to3fixer: print

     Converts the ‘print’ statement to the *note print(): 88b. function.

 -- 2to3fixer: raise

     Converts ‘raise E, V’ to ‘raise E(V)’, and ‘raise E, V, T’ to
     ‘raise E(V).with_traceback(T)’.  If ‘E’ is a tuple, the translation
     will be incorrect because substituting tuples for exceptions has
     been removed in 3.0.

 -- 2to3fixer: raw_input

     Converts ‘raw_input()’ to *note input(): c70.

 -- 2to3fixer: reduce

     Handles the move of ‘reduce()’ to *note functools.reduce(): c74.

 -- 2to3fixer: reload

     Converts ‘reload()’ to *note importlib.reload(): 39e.

 -- 2to3fixer: renames

     Changes ‘sys.maxint’ to *note sys.maxsize: b48.

 -- 2to3fixer: repr

     Replaces backtick repr with the *note repr(): 7d1. function.

 -- 2to3fixer: set_literal

     Replaces use of the *note set: b74. constructor with set literals.
     This fixer is optional.

 -- 2to3fixer: standarderror

     Renames ‘StandardError’ to *note Exception: 1aa.

 -- 2to3fixer: sys_exc

     Changes the deprecated ‘sys.exc_value’, ‘sys.exc_type’,
     ‘sys.exc_traceback’ to use *note sys.exc_info(): c64.

 -- 2to3fixer: throw

     Fixes the API change in generator’s ‘throw()’ method.

 -- 2to3fixer: tuple_params

     Removes implicit tuple parameter unpacking.  This fixer inserts
     temporary variables.

 -- 2to3fixer: types

     Fixes code broken from the removal of some members in the *note
     types: 119. module.

 -- 2to3fixer: unicode

     Renames ‘unicode’ to *note str: 335.

 -- 2to3fixer: urllib

     Handles the rename of *note urllib: 11e. and ‘urllib2’ to the *note
     urllib: 11e. package.

 -- 2to3fixer: ws_comma

     Removes excess whitespace from comma separated items.  This fixer
     is optional.

 -- 2to3fixer: xrange

     Renames ‘xrange()’ to *note range(): 9c3. and wraps existing *note
     range(): 9c3. calls with *note list: 263.

 -- 2to3fixer: xreadlines

     Changes ‘for x in file.xreadlines()’ to ‘for x in file’.

 -- 2to3fixer: zip

     Wraps *note zip(): c37. usage in a *note list: 263. call.  This is
     disabled when ‘from future_builtins import zip’ appears.


File: python.info,  Node: lib2to3 - 2to3's library,  Prev: Fixers,  Up: 2to3 - 自動將 Python 2的程式碼轉成 Python 3

5.26.7.3 ‘lib2to3’ - 2to3’s library
...................................

`Source code:' Lib/lib2to3/(1)

__________________________________________________________________

     備註: The *note lib2to3: a8. API should be considered unstable and
     may change drastically in the future.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/lib2to3/


File: python.info,  Node: test --- Regression tests package for Python,  Next: test support --- Utilities for the Python test suite,  Prev: 2to3 - 自動將 Python 2的程式碼轉成 Python 3,  Up: 開發工具

5.26.8 ‘test’ — Regression tests package for Python
---------------------------------------------------

     備註: The *note test: 106. 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: 106. package contains all regression tests for Python as
well as the modules *note test.support: 107. and ‘test.regrtest’.  *note
test.support: 107. is used to enhance your tests while ‘test.regrtest’
drives the testing suite.

Each module in the *note test: 106. 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: 11c. or *note doctest:
67. 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.

也參考
......

Module *note unittest: 11c.

     Writing PyUnit regression tests.

模組 *note doctest: 67.

     Tests embedded in documentation strings.

* Menu:

* Writing Unit Tests for the test package::
* Running tests using the command-line interface::


File: python.info,  Node: Writing Unit Tests for the test package,  Next: Running tests using the command-line interface,  Up: test --- Regression tests package for Python

5.26.8.1 Writing Unit Tests for the ‘test’ package
..................................................

It is preferred that tests that use the *note unittest: 11c. 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 ‘test.regrtest’,
on its own as a script that supports the *note unittest: 11c. 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: 904. are run as tests.  The ‘Mixin’
     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: 904.

也參考
......

Test Driven Development

     A book by Kent Beck on writing tests before code.


File: python.info,  Node: Running tests using the command-line interface,  Prev: Writing Unit Tests for the test package,  Up: test --- Regression tests package for Python

5.26.8.2 Running tests using the command-line interface
.......................................................

The *note test: 106. package can be run as a script to drive Python’s
regression test suite, thanks to the *note -m: 33c. option: ‘python -m
test’.  Under the hood, it uses ‘test.regrtest’; 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: 106. 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: 106. 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: 106. 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 --- Utilities for the Python test suite,  Next: test support script_helper --- Utilities for the Python execution tests,  Prev: test --- Regression tests package for Python,  Up: 開發工具

5.26.9 ‘test.support’ — Utilities for the Python test suite
-----------------------------------------------------------

The *note test.support: 107. module provides support for Python’s
regression test suite.

     備註: *note test.support: 107. 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.

This module defines the following exceptions:

 -- 例外: test.support.TestFailed

     Exception to be raised when a test fails.  This is deprecated in
     favor of *note unittest: 11c.-based tests and *note
     unittest.TestCase: 904.’s assertion methods.

 -- 例外: test.support.ResourceDenied

     Subclass of *note unittest.SkipTest: 908.  Raised when a resource
     (such as a network connection) is not available.  Raised by the
     *note requires(): 342a. function.

The *note test.support: 107. module defines the following constants:

 -- Data: 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 ‘test.regrtest’.

 -- Data: test.support.is_jython

     ‘True’ if the running interpreter is Jython.

 -- Data: test.support.is_android

     ‘True’ if the system is Android.

 -- Data: test.support.unix_shell

     Path for shell if not on Windows; otherwise ‘None’.

 -- Data: test.support.FS_NONASCII

     A non-ASCII character encodable by *note os.fsencode(): 4f4.

 -- Data: test.support.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).

 -- Data: test.support.TESTFN_UNICODE

     Set to a non-ASCII name for a temporary file.

 -- Data: test.support.TESTFN_ENCODING

     Set to *note sys.getfilesystemencoding(): 4fb.

 -- Data: test.support.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.

 -- Data: test.support.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.

 -- Data: test.support.TESTFN_NONASCII

     Set to a filename containing the *note FS_NONASCII: 342f.
     character.

 -- Data: test.support.IPV6_ENABLED

     Set to ‘True’ if IPV6 is enabled on this host, ‘False’ otherwise.

 -- Data: test.support.SAVEDCWD

     Set to *note os.getcwd(): fe3.

 -- Data: test.support.PGO

     Set when tests can be skipped when they are not useful for PGO.

 -- Data: test.support.PIPE_MAX_SIZE

     A constant that is likely larger than the underlying OS pipe buffer
     size, to make writes blocking.

 -- Data: test.support.SOCK_MAX_SIZE

     A constant that is likely larger than the underlying OS socket
     buffer size, to make writes blocking.

 -- Data: test.support.TEST_SUPPORT_DIR

     Set to the top level directory that contains *note test.support:
     107.

 -- Data: test.support.TEST_HOME_DIR

     Set to the top level directory for the test package.

 -- Data: test.support.TEST_DATA_DIR

     Set to the ‘data’ directory within the test package.

 -- Data: test.support.MAX_Py_ssize_t

     Set to *note sys.maxsize: b48. for big memory tests.

 -- Data: test.support.max_memuse

     Set by *note set_memlimit(): 3440. as the memory limit for big
     memory tests.  Limited by *note MAX_Py_ssize_t: 343e.

 -- Data: test.support.real_max_memuse

     Set by *note set_memlimit(): 3440. as the memory limit for big
     memory tests.  Not limited by *note MAX_Py_ssize_t: 343e.

 -- Data: test.support.MISSING_C_DOCSTRINGS

     Return ‘True’ if running on CPython, not on Windows, and
     configuration not set with ‘WITH_DOC_STRINGS’.

 -- Data: test.support.HAVE_DOCSTRINGS

     Check for presence of docstrings.

 -- Data: test.support.TEST_HTTP_URL

     Define the URL of a dedicated HTTP server for the network tests.

 -- Data: test.support.ALWAYS_EQ

     Object that is equal to anything.  Used to test mixed type
     comparison.

 -- Data: test.support.LARGEST

     Object that is greater than anything (except itself).  Used to test
     mixed type comparison.

 -- Data: test.support.SMALLEST

     Object that is less than anything (except itself).  Used to test
     mixed type comparison.

The *note test.support: 107. module defines the following functions:

 -- 函式: test.support.forget (module_name)

     Remove the module named `module_name' from ‘sys.modules’ and delete
     any byte-compiled files of the module.

 -- 函式: test.support.unload (name)

     Delete `name' from ‘sys.modules’.

 -- 函式: test.support.unlink (filename)

     Call *note os.unlink(): a41. on `filename'.  On Windows platforms,
     this is wrapped with a wait loop that checks for the existence fo
     the file.

 -- 函式: test.support.rmdir (filename)

     Call *note os.rmdir(): a3f. on `filename'.  On Windows platforms,
     this is wrapped with a wait loop that checks for the existence of
     the file.

 -- 函式: test.support.rmtree (path)

     Call *note shutil.rmtree(): 21d. on `path' or call *note
     os.lstat(): 1f3. and *note os.rmdir(): a3f. to remove a path and
     its contents.  On Windows platforms, this is wrapped with a wait
     loop that checks for the existence of the files.

 -- 函式: test.support.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.is_resource_enabled (resource)

     Return ‘True’ if `resource' is enabled and available.  The list of
     available resources is only set when ‘test.regrtest’ is executing
     the tests.

 -- 函式: test.support.python_is_optimized ()

     Return ‘True’ if Python was not built with ‘-O0’ or ‘-Og’.

 -- 函式: test.support.with_pymalloc ()

     Return ‘_testcapi.WITH_PYMALLOC’.

 -- 函式: test.support.requires (resource, msg=None)

     Raise *note ResourceDenied: 3429. if `resource' is not available.
     `msg' is the argument to *note ResourceDenied: 3429. if it is
     raised.  Always returns ‘True’ if called by a function whose
     ‘__name__’ is ‘'__main__'’.  Used when tests are executed by
     ‘test.regrtest’.

 -- 函式: test.support.system_must_validate_cert (f)

     Raise *note unittest.SkipTest: 908. on TLS certification validation
     failures.

 -- 函式: 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.create_empty_file (filename)

     Create an empty file with `filename'.  If it already exists,
     truncate it.

 -- 函式: test.support.fd_count ()

     Count the number of open file descriptors.

 -- 函式: test.support.match_test (test)

     Match `test' to patterns set in *note set_match_tests(): 3457.

 -- 函式: test.support.set_match_tests (patterns)

     Define match test with regular expression `patterns'.

 -- 函式: test.support.run_unittest (*classes)

     Execute *note unittest.TestCase: 904. subclasses passed to the
     function.  The function scans the classes for methods starting with
     the prefix ‘test_’ and executes the tests individually.

     It is also legal to pass strings as parameters; these should be
     keys in ‘sys.modules’.  Each associated module will be scanned by
     ‘unittest.TestLoader.loadTestsFromModule()’.  This is usually seen
     in the following ‘test_main()’ function:

          def test_main():
              support.run_unittest(__name__)

     This will run all tests defined in the named module.

 -- 函式: test.support.run_doctest (module, verbosity=None,
          optionflags=0)

     Run *note doctest.testmod(): dd5. on the given `module'.  Return
     ‘(failure_count, test_count)’.

     If `verbosity' is ‘None’, *note doctest.testmod(): dd5. is run with
     verbosity set to *note verbose: 342b.  Otherwise, it is run with
     verbosity set to ‘None’.  `optionflags' is passed as ‘optionflags’
     to *note doctest.testmod(): dd5.

 -- 函式: test.support.setswitchinterval (interval)

     Set the *note sys.setswitchinterval(): bf0. 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:

          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.check_warnings (*filters, quiet=True)

     A convenience wrapper for *note warnings.catch_warnings(): 345c.
     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(): 345d. 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’.

     If no arguments are specified, it defaults to:

          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(): 345c. is available via the recorder object’s
     *note warnings: 127. 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(): 345b. 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 版更變: New optional arguments `filters' and `quiet'.

 -- 函式: test.support.check_no_resource_warning (testcase)

     Context manager to check that no *note ResourceWarning: 4d5. was
     raised.  You must remove the object which may emit *note
     ResourceWarning: 4d5. before the end of the context manager.

 -- 函式: test.support.set_memlimit (limit)

     Set the values for *note max_memuse: 343f. and *note
     real_max_memuse: 3441. 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():
     345f. or ‘sys.stdout’ if it’s not set.

 -- 函式: test.support.strip_python_strerr (stderr)

     Strip the `stderr' of a Python process from potential debug output
     emitted by the interpreter.  This will typically be run on the
     result of *note subprocess.Popen.communicate(): 2458.

 -- 函式: 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: 832. object.

     Example use with output streams:

          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"

     Example use with input stream:

          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.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(): 1c6e.  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.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.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(): 1c6e.

     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.temp_umask (umask)

     A context manager that temporarily sets the process umask.

 -- 函式: test.support.transient_internet (resource_name, *,
          timeout=30.0, errnos=())

     A context manager that raises *note ResourceDenied: 3429. when
     various issues with the internet connection manifest themselves as
     exceptions.

 -- 函式: test.support.disable_faulthandler ()

     A context manager that replaces ‘sys.stderr’ with ‘sys.__stderr__’.

 -- 函式: 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 upon entry
     and reenables it upon exit.

 -- 函式: test.support.swap_attr (obj, attr, new_val)

     Context manager to swap out an attribute with a new object.

     Usage:

          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.

     Usage:

          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.wait_threads_exit (timeout=60.0)

     Context manager to wait until all threads created in the ‘with’
     statement exit.

 -- 函式: test.support.start_threads (threads, unlock=None)

     Context manager to start `threads'.  It attempts to join the
     threads upon exit.

 -- 函式: test.support.calcobjsize (fmt)

     Return *note struct.calcsize(): 1815. for ‘nP{fmt}0n’ or, if
     ‘gettotalrefcount’ exists, ‘2PnP{fmt}0P’.

 -- 函式: test.support.calcvobjsize (fmt)

     Return *note struct.calcsize(): 1815. for ‘nPn{fmt}0n’ or, if
     ‘gettotalrefcount’ exists, ‘2PnPn{fmt}0P’.

 -- 函式: 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.can_symlink ()

     Return ‘True’ if the OS supports symbolic links, ‘False’ otherwise.

 -- 函式: test.support.can_xattr ()

     Return ‘True’ if the OS supports xattr, ‘False’ otherwise.

 -- 函式: @test.support.skip_unless_symlink

     A decorator for running tests that require support for symbolic
     links.

 -- 函式: @test.support.skip_unless_xattr

     A decorator for running tests that require support for xattr.

 -- 函式: @test.support.skip_unless_bind_unix_socket

     A decorator for running tests that require a functional bind() for
     Unix sockets.

 -- 函式: @test.support.anticipate_failure (condition)

     A decorator to conditionally mark tests with *note
     unittest.expectedFailure(): 3336.  Any use of this decorator should
     have an associated comment identifying the relevant tracker issue.

 -- 函式: @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, raise *note
     unittest.SkipTest: 908.

 -- 函式: @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, raise *note
     unittest.SkipTest: 908.

 -- 函式: @test.support.requires_mac_version (*min_version)

     Decorator for the minimum version when running test on Mac OS X. If
     the MAC OS X version is less than the minimum, raise *note
     unittest.SkipTest: 908.

 -- 函式: @test.support.requires_IEEE_754

     Decorator for skipping tests on non-IEEE 754 platforms.

 -- 函式: @test.support.requires_zlib

     Decorator for skipping tests if *note zlib: 145. doesn’t exist.

 -- 函式: @test.support.requires_gzip

     Decorator for skipping tests if *note gzip: 8c. doesn’t exist.

 -- 函式: @test.support.requires_bz2

     Decorator for skipping tests if *note bz2: 14. doesn’t exist.

 -- 函式: @test.support.requires_lzma

     Decorator for skipping tests if *note lzma: ae. doesn’t exist.

 -- 函式: @test.support.requires_resource (resource)

     Decorator for skipping tests if `resource' is not available.

 -- 函式: @test.support.requires_docstrings

     Decorator for only running the test if *note HAVE_DOCSTRINGS: 3443.

 -- 函式: @test.support.cpython_only (test)

     Decorator for tests only applicable to CPython.

 -- 函式: @test.support.impl_detail (msg=None, **guards)

     Decorator for invoking *note check_impl_detail(): 345a. on
     `guards'.  If that returns ‘False’, then uses `msg' as the reason
     for skipping the test.

 -- 函式: @test.support.no_tracing (func)

     Decorator to temporarily turn off tracing for the duration of the
     test.

 -- 函式: @test.support.refcount_test (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.reap_threads (func)

     Decorator to ensure the threads are cleaned up even if the test
     fails.

 -- 函式: @test.support.bigmemtest (size, memuse, dry_run=True)

     Decorator for bigmem tests.

     `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 (f)

     Decorator for tests that fill the address space.  `f' is the
     function to wrap.

 -- 函式: test.support.make_bad_fd ()

     Create an invalid file descriptor by opening and closing a
     temporary file, and returning its descriptor.

 -- 函式: 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: 11c. instance for
     the test.  `errtext' is the regular expression which should match
     the string representation of the raised *note SyntaxError: 45d.  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.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: 192. is
     emitted only once, and that it will be converted to a *note
     SyntaxError: 45d. when turned into error.  `testcase' is the *note
     unittest: 11c. instance for the test.  `errtext' is the regular
     expression which should match the string representation of the
     emitted *note SyntaxWarning: 192. and raised *note SyntaxError:
     45d.  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.open_urlresource (url, *args, **kw)

     Open `url'.  If open fails, raises *note TestFailed: 3428.

 -- 函式: test.support.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: 908.
     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: 2b2.

     3.1 版新加入.

 -- 函式: test.support.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: 339.

     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’.

     This function will raise *note ImportError: 339. if the named
     module cannot be imported.

     Example use:

          # 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.modules_setup ()

     Return a copy of *note sys.modules: f2b.

 -- 函式: test.support.modules_cleanup (oldmodules)

     Remove modules except for `oldmodules' and ‘encodings’ in order to
     preserve internal cache.

 -- 函式: test.support.threading_setup ()

     Return current thread count and copy of dangling threads.

 -- 函式: test.support.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.join_thread (thread, timeout=30.0)

     Join a `thread' within `timeout'.  Raise an *note AssertionError:
     1033. if thread is still alive after `timeout' seconds.

 -- 函式: 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: 908. if *note
     AttributeError: 3a0. is raised.

 -- 函式: test.support.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: 25ae. and
     ‘sock.type’ is *note SOCK_STREAM: c8f, 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.bind_unix_socket (sock, addr)

     Bind a unix socket, raising *note unittest.SkipTest: 908. if *note
     PermissionError: 604. is raised.

 -- 函式: test.support.catch_threading_exception ()

     Context manager catching *note threading.Thread: 236. exception
     using *note threading.excepthook(): 232.

     Attributes set when an exception is catched:

        * ‘exc_type’

        * ‘exc_value’

        * ‘exc_traceback’

        * ‘thread’

     See *note threading.excepthook(): 232. documentation.

     These attributes are deleted at the context manager exit.

     Usage:

          with support.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 版新加入.

 -- 函式: test.support.catch_unraisable_exception ()

     Context manager catching unraisable exception using *note
     sys.unraisablehook(): 22e.

     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.

     Usage:

          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.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: 25ae, *note
     SOCK_STREAM: c8f.), 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(): 349a. 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(): 349a. over *note
     find_unused_port(): 349c. 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.load_package_tests (pkg_dir, loader,
          standard_tests, pattern)

     Generic implementation of the *note unittest: 11c. ‘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.fs_is_case_insensitive (directory)

     Return ‘True’ if the file system for `directory' is
     case-insensitive.

 -- 函式: 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'.

     By default this skips private attributes beginning with ’_’ but
     includes all magic methods, i.e.  those starting and ending in
     ’__’.

     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: 908.
     if *note tracemalloc: 115. is enabled.

 -- 函式: test.support.check_free_after_iterating (test, iter, cls,
          args=())

     Assert that `iter' is 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=(), blacklist=())

     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 `blacklist' argument can be a set of names that must not be
     treated as part of the public API even though their names indicate
     otherwise.

     Example use:

          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'}
                  blacklist = {'baz'}  # Undocumented name.
                  # bar imports part of its API from _bar.
                  support.check__all__(self, bar, ('bar', '_bar'),
                                       extra=extra, blacklist=blacklist)

     3.6 版新加入.

The *note test.support: 107. module defines the following classes:

 -- 類別: test.support.TransientResource (exc, **kwargs)

     Instances are a context manager that raises *note ResourceDenied:
     3429. if the specified exception type is raised.  Any keyword
     arguments are treated as attribute/value pairs to be compared
     against any exception raised within the *note with: 6ee. statement.
     Only if all pairs match properly against attributes on the
     exception is *note ResourceDenied: 3429. raised.

 -- 類別: test.support.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 版更變: Added dictionary interface.

 -- 成員函式: EnvironmentVarGuard.set (envvar, value)

     Temporarily set the environment variable ‘envvar’ to the value of
     ‘value’.

 -- 成員函式: EnvironmentVarGuard.unset (envvar)

     Temporarily unset the environment variable ‘envvar’.

 -- 類別: 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(3).

     On UNIX, *note resource.setrlimit(): 34aa. is used to set *note
     resource.RLIMIT_CORE: 34ab.’s soft limit to 0 to prevent coredump
     file creation.

     On both platforms, the old value is restored by *note __exit__():
     c9b.

 -- 類別: test.support.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 DeprecationWarning on import.  Example usage:

          with CleanImport('foo'):
              importlib.import_module('foo')  # New reference.

 -- 類別: test.support.DirsOnSysPath (*paths)

     A context manager to temporarily add directories to sys.path.

     This makes a copy of *note sys.path: 48d, appends any directories
     given as positional arguments, then reverts *note sys.path: 48d. to
     the copied settings when the context ends.

     Note that `all' *note sys.path: 48d. modifications in the body of
     the context manager, including replacement of the object, will be
     reverted at the end of the block.

 -- 類別: test.support.SaveSignals

     Class to save and restore signal handlers registered by the Python
     signal 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').

 -- 類別: test.support.WarningsRecorder

     Class used to record warnings for unit tests.  See documentation of
     *note check_warnings(): 345b. above for more details.

 -- 類別: test.support.BasicTestRunner

      -- 成員函式: run (test)

          Run `test' and return the result.

 -- 類別: test.support.TestHandler (logging.handlers.BufferingHandler)

     Class for logging support.

 -- 類別: test.support.FakePath (path)

     Simple *note path-like object: 36f.  It implements the
     ‘__fspath__()’ method which just returns the `path' argument.  If
     `path' is an exception, it will be raised in ‘__fspath__()’.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3147

   (2) https://www.python.org/dev/peps/pep-0488

   (3) 
https://msdn.microsoft.com/en-us/library/windows/desktop/ms680621.aspx


File: python.info,  Node: test support script_helper --- Utilities for the Python execution tests,  Prev: test support --- Utilities for the Python test suite,  Up: 開發工具

5.26.10 ‘test.support.script_helper’ — Utilities for the Python execution tests
-------------------------------------------------------------------------------

The *note test.support.script_helper: 108. module provides support for
Python’s script execution tests.

 -- 函式: 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: 4db. is one way to get most of the
     testsuite to run in that situation.  *note PYTHONPATH: 958. 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’.

 -- 函式: 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 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 is set to ‘False’.

 -- 函式: 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.

     See *note assert_python_ok(): 34ba. for more options.

 -- 函式: 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():
     2ba.  Returns a *note subprocess.Popen: 2ba. object.

 -- 函式: test.support.script_helper.kill_python (p)

     Run the given *note subprocess.Popen: 2ba. 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.

See also the Python development mode: the *note -X: 156. ‘dev’ option
and *note PYTHONDEVMODE: 331. environment variable.


File: python.info,  Node: Debugging and Profiling,  Next: 軟體封裝與發布,  Prev: 開發工具,  Up: Python 標準函式庫 Standard Library

5.27 Debugging and Profiling
============================

These libraries help you with Python development: the debugger enables
you to step through code, analyze stack frames and set breakpoints etc.,
and the profilers run code and give you a detailed breakdown of
execution times, allowing you to identify bottlenecks in your programs.
Auditing events provide visibility into runtime behaviors that would
otherwise require intrusive debugging or patching.

* Menu:

* Audit events table::
* bdb: bdb --- Debugger framework. Debugger framework
* faulthandler: faulthandler --- Dump the Python traceback. Dump the Python traceback
* pdb: pdb --- The Python Debugger. The Python Debugger
* The Python Profilers::
* timeit: timeit --- Measure execution time of small code snippets. Measure execution time of small code snippets
* trace: trace --- Trace or track Python statement execution. Trace or track Python statement execution
* tracemalloc: tracemalloc --- Trace memory allocations. Trace memory allocations


File: python.info,  Node: Audit events table,  Next: bdb --- Debugger framework,  Up: Debugging and Profiling

5.27.1 Audit events table
-------------------------

This table contains all events raised by *note sys.audit(): f2d. or
*note PySys_Audit(): f3b. calls throughout the CPython runtime and the
standard library.  These calls were added in 3.8.0 or later (see PEP
578(1)).

See *note sys.addaudithook(): 34c7. and *note PySys_AddAuditHook():
34c8. for information on handling these events.

`CPython implementation detail:' This table is generated from the
CPython documentation, and may not represent events raised by other
implementations.  See your runtime specific documentation for actual
events raised.

Audit event                        Arguments                                                   References
                                                                                               
-------------------------------------------------------------------------------------------------------------------
                                                                                               
array.__new__                      ‘typecode’, ‘initializer’                                   *note [1]: 456.
                                                                                               
                                                                                               
builtins.breakpoint                ‘breakpointhook’                                            *note [1]: 2fe.
                                                                                               
                                                                                               
builtins.id                        ‘id’                                                        *note [1]: d8b.
                                                                                               
                                                                                               
builtins.input                     ‘prompt’                                                    *note [1]: c70.
                                                                                               
                                                                                               
builtins.input/result              ‘result’                                                    *note [1]: c70.
                                                                                               
                                                                                               
code.__new__                       ‘code’, ‘filename’, ‘name’, ‘argcount’,                     *note [1]: 199.
                                   ‘posonlyargcount’, ‘kwonlyargcount’, ‘nlocals’,             
                                   ‘stacksize’, ‘flags’
                                   
                                                                                               
compile                            ‘source’, ‘filename’                                        *note [1]: 1b5.
                                                                                               
                                                                                               
cpython.PyInterpreterState_Clear                                                               *note [1]: 34c9.
                                                                                               
                                                                                               
cpython.PyInterpreterState_New                                                                 *note [1]: 34ca.
                                                                                               
                                                                                               
cpython._PySys_ClearAuditHooks                                                                 *note [1]: 5ce.
                                                                                               
                                                                                               
cpython.run_command                ‘command’                                                   *note [1]: 1210.
                                                                                               
                                                                                               
cpython.run_file                   ‘filename’                                                  *note [1]: 34cb.
                                                                                               
                                                                                               
cpython.run_interactivehook        ‘hook’                                                      *note [1]: 8e9.
                                                                                               
                                                                                               
cpython.run_module                 ‘module-name’                                               *note [1]: 33c.
                                                                                               
                                                                                               
cpython.run_startup                ‘filename’                                                  *note [1]: 8ea.
                                                                                               
                                                                                               
cpython.run_stdin                                                                              *note [1]: 34cc.
                                                                                               
                                                                                               
ctypes.addressof                   ‘obj’                                                       *note [1]: 2320.
                                                                                               
                                                                                               
ctypes.call_function               ‘func_pointer’, ‘arguments’                                 *note [1]: 2315.
                                                                                               
                                                                                               
ctypes.cdata                       ‘address’                                                   *note [1]: 2332.
                                                                                               
                                                                                               
ctypes.cdata/buffer                ‘pointer’, ‘size’, ‘offset’                                 *note [1]: 2330.*note [2]: 2331.
                                                                                               
                                                                                               
ctypes.create_string_buffer        ‘init’, ‘size’                                              *note [1]: 22d2.
                                                                                               
                                                                                               
ctypes.create_unicode_buffer       ‘init’, ‘size’                                              *note [1]: fb2.
                                                                                               
                                                                                               
ctypes.dlopen                      ‘name’                                                      *note [1]: 2312.
                                                                                               
                                                                                               
ctypes.dlsym                       ‘library’, ‘name’                                           *note [1]: 2312.
                                                                                               
                                                                                               
ctypes.dlsym/handle                ‘handle’, ‘name’                                            *note [1]: 2312.
                                                                                               
                                                                                               
ctypes.get_errno                                                                               *note [1]: 230c.
                                                                                               
                                                                                               
ctypes.get_last_error                                                                          *note [1]: 230e.
                                                                                               
                                                                                               
ctypes.seh_exception               ‘code’                                                      *note [1]: 2315.
                                                                                               
                                                                                               
ctypes.set_errno                   ‘errno’                                                     *note [1]: 230d.
                                                                                               
                                                                                               
ctypes.set_last_error              ‘error’                                                     *note [1]: 230f.
                                                                                               
                                                                                               
ctypes.string_at                   ‘address’, ‘size’                                           *note [1]: 2329.
                                                                                               
                                                                                               
ctypes.wstring_at                  ‘address’, ‘size’                                           *note [1]: 232b.
                                                                                               
                                                                                               
ensurepip.bootstrap                ‘root’                                                      *note [1]: 34cd.
                                                                                               
                                                                                               
exec                               ‘code_object’                                               *note [1]: b95.*note [2]: c49.
                                                                                               
                                                                                               
fcntl.fcntl                        ‘fd’, ‘cmd’, ‘arg’                                          *note [1]: 26a0.
                                                                                               
                                                                                               
fcntl.flock                        ‘fd’, ‘operation’                                           *note [1]: 34ce.
                                                                                               
                                                                                               
fcntl.ioctl                        ‘fd’, ‘request’, ‘arg’                                      *note [1]: de3.
                                                                                               
                                                                                               
fcntl.lockf                        ‘fd’, ‘cmd’, ‘len’, ‘start’, ‘whence’                       *note [1]: d57.
                                                                                               
                                                                                               
ftplib.connect                     ‘self’, ‘host’, ‘port’                                      *note [1]: 2d1c.
                                                                                               
                                                                                               
ftplib.sendcmd                     ‘self’, ‘cmd’                                               *note [1]: 2d20.*note [2]: 2d21.
                                                                                               
                                                                                               
function.__new__                   ‘code’                                                      *note [1]: 19ad.
                                                                                               
                                                                                               
gc.get_objects                     ‘generation’                                                *note [1]: 1ce.
                                                                                               
                                                                                               
gc.get_referents                   ‘objs’                                                      *note [1]: eaa.
                                                                                               
                                                                                               
gc.get_referrers                   ‘objs’                                                      *note [1]: ea9.
                                                                                               
                                                                                               
glob.glob                          ‘pathname’, ‘recursive’                                     *note [1]: 5cb.*note [2]: 5cc.
                                                                                               
                                                                                               
imaplib.open                       ‘self’, ‘host’, ‘port’                                      *note [1]: 2d6c.
                                                                                               
                                                                                               
imaplib.send                       ‘self’, ‘data’                                              *note [1]: 2d6f.
                                                                                               
                                                                                               
import                             ‘module’, ‘filename’, ‘sys.path’, ‘sys.meta_path’,          *note [1]: c22.
                                   ‘sys.path_hooks’                                            
                                   
                                                                                               
mmap.__new__                       ‘fileno’, ‘length’, ‘access’, ‘offset’                      *note [1]: 1ed.
                                                                                               
                                                                                               
msvcrt.get_osfhandle               ‘fd’                                                        *note [1]: 34cf.
                                                                                               
                                                                                               
msvcrt.locking                     ‘fd’, ‘mode’, ‘nbytes’                                      *note [1]: 34d0.
                                                                                               
                                                                                               
msvcrt.open_osfhandle              ‘handle’, ‘flags’                                           *note [1]: 34d1.
                                                                                               
                                                                                               
nntplib.connect                    ‘self’, ‘host’, ‘port’                                      *note [1]: a31.*note [2]: baa.
                                                                                               
                                                                                               
nntplib.putline                    ‘self’, ‘line’                                              *note [1]: a31.*note [2]: baa.
                                                                                               
                                                                                               
object.__delattr__                 ‘obj’, ‘name’                                               *note [1]: 1435.
                                                                                               
                                                                                               
object.__getattr__                 ‘obj’, ‘name’                                               *note [1]: 44e.
                                                                                               
                                                                                               
object.__setattr__                 ‘obj’, ‘name’, ‘value’                                      *note [1]: e31.
                                                                                               
                                                                                               
open                               ‘file’, ‘mode’, ‘flags’                                     *note [1]: 4f5.*note [2]: 65f.*note [3]: 66a.
                                                                                               
                                                                                               
os.add_dll_directory               ‘path’                                                      *note [1]: 1c3.
                                                                                               
                                                                                               
os.chdir                           ‘path’                                                      *note [1]: a44.*note [2]: 660.
                                                                                               
                                                                                               
os.chflags                         ‘path’, ‘flags’                                             *note [1]: a37.*note [2]: 1f52.
                                                                                               
                                                                                               
os.chmod                           ‘path’, ‘mode’, ‘dir_fd’                                    *note [1]: a38.*note [2]: 661.*note [3]: 102e.
                                                                                               
                                                                                               
os.chown                           ‘path’, ‘uid’, ‘gid’, ‘dir_fd’                              *note [1]: a39.*note [2]: 662.*note [3]: 1f53.
                                                                                               
                                                                                               
os.exec                            ‘path’, ‘args’, ‘env’                                       *note [1]: 1f8f.
                                                                                               
                                                                                               
os.fork                                                                                        *note [1]: 966.
                                                                                               
                                                                                               
os.forkpty                                                                                     *note [1]: 1fa7.
                                                                                               
                                                                                               
os.getxattr                        ‘path’, ‘attribute’                                         *note [1]: a50.
                                                                                               
                                                                                               
os.kill                            ‘pid’, ‘sig’                                                *note [1]: cf8.
                                                                                               
                                                                                               
os.killpg                          ‘pgid’, ‘sig’                                               *note [1]: f34.
                                                                                               
                                                                                               
os.link                            ‘src’, ‘dst’, ‘src_dir_fd’, ‘dst_dir_fd’                    *note [1]: a3a.
                                                                                               
                                                                                               
os.listdir                         ‘path’                                                      *note [1]: a46.
                                                                                               
                                                                                               
os.listxattr                       ‘path’                                                      *note [1]: a51.
                                                                                               
                                                                                               
os.lockf                           ‘fd’, ‘cmd’, ‘len’                                          *note [1]: a5f.
                                                                                               
                                                                                               
os.mkdir                           ‘path’, ‘mode’, ‘dir_fd’                                    *note [1]: 3c2.*note [2]: a3b.
                                                                                               
                                                                                               
os.posix_spawn                     ‘path’, ‘argv’, ‘env’                                       *note [1]: 258.*note [2]: 101a.
                                                                                               
                                                                                               
os.putenv                          ‘key’, ‘value’                                              *note [1]: 1eeb.
                                                                                               
                                                                                               
os.remove                          ‘path’, ‘dir_fd’                                            *note [1]: a3c.*note [2]: 1f5a.*note [3]: a41.
                                                                                               
                                                                                               
os.removexattr                     ‘path’, ‘attribute’                                         *note [1]: a52.
                                                                                               
                                                                                               
os.rename                          ‘src’, ‘dst’, ‘src_dir_fd’, ‘dst_dir_fd’                    *note [1]: a3d.*note [2]: 1f5b.*note [3]: a3e.
                                                                                               
                                                                                               
os.rmdir                           ‘path’, ‘dir_fd’                                            *note [1]: a3f.
                                                                                               
                                                                                               
os.scandir                         ‘path’                                                      *note [1]: 260.
                                                                                               
                                                                                               
os.setxattr                        ‘path’, ‘attribute’, ‘value’, ‘flags’                       *note [1]: a53.
                                                                                               
                                                                                               
os.spawn                           ‘mode’, ‘path’, ‘args’, ‘env’                               *note [1]: 1f4b.
                                                                                               
                                                                                               
os.startfile                       ‘path’, ‘operation’                                         *note [1]: 1fbb.
                                                                                               
                                                                                               
os.symlink                         ‘src’, ‘dst’, ‘dir_fd’                                      *note [1]: a40.
                                                                                               
                                                                                               
os.system                          ‘command’                                                   *note [1]: dc6.
                                                                                               
                                                                                               
os.truncate                        ‘fd’, ‘length’                                              *note [1]: 667.*note [2]: 729.
                                                                                               
                                                                                               
os.unsetenv                        ‘key’                                                       *note [1]: d48.
                                                                                               
                                                                                               
os.utime                           ‘path’, ‘times’, ‘ns’, ‘dir_fd’                             *note [1]: a42.
                                                                                               
                                                                                               
pdb.Pdb                                                                                        *note [1]: 571.
                                                                                               
                                                                                               
pickle.find_class                  ‘module’, ‘name’                                            *note [1]: 1cc6.
                                                                                               
                                                                                               
poplib.connect                     ‘self’, ‘host’, ‘port’                                      *note [1]: 2d37.*note [2]: bc6.
                                                                                               
                                                                                               
poplib.putline                     ‘self’, ‘line’                                              *note [1]: 2d37.*note [2]: bc6.
                                                                                               
                                                                                               
pty.spawn                          ‘argv’                                                      *note [1]: 89d.
                                                                                               
                                                                                               
resource.prlimit                   ‘pid’, ‘resource’, ‘limits’                                 *note [1]: 8a4.
                                                                                               
                                                                                               
resource.setrlimit                 ‘resource’, ‘limits’                                        *note [1]: 34aa.
                                                                                               
                                                                                               
setopencodehook                                                                                *note [1]: 1fec.
                                                                                               
                                                                                               
shutil.chown                       ‘path’, ‘user’, ‘group’                                     *note [1]: a7b.
                                                                                               
                                                                                               
shutil.copyfile                    ‘src’, ‘dst’                                                *note [1]: 25a.*note [2]: 25b.*note [3]: 259.
                                                                                               
                                                                                               
shutil.copymode                    ‘src’, ‘dst’                                                *note [1]: 25a.*note [2]: 1c8d.
                                                                                               
                                                                                               
shutil.copystat                    ‘src’, ‘dst’                                                *note [1]: 25b.*note [2]: a7c.
                                                                                               
                                                                                               
shutil.copytree                    ‘src’, ‘dst’                                                *note [1]: 21b.
                                                                                               
                                                                                               
shutil.make_archive                ‘base_name’, ‘format’, ‘root_dir’, ‘base_dir’               *note [1]: 21c.
                                                                                               
                                                                                               
shutil.move                        ‘src’, ‘dst’                                                *note [1]: 25c.
                                                                                               
                                                                                               
shutil.rmtree                      ‘path’                                                      *note [1]: 21d.
                                                                                               
                                                                                               
shutil.unpack_archive              ‘filename’, ‘extract_dir’, ‘format’                         *note [1]: b9c.
                                                                                               
                                                                                               
signal.pthread_kill                ‘thread_id’, ‘signalnum’                                    *note [1]: a7f.
                                                                                               
                                                                                               
smtplib.connect                    ‘self’, ‘host’, ‘port’                                      *note [1]: ee0.
                                                                                               
                                                                                               
smtplib.send                       ‘self’, ‘data’                                              *note [1]: a86.
                                                                                               
                                                                                               
socket.__new__                     ‘self’, ‘family’, ‘type’, ‘protocol’                        *note [1]: 679.
                                                                                               
                                                                                               
socket.bind                        ‘self’, ‘address’                                           *note [1]: 269a.
                                                                                               
                                                                                               
socket.connect                     ‘self’, ‘address’                                           *note [1]: 67b.*note [2]: 269c.
                                                                                               
                                                                                               
socket.getaddrinfo                 ‘host’, ‘port’, ‘family’, ‘type’, ‘protocol’                *note [1]: 25c2.
                                                                                               
                                                                                               
socket.gethostbyaddr               ‘ip_address’                                                *note [1]: ea2.
                                                                                               
                                                                                               
socket.gethostbyname               ‘hostname’                                                  *note [1]: 2691.*note [2]: ea3.
                                                                                               
                                                                                               
socket.gethostname                                                                             *note [1]: 1f0a.
                                                                                               
                                                                                               
socket.getnameinfo                 ‘sockaddr’                                                  *note [1]: 25c3.
                                                                                               
                                                                                               
socket.getservbyname               ‘servicename’, ‘protocolname’                               *note [1]: 2693.
                                                                                               
                                                                                               
socket.getservbyport               ‘port’, ‘protocolname’                                      *note [1]: 2694.
                                                                                               
                                                                                               
socket.sendmsg                     ‘self’, ‘address’                                           *note [1]: 681.
                                                                                               
                                                                                               
socket.sendto                      ‘self’, ‘address’                                           *note [1]: 682.
                                                                                               
                                                                                               
socket.sethostname                 ‘name’                                                      *note [1]: a8c.
                                                                                               
                                                                                               
sqlite3.connect                    ‘database’                                                  *note [1]: 3df.
                                                                                               
                                                                                               
subprocess.Popen                   ‘executable’, ‘args’, ‘cwd’, ‘env’                          *note [1]: 2ba.
                                                                                               
                                                                                               
sys._current_frames                                                                            *note [1]: da0.
                                                                                               
                                                                                               
sys._getframe                                                                                  *note [1]: e69.
                                                                                               
                                                                                               
sys.addaudithook                                                                               *note [1]: 34c8.*note [2]: 34c7.
                                                                                               
                                                                                               
sys.excepthook                     ‘hook’, ‘type’, ‘value’, ‘traceback’                        *note [1]: e68.
                                                                                               
                                                                                               
sys.set_asyncgen_hooks_finalizer                                                               *note [1]: f2e.
                                                                                               
                                                                                               
sys.set_asyncgen_hooks_firstiter                                                               *note [1]: f2e.
                                                                                               
                                                                                               
sys.setprofile                                                                                 *note [1]: e42.
                                                                                               
                                                                                               
sys.settrace                                                                                   *note [1]: e43.
                                                                                               
                                                                                               
sys.unraisablehook                 ‘hook’, ‘unraisable’                                        *note [1]: 22e.
                                                                                               
                                                                                               
syslog.closelog                                                                                *note [1]: 34d2.
                                                                                               
                                                                                               
syslog.openlog                     ‘ident’, ‘logoption’, ‘facility’                            *note [1]: 34d3.
                                                                                               
                                                                                               
syslog.setlogmask                  ‘maskpri’                                                   *note [1]: 34d4.
                                                                                               
                                                                                               
syslog.syslog                      ‘priority’, ‘message’                                       *note [1]: 34d5.
                                                                                               
                                                                                               
telnetlib.Telnet.open              ‘self’, ‘host’, ‘port’                                      *note [1]: 2de1.
                                                                                               
                                                                                               
telnetlib.Telnet.write             ‘self’, ‘buffer’                                            *note [1]: 2df1.
                                                                                               
                                                                                               
tempfile.mkdtemp                   ‘fullpath’                                                  *note [1]: bcd.*note [2]: 1c6e.
                                                                                               
                                                                                               
tempfile.mkstemp                   ‘fullpath’                                                  *note [1]: d4e.*note [2]: 1c6c.*note [3]: 1c6d.
                                                                                               
                                                                                               
urllib.Request                     ‘fullurl’, ‘data’, ‘headers’, ‘method’                      *note [1]: 791.
                                                                                               
                                                                                               
webbrowser.open                    ‘url’                                                       *note [1]: 2bd4.
                                                                                               
                                                                                               
winreg.ConnectRegistry             ‘computer_name’, ‘key’                                      *note [1]: 34d6.
                                                                                               
                                                                                               
winreg.CreateKey                   ‘key’, ‘sub_key’, ‘access’                                  *note [1]: 34d7.*note [2]: 34d8.
                                                                                               
                                                                                               
winreg.DeleteKey                   ‘key’, ‘sub_key’, ‘access’                                  *note [1]: 34d9.*note [2]: 34da.
                                                                                               
                                                                                               
winreg.DeleteValue                 ‘key’, ‘value’                                              *note [1]: 34db.
                                                                                               
                                                                                               
winreg.DisableReflectionKey        ‘key’                                                       *note [1]: 34dc.
                                                                                               
                                                                                               
winreg.EnableReflectionKey         ‘key’                                                       *note [1]: 34dd.
                                                                                               
                                                                                               
winreg.EnumKey                     ‘key’, ‘index’                                              *note [1]: 34de.
                                                                                               
                                                                                               
winreg.EnumValue                   ‘key’, ‘index’                                              *note [1]: 34df.
                                                                                               
                                                                                               
winreg.ExpandEnvironmentStrings    ‘str’                                                       *note [1]: 34e0.
                                                                                               
                                                                                               
winreg.LoadKey                     ‘key’, ‘sub_key’, ‘file_name’                               *note [1]: 34e1.
                                                                                               
                                                                                               
winreg.OpenKey                     ‘key’, ‘sub_key’, ‘access’                                  *note [1]: 34e2.
                                                                                               
                                                                                               
winreg.OpenKey/result              ‘key’                                                       *note [1]: 34d7.*note [2]: 34d8.*note [3]: 34e2.
                                                                                               
                                                                                               
winreg.PyHKEY.Detach               ‘key’                                                       *note [1]: 34e3.
                                                                                               
                                                                                               
winreg.QueryInfoKey                ‘key’                                                       *note [1]: 34e4.
                                                                                               
                                                                                               
winreg.QueryReflectionKey          ‘key’                                                       *note [1]: 34e5.
                                                                                               
                                                                                               
winreg.QueryValue                  ‘key’, ‘sub_key’, ‘value_name’                              *note [1]: 34e6.*note [2]: 34e7.
                                                                                               
                                                                                               
winreg.SaveKey                     ‘key’, ‘file_name’                                          *note [1]: 34e8.
                                                                                               
                                                                                               
winreg.SetValue                    ‘key’, ‘sub_key’, ‘type’, ‘value’                           *note [1]: 34e9.*note [2]: 34ea.
                                                                                               

The following events are raised internally and do not correspond to any
public API of CPython:

Audit event                    Arguments
                               
-------------------------------------------------------------------------------
                               
_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://www.python.org/dev/peps/pep-0578


File: python.info,  Node: bdb --- Debugger framework,  Next: faulthandler --- Dump the Python traceback,  Prev: Audit events table,  Up: Debugging and Profiling

5.27.2 ‘bdb’ — Debugger framework
---------------------------------

`Source code:' Lib/bdb.py(1)

__________________________________________________________________

The *note bdb: f. module handles basic debugger functions, like setting
breakpoints or managing execution via the debugger.

The following exception is defined:

 -- 例外: bdb.BdbQuit

     Exception raised by the *note Bdb: c9d. class for quitting the
     debugger.

The *note bdb: f. module also defines two classes:

 -- 類別: bdb.Breakpoint (self, file, line, temporary=0, 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
     ‘bpbynumber’ and by ‘(file, line)’ pairs through ‘bplist’.  The
     former points to a single instance of class *note Breakpoint: 34ee.
     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 filename should be in
     canonical form.  If a `funcname' is defined, a breakpoint hit will
     be counted when the first line of that function is executed.  A
     conditional breakpoint always counts a hit.

     *note Breakpoint: 34ee. instances have the following methods:

      -- 成員函式: 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:

             * The breakpoint number.

             * If it is temporary or not.

             * Its file,line position.

             * The condition that causes a break.

             * If it must be ignored the next N times.

             * The breakpoint hit count.

          3.2 版新加入.

      -- 成員函式: bpprint (out=None)

          Print the output of *note bpformat(): 34f2. to the file `out',
          or if it is ‘None’, to standard output.

 -- 類別: bdb.Bdb (skip=None)

     The *note Bdb: c9d. 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: 571.) 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 版新加入: The `skip' argument.

     The following methods of *note Bdb: c9d. normally don’t need to be
     overridden.

      -- 成員函式: canonic (filename)

          Auxiliary method for getting a filename in a canonical form,
          that is, as a case-normalized (on case-insensitive
          filesystems) absolute path, stripped of surrounding angle
          brackets.

      -- 成員函式: reset ()

          Set the ‘botframe’, ‘stopframe’, ‘returnframe’ and ‘quitting’
          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(): e43. for more
          information on the trace function.  For more information on
          code and frame objects, refer to *note The standard type
          hierarchy: 1426.

      -- 成員函式: dispatch_line (frame)

          If the debugger should stop on the current line, invoke the
          *note user_line(): 34f8. method (which should be overridden in
          subclasses).  Raise a *note BdbQuit: 34ed. exception if the
          ‘Bdb.quitting’ flag is set (which can be set from *note
          user_line(): 34f8.).  Return a reference to the *note
          trace_dispatch(): 34f6. 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(): 34fa. method (which should be overridden in
          subclasses).  Raise a *note BdbQuit: 34ed. exception if the
          ‘Bdb.quitting’ flag is set (which can be set from *note
          user_call(): 34fa.).  Return a reference to the *note
          trace_dispatch(): 34f6. 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(): 34fc. method (which should be
          overridden in subclasses).  Raise a *note BdbQuit: 34ed.
          exception if the ‘Bdb.quitting’ flag is set (which can be set
          from *note user_return(): 34fc.).  Return a reference to the
          *note trace_dispatch(): 34f6. method for further tracing in
          that scope.

      -- 成員函式: dispatch_exception (frame, arg)

          If the debugger should stop at this exception, invokes the
          *note user_exception(): 34fe. method (which should be
          overridden in subclasses).  Raise a *note BdbQuit: 34ed.
          exception if the ‘Bdb.quitting’ flag is set (which can be set
          from *note user_exception(): 34fe.).  Return a reference to
          the *note trace_dispatch(): 34f6. 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.

      -- 成員函式: stop_here (frame)

          This method checks if the `frame' is somewhere below
          ‘botframe’ in the call stack.  ‘botframe’ is the frame in
          which debugging started.

      -- 成員函式: break_here (frame)

          This method checks if there is a breakpoint in the filename
          and line belonging to `frame' or, at least, in the current
          function.  If the breakpoint is a temporary one, this method
          deletes it.

      -- 成員函式: break_anywhere (frame)

          This method checks if there is a breakpoint in the filename of
          the current frame.

     Derived classes should override these methods to gain control over
     debugger operation.

      -- 成員函式: user_call (frame, argument_list)

          This method is called from *note dispatch_call(): 34f9. when
          there is the possibility that a break might be necessary
          anywhere inside the called function.

      -- 成員函式: user_line (frame)

          This method is called from *note dispatch_line(): 34f7. when
          either *note stop_here(): 34ff. or *note break_here(): 3500.
          yields ‘True’.

      -- 成員函式: user_return (frame, return_value)

          This method is called from *note dispatch_return(): 34fb. when
          *note stop_here(): 34ff. yields ‘True’.

      -- 成員函式: user_exception (frame, exc_info)

          This method is called from *note dispatch_exception(): 34fd.
          when *note stop_here(): 34ff. yields ‘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)

          Stop when the line with the line no 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.

      -- 成員函式: 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: 34ed. 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=0, cond,
               funcname)

          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(): 34f4. method.

      -- 成員函式: clear_break (filename, lineno)

          Delete the breakpoints in `filename' and `lineno'.  If none
          were set, an error message is returned.

      -- 成員函式: clear_bpbynumber (arg)

          Delete the breakpoint which has the index `arg' in the
          ‘Breakpoint.bpbynumber’.  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, an
          error message is returned.

      -- 成員函式: clear_all_breaks ()

          Delete all existing breakpoints.

      -- 成員函式: 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: 1fc. is raised.

          3.2 版新加入.

      -- 成員函式: get_break (filename, lineno)

          Check if there is a breakpoint for `lineno' of `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)

          Get a list of records for a frame and all higher (calling) and
          lower frames, and the size of the higher part.

      -- 成員函式: format_stack_entry (frame_lineno, lprefix=': ')

          Return a string with information about a stack entry,
          identified by a ‘(frame, lineno)’ tuple:

             * The canonical form of the filename which contains the
               frame.

             * The function name, or ‘"<lambda>"’.

             * The input arguments.

             * The return value.

             * 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: 1b97, given as a string.

      -- 成員函式: run (cmd, globals=None, locals=None)

          Debug a statement executed via the *note exec(): c49.
          function.  `globals' defaults to ‘__main__.__dict__’, `locals'
          defaults to `globals'.

      -- 成員函式: runeval (expr, globals=None, locals=None)

          Debug an expression executed via the *note eval(): b95.
          function.  `globals' and `locals' have the same meaning as in
          *note run(): 3516.

      -- 成員函式: runctx (cmd, globals, locals)

          For backwards compatibility.  Calls the *note run(): 3516.
          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)

     Check whether we should break here, depending on the way the
     breakpoint `b' was set.

     If it was set via line number, it checks if ‘b.line’ is the same as
     the one in the frame also passed as argument.  If the breakpoint
     was set via function name, we have to check we are in the right
     frame (the right function) and if we are in its first executable
     line.

 -- 函式: bdb.effective (file, line, frame)

     Determine if there is an effective (active) breakpoint at this line
     of code.  Return a tuple of the breakpoint and a boolean that
     indicates if it is ok to delete a temporary breakpoint.  Return
     ‘(None, None)’ if there is no matching breakpoint.

 -- 函式: bdb.set_trace ()

     Start debugging with a *note Bdb: c9d. instance from caller’s
     frame.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/bdb.py


File: python.info,  Node: faulthandler --- Dump the Python traceback,  Next: pdb --- The Python Debugger,  Prev: bdb --- Debugger framework,  Up: Debugging and Profiling

5.27.3 ‘faulthandler’ — Dump the Python traceback
-------------------------------------------------

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(): 54d. 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: 9cd.
environment variable or by using the *note -X: 156. ‘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: 314.
To see tracebacks, applications must be run in the terminal.  A log file
can alternatively be passed to *note faulthandler.enable(): 54d.

The module is implemented in C, so tracebacks can be dumped on a crash
or when Python is deadlocked.

* Menu:

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


File: python.info,  Node: Dumping the traceback,  Next: Fault handler state,  Up: faulthandler --- Dump the Python traceback

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.

     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 --- Dump the Python traceback

5.27.3.2 Fault handler state
............................

 -- 函式: faulthandler.enable (file=sys.stderr, all_threads=True)

     Enable the fault handler: install handlers for the ‘SIGSEGV’,
     ‘SIGFPE’, ‘SIGABRT’, ‘SIGBUS’ and ‘SIGILL’ 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: 3520.

     3.5 版更變: Added support for passing file descriptor to this
     function.

     3.6 版更變: On Windows, a handler for Windows exception is also
     installed.

 -- 函式: faulthandler.disable ()

     Disable the fault handler: uninstall the signal handlers installed
     by *note enable(): 54d.

 -- 函式: 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 --- Dump the Python traceback

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(): 3524. is called: see *note issue
     with file descriptors: 3520.

     This function is implemented using a watchdog thread.

     3.7 版更變: This function is now always available.

     3.5 版更變: Added support for passing file descriptor to this
     function.

 -- 函式: faulthandler.cancel_dump_traceback_later ()

     Cancel the last call to *note dump_traceback_later(): 6de.


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 --- Dump the Python traceback

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(): 3526.: see *note issue with file descriptors:
     3520.

     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(): 6dc.  Return ‘True’ if the
     signal was registered, ‘False’ otherwise.

     Not available on Windows.


File: python.info,  Node: Issue with file descriptors,  Next: Example<15>,  Prev: Dumping the traceback on a user signal,  Up: faulthandler --- Dump the Python traceback

5.27.3.5 Issue with file descriptors
....................................

*note enable(): 54d, *note dump_traceback_later(): 6de. and *note
register(): 6dc. 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(): 3c3. 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: Example<15>,  Prev: Issue with file descriptors,  Up: faulthandler --- Dump the Python traceback

5.27.3.6 Example
................

Example of a segmentation fault on Linux with and without enabling the
fault handler:

     $ python3 -c "import ctypes; ctypes.string_at(0)"
     Segmentation fault

     $ python3 -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: The Python Profilers,  Prev: faulthandler --- Dump the Python traceback,  Up: Debugging and Profiling

5.27.4 ‘pdb’ — The Python Debugger
----------------------------------

`Source code:' Lib/pdb.py(1)

__________________________________________________________________

The module *note pdb: ca. 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: 571.  This is currently undocumented but easily understood by
reading the source.  The extension interface uses the modules *note bdb:
f. and *note cmd: 1a.

The debugger’s prompt is ‘(Pdb)’.  Typical usage to run a program under
control of the debugger is:

     >>> import pdb
     >>> import mymodule
     >>> pdb.run('mymodule.test()')
     > <string>(0)?()
     (Pdb) continue
     > <string>(1)?()
     (Pdb) continue
     NameError: 'spam'
     > <string>(1)?()
     (Pdb)

3.3 版更變: Tab-completion via the *note readline: df. module is
available for commands and command arguments, e.g.  the current global
and local names are offered as arguments of the ‘p’ command.

‘pdb.py’ can also be invoked as a script to debug other scripts.  For
example:

     python3 -m pdb myscript.py

When invoked as a script, 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 版新加入: ‘pdb.py’ now accepts a ‘-c’ option that executes commands
as if given in a ‘.pdbrc’ file, see *note Debugger Commands: 352c.

3.7 版新加入: ‘pdb.py’ now accepts a ‘-m’ option that execute modules
similar to the way ‘python3 -m’ does.  As with a script, the debugger
will pause execution just before the first line of the module.

The typical usage to break into the debugger from a running program is
to insert

     import pdb; pdb.set_trace()

at the location you want to break into the debugger.  You can then step
through the code following this statement, and continue running without
the debugger using the *note continue: 352d. command.

3.7 版新加入: The built-in *note breakpoint(): 2fe, when called with
defaults, can be used instead of ‘import pdb; pdb.set_trace()’.

The typical usage to inspect a crashed program is:

     >>> import pdb
     >>> import mymodule
     >>> mymodule.test()
     Traceback (most recent call last):
       File "<stdin>", line 1, in <module>
       File "./mymodule.py", line 4, in test
         test2()
       File "./mymodule.py", line 3, in test2
         print(spam)
     NameError: spam
     >>> pdb.pm()
     > ./mymodule.py(3)test2()
     -> print(spam)
     (Pdb)

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: 352d, or
     you can step through the statement using *note step: 352e. or *note
     next: 352f. (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(): c49. or *note eval(): b95. 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(): 3530. returns, it
     returns the value of the expression.  Otherwise this function is
     similar to *note run(): 3310.

 -- 函式: pdb.runcall (function, *args, **kwds)

     Call the `function' (a function or method object, not a string)
     with the given arguments.  When *note runcall(): 3531. 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'.

 -- 函式: 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 traceback found in *note
     sys.last_traceback: 3533.

The ‘run*’ functions and *note set_trace(): 3c7. are aliases for
instantiating the *note Pdb: 571. 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: 571. is the debugger class.

     The `completekey', `stdin' and `stdout' arguments are passed to the
     underlying *note cmd.Cmd: 313b. 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.  (2)

     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
     ‘continue’ 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()

     Raises an *note auditing event: e96. ‘pdb.Pdb’ with no arguments.

     3.1 版新加入: The `skip' argument.

     3.2 版新加入: The `nosigint' argument.  Previously, a SIGINT
     handler was never set by Pdb.

     3.6 版更變: The `readrc' argument.

      -- 成員函式: 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.8/Lib/pdb.py

   (2) (1) 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: 3539. 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.

The debugger supports *note aliases: 353a.  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.

If a file ‘.pdbrc’ exists in the user’s home directory or in the current
directory, it is read in and executed as if it had been typed at the
debugger prompt.  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: 352d. or *note next: 352f.  Previously, these
commands had no effect.

 -- 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:
     ca. 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 there in the current file.
     With a `function' argument, set a break at the first executable
     statement within that function.  The line number may be prefixed
     with a filename and a colon, to specify a breakpoint in another
     file (probably one that hasn’t been loaded yet).  The file is
     searched on *note sys.path: 48d.  Note that each breakpoint is
     assigned a number to which all the other breakpoint commands refer.

     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.

 -- 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: 353f.

 -- Pdbcommand: cl(ear) [filename:lineno | bpnumber [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: 352d. command, or *note step: 352e,
     or any other command that resumes execution.

     Specifying any command resuming execution (currently *note
     continue: 352d, *note step: 352e, *note next: 352f, *note return:
     3547, *note jump: 3548, *note quit: 3549. 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: 352f.
     and *note step: 352e. is that *note step: 352e. stops inside a
     called function, while *note next: 352f. 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 a line number, continue execution until a line with a number
     greater or equal to that 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: c35. loop
     or out of a *note finally: 183. 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 版新加入: The ‘>>’ marker.

 -- Pdbcommand: ll | longlist

     List all source code for the current function or frame.
     Interesting lines are marked as for *note list: 3539.

     3.2 版新加入.

 -- Pdbcommand: a(rgs)

     Print the argument list of the current function.

 -- Pdbcommand: p expression

     Evaluate the `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(): 88b.
          function.

 -- Pdbcommand: pp expression

     Like the *note p: 88c. command, except the value of the expression
     is pretty-printed using the *note pprint: d3. module.

 -- Pdbcommand: whatis expression

     Print the type of the `expression'.

 -- Pdbcommand: source expression

     Try to get source code for the given object and display it.

     3.2 版新加入.

 -- Pdbcommand: display [expression]

     Display the value of the expression if it changed, each time
     execution stops in the current frame.

     Without expression, list all display expressions for the current
     frame.

     3.2 版新加入.

 -- Pdbcommand: undisplay [expression]

     Do not display the expression any more 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: 1b. module)
     whose global namespace contains all the (global and local) names
     found in the current scope.

     3.2 版新加入.

 -- 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 so on, while ‘%*’ is replaced by all
     the parameters.  If no command is given, 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("%1.",k,"=",%1.__dict__[k])
          # Print instance variables in self
          alias ps pi self

 -- Pdbcommand: unalias name

     Delete the specified alias.

 -- 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.  To set a
     global variable, you can prefix the assignment command with a *note
     global: 1249. 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 an argument is supplied,
     it is split with *note shlex: e9. and the result is used as the new
     *note sys.argv: c00.  History, breakpoints, actions and debugger
     options are preserved.  *note restart: 3557. is an alias for *note
     run: 3556.

 -- Pdbcommand: q(uit)

     Quit from the debugger.  The program being executed is aborted.

 -- Pdbcommand: debug code

     Enter a recursive debugger that steps through the code argument
     (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 a function.

註解
....


File: python.info,  Node: The Python Profilers,  Next: timeit --- Measure execution time of small code snippets,  Prev: pdb --- The Python Debugger,  Up: Debugging and Profiling

5.27.5 The Python Profilers
---------------------------

`Source code:' Lib/profile.py(1) and 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?::
* Limitations::
* Calibration::
* Using a custom timer::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/profile.py

   (2) https://github.com/python/cpython/tree/3.8/Lib/pstats.py


File: python.info,  Node: Introduction to the profilers,  Next: Instant User's Manual,  Up: The Python Profilers

5.27.5.1 Introduction to the profilers
......................................

*note cProfile: 28. and *note profile: d4. 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: d5. module.

The Python standard library provides two different implementations of
the same profiling interface:

  1. *note cProfile: 28. 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: d4, a pure Python module whose interface is imitated
     by *note cProfile: 28, 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: 10c. 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: The Python Profilers

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: d4. instead of *note cProfile: 28. if the latter is
not available on your system.)

The above action would run *note re.compile(): 44f. and print profile
results like the following:

           197 function calls (192 primitive calls) in 0.002 seconds

     Ordered by: standard name

     ncalls  tottime  percall  cumtime  percall filename:lineno(function)
          1    0.000    0.000    0.001    0.001 <string>:1(<module>)
          1    0.000    0.000    0.001    0.001 re.py:212(compile)
          1    0.000    0.000    0.001    0.001 re.py:268(_compile)
          1    0.000    0.000    0.000    0.000 sre_compile.py:172(_compile_charset)
          1    0.000    0.000    0.000    0.000 sre_compile.py:201(_optimize_charset)
          4    0.000    0.000    0.000    0.000 sre_compile.py:25(_identityfunction)
        3/1    0.000    0.000    0.000    0.000 sre_compile.py:33(_compile)

The first line indicates that 197 calls were monitored.  Of those calls,
192 were `primitive', meaning that the call was not induced via
recursion.  The next line: ‘Ordered by: standard name’, indicates that
the text string in the far right column was used to sort the output.
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: 3561. class reads profile results from a file
and formats them in various ways.

The files *note cProfile: 28. and *note profile: d4. 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(): 3562. 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 版新加入: Added the ‘-m’ option to *note cProfile: 28.

     3.8 版新加入: Added the ‘-m’ option to *note profile: d4.

The *note pstats: d5. module’s *note Stats: 3561. 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(): 3563. method removed the extraneous path from
all the module names.  The *note sort_stats(): 3562. method sorted all
the entries according to the standard module/line/name string that is
printed.  The *note print_stats(): 3564. 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: d5. module is a statistics
browser for reading and examining profile dumps.  It has a simple
line-oriented interface (implemented using *note cmd: 1a.) and
interactive help.


File: python.info,  Node: profile and cProfile Module Reference,  Next: The Stats Class,  Prev: Instant User's Manual,  Up: The Python Profilers

5.27.5.3 ‘profile’ and ‘cProfile’ Module Reference
..................................................

Both the *note profile: d4. and *note cProfile: 28. 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(): c49. 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: 3561. instance and prints a simple profiling report.  If the
     sort value is specified, it is passed to this *note Stats: 3561.
     instance to control how the results are sorted.

 -- 函式: profile.runctx (command, globals, locals, filename=None,
          sort=-1)

     This function is similar to *note run(): 3566, with added arguments
     to supply the globals and locals dictionaries for the `command'
     string.  This routine executes:

          exec(command, globals, locals)

     and gathers profiling statistics as in the *note run(): 3566.
     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: 1bc. 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: 1bc. class can also be used as a context manager
     (supported only in *note cProfile: 28. module.  see *note Context
     Manager Types: 148d.):

          import cProfile

          with cProfile.Profile() as pr:
              # ... do something ...

          pr.print_stats()

     3.8 版更變: Added context manager support.

      -- 成員函式: enable ()

          Start collecting profiling data.  Only in *note cProfile: 28.

      -- 成員函式: disable ()

          Stop collecting profiling data.  Only in *note cProfile: 28.

      -- 成員函式: create_stats ()

          Stop collecting profiling data and record the results
          internally as the current profile.

      -- 成員函式: print_stats (sort=-1)

          Create a *note Stats: 3561. object based on the current
          profile and print the results to stdout.

      -- 成員函式: dump_stats (filename)

          Write the results of the current profile to `filename'.

      -- 成員函式: run (cmd)

          Profile the cmd via *note exec(): c49.

      -- 成員函式: runctx (cmd, globals, locals)

          Profile the cmd via *note exec(): c49. 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(): ce7. 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: The Python Profilers

5.27.5.4 The ‘Stats’ Class
..........................

Analysis of the profiler data is done using the *note Stats: 3561.
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: d4. or *note
     cProfile: 28.  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: 3561. object, the
     *note add(): 3571. method can be used.

     Instead of reading the profile data from a file, a
     ‘cProfile.Profile’ or *note profile.Profile: 1bc. object can be
     used as the profile data source.

     *note Stats: 3561. objects have the following methods:

      -- 成員函式: strip_dirs ()

          This method for the *note Stats: 3561. 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(): 3563. 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: 3561. 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(): 3566. 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: 3561. 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: 1bc. and ‘cProfile.Profile’ classes.

      -- 成員函式: sort_stats (*keys)

          This method modifies the *note Stats: 3561. 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            Meaning
                                                           
          ----------------------------------------------------------------------------
                                                           
          ‘'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              line number
                                                           
                                                           
          ‘'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: 3561. 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: 3561. class prints out a
          report as described in the *note profile.run(): 3566.
          definition.

          The order of the printing is based on the last *note
          sort_stats(): 3562. operation done on the object (subject to
          caveats in *note add(): 3571. and *note strip_dirs(): 3563.).

          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: 3561. 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(): 3564, 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: d4, 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: 28, 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: 3561. 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(): 3574. method.


File: python.info,  Node: What Is Deterministic Profiling?,  Next: Limitations,  Prev: The Stats Class,  Up: The Python Profilers

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: Limitations,  Next: Calibration,  Prev: What Is Deterministic Profiling?,  Up: The Python Profilers

5.27.5.6 Limitations
....................

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: d4. than with the
lower-overhead *note cProfile: 28.  For this reason, *note profile: d4.
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: Calibration,  Next: Using a custom timer,  Prev: Limitations,  Up: The Python Profilers

5.27.5.7 Calibration
....................

The profiler of the *note profile: d4. 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 Limitations: 3579.).

     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 Mac OS X,
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: Calibration,  Up: The Python Profilers

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: 1bc. or ‘cProfile.Profile’,
‘your_time_func’’s return value will be interpreted differently:

*note profile.Profile: 1bc.

     ‘your_time_func’ should return a single number, or a list of
     numbers whose sum is the current time (like what *note os.times():
     a61. 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 Calibration: 357b.).  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(): a61. 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: 10b. that can be
used to make precise measurements of process or wall-clock time.  For
example, see *note time.perf_counter(): 2ab.


File: python.info,  Node: timeit --- Measure execution time of small code snippets,  Next: trace --- Trace or track Python statement execution,  Prev: The Python Profilers,  Up: Debugging and Profiling

5.27.6 ‘timeit’ — Measure execution time of small code snippets
---------------------------------------------------------------

`Source code:' Lib/timeit.py(1)

__________________________________________________________________

This module provides a simple way to time small bits of Python code.  It
has both a *note 命令執行列介面: 3580. as well as a *note callable:
3581. one.  It avoids a number of common traps for measuring execution
times.  See also Tim Peters’ introduction to the "Algorithms" chapter in
the `Python Cookbook', published by O’Reilly.

* Menu:

* 基礎範例: 基礎範例<2>.
* Python Interface::
* 命令執行列介面::
* Examples: Examples<25>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/timeit.py


File: python.info,  Node: 基礎範例<2>,  Next: Python Interface,  Up: timeit --- Measure execution time of small code snippets

5.27.6.1 基礎範例
.................

The following example shows how the *note 命令執行列介面: 3580. can be
used to compare three different expressions:

     $ python3 -m timeit '"-".join(str(n) for n in range(100))'
     10000 loops, best of 5: 30.2 usec per loop
     $ python3 -m timeit '"-".join([str(n) for n in range(100)])'
     10000 loops, best of 5: 27.5 usec per loop
     $ python3 -m timeit '"-".join(map(str, range(100)))'
     10000 loops, best of 5: 23.2 usec per loop

This can be achieved from the *note Python Interface: 3581. with:

     >>> 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

A callable can also be passed from the *note Python Interface: 3581.:

     >>> timeit.timeit(lambda: "-".join(map(str, range(100))), number=10000)
     0.19665591977536678

Note however that *note timeit(): 776. will automatically determine the
number of repetitions only when the command-line interface is used.  In
the *note Examples: 3583. section you can find more advanced examples.


File: python.info,  Node: Python Interface,  Next: 命令執行列介面,  Prev: 基礎範例<2>,  Up: timeit --- Measure execution time of small code snippets

5.27.6.2 Python Interface
.........................

The module defines three convenience functions and a public class:

 -- 函式: timeit.timeit (stmt='pass', setup='pass', timer=<default
          timer>, number=1000000, globals=None)

     Create a *note Timer: 3585. instance with the given statement,
     `setup' code and `timer' function and run its *note timeit(): 5a1.
     method with `number' executions.  The optional `globals' argument
     specifies a namespace in which to execute the code.

     3.5 版更變: The optional `globals' parameter was added.

 -- 函式: timeit.repeat (stmt='pass', setup='pass', timer=<default
          timer>, repeat=5, number=1000000, globals=None)

     Create a *note Timer: 3585. instance with the given statement,
     `setup' code and `timer' function and run its *note repeat(): 3587.
     method with the given `repeat' count and `number' executions.  The
     optional `globals' argument specifies a namespace in which to
     execute the code.

     3.5 版更變: The optional `globals' parameter was added.

     3.7 版更變: Default value of `repeat' changed from 3 to 5.

 -- 函式: timeit.default_timer ()

     The default timer, which is always *note time.perf_counter(): 2ab.

     3.3 版更變: *note time.perf_counter(): 2ab. is now the default
     timer.

 -- 類別: timeit.Timer (stmt='pass', setup='pass', timer=<timer
          function>, globals=None)

     Class for timing execution speed of small code snippets.

     The constructor takes a statement to be timed, an additional
     statement used for setup, and a timer function.  Both statements
     default to ‘'pass'’; the timer function is platform-dependent (see
     the module doc string).  `stmt' and `setup' may also contain
     multiple statements separated by ‘;’ or newlines, as long as they
     don’t contain multi-line string literals.  The statement will by
     default be executed within timeit’s namespace; this behavior can be
     controlled by passing a namespace to `globals'.

     To measure the execution time of the first statement, use the *note
     timeit(): 5a1. method.  The *note repeat(): 3587. and *note
     autorange(): 5a0. methods are convenience methods to call *note
     timeit(): 5a1. multiple times.

     The execution time of `setup' is excluded from the overall timed
     execution run.

     The `stmt' and `setup' parameters can also take objects that are
     callable without arguments.  This will embed calls to them in a
     timer function that will then be executed by *note timeit(): 5a1.
     Note that the timing overhead is a little larger in this case
     because of the extra function calls.

     3.5 版更變: The optional `globals' parameter was added.

      -- 成員函式: timeit (number=1000000)

          Time `number' executions of the main statement.  This executes
          the setup statement once, and then returns the time it takes
          to execute the main statement a number of times, measured in
          seconds as a float.  The argument is the number of times
          through the loop, defaulting to one million.  The main
          statement, the setup statement and the timer function to be
          used are passed to the constructor.

               備註: By default, *note timeit(): 5a1. temporarily turns
               off *note garbage collection: ecd. during the timing.
               The advantage of this approach is that it makes
               independent timings more comparable.  The disadvantage is
               that GC may be an important component of the performance
               of the function being measured.  If so, GC can be
               re-enabled as the first statement in the `setup' string.
               For example:

                    timeit.Timer('for i in range(10): oct(i)', 'gc.enable()').timeit()

      -- 成員函式: autorange (callback=None)

          Automatically determine how many times to call *note timeit():
          5a1.

          This is a convenience function that calls *note timeit(): 5a1.
          repeatedly so that the total time >= 0.2 second, returning the
          eventual (number of loops, time taken for that number of
          loops).  It calls *note timeit(): 5a1. with increasing numbers
          from the sequence 1, 2, 5, 10, 20, 50, ...  until the time
          taken is at least 0.2 second.

          If `callback' is given and is not ‘None’, it will be called
          after each trial with two arguments: ‘callback(number,
          time_taken)’.

          3.6 版新加入.

      -- 成員函式: repeat (repeat=5, number=1000000)

          Call *note timeit(): 5a1. a few times.

          This is a convenience function that calls the *note timeit():
          5a1. repeatedly, returning a list of results.  The first
          argument specifies how many times to call *note timeit(): 5a1.
          The second argument specifies the `number' argument for *note
          timeit(): 5a1.

               備註: It’s tempting to calculate mean and standard
               deviation from the result vector and report these.
               However, this is not very useful.  In a typical case, the
               lowest value gives a lower bound for how fast your
               machine can run the given code snippet; higher values in
               the result vector are typically not caused by variability
               in Python’s speed, but by other processes interfering
               with your timing accuracy.  So the *note min(): 80e. of
               the result is probably the only number you should be
               interested in.  After that, you should look at the entire
               vector and apply common sense rather than statistics.

          3.7 版更變: Default value of `repeat' changed from 3 to 5.

      -- 成員函式: print_exc (file=None)

          Helper to print a traceback from the timed code.

          Typical use:

               t = Timer(...)       # outside the try/except
               try:
                   t.timeit(...)    # or t.repeat(...)
               except Exception:
                   t.print_exc()

          The advantage over the standard traceback is that source lines
          in the compiled template will be displayed.  The optional
          `file' argument directs where the traceback is sent; it
          defaults to *note sys.stderr: 314.


File: python.info,  Node: 命令執行列介面,  Next: Examples<25>,  Prev: Python Interface,  Up: timeit --- Measure execution time of small code snippets

5.27.6.3 命令執行列介面
.......................

When called as a program from the command line, the following form is
used:

     python -m timeit [-n N] [-r N] [-u U] [-s S] [-h] [statement ...]

Where the following options are understood:

 -- 程式選項: -n N, --number=N

     how many times to execute ’statement’

 -- 程式選項: -r N, --repeat=N

     how many times to repeat the timer (default 5)

 -- 程式選項: -s S, --setup=S

     statement to be executed once initially (default ‘pass’)

 -- 程式選項: -p, --process

     measure process time, not wallclock time, using *note
     time.process_time(): 2ac. instead of *note time.perf_counter():
     2ab, which is the default

     3.3 版新加入.

 -- 程式選項: -u, --unit=U

     specify a time unit for timer output; can select nsec, usec, msec,
     or sec

     3.5 版新加入.

 -- 程式選項: -v, --verbose

     print raw timing results; repeat for more digits precision

 -- 程式選項: -h, --help

     print a short usage message and exit

A multi-line statement may be given by specifying each line as a
separate statement argument; indented lines are possible by enclosing an
argument in quotes and using leading spaces.  Multiple *note -s: 358d.
options are treated similarly.

If *note -n: 358b. is not given, a suitable number of loops is
calculated by trying increasing numbers from the sequence 1, 2, 5, 10,
20, 50, ...  until the total time is at least 0.2 seconds.

*note default_timer(): 3588. measurements can be affected by other
programs running on the same machine, so the best thing to do when
accurate timing is necessary is to repeat the timing a few times and use
the best time.  The *note -r: 358c. option is good for this; the default
of 5 repetitions is probably enough in most cases.  You can use *note
time.process_time(): 2ac. to measure CPU time.

     備註: There is a certain baseline overhead associated with
     executing a pass statement.  The code here doesn’t try to hide it,
     but you should be aware of it.  The baseline overhead can be
     measured by invoking the program without arguments, and it might
     differ between Python versions.


File: python.info,  Node: Examples<25>,  Prev: 命令執行列介面,  Up: timeit --- Measure execution time of small code snippets

5.27.6.4 Examples
.................

It is possible to provide a setup statement that is executed only once
at the beginning:

     $ 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

     >>> 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

The same can be done using the *note Timer: 3585. class and its methods:

     >>> 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]

The following examples show how to time expressions that contain
multiple lines.  Here we compare the cost of using *note hasattr(): 44c.
vs.  *note try: d77./*note except: b43. to test for missing and present
object attributes:

     $ 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

To give the *note timeit: 10c. module access to functions you define,
you can pass a `setup' parameter which contains an import statement:

     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"))

Another option is to pass *note globals(): 15e7. to the `globals'
parameter, which will cause the code to be executed within your current
global namespace.  This can be more convenient than individually
specifying imports:

     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 --- Trace or track Python statement execution,  Next: tracemalloc --- Trace memory allocations,  Prev: timeit --- Measure execution time of small code snippets,  Up: Debugging and Profiling

5.27.7 ‘trace’ — Trace or track Python statement execution
----------------------------------------------------------

`Source code:' Lib/trace.py(1)

__________________________________________________________________

The *note trace: 113. 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.8/Lib/trace.py

   (2) https://coverage.readthedocs.io/


File: python.info,  Node: Command-Line Usage,  Next: Programmatic Interface,  Up: trace --- Trace or track Python statement execution

5.27.7.1 Command-Line Usage
...........................

The *note trace: 113. 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.

 -- 程式選項: --help

     Display usage and exit.

 -- 程式選項: --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: 113.  The *note –listfuncs: 359a. option is mutually
exclusive with the *note –trace: 359b. and *note –count: 359c. options.
When *note –listfuncs: 359a. is provided, neither *note –count: 359c.
nor *note –trace: 359b. are accepted, and vice versa.

 -- 程式選項: -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: 359d, *note –file: 359e. and *note –no-report:
     359f. below.

 -- 程式選項: -t, --trace

     Display lines as they are executed.

 -- 程式選項: -l, --listfuncs

     Display the functions executed by running the program.

 -- 程式選項: -r, --report

     Produce an annotated list from an earlier program run that used the
     *note –count: 359c. and *note –file: 359e. option.  This does not
     execute any code.

 -- 程式選項: -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
..................

 -- 程式選項: -f, --file=<file>

     Name of a file to accumulate counts over several tracing runs.
     Should be used with the *note –count: 359c. option.

 -- 程式選項: -C, --coverdir=<dir>

     Directory where the report files go.  The coverage report for
     ‘package.module’ is written to file
     ‘`dir'/`package'/`module'.cover’.

 -- 程式選項: -m, --missing

     When generating annotated listings, mark lines which were not
     executed with ‘>>>>>>’.

 -- 程式選項: -s, --summary

     When using *note –count: 359c. or *note –report: 35a0, write a
     brief summary to stdout for each file processed.

 -- 程式選項: -R, --no-report

     Do not generate annotated listings.  This is useful if you intend
     to make several runs with *note –count: 359c, and then produce a
     single set of annotated listings at the end.

 -- 程式選項: -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.

 -- 程式選項: --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.

 -- 程式選項: --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: 135a.


File: python.info,  Node: Programmatic Interface,  Prev: Command-Line Usage,  Up: trace --- Trace or track Python statement execution

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(): c49.

      -- 成員函式: 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: 35ab. object with the current tracing parameters.

      -- 成員函式: results ()

          Return a *note CoverageResults: 35af. object that contains the
          cumulative results of all previous calls to ‘run’, ‘runctx’
          and ‘runfunc’ for the given *note Trace: 35ab. instance.  Does
          not reset the accumulated trace results.

 -- 類別: trace.CoverageResults

     A container for coverage results, created by *note Trace.results():
     35ae.  Should not be created directly by the user.

      -- 成員函式: update (other)

          Merge in data from another *note CoverageResults: 35af.
          object.

      -- 成員函式: write_results (show_missing=True, summary=False,
               coverdir=None)

          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.

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 --- Trace memory allocations,  Prev: trace --- Trace or track Python statement execution,  Up: Debugging and Profiling

5.27.8 ‘tracemalloc’ — Trace memory allocations
-----------------------------------------------

3.4 版新加入.

`Source code:' 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:
1360. environment variable to ‘1’, or by using *note -X: 156.
‘tracemalloc’ command line option.  The *note tracemalloc.start(): 1354.
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: 1360. environment variable to ‘25’, or use the *note
-X: 156. ‘tracemalloc=25’ command line option.

* Menu:

* Examples: Examples<26>.
* API::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/tracemalloc.py


File: python.info,  Node: Examples<26>,  Next: API,  Up: tracemalloc --- Trace memory allocations

5.27.8.1 Examples
.................

* 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: Examples<26>

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: 1e. module allocated ‘244
KiB’ to build *note namedtuple: 1b8. types.

See *note Snapshot.statistics(): 35b6. for more options.


File: python.info,  Node: Compute differences,  Next: Get the traceback of a memory block,  Prev: Display the top 10,  Up: Examples<26>

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: a9. 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(): 35b8. method to analyze the snapshot
offline.  Then use the *note Snapshot.load(): 35b9. method reload the
snapshot.


File: python.info,  Node: Get the traceback of a memory block,  Next: Pretty top,  Prev: Compute differences,  Up: Examples<26>

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:
9b. module to load data (bytecode and constants) from modules: ‘870.1
KiB’.  The traceback is where the *note importlib: 9b. loaded data most
recently: on the ‘import pdb’ line of the *note doctest: 67. 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: Examples<26>

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

See *note Snapshot.statistics(): 35b6. for more options.


File: python.info,  Node: API,  Prev: Examples<26>,  Up: tracemalloc --- Trace memory allocations

5.27.8.6 API
............

* Menu:

* Functions: Functions<9>.
* DomainFilter::
* Filter::
* Frame::
* Snapshot::
* Statistic::
* StatisticDiff::
* Trace::
* Traceback::


File: python.info,  Node: Functions<9>,  Next: DomainFilter,  Up: API

5.27.8.7 Functions
..................

 -- 函式: tracemalloc.clear_traces ()

     Clear traces of memory blocks allocated by Python.

     See also *note stop(): 35bf.

 -- 函式: tracemalloc.get_object_traceback (obj)

     Get the traceback where the Python object `obj' was allocated.
     Return a *note Traceback: 404. instance, or ‘None’ if the *note
     tracemalloc: 115. module is not tracing memory allocations or did
     not trace the allocation of the object.

     See also *note gc.get_referrers(): ea9. and *note sys.getsizeof():
     35c0. functions.

 -- 函式: tracemalloc.get_traceback_limit ()

     Get the maximum number of frames stored in the traceback of a
     trace.

     The *note tracemalloc: 115. module must be tracing memory
     allocations to get the limit, otherwise an exception is raised.

     The limit is set by the *note start(): 1354. function.

 -- 函式: tracemalloc.get_traced_memory ()

     Get the current size and peak size of memory blocks traced by the
     *note tracemalloc: 115. module as a tuple: ‘(current: int, peak:
     int)’.

 -- 函式: tracemalloc.get_tracemalloc_memory ()

     Get the memory usage in bytes of the *note tracemalloc: 115. module
     used to store traces of memory blocks.  Return an *note int: 185.

 -- 函式: tracemalloc.is_tracing ()

     ‘True’ if the *note tracemalloc: 115. module is tracing Python
     memory allocations, ‘False’ otherwise.

     See also *note start(): 1354. and *note stop(): 35bf. functions.

 -- 函式: 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’.

     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(): 35c5. and *note
     Snapshot.statistics(): 35b6. methods.

     Storing more frames increases the memory and CPU overhead of the
     *note tracemalloc: 115. module.  Use the *note
     get_tracemalloc_memory(): 35c3. function to measure how much memory
     is used by the *note tracemalloc: 115. module.

     The *note PYTHONTRACEMALLOC: 1360. environment variable
     (‘PYTHONTRACEMALLOC=NFRAME’) and the *note -X: 156.
     ‘tracemalloc=NFRAME’ command line option can be used to start
     tracing at startup.

     See also *note stop(): 35bf, *note is_tracing(): 35c4. and *note
     get_traceback_limit(): 35c1. 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(): 35c6. function to take a snapshot of
     traces before clearing them.

     See also *note start(): 1354, *note is_tracing(): 35c4. and *note
     clear_traces(): 35be. functions.

 -- 函式: tracemalloc.take_snapshot ()

     Take a snapshot of traces of memory blocks allocated by Python.
     Return a new *note Snapshot: 35c7. instance.

     The snapshot does not include memory blocks allocated before the
     *note tracemalloc: 115. module started to trace memory allocations.

     Tracebacks of traces are limited to *note get_traceback_limit():
     35c1. frames.  Use the `nframe' parameter of the *note start():
     1354. function to store more frames.

     The *note tracemalloc: 115. module must be tracing memory
     allocations to take a snapshot, see the *note start(): 1354.
     function.

     See also the *note get_object_traceback(): 116b. function.


File: python.info,  Node: DomainFilter,  Next: Filter,  Prev: Functions<9>,  Up: API

5.27.8.8 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: 35ca.

          If `inclusive' is ‘False’ (exclude), match memory blocks not
          allocated in the address space *note domain: 35ca.

      -- 屬性: 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.9 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(): 1c7c. function for the syntax of
     `filename_pattern'.  The ‘'.pyc'’ file extension is replaced with
     ‘'.py'’.

     Examples:

        * ‘Filter(True, subprocess.__file__)’ only includes traces of
          the *note subprocess: fa. module

        * ‘Filter(False, tracemalloc.__file__)’ excludes traces of the
          *note tracemalloc: 115. module

        * ‘Filter(False, "<unknown>")’ excludes empty tracebacks

     3.5 版更變: The ‘'.pyo'’ file extension is no longer replaced with
     ‘'.py'’.

     3.6 版更變: Added the *note domain: 35cd. attribute.

      -- 屬性: 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: 35cf. at line number *note lineno: 35d0.

          If `inclusive' is ‘False’ (exclude), ignore memory blocks
          allocated in a file with a name matching *note
          filename_pattern: 35cf. at line number *note lineno: 35d0.

      -- 屬性: 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(): 35c1. function and *note
          Snapshot.traceback_limit: 35d2. attribute.


File: python.info,  Node: Frame,  Next: Snapshot,  Prev: Filter,  Up: API

5.27.8.10 Frame
...............

 -- 類別: tracemalloc.Frame

     Frame of a traceback.

     The *note Traceback: 404. class is a sequence of *note Frame: 35d4.
     instances.

      -- 屬性: filename

          Filename (‘str’).

      -- 屬性: lineno

          Line number (‘int’).


File: python.info,  Node: Snapshot,  Next: Statistic,  Prev: Frame,  Up: API

5.27.8.11 Snapshot
..................

 -- 類別: tracemalloc.Snapshot

     Snapshot of traces of memory blocks allocated by Python.

     The *note take_snapshot(): 35c6. 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: 35d8. instances
          grouped by `key_type'.

          See the *note Snapshot.statistics(): 35b6. 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: 35d9, *note
          StatisticDiff.size: 35da, absolute value of *note
          StatisticDiff.count_diff: 35db, *note Statistic.count: 35dc.
          and then by *note StatisticDiff.traceback: 35dd.

      -- 成員函式: dump (filename)

          Write the snapshot into a file.

          Use *note load(): 35b9. to reload the snapshot.

      -- 成員函式: filter_traces (filters)

          Create a new *note Snapshot: 35c7. instance with a filtered
          *note traces: 35df. sequence, `filters' is a list of *note
          DomainFilter: 5a5. and *note Filter: 35cc. instances.  If
          `filters' is an empty list, return a new *note Snapshot: 35c7.
          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: 5a5. instances are now also
          accepted in `filters'.

      -- 成員函式: classmethod load (filename)

          Load a snapshot from a file.

          See also *note dump(): 35b8.

      -- 成員函式: statistics (key_type: str, cumulative: bool=False)

          Get statistics as a sorted list of *note Statistic: 35e0.
          instances grouped by `key_type':

          key_type                  description
                                    
          -------------------------------------------------------
                                    
          ‘'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: 35e1, *note Statistic.count: 35dc. and
          then by *note Statistic.traceback: 35e2.

      -- 屬性: traceback_limit

          Maximum number of frames stored in the traceback of *note
          traces: 35df.: result of the *note get_traceback_limit():
          35c1. when the snapshot was taken.

      -- 屬性: traces

          Traces of all memory blocks allocated by Python: sequence of
          *note Trace: 35e3. instances.

          The sequence has an undefined order.  Use the *note
          Snapshot.statistics(): 35b6. method to get a sorted list of
          statistics.


File: python.info,  Node: Statistic,  Next: StatisticDiff,  Prev: Snapshot,  Up: API

5.27.8.12 Statistic
...................

 -- 類別: tracemalloc.Statistic

     Statistic on memory allocations.

     *note Snapshot.statistics(): 35b6. returns a list of *note
     Statistic: 35e0. instances.

     See also the *note StatisticDiff: 35d8. 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: 404. instance.


File: python.info,  Node: StatisticDiff,  Next: Trace,  Prev: Statistic,  Up: API

5.27.8.13 StatisticDiff
.......................

 -- 類別: tracemalloc.StatisticDiff

     Statistic difference on memory allocations between an old and a new
     *note Snapshot: 35c7. instance.

     *note Snapshot.compare_to(): 35c5. returns a list of *note
     StatisticDiff: 35d8. instances.  See also the *note Statistic:
     35e0. 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: 404. instance.


File: python.info,  Node: Trace,  Next: Traceback,  Prev: StatisticDiff,  Up: API

5.27.8.14 Trace
...............

 -- 類別: tracemalloc.Trace

     Trace of a memory block.

     The *note Snapshot.traces: 35df. attribute is a sequence of *note
     Trace: 35e3. instances.

     3.6 版更變: Added the *note domain: 35e8. attribute.

      -- 屬性: 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: 404. instance.


File: python.info,  Node: Traceback,  Prev: Trace,  Up: API

5.27.8.15 Traceback
...................

 -- 類別: tracemalloc.Traceback

     Sequence of *note Frame: 35d4. 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(): 35c1. frames.  See the *note
     take_snapshot(): 35c6. function.

     The *note Trace.traceback: 35ea. attribute is an instance of *note
     Traceback: 404. instance.

     3.7 版更變: Frames are now sorted from the oldest to the most
     recent, instead of most recent to oldest.

      -- 成員函式: format (limit=None, most_recent_first=False)

          Format the traceback as a list of lines with newlines.  Use
          the *note linecache: a9. 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(): 35ec. function,
          except that *note format(): 405. does not include newlines.

          Example:

               print("Traceback (most recent call first):")
               for line in traceback:
                   print(line)

          Output:

               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 Services,  Prev: Debugging and Profiling,  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:

* distutils: distutils --- Building and installing Python modules. Building and installing Python modules
* ensurepip: ensurepip --- Bootstrapping the pip installer. Bootstrapping the pip installer
* venv: venv --- Creation of virtual environments. Creation of virtual environments
* zipapp: zipapp --- Manage executable Python zip archives. Manage executable Python zip archives

   ---------- Footnotes ----------

   (1) https://pypi.org


File: python.info,  Node: distutils --- Building and installing Python modules,  Next: ensurepip --- Bootstrapping the pip installer,  Up: 軟體封裝與發布

5.28.1 ‘distutils’ — Building and installing Python modules
-----------------------------------------------------------

__________________________________________________________________

The *note distutils: 39. package provides support for building and
installing additional modules into a Python installation.  The new
modules may be either 100%-pure Python, or may be extension modules
written in C, or may be collections of Python packages which include
modules coded in both Python and C.

Most Python users will `not' want to use this module directly, but
instead use the cross-version tools maintained by the Python Packaging
Authority.  In particular, setuptools(1) is an enhanced alternative to
*note distutils: 39. that provides:

   * support for declaring project dependencies

   * additional mechanisms for configuring which files to include in
     source releases (including plugins for integration with version
     control systems)

   * the ability to declare project "entry points", which can be used as
     the basis for application plugin systems

   * the ability to automatically generate Windows command line
     executables at installation time rather than needing to prebuild
     them

   * consistent behaviour across all supported Python versions

The recommended pip(2) installer runs all ‘setup.py’ scripts with
‘setuptools’, even if the script itself only imports ‘distutils’.  Refer
to the Python Packaging User Guide(3) for more information.

For the benefits of packaging tool authors and users seeking a deeper
understanding of the details of the current packaging and distribution
system, the legacy *note distutils: 39. based user documentation and API
reference remain available:

   * *note 安裝 Python 模組（舊版）: 7fc.

   * *note 發布 Python 模組（舊版）: 7fd.

   ---------- Footnotes ----------

   (1) https://setuptools.readthedocs.io/en/latest/

   (2) https://pip.pypa.io/

   (3) https://packaging.python.org


File: python.info,  Node: ensurepip --- Bootstrapping the pip installer,  Next: venv --- Creation of virtual environments,  Prev: distutils --- Building and installing Python modules,  Up: 軟體封裝與發布

5.28.2 ‘ensurepip’ — Bootstrapping the ‘pip’ installer
------------------------------------------------------

3.4 版新加入.

__________________________________________________________________

The *note ensurepip: 7a. package provides support for bootstrapping the
‘pip’ installer into an existing Python installation or virtual
environment.  This bootstrapping approach reflects the fact that ‘pip’
is an independent project with its own release cycle, and the latest
available stable version is bundled with maintenance and feature
releases of the CPython reference interpreter.

In most cases, end users of Python shouldn’t need to invoke this module
directly (as ‘pip’ should be bootstrapped by default), but it may be
needed if installing ‘pip’ was skipped when installing Python (or when
creating a virtual environment) or after explicitly uninstalling ‘pip’.

     備註: This module `does not' access the internet.  All of the
     components needed to bootstrap ‘pip’ are included as internal parts
     of the package.

也參考
......

*note 安裝 Python 模組: 7fa.

     The end user guide for installing Python packages

PEP 453(1): Explicit bootstrapping of pip in Python installations

     The original rationale and specification for this module.

* Menu:

* Command line interface::
* Module API::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0453


File: python.info,  Node: Command line interface,  Next: Module API,  Up: ensurepip --- Bootstrapping the pip installer

5.28.2.1 Command line interface
...............................

The command line interface is invoked using the interpreter’s ‘-m’
switch.

The simplest possible invocation is:

     python -m ensurepip

This invocation will install ‘pip’ if it is not already installed, but
otherwise does nothing.  To ensure the installed version of ‘pip’ is at
least as recent as the one bundled with ‘ensurepip’, pass the
‘--upgrade’ option:

     python -m ensurepip --upgrade

By default, ‘pip’ is installed into the current virtual environment (if
one is active) or into the system site packages (if there is no active
virtual environment).  The installation location can be controlled
through two additional command line options:

   * ‘--root <dir>’: Installs ‘pip’ relative to the given root directory
     rather than the root of the currently active virtual environment
     (if any) or the default root for the current Python installation.

   * ‘--user’: Installs ‘pip’ into the user site packages directory
     rather than globally for the current Python installation (this
     option is not permitted inside an active virtual environment).

By default, the scripts ‘pipX’ and ‘pipX.Y’ will be installed (where X.Y
stands for the version of Python used to invoke ‘ensurepip’).  The
scripts installed can be controlled through two additional command line
options:

   * ‘--altinstall’: if an alternate installation is requested, the
     ‘pipX’ script will `not' be installed.

   * ‘--default-pip’: if a "default pip" installation is requested, the
     ‘pip’ script will be installed in addition to the two regular
     scripts.

Providing both of the script selection options will trigger an
exception.


File: python.info,  Node: Module API,  Prev: Command line interface,  Up: ensurepip --- Bootstrapping the pip installer

5.28.2.2 Module API
...................

*note ensurepip: 7a. exposes two functions for programmatic use:

 -- 函式: ensurepip.version ()

     Returns a string specifying the bundled version of pip that will be
     installed when bootstrapping an environment.

 -- 函式: ensurepip.bootstrap (root=None, upgrade=False, user=False,
          altinstall=False, default_pip=False, verbosity=0)

     Bootstraps ‘pip’ into the current or designated environment.

     `root' specifies an alternative root directory to install relative
     to.  If `root' is ‘None’, then installation uses the default
     install location for the current environment.

     `upgrade' indicates whether or not to upgrade an existing
     installation of an earlier version of ‘pip’ to the bundled version.

     `user' indicates whether to use the user scheme rather than
     installing globally.

     By default, the scripts ‘pipX’ and ‘pipX.Y’ will be installed
     (where X.Y stands for the current version of Python).

     If `altinstall' is set, then ‘pipX’ will `not' be installed.

     If `default_pip' is set, then ‘pip’ will be installed in addition
     to the two regular scripts.

     Setting both `altinstall' and `default_pip' will trigger *note
     ValueError: 1fc.

     `verbosity' controls the level of output to *note sys.stdout: 313.
     from the bootstrapping operation.

     Raises an *note auditing event: e96. ‘ensurepip.bootstrap’ with
     argument ‘root’.

          備註: The bootstrapping process has side effects on both
          ‘sys.path’ and ‘os.environ’.  Invoking the command line
          interface in a subprocess instead allows these side effects to
          be avoided.

          備註: The bootstrapping process may install additional modules
          required by ‘pip’, but other software should not assume those
          dependencies will always be present by default (as the
          dependencies may be removed in a future version of ‘pip’).


File: python.info,  Node: venv --- Creation of virtual environments,  Next: zipapp --- Manage executable Python zip archives,  Prev: ensurepip --- Bootstrapping the pip installer,  Up: 軟體封裝與發布

5.28.3 ‘venv’ — Creation of virtual environments
------------------------------------------------

3.3 版新加入.

`Source code:' Lib/venv/(1)

__________________________________________________________________

The *note venv: 126. module provides support for creating lightweight
"virtual environments" with their own site directories, optionally
isolated from system site directories.  Each virtual environment has its
own Python binary (which matches the version of the binary that was used
to create this environment) and can have its own independent set of
installed Python packages in its site directories.

See PEP 405(2) for more information about Python virtual environments.

也參考
......

Python Packaging User Guide: Creating and using virtual environments(3)

* Menu:

* Creating virtual environments::
* API: API<2>.
* An example of extending EnvBuilder::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/venv/

   (2) https://www.python.org/dev/peps/pep-0405

   (3) 
https://packaging.python.org/guides/installing-using-pip-and-virtual-environments/#creating-a-virtual-environment


File: python.info,  Node: Creating virtual environments,  Next: API<2>,  Up: venv --- Creation of virtual environments

5.28.3.1 Creating virtual environments
......................................

Creation of *note virtual environments: 35f9. is done by executing the
command ‘venv’:

     python3 -m venv /path/to/new/virtual/environment

Running this command creates the target directory (creating any parent
directories that don’t exist already) and places a ‘pyvenv.cfg’ file in
it with a ‘home’ key pointing to the Python installation from which the
command was run (a common name for the target directory is ‘.venv’).  It
also creates a ‘bin’ (or ‘Scripts’ on Windows) subdirectory containing a
copy/symlink of the Python binary/binaries (as appropriate for the
platform or arguments used at environment creation time).  It also
creates an (initially empty) ‘lib/pythonX.Y/site-packages’ subdirectory
(on Windows, this is ‘Lib\site-packages’).  If an existing directory is
specified, it will be re-used.

3.6 版後已棄用: ‘pyvenv’ was the recommended tool for creating virtual
environments for Python 3.3 and 3.4, and is deprecated in Python 3.6(1).

3.5 版更變: The use of ‘venv’ is now recommended for creating virtual
environments.

On Windows, invoke the ‘venv’ command as follows:

     c:\>c:\Python35\python -m venv c:\path\to\myenv

Alternatively, if you configured the ‘PATH’ and ‘PATHEXT’ variables for
your *note Python installation: 2da.:

     c:\>python -m venv c:\path\to\myenv

The command, if run with ‘-h’, will show the available options:

     usage: venv [-h] [--system-site-packages] [--symlinks | --copies] [--clear]
                 [--upgrade] [--without-pip] [--prompt PROMPT]
                 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.

     optional arguments:
       -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.

     Once an environment has been created, you may wish to activate it, e.g. by
     sourcing an activate script in its bin directory.

3.4 版更變: Installs pip by default, added the ‘--without-pip’ and
‘--copies’ options

3.4 版更變: In earlier versions, if the target directory already
existed, an error was raised, unless the ‘--clear’ or ‘--upgrade’ option
was provided.

     備註: While symlinks are supported on Windows, they are not
     recommended.  Of particular note is that double-clicking
     ‘python.exe’ in File Explorer will resolve the symlink eagerly and
     ignore the virtual environment.

     備註: On Microsoft Windows, it may be required to enable the
     ‘Activate.ps1’ script by setting the execution policy for the user.
     You can do this by issuing the following PowerShell command:

     PS C:> Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope
     CurrentUser

     See About Execution Policies(2) for more information.

The created ‘pyvenv.cfg’ file also includes the
‘include-system-site-packages’ key, set to ‘true’ if ‘venv’ is run with
the ‘--system-site-packages’ option, ‘false’ otherwise.

Unless the ‘--without-pip’ option is given, *note ensurepip: 7a. will be
invoked to bootstrap ‘pip’ into the virtual environment.

Multiple paths can be given to ‘venv’, in which case an identical
virtual environment will be created, according to the given options, at
each provided path.

Once a virtual environment has been created, it can be "activated" using
a script in the virtual environment’s binary directory.  The invocation
of the script is platform-specific (‘<venv>’ must be replaced by the
path of the directory containing the virtual environment):

Platform          Shell                 Command to activate virtual environment
                                        
--------------------------------------------------------------------------------------
                                        
POSIX             bash/zsh              $ source <venv>/bin/activate
                                        
                                        
                  fish                  $ .  <venv>/bin/activate.fish
                                        
                                        
                  csh/tcsh              $ source <venv>/bin/activate.csh
                                        
                                        
                  PowerShell Core       $ <venv>/bin/Activate.ps1
                                        
                                        
Windows           cmd.exe               C:\> <venv>\Scripts\activate.bat
                                        
                                        
                  PowerShell            PS C:\> <venv>\Scripts\Activate.ps1
                                        

When a virtual environment is active, the ‘VIRTUAL_ENV’ environment
variable is set to the path of the virtual environment.  This can be
used to check if one is running inside a virtual environment.

You don’t specifically `need' to activate an environment; activation
just prepends the virtual environment’s binary directory to your path,
so that "python" invokes the virtual environment’s Python interpreter
and you can run installed scripts without having to use their full path.
However, all scripts installed in a virtual environment should be
runnable without activating it, and run with the virtual environment’s
Python automatically.

You can deactivate a virtual environment by typing "deactivate" in your
shell.  The exact mechanism is platform-specific and is an internal
implementation detail (typically a script or shell function will be
used).

3.4 版新加入: ‘fish’ and ‘csh’ activation scripts.

3.8 版新加入: PowerShell activation scripts installed under POSIX for
PowerShell Core support.

     備註: A virtual environment is a Python environment such that the
     Python interpreter, libraries and scripts installed into it are
     isolated from those installed in other virtual environments, and
     (by default) any libraries installed in a "system" Python, i.e.,
     one which is installed as part of your operating system.

     A virtual environment is a directory tree which contains Python
     executable files and other files which indicate that it is a
     virtual environment.

     Common installation tools such as setuptools(3) and pip(4) work as
     expected with virtual environments.  In other words, when a virtual
     environment is active, they install Python packages into the
     virtual environment without needing to be told to do so explicitly.

     When a virtual environment is active (i.e., the virtual
     environment’s Python interpreter is running), the attributes *note
     sys.prefix: 35fa. and *note sys.exec_prefix: 35fb. point to the
     base directory of the virtual environment, whereas *note
     sys.base_prefix: 3045. and *note sys.base_exec_prefix: 35fc. point
     to the non-virtual environment Python installation which was used
     to create the virtual environment.  If a virtual environment is not
     active, then *note sys.prefix: 35fa. is the same as *note
     sys.base_prefix: 3045. and *note sys.exec_prefix: 35fb. is the same
     as *note sys.base_exec_prefix: 35fc. (they all point to a
     non-virtual environment Python installation).

     When a virtual environment is active, any options that change the
     installation path will be ignored from all *note distutils: 39.
     configuration files to prevent projects being inadvertently
     installed outside of the virtual environment.

     When working in a command shell, users can make a virtual
     environment active by running an ‘activate’ script in the virtual
     environment’s executables directory (the precise filename and
     command to use the file is shell-dependent), which prepends the
     virtual environment’s directory for executables to the ‘PATH’
     environment variable for the running shell.  There should be no
     need in other circumstances to activate a virtual environment;
     scripts installed into virtual environments have a "shebang" line
     which points to the virtual environment’s Python interpreter.  This
     means that the script will run with that interpreter regardless of
     the value of ‘PATH’.  On Windows, "shebang" line processing is
     supported if you have the Python Launcher for Windows installed
     (this was added to Python in 3.3 - see PEP 397(5) for more
     details).  Thus, double-clicking an installed script in a Windows
     Explorer window should run the script with the correct interpreter
     without there needing to be any reference to its virtual
     environment in ‘PATH’.

   ---------- Footnotes ----------

   (1) https://docs.python.org/dev/whatsnew/3.6.html#deprecated-features

   (2) https://go.microsoft.com/fwlink/?LinkID=135170

   (3) https://pypi.org/project/setuptools/

   (4) https://pypi.org/project/pip/

   (5) https://www.python.org/dev/peps/pep-0397


File: python.info,  Node: API<2>,  Next: An example of extending EnvBuilder,  Prev: Creating virtual environments,  Up: venv --- Creation of virtual environments

5.28.3.2 API
............

The high-level method described above makes use of a simple API which
provides mechanisms for third-party virtual environment creators to
customize environment creation according to their needs, the *note
EnvBuilder: 90d. class.

 -- 類別: venv.EnvBuilder (system_site_packages=False, clear=False,
          symlinks=False, upgrade=False, with_pip=False, prompt=None)

     The *note EnvBuilder: 90d. class accepts the following keyword
     arguments on instantiation:

        * ‘system_site_packages’ – a Boolean value indicating that the
          system Python site-packages should be available to the
          environment (defaults to ‘False’).

        * ‘clear’ – a Boolean value which, if true, will delete the
          contents of any existing target directory, before creating the
          environment.

        * ‘symlinks’ – a Boolean value indicating whether to attempt to
          symlink the Python binary rather than copying.

        * ‘upgrade’ – a Boolean value which, if true, will upgrade an
          existing environment with the running Python - for use when
          that Python has been upgraded in-place (defaults to ‘False’).

        * ‘with_pip’ – a Boolean value which, if true, ensures pip is
          installed in the virtual environment.  This uses *note
          ensurepip: 7a. with the ‘--default-pip’ option.

        * ‘prompt’ – a String to be used after virtual environment is
          activated (defaults to ‘None’ which means directory name of
          the environment would be used).

     3.4 版更變: Added the ‘with_pip’ parameter

     3.6 版新加入: Added the ‘prompt’ parameter

     Creators of third-party virtual environment tools will be free to
     use the provided *note EnvBuilder: 90d. class as a base class.

     The returned env-builder is an object which has a method, ‘create’:

      -- 成員函式: create (env_dir)

          Create a virtual environment by specifying the target
          directory (absolute or relative to the current directory)
          which is to contain the virtual environment.  The ‘create’
          method will either create the environment in the specified
          directory, or raise an appropriate exception.

          The ‘create’ method of the *note EnvBuilder: 90d. class
          illustrates the hooks available for subclass customization:

               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)

          Each of the methods *note ensure_directories(): 35ff, *note
          create_configuration(): 3600, *note setup_python(): 3601,
          *note setup_scripts(): 3602. and *note post_setup(): 3603. can
          be overridden.

      -- 成員函式: ensure_directories (env_dir)

          Creates the environment directory and all necessary
          directories, and returns a context object.  This is just a
          holder for attributes (such as paths), for use by the other
          methods.  The directories are allowed to exist already, as
          long as either ‘clear’ or ‘upgrade’ were specified to allow
          operating on an existing environment directory.

      -- 成員函式: 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.

      -- 成員函式: 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(): 3601. 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(): 3601. instead of *note setup_scripts(): 3602.
     This was not the case in 3.7.2.  When using symlinks, the original
     executables will be linked.

     In addition, *note EnvBuilder: 90d. provides this utility method
     that can be called from *note setup_scripts(): 3602. or *note
     post_setup(): 3603. 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: 1ee5. 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).

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)

     Create an *note EnvBuilder: 90d. with the given keyword arguments,
     and call its *note create(): 35fe. method with the `env_dir'
     argument.

     3.3 版新加入.

     3.4 版更變: Added the ‘with_pip’ parameter

     3.6 版更變: Added the ‘prompt’ parameter


File: python.info,  Node: An example of extending EnvBuilder,  Prev: API<2>,  Up: venv --- Creation of virtual environments

5.28.3.3 An example of extending ‘EnvBuilder’
.............................................

The following script shows how to extend *note EnvBuilder: 90d. 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://bitbucket.org/pypa/setuptools/downloads/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):
         compatible = True
         if sys.version_info < (3, 3):
             compatible = False
         elif not hasattr(sys, 'base_prefix'):
             compatible = False
         if not compatible:
             raise ValueError('This script is only for use with '
                              'Python 3.3 or later')
         else:
             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 --- Manage executable Python zip archives,  Prev: venv --- Creation of virtual environments,  Up: 軟體封裝與發布

5.28.4 ‘zipapp’ — Manage executable Python zip archives
-------------------------------------------------------

3.5 版新加入.

`Source code:' 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: 133f.  The module provides both a *note
命令執行列介面: 3609. and a *note Python API: 360a.

* Menu:

* Basic Example::
* 命令執行列介面: 命令執行列介面<2>.
* Python API::
* Examples: Examples<27>.
* Specifying the Interpreter::
* Creating Standalone Applications with zipapp::
* The Python Zip Application Archive Format::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/zipapp.py


File: python.info,  Node: Basic Example,  Next: 命令執行列介面<2>,  Up: zipapp --- Manage executable Python zip archives

5.28.4.1 Basic Example
......................

The following example shows how the *note 命令執行列介面: 3609. 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: 命令執行列介面<2>,  Next: Python API,  Prev: Basic Example,  Up: zipapp --- Manage executable Python zip archives

5.28.4.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:

 -- 程式選項: -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').

 -- 程式選項: -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.

 -- 程式選項: -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: 360f. cannot be specified when copying an archive.

 -- 程式選項: -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: 3610. has no effect when copying an archive.

     3.7 版新加入.

 -- 程式選項: --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.

 -- 程式選項: -h, --help

     Print a short usage message and exit.


File: python.info,  Node: Python API,  Next: Examples<27>,  Prev: 命令執行列介面<2>,  Up: zipapp --- Manage executable Python zip archives

5.28.4.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: 36f.
          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: 36f. 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: 36f,
          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 版新加入: Added the `filter' and `compressed' arguments.

 -- 函式: 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: 158.
     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: Examples<27>,  Next: Specifying the Interpreter,  Prev: Python API,  Up: zipapp --- Manage executable Python zip archives

5.28.4.4 Examples
.................

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(): 422. 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(): 422. 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
‘BytesIO’ 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: Examples<27>,  Up: zipapp --- Manage executable Python zip archives

5.28.4.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 --- Manage executable Python zip archives

5.28.4.6 Creating Standalone Applications with zipapp
.....................................................

Using the *note zipapp: 142. 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. Optionally, delete the ‘.dist-info’ directories created by pip in
     the ‘myapp’ directory.  These hold metadata for pip to manage the
     packages, and as you won’t be making any further use of pip they
     aren’t required - although it won’t do any harm if you leave them.

  4. 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: 3618. 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:

* Making a Windows executable::
* Caveats::


File: python.info,  Node: Making a Windows executable,  Next: Caveats,  Up: Creating Standalone Applications with zipapp

5.28.4.7 Making a Windows executable
....................................

On Windows, registration of the ‘.pyz’ extension is optional, and
furthermore, there are certain places that don’t recognise registered
extensions "transparently" (the simplest example is that
‘subprocess.run(['myapp'])’ won’t find your application - you need to
explicitly specify the extension).

On Windows, therefore, it is often preferable to create an executable
from the zipapp.  This is relatively easy, although it does require a C
compiler.  The basic approach relies on the fact that zipfiles can have
arbitrary data prepended, and Windows exe files can have arbitrary data
appended.  So by creating a suitable launcher and tacking the ‘.pyz’
file onto the end of it, you end up with a single-file executable that
runs your application.

A suitable launcher can be as simple as the following:

     #define Py_LIMITED_API 1
     #include "Python.h"

     #define WIN32_LEAN_AND_MEAN
     #include <windows.h>

     #ifdef WINDOWS
     int WINAPI wWinMain(
         HINSTANCE hInstance,      /* handle to current instance */
         HINSTANCE hPrevInstance,  /* handle to previous instance */
         LPWSTR lpCmdLine,         /* pointer to command line */
         int nCmdShow              /* show state of window */
     )
     #else
     int wmain()
     #endif
     {
         wchar_t **myargv = _alloca((__argc + 1) * sizeof(wchar_t*));
         myargv[0] = __wargv[0];
         memcpy(myargv + 1, __wargv, __argc * sizeof(wchar_t *));
         return Py_Main(__argc+1, myargv);
     }

If you define the ‘WINDOWS’ preprocessor symbol, this will generate a
GUI executable, and without it, a console executable.

To compile the executable, you can either just use the standard MSVC
command line tools, or you can take advantage of the fact that distutils
knows how to compile Python source:

     >>> from distutils.ccompiler import new_compiler
     >>> import distutils.sysconfig
     >>> import sys
     >>> import os
     >>> from pathlib import Path

     >>> def compile(src):
     >>>     src = Path(src)
     >>>     cc = new_compiler()
     >>>     exe = src.stem
     >>>     cc.add_include_dir(distutils.sysconfig.get_python_inc())
     >>>     cc.add_library_dir(os.path.join(sys.base_exec_prefix, 'libs'))
     >>>     # First the CLI executable
     >>>     objs = cc.compile([str(src)])
     >>>     cc.link_executable(objs, exe)
     >>>     # Now the GUI executable
     >>>     cc.define_macro('WINDOWS')
     >>>     objs = cc.compile([str(src)])
     >>>     cc.link_executable(objs, exe + 'w')

     >>> if __name__ == "__main__":
     >>>     compile("zastub.c")

The resulting launcher uses the "Limited ABI", so it will run unchanged
with any version of Python 3.x.  All it needs is for Python
(‘python3.dll’) to be on the user’s ‘PATH’.

For a fully standalone distribution, you can distribute the launcher
with your application appended, bundled with the Python "embedded"
distribution.  This will run on any PC with the appropriate architecture
(32 bit or 64 bit).


File: python.info,  Node: Caveats,  Prev: Making a Windows executable,  Up: Creating Standalone Applications with zipapp

5.28.4.8 Caveats
................

There are some limitations to the process of bundling your application
into a single file.  In most, if not all, cases they can be addressed
without needing major changes to your application.

  1. 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).

  2. If you are shipping a Windows executable as described above, you
     either need to ensure that your users have ‘python3.dll’ on their
     PATH (which is not the default behaviour of the installer) or you
     should bundle your application with the embedded distribution.

  3. The suggested launcher above uses the Python embedding API. This
     means that in your application, ‘sys.executable’ will be your
     application, and `not' a conventional Python interpreter.  Your
     code and its dependencies need to be prepared for this possibility.
     For example, if your application uses the *note multiprocessing:
     b8. module, it will need to call *note
     multiprocessing.set_executable(): 23cf. to let the module know
     where to find the standard Python interpreter.


File: python.info,  Node: The Python Zip Application Archive Format,  Prev: Creating Standalone Applications with zipapp,  Up: zipapp --- Manage executable Python zip archives

5.28.4.9 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: 48d. 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(): 4fb. on POSIX.

  2. Standard zipfile data, as generated by the *note zipfile: 143.
     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 Services,  Next: Custom Python Interpreters,  Prev: 軟體封裝與發布,  Up: Python 標準函式庫 Standard Library

5.29 Python Runtime Services
============================

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 --- System-specific parameters and functions. System-specific parameters and functions
* sysconfig: sysconfig --- Provide access to Python's configuration information. Provide access to Python’s configuration information
* builtins: builtins --- Built-in objects. Built-in objects
* __main__: __main__ --- Top-level script environment. Top-level script environment
* warnings: warnings --- Warning control. Warning control
* dataclasses: dataclasses --- Data Classes. Data Classes
* contextlib: contextlib --- Utilities for with-statement contexts. Utilities for with-statement contexts
* abc: abc --- Abstract Base Classes. Abstract Base Classes
* atexit: atexit --- Exit handlers. Exit handlers
* traceback: traceback --- Print or retrieve a stack traceback. Print or retrieve a stack traceback
* __future__: __future__ --- Future statement definitions. Future statement definitions
* gc: gc --- Garbage Collector interface. Garbage Collector interface
* inspect: inspect --- Inspect live objects. Inspect live objects
* site: site --- Site-specific configuration hook. Site-specific configuration hook


File: python.info,  Node: sys --- System-specific parameters and functions,  Next: sysconfig --- Provide access to Python's configuration information,  Up: Python Runtime Services

5.29.1 ‘sys’ — System-specific parameters and functions
-------------------------------------------------------

__________________________________________________________________

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.

 -- Data: 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.8 版更變: Default flags became an empty string (‘m’ flag for
     pymalloc has been removed).

     3.2 版新加入.

 -- 函式: 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():
     f2d. 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(): 34c8. 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.

     Calling *note sys.addaudithook(): 34c7. will itself raise an
     auditing event named ‘sys.addaudithook’ with no arguments.  If any
     existing hooks raise an exception derived from *note RuntimeError:
     2bb, the new hook will not be added and the exception suppressed.
     As a result, callers cannot assume that their hook has been added
     unless they control all existing hooks.

     See the *note audit events table: 34c4. for all events raised by
     CPython, and PEP 578(2) for the original design discussion.

     3.8 版新加入.

     3.8.1 版更變: Exceptions derived from *note Exception: 1aa. but not
     *note RuntimeError: 2bb. are no longer suppressed.

     `CPython implementation detail:' When tracing is enabled (see *note
     settrace(): e43.), 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.

 -- Data: 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: 1210. 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: 80. module.

          備註: 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.

     For example, one auditing event is named ‘os.chdir’.  This event
     has one argument called `path' that will contain the requested new
     working directory.

     *note sys.audit(): f2d. 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(): 34c7. or *note
     PySys_AddAuditHook(): 34c8. functions.

     The native equivalent of this function is *note PySys_Audit(): f3b.
     Using the native function is preferred when possible.

     See the *note audit events table: 34c4. for all events raised by
     CPython.

     3.8 版新加入.

 -- Data: sys.base_exec_prefix

     Set during Python startup, before ‘site.py’ is run, to the same
     value as *note exec_prefix: 35fb.  If not running in a *note
     virtual environment: 35f9, the values will stay the same; if
     ‘site.py’ finds that a virtual environment is in use, the values of
     *note prefix: 35fa. and *note exec_prefix: 35fb. will be changed to
     point to the virtual environment, whereas *note base_prefix: 3045.
     and *note base_exec_prefix: 35fc. will remain pointing to the base
     Python installation (the one which the virtual environment was
     created from).

     3.3 版新加入.

 -- Data: sys.base_prefix

     Set during Python startup, before ‘site.py’ is run, to the same
     value as *note prefix: 35fa.  If not running in a *note virtual
     environment: 35f9, the values will stay the same; if ‘site.py’
     finds that a virtual environment is in use, the values of *note
     prefix: 35fa. and *note exec_prefix: 35fb. will be changed to point
     to the virtual environment, whereas *note base_prefix: 3045. and
     *note base_exec_prefix: 35fc. will remain pointing to the base
     Python installation (the one which the virtual environment was
     created from).

     3.3 版新加入.

 -- Data: 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.

 -- Data: sys.builtin_module_names

     A tuple of strings giving 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.)

 -- 函式: 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 some other code.

 -- Data: 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.

 -- 函式: 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:
     114. 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.

     Raises an *note auditing event: e96. ‘sys._current_frames’ with no
     arguments.

 -- 函式: sys.breakpointhook ()

     This hook function is called by built-in *note breakpoint(): 2fe.
     By default, it drops you into the *note pdb: ca. 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: 319.  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():
     2fe. function.

     Note that if anything goes wrong while importing the callable named
     by *note PYTHONBREAKPOINT: 319, a *note RuntimeWarning: 2c1. is
     reported and the breakpoint is ignored.

     Also note that if ‘sys.breakpointhook()’ is overridden
     programmatically, *note PYTHONBREAKPOINT: 319. is `not' consulted.

     3.7 版新加入.

 -- 函式: sys._debugmallocstats ()

     Print low-level information to stderr about the state of CPython’s
     memory allocator.

     If Python is configured –with-pydebug, it also performs some
     expensive internal consistency checks.

     3.3 版新加入.

     `CPython implementation detail:' This function is specific to
     CPython.  The exact output format is not defined here, and may
     change.

 -- Data: sys.dllhandle

     Integer specifying the handle of the Python DLL.

     *note Availability: 1364.: 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: 3628. 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: 1fd.

 -- Data: 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: d3d. command line option and the
     *note PYTHONDONTWRITEBYTECODE: d3e. environment variable, but you
     can set it yourself to control bytecode file generation.

 -- Data: 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: 21. 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:
     156. ‘pycache_prefix=PATH’ command-line option or the *note
     PYTHONPYCACHEPREFIX: 155. 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 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: 2bb. 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(): 22e. function handles unraisable
     exceptions and the *note threading.excepthook(): 232. function
     handles exception raised by *note threading.Thread.run(): 233.

 -- Data: sys.__breakpointhook__
 -- Data: sys.__displayhook__
 -- Data: sys.__excepthook__
 -- Data: 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.exc_info ()

     This function returns a tuple of three values that give information
     about the exception that is currently being handled.  The
     information returned is specific both to the current thread and to
     the current stack frame.  If the current stack frame is not
     handling an exception, the information is taken from the calling
     stack frame, or its caller, and so on until a stack frame is found
     that is handling an exception.  Here, "handling an exception" is
     defined as "executing an except clause."  For any stack frame, only
     information about the exception being currently handled is
     accessible.

     If no exception is being handled anywhere on the stack, a tuple
     containing three ‘None’ values is returned.  Otherwise, the values
     returned are ‘(type, value, traceback)’.  Their meaning is: `type'
     gets the type of the exception being handled (a subclass of *note
     BaseException: 1a9.); `value' gets the exception instance (an
     instance of the exception type); `traceback' gets a *note traceback
     object: 33b. which encapsulates the call stack at the point where
     the exception originally occurred.

 -- Data: 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: 35f9. 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: 35fc.

 -- Data: 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: 275. will be an empty string or ‘None’.

 -- 函式: sys.exit ([arg])

     Exit from Python.  This is implemented by raising the *note
     SystemExit: 601. exception, so cleanup actions specified by finally
     clauses of *note try: d77. statements are honored, and it is
     possible to intercept the exit attempt at an outer level.

     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:
     314. 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(): 1614. ultimately "only" raises an exception, it
     will only exit the process when called from the main thread, and
     the exception is not intercepted.

     3.6 版更變: If an error occurs in the cleanup after the Python
     interpreter has caught *note SystemExit: 601. (such as an error
     flushing buffered data in the standard streams), the exit status is
     changed to 120.

 -- Data: sys.flags

     The *note named tuple: aa8. `flags' exposes the status of command
     line flags.  The attributes are read only.

     attribute                         flag
                                       
     --------------------------------------------------------------------
                                       
     ‘debug’                           *note -d: 1347.
                                       
                                       
     *note inspect: a1.                *note -i: e24.
                                       
                                       
     ‘interactive’                     *note -i: e24.
                                       
                                       
     ‘isolated’                        *note -I: 100d.
                                       
                                       
     ‘optimize’                        *note -O: 690. or
                                       *note -OO: 691.
                                       
                                       
     *note dont_write_bytecode: 3629.  *note -B: d3d.
                                       
                                       
     ‘no_user_site’                    *note -s: d1a.
                                       
                                       
     ‘no_site’                         *note -S: b29.
                                       
                                       
     ‘ignore_environment’              *note -E: 100e.
                                       
                                       
     ‘verbose’                         *note -v: d8d.
                                       
                                       
     ‘bytes_warning’                   *note -b: 41a.
                                       
                                       
     ‘quiet’                           *note -q: 134a.
                                       
                                       
     ‘hash_randomization’              *note -R: 1099.
                                       
                                       
     ‘dev_mode’                        *note -X: 156. ‘dev’
                                       
                                       
     ‘utf8_mode’                       *note -X: 156. ‘utf8’
                                       

     3.2 版更變: Added ‘quiet’ attribute for the new *note -q: 134a.
     flag.

     3.2.3 版新加入: The ‘hash_randomization’ attribute.

     3.3 版更變: Removed obsolete ‘division_warning’ attribute.

     3.4 版更變: Added ‘isolated’ attribute for *note -I: 100d.
     ‘isolated’ flag.

     3.7 版更變: Added ‘dev_mode’ attribute for the new *note -X: 156.
     ‘dev’ flag and ‘utf8_mode’ attribute for the new *note -X: 156.
     ‘utf8’ flag.

 -- Data: sys.float_info

     A *note named tuple: aa8. 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]: 362e, ’Characteristics
     of floating types’, for details.

     attribute                 float.h macro        explanation
                                                    
     ------------------------------------------------------------------------------------------------------
                                                    
     ‘epsilon’                 DBL_EPSILON          difference between 1.0 and the least value greater
                                                    than 1.0 that is representable as a float
                                                    
                                                    
     ‘dig’                     DBL_DIG              maximum number of decimal digits that can be
                                                    faithfully represented in a float; see below
                                                    
                                                    
     ‘mant_dig’                DBL_MANT_DIG         float precision: the number of base-‘radix’ digits
                                                    in the significand of a float
                                                    
                                                    
     *note max: 80f.           DBL_MAX              maximum representable positive finite float
                                                    
                                                    
     ‘max_exp’                 DBL_MAX_EXP          maximum integer `e' such that ‘radix**(e-1)’ is a
                                                    representable finite float
                                                    
                                                    
     ‘max_10_exp’              DBL_MAX_10_EXP       maximum integer `e' such that ‘10**e’ is in the
                                                    range of representable finite floats
                                                    
                                                    
     *note min: 80e.           DBL_MIN              minimum representable positive `normalized' float
                                                    
                                                    
     ‘min_exp’                 DBL_MIN_EXP          minimum integer `e' such that ‘radix**(e-1)’ is a
                                                    normalized float
                                                    
                                                    
     ‘min_10_exp’              DBL_MIN_10_EXP       minimum integer `e' such that ‘10**e’ is a
                                                    normalized float
                                                    
                                                    
     ‘radix’                   FLT_RADIX            radix of exponent representation
                                                    
                                                    
     ‘rounds’                  FLT_ROUNDS           integer constant representing the rounding mode used
                                                    for arithmetic operations.  This reflects the value
                                                    of the system FLT_ROUNDS macro at interpreter
                                                    startup time.  See section 5.2.4.2.2 of the C99
                                                    standard for an explanation of the possible values
                                                    and their meanings.
                                                    

     The attribute ‘sys.float_info.dig’ 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 ‘sys.float_info.dig’ significant
     digits, this isn’t always true:

          >>> s = '9876543211234567'    # 16 significant digits is too many!
          >>> format(float(s), '.16g')  # conversion changes value
          '9876543211234568'

 -- Data: sys.float_repr_style

     A string indicating how the *note repr(): 7d1. 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_type_cache(): 3625. and
     *note gc.collect(): 22f. to get more predictable results.

     If a Python build or implementation cannot reasonably compute this
     information, *note getallocatedblocks(): 8e7. is allowed to return
     0 instead.

     3.4 版新加入.

 -- 函式: sys.getandroidapilevel ()

     Return the build time API version of Android as an integer.

     *note Availability: 1364.: Android.

     3.7 版新加入.

 -- 函式: sys.getcheckinterval ()

     Return the interpreter’s "check interval"; see *note
     setcheckinterval(): 362f.

     3.2 版後已棄用: Use *note getswitchinterval(): 3630. instead.

 -- 函式: 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: c5. module (‘RTLD_xxx’ constants, e.g.  *note
     os.RTLD_LAZY: a64.).

     *note Availability: 1364.: Unix.

 -- 函式: sys.getfilesystemencoding ()

     Return the name of the encoding used to convert between Unicode
     filenames and bytes filenames.  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.

     This encoding is always ASCII-compatible.

     *note os.fsencode(): 4f4. and *note os.fsdecode(): 4f3. should be
     used to ensure that the correct encoding and errors mode are used.

        * In the UTF-8 mode, the encoding is ‘utf-8’ on any platform.

        * On macOS, the encoding is ‘'utf-8'’.

        * On Unix, the encoding is the locale encoding.

        * On Windows, the encoding may be ‘'utf-8'’ or ‘'mbcs'’,
          depending on user configuration.

        * On Android, the encoding is ‘'utf-8'’.

        * On VxWorks, the encoding is ‘'utf-8'’.

     3.2 版更變: *note getfilesystemencoding(): 4fb. result cannot be
     ‘None’ anymore.

     3.6 版更變: Windows is no longer guaranteed to return ‘'mbcs'’.
     See PEP 529(3) and *note _enablelegacywindowsfsencoding(): 4fd. for
     more information.

     3.7 版更變: Return ’utf-8’ in the UTF-8 mode.

 -- 函式: sys.getfilesystemencodeerrors ()

     Return the name of the error mode used to convert between Unicode
     filenames and bytes filenames.  The encoding name is returned from
     *note getfilesystemencoding(): 4fb.

     *note os.fsencode(): 4f4. and *note os.fsdecode(): 4f3. should be
     used to ensure that the correct encoding and errors mode are used.

     3.6 版新加入.

 -- 函式: 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(): 3632.

 -- 函式: 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(): e80.

 -- 函式: 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: 193. will
     be raised.

     *note getsizeof(): 35c0. 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(): 35c0. recursively to find the size of containers and
     all their contents.

 -- 函式: sys.getswitchinterval ()

     Return the interpreter’s "thread switch interval"; see *note
     setswitchinterval(): bf0.

     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: 1fc. is raised.  The default for `depth' is zero,
     returning the frame at the top of the call stack.

     Raises an *note auditing event: e96. ‘sys._getframe’ with no
     arguments.

     `CPython implementation detail:' 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(): e42.

 -- 函式: sys.gettrace ()

     Get the trace function as set by *note settrace(): e43.

     `CPython implementation detail:' The *note gettrace(): d4d.
     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                                    Meaning
                                                 
     ----------------------------------------------------------------------------------
                                                 
     ‘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: cf. module for achieving accurate
          OS version.

     *note Availability: 1364.: Windows.

     3.2 版更變: Changed to a named tuple and added
     `service_pack_minor', `service_pack_major', `suite_mask', and
     `product_type'.

     3.6 版更變: Added `platform_version'

 -- 函式: sys.get_asyncgen_hooks ()

     Returns an `asyncgen_hooks' object, which is similar to a *note
     namedtuple: 1b8. of the form ‘(firstiter, finalizer)’, where
     `firstiter' and `finalizer' are expected to be either ‘None’ or
     functions which take an *note asynchronous generator iterator:
     3634. as an argument, and are used to schedule finalization of an
     asynchronous generator by an event loop.

     3.6 版新加入: See PEP 525(5) for more details.

          備註: 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(): 3f8.

     3.7 版新加入.

          備註: This function has been added on a provisional basis (see
          PEP 411(7) for details.)  Use it only for debugging purposes.

 -- Data: sys.hash_info

     A *note named tuple: aa8. giving parameters of the numeric hash
     implementation.  For more details about hashing of numeric types,
     see *note Hashing of numeric types: 162c.

     attribute                 explanation
                               
     ---------------------------------------------------------------------------------
                               
     ‘width’                   width in bits used for hash values
                               
                               
     ‘modulus’                 prime modulus P used for numeric hash scheme
                               
                               
     ‘inf’                     hash value returned for a positive infinity
                               
                               
     ‘nan’                     hash value returned for a nan
                               
                               
     ‘imag’                    multiplier used for the imaginary part of a complex
                               number
                               
                               
     ‘algorithm’               name of the algorithm for hashing of str, bytes, and
                               memoryview
                               
                               
     ‘hash_bits’               internal output size of the hash algorithm
                               
                               
     ‘seed_bits’               size of the seed key of the hash algorithm
                               

     3.2 版新加入.

     3.4 版更變: Added `algorithm', `hash_bits' and `seed_bits'

 -- Data: 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(): c6b. function.  The *note named tuple: aa8. *note
     sys.version_info: b1f. may be used for a more human-friendly
     encoding of the same information.

     More details of ‘hexversion’ can be found at *note API and ABI
     Versioning: 3636.

 -- Data: 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: b1f.  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: 3635.

     `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: 9af. 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: 9af.
     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.

 -- Data: sys.int_info

     A *note named tuple: aa8. that holds information about Python’s
     internal representation of integers.  The attributes are read only.

     Attribute                     Explanation
                                   
     ---------------------------------------------------------------------------------
                                   
     ‘bits_per_digit’              number of bits held in each digit.  Python
                                   integers are stored internally in base
                                   ‘2**int_info.bits_per_digit’
                                   
                                   
     ‘sizeof_digit’                size in bytes of the C type used to represent a
                                   digit
                                   

     3.1 版新加入.

 -- Data: sys.__interactivehook__

     When this attribute exists, its value is automatically called (with
     no arguments) when the interpreter is launched in *note interactive
     mode: 8e8.  This is done after the *note PYTHONSTARTUP: 8ea. file
     is read, so that you can set this hook there.  The *note site: ec.
     module *note sets this: 8eb.

     Raises an *note auditing event: e96. ‘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 immortal; you must keep a reference to the
     return value of *note intern(): c73. around to benefit from it.

 -- 函式: sys.is_finalizing ()

     Return *note True: 49e. if the Python interpreter is *note shutting
     down: 768, *note False: 38d. otherwise.

     3.5 版新加入.

 -- Data: sys.last_type
 -- Data: sys.last_value
 -- Data: sys.last_traceback

     These three variables are not always defined; they are set when an
     exception is not handled and the interpreter prints an error
     message and a stack traceback.  Their 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: ca. module for more
     information.)

     The meaning of the variables is the same as that of the return
     values from *note exc_info(): c64. above.

 -- Data: sys.maxsize

     An integer giving the maximum value a variable of type ‘Py_ssize_t’
     can take.  It’s usually ‘2**31 - 1’ on a 32-bit platform and ‘2**63
     - 1’ on a 64-bit platform.

 -- Data: 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.

 -- Data: sys.meta_path

     A list of *note meta path finder: 9b6. objects that have their
     *note find_spec(): 468. methods called to see if one of the objects
     can find the module to be imported.  The *note find_spec(): 468.
     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__: 1294. attribute
     is passed in as a second argument.  The method returns a *note
     module spec: 3638, or ‘None’ if the module cannot be found.

     也參考
     ......

     *note importlib.abc.MetaPathFinder: 9b8.

          The abstract base class defining the interface of finder
          objects on *note meta_path: 5eb.

     *note importlib.machinery.ModuleSpec: 14cb.

          The concrete class which *note find_spec(): 468. should return
          instances of.

     3.4 版更變: *note Module specs: 3638. were introduced in Python
     3.4, by PEP 451(11).  Earlier versions of Python looked for a
     method called *note find_module(): 467.  This is still called as a
     fallback if a *note meta_path: 5eb. entry doesn’t have a *note
     find_spec(): 468. method.

 -- Data: 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.

 -- Data: sys.path

     A list of strings that specifies the search path for modules.
     Initialized from the environment variable *note PYTHONPATH: 958,
     plus an installation-dependent default.

     As initialized upon program startup, the first item of this list,
     ‘path[0]’, is the directory containing the script that was used to
     invoke the Python interpreter.  If the script directory is not
     available (e.g.  if the interpreter is invoked interactively or if
     the script is read from standard input), ‘path[0]’ is the empty
     string, which directs Python to search modules in the current
     directory first.  Notice that the script directory is inserted
     `before' the entries inserted as a result of *note PYTHONPATH: 958.

     A program is free to modify this list for its own purposes.  Only
     strings and bytes should be added to *note sys.path: 48d.; all
     other data types are ignored during import.

     也參考
     ......

     Module *note site: ec. This describes how to use .pth files to
     extend *note sys.path: 48d.

 -- Data: sys.path_hooks

     A list of callables that take a path argument to try to create a
     *note finder: 14bf. for the path.  If a finder can be created, it
     is to be returned by the callable, else raise *note ImportError:
     339.

     Originally specified in PEP 302(12).

 -- Data: sys.path_importer_cache

     A dictionary acting as a cache for *note finder: 14bf. objects.
     The keys are paths that have been passed to *note sys.path_hooks:
     961. 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: 961. then ‘None’ is stored.

     Originally specified in PEP 302(13).

     3.3 版更變: ‘None’ is stored instead of *note imp.NullImporter:
     9c0. when no finder is found.

 -- Data: sys.platform

     This string contains a platform identifier that can be used to
     append platform-specific components to *note sys.path: 48d, for
     instance.

     For Unix systems, except on Linux and AIX, this 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...
          elif sys.platform.startswith('linux'):
              # Linux-specific code here...
          elif sys.platform.startswith('aix'):
              # AIX-specific code here...

     For other systems, the values are:

     System               ‘platform’ value
                          
     -----------------------------------------------------
                          
     AIX                  ‘'aix'’
                          
                          
     Linux                ‘'linux'’
                          
                          
     Windows              ‘'win32'’
                          
                          
     Windows/Cygwin       ‘'cygwin'’
                          
                          
     macOS                ‘'darwin'’
                          

     3.3 版更變: On Linux, *note sys.platform: 2b2. doesn’t contain the
     major version anymore.  It is always ‘'linux'’, instead of
     ‘'linux2'’ or ‘'linux3'’.  Since older Python versions include the
     version number, it is recommended to always use the ‘startswith’
     idiom presented above.

     3.8 版更變: On AIX, *note sys.platform: 2b2. doesn’t contain the
     major version anymore.  It is always ‘'aix'’, instead of ‘'aix5'’
     or ‘'aix7'’.  Since older Python versions include the version
     number, it is recommended to always use the ‘startswith’ idiom
     presented above.

     也參考
     ......

     *note os.name: 1ee5. has a coarser granularity.  *note os.uname():
     a62. gives system-dependent version information.

     The *note platform: cf. module provides detailed checks for the
     system’s identity.

 -- Data: sys.prefix

     A string giving the site-specific directory prefix where the
     platform independent Python files are installed; by default, this
     is the string ‘'/usr/local'’.  This can be set at build time with
     the ‘--prefix’ argument to the ‘configure’ script.  The main
     collection of Python library modules is installed in the directory
     ‘`prefix'/lib/python`X.Y'’ while the platform independent header
     files (all except ‘pyconfig.h’) are stored in
     ‘`prefix'/include/python`X.Y'’, where `X.Y' is the version number
     of Python, for example ‘3.2’.

          備註: If a *note virtual environment: 35f9. 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: 3045.

 -- Data: sys.ps1
 -- Data: 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(): 335. is re-evaluated each time the
     interpreter prepares to read a new interactive command; this can be
     used to implement a dynamic prompt.

 -- 函式: sys.setcheckinterval (interval)

     Set the interpreter’s "check interval".  This integer value
     determines how often the interpreter checks for periodic things
     such as thread switches and signal handlers.  The default is ‘100’,
     meaning the check is performed every 100 Python virtual
     instructions.  Setting it to a larger value may increase
     performance for programs using threads.  Setting it to a value ‘<=’
     0 checks every virtual instruction, maximizing responsiveness as
     well as overhead.

     3.2 版後已棄用: This function doesn’t have an effect anymore, as
     the internal logic for thread switching and asynchronous tasks has
     been rewritten.  Use *note setswitchinterval(): bf0. instead.

 -- 函式: 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: c5. module (‘RTLD_xxx’
     constants, e.g.  *note os.RTLD_LAZY: a64.).

     *note Availability: 1364.: Unix.

 -- 函式: sys.setprofile (profilefunc)

     Set the system’s profile function, which allows you to implement a
     Python source code profiler in Python.  See chapter *note The
     Python Profilers: 355b. for more information on the Python
     profiler.  The system’s profile function is called similarly to the
     system’s trace function (see *note settrace(): e43.), 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.

     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.

     Raises an *note auditing event: e96. ‘sys.setprofile’ with no
     arguments.

     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.

 -- 函式: 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: 639. exception is raised.

     3.5.1 版更變: A *note RecursionError: 639. 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(): e43. for
     each thread being debugged or use *note threading.settrace(): 2357.

     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 for further tracing in that scope), or ‘None’ to
     turn off tracing in that scope.

     If there is any error occurred in the trace function, it will be
     unset, just like ‘settrace(None)’ is called.

     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 ‘f_trace_lines’ to *note
          False: 38d. on that frame.

     ‘'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: 38. 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
          ‘f_trace_opcodes’ to *note True: 49e. on the frame.

     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(): e43. doesn’t do.  Note that in order for this to work,
     a global tracing function must have been installed with *note
     settrace(): e43. 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 The
     standard type hierarchy: 1426.

     Raises an *note auditing event: e96. ‘sys.settrace’ with no
     arguments.

     `CPython implementation detail:' The *note settrace(): e43.
     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; ‘f_trace_lines’ and
     ‘f_trace_opcodes’ 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: 3634. 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.

     Raises an *note auditing event: e96.
     ‘sys.set_asyncgen_hooks_firstiter’ with no arguments.

     Raises an *note auditing event: e96.
     ‘sys.set_asyncgen_hooks_finalizer’ with no arguments.

     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._enablelegacywindowsfsencoding ()

     Changes the default filesystem encoding and errors mode to ’mbcs’
     and ’replace’ respectively, for consistency with versions of Python
     prior to 3.6.

     This is equivalent to defining the *note
     PYTHONLEGACYWINDOWSFSENCODING: 4fc. environment variable before
     launching Python.

     *note Availability: 1364.: Windows.

     3.6 版新加入: See PEP 529(18) for more details.

 -- Data: sys.stdin
 -- Data: sys.stdout
 -- Data: sys.stderr

     *note File objects: b47. used by the interpreter for standard
     input, output and errors:

        * ‘stdin’ is used for all interactive input (including calls to
          *note input(): c70.);

        * ‘stdout’ is used for the output of *note print(): 88b. and
          *note expression: 3628. statements and for the prompts of
          *note input(): c70.;

        * The interpreter’s own prompts and its error messages go to
          ‘stderr’.

     These streams are regular *note text files: 12aa. like those
     returned by the *note open(): 4f5. function.  Their parameters are
     chosen as follows:

        * The character encoding is platform-dependent.  Non-Windows
          platforms use the locale encoding (see *note
          locale.getpreferredencoding(): 3aa.).

          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 locale encoding 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: 934. environment
          variable before starting Python or by using the new *note -X:
          156. ‘utf8’ command line option and *note PYTHONUTF8: 316.
          environment variable.  However, for the Windows console, this
          only applies when *note PYTHONLEGACYWINDOWSSTDIO: 4ff. is also
          set.

        * When interactive, ‘stdout’ and ‘stderr’ streams are
          line-buffered.  Otherwise, they are block-buffered like
          regular text files.  You can override this value with the
          *note -u: 134d. command-line option.

          備註: To write or read binary data from/to the standard
          streams, use the underlying binary *note buffer: c3f. object.
          For example, to write bytes to *note stdout: 313, 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: 832. which do not support the ‘buffer’
          attribute.

 -- Data: sys.__stdin__
 -- Data: sys.__stdout__
 -- Data: 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’.

 -- Data: sys.thread_info

     A *note named tuple: aa8. holding information about the thread
     implementation.

     Attribute              Explanation
                            
     -------------------------------------------------------------------------------------
                            
     ‘name’                 Name of the thread implementation:
                            
                                    * ‘'nt'’: Windows threads
                            
                                    * ‘'pthread'’: POSIX threads
                            
                                    * ‘'solaris'’: Solaris threads
                            
                            
     ‘lock’                 Name of the lock implementation:
                            
                                    * ‘'semaphore'’: a lock uses a semaphore
                            
                                    * ‘'mutex+cond'’: a lock uses a mutex and a
                                      condition variable
                            
                                    * ‘None’ if this information is unknown
                            
                            
     *note version: 5d8.    Name and version of the thread library.  It is a string, or
                            ‘None’ if this information is unknown.
                            

     3.3 版新加入.

 -- Data: 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, /)

     Handle an unraisable exception.

     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(): 22f.).

     The `unraisable' argument has the following attributes:

        * `exc_type': Exception type.

        * `exc_value': Exception value, can be ‘None’.

        * `exc_traceback': Exception traceback, can be ‘None’.

        * `err_msg': Error message, can be ‘None’.

        * `object': Object causing the exception, can be ‘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(): 22e. can be overridden to control how
     unraisable exceptions 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 `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.

     See also *note excepthook(): e68. which handles uncaught
     exceptions.

     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 版新加入.

 -- Data: 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: b1f. and the functions provided by the *note
     platform: cf. module.

 -- Data: sys.api_version

     The C API version for this interpreter.  Programmers may find this
     useful when debugging version conflicts between Python and
     extension modules.

 -- Data: 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 版更變: Added named component attributes.

 -- Data: sys.warnoptions

     This is an implementation detail of the warnings framework; do not
     modify this value.  Refer to the *note warnings: 127. module for
     more information on the warnings framework.

 -- Data: 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 first three characters of *note version: 5d8.  It
     is provided in the *note sys: fe. module for informational
     purposes; modifying this value has no effect on the registry keys
     used by Python.

     *note Availability: 1364.: Windows.

 -- Data: sys._xoptions

     A dictionary of the various implementation-specific flags passed
     through the *note -X: 156. command-line option.  Option names are
     either mapped to their values, if given explicitly, or to *note
     True: 49e.  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 implementation detail:' This is a CPython-specific way of
     accessing options passed through *note -X: 156.  Other
     implementations may export them through other means, or not at all.

     3.2 版新加入.

Citations
.........

(C99) ISO/IEC 9899:1999.  "Programming languages – C." A public draft of
this standard is available at
‘http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf’.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3149

   (2) https://www.python.org/dev/peps/pep-0578

   (3) https://www.python.org/dev/peps/pep-0529

   (4) https://code.activestate.com/recipes/577504

   (5) https://www.python.org/dev/peps/pep-0525

   (6) https://www.python.org/dev/peps/pep-0411

   (7) https://www.python.org/dev/peps/pep-0411

   (8) https://www.python.org/dev/peps/pep-0421

   (9) https://www.python.org/dev/peps/pep-0421

   (10) https://www.python.org/dev/peps/pep-0393

   (11) https://www.python.org/dev/peps/pep-0451

   (12) https://www.python.org/dev/peps/pep-0302

   (13) https://www.python.org/dev/peps/pep-0302

   (14) https://www.python.org/dev/peps/pep-0525

   (15) 
https://github.com/python/cpython/tree/3.8/Lib/asyncio/base_events.py

   (16) https://www.python.org/dev/peps/pep-0411

   (17) https://www.python.org/dev/peps/pep-0411

   (18) https://www.python.org/dev/peps/pep-0529


File: python.info,  Node: sysconfig --- Provide access to Python's configuration information,  Next: builtins --- Built-in objects,  Prev: sys --- System-specific parameters and functions,  Up: Python Runtime Services

5.29.2 ‘sysconfig’ — Provide access to Python’s configuration information
-------------------------------------------------------------------------

3.2 版新加入.

`Source code:' Lib/sysconfig.py(1)

__________________________________________________________________

The *note sysconfig: ff. 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::
* Other functions: Other functions<3>.
* Using sysconfig as a script::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/sysconfig.py


File: python.info,  Node: Configuration variables,  Next: Installation paths,  Up: sysconfig --- Provide access to Python's configuration information

5.29.2.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 *note distutils: 39.

*note sysconfig: ff. puts all variables found in these files in a
dictionary that can be accessed using *note get_config_vars(): 96a. or
*note get_config_var(): 969.

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’.

Example of usage:

     >>> 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: Other functions<3>,  Prev: Configuration variables,  Up: sysconfig --- Provide access to Python's configuration information

5.29.2.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: ff. under unique identifiers based on the value
returned by *note os.name: 1ee5.

Every new component that is installed using *note distutils: 39. or a
Distutils-based system will follow the same scheme to copy its file in
the right places.

Python currently supports seven schemes:

   - `posix_prefix': scheme for POSIX platforms like Linux or Mac OS X.
     This is the default scheme used when Python or a component is
     installed.

   - `posix_home': scheme for POSIX platforms used when a `home' option
     is used upon installation.  This scheme is used when a component is
     installed through Distutils with a specific home prefix.

   - `posix_user': scheme for POSIX platforms used when a component is
     installed through Distutils and the `user' option is used.  This
     scheme defines paths located under the user home directory.

   - `nt': scheme for NT platforms like Windows.

   - `nt_user': scheme for NT platforms, 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.

   - `include': directory for non-platform-specific header files.

   - `platinclude': directory for platform-specific header files.

   - `scripts': directory for script files.

   - `data': directory for data files.

*note sysconfig: ff. provides some functions to determine these paths.

 -- 函式: sysconfig.get_scheme_names ()

     Return a tuple containing all schemes currently supported in *note
     sysconfig: ff.

 -- 函式: sysconfig.get_path_names ()

     Return a tuple containing all path names currently supported in
     *note sysconfig: ff.

 -- 函式: 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(): 3643.

     *note sysconfig: ff. 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(): cc3. will use the variables returned by *note
     get_config_vars(): 96a. 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(): 3642.  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 return by *note get_config_vars(): 96a.

     If `expand' is set to ‘False’, the path will not be expanded using
     the variables.

     If `name' is not found, return ‘None’.

 -- 函式: sysconfig.get_paths ([scheme[, vars[, expand]]])

     Return a dictionary containing all installation paths corresponding
     to an installation scheme.  See *note get_path(): cc3. 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(): bde. will
     raise a *note KeyError: 2c8.


File: python.info,  Node: Other functions<3>,  Next: Using sysconfig as a script,  Prev: Installation paths,  Up: sysconfig --- Provide access to Python's configuration information

5.29.2.3 Other functions
........................

 -- 函式: sysconfig.get_python_version ()

     Return the ‘MAJOR.MINOR’ Python version number as a string.
     Similar to ‘'%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 ’os.uname()’), 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)

     Mac OS X 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: 2b2.

 -- 函式: 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 ()

     Return the path of ‘pyconfig.h’.

 -- 函式: sysconfig.get_makefile_filename ()

     Return the path of ‘Makefile’.


File: python.info,  Node: Using sysconfig as a script,  Prev: Other functions<3>,  Up: sysconfig --- Provide access to Python's configuration information

5.29.2.4 Using ‘sysconfig’ as a script
......................................

You can use *note sysconfig: ff. 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(): bdc, *note get_python_version(): bdd, *note
get_path(): cc3. and *note get_config_vars(): 96a.


File: python.info,  Node: builtins --- Built-in objects,  Next: __main__ --- Top-level script environment,  Prev: sysconfig --- Provide access to Python's configuration information,  Up: Python Runtime Services

5.29.3 ‘builtins’ — Built-in objects
------------------------------------

__________________________________________________________________

This module provides direct access to all ’built-in’ identifiers of
Python; for example, ‘builtins.open’ is the full name for the built-in
function *note open(): 4f5.  See *note 內建函式: bf8. and *note
內建常數: 1610. for documentation.

This module is not normally accessed explicitly by most applications,
but can be useful in modules that provide objects with the same name as
a built-in value, but in which the built-in of that name is also needed.
For example, in a module that wants to implement an *note open(): 4f5.
function that wraps the built-in *note open(): 4f5, this module can be
used directly:

     import builtins

     def open(path):
         f = builtins.open(path, 'r')
         return UpperCaser(f)

     class UpperCaser:
         '''Wrapper around a file that converts output to upper-case.'''

         def __init__(self, f):
             self._f = f

         def read(self, count=-1):
             return self._f.read(count).upper()

         # ...

As an implementation detail, most modules have the name ‘__builtins__’
made available as part of their globals.  The value of ‘__builtins__’ is
normally either this module or the value of this module’s *note
__dict__: 501. attribute.  Since this is an implementation detail, it
may not be used by alternate implementations of Python.


File: python.info,  Node: __main__ --- Top-level script environment,  Next: warnings --- Warning control,  Prev: builtins --- Built-in objects,  Up: Python Runtime Services

5.29.4 ‘__main__’ — Top-level script environment
------------------------------------------------

__________________________________________________________________

‘'__main__'’ is the name of the scope in which top-level code executes.
A module’s __name__ is set equal to ‘'__main__'’ when read from standard
input, a script, or from an interactive prompt.

A module can discover whether or not it is running in the main scope by
checking its own ‘__name__’, which allows a common idiom for
conditionally executing code in a module when it is run as a script or
with ‘python -m’ but not when it is imported:

     if __name__ == "__main__":
         # execute only if run as a script
         main()

For a package, the same effect can be achieved by including a
‘__main__.py’ module, the contents of which will be executed when the
module is run with ‘-m’.


File: python.info,  Node: warnings --- Warning control,  Next: dataclasses --- Data Classes,  Prev: __main__ --- Top-level script environment,  Up: Python Runtime Services

5.29.5 ‘warnings’ — Warning control
-----------------------------------

`Source code:' 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(): e5d.
function defined in this module.  (C programmers use *note
PyErr_WarnEx(): db6.; see *note 例外處理: 364f. for details).

Warning messages are normally written to *note sys.stderr: 314, 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: 171e, 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: 1351, which is a sequence of matching rules
and actions.  Rules can be added to the filter by calling *note
filterwarnings(): e0c. and reset to its default state by calling *note
resetwarnings(): 3650.

The printing of warning messages is done by calling *note showwarning():
3651, which may be overridden; the default implementation of this
function formats the message by calling *note formatwarning(): ff7,
which is also available for use by custom implementations.

也參考
......

*note logging.captureWarnings(): 20d5. 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.8/Lib/warnings.py


File: python.info,  Node: Warning Categories,  Next: The Warnings Filter,  Up: warnings --- Warning control

5.29.5.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: 171c, 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: 171f. class.

The following warnings category classes are currently defined:

Class                                  描述
                                       
-------------------------------------------------------------------------------------------
                                       
*note Warning: 171f.                   This is the base class of all warning category
                                       classes.  It is a subclass of
                                       *note Exception: 1aa.
                                       
                                       
*note UserWarning: 1720.               The default category for *note warn(): e5d.
                                       
                                       
*note DeprecationWarning: 279.         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: 192.              Base category for warnings about dubious
                                       syntactic features.
                                       
                                       
*note RuntimeWarning: 2c1.             Base category for warnings about dubious runtime
                                       features.
                                       
                                       
*note FutureWarning: 32a.              Base category for warnings about deprecated
                                       features when those warnings are intended for end
                                       users of applications that are written in Python.
                                       
                                       
*note PendingDeprecationWarning: 27a.  Base category for warnings about features that
                                       will be deprecated in the future (ignored by
                                       default).
                                       
                                       
*note ImportWarning: 5dd.              Base category for warnings triggered during the
                                       process of importing a module (ignored by
                                       default).
                                       
                                       
*note UnicodeWarning: d8c.             Base category for warnings related to Unicode.
                                       
                                       
*note BytesWarning: 4ba.               Base category for warnings related to
                                       *note bytes: 336. and *note bytearray: 337.
                                       
                                       
*note ResourceWarning: 4d5.            Base category for warnings related to resource
                                       usage.
                                       

3.7 版更變: Previously *note DeprecationWarning: 279. and *note
FutureWarning: 32a. 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 --- Warning control

5.29.5.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.  The expression is
     compiled to always be case-insensitive.

   * `category' is a class (a subclass of *note Warning: 171f.) of which
     the warning category must be a subclass in order to match.

   * `module' is a string containing a regular expression that the
     module name must match.  The expression is compiled to be
     case-sensitive.

   * `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: 171f. class is derived from the built-in *note
Exception: 1aa. 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.5.3 Describing Warning Filters
...................................

The warnings filter is initialized by *note -W: 41c. options passed to
the Python interpreter command line and the *note PYTHONWARNINGS: 41d.
environment variable.  The interpreter saves the arguments for all
supplied entries without interpretation in *note sys.warnoptions: 41b.;
the *note warnings: 127. module parses these when it is first imported
(invalid options are ignored, after printing a message to *note
sys.stderr: 314.).

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: 1351.  When listing multiple filters on a single line
(as for *note PYTHONWARNINGS: 41d.), 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"
                                  # and any subpackages of "mymodule"


File: python.info,  Node: Default Warning Filter,  Next: Overriding the default filter,  Prev: Describing Warning Filters,  Up: The Warnings Filter

5.29.5.4 Default Warning Filter
...............................

By default, Python installs several warning filters, which can be
overridden by the *note -W: 41c. command-line option, the *note
PYTHONWARNINGS: 41d. environment variable and calls to *note
filterwarnings(): e0c.

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 debug builds, the list of default warning filters is empty.

3.2 版更變: *note DeprecationWarning: 279. is now ignored by default in
addition to *note PendingDeprecationWarning: 27a.

3.7 版更變: *note DeprecationWarning: 279. is once again shown by
default when triggered directly by code in ‘__main__’.

3.7 版更變: *note BytesWarning: 4ba. no longer appears in the default
filter list and is instead configured via *note sys.warnoptions: 41b.
when *note -b: 41a. is specified twice.


File: python.info,  Node: Overriding the default filter,  Prev: Default Warning Filter,  Up: The Warnings Filter

5.29.5.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: 41b. 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: 279. 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 --- Warning control

5.29.5.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:
345c. 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: 345c. 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 --- Warning control

5.29.5.7 Testing Warnings
.........................

To test warnings raised by code, use the *note catch_warnings: 345c.
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(): 3651. 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: 345c. 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 --- Warning control

5.29.5.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: 279. (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: 11c.
module does this).

In less ideal cases, applications can be checked for use of deprecated
interfaces by passing *note -Wd: 41c. 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:
41c. (e.g.  ‘-W error’).  See the *note -W: 41c. 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 --- Warning control

5.29.5.9 Available Functions
............................

 -- 函式: warnings.warn (message, category=None, stacklevel=1,
          source=None)

     Issue a warning, or maybe ignore it or raise an exception.  The
     `category' argument, if given, must be a *note warning category
     class: 171e.; it defaults to *note UserWarning: 1720.
     Alternatively, `message' can be a *note Warning: 171f. 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: 1351.  The
     `stacklevel' argument can be used by wrapper functions written in
     Python, like this:

          def deprecation(message):
              warnings.warn(message, DeprecationWarning, stacklevel=2)

     This makes the warning refer to ‘deprecation()’’s caller, rather
     than to the source of ‘deprecation()’ itself (since the latter
     would defeat the purpose of the warning message).

     `source', if supplied, is the destroyed object which emitted a
     *note ResourceWarning: 4d5.

     3.6 版更變: Added `source' parameter.

 -- 函式: 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():
     e5d, 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: 171f.
     or `message' may be a *note Warning: 171f. 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: 4d5.

     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: 314.  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(): 3651. 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(): ff7. 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: 1351.  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: 1351.  The meaning of the function parameters is as
     for *note filterwarnings(): e0c, 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(): e0c, including that of
     the *note -W: 41c. command line options and calls to *note
     simplefilter(): 345d.


File: python.info,  Node: Available Context Managers,  Prev: Available Functions,  Up: warnings --- Warning control

5.29.5.10 Available Context Managers
....................................

 -- 類別: warnings.catch_warnings (*, record=False, module=None)

     A context manager that copies and, upon exit, restores the warnings
     filter and the *note showwarning(): 3651. function.  If the
     `record' argument is *note False: 38d. (the default) the context
     manager returns *note None: 158. on entry.  If `record' is *note
     True: 49e, a list is returned that is progressively populated with
     objects as seen by a custom *note showwarning(): 3651. 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(): 3651.

     The `module' argument takes a module that will be used instead of
     the module returned when you import *note warnings: 127. whose
     filter will be protected.  This argument exists primarily for
     testing the *note warnings: 127. module itself.

          備註: The *note catch_warnings: 345c. manager works by
          replacing and then later restoring the module’s *note
          showwarning(): 3651. function and internal list of filter
          specifications.  This means the context manager is modifying
          global state and therefore is not thread-safe.


File: python.info,  Node: dataclasses --- Data Classes,  Next: contextlib --- Utilities for with-statement contexts,  Prev: warnings --- Warning control,  Up: Python Runtime Services

5.29.6 ‘dataclasses’ — Data Classes
-----------------------------------

`Source code:' Lib/dataclasses.py(1)

__________________________________________________________________

This module provides a decorator and functions for automatically adding
generated *note special method: 3663.s such as *note __init__(): d63.
and *note __repr__(): 343. 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 *note __init__(): d63. 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:

* Module-level decorators, classes, and functions: Module-level decorators classes and functions.
* Post-init processing::
* Class variables::
* Init-only variables::
* Frozen instances::
* Inheritance: Inheritance<2>.
* Default factory functions::
* Mutable default values::
* Exceptions: Exceptions<15>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/dataclasses.py

   (2) https://www.python.org/dev/peps/pep-0557

   (3) https://www.python.org/dev/peps/pep-0526


File: python.info,  Node: Module-level decorators classes and functions,  Next: Post-init processing,  Up: dataclasses --- Data Classes

5.29.6.1 Module-level decorators, classes, and functions
........................................................

 -- 函式: @dataclasses.dataclass (*, init=True, repr=True, eq=True,
          order=False, unsafe_hash=False, frozen=False)

     This function is a *note decorator: 284. that is used to add
     generated *note special method: 3663.s to classes, as described
     below.

     The *note dataclass(): 342. decorator examines the class to find
     ‘field’s.  A ‘field’ is defined as class variable that has a *note
     type annotation: 624.  With two exceptions described below, nothing
     in *note dataclass(): 342. 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 *note dataclass(): 342. decorator will add various "dunder"
     methods to the class, described below.  If any of the added methods
     already exist on the class, the behavior depends on the parameter,
     as documented below.  The decorator returns the same class that is
     called on; no new class is created.

     If *note dataclass(): 342. 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 *note dataclass():
     342. are equivalent:

          @dataclass
          class C:
              ...

          @dataclass()
          class C:
              ...

          @dataclass(init=True, repr=True, eq=True, order=False, unsafe_hash=False, frozen=False)
          class C:
             ...

     The parameters to *note dataclass(): 342. are:

        - ‘init’: If true (the default), a *note __init__(): d63. method
          will be generated.

          If the class already defines *note __init__(): d63, this
          parameter is ignored.

        - ‘repr’: If true (the default), a *note __repr__(): 343. 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 *note __repr__(): 343, this
          parameter is ignored.

        - ‘eq’: If true (the default), an *note __eq__(): 344. 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 *note __eq__(): 344, this
          parameter is ignored.

        - ‘order’: If true (the default is ‘False’), *note __lt__():
          c39, *note __le__(): ca5, *note __gt__(): ca6, and *note
          __ge__(): ca7. 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: 1fc. is
          raised.

          If the class already defines any of *note __lt__(): c39, *note
          __le__(): ca5, *note __gt__(): ca6, or *note __ge__(): ca7,
          then *note TypeError: 193. is raised.

        - ‘unsafe_hash’: If ‘False’ (the default), a *note __hash__():
          345. method is generated according to how ‘eq’ and ‘frozen’
          are set.

          *note __hash__(): 345. is used by built-in *note hash(): 9c9,
          and when objects are added to hashed collections such as
          dictionaries and sets.  Having a *note __hash__(): 345.
          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 *note __eq__(): 344, and
          the values of the ‘eq’ and ‘frozen’ flags in the *note
          dataclass(): 342. decorator.

          By default, *note dataclass(): 342. will not implicitly add a
          *note __hash__(): 345. method unless it is safe to do so.
          Neither will it add or change an existing explicitly defined
          *note __hash__(): 345. method.  Setting the class attribute
          ‘__hash__ = None’ has a specific meaning to Python, as
          described in the *note __hash__(): 345. documentation.

          If *note __hash__(): 345. is not explicitly defined, or if it
          is set to ‘None’, then *note dataclass(): 342. `may' add an
          implicit *note __hash__(): 345. method.  Although not
          recommended, you can force *note dataclass(): 342. to create a
          *note __hash__(): 345. method with ‘unsafe_hash=True’.  This
          might be the case if your class is logically immutable but can
          nonetheless be mutated.  This is a specialized use case and
          should be considered carefully.

          Here are the rules governing implicit creation of a *note
          __hash__(): 345. method.  Note that you cannot both have an
          explicit *note __hash__(): 345. method in your dataclass and
          set ‘unsafe_hash=True’; this will result in a *note TypeError:
          193.

          If ‘eq’ and ‘frozen’ are both true, by default *note
          dataclass(): 342. will generate a *note __hash__(): 345.
          method for you.  If ‘eq’ is true and ‘frozen’ is false, *note
          __hash__(): 345. will be set to ‘None’, marking it unhashable
          (which it is, since it is mutable).  If ‘eq’ is false, *note
          __hash__(): 345. will be left untouched meaning the *note
          __hash__(): 345. method of the superclass will be used (if the
          superclass is *note object: 2b1, 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__(): e31. or *note
          __delattr__(): 1435. is defined in the class, then *note
          TypeError: 193. is raised.  See the discussion below.

     ‘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__(): d63. method, which will be defined as:

          def __init__(self, a: int, b: int = 0):

     *note TypeError: 193. will be raised if a field without a default
     value follows a field with a default value.  This is true either
     when this occurs in a single class, or as a result of class
     inheritance.

 -- 函式: dataclasses.field (*, default=MISSING,
          default_factory=MISSING, repr=True, hash=None, init=True,
          compare=True, metadata=None)

     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 *note field(): 1003. function.  For
     example:

          @dataclass
          class C:
              mylist: List[int] = field(default_factory=list)

          c = C()
          c.mylist += [1, 2, 3]

     As shown above, the ‘MISSING’ value is a sentinel object used to
     detect if the ‘default’ and ‘default_factory’ parameters are
     provided.  This sentinel is used because ‘None’ is a valid value
     for ‘default’.  No code should directly use the ‘MISSING’ value.

     The parameters to *note field(): 1003. are:

        - ‘default’: If provided, this will be the default value for
          this field.  This is needed because the *note field(): 1003.
          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__(): d63. method.

        - ‘repr’: If true (the default), this field is included in the
          string returned by the generated *note __repr__(): 343.
          method.

        - ‘compare’: If true (the default), this field is included in
          the generated equality and comparison methods (*note __eq__():
          344, *note __gt__(): ca6, et al.).

        - ‘hash’: This can be a bool or ‘None’.  If true, this field is
          included in the generated *note __hash__(): 345. 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.

        - ‘metadata’: This can be a mapping or None.  None is treated as
          an empty dict.  This value is wrapped in *note
          MappingProxyType(): abb. to make it read-only, and exposed on
          the *note Field: 3665. 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.

     If the default value of a field is specified by a call to *note
     field(): 1003, then the class attribute for this field will be
     replaced by the specified ‘default’ value.  If no ‘default’ is
     provided, then the class attribute will be deleted.  The intent is
     that after the *note dataclass(): 342. 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

     *note Field: 3665. objects describe each defined field.  These
     objects are created internally, and are returned by the *note
     fields(): 3666. module-level method (see below).  Users should
     never instantiate a *note Field: 3665. object directly.  Its
     documented attributes are:

             - ‘name’: The name of the field.

             - ‘type’: The type of the field.

             - ‘default’, ‘default_factory’, ‘init’, ‘repr’, ‘hash’,
               ‘compare’, and ‘metadata’ have the identical meaning and
               values as they do in the *note field(): 1003.
               declaration.

     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: 3665. objects that define the
     fields for this dataclass.  Accepts either a dataclass, or an
     instance of a dataclass.  Raises *note TypeError: 193. if not
     passed a dataclass or instance of one.  Does not return
     pseudo-fields which are ‘ClassVar’ or ‘InitVar’.

 -- 函式: dataclasses.asdict (instance, *, dict_factory=dict)

     Converts the dataclass ‘instance’ 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.  For example:

          @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}]}

     Raises *note TypeError: 193. if ‘instance’ is not a dataclass
     instance.

 -- 函式: dataclasses.astuple (instance, *, tuple_factory=tuple)

     Converts the dataclass ‘instance’ 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.

     Continuing from the previous example:

          assert astuple(p) == (10, 20)
          assert astuple(c) == ([(0, 0), (10, 4)],)

     Raises *note TypeError: 193. if ‘instance’ 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)

     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, ‘typing.Any’ is used for
     ‘type’.  The values of ‘init’, ‘repr’, ‘eq’, ‘order’,
     ‘unsafe_hash’, and ‘frozen’ have the same meaning as they do in
     *note dataclass(): 342.

     This function is not strictly required, because any Python
     mechanism for creating a new class with ‘__annotations__’ can then
     apply the *note dataclass(): 342. 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})

     Is equivalent to:

          @dataclass
          class C:
              x: int
              y: 'typing.Any'
              z: int = 5

              def add_one(self):
                  return self.x + 1

 -- 函式: dataclasses.replace (instance, **changes)

     Creates a new object of the same type of ‘instance’, replacing
     fields with values from ‘changes’.  If ‘instance’ is not a Data
     Class, raises *note TypeError: 193.  If values in ‘changes’ do not
     specify fields, raises *note TypeError: 193.

     The newly returned object is created by calling the *note
     __init__(): d63. method of the dataclass.  This ensures that
     ‘__post_init__()’, if present, is also called.

     Init-only variables without default values, if any exist, must be
     specified on the call to *note replace(): e9d. so that they can be
     passed to *note __init__(): d63. and ‘__post_init__()’.

     It is an error for ‘changes’ to contain any fields that are defined
     as having ‘init=False’.  A *note ValueError: 1fc. will be raised in
     this case.

     Be forewarned about how ‘init=False’ fields work during a call to
     *note replace(): e9d.  They are not copied from the source object,
     but rather are initialized in ‘__post_init__()’, 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.

 -- 函式: dataclasses.is_dataclass (class_or_instance)

     Return ‘True’ if its parameter is 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)


File: python.info,  Node: Post-init processing,  Next: Class variables,  Prev: Module-level decorators classes and functions,  Up: dataclasses --- Data Classes

5.29.6.2 Post-init processing
.............................

The generated *note __init__(): d63. code will call a method named
‘__post_init__()’, if ‘__post_init__()’ is defined on the class.  It
will normally be called 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
*note __init__(): d63. 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

See the section below on init-only variables for ways to pass parameters
to ‘__post_init__()’.  Also see the warning about how *note replace():
e9d. handles ‘init=False’ fields.


File: python.info,  Node: Class variables,  Next: Init-only variables,  Prev: Post-init processing,  Up: dataclasses --- Data Classes

5.29.6.3 Class variables
........................

One of two places where *note dataclass(): 342. 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 ‘typing.ClassVar’.  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(): 3666. function.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0526


File: python.info,  Node: Init-only variables,  Next: Frozen instances,  Prev: Class variables,  Up: dataclasses --- Data Classes

5.29.6.4 Init-only variables
............................

The other place where *note dataclass(): 342. 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(): 3666. function.  Init-only fields are added
as parameters to the generated *note __init__(): d63. method, and are
passed to the optional ‘__post_init__()’ 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
         database: InitVar[DatabaseType] = 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(): 3666. will return *note Field: 3665.
objects for ‘i’ and ‘j’, but not for ‘database’.


File: python.info,  Node: Frozen instances,  Next: Inheritance<2>,  Prev: Init-only variables,  Up: dataclasses --- Data Classes

5.29.6.5 Frozen instances
.........................

It is not possible to create truly immutable Python objects.  However,
by passing ‘frozen=True’ to the *note dataclass(): 342. decorator you
can emulate immutability.  In that case, dataclasses will add *note
__setattr__(): e31. and *note __delattr__(): 1435. methods to the class.
These methods will raise a *note FrozenInstanceError: 366f. when
invoked.

There is a tiny performance penalty when using ‘frozen=True’: *note
__init__(): d63. cannot use simple assignment to initialize fields, and
must use *note object.__setattr__(): e31.


File: python.info,  Node: Inheritance<2>,  Next: Default factory functions,  Prev: Frozen instances,  Up: dataclasses --- Data Classes

5.29.6.6 Inheritance
....................

When the dataclass is being created by the *note dataclass(): 342.
decorator, it looks through all of the class’s base classes in reverse
MRO (that is, starting at *note object: 2b1.) 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 ‘int’, as specified in class ‘C’.

The generated *note __init__(): d63. method for ‘C’ will look like:

     def __init__(self, x: int = 15, y: int = 0, z: int = 10):


File: python.info,  Node: Default factory functions,  Next: Mutable default values,  Prev: Inheritance<2>,  Up: dataclasses --- Data Classes

5.29.6.7 Default factory functions
..................................

     If a *note field(): 1003. 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__(): d63. (using
     ‘init=False’) and the field also specifies ‘default_factory’, then
     the default factory function will always be called from the
     generated *note __init__(): d63. function.  This happens because
     there is no other way to give the field an initial value.


File: python.info,  Node: Mutable default values,  Next: Exceptions<15>,  Prev: Default factory functions,  Up: dataclasses --- Data Classes

5.29.6.8 Mutable default values
...............................

     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 = []
              def add(self, element):
                  self.x += element

     it would generate code similar to:

          class D:
              x = []
              def __init__(self, x=x):
                  self.x = x
              def add(self, element):
                  self.x += 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, dataclasses will raise a *note
     TypeError: 193. if it detects a default parameter of type ‘list’,
     ‘dict’, or ‘set’.  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


File: python.info,  Node: Exceptions<15>,  Prev: Mutable default values,  Up: dataclasses --- Data Classes

5.29.6.9 Exceptions
...................

 -- 例外: dataclasses.FrozenInstanceError

     Raised when an implicitly defined *note __setattr__(): e31. or
     *note __delattr__(): 1435. is called on a dataclass which was
     defined with ‘frozen=True’.  It is a subclass of *note
     AttributeError: 3a0.


File: python.info,  Node: contextlib --- Utilities for with-statement contexts,  Next: abc --- Abstract Base Classes,  Prev: dataclasses --- Data Classes,  Up: Python Runtime Services

5.29.7 ‘contextlib’ — Utilities for ‘with’-statement contexts
-------------------------------------------------------------

`Source code:' Lib/contextlib.py(1)

__________________________________________________________________

This module provides utilities for common tasks involving the *note
with: 6ee. statement.  For more information see also *note Context
Manager Types: 148d. and *note With Statement Context Managers: 148b.

* 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.8/Lib/contextlib.py


File: python.info,  Node: Utilities,  Next: Examples and Recipes<2>,  Up: contextlib --- Utilities for with-statement contexts

5.29.7.1 Utilities
..................

Functions and classes provided:

 -- 類別: contextlib.AbstractContextManager

     An *note abstract base class: b38. for classes that implement *note
     object.__enter__(): c9a. and *note object.__exit__(): c9b.  A
     default implementation for *note object.__enter__(): c9a. is
     provided which returns ‘self’ while *note object.__exit__(): c9b.
     is an abstract method which by default returns ‘None’.  See also
     the definition of *note Context Manager Types: 148d.

     3.6 版新加入.

 -- 類別: contextlib.AbstractAsyncContextManager

     An *note abstract base class: b38. for classes that implement *note
     object.__aenter__(): 149d. and *note object.__aexit__(): 149e.  A
     default implementation for *note object.__aenter__(): 149d. is
     provided which returns ‘self’ while *note object.__aexit__(): 149e.
     is an abstract method which by default returns ‘None’.  See also
     the definition of *note Asynchronous Context Managers: 149b.

     3.7 版新加入.

 -- 函式: @contextlib.contextmanager

     This function is a *note decorator: 284. that can be used to define
     a factory function for *note with: 6ee. statement context managers,
     without needing to create a class or separate *note __enter__():
     c9a. and *note __exit__(): c9b. 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)

          >>> 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:
     9a7.-iterator when called.  This iterator must yield exactly one
     value, which will be bound to the targets in the *note with: 6ee.
     statement’s ‘as’ clause, if any.

     At the point where the generator yields, the block nested in the
     *note with: 6ee. 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:
     d77...*note except: b43...*note finally: 183. 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(): b83. uses *note ContextDecorator: b82. so
     the context managers it creates can be used as decorators as well
     as in *note with: 6ee. 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(): b83. to meet the requirement that context
     managers support multiple invocations in order to be used as
     decorators).

     3.2 版更變: Use of *note ContextDecorator: b82.

 -- 函式: @contextlib.asynccontextmanager

     Similar to *note contextmanager(): b83, but creates an *note
     asynchronous context manager: 149b.

     This function is a *note decorator: 284. that can be used to define
     a factory function for *note async with: 648. statement
     asynchronous context managers, without needing to create a class or
     separate *note __aenter__(): 149d. and *note __aexit__(): 149e.
     methods.  It must be applied to an *note asynchronous generator:
     1508. function.

     A simple example:

          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 版新加入.

 -- 函式: 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('http://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: 6ee.
     block is exited.
 -- 函式: 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

     An example using `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

     3.7 版新加入.

 -- 函式: 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.

     For example:

          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: 3679.

     3.4 版新加入.

 -- 函式: contextlib.redirect_stdout (new_target)

     Context manager for temporarily redirecting *note sys.stdout: 313.
     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(): 577. normally is sent to
     `sys.stdout'.  You can capture that output in a string by
     redirecting the output to an *note io.StringIO: 832. object:

          f = io.StringIO()
          with redirect_stdout(f):
              help(pow)
          s = f.getvalue()

     To send the output of *note help(): 577. 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(): 577. to `sys.stderr':

          with redirect_stdout(sys.stderr):
              help(pow)

     Note that the global side effect on *note sys.stdout: 313. 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: 3679.

     3.4 版新加入.

 -- 函式: contextlib.redirect_stderr (new_target)

     Similar to *note redirect_stdout(): 6c7. but redirecting *note
     sys.stderr: 314. to another file or file-like object.

     This context manager is *note reentrant: 3679.

     3.5 版新加入.

 -- 類別: 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(): b83, so you
     get this functionality automatically.

     Example of ‘ContextDecorator’:

          from contextlib import ContextDecorator

          class mycontext(ContextDecorator):
              def __enter__(self):
                  print('Starting')
                  return self

              def __exit__(self, *exc):
                  print('Finishing')
                  return False

          >>> @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: 6ee. 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.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

     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: 6ee.
     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: 6ee. 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__():
          c9b. method to the callback stack.  The return value is the
          result of the context manager’s own *note __enter__(): c9a.
          method.

          These context managers may suppress exceptions just as they
          normally would if used directly as part of a *note with: 6ee.
          statement.

      -- 成員函式: push (exit)

          Adds a context manager’s *note __exit__(): c9b. method to the
          callback stack.

          As ‘__enter__’ is `not' invoked, this method can be used to
          cover part of an *note __enter__(): c9a. implementation with a
          context manager’s own *note __exit__(): c9b. 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__(): c9b. 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__(): c9b.
          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: 37b.
          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: 6ee. 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: 149b, similar to *note
     ExitStack: 37b, that supports combining both synchronous and
     asynchronous context managers, as well as having coroutines for
     cleanup logic.

     The ‘close()’ method is not implemented, *note aclose(): 367e. must
     be used instead.

      -- 成員函式: enter_async_context (cm)

          Similar to ‘enter_context()’ but expects an asynchronous
          context manager.

      -- 成員函式: push_async_exit (exit)

          Similar to ‘push()’ but expects either an asynchronous context
          manager or a coroutine function.

      -- 成員函式: push_async_callback (callback, *args, **kwds)

          Similar to ‘callback()’ but expects a coroutine function.

      -- 成員函式: aclose ()

          Similar to ‘close()’ but properly handles awaitables.

     Continuing the example for *note asynccontextmanager(): 37c.:

          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.7.2 Examples and Recipes
.............................

This section describes some examples and recipes for making effective
use of the tools provided by *note contextlib: 24.

* 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.7.3 Supporting a variable number of context managers
.........................................................

The primary use case for *note ExitStack: 37b. is the one given in the
class documentation: supporting a variable number of context managers
and other cleanup operations in a single *note with: 6ee. 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: 37b. also makes it quite easy to use *note
with: 6ee. 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.7.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: 6ee. statement body or the context manager’s ‘__exit__’
method.  By using *note ExitStack: 37b. 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: d77./*note except: b43./*note finally: 183. 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: 37b. can make it easier to handle various situations that
can’t be handled directly in a *note with: 6ee. 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.7.5 Cleaning up in an ‘__enter__’ implementation
.....................................................

As noted in the documentation of *note ExitStack.push(): 367b, this
method can be useful in cleaning up an already allocated resource if
later steps in the *note __enter__(): c9a. 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.7.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: 37b. 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 up 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(): 2a6. 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.7.7 Using a context manager as a function decorator
........................................................

*note ContextDecorator: b82. 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: b82.
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__(): c9a.  If that value is needed, then it is still
necessary to use an explicit ‘with’ statement.

也參考
......

PEP 343(1) - The "with" statement

     The specification, background, and examples for the Python *note
     with: 6ee. statement.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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.7.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: 6ee. 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: 6ee.
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: 6ee. statement will close the file, preventing any
further IO operations using that file object.

Context managers created using *note contextmanager(): b83. 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.7.9 Reentrant context managers
...................................

More sophisticated context managers may be "reentrant".  These context
managers can not only be used in multiple *note with: 6ee. statements,
but may also be used `inside' a ‘with’ statement that is already using
the same context manager.

*note threading.RLock: bf4. is an example of a reentrant context
manager, as are *note suppress(): 831. and *note redirect_stdout(): 6c7.
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(): 6c7, for example, is definitely not
thread safe, as it makes a global modification to the system state by
binding *note sys.stdout: 313. 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.7.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: 236a. is an example of a reusable, but not
reentrant, context manager (for a reentrant lock, it is necessary to use
*note threading.RLock: bf4. instead).

Another example of a reusable, but not reentrant, context manager is
*note ExitStack: 37b, 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: 37b. 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 --- Abstract Base Classes,  Next: atexit --- Exit handlers,  Prev: contextlib --- Utilities for with-statement contexts,  Up: Python Runtime Services

5.29.8 ‘abc’ — Abstract Base Classes
------------------------------------

`Source code:' Lib/abc.py(1)

__________________________________________________________________

This module provides the infrastructure for defining *note abstract base
classes: b38. (ABCs) in Python, as outlined in PEP 3119(2); see the PEP
for why this was added to Python.  (See also PEP 3141(3) and the *note
numbers: c2. module regarding a type hierarchy for numbers based on
ABCs.)

The *note collections: 1e. module has some concrete classes that derive
from ABCs; these can, of course, be further derived.  In addition, the
*note collections.abc: 1f. submodule has some ABCs that can be used to
test whether a class or instance provides a particular interface, for
example, if it is hashable or if it is a mapping.

This module provides the metaclass *note ABCMeta: 81e. for defining ABCs
and a helper class *note ABC: 81d. to alternatively define ABCs through
inheritance:

 -- 類別: abc.ABC

     A helper class that has *note ABCMeta: 81e. as its metaclass.  With
     this class, an abstract base class can be created by simply
     deriving from *note ABC: 81d. avoiding sometimes confusing
     metaclass usage, for example:

          from abc import ABC

          class MyABC(ABC):
              pass

     Note that the type of *note ABC: 81d. is still *note ABCMeta: 81e,
     therefore inheriting from *note ABC: 81d. requires the usual
     precautions regarding metaclass usage, as multiple inheritance may
     lead to metaclass conflicts.  One may also define an abstract base
     class by passing the metaclass keyword and using *note ABCMeta:
     81e. directly, for example:

          from abc import ABCMeta

          class MyABC(metaclass=ABCMeta):
              pass

     3.4 版新加入.

 -- 類別: abc.ABCMeta

     Metaclass for defining Abstract Base Classes (ABCs).

     Use this metaclass to create an ABC. An ABC can be subclassed
     directly, and then acts as a mix-in class.  You can also register
     unrelated concrete classes (even built-in classes) and unrelated
     ABCs as "virtual subclasses" – these and their descendants will be
     considered subclasses of the registering ABC by the built-in *note
     issubclass(): 455. function, but the registering ABC won’t show up
     in their MRO (Method Resolution Order) nor will method
     implementations defined by the registering ABC be callable (not
     even via *note super(): 4e7.).  (4)

     Classes created with a metaclass of *note ABCMeta: 81e. have the
     following method:

      -- 成員函式: register (subclass)

          Register `subclass' as a "virtual subclass" of this ABC. For
          example:

               from abc import ABC

               class MyABC(ABC):
                   pass

               MyABC.register(tuple)

               assert issubclass(tuple, MyABC)
               assert isinstance((), MyABC)

          3.3 版更變: Returns the registered subclass, to allow usage as
          a class decorator.

          3.4 版更變: To detect calls to *note register(): 9d6, you can
          use the *note get_cache_token(): 81c. function.

     You can also override this method in an abstract base class:

      -- 成員函式: __subclasshook__ (subclass)

          (Must be defined as a class method.)

          Check whether `subclass' is considered a subclass of this ABC.
          This means that you can customize the behavior of ‘issubclass’
          further without the need to call *note register(): 9d6. on
          every class you want to consider a subclass of the ABC. (This
          class method is called from the ‘__subclasscheck__()’ method
          of the ABC.)

          This method should return ‘True’, ‘False’ or ‘NotImplemented’.
          If it returns ‘True’, the `subclass' is considered a subclass
          of this ABC. If it returns ‘False’, the `subclass' is not
          considered a subclass of this ABC, even if it would normally
          be one.  If it returns ‘NotImplemented’, the subclass check is
          continued with the usual mechanism.

     For a demonstration of these concepts, look at this example ABC
     definition:

          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)

     The ABC ‘MyIterable’ defines the standard iterable method, *note
     __iter__(): 162f, as an abstract method.  The implementation given
     here can still be called from subclasses.  The ‘get_iterator()’
     method is also part of the ‘MyIterable’ abstract base class, but it
     does not have to be overridden in non-abstract derived classes.

     The *note __subclasshook__(): 368d. class method defined here says
     that any class that has an *note __iter__(): 162f. method in its
     *note __dict__: 501. (or in that of one of its base classes,
     accessed via the *note __mro__: 160a. list) is considered a
     ‘MyIterable’ too.

     Finally, the last line makes ‘Foo’ a virtual subclass of
     ‘MyIterable’, even though it does not define an *note __iter__():
     162f. method (it uses the old-style iterable protocol, defined in
     terms of *note __len__(): dd0. and *note __getitem__(): 27d.).
     Note that this will not make ‘get_iterator’ available as a method
     of ‘Foo’, so it is provided separately.

The *note abc: 4. module also provides the following decorator:

 -- 函式: @abc.abstractmethod

     A decorator indicating abstract methods.

     Using this decorator requires that the class’s metaclass is *note
     ABCMeta: 81e. or is derived from it.  A class that has a metaclass
     derived from *note ABCMeta: 81e. cannot be instantiated unless all
     of its abstract methods and properties are overridden.  The
     abstract methods can be called using any of the normal ’super’ call
     mechanisms.  *note abstractmethod(): 9d3. may be used to declare
     abstract methods for properties and descriptors.

     Dynamically adding abstract methods to a class, or attempting to
     modify the abstraction status of a method or class once it is
     created, are not supported.  The *note abstractmethod(): 9d3. only
     affects subclasses derived using regular inheritance; "virtual
     subclasses" registered with the ABC’s ‘register()’ method are not
     affected.

     When *note abstractmethod(): 9d3. is applied in combination with
     other method descriptors, it should be applied as the innermost
     decorator, as shown in the following usage examples:

          class C(ABC):
              @abstractmethod
              def my_abstract_method(self, ...):
                  ...
              @classmethod
              @abstractmethod
              def my_abstract_classmethod(cls, ...):
                  ...
              @staticmethod
              @abstractmethod
              def my_abstract_staticmethod(...):
                  ...

              @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)

     In order to correctly interoperate with the abstract base class
     machinery, the descriptor must identify itself as abstract using
     ‘__isabstractmethod__’.  In general, this attribute should be
     ‘True’ if any of the methods used to compose the descriptor are
     abstract.  For example, Python’s built-in *note property: 1d8. does
     the equivalent of:

          class Descriptor:
              ...
              @property
              def __isabstractmethod__(self):
                  return any(getattr(f, '__isabstractmethod__', False) for
                             f in (self._fget, self._fset, self._fdel))

          備註: Unlike Java abstract methods, these abstract methods may
          have an implementation.  This implementation can be called via
          the *note super(): 4e7. mechanism from the class that
          overrides it.  This could be useful as an end-point for a
          super-call in a framework that uses cooperative
          multiple-inheritance.

The *note abc: 4. module also supports the following legacy decorators:

 -- 函式: @abc.abstractclassmethod

     3.2 版新加入.

     3.3 版後已棄用: It is now possible to use *note classmethod: 1d9.
     with *note abstractmethod(): 9d3, making this decorator redundant.

     A subclass of the built-in *note classmethod(): 1d9, indicating an
     abstract classmethod.  Otherwise it is similar to *note
     abstractmethod(): 9d3.

     This special case is deprecated, as the *note classmethod(): 1d9.
     decorator is now correctly identified as abstract when applied to
     an abstract method:

          class C(ABC):
              @classmethod
              @abstractmethod
              def my_abstract_classmethod(cls, ...):
                  ...

 -- 函式: @abc.abstractstaticmethod

     3.2 版新加入.

     3.3 版後已棄用: It is now possible to use *note staticmethod: 1da.
     with *note abstractmethod(): 9d3, making this decorator redundant.

     A subclass of the built-in *note staticmethod(): 1da, indicating an
     abstract staticmethod.  Otherwise it is similar to *note
     abstractmethod(): 9d3.

     This special case is deprecated, as the *note staticmethod(): 1da.
     decorator is now correctly identified as abstract when applied to
     an abstract method:

          class C(ABC):
              @staticmethod
              @abstractmethod
              def my_abstract_staticmethod(...):
                  ...

 -- 函式: @abc.abstractproperty

     3.3 版後已棄用: It is now possible to use *note property: 1d8,
     ‘property.getter()’, ‘property.setter()’ and ‘property.deleter()’
     with *note abstractmethod(): 9d3, making this decorator redundant.

     A subclass of the built-in *note property(): 1d8, indicating an
     abstract property.

     This special case is deprecated, as the *note property(): 1d8.
     decorator is now correctly identified as abstract when applied to
     an abstract method:

          class C(ABC):
              @property
              @abstractmethod
              def my_abstract_property(self):
                  ...

     The above example defines a read-only property; you can also define
     a read-write abstract property by appropriately marking one or more
     of the underlying methods as abstract:

          class C(ABC):
              @property
              def x(self):
                  ...

              @x.setter
              @abstractmethod
              def x(self, val):
                  ...

     If only some components are abstract, only those components need to
     be updated to create a concrete property in a subclass:

          class D(C):
              @C.x.setter
              def x(self, val):
                  ...

The *note abc: 4. module also provides the following functions:

 -- 函式: abc.get_cache_token ()

     Returns the current abstract base class cache token.

     The token is an opaque object (that supports equality testing)
     identifying the current version of the abstract base class cache
     for virtual subclasses.  The token changes with every call to *note
     ABCMeta.register(): 9d6. on any ABC.

     3.4 版新加入.

註解
....

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/abc.py

   (2) https://www.python.org/dev/peps/pep-3119

   (3) https://www.python.org/dev/peps/pep-3141

   (4) (1) C++ programmers should note that Python’s virtual base class
concept is not the same as C++’s.


File: python.info,  Node: atexit --- Exit handlers,  Next: traceback --- Print or retrieve a stack traceback,  Prev: abc --- Abstract Base Classes,  Up: Python Runtime Services

5.29.9 ‘atexit’ — Exit handlers
-------------------------------

__________________________________________________________________

The *note atexit: c. module defines functions to register and unregister
cleanup functions.  Functions thus registered are automatically executed
upon normal interpreter termination.  *note atexit: c. runs these
functions in the `reverse' order in which they were registered; if you
register ‘A’, ‘B’, and ‘C’, at interpreter termination time they will be
run in the order ‘C’, ‘B’, ‘A’.

`Note:' The functions registered via this module are not called when the
program is killed by a signal not handled by Python, when a Python fatal
internal error is detected, or when *note os._exit(): 1713. is called.

3.7 版更變: When used with C-API subinterpreters, registered functions
are local to the interpreter they were registered in.

 -- 函式: atexit.register (func, *args, **kwargs)

     Register `func' as a function to be executed at termination.  Any
     optional arguments that are to be passed to `func' must be passed
     as arguments to *note register(): e8a.  It is possible to register
     the same function and arguments more than once.

     At normal program termination (for instance, if *note sys.exit():
     ce7. is called or the main module’s execution completes), all
     functions registered are called in last in, first out order.  The
     assumption is that lower level modules will normally be imported
     before higher level modules and thus must be cleaned up later.

     If an exception is raised during execution of the exit handlers, a
     traceback is printed (unless *note SystemExit: 601. is raised) and
     the exception information is saved.  After all exit handlers have
     had a chance to run the last exception to be raised is re-raised.

     This function returns `func', which makes it possible to use it as
     a decorator.

 -- 函式: atexit.unregister (func)

     Remove `func' from the list of functions to be run at interpreter
     shutdown.  After calling *note unregister(): 3690, `func' is
     guaranteed not to be called when the interpreter shuts down, even
     if it was registered more than once.  *note unregister(): 3690.
     silently does nothing if `func' was not previously registered.

也參考
......

Module *note readline: df.

     Useful example of *note atexit: c. to read and write *note
     readline: df. history files.

* Menu:

* atexit Example::


File: python.info,  Node: atexit Example,  Up: atexit --- Exit handlers

5.29.9.1 ‘atexit’ Example
.........................

The following simple example demonstrates how a module can initialize a
counter from a file when it is imported and save the counter’s updated
value automatically when the program terminates without relying on the
application making an explicit call into this module at termination.

     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)

Positional and keyword arguments may also be passed to *note register():
e8a. to be passed along to the registered function when it is called:

     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')

Usage as a *note decorator: 284.:

     import atexit

     @atexit.register
     def goodbye():
         print("You are now leaving the Python sector.")

This only works with functions that can be called without arguments.


File: python.info,  Node: traceback --- Print or retrieve a stack traceback,  Next: __future__ --- Future statement definitions,  Prev: atexit --- Exit handlers,  Up: Python Runtime Services

5.29.10 ‘traceback’ — Print or retrieve a stack traceback
---------------------------------------------------------

`Source code:' 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 traceback objects — this is the object type that is
stored in the *note sys.last_traceback: 3533. variable and returned as
the third item from *note sys.exc_info(): c64.

The module defines the following functions:

 -- 函式: traceback.print_tb (tb, limit=None, file=None)

     Print up to `limit' stack trace entries from traceback object `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 ‘sys.stderr’; otherwise it should be
     an open file or file-like object to receive the output.

     3.5 版更變: Added negative `limit' support.

 -- 函式: traceback.print_exception (etype, value, tb, limit=None,
          file=None, chain=True)

     Print exception information and stack trace entries from traceback
     object `tb' to `file'.  This differs from *note print_tb(): 77e. in
     the following ways:

        * if `tb' is not ‘None’, it prints a header ‘Traceback (most
          recent call last):’

        * it prints the exception `etype' and `value' after the stack
          trace

        * if `type(value)' is *note SyntaxError: 45d. 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.

     The optional `limit' argument has the same meaning as for *note
     print_tb(): 77e.  If `chain' is true (the default), then chained
     exceptions (the ‘__cause__’ or ‘__context__’ 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'.

 -- 函式: traceback.print_exc (limit=None, file=None, chain=True)

     This is a shorthand for ‘print_exception(*sys.exc_info(), limit,
     file, chain)’.

 -- 函式: traceback.print_last (limit=None, file=None, chain=True)

     This is a shorthand for ‘print_exception(sys.last_type,
     sys.last_value, sys.last_traceback, limit, file, chain)’.  In
     general it will work only after an exception has reached an
     interactive prompt (see *note sys.last_type: c5f.).

 -- 函式: 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 stack frame to start.  The optional `file'
     argument has the same meaning as for *note print_tb(): 77e.

     3.5 版更變: Added negative `limit' support.

 -- 函式: traceback.extract_tb (tb, limit=None)

     Return a *note StackSummary: 77c. object representing a list of
     "pre-processed" stack trace entries extracted from the traceback
     object `tb'.  It is useful for alternate formatting of stack
     traces.  The optional `limit' argument has the same meaning as for
     *note print_tb(): 77e.  A "pre-processed" stack trace entry is a
     *note FrameSummary: 77d. object containing attributes ‘filename’,
     ‘lineno’, ‘name’, and ‘line’ representing the information that is
     usually printed for a stack trace.  The ‘line’ is a string with
     leading and trailing whitespace stripped; if the source is not
     available it is ‘None’.

 -- 函式: traceback.extract_stack (f=None, limit=None)

     Extract the raw traceback from the current stack frame.  The return
     value has the same format as for *note extract_tb(): 3697.  The
     optional `f' and `limit' arguments have the same meaning as for
     *note print_stack(): 77f.

 -- 函式: traceback.format_list (extracted_list)

     Given a list of tuples or *note FrameSummary: 77d. objects as
     returned by *note extract_tb(): 3697. or *note extract_stack():
     3698, 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 (etype, value)

     Format the exception part of a traceback.  The arguments are the
     exception type and value such as given by ‘sys.last_type’ and
     ‘sys.last_value’.  The return value is a list of strings, each
     ending in a newline.  Normally, the list contains a single string;
     however, for *note SyntaxError: 45d. exceptions, it contains
     several lines that (when printed) display detailed information
     about where the syntax error occurred.  The message indicating
     which exception occurred is the always last string in the list.

 -- 函式: traceback.format_exception (etype, 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(): 20b5.  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(): 20b5.

     3.5 版更變: The `etype' argument is ignored and inferred from the
     type of `value'.

 -- 函式: 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)

     A shorthand for ‘format_list(extract_tb(tb, limit))’.

 -- 函式: traceback.format_stack (f=None, limit=None)

     A shorthand for ‘format_list(extract_stack(f, limit))’.

 -- 函式: traceback.clear_frames (tb)

     Clears the local variables of all the stack frames in a traceback
     `tb' by calling the ‘clear()’ method of each frame object.

     3.4 版新加入.

 -- 函式: traceback.walk_stack (f)

     Walk a stack following ‘f.f_back’ 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(): 369d.

     3.5 版新加入.

 -- 函式: traceback.walk_tb (tb)

     Walk a traceback following ‘tb_next’ yielding the frame and line
     number for each frame.  This helper is used with *note
     StackSummary.extract(): 369d.

     3.5 版新加入.

The module also defines the following classes:

* Menu:

* TracebackException Objects::
* StackSummary Objects::
* FrameSummary Objects::
* Traceback Examples::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/traceback.py


File: python.info,  Node: TracebackException Objects,  Next: StackSummary Objects,  Up: traceback --- Print or retrieve a stack traceback

5.29.10.1 ‘TracebackException’ Objects
......................................

3.5 版新加入.

*note TracebackException: 77b. 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)

     Capture an exception for later rendering.  `limit', `lookup_lines'
     and `capture_locals' are as for the *note StackSummary: 77c. class.

     Note that when locals are captured, they are also shown in the
     traceback.

      -- 屬性: __cause__

          A *note TracebackException: 77b. of the original ‘__cause__’.

      -- 屬性: __context__

          A *note TracebackException: 77b. of the original
          ‘__context__’.

      -- 屬性: __suppress_context__

          The ‘__suppress_context__’ value from the original exception.

      -- 屬性: stack

          A *note StackSummary: 77c. representing the traceback.

      -- 屬性: exc_type

          The class of the original traceback.

      -- 屬性: filename

          For syntax errors - the file name where the error occurred.

      -- 屬性: lineno

          For syntax errors - the line number where the error occurred.

      -- 屬性: text

          For syntax errors - the text where the error occurred.

      -- 屬性: offset

          For syntax errors - the offset into the text where the error
          occurred.

      -- 屬性: 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: 77c. class.

          Note that when locals are captured, they are also shown in the
          traceback.

      -- 成員函式: format (*, chain=True)

          Format the exception.

          If `chain' is not ‘True’, ‘__cause__’ and ‘__context__’ 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(): 20b5. is a wrapper around this method which
          just prints the lines to a file.

          The message indicating which exception occurred is always the
          last string in the output.

      -- 成員函式: format_exception_only ()

          Format the exception part of the traceback.

          The return value is a generator of strings, each ending in a
          newline.

          Normally, the generator emits a single string; however, for
          *note SyntaxError: 45d. exceptions, it emits several lines
          that (when printed) display detailed information about where
          the syntax error occurred.

          The message indicating which exception occurred is always the
          last string in the output.


File: python.info,  Node: StackSummary Objects,  Next: FrameSummary Objects,  Prev: TracebackException Objects,  Up: traceback --- Print or retrieve a stack traceback

5.29.10.2 ‘StackSummary’ Objects
................................

3.5 版新加入.

*note StackSummary: 77c. objects represent a call stack ready for
formatting.

 -- 類別: traceback.StackSummary

      -- 成員函式: classmethod extract (frame_gen, *, limit=None,
               lookup_lines=True, capture_locals=False)

          Construct a *note StackSummary: 77c. object from a frame
          generator (such as is returned by *note walk_stack(): 779. or
          *note walk_tb(): 77a.).

          If `limit' is supplied, only this many frames are taken from
          `frame_gen'.  If `lookup_lines' is ‘False’, the returned *note
          FrameSummary: 77d. objects will not have read their lines in
          yet, making the cost of creating the *note StackSummary: 77c.
          cheaper (which may be valuable if it may not actually get
          formatted).  If `capture_locals' is ‘True’ the local variables
          in each *note FrameSummary: 77d. are captured as object
          representations.

      -- 成員函式: classmethod from_list (a_list)

          Construct a *note StackSummary: 77c. object from a supplied
          list of *note FrameSummary: 77d. 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 frame 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.


File: python.info,  Node: FrameSummary Objects,  Next: Traceback Examples,  Prev: StackSummary Objects,  Up: traceback --- Print or retrieve a stack traceback

5.29.10.3 ‘FrameSummary’ Objects
................................

3.5 版新加入.

*note FrameSummary: 77d. objects represent a single frame in a
traceback.

 -- 類別: traceback.FrameSummary (filename, lineno, name,
          lookup_line=True, locals=None, line=None)

     Represent a single frame in the traceback or stack that is being
     formatted or printed.  It may optionally have a stringified version
     of the frames locals included in it.  If `lookup_line' is ‘False’,
     the source code is not looked up until the *note FrameSummary: 77d.
     has the ‘line’ attribute accessed (which also happens when casting
     it to a tuple).  ‘line’ may be directly provided, and will prevent
     line lookups happening at all.  `locals' is an optional local
     variable dictionary, and if supplied the variable representations
     are stored in the summary for later display.


File: python.info,  Node: Traceback Examples,  Prev: FrameSummary Objects,  Up: traceback --- Print or retrieve a stack traceback

5.29.10.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: 1b. 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_death()

     def bright_side_of_death():
         return tuple()[0]

     try:
         lumberjack()
     except IndexError:
         exc_type, exc_value, exc_traceback = sys.exc_info()
         print("*** print_tb:")
         traceback.print_tb(exc_traceback, limit=1, file=sys.stdout)
         print("*** print_exception:")
         # exc_type below is ignored on 3.5 and later
         traceback.print_exception(exc_type, exc_value, exc_traceback,
                                   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:")
         # exc_type below is ignored on 3.5 and later
         print(repr(traceback.format_exception(exc_type, exc_value,
                                               exc_traceback)))
         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_death()
     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_death()
     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...>", line 10, in <module>\n    lumberjack()\n',
      '  File "<doctest...>", line 4, in lumberjack\n    bright_side_of_death()\n',
      '  File "<doctest...>", line 7, in bright_side_of_death\n    return tuple()[0]\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_death>]
     *** format_tb:
     ['  File "<doctest...>", line 10, in <module>\n    lumberjack()\n',
      '  File "<doctest...>", line 4, in lumberjack\n    bright_side_of_death()\n',
      '  File "<doctest...>", line 7, in bright_side_of_death\n    return tuple()[0]\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 statement definitions,  Next: gc --- Garbage Collector interface,  Prev: traceback --- Print or retrieve a stack traceback,  Up: Python Runtime Services

5.29.11 ‘__future__’ — Future statement definitions
---------------------------------------------------

`Source code:' Lib/__future__.py(1)

__________________________________________________________________

*note __future__: 0. is a real module, and serves three purposes:

   * To avoid confusing existing tools that analyze import statements
     and expect to find the modules they’re importing.

   * To ensure that *note future statements: 1592. run under releases
     prior to 2.1 at least yield runtime exceptions (the import of *note
     __future__: 0. will fail, because there was no module of that name
     prior to 2.1).

   * To document when incompatible changes were introduced, and when
     they will be — or were — made mandatory.  This is a form of
     executable documentation, and can be inspected programmatically via
     importing *note __future__: 0. and examining its contents.

Each statement in ‘__future__.py’ is of the form:

     FeatureName = _Feature(OptionalRelease, MandatoryRelease,
                            CompilerFlag)

where, normally, `OptionalRelease' is less than `MandatoryRelease', and
both are 5-tuples of the same form as *note sys.version_info: b1f.:

     (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
     )

`OptionalRelease' records the first release in which the feature was
accepted.

In the case of a `MandatoryRelease' that has not yet occurred,
`MandatoryRelease' predicts the release in which the feature will become
part of the language.

Else `MandatoryRelease' records when the feature became part of the
language; in releases at or after that, modules no longer need a future
statement to use the feature in question, but may continue to use such
imports.

`MandatoryRelease' may also be ‘None’, meaning that a planned feature
got dropped.

Instances of class ‘_Feature’ have two corresponding methods,
‘getOptionalRelease()’ and ‘getMandatoryRelease()’.

`CompilerFlag' is the (bitfield) flag that should be passed in the
fourth argument to the built-in function *note compile(): 1b5. to enable
the feature in dynamically compiled code.  This flag is stored in the
‘compiler_flag’ attribute on ‘_Feature’ instances.

No feature description will ever be deleted from *note __future__: 0.
Since its introduction in Python 2.1 the following features have found
their way into the language using this mechanism:

feature                optional in       mandatory in       effect
                                                            
--------------------------------------------------------------------------------------------------------------
                                                            
nested_scopes          2.1.0b1           2.2                PEP 227(2): `Statically Nested Scopes'
                                                            
                                                            
generators             2.2.0a1           2.3                PEP 255(3): `Simple Generators'
                                                            
                                                            
division               2.2.0a2           3.0                PEP 238(4): `Changing the Division Operator'
                                                            
                                                            
absolute_import        2.5.0a1           3.0                PEP 328(5): `Imports: Multi-Line and
                                                            Absolute/Relative'
                                                            
                                                            
with_statement         2.5.0a1           2.6                PEP 343(6): `The "with" Statement'
                                                            
                                                            
print_function         2.6.0a2           3.0                PEP 3105(7): `Make print a function'
                                                            
                                                            
unicode_literals       2.6.0a2           3.0                PEP 3112(8): `Bytes literals in Python 3000'
                                                            
                                                            
generator_stop         3.5.0b1           3.7                PEP 479(9): `StopIteration handling inside
                                                            generators'
                                                            
                                                            
annotations            3.7.0b1           3.10               PEP 563(10): `Postponed evaluation of
                                                            annotations'
                                                            

也參考
......

*note Future statements: 1592.

     How the compiler treats future imports.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/__future__.py

   (2) https://www.python.org/dev/peps/pep-0227

   (3) https://www.python.org/dev/peps/pep-0255

   (4) https://www.python.org/dev/peps/pep-0238

   (5) https://www.python.org/dev/peps/pep-0328

   (6) https://www.python.org/dev/peps/pep-0343

   (7) https://www.python.org/dev/peps/pep-3105

   (8) https://www.python.org/dev/peps/pep-3112

   (9) https://www.python.org/dev/peps/pep-0479

   (10) https://www.python.org/dev/peps/pep-0563


File: python.info,  Node: gc --- Garbage Collector interface,  Next: inspect --- Inspect live objects,  Prev: __future__ --- Future statement definitions,  Up: Python Runtime Services

5.29.12 ‘gc’ — Garbage Collector interface
------------------------------------------

__________________________________________________________________

This module provides an interface to the optional garbage collector.  It
provides the ability to disable the collector, tune the collection
frequency, and set debugging options.  It also provides access to
unreachable objects that the collector found but cannot free.  Since the
collector supplements the reference counting already used in Python, you
can disable the collector if you are sure your program does not create
reference cycles.  Automatic collection can be disabled by calling
‘gc.disable()’.  To debug a leaking program call
‘gc.set_debug(gc.DEBUG_LEAK)’.  Notice that this includes
‘gc.DEBUG_SAVEALL’, causing garbage-collected objects to be saved in
gc.garbage for inspection.

The *note gc: 86. module provides the following functions:

 -- 函式: gc.enable ()

     Enable automatic garbage collection.

 -- 函式: gc.disable ()

     Disable automatic garbage collection.

 -- 函式: gc.isenabled ()

     Return ‘True’ if automatic collection is enabled.

 -- 函式: gc.collect (generation=2)

     With no arguments, run a full collection.  The optional argument
     `generation' may be an integer specifying which generation to
     collect (from 0 to 2).  A *note ValueError: 1fc. is raised if the
     generation number is invalid.  The number of unreachable objects
     found is returned.

     The free lists maintained for a number of built-in types are
     cleared whenever a full collection or collection of the highest
     generation (2) is run.  Not all items in some free lists may be
     freed due to the particular implementation, in particular *note
     float: 188.

 -- 函式: gc.set_debug (flags)

     Set the garbage collection debugging flags.  Debugging information
     will be written to ‘sys.stderr’.  See below for a list of debugging
     flags which can be combined using bit operations to control
     debugging.

 -- 函式: gc.get_debug ()

     Return the debugging flags currently set.

 -- 函式: 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 tracked by the collector that are in that generation.

     3.8 版更變: New `generation' parameter.

     Raises an *note auditing event: e96. ‘gc.get_objects’ with argument
     ‘generation’.

 -- 函式: gc.get_stats ()

     Return a list of three per-generation dictionaries containing
     collection statistics since interpreter start.  The number of keys
     may change in the future, but currently each dictionary will
     contain the following items:

        * ‘collections’ is the number of times this generation was
          collected;

        * ‘collected’ is the total number of objects collected inside
          this generation;

        * ‘uncollectable’ is the total number of objects which were
          found to be uncollectable (and were therefore moved to the
          *note garbage: b45. list) inside this generation.

     3.4 版新加入.

 -- 函式: gc.set_threshold (threshold0[, threshold1[, threshold2]])

     Set the garbage collection thresholds (the collection frequency).
     Setting `threshold0' to zero disables collection.

     The GC classifies objects into three generations depending on how
     many collection sweeps they have survived.  New objects are placed
     in the youngest generation (generation ‘0’).  If an object survives
     a collection it is moved into the next older generation.  Since
     generation ‘2’ is the oldest generation, objects in that generation
     remain there after a collection.  In order to decide when to run,
     the collector keeps track of the number object allocations and
     deallocations since the last collection.  When the number of
     allocations minus the number of deallocations exceeds `threshold0',
     collection starts.  Initially only generation ‘0’ is examined.  If
     generation ‘0’ has been examined more than `threshold1' times since
     generation ‘1’ has been examined, then generation ‘1’ is examined
     as well.  With the third generation, things are a bit more
     complicated, see Collecting the oldest generation(1) for more
     information.

 -- 函式: gc.get_count ()

     Return the current collection counts as a tuple of ‘(count0,
     count1, count2)’.

 -- 函式: gc.get_threshold ()

     Return the current collection thresholds as a tuple of
     ‘(threshold0, threshold1, threshold2)’.

 -- 函式: gc.get_referrers (*objs)

     Return the list of objects that directly refer to any of objs.
     This function will only locate those containers which support
     garbage collection; extension types which do refer to other objects
     but do not support garbage collection will not be found.

     Note that objects which have already been dereferenced, but which
     live in cycles and have not yet been collected by the garbage
     collector can be listed among the resulting referrers.  To get only
     currently live objects, call *note collect(): 22f. before calling
     *note get_referrers(): ea9.

          警告: Care must be taken when using objects returned by *note
          get_referrers(): ea9. because some of them could still be
          under construction and hence in a temporarily invalid state.
          Avoid using *note get_referrers(): ea9. for any purpose other
          than debugging.

     Raises an *note auditing event: e96. ‘gc.get_referrers’ with
     argument ‘objs’.

 -- 函式: gc.get_referents (*objs)

     Return a list of objects directly referred to by any of the
     arguments.  The referents returned are those objects visited by the
     arguments’ C-level *note tp_traverse: 36be. methods (if any), and
     may not be all objects actually directly reachable.  *note
     tp_traverse: 36be. methods are supported only by objects that
     support garbage collection, and are only required to visit objects
     that may be involved in a cycle.  So, for example, if an integer is
     directly reachable from an argument, that integer object may or may
     not appear in the result list.

     Raises an *note auditing event: e96. ‘gc.get_referents’ with
     argument ‘objs’.

 -- 函式: gc.is_tracked (obj)

     Returns ‘True’ if the object is currently tracked by the garbage
     collector, ‘False’ otherwise.  As a general rule, instances of
     atomic types aren’t tracked and instances of non-atomic types
     (containers, user-defined objects...)  are.  However, some
     type-specific optimizations can be present in order to suppress the
     garbage collector footprint of simple instances (e.g.  dicts
     containing only atomic keys and values):

          >>> 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.freeze ()

     Freeze all the objects tracked by gc - move them to a permanent
     generation and ignore all the future collections.  This can be used
     before a POSIX fork() call to make the gc copy-on-write friendly or
     to speed up collection.  Also collection before a POSIX fork() call
     may free pages for future allocation which can cause copy-on-write
     too so it’s advised to disable gc in parent process and freeze
     before fork and enable gc in child process.

     3.7 版新加入.

 -- 函式: gc.unfreeze ()

     Unfreeze the objects in the permanent generation, put them back
     into the oldest generation.

     3.7 版新加入.

 -- 函式: gc.get_freeze_count ()

     Return the number of objects in the permanent generation.

     3.7 版新加入.

The following variables are provided for read-only access (you can
mutate the values but should not rebind them):

 -- Data: gc.garbage

     A list of objects which the collector found to be unreachable but
     could not be freed (uncollectable objects).  Starting with Python
     3.4, this list should be empty most of the time, except when using
     instances of C extension types with a non-‘NULL’ ‘tp_del’ slot.

     If *note DEBUG_SAVEALL: 36bf. is set, then all unreachable objects
     will be added to this list rather than freed.

     3.2 版更變: If this list is non-empty at *note interpreter
     shutdown: 768, a *note ResourceWarning: 4d5. is emitted, which is
     silent by default.  If *note DEBUG_UNCOLLECTABLE: b46. is set, in
     addition all uncollectable objects are printed.

     3.4 版更變: Following PEP 442(2), objects with a *note __del__():
     924. method don’t end up in *note gc.garbage: b45. anymore.

 -- Data: gc.callbacks

     A list of callbacks that will be invoked by the garbage collector
     before and after collection.  The callbacks will be called with two
     arguments, `phase' and `info'.

     `phase' can be one of two values:

          "start": The garbage collection is about to start.

          "stop": The garbage collection has finished.

     `info' is a dict providing more information for the callback.  The
     following keys are currently defined:

          "generation": The oldest generation being collected.

          "collected": When `phase' is "stop", the number of objects
          successfully collected.

          "uncollectable": When `phase' is "stop", the number of objects
          that could not be collected and were put in *note garbage:
          b45.

     Applications can add their own callbacks to this list.  The primary
     use cases are:

          Gathering statistics about garbage collection, such as how
          often various generations are collected, and how long the
          collection takes.

          Allowing applications to identify and clear their own
          uncollectable types when they appear in *note garbage: b45.

     3.3 版新加入.

The following constants are provided for use with *note set_debug():
36b9.:

 -- Data: gc.DEBUG_STATS

     Print statistics during collection.  This information can be useful
     when tuning the collection frequency.

 -- Data: gc.DEBUG_COLLECTABLE

     Print information on collectable objects found.

 -- Data: gc.DEBUG_UNCOLLECTABLE

     Print information of uncollectable objects found (objects which are
     not reachable but cannot be freed by the collector).  These objects
     will be added to the ‘garbage’ list.

     3.2 版更變: Also print the contents of the *note garbage: b45. list
     at *note interpreter shutdown: 768, if it isn’t empty.

 -- Data: gc.DEBUG_SAVEALL

     When set, all unreachable objects found will be appended to
     `garbage' rather than being freed.  This can be useful for
     debugging a leaking program.

 -- Data: gc.DEBUG_LEAK

     The debugging flags necessary for the collector to print
     information about a leaking program (equal to ‘DEBUG_COLLECTABLE |
     DEBUG_UNCOLLECTABLE | DEBUG_SAVEALL’).

   ---------- Footnotes ----------

   (1) 
https://devguide.python.org/garbage_collector/#collecting-the-oldest-generation

   (2) https://www.python.org/dev/peps/pep-0442


File: python.info,  Node: inspect --- Inspect live objects,  Next: site --- Site-specific configuration hook,  Prev: gc --- Garbage Collector interface,  Up: Python Runtime Services

5.29.13 ‘inspect’ — Inspect live objects
----------------------------------------

`Source code:' Lib/inspect.py(1)

__________________________________________________________________

The *note inspect: a1. 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::
* Retrieving source code::
* Introspecting callables with the Signature object::
* Classes and functions: Classes and functions<2>.
* The interpreter stack::
* Fetching attributes statically::
* Current State of Generators and Coroutines::
* Code Objects Bit Flags::
* Command Line Interface: Command Line Interface<3>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/inspect.py


File: python.info,  Node: Types and members,  Next: Retrieving source code,  Up: inspect --- Inspect live objects

5.29.13.1 Types and members
...........................

The *note getmembers(): 36c7. 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(): 36c7.  They also help you determine when you can
expect to find the following special attributes:

Type            Attribute               描述
                                        
------------------------------------------------------------------------
                                        
module          __doc__                 documentation string
                                        
                                        
                __file__                filename (missing for
                                        built-in modules)
                                        
                                        
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
                                        
                                        
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
                                        
                                        
function        __doc__                 documentation string
                                        
                                        
                __name__                name with which this function
                                        was defined
                                        
                                        
                __qualname__            qualified name
                                        
                                        
                __code__                code object containing
                                        compiled function
                                        *note bytecode: 619.
                                        
                                        
                __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
                                        
                                        
                __annotations__         mapping of parameters names
                                        to annotations; ‘"return"’
                                        key is reserved for return
                                        annotations.
                                        
                                        
                __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: 36c8.
                                        
                                        
                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_names                tuple of names of local
                                        variables
                                        
                                        
                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’
                                        
                                        
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(): 3f8.
                                        
                                        
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 版更變: Add ‘__qualname__’ and ‘gi_yieldfrom’ attributes to
generators.

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 版更變: Add ‘cr_origin’ attribute to coroutines.

 -- 函式: 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(): 36c7. 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__(): 320.

 -- 函式: 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(): 36c9.  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 版更變: The function is based directly on *note importlib: 9b.

 -- 函式: inspect.ismodule (object)

     Return ‘True’ if the object is a module.

 -- 函式: 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: 36ce. expression.

 -- 函式: inspect.isgeneratorfunction (object)

     Return ‘True’ if the object is a Python generator function.

     3.8 版更變: Functions wrapped in *note functools.partial(): 7cd.
     now return ‘True’ if the wrapped function is a Python generator
     function.

 -- 函式: inspect.isgenerator (object)

     Return ‘True’ if the object is a generator.

 -- 函式: inspect.iscoroutinefunction (object)

     Return ‘True’ if the object is a *note coroutine function: 644. (a
     function defined with an *note async def: 285. syntax).

     3.5 版新加入.

     3.8 版更變: Functions wrapped in *note functools.partial(): 7cd.
     now return ‘True’ if the wrapped function is a *note coroutine
     function: 644.

 -- 函式: inspect.iscoroutine (object)

     Return ‘True’ if the object is a *note coroutine: 1a7. created by
     an *note async def: 285. function.

     3.5 版新加入.

 -- 函式: inspect.isawaitable (object)

     Return ‘True’ if the object can be used in *note await: 1a4.
     expression.

     Can also be used to distinguish generator-based coroutines from
     regular generators:

          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:
     1508. function, for example:

          >>> async def agen():
          ...     yield 1
          ...
          >>> inspect.isasyncgenfunction(agen)
          True

     3.6 版新加入.

     3.8 版更變: Functions wrapped in *note functools.partial(): 7cd.
     now return ‘True’ if the wrapped function is a *note asynchronous
     generator: 1508. function.

 -- 函式: inspect.isasyncgen (object)

     Return ‘True’ if the object is an *note asynchronous generator
     iterator: 3634. created by an *note asynchronous generator: 1508.
     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)

     Return ‘True’ if the object is a code.

 -- 函式: inspect.isbuiltin (object)

     Return ‘True’ if the object is a built-in function or a bound
     built-in method.

 -- 函式: inspect.isroutine (object)

     Return ‘True’ if the object is a user-defined or built-in function
     or method.

 -- 函式: inspect.isabstract (object)

     Return ‘True’ if the object is an abstract base class.

 -- 函式: inspect.ismethoddescriptor (object)

     Return ‘True’ if the object is a method descriptor, but not if
     *note ismethod(): 36cc, *note isclass(): 36cb, *note isfunction():
     36cd. or *note isbuiltin(): 36d4. are true.

     This, for example, is true of ‘int.__add__’.  An object passing
     this test has a *note __get__(): 1440. method but not a *note
     __set__(): 1444. method, but beyond that the set of attributes
     varies.  A *note __name__: c6c. 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(): 36d7.
     test, simply because the other tests promise more – you can, e.g.,
     count on having the ‘__func__’ attribute (etc) when an object
     passes *note ismethod(): 36cc.

 -- 函式: inspect.isdatadescriptor (object)

     Return ‘True’ if the object is a data descriptor.

     Data descriptors have a *note __set__: 1444. or a *note __delete__:
     1445. 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__: c6c. 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 implementation detail:' getsets are attributes defined in
     extension modules via *note PyGetSetDef: 42c. structures.  For
     Python implementations without such types, this method will always
     return ‘False’.

 -- 函式: inspect.ismemberdescriptor (object)

     Return ‘True’ if the object is a member descriptor.

     `CPython implementation detail:' Member descriptors are attributes
     defined in extension modules via *note PyMemberDef: 42b.
     structures.  For Python implementations without such types, this
     method will always return ‘False’.


File: python.info,  Node: Retrieving source code,  Next: Introspecting callables with the Signature object,  Prev: Types and members,  Up: inspect --- Inspect live objects

5.29.13.2 Retrieving source code
................................

 -- 函式: inspect.getdoc (object)

     Get the documentation string for an object, cleaned up with *note
     cleandoc(): 36dd.  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.

     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: 193. if the object
     is a built-in module, class, or function.

 -- 函式: inspect.getmodule (object)

     Try to guess which module an object was defined in.

 -- 函式: inspect.getsourcefile (object)

     Return the name of the Python source file in which an object was
     defined.  This will fail with a *note TypeError: 193. 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: 1d4. is raised if the source code
     cannot be retrieved.

     3.3 版更變: *note OSError: 1d4. is raised instead of *note IOError:
     997, 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: 1d4. is raised if the source code cannot be retrieved.

     3.3 版更變: *note OSError: 1d4. is raised instead of *note IOError:
     997, 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: Classes and functions<2>,  Prev: Retrieving source code,  Up: inspect --- Inspect live objects

5.29.13.3 Introspecting callables with the Signature object
...........................................................

3.3 版新加入.

The Signature object represents the call signature of a callable object
and its return annotation.  To retrieve a Signature object, use the
*note signature(): 560. function.

 -- 函式: inspect.signature (callable, *, follow_wrapped=True)

     Return a *note Signature: 6f8. 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(): 7cd. objects.

     Raises *note ValueError: 1fc. if no signature can be provided, and
     *note TypeError: 193. if that type of object is not supported.

     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: 15f8.

     3.5 版新加入: ‘follow_wrapped’ parameter.  Pass ‘False’ to get a
     signature of ‘callable’ specifically (‘callable.__wrapped__’ will
     not be used to unwrap decorated callables.)

          備註: 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.

 -- 類別: 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: 6f9. object in its *note parameters:
     36e2. collection.

     The optional `parameters' argument is a sequence of *note
     Parameter: 6f9. 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, is the "return" annotation of the callable.

     Signature objects are `immutable'.  Use *note Signature.replace():
     36e3. to make a modified copy.

     3.5 版更變: Signature objects are picklable and hashable.

      -- 屬性: 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: 6f9. 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: 36e4.

      -- 成員函式: bind (*args, **kwargs)

          Create a mapping from positional and keyword arguments to
          parameters.  Returns *note BoundArguments: 9ad. if ‘*args’ and
          ‘**kwargs’ match the signature, or raises a *note TypeError:
          193.

      -- 成員函式: bind_partial (*args, **kwargs)

          Works the same way as *note Signature.bind(): 36e6, but allows
          the omission of some required arguments (mimics *note
          functools.partial(): 7cd. behavior.)  Returns *note
          BoundArguments: 9ad, or raises a *note TypeError: 193. if the
          passed arguments do not match the signature.

      -- 成員函式: replace (*[, parameters][, return_annotation])

          Create a new Signature instance based on the instance replace
          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:
          36e4.

               >>> 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'"

      -- 成員函式: classmethod from_callable (obj, *,
               follow_wrapped=True)

          Return a *note Signature: 6f8. (or its subclass) object for a
          given callable ‘obj’.  Pass ‘follow_wrapped=False’ to get a
          signature of ‘obj’ without unwrapping its ‘__wrapped__’ chain.

          This method simplifies subclassing of *note Signature: 6f8.:

               class MySignature(Signature):
                   pass
               sig = MySignature.from_callable(min)
               assert isinstance(sig, MySignature)

          3.5 版新加入.

 -- 類別: 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(): 36e8. to
     create a modified copy.

     3.5 版更變: Parameter objects are picklable and hashable.

      -- 屬性: 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 implementation detail:' 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 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:
          36e9.

      -- 屬性: annotation

          The annotation for the parameter.  If the parameter has no
          annotation, this attribute is set to *note Parameter.empty:
          36e9.

      -- 屬性: kind

          Describes how argument values are bound to the parameter.
          Possible values (accessible via *note Parameter: 6f9, like
          ‘Parameter.KEYWORD_ONLY’):

          Name                         Meaning
                                       
          --------------------------------------------------------------------------------
                                       
          `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 a enum value of Parameter.kind.

          3.8 版新加入.

          Example: print all descriptions of arguments:

               >>> 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 Parameter instance based on the instance
               replaced was invoked on.  To override a *note Parameter:
               6f9. attribute, pass the corresponding argument.  To
               remove a default value or/and an annotation from a
               Parameter, pass *note Parameter.empty: 36e9.

                    >>> 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'"

          3.4 版更變: In Python 3.3 Parameter 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(): 36e6. or *note
     Signature.bind_partial(): 36e7. call.  Holds the mapping of
     arguments to the function’s parameters.

      -- 屬性: arguments

          An ordered, mutable mapping (*note collections.OrderedDict:
          1ba.) of parameters’ names to arguments’ values.  Contains
          only explicitly bound arguments.  Changes in *note arguments:
          36ef. will reflect in *note args: 36f0. and *note kwargs:
          36f1.

          Should be used in conjunction with *note Signature.parameters:
          36e2. for any argument processing purposes.

               備註: Arguments for which *note Signature.bind(): 36e6.
               or *note Signature.bind_partial(): 36e7. relied on a
               default value are skipped.  However, if needed, use *note
               BoundArguments.apply_defaults(): 6fa. to add them.

      -- 屬性: args

          A tuple of positional arguments values.  Dynamically computed
          from the *note arguments: 36ef. attribute.

      -- 屬性: kwargs

          A dict of keyword arguments values.  Dynamically computed from
          the *note arguments: 36ef. attribute.

      -- 屬性: signature

          A reference to the parent *note Signature: 6f8. object.

      -- 成員函式: apply_defaults ()

          Set default values for missing arguments.

          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
               OrderedDict([('a', 'spam'), ('b', 'ham'), ('args', ())])

          3.5 版新加入.

     The *note args: 36f0. and *note kwargs: 36f1. 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://www.python.org/dev/peps/pep-0362


File: python.info,  Node: Classes and functions<2>,  Next: The interpreter stack,  Prev: Introspecting callables with the Signature object,  Up: inspect --- Inspect live objects

5.29.13.4 Classes and functions
...............................

 -- 函式: 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.getargspec (func)

     Get the names and default values of a Python function’s parameters.
     A *note named tuple: aa8. ‘ArgSpec(args, varargs, keywords,
     defaults)’ is returned.  `args' is a list of the parameter names.
     `varargs' and `keywords' are the names of the ‘*’ and ‘**’
     parameters or ‘None’.  `defaults' is a tuple of default argument
     values or ‘None’ if there are no default arguments; if this tuple
     has `n' elements, they correspond to the last `n' elements listed
     in `args'.

     3.0 版後已棄用: Use *note getfullargspec(): 562. for an updated API
     that is usually a drop-in replacement, but also correctly handles
     function annotations and keyword-only parameters.

     Alternatively, use *note signature(): 560. and *note Signature
     Object: 36e0, which provide a more structured introspection API for
     callables.

 -- 函式: inspect.getfullargspec (func)

     Get the names and default values of a Python function’s parameters.
     A *note named tuple: aa8. 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(): 560. and *note Signature Object: 36e0.
     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(): 560,
     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(): 560. 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 *note getargspec(): 561. 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: aa8. ‘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.formatargspec (args[, varargs, varkw, defaults,
          kwonlyargs, kwonlydefaults, annotations[, formatarg,
          formatvarargs, formatvarkw, formatvalue, formatreturns,
          formatannotations]])

     Format a pretty argument spec from the values returned by *note
     getfullargspec(): 562.

     The first seven arguments are (‘args’, ‘varargs’, ‘varkw’,
     ‘defaults’, ‘kwonlyargs’, ‘kwonlydefaults’, ‘annotations’).

     The other six arguments are functions that are called to turn
     argument names, ‘*’ argument name, ‘**’ argument name, default
     values, return annotation and individual annotations into strings,
     respectively.

     For example:

          >>> from inspect import formatargspec, getfullargspec
          >>> def f(a: int, b: float):
          ...     pass
          ...
          >>> formatargspec(*getfullargspec(f))
          '(a: int, b: float)'

     3.5 版後已棄用: Use *note signature(): 560. and *note Signature
     Object: 36e0, which provide a better introspecting API for
     callables.

 -- 函式: inspect.formatargvalues (args[, varargs, varkw, locals,
          formatarg, formatvarargs, formatvarkw, formatvalue])

     Format a pretty argument spec from the four values returned by
     *note getargvalues(): 7bd.  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 版後已棄用: Use *note Signature.bind(): 36e6. and *note
     Signature.bind_partial(): 36e7. instead.

 -- 函式: 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: aa8.
     ‘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.

     *note TypeError: 193. is raised if `func' is not a Python function
     or method.

     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(): 560. uses
     this to stop unwrapping if any object in the chain has a
     ‘__signature__’ attribute defined.

     *note ValueError: 1fc. is raised if a cycle is encountered.

     3.4 版新加入.


File: python.info,  Node: The interpreter stack,  Next: Fetching attributes statically,  Prev: Classes and functions<2>,  Up: inspect --- Inspect live objects

5.29.13.5 The interpreter stack
...............................

When the following functions return "frame records," each record is a
*note named tuple: aa8. ‘FrameInfo(frame, filename, lineno, function,
code_context, index)’.  The tuple contains the frame object, the
filename, the line number of the current line, the function name, a list
of lines of context from the source code, and the index of the current
line within that list.

3.5 版更變: Return a named tuple instead of a tuple.

     備註: 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: 183. clause.  This is also important
     if the cycle detector was disabled when Python was compiled or
     using *note gc.disable(): 36b7.  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(): 810. 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 named
     tuple: aa8. ‘Traceback(filename, lineno, function, code_context,
     index)’ is returned.

 -- 函式: inspect.getouterframes (frame, context=1)

     Get a list of frame records 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: aa8. ‘FrameInfo(frame,
     filename, lineno, function, code_context, index)’ is returned.

 -- 函式: inspect.getinnerframes (traceback, context=1)

     Get a list of frame records 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: aa8. ‘FrameInfo(frame,
     filename, lineno, function, code_context, index)’ is returned.

 -- 函式: inspect.currentframe ()

     Return the frame object for the caller’s stack frame.

     `CPython implementation detail:' 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 frame records 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: aa8. ‘FrameInfo(frame,
     filename, lineno, function, code_context, index)’ is returned.

 -- 函式: inspect.trace (context=1)

     Return a list of frame records 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: aa8. ‘FrameInfo(frame,
     filename, lineno, function, code_context, index)’ is returned.


File: python.info,  Node: Fetching attributes statically,  Next: Current State of Generators and Coroutines,  Prev: The interpreter stack,  Up: inspect --- Inspect live objects

5.29.13.6 Fetching attributes statically
........................................

Both *note getattr(): 44d. and *note hasattr(): 44c. can trigger code
execution when fetching or checking for the existence of attributes.
Descriptors, like properties, will be invoked and *note __getattr__():
31f. and *note __getattribute__(): 44e. may be called.

For cases where you want passive introspection, like documentation
tools, this can be inconvenient.  *note getattr_static(): bd0. has the
same signature as *note getattr(): 44d. 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__(): 31f. or *note
     __getattribute__(): 44e.

     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__: 501. is shadowed by another member
     (for example a property) then this function will be unable to find
     instance members.

     3.2 版新加入.

*note getattr_static(): bd0. 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 and Coroutines,  Next: Code Objects Bit Flags,  Prev: Fetching attributes statically,  Up: inspect --- Inspect live objects

5.29.13.7 Current State of Generators and Coroutines
....................................................

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(): bcf. 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: 285.
     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 版新加入.

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():
     45a. in the body of the generator, and all the same caveats apply.

     If `generator' is a *note generator: 9a7. with no currently
     associated frame, then an empty dictionary is returned.  *note
     TypeError: 193. is raised if `generator' is not a Python generator
     object.

     `CPython implementation detail:' 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(): a1f, but
     works for coroutine objects created by *note async def: 285.
     functions.

     3.5 版新加入.


File: python.info,  Node: Code Objects Bit Flags,  Next: Command Line Interface<3>,  Prev: Current State of Generators and Coroutines,  Up: inspect --- Inspect live objects

5.29.13.8 Code Objects Bit Flags
................................

Python code objects have a ‘co_flags’ attribute, which is a bitmap of
the following flags:

 -- Data: inspect.CO_OPTIMIZED

     The code object is optimized, using fast locals.

 -- Data: inspect.CO_NEWLOCALS

     If set, a new dict will be created for the frame’s ‘f_locals’ when
     the code object is executed.

 -- Data: inspect.CO_VARARGS

     The code object has a variable positional parameter (‘*args’-like).

 -- Data: inspect.CO_VARKEYWORDS

     The code object has a variable keyword parameter (‘**kwargs’-like).

 -- Data: inspect.CO_NESTED

     The flag is set when the code object is a nested function.

 -- Data: 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.

 -- Data: inspect.CO_NOFREE

     The flag is set if there are no free or cell variables.

 -- Data: 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 版新加入.

 -- Data: 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 版新加入.

 -- Data: 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: a1. module for any introspection needs.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0492

   (2) https://www.python.org/dev/peps/pep-0492

   (3) https://www.python.org/dev/peps/pep-0525


File: python.info,  Node: Command Line Interface<3>,  Prev: Code Objects Bit Flags,  Up: inspect --- Inspect live objects

5.29.13.9 Command Line Interface
................................

The *note inspect: a1. 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.

 -- 程式選項: --details

     Print information about the specified object rather than the source
     code


File: python.info,  Node: site --- Site-specific configuration hook,  Prev: inspect --- Inspect live objects,  Up: Python Runtime Services

5.29.14 ‘site’ — Site-specific configuration hook
-------------------------------------------------

`Source code:' Lib/site.py(1)

__________________________________________________________________

`This module is automatically imported during initialization.'  The
automatic import can be suppressed using the interpreter’s *note -S:
b29. option.

Importing this module will append site-specific paths to the module
search path and add a few builtins, unless *note -S: b29. was used.  In
that case, 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
site.main(): 134c. function.

3.3 版更變: Importing the module used to trigger paths manipulation even
when using *note -S: b29.

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'/site-packages’ (on Unix and Macintosh).  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.

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.

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.

After these path manipulations, an attempt is made to import a module
named ‘sitecustomize’, 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: 339. or its subclass exception, and the exception’s ‘name’
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 ‘sitecustomize’ is ignored.  Any other exception
causes a silent and perhaps mysterious failure of the process.

After this, an attempt is made to import a module named ‘usercustomize’,
which can perform arbitrary user-specific customizations, if *note
ENABLE_USER_SITE: 370c. 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: d1a.  If this import fails with
an *note ImportError: 339. or its subclass exception, and the
exception’s ‘name’ 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
‘sitecustomize’ and ‘usercustomize’ is still attempted.

* Menu:

* Readline configuration::
* Module contents: Module contents<3>.
* Command Line Interface: Command Line Interface<4>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/site.py


File: python.info,  Node: Readline configuration,  Next: Module contents<3>,  Up: site --- Site-specific configuration hook

5.29.14.1 Readline configuration
................................

On systems that support *note readline: df, this module will also import
and configure the *note rlcompleter: e2. module, if Python is started in
*note interactive mode: 8e8. and without the *note -S: b29. 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__: 8e9. attribute in your ‘sitecustomize’ or
‘usercustomize’ module or your *note PYTHONSTARTUP: 8ea. file.

3.4 版更變: Activation of rlcompleter and history was made automatic.


File: python.info,  Node: Module contents<3>,  Next: Command Line Interface<4>,  Prev: Readline configuration,  Up: site --- Site-specific configuration hook

5.29.14.2 Module contents
.........................

 -- Data: site.PREFIXES

     A list of prefixes for site-packages directories.

 -- Data: 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:
     d1a. or *note PYTHONNOUSERSITE: d1b.).  ‘None’ means it was
     disabled for security reasons (mismatch between user or group id
     and effective id) or by an administrator.

 -- Data: site.USER_SITE

     Path to the user site-packages for the running Python.  Can be
     ‘None’ if *note getusersitepackages(): bda. hasn’t been called yet.
     Default value is ‘~/.local/lib/python`X.Y'/site-packages’ for UNIX
     and non-framework Mac OS X builds,
     ‘~/Library/Python/`X.Y'/lib/python/site-packages’ for Mac framework
     builds, and ‘`%APPDATA%'\Python\Python`XY'\site-packages’ on
     Windows.  This directory is a site directory, which means that
     ‘.pth’ files in it will be processed.

 -- Data: site.USER_BASE

     Path to the base directory for the user site-packages.  Can be
     ‘None’ if *note getuserbase(): bd9. hasn’t been called yet.
     Default value is ‘~/.local’ for UNIX and Mac OS X non-framework
     builds, ‘~/Library/Python/`X.Y'’ for Mac framework builds, and
     ‘`%APPDATA%'\Python’ for Windows.  This value is used by Distutils
     to compute the installation directories for scripts, data files,
     Python modules, etc.  for the *note user installation scheme: 135e.
     See also *note PYTHONUSERBASE: d19.

 -- 函式: 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: b29. 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 ‘sitecustomize’ or ‘usercustomize’ (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: 135d.
     If it is not initialized yet, this function will also set it,
     respecting *note PYTHONUSERBASE: d19.

     3.2 版新加入.

 -- 函式: site.getusersitepackages ()

     Return the path of the user-specific site-packages directory, *note
     USER_SITE: 134b.  If it is not initialized yet, this function will
     also set it, respecting *note USER_BASE: 135d.  To determine if the
     user-specific site-packages was added to ‘sys.path’ *note
     ENABLE_USER_SITE: 370c. should be used.

     3.2 版新加入.


File: python.info,  Node: Command Line Interface<4>,  Prev: Module contents<3>,  Up: site --- Site-specific configuration hook

5.29.14.3 Command Line Interface
................................

The *note site: ec. module also provides a way to get the user
directories from the command line:

     $ python3 -m site --user-site
     /home/user/.local/lib/python3.3/site-packages

If it is called without arguments, it will print the contents of *note
sys.path: 48d. on the standard output, followed by the value of *note
USER_BASE: 135d. and whether the directory exists, then the same thing
for *note USER_SITE: 134b, and finally the value of *note
ENABLE_USER_SITE: 370c.

 -- 程式選項: --user-base

     Print the path to the user base directory.

 -- 程式選項: --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: 135a.

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

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0370


File: python.info,  Node: Custom Python Interpreters,  Next: 匯入模組,  Prev: Python Runtime Services,  Up: Python 標準函式庫 Standard Library

5.30 Custom Python Interpreters
===============================

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: 1b. module.  (The *note codeop: 1d.
module is lower-level, used to support compiling a possibly-incomplete
chunk of Python code.)

The full list of modules described in this chapter is:

* Menu:

* code: code --- Interpreter base classes. Interpreter base classes
* codeop: codeop --- Compile Python code. Compile Python code


File: python.info,  Node: code --- Interpreter base classes,  Next: codeop --- Compile Python code,  Up: Custom Python Interpreters

5.30.1 ‘code’ — Interpreter base classes
----------------------------------------

`Source 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 the dictionary 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>")

     Closely emulate the behavior of the interactive Python interpreter.
     This class builds on *note InteractiveInterpreter: 371a. and adds
     prompting using the familiar ‘sys.ps1’ and ‘sys.ps2’, and input
     buffering.

 -- 函式: code.interact (banner=None, readfunc=None, local=None,
          exitmsg=None)

     Convenience function to run a read-eval-print loop.  This creates a
     new instance of *note InteractiveConsole: 1806. and sets `readfunc'
     to be used as the *note InteractiveConsole.raw_input(): 371c.
     method, if provided.  If `local' is provided, it is passed to the
     *note InteractiveConsole: 1806. constructor for use as the default
     namespace for the interpreter loop.  The *note interact(): 371b.
     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 版更變: Added `exitmsg' 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: 45d. if the
     command is complete and contains a syntax error, or raises *note
     OverflowError: 965. or *note ValueError: 1fc. if the command
     contains an invalid literal.

* Menu:

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/code.py


File: python.info,  Node: Interactive Interpreter Objects,  Next: Interactive Console Objects,  Up: code --- Interpreter base classes

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(): 371d.; the default for
     `filename' is ‘'<input>'’, and for `symbol' is ‘'single'’.  One of
     several things can happen:

        * The input is incorrect; *note compile_command(): 371d. raised
          an exception (*note SyntaxError: 45d. or *note OverflowError:
          965.).  A syntax traceback will be printed by calling the
          *note showsyntaxerror(): 3721. method.  *note runsource():
          3720. returns ‘False’.

        * The input is incomplete, and more input is required; *note
          compile_command(): 371d. returned ‘None’.  *note runsource():
          3720. returns ‘True’.

        * The input is complete; *note compile_command(): 371d. returned
          a code object.  The code is executed by calling the *note
          runcode(): 3722. (which also handles run-time exceptions,
          except for *note SystemExit: 601.).  *note runsource(): 3720.
          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(): 6ac. is called to display a traceback.  All
     exceptions are caught except *note SystemExit: 601, which is
     allowed to propagate.

     A note about *note KeyboardInterrupt: 198.: 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(): 3723. 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(): 3723.
     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 --- Interpreter base classes

5.30.1.2 Interactive Console Objects
....................................

The *note InteractiveConsole: 1806. class is a subclass of *note
InteractiveInterpreter: 371a, 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 ‘runsource()’ 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: c71. is raised.  The base implementation reads from
     ‘sys.stdin’; a subclass may replace this with a different
     implementation.


File: python.info,  Node: codeop --- Compile Python code,  Prev: code --- Interpreter base classes,  Up: Custom Python Interpreters

5.30.2 ‘codeop’ — Compile Python code
-------------------------------------

`Source code:' Lib/codeop.py(1)

__________________________________________________________________

The *note codeop: 1d. module provides utilities upon which the Python
read-eval-print loop can be emulated, as is done in the *note code: 1b.
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: 1b. 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: 1d. 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: 45d. is raised if there is invalid Python
     syntax, and *note OverflowError: 965. or *note ValueError: 1fc. if
     there is an invalid literal.

     The `symbol' argument determines whether `source' is compiled as a
     statement (‘'single'’, the default), as a sequence of statements
     (‘'exec'’) or as an *note expression: 3628. (‘'eval'’).  Any other
     value will cause *note ValueError: 1fc. 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__(): 1433. methods
     identical in signature to the built-in function *note compile():
     1b5, 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__(): 1433. methods
     identical in signature to *note compile_command(): 372b.; the
     difference is that if the instance compiles program text containing
     a ‘__future__’ statement, the instance ’remembers’ and compiles all
     subsequent program texts with the statement in force.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/codeop.py


File: python.info,  Node: 匯入模組,  Next: Python Language Services,  Prev: Custom Python Interpreters,  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 --- Import modules from Zip archives. Import modules from Zip archives
* pkgutil: pkgutil --- Package extension utility. Package extension utility
* modulefinder: modulefinder --- Find modules used by a script. Find modules used by a script
* runpy: runpy --- Locating and executing Python modules. Locating and executing Python modules
* importlib: importlib --- The implementation of import. The implementation of import
* Using importlib.metadata: Using importlib metadata.


File: python.info,  Node: zipimport --- Import modules from Zip archives,  Next: pkgutil --- Package extension utility,  Up: 匯入模組

5.31.1 ‘zipimport’ — Import modules from Zip archives
-----------------------------------------------------

`Source code:' 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: 144. module explicitly; it is automatically used by
the built-in *note import: c22. mechanism for *note sys.path: 48d. items
that are paths to ZIP archives.

Typically, *note sys.path: 48d. is a list of directory names as strings.
This module also allows an item of *note sys.path: 48d. 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 only files ‘.py’ and
‘.pyc’ are available for import.  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.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).

PEP 302(6) - New Import Hooks

     The PEP to add the import hooks that help this module work.

This module defines an exception:

 -- 例外: zipimport.ZipImportError

     Exception raised by zipimporter objects.  It’s a subclass of *note
     ImportError: 339, so it can be caught as *note ImportError: 339,
     too.

* Menu:

* zipimporter Objects::
* Examples: Examples<28>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/zipimport.py

   (2) https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT

   (3) https://www.python.org/dev/peps/pep-0273

   (4) https://www.python.org/dev/peps/pep-0273

   (5) https://www.python.org/dev/peps/pep-0302

   (6) https://www.python.org/dev/peps/pep-0302


File: python.info,  Node: zipimporter Objects,  Next: Examples<28>,  Up: zipimport --- Import modules from Zip archives

5.31.1.1 zipimporter Objects
............................

*note zipimporter: 3736. 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: 3733. is raised if `archivepath' doesn’t
     point to a valid ZIP archive.

      -- 成員函式: find_module (fullname[, path])

          Search for a module specified by `fullname'.  `fullname' must
          be the fully qualified (dotted) module name.  It returns the
          zipimporter instance itself if the module was found, or *note
          None: 158. if it wasn’t.  The optional `path' argument is
          ignored—it’s there for compatibility with the importer
          protocol.

      -- 成員函式: get_code (fullname)

          Return the code object for the specified module.  Raise *note
          ZipImportError: 3733. if the module couldn’t be found.

      -- 成員函式: get_data (pathname)

          Return the data associated with `pathname'.  Raise *note
          OSError: 1d4. if the file wasn’t found.

          3.3 版更變: *note IOError: 997. used to be raised instead of
          *note OSError: 1d4.

      -- 成員函式: get_filename (fullname)

          Return the value ‘__file__’ would be set to if the specified
          module was imported.  Raise *note ZipImportError: 3733. if the
          module couldn’t be found.

          3.1 版新加入.

      -- 成員函式: get_source (fullname)

          Return the source code for the specified module.  Raise *note
          ZipImportError: 3733. if the module couldn’t be found, return
          *note None: 158. 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: 3733. 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.  It returns the
          imported module, or raises *note ZipImportError: 3733. if it
          wasn’t found.

      -- 屬性: 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: 373d. and *note prefix: 373e. attributes, when
     combined with a slash, equal the original `archivepath' argument
     given to the *note zipimporter: 3736. constructor.


File: python.info,  Node: Examples<28>,  Prev: zipimporter Objects,  Up: zipimport --- Import modules from Zip archives

5.31.1.2 Examples
.................

Here is an example that imports a module from a ZIP archive - note that
the *note zipimport: 144. 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')  # Add .zip file to front of path
     >>> import jwzthreading
     >>> jwzthreading.__file__
     'example.zip/jwzthreading.py'


File: python.info,  Node: pkgutil --- Package extension utility,  Next: modulefinder --- Find modules used by a script,  Prev: zipimport --- Import modules from Zip archives,  Up: 匯入模組

5.31.2 ‘pkgutil’ — Package extension utility
--------------------------------------------

`Source code:' Lib/pkgutil.py(1)

__________________________________________________________________

This module provides utilities for the import system, in particular
package support.

 -- 類別: pkgutil.ModuleInfo (module_finder, name, ispkg)

     A namedtuple that holds a brief summary of a module’s info.

     3.6 版新加入.

 -- 函式: pkgutil.extend_path (path, name)

     Extend the search path for the modules which comprise a package.
     Intended use is to place the following code in a package’s
     ‘__init__.py’:

          from pkgutil import extend_path
          __path__ = extend_path(__path__, __name__)

     This will add to the package’s ‘__path__’ all subdirectories of
     directories on ‘sys.path’ named after the package.  This is useful
     if one wants to distribute different parts of a single logical
     package as multiple directories.

     It also looks for ‘*.pkg’ files beginning where ‘*’ matches the
     `name' argument.  This feature is similar to ‘*.pth’ files (see the
     *note site: ec. module for more information), except that it
     doesn’t special-case lines starting with ‘import’.  A ‘*.pkg’ file
     is trusted at face value: apart from checking for duplicates, all
     entries found in a ‘*.pkg’ file are added to the path, regardless
     of whether they exist on the filesystem.  (This is a feature.)

     If the input path is not a list (as is the case for frozen
     packages) it is returned unchanged.  The input path is not
     modified; an extended copy is returned.  Items are only appended to
     the copy at the end.

     It is assumed that *note sys.path: 48d. is a sequence.  Items of
     *note sys.path: 48d. that are not strings referring to existing
     directories are ignored.  Unicode items on *note sys.path: 48d.
     that cause errors when used as filenames may cause this function to
     raise an exception (in line with *note os.path.isdir(): 1f9.
     behavior).

 -- 類別: pkgutil.ImpImporter (dirname=None)

     PEP 302(2) Finder that wraps Python’s "classic" import algorithm.

     If `dirname' is a string, a PEP 302(3) finder is created that
     searches that directory.  If `dirname' is ‘None’, a PEP 302(4)
     finder is created that searches the current *note sys.path: 48d,
     plus any modules that are frozen or built-in.

     Note that *note ImpImporter: 3744. does not currently support being
     used by placement on *note sys.meta_path: 5eb.

     3.3 版後已棄用: This emulation is no longer needed, as the standard
     import mechanism is now fully PEP 302(5) compliant and available in
     *note importlib: 9b.

 -- 類別: pkgutil.ImpLoader (fullname, file, filename, etc)

     *note Loader: 14c0. that wraps Python’s "classic" import algorithm.

     3.3 版後已棄用: This emulation is no longer needed, as the standard
     import mechanism is now fully PEP 302(6) compliant and available in
     *note importlib: 9b.

 -- 函式: pkgutil.find_loader (fullname)

     Retrieve a module *note loader: 14c0. for the given `fullname'.

     This is a backwards compatibility wrapper around *note
     importlib.util.find_spec(): 93d. that converts most failures to
     *note ImportError: 339. and only returns the loader rather than the
     full ‘ModuleSpec’.

     3.3 版更變: Updated to be based directly on *note importlib: 9b.
     rather than relying on the package internal PEP 302(7) import
     emulation.

     3.4 版更變: Updated to be based on PEP 451(8)

 -- 函式: pkgutil.get_importer (path_item)

     Retrieve a *note finder: 14bf. for the given `path_item'.

     The returned finder is cached in *note sys.path_importer_cache:
     4a2. if it was newly created by a path hook.

     The cache (or part of it) can be cleared manually if a rescan of
     *note sys.path_hooks: 961. is necessary.

     3.3 版更變: Updated to be based directly on *note importlib: 9b.
     rather than relying on the package internal PEP 302(9) import
     emulation.

 -- 函式: pkgutil.get_loader (module_or_name)

     Get a *note loader: 14c0. object for `module_or_name'.

     If the module or package is accessible via the normal import
     mechanism, a wrapper around the relevant part of that machinery is
     returned.  Returns ‘None’ if the module cannot be found or
     imported.  If the named module is not already imported, its
     containing package (if any) is imported, in order to establish the
     package ‘__path__’.

     3.3 版更變: Updated to be based directly on *note importlib: 9b.
     rather than relying on the package internal PEP 302(10) import
     emulation.

     3.4 版更變: Updated to be based on PEP 451(11)

 -- 函式: pkgutil.iter_importers (fullname='')

     Yield *note finder: 14bf. objects for the given module name.

     If fullname contains a ’.’, the finders will be for the package
     containing fullname, otherwise they will be all registered top
     level finders (i.e.  those on both sys.meta_path and
     sys.path_hooks).

     If the named module is in a package, that package is imported as a
     side effect of invoking this function.

     If no module name is specified, all top level finders are produced.

     3.3 版更變: Updated to be based directly on *note importlib: 9b.
     rather than relying on the package internal PEP 302(12) import
     emulation.

 -- 函式: pkgutil.iter_modules (path=None, prefix='')

     Yields *note ModuleInfo: 612. for all submodules on `path', or, if
     `path' is ‘None’, all top-level modules on ‘sys.path’.

     `path' should be either ‘None’ or a list of paths to look for
     modules in.

     `prefix' is a string to output on the front of every module name on
     output.

          備註: Only works for a *note finder: 14bf. which defines an
          ‘iter_modules()’ method.  This interface is non-standard, so
          the module also provides implementations for *note
          importlib.machinery.FileFinder: 9bb. and *note
          zipimport.zipimporter: 3736.

     3.3 版更變: Updated to be based directly on *note importlib: 9b.
     rather than relying on the package internal PEP 302(13) import
     emulation.

 -- 函式: pkgutil.walk_packages (path=None, prefix='', onerror=None)

     Yields *note ModuleInfo: 612. for all modules recursively on
     `path', or, if `path' is ‘None’, all accessible modules.

     `path' should be either ‘None’ or a list of paths to look for
     modules in.

     `prefix' is a string to output on the front of every module name on
     output.

     Note that this function must import all `packages' (`not' all
     modules!)  on the given `path', in order to access the ‘__path__’
     attribute to find submodules.

     `onerror' is a function which gets called with one argument (the
     name of the package which was being imported) if any exception
     occurs while trying to import a package.  If no `onerror' function
     is supplied, *note ImportError: 339.s are caught and ignored, while
     all other exceptions are propagated, terminating the search.

     Examples:

          # list all modules python can access
          walk_packages()

          # list all submodules of ctypes
          walk_packages(ctypes.__path__, ctypes.__name__ + '.')

          備註: Only works for a *note finder: 14bf. which defines an
          ‘iter_modules()’ method.  This interface is non-standard, so
          the module also provides implementations for *note
          importlib.machinery.FileFinder: 9bb. and *note
          zipimport.zipimporter: 3736.

     3.3 版更變: Updated to be based directly on *note importlib: 9b.
     rather than relying on the package internal PEP 302(14) import
     emulation.

 -- 函式: pkgutil.get_data (package, resource)

     Get a resource from a package.

     This is a wrapper for the *note loader: 14c0. *note get_data: 374a.
     API. The `package' argument should be the name of a package, in
     standard module format (‘foo.bar’).  The `resource' argument should
     be in the form of a relative filename, using ‘/’ as the path
     separator.  The parent directory name ‘..’ is not allowed, and nor
     is a rooted name (starting with a ‘/’).

     The function returns a binary string that is the contents of the
     specified resource.

     For packages located in the filesystem, which have already been
     imported, this is the rough equivalent of:

          d = os.path.dirname(sys.modules[package].__file__)
          data = open(os.path.join(d, resource), 'rb').read()

     If the package cannot be located or loaded, or it uses a *note
     loader: 14c0. which does not support *note get_data: 374a, then
     ‘None’ is returned.  In particular, the *note loader: 14c0. for
     *note namespace packages: 14b8. does not support *note get_data:
     374a.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/pkgutil.py

   (2) https://www.python.org/dev/peps/pep-0302

   (3) https://www.python.org/dev/peps/pep-0302

   (4) https://www.python.org/dev/peps/pep-0302

   (5) https://www.python.org/dev/peps/pep-0302

   (6) https://www.python.org/dev/peps/pep-0302

   (7) https://www.python.org/dev/peps/pep-0302

   (8) https://www.python.org/dev/peps/pep-0451

   (9) https://www.python.org/dev/peps/pep-0302

   (10) https://www.python.org/dev/peps/pep-0302

   (11) https://www.python.org/dev/peps/pep-0451

   (12) https://www.python.org/dev/peps/pep-0302

   (13) https://www.python.org/dev/peps/pep-0302

   (14) https://www.python.org/dev/peps/pep-0302


File: python.info,  Node: modulefinder --- Find modules used by a script,  Next: runpy --- Locating and executing Python modules,  Prev: pkgutil --- Package extension utility,  Up: 匯入模組

5.31.3 ‘modulefinder’ — Find modules used by a script
-----------------------------------------------------

`Source code:' Lib/modulefinder.py(1)

__________________________________________________________________

This module provides a *note ModuleFinder: fe5. class that can be used
to determine the set of modules imported by a script.  ‘modulefinder.py’
can also be run as a script, giving the filename of a Python script as
its argument, after which a report of the imported modules will be
printed.

 -- 函式: modulefinder.AddPackagePath (pkg_name, path)

     Record that the package named `pkg_name' can be found in the
     specified `path'.

 -- 函式: modulefinder.ReplacePackage (oldname, newname)

     Allows specifying that the module named `oldname' is in fact the
     package named `newname'.

 -- 類別: modulefinder.ModuleFinder (path=None, debug=0, excludes=[],
          replace_paths=[])

     This class provides *note run_script(): 374f. and *note report():
     3750. methods to determine the set of modules imported by a script.
     `path' can be a list of directories to search for modules; if not
     specified, ‘sys.path’ is used.  `debug' sets the debugging level;
     higher values make the class print debugging messages about what
     it’s doing.  `excludes' is a list of module names to exclude from
     the analysis.  `replace_paths' is a list of ‘(oldpath, newpath)’
     tuples that will be replaced in module paths.

      -- 成員函式: report ()

          Print a report to standard output that lists the modules
          imported by the script and their paths, as well as modules
          that are missing or seem to be missing.

      -- 成員函式: run_script (pathname)

          Analyze the contents of the `pathname' file, which must
          contain Python code.

      -- 屬性: modules

          A dictionary mapping module names to modules.  See *note
          Example usage of ModuleFinder: 3752.

* Menu:

* Example usage of ModuleFinder::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/modulefinder.py


File: python.info,  Node: Example usage of ModuleFinder,  Up: modulefinder --- Find modules used by a script

5.31.3.1 Example usage of ‘ModuleFinder’
........................................

The script that is going to get analyzed later on (bacon.py):

     import re, itertools

     try:
         import baconhameggs
     except ImportError:
         pass

     try:
         import guido.python.ham
     except ImportError:
         pass

The script that will output the report of 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()))

Sample output (may vary depending on the architecture):

     Loaded modules:
     _types:
     copyreg:  _inverted_registry,_slotnames,__all__
     sre_compile:  isstring,_sre,_optimize_unicode
     _sre:
     sre_constants:  REPEAT_ONE,makedict,AT_END_LINE
     sys:
     re:  __module__,finditer,_expand
     itertools:
     __main__:  re,itertools,baconhameggs
     sre_parse:  _PATTERNENDERS,SRE_FLAG_UNICODE
     array:
     types:  __module__,IntType,TypeType
     ---------------------------------------------------
     Modules not imported:
     guido.python.ham
     baconhameggs


File: python.info,  Node: runpy --- Locating and executing Python modules,  Next: importlib --- The implementation of import,  Prev: modulefinder --- Find modules used by a script,  Up: 匯入模組

5.31.4 ‘runpy’ — Locating and executing Python modules
------------------------------------------------------

`Source code:' Lib/runpy.py(1)

__________________________________________________________________

The *note runpy: e3. module is used to locate and run Python modules
without importing them first.  Its main use is to implement the *note
-m: 33c. 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: e3. function has
returned.  If that limitation is not acceptable for a given use case,
*note importlib: 9b. is likely to be a more suitable choice than this
module.

The *note runpy: e3. 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 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 ‘__main__’ 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.  The supplied dictionary will not be modified.  If any of
     the special global variables below are defined in the supplied
     dictionary, those definitions are overridden by *note run_module():
     1340.

     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: 158, 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: 14c7. based on the module spec.

     If the argument `alter_sys' is supplied and evaluates to *note
     True: 49e, 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: fe. 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 *note
     sys: fe. module be left alone when invoking this function from
     threaded code.

     也參考
     ......

     The *note -m: 33c. option offering equivalent functionality from
     the command line.

     3.1 版更變: Added ability to execute packages by looking for a
     ‘__main__’ 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’.

 -- 函式: runpy.run_path (file_path, init_globals=None, run_name=None)

     Execute the code at the named filesystem location and return the
     resulting module globals dictionary.  As with a script name
     supplied to the CPython command line, the supplied path may refer
     to a Python source file, a compiled bytecode file or a valid
     sys.path entry containing a ‘__main__’ 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 sys.path 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 *note __main__: 1.
     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.  The supplied dictionary will not be modified.  If any of
     the special global variables below are defined in the supplied
     dictionary, those definitions are overridden by *note run_path():
     cb6.

     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: 158. and to ‘'<run_path>'’ otherwise.

     If the supplied path directly references a script file (whether as
     source or as precompiled byte code), then ‘__file__’ will be set to
     the supplied path, and ‘__spec__’, ‘__cached__’, ‘__loader__’ and
     ‘__package__’ will all be set to *note None: 158.

     If the supplied path is a reference to a valid sys.path entry, then
     ‘__spec__’ will be set appropriately for the imported ‘__main__’
     module (that is, ‘__spec__.name’ will always be ‘__main__’).
     ‘__file__’, ‘__cached__’, ‘__loader__’ and ‘__package__’ will be
     *note set as normal: 14c7. based on the module spec.

     A number of alterations are also made to the *note sys: fe. module.
     Firstly, ‘sys.path’ 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: fe. are reverted before the function returns.

     Note that, unlike *note run_module(): 1340, the alterations made to
     *note sys: fe. are not optional in this function as these
     adjustments are essential to allowing the execution of sys.path
     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 Interface options: 133f. 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 sys.path
     entry rather than being executed directly.

也參考
......

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 Command line and environment: faf. - CPython command line details

The *note importlib.import_module(): b18. function

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/runpy.py

   (2) https://www.python.org/dev/peps/pep-0302

   (3) https://www.python.org/dev/peps/pep-3147

   (4) https://www.python.org/dev/peps/pep-0451

   (5) https://www.python.org/dev/peps/pep-0451

   (6) https://www.python.org/dev/peps/pep-0338

   (7) https://www.python.org/dev/peps/pep-0366

   (8) https://www.python.org/dev/peps/pep-0451


File: python.info,  Node: importlib --- The implementation of import,  Next: Using importlib metadata,  Prev: runpy --- Locating and executing Python modules,  Up: 匯入模組

5.31.5 ‘importlib’ — The implementation of ‘import’
---------------------------------------------------

3.1 版新加入.

`Source code:' Lib/importlib/__init__.py(1)

__________________________________________________________________

* Menu:

* 簡介: 簡介<11>.
* Functions: Functions<10>.
* importlib.abc: importlib abc -- Abstract base classes related to import. Abstract base classes related to import
* importlib.resources: importlib resources -- Resources. Resources
* importlib.machinery: importlib machinery -- Importers and path hooks. Importers and path hooks
* importlib.util: importlib util -- Utility code for importers. Utility code for importers
* Examples: Examples<29>.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/importlib/__init__.py


File: python.info,  Node: 簡介<11>,  Next: Functions<10>,  Up: importlib --- The implementation of import

5.31.5.1 簡介
.............

The purpose of the *note importlib: 9b. package is two-fold.  One is to
provide the implementation of the *note import: c22. statement (and
thus, by extension, the *note __import__(): 615. 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: c22. are exposed in this
package, making it easier for users to create their own custom objects
(known generically as an *note importer: 14c1.) to participate in the
import process.

也參考
......

*note The import statement: c22.

     The language reference for the *note import: c22. 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: f2b.).

The *note __import__(): 9b3. function

     The *note import: c22. statement is syntactic sugar for this
     function.

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://www.python.org/dev/peps/pep-0235

   (3) https://www.python.org/dev/peps/pep-0263

   (4) https://www.python.org/dev/peps/pep-0302

   (5) https://www.python.org/dev/peps/pep-0328

   (6) https://www.python.org/dev/peps/pep-0366

   (7) https://www.python.org/dev/peps/pep-0420

   (8) https://www.python.org/dev/peps/pep-0451

   (9) https://www.python.org/dev/peps/pep-0488

   (10) https://www.python.org/dev/peps/pep-0489

   (11) https://www.python.org/dev/peps/pep-0552

   (12) https://www.python.org/dev/peps/pep-3120

   (13) https://www.python.org/dev/peps/pep-3147


File: python.info,  Node: Functions<10>,  Next: importlib abc -- Abstract base classes related to import,  Prev: 簡介<11>,  Up: importlib --- The implementation of import

5.31.5.2 Functions
..................

 -- 函式: importlib.__import__ (name, globals=None, locals=None,
          fromlist=(), level=0)

     An implementation of the built-in *note __import__(): 615.
     function.

          備註: Programmatic importing of modules should use *note
          import_module(): b18. 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(): b18. function acts as a simplifying
     wrapper around *note importlib.__import__(): 9b3.  This means all
     semantics of the function are derived from *note
     importlib.__import__(): 9b3.  The most important difference between
     these two functions is that *note import_module(): b18. returns the
     specified package or module (e.g.  ‘pkg.mod’), while *note
     __import__(): 615. 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(): 4a1. in
     order for the new module to be noticed by the import system.

     3.3 版更變: Parent packages are automatically imported.

 -- 函式: importlib.find_loader (name, path=None)

     Find the loader for a module, optionally within the specified
     `path'.  If the module is in *note sys.modules: f2b, then
     ‘sys.modules[name].__loader__’ is returned (unless the loader would
     be ‘None’ or is not set, in which case *note ValueError: 1fc. is
     raised).  Otherwise a search using *note sys.meta_path: 5eb. is
     done.  ‘None’ is returned if no loader is found.

     A dotted name does not have its parents implicitly imported as that
     requires loading them and that may not be desired.  To properly
     import a submodule you will need to import all parent packages of
     the submodule and use the correct argument to `path'.

     3.3 版新加入.

     3.4 版更變: If ‘__loader__’ is not set, raise *note ValueError:
     1fc, just like when the attribute is set to ‘None’.

     3.4 版後已棄用: Use *note importlib.util.find_spec(): 93d. instead.

 -- 函式: importlib.invalidate_caches ()

     Invalidate the internal caches of finders stored at *note
     sys.meta_path: 5eb.  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 版新加入.

 -- 函式: 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: f2b.).

     When *note reload(): 39e. 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:
          14c0. 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: d77. 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: fe, *note __main__: 1, *note
     builtins: 13. 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:
     c4a. ...  *note import: c22. ..., calling *note reload(): 39e. 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: 39f. is raised when the
     module being reloaded lacks a ‘ModuleSpec’.


File: python.info,  Node: importlib abc -- Abstract base classes related to import,  Next: importlib resources -- Resources,  Prev: Functions<10>,  Up: importlib --- The implementation of import

5.31.5.3 ‘importlib.abc’ – Abstract base classes related to import
..................................................................

`Source code:' Lib/importlib/abc.py(1)

__________________________________________________________________

The *note importlib.abc: 9c. module contains all of the core abstract
base classes used by *note import: c22.  Some subclasses of the core
abstract base classes are also provided to help in implementing the core
ABCs.

ABC hierarchy:

     object
      +-- Finder (deprecated)
      |    +-- MetaPathFinder
      |    +-- PathEntryFinder
      +-- Loader
           +-- ResourceLoader --------+
           +-- InspectLoader          |
                +-- ExecutionLoader --+
                                      +-- FileLoader
                                      +-- SourceLoader

 -- 類別: importlib.abc.Finder

     An abstract base class representing a *note finder: 14bf.

     3.3 版後已棄用: Use *note MetaPathFinder: 9b8. or *note
     PathEntryFinder: 9b9. instead.

      -- 成員函式: abstractmethod find_module (fullname, path=None)

          An abstract method for finding a *note loader: 14c0. for the
          specified module.  Originally specified in PEP 302(2), this
          method was meant for use in *note sys.meta_path: 5eb. and in
          the path-based import subsystem.

          3.4 版更變: Returns ‘None’ when called instead of raising
          *note NotImplementedError: 613.

 -- 類別: importlib.abc.MetaPathFinder

     An abstract base class representing a *note meta path finder: 9b6.
     For compatibility, this is a subclass of *note Finder: 9ba.

     3.3 版新加入.

      -- 成員函式: find_spec (fullname, path, target=None)

          An abstract method for finding a *note spec: 3638. 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__: 1294.
          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():
          375c. may be useful for implementing concrete
          ‘MetaPathFinders’.

          3.4 版新加入.

      -- 成員函式: find_module (fullname, path)

          A legacy method for finding a *note loader: 14c0. 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__: 1294.
          from the parent package.  If a loader cannot be found, ‘None’
          is returned.

          If *note find_spec(): 468. is defined, backwards-compatible
          functionality is provided.

          3.4 版更變: Returns ‘None’ when called instead of raising
          *note NotImplementedError: 613.  Can use *note find_spec():
          468. to provide functionality.

          3.4 版後已棄用: Use *note find_spec(): 468. instead.

      -- 成員函式: invalidate_caches ()

          An optional method which, when called, should invalidate any
          internal cache used by the finder.  Used by *note
          importlib.invalidate_caches(): 4a1. when invalidating the
          caches of all finders on *note sys.meta_path: 5eb.

          3.4 版更變: Returns ‘None’ when called instead of
          ‘NotImplemented’.

 -- 類別: importlib.abc.PathEntryFinder

     An abstract base class representing a *note path entry finder: 9b7.
     Though it bears some similarities to *note MetaPathFinder: 9b8,
     ‘PathEntryFinder’ is meant for use only within the path-based
     import subsystem provided by ‘PathFinder’.  This ABC is a subclass
     of *note Finder: 9ba. for compatibility reasons only.

     3.3 版新加入.

      -- 成員函式: find_spec (fullname, target=None)

          An abstract method for finding a *note spec: 3638. for the
          specified module.  The finder will search for the module only
          within the *note path entry: 14d4. 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(): 375c. may be useful for
          implementing concrete ‘PathEntryFinders’.

          3.4 版新加入.

      -- 成員函式: find_loader (fullname)

          A legacy method for finding a *note loader: 14c0. for the
          specified module.  Returns a 2-tuple of ‘(loader, portion)’
          where ‘portion’ is a sequence of file system locations
          contributing to part of a namespace package.  The loader may
          be ‘None’ while specifying ‘portion’ to signify the
          contribution of the file system locations to a namespace
          package.  An empty list can be used for ‘portion’ to signify
          the loader is not part of a namespace package.  If ‘loader’ is
          ‘None’ and ‘portion’ is the empty list then no loader or
          location for a namespace package were found (i.e.  failure to
          find anything for the module).

          If *note find_spec(): 46a. is defined then
          backwards-compatible functionality is provided.

          3.4 版更變: Returns ‘(None, [])’ instead of raising *note
          NotImplementedError: 613.  Uses *note find_spec(): 46a. when
          available to provide functionality.

          3.4 版後已棄用: Use *note find_spec(): 46a. instead.

      -- 成員函式: find_module (fullname)

          A concrete implementation of *note Finder.find_module(): 375b.
          which is equivalent to ‘self.find_loader(fullname)[0]’.

          3.4 版後已棄用: Use *note find_spec(): 46a. instead.

      -- 成員函式: invalidate_caches ()

          An optional method which, when called, should invalidate any
          internal cache used by the finder.  Used by
          ‘PathFinder.invalidate_caches()’ when invalidating the caches
          of all cached finders.

 -- 類別: importlib.abc.Loader

     An abstract base class for a *note loader: 14c0.  See PEP 302(3)
     for the exact definition for a loader.

     Loaders that wish to support resource reading should implement a
     ‘get_resource_reader(fullname)’ method as specified by *note
     importlib.abc.ResourceReader: 347.

     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.5 版更變: Starting in Python 3.6, this method will not be
          optional when *note exec_module(): 5e9. 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 ‘exec_module()’ is called.
          When this method exists, *note create_module(): 559. must be
          defined.

          3.4 版新加入.

          3.6 版更變: *note create_module(): 559. must also be defined.

      -- 成員函式: load_module (fullname)

          A legacy method for loading a module.  If the module cannot be
          loaded, *note ImportError: 339. is raised, otherwise the
          loaded module is returned.

          If the requested module already exists in *note sys.modules:
          f2b, that module should be used and reloaded.  Otherwise the
          loader should create a new module and insert it into *note
          sys.modules: f2b. 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: f2b.; modules already in *note sys.modules:
          f2b. before the loader began execution should be left alone
          (see *note importlib.util.module_for_loader(): 947.).

          The loader should set several attributes on the module.  (Note
          that some of these attributes can change when a module is
          reloaded):

             - 
               *note __name__: d17.

                    The name of the module.

             - 
               *note __file__: ebc.

                    The path to where the module data is stored (not set
                    for built-in modules).

             - 
               *note __cached__: b37.

                    The path to where a compiled version of the module
                    is/should be stored (not set when the attribute
                    would be inappropriate).

             - 
               *note __path__: 1294.

                    A list of strings specifying the search path within
                    a package.  This attribute is not set on modules.

             - 
               *note __package__: 95a.

                    The fully-qualified name of the package under which
                    the module was loaded as a submodule (or the empty
                    string for top-level modules).  For packages, it is
                    the same as *note __name__: d17.  The *note
                    importlib.util.module_for_loader(): 947. decorator
                    can handle the details for *note __package__: 95a.

             - 
               *note __loader__: 95b.

                    The loader used to load the module.  The *note
                    importlib.util.module_for_loader(): 947. decorator
                    can handle the details for *note __package__: 95a.

          When *note exec_module(): 5e9. is available then
          backwards-compatible functionality is provided.

          3.4 版更變: Raise *note ImportError: 339. when called instead
          of *note NotImplementedError: 613.  Functionality provided
          when *note exec_module(): 5e9. is available.

          3.4 版後已棄用: The recommended API for loading a module is
          *note exec_module(): 5e9. (and *note create_module(): 559.).
          Loaders should implement it instead of load_module().  The
          import machinery takes care of all the other responsibilities
          of load_module() when exec_module() is implemented.

      -- 成員函式: module_repr (module)

          A legacy method which when implemented calculates and returns
          the given module’s repr, as a string.  The module type’s
          default repr() will use the result of this method as
          appropriate.

          3.3 版新加入.

          3.4 版更變: Made optional instead of an abstractmethod.

          3.4 版後已棄用: The import machinery now takes care of this
          automatically.

 -- 類別: importlib.abc.ResourceReader

     An *note abstract base class: b38. 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 in a e.g.  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: 36f. 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: 158.  An object compatible with this ABC should only be
     returned when the specified module is a package.

     3.7 版新加入.

      -- 成員函式: abstractmethod open_resource (resource)

          Returns an opened, *note file-like object: 1c6f. for binary
          reading of the `resource'.

          If the resource cannot be found, *note FileNotFoundError: 7c5.
          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: 7c5.

      -- 成員函式: abstractmethod is_resource (name)

          Returns ‘True’ if the named `name' is considered a resource.
          *note FileNotFoundError: 7c5. is raised if `name' does not
          exist.

      -- 成員函式: abstractmethod contents ()

          Returns an *note iterable: bb1. 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():
          3761. 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.ResourceLoader

     An abstract base class for a *note loader: 14c0. which implements
     the optional PEP 302(4) 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.abc.ResourceReader: 347.

      -- 成員函式: 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: 1d4. is to be raised if the `path' cannot be found.
          The `path' is expected to be constructed using a module’s
          *note __file__: ebc. attribute or an item from a package’s
          *note __path__: 1294.

          3.4 版更變: Raises *note OSError: 1d4. instead of *note
          NotImplementedError: 613.

 -- 類別: importlib.abc.InspectLoader

     An abstract base class for a *note loader: 14c0. which implements
     the optional PEP 302(5) 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:
          339. 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: 5f9,
          translating all recognized line separators into ‘'\n'’
          characters.  Returns ‘None’ if no source is available (e.g.  a
          built-in module).  Raises *note ImportError: 339. if the
          loader cannot find the module specified.

          3.4 版更變: Raises *note ImportError: 339. instead of *note
          NotImplementedError: 613.

      -- 成員函式: is_package (fullname)

          An abstract method to return a true value if the module is a
          package, a false value otherwise.  *note ImportError: 339. is
          raised if the *note loader: 14c0. cannot find the module.

          3.4 版更變: Raises *note ImportError: 339. instead of *note
          NotImplementedError: 613.

      -- 成員函式: static source_to_code (data, path='<string>')

          Create a code object from Python source.

          The `data' argument can be whatever the *note compile(): 1b5.
          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)

          Implementation of *note Loader.exec_module(): 5e9.

          3.4 版新加入.

      -- 成員函式: load_module (fullname)

          Implementation of *note Loader.load_module(): 5e8.

          3.4 版後已棄用: use *note exec_module(): 944. instead.

 -- 類別: importlib.abc.ExecutionLoader

     An abstract base class which inherits from *note InspectLoader:
     865. that, when implemented, helps a module to be executed as a
     script.  The ABC represents an optional PEP 302(6) protocol.

      -- 成員函式: abstractmethod get_filename (fullname)

          An abstract method that is to return the value of *note
          __file__: ebc. for the specified module.  If no path is
          available, *note ImportError: 339. 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: 339. instead of *note
          NotImplementedError: 613.

 -- 類別: importlib.abc.FileLoader (fullname, path)

     An abstract base class which inherits from *note ResourceLoader:
     46b. and *note ExecutionLoader: 3763, providing concrete
     implementations of *note ResourceLoader.get_data(): 374a. and *note
     ExecutionLoader.get_filename(): 3764.

     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(): 5e9. instead.

      -- 成員函式: abstractmethod get_filename (fullname)

          Returns *note path: 3766.

      -- 成員函式: 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: 46b. and *note ExecutionLoader: 3763, requiring the
     implementation of:

        * *note ResourceLoader.get_data(): 374a.

        * 
          *note ExecutionLoader.get_filename(): 3764.

               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: 613.) 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: 1b9.
          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: 1d4. is raised.

          3.3 版新加入.

          3.4 版更變: Raise *note OSError: 1d4. instead of *note
          NotImplementedError: 613.

      -- 成員函式: 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(): af1.  You don’t have to implement it, but it is
          still available for compatibility purposes.  Raise *note
          OSError: 1d4. if the path cannot be handled.

          3.4 版更變: Raise *note OSError: 1d4. instead of *note
          NotImplementedError: 613.

      -- 成員函式: 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: 224a./*note PermissionError: 604.), do
          not propagate the exception.

          3.4 版更變: No longer raises *note NotImplementedError: 613.
          when called.

      -- 成員函式: get_code (fullname)

          Concrete implementation of *note InspectLoader.get_code():
          866.

      -- 成員函式: exec_module (module)

          Concrete implementation of *note Loader.exec_module(): 5e9.

          3.4 版新加入.

      -- 成員函式: load_module (fullname)

          Concrete implementation of *note Loader.load_module(): 5e8.

          3.4 版後已棄用: Use *note exec_module(): 945. instead.

      -- 成員函式: get_source (fullname)

          Concrete implementation of *note InspectLoader.get_source():
          86a.

      -- 成員函式: is_package (fullname)

          Concrete implementation of *note InspectLoader.is_package():
          3762.  A module is determined to be a package if its file path
          (as provided by *note ExecutionLoader.get_filename(): 3764.)
          is a file named ‘__init__’ when the file extension is removed
          `and' the module name itself does not end in ‘__init__’.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/importlib/abc.py

   (2) https://www.python.org/dev/peps/pep-0302

   (3) https://www.python.org/dev/peps/pep-0302

   (4) https://www.python.org/dev/peps/pep-0302

   (5) https://www.python.org/dev/peps/pep-0302

   (6) https://www.python.org/dev/peps/pep-0302


File: python.info,  Node: importlib resources -- Resources,  Next: importlib machinery -- Importers and path hooks,  Prev: importlib abc -- Abstract base classes related to import,  Up: importlib --- The implementation of import

5.31.5.4 ‘importlib.resources’ – Resources
..........................................

`Source code:' Lib/importlib/resources.py(1)

__________________________________________________________________

3.7 版新加入.

This module leverages Python’s import system to provide access to
`resources' within `packages'.  If you can import a package, you can
access resources within that package.  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.

     備註: 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).

Loaders that wish to support resource reading should implement a
‘get_resource_reader(fullname)’ method as specified by *note
importlib.abc.ResourceReader: 347.

The following types are defined.

 -- Data: importlib.resources.Package

     The ‘Package’ type is defined as ‘Union[str, ModuleType]’.  This
     means that where the function describes accepting a ‘Package’, you
     can pass in either a string or a module.  Module objects must have
     a resolvable ‘__spec__.submodule_search_locations’ that is not
     ‘None’.

 -- Data: importlib.resources.Resource

     This type describes the resource names passed into the various
     functions in this package.  This is defined as ‘Union[str,
     os.PathLike]’.

The following functions are available.

 -- 函式: importlib.resources.open_binary (package, resource)

     Open for binary reading the `resource' within `package'.

     `package' is either a name or a module object which conforms to the
     ‘Package’ requirements.  `resource' is the name of the resource to
     open within `package'; it may not contain path separators and it
     may not have sub-resources (i.e.  it cannot be a directory).  This
     function returns a ‘typing.BinaryIO’ instance, a binary I/O stream
     open for reading.

 -- 函式: importlib.resources.open_text (package, resource,
          encoding='utf-8', errors='strict')

     Open for text reading the `resource' within `package'.  By default,
     the resource is opened for reading as UTF-8.

     `package' is either a name or a module object which conforms to the
     ‘Package’ requirements.  `resource' is the name of the resource to
     open within `package'; it may not contain path separators and it
     may not have sub-resources (i.e.  it cannot be a directory).
     `encoding' and `errors' have the same meaning as with built-in
     *note open(): 4f5.

     This function returns a ‘typing.TextIO’ instance, a text I/O stream
     open for reading.

 -- 函式: importlib.resources.read_binary (package, resource)

     Read and return the contents of the `resource' within `package' as
     ‘bytes’.

     `package' is either a name or a module object which conforms to the
     ‘Package’ requirements.  `resource' is the name of the resource to
     open within `package'; it may not contain path separators and it
     may not have sub-resources (i.e.  it cannot be a directory).  This
     function returns the contents of the resource as *note bytes: 336.

 -- 函式: importlib.resources.read_text (package, resource,
          encoding='utf-8', errors='strict')

     Read and return the contents of `resource' within `package' as a
     ‘str’.  By default, the contents are read as strict UTF-8.

     `package' is either a name or a module object which conforms to the
     ‘Package’ requirements.  `resource' is the name of the resource to
     open within `package'; it may not contain path separators and it
     may not have sub-resources (i.e.  it cannot be a directory).
     `encoding' and `errors' have the same meaning as with built-in
     *note open(): 4f5.  This function returns the contents of the
     resource as *note str: 335.

 -- 函式: importlib.resources.path (package, resource)

     Return the path to the `resource' as an actual file system path.
     This function returns a context manager for use in a *note with:
     6ee. statement.  The context manager provides a *note pathlib.Path:
     202. object.

     Exiting the context manager cleans up any temporary file created
     when the resource needs to be extracted from e.g.  a zip file.

     `package' is either a name or a module object which conforms to the
     ‘Package’ requirements.  `resource' is the name of the resource to
     open within `package'; it may not contain path separators and it
     may not have sub-resources (i.e.  it cannot be a directory).

 -- 函式: importlib.resources.is_resource (package, name)

     Return ‘True’ if there is a resource named `name' in the package,
     otherwise ‘False’.  Remember that directories are `not' resources!
     `package' is either a name or a module object which conforms to the
     ‘Package’ requirements.

 -- 函式: importlib.resources.contents (package)

     Return an iterable over the named items within the package.  The
     iterable returns *note str: 335. resources (e.g.  files) and
     non-resources (e.g.  directories).  The iterable does not recurse
     into subdirectories.

     `package' is either a name or a module object which conforms to the
     ‘Package’ requirements.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/importlib/resources.py

   (2) https://setuptools.readthedocs.io/en/latest/pkg_resources.html

   (3) 
http://setuptools.readthedocs.io/en/latest/pkg_resources.html#basic-resource-access

   (4) http://importlib-resources.readthedocs.io/en/latest/using.html

   (5) 
http://importlib-resources.readthedocs.io/en/latest/migration.html


File: python.info,  Node: importlib machinery -- Importers and path hooks,  Next: importlib util -- Utility code for importers,  Prev: importlib resources -- Resources,  Up: importlib --- The implementation of import

5.31.5.5 ‘importlib.machinery’ – Importers and path hooks
.........................................................

`Source code:' Lib/importlib/machinery.py(1)

__________________________________________________________________

This module contains the various objects that help *note import: c22.
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: 3778. 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: 3778. 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(): 5f7.).

     3.3 版新加入.

 -- 類別: importlib.machinery.BuiltinImporter

     An *note importer: 14c1. for built-in modules.  All known built-in
     modules are listed in *note sys.builtin_module_names: 3622.  This
     class implements the *note importlib.abc.MetaPathFinder: 9b8. and
     *note importlib.abc.InspectLoader: 865. 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: 14c1. for frozen modules.  This class implements
     the *note importlib.abc.MetaPathFinder: 9b8. and *note
     importlib.abc.InspectLoader: 865. 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: 14bf. for modules declared in the Windows registry.
     This class implements the *note importlib.abc.MetaPathFinder: 9b8.
     ABC.

     Only class methods are defined by this class to alleviate the need
     for instantiation.

     3.3 版新加入.

     3.6 版後已棄用: Use *note site: ec. configuration instead.  Future
     versions of Python may not enable this finder by default.

 -- 類別: importlib.machinery.PathFinder

     A *note Finder: 14bf. for *note sys.path: 48d. and package
     ‘__path__’ attributes.  This class implements the *note
     importlib.abc.MetaPathFinder: 9b8. 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: 3638. for the
          module specified by `fullname' on *note sys.path: 48d. or, if
          defined, on `path'.  For each path entry that is searched,
          *note sys.path_importer_cache: 4a2. is checked.  If a
          non-false object is found then it is used as the *note path
          entry finder: 9b7. to look for the module being searched for.
          If no entry is found in *note sys.path_importer_cache: 4a2,
          then *note sys.path_hooks: 961. is searched for a finder for
          the path entry and, if found, is stored in *note
          sys.path_importer_cache: 4a2. 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: 4a2.

      -- 成員函式: classmethod find_module (fullname, path=None)

          A legacy wrapper around *note find_spec(): 93f.

          3.4 版後已棄用: Use *note find_spec(): 93f. instead.

      -- 成員函式: classmethod invalidate_caches ()

          Calls *note importlib.abc.PathEntryFinder.invalidate_caches():
          375e. on all finders stored in *note sys.path_importer_cache:
          4a2. that define the method.  Otherwise entries in *note
          sys.path_importer_cache: 4a2. set to ‘None’ are deleted.

          3.7 版更變: Entries of ‘None’ in *note
          sys.path_importer_cache: 4a2. are deleted.

     3.4 版更變: Calls objects in *note sys.path_hooks: 961. 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:
     9b9. 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(): 4a1.

     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: 377b.

          3.4 版新加入.

      -- 成員函式: find_loader (fullname)

          Attempt to find the loader to handle `fullname' within *note
          path: 377b.

      -- 成員函式: 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: 961.  An instance of *note FileFinder: 9bb. 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: 339. is raised.

 -- 類別: importlib.machinery.SourceFileLoader (fullname, path)

     A concrete implementation of *note importlib.abc.SourceLoader:
     3769. by subclassing *note importlib.abc.FileLoader: 9bc. 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: 3780. appears to be for a
          package.

      -- 成員函式: path_stats (path)

          Concrete implementation of *note
          importlib.abc.SourceLoader.path_stats(): af1.

      -- 成員函式: set_data (path, data)

          Concrete implementation of *note
          importlib.abc.SourceLoader.set_data(): 376a.

      -- 成員函式: load_module (name=None)

          Concrete implementation of *note
          importlib.abc.Loader.load_module(): 5e8. where specifying the
          name of the module to load is optional.

          3.6 版後已棄用: Use *note importlib.abc.Loader.exec_module():
          5e9. instead.

 -- 類別: importlib.machinery.SourcelessFileLoader (fullname, path)

     A concrete implementation of *note importlib.abc.FileLoader: 9bc.
     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:
          3785.

      -- 成員函式: get_code (fullname)

          Returns the code object for *note name: 3784. created from
          *note path: 3785.

      -- 成員函式: 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(): 5e8. where specifying the name
     of the module to load is optional.

     3.6 版後已棄用: Use *note importlib.abc.Loader.exec_module(): 5e9.
     instead.

 -- 類別: importlib.machinery.ExtensionFileLoader (fullname, path)

     A concrete implementation of *note importlib.abc.ExecutionLoader:
     3763. 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.

     3.3 版新加入.

      -- 屬性: 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(3).

          3.5 版新加入.

      -- 成員函式: exec_module (module)

          Initializes the given module object in accordance with PEP
          489(4).

          3.5 版新加入.

      -- 成員函式: is_package (fullname)

          Returns ‘True’ if the file path points to a package’s
          ‘__init__’ module based on *note EXTENSION_SUFFIXES: 377a.

      -- 成員函式: 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: 378a.

          3.4 版新加入.

 -- 類別: 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 ‘__spec__’ 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.  Thus it is
     possible to update the module’s ‘__path__’ at runtime, and this
     will not be automatically reflected in
     ‘__spec__.submodule_search_locations’.

     3.4 版新加入.

      -- 屬性: name

     (‘__name__’)

     A string for the fully-qualified name of the module.

      -- 屬性: loader

     (‘__loader__’)

     The *note Loader: 14c0. that should be used when loading the
     module.  *note Finders: 14bf. should always set this.

      -- 屬性: origin

     (‘__file__’)

     Name of the place from which the module is loaded, e.g.  "builtin"
     for built-in modules and the filename for modules loaded from
     source.  Normally "origin" should be set, but it may be ‘None’ (the
     default) which indicates it is unspecified (e.g.  for namespace
     packages).

      -- 屬性: submodule_search_locations

     (‘__path__’)

     List of strings for where to find submodules, if a package (‘None’
     otherwise).

      -- 屬性: loader_state

     Container of extra module-specific data for use during loading (or
     ‘None’).

      -- 屬性: cached

     (‘__cached__’)

     String for where the compiled module should be stored (or ‘None’).

      -- 屬性: parent

     (‘__package__’)

     (Read-only) The fully-qualified name of the package under which the
     module should be loaded as a submodule (or the empty string for
     top-level modules).  For packages, it is the same as *note
     __name__: d17.

      -- 屬性: has_location

     Boolean indicating whether or not the module’s "origin" attribute
     refers to a loadable location.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/importlib/machinery.py

   (2) https://www.python.org/dev/peps/pep-0489

   (3) https://www.python.org/dev/peps/pep-0489

   (4) https://www.python.org/dev/peps/pep-0489


File: python.info,  Node: importlib util -- Utility code for importers,  Next: Examples<29>,  Prev: importlib machinery -- Importers and path hooks,  Up: importlib --- The implementation of import

5.31.5.6 ‘importlib.util’ – Utility code for importers
......................................................

`Source code:' Lib/importlib/util.py(1)

__________________________________________________________________

This module contains the various objects that help in the construction
of an *note importer: 14c1.

 -- 屬性: 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: 3769.

     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: 613. 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: 1fc. 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: 193. 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: 36f.

 -- 函式: 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: 1fc. is raised.  If ‘sys.implementation.cache_tag’ is
     not defined, *note NotImplementedError: 613. is raised.

     3.4 版新加入.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- 函式: 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(): 86a.).

     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 ValueError: 1fc. is raised if `name' is a relative module
     name but package is a false value (e.g.  ‘None’ or the empty
     string).  *note ValueError: 1fc. is also raised a relative name
     would escape its containing package (e.g.  requesting ‘..bacon’
     from within the ‘spam’ package).

     3.3 版新加入.

 -- 函式: importlib.util.find_spec (name, package=None)

     Find the *note spec: 3638. for a module, optionally relative to the
     specified `package' name.  If the module is in *note sys.modules:
     f2b, then ‘sys.modules[name].__spec__’ is returned (unless the spec
     would be ‘None’ or is not set, in which case *note ValueError: 1fc.
     is raised).  Otherwise a search using *note sys.meta_path: 5eb. 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: 39f. instead of *note
     AttributeError: 3a0. if `package' is in fact not a package (i.e.
     lacks a *note __path__: 1294. attribute).

 -- 函式: importlib.util.module_from_spec (spec)

     Create a new module based on `spec' and *note
     spec.loader.create_module: 559.

     If *note spec.loader.create_module: 559. does not return ‘None’,
     then any pre-existing attributes will not be reset.  Also, no *note
     AttributeError: 3a0. will be raised if triggered while accessing
     `spec' or setting an attribute on the module.

     This function is preferred over using *note types.ModuleType: 6f6.
     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.module_for_loader

     A *note decorator: 284. for *note
     importlib.abc.Loader.load_module(): 5e8. to handle selecting the
     proper module object to load with.  The decorated method is
     expected to have a call signature taking two positional arguments
     (e.g.  ‘load_module(self, module)’) for which the second argument
     will be the module `object' to be used by the loader.  Note that
     the decorator will not work on static methods because of the
     assumption of two arguments.

     The decorated method will take in the `name' of the module to be
     loaded as expected for a *note loader: 14c0.  If the module is not
     found in *note sys.modules: f2b. then a new one is constructed.
     Regardless of where the module came from, *note __loader__: 95b.
     set to `self' and *note __package__: 95a. is set based on what
     *note importlib.abc.InspectLoader.is_package(): 3762. returns (if
     available).  These attributes are set unconditionally to support
     reloading.

     If an exception is raised by the decorated method and a module was
     added to *note sys.modules: f2b, then the module will be removed to
     prevent a partially initialized module from being in left in *note
     sys.modules: f2b.  If the module was already in *note sys.modules:
     f2b. then it is left alone.

     3.3 版更變: *note __loader__: 95b. and *note __package__: 95a. are
     automatically set (when possible).

     3.4 版更變: Set *note __name__: d17, *note __loader__: 95b. *note
     __package__: 95a. unconditionally to support reloading.

     3.4 版後已棄用: The import machinery now directly performs all the
     functionality provided by this function.

 -- 函式: @importlib.util.set_loader

     A *note decorator: 284. for *note
     importlib.abc.Loader.load_module(): 5e8. to set the *note
     __loader__: 95b. attribute on the returned module.  If the
     attribute is already set the decorator does nothing.  It is assumed
     that the first positional argument to the wrapped method (i.e.
     ‘self’) is what *note __loader__: 95b. should be set to.

     3.4 版更變: Set ‘__loader__’ if set to ‘None’, as if the attribute
     does not exist.

     3.4 版後已棄用: The import machinery takes care of this
     automatically.

 -- 函式: @importlib.util.set_package

     A *note decorator: 284. for *note
     importlib.abc.Loader.load_module(): 5e8. to set the *note
     __package__: 95a. attribute on the returned module.  If *note
     __package__: 95a. is set and has a value other than ‘None’ it will
     not be changed.

     3.4 版後已棄用: The import machinery takes care of this
     automatically.

 -- 函式: importlib.util.spec_from_loader (name, loader, *, origin=None,
          is_package=None)

     A factory function for creating a ‘ModuleSpec’ instance based on a
     loader.  The parameters have the same meaning as they do for
     ModuleSpec.  The function uses available *note loader: 14c0. 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 ‘ModuleSpec’ 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: 36f.

 -- 函式: importlib.util.source_hash (source_bytes)

     Return the hash of `source_bytes' as bytes.  A hash-based ‘.pyc’
     file embeds the *note source_hash(): 3796. of the corresponding
     source file’s contents in its header.

     3.7 版新加入.

 -- 類別: 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(): 5e9. as control over what module type is used for
     the module is required.  For those same reasons, the loader’s *note
     create_module(): 559. method must return ‘None’ or a type for which
     its ‘__class__’ attribute can be mutated along with not using *note
     slots: 3797.  Finally, modules which substitute the object placed
     into *note sys.modules: f2b. will not work as there is no way to
     properly replace the module references throughout the interpreter
     safely; *note ValueError: 1fc. 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(): 559, removing the
     compatibility warning for *note
     importlib.machinery.BuiltinImporter: 55a. and *note
     importlib.machinery.ExtensionFileLoader: 55b.

      -- 成員函式: classmethod factory (loader)

          A static 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.8/Lib/importlib/util.py

   (2) https://www.python.org/dev/peps/pep-3147

   (3) https://www.python.org/dev/peps/pep-0488

   (4) https://www.python.org/dev/peps/pep-3147

   (5) https://www.python.org/dev/peps/pep-3147

   (6) https://www.python.org/dev/peps/pep-0488


File: python.info,  Node: Examples<29>,  Prev: importlib util -- Utility code for importers,  Up: importlib --- The implementation of import

5.31.5.7 Examples
.................

* Menu:

* Importing programmatically::
* Checking if a module can be imported::
* Importing a source file directly::
* 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: Examples<29>

5.31.5.8 Importing programmatically
...................................

To programmatically import a module, use *note
importlib.import_module(): b18.

     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: Examples<29>

5.31.5.9 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():
93d.

     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: Setting up an importer,  Prev: Checking if a module can be imported,  Up: Examples<29>

5.31.5.10 Importing a source file directly
..........................................

To import a Python source file directly, use the following recipe
(Python 3.5 and newer only):

     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: Setting up an importer,  Next: Approximating importlib import_module,  Prev: Importing a source file directly,  Up: Examples<29>

5.31.5.11 Setting up an importer
................................

For deep customizations of import, you typically want to implement an
*note importer: 14c1.  This means managing both the *note finder: 14bf.
and *note loader: 14c0. side of things.  For finders there are two
flavours to choose from depending on your needs: a *note meta path
finder: 9b6. or a *note path entry finder: 9b7.  The former is what you
would put on *note sys.meta_path: 5eb. while the latter is what you
create using a *note path entry hook: 14d6. on *note sys.path_hooks:
961. which works with *note sys.path: 48d. 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: Examples<29>

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(): b18.
(Python 3.4 and newer for the importlib usage, Python 3.6 and newer for
other parts of the code).

     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: Using importlib metadata,  Prev: importlib --- The implementation of import,  Up: 匯入模組

5.31.6 Using ‘importlib.metadata’
---------------------------------

3.8 版新加入.

`Source code:' Lib/importlib/metadata.py(1)

     備註: This functionality is provisional and may deviate from the
     usual version semantics of the standard library.

‘importlib.metadata’ is a library that provides for access to installed
package metadata.  Built in part on Python’s import system, this library
intends to replace similar functionality in the entry point API(2) and
metadata API(3) of ‘pkg_resources’.  Along with *note
importlib.resources: 9f. in Python 3.7 and newer (backported as
importlib_resources(4) for older versions of Python), this can eliminate
the need to use the older and less efficient ‘pkg_resources’ package.

By "installed package" we generally mean a third-party package installed
into Python’s ‘site-packages’ directory via tools such as pip(5).
Specifically, it means a package with either a discoverable ‘dist-info’
or ‘egg-info’ directory, and metadata defined by PEP 566(6) or its older
specifications.  By default, package metadata can live on the file
system or in zip archives on *note sys.path: 48d.  Through an extension
mechanism, the metadata can live almost anywhere.

* Menu:

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

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Lib/importlib/metadata.py

   (2) 
https://setuptools.readthedocs.io/en/latest/pkg_resources.html#entry-points

   (3) 
https://setuptools.readthedocs.io/en/latest/pkg_resources.html#metadata-api

   (4) https://importlib-resources.readthedocs.io/en/latest/index.html

   (5) https://pypi.org/project/pip/

   (6) https://www.python.org/dev/peps/pep-0566


File: python.info,  Node: Overview,  Next: Functional API<2>,  Up: Using importlib metadata

5.31.6.1 Overview
.................

Let’s say you wanted to get the version string for a package you’ve
installed using ‘pip’.  We start by creating a virtual environment and
installing something into it:

     $ python3 -m venv example
     $ source example/bin/activate
     (example) $ 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 the set of entry points keyed by group, such as
‘console_scripts’, ‘distutils.commands’ and others.  Each group contains
a sequence of *note EntryPoint: 37a4. objects.

You can get the *note metadata for a distribution: 37a5.:

     >>> 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: 37a6, list its
*note constituent files: 37a7, and get a list of the distribution’s
*note Distribution requirements: 37a8.


File: python.info,  Node: Functional API<2>,  Next: Distributions,  Prev: Overview,  Up: Using importlib metadata

5.31.6.2 Functional API
.......................

This package provides the following functionality via its public API.

* Menu:

* Entry points::
* Distribution metadata::
* Distribution versions::
* Distribution files::
* Distribution requirements::


File: python.info,  Node: Entry points,  Next: Distribution metadata,  Up: Functional API<2>

5.31.6.3 Entry points
.....................

The ‘entry_points()’ function returns a dictionary of all entry points,
keyed by group.  Entry points are represented by ‘EntryPoint’ instances;
each ‘EntryPoint’ has a ‘.name’, ‘.group’, and ‘.value’ attributes and a
‘.load()’ method to resolve the value.

     >>> eps = entry_points()
     >>> list(eps)
     ['console_scripts', 'distutils.commands', 'distutils.setup_keywords', 'egg_info.writers', 'setuptools.installation']
     >>> scripts = eps['console_scripts']
     >>> wheel = [ep for ep in scripts if ep.name == 'wheel'][0]
     >>> wheel
     EntryPoint(name='wheel', value='wheel.cli:main', group='console_scripts')
     >>> 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
entrypoints, their definition, and usage.

   ---------- Footnotes ----------

   (1) 
https://setuptools.readthedocs.io/en/latest/setuptools.html#dynamic-discovery-of-services-and-plugins


File: python.info,  Node: Distribution metadata,  Next: Distribution versions,  Prev: Entry points,  Up: Functional API<2>

5.31.6.4 Distribution metadata
..............................

Every distribution includes some metadata, which you can extract using
the ‘metadata()’ function:

     >>> wheel_metadata = metadata('wheel')

The keys of the returned data structure (1) name the metadata keywords,
and their values are returned unparsed from the distribution metadata:

     >>> wheel_metadata['Requires-Python']
     '>=2.7, !=3.0.*, !=3.1.*, !=3.2.*, !=3.3.*'

   ---------- Footnotes ----------

   (1) (1) Technically, the returned distribution metadata object is an
*note email.message.EmailMessage: 547. instance, but this is an
implementation detail, and not part of the stable API. You should only
use dictionary-like methods and syntax to access the metadata contents.


File: python.info,  Node: Distribution versions,  Next: Distribution files,  Prev: Distribution metadata,  Up: Functional API<2>

5.31.6.5 Distribution versions
..............................

The ‘version()’ function is the quickest way to get a distribution’s
version number, as a string:

     >>> version('wheel')
     '0.32.3'


File: python.info,  Node: Distribution files,  Next: Distribution requirements,  Prev: Distribution versions,  Up: Functional API<2>

5.31.6.6 Distribution files
...........................

You can also get the full set of files contained within a distribution.
The ‘files()’ function takes a distribution package name and returns all
of the files installed by this distribution.  Each file object returned
is a ‘PackagePath’, a *note pathlib.Path: 202. 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

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(1) or otherwise guard
against this condition if the target distribution is not known to have
the metadata present.

   ---------- Footnotes ----------

   (1) 
https://more-itertools.readthedocs.io/en/stable/api.html#more_itertools.always_iterable


File: python.info,  Node: Distribution requirements,  Prev: Distribution files,  Up: Functional API<2>

5.31.6.7 Distribution requirements
..................................

To get the full set of requirements for a distribution, use the
‘requires()’ function:

     >>> requires('wheel')
     ["pytest (>=3.0.0) ; extra == 'test'", "pytest-cov ; extra == 'test'"]


File: python.info,  Node: Distributions,  Next: Extending the search algorithm,  Prev: Functional API<2>,  Up: Using importlib metadata

5.31.6.8 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 package.
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'

The full set of available metadata is not described here.  See PEP
566(1) for additional details.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0566


File: python.info,  Node: Extending the search algorithm,  Prev: Distributions,  Up: Using importlib metadata

5.31.6.9 Extending the search algorithm
.......................................

Because package metadata is not available through *note sys.path: 48d.
searches, or package loaders directly, the metadata for a package is
found through import system *note finders: 14bd.  To find a distribution
package’s metadata, ‘importlib.metadata’ queries the list of *note meta
path finders: 9b6. on *note sys.meta_path: 5eb.

The default ‘PathFinder’ for Python includes a hook that calls into
‘importlib.metadata.MetadataPathFinder’ for finding distributions loaded
from typical file-system-based paths.

The abstract class *note importlib.abc.MetaPathFinder: 9b8. 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:
5eb. 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 names 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.


File: python.info,  Node: Python Language Services,  Next: Miscellaneous Services,  Prev: 匯入模組,  Up: Python 標準函式庫 Standard Library

5.32 Python Language Services
=============================

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.

These modules include:

* Menu:

* parser: parser --- Access Python parse trees. Access Python parse trees
* ast: ast --- Abstract Syntax Trees. Abstract Syntax Trees
* symtable: symtable --- Access to the compiler's symbol tables. Access to the compiler’s symbol tables
* symbol: symbol --- Constants used with Python parse trees. Constants used with Python parse trees
* token: token --- Constants used with Python parse trees. Constants used with Python parse trees
* keyword: keyword --- Testing for Python keywords. Testing for Python keywords
* tokenize: tokenize --- Tokenizer for Python source. Tokenizer for Python source
* tabnanny: tabnanny --- Detection of ambiguous indentation. Detection of ambiguous indentation
* pyclbr: pyclbr --- Python module browser support. Python module browser support
* py_compile: py_compile --- Compile Python source files. Compile Python source files
* compileall: compileall --- Byte-compile Python libraries. Byte-compile Python libraries
* dis: dis --- Python bytecode的反組譯器. Python bytecode的反組譯器
* pickletools: pickletools --- Tools for pickle developers. Tools for pickle developers


File: python.info,  Node: parser --- Access Python parse trees,  Next: ast --- Abstract Syntax Trees,  Up: Python Language Services

5.32.1 ‘parser’ — Access Python parse trees
-------------------------------------------

__________________________________________________________________

The *note parser: c8. module provides an interface to Python’s internal
parser and byte-code compiler.  The primary purpose for this interface
is to allow Python code to edit the parse tree of a Python expression
and create executable code from this.  This is better than trying to
parse and modify an arbitrary Python code fragment as a string because
parsing is performed in a manner identical to the code forming the
application.  It is also faster.

     備註: From Python 2.5 onward, it’s much more convenient to cut in
     at the Abstract Syntax Tree (AST) generation and compilation stage,
     using the *note ast: 8. module.

There are a few things to note about this module which are important to
making use of the data structures created.  This is not a tutorial on
editing the parse trees for Python code, but some examples of using the
*note parser: c8. module are presented.

Most importantly, a good understanding of the Python grammar processed
by the internal parser is required.  For full information on the
language syntax, refer to *note The Python Language Reference: 1201.
The parser itself is created from a grammar specification defined in the
file ‘Grammar/Grammar’ in the standard Python distribution.  The parse
trees stored in the ST objects created by this module are the actual
output from the internal parser when created by the *note expr(): 37b6.
or *note suite(): 37b7. functions, described below.  The ST objects
created by *note sequence2st(): 37b8. faithfully simulate those
structures.  Be aware that the values of the sequences which are
considered "correct" will vary from one version of Python to another as
the formal grammar for the language is revised.  However, transporting
code from one Python version to another as source text will always allow
correct parse trees to be created in the target version, with the only
restriction being that migrating to an older version of the interpreter
will not support more recent language constructs.  The parse trees are
not typically compatible from one version to another, though source code
has usually been forward-compatible within a major release series.

Each element of the sequences returned by *note st2list(): 37b9. or
*note st2tuple(): 37ba. has a simple form.  Sequences representing
non-terminal elements in the grammar always have a length greater than
one.  The first element is an integer which identifies a production in
the grammar.  These integers are given symbolic names in the C header
file ‘Include/graminit.h’ and the Python module *note symbol: fc.  Each
additional element of the sequence represents a component of the
production as recognized in the input string: these are always sequences
which have the same form as the parent.  An important aspect of this
structure which should be noted is that keywords used to identify the
parent node type, such as the keyword *note if: dec. in an ‘if_stmt’,
are included in the node tree without any special treatment.  For
example, the ‘if’ keyword is represented by the tuple ‘(1, 'if')’, where
‘1’ is the numeric value associated with all ‘NAME’ tokens, including
variable and function names defined by the user.  In an alternate form
returned when line number information is requested, the same token might
be represented as ‘(1, 'if', 12)’, where the ‘12’ represents the line
number at which the terminal symbol was found.

Terminal elements are represented in much the same way, but without any
child elements and the addition of the source text which was identified.
The example of the *note if: dec. keyword above is representative.  The
various types of terminal symbols are defined in the C header file
‘Include/token.h’ and the Python module *note token: 111.

The ST objects are not required to support the functionality of this
module, but are provided for three purposes: to allow an application to
amortize the cost of processing complex parse trees, to provide a parse
tree representation which conserves memory space when compared to the
Python list or tuple representation, and to ease the creation of
additional modules in C which manipulate parse trees.  A simple
"wrapper" class may be created in Python to hide the use of ST objects.

The *note parser: c8. module defines functions for a few distinct
purposes.  The most important purposes are to create ST objects and to
convert ST objects to other representations such as parse trees and
compiled code objects, but there are also functions which serve to query
the type of parse tree represented by an ST object.

也參考
......

Module *note symbol: fc.

     Useful constants representing internal nodes of the parse tree.

Module *note token: 111.

     Useful constants representing leaf nodes of the parse tree and
     functions for testing node values.

* Menu:

* Creating ST Objects::
* Converting ST Objects::
* Queries on ST Objects::
* Exceptions and Error Handling::
* ST Objects::
* Example; Emulation of compile(): Example Emulation of compile.


File: python.info,  Node: Creating ST Objects,  Next: Converting ST Objects,  Up: parser --- Access Python parse trees

5.32.1.1 Creating ST Objects
............................

ST objects may be created from source code or from a parse tree.  When
creating an ST object from source, different functions are used to
create the ‘'eval'’ and ‘'exec'’ forms.

 -- 函式: parser.expr (source)

     The *note expr(): 37b6. function parses the parameter `source' as
     if it were an input to ‘compile(source, 'file.py', 'eval')’.  If
     the parse succeeds, an ST object is created to hold the internal
     parse tree representation, otherwise an appropriate exception is
     raised.

 -- 函式: parser.suite (source)

     The *note suite(): 37b7. function parses the parameter `source' as
     if it were an input to ‘compile(source, 'file.py', 'exec')’.  If
     the parse succeeds, an ST object is created to hold the internal
     parse tree representation, otherwise an appropriate exception is
     raised.

 -- 函式: parser.sequence2st (sequence)

     This function accepts a parse tree represented as a sequence and
     builds an internal representation if possible.  If it can validate
     that the tree conforms to the Python grammar and all nodes are
     valid node types in the host version of Python, an ST object is
     created from the internal representation and returned to the
     called.  If there is a problem creating the internal
     representation, or if the tree cannot be validated, a *note
     ParserError: 37bd. exception is raised.  An ST object created this
     way should not be assumed to compile correctly; normal exceptions
     raised by compilation may still be initiated when the ST object is
     passed to *note compilest(): 37be.  This may indicate problems not
     related to syntax (such as a *note MemoryError: ef1. exception),
     but may also be due to constructs such as the result of parsing
     ‘del f(0)’, which escapes the Python parser but is checked by the
     bytecode compiler.

     Sequences representing terminal tokens may be represented as either
     two-element lists of the form ‘(1, 'name')’ or as three-element
     lists of the form ‘(1, 'name', 56)’.  If the third element is
     present, it is assumed to be a valid line number.  The line number
     may be specified for any subset of the terminal symbols in the
     input tree.

 -- 函式: parser.tuple2st (sequence)

     This is the same function as *note sequence2st(): 37b8.  This entry
     point is maintained for backward compatibility.


File: python.info,  Node: Converting ST Objects,  Next: Queries on ST Objects,  Prev: Creating ST Objects,  Up: parser --- Access Python parse trees

5.32.1.2 Converting ST Objects
..............................

ST objects, regardless of the input used to create them, may be
converted to parse trees represented as list- or tuple- trees, or may be
compiled into executable code objects.  Parse trees may be extracted
with or without line numbering information.

 -- 函式: parser.st2list (st, line_info=False, col_info=False)

     This function accepts an ST object from the caller in `st' and
     returns a Python list representing the equivalent parse tree.  The
     resulting list representation can be used for inspection or the
     creation of a new parse tree in list form.  This function does not
     fail so long as memory is available to build the list
     representation.  If the parse tree will only be used for
     inspection, *note st2tuple(): 37ba. should be used instead to
     reduce memory consumption and fragmentation.  When the list
     representation is required, this function is significantly faster
     than retrieving a tuple representation and converting that to
     nested lists.

     If `line_info' is true, line number information will be included
     for all terminal tokens as a third element of the list representing
     the token.  Note that the line number provided specifies the line
     on which the token `ends'.  This information is omitted if the flag
     is false or omitted.

 -- 函式: parser.st2tuple (st, line_info=False, col_info=False)

     This function accepts an ST object from the caller in `st' and
     returns a Python tuple representing the equivalent parse tree.
     Other than returning a tuple instead of a list, this function is
     identical to *note st2list(): 37b9.

     If `line_info' is true, line number information will be included
     for all terminal tokens as a third element of the list representing
     the token.  This information is omitted if the flag is false or
     omitted.

 -- 函式: parser.compilest (st, filename='<syntax-tree>')

     The Python byte compiler can be invoked on an ST object to produce
     code objects which can be used as part of a call to the built-in
     *note exec(): c49. or *note eval(): b95. functions.  This function
     provides the interface to the compiler, passing the internal parse
     tree from `st' to the parser, using the source file name specified
     by the `filename' parameter.  The default value supplied for
     `filename' indicates that the source was an ST object.

     Compiling an ST object may result in exceptions related to
     compilation; an example would be a *note SyntaxError: 45d. caused
     by the parse tree for ‘del f(0)’: this statement is considered
     legal within the formal grammar for Python but is not a legal
     language construct.  The *note SyntaxError: 45d. raised for this
     condition is actually generated by the Python byte-compiler
     normally, which is why it can be raised at this point by the *note
     parser: c8. module.  Most causes of compilation failure can be
     diagnosed programmatically by inspection of the parse tree.


File: python.info,  Node: Queries on ST Objects,  Next: Exceptions and Error Handling,  Prev: Converting ST Objects,  Up: parser --- Access Python parse trees

5.32.1.3 Queries on ST Objects
..............................

Two functions are provided which allow an application to determine if an
ST was created as an expression or a suite.  Neither of these functions
can be used to determine if an ST was created from source code via *note
expr(): 37b6. or *note suite(): 37b7. or from a parse tree via *note
sequence2st(): 37b8.

 -- 函式: parser.isexpr (st)

     When `st' represents an ‘'eval'’ form, this function returns
     ‘True’, otherwise it returns ‘False’.  This is useful, since code
     objects normally cannot be queried for this information using
     existing built-in functions.  Note that the code objects created by
     *note compilest(): 37be. cannot be queried like this either, and
     are identical to those created by the built-in *note compile():
     1b5. function.

 -- 函式: parser.issuite (st)

     This function mirrors *note isexpr(): 37c4. in that it reports
     whether an ST object represents an ‘'exec'’ form, commonly known as
     a "suite."  It is not safe to assume that this function is
     equivalent to ‘not isexpr(st)’, as additional syntactic fragments
     may be supported in the future.


File: python.info,  Node: Exceptions and Error Handling,  Next: ST Objects,  Prev: Queries on ST Objects,  Up: parser --- Access Python parse trees

5.32.1.4 Exceptions and Error Handling
......................................

The parser module defines a single exception, but may also pass other
built-in exceptions from other portions of the Python runtime
environment.  See each function for information about the exceptions it
can raise.

 -- 例外: parser.ParserError

     Exception raised when a failure occurs within the parser module.
     This is generally produced for validation failures rather than the
     built-in *note SyntaxError: 45d. raised during normal parsing.  The
     exception argument is either a string describing the reason of the
     failure or a tuple containing a sequence causing the failure from a
     parse tree passed to *note sequence2st(): 37b8. and an explanatory
     string.  Calls to *note sequence2st(): 37b8. need to be able to
     handle either type of exception, while calls to other functions in
     the module will only need to be aware of the simple string values.

Note that the functions *note compilest(): 37be, *note expr(): 37b6, and
*note suite(): 37b7. may raise exceptions which are normally raised by
the parsing and compilation process.  These include the built in
exceptions *note MemoryError: ef1, *note OverflowError: 965, *note
SyntaxError: 45d, and *note SystemError: 600.  In these cases, these
exceptions carry all the meaning normally associated with them.  Refer
to the descriptions of each function for detailed information.


File: python.info,  Node: ST Objects,  Next: Example Emulation of compile,  Prev: Exceptions and Error Handling,  Up: parser --- Access Python parse trees

5.32.1.5 ST Objects
...................

Ordered and equality comparisons are supported between ST objects.
Pickling of ST objects (using the *note pickle: cb. module) is also
supported.

 -- Data: parser.STType

     The type of the objects returned by *note expr(): 37b6, *note
     suite(): 37b7. and *note sequence2st(): 37b8.

ST objects have the following methods:

 -- 成員函式: ST.compile (filename='<syntax-tree>')

     Same as ‘compilest(st, filename)’.

 -- 成員函式: ST.isexpr ()

     Same as ‘isexpr(st)’.

 -- 成員函式: ST.issuite ()

     Same as ‘issuite(st)’.

 -- 成員函式: ST.tolist (line_info=False, col_info=False)

     Same as ‘st2list(st, line_info, col_info)’.

 -- 成員函式: ST.totuple (line_info=False, col_info=False)

     Same as ‘st2tuple(st, line_info, col_info)’.


File: python.info,  Node: Example Emulation of compile,  Prev: ST Objects,  Up: parser --- Access Python parse trees

5.32.1.6 Example: Emulation of ‘compile()’
..........................................

While many useful operations may take place between parsing and bytecode
generation, the simplest operation is to do nothing.  For this purpose,
using the *note parser: c8. module to produce an intermediate data
structure is equivalent to the code

     >>> code = compile('a + 5', 'file.py', 'eval')
     >>> a = 5
     >>> eval(code)
     10

The equivalent operation using the *note parser: c8. module is somewhat
longer, and allows the intermediate internal parse tree to be retained
as an ST object:

     >>> import parser
     >>> st = parser.expr('a + 5')
     >>> code = st.compile('file.py')
     >>> a = 5
     >>> eval(code)
     10

An application which needs both ST and code objects can package this
code into readily available functions:

     import parser

     def load_suite(source_string):
         st = parser.suite(source_string)
         return st, st.compile()

     def load_expression(source_string):
         st = parser.expr(source_string)
         return st, st.compile()


File: python.info,  Node: ast --- Abstract Syntax Trees,  Next: symtable --- Access to the compiler's symbol tables,  Prev: parser --- Access Python parse trees,  Up: Python Language Services

5.32.2 ‘ast’ — Abstract Syntax Trees
------------------------------------

`Source code:' Lib/ast.py(1)

__________________________________________________________________

The *note ast: 8. module helps Python applications to process trees of
the Python abstract syntax grammar.  The abstract syntax itself might
change with each Python release; this module helps to find out
programmatically what the current grammar looks like.

An abstract syntax tree can be generated by passing ‘ast.PyCF_ONLY_AST’
as a flag to the *note compile(): 1b5. built-in function, or using the
*note parse(): 1a2. helper provided in this module.  The result will be
a tree of objects whose classes all inherit from *note ast.AST: 37d3.
An abstract syntax tree can be compiled into a Python code object using
the built-in *note compile(): 1b5. function.

* Menu:

* Node classes::
* Abstract Grammar::
* ast Helpers::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/ast.py


File: python.info,  Node: Node classes,  Next: Abstract Grammar,  Up: ast --- Abstract Syntax Trees

5.32.2.1 Node classes
.....................

 -- 類別: ast.AST

     This is the base of all AST node classes.  The actual node classes
     are derived from the ‘Parser/Python.asdl’ file, which is reproduced
     *note below: 37d5.  They are defined in the ‘_ast’ C module and
     re-exported in *note ast: 8.

     There is one class defined for each left-hand side symbol in the
     abstract grammar (for example, ‘ast.stmt’ or ‘ast.expr’).  In
     addition, there is one class defined for each constructor on the
     right-hand side; these classes inherit from the classes for the
     left-hand side trees.  For example, ‘ast.BinOp’ inherits from
     ‘ast.expr’.  For production rules with alternatives (aka "sums"),
     the left-hand side class is abstract: only instances of specific
     constructor nodes are ever created.

      -- 屬性: _fields

          Each concrete class has an attribute *note _fields: 37d6.
          which gives the names of all child nodes.

          Each instance of a concrete class has one attribute for each
          child node, of the type as defined in the grammar.  For
          example, ‘ast.BinOp’ instances have an attribute ‘left’ of
          type ‘ast.expr’.

          If these attributes are marked as optional in the grammar
          (using a question mark), the value might be ‘None’.  If the
          attributes can have zero-or-more values (marked with an
          asterisk), the values are represented as Python lists.  All
          possible attributes must be present and have valid values when
          compiling an AST with *note compile(): 1b5.

      -- 屬性: lineno
      -- 屬性: col_offset
      -- 屬性: end_lineno
      -- 屬性: end_col_offset

          Instances of ‘ast.expr’ and ‘ast.stmt’ subclasses have *note
          lineno: 37d7, *note col_offset: 37d8, *note lineno: 37d7, and
          *note col_offset: 37d8. attributes.  The *note lineno: 37d7.
          and *note end_lineno: 37d9. are the first and last line
          numbers of source text span (1-indexed so the first line is
          line 1) and the *note col_offset: 37d8. and *note
          end_col_offset: 37da. are the corresponding UTF-8 byte offsets
          of the first and last tokens that generated the node.  The
          UTF-8 offset is recorded because the parser uses UTF-8
          internally.

          Note that the end positions are not required by the compiler
          and are therefore optional.  The end offset is `after' the
          last symbol, for example one can get the source segment of a
          one-line expression node using ‘source_line[node.col_offset :
          node.end_col_offset]’.

     The constructor of a class ‘ast.T’ parses its arguments as follows:

        * If there are positional arguments, there must be as many as
          there are items in ‘T._fields’; they will be assigned as
          attributes of these names.

        * If there are keyword arguments, they will set the attributes
          of the same names to the given values.

     For example, to create and populate an ‘ast.UnaryOp’ node, you
     could use

          node = ast.UnaryOp()
          node.op = ast.USub()
          node.operand = ast.Constant()
          node.operand.value = 5
          node.operand.lineno = 0
          node.operand.col_offset = 0
          node.lineno = 0
          node.col_offset = 0

     or the more compact

          node = ast.UnaryOp(ast.USub(), ast.Constant(5, lineno=0, col_offset=0),
                             lineno=0, col_offset=0)

3.8 版更變: Class ‘ast.Constant’ is now used for all constants.

3.8 版後已棄用: Old classes ‘ast.Num’, ‘ast.Str’, ‘ast.Bytes’,
‘ast.NameConstant’ and ‘ast.Ellipsis’ are still available, but they will
be removed in future Python releases.  In the meanwhile, instantiating
them will return an instance of a different class.


File: python.info,  Node: Abstract Grammar,  Next: ast Helpers,  Prev: Node classes,  Up: ast --- Abstract Syntax Trees

5.32.2.2 Abstract Grammar
.........................

The abstract grammar is currently defined as follows:

     -- ASDL's 5 builtin types are:
     -- identifier, int, string, object, constant

     module Python
     {
         mod = Module(stmt* body, type_ignore *type_ignores)
             | Interactive(stmt* body)
             | Expression(expr body)
             | FunctionType(expr* argtypes, expr returns)

             -- not really an actual node but useful in Jython's typesystem.
             | Suite(stmt* body)

         stmt = FunctionDef(identifier name, arguments args,
                            stmt* body, expr* decorator_list, expr? returns,
                            string? type_comment)
               | AsyncFunctionDef(identifier name, arguments args,
                                  stmt* body, expr* decorator_list, expr? returns,
                                  string? type_comment)

               | ClassDef(identifier name,
                  expr* bases,
                  keyword* keywords,
                  stmt* body,
                  expr* decorator_list)
               | Return(expr? value)

               | Delete(expr* targets)
               | Assign(expr* targets, expr value, string? type_comment)
               | 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)

               | Raise(expr? exc, expr? cause)
               | Try(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

               -- XXX Jython will be different
               -- 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, slice 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)

               -- 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 | AugLoad | AugStore | Param

         slice = Slice(expr? lower, expr? upper, expr? step)
               | ExtSlice(slice* dims)
               | Index(expr value)

         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)

         -- import name with optional 'as' alias.
         alias = (identifier name, identifier? asname)

         withitem = (expr context_expr, expr? optional_vars)

         type_ignore = TypeIgnore(int lineno, string tag)
     }


File: python.info,  Node: ast Helpers,  Prev: Abstract Grammar,  Up: ast --- Abstract Syntax Trees

5.32.2.3 ‘ast’ Helpers
......................

Apart from the node classes, the *note ast: 8. module defines these
utility functions and classes for traversing abstract syntax trees:

 -- 函式: ast.parse (source, filename='<unknown>', mode='exec', *,
          type_comments=False, feature_version=None)

     Parse the source into an AST node.  Equivalent to ‘compile(source,
     filename, mode, ast.PyCF_ONLY_AST)’.

     If ‘type_comments=True’ is given, the parser is modified to check
     and return type comments as specified by PEP 484(1) and PEP 526(2).
     This is equivalent to adding ‘ast.PyCF_TYPE_COMMENTS’ to the flags
     passed to *note compile(): 1b5.  This will report syntax errors for
     misplaced type comments.  Without this flag, type comments will be
     ignored, and the ‘type_comment’ field on selected AST nodes will
     always be ‘None’.  In addition, the locations of ‘# type: ignore’
     comments will be returned as the ‘type_ignores’ attribute of
     ‘Module’ (otherwise it is always an empty list).

     In addition, if ‘mode’ is ‘'func_type'’, the input syntax is
     modified to correspond to PEP 484(3) "signature type comments",
     e.g.  ‘(str, int) -> List[str]’.

     Also, setting ‘feature_version’ to a tuple ‘(major, minor)’ will
     attempt to parse using that Python version’s grammar.  Currently
     ‘major’ must equal to ‘3’.  For example, setting
     ‘feature_version=(3, 4)’ will allow the use of ‘async’ and ‘await’
     as variable names.  The lowest supported version is ‘(3, 4)’; the
     highest is ‘sys.version_info[0:2]’.

          警告: It is possible to crash the Python interpreter with a
          sufficiently large/complex string due to stack depth
          limitations in Python’s AST compiler.

     3.8 版更變: Added ‘type_comments’, ‘mode='func_type'’ and
     ‘feature_version’.

 -- 函式: ast.literal_eval (node_or_string)

     Safely evaluate an expression node or a string containing a Python
     literal or container display.  The string or node provided may only
     consist of the following Python literal structures: strings, bytes,
     numbers, tuples, lists, dicts, sets, booleans, and ‘None’.

     This can be used for safely evaluating strings containing Python
     values from untrusted sources without the need to parse the values
     oneself.  It is not capable of evaluating arbitrarily complex
     expressions, for example involving operators or indexing.

          警告: It is possible to crash the Python interpreter with a
          sufficiently large/complex string due to stack depth
          limitations in Python’s AST compiler.

     3.2 版更變: Now allows bytes and set literals.

 -- 函式: ast.get_docstring (node, clean=True)

     Return the docstring of the given `node' (which must be a
     ‘FunctionDef’, ‘AsyncFunctionDef’, ‘ClassDef’, or ‘Module’ node),
     or ‘None’ if it has no docstring.  If `clean' is true, clean up the
     docstring’s indentation with *note inspect.cleandoc(): 36dd.

     3.5 版更變: ‘AsyncFunctionDef’ is now supported.

 -- 函式: ast.get_source_segment (source, node, *, padded=False)

     Get source code segment of the `source' that generated `node'.  If
     some location information (‘lineno’, ‘end_lineno’, ‘col_offset’, or
     ‘end_col_offset’) is missing, return ‘None’.

     If `padded' is ‘True’, the first line of a multi-line statement
     will be padded with spaces to match its original position.

     3.8 版新加入.

 -- 函式: ast.fix_missing_locations (node)

     When you compile a node tree with *note compile(): 1b5, the
     compiler expects ‘lineno’ and ‘col_offset’ attributes for every
     node that supports them.  This is rather tedious to fill in for
     generated nodes, so this helper adds these attributes recursively
     where not already set, by setting them to the values of the parent
     node.  It works recursively starting at `node'.

 -- 函式: ast.increment_lineno (node, n=1)

     Increment the line number and end line number of each node in the
     tree starting at `node' by `n'.  This is useful to "move code" to a
     different location in a file.

 -- 函式: ast.copy_location (new_node, old_node)

     Copy source location (‘lineno’, ‘col_offset’, ‘end_lineno’, and
     ‘end_col_offset’) from `old_node' to `new_node' if possible, and
     return `new_node'.

 -- 函式: ast.iter_fields (node)

     Yield a tuple of ‘(fieldname, value)’ for each field in
     ‘node._fields’ that is present on `node'.

 -- 函式: ast.iter_child_nodes (node)

     Yield all direct child nodes of `node', that is, all fields that
     are nodes and all items of fields that are lists of nodes.

 -- 函式: ast.walk (node)

     Recursively yield all descendant nodes in the tree starting at
     `node' (including `node' itself), in no specified order.  This is
     useful if you only want to modify nodes in place and don’t care
     about the context.

 -- 類別: ast.NodeVisitor

     A node visitor base class that walks the abstract syntax tree and
     calls a visitor function for every node found.  This function may
     return a value which is forwarded by the *note visit(): 37e2.
     method.

     This class is meant to be subclassed, with the subclass adding
     visitor methods.

      -- 成員函式: visit (node)

          Visit a node.  The default implementation calls the method
          called ‘self.visit_`classname'’ where `classname' is the name
          of the node class, or *note generic_visit(): 37e3. if that
          method doesn’t exist.

      -- 成員函式: generic_visit (node)

          This visitor calls *note visit(): 37e2. on all children of the
          node.

          Note that child nodes of nodes that have a custom visitor
          method won’t be visited unless the visitor calls *note
          generic_visit(): 37e3. or visits them itself.

     Don’t use the *note NodeVisitor: 282. if you want to apply changes
     to nodes during traversal.  For this a special visitor exists
     (*note NodeTransformer: 37e4.) that allows modifications.

     3.8 版後已棄用: 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 ‘visit_Constant()’ method to handle all constant nodes.

 -- 類別: ast.NodeTransformer

     A *note NodeVisitor: 282. subclass that walks the abstract syntax
     tree and allows modification of nodes.

     The *note NodeTransformer: 37e4. will walk the AST and use the
     return value of the visitor methods to replace or remove the old
     node.  If the return value of the visitor method is ‘None’, the
     node will be removed from its location, otherwise it is replaced
     with the return value.  The return value may be the original node
     in which case no replacement takes place.

     Here is an example transformer that rewrites all occurrences of
     name lookups (‘foo’) to ‘data['foo']’:

          class RewriteName(NodeTransformer):

              def visit_Name(self, node):
                  return Subscript(
                      value=Name(id='data', ctx=Load()),
                      slice=Index(value=Constant(value=node.id)),
                      ctx=node.ctx
                  )

     Keep in mind that if the node you’re operating on has child nodes
     you must either transform the child nodes yourself or call the
     ‘generic_visit()’ method for the node first.

     For nodes that were part of a collection of statements (that
     applies to all statement nodes), the visitor may also return a list
     of nodes rather than just a single node.

     If *note NodeTransformer: 37e4. introduces new nodes (that weren’t
     part of original tree) without giving them location information
     (such as ‘lineno’), *note fix_missing_locations(): 37dd. should be
     called with the new sub-tree to recalculate the location
     information:

          tree = ast.parse('foo', mode='eval')
          new_tree = fix_missing_locations(RewriteName().visit(tree))

     Usually you use the transformer like this:

          node = YourTransformer().visit(node)

 -- 函式: ast.dump (node, annotate_fields=True,
          include_attributes=False)

     Return a formatted dump of the tree in `node'.  This is mainly
     useful for debugging purposes.  If `annotate_fields' is true (by
     default), the returned string will show the names and the values
     for fields.  If `annotate_fields' is false, the result string will
     be more compact by omitting unambiguous field names.  Attributes
     such as line numbers and column offsets are not dumped by default.
     If this is wanted, `include_attributes' can be set to true.

也參考
......

Green Tree Snakes(4), an external documentation resource, has good
details on working with Python ASTs.

ASTTokens(5) annotates Python ASTs with the positions of tokens and text
in the source code that generated them.  This is helpful for tools that
make source code transformations.

leoAst.py(6) unifies the token-based and parse-tree-based views of
python programs by inserting two-way links between tokens and ast nodes.

LibCST(7) parses code as a Concrete Syntax Tree that looks like an ast
tree and keeps all formatting details.  It’s useful for building
automated refactoring (codemod) applications and linters.

Parso(8) is a Python parser that supports error recovery and round-trip
parsing for different Python versions (in multiple Python versions).
Parso is also able to list multiple syntax errors in your python file.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0484

   (2) https://www.python.org/dev/peps/pep-0526

   (3) https://www.python.org/dev/peps/pep-0484

   (4) https://greentreesnakes.readthedocs.io/

   (5) https://asttokens.readthedocs.io/en/latest/user-guide.html

   (6) http://leoeditor.com/appendices.html#leoast-py

   (7) https://libcst.readthedocs.io/

   (8) https://parso.readthedocs.io


File: python.info,  Node: symtable --- Access to the compiler's symbol tables,  Next: symbol --- Constants used with Python parse trees,  Prev: ast --- Abstract Syntax Trees,  Up: Python Language Services

5.32.3 ‘symtable’ — Access to the compiler’s symbol tables
----------------------------------------------------------

`Source code:' Lib/symtable.py(1)

__________________________________________________________________

Symbol tables are generated by the compiler from AST just before
bytecode is generated.  The symbol table is responsible for calculating
the scope of every identifier in the code.  *note symtable: fd. provides
an interface to examine these tables.

* Menu:

* Generating Symbol Tables::
* Examining Symbol Tables::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/symtable.py


File: python.info,  Node: Generating Symbol Tables,  Next: Examining Symbol Tables,  Up: symtable --- Access to the compiler's symbol tables

5.32.3.1 Generating Symbol Tables
.................................

 -- 函式: symtable.symtable (code, filename, compile_type)

     Return the toplevel *note SymbolTable: 37e8. for the Python source
     `code'.  `filename' is the name of the file containing the code.
     `compile_type' is like the `mode' argument to *note compile(): 1b5.


File: python.info,  Node: Examining Symbol Tables,  Prev: Generating Symbol Tables,  Up: symtable --- Access to the compiler's symbol tables

5.32.3.2 Examining Symbol Tables
................................

 -- 類別: symtable.SymbolTable

     A namespace table for a block.  The constructor is not public.

      -- 成員函式: get_type ()

          Return the type of the symbol table.  Possible values are
          ‘'class'’, ‘'module'’, and ‘'function'’.

      -- 成員函式: get_id ()

          Return the table’s identifier.

      -- 成員函式: get_name ()

          Return the table’s name.  This is the name of the class if the
          table is for a class, the name of the function if the table is
          for a function, or ‘'top'’ if the table is global (*note
          get_type(): 37ea. returns ‘'module'’).

      -- 成員函式: get_lineno ()

          Return the number of the first line in the block this table
          represents.

      -- 成員函式: is_optimized ()

          Return ‘True’ if the locals in this table can be optimized.

      -- 成員函式: is_nested ()

          Return ‘True’ if the block is a nested class or function.

      -- 成員函式: has_children ()

          Return ‘True’ if the block has nested namespaces within it.
          These can be obtained with *note get_children(): 37f1.

      -- 成員函式: has_exec ()

          Return ‘True’ if the block uses ‘exec’.

      -- 成員函式: get_identifiers ()

          Return a list of names of symbols in this table.

      -- 成員函式: lookup (name)

          Lookup `name' in the table and return a *note Symbol: 37f5.
          instance.

      -- 成員函式: get_symbols ()

          Return a list of *note Symbol: 37f5. instances for names in
          the table.

      -- 成員函式: get_children ()

          Return a list of the nested symbol tables.

 -- 類別: symtable.Function

     A namespace for a function or method.  This class inherits *note
     SymbolTable: 37e8.

      -- 成員函式: get_parameters ()

          Return a tuple containing names of parameters to this
          function.

      -- 成員函式: get_locals ()

          Return a tuple containing names of locals in this function.

      -- 成員函式: get_globals ()

          Return a tuple containing names of globals in this function.

      -- 成員函式: get_nonlocals ()

          Return a tuple containing names of nonlocals in this function.

      -- 成員函式: get_frees ()

          Return a tuple containing names of free variables in this
          function.

 -- 類別: symtable.Class

     A namespace of a class.  This class inherits *note SymbolTable:
     37e8.

      -- 成員函式: get_methods ()

          Return a tuple containing the names of methods declared in the
          class.

 -- 類別: symtable.Symbol

     An entry in a *note SymbolTable: 37e8. corresponding to an
     identifier in the source.  The constructor is not public.

      -- 成員函式: get_name ()

          Return the symbol’s name.

      -- 成員函式: is_referenced ()

          Return ‘True’ if the symbol is used in its block.

      -- 成員函式: is_imported ()

          Return ‘True’ if the symbol is created from an import
          statement.

      -- 成員函式: is_parameter ()

          Return ‘True’ if the symbol is a parameter.

      -- 成員函式: is_global ()

          Return ‘True’ if the symbol is global.

      -- 成員函式: is_nonlocal ()

          Return ‘True’ if the symbol is nonlocal.

      -- 成員函式: is_declared_global ()

          Return ‘True’ if the symbol is declared global with a global
          statement.

      -- 成員函式: is_local ()

          Return ‘True’ if the symbol is local to its block.

      -- 成員函式: is_annotated ()

          Return ‘True’ if the symbol is annotated.

          3.6 版新加入.

      -- 成員函式: is_free ()

          Return ‘True’ if the symbol is referenced in its block, but
          not assigned to.

      -- 成員函式: is_assigned ()

          Return ‘True’ if the symbol is assigned to in its block.

      -- 成員函式: is_namespace ()

          Return ‘True’ if name binding introduces new namespace.

          If the name is used as the target of a function or class
          statement, this will be true.

          For example:

               >>> table = symtable.symtable("def some_func(): pass", "string", "exec")
               >>> table.lookup("some_func").is_namespace()
               True

          Note that a single name can be bound to multiple objects.  If
          the result is ‘True’, the name may also be bound to other
          objects, like an int or list, that does not introduce a new
          namespace.

      -- 成員函式: get_namespaces ()

          Return a list of namespaces bound to this name.

      -- 成員函式: get_namespace ()

          Return the namespace bound to this name.  If more than one
          namespace is bound, *note ValueError: 1fc. is raised.


File: python.info,  Node: symbol --- Constants used with Python parse trees,  Next: token --- Constants used with Python parse trees,  Prev: symtable --- Access to the compiler's symbol tables,  Up: Python Language Services

5.32.4 ‘symbol’ — Constants used with Python parse trees
--------------------------------------------------------

`Source code:' Lib/symbol.py(1)

__________________________________________________________________

This module provides constants which represent the numeric values of
internal nodes of the parse tree.  Unlike most Python constants, these
use lower-case names.  Refer to the file ‘Grammar/Grammar’ 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.

This module also provides one additional data object:

 -- Data: symbol.sym_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.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/symbol.py


File: python.info,  Node: token --- Constants used with Python parse trees,  Next: keyword --- Testing for Python keywords,  Prev: symbol --- Constants used with Python parse trees,  Up: Python Language Services

5.32.5 ‘token’ — Constants used with Python parse trees
-------------------------------------------------------

`Source code:' 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/Grammar’ 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.

 -- Data: 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:

 -- Data: token.ENDMARKER

 -- Data: token.NAME

 -- Data: token.NUMBER

 -- Data: token.STRING

 -- Data: token.NEWLINE

 -- Data: token.INDENT

 -- Data: token.DEDENT

 -- Data: token.LPAR

     Token value for ‘"("’.

 -- Data: token.RPAR

     Token value for ‘")"’.

 -- Data: token.LSQB

     Token value for ‘"["’.

 -- Data: token.RSQB

     Token value for ‘"]"’.

 -- Data: token.COLON

     Token value for ‘":"’.

 -- Data: token.COMMA

     Token value for ‘","’.

 -- Data: token.SEMI

     Token value for ‘";"’.

 -- Data: token.PLUS

     Token value for ‘"+"’.

 -- Data: token.MINUS

     Token value for ‘"-"’.

 -- Data: token.STAR

     Token value for ‘"*"’.

 -- Data: token.SLASH

     Token value for ‘"/"’.

 -- Data: token.VBAR

     Token value for ‘"|"’.

 -- Data: token.AMPER

     Token value for ‘"&"’.

 -- Data: token.LESS

     Token value for ‘"<"’.

 -- Data: token.GREATER

     Token value for ‘">"’.

 -- Data: token.EQUAL

     Token value for ‘"="’.

 -- Data: token.DOT

     Token value for ‘"."’.

 -- Data: token.PERCENT

     Token value for ‘"%"’.

 -- Data: token.LBRACE

     Token value for ‘"{"’.

 -- Data: token.RBRACE

     Token value for ‘"}"’.

 -- Data: token.EQEQUAL

     Token value for ‘"=="’.

 -- Data: token.NOTEQUAL

     Token value for ‘"!="’.

 -- Data: token.LESSEQUAL

     Token value for ‘"<="’.

 -- Data: token.GREATEREQUAL

     Token value for ‘">="’.

 -- Data: token.TILDE

     Token value for ‘"~"’.

 -- Data: token.CIRCUMFLEX

     Token value for ‘"^"’.

 -- Data: token.LEFTSHIFT

     Token value for ‘"<<"’.

 -- Data: token.RIGHTSHIFT

     Token value for ‘">>"’.

 -- Data: token.DOUBLESTAR

     Token value for ‘"**"’.

 -- Data: token.PLUSEQUAL

     Token value for ‘"+="’.

 -- Data: token.MINEQUAL

     Token value for ‘"-="’.

 -- Data: token.STAREQUAL

     Token value for ‘"*="’.

 -- Data: token.SLASHEQUAL

     Token value for ‘"/="’.

 -- Data: token.PERCENTEQUAL

     Token value for ‘"%="’.

 -- Data: token.AMPEREQUAL

     Token value for ‘"&="’.

 -- Data: token.VBAREQUAL

     Token value for ‘"|="’.

 -- Data: token.CIRCUMFLEXEQUAL

     Token value for ‘"^="’.

 -- Data: token.LEFTSHIFTEQUAL

     Token value for ‘"<<="’.

 -- Data: token.RIGHTSHIFTEQUAL

     Token value for ‘">>="’.

 -- Data: token.DOUBLESTAREQUAL

     Token value for ‘"**="’.

 -- Data: token.DOUBLESLASH

     Token value for ‘"//"’.

 -- Data: token.DOUBLESLASHEQUAL

     Token value for ‘"//="’.

 -- Data: token.AT

     Token value for ‘"@"’.

 -- Data: token.ATEQUAL

     Token value for ‘"@="’.

 -- Data: token.RARROW

     Token value for ‘"->"’.

 -- Data: token.ELLIPSIS

     Token value for ‘"..."’.

 -- Data: token.COLONEQUAL

     Token value for ‘":="’.

 -- Data: token.OP

 -- Data: token.AWAIT

 -- Data: token.ASYNC

 -- Data: token.TYPE_IGNORE

 -- Data: token.TYPE_COMMENT

 -- Data: token.ERRORTOKEN

 -- Data: token.N_TOKENS

 -- Data: token.NT_OFFSET

The following token type values aren’t used by the C tokenizer but are
needed for the *note tokenize: 112. module.

 -- Data: token.COMMENT

     Token value used to indicate a comment.

 -- Data: token.NL

     Token value used to indicate a non-terminating newline.  The *note
     NEWLINE: 3818. 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.

 -- Data: token.ENCODING

     Token value that indicates the encoding used to decode the source
     bytes into text.  The first token returned by *note
     tokenize.tokenize(): c60. will always be an ‘ENCODING’ token.

 -- Data: token.TYPE_COMMENT

     Token value indicating that a type comment was recognized.  Such
     tokens are only produced when *note ast.parse(): 1a2. is invoked
     with ‘type_comments=True’.

3.5 版更變: Added *note AWAIT: 384b. and *note ASYNC: 384c. tokens.

3.7 版更變: Added *note COMMENT: 3852, *note NL: 3853. and *note
ENCODING: 3854. tokens.

3.7 版更變: Removed *note AWAIT: 384b. and *note ASYNC: 384c. tokens.
"async" and "await" are now tokenized as *note NAME: 3815. tokens.

3.8 版更變: Added *note TYPE_COMMENT: 384e, *note TYPE_IGNORE: 384d,
*note COLONEQUAL: 3849.  Added *note AWAIT: 384b. and *note ASYNC: 384c.
tokens back (they’re needed to support parsing older Python versions for
*note ast.parse(): 1a2. with ‘feature_version’ set to 6 or lower).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/token.py


File: python.info,  Node: keyword --- Testing for Python keywords,  Next: tokenize --- Tokenizer for Python source,  Prev: token --- Constants used with Python parse trees,  Up: Python Language Services

5.32.6 ‘keyword’ — Testing for Python keywords
----------------------------------------------

`Source code:' Lib/keyword.py(1)

__________________________________________________________________

This module allows a Python program to determine if a string is a *note
keyword: 13e1.

 -- 函式: keyword.iskeyword (s)

     Return ‘True’ if `s' is a Python *note keyword: 13e1.

 -- Data: keyword.kwlist

     Sequence containing all the *note keywords: 13e1. defined for the
     interpreter.  If any keywords are defined to only be active when
     particular *note __future__: 0. statements are in effect, these
     will be included as well.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/keyword.py


File: python.info,  Node: tokenize --- Tokenizer for Python source,  Next: tabnanny --- Detection of ambiguous indentation,  Prev: keyword --- Testing for Python keywords,  Up: Python Language Services

5.32.7 ‘tokenize’ — Tokenizer for Python source
-----------------------------------------------

`Source code:' Lib/tokenize.py(1)

__________________________________________________________________

The *note tokenize: 112. 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: 141e. and *note
delimiter: 141f. tokens and *note Ellipsis: 1611. are returned using the
generic *note OP: 384a. token type.  The exact type can be determined by
checking the ‘exact_type’ property on the *note named tuple: aa8.
returned from *note tokenize.tokenize(): c60.

* Menu:

* Tokenizing Input::
* Command-Line Usage: Command-Line Usage<2>.
* Examples: Examples<30>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/tokenize.py


File: python.info,  Node: Tokenizing Input,  Next: Command-Line Usage<2>,  Up: tokenize --- Tokenizer for Python source

5.32.7.1 Tokenizing Input
.........................

The primary entry point is a *note generator: 9a7.:

 -- 函式: tokenize.tokenize (readline)

     The *note tokenize(): c60. generator requires one argument,
     `readline', which must be a callable object which provides the same
     interface as the *note io.IOBase.readline(): 1708. 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: aa8. with
     the field names: ‘type string start end line’.

     The returned *note named tuple: aa8. has an additional property
     named ‘exact_type’ that contains the exact operator type for *note
     OP: 384a. tokens.  For all other token types ‘exact_type’ equals
     the named tuple ‘type’ field.

     3.1 版更變: Added support for named tuples.

     3.3 版更變: Added support for ‘exact_type’.

     *note tokenize(): c60. 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(): c60, the `readline' argument is a callable
     returning a single line of input.  However, *note
     generate_tokens(): 103a. expects `readline' to return a str object
     rather than bytes.

     The result is an iterator yielding named tuples, exactly like *note
     tokenize(): c60.  It does not yield an *note ENCODING: 3854. token.

All constants from the *note token: 111. module are also exported from
*note tokenize: 112.

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: 3854. token,
     which is the first token sequence output by *note tokenize(): c60.
     If there is no encoding token in the input, it returns a str
     instead.

*note tokenize(): c60. 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(): 1c86. 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(): c60. 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: 45d. 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(): 1c85. to open Python source files: it uses *note
     detect_encoding(): 1c86. to detect the file encoding.

 -- 函式: tokenize.open (filename)

     Open a file in read only mode using the encoding detected by *note
     detect_encoding(): 1c86.

     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

Note that unclosed single-quoted strings do not cause an error to be
raised.  They are tokenized as *note ERRORTOKEN: 384f, followed by the
tokenization of their contents.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0263

   (2) https://www.python.org/dev/peps/pep-0263


File: python.info,  Node: Command-Line Usage<2>,  Next: Examples<30>,  Prev: Tokenizing Input,  Up: tokenize --- Tokenizer for Python source

5.32.7.2 Command-Line Usage
...........................

3.3 版新加入.

The *note tokenize: 112. 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:

 -- 程式選項: -h, --help

     show this help message and exit

 -- 程式選項: -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: Examples<30>,  Prev: Command-Line Usage<2>,  Up: tokenize --- Tokenizer for Python source

5.32.7.3 Examples
.................

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: 3860.
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(): 103a.:

     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(): c60.:

     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 --- Detection of ambiguous indentation,  Next: pyclbr --- Python module browser support,  Prev: tokenize --- Tokenizer for Python source,  Up: Python Language Services

5.32.8 ‘tabnanny’ — Detection of ambiguous indentation
------------------------------------------------------

`Source code:' Lib/tabnanny.py(1)

__________________________________________________________________

For the time being this module is intended to be called as a script.
However it is possible to import it into an IDE and use the function
*note check(): 3864. described below.

     備註: The API provided by this module is likely to change in future
     releases; such changes may not be backward compatible.

 -- 函式: tabnanny.check (file_or_dir)

     If `file_or_dir' is a directory and not a symbolic link, then
     recursively descend the directory tree named by `file_or_dir',
     checking all ‘.py’ files along the way.  If `file_or_dir' is an
     ordinary Python source file, it is checked for whitespace related
     problems.  The diagnostic messages are written to standard output
     using the *note print(): 88b. function.

 -- Data: tabnanny.verbose

     Flag indicating whether to print verbose messages.  This is
     incremented by the ‘-v’ option if called as a script.

 -- Data: tabnanny.filename_only

     Flag indicating whether to print only the filenames of files
     containing whitespace related problems.  This is set to true by the
     ‘-q’ option if called as a script.

 -- 例外: tabnanny.NannyNag

     Raised by *note process_tokens(): 3868. if detecting an ambiguous
     indent.  Captured and handled in *note check(): 3864.

 -- 函式: tabnanny.process_tokens (tokens)

     This function is used by *note check(): 3864. to process tokens
     generated by the *note tokenize: 112. module.

也參考
......

Module *note tokenize: 112.

     Lexical scanner for Python source code.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/tabnanny.py


File: python.info,  Node: pyclbr --- Python module browser support,  Next: py_compile --- Compile Python source files,  Prev: tabnanny --- Detection of ambiguous indentation,  Up: Python Language Services

5.32.9 ‘pyclbr’ — Python module browser support
-----------------------------------------------

`Source code:' Lib/pyclbr.py(1)

__________________________________________________________________

The *note pyclbr: d9. 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: Class Objects<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/pyclbr.py


File: python.info,  Node: 函式物件,  Next: Class Objects<2>,  Up: pyclbr --- Python module browser support

5.32.9.1 函式物件
.................

Class ‘Function’ instances describe functions defined by def statements.
They have the following attributes:

 -- 屬性: Function.file

     Name of the file in which the function is defined.

 -- 屬性: Function.module

     The name of the module defining the function described.

 -- 屬性: Function.name

     The name of the function.

 -- 屬性: Function.lineno

     The line number in the file where the definition starts.

 -- 屬性: Function.parent

     For top-level functions, None.  For nested functions, the parent.

     3.7 版新加入.

 -- 屬性: Function.children

     A dictionary mapping names to descriptors for nested functions and
     classes.

     3.7 版新加入.


File: python.info,  Node: Class Objects<2>,  Prev: 函式物件,  Up: pyclbr --- Python module browser support

5.32.9.2 Class Objects
......................

Class ‘Class’ instances describe classes defined by class statements.
They have the same attributes as Functions and two more.

 -- 屬性: Class.file

     Name of the file in which the class is defined.

 -- 屬性: Class.module

     The name of the module defining the class described.

 -- 屬性: Class.name

     The name of the class.

 -- 屬性: Class.lineno

     The line number in the file where the definition starts.

 -- 屬性: Class.parent

     For top-level classes, None.  For nested classes, the parent.

     3.7 版新加入.

 -- 屬性: Class.children

     A dictionary mapping names to descriptors for nested functions and
     classes.

     3.7 版新加入.

 -- 屬性: Class.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(): 116f. are listed as a string with the class name
     instead of as ‘Class’ objects.

 -- 屬性: Class.methods

     A dictionary mapping method names to line numbers.  This can be
     derived from the newer children dictionary, but remains for
     back-compatibility.


File: python.info,  Node: py_compile --- Compile Python source files,  Next: compileall --- Byte-compile Python libraries,  Prev: pyclbr --- Python module browser support,  Up: Python Language Services

5.32.10 ‘py_compile’ — Compile Python source files
--------------------------------------------------

`Source code:' Lib/py_compile.py(1)

__________________________________________________________________

The *note py_compile: d8. 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 as the name of the source file in
     error messages instead of `file'.  If `doraise' is true, a *note
     PyCompileError: 387f. 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: 387f. 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:
     95d. 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(): 1b5. function.  The default of ‘-1’
     selects the optimization level of the current interpreter.

     `invalidation_mode' should be a member of the *note
     PycInvalidationMode: 3880. enum and controls how the generated
     bytecode cache is invalidated at runtime.  The default is *note
     PycInvalidationMode.CHECKED_HASH: 3881. if the ‘SOURCE_DATE_EPOCH’
     environment variable is set, otherwise the default is *note
     PycInvalidationMode.TIMESTAMP: 3882.

     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: 9b. for the
     byte-code cache file writing.  This means file creation/writing
     semantics now match what *note importlib: 9b. does, e.g.
     permissions, write-and-move semantics, etc.  Also added the caveat
     that *note FileExistsError: 95d. 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: 3881.

     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 版更變: The `quiet' parameter was added.

 -- 類別: py_compile.PycInvalidationMode

     A 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: 32e. 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: 3881, 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.

 -- 函式: py_compile.main (args=None)

     Compile several source files.  The files named in `args' (or on the
     command line, if `args' is ‘None’) are compiled and the resulting
     byte-code is cached in the normal manner.  This function does not
     search a directory structure to locate source files; it only
     compiles files named explicitly.  If ‘'-'’ is the only parameter in
     args, the list of files is taken from standard input.

     3.2 版更變: Added support for ‘'-'’.

When this module is run as a script, the *note main(): 3884. is used to
compile all the files named on the command line.  The exit status is
nonzero if one of the files could not be compiled.

也參考
......

Module *note compileall: 21.

     Utilities to compile all Python source files in a directory tree.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/py_compile.py

   (2) https://www.python.org/dev/peps/pep-3147

   (3) https://www.python.org/dev/peps/pep-0488

   (4) https://www.python.org/dev/peps/pep-3147

   (5) https://www.python.org/dev/peps/pep-0552


File: python.info,  Node: compileall --- Byte-compile Python libraries,  Next: dis --- Python bytecode的反組譯器,  Prev: py_compile --- Compile Python source files,  Up: Python Language Services

5.32.11 ‘compileall’ — Byte-compile Python libraries
----------------------------------------------------

`Source code:' 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.

* Menu:

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

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/compileall.py


File: python.info,  Node: Command-line use,  Next: Public functions,  Up: compileall --- Byte-compile Python libraries

5.32.11.1 Command-line use
..........................

This module can work as a script (using ‘python -m compileall’) to
compile Python sources.

 -- 程式選項: directory ...
 -- 程式選項: 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>’.

 -- 程式選項: -l

     Do not recurse into subdirectories, only compile source code files
     directly contained in the named or implied directories.

 -- 程式選項: -f

     Force rebuild even if timestamps are up-to-date.

 -- 程式選項: -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.

 -- 程式選項: -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.

 -- 程式選項: -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.

 -- 程式選項: -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’.

 -- 程式選項: -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.

 -- 程式選項: -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’.

 -- 程式選項: -j N

     Use `N' workers to compile the files within the given directory.
     If ‘0’ is used, then the result of *note os.cpu_count(): 884. will
     be used.

 -- 程式選項: --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: 32e. 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.

3.2 版更變: Added the ‘-i’, ‘-b’ and ‘-h’ options.

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 版更變: Added the ‘--invalidation-mode’ option.

There is no command-line option to control the optimization level used
by the *note compile(): 1b5. function, because the Python interpreter
itself already provides the option: ‘python -O -m compileall’.

Similarly, the *note compile(): 1b5. function respects the *note
sys.pycache_prefix: 157. setting.  The generated bytecode cache will
only be useful if *note compile(): 1b5. is run with the same *note
sys.pycache_prefix: 157. (if any) that will be used at runtime.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3147


File: python.info,  Node: Public functions,  Prev: Command-line use,  Up: compileall --- Byte-compile Python libraries

5.32.11.2 Public functions
..........................

 -- 函式: compileall.compile_dir (dir, maxlevels=10, ddir=None,
          force=False, rx=None, quiet=0, legacy=False, optimize=-1,
          workers=1, invalidation_mode=None)

     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 ‘10’.

     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.

     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(): 1b5. function.

     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: 1fc.
     will be raised.

     `invalidation_mode' should be a member of the *note
     py_compile.PycInvalidationMode: 3880. enum and controls how the
     generated pycs are invalidated at runtime.

     3.2 版更變: Added the `legacy' and `optimize' parameter.

     3.5 版更變: Added the `workers' parameter.

     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: 36f.

     3.7 版更變: The `invalidation_mode' parameter was added.

     3.7.2 版更變: The `invalidation_mode' parameter’s default value is
     updated to None.

     3.8 版更變: Setting `workers' to 0 now chooses the optimal number
     of cores.

 -- 函式: compileall.compile_file (fullname, ddir=None, force=False,
          rx=None, quiet=0, legacy=False, optimize=-1,
          invalidation_mode=None)

     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.

     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(): 1b5. function.

     `invalidation_mode' should be a member of the *note
     py_compile.PycInvalidationMode: 3880. enum and controls how the
     generated pycs are invalidated at runtime.

     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 版更變: The `invalidation_mode' parameter was added.

     3.7.2 版更變: The `invalidation_mode' parameter’s default value is
     updated to None.

 -- 函式: 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(): 377. function.  Note that unlike the other
     compile functions, ‘maxlevels’ defaults to ‘0’.

     3.2 版更變: Added the `legacy' and `optimize' parameter.

     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 版更變: The `invalidation_mode' parameter was added.

     3.7.2 版更變: The `invalidation_mode' parameter’s default value is
     updated to 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)

也參考
......

Module *note py_compile: d8.

     Byte-compile a single source file.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3147

   (2) https://www.python.org/dev/peps/pep-3147


File: python.info,  Node: dis --- Python bytecode的反組譯器,  Next: pickletools --- Tools for pickle developers,  Prev: compileall --- Byte-compile Python libraries,  Up: Python Language Services

5.32.12 ‘dis’ — Python bytecode的反組譯器
-----------------------------------------

`原始碼：'Lib/dis.py(1)

__________________________________________________________________

*note dis: 38. 模組支援反組譯分析 CPython *note bytecode: 619.。CPython
bytecode 作為輸入的模組被定義於 ‘Include/opcode.h’ 並且被編譯器和直譯器
所使用。

`CPython implementation detail:' 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.

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           0 LOAD_GLOBAL              0 (len)
                   2 LOAD_FAST                0 (alist)
                   4 CALL_FUNCTION            1
                   6 RETURN_VALUE

(The "2" is a line number).

* Menu:

* Bytecode analysis::
* Analysis functions::
* Python Bytecode Instructions::
* Opcode collections::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/dis.py


File: python.info,  Node: Bytecode analysis,  Next: Analysis functions,  Up: dis --- Python bytecode的反組譯器

5.32.12.1 Bytecode analysis
...........................

3.4 版新加入.

The bytecode analysis API allows pieces of Python code to be wrapped in
a *note Bytecode: 83c. object that provides easy access to details of
the compiled code.

 -- 類別: dis.Bytecode (x, *, first_line=None, current_offset=None)

     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(): 1b5.).

     This is a convenience wrapper around many of the functions listed
     below, most notably *note get_instructions(): 83b, as iterating
     over a *note Bytecode: 83c. instance yields the bytecode operations
     as *note Instruction: 83a. 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():
     83d. will display a "current instruction" marker against the
     specified opcode.

      -- 成員函式: classmethod from_traceback (tb)

          Construct a *note Bytecode: 83c. instance from the given
          traceback, setting `current_offset' to the instruction
          responsible for the exception.

      -- Data: codeobj

          The compiled code object.

      -- Data: 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(): 389, 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(): bd3.

     3.7 版更變: This can now handle coroutine and asynchronous
     generator objects.

Example:

     >>> bytecode = dis.Bytecode(myfunc)
     >>> for instr in bytecode:
     ...     print(instr.opname)
     ...
     LOAD_GLOBAL
     LOAD_FAST
     CALL_FUNCTION
     RETURN_VALUE


File: python.info,  Node: Analysis functions,  Next: Python Bytecode Instructions,  Prev: Bytecode analysis,  Up: dis --- Python bytecode的反組譯器

5.32.12.2 Analysis functions
............................

The *note dis: 38. 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 版更變: Added `file' parameter.

 -- 函式: dis.dis (x=None, *, file=None, depth=None)

     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 (the code of
     comprehensions, generator expressions and nested functions, and the
     code used for building nested classes).  Strings are first compiled
     to code objects with the *note compile(): 1b5. 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.

     3.4 版更變: Added `file' parameter.

     3.7 版更變: Implemented recursive disassembling and added `depth'
     parameter.

     3.7 版更變: This can now handle coroutine and asynchronous
     generator objects.

 -- 函式: dis.distb (tb=None, *, file=None)

     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 版更變: Added `file' parameter.

 -- 函式: dis.disassemble (code, lasti=-1, *, file=None)
 -- 函式: dis.disco (code, lasti=-1, *, file=None)

     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 版更變: Added `file' parameter.

 -- 函式: dis.get_instructions (x, *, first_line=None)

     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: 83a. 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.

     3.4 版新加入.

 -- 函式: dis.findlinestarts (code)

     This generator function uses the ‘co_firstlineno’ and ‘co_lnotab’
     attributes of the code object `code' to find the offsets which are
     starts of lines in the source code.  They are generated as
     ‘(offset, lineno)’ pairs.  See Objects/lnotab_notes.txt(1) for the
     ‘co_lnotab’ format and how to decode it.

     3.6 版更變: Line numbers can be decreasing.  Before, they were
     always increasing.

 -- 函式: 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(): 83f. 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 版更變: Added `jump' parameter.

   ---------- Footnotes ----------

   (1) 
https://github.com/python/cpython/tree/3.8/Objects/lnotab_notes.txt


File: python.info,  Node: Python Bytecode Instructions,  Next: Opcode collections,  Prev: Analysis functions,  Up: dis --- Python bytecode的反組譯器

5.32.12.3 Python Bytecode Instructions
......................................

The *note get_instructions(): 83b. function and *note Bytecode: 83c.
class provide details of bytecode instructions as *note Instruction:
83a. instances:

 -- 類別: dis.Instruction

     Details for a bytecode operation

      -- Data: opcode

          numeric code for operation, corresponding to the opcode values
          listed below and the bytecode values in the *note Opcode
          collections: 38a2.

      -- Data: opname

          human readable name for operation

      -- Data: arg

          numeric argument to operation (if any), otherwise ‘None’

      -- Data: argval

          resolved arg value (if known), otherwise same as arg

      -- Data: argrepr

          human readable description of operation argument

      -- Data: offset

          start index of operation within bytecode sequence

      -- Data: starts_line

          line started by this opcode (if any), otherwise ‘None’

      -- Data: is_jump_target

          ‘True’ if other code jumps to here, otherwise ‘False’

     3.4 版新加入.

The Python compiler currently generates the following bytecode
instructions.

`General instructions'

 -- Opcode: NOP

     Do nothing code.  Used as a placeholder by the bytecode optimizer.

 -- Opcode: POP_TOP

     Removes the top-of-stack (TOS) item.

 -- Opcode: ROT_TWO

     Swaps the two top-most stack items.

 -- Opcode: ROT_THREE

     Lifts second and third stack item one position up, moves top down
     to position three.

 -- Opcode: ROT_FOUR

     Lifts second, third and fourth stack items one position up, moves
     top down to position four.

     3.8 版新加入.

 -- Opcode: DUP_TOP

     Duplicates the reference on top of the stack.

     3.2 版新加入.

 -- Opcode: DUP_TOP_TWO

     Duplicates the two references on top of the stack, leaving them in
     the same order.

     3.2 版新加入.

`Unary operations'

Unary operations take the top of the stack, apply the operation, and
push the result back on the stack.

 -- Opcode: UNARY_POSITIVE

     Implements ‘TOS = +TOS’.

 -- Opcode: UNARY_NEGATIVE

     Implements ‘TOS = -TOS’.

 -- Opcode: UNARY_NOT

     Implements ‘TOS = not TOS’.

 -- Opcode: UNARY_INVERT

     Implements ‘TOS = ~TOS’.

 -- Opcode: GET_ITER

     Implements ‘TOS = iter(TOS)’.

 -- Opcode: GET_YIELD_FROM_ITER

     If ‘TOS’ is a *note generator iterator: 45c. or *note coroutine:
     1a7. object it is left as is.  Otherwise, implements ‘TOS =
     iter(TOS)’.

     3.5 版新加入.

`Binary operations'

Binary operations remove the top of the stack (TOS) and the second
top-most stack item (TOS1) from the stack.  They perform the operation,
and put the result back on the stack.

 -- Opcode: BINARY_POWER

     Implements ‘TOS = TOS1 ** TOS’.

 -- Opcode: BINARY_MULTIPLY

     Implements ‘TOS = TOS1 * TOS’.

 -- Opcode: BINARY_MATRIX_MULTIPLY

     Implements ‘TOS = TOS1 @ TOS’.

     3.5 版新加入.

 -- Opcode: BINARY_FLOOR_DIVIDE

     Implements ‘TOS = TOS1 // TOS’.

 -- Opcode: BINARY_TRUE_DIVIDE

     Implements ‘TOS = TOS1 / TOS’.

 -- Opcode: BINARY_MODULO

     Implements ‘TOS = TOS1 % TOS’.

 -- Opcode: BINARY_ADD

     Implements ‘TOS = TOS1 + TOS’.

 -- Opcode: BINARY_SUBTRACT

     Implements ‘TOS = TOS1 - TOS’.

 -- Opcode: BINARY_SUBSCR

     Implements ‘TOS = TOS1[TOS]’.

 -- Opcode: BINARY_LSHIFT

     Implements ‘TOS = TOS1 << TOS’.

 -- Opcode: BINARY_RSHIFT

     Implements ‘TOS = TOS1 >> TOS’.

 -- Opcode: BINARY_AND

     Implements ‘TOS = TOS1 & TOS’.

 -- Opcode: BINARY_XOR

     Implements ‘TOS = TOS1 ^ TOS’.

 -- Opcode: BINARY_OR

     Implements ‘TOS = TOS1 | TOS’.

`In-place operations'

In-place operations are like binary operations, in that they remove TOS
and TOS1, and push the result back on the stack, but the operation is
done in-place when TOS1 supports it, and the resulting TOS may be (but
does not have to be) the original TOS1.

 -- Opcode: INPLACE_POWER

     Implements in-place ‘TOS = TOS1 ** TOS’.

 -- Opcode: INPLACE_MULTIPLY

     Implements in-place ‘TOS = TOS1 * TOS’.

 -- Opcode: INPLACE_MATRIX_MULTIPLY

     Implements in-place ‘TOS = TOS1 @ TOS’.

     3.5 版新加入.

 -- Opcode: INPLACE_FLOOR_DIVIDE

     Implements in-place ‘TOS = TOS1 // TOS’.

 -- Opcode: INPLACE_TRUE_DIVIDE

     Implements in-place ‘TOS = TOS1 / TOS’.

 -- Opcode: INPLACE_MODULO

     Implements in-place ‘TOS = TOS1 % TOS’.

 -- Opcode: INPLACE_ADD

     Implements in-place ‘TOS = TOS1 + TOS’.

 -- Opcode: INPLACE_SUBTRACT

     Implements in-place ‘TOS = TOS1 - TOS’.

 -- Opcode: INPLACE_LSHIFT

     Implements in-place ‘TOS = TOS1 << TOS’.

 -- Opcode: INPLACE_RSHIFT

     Implements in-place ‘TOS = TOS1 >> TOS’.

 -- Opcode: INPLACE_AND

     Implements in-place ‘TOS = TOS1 & TOS’.

 -- Opcode: INPLACE_XOR

     Implements in-place ‘TOS = TOS1 ^ TOS’.

 -- Opcode: INPLACE_OR

     Implements in-place ‘TOS = TOS1 | TOS’.

 -- Opcode: STORE_SUBSCR

     Implements ‘TOS1[TOS] = TOS2’.

 -- Opcode: DELETE_SUBSCR

     Implements ‘del TOS1[TOS]’.

`Coroutine opcodes'

 -- Opcode: GET_AWAITABLE

     Implements ‘TOS = get_awaitable(TOS)’, where ‘get_awaitable(o)’
     returns ‘o’ if ‘o’ is a coroutine object or a generator object with
     the CO_ITERABLE_COROUTINE flag, or resolves ‘o.__await__’.

     3.5 版新加入.

 -- Opcode: GET_AITER

     Implements ‘TOS = TOS.__aiter__()’.

     3.5 版新加入.

     3.7 版更變: Returning awaitable objects from ‘__aiter__’ is no
     longer supported.

 -- Opcode: GET_ANEXT

     Implements ‘PUSH(get_awaitable(TOS.__anext__()))’.  See
     ‘GET_AWAITABLE’ for details about ‘get_awaitable’

     3.5 版新加入.

 -- Opcode: END_ASYNC_FOR

     Terminates an *note async for: 2e4. loop.  Handles an exception
     raised when awaiting a next item.  If TOS is *note
     StopAsyncIteration: 1017. pop 7 values from the stack and restore
     the exception state using the second three of them.  Otherwise
     re-raise the exception using the three values from the stack.  An
     exception handler block is removed from the block stack.

     3.8 版新加入.

 -- Opcode: BEFORE_ASYNC_WITH

     Resolves ‘__aenter__’ and ‘__aexit__’ from the object on top of the
     stack.  Pushes ‘__aexit__’ and result of ‘__aenter__()’ to the
     stack.

     3.5 版新加入.

 -- Opcode: SETUP_ASYNC_WITH

     Creates a new frame object.

     3.5 版新加入.

`Miscellaneous opcodes'

 -- Opcode: PRINT_EXPR

     Implements the expression statement for the interactive mode.  TOS
     is removed from the stack and printed.  In non-interactive mode, an
     expression statement is terminated with *note POP_TOP: 38ab.

 -- Opcode: SET_ADD (i)

     Calls ‘set.add(TOS1[-i], TOS)’.  Used to implement set
     comprehensions.

 -- Opcode: LIST_APPEND (i)

     Calls ‘list.append(TOS1[-i], TOS)’.  Used to implement list
     comprehensions.

 -- Opcode: MAP_ADD (i)

     Calls ‘dict.__setitem__(TOS1[-i], TOS1, TOS)’.  Used to implement
     dict comprehensions.

     3.1 版新加入.

     3.8 版更變: Map value is TOS and map key is TOS1.  Before, those
     were reversed.

For all of the *note SET_ADD: 38d9, *note LIST_APPEND: 38da. and *note
MAP_ADD: 2e5. 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 TOS to the caller of the function.

 -- Opcode: YIELD_VALUE

     Pops TOS and yields it from a *note generator: 9a7.

 -- Opcode: YIELD_FROM

     Pops TOS and delegates to it as a subiterator from a *note
     generator: 9a7.

     3.3 版新加入.

 -- 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: 624.
     statically.

     3.6 版新加入.

 -- Opcode: IMPORT_STAR

     Loads all symbols not starting with ‘'_'’ directly from the module
     TOS to the local namespace.  The module is popped after loading all
     names.  This opcode implements ‘from module import *’.

 -- Opcode: POP_BLOCK

     Removes one block from the block stack.  Per frame, there is a
     stack of blocks, denoting *note try: d77. statements, and such.

 -- Opcode: POP_EXCEPT

     Removes one block from the block stack.  The popped block must be
     an exception handler block, as implicitly created when entering an
     except handler.  In addition to popping extraneous values from the
     frame stack, the last three popped values are used to restore the
     exception state.

 -- Opcode: POP_FINALLY (preserve_tos)

     Cleans up the value stack and the block stack.  If `preserve_tos'
     is not ‘0’ TOS first is popped from the stack and pushed on the
     stack after performing other stack operations:

        * If TOS is ‘NULL’ or an integer (pushed by *note BEGIN_FINALLY:
          2de. or *note CALL_FINALLY: 2df.) it is popped from the stack.

        * If TOS is an exception type (pushed when an exception has been
          raised) 6 values are popped from the stack, the last three
          popped values are used to restore the exception state.  An
          exception handler block is removed from the block stack.

     It is similar to *note END_FINALLY: 2e1, but doesn’t change the
     bytecode counter nor raise an exception.  Used for implementing
     *note break: 2dc, *note continue: 182. and *note return: 191. in
     the *note finally: 183. block.

     3.8 版新加入.

 -- Opcode: BEGIN_FINALLY

     Pushes ‘NULL’ onto the stack for using it in *note END_FINALLY:
     2e1, *note POP_FINALLY: 2e0, *note WITH_CLEANUP_START: 2e2. and
     *note WITH_CLEANUP_FINISH: 38e1.  Starts the *note finally: 183.
     block.

     3.8 版新加入.

 -- Opcode: END_FINALLY

     Terminates a *note finally: 183. clause.  The interpreter recalls
     whether the exception has to be re-raised or execution has to be
     continued depending on the value of TOS.

        * If TOS is ‘NULL’ (pushed by *note BEGIN_FINALLY: 2de.)
          continue from the next instruction.  TOS is popped.

        * If TOS is an integer (pushed by *note CALL_FINALLY: 2df.),
          sets the bytecode counter to TOS. TOS is popped.

        * If TOS is an exception type (pushed when an exception has been
          raised) 6 values are popped from the stack, the first three
          popped values are used to re-raise the exception and the last
          three popped values are used to restore the exception state.
          An exception handler block is removed from the block stack.

 -- Opcode: LOAD_BUILD_CLASS

     Pushes ‘builtins.__build_class__()’ onto the stack.  It is later
     called by *note CALL_FUNCTION: 61e. to construct a class.

 -- Opcode: SETUP_WITH (delta)

     This opcode performs several operations before a with block starts.
     First, it loads *note __exit__(): c9b. from the context manager and
     pushes it onto the stack for later use by *note WITH_CLEANUP_START:
     2e2.  Then, *note __enter__(): c9a. is called, and a finally block
     pointing to `delta' is pushed.  Finally, the result of calling the
     ‘__enter__()’ method is pushed onto the stack.  The next opcode
     will either ignore it (*note POP_TOP: 38ab.), or store it in (a)
     variable(s) (*note STORE_FAST: 38e4, *note STORE_NAME: 38e5, or
     *note UNPACK_SEQUENCE: 38e6.).

     3.2 版新加入.

 -- Opcode: WITH_CLEANUP_START

     Starts cleaning up the stack when a *note with: 6ee. statement
     block exits.

     At the top of the stack are either ‘NULL’ (pushed by *note
     BEGIN_FINALLY: 2de.) or 6 values pushed if an exception has been
     raised in the with block.  Below is the context manager’s *note
     __exit__(): c9b. or *note __aexit__(): 149e. bound method.

     If TOS is ‘NULL’, calls ‘SECOND(None, None, None)’, removes the
     function from the stack, leaving TOS, and pushes ‘None’ to the
     stack.  Otherwise calls ‘SEVENTH(TOP, SECOND, THIRD)’, shifts the
     bottom 3 values of the stack down, replaces the empty spot with
     ‘NULL’ and pushes TOS. Finally pushes the result of the call.

 -- Opcode: WITH_CLEANUP_FINISH

     Finishes cleaning up the stack when a *note with: 6ee. statement
     block exits.

     TOS is result of ‘__exit__()’ or ‘__aexit__()’ function call pushed
     by *note WITH_CLEANUP_START: 2e2.  SECOND is ‘None’ or an exception
     type (pushed when an exception has been raised).

     Pops two values from the stack.  If SECOND is not None and TOS is
     true unwinds the EXCEPT_HANDLER block which was created when the
     exception was caught and pushes ‘NULL’ to the stack.

All of the following opcodes use their arguments.

 -- Opcode: STORE_NAME (namei)

     Implements ‘name = TOS’.  `namei' is the index of `name' in the
     attribute ‘co_names’ of the code object.  The compiler tries to use
     *note STORE_FAST: 38e4. or *note STORE_GLOBAL: 38e7. if possible.

 -- Opcode: DELETE_NAME (namei)

     Implements ‘del name’, where `namei' is the index into ‘co_names’
     attribute of the code object.

 -- Opcode: UNPACK_SEQUENCE (count)

     Unpacks TOS into `count' individual values, which are put onto the
     stack right-to-left.

 -- Opcode: UNPACK_EX (counts)

     Implements assignment with a starred target: Unpacks an iterable in
     TOS 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 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 resulting values are put onto the stack right-to-left.

 -- Opcode: STORE_ATTR (namei)

     Implements ‘TOS.name = TOS1’, where `namei' is the index of name in
     ‘co_names’.

 -- Opcode: DELETE_ATTR (namei)

     Implements ‘del TOS.name’, using `namei' as index into ‘co_names’.

 -- Opcode: STORE_GLOBAL (namei)

     Works as *note STORE_NAME: 38e5, but stores the name as a global.

 -- Opcode: DELETE_GLOBAL (namei)

     Works as *note DELETE_NAME: 38e8, 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.

 -- Opcode: BUILD_TUPLE (count)

     Creates a tuple consuming `count' items from the stack, and pushes
     the resulting tuple onto the stack.

 -- Opcode: BUILD_LIST (count)

     Works as *note BUILD_TUPLE: 38ef, but creates a list.

 -- Opcode: BUILD_SET (count)

     Works as *note BUILD_TUPLE: 38ef, 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: ‘{..., TOS3:
     TOS2, TOS1: TOS}’.

     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: 38f2. specialized for constant
     keys.  Pops the top element on the stack which contains a tuple of
     keys, then starting from ‘TOS1’, 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: BUILD_TUPLE_UNPACK (count)

     Pops `count' iterables from the stack, joins them in a single
     tuple, and pushes the result.  Implements iterable unpacking in
     tuple displays ‘(*x, *y, *z)’.

     3.5 版新加入.

 -- Opcode: BUILD_TUPLE_UNPACK_WITH_CALL (count)

     This is similar to *note BUILD_TUPLE_UNPACK: 38f3, but is used for
     ‘f(*x, *y, *z)’ call syntax.  The stack item at position ‘count +
     1’ should be the corresponding callable ‘f’.

     3.6 版新加入.

 -- Opcode: BUILD_LIST_UNPACK (count)

     This is similar to *note BUILD_TUPLE_UNPACK: 38f3, but pushes a
     list instead of tuple.  Implements iterable unpacking in list
     displays ‘[*x, *y, *z]’.

     3.5 版新加入.

 -- Opcode: BUILD_SET_UNPACK (count)

     This is similar to *note BUILD_TUPLE_UNPACK: 38f3, but pushes a set
     instead of tuple.  Implements iterable unpacking in set displays
     ‘{*x, *y, *z}’.

     3.5 版新加入.

 -- Opcode: BUILD_MAP_UNPACK (count)

     Pops `count' mappings from the stack, merges them into a single
     dictionary, and pushes the result.  Implements dictionary unpacking
     in dictionary displays ‘{**x, **y, **z}’.

     3.5 版新加入.

 -- Opcode: BUILD_MAP_UNPACK_WITH_CALL (count)

     This is similar to *note BUILD_MAP_UNPACK: 38f6, but is used for
     ‘f(**x, **y, **z)’ call syntax.  The stack item at position ‘count
     + 2’ should be the corresponding callable ‘f’.

     3.5 版新加入.

     3.6 版更變: The position of the callable is determined by adding 2
     to the opcode argument instead of encoding it in the second byte of
     the argument.

 -- Opcode: LOAD_ATTR (namei)

     Replaces TOS with ‘getattr(TOS, co_names[namei])’.

 -- Opcode: COMPARE_OP (opname)

     Performs a Boolean operation.  The operation name can be found in
     ‘cmp_op[opname]’.

 -- Opcode: IMPORT_NAME (namei)

     Imports the module ‘co_names[namei]’.  TOS and TOS1 are popped and
     provide the `fromlist' and `level' arguments of *note __import__():
     615.  The module object is pushed onto the stack.  The current
     namespace is not affected: for a proper import statement, a
     subsequent *note STORE_FAST: 38e4. instruction modifies the
     namespace.

 -- Opcode: IMPORT_FROM (namei)

     Loads the attribute ‘co_names[namei]’ from the module found in TOS.
     The resulting object is pushed onto the stack, to be subsequently
     stored by a *note STORE_FAST: 38e4. instruction.

 -- Opcode: JUMP_FORWARD (delta)

     Increments bytecode counter by `delta'.

 -- Opcode: POP_JUMP_IF_TRUE (target)

     If TOS is true, sets the bytecode counter to `target'.  TOS is
     popped.

     3.1 版新加入.

 -- Opcode: POP_JUMP_IF_FALSE (target)

     If TOS is false, sets the bytecode counter to `target'.  TOS is
     popped.

     3.1 版新加入.

 -- Opcode: JUMP_IF_TRUE_OR_POP (target)

     If TOS is true, sets the bytecode counter to `target' and leaves
     TOS on the stack.  Otherwise (TOS is false), TOS is popped.

     3.1 版新加入.

 -- Opcode: JUMP_IF_FALSE_OR_POP (target)

     If TOS is false, sets the bytecode counter to `target' and leaves
     TOS on the stack.  Otherwise (TOS is true), TOS is popped.

     3.1 版新加入.

 -- Opcode: JUMP_ABSOLUTE (target)

     Set bytecode counter to `target'.

 -- Opcode: FOR_ITER (delta)

     TOS is an *note iterator: 1040.  Call its *note __next__(): c69.
     method.  If this yields a new value, push it on the stack (leaving
     the iterator below it).  If the iterator indicates it is exhausted
     TOS is popped, and the byte code counter is incremented by `delta'.

 -- Opcode: LOAD_GLOBAL (namei)

     Loads the global named ‘co_names[namei]’ onto the stack.

 -- Opcode: SETUP_FINALLY (delta)

     Pushes a try block from a try-finally or try-except clause onto the
     block stack.  `delta' points to the finally block or the first
     except block.

 -- Opcode: CALL_FINALLY (delta)

     Pushes the address of the next instruction onto the stack and
     increments bytecode counter by `delta'.  Used for calling the
     finally block as a "subroutine".

     3.8 版新加入.

 -- Opcode: LOAD_FAST (var_num)

     Pushes a reference to the local ‘co_varnames[var_num]’ onto the
     stack.

 -- Opcode: STORE_FAST (var_num)

     Stores TOS into the local ‘co_varnames[var_num]’.

 -- Opcode: DELETE_FAST (var_num)

     Deletes local ‘co_varnames[var_num]’.

 -- Opcode: LOAD_CLOSURE (i)

     Pushes a reference to the cell contained in slot `i' of the cell
     and free variable storage.  The name of the variable is
     ‘co_cellvars[i]’ if `i' is less than the length of `co_cellvars'.
     Otherwise it is ‘co_freevars[i - len(co_cellvars)]’.

 -- Opcode: LOAD_DEREF (i)

     Loads the cell contained in slot `i' of the cell and free variable
     storage.  Pushes a reference to the object the cell contains on the
     stack.

 -- Opcode: LOAD_CLASSDEREF (i)

     Much like *note LOAD_DEREF: 3907. but first checks the locals
     dictionary before consulting the cell.  This is used for loading
     free variables in class bodies.

     3.4 版新加入.

 -- Opcode: STORE_DEREF (i)

     Stores TOS into the cell contained in slot `i' of the cell and free
     variable storage.

 -- Opcode: DELETE_DEREF (i)

     Empties the cell contained in slot `i' of the cell and free
     variable storage.  Used by the *note del: 1273. statement.

     3.2 版新加入.

 -- 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 TOS’ (raise exception instance or type at ‘TOS’)

        * 2: ‘raise TOS1 from TOS’ (raise exception instance or type at
          ‘TOS1’ with ‘__cause__’ set to ‘TOS’)

 -- Opcode: CALL_FUNCTION (argc)

     Calls a callable object with positional arguments.  `argc'
     indicates the number of positional arguments.  The top of the stack
     contains positional arguments, with the right-most argument on top.
     Below the arguments is a callable object to call.  ‘CALL_FUNCTION’
     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 版更變: This opcode is used only for calls with positional
     arguments.

 -- Opcode: CALL_FUNCTION_KW (argc)

     Calls a callable object with positional (if any) and keyword
     arguments.  `argc' indicates the total number of positional and
     keyword arguments.  The top element on the stack contains a tuple
     of keyword argument names.  Below that are keyword arguments in the
     order corresponding to the tuple.  Below that are positional
     arguments, with the right-most parameter on top.  Below the
     arguments is a callable object to call.  ‘CALL_FUNCTION_KW’ 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 版更變: Keyword arguments are packed in a tuple instead of a
     dictionary, `argc' indicates the total number of arguments.

 -- 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.  Below that is an iterable object containing positional
     arguments and a callable object to call.  *note
     BUILD_MAP_UNPACK_WITH_CALL: 620. and *note
     BUILD_TUPLE_UNPACK_WITH_CALL: 622. can be used for merging multiple
     mapping objects and iterables containing 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: LOAD_METHOD (namei)

     Loads a method named ‘co_names[namei]’ from the TOS object.  TOS is
     popped.  This bytecode distinguishes two cases: if TOS has a method
     with the correct name, the bytecode pushes the unbound method and
     TOS. TOS will be used as the first argument (‘self’) by *note
     CALL_METHOD: 4b3. when calling the unbound method.  Otherwise,
     ‘NULL’ and the object return by the attribute lookup are pushed.

     3.7 版新加入.

 -- Opcode: CALL_METHOD (argc)

     Calls a method.  `argc' is the number of positional arguments.
     Keyword arguments are not supported.  This opcode is designed to be
     used with *note LOAD_METHOD: 4b2.  Positional arguments are on top
     of the stack.  Below them, the two items described in *note
     LOAD_METHOD: 4b2. are on the stack (either ‘self’ and an unbound
     method object or ‘NULL’ and an arbitrary callable).  All of them
     are popped and the return value is pushed.

     3.7 版新加入.

 -- Opcode: MAKE_FUNCTION (flags)

     Pushes a new function object on the stack.  From bottom to top, the
     consumed stack must consist of values if the argument carries a
     specified flag value

        * ‘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’ an annotation dictionary

        * ‘0x08’ a tuple containing cells for free variables, making a
          closure

        * the code associated with the function (at TOS1)

        * the *note qualified name: 1430. of the function (at TOS)

 -- Opcode: BUILD_SLICE (argc)

     Pushes a slice object on the stack.  `argc' must be 2 or 3.  If it
     is 2, ‘slice(TOS1, TOS)’ is pushed; if it is 3, ‘slice(TOS2, TOS1,
     TOS)’ is pushed.  See the *note slice(): e09. 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: FORMAT_VALUE (flags)

     Used for implementing formatted literal strings (f-strings).  Pops
     an optional `fmt_spec' from the stack, then a required `value'.
     `flags' is interpreted as follows:

        * ‘(flags & 0x03) == 0x00’: `value' is formatted as-is.

        * ‘(flags & 0x03) == 0x01’: call *note str(): 335. on `value'
          before formatting it.

        * ‘(flags & 0x03) == 0x02’: call *note repr(): 7d1. on `value'
          before formatting it.

        * ‘(flags & 0x03) == 0x03’: call *note ascii(): d51. on `value'
          before formatting it.

        * ‘(flags & 0x04) == 0x04’: pop `fmt_spec' from the stack and
          use it, else use an empty `fmt_spec'.

     Formatting is performed using ‘PyObject_Format()’.  The result is
     pushed on the stack.

     3.6 版新加入.

 -- Opcode: HAVE_ARGUMENT

     This is not really an opcode.  It identifies the dividing line
     between opcodes which don’t use their argument and those that do
     (‘< HAVE_ARGUMENT’ and ‘>= HAVE_ARGUMENT’, respectively).

     3.6 版更變: Now every instruction has an argument, but opcodes ‘<
     HAVE_ARGUMENT’ ignore it.  Before, only opcodes ‘>= HAVE_ARGUMENT’
     had an argument.


File: python.info,  Node: Opcode collections,  Prev: Python Bytecode Instructions,  Up: dis --- Python bytecode的反組譯器

5.32.12.4 Opcode collections
............................

These collections are provided for automatic introspection of bytecode
instructions:

 -- Data: dis.opname

     Sequence of operation names, indexable using the bytecode.

 -- Data: dis.opmap

     Dictionary mapping operation names to bytecodes.

 -- Data: dis.cmp_op

     Sequence of all compare operation names.

 -- Data: dis.hasconst

     Sequence of bytecodes that access a constant.

 -- Data: dis.hasfree

     Sequence of bytecodes that access a free variable (note that ’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).

 -- Data: dis.hasname

     Sequence of bytecodes that access an attribute by name.

 -- Data: dis.hasjrel

     Sequence of bytecodes that have a relative jump target.

 -- Data: dis.hasjabs

     Sequence of bytecodes that have an absolute jump target.

 -- Data: dis.haslocal

     Sequence of bytecodes that access a local variable.

 -- Data: dis.hascompare

     Sequence of bytecodes of Boolean operations.


File: python.info,  Node: pickletools --- Tools for pickle developers,  Prev: dis --- Python bytecode的反組譯器,  Up: Python Language Services

5.32.13 ‘pickletools’ — Tools for pickle developers
---------------------------------------------------

`Source code:' Lib/pickletools.py(1)

__________________________________________________________________

This module contains various constants relating to the intimate details
of the *note pickle: cb. module, some lengthy comments about the
implementation, and a few useful functions for analyzing pickled data.
The contents of this module are useful for Python core developers who
are working on the *note pickle: cb.; ordinary users of the *note
pickle: cb. module probably won’t find the *note pickletools: cc. module
relevant.

* Menu:

* Command line usage: Command line usage<2>.
* Programmatic Interface: Programmatic Interface<2>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/pickletools.py


File: python.info,  Node: Command line usage<2>,  Next: Programmatic Interface<2>,  Up: pickletools --- Tools for pickle developers

5.32.13.1 Command line usage
............................

3.2 版新加入.

When invoked from the command line, ‘python -m pickletools’ will
disassemble the contents of one or more pickle files.  Note that if you
want to see the Python object stored in the pickle rather than the
details of pickle format, you may want to use ‘-m pickle’ instead.
However, when the pickle file that you want to examine comes from an
untrusted source, ‘-m pickletools’ is a safer option because it does not
execute pickle bytecode.

For example, with a tuple ‘(1, 2)’ pickled in file ‘x.pickle’:

     $ 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:

* Command line options: Command line options<3>.


File: python.info,  Node: Command line options<3>,  Up: Command line usage<2>

5.32.13.2 Command line options
..............................

 -- 程式選項: -a, --annotate

     Annotate each line with a short opcode description.

 -- 程式選項: -o, --output=<file>

     Name of a file where the output should be written.

 -- 程式選項: -l, --indentlevel=<num>

     The number of blanks by which to indent a new MARK level.

 -- 程式選項: -m, --memo

     When multiple objects are disassembled, preserve memo between
     disassemblies.

 -- 程式選項: -p, --preamble=<preamble>

     When more than one pickle file are specified, print given preamble
     before each disassembly.


File: python.info,  Node: Programmatic Interface<2>,  Prev: Command line usage<2>,  Up: pickletools --- Tools for pickle developers

5.32.13.3 Programmatic Interface
................................

 -- 函式: pickletools.dis (pickle, out=None, memo=None, indentlevel=4,
          annotate=0)

     Outputs a symbolic disassembly of the pickle to the file-like
     object `out', defaulting to ‘sys.stdout’.  `pickle' can be a string
     or a file-like object.  `memo' can be a Python dictionary that will
     be used as the pickle’s memo; it can be used to perform
     disassemblies across multiple pickles created by the same pickler.
     Successive levels, indicated by ‘MARK’ opcodes in the stream, are
     indented by `indentlevel' spaces.  If a nonzero value is given to
     `annotate', each opcode in the output is annotated with a short
     description.  The value of `annotate' is used as a hint for the
     column where annotation should start.

     3.2 版新加入: The `annotate' argument.

 -- 函式: pickletools.genops (pickle)

     Provides an *note iterator: 1040. over all of the opcodes in a
     pickle, returning a sequence of ‘(opcode, arg, pos)’ triples.
     `opcode' is an instance of an ‘OpcodeInfo’ class; `arg' is the
     decoded value, as a Python object, of the opcode’s argument; `pos'
     is the position at which this opcode is located.  `pickle' can be a
     string or a file-like object.

 -- 函式: pickletools.optimize (picklestring)

     Returns a new equivalent pickle string after eliminating unused
     ‘PUT’ opcodes.  The optimized pickle is shorter, takes less
     transmission time, requires less storage space, and unpickles more
     efficiently.


File: python.info,  Node: Miscellaneous Services,  Next: MS Windows Specific Services,  Prev: Python Language Services,  Up: Python 標準函式庫 Standard Library

5.33 Miscellaneous Services
===========================

The modules described in this chapter provide miscellaneous services
that are available in all Python versions.  Here’s an overview:

* Menu:

* formatter: formatter --- Generic output formatting. Generic output formatting


File: python.info,  Node: formatter --- Generic output formatting,  Up: Miscellaneous Services

5.33.1 ‘formatter’ — Generic output formatting
----------------------------------------------

3.4 版後已棄用: Due to lack of usage, the formatter module has been
deprecated.

__________________________________________________________________

This module supports two interface definitions, each with multiple
implementations: The `formatter' interface, and the `writer' interface
which is required by the formatter interface.

Formatter objects transform an abstract flow of formatting events into
specific output events on writer objects.  Formatters manage several
stack structures to allow various properties of a writer object to be
changed and restored; writers need not be able to handle relative
changes nor any sort of "change back" operation.  Specific writer
properties which may be controlled via formatter objects are horizontal
alignment, font, and left margin indentations.  A mechanism is provided
which supports providing arbitrary, non-exclusive style settings to a
writer as well.  Additional interfaces facilitate formatting events
which are not reversible, such as paragraph separation.

Writer objects encapsulate device interfaces.  Abstract devices, such as
file formats, are supported as well as physical devices.  The provided
implementations all work with abstract devices.  The interface makes
available mechanisms for setting the properties which formatter objects
manage and inserting data into the output.

* Menu:

* The Formatter Interface::
* Formatter Implementations::
* The Writer Interface::
* Writer Implementations::


File: python.info,  Node: The Formatter Interface,  Next: Formatter Implementations,  Up: formatter --- Generic output formatting

5.33.1.1 The Formatter Interface
................................

Interfaces to create formatters are dependent on the specific formatter
class being instantiated.  The interfaces described below are the
required interfaces which all formatters must support once initialized.

One data element is defined at the module level:

 -- Data: formatter.AS_IS

     Value which can be used in the font specification passed to the
     ‘push_font()’ method described below, or as the new value to any
     other ‘push_property()’ method.  Pushing the ‘AS_IS’ value allows
     the corresponding ‘pop_property()’ method to be called without
     having to track whether the property was changed.

The following attributes are defined for formatter instance objects:

 -- 屬性: formatter.writer

     The writer instance with which the formatter interacts.

 -- 成員函式: formatter.end_paragraph (blanklines)

     Close any open paragraphs and insert at least `blanklines' before
     the next paragraph.

 -- 成員函式: formatter.add_line_break ()

     Add a hard line break if one does not already exist.  This does not
     break the logical paragraph.

 -- 成員函式: formatter.add_hor_rule (*args, **kw)

     Insert a horizontal rule in the output.  A hard break is inserted
     if there is data in the current paragraph, but the logical
     paragraph is not broken.  The arguments and keywords are passed on
     to the writer’s ‘send_line_break()’ method.

 -- 成員函式: formatter.add_flowing_data (data)

     Provide data which should be formatted with collapsed whitespace.
     Whitespace from preceding and successive calls to *note
     add_flowing_data(): 3930. is considered as well when the whitespace
     collapse is performed.  The data which is passed to this method is
     expected to be word-wrapped by the output device.  Note that any
     word-wrapping still must be performed by the writer object due to
     the need to rely on device and font information.

 -- 成員函式: formatter.add_literal_data (data)

     Provide data which should be passed to the writer unchanged.
     Whitespace, including newline and tab characters, are considered
     legal in the value of `data'.

 -- 成員函式: formatter.add_label_data (format, counter)

     Insert a label which should be placed to the left of the current
     left margin.  This should be used for constructing bulleted or
     numbered lists.  If the `format' value is a string, it is
     interpreted as a format specification for `counter', which should
     be an integer.  The result of this formatting becomes the value of
     the label; if `format' is not a string it is used as the label
     value directly.  The label value is passed as the only argument to
     the writer’s ‘send_label_data()’ method.  Interpretation of
     non-string label values is dependent on the associated writer.

     Format specifications are strings which, in combination with a
     counter value, are used to compute label values.  Each character in
     the format string is copied to the label value, with some
     characters recognized to indicate a transform on the counter value.
     Specifically, the character ‘'1'’ represents the counter value
     formatter as an Arabic number, the characters ‘'A'’ and ‘'a'’
     represent alphabetic representations of the counter value in upper
     and lower case, respectively, and ‘'I'’ and ‘'i'’ represent the
     counter value in Roman numerals, in upper and lower case.  Note
     that the alphabetic and roman transforms require that the counter
     value be greater than zero.

 -- 成員函式: formatter.flush_softspace ()

     Send any pending whitespace buffered from a previous call to *note
     add_flowing_data(): 3930. to the associated writer object.  This
     should be called before any direct manipulation of the writer
     object.

 -- 成員函式: formatter.push_alignment (align)

     Push a new alignment setting onto the alignment stack.  This may be
     *note AS_IS: 392b. if no change is desired.  If the alignment value
     is changed from the previous setting, the writer’s
     ‘new_alignment()’ method is called with the `align' value.

 -- 成員函式: formatter.pop_alignment ()

     Restore the previous alignment.

 -- 成員函式: formatter.push_font ((size, italic, bold, teletype))

     Change some or all font properties of the writer object.
     Properties which are not set to *note AS_IS: 392b. are set to the
     values passed in while others are maintained at their current
     settings.  The writer’s ‘new_font()’ method is called with the
     fully resolved font specification.

 -- 成員函式: formatter.pop_font ()

     Restore the previous font.

 -- 成員函式: formatter.push_margin (margin)

     Increase the number of left margin indentations by one, associating
     the logical tag `margin' with the new indentation.  The initial
     margin level is ‘0’.  Changed values of the logical tag must be
     true values; false values other than *note AS_IS: 392b. are not
     sufficient to change the margin.

 -- 成員函式: formatter.pop_margin ()

     Restore the previous margin.

 -- 成員函式: formatter.push_style (*styles)

     Push any number of arbitrary style specifications.  All styles are
     pushed onto the styles stack in order.  A tuple representing the
     entire stack, including *note AS_IS: 392b. values, is passed to the
     writer’s ‘new_styles()’ method.

 -- 成員函式: formatter.pop_style (n=1)

     Pop the last `n' style specifications passed to *note push_style():
     393a.  A tuple representing the revised stack, including *note
     AS_IS: 392b. values, is passed to the writer’s ‘new_styles()’
     method.

 -- 成員函式: formatter.set_spacing (spacing)

     Set the spacing style for the writer.

 -- 成員函式: formatter.assert_line_data (flag=1)

     Inform the formatter that data has been added to the current
     paragraph out-of-band.  This should be used when the writer has
     been manipulated directly.  The optional `flag' argument can be set
     to false if the writer manipulations produced a hard line break at
     the end of the output.


File: python.info,  Node: Formatter Implementations,  Next: The Writer Interface,  Prev: The Formatter Interface,  Up: formatter --- Generic output formatting

5.33.1.2 Formatter Implementations
..................................

Two implementations of formatter objects are provided by this module.
Most applications may use one of these classes without modification or
subclassing.

 -- 類別: formatter.NullFormatter (writer=None)

     A formatter which does nothing.  If `writer' is omitted, a *note
     NullWriter: 3941. instance is created.  No methods of the writer
     are called by *note NullFormatter: 3940. instances.
     Implementations should inherit from this class if implementing a
     writer interface but don’t need to inherit any implementation.

 -- 類別: formatter.AbstractFormatter (writer)

     The standard formatter.  This implementation has demonstrated wide
     applicability to many writers, and may be used directly in most
     circumstances.  It has been used to implement a full-featured World
     Wide Web browser.


File: python.info,  Node: The Writer Interface,  Next: Writer Implementations,  Prev: Formatter Implementations,  Up: formatter --- Generic output formatting

5.33.1.3 The Writer Interface
.............................

Interfaces to create writers are dependent on the specific writer class
being instantiated.  The interfaces described below are the required
interfaces which all writers must support once initialized.  Note that
while most applications can use the *note AbstractFormatter: 3942. class
as a formatter, the writer must typically be provided by the
application.

 -- 成員函式: writer.flush ()

     Flush any buffered output or device control events.

 -- 成員函式: writer.new_alignment (align)

     Set the alignment style.  The `align' value can be any object, but
     by convention is a string or ‘None’, where ‘None’ indicates that
     the writer’s "preferred" alignment should be used.  Conventional
     `align' values are ‘'left'’, ‘'center'’, ‘'right'’, and
     ‘'justify'’.

 -- 成員函式: writer.new_font (font)

     Set the font style.  The value of `font' will be ‘None’, indicating
     that the device’s default font should be used, or a tuple of the
     form ‘(size, italic, bold, teletype)’.  Size will be a string
     indicating the size of font that should be used; specific strings
     and their interpretation must be defined by the application.  The
     `italic', `bold', and `teletype' values are Boolean values
     specifying which of those font attributes should be used.

 -- 成員函式: writer.new_margin (margin, level)

     Set the margin level to the integer `level' and the logical tag to
     `margin'.  Interpretation of the logical tag is at the writer’s
     discretion; the only restriction on the value of the logical tag is
     that it not be a false value for non-zero values of `level'.

 -- 成員函式: writer.new_spacing (spacing)

     Set the spacing style to `spacing'.

 -- 成員函式: writer.new_styles (styles)

     Set additional styles.  The `styles' value is a tuple of arbitrary
     values; the value *note AS_IS: 392b. should be ignored.  The
     `styles' tuple may be interpreted either as a set or as a stack
     depending on the requirements of the application and writer
     implementation.

 -- 成員函式: writer.send_line_break ()

     Break the current line.

 -- 成員函式: writer.send_paragraph (blankline)

     Produce a paragraph separation of at least `blankline' blank lines,
     or the equivalent.  The `blankline' value will be an integer.  Note
     that the implementation will receive a call to *note
     send_line_break(): 394b. before this call if a line break is
     needed; this method should not include ending the last line of the
     paragraph.  It is only responsible for vertical spacing between
     paragraphs.

 -- 成員函式: writer.send_hor_rule (*args, **kw)

     Display a horizontal rule on the output device.  The arguments to
     this method are entirely application- and writer-specific, and
     should be interpreted with care.  The method implementation may
     assume that a line break has already been issued via *note
     send_line_break(): 394b.

 -- 成員函式: writer.send_flowing_data (data)

     Output character data which may be word-wrapped and re-flowed as
     needed.  Within any sequence of calls to this method, the writer
     may assume that spans of multiple whitespace characters have been
     collapsed to single space characters.

 -- 成員函式: writer.send_literal_data (data)

     Output character data which has already been formatted for display.
     Generally, this should be interpreted to mean that line breaks
     indicated by newline characters should be preserved and no new line
     breaks should be introduced.  The data may contain embedded newline
     and tab characters, unlike data provided to the
     ‘send_formatted_data()’ interface.

 -- 成員函式: writer.send_label_data (data)

     Set `data' to the left of the current left margin, if possible.
     The value of `data' is not restricted; treatment of non-string
     values is entirely application- and writer-dependent.  This method
     will only be called at the beginning of a line.


File: python.info,  Node: Writer Implementations,  Prev: The Writer Interface,  Up: formatter --- Generic output formatting

5.33.1.4 Writer Implementations
...............................

Three implementations of the writer object interface are provided as
examples by this module.  Most applications will need to derive new
writer classes from the *note NullWriter: 3941. class.

 -- 類別: formatter.NullWriter

     A writer which only provides the interface definition; no actions
     are taken on any methods.  This should be the base class for all
     writers which do not need to inherit any implementation methods.

 -- 類別: formatter.AbstractWriter

     A writer which can be used in debugging formatters, but not much
     else.  Each method simply announces itself by printing its name and
     arguments on standard output.

 -- 類別: formatter.DumbWriter (file=None, maxcol=72)

     Simple writer class which writes output on the *note file object:
     b47. passed in as `file' or, if `file' is omitted, on standard
     output.  The output is simply word-wrapped to the number of columns
     specified by `maxcol'.  This class is suitable for reflowing a
     sequence of paragraphs.


File: python.info,  Node: MS Windows Specific Services,  Next: Unix Specific Services,  Prev: Miscellaneous Services,  Up: Python 標準函式庫 Standard Library

5.34 MS Windows Specific Services
=================================

This chapter describes modules that are only available on MS Windows
platforms.

* Menu:

* msilib: msilib --- Read and write Microsoft Installer files. Read and write Microsoft Installer files
* msvcrt: msvcrt --- Useful routines from the MS VC++ runtime. Useful routines from the MS VC++ runtime
* winreg: winreg --- Windows registry access. Windows registry access
* winsound: winsound --- Sound-playing interface for Windows. Sound-playing interface for Windows


File: python.info,  Node: msilib --- Read and write Microsoft Installer files,  Next: msvcrt --- Useful routines from the MS VC++ runtime,  Up: MS Windows Specific Services

5.34.1 ‘msilib’ — Read and write Microsoft Installer files
----------------------------------------------------------

`Source code:' Lib/msilib/__init__.py(1)

__________________________________________________________________

The *note msilib: b6. supports the creation of Microsoft Installer
(‘.msi’) files.  Because these files often contain an embedded "cabinet"
file (‘.cab’), it also exposes an API to create CAB files.  Support for
reading ‘.cab’ files is currently not implemented; read support for the
‘.msi’ database is possible.

This package aims to provide complete access to all tables in an ‘.msi’
file, therefore, it is a fairly low-level API. Two primary applications
of this package are the *note distutils: 39. command ‘bdist_msi’, and
the creation of Python installer package itself (although that currently
uses a different version of ‘msilib’).

The package contents can be roughly split into four parts: low-level CAB
routines, low-level MSI routines, higher-level MSI routines, and
standard table structures.

 -- 函式: msilib.FCICreate (cabname, files)

     Create a new CAB file named `cabname'.  `files' must be a list of
     tuples, each containing the name of the file on disk, and the name
     of the file inside the CAB file.

     The files are added to the CAB file in the order they appear in the
     list.  All files are added into a single CAB file, using the MSZIP
     compression algorithm.

     Callbacks to Python for the various steps of MSI creation are
     currently not exposed.

 -- 函式: msilib.UuidCreate ()

     Return the string representation of a new unique identifier.  This
     wraps the Windows API functions ‘UuidCreate()’ and
     ‘UuidToString()’.

 -- 函式: msilib.OpenDatabase (path, persist)

     Return a new database object by calling MsiOpenDatabase.  `path' is
     the file name of the MSI file; `persist' can be one of the
     constants ‘MSIDBOPEN_CREATEDIRECT’, ‘MSIDBOPEN_CREATE’,
     ‘MSIDBOPEN_DIRECT’, ‘MSIDBOPEN_READONLY’, or ‘MSIDBOPEN_TRANSACT’,
     and may include the flag ‘MSIDBOPEN_PATCHFILE’.  See the Microsoft
     documentation for the meaning of these flags; depending on the
     flags, an existing database is opened, or a new one created.

 -- 函式: msilib.CreateRecord (count)

     Return a new record object by calling ‘MSICreateRecord()’.  `count'
     is the number of fields of the record.

 -- 函式: msilib.init_database (name, schema, ProductName, ProductCode,
          ProductVersion, Manufacturer)

     Create and return a new database `name', initialize it with
     `schema', and set the properties `ProductName', `ProductCode',
     `ProductVersion', and `Manufacturer'.

     `schema' must be a module object containing ‘tables’ and
     ‘_Validation_records’ attributes; typically, *note msilib.schema:
     395c. should be used.

     The database will contain just the schema and the validation
     records when this function returns.

 -- 函式: msilib.add_data (database, table, records)

     Add all `records' to the table named `table' in `database'.

     The `table' argument must be one of the predefined tables in the
     MSI schema, e.g.  ‘'Feature'’, ‘'File'’, ‘'Component'’, ‘'Dialog'’,
     ‘'Control'’, etc.

     `records' should be a list of tuples, each one containing all
     fields of a record according to the schema of the table.  For
     optional fields, ‘None’ can be passed.

     Field values can be ints, strings, or instances of the Binary
     class.

 -- 類別: msilib.Binary (filename)

     Represents entries in the Binary table; inserting such an object
     using *note add_data(): 395d. reads the file named `filename' into
     the table.

 -- 函式: msilib.add_tables (database, module)

     Add all table content from `module' to `database'.  `module' must
     contain an attribute `tables' listing all tables for which content
     should be added, and one attribute per table that has the actual
     content.

     This is typically used to install the sequence tables.

 -- 函式: msilib.add_stream (database, name, path)

     Add the file `path' into the ‘_Stream’ table of `database', with
     the stream name `name'.

 -- 函式: msilib.gen_uuid ()

     Return a new UUID, in the format that MSI typically requires (i.e.
     in curly braces, and with all hexdigits in upper-case).

也參考
......

FCICreate(2) UuidCreate(3) UuidToString(4)

* Menu:

* Database Objects::
* View Objects::
* Summary Information Objects::
* Record Objects::
* Errors::
* CAB Objects::
* Directory Objects::
* Features: Features<3>.
* GUI classes::
* Precomputed tables::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/msilib/__init__.py

   (2) https://msdn.microsoft.com/en-us/library/bb432265.aspx

   (3) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa379205.aspx

   (4) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa379352.aspx


File: python.info,  Node: Database Objects,  Next: View Objects,  Up: msilib --- Read and write Microsoft Installer files

5.34.1.1 Database Objects
.........................

 -- 成員函式: Database.OpenView (sql)

     Return a view object, by calling ‘MSIDatabaseOpenView()’.  `sql' is
     the SQL statement to execute.

 -- 成員函式: Database.Commit ()

     Commit the changes pending in the current transaction, by calling
     ‘MSIDatabaseCommit()’.

 -- 成員函式: Database.GetSummaryInformation (count)

     Return a new summary information object, by calling
     ‘MsiGetSummaryInformation()’.  `count' is the maximum number of
     updated values.

 -- 成員函式: Database.Close ()

     Close the database object, through ‘MsiCloseHandle()’.

     3.7 版新加入.

也參考
......

MSIDatabaseOpenView(1) MSIDatabaseCommit(2) MSIGetSummaryInformation(3)
MsiCloseHandle(4)

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370082.aspx

   (2) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370075.aspx

   (3) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370301.aspx

   (4) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370067.aspx


File: python.info,  Node: View Objects,  Next: Summary Information Objects,  Prev: Database Objects,  Up: msilib --- Read and write Microsoft Installer files

5.34.1.2 View Objects
.....................

 -- 成員函式: View.Execute (params)

     Execute the SQL query of the view, through ‘MSIViewExecute()’.  If
     `params' is not ‘None’, it is a record describing actual values of
     the parameter tokens in the query.

 -- 成員函式: View.GetColumnInfo (kind)

     Return a record describing the columns of the view, through calling
     ‘MsiViewGetColumnInfo()’.  `kind' can be either ‘MSICOLINFO_NAMES’
     or ‘MSICOLINFO_TYPES’.

 -- 成員函式: View.Fetch ()

     Return a result record of the query, through calling
     ‘MsiViewFetch()’.

 -- 成員函式: View.Modify (kind, data)

     Modify the view, by calling ‘MsiViewModify()’.  `kind' can be one
     of ‘MSIMODIFY_SEEK’, ‘MSIMODIFY_REFRESH’, ‘MSIMODIFY_INSERT’,
     ‘MSIMODIFY_UPDATE’, ‘MSIMODIFY_ASSIGN’, ‘MSIMODIFY_REPLACE’,
     ‘MSIMODIFY_MERGE’, ‘MSIMODIFY_DELETE’,
     ‘MSIMODIFY_INSERT_TEMPORARY’, ‘MSIMODIFY_VALIDATE’,
     ‘MSIMODIFY_VALIDATE_NEW’, ‘MSIMODIFY_VALIDATE_FIELD’, or
     ‘MSIMODIFY_VALIDATE_DELETE’.

     `data' must be a record describing the new data.

 -- 成員函式: View.Close ()

     Close the view, through ‘MsiViewClose()’.

也參考
......

MsiViewExecute(1) MSIViewGetColumnInfo(2) MsiViewFetch(3)
MsiViewModify(4) MsiViewClose(5)

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370513.aspx

   (2) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370516.aspx

   (3) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370514.aspx

   (4) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370519.aspx

   (5) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370510.aspx


File: python.info,  Node: Summary Information Objects,  Next: Record Objects,  Prev: View Objects,  Up: msilib --- Read and write Microsoft Installer files

5.34.1.3 Summary Information Objects
....................................

 -- 成員函式: SummaryInformation.GetProperty (field)

     Return a property of the summary, through
     ‘MsiSummaryInfoGetProperty()’.  `field' is the name of the
     property, and can be one of the constants ‘PID_CODEPAGE’,
     ‘PID_TITLE’, ‘PID_SUBJECT’, ‘PID_AUTHOR’, ‘PID_KEYWORDS’,
     ‘PID_COMMENTS’, ‘PID_TEMPLATE’, ‘PID_LASTAUTHOR’, ‘PID_REVNUMBER’,
     ‘PID_LASTPRINTED’, ‘PID_CREATE_DTM’, ‘PID_LASTSAVE_DTM’,
     ‘PID_PAGECOUNT’, ‘PID_WORDCOUNT’, ‘PID_CHARCOUNT’, ‘PID_APPNAME’,
     or ‘PID_SECURITY’.

 -- 成員函式: SummaryInformation.GetPropertyCount ()

     Return the number of summary properties, through
     ‘MsiSummaryInfoGetPropertyCount()’.

 -- 成員函式: SummaryInformation.SetProperty (field, value)

     Set a property through ‘MsiSummaryInfoSetProperty()’.  `field' can
     have the same values as in *note GetProperty(): fc8, `value' is the
     new value of the property.  Possible value types are integer and
     string.

 -- 成員函式: SummaryInformation.Persist ()

     Write the modified properties to the summary information stream,
     using ‘MsiSummaryInfoPersist()’.

也參考
......

MsiSummaryInfoGetProperty(1) MsiSummaryInfoGetPropertyCount(2)
MsiSummaryInfoSetProperty(3) MsiSummaryInfoPersist(4)

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370409.aspx

   (2) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370488.aspx

   (3) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370491.aspx

   (4) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370490.aspx


File: python.info,  Node: Record Objects,  Next: Errors,  Prev: Summary Information Objects,  Up: msilib --- Read and write Microsoft Installer files

5.34.1.4 Record Objects
.......................

 -- 成員函式: Record.GetFieldCount ()

     Return the number of fields of the record, through
     ‘MsiRecordGetFieldCount()’.

 -- 成員函式: Record.GetInteger (field)

     Return the value of `field' as an integer where possible.  `field'
     must be an integer.

 -- 成員函式: Record.GetString (field)

     Return the value of `field' as a string where possible.  `field'
     must be an integer.

 -- 成員函式: Record.SetString (field, value)

     Set `field' to `value' through ‘MsiRecordSetString()’.  `field'
     must be an integer; `value' a string.

 -- 成員函式: Record.SetStream (field, value)

     Set `field' to the contents of the file named `value', through
     ‘MsiRecordSetStream()’.  `field' must be an integer; `value' a
     string.

 -- 成員函式: Record.SetInteger (field, value)

     Set `field' to `value' through ‘MsiRecordSetInteger()’.  Both
     `field' and `value' must be an integer.

 -- 成員函式: Record.ClearData ()

     Set all fields of the record to 0, through ‘MsiRecordClearData()’.

也參考
......

MsiRecordGetFieldCount(1) MsiRecordSetString(2) MsiRecordSetStream(3)
MsiRecordSetInteger(4) MsiRecordClearData(5)

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370366.aspx

   (2) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370373.aspx

   (3) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370372.aspx

   (4) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370371.aspx

   (5) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370364.aspx


File: python.info,  Node: Errors,  Next: CAB Objects,  Prev: Record Objects,  Up: msilib --- Read and write Microsoft Installer files

5.34.1.5 Errors
...............

All wrappers around MSI functions raise ‘MSIError’; the string inside
the exception will contain more detail.


File: python.info,  Node: CAB Objects,  Next: Directory Objects,  Prev: Errors,  Up: msilib --- Read and write Microsoft Installer files

5.34.1.6 CAB Objects
....................

 -- 類別: msilib.CAB (name)

     The class *note CAB: 397f. represents a CAB file.  During MSI
     construction, files will be added simultaneously to the ‘Files’
     table, and to a CAB file.  Then, when all files have been added,
     the CAB file can be written, then added to the MSI file.

     `name' is the name of the CAB file in the MSI file.

      -- 成員函式: append (full, file, logical)

          Add the file with the pathname `full' to the CAB file, under
          the name `logical'.  If there is already a file named
          `logical', a new file name is created.

          Return the index of the file in the CAB file, and the new name
          of the file inside the CAB file.

      -- 成員函式: commit (database)

          Generate a CAB file, add it as a stream to the MSI file, put
          it into the ‘Media’ table, and remove the generated file from
          the disk.


File: python.info,  Node: Directory Objects,  Next: Features<3>,  Prev: CAB Objects,  Up: msilib --- Read and write Microsoft Installer files

5.34.1.7 Directory Objects
..........................

 -- 類別: msilib.Directory (database, cab, basedir, physical, logical,
          default[, componentflags])

     Create a new directory in the Directory table.  There is a current
     component at each point in time for the directory, which is either
     explicitly created through *note start_component(): fc9, or
     implicitly when files are added for the first time.  Files are
     added into the current component, and into the cab file.  To create
     a directory, a base directory object needs to be specified (can be
     ‘None’), the path to the physical directory, and a logical
     directory name.  `default' specifies the DefaultDir slot in the
     directory table.  `componentflags' specifies the default flags that
     new components get.

      -- 成員函式: start_component (component=None, feature=None,
               flags=None, keyfile=None, uuid=None)

          Add an entry to the Component table, and make this component
          the current component for this directory.  If no component
          name is given, the directory name is used.  If no `feature' is
          given, the current feature is used.  If no `flags' are given,
          the directory’s default flags are used.  If no `keyfile' is
          given, the KeyPath is left null in the Component table.

      -- 成員函式: add_file (file, src=None, version=None,
               language=None)

          Add a file to the current component of the directory, starting
          a new one if there is no current component.  By default, the
          file name in the source and the file table will be identical.
          If the `src' file is specified, it is interpreted relative to
          the current directory.  Optionally, a `version' and a
          `language' can be specified for the entry in the File table.

      -- 成員函式: glob (pattern, exclude=None)

          Add a list of files to the current component as specified in
          the glob pattern.  Individual files can be excluded in the
          `exclude' list.

      -- 成員函式: remove_pyc ()

          Remove ‘.pyc’ files on uninstall.

也參考
......

Directory Table(1) File Table(2) Component Table(3) FeatureComponents
Table(4)

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368295.aspx

   (2) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368596.aspx

   (3) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368007.aspx

   (4) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368579.aspx


File: python.info,  Node: Features<3>,  Next: GUI classes,  Prev: Directory Objects,  Up: msilib --- Read and write Microsoft Installer files

5.34.1.8 Features
.................

 -- 類別: msilib.Feature (db, id, title, desc, display, level=1,
          parent=None, directory=None, attributes=0)

     Add a new record to the ‘Feature’ table, using the values `id',
     `parent.id', `title', `desc', `display', `level', `directory', and
     `attributes'.  The resulting feature object can be passed to the
     ‘start_component()’ method of *note Directory: 3984.

      -- 成員函式: set_current ()

          Make this feature the current feature of *note msilib: b6.
          New components are automatically added to the default feature,
          unless a feature is explicitly specified.

也參考
......

Feature Table(1)

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368585.aspx


File: python.info,  Node: GUI classes,  Next: Precomputed tables,  Prev: Features<3>,  Up: msilib --- Read and write Microsoft Installer files

5.34.1.9 GUI classes
....................

*note msilib: b6. provides several classes that wrap the GUI tables in
an MSI database.  However, no standard user interface is provided; use
*note bdist_msi: 41. to create MSI files with a user-interface for
installing Python packages.

 -- 類別: msilib.Control (dlg, name)

     Base class of the dialog controls.  `dlg' is the dialog object the
     control belongs to, and `name' is the control’s name.

      -- 成員函式: event (event, argument, condition=1, ordering=None)

          Make an entry into the ‘ControlEvent’ table for this control.

      -- 成員函式: mapping (event, attribute)

          Make an entry into the ‘EventMapping’ table for this control.

      -- 成員函式: condition (action, condition)

          Make an entry into the ‘ControlCondition’ table for this
          control.

 -- 類別: msilib.RadioButtonGroup (dlg, name, property)

     Create a radio button control named `name'.  `property' is the
     installer property that gets set when a radio button is selected.

      -- 成員函式: add (name, x, y, width, height, text, value=None)

          Add a radio button named `name' to the group, at the
          coordinates `x', `y', `width', `height', and with the label
          `text'.  If `value' is ‘None’, it defaults to `name'.

 -- 類別: msilib.Dialog (db, name, x, y, w, h, attr, title, first,
          default, cancel)

     Return a new *note Dialog: 3994. object.  An entry in the ‘Dialog’
     table is made, with the specified coordinates, dialog attributes,
     title, name of the first, default, and cancel controls.

      -- 成員函式: control (name, type, x, y, width, height, attributes,
               property, text, control_next, help)

          Return a new *note Control: 398e. object.  An entry in the
          ‘Control’ table is made with the specified parameters.

          This is a generic method; for specific types, specialized
          methods are provided.

      -- 成員函式: text (name, x, y, width, height, attributes, text)

          Add and return a ‘Text’ control.

      -- 成員函式: bitmap (name, x, y, width, height, text)

          Add and return a ‘Bitmap’ control.

      -- 成員函式: line (name, x, y, width, height)

          Add and return a ‘Line’ control.

      -- 成員函式: pushbutton (name, x, y, width, height, attributes,
               text, next_control)

          Add and return a ‘PushButton’ control.

      -- 成員函式: radiogroup (name, x, y, width, height, attributes,
               property, text, next_control)

          Add and return a ‘RadioButtonGroup’ control.

      -- 成員函式: checkbox (name, x, y, width, height, attributes,
               property, text, next_control)

          Add and return a ‘CheckBox’ control.

也參考
......

Dialog Table(1) Control Table(2) Control Types(3) ControlCondition
Table(4) ControlEvent Table(5) EventMapping Table(6) RadioButton
Table(7)

   ---------- Footnotes ----------

   (1) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368286.aspx

   (2) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368044.aspx

   (3) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368039.aspx

   (4) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368035.aspx

   (5) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368037.aspx

   (6) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa368559.aspx

   (7) 
https://msdn.microsoft.com/en-us/library/windows/desktop/aa370962.aspx


File: python.info,  Node: Precomputed tables,  Prev: GUI classes,  Up: msilib --- Read and write Microsoft Installer files

5.34.1.10 Precomputed tables
............................

*note msilib: b6. provides a few subpackages that contain only schema
and table definitions.  Currently, these definitions are based on MSI
version 2.0.

 -- Data: msilib.schema

     This is the standard MSI schema for MSI 2.0, with the `tables'
     variable providing a list of table definitions, and
     `_Validation_records' providing the data for MSI validation.

 -- Data: msilib.sequence

     This module contains table contents for the standard sequence
     tables: `AdminExecuteSequence', `AdminUISequence',
     `AdvtExecuteSequence', `InstallExecuteSequence', and
     `InstallUISequence'.

 -- Data: msilib.text

     This module contains definitions for the UIText and ActionText
     tables, for the standard installer actions.


File: python.info,  Node: msvcrt --- Useful routines from the MS VC++ runtime,  Next: winreg --- Windows registry access,  Prev: msilib --- Read and write Microsoft Installer files,  Up: MS Windows Specific Services

5.34.2 ‘msvcrt’ — Useful routines from the 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: 88. module uses this in the implementation of the *note
getpass(): 88. 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: 1d4.
where *note IOError: 997. was raised.

* Menu:

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


File: python.info,  Node: File Operations,  Next: Console I/O,  Up: msvcrt --- Useful routines from the MS VC++ runtime

5.34.2.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: 1d4. 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.

     Raises an *note auditing event: e96. ‘msvcrt.locking’ with
     arguments ‘fd’, ‘mode’, ‘nbytes’.

 -- Data: msvcrt.LK_LOCK
 -- Data: 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: 1d4. is
     raised.

 -- Data: msvcrt.LK_NBLCK
 -- Data: msvcrt.LK_NBRLCK

     Locks the specified bytes.  If the bytes cannot be locked, *note
     OSError: 1d4. is raised.

 -- Data: 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: 1f2d.; for
     binary, it should be *note os.O_BINARY: 1f1e.

 -- 函式: 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:
     1f20, *note os.O_RDONLY: 1f1c, and *note os.O_TEXT: 1f2d.  The
     returned file descriptor may be used as a parameter to *note
     os.fdopen(): 1436. to create a file object.

     Raises an *note auditing event: e96. ‘msvcrt.open_osfhandle’ with
     arguments ‘handle’, ‘flags’.

 -- 函式: msvcrt.get_osfhandle (fd)

     Return the file handle for the file descriptor `fd'.  Raises *note
     OSError: 1d4. if `fd' is not recognized.

     Raises an *note auditing event: e96. ‘msvcrt.get_osfhandle’ with
     argument ‘fd’.


File: python.info,  Node: Console I/O,  Next: Other Functions,  Prev: File Operations,  Up: msvcrt --- Useful routines from the MS VC++ runtime

5.34.2.2 Console I/O
....................

 -- 函式: msvcrt.kbhit ()

     Return ‘True’ if a keypress is waiting to be read.

 -- 函式: 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(): 39ad, returning a Unicode
     value.

 -- 函式: msvcrt.getche ()

     Similar to *note getch(): 39ad, but the keypress will be echoed if
     it represents a printable character.

 -- 函式: msvcrt.getwche ()

     Wide char variant of *note getche(): 39af, 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(): 39b1, 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(): 39ad.
     or *note getche(): 39af.

 -- 函式: msvcrt.ungetwch (unicode_char)

     Wide char variant of *note ungetch(): 39b3, accepting a Unicode
     value.


File: python.info,  Node: Other Functions,  Prev: Console I/O,  Up: msvcrt --- Useful routines from the MS VC++ runtime

5.34.2.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: 1d4.


File: python.info,  Node: winreg --- Windows registry access,  Next: winsound --- Sound-playing interface for Windows,  Prev: msvcrt --- Useful routines from the MS VC++ runtime,  Up: MS Windows Specific Services

5.34.3 ‘winreg’ — Windows registry access
-----------------------------------------

__________________________________________________________________

These functions expose the Windows registry API to Python.  Instead of
using an integer as the registry handle, a *note handle object: 39ba. 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: 999, which is now an alias of *note OSError: 1d4.

* Menu:

* Functions: Functions<11>.
* Constants: Constants<10>.
* Registry Handle Objects::


File: python.info,  Node: Functions<11>,  Next: Constants<10>,  Up: winreg --- Windows registry access

5.34.3.1 Functions
..................

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(): 39bf.), 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: 39ba.

     `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: 1d4. exception is raised.

     Raises an *note auditing event: e96. ‘winreg.ConnectRegistry’ with
     arguments ‘computer_name’, ‘key’.

     3.3 版更變: See *note above: 39bb.

 -- 函式: winreg.CreateKey (key, sub_key)

     Creates or opens the specified key, returning a *note handle
     object: 39ba.

     `key' is an already open key, or one of the predefined *note HKEY_*
     constants: 39c0.

     `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: 1d4. exception is raised.

     Raises an *note auditing event: e96. ‘winreg.CreateKey’ with
     arguments ‘key’, ‘sub_key’, ‘access’.

     Raises an *note auditing event: e96. ‘winreg.OpenKey/result’ with
     argument ‘key’.

     3.3 版更變: See *note above: 39bb.

 -- 函式: winreg.CreateKeyEx (key, sub_key, reserved=0,
          access=KEY_WRITE)

     Creates or opens the specified key, returning a *note handle
     object: 39ba.

     `key' is an already open key, or one of the predefined *note HKEY_*
     constants: 39c0.

     `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: 39c1.  See *note Access Rights: 39c2. 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: 1d4. exception is raised.

     Raises an *note auditing event: e96. ‘winreg.CreateKey’ with
     arguments ‘key’, ‘sub_key’, ‘access’.

     Raises an *note auditing event: e96. ‘winreg.OpenKey/result’ with
     argument ‘key’.

     3.2 版新加入.

     3.3 版更變: See *note above: 39bb.

 -- 函式: winreg.DeleteKey (key, sub_key)

     Deletes the specified key.

     `key' is an already open key, or one of the predefined *note HKEY_*
     constants: 39c0.

     `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: 1d4.
     exception is raised.

     Raises an *note auditing event: e96. ‘winreg.DeleteKey’ with
     arguments ‘key’, ‘sub_key’, ‘access’.

     3.3 版更變: See *note above: 39bb.

 -- 函式: winreg.DeleteKeyEx (key, sub_key, access=KEY_WOW64_64KEY,
          reserved=0)

     Deletes the specified key.

          備註: The *note DeleteKeyEx(): 34da. function is implemented
          with the RegDeleteKeyEx Windows API function, which is
          specific to 64-bit versions of Windows.  See the
          RegDeleteKeyEx documentation(1).

     `key' is an already open key, or one of the predefined *note HKEY_*
     constants: 39c0.

     `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: 39c3.  See *note Access Rights: 39c2. 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: 1d4.
     exception is raised.

     On unsupported Windows versions, *note NotImplementedError: 613. is
     raised.

     Raises an *note auditing event: e96. ‘winreg.DeleteKey’ with
     arguments ‘key’, ‘sub_key’, ‘access’.

     3.2 版新加入.

     3.3 版更變: See *note above: 39bb.

 -- 函式: 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: 39c0.

     `value' is a string that identifies the value to remove.

     Raises an *note auditing event: e96. ‘winreg.DeleteValue’ with
     arguments ‘key’, ‘value’.

 -- 函式: 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: 39c0.

     `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:
     1d4. exception is raised, indicating, no more values are available.

     Raises an *note auditing event: e96. ‘winreg.EnumKey’ with
     arguments ‘key’, ‘index’.

     3.3 版更變: See *note above: 39bb.

 -- 函式: 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: 39c0.

     `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:
     1d4. exception is raised, indicating no more values.

     The result is a tuple of 3 items:

     Index       Meaning
                 
     -------------------------------------------------------------
                 
     ‘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(): 34ea.)
                 

     Raises an *note auditing event: e96. ‘winreg.EnumValue’ with
     arguments ‘key’, ‘index’.

     3.3 版更變: See *note above: 39bb.

 -- 函式: winreg.ExpandEnvironmentStrings (str)

     Expands environment variable placeholders ‘%NAME%’ in strings like
     *note REG_EXPAND_SZ: 39c4.:

          >>> ExpandEnvironmentStrings('%windir%')
          'C:\\Windows'

     Raises an *note auditing event: e96.
     ‘winreg.ExpandEnvironmentStrings’ with argument ‘str’.

 -- 函式: 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: 39c0.

     It is not necessary to call *note FlushKey(): 39c5. 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(): 39be, the *note
     FlushKey(): 39c5. method returns only when all the data has been
     written to the registry.  An application should only call *note
     FlushKey(): 39c5. if it requires absolute certainty that registry
     changes are on disk.

          備註: If you don’t know whether a *note FlushKey(): 39c5. 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(): 34d6. or one
     of the constants *note HKEY_USERS: 39c6. or *note
     HKEY_LOCAL_MACHINE: 39c7.

     `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(): 34e8.
     function.  Under the file allocation table (FAT) file system, the
     filename may not have an extension.

     A call to *note LoadKey(): 34e1. fails if the calling process does
     not have the ‘SE_RESTORE_PRIVILEGE’ privilege.  Note that
     privileges are different from permissions – see the RegLoadKey
     documentation(2) for more details.

     If `key' is a handle returned by *note ConnectRegistry(): 34d6,
     then the path specified in `file_name' is relative to the remote
     computer.

     Raises an *note auditing event: e96. ‘winreg.LoadKey’ with
     arguments ‘key’, ‘sub_key’, ‘file_name’.

 -- 函式: 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: 39ba.

     `key' is an already open key, or one of the predefined *note HKEY_*
     constants: 39c0.

     `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: 39c9.  See *note Access Rights: 39c2. for other allowed
     values.

     The result is a new handle to the specified key.

     If the function fails, *note OSError: 1d4. is raised.

     Raises an *note auditing event: e96. ‘winreg.OpenKey’ with
     arguments ‘key’, ‘sub_key’, ‘access’.

     Raises an *note auditing event: e96. ‘winreg.OpenKey/result’ with
     argument ‘key’.

     3.2 版更變: Allow the use of named arguments.

     3.3 版更變: See *note above: 39bb.

 -- 函式: 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: 39c0.

     The result is a tuple of 3 items:

     Index       Meaning
                 
     --------------------------------------------------------------
                 
     ‘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.
                 

     Raises an *note auditing event: e96. ‘winreg.QueryInfoKey’ with
     argument ‘key’.

 -- 函式: 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: 39c0.

     `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(): 34e9.
     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(): 34e7. if possible.

     Raises an *note auditing event: e96. ‘winreg.QueryValue’ with
     arguments ‘key’, ‘sub_key’, ‘value_name’.

 -- 函式: 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: 39c0.

     `value_name' is a string indicating the value to query.

     The result is a tuple of 2 items:

     Index       Meaning
                 
     ----------------------------------------------------------
                 
     ‘0’         The value of the registry item.
                 
                 
     ‘1’         An integer giving the registry type for
                 this value (see table in docs for
                 *note SetValueEx(): 34ea.)
                 

     Raises an *note auditing event: e96. ‘winreg.QueryValue’ with
     arguments ‘key’, ‘sub_key’, ‘value_name’.

 -- 函式: 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: 39c0.

     `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(): 34e1. 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(3) for more details.

     This function passes ‘NULL’ for `security_attributes' to the API.

     Raises an *note auditing event: e96. ‘winreg.SaveKey’ with
     arguments ‘key’, ‘file_name’.

 -- 函式: 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: 39c0.

     `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: 39ca, meaning only strings are
     supported.  Use the *note SetValueEx(): 34ea. 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: 39cb. access.

     Raises an *note auditing event: e96. ‘winreg.SetValue’ with
     arguments ‘key’, ‘sub_key’, ‘type’, ‘value’.

 -- 函式: 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: 39c0.

     `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: 39cc. 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: 39cb. access.

     To open the key, use the *note CreateKey(): 34d7. or *note
     OpenKey(): 34e2. 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.

     Raises an *note auditing event: e96. ‘winreg.SetValue’ with
     arguments ‘key’, ‘sub_key’, ‘type’, ‘value’.

 -- 函式: 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: 39c0.

     Will generally raise *note NotImplementedError: 613. 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.

     Raises an *note auditing event: e96. ‘winreg.DisableReflectionKey’
     with argument ‘key’.

 -- 函式: 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: 39c0.

     Will generally raise *note NotImplementedError: 613. if executed on
     a 32-bit operating system.

     Restoring reflection for a key does not affect reflection of any
     subkeys.

     Raises an *note auditing event: e96. ‘winreg.EnableReflectionKey’
     with argument ‘key’.

 -- 函式: 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: 39c0.

     Returns ‘True’ if reflection is disabled.

     Will generally raise *note NotImplementedError: 613. if executed on
     a 32-bit operating system.

     Raises an *note auditing event: e96. ‘winreg.QueryReflectionKey’
     with argument ‘key’.

   ---------- Footnotes ----------

   (1) https://msdn.microsoft.com/en-us/library/ms724847%28VS.85%29.aspx

   (2) 
https://msdn.microsoft.com/en-us/library/ms724889%28v=VS.85%29.aspx

   (3) 
https://msdn.microsoft.com/en-us/library/ms724878%28v=VS.85%29.aspx


File: python.info,  Node: Constants<10>,  Next: Registry Handle Objects,  Prev: Functions<11>,  Up: winreg --- Windows registry access

5.34.3.2 Constants
..................

The following constants are defined for use in many ‘_winreg’ functions.

* Menu:

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


File: python.info,  Node: HKEY_* Constants,  Next: Access Rights,  Up: Constants<10>

5.34.3.3 HKEY_* Constants
.........................

 -- Data: 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.

 -- Data: 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.

 -- Data: 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.

 -- Data: 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.

 -- Data: 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.

 -- Data: winreg.HKEY_CURRENT_CONFIG

     Contains information about the current hardware profile of the
     local computer system.

 -- Data: 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: Constants<10>

5.34.3.4 Access Rights
......................

For more information, see Registry Key Security and Access(1).

 -- Data: winreg.KEY_ALL_ACCESS

     Combines the STANDARD_RIGHTS_REQUIRED, *note KEY_QUERY_VALUE: 39d7,
     *note KEY_SET_VALUE: 39cb, *note KEY_CREATE_SUB_KEY: 39d8, *note
     KEY_ENUMERATE_SUB_KEYS: 39d9, *note KEY_NOTIFY: 39da, and *note
     KEY_CREATE_LINK: 39db. access rights.

 -- Data: winreg.KEY_WRITE

     Combines the STANDARD_RIGHTS_WRITE, *note KEY_SET_VALUE: 39cb, and
     *note KEY_CREATE_SUB_KEY: 39d8. access rights.

 -- Data: winreg.KEY_READ

     Combines the STANDARD_RIGHTS_READ, *note KEY_QUERY_VALUE: 39d7,
     *note KEY_ENUMERATE_SUB_KEYS: 39d9, and *note KEY_NOTIFY: 39da.
     values.

 -- Data: winreg.KEY_EXECUTE

     Equivalent to *note KEY_READ: 39c9.

 -- Data: winreg.KEY_QUERY_VALUE

     Required to query the values of a registry key.

 -- Data: winreg.KEY_SET_VALUE

     Required to create, delete, or set a registry value.

 -- Data: winreg.KEY_CREATE_SUB_KEY

     Required to create a subkey of a registry key.

 -- Data: winreg.KEY_ENUMERATE_SUB_KEYS

     Required to enumerate the subkeys of a registry key.

 -- Data: winreg.KEY_NOTIFY

     Required to request change notifications for a registry key or for
     subkeys of a registry key.

 -- Data: 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.34.3.5 64-bit Specific
........................

For more information, see Accessing an Alternate Registry View(1).

 -- Data: winreg.KEY_WOW64_64KEY

     Indicates that an application on 64-bit Windows should operate on
     the 64-bit registry view.

 -- Data: winreg.KEY_WOW64_32KEY

     Indicates that an application on 64-bit Windows should operate on
     the 32-bit registry view.

   ---------- Footnotes ----------

   (1) https://msdn.microsoft.com/en-us/library/aa384129(v=VS.85).aspx


File: python.info,  Node: Value Types,  Prev: Access Rights,  Up: Constants<10>

5.34.3.6 Value Types
....................

For more information, see Registry Value Types(1).

 -- Data: winreg.REG_BINARY

     Binary data in any form.

 -- Data: winreg.REG_DWORD

     32-bit number.

 -- Data: winreg.REG_DWORD_LITTLE_ENDIAN

     A 32-bit number in little-endian format.  Equivalent to *note
     REG_DWORD: 39e2.

 -- Data: winreg.REG_DWORD_BIG_ENDIAN

     A 32-bit number in big-endian format.

 -- Data: winreg.REG_EXPAND_SZ

     Null-terminated string containing references to environment
     variables (‘%PATH%’).

 -- Data: winreg.REG_LINK

     A Unicode symbolic link.

 -- Data: winreg.REG_MULTI_SZ

     A sequence of null-terminated strings, terminated by two null
     characters.  (Python handles this termination automatically.)

 -- Data: winreg.REG_NONE

     No defined value type.

 -- Data: winreg.REG_QWORD

     A 64-bit number.

     3.6 版新加入.

 -- Data: winreg.REG_QWORD_LITTLE_ENDIAN

     A 64-bit number in little-endian format.  Equivalent to *note
     REG_QWORD: 5b7.

     3.6 版新加入.

 -- Data: winreg.REG_RESOURCE_LIST

     A device-driver resource list.

 -- Data: winreg.REG_FULL_RESOURCE_DESCRIPTOR

     A hardware setting.

 -- Data: winreg.REG_RESOURCE_REQUIREMENTS_LIST

     A hardware resource list.

 -- Data: 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: Constants<10>,  Up: winreg --- Windows registry access

5.34.3.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(): 39bf. method on the object, or the *note CloseKey():
39be. 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__(): c6d. – 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(): 185. function), in which case the underlying Windows handle
value is returned.  You can also use the *note Detach(): 34e3. 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.

     Raises an *note auditing event: e96. ‘winreg.PyHKEY.Detach’ with
     argument ‘key’.

 -- 成員函式: PyHKEY.__enter__ ()
 -- 成員函式: PyHKEY.__exit__ (*exc_info)

     The HKEY object implements *note __enter__(): c9a. and *note
     __exit__(): c9b. and thus supports the context protocol for the
     *note with: 6ee. statement:

          with OpenKey(HKEY_LOCAL_MACHINE, "foo") as key:
              ...  # work with key

     will automatically close `key' when control leaves the *note with:
     6ee. block.


File: python.info,  Node: winsound --- Sound-playing interface for Windows,  Prev: winreg --- Windows registry access,  Up: MS Windows Specific Services

5.34.4 ‘winsound’ — Sound-playing interface for Windows
-------------------------------------------------------

__________________________________________________________________

The *note winsound: 12c. 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: 2bb. 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: 5ed, 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:
     2bb. 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: 2bb. is raised.

 -- Data: winsound.SND_FILENAME

     The `sound' parameter is the name of a WAV file.  Do not use with
     *note SND_ALIAS: 39f1.

 -- Data: 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: 39f2. is also specified.
     If no default sound is registered, raise *note RuntimeError: 2bb.
     Do not use with *note SND_FILENAME: 39f0.

     All Win32 systems support at least the following; most systems
     support many more:

     *note PlaySound(): 5bb.        Corresponding Control Panel Sound name
     `name'                         

     ----------------------------------------------------------------------------
                                    
     ‘'SystemAsterisk'’             Asterisk
                                    
                                    
     ‘'SystemExclamation'’          Exclamation
                                    
                                    
     ‘'SystemExit'’                 Exit Windows
                                    
                                    
     ‘'SystemHand'’                 Critical Stop
                                    
                                    
     ‘'SystemQuestion'’             Question
                                    

     For example:

          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)

 -- Data: winsound.SND_LOOP

     Play the sound repeatedly.  The *note SND_ASYNC: 39f4. flag must
     also be used to avoid blocking.  Cannot be used with *note
     SND_MEMORY: 39f5.

 -- Data: winsound.SND_MEMORY

     The `sound' parameter to *note PlaySound(): 5bb. is a memory image
     of a WAV file, as a *note bytes-like object: 5ed.

          備註: This module does not support playing from a memory image
          asynchronously, so a combination of this flag and *note
          SND_ASYNC: 39f4. will raise *note RuntimeError: 2bb.

 -- Data: winsound.SND_PURGE

     Stop playing all instances of the specified sound.

          備註: This flag is not supported on modern Windows platforms.

 -- Data: winsound.SND_ASYNC

     Return immediately, allowing sounds to play asynchronously.

 -- Data: winsound.SND_NODEFAULT

     If the specified sound cannot be found, do not play the system
     default sound.

 -- Data: winsound.SND_NOSTOP

     Do not interrupt sounds currently playing.

 -- Data: winsound.SND_NOWAIT

     Return immediately if the sound driver is busy.

          備註: This flag is not supported on modern Windows platforms.

 -- Data: winsound.MB_ICONASTERISK

     Play the ‘SystemDefault’ sound.

 -- Data: winsound.MB_ICONEXCLAMATION

     Play the ‘SystemExclamation’ sound.

 -- Data: winsound.MB_ICONHAND

     Play the ‘SystemHand’ sound.

 -- Data: winsound.MB_ICONQUESTION

     Play the ‘SystemQuestion’ sound.

 -- Data: winsound.MB_OK

     Play the ‘SystemDefault’ sound.


File: python.info,  Node: Unix Specific Services,  Next: Superseded Modules,  Prev: MS Windows Specific Services,  Up: Python 標準函式庫 Standard Library

5.35 Unix Specific Services
===========================

The modules described in this chapter provide interfaces to features
that are unique to the Unix operating system, or in some cases to some
or many variants of it.  Here’s an overview:

* Menu:

* posix: posix --- The most common POSIX system calls. The most common POSIX system calls
* pwd: pwd --- The password database. The password database
* spwd: spwd --- The shadow password database. The shadow password database
* grp: grp --- The group database. The group database
* crypt: crypt --- Function to check Unix passwords. Function to check Unix passwords
* termios: termios --- POSIX style tty control. POSIX style tty control
* tty: tty --- Terminal control functions. Terminal control functions
* pty: pty --- Pseudo-terminal utilities. Pseudo-terminal utilities
* fcntl: fcntl --- The fcntl and ioctl system calls. The fcntl and ioctl system calls
* pipes: pipes --- Interface to shell pipelines. Interface to shell pipelines
* resource: resource --- Resource usage information. Resource usage information
* nis: nis --- Interface to Sun's NIS Yellow Pages. Interface to Sun’s NIS (Yellow Pages)
* syslog: syslog --- Unix syslog library routines. Unix syslog library routines


File: python.info,  Node: posix --- The most common POSIX system calls,  Next: pwd --- The password database,  Up: Unix Specific Services

5.35.1 ‘posix’ — The most common POSIX system calls
---------------------------------------------------

__________________________________________________________________

This module provides access to operating system functionality that is
standardized by the C Standard and the POSIX standard (a thinly
disguised Unix interface).

`Do not import this module directly.'  Instead, import the module *note
os: c5, which provides a `portable' version of this interface.  On Unix,
the *note os: c5. module provides a superset of the *note posix: d2.
interface.  On non-Unix operating systems the *note posix: d2. module is
not available, but a subset is always available through the *note os:
c5. interface.  Once *note os: c5. is imported, there is `no'
performance penalty in using it instead of *note posix: d2.  In
addition, *note os: c5. provides some additional functionality, such as
automatically calling *note putenv(): 1eeb. when an entry in
‘os.environ’ is changed.

Errors are reported as exceptions; the usual exceptions are given for
type errors, while errors reported by the system calls raise *note
OSError: 1d4.

* Menu:

* Large File Support::
* Notable Module Contents::


File: python.info,  Node: Large File Support,  Next: Notable Module Contents,  Up: posix --- The most common POSIX system calls

5.35.1.1 Large File Support
...........................

Several operating systems (including AIX, HP-UX, Irix and Solaris)
provide support for files that are larger than 2 GiB from a C
programming model where ‘int’ and ‘long’ are 32-bit values.  This is
typically accomplished by defining the relevant size and offset types as
64-bit values.  Such files are sometimes referred to as `large files'.

Large file support is enabled in Python when the size of an ‘off_t’ is
larger than a ‘long’ and the ‘long long’ is at least as large as an
‘off_t’.  It may be necessary to configure and compile Python with
certain compiler flags to enable this mode.  For example, it is enabled
by default with recent versions of Irix, but with Solaris 2.6 and 2.7
you need to do something like:

     CFLAGS="`getconf LFS_CFLAGS`" OPT="-g -O2 $CFLAGS" \
             ./configure

On large-file-capable Linux systems, this might work:

     CFLAGS='-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64' OPT="-g -O2 $CFLAGS" \
             ./configure


File: python.info,  Node: Notable Module Contents,  Prev: Large File Support,  Up: posix --- The most common POSIX system calls

5.35.1.2 Notable Module Contents
................................

In addition to many functions described in the *note os: c5. module
documentation, *note posix: d2. defines the following data item:

 -- Data: posix.environ

     A dictionary representing the string environment at the time the
     interpreter was started.  Keys and values are bytes on Unix and str
     on Windows.  For example, ‘environ[b'HOME']’ (‘environ['HOME']’ on
     Windows) is the pathname of your home directory, equivalent to
     ‘getenv("HOME")’ in C.

     Modifying this dictionary does not affect the string environment
     passed on by *note execv(): 1efe, *note popen(): 2aa. or *note
     system(): dc6.; if you need to change the environment, pass
     ‘environ’ to *note execve(): a45. or add variable assignments and
     export statements to the command string for *note system(): dc6. or
     *note popen(): 2aa.

     3.2 版更變: On Unix, keys and values are bytes.

          備註: The *note os: c5. module provides an alternate
          implementation of ‘environ’ which updates the environment on
          modification.  Note also that updating *note os.environ: b3c.
          will render this dictionary obsolete.  Use of the *note os:
          c5. module version of this is recommended over direct access
          to the *note posix: d2. module.


File: python.info,  Node: pwd --- The password database,  Next: spwd --- The shadow password database,  Prev: posix --- The most common POSIX system calls,  Up: Unix Specific Services

5.35.2 ‘pwd’ — The password database
------------------------------------

__________________________________________________________________

This module provides access to the Unix user account and password
database.  It is available on all Unix versions.

Password database entries are reported as a tuple-like object, whose
attributes correspond to the members of the ‘passwd’ structure
(Attribute field below, see ‘<pwd.h>’):

Index       Attribute           Meaning
                                
------------------------------------------------------------------
                                
0           ‘pw_name’           Login name
                                
                                
1           ‘pw_passwd’         Optional encrypted password
                                
                                
2           ‘pw_uid’            Numerical user ID
                                
                                
3           ‘pw_gid’            Numerical group ID
                                
                                
4           ‘pw_gecos’          User name or comment field
                                
                                
5           ‘pw_dir’            User home directory
                                
                                
6           ‘pw_shell’          User command interpreter
                                

The uid and gid items are integers, all others are strings.  *note
KeyError: 2c8. is raised if the entry asked for cannot be found.

     備註: 
     In traditional Unix the field ‘pw_passwd’ usually contains a
     password encrypted with a DES derived algorithm (see module *note
     crypt: 29.).  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.  If available, the *note spwd: f2.
     module should be used where access to the encrypted password is
     required.

It defines the following items:

 -- 函式: pwd.getpwuid (uid)

     Return the password database entry for the given numeric user ID.

 -- 函式: pwd.getpwnam (name)

     Return the password database entry for the given user name.

 -- 函式: pwd.getpwall ()

     Return a list of all available password database entries, in
     arbitrary order.

也參考
......

Module *note grp: 8b.

     An interface to the group database, similar to this.

Module *note spwd: f2.

     An interface to the shadow password database, similar to this.


File: python.info,  Node: spwd --- The shadow password database,  Next: grp --- The group database,  Prev: pwd --- The password database,  Up: Unix Specific Services

5.35.3 ‘spwd’ — The shadow password database
--------------------------------------------

__________________________________________________________________

This module provides access to the Unix shadow password database.  It is
available on various Unix versions.

You must have enough privileges to access the shadow password database
(this usually means you have to be root).

Shadow password database entries are reported as a tuple-like object,
whose attributes correspond to the members of the ‘spwd’ structure
(Attribute field below, see ‘<shadow.h>’):

Index       Attribute           Meaning
                                
----------------------------------------------------------------------
                                
0           ‘sp_namp’           Login name
                                
                                
1           ‘sp_pwdp’           Encrypted password
                                
                                
2           ‘sp_lstchg’         Date of last change
                                
                                
3           ‘sp_min’            Minimal number of days between
                                changes
                                
                                
4           ‘sp_max’            Maximum number of days between
                                changes
                                
                                
5           ‘sp_warn’           Number of days before password
                                expires to warn user about it
                                
                                
6           ‘sp_inact’          Number of days after password
                                expires until account is disabled
                                
                                
7           ‘sp_expire’         Number of days since 1970-01-01
                                when account expires
                                
                                
8           ‘sp_flag’           Reserved
                                

The sp_namp and sp_pwdp items are strings, all others are integers.
*note KeyError: 2c8. is raised if the entry asked for cannot be found.

The following functions are defined:

 -- 函式: spwd.getspnam (name)

     Return the shadow password database entry for the given user name.

     3.6 版更變: Raises a *note PermissionError: 604. instead of *note
     KeyError: 2c8. if the user doesn’t have privileges.

 -- 函式: spwd.getspall ()

     Return a list of all available shadow password database entries, in
     arbitrary order.

也參考
......

Module *note grp: 8b.

     An interface to the group database, similar to this.

Module *note pwd: d7.

     An interface to the normal password database, similar to this.


File: python.info,  Node: grp --- The group database,  Next: crypt --- Function to check Unix passwords,  Prev: spwd --- The shadow password database,  Up: Unix Specific Services

5.35.4 ‘grp’ — The group database
---------------------------------

__________________________________________________________________

This module provides access to the Unix group database.  It is available
on all Unix versions.

Group database entries are reported as a tuple-like object, whose
attributes correspond to the members of the ‘group’ structure (Attribute
field below, see ‘<pwd.h>’):

Index       Attribute       Meaning
                            
------------------------------------------------------------------
                            
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(): 1030.
or *note getgrgid(): 5e4.)

It defines the following items:

 -- 函式: grp.getgrgid (gid)

     Return the group database entry for the given numeric group ID.
     *note KeyError: 2c8. is raised if the entry asked for cannot be
     found.

     3.6 版後已棄用: Since Python 3.6 the support of non-integer
     arguments like floats or strings in *note getgrgid(): 5e4. is
     deprecated.

 -- 函式: grp.getgrnam (name)

     Return the group database entry for the given group name.  *note
     KeyError: 2c8. is raised if the entry asked for cannot be found.

 -- 函式: grp.getgrall ()

     Return a list of all available group entries, in arbitrary order.

也參考
......

Module *note pwd: d7.

     An interface to the user database, similar to this.

Module *note spwd: f2.

     An interface to the shadow password database, similar to this.


File: python.info,  Node: crypt --- Function to check Unix passwords,  Next: termios --- POSIX style tty control,  Prev: grp --- The group database,  Up: Unix Specific Services

5.35.5 ‘crypt’ — Function to check Unix passwords
-------------------------------------------------

`Source code:' Lib/crypt.py(1)

__________________________________________________________________

This module implements an interface to the ‘crypt(3)’ routine, which is
a one-way hash function based upon a modified DES algorithm; see the
Unix man page for further details.  Possible uses include storing hashed
passwords so you can check passwords without storing the actual
password, or attempting to crack Unix passwords with a dictionary.

Notice that the behavior of this module depends on the actual
implementation of the ‘crypt(3)’ routine in the running system.
Therefore, any extensions available on the current implementation will
also be available on this module.

*note Availability: 1364.: Unix.  Not available on VxWorks.

* Menu:

* Hashing Methods::
* Module Attributes::
* Module Functions: Module Functions<2>.
* Examples: Examples<31>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/crypt.py


File: python.info,  Node: Hashing Methods,  Next: Module Attributes,  Up: crypt --- Function to check Unix passwords

5.35.5.1 Hashing Methods
........................

3.3 版新加入.

The *note crypt: 29. module defines the list of hashing methods (not all
methods are available on all platforms):

 -- Data: crypt.METHOD_SHA512

     A Modular Crypt Format method with 16 character salt and 86
     character hash based on the SHA-512 hash function.  This is the
     strongest method.

 -- Data: crypt.METHOD_SHA256

     Another Modular Crypt Format method with 16 character salt and 43
     character hash based on the SHA-256 hash function.

 -- Data: crypt.METHOD_BLOWFISH

     Another Modular Crypt Format method with 22 character salt and 31
     character hash based on the Blowfish cipher.

     3.7 版新加入.

 -- Data: crypt.METHOD_MD5

     Another Modular Crypt Format method with 8 character salt and 22
     character hash based on the MD5 hash function.

 -- Data: crypt.METHOD_CRYPT

     The traditional method with a 2 character salt and 13 characters of
     hash.  This is the weakest method.


File: python.info,  Node: Module Attributes,  Next: Module Functions<2>,  Prev: Hashing Methods,  Up: crypt --- Function to check Unix passwords

5.35.5.2 Module Attributes
..........................

3.3 版新加入.

 -- 屬性: crypt.methods

     A list of available password hashing algorithms, as
     ‘crypt.METHOD_*’ objects.  This list is sorted from strongest to
     weakest.


File: python.info,  Node: Module Functions<2>,  Next: Examples<31>,  Prev: Module Attributes,  Up: crypt --- Function to check Unix passwords

5.35.5.3 Module Functions
.........................

The *note crypt: 29. module defines the following functions:

 -- 函式: crypt.crypt (word, salt=None)

     `word' will usually be a user’s password as typed at a prompt or in
     a graphical interface.  The optional `salt' is either a string as
     returned from *note mksalt(): 381, one of the ‘crypt.METHOD_*’
     values (though not all may be available on all platforms), or a
     full encrypted password including salt, as returned by this
     function.  If `salt' is not provided, the strongest method will be
     used (as returned by *note methods(): 3a19.).

     Checking a password is usually done by passing the plain-text
     password as `word' and the full results of a previous *note
     crypt(): 29. call, which should be the same as the results of this
     call.

     `salt' (either a random 2 or 16 character string, possibly prefixed
     with ‘$digit$’ to indicate the method) which will be used to
     perturb the encryption algorithm.  The characters in `salt' must be
     in the set ‘[./a-zA-Z0-9]’, with the exception of Modular Crypt
     Format which prefixes a ‘$digit$’.

     Returns the hashed password as a string, which will be composed of
     characters from the same alphabet as the salt.

     Since a few ‘crypt(3)’ extensions allow different values, with
     different sizes in the `salt', it is recommended to use the full
     crypted password as salt when checking for a password.

     3.3 版更變: Accept ‘crypt.METHOD_*’ values in addition to strings
     for `salt'.

 -- 函式: crypt.mksalt (method=None, *, rounds=None)

     Return a randomly generated salt of the specified method.  If no
     `method' is given, the strongest method available as returned by
     *note methods(): 3a19. is used.

     The return value is a string suitable for passing as the `salt'
     argument to *note crypt(): 29.

     `rounds' specifies the number of rounds for ‘METHOD_SHA256’,
     ‘METHOD_SHA512’ and ‘METHOD_BLOWFISH’.  For ‘METHOD_SHA256’ and
     ‘METHOD_SHA512’ it must be an integer between ‘1000’ and
     ‘999_999_999’, the default is ‘5000’.  For ‘METHOD_BLOWFISH’ it
     must be a power of two between ‘16’ (2^4) and ‘2_147_483_648’
     (2^31), the default is ‘4096’ (2^12).

     3.3 版新加入.

     3.7 版更變: Added the `rounds' parameter.


File: python.info,  Node: Examples<31>,  Prev: Module Functions<2>,  Up: crypt --- Function to check Unix passwords

5.35.5.4 Examples
.................

A simple example illustrating typical use (a constant-time comparison
operation is needed to limit exposure to timing attacks.  *note
hmac.compare_digest(): a11. is suitable for this purpose):

     import pwd
     import crypt
     import getpass
     from hmac import compare_digest as compare_hash

     def login():
         username = input('Python login: ')
         cryptedpasswd = pwd.getpwnam(username)[1]
         if cryptedpasswd:
             if cryptedpasswd == 'x' or cryptedpasswd == '*':
                 raise ValueError('no support for shadow passwords')
             cleartext = getpass.getpass()
             return compare_hash(crypt.crypt(cleartext, cryptedpasswd), cryptedpasswd)
         else:
             return True

To generate a hash of a password using the strongest available method
and check it against the original:

     import crypt
     from hmac import compare_digest as compare_hash

     hashed = crypt.crypt(plaintext)
     if not compare_hash(hashed, crypt.crypt(plaintext, hashed)):
         raise ValueError("hashed version doesn't validate against original")


File: python.info,  Node: termios --- POSIX style tty control,  Next: tty --- Terminal control functions,  Prev: crypt --- Function to check Unix passwords,  Up: Unix Specific Services

5.35.6 ‘termios’ — POSIX style tty control
------------------------------------------

__________________________________________________________________

This module provides an interface to the POSIX calls for tty I/O
control.  For a complete description of these calls, see ‘termios(3)’
Unix manual page.  It is only available for those Unix versions that
support POSIX `termios' style tty I/O control configured during
installation.

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: b47, 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: 105. 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(): 3a1f.  The `when' argument determines when the
     attributes are changed: ‘TCSANOW’ to change immediately,
     ‘TCSADRAIN’ to change after transmitting all queued output, or
     ‘TCSAFLUSH’ to change 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.

也參考
......

Module *note tty: 116.

     Convenience functions for common terminal control operations.

* Menu:

* Example: Example<16>.


File: python.info,  Node: Example<16>,  Up: termios --- POSIX style tty control

5.35.6.1 Example
................

Here’s a function that prompts for a password with echoing turned off.
Note the technique using a separate *note tcgetattr(): 3a1f. call and a
*note try: d77. ...  *note finally: 183. 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 --- Terminal control functions,  Next: pty --- Pseudo-terminal utilities,  Prev: termios --- POSIX style tty control,  Up: Unix Specific Services

5.35.7 ‘tty’ — Terminal control functions
-----------------------------------------

`Source code:' Lib/tty.py(1)

__________________________________________________________________

The *note tty: 116. module defines functions for putting the tty into
cbreak and raw modes.

Because it requires the *note termios: 105. module, it will work only on
Unix.

The *note tty: 116. module defines the following functions:

 -- 函式: tty.setraw (fd, when=termios.TCSAFLUSH)

     Change the mode of the file descriptor `fd' to raw.  If `when' is
     omitted, it defaults to ‘termios.TCSAFLUSH’, and is passed to *note
     termios.tcsetattr(): 3a20.

 -- 函式: tty.setcbreak (fd, when=termios.TCSAFLUSH)

     Change the mode of file descriptor `fd' to cbreak.  If `when' is
     omitted, it defaults to ‘termios.TCSAFLUSH’, and is passed to *note
     termios.tcsetattr(): 3a20.

也參考
......

Module *note termios: 105.

     Low-level terminal control interface.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/tty.py


File: python.info,  Node: pty --- Pseudo-terminal utilities,  Next: fcntl --- The fcntl and ioctl system calls,  Prev: tty --- Terminal control functions,  Up: Unix Specific Services

5.35.8 ‘pty’ — Pseudo-terminal utilities
----------------------------------------

`Source code:' Lib/pty.py(1)

__________________________________________________________________

The *note pty: d6. 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.

Because pseudo-terminal handling is highly platform dependent, there is
code to do it only for Linux.  (The Linux code is supposed to work on
other platforms, but hasn’t been tested yet.)

The *note pty: d6. 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).

 -- 函式: pty.openpty ()

     Open a new pseudo-terminal pair, using *note os.openpty(): 1f33. 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.

     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 *note OSError: 1d4. should be thrown.

     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).

     If both callbacks signal EOF then `spawn' will probably never
     return, unless `select' throws an error on your platform when
     passed three empty lists.  This is a bug, documented in issue
     26228(2).

     Raises an *note auditing event: e96. ‘pty.spawn’ with argument
     ‘argv’.

     3.4 版更變: *note spawn(): 89d. now returns the status value from
     *note os.waitpid(): 672. on the child process.

* Menu:

* Example: Example<17>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/pty.py

   (2) https://bugs.python.org/issue26228


File: python.info,  Node: Example<17>,  Up: pty --- Pseudo-terminal utilities

5.35.8.1 Example
................

The following program acts like the Unix command ‘script(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)


File: python.info,  Node: fcntl --- The fcntl and ioctl system calls,  Next: pipes --- Interface to shell pipelines,  Prev: pty --- Pseudo-terminal utilities,  Up: Unix Specific Services

5.35.9 ‘fcntl’ — The ‘fcntl’ and ‘ioctl’ system calls
-----------------------------------------------------

__________________________________________________________________

This module performs file control and I/O control on file descriptors.
It is an interface to the ‘fcntl()’ and ‘ioctl()’ Unix routines.  For a
complete description of these calls, see ‘fcntl(2)’ and ‘ioctl(2)’ Unix
manual pages.

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: 1dc. object, such as
‘sys.stdin’ itself, which provides a *note fileno(): 1f0f. that returns
a genuine file descriptor.

3.3 版更變: Operations in this module used to raise an *note IOError:
997. where they now raise an *note OSError: 1d4.

3.8 版更變: The fcntl module now contains ‘F_ADD_SEALS’, ‘F_GET_SEALS’,
and ‘F_SEAL_*’ constants for sealing of *note os.memfd_create(): 1f1.
file descriptors.

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(): 1f0f. method are accepted as well).
     The values used for `cmd' are operating system dependent, and are
     available as constants in the *note fcntl: 7e. 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: 336.
     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(): c10.  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: 336. 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()’ fails, an *note OSError: 1d4. is raised.

     Raises an *note auditing event: e96. ‘fcntl.fcntl’ with arguments
     ‘fd’, ‘cmd’, ‘arg’.

 -- 函式: fcntl.ioctl (fd, request, arg=0, mutate_flag=True)

     This function is identical to the *note fcntl(): 26a0. 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: 105. 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: 336.) or an
     object supporting the read-write buffer interface (like *note
     bytearray: 337.).

     In all but the last case, behaviour is as for the *note fcntl():
     26a0. 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(): de3. 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():
     de3.  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(): de3. and copied back into the supplied buffer.

     If the ‘ioctl()’ fails, an *note OSError: 1d4. 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])

     Raises an *note auditing event: e96. ‘fcntl.ioctl’ with arguments
     ‘fd’, ‘request’, ‘arg’.

 -- 函式: fcntl.flock (fd, operation)

     Perform the lock operation `operation' on file descriptor `fd'
     (file objects providing a *note fileno(): 1f0f. method are accepted
     as well).  See the Unix manual ‘flock(2)’ for details.  (On some
     systems, this function is emulated using ‘fcntl()’.)

     If the ‘flock()’ fails, an *note OSError: 1d4. exception is raised.

     Raises an *note auditing event: e96. ‘fcntl.flock’ with arguments
     ‘fd’, ‘operation’.

 -- 函式: fcntl.lockf (fd, cmd, len=0, start=0, whence=0)

     This is essentially a wrapper around the *note fcntl(): 26a0.
     locking calls.  `fd' is the file descriptor (file objects providing
     a *note fileno(): 1f0f. method are accepted as well) of the file to
     lock or unlock, and `cmd' is one of the following values:

        * ‘LOCK_UN’ – unlock

        * ‘LOCK_SH’ – acquire a shared lock

        * ‘LOCK_EX’ – acquire an exclusive lock

     When `cmd' is ‘LOCK_SH’ or ‘LOCK_EX’, it can also be bitwise ORed
     with ‘LOCK_NB’ to avoid blocking on lock acquisition.  If ‘LOCK_NB’
     is used and the lock cannot be acquired, an *note OSError: 1d4.
     will be raised and the exception will have an `errno' attribute set
     to ‘EACCES’ or ‘EAGAIN’ (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(): 1d9d, specifically:

        * ‘0’ – relative to the start of the file (*note os.SEEK_SET:
          d99.)

        * ‘1’ – relative to the current buffer position (*note
          os.SEEK_CUR: d9a.)

        * ‘2’ – relative to the end of the file (*note os.SEEK_END:
          d9b.)

     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.

     Raises an *note auditing event: e96. ‘fcntl.lockf’ with arguments
     ‘fd’, ‘cmd’, ‘len’, ‘start’, ‘whence’.

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: 336.
object.  The structure lay-out for the `lockdata' variable is system
dependent — therefore using the *note flock(): 34ce. call may be better.

也參考
......

Module *note os: c5.

     If the locking flags *note O_SHLOCK: d9c. and *note O_EXLOCK: d9d.
     are present in the *note os: c5. module (on BSD only), the *note
     os.open(): 66a. function provides an alternative to the *note
     lockf(): d57. and *note flock(): 34ce. functions.


File: python.info,  Node: pipes --- Interface to shell pipelines,  Next: resource --- Resource usage information,  Prev: fcntl --- The fcntl and ioctl system calls,  Up: Unix Specific Services

5.35.10 ‘pipes’ — Interface to shell pipelines
----------------------------------------------

`Source code:' Lib/pipes.py(1)

__________________________________________________________________

The *note pipes: cd. module defines a class to abstract the concept of a
`pipeline' — a sequence of converters from one file to another.

Because the module uses ‘/bin/sh’ command lines, a POSIX or compatible
shell for *note os.system(): dc6. and *note os.popen(): 2aa. is
required.

The *note pipes: cd. module defines the following class:

 -- 類別: pipes.Template

     An abstraction of a pipeline.

Example:

     >>> import pipes
     >>> t = pipes.Template()
     >>> t.append('tr a-z A-Z', '--')
     >>> f = t.open('pipefile', 'w')
     >>> f.write('hello world')
     >>> f.close()
     >>> open('pipefile').read()
     'HELLO WORLD'

* Menu:

* Template Objects::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/pipes.py


File: python.info,  Node: Template Objects,  Up: pipes --- Interface to shell pipelines

5.35.10.1 Template Objects
..........................

Template objects following methods:

 -- 成員函式: Template.reset ()

     Restore a pipeline template to its initial state.

 -- 成員函式: Template.clone ()

     Return a new, equivalent, pipeline template.

 -- 成員函式: Template.debug (flag)

     If `flag' is true, turn debugging on.  Otherwise, turn debugging
     off.  When debugging is on, commands to be executed are printed,
     and the shell is given ‘set -x’ command to be more verbose.

 -- 成員函式: Template.append (cmd, kind)

     Append a new action at the end.  The `cmd' variable must be a valid
     bourne shell command.  The `kind' variable consists of two letters.

     The first letter can be either of ‘'-'’ (which means the command
     reads its standard input), ‘'f'’ (which means the commands reads a
     given file on the command line) or ‘'.'’ (which means the commands
     reads no input, and hence must be first.)

     Similarly, the second letter can be either of ‘'-'’ (which means
     the command writes to standard output), ‘'f'’ (which means the
     command writes a file on the command line) or ‘'.'’ (which means
     the command does not write anything, and hence must be last.)

 -- 成員函式: Template.prepend (cmd, kind)

     Add a new action at the beginning.  See *note append(): 3a3a. for
     explanations of the arguments.

 -- 成員函式: Template.open (file, mode)

     Return a file-like object, open to `file', but read from or written
     to by the pipeline.  Note that only one of ‘'r'’, ‘'w'’ may be
     given.

 -- 成員函式: Template.copy (infile, outfile)

     Copy `infile' to `outfile' through the pipe.


File: python.info,  Node: resource --- Resource usage information,  Next: nis --- Interface to Sun's NIS Yellow Pages,  Prev: pipes --- Interface to shell pipelines,  Up: Unix Specific Services

5.35.11 ‘resource’ — Resource usage information
-----------------------------------------------

__________________________________________________________________

This module provides basic mechanisms for measuring and controlling
system resources utilized by a program.

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: 1d4. is raised on syscall failure.

 -- 例外: resource.error

     A deprecated alias of *note OSError: 1d4.

     3.3 版更變: Following PEP 3151(1), this class was made an alias of
     *note OSError: 1d4.

* Menu:

* Resource Limits::
* Resource Usage::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3151


File: python.info,  Node: Resource Limits,  Next: Resource Usage,  Up: resource --- Resource usage information

5.35.11.1 Resource Limits
.........................

Resources usage can be limited using the *note setrlimit(): 34aa.
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)’ 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.

 -- Data: 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: 1fc. if an invalid
     resource is specified, or *note error: 3a40. 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: 3a42. can be used
     to request a limit that is unlimited.

     Raises *note ValueError: 1fc. 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: 3a42. when the hard or system limit for that
     resource is not unlimited will result in a *note ValueError: 1fc.
     A process with the effective UID of super-user can request any
     valid limit value, including unlimited, but *note ValueError: 1fc.
     will still be raised if the requested limit exceeds the system
     imposed limit.

     ‘setrlimit’ may also raise *note error: 3a40. if the underlying
     system call fails.

     VxWorks only supports setting *note RLIMIT_NOFILE: 3a44.

     Raises an *note auditing event: e96. ‘resource.setrlimit’ with
     arguments ‘resource’, ‘limits’.

 -- 函式: resource.prlimit (pid, resource[, limits])

     Combines *note setrlimit(): 34aa. and *note getrlimit(): 3a43. 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(): 34aa, 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: 9a0. when `pid' can’t be found and
     *note PermissionError: 604. when the user doesn’t have
     ‘CAP_SYS_RESOURCE’ for the process.

     Raises an *note auditing event: e96. ‘resource.prlimit’ with
     arguments ‘pid’, ‘resource’, ‘limits’.

     *note Availability: 1364.: Linux 2.6.36 or later with glibc 2.13 or
     later.

     3.4 版新加入.

These symbols define resources whose consumption can be controlled using
the *note setrlimit(): 34aa. and *note getrlimit(): 3a43. functions
described below.  The values of these symbols are exactly the constants
used by C programs.

The Unix man page for ‘getrlimit(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.

 -- Data: 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.

 -- Data: 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: eb. module documentation for
     information about how to catch this signal and do something useful,
     e.g.  flush open files to disk.)

 -- Data: resource.RLIMIT_FSIZE

     The maximum size of a file which the process may create.

 -- Data: resource.RLIMIT_DATA

     The maximum size (in bytes) of the process’s heap.

 -- Data: 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.

 -- Data: resource.RLIMIT_RSS

     The maximum resident set size that should be made available to the
     process.

 -- Data: resource.RLIMIT_NPROC

     The maximum number of processes the current process may create.

 -- Data: resource.RLIMIT_NOFILE

     The maximum number of open file descriptors for the current
     process.

 -- Data: resource.RLIMIT_OFILE

     The BSD name for *note RLIMIT_NOFILE: 3a44.

 -- Data: resource.RLIMIT_MEMLOCK

     The maximum address space which may be locked in memory.

 -- Data: resource.RLIMIT_VMEM

     The largest area of mapped memory which the process may occupy.

 -- Data: resource.RLIMIT_AS

     The maximum area (in bytes) of address space which may be taken by
     the process.

 -- Data: resource.RLIMIT_MSGQUEUE

     The number of bytes that can be allocated for POSIX message queues.

     *note Availability: 1364.: Linux 2.6.8 or later.

     3.4 版新加入.

 -- Data: resource.RLIMIT_NICE

     The ceiling for the process’s nice level (calculated as 20 -
     rlim_cur).

     *note Availability: 1364.: Linux 2.6.12 or later.

     3.4 版新加入.

 -- Data: resource.RLIMIT_RTPRIO

     The ceiling of the real-time priority.

     *note Availability: 1364.: Linux 2.6.12 or later.

     3.4 版新加入.

 -- Data: 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 Availability: 1364.: Linux 2.6.25 or later.

     3.4 版新加入.

 -- Data: resource.RLIMIT_SIGPENDING

     The number of signals which the process may queue.

     *note Availability: 1364.: Linux 2.6.8 or later.

     3.4 版新加入.

 -- Data: 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 Availability: 1364.: FreeBSD 9 or later.

     3.4 版新加入.

 -- Data: 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)(1) for a complete description of this sysctl.

     *note Availability: 1364.: FreeBSD 9 or later.

     3.4 版新加入.

 -- Data: resource.RLIMIT_NPTS

     The maximum number of pseudo-terminals created by this user id.

     *note Availability: 1364.: FreeBSD 9 or later.

     3.4 版新加入.

   ---------- Footnotes ----------

   (1) https://www.freebsd.org/cgi/man.cgi?query=tuning&sektion=7


File: python.info,  Node: Resource Usage,  Prev: Resource Limits,  Up: resource --- Resource usage information

5.35.11.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.

     A simple example:

          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)’ 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: 1fc. if an invalid
     `who' parameter is specified.  It may also raise *note error: 3a40.
     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():
d9e. function to specify which processes information should be provided
for.

 -- Data: resource.RUSAGE_SELF

     Pass to *note getrusage(): d9e. to request resources consumed by
     the calling process, which is the sum of resources used by all
     threads in the process.

 -- Data: resource.RUSAGE_CHILDREN

     Pass to *note getrusage(): d9e. to request resources consumed by
     child processes of the calling process which have been terminated
     and waited for.

 -- Data: resource.RUSAGE_BOTH

     Pass to *note getrusage(): d9e. to request resources consumed by
     both the current process and child processes.  May not be available
     on all systems.

 -- Data: resource.RUSAGE_THREAD

     Pass to *note getrusage(): d9e. to request resources consumed by
     the current thread.  May not be available on all systems.

     3.2 版新加入.


File: python.info,  Node: nis --- Interface to Sun's NIS Yellow Pages,  Next: syslog --- Unix syslog library routines,  Prev: resource --- Resource usage information,  Up: Unix Specific Services

5.35.12 ‘nis’ — Interface to Sun’s NIS (Yellow Pages)
-----------------------------------------------------

__________________________________________________________________

The *note nis: c0. module gives a thin wrapper around the NIS library,
useful for central administration of several hosts.

Because NIS exists only on Unix systems, this module is only available
for Unix.

The *note nis: c0. module defines the following functions:

 -- 函式: nis.match (key, mapname, domain=default_domain)

     Return the match for `key' in map `mapname', or raise an error
     (*note nis.error: 3a57.) if there is none.  Both should be strings,
     `key' is 8-bit clean.  Return value is an arbitrary array of bytes
     (may contain ‘NULL’ and other joys).

     Note that `mapname' is first checked if it is an alias to another
     name.

     The `domain' argument allows overriding the NIS domain used for the
     lookup.  If unspecified, lookup is in the default NIS domain.

 -- 函式: nis.cat (mapname, domain=default_domain)

     Return a dictionary mapping `key' to `value' such that ‘match(key,
     mapname)==value’.  Note that both keys and values of the dictionary
     are arbitrary arrays of bytes.

     Note that `mapname' is first checked if it is an alias to another
     name.

     The `domain' argument allows overriding the NIS domain used for the
     lookup.  If unspecified, lookup is in the default NIS domain.

 -- 函式: nis.maps (domain=default_domain)

     Return a list of all valid maps.

     The `domain' argument allows overriding the NIS domain used for the
     lookup.  If unspecified, lookup is in the default NIS domain.

 -- 函式: nis.get_default_domain ()

     Return the system default NIS domain.

The *note nis: c0. module defines the following exception:

 -- 例外: nis.error

     An error raised when a NIS function returns an error code.


File: python.info,  Node: syslog --- Unix syslog library routines,  Prev: nis --- Interface to Sun's NIS Yellow Pages,  Up: Unix Specific Services

5.35.13 ‘syslog’ — Unix syslog library routines
-----------------------------------------------

__________________________________________________________________

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.

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: ad. module as ‘SysLogHandler’.

The module defines the following functions:

 -- 函式: 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 ‘LOG_INFO’, 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(): 34d3. call is used.

     If *note openlog(): 34d3. has not been called prior to the call to
     *note syslog(): 100, ‘openlog()’ will be called with no arguments.

     Raises an *note auditing event: e96. ‘syslog.syslog’ with arguments
     ‘priority’, ‘message’.

 -- 函式: syslog.openlog ([ident[, logoption[, facility]]])

     Logging options of subsequent *note syslog(): 100. calls can be set
     by calling *note openlog(): 34d3.  *note syslog(): 100. will call
     *note openlog(): 34d3. 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 ‘LOG_USER’) sets the default facility for messages
     which do not have a facility explicitly encoded.

     Raises an *note auditing event: e96. ‘syslog.openlog’ with
     arguments ‘ident’, ‘logoption’, ‘facility’.

     3.2 版更變: In previous versions, keyword arguments were not
     allowed, and `ident' was required.  The default for `ident' was
     dependent on the system libraries, and often was ‘python’ instead
     of the name of the Python program file.

 -- 函式: 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(): 34d3. will be called on
     the first *note syslog(): 100. call (if *note openlog(): 34d3.
     hasn’t already been called), and `ident' and other *note openlog():
     34d3. parameters are reset to defaults.

     Raises an *note auditing event: e96. ‘syslog.closelog’ with no
     arguments.

 -- 函式: syslog.setlogmask (maskpri)

     Set the priority mask to `maskpri' and return the previous mask
     value.  Calls to *note syslog(): 100. 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'.

     Raises an *note auditing event: e96. ‘syslog.setlogmask’ with
     argument ‘maskpri’.

The module defines the following constants:

Priority levels (high to low):

     ‘LOG_EMERG’, ‘LOG_ALERT’, ‘LOG_CRIT’, ‘LOG_ERR’, ‘LOG_WARNING’,
     ‘LOG_NOTICE’, ‘LOG_INFO’, ‘LOG_DEBUG’.

Facilities:

     ‘LOG_KERN’, ‘LOG_USER’, ‘LOG_MAIL’, ‘LOG_DAEMON’, ‘LOG_AUTH’,
     ‘LOG_LPR’, ‘LOG_NEWS’, ‘LOG_UUCP’, ‘LOG_CRON’, ‘LOG_SYSLOG’,
     ‘LOG_LOCAL0’ to ‘LOG_LOCAL7’, and, if defined in ‘<syslog.h>’,
     ‘LOG_AUTHPRIV’.

Log options:

     ‘LOG_PID’, ‘LOG_CONS’, ‘LOG_NDELAY’, and, if defined in
     ‘<syslog.h>’, ‘LOG_ODELAY’, ‘LOG_NOWAIT’, and ‘LOG_PERROR’.

* Menu:

* Examples: Examples<32>.


File: python.info,  Node: Examples<32>,  Up: syslog --- Unix syslog library routines

5.35.13.1 Examples
..................

* Menu:

* Simple example::


File: python.info,  Node: Simple example,  Up: Examples<32>

5.35.13.2 Simple example
........................

A simple set of examples:

     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: Superseded Modules,  Next: Undocumented Modules,  Prev: Unix Specific Services,  Up: Python 標準函式庫 Standard Library

5.36 Superseded Modules
=======================

The modules described in this chapter are deprecated and only kept for
backwards compatibility.  They have been superseded by other modules.

* Menu:

* optparse: optparse --- Parser for command line options. Parser for command line options
* imp: imp --- Access the import internals. Access the import internals


File: python.info,  Node: optparse --- Parser for command line options,  Next: imp --- Access the import internals,  Up: Superseded Modules

5.36.1 ‘optparse’ — Parser for command line options
---------------------------------------------------

`Source code:' Lib/optparse.py(1)

3.2 版後已棄用: The *note optparse: c4. module is deprecated and will
not be developed further; development will continue with the *note
argparse: 6. module.

__________________________________________________________________

*note optparse: c4. is a more convenient, flexible, and powerful library
for parsing command-line options than the old *note getopt: 87. module.
*note optparse: c4. uses a more declarative style of command-line
parsing: you create an instance of *note OptionParser: 3a63, populate it
with options, and parse the command line.  *note optparse: c4. 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: c4. 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: c4. sets attributes of
the ‘options’ object returned by ‘parse_args()’ based on user-supplied
command-line values.  When ‘parse_args()’ returns from parsing this
command line, ‘options.filename’ will be ‘"outfile"’ and
‘options.verbose’ will be ‘False’.  *note optparse: c4. 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: c4. 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:

* Background::
* Tutorial: Tutorial<2>.
* Reference Guide::
* Option Callbacks::
* Extending optparse::

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/optparse.py


File: python.info,  Node: Background,  Next: Tutorial<2>,  Up: optparse --- Parser for command line options

5.36.1.1 Background
...................

*note optparse: c4. 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:

* Terminology::
* What are options for?::
* What are positional arguments for?::


File: python.info,  Node: Terminology,  Next: What are options for?,  Up: Background

5.36.1.2 Terminology
....................

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: c4.

     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: c4, 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 VMS, MS-DOS, and/or Windows.

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: c4, 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: c4. 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: c4. 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: Terminology,  Up: Background

5.36.1.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: Background

5.36.1.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: Tutorial<2>,  Next: Reference Guide,  Prev: Background,  Up: optparse --- Parser for command line options

5.36.1.5 Tutorial
.................

While *note optparse: c4. 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: c4.-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: c4. 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(): 2079. 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: c4. encounters `option strings' and looks up
options from them.

Once all of your options are defined, instruct *note optparse: c4. to
parse your program’s command line:

     (options, args) = parser.parse_args()

(If you like, you can pass a custom argument list to ‘parse_args()’, but
that’s rarely necessary: by default it uses ‘sys.argv[1:]’.)

‘parse_args()’ returns two values:

   * ‘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: 3a6e, *note type: 3a6f, *note dest: 3a70.
(destination), and *note help: 3a71.  Of these, *note action: 3a6e. 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: Tutorial<2>

5.36.1.6 Understanding option actions
.....................................

Actions tell *note optparse: c4. what to do when it encounters an option
on the command line.  There is a fixed set of actions hard-coded into
*note optparse: c4.; adding new actions is an advanced topic covered in
section *note Extending optparse: 3a74.  Most actions tell *note
optparse: c4. 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: c4. defaults to
‘store’.


File: python.info,  Node: The store action,  Next: Handling boolean flag options,  Prev: Understanding option actions,  Up: Tutorial<2>

5.36.1.7 The store action
.........................

The most common option action is ‘store’, which tells *note optparse:
c4. 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.

For example:

     parser.add_option("-f", "--file",
                       action="store", type="string", dest="filename")

Now let’s make up a fake command line and ask *note optparse: c4. to
parse it:

     args = ["-f", "foo.txt"]
     (options, args) = parser.parse_args(args)

When *note optparse: c4. sees the option string ‘-f’, it consumes the
next argument, ‘foo.txt’, and stores it in ‘options.filename’.  So,
after this call to ‘parse_args()’, ‘options.filename’ is ‘"foo.txt"’.

Some other option types supported by *note optparse: c4. 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: c4. 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: c4. 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: c4. looks at the first
short option string: the default destination for ‘-f’ is ‘f’.

*note optparse: c4. also includes the built-in ‘complex’ type.  Adding
types is covered in section *note Extending optparse: 3a74.


File: python.info,  Node: Handling boolean flag options,  Next: Other actions,  Prev: The store action,  Up: Tutorial<2>

5.36.1.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: c4. 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: c4. 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: Tutorial<2>

5.36.1.9 Other actions
......................

Some other actions supported by *note optparse: c4. are:

‘"store_const"’

     store a constant value

‘"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: 3a7b, and section
*note Option Callbacks: 3a7c.


File: python.info,  Node: Default values,  Next: Generating help,  Prev: Other actions,  Up: Tutorial<2>

5.36.1.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: c4. 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:
c4. 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
‘parse_args()’:

     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: Tutorial<2>

5.36.1.11 Generating help
.........................

*note optparse: c4.’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: 3a71. 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: c4. 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: c4.
exits after printing the help text.)

There’s a lot going on here to help *note optparse: c4. generate the
best possible help message:

   * the script defines its own usage message:

          usage = "usage: %prog [options] arg1 arg2"

     *note optparse: c4. 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: c4. 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: c4. 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: c4. 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: c4. will replace it with *note str():
     335. 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.1.12 Grouping Options
..........................

When dealing with many options, it is convenient to group these options
for better help output.  An *note OptionParser: 3a63. can contain
several option groups, each of which can contain several options.

An option group is obtained using the class *note OptionGroup: 3a82.:

 -- 類別: optparse.OptionGroup (parser, title, description=None)

     where

        * parser is the *note OptionParser: 3a63. instance the group
          will be inserted in to

        * title is the group title

        * description, optional, is a long description of the group

*note OptionGroup: 3a82. inherits from ‘OptionContainer’ (like *note
OptionParser: 3a63.) 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: 3a63.
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: 3a82. 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: 3a82. to which the short or long
     option string `opt_str' (e.g.  ‘'-o'’ or ‘'--option'’) belongs.  If
     there’s no such *note OptionGroup: 3a82, return ‘None’.


File: python.info,  Node: Printing a version string,  Next: How optparse handles errors,  Prev: Generating help,  Up: Tutorial<2>

5.36.1.13 Printing a version string
...................................

Similar to the brief usage string, *note optparse: c4. 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: c4. 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(): 3a87, 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(): 3a86. 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: Tutorial<2>

5.36.1.14 How ‘optparse’ handles errors
.......................................

There are two broad classes of errors that *note optparse: c4. has to
worry about: programmer errors and user errors.  Programmer errors are
usually erroneous calls to *note OptionParser.add_option(): 2079, e.g.
invalid option strings, unknown option attributes, missing option
attributes, etc.  These are dealt with in the usual way: raise an
exception (either ‘optparse.OptionError’ or *note TypeError: 193.) 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: c4. 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: c4. 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: c4.-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: c4.’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: Tutorial<2>

5.36.1.15 Putting it all together
.................................

Here’s what *note optparse: c4.-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: Tutorial<2>,  Up: optparse --- Parser for command line options

5.36.1.16 Reference Guide
.........................

* Menu:

* Creating the parser::
* Populating the parser::
* Defining options::
* Option attributes::
* Standard option actions::
* Standard option types::
* Parsing arguments: Parsing arguments<2>.
* Querying and manipulating your option parser::
* Conflicts between options::
* Cleanup: Cleanup<2>.
* Other methods::


File: python.info,  Node: Creating the parser,  Next: Populating the parser,  Up: Reference Guide

5.36.1.17 Creating the parser
.............................

The first step in using *note optparse: c4. 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: c4.
          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(): 2079. after
          creating the parser instead.

     ‘option_class’ (default: optparse.Option)

          Class to use when adding options to the parser in *note
          add_option(): 2079.

     ‘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: c4. 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: 3a90.

     ‘description’ (default: ‘None’)

          A paragraph of text giving a brief overview of your program.
          *note optparse: c4. 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: c4. provides two concrete
          classes for this purpose: IndentedHelpFormatter and
          TitledHelpFormatter.

     ‘add_help_option’ (default: ‘True’)

          If true, *note optparse: c4. 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.1.18 Populating the parser
...............................

There are several ways to populate the parser with options.  The
preferred way is by using *note OptionParser.add_option(): 2079, as
shown in section *note Tutorial: 3a6c.  ‘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: c4. 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.1.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 ‘Option’ instance is with the
‘add_option()’ method of *note OptionParser: 3a63.

 -- 成員函式: 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: 3a6e, 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: c4. raises an ‘OptionError’ exception
     explaining your mistake.

     An option’s `action' determines what *note optparse: c4. does when
     it encounters this option on the command-line.  The standard option
     actions hard-coded into *note optparse: c4. are:

     ‘"store"’

          store this option’s argument (default)

     ‘"store_const"’

          store a constant value

     ‘"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

     ‘"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: 3a6f. and *note dest: 3a70.
     option attributes; see *note Standard option actions: 3a95.)

As you can see, most actions involve storing or updating a value
somewhere.  *note optparse: c4. always creates a special object for
this, conventionally called ‘options’ (it happens to be an instance of
‘optparse.Values’).  Option arguments (and various other values) are
stored as attributes of this object, according to the *note dest: 3a70.
(destination) option attribute.

For example, when you call

     parser.parse_args()

one of the first things *note optparse: c4. 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: c4, on seeing this option, will do the equivalent
of

     options.filename = "foo"

The *note type: 3a6f. and *note dest: 3a70. option attributes are almost
as important as *note action: 3a6e, but *note action: 3a6e. 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.1.20 Option attributes
...........................

The following option attributes may be passed as keyword arguments to
*note OptionParser.add_option(): 2079.  If you pass an option attribute
that is not relevant to a particular option, or fail to pass a required
option attribute, *note optparse: c4. raises ‘OptionError’.

 -- 屬性: Option.action

     (default: ‘"store"’)

     Determines *note optparse: c4.’s behaviour when this option is seen
     on the command line; the available options are documented *note
     here: 3a95.

 -- 屬性: Option.type

     (default: ‘"string"’)

     The argument type expected by this option (e.g., ‘"string"’ or
     ‘"int"’); the available option types are documented *note here:
     3a98.

 -- 屬性: Option.dest

     (default: derived from option strings)

     If the option’s action implies writing or modifying a value
     somewhere, this tells *note optparse: c4. where to write it: *note
     dest: 3a70. names an attribute of the ‘options’ object that *note
     optparse: c4. 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(): 3a9a.

 -- 屬性: Option.nargs

     (default: 1)

     How many arguments of type *note type: 3a6f. should be consumed
     when this option is seen.  If > 1, *note optparse: c4. will store a
     tuple of values to *note dest: 3a70.

 -- 屬性: 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: 3a7c. 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: 3a71. 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 Tutorial: 3a6c. for an example.


File: python.info,  Node: Standard option actions,  Next: Standard option types,  Prev: Option attributes,  Up: Reference Guide

5.36.1.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: c4.’s behaviour; a few have
required attributes, which you must specify for any option using that
action.

   * ‘"store"’ [relevant: *note type: 3a6f, *note dest: 3a70, *note
     nargs: 3a9b, *note choices: 3a9d.]

     The option must be followed by an argument, which is converted to a
     value according to *note type: 3a6f. and stored in *note dest:
     3a70.  If *note nargs: 3a9b. > 1, multiple arguments will be
     consumed from the command line; all will be converted according to
     *note type: 3a6f. and stored to *note dest: 3a70. as a tuple.  See
     the *note Standard option types: 3a98. section.

     If *note choices: 3a9d. is supplied (a list or tuple of strings),
     the type defaults to ‘"choice"’.

     If *note type: 3a6f. is not supplied, it defaults to ‘"string"’.

     If *note dest: 3a70. is not supplied, *note optparse: c4. 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: c4. derives a destination from the first short option
     string (e.g., ‘-f’ implies ‘f’).

     Example:

          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: c4. will set

          options.f = "foo.txt"
          options.point = (1.0, -3.5, 4.0)
          options.f = "bar.txt"

   * ‘"store_const"’ [required: *note const: 3a9c.; relevant: *note
     dest: 3a70.]

     The value *note const: 3a9c. is stored in *note dest: 3a70.

     Example:

          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: c4. will set

          options.verbose = 2

   * ‘"store_true"’ [relevant: *note dest: 3a70.]

     A special case of ‘"store_const"’ that stores ‘True’ to *note dest:
     3a70.

   * ‘"store_false"’ [relevant: *note dest: 3a70.]

     Like ‘"store_true"’, but stores ‘False’.

     Example:

          parser.add_option("--clobber", action="store_true", dest="clobber")
          parser.add_option("--no-clobber", action="store_false", dest="clobber")

   * ‘"append"’ [relevant: *note type: 3a6f, *note dest: 3a70, *note
     nargs: 3a9b, *note choices: 3a9d.]

     The option must be followed by an argument, which is appended to
     the list in *note dest: 3a70.  If no default value for *note dest:
     3a70. is supplied, an empty list is automatically created when
     *note optparse: c4. first encounters this option on the
     command-line.  If *note nargs: 3a9b. > 1, multiple arguments are
     consumed, and a tuple of length *note nargs: 3a9b. is appended to
     *note dest: 3a70.

     The defaults for *note type: 3a6f. and *note dest: 3a70. are the
     same as for the ‘"store"’ action.

     Example:

          parser.add_option("-t", "--tracks", action="append", type="int")

     If ‘-t3’ is seen on the command-line, *note optparse: c4. 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: 3a9c.; relevant: *note
     dest: 3a70.]

     Like ‘"store_const"’, but the value *note const: 3a9c. is appended
     to *note dest: 3a70.; as with ‘"append"’, *note dest: 3a70.
     defaults to ‘None’, and an empty list is automatically created the
     first time the option is encountered.

   * ‘"count"’ [relevant: *note dest: 3a70.]

     Increment the integer stored at *note dest: 3a70.  If no default
     value is supplied, *note dest: 3a70. is set to zero before being
     incremented the first time.

     Example:

          parser.add_option("-v", action="count", dest="verbosity")

     The first time ‘-v’ is seen on the command line, *note optparse:
     c4. does the equivalent of:

          options.verbosity = 0
          options.verbosity += 1

     Every subsequent occurrence of ‘-v’ results in

          options.verbosity += 1

   * ‘"callback"’ [required: *note callback: 3a9e.; relevant: *note
     type: 3a6f, *note nargs: 3a9b, *note callback_args: 3a9f, *note
     callback_kwargs: 3aa0.]

     Call the function specified by *note callback: 3a9e, which is
     called as

          func(option, opt_str, value, parser, *args, **kwargs)

     See section *note Option Callbacks: 3a7c. for more detail.

   * ‘"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:
     3a71. string passed to every option.

     If no *note help: 3a71. 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: c4. automatically adds a *note help: 3a71. option
     to all OptionParsers, so you do not normally need to create one.

     Example:

          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: c4. 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: c4. 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: 3a71. options, you will rarely
     create ‘version’ options, since *note optparse: c4. automatically
     adds them when needed.


File: python.info,  Node: Standard option types,  Next: Parsing arguments<2>,  Prev: Standard option actions,  Up: Reference Guide

5.36.1.22 Standard option types
...............................

*note optparse: c4. 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: 3a74.

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(): 185. with the appropriate
base (2, 8, 10, or 16).  If this fails, so will *note optparse: c4,
although with a more useful error message.

‘"float"’ and ‘"complex"’ option arguments are converted directly with
*note float(): 188. and *note complex(): 18a, with similar
error-handling.

‘"choice"’ options are a subtype of ‘"string"’ options.  The *note
choices: 3a9d. 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
‘OptionValueError’ if an invalid string is given.


File: python.info,  Node: Parsing arguments<2>,  Next: Querying and manipulating your option parser,  Prev: Standard option types,  Up: Reference Guide

5.36.1.23 Parsing arguments
...........................

The whole point of creating and populating an OptionParser is to call
its ‘parse_args()’ method:

     (options, args) = parser.parse_args(args=None, values=None)

where the input parameters are

‘args’

     the list of arguments to process (default: ‘sys.argv[1:]’)

‘values’

     an ‘optparse.Values’ object to store option arguments in (default:
     a new instance of ‘Values’) – if you give an existing object, the
     option defaults will not be initialized on it

and the return values are

‘options’

     the same object that was passed in as ‘values’, or the
     optparse.Values instance created by *note optparse: c4.

‘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():
15e1. calls (roughly one for every option argument stored to an option
destination) and returned by ‘parse_args()’.

If ‘parse_args()’ 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: Parsing arguments<2>,  Up: Reference Guide

5.36.1.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: c4. 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():
     207a.  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: 3a63. 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: 3a63, raises *note ValueError: 1fc.


File: python.info,  Node: Conflicts between options,  Next: Cleanup<2>,  Prev: Querying and manipulating your option parser,  Up: Reference Guide

5.36.1.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: c4. 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
          ‘OptionConflictError’

     ‘"resolve"’

          resolve option conflicts intelligently (see below)

As an example, let’s define an *note OptionParser: 3a63. 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: c4. 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: c4.
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: c4. removes it, leaving this help text:

     Options:
       ...
       -n, --noisy   be noisy
       --dry-run     new dry-run option


File: python.info,  Node: Cleanup<2>,  Next: Other methods,  Prev: Conflicts between options,  Up: Reference Guide

5.36.1.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: Other methods,  Prev: Cleanup<2>,  Up: Reference Guide

5.36.1.27 Other methods
.......................

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(): 3a87. 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(): 3a9a. 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(): 3a9a.:

          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 --- Parser for command line options

5.36.1.28 Option Callbacks
..........................

When *note optparse: c4.’s built-in actions and types aren’t quite
enough for your needs, you have two choices: extend *note optparse: c4.
or define a callback option.  Extending *note optparse: c4. 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.1.29 Defining a callback option
....................................

As always, the easiest way to define a callback option is by using the
*note OptionParser.add_option(): 2079. method.  Apart from *note action:
3a6e, 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: c4. 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: c4. always passes four particular arguments to your
callback, and it will only pass additional arguments if you specify them
via *note callback_args: 3a9f. and *note callback_kwargs: 3aa0.  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: 3a6f.

     has its usual meaning: as with the ‘"store"’ or ‘"append"’ actions,
     it instructs *note optparse: c4. to consume one argument and
     convert it to *note type: 3a6f.  Rather than storing the converted
     value(s) anywhere, though, *note optparse: c4. passes it to your
     callback function.

*note nargs: 3a9b.

     also has its usual meaning: if it is supplied and > 1, *note
     optparse: c4. will consume *note nargs: 3a9b. arguments, each of
     which must be convertible to *note type: 3a6f.  It then passes a
     tuple of converted values to your callback.

*note callback_args: 3a9f.

     a tuple of extra positional arguments to pass to the callback

*note callback_kwargs: 3aa0.

     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.1.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: c4. will only expect an argument if *note type: 3a6f. is
     set; the type of ‘value’ will be the type implied by the option’s
     type.  If *note type: 3a6f. for this option is ‘None’ (no argument
     expected), then ‘value’ will be ‘None’.  If *note nargs: 3a9b. > 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 ‘parse_args()’.)

     ‘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: c4. 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: 3a9f. option attribute.

‘kwargs’

     is a dictionary of arbitrary keyword arguments supplied via *note
     callback_kwargs: 3aa0.


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.1.31 Raising errors in a callback
......................................

The callback function should raise ‘OptionValueError’ if there are any
problems with the option or its argument(s).  *note optparse: c4.
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.1.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.1.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.1.34 Callback example 3: check option order (generalized)
..............................................................

If you want to re-use 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.1.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.1.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: 3a6f, then the option takes one
argument that must be convertible to that type; if you further define
*note nargs: 3a9b, then the option takes *note nargs: 3a9b. 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: c4. 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.1.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:
c4. 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: c4. 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: c4.
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,  Prev: Option Callbacks,  Up: optparse --- Parser for command line options

5.36.1.38 Extending ‘optparse’
..............................

Since the two major controlling factors in how *note optparse: c4.
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.1.39 Adding new types
..........................

To add new types, you need to define your own subclass of *note
optparse: c4.’s ‘Option’ class.  This class has a couple of attributes
that define *note optparse: c4.’s types: *note TYPES: 3ac9. and *note
TYPE_CHECKER: 3aca.

 -- 屬性: Option.TYPES

     A tuple of type names; in your subclass, simply define a new tuple
     *note TYPES: 3ac9. 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 ‘Option’ 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
     ‘OptionParser.parse_args()’, or be passed to a callback as the
     ‘value’ parameter.

     Your type-checking function should raise ‘OptionValueError’ if it
     encounters any problems.  ‘OptionValueError’ takes a single string
     argument, which is passed as-is to *note OptionParser: 3a63.’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: c4. 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: 3aca. 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(): 26. of *note Option.TYPE_CHECKER:
3aca, we would end up modifying the *note TYPE_CHECKER: 3aca. attribute
of *note optparse: c4.’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: c4.-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.1.40 Adding new actions
............................

Adding new actions is a bit trickier, because you have to understand
that *note optparse: c4. has a couple of classifications for actions:

"store" actions

     actions that result in *note optparse: c4. storing a value to an
     attribute of the current OptionValues instance; these options
     require a *note dest: 3a70. 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: 3a6f. 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: c4. assigns the default type, ‘"string"’, to
     options with no explicit type whose action is listed in *note
     ALWAYS_TYPED_ACTIONS: 3ad0.

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: 3ace. and
     *note TYPED_ACTIONS: 3acf.

   * to ensure that *note optparse: c4. assigns the default type of
     ‘"string"’ to ‘"extend"’ actions, we put the ‘"extend"’ action in
     *note ALWAYS_TYPED_ACTIONS: 3ad0. as well.

   * ‘MyOption.take_action()’ implements just this one new action, and
     passes control back to ‘Option.take_action()’ for the standard
     *note optparse: c4. 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(): 44d. 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: imp --- Access the import internals,  Prev: optparse --- Parser for command line options,  Up: Superseded Modules

5.36.2 ‘imp’ — Access the import internals
------------------------------------------

`Source code:' Lib/imp.py(1)

3.4 版後已棄用: The *note imp: 9a. module is deprecated in favor of
*note importlib: 9b.

__________________________________________________________________

This module provides an interface to the mechanisms used to implement
the *note import: c22. statement.  It defines the following constants
and functions:

 -- 函式: imp.get_magic ()

     Return the magic string value used to recognize byte-compiled code
     files (‘.pyc’ files).  (This value may be different for each Python
     version.)

     3.4 版後已棄用: Use *note importlib.util.MAGIC_NUMBER: 867.
     instead.

 -- 函式: imp.get_suffixes ()

     Return a list of 3-element tuples, each describing a particular
     type of module.  Each triple has the form ‘(suffix, mode, type)’,
     where `suffix' is a string to be appended to the module name to
     form the filename to search for, `mode' is the mode string to pass
     to the built-in *note open(): 4f5. function to open the file (this
     can be ‘'r'’ for text files or ‘'rb'’ for binary files), and `type'
     is the file type, which has one of the values *note PY_SOURCE:
     3ad4, *note PY_COMPILED: 3ad5, or *note C_EXTENSION: 3ad6,
     described below.

     3.3 版後已棄用: Use the constants defined on *note
     importlib.machinery: 9d. instead.

 -- 函式: imp.find_module (name[, path])

     Try to find the module `name'.  If `path' is omitted or ‘None’, the
     list of directory names given by ‘sys.path’ is searched, but first
     a few special places are searched: the function tries to find a
     built-in module with the given name (*note C_BUILTIN: 3ad8.), then
     a frozen module (*note PY_FROZEN: 3ad9.), and on some systems some
     other places are looked in as well (on Windows, it looks in the
     registry which may point to a specific file).

     Otherwise, `path' must be a list of directory names; each directory
     is searched for files with any of the suffixes returned by *note
     get_suffixes(): 3ad3. above.  Invalid names in the list are
     silently ignored (but all list items must be strings).

     If search is successful, the return value is a 3-element tuple
     ‘(file, pathname, description)’:

     `file' is an open *note file object: b47. positioned at the
     beginning, `pathname' is the pathname of the file found, and
     `description' is a 3-element tuple as contained in the list
     returned by *note get_suffixes(): 3ad3. describing the kind of
     module found.

     If the module is built-in or frozen then `file' and `pathname' are
     both ‘None’ and the `description' tuple contains empty strings for
     its suffix and mode; the module type is indicated as given in
     parentheses above.  If the search is unsuccessful, *note
     ImportError: 339. is raised.  Other exceptions indicate problems
     with the arguments or environment.

     If the module is a package, `file' is ‘None’, `pathname' is the
     package path and the last item in the `description' tuple is *note
     PKG_DIRECTORY: 3ada.

     This function does not handle hierarchical module names (names
     containing dots).  In order to find `P.M', that is, submodule `M'
     of package `P', use *note find_module(): 3ad7. and *note
     load_module(): 3adb. to find and load package `P', and then use
     *note find_module(): 3ad7. with the `path' argument set to
     ‘P.__path__’.  When `P' itself has a dotted name, apply this recipe
     recursively.

     3.3 版後已棄用: Use *note importlib.util.find_spec(): 93d. instead
     unless Python 3.3 compatibility is required, in which case use
     *note importlib.find_loader(): 93c.  For example usage of the
     former case, see the *note Examples: 379a. section of the *note
     importlib: 9b. documentation.

 -- 函式: imp.load_module (name, file, pathname, description)

     Load a module that was previously found by *note find_module():
     3ad7. (or by an otherwise conducted search yielding compatible
     results).  This function does more than importing the module: if
     the module was already imported, it will reload the module!  The
     `name' argument indicates the full module name (including the
     package name, if this is a submodule of a package).  The `file'
     argument is an open file, and `pathname' is the corresponding file
     name; these can be ‘None’ and ‘''’, respectively, when the module
     is a package or not being loaded from a file.  The `description'
     argument is a tuple, as would be returned by *note get_suffixes():
     3ad3, describing what kind of module must be loaded.

     If the load is successful, the return value is the module object;
     otherwise, an exception (usually *note ImportError: 339.) is
     raised.

     `Important:' the caller is responsible for closing the `file'
     argument, if it was not ‘None’, even when an exception is raised.
     This is best done using a *note try: d77. ...  *note finally: 183.
     statement.

     3.3 版後已棄用: If previously used in conjunction with *note
     imp.find_module(): 3ad7. then consider using *note
     importlib.import_module(): b18, otherwise use the loader returned
     by the replacement you chose for *note imp.find_module(): 3ad7.  If
     you called *note imp.load_module(): 3adb. and related functions
     directly with file path arguments then use a combination of *note
     importlib.util.spec_from_file_location(): 55e. and *note
     importlib.util.module_from_spec(): 6f5.  See the *note Examples:
     379a. section of the *note importlib: 9b. documentation for details
     of the various approaches.

 -- 函式: imp.new_module (name)

     Return a new empty module object called `name'.  This object is
     `not' inserted in ‘sys.modules’.

     3.4 版後已棄用: Use *note importlib.util.module_from_spec(): 6f5.
     instead.

 -- 函式: imp.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 (the
     same as the `module' argument).

     When ‘reload(module)’ is executed:

        * Python modules’ code is recompiled and the module-level code
          reexecuted, defining a new set of objects which are bound to
          names in the module’s dictionary.  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: d77. statement
     it can test for the table’s presence and skip its initialization if
     desired:

          try:
              cache
          except NameError:
              cache = {}

     It is legal though generally not very useful to reload built-in or
     dynamically loaded modules, except for *note sys: fe, *note
     __main__: 1. and *note builtins: 13.  In many cases, however,
     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:
     c4a. ...  *note import: c22. ..., calling *note reload(): c75. 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.3 版更變: Relies on both ‘__name__’ and ‘__loader__’ being
     defined on the module being reloaded instead of just ‘__name__’.

     3.4 版後已棄用: Use *note importlib.reload(): 39e. instead.

The following functions are conveniences for handling PEP 3147(2)
byte-compiled file paths.

3.2 版新加入.

 -- 函式: imp.cache_from_source (path, debug_override=None)

     Return the PEP 3147(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 *note
     get_tag(): 3ade.; if ‘sys.implementation.cache_tag’ is not defined
     then *note NotImplementedError: 613. will be raised).  By passing
     in ‘True’ or ‘False’ for `debug_override' you can override the
     system’s value for ‘__debug__’, leading to optimized bytecode.

     `path' need not exist.

     3.3 版更變: If ‘sys.implementation.cache_tag’ is ‘None’, then *note
     NotImplementedError: 613. is raised.

     3.4 版後已棄用: Use *note importlib.util.cache_from_source(): 55c.
     instead.

     3.5 版更變: The `debug_override' parameter no longer creates a
     ‘.pyo’ file.

 -- 函式: imp.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) format, a *note ValueError: 1fc. is
     raised.  If ‘sys.implementation.cache_tag’ is not defined, *note
     NotImplementedError: 613. is raised.

     3.3 版更變: Raise *note NotImplementedError: 613. when
     ‘sys.implementation.cache_tag’ is not defined.

     3.4 版後已棄用: Use *note importlib.util.source_from_cache(): 55d.
     instead.

 -- 函式: imp.get_tag ()

     Return the PEP 3147(6) magic tag string matching this version of
     Python’s magic number, as returned by *note get_magic(): 868.

     3.4 版後已棄用: Use ‘sys.implementation.cache_tag’ directly
     starting in Python 3.3.

The following functions help interact with the import system’s internal
locking mechanism.  Locking semantics of imports are an implementation
detail which may vary from release to release.  However, Python ensures
that circular imports work without any deadlocks.

 -- 函式: imp.lock_held ()

     Return ‘True’ if the global import lock is currently held, else
     ‘False’.  On platforms without threads, always return ‘False’.

     On platforms with threads, a thread executing an import first holds
     a global import lock, then sets up a per-module lock for the rest
     of the import.  This blocks other threads from importing the same
     module until the original import completes, preventing other
     threads from seeing incomplete module objects constructed by the
     original thread.  An exception is made for circular imports, which
     by construction have to expose an incomplete module object at some
     point.

     3.3 版更變: The locking scheme has changed to per-module locks for
     the most part.  A global import lock is kept for some critical
     tasks, such as initializing the per-module locks.

     3.4 版後已棄用.

 -- 函式: imp.acquire_lock ()

     Acquire the interpreter’s global import lock for the current
     thread.  This lock should be used by import hooks to ensure
     thread-safety when importing modules.

     Once a thread has acquired the import lock, the same thread may
     acquire it again without blocking; the thread must release it once
     for each time it has acquired it.

     On platforms without threads, this function does nothing.

     3.3 版更變: The locking scheme has changed to per-module locks for
     the most part.  A global import lock is kept for some critical
     tasks, such as initializing the per-module locks.

     3.4 版後已棄用.

 -- 函式: imp.release_lock ()

     Release the interpreter’s global import lock.  On platforms without
     threads, this function does nothing.

     3.3 版更變: The locking scheme has changed to per-module locks for
     the most part.  A global import lock is kept for some critical
     tasks, such as initializing the per-module locks.

     3.4 版後已棄用.

The following constants with integer values, defined in this module, are
used to indicate the search result of *note find_module(): 3ad7.

 -- Data: imp.PY_SOURCE

     The module was found as a source file.

     3.3 版後已棄用.

 -- Data: imp.PY_COMPILED

     The module was found as a compiled code object file.

     3.3 版後已棄用.

 -- Data: imp.C_EXTENSION

     The module was found as dynamically loadable shared library.

     3.3 版後已棄用.

 -- Data: imp.PKG_DIRECTORY

     The module was found as a package directory.

     3.3 版後已棄用.

 -- Data: imp.C_BUILTIN

     The module was found as a built-in module.

     3.3 版後已棄用.

 -- Data: imp.PY_FROZEN

     The module was found as a frozen module.

     3.3 版後已棄用.

 -- 類別: imp.NullImporter (path_string)

     The *note NullImporter: 9c0. type is a PEP 302(7) import hook that
     handles non-directory path strings by failing to find any modules.
     Calling this type with an existing directory or empty string raises
     *note ImportError: 339.  Otherwise, a *note NullImporter: 9c0.
     instance is returned.

     Instances have only one method:

      -- 成員函式: find_module (fullname[, path])

          This method always returns ‘None’, indicating that the
          requested module could not be found.

     3.3 版更變: ‘None’ is inserted into ‘sys.path_importer_cache’
     instead of an instance of *note NullImporter: 9c0.

     3.4 版後已棄用: Insert ‘None’ into ‘sys.path_importer_cache’
     instead.

* Menu:

* Examples: Examples<33>.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Lib/imp.py

   (2) https://www.python.org/dev/peps/pep-3147

   (3) https://www.python.org/dev/peps/pep-3147

   (4) https://www.python.org/dev/peps/pep-3147

   (5) https://www.python.org/dev/peps/pep-3147

   (6) https://www.python.org/dev/peps/pep-3147

   (7) https://www.python.org/dev/peps/pep-0302


File: python.info,  Node: Examples<33>,  Up: imp --- Access the import internals

5.36.2.1 Examples
.................

The following function emulates what was the standard import statement
up to Python 1.4 (no hierarchical module names).  (This `implementation'
wouldn’t work in that version, since *note find_module(): 3ad7. has been
extended and *note load_module(): 3adb. has been added in 1.4.)

     import imp
     import sys

     def __import__(name, globals=None, locals=None, fromlist=None):
         # Fast path: see if the module has already been imported.
         try:
             return sys.modules[name]
         except KeyError:
             pass

         # If any of the following calls raises an exception,
         # there's a problem we can't handle -- let the caller handle it.

         fp, pathname, description = imp.find_module(name)

         try:
             return imp.load_module(name, fp, pathname, description)
         finally:
             # Since we may exit via an exception, close fp explicitly.
             if fp:
                 fp.close()


File: python.info,  Node: Undocumented Modules,  Prev: Superseded Modules,  Up: Python 標準函式庫 Standard Library

5.37 Undocumented Modules
=========================

Here’s a quick listing of modules that are currently undocumented, but
that should be documented.  Feel free to contribute documentation for
them!  (Send via email to <docs@python.org>.)

The idea and original contents for this chapter were taken from a
posting by Fredrik Lundh; the specific contents of this chapter have
been substantially revised.

* Menu:

* Platform specific modules::


File: python.info,  Node: Platform specific modules,  Up: Undocumented Modules

5.37.1 Platform specific modules
--------------------------------

These modules are used to implement the *note os.path: c6. module, and
are not documented beyond this mention.  There’s little need to document
these.

‘ntpath’

     — Implementation of *note os.path: c6. on Win32 and Win64
     platforms.

‘posixpath’

     — Implementation of *note os.path: c6. on POSIX.


File: python.info,  Node: Extending and Embedding the Python Interpreter,  Next: Python / C API 參考手冊,  Prev: Python 標準函式庫 Standard Library,  Up: Top

6 Extending and Embedding the Python Interpreter
************************************************

This document describes how to write modules in C or C++ to extend the
Python interpreter with new modules.  Those modules can not only define
new functions but also new object types and their methods.  The document
also describes how to embed the Python interpreter in another
application, for use as an extension language.  Finally, it shows how to
compile and link extension modules so that they can be loaded
dynamically (at run time) into the interpreter, if the underlying
operating system supports this feature.

This document assumes basic knowledge about Python.  For an informal
introduction to the language, see *note Python 教學: 11ff.  *note The
Python Language Reference: 1201. gives a more formal definition of the
language.  *note Python 標準函式庫 (Standard Library): 1200. documents
the existing object types, functions and modules (both built-in and
written in Python) that give the language its wide application range.

For a detailed description of the whole Python/C API, see the separate
*note Python / C API 參考手冊: 1203.

* Menu:

* Recommended third party tools::
* Creating extensions without third party tools::
* Embedding the CPython runtime in a larger application::


File: python.info,  Node: Recommended third party tools,  Next: Creating extensions without third party tools,  Up: Extending and Embedding the Python Interpreter

6.1 Recommended third party tools
=================================

This guide only covers the basic tools for creating extensions provided
as part of this version of CPython.  Third party tools like Cython(1),
cffi(2), SWIG(3) and Numba(4) offer both simpler and more sophisticated
approaches to creating C and C++ extensions for Python.

也參考
......

Python Packaging User Guide: Binary Extensions(5)

     The Python Packaging User Guide not only covers several available
     tools that simplify the creation of binary extensions, but also
     discusses the various reasons why creating an extension module may
     be desirable in the first place.

   ---------- Footnotes ----------

   (1) http://cython.org/

   (2) https://cffi.readthedocs.io

   (3) http://www.swig.org

   (4) https://numba.pydata.org/

   (5) https://packaging.python.org/guides/packaging-binary-extensions/


File: python.info,  Node: Creating extensions without third party tools,  Next: Embedding the CPython runtime in a larger application,  Prev: Recommended third party tools,  Up: Extending and Embedding the Python Interpreter

6.2 Creating extensions without third party tools
=================================================

This section of the guide covers creating C and C++ extensions without
assistance from third party tools.  It is intended primarily for
creators of those tools, rather than being a recommended way to create
your own C extensions.

* Menu:

* 以 C 或 C++ 擴充 Python::
* Defining Extension Types; Tutorial: Defining Extension Types Tutorial.
* Defining Extension Types; Assorted Topics: Defining Extension Types Assorted Topics.
* Building C and C++ Extensions::
* Building C and C++ Extensions on Windows::


File: python.info,  Node: 以 C 或 C++ 擴充 Python,  Next: Defining Extension Types Tutorial,  Up: Creating extensions without third party tools

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: 2b. 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:

* A Simple Example::
* Intermezzo; Errors and Exceptions: Intermezzo Errors and Exceptions.
* Back to the Example::
* 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: A Simple Example,  Next: Intermezzo Errors and Exceptions,  Up: 以 C 或 C++ 擴充 Python

6.2.1.1 A Simple Example
........................

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.

     It is recommended to always define ‘PY_SSIZE_T_CLEAN’ before
     including ‘Python.h’.  See *note Extracting Parameters in Extension
     Functions: 3af3. 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(): 26b. 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(): 26b. 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) (1) An interface for this function already exists in the standard
module *note os: c5. — it was chosen as a simple and straightforward
example.


File: python.info,  Node: Intermezzo Errors and Exceptions,  Next: Back to the Example,  Prev: A Simple Example,  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 a ‘NULL’ pointer).  Exceptions are
stored in a static global variable inside the interpreter; if this
variable is ‘NULL’ no exception has occurred.  A second global variable
stores the "associated value" of the exception (the second argument to
*note raise: c47.).  A third variable contains the stack traceback in
case the error originated in Python code.  These three variables are the
C equivalents of the result in Python of *note sys.exc_info(): c64. (see
the section on module *note sys: fe. in the Python Library Reference).
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(): 3af6.  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(): 3af7, 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(): 3af8, which takes two object arguments, the
exception and its associated value.  You don’t need to *note
Py_INCREF(): 266. the objects passed to any of these functions.

You can test non-destructively whether an exception has been set with
*note PyErr_Occurred(): 3af9.  This returns the current exception
object, or ‘NULL’ if no exception has occurred.  You normally don’t need
to call *note PyErr_Occurred(): 3af9. 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():
970.  The only time C code should call *note PyErr_Clear(): 970. 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(): 3afa. and return a failure indicator itself.  All the
object-creating functions (for example, *note PyLong_FromLong(): 3afb.)
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(): 26b. 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():
269. or *note Py_DECREF(): 267. 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_IOError’).  If something’s wrong with the argument
list, the *note PyArg_ParseTuple(): 26b. 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);
         Py_XINCREF(SpamError);
         if (PyModule_AddObject(m, "error", SpamError) < 0) {
             Py_XDECREF(SpamError);
             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(): c05. function may create a class with the
base class being *note Exception: 1aa. (unless another class is passed
in instead of ‘NULL’), described in *note 內建的例外: 12b3.

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 ‘PyMODINIT_FUNC’ 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(): 3af6. 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: Back to the Example,  Next: The Module's Method Table and Initialization Function,  Prev: Intermezzo Errors and Exceptions,  Up: 以 C 或 C++ 擴充 Python

6.2.1.3 Back to the Example
...........................

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(): 26b.  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(): 26b.:

     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(): 3afb.

     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: ddb. macro):

     Py_INCREF(Py_None);
     return Py_None;

*note Py_None: 3afe. 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: Back to the Example,  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(): 26b. 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(): 26b.; more information on this
function is provided below.

The ‘METH_KEYWORDS’ 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(): 5cf.
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 PyMODINIT_FUNC 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(): 3b01, 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: e20.
structures) found in the module definition.  *note PyModule_Create():
3b01. 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(): 3b02, optionally followed by an import of the
module:

     int
     main(int argc, char *argv[])
     {
         wchar_t *program = Py_DecodeLocale(argv[0], NULL);
         if (program == NULL) {
             fprintf(stderr, "Fatal error: cannot decode argv[0]\n");
             exit(1);
         }

         /* 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 */
         Py_SetProgramName(program);

         /* Initialize the Python interpreter.  Required.
            If this step fails, it will be a fatal error. */
         Py_Initialize();

         /* 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");
         }

         ...

         PyMem_RawFree(program);
         return 0;
     }

     備註: 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://www.python.org/dev/peps/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 Building C and C++ Extensions: 3b05.) and additional information
that pertains only to building on Windows (chapter *note Building C and
C++ Extensions on Windows: 13a1.) 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:
1210. 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(): 266. 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: e4d. flag; this is described in section *note The Module’s
Method Table and Initialization Function: 3aff.  The *note
PyArg_ParseTuple(): 26b. function and its arguments are documented in
section *note Extracting Parameters in Extension Functions: 3af3.

The macros *note Py_XINCREF(): 268. and *note Py_XDECREF(): 269.
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:
3b08.

Later, when it is time to call the function, you call the C function
*note PyObject_CallObject(): 3b09.  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(): 2cf. 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(): 3b09. returns a Python object pointer: this
is the return value of the Python function.  *note
PyObject_CallObject(): 3b09. 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(): 267.-ed immediately after
the *note PyObject_CallObject(): 3b09. call.

The return value of *note PyObject_CallObject(): 3b09. 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(): 267. 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():
3b09. 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(): 970.  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(): 3b09.  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(): 2cf.  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(): 2cf. may run out of memory, and
this should be checked.

You may also call a function with keyword arguments by using *note
PyObject_Call(): 3b0a, which supports arguments and keyword arguments.
As in the above example, we use *note Py_BuildValue(): 2cf. 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(): 26b. 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 Parsing arguments and
building values: 2d1. 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(): 26b. 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!

Some example calls:

     #define PY_SSIZE_T_CLEAN  /* Make "s#" use Py_ssize_t rather than int. */
     #include <Python.h>

     int ok;
     int i, j;
     long k, l;
     const char *s;
     Py_ssize_t size;

     ok = PyArg_ParseTuple(args, ""); /* No arguments */
         /* Python call: 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(): 5cf. function is declared as
follows:

     int PyArg_ParseTupleAndKeywords(PyObject *arg, PyObject *kwdict,
                                     const char *format, char *kwlist[], ...);

The `arg' and `format' parameters are identical to those of the *note
PyArg_ParseTuple(): 26b. 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(): 5cf. 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: 193. 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  /* Make "s#" use Py_ssize_t rather than int. */
     #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(): 26b.  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(): 26b, 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(): 26b.: while the latter
requires its first argument to be a tuple (since Python argument lists
are always represented as tuples internally), *note Py_BuildValue():
2cf. 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 re-use 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: 86. module exposes a way to run the detector (the
*note collect(): 22f. function), as well as configuration interfaces and
the ability to disable the detector at runtime.  The cycle detector is
considered an optional component; though it is included by default, it
can be disabled at build time using the ‘--without-cycle-gc’ option to
the ‘configure’ script on Unix platforms (including Mac OS X). If the
cycle detector is disabled in this way, the *note gc: 86. module will
not be available.

* Menu:

* Reference Counting in Python::
* Ownership Rules::
* Thin Ice::
* NULL Pointers::


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(): 267. 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():
267. 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(): 267.
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(): 267.  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(): 266.  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) (2) The metaphor of "borrowing" a reference is not completely
correct: the owner still has a copy of the reference.

   (2) (3) 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(): 3afb. and *note
Py_BuildValue(): 2cf, 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(): 3afb.
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(): 3b15.  The picture is less clear, here,
however, since a few common routines are exceptions: *note
PyTuple_GetItem(): 3b16, *note PyList_GetItem(): 3b17, *note
PyDict_GetItem(): 3b18, and *note PyDict_GetItemString(): 3b19. all
return references that you borrow from the tuple, list or dictionary.

The function *note PyImport_AddModule(): 3b1a. 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(): 266. to become an independent owner.  There
are exactly two important exceptions to this rule: *note
PyTuple_SetItem(): 3b1b. and *note PyList_SetItem(): 3b1c.  These
functions take over ownership of the item passed to them — even if they
fail!  (Note that *note PyDict_SetItem(): 3b1d. 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(): 266.

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 Pointers,  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(): 267. 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(): 3b1c.  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 *note __del__(): 924. method.  If this
class instance has a reference count of 1, disposing of it will call its
*note __del__(): 924. method.

Since it is written in Python, the *note __del__(): 924. 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 *note __del__(): 924.
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 *note __del__(): 924. 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: 3b20,
and to re-acquire it using *note Py_END_ALLOW_THREADS: 2b6.  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 Pointers,  Prev: Thin Ice,  Up: Reference Counts

6.2.1.14 NULL Pointers
......................

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(): 266. and *note Py_DECREF(): 267. do not
check for ‘NULL’ pointers — however, their variants *note Py_XINCREF():
268. and *note Py_XDECREF(): 269. 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) (4) 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:
3aff.).  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(): 3b26. 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(): 3b27. 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 A Simple Example: 3af2.  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_AddObject(m, "_C_API", c_api_object) < 0) {
             Py_XDECREF(c_api_object);
             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: 3b28. 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: Creating extensions without third party tools

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: 335. and *note list: 263. 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: 143b. runtime sees all Python objects as variables of
type *note PyObject*: 4bf, which serves as a "base type" for all Python
objects.  The *note PyObject: 4bf. structure itself only contains the
object’s *note reference count: 3b2e. 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(): 2d2. 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 = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "custom.Custom",
         .tp_doc = "Custom objects",
         .tp_basicsize = sizeof(CustomObject),
         .tp_itemsize = 0,
         .tp_flags = Py_TPFLAGS_DEFAULT,
         .tp_new = PyType_GenericNew,
     };

     static PyModuleDef custommodule = {
         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;

         Py_INCREF(&CustomType);
         if (PyModule_AddObject(m, "Custom", (PyObject *) &CustomType) < 0) {
             Py_DECREF(&CustomType);
             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: 4bf, containing a pointer to a type object and a
reference count (these can be accessed using the macros *note Py_REFCNT:
3b2f. and *note Py_TYPE: 3b30. respectively).  The reason for the macro
is to abstract away the layout and to enable additional fields in debug
builds.

     備註: There is no semicolon above after the *note PyObject_HEAD:
     c77. 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 = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "custom.Custom",
         .tp_doc = "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: 2d7. fields
     that you don’t care about and also to avoid caring about the
     fields’ declaration order.

The actual definition of *note PyTypeObject: 2d7. in ‘object.h’ has many
more *note fields: 3b31. 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:

     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: da. and *note pickle: cb.
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: 3b32. 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: 3b33. 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__: e0e, or else it will not be able to call your type’s
     *note __new__(): 88e. method without getting an error.  You can
     avoid this problem by ensuring that your type has a larger value
     for *note tp_basicsize: 3b33. than its base type does.  Most of the
     time, this will be true anyway, because either your base type will
     be *note object: 2b1, 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: 3b34.

     .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: 3b35.

     .tp_doc = "Custom objects",

To enable object creation, we have to provide a *note tp_new: 3b36.
handler.  This is the equivalent of the Python method *note __new__():
88e, but has to be specified explicitly.  In this case, we can just use
the default implementation provided by the API function *note
PyType_GenericNew(): 3b37.

     .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 ‘ob_type’ that we initially
set to ‘NULL’.

     Py_INCREF(&CustomType);
     if (PyModule_AddObject(m, "Custom", (PyObject *) &CustomType) < 0) {
         Py_DECREF(&CustomType);
         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’ and:

     from distutils.core import setup, Extension
     setup(name="custom", version="1.0",
           ext_modules=[Extension("custom", ["custom.c"])])

in a file called ‘setup.py’; then typing

     $ python setup.py build

at a shell should produce a file ‘custom.so’ in a subdirectory; move to
that directory and 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.

     備註: While this documentation showcases the standard *note
     distutils: 39. module for building C extensions, it is recommended
     in real-world use cases to use the newer and better-maintained
     ‘setuptools’ library.  Documentation on how to do this is out of
     scope for this document and can be found in the Python Packaging
     User’s Guide(1).

   ---------- Footnotes ----------

   (1) https://packaging.python.org/tutorials/distributing-packages/


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 "structmember.h"

     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, *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;
     }

     static PyMemberDef Custom_members[] = {
         {"first", T_OBJECT_EX, offsetof(CustomObject, first), 0,
          "first name"},
         {"last", T_OBJECT_EX, offsetof(CustomObject, last), 0,
          "last name"},
         {"number", 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 = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "custom2.Custom",
         .tp_doc = "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 = {
         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;

         Py_INCREF(&CustomType);
         if (PyModule_AddObject(m, "Custom", (PyObject *) &CustomType) < 0) {
             Py_DECREF(&CustomType);
             Py_DECREF(m);
             return NULL;
         }

         return m;
     }

This version of the module has a number of changes.

We’ve added an extra include:

     #include <structmember.h>

This include provides declarations that we use to handle attributes, as
described a bit later.

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: 3b39. member:

     .tp_dealloc = (destructor) Custom_dealloc,

This method first clears the reference counts of the two Python
attributes.  *note Py_XDECREF(): 269. 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: 3b3a. 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: 3b36. 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__(): 88e. method.  It is not required to define a ‘tp_new’ member,
and indeed many extension types will simply reuse *note
PyType_GenericNew(): 3b37. 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: 3b3b. slot to
allocate memory:

     self = (CustomObject *) type->tp_alloc(type, 0);

Since memory allocation may fail, we must check the *note tp_alloc:
3b3b. result against ‘NULL’ before proceeding.

     備註: We didn’t fill the *note tp_alloc: 3b3b. slot ourselves.
     Rather *note PyType_Ready(): 3b3c. fills it for us by inheriting it
     from our base class, which is *note object: 2b1. by default.  Most
     types use the default allocation strategy.

     備註: If you are creating a co-operative *note tp_new: 3b36. (one
     that calls a base type’s *note tp_new: 3b36. or *note __new__():
     88e.), 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: 3b36.
     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: 193.)

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: 3b3d. slot.

     .tp_init = (initproc) Custom_init,

The *note tp_init: 3b3d. slot is exposed in Python as the *note
__init__(): d63. 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: cb. module by default
doesn’t call *note __init__(): d63. on unpickled instances).  It can
also be called multiple times.  Anyone can call the *note __init__():
d63. 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: bef. 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: bef. nor cause any calls back into our
     type’s code;

   * when decrementing a reference count in a *note tp_dealloc: 3b39.
     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", T_OBJECT_EX, offsetof(CustomObject, first), 0,
          "first name"},
         {"last", T_OBJECT_EX, offsetof(CustomObject, last), 0,
          "last name"},
         {"number", T_INT, offsetof(CustomObject, number), 0,
          "custom number"},
         {NULL}  /* Sentinel */
     };

and put the definitions in the *note tp_members: 3b3e. 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: 3b3f.
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: e1d. flag to indicate that the
method is expecting no arguments other than `self')

and assign it to the *note tp_methods: 3b40. 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: 3b41. 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: 3b42. struct, and update the full class
name in the *note PyTypeObject: 2d7. struct.

Finally, we update our ‘setup.py’ file to build the new module:

     from distutils.core import setup, Extension
     setup(name="custom", version="1.0",
           ext_modules=[
              Extension("custom", ["custom.c"]),
              Extension("custom2", ["custom2.c"]),
              ])

   ---------- Footnotes ----------

   (1) (1) This is true when we know that the object is a basic type,
like a string or a float.

   (2) (2) We relied on this in the *note tp_dealloc: 3b39. 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 "structmember.h"

     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, *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;
     }

     static PyMemberDef Custom_members[] = {
         {"number", T_INT, offsetof(CustomObject, number), 0,
          "custom number"},
         {NULL}  /* Sentinel */
     };

     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;
     }

     static PyObject *
     Custom_getlast(CustomObject *self, void *closure)
     {
         Py_INCREF(self->last);
         return self->last;
     }

     static int
     Custom_setlast(CustomObject *self, PyObject *value, void *closure)
     {
         PyObject *tmp;
         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;
         }
         tmp = self->last;
         Py_INCREF(value);
         self->last = value;
         Py_DECREF(tmp);
         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 = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "custom3.Custom",
         .tp_doc = "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 = {
         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;

         Py_INCREF(&CustomType);
         if (PyModule_AddObject(m, "Custom", (PyObject *) &CustomType) < 0) {
             Py_DECREF(&CustomType);
             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: 42c. 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: 3b44. slot:

     .tp_getset = Custom_getsetters,

The last item in a *note PyGetSetDef: 42c. 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", T_INT, offsetof(CustomObject, number), 0,
          "custom number"},
         {NULL}  /* Sentinel */
     };

We also need to update the *note tp_init: 3b3d. 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(): 269. calls can
be converted to *note Py_DECREF(): 267. 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) (3) 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): ecd. 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 "structmember.h"

     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, *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;
     }

     static PyMemberDef Custom_members[] = {
         {"number", T_INT, offsetof(CustomObject, number), 0,
          "custom number"},
         {NULL}  /* Sentinel */
     };

     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)
     {
         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_INCREF(value);
         Py_CLEAR(self->first);
         self->first = value;
         return 0;
     }

     static PyObject *
     Custom_getlast(CustomObject *self, void *closure)
     {
         Py_INCREF(self->last);
         return 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_INCREF(value);
         Py_CLEAR(self->last);
         self->last = 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 = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "custom4.Custom",
         .tp_doc = "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 = {
         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;

         Py_INCREF(&CustomType);
         if (PyModule_AddObject(m, "Custom", (PyObject *) &CustomType) < 0) {
             Py_DECREF(&CustomType);
             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(): 3b46. macro that automates calling
visit functions.  With *note Py_VISIT(): 3b46, 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: 36be. implementation must name its
     arguments exactly `visit' and `arg' in order to use *note
     Py_VISIT(): 3b46.

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(): 3b47. 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(): 269. 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(): 3b47. 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(): 3b47. 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():
e4a. before clearing members.  Here is our reimplemented deallocator
using *note PyObject_GC_UnTrack(): e4a. 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: 3b48. 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: 3b3b.
or *note tp_free: 3b3a. handlers, we’d need to modify them for cyclic
garbage collection.  Most extensions will use the versions automatically
provided.

   ---------- Footnotes ----------

   (1) (4) Also, even with our attributes restricted to strings
instances, the user could pass arbitrary *note str: 335. 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: 2d7. it needs.  It
can be difficult to share these *note PyTypeObject: 2d7. structures
between extension modules.

In this example we will create a ‘SubList’ type that inherits from the
built-in *note list: 263. 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 = "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;

         Py_INCREF(&SubListType);
         if (PyModule_AddObject(m, "SubList", (PyObject *) &SubListType) < 0) {
             Py_DECREF(&SubListType);
             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(): c77. 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__: d63. method of
the base type.

This pattern is important when writing a type with custom *note tp_new:
3b36. and *note tp_dealloc: 3b39. members.  The *note tp_new: 3b36.
handler should not actually create the memory for the object with its
*note tp_alloc: 3b3b, but let the base class handle it by calling its
own *note tp_new: 3b36.

The *note PyTypeObject: 2d7. struct supports a *note tp_base: 3b4a.
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: 3b4b.; 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;

         Py_INCREF(&SubListType);
         if (PyModule_AddObject(m, "SubList", (PyObject *) &SubListType) < 0) {
             Py_DECREF(&SubListType);
             Py_DECREF(m);
             return NULL;
         }

         return m;
     }

Before calling *note PyType_Ready(): 3b3c, the type structure must have
the *note tp_base: 3b4a. slot filled in.  When we are deriving an
existing type, it is not necessary to fill out the *note tp_alloc: 3b3b.
slot with *note PyType_GenericNew(): 3b37. – the allocation function
from the base type will be inherited.

After that, calling *note PyType_Ready(): 3b3c. 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: Building C and C++ Extensions,  Prev: Defining Extension Types Tutorial,  Up: Creating extensions without third party tools

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: 2d7, with some fields only
used in debug builds 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 */

         /* call function for all accessible objects */
         traverseproc tp_traverse;

         /* delete references to contained objects */
         inquiry tp_clear;

         /* 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;
         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;

     } 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: 3b32. 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(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():
96f. and *note PyErr_Restore(): 3b51. 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_CallObject(self->my_callback, NULL);
             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: 36be. and/or *note tp_clear:
     3b52.), some of the object’s members can have been cleared or
     finalized by the time *note tp_dealloc: 3b39. is called.  Second,
     in *note tp_dealloc: 3b39, 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: 3b39. 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: 3b39, and instead use the
     new *note tp_finalize: 2d8. type method.

     也參考
     ......

     PEP 442(1) explains the new finalization scheme.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/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(): 7d1. function, and the *note str(): 335.
function.  (The *note print(): 88b. function just calls *note str():
335.)  These handlers are both optional.

     reprfunc tp_repr;
     reprfunc tp_str;

The *note tp_repr: 3b54. 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: 3b54. handler is specified, the interpreter will
supply a representation that uses the type’s *note tp_name: 3b55. and a
uniquely-identifying value for the object.

The *note tp_str: 3b56. handler is to *note str(): 335. what the *note
tp_repr: 3b54. handler described above is to *note repr(): 7d1.; that
is, it is called when Python code calls *note str(): 335. on an instance
of your object.  Its implementation is very similar to the *note
tp_repr: 3b54. function, but the resulting string is intended for human
consumption.  If *note tp_str: 3b56. is not specified, the *note
tp_repr: 3b54. handler is used instead.

Here is a simple example:

     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*: 4bf.  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*: 4bf. 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():
     3b3c. 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(): 3b3c. is called, it uses three tables
referenced by the type object to create *note descriptor: 160b.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: 3b59. and *note tp_setattro: 3b5a. 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: 3b40. is not ‘NULL’, it must refer to an array of
*note PyMethodDef: e20. 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 ‘ml_name’ 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: 160b. will be
constructed and added to the type which will be able to extract a value
from the instance structure.  The *note type: 60d. field should contain
one of the type codes defined in the ‘structmember.h’ header; the value
will be used to determine how to convert Python values to and from C
values.  The ‘flags’ field is used to store flags which control how the
attribute can be accessed.

The following flag constants are defined in ‘structmember.h’; they may
be combined using bitwise-OR.

Constant                        Meaning
                                
-----------------------------------------------------------------------------------
                                
‘READONLY’                      Never writable.
                                
                                
‘READ_RESTRICTED’               Not readable in restricted mode.
                                
                                
‘WRITE_RESTRICTED’              Not writable in restricted mode.
                                
                                
‘RESTRICTED’                    Not readable or writable in restricted mode.
                                

An interesting advantage of using the *note tp_members: 3b3e. 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: 3b40. table, a sentinel entry with a
‘name’ 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*: 4bf. 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: 3b5c. handler is called when the object requires
an attribute look-up.  It is called in the same situations where the
*note __getattr__(): 31f. method of a class would be called.

Here is an example:

     static PyObject *
     newdatatype_getattr(newdatatypeobject *obj, char *name)
     {
         if (strcmp(name, "data") == 0)
         {
             return PyLong_FromLong(obj->data);
         }

         PyErr_Format(PyExc_AttributeError,
                      "'%.50s' object has no attribute '%.400s'",
                      tp->tp_name, name);
         return NULL;
     }

The *note tp_setattr: 3b5d. handler is called when the *note
__setattr__(): e31. or *note __delattr__(): 1435. 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:
3b5d. 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: 3b5f. handler is called when comparisons are
needed.  It is analogous to the *note rich comparison methods: 143d,
like *note __lt__(): c39, and also called by *note
PyObject_RichCompare(): 3b60. and *note PyObject_RichCompareBool(): f4c.

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_GT’, ‘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(PyObject *obj1, PyObject *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
抽象物件層: 3b62.

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: d86, *note
PySequenceMethods: 3b63, or *note PyMappingMethods: 3b64, 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;
     }

‘Py_hash_t’ is a signed integer type with a platform-varying width.
Returning ‘-1’ from *note tp_hash: 3b65. 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: 3b66. 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(): 26b. 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(): 5cf. to extract the arguments.  If
     you do not want to support keyword arguments and this is
     non-‘NULL’, raise a *note TypeError: 193. with a message saying
     that keyword arguments are not supported.

Here is a toy ‘tp_call’ implementation:

     static PyObject *
     newdatatype_call(newdatatypeobject *self, 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;
     }

     /* Iterators */
     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: e35.
corresponds to the Python *note __iter__(): 514. method, while *note
tp_iternext: e36. corresponds to the Python *note __next__(): c69.
method.

Any *note iterable: bb1. object must implement the *note tp_iter: e35.
handler, which must return an *note iterator: 1040. 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: e35.

   * Objects which can only be iterated over once (usually due to side
     effects of iteration, such as file objects) can implement *note
     tp_iter: e35. by returning a new reference to themselves – and
     should also therefore implement the *note tp_iternext: e36.
     handler.

Any *note iterator: 1040. object should implement both *note tp_iter:
e35. and *note tp_iternext: e36.  An iterator’s *note tp_iter: e35.
handler should return a new reference to the iterator.  Its *note
tp_iternext: e36. 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: e36. may return ‘NULL’ without setting an
exception, or it may set *note StopIteration: 48b. `in addition' to
returning ‘NULL’; avoiding the exception can yield slightly better
performance.  If an actual error occurs, *note tp_iternext: e36. 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: 129. module.

For an object to be weakly referencable, the extension type must do two
things:

  1. Include a *note PyObject*: 4bf. field in the C object structure
     dedicated to the weak reference mechanism.  The object’s
     constructor should leave it ‘NULL’ (which is automatic when using
     the default *note tp_alloc: 3b3b.).

  2. Set the *note tp_weaklistoffset: 3b68. type member to the offset of
     the aforementioned field in the C object structure, so that the
     interpreter knows how to access and modify that field.

Concretely, here is how a trivial object structure would be augmented
with the required field:

     typedef struct {
         PyObject_HEAD
         PyObject *weakreflist;  /* List of weak references */
     } TrivialObject;

And the corresponding member in the statically-declared type object:

     static PyTypeObject TrivialType = {
         PyVarObject_HEAD_INIT(NULL, 0)
         /* ... other members omitted for brevity ... */
         .tp_weaklistoffset = offsetof(TrivialObject, weakreflist),
     };

The only further addition is that ‘tp_dealloc’ needs to clear any weak
references (by calling ‘PyObject_ClearWeakRefs()’) if the field is
non-‘NULL’:

     static void
     Trivial_dealloc(TrivialObject *self)
     {
         /* Clear weakrefs first before calling any destructors */
         if (self->weakreflist != NULL)
             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: 143b. 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(): 3b6a.
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: Building C and C++ Extensions,  Next: Building C and C++ Extensions on Windows,  Prev: Defining Extension Types Assorted Topics,  Up: Creating extensions without third party tools

6.2.4 Building C and C++ Extensions
-----------------------------------

A C extension for CPython is a shared library (e.g.  a ‘.so’ file on
Linux, ‘.pyd’ on Windows), which exports an `initialization function'.

To be importable, the shared library must be available on *note
PYTHONPATH: 958, and must be named after the module name, with an
appropriate extension.  When using distutils, the correct filename is
generated automatically.

The initialization function has the signature:

 -- C 函式: PyObject* PyInit_modulename (void)

It returns either a fully-initialized module, or a *note PyModuleDef:
3b42. instance.  See *note Initializing C modules: 3b6e. 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: 3b6f, 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 distutils::
* Distributing your extension modules::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0489


File: python.info,  Node: Building C and C++ Extensions with distutils,  Next: Distributing your extension modules,  Up: Building C and C++ Extensions

6.2.4.1 Building C and C++ Extensions with distutils
....................................................

Extension modules can be built using distutils, which is included in
Python.  Since distutils also supports creation of binary packages,
users don’t necessarily need a compiler and distutils to install the
extension.

A distutils package contains a driver script, ‘setup.py’.  This is a
plain Python file, which, in the most simple case, could look like this:

     from distutils.core import setup, Extension

     module1 = Extension('demo',
                         sources = ['demo.c'])

     setup (name = 'PackageName',
            version = '1.0',
            description = 'This is a demo package',
            ext_modules = [module1])

With this ‘setup.py’, and a file ‘demo.c’, running

     python setup.py build

will compile ‘demo.c’, and produce an extension module named ‘demo’ in
the ‘build’ directory.  Depending on the system, the module file will
end up in a subdirectory ‘build/lib.system’, and may have a name like
‘demo.so’ or ‘demo.pyd’.

In the ‘setup.py’, all execution is performed by calling the ‘setup’
function.  This takes a variable number of keyword arguments, of which
the example above uses only a subset.  Specifically, the example
specifies meta-information to build packages, and it specifies the
contents of the package.  Normally, a package will contain additional
modules, like Python source modules, documentation, subpackages, etc.
Please refer to the distutils documentation in *note 發布 Python
模組（舊版）: 7fd. to learn more about the features of distutils; this
section explains building extension modules only.

It is common to pre-compute arguments to ‘setup()’, to better structure
the driver script.  In the example above, the ‘ext_modules’ argument to
*note setup(): 3b71. is a list of extension modules, each of which is an
instance of the ‘Extension’.  In the example, the instance defines an
extension named ‘demo’ which is build by compiling a single source file,
‘demo.c’.

In many cases, building an extension is more complex, since additional
preprocessor defines and libraries may be needed.  This is demonstrated
in the example below.

     from distutils.core import setup, Extension

     module1 = Extension('demo',
                         define_macros = [('MAJOR_VERSION', '1'),
                                          ('MINOR_VERSION', '0')],
                         include_dirs = ['/usr/local/include'],
                         libraries = ['tcl83'],
                         library_dirs = ['/usr/local/lib'],
                         sources = ['demo.c'])

     setup (name = 'PackageName',
            version = '1.0',
            description = 'This is a demo package',
            author = 'Martin v. Loewis',
            author_email = 'martin@v.loewis.de',
            url = 'https://docs.python.org/extending/building',
            long_description = '''
     This is really just a demo package.
     ''',
            ext_modules = [module1])

In this example, *note setup(): 3b71. is called with additional
meta-information, which is recommended when distribution packages have
to be built.  For the extension itself, it specifies preprocessor
defines, include directories, library directories, and libraries.
Depending on the compiler, distutils passes this information in
different ways to the compiler.  For example, on Unix, this may result
in the compilation commands

     gcc -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -DMAJOR_VERSION=1 -DMINOR_VERSION=0 -I/usr/local/include -I/usr/local/include/python2.2 -c demo.c -o build/temp.linux-i686-2.2/demo.o

     gcc -shared build/temp.linux-i686-2.2/demo.o -L/usr/local/lib -ltcl83 -o build/lib.linux-i686-2.2/demo.so

These lines are for demonstration purposes only; distutils users should
trust that distutils gets the invocations right.


File: python.info,  Node: Distributing your extension modules,  Prev: Building C and C++ Extensions with distutils,  Up: Building C and C++ Extensions

6.2.4.2 Distributing your extension modules
...........................................

When an extension has been successfully built, there are three ways to
use it.

End-users will typically want to install the module, they do so by
running

     python setup.py install

Module maintainers should produce source packages; to do so, they run

     python setup.py sdist

In some cases, additional files need to be included in a source
distribution; this is done through a ‘MANIFEST.in’ file; see *note
Specifying the files to distribute: 3b74. for details.

If the source distribution has been built successfully, maintainers can
also create binary distributions.  Depending on the platform, one of the
following commands can be used to do so.

     python setup.py bdist_wininst
     python setup.py bdist_rpm
     python setup.py bdist_dumb


File: python.info,  Node: Building C and C++ Extensions on Windows,  Prev: Building C and C++ Extensions,  Up: Creating extensions without third party tools

6.2.5 Building C and C++ Extensions on Windows
----------------------------------------------

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: Building C and C++ Extensions on Windows

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 *note distutils: 39. package to control
the build process, or do things manually.  The distutils approach works
well for most extensions; documentation on using *note distutils: 39. to
build and package extension modules is available in *note 發布 Python
模組（舊版）: 7fd.  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.8/PCbuild/winsound.vcxproj


File: python.info,  Node: Differences Between Unix and Windows,  Next: Using DLLs in Practice,  Prev: A Cookbook Approach,  Up: Building C and C++ Extensions on Windows

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: Building C and C++ Extensions on Windows

6.2.5.3 Using DLLs in Practice
..............................

Windows Python is built in Microsoft Visual C++; using other compilers
may or may not work (though Borland seems to).  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(): 26b.), 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 ‘msvcrtxx.lib’ to the list of libraries.


File: python.info,  Node: Embedding the CPython runtime in a larger application,  Prev: Creating extensions without third party tools,  Up: Extending and Embedding the Python Interpreter

6.3 Embedding the CPython runtime in a larger application
=========================================================

Sometimes, rather than creating an extension that runs inside the Python
interpreter as the main application, it is desirable to instead embed
the CPython runtime inside a larger application.  This section covers
some of the details involved in doing that successfully.

* Menu:

* 在其它 App 內嵌入 Python::


File: python.info,  Node: 在其它 App 內嵌入 Python,  Up: Embedding the CPython runtime in a larger application

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(): 43e.  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(): 3b81,
or you can pass a stdio file pointer and a file name (for identification
in error messages only) to *note PyRun_SimpleFile(): 3b82.  You can also
call the lower-level operations described in the previous chapters to
construct and use Python objects.

也參考
......

*note Python / C API 參考手冊: 1203.

     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[])
     {
         wchar_t *program = Py_DecodeLocale(argv[0], NULL);
         if (program == NULL) {
             fprintf(stderr, "Fatal error: cannot decode argv[0]\n");
             exit(1);
         }
         Py_SetProgramName(program);  /* optional but recommended */
         Py_Initialize();
         PyRun_SimpleString("from time import time,ctime\n"
                            "print('Today is', ctime(time()))\n");
         if (Py_FinalizeEx() < 0) {
             exit(120);
         }
         PyMem_RawFree(program);
         return 0;
     }

The *note Py_SetProgramName(): f8e. function should be called before
*note Py_Initialize(): 43e. to inform the interpreter about paths to
Python run-time libraries.  Next, the Python interpreter is initialized
with *note Py_Initialize(): 43e, followed by the execution of a
hard-coded Python script that prints the date and time.  Afterwards, the
*note Py_FinalizeEx(): 5ce. 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(): 3b82. 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: 3b89. 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(): d64.  This routine needs a Python string as its
argument, which is constructed using the *note PyUnicode_FromString():
3b8a. 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(): 3b15.  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():
43e.:

     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.4-config --cflags
          -I/opt/include/python3.4m -I/opt/include/python3.4m -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes

   * ‘pythonX.Y-config --ldflags’ will give you the recommended flags
     when linking:

          $ /opt/bin/python3.4-config --ldflags
          -L/opt/lib/python3.4/config-3.4m -lpthread -ldl -lutil -lm -lpython3.4m -Xlinker -export-dynamic

     備註: 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: 3b90.)
you will have to read your system’s documentation about dynamic linking
and/or examine Python’s ‘Makefile’ (use *note
sysconfig.get_makefile_filename(): 3647. to find its location) and
compilation options.  In this case, the *note sysconfig: ff. 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: Extending and Embedding the Python Interpreter,  Up: Top

7 Python / C API 參考手冊
*************************

This manual documents the API used by C and C++ programmers who want to
write extension modules or embed Python.  It is a companion to *note
Extending and Embedding the Python Interpreter: 1202, which describes
the general principles of extension writing but does not document the
API functions in detail.

* Menu:

* 簡介: 簡介<12>.
* Stable Application Binary Interface::
* The Very High Level Layer::
* 參照計數::
* 例外處理::
* 工具::
* 抽象物件層::
* Concrete Objects Layer::
* Initialization, Finalization, and Threads: Initialization Finalization and Threads.
* Python Initialization Configuration::
* 記憶體管理::
* Object Implementation Support::
* API and ABI Versioning::


File: python.info,  Node: 簡介<12>,  Next: Stable Application Binary Interface,  Up: Python / C API 參考手冊

7.1 簡介
========

The Application Programmer’s Interface to Python gives C and C++
programmers access to the Python interpreter at a variety of levels.
The API is equally usable from C++, but for brevity it is generally
referred to as the Python/C API. There are two fundamentally different
reasons for using the Python/C API. The first reason is to write
`extension modules' for specific purposes; these are C modules that
extend the Python interpreter.  This is probably the most common use.
The second reason is to use Python as a component in a larger
application; this technique is generally referred to as `embedding'
Python in an application.

Writing an extension module is a relatively well-understood process,
where a "cookbook" approach works well.  There are several tools that
automate the process to some extent.  While people have embedded Python
in other applications since its early existence, the process of
embedding Python is less straightforward than writing an extension.

Many API functions are useful independent of whether you’re embedding or
extending Python; moreover, most applications that embed Python will
need to provide a custom extension as well, so it’s probably a good idea
to become familiar with writing an extension before attempting to embed
Python in a real application.

* Menu:

* Coding standards::
* Include Files::
* Useful macros::
* Objects, Types and Reference Counts: Objects Types and Reference Counts.
* Exceptions: Exceptions<16>.
* 嵌入式Python::
* Debugging Builds::


File: python.info,  Node: Coding standards,  Next: Include Files,  Up: 簡介<12>

7.1.1 Coding standards
----------------------

If you’re writing C code for inclusion in CPython, you `must' follow the
guidelines and standards defined in PEP 7(1).  These guidelines apply
regardless of the version of Python you are contributing to.  Following
these conventions is not necessary for your own third party extension
modules, unless you eventually expect to contribute them to Python.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0007


File: python.info,  Node: Include Files,  Next: Useful macros,  Prev: Coding standards,  Up: 簡介<12>

7.1.2 Include Files
-------------------

All function, type and macro definitions needed to use the Python/C API
are included in your code by the following line:

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>

This implies inclusion of the following standard headers: ‘<stdio.h>’,
‘<string.h>’, ‘<errno.h>’, ‘<limits.h>’, ‘<assert.h>’ and ‘<stdlib.h>’
(if available).

     備註: 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.

     It is recommended to always define ‘PY_SSIZE_T_CLEAN’ before
     including ‘Python.h’.  See *note Parsing arguments and building
     values: 2d1. for a description of this macro.

All user visible names defined by Python.h (except those defined by the
included standard headers) have one of the prefixes ‘Py’ or ‘_Py’.
Names beginning with ‘_Py’ are for internal use by the Python
implementation and should not be used by extension writers.  Structure
member names do not have a reserved prefix.

     備註: User code should never define names that begin with ‘Py’ or
     ‘_Py’.  This confuses the reader, and jeopardizes the portability
     of the user code to future Python versions, which may define
     additional names beginning with one of these prefixes.

The header files are typically installed with Python.  On Unix, these
are located in the directories ‘`prefix'/include/pythonversion/’ and
‘`exec_prefix'/include/pythonversion/’, where ‘prefix’ and ‘exec_prefix’
are defined by the corresponding parameters to Python’s ‘configure’
script and `version' is ‘'%d.%d' % sys.version_info[:2]’.  On Windows,
the headers are installed in ‘`prefix'/include’, where ‘prefix’ is the
installation directory specified to the installer.

To include the headers, place both directories (if different) on your
compiler’s search path for includes.  Do `not' place the parent
directories on the search path and then use ‘#include
<pythonX.Y/Python.h>’; this will break on multi-platform builds since
the platform independent headers under ‘prefix’ include the platform
specific headers from ‘exec_prefix’.

C++ users should note that although the API is defined entirely using C,
the header files properly declare the entry points to be ‘extern "C"’.
As a result, there is no need to do anything special to use the API from
C++.


File: python.info,  Node: Useful macros,  Next: Objects Types and Reference Counts,  Prev: Include Files,  Up: 簡介<12>

7.1.3 Useful macros
-------------------

Several useful macros are defined in the Python header files.  Many are
defined closer to where they are useful (e.g.  *note Py_RETURN_NONE:
ddb.).  Others of a more general utility are defined here.  This is not
necessarily a complete listing.

 -- C 巨集: Py_UNREACHABLE ()

     Use this when you have a code path that you do not expect to be
     reached.  For example, in the ‘default:’ clause in a ‘switch’
     statement for which all possible values are covered in ‘case’
     statements.  Use this in places where you might be tempted to put
     an ‘assert(0)’ or ‘abort()’ call.

     3.7 版新加入.

 -- C 巨集: Py_ABS (x)

     Return the absolute value of ‘x’.

     3.3 版新加入.

 -- C 巨集: Py_MIN (x, y)

     Return the minimum value between ‘x’ and ‘y’.

     3.3 版新加入.

 -- C 巨集: Py_MAX (x, y)

     Return the maximum value between ‘x’ and ‘y’.

     3.3 版新加入.

 -- C 巨集: Py_STRINGIFY (x)

     Convert ‘x’ to a C string.  E.g.  ‘Py_STRINGIFY(123)’ returns
     ‘"123"’.

     3.4 版新加入.

 -- C 巨集: Py_MEMBER_SIZE (type, member)

     Return the size of a structure (‘type’) ‘member’ in bytes.

     3.6 版新加入.

 -- C 巨集: Py_CHARMASK (c)

     Argument must be a character or an integer in the range [-128, 127]
     or [0, 255].  This macro returns ‘c’ cast to an ‘unsigned char’.

 -- C 巨集: Py_GETENV (s)

     Like ‘getenv(s)’, but returns ‘NULL’ if *note -E: 100e. was passed
     on the command line (i.e.  if ‘Py_IgnoreEnvironmentFlag’ is set).

 -- C 巨集: Py_UNUSED (arg)

     Use this for unused arguments in a function definition to silence
     compiler warnings.  Example: ‘int func(int a, int Py_UNUSED(b)) {
     return a; }’.

     3.4 版新加入.

 -- C 巨集: Py_DEPRECATED (version)

     Use this for deprecated declarations.  The macro must be placed
     before the symbol name.

     Example:

          Py_DEPRECATED(3.8) PyAPI_FUNC(int) Py_OldFunction(void);

     3.8 版更變: MSVC support was added.

 -- C 巨集: PyDoc_STRVAR (name, str)

     Creates a variable with name ‘name’ that can be used in docstrings.
     If Python is built without docstrings, the value will be empty.

     Use *note PyDoc_STRVAR: f31. for docstrings to support building
     Python without docstrings, as specified in PEP 7(1).

     Example:

          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)

     Creates a docstring for the given input string or an empty string
     if docstrings are disabled.

     Use *note PyDoc_STR: 3ba3. in specifying docstrings to support
     building Python without docstrings, as specified in PEP 7(2).

     Example:

          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://www.python.org/dev/peps/pep-0007

   (2) https://www.python.org/dev/peps/pep-0007


File: python.info,  Node: Objects Types and Reference Counts,  Next: Exceptions<16>,  Prev: Useful macros,  Up: 簡介<12>

7.1.4 Objects, Types and Reference Counts
-----------------------------------------

Most Python/C API functions have one or more arguments as well as a
return value of type *note PyObject*: 4bf.  This type is a pointer to an
opaque data type representing an arbitrary Python object.  Since all
Python object types are treated the same way by the Python language in
most situations (e.g., assignments, scope rules, and argument passing),
it is only fitting that they should be represented by a single C type.
Almost all Python objects live on the heap: you never declare an
automatic or static variable of type *note PyObject: 4bf, only pointer
variables of type *note PyObject*: 4bf. can be declared.  The sole
exception are the type objects; since these must never be deallocated,
they are typically static *note PyTypeObject: 2d7. objects.

All Python objects (even Python integers) have a `type' and a `reference
count'.  An object’s type determines what kind of object it is (e.g., an
integer, a list, or a user-defined function; there are many more as
explained in *note The standard type hierarchy: 1426.).  For each of the
well-known types there is a macro to check whether an object is of that
type; for instance, ‘PyList_Check(a)’ is true if (and only if) the
object pointed to by `a' is a Python list.

* Menu:

* Reference Counts: Reference Counts<2>.
* Types::


File: python.info,  Node: Reference Counts<2>,  Next: Types,  Up: Objects Types and Reference Counts

7.1.4.1 Reference Counts
........................

The reference count is important because today’s computers have a finite
(and often severely limited) memory size; it counts how many different
places there are that have a reference to an object.  Such a place could
be another object, or a global (or static) C variable, or a local
variable in some C function.  When an object’s reference count becomes
zero, the object is deallocated.  If it contains references to other
objects, their reference count is decremented.  Those other objects may
be deallocated in turn, if this decrement makes their reference count
become zero, and so on.  (There’s an obvious problem with objects that
reference each other here; for now, the solution is "don’t do that.")

Reference counts are always manipulated explicitly.  The normal way is
to use the macro *note Py_INCREF(): 266. to increment an object’s
reference count by one, and *note Py_DECREF(): 267. to decrement it by
one.  The *note Py_DECREF(): 267. macro is considerably more complex
than the incref one, since it must check whether the reference count
becomes zero and then cause the object’s deallocator to be called.  The
deallocator is a function pointer contained in the object’s type
structure.  The type-specific deallocator takes care of decrementing the
reference counts for other objects contained in the object if this is a
compound object type, such as a list, as well as performing any
additional finalization that’s needed.  There’s no chance that the
reference count can overflow; at least as many bits are used to hold the
reference count as there are distinct memory locations in virtual memory
(assuming ‘sizeof(Py_ssize_t) >= sizeof(void*)’).  Thus, the reference
count increment is a simple operation.

It is not necessary to increment an object’s reference count for every
local variable that contains a pointer to an object.  In theory, the
object’s reference count goes up by one when the variable is made to
point to it and it goes down by one when the variable goes out of scope.
However, these two cancel each other out, so at the end the reference
count hasn’t changed.  The only real reason to use the reference count
is to prevent the object from being deallocated as long as our variable
is pointing to it.  If we know that there is at least one other
reference to the object that lives at least as long as our variable,
there is no need to increment the reference count temporarily.  An
important situation where this arises is in objects that are passed as
arguments to C functions in an extension module that are called from
Python; the call mechanism guarantees to hold a reference to every
argument for the duration of the call.

However, a common pitfall is to extract an object from a list and hold
on to it for a while without incrementing its reference count.  Some
other operation might conceivably remove the object from the list,
decrementing its reference count and possibly deallocating it.  The real
danger is that innocent-looking operations may invoke arbitrary Python
code which could do this; there is a code path which allows control to
flow back to the user from a *note Py_DECREF(): 267, so almost any
operation is potentially dangerous.

A safe approach is to always use the generic operations (functions whose
name begins with ‘PyObject_’, ‘PyNumber_’, ‘PySequence_’ or
‘PyMapping_’).  These operations always increment the reference count of
the object they return.  This leaves the caller with the responsibility
to call *note Py_DECREF(): 267. when they are done with the result; this
soon becomes second nature.

* Menu:

* Reference Count Details::


File: python.info,  Node: Reference Count Details,  Up: Reference Counts<2>

7.1.4.2 Reference Count Details
...............................

The reference count behavior of functions in the Python/C API is best
explained in terms of `ownership of references'.  Ownership pertains to
references, never to objects (objects are not owned: they are always
shared).  "Owning a reference" means being responsible for calling
Py_DECREF on it when the reference is no longer needed.  Ownership can
also be transferred, meaning that the code that receives ownership of
the reference then becomes responsible for eventually decref’ing it by
calling *note Py_DECREF(): 267. or *note Py_XDECREF(): 269. when it’s no
longer needed—or passing on this responsibility (usually to its caller).
When a function passes ownership of a reference on to its caller, the
caller is said to receive a `new' reference.  When no ownership is
transferred, the caller is said to `borrow' the reference.  Nothing
needs to be done for a borrowed reference.

Conversely, when a calling function passes in a reference to an object,
there are two possibilities: the function `steals' a reference to the
object, or it does not.  `Stealing a reference' means that when you pass
a reference to a function, that function assumes that it now owns that
reference, and you are not responsible for it any longer.

Few functions steal references; the two notable exceptions are *note
PyList_SetItem(): 3b1c. and *note PyTuple_SetItem(): 3b1b, which steal a
reference to the item (but not to the tuple or list into which the item
is put!).  These functions were designed to steal a reference because of
a common idiom for populating a tuple or list with newly created
objects; for example, the code to create the tuple ‘(1, 2, "three")’
could look like this (forgetting about error handling for the moment; a
better way to code this is shown below):

     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"));

Here, *note PyLong_FromLong(): 3afb. returns a new reference which is
immediately stolen by *note PyTuple_SetItem(): 3b1b.  When you want to
keep using an object although the reference to it will be stolen, use
*note Py_INCREF(): 266. to grab another reference before calling the
reference-stealing function.

Incidentally, *note PyTuple_SetItem(): 3b1b. is the `only' way to set
tuple items; *note PySequence_SetItem(): 1054. and *note
PyObject_SetItem(): 3baa. refuse to do this since tuples are an
immutable data type.  You should only use *note PyTuple_SetItem(): 3b1b.
for tuples that you are creating yourself.

Equivalent code for populating a list can be written using *note
PyList_New(): 3bab. and *note PyList_SetItem(): 3b1c.

However, in practice, you will rarely use these ways of creating and
populating a tuple or list.  There’s a generic function, *note
Py_BuildValue(): 2cf, that can create most common objects from C values,
directed by a `format string'.  For example, the above two blocks of
code could be replaced by the following (which also takes care of the
error checking):

     PyObject *tuple, *list;

     tuple = Py_BuildValue("(iis)", 1, 2, "three");
     list = Py_BuildValue("[iis]", 1, 2, "three");

It is much more common to use *note PyObject_SetItem(): 3baa. and
friends with items whose references you are only borrowing, like
arguments that were passed in to the function you are writing.  In that
case, their behaviour regarding reference counts is much saner, since
you don’t have to increment a reference count so you can give a
reference away ("have it be stolen").  For example, this function sets
all items of a list (actually, any mutable sequence) to a given item:

     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;
     }

The situation is slightly different for function return values.  While
passing a reference to most functions does not change your ownership
responsibilities for that reference, many functions that return a
reference to an object give you ownership of the reference.  The reason
is simple: in many cases, the returned object is created on the fly, and
the reference you get is the only reference to the object.  Therefore,
the generic functions that return object references, like *note
PyObject_GetItem(): 3bac. and *note PySequence_GetItem(): 1053, always
return a new reference (the caller becomes the owner of the reference).

It is important to realize that whether you own a reference returned by
a function depends on which function you call only — `the plumage' (the
type of the object passed as an argument to the function) `doesn’t enter
into it!'  Thus, if you extract an item from a list using *note
PyList_GetItem(): 3b17, you don’t own the reference — but if you obtain
the same item from the same list using *note PySequence_GetItem(): 1053.
(which happens to take exactly the same arguments), you do own a
reference to the returned object.

Here is an example of how you could write a function that computes the
sum of the items in a list of integers; once using *note
PyList_GetItem(): 3b17, and once using *note PySequence_GetItem(): 1053.

     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: Types,  Prev: Reference Counts<2>,  Up: Objects Types and Reference Counts

7.1.4.3 Types
.............

There are few other data types that play a significant role in the
Python/C API; most are simple C types such as ‘int’, ‘long’, ‘double’
and ‘char*’.  A few structure types are used to describe static tables
used to list the functions exported by a module or the data attributes
of a new object type, and another is used to describe the value of a
complex number.  These will be discussed together with the functions
that use them.


File: python.info,  Node: Exceptions<16>,  Next: 嵌入式Python,  Prev: Objects Types and Reference Counts,  Up: 簡介<12>

7.1.5 Exceptions
----------------

The Python programmer only needs to deal with exceptions if specific
error handling is required; unhandled exceptions are automatically
propagated to the caller, then to the caller’s caller, and so on, until
they reach the top-level interpreter, where they are reported to the
user accompanied by a stack traceback.

For C programmers, however, error checking always has to be explicit.
All functions in the Python/C API can raise exceptions, unless an
explicit claim is made otherwise in a function’s documentation.  In
general, when a function encounters an error, it sets an exception,
discards any object references that it owns, and returns an error
indicator.  If not documented otherwise, this indicator is either ‘NULL’
or ‘-1’, depending on the function’s return type.  A few functions
return a Boolean true/false result, with false indicating an error.
Very few functions return no explicit error indicator or have an
ambiguous return value, and require explicit testing for errors with
*note PyErr_Occurred(): 3af9.  These exceptions are always explicitly
documented.

Exception state is maintained in per-thread storage (this is equivalent
to using global storage in an unthreaded application).  A thread can be
in one of two states: an exception has occurred, or not.  The function
*note PyErr_Occurred(): 3af9. can be used to check for this: it returns
a borrowed reference to the exception type object when an exception has
occurred, and ‘NULL’ otherwise.  There are a number of functions to set
the exception state: *note PyErr_SetString(): 3af6. is the most common
(though not the most general) function to set the exception state, and
*note PyErr_Clear(): 970. clears the exception state.

The full exception state consists of three objects (all of which can be
‘NULL’): the exception type, the corresponding exception value, and the
traceback.  These have the same meanings as the Python result of
‘sys.exc_info()’; however, they are not the same: the Python objects
represent the last exception being handled by a Python *note try: d77.
...  *note except: b43. statement, while the C level exception state
only exists while an exception is being passed on between C functions
until it reaches the Python bytecode interpreter’s main loop, which
takes care of transferring it to ‘sys.exc_info()’ and friends.

Note that starting with Python 1.5, the preferred, thread-safe way to
access the exception state from Python code is to call the function
*note sys.exc_info(): c64, which returns the per-thread exception state
for Python code.  Also, the semantics of both ways to access the
exception state have changed so that a function which catches an
exception will save and restore its thread’s exception state so as to
preserve the exception state of its caller.  This prevents common bugs
in exception handling code caused by an innocent-looking function
overwriting the exception being handled; it also reduces the often
unwanted lifetime extension for objects that are referenced by the stack
frames in the traceback.

As a general principle, a function that calls another function to
perform some task should check whether the called function raised an
exception, and if so, pass the exception state on to its caller.  It
should discard any object references that it owns, and return an error
indicator, but it should `not' set another exception — that would
overwrite the exception that was just raised, and lose important
information about the exact cause of the error.

A simple example of detecting exceptions and passing them on is shown in
the ‘sum_sequence()’ example above.  It so happens that this example
doesn’t need to clean up any owned references when it detects an error.
The following example function shows some error cleanup.  First, to
remind you why you like Python, we show the equivalent Python code:

     def incr_item(dict, key):
         try:
             item = dict[key]
         except KeyError:
             item = 0
         dict[key] = item + 1

Here is the corresponding C code, in all its glory:

     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 */
     }

This example represents an endorsed use of the ‘goto’ statement in C! It
illustrates the use of *note PyErr_ExceptionMatches(): 3bb1. and *note
PyErr_Clear(): 970. to handle specific exceptions, and the use of *note
Py_XDECREF(): 269. to dispose of owned references that may be ‘NULL’
(note the ‘'X'’ in the name; *note Py_DECREF(): 267. would crash when
confronted with a ‘NULL’ reference).  It is important that the variables
used to hold owned references are initialized to ‘NULL’ for this to
work; likewise, the proposed return value is initialized to ‘-1’
(failure) and only set to success after the final call made is
successful.


File: python.info,  Node: 嵌入式Python,  Next: Debugging Builds,  Prev: Exceptions<16>,  Up: 簡介<12>

7.1.6 嵌入式Python
------------------

The one important task that only embedders (as opposed to extension
writers) of the Python interpreter have to worry about is the
initialization, and possibly the finalization, of the Python
interpreter.  Most functionality of the interpreter can only be used
after the interpreter has been initialized.

The basic initialization function is *note Py_Initialize(): 43e.  This
initializes the table of loaded modules, and creates the fundamental
modules *note builtins: 13, *note __main__: 1, and *note sys: fe.  It
also initializes the module search path (‘sys.path’).

*note Py_Initialize(): 43e. does not set the "script argument list"
(‘sys.argv’).  If this variable is needed by Python code that will be
executed later, it must be set explicitly with a call to
‘PySys_SetArgvEx(argc, argv, updatepath)’ after the call to *note
Py_Initialize(): 43e.

On most systems (in particular, on Unix and Windows, although the
details are slightly different), *note Py_Initialize(): 43e. calculates
the module search path based upon its best guess for the location of the
standard Python interpreter executable, assuming that the Python library
is found in a fixed location relative to the Python interpreter
executable.  In particular, it looks for a directory named
‘lib/python`X.Y'’ relative to the parent directory where the executable
named ‘python’ is found on the shell command search path (the
environment variable ‘PATH’).

For instance, if the Python executable is found in
‘/usr/local/bin/python’, it will assume that the libraries are in
‘/usr/local/lib/python`X.Y'’.  (In fact, this particular path is also
the "fallback" location, used when no executable file named ‘python’ is
found along ‘PATH’.)  The user can override this behavior by setting the
environment variable *note PYTHONHOME: 4db, or insert additional
directories in front of the standard path by setting *note PYTHONPATH:
958.

The embedding application can steer the search by calling
‘Py_SetProgramName(file)’ `before' calling *note Py_Initialize(): 43e.
Note that *note PYTHONHOME: 4db. still overrides this and *note
PYTHONPATH: 958. 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(): 3bb4, *note Py_GetPrefix(): 3bb5,
*note Py_GetExecPrefix(): 3bb6, and *note Py_GetProgramFullPath(): 276.
(all defined in ‘Modules/getpath.c’).

Sometimes, it is desirable to "uninitialize" Python.  For instance, the
application may want to start over (make another call to *note
Py_Initialize(): 43e.) or the application is simply done with its use of
Python and wants to free memory allocated by Python.  This can be
accomplished by calling *note Py_FinalizeEx(): 5ce.  The function *note
Py_IsInitialized(): 3bb7. returns true if Python is currently in the
initialized state.  More information about these functions is given in a
later chapter.  Notice that *note Py_FinalizeEx(): 5ce. does `not' free
all memory allocated by the Python interpreter, e.g.  memory allocated
by extension modules currently cannot be released.


File: python.info,  Node: Debugging Builds,  Prev: 嵌入式Python,  Up: 簡介<12>

7.1.7 Debugging Builds
----------------------

Python can be built with several macros to enable extra checks of the
interpreter and extension modules.  These checks tend to add a large
amount of overhead to the runtime so they are not enabled by default.

A full list of the various types of debugging builds is in the file
‘Misc/SpecialBuilds.txt’ in the Python source distribution.  Builds are
available that support tracing of reference counts, debugging the memory
allocator, or low-level profiling of the main interpreter loop.  Only
the most frequently-used builds will be described in the remainder of
this section.

Compiling the interpreter with the ‘Py_DEBUG’ macro defined produces
what is generally meant by "a debug build" of Python.  ‘Py_DEBUG’ is
enabled in the Unix build by adding ‘--with-pydebug’ to the
‘./configure’ command.  It is also implied by the presence of the
not-Python-specific ‘_DEBUG’ macro.  When ‘Py_DEBUG’ is enabled in the
Unix build, compiler optimization is disabled.

In addition to the reference count debugging described below, the
following extra checks are performed:

   * Extra checks are added to the object allocator.

   * Extra checks are added to the parser and compiler.

   * Downcasts from wide types to narrow types are checked for loss of
     information.

   * A number of assertions are added to the dictionary and set
     implementations.  In addition, the set object acquires a
     ‘test_c_api()’ method.

   * Sanity checks of the input arguments are added to frame creation.

   * The storage for ints is initialized with a known invalid pattern to
     catch reference to uninitialized digits.

   * Low-level tracing and extra exception checking are added to the
     runtime virtual machine.

   * Extra checks are added to the memory arena implementation.

   * Extra debugging is added to the thread module.

There may be additional checks not mentioned here.

Defining ‘Py_TRACE_REFS’ enables reference tracing.  When defined, a
circular doubly linked list of active objects is maintained by adding
two extra fields to every *note PyObject: 4bf.  Total allocations are
tracked as well.  Upon exit, all existing references are printed.  (In
interactive mode this happens after every statement run by the
interpreter.)  Implied by ‘Py_DEBUG’.

Please refer to ‘Misc/SpecialBuilds.txt’ in the Python source
distribution for more detailed information.


File: python.info,  Node: Stable Application Binary Interface,  Next: The Very High Level Layer,  Prev: 簡介<12>,  Up: Python / C API 參考手冊

7.2 Stable Application Binary Interface
=======================================

Traditionally, the C API of Python will change with every release.  Most
changes will be source-compatible, typically by only adding API, rather
than changing existing API or removing API (although some interfaces do
get removed after being deprecated first).

Unfortunately, the API compatibility does not extend to binary
compatibility (the ABI). The reason is primarily the evolution of struct
definitions, where addition of a new field, or changing the type of a
field, might not break the API, but can break the ABI. As a consequence,
extension modules need to be recompiled for every Python release
(although an exception is possible on Unix when none of the affected
interfaces are used).  In addition, on Windows, extension modules link
with a specific pythonXY.dll and need to be recompiled to link with a
newer one.

Since Python 3.2, a subset of the API has been declared to guarantee a
stable ABI. Extension modules wishing to use this API (called "limited
API") need to define ‘Py_LIMITED_API’.  A number of interpreter details
then become hidden from the extension module; in return, a module is
built that works on any 3.x version (x>=2) without recompilation.

In some cases, the stable ABI needs to be extended with new functions.
Extension modules wishing to use these new APIs need to set
‘Py_LIMITED_API’ to the ‘PY_VERSION_HEX’ value (see *note API and ABI
Versioning: 3636.) of the minimum Python version they want to support
(e.g.  ‘0x03030000’ for Python 3.3).  Such modules will work on all
subsequent Python releases, but fail to load (because of missing
symbols) on the older releases.

As of Python 3.2, the set of functions available to the limited API is
documented in PEP 384(1).  In the C API documentation, API elements that
are not part of the limited API are marked as "Not part of the limited
API."

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0384


File: python.info,  Node: The Very High Level Layer,  Next: 參照計數,  Prev: Stable Application Binary Interface,  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 ‘Py_eval_input’,
‘Py_file_input’, and ‘Py_single_input’.  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)

     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: 601. is
     raised, this function will not return ‘1’, but exit the process, as
     long as ‘Py_InspectFlag’ is not set.

 -- C 函式: int Py_BytesMain (int argc, char **argv)

     Similar to *note Py_Main(): 4bc. 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():
     3bc1. 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():
     3bc1. 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():
     3bc1. 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(): 3bc4, otherwise return the
     result of *note PyRun_SimpleFile(): 3b82.  `filename' is decoded
     from the filesystem encoding (*note sys.getfilesystemencoding():
     4fb.).  If `filename' is ‘NULL’, this function uses ‘"???"’ as the
     filename.

 -- C 函式: int PyRun_SimpleString (const char *command)

     This is a simplified interface to *note PyRun_SimpleStringFlags():
     3bc5. below, leaving the *note PyCompilerFlags: 2cd.* 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: 601. is
     raised, this function will not return ‘-1’, but exit the process,
     as long as ‘Py_InspectFlag’ is not set.

 -- C 函式: int PyRun_SimpleFile (FILE *fp, const char *filename)

     This is a simplified interface to *note PyRun_SimpleFileExFlags():
     ecc. 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():
     ecc. below, leaving `flags' set to ‘NULL’.

 -- C 函式: int PyRun_SimpleFileExFlags (FILE *fp, const char *filename,
          int closeit, PyCompilerFlags *flags)

     Similar to *note PyRun_SimpleStringFlags(): 3bc5, 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
     filesystem encoding (*note sys.getfilesystemencoding(): 4fb.).  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(): 3bc8. 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 filesystem encoding (*note
     sys.getfilesystemencoding(): 4fb.).

     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(): 3bc9. 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
     filesystem encoding (*note sys.getfilesystemencoding(): 4fb.).
     Returns ‘0’ at EOF or a negative number upon failure.

 -- C 變數: int (*PyOS_InputHook) (void)

     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.

 -- 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: df. module sets this hook
     to provide line-editing and tab-completion features.

     The result must be a string allocated by *note PyMem_RawMalloc():
     972. or *note PyMem_RawRealloc(): 973, or ‘NULL’ if an error
     occurred.

     3.4 版更變: The result must be allocated by *note
     PyMem_RawMalloc(): 972. or *note PyMem_RawRealloc(): 973, instead
     of being allocated by *note PyMem_Malloc(): 50a. or *note
     PyMem_Realloc(): 974.

 -- C 函式: struct _node* PyParser_SimpleParseString (const char *str,
          int start)

     This is a simplified interface to *note
     PyParser_SimpleParseStringFlagsFilename(): 3bcc. below, leaving
     `filename' set to ‘NULL’ and `flags' set to ‘0’.

 -- C 函式: struct _node* PyParser_SimpleParseStringFlags (const
          char *str, int start, int flags)

     This is a simplified interface to *note
     PyParser_SimpleParseStringFlagsFilename(): 3bcc. below, leaving
     `filename' set to ‘NULL’.

 -- C 函式: struct _node* PyParser_SimpleParseStringFlagsFilename (const
          char *str, const char *filename, int start, int flags)

     Parse Python source code from `str' using the start token `start'
     according to the `flags' argument.  The result can be used to
     create a code object which can be evaluated efficiently.  This is
     useful if a code fragment must be evaluated many times.  `filename'
     is decoded from the filesystem encoding (*note
     sys.getfilesystemencoding(): 4fb.).

 -- C 函式: struct _node* PyParser_SimpleParseFile (FILE *fp, const
          char *filename, int start)

     This is a simplified interface to *note
     PyParser_SimpleParseFileFlags(): 3bcf. below, leaving `flags' set
     to ‘0’.

 -- C 函式: struct _node* PyParser_SimpleParseFileFlags (FILE *fp, const
          char *filename, int start, int flags)

     Similar to *note PyParser_SimpleParseStringFlagsFilename(): 3bcc,
     but the Python source code is read from `fp' instead of an
     in-memory string.

 -- C 函式: PyObject* PyRun_String (const char *str, int start,
          PyObject *globals, PyObject *locals)
     `Return value: New reference.'  This is a simplified interface to
     *note PyRun_StringFlags(): 3bd0. below, leaving `flags' set to
     ‘NULL’.

 -- C 函式: PyObject* PyRun_StringFlags (const char *str, int start,
          PyObject *globals, PyObject *locals, PyCompilerFlags *flags)
     `Return value: New reference.'  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 函式: PyObject* PyRun_File (FILE *fp, const char *filename,
          int start, PyObject *globals, PyObject *locals)
     `Return value: New reference.'  This is a simplified interface to
     *note PyRun_FileExFlags(): 3bd2. below, leaving `closeit' set to
     ‘0’ and `flags' set to ‘NULL’.

 -- C 函式: PyObject* PyRun_FileEx (FILE *fp, const char *filename,
          int start, PyObject *globals, PyObject *locals, int closeit)
     `Return value: New reference.'  This is a simplified interface to
     *note PyRun_FileExFlags(): 3bd2. below, leaving `flags' set to
     ‘NULL’.

 -- C 函式: PyObject* PyRun_FileFlags (FILE *fp, const char *filename,
          int start, PyObject *globals, PyObject *locals,
          PyCompilerFlags *flags)
     `Return value: New reference.'  This is a simplified interface to
     *note PyRun_FileExFlags(): 3bd2. below, leaving `closeit' set to
     ‘0’.

 -- C 函式: PyObject* PyRun_FileExFlags (FILE *fp, const char *filename,
          int start, PyObject *globals, PyObject *locals, int closeit,
          PyCompilerFlags *flags)
     `Return value: New reference.'  Similar to *note
     PyRun_StringFlags(): 3bd0, 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 filesystem encoding (*note
     sys.getfilesystemencoding(): 4fb.).  If `closeit' is true, the file
     is closed before *note PyRun_FileExFlags(): 3bd2. returns.

 -- C 函式: PyObject* Py_CompileString (const char *str, const
          char *filename, int start)
     `Return value: New reference.'  This is a simplified interface to
     *note Py_CompileStringFlags(): 3bd6. below, leaving `flags' set to
     ‘NULL’.

 -- C 函式: PyObject* Py_CompileStringFlags (const char *str, const
          char *filename, int start, PyCompilerFlags *flags)
     `Return value: New reference.'  This is a simplified interface to
     *note Py_CompileStringExFlags(): 3bd7. below, with `optimize' set
     to ‘-1’.

 -- C 函式: PyObject* Py_CompileStringObject (const char *str,
          PyObject *filename, int start, PyCompilerFlags *flags,
          int optimize)
     `Return value: New reference.'  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 ‘Py_eval_input’,
     ‘Py_file_input’, or ‘Py_single_input’.  The filename specified by
     `filename' is used to construct the code object and may appear in
     tracebacks or *note SyntaxError: 45d. 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: 690. 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 函式: PyObject* Py_CompileStringExFlags (const char *str, const
          char *filename, int start, PyCompilerFlags *flags,
          int optimize)
     `Return value: New reference.'  Like *note
     Py_CompileStringObject(): 3bd8, but `filename' is a byte string
     decoded from the filesystem encoding (*note os.fsdecode(): 4f3.).

     3.2 版新加入.

 -- C 函式: PyObject* PyEval_EvalCode (PyObject *co, PyObject *globals,
          PyObject *locals)
     `Return value: New reference.'  This is a simplified interface to
     *note PyEval_EvalCodeEx(): 3bda, with just the code object, and
     global and local variables.  The other arguments are set to ‘NULL’.

 -- C 函式: PyObject* 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)
     `Return value: New reference.'  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:
     2ad. arguments and a closure tuple of cells.

 -- C 類型: PyFrameObject

     The C structure of the objects used to describe frame objects.  The
     fields of this type are subject to change at any time.

 -- C 函式: PyObject* PyEval_EvalFrame (PyFrameObject *f)
     `Return value: New reference.'  Evaluate an execution frame.  This
     is a simplified interface to *note PyEval_EvalFrameEx(): 96c, for
     backward compatibility.

 -- C 函式: PyObject* PyEval_EvalFrameEx (PyFrameObject *f,
          int throwflag)
     `Return value: New reference.'  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(): 1496.
     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(): 3bd5.

 -- 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(): 3bd5.  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(): 3bd5.  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’, ‘cf_flags’ 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 `cf_flags'.

     3.8 版更變: Added `cf_feature_version' field.

 -- 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://www.python.org/dev/peps/pep-0238


File: python.info,  Node: 參照計數,  Next: 例外處理,  Prev: The Very High Level Layer,  Up: Python / C API 參考手冊

7.4 參照計數
============

The macros in this section are used for managing reference counts of
Python objects.

 -- C 函式: void Py_INCREF (PyObject *o)

     Increment the reference count for object `o'.  The object must not
     be ‘NULL’; if you aren’t sure that it isn’t ‘NULL’, use *note
     Py_XINCREF(): 268.

 -- C 函式: void Py_XINCREF (PyObject *o)

     Increment the reference count for object `o'.  The object may be
     ‘NULL’, in which case the macro has no effect.

 -- C 函式: void Py_DECREF (PyObject *o)

     Decrement the reference count for object `o'.  The object must not
     be ‘NULL’; if you aren’t sure that it isn’t ‘NULL’, use *note
     Py_XDECREF(): 269.  If the reference count reaches zero, the
     object’s type’s deallocation function (which must not be ‘NULL’) is
     invoked.

          警告: The deallocation function can cause arbitrary Python
          code to be invoked (e.g.  when a class instance with a *note
          __del__(): 924. method is deallocated).  While exceptions in
          such code are not propagated, the executed code has free
          access to all Python global variables.  This means that any
          object that is reachable from a global variable should be in a
          consistent state before *note Py_DECREF(): 267. is invoked.
          For example, code to delete an object from a list should copy
          a reference to the deleted object in a temporary variable,
          update the list data structure, and then call *note
          Py_DECREF(): 267. for the temporary variable.

 -- C 函式: void Py_XDECREF (PyObject *o)

     Decrement the reference count for object `o'.  The object may be
     ‘NULL’, in which case the macro has no effect; otherwise the effect
     is the same as for *note Py_DECREF(): 267, and the same warning
     applies.

 -- C 函式: void Py_CLEAR (PyObject *o)

     Decrement the reference count for object `o'.  The object may be
     ‘NULL’, in which case the macro has no effect; otherwise the effect
     is the same as for *note Py_DECREF(): 267, except that the argument
     is also set to ‘NULL’.  The warning for *note Py_DECREF(): 267.
     does not apply with respect to the object passed because the macro
     carefully uses a temporary variable and sets the argument to ‘NULL’
     before decrementing its reference count.

     It is a good idea to use this macro whenever decrementing the
     reference count of an object that might be traversed during garbage
     collection.

The following functions are for runtime dynamic embedding of Python:
‘Py_IncRef(PyObject *o)’, ‘Py_DecRef(PyObject *o)’.  They are simply
exported function versions of *note Py_XINCREF(): 268. and *note
Py_XDECREF(): 269, respectively.

The following functions or macros are only for use within the
interpreter core: ‘_Py_Dealloc()’, ‘_Py_ForgetReference()’,
‘_Py_NewReference()’, as well as the global variable ‘_Py_RefTotal’.


File: python.info,  Node: 例外處理,  Next: 工具,  Prev: 參照計數,  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(): c64.  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>.
* Exception Classes::
* Exception Objects::
* 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 ()

     Clear the error indicator.  If the error indicator is not set,
     there is no effect.

 -- C 函式: void PyErr_PrintEx (int set_sys_last_vars)

     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 variables *note
     sys.last_type: c5f, *note sys.last_value: 3637. and *note
     sys.last_traceback: 3533. will be set to the type, value and
     traceback of the printed exception, respectively.

 -- C 函式: void PyErr_Print ()

     Alias for ‘PyErr_PrintEx(1)’.

 -- C 函式: void PyErr_WriteUnraisable (PyObject *obj)

     Call *note sys.unraisablehook(): 22e. 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__(): 924. 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.

     An exception must be set when calling this function.


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)

     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
     increment its reference count.  The second argument is an error
     message; it is decoded from ‘'utf-8’’.

 -- C 函式: void PyErr_SetObject (PyObject *type, PyObject *value)

     This function is similar to *note PyErr_SetString(): 3af6. but lets
     you specify an arbitrary Python object for the "value" of the
     exception.

 -- C 函式: PyObject* PyErr_Format (PyObject *exception, const
          char *format, ...)
     `Return value: Always NULL.' 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(): 7d0.  `format' is an ASCII-encoded string.

 -- C 函式: PyObject* PyErr_FormatV (PyObject *exception, const
          char *format, va_list vargs)
     `Return value: Always NULL.' Same as *note PyErr_Format(): 7af, but
     taking a ‘va_list’ argument rather than a variable number of
     arguments.

     3.5 版新加入.

 -- C 函式: void PyErr_SetNone (PyObject *type)

     This is a shorthand for ‘PyErr_SetObject(type, Py_None)’.

 -- C 函式: int PyErr_BadArgument ()

     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 函式: PyObject* PyErr_NoMemory ()
     `Return value: Always NULL.' 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 函式: PyObject* PyErr_SetFromErrno (PyObject *type)
     `Return value: Always NULL.'

     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(): 3bed, 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 函式: PyObject* PyErr_SetFromErrnoWithFilenameObject
          (PyObject *type, PyObject *filenameObject)
     `Return value: Always NULL.' Similar to *note PyErr_SetFromErrno():
     3af7, 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: 1d4. exception, this is
     used to define the ‘filename’ attribute of the exception instance.

 -- C 函式: PyObject* PyErr_SetFromErrnoWithFilenameObjects
          (PyObject *type, PyObject *filenameObject,
          PyObject *filenameObject2)
     `Return value: Always NULL.' Similar to *note
     PyErr_SetFromErrnoWithFilenameObject(): 3bee, but takes a second
     filename object, for raising errors when a function that takes two
     filenames fails.

     3.4 版新加入.

 -- C 函式: PyObject* PyErr_SetFromErrnoWithFilename (PyObject *type,
          const char *filename)
     `Return value: Always NULL.' Similar to *note
     PyErr_SetFromErrnoWithFilenameObject(): 3bee, but the filename is
     given as a C string.  `filename' is decoded from the filesystem
     encoding (*note os.fsdecode(): 4f3.).

 -- C 函式: PyObject* PyErr_SetFromWindowsErr (int ierr)
     `Return value: Always NULL.' This is a convenience function to
     raise *note WindowsError: 999.  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 tuple object whose first
     item is the `ierr' value and whose second item is the corresponding
     error message (gotten from ‘FormatMessage()’), and then calls
     ‘PyErr_SetObject(PyExc_WindowsError, object)’.  This function
     always returns ‘NULL’.

     *note Availability: 1364.: Windows.

 -- C 函式: PyObject* PyErr_SetExcFromWindowsErr (PyObject *type,
          int ierr)
     `Return value: Always NULL.' Similar to *note
     PyErr_SetFromWindowsErr(): 3bf1, with an additional parameter
     specifying the exception type to be raised.

     *note Availability: 1364.: Windows.

 -- C 函式: PyObject* PyErr_SetFromWindowsErrWithFilename (int ierr,
          const char *filename)
     `Return value: Always NULL.' Similar to
     ‘PyErr_SetFromWindowsErrWithFilenameObject()’, but the filename is
     given as a C string.  `filename' is decoded from the filesystem
     encoding (*note os.fsdecode(): 4f3.).

     *note Availability: 1364.: Windows.

 -- C 函式: PyObject* PyErr_SetExcFromWindowsErrWithFilenameObject
          (PyObject *type, int ierr, PyObject *filename)
     `Return value: Always NULL.' Similar to
     ‘PyErr_SetFromWindowsErrWithFilenameObject()’, with an additional
     parameter specifying the exception type to be raised.

     *note Availability: 1364.: Windows.

 -- C 函式: PyObject* PyErr_SetExcFromWindowsErrWithFilenameObjects
          (PyObject *type, int ierr, PyObject *filename,
          PyObject *filename2)
     `Return value: Always NULL.' Similar to *note
     PyErr_SetExcFromWindowsErrWithFilenameObject(): 3bf4, but accepts a
     second filename object.

     *note Availability: 1364.: Windows.

     3.4 版新加入.

 -- C 函式: PyObject* PyErr_SetExcFromWindowsErrWithFilename
          (PyObject *type, int ierr, const char *filename)
     `Return value: Always NULL.' Similar to *note
     PyErr_SetFromWindowsErrWithFilename(): 3bf3, with an additional
     parameter specifying the exception type to be raised.

     *note Availability: 1364.: Windows.

 -- C 函式: PyObject* PyErr_SetImportError (PyObject *msg,
          PyObject *name, PyObject *path)
     `Return value: Always NULL.' This is a convenience function to
     raise *note ImportError: 339.  `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: 339.’s respective ‘name’ and
     ‘path’ attributes.

     3.3 版新加入.

 -- 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: 45d, then it
     sets additional attributes, which make the exception printing
     subsystem think the exception is a *note SyntaxError: 45d.

     3.4 版新加入.

 -- C 函式: void PyErr_SyntaxLocationEx (const char *filename,
          int lineno, int col_offset)

     Like *note PyErr_SyntaxLocationObject(): 3bf7, but `filename' is a
     byte string decoded from the filesystem encoding (*note
     os.fsdecode(): 4f3.).

     3.2 版新加入.

 -- C 函式: void PyErr_SyntaxLocation (const char *filename, int lineno)

     Like *note PyErr_SyntaxLocationEx(): 3bf8, but the col_offset
     parameter is omitted.

 -- C 函式: void PyErr_BadInternalCall ()

     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: 127. 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(): 267. owned references and return an error value).

 -- C 函式: int PyErr_WarnEx (PyObject *category, const char *message,
          Py_ssize_t stack_level)

     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(): db6, 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: 3bfc.

     For information about warning control, see the documentation for
     the *note warnings: 127. module and the *note -W: 41c. option in
     the command line documentation.  There is no C API for warning
     control.

 -- C 函式: PyObject* PyErr_SetImportErrorSubclass (PyObject *exception,
          PyObject *msg, PyObject *name, PyObject *path)
     `Return value: Always NULL.' Much like *note
     PyErr_SetImportError(): 5fd. but this function allows for
     specifying a subclass of *note ImportError: 339. to raise.

     3.6 版新加入.

 -- 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(): 5b5, 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)

     Similar to *note PyErr_WarnExplicitObject(): 3bfd. except that
     `message' and `module' are UTF-8 encoded strings, and `filename' is
     decoded from the filesystem encoding (*note os.fsdecode(): 4f3.).

 -- C 函式: int PyErr_WarnFormat (PyObject *category,
          Py_ssize_t stack_level, const char *format, ...)

     Function similar to *note PyErr_WarnEx(): db6, but use *note
     PyUnicode_FromFormat(): 7d0. 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, ...)

     Function similar to *note PyErr_WarnFormat(): 3bff, but `category'
     is *note ResourceWarning: 4d5. 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 函式: PyObject* PyErr_Occurred ()
     `Return value: Borrowed reference.'  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(): 3b51.).  If not set, return ‘NULL’.  You
     do not own a reference to the return value, so you do not need to
     *note Py_DECREF(): 267. it.

          備註: Do not compare the return value to a specific exception;
          use *note PyErr_ExceptionMatches(): 3bb1. 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)

     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)

     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 函式: void PyErr_Fetch (PyObject **ptype, PyObject **pvalue,
          PyObject **ptraceback)

     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 code that needs
          to catch exceptions or by code that needs to save and restore
          the error indicator temporarily, e.g.:

               {
                  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)

     Set the error indicator from the three objects.  If the error
     indicator is already set, it is cleared first.  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 code that needs
          to save and restore the error indicator temporarily.  Use
          *note PyErr_Fetch(): 96f. to save the current error indicator.

 -- C 函式: void PyErr_NormalizeException (PyObject**exc, PyObject**val,
          PyObject**tb)

     Under certain circumstances, the values returned by *note
     PyErr_Fetch(): 96f. 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
          ‘__traceback__’ 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 函式: void PyErr_GetExcInfo (PyObject **ptype, PyObject **pvalue,
          PyObject **ptraceback)

     Retrieve 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.  Returns new references for the
     three objects, any of which may be ‘NULL’.  Does not modify the
     exception info 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_SetExcInfo(): 3c03. to restore or clear the exception
          state.

     3.3 版新加入.

 -- C 函式: void PyErr_SetExcInfo (PyObject *type, PyObject *value,
          PyObject *traceback)

     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.  For general rules about the three
     arguments, see *note PyErr_Restore(): 3b51.

          備註: 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(): 3c02. to read the exception state.

     3.3 版新加入.


File: python.info,  Node: Signal Handling<2>,  Next: Exception Classes,  Prev: Querying the error indicator,  Up: 例外處理

7.5.5 Signal Handling
---------------------

 -- C 函式: int PyErr_CheckSignals ()

     This function interacts with Python’s signal handling.  It checks
     whether a signal has been sent to the processes and if so, invokes
     the corresponding signal handler.  If the *note signal: eb. module
     is supported, this can invoke a signal handler written in Python.
     In all cases, the default effect for ‘SIGINT’ is to raise the *note
     KeyboardInterrupt: 198. exception.  If an exception is raised the
     error indicator is set and the function returns ‘-1’; otherwise the
     function returns ‘0’.  The error indicator may or may not be
     cleared if it was previously set.

 -- C 函式: void PyErr_SetInterrupt ()

     Simulate the effect of a ‘SIGINT’ signal arriving.  The next time
     *note PyErr_CheckSignals(): 3bed. is called, the Python signal
     handler for ‘SIGINT’ will be called.

     If ‘SIGINT’ isn’t handled by Python (it was set to *note
     signal.SIG_DFL: 24d9. or *note signal.SIG_IGN: 24da.), this
     function does nothing.

 -- 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(): 3d3. 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: Exception Classes,  Next: Exception Objects,  Prev: Signal Handling<2>,  Up: 例外處理

7.5.6 Exception Classes
-----------------------

 -- C 函式: PyObject* PyErr_NewException (const char *name,
          PyObject *base, PyObject *dict)
     `Return value: New reference.'  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:
     1aa. (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 函式: PyObject* PyErr_NewExceptionWithDoc (const char *name, const
          char *doc, PyObject *base, PyObject *dict)
     `Return value: New reference.'  Same as *note PyErr_NewException():
     c05, 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: Exception Objects,  Next: Unicode Exception Objects,  Prev: Exception Classes,  Up: 例外處理

7.5.7 Exception Objects
-----------------------

 -- C 函式: PyObject* PyException_GetTraceback (PyObject *ex)
     `Return value: New reference.'  Return the traceback associated
     with the exception as a new reference, as accessible from Python
     through ‘__traceback__’.  If there is no traceback associated, this
     returns ‘NULL’.

 -- C 函式: int PyException_SetTraceback (PyObject *ex, PyObject *tb)

     Set the traceback associated with the exception to `tb'.  Use
     ‘Py_None’ to clear it.

 -- C 函式: PyObject* PyException_GetContext (PyObject *ex)
     `Return value: New reference.'  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 ‘__context__’.  If there is no context
     associated, this returns ‘NULL’.

 -- C 函式: void PyException_SetContext (PyObject *ex, PyObject *ctx)

     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 函式: PyObject* PyException_GetCause (PyObject *ex)
     `Return value: New reference.'  Return the cause (either an
     exception instance, or *note None: 158, set by ‘raise ... from
     ...’) associated with the exception as a new reference, as
     accessible from Python through ‘__cause__’.

 -- C 函式: void PyException_SetCause (PyObject *ex, PyObject *cause)

     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 *note None: 158.  This steals a
     reference to `cause'.

     ‘__suppress_context__’ is implicitly set to ‘True’ by this
     function.


File: python.info,  Node: Unicode Exception Objects,  Next: Recursion Control,  Prev: Exception Objects,  Up: 例外處理

7.5.8 Unicode Exception Objects
-------------------------------

The following functions are used to create and modify Unicode exceptions
from C.

 -- C 函式: PyObject* PyUnicodeDecodeError_Create (const char *encoding,
          const char *object, Py_ssize_t length, Py_ssize_t start,
          Py_ssize_t end, const char *reason)
     `Return value: New reference.'  Create a *note UnicodeDecodeError:
     1fe. object with the attributes `encoding', `object', `length',
     `start', `end' and `reason'.  `encoding' and `reason' are UTF-8
     encoded strings.

 -- C 函式: PyObject* PyUnicodeEncodeError_Create (const char *encoding,
          const Py_UNICODE *object, Py_ssize_t length, Py_ssize_t start,
          Py_ssize_t end, const char *reason)
     `Return value: New reference.'  Create a *note UnicodeEncodeError:
     1fd. object with the attributes `encoding', `object', `length',
     `start', `end' and `reason'.  `encoding' and `reason' are UTF-8
     encoded strings.

     3.3 版後已棄用: 3.11

     ‘Py_UNICODE’ is deprecated since Python 3.3.  Please migrate to
     ‘PyObject_CallFunction(PyExc_UnicodeEncodeError, "sOnns", ...)’.

 -- C 函式: PyObject* PyUnicodeTranslateError_Create (const
          Py_UNICODE *object, Py_ssize_t length, Py_ssize_t start,
          Py_ssize_t end, const char *reason)
     `Return value: New reference.'  Create a *note
     UnicodeTranslateError: 171a. object with the attributes `object',
     `length', `start', `end' and `reason'.  `reason' is a UTF-8 encoded
     string.

     3.3 版後已棄用: 3.11

     ‘Py_UNICODE’ is deprecated since Python 3.3.  Please migrate to
     ‘PyObject_CallFunction(PyExc_UnicodeTranslateError, "Onns", ...)’.

 -- C 函式: PyObject* PyUnicodeDecodeError_GetEncoding (PyObject *exc)
 -- C 函式: PyObject* PyUnicodeEncodeError_GetEncoding (PyObject *exc)
     `Return value: New reference.'  Return the `encoding' attribute of
     the given exception object.

 -- C 函式: PyObject* PyUnicodeDecodeError_GetObject (PyObject *exc)
 -- C 函式: PyObject* PyUnicodeEncodeError_GetObject (PyObject *exc)
 -- C 函式: PyObject* PyUnicodeTranslateError_GetObject (PyObject *exc)
     `Return value: New reference.'  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)

     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)

     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)

     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)

     Set the `end' attribute of the given exception object to `end'.
     Return ‘0’ on success, ‘-1’ on failure.

 -- C 函式: PyObject* PyUnicodeDecodeError_GetReason (PyObject *exc)
 -- C 函式: PyObject* PyUnicodeEncodeError_GetReason (PyObject *exc)
 -- C 函式: PyObject* PyUnicodeTranslateError_GetReason (PyObject *exc)
     `Return value: New reference.'  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)

     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).

 -- C 函式: int Py_EnterRecursiveCall (const char *where)

     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(): 3c2b.  In this is
     the case, it sets a *note MemoryError: ef1. and returns a nonzero
     value.

     The function then checks if the recursion limit is reached.  If
     this is the case, a *note RecursionError: 639. is set and a nonzero
     value is returned.  Otherwise, zero is returned.

     `where' should be a string such as ‘" in instance check"’ to be
     concatenated to the *note RecursionError: 639. message caused by
     the recursion depth limit.

 -- C 函式: void Py_LeaveRecursiveCall ()

     Ends a *note Py_EnterRecursiveCall(): 3c2a.  Must be called once
     for each `successful' invocation of *note Py_EnterRecursiveCall():
     3c2a.

Properly implementing *note tp_repr: 3b54. for container types requires
special recursion handling.  In addition to protecting the stack, *note
tp_repr: 3b54. 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(): b75.

 -- C 函式: int Py_ReprEnter (PyObject *object)

     Called at the beginning of the *note tp_repr: 3b54. implementation
     to detect cycles.

     If the object has already been processed, the function returns a
     positive integer.  In that case the *note tp_repr: 3b54.
     implementation should return a string object indicating a cycle.
     As examples, *note dict: 1b9. objects return ‘{...}’ and *note
     list: 263. objects return ‘[...]’.

     The function will return a negative integer if the recursion limit
     is reached.  In that case the *note tp_repr: 3b54. implementation
     should typically return ‘NULL’.

     Otherwise, the function returns zero and the *note tp_repr: 3b54.
     implementation can continue normally.

 -- C 函式: void Py_ReprLeave (PyObject *object)

     Ends a *note Py_ReprEnter(): 3c2d.  Must be called once for each
     invocation of *note Py_ReprEnter(): 3c2d. 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*: 4bf.; they are all class objects.  For
completeness, here are all the variables:

C Name                                        Python Name                           註解
                                                                                    
---------------------------------------------------------------------------------------------------
                                                                                    
‘PyExc_BaseException’                         *note BaseException: 1a9.             (1)
                                                                                    
                                                                                    
‘PyExc_Exception’                             *note Exception: 1aa.                 (1)
                                                                                    
                                                                                    
‘PyExc_ArithmeticError’                       *note ArithmeticError: 1703.          (1)
                                                                                    
                                                                                    
‘PyExc_AssertionError’                        *note AssertionError: 1033.
                                              
                                                                                    
‘PyExc_AttributeError’                        *note AttributeError: 3a0.
                                              
                                                                                    
‘PyExc_BlockingIOError’                       *note BlockingIOError: 99c.
                                              
                                                                                    
‘PyExc_BrokenPipeError’                       *note BrokenPipeError: 9a2.
                                              
                                                                                    
‘PyExc_BufferError’                           *note BufferError: 1705.
                                              
                                                                                    
‘PyExc_ChildProcessError’                     *note ChildProcessError: 99d.
                                              
                                                                                    
‘PyExc_ConnectionAbortedError’                *note ConnectionAbortedError: 9a3.
                                              
                                                                                    
‘PyExc_ConnectionError’                       *note ConnectionError: 6eb.
                                              
                                                                                    
‘PyExc_ConnectionRefusedError’                *note ConnectionRefusedError: 9a4.
                                              
                                                                                    
‘PyExc_ConnectionResetError’                  *note ConnectionResetError: 9a5.
                                              
                                                                                    
‘PyExc_EOFError’                              *note EOFError: c71.
                                              
                                                                                    
‘PyExc_FileExistsError’                       *note FileExistsError: 95d.
                                              
                                                                                    
‘PyExc_FileNotFoundError’                     *note FileNotFoundError: 7c5.
                                              
                                                                                    
‘PyExc_FloatingPointError’                    *note FloatingPointError: 1704.
                                              
                                                                                    
‘PyExc_GeneratorExit’                         *note GeneratorExit: d37.
                                              
                                                                                    
‘PyExc_ImportError’                           *note ImportError: 339.
                                              
                                                                                    
‘PyExc_IndentationError’                      *note IndentationError: e7d.
                                              
                                                                                    
‘PyExc_IndexError’                            *note IndexError: e7a.
                                              
                                                                                    
‘PyExc_InterruptedError’                      *note InterruptedError: 65e.
                                              
                                                                                    
‘PyExc_IsADirectoryError’                     *note IsADirectoryError: 99e.
                                              
                                                                                    
‘PyExc_KeyError’                              *note KeyError: 2c8.
                                              
                                                                                    
‘PyExc_KeyboardInterrupt’                     *note KeyboardInterrupt: 198.
                                              
                                                                                    
‘PyExc_LookupError’                           *note LookupError: 1662.              (1)
                                                                                    
                                                                                    
‘PyExc_MemoryError’                           *note MemoryError: ef1.
                                              
                                                                                    
‘PyExc_ModuleNotFoundError’                   *note ModuleNotFoundError: 39f.
                                              
                                                                                    
‘PyExc_NameError’                             *note NameError: d80.
                                              
                                                                                    
‘PyExc_NotADirectoryError’                    *note NotADirectoryError: 99f.
                                              
                                                                                    
‘PyExc_NotImplementedError’                   *note NotImplementedError: 613.
                                              
                                                                                    
‘PyExc_OSError’                               *note OSError: 1d4.                   (1)
                                                                                    
                                                                                    
‘PyExc_OverflowError’                         *note OverflowError: 965.
                                              
                                                                                    
‘PyExc_PermissionError’                       *note PermissionError: 604.
                                              
                                                                                    
‘PyExc_ProcessLookupError’                    *note ProcessLookupError: 9a0.
                                              
                                                                                    
‘PyExc_RecursionError’                        *note RecursionError: 639.
                                              
                                                                                    
‘PyExc_ReferenceError’                        *note ReferenceError: e52.            (2)
                                                                                    
                                                                                    
‘PyExc_RuntimeError’                          *note RuntimeError: 2bb.
                                              
                                                                                    
‘PyExc_StopAsyncIteration’                    *note StopAsyncIteration: 1017.
                                              
                                                                                    
‘PyExc_StopIteration’                         *note StopIteration: 48b.
                                              
                                                                                    
‘PyExc_SyntaxError’                           *note SyntaxError: 45d.
                                              
                                                                                    
‘PyExc_SystemError’                           *note SystemError: 600.
                                              
                                                                                    
‘PyExc_SystemExit’                            *note SystemExit: 601.
                                              
                                                                                    
‘PyExc_TabError’                              *note TabError: e7c.
                                              
                                                                                    
‘PyExc_TimeoutError’                          *note TimeoutError: 9a1.
                                              
                                                                                    
‘PyExc_TypeError’                             *note TypeError: 193.
                                              
                                                                                    
‘PyExc_UnboundLocalError’                     *note UnboundLocalError: e7b.
                                              
                                                                                    
‘PyExc_UnicodeDecodeError’                    *note UnicodeDecodeError: 1fe.
                                              
                                                                                    
‘PyExc_UnicodeEncodeError’                    *note UnicodeEncodeError: 1fd.
                                              
                                                                                    
‘PyExc_UnicodeError’                          *note UnicodeError: c40.
                                              
                                                                                    
‘PyExc_UnicodeTranslateError’                 *note UnicodeTranslateError: 171a.
                                              
                                                                                    
‘PyExc_ValueError’                            *note ValueError: 1fc.
                                              
                                                                                    
‘PyExc_ZeroDivisionError’                     *note ZeroDivisionError: 12b2.
                                              

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’ and
‘PyExc_TimeoutError’ were introduced following PEP 3151(1).

3.5 版新加入: ‘PyExc_StopAsyncIteration’ and ‘PyExc_RecursionError’.

3.6 版新加入: ‘PyExc_ModuleNotFoundError’.

These are compatibility aliases to ‘PyExc_OSError’:

C Name                                    註解
                                          
---------------------------------------------------------
                                          
‘PyExc_EnvironmentError’

‘PyExc_IOError’

‘PyExc_WindowsError’                      (3)
                                          

3.3 版更變: These aliases used to be separate exception types.

註解：

  1. This is a base class for other standard exceptions.

  2. Only defined on Windows; protect code that uses this by testing
     that the preprocessor macro ‘MS_WINDOWS’ is defined.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3151


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*: 4bf.; they are all class objects.  For
completeness, here are all the variables:

C Name                                         Python Name                           註解
                                                                                     
----------------------------------------------------------------------------------------------------
                                                                                     
‘PyExc_Warning’                                *note Warning: 171f.                  (1)
                                                                                     
                                                                                     
‘PyExc_BytesWarning’                           *note BytesWarning: 4ba.
                                               
                                                                                     
‘PyExc_DeprecationWarning’                     *note DeprecationWarning: 279.
                                               
                                                                                     
‘PyExc_FutureWarning’                          *note FutureWarning: 32a.
                                               
                                                                                     
‘PyExc_ImportWarning’                          *note ImportWarning: 5dd.
                                               
                                                                                     
‘PyExc_PendingDeprecationWarning’              *note PendingDeprecationWarning: 27a.
                                               
                                                                                     
‘PyExc_ResourceWarning’                        *note ResourceWarning: 4d5.
                                               
                                                                                     
‘PyExc_RuntimeWarning’                         *note RuntimeWarning: 2c1.
                                               
                                                                                     
‘PyExc_SyntaxWarning’                          *note SyntaxWarning: 192.
                                               
                                                                                     
‘PyExc_UnicodeWarning’                         *note UnicodeWarning: d8c.
                                               
                                                                                     
‘PyExc_UserWarning’                            *note UserWarning: 1720.
                                               

3.2 版新加入: ‘PyExc_ResourceWarning’.

註解：

  1. This is a base class for other standard warning categories.


File: python.info,  Node: 工具,  Next: 抽象物件層,  Prev: 例外處理,  Up: Python / C API 參考手冊

7.6 工具
========

The functions in this chapter perform various utility tasks, ranging
from helping C code be more portable across platforms, using Python
modules from C, and parsing function arguments and constructing Python
values from C values.

* Menu:

* 作業系統工具::
* 系統函式::
* 行程（Process）控制::
* 匯入模組: 匯入模組<2>.
* Data marshalling support::
* Parsing arguments and building values::
* 字串轉換與格式化::
* Reflection::
* Codec registry and support functions::


File: python.info,  Node: 作業系統工具,  Next: 系統函式,  Up: 工具

7.6.1 作業系統工具
------------------

 -- C 函式: PyObject* PyOS_FSPath (PyObject *path)
     `Return value: New reference.'  Return the file system
     representation for `path'.  If the object is a *note str: 335. or
     *note bytes: 336. object, then its reference count is incremented.
     If the object implements the *note os.PathLike: 4f0. interface,
     then *note __fspath__(): 4f1. is returned as long as it is a *note
     str: 335. or *note bytes: 336. object.  Otherwise *note TypeError:
     193. 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 global flag *note
     Py_InteractiveFlag: 3c39. is true, this function also returns true
     if the `filename' pointer is ‘NULL’ or if the name is equal to one
     of the strings ‘'<stdin>'’ or ‘'???'’.

 -- C 函式: void PyOS_BeforeFork ()

     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: 3c3a. (of the *note "main" interpreter: 3c3b.).
          The same is true for ‘PyOS_BeforeFork()’.

     3.7 版新加入.

 -- C 函式: void PyOS_AfterFork_Parent ()

     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: 3c3a. (of the *note "main" interpreter: 3c3b.).
          The same is true for ‘PyOS_AfterFork_Parent()’.

     3.7 版新加入.

 -- C 函式: void PyOS_AfterFork_Child ()

     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: 3c3a. (of the *note "main" interpreter: 3c3b.).
          The same is true for ‘PyOS_AfterFork_Child()’.

     3.7 版新加入.

     也參考
     ......

     *note os.register_at_fork(): 3bb. allows registering custom Python
     functions to be called by *note PyOS_BeforeFork(): 437, *note
     PyOS_AfterFork_Parent(): 438. and *note PyOS_AfterFork_Child():
     2ce.

 -- C 函式: void PyOS_AfterFork ()

     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(): 2ce.

 -- C 函式: int PyOS_CheckStack ()

     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 Windows using the Microsoft Visual C++
     compiler).  ‘USE_STACKCHECK’ will be defined automatically; you
     should never change the definition in your own code.

 -- C 函式: PyOS_sighandler_t PyOS_getsig (int i)

     Return the current signal handler for signal `i'.  This is a thin
     wrapper around either ‘sigaction()’ or ‘signal()’.  Do not call
     those functions directly!  ‘PyOS_sighandler_t’ is a typedef alias
     for ‘void (*)(int)’.

 -- C 函式: PyOS_sighandler_t PyOS_setsig (int i, PyOS_sighandler_t h)

     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!
     ‘PyOS_sighandler_t’ is a typedef alias for ‘void (*)(int)’.

 -- C 函式: wchar_t* Py_DecodeLocale (const char* arg, size_t *size)

     Decode a byte string from the locale encoding with the *note
     surrogateescape error handler: 184d.: undecodable bytes are decoded
     as characters in range U+DC80..U+DCFF. If a byte sequence can be
     decoded as a surrogate character, escape the bytes using the
     surrogateescape error handler instead of decoding them.

     Encoding, highest priority to lowest priority:

        * ‘UTF-8’ on macOS, Android, and VxWorks;

        * ‘UTF-8’ on Windows if *note Py_LegacyWindowsFSEncodingFlag:
          3c3e. is zero;

        * ‘UTF-8’ if the Python UTF-8 mode is enabled;

        * ‘ASCII’ if the ‘LC_CTYPE’ locale is ‘"C"’,
          ‘nl_langinfo(CODESET)’ returns the ‘ASCII’ encoding (or an
          alias), and ‘mbstowcs()’ and ‘wcstombs()’ functions uses the
          ‘ISO-8859-1’ encoding.

        * the current locale encoding.

     Return a pointer to a newly allocated wide character string, use
     *note PyMem_RawFree(): 3c3f. 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.

     Decoding errors should never happen, unless there is a bug in the C
     library.

     Use the *note Py_EncodeLocale(): 442. function to encode the
     character string back to a byte string.

     也參考
     ......

     The *note PyUnicode_DecodeFSDefaultAndSize(): 3c40. and *note
     PyUnicode_DecodeLocaleAndSize(): 443. functions.

     3.5 版新加入.

     3.7 版更變: The function now uses the UTF-8 encoding in the UTF-8
     mode.

     3.8 版更變: The function now uses the UTF-8 encoding on Windows if
     *note Py_LegacyWindowsFSEncodingFlag: 3c3e. is zero;

 -- C 函式: char* Py_EncodeLocale (const wchar_t *text,
          size_t *error_pos)

     Encode a wide character string to the locale encoding with the
     *note surrogateescape error handler: 184d.: surrogate characters in
     the range U+DC80..U+DCFF are converted to bytes 0x80..0xFF.

     Encoding, highest priority to lowest priority:

        * ‘UTF-8’ on macOS, Android, and VxWorks;

        * ‘UTF-8’ on Windows if *note Py_LegacyWindowsFSEncodingFlag:
          3c3e. is zero;

        * ‘UTF-8’ if the Python UTF-8 mode is enabled;

        * ‘ASCII’ if the ‘LC_CTYPE’ locale is ‘"C"’,
          ‘nl_langinfo(CODESET)’ returns the ‘ASCII’ encoding (or an
          alias), and ‘mbstowcs()’ and ‘wcstombs()’ functions uses the
          ‘ISO-8859-1’ encoding.

        * the current locale encoding.

     The function uses the UTF-8 encoding in the Python UTF-8 mode.

     Return a pointer to a newly allocated byte string, use *note
     PyMem_Free(): dae. 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.

     Use the *note Py_DecodeLocale(): 441. function to decode the bytes
     string back to a wide character string.

     也參考
     ......

     The *note PyUnicode_EncodeFSDefault(): 1050. and *note
     PyUnicode_EncodeLocale(): 444. functions.

     3.5 版新加入.

     3.7 版更變: The function now uses the UTF-8 encoding in the UTF-8
     mode.

     3.8 版更變: The function now uses the UTF-8 encoding on Windows if
     *note Py_LegacyWindowsFSEncodingFlag: 3c3e. is zero;


File: python.info,  Node: 系統函式,  Next: 行程（Process）控制,  Prev: 作業系統工具,  Up: 工具

7.6.2 系統函式
--------------

These are utility functions that make functionality from the *note sys:
fe. module accessible to C code.  They all work with the current
interpreter thread’s *note sys: fe. module’s dict, which is contained in
the internal thread state structure.

 -- C 函式: PyObject *PySys_GetObject (const char *name)
     `Return value: Borrowed reference.'  Return the object `name' from
     the *note sys: fe. module or ‘NULL’ if it does not exist, without
     setting an exception.

 -- C 函式: int PySys_SetObject (const char *name, PyObject *v)

     Set `name' in the *note sys: fe. 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 ()

     Reset *note sys.warnoptions: 41b. to an empty list.  This function
     may be called prior to *note Py_Initialize(): 43e.

 -- C 函式: void PySys_AddWarnOption (const wchar_t *s)

     Append `s' to *note sys.warnoptions: 41b.  This function must be
     called prior to *note Py_Initialize(): 43e. in order to affect the
     warnings filter list.

 -- C 函式: void PySys_AddWarnOptionUnicode (PyObject *unicode)

     Append `unicode' to *note sys.warnoptions: 41b.

     Note: this function is not currently usable from outside the
     CPython implementation, as it must be called prior to the implicit
     import of *note warnings: 127. in *note Py_Initialize(): 43e. to be
     effective, but can’t be called until enough of the runtime has been
     initialized to permit the creation of Unicode objects.

 -- C 函式: void PySys_SetPath (const wchar_t *path)

     Set *note sys.path: 48d. to a list object of paths found in `path'
     which should be a list of paths separated with the platform’s
     search path delimiter (‘:’ on Unix, ‘;’ on Windows).

 -- C 函式: void PySys_WriteStdout (const char *format, ...)

     Write the output string described by `format' to *note sys.stdout:
     313.  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: 313. is unset, the
     formatted message is written to the real (C level) `stdout'.

 -- C 函式: void PySys_WriteStderr (const char *format, ...)

     As *note PySys_WriteStdout(): 3c47, but write to *note sys.stderr:
     314. or `stderr' instead.

 -- C 函式: void PySys_FormatStdout (const char *format, ...)

     Function similar to PySys_WriteStdout() but format the message
     using *note PyUnicode_FromFormatV(): 3c4a. and don’t truncate the
     message to an arbitrary length.

     3.2 版新加入.

 -- C 函式: void PySys_FormatStderr (const char *format, ...)

     As *note PySys_FormatStdout(): 3c49, but write to *note sys.stderr:
     314. or `stderr' instead.

     3.2 版新加入.

 -- C 函式: void PySys_AddXOption (const wchar_t *s)

     Parse `s' as a set of *note -X: 156. options and add them to the
     current options mapping as returned by *note PySys_GetXOptions():
     3c4d.  This function may be called prior to *note Py_Initialize():
     43e.

     3.2 版新加入.

 -- C 函式: PyObject *PySys_GetXOptions ()
     `Return value: Borrowed reference.'  Return the current dictionary
     of *note -X: 156. options, similarly to *note sys._xoptions: 1356.
     On error, ‘NULL’ is returned and an exception is set.

     3.2 版新加入.

 -- C 函式: int PySys_Audit (const char *event, const char *format, ...)

     Raise an auditing event with any active hooks.  Return zero for
     success and non-zero with an exception set on failure.

     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(): 2cf. are available.
     If the built value is not a tuple, it will be added into a
     single-element tuple.  (The ‘N’ format option 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
     ‘Py_ssize_t’, regardless of whether ‘PY_SSIZE_T_CLEAN’ was defined.

     *note sys.audit(): f2d. performs the same function from Python
     code.

     3.8 版新加入.

     3.8.2 版更變: Require ‘Py_ssize_t’ for ‘#’ format characters.
     Previously, an unavoidable deprecation warning was raised.

 -- C 函式: int PySys_AddAuditHook (Py_AuditHookFunction hook,
          void *userData)

     Append the callable `hook' to the list of active auditing hooks.
     Return zero for 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(): 43e.
     When called after runtime initialization, existing audit hooks are
     notified and may silently abort the operation by raising an error
     subclassed from *note Exception: 1aa. (other errors will not be
     silenced).

     The hook function is of type ‘int (*)(const char *event, PyObject
     *args, void *userData)’, where `args' is guaranteed to be a *note
     PyTupleObject: 3c4e.  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: 34c4.  Details are in each function’s
     documentation.

     If the interpreter is initialized, this function raises a auditing
     event ‘sys.addaudithook’ with no arguments.  If any existing hooks
     raise an exception derived from *note Exception: 1aa, 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.

     3.8 版新加入.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0578


File: python.info,  Node: 行程（Process）控制,  Next: 匯入模組<2>,  Prev: 系統函式,  Up: 工具

7.6.3 行程（Process）控制
-------------------------

 -- C 函式: void Py_FatalError (const char *message)

     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.

 -- C 函式: void Py_Exit (int status)

     Exit the current process.  This calls *note Py_FinalizeEx(): 5ce.
     and then calls the standard C library function ‘exit(status)’.  If
     *note Py_FinalizeEx(): 5ce. indicates an error, the exit status is
     set to 120.

     3.6 版更變: Errors from finalization no longer ignored.

 -- C 函式: int Py_AtExit (void (*func)())

     Register a cleanup function to be called by *note Py_FinalizeEx():
     5ce.  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(): 3c51. 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: Data marshalling support,  Prev: 行程（Process）控制,  Up: 工具

7.6.4 匯入模組
--------------

 -- C 函式: PyObject* PyImport_ImportModule (const char *name)
     `Return value: New reference.'

     This is a simplified interface to *note PyImport_ImportModuleEx():
     b26. below, leaving the `globals' and `locals' arguments set to
     ‘NULL’ and `level' set to 0.  When the `name' argument contains a
     dot (when it specifies a submodule of a package), the `fromlist'
     argument is set to the list ‘['*']’ so that the return value is the
     named module rather than the top-level package containing it as
     would otherwise be the case.  (Unfortunately, this has an
     additional side effect when `name' in fact specifies a subpackage
     instead of a submodule: the submodules specified in the package’s
     ‘__all__’ variable are loaded.)  Return a new reference to the
     imported module, or ‘NULL’ with an exception set on failure.  A
     failing import of a module doesn’t leave the module in *note
     sys.modules: f2b.

     This function always uses absolute imports.

 -- C 函式: PyObject* PyImport_ImportModuleNoBlock (const char *name)
     `Return value: New reference.'  This function is a deprecated alias
     of *note PyImport_ImportModule(): c78.

     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.

 -- C 函式: PyObject* PyImport_ImportModuleEx (const char *name,
          PyObject *globals, PyObject *locals, PyObject *fromlist)
     `Return value: New reference.'

     Import a module.  This is best described by referring to the
     built-in Python function *note __import__(): 615.

     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__(): 615, 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(): c78.

 -- C 函式: PyObject* PyImport_ImportModuleLevelObject (PyObject *name,
          PyObject *globals, PyObject *locals, PyObject *fromlist,
          int level)
     `Return value: New reference.'  Import a module.  This is best
     described by referring to the built-in Python function *note
     __import__(): 615, as the standard *note __import__(): 615.
     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__(): 615, 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 函式: PyObject* PyImport_ImportModuleLevel (const char *name,
          PyObject *globals, PyObject *locals, PyObject *fromlist,
          int level)
     `Return value: New reference.'  Similar to *note
     PyImport_ImportModuleLevelObject(): 3c55, 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 函式: PyObject* PyImport_Import (PyObject *name)
     `Return value: New reference.'  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__(): 615. 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 函式: PyObject* PyImport_ReloadModule (PyObject *m)
     `Return value: New reference.'  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 函式: PyObject* PyImport_AddModuleObject (PyObject *name)
     `Return value: Borrowed reference.'  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 ‘NULL’ with an exception set on
     failure.

          備註: 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(): c78. 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.3 版新加入.

 -- C 函式: PyObject* PyImport_AddModule (const char *name)
     `Return value: Borrowed reference.'  Similar to *note
     PyImport_AddModuleObject(): 3c57, but the name is a UTF-8 encoded
     string instead of a Unicode object.

 -- C 函式: PyObject* PyImport_ExecCodeModule (const char *name,
          PyObject *co)
     `Return value: New reference.'

     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(): 1b5, 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:
     f2b. in error cases, even if `name' was already in *note
     sys.modules: f2b. on entry to *note PyImport_ExecCodeModule():
     3c58.  Leaving incompletely initialized modules in *note
     sys.modules: f2b. 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__: ebd. and *note __loader__: 95b. 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 ‘SourceFileLoader’ otherwise.

     The module’s *note __file__: ebc. attribute will be set to the code
     object’s ‘co_filename’.  If applicable, *note __cached__: b37. will
     also be set.

     This function will reload the module if it was already imported.
     See *note PyImport_ReloadModule(): 3c56. 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(): 3c59. and *note
     PyImport_ExecCodeModuleWithPathnames(): 3c5a.

 -- C 函式: PyObject* PyImport_ExecCodeModuleEx (const char *name,
          PyObject *co, const char *pathname)
     `Return value: New reference.'  Like *note
     PyImport_ExecCodeModule(): 3c58, but the *note __file__: ebc.
     attribute of the module object is set to `pathname' if it is
     non-‘NULL’.

     See also *note PyImport_ExecCodeModuleWithPathnames(): 3c5a.

 -- C 函式: PyObject* PyImport_ExecCodeModuleObject (PyObject *name,
          PyObject *co, PyObject *pathname, PyObject *cpathname)
     `Return value: New reference.'  Like *note
     PyImport_ExecCodeModuleEx(): 3c59, but the *note __cached__: b37.
     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 版新加入.

 -- C 函式: PyObject* PyImport_ExecCodeModuleWithPathnames (const
          char *name, PyObject *co, const char *pathname, const
          char *cpathname)
     `Return value: New reference.'  Like *note
     PyImport_ExecCodeModuleObject(): 3c5b, 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 *note imp.source_from_cache(): 3adf. in
     calculating the source path if only the bytecode path is provided.

 -- C 函式: long PyImport_GetMagicNumber ()

     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 版更變: Return value of ‘-1’ upon failure.

 -- C 函式: const char * PyImport_GetMagicTag ()

     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 函式: PyObject* PyImport_GetModuleDict ()
     `Return value: Borrowed reference.'  Return the dictionary used for
     the module administration (a.k.a.  ‘sys.modules’).  Note that this
     is a per-interpreter variable.

 -- C 函式: PyObject* PyImport_GetModule (PyObject *name)
     `Return value: New reference.'  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 函式: PyObject* PyImport_GetImporter (PyObject *path)
     `Return value: New reference.'  Return a finder object for a *note
     sys.path: 48d./‘pkg.__path__’ item `path', possibly by fetching it
     from the *note sys.path_importer_cache: 4a2. dict.  If it wasn’t
     yet cached, traverse *note sys.path_hooks: 961. 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:
     14c5. could not find a finder for this path item.  Cache the result
     in *note sys.path_importer_cache: 4a2.  Return a new reference to
     the finder object.

 -- C 函式: void _PyImport_Init ()

     Initialize the import mechanism.  For internal use only.

 -- C 函式: void PyImport_Cleanup ()

     Empty the module table.  For internal use only.

 -- C 函式: void _PyImport_Fini ()

     Finalize the import mechanism.  For internal use only.

 -- C 函式: int PyImport_ImportFrozenModuleObject (PyObject *name)
     `Return value: New reference.'  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(): c78.  (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)

     Similar to *note PyImport_ImportFrozenModuleObject(): 3c62, 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;
          };

 -- C 變數: const struct _frozen* PyImport_FrozenModules

     This pointer is initialized to point to an array of ‘struct
     _frozen’ 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))

     Add a single module to the existing table of built-in modules.
     This is a convenience wrapper around *note
     PyImport_ExtendInittab(): 3c65, 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(): 43e.

 -- C 類型: struct _inittab

     Structure describing a single entry in the list of built-in
     modules.  Each of these structures gives the name and
     initialization function for a module built into the interpreter.
     The name is an ASCII encoded string.  Programs which embed Python
     may use an array of these structures in conjunction with *note
     PyImport_ExtendInittab(): 3c65. to provide additional built-in
     modules.  The structure is defined in ‘Include/import.h’ as:

          struct _inittab {
              const char *name;           /* ASCII encoded string */
              PyObject* (*initfunc)(void);
          };

 -- 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 ‘name’ 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 should be called before *note
     Py_Initialize(): 43e.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3147


File: python.info,  Node: Data marshalling support,  Next: Parsing arguments and building values,  Prev: 匯入模組<2>,  Up: 工具

7.6.5 Data marshalling support
------------------------------

These routines allow C code to work with serialized objects using the
same data format as the *note marshal: b1. 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.

 -- C 函式: void PyMarshal_WriteObjectToFile (PyObject *value,
          FILE *file, int version)

     Marshal a Python object, `value', to `file'.  `version' indicates
     the file format.

 -- C 函式: PyObject* PyMarshal_WriteObjectToString (PyObject *value,
          int version)
     `Return value: New reference.'  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: c71.) 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: c71.) and
     returns ‘-1’.

 -- C 函式: PyObject* PyMarshal_ReadObjectFromFile (FILE *file)
     `Return value: New reference.'  Return a Python object from the
     data stream in a ‘FILE*’ opened for reading.

     On error, sets the appropriate exception (*note EOFError: c71,
     *note ValueError: 1fc. or *note TypeError: 193.) and returns
     ‘NULL’.

 -- C 函式: PyObject* PyMarshal_ReadLastObjectFromFile (FILE *file)
     `Return value: New reference.'  Return a Python object from the
     data stream in a ‘FILE*’ opened for reading.  Unlike *note
     PyMarshal_ReadObjectFromFile(): 3c6f, 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: c71,
     *note ValueError: 1fc. or *note TypeError: 193.) and returns
     ‘NULL’.

 -- C 函式: PyObject* PyMarshal_ReadObjectFromString (const char *data,
          Py_ssize_t len)
     `Return value: New reference.'  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: c71,
     *note ValueError: 1fc. or *note TypeError: 193.) and returns
     ‘NULL’.


File: python.info,  Node: Parsing arguments and building values,  Next: 字串轉換與格式化,  Prev: Data marshalling support,  Up: 工具

7.6.6 Parsing arguments and building values
-------------------------------------------

These functions are useful when creating your own extensions functions
and methods.  Additional information and examples are available in *note
Extending and Embedding the Python Interpreter: 1202.

The first three of these functions described, *note PyArg_ParseTuple():
26b, *note PyArg_ParseTupleAndKeywords(): 5cf, and *note PyArg_Parse():
f6a, 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: Parsing arguments<3>.
* Building values::


File: python.info,  Node: Parsing arguments<3>,  Next: Building values,  Up: Parsing arguments and building values

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::
* 數字::
* Other objects::
* API Functions::


File: python.info,  Node: Strings and buffers,  Next: 數字,  Up: Parsing arguments<3>

7.6.6.2 Strings and buffers
...........................

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.

In general, when a format sets a pointer to a buffer, the buffer is
managed by the corresponding Python object, and the buffer shares the
lifetime of this object.  You won’t have to release any memory yourself.
The only exceptions are ‘es’, ‘es#’, ‘et’ and ‘et#’.

However, when a *note Py_buffer: b20. structure gets filled, the
underlying buffer is locked so that the caller can subsequently use the
buffer even inside a *note Py_BEGIN_ALLOW_THREADS: 3b20. block without
the risk of mutable data being resized or destroyed.  As a result, `you
have to call' *note PyBuffer_Release(): d59. after you have finished
processing the data (or in any early abort case).

Unless otherwise stated, buffers are not NUL-terminated.

Some formats require a read-only *note bytes-like object: 5ed, and set a
pointer instead of a buffer structure.  They work by checking that the
object’s *note PyBufferProcs.bf_releasebuffer: 3c76. field is ‘NULL’,
which disallows mutable objects such as *note bytearray: 337.

     備註: For all ‘#’ variants of formats (‘s#’, ‘y#’, etc.), the type
     of the length argument (int or ‘Py_ssize_t’) is controlled by
     defining the macro ‘PY_SSIZE_T_CLEAN’ before including ‘Python.h’.
     If the macro was defined, length is a ‘Py_ssize_t’ rather than an
     ‘int’.  This behavior will change in a future Python version to
     only support ‘Py_ssize_t’ and drop ‘int’ support.  It is best to
     always define ‘PY_SSIZE_T_CLEAN’.

‘s’ (*note str: 335.) [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: 1fc. exception is raised.  Unicode
     objects are converted to C strings using ‘'utf-8'’ encoding.  If
     this conversion fails, a *note UnicodeError: c40. is raised.

          備註: This format does not accept *note bytes-like objects:
          5ed.  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(): 5d3. as
          `converter'.

     3.5 版更變: Previously, *note TypeError: 193. was raised when
     embedded null code points were encountered in the Python string.

‘s*’ (*note str: 335. or *note bytes-like object: 5ed.) [Py_buffer]

     This format accepts Unicode objects as well as bytes-like objects.
     It fills a *note Py_buffer: b20. 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: 335, read-only *note bytes-like object: 5ed.) [const char *, int or ‘Py_ssize_t’]

     Like ‘s*’, except that it doesn’t accept mutable objects.  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: 335. or ‘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: 335, *note bytes-like object: 5ed. or ‘None’) [Py_buffer]

     Like ‘s*’, but the Python object may also be ‘None’, in which case
     the ‘buf’ member of the *note Py_buffer: b20. structure is set to
     ‘NULL’.

‘z#’ (*note str: 335, read-only *note bytes-like object: 5ed. or ‘None’) [const char *, int or ‘Py_ssize_t’]

     Like ‘s#’, but the Python object may also be ‘None’, in which case
     the C pointer is set to ‘NULL’.

‘y’ (read-only *note bytes-like object: 5ed.) [const char *]

     This format converts a bytes-like object to a C pointer to a
     character string; it does not accept Unicode objects.  The bytes
     buffer must not contain embedded null bytes; if it does, a *note
     ValueError: 1fc. exception is raised.

     3.5 版更變: Previously, *note TypeError: 193. was raised when
     embedded null bytes were encountered in the bytes buffer.

‘y*’ (*note bytes-like object: 5ed.) [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: 5ed.) [const char *, int or ‘Py_ssize_t’]

     This variant on ‘s#’ doesn’t accept Unicode objects, only
     bytes-like objects.

‘S’ (*note bytes: 336.) [PyBytesObject *]

     Requires that the Python object is a *note bytes: 336. object,
     without attempting any conversion.  Raises *note TypeError: 193. if
     the object is not a bytes object.  The C variable may also be
     declared as *note PyObject*: 4bf.

‘Y’ (*note bytearray: 337.) [PyByteArrayObject *]

     Requires that the Python object is a *note bytearray: 337. object,
     without attempting any conversion.  Raises *note TypeError: 193. if
     the object is not a *note bytearray: 337. object.  The C variable
     may also be declared as *note PyObject*: 4bf.

‘u’ (*note str: 335.) [const Py_UNICODE *]

     Convert a Python Unicode object to a C pointer to a NUL-terminated
     buffer of Unicode characters.  You must pass the address of a *note
     Py_UNICODE: af3. pointer variable, which will be filled with the
     pointer to an existing Unicode buffer.  Please note that the width
     of a *note Py_UNICODE: af3. character depends on compilation
     options (it is either 16 or 32 bits).  The Python string must not
     contain embedded null code points; if it does, a *note ValueError:
     1fc. exception is raised.

     3.5 版更變: Previously, *note TypeError: 193. was raised when
     embedded null code points were encountered in the Python string.

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsWideCharString(): 43d.

‘u#’ (*note str: 335.) [const Py_UNICODE *, int or ‘Py_ssize_t’]

     This variant on ‘u’ stores into two C variables, the first one a
     pointer to a Unicode data buffer, the second one its length.  This
     variant allows null code points.

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsWideCharString(): 43d.

‘Z’ (*note str: 335. or ‘None’) [const Py_UNICODE *]

     Like ‘u’, but the Python object may also be ‘None’, in which case
     the *note Py_UNICODE: af3. pointer is set to ‘NULL’.

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsWideCharString(): 43d.

‘Z#’ (*note str: 335. or ‘None’) [const Py_UNICODE *, int or ‘Py_ssize_t’]

     Like ‘u#’, but the Python object may also be ‘None’, in which case
     the *note Py_UNICODE: af3. pointer is set to ‘NULL’.

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsWideCharString(): 43d.

‘U’ (*note str: 335.) [PyObject *]

     Requires that the Python object is a Unicode object, without
     attempting any conversion.  Raises *note TypeError: 193. if the
     object is not a Unicode object.  The C variable may also be
     declared as *note PyObject*: 4bf.

‘w*’ (read-write *note bytes-like object: 5ed.) [Py_buffer]

     This format accepts any object which implements the read-write
     buffer interface.  It fills a *note Py_buffer: b20. structure
     provided by the caller.  The buffer may contain embedded null
     bytes.  The caller have to call *note PyBuffer_Release(): d59. when
     it is done with the buffer.

‘es’ (*note str: 335.) [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(): 26b. 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(): dae. to free the
     allocated buffer after use.

‘et’ (*note str: 335, *note bytes: 336. or *note bytearray: 337.) [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: 335.) [const char *encoding, char **buffer, int or ‘Py_ssize_t’ *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(): dae. to free
     the allocated buffer after usage.

     If `*buffer' points to a non-‘NULL’ pointer (an already allocated
     buffer), *note PyArg_ParseTuple(): 26b. 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: 1fc. 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: 335, *note bytes: 336. or *note bytearray: 337.) [const char *encoding, char **buffer, int or ‘Py_ssize_t’ *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.


File: python.info,  Node: 數字,  Next: Other objects,  Prev: Strings and buffers,  Up: Parsing arguments<3>

7.6.6.3 數字
............

‘b’ (*note int: 185.) [unsigned char]

     Convert a nonnegative Python integer to an unsigned tiny int,
     stored in a C ‘unsigned char’.

‘B’ (*note int: 185.) [unsigned char]

     Convert a Python integer to a tiny int without overflow checking,
     stored in a C ‘unsigned char’.

‘h’ (*note int: 185.) [short int]

     Convert a Python integer to a C ‘short int’.

‘H’ (*note int: 185.) [unsigned short int]

     Convert a Python integer to a C ‘unsigned short int’, without
     overflow checking.

‘i’ (*note int: 185.) [int]

     Convert a Python integer to a plain C ‘int’.

‘I’ (*note int: 185.) [unsigned int]

     Convert a Python integer to a C ‘unsigned int’, without overflow
     checking.

‘l’ (*note int: 185.) [long int]

     Convert a Python integer to a C ‘long int’.

‘k’ (*note int: 185.) [unsigned long]

     Convert a Python integer to a C ‘unsigned long’ without overflow
     checking.

‘L’ (*note int: 185.) [long long]

     Convert a Python integer to a C ‘long long’.

‘K’ (*note int: 185.) [unsigned long long]

     Convert a Python integer to a C ‘unsigned long long’ without
     overflow checking.

‘n’ (*note int: 185.) [Py_ssize_t]

     Convert a Python integer to a C ‘Py_ssize_t’.

‘c’ (*note bytes: 336. or *note bytearray: 337. of length 1) [char]

     Convert a Python byte, represented as a *note bytes: 336. or *note
     bytearray: 337. object of length 1, to a C ‘char’.

     3.3 版更變: Allow *note bytearray: 337. objects.

‘C’ (*note str: 335. of length 1) [int]

     Convert a Python character, represented as a *note str: 335. object
     of length 1, to a C ‘int’.

‘f’ (*note float: 188.) [float]

     Convert a Python floating point number to a C ‘float’.

‘d’ (*note float: 188.) [double]

     Convert a Python floating point number to a C ‘double’.

‘D’ (*note complex: 18a.) [Py_complex]

     Convert a Python complex number to a C *note Py_complex: 3c78.
     structure.


File: python.info,  Node: Other objects,  Next: API Functions,  Prev: 數字,  Up: Parsing arguments<3>

7.6.6.4 Other objects
.....................

‘O’ (object) [PyObject *]

     Store a Python object (without any conversion) in a C object
     pointer.  The C program thus receives the actual object that was
     passed.  The object’s reference count is not increased.  The
     pointer stored is not ‘NULL’.

‘O!’ (object) [`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*: 4bf.) into which the object pointer is
     stored.  If the Python object does not have the required type,
     *note TypeError: 193. is raised.

‘O&’ (object) [`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 *note
     PyArg_Parse*(): f6a. 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’ was added.

‘p’ (*note bool: 184.) [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 Truth Value
     Testing: 15e8. for more information about how Python tests values
     for truth.

     3.3 版新加入.

‘(items)’ (*note tuple: 483.) [`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(): 26b. does not
     touch the contents of the corresponding C variable(s).

‘$’

     *note PyArg_ParseTupleAndKeywords(): 5cf. 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(): 26b. 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 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 *note PyArg_Parse*():
f6a. functions return true, otherwise they return false and raise an
appropriate exception.  When the *note PyArg_Parse*(): f6a. 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 Functions,  Prev: Other objects,  Up: Parsing arguments<3>

7.6.6.5 API Functions
.....................

 -- C 函式: int PyArg_ParseTuple (PyObject *args, const char *format,
          ...)

     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)

     Identical to *note PyArg_ParseTuple(): 26b, 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 *keywords[], ...)

     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.  Empty
     names denote *note positional-only parameters: 2a8.  Returns true
     on success; on failure, it returns false and raises the appropriate
     exception.

     3.6 版更變: Added support for *note positional-only parameters:
     2a8.

 -- C 函式: int PyArg_VaParseTupleAndKeywords (PyObject *args,
          PyObject *kw, const char *format, char *keywords[],
          va_list vargs)

     Identical to *note PyArg_ParseTupleAndKeywords(): 5cf, except that
     it accepts a va_list rather than a variable number of arguments.

 -- C 函式: int PyArg_ValidateKeywordArguments (PyObject *)

     Ensure that the keys in the keywords argument dictionary are
     strings.  This is only needed if *note
     PyArg_ParseTupleAndKeywords(): 5cf. is not used, since the latter
     already does this check.

     3.2 版新加入.

 -- C 函式: int PyArg_Parse (PyObject *args, const char *format, ...)

     Function used to deconstruct the argument lists of "old-style"
     functions — these are functions which use the ‘METH_OLDARGS’
     parameter parsing method, which has been removed in Python 3.  This
     is not recommended for use in parameter parsing in new code, and
     most code in the standard interpreter has been modified to no
     longer use this for that purpose.  It does remain a convenient way
     to decompose other tuples, however, and may continue to be used for
     that purpose.

 -- C 函式: int PyArg_UnpackTuple (PyObject *args, const char *name,
          Py_ssize_t min, Py_ssize_t max, ...)

     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: e4d. 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*: 4bf. variable; these will
     be filled in with the values from `args'; they will contain
     borrowed references.  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(): e4b. in this example is
     entirely equivalent to this call to *note PyArg_ParseTuple(): 26b.:

          PyArg_ParseTuple(args, "O|O:ref", &object, &callback)


File: python.info,  Node: Building values,  Prev: Parsing arguments<3>,  Up: Parsing arguments and building values

7.6.6.6 Building values
.......................

 -- C 函式: PyObject* Py_BuildValue (const char *format, ...)
     `Return value: New reference.'  Create a new value based on a
     format string similar to those accepted by the *note
     PyArg_Parse*(): f6a. 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(): 2cf. 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(): 2cf.  In other words,
     if your code invokes ‘malloc()’ and passes the allocated memory to
     *note Py_BuildValue(): 2cf, your code is responsible for calling
     ‘free()’ for that memory once *note Py_BuildValue(): 2cf. 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: 335. or ‘None’) [const char *]

          Convert a null-terminated C string to a Python *note str: 335.
          object using ‘'utf-8'’ encoding.  If the C string pointer is
          ‘NULL’, ‘None’ is used.

     ‘s#’ (*note str: 335. or ‘None’) [const char *, int or ‘Py_ssize_t’]

          Convert a C string and its length to a Python *note str: 335.
          object using ‘'utf-8'’ encoding.  If the C string pointer is
          ‘NULL’, the length is ignored and ‘None’ is returned.

     ‘y’ (*note bytes: 336.) [const char *]

          This converts a C string to a Python *note bytes: 336. object.
          If the C string pointer is ‘NULL’, ‘None’ is returned.

     ‘y#’ (*note bytes: 336.) [const char *, int or ‘Py_ssize_t’]

          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: 335. or ‘None’) [const char *]

          Same as ‘s’.

     ‘z#’ (*note str: 335. or ‘None’) [const char *, int or ‘Py_ssize_t’]

          Same as ‘s#’.

     ‘u’ (*note str: 335.) [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: 335.) [const wchar_t *, int or ‘Py_ssize_t’]

          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: 335. or ‘None’) [const char *]

          Same as ‘s’.

     ‘U#’ (*note str: 335. or ‘None’) [const char *, int or ‘Py_ssize_t’]

          Same as ‘s#’.

     ‘i’ (*note int: 185.) [int]

          Convert a plain C ‘int’ to a Python integer object.

     ‘b’ (*note int: 185.) [char]

          Convert a plain C ‘char’ to a Python integer object.

     ‘h’ (*note int: 185.) [short int]

          Convert a plain C ‘short int’ to a Python integer object.

     ‘l’ (*note int: 185.) [long int]

          Convert a C ‘long int’ to a Python integer object.

     ‘B’ (*note int: 185.) [unsigned char]

          Convert a C ‘unsigned char’ to a Python integer object.

     ‘H’ (*note int: 185.) [unsigned short int]

          Convert a C ‘unsigned short int’ to a Python integer object.

     ‘I’ (*note int: 185.) [unsigned int]

          Convert a C ‘unsigned int’ to a Python integer object.

     ‘k’ (*note int: 185.) [unsigned long]

          Convert a C ‘unsigned long’ to a Python integer object.

     ‘L’ (*note int: 185.) [long long]

          Convert a C ‘long long’ to a Python integer object.

     ‘K’ (*note int: 185.) [unsigned long long]

          Convert a C ‘unsigned long long’ to a Python integer object.

     ‘n’ (*note int: 185.) [Py_ssize_t]

          Convert a C ‘Py_ssize_t’ to a Python integer.

     ‘c’ (*note bytes: 336. of length 1) [char]

          Convert a C ‘int’ representing a byte to a Python *note bytes:
          336. object of length 1.

     ‘C’ (*note str: 335. of length 1) [int]

          Convert a C ‘int’ representing a character to Python *note
          str: 335. object of length 1.

     ‘d’ (*note float: 188.) [double]

          Convert a C ‘double’ to a Python floating point number.

     ‘f’ (*note float: 188.) [float]

          Convert a C ‘float’ to a Python floating point number.

     ‘D’ (*note complex: 18a.) [Py_complex *]

          Convert a C *note Py_complex: 3c78. structure to a Python
          complex number.

     ‘O’ (object) [PyObject *]

          Pass a Python object untouched (except for its reference
          count, which 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(): 2cf. will
          return ‘NULL’ but won’t raise an exception.  If no exception
          has been raised yet, *note SystemError: 600. is set.

     ‘S’ (object) [PyObject *]

          Same as ‘O’.

     ‘N’ (object) [PyObject *]

          Same as ‘O’, except it doesn’t increment the reference count
          on the object.  Useful when the object is created by a call to
          an object constructor in the argument list.

     ‘O&’ (object) [`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: 483.) [`matching-items']

          Convert a sequence of C values to a Python tuple with the same
          number of items.

     ‘[items]’ (*note list: 263.) [`matching-items']

          Convert a sequence of C values to a Python list with the same
          number of items.

     ‘{items}’ (*note dict: 1b9.) [`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:
     600. exception is set and ‘NULL’ returned.

 -- C 函式: PyObject* Py_VaBuildValue (const char *format,
          va_list vargs)
     `Return value: New reference.'  Identical to *note Py_BuildValue():
     2cf, except that it accepts a va_list rather than a variable number
     of arguments.


File: python.info,  Node: 字串轉換與格式化,  Next: Reflection,  Prev: Parsing arguments and building values,  Up: 工具

7.6.7 字串轉換與格式化
----------------------

數字轉換函數和被格式化的字串輸出。

 -- C 函式: int PyOS_snprintf (char *str, size_t size, const
          char *format, ...)

     Output not more than `size' bytes to `str' according to the format
     string `format' and the extra arguments.  See the Unix man page
     ‘snprintf(3)’.

 -- C 函式: int PyOS_vsnprintf (char *str, size_t size, const
          char *format, va_list va)

     Output not more than `size' bytes to `str' according to the format
     string `format' and the variable argument list `va'.  Unix man page
     ‘vsnprintf(3)’.

*note PyOS_snprintf(): e4e. and *note PyOS_vsnprintf(): e4f. wrap the
Standard C library functions ‘snprintf()’ and ‘vsnprintf()’.  Their
purpose is to guarantee consistent behavior in corner cases, which the
Standard C functions do not.

The wrappers ensure that ‘str[size-1]’ is always ‘'\0'’ upon return.
They never write more than `size' bytes (including the trailing ‘'\0'’)
into str.  Both functions require that ‘str != NULL’, ‘size > 0’ and
‘format != NULL’.

If the platform doesn’t have ‘vsnprintf()’ and the buffer size needed to
avoid truncation exceeds `size' by more than 512 bytes, Python aborts
with a *note Py_FatalError(): f8f.

當回傳值 (`rv') 給這些函數應該被編譯如下：

   * When ‘0 <= rv < size’, the output conversion was successful and
     `rv' characters were written to `str' (excluding the trailing
     ‘'\0'’ byte at ‘str[rv]’).

   * When ‘rv >= size’, the output conversion was truncated and a buffer
     with ‘rv + 1’ bytes would have been needed to succeed.
     ‘str[size-1]’ is ‘'\0'’ in this case.

   * When ‘rv < 0’, "something bad happened."  ‘str[size-1]’ is ‘'\0'’
     in this case too, but the rest of `str' is undefined.  The exact
     cause of the error depends on the underlying platform.

The following functions provide locale-independent string to number
conversions.

 -- C 函式: double PyOS_string_to_double (const char *s, char **endptr,
          PyObject *overflow_exception)

     Convert a string ‘s’ to a ‘double’, raising a Python exception on
     failure.  The set of accepted strings corresponds to the set of
     strings accepted by Python’s *note float(): 188. constructor,
     except that ‘s’ must not have leading or trailing whitespace.  The
     conversion is independent of the current locale.

     If ‘endptr’ is ‘NULL’, convert the whole string.  Raise *note
     ValueError: 1fc. and return ‘-1.0’ if the string is not a valid
     representation of a floating-point number.

     If endptr is not ‘NULL’, convert as much of the string as possible
     and set ‘*endptr’ to point to the first unconverted character.  If
     no initial segment of the string is the valid representation of a
     floating-point number, set ‘*endptr’ to point to the beginning of
     the string, raise ValueError, and return ‘-1.0’.

     If ‘s’ represents a value that is too large to store in a float
     (for example, ‘"1e500"’ is such a string on many platforms) then if
     ‘overflow_exception’ is ‘NULL’ return ‘Py_HUGE_VAL’ (with an
     appropriate sign) and don’t set any exception.  Otherwise,
     ‘overflow_exception’ must point to a Python exception object; raise
     that exception and return ‘-1.0’.  In both cases, set ‘*endptr’ to
     point to the first character after the converted value.

     If any other error occurs during the conversion (for example an
     out-of-memory error), set the appropriate Python exception and
     return ‘-1.0’.

     3.1 版新加入.

 -- C 函式: char* PyOS_double_to_string (double val, char format_code,
          int precision, int flags, int *ptype)

     Convert a ‘double’ `val' to a string using supplied `format_code',
     `precision', and `flags'.

     `format_code' must be one of ‘'e'’, ‘'E'’, ‘'f'’, ‘'F'’, ‘'g'’,
     ‘'G'’ or ‘'r'’.  For ‘'r'’, the supplied `precision' must be 0 and
     is ignored.  The ‘'r'’ format code specifies the standard *note
     repr(): 7d1. format.

     `flags' can be zero or more of the values ‘Py_DTSF_SIGN’,
     ‘Py_DTSF_ADD_DOT_0’, or ‘Py_DTSF_ALT’, or-ed together:

        * ‘Py_DTSF_SIGN’ means to always precede the returned string
          with a sign character, even if `val' is non-negative.

        * ‘Py_DTSF_ADD_DOT_0’ means to ensure that the returned string
          will not look like an integer.

        * ‘Py_DTSF_ALT’ means to apply "alternate" formatting rules.
          See the documentation for the *note PyOS_snprintf(): e4e.
          ‘'#'’ specifier for details.

     If `ptype' is non-‘NULL’, then the value it points to will be set
     to one of ‘Py_DTST_FINITE’, ‘Py_DTST_INFINITE’, or ‘Py_DTST_NAN’,
     signifying that `val' is a finite number, an infinite number, or
     not a number, respectively.

     The return value is a pointer to `buffer' with the converted string
     or ‘NULL’ if the conversion failed.  The caller is responsible for
     freeing the returned string by calling *note PyMem_Free(): dae.

     3.1 版新加入.

 -- C 函式: int PyOS_stricmp (const char *s1, const char *s2)

     Case insensitive comparison of strings.  The function works almost
     identically to ‘strcmp()’ except that it ignores the case.

 -- C 函式: int PyOS_strnicmp (const char *s1, const char *s2,
          Py_ssize_t  size)

     Case insensitive comparison of strings.  The function works almost
     identically to ‘strncmp()’ except that it ignores the case.


File: python.info,  Node: Reflection,  Next: Codec registry and support functions,  Prev: 字串轉換與格式化,  Up: 工具

7.6.8 Reflection
----------------

 -- C 函式: PyObject* PyEval_GetBuiltins ()
     `Return value: Borrowed reference.'  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 函式: PyObject* PyEval_GetLocals ()
     `Return value: Borrowed reference.'  Return a dictionary of the
     local variables in the current execution frame, or ‘NULL’ if no
     frame is currently executing.

 -- C 函式: PyObject* PyEval_GetGlobals ()
     `Return value: Borrowed reference.'  Return a dictionary of the
     global variables in the current execution frame, or ‘NULL’ if no
     frame is currently executing.

 -- C 函式: PyFrameObject* PyEval_GetFrame ()
     `Return value: Borrowed reference.'  Return the current thread
     state’s frame, which is ‘NULL’ if no frame is currently executing.

 -- C 函式: int PyFrame_GetLineNumber (PyFrameObject *frame)

     Return the line number that `frame' is currently executing.

 -- C 函式: const char* PyEval_GetFuncName (PyObject *func)

     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)

     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(): 3c8d, the result will be a
     description of `func'.


File: python.info,  Node: Codec registry and support functions,  Prev: Reflection,  Up: 工具

7.6.9 Codec registry and support functions
------------------------------------------

 -- C 函式: int PyCodec_Register (PyObject *search_function)

     Register a new codec search function.

     As side effect, this tries to load the ‘encodings’ package, if not
     yet done, to make sure that it is always first in the list of
     search functions.

 -- C 函式: int PyCodec_KnownEncoding (const char *encoding)

     Return ‘1’ or ‘0’ depending on whether there is a registered codec
     for the given `encoding'.  This function always succeeds.

 -- C 函式: PyObject* PyCodec_Encode (PyObject *object, const
          char *encoding, const char *errors)
     `Return value: New reference.'  Generic codec based encoding API.

     `object' is passed through the encoder function found for the given
     `encoding' using the error handling method defined by `errors'.
     `errors' may be ‘NULL’ to use the default method defined for the
     codec.  Raises a *note LookupError: 1662. if no encoder can be
     found.

 -- C 函式: PyObject* PyCodec_Decode (PyObject *object, const
          char *encoding, const char *errors)
     `Return value: New reference.'  Generic codec based decoding API.

     `object' is passed through the decoder function found for the given
     `encoding' using the error handling method defined by `errors'.
     `errors' may be ‘NULL’ to use the default method defined for the
     codec.  Raises a *note LookupError: 1662. if no encoder can be
     found.

* Menu:

* Codec lookup API::
* Registry API for Unicode encoding error handlers::


File: python.info,  Node: Codec lookup API,  Next: Registry API for Unicode encoding error handlers,  Up: Codec registry and support functions

7.6.9.1 Codec lookup API
........................

In the following functions, the `encoding' string is looked up converted
to all lower-case characters, which makes encodings looked up through
this mechanism effectively case-insensitive.  If no codec is found, a
*note KeyError: 2c8. is set and ‘NULL’ returned.

 -- C 函式: PyObject* PyCodec_Encoder (const char *encoding)
     `Return value: New reference.'  Get an encoder function for the
     given `encoding'.

 -- C 函式: PyObject* PyCodec_Decoder (const char *encoding)
     `Return value: New reference.'  Get a decoder function for the
     given `encoding'.

 -- C 函式: PyObject* PyCodec_IncrementalEncoder (const char *encoding,
          const char *errors)
     `Return value: New reference.'  Get an *note IncrementalEncoder:
     1831. object for the given `encoding'.

 -- C 函式: PyObject* PyCodec_IncrementalDecoder (const char *encoding,
          const char *errors)
     `Return value: New reference.'  Get an *note IncrementalDecoder:
     1832. object for the given `encoding'.

 -- C 函式: PyObject* PyCodec_StreamReader (const char *encoding,
          PyObject *stream, const char *errors)
     `Return value: New reference.'  Get a *note StreamReader: 1836.
     factory function for the given `encoding'.

 -- C 函式: PyObject* PyCodec_StreamWriter (const char *encoding,
          PyObject *stream, const char *errors)
     `Return value: New reference.'  Get a *note StreamWriter: 1835.
     factory function for the given `encoding'.


File: python.info,  Node: Registry API for Unicode encoding error handlers,  Prev: Codec lookup API,  Up: Codec registry and support functions

7.6.9.2 Registry API for Unicode encoding error handlers
........................................................

 -- C 函式: int PyCodec_RegisterError (const char *name,
          PyObject *error)

     Register the error handling callback function `error' under the
     given `name'.  This callback function will be called by a codec
     when it encounters unencodable characters/undecodable bytes and
     `name' is specified as the error parameter in the call to the
     encode/decode function.

     The callback gets a single argument, an instance of *note
     UnicodeEncodeError: 1fd, *note UnicodeDecodeError: 1fe. or *note
     UnicodeTranslateError: 171a. that holds information about the
     problematic sequence of characters or bytes and their offset in the
     original string (see *note Unicode Exception Objects: 3c0e. for
     functions to extract this information).  The callback must either
     raise the given exception, or return a two-item tuple containing
     the replacement for the problematic sequence, and an integer giving
     the offset in the original string at which encoding/decoding should
     be resumed.

     Return ‘0’ on success, ‘-1’ on error.

 -- C 函式: PyObject* PyCodec_LookupError (const char *name)
     `Return value: New reference.'  Lookup the error handling callback
     function registered under `name'.  As a special case ‘NULL’ can be
     passed, in which case the error handling callback for "strict" will
     be returned.

 -- C 函式: PyObject* PyCodec_StrictErrors (PyObject *exc)
     `Return value: Always NULL.' Raise `exc' as an exception.

 -- C 函式: PyObject* PyCodec_IgnoreErrors (PyObject *exc)
     `Return value: New reference.'  Ignore the unicode error, skipping
     the faulty input.

 -- C 函式: PyObject* PyCodec_ReplaceErrors (PyObject *exc)
     `Return value: New reference.'  Replace the unicode encode error
     with ‘?’ or ‘U+FFFD’.

 -- C 函式: PyObject* PyCodec_XMLCharRefReplaceErrors (PyObject *exc)
     `Return value: New reference.'  Replace the unicode encode error
     with XML character references.

 -- C 函式: PyObject* PyCodec_BackslashReplaceErrors (PyObject *exc)
     `Return value: New reference.'  Replace the unicode encode error
     with backslash escapes (‘\x’, ‘\u’ and ‘\U’).

 -- C 函式: PyObject* PyCodec_NameReplaceErrors (PyObject *exc)
     `Return value: New reference.'  Replace the unicode encode error
     with ‘\N{...}’ escapes.

     3.5 版新加入.


File: python.info,  Node: 抽象物件層,  Next: Concrete Objects Layer,  Prev: 工具,  Up: Python / C API 參考手冊

7.7 抽象物件層
==============

The functions in this chapter interact with Python objects regardless of
their type, or with wide classes of object types (e.g.  all numerical
types, or all sequence types).  When used on object types for which they
do not apply, they will raise a Python exception.

It is not possible to use these functions on objects that are not
properly initialized, such as a list object that has been created by
*note PyList_New(): 3bab, but whose items have not been set to some
non-‘NULL’ value yet.

* Menu:

* Object Protocol::
* Number Protocol::
* Sequence Protocol::
* Mapping Protocol::
* Iterator Protocol::
* Buffer Protocol::
* Old Buffer Protocol::


File: python.info,  Node: Object Protocol,  Next: Number Protocol,  Up: 抽象物件層

7.7.1 Object Protocol
---------------------

 -- C 變數: PyObject* 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: 3ca9. from
     within a C function (that is, increment the reference count of
     NotImplemented and return it).

 -- 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 ‘Py_PRINT_RAW’; if given, the
     *note str(): 335. of the object is written instead of the *note
     repr(): 7d1.

 -- C 函式: int PyObject_HasAttr (PyObject *o, PyObject *attr_name)

     Returns ‘1’ if `o' has the attribute `attr_name', and ‘0’
     otherwise.  This is equivalent to the Python expression ‘hasattr(o,
     attr_name)’.  This function always succeeds.

     Note that exceptions which occur while calling *note __getattr__():
     31f. and *note __getattribute__(): 44e. methods will get
     suppressed.  To get error reporting use *note PyObject_GetAttr():
     3cac. instead.

 -- C 函式: int PyObject_HasAttrString (PyObject *o, const
          char *attr_name)

     Returns ‘1’ if `o' has the attribute `attr_name', and ‘0’
     otherwise.  This is equivalent to the Python expression ‘hasattr(o,
     attr_name)’.  This function always succeeds.

     Note that exceptions which occur while calling *note __getattr__():
     31f. and *note __getattribute__(): 44e. methods and creating a
     temporary string object will get suppressed.  To get error
     reporting use *note PyObject_GetAttrString(): 3b15. instead.

 -- C 函式: PyObject* PyObject_GetAttr (PyObject *o,
          PyObject *attr_name)
     `Return value: New reference.'  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’.

 -- C 函式: PyObject* PyObject_GetAttrString (PyObject *o, const
          char *attr_name)
     `Return value: New reference.'  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’.

 -- C 函式: PyObject* PyObject_GenericGetAttr (PyObject *o,
          PyObject *name)
     `Return value: New reference.'  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__: 501. (if present).  As outlined in *note Implementing
     Descriptors: 4ee, data descriptors take preference over instance
     attributes, while non-data descriptors don’t.  Otherwise, an *note
     AttributeError: 3a0. is raised.

 -- C 函式: int PyObject_SetAttr (PyObject *o, PyObject *attr_name,
          PyObject *v)

     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, however this feature is
     deprecated in favour of using *note PyObject_DelAttr(): 3cb0.

 -- C 函式: int PyObject_SetAttrString (PyObject *o, const
          char *attr_name, PyObject *v)

     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, however this feature is
     deprecated in favour of using *note PyObject_DelAttrString(): 3cb2.

 -- C 函式: int PyObject_GenericSetAttr (PyObject *o, PyObject *name,
          PyObject *value)

     Generic attribute setter and deleter function that is meant to be
     put into a type object’s *note tp_setattro: 3b5a. 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__: 501. (if present).
     On success, ‘0’ is returned, otherwise an *note AttributeError:
     3a0. is raised and ‘-1’ is returned.

 -- C 函式: int PyObject_DelAttr (PyObject *o, PyObject *attr_name)

     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)

     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 函式: PyObject* PyObject_GenericGetDict (PyObject *o,
          void *context)
     `Return value: New reference.'  A generic implementation for the
     getter of a ‘__dict__’ descriptor.  It creates the dictionary if
     necessary.

     3.3 版新加入.

 -- C 函式: int PyObject_GenericSetDict (PyObject *o, PyObject *value,
          void *context)

     A generic implementation for the setter of a ‘__dict__’ descriptor.
     This implementation does not allow the dictionary to be deleted.

     3.3 版新加入.

 -- C 函式: PyObject* PyObject_RichCompare (PyObject *o1, PyObject *o2,
          int opid)
     `Return value: New reference.'  Compare the values of `o1' and `o2'
     using the operation specified by `opid', which must be one of
     ‘Py_LT’, ‘Py_LE’, ‘Py_EQ’, ‘Py_NE’, ‘Py_GT’, or ‘Py_GE’,
     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)

     Compare the values of `o1' and `o2' using the operation specified
     by `opid', which must be one of ‘Py_LT’, ‘Py_LE’, ‘Py_EQ’, ‘Py_NE’,
     ‘Py_GT’, or ‘Py_GE’, corresponding to ‘<’, ‘<=’, ‘==’, ‘!=’, ‘>’,
     or ‘>=’ respectively.  Returns ‘-1’ on error, ‘0’ if the result is
     false, ‘1’ otherwise.  This is the equivalent of the Python
     expression ‘o1 op o2’, where ‘op’ is the operator corresponding to
     `opid'.

     備註: If `o1' and `o2' are the same object, *note
     PyObject_RichCompareBool(): f4c. will always return ‘1’ for ‘Py_EQ’
     and ‘0’ for ‘Py_NE’.

 -- C 函式: PyObject* PyObject_Repr (PyObject *o)
     `Return value: New reference.'

     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(): 7d1. 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 函式: PyObject* PyObject_ASCII (PyObject *o)
     `Return value: New reference.'

     As *note PyObject_Repr(): 96d, compute a string representation of
     object `o', but escape the non-ASCII characters in the string
     returned by *note PyObject_Repr(): 96d. with ‘\x’, ‘\u’ or ‘\U’
     escapes.  This generates a string similar to that returned by *note
     PyObject_Repr(): 96d. in Python 2.  Called by the *note ascii():
     d51. built-in function.

 -- C 函式: PyObject* PyObject_Str (PyObject *o)
     `Return value: New reference.'  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(): 335. built-in function and,
     therefore, by the *note print(): 88b. function.

     3.4 版更變: This function now includes a debug assertion to help
     ensure that it does not silently discard an active exception.

 -- C 函式: PyObject* PyObject_Bytes (PyObject *o)
     `Return value: New reference.'

     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)

     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__(): 1456. 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: 60d. or
     a derived class, are considered classes.  However, objects can
     override this by having a ‘__bases__’ attribute (which must be a
     tuple of base classes).

 -- C 函式: int PyObject_IsInstance (PyObject *inst, PyObject *cls)

     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__(): 1455. 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 ‘__class__’ attribute.

     An object `cls' can override if it is considered a class, and what
     its base classes are, by having a ‘__bases__’ attribute (which must
     be a tuple of base classes).

 -- C 函式: int PyCallable_Check (PyObject *o)

     Determine if the object `o' is callable.  Return ‘1’ if the object
     is callable and ‘0’ otherwise.  This function always succeeds.

 -- C 函式: PyObject* PyObject_Call (PyObject *callable, PyObject *args,
          PyObject *kwargs)
     `Return value: New reference.'  Call a callable Python object
     `callable', with arguments given by the tuple `args', and named
     arguments given by the dictionary `kwargs'.

     `args' must not be ‘NULL’, use an empty tuple if no arguments are
     needed.  If no named arguments are needed, `kwargs' can be ‘NULL’.

     Return the result of the call on success, or raise an exception and
     return ‘NULL’ on failure.

     This is the equivalent of the Python expression: ‘callable(*args,
     **kwargs)’.

 -- C 函式: PyObject* PyObject_CallObject (PyObject *callable,
          PyObject *args)
     `Return value: New reference.'  Call a callable Python object
     `callable', with arguments given by the tuple `args'.  If no
     arguments are needed, then `args' can be ‘NULL’.

     Return the result of the call on success, or raise an exception and
     return ‘NULL’ on failure.

     This is the equivalent of the Python expression: ‘callable(*args)’.

 -- C 函式: PyObject* PyObject_CallFunction (PyObject *callable, const
          char *format, ...)
     `Return value: New reference.'  Call a callable Python object
     `callable', with a variable number of C arguments.  The C arguments
     are described using a *note Py_BuildValue(): 2cf. style format
     string.  The format can be ‘NULL’, indicating that no arguments are
     provided.

     Return the result of the call on success, or raise an exception and
     return ‘NULL’ on failure.

     This is the equivalent of the Python expression: ‘callable(*args)’.

     Note that if you only pass *note PyObject *: 4bf. args, *note
     PyObject_CallFunctionObjArgs(): 3cb9. is a faster alternative.

     3.4 版更變: The type of `format' was changed from ‘char *’.

 -- C 函式: PyObject* PyObject_CallMethod (PyObject *obj, const
          char *name, const char *format, ...)
     `Return value: New reference.'  Call the method named `name' of
     object `obj' with a variable number of C arguments.  The C
     arguments are described by a *note Py_BuildValue(): 2cf. format
     string that should produce a tuple.

     The format can be ‘NULL’, indicating that no arguments are
     provided.

     Return the result of the call on success, or raise an exception and
     return ‘NULL’ on failure.

     This is the equivalent of the Python expression: ‘obj.name(arg1,
     arg2, ...)’.

     Note that if you only pass *note PyObject *: 4bf. args, *note
     PyObject_CallMethodObjArgs(): fde. is a faster alternative.

     3.4 版更變: The types of `name' and `format' were changed from
     ‘char *’.

 -- C 函式: PyObject* PyObject_CallFunctionObjArgs (PyObject *callable,
          ...)
     `Return value: New reference.'  Call a callable Python object
     `callable', with a variable number of *note PyObject*: 4bf.
     arguments.  The arguments are provided as a variable number of
     parameters followed by ‘NULL’.

     Return the result of the call on success, or raise an exception and
     return ‘NULL’ on failure.

     This is the equivalent of the Python expression: ‘callable(arg1,
     arg2, ...)’.

 -- C 函式: PyObject* PyObject_CallMethodObjArgs (PyObject *obj,
          PyObject *name, ...)
     `Return value: New reference.'  Calls a method of the Python object
     `obj', where the name of the method is given as a Python string
     object in `name'.  It is called with a variable number of *note
     PyObject*: 4bf. arguments.  The arguments are provided as a
     variable number of parameters followed by ‘NULL’.

     Return the result of the call on success, or raise an exception and
     return ‘NULL’ on failure.

 -- C 函式: PyObject* _PyObject_Vectorcall (PyObject *callable, PyObject
          *const *args, size_t nargsf, PyObject *kwnames)

     Call a callable Python object `callable', using *note vectorcall:
     3cbc. if possible.

     `args' is a C array with the positional arguments.

     `nargsf' is the number of positional arguments plus optionally the
     flag ‘PY_VECTORCALL_ARGUMENTS_OFFSET’ (see below).  To get actual
     number of arguments, use *note PyVectorcall_NARGS(nargsf): 3cbd.

     `kwnames' can be either ‘NULL’ (no keyword arguments) or a tuple of
     keyword names.  In the latter case, the values of the keyword
     arguments are stored in `args' after the positional arguments.  The
     number of keyword arguments does not influence `nargsf'.

     `kwnames' must contain only objects of type ‘str’ (not a subclass),
     and all keys must be unique.

     Return the result of the call on success, or raise an exception and
     return ‘NULL’ on failure.

     This uses the vectorcall protocol if the callable supports it;
     otherwise, the arguments are converted to use *note tp_call: 3b66.

          備註: This function is provisional and expected to become
          public in Python 3.9, with a different name and, possibly,
          changed semantics.  If you use the function, plan for updating
          your code for Python 3.9.

     3.8 版新加入.

 -- C 巨集: PY_VECTORCALL_ARGUMENTS_OFFSET

     If set in a vectorcall `nargsf' argument, the callee is allowed to
     temporarily change ‘args[-1]’.  In other words, `args' points to
     argument 1 (not 0) in the allocated vector.  The callee must
     restore the value of ‘args[-1]’ before returning.

     Whenever they can do so cheaply (without additional allocation),
     callers are encouraged to use ‘PY_VECTORCALL_ARGUMENTS_OFFSET’.
     Doing so will allow callables such as bound methods to make their
     onward calls (which include a prepended `self' argument) cheaply.

     3.8 版新加入.

 -- C 函式: Py_ssize_t PyVectorcall_NARGS (size_t nargsf)

     Given a vectorcall `nargsf' argument, return the actual number of
     arguments.  Currently equivalent to ‘nargsf &
     ~PY_VECTORCALL_ARGUMENTS_OFFSET’.

     3.8 版新加入.

 -- C 函式: PyObject* _PyObject_FastCallDict (PyObject *callable,
          PyObject *const *args, size_t nargsf, PyObject *kwdict)

     Same as *note _PyObject_Vectorcall(): 3cbb. except that the keyword
     arguments are passed as a dictionary in `kwdict'.  This may be
     ‘NULL’ if there are no keyword arguments.

     For callables supporting *note vectorcall: 3cbc, the arguments are
     internally converted to the vectorcall convention.  Therefore, this
     function adds some overhead compared to *note
     _PyObject_Vectorcall(): 3cbb.  It should only be used if the caller
     already has a dictionary ready to use.

          備註: This function is provisional and expected to become
          public in Python 3.9, with a different name and, possibly,
          changed semantics.  If you use the function, plan for updating
          your code for Python 3.9.

     3.8 版新加入.

 -- C 函式: Py_hash_t PyObject_Hash (PyObject *o)

     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 Py_ssize_t.

 -- C 函式: Py_hash_t PyObject_HashNotImplemented (PyObject *o)

     Set a *note TypeError: 193. indicating that ‘type(o)’ is not
     hashable 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)

     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)

     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 函式: PyObject* PyObject_Type (PyObject *o)
     `Return value: New reference.'

     When `o' is non-‘NULL’, returns a type object corresponding to the
     object type of object `o'.  On failure, raises *note SystemError:
     600. and returns ‘NULL’.  This is equivalent to the Python
     expression ‘type(o)’.  This function increments the reference count
     of the return value.  There’s really no reason to use this function
     instead of the common expression ‘o->ob_type’, which returns a
     pointer of type *note PyTypeObject*: 2d7, except when the
     incremented reference count is needed.

 -- C 函式: int PyObject_TypeCheck (PyObject *o, PyTypeObject *type)

     Return true if the object `o' is of type `type' or a subtype of
     `type'.  Both parameters must be non-‘NULL’.

 -- C 函式: Py_ssize_t PyObject_Size (PyObject *o)
 -- C 函式: Py_ssize_t PyObject_Length (PyObject *o)

     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 函式: Py_ssize_t PyObject_LengthHint (PyObject *o,
          Py_ssize_t default)

     Return an estimated length for the object `o'.  First try to return
     its actual length, then an estimate using *note __length_hint__():
     811, and finally return the default value.  On error return ‘-1’.
     This is the equivalent to the Python expression
     ‘operator.length_hint(o, default)’.

     3.4 版新加入.

 -- C 函式: PyObject* PyObject_GetItem (PyObject *o, PyObject *key)
     `Return value: New reference.'  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)

     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)

     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 函式: PyObject* PyObject_Dir (PyObject *o)
     `Return value: New reference.'  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(): 3af9. will return false.

 -- C 函式: PyObject* PyObject_GetIter (PyObject *o)
     `Return value: New reference.'  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: 193. and returns ‘NULL’ if the
     object cannot be iterated.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3119

   (2) https://www.python.org/dev/peps/pep-3119


File: python.info,  Node: Number Protocol,  Next: Sequence Protocol,  Prev: Object Protocol,  Up: 抽象物件層

7.7.2 Number Protocol
---------------------

 -- C 函式: int PyNumber_Check (PyObject *o)

     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 函式: PyObject* PyNumber_Add (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  Returns the result of adding `o1'
     and `o2', or ‘NULL’ on failure.  This is the equivalent of the
     Python expression ‘o1 + o2’.

 -- C 函式: PyObject* PyNumber_Subtract (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  Returns the result of subtracting
     `o2' from `o1', or ‘NULL’ on failure.  This is the equivalent of
     the Python expression ‘o1 - o2’.

 -- C 函式: PyObject* PyNumber_Multiply (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  Returns the result of multiplying
     `o1' and `o2', or ‘NULL’ on failure.  This is the equivalent of the
     Python expression ‘o1 * o2’.

 -- C 函式: PyObject* PyNumber_MatrixMultiply (PyObject *o1,
          PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_FloorDivide (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  Return the floor of `o1' divided by
     `o2', or ‘NULL’ on failure.  This is equivalent to the "classic"
     division of integers.

 -- C 函式: PyObject* PyNumber_TrueDivide (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  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.

 -- C 函式: PyObject* PyNumber_Remainder (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  Returns the remainder of dividing
     `o1' by `o2', or ‘NULL’ on failure.  This is the equivalent of the
     Python expression ‘o1 % o2’.

 -- C 函式: PyObject* PyNumber_Divmod (PyObject *o1, PyObject *o2)
     `Return value: New reference.'

     See the built-in function *note divmod(): 153.  Returns ‘NULL’ on
     failure.  This is the equivalent of the Python expression
     ‘divmod(o1, o2)’.

 -- C 函式: PyObject* PyNumber_Power (PyObject *o1, PyObject *o2,
          PyObject *o3)
     `Return value: New reference.'

     See the built-in function *note pow(): 19b.  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: 3afe. in its place (passing ‘NULL’ for `o3' would
     cause an illegal memory access).

 -- C 函式: PyObject* PyNumber_Negative (PyObject *o)
     `Return value: New reference.'  Returns the negation of `o' on
     success, or ‘NULL’ on failure.  This is the equivalent of the
     Python expression ‘-o’.

 -- C 函式: PyObject* PyNumber_Positive (PyObject *o)
     `Return value: New reference.'  Returns `o' on success, or ‘NULL’
     on failure.  This is the equivalent of the Python expression ‘+o’.

 -- C 函式: PyObject* PyNumber_Absolute (PyObject *o)
     `Return value: New reference.'

     Returns the absolute value of `o', or ‘NULL’ on failure.  This is
     the equivalent of the Python expression ‘abs(o)’.

 -- C 函式: PyObject* PyNumber_Invert (PyObject *o)
     `Return value: New reference.'  Returns the bitwise negation of `o'
     on success, or ‘NULL’ on failure.  This is the equivalent of the
     Python expression ‘~o’.

 -- C 函式: PyObject* PyNumber_Lshift (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_Rshift (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_And (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_Xor (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_Or (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlaceAdd (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlaceSubtract (PyObject *o1,
          PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlaceMultiply (PyObject *o1,
          PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlaceMatrixMultiply (PyObject *o1,
          PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlaceFloorDivide (PyObject *o1,
          PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlaceTrueDivide (PyObject *o1,
          PyObject *o2)
     `Return value: New reference.'  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.

 -- C 函式: PyObject* PyNumber_InPlaceRemainder (PyObject *o1,
          PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlacePower (PyObject *o1, PyObject *o2,
          PyObject *o3)
     `Return value: New reference.'

     See the built-in function *note pow(): 19b.  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: 3afe, or an in-place variant of ‘pow(o1, o2, o3)’
     otherwise.  If `o3' is to be ignored, pass *note Py_None: 3afe. in
     its place (passing ‘NULL’ for `o3' would cause an illegal memory
     access).

 -- C 函式: PyObject* PyNumber_InPlaceLshift (PyObject *o1,
          PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlaceRshift (PyObject *o1,
          PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlaceAnd (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlaceXor (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_InPlaceOr (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PyNumber_Long (PyObject *o)
     `Return value: New reference.'

     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 函式: PyObject* PyNumber_Float (PyObject *o)
     `Return value: New reference.'

     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 函式: PyObject* PyNumber_Index (PyObject *o)
     `Return value: New reference.'  Returns the `o' converted to a
     Python int on success or ‘NULL’ with a *note TypeError: 193.
     exception raised on failure.

 -- C 函式: PyObject* PyNumber_ToBase (PyObject *n, int base)
     `Return value: New reference.'  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(): 3ce9. first.

 -- C 函式: Py_ssize_t PyNumber_AsSsize_t (PyObject *o, PyObject *exc)

     Returns `o' converted to a Py_ssize_t 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 Py_ssize_t value would raise an *note OverflowError: 965, then
     the `exc' argument is the type of exception that will be raised
     (usually *note IndexError: e7a. or *note OverflowError: 965.).  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)

     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: Sequence Protocol,  Next: Mapping Protocol,  Prev: Number Protocol,  Up: 抽象物件層

7.7.3 Sequence Protocol
-----------------------

 -- C 函式: int PySequence_Check (PyObject *o)

     Return ‘1’ if the object provides sequence protocol, and ‘0’
     otherwise.  Note that it returns ‘1’ for Python classes with a
     *note __getitem__(): 27d. method unless they are *note dict: 1b9.
     subclasses since in general case it is impossible to determine what
     the type of keys it supports.  This function always succeeds.

 -- C 函式: Py_ssize_t PySequence_Size (PyObject *o)
 -- C 函式: Py_ssize_t PySequence_Length (PyObject *o)

     Returns the number of objects in sequence `o' on success, and ‘-1’
     on failure.  This is equivalent to the Python expression ‘len(o)’.

 -- C 函式: PyObject* PySequence_Concat (PyObject *o1, PyObject *o2)
     `Return value: New reference.'  Return the concatenation of `o1'
     and `o2' on success, and ‘NULL’ on failure.  This is the equivalent
     of the Python expression ‘o1 + o2’.

 -- C 函式: PyObject* PySequence_Repeat (PyObject *o, Py_ssize_t count)
     `Return value: New reference.'  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 函式: PyObject* PySequence_InPlaceConcat (PyObject *o1,
          PyObject *o2)
     `Return value: New reference.'  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 函式: PyObject* PySequence_InPlaceRepeat (PyObject *o,
          Py_ssize_t count)
     `Return value: New reference.'  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 函式: PyObject* PySequence_GetItem (PyObject *o, Py_ssize_t i)
     `Return value: New reference.'  Return the `i'th element of `o', or
     ‘NULL’ on failure.  This is the equivalent of the Python expression
     ‘o[i]’.

 -- C 函式: PyObject* PySequence_GetSlice (PyObject *o, Py_ssize_t i1,
          Py_ssize_t i2)
     `Return value: New reference.'  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)

     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, however this feature is
     deprecated in favour of using *note PySequence_DelItem(): 1055.

 -- C 函式: int PySequence_DelItem (PyObject *o, Py_ssize_t i)

     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)

     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)

     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 函式: Py_ssize_t PySequence_Count (PyObject *o, PyObject *value)

     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)

     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 函式: Py_ssize_t PySequence_Index (PyObject *o, PyObject *value)

     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 函式: PyObject* PySequence_List (PyObject *o)
     `Return value: New reference.'  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 函式: PyObject* PySequence_Tuple (PyObject *o)
     `Return value: New reference.'

     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 函式: PyObject* PySequence_Fast (PyObject *o, const char *m)
     `Return value: New reference.'  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: 193. 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: 3c4e. or a *note PyListObject: 3cfd.
     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 函式: Py_ssize_t PySequence_Fast_GET_SIZE (PyObject *o)

     Returns the length of `o', assuming that `o' was returned by *note
     PySequence_Fast(): 3cfc. and that `o' is not ‘NULL’.  The size can
     also be gotten by calling *note PySequence_Size(): 1052. on `o',
     but *note PySequence_Fast_GET_SIZE(): 3cfe. is faster because it
     can assume `o' is a list or tuple.

 -- C 函式: PyObject* PySequence_Fast_GET_ITEM (PyObject *o,
          Py_ssize_t i)
     `Return value: Borrowed reference.'  Return the `i'th element of
     `o', assuming that `o' was returned by *note PySequence_Fast():
     3cfc, `o' is not ‘NULL’, and that `i' is within bounds.

 -- C 函式: PyObject** PySequence_Fast_ITEMS (PyObject *o)

     Return the underlying array of PyObject pointers.  Assumes that `o'
     was returned by *note PySequence_Fast(): 3cfc. 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 函式: PyObject* PySequence_ITEM (PyObject *o, Py_ssize_t i)
     `Return value: New reference.'  Return the `i'th element of `o' or
     ‘NULL’ on failure.  Faster form of *note PySequence_GetItem():
     1053. but without checking that *note PySequence_Check(): 3cee. on
     `o' is true and without adjustment for negative indices.


File: python.info,  Node: Mapping Protocol,  Next: Iterator Protocol,  Prev: Sequence Protocol,  Up: 抽象物件層

7.7.4 Mapping Protocol
----------------------

See also *note PyObject_GetItem(): 3bac, *note PyObject_SetItem(): 3baa.
and *note PyObject_DelItem(): 3cc6.

 -- C 函式: int PyMapping_Check (PyObject *o)

     Return ‘1’ if the object provides mapping protocol or supports
     slicing, and ‘0’ otherwise.  Note that it returns ‘1’ for Python
     classes with a *note __getitem__(): 27d. method since in general
     case it is impossible to determine what type of keys it supports.
     This function always succeeds.

 -- C 函式: Py_ssize_t PyMapping_Size (PyObject *o)
 -- C 函式: Py_ssize_t PyMapping_Length (PyObject *o)

     Returns the number of keys in object `o' on success, and ‘-1’ on
     failure.  This is equivalent to the Python expression ‘len(o)’.

 -- C 函式: PyObject* PyMapping_GetItemString (PyObject *o, const
          char *key)
     `Return value: New reference.'  Return element of `o' corresponding
     to the string `key' or ‘NULL’ on failure.  This is the equivalent
     of the Python expression ‘o[key]’.  See also *note
     PyObject_GetItem(): 3bac.

 -- C 函式: int PyMapping_SetItemString (PyObject *o, const char *key,
          PyObject *v)

     Map the string `key' to the value `v' in object `o'.  Returns ‘-1’
     on failure.  This is the equivalent of the Python statement ‘o[key]
     = v’.  See also *note PyObject_SetItem(): 3baa.  This function
     `does not' steal a reference to `v'.

 -- C 函式: int PyMapping_DelItem (PyObject *o, PyObject *key)

     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]’.  This is an alias of *note PyObject_DelItem(): 3cc6.

 -- C 函式: int PyMapping_DelItemString (PyObject *o, const char *key)

     Remove the mapping for the string `key' from the object `o'.
     Return ‘-1’ on failure.  This is equivalent to the Python statement
     ‘del o[key]’.

 -- C 函式: int PyMapping_HasKey (PyObject *o, PyObject *key)

     Return ‘1’ if the mapping object has the key `key' and ‘0’
     otherwise.  This is equivalent to the Python expression ‘key in o’.
     This function always succeeds.

     Note that exceptions which occur while calling the *note
     __getitem__(): 27d. method will get suppressed.  To get error
     reporting use *note PyObject_GetItem(): 3bac. instead.

 -- C 函式: int PyMapping_HasKeyString (PyObject *o, const char *key)

     Return ‘1’ if the mapping object has the key `key' and ‘0’
     otherwise.  This is equivalent to the Python expression ‘key in o’.
     This function always succeeds.

     Note that exceptions which occur while calling the *note
     __getitem__(): 27d. method and creating a temporary string object
     will get suppressed.  To get error reporting use *note
     PyMapping_GetItemString(): 3d07. instead.

 -- C 函式: PyObject* PyMapping_Keys (PyObject *o)
     `Return value: New reference.'  On success, return a list of the
     keys in object `o'.  On failure, return ‘NULL’.

     3.7 版更變: Previously, the function returned a list or a tuple.

 -- C 函式: PyObject* PyMapping_Values (PyObject *o)
     `Return value: New reference.'  On success, return a list of the
     values in object `o'.  On failure, return ‘NULL’.

     3.7 版更變: Previously, the function returned a list or a tuple.

 -- C 函式: PyObject* PyMapping_Items (PyObject *o)
     `Return value: New reference.'  On success, return a list of the
     items in object `o', where each item is a tuple containing a
     key-value pair.  On failure, return ‘NULL’.

     3.7 版更變: Previously, the function returned a list or a tuple.


File: python.info,  Node: Iterator Protocol,  Next: Buffer Protocol,  Prev: Mapping Protocol,  Up: 抽象物件層

7.7.5 Iterator Protocol
-----------------------

There are two functions specifically for working with iterators.

 -- C 函式: int PyIter_Check (PyObject *o)

     Return true if the object `o' supports the iterator protocol.

 -- C 函式: PyObject* PyIter_Next (PyObject *o)
     `Return value: New reference.'  Return the next value from the
     iteration `o'.  The object must be an iterator (it is up to the
     caller to check this).  If there are no remaining values, returns
     ‘NULL’ with no exception set.  If an error occurs while retrieving
     the item, returns ‘NULL’ and passes along the exception.

To write a loop which iterates over an iterator, the C code should look
something like this:

     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 */
     }


File: python.info,  Node: Buffer Protocol,  Next: Old Buffer Protocol,  Prev: Iterator Protocol,  Up: 抽象物件層

7.7.6 Buffer Protocol
---------------------

Certain objects available in Python wrap access to an underlying memory
array or `buffer'.  Such objects include the built-in *note bytes: 336.
and *note bytearray: 337, and some extension types like *note
array.array: 456.  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: 15ec.  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: 3d13.;

   - 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: 336. and *note bytearray: 337.
expose their underlying buffer in byte-oriented form.  Other forms are
possible; for example, the elements exposed by an *note array.array:
456. can be multi-byte values.

An example consumer of the buffer interface is the *note write(): 58e.
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(): 1ff9. 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(): d2a. with the right parameters;

   * call *note PyArg_ParseTuple(): 26b. (or one of its siblings) with
     one of the ‘y*’, ‘w*’ or ‘s*’ *note format codes: 2d1.

In both cases, *note PyBuffer_Release(): d59. 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.6.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: 4bf. 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: 3d16. object can
be created.

For short instructions how to write an exporting object, see *note
Buffer Object Structures: 3d13.  For obtaining a buffer, see *note
PyObject_GetBuffer(): d2a.

 -- C 類型: Py_buffer

      -- 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: 3d18. the value may
          point to the end of the memory block.

          For *note contiguous: 16ba. arrays, the value points to the
          beginning of the memory block.

      -- C 成員函數: void *obj

          A new reference to the exporting object.  The reference is
          owned by the consumer and automatically decremented and set to
          ‘NULL’ by *note PyBuffer_Release(): d59.  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(): 3d1a. or *note
          PyBuffer_FillInfo(): 3d1b. this field is ‘NULL’.  In general,
          exporting objects MUST NOT use this scheme.

      -- C 成員函數: Py_ssize_t 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: 3d1d. or *note PyBUF_WRITABLE: 3d1e.

      -- C 成員函數: int readonly

          An indicator of whether the buffer is read-only.  This field
          is controlled by the *note PyBUF_WRITABLE: 3d1e. flag.

      -- C 成員函數: Py_ssize_t itemsize

          Item size in bytes of a single element.  Same as the value of
          *note struct.calcsize(): 1815. called on non-‘NULL’ *note
          format: 3d21. values.

          Important exception: If a consumer requests a buffer without
          the *note PyBUF_FORMAT: 3d22. flag, *note format: 3d21. will
          be set to ‘NULL’, but *note itemsize: 3d20. still has the
          value for the original format.

          If *note shape: 3d23. is present, the equality ‘product(shape)
          * itemsize == len’ still holds and the consumer can use *note
          itemsize: 3d20. to navigate the buffer.

          If *note shape: 3d23. is ‘NULL’ as a result of a *note
          PyBUF_SIMPLE: 3d1d. or a *note PyBUF_WRITABLE: 3d1e. request,
          the consumer must disregard *note itemsize: 3d20. and assume
          ‘itemsize == 1’.

      -- C 成員函數: const char *format

          A `NUL' terminated string in *note struct: f9. 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: 3d22.
          flag.

      -- C 成員函數: int ndim

          The number of dimensions the memory represents as an
          n-dimensional array.  If it is ‘0’, *note buf: 3d17. points to
          a single item representing a scalar.  In this case, *note
          shape: 3d23, *note strides: 3d18. and *note suboffsets: 3d25.
          MUST be ‘NULL’.

          The macro ‘PyBUF_MAX_NDIM’ limits the maximum number of
          dimensions to 64.  Exporters MUST respect this limit,
          consumers of multi-dimensional buffers SHOULD be able to
          handle up to ‘PyBUF_MAX_NDIM’ dimensions.

      -- C 成員函數: Py_ssize_t *shape

          An array of ‘Py_ssize_t’ of length *note ndim: 3d24.
          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: 3d1c.

          Shape values are restricted to ‘shape[n] >= 0’.  The case
          ‘shape[n] == 0’ requires special attention.  See *note complex
          arrays: 3d26. for further information.

          The shape array is read-only for the consumer.

      -- C 成員函數: Py_ssize_t *strides

          An array of ‘Py_ssize_t’ of length *note ndim: 3d24. 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: 3d26.
          for further information.

          The strides array is read-only for the consumer.

      -- C 成員函數: Py_ssize_t *suboffsets

          An array of ‘Py_ssize_t’ of length *note ndim: 3d24.  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: 3d26. 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.


File: python.info,  Node: Buffer request types,  Next: Complex arrays,  Prev: Buffer structure,  Up: Buffer Protocol

7.7.6.2 Buffer request types
............................

Buffers are usually obtained by sending a buffer request to an exporting
object via *note PyObject_GetBuffer(): d2a.  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: b20. 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.6.3 request-independent fields
..................................

The following fields are not influenced by `flags' and must always be
filled in with the correct values: *note obj: 3d19, *note buf: 3d17,
*note len: 3d1c, *note itemsize: 3d20, *note ndim: 3d24.


File: python.info,  Node: readonly format,  Next: shape strides suboffsets,  Prev: request-independent fields,  Up: Buffer request types

7.7.6.4 readonly, format
........................

      -- C 巨集: PyBUF_WRITABLE

          Controls the *note readonly: 3d1f. 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: 3d21. field.  If set, this field
          MUST be filled in correctly.  Otherwise, this field MUST be
          ‘NULL’.

*note PyBUF_WRITABLE: 3d1e. can be |’d to any of the flags in the next
section.  Since *note PyBUF_SIMPLE: 3d1d. is defined as 0, *note
PyBUF_WRITABLE: 3d1e. can be used as a stand-alone flag to request a
simple writable buffer.

*note PyBUF_FORMAT: 3d22. can be |’d to any of the flags except *note
PyBUF_SIMPLE: 3d1d.  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.6.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.6.6 contiguity requests
...........................

C or Fortran *note contiguity: 16ba. 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 or F
                                                                                   
                                                                                   
*note PyBUF_ND: 3d2f.                   yes         NULL          NULL             C
                                                                                   


File: python.info,  Node: compound requests,  Prev: contiguity requests,  Up: Buffer request types

7.7.6.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(): 3d35. 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 or 0         yes
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_RECORDS           yes         yes           NULL             U            0              yes
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_RECORDS_RO        yes         yes           NULL             U            1 or 0         yes
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_STRIDED           yes         yes           NULL             U            0              NULL
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_STRIDED_RO        yes         yes           NULL             U            1 or 0         NULL
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_CONTIG            yes         NULL          NULL             C            0              NULL
                                                                                                           
                                                                                                           
 -- C 巨集: PyBUF_CONTIG_RO         yes         NULL          NULL             C            1 or 0         NULL
                                                                                                           


File: python.info,  Node: Complex arrays,  Next: Buffer-related functions,  Prev: Buffer request types,  Up: Buffer Protocol

7.7.6.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.6.9 NumPy-style: shape and strides
......................................

The logical structure of NumPy-style arrays is defined by *note
itemsize: 3d20, *note ndim: 3d24, *note shape: 3d23. and *note strides:
3d18.

If ‘ndim == 0’, the memory location pointed to by *note buf: 3d17. is
interpreted as a scalar of size *note itemsize: 3d20.  In that case,
both *note shape: 3d23. and *note strides: 3d18. are ‘NULL’.

If *note strides: 3d18. 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: 3d17. 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.6.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: 3d17, 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.6.11 Buffer-related functions
.................................

 -- C 函式: int PyObject_CheckBuffer (PyObject *obj)

     Return ‘1’ if `obj' supports the buffer interface otherwise ‘0’.
     When ‘1’ is returned, it doesn’t guarantee that *note
     PyObject_GetBuffer(): d2a. will succeed.  This function always
     succeeds.

 -- C 函式: int PyObject_GetBuffer (PyObject *exporter, Py_buffer *view,
          int flags)

     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 ‘PyExc_BufferError’, 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: 3d13.).

     Successful calls to *note PyObject_GetBuffer(): d2a. must be paired
     with calls to *note PyBuffer_Release(): d59, similar to ‘malloc()’
     and ‘free()’.  Thus, after the consumer is done with the buffer,
     *note PyBuffer_Release(): d59. must be called exactly once.

 -- C 函式: void PyBuffer_Release (Py_buffer *view)

     Release the buffer `view' and decrement the reference count for
     ‘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(): d2a.

 -- C 函式: Py_ssize_t PyBuffer_SizeFromFormat (const char *)

     Return the implied *note itemsize: 3d20. from *note format: 3d21.
     This function is not yet implemented.

 -- C 函式: int PyBuffer_IsContiguous (Py_buffer *view, char order)

     Return ‘1’ if the memory defined by the `view' is C-style (`order'
     is ‘'C'’) or Fortran-style (`order' is ‘'F'’) *note contiguous:
     16ba. or either one (`order' is ‘'A'’).  Return ‘0’ otherwise.
     This function always succeeds.

 -- C 函式: void* PyBuffer_GetPointer (Py_buffer *view,
          Py_ssize_t *indices)

     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 (Py_buffer *view, void *buf,
          Py_ssize_t len, char fort)

     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, Py_buffer *src,
          Py_ssize_t len, char order)

     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 函式: void PyBuffer_FillContiguousStrides (int ndims,
          Py_ssize_t *shape, Py_ssize_t *strides, int itemsize,
          char order)

     Fill the `strides' array with byte-strides of a *note contiguous:
     16ba. (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)

     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: 3d1e. is set in
     `flags'.

     On success, set ‘view->obj’ to a new reference to `exporter' and
     return 0.  Otherwise, raise ‘PyExc_BufferError’, set ‘view->obj’ to
     ‘NULL’ and return ‘-1’;

     If this function is used as part of a *note getbufferproc: 3d13,
     `exporter' MUST be set to the exporting object and `flags' must be
     passed unmodified.  Otherwise, `exporter' MUST be ‘NULL’.


File: python.info,  Node: Old Buffer Protocol,  Prev: Buffer Protocol,  Up: 抽象物件層

7.7.7 Old Buffer Protocol
-------------------------

3.0 版後已棄用.

These functions were part of the "old buffer protocol" API in Python 2.
In Python 3, this protocol doesn’t exist anymore but the functions are
still exposed to ease porting 2.x code.  They act as a compatibility
wrapper around the *note new buffer protocol: 15ec, but they don’t give
you control over the lifetime of the resources acquired when a buffer is
exported.

Therefore, it is recommended that you call *note PyObject_GetBuffer():
d2a. (or the ‘y*’ or ‘w*’ *note format codes: 2d1. with the *note
PyArg_ParseTuple(): 26b. family of functions) to get a buffer view over
an object, and *note PyBuffer_Release(): d59. when the buffer view can
be released.

 -- C 函式: int PyObject_AsCharBuffer (PyObject *obj, const
          char **buffer, Py_ssize_t *buffer_len)

     Returns a pointer to a read-only memory location usable as
     character-based input.  The `obj' argument must support the
     single-segment character buffer interface.  On success, returns
     ‘0’, sets `buffer' to the memory location and `buffer_len' to the
     buffer length.  Returns ‘-1’ and sets a *note TypeError: 193. on
     error.

 -- C 函式: int PyObject_AsReadBuffer (PyObject *obj, const
          void **buffer, Py_ssize_t *buffer_len)

     Returns a pointer to a read-only memory location containing
     arbitrary data.  The `obj' argument must support the single-segment
     readable buffer interface.  On success, returns ‘0’, sets `buffer'
     to the memory location and `buffer_len' to the buffer length.
     Returns ‘-1’ and sets a *note TypeError: 193. on error.

 -- C 函式: int PyObject_CheckReadBuffer (PyObject *o)

     Returns ‘1’ if `o' supports the single-segment readable buffer
     interface.  Otherwise returns ‘0’.  This function always succeeds.

     Note that this function tries to get and release a buffer, and
     exceptions which occur while calling corresponding functions will
     get suppressed.  To get error reporting use *note
     PyObject_GetBuffer(): d2a. instead.

 -- C 函式: int PyObject_AsWriteBuffer (PyObject *obj, void **buffer,
          Py_ssize_t *buffer_len)

     Returns a pointer to a writable memory location.  The `obj'
     argument must support the single-segment, character buffer
     interface.  On success, returns ‘0’, sets `buffer' to the memory
     location and `buffer_len' to the buffer length.  Returns ‘-1’ and
     sets a *note TypeError: 193. on error.


File: python.info,  Node: Concrete Objects Layer,  Next: Initialization Finalization and Threads,  Prev: 抽象物件層,  Up: Python / C API 參考手冊

7.8 Concrete Objects Layer
==========================

The functions in this chapter are specific to certain Python object
types.  Passing them an object of the wrong type is not a good idea; if
you receive an object from a Python program and you are not sure that it
has the right type, you must perform a type check first; for example, to
check that an object is a dictionary, use *note PyDict_Check(): 3d50.
The chapter is structured like the "family tree" of Python object types.

     警告: While the functions described in this chapter carefully check
     the type of the objects which are passed in, many of them do not
     check for ‘NULL’ being passed instead of a valid object.  Allowing
     ‘NULL’ to be passed in can cause memory access violations and
     immediate termination of the interpreter.

* Menu:

* Fundamental Objects::
* Numeric Objects::
* Sequence Objects::
* Container Objects::
* 函式物件: 函式物件<2>.
* Other Objects::


File: python.info,  Node: Fundamental Objects,  Next: Numeric Objects,  Up: Concrete Objects Layer

7.8.1 Fundamental Objects
-------------------------

This section describes Python type objects and the singleton object
‘None’.

* Menu:

* Type Objects: Type Objects<2>.
* The None Object::


File: python.info,  Node: Type Objects<2>,  Next: The None Object,  Up: Fundamental Objects

7.8.1.1 Type Objects
....................

 -- C 類型: PyTypeObject

     The C structure of the objects used to describe built-in types.

 -- C 變數: PyObject* PyType_Type

     This is the type object for type objects; it is the same object as
     *note type: 60d. in the Python layer.

 -- C 函式: int PyType_Check (PyObject *o)

     Return true if the object `o' is a type object, including instances
     of types derived from the standard type object.  Return false in
     all other cases.

 -- C 函式: int PyType_CheckExact (PyObject *o)

     Return true if the object `o' is a type object, but not a subtype
     of the standard type object.  Return false in all other cases.

 -- C 函式: unsigned int PyType_ClearCache ()

     Clear the internal lookup cache.  Return the current version tag.

 -- C 函式: unsigned long PyType_GetFlags (PyTypeObject* type)

     Return the *note tp_flags: 3d5b. 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: 3d5b. itself is not part of the limited
     API.

     3.2 版新加入.

     3.4 版更變: The return type is now ‘unsigned long’ rather than
     ‘long’.

 -- C 函式: void PyType_Modified (PyTypeObject *type)

     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_HasFeature (PyTypeObject *o, int feature)

     Return true 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: 3b48.

 -- C 函式: int PyType_IsSubtype (PyTypeObject *a, PyTypeObject *b)

     Return true if `a' is a subtype of `b'.

     This function only checks for actual subtypes, which means that
     *note __subclasscheck__(): 1456. is not called on `b'.  Call *note
     PyObject_IsSubclass(): 7a3. to do the same check that *note
     issubclass(): 455. would do.

 -- C 函式: PyObject* PyType_GenericAlloc (PyTypeObject *type,
          Py_ssize_t nitems)
     `Return value: New reference.'  Generic handler for the *note
     tp_alloc: 3b3b. 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 函式: PyObject* PyType_GenericNew (PyTypeObject *type,
          PyObject *args, PyObject *kwds)
     `Return value: New reference.'  Generic handler for the *note
     tp_new: 3b36. slot of a type object.  Create a new instance using
     the type’s *note tp_alloc: 3b3b. slot.

 -- C 函式: int PyType_Ready (PyTypeObject *type)

     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.

 -- C 函式: void* PyType_GetSlot (PyTypeObject *type, int slot)

     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 ‘PyType_Slot.slot’ for possible values of the `slot' argument.

     An exception is raised if `type' is not a heap type.

     3.4 版新加入.

* Menu:

* Creating Heap-Allocated Types::


File: python.info,  Node: Creating Heap-Allocated Types,  Up: Type Objects<2>

7.8.1.2 Creating Heap-Allocated Types
.....................................

The following functions and structs are used to create *note heap types:
3d61.

 -- C 函式: PyObject* PyType_FromSpecWithBases (PyType_Spec *spec,
          PyObject *bases)
     `Return value: New reference.'  Creates and returns a heap type
     object from the `spec' (*note Py_TPFLAGS_HEAPTYPE: 3d63.).

     If `bases' is a tuple, the created heap type contains all types
     contained in it as base types.

     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: 2b1.

     This function calls *note PyType_Ready(): 3b3c. on the new type.

     3.3 版新加入.

 -- C 函式: PyObject* PyType_FromSpec (PyType_Spec *spec)
     `Return value: New reference.'  Equivalent to
     ‘PyType_FromSpecWithBases(spec, NULL)’.

 -- C 類型: PyType_Spec

     Structure defining a type’s behavior.

      -- C 成員函數: const char* PyType_Spec.name

          Name of the type, used to set *note PyTypeObject.tp_name:
          3b55.

      -- C 成員函數: int PyType_Spec.basicsize

      -- C 成員函數: int PyType_Spec.itemsize

          Size of the instance in bytes, used to set *note
          PyTypeObject.tp_basicsize: 3b33. and *note
          PyTypeObject.tp_itemsize: 3b32.

      -- C 成員函數: int PyType_Spec.flags

          Type flags, used to set *note PyTypeObject.tp_flags: 3d5b.

          If the ‘Py_TPFLAGS_HEAPTYPE’ flag is not set, *note
          PyType_FromSpecWithBases(): 3d62. sets it automatically.

      -- C 成員函數: PyType_Slot *PyType_Spec.slots

          Array of *note PyType_Slot: 3d6a. structures.  Terminated by
          the special slot value ‘{0, NULL}’.

 -- C 類型: PyType_Slot

     Structure defining optional functionality of a type, containing a
     slot ID and a value pointer.

      -- C 成員函數: int PyType_Slot.slot

          A slot ID.

          Slot IDs are named like the field names of the structures
          *note PyTypeObject: 2d7, *note PyNumberMethods: d86, *note
          PySequenceMethods: 3b63, *note PyMappingMethods: 3b64. and
          *note PyAsyncMethods: 3d6c. with an added ‘Py_’ prefix.  For
          example, use:

             * ‘Py_tp_dealloc’ to set *note PyTypeObject.tp_dealloc:
               3b39.

             * ‘Py_nb_add’ to set *note PyNumberMethods.nb_add: 3d6d.

             * ‘Py_sq_length’ to set *note PySequenceMethods.sq_length:
               3d6e.

          The following fields cannot be set using *note PyType_Spec:
          3d64. and *note PyType_Slot: 3d6a.:

             * *note tp_dict: 3d6f.

             * *note tp_mro: 3d70.

             * *note tp_cache: 3d71.

             * *note tp_subclasses: 3d72.

             * *note tp_weaklist: 3d73.

             * ‘tp_print’

             * *note tp_weaklistoffset: 3b68.

             * *note tp_dictoffset: 3d74.

             * *note bf_getbuffer: 3d75.

             * *note bf_releasebuffer: 3c76.

          Setting ‘Py_tp_bases’ or ‘Py_tp_base’ may be problematic on
          some platforms.  To avoid issues, use the `bases' argument of
          ‘PyType_FromSpecWithBases()’ instead.

      -- C 成員函數: void *PyType_Slot.pfunc

          The desired value of the slot.  In most cases, this is a
          pointer to a function.

          May not be ‘NULL’.


File: python.info,  Node: The None Object,  Prev: Type Objects<2>,  Up: Fundamental Objects

7.8.1.3 The ‘None’ Object
.........................

Note that the *note PyTypeObject: 2d7. 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 變數: PyObject* Py_None

     The Python ‘None’ object, denoting lack of value.  This object has
     no methods.  It needs to be treated just like any other object with
     respect to reference counts.

 -- C 巨集: Py_RETURN_NONE

     Properly handle returning *note Py_None: 3afe. from within a C
     function (that is, increment the reference count of ‘None’ and
     return it.)


File: python.info,  Node: Numeric Objects,  Next: Sequence Objects,  Prev: Fundamental Objects,  Up: Concrete Objects Layer

7.8.2 Numeric Objects
---------------------

* Menu:

* 整數物件::
* 布林物件::
* 浮點數（Floating Point）物件::
* Complex Number Objects::


File: python.info,  Node: 整數物件,  Next: 布林物件,  Up: Numeric Objects

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(): 3af9. to
disambiguate.

 -- C 類型: PyLongObject

     This subtype of *note PyObject: 4bf. represents a Python integer
     object.

 -- C 變數: PyTypeObject PyLong_Type

     This instance of *note PyTypeObject: 2d7. represents the Python
     integer type.  This is the same object as *note int: 185. in the
     Python layer.

 -- C 函式: int PyLong_Check (PyObject *p)

     Return true if its argument is a *note PyLongObject: 3d7f. or a
     subtype of *note PyLongObject: 3d7f.

 -- C 函式: int PyLong_CheckExact (PyObject *p)

     Return true if its argument is a *note PyLongObject: 3d7f, but not
     a subtype of *note PyLongObject: 3d7f.

 -- C 函式: PyObject* PyLong_FromLong (long v)
     `Return value: New reference.'  Return a new *note PyLongObject:
     3d7f. 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.  So it should be possible to change the value of ‘1’.  I
     suspect the behaviour of Python in this case is undefined.  :-)

 -- C 函式: PyObject* PyLong_FromUnsignedLong (unsigned long v)
     `Return value: New reference.'  Return a new *note PyLongObject:
     3d7f. object from a C ‘unsigned long’, or ‘NULL’ on failure.

 -- C 函式: PyObject* PyLong_FromSsize_t (Py_ssize_t v)
     `Return value: New reference.'  Return a new *note PyLongObject:
     3d7f. object from a C ‘Py_ssize_t’, or ‘NULL’ on failure.

 -- C 函式: PyObject* PyLong_FromSize_t (size_t v)
     `Return value: New reference.'  Return a new *note PyLongObject:
     3d7f. object from a C ‘size_t’, or ‘NULL’ on failure.

 -- C 函式: PyObject* PyLong_FromLongLong (long long v)
     `Return value: New reference.'  Return a new *note PyLongObject:
     3d7f. object from a C ‘long long’, or ‘NULL’ on failure.

 -- C 函式: PyObject* PyLong_FromUnsignedLongLong (unsigned long long v)
     `Return value: New reference.'  Return a new *note PyLongObject:
     3d7f. object from a C ‘unsigned long long’, or ‘NULL’ on failure.

 -- C 函式: PyObject* PyLong_FromDouble (double v)
     `Return value: New reference.'  Return a new *note PyLongObject:
     3d7f. object from the integer part of `v', or ‘NULL’ on failure.

 -- C 函式: PyObject* PyLong_FromString (const char *str, char **pend,
          int base)
     `Return value: New reference.'  Return a new *note PyLongObject:
     3d7f. based on the string value in `str', which is interpreted
     according to the radix in `base'.  If `pend' is non-‘NULL’, `*pend'
     will point to the first character in `str' which follows the
     representation of the number.  If `base' is ‘0’, `str' is
     interpreted using the *note Integer literals: 1407. definition; in
     this case, leading zeros in a non-zero decimal number raises a
     *note ValueError: 1fc.  If `base' is not ‘0’, it must be between
     ‘2’ and ‘36’, inclusive.  Leading spaces and single underscores
     after a base specifier and between digits are ignored.  If there
     are no digits, *note ValueError: 1fc. will be raised.

 -- C 函式: PyObject* PyLong_FromUnicode (Py_UNICODE *u,
          Py_ssize_t length, int base)
     `Return value: New reference.'  Convert a sequence of Unicode
     digits to a Python integer value.

     Deprecated since version 3.3, will be removed in version 3.10: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyLong_FromUnicodeObject(): 3d8b.

 -- C 函式: PyObject* PyLong_FromUnicodeObject (PyObject *u, int base)
     `Return value: New reference.'  Convert a sequence of Unicode
     digits in the string `u' to a Python integer value.

     3.3 版新加入.

 -- C 函式: PyObject* PyLong_FromVoidPtr (void *p)
     `Return value: New reference.'  Create a Python integer from the
     pointer `p'.  The pointer value can be retrieved from the resulting
     value using *note PyLong_AsVoidPtr(): 3d8d.

 -- C 函式: long PyLong_AsLong (PyObject *obj)

     Return a C ‘long’ representation of `obj'.  If `obj' is not an
     instance of *note PyLongObject: 3d7f, first call its *note
     __index__(): 18b. or *note __int__(): 18c. method (if present) to
     convert it to a *note PyLongObject: 3d7f.

     Raise *note OverflowError: 965. if the value of `obj' is out of
     range for a ‘long’.

     Returns ‘-1’ on error.  Use *note PyErr_Occurred(): 3af9. to
     disambiguate.

     3.8 版更變: Use *note __index__(): 18b. if available.

     3.8 版後已棄用: Using *note __int__(): 18c. is deprecated.

 -- C 函式: long PyLong_AsLongAndOverflow (PyObject *obj, int *overflow)

     Return a C ‘long’ representation of `obj'.  If `obj' is not an
     instance of *note PyLongObject: 3d7f, first call its *note
     __index__(): 18b. or *note __int__(): 18c. method (if present) to
     convert it to a *note PyLongObject: 3d7f.

     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(): 3af9. to
     disambiguate.

     3.8 版更變: Use *note __index__(): 18b. if available.

     3.8 版後已棄用: Using *note __int__(): 18c. is deprecated.

 -- C 函式: long long PyLong_AsLongLong (PyObject *obj)

     Return a C ‘long long’ representation of `obj'.  If `obj' is not an
     instance of *note PyLongObject: 3d7f, first call its *note
     __index__(): 18b. or *note __int__(): 18c. method (if present) to
     convert it to a *note PyLongObject: 3d7f.

     Raise *note OverflowError: 965. if the value of `obj' is out of
     range for a ‘long long’.

     Returns ‘-1’ on error.  Use *note PyErr_Occurred(): 3af9. to
     disambiguate.

     3.8 版更變: Use *note __index__(): 18b. if available.

     3.8 版後已棄用: Using *note __int__(): 18c. is deprecated.

 -- C 函式: long long PyLong_AsLongLongAndOverflow (PyObject *obj,
          int *overflow)

     Return a C ‘long long’ representation of `obj'.  If `obj' is not an
     instance of *note PyLongObject: 3d7f, first call its *note
     __index__(): 18b. or *note __int__(): 18c. method (if present) to
     convert it to a *note PyLongObject: 3d7f.

     If the value of `obj' is greater than ‘PY_LLONG_MAX’ or less than
     ‘PY_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(): 3af9. to
     disambiguate.

     3.2 版新加入.

     3.8 版更變: Use *note __index__(): 18b. if available.

     3.8 版後已棄用: Using *note __int__(): 18c. is deprecated.

 -- C 函式: Py_ssize_t PyLong_AsSsize_t (PyObject *pylong)

     Return a C ‘Py_ssize_t’ representation of `pylong'.  `pylong' must
     be an instance of *note PyLongObject: 3d7f.

     Raise *note OverflowError: 965. if the value of `pylong' is out of
     range for a ‘Py_ssize_t’.

     Returns ‘-1’ on error.  Use *note PyErr_Occurred(): 3af9. to
     disambiguate.

 -- C 函式: unsigned long PyLong_AsUnsignedLong (PyObject *pylong)

     Return a C ‘unsigned long’ representation of `pylong'.  `pylong'
     must be an instance of *note PyLongObject: 3d7f.

     Raise *note OverflowError: 965. if the value of `pylong' is out of
     range for a ‘unsigned long’.

     Returns ‘(unsigned long)-1’ on error.  Use *note PyErr_Occurred():
     3af9. to disambiguate.

 -- C 函式: size_t PyLong_AsSize_t (PyObject *pylong)

     Return a C ‘size_t’ representation of `pylong'.  `pylong' must be
     an instance of *note PyLongObject: 3d7f.

     Raise *note OverflowError: 965. if the value of `pylong' is out of
     range for a ‘size_t’.

     Returns ‘(size_t)-1’ on error.  Use *note PyErr_Occurred(): 3af9.
     to disambiguate.

 -- C 函式: unsigned long long PyLong_AsUnsignedLongLong
          (PyObject *pylong)

     Return a C ‘unsigned long long’ representation of `pylong'.
     `pylong' must be an instance of *note PyLongObject: 3d7f.

     Raise *note OverflowError: 965. 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(): 3af9. to disambiguate.

     3.1 版更變: A negative `pylong' now raises *note OverflowError:
     965, not *note TypeError: 193.

 -- C 函式: unsigned long PyLong_AsUnsignedLongMask (PyObject *obj)

     Return a C ‘unsigned long’ representation of `obj'.  If `obj' is
     not an instance of *note PyLongObject: 3d7f, first call its *note
     __index__(): 18b. or *note __int__(): 18c. method (if present) to
     convert it to a *note PyLongObject: 3d7f.

     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():
     3af9. to disambiguate.

     3.8 版更變: Use *note __index__(): 18b. if available.

     3.8 版後已棄用: Using *note __int__(): 18c. is deprecated.

 -- C 函式: unsigned long long PyLong_AsUnsignedLongLongMask
          (PyObject *obj)

     Return a C ‘unsigned long long’ representation of `obj'.  If `obj'
     is not an instance of *note PyLongObject: 3d7f, first call its
     *note __index__(): 18b. or *note __int__(): 18c. method (if
     present) to convert it to a *note PyLongObject: 3d7f.

     If the value of `obj' is out of range for an ‘unsigned long long’,
     return the reduction of that value modulo ‘PY_ULLONG_MAX + 1’.

     Returns ‘(unsigned long long)-1’ on error.  Use *note
     PyErr_Occurred(): 3af9. to disambiguate.

     3.8 版更變: Use *note __index__(): 18b. if available.

     3.8 版後已棄用: Using *note __int__(): 18c. is deprecated.

 -- C 函式: double PyLong_AsDouble (PyObject *pylong)

     Return a C ‘double’ representation of `pylong'.  `pylong' must be
     an instance of *note PyLongObject: 3d7f.

     Raise *note OverflowError: 965. if the value of `pylong' is out of
     range for a ‘double’.

     Returns ‘-1.0’ on error.  Use *note PyErr_Occurred(): 3af9. to
     disambiguate.

 -- C 函式: void* PyLong_AsVoidPtr (PyObject *pylong)

     Convert a Python integer `pylong' to a C ‘void’ pointer.  If
     `pylong' cannot be converted, an *note OverflowError: 965. will be
     raised.  This is only assured to produce a usable ‘void’ pointer
     for values created with *note PyLong_FromVoidPtr(): 3d8c.

     Returns ‘NULL’ on error.  Use *note PyErr_Occurred(): 3af9. to
     disambiguate.


File: python.info,  Node: 布林物件,  Next: 浮點數（Floating Point）物件,  Prev: 整數物件,  Up: Numeric Objects

7.8.2.2 布林物件
................

Booleans in Python are implemented as a subclass of integers.  There are
only two booleans, ‘Py_False’ and ‘Py_True’.  As such, the normal
creation and deletion functions don’t apply to booleans.  The following
macros are available, however.

 -- C 函式: int PyBool_Check (PyObject *o)

     Return true if `o' is of type ‘PyBool_Type’.

 -- C 變數: PyObject* Py_False

     The Python ‘False’ object.  This object has no methods.  It needs
     to be treated just like any other object with respect to reference
     counts.

 -- C 變數: PyObject* Py_True

     The Python ‘True’ object.  This object has no methods.  It needs to
     be treated just like any other object with respect to reference
     counts.

 -- C 巨集: Py_RETURN_FALSE

     Return ‘Py_False’ from a function, properly incrementing its
     reference count.

 -- C 巨集: Py_RETURN_TRUE

     Return ‘Py_True’ from a function, properly incrementing its
     reference count.

 -- C 函式: PyObject* PyBool_FromLong (long v)
     `Return value: New reference.'  Return a new reference to ‘Py_True’
     or ‘Py_False’ depending on the truth value of `v'.


File: python.info,  Node: 浮點數（Floating Point）物件,  Next: Complex Number Objects,  Prev: 布林物件,  Up: Numeric Objects

7.8.2.3 浮點數（Floating Point）物件
....................................

 -- C 類型: PyFloatObject

     This subtype of *note PyObject: 4bf. represents a Python floating
     point object.

 -- C 變數: PyTypeObject PyFloat_Type

     This instance of *note PyTypeObject: 2d7. represents the Python
     floating point type.  This is the same object as *note float: 188.
     in the Python layer.

 -- C 函式: int PyFloat_Check (PyObject *p)

     Return true if its argument is a *note PyFloatObject: 3d9e. or a
     subtype of *note PyFloatObject: 3d9e.

 -- C 函式: int PyFloat_CheckExact (PyObject *p)

     Return true if its argument is a *note PyFloatObject: 3d9e, but not
     a subtype of *note PyFloatObject: 3d9e.

 -- C 函式: PyObject* PyFloat_FromString (PyObject *str)
     `Return value: New reference.'  Create a *note PyFloatObject: 3d9e.
     object based on the string value in `str', or ‘NULL’ on failure.

 -- C 函式: PyObject* PyFloat_FromDouble (double v)
     `Return value: New reference.'  Create a *note PyFloatObject: 3d9e.
     object from `v', or ‘NULL’ on failure.

 -- C 函式: double PyFloat_AsDouble (PyObject *pyfloat)

     Return a C ‘double’ representation of the contents of `pyfloat'.
     If `pyfloat' is not a Python floating point object but has a *note
     __float__(): 18d. 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__(): 18b.  This method returns
     ‘-1.0’ upon failure, so one should call *note PyErr_Occurred():
     3af9. to check for errors.

     3.8 版更變: Use *note __index__(): 18b. if available.

 -- C 函式: double PyFloat_AS_DOUBLE (PyObject *pyfloat)

     Return a C ‘double’ representation of the contents of `pyfloat',
     but without error checking.

 -- C 函式: PyObject* PyFloat_GetInfo (void)
     `Return value: New reference.'  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 ()

     Return the maximum representable finite float `DBL_MAX' as C
     ‘double’.

 -- C 函式: double PyFloat_GetMin ()

     Return the minimum normalized positive float `DBL_MIN' as C
     ‘double’.

 -- C 函式: int PyFloat_ClearFreeList ()

     Clear the float free list.  Return the number of items that could
     not be freed.


File: python.info,  Node: Complex Number Objects,  Prev: 浮點數（Floating Point）物件,  Up: Numeric Objects

7.8.2.4 Complex Number Objects
..............................

Python’s complex number objects are implemented as two distinct types
when viewed from the C API: one is the Python object exposed to Python
programs, and the other is a C structure which represents the actual
complex number value.  The API provides functions for working with both.

* Menu:

* Complex Numbers as C Structures::
* Complex Numbers as Python Objects::


File: python.info,  Node: Complex Numbers as C Structures,  Next: Complex Numbers as Python Objects,  Up: Complex Number Objects

7.8.2.5 Complex Numbers as C Structures
.......................................

Note that the functions which accept these structures as parameters and
return them as results do so `by value' rather than dereferencing them
through pointers.  This is consistent throughout the API.

 -- C 類型: Py_complex

     The C structure which corresponds to the value portion of a Python
     complex number object.  Most of the functions for dealing with
     complex number objects use structures of this type as input or
     output values, as appropriate.  It is defined as:

          typedef struct {
             double real;
             double imag;
          } Py_complex;

 -- C 函式: Py_complex _Py_c_sum (Py_complex left, Py_complex right)

     Return the sum of two complex numbers, using the C *note
     Py_complex: 3c78. representation.

 -- C 函式: Py_complex _Py_c_diff (Py_complex left, Py_complex right)

     Return the difference between two complex numbers, using the C
     *note Py_complex: 3c78. representation.

 -- C 函式: Py_complex _Py_c_neg (Py_complex complex)

     Return the negation of the complex number `complex', using the C
     *note Py_complex: 3c78. representation.

 -- C 函式: Py_complex _Py_c_prod (Py_complex left, Py_complex right)

     Return the product of two complex numbers, using the C *note
     Py_complex: 3c78. representation.

 -- C 函式: Py_complex _Py_c_quot (Py_complex dividend,
          Py_complex divisor)

     Return the quotient of two complex numbers, using the C *note
     Py_complex: 3c78. representation.

     If `divisor' is null, this method returns zero and sets ‘errno’ to
     ‘EDOM’.

 -- C 函式: Py_complex _Py_c_pow (Py_complex num, Py_complex exp)

     Return the exponentiation of `num' by `exp', using the C *note
     Py_complex: 3c78. representation.

     If `num' is null and `exp' is not a positive real number, this
     method returns zero and sets ‘errno’ to ‘EDOM’.


File: python.info,  Node: Complex Numbers as Python Objects,  Prev: Complex Numbers as C Structures,  Up: Complex Number Objects

7.8.2.6 Complex Numbers as Python Objects
.........................................

 -- C 類型: PyComplexObject

     This subtype of *note PyObject: 4bf. represents a Python complex
     number object.

 -- C 變數: PyTypeObject PyComplex_Type

     This instance of *note PyTypeObject: 2d7. represents the Python
     complex number type.  It is the same object as *note complex: 18a.
     in the Python layer.

 -- C 函式: int PyComplex_Check (PyObject *p)

     Return true if its argument is a *note PyComplexObject: 3db1. or a
     subtype of *note PyComplexObject: 3db1.

 -- C 函式: int PyComplex_CheckExact (PyObject *p)

     Return true if its argument is a *note PyComplexObject: 3db1, but
     not a subtype of *note PyComplexObject: 3db1.

 -- C 函式: PyObject* PyComplex_FromCComplex (Py_complex v)
     `Return value: New reference.'  Create a new Python complex number
     object from a C *note Py_complex: 3c78. value.

 -- C 函式: PyObject* PyComplex_FromDoubles (double real, double imag)
     `Return value: New reference.'  Return a new *note PyComplexObject:
     3db1. object from `real' and `imag'.

 -- C 函式: double PyComplex_RealAsDouble (PyObject *op)

     Return the real part of `op' as a C ‘double’.

 -- C 函式: double PyComplex_ImagAsDouble (PyObject *op)

     Return the imaginary part of `op' as a C ‘double’.

 -- C 函式: Py_complex PyComplex_AsCComplex (PyObject *op)

     Return the *note Py_complex: 3c78. value of the complex number
     `op'.

     If `op' is not a Python complex number object but has a *note
     __complex__(): 18e. 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 *note __float__(): 18d.  If
     ‘__float__()’ is not defined then it falls back to *note
     __index__(): 18b.  Upon failure, this method returns ‘-1.0’ as a
     real value.

     3.8 版更變: Use *note __index__(): 18b. if available.


File: python.info,  Node: Sequence Objects,  Next: Container Objects,  Prev: Numeric Objects,  Up: Concrete Objects Layer

7.8.3 Sequence Objects
----------------------

Generic operations on sequence objects were discussed in the previous
chapter; this section deals with the specific kinds of sequence objects
that are intrinsic to the Python language.

* Menu:

* Bytes Objects: Bytes Objects<2>.
* Byte Array Objects::
* Unicode物件與編碼::
* 元組（Tuple）物件::
* Struct Sequence Objects::
* List（串列）物件::


File: python.info,  Node: Bytes Objects<2>,  Next: Byte Array Objects,  Up: Sequence Objects

7.8.3.1 Bytes Objects
.....................

These functions raise *note TypeError: 193. when expecting a bytes
parameter and are called with a non-bytes parameter.

 -- C 類型: PyBytesObject

     This subtype of *note PyObject: 4bf. represents a Python bytes
     object.

 -- C 變數: PyTypeObject PyBytes_Type

     This instance of *note PyTypeObject: 2d7. represents the Python
     bytes type; it is the same object as *note bytes: 336. 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.

 -- 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.

 -- C 函式: PyObject* PyBytes_FromString (const char *v)
     `Return value: New reference.'  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 函式: PyObject* PyBytes_FromStringAndSize (const char *v,
          Py_ssize_t len)
     `Return value: New reference.'  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 函式: PyObject* PyBytes_FromFormat (const char *format, ...)
     `Return value: New reference.'  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                 Equivalent to ‘printf("%d")’.  (1)
                                                 
                                                 
     ‘%u’                    unsigned int        Equivalent to ‘printf("%u")’.  (2)
                                                 
                                                 
     ‘%ld’                   long                Equivalent to ‘printf("%ld")’.
                                                 (3)
                                                 
                                                 
     ‘%lu’                   unsigned long       Equivalent to ‘printf("%lu")’.
                                                 (4)
                                                 
                                                 
     ‘%zd’                   Py_ssize_t          Equivalent to ‘printf("%zd")’.
                                                 (5)
                                                 
                                                 
     ‘%zu’                   size_t              Equivalent to ‘printf("%zu")’.
                                                 (6)
                                                 
                                                 
     ‘%i’                    int                 Equivalent to ‘printf("%i")’.  (7)
                                                 
                                                 
     ‘%x’                    int                 Equivalent to ‘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 函式: PyObject* PyBytes_FromFormatV (const char *format,
          va_list vargs)
     `Return value: New reference.'  Identical to *note
     PyBytes_FromFormat(): 1010. except that it takes exactly two
     arguments.

 -- C 函式: PyObject* PyBytes_FromObject (PyObject *o)
     `Return value: New reference.'  Return the bytes representation of
     object `o' that implements the buffer protocol.

 -- C 函式: Py_ssize_t PyBytes_Size (PyObject *o)

     Return the length of the bytes in bytes object `o'.

 -- C 函式: Py_ssize_t PyBytes_GET_SIZE (PyObject *o)

     Macro form of *note PyBytes_Size(): 3dc3. but without error
     checking.

 -- C 函式: char* PyBytes_AsString (PyObject *o)

     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(): 3dc5. returns ‘NULL’ and raises *note
     TypeError: 193.

 -- C 函式: char* PyBytes_AS_STRING (PyObject *string)

     Macro form of *note PyBytes_AsString(): 3dc5. but without error
     checking.

 -- C 函式: int PyBytes_AsStringAndSize (PyObject *obj, char **buffer,
          Py_ssize_t *length)

     Return the null-terminated contents of the object `obj' through the
     output variables `buffer' and `length'.

     If `length' is ‘NULL’, the bytes object may not contain embedded
     null bytes; if it does, the function returns ‘-1’ and a *note
     ValueError: 1fc. 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(): 3dc7. returns ‘-1’ and raises *note
     TypeError: 193.

     3.5 版更變: Previously, *note TypeError: 193. was raised when
     embedded null bytes were encountered in the bytes object.

 -- C 函式: void PyBytes_Concat (PyObject **bytes, PyObject *newpart)

     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)

     Create a new bytes object in `*bytes' containing the contents of
     `newpart' appended to `bytes'.  This version decrements the
     reference count of `newpart'.

 -- C 函式: int _PyBytes_Resize (PyObject **bytes, Py_ssize_t newsize)

     A way to resize a bytes object even though it is "immutable".  Only
     use this to build up a brand new bytes object; don’t use this if
     the bytes may already be known in other parts of the code.  It is
     an error to call this function if the refcount on the input bytes
     object is not one.  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: ef1. is
     set, and ‘-1’ is returned.

   ---------- Footnotes ----------

   (1) (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) (1) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (3) (1) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (4) (1) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (5) (1) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (6) (1) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (7) (1) For integer specifiers (d, u, ld, lu, zd, zu, i, x): the
0-conversion flag has effect even when a precision is given.

   (8) (1) 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<2>,  Up: Sequence Objects

7.8.3.2 Byte Array Objects
..........................

 -- C 類型: PyByteArrayObject

     This subtype of *note PyObject: 4bf. represents a Python bytearray
     object.

 -- C 變數: PyTypeObject PyByteArray_Type

     This instance of *note PyTypeObject: 2d7. represents the Python
     bytearray type; it is the same object as *note bytearray: 337. in
     the Python layer.

* Menu:

* Type check macros::
* Direct API functions::
* Macros::


File: python.info,  Node: Type check macros,  Next: Direct API functions,  Up: Byte Array Objects

7.8.3.3 Type check macros
.........................

 -- C 函式: int PyByteArray_Check (PyObject *o)

     Return true if the object `o' is a bytearray object or an instance
     of a subtype of the bytearray type.

 -- C 函式: int PyByteArray_CheckExact (PyObject *o)

     Return true if the object `o' is a bytearray object, but not an
     instance of a subtype of the bytearray type.


File: python.info,  Node: Direct API functions,  Next: Macros,  Prev: Type check macros,  Up: Byte Array Objects

7.8.3.4 Direct API functions
............................

 -- C 函式: PyObject* PyByteArray_FromObject (PyObject *o)
     `Return value: New reference.'  Return a new bytearray object from
     any object, `o', that implements the *note buffer protocol: 15ec.

 -- C 函式: PyObject* PyByteArray_FromStringAndSize (const char *string,
          Py_ssize_t len)
     `Return value: New reference.'  Create a new bytearray object from
     `string' and its length, `len'.  On failure, ‘NULL’ is returned.

 -- C 函式: PyObject* PyByteArray_Concat (PyObject *a, PyObject *b)
     `Return value: New reference.'  Concat bytearrays `a' and `b' and
     return a new bytearray with the result.

 -- C 函式: Py_ssize_t PyByteArray_Size (PyObject *bytearray)

     Return the size of `bytearray' after checking for a ‘NULL’ pointer.

 -- C 函式: char* PyByteArray_AsString (PyObject *bytearray)

     Return the contents of `bytearray' as a char array after checking
     for a ‘NULL’ pointer.  The returned array always has an extra null
     byte appended.

 -- C 函式: int PyByteArray_Resize (PyObject *bytearray, Py_ssize_t len)

     Resize the internal buffer of `bytearray' to `len'.


File: python.info,  Node: Macros,  Prev: Direct API functions,  Up: Byte Array Objects

7.8.3.5 Macros
..............

These macros trade safety for speed and they don’t check pointers.

 -- C 函式: char* PyByteArray_AS_STRING (PyObject *bytearray)

     Macro version of *note PyByteArray_AsString(): 3dd5.

 -- C 函式: Py_ssize_t PyByteArray_GET_SIZE (PyObject *bytearray)

     Macro version of *note PyByteArray_Size(): 3dd4.


File: python.info,  Node: Unicode物件與編碼,  Next: 元組（Tuple）物件,  Prev: Byte Array Objects,  Up: Sequence Objects

7.8.3.6 Unicode物件與編碼
.........................

* Menu:

* Unicode Objects::
* Built-in Codecs::
* Methods and Slot Functions::


File: python.info,  Node: Unicode Objects,  Next: Built-in Codecs,  Up: Unicode物件與編碼

7.8.3.7 Unicode Objects
.......................

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).

*note Py_UNICODE*: af3. and UTF-8 representations are created on demand
and cached in the Unicode object.  The *note Py_UNICODE*: af3.
representation is deprecated and inefficient.

Due to the transition between the old APIs and the new APIs, Unicode
objects can internally be in two states depending on how they were
created:

   * "canonical" Unicode objects are all objects created by a
     non-deprecated Unicode API. They use the most efficient
     representation allowed by the implementation.

   * "legacy" Unicode objects have been created through one of the
     deprecated APIs (typically *note PyUnicode_FromUnicode(): af4.) and
     only bear the *note Py_UNICODE*: af3. representation; you will have
     to call *note PyUnicode_READY(): adb. on them before calling any
     other API.

     備註: The "legacy" Unicode object will be removed in Python 3.12
     with deprecated APIs.  All Unicode objects will be "canonical"
     since then.  See PEP 623(2) for more information.

* Menu:

* Unicode Type::
* Unicode Character Properties::
* Creating and accessing Unicode strings::
* Deprecated Py_UNICODE APIs::
* Locale Encoding::
* File System Encoding::
* wchar_t Support::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0393

   (2) https://www.python.org/dev/peps/pep-0623


File: python.info,  Node: Unicode Type,  Next: Unicode Character Properties,  Up: Unicode Objects

7.8.3.8 Unicode Type
....................

These are the basic Unicode object types used for the Unicode
implementation in Python:

 -- C 類型: Py_UCS4
 -- C 類型: Py_UCS2
 -- C 類型: Py_UCS1

     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:
     ad8.

     3.3 版新加入.

 -- C 類型: 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.

 -- C 類型: PyASCIIObject
 -- C 類型: PyCompactUnicodeObject
 -- C 類型: PyUnicodeObject

     These subtypes of *note PyObject: 4bf. 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: 4bf. pointers.

     3.3 版新加入.

 -- C 變數: PyTypeObject PyUnicode_Type

     This instance of *note PyTypeObject: 2d7. represents the Python
     Unicode type.  It is exposed to Python code as ‘str’.

The following APIs are really C macros and can be used to do fast checks
and to access internal read-only data of Unicode objects:

 -- C 函式: int PyUnicode_Check (PyObject *o)

     Return true if the object `o' is a Unicode object or an instance of
     a Unicode subtype.

 -- C 函式: int PyUnicode_CheckExact (PyObject *o)

     Return true if the object `o' is a Unicode object, but not an
     instance of a subtype.

 -- C 函式: int PyUnicode_READY (PyObject *o)

     Ensure the string object `o' is in the "canonical" representation.
     This is required before using any of the access macros described
     below.

     Returns ‘0’ on success and ‘-1’ with an exception set on failure,
     which in particular happens if memory allocation fails.

     3.3 版新加入.

     Deprecated since version 3.10, will be removed in version 3.12:
     This API will be removed with *note PyUnicode_FromUnicode(): af4.

 -- C 函式: Py_ssize_t PyUnicode_GET_LENGTH (PyObject *o)

     Return the length of the Unicode string, in code points.  `o' has
     to be a Unicode object in the "canonical" representation (not
     checked).

     3.3 版新加入.

 -- C 函式: Py_UCS1* PyUnicode_1BYTE_DATA (PyObject *o)
 -- C 函式: Py_UCS2* PyUnicode_2BYTE_DATA (PyObject *o)
 -- C 函式: Py_UCS4* PyUnicode_4BYTE_DATA (PyObject *o)

     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(): ae3. to select the right macro.
     Make sure *note PyUnicode_READY(): adb. has been called before
     accessing this.

     3.3 版新加入.

 -- C 巨集: PyUnicode_WCHAR_KIND
 -- C 巨集: PyUnicode_1BYTE_KIND
 -- C 巨集: PyUnicode_2BYTE_KIND
 -- C 巨集: PyUnicode_4BYTE_KIND

     Return values of the *note PyUnicode_KIND(): ae3. macro.

     3.3 版新加入.

     Deprecated since version 3.10, will be removed in version 3.12:
     ‘PyUnicode_WCHAR_KIND’ is deprecated.

 -- C 函式: int PyUnicode_KIND (PyObject *o)

     Return one of the PyUnicode kind constants (see above) that
     indicate how many bytes per character this Unicode object uses to
     store its data.  `o' has to be a Unicode object in the "canonical"
     representation (not checked).

     3.3 版新加入.

 -- C 函式: void* PyUnicode_DATA (PyObject *o)

     Return a void pointer to the raw Unicode buffer.  `o' 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(): adf.).  This macro does not do any sanity
     checks and is intended for usage in loops.  The caller should cache
     the `kind' value and `data' pointer as obtained from other macro
     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 函式: Py_UCS4 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(): adf.).  No checks or ready
     calls are performed.

     3.3 版新加入.

 -- C 函式: Py_UCS4 PyUnicode_READ_CHAR (PyObject *o, Py_ssize_t index)

     Read a character from a Unicode object `o', which must be in the
     "canonical" representation.  This is less efficient than *note
     PyUnicode_READ(): ae8. if you do multiple consecutive reads.

     3.3 版新加入.

 -- C 巨集: PyUnicode_MAX_CHAR_VALUE (o)

     Return the maximum code point that is suitable for creating another
     string based on `o', 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_ClearFreeList ()

     Clear the free list.  Return the total number of freed items.

 -- C 函式: Py_ssize_t PyUnicode_GET_SIZE (PyObject *o)

     Return the size of the deprecated *note Py_UNICODE: af3.
     representation, in code units (this includes surrogate pairs as 2
     units).  `o' has to be a Unicode object (not checked).

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style Unicode API, please migrate to using *note
     PyUnicode_GET_LENGTH(): ad1.

 -- C 函式: Py_ssize_t PyUnicode_GET_DATA_SIZE (PyObject *o)

     Return the size of the deprecated *note Py_UNICODE: af3.
     representation in bytes.  `o' has to be a Unicode object (not
     checked).

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style Unicode API, please migrate to using *note
     PyUnicode_GET_LENGTH(): ad1.

 -- C 函式: Py_UNICODE* PyUnicode_AS_UNICODE (PyObject *o)
 -- C 函式: const char* PyUnicode_AS_DATA (PyObject *o)

     Return a pointer to a *note Py_UNICODE: af3. representation of the
     object.  The returned buffer is always terminated with an extra
     null code point.  It may also contain embedded null code points,
     which would cause the string to be truncated when used in most C
     functions.  The ‘AS_DATA’ form casts the pointer to ‘const char *’.
     The `o' argument has to be a Unicode object (not checked).

     3.3 版更變: This macro is now inefficient – because in many cases
     the *note Py_UNICODE: af3. representation does not exist and needs
     to be created – and can fail (return ‘NULL’ with an exception set).
     Try to port the code to use the new ‘PyUnicode_nBYTE_DATA()’ macros
     or use *note PyUnicode_WRITE(): aea. or *note PyUnicode_READ():
     ae8.

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style Unicode API, please migrate to using the
     ‘PyUnicode_nBYTE_DATA()’ family of macros.


File: python.info,  Node: Unicode Character Properties,  Next: Creating and accessing Unicode strings,  Prev: Unicode Type,  Up: Unicode Objects

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_UNICODE ch)

     Return ‘1’ or ‘0’ depending on whether `ch' is a whitespace
     character.

 -- C 函式: int Py_UNICODE_ISLOWER (Py_UNICODE ch)

     Return ‘1’ or ‘0’ depending on whether `ch' is a lowercase
     character.

 -- C 函式: int Py_UNICODE_ISUPPER (Py_UNICODE ch)

     Return ‘1’ or ‘0’ depending on whether `ch' is an uppercase
     character.

 -- C 函式: int Py_UNICODE_ISTITLE (Py_UNICODE ch)

     Return ‘1’ or ‘0’ depending on whether `ch' is a titlecase
     character.

 -- C 函式: int Py_UNICODE_ISLINEBREAK (Py_UNICODE ch)

     Return ‘1’ or ‘0’ depending on whether `ch' is a linebreak
     character.

 -- C 函式: int Py_UNICODE_ISDECIMAL (Py_UNICODE ch)

     Return ‘1’ or ‘0’ depending on whether `ch' is a decimal character.

 -- C 函式: int Py_UNICODE_ISDIGIT (Py_UNICODE ch)

     Return ‘1’ or ‘0’ depending on whether `ch' is a digit character.

 -- C 函式: int Py_UNICODE_ISNUMERIC (Py_UNICODE ch)

     Return ‘1’ or ‘0’ depending on whether `ch' is a numeric character.

 -- C 函式: int Py_UNICODE_ISALPHA (Py_UNICODE ch)

     Return ‘1’ or ‘0’ depending on whether `ch' is an alphabetic
     character.

 -- C 函式: int Py_UNICODE_ISALNUM (Py_UNICODE ch)

     Return ‘1’ or ‘0’ depending on whether `ch' is an alphanumeric
     character.

 -- C 函式: int Py_UNICODE_ISPRINTABLE (Py_UNICODE 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(): 7d1. is invoked on a string.  It has no
     bearing on the handling of strings written to *note sys.stdout:
     313. or *note sys.stderr: 314.)

These APIs can be used for fast direct character conversions:

 -- C 函式: Py_UNICODE Py_UNICODE_TOLOWER (Py_UNICODE ch)

     Return the character `ch' converted to lower case.

     3.3 版後已棄用: This function uses simple case mappings.

 -- C 函式: Py_UNICODE Py_UNICODE_TOUPPER (Py_UNICODE ch)

     Return the character `ch' converted to upper case.

     3.3 版後已棄用: This function uses simple case mappings.

 -- C 函式: Py_UNICODE Py_UNICODE_TOTITLE (Py_UNICODE ch)

     Return the character `ch' converted to title case.

     3.3 版後已棄用: This function uses simple case mappings.

 -- C 函式: int Py_UNICODE_TODECIMAL (Py_UNICODE ch)

     Return the character `ch' converted to a decimal positive integer.
     Return ‘-1’ if this is not possible.  This macro does not raise
     exceptions.

 -- C 函式: int Py_UNICODE_TODIGIT (Py_UNICODE ch)

     Return the character `ch' converted to a single digit integer.
     Return ‘-1’ if this is not possible.  This macro does not raise
     exceptions.

 -- C 函式: double Py_UNICODE_TONUMERIC (Py_UNICODE ch)

     Return the character `ch' converted to a double.  Return ‘-1.0’ if
     this is not possible.  This macro does not raise exceptions.

These APIs can be used to work with surrogates:

 -- C 巨集: Py_UNICODE_IS_SURROGATE (ch)

     Check if `ch' is a surrogate (‘0xD800 <= ch <= 0xDFFF’).

 -- C 巨集: Py_UNICODE_IS_HIGH_SURROGATE (ch)

     Check if `ch' is a high surrogate (‘0xD800 <= ch <= 0xDBFF’).

 -- C 巨集: Py_UNICODE_IS_LOW_SURROGATE (ch)

     Check if `ch' is a low surrogate (‘0xDC00 <= ch <= 0xDFFF’).

 -- C 巨集: Py_UNICODE_JOIN_SURROGATES (high, low)

     Join two surrogate characters and return a single Py_UCS4 value.
     `high' and `low' are respectively the leading and trailing
     surrogates in a surrogate pair.


File: python.info,  Node: Creating and accessing Unicode strings,  Next: Deprecated Py_UNICODE APIs,  Prev: Unicode Character Properties,  Up: Unicode Objects

7.8.3.10 Creating and accessing Unicode strings
...............................................

To create Unicode objects and access their basic sequence properties,
use these APIs:

 -- C 函式: PyObject* PyUnicode_New (Py_ssize_t size, Py_UCS4 maxchar)
     `Return value: New reference.'  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 函式: PyObject* PyUnicode_FromKindAndData (int kind, const
          void *buffer, Py_ssize_t size)
     `Return value: New reference.'  Create a new Unicode object with
     the given `kind' (possible values are *note PyUnicode_1BYTE_KIND:
     ae5. etc., as returned by *note PyUnicode_KIND(): ae3.).  The
     `buffer' must point to an array of `size' units of 1, 2 or 4 bytes
     per character, as given by the kind.

     3.3 版新加入.

 -- C 函式: PyObject* PyUnicode_FromStringAndSize (const char *u,
          Py_ssize_t size)
     `Return value: New reference.'  Create a Unicode object from the
     char buffer `u'.  The bytes will be interpreted as being UTF-8
     encoded.  The buffer is copied into the new object.  If the buffer
     is not ‘NULL’, the return value might be a shared object, i.e.
     modification of the data is not allowed.

     If `u' is ‘NULL’, this function behaves like *note
     PyUnicode_FromUnicode(): af4. with the buffer set to ‘NULL’.  This
     usage is deprecated in favor of *note PyUnicode_New(): ad2, and
     will be removed in Python 3.12.

 -- C 函式: PyObject *PyUnicode_FromString (const char *u)
     `Return value: New reference.'  Create a Unicode object from a
     UTF-8 encoded null-terminated char buffer `u'.

 -- C 函式: PyObject* PyUnicode_FromFormat (const char *format, ...)
     `Return value: New reference.'  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.  The following format characters are
     allowed:

     Format Characters       Type                      Comment
                                                       
     -----------------------------------------------------------------------------------------
                                                       
     ‘%%’                    `n/a'                     The literal % character.
                                                       
                                                       
     ‘%c’                    int                       A single character, represented as a
                                                       C int.
                                                       
                                                       
     ‘%d’                    int                       Equivalent to ‘printf("%d")’.  (1)
                                                       
                                                       
     ‘%u’                    unsigned int              Equivalent to ‘printf("%u")’.  (2)
                                                       
                                                       
     ‘%ld’                   long                      Equivalent to ‘printf("%ld")’.  (3)
                                                       
                                                       
     ‘%li’                   long                      Equivalent to ‘printf("%li")’.  (4)
                                                       
                                                       
     ‘%lu’                   unsigned long             Equivalent to ‘printf("%lu")’.  (5)
                                                       
                                                       
     ‘%lld’                  long long                 Equivalent to ‘printf("%lld")’.  (6)
                                                       
                                                       
     ‘%lli’                  long long                 Equivalent to ‘printf("%lli")’.  (7)
                                                       
                                                       
     ‘%llu’                  unsigned long long        Equivalent to ‘printf("%llu")’.  (8)
                                                       
                                                       
     ‘%zd’                   Py_ssize_t                Equivalent to ‘printf("%zd")’.  (9)
                                                       
                                                       
     ‘%zi’                   Py_ssize_t                Equivalent to ‘printf("%zi")’.  (10)
                                                       
                                                       
     ‘%zu’                   size_t                    Equivalent to ‘printf("%zu")’.  (11)
                                                       
                                                       
     ‘%i’                    int                       Equivalent to ‘printf("%i")’.  (12)
                                                       
                                                       
     ‘%x’                    int                       Equivalent to ‘printf("%x")’.  (13)
                                                       
                                                       
     ‘%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.
                                                       
                                                       
     ‘%A’                    PyObject*                 The result of calling
                                                       *note ascii(): d51.
                                                       
                                                       
     ‘%U’                    PyObject*                 A Unicode object.
                                                       
                                                       
     ‘%V’                    PyObject*, const char*    A Unicode object (which may be
                                                       ‘NULL’) and a null-terminated C
                                                       character array as a second
                                                       parameter (which will be used, if
                                                       the first parameter is ‘NULL’).
                                                       
                                                       
     ‘%S’                    PyObject*                 The result of calling
                                                       *note PyObject_Str(): 96e.
                                                       
                                                       
     ‘%R’                    PyObject*                 The result of calling
                                                       *note PyObject_Repr(): 96d.
                                                       

     An unrecognized format character causes all the rest of the format
     string to be copied as-is to the result string, and any extra
     arguments discarded.

          備註: The width formatter unit is number of characters rather
          than bytes.  The precision formatter unit is number of bytes
          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’).

     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.

 -- C 函式: PyObject* PyUnicode_FromFormatV (const char *format,
          va_list vargs)
     `Return value: New reference.'  Identical to *note
     PyUnicode_FromFormat(): 7d0. except that it takes exactly two
     arguments.

 -- C 函式: PyObject* PyUnicode_FromEncodedObject (PyObject *obj, const
          char *encoding, const char *errors)
     `Return value: New reference.'  Decode an encoded object `obj' to a
     Unicode object.

     *note bytes: 336, *note bytearray: 337. and other *note bytes-like
     objects: 5ed. 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: 3dfb. for details).

     All other objects, including Unicode objects, cause a *note
     TypeError: 193. to be set.

     The API returns ‘NULL’ if there was an error.  The caller is
     responsible for decref’ing the returned objects.

 -- C 函式: Py_ssize_t PyUnicode_GetLength (PyObject *unicode)

     Return the length of the Unicode object, in code points.

     3.3 版新加入.

 -- C 函式: Py_ssize_t 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 函式: Py_ssize_t 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)

     Write a character to a string.  The string must have been created
     through *note PyUnicode_New(): ad2.  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 函式: Py_UCS4 PyUnicode_ReadChar (PyObject *unicode,
          Py_ssize_t index)

     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 the macro version *note PyUnicode_READ_CHAR(): ae9.

     3.3 版新加入.

 -- C 函式: PyObject* PyUnicode_Substring (PyObject *str,
          Py_ssize_t start, Py_ssize_t end)
     `Return value: New reference.'  Return a substring of `str', from
     character index `start' (included) to character index `end'
     (excluded).  Negative indices are not supported.

     3.3 版新加入.

 -- C 函式: Py_UCS4* PyUnicode_AsUCS4 (PyObject *u, Py_UCS4 *buffer,
          Py_ssize_t buflen, int copy_null)

     Copy the string `u' 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: 600. if `buflen' is
     smaller than the length of `u').  `buffer' is returned on success.

     3.3 版新加入.

 -- C 函式: Py_UCS4* PyUnicode_AsUCS4Copy (PyObject *u)

     Copy the string `u' into a new UCS4 buffer that is allocated using
     *note PyMem_Malloc(): 50a.  If this fails, ‘NULL’ is returned with
     a *note MemoryError: ef1. set.  The returned buffer always has an
     extra null code point appended.

     3.3 版新加入.

   ---------- Footnotes ----------

   (1) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (2) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (3) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (4) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (5) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (6) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (7) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (8) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (9) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (10) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (11) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (12) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.

   (13) (1) For integer specifiers (d, u, ld, li, lu, lld, lli, llu, zd,
zi, zu, i, x): the 0-conversion flag has effect even when a precision is
given.


File: python.info,  Node: Deprecated Py_UNICODE APIs,  Next: Locale Encoding,  Prev: Creating and accessing Unicode strings,  Up: Unicode Objects

7.8.3.11 Deprecated Py_UNICODE APIs
...................................

Deprecated since version 3.3, will be removed in version 3.12.

These API functions are deprecated with the implementation of PEP
393(1).  Extension modules can continue using them, as they will not be
removed in Python 3.x, but need to be aware that their use can now cause
performance and memory hits.

 -- C 函式: PyObject* PyUnicode_FromUnicode (const Py_UNICODE *u,
          Py_ssize_t size)
     `Return value: New reference.'  Create a Unicode object from the
     Py_UNICODE buffer `u' of the given size.  `u' may be ‘NULL’ which
     causes the contents to be undefined.  It is the user’s
     responsibility to fill in the needed data.  The buffer is copied
     into the new object.

     If the buffer is not ‘NULL’, the return value might be a shared
     object.  Therefore, modification of the resulting Unicode object is
     only allowed when `u' is ‘NULL’.

     If the buffer is ‘NULL’, *note PyUnicode_READY(): adb. must be
     called once the string content has been filled before using any of
     the access macros such as *note PyUnicode_KIND(): ae3.

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style Unicode API, please migrate to using *note
     PyUnicode_FromKindAndData(): adc, *note PyUnicode_FromWideChar():
     af5, or *note PyUnicode_New(): ad2.

 -- C 函式: Py_UNICODE* PyUnicode_AsUnicode (PyObject *unicode)

     Return a read-only pointer to the Unicode object’s internal *note
     Py_UNICODE: af3. buffer, or ‘NULL’ on error.  This will create the
     *note Py_UNICODE*: af3. representation of the object if it is not
     yet available.  The buffer is always terminated with an extra null
     code point.  Note that the resulting *note Py_UNICODE: af3. string
     may also contain embedded null code points, which would cause the
     string to be truncated when used in most C functions.

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style Unicode API, please migrate to using *note
     PyUnicode_AsUCS4(): add, *note PyUnicode_AsWideChar(): 1057, *note
     PyUnicode_ReadChar(): ad4. or similar new APIs.

     Deprecated since version 3.3, will be removed in version 3.10.

 -- C 函式: PyObject* PyUnicode_TransformDecimalToASCII (Py_UNICODE *s,
          Py_ssize_t size)
     `Return value: New reference.'  Create a Unicode object by
     replacing all decimal digits in *note Py_UNICODE: af3. buffer of
     the given `size' by ASCII digits 0–9 according to their decimal
     value.  Return ‘NULL’ if an exception occurs.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note Py_UNICODE_TODECIMAL(): 3df1.

 -- C 函式: Py_UNICODE* PyUnicode_AsUnicodeAndSize (PyObject *unicode,
          Py_ssize_t *size)

     Like *note PyUnicode_AsUnicode(): af7, but also saves the *note
     Py_UNICODE(): af3. array length (excluding the extra null
     terminator) in `size'.  Note that the resulting *note Py_UNICODE*:
     af3. string may contain embedded null code points, which would
     cause the string to be truncated when used in most C functions.

     3.3 版新加入.

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style Unicode API, please migrate to using *note
     PyUnicode_AsUCS4(): add, *note PyUnicode_AsWideChar(): 1057, *note
     PyUnicode_ReadChar(): ad4. or similar new APIs.

 -- C 函式: Py_UNICODE* PyUnicode_AsUnicodeCopy (PyObject *unicode)

     Create a copy of a Unicode string ending with a null code point.
     Return ‘NULL’ and raise a *note MemoryError: ef1. exception on
     memory allocation failure, otherwise return a new allocated buffer
     (use *note PyMem_Free(): dae. to free the buffer).  Note that the
     resulting *note Py_UNICODE*: af3. string may contain embedded null
     code points, which would cause the string to be truncated when used
     in most C functions.

     3.2 版新加入.

     Please migrate to using *note PyUnicode_AsUCS4Copy(): ade. or
     similar new APIs.

 -- C 函式: Py_ssize_t PyUnicode_GetSize (PyObject *unicode)

     Return the size of the deprecated *note Py_UNICODE: af3.
     representation, in code units (this includes surrogate pairs as 2
     units).

     Deprecated since version 3.3, will be removed in version 3.12: Part
     of the old-style Unicode API, please migrate to using *note
     PyUnicode_GET_LENGTH(): ad1.

 -- C 函式: PyObject* PyUnicode_FromObject (PyObject *obj)
     `Return value: New reference.'  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 the reference
     with incremented refcount.

     Objects other than Unicode or its subtypes will cause a *note
     TypeError: 193.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0393


File: python.info,  Node: Locale Encoding,  Next: File System Encoding,  Prev: Deprecated Py_UNICODE APIs,  Up: Unicode Objects

7.8.3.12 Locale Encoding
........................

The current locale encoding can be used to decode text from the
operating system.

 -- C 函式: PyObject* PyUnicode_DecodeLocaleAndSize (const char *str,
          Py_ssize_t len, const char *errors)
     `Return value: New reference.'  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(): 3c40. to decode a
     string from ‘Py_FileSystemDefaultEncoding’ (the locale encoding
     read at Python startup).

     This function ignores the Python UTF-8 mode.

     也參考
     ......

     The *note Py_DecodeLocale(): 441. function.

     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(): 441. was used for the
     ‘surrogateescape’, and the current locale encoding was used for
     ‘strict’.

 -- C 函式: PyObject* PyUnicode_DecodeLocale (const char *str, const
          char *errors)
     `Return value: New reference.'  Similar to *note
     PyUnicode_DecodeLocaleAndSize(): 443, but compute the string length
     using ‘strlen()’.

     3.3 版新加入.

 -- C 函式: PyObject* PyUnicode_EncodeLocale (PyObject *unicode, const
          char *errors)
     `Return value: New reference.'  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: 336.
     object.  `unicode' cannot contain embedded null characters.

     Use *note PyUnicode_EncodeFSDefault(): 1050. to encode a string to
     ‘Py_FileSystemDefaultEncoding’ (the locale encoding read at Python
     startup).

     This function ignores the Python UTF-8 mode.

     也參考
     ......

     The *note Py_EncodeLocale(): 442. function.

     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(): 442. was used for the
     ‘surrogateescape’, and the current locale encoding was used for
     ‘strict’.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0383

   (2) https://www.python.org/dev/peps/pep-0383


File: python.info,  Node: File System Encoding,  Next: wchar_t Support,  Prev: Locale Encoding,  Up: Unicode Objects

7.8.3.13 File System Encoding
.............................

To encode and decode file names and other environment strings,
‘Py_FileSystemDefaultEncoding’ should be used as the encoding, and
‘Py_FileSystemDefaultEncodeErrors’ should be used as the error handler (
PEP 383(1) and PEP 529(2)).  To encode file names to *note bytes: 336.
during argument parsing, the ‘"O&"’ converter should be used, passing
*note PyUnicode_FSConverter(): 5d3. as the conversion function:

 -- C 函式: int PyUnicode_FSConverter (PyObject* obj, void* result)

     ParseTuple converter: encode *note str: 335. objects – obtained
     directly or through the *note os.PathLike: 4f0. interface – to
     *note bytes: 336. using *note PyUnicode_EncodeFSDefault(): 1050.;
     *note bytes: 336. objects are output as-is.  `result' must be a
     *note PyBytesObject*: d23. which must be released when it is no
     longer used.

     3.1 版新加入.

     3.6 版更變: Accepts a *note path-like object: 36f.

To decode file names to *note str: 335. during argument parsing, the
‘"O&"’ converter should be used, passing *note PyUnicode_FSDecoder():
5d4. as the conversion function:

 -- C 函式: int PyUnicode_FSDecoder (PyObject* obj, void* result)

     ParseTuple converter: decode *note bytes: 336. objects – obtained
     either directly or indirectly through the *note os.PathLike: 4f0.
     interface – to *note str: 335. using *note
     PyUnicode_DecodeFSDefaultAndSize(): 3c40.; *note str: 335. objects
     are output as-is.  `result' must be a *note PyUnicodeObject*: 3dde.
     which must be released when it is no longer used.

     3.2 版新加入.

     3.6 版更變: Accepts a *note path-like object: 36f.

 -- C 函式: PyObject* PyUnicode_DecodeFSDefaultAndSize (const char *s,
          Py_ssize_t size)
     `Return value: New reference.'  Decode a string using
     ‘Py_FileSystemDefaultEncoding’ and the
     ‘Py_FileSystemDefaultEncodeErrors’ error handler.

     If ‘Py_FileSystemDefaultEncoding’ is not set, fall back to the
     locale encoding.

     ‘Py_FileSystemDefaultEncoding’ is initialized at startup from the
     locale encoding and cannot be modified later.  If you need to
     decode a string from the current locale encoding, use *note
     PyUnicode_DecodeLocaleAndSize(): 443.

     也參考
     ......

     The *note Py_DecodeLocale(): 441. function.

     3.6 版更變: Use ‘Py_FileSystemDefaultEncodeErrors’ error handler.

 -- C 函式: PyObject* PyUnicode_DecodeFSDefault (const char *s)
     `Return value: New reference.'  Decode a null-terminated string
     using ‘Py_FileSystemDefaultEncoding’ and the
     ‘Py_FileSystemDefaultEncodeErrors’ error handler.

     If ‘Py_FileSystemDefaultEncoding’ is not set, fall back to the
     locale encoding.

     Use *note PyUnicode_DecodeFSDefaultAndSize(): 3c40. if you know the
     string length.

     3.6 版更變: Use ‘Py_FileSystemDefaultEncodeErrors’ error handler.

 -- C 函式: PyObject* PyUnicode_EncodeFSDefault (PyObject *unicode)
     `Return value: New reference.'  Encode a Unicode object to
     ‘Py_FileSystemDefaultEncoding’ with the
     ‘Py_FileSystemDefaultEncodeErrors’ error handler, and return *note
     bytes: 336.  Note that the resulting *note bytes: 336. object may
     contain null bytes.

     If ‘Py_FileSystemDefaultEncoding’ is not set, fall back to the
     locale encoding.

     ‘Py_FileSystemDefaultEncoding’ is initialized at startup from the
     locale encoding and cannot be modified later.  If you need to
     encode a string to the current locale encoding, use *note
     PyUnicode_EncodeLocale(): 444.

     也參考
     ......

     The *note Py_EncodeLocale(): 442. function.

     3.2 版新加入.

     3.6 版更變: Use ‘Py_FileSystemDefaultEncodeErrors’ error handler.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0383

   (2) https://www.python.org/dev/peps/pep-0529


File: python.info,  Node: wchar_t Support,  Prev: File System Encoding,  Up: Unicode Objects

7.8.3.14 wchar_t Support
........................

‘wchar_t’ support for platforms which support it:

 -- C 函式: PyObject* PyUnicode_FromWideChar (const wchar_t *w,
          Py_ssize_t size)
     `Return value: New reference.'  Create a Unicode object from the
     ‘wchar_t’ buffer `w' 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 函式: Py_ssize_t PyUnicode_AsWideChar (PyObject *unicode,
          wchar_t *w, Py_ssize_t size)

     Copy the Unicode object contents into the ‘wchar_t’ buffer `w'.  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.  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)

     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: 1fc. is raised.

     Returns a buffer allocated by ‘PyMem_Alloc()’ (use *note
     PyMem_Free(): dae. to free it) on success.  On error, returns
     ‘NULL’ and `*size' is undefined.  Raises a *note MemoryError: ef1.
     if memory allocation is failed.

     3.2 版新加入.

     3.7 版更變: Raises a *note ValueError: 1fc. 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 Objects,  Up: Unicode物件與編碼

7.8.3.15 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():
335. string object constructor.

Setting encoding to ‘NULL’ causes the default encoding to be used which
is ASCII. The file system calls should use *note
PyUnicode_FSConverter(): 5d3. for encoding file names.  This uses the
variable ‘Py_FileSystemDefaultEncoding’ internally.  This variable
should be treated as read-only: on some systems, it will be a pointer to
a static string, on others, it will change at run-time (such as when the
application invokes setlocale).

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: 1fc. is
raised).

The codecs all use a similar interface.  Only deviation from the
following generic ones are documented for simplicity.

* Menu:

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


File: python.info,  Node: Generic Codecs,  Next: UTF-8 Codecs,  Up: Built-in Codecs

7.8.3.16 Generic Codecs
.......................

These are the generic codec APIs:

 -- C 函式: PyObject* PyUnicode_Decode (const char *s, Py_ssize_t size,
          const char *encoding, const char *errors)
     `Return value: New reference.'  Create a Unicode object by decoding
     `size' bytes of the encoded string `s'.  `encoding' and `errors'
     have the same meaning as the parameters of the same name in the
     *note str(): 335. 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 函式: PyObject* PyUnicode_AsEncodedString (PyObject *unicode,
          const char *encoding, const char *errors)
     `Return value: New reference.'  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(): c3c. method.  The codec to be used is looked up
     using the Python codec registry.  Return ‘NULL’ if an exception was
     raised by the codec.

 -- C 函式: PyObject* PyUnicode_Encode (const Py_UNICODE *s,
          Py_ssize_t size, const char *encoding, const char *errors)
     `Return value: New reference.'  Encode the *note Py_UNICODE: af3.
     buffer `s' of the given `size' and return a Python bytes object.
     `encoding' and `errors' have the same meaning as the parameters of
     the same name in the Unicode *note encode(): c3c. method.  The
     codec to be used is looked up using the Python codec registry.
     Return ‘NULL’ if an exception was raised by the codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsEncodedString(): 3e05.


File: python.info,  Node: UTF-8 Codecs,  Next: UTF-32 Codecs,  Prev: Generic Codecs,  Up: Built-in Codecs

7.8.3.17 UTF-8 Codecs
.....................

These are the UTF-8 codec APIs:

 -- C 函式: PyObject* PyUnicode_DecodeUTF8 (const char *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Create a Unicode object by decoding
     `size' bytes of the UTF-8 encoded string `s'.  Return ‘NULL’ if an
     exception was raised by the codec.

 -- C 函式: PyObject* PyUnicode_DecodeUTF8Stateful (const char *s,
          Py_ssize_t size, const char *errors, Py_ssize_t *consumed)
     `Return value: New reference.'  If `consumed' is ‘NULL’, behave
     like *note PyUnicode_DecodeUTF8(): 3e07.  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 函式: PyObject* PyUnicode_AsUTF8String (PyObject *unicode)
     `Return value: New reference.'  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)

     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.

     In the case of an error, ‘NULL’ is returned with an exception set
     and no `size' is stored.

     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.

     3.3 版新加入.

     3.7 版更變: The return type is now ‘const char *’ rather of ‘char
     *’.

 -- C 函式: const char* PyUnicode_AsUTF8 (PyObject *unicode)

     As *note PyUnicode_AsUTF8AndSize(): 42f, but does not store the
     size.

     3.3 版新加入.

     3.7 版更變: The return type is now ‘const char *’ rather of ‘char
     *’.

 -- C 函式: PyObject* PyUnicode_EncodeUTF8 (const Py_UNICODE *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Encode the *note Py_UNICODE: af3.
     buffer `s' of the given `size' using UTF-8 and return a Python
     bytes object.  Return ‘NULL’ if an exception was raised by the
     codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsUTF8String(): b04, *note
     PyUnicode_AsUTF8AndSize(): 42f. or *note
     PyUnicode_AsEncodedString(): 3e05.


File: python.info,  Node: UTF-32 Codecs,  Next: UTF-16 Codecs,  Prev: UTF-8 Codecs,  Up: Built-in Codecs

7.8.3.18 UTF-32 Codecs
......................

These are the UTF-32 codec APIs:

 -- C 函式: PyObject* PyUnicode_DecodeUTF32 (const char *s,
          Py_ssize_t size, const char *errors, int *byteorder)
     `Return value: New reference.'  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 函式: PyObject* PyUnicode_DecodeUTF32Stateful (const char *s,
          Py_ssize_t size, const char *errors, int *byteorder,
          Py_ssize_t *consumed)
     `Return value: New reference.'  If `consumed' is ‘NULL’, behave
     like *note PyUnicode_DecodeUTF32(): 3e0a.  If `consumed' is not
     ‘NULL’, *note PyUnicode_DecodeUTF32Stateful(): 3e0b. 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 函式: PyObject* PyUnicode_AsUTF32String (PyObject *unicode)
     `Return value: New reference.'  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.

 -- C 函式: PyObject* PyUnicode_EncodeUTF32 (const Py_UNICODE *s,
          Py_ssize_t size, const char *errors, int byteorder)
     `Return value: New reference.'  Return a Python bytes object
     holding the UTF-32 encoded value of the Unicode data in `s'.
     Output is written according to the following byte order:

          byteorder == -1: little endian
          byteorder == 0:  native byte order (writes a BOM mark)
          byteorder == 1:  big endian

     If byteorder is ‘0’, the output string will always start with the
     Unicode BOM mark (U+FEFF). In the other two modes, no BOM mark is
     prepended.

     If ‘Py_UNICODE_WIDE’ is not defined, surrogate pairs will be output
     as a single code point.

     Return ‘NULL’ if an exception was raised by the codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsUTF32String(): 3e0c. or *note
     PyUnicode_AsEncodedString(): 3e05.


File: python.info,  Node: UTF-16 Codecs,  Next: UTF-7 Codecs,  Prev: UTF-32 Codecs,  Up: Built-in Codecs

7.8.3.19 UTF-16 Codecs
......................

These are the UTF-16 codec APIs:

 -- C 函式: PyObject* PyUnicode_DecodeUTF16 (const char *s,
          Py_ssize_t size, const char *errors, int *byteorder)
     `Return value: New reference.'  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 函式: PyObject* PyUnicode_DecodeUTF16Stateful (const char *s,
          Py_ssize_t size, const char *errors, int *byteorder,
          Py_ssize_t *consumed)
     `Return value: New reference.'  If `consumed' is ‘NULL’, behave
     like *note PyUnicode_DecodeUTF16(): 3e0e.  If `consumed' is not
     ‘NULL’, *note PyUnicode_DecodeUTF16Stateful(): 3e0f. 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 函式: PyObject* PyUnicode_AsUTF16String (PyObject *unicode)
     `Return value: New reference.'  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.

 -- C 函式: PyObject* PyUnicode_EncodeUTF16 (const Py_UNICODE *s,
          Py_ssize_t size, const char *errors, int byteorder)
     `Return value: New reference.'  Return a Python bytes object
     holding the UTF-16 encoded value of the Unicode data in `s'.
     Output is written according to the following byte order:

          byteorder == -1: little endian
          byteorder == 0:  native byte order (writes a BOM mark)
          byteorder == 1:  big endian

     If byteorder is ‘0’, the output string will always start with the
     Unicode BOM mark (U+FEFF). In the other two modes, no BOM mark is
     prepended.

     If ‘Py_UNICODE_WIDE’ is defined, a single *note Py_UNICODE: af3.
     value may get represented as a surrogate pair.  If it is not
     defined, each *note Py_UNICODE: af3. values is interpreted as a
     UCS-2 character.

     Return ‘NULL’ if an exception was raised by the codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsUTF16String(): 3e10. or *note
     PyUnicode_AsEncodedString(): 3e05.


File: python.info,  Node: UTF-7 Codecs,  Next: Unicode-Escape Codecs,  Prev: UTF-16 Codecs,  Up: Built-in Codecs

7.8.3.20 UTF-7 Codecs
.....................

These are the UTF-7 codec APIs:

 -- C 函式: PyObject* PyUnicode_DecodeUTF7 (const char *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Create a Unicode object by decoding
     `size' bytes of the UTF-7 encoded string `s'.  Return ‘NULL’ if an
     exception was raised by the codec.

 -- C 函式: PyObject* PyUnicode_DecodeUTF7Stateful (const char *s,
          Py_ssize_t size, const char *errors, Py_ssize_t *consumed)
     `Return value: New reference.'  If `consumed' is ‘NULL’, behave
     like *note PyUnicode_DecodeUTF7(): 3e12.  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'.

 -- C 函式: PyObject* PyUnicode_EncodeUTF7 (const Py_UNICODE *s,
          Py_ssize_t size, int base64SetO, int base64WhiteSpace, const
          char *errors)
     `Return value: New reference.'  Encode the *note Py_UNICODE: af3.
     buffer of the given size using UTF-7 and return a Python bytes
     object.  Return ‘NULL’ if an exception was raised by the codec.

     If `base64SetO' is nonzero, "Set O" (punctuation that has no
     otherwise special meaning) will be encoded in base-64.  If
     `base64WhiteSpace' is nonzero, whitespace will be encoded in
     base-64.  Both are set to zero for the Python "utf-7" codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsEncodedString(): 3e05.


File: python.info,  Node: Unicode-Escape Codecs,  Next: Raw-Unicode-Escape Codecs,  Prev: UTF-7 Codecs,  Up: Built-in Codecs

7.8.3.21 Unicode-Escape Codecs
..............................

These are the "Unicode Escape" codec APIs:

 -- C 函式: PyObject* PyUnicode_DecodeUnicodeEscape (const char *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Create a Unicode object by decoding
     `size' bytes of the Unicode-Escape encoded string `s'.  Return
     ‘NULL’ if an exception was raised by the codec.

 -- C 函式: PyObject* PyUnicode_AsUnicodeEscapeString
          (PyObject *unicode)
     `Return value: New reference.'  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.

 -- C 函式: PyObject* PyUnicode_EncodeUnicodeEscape (const
          Py_UNICODE *s, Py_ssize_t size)
     `Return value: New reference.'  Encode the *note Py_UNICODE: af3.
     buffer of the given `size' using Unicode-Escape and return a bytes
     object.  Return ‘NULL’ if an exception was raised by the codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsUnicodeEscapeString(): b08.


File: python.info,  Node: Raw-Unicode-Escape Codecs,  Next: Latin-1 Codecs,  Prev: Unicode-Escape Codecs,  Up: Built-in Codecs

7.8.3.22 Raw-Unicode-Escape Codecs
..................................

These are the "Raw Unicode Escape" codec APIs:

 -- C 函式: PyObject* PyUnicode_DecodeRawUnicodeEscape (const char *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Create a Unicode object by decoding
     `size' bytes of the Raw-Unicode-Escape encoded string `s'.  Return
     ‘NULL’ if an exception was raised by the codec.

 -- C 函式: PyObject* PyUnicode_AsRawUnicodeEscapeString
          (PyObject *unicode)
     `Return value: New reference.'  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.

 -- C 函式: PyObject* PyUnicode_EncodeRawUnicodeEscape (const
          Py_UNICODE *s, Py_ssize_t size)
     `Return value: New reference.'  Encode the *note Py_UNICODE: af3.
     buffer of the given `size' using Raw-Unicode-Escape and return a
     bytes object.  Return ‘NULL’ if an exception was raised by the
     codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsRawUnicodeEscapeString(): b0a. or *note
     PyUnicode_AsEncodedString(): 3e05.


File: python.info,  Node: Latin-1 Codecs,  Next: ASCII Codecs,  Prev: Raw-Unicode-Escape Codecs,  Up: Built-in Codecs

7.8.3.23 Latin-1 Codecs
.......................

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 函式: PyObject* PyUnicode_DecodeLatin1 (const char *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Create a Unicode object by decoding
     `size' bytes of the Latin-1 encoded string `s'.  Return ‘NULL’ if
     an exception was raised by the codec.

 -- C 函式: PyObject* PyUnicode_AsLatin1String (PyObject *unicode)
     `Return value: New reference.'  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.

 -- C 函式: PyObject* PyUnicode_EncodeLatin1 (const Py_UNICODE *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Encode the *note Py_UNICODE: af3.
     buffer of the given `size' using Latin-1 and return a Python bytes
     object.  Return ‘NULL’ if an exception was raised by the codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsLatin1String(): b0c. or *note
     PyUnicode_AsEncodedString(): 3e05.


File: python.info,  Node: ASCII Codecs,  Next: Character Map Codecs,  Prev: Latin-1 Codecs,  Up: Built-in Codecs

7.8.3.24 ASCII Codecs
.....................

These are the ASCII codec APIs.  Only 7-bit ASCII data is accepted.  All
other codes generate errors.

 -- C 函式: PyObject* PyUnicode_DecodeASCII (const char *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Create a Unicode object by decoding
     `size' bytes of the ASCII encoded string `s'.  Return ‘NULL’ if an
     exception was raised by the codec.

 -- C 函式: PyObject* PyUnicode_AsASCIIString (PyObject *unicode)
     `Return value: New reference.'  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.

 -- C 函式: PyObject* PyUnicode_EncodeASCII (const Py_UNICODE *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Encode the *note Py_UNICODE: af3.
     buffer of the given `size' using ASCII and return a Python bytes
     object.  Return ‘NULL’ if an exception was raised by the codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsASCIIString(): b0e. or *note
     PyUnicode_AsEncodedString(): 3e05.


File: python.info,  Node: Character Map Codecs,  Next: MBCS codecs for Windows,  Prev: ASCII Codecs,  Up: Built-in Codecs

7.8.3.25 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 mapping to
encode and decode characters.  The mapping objects provided must support
the *note __getitem__(): 27d. mapping interface; dictionaries and
sequences work well.

These are the mapping codec APIs:

 -- C 函式: PyObject* PyUnicode_DecodeCharmap (const char *data,
          Py_ssize_t size, PyObject *mapping, const char *errors)
     `Return value: New reference.'  Create a Unicode object by decoding
     `size' bytes of the encoded string `s' 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: 1662, as well as ones which get mapped
     to ‘None’, ‘0xFFFE’ or ‘'\ufffe'’, are treated as undefined
     mappings and cause an error.

 -- C 函式: PyObject* PyUnicode_AsCharmapString (PyObject *unicode,
          PyObject *mapping)
     `Return value: New reference.'  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: 1662.) as
     well as mapped to ‘None’ are treated as "undefined mapping" and
     cause an error.

 -- C 函式: PyObject* PyUnicode_EncodeCharmap (const Py_UNICODE *s,
          Py_ssize_t size, PyObject *mapping, const char *errors)
     `Return value: New reference.'  Encode the *note Py_UNICODE: af3.
     buffer of the given `size' using the given `mapping' object and
     return the result as a bytes object.  Return ‘NULL’ if an exception
     was raised by the codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsCharmapString(): 3e1e. or *note
     PyUnicode_AsEncodedString(): 3e05.

The following codec API is special in that maps Unicode to Unicode.

 -- C 函式: PyObject* PyUnicode_Translate (PyObject *str,
          PyObject *table, const char *errors)
     `Return value: New reference.'  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__(): 27d.
     interface; dictionaries and sequences work well.  Unmapped
     character ordinals (ones which cause a *note LookupError: 1662.)
     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.

 -- C 函式: PyObject* PyUnicode_TranslateCharmap (const Py_UNICODE *s,
          Py_ssize_t size, PyObject *mapping, const char *errors)
     `Return value: New reference.'  Translate a *note Py_UNICODE: af3.
     buffer of the given `size' by applying a character `mapping' table
     to it and return the resulting Unicode object.  Return ‘NULL’ when
     an exception was raised by the codec.

     Deprecated since version 3.3, will be removed in version 3.11: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_Translate(): 3e1f.  or *note generic codec
     based API: 5f3.


File: python.info,  Node: MBCS codecs for Windows,  Next: Methods & Slots,  Prev: Character Map Codecs,  Up: Built-in Codecs

7.8.3.26 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 函式: PyObject* PyUnicode_DecodeMBCS (const char *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Create a Unicode object by decoding
     `size' bytes of the MBCS encoded string `s'.  Return ‘NULL’ if an
     exception was raised by the codec.

 -- C 函式: PyObject* PyUnicode_DecodeMBCSStateful (const char *s,
          Py_ssize_t size, const char *errors, Py_ssize_t *consumed)
     `Return value: New reference.'  If `consumed' is ‘NULL’, behave
     like *note PyUnicode_DecodeMBCS(): 3e21.  If `consumed' is not
     ‘NULL’, *note PyUnicode_DecodeMBCSStateful(): 3e22. will not decode
     trailing lead byte and the number of bytes that have been decoded
     will be stored in `consumed'.

 -- C 函式: PyObject* PyUnicode_AsMBCSString (PyObject *unicode)
     `Return value: New reference.'  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 函式: PyObject* PyUnicode_EncodeCodePage (int code_page,
          PyObject *unicode, const char *errors)
     `Return value: New reference.'  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 版新加入.

 -- C 函式: PyObject* PyUnicode_EncodeMBCS (const Py_UNICODE *s,
          Py_ssize_t size, const char *errors)
     `Return value: New reference.'  Encode the *note Py_UNICODE: af3.
     buffer of the given `size' using MBCS and return a Python bytes
     object.  Return ‘NULL’ if an exception was raised by the codec.

     Deprecated since version 3.3, will be removed in version 4.0: Part
     of the old-style *note Py_UNICODE: af3. API; please migrate to
     using *note PyUnicode_AsMBCSString(): b12, *note
     PyUnicode_EncodeCodePage(): b13. or *note
     PyUnicode_AsEncodedString(): 3e05.


File: python.info,  Node: Methods & Slots,  Prev: MBCS codecs for Windows,  Up: Built-in Codecs

7.8.3.27 Methods & Slots
........................


File: python.info,  Node: Methods and Slot Functions,  Prev: Built-in Codecs,  Up: Unicode物件與編碼

7.8.3.28 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 函式: PyObject* PyUnicode_Concat (PyObject *left, PyObject *right)
     `Return value: New reference.'  Concat two strings giving a new
     Unicode string.

 -- C 函式: PyObject* PyUnicode_Split (PyObject *s, PyObject *sep,
          Py_ssize_t maxsplit)
     `Return value: New reference.'  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 函式: PyObject* PyUnicode_Splitlines (PyObject *s, int keepend)
     `Return value: New reference.'  Split a Unicode string at line
     breaks, returning a list of Unicode strings.  CRLF is considered to
     be one line break.  If `keepend' is ‘0’, the Line break characters
     are not included in the resulting strings.

 -- C 函式: PyObject* PyUnicode_Join (PyObject *separator,
          PyObject *seq)
     `Return value: New reference.'  Join a sequence of strings using
     the given `separator' and return the resulting Unicode string.

 -- C 函式: Py_ssize_t PyUnicode_Tailmatch (PyObject *str,
          PyObject *substr, Py_ssize_t start, Py_ssize_t end,
          int direction)

     Return ‘1’ if `substr' matches ‘str[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 函式: Py_ssize_t PyUnicode_Find (PyObject *str, PyObject *substr,
          Py_ssize_t start, Py_ssize_t end, int direction)

     Return the first position of `substr' in ‘str[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 函式: Py_ssize_t PyUnicode_FindChar (PyObject *str, Py_UCS4 ch,
          Py_ssize_t start, Py_ssize_t end, int direction)

     Return the first position of the character `ch' in ‘str[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
     ‘str[start:end]’.

 -- C 函式: Py_ssize_t PyUnicode_Count (PyObject *str, PyObject *substr,
          Py_ssize_t start, Py_ssize_t end)

     Return the number of non-overlapping occurrences of `substr' in
     ‘str[start:end]’.  Return ‘-1’ if an error occurred.

 -- C 函式: PyObject* PyUnicode_Replace (PyObject *str,
          PyObject *substr, PyObject *replstr, Py_ssize_t maxcount)
     `Return value: New reference.'  Replace at most `maxcount'
     occurrences of `substr' in `str' with `replstr' and return the
     resulting Unicode object.  `maxcount' == ‘-1’ means replace all
     occurrences.

 -- C 函式: int PyUnicode_Compare (PyObject *left, PyObject *right)

     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(): 3af9. to check for errors.

 -- C 函式: int PyUnicode_CompareWithASCIIString (PyObject *uni, const
          char *string)

     Compare a Unicode object, `uni', 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 函式: PyObject* PyUnicode_RichCompare (PyObject *left,
          PyObject *right, int op)
     `Return value: New reference.'  Rich compare two Unicode strings
     and return one of the following:

        * ‘NULL’ in case an exception was raised

        * ‘Py_True’ or ‘Py_False’ for successful comparisons

        * ‘Py_NotImplemented’ in case the type combination is unknown

     Possible values for `op' are ‘Py_GT’, ‘Py_GE’, ‘Py_EQ’, ‘Py_NE’,
     ‘Py_LT’, and ‘Py_LE’.

 -- C 函式: PyObject* PyUnicode_Format (PyObject *format,
          PyObject *args)
     `Return value: New reference.'  Return a new string object from
     `format' and `args'; this is analogous to ‘format % args’.

 -- C 函式: int PyUnicode_Contains (PyObject *container,
          PyObject *element)

     Check whether `element' is contained in `container' and return true
     or false accordingly.

     `element' has to coerce to a one element Unicode string.  ‘-1’ is
     returned if there was an error.

 -- C 函式: void PyUnicode_InternInPlace (PyObject **string)

     Intern the argument `*string' 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 `*string', it sets `*string' to it (decrementing the reference
     count of the old string object and incrementing the reference count
     of the interned string object), otherwise it leaves `*string' alone
     and interns it (incrementing its reference count).  (Clarification:
     even though there is a lot of talk about reference counts, think of
     this function as reference-count-neutral; you own the object after
     the call if and only if you owned it before the call.)

 -- C 函式: PyObject* PyUnicode_InternFromString (const char *v)
     `Return value: New reference.'  A combination of *note
     PyUnicode_FromString(): 3b8a. and *note PyUnicode_InternInPlace():
     3e2e, returning either a new Unicode string object that has been
     interned, or a new ("owned") reference to an earlier interned
     string object with the same value.


File: python.info,  Node: 元組（Tuple）物件,  Next: Struct Sequence Objects,  Prev: Unicode物件與編碼,  Up: Sequence Objects

7.8.3.29 元組（Tuple）物件
..........................

 -- C 類型: PyTupleObject

     This subtype of *note PyObject: 4bf. represents a Python tuple
     object.

 -- C 變數: PyTypeObject PyTuple_Type

     This instance of *note PyTypeObject: 2d7. represents the Python
     tuple type; it is the same object as *note tuple: 483. 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.

 -- 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.

 -- C 函式: PyObject* PyTuple_New (Py_ssize_t len)
     `Return value: New reference.'  Return a new tuple object of size
     `len', or ‘NULL’ on failure.

 -- C 函式: PyObject* PyTuple_Pack (Py_ssize_t n, ...)
     `Return value: New reference.'  Return a new tuple object of size
     `n', or ‘NULL’ 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 函式: Py_ssize_t PyTuple_Size (PyObject *p)

     Take a pointer to a tuple object, and return the size of that
     tuple.

 -- C 函式: Py_ssize_t PyTuple_GET_SIZE (PyObject *p)

     Return the size of the tuple `p', which must be non-‘NULL’ and
     point to a tuple; no error checking is performed.

 -- C 函式: PyObject* PyTuple_GetItem (PyObject *p, Py_ssize_t pos)
     `Return value: Borrowed reference.'  Return the object at position
     `pos' in the tuple pointed to by `p'.  If `pos' is out of bounds,
     return ‘NULL’ and set an *note IndexError: e7a. exception.

 -- C 函式: PyObject* PyTuple_GET_ITEM (PyObject *p, Py_ssize_t pos)
     `Return value: Borrowed reference.'  Like *note PyTuple_GetItem():
     3b16, but does no checking of its arguments.

 -- C 函式: PyObject* PyTuple_GetSlice (PyObject *p, Py_ssize_t low,
          Py_ssize_t high)
     `Return value: New reference.'  Return the slice of the tuple
     pointed to by `p' between `low' and `high', or ‘NULL’ on failure.
     This is the equivalent of the Python expression ‘p[low:high]’.
     Indexing from the end of the list is not supported.

 -- C 函式: int PyTuple_SetItem (PyObject *p, Py_ssize_t pos,
          PyObject *o)

     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: e7a. 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(): 3b1b, but does no error checking, and
     should `only' be used to fill in brand new tuples.

          備註: This macro "steals" a reference to `o', and, unlike
          *note PyTuple_SetItem(): 3b1b, 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: ef1. or
     *note SystemError: 600.

 -- C 函式: int PyTuple_ClearFreeList ()

     Clear the free list.  Return the total number of freed items.


File: python.info,  Node: Struct Sequence Objects,  Next: List（串列）物件,  Prev: 元組（Tuple）物件,  Up: Sequence Objects

7.8.3.30 Struct Sequence Objects
................................

Struct sequence objects are the C equivalent of *note namedtuple(): 1b8.
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 函式: PyTypeObject* PyStructSequence_NewType
          (PyStructSequence_Desc *desc)
     `Return value: New reference.'  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():
     3e40.

 -- 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)

     The same as ‘PyStructSequence_InitType’, but returns ‘0’ on success
     and ‘-1’ on failure.

     3.4 版新加入.

 -- C 類型: PyStructSequence_Desc

     Contains the meta information of a struct sequence type to create.

     Field                   C Type                             Meaning
                                                                
     ------------------------------------------------------------------------------------------------------
                                                                
     ‘name’                  ‘const char *’                     name of the struct sequence type
                                                                
                                                                
     ‘doc’                   ‘const char *’                     pointer to docstring for the type or
                                                                ‘NULL’ to omit
                                                                
                                                                
     ‘fields’                ‘PyStructSequence_Field *’         pointer to ‘NULL’-terminated array with
                                                                field names of the new type
                                                                
                                                                
     ‘n_in_sequence’         ‘int’                              number of fields visible to the Python
                                                                side (if used as tuple)
                                                                

 -- C 類型: PyStructSequence_Field

     Describes a field of a struct sequence.  As a struct sequence is
     modeled as a tuple, all fields are typed as *note PyObject*: 4bf.
     The index in the ‘fields’ array of the *note PyStructSequence_Desc:
     42e. determines which field of the struct sequence is described.

     Field           C Type                 Meaning
                                            
     -------------------------------------------------------------------------------------
                                            
     ‘name’          ‘const char *’         name for the field or ‘NULL’ to end the
                                            list of named fields, set to
                                            *note PyStructSequence_UnnamedField: 3e41.
                                            to leave unnamed
                                            
                                            
     ‘doc’           ‘const char *’         field docstring or ‘NULL’ to omit
                                            

 -- C 變數: char* PyStructSequence_UnnamedField

     Special value for a field name to leave it unnamed.

 -- C 函式: PyObject* PyStructSequence_New (PyTypeObject *type)
     `Return value: New reference.'  Creates an instance of `type',
     which must have been created with *note PyStructSequence_NewType():
     3e3f.

 -- C 函式: PyObject* PyStructSequence_GetItem (PyObject *p,
          Py_ssize_t pos)
     `Return value: Borrowed reference.'  Return the object at position
     `pos' in the struct sequence pointed to by `p'.  No bounds checking
     is performed.

 -- C 函式: PyObject* PyStructSequence_GET_ITEM (PyObject *p,
          Py_ssize_t pos)
     `Return value: Borrowed reference.'  Macro equivalent of *note
     PyStructSequence_GetItem(): 3e42.

 -- C 函式: void PyStructSequence_SetItem (PyObject *p, Py_ssize_t pos,
          PyObject *o)

     Sets the field at index `pos' of the struct sequence `p' to value
     `o'.  Like *note PyTuple_SET_ITEM(): 3e3c, this should only be used
     to fill in brand new instances.

          備註: This function "steals" a reference to `o'.

 -- C 函式: void PyStructSequence_SET_ITEM (PyObject *p,
          Py_ssize_t *pos, PyObject *o)

     Macro equivalent of *note PyStructSequence_SetItem(): 3e44.

          備註: This function "steals" a reference to `o'.


File: python.info,  Node: List（串列）物件,  Prev: Struct Sequence Objects,  Up: Sequence Objects

7.8.3.31 List（串列）物件
.........................

 -- C 類型: PyListObject

     This subtype of *note PyObject: 4bf. represents a Python list
     object.

 -- C 變數: PyTypeObject PyList_Type

     This instance of *note PyTypeObject: 2d7. represents the Python
     list type.  This is the same object as *note list: 263. in the
     Python layer.

 -- C 函式: int PyList_Check (PyObject *p)

     Return true if `p' is a list object or an instance of a subtype of
     the list type.

 -- C 函式: int PyList_CheckExact (PyObject *p)

     Return true if `p' is a list object, but not an instance of a
     subtype of the list type.

 -- C 函式: PyObject* PyList_New (Py_ssize_t len)
     `Return value: New reference.'  Return a new list of length `len'
     on success, or ‘NULL’ on failure.

          備註: 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():
          1054. or expose the object to Python code before setting all
          items to a real object with *note PyList_SetItem(): 3b1c.

 -- C 函式: Py_ssize_t PyList_Size (PyObject *list)

     Return the length of the list object in `list'; this is equivalent
     to ‘len(list)’ on a list object.

 -- C 函式: Py_ssize_t PyList_GET_SIZE (PyObject *list)

     Macro form of *note PyList_Size(): d83. without error checking.

 -- C 函式: PyObject* PyList_GetItem (PyObject *list, Py_ssize_t index)
     `Return value: Borrowed reference.'  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: e7a. exception.

 -- C 函式: PyObject* PyList_GET_ITEM (PyObject *list, Py_ssize_t i)
     `Return value: Borrowed reference.'  Macro form of *note
     PyList_GetItem(): 3b17. without error checking.

 -- C 函式: int PyList_SetItem (PyObject *list, Py_ssize_t index,
          PyObject *item)

     Set the item at index `index' in list to `item'.  Return ‘0’ on
     success.  If `index' is out of bounds, return ‘-1’ and set an *note
     IndexError: e7a. exception.

          備註: This function "steals" a reference to `item' and
          discards a reference to an item already in the list at the
          affected position.

 -- C 函式: void PyList_SET_ITEM (PyObject *list, Py_ssize_t i,
          PyObject *o)

     Macro form of *note PyList_SetItem(): 3b1c. without error checking.
     This is normally only used to fill in new lists where there is no
     previous content.

          備註: This macro "steals" a reference to `item', and, unlike
          *note PyList_SetItem(): 3b1c, does `not' discard a reference
          to any item that is being replaced; any reference in `list' at
          position `i' will be leaked.

 -- C 函式: int PyList_Insert (PyObject *list, Py_ssize_t index,
          PyObject *item)

     Insert the item `item' into list `list' in front of index `index'.
     Return ‘0’ if successful; return ‘-1’ and set an exception if
     unsuccessful.  Analogous to ‘list.insert(index, item)’.

 -- C 函式: int PyList_Append (PyObject *list, PyObject *item)

     Append the object `item' at the end of list `list'.  Return ‘0’ if
     successful; return ‘-1’ and set an exception if unsuccessful.
     Analogous to ‘list.append(item)’.

 -- C 函式: PyObject* PyList_GetSlice (PyObject *list, Py_ssize_t low,
          Py_ssize_t high)
     `Return value: New reference.'  Return a list of the objects in
     `list' containing the objects `between' `low' and `high'.  Return
     ‘NULL’ and set an exception if unsuccessful.  Analogous to
     ‘list[low:high]’.  Indexing from the end of the list is not
     supported.

 -- C 函式: int PyList_SetSlice (PyObject *list, Py_ssize_t low,
          Py_ssize_t high, PyObject *itemlist)

     Set the slice of `list' between `low' and `high' to the contents of
     `itemlist'.  Analogous to ‘list[low:high] = itemlist’.  The
     `itemlist' may be ‘NULL’, indicating the assignment of an empty
     list (slice deletion).  Return ‘0’ on success, ‘-1’ on failure.
     Indexing from the end of the list is not supported.

 -- C 函式: int PyList_Sort (PyObject *list)

     Sort the items of `list' in place.  Return ‘0’ on success, ‘-1’ on
     failure.  This is equivalent to ‘list.sort()’.

 -- C 函式: int PyList_Reverse (PyObject *list)

     Reverse the items of `list' in place.  Return ‘0’ on success, ‘-1’
     on failure.  This is the equivalent of ‘list.reverse()’.

 -- C 函式: PyObject* PyList_AsTuple (PyObject *list)
     `Return value: New reference.'

     Return a new tuple object containing the contents of `list';
     equivalent to ‘tuple(list)’.

 -- C 函式: int PyList_ClearFreeList ()

     Clear the free list.  Return the total number of freed items.

     3.3 版新加入.


File: python.info,  Node: Container Objects,  Next: 函式物件<2>,  Prev: Sequence Objects,  Up: Concrete Objects Layer

7.8.4 Container Objects
-----------------------

* Menu:

* 字典物件::
* Set Objects::


File: python.info,  Node: 字典物件,  Next: Set Objects,  Up: Container Objects

7.8.4.1 字典物件
................

 -- C 類型: PyDictObject

     *note PyObject: 4bf. 子型態代表一個 Python 字典物件。

 -- C 變數: PyTypeObject PyDict_Type

     *note PyTypeObject: 2d7. 實例代表一個 Python 字典型態。此與 Python
     層中的 *note dict: 1b9. 為同一個物件。

 -- C 函式: int PyDict_Check (PyObject *p)

     若 `p' 是一個字典物件或字典的子型態實例則會回傳 true。

 -- C 函式: int PyDict_CheckExact (PyObject *p)

     若 `p' 是一個字典物件但並不是一個字典子型態的實例，則回傳 true。

 -- C 函式: PyObject* PyDict_New ()
     `Return value: New reference.'  Return a new empty dictionary, or
     ‘NULL’ on failure.

 -- C 函式: PyObject* PyDictProxy_New (PyObject *mapping)
     `Return value: New reference.'  Return a *note
     types.MappingProxyType: abb. 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)

     Empty an existing dictionary of all key-value pairs.

 -- C 函式: int PyDict_Contains (PyObject *p, PyObject *key)

     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 函式: PyObject* PyDict_Copy (PyObject *p)
     `Return value: New reference.'  Return a new dictionary that
     contains the same key-value pairs as `p'.

 -- C 函式: int PyDict_SetItem (PyObject *p, PyObject *key,
          PyObject *val)

     Insert `val' into the dictionary `p' with a key of `key'.  `key'
     must be *note hashable: 142e.; if it isn’t, *note TypeError: 193.
     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)

     Insert `val' into the dictionary `p' using `key' as a key.  `key'
     should be a ‘const char*’.  The key object is created using
     ‘PyUnicode_FromString(key)’.  Return ‘0’ on success or ‘-1’ on
     failure.  This function `does not' steal a reference to `val'.

 -- C 函式: int PyDict_DelItem (PyObject *p, PyObject *key)

     Remove the entry in dictionary `p' with key `key'.  `key' must be
     hashable; if it isn’t, *note TypeError: 193. is raised.  If `key'
     is not in the dictionary, *note KeyError: 2c8. is raised.  Return
     ‘0’ on success or ‘-1’ on failure.

 -- C 函式: int PyDict_DelItemString (PyObject *p, const char *key)

     Remove the entry in dictionary `p' which has a key specified by the
     string `key'.  If `key' is not in the dictionary, *note KeyError:
     2c8. is raised.  Return ‘0’ on success or ‘-1’ on failure.

 -- C 函式: PyObject* PyDict_GetItem (PyObject *p, PyObject *key)
     `Return value: Borrowed reference.'  Return the object from
     dictionary `p' which has a key `key'.  Return ‘NULL’ if the key
     `key' is not present, but `without' setting an exception.

     Note that exceptions which occur while calling *note __hash__():
     345. and *note __eq__(): 344. methods will get suppressed.  To get
     error reporting use *note PyDict_GetItemWithError(): 3e66. instead.

 -- C 函式: PyObject* PyDict_GetItemWithError (PyObject *p,
          PyObject *key)
     `Return value: Borrowed reference.'  Variant of *note
     PyDict_GetItem(): 3b18. 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 函式: PyObject* PyDict_GetItemString (PyObject *p, const
          char *key)
     `Return value: Borrowed reference.'  This is the same as *note
     PyDict_GetItem(): 3b18, but `key' is specified as a ‘const char*’,
     rather than a *note PyObject*: 4bf.

     Note that exceptions which occur while calling *note __hash__():
     345. and *note __eq__(): 344. methods and creating a temporary
     string object will get suppressed.  To get error reporting use
     *note PyDict_GetItemWithError(): 3e66. instead.

 -- C 函式: PyObject* PyDict_SetDefault (PyObject *p, PyObject *key,
          PyObject *defaultobj)
     `Return value: Borrowed reference.'  This is the same as the
     Python-level *note dict.setdefault(): 9c4.  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 函式: PyObject* PyDict_Items (PyObject *p)
     `Return value: New reference.'  Return a *note PyListObject: 3cfd.
     containing all the items from the dictionary.

 -- C 函式: PyObject* PyDict_Keys (PyObject *p)
     `Return value: New reference.'  Return a *note PyListObject: 3cfd.
     containing all the keys from the dictionary.

 -- C 函式: PyObject* PyDict_Values (PyObject *p)
     `Return value: New reference.'  Return a *note PyListObject: 3cfd.
     containing all the values from the dictionary `p'.

 -- C 函式: Py_ssize_t PyDict_Size (PyObject *p)

     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)

     Iterate over all key-value pairs in the dictionary `p'.  The
     ‘Py_ssize_t’ 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*: 4bf. 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.

     For example:

          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);
          }

 -- C 函式: int PyDict_Merge (PyObject *a, PyObject *b, int override)

     Iterate over mapping object `b' adding key-value pairs to
     dictionary `a'.  `b' may be a dictionary, or any object supporting
     *note PyMapping_Keys(): 431. and *note PyObject_GetItem(): 3bac.
     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)

     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(): 3e6e.
     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)

     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_ClearFreeList ()

     Clear the free list.  Return the total number of freed items.

     3.3 版新加入.


File: python.info,  Node: Set Objects,  Prev: 字典物件,  Up: Container Objects

7.8.4.2 Set Objects
...................

This section details the public API for *note set: b74. and *note
frozenset: bf3. objects.  Any functionality not listed below is best
accessed using the either the abstract object protocol (including *note
PyObject_CallMethod(): 3cba, *note PyObject_RichCompareBool(): f4c,
*note PyObject_Hash(): 3cc0, *note PyObject_Repr(): 96d, *note
PyObject_IsTrue(): 3cc1, *note PyObject_Print(): 1051, and *note
PyObject_GetIter(): 3cc8.) or the abstract number protocol (including
*note PyNumber_And(): 3cda, *note PyNumber_Subtract(): 3ccd, *note
PyNumber_Or(): 3cdc, *note PyNumber_Xor(): 3cdb, *note
PyNumber_InPlaceAnd(): 3ce6, *note PyNumber_InPlaceSubtract(): 3cde,
*note PyNumber_InPlaceOr(): 3ce8, and *note PyNumber_InPlaceXor():
3ce7.).

 -- C 類型: PySetObject

     This subtype of *note PyObject: 4bf. is used to hold the internal
     data for both *note set: b74. and *note frozenset: bf3. objects.
     It is like a *note PyDictObject: 3e5b. 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 are subject to change.
     All access should be done through the documented API rather than by
     manipulating the values in the structure.

 -- C 變數: PyTypeObject PySet_Type

     This is an instance of *note PyTypeObject: 2d7. representing the
     Python *note set: b74. type.

 -- C 變數: PyTypeObject PyFrozenSet_Type

     This is an instance of *note PyTypeObject: 2d7. representing the
     Python *note frozenset: bf3. 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: b74. object or an instance of a
     subtype.

 -- C 函式: int PyFrozenSet_Check (PyObject *p)

     Return true if `p' is a *note frozenset: bf3. object or an instance
     of a subtype.

 -- C 函式: int PyAnySet_Check (PyObject *p)

     Return true if `p' is a *note set: b74. object, a *note frozenset:
     bf3. object, or an instance of a subtype.

 -- C 函式: int PyAnySet_CheckExact (PyObject *p)

     Return true if `p' is a *note set: b74. object or a *note
     frozenset: bf3. object but not an instance of a subtype.

 -- C 函式: int PyFrozenSet_CheckExact (PyObject *p)

     Return true if `p' is a *note frozenset: bf3. object but not an
     instance of a subtype.

 -- C 函式: PyObject* PySet_New (PyObject *iterable)
     `Return value: New reference.'  Return a new *note set: b74.
     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: 193. if `iterable' is
     not actually iterable.  The constructor is also useful for copying
     a set (‘c=set(s)’).

 -- C 函式: PyObject* PyFrozenSet_New (PyObject *iterable)
     `Return value: New reference.'  Return a new *note frozenset: bf3.
     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: 193. if
     `iterable' is not actually iterable.

The following functions and macros are available for instances of *note
set: b74. or *note frozenset: bf3. or instances of their subtypes.

 -- C 函式: Py_ssize_t PySet_Size (PyObject *anyset)

     Return the length of a *note set: b74. or *note frozenset: bf3.
     object.  Equivalent to ‘len(anyset)’.  Raises a ‘PyExc_SystemError’
     if `anyset' is not a *note set: b74, *note frozenset: bf3, or an
     instance of a subtype.

 -- C 函式: Py_ssize_t PySet_GET_SIZE (PyObject *anyset)

     Macro form of *note PySet_Size(): db5. without error checking.

 -- C 函式: int PySet_Contains (PyObject *anyset, PyObject *key)

     Return ‘1’ if found, ‘0’ if not found, and ‘-1’ if an error is
     encountered.  Unlike the Python *note __contains__(): d2d. method,
     this function does not automatically convert unhashable sets into
     temporary frozensets.  Raise a *note TypeError: 193. if the `key'
     is unhashable.  Raise ‘PyExc_SystemError’ if `anyset' is not a
     *note set: b74, *note frozenset: bf3, or an instance of a subtype.

 -- C 函式: int PySet_Add (PyObject *set, PyObject *key)

     Add `key' to a *note set: b74. instance.  Also works with *note
     frozenset: bf3. instances (like *note PyTuple_SetItem(): 3b1b. 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: 193. if the `key' is unhashable.
     Raise a *note MemoryError: ef1. if there is no room to grow.  Raise
     a *note SystemError: 600. if `set' is not an instance of *note set:
     b74. or its subtype.

The following functions are available for instances of *note set: b74.
or its subtypes but not for instances of *note frozenset: bf3. or its
subtypes.

 -- C 函式: int PySet_Discard (PyObject *set, PyObject *key)

     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: 2c8. for missing keys.  Raise a *note TypeError: 193. if
     the `key' is unhashable.  Unlike the Python ‘discard()’ method,
     this function does not automatically convert unhashable sets into
     temporary frozensets.  Raise ‘PyExc_SystemError’ if `set' is not an
     instance of *note set: b74. or its subtype.

 -- C 函式: PyObject* PySet_Pop (PyObject *set)
     `Return value: New reference.'  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: 2c8. if
     the set is empty.  Raise a *note SystemError: 600. if `set' is not
     an instance of *note set: b74. or its subtype.

 -- C 函式: int PySet_Clear (PyObject *set)

     Empty an existing set of all elements.

 -- C 函式: int PySet_ClearFreeList ()

     Clear the free list.  Return the total number of freed items.

     3.3 版新加入.


File: python.info,  Node: 函式物件<2>,  Next: Other Objects,  Prev: Container Objects,  Up: Concrete Objects Layer

7.8.5 函式物件
--------------

* Menu:

* 函式（Function）物件::
* 實體方法物件::
* Method Objects: Method Objects<2>.
* Cell 物件::
* Code Objects: Code Objects<2>.


File: python.info,  Node: 函式（Function）物件,  Next: 實體方法物件,  Up: 函式物件<2>

7.8.5.1 函式（Function）物件
............................

這有一些少數Python函數的於具體說明。

 -- C 類型: PyFunctionObject

     The C structure used for functions.

 -- C 變數: PyTypeObject PyFunction_Type

     This is an instance of *note PyTypeObject: 2d7. and represents the
     Python function type.  It is exposed to Python programmers as
     ‘types.FunctionType’.

 -- C 函式: int PyFunction_Check (PyObject *o)

     Return true if `o' is a function object (has type *note
     PyFunction_Type: 3e86.).  The parameter must not be ‘NULL’.

 -- C 函式: PyObject* PyFunction_New (PyObject *code, PyObject *globals)
     `Return value: New reference.'  Return a new function object
     associated with the code object `code'.  `globals' must be a
     dictionary with the global variables accessible to the function.

     The function’s docstring and name are retrieved from the code
     object.  `__module__' is retrieved from `globals'.  The argument
     defaults, annotations and closure are set to ‘NULL’.
     `__qualname__' is set to the same value as the function’s name.

 -- C 函式: PyObject* PyFunction_NewWithQualName (PyObject *code,
          PyObject *globals, PyObject *qualname)
     `Return value: New reference.'  As *note PyFunction_New(): 3e88,
     but also allows setting the function object’s ‘__qualname__’
     attribute.  `qualname' should be a unicode object or ‘NULL’; if
     ‘NULL’, the ‘__qualname__’ attribute is set to the same value as
     its ‘__name__’ attribute.

     3.3 版新加入.

 -- C 函式: PyObject* PyFunction_GetCode (PyObject *op)
     `Return value: Borrowed reference.' 回傳與程式碼物件相關的函數物件
     `op'。

 -- C 函式: PyObject* PyFunction_GetGlobals (PyObject *op)
     `Return value: Borrowed reference.' 回傳與全域函數字典相關的函數物
     件 `op'。

 -- C 函式: PyObject* PyFunction_GetModule (PyObject *op)
     `Return value: Borrowed reference.'  Return the `__module__'
     attribute of the function object `op'.  This is normally a string
     containing the module name, but can be set to any other object by
     Python code.

 -- C 函式: PyObject* PyFunction_GetDefaults (PyObject *op)
     `Return value: Borrowed reference.'  Return the argument default
     values of the function object `op'.  This can be a tuple of
     arguments or ‘NULL’.

 -- C 函式: int PyFunction_SetDefaults (PyObject *op,
          PyObject *defaults)

     Set the argument default values for the function object `op'.
     `defaults' must be ‘Py_None’ or a tuple.

     Raises *note SystemError: 600. and returns ‘-1’ on failure.

 -- C 函式: PyObject* PyFunction_GetClosure (PyObject *op)
     `Return value: Borrowed reference.'  Return the closure associated
     with the function object `op'.  This can be ‘NULL’ or a tuple of
     cell objects.

 -- C 函式: int PyFunction_SetClosure (PyObject *op, PyObject *closure)

     Set the closure associated with the function object `op'.
     `closure' must be ‘Py_None’ or a tuple of cell objects.

     Raises *note SystemError: 600. and returns ‘-1’ on failure.

 -- C 函式: PyObject *PyFunction_GetAnnotations (PyObject *op)
     `Return value: Borrowed reference.'  Return the annotations of the
     function object `op'.  This can be a mutable dictionary or ‘NULL’.

 -- C 函式: int PyFunction_SetAnnotations (PyObject *op,
          PyObject *annotations)

     Set the annotations for the function object `op'.  `annotations'
     must be a dictionary or ‘Py_None’.

     Raises *note SystemError: 600. and returns ‘-1’ on failure.


File: python.info,  Node: 實體方法物件,  Next: Method Objects<2>,  Prev: 函式（Function）物件,  Up: 函式物件<2>

7.8.5.2 實體方法物件
....................

An instance method is a wrapper for a *note PyCFunction: de0. and the
new way to bind a *note PyCFunction: de0. to a class object.  It
replaces the former call ‘PyMethod_New(func, NULL, class)’.

 -- C 變數: PyTypeObject PyInstanceMethod_Type

     This instance of *note PyTypeObject: 2d7. represents the Python
     instance method type.  It is not exposed to Python programs.

 -- C 函式: int PyInstanceMethod_Check (PyObject *o)

     Return true if `o' is an instance method object (has type *note
     PyInstanceMethod_Type: 3e96.).  The parameter must not be ‘NULL’.

 -- C 函式: PyObject* PyInstanceMethod_New (PyObject *func)
     `Return value: New reference.'  Return a new instance method
     object, with `func' being any callable object `func' is the
     function that will be called when the instance method is called.

 -- C 函式: PyObject* PyInstanceMethod_Function (PyObject *im)
     `Return value: Borrowed reference.'  Return the function object
     associated with the instance method `im'.

 -- C 函式: PyObject* PyInstanceMethod_GET_FUNCTION (PyObject *im)
     `Return value: Borrowed reference.'  Macro version of *note
     PyInstanceMethod_Function(): 3e99. which avoids error checking.


File: python.info,  Node: Method Objects<2>,  Next: Cell 物件,  Prev: 實體方法物件,  Up: 函式物件<2>

7.8.5.3 Method Objects
......................

Methods are bound function objects.  Methods are always bound to an
instance of a user-defined class.  Unbound methods (methods bound to a
class object) are no longer available.

 -- C 變數: PyTypeObject PyMethod_Type

     This instance of *note PyTypeObject: 2d7. represents the Python
     method type.  This is exposed to Python programs as
     ‘types.MethodType’.

 -- C 函式: int PyMethod_Check (PyObject *o)

     Return true if `o' is a method object (has type *note
     PyMethod_Type: 3e9d.).  The parameter must not be ‘NULL’.

 -- C 函式: PyObject* PyMethod_New (PyObject *func, PyObject *self)
     `Return value: New reference.'  Return a new method object, with
     `func' being any callable object and `self' the instance the method
     should be bound.  `func' is the function that will be called when
     the method is called.  `self' must not be ‘NULL’.

 -- C 函式: PyObject* PyMethod_Function (PyObject *meth)
     `Return value: Borrowed reference.'  Return the function object
     associated with the method `meth'.

 -- C 函式: PyObject* PyMethod_GET_FUNCTION (PyObject *meth)
     `Return value: Borrowed reference.'  Macro version of *note
     PyMethod_Function(): 3ea0. which avoids error checking.

 -- C 函式: PyObject* PyMethod_Self (PyObject *meth)
     `Return value: Borrowed reference.'  Return the instance associated
     with the method `meth'.

 -- C 函式: PyObject* PyMethod_GET_SELF (PyObject *meth)
     `Return value: Borrowed reference.'  Macro version of *note
     PyMethod_Self(): 3ea2. which avoids error checking.

 -- C 函式: int PyMethod_ClearFreeList ()

     Clear the free list.  Return the total number of freed items.


File: python.info,  Node: Cell 物件,  Next: Code Objects<2>,  Prev: Method Objects<2>,  Up: 函式物件<2>

7.8.5.4 Cell 物件
.................

"Cell" objects are used to implement variables referenced by multiple
scopes.  For each such variable, a cell object is created to store the
value; the local variables of each stack frame that references the value
contains a reference to the cells from outer scopes which also use that
variable.  When the value is accessed, the value contained in the cell
is used instead of the cell object itself.  This de-referencing of the
cell object requires support from the generated byte-code; these are not
automatically de-referenced when accessed.  Cell objects are not likely
to be useful elsewhere.

 -- C 類型: PyCellObject

     C 結構的 cell 物件

 -- C 變數: PyTypeObject PyCell_Type

     對應 cell 物件的物件型別。

 -- C 函式: int PyCell_Check (ob)

     Return true if `ob' is a cell object; `ob' must not be ‘NULL’.

 -- C 函式: PyObject* PyCell_New (PyObject *ob)
     `Return value: New reference.'  Create and return a new cell object
     containing the value `ob'.  The parameter may be ‘NULL’.

 -- C 函式: PyObject* PyCell_Get (PyObject *cell)
     `Return value: New reference.' 回傳 cell 內容中的 `cell'。

 -- C 函式: PyObject* PyCell_GET (PyObject *cell)
     `Return value: Borrowed reference.'  Return the contents of the
     cell `cell', but without checking that `cell' is non-‘NULL’ and a
     cell object.

 -- C 函式: int PyCell_Set (PyObject *cell, PyObject *value)

     Set the contents of the cell object `cell' to `value'.  This
     releases the reference to any current content of the cell.  `value'
     may be ‘NULL’.  `cell' must be non-‘NULL’; if it is not a cell
     object, ‘-1’ will be returned.  On success, ‘0’ will be returned.

 -- C 函式: void PyCell_SET (PyObject *cell, PyObject *value)

     Sets the value of the cell object `cell' to `value'.  No reference
     counts are adjusted, and no checks are made for safety; `cell' must
     be non-‘NULL’ and must be a cell object.


File: python.info,  Node: Code Objects<2>,  Prev: Cell 物件,  Up: 函式物件<2>

7.8.5.5 Code Objects
....................

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 類型: 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 變數: PyTypeObject PyCode_Type

     This is an instance of *note PyTypeObject: 2d7. representing the
     Python *note code: 1b. type.

 -- C 函式: int PyCode_Check (PyObject *co)

     Return true if `co' is a *note code: 1b. object.

 -- C 函式: int PyCode_GetNumFree (PyCodeObject *co)

     Return the number of free variables in `co'.

 -- C 函式: PyCodeObject* PyCode_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, int firstlineno, PyObject *lnotab)
     `Return value: New reference.'  Return a new code object.  If you
     need a dummy code object to create a frame, use *note
     PyCode_NewEmpty(): cef. instead.  Calling *note PyCode_New(): 273.
     directly can bind you to a precise Python version since the
     definition of the bytecode changes often.

 -- C 函式: PyCodeObject* PyCode_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,
          int firstlineno, PyObject *lnotab)
     `Return value: New reference.'  Similar to *note PyCode_New(): 273,
     but with an extra "posonlyargcount" for positional-only arguments.

     3.8 版新加入.

 -- C 函式: PyCodeObject* PyCode_NewEmpty (const char *filename, const
          char *funcname, int firstlineno)
     `Return value: New reference.'  Return a new empty code object with
     the specified filename, function name, and first line number.  It
     is illegal to *note exec(): c49. or *note eval(): b95. the
     resulting code object.


File: python.info,  Node: Other Objects,  Prev: 函式物件<2>,  Up: Concrete Objects Layer

7.8.6 Other Objects
-------------------

* Menu:

* 檔案（File）物件::
* 模組物件模組::
* 迭代器（Iterator）物件::
* 修飾器物件::
* 切片物件::
* Ellipsis Object::
* MemoryView objects::
* 弱參照物件::
* Capsules: Capsules<2>.
* 產生器物件::
* Coroutine Objects: Coroutine Objects<2>.
* Context Variables Objects::
* DateTime 物件::


File: python.info,  Node: 檔案（File）物件,  Next: 模組物件模組,  Up: Other Objects

7.8.6.1 檔案（File）物件
........................

These APIs are a minimal emulation of the Python 2 C API for built-in
file objects, which used to rely on the buffered I/O (‘FILE*’) support
from the C standard library.  In Python 3, files and streams use the new
*note io: a2. module, which defines several layers over the low-level
unbuffered I/O of the operating system.  The functions described below
are convenience C wrappers over these new APIs, and meant mostly for
internal error reporting in the interpreter; third-party code is advised
to access the *note io: a2. APIs instead.

 -- C 函式: PyObject* PyFile_FromFd (int fd, const char *name, const
          char *mode, int buffering, const char *encoding, const
          char *errors, const char *newline, int closefd)
     `Return value: New reference.'  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(): 65f. function documentation.

          警告: Since Python streams have their own buffering layer,
          mixing them with OS-level file descriptors can produce various
          issues (such as unexpected ordering of data).

     3.2 版更變: 忽略 `name' 屬性。

 -- C 函式: int PyObject_AsFileDescriptor (PyObject *p)

     Return the file descriptor associated with `p' as an ‘int’.  If the
     object is an integer, its value is returned.  If not, the object’s
     *note fileno(): 1f0f. method is called if it exists; the method
     must return an integer, which is returned as the file descriptor
     value.  Sets an exception and returns ‘-1’ on failure.

 -- C 函式: PyObject* PyFile_GetLine (PyObject *p, int n)
     `Return value: New reference.'

     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(): 1708. 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: c71. is raised if the end of the file is reached
     immediately.

 -- C 函式: int PyFile_SetOpenCodeHook (Py_OpenCodeHookFunction handler)

     Overrides the normal behavior of *note io.open_code(): f27. to pass
     its parameter through the provided handler.

     The handler is a function of type ‘PyObject *(*)(PyObject *path,
     void *userData)’, where `path' is guaranteed to be *note
     PyUnicodeObject: 3dde.

     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.

     As this hook is intentionally used during import, avoid importing
     new modules during its execution unless they are known to be frozen
     or available in ‘sys.modules’.

     Once a hook has been set, it cannot be removed or replaced, and
     later calls to *note PyFile_SetOpenCodeHook(): 1fec. will fail.  On
     failure, the function returns -1 and sets an exception if the
     interpreter has been initialized.

     This function is safe to call before *note Py_Initialize(): 43e.

     Raises an *note auditing event: e96. ‘setopencodehook’ with no
     arguments.

     3.8 版新加入.

 -- C 函式: int PyFile_WriteObject (PyObject *obj, PyObject *p,
          int flags)

     Write object `obj' to file object `p'.  The only supported flag for
     `flags' is ‘Py_PRINT_RAW’; if given, the *note str(): 335. of the
     object is written instead of the *note repr(): 7d1.  Return ‘0’ on
     success or ‘-1’ on failure; the appropriate exception will be set.

 -- C 函式: int PyFile_WriteString (const char *s, PyObject *p)

     寫入字串 `s' 到 檔案物件 `p'。當成功時回傳 0，而當失敗時回傳 -1，並
     會設定合適的例外狀況。


File: python.info,  Node: 模組物件模組,  Next: 迭代器（Iterator）物件,  Prev: 檔案（File）物件,  Up: Other Objects

7.8.6.2 模組物件模組
....................

 -- C 變數: PyTypeObject PyModule_Type

     This instance of *note PyTypeObject: 2d7. 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.

 -- C 函式: int PyModule_CheckExact (PyObject *p)

     Return true if `p' is a module object, but not a subtype of *note
     PyModule_Type: 3ec3.

 -- C 函式: PyObject* PyModule_NewObject (PyObject *name)
     `Return value: New reference.'

     Return a new module object with the *note __name__: d17. attribute
     set to `name'.  The module’s *note __name__: d17, ‘__doc__’, *note
     __package__: 95a, and *note __loader__: 95b. attributes are filled
     in (all but *note __name__: d17. are set to ‘None’); the caller is
     responsible for providing a *note __file__: ebc. attribute.

     3.3 版新加入.

     3.4 版更變: *note __package__: 95a. and *note __loader__: 95b. are
     set to ‘None’.

 -- C 函式: PyObject* PyModule_New (const char *name)
     `Return value: New reference.'  Similar to *note
     PyModule_NewObject(): 3ec6, but the name is a UTF-8 encoded string
     instead of a Unicode object.

 -- C 函式: PyObject* PyModule_GetDict (PyObject *module)
     `Return value: Borrowed reference.'

     Return the dictionary object that implements `module'’s namespace;
     this object is the same as the *note __dict__: 501. attribute of
     the module object.  If `module' is not a module object (or a
     subtype of a module object), *note SystemError: 600. 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__: 501.

 -- C 函式: PyObject* PyModule_GetNameObject (PyObject *module)
     `Return value: New reference.'

     Return `module'’s *note __name__: d17. value.  If the module does
     not provide one, or if it is not a string, *note SystemError: 600.
     is raised and ‘NULL’ is returned.

     3.3 版新加入.

 -- C 函式: const char* PyModule_GetName (PyObject *module)

     Similar to *note PyModule_GetNameObject(): 3ec9. but return the
     name encoded to ‘'utf-8'’.

 -- C 函式: void* PyModule_GetState (PyObject *module)

     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: 3ecc.

 -- C 函式: PyModuleDef* PyModule_GetDef (PyObject *module)

     Return a pointer to the *note PyModuleDef: 3b42. struct from which
     the module was created, or ‘NULL’ if the module wasn’t created from
     a definition.

 -- C 函式: PyObject* PyModule_GetFilenameObject (PyObject *module)
     `Return value: New reference.'

     Return the name of the file from which `module' was loaded using
     `module'’s *note __file__: ebc. attribute.  If this is not defined,
     or if it is not a unicode string, raise *note SystemError: 600. and
     return ‘NULL’; otherwise return a reference to a Unicode object.

     3.2 版新加入.

 -- C 函式: const char* PyModule_GetFilename (PyObject *module)

     Similar to *note PyModule_GetFilenameObject(): 3ece. but return the
     filename encoded to ’utf-8’.

     3.2 版後已棄用: *note PyModule_GetFilename(): 3ecf. raises
     ‘UnicodeEncodeError’ on unencodable filenames, use *note
     PyModule_GetFilenameObject(): 3ece. instead.

* Menu:

* Initializing C modules::
* Module lookup::


File: python.info,  Node: Initializing C modules,  Next: Module lookup,  Up: 模組物件模組

7.8.6.3 Initializing C modules
..............................

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(): 3b02.).  See *note Building C and C++
Extensions: 3b05. or *note Extending Embedded Python: 3b8c. for details.

The initialization function can either pass a module definition instance
to *note PyModule_Create(): 3b01, and return the resulting module
object, or request "multi-phase initialization" by returning the
definition struct itself.

 -- C 類型: PyModuleDef

     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: f31. is used.

      -- C 成員函數: Py_ssize_t m_size

          Module state may be kept in a per-module memory area that can
          be retrieved with *note PyModule_GetState(): 3ecb, 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 ‘m_free’ 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.

          See PEP 3121(1) for more details.

      -- C 成員函數: PyMethodDef* m_methods

          A pointer to a table of module-level functions, described by
          *note PyMethodDef: e20. values.  Can be ‘NULL’ if no functions
          are present.

      -- C 成員函數: PyModuleDef_Slot* 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 成員函數: inquiry m_reload

      -- C 成員函數: traverseproc m_traverse

          A traversal function to call during GC traversal of the module
          object, or ‘NULL’ if not needed.  This function may be called
          before module state is allocated (*note PyModule_GetState():
          3ecb. may return ‘NULL’), and before the *note Py_mod_exec:
          3ed8. function is executed.

      -- C 成員函數: inquiry m_clear

          A clear function to call during GC clearing of the module
          object, or ‘NULL’ if not needed.  This function may be called
          before module state is allocated (*note PyModule_GetState():
          3ecb. may return ‘NULL’), and before the *note Py_mod_exec:
          3ed8. function is executed.

      -- C 成員函數: freefunc m_free

          A function to call during deallocation of the module object,
          or ‘NULL’ if not needed.  This function may be called before
          module state is allocated (*note PyModule_GetState(): 3ecb.
          may return ‘NULL’), and before the *note Py_mod_exec: 3ed8.
          function is executed.

* Menu:

* Single-phase initialization::
* Multi-phase initialization::
* Low-level module creation functions::
* Support functions::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3121


File: python.info,  Node: Single-phase initialization,  Next: Multi-phase initialization,  Up: Initializing C modules

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 函式: PyObject* PyModule_Create (PyModuleDef *def)
     `Return value: New reference.'  Create a new module object, given
     the definition in `def'.  This behaves like *note
     PyModule_Create2(): 3edc. with `module_api_version' set to
     ‘PYTHON_API_VERSION’.

 -- C 函式: PyObject* PyModule_Create2 (PyModuleDef *def,
          int module_api_version)
     `Return value: New reference.'  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: 2c1. is
     emitted.

          備註: Most uses of this function should be using *note
          PyModule_Create(): 3b01. 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_AddObject(): f83.


File: python.info,  Node: Multi-phase initialization,  Next: Low-level module creation functions,  Prev: Single-phase initialization,  Up: Initializing C modules

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 *note
__new__(): 88e. and *note __init__(): d63. 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(): 3ecb.), or its contents (such as the
module’s *note __dict__: 501. or individual classes created with *note
PyType_FromSpec(): 2d2.).

All modules created using multi-phase initialization are expected to
support *note sub-interpreters: 3c3b.  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: 3b42. instance with
non-empty *note m_slots: 3ed5.  Before it is returned, the ‘PyModuleDef’
instance must be initialized with the following function:

 -- C 函式: PyObject* PyModuleDef_Init (PyModuleDef *def)
     `Return value: Borrowed reference.'  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 類型: 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 函式: PyObject* create_module (PyObject *spec,
               PyModuleDef *def)

     The function receives a *note ModuleSpec: 14cb. 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(): 3ec7.
     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: 3ec3.  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.

See PEP 489(2) for more details on multi-phase initialization.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0451

   (2) https://www.python.org/dev/peps/pep-0489


File: python.info,  Node: Low-level module creation functions,  Next: Support functions,  Prev: Multi-phase initialization,  Up: Initializing C modules

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 函式: PyObject * PyModule_FromDefAndSpec (PyModuleDef *def,
          PyObject *spec)
     `Return value: New reference.'  Create a new module object, given
     the definition in `module' and the ModuleSpec `spec'.  This behaves
     like *note PyModule_FromDefAndSpec2(): 7b1. with
     `module_api_version' set to ‘PYTHON_API_VERSION’.

     3.5 版新加入.

 -- C 函式: PyObject * PyModule_FromDefAndSpec2 (PyModuleDef *def,
          PyObject *spec, int module_api_version)
     `Return value: New reference.'  Create a new module object, given
     the definition in `module' 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:
     2c1. is emitted.

          備註: Most uses of this function should be using *note
          PyModule_FromDefAndSpec(): 7b0. instead; only use this if you
          are sure you need it.

     3.5 版新加入.

 -- C 函式: int PyModule_ExecDef (PyObject *module, PyModuleDef *def)

     Process any execution slots (*note Py_mod_exec: 3ed8.) given in
     `def'.

     3.5 版新加入.

 -- C 函式: int PyModule_SetDocString (PyObject *module, const
          char *docstring)

     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)

     Add the functions from the ‘NULL’ terminated `functions' array to
     `module'.  Refer to the *note PyMethodDef: e20. 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: Support functions,  Prev: Low-level module creation functions,  Up: Initializing C modules

7.8.6.7 Support functions
.........................

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_AddObject (PyObject *module, const char *name,
          PyObject *value)

     Add an object to `module' as `name'.  This is a convenience
     function which can be used from the module’s initialization
     function.  This steals a reference to `value' on success.  Return
     ‘-1’ on error, ‘0’ on success.

          備註: Unlike other functions that steal references,
          ‘PyModule_AddObject()’ only decrements the reference count of
          `value' `on success'.

          This means that its return value must be checked, and calling
          code must *note Py_DECREF(): 267. `value' manually on error.
          Example usage:

               Py_INCREF(spam);
               if (PyModule_AddObject(module, "spam", spam) < 0) {
                   Py_DECREF(module);
                   Py_DECREF(spam);
                   return NULL;
               }

 -- C 函式: int PyModule_AddIntConstant (PyObject *module, const
          char *name, long value)

     Add an integer constant to `module' as `name'.  This convenience
     function can be used from the module’s initialization function.
     Return ‘-1’ on error, ‘0’ on success.

 -- C 函式: int PyModule_AddStringConstant (PyObject *module, const
          char *name, const char *value)

     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’ on
     error, ‘0’ on success.

 -- C 函式: int PyModule_AddIntMacro (PyObject *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’ on error, ‘0’ on success.

 -- C 函式: int PyModule_AddStringMacro (PyObject *module, macro)

     Add a string constant to `module'.


File: python.info,  Node: Module lookup,  Prev: Initializing C modules,  Up: 模組物件模組

7.8.6.8 Module lookup
.....................

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 函式: PyObject* PyState_FindModule (PyModuleDef *def)
     `Return value: Borrowed reference.'  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(): 3eee. 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)

     Attaches the module object passed to the function to the
     interpreter state.  This allows the module object to be accessible
     via *note PyState_FindModule(): 3eed.

     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).

     Return 0 on success or -1 on failure.

     3.3 版新加入.

 -- C 函式: int PyState_RemoveModule (PyModuleDef *def)

     Removes the module object created from `def' from the interpreter
     state.  Return 0 on success or -1 on failure.

     3.3 版新加入.


File: python.info,  Node: 迭代器（Iterator）物件,  Next: 修飾器物件,  Prev: 模組物件模組,  Up: Other Objects

7.8.6.9 迭代器（Iterator）物件
..............................

Python provides two general-purpose iterator objects.  The first, a
sequence iterator, works with an arbitrary sequence supporting the *note
__getitem__(): 27d. method.  The second works with a callable object and
a sentinel value, calling the callable for each item in the sequence,
and ending the iteration when the sentinel value is returned.

 -- C 變數: PyTypeObject PySeqIter_Type

     Type object for iterator objects returned by *note PySeqIter_New():
     3ef4. and the one-argument form of the *note iter(): d2c. built-in
     function for built-in sequence types.

 -- C 函式: int PySeqIter_Check (op)

     Return true if the type of `op' is *note PySeqIter_Type: 3ef3.

 -- C 函式: PyObject* PySeqIter_New (PyObject *seq)
     `Return value: New reference.'  Return an iterator that works with
     a general sequence object, `seq'.  The iteration ends when the
     sequence raises *note IndexError: e7a. for the subscripting
     operation.

 -- C 變數: PyTypeObject PyCallIter_Type

     Type object for iterator objects returned by *note
     PyCallIter_New(): 3ef7. and the two-argument form of the *note
     iter(): d2c. built-in function.

 -- C 函式: int PyCallIter_Check (op)

     Return true if the type of `op' is *note PyCallIter_Type: 3ef6.

 -- C 函式: PyObject* PyCallIter_New (PyObject *callable,
          PyObject *sentinel)
     `Return value: New reference.'  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: 修飾器物件,  Next: 切片物件,  Prev: 迭代器（Iterator）物件,  Up: Other Objects

7.8.6.10 修飾器物件
...................

"Descriptors" are objects that describe some attribute of an object.
They are found in the dictionary of type objects.

 -- C 變數: PyTypeObject PyProperty_Type

     The type object for the built-in descriptor types.

 -- C 函式: PyObject* PyDescr_NewGetSet (PyTypeObject *type, struct
          PyGetSetDef *getset)
     `Return value: New reference.'

 -- C 函式: PyObject* PyDescr_NewMember (PyTypeObject *type, struct
          PyMemberDef *meth)
     `Return value: New reference.'

 -- C 函式: PyObject* PyDescr_NewMethod (PyTypeObject *type, struct
          PyMethodDef *meth)
     `Return value: New reference.'

 -- C 函式: PyObject* PyDescr_NewWrapper (PyTypeObject *type, struct
          wrapperbase *wrapper, void *wrapped)
     `Return value: New reference.'

 -- C 函式: PyObject* PyDescr_NewClassMethod (PyTypeObject *type,
          PyMethodDef *method)
     `Return value: New reference.'

 -- C 函式: int PyDescr_IsData (PyObject *descr)

     Return true if the descriptor objects `descr' describes a data
     attribute, or false if it describes a method.  `descr' must be a
     descriptor object; there is no error checking.

 -- C 函式: PyObject* PyWrapper_New (PyObject *, PyObject *)
     `Return value: New reference.'


File: python.info,  Node: 切片物件,  Next: Ellipsis Object,  Prev: 修飾器物件,  Up: Other Objects

7.8.6.11 切片物件
.................

 -- C 變數: PyTypeObject PySlice_Type

     The type object for slice objects.  This is the same as *note
     slice: e09. in the Python layer.

 -- C 函式: int PySlice_Check (PyObject *ob)

     Return true if `ob' is a slice object; `ob' must not be ‘NULL’.

 -- C 函式: PyObject* PySlice_New (PyObject *start, PyObject *stop,
          PyObject *step)
     `Return value: New reference.'  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’ 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)

     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 *note None: 158. 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)

     Usable replacement for *note PySlice_GetIndices(): 3f09.  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.

     Returns ‘0’ on success and ‘-1’ on error with exception set.

          備註: This function is considered not safe for resizable
          sequences.  Its invocation should be replaced by a combination
          of *note PySlice_Unpack(): 434. and *note
          PySlice_AdjustIndices(): 435. 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)

     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’.

     Return ‘-1’ on error, ‘0’ on success.

     3.6.1 版新加入.

 -- C 函式: Py_ssize_t PySlice_AdjustIndices (Py_ssize_t length,
          Py_ssize_t *start, Py_ssize_t *stop, Py_ssize_t step)

     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 版新加入.


File: python.info,  Node: Ellipsis Object,  Next: MemoryView objects,  Prev: 切片物件,  Up: Other Objects

7.8.6.12 Ellipsis Object
........................

 -- C 變數: PyObject *Py_Ellipsis

     The Python ‘Ellipsis’ object.  This object has no methods.  It
     needs to be treated just like any other object with respect to
     reference counts.  Like *note Py_None: 3afe. it is a singleton
     object.


File: python.info,  Node: MemoryView objects,  Next: 弱參照物件,  Prev: Ellipsis Object,  Up: Other Objects

7.8.6.13 MemoryView objects
...........................

A *note memoryview: 25d. object exposes the C level *note buffer
interface: 15ec. as a Python object which can then be passed around like
any other object.

 -- C 函式: PyObject *PyMemoryView_FromObject (PyObject *obj)
     `Return value: New reference.'  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 函式: PyObject *PyMemoryView_FromMemory (char *mem,
          Py_ssize_t size, int flags)
     `Return value: New reference.'  Create a memoryview object using
     `mem' as the underlying buffer.  `flags' can be one of ‘PyBUF_READ’
     or ‘PyBUF_WRITE’.

     3.3 版新加入.

 -- C 函式: PyObject *PyMemoryView_FromBuffer (Py_buffer *view)
     `Return value: New reference.'  Create a memoryview object wrapping
     the given buffer structure `view'.  For simple byte buffers, *note
     PyMemoryView_FromMemory(): ace. is the preferred function.

 -- C 函式: PyObject *PyMemoryView_GetContiguous (PyObject *obj,
          int buffertype, char order)
     `Return value: New reference.'  Create a memoryview object to a
     *note contiguous: 16ba. 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.

 -- 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: 25d.

 -- C 函式: Py_buffer *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 函式: Py_buffer *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(): ace. or *note
     PyMemoryView_FromBuffer(): 3d1a.  `mview' `must' be a memoryview
     instance.


File: python.info,  Node: 弱參照物件,  Next: Capsules<2>,  Prev: MemoryView objects,  Up: Other Objects

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 (ob)

     Return true if `ob' is either a reference or proxy object.

 -- C 函式: int PyWeakref_CheckRef (ob)

     Return true if `ob' is a reference object.

 -- C 函式: int PyWeakref_CheckProxy (ob)

     Return true if `ob' is a proxy object.

 -- C 函式: PyObject* PyWeakref_NewRef (PyObject *ob,
          PyObject *callback)
     `Return value: New reference.'  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-referencable object, or if
     `callback' is not callable, ‘None’, or ‘NULL’, this will return
     ‘NULL’ and raise *note TypeError: 193.

 -- C 函式: PyObject* PyWeakref_NewProxy (PyObject *ob,
          PyObject *callback)
     `Return value: New reference.'  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-referencable object, or if `callback' is not callable,
     ‘None’, or ‘NULL’, this will return ‘NULL’ and raise *note
     TypeError: 193.

 -- C 函式: PyObject* PyWeakref_GetObject (PyObject *ref)
     `Return value: Borrowed reference.'  Return the referenced object
     from a weak reference, `ref'.  If the referent is no longer live,
     returns ‘Py_None’.

          備註: This function returns a `borrowed reference' to the
          referenced object.  This means that you should always call
          *note Py_INCREF(): 266. on the object except if you know that
          it cannot be destroyed while you are still using it.

 -- C 函式: PyObject* PyWeakref_GET_OBJECT (PyObject *ref)
     `Return value: Borrowed reference.'  Similar to *note
     PyWeakref_GetObject(): 3f1b, but implemented as a macro that does
     no error checking.


File: python.info,  Node: Capsules<2>,  Next: 產生器物件,  Prev: 弱參照物件,  Up: Other Objects

7.8.6.15 Capsules
.................

Refer to *note Providing a C API for an Extension Module: cf6. for more
information on using these objects.

3.1 版新加入.

 -- C 類型: PyCapsule

     This subtype of *note PyObject: 4bf. 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 類型: PyCapsule_Destructor

     The type of a destructor callback for a capsule.  Defined as:

          typedef void (*PyCapsule_Destructor)(PyObject *);

     See *note PyCapsule_New(): 3b26. for the semantics of
     PyCapsule_Destructor callbacks.

 -- C 函式: int PyCapsule_CheckExact (PyObject *p)

     Return true if its argument is a *note PyCapsule: c0c.

 -- C 函式: PyObject* PyCapsule_New (void *pointer, const char *name,
          PyCapsule_Destructor destructor)
     `Return value: New reference.'  Create a *note PyCapsule: c0c.
     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(): 3b27.

 -- C 函式: void* PyCapsule_GetPointer (PyObject *capsule, const
          char *name)

     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 函式: PyCapsule_Destructor PyCapsule_GetDestructor
          (PyObject *capsule)

     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(): cf5. or *note PyErr_Occurred(): 3af9. to
     disambiguate.

 -- C 函式: void* PyCapsule_GetContext (PyObject *capsule)

     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(): cf5. or *note PyErr_Occurred(): 3af9. to
     disambiguate.

 -- C 函式: const char* PyCapsule_GetName (PyObject *capsule)

     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(): cf5. or *note PyErr_Occurred(): 3af9. to
     disambiguate.

 -- C 函式: void* PyCapsule_Import (const char *name, int no_block)

     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.  If `no_block' is true,
     import the module without blocking (using *note
     PyImport_ImportModuleNoBlock(): 9c6.).  If `no_block' is false,
     import the module conventionally (using *note
     PyImport_ImportModule(): c78.).

     Return the capsule’s internal `pointer' on success.  On failure,
     set an exception and return ‘NULL’.

 -- C 函式: int PyCapsule_IsValid (PyObject *capsule, const char *name)

     Determines whether or not `capsule' is a valid capsule.  A valid
     capsule is non-‘NULL’, passes *note PyCapsule_CheckExact(): 3f20,
     has a non-‘NULL’ pointer stored in it, and its internal name
     matches the `name' parameter.  (See *note PyCapsule_GetPointer():
     3f21. for information on how capsule names are compared.)

     In other words, if *note PyCapsule_IsValid(): cf5. 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)

     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)

     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)

     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)

     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: 產生器物件,  Next: Coroutine Objects<2>,  Prev: Capsules<2>,  Up: Other Objects

7.8.6.16 產生器物件
...................

Generator objects are what Python uses to implement generator iterators.
They are normally created by iterating over a function that yields
values, rather than explicitly calling *note PyGen_New(): 3f2c. or *note
PyGen_NewWithQualName(): 3f2d.

 -- C 類型: PyGenObject

     The C structure used for generator objects.

 -- C 變數: PyTypeObject PyGen_Type

     The type object corresponding to generator objects.

 -- C 函式: int PyGen_Check (PyObject *ob)

     Return true if `ob' is a generator object; `ob' must not be ‘NULL’.

 -- C 函式: int PyGen_CheckExact (PyObject *ob)

     Return true if `ob'’s type is *note PyGen_Type: 3f2f.; `ob' must
     not be ‘NULL’.

 -- C 函式: PyObject* PyGen_New (PyFrameObject *frame)
     `Return value: New reference.'  Create and return a new generator
     object based on the `frame' object.  A reference to `frame' is
     stolen by this function.  The argument must not be ‘NULL’.

 -- C 函式: PyObject* PyGen_NewWithQualName (PyFrameObject *frame,
          PyObject *name, PyObject *qualname)
     `Return value: New reference.'  Create and return a new generator
     object based on the `frame' object, with ‘__name__’ and
     ‘__qualname__’ set to `name' and `qualname'.  A reference to
     `frame' is stolen by this function.  The `frame' argument must not
     be ‘NULL’.


File: python.info,  Node: Coroutine Objects<2>,  Next: Context Variables Objects,  Prev: 產生器物件,  Up: Other Objects

7.8.6.17 Coroutine Objects
..........................

3.5 版新加入.

Coroutine objects are what functions declared with an ‘async’ keyword
return.

 -- C 類型: PyCoroObject

     The C structure used for coroutine objects.

 -- C 變數: PyTypeObject PyCoro_Type

     The type object corresponding to coroutine objects.

 -- C 函式: int PyCoro_CheckExact (PyObject *ob)

     Return true if `ob'’s type is *note PyCoro_Type: 3f35.; `ob' must
     not be ‘NULL’.

 -- C 函式: PyObject* PyCoro_New (PyFrameObject *frame, PyObject *name,
          PyObject *qualname)
     `Return value: New reference.'  Create and return a new coroutine
     object based on the `frame' object, with ‘__name__’ and
     ‘__qualname__’ set to `name' and `qualname'.  A reference to
     `frame' is stolen by this function.  The `frame' argument must not
     be ‘NULL’.


File: python.info,  Node: Context Variables Objects,  Next: DateTime 物件,  Prev: Coroutine Objects<2>,  Up: Other Objects

7.8.6.18 Context Variables Objects
..................................

     備註 3.7.1 版更變:: In Python 3.7.1 the signatures of all context
     variables C APIs were `changed' to use *note PyObject: 4bf.
     pointers instead of *note PyContext: 3f3a, *note PyContextVar:
     3f3b, and *note PyContextToken: 3f3c, e.g.:

          // in 3.7.0:
          PyContext *PyContext_New(void);

          // in 3.7.1+:
          PyObject *PyContext_New(void);

     See bpo-34762(1) for more details.

3.7 版新加入.

This section details the public C API for the *note contextvars: 25.
module.

 -- C 類型: PyContext

     The C structure used to represent a *note contextvars.Context:
     24c1. object.

 -- C 類型: PyContextVar

     The C structure used to represent a *note contextvars.ContextVar:
     24bf. object.

 -- C 類型: PyContextToken

     The C structure used to represent a ‘contextvars.Token’ object.

 -- C 變數: PyTypeObject PyContext_Type

     The type object representing the `context' type.

 -- C 變數: PyTypeObject PyContextVar_Type

     The type object representing the `context variable' type.

 -- C 變數: PyTypeObject 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: 3f3d.  `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: 3f3e.  `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: 3f3f.  `o'
     must not be ‘NULL’.  This function always succeeds.

Context object management functions:

 -- C 函式: PyObject *PyContext_New (void)
     `Return value: New reference.'  Create a new empty context object.
     Returns ‘NULL’ if an error has occurred.

 -- C 函式: PyObject *PyContext_Copy (PyObject *ctx)
     `Return value: New reference.'  Create a shallow copy of the passed
     `ctx' context object.  Returns ‘NULL’ if an error has occurred.

 -- C 函式: PyObject *PyContext_CopyCurrent (void)
     `Return value: New reference.'  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.

 -- C 函式: int PyContext_ClearFreeList ()

     Clear the context variable free list.  Return the total number of
     freed items.  This function always succeeds.

Context variable functions:

 -- C 函式: PyObject *PyContextVar_New (const char *name, PyObject *def)
     `Return value: New reference.'  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 函式: PyObject *PyContextVar_Set (PyObject *var, PyObject *value)
     `Return value: New reference.'  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(): 3f4b. that returned the `token'
     was called.  This function returns ‘0’ on success and ‘-1’ on
     error.

   ---------- Footnotes ----------

   (1) https://bugs.python.org/issue34762


File: python.info,  Node: DateTime 物件,  Prev: Context Variables Objects,  Up: Other Objects

7.8.6.19 DateTime 物件
......................

Various date and time objects are supplied by the *note datetime: 31.
module.  Before using any of these functions, the header file
‘datetime.h’ must be included in your source (note that this is not
included by ‘Python.h’), and the macro ‘PyDateTime_IMPORT’ must be
invoked, usually as part of the module initialisation function.  The
macro puts a pointer to a C structure into a static variable,
‘PyDateTimeAPI’, that is used by the following macros.

Macro for access to the UTC singleton:

 -- C 變數: PyObject* PyDateTime_TimeZone_UTC

     Returns the time zone singleton representing UTC, the same object
     as *note datetime.timezone.utc: 18ef.

     3.7 版新加入.

Type-check macros:

 -- C 函式: int PyDate_Check (PyObject *ob)

     Return true if `ob' is of type ‘PyDateTime_DateType’ or a subtype
     of ‘PyDateTime_DateType’.  `ob' must not be ‘NULL’.

 -- C 函式: int PyDate_CheckExact (PyObject *ob)

     Return true if `ob' is of type ‘PyDateTime_DateType’.  `ob' must
     not be ‘NULL’.

 -- C 函式: int PyDateTime_Check (PyObject *ob)

     Return true if `ob' is of type ‘PyDateTime_DateTimeType’ or a
     subtype of ‘PyDateTime_DateTimeType’.  `ob' must not be ‘NULL’.

 -- C 函式: int PyDateTime_CheckExact (PyObject *ob)

     Return true if `ob' is of type ‘PyDateTime_DateTimeType’.  `ob'
     must not be ‘NULL’.

 -- C 函式: int PyTime_Check (PyObject *ob)

     Return true if `ob' is of type ‘PyDateTime_TimeType’ or a subtype
     of ‘PyDateTime_TimeType’.  `ob' must not be ‘NULL’.

 -- C 函式: int PyTime_CheckExact (PyObject *ob)

     Return true if `ob' is of type ‘PyDateTime_TimeType’.  `ob' must
     not be ‘NULL’.

 -- C 函式: int PyDelta_Check (PyObject *ob)

     Return true if `ob' is of type ‘PyDateTime_DeltaType’ or a subtype
     of ‘PyDateTime_DeltaType’.  `ob' must not be ‘NULL’.

 -- C 函式: int PyDelta_CheckExact (PyObject *ob)

     Return true if `ob' is of type ‘PyDateTime_DeltaType’.  `ob' must
     not be ‘NULL’.

 -- C 函式: int PyTZInfo_Check (PyObject *ob)

     Return true if `ob' is of type ‘PyDateTime_TZInfoType’ or a subtype
     of ‘PyDateTime_TZInfoType’.  `ob' must not be ‘NULL’.

 -- C 函式: int PyTZInfo_CheckExact (PyObject *ob)

     Return true if `ob' is of type ‘PyDateTime_TZInfoType’.  `ob' must
     not be ‘NULL’.

Macros to create objects:

 -- C 函式: PyObject* PyDate_FromDate (int year, int month, int day)
     `Return value: New reference.'  Return a *note datetime.date: 194.
     object with the specified year, month and day.

 -- C 函式: PyObject* PyDateTime_FromDateAndTime (int year, int month,
          int day, int hour, int minute, int second, int usecond)
     `Return value: New reference.'  Return a *note datetime.datetime:
     195. object with the specified year, month, day, hour, minute,
     second and microsecond.

 -- C 函式: PyObject* PyDateTime_FromDateAndTimeAndFold (int year,
          int month, int day, int hour, int minute, int second,
          int usecond, int fold)
     `Return value: New reference.'  Return a *note datetime.datetime:
     195. object with the specified year, month, day, hour, minute,
     second, microsecond and fold.

     3.6 版新加入.

 -- C 函式: PyObject* PyTime_FromTime (int hour, int minute, int second,
          int usecond)
     `Return value: New reference.'  Return a *note datetime.time: 4f8.
     object with the specified hour, minute, second and microsecond.

 -- C 函式: PyObject* PyTime_FromTimeAndFold (int hour, int minute,
          int second, int usecond, int fold)
     `Return value: New reference.'  Return a *note datetime.time: 4f8.
     object with the specified hour, minute, second, microsecond and
     fold.

     3.6 版新加入.

 -- C 函式: PyObject* PyDelta_FromDSU (int days, int seconds,
          int useconds)
     `Return value: New reference.'  Return a *note datetime.timedelta:
     196. object representing the given number of days, seconds and
     microseconds.  Normalization is performed so that the resulting
     number of microseconds and seconds lie in the ranges documented for
     *note datetime.timedelta: 196. objects.

 -- C 函式: PyObject* PyTimeZone_FromOffset
          (PyDateTime_DeltaType* offset)
     `Return value: New reference.'  Return a *note datetime.timezone:
     a06. object with an unnamed fixed offset represented by the
     `offset' argument.

     3.7 版新加入.

 -- C 函式: PyObject* PyTimeZone_FromOffsetAndName
          (PyDateTime_DeltaType* offset, PyUnicode* name)
     `Return value: New reference.'  Return a *note datetime.timezone:
     a06. object with a fixed offset represented by the `offset'
     argument and with tzname `name'.

     3.7 版新加入.

Macros to extract fields from date objects.  The argument must be an
instance of ‘PyDateTime_Date’, including subclasses (such as
‘PyDateTime_DateTime’).  The argument must not be ‘NULL’, and the type
is not checked:

 -- 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。

Macros to extract fields from datetime objects.  The argument must be an
instance of ‘PyDateTime_DateTime’, including subclasses.  The argument
must not be ‘NULL’, and the type is not checked:

 -- 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。

Macros to extract fields from time objects.  The argument must be an
instance of ‘PyDateTime_Time’, including subclasses.  The argument must
not be ‘NULL’, and the type is not checked:

 -- 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。

Macros to extract fields from time delta objects.  The argument must be
an instance of ‘PyDateTime_Delta’, including subclasses.  The argument
must not be ‘NULL’, and the type is not checked:

 -- C 函式: int PyDateTime_DELTA_GET_DAYS (PyDateTime_Delta *o)

     Return the number of days, as an int from -999999999 to 999999999.

     3.3 版新加入.

 -- C 函式: int PyDateTime_DELTA_GET_SECONDS (PyDateTime_Delta *o)

     Return the number of seconds, as an int from 0 through 86399.

     3.3 版新加入.

 -- C 函式: int PyDateTime_DELTA_GET_MICROSECONDS (PyDateTime_Delta *o)

     Return the number of microseconds, as an int from 0 through 999999.

     3.3 版新加入.

Macros for the convenience of modules implementing the DB API:

 -- C 函式: PyObject* PyDateTime_FromTimestamp (PyObject *args)
     `Return value: New reference.'  Create and return a new *note
     datetime.datetime: 195. object given an argument tuple suitable for
     passing to *note datetime.datetime.fromtimestamp(): 1090.

 -- C 函式: PyObject* PyDate_FromTimestamp (PyObject *args)
     `Return value: New reference.'  Create and return a new *note
     datetime.date: 194. object given an argument tuple suitable for
     passing to *note datetime.date.fromtimestamp(): 18ae.


File: python.info,  Node: Initialization Finalization and Threads,  Next: Python Initialization Configuration,  Prev: Concrete Objects Layer,  Up: Python / C API 參考手冊

7.9 Initialization, Finalization, and Threads
=============================================

See also *note Python Initialization Configuration: 17e.

* Menu:

* Before Python Initialization::
* 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::
* Advanced Debugger Support::
* Thread Local Storage Support::


File: python.info,  Node: Before Python Initialization,  Next: Global configuration variables,  Up: Initialization Finalization and Threads

7.9.1 Before Python Initialization
----------------------------------

In an application embedding Python, the *note Py_Initialize(): 43e.
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: 3f73.

The following functions can be safely called before Python is
initialized:

   * Configuration functions:

        * *note PyImport_AppendInittab(): 3b02.

        * *note PyImport_ExtendInittab(): 3c65.

        * ‘PyInitFrozenExtensions()’

        * *note PyMem_SetAllocator(): 3f74.

        * *note PyMem_SetupDebugHooks(): 50f.

        * *note PyObject_SetArenaAllocator(): 3f75.

        * *note Py_SetPath(): 274.

        * *note Py_SetProgramName(): f8e.

        * *note Py_SetPythonHome(): f8d.

        * *note Py_SetStandardStreamEncoding(): 92a.

        * *note PySys_AddWarnOption(): 4b8.

        * *note PySys_AddXOption(): 3c4c.

        * *note PySys_ResetWarnOptions(): 3c45.

   * Informative functions:

        * *note Py_IsInitialized(): 3bb7.

        * *note PyMem_GetAllocator(): 3f76.

        * *note PyObject_GetArenaAllocator(): 3f77.

        * *note Py_GetBuildInfo(): d9f.

        * *note Py_GetCompiler(): 3f78.

        * *note Py_GetCopyright(): 3f79.

        * *note Py_GetPlatform(): 3f7a.

        * *note Py_GetVersion(): 3f7b.

   * Utilities:

        * *note Py_DecodeLocale(): 441.

   * Memory allocators:

        * *note PyMem_RawMalloc(): 972.

        * *note PyMem_RawRealloc(): 973.

        * *note PyMem_RawCalloc(): 7aa.

        * *note PyMem_RawFree(): 3c3f.

     備註: The following functions `should not be called' before *note
     Py_Initialize(): 43e.: *note Py_EncodeLocale(): 442, *note
     Py_GetPath(): 3bb4, *note Py_GetPrefix(): 3bb5, *note
     Py_GetExecPrefix(): 3bb6, *note Py_GetProgramFullPath(): 276, *note
     Py_GetPythonHome(): 3f7c, *note Py_GetProgramName(): 277. and *note
     PyEval_InitThreads(): c17.


File: python.info,  Node: Global configuration variables,  Next: Initializing and finalizing the interpreter,  Prev: Before Python Initialization,  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: 133f.

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: 4b9. to 1 and ‘-bb’ sets *note Py_BytesWarningFlag:
4b9. to 2.

 -- C 變數: int Py_BytesWarningFlag

     Issue a warning when comparing *note bytes: 336. or *note
     bytearray: 337. with *note str: 335. or *note bytes: 336. with
     *note int: 185.  Issue an error if greater or equal to ‘2’.

     Set by the *note -b: 41a. option.

 -- C 變數: int Py_DebugFlag

     Turn on parser debugging output (for expert only, depending on
     compilation options).

     Set by the *note -d: 1347. option and the *note PYTHONDEBUG: 1348.
     environment variable.

 -- C 變數: int Py_DontWriteBytecodeFlag

     If set to non-zero, Python won’t try to write ‘.pyc’ files on the
     import of source modules.

     Set by the *note -B: d3d. option and the *note
     PYTHONDONTWRITEBYTECODE: d3e. environment variable.

 -- C 變數: int Py_FrozenFlag

     Suppress error messages when calculating the module search path in
     *note Py_GetPath(): 3bb4.

     Private flag used by ‘_freeze_importlib’ and ‘frozenmain’ programs.

 -- C 變數: int Py_HashRandomizationFlag

     Set to ‘1’ if the *note PYTHONHASHSEED: 9ca. environment variable
     is set to a non-empty string.

     If the flag is non-zero, read the *note PYTHONHASHSEED: 9ca.
     environment variable to initialize the secret hash seed.

 -- C 變數: int Py_IgnoreEnvironmentFlag

     Ignore all ‘PYTHON*’ environment variables, e.g.  *note PYTHONPATH:
     958. and *note PYTHONHOME: 4db, that might be set.

     Set by the *note -E: 100e. and *note -I: 100d. options.

 -- C 變數: int Py_InspectFlag

     When a script is passed as first argument or the *note -c: 1210.
     option is used, enter interactive mode after executing the script
     or the command, even when *note sys.stdin: 312. does not appear to
     be a terminal.

     Set by the *note -i: e24. option and the *note PYTHONINSPECT: e23.
     environment variable.

 -- C 變數: int Py_InteractiveFlag

     Set by the *note -i: e24. option.

 -- C 變數: int Py_IsolatedFlag

     Run Python in isolated mode.  In isolated mode *note sys.path: 48d.
     contains neither the script’s directory nor the user’s
     site-packages directory.

     Set by the *note -I: 100d. option.

     3.4 版新加入.

 -- C 變數: int Py_LegacyWindowsFSEncodingFlag

     If the flag is non-zero, use the ‘mbcs’ encoding instead of the
     UTF-8 encoding for the filesystem encoding.

     Set to ‘1’ if the *note PYTHONLEGACYWINDOWSFSENCODING: 4fc.
     environment variable is set to a non-empty string.

     See PEP 529(1) for more details.

     *note Availability: 1364.: Windows.

 -- C 變數: int Py_LegacyWindowsStdioFlag

     If the flag is non-zero, use *note io.FileIO: ca9. instead of
     ‘WindowsConsoleIO’ for *note sys: fe. standard streams.

     Set to ‘1’ if the *note PYTHONLEGACYWINDOWSSTDIO: 4ff. environment
     variable is set to a non-empty string.

     See PEP 528(2) for more details.

     *note Availability: 1364.: Windows.

 -- C 變數: int Py_NoSiteFlag

     Disable the import of the module *note site: ec. and the
     site-dependent manipulations of *note sys.path: 48d. that it
     entails.  Also disable these manipulations if *note site: ec. is
     explicitly imported later (call *note site.main(): 134c. if you
     want them to be triggered).

     Set by the *note -S: b29. option.

 -- C 變數: int Py_NoUserSiteDirectory

     Don’t add the *note user site-packages directory: 134b. to *note
     sys.path: 48d.

     Set by the *note -s: d1a. and *note -I: 100d. options, and the
     *note PYTHONNOUSERSITE: d1b. environment variable.

 -- C 變數: int Py_OptimizeFlag

     Set by the *note -O: 690. option and the *note PYTHONOPTIMIZE:
     1349. environment variable.

 -- C 變數: int Py_QuietFlag

     Don’t display the copyright and version messages even in
     interactive mode.

     Set by the *note -q: 134a. option.

     3.2 版新加入.

 -- C 變數: int Py_UnbufferedStdioFlag

     Force the stdout and stderr streams to be unbuffered.

     Set by the *note -u: 134d. option and the *note PYTHONUNBUFFERED:
     134e. environment variable.

 -- C 變數: int Py_VerboseFlag

     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.

     Set by the *note -v: d8d. option and the *note PYTHONVERBOSE: 134f.
     environment variable.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0529

   (2) https://www.python.org/dev/peps/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 ()

     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: 43f. for the few
     exceptions.

     This initializes the table of loaded modules (‘sys.modules’), and
     creates the fundamental modules *note builtins: 13, *note __main__:
     1. and *note sys: fe.  It also initializes the module search path
     (‘sys.path’).  It does not set ‘sys.argv’; use *note
     PySys_SetArgvEx(): bff. for that.  This is a no-op when called for
     a second time (without calling *note Py_FinalizeEx(): 5ce. first).
     There is no return value; it is a fatal error if the initialization
     fails.

          備註: 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)

     This function works like *note Py_Initialize(): 43e. if `initsigs'
     is ‘1’.  If `initsigs' is ‘0’, it skips initialization registration
     of signal handlers, which might be useful when Python is embedded.

 -- C 函式: int Py_IsInitialized ()

     Return true (nonzero) when the Python interpreter has been
     initialized, false (zero) if not.  After *note Py_FinalizeEx():
     5ce. is called, this returns false until *note Py_Initialize():
     43e. is called again.

 -- C 函式: int Py_FinalizeEx ()

     Undo all initializations made by *note Py_Initialize(): 43e. and
     subsequent use of Python/C API functions, and destroy all
     sub-interpreters (see *note Py_NewInterpreter(): 3f8c. below) that
     were created and not yet destroyed since the last call to *note
     Py_Initialize(): 43e.  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(): 43e. again first).
     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__(): 924. 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(): 43e. and
     *note Py_FinalizeEx(): 5ce. more than once.

     Raises an *note auditing event: e96.
     ‘cpython._PySys_ClearAuditHooks’ with no arguments.

     3.6 版新加入.

 -- C 函式: void Py_Finalize ()

     This is a backwards-compatible version of *note Py_FinalizeEx():
     5ce. 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 函式: int Py_SetStandardStreamEncoding (const char *encoding,
          const char *errors)

     This function should be called before *note Py_Initialize(): 43e,
     if it is called at all.  It specifies which encoding and error
     handling to use with standard IO, with the same meanings as in
     *note str.encode(): c3c.

     It overrides *note PYTHONIOENCODING: 934. values, and allows
     embedding code to control IO encoding when the environment variable
     does not work.

     `encoding' and/or `errors' may be ‘NULL’ to use *note
     PYTHONIOENCODING: 934. and/or default values (depending on other
     settings).

     Note that *note sys.stderr: 314. always uses the "backslashreplace"
     error handler, regardless of this (or any other) setting.

     If *note Py_FinalizeEx(): 5ce. is called, this function will need
     to be called again in order to affect subsequent calls to *note
     Py_Initialize(): 43e.

     Returns ‘0’ if successful, a nonzero value on error (e.g.  calling
     after the interpreter has already been initialized).

     3.4 版新加入.

 -- C 函式: void Py_SetProgramName (const wchar_t *name)

     This function should be called before *note Py_Initialize(): 43e.
     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(): 3bb4. 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(): 441. to decode a bytes string to get a
     ‘wchar_*’ string.

 -- C 函式: wchar* Py_GetProgramName ()

     Return the program name set with *note Py_SetProgramName(): f8e, or
     the default.  The returned string points into static storage; the
     caller should not modify its value.

 -- C 函式: wchar_t* Py_GetPrefix ()

     Return the `prefix' for installed platform-independent files.  This
     is derived through a number of complicated rules from the program
     name set with *note Py_SetProgramName(): f8e. 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 ‘--prefix’ 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.

 -- C 函式: wchar_t* Py_GetExecPrefix ()

     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 Py_SetProgramName(): f8e. 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.

 -- C 函式: wchar_t* Py_GetProgramFullPath ()

     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 Py_SetProgramName(): f8e.
     above).  The returned string points into static storage; the caller
     should not modify its value.  The value is available to Python code
     as ‘sys.executable’.

 -- C 函式: wchar_t* Py_GetPath ()

     Return the default module search path; this is computed from the
     program name (set by *note Py_SetProgramName(): f8e. above) 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
     Mac OS X, ‘';'’ on Windows.  The returned string points into static
     storage; the caller should not modify its value.  The list *note
     sys.path: 48d. is initialized with this value on interpreter
     startup; it can be (and usually is) modified later to change the
     search path for loading modules.

 -- C 函式: void Py_SetPath (const wchar_t *)

     Set the default module search path.  If this function is called
     before *note Py_Initialize(): 43e, then *note Py_GetPath(): 3bb4.
     won’t attempt to compute a default search path but uses the one
     provided instead.  This is useful if Python is embedded by an
     application that has full knowledge of the location of all modules.
     The path components should be separated by the platform dependent
     delimiter character, which is ‘':'’ on Unix and Mac OS X, ‘';'’ on
     Windows.

     This also causes *note sys.executable: 275. to be set to the
     program full path (see *note Py_GetProgramFullPath(): 276.) and for
     *note sys.prefix: 35fa. and *note sys.exec_prefix: 35fb. to be
     empty.  It is up to the caller to modify these if required after
     calling *note Py_Initialize(): 43e.

     Use *note Py_DecodeLocale(): 441. to decode a bytes string to get a
     ‘wchar_*’ string.

     The path argument is copied internally, so the caller may free it
     after the call completes.

     3.8 版更變: The program full path is now used for *note
     sys.executable: 275, instead of the program name.

 -- C 函式: const char* Py_GetVersion ()

     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 three 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: 5d8.

 -- C 函式: const char* Py_GetPlatform ()

     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 Mac OS X, 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 ()

     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 ()

     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 ()

     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)

     Set *note sys.argv: c00. 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: c00, a fatal condition is
     signalled using *note Py_FatalError(): f8f.

     If `updatepath' is zero, this is all the function does.  If
     `updatepath' is non-zero, the function also modifies *note
     sys.path: 48d. 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: 48d.

        - 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: 48d, which is the same as prepending the
          current working directory (‘"."’).

     Use *note Py_DecodeLocale(): 441. to decode a bytes string to get a
     ‘wchar_*’ string.

          備註: 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: 48d.
          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: 48d. element after
          having called *note PySys_SetArgv(): cf1, for example using:

               PyRun_SimpleString("import sys; sys.path.pop(0)\n");

     3.1.3 版新加入.

 -- C 函式: void PySys_SetArgv (int argc, wchar_t **argv)

     This function works like *note PySys_SetArgvEx(): bff. with
     `updatepath' set to ‘1’ unless the ‘python’ interpreter was started
     with the *note -I: 100d.

     Use *note Py_DecodeLocale(): 441. to decode a bytes string to get a
     ‘wchar_*’ string.

     3.4 版更變: The `updatepath' value depends on *note -I: 100d.

 -- C 函式: void Py_SetPythonHome (const wchar_t *home)

     Set the default "home" directory, that is, the location of the
     standard Python libraries.  See *note PYTHONHOME: 4db. 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(): 441. to decode a bytes string to get a
     ‘wchar_*’ string.

 -- C 函式: w_char* Py_GetPythonHome ()

     Return the default "home", that is, the value set by a previous
     call to *note Py_SetPythonHome(): f8d, or the value of the *note
     PYTHONHOME: 4db. environment variable if it is set.

   ---------- 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: 50b. or *note GIL: bef, 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: bef. 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(): bf0.).  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: 3f90.
There’s also one global variable pointing to the current *note
PyThreadState: 3f90.: it can be retrieved using *note
PyThreadState_Get(): 3f91.

* Menu:

* Releasing the GIL from extension code::
* Non-Python created threads::
* Cautions about fork(): Cautions about fork.
* High-level API::
* Low-level 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: bef. 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: 3b20. macro opens a new block and
declares a hidden local variable; the *note Py_END_ALLOW_THREADS: 2b6.
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: 145.
     and *note hashlib: 8d. 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: 10a. 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(): 2b7. and *note PyGILState_Release():
3f95. 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(): 43e.).
Python supports the creation of additional interpreters (using *note
Py_NewInterpreter(): 3f8c.), but mixing multiple interpreters and the
‘PyGILState_*()’ API is unsupported.


File: python.info,  Node: Cautions about fork,  Next: High-level 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(): 966. by acquiring the locks it uses internally before the
fork, and releasing them afterwards.  In addition, it resets any *note
Lock Objects: 2367. 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(): 966. (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(): 2ce. 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():
966. does.  This means finalizing all other *note PyThreadState: 3f90.
objects belonging to the current interpreter and all other *note
PyInterpreterState: 2c3. objects.  Due to this and the special nature of
the *note "main" interpreter: 3c3b, ‘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: High-level API,  Next: Low-level API,  Prev: Cautions about fork,  Up: Thread State and the Global Interpreter Lock

7.9.5.4 High-level API
......................

These are the most commonly used types and functions when writing C
extension code, or when embedding the Python interpreter:

 -- C 類型: PyInterpreterState

     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 類型: PyThreadState

     This data structure represents the state of a single thread.  The
     only public data member is ‘interp’ (*note PyInterpreterState *:
     2c3.), which points to this thread’s interpreter state.

 -- C 函式: void PyEval_InitThreads ()

     Initialize and acquire the global interpreter lock.  It should be
     called in the main thread before creating a second thread or
     engaging in any other thread operations such as
     ‘PyEval_ReleaseThread(tstate)’.  It is not needed before calling
     *note PyEval_SaveThread(): c16. or *note PyEval_RestoreThread():
     2b5.

     This is a no-op when called for a second time.

     3.7 版更變: This function is now called by *note Py_Initialize():
     43e, so you don’t have to call it yourself anymore.

     3.2 版更變: This function cannot be called before *note
     Py_Initialize(): 43e. anymore.

 -- C 函式: int PyEval_ThreadsInitialized ()

     Returns a non-zero value if *note PyEval_InitThreads(): c17. has
     been called.  This function can be called without holding the GIL,
     and therefore can be used to avoid calls to the locking API when
     running single-threaded.

     3.7 版更變: The *note GIL: bef. is now initialized by *note
     Py_Initialize(): 43e.

 -- C 函式: PyThreadState* PyEval_SaveThread ()

     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)

     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 ‘_Py_IsFinalizing()’ or
          *note sys.is_finalizing(): 767. to check if the interpreter is
          in process of being finalized before calling this function to
          avoid unwanted termination.

 -- C 函式: PyThreadState* PyThreadState_Get ()

     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’).

 -- C 函式: PyThreadState* PyThreadState_Swap (PyThreadState *tstate)

     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 ()

     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(): 3f95.  In general, other thread-related APIs
     may be used between *note PyGILState_Ensure(): 2b7. and *note
     PyGILState_Release(): 3f95. 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: 3b20. and *note
     Py_END_ALLOW_THREADS: 2b6. macros is acceptable.

     The return value is an opaque "handle" to the thread state when
     *note PyGILState_Ensure(): 2b7. was called, and must be passed to
     *note PyGILState_Release(): 3f95. 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():
     2b7. must save the handle for its call to *note
     PyGILState_Release(): 3f95.

     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 ‘_Py_IsFinalizing()’ or
          *note sys.is_finalizing(): 767. 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)

     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(): 2b7. call (but generally
     this state will be unknown to the caller, hence the use of the
     GILState API).

     Every call to *note PyGILState_Ensure(): 2b7. must be matched by a
     call to *note PyGILState_Release(): 3f95. on the same thread.

 -- C 函式: PyThreadState* PyGILState_GetThisThreadState ()

     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

     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: 2b6.
     macro.  See above for further discussion of this macro.

 -- C 巨集: Py_END_ALLOW_THREADS

     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: 3b20. macro.  See above for further
     discussion of this macro.

 -- C 巨集: Py_BLOCK_THREADS

     This macro expands to ‘PyEval_RestoreThread(_save);’: it is
     equivalent to *note Py_END_ALLOW_THREADS: 2b6. without the closing
     brace.

 -- C 巨集: Py_UNBLOCK_THREADS

     This macro expands to ‘_save = PyEval_SaveThread();’: it is
     equivalent to *note Py_BEGIN_ALLOW_THREADS: 3b20. without the
     opening brace and variable declaration.


File: python.info,  Node: Low-level API,  Prev: High-level API,  Up: Thread State and the Global Interpreter Lock

7.9.5.5 Low-level API
.....................

All of the following functions must be called after *note
Py_Initialize(): 43e.

3.7 版更變: *note Py_Initialize(): 43e. now initializes the *note GIL:
bef.

 -- C 函式: PyInterpreterState* PyInterpreterState_New ()

     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.

     Raises an *note auditing event: e96.
     ‘cpython.PyInterpreterState_New’ with no arguments.

 -- C 函式: void PyInterpreterState_Clear (PyInterpreterState *interp)

     Reset all information in an interpreter state object.  The global
     interpreter lock must be held.

     Raises an *note auditing event: e96.
     ‘cpython.PyInterpreterState_Clear’ with no arguments.

 -- C 函式: void PyInterpreterState_Delete (PyInterpreterState *interp)

     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(): 34c9.

 -- C 函式: PyThreadState* PyThreadState_New
          (PyInterpreterState *interp)

     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)

     Reset all information in a thread state object.  The global
     interpreter lock must be held.

 -- C 函式: void PyThreadState_Delete (PyThreadState *tstate)

     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(): f24.

 -- C 函式: PY_INT64_T PyInterpreterState_GetID
          (PyInterpreterState *interp)

     Return the interpreter’s unique ID. If there was any error in doing
     so then ‘-1’ is returned and an error is set.

     3.7 版新加入.

 -- C 函式: PyObject* PyInterpreterState_GetDict
          (PyInterpreterState *interp)

     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(): 3ecb,
     which extensions should use to store interpreter-specific state
     information.

     3.8 版新加入.

 -- C 函式: PyObject* PyThreadState_GetDict ()
     `Return value: Borrowed reference.'  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)

     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)

     Acquire the global interpreter lock and set the current thread
     state to `tstate', which should 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 ‘_Py_IsFinalizing()’ or
          *note sys.is_finalizing(): 767. 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(): 2b5, *note Py_END_ALLOW_THREADS(): 2b6, and
     *note PyGILState_Ensure(): 2b7, and terminate the current thread if
     called while the interpreter is finalizing.

     *note PyEval_RestoreThread(): 2b5. is a higher-level function which
     is always available (even when threads have not been initialized).

 -- C 函式: void PyEval_ReleaseThread (PyThreadState *tstate)

     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(): c16. is a higher-level function which is
     always available (even when threads have not been initialized).

 -- C 函式: void PyEval_AcquireLock ()

     Acquire the global interpreter lock.  The lock must have been
     created earlier.  If this thread already has the lock, a deadlock
     ensues.

     3.2 版後已棄用: This function does not update the current thread
     state.  Please use *note PyEval_RestoreThread(): 2b5. or *note
     PyEval_AcquireThread(): 2b4. instead.

          備註: 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 ‘_Py_IsFinalizing()’ or
          *note sys.is_finalizing(): 767. 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(): 2b5, *note Py_END_ALLOW_THREADS(): 2b6, and
     *note PyGILState_Ensure(): 2b7, and terminate the current thread if
     called while the interpreter is finalizing.

 -- C 函式: void PyEval_ReleaseLock ()

     Release the global interpreter lock.  The lock must have been
     created earlier.

     3.2 版後已棄用: This function does not update the current thread
     state.  Please use *note PyEval_SaveThread(): c16. or *note
     PyEval_ReleaseThread(): 3fa3. instead.


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(): 3fa5. function returns a pointer to its
state.

You can switch between sub-interpreters using the *note
PyThreadState_Swap(): 3f98. function.  You can create and destroy them
using the following functions:

 -- C 函式: PyThreadState* Py_NewInterpreter ()

     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: 13,
     *note __main__: 1. and *note sys: fe.  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 return value points 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, ‘NULL’ is returned; 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;
     however, unlike most other Python/C API functions, there needn’t be
     a current thread state on entry.)

     Extension modules are shared between (sub-)interpreters as follows:

        * For modules using multi-phase initialization, e.g.  *note
          PyModule_FromDefAndSpec(): 7b0, 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(): 3b01, 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: 3fa6. 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():
          5ce. and *note Py_Initialize(): 43e.; 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 函式: void Py_EndInterpreter (PyThreadState *tstate)

     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
     must be held before calling this function and is still held when it
     returns.)  *note Py_FinalizeEx(): 5ce. will destroy all
     sub-interpreters that haven’t been explicitly destroyed at that
     point.

* Menu:

* Bugs and caveats::


File: python.info,  Node: Bugs and caveats,  Up: Sub-interpreter support

7.9.6.1 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(): 3d7. 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():
2b7. and *note PyGILState_Release(): 3f95. calls.  Furthermore,
extensions (such as *note ctypes: 2b.) 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)

     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: 619. boundary;

        * with the main thread holding the *note global interpreter
          lock: 50b. (`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.

          警告: 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: 3f93.

     3.1 版新加入.


File: python.info,  Node: Profiling and Tracing,  Next: Advanced Debugger Support,  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 類型: int (*Py_tracefunc) (PyObject *obj, PyFrameObject *frame,
          int what, PyObject *arg)

     The type of the trace function registered using *note
     PyEval_SetProfile(): e40. and *note PyEval_SetTrace(): e41.  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 ‘PyTrace_CALL’, ‘PyTrace_EXCEPTION’,
     ‘PyTrace_LINE’, ‘PyTrace_RETURN’, ‘PyTrace_C_CALL’,
     ‘PyTrace_C_EXCEPTION’, ‘PyTrace_C_RETURN’, or ‘PyTrace_OPCODE’, and
     `arg' depends on the value of `what':

     Value of `what'                    Meaning of `arg'
                                        
     --------------------------------------------------------------------------------
                                        
     ‘PyTrace_CALL’                     Always *note Py_None: 3afe.
                                        
                                        
     ‘PyTrace_EXCEPTION’                Exception information as returned by
                                        *note sys.exc_info(): c64.
                                        
                                        
     ‘PyTrace_LINE’                     Always *note Py_None: 3afe.
                                        
                                        
     ‘PyTrace_RETURN’                   Value being returned to the caller, or
                                        ‘NULL’ if caused by an exception.
                                        
                                        
     ‘PyTrace_C_CALL’                   Function object being called.
                                        
                                        
     ‘PyTrace_C_EXCEPTION’              Function object being called.
                                        
                                        
     ‘PyTrace_C_RETURN’                 Function object being called.
                                        
                                        
     ‘PyTrace_OPCODE’                   Always *note Py_None: 3afe.
                                        

 -- C 變數: int PyTrace_CALL

     The value of the `what' parameter to a *note Py_tracefunc: 3fab.
     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: 3fab.
     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:
     3fab. function (but not a profiling function) when a line-number
     event is being reported.  It may be disabled for a frame by setting
     ‘f_trace_lines’ to `0' on that frame.

 -- C 變數: int PyTrace_RETURN

     The value for the `what' parameter to *note Py_tracefunc: 3fab.
     functions when a call is about to return.

 -- C 變數: int PyTrace_C_CALL

     The value for the `what' parameter to *note Py_tracefunc: 3fab.
     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: 3fab.
     functions when a C function has raised an exception.

 -- C 變數: int PyTrace_C_RETURN

     The value for the `what' parameter to *note Py_tracefunc: 3fab.
     functions when a C function has returned.

 -- C 變數: int PyTrace_OPCODE

     The value for the `what' parameter to *note Py_tracefunc: 3fab.
     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 ‘f_trace_opcodes’ 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 ‘PyTrace_LINE’
     ‘PyTrace_OPCODE’ and ‘PyTrace_EXCEPTION’.

 -- C 函式: void PyEval_SetTrace (Py_tracefunc func, PyObject *obj)

     Set the tracing function to `func'.  This is similar to *note
     PyEval_SetProfile(): e40, 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(): e41. will not
     receive ‘PyTrace_C_CALL’, ‘PyTrace_C_EXCEPTION’ or
     ‘PyTrace_C_RETURN’ as a value for the `what' parameter.


File: python.info,  Node: Advanced Debugger Support,  Next: Thread Local Storage Support,  Prev: Profiling and Tracing,  Up: Initialization Finalization and Threads

7.9.9 Advanced Debugger Support
-------------------------------

These functions are only intended to be used by advanced debugging
tools.

 -- C 函式: PyInterpreterState* PyInterpreterState_Head ()

     Return the interpreter state object at the head of the list of all
     such objects.

 -- C 函式: PyInterpreterState* PyInterpreterState_Main ()

     Return the main interpreter state object.

 -- C 函式: PyInterpreterState* PyInterpreterState_Next
          (PyInterpreterState *interp)

     Return the next interpreter state object after `interp' from the
     list of all such objects.

 -- C 函式: PyThreadState * PyInterpreterState_ThreadHead
          (PyInterpreterState *interp)

     Return the pointer to the first *note PyThreadState: 3f90. object
     in the list of threads associated with the interpreter `interp'.

 -- C 函式: PyThreadState* 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:
     2c3. object.


File: python.info,  Node: Thread Local Storage Support,  Prev: Advanced Debugger Support,  Up: Initialization Finalization and Threads

7.9.10 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: 22f8.).  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*:
     4bf, 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.10.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: 31d. instead of ‘int’ to represent thread keys.

3.7 版新加入.

也參考
......

"A New C-API for Thread-Local Storage in CPython" ( PEP 539(1))

 -- C 類型: 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: 3bbb. is not defined, static allocation
     of this type by *note Py_tss_NEEDS_INIT: 3fb9. is allowed.

 -- C 巨集: Py_tss_NEEDS_INIT

     This macro expands to the initializer for *note Py_tss_t: 31d.
     variables.  Note that this macro won’t be defined with *note
     Py_LIMITED_API: 3bbb.

* Menu:

* Dynamic Allocation::
* Methods: Methods<4>.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0539


File: python.info,  Node: Dynamic Allocation,  Next: Methods<4>,  Up: Thread Specific Storage TSS API

7.9.10.2 Dynamic Allocation
...........................

Dynamic allocation of the *note Py_tss_t: 31d, required in extension
modules built with *note Py_LIMITED_API: 3bbb, where static allocation
of this type is not possible due to its implementation being opaque at
build time.

 -- C 函式: Py_tss_t* PyThread_tss_alloc ()

     Return a value which is the same state as a value initialized with
     *note Py_tss_NEEDS_INIT: 3fb9, or ‘NULL’ in the case of dynamic
     allocation failure.

 -- C 函式: void PyThread_tss_free (Py_tss_t *key)

     Free the given `key' allocated by *note PyThread_tss_alloc(): 3fbb,
     after first calling *note PyThread_tss_delete(): 3fbd. 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: Methods<4>,  Prev: Dynamic Allocation,  Up: Thread Specific Storage TSS API

7.9.10.3 Methods
................

The parameter `key' of these functions must not be ‘NULL’.  Moreover,
the behaviors of *note PyThread_tss_set(): 3fbf. and *note
PyThread_tss_get(): 3fc0. are undefined if the given *note Py_tss_t:
31d. has not been initialized by *note PyThread_tss_create(): 3fc1.

 -- C 函式: int PyThread_tss_is_created (Py_tss_t *key)

     Return a non-zero value if the given *note Py_tss_t: 31d. has been
     initialized by *note PyThread_tss_create(): 3fc1.

 -- C 函式: int PyThread_tss_create (Py_tss_t *key)

     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: 3fb9.  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)

     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(): 3fc1.  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)

     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)

     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.10.4 Thread Local Storage (TLS) API
.......................................

3.7 版後已棄用: This API is superseded by *note Thread Specific Storage
(TSS) API: 31c.

     備註: 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(): 3fc4. 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 ()

 -- C 函式: void PyThread_delete_key (int key)

 -- C 函式: int PyThread_set_key_value (int key, void *value)

 -- C 函式: void* PyThread_get_key_value (int key)

 -- C 函式: void PyThread_delete_key_value (int key)

 -- C 函式: void PyThread_ReInitTLS ()


File: python.info,  Node: Python Initialization Configuration,  Next: 記憶體管理,  Prev: Initialization Finalization and Threads,  Up: Python / C API 參考手冊

7.10 Python Initialization Configuration
========================================

3.8 版新加入.

Structures:

   * *note PyConfig: 160.

   * *note PyPreConfig: 161.

   * *note PyStatus: 162.

   * *note PyWideStringList: 163.

Functions:

   * *note PyConfig_Clear(): 164.

   * *note PyConfig_InitIsolatedConfig(): 165.

   * *note PyConfig_InitPythonConfig(): 166.

   * *note PyConfig_Read(): 167.

   * *note PyConfig_SetArgv(): 168.

   * *note PyConfig_SetBytesArgv(): 169.

   * *note PyConfig_SetBytesString(): 16a.

   * *note PyConfig_SetString(): 16b.

   * *note PyConfig_SetWideStringList(): 3fcb.

   * *note PyPreConfig_InitIsolatedConfig(): 16c.

   * *note PyPreConfig_InitPythonConfig(): 16d.

   * *note PyStatus_Error(): 16e.

   * *note PyStatus_Exception(): 16f.

   * *note PyStatus_Exit(): 170.

   * *note PyStatus_IsError(): 171.

   * *note PyStatus_IsExit(): 172.

   * *note PyStatus_NoMemory(): 173.

   * *note PyStatus_Ok(): 174.

   * *note PyWideStringList_Append(): 175.

   * *note PyWideStringList_Insert(): 176.

   * *note Py_ExitStatusException(): 178.

   * *note Py_InitializeFromConfig(): 179.

   * *note Py_PreInitialize(): 17a.

   * *note Py_PreInitializeFromArgs(): 17b.

   * *note Py_PreInitializeFromBytesArgs(): 17c.

   * *note Py_RunMain(): 17d.

The preconfiguration (‘PyPreConfig’ type) is stored in
‘_PyRuntime.preconfig’ and the configuration (‘PyConfig’ type) is stored
in ‘PyInterpreterState.config’.

See also *note Initialization, Finalization, and Threads: 3f70.

也參考
......

PEP 587(1) "Python Initialization Configuration".

* Menu:

* PyWideStringList::
* PyStatus::
* PyPreConfig::
* Preinitialization with PyPreConfig::
* PyConfig::
* Initialization with PyConfig::
* Isolated Configuration::
* Python Configuration::
* Path Configuration::
* Py_RunMain(): Py_RunMain.
* Multi-Phase Initialization Private Provisional API::

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0587


File: python.info,  Node: PyWideStringList,  Next: PyStatus,  Up: Python Initialization Configuration

7.10.1 PyWideStringList
-----------------------

 -- C 類型: PyWideStringList

     List of ‘wchar_t*’ strings.

     If `length' is non-zero, `items' must be non-‘NULL’ and all strings
     must be non-‘NULL’.

     Methods:

      -- C 函式: PyStatus PyWideStringList_Append
               (PyWideStringList *list, const wchar_t *item)

          Append `item' to `list'.

          Python must be preinitialized to call this function.

      -- C 函式: PyStatus 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 成員函數: Py_ssize_t length

          List length.

      -- C 成員函數: wchar_t** items

          List items.


File: python.info,  Node: PyStatus,  Next: PyPreConfig,  Prev: PyWideStringList,  Up: Python Initialization Configuration

7.10.2 PyStatus
---------------

 -- C 類型: 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

          Error message.

      -- C 成員函數: const char *func

          Name of the function which created an error, can be ‘NULL’.

     Functions to create a status:

      -- C 函式: PyStatus PyStatus_Ok (void)

          Success.

      -- C 函式: PyStatus PyStatus_Error (const char *err_msg)

          Initialization error with a message.

      -- C 函式: PyStatus PyStatus_NoMemory (void)

          Memory allocation failure (out of memory).

      -- C 函式: PyStatus 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():
          178. 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’.

Example:

     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: Preinitialization with PyPreConfig,  Prev: PyStatus,  Up: Python Initialization Configuration

7.10.3 PyPreConfig
------------------

 -- C 類型: PyPreConfig

     Structure used to preinitialize Python:

        * Set the Python memory allocator

        * Configure the LC_CTYPE locale

        * Set the UTF-8 mode

     Function to initialize a preconfiguration:

      -- C 函式: void PyPreConfig_InitPythonConfig
               (PyPreConfig *preconfig)

          Initialize the preconfiguration with *note Python
          Configuration: 3fd4.

      -- C 函式: void PyPreConfig_InitIsolatedConfig
               (PyPreConfig *preconfig)

          Initialize the preconfiguration with *note Isolated
          Configuration: 3fd5.

     Structure fields:

      -- C 成員函數: int allocator

          Name of the memory allocator:

             * ‘PYMEM_ALLOCATOR_NOT_SET’ (‘0’): don’t change memory
               allocators (use defaults)

             * ‘PYMEM_ALLOCATOR_DEFAULT’ (‘1’): default memory
               allocators

             * ‘PYMEM_ALLOCATOR_DEBUG’ (‘2’): default memory allocators
               with debug hooks

             * ‘PYMEM_ALLOCATOR_MALLOC’ (‘3’): force usage of ‘malloc()’

             * ‘PYMEM_ALLOCATOR_MALLOC_DEBUG’ (‘4’): force usage of
               ‘malloc()’ with debug hooks

             * ‘PYMEM_ALLOCATOR_PYMALLOC’ (‘5’): *note Python pymalloc
               memory allocator: 5c6.

             * ‘PYMEM_ALLOCATOR_PYMALLOC_DEBUG’ (‘6’): *note Python
               pymalloc memory allocator: 5c6. with debug hooks

          ‘PYMEM_ALLOCATOR_PYMALLOC’ and
          ‘PYMEM_ALLOCATOR_PYMALLOC_DEBUG’ are not supported if Python
          is configured using ‘--without-pymalloc’

          See *note Memory Management: 3fd7.

      -- C 成員函數: int configure_locale

          Set the LC_CTYPE locale to the user preferred locale?  If
          equals to 0, set ‘coerce_c_locale’ and ‘coerce_c_locale_warn’
          to 0.

      -- 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.

      -- C 成員函數: int coerce_c_locale_warn

          If non-zero, emit a warning if the C locale is coerced.

      -- C 成員函數: int dev_mode

          See *note PyConfig.dev_mode: 3fdc.

      -- C 成員函數: int isolated

          See *note PyConfig.isolated: 3fde.

      -- C 成員函數: int legacy_windows_fs_encoding (Windows only)

          If non-zero, disable UTF-8 Mode, set the Python filesystem
          encoding to ‘mbcs’, set the filesystem error handler to
          ‘replace’.

          Only available on Windows.  ‘#ifdef MS_WINDOWS’ macro can be
          used for Windows specific code.

      -- C 成員函數: int parse_argv

          If non-zero, *note Py_PreInitializeFromArgs(): 17b. and *note
          Py_PreInitializeFromBytesArgs(): 17c. parse their ‘argv’
          argument the same way the regular Python parses command line
          arguments: see *note Command Line Arguments: 930.

      -- C 成員函數: int use_environment

          See *note PyConfig.use_environment: 3fe2.

      -- C 成員函數: int utf8_mode

          If non-zero, enable the UTF-8 mode.


File: python.info,  Node: Preinitialization with PyPreConfig,  Next: PyConfig,  Prev: PyPreConfig,  Up: Python Initialization Configuration

7.10.4 Preinitialization with PyPreConfig
-----------------------------------------

Functions to preinitialize Python:

 -- C 函式: PyStatus Py_PreInitialize (const PyPreConfig *preconfig)

     Preinitialize Python from `preconfig' preconfiguration.

 -- C 函式: PyStatus Py_PreInitializeFromBytesArgs (const
          PyPreConfig *preconfig, int argc, char * const *argv)

     Preinitialize Python from `preconfig' preconfiguration and command
     line arguments (bytes strings).

 -- C 函式: PyStatus Py_PreInitializeFromArgs (const
          PyPreConfig *preconfig, int argc, wchar_t * const * argv)

     Preinitialize Python from `preconfig' preconfiguration and command
     line arguments (wide strings).

The caller is responsible to handle exceptions (error or exit) using
*note PyStatus_Exception(): 16f. and *note Py_ExitStatusException():
178.

For *note Python Configuration: 3fd4. (*note
PyPreConfig_InitPythonConfig(): 16d.), 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: 156.
command line option enables the UTF-8 Mode.

‘PyMem_SetAllocator()’ can be called after *note Py_PreInitialize():
17a. and before *note Py_InitializeFromConfig(): 179. to install a
custom memory allocator.  It can be called before *note
Py_PreInitialize(): 17a. if *note PyPreConfig.allocator: 3fd6. is set to
‘PYMEM_ALLOCATOR_NOT_SET’.

Python memory allocation functions like *note PyMem_RawMalloc(): 972.
must not be used before Python preinitialization, whereas calling
directly ‘malloc()’ and ‘free()’ is always safe.  *note
Py_DecodeLocale(): 441. must not be called before the preinitialization.

Example using the preinitialization to enable the UTF-8 Mode:

     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 will speak UTF-8 */

     Py_Initialize();
     /* ... use Python API here ... */
     Py_Finalize();


File: python.info,  Node: PyConfig,  Next: Initialization with PyConfig,  Prev: Preinitialization with PyPreConfig,  Up: Python Initialization Configuration

7.10.5 PyConfig
---------------

 -- C 類型: PyConfig

     Structure containing most parameters to configure Python.

     Structure methods:

      -- C 函式: void PyConfig_InitPythonConfig (PyConfig *config)

          Initialize configuration with *note Python Configuration:
          3fd4.

      -- C 函式: void PyConfig_InitIsolatedConfig (PyConfig *config)

          Initialize configuration with *note Isolated Configuration:
          3fd5.

      -- C 函式: PyStatus PyConfig_SetString (PyConfig *config, wchar_t
               * const *config_str, const wchar_t *str)

          Copy the wide character string `str' into ‘*config_str’.

          Preinitialize Python if needed.

      -- C 函式: PyStatus PyConfig_SetBytesString (PyConfig *config,
               wchar_t * const *config_str, const char *str)

          Decode `str' using ‘Py_DecodeLocale()’ and set the result into
          ‘*config_str’.

          Preinitialize Python if needed.

      -- C 函式: PyStatus PyConfig_SetArgv (PyConfig *config, int argc,
               wchar_t * const *argv)

          Set command line arguments from wide character strings.

          Preinitialize Python if needed.

      -- C 函式: PyStatus PyConfig_SetBytesArgv (PyConfig *config,
               int argc, char * const *argv)

          Set command line arguments: decode bytes using *note
          Py_DecodeLocale(): 441.

          Preinitialize Python if needed.

      -- C 函式: PyStatus PyConfig_SetWideStringList (PyConfig *config,
               PyWideStringList *list, Py_ssize_t length,
               wchar_t **items)

          Set the list of wide strings `list' to `length' and `items'.

          Preinitialize Python if needed.

      -- C 函式: PyStatus PyConfig_Read (PyConfig *config)

          Read all Python configuration.

          Fields which are already initialized are left unchanged.

          Preinitialize Python if needed.

      -- C 函式: void PyConfig_Clear (PyConfig *config)

          Release configuration memory.

     Most ‘PyConfig’ methods preinitialize Python if needed.  In that
     case, the Python preinitialization configuration in based on the
     *note PyConfig: 160.  If configuration fields which are in common
     with *note PyPreConfig: 161. are tuned, they must be set before
     calling a *note PyConfig: 160. method:

        * *note dev_mode: 3fdc.

        * *note isolated: 3fde.

        * *note parse_argv: 3fe6.

        * *note use_environment: 3fe2.

     Moreover, if *note PyConfig_SetArgv(): 168. or *note
     PyConfig_SetBytesArgv(): 169. is used, this method must be called
     first, before other methods, since the preinitialization
     configuration depends on command line arguments (if ‘parse_argv’ 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 成員函數: PyWideStringList argv

          Command line arguments, *note sys.argv: c00.  See *note
          parse_argv: 3fe6. to parse *note argv: 3fe7. the same way the
          regular Python parses Python command line arguments.  If *note
          argv: 3fe7. is empty, an empty string is added to ensure that
          *note sys.argv: c00. always exists and is never empty.

      -- C 成員函數: wchar_t* base_exec_prefix

          *note sys.base_exec_prefix: 35fc.

      -- C 成員函數: wchar_t* base_executable

          ‘sys._base_executable’: ‘__PYVENV_LAUNCHER__’ environment
          variable value, or copy of *note PyConfig.executable: 3fea.

      -- C 成員函數: wchar_t* base_prefix

          *note sys.base_prefix: 3045.

      -- C 成員函數: int buffered_stdio

          If equals to 0, enable unbuffered mode, making the stdout and
          stderr streams unbuffered.

          stdin is always opened in buffered mode.

      -- C 成員函數: int bytes_warning

          If equals to 1, issue a warning when comparing *note bytes:
          336. or *note bytearray: 337. with *note str: 335, or
          comparing *note bytes: 336. with *note int: 185.  If equal or
          greater to 2, raise a *note BytesWarning: 4ba. exception.

      -- C 成員函數: wchar_t* check_hash_pycs_mode

          Control the validation behavior of hash-based ‘.pyc’ files
          (see PEP 552(1)): *note –check-hash-based-pycs: 1346. command
          line option value.

          Valid values: ‘always’, ‘never’ and ‘default’.

          The default value is: ‘default’.

      -- C 成員函數: int configure_c_stdio

          If non-zero, configure C standard streams (‘stdio’, ‘stdout’,
          ‘stdout’).  For example, set their mode to ‘O_BINARY’ on
          Windows.

      -- C 成員函數: int dev_mode

          Development mode: see *note -X dev: 156.

      -- C 成員函數: int dump_refs

          If non-zero, dump all objects which are still alive at exit.

          Require a debug build of Python (‘Py_REF_DEBUG’ macro must be
          defined).

      -- C 成員函數: wchar_t* exec_prefix

          *note sys.exec_prefix: 35fb.

      -- C 成員函數: wchar_t* executable

          *note sys.executable: 275.

      -- C 成員函數: int faulthandler

          If non-zero, call *note faulthandler.enable(): 54d. at
          startup.

      -- C 成員函數: wchar_t* filesystem_encoding

          Filesystem encoding, *note sys.getfilesystemencoding(): 4fb.

      -- C 成員函數: wchar_t* filesystem_errors

          Filesystem encoding errors, *note
          sys.getfilesystemencodeerrors(): 599.

      -- C 成員函數: unsigned long hash_seed

      -- C 成員函數: int use_hash_seed

          Randomized hash function seed.

          If *note use_hash_seed: 3ff6. is zero, a seed is chosen
          randomly at Pythonstartup, and *note hash_seed: 3ff5. is
          ignored.

      -- C 成員函數: wchar_t* home

          Python home directory.

          Initialized from *note PYTHONHOME: 4db. environment variable
          value by default.

      -- C 成員函數: int import_time

          If non-zero, profile import time.

      -- C 成員函數: int inspect

          Enter interactive mode after executing a script or a command.

      -- C 成員函數: int install_signal_handlers

          Install signal handlers?

      -- C 成員函數: int interactive

          Interactive mode.

      -- C 成員函數: int isolated

          If greater than 0, enable isolated mode:

             * *note sys.path: 48d. contains neither the script’s
               directory (computed from ‘argv[0]’ or the current
               directory) nor the user’s site-packages directory.

             * Python REPL doesn’t import *note readline: df. nor enable
               default readline configuration on interactive prompts.

             * Set *note use_environment: 3fe2. and *note
               user_site_directory: 3ffb. to 0.

      -- C 成員函數: int legacy_windows_stdio

          If non-zero, use *note io.FileIO: ca9. instead of
          ‘io.WindowsConsoleIO’ for *note sys.stdin: 312, *note
          sys.stdout: 313. and *note sys.stderr: 314.

          Only available on Windows.  ‘#ifdef MS_WINDOWS’ macro can be
          used for Windows specific code.

      -- C 成員函數: int malloc_stats

          If non-zero, dump statistics on *note Python pymalloc memory
          allocator: 5c6. at exit.

          The option is ignored if Python is built using
          ‘--without-pymalloc’.

      -- C 成員函數: wchar_t* pythonpath_env

          Module search paths as a string separated by ‘DELIM’
          (‘os.path.pathsep’).

          Initialized from *note PYTHONPATH: 958. environment variable
          value by default.

      -- C 成員函數: PyWideStringList module_search_paths

      -- C 成員函數: int module_search_paths_set

          *note sys.path: 48d.  If *note module_search_paths_set: 4000.
          is equal to 0, the *note module_search_paths: 3fff. is
          overridden by the function calculating the *note Path
          Configuration: 4001.

      -- C 成員函數: int optimization_level

          Compilation optimization level:

             * 0: Peephole optimizer (and ‘__debug__’ is set to ‘True’)

             * 1: Remove assertions, set ‘__debug__’ to ‘False’

             * 2: Strip docstrings

      -- C 成員函數: int parse_argv

          If non-zero, parse *note argv: 3fe7. the same way the regular
          Python command line arguments, and strip Python arguments from
          *note argv: 3fe7.: see *note Command Line Arguments: 930.

      -- C 成員函數: int parser_debug

          If non-zero, turn on parser debugging output (for expert only,
          depending on compilation options).

      -- C 成員函數: int pathconfig_warnings

          If equal to 0, suppress warnings when calculating the *note
          Path Configuration: 4001. (Unix only, Windows does not log any
          warning).  Otherwise, warnings are written into ‘stderr’.

      -- C 成員函數: wchar_t* prefix

          *note sys.prefix: 35fa.

      -- C 成員函數: wchar_t* program_name

          Program name.  Used to initialize *note executable: 3fea, and
          in early error messages.

      -- C 成員函數: wchar_t* pycache_prefix

          *note sys.pycache_prefix: 157.: ‘.pyc’ cache prefix.

          If ‘NULL’, *note sys.pycache_prefix: 157. is set to ‘None’.

      -- C 成員函數: int quiet

          Quiet mode.  For example, don’t display the copyright and
          version messages in interactive mode.

      -- C 成員函數: wchar_t* run_command

          ‘python3 -c COMMAND’ argument.  Used by *note Py_RunMain():
          17d.

      -- C 成員函數: wchar_t* run_filename

          ‘python3 FILENAME’ argument.  Used by *note Py_RunMain(): 17d.

      -- C 成員函數: wchar_t* run_module

          ‘python3 -m MODULE’ argument.  Used by *note Py_RunMain():
          17d.

      -- C 成員函數: int show_alloc_count

          Show allocation counts at exit?

          Set to 1 by *note -X showalloccount: 156. command line option.

          Need a special Python build with ‘COUNT_ALLOCS’ macro defined.

      -- C 成員函數: int show_ref_count

          Show total reference count at exit?

          Set to 1 by *note -X showrefcount: 156. command line option.

          Need a debug build of Python (‘Py_REF_DEBUG’ macro must be
          defined).

      -- C 成員函數: int site_import

          Import the *note site: ec. module at startup?

      -- C 成員函數: int skip_source_first_line

          Skip the first line of the source?

      -- C 成員函數: wchar_t* stdio_encoding

      -- C 成員函數: wchar_t* stdio_errors

          Encoding and encoding errors of *note sys.stdin: 312, *note
          sys.stdout: 313. and *note sys.stderr: 314.

      -- C 成員函數: int tracemalloc

          If non-zero, call *note tracemalloc.start(): 1354. at startup.

      -- C 成員函數: int use_environment

          If greater than 0, use *note environment variables: 1359.

      -- C 成員函數: int user_site_directory

          If non-zero, add user site directory to *note sys.path: 48d.

      -- C 成員函數: int verbose

          If non-zero, enable verbose mode.

      -- C 成員函數: PyWideStringList warnoptions

          *note sys.warnoptions: 41b.: options of the *note warnings:
          127. module to build warnings filters: lowest to highest
          priority.

          The *note warnings: 127. module adds *note sys.warnoptions:
          41b. in the reverse order: the last *note
          PyConfig.warnoptions: 4014. item becomes the first item of
          ‘warnings.filters’ which is checked first (highest priority).

      -- C 成員函數: int write_bytecode

          If non-zero, write ‘.pyc’ files.

          *note sys.dont_write_bytecode: 3629. is initialized to the
          inverted value of *note write_bytecode: 4015.

      -- C 成員函數: PyWideStringList xoptions

          *note sys._xoptions: 1356.

If ‘parse_argv’ is non-zero, ‘argv’ arguments are parsed the same way
the regular Python parses command line arguments, and Python arguments
are stripped from ‘argv’: see *note Command Line Arguments: 930.

The ‘xoptions’ options are parsed to set other options: see *note -X:
156. option.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0552


File: python.info,  Node: Initialization with PyConfig,  Next: Isolated Configuration,  Prev: PyConfig,  Up: Python Initialization Configuration

7.10.6 Initialization with PyConfig
-----------------------------------

Function to initialize Python:

 -- C 函式: PyStatus Py_InitializeFromConfig (const PyConfig *config)

     Initialize Python from `config' configuration.

The caller is responsible to handle exceptions (error or exit) using
*note PyStatus_Exception(): 16f. and *note Py_ExitStatusException():
178.

If ‘PyImport_FrozenModules’, ‘PyImport_AppendInittab()’ or
‘PyImport_ExtendInittab()’ are used, they must be set or called after
Python preinitialization and before the Python initialization.

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 fail;
         }

         status = Py_InitializeFromConfig(&config);
         if (PyStatus_Exception(status)) {
             goto fail;
         }
         PyConfig_Clear(&config);
         return;

     fail:
         PyConfig_Clear(&config);
         Py_ExitStatusException(status);
     }

More complete example modifying the default configuration, read the
configuration, and then override some parameters:

     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;
         }

         /* Append our custom search path to sys.path */
         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 Initialization Configuration

7.10.7 Isolated Configuration
-----------------------------

*note PyPreConfig_InitIsolatedConfig(): 16c. and *note
PyConfig_InitIsolatedConfig(): 165. functions create a configuration to
isolate Python from the system.  For example, to embed Python into an
application.

This configuration ignores global configuration variables, environments
variables, command line arguments (*note PyConfig.argv: 3fe7. 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.  Set the
*note Path Configuration: 4001. ("output fields") to ignore these
configuration files and avoid the function computing the default path
configuration.


File: python.info,  Node: Python Configuration,  Next: Path Configuration,  Prev: Isolated Configuration,  Up: Python Initialization Configuration

7.10.8 Python Configuration
---------------------------

*note PyPreConfig_InitPythonConfig(): 16d. and *note
PyConfig_InitPythonConfig(): 166. 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 UTF-8 Mode (
PEP 540(2)) depending on the LC_CTYPE locale, *note PYTHONUTF8: 316. and
*note PYTHONCOERCECLOCALE: 311. environment variables.

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 fail;
         }

         status = Py_InitializeFromConfig(&config);
         if (PyStatus_Exception(status)) {
             goto fail;
         }
         PyConfig_Clear(&config);

         return Py_RunMain();

     fail:
         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);
     }

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0538

   (2) https://www.python.org/dev/peps/pep-0540


File: python.info,  Node: Path Configuration,  Next: Py_RunMain,  Prev: Python Configuration,  Up: Python Initialization Configuration

7.10.9 Path Configuration
-------------------------

*note PyConfig: 160. contains multiple fields for the path
configuration:

   * Path configuration inputs:

        * *note PyConfig.home: 3ff7.

        * *note PyConfig.pathconfig_warnings: 4004.

        * *note PyConfig.program_name: 4006.

        * *note PyConfig.pythonpath_env: 3ffe.

        * current working directory: to get absolute paths

        * ‘PATH’ environment variable to get the program full path (from
          *note PyConfig.program_name: 4006.)

        * ‘__PYVENV_LAUNCHER__’ environment variable

        * (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: 3fe8.

        * *note PyConfig.base_executable: 3fe9.

        * *note PyConfig.base_prefix: 3feb.

        * *note PyConfig.exec_prefix: 3ff1.

        * *note PyConfig.executable: 3fea.

        * *note PyConfig.module_search_paths_set: 4000, *note
          PyConfig.module_search_paths: 3fff.

        * *note PyConfig.prefix: 4005.

If at least one "output field" is not set, Python calculates the path
configuration to fill unset fields.  If *note module_search_paths_set:
4000. is equal to 0, *note module_search_paths: 3fff. is overridden and
*note module_search_paths_set: 4000. 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, path configuration
input fields are ignored as well.

Set *note pathconfig_warnings: 4004. to 0 to suppress warnings when
calculating the path configuration (Unix only, Windows does not log any
warning).

If *note base_prefix: 3feb. or *note base_exec_prefix: 3fe8. fields are
not set, they inherit their value from *note prefix: 4005. and *note
exec_prefix: 3ff1. respectively.

*note Py_RunMain(): 17d. and *note Py_Main(): 4bc. modify *note
sys.path: 48d.:

   * If *note run_filename: 400a. is set and is a directory which
     contains a ‘__main__.py’ script, prepend *note run_filename: 400a.
     to *note sys.path: 48d.

   * If *note isolated: 3fde. is zero:

        * If *note run_module: 400b. is set, prepend the current
          directory to *note sys.path: 48d.  Do nothing if the current
          directory cannot be read.

        * If *note run_filename: 400a. is set, prepend the directory of
          the filename to *note sys.path: 48d.

        * Otherwise, prepend an empty string to *note sys.path: 48d.

If *note site_import: 400e. is non-zero, *note sys.path: 48d. can be
modified by the *note site: ec. module.  If *note user_site_directory:
3ffb. is non-zero and the user’s site-package directory exists, the
*note site: ec. module appends the user’s site-package directory to
*note sys.path: 48d.

The following configuration files are used by the path configuration:

   * ‘pyvenv.cfg’

   * ‘python._pth’ (Windows only)

   * ‘pybuilddir.txt’ (Unix only)

The ‘__PYVENV_LAUNCHER__’ environment variable is used to set *note
PyConfig.base_executable: 3fe9.


File: python.info,  Node: Py_RunMain,  Next: Multi-Phase Initialization Private Provisional API,  Prev: Path Configuration,  Up: Python Initialization Configuration

7.10.10 Py_RunMain()
--------------------

 -- C 函式: int Py_RunMain (void)

     Execute the command (*note PyConfig.run_command: 4009.), the script
     (*note PyConfig.run_filename: 400a.) or the module (*note
     PyConfig.run_module: 400b.) specified on the command line or in the
     configuration.

     By default and when if *note -i: e24. 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: 3fd4. for an example of customized
Python always running in isolated mode using *note Py_RunMain(): 17d.


File: python.info,  Node: Multi-Phase Initialization Private Provisional API,  Prev: Py_RunMain,  Up: Python Initialization Configuration

7.10.11 Multi-Phase Initialization Private Provisional API
----------------------------------------------------------

This section is a private provisional API introducing multi-phase
initialization, the core feature of the PEP 432(1):

   * "Core" initialization phase, "bare minimum Python":

        * Builtin types;

        * Builtin exceptions;

        * Builtin and frozen modules;

        * The *note sys: fe. module is only partially initialized (ex:
          *note sys.path: 48d. doesn’t exist yet).

   * "Main" initialization phase, Python is fully initialized:

        * Install and configure *note importlib: 9b.;

        * Apply the *note Path Configuration: 4001.;

        * Install signal handlers;

        * Finish *note sys: fe. module initialization (ex: create *note
          sys.stdout: 313. and *note sys.path: 48d.);

        * Enable optional features like *note faulthandler: 7d. and
          *note tracemalloc: 115.;

        * Import the *note site: ec. module;

        * etc.

Private provisional API:

   * ‘PyConfig._init_main’: if set to 0, *note
     Py_InitializeFromConfig(): 179. stops at the "Core" initialization
     phase.

 -- C 函式: PyStatus _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: 4001. is only applied
during the "Main" phase.  It may allow to customize Python in Python to
override or tune the *note Path Configuration: 4001, maybe install a
custom *note sys.meta_path: 5eb. importer or an import hook, etc.

It may become possible to calculatin the *note Path Configuration: 4001.
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://www.python.org/dev/peps/pep-0432

   (2) https://www.python.org/dev/peps/pep-0432


File: python.info,  Node: 記憶體管理,  Next: Object Implementation Support,  Prev: Python Initialization Configuration,  Up: Python / C API 參考手冊

7.11 記憶體管理
===============

* Menu:

* 總覽: 總覽<2>.
* Raw Memory Interface::
* Memory Interface::
* Object allocators::
* Default Memory Allocators::
* Customize Memory Allocators::
* The pymalloc allocator::
* tracemalloc C API::
* Examples: Examples<34>.


File: python.info,  Node: 總覽<2>,  Next: Raw Memory Interface,  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: 508. environment variable can be used to
configure the memory allocators used by Python.

The *note PYTHONMALLOCSTATS: 1167. environment variable can be used to
print statistics of the *note pymalloc memory allocator: 5c6. every time
a new pymalloc object arena is created, and on shutdown.


File: python.info,  Node: Raw Memory Interface,  Next: Memory Interface,  Prev: 總覽<2>,  Up: 記憶體管理

7.11.2 Raw Memory Interface
---------------------------

The following function sets are wrappers to the system allocator.  These
functions are thread-safe, the *note GIL: 50b. does not need to be held.

The *note default raw memory allocator: 1362. 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)

     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)

     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)

     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(): 972, *note PyMem_RawRealloc(): 973. or
     *note PyMem_RawCalloc(): 7aa.

     If the request fails, *note PyMem_RawRealloc(): 973. returns ‘NULL’
     and `p' remains a valid pointer to the previous memory area.

 -- C 函式: void PyMem_RawFree (void *p)

     Frees the memory block pointed to by `p', which must have been
     returned by a previous call to *note PyMem_RawMalloc(): 972, *note
     PyMem_RawRealloc(): 973. or *note PyMem_RawCalloc(): 7aa.
     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: Memory Interface,  Next: Object allocators,  Prev: Raw Memory Interface,  Up: 記憶體管理

7.11.3 Memory Interface
-----------------------

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: 1362. uses the *note pymalloc memory
allocator: 5c6.

     警告: The *note GIL: 50b. 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)

     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)

     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)

     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(): 50a, *note PyMem_Realloc(): 974. or *note
     PyMem_Calloc(): 7ab.

     If the request fails, *note PyMem_Realloc(): 974. returns ‘NULL’
     and `p' remains a valid pointer to the previous memory area.

 -- C 函式: void PyMem_Free (void *p)

     Frees the memory block pointed to by `p', which must have been
     returned by a previous call to *note PyMem_Malloc(): 50a, *note
     PyMem_Realloc(): 974. or *note PyMem_Calloc(): 7ab.  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 函式: TYPE* PyMem_New (TYPE, size_t n)

     Same as *note PyMem_Malloc(): 50a, 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 函式: TYPE* PyMem_Resize (void *p, TYPE, size_t n)

     Same as *note PyMem_Realloc(): 974, 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)

     Same as *note PyMem_Free(): dae.

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: Memory Interface,  Up: 記憶體管理

7.11.4 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.

The *note default object allocator: 1362. uses the *note pymalloc memory
allocator: 5c6.

     警告: The *note GIL: 50b. must be held when using these functions.

 -- C 函式: void* PyObject_Malloc (size_t n)

     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)

     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)

     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(): 50d, *note PyObject_Realloc(): daf. or
     *note PyObject_Calloc(): 7ac.

     If the request fails, *note PyObject_Realloc(): daf. returns ‘NULL’
     and `p' remains a valid pointer to the previous memory area.

 -- C 函式: void PyObject_Free (void *p)

     Frees the memory block pointed to by `p', which must have been
     returned by a previous call to *note PyObject_Malloc(): 50d, *note
     PyObject_Realloc(): daf. or *note PyObject_Calloc(): 7ac.
     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.5 Default Memory Allocators
--------------------------------

Default memory allocators:

Configuration                       Name                     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: 508. environment variable

   * ‘malloc’: system allocators from the standard C library, C
     functions: ‘malloc()’, ‘calloc()’, ‘realloc()’ and ‘free()’

   * ‘pymalloc’: *note pymalloc memory allocator: 5c6.

   * "+ debug": with debug hooks installed by *note
     PyMem_SetupDebugHooks(): 50f.


File: python.info,  Node: Customize Memory Allocators,  Next: The pymalloc allocator,  Prev: Default Memory Allocators,  Up: 記憶體管理

7.11.6 Customize Memory Allocators
----------------------------------

3.4 版新加入.

 -- C 類型: PyMemAllocatorEx

     Structure used to describe a memory block allocator.  The structure
     has four fields:

     Field                                                          Meaning
                                                                    
     -----------------------------------------------------------------------------------------------------------
                                                                    
     ‘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: 7cf. and a new ‘calloc’ field was added.

 -- C 類型: PyMemAllocatorDomain

     Enum used to identify an allocator domain.  Domains:

      -- C 巨集: PYMEM_DOMAIN_RAW

          Functions:

             * *note PyMem_RawMalloc(): 972.

             * *note PyMem_RawRealloc(): 973.

             * *note PyMem_RawCalloc(): 7aa.

             * *note PyMem_RawFree(): 3c3f.

      -- C 巨集: PYMEM_DOMAIN_MEM

          Functions:

             * *note PyMem_Malloc(): 50a,

             * *note PyMem_Realloc(): 974.

             * *note PyMem_Calloc(): 7ab.

             * *note PyMem_Free(): dae.

      -- C 巨集: PYMEM_DOMAIN_OBJ

          Functions:

             * *note PyObject_Malloc(): 50d.

             * *note PyObject_Realloc(): daf.

             * *note PyObject_Calloc(): 7ac.

             * *note PyObject_Free(): 509.

 -- 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: 1363. domain, the allocator must be
     thread-safe: the *note GIL: 50b. is not held when the allocator is
     called.

     If the new allocator is not a hook (does not call the previous
     allocator), the *note PyMem_SetupDebugHooks(): 50f. function must
     be called to reinstall the debug hooks on top on the new allocator.

 -- C 函式: void PyMem_SetupDebugHooks (void)

     Setup hooks to detect bugs in the Python memory allocator
     functions.

     Newly allocated memory is filled with the byte ‘0xCD’
     (‘CLEANBYTE’), freed memory is filled with the byte ‘0xDD’
     (‘DEADBYTE’).  Memory blocks are surrounded by "forbidden bytes"
     (‘FORBIDDENBYTE’: byte ‘0xFD’).

     Runtime checks:

        - Detect API violations, ex: *note PyObject_Free(): 509. called
          on a buffer allocated by *note PyMem_Malloc(): 50a.

        - 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: 50b. is held when allocator
          functions of *note PYMEM_DOMAIN_OBJ: 50c. (ex: *note
          PyObject_Malloc(): 50d.) and *note PYMEM_DOMAIN_MEM: 50e. (ex:
          *note PyMem_Malloc(): 50a.) domains are called

     On error, the debug hooks use the *note tracemalloc: 115. module to
     get the traceback where a memory block was allocated.  The
     traceback is only displayed if *note tracemalloc: 115. is tracing
     Python memory allocations and the memory block was traced.

     These hooks are *note installed by default: 1362. if Python is
     compiled in debug mode.  The *note PYTHONMALLOC: 508. environment
     variable can be used to install debug hooks on a Python compiled in
     release mode.

     3.6 版更變: This function now also works on Python compiled in
     release mode.  On error, the debug hooks now use *note tracemalloc:
     115. 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: 50c. and *note PYMEM_DOMAIN_MEM: 50e.
     domains are called.

     3.8 版更變: Byte patterns ‘0xCB’ (‘CLEANBYTE’), ‘0xDB’ (‘DEADBYTE’)
     and ‘0xFB’ (‘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: tracemalloc C API,  Prev: Customize Memory Allocators,  Up: 記憶體管理

7.11.7 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 256 KiB. It falls back to *note
PyMem_RawMalloc(): 972. and *note PyMem_RawRealloc(): 973. for
allocations larger than 512 bytes.

`pymalloc' is the *note default allocator: 1362. of the *note
PYMEM_DOMAIN_MEM: 50e. (ex: *note PyMem_Malloc(): 50a.) and *note
PYMEM_DOMAIN_OBJ: 50c. (ex: *note PyObject_Malloc(): 50d.) domains.

The arena allocator uses the following functions:

   * ‘VirtualAlloc()’ and ‘VirtualFree()’ on Windows,

   * ‘mmap()’ and ‘munmap()’ if available,

   * ‘malloc()’ and ‘free()’ otherwise.

* Menu:

* Customize pymalloc Arena Allocator::


File: python.info,  Node: Customize pymalloc Arena Allocator,  Up: The pymalloc allocator

7.11.7.1 Customize pymalloc Arena Allocator
...........................................

3.4 版新加入.

 -- C 類型: PyObjectArenaAllocator

     Structure used to describe an arena allocator.  The structure has
     three fields:

     Field                                                  Meaning
                                                            
     ---------------------------------------------------------------------------------------------------
                                                            
     ‘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: tracemalloc C API,  Next: Examples<34>,  Prev: The pymalloc allocator,  Up: 記憶體管理

7.11.8 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: 115.
     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: 115.
     module.  Do nothing if the block was not tracked.

     Return ‘-2’ if tracemalloc is disabled, otherwise return ‘0’.


File: python.info,  Node: Examples<34>,  Prev: tracemalloc C API,  Up: 記憶體管理

7.11.9 Examples
---------------

Here is the example from section *note 總覽: 4020, 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(): 2d3, *note PyObject_NewVar(): 2d4. and *note
PyObject_Del(): e1b.

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 and ABI Versioning,  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:

* Allocating Objects on the Heap::
* 通用物件結構::
* Type Objects: Type Objects<3>.
* Number Object Structures::
* Mapping Object Structures::
* Sequence Object Structures::
* Buffer Object Structures::
* Async Object Structures::
* Slot Type typedefs::
* Examples: Examples<35>.
* Supporting Cyclic Garbage Collection::


File: python.info,  Node: Allocating Objects on the Heap,  Next: 通用物件結構,  Up: Object Implementation Support

7.12.1 Allocating Objects on the Heap
-------------------------------------

 -- C 函式: PyObject* _PyObject_New (PyTypeObject *type)
     `Return value: New reference.'

 -- C 函式: PyVarObject* _PyObject_NewVar (PyTypeObject *type,
          Py_ssize_t size)
     `Return value: New reference.'

 -- C 函式: PyObject* PyObject_Init (PyObject *op, PyTypeObject *type)
     `Return value: Borrowed reference.'  Initialize a newly-allocated
     object `op' with its type and initial reference.  Returns the
     initialized object.  If `type' indicates that the object
     participates in the cyclic garbage detector, it is added to the
     detector’s set of observed objects.  Other fields of the object are
     not affected.

 -- C 函式: PyVarObject* PyObject_InitVar (PyVarObject *op,
          PyTypeObject *type, Py_ssize_t size)
     `Return value: Borrowed reference.'  This does everything *note
     PyObject_Init(): 270. does, and also initializes the length
     information for a variable-size object.

 -- C 函式: TYPE* PyObject_New (TYPE, PyTypeObject *type)
     `Return value: New reference.'  Allocate a new Python object using
     the C structure type `TYPE' and the Python type object `type'.
     Fields not defined by the Python object header are not initialized;
     the object’s reference count will be one.  The size of the memory
     allocation is determined from the *note tp_basicsize: 3b33. field
     of the type object.

 -- C 函式: TYPE* PyObject_NewVar (TYPE, PyTypeObject *type,
          Py_ssize_t size)
     `Return value: New reference.'  Allocate a new Python object using
     the C structure type `TYPE' and the Python type object `type'.
     Fields not defined by the Python object header are not initialized.
     The allocated memory allows for the `TYPE' structure plus `size'
     fields of the size given by the *note tp_itemsize: 3b32. field of
     `type'.  This is useful for implementing objects like tuples, which
     are able to determine their size at construction time.  Embedding
     the array of fields into the same allocation decreases the number
     of allocations, improving the memory management efficiency.

 -- C 函式: void PyObject_Del (void *op)

     Releases memory allocated to an object using *note PyObject_New():
     2d3. or *note PyObject_NewVar(): 2d4.  This is normally called from
     the *note tp_dealloc: 3b39. handler specified in the object’s type.
     The fields of the object should not be accessed after this call as
     the memory is no longer a valid Python object.

 -- C 變數: PyObject _Py_NoneStruct

     Object which is visible in Python as ‘None’.  This should only be
     accessed using the *note Py_None: 3afe. macro, which evaluates to a
     pointer to this object.

也參考
......

*note PyModule_Create(): 3b01.

     To allocate and create extension modules.


File: python.info,  Node: 通用物件結構,  Next: Type Objects<3>,  Prev: Allocating Objects on the 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.

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: 4bf. and *note PyVarObject: 403f.
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.

 -- C 類型: PyObject

     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:
     4bf, but every pointer to a Python object can be cast to a *note
     PyObject*: 4bf.  Access to the members must be done by using the
     macros *note Py_REFCNT: 3b2f. and *note Py_TYPE: 3b30.

 -- C 類型: PyVarObject

     This is an extension of *note PyObject: 4bf. that adds the
     ‘ob_size’ 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: 3b2f, *note Py_TYPE: 3b30, and *note
     Py_SIZE: 4040.

 -- 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: 4bf. 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;

     See documentation of *note PyVarObject: 403f. above.

 -- C 巨集: Py_TYPE (o)

     This macro is used to access the ‘ob_type’ member of a Python
     object.  It expands to:

          (((PyObject*)(o))->ob_type)

 -- C 巨集: Py_REFCNT (o)

     This macro is used to access the ‘ob_refcnt’ member of a Python
     object.  It expands to:

          (((PyObject*)(o))->ob_refcnt)

 -- C 巨集: Py_SIZE (o)

     This macro is used to access the ‘ob_size’ member of a Python
     object.  It expands to:

          (((PyVarObject*)(o))->ob_size)

 -- C 巨集: PyObject_HEAD_INIT (type)

     This is a macro which expands to initialization values for a new
     *note PyObject: 4bf. 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: 403f. type, including the ‘ob_size’ field.  This
     macro expands to:

          _PyObject_EXTRA_INIT
          1, type, size,

 -- C 類型: PyCFunction

     Type of the functions used to implement most Python callables in C.
     Functions of this type take two *note PyObject*: 4bf. 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.

 -- C 類型: PyCFunctionWithKeywords

     Type of the functions used to implement Python callables in C with
     signature ‘METH_VARARGS | METH_KEYWORDS’.

 -- C 類型: _PyCFunctionFast

     Type of the functions used to implement Python callables in C with
     signature *note METH_FASTCALL: fbd.

 -- C 類型: _PyCFunctionFastWithKeywords

     Type of the functions used to implement Python callables in C with
     signature ‘METH_FASTCALL | METH_KEYWORDS’.

 -- C 類型: PyMethodDef

     Structure used to describe a method of an extension type.  This
     structure has four fields:

     Field                  C Type              Meaning
                                                
     -------------------------------------------------------------------------------
                                                
     ‘ml_name’              const char *        name of the method
                                                
                                                
     ‘ml_meth’              PyCFunction         pointer to the C implementation
                                                
                                                
     ‘ml_flags’             int                 flag bits indicating how the call
                                                should be constructed
                                                
                                                
     ‘ml_doc’               const char *        points to the contents of the
                                                docstring
                                                

The ‘ml_meth’ is a C function pointer.  The functions may be of
different types, but they always return *note PyObject*: 4bf.  If the
function is not of the *note PyCFunction: de0, the compiler will require
a cast in the method table.  Even though *note PyCFunction: de0. defines
the first parameter as *note PyObject*: 4bf, it is common that the
method implementation uses the specific C type of the `self' object.

The ‘ml_flags’ field is a bitfield which can include the following
flags.  The individual flags indicate either a calling convention or a
binding convention.

There are four basic calling conventions for positional arguments and
two of them can be combined with ‘METH_KEYWORDS’ to support also keyword
arguments.  So there are a total of 6 calling conventions:

 -- Data: METH_VARARGS

     This is the typical calling convention, where the methods have the
     type *note PyCFunction: de0.  The function expects two *note
     PyObject*: 4bf. 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(): 26b. or *note PyArg_UnpackTuple(): e4b.

 -- Data: METH_VARARGS | METH_KEYWORDS

     Methods with these flags must be of type *note
     PyCFunctionWithKeywords: 4044.  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(): 5cf.

 -- Data: METH_FASTCALL

     Fast calling convention supporting only positional arguments.  The
     methods have the type *note _PyCFunctionFast: 4045.  The first
     parameter is `self', the second parameter is a C array of *note
     PyObject*: 4bf. values indicating the arguments and the third
     parameter is the number of arguments (the length of the array).

     This is not part of the *note limited API: 3bbb.

     3.7 版新加入.

 -- Data: METH_FASTCALL | METH_KEYWORDS

     Extension of *note METH_FASTCALL: fbd. supporting also keyword
     arguments, with methods of type *note _PyCFunctionFastWithKeywords:
     4046.  Keyword arguments are passed the same way as in the
     vectorcall protocol: there is an additional fourth *note PyObject*:
     4bf. parameter which is a tuple representing the names of the
     keyword arguments or possibly ‘NULL’ if there are no keywords.  The
     values of the keyword arguments are stored in the `args' array,
     after the positional arguments.

     This is not part of the *note limited API: 3bbb.

     3.7 版新加入.

 -- Data: METH_NOARGS

     Methods without parameters don’t need to check whether arguments
     are given if they are listed with the *note METH_NOARGS: e1d. flag.
     They need to be of type *note PyCFunction: de0.  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’.

 -- Data: METH_O

     Methods with a single object argument can be listed with the *note
     METH_O: e4c. flag, instead of invoking *note PyArg_ParseTuple():
     26b. with a ‘"O"’ argument.  They have the type *note PyCFunction:
     de0, with the `self' parameter, and a *note PyObject*: 4bf.
     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.

 -- Data: 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(): 1d9. built-in function.

 -- Data: 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():
     1da. built-in function.

One other constant controls whether a method is loaded in place of
another definition with the same method name.

 -- Data: 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__(): d2d. 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 類型: PyMemberDef

     Structure which describes an attribute of a type which corresponds
     to a C struct member.  Its fields are:

     Field                  C Type              Meaning
                                                
     -------------------------------------------------------------------------------
                                                
     ‘name’                 const char *        name of the member
                                                
                                                
     ‘type’                 int                 the type of the member in the C
                                                struct
                                                
                                                
     ‘offset’               Py_ssize_t          the offset in bytes that the
                                                member is located on the type’s
                                                object struct
                                                
                                                
     ‘flags’                int                 flag bits indicating if the field
                                                should be read-only or writable
                                                
                                                
     ‘doc’                  const char *        points to the contents of the
                                                docstring
                                                

     ‘type’ can be one of many ‘T_’ macros corresponding to various C
     types.  When the member is accessed in Python, it will be converted
     to the equivalent Python type.

     Macro name          C type
                         
     -------------------------------------------
                         
     T_SHORT             short
                         
                         
     T_INT               int
                         
                         
     T_LONG              long
                         
                         
     T_FLOAT             float
                         
                         
     T_DOUBLE            double
                         
                         
     T_STRING            const char *
                         
                         
     T_OBJECT            PyObject *
                         
                         
     T_OBJECT_EX         PyObject *
                         
                         
     T_CHAR              char
                         
                         
     T_BYTE              char
                         
                         
     T_UBYTE             unsigned char
                         
                         
     T_UINT              unsigned int
                         
                         
     T_USHORT            unsigned short
                         
                         
     T_ULONG             unsigned long
                         
                         
     T_BOOL              char
                         
                         
     T_LONGLONG          long long
                         
                         
     T_ULONGLONG         unsigned long long
                         
                         
     T_PYSSIZET          Py_ssize_t
                         

     ‘T_OBJECT’ and ‘T_OBJECT_EX’ differ in that ‘T_OBJECT’ returns
     ‘None’ if the member is ‘NULL’ and ‘T_OBJECT_EX’ raises an *note
     AttributeError: 3a0.  Try to use ‘T_OBJECT_EX’ over ‘T_OBJECT’
     because ‘T_OBJECT_EX’ handles use of the *note del: 1273. statement
     on that attribute more correctly than ‘T_OBJECT’.

     ‘flags’ can be ‘0’ for write and read access or ‘READONLY’ for
     read-only access.  Using ‘T_STRING’ for *note type: 60d. implies
     ‘READONLY’.  ‘T_STRING’ data is interpreted as UTF-8.  Only
     ‘T_OBJECT’ and ‘T_OBJECT_EX’ members can be deleted.  (They are set
     to ‘NULL’).

 -- C 類型: PyGetSetDef

     Structure to define property-like access for a type.  See also
     description of the *note PyTypeObject.tp_getset: 3b44. slot.

     Field             C Type                 Meaning
                                              
     ---------------------------------------------------------------------------------
                                              
     name              const char *           attribute name
                                              
                                              
     get               getter                 C Function to get the attribute
                                              
                                              
     set               setter                 optional C function to set or delete
                                              the attribute, if omitted the
                                              attribute is readonly
                                              
                                              
     doc               const char *           optional docstring
                                              
                                              
     closure           void *                 optional function pointer, providing
                                              additional data for getter and setter
                                              

     The ‘get’ function takes one *note PyObject*: 4bf. parameter (the
     instance) and a function pointer (the associated ‘closure’):

          typedef PyObject *(*getter)(PyObject *, void *);

     It should return a new reference on success or ‘NULL’ with a set
     exception on failure.

     ‘set’ functions take two *note PyObject*: 4bf. parameters (the
     instance and the value to be set) and a function pointer (the
     associated ‘closure’):

          typedef int (*setter)(PyObject *, PyObject *, void *);

     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: Type Objects<3>,  Next: Number Object Structures,  Prev: 通用物件結構,  Up: Object Implementation Support

7.12.3 Type Objects
-------------------

Perhaps one of the most important structures of the Python object system
is the structure that defines a new type: the *note PyTypeObject: 2d7.
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 Examples: 404a.
section provides at-a-glance insight into the meaning and use of *note
PyTypeObject: 2d7.

* Menu:

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


File: python.info,  Node: Quick Reference,  Next: PyTypeObject Definition,  Up: Type Objects<3>

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: 404e.      special                Info
(1)                                           methods/attrs          (2)
                                                                     
---------------------------------------------------------------------------------------------
                                                                     
O                      T                      D                      I
                                                                     
                                                                                       
<R>                    const char *           __name__               X     X
*note tp_name: 3b55.                                                       

*note tp_basicsize: 3b33.Py_ssize_t                                  X     X           X
                                                                                       
                                                                                       
*note tp_itemsize: 3b32.Py_ssize_t                                         X           X
                                                                                       
                                                                                       
*note tp_dealloc: 3b39.*note destructor: 404f.                       X     X           X
                                                                                       
                                                                                       
*note tp_vectorcall_offset: 3cbc.Py_ssize_t                                            ?
                                                                                       
                                                                                       
(*note tp_getattr: 3b5c.)*note getattrfunc: 4050.__getattribute__,                     G
                                              __getattr__                              
                                              
                                                                                       
(*note tp_setattr: 3b5d.)*note setattrfunc: 4051.__setattr__,                          G
                                              __delattr__                              
                                              
                                                                                       
*note tp_as_async: 4052.*note PyAsyncMethods: 3d6c.*note sub-slots: 4053.              %
                       *                                                               
                       
                                                                                       
*note tp_repr: 3b54.   *note reprfunc: 4054.  __repr__               X     X           X
                                                                                       
                                                                                       
*note tp_as_number: 4055.*note PyNumberMethods: d86.*note sub-slots: 4053.             %
                       *                                                               
                       
                                                                                       
*note tp_as_sequence: 4056.*note PySequenceMethods: 3b63.*note sub-slots: 4053.        %
                       *                                                               
                       
                                                                                       
*note tp_as_mapping: 4057.*note PyMappingMethods: 3b64.*note sub-slots: 4053.          %
                       *                                                               
                       
                                                                                       
*note tp_hash: 3b65.   *note hashfunc: 4058.  __hash__               X                 G
                                                                                       
                                                                                       
*note tp_call: 3b66.   *note ternaryfunc: 4059.__call__                    X           X
                                                                                       
                                                                                       
*note tp_str: 3b56.    *note reprfunc: 4054.  __str__                X                 X
                                                                                       
                                                                                       
*note tp_getattro: 3b59.*note getattrofunc: 405a.__getattribute__,   X     X           G
                                              __getattr__                              
                                              
                                                                                       
*note tp_setattro: 3b5a.*note setattrofunc: 405b.__setattr__,        X     X           G
                                              __delattr__                              
                                              
                                                                                       
*note tp_as_buffer: 405c.*note PyBufferProcs: 405d.                                    %
                       *                                                               
                       
                                                                                       
*note tp_flags: 3d5b.  unsigned long                                 X     X           ?
                                                                                       
                                                                                       
*note tp_doc: 3b35.    const char *           __doc__                X     X
                                                                           
                                                                                       
*note tp_traverse: 36be.*note traverseproc: 405e.                          X           G
                                                                                       
                                                                                       
*note tp_clear: 3b52.  *note inquiry: 405f.                                X           G
                                                                                       
                                                                                       
*note tp_richcompare: 3b5f.*note richcmpfunc: 4060.__lt__, __le__,   X                 G
                                              __eq__, __ne__,                          
                                              __gt__, __ge__
                                              
                                                                                       
*note tp_weaklistoffset: 3b68.Py_ssize_t                                   X           ?
                                                                                       
                                                                                       
*note tp_iter: e35.    *note getiterfunc: 4061.__iter__                                X
                                                                                       
                                                                                       
*note tp_iternext: e36.*note iternextfunc: 4062.__next__                               X
                                                                                       
                                                                                       
*note tp_methods: 3b40.*note PyMethodDef: e20.                       X     X
                       []                                                  
                       
                                                                                       
*note tp_members: 3b3e.*note PyMemberDef: 42b.                             X
                       []                                                  
                       
                                                                                       
*note tp_getset: 3b44. *note PyGetSetDef: 42c.                       X     X
                       []                                                  
                       
                                                                                       
*note tp_base: 3b4a.   *note PyTypeObject: 2d7.__base__                          X
                       *                                                         
                       
                                                                                       
*note tp_dict: 3d6f.   *note PyObject: 4bf.   __dict__                           ?
                       *                                                         
                       
                                                                                       
*note tp_descr_get: 4063.*note descrgetfunc: 4064.__get__                              X
                                                                                       
                                                                                       
*note tp_descr_set: 4065.*note descrsetfunc: 4066.__set__, __delete__                  X
                                                                                       
                                                                                       
*note tp_dictoffset: 3d74.Py_ssize_t                                       X           ?
                                                                                       
                                                                                       
*note tp_init: 3b3d.   *note initproc: 4067.  __init__               X     X           X
                                                                                       
                                                                                       
*note tp_alloc: 3b3b.  *note allocfunc: 4068.                        X           ?     ?
                                                                                       
                                                                                       
*note tp_new: 3b36.    *note newfunc: 4069.   __new__                X     X     ?     ?
                                                                                       
                                                                                       
*note tp_free: 3b3a.   *note freefunc: 406a.                         X     X     ?     ?
                                                                                       
                                                                                       
*note tp_is_gc: 406b.  *note inquiry: 405f.                                X           X
                                                                                       
                                                                                       
<*note tp_bases: 406c.>*note PyObject: 4bf.   __bases__                          ~
                       *                                                         
                       
                                                                                       
<*note tp_mro: 3d70.>  *note PyObject: 4bf.   __mro__                            ~
                       *                                                         
                       
                                                                                       
[*note tp_cache: 3d71.]*note PyObject: 4bf.
                       *
                       
                                                                                       
[*note tp_subclasses: 3d72.]*note PyObject: 4bf.__subclasses__
                       *                      
                       
                                                                                       
[*note tp_weaklist: 3d73.]*note PyObject: 4bf.
                       *
                       
                                                                                       
(*note tp_del: 406d.)  *note destructor: 404f.
                       
                                                                                       
[*note tp_version_tag: 406e.]unsigned int
                       
                                                                                       
*note tp_finalize: 2d8.*note destructor: 404f.__del__                                  X
                                                                                       

If ‘COUNT_ALLOCS’ is defined then the following (internal-only) fields
exist as well:

   * *note tp_allocs: 406f.

   * *note tp_frees: 4070.

   * *note tp_maxalloc: 4071.

   * *note tp_prev: 4072.

   * *note tp_next: 4073.

   ---------- Footnotes ----------

   (1) (1) A slot name in parentheses indicates it is (effectively)
deprecated.  Names in angle brackets should be 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) (2) Columns:

`"O"': set on ‘PyBaseObject_Type’

`"T"': set on *note PyType_Type: 3d56.

`"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: 404e.     special
                                                     methods
                                                     
----------------------------------------------------------------------
                                                     
*note am_await: 4075.          *note unaryfunc: 4076.__await__
                                                     
                                                     
*note am_aiter: 4077.          *note unaryfunc: 4076.__aiter__
                                                     
                                                     
*note am_anext: 4078.          *note unaryfunc: 4076.__anext__
                                                     
                                                     
                                                     
*note nb_add: 3d6d.            *note binaryfunc: 4079.__add__
                                                     __radd__
                                                     
                                                     
*note nb_inplace_add: 407a.    *note binaryfunc: 4079.__iadd__
                                                     
                                                     
*note nb_subtract: 407b.       *note binaryfunc: 4079.__sub__
                                                     __rsub__
                                                     
                                                     
*note nb_inplace_subtract: 407c.*note binaryfunc: 4079.__sub__
                                                     
                                                     
*note nb_multiply: 407d.       *note binaryfunc: 4079.__mul__
                                                     __rmul__
                                                     
                                                     
*note nb_inplace_multiply: 407e.*note binaryfunc: 4079.__mul__
                                                     
                                                     
*note nb_remainder: 407f.      *note binaryfunc: 4079.__mod__
                                                     __rmod__
                                                     
                                                     
*note nb_inplace_remainder: 4080.*note binaryfunc: 4079.__mod__
                                                     
                                                     
*note nb_divmod: 4081.         *note binaryfunc: 4079.__divmod__
                                                     __rdivmod__
                                                     
                                                     
*note nb_power: 4082.          *note ternaryfunc: 4059.__pow__
                                                     __rpow__
                                                     
                                                     
*note nb_inplace_power: 4083.  *note ternaryfunc: 4059.__pow__
                                                     
                                                     
*note nb_negative: 4084.       *note unaryfunc: 4076.__neg__
                                                     
                                                     
*note nb_positive: 4085.       *note unaryfunc: 4076.__pos__
                                                     
                                                     
*note nb_absolute: 4086.       *note unaryfunc: 4076.__abs__
                                                     
                                                     
*note nb_bool: 4087.           *note inquiry: 405f.  __bool__
                                                     
                                                     
*note nb_invert: 4088.         *note unaryfunc: 4076.__invert__
                                                     
                                                     
*note nb_lshift: 4089.         *note binaryfunc: 4079.__lshift__
                                                     __rlshift__
                                                     
                                                     
*note nb_inplace_lshift: 408a. *note binaryfunc: 4079.__lshift__
                                                     
                                                     
*note nb_rshift: 408b.         *note binaryfunc: 4079.__rshift__
                                                     __rrshift__
                                                     
                                                     
*note nb_inplace_rshift: 408c. *note binaryfunc: 4079.__rshift__
                                                     
                                                     
*note nb_and: 408d.            *note binaryfunc: 4079.__and__
                                                     __rand__
                                                     
                                                     
*note nb_inplace_and: 408e.    *note binaryfunc: 4079.__and__
                                                     
                                                     
*note nb_xor: 408f.            *note binaryfunc: 4079.__xor__
                                                     __rxor__
                                                     
                                                     
*note nb_inplace_xor: 4090.    *note binaryfunc: 4079.__xor__
                                                     
                                                     
*note nb_or: 4091.             *note binaryfunc: 4079.__or__ __ror__
                                                     
                                                     
*note nb_inplace_or: 4092.     *note binaryfunc: 4079.__or__
                                                     
                                                     
*note nb_int: 4093.            *note unaryfunc: 4076.__int__
                                                     
                                                     
*note nb_reserved: 4094.       void *
                               
                                                     
*note nb_float: 4095.          *note unaryfunc: 4076.__float__
                                                     
                                                     
*note nb_floor_divide: 4096.   *note binaryfunc: 4079.__floordiv__
                                                     
                                                     
*note nb_inplace_floor_divide: 4097.*note binaryfunc: 4079.__floordiv__
                                                     
                                                     
*note nb_true_divide: 4098.    *note binaryfunc: 4079.__truediv__
                                                     
                                                     
*note nb_inplace_true_divide: 4099.*note binaryfunc: 4079.__truediv__
                                                     
                                                     
*note nb_index: 409a.          *note unaryfunc: 4076.__index__
                                                     
                                                     
*note nb_matrix_multiply: 409b.*note binaryfunc: 4079.__matmul__
                                                     __rmatmul__
                                                     
                                                     
*note nb_inplace_matrix_multiply: 409c.*note binaryfunc: 4079.__matmul__
                                                     
                                                     
                                                     
*note mp_length: 409d.         *note lenfunc: 409e.  __len__
                                                     
                                                     
*note mp_subscript: 409f.      *note binaryfunc: 4079.__getitem__
                                                     
                                                     
*note mp_ass_subscript: 40a0.  *note objobjargproc: 40a1.__setitem__,
                                                     __delitem__
                                                     
                                                     
                                                     
*note sq_length: 3d6e.         *note lenfunc: 409e.  __len__
                                                     
                                                     
*note sq_concat: 40a2.         *note binaryfunc: 4079.__add__
                                                     
                                                     
*note sq_repeat: 40a3.         *note ssizeargfunc: 40a4.__mul__
                                                     
                                                     
*note sq_item: 40a5.           *note ssizeargfunc: 40a4.__getitem__
                                                     
                                                     
*note sq_ass_item: 40a6.       *note ssizeobjargproc: 40a7.__setitem__
                                                     __delitem__
                                                     
                                                     
*note sq_contains: 40a8.       *note objobjproc: 40a9.__contains__
                                                     
                                                     
*note sq_inplace_concat: 40aa. *note binaryfunc: 4079.__iadd__
                                                     
                                                     
*note sq_inplace_repeat: 40ab. *note ssizeargfunc: 40a4.__imul__
                                                     
                                                     
                                                     
*note bf_getbuffer: 3d75.      *note getbufferproc(): 40ac.
                               
                                                     
*note bf_releasebuffer: 3c76.  *note releasebufferproc(): 40ad.
                               


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: 4068.                 *note PyTypeObject: 2d7. *   *note PyObject: 4bf. *
                                       Py_ssize_t                   
                                  
                                                                    
*note destructor: 404f.           void *                            void
                                                                    
                                                                    
*note freefunc: 406a.             void *                            void
                                                                    
                                                                    
*note traverseproc: 405e.              void *                       int
                                       *note visitproc: 40af.       
                                       void * 
                                  
                                                                    
*note newfunc: 4069.                   *note PyObject: 4bf. *       *note PyObject: 4bf. *
                                       *note PyObject: 4bf. *       
                                       *note PyObject: 4bf. * 
                                  
                                                                    
*note initproc: 4067.                  *note PyObject: 4bf. *       int
                                       *note PyObject: 4bf. *       
                                       *note PyObject: 4bf. * 
                                  
                                                                    
*note reprfunc: 4054.             *note PyObject: 4bf. *            *note PyObject: 4bf. *
                                                                    
                                                                    
*note getattrfunc: 4050.               *note PyObject: 4bf. *       *note PyObject: 4bf. *
                                       const char *                 
                                  
                                                                    
*note setattrfunc: 4051.               *note PyObject: 4bf. *       int
                                       const char *                 
                                       *note PyObject: 4bf. * 
                                  
                                                                    
*note getattrofunc: 405a.              *note PyObject: 4bf. *       *note PyObject: 4bf. *
                                       *note PyObject: 4bf. *       
                                  
                                                                    
*note setattrofunc: 405b.              *note PyObject: 4bf. *       int
                                       *note PyObject: 4bf. *       
                                       *note PyObject: 4bf. * 
                                  
                                                                    
*note descrgetfunc: 4064.              *note PyObject: 4bf. *       *note PyObject: 4bf. *
                                       *note PyObject: 4bf. *       
                                       *note PyObject: 4bf. * 
                                  
                                                                    
*note descrsetfunc: 4066.              *note PyObject: 4bf. *       int
                                       *note PyObject: 4bf. *       
                                       *note PyObject: 4bf. * 
                                  
                                                                    
*note hashfunc: 4058.             *note PyObject: 4bf. *            Py_hash_t
                                                                    
                                                                    
*note richcmpfunc: 4060.               *note PyObject: 4bf. *       *note PyObject: 4bf. *
                                       *note PyObject: 4bf. *       
                                       int 
                                  
                                                                    
*note getiterfunc: 4061.          *note PyObject: 4bf. *            *note PyObject: 4bf. *
                                                                    
                                                                    
*note iternextfunc: 4062.         *note PyObject: 4bf. *            *note PyObject: 4bf. *
                                                                    
                                                                    
*note lenfunc: 409e.              *note PyObject: 4bf. *            Py_ssize_t
                                                                    
                                                                    
*note getbufferproc: 40ac.             *note PyObject: 4bf. *       int
                                       *note Py_buffer: b20. *      
                                       int 
                                  
                                                                    
*note releasebufferproc: 40ad.         *note PyObject: 4bf. *       void
                                       *note Py_buffer: b20. *      
                                  
                                                                    
*note inquiry: 405f.              void *                            int
                                                                    
                                                                    
*note unaryfunc: 4076.                 *note PyObject: 4bf. *       *note PyObject: 4bf. *
                                                                    
                                                                    
*note binaryfunc: 4079.                *note PyObject: 4bf. *       *note PyObject: 4bf. *
                                       *note PyObject: 4bf. *       
                                  
                                                                    
*note ternaryfunc: 4059.               *note PyObject: 4bf. *       *note PyObject: 4bf. *
                                       *note PyObject: 4bf. *       
                                       *note PyObject: 4bf. * 
                                  
                                                                    
*note ssizeargfunc: 40a4.              *note PyObject: 4bf. *       *note PyObject: 4bf. *
                                       Py_ssize_t                   
                                  
                                                                    
*note ssizeobjargproc: 40a7.           *note PyObject: 4bf. *       int
                                       Py_ssize_t                   
                                  
                                                                    
*note objobjproc: 40a9.                *note PyObject: 4bf. *       int
                                       *note PyObject: 4bf. *       
                                  
                                                                    
*note objobjargproc: 40a1.             *note PyObject: 4bf. *       int
                                       *note PyObject: 4bf. *       
                                       *note PyObject: 4bf. * 
                                  

See *note Slot Type typedefs: 40b0. below for more detail.


File: python.info,  Node: PyTypeObject Definition,  Next: PyObject Slots,  Prev: Quick Reference,  Up: Type Objects<3>

7.12.3.5 PyTypeObject Definition
................................

The structure definition for *note PyTypeObject: 2d7. 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 */

         /* call function for all accessible objects */
         traverseproc tp_traverse;

         /* delete references to contained objects */
         inquiry tp_clear;

         /* 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;
         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;

     } PyTypeObject;


File: python.info,  Node: PyObject Slots,  Next: PyVarObject Slots,  Prev: PyTypeObject Definition,  Up: Type Objects<3>

7.12.3.6 PyObject Slots
.......................

The type object structure extends the *note PyVarObject: 403f.
structure.  The ‘ob_size’ field is used for dynamic types (created by
‘type_new()’, usually called from a class statement).  Note that *note
PyType_Type: 3d56. (the metatype) initializes *note tp_itemsize: 3b32,
which means that its instances (i.e.  type objects) `must' have the
‘ob_size’ field.

 -- C 成員函數: PyObject* PyObject._ob_next
 -- C 成員函數: PyObject* PyObject._ob_prev

     These fields are only present when the macro ‘Py_TRACE_REFS’ is
     defined.  Their initialization to ‘NULL’ is taken care of by the
     ‘PyObject_HEAD_INIT’ macro.  For statically allocated objects,
     these fields always remain ‘NULL’.  For dynamically allocated
     objects, these two fields are used to link the object into a
     doubly-linked list of `all' live objects on the heap.  This could
     be used for various debugging purposes; currently the only use is
     to print the objects that are still alive at the end of a run when
     the environment variable *note PYTHONDUMPREFS: 15a. is set.

     `Inheritance:'

     These fields are not inherited by subtypes.

 -- C 成員函數: Py_ssize_t PyObject.ob_refcnt

     This is the type object’s reference count, initialized to ‘1’ by
     the ‘PyObject_HEAD_INIT’ macro.  Note that for statically allocated
     type objects, the type’s instances (objects whose ‘ob_type’ points
     back to the type) do `not' count as references.  But for
     dynamically allocated type objects, the instances `do' count as
     references.

     `Inheritance:'

     This field is not inherited by subtypes.

 -- C 成員函數: PyTypeObject* PyObject.ob_type

     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(): 3b3c. checks if ‘ob_type’ is ‘NULL’, and if
     so, initializes it to the ‘ob_type’ field of the base class.  *note
     PyType_Ready(): 3b3c. 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: Type Objects<3>

7.12.3.7 PyVarObject Slots
..........................

 -- C 成員函數: Py_ssize_t PyVarObject.ob_size

     For statically allocated type objects, this should be initialized
     to zero.  For dynamically allocated type objects, this field has a
     special internal meaning.

     `Inheritance:'

     This field is not inherited by subtypes.


File: python.info,  Node: PyTypeObject Slots,  Next: Heap Types,  Prev: PyVarObject Slots,  Up: Type Objects<3>

7.12.3.8 PyTypeObject Slots
...........................

Each slot has a section describing inheritance.  If *note
PyType_Ready(): 3b3c. 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: 3d56. effectively act as
defaults.)

 -- C 成員函數: const char* PyTypeObject.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: 3b55. initializer ‘"P.Q.M.T"’.

     For dynamically allocated type objects, this should just be the
     type name, and the module name explicitly stored in the type dict
     as the value for key ‘'__module__'’.

     For statically allocated type objects, 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__: c6c. attribute.

     If no dot is present, the entire *note tp_name: 3b55. field is made
     accessible as the *note __name__: c6c. 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(): 2d7. (other than potentially *note
     tp_itemsize: 3b32.).

     `Inheritance:'

     This field is not inherited by subtypes.

 -- C 成員函數: Py_ssize_t PyTypeObject.tp_basicsize
 -- C 成員函數: Py_ssize_t PyTypeObject.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: 3b32. field, types with
     variable-length instances have a non-zero *note tp_itemsize: 3b32.
     field.  For a type with fixed-length instances, all instances have
     the same size, given in *note tp_basicsize: 3b33.

     For a type with variable-length instances, the instances must have
     an ‘ob_size’ field, and the instance size is *note tp_basicsize:
     3b33. plus N times *note tp_itemsize: 3b32, where N is the "length"
     of the object.  The value of N is typically stored in the
     instance’s ‘ob_size’ field.  There are exceptions: for example,
     ints use a negative ‘ob_size’ to indicate a negative number, and N
     is ‘abs(ob_size)’ there.  Also, the presence of an ‘ob_size’ 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
     ‘ob_size’ field).

     The basic size includes the fields in the instance declared by the
     macro *note PyObject_HEAD: c77. or *note PyObject_VAR_HEAD: 4041.
     (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: 3b33. 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: 3b33.  Example: suppose a type implements an array of
     ‘double’.  *note tp_itemsize: 3b32. is ‘sizeof(double)’.  It is the
     programmer’s responsibility that *note tp_basicsize: 3b33. 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: 3b32, it is generally not
     safe to set *note tp_itemsize: 3b32. to a different non-zero value
     in a subtype (though this depends on the implementation of the base
     type).

 -- C 成員函數: destructor PyTypeObject.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(): 267.
     and *note Py_XDECREF(): 269. 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: 3b3a. function.  If the type is not
     subtypable (doesn’t have the *note Py_TPFLAGS_BASETYPE: 3b41. flag
     bit set), it is permissible to call the object deallocator directly
     instead of via *note tp_free: 3b3a.  The object deallocator should
     be the one used to allocate the instance; this is normally *note
     PyObject_Del(): e1b. if the instance was allocated using *note
     PyObject_New(): 2d3. or ‘PyObject_VarNew()’, or *note
     PyObject_GC_Del(): e48. if the instance was allocated using *note
     PyObject_GC_New(): 2d5. or *note PyObject_GC_NewVar(): 2d6.

     Finally, if the type is heap allocated (*note Py_TPFLAGS_HEAPTYPE:
     3d63.), the deallocator should decrement the reference count for
     its type object 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 成員函數: Py_ssize_t PyTypeObject.tp_vectorcall_offset

     An optional offset to a per-instance function that implements
     calling the object using the `vectorcall' protocol, a more
     efficient alternative of the simpler *note tp_call: 3b66.

     This field is only used if the flag *note
     _Py_TPFLAGS_HAVE_VECTORCALL: 40ba. is set.  If so, this must be a
     positive integer containing the offset in the instance of a *note
     vectorcallfunc: 40bb. pointer.  The signature is the same as for
     *note _PyObject_Vectorcall(): 3cbb.:

          PyObject *vectorcallfunc(PyObject *callable, PyObject *const *args, size_t nargsf, PyObject *kwnames)

     The `vectorcallfunc' pointer may be zero, in which case the
     instance behaves as if *note _Py_TPFLAGS_HAVE_VECTORCALL: 40ba. was
     not set: calling the instance falls back to *note tp_call: 3b66.

     Any class that sets ‘_Py_TPFLAGS_HAVE_VECTORCALL’ must also set
     *note tp_call: 3b66. and make sure its behaviour is consistent with
     the `vectorcallfunc' function.  This can be done by setting
     `tp_call' to ‘PyVectorcall_Call’:

      -- C 函式: PyObject *PyVectorcall_Call (PyObject *callable,
               PyObject *tuple, PyObject *dict)

          Call `callable'’s `vectorcallfunc' with positional and keyword
          arguments given in a tuple and dict, respectively.

          This function is intended to be used in the ‘tp_call’ slot.
          It does not fall back to ‘tp_call’ and it currently does not
          check the ‘_Py_TPFLAGS_HAVE_VECTORCALL’ flag.  To call an
          object, use one of the *note PyObject_Call: 3b0a. functions
          instead.

          備註: It is not recommended for *note heap types: 3d61. to
          implement the vectorcall protocol.  When a user sets
          ‘__call__’ in Python code, only ‘tp_call’ is updated, possibly
          making it inconsistent with the vectorcall function.

          備註: The semantics of the ‘tp_vectorcall_offset’ slot are
          provisional and expected to be finalized in Python 3.9.  If
          you use vectorcall, plan for updating your code for Python
          3.9.

     3.8 版更變: This slot was used for print formatting in Python 2.x.
     In Python 3.0 to 3.7, it was reserved and named ‘tp_print’.

     `Inheritance:'

     This field is inherited by subtypes together with *note tp_call:
     3b66.: a subtype inherits *note tp_vectorcall_offset: 3cbc. from
     its base type when the subtype’s *note tp_call: 3b66. is ‘NULL’.

     Note that *note heap types: 40bd. (including subclasses defined in
     Python) do not inherit the *note _Py_TPFLAGS_HAVE_VECTORCALL: 40ba.
     flag.

 -- C 成員函數: getattrfunc PyTypeObject.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: 3b59.
     function, but taking a C string instead of a Python string object
     to give the attribute name.

     `Inheritance:'

     Group: ‘tp_getattr’, ‘tp_getattro’

     This field is inherited by subtypes together with *note
     tp_getattro: 3b59.: a subtype inherits both *note tp_getattr: 3b5c.
     and *note tp_getattro: 3b59. from its base type when the subtype’s
     *note tp_getattr: 3b5c. and *note tp_getattro: 3b59. are both
     ‘NULL’.

 -- C 成員函數: setattrfunc PyTypeObject.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: 3b5a.
     function, but taking a C string instead of a Python string object
     to give the attribute name.

     `Inheritance:'

     Group: ‘tp_setattr’, ‘tp_setattro’

     This field is inherited by subtypes together with *note
     tp_setattro: 3b5a.: a subtype inherits both *note tp_setattr: 3b5d.
     and *note tp_setattro: 3b5a. from its base type when the subtype’s
     *note tp_setattr: 3b5d. and *note tp_setattro: 3b5a. are both
     ‘NULL’.

 -- C 成員函數: PyAsyncMethods* PyTypeObject.tp_as_async

     Pointer to an additional structure that contains fields relevant
     only to objects which implement *note awaitable: 51e. and *note
     asynchronous iterator: 64a. protocols at the C-level.  See *note
     Async Object Structures: 40be. for details.

     3.5 版新加入: Formerly known as ‘tp_compare’ and ‘tp_reserved’.

     `Inheritance:'

     The *note tp_as_async: 4052. field is not inherited, but the
     contained fields are inherited individually.

 -- C 成員函數: reprfunc PyTypeObject.tp_repr

     An optional pointer to a function that implements the built-in
     function *note repr(): 7d1.

     The signature is the same as for *note PyObject_Repr(): 96d.:

          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(): b95, 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.

     `Default:'

     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 成員函數: PyNumberMethods* PyTypeObject.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: 40bf.

     `Inheritance:'

     The *note tp_as_number: 4055. field is not inherited, but the
     contained fields are inherited individually.

 -- C 成員函數: PySequenceMethods* PyTypeObject.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: 40c0.

     `Inheritance:'

     The *note tp_as_sequence: 4056. field is not inherited, but the
     contained fields are inherited individually.

 -- C 成員函數: PyMappingMethods* PyTypeObject.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: 40c1.

     `Inheritance:'

     The *note tp_as_mapping: 4057. field is not inherited, but the
     contained fields are inherited individually.

 -- C 成員函數: hashfunc PyTypeObject.tp_hash

     An optional pointer to a function that implements the built-in
     function *note hash(): 9c9.

     The signature is the same as for *note PyObject_Hash(): 3cc0.:

          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' ‘tp_richcompare’ is not set), an
     attempt to take the hash of the object raises *note TypeError: 193.
     This is the same as setting it to *note
     PyObject_HashNotImplemented(): d36.

     This field can be set explicitly to *note
     PyObject_HashNotImplemented(): d36. 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(): d36.

     `Inheritance:'

     Group: ‘tp_hash’, ‘tp_richcompare’

     This field is inherited by subtypes together with *note
     tp_richcompare: 3b5f.: a subtype inherits both of *note
     tp_richcompare: 3b5f. and *note tp_hash: 3b65, when the subtype’s
     *note tp_richcompare: 3b5f. and *note tp_hash: 3b65. are both
     ‘NULL’.

 -- C 成員函數: ternaryfunc PyTypeObject.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(): 3b0a.:

          PyObject *tp_call(PyObject *self, PyObject *args, PyObject *kwargs);

     `Inheritance:'

     This field is inherited by subtypes.

 -- C 成員函數: reprfunc PyTypeObject.tp_str

     An optional pointer to a function that implements the built-in
     operation *note str(): 335.  (Note that *note str: 335. is a type
     now, and *note str(): 335. calls the constructor for that type.
     This constructor calls *note PyObject_Str(): 96e. to do the actual
     work, and *note PyObject_Str(): 96e. will call this handler.)

     The signature is the same as for *note PyObject_Str(): 96e.:

          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(): 88b. function.

     `Inheritance:'

     This field is inherited by subtypes.

     `Default:'

     When this field is not set, *note PyObject_Repr(): 96d. is called
     to return a string representation.

 -- C 成員函數: getattrofunc PyTypeObject.tp_getattro

     An optional pointer to the get-attribute function.

     The signature is the same as for *note PyObject_GetAttr(): 3cac.:

          PyObject *tp_getattro(PyObject *self, PyObject *attr);

     It is usually convenient to set this field to *note
     PyObject_GenericGetAttr(): 3cae, which implements the normal way of
     looking for object attributes.

     `Inheritance:'

     Group: ‘tp_getattr’, ‘tp_getattro’

     This field is inherited by subtypes together with *note tp_getattr:
     3b5c.: a subtype inherits both *note tp_getattr: 3b5c. and *note
     tp_getattro: 3b59. from its base type when the subtype’s *note
     tp_getattr: 3b5c. and *note tp_getattro: 3b59. are both ‘NULL’.

     `Default:'

     ‘PyBaseObject_Type’ uses *note PyObject_GenericGetAttr(): 3cae.

 -- C 成員函數: setattrofunc PyTypeObject.tp_setattro

     An optional pointer to the function for setting and deleting
     attributes.

     The signature is the same as for *note PyObject_SetAttr(): 3caf.:

          PyObject *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(): 3cb3, which implements the normal way of
     setting object attributes.

     `Inheritance:'

     Group: ‘tp_setattr’, ‘tp_setattro’

     This field is inherited by subtypes together with *note tp_setattr:
     3b5d.: a subtype inherits both *note tp_setattr: 3b5d. and *note
     tp_setattro: 3b5a. from its base type when the subtype’s *note
     tp_setattr: 3b5d. and *note tp_setattro: 3b5a. are both ‘NULL’.

     `Default:'

     ‘PyBaseObject_Type’ uses *note PyObject_GenericSetAttr(): 3cb3.

 -- C 成員函數: PyBufferProcs* PyTypeObject.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: 3d13.

     `Inheritance:'

     The *note tp_as_buffer: 405c. field is not inherited, but the
     contained fields are inherited individually.

 -- C 成員函數: unsigned long PyTypeObject.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: 4055, *note
     tp_as_sequence: 4056, *note tp_as_mapping: 4057, and *note
     tp_as_buffer: 405c.) 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: 3b48. flag bit is
     inherited together with the *note tp_traverse: 36be. and *note
     tp_clear: 3b52. fields, i.e.  if the *note Py_TPFLAGS_HAVE_GC:
     3b48. flag bit is clear in the subtype and the *note tp_traverse:
     36be. and *note tp_clear: 3b52. fields in the subtype exist and
     have ‘NULL’ values.

     `Default:'

     ‘PyBaseObject_Type’ uses ‘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: 3d5b. field.  The macro *note PyType_HasFeature(): 3d5d.
     takes a type and a flags value, `tp' and `f', and checks whether
     ‘tp->tp_flags & f’ is non-zero.

      -- Data: 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(): 2d2.  In this case, the ‘ob_type’ 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).

          `Inheritance:'

          ???

      -- Data: 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:'

          ???

      -- Data: Py_TPFLAGS_READY

          This bit is set when the type object has been fully
          initialized by *note PyType_Ready(): 3b3c.

          `Inheritance:'

          ???

      -- Data: Py_TPFLAGS_READYING

          This bit is set while *note PyType_Ready(): 3b3c. is in the
          process of initializing the type object.

          `Inheritance:'

          ???

      -- Data: 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(): 2d5. and destroyed using *note
          PyObject_GC_Del(): e48.  More information in section *note
          Supporting Cyclic Garbage Collection: 40c4.  This bit also
          implies that the GC-related fields *note tp_traverse: 36be.
          and *note tp_clear: 3b52. are present in the type object.

          `Inheritance:'

          Group: *note Py_TPFLAGS_HAVE_GC: 3b48, ‘tp_traverse’,
          ‘tp_clear’

          The *note Py_TPFLAGS_HAVE_GC: 3b48. flag bit is inherited
          together with the ‘tp_traverse’ and ‘tp_clear’ fields, i.e.
          if the *note Py_TPFLAGS_HAVE_GC: 3b48. flag bit is clear in
          the subtype and the ‘tp_traverse’ and ‘tp_clear’ fields in the
          subtype exist and have ‘NULL’ values.

      -- Data: 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’,
          ‘Py_TPFLAGS_HAVE_VERSION_TAG’.

          `Inheritance:'

          ???

      -- Data: 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 heap types.  For extension
          types, it is inherited whenever *note tp_descr_get: 4063. is
          inherited.

      -- Data: Py_TPFLAGS_LONG_SUBCLASS

      -- Data: Py_TPFLAGS_LIST_SUBCLASS

      -- Data: Py_TPFLAGS_TUPLE_SUBCLASS

      -- Data: Py_TPFLAGS_BYTES_SUBCLASS

      -- Data: Py_TPFLAGS_UNICODE_SUBCLASS

      -- Data: Py_TPFLAGS_DICT_SUBCLASS

      -- Data: Py_TPFLAGS_BASE_EXC_SUBCLASS

      -- Data: Py_TPFLAGS_TYPE_SUBCLASS

          These flags are used by functions such as *note
          PyLong_Check(): 3d81. 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(): 7a2.
          Custom types that inherit from built-ins should have their
          *note tp_flags: 3d5b. set appropriately, or the code that
          interacts with such types will behave differently depending on
          what kind of check is used.

      -- Data: Py_TPFLAGS_HAVE_FINALIZE

          This bit is set when the *note tp_finalize: 2d8. 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: 2d8. slot is always
          present in the type structure.

      -- Data: _Py_TPFLAGS_HAVE_VECTORCALL

          This bit is set when the class implements the vectorcall
          protocol.  See *note tp_vectorcall_offset: 3cbc. for details.

          `Inheritance:'

          This bit is set on `static' subtypes if ‘tp_flags’ is not
          overridden: a subtype inherits ‘_Py_TPFLAGS_HAVE_VECTORCALL’
          from its base type when the subtype’s *note tp_call: 3b66. is
          ‘NULL’ and the subtype’s ‘Py_TPFLAGS_HEAPTYPE’ is not set.

          *note Heap types: 40bd. do not inherit
          ‘_Py_TPFLAGS_HAVE_VECTORCALL’.

               備註: This flag is provisional and expected to become
               public in Python 3.9, with a different name and,
               possibly, changed semantics.  If you use vectorcall, plan
               for updating your code for Python 3.9.

          3.8 版新加入.

 -- C 成員函數: const char* PyTypeObject.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 成員函數: traverseproc PyTypeObject.tp_traverse

     An optional pointer to a traversal function for the garbage
     collector.  This is only used if the *note Py_TPFLAGS_HAVE_GC:
     3b48. 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 Supporting Cyclic Garbage Collection: 40c4.

     The *note tp_traverse: 36be. pointer is used by the garbage
     collector to detect reference cycles.  A typical implementation of
     a *note tp_traverse: 36be. function simply calls *note Py_VISIT():
     3b46. on each of the instance’s members that are Python objects
     that the instance owns.  For example, this is function
     ‘local_traverse()’ from the *note _thread: 3. 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(): 3b46. 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: 86. module’s *note get_referents(): eaa. function
     will include it.

          警告: When implementing *note tp_traverse: 36be, only the
          members that the instance `owns' (by having strong references
          to them) must be visited.  For instance, if an object supports
          weak references via the *note tp_weaklist: 3d73. 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(): 3b46. requires the `visit' and `arg'
     parameters to ‘local_traverse()’ to have these specific names;
     don’t name them just anything.

     `Inheritance:'

     Group: *note Py_TPFLAGS_HAVE_GC: 3b48, ‘tp_traverse’, ‘tp_clear’

     This field is inherited by subtypes together with *note tp_clear:
     3b52. and the *note Py_TPFLAGS_HAVE_GC: 3b48. flag bit: the flag
     bit, *note tp_traverse: 36be, and *note tp_clear: 3b52. are all
     inherited from the base type if they are all zero in the subtype.

 -- C 成員函數: inquiry PyTypeObject.tp_clear

     An optional pointer to a clear function for the garbage collector.
     This is only used if the *note Py_TPFLAGS_HAVE_GC: 3b48. flag bit
     is set.  The signature is:

          int tp_clear(PyObject *);

     The *note tp_clear: 3b52. member function is used to break
     reference cycles in cyclic garbage detected by the garbage
     collector.  Taken together, all *note tp_clear: 3b52. functions in
     the system must combine to break all reference cycles.  This is
     subtle, and if in any doubt supply a *note tp_clear: 3b52.
     function.  For example, the tuple type does not implement a *note
     tp_clear: 3b52. function, because it’s possible to prove that no
     reference cycle can be composed entirely of tuples.  Therefore the
     *note tp_clear: 3b52. 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: 3b52.

     Implementations of *note tp_clear: 3b52. 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(): 3b47. macro should be used, because clearing
     references is delicate: the reference to the contained object must
     not be decremented until after the pointer to the contained object
     is set to ‘NULL’.  This is because decrementing the reference count
     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(): 3b47. macro
     performs the operations in a safe order.

     Because the goal of *note tp_clear: 3b52. 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: 3b39. function to invoke *note tp_clear: 3b52.

     More information about Python’s garbage collection scheme can be
     found in section *note Supporting Cyclic Garbage Collection: 40c4.

     `Inheritance:'

     Group: *note Py_TPFLAGS_HAVE_GC: 3b48, ‘tp_traverse’, ‘tp_clear’

     This field is inherited by subtypes together with *note
     tp_traverse: 36be. and the *note Py_TPFLAGS_HAVE_GC: 3b48. flag
     bit: the flag bit, *note tp_traverse: 36be, and *note tp_clear:
     3b52. are all inherited from the base type if they are all zero in
     the subtype.

 -- C 成員函數: richcmpfunc PyTypeObject.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: 2d7.

     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: 3b5f. and for *note
     PyObject_RichCompare(): 3b60.:

     Constant             Comparison
                          
     --------------------------------------
                          
     ‘Py_LT’              ‘<’
                          
                          
     ‘Py_LE’              ‘<=’
                          
                          
     ‘Py_EQ’              ‘==’
                          
                          
     ‘Py_NE’              ‘!=’
                          
                          
     ‘Py_GT’              ‘>’
                          
                          
     ‘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(): 3b60.

          The return value’s reference count is properly incremented.

          On error, sets an exception and returns ‘NULL’ from the
          function.

          3.7 版新加入.

     `Inheritance:'

     Group: ‘tp_hash’, ‘tp_richcompare’

     This field is inherited by subtypes together with *note tp_hash:
     3b65.: a subtype inherits *note tp_richcompare: 3b5f. and *note
     tp_hash: 3b65. when the subtype’s *note tp_richcompare: 3b5f. and
     *note tp_hash: 3b65. are both ‘NULL’.

     `Default:'

     ‘PyBaseObject_Type’ provides a ‘tp_richcompare’ implementation,
     which may be inherited.  However, if only ‘tp_hash’ is defined, not
     even the inherited function is used and instances of the type will
     not be able to participate in any comparisons.

 -- C 成員函數: Py_ssize_t PyTypeObject.tp_weaklistoffset

     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 ‘PyObject_ClearWeakRefs()’ and
     the ‘PyWeakref_*()’ functions.  The instance structure needs to
     include a field of type *note PyObject*: 4bf. which is initialized
     to ‘NULL’.

     Do not confuse this field with *note tp_weaklist: 3d73.; that is
     the list head for weak references to the type object itself.

     `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: 3b68, this should not be a problem.

     When a type defined by a class statement has no *note __slots__:
     e32. declaration, and none of its base types are weakly
     referenceable, the type is made weakly referenceable by adding a
     weak reference list head slot to the instance layout and setting
     the *note tp_weaklistoffset: 3b68. of that slot’s offset.

     When a type’s *note __slots__: e32. declaration contains a slot
     named ‘__weakref__’, that slot becomes the weak reference list head
     for instances of the type, and the slot’s offset is stored in the
     type’s *note tp_weaklistoffset: 3b68.

     When a type’s *note __slots__: e32. declaration does not contain a
     slot named ‘__weakref__’, the type inherits its *note
     tp_weaklistoffset: 3b68. from its base type.

 -- C 成員函數: getiterfunc PyTypeObject.tp_iter

     An optional pointer to a function that returns an iterator for the
     object.  Its presence normally signals that the instances of this
     type are iterable (although sequences may be iterable without this
     function).

     This function has the same signature as *note PyObject_GetIter():
     3cc8.:

          PyObject *tp_iter(PyObject *self);

     `Inheritance:'

     This field is inherited by subtypes.

 -- C 成員函數: iternextfunc PyTypeObject.tp_iternext

     An optional pointer to a function that returns the next item in an
     iterator.  The signature is:

          PyObject *tp_iternext(PyObject *self);

     When the iterator is exhausted, it must return ‘NULL’; a *note
     StopIteration: 48b. 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: e35. 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(): 3d10.

     `Inheritance:'

     This field is inherited by subtypes.

 -- C 成員函數: struct PyMethodDef* PyTypeObject.tp_methods

     An optional pointer to a static ‘NULL’-terminated array of *note
     PyMethodDef: e20. 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: 3d6f. below) containing a method
     descriptor.

     `Inheritance:'

     This field is not inherited by subtypes (methods are inherited
     through a different mechanism).

 -- C 成員函數: struct PyMemberDef* PyTypeObject.tp_members

     An optional pointer to a static ‘NULL’-terminated array of *note
     PyMemberDef: 42b. 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: 3d6f. below) containing a member
     descriptor.

     `Inheritance:'

     This field is not inherited by subtypes (members are inherited
     through a different mechanism).

 -- C 成員函數: struct PyGetSetDef* PyTypeObject.tp_getset

     An optional pointer to a static ‘NULL’-terminated array of *note
     PyGetSetDef: 42c. 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: 3d6f. below) containing a getset
     descriptor.

     `Inheritance:'

     This field is not inherited by subtypes (computed attributes are
     inherited through a different mechanism).

 -- C 成員函數: PyTypeObject* PyTypeObject.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(): 3b37, 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: 3b4a. should be set in the
          extension module’s init function.

     `Inheritance:'

     This field is not inherited by subtypes (obviously).

     `Default:'

     This field defaults to ‘&PyBaseObject_Type’ (which to Python
     programmers is known as the type *note object: 2b1.).

 -- C 成員函數: PyObject* PyTypeObject.tp_dict

     The type’s dictionary is stored here by *note PyType_Ready(): 3b3c.

     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(): 3b3c. 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__(): 145c.).

     `Inheritance:'

     This field is not inherited by subtypes (though the attributes
     defined in here are inherited through a different mechanism).

     `Default:'

     If this field is ‘NULL’, *note PyType_Ready(): 3b3c. will assign a
     new dictionary to it.

          警告: It is not safe to use *note PyDict_SetItem(): 3b1d. on
          or otherwise modify *note tp_dict: 3d6f. with the dictionary
          C-API.

 -- C 成員函數: descrgetfunc PyTypeObject.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 成員函數: descrsetfunc PyTypeObject.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 成員函數: Py_ssize_t PyTypeObject.tp_dictoffset

     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(): 3cae.

     Do not confuse this field with *note tp_dict: 3d6f.; that is the
     dictionary for attributes of the type object itself.

     If the value of this field is greater than zero, it specifies the
     offset from the start of the instance structure.  If the value is
     less than zero, it specifies the offset from the `end' of the
     instance structure.  A negative offset is more expensive to use,
     and should only be used when the instance structure contains a
     variable-length part.  This is used for example to add an instance
     variable dictionary to subtypes of *note str: 335. or *note tuple:
     483.  Note that the *note tp_basicsize: 3b33. field should account
     for the dictionary added to the end in that case, even though the
     dictionary is not included in the basic object layout.  On a system
     with a pointer size of 4 bytes, *note tp_dictoffset: 3d74. should
     be set to ‘-4’ to indicate that the dictionary is at the very end
     of the structure.

     The real dictionary offset in an instance can be computed from a
     negative *note tp_dictoffset: 3d74. as follows:

          dictoffset = tp_basicsize + abs(ob_size)*tp_itemsize + tp_dictoffset
          if dictoffset is not aligned on sizeof(void*):
              round up to sizeof(void*)

     where *note tp_basicsize: 3b33, *note tp_itemsize: 3b32. and *note
     tp_dictoffset: 3d74. are taken from the type object, and ‘ob_size’
     is taken from the instance.  The absolute value is taken because
     ints use the sign of ‘ob_size’ to store the sign of the number.
     (There’s never a need to do this calculation yourself; it is done
     for you by ‘_PyObject_GetDictPtr()’.)

     `Inheritance:'

     This field is inherited by subtypes, but see the rules listed
     below.  A subtype may override this offset; this means that the
     subtype instances store the dictionary at a difference offset than
     the base type.  Since the dictionary is always found via *note
     tp_dictoffset: 3d74, this should not be a problem.

     When a type defined by a class statement has no *note __slots__:
     e32. declaration, and none of its base types has an instance
     variable dictionary, a dictionary slot is added to the instance
     layout and the *note tp_dictoffset: 3d74. is set to that slot’s
     offset.

     When a type defined by a class statement has a *note __slots__:
     e32. declaration, the type inherits its *note tp_dictoffset: 3d74.
     from its base type.

     (Adding a slot named *note __dict__: 501. to the *note __slots__:
     e32. declaration does not have the expected effect, it just causes
     confusion.  Maybe this should be added as a feature just like
     ‘__weakref__’ though.)

     `Default:'

     This slot has no default.  For static types, if the field is ‘NULL’
     then no *note __dict__: 501. gets created for instances.

 -- C 成員函數: initproc PyTypeObject.tp_init

     An optional pointer to an instance initialization function.

     This function corresponds to the *note __init__(): d63. method of
     classes.  Like *note __init__(): d63, it is possible to create an
     instance without calling *note __init__(): d63, and it is possible
     to reinitialize an instance by calling its *note __init__(): d63.
     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__(): d63.

     The *note tp_init: 3b3d. function, if not ‘NULL’, is called when an
     instance is created normally by calling its type, after the type’s
     *note tp_new: 3b36. function has returned an instance of the type.
     If the *note tp_new: 3b36. function returns an instance of some
     other type that is not a subtype of the original type, no *note
     tp_init: 3b3d. function is called; if *note tp_new: 3b36. returns
     an instance of a subtype of the original type, the subtype’s *note
     tp_init: 3b3d. is called.

     Returns ‘0’ on success, ‘-1’ and sets an exception on error.

     `Inheritance:'

     This field is inherited by subtypes.

     `Default:'

     For static types this field does not have a default.

 -- C 成員函數: allocfunc PyTypeObject.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).

     `Default:'

     For dynamic subtypes, this field is always set to *note
     PyType_GenericAlloc(): 271, to force a standard heap allocation
     strategy.

     For static subtypes, ‘PyBaseObject_Type’ uses *note
     PyType_GenericAlloc(): 271.  That is the recommended value for all
     statically defined types.

 -- C 成員函數: newfunc PyTypeObject.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: 3b36. function is called; it
     may be a subtype of that type (but not an unrelated type).

     The *note tp_new: 3b36. 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: 3b3d. handler.  A
     good rule of thumb is that for immutable types, all initialization
     should take place in *note tp_new: 3b36, while for mutable types,
     most initialization should be deferred to *note tp_init: 3b3d.

     `Inheritance:'

     This field is inherited by subtypes, except it is not inherited by
     static types whose *note tp_base: 3b4a. is ‘NULL’ or
     ‘&PyBaseObject_Type’.

     `Default:'

     For static types 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 成員函數: freefunc PyTypeObject.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(): 509.

     `Inheritance:'

     This field is inherited by static subtypes, but not by dynamic
     subtypes (subtypes created by a class statement)

     `Default:'

     In dynamic subtypes, this field is set to a deallocator suitable to
     match *note PyType_GenericAlloc(): 271. and the value of the *note
     Py_TPFLAGS_HAVE_GC: 3b48. flag bit.

     For static subtypes, ‘PyBaseObject_Type’ uses PyObject_Del.

 -- C 成員函數: inquiry PyTypeObject.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: 3d5b. field, and check the *note
     Py_TPFLAGS_HAVE_GC: 3b48. 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: 3d56, defines this function to distinguish
     between statically and dynamically allocated types.)

     `Inheritance:'

     This field is inherited by subtypes.

     `Default:'

     This slot has no default.  If this field is ‘NULL’, *note
     Py_TPFLAGS_HAVE_GC: 3b48. is used as the functional equivalent.

 -- C 成員函數: PyObject* PyTypeObject.tp_bases

     Tuple of base types.

     This is set for types created by a class statement.  It should be
     ‘NULL’ for statically defined types.

     `Inheritance:'

     This field is not inherited.

 -- C 成員函數: PyObject* PyTypeObject.tp_mro

     Tuple containing the expanded set of base types, starting with the
     type itself and ending with *note object: 2b1, in Method Resolution
     Order.

     `Inheritance:'

     This field is not inherited; it is calculated fresh by *note
     PyType_Ready(): 3b3c.

 -- C 成員函數: PyObject* PyTypeObject.tp_cache

     Unused.  Internal use only.

     `Inheritance:'

     This field is not inherited.

 -- C 成員函數: PyObject* PyTypeObject.tp_subclasses

     List of weak references to subclasses.  Internal use only.

     `Inheritance:'

     This field is not inherited.

 -- C 成員函數: PyObject* PyTypeObject.tp_weaklist

     Weak reference list head, for weak references to this type object.
     Not inherited.  Internal use only.

     `Inheritance:'

     This field is not inherited.

 -- C 成員函數: destructor PyTypeObject.tp_del

     This field is deprecated.  Use *note tp_finalize: 2d8. instead.

 -- C 成員函數: unsigned int PyTypeObject.tp_version_tag

     Used to index into the method cache.  Internal use only.

     `Inheritance:'

     This field is not inherited.

 -- C 成員函數: destructor PyTypeObject.tp_finalize

     An optional pointer to an instance finalization function.  Its
     signature is:

          void tp_finalize(PyObject *self);

     If *note tp_finalize: 2d8. 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: 2d8. 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);
          }

     For this field to be taken into account (even through inheritance),
     you must also set the *note Py_TPFLAGS_HAVE_FINALIZE: 2d9. flags
     bit.

     `Inheritance:'

     This field is inherited by subtypes.

     3.4 版新加入.

     也參考
     ......

     "Safe object finalization" ( PEP 442(1))

The remaining fields are only defined if the feature test macro
‘COUNT_ALLOCS’ is defined, and are for internal use only.  They are
documented here for completeness.  None of these fields are inherited by
subtypes.

 -- C 成員函數: Py_ssize_t PyTypeObject.tp_allocs

     Number of allocations.

 -- C 成員函數: Py_ssize_t PyTypeObject.tp_frees

     Number of frees.

 -- C 成員函數: Py_ssize_t PyTypeObject.tp_maxalloc

     Maximum simultaneously allocated objects.

 -- C 成員函數: PyTypeObject* PyTypeObject.tp_prev

     Pointer to the previous type object with a non-zero *note
     tp_allocs: 406f. field.

 -- C 成員函數: PyTypeObject* PyTypeObject.tp_next

     Pointer to the next type object with a non-zero *note tp_allocs:
     406f. field.

Also, note that, in a garbage collected Python, *note tp_dealloc: 3b39.
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.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0442


File: python.info,  Node: Heap Types,  Prev: PyTypeObject Slots,  Up: Type Objects<3>

7.12.3.9 Heap Types
...................

Traditionally, types defined in C code are `static', that is, a static
*note PyTypeObject: 2d7. structure is defined directly in code and
initialized using *note PyType_Ready(): 3b3c.

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: 3c3b,
     so they should not include any subinterpreter-specific state.

Also, since *note PyTypeObject: 2d7. is not part of the *note stable
ABI: 3bbb, any extension modules using static types must be compiled for
a specific Python minor version.

An alternative to static types is `heap-allocated types', or `heap
types' for short, which correspond closely to classes created by
Python’s ‘class’ statement.

This is done by filling a *note PyType_Spec: 3d64. structure and calling
*note PyType_FromSpecWithBases(): 3d62.


File: python.info,  Node: Number Object Structures,  Next: Mapping Object Structures,  Prev: Type Objects<3>,  Up: Object Implementation Support

7.12.4 Number Object Structures
-------------------------------

 -- C 類型: 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 Number Protocol:
     3cca. 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 ‘nb_reserved’ field should always be ‘NULL’.  It was
          previously called ‘nb_long’, and was renamed in Python 3.0.1.

 -- C 成員函數: binaryfunc PyNumberMethods.nb_add

 -- C 成員函數: binaryfunc PyNumberMethods.nb_subtract

 -- C 成員函數: binaryfunc PyNumberMethods.nb_multiply

 -- C 成員函數: binaryfunc PyNumberMethods.nb_remainder

 -- C 成員函數: binaryfunc PyNumberMethods.nb_divmod

 -- C 成員函數: ternaryfunc PyNumberMethods.nb_power

 -- C 成員函數: unaryfunc PyNumberMethods.nb_negative

 -- C 成員函數: unaryfunc PyNumberMethods.nb_positive

 -- C 成員函數: unaryfunc PyNumberMethods.nb_absolute

 -- C 成員函數: inquiry PyNumberMethods.nb_bool

 -- C 成員函數: unaryfunc PyNumberMethods.nb_invert

 -- C 成員函數: binaryfunc PyNumberMethods.nb_lshift

 -- C 成員函數: binaryfunc PyNumberMethods.nb_rshift

 -- C 成員函數: binaryfunc PyNumberMethods.nb_and

 -- C 成員函數: binaryfunc PyNumberMethods.nb_xor

 -- C 成員函數: binaryfunc PyNumberMethods.nb_or

 -- C 成員函數: unaryfunc PyNumberMethods.nb_int

 -- C 成員函數: void *PyNumberMethods.nb_reserved

 -- C 成員函數: unaryfunc PyNumberMethods.nb_float

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_add

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_subtract

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_multiply

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_remainder

 -- C 成員函數: ternaryfunc PyNumberMethods.nb_inplace_power

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_lshift

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_rshift

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_and

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_xor

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_or

 -- C 成員函數: binaryfunc PyNumberMethods.nb_floor_divide

 -- C 成員函數: binaryfunc PyNumberMethods.nb_true_divide

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_floor_divide

 -- C 成員函數: binaryfunc PyNumberMethods.nb_inplace_true_divide

 -- C 成員函數: unaryfunc PyNumberMethods.nb_index

 -- C 成員函數: binaryfunc PyNumberMethods.nb_matrix_multiply

 -- C 成員函數: binaryfunc PyNumberMethods.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 類型: PyMappingMethods

     This structure holds pointers to the functions which an object uses
     to implement the mapping protocol.  It has three members:

 -- C 成員函數: lenfunc PyMappingMethods.mp_length

     This function is used by *note PyMapping_Size(): 1056. and *note
     PyObject_Size(): 3cc4, and has the same signature.  This slot may
     be set to ‘NULL’ if the object has no defined length.

 -- C 成員函數: binaryfunc PyMappingMethods.mp_subscript

     This function is used by *note PyObject_GetItem(): 3bac. and *note
     PySequence_GetSlice(): 3cf4, and has the same signature as
     ‘PyObject_GetItem()’.  This slot must be filled for the *note
     PyMapping_Check(): 3d05. function to return ‘1’, it can be ‘NULL’
     otherwise.

 -- C 成員函數: objobjargproc PyMappingMethods.mp_ass_subscript

     This function is used by *note PyObject_SetItem(): 3baa, *note
     PyObject_DelItem(): 3cc6, ‘PyObject_SetSlice()’ and
     ‘PyObject_DelSlice()’.  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 類型: PySequenceMethods

     This structure holds pointers to the functions which an object uses
     to implement the sequence protocol.

 -- C 成員函數: lenfunc PySequenceMethods.sq_length

     This function is used by *note PySequence_Size(): 1052. and *note
     PyObject_Size(): 3cc4, and has the same signature.  It is also used
     for handling negative indices via the *note sq_item: 40a5. and the
     *note sq_ass_item: 40a6. slots.

 -- C 成員函數: binaryfunc PySequenceMethods.sq_concat

     This function is used by *note PySequence_Concat(): 3cf0. and has
     the same signature.  It is also used by the ‘+’ operator, after
     trying the numeric addition via the *note nb_add: 3d6d. slot.

 -- C 成員函數: ssizeargfunc PySequenceMethods.sq_repeat

     This function is used by *note PySequence_Repeat(): 3cf1. and has
     the same signature.  It is also used by the ‘*’ operator, after
     trying numeric multiplication via the *note nb_multiply: 407d.
     slot.

 -- C 成員函數: ssizeargfunc PySequenceMethods.sq_item

     This function is used by *note PySequence_GetItem(): 1053. and has
     the same signature.  It is also used by *note PyObject_GetItem():
     3bac, after trying the subscription via the *note mp_subscript:
     409f. slot.  This slot must be filled for the *note
     PySequence_Check(): 3cee. function to return ‘1’, it can be ‘NULL’
     otherwise.

     Negative indexes are handled as follows: if the ‘sq_length’ slot is
     filled, it is called and the sequence length is used to compute a
     positive index which is passed to ‘sq_item’.  If ‘sq_length’ is
     ‘NULL’, the index is passed as is to the function.

 -- C 成員函數: ssizeobjargproc PySequenceMethods.sq_ass_item

     This function is used by *note PySequence_SetItem(): 1054. and has
     the same signature.  It is also used by *note PyObject_SetItem():
     3baa. and *note PyObject_DelItem(): 3cc6, after trying the item
     assignment and deletion via the *note mp_ass_subscript: 40a0. slot.
     This slot may be left to ‘NULL’ if the object does not support item
     assignment and deletion.

 -- C 成員函數: objobjproc PySequenceMethods.sq_contains

     This function may be used by *note PySequence_Contains(): 3cf8. 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 成員函數: binaryfunc PySequenceMethods.sq_inplace_concat

     This function is used by *note PySequence_InPlaceConcat(): 3cf2.
     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(): 3cf0.  It is also used by the augmented
     assignment ‘+=’, after trying numeric in-place addition via the
     *note nb_inplace_add: 407a. slot.

 -- C 成員函數: ssizeargfunc PySequenceMethods.sq_inplace_repeat

     This function is used by *note PySequence_InPlaceRepeat(): 3cf3.
     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(): 3cf1.  It is also used by the augmented
     assignment ‘*=’, after trying numeric in-place multiplication via
     the *note nb_inplace_multiply: 407e. 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 類型: PyBufferProcs

     This structure holds pointers to the functions required by the
     *note Buffer protocol: 15ec.  The protocol defines how an exporter
     object can expose its internal data to consumer objects.

 -- C 成員函數: getbufferproc PyBufferProcs.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
          ‘PyExc_BufferError’, 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. Return ‘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: 3d14, the rules how an exporter must react to
     specific requests are in section *note Buffer request types: 3d28.

     All memory pointed to in the *note Py_buffer: b20. structure
     belongs to the exporter and must remain valid until there are no
     consumers left.  *note format: 3d21, *note shape: 3d23, *note
     strides: 3d18, *note suboffsets: 3d25. and *note internal: 3d27.
     are read-only for the consumer.

     *note PyBuffer_FillInfo(): 3d1b. provides an easy way of exposing a
     simple bytes buffer while dealing correctly with all request types.

     *note PyObject_GetBuffer(): d2a. is the interface for the consumer
     that wraps this function.

 -- C 成員函數: releasebufferproc PyBufferProcs.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: 3c76. 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: 3d27. 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(): d59. (this scheme is
     useful for breaking reference cycles).

     *note PyBuffer_Release(): d59. 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 類型: PyAsyncMethods

     This structure holds pointers to the functions required to
     implement *note awaitable: 51e. and *note asynchronous iterator:
     64a. objects.

     Here is the structure definition:

          typedef struct {
              unaryfunc am_await;
              unaryfunc am_aiter;
              unaryfunc am_anext;
          } PyAsyncMethods;

 -- C 成員函數: unaryfunc PyAsyncMethods.am_await

     The signature of this function is:

          PyObject *am_await(PyObject *self);

     The returned object must be an iterator, i.e.  *note
     PyIter_Check(): 1015. must return ‘1’ for it.

     This slot may be set to ‘NULL’ if an object is not an *note
     awaitable: 51e.

 -- C 成員函數: unaryfunc PyAsyncMethods.am_aiter

     The signature of this function is:

          PyObject *am_aiter(PyObject *self);

     Must return an *note awaitable: 51e. object.  See *note
     __anext__(): 149a. for details.

     This slot may be set to ‘NULL’ if an object does not implement
     asynchronous iteration protocol.

 -- C 成員函數: unaryfunc PyAsyncMethods.am_anext

     The signature of this function is:

          PyObject *am_anext(PyObject *self);

     Must return an *note awaitable: 51e. object.  See *note
     __anext__(): 149a. for details.  This slot may be set to ‘NULL’.


File: python.info,  Node: Slot Type typedefs,  Next: Examples<35>,  Prev: Async Object Structures,  Up: Object Implementation Support

7.12.9 Slot Type typedefs
-------------------------

 -- C 類型: PyObject *(*allocfunc) (PyTypeObject *cls,
          Py_ssize_t nitems)

     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 ‘ob_refcnt’ set to ‘1’ and ‘ob_type’
     set to the type argument.  If the type’s *note tp_itemsize: 3b32.
     is non-zero, the object’s ‘ob_size’ 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: 3b33.

     This function should not do any other instance initialization, not
     even to allocate additional memory; that should be done by *note
     tp_new: 3b36.

 -- C 類型: void (*destructor) (PyObject *)

 -- C 類型: PyObject *(*vectorcallfunc) (PyObject *callable, PyObject
          *const *args, size_t nargsf, PyObject *kwnames)

     See *note tp_vectorcall_offset: 3cbc.

     Arguments to ‘vectorcallfunc’ are the same as for *note
     _PyObject_Vectorcall(): 3cbb.

     3.8 版新加入.

 -- C 類型: void (*freefunc) (void *)

     See *note tp_free: 3b3a.

 -- C 類型: PyObject *(*newfunc) (PyObject *, PyObject *, PyObject *)

     See *note tp_new: 3b36.

 -- C 類型: int (*initproc) (PyObject *, PyObject *, PyObject *)

     See *note tp_init: 3b3d.

 -- C 類型: PyObject *(*reprfunc) (PyObject *)

     See *note tp_repr: 3b54.

 -- C 類型: PyObject *(*getattrfunc) (PyObject *self, char *attr)

     Return the value of the named attribute for the object.

 -- C 類型: int (*setattrfunc) (PyObject *self, char *attr,
          PyObject *value)

     Set the value of the named attribute for the object.  The value
     argument is set to ‘NULL’ to delete the attribute.

 -- C 類型: PyObject *(*getattrofunc) (PyObject *self, PyObject *attr)

     Return the value of the named attribute for the object.

     See *note tp_getattro: 3b59.

 -- C 類型: int (*setattrofunc) (PyObject *self, PyObject *attr,
          PyObject *value)

     Set the value of the named attribute for the object.  The value
     argument is set to ‘NULL’ to delete the attribute.

     See *note tp_setattro: 3b5a.

 -- C 類型: PyObject *(*descrgetfunc) (PyObject *, PyObject *,
          PyObject *)

     See ‘tp_descrget’.

 -- C 類型: int (*descrsetfunc) (PyObject *, PyObject *, PyObject *)

     See ‘tp_descrset’.

 -- C 類型: Py_hash_t (*hashfunc) (PyObject *)

     See *note tp_hash: 3b65.

 -- C 類型: PyObject *(*richcmpfunc) (PyObject *, PyObject *, int)

     See *note tp_richcompare: 3b5f.

 -- C 類型: PyObject *(*getiterfunc) (PyObject *)

     See *note tp_iter: e35.

 -- C 類型: PyObject *(*iternextfunc) (PyObject *)

     See *note tp_iternext: e36.

 -- C 類型: Py_ssize_t (*lenfunc) (PyObject *)

 -- C 類型: int (*getbufferproc) (PyObject *, Py_buffer *, int)

 -- C 類型: void (*releasebufferproc) (PyObject *, Py_buffer *)

 -- C 類型: PyObject *(*unaryfunc) (PyObject *)

 -- C 類型: PyObject *(*binaryfunc) (PyObject *, PyObject *)

 -- C 類型: PyObject *(*ternaryfunc) (PyObject *, PyObject *,
          PyObject *)

 -- C 類型: PyObject *(*ssizeargfunc) (PyObject *, Py_ssize_t)

 -- C 類型: int (*ssizeobjargproc) (PyObject *, Py_ssize_t)

 -- C 類型: int (*objobjproc) (PyObject *, PyObject *)

 -- C 類型: int (*objobjargproc) (PyObject *, PyObject *, PyObject *)


File: python.info,  Node: Examples<35>,  Next: Supporting Cyclic Garbage Collection,  Prev: Slot Type typedefs,  Up: Object Implementation Support

7.12.10 Examples
----------------

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: 3b2b. and *note Defining Extension
Types; Assorted Topics: 3b4e.

A basic static type:

     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 = "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 */
         "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;
         PyObject *inst_dict;
         PyObject *weakreflist;
     } MyObject;

     static PyTypeObject MyObject_Type = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "mymod.MyObject",
         .tp_basicsize = sizeof(MyObject),
         .tp_doc = "My objects",
         .tp_weaklistoffset = offsetof(MyObject, weakreflist),
         .tp_dictoffset = offsetof(MyObject, inst_dict),
         .tp_flags = Py_TPFLAGS_DEFAULT | Py_TPFLAGS_BASETYPE | Py_TPFLAGS_HAVE_GC,
         .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):

     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 = "my custom str",
         .tp_flags = Py_TPFLAGS_DEFAULT,
         .tp_new = NULL,
         .tp_repr = (reprfunc)myobj_repr,
     };

The simplest static type (with fixed-length instances):

     typedef struct {
         PyObject_HEAD
     } MyObject;

     static PyTypeObject MyObject_Type = {
         PyVarObject_HEAD_INIT(NULL, 0)
         .tp_name = "mymod.MyObject",
     };

The simplest static type (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: Supporting Cyclic Garbage Collection,  Prev: Examples<35>,  Up: Object Implementation Support

7.12.11 Supporting Cyclic Garbage Collection
--------------------------------------------

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: 3d5b. field of the type
object must include the *note Py_TPFLAGS_HAVE_GC: 3b48. and provide an
implementation of the *note tp_traverse: 36be. handler.  If instances of
the type are mutable, a *note tp_clear: 3b52. implementation must also
be provided.

 -- Data: Py_TPFLAGS_HAVE_GC

     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(): 2d5. or *note PyObject_GC_NewVar(): 2d6.

  2. Once all the fields which may contain references to other
     containers are initialized, it must call *note PyObject_GC_Track():
     e49.

 -- C 函式: TYPE* PyObject_GC_New (TYPE, PyTypeObject *type)

     Analogous to *note PyObject_New(): 2d3. but for container objects
     with the *note Py_TPFLAGS_HAVE_GC: 3b48. flag set.

 -- C 函式: TYPE* PyObject_GC_NewVar (TYPE, PyTypeObject *type,
          Py_ssize_t size)

     Analogous to *note PyObject_NewVar(): 2d4. but for container
     objects with the *note Py_TPFLAGS_HAVE_GC: 3b48. flag set.

 -- C 函式: TYPE* PyObject_GC_Resize (TYPE, PyVarObject *op,
          Py_ssize_t newsize)

     Resize an object allocated by *note PyObject_NewVar(): 2d4.
     Returns the resized object or ‘NULL’ on failure.  `op' must not be
     tracked by the collector yet.

 -- C 函式: void PyObject_GC_Track (PyObject *op)

     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: 36be. handler become
     valid, usually near the end of the constructor.

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(): e4a. must be called.

  2. The object’s memory must be deallocated using *note
     PyObject_GC_Del(): e48.

 -- C 函式: void PyObject_GC_Del (void *op)

     Releases memory allocated to an object using *note
     PyObject_GC_New(): 2d5. or *note PyObject_GC_NewVar(): 2d6.

 -- C 函式: void PyObject_GC_UnTrack (void *op)

     Remove the object `op' from the set of container objects tracked by
     the collector.  Note that *note PyObject_GC_Track(): e49. can be
     called again on this object to add it back to the set of tracked
     objects.  The deallocator (*note tp_dealloc: 3b39. handler) should
     call this for the object before any of the fields used by the *note
     tp_traverse: 36be. 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: 36be. handler accepts a function parameter of
this type:

 -- C 類型: int (*visitproc) (PyObject *object, void *arg)

     Type of the visitor function passed to the *note tp_traverse: 36be.
     handler.  The function should be called with an object to traverse
     as `object' and the third parameter to the *note tp_traverse: 36be.
     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: 36be. handler must have the following type:

 -- C 類型: int (*traverseproc) (PyObject *self, visitproc visit,
          void *arg)

     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: 36be. handlers, a *note
Py_VISIT(): 3b46. macro is provided.  In order to use this macro, the
*note tp_traverse: 36be. 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: 36be. 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: 3b52. handler must be of the *note inquiry: 405f.
type, or ‘NULL’ if the object is immutable.

 -- C 類型: int (*inquiry) (PyObject *self)

     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(): 267. on a reference).  The collector will call this
     method if it detects that this object is involved in a reference
     cycle.


File: python.info,  Node: API and ABI Versioning,  Prev: Object Implementation Support,  Up: Python / C API 參考手冊

7.13 API and ABI Versioning
===========================

‘PY_VERSION_HEX’ is the Python version number encoded in a single
integer.

For example if the ‘PY_VERSION_HEX’ is set to ‘0x030401a2’, the
underlying version information can be found by treating it as a 32 bit
number in the following manner:

     Bytes       Bits (big endian order)       Meaning
                                               
     -----------------------------------------------------------------------------------------------
                                               
     ‘1’         ‘1-8’                         ‘PY_MAJOR_VERSION’ (the ‘3’ in ‘3.4.1a2’)
                                               
                                               
     ‘2’         ‘9-16’                        ‘PY_MINOR_VERSION’ (the ‘4’ in ‘3.4.1a2’)
                                               
                                               
     ‘3’         ‘17-24’                       ‘PY_MICRO_VERSION’ (the ‘1’ in ‘3.4.1a2’)
                                               
                                               
     ‘4’         ‘25-28’                       ‘PY_RELEASE_LEVEL’ (‘0xA’ for alpha, ‘0xB’ for
                                               beta, ‘0xC’ for release candidate and ‘0xF’ for
                                               final), in this case it is alpha.
                                               
                                               
                 ‘29-32’                       ‘PY_RELEASE_SERIAL’ (the ‘2’ in ‘3.4.1a2’, zero
                                               for final releases)
                                               

Thus ‘3.4.1a2’ is hexversion ‘0x030401a2’.

All the given macros are defined in Include/patchlevel.h(1).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Include/patchlevel.h


File: python.info,  Node: 發布 Python 模組,  Next: 安裝 Python 模組,  Prev: Python / C API 參考手冊,  Up: Top

8 發布 Python 模組
******************


Email: <distutils-sig@python.org>

As a popular open source development project, Python has an active
supporting community of contributors and users that also make their
software available for other Python developers to use under open source
license terms.

This allows Python users to share and collaborate effectively,
benefiting from the solutions others have already created to common (and
sometimes even rare!)  problems, as well as potentially contributing
their own solutions to the common pool.

This guide covers the distribution part of the process.  For a guide to
installing other Python projects, refer to the *note installation guide:
7fa.

     備註: For corporate and other institutional users, be aware that
     many organisations have their own policies around using and
     contributing to open source software.  Please take such policies
     into account when making use of the distribution and installation
     tools provided with Python.

* Menu:

* Key terms::
* Open source licensing and collaboration::
* Installing the tools::
* Reading the Python Packaging User Guide::
* How do I...?: How do I ?.


File: python.info,  Node: Key terms,  Next: Open source licensing and collaboration,  Up: 發布 Python 模組

8.1 Key terms
=============

   * the Python Packaging Index(1) is a public repository of open source
     licensed packages made available for use by other Python users

   * the Python Packaging Authority(2) are the group of developers and
     documentation authors responsible for the maintenance and evolution
     of the standard packaging tools and the associated metadata and
     file format standards.  They maintain a variety of tools,
     documentation and issue trackers on both GitHub(3) and
     Bitbucket(4).

   * *note distutils: 39. is the original build and distribution system
     first added to the Python standard library in 1998.  While direct
     use of *note distutils: 39. is being phased out, it still laid the
     foundation for the current packaging and distribution
     infrastructure, and it not only remains part of the standard
     library, but its name lives on in other ways (such as the name of
     the mailing list used to coordinate Python packaging standards
     development).

   * setuptools(5) is a (largely) drop-in replacement for *note
     distutils: 39. first published in 2004.  Its most notable addition
     over the unmodified *note distutils: 39. tools was the ability to
     declare dependencies on other packages.  It is currently
     recommended as a more regularly updated alternative to *note
     distutils: 39. that offers consistent support for more recent
     packaging standards across a wide range of Python versions.

   * wheel(6) (in this context) is a project that adds the ‘bdist_wheel’
     command to *note distutils: 39./setuptools(7).  This produces a
     cross platform binary packaging format (called "wheels" or "wheel
     files" and defined in PEP 427(8)) that allows Python libraries,
     even those including binary extensions, to be installed on a system
     without needing to be built locally.

   ---------- Footnotes ----------

   (1) https://pypi.org

   (2) https://www.pypa.io/

   (3) https://github.com/pypa

   (4) https://bitbucket.org/pypa/

   (5) https://setuptools.readthedocs.io/en/latest/

   (6) https://wheel.readthedocs.io/

   (7) https://setuptools.readthedocs.io/en/latest/

   (8) https://www.python.org/dev/peps/pep-0427


File: python.info,  Node: Open source licensing and collaboration,  Next: Installing the tools,  Prev: Key terms,  Up: 發布 Python 模組

8.2 Open source licensing and collaboration
===========================================

In most parts of the world, software is automatically covered by
copyright.  This means that other developers require explicit permission
to copy, use, modify and redistribute the software.

Open source licensing is a way of explicitly granting such permission in
a relatively consistent way, allowing developers to share and
collaborate efficiently by making common solutions to various problems
freely available.  This leaves many developers free to spend more time
focusing on the problems that are relatively unique to their specific
situation.

The distribution tools provided with Python are designed to make it
reasonably straightforward for developers to make their own
contributions back to that common pool of software if they choose to do
so.

The same distribution tools can also be used to distribute software
within an organisation, regardless of whether that software is published
as open source software or not.


File: python.info,  Node: Installing the tools,  Next: Reading the Python Packaging User Guide,  Prev: Open source licensing and collaboration,  Up: 發布 Python 模組

8.3 Installing the tools
========================

The standard library does not include build tools that support modern
Python packaging standards, as the core development team has found that
it is important to have standard tools that work consistently, even on
older versions of Python.

The currently recommended build and distribution tools can be installed
by invoking the ‘pip’ module at the command line:

     python -m pip install setuptools wheel twine

     備註: For POSIX users (including Mac OS X and Linux users), these
     instructions assume the use of a *note virtual environment: 1317.

     For Windows users, these instructions assume that the option to
     adjust the system PATH environment variable was selected when
     installing Python.

The Python Packaging User Guide includes more details on the currently
recommended tools(1).

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/guides/tool-recommendations/#packaging-tool-recommendations


File: python.info,  Node: Reading the Python Packaging User Guide,  Next: How do I ?,  Prev: Installing the tools,  Up: 發布 Python 模組

8.4 Reading the Python Packaging User Guide
===========================================

The Python Packaging User Guide covers the various key steps and
elements involved in creating and publishing a project:

   * Project structure(1)

   * Building and packaging the project(2)

   * Uploading the project to the Python Packaging Index(3)

   * The .pypirc file(4)

   ---------- Footnotes ----------

   (1) https://packaging.python.org/tutorials/distributing-packages/

   (2) 
https://packaging.python.org/tutorials/distributing-packages/#packaging-your-project

   (3) 
https://packaging.python.org/tutorials/distributing-packages/#uploading-your-project-to-pypi

   (4) https://packaging.python.org/specifications/pypirc/


File: python.info,  Node: How do I ?,  Prev: Reading the Python Packaging User Guide,  Up: 發布 Python 模組

8.5 How do I...?
================

These are quick answers or links for some common tasks.

* Menu:

* ... choose a name for my project?: choose a name for my project?.
* ... create and distribute binary extensions?: create and distribute binary extensions?.


File: python.info,  Node: choose a name for my project?,  Next: create and distribute binary extensions?,  Up: How do I ?

8.5.1 ... choose a name for my project?
---------------------------------------

This isn’t an easy topic, but here are a few tips:

   * check the Python Packaging Index to see if the name is already in
     use

   * check popular hosting sites like GitHub, Bitbucket, etc to see if
     there is already a project with that name

   * check what comes up in a web search for the name you’re considering

   * avoid particularly common words, especially ones with multiple
     meanings, as they can make it difficult for users to find your
     software when searching for it


File: python.info,  Node: create and distribute binary extensions?,  Prev: choose a name for my project?,  Up: How do I ?

8.5.2 ... create and distribute binary extensions?
--------------------------------------------------

This is actually quite a complex topic, with a variety of alternatives
available depending on exactly what you’re aiming to achieve.  See the
Python Packaging User Guide for more information and recommendations.

也參考
......

Python Packaging User Guide: Binary Extensions(1)

   ---------- Footnotes ----------

   (1) https://packaging.python.org/guides/packaging-binary-extensions/


File: python.info,  Node: 安裝 Python 模組,  Next: Python HOWTOs,  Prev: 發布 Python 模組,  Up: Top

9 安裝 Python 模組
******************


Email: <distutils-sig@python.org>

As a popular open source development project, Python has an active
supporting community of contributors and users that also make their
software available for other Python developers to use under open source
license terms.

This allows Python users to share and collaborate effectively,
benefiting from the solutions others have already created to common (and
sometimes even rare!)  problems, as well as potentially contributing
their own solutions to the common pool.

This guide covers the installation part of the process.  For a guide to
creating and sharing your own Python projects, refer to the *note
distribution guide: 7fb.

     備註: For corporate and other institutional users, be aware that
     many organisations have their own policies around using and
     contributing to open source software.  Please take such policies
     into account when making use of the distribution and installation
     tools provided with Python.

* Menu:

* Key terms: Key terms<2>.
* Basic usage::
* How do I ...?: How do I ?<2>.
* Common installation issues::


File: python.info,  Node: Key terms<2>,  Next: Basic usage,  Up: 安裝 Python 模組

9.1 Key terms
=============

   * ‘pip’ is the preferred installer program.  Starting with Python
     3.4, it is included by default with the Python binary installers.

   * A `virtual environment' is a semi-isolated Python environment that
     allows packages to be installed for use by a particular
     application, rather than being installed system wide.

   * ‘venv’ is the standard tool for creating virtual environments, and
     has been part of Python since Python 3.3.  Starting with Python
     3.4, it defaults to installing ‘pip’ into all created virtual
     environments.

   * ‘virtualenv’ is a third party alternative (and predecessor) to
     ‘venv’.  It allows virtual environments to be used on versions of
     Python prior to 3.4, which either don’t provide ‘venv’ at all, or
     aren’t able to automatically install ‘pip’ into created
     environments.

   * The Python Packaging Index(1) is a public repository of open source
     licensed packages made available for use by other Python users.

   * the Python Packaging Authority(2) is the group of developers and
     documentation authors responsible for the maintenance and evolution
     of the standard packaging tools and the associated metadata and
     file format standards.  They maintain a variety of tools,
     documentation, and issue trackers on both GitHub(3) and
     Bitbucket(4).

   * ‘distutils’ is the original build and distribution system first
     added to the Python standard library in 1998.  While direct use of
     ‘distutils’ is being phased out, it still laid the foundation for
     the current packaging and distribution infrastructure, and it not
     only remains part of the standard library, but its name lives on in
     other ways (such as the name of the mailing list used to coordinate
     Python packaging standards development).

3.5 版更變: The use of ‘venv’ is now recommended for creating virtual
environments.

也參考
......

Python Packaging User Guide: Creating and using virtual environments(5)

   ---------- Footnotes ----------

   (1) https://pypi.org

   (2) https://www.pypa.io/

   (3) https://github.com/pypa

   (4) https://bitbucket.org/pypa/

   (5) 
https://packaging.python.org/installing/#creating-virtual-environments


File: python.info,  Node: Basic usage,  Next: How do I ?<2>,  Prev: Key terms<2>,  Up: 安裝 Python 模組

9.2 Basic usage
===============

The standard packaging tools are all designed to be used from the
command line.

The following command will install the latest version of a module and
its dependencies from the Python Packaging Index:

     python -m pip install SomePackage

     備註: For POSIX users (including Mac OS X and Linux users), the
     examples in this guide assume the use of a *note virtual
     environment: 1317.

     For Windows users, the examples in this guide assume that the
     option to adjust the system PATH environment variable was selected
     when installing Python.

It’s also possible to specify an exact or minimum version directly on
the command line.  When using comparator operators such as ‘>’, ‘<’ or
some other special character which get interpreted by shell, the package
name and the version should be enclosed within double quotes:

     python -m pip install SomePackage==1.0.4    # specific version
     python -m pip install "SomePackage>=1.0.4"  # minimum version

Normally, if a suitable module is already installed, attempting to
install it again will have no effect.  Upgrading existing modules must
be requested explicitly:

     python -m pip install --upgrade SomePackage

More information and resources regarding ‘pip’ and its capabilities can
be found in the Python Packaging User Guide(1).

Creation of virtual environments is done through the *note venv: 126.
module.  Installing packages into an active virtual environment uses the
commands shown above.

也參考
......

Python Packaging User Guide: Installing Python Distribution Packages(2)

   ---------- Footnotes ----------

   (1) https://packaging.python.org

   (2) https://packaging.python.org/installing/


File: python.info,  Node: How do I ?<2>,  Next: Common installation issues,  Prev: Basic usage,  Up: 安裝 Python 模組

9.3 How do I ...?
=================

These are quick answers or links for some common tasks.

* Menu:

* ... install pip in versions of Python prior to Python 3.4?: install pip in versions of Python prior to Python 3 4?.
* ... install packages just for the current user?: install packages just for the current user?.
* ... install scientific Python packages?: install scientific Python packages?.
* ... work with multiple versions of Python installed in parallel?: work with multiple versions of Python installed in parallel?.


File: python.info,  Node: install pip in versions of Python prior to Python 3 4?,  Next: install packages just for the current user?,  Up: How do I ?<2>

9.3.1 ... install ‘pip’ in versions of Python prior to Python 3.4?
------------------------------------------------------------------

Python only started bundling ‘pip’ with Python 3.4.  For earlier
versions, ‘pip’ needs to be "bootstrapped" as described in the Python
Packaging User Guide.

也參考
......

Python Packaging User Guide: Requirements for Installing Packages(1)

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/installing/#requirements-for-installing-packages


File: python.info,  Node: install packages just for the current user?,  Next: install scientific Python packages?,  Prev: install pip in versions of Python prior to Python 3 4?,  Up: How do I ?<2>

9.3.2 ... install packages just for the current user?
-----------------------------------------------------

Passing the ‘--user’ option to ‘python -m pip install’ will install a
package just for the current user, rather than for all users of the
system.


File: python.info,  Node: install scientific Python packages?,  Next: work with multiple versions of Python installed in parallel?,  Prev: install packages just for the current user?,  Up: How do I ?<2>

9.3.3 ... install scientific Python packages?
---------------------------------------------

A number of scientific Python packages have complex binary dependencies,
and aren’t currently easy to install using ‘pip’ directly.  At this
point in time, it will often be easier for users to install these
packages by other means(1) rather than attempting to install them with
‘pip’.

也參考
......

Python Packaging User Guide: Installing Scientific Packages(2)

   ---------- Footnotes ----------

   (1) https://packaging.python.org/science/

   (2) https://packaging.python.org/science/


File: python.info,  Node: work with multiple versions of Python installed in parallel?,  Prev: install scientific Python packages?,  Up: How do I ?<2>

9.3.4 ... work with multiple versions of Python installed in parallel?
----------------------------------------------------------------------

On Linux, Mac OS X, and other POSIX systems, use the versioned Python
commands in combination with the ‘-m’ switch to run the appropriate copy
of ‘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

Appropriately versioned ‘pip’ commands may also be available.

On Windows, use the ‘py’ Python launcher in combination with the ‘-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: Common installation issues,  Prev: How do I ?<2>,  Up: 安裝 Python 模組

9.4 Common installation issues
==============================

* Menu:

* Installing into the system Python on Linux::
* Pip not installed::
* Installing binary extensions::


File: python.info,  Node: Installing into the system Python on Linux,  Next: Pip not installed,  Up: Common installation issues

9.4.1 Installing into the system Python on Linux
------------------------------------------------

On Linux systems, a Python installation will typically be included as
part of the distribution.  Installing into this Python installation
requires root access to the system, and may interfere with the operation
of the system package manager and other components of the system if a
component is unexpectedly upgraded using ‘pip’.

On such systems, it is often better to use a virtual environment or a
per-user installation when installing packages with ‘pip’.


File: python.info,  Node: Pip not installed,  Next: Installing binary extensions,  Prev: Installing into the system Python on Linux,  Up: Common installation issues

9.4.2 Pip not installed
-----------------------

It is possible that ‘pip’ does not get installed by default.  One
potential fix is:

     python -m ensurepip --default-pip

There are also additional resources for installing pip.(1)

   ---------- Footnotes ----------

   (1) 
https://packaging.python.org/tutorials/installing-packages/#install-pip-setuptools-and-wheel


File: python.info,  Node: Installing binary extensions,  Prev: Pip not installed,  Up: Common installation issues

9.4.3 Installing binary extensions
----------------------------------

Python has typically relied heavily on source based distribution, with
end users being expected to compile extension modules from source as
part of the installation process.

With the introduction of support for the binary ‘wheel’ format, and the
ability to publish wheels for at least Windows and Mac OS X through the
Python Packaging Index, this problem is expected to diminish over time,
as users are more regularly able to install pre-built extensions rather
than needing to build them themselves.

Some of the solutions for installing scientific software(1) that are not
yet available as pre-built ‘wheel’ files may also help with obtaining
other binary extensions without needing to build them locally.

也參考
......

Python Packaging User Guide: Binary Extensions(2)

   ---------- Footnotes ----------

   (1) https://packaging.python.org/science/

   (2) https://packaging.python.org/extensions/


File: python.info,  Node: Python HOWTOs,  Next: Python 常見問題,  Prev: 安裝 Python 模組,  Up: Top

10 Python HOWTOs
****************

Python HOWTOs are documents that cover a single, specific topic, and
attempt to cover it fairly completely.  Modelled 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.

Currently, the HOWTOs are:

* Menu:

* Python 2 的程式碼移植到Python 3::
* 遷移延伸模組到 Python 3::
* Curses Programming with Python::
* 修飾器 HowTo 指南::
* 函式編程 HOWTO::
* 如何使用 Logging 模組::
* Logging Cookbook::
* 如何使用正規表達式::
* Socket Programming HOWTO::
* 如何排序::
* Unicode HOWTO::
* 如何使用urllib套件取得網路資源::
* Argparse 教學::
* ipaddress模組介紹::
* Argument Clinic How-To::
* Instrumenting CPython with DTrace and SystemTap::


File: python.info,  Node: Python 2 的程式碼移植到Python 3,  Next: 遷移延伸模組到 Python 3,  Up: Python HOWTOs

10.1 Python 2 的程式碼移植到Python 3
====================================


author: Brett Cannon

Abstract
........

With Python 3 being the future of Python while Python 2 is still in
active use, it is good to have your project available for both major
releases of Python.  This guide is meant to help you figure out how best
to support both Python 2 & 3 simultaneously.

If you are looking to port an extension module instead of pure Python
code, please see *note 遷移延伸模組到 Python 3: c7c.

If you would like to read one core Python developer’s take on why Python
3 came into existence, you can read Nick Coghlan’s Python 3 Q & A(1) or
Brett Cannon’s Why Python 3 exists(2).

For help with porting, you can email the python-porting(3) mailing list
with questions.

* Menu:

* 簡短的說明::
* 詳細的::

   ---------- Footnotes ----------

   (1) 
https://ncoghlan-devs-python-notes.readthedocs.io/en/latest/python3/questions_and_answers.html

   (2) https://snarky.ca/why-python-3-exists

   (3) https://mail.python.org/mailman/listinfo/python-porting


File: python.info,  Node: 簡短的說明,  Next: 詳細的,  Up: Python 2 的程式碼移植到Python 3

10.1.1 簡短的說明
-----------------

To make your project be single-source Python 2/3 compatible, the basic
steps are:

  1. Only worry about supporting Python 2.7

  2. Make sure you have good test coverage (coverage.py(1) can help;
     ‘pip install coverage’)

  3. 瞭解Python 2 & 3的差異

  4. Use Futurize(2) (or Modernize(3)) to update your code (e.g.  ‘pip
     install future’)

  5. Use Pylint(4) to help make sure you don’t regress on your Python 3
     support (‘pip install pylint’)

  6. Use caniusepython3(5) to find out which of your dependencies are
     blocking your use of Python 3 (‘pip install caniusepython3’)

  7. Once your dependencies are no longer blocking you, use continuous
     integration to make sure you stay compatible with Python 2 & 3
     (tox(6) can help test against multiple versions of Python; ‘pip
     install tox’)

  8. Consider using optional static type checking to make sure your type
     usage works in both Python 2 & 3 (e.g.  use mypy(7) to check your
     typing under both Python 2 & Python 3).

   ---------- Footnotes ----------

   (1) https://pypi.org/project/coverage

   (2) http://python-future.org/automatic_conversion.html

   (3) https://python-modernize.readthedocs.io/

   (4) https://pypi.org/project/pylint

   (5) https://pypi.org/project/caniusepython3

   (6) https://pypi.org/project/tox

   (7) http://mypy-lang.org/


File: python.info,  Node: 詳細的,  Prev: 簡短的說明,  Up: Python 2 的程式碼移植到Python 3

10.1.2 詳細的
-------------

A key point about supporting Python 2 & 3 simultaneously is that you can
start `today'!  Even if your dependencies are not supporting Python 3
yet that does not mean you can’t modernize your code `now' to support
Python 3.  Most changes required to support Python 3 lead to cleaner
code using newer practices even in Python 2 code.

Another key point is that modernizing your Python 2 code to also support
Python 3 is largely automated for you.  While you might have to make
some API decisions thanks to Python 3 clarifying text data versus binary
data, the lower-level work is now mostly done for you and thus can at
least benefit from the automated changes immediately.

Keep those key points in mind while you read on about the details of
porting your code to support Python 2 & 3 simultaneously.

* Menu:

* 向下支援Python 2.6和更舊的版本: 向下支援Python 2 6和更舊的版本.
* Make sure you specify the proper version support in your setup.py file: Make sure you specify the proper version support in your setup py file.
* 有好的測試覆蓋率::
* 瞭解Python 2 & 3的差異::
* 更新你的程式碼::
* Prevent compatibility regressions::
* Check which dependencies block your transition::
* Update your setup.py file to denote Python 3 compatibility: Update your setup py file to denote Python 3 compatibility.
* Use continuous integration to stay compatible::
* Consider using optional static type checking::


File: python.info,  Node: 向下支援Python 2 6和更舊的版本,  Next: Make sure you specify the proper version support in your setup py file,  Up: 詳細的

10.1.2.1 向下支援Python 2.6和更舊的版本
.......................................

While you can make Python 2.5 work with Python 3, it is `much' easier if
you only have to work with Python 2.7.  If dropping Python 2.5 is not an
option then the six(1) project can help you support Python 2.5 & 3
simultaneously (‘pip install six’).  Do realize, though, that nearly all
the projects listed in this HOWTO will not be available to you.

If you are able to skip Python 2.5 and older, then the required changes
to your code should continue to look and feel like idiomatic Python
code.  At worst you will have to use a function instead of a method in
some instances or have to import a function instead of using a built-in
one, but otherwise the overall transformation should not feel foreign to
you.

But you should aim for only supporting Python 2.7.  Python 2.6 is no
longer freely supported and thus is not receiving bugfixes.  This means
`you' will have to work around any issues you come across with Python
2.6.  There are also some tools mentioned in this HOWTO which do not
support Python 2.6 (e.g., Pylint(2)), and this will become more
commonplace as time goes on.  It will simply be easier for you if you
only support the versions of Python that you have to support.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/six

   (2) https://pypi.org/project/pylint


File: python.info,  Node: Make sure you specify the proper version support in your setup py file,  Next: 有好的測試覆蓋率,  Prev: 向下支援Python 2 6和更舊的版本,  Up: 詳細的

10.1.2.2 Make sure you specify the proper version support in your ‘setup.py’ file
.................................................................................

In your ‘setup.py’ file you should have the proper trove classifier(1)
specifying what versions of Python you support.  As your project does
not support Python 3 yet you should at least have ‘Programming Language
:: Python :: 2 :: Only’ specified.  Ideally you should also specify each
major/minor version of Python that you do support, e.g.  ‘Programming
Language :: Python :: 2.7’.

   ---------- Footnotes ----------

   (1) https://pypi.org/classifiers


File: python.info,  Node: 有好的測試覆蓋率,  Next: 瞭解Python 2 & 3的差異,  Prev: Make sure you specify the proper version support in your setup py file,  Up: 詳細的

10.1.2.3 有好的測試覆蓋率
.........................

Once you have your code supporting the oldest version of Python 2 you
want it to, you will want to make sure your test suite has good
coverage.  A good rule of thumb is that if you want to be confident
enough in your test suite that any failures that appear after having
tools rewrite your code are actual bugs in the tools and not in your
code.  If you want a number to aim for, try to get over 80% coverage
(and don’t feel bad if you find it hard to get better than 90%
coverage).  If you don’t already have a tool to measure test coverage
then coverage.py(1) is recommended.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/coverage


File: python.info,  Node: 瞭解Python 2 & 3的差異,  Next: 更新你的程式碼,  Prev: 有好的測試覆蓋率,  Up: 詳細的

10.1.2.4 瞭解Python 2 & 3的差異
...............................

Once you have your code well-tested you are ready to begin porting your
code to Python 3!  But to fully understand how your code is going to
change and what you want to look out for while you code, you will want
to learn what changes Python 3 makes in terms of Python 2.  Typically
the two best ways of doing that is reading the *note "What’s New": 14a.
doc for each release of Python 3 and the Porting to Python 3(1) book
(which is free online).  There is also a handy cheat sheet(2) from the
Python-Future project.

   ---------- Footnotes ----------

   (1) http://python3porting.com/

   (2) http://python-future.org/compatible_idioms.html


File: python.info,  Node: 更新你的程式碼,  Next: Prevent compatibility regressions,  Prev: 瞭解Python 2 & 3的差異,  Up: 詳細的

10.1.2.5 更新你的程式碼
.......................

Once you feel like you know what is different in Python 3 compared to
Python 2, it’s time to update your code!  You have a choice between two
tools in porting your code automatically: Futurize(1) and Modernize(2).
Which tool you choose will depend on how much like Python 3 you want
your code to be.  Futurize(3) does its best to make Python 3 idioms and
practices exist in Python 2, e.g.  backporting the ‘bytes’ type from
Python 3 so that you have semantic parity between the major versions of
Python.  Modernize(4), on the other hand, is more conservative and
targets a Python 2/3 subset of Python, directly relying on six(5) to
help provide compatibility.  As Python 3 is the future, it might be best
to consider Futurize to begin adjusting to any new practices that Python
3 introduces which you are not accustomed to yet.

Regardless of which tool you choose, they will update your code to run
under Python 3 while staying compatible with the version of Python 2 you
started with.  Depending on how conservative you want to be, you may
want to run the tool over your test suite first and visually inspect the
diff to make sure the transformation is accurate.  After you have
transformed your test suite and verified that all the tests still pass
as expected, then you can transform your application code knowing that
any tests which fail is a translation failure.

Unfortunately the tools can’t automate everything to make your code work
under Python 3 and so there are a handful of things you will need to
update manually to get full Python 3 support (which of these steps are
necessary vary between the tools).  Read the documentation for the tool
you choose to use to see what it fixes by default and what it can do
optionally to know what will (not) be fixed for you and what you may
have to fix on your own (e.g.  using ‘io.open()’ over the built-in
‘open()’ function is off by default in Modernize).  Luckily, though,
there are only a couple of things to watch out for which can be
considered large issues that may be hard to debug if not watched for.

* Menu:

* Division::
* Text versus binary data::
* Use feature detection instead of version detection::

   ---------- Footnotes ----------

   (1) http://python-future.org/automatic_conversion.html

   (2) https://python-modernize.readthedocs.io/

   (3) http://python-future.org/automatic_conversion.html

   (4) https://python-modernize.readthedocs.io/

   (5) https://pypi.org/project/six


File: python.info,  Node: Division,  Next: Text versus binary data,  Up: 更新你的程式碼

10.1.2.6 Division
.................

In Python 3, ‘5 / 2 == 2.5’ and not ‘2’; all division between ‘int’
values result in a ‘float’.  This change has actually been planned since
Python 2.2 which was released in 2002.  Since then users have been
encouraged to add ‘from __future__ import division’ to any and all files
which use the ‘/’ and ‘//’ operators or to be running the interpreter
with the ‘-Q’ flag.  If you have not been doing this then you will need
to go through your code and do two things:

  1. Add ‘from __future__ import division’ to your files

  2. Update any division operator as necessary to either use ‘//’ to use
     floor division or continue using ‘/’ and expect a float

The reason that ‘/’ isn’t simply translated to ‘//’ automatically is
that if an object defines a ‘__truediv__’ method but not ‘__floordiv__’
then your code would begin to fail (e.g.  a user-defined class that uses
‘/’ to signify some operation but not ‘//’ for the same thing or at
all).


File: python.info,  Node: Text versus binary data,  Next: Use feature detection instead of version detection,  Prev: Division,  Up: 更新你的程式碼

10.1.2.7 Text versus binary data
................................

In Python 2 you could use the ‘str’ type for both text and binary data.
Unfortunately this confluence of two different concepts could lead to
brittle code which sometimes worked for either kind of data, sometimes
not.  It also could lead to confusing APIs if people didn’t explicitly
state that something that accepted ‘str’ accepted either text or binary
data instead of one specific type.  This complicated the situation
especially for anyone supporting multiple languages as APIs wouldn’t
bother explicitly supporting ‘unicode’ when they claimed text data
support.

To make the distinction between text and binary data clearer and more
pronounced, Python 3 did what most languages created in the age of the
internet have done and made text and binary data distinct types that
cannot blindly be mixed together (Python predates widespread access to
the internet).  For any code that deals only with text or only binary
data, this separation doesn’t pose an issue.  But for code that has to
deal with both, it does mean you might have to now care about when you
are using text compared to binary data, which is why this cannot be
entirely automated.

To start, you will need to decide which APIs take text and which take
binary (it is `highly' recommended you don’t design APIs that can take
both due to the difficulty of keeping the code working; as stated
earlier it is difficult to do well).  In Python 2 this means making sure
the APIs that take text can work with ‘unicode’ and those that work with
binary data work with the ‘bytes’ type from Python 3 (which is a subset
of ‘str’ in Python 2 and acts as an alias for ‘bytes’ type in Python 2).
Usually the biggest issue is realizing which methods exist on which
types in Python 2 & 3 simultaneously (for text that’s ‘unicode’ in
Python 2 and ‘str’ in Python 3, for binary that’s ‘str’/‘bytes’ in
Python 2 and ‘bytes’ in Python 3).  The following table lists the
`unique' methods of each data type across Python 2 & 3 (e.g., the
‘decode()’ method is usable on the equivalent binary data type in either
Python 2 or 3, but it can’t be used by the textual data type
consistently between Python 2 and 3 because ‘str’ in Python 3 doesn’t
have the method).  Do note that as of Python 3.5 the ‘__mod__’ method
was added to the bytes type.

`Text data'                  `Binary data'
                             
                             
                             decode
                             
                             
encode

format

isdecimal

isnumeric

Making the distinction easier to handle can be accomplished by encoding
and decoding between binary data and text at the edge of your code.
This means that when you receive text in binary data, you should
immediately decode it.  And if your code needs to send text as binary
data then encode it as late as possible.  This allows your code to work
with only text internally and thus eliminates having to keep track of
what type of data you are working with.

The next issue is making sure you know whether the string literals in
your code represent text or binary data.  You should add a ‘b’ prefix to
any literal that presents binary data.  For text you should add a ‘u’
prefix to the text literal.  (there is a *note __future__: 0. import to
force all unspecified literals to be Unicode, but usage has shown it
isn’t as effective as adding a ‘b’ or ‘u’ prefix to all literals
explicitly)

As part of this dichotomy you also need to be careful about opening
files.  Unless you have been working on Windows, there is a chance you
have not always bothered to add the ‘b’ mode when opening a binary file
(e.g., ‘rb’ for binary reading).  Under Python 3, binary files and text
files are clearly distinct and mutually incompatible; see the *note io:
a2. module for details.  Therefore, you `must' make a decision of
whether a file will be used for binary access (allowing binary data to
be read and/or written) or textual access (allowing text data to be read
and/or written).  You should also use *note io.open(): 65f. for opening
files instead of the built-in *note open(): 4f5. function as the *note
io: a2. module is consistent from Python 2 to 3 while the built-in *note
open(): 4f5. function is not (in Python 3 it’s actually *note io.open():
65f.).  Do not bother with the outdated practice of using *note
codecs.open(): 1367. as that’s only necessary for keeping compatibility
with Python 2.5.

The constructors of both ‘str’ and ‘bytes’ have different semantics for
the same arguments between Python 2 & 3.  Passing an integer to ‘bytes’
in Python 2 will give you the string representation of the integer:
‘bytes(3) == '3'’.  But in Python 3, an integer argument to ‘bytes’ will
give you a bytes object as long as the integer specified, filled with
null bytes: ‘bytes(3) == b'\x00\x00\x00'’.  A similar worry is necessary
when passing a bytes object to ‘str’.  In Python 2 you just get the
bytes object back: ‘str(b'3') == b'3'’.  But in Python 3 you get the
string representation of the bytes object: ‘str(b'3') == "b'3'"’.

Finally, the indexing of binary data requires careful handling (slicing
does `not' require any special handling).  In Python 2, ‘b'123'[1] ==
b'2'’ while in Python 3 ‘b'123'[1] == 50’.  Because binary data is
simply a collection of binary numbers, Python 3 returns the integer
value for the byte you index on.  But in Python 2 because ‘bytes ==
str’, indexing returns a one-item slice of bytes.  The six(1) project
has a function named ‘six.indexbytes()’ which will return an integer
like in Python 3: ‘six.indexbytes(b'123', 1)’.

To summarize:

  1. Decide which of your APIs take text and which take binary data

  2. Make sure that your code that works with text also works with
     ‘unicode’ and code for binary data works with ‘bytes’ in Python 2
     (see the table above for what methods you cannot use for each type)

  3. Mark all binary literals with a ‘b’ prefix, textual literals with a
     ‘u’ prefix

  4. Decode binary data to text as soon as possible, encode text as
     binary data as late as possible

  5. Open files using *note io.open(): 65f. and make sure to specify the
     ‘b’ mode when appropriate

  6. Be careful when indexing into binary data

   ---------- Footnotes ----------

   (1) https://pypi.org/project/six


File: python.info,  Node: Use feature detection instead of version detection,  Prev: Text versus binary data,  Up: 更新你的程式碼

10.1.2.8 Use feature detection instead of version detection
...........................................................

Inevitably you will have code that has to choose what to do based on
what version of Python is running.  The best way to do this is with
feature detection of whether the version of Python you’re running under
supports what you need.  If for some reason that doesn’t work then you
should make the version check be against Python 2 and not Python 3.  To
help explain this, let’s look at an example.

Let’s pretend that you need access to a feature of *note importlib: 9b.
that is available in Python’s standard library since Python 3.3 and
available for Python 2 through importlib2(1) on PyPI. You might be
tempted to write code to access e.g.  the *note importlib.abc: 9c.
module by doing the following:

     import sys

     if sys.version_info[0] == 3:
         from importlib import abc
     else:
         from importlib2 import abc

The problem with this code is what happens when Python 4 comes out?  It
would be better to treat Python 2 as the exceptional case instead of
Python 3 and assume that future Python versions will be more compatible
with Python 3 than Python 2:

     import sys

     if sys.version_info[0] > 2:
         from importlib import abc
     else:
         from importlib2 import abc

The best solution, though, is to do no version detection at all and
instead rely on feature detection.  That avoids any potential issues of
getting the version detection wrong and helps keep you
future-compatible:

     try:
         from importlib import abc
     except ImportError:
         from importlib2 import abc

   ---------- Footnotes ----------

   (1) https://pypi.org/project/importlib2


File: python.info,  Node: Prevent compatibility regressions,  Next: Check which dependencies block your transition,  Prev: 更新你的程式碼,  Up: 詳細的

10.1.2.9 Prevent compatibility regressions
..........................................

Once you have fully translated your code to be compatible with Python 3,
you will want to make sure your code doesn’t regress and stop working
under Python 3.  This is especially true if you have a dependency which
is blocking you from actually running under Python 3 at the moment.

To help with staying compatible, any new modules you create should have
at least the following block of code at the top of it:

     from __future__ import absolute_import
     from __future__ import division
     from __future__ import print_function

You can also run Python 2 with the ‘-3’ flag to be warned about various
compatibility issues your code triggers during execution.  If you turn
warnings into errors with ‘-Werror’ then you can make sure that you
don’t accidentally miss a warning.

You can also use the Pylint(1) project and its ‘--py3k’ flag to lint
your code to receive warnings when your code begins to deviate from
Python 3 compatibility.  This also prevents you from having to run
Modernize(2) or Futurize(3) over your code regularly to catch
compatibility regressions.  This does require you only support Python
2.7 and Python 3.4 or newer as that is Pylint’s minimum Python version
support.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/pylint

   (2) https://python-modernize.readthedocs.io/

   (3) http://python-future.org/automatic_conversion.html


File: python.info,  Node: Check which dependencies block your transition,  Next: Update your setup py file to denote Python 3 compatibility,  Prev: Prevent compatibility regressions,  Up: 詳細的

10.1.2.10 Check which dependencies block your transition
........................................................

`After' you have made your code compatible with Python 3 you should
begin to care about whether your dependencies have also been ported.
The caniusepython3(1) project was created to help you determine which
projects – directly or indirectly – are blocking you from supporting
Python 3.  There is both a command-line tool as well as a web interface
at ‘https://caniusepython3.com’.

The project also provides code which you can integrate into your test
suite so that you will have a failing test when you no longer have
dependencies blocking you from using Python 3.  This allows you to avoid
having to manually check your dependencies and to be notified quickly
when you can start running on Python 3.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/caniusepython3


File: python.info,  Node: Update your setup py file to denote Python 3 compatibility,  Next: Use continuous integration to stay compatible,  Prev: Check which dependencies block your transition,  Up: 詳細的

10.1.2.11 Update your ‘setup.py’ file to denote Python 3 compatibility
......................................................................

Once your code works under Python 3, you should update the classifiers
in your ‘setup.py’ to contain ‘Programming Language :: Python :: 3’ and
to not specify sole Python 2 support.  This will tell anyone using your
code that you support Python 2 `and' 3.  Ideally you will also want to
add classifiers for each major/minor version of Python you now support.


File: python.info,  Node: Use continuous integration to stay compatible,  Next: Consider using optional static type checking,  Prev: Update your setup py file to denote Python 3 compatibility,  Up: 詳細的

10.1.2.12 Use continuous integration to stay compatible
.......................................................

Once you are able to fully run under Python 3 you will want to make sure
your code always works under both Python 2 & 3.  Probably the best tool
for running your tests under multiple Python interpreters is tox(1).
You can then integrate tox with your continuous integration system so
that you never accidentally break Python 2 or 3 support.

You may also want to use the ‘-bb’ flag with the Python 3 interpreter to
trigger an exception when you are comparing bytes to strings or bytes to
an int (the latter is available starting in Python 3.5).  By default
type-differing comparisons simply return ‘False’, but if you made a
mistake in your separation of text/binary data handling or indexing on
bytes you wouldn’t easily find the mistake.  This flag will raise an
exception when these kinds of comparisons occur, making the mistake much
easier to track down.

And that’s mostly it!  At this point your code base is compatible with
both Python 2 and 3 simultaneously.  Your testing will also be set up so
that you don’t accidentally break Python 2 or 3 compatibility regardless
of which version you typically run your tests under while developing.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/tox


File: python.info,  Node: Consider using optional static type checking,  Prev: Use continuous integration to stay compatible,  Up: 詳細的

10.1.2.13 Consider using optional static type checking
......................................................

Another way to help port your code is to use a static type checker like
mypy(1) or pytype(2) on your code.  These tools can be used to analyze
your code as if it’s being run under Python 2, then you can run the tool
a second time as if your code is running under Python 3.  By running a
static type checker twice like this you can discover if you’re e.g.
misusing binary data type in one version of Python compared to another.
If you add optional type hints to your code you can also explicitly
state whether your APIs use textual or binary data, helping to make sure
everything functions as expected in both versions of Python.

   ---------- Footnotes ----------

   (1) http://mypy-lang.org/

   (2) https://github.com/google/pytype


File: python.info,  Node: 遷移延伸模組到 Python 3,  Next: Curses Programming with Python,  Prev: Python 2 的程式碼移植到Python 3,  Up: Python HOWTOs

10.2 遷移延伸模組到 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) http://cython.org/

   (4) https://cffi.readthedocs.io/en/latest/


File: python.info,  Node: Curses Programming with Python,  Next: 修飾器 HowTo 指南,  Prev: 遷移延伸模組到 Python 3,  Up: Python HOWTOs

10.3 Curses Programming with Python
===================================


Author: A.M. Kuchling, Eric S. Raymond


Release: 2.04

Abstract
........

This document describes how to use the *note curses: 2c. extension
module to control text-mode displays.

* Menu:

* What is curses?::
* Starting and ending a curses application::
* Windows and Pads::
* Displaying Text::
* User Input::
* For More Information::


File: python.info,  Node: What is curses?,  Next: Starting and ending a curses application,  Up: Curses Programming with Python

10.3.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: 2c.
module.  A ported version called UniCurses(2) is available.  You could
also try the Console module(3) written by Fredrik Lundh, which doesn’t
use the same API as curses but provides cursor-addressable text output
and full support for mouse and keyboard input.

* Menu:

* The Python curses module::

   ---------- Footnotes ----------

   (1) https://pypi.org/project/urwid/

   (2) https://pypi.org/project/UniCurses

   (3) http://effbot.org/zone/console-index.htm


File: python.info,  Node: The Python curses module,  Up: What is curses?

10.3.1.1 The Python curses module
.................................

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(): 216a. 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

10.3.2 Starting and ending a curses application
-----------------------------------------------

Before doing anything, curses must be initialized.  This is done by
calling the *note initscr(): 2170. 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(): 218f.
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 ‘curses.KEY_LEFT’.  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(): 216d. 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(): 2a2. 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(): 2a2. 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: d77...*note
except: b43. 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

10.3.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(): 2170. 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(): 218d. 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
‘curses.LINES’ and ‘curses.COLS’ 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(): 216b. 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(): 2169. method of each window to
     update an underlying data structure representing the desired state
     of the screen.

  2. Calls the function *note doupdate(): 2168. 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: User Input,  Prev: Windows and Pads,  Up: Curses Programming with Python

10.3.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(): 216a.
accept multiple argument forms.  Usually there are four different forms.

Form                                  描述
                                      
------------------------------------------------------------------------------------------
                                      
`str' or `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' or `ch'               Move to position `y,x' within the window, and
                                      display `str' or `ch'
                                      
                                      
`y', `x', `str' or `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(): 216a. 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 ‘encoding’ attribute; this defaults to the default system
encoding as returned by *note locale.getpreferredencoding(): 3aa.

The *note addch(): 21a8. 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, ‘ACS_PLMINUS’ is a +/- symbol,
and ‘ACS_ULCORNER’ 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(): 2162.  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

10.3.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.

Attribute                  描述
                           
----------------------------------------------------------------------
                           
‘A_BLINK’                  Blinking text
                           
                           
‘A_BOLD’                   Extra bright or bold text
                           
                           
‘A_DIM’                    Half bright text
                           
                           
‘A_REVERSE’                Reverse-video text
                           
                           
‘A_STANDOUT’               The best highlighting mode available
                           
                           
‘A_UNDERLINE’              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(): 219b. function soon
after calling *note initscr(): 2170, to initialize the default color set
(the *note curses.wrapper(): 2a2. function does this automatically).
Once that’s done, the *note has_colors(): 2178. 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(): 2160. function; this can be bitwise-OR’ed with other
attributes such as ‘A_REVERSE’, 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 ‘start_color()’ 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: 2c. module
defines named constants for each of these colors: ‘curses.COLOR_BLACK’,
‘curses.COLOR_RED’, 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(): 215c, 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: User Input,  Next: For More Information,  Prev: Displaying Text,  Up: Curses Programming with Python

10.3.5 User Input
-----------------

The C curses library offers only very simple input mechanisms.  Python’s
*note curses: 2c. 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(): 2174. refreshes the screen and then waits for the
     user to hit a key, displaying the key if *note echo(): 216c. has
     been called earlier.  You can optionally specify a coordinate to
     which the cursor should be moved before pausing.

   * *note getkey(): 21c1. 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(): 21d7.
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(): 217c. 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 ‘curses.KEY_PPAGE’,
‘curses.KEY_HOME’, or ‘curses.KEY_LEFT’.  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: 2d. 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(): 220b. returns the control character
corresponding to its argument.

There’s also a method to retrieve an entire string, *note getstr():
21c4.  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: 2f. module supplies a text box that supports
an Emacs-like set of keybindings.  Various methods of the *note Textbox:
21f1. 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: 2f. for more
details.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/urwid/


File: python.info,  Node: For More Information,  Prev: User Input,  Up: Curses Programming with Python

10.3.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: 2c. 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 ‘ACS_*’ 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.

   * The ncurses man page(3)

   * The ncurses FAQ(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) http://invisible-island.net/ncurses/ncurses-intro.html

   (3) https://linux.die.net/man/3/ncurses

   (4) http://invisible-island.net/ncurses/ncurses.faq.html

   (5) https://www.youtube.com/watch?v=eN1eZtjLEnU

   (6) http://www.pyvideo.org/video/1568/console-applications-with-urwid


File: python.info,  Node: 修飾器 HowTo 指南,  Next: 函式編程 HOWTO,  Prev: Curses Programming with Python,  Up: Python HOWTOs

10.4 修飾器 HowTo 指南
======================


Author: Raymond Hettinger


Contact: <python at rcn dot com>

* Menu:

* 摘要::
* Definition and Introduction::
* Descriptor Protocol::
* Invoking Descriptors: Invoking Descriptors<2>.
* Descriptor Example::
* Properties::
* Functions and Methods::
* Static Methods and Class Methods::


File: python.info,  Node: 摘要,  Next: Definition and Introduction,  Up: 修飾器 HowTo 指南

10.4.1 摘要
-----------

Defines descriptors, summarizes the protocol, and shows how descriptors
are called.  Examines a custom descriptor and several built-in Python
descriptors including functions, properties, static methods, and class
methods.  Shows how each works by giving a pure Python equivalent and a
sample application.

Learning about descriptors not only provides access to a larger toolset,
it creates a deeper understanding of how Python works and an
appreciation for the elegance of its design.


File: python.info,  Node: Definition and Introduction,  Next: Descriptor Protocol,  Prev: 摘要,  Up: 修飾器 HowTo 指南

10.4.2 Definition and Introduction
----------------------------------

In general, a descriptor is an object attribute with "binding behavior",
one whose attribute access has been overridden by methods in the
descriptor protocol.  Those methods are *note __get__(): 1440, *note
__set__(): 1444, and *note __delete__(): 1445.  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.
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(): 4e7.  They are used throughout Python itself to implement
the new style classes introduced in version 2.2.  Descriptors simplify
the underlying C-code and offer a flexible set of new tools for everyday
Python programs.


File: python.info,  Node: Descriptor Protocol,  Next: Invoking Descriptors<2>,  Prev: Definition and Introduction,  Up: 修飾器 HowTo 指南

10.4.3 Descriptor Protocol
--------------------------

‘descr.__get__(self, obj, type=None) -> value’

‘descr.__set__(self, obj, value) -> None’

‘descr.__delete__(self, obj) -> None’

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 *note __set__(): 1444. or *note __delete__(): 1445,
it is considered a data descriptor.  Descriptors that only define *note
__get__(): 1440. are called non-data descriptors (they are typically
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 *note __get__(): 1440.
and *note __set__(): 1444. with the *note __set__(): 1444. raising an
*note AttributeError: 3a0. when called.  Defining the *note __set__():
1444. method with an exception raising placeholder is enough to make it
a data descriptor.


File: python.info,  Node: Invoking Descriptors<2>,  Next: Descriptor Example,  Prev: Descriptor Protocol,  Up: 修飾器 HowTo 指南

10.4.4 Invoking Descriptors
---------------------------

A descriptor can be called directly by its method name.  For example,
‘d.__get__(obj)’.

Alternatively, it is more common for a descriptor to be invoked
automatically upon attribute access.  For example, ‘obj.d’ looks up ‘d’
in the dictionary of ‘obj’.  If ‘d’ defines the method *note __get__():
1440, then ‘d.__get__(obj)’ is invoked according to the precedence rules
listed below.

The details of invocation depend on whether ‘obj’ is an object or a
class.

For objects, the machinery is in *note object.__getattribute__(): 44e.
which transforms ‘b.x’ into ‘type(b).__dict__['x'].__get__(b, type(b))’.
The implementation works through a precedence chain that gives data
descriptors priority over instance variables, instance variables
priority over non-data descriptors, and assigns lowest priority to *note
__getattr__(): 31f. if provided.  The full C implementation can be found
in *note PyObject_GenericGetAttr(): 3cae. in Objects/object.c(1).

For classes, the machinery is in ‘type.__getattribute__()’ which
transforms ‘B.x’ into ‘B.__dict__['x'].__get__(None, B)’.  In pure
Python, it looks like:

     def __getattribute__(self, key):
         "Emulate type_getattro() in Objects/typeobject.c"
         v = object.__getattribute__(self, key)
         if hasattr(v, '__get__'):
             return v.__get__(None, self)
         return v

The important points to remember are:

   * descriptors are invoked by the *note __getattribute__(): 44e.
     method

   * overriding *note __getattribute__(): 44e. prevents automatic
     descriptor calls

   * *note object.__getattribute__(): 44e. and ‘type.__getattribute__()’
     make different calls to *note __get__(): 1440.

   * data descriptors always override instance dictionaries.

   * non-data descriptors may be overridden by instance dictionaries.

The object returned by ‘super()’ also has a custom *note
__getattribute__(): 44e. method for invoking descriptors.  The attribute
lookup ‘super(B, obj).m’ searches ‘obj.__class__.__mro__’ for the base
class ‘A’ immediately following ‘B’ and then returns
‘A.__dict__['m'].__get__(obj, B)’.  If not a descriptor, ‘m’ is returned
unchanged.  If not in the dictionary, ‘m’ reverts to a search using
*note object.__getattribute__(): 44e.

The implementation details are in ‘super_getattro()’ in
Objects/typeobject.c(2).  and a pure Python equivalent can be found in
Guido’s Tutorial(3).

The details above show that the mechanism for descriptors is embedded in
the *note __getattribute__(): 44e. methods for *note object: 2b1, *note
type: 60d, and *note super(): 4e7.  Classes inherit this machinery when
they derive from *note object: 2b1. or if they have a meta-class
providing similar functionality.  Likewise, classes can turn-off
descriptor invocation by overriding *note __getattribute__(): 44e.

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Objects/object.c

   (2) https://github.com/python/cpython/tree/3.8/Objects/typeobject.c

   (3) 
https://www.python.org/download/releases/2.2.3/descrintro/#cooperation


File: python.info,  Node: Descriptor Example,  Next: Properties,  Prev: Invoking Descriptors<2>,  Up: 修飾器 HowTo 指南

10.4.5 Descriptor Example
-------------------------

The following code creates a class whose objects are data descriptors
which print a message for each get or set.  Overriding *note
__getattribute__(): 44e. is alternate approach that could do this for
every attribute.  However, this descriptor is useful for monitoring just
a few chosen attributes:

     class RevealAccess(object):
         """A data descriptor that sets and returns values
            normally and prints a message logging their access.
         """

         def __init__(self, initval=None, name='var'):
             self.val = initval
             self.name = name

         def __get__(self, obj, objtype):
             print('Retrieving', self.name)
             return self.val

         def __set__(self, obj, val):
             print('Updating', self.name)
             self.val = val

     >>> class MyClass(object):
     ...     x = RevealAccess(10, 'var "x"')
     ...     y = 5
     ...
     >>> m = MyClass()
     >>> m.x
     Retrieving var "x"
     10
     >>> m.x = 20
     Updating var "x"
     >>> m.x
     Retrieving var "x"
     20
     >>> m.y
     5

The protocol is simple and offers exciting possibilities.  Several use
cases are so common that they have been packaged into individual
function calls.  Properties, bound methods, static methods, and class
methods are all based on the descriptor protocol.


File: python.info,  Node: Properties,  Next: Functions and Methods,  Prev: Descriptor Example,  Up: 修飾器 HowTo 指南

10.4.6 Properties
-----------------

Calling *note property(): 1d8. is a succinct way of building a data
descriptor that triggers function calls upon access to an attribute.
Its signature is:

     property(fget=None, fset=None, fdel=None, doc=None) -> property attribute

The documentation shows a typical use to define a managed attribute ‘x’:

     class C(object):
         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(): 1d8. is implemented in terms of the
descriptor protocol, here is a pure Python equivalent:

     class Property(object):
         "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

         def __get__(self, obj, objtype=None):
             if obj is None:
                 return self
             if self.fget is None:
                 raise AttributeError("unreadable attribute")
             return self.fget(obj)

         def __set__(self, obj, value):
             if self.fset is None:
                 raise AttributeError("can't set attribute")
             self.fset(obj, value)

         def __delete__(self, obj):
             if self.fdel is None:
                 raise AttributeError("can't delete attribute")
             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(): 1d8. 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(object):
         . . .
         def getvalue(self):
             "Recalculate the cell before returning value"
             self.recalc()
             return self._value
         value = property(getvalue)


File: python.info,  Node: Functions and Methods,  Next: Static Methods and Class Methods,  Prev: Properties,  Up: 修飾器 HowTo 指南

10.4.7 Functions and Methods
----------------------------

Python’s object oriented features are built upon a function based
environment.  Using non-data descriptors, the two are merged seamlessly.

Class dictionaries store methods as functions.  In a class definition,
methods are written using *note def: dc3. or *note lambda: c34, the
usual tools for creating functions.  Methods only differ from regular
functions in that the first argument is reserved for the object
instance.  By Python convention, the instance reference is called `self'
but may be called `this' or any other variable name.

To support method calls, functions include the *note __get__(): 1440.
method for binding methods during attribute access.  This means that all
functions are non-data descriptors which return bound methods when they
are invoked from an object.  In pure Python, it works like this:

     class Function(object):
         . . .
         def __get__(self, obj, objtype=None):
             "Simulate func_descr_get() in Objects/funcobject.c"
             if obj is None:
                 return self
             return types.MethodType(self, obj)

Running the interpreter shows how the function descriptor works in
practice:

     >>> class D(object):
     ...     def f(self, x):
     ...         return x
     ...
     >>> d = D()

     # Access through the class dictionary does not invoke __get__.
     # 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 function has a __qualname__ attribute to support introspection
     >>> D.f.__qualname__
     'D.f'

     # Dotted access from an instance calls __get__() which returns the
     # function wrapped in a bound method object
     >>> 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 0x1012e5ae8>
     >>> d.f.__self__
     <__main__.D object at 0x1012e1f98>


File: python.info,  Node: Static Methods and Class Methods,  Prev: Functions and Methods,  Up: 修飾器 HowTo 指南

10.4.8 Static Methods and Class Methods
---------------------------------------

Non-data descriptors provide a simple mechanism for variations on the
usual patterns of binding functions into methods.

To recap, functions have a *note __get__(): 1440. 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 ‘klass.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
                                                      
     ------------------------------------------------------------------------
                                                      
     function              f(obj, *args)              f(*args)
                                                      
                                                      
     staticmethod          f(*args)                   f(*args)
                                                      
                                                      
     classmethod           f(type(obj), *args)        f(klass, *args)
                                                      

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 staticmethods return the underlying function with no changes, the
example calls are unexciting:

     >>> class E(object):
     ...     def f(x):
     ...         print(x)
     ...     f = staticmethod(f)
     ...
     >>> E.f(3)
     3
     >>> E().f(3)
     3

Using the non-data descriptor protocol, a pure Python version of *note
staticmethod(): 1da. would look like this:

     class StaticMethod(object):
         "Emulate PyStaticMethod_Type() in Objects/funcobject.c"

         def __init__(self, f):
             self.f = f

         def __get__(self, obj, objtype=None):
             return self.f

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 E(object):
     ...     def f(klass, x):
     ...         return klass.__name__, x
     ...     f = classmethod(f)
     ...
     >>> print(E.f(3))
     ('E', 3)
     >>> print(E().f(3))
     ('E', 3)

This behavior is useful whenever the function only needs to have a class
reference and does not care about any underlying data.  One use for
classmethods is to create alternate class constructors.  In Python 2.3,
the classmethod *note dict.fromkeys(): 16d9. creates a new dictionary
from a list of keys.  The pure Python equivalent is:

     class Dict(object):
         . . .
         def fromkeys(klass, iterable, value=None):
             "Emulate dict_fromkeys() in Objects/dictobject.c"
             d = klass()
             for key in iterable:
                 d[key] = value
             return d
         fromkeys = classmethod(fromkeys)

Now a new dictionary of unique keys can be constructed like this:

     >>> Dict.fromkeys('abracadabra')
     {'a': None, 'r': None, 'b': None, 'c': None, 'd': None}

Using the non-data descriptor protocol, a pure Python version of *note
classmethod(): 1d9. would look like this:

     class ClassMethod(object):
         "Emulate PyClassMethod_Type() in Objects/funcobject.c"

         def __init__(self, f):
             self.f = f

         def __get__(self, obj, klass=None):
             if klass is None:
                 klass = type(obj)
             def newfunc(*args):
                 return self.f(klass, *args)
             return newfunc


File: python.info,  Node: 函式編程 HOWTO,  Next: 如何使用 Logging 模組,  Prev: 修飾器 HowTo 指南,  Up: Python HOWTOs

10.5 函式編程 HOWTO
===================


Author: A. M. Kuchling


Release: 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: 1040.s and *note generator: 9a7.s and relevant
library modules such as *note itertools: a4. and *note functools: 85.

* Menu:

* 簡介: 簡介<13>.
* Iterators: Iterators<2>.
* Generator expressions and list comprehensions::
* Generators: Generators<2>.
* Built-in functions::
* The itertools module::
* The functools module::
* Small functions and the lambda expression::
* Revision History and Acknowledgements::
* References: References<2>.


File: python.info,  Node: 簡介<13>,  Next: Iterators<2>,  Up: 函式編程 HOWTO

10.5.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: 4121.

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.  Printing to the screen or writing to a disk
file are side effects, for example.  For example, in Python a call to
the *note print(): 88b. or *note time.sleep(): 685. function both return
no useful value; they’re only called 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: 簡介<13>

10.5.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: 簡介<13>

10.5.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: 簡介<13>

10.5.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: 簡介<13>

10.5.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<2>,  Next: Generator expressions and list comprehensions,  Prev: 簡介<13>,  Up: 函式編程 HOWTO

10.5.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__(): c69. that takes no arguments and
always returns the next element of the stream.  If there are no more
elements in the stream, *note __next__(): c69. must raise the *note
StopIteration: 48b. 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(): d2c. function takes an arbitrary object and
tries to return an iterator that will return the object’s contents or
elements, raising *note TypeError: 193. 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: bb1. 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: c35. statement.  In the statement ‘for X
in Y’, Y must be an iterator or some object for which *note iter(): d2c.
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(): 263. or *note tuple(): 483. 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(): 80f. and *note min(): 80e. 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(): 80f, *note min(): 80e. 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__(): c69.
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<2>

10.5.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(): d2c. 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(): d2c. 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(): c31. or *note items(): c30. methods to get an
appropriate iterator.

The *note dict(): 1b9. 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(): 1c03.
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)


File: python.info,  Node: Generator expressions and list comprehensions,  Next: Generators<2>,  Prev: Iterators<2>,  Up: 函式編程 HOWTO

10.5.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', ...]

     # 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:

     # Syntax error
     [x, y for x in seq1 for y in seq2]
     # Correct
     [(x, y) for x in seq1 for y in seq2]


File: python.info,  Node: Generators<2>,  Next: Built-in functions,  Prev: Generator expressions and list comprehensions,  Up: 函式編程 HOWTO

10.5.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: 190. keyword is a generator
function; this is detected by Python’s *note bytecode: 619. 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__(): 12df.
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__(): 12df.
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__(): c69. 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.8/Lib/test/test_generators.py


File: python.info,  Node: Passing values into a generator,  Up: Generators<2>

10.5.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: 190. 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): 1494.
method.  This method resumes the generator’s code and the ‘yield’
expression returns the specified value.  If the regular *note
__next__(): 12df. 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(): 1494. method will be the only method used to
resume your generator function.

In addition to *note send(): 1494, there are two other methods on
generators:

   * *note throw(type, value=None, traceback=None): 1496. 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(): 1498. raises a *note GeneratorExit: d37. exception
     inside the generator to terminate the iteration.  On receiving this
     exception, the generator’s code must either raise *note
     GeneratorExit: d37. or *note StopIteration: 48b.; catching the
     exception and doing anything else is illegal and will trigger a
     *note RuntimeError: 2bb.  *note close(): 1498. 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: d37.
     occurs, I suggest using a ‘try: ... finally:’ suite instead of
     catching *note GeneratorExit: d37.

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://www.python.org/dev/peps/pep-0342


File: python.info,  Node: Built-in functions,  Next: The itertools module,  Prev: Generators<2>,  Up: 函式編程 HOWTO

10.5.5 Built-in functions
-------------------------

Let’s look in more detail at built-in functions often used with
iterators.

Two of Python’s built-in functions, *note map(): c32. and *note
filter(): c33. duplicate the features of generator expressions:

*note map(f, iterA, iterB, ...): c32. 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): c33. 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():
c33, 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): de8. 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(): de8. 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): 449. 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(): 44a. 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 如何排序:
1606.)

The *note any(iter): d89. and *note all(iter): d8a. built-ins look at
the truth values of an iterable’s contents.  *note any(): d89. returns
‘True’ if any element in the iterable is a true value, and *note all():
d8a. 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, ...): c37. 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: The itertools module,  Next: The functools module,  Prev: Built-in functions,  Up: 函式編程 HOWTO

10.5.6 The itertools module
---------------------------

The *note itertools: a4. 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:

* Creating new iterators::
* Calling functions on elements::
* Selecting elements::
* Combinatoric functions::
* Grouping elements::


File: python.info,  Node: Creating new iterators,  Next: Calling functions on elements,  Up: The itertools module

10.5.6.1 Creating new iterators
...............................

*note itertools.count(start, step): c20. 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): 1b44. 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]): 10b7. 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, ...): 1608. 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]): 3a7. 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]): 1b49. 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: Creating new iterators,  Up: The itertools module

10.5.6.2 Calling functions on elements
......................................

The *note operator: c3. module contains a set of functions corresponding
to Python’s operators.  Some examples are *note operator.add(a, b):
1b6a. (adds two values), *note operator.ne(a, b): 1b5a. (same as ‘a !=
b’), and *note operator.attrgetter(’id’): 720. (returns a callable that
fetches the ‘.id’ attribute).

*note itertools.starmap(func, iter): a2d. 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: The itertools module

10.5.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): 15f1. is the opposite of
*note filter(): c33, 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): 1b48. 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): 1b46. 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): c1f. 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: The itertools module

10.5.6.4 Combinatoric functions
...............................

The *note itertools.combinations(iterable, r): cab. 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): ece, 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): c1e.
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: The itertools module

10.5.6.5 Grouping elements
..........................

The last function I’ll discuss, *note itertools.groupby(iter,
key_func=None): 1b47, 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(): 1b47. 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(): 1b47. 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: The functools module,  Next: Small functions and the lambda expression,  Prev: The itertools module,  Up: 函式編程 HOWTO

10.5.7 The functools module
---------------------------

The *note functools: 85. module in Python 2.5 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(): 7cd. 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(): 7cd. 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')

*note functools.reduce(func, iter, [initial_value]): c74. 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(): c74. 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:
193. 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(): 1b6a. with *note functools.reduce():
c74, 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(): 1e6. 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(): c74, though, it can be
clearer to just write the obvious *note for: c35. 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): 1de.  It performs the same calculation, but instead
of returning only the final result, ‘accumulate()’ 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:

* The operator module::


File: python.info,  Node: The operator module,  Up: The functools module

10.5.7.1 The operator module
............................

The *note operator: c3. 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:

   * Math operations: ‘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: The functools module,  Up: 函式編程 HOWTO

10.5.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: c34. 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(): 1e6. built-in and a generator expression:

     total = sum(b for a, b in items)

Many uses of *note functools.reduce(): c74. 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

10.5.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

10.5.10 References
------------------

* Menu:

* General::
* Python-specific::
* Python documentation::


File: python.info,  Node: General,  Next: Python-specific,  Up: References<2>

10.5.10.1 General
.................

`Structure and Interpretation of Computer Programs', by Harold Abelson
and Gerald Jay Sussman with Julie Sussman.  Full text 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.

‘http://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’: Entry for coroutines.

‘https://en.wikipedia.org/wiki/Currying’: Entry for the concept of
currying.


File: python.info,  Node: Python-specific,  Next: Python documentation,  Prev: General,  Up: References<2>

10.5.10.2 Python-specific
.........................

‘http://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 documentation,  Prev: Python-specific,  Up: References<2>

10.5.10.3 Python documentation
..............................

Documentation for the *note itertools: a4. module.

Documentation for the *note functools: 85. module.

Documentation for the *note operator: c3. module.

PEP 289(1): "Generator Expressions"

PEP 342(2): "Coroutines via Enhanced Generators" describes the new
generator features in Python 2.5.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0289

   (2) https://www.python.org/dev/peps/pep-0342


File: python.info,  Node: 如何使用 Logging 模組,  Next: Logging Cookbook,  Prev: 函式編程 HOWTO,  Up: Python HOWTOs

10.6 如何使用 Logging 模組
==========================


Author: 原文作者 Vinay Sajip <vinay_sajip at red-dove dot com>

* Menu:

* 基礎 Logging 指南::
* Advanced Logging Tutorial::
* Logging Levels: Logging Levels<2>.
* Useful Handlers::
* Exceptions raised during logging::
* Using arbitrary objects as messages::
* Optimization::


File: python.info,  Node: 基礎 Logging 指南,  Next: Advanced Logging Tutorial,  Up: 如何使用 Logging 模組

10.6.1 基礎 Logging 指南
------------------------

軟體執行時，追蹤有什麼事件發生的動作稱為 Logging。軟體開發者會使用
Logging 這樣的機制是因為想知道在運行過程中是否有特定的事件發生。事件會被
一段訊息所描述。這段訊息可能包含一些因為此事件發生而改變的資料。開發者也
可以指派事件的重要程度，重要程度有時候也會被稱作 `程度' 或是 `嚴重性' 。

* Menu:

* 什麼時候使用 logging::
* A simple example::
* Logging to a file::
* Logging from multiple modules::
* Logging variable data::
* Changing the format of displayed messages::
* Displaying the date/time in messages::
* Next Steps::


File: python.info,  Node: 什麼時候使用 logging,  Next: A simple example,  Up: 基礎 Logging 指南

10.6.1.1 什麼時候使用 logging
.............................

Logging provides a set of convenience functions for simple logging
usage.  These are *note debug(): 208e, *note info(): 20b9, *note
warning(): 20cb, *note error(): 20cc. and *note critical(): 20cd.  To
determine when to use logging, see the table below, which states, for
each of a set of common tasks, the best tool to use for it.

Task you want to perform                  The best tool for the task
                                          
-------------------------------------------------------------------------------------
                                          
Display console output for ordinary       *note print(): 88b.
usage of a command line script or         
program

Report events that occur during normal    *note logging.info(): 20b9. (or
operation of a program (e.g.  for         *note logging.debug(): 208e. for very
status monitoring or fault                detailed output for diagnostic purposes)
investigation)                            

Issue a warning regarding a particular    *note warnings.warn(): e5d. in library
runtime event                             code if the issue is avoidable and the
                                          client application should be modified to
                                          eliminate the warning
                                          
                                          *note logging.warning(): 20cb. 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    *note logging.error(): 20cc,
raising an exception (e.g.  error         *note logging.exception(): 20ce. or
handler in a long-running server          *note logging.critical(): 20cd. as
process)                                  appropriate for the specific error and
                                          application domain
                                          

The logging functions 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
level and above 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: A simple example,  Next: Logging to a file,  Prev: 什麼時候使用 logging,  Up: 基礎 Logging 指南

10.6.1.2 A simple example
.........................

A very simple example is:

     import logging
     logging.warning('Watch out!')  # will print a message to the console
     logging.info('I told you so')  # will not print anything

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!’.  Don’t worry about the ’root’ part for
now: it will be explained later.  The actual output can be formatted
quite flexibly if you need that; formatting options will also be
explained later.


File: python.info,  Node: Logging to a file,  Next: Logging from multiple modules,  Prev: A simple example,  Up: 基礎 Logging 指南

10.6.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
     logging.basicConfig(filename='example.log',level=logging.DEBUG)
     logging.debug('This message should go to the log file')
     logging.info('So should this')
     logging.warning('And this, too')

And now if we open the file and look at what we have, we should find the
log messages:

     DEBUG:root:This message should go to the log file
     INFO:root:So should this
     WARNING:root:And this, too

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(): 1e1. 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(): 1e1. should come `before' any calls to
*note debug(): 208e, *note info(): 20b9. etc.  As it’s intended as a
one-off simple configuration facility, only the first call will actually
do anything: subsequent calls are effectively no-ops.

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 from multiple modules,  Next: Logging variable data,  Prev: Logging to a file,  Up: 基礎 Logging 指南

10.6.1.4 Logging from multiple modules
......................................

If your program consists of multiple modules, here’s an example of how
you could organize logging in it:

     # myapp.py
     import logging
     import mylib

     def main():
         logging.basicConfig(filename='myapp.log', level=logging.INFO)
         logging.info('Started')
         mylib.do_something()
         logging.info('Finished')

     if __name__ == '__main__':
         main()

     # mylib.py
     import logging

     def do_something():
         logging.info('Doing something')

If you run `myapp.py', you should see this in `myapp.log':

     INFO:root:Started
     INFO:root:Doing something
     INFO:root:Finished

which is hopefully what you were expecting to see.  You can generalize
this to multiple modules, using the pattern in `mylib.py'.  Note that
for this simple usage pattern, you won’t know, by looking in the log
file, `where' in your application your messages came from, apart from
looking at the event description.  If you want to track the location of
your messages, you’ll need to refer to the documentation beyond the
tutorial level – see *note Advanced Logging Tutorial: b78.


File: python.info,  Node: Logging variable data,  Next: Changing the format of displayed messages,  Prev: Logging from multiple modules,  Up: 基礎 Logging 指南

10.6.1.5 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(): 4df. and *note string.Template: 3f0.
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: 20b1. 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 指南

10.6.1.6 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: 20af, 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 指南

10.6.1.7 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(): b6a.

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc3339.html


File: python.info,  Node: Next Steps,  Prev: Displaying the date/time in messages,  Up: 基礎 Logging 指南

10.6.1.8 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/forum/#!forum/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:
b79.


File: python.info,  Node: Advanced Logging Tutorial,  Next: Logging Levels<2>,  Prev: 基礎 Logging 指南,  Up: 如何使用 Logging 模組

10.6.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: 90b. instance.

Logging is performed by calling methods on instances of the *note
Logger: 3ac. 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(): 208e, *note info():
20b9, *note warning(): 20cb, *note error(): 20cc. and *note critical():
20cd, 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(): 1e1. as in the tutorial examples.  If you call the
functions *note debug(): 208e, *note info(): 20b9, *note warning():
20cb, *note error(): 20cc. and *note critical(): 20cd, 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(): 1e1. for messages is:

     severity:logger name:message

You can change this by passing a format string to *note basicConfig():
1e1. with the `format' keyword argument.  For all options regarding how
a format string is constructed, see *note Formatter Objects: 20ad.

* 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

10.6.2.1 Logging Flow
.....................

The flow of log event information in loggers and handlers is illustrated
in the following diagram.

[python-figures/logging_flow]

File: python.info,  Node: Loggers,  Next: Handlers,  Prev: Logging Flow,  Up: Advanced Logging Tutorial

10.6.2.2 Loggers
................

*note Logger: 3ac. 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(): 2087. 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(): 2094. and *note Logger.removeHandler():
     2095. add and remove handler objects from the logger object.
     Handlers are covered in more detail in *note Handlers: 4149.

   * *note Logger.addFilter(): 2091. and *note Logger.removeFilter():
     2092. add and remove filter objects from the logger object.
     Filters are covered in more detail in *note Filter Objects: 20b6.

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(): 715, *note Logger.info(): 208d, *note
     Logger.warning(): 208f, *note Logger.error(): 2090, and *note
     Logger.critical(): 714. 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(): 713. creates a log message similar to
     *note Logger.error(): 2090.  The difference is that *note
     Logger.exception(): 713. dumps a stack trace along with it.  Call
     this method only from an exception handler.

   * *note Logger.log(): 712. 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(): 2085. 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(): 2085. 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

10.6.2.3 Handlers
.................

*note Handler: 208c. objects are responsible for dispatching the
appropriate log messages (based on the log messages’ severity) to the
handler’s specified destination.  *note Logger: 3ac. objects can add
zero or more handler objects to themselves with an *note addHandler():
2094. 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: 414b.); the tutorials use mainly *note StreamHandler:
b7a. and *note FileHandler: 20f0. 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(): 20a1. method, just as in logger objects,
     specifies the lowest severity that will be dispatched to the
     appropriate destination.  Why are there two ‘setLevel()’ 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(): 20a2. selects a Formatter object for this
     handler to use.

   * *note addFilter(): 20a3. and *note removeFilter(): 20a4.
     respectively configure and deconfigure filter objects on handlers.

Application code should not directly instantiate and use instances of
*note Handler: 208c.  Instead, the *note Handler: 208c. 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

10.6.2.4 Formatters
...................

Formatter objects configure the final order, structure, and contents of
the log message.  Unlike the base *note logging.Handler: 208c. 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: 20af.  If the style is ’{’, the message
format string is assumed to be compatible with *note str.format(): 4df.
(using keyword arguments), while if the style is ’$’ then the message
format string should conform to what is expected by *note
string.Template.substitute(): 1304.

3.2 版更變: Added the ‘style’ parameter.

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(): f52. 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(): f52. or *note time.gmtime(): b44.
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

10.6.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(): 3ae. function.

  3. Creating a dictionary of configuration information and passing it
     to the *note dictConfig(): b30. function.

For the reference documentation on the last two options, see *note
Configuration functions: c8d.  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
     datefmt=

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(): 3ae. 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(): 3ae. 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(): b30. 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: 2101. (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: c8d.


File: python.info,  Node: What happens if no configuration is provided,  Next: Configuring Logging for a Library,  Prev: Configuring Logging,  Up: Advanced Logging Tutorial

10.6.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 behaviour of the logging package in
these circumstances is dependent on the Python version.

For versions of Python prior to 3.2, the behaviour is as follows:

   * If `logging.raiseExceptions' is ‘False’ (production mode), the
     event is silently dropped.

   * If `logging.raiseExceptions' is ‘True’ (development mode), a
     message ’No handlers could be found for logger X.Y.Z’ is printed
     once.

In Python 3.2 and later, the behaviour is as follows:

   * The event is output using a ’handler of last resort’, stored in
     ‘logging.lastResort’.  This internal handler is not associated with
     any logger, and acts like a *note StreamHandler: b7a. 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.

To obtain the pre-3.2 behaviour, ‘logging.lastResort’ 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

10.6.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: c21. (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 add any handlers
     other than' *note NullHandler: c21. `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 模組

10.6.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: 90b.
class.  When a logger decides to actually log an event, a *note
LogRecord: 90b. 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:
208c. class.  Handlers are responsible for ensuring that a logged
message (in the form of a *note LogRecord: 90b.) 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: 90b.
instances intended for particular destinations.  Each logger can have
zero, one or more handlers associated with it (via the *note
addHandler(): 2094. method of *note Logger: 3ac.).  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(): 20ab. method is used to send the message to its destination.
Most user-defined subclasses of *note Handler: 208c. will need to
override this *note emit(): 20ab.

* Menu:

* Custom Levels::


File: python.info,  Node: Custom Levels,  Up: Logging Levels<2>

10.6.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 模組

10.6.4 Useful Handlers
----------------------

In addition to the base *note Handler: 208c. class, many useful
subclasses are provided:

  1. *note StreamHandler: b7a. instances send messages to streams
     (file-like objects).

  2. *note FileHandler: 20f0. instances send messages to disk files.

  3. *note BaseRotatingHandler: 2105. 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:
     20e1. or *note TimedRotatingFileHandler: 873.

  4. *note RotatingFileHandler: 20e1. instances send messages to disk
     files, with support for maximum log file sizes and log file
     rotation.

  5. *note TimedRotatingFileHandler: 873. instances send messages to
     disk files, rotating the log file at certain timed intervals.

  6. *note SocketHandler: 874. instances send messages to TCP/IP
     sockets.  Since 3.4, Unix domain sockets are also supported.

  7. *note DatagramHandler: 875. instances send messages to UDP sockets.
     Since 3.4, Unix domain sockets are also supported.

  8. *note SMTPHandler: 2131. instances send messages to a designated
     email address.

  9. *note SysLogHandler: a23. instances send messages to a Unix syslog
     daemon, possibly on a remote machine.

  10. *note NTEventLogHandler: 2129. instances send messages to a
     Windows NT/2000/XP event log.

  11. *note MemoryHandler: 20ea. instances send messages to a buffer in
     memory, which is flushed whenever specific criteria are met.

  12. *note HTTPHandler: 716. instances send messages to an HTTP server
     using either ‘GET’ or ‘POST’ semantics.

  13. *note WatchedFileHandler: 2101. 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: 2144. instances send messages to a queue, such
     as those implemented in the *note queue: db. or *note
     multiprocessing: b8. modules.

  15. *note NullHandler: c21. 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:
     20fe. for more information.

3.1 版新加入: The *note NullHandler: c21. class.

3.2 版新加入: The *note QueueHandler: 2144. class.

The *note NullHandler: c21, *note StreamHandler: b7a. and *note
FileHandler: 20f0. classes are defined in the core logging package.  The
other handlers are defined in a sub-module, *note logging.handlers: ad.
(There is also another sub-module, *note logging.config: ac, for
configuration functionality.)

Logged messages are formatted for presentation through instances of the
*note Formatter: 208b. 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
‘BufferingFormatter’ 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: b7c. can be added to both *note Logger: 3ac.
and *note Handler: 208c. instances (through their *note addFilter():
20a3. 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: b7c. 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 模組

10.6.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: 601. and *note KeyboardInterrupt: 198. exceptions are
never swallowed.  Other exceptions which occur during the *note emit():
20ab. method of a *note Handler: 208c. subclass are passed to its *note
handleError(): 20aa. method.

The default implementation of *note handleError(): 20aa. in *note
Handler: 208c. checks to see if a module-level variable,
‘raiseExceptions’, is set.  If set, a traceback is printed to *note
sys.stderr: 314.  If not set, the exception is swallowed.

     備註: The default value of ‘raiseExceptions’ is ‘True’.  This is
     because during development, you typically want to be notified of
     any exceptions that occur.  It’s advised that you set
     ‘raiseExceptions’ to ‘False’ for production usage.


File: python.info,  Node: Using arbitrary objects as messages,  Next: Optimization,  Prev: Exceptions raised during logging,  Up: 如何使用 Logging 模組

10.6.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__(): e3c. 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: 874. emits an event by pickling it
and sending it over the wire.


File: python.info,  Node: Optimization,  Prev: Using arbitrary objects as messages,  Up: 如何使用 Logging 模組

10.6.7 Optimization
-------------------

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(): 208a. 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(): 208a. 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():
     208a. 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(): e69,
                                                    which may help to speed up your code in
                                                    environments like PyPy (which can’t speed
                                                    up code that uses
                                                    *note sys._getframe(): e69.), if and when
                                                    PyPy supports Python 3.x.
                                                    
                                                    
Threading information.                              Set ‘logging.logThreads’ to ‘0’.
                                                    
                                                    
Process information.                                Set ‘logging.logProcesses’ to ‘0’.
                                                    

Also note that the core logging module only includes the basic handlers.
If you don’t import *note logging.handlers: ad. and *note
logging.config: ac, they won’t take up any memory.

也參考
......

Module *note logging: ab.

     API reference for the logging module.

Module *note logging.config: ac.

     Configuration API for the logging module.

Module *note logging.handlers: ad.

     Useful handlers included with the logging module.

*note A logging cookbook: b79.


File: python.info,  Node: Logging Cookbook,  Next: 如何使用正規表達式,  Prev: 如何使用 Logging 模組,  Up: Python HOWTOs

10.7 Logging Cookbook
=====================


Author: 原文作者 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.

* Menu:

* Using logging in multiple modules::
* Logging from multiple threads::
* Multiple handlers and formatters::
* Logging to multiple destinations::
* Configuration server example::
* Dealing with handlers that block::
* Sending and receiving logging events across a network::
* Adding contextual information to your logging output::
* Logging to a single file from multiple processes::
* Using file rotation::
* Use of alternative formatting styles::
* Customizing LogRecord::
* Subclassing QueueHandler - a ZeroMQ example::
* Subclassing QueueListener - a ZeroMQ 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::
* 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::


File: python.info,  Node: Using logging in multiple modules,  Next: Logging from multiple threads,  Up: Logging Cookbook

10.7.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

10.7.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

10.7.3 Multiple handlers and formatters
---------------------------------------

Loggers are plain Python objects.  The *note addHandler(): 2094. 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: Configuration server example,  Prev: Multiple handlers and formatters,  Up: Logging Cookbook

10.7.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='/temp/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.


File: python.info,  Node: Configuration server example,  Next: Dealing with handlers that block,  Prev: Logging to multiple destinations,  Up: Logging Cookbook

10.7.5 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

10.7.6 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: 2131.: 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: 874.
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: 2144. 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: 23bb. 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: 717, which has
been designed as the counterpart to *note QueueHandler: 2144.  A *note
QueueListener: 717. 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: 717. 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!

3.5 版更變: Prior to Python 3.5, the *note QueueListener: 717. 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

10.7.7 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: 874. 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: f1. 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 ‘makePickle()’ method and implementing your alternative
there, as well as adapting the above script to use your alternative
serialization.


File: python.info,  Node: Adding contextual information to your logging output,  Next: Logging to a single file from multiple processes,  Prev: Sending and receiving logging events across a network,  Up: Logging Cookbook

10.7.8 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 ‘Logger’ 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 ‘Logger’
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
‘Logger’ 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

10.7.8.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 ‘LoggerAdapter’
class.  This class is designed to look like a ‘Logger’, so that you can
call ‘debug()’, ‘info()’, ‘warning()’, ‘error()’, ‘exception()’,
‘critical()’ and ‘log()’.  These methods have the same signatures as
their counterparts in ‘Logger’, so you can use the two types of
instances interchangeably.

When you create an instance of ‘LoggerAdapter’, you pass it a ‘Logger’
instance and a dict-like object which contains your contextual
information.  When you call one of the logging methods on an instance of
‘LoggerAdapter’, it delegates the call to the underlying instance of
‘Logger’ passed to its constructor, and arranges to pass the contextual
information in the delegated call.  Here’s a snippet from the code of
‘LoggerAdapter’:

     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 ‘process()’ method of ‘LoggerAdapter’ 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 ‘LogRecord’ instance’s __dict__, allowing you
to use customized strings with your ‘Formatter’ 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 ‘LoggerAdapter’ and override
‘process()’ 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

10.7.8.2 Using objects other than dicts to pass contextual information
......................................................................

You don’t need to pass an actual dict to a ‘LoggerAdapter’ - 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

10.7.8.3 Using Filters to impart contextual information
.......................................................

You can also add contextual information to log output using a
user-defined ‘Filter’.  ‘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 ‘Formatter’.

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: 22f8.) 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: Logging to a single file from multiple processes,  Next: Using file rotation,  Prev: Adding contextual information to your logging output,  Up: Logging Cookbook

10.7.9 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
‘SocketHandler’, 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: 4161. 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: 239c.
class from the *note multiprocessing: b8. module to serialize access to
the file from your processes.  The existing ‘FileHandler’ and subclasses
do not make use of *note multiprocessing: b8. at present, though they
may do so in the future.  Note that at present, the *note
multiprocessing: b8. 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: 2144. 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.


File: python.info,  Node: Using concurrent futures ProcessPoolExecutor,  Up: Logging to a single file from multiple processes

10.7.9.1 Using concurrent.futures.ProcessPoolExecutor
.....................................................

If you want to use *note concurrent.futures.ProcessPoolExecutor: 2a5. 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: 22.):

     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: Using file rotation,  Next: Use of alternative formatting styles,  Prev: Logging to a single file from multiple processes,  Up: Logging Cookbook

10.7.10 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
‘RotatingFileHandler’:

     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

10.7.11 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: 3f0. (added in Python 2.4) and *note
str.format(): 4df. (added in Python 2.6).

Logging (as of 3.2) provides improved support for these two additional
formatting styles.  The ‘Formatter’ 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(): 4df. or *note
string.Template: 3f0.  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(): 4df. or *note string.Template: 3f0. 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(): dd2. 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 ‘LoggerAdapter’ 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 __init__(self, logger, extra=None):
             super().__init__(logger, extra or {})

         def log(self, level, msg, /, *args, **kwargs):
             if self.isEnabledFor(level):
                 msg, kwargs = self.process(msg, kwargs)
                 self.logger._log(level, Message(msg, args), (), **kwargs)

     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.2 or later.


File: python.info,  Node: Customizing LogRecord,  Next: Subclassing QueueHandler - a ZeroMQ example,  Prev: Use of alternative formatting styles,  Up: Logging Cookbook

10.7.12 Customizing ‘LogRecord’
-------------------------------

Every logging event is represented by a *note LogRecord: 90b. instance.
When an event is logged and not filtered out by a logger’s level, a
*note LogRecord: 90b. 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(): 2098, which is called in the normal
     process of logging an event.  This invoked *note LogRecord: 90b.
     directly to create an instance.

   * *note makeLogRecord(): 20bd, 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: 874,
     or in JSON form via an *note HTTPHandler: 716.).

This has usually meant that if you need to do anything special with a
*note LogRecord: 90b, you’ve had to do one of the following.

   * Create your own *note Logger: 3ac. subclass, which overrides *note
     Logger.makeRecord(): 2098, and set it using *note setLoggerClass():
     20ca. before any loggers that you care about are instantiated.

   * Add a *note Filter: b7c. to a logger or handler, which does the
     necessary special manipulation you need when its *note filter():
     20b8. 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: 3ac. 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: 90b.
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: c21.
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: 90b. creation is done through
a factory, which you can specify.  The factory is just a callable you
can set with *note setLogRecordFactory(): 20c0, and interrogate with
*note getLogRecordFactory(): 20bf.  The factory is invoked with the same
signature as the *note LogRecord: 90b. constructor, as *note LogRecord:
90b. 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: b7c.
does not provide the desired result.


File: python.info,  Node: Subclassing QueueHandler - a ZeroMQ example,  Next: Subclassing QueueListener - a ZeroMQ example,  Prev: Customizing LogRecord,  Up: Logging Cookbook

10.7.13 Subclassing QueueHandler - a ZeroMQ example
---------------------------------------------------

You can use a ‘QueueHandler’ 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: Subclassing QueueListener - a ZeroMQ example,  Next: An example dictionary-based configuration,  Prev: Subclassing QueueHandler - a ZeroMQ example,  Up: Logging Cookbook

10.7.14 Subclassing QueueListener - a ZeroMQ example
----------------------------------------------------

You can also subclass ‘QueueListener’ 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)

也參考
......

Module *note logging: ab.

     API reference for the logging module.

Module *note logging.config: ac.

     Configuration API for the logging module.

Module *note logging.handlers: ad.

     Useful handlers included with the logging module.

*note A basic logging tutorial: b77.

*note A more advanced logging tutorial: b78.


File: python.info,  Node: An example dictionary-based configuration,  Next: Using a rotator and namer to customize log rotation processing,  Prev: Subclassing QueueListener - a ZeroMQ example,  Up: Logging Cookbook

10.7.15 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(): b30. to put the configuration into effect:

     LOGGING = {
         'version': 1,
         'disable_existing_loggers': True,
         'formatters': {
             'verbose': {
                 'format': '%(levelname)s %(asctime)s %(module)s %(process)d %(thread)d %(message)s'
             },
             'simple': {
                 'format': '%(levelname)s %(message)s'
             },
         },
         'filters': {
             'special': {
                 '()': 'project.logging.SpecialFilter',
                 'foo': 'bar',
             }
         },
         'handlers': {
             'null': {
                 'level':'DEBUG',
                 'class':'django.utils.log.NullHandler',
             },
             'console':{
                 'level':'DEBUG',
                 'class':'logging.StreamHandler',
                 'formatter': 'simple'
             },
             'mail_admins': {
                 'level': 'ERROR',
                 'class': 'django.utils.log.AdminEmailHandler',
                 'filters': ['special']
             }
         },
         'loggers': {
             'django': {
                 'handlers':['null'],
                 'propagate': True,
                 'level':'INFO',
             },
             '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

10.7.16 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 snippet, which shows zlib-based compression of the log file:

     def namer(name):
         return name + ".gz"

     def rotator(source, dest):
         with open(source, "rb") as sf:
             data = sf.read()
             compressed = zlib.compress(data, 9)
             with open(dest, "wb") as df:
                 df.write(compressed)
         os.remove(source)

     rh = logging.handlers.RotatingFileHandler(...)
     rh.rotator = rotator
     rh.namer = namer

These are not "true" .gz files, as they are bare compressed data, with
no "container" such as you’d find in an actual gzip file.  This snippet
is just for illustration purposes.


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

10.7.17 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

10.7.18 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: a23. 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: 208b. instance to your *note
     SysLogHandler: a23. 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://tools.ietf.org/html/rfc5424.html

   (2) https://tools.ietf.org/html/rfc5424.html#section-6

   (3) https://tools.ietf.org/html/rfc5424.html

   (4) https://tools.ietf.org/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

10.7.19 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:

     from __future__ import unicode_literals

     import json
     import logging

     # This next bit is to ensure the script runs unchanged on 2.x and 3.x
     try:
         unicode
     except NameError:
         unicode = str

     class Encoder(json.JSONEncoder):
         def default(self, o):
             if isinstance(o, set):
                 return tuple(o)
             elif isinstance(o, unicode):
                 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

10.7.20 Customizing handlers with ‘dictConfig()’
------------------------------------------------

There are times when you want to customize logging handlers in
particular ways, and if you use *note dictConfig(): b30. 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(): a7b, 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(): b30, 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(): a7b. makes an appearance.  This approach should work
with any Python version that supports *note dictConfig(): b30. - 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(): a39.

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(): b30. 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(): a38.

Of course, the approach could also be extended to types of handler other
than a *note FileHandler: 20f0. - 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

10.7.21 Using particular formatting styles throughout your application
----------------------------------------------------------------------

In Python 3.2, the *note Formatter: 208b. 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(): 4df. and *note
string.Template: 3f0.  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(): 715, *note info(): 208d. 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(): 4df. or *note string.Template: 3f0. syntax, because
internally the logging package uses %-formatting to merge the format
string and the variable arguments.  There would 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

10.7.21.1 Using LogRecord factories
...................................

In Python 3.2, along with the *note Formatter: 208b. changes mentioned
above, the logging package gained the ability to allow users to set
their own *note LogRecord: 90b. subclasses, using the *note
setLogRecordFactory(): 20c0. function.  You can use this to set your own
subclass of *note LogRecord: 90b, which does the Right Thing by
overriding the *note getMessage(): 20be. 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():
20c0. and *note LogRecord: 90b. for more information.


File: python.info,  Node: Using custom message objects,  Prev: Using LogRecord factories,  Up: Using particular formatting styles throughout your application

10.7.21.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: 20c2.) that when
logging you can use an arbitrary object as a message format string, and
that the logging package will call *note str(): 335. 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(): 4df.:

     >>> __ = 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: 3f0.:

     >>> __ = 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

10.7.22 Configuring filters with ‘dictConfig()’
-----------------------------------------------

You `can' configure filters using *note dictConfig(): b30, though it
might not be obvious at first glance how to do it (hence this recipe).
Since *note Filter: b7c. 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: b7c. subclass with an overridden *note filter(): 20b8.
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: b7c. 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:
     20e7.  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: 20e0. 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(): 4177.
     above.


File: python.info,  Node: Customized exception formatting,  Next: Speaking logging messages,  Prev: Configuring filters with dictConfig,  Up: Logging Cookbook

10.7.23 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: 114. 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

10.7.24 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: fa.  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: Formatting times using UTC GMT via configuration,  Prev: Speaking logging messages,  Up: Logging Cookbook

10.7.25 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: 20ea, 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: b7a. 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: Formatting times using UTC GMT via configuration,  Next: Using a context manager for selective logging,  Prev: Buffering logging messages and outputting them conditionally,  Up: Logging Cookbook

10.7.26 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: 208b.  If you want to do that via configuration, you can use
the *note dictConfig(): b30. 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

10.7.27 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

10.7.28 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,  Prev: A CLI application starter template,  Up: Logging Cookbook

10.7.29 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: 10a. 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 either ‘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 PySide2 and PyQt5
     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)
                 level = random.choice(LEVELS)
                 logger.log(level, 'Message after delay of %3.1f: %d', delay, i, 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')
             f.setStyleHint(f.Monospace)
             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()
         sys.exit(app.exec_())

     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: 如何使用正規表達式,  Next: Socket Programming HOWTO,  Prev: Logging Cookbook,  Up: Python HOWTOs

10.8 如何使用正規表達式
=======================


Author: A.M. Kuchling <<amk@amk.ca>>

Abstract
........

此文件為如何在 Python 中使用 *note re: de. 模組來撰寫正規表達式的入門指
導。進階使用及參考文件請見函式庫參考一章。

* Menu:

* 簡介: 簡介<14>.
* Simple Patterns::
* Using Regular Expressions::
* More Pattern Power::
* Modifying Strings::
* Common Problems::
* Feedback::


File: python.info,  Node: 簡介<14>,  Next: Simple Patterns,  Up: 如何使用正規表達式

10.8.1 簡介
-----------

正規表示式 (也稱為 REs、regexes 或 regex patterns) 是一個輕量且高專業化
的程式語言。在 Python 中可透過內建的 *note re: de. 模組直接使用。你可以
使用此輕量化的語言針對想要匹配的一組字串撰寫規則，這組字串可能包含了英語
句子、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: 簡介<14>,  Up: 如何使用正規表達式

10.8.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

10.8.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 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: 11b. module.  You can use the more restricted
definition of ‘\w’ in a string pattern by supplying the *note re.ASCII:
3cd. 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: 1752. 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: 1756.) 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

10.8.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 qualifiers.  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 repeated qualifier is ‘{m,n}’, where `m' and `n'
are decimal integers.  This qualifier 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.

Readers of a reductionist bent may notice that the three other
qualifiers 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: 如何使用正規表達式

10.8.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: de. 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

10.8.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(): 44f. 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(): 44f. 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: de. module is simply a C extension module included with
Python, just like the *note socket: f0. or *note zlib: 145. 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

10.8.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(): 44f. 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(): 44f.
                        
                        
‘"\\\\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: 279. and will eventually become a *note
SyntaxError: 45d, 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

10.8.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: de. 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: 1040.
                       

*note match(): 1761. and *note search(): 1762. return ‘None’ if no match
can be found.  If they’re successful, a *note match object: 8a2.
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: de. module.  If you have *note tkinter: 10d. available, you may also
want to look at Tools/demo/redemo.py(1), a demonstration program
included with the Python distribution.  It allows you to enter REs and
strings, and displays whether the RE matches or fails.  ‘redemo.py’ can
be quite useful when trying to debug a complicated RE.

This HOWTO uses the standard Python interpreter for its examples.
First, run the Python interpreter, import the *note re: de. 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(): 1761. 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(): 1761. will return a *note match object: 8a2,
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: 8a2. 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(): 1776. returns the substring that was matched by the RE.
*note start(): 177a. and *note end(): 177b. return the starting and
ending index of the match.  *note span(): 177c. returns both start and
end indexes in a single tuple.  Since the *note match(): 1761. method
only checks if the RE matches at the start of a string, ‘start()’ will
always be zero.  However, the *note search(): 1762. 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: 8a2. 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(): 176c. 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: 279. and will
eventually become a *note SyntaxError: 45d.  See *note The Backslash
Plague: 4195.

*note findall(): 176c. has to create the entire list before it can be
returned as the result.  The *note finditer(): 176d. method returns a
sequence of *note match object: 8a2. instances as an *note iterator:
1040.:

     >>> 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)

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Tools/demo/redemo.py


File: python.info,  Node: Module-Level Functions<2>,  Next: Compilation Flags,  Prev: Performing Matches,  Up: Using Regular Expressions

10.8.3.4 Module-Level Functions
...............................

You don’t have to create a pattern object and call its methods; the
*note re: de. module also provides top-level functions called *note
match(): bb8, *note search(): bb7, *note findall(): 968, *note sub():
480, 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: 8a2.
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

10.8.3.5 Compilation Flags
..........................

Compilation flags let you modify some aspects of how regular expressions
work.  Flags are available in the *note re: de. module under two names,
a long name such as ‘IGNORECASE’ and a short, one-letter form such as
‘I’.  (If you’re familiar with Perl’s pattern modifiers, the one-letter
forms use the same letters; the short form of *note re.VERBOSE: 1765. is
*note re.X: 175d, for example.)  Multiple flags can be specified by
bitwise OR-ing them; ‘re.I | re.M’ sets both the ‘I’ and ‘M’ flags, for
example.

Here’s a table of the available flags, followed by a more detailed
explanation of each one.

Flag                                  Meaning
                                      
---------------------------------------------------------------------------------------
                                      
‘ASCII’, ‘A’                          Makes several escapes like ‘\w’, ‘\b’, ‘\s’
                                      and ‘\d’ match only on ASCII characters with
                                      the respective property.
                                      
                                      
‘DOTALL’, ‘S’                         Make ‘.’ match any character, including
                                      newlines.
                                      
                                      
‘IGNORECASE’, ‘I’                     Do case-insensitive matches.
                                      
                                      
‘LOCALE’, ‘L’                         Do a locale-aware match.
                                      
                                      
‘MULTILINE’, ‘M’                      Multi-line matching, affecting ‘^’ and ‘$’.
                                      
                                      
‘VERBOSE’, ‘X’ (for ’extended’)       Enable verbose REs, which can be organized
                                      more cleanly and understandably.
                                      

 -- Data: I

 -- Data: 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 ‘ASCII’ flag is used to disable non-ASCII matches.
     When the Unicode patterns ‘[a-z]’ or ‘[A-Z]’ are used in
     combination with the ‘IGNORECASE’ 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 ‘LOCALE’ flag.

 -- Data: L

 -- Data: 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 ‘LOCALE’ 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.

 -- Data: M

 -- Data: MULTILINE

     (‘^’ and ‘$’ haven’t been explained yet; they’ll be introduced in
     section *note More Metacharacters: 4199.)

     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).

 -- Data: S

 -- Data: DOTALL

     Makes the ‘'.'’ special character match any character at all,
     including a newline; without this flag, ‘'.'’ will match anything
     `except' a newline.

 -- Data: A

 -- Data: 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.

 -- Data: X

 -- Data: 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: 1765.; 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: 1765.


File: python.info,  Node: More Pattern Power,  Next: Modifying Strings,  Prev: Using Regular Expressions,  Up: 如何使用正規表達式

10.8.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

10.8.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 ‘MULTILINE’ flag has
     been set, this will only match at the beginning of the string.  In
     ‘MULTILINE’ 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 ‘MULTILINE’
     mode, ‘\A’ and ‘^’ are effectively the same.  In ‘MULTILINE’ 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

10.8.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 repeating qualifier, 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(): 1776, *note start(): 177a, *note end(): 177b,
and *note span(): 177c.  Groups are numbered starting with 0.  Group 0
is always present; it’s the whole RE, so *note match object: 8a2.
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(): 1776. 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(): 1778. 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

10.8.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: 8a2. 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(): 1779.:

     >>> 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: 98. 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

10.8.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: 如何使用正規表達式

10.8.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::


File: python.info,  Node: Splitting Strings,  Next: Search and Replace,  Up: Modifying Strings

10.8.5.1 Splitting Strings
..........................

The *note split(): 176b. 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(): 7a6. 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(): 3cf. 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(): 3cf. 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,  Prev: Splitting Strings,  Up: Modifying Strings

10.8.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(): 176e. 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(): 176e. 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(): 176f. 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: 8a2. 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(): 480. 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: 如何使用正規表達式

10.8.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

10.8.6.1 Use String Methods
...........................

Sometimes using the *note re: de. module is a mistake.  If you’re
matching a fixed string, or a single character class, and you’re not
using any *note re: de. features such as the *note IGNORECASE: 1764.
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(): 480.
seems like the function to use for this, but consider the *note
replace(): 1659. 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(): 1658. 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: de. 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

10.8.6.2 match() versus search()
................................

The *note match(): bb8. function only checks if the RE matches at the
beginning of the string while *note search(): bb7. 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(): bb7. 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(): bb8, and
just add ‘.*’ to the front of your RE. Resist this temptation and use
*note re.search(): bb7. 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(): bb7. instead.


File: python.info,  Node: Greedy versus Non-Greedy,  Next: Using re VERBOSE,  Prev: match versus search,  Up: Common Problems

10.8.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 qualifiers ‘*?’,
‘+?’, ‘??’, 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

10.8.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: 1765. 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: 如何使用正規表達式

10.8.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 Programming HOWTO,  Next: 如何排序,  Prev: 如何使用正規表達式,  Up: Python HOWTOs

10.9 Socket Programming HOWTO
=============================


Author: Gordon McMillan

Abstract
........

Sockets are used nearly everywhere, but are one of the most severely
misunderstood technologies around.  This is a 10,000 foot overview of
sockets.  It’s not really a tutorial - you’ll still have work to do in
getting things operational.  It doesn’t cover the fine points (and there
are a lot of them), but I hope it will give you enough background to
begin using them decently.

* Menu:

* Sockets::
* Creating a Socket::
* Using a Socket::
* Disconnecting::
* Non-blocking Sockets::


File: python.info,  Node: Sockets,  Next: Creating a Socket,  Up: Socket Programming HOWTO

10.9.1 Sockets
--------------

I’m only going to talk about INET (i.e.  IPv4) sockets, but they account
for at least 99% of the sockets in use.  And I’ll only talk about STREAM
(i.e.  TCP) sockets - unless you really know what you’re doing (in which
case this HOWTO isn’t for you!), you’ll get better behavior and
performance from a STREAM socket than anything else.  I will try to
clear up the mystery of what a socket is, as well as some hints on how
to work with blocking and non-blocking sockets.  But I’ll start by
talking about blocking sockets.  You’ll need to know how they work
before dealing with non-blocking sockets.

Part of the trouble with understanding these things is that "socket" can
mean a number of subtly different things, depending on context.  So
first, let’s make a distinction between a "client" socket - an endpoint
of a conversation, and a "server" socket, which is more like a
switchboard operator.  The client application (your browser, for
example) uses "client" sockets exclusively; the web server it’s talking
to uses both "server" sockets and "client" sockets.

* Menu:

* History::


File: python.info,  Node: History,  Up: Sockets

10.9.1.1 History
................

Of the various forms of IPC (Inter Process Communication), sockets are
by far the most popular.  On any given platform, there are likely to be
other forms of IPC that are faster, but for cross-platform
communication, sockets are about the only game in town.

They were invented in Berkeley as part of the BSD flavor of Unix.  They
spread like wildfire with the Internet.  With good reason — the
combination of sockets with INET makes talking to arbitrary machines
around the world unbelievably easy (at least compared to other schemes).


File: python.info,  Node: Creating a Socket,  Next: Using a Socket,  Prev: Sockets,  Up: Socket Programming HOWTO

10.9.2 Creating a Socket
------------------------

Roughly speaking, when you clicked on the link that brought you to this
page, your browser did something like the following:

     # 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))

When the ‘connect’ completes, the socket ‘s’ can be used to send in a
request for the text of the page.  The same socket will read the reply,
and then be destroyed.  That’s right, destroyed.  Client sockets are
normally only used for one exchange (or a small set of sequential
exchanges).

What happens in the web server is a bit more complex.  First, the web
server creates a "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)

A couple things to notice: we used ‘socket.gethostname()’ so that the
socket would be visible to the outside world.  If we had used
‘s.bind(('localhost', 80))’ or ‘s.bind(('127.0.0.1', 80))’ we would
still have a "server" socket, but one that was only visible within the
same machine.  ‘s.bind(('', 80))’ specifies that the socket is reachable
by any address the machine happens to have.

A second thing to note: low number ports are usually reserved for "well
known" services (HTTP, SNMP etc).  If you’re playing around, use a nice
high number (4 digits).

Finally, the argument to ‘listen’ tells the socket library that we want
it to queue up as many as 5 connect requests (the normal max) before
refusing outside connections.  If the rest of the code is written
properly, that should be plenty.

Now that we have a "server" socket, listening on port 80, we can enter
the mainloop of the web server:

     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()

There’s actually 3 general ways in which this loop could work -
dispatching a thread to handle ‘clientsocket’, create a new process to
handle ‘clientsocket’, or restructure this app to use non-blocking
sockets, and multiplex between our "server" socket and any active
‘clientsocket’s using ‘select’.  More about that later.  The important
thing to understand now is this: this is `all' a "server" socket does.
It doesn’t send any data.  It doesn’t receive any data.  It just
produces "client" sockets.  Each ‘clientsocket’ is created in response
to some `other' "client" socket doing a ‘connect()’ to the host and port
we’re bound to.  As soon as we’ve created that ‘clientsocket’, we go
back to listening for more connections.  The two "clients" are free to
chat it up - they are using some dynamically allocated port which will
be recycled when the conversation ends.

* Menu:

* IPC::


File: python.info,  Node: IPC,  Up: Creating a Socket

10.9.2.1 IPC
............

If you need fast IPC between two processes on one machine, you should
look into pipes or shared memory.  If you do decide to use AF_INET
sockets, bind the "server" socket to ‘'localhost'’.  On most platforms,
this will take a shortcut around a couple of layers of network code and
be quite a bit faster.

也參考
......

The *note multiprocessing: b8. integrates cross-platform IPC into a
higher-level API.


File: python.info,  Node: Using a Socket,  Next: Disconnecting,  Prev: Creating a Socket,  Up: Socket Programming HOWTO

10.9.3 Using a Socket
---------------------

The first thing to note, is that the web browser’s "client" socket and
the web server’s "client" socket are identical beasts.  That is, this is
a "peer to peer" conversation.  Or to put it another way, `as the
designer, you will have to decide what the rules of etiquette are for a
conversation'.  Normally, the ‘connect’ing socket starts the
conversation, by sending in a request, or perhaps a signon.  But that’s
a design decision - it’s not a rule of sockets.

Now there are two sets of verbs to use for communication.  You can use
‘send’ and ‘recv’, or you can transform your client socket into a
file-like beast and use ‘read’ and ‘write’.  The latter is the way Java
presents its sockets.  I’m not going to talk about it here, except to
warn you that you need to use ‘flush’ on sockets.  These are buffered
"files", and a common mistake is to ‘write’ something, and then ‘read’
for a reply.  Without a ‘flush’ in there, you may wait forever for the
reply, because the request may still be in your output buffer.

Now we come to the major stumbling block of sockets - ‘send’ and ‘recv’
operate on the network buffers.  They do not necessarily handle all the
bytes you hand them (or expect from them), because their major focus is
handling the network buffers.  In general, they return when the
associated network buffers have been filled (‘send’) or emptied
(‘recv’).  They then tell you how many bytes they handled.  It is `your'
responsibility to call them again until your message has been completely
dealt with.

When a ‘recv’ returns 0 bytes, it means the other side has closed (or is
in the process of closing) the connection.  You will not receive any
more data on this connection.  Ever.  You may be able to send data
successfully; I’ll talk more about this later.

A protocol like HTTP uses a socket for only one transfer.  The client
sends a request, then reads a reply.  That’s it.  The socket is
discarded.  This means that a client can detect the end of the reply by
receiving 0 bytes.

But if you plan to reuse your socket for further transfers, you need to
realize that `there is no' EOT (End of Transfer) `on a socket.'  I
repeat: if a socket ‘send’ or ‘recv’ returns after handling 0 bytes, the
connection has been broken.  If the connection has `not' been broken,
you may wait on a ‘recv’ forever, because the socket will `not' tell you
that there’s nothing more to read (for now).  Now if you think about
that a bit, you’ll come to realize a fundamental truth of sockets:
`messages must either be fixed length' (yuck), `or be delimited'
(shrug), `or indicate how long they are' (much better), `or end by
shutting down the connection'.  The choice is entirely yours, (but some
ways are righter than others).

Assuming you don’t want to end the connection, the simplest solution is
a fixed length message:

     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)

The sending code here is usable for almost any messaging scheme - in
Python you send strings, and you can use ‘len()’ to determine its length
(even if it has embedded ‘\0’ characters).  It’s mostly the receiving
code that gets more complex.  (And in C, it’s not much worse, except you
can’t use ‘strlen’ if the message has embedded ‘\0’s.)

The easiest enhancement is to make the first character of the message an
indicator of message type, and have the type determine the length.  Now
you have two ‘recv’s - the first to get (at least) that first character
so you can look up the length, and the second in a loop to get the rest.
If you decide to go the delimited route, you’ll be receiving in some
arbitrary chunk size, (4096 or 8192 is frequently a good match for
network buffer sizes), and scanning what you’ve received for a
delimiter.

One complication to be aware of: if your conversational protocol allows
multiple messages to be sent back to back (without some kind of reply),
and you pass ‘recv’ an arbitrary chunk size, you may end up reading the
start of a following message.  You’ll need to put that aside and hold
onto it, until it’s needed.

Prefixing the message with its length (say, as 5 numeric characters)
gets more complex, because (believe it or not), you may not get all 5
characters in one ‘recv’.  In playing around, you’ll get away with it;
but in high network loads, your code will very quickly break unless you
use two ‘recv’ loops - the first to determine the length, the second to
get the data part of the message.  Nasty.  This is also when you’ll
discover that ‘send’ does not always manage to get rid of everything in
one pass.  And despite having read this, you will eventually get bit by
it!

In the interests of space, building your character, (and preserving my
competitive position), these enhancements are left as an exercise for
the reader.  Lets move on to cleaning up.

* Menu:

* Binary Data::


File: python.info,  Node: Binary Data,  Up: Using a Socket

10.9.3.1 Binary Data
....................

It is perfectly possible to send binary data over a socket.  The major
problem is that not all machines use the same formats for binary data.
For example, a Motorola chip will represent a 16 bit integer with the
value 1 as the two hex bytes 00 01.  Intel and DEC, however, are
byte-reversed - that same 1 is 01 00.  Socket libraries have calls for
converting 16 and 32 bit integers - ‘ntohl, htonl, ntohs, htons’ where
"n" means `network' and "h" means `host', "s" means `short' and "l"
means `long'.  Where network order is host order, these do nothing, but
where the machine is byte-reversed, these swap the bytes around
appropriately.

In these days of 32 bit machines, the ascii representation of binary
data is frequently smaller than the binary representation.  That’s
because a surprising amount of the time, all those longs have the value
0, or maybe 1.  The string "0" would be two bytes, while binary is four.
Of course, this doesn’t fit well with fixed-length messages.  Decisions,
decisions.


File: python.info,  Node: Disconnecting,  Next: Non-blocking Sockets,  Prev: Using a Socket,  Up: Socket Programming HOWTO

10.9.4 Disconnecting
--------------------

Strictly speaking, you’re supposed to use ‘shutdown’ on a socket before
you ‘close’ it.  The ‘shutdown’ is an advisory to the socket at the
other end.  Depending on the argument you pass it, it can mean "I’m not
going to send anymore, but I’ll still listen", or "I’m not listening,
good riddance!".  Most socket libraries, however, are so used to
programmers neglecting to use this piece of etiquette that normally a
‘close’ is the same as ‘shutdown(); close()’.  So in most situations, an
explicit ‘shutdown’ is not needed.

One way to use ‘shutdown’ effectively is in an HTTP-like exchange.  The
client sends a request and then does a ‘shutdown(1)’.  This tells the
server "This client is done sending, but can still receive."  The server
can detect "EOF" by a receive of 0 bytes.  It can assume it has the
complete request.  The server sends a reply.  If the ‘send’ completes
successfully then, indeed, the client was still receiving.

Python takes the automatic shutdown a step further, and says that when a
socket is garbage collected, it will automatically do a ‘close’ if it’s
needed.  But relying on this is a very bad habit.  If your socket just
disappears without doing a ‘close’, the socket at the other end may hang
indefinitely, thinking you’re just being slow.  `Please' ‘close’ your
sockets when you’re done.

* Menu:

* When Sockets Die::


File: python.info,  Node: When Sockets Die,  Up: Disconnecting

10.9.4.1 When Sockets Die
.........................

Probably the worst thing about using blocking sockets is what happens
when the other side comes down hard (without doing a ‘close’).  Your
socket is likely to hang.  TCP is a reliable protocol, and it will wait
a long, long time before giving up on a connection.  If you’re using
threads, the entire thread is essentially dead.  There’s not much you
can do about it.  As long as you aren’t doing something dumb, like
holding a lock while doing a blocking read, the thread isn’t really
consuming much in the way of resources.  Do `not' try to kill the thread
- part of the reason that threads are more efficient than processes is
that they avoid the overhead associated with the automatic recycling of
resources.  In other words, if you do manage to kill the thread, your
whole process is likely to be screwed up.


File: python.info,  Node: Non-blocking Sockets,  Prev: Disconnecting,  Up: Socket Programming HOWTO

10.9.5 Non-blocking Sockets
---------------------------

If you’ve understood the preceding, you already know most of what you
need to know about the mechanics of using sockets.  You’ll still use the
same calls, in much the same ways.  It’s just that, if you do it right,
your app will be almost inside-out.

In Python, you use ‘socket.setblocking(0)’ to make it non-blocking.  In
C, it’s more complex, (for one thing, you’ll need to choose between the
BSD flavor ‘O_NONBLOCK’ and the almost indistinguishable POSIX flavor
‘O_NDELAY’, which is completely different from ‘TCP_NODELAY’), but it’s
the exact same idea.  You do this after creating the socket, but before
using it.  (Actually, if you’re nuts, you can switch back and forth.)

The major mechanical difference is that ‘send’, ‘recv’, ‘connect’ and
‘accept’ can return without having done anything.  You have (of course)
a number of choices.  You can check return code and error codes and
generally drive yourself crazy.  If you don’t believe me, try it
sometime.  Your app will grow large, buggy and suck CPU. So let’s skip
the brain-dead solutions and do it right.

Use ‘select’.

In C, coding ‘select’ is fairly complex.  In Python, it’s a piece of
cake, but it’s close enough to the C version that if you understand
‘select’ in Python, you’ll have little trouble with it in C:

     ready_to_read, ready_to_write, in_error = \
                    select.select(
                       potential_readers,
                       potential_writers,
                       potential_errs,
                       timeout)

You pass ‘select’ three lists: the first contains all sockets that you
might want to try reading; the second all the sockets you might want to
try writing to, and the last (normally left empty) those that you want
to check for errors.  You should note that a socket can go into more
than one list.  The ‘select’ call is blocking, but you can give it a
timeout.  This is generally a sensible thing to do - give it a nice long
timeout (say a minute) unless you have good reason to do otherwise.

In return, you will get three lists.  They contain the sockets that are
actually readable, writable and in error.  Each of these lists is a
subset (possibly empty) of the corresponding list you passed in.

If a socket is in the output readable list, you can be
as-close-to-certain-as-we-ever-get-in-this-business that a ‘recv’ on
that socket will return `something'.  Same idea for the writable list.
You’ll be able to send `something'.  Maybe not all you want to, but
`something' is better than nothing.  (Actually, any reasonably healthy
socket will return as writable - it just means outbound network buffer
space is available.)

If you have a "server" socket, put it in the potential_readers list.  If
it comes out in the readable list, your ‘accept’ will (almost certainly)
work.  If you have created a new socket to ‘connect’ to someone else,
put it in the potential_writers list.  If it shows up in the writable
list, you have a decent chance that it has connected.

Actually, ‘select’ can be handy even with blocking sockets.  It’s one
way of determining whether you will block - the socket returns as
readable when there’s something in the buffers.  However, this still
doesn’t help with the problem of determining whether the other end is
done, or just busy with something else.

`Portability alert': On Unix, ‘select’ works both with the sockets and
files.  Don’t try this on Windows.  On Windows, ‘select’ works with
sockets only.  Also note that in C, many of the more advanced socket
options are done differently on Windows.  In fact, on Windows I usually
use threads (which work very, very well) with my sockets.


File: python.info,  Node: 如何排序,  Next: Unicode HOWTO,  Prev: Socket Programming HOWTO,  Up: Python HOWTOs

10.10 如何排序
==============


Author: Andrew Dalke and Raymond Hettinger


Release: 0.1

Python lists have a built-in *note list.sort(): 44a. method that
modifies the list in-place.  There is also a *note sorted(): 449.
built-in function that builds a new sorted list from an iterable.

在此文件，我們使用Python進行各種方式排序資料

* Menu:

* 排序 基本::
* Key Functions::
* Operator Module Functions::
* 升冪與降冪::
* Sort Stability and Complex Sorts::
* The Old Way Using Decorate-Sort-Undecorate::
* The Old Way Using the cmp Parameter::
* Odd and Ends::


File: python.info,  Node: 排序 基本,  Next: Key Functions,  Up: 如何排序

10.10.1 排序 基本
-----------------

A simple ascending sort is very easy: just call the *note sorted(): 449.
function.  It returns a new sorted list:

     >>> sorted([5, 2, 3, 1, 4])
     [1, 2, 3, 4, 5]

You can also use the *note list.sort(): 44a. method.  It modifies the
list in-place (and returns ‘None’ to avoid confusion).  Usually it’s
less convenient than *note sorted(): 449. - but if you don’t need the
original list, it’s slightly more efficient.

     >>> a = [5, 2, 3, 1, 4]
     >>> a.sort()
     >>> a
     [1, 2, 3, 4, 5]

Another difference is that the *note list.sort(): 44a. method is only
defined for lists.  In contrast, the *note sorted(): 449. function
accepts any iterable.

     >>> 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,  Prev: 排序 基本,  Up: 如何排序

10.10.2 Key Functions
---------------------

Both *note list.sort(): 44a. and *note sorted(): 449. have a `key'
parameter to specify a function to be called on each list element prior
to making comparisons.

For example, here’s a case-insensitive string comparison:

     >>> sorted("This is a test string from Andrew".split(), key=str.lower)
     ['a', 'Andrew', 'from', 'is', 'string', 'test', 'This']

The value of the `key' parameter should be a function that takes a
single argument and returns a key to use for sorting purposes.  This
technique is fast because the key function is called exactly once for
each input record.

A common pattern is to sort complex objects using some of the object’s
indices as keys.  For example:

     >>> 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)]

The same technique works for objects with named attributes.  For
example:

     >>> 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)]


File: python.info,  Node: Operator Module Functions,  Next: 升冪與降冪,  Prev: Key Functions,  Up: 如何排序

10.10.3 Operator Module Functions
---------------------------------

The key-function patterns shown above are very common, so Python
provides convenience functions to make accessor functions easier and
faster.  The *note operator: c3. module has *note itemgetter(): 262,
*note attrgetter(): 720, and a *note methodcaller(): 721. function.

Using those functions, the above examples become simpler and faster:

     >>> 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)]

The operator module functions allow multiple levels of sorting.  For
example, to sort by `grade' then by `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)]


File: python.info,  Node: 升冪與降冪,  Next: Sort Stability and Complex Sorts,  Prev: Operator Module Functions,  Up: 如何排序

10.10.4 升冪與降冪
------------------

Both *note list.sort(): 44a. and *note sorted(): 449. accept a `reverse'
parameter with a boolean value.  This is used to flag descending sorts.
For example, to get the student data in reverse `age' order:

     >>> 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: Sort Stability and Complex Sorts,  Next: The Old Way Using Decorate-Sort-Undecorate,  Prev: 升冪與降冪,  Up: 如何排序

10.10.5 Sort Stability and Complex Sorts
----------------------------------------

Sorts are guaranteed to be stable(1).  That means that when multiple
records have the same key, their original order is preserved.

     >>> data = [('red', 1), ('blue', 1), ('red', 2), ('blue', 2)]
     >>> sorted(data, key=itemgetter(0))
     [('blue', 1), ('blue', 2), ('red', 1), ('red', 2)]

Notice how the two records for `blue' retain their original order so
that ‘('blue', 1)’ is guaranteed to precede ‘('blue', 2)’.

This wonderful property lets you build complex sorts in a series of
sorting steps.  For example, to sort the student data by descending
`grade' and then ascending `age', do the `age' sort first and then sort
again using `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)]

This can be abstracted out into a wrapper function that can take a list
and tuples of field and order to sort them on multiple passes.

     >>> 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)]

The Timsort(2) algorithm used in Python does multiple sorts efficiently
because it can take advantage of any ordering already present in a
dataset.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Sorting_algorithm#Stability

   (2) https://en.wikipedia.org/wiki/Timsort


File: python.info,  Node: The Old Way Using Decorate-Sort-Undecorate,  Next: The Old Way Using the cmp Parameter,  Prev: Sort Stability and Complex Sorts,  Up: 如何排序

10.10.6 The Old Way Using Decorate-Sort-Undecorate
--------------------------------------------------

This idiom is called Decorate-Sort-Undecorate after its three steps:

   * First, the initial list is decorated with new values that control
     the sort order.

   * Second, the decorated list is sorted.

   * Finally, the decorations are removed, creating a list that contains
     only the initial values in the new order.

For example, to sort the student data by `grade' using the DSU approach:

     >>> 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)]

This idiom works because tuples are compared lexicographically; the
first items are compared; if they are the same then the second items are
compared, and so on.

It is not strictly necessary in all cases to include the index `i' in
the decorated list, but including it gives two benefits:

   * The sort is stable – if two items have the same key, their order
     will be preserved in the sorted list.

   * The original items do not have to be comparable because the
     ordering of the decorated tuples will be determined by at most the
     first two items.  So for example the original list could contain
     complex numbers which cannot be sorted directly.

Another name for this idiom is Schwartzian transform(1), after Randal L.
Schwartz, who popularized it among Perl programmers.

Now that Python sorting provides key-functions, this technique is not
often needed.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Schwartzian_transform


File: python.info,  Node: The Old Way Using the cmp Parameter,  Next: Odd and Ends,  Prev: The Old Way Using Decorate-Sort-Undecorate,  Up: 如何排序

10.10.7 The Old Way Using the `cmp' Parameter
---------------------------------------------

Many constructs given in this HOWTO assume Python 2.4 or later.  Before
that, there was no *note sorted(): 449. builtin and *note list.sort():
44a. took no keyword arguments.  Instead, all of the Py2.x versions
supported a `cmp' parameter to handle user specified comparison
functions.

In Py3.0, the `cmp' parameter was removed entirely (as part of a larger
effort to simplify and unify the language, eliminating the conflict
between rich comparisons and the ‘__cmp__()’ magic method).

In Py2.x, sort allowed an optional function which can be called for
doing the comparisons.  That function should take two arguments to be
compared and then return a negative value for less-than, return zero if
they are equal, or return a positive value for greater-than.  For
example, we can do:

     >>> def numeric_compare(x, y):
     ...     return x - y
     >>> sorted([5, 2, 4, 1, 3], cmp=numeric_compare)
     [1, 2, 3, 4, 5]

Or you can reverse the order of comparison with:

     >>> def reverse_numeric(x, y):
     ...     return y - x
     >>> sorted([5, 2, 4, 1, 3], cmp=reverse_numeric)
     [5, 4, 3, 2, 1]

When porting code from Python 2.x to 3.x, the situation can arise when
you have the user supplying a comparison function and you need to
convert that to a key function.  The following wrapper makes that easy
to do:

     def cmp_to_key(mycmp):
         'Convert a cmp= function into a key= function'
         class K:
             def __init__(self, obj, *args):
                 self.obj = obj
             def __lt__(self, other):
                 return mycmp(self.obj, other.obj) < 0
             def __gt__(self, other):
                 return mycmp(self.obj, other.obj) > 0
             def __eq__(self, other):
                 return mycmp(self.obj, other.obj) == 0
             def __le__(self, other):
                 return mycmp(self.obj, other.obj) <= 0
             def __ge__(self, other):
                 return mycmp(self.obj, other.obj) >= 0
             def __ne__(self, other):
                 return mycmp(self.obj, other.obj) != 0
         return K

To convert to a key function, just wrap the old comparison function:

     >>> sorted([5, 2, 4, 1, 3], key=cmp_to_key(reverse_numeric))
     [5, 4, 3, 2, 1]

In Python 3.2, the *note functools.cmp_to_key(): b5b. function was added
to the *note functools: 85. module in the standard library.


File: python.info,  Node: Odd and Ends,  Prev: The Old Way Using the cmp Parameter,  Up: 如何排序

10.10.8 Odd and Ends
--------------------

   * For locale aware sorting, use *note locale.strxfrm(): 3088. for a
     key function or *note locale.strcoll(): 3086. for a comparison
     function.

   * The `reverse' parameter still maintains sort stability (so that
     records with equal keys retain the original order).  Interestingly,
     that effect can be simulated without the parameter by using the
     builtin *note reversed(): 18f. function twice:

          >>> 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)]

   * The sort routines are guaranteed to use *note __lt__(): c39. when
     making comparisons between two objects.  So, it is easy to add a
     standard sort order to a class by defining an *note __lt__(): c39.
     method:

          >>> Student.__lt__ = lambda self, other: self.age < other.age
          >>> sorted(student_objects)
          [('dave', 'B', 10), ('jane', 'B', 12), ('john', 'A', 15)]

   * Key functions need not depend directly on the objects being sorted.
     A key function can also access external resources.  For instance,
     if the student grades are stored in a dictionary, they can be used
     to sort a separate list of student names:

          >>> students = ['dave', 'john', 'jane']
          >>> newgrades = {'john': 'F', 'jane':'A', 'dave': 'C'}
          >>> sorted(students, key=newgrades.__getitem__)
          ['jane', 'dave', 'john']


File: python.info,  Node: Unicode HOWTO,  Next: 如何使用urllib套件取得網路資源,  Prev: 如何排序,  Up: Python HOWTOs

10.11 Unicode HOWTO
===================


Release: 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::
* Acknowledgements: Acknowledgements<10>.


File: python.info,  Node: Introduction to Unicode,  Next: Python's Unicode Support,  Up: Unicode HOWTO

10.11.1 Introduction to Unicode
-------------------------------

* Menu:

* Definitions::
* Encodings::
* References: References<3>.


File: python.info,  Node: Definitions,  Next: Encodings,  Up: Introduction to Unicode

10.11.1.1 Definitions
.....................

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, with some 110 thousand assigned so far).  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.


File: python.info,  Node: Encodings,  Next: References<3>,  Prev: Definitions,  Up: Introduction to Unicode

10.11.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

10.11.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) http://www.unicode.org

   (2) http://www.unicode.org/history/

   (3) https://www.youtube.com/watch?v=MijmeoH9LT4

   (4) http://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

10.11.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

10.11.2.1 The String Type
.........................

Since Python 3.0, the language’s *note str: 335. 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(): c3d.
method of *note bytes: 336.  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: 1fe.
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: 694. 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():
142d. 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(): 142c. 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

10.11.2.2 Converting to Bytes
.............................

The opposite method of *note bytes.decode(): c3d. is *note str.encode():
c3c, which returns a *note bytes: 336. representation of the Unicode
string, encoded in the requested `encoding'.

The `errors' parameter is the same as the parameter of the *note
decode(): c3d. 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: 1c. module.  Implementing new
encodings also requires understanding the *note codecs: 1c. 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

10.11.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(): 142d. 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://www.python.org/dev/peps/pep-0263


File: python.info,  Node: Unicode Properties,  Next: Comparing Strings,  Prev: Unicode Literals in Python Source Code,  Up: Python's Unicode Support

10.11.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) http://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

10.11.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(): 6b5.
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: 11b. module’s *note normalize():
10b4. function that converts strings to one of several normal forms,
where letters followed by a combining character are replaced with single
characters.  ‘normalize()’ 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:

     $ python3 compare-strs.py
     length of first string= 1
     length of second string= 2
     True

The first argument to the *note normalize(): 10b4. 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 ‘casefold()’ 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

10.11.2.6 Unicode Regular Expressions
.....................................

The regular expressions supported by the *note re: de. 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: 3cd. flag to *note compile(): 44f,
‘\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: 3cd. 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

10.11.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: 335. type is described in the Python library reference at
*note Text Sequence Type — str: 1228.

The documentation for the *note unicodedata: 11b. module.

The documentation for the *note codecs: 1c. module.

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) 
http://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: Acknowledgements<10>,  Prev: Python's Unicode Support,  Up: Unicode HOWTO

10.11.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(): 4f5. 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(): 200b. and *note write(): 200e.  This works through *note
open(): 4f5.’s `encoding' and `errors' parameters which are interpreted
just like those in *note str.encode(): c3c. and *note bytes.decode():
c3d.

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

10.11.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
filesystem encoding 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(): 4fb. 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: c5. module such as *note os.stat(): 1f2. will
also accept Unicode filenames.

The *note os.listdir(): a46. 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(): a46.
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 filesystem
encoding 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

10.11.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:
193. 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

10.11.3.3 Converting Between File Encodings
...........................................

The *note StreamRecoder: fd2. 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: fd2. 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

10.11.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

10.11.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) http://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) http://pyvideo.org/video/1768/the-guts-of-unicode-in-python


File: python.info,  Node: Acknowledgements<10>,  Prev: Reading and Writing Unicode Data,  Up: Unicode HOWTO

10.11.4 Acknowledgements
------------------------

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 HOWTOs

10.12 如何使用urllib套件取得網路資源
====================================


Author: 原文作者 Michael Foord(1)

     備註: 這份指南出自於早期版本的法文翻譯 urllib2 - Le Manuel
     manquant(2).

* Menu:

* 簡介: 簡介<15>.
* 從URL取得資源::
* Handling Exceptions::
* info and geturl::
* Openers and Handlers::
* Basic Authentication::
* Proxies::
* Sockets and Layers::
* 註解: 註解<3>.

   ---------- Footnotes ----------

   (1) http://www.voidspace.org.uk/python/index.shtml

   (2) 
http://www.voidspace.org.uk/python/articles/urllib2_francais.shtml


File: python.info,  Node: 簡介<15>,  Next: 從URL取得資源,  Up: 如何使用urllib套件取得網路資源

10.12.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: 121. 這份文件，你還是會需要它!

   ---------- Footnotes ----------

   (1) http://www.voidspace.org.uk/python/articles/authentication.shtml

   (2) https://tools.ietf.org/html/rfc2616.html


File: python.info,  Node: 從URL取得資源,  Next: Handling Exceptions,  Prev: 簡介<15>,  Up: 如何使用urllib套件取得網路資源

10.12.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(): 25e. and
*note tempfile.NamedTemporaryFile(): d4e. 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://www.voidspace.org.uk')
     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取得資源

10.12.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: 120.
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取得資源

10.12.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: 41d8. which comes after we have a look at what happens when
things go wrong.

   ---------- Footnotes ----------

   (1) (1) Google for example.

   (2) (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) (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) (4) For details of more HTTP request headers, see Quick Reference
to HTTP Headers (http://jkorpela.fi/http.html).


File: python.info,  Node: Handling Exceptions,  Next: info and geturl,  Prev: 從URL取得資源,  Up: 如何使用urllib套件取得網路資源

10.12.3 Handling Exceptions
---------------------------

`urlopen' raises ‘URLError’ when it cannot handle a response (though as
usual with Python APIs, built-in exceptions such as *note ValueError:
1fc, *note TypeError: 193. etc.  may also be raised).

‘HTTPError’ is the subclass of ‘URLError’ raised in the specific case of
HTTP URLs.

The exception classes are exported from the *note urllib.error: 11f.
module.

* Menu:

* URLError::
* HTTPError::
* Wrapping it Up::


File: python.info,  Node: URLError,  Next: HTTPError,  Up: Handling Exceptions

10.12.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.

e.g.

     >>> 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

10.12.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
‘HTTPError’.  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 ‘HTTPError’ instance raised will have an integer ’code’ attribute,
which corresponds to the error sent by the server.

* Menu:

* Error Codes::

   ---------- Footnotes ----------

   (1) https://tools.ietf.org/html/rfc2616.html


File: python.info,  Node: Error Codes,  Up: HTTPError

10.12.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: 2cd7. 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 ‘HTTPError’ 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://tools.ietf.org/html/rfc2616.html


File: python.info,  Node: Wrapping it Up,  Prev: HTTPError,  Up: Handling Exceptions

10.12.3.4 Wrapping it Up
........................

So if you want to be prepared for ‘HTTPError’ `or' ‘URLError’ 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

10.12.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 ‘HTTPError’.


File: python.info,  Node: Number 2,  Prev: Number 1,  Up: Wrapping it Up

10.12.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套件取得網路資源

10.12.4 info and geturl
-----------------------

The response returned by urlopen (or the ‘HTTPError’ instance) has two
useful methods ‘info()’ and ‘geturl()’ and is defined in the module
*note urllib.response: 122..

`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 ‘http.client.HTTPMessage’ 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) http://jkorpela.fi/http.html


File: python.info,  Node: Openers and Handlers,  Next: Basic Authentication,  Prev: info and geturl,  Up: 如何使用urllib套件取得網路資源

10.12.5 Openers and Handlers
----------------------------

When you fetch a URL you use an opener (an instance of the perhaps
confusingly-named *note urllib.request.OpenerDirector: 2c3a.).  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套件取得網路資源

10.12.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"’.

e.g.

     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) http://www.voidspace.org.uk/python/articles/authentication.shtml


File: python.info,  Node: Proxies,  Next: Sockets and Layers,  Prev: Basic Authentication,  Up: 如何使用urllib套件取得網路資源

10.12.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(): 2c47.

   ---------- Footnotes ----------

   (1) (5) 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) http://www.voidspace.org.uk/python/articles/authentication.shtml

   (3) (6) urllib opener for SSL proxy (CONNECT method): ASPN Cookbook
Recipe (https://code.activestate.com/recipes/456195/).


File: python.info,  Node: Sockets and Layers,  Next: 註解<3>,  Prev: Proxies,  Up: 如何使用urllib套件取得網路資源

10.12.8 Sockets and Layers
--------------------------

The Python support for fetching resources from the web is layered.
urllib uses the *note http.client: 94. 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: 註解<3>,  Prev: Sockets and Layers,  Up: 如何使用urllib套件取得網路資源

10.12.9 註解
------------

This document was reviewed and revised by John Lee.


File: python.info,  Node: Argparse 教學,  Next: ipaddress模組介紹,  Prev: 如何使用urllib套件取得網路資源,  Up: Python HOWTOs

10.13 Argparse 教學
===================


author: Tshepang Lekhonkhobe

這個教學傾向簡介 Python 官方標準含式庫中推薦的命令列解析模組 *note
argparse: 6.。

     備註: 另外兩個具有同樣功能的模組 *note getopt: 87. （一個相等於 C 語
     言中的 ‘getopt()’）以及被棄用的 *note optparse: c4.。而 *note
     argparse: 6. 也是根據 *note optparse: c4. 為基礎發展而來，因此有非
     常近似的使用方式。

* Menu:

* 概念::
* 基本用法::
* 介紹位置參數::
* 介紹選項參數::
* 現在結合位置與選項參數::
* Getting a little more advanced::
* 結論::


File: python.info,  Node: 概念,  Next: 基本用法,  Up: Argparse 教學

10.13.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’ 這個參數。

   * 這是 help 文件的片段。對於以前從未使用過的程序來說非常有用，可以透
     過這些 help 文件來了解這些該怎麼使用。


File: python.info,  Node: 基本用法,  Next: 介紹位置參數,  Prev: 概念,  Up: Argparse 教學

10.13.2 基本用法
----------------

我們以一個很簡單的例子開始下面的介紹：

     import argparse
     parser = argparse.ArgumentParser()
     parser.parse_args()

下面是運行這些代碼的結果：

     $ python3 prog.py
     $ python3 prog.py --help
     usage: prog.py [-h]

     optional arguments:
       -h, --help  show this help message and exit
     $ python3 prog.py --verbose
     usage: prog.py [-h]
     prog.py: error: unrecognized arguments: --verbose
     $ python3 prog.py foo
     usage: prog.py [-h]
     prog.py: error: unrecognized arguments: foo

接者是發生的情況：

   * 運行這個腳本而沒有給與任何參數時就不會顯示任何東西至標準輸出畫面上
     。這裡並不是這麼的有用。

   * 第二個我們呈現出了 *note argparse: 6. 模組的用處。我們幾乎沒有做什
     麼事情，但已經得到一個很好的幫助信息。

   * 這個 ‘--help’ 選項可以簡短的表示成 ‘-h’ , 這是唯一一個選項我們不用
     去指明的（意即，沒有必要在這個參數後加上任何數值）。如果指定其他參
     數給他會造成錯誤。也因為這樣，我們得到了一個免費的信息。


File: python.info,  Node: 介紹位置參數,  Next: 介紹選項參數,  Prev: 基本用法,  Up: Argparse 教學

10.13.3 介紹位置參數
--------------------

例子：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("echo")
     args = parser.parse_args()
     print(args.echo)

運行這段代碼：

     $ python3 prog.py
     usage: prog.py [-h] echo
     prog.py: error: the following arguments are required: echo
     $ python3 prog.py --help
     usage: prog.py [-h] echo

     positional arguments:
       echo

     optional arguments:
       -h, --help  show this help message and exit
     $ python3 prog.py foo
     foo

接者是發生的情況：

   * 我們增加了 ‘add_argument()’ ，利用這個方法可以指名讓我們的程式接受
     哪些命令列參數。

   * 現在呼叫我們的程序時需要指定一個參數選項。

   * 在這個例子中， ‘parse_args()’ 這個方法確實根據了 ‘echo’ 這個選項回
     傳了資料。

   * The variable is some form of ’magic’ that *note argparse: 6.
     performs for free (i.e.  no need to specify which variable that
     value is stored in).  You will also notice that its name matches
     the string argument given to the method, ‘echo’.

注意, 雖然 help 秀出了看起來不錯的信息, 但現在並沒有給予到實質幫助。像剛
剛增加的 ‘echo’ 這個位置參數，除了猜測和讀原始碼之外，我們根本不曉得該怎
麼使用他。因此我們來做一點事讓他變得更有用：

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("echo", help="echo the string you use here")
     args = parser.parse_args()
     print(args.echo)

然後我們得到：

     $ python3 prog.py -h
     usage: prog.py [-h] echo

     positional arguments:
       echo        echo the string you use here

     optional arguments:
       -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)

下面是運行這些代碼的結果：

     $ python3 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: 6. 將我們給予選項的值當成字
串，除然我們告訴他要怎麼做。所以我們來告訴 *note argparse: 6. 將這個輸入
值當成整數來使用：

     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)

下面是運行這些代碼的結果：

     $ python3 prog.py 4
     16
     $ python3 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 教學

10.13.4 介紹選項參數
--------------------

So far we have been playing with positional arguments.  Let us have a
look on how to add optional ones:

     import argparse
     parser = argparse.ArgumentParser()
     parser.add_argument("--verbosity", help="increase output verbosity")
     args = parser.parse_args()
     if args.verbosity:
         print("verbosity turned on")

接者是結果：

     $ python3 prog.py --verbosity 1
     verbosity turned on
     $ python3 prog.py
     $ python3 prog.py --help
     usage: prog.py [-h] [--verbosity VERBOSITY]

     optional arguments:
       -h, --help            show this help message and exit
       --verbosity VERBOSITY
                             increase output verbosity
     $ python3 prog.py --verbosity
     usage: prog.py [-h] [--verbosity VERBOSITY]
     prog.py: error: argument --verbosity: expected one argument

接者是發生的情況：

   * 這個程式是寫成如果有指名 ‘--verbosity’ 這個參數選項那才顯示些資訊，
     反之亦然。

   * To show that the option is actually optional, there is no error
     when running the program without it.  Note that by default, if an
     optional argument isn’t used, the relevant variable, in this case
     ‘args.verbosity’, is given ‘None’ as a value, which is the reason
     it fails the truth test of the *note if: dec. statement.

   * Help 訊息稍微有些不一樣。

   * 當使用 ‘--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")

接者是結果：

     $ python3 prog.py --verbose
     verbosity turned on
     $ python3 prog.py --verbose 1
     usage: prog.py [-h] [--verbose]
     prog.py: error: unrecognized arguments: 1
     $ python3 prog.py --help
     usage: prog.py [-h] [--verbose]

     optional arguments:
       -h, --help  show this help message and exit
       --verbose   increase output verbosity

接者是發生的情況：

   * The option is now more of a flag than something that requires a
     value.  We even changed the name of the option to match that idea.
     Note that we now specify a new keyword, ‘action’, and give it the
     value ‘"store_true"’.  This means that, if the option is specified,
     assign the value ‘True’ to ‘args.verbose’.  Not specifying it
     implies ‘False’.

   * It complains when you specify a value, in true spirit of what flags
     actually are.

   * 注意不同的 help 文件。

* Menu:

* Short options::


File: python.info,  Node: Short options,  Up: 介紹選項參數

10.13.4.1 Short options
.......................

如果你很熟悉命令列的使用的話，你將會發現我還沒講到關於短參數。其實這很簡
單：

     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")

And here goes:

     $ python3 prog.py -v
     verbosity turned on
     $ python3 prog.py --help
     usage: prog.py [-h] [-v]

     optional arguments:
       -h, --help     show this help message and exit
       -v, --verbose  increase output verbosity

注意新的表示對於幫助文件也是一樣的


File: python.info,  Node: 現在結合位置與選項參數,  Next: Getting a little more advanced,  Prev: 介紹選項參數,  Up: Argparse 教學

10.13.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("the square of {} equals {}".format(args.square, answer))
     else:
         print(answer)

然後現在的輸出結果：

     $ python3 prog.py
     usage: prog.py [-h] [-v] square
     prog.py: error: the following arguments are required: square
     $ python3 prog.py 4
     16
     $ python3 prog.py 4 --verbose
     the square of 4 equals 16
     $ python3 prog.py --verbose 4
     the square of 4 equals 16

   * We’ve brought back a positional argument, hence the complaint.

   * 注意現在的順序對於程式來說已經不再重要了.

How about we give this program of ours back the ability to have multiple
verbosity values, and actually get to use them:

     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("the square of {} equals {}".format(args.square, answer))
     elif args.verbosity == 1:
         print("{}^2 == {}".format(args.square, answer))
     else:
         print(answer)

接者是結果：

     $ python3 prog.py 4
     16
     $ python3 prog.py 4 -v
     usage: prog.py [-h] [-v VERBOSITY] square
     prog.py: error: argument -v/--verbosity: expected one argument
     $ python3 prog.py 4 -v 1
     4^2 == 16
     $ python3 prog.py 4 -v 2
     the square of 4 equals 16
     $ python3 prog.py 4 -v 3
     16

These all look good except the last one, which exposes a bug in our
program.  Let’s fix it by restricting the values the ‘--verbosity’
option can accept:

     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("the square of {} equals {}".format(args.square, answer))
     elif args.verbosity == 1:
         print("{}^2 == {}".format(args.square, answer))
     else:
         print(answer)

接者是結果：

     $ python3 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)
     $ python3 prog.py 4 -h
     usage: prog.py [-h] [-v {0,1,2}] square

     positional arguments:
       square                display a square of a given number

     optional arguments:
       -h, --help            show this help message and exit
       -v {0,1,2}, --verbosity {0,1,2}
                             increase output verbosity

Note that the change also reflects both in the error message as well as
the help string.

Now, let’s use a different approach of playing with verbosity, which is
pretty common.  It also matches the way the CPython executable handles
its own verbosity argument (check the output of ‘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("the square of {} equals {}".format(args.square, answer))
     elif args.verbosity == 1:
         print("{}^2 == {}".format(args.square, answer))
     else:
         print(answer)

我們已經介紹過另一個操作 "count" 用來計算指定的選項參數出現的次數。

     $ python3 prog.py 4
     16
     $ python3 prog.py 4 -v
     4^2 == 16
     $ python3 prog.py 4 -vv
     the square of 4 equals 16
     $ python3 prog.py 4 --verbosity --verbosity
     the square of 4 equals 16
     $ python3 prog.py 4 -v 1
     usage: prog.py [-h] [-v] square
     prog.py: error: unrecognized arguments: 1
     $ python3 prog.py 4 -h
     usage: prog.py [-h] [-v] square

     positional arguments:
       square           display a square of a given number

     optional arguments:
       -h, --help       show this help message and exit
       -v, --verbosity  increase output verbosity
     $ python3 prog.py 4 -vvv
     16

   * Yes, it’s now more of a flag (similar to ‘action="store_true"’) in
     the previous version of our script.  That should explain the
     complaint.

   * It also behaves similar to "store_true" action.

   * 現在來秀一下 "count" 這個動作會給予什麼。你可能之前就有見過這種用法
     。

   * And if you don’t specify the ‘-v’ flag, that flag is considered to
     have ‘None’ value.

   * 應該要如預期那樣，就算給予長選項我們也要獲得一樣的輸出結果。

   * Sadly, our help output isn’t very informative on the new ability
     our script has acquired, but that can always be fixed by improving
     the documentation for our script (e.g.  via the ‘help’ keyword
     argument).

   * That last output exposes a bug in our program.

讓我們來解決問題

     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("the square of {} equals {}".format(args.square, answer))
     elif args.verbosity >= 1:
         print("{}^2 == {}".format(args.square, answer))
     else:
         print(answer)

而這也正是它給的：

     $ python3 prog.py 4 -vvv
     the square of 4 equals 16
     $ python3 prog.py 4 -vvvv
     the square of 4 equals 16
     $ python3 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'

   * First output went well, and fixes the bug we had before.  That is,
     we want any value >= 2 to be as verbose as possible.

   * 第三個輸出不是這麼的好。

我們來修復這個錯誤：

     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("the square of {} equals {}".format(args.square, answer))
     elif args.verbosity >= 1:
         print("{}^2 == {}".format(args.square, answer))
     else:
         print(answer)

We’ve just introduced yet another keyword, ‘default’.  We’ve set it to
‘0’ in order to make it comparable to the other int values.  Remember
that by default, if an optional argument isn’t specified, it gets the
‘None’ value, and that cannot be compared to an int value (hence the
*note TypeError: 193. exception).

而且

     $ python3 prog.py 4
     16

You can go quite far just with what we’ve learned so far, and we have
only scratched the surface.  The *note argparse: 6. module is very
powerful, and we’ll explore a bit more of it before we end this
tutorial.


File: python.info,  Node: Getting a little more advanced,  Next: 結論,  Prev: 現在結合位置與選項參數,  Up: Argparse 教學

10.13.6 Getting a little more advanced
--------------------------------------

如果我們想要擴展我們的小程式做比範例更多的事：

     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("{} to the power {} equals {}".format(args.x, args.y, answer))
     elif args.verbosity >= 1:
         print("{}^{} == {}".format(args.x, args.y, answer))
     else:
         print(answer)

結果：

     $ python3 prog.py
     usage: prog.py [-h] [-v] x y
     prog.py: error: the following arguments are required: x, y
     $ python3 prog.py -h
     usage: prog.py [-h] [-v] x y

     positional arguments:
       x                the base
       y                the exponent

     optional arguments:
       -h, --help       show this help message and exit
       -v, --verbosity
     $ python3 prog.py 4 2 -v
     4^2 == 16

Notice that so far we’ve been using verbosity level to `change' the text
that gets displayed.  The following example instead uses verbosity level
to display `more' text instead:

     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("Running '{}'".format(__file__))
     if args.verbosity >= 1:
         print("{}^{} == ".format(args.x, args.y), end="")
     print(answer)

結果：

     $ python3 prog.py 4 2
     16
     $ python3 prog.py 4 2 -v
     4^2 == 16
     $ python3 prog.py 4 2 -vv
     Running 'prog.py'
     4^2 == 16

* Menu:

* Conflicting options::


File: python.info,  Node: Conflicting options,  Up: Getting a little more advanced

10.13.6.1 Conflicting options
.............................

So far, we have been working with two methods of an *note
argparse.ArgumentParser: 69a. instance.  Let’s introduce a third one,
‘add_mutually_exclusive_group()’.  It allows for us to specify options
that conflict with each other.  Let’s also change the rest of the
program so that the new functionality makes more sense: we’ll introduce
the ‘--quiet’ option, which will be the opposite of the ‘--verbose’ one:

     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("{} to the power {} equals {}".format(args.x, args.y, answer))
     else:
         print("{}^{} == {}".format(args.x, args.y, answer))

Our program is now simpler, and we’ve lost some functionality for the
sake of demonstration.  Anyways, here’s the output:

     $ python3 prog.py 4 2
     4^2 == 16
     $ python3 prog.py 4 2 -q
     16
     $ python3 prog.py 4 2 -v
     4 to the power 2 equals 16
     $ python3 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
     $ python3 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

That should be easy to follow.  I’ve added that last output so you can
see the sort of flexibility you get, i.e.  mixing long form options with
short form ones.

在我們結論之前，你可能想告訴你的用戶這個程式的主要目的，以防萬一他們不知
道：

     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("{} to the power {} equals {}".format(args.x, args.y, answer))
     else:
         print("{}^{} == {}".format(args.x, args.y, answer))

Note that slight difference in the usage text.  Note the ‘[-v | -q]’,
which tells us that we can either use ‘-v’ or ‘-q’, but not both at the
same time:

     $ python3 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

     optional arguments:
       -h, --help     show this help message and exit
       -v, --verbose
       -q, --quiet


File: python.info,  Node: 結論,  Prev: Getting a little more advanced,  Up: Argparse 教學

10.13.7 結論
------------

*note argparse: 6. 模組提供了比這裡展示更多的功能。它的文件是非常全面詳
細且充滿了例子。通過本教學，你應該比較容易消化它們了。


File: python.info,  Node: ipaddress模組介紹,  Next: Argument Clinic How-To,  Prev: Argparse 教學,  Up: Python HOWTOs

10.14 ipaddress模組介紹
=======================


author: Peter Moody


author: Nick Coghlan

Overview
........

This document aims to provide a gentle introduction to the *note
ipaddress: a3. module.  It is aimed primarily at users that aren’t
already familiar with IP networking terminology, but may also be useful
to network engineers wanting an overview of how *note ipaddress: a3.
represents IP network addressing concepts.

* Menu:

* Creating Address/Network/Interface objects::
* Inspecting Address/Network/Interface Objects::
* Networks as lists of Addresses::
* Comparisons: Comparisons<4>.
* 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模組介紹

10.14.1 Creating Address/Network/Interface objects
--------------------------------------------------

Since *note ipaddress: a3. 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: a3. to create objects from strings and
integers.

* Menu:

* A Note on IP Versions::
* IP Host Addresses::
* Defining Networks::
* Host Interfaces::


File: python.info,  Node: A Note on IP Versions,  Next: IP Host Addresses,  Up: Creating Address/Network/Interface objects

10.14.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 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: Defining Networks,  Prev: A Note on IP Versions,  Up: Creating Address/Network/Interface objects

10.14.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(): 2f0b. 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: Defining Networks,  Next: Host Interfaces,  Prev: IP Host Addresses,  Up: Creating Address/Network/Interface objects

10.14.1.3 Defining Networks
...........................

Host addresses are usually grouped together into IP networks, so *note
ipaddress: a3. 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: 1fc. 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: Defining Networks,  Up: Creating Address/Network/Interface objects

10.14.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: a3. 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模組介紹

10.14.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: a3. 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<4>,  Prev: Inspecting Address/Network/Interface Objects,  Up: ipaddress模組介紹

10.14.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<4>,  Next: Using IP Addresses with other modules,  Prev: Networks as lists of Addresses,  Up: ipaddress模組介紹

10.14.4 Comparisons
-------------------

*note ipaddress: a3. 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: 193. 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<4>,  Up: ipaddress模組介紹

10.14.5 Using IP Addresses with other modules
---------------------------------------------

Other modules that use IP addresses (such as *note socket: f0.) 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模組介紹

10.14.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: 1fc. 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: 1fc. subclasses *note ipaddress.AddressValueError:
2f14. and *note ipaddress.NetmaskValueError: 2f39. 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:
1fc. 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: Argument Clinic How-To,  Next: Instrumenting CPython with DTrace and SystemTap,  Prev: ipaddress模組介紹,  Up: Python HOWTOs

10.15 Argument Clinic How-To
============================


author: Larry Hastings

Abstract
........

Argument Clinic is a preprocessor for CPython C files.  Its purpose is
to automate all the boilerplate involved with writing argument parsing
code for "builtins".  This document shows you how to convert your first
C function to work with Argument Clinic, and then introduces some
advanced topics on Argument Clinic usage.

Currently Argument Clinic is considered internal-only for CPython.  Its
use is not supported for files outside CPython, and no guarantees are
made regarding backwards compatibility for future versions.  In other
words: if you maintain an external C extension for CPython, you’re
welcome to experiment with Argument Clinic in your own code.  But the
version of Argument Clinic that ships with the next version of CPython
`could' be totally incompatible and break all your code.

* Menu:

* The Goals Of Argument Clinic::
* Basic Concepts And Usage::
* Converting Your First Function::
* Advanced Topics::


File: python.info,  Node: The Goals Of Argument Clinic,  Next: Basic Concepts And Usage,  Up: Argument Clinic How-To

10.15.1 The Goals Of Argument Clinic
------------------------------------

Argument Clinic’s primary goal is to take over responsibility for all
argument parsing code inside CPython.  This means that, when you convert
a function to work with Argument Clinic, that function should no longer
do any of its own argument parsing—the code generated by Argument Clinic
should be a "black box" to you, where CPython calls in at the top, and
your code gets called at the bottom, with ‘PyObject *args’ (and maybe
‘PyObject *kwargs’) magically converted into the C variables and types
you need.

In order for Argument Clinic to accomplish its primary goal, it must be
easy to use.  Currently, working with CPython’s argument parsing library
is a chore, requiring maintaining redundant information in a surprising
number of places.  When you use Argument Clinic, you don’t have to
repeat yourself.

Obviously, no one would want to use Argument Clinic unless it’s solving
their problem—and without creating new problems of its own.  So it’s
paramount that Argument Clinic generate correct code.  It’d be nice if
the code was faster, too, but at the very least it should not introduce
a major speed regression.  (Eventually Argument Clinic `should' make a
major speedup possible—we could rewrite its code generator to produce
tailor-made argument parsing code, rather than calling the
general-purpose CPython argument parsing library.  That would make for
the fastest argument parsing possible!)

Additionally, Argument Clinic must be flexible enough to work with any
approach to argument parsing.  Python has some functions with some very
strange parsing behaviors; Argument Clinic’s goal is to support all of
them.

Finally, the original motivation for Argument Clinic was to provide
introspection "signatures" for CPython builtins.  It used to be, the
introspection query functions would throw an exception if you passed in
a builtin.  With Argument Clinic, that’s a thing of the past!

One idea you should keep in mind, as you work with Argument Clinic: the
more information you give it, the better job it’ll be able to do.
Argument Clinic is admittedly relatively simple right now.  But as it
evolves it will get more sophisticated, and it should be able to do many
interesting and smart things with all the information you give it.


File: python.info,  Node: Basic Concepts And Usage,  Next: Converting Your First Function,  Prev: The Goals Of Argument Clinic,  Up: Argument Clinic How-To

10.15.2 Basic Concepts And Usage
--------------------------------

Argument Clinic ships with CPython; you’ll find it in
‘Tools/clinic/clinic.py’.  If you run that script, specifying a C file
as an argument:

     $ python3 Tools/clinic/clinic.py foo.c

Argument Clinic will scan over the file looking for lines that look
exactly like this:

     /*[clinic input]

When it finds one, it reads everything up to a line that looks exactly
like this:

     [clinic start generated code]*/

Everything in between these two lines is input for Argument Clinic.  All
of these lines, including the beginning and ending comment lines, are
collectively called an Argument Clinic "block".

When Argument Clinic parses one of these blocks, it generates output.
This output is rewritten into the C file immediately after the block,
followed by a comment containing a checksum.  The Argument Clinic block
now looks like this:

     /*[clinic input]
     ... clinic input goes here ...
     [clinic start generated code]*/
     ... clinic output goes here ...
     /*[clinic end generated code: checksum=...]*/

If you run Argument Clinic on the same file a second time, Argument
Clinic will discard the old output and write out the new output with a
fresh checksum line.  However, if the input hasn’t changed, the output
won’t change either.

You should never modify the output portion of an Argument Clinic block.
Instead, change the input until it produces the output you want.
(That’s the purpose of the checksum—to detect if someone changed the
output, as these edits would be lost the next time Argument Clinic
writes out fresh output.)

For the sake of clarity, here’s the terminology we’ll use with Argument
Clinic:

   * The first line of the comment (‘/*[clinic input]’) is the `start
     line'.

   * The last line of the initial comment (‘[clinic start generated
     code]*/’) is the `end line'.

   * The last line (‘/*[clinic end generated code: checksum=...]*/’) is
     the `checksum line'.

   * In between the start line and the end line is the `input'.

   * In between the end line and the checksum line is the `output'.

   * All the text collectively, from the start line to the checksum line
     inclusively, is the `block'.  (A block that hasn’t been
     successfully processed by Argument Clinic yet doesn’t have output
     or a checksum line, but it’s still considered a block.)


File: python.info,  Node: Converting Your First Function,  Next: Advanced Topics,  Prev: Basic Concepts And Usage,  Up: Argument Clinic How-To

10.15.3 Converting Your First Function
--------------------------------------

The best way to get a sense of how Argument Clinic works is to convert a
function to work with it.  Here, then, are the bare minimum steps you’d
need to follow to convert a function to work with Argument Clinic.  Note
that for code you plan to check in to CPython, you really should take
the conversion farther, using some of the advanced concepts you’ll see
later on in the document (like "return converters" and "self
converters").  But we’ll keep it simple for this walkthrough so you can
learn.

Let’s dive in!

  0. Make sure you’re working with a freshly updated checkout of the
     CPython trunk.

  1. Find a Python builtin that calls either *note PyArg_ParseTuple():
     26b. or *note PyArg_ParseTupleAndKeywords(): 5cf, and hasn’t been
     converted to work with Argument Clinic yet.  For my example I’m
     using ‘_pickle.Pickler.dump()’.

  2. If the call to the ‘PyArg_Parse’ function uses any of the following
     format units:

          O&
          O!
          es
          es#
          et
          et#

     or if it has multiple calls to *note PyArg_ParseTuple(): 26b, you
     should choose a different function.  Argument Clinic `does' support
     all of these scenarios.  But these are advanced topics—let’s do
     something simpler for your first function.

     Also, if the function has multiple calls to *note
     PyArg_ParseTuple(): 26b. or *note PyArg_ParseTupleAndKeywords():
     5cf. where it supports different types for the same argument, or if
     the function uses something besides PyArg_Parse functions to parse
     its arguments, it probably isn’t suitable for conversion to
     Argument Clinic.  Argument Clinic doesn’t support generic functions
     or polymorphic parameters.

  3. Add the following boilerplate above the function, creating our
     block:

          /*[clinic input]
          [clinic start generated code]*/

  4. Cut the docstring and paste it in between the ‘[clinic]’ lines,
     removing all the junk that makes it a properly quoted C string.
     When you’re done you should have just the text, based at the left
     margin, with no line wider than 80 characters.  (Argument Clinic
     will preserve indents inside the docstring.)

     If the old docstring had a first line that looked like a function
     signature, throw that line away.  (The docstring doesn’t need it
     anymore—when you use ‘help()’ on your builtin in the future, the
     first line will be built automatically based on the function’s
     signature.)

     Sample:

          /*[clinic input]
          Write a pickled representation of obj to the open file.
          [clinic start generated code]*/

  5. If your docstring doesn’t have a "summary" line, Argument Clinic
     will complain.  So let’s make sure it has one.  The "summary" line
     should be a paragraph consisting of a single 80-column line at the
     beginning of the docstring.

     (Our example docstring consists solely of a summary line, so the
     sample code doesn’t have to change for this step.)

  6. Above the docstring, enter the name of the function, followed by a
     blank line.  This should be the Python name of the function, and
     should be the full dotted path to the function—it should start with
     the name of the module, include any sub-modules, and if the
     function is a method on a class it should include the class name
     too.

     Sample:

          /*[clinic input]
          _pickle.Pickler.dump

          Write a pickled representation of obj to the open file.
          [clinic start generated code]*/

  7. If this is the first time that module or class has been used with
     Argument Clinic in this C file, you must declare the module and/or
     class.  Proper Argument Clinic hygiene prefers declaring these in a
     separate block somewhere near the top of the C file, in the same
     way that include files and statics go at the top.  (In our sample
     code we’ll just show the two blocks next to each other.)

     The name of the class and module should be the same as the one seen
     by Python.  Check the name defined in the *note PyModuleDef: 3b42.
     or *note PyTypeObject: 2d7. as appropriate.

     When you declare a class, you must also specify two aspects of its
     type in C: the type declaration you’d use for a pointer to an
     instance of this class, and a pointer to the *note PyTypeObject:
     2d7. for this class.

     Sample:

          /*[clinic input]
          module _pickle
          class _pickle.Pickler "PicklerObject *" "&Pickler_Type"
          [clinic start generated code]*/

          /*[clinic input]
          _pickle.Pickler.dump

          Write a pickled representation of obj to the open file.
          [clinic start generated code]*/

  8. Declare each of the parameters to the function.  Each parameter
     should get its own line.  All the parameter lines should be
     indented from the function name and the docstring.

     The general form of these parameter lines is as follows:

          name_of_parameter: converter

     If the parameter has a default value, add that after the converter:

          name_of_parameter: converter = default_value

     Argument Clinic’s support for "default values" is quite
     sophisticated; please see *note the section below on default
     values: 4201. for more information.

     Add a blank line below the parameters.

     What’s a "converter"?  It establishes both the type of the variable
     used in C, and the method to convert the Python value into a C
     value at runtime.  For now you’re going to use what’s called a
     "legacy converter"—a convenience syntax intended to make porting
     old code into Argument Clinic easier.

     For each parameter, copy the "format unit" for that parameter from
     the ‘PyArg_Parse()’ format argument and specify `that' as its
     converter, as a quoted string.  ("format unit" is the formal name
     for the one-to-three character substring of the ‘format’ parameter
     that tells the argument parsing function what the type of the
     variable is and how to convert it.  For more on format units please
     see *note Parsing arguments and building values: 2d1.)

     For multicharacter format units like ‘z#’, use the entire
     two-or-three character string.

     Sample:

           /*[clinic input]
           module _pickle
           class _pickle.Pickler "PicklerObject *" "&Pickler_Type"
           [clinic start generated code]*/

           /*[clinic input]
           _pickle.Pickler.dump

              obj: 'O'

          Write a pickled representation of obj to the open file.
          [clinic start generated code]*/

  9. If your function has ‘|’ in the format string, meaning some
     parameters have default values, you can ignore it.  Argument Clinic
     infers which parameters are optional based on whether or not they
     have default values.

     If your function has ‘$’ in the format string, meaning it takes
     keyword-only arguments, specify ‘*’ on a line by itself before the
     first keyword-only argument, indented the same as the parameter
     lines.

     (‘_pickle.Pickler.dump’ has neither, so our sample is unchanged.)

  10. If the existing C function calls *note PyArg_ParseTuple(): 26b.
     (as opposed to *note PyArg_ParseTupleAndKeywords(): 5cf.), then all
     its arguments are positional-only.

     To mark all parameters as positional-only in Argument Clinic, add a
     ‘/’ on a line by itself after the last parameter, indented the same
     as the parameter lines.

     Currently this is all-or-nothing; either all parameters are
     positional-only, or none of them are.  (In the future Argument
     Clinic may relax this restriction.)

     Sample:

          /*[clinic input]
          module _pickle
          class _pickle.Pickler "PicklerObject *" "&Pickler_Type"
          [clinic start generated code]*/

          /*[clinic input]
          _pickle.Pickler.dump

              obj: 'O'
              /

          Write a pickled representation of obj to the open file.
          [clinic start generated code]*/

  11. It’s helpful to write a per-parameter docstring for each
     parameter.  But per-parameter docstrings are optional; you can skip
     this step if you prefer.

     Here’s how to add a per-parameter docstring.  The first line of the
     per-parameter docstring must be indented further than the parameter
     definition.  The left margin of this first line establishes the
     left margin for the whole per-parameter docstring; all the text you
     write will be outdented by this amount.  You can write as much text
     as you like, across multiple lines if you wish.

     Sample:

          /*[clinic input]
          module _pickle
          class _pickle.Pickler "PicklerObject *" "&Pickler_Type"
          [clinic start generated code]*/

          /*[clinic input]
          _pickle.Pickler.dump

              obj: 'O'
                  The object to be pickled.
              /

          Write a pickled representation of obj to the open file.
          [clinic start generated code]*/

  12. Save and close the file, then run ‘Tools/clinic/clinic.py’ on it.
     With luck everything worked—your block now has output, and a ‘.c.h’
     file has been generated!  Reopen the file in your text editor to
     see:

          /*[clinic input]
          _pickle.Pickler.dump

              obj: 'O'
                  The object to be pickled.
              /

          Write a pickled representation of obj to the open file.
          [clinic start generated code]*/

          static PyObject *
          _pickle_Pickler_dump(PicklerObject *self, PyObject *obj)
          /*[clinic end generated code: output=87ecad1261e02ac7 input=552eb1c0f52260d9]*/

     Obviously, if Argument Clinic didn’t produce any output, it’s
     because it found an error in your input.  Keep fixing your errors
     and retrying until Argument Clinic processes your file without
     complaint.

     For readability, most of the glue code has been generated to a
     ‘.c.h’ file.  You’ll need to include that in your original ‘.c’
     file, typically right after the clinic module block:

          #include "clinic/_pickle.c.h"

  13. Double-check that the argument-parsing code Argument Clinic
     generated looks basically the same as the existing code.

     First, ensure both places use the same argument-parsing function.
     The existing code must call either *note PyArg_ParseTuple(): 26b.
     or *note PyArg_ParseTupleAndKeywords(): 5cf.; ensure that the code
     generated by Argument Clinic calls the `exact' same function.

     Second, the format string passed in to *note PyArg_ParseTuple():
     26b. or *note PyArg_ParseTupleAndKeywords(): 5cf. should be
     `exactly' the same as the hand-written one in the existing
     function, up to the colon or semi-colon.

     (Argument Clinic always generates its format strings with a ‘:’
     followed by the name of the function.  If the existing code’s
     format string ends with ‘;’, to provide usage help, this change is
     harmless—don’t worry about it.)

     Third, for parameters whose format units require two arguments
     (like a length variable, or an encoding string, or a pointer to a
     conversion function), ensure that the second argument is `exactly'
     the same between the two invocations.

     Fourth, inside the output portion of the block you’ll find a
     preprocessor macro defining the appropriate static *note
     PyMethodDef: e20. structure for this builtin:

          #define __PICKLE_PICKLER_DUMP_METHODDEF    \
          {"dump", (PyCFunction)__pickle_Pickler_dump, METH_O, __pickle_Pickler_dump__doc__},

     This static structure should be `exactly' the same as the existing
     static *note PyMethodDef: e20. structure for this builtin.

     If any of these items differ in `any way', adjust your Argument
     Clinic function specification and rerun ‘Tools/clinic/clinic.py’
     until they `are' the same.

  14. Notice that the last line of its output is the declaration of your
     "impl" function.  This is where the builtin’s implementation goes.
     Delete the existing prototype of the function you’re modifying, but
     leave the opening curly brace.  Now delete its argument parsing
     code and the declarations of all the variables it dumps the
     arguments into.  Notice how the Python arguments are now arguments
     to this impl function; if the implementation used different names
     for these variables, fix it.

     Let’s reiterate, just because it’s kind of weird.  Your code should
     now look like this:

          static return_type
          your_function_impl(...)
          /*[clinic end generated code: checksum=...]*/
          {
          ...

     Argument Clinic generated the checksum line and the function
     prototype just above it.  You should write the opening (and
     closing) curly braces for the function, and the implementation
     inside.

     Sample:

          /*[clinic input]
          module _pickle
          class _pickle.Pickler "PicklerObject *" "&Pickler_Type"
          [clinic start generated code]*/
          /*[clinic end generated code: checksum=da39a3ee5e6b4b0d3255bfef95601890afd80709]*/

          /*[clinic input]
          _pickle.Pickler.dump

              obj: 'O'
                  The object to be pickled.
              /

          Write a pickled representation of obj to the open file.
          [clinic start generated code]*/

          PyDoc_STRVAR(__pickle_Pickler_dump__doc__,
          "Write a pickled representation of obj to the open file.\n"
          "\n"
          ...
          static PyObject *
          _pickle_Pickler_dump_impl(PicklerObject *self, PyObject *obj)
          /*[clinic end generated code: checksum=3bd30745bf206a48f8b576a1da3d90f55a0a4187]*/
          {
              /* Check whether the Pickler was initialized correctly (issue3664).
                 Developers often forget to call __init__() in their subclasses, which
                 would trigger a segfault without this check. */
              if (self->write == NULL) {
                  PyErr_Format(PicklingError,
                               "Pickler.__init__() was not called by %s.__init__()",
                               Py_TYPE(self)->tp_name);
                  return NULL;
              }

              if (_Pickler_ClearBuffer(self) < 0)
                  return NULL;

              ...

  15. Remember the macro with the *note PyMethodDef: e20. structure for
     this function?  Find the existing *note PyMethodDef: e20. structure
     for this function and replace it with a reference to the macro.
     (If the builtin is at module scope, this will probably be very near
     the end of the file; if the builtin is a class method, this will
     probably be below but relatively near to the implementation.)

     Note that the body of the macro contains a trailing comma.  So when
     you replace the existing static *note PyMethodDef: e20. structure
     with the macro, `don’t' add a comma to the end.

     Sample:

          static struct PyMethodDef Pickler_methods[] = {
              __PICKLE_PICKLER_DUMP_METHODDEF
              __PICKLE_PICKLER_CLEAR_MEMO_METHODDEF
              {NULL, NULL}                /* sentinel */
          };

  16. Compile, then run the relevant portions of the regression-test
     suite.  This change should not introduce any new compile-time
     warnings or errors, and there should be no externally-visible
     change to Python’s behavior.

     Well, except for one difference: ‘inspect.signature()’ run on your
     function should now provide a valid signature!

     Congratulations, you’ve ported your first function to work with
     Argument Clinic!


File: python.info,  Node: Advanced Topics,  Prev: Converting Your First Function,  Up: Argument Clinic How-To

10.15.4 Advanced Topics
-----------------------

Now that you’ve had some experience working with Argument Clinic, it’s
time for some advanced topics.

* Menu:

* Symbolic default values::
* Renaming the C functions and variables generated by Argument Clinic::
* Converting functions using PyArg_UnpackTuple::
* Optional Groups::
* Using real Argument Clinic converters, instead of "legacy converters": Using real Argument Clinic converters instead of "legacy converters".
* Py_buffer::
* Advanced converters::
* Parameter default values::
* The NULL default value::
* Expressions specified as default values::
* Using a return converter::
* Cloning existing functions::
* Calling Python code::
* Using a "self converter"::
* Writing a custom converter::
* Writing a custom return converter::
* METH_O and METH_NOARGS::
* tp_new and tp_init functions::
* Changing and redirecting Clinic's output::
* The #ifdef trick::
* Using Argument Clinic in Python files::


File: python.info,  Node: Symbolic default values,  Next: Renaming the C functions and variables generated by Argument Clinic,  Up: Advanced Topics

10.15.4.1 Symbolic default values
.................................

The default value you provide for a parameter can’t be any arbitrary
expression.  Currently the following are explicitly supported:

   * Numeric constants (integer and float)

   * String constants

   * ‘True’, ‘False’, and ‘None’

   * Simple symbolic constants like ‘sys.maxsize’, which must start with
     the name of the module

In case you’re curious, this is implemented in ‘from_builtin()’ in
‘Lib/inspect.py’.

(In the future, this may need to get even more elaborate, to allow full
expressions like ‘CONSTANT - 1’.)


File: python.info,  Node: Renaming the C functions and variables generated by Argument Clinic,  Next: Converting functions using PyArg_UnpackTuple,  Prev: Symbolic default values,  Up: Advanced Topics

10.15.4.2 Renaming the C functions and variables generated by Argument Clinic
.............................................................................

Argument Clinic automatically names the functions it generates for you.
Occasionally this may cause a problem, if the generated name collides
with the name of an existing C function.  There’s an easy solution:
override the names used for the C functions.  Just add the keyword
‘"as"’ to your function declaration line, followed by the function name
you wish to use.  Argument Clinic will use that function name for the
base (generated) function, then add ‘"_impl"’ to the end and use that
for the name of the impl function.

For example, if we wanted to rename the C function names generated for
‘pickle.Pickler.dump’, it’d look like this:

     /*[clinic input]
     pickle.Pickler.dump as pickler_dumper

     ...

The base function would now be named ‘pickler_dumper()’, and the impl
function would now be named ‘pickler_dumper_impl()’.

Similarly, you may have a problem where you want to give a parameter a
specific Python name, but that name may be inconvenient in C. Argument
Clinic allows you to give a parameter different names in Python and in
C, using the same ‘"as"’ syntax:

     /*[clinic input]
     pickle.Pickler.dump

         obj: object
         file as file_obj: object
         protocol: object = NULL
         *
         fix_imports: bool = True

Here, the name used in Python (in the signature and the ‘keywords’
array) would be ‘file’, but the C variable would be named ‘file_obj’.

You can use this to rename the ‘self’ parameter too!


File: python.info,  Node: Converting functions using PyArg_UnpackTuple,  Next: Optional Groups,  Prev: Renaming the C functions and variables generated by Argument Clinic,  Up: Advanced Topics

10.15.4.3 Converting functions using PyArg_UnpackTuple
......................................................

To convert a function parsing its arguments with *note
PyArg_UnpackTuple(): e4b, simply write out all the arguments, specifying
each as an ‘object’.  You may specify the ‘type’ argument to cast the
type as appropriate.  All arguments should be marked positional-only
(add a ‘/’ on a line by itself after the last argument).

Currently the generated code will use *note PyArg_ParseTuple(): 26b, but
this will change soon.


File: python.info,  Node: Optional Groups,  Next: Using real Argument Clinic converters instead of "legacy converters",  Prev: Converting functions using PyArg_UnpackTuple,  Up: Advanced Topics

10.15.4.4 Optional Groups
.........................

Some legacy functions have a tricky approach to parsing their arguments:
they count the number of positional arguments, then use a ‘switch’
statement to call one of several different *note PyArg_ParseTuple():
26b. calls depending on how many positional arguments there are.  (These
functions cannot accept keyword-only arguments.)  This approach was used
to simulate optional arguments back before *note
PyArg_ParseTupleAndKeywords(): 5cf. was created.

While functions using this approach can often be converted to use *note
PyArg_ParseTupleAndKeywords(): 5cf, optional arguments, and default
values, it’s not always possible.  Some of these legacy functions have
behaviors *note PyArg_ParseTupleAndKeywords(): 5cf. doesn’t directly
support.  The most obvious example is the builtin function ‘range()’,
which has an optional argument on the `left' side of its required
argument!  Another example is ‘curses.window.addch()’, which has a group
of two arguments that must always be specified together.  (The arguments
are called ‘x’ and ‘y’; if you call the function passing in ‘x’, you
must also pass in ‘y’—and if you don’t pass in ‘x’ you may not pass in
‘y’ either.)

In any case, the goal of Argument Clinic is to support argument parsing
for all existing CPython builtins without changing their semantics.
Therefore Argument Clinic supports this alternate approach to parsing,
using what are called `optional groups'.  Optional groups are groups of
arguments that must all be passed in together.  They can be to the left
or the right of the required arguments.  They can `only' be used with
positional-only parameters.

     備註: Optional groups are `only' intended for use when converting
     functions that make multiple calls to *note PyArg_ParseTuple():
     26b.!  Functions that use `any' other approach for parsing
     arguments should `almost never' be converted to Argument Clinic
     using optional groups.  Functions using optional groups currently
     cannot have accurate signatures in Python, because Python just
     doesn’t understand the concept.  Please avoid using optional groups
     wherever possible.

To specify an optional group, add a ‘[’ on a line by itself before the
parameters you wish to group together, and a ‘]’ on a line by itself
after these parameters.  As an example, here’s how ‘curses.window.addch’
uses optional groups to make the first two parameters and the last
parameter optional:

     /*[clinic input]

     curses.window.addch

         [
         x: int
           X-coordinate.
         y: int
           Y-coordinate.
         ]

         ch: object
           Character to add.

         [
         attr: long
           Attributes for the character.
         ]
         /

     ...

註解：

   * For every optional group, one additional parameter will be passed
     into the impl function representing the group.  The parameter will
     be an int named ‘group_{direction}_{number}’, where ‘{direction}’
     is either ‘right’ or ‘left’ depending on whether the group is
     before or after the required parameters, and ‘{number}’ is a
     monotonically increasing number (starting at 1) indicating how far
     away the group is from the required parameters.  When the impl is
     called, this parameter will be set to zero if this group was
     unused, and set to non-zero if this group was used.  (By used or
     unused, I mean whether or not the parameters received arguments in
     this invocation.)

   * If there are no required arguments, the optional groups will behave
     as if they’re to the right of the required arguments.

   * In the case of ambiguity, the argument parsing code favors
     parameters on the left (before the required parameters).

   * Optional groups can only contain positional-only parameters.

   * Optional groups are `only' intended for legacy code.  Please do not
     use optional groups for new code.


File: python.info,  Node: Using real Argument Clinic converters instead of "legacy converters",  Next: Py_buffer,  Prev: Optional Groups,  Up: Advanced Topics

10.15.4.5 Using real Argument Clinic converters, instead of "legacy converters"
...............................................................................

To save time, and to minimize how much you need to learn to achieve your
first port to Argument Clinic, the walkthrough above tells you to use
"legacy converters".  "Legacy converters" are a convenience, designed
explicitly to make porting existing code to Argument Clinic easier.  And
to be clear, their use is acceptable when porting code for Python 3.4.

However, in the long term we probably want all our blocks to use
Argument Clinic’s real syntax for converters.  Why?  A couple reasons:

   * The proper converters are far easier to read and clearer in their
     intent.

   * There are some format units that are unsupported as "legacy
     converters", because they require arguments, and the legacy
     converter syntax doesn’t support specifying arguments.

   * In the future we may have a new argument parsing library that isn’t
     restricted to what *note PyArg_ParseTuple(): 26b. supports; this
     flexibility won’t be available to parameters using legacy
     converters.

Therefore, if you don’t mind a little extra effort, please use the
normal converters instead of legacy converters.

In a nutshell, the syntax for Argument Clinic (non-legacy) converters
looks like a Python function call.  However, if there are no explicit
arguments to the function (all functions take their default values), you
may omit the parentheses.  Thus ‘bool’ and ‘bool()’ are exactly the same
converters.

All arguments to Argument Clinic converters are keyword-only.  All
Argument Clinic converters accept the following arguments:

     ‘c_default’

          The default value for this parameter when defined in C.
          Specifically, this will be the initializer for the variable
          declared in the "parse function".  See *note the section on
          default values: 4201. for how to use this.  Specified as a
          string.

     ‘annotation’

          The annotation value for this parameter.  Not currently
          supported, because PEP 8(1) mandates that the Python library
          may not use annotations.

In addition, some converters accept additional arguments.  Here is a
list of these arguments, along with their meanings:

     ‘accept’

          A set of Python types (and possibly pseudo-types); this
          restricts the allowable Python argument to values of these
          types.  (This is not a general-purpose facility; as a rule it
          only supports specific lists of types as shown in the legacy
          converter table.)

          To accept ‘None’, add ‘NoneType’ to this set.

     ‘bitwise’

          Only supported for unsigned integers.  The native integer
          value of this Python argument will be written to the parameter
          without any range checking, even for negative values.

     ‘converter’

          Only supported by the ‘object’ converter.  Specifies the name
          of a *note C "converter function": 3c7a. to use to convert
          this object to a native type.

     ‘encoding’

          Only supported for strings.  Specifies the encoding to use
          when converting this string from a Python str (Unicode) value
          into a C ‘char *’ value.

     ‘subclass_of’

          Only supported for the ‘object’ converter.  Requires that the
          Python value be a subclass of a Python type, as expressed in
          C.

     ‘type’

          Only supported for the ‘object’ and ‘self’ converters.
          Specifies the C type that will be used to declare the
          variable.  Default value is ‘"PyObject *"’.

     ‘zeroes’

          Only supported for strings.  If true, embedded NUL bytes
          (‘'\\0'’) are permitted inside the value.  The length of the
          string will be passed in to the impl function, just after the
          string parameter, as a parameter named
          ‘<parameter_name>_length’.

Please note, not every possible combination of arguments will work.
Usually these arguments are implemented by specific ‘PyArg_ParseTuple’
`format units', with specific behavior.  For example, currently you
cannot call ‘unsigned_short’ without also specifying ‘bitwise=True’.
Although it’s perfectly reasonable to think this would work, these
semantics don’t map to any existing format unit.  So Argument Clinic
doesn’t support it.  (Or, at least, not yet.)

Below is a table showing the mapping of legacy converters into real
Argument Clinic converters.  On the left is the legacy converter, on the
right is the text you’d replace it with.

‘'B'’         ‘unsigned_char(bitwise=True)’
              
              
‘'b'’         ‘unsigned_char’
              
              
‘'c'’         ‘char’
              
              
‘'C'’         ‘int(accept={str})’
              
              
‘'d'’         ‘double’
              
              
‘'D'’         ‘Py_complex’
              
              
‘'es'’        ‘str(encoding='name_of_encoding')’
              
              
‘'es#'’       ‘str(encoding='name_of_encoding', zeroes=True)’
              
              
‘'et'’        ‘str(encoding='name_of_encoding', accept={bytes, bytearray, str})’
              
              
‘'et#'’       ‘str(encoding='name_of_encoding', accept={bytes, bytearray, str}, zeroes=True)’
              
              
‘'f'’         ‘float’
              
              
‘'h'’         ‘short’
              
              
‘'H'’         ‘unsigned_short(bitwise=True)’
              
              
‘'i'’         ‘int’
              
              
‘'I'’         ‘unsigned_int(bitwise=True)’
              
              
‘'k'’         ‘unsigned_long(bitwise=True)’
              
              
‘'K'’         ‘unsigned_long_long(bitwise=True)’
              
              
‘'l'’         ‘long’
              
              
‘'L'’         ‘long long’
              
              
‘'n'’         ‘Py_ssize_t’
              
              
‘'O'’         ‘object’
              
              
‘'O!'’        ‘object(subclass_of='&PySomething_Type')’
              
              
‘'O&'’        ‘object(converter='name_of_c_function')’
              
              
‘'p'’         ‘bool’
              
              
‘'S'’         ‘PyBytesObject’
              
              
‘'s'’         ‘str’
              
              
‘'s#'’        ‘str(zeroes=True)’
              
              
‘'s*'’        ‘Py_buffer(accept={buffer, str})’
              
              
‘'U'’         ‘unicode’
              
              
‘'u'’         ‘Py_UNICODE’
              
              
‘'u#'’        ‘Py_UNICODE(zeroes=True)’
              
              
‘'w*'’        ‘Py_buffer(accept={rwbuffer})’
              
              
‘'Y'’         ‘PyByteArrayObject’
              
              
‘'y'’         ‘str(accept={bytes})’
              
              
‘'y#'’        ‘str(accept={robuffer}, zeroes=True)’
              
              
‘'y*'’        ‘Py_buffer’
              
              
‘'Z'’         ‘Py_UNICODE(accept={str, NoneType})’
              
              
‘'Z#'’        ‘Py_UNICODE(accept={str, NoneType}, zeroes=True)’
              
              
‘'z'’         ‘str(accept={str, NoneType})’
              
              
‘'z#'’        ‘str(accept={str, NoneType}, zeroes=True)’
              
              
‘'z*'’        ‘Py_buffer(accept={buffer, str, NoneType})’
              

As an example, here’s our sample ‘pickle.Pickler.dump’ using the proper
converter:

     /*[clinic input]
     pickle.Pickler.dump

         obj: object
             The object to be pickled.
         /

     Write a pickled representation of obj to the open file.
     [clinic start generated code]*/

One advantage of real converters is that they’re more flexible than
legacy converters.  For example, the ‘unsigned_int’ converter (and all
the ‘unsigned_’ converters) can be specified without ‘bitwise=True’.
Their default behavior performs range checking on the value, and they
won’t accept negative numbers.  You just can’t do that with a legacy
converter!

Argument Clinic will show you all the converters it has available.  For
each converter it’ll show you all the parameters it accepts, along with
the default value for each parameter.  Just run ‘Tools/clinic/clinic.py
--converters’ to see the full list.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0008


File: python.info,  Node: Py_buffer,  Next: Advanced converters,  Prev: Using real Argument Clinic converters instead of "legacy converters",  Up: Advanced Topics

10.15.4.6 Py_buffer
...................

When using the ‘Py_buffer’ converter (or the ‘'s*'’, ‘'w*'’, ‘'*y'’, or
‘'z*'’ legacy converters), you `must' not call *note PyBuffer_Release():
d59. on the provided buffer.  Argument Clinic generates code that does
it for you (in the parsing function).


File: python.info,  Node: Advanced converters,  Next: Parameter default values,  Prev: Py_buffer,  Up: Advanced Topics

10.15.4.7 Advanced converters
.............................

Remember those format units you skipped for your first time because they
were advanced?  Here’s how to handle those too.

The trick is, all those format units take arguments—either conversion
functions, or types, or strings specifying an encoding.  (But "legacy
converters" don’t support arguments.  That’s why we skipped them for
your first function.)  The argument you specified to the format unit is
now an argument to the converter; this argument is either ‘converter’
(for ‘O&’), ‘subclass_of’ (for ‘O!’), or ‘encoding’ (for all the format
units that start with ‘e’).

When using ‘subclass_of’, you may also want to use the other custom
argument for ‘object()’: ‘type’, which lets you set the type actually
used for the parameter.  For example, if you want to ensure that the
object is a subclass of ‘PyUnicode_Type’, you probably want to use the
converter ‘object(type='PyUnicodeObject *',
subclass_of='&PyUnicode_Type')’.

One possible problem with using Argument Clinic: it takes away some
possible flexibility for the format units starting with ‘e’.  When
writing a ‘PyArg_Parse’ call by hand, you could theoretically decide at
runtime what encoding string to pass in to *note PyArg_ParseTuple():
26b.  But now this string must be hard-coded at
Argument-Clinic-preprocessing-time.  This limitation is deliberate; it
made supporting this format unit much easier, and may allow for future
optimizations.  This restriction doesn’t seem unreasonable; CPython
itself always passes in static hard-coded encoding strings for
parameters whose format units start with ‘e’.


File: python.info,  Node: Parameter default values,  Next: The NULL default value,  Prev: Advanced converters,  Up: Advanced Topics

10.15.4.8 Parameter default values
..................................

Default values for parameters can be any of a number of values.  At
their simplest, they can be string, int, or float literals:

     foo: str = "abc"
     bar: int = 123
     bat: float = 45.6

They can also use any of Python’s built-in constants:

     yep:  bool = True
     nope: bool = False
     nada: object = None

There’s also special support for a default value of ‘NULL’, and for
simple expressions, documented in the following sections.


File: python.info,  Node: The NULL default value,  Next: Expressions specified as default values,  Prev: Parameter default values,  Up: Advanced Topics

10.15.4.9 The ‘NULL’ default value
..................................

For string and object parameters, you can set them to ‘None’ to indicate
that there’s no default.  However, that means the C variable will be
initialized to ‘Py_None’.  For convenience’s sakes, there’s a special
value called ‘NULL’ for just this reason: from Python’s perspective it
behaves like a default value of ‘None’, but the C variable is
initialized with ‘NULL’.


File: python.info,  Node: Expressions specified as default values,  Next: Using a return converter,  Prev: The NULL default value,  Up: Advanced Topics

10.15.4.10 Expressions specified as default values
..................................................

The default value for a parameter can be more than just a literal value.
It can be an entire expression, using math operators and looking up
attributes on objects.  However, this support isn’t exactly simple,
because of some non-obvious semantics.

Consider the following example:

     foo: Py_ssize_t = sys.maxsize - 1

‘sys.maxsize’ can have different values on different platforms.
Therefore Argument Clinic can’t simply evaluate that expression locally
and hard-code it in C. So it stores the default in such a way that it
will get evaluated at runtime, when the user asks for the function’s
signature.

What namespace is available when the expression is evaluated?  It’s
evaluated in the context of the module the builtin came from.  So, if
your module has an attribute called "‘max_widgets’", you may simply use
it:

     foo: Py_ssize_t = max_widgets

If the symbol isn’t found in the current module, it fails over to
looking in ‘sys.modules’.  That’s how it can find ‘sys.maxsize’ for
example.  (Since you don’t know in advance what modules the user will
load into their interpreter, it’s best to restrict yourself to modules
that are preloaded by Python itself.)

Evaluating default values only at runtime means Argument Clinic can’t
compute the correct equivalent C default value.  So you need to tell it
explicitly.  When you use an expression, you must also specify the
equivalent expression in C, using the ‘c_default’ parameter to the
converter:

     foo: Py_ssize_t(c_default="PY_SSIZE_T_MAX - 1") = sys.maxsize - 1

Another complication: Argument Clinic can’t know in advance whether or
not the expression you supply is valid.  It parses it to make sure it
looks legal, but it can’t `actually' know.  You must be very careful
when using expressions to specify values that are guaranteed to be valid
at runtime!

Finally, because expressions must be representable as static C values,
there are many restrictions on legal expressions.  Here’s a list of
Python features you’re not permitted to use:

   * Function calls.

   * Inline if statements (‘3 if foo else 5’).

   * Automatic sequence unpacking (‘*[1, 2, 3]’).

   * List/set/dict comprehensions and generator expressions.

   * Tuple/list/set/dict literals.


File: python.info,  Node: Using a return converter,  Next: Cloning existing functions,  Prev: Expressions specified as default values,  Up: Advanced Topics

10.15.4.11 Using a return converter
...................................

By default the impl function Argument Clinic generates for you returns
‘PyObject *’.  But your C function often computes some C type, then
converts it into the ‘PyObject *’ at the last moment.  Argument Clinic
handles converting your inputs from Python types into native C types—why
not have it convert your return value from a native C type into a Python
type too?

That’s what a "return converter" does.  It changes your impl function to
return some C type, then adds code to the generated (non-impl) function
to handle converting that value into the appropriate ‘PyObject *’.

The syntax for return converters is similar to that of parameter
converters.  You specify the return converter like it was a return
annotation on the function itself.  Return converters behave much the
same as parameter converters; they take arguments, the arguments are all
keyword-only, and if you’re not changing any of the default arguments
you can omit the parentheses.

(If you use both ‘"as"’ `and' a return converter for your function, the
‘"as"’ should come before the return converter.)

There’s one additional complication when using return converters: how do
you indicate an error has occurred?  Normally, a function returns a
valid (non-‘NULL’) pointer for success, and ‘NULL’ for failure.  But if
you use an integer return converter, all integers are valid.  How can
Argument Clinic detect an error?  Its solution: each return converter
implicitly looks for a special value that indicates an error.  If you
return that value, and an error has been set (‘PyErr_Occurred()’ returns
a true value), then the generated code will propagate the error.
Otherwise it will encode the value you return like normal.

Currently Argument Clinic supports only a few return converters:

     bool
     int
     unsigned int
     long
     unsigned int
     size_t
     Py_ssize_t
     float
     double
     DecodeFSDefault

None of these take parameters.  For the first three, return -1 to
indicate error.  For ‘DecodeFSDefault’, the return type is ‘const char
*’; return a ‘NULL’ pointer to indicate an error.

(There’s also an experimental ‘NoneType’ converter, which lets you
return ‘Py_None’ on success or ‘NULL’ on failure, without having to
increment the reference count on ‘Py_None’.  I’m not sure it adds enough
clarity to be worth using.)

To see all the return converters Argument Clinic supports, along with
their parameters (if any), just run ‘Tools/clinic/clinic.py
--converters’ for the full list.


File: python.info,  Node: Cloning existing functions,  Next: Calling Python code,  Prev: Using a return converter,  Up: Advanced Topics

10.15.4.12 Cloning existing functions
.....................................

If you have a number of functions that look similar, you may be able to
use Clinic’s "clone" feature.  When you clone an existing function, you
reuse:

   * its parameters, including

        * their names,

        * their converters, with all parameters,

        * their default values,

        * their per-parameter docstrings,

        * their `kind' (whether they’re positional only, positional or
          keyword, or keyword only), and

   * its return converter.

The only thing not copied from the original function is its docstring;
the syntax allows you to specify a new docstring.

Here’s the syntax for cloning a function:

     /*[clinic input]
     module.class.new_function [as c_basename] = module.class.existing_function

     Docstring for new_function goes here.
     [clinic start generated code]*/

(The functions can be in different modules or classes.  I wrote
‘module.class’ in the sample just to illustrate that you must use the
full path to `both' functions.)

Sorry, there’s no syntax for partially-cloning a function, or cloning a
function then modifying it.  Cloning is an all-or nothing proposition.

Also, the function you are cloning from must have been previously
defined in the current file.


File: python.info,  Node: Calling Python code,  Next: Using a "self converter",  Prev: Cloning existing functions,  Up: Advanced Topics

10.15.4.13 Calling Python code
..............................

The rest of the advanced topics require you to write Python code which
lives inside your C file and modifies Argument Clinic’s runtime state.
This is simple: you simply define a Python block.

A Python block uses different delimiter lines than an Argument Clinic
function block.  It looks like this:

     /*[python input]
     # python code goes here
     [python start generated code]*/

All the code inside the Python block is executed at the time it’s
parsed.  All text written to stdout inside the block is redirected into
the "output" after the block.

As an example, here’s a Python block that adds a static integer variable
to the C code:

     /*[python input]
     print('static int __ignored_unused_variable__ = 0;')
     [python start generated code]*/
     static int __ignored_unused_variable__ = 0;
     /*[python checksum:...]*/


File: python.info,  Node: Using a "self converter",  Next: Writing a custom converter,  Prev: Calling Python code,  Up: Advanced Topics

10.15.4.14 Using a "self converter"
...................................

Argument Clinic automatically adds a "self" parameter for you using a
default converter.  It automatically sets the ‘type’ of this parameter
to the "pointer to an instance" you specified when you declared the
type.  However, you can override Argument Clinic’s converter and specify
one yourself.  Just add your own ‘self’ parameter as the first parameter
in a block, and ensure that its converter is an instance of
‘self_converter’ or a subclass thereof.

What’s the point?  This lets you override the type of ‘self’, or give it
a different default name.

How do you specify the custom type you want to cast ‘self’ to?  If you
only have one or two functions with the same type for ‘self’, you can
directly use Argument Clinic’s existing ‘self’ converter, passing in the
type you want to use as the ‘type’ parameter:

     /*[clinic input]

     _pickle.Pickler.dump

       self: self(type="PicklerObject *")
       obj: object
       /

     Write a pickled representation of the given object to the open file.
     [clinic start generated code]*/

On the other hand, if you have a lot of functions that will use the same
type for ‘self’, it’s best to create your own converter, subclassing
‘self_converter’ but overwriting the ‘type’ member:

     /*[python input]
     class PicklerObject_converter(self_converter):
         type = "PicklerObject *"
     [python start generated code]*/

     /*[clinic input]

     _pickle.Pickler.dump

       self: PicklerObject
       obj: object
       /

     Write a pickled representation of the given object to the open file.
     [clinic start generated code]*/


File: python.info,  Node: Writing a custom converter,  Next: Writing a custom return converter,  Prev: Using a "self converter",  Up: Advanced Topics

10.15.4.15 Writing a custom converter
.....................................

As we hinted at in the previous section...  you can write your own
converters!  A converter is simply a Python class that inherits from
‘CConverter’.  The main purpose of a custom converter is if you have a
parameter using the ‘O&’ format unit—parsing this parameter means
calling a *note PyArg_ParseTuple(): 26b. "converter function".

Your converter class should be named ‘*something*_converter’.  If the
name follows this convention, then your converter class will be
automatically registered with Argument Clinic; its name will be the name
of your class with the ‘_converter’ suffix stripped off.  (This is
accomplished with a metaclass.)

You shouldn’t subclass ‘CConverter.__init__’.  Instead, you should write
a ‘converter_init()’ function.  ‘converter_init()’ always accepts a
‘self’ parameter; after that, all additional parameters `must' be
keyword-only.  Any arguments passed in to the converter in Argument
Clinic will be passed along to your ‘converter_init()’.

There are some additional members of ‘CConverter’ you may wish to
specify in your subclass.  Here’s the current list:

‘type’

     The C type to use for this variable.  ‘type’ should be a Python
     string specifying the type, e.g.  ‘int’.  If this is a pointer
     type, the type string should end with ‘' *'’.

‘default’

     The Python default value for this parameter, as a Python value.  Or
     the magic value ‘unspecified’ if there is no default.

‘py_default’

     ‘default’ as it should appear in Python code, as a string.  Or
     ‘None’ if there is no default.

‘c_default’

     ‘default’ as it should appear in C code, as a string.  Or ‘None’ if
     there is no default.

‘c_ignored_default’

     The default value used to initialize the C variable when there is
     no default, but not specifying a default may result in an
     "uninitialized variable" warning.  This can easily happen when
     using option groups—although properly-written code will never
     actually use this value, the variable does get passed in to the
     impl, and the C compiler will complain about the "use" of the
     uninitialized value.  This value should always be a non-empty
     string.

‘converter’

     The name of the C converter function, as a string.

‘impl_by_reference’

     A boolean value.  If true, Argument Clinic will add a ‘&’ in front
     of the name of the variable when passing it into the impl function.

‘parse_by_reference’

     A boolean value.  If true, Argument Clinic will add a ‘&’ in front
     of the name of the variable when passing it into *note
     PyArg_ParseTuple(): 26b.

Here’s the simplest example of a custom converter, from
‘Modules/zlibmodule.c’:

     /*[python input]

     class ssize_t_converter(CConverter):
         type = 'Py_ssize_t'
         converter = 'ssize_t_converter'

     [python start generated code]*/
     /*[python end generated code: output=da39a3ee5e6b4b0d input=35521e4e733823c7]*/

This block adds a converter to Argument Clinic named ‘ssize_t’.
Parameters declared as ‘ssize_t’ will be declared as type ‘Py_ssize_t’,
and will be parsed by the ‘'O&'’ format unit, which will call the
‘ssize_t_converter’ converter function.  ‘ssize_t’ variables
automatically support default values.

More sophisticated custom converters can insert custom C code to handle
initialization and cleanup.  You can see more examples of custom
converters in the CPython source tree; grep the C files for the string
‘CConverter’.


File: python.info,  Node: Writing a custom return converter,  Next: METH_O and METH_NOARGS,  Prev: Writing a custom converter,  Up: Advanced Topics

10.15.4.16 Writing a custom return converter
............................................

Writing a custom return converter is much like writing a custom
converter.  Except it’s somewhat simpler, because return converters are
themselves much simpler.

Return converters must subclass ‘CReturnConverter’.  There are no
examples yet of custom return converters, because they are not widely
used yet.  If you wish to write your own return converter, please read
‘Tools/clinic/clinic.py’, specifically the implementation of
‘CReturnConverter’ and all its subclasses.


File: python.info,  Node: METH_O and METH_NOARGS,  Next: tp_new and tp_init functions,  Prev: Writing a custom return converter,  Up: Advanced Topics

10.15.4.17 METH_O and METH_NOARGS
.................................

To convert a function using ‘METH_O’, make sure the function’s single
argument is using the ‘object’ converter, and mark the arguments as
positional-only:

     /*[clinic input]
     meth_o_sample

          argument: object
          /
     [clinic start generated code]*/

To convert a function using ‘METH_NOARGS’, just don’t specify any
arguments.

You can still use a self converter, a return converter, and specify a
‘type’ argument to the object converter for ‘METH_O’.


File: python.info,  Node: tp_new and tp_init functions,  Next: Changing and redirecting Clinic's output,  Prev: METH_O and METH_NOARGS,  Up: Advanced Topics

10.15.4.18 tp_new and tp_init functions
.......................................

You can convert ‘tp_new’ and ‘tp_init’ functions.  Just name them
‘__new__’ or ‘__init__’ as appropriate.  Notes:

   * The function name generated for ‘__new__’ doesn’t end in ‘__new__’
     like it would by default.  It’s just the name of the class,
     converted into a valid C identifier.

   * No ‘PyMethodDef’ ‘#define’ is generated for these functions.

   * ‘__init__’ functions return ‘int’, not ‘PyObject *’.

   * Use the docstring as the class docstring.

   * Although ‘__new__’ and ‘__init__’ functions must always accept both
     the ‘args’ and ‘kwargs’ objects, when converting you may specify
     any signature for these functions that you like.  (If your function
     doesn’t support keywords, the parsing function generated will throw
     an exception if it receives any.)


File: python.info,  Node: Changing and redirecting Clinic's output,  Next: The #ifdef trick,  Prev: tp_new and tp_init functions,  Up: Advanced Topics

10.15.4.19 Changing and redirecting Clinic’s output
...................................................

It can be inconvenient to have Clinic’s output interspersed with your
conventional hand-edited C code.  Luckily, Clinic is configurable: you
can buffer up its output for printing later (or earlier!), or write its
output to a separate file.  You can also add a prefix or suffix to every
line of Clinic’s generated output.

While changing Clinic’s output in this manner can be a boon to
readability, it may result in Clinic code using types before they are
defined, or your code attempting to use Clinic-generated code before it
is defined.  These problems can be easily solved by rearranging the
declarations in your file, or moving where Clinic’s generated code goes.
(This is why the default behavior of Clinic is to output everything into
the current block; while many people consider this hampers readability,
it will never require rearranging your code to fix definition-before-use
problems.)

Let’s start with defining some terminology:

`field'

     A field, in this context, is a subsection of Clinic’s output.  For
     example, the ‘#define’ for the ‘PyMethodDef’ structure is a field,
     called ‘methoddef_define’.  Clinic has seven different fields it
     can output per function definition:

          docstring_prototype
          docstring_definition
          methoddef_define
          impl_prototype
          parser_prototype
          parser_definition
          impl_definition

     All the names are of the form ‘"<a>_<b>"’, where ‘"<a>"’ is the
     semantic object represented (the parsing function, the impl
     function, the docstring, or the methoddef structure) and ‘"<b>"’
     represents what kind of statement the field is.  Field names that
     end in ‘"_prototype"’ represent forward declarations of that thing,
     without the actual body/data of the thing; field names that end in
     ‘"_definition"’ represent the actual definition of the thing, with
     the body/data of the thing.  (‘"methoddef"’ is special, it’s the
     only one that ends with ‘"_define"’, representing that it’s a
     preprocessor #define.)

`destination'

     A destination is a place Clinic can write output to.  There are
     five built-in destinations:

     ‘block’

          The default destination: printed in the output section of the
          current Clinic block.

     ‘buffer’

          A text buffer where you can save text for later.  Text sent
          here is appended to the end of any existing text.  It’s an
          error to have any text left in the buffer when Clinic finishes
          processing a file.

     ‘file’

          A separate "clinic file" that will be created automatically by
          Clinic.  The filename chosen for the file is
          ‘{basename}.clinic{extension}’, where ‘basename’ and
          ‘extension’ were assigned the output from ‘os.path.splitext()’
          run on the current file.  (Example: the ‘file’ destination for
          ‘_pickle.c’ would be written to ‘_pickle.clinic.c’.)

          `Important: When using a' ‘file’ `destination, you' `must
          check in' `the generated file!'

     ‘two-pass’

          A buffer like ‘buffer’.  However, a two-pass buffer can only
          be dumped once, and it prints out all text sent to it during
          all processing, even from Clinic blocks `after' the dumping
          point.

     ‘suppress’

          The text is suppressed—thrown away.

Clinic defines five new directives that let you reconfigure its output.

The first new directive is ‘dump’:

     dump <destination>

This dumps the current contents of the named destination into the output
of the current block, and empties it.  This only works with ‘buffer’ and
‘two-pass’ destinations.

The second new directive is ‘output’.  The most basic form of ‘output’
is like this:

     output <field> <destination>

This tells Clinic to output `field' to `destination'.  ‘output’ also
supports a special meta-destination, called ‘everything’, which tells
Clinic to output `all' fields to that `destination'.

‘output’ has a number of other functions:

     output push
     output pop
     output preset <preset>

‘output push’ and ‘output pop’ allow you to push and pop configurations
on an internal configuration stack, so that you can temporarily modify
the output configuration, then easily restore the previous
configuration.  Simply push before your change to save the current
configuration, then pop when you wish to restore the previous
configuration.

‘output preset’ sets Clinic’s output to one of several built-in preset
configurations, as follows:

     ‘block’

          Clinic’s original starting configuration.  Writes everything
          immediately after the input block.

          Suppress the ‘parser_prototype’ and ‘docstring_prototype’,
          write everything else to ‘block’.

     ‘file’

          Designed to write everything to the "clinic file" that it can.
          You then ‘#include’ this file near the top of your file.  You
          may need to rearrange your file to make this work, though
          usually this just means creating forward declarations for
          various ‘typedef’ and ‘PyTypeObject’ definitions.

          Suppress the ‘parser_prototype’ and ‘docstring_prototype’,
          write the ‘impl_definition’ to ‘block’, and write everything
          else to ‘file’.

          The default filename is ‘"{dirname}/clinic/{basename}.h"’.

     ‘buffer’

          Save up most of the output from Clinic, to be written into
          your file near the end.  For Python files implementing modules
          or builtin types, it’s recommended that you dump the buffer
          just above the static structures for your module or builtin
          type; these are normally very near the end.  Using ‘buffer’
          may require even more editing than ‘file’, if your file has
          static ‘PyMethodDef’ arrays defined in the middle of the file.

          Suppress the ‘parser_prototype’, ‘impl_prototype’, and
          ‘docstring_prototype’, write the ‘impl_definition’ to ‘block’,
          and write everything else to ‘file’.

     ‘two-pass’

          Similar to the ‘buffer’ preset, but writes forward
          declarations to the ‘two-pass’ buffer, and definitions to the
          ‘buffer’.  This is similar to the ‘buffer’ preset, but may
          require less editing than ‘buffer’.  Dump the ‘two-pass’
          buffer near the top of your file, and dump the ‘buffer’ near
          the end just like you would when using the ‘buffer’ preset.

          Suppresses the ‘impl_prototype’, write the ‘impl_definition’
          to ‘block’, write ‘docstring_prototype’, ‘methoddef_define’,
          and ‘parser_prototype’ to ‘two-pass’, write everything else to
          ‘buffer’.

     ‘partial-buffer’

          Similar to the ‘buffer’ preset, but writes more things to
          ‘block’, only writing the really big chunks of generated code
          to ‘buffer’.  This avoids the definition-before-use problem of
          ‘buffer’ completely, at the small cost of having slightly more
          stuff in the block’s output.  Dump the ‘buffer’ near the end,
          just like you would when using the ‘buffer’ preset.

          Suppresses the ‘impl_prototype’, write the
          ‘docstring_definition’ and ‘parser_definition’ to ‘buffer’,
          write everything else to ‘block’.

The third new directive is ‘destination’:

     destination <name> <command> [...]

This performs an operation on the destination named ‘name’.

There are two defined subcommands: ‘new’ and ‘clear’.

The ‘new’ subcommand works like this:

     destination <name> new <type>

This creates a new destination with name ‘<name>’ and type ‘<type>’.

There are five destination types:

     ‘suppress’

          Throws the text away.

     ‘block’

          Writes the text to the current block.  This is what Clinic
          originally did.

     ‘buffer’

          A simple text buffer, like the "buffer" builtin destination
          above.

     ‘file’

          A text file.  The file destination takes an extra argument, a
          template to use for building the filename, like so:

               destination <name> new <type> <file_template>

          The template can use three strings internally that will be
          replaced by bits of the filename:

               {path}

                    The full path to the file, including directory and
                    full filename.

               {dirname}

                    The name of the directory the file is in.

               {basename}

                    Just the name of the file, not including the
                    directory.

               {basename_root}

                    Basename with the extension clipped off (everything
                    up to but not including the last ’.’).

               {basename_extension}

                    The last ’.’ and everything after it.  If the
                    basename does not contain a period, this will be the
                    empty string.

          If there are no periods in the filename, {basename} and
          {filename} are the same, and {extension} is empty.
          "{basename}{extension}" is always exactly the same as
          "{filename}"."

     ‘two-pass’

          A two-pass buffer, like the "two-pass" builtin destination
          above.

The ‘clear’ subcommand works like this:

     destination <name> clear

It removes all the accumulated text up to this point in the destination.
(I don’t know what you’d need this for, but I thought maybe it’d be
useful while someone’s experimenting.)

The fourth new directive is ‘set’:

     set line_prefix "string"
     set line_suffix "string"

‘set’ lets you set two internal variables in Clinic.  ‘line_prefix’ is a
string that will be prepended to every line of Clinic’s output;
‘line_suffix’ is a string that will be appended to every line of
Clinic’s output.

Both of these support two format strings:

     ‘{block comment start}’

          Turns into the string ‘/*’, the start-comment text sequence
          for C files.

     ‘{block comment end}’

          Turns into the string ‘*/’, the end-comment text sequence for
          C files.

The final new directive is one you shouldn’t need to use directly,
called ‘preserve’:

     preserve

This tells Clinic that the current contents of the output should be
kept, unmodified.  This is used internally by Clinic when dumping output
into ‘file’ files; wrapping it in a Clinic block lets Clinic use its
existing checksum functionality to ensure the file was not modified by
hand before it gets overwritten.


File: python.info,  Node: The #ifdef trick,  Next: Using Argument Clinic in Python files,  Prev: Changing and redirecting Clinic's output,  Up: Advanced Topics

10.15.4.20 The #ifdef trick
...........................

If you’re converting a function that isn’t available on all platforms,
there’s a trick you can use to make life a little easier.  The existing
code probably looks like this:

     #ifdef HAVE_FUNCTIONNAME
     static module_functionname(...)
     {
     ...
     }
     #endif /* HAVE_FUNCTIONNAME */

And then in the ‘PyMethodDef’ structure at the bottom the existing code
will have:

     #ifdef HAVE_FUNCTIONNAME
     {'functionname', ... },
     #endif /* HAVE_FUNCTIONNAME */

In this scenario, you should enclose the body of your impl function
inside the ‘#ifdef’, like so:

     #ifdef HAVE_FUNCTIONNAME
     /*[clinic input]
     module.functionname
     ...
     [clinic start generated code]*/
     static module_functionname(...)
     {
     ...
     }
     #endif /* HAVE_FUNCTIONNAME */

Then, remove those three lines from the ‘PyMethodDef’ structure,
replacing them with the macro Argument Clinic generated:

     MODULE_FUNCTIONNAME_METHODDEF

(You can find the real name for this macro inside the generated code.
Or you can calculate it yourself: it’s the name of your function as
defined on the first line of your block, but with periods changed to
underscores, uppercased, and ‘"_METHODDEF"’ added to the end.)

Perhaps you’re wondering: what if ‘HAVE_FUNCTIONNAME’ isn’t defined?
The ‘MODULE_FUNCTIONNAME_METHODDEF’ macro won’t be defined either!

Here’s where Argument Clinic gets very clever.  It actually detects that
the Argument Clinic block might be deactivated by the ‘#ifdef’.  When
that happens, it generates a little extra code that looks like this:

     #ifndef MODULE_FUNCTIONNAME_METHODDEF
         #define MODULE_FUNCTIONNAME_METHODDEF
     #endif /* !defined(MODULE_FUNCTIONNAME_METHODDEF) */

That means the macro always works.  If the function is defined, this
turns into the correct structure, including the trailing comma.  If the
function is undefined, this turns into nothing.

However, this causes one ticklish problem: where should Argument Clinic
put this extra code when using the "block" output preset?  It can’t go
in the output block, because that could be deactivated by the ‘#ifdef’.
(That’s the whole point!)

In this situation, Argument Clinic writes the extra code to the "buffer"
destination.  This may mean that you get a complaint from Argument
Clinic:

     Warning in file "Modules/posixmodule.c" on line 12357:
     Destination buffer 'buffer' not empty at end of file, emptying.

When this happens, just open your file, find the ‘dump buffer’ block
that Argument Clinic added to your file (it’ll be at the very bottom),
then move it above the ‘PyMethodDef’ structure where that macro is used.


File: python.info,  Node: Using Argument Clinic in Python files,  Prev: The #ifdef trick,  Up: Advanced Topics

10.15.4.21 Using Argument Clinic in Python files
................................................

It’s actually possible to use Argument Clinic to preprocess Python
files.  There’s no point to using Argument Clinic blocks, of course, as
the output wouldn’t make any sense to the Python interpreter.  But using
Argument Clinic to run Python blocks lets you use Python as a Python
preprocessor!

Since Python comments are different from C comments, Argument Clinic
blocks embedded in Python files look slightly different.  They look like
this:

     #/*[python input]
     #print("def foo(): pass")
     #[python start generated code]*/
     def foo(): pass
     #/*[python checksum:...]*/


File: python.info,  Node: Instrumenting CPython with DTrace and SystemTap,  Prev: Argument Clinic How-To,  Up: Python HOWTOs

10.16 Instrumenting CPython with DTrace and SystemTap
=====================================================


author: David Malcolm


author: Łukasz Langa

DTrace and SystemTap are monitoring tools, each providing a way to
inspect what the processes on a computer system are doing.  They both
use domain-specific languages allowing a user to write scripts which:

        - filter which processes are to be observed

        - gather data from the processes of interest

        - generate reports on the data

As of Python 3.6, CPython can be built with embedded "markers", also
known as "probes", that can be observed by a DTrace or SystemTap script,
making it easier to monitor what the CPython processes on a system are
doing.

`CPython implementation detail:' DTrace markers are implementation
details of the CPython interpreter.  No guarantees are made about probe
compatibility between versions of CPython.  DTrace scripts can stop
working or work incorrectly without warning when changing CPython
versions.

* Menu:

* Enabling the static markers::
* Static DTrace probes::
* Static SystemTap markers::
* Available static markers::
* SystemTap Tapsets::
* Examples: Examples<36>.


File: python.info,  Node: Enabling the static markers,  Next: Static DTrace probes,  Up: Instrumenting CPython with DTrace and SystemTap

10.16.1 Enabling the static markers
-----------------------------------

macOS comes with built-in support for DTrace.  On Linux, in order to
build CPython with the embedded markers for SystemTap, the SystemTap
development tools must be installed.

On a Linux machine, this can be done via:

     $ yum install systemtap-sdt-devel

or:

     $ sudo apt-get install systemtap-sdt-dev

CPython must then be configured ‘--with-dtrace’:

     checking for --with-dtrace... yes

On macOS, you can list available DTrace probes by running a Python
process in the background and listing all probes made available by the
Python provider:

     $ python3.6 -q &
     $ sudo dtrace -l -P python$!  # or: 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

On Linux, you can verify if the SystemTap static markers are present in
the built binary by seeing if it contains a ".note.stapsdt" section.

     $ readelf -S ./python | grep .note.stapsdt
     [30] .note.stapsdt        NOTE         0000000000000000 00308d78

If you’ve built Python as a shared library (with –enable-shared), you
need to look instead within the shared library.  For example:

     $ readelf -S libpython3.3dm.so.1.0 | grep .note.stapsdt
     [29] .note.stapsdt        NOTE         0000000000000000 00365b68

Sufficiently modern readelf can print the 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

The above metadata contains information for SystemTap describing how it
can patch strategically-placed machine code instructions to enable the
tracing hooks used by a SystemTap script.


File: python.info,  Node: Static DTrace probes,  Next: Static SystemTap markers,  Prev: Enabling the static markers,  Up: Instrumenting CPython with DTrace and SystemTap

10.16.2 Static DTrace probes
----------------------------

The following example DTrace script can be used to show the call/return
hierarchy of a Python script, only tracing within the invocation of a
function called "start".  In other words, import-time function
invocations are not going to be listed:

     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;
     }

It can be invoked like this:

     $ sudo dtrace -q -s call_stack.d -c "python3.6 script.py"

The output looks like this:

     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: Static SystemTap markers,  Next: Available static markers,  Prev: Static DTrace probes,  Up: Instrumenting CPython with DTrace and SystemTap

10.16.3 Static SystemTap markers
--------------------------------

The low-level way to use the SystemTap integration is to use the static
markers directly.  This requires you to explicitly state the binary file
containing them.

For example, this SystemTap script can be used to show the call/return
hierarchy of a Python script:

     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);
     }

It can be invoked like this:

     $ stap \
       show-call-hierarchy.stp \
       -c "./python test.py"

The output looks like this:

     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

where the columns are:

        - time in microseconds since start of script

        - name of executable

        - PID of process

and the remainder indicates the call/return hierarchy as the script
executes.

For a ‘–enable-shared’ build of CPython, the markers are contained
within the libpython shared library, and the probe’s dotted path needs
to reflect this.  For example, this line from the above example:

     probe process("python").mark("function__entry") {

should instead read:

     probe process("python").library("libpython3.6dm.so.1.0").mark("function__entry") {

(assuming a debug build of CPython 3.6)


File: python.info,  Node: Available static markers,  Next: SystemTap Tapsets,  Prev: Static SystemTap markers,  Up: Instrumenting CPython with DTrace and SystemTap

10.16.4 Available static markers
--------------------------------

 -- Object: function__entry(str filename, str funcname, int lineno)

     This marker indicates that execution of a Python function has
     begun.  It is only triggered for pure-Python (bytecode) functions.

     The filename, function name, and line number are provided back to
     the tracing script as positional arguments, which must be accessed
     using ‘$arg1’, ‘$arg2’, ‘$arg3’:

             * ‘$arg1’ : ‘(const char *)’ filename, accessible using
               ‘user_string($arg1)’

             * ‘$arg2’ : ‘(const char *)’ function name, accessible
               using ‘user_string($arg2)’

             * ‘$arg3’ : ‘int’ line number

 -- Object: function__return(str filename, str funcname, int lineno)

     This marker is the converse of ‘function__entry()’, and indicates
     that execution of a Python function has ended (either via ‘return’,
     or via an exception).  It is only triggered for pure-Python
     (bytecode) functions.

     The arguments are the same as for ‘function__entry()’

 -- Object: line(str filename, str funcname, int lineno)

     This marker indicates a Python line is about to be executed.  It is
     the equivalent of line-by-line tracing with a Python profiler.  It
     is not triggered within C functions.

     The arguments are the same as for ‘function__entry()’.

 -- Object: gc__start(int generation)

     Fires when the Python interpreter starts a garbage collection
     cycle.  ‘arg0’ is the generation to scan, like *note gc.collect():
     22f.

 -- Object: gc__done(long collected)

     Fires when the Python interpreter finishes a garbage collection
     cycle.  ‘arg0’ is the number of collected objects.

 -- Object: import__find__load__start(str modulename)

     Fires before *note importlib: 9b. attempts to find and load the
     module.  ‘arg0’ is the module name.

     3.7 版新加入.

 -- Object: import__find__load__done(str modulename, int found)

     Fires after *note importlib: 9b.’s find_and_load function is
     called.  ‘arg0’ is the module name, ‘arg1’ indicates if module was
     successfully loaded.

     3.7 版新加入.

 -- Object: audit(str event, void *tuple)

     Fires when *note sys.audit(): f2d. or *note PySys_Audit(): f3b. is
     called.  ‘arg0’ is the event name as C string, ‘arg1’ is a *note
     PyObject: 4bf. pointer to a tuple object.

     3.8 版新加入.


File: python.info,  Node: SystemTap Tapsets,  Next: Examples<36>,  Prev: Available static markers,  Up: Instrumenting CPython with DTrace and SystemTap

10.16.5 SystemTap Tapsets
-------------------------

The higher-level way to use the SystemTap integration is to use a
"tapset": SystemTap’s equivalent of a library, which hides some of the
lower-level details of the static markers.

Here is a tapset file, based on a non-shared build of 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
     }

If this file is installed in SystemTap’s tapset directory (e.g.
‘/usr/share/systemtap/tapset’), then these additional probepoints become
available:

 -- Object: python.function.entry(str filename, str funcname, int
          lineno, frameptr)

     This probe point indicates that execution of a Python function has
     begun.  It is only triggered for pure-Python (bytecode) functions.

 -- Object: python.function.return(str filename, str funcname, int
          lineno, frameptr)

     This probe point is the converse of ‘python.function.return’, and
     indicates that execution of a Python function has ended (either via
     ‘return’, or via an exception).  It is only triggered for
     pure-Python (bytecode) functions.


File: python.info,  Node: Examples<36>,  Prev: SystemTap Tapsets,  Up: Instrumenting CPython with DTrace and SystemTap

10.16.6 Examples
----------------

This SystemTap script uses the tapset above to more cleanly implement
the example given above of tracing the Python function-call hierarchy,
without needing to directly name the static markers:

     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);
     }

The following script uses the tapset above to provide a top-like view of
all running CPython code, showing the top 20 most frequently-entered
bytecode frames, each second, across the whole system:

     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 常見問題,  Next: Glossary,  Prev: Python HOWTOs,  Up: Top

11 Python 常見問題
******************

* Menu:

* 常見Python問答集::
* 程式開發常見問答集::
* Design and History FAQ::
* 函式庫和擴充功能的常見問題::
* Extending/Embedding FAQ::
* FAQ：在 Windows 使用 Python::
* 圖形化使用者界面常見問答集::
* 為什麼Python被安裝在我的機器上?常見問答集::


File: python.info,  Node: 常見Python問答集,  Next: 程式開發常見問答集,  Up: Python 常見問題

11.1 常見Python問答集
=====================

* Menu:

* 常見資訊::
* Python在真實世界::


File: python.info,  Node: 常見資訊,  Next: Python在真實世界,  Up: 常見Python問答集

11.1.1 常見資訊
---------------

* Menu:

* 什麼是Python?::
* 什麼是Python軟體基金會?::
* 當使用Python時有任何版權限制嗎?::
* 為什麼Python被創造出來::
* 什麼是Python擅長的事情::
* How does the Python version numbering scheme work?::
* 我如何拿到Python的原始碼::
* 如何取得Python的相關文件::
* 我從來沒寫過程式，有沒有Python的教學::
* 有沒有新手的群組或是郵件群組討論Python::
* How do I get a beta test version of Python?::
* How do I submit bug reports and patches for Python?::
* Are there any published articles about Python that I can reference?::
* 有沒有關於Python的書::
* www.python.org 這個非營利組織位於哪裡: www python org 這個非營利組織位於哪裡.
* 為什麼要取名為Python::
* 我需要喜歡蒙提·派森的飛行馬戲團這個節目嗎::


File: python.info,  Node: 什麼是Python?,  Next: 什麼是Python軟體基金會?,  Up: 常見資訊

11.1.1.1 什麼是Python?
......................

Python is an interpreted, interactive, object-oriented programming
language.  It incorporates modules, exceptions, dynamic typing, very
high level dynamic data types, and classes.  It supports multiple
programming paradigms beyond object-oriented programming, such as
procedural and functional programming.  Python combines remarkable power
with very clear syntax.  It has interfaces to many system calls and
libraries, as well as to various window systems, and is extensible in C
or C++.  It is also usable as an extension language for applications
that need a programmable interface.  Finally, Python is portable: it
runs on many Unix variants including Linux and macOS, and on Windows.

To find out more, start with *note Python 教學: 11ff.  The Beginner’s
Guide to Python(1) links to other introductory tutorials and resources
for learning Python.

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/BeginnersGuide


File: python.info,  Node: 什麼是Python軟體基金會?,  Next: 當使用Python時有任何版權限制嗎?,  Prev: 什麼是Python?,  Up: 常見資訊

11.1.1.2 什麼是Python軟體基金會?
................................

Python軟體基金會是一個獨立非營利性組織，並且擁有Python版本2.1 與更新的版
本版權。Python軟體基金會的任務在於精進相關於Python 程式語言撰寫於開放原
始碼技術，而且宣傳使用Python 。Python軟體基金會網址
:‘https://www.python.org/psf/’

在美國捐款給Python軟體基金會是免稅的，如果你使用Python而且發現很好用，請
貢獻捐款到Python軟體基金會捐款頁面
<‘https://www.python.org/psf/donations/’>


File: python.info,  Node: 當使用Python時有任何版權限制嗎?,  Next: 為什麼Python被創造出來,  Prev: 什麼是Python軟體基金會?,  Up: 常見資訊

11.1.1.3 當使用Python時有任何版權限制嗎?
........................................

You can do anything you want with the source, as long as you leave the
copyrights in and display those copyrights in any documentation about
Python that you produce.  If you honor the copyright rules, it’s OK to
use Python for commercial use, to sell copies of Python in source or
binary form (modified or unmodified), or to sell products that
incorporate Python in some form.  We would still like to know about all
commercial use of Python, of course.

請看Python軟體基金會的授權頁面<‘https://www.python.org/psf/license/’>有
更完整的授權說明

The Python logo is trademarked, and in certain cases permission is
required to use it.  Consult the Trademark Usage Policy(1) for more
information.

   ---------- Footnotes ----------

   (1) https://www.python.org/psf/trademarks/


File: python.info,  Node: 為什麼Python被創造出來,  Next: 什麼是Python擅長的事情,  Prev: 當使用Python時有任何版權限制嗎?,  Up: 常見資訊

11.1.1.4 為什麼Python被創造出來
...............................

Guido van Rossum寫下這篇"非常長"的簡述說明Python的由來

     I had extensive experience with implementing an interpreted
     language in the ABC group at CWI, and from working with this group
     I had learned a lot about language design.  This is the origin of
     many Python features, including the use of indentation for
     statement grouping and the inclusion of very-high-level data types
     (although the details are all different in Python).

     I had a number of gripes about the ABC language, but also liked
     many of its features.  It was impossible to extend the ABC language
     (or its implementation) to remedy my complaints – in fact its lack
     of extensibility was one of its biggest problems.  I had some
     experience with using Modula-2+ and talked with the designers of
     Modula-3 and read the Modula-3 report.  Modula-3 is the origin of
     the syntax and semantics used for exceptions, and some other Python
     features.

     I was working in the Amoeba distributed operating system group at
     CWI. We needed a better way to do system administration than by
     writing either C programs or Bourne shell scripts, since Amoeba had
     its own system call interface which wasn’t easily accessible from
     the Bourne shell.  My experience with error handling in Amoeba made
     me acutely aware of the importance of exceptions as a programming
     language feature.

     It occurred to me that a scripting language with a syntax like ABC
     but with access to the Amoeba system calls would fill the need.  I
     realized that it would be foolish to write an Amoeba-specific
     language, so I decided that I needed a language that was generally
     extensible.

     During the 1989 Christmas holidays, I had a lot of time on my hand,
     so I decided to give it a try.  During the next year, while still
     mostly working on it in my own time, Python was used in the Amoeba
     project with increasing success, and the feedback from colleagues
     made me add many early improvements.

     In February 1991, after just over a year of development, I decided
     to post to USENET. The rest is in the ‘Misc/HISTORY’ file.


File: python.info,  Node: 什麼是Python擅長的事情,  Next: How does the Python version numbering scheme work?,  Prev: 為什麼Python被創造出來,  Up: 常見資訊

11.1.1.5 什麼是Python擅長的事情
...............................

Python是高階語言及一般任何用途都可以使用的語言，可以用來解決不同的問題

The language comes with a large standard library that covers areas such
as string processing (regular expressions, Unicode, calculating
differences between files), Internet protocols (HTTP, FTP, SMTP,
XML-RPC, POP, IMAP, CGI programming), software engineering (unit
testing, logging, profiling, parsing Python code), and operating system
interfaces (system calls, filesystems, TCP/IP sockets).  Look at the
table of contents for *note Python 標準函式庫 (Standard Library): 1200.
to get an idea of what’s available.  A wide variety of third-party
extensions are also available.  Consult the Python Package Index(1) to
find packages of interest to you.

   ---------- Footnotes ----------

   (1) https://pypi.org


File: python.info,  Node: How does the Python version numbering scheme work?,  Next: 我如何拿到Python的原始碼,  Prev: 什麼是Python擅長的事情,  Up: 常見資訊

11.1.1.6 How does the Python version numbering scheme work?
...........................................................

Python versions are numbered A.B.C or A.B. A is the major version number
– it is only incremented for really major changes in the language.  B is
the minor version number, incremented for less earth-shattering changes.
C is the micro-level – it is incremented for each bugfix release.  See
PEP 6(1) for more information about bugfix releases.

Not all releases are bugfix releases.  In the run-up to a new major
release, a series of development releases are made, denoted as alpha,
beta, or release candidate.  Alphas are early releases in which
interfaces aren’t yet finalized; it’s not unexpected to see an interface
change between two alpha releases.  Betas are more stable, preserving
existing interfaces but possibly adding new modules, and release
candidates are frozen, making no changes except as needed to fix
critical bugs.

Alpha, beta and release candidate versions have an additional suffix.
The suffix for an alpha version is "aN" for some small number N, the
suffix for a beta version is "bN" for some small number N, and the
suffix for a release candidate version is "cN" for some small number N.
In other words, all versions labeled 2.0aN precede the versions labeled
2.0bN, which precede versions labeled 2.0cN, and `those' precede 2.0.

You may also find version numbers with a "+" suffix, e.g.  "2.2+".
These are unreleased versions, built directly from the CPython
development repository.  In practice, after a final minor release is
made, the version is incremented to the next minor version, which
becomes the "a0" version, e.g.  "2.4a0".

See also the documentation for *note sys.version: 5d8, *note
sys.hexversion: 3635, and *note sys.version_info: b1f.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0006


File: python.info,  Node: 我如何拿到Python的原始碼,  Next: 如何取得Python的相關文件,  Prev: How does the Python version numbering scheme work?,  Up: 常見資訊

11.1.1.7 我如何拿到Python的原始碼
.................................

The latest Python source distribution is always available from
python.org, at ‘https://www.python.org/downloads/’.  The latest
development sources can be obtained at
‘https://github.com/python/cpython/’.

The source distribution is a gzipped tar file containing the complete C
source, Sphinx-formatted documentation, Python library modules, example
programs, and several useful pieces of freely distributable software.
The source will compile and run out of the box on most UNIX platforms.

Consult the Getting Started section of the Python Developer’s Guide(1)
for more information on getting the source code and compiling it.

   ---------- Footnotes ----------

   (1) https://devguide.python.org/setup/


File: python.info,  Node: 如何取得Python的相關文件,  Next: 我從來沒寫過程式，有沒有Python的教學,  Prev: 我如何拿到Python的原始碼,  Up: 常見資訊

11.1.1.8 如何取得Python的相關文件
.................................

The standard documentation for the current stable version of Python is
available at ‘https://docs.python.org/3/’.  PDF, plain text, and
downloadable HTML versions are also available at
‘https://docs.python.org/3/download.html’.

The documentation is written in reStructuredText and processed by the
Sphinx documentation tool(1).  The reStructuredText source for the
documentation is part of the Python source distribution.

   ---------- Footnotes ----------

   (1) http://sphinx-doc.org/


File: python.info,  Node: 我從來沒寫過程式，有沒有Python的教學,  Next: 有沒有新手的群組或是郵件群組討論Python,  Prev: 如何取得Python的相關文件,  Up: 常見資訊

11.1.1.9 我從來沒寫過程式，有沒有Python的教學
.............................................

There are numerous tutorials and books available.  The standard
documentation includes *note Python 教學: 11ff.

Consult the Beginner’s Guide(1) to find information for beginning Python
programmers, including lists of tutorials.

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/BeginnersGuide


File: python.info,  Node: 有沒有新手的群組或是郵件群組討論Python,  Next: How do I get a beta test version of Python?,  Prev: 我從來沒寫過程式，有沒有Python的教學,  Up: 常見資訊

11.1.1.10 有沒有新手的群組或是郵件群組討論Python
................................................

There is a newsgroup, ‘comp.lang.python’, and a mailing list,
python-list(1).  The newsgroup and mailing list are gatewayed into each
other – if you can read news it’s unnecessary to subscribe to the
mailing list.  ‘comp.lang.python’ is high-traffic, receiving hundreds of
postings every day, and Usenet readers are often more able to cope with
this volume.

Announcements of new software releases and events can be found in
comp.lang.python.announce, a low-traffic moderated list that receives
about five postings per day.  It’s available as the python-announce
mailing list(2).

More info about other mailing lists and newsgroups can be found at
‘https://www.python.org/community/lists/’.

   ---------- Footnotes ----------

   (1) https://mail.python.org/mailman/listinfo/python-list

   (2) https://mail.python.org/mailman/listinfo/python-announce-list


File: python.info,  Node: How do I get a beta test version of Python?,  Next: How do I submit bug reports and patches for Python?,  Prev: 有沒有新手的群組或是郵件群組討論Python,  Up: 常見資訊

11.1.1.11 How do I get a beta test version of Python?
.....................................................

Alpha and beta releases are available from
‘https://www.python.org/downloads/’.  All releases are announced on the
comp.lang.python and comp.lang.python.announce newsgroups and on the
Python home page at ‘https://www.python.org/’; an RSS feed of news is
available.

You can also access the development version of Python through Git.  See
The Python Developer’s Guide(1) for details.

   ---------- Footnotes ----------

   (1) https://devguide.python.org/


File: python.info,  Node: How do I submit bug reports and patches for Python?,  Next: Are there any published articles about Python that I can reference?,  Prev: How do I get a beta test version of Python?,  Up: 常見資訊

11.1.1.12 How do I submit bug reports and patches for Python?
.............................................................

To report a bug or submit a patch, please use the Roundup installation
at ‘https://bugs.python.org/’.

You must have a Roundup account to report bugs; this makes it possible
for us to contact you if we have follow-up questions.  It will also
enable Roundup to send you updates as we act on your bug.  If you had
previously used SourceForge to report bugs to Python, you can obtain
your Roundup password through Roundup’s password reset procedure(1).

For more information on how Python is developed, consult the Python
Developer’s Guide(2).

   ---------- Footnotes ----------

   (1) https://bugs.python.org/user?@template=forgotten

   (2) https://devguide.python.org/


File: python.info,  Node: Are there any published articles about Python that I can reference?,  Next: 有沒有關於Python的書,  Prev: How do I submit bug reports and patches for Python?,  Up: 常見資訊

11.1.1.13 Are there any published articles about Python that I can reference?
.............................................................................

It’s probably best to cite your favorite book about Python.

最早討論Python的文章在1991年，但現在來看已經有點過時

     Guido van Rossum and Jelke de Boer, "Interactively Testing Remote
     Servers Using the Python Programming Language", CWI Quarterly,
     Volume 4, Issue 4 (December 1991), Amsterdam, pp 283–303.


File: python.info,  Node: 有沒有關於Python的書,  Next: www python org 這個非營利組織位於哪裡,  Prev: Are there any published articles about Python that I can reference?,  Up: 常見資訊

11.1.1.14 有沒有關於Python的書
..............................

是的已經有很多書出版，可以參考這個連結的參考書目
‘https://wiki.python.org/moin/PythonBooks’

你也可以上網搜尋網路書店關鍵字為"Python"，但不要使用"Monty Python"當作關
鍵字。或者可以搜尋"Python"和"語言"


File: python.info,  Node: www python org 這個非營利組織位於哪裡,  Next: 為什麼要取名為Python,  Prev: 有沒有關於Python的書,  Up: 常見資訊

11.1.1.15 www.python.org 這個非營利組織位於哪裡
...............................................

The Python project’s infrastructure is located all over the world and is
managed by the Python Infrastructure Team.  Details here(1).

   ---------- Footnotes ----------

   (1) http://infra.psf.io


File: python.info,  Node: 為什麼要取名為Python,  Next: 我需要喜歡蒙提·派森的飛行馬戲團這個節目嗎,  Prev: www python org 這個非營利組織位於哪裡,  Up: 常見資訊

11.1.1.16 為什麼要取名為Python
..............................

When he began implementing Python, Guido van Rossum was also reading the
published scripts from "Monty Python’s Flying Circus"(1), a BBC comedy
series from the 1970s.  Van Rossum thought he needed a name that was
short, unique, and slightly mysterious, so he decided to call the
language Python.

   ---------- Footnotes ----------

   (1) https://en.wikipedia.org/wiki/Monty_Python


File: python.info,  Node: 我需要喜歡蒙提·派森的飛行馬戲團這個節目嗎,  Prev: 為什麼要取名為Python,  Up: 常見資訊

11.1.1.17 我需要喜歡蒙提·派森的飛行馬戲團這個節目嗎
...................................................

不需要，但它有幫助 :)


File: python.info,  Node: Python在真實世界,  Prev: 常見資訊,  Up: 常見Python問答集

11.1.2 Python在真實世界
-----------------------

* Menu:

* Python穩定性如何::
* 有多少人使用Python::
* 有沒有任何重要的案子使用Python完成開發::
* 對於程式開發者Python對於未來有什麼期待::
* Is it reasonable to propose incompatible changes to Python?::
* Python對於入門的程式設計者而言是否為好的程式語言::


File: python.info,  Node: Python穩定性如何,  Next: 有多少人使用Python,  Up: Python在真實世界

11.1.2.1 Python穩定性如何
.........................

Very stable.  New, stable releases have been coming out roughly every 6
to 18 months since 1991, and this seems likely to continue.  As of
version 3.9, Python will have a major new release every 12 months ( PEP
602(1)).

The developers issue "bugfix" releases of older versions, so the
stability of existing releases gradually improves.  Bugfix releases,
indicated by a third component of the version number (e.g.  3.5.3,
3.6.2), are managed for stability; only fixes for known problems are
included in a bugfix release, and it’s guaranteed that interfaces will
remain the same throughout a series of bugfix releases.

The latest stable releases can always be found on the Python download
page(2).  There are two production-ready versions of Python: 2.x and
3.x.  The recommended version is 3.x, which is supported by most widely
used libraries.  Although 2.x is still widely used, it will not be
maintained after January 1, 2020(3).

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0602

   (2) https://www.python.org/downloads/

   (3) https://www.python.org/dev/peps/pep-0373/


File: python.info,  Node: 有多少人使用Python,  Next: 有沒有任何重要的案子使用Python完成開發,  Prev: Python穩定性如何,  Up: Python在真實世界

11.1.2.2 有多少人使用Python
...........................

There are probably millions of users, though it’s difficult to obtain an
exact count.

Python is available for free download, so there are no sales figures,
and it’s available from many different sites and packaged with many
Linux distributions, so download statistics don’t tell the whole story
either.

The comp.lang.python newsgroup is very active, but not all Python users
post to the group or even read it.


File: python.info,  Node: 有沒有任何重要的案子使用Python完成開發,  Next: 對於程式開發者Python對於未來有什麼期待,  Prev: 有多少人使用Python,  Up: Python在真實世界

11.1.2.3 有沒有任何重要的案子使用Python完成開發
...............................................

See ‘https://www.python.org/about/success’ for a list of projects that
use Python.  Consulting the proceedings for past Python conferences(1)
will reveal contributions from many different companies and
organizations.

High-profile Python projects include the Mailman mailing list manager(2)
and the Zope application server(3).  Several Linux distributions, most
notably Red Hat(4), have written part or all of their installer and
system administration software in Python.  Companies that use Python
internally include Google, Yahoo, and Lucasfilm Ltd.

   ---------- Footnotes ----------

   (1) https://www.python.org/community/workshops/

   (2) http://www.list.org

   (3) http://www.zope.org

   (4) https://www.redhat.com


File: python.info,  Node: 對於程式開發者Python對於未來有什麼期待,  Next: Is it reasonable to propose incompatible changes to Python?,  Prev: 有沒有任何重要的案子使用Python完成開發,  Up: Python在真實世界

11.1.2.4 對於程式開發者Python對於未來有什麼期待
...............................................

See ‘https://www.python.org/dev/peps/’ for the Python Enhancement
Proposals (PEPs).  PEPs are design documents describing a suggested new
feature for Python, providing a concise technical specification and a
rationale.  Look for a PEP titled "Python X.Y Release Schedule", where
X.Y is a version that hasn’t been publicly released yet.

New development is discussed on the python-dev mailing list(1).

   ---------- Footnotes ----------

   (1) https://mail.python.org/mailman/listinfo/python-dev/


File: python.info,  Node: Is it reasonable to propose incompatible changes to Python?,  Next: Python對於入門的程式設計者而言是否為好的程式語言,  Prev: 對於程式開發者Python對於未來有什麼期待,  Up: Python在真實世界

11.1.2.5 Is it reasonable to propose incompatible changes to Python?
....................................................................

In general, no.  There are already millions of lines of Python code
around the world, so any change in the language that invalidates more
than a very small fraction of existing programs has to be frowned upon.
Even if you can provide a conversion program, there’s still the problem
of updating all documentation; many books have been written about
Python, and we don’t want to invalidate them all at a single stroke.

Providing a gradual upgrade path is necessary if a feature has to be
changed.  PEP 5(1) describes the procedure followed for introducing
backward-incompatible changes while minimizing disruption for users.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0005


File: python.info,  Node: Python對於入門的程式設計者而言是否為好的程式語言,  Prev: Is it reasonable to propose incompatible changes to Python?,  Up: Python在真實世界

11.1.2.6 Python對於入門的程式設計者而言是否為好的程式語言
.........................................................

是的

It is still common to start students with a procedural and statically
typed language such as Pascal, C, or a subset of C++ or Java.  Students
may be better served by learning Python as their first language.  Python
has a very simple and consistent syntax and a large standard library
and, most importantly, using Python in a beginning programming course
lets students concentrate on important programming skills such as
problem decomposition and data type design.  With Python, students can
be quickly introduced to basic concepts such as loops and procedures.
They can probably even work with user-defined objects in their very
first course.

For a student who has never programmed before, using a statically typed
language seems unnatural.  It presents additional complexity that the
student must master and slows the pace of the course.  The students are
trying to learn to think like a computer, decompose problems, design
consistent interfaces, and encapsulate data.  While learning to use a
statically typed language is important in the long term, it is not
necessarily the best topic to address in the students’ first programming
course.

Many other aspects of Python make it a good first language.  Like Java,
Python has a large standard library so that students can be assigned
programming projects very early in the course that `do' something.
Assignments aren’t restricted to the standard four-function calculator
and check balancing programs.  By using the standard library, students
can gain the satisfaction of working on realistic applications as they
learn the fundamentals of programming.  Using the standard library also
teaches students about code reuse.  Third-party modules such as PyGame
are also helpful in extending the students’ reach.

Python’s interactive interpreter enables students to test language
features while they’re programming.  They can keep a window with the
interpreter running while they enter their program’s source in another
window.  If they can’t remember the methods for a list, they can do
something like this:

     >>> 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]

With the interpreter, documentation is never far from the student as
they are programming.

There are also good IDEs for Python.  IDLE is a cross-platform IDE for
Python that is written in Python using Tkinter.  PythonWin is a
Windows-specific IDE. Emacs users will be happy to know that there is a
very good Python mode for Emacs.  All of these programming environments
provide syntax highlighting, auto-indenting, and access to the
interactive interpreter while coding.  Consult the Python wiki(1) for a
full list of Python editing environments.

If you want to discuss Python’s use in education, you may be interested
in joining the edu-sig mailing list(2).

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/PythonEditors

   (2) https://www.python.org/community/sigs/current/edu-sig


File: python.info,  Node: 程式開發常見問答集,  Next: Design and History FAQ,  Prev: 常見Python問答集,  Up: Python 常見問題

11.2 程式開發常見問答集
=======================

* Menu:

* 常見問題::
* Core Language::
* Numbers and strings::
* Performance: Performance<4>.
* Sequences (Tuples/Lists): Sequences Tuples/Lists.
* Objects::
* Modules: Modules<2>.


File: python.info,  Node: 常見問題,  Next: Core Language,  Up: 程式開發常見問答集

11.2.1 常見問題
---------------

* Menu:

* 是否有可以使用在程式碼階段,具有中斷點,步驟執行等功能的除錯器？: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？.
* Are there tools to help find bugs or perform static analysis?::
* How can I create a stand-alone binary from a Python script?::
* Are there coding standards or a style guide for Python programs?::


File: python.info,  Node: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？,  Next: Are there tools to help find bugs or perform static analysis?,  Up: 常見問題

11.2.1.1 是否有可以使用在程式碼階段,具有中斷點,步驟執行等功能的除錯器？
.......................................................................

有的

Several debuggers for Python are described below, and the built-in
function *note breakpoint(): 2fe. allows you to drop into any of them.

The pdb module is a simple but adequate console-mode debugger for
Python.  It is part of the standard Python library, and is *note
documented in the Library Reference Manual: ca.  You can also write your
own debugger by using the code for pdb as an example.

The IDLE interactive development environment, which is part of the
standard Python distribution (normally available as Tools/scripts/idle),
includes a graphical debugger.

PythonWin is a Python IDE that includes a GUI debugger based on pdb.
The PythonWin debugger colors breakpoints and has quite a few cool
features such as debugging non-PythonWin programs.  PythonWin is
available as part of pywin32(1) project and as a part of the
ActivePython(2) distribution.

Eric(3) is an IDE built on PyQt and the Scintilla editing component.

trepan3k(4) is a gdb-like debugger.

Visual Studio Code(5) is an IDE with debugging tools that integrates
with version-control software.

有數個商業化Python整合化開發工具包含圖形除錯功能。這些包含：

   * Wing IDE(6)

   * Komodo IDE(7)

   * PyCharm(8)

   ---------- Footnotes ----------

   (1) https://github.com/mhammond/pywin32

   (2) https://www.activestate.com/products/python/

   (3) http://eric-ide.python-projects.org/

   (4) https://github.com/rocky/python3-trepan/

   (5) https://code.visualstudio.com/

   (6) https://wingware.com/

   (7) https://www.activestate.com/products/komodo-ide/

   (8) https://www.jetbrains.com/pycharm/


File: python.info,  Node: Are there tools to help find bugs or perform static analysis?,  Next: How can I create a stand-alone binary from a Python script?,  Prev: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？,  Up: 常見問題

11.2.1.2 Are there tools to help find bugs or perform static analysis?
......................................................................

有的

Pylint(1) and Pyflakes(2) do basic checking that will help you catch
bugs sooner.

Static type checkers such as Mypy(3), Pyre(4), and Pytype(5) can check
type hints in Python source code.

   ---------- Footnotes ----------

   (1) https://www.pylint.org/

   (2) https://github.com/PyCQA/pyflakes

   (3) http://mypy-lang.org/

   (4) https://pyre-check.org/

   (5) https://github.com/google/pytype


File: python.info,  Node: How can I create a stand-alone binary from a Python script?,  Next: Are there coding standards or a style guide for Python programs?,  Prev: Are there tools to help find bugs or perform static analysis?,  Up: 常見問題

11.2.1.3 How can I create a stand-alone binary from a Python script?
....................................................................

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’.  It converts Python byte code to C arrays; 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.

Obviously, freeze requires a C compiler.  There are several other
utilities which don’t:

   * py2exe(1) for Windows binaries

   * py2app(2) for Mac OS X binaries

   * cx_Freeze(3) for cross-platform binaries

   ---------- Footnotes ----------

   (1) http://www.py2exe.org/

   (2) https://github.com/ronaldoussoren/py2app

   (3) https://cx-freeze.readthedocs.io/en/latest/


File: python.info,  Node: Are there coding standards or a style guide for Python programs?,  Prev: How can I create a stand-alone binary from a Python script?,  Up: 常見問題

11.2.1.4 Are there coding standards or a style guide for Python programs?
.........................................................................

Yes.  The coding style required for standard library modules is
documented as PEP 8(1).

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0008


File: python.info,  Node: Core Language,  Next: Numbers and strings,  Prev: 常見問題,  Up: 程式開發常見問答集

11.2.2 Core Language
--------------------

* Menu:

* 為什麼當變數有值時我得到錯誤訊息 UnboundLocalError::
* Python 的區域變數和全域變數有什麼規則？::
* Why do lambdas defined in a loop with different values all return the same result?::
* How do I share global variables across modules?::
* 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?::
* What is the difference between arguments and parameters?::
* Why did changing list 'y' also change 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?::
* How do I copy an object in Python?::
* How can I find the methods or attributes of an object?::
* How can my code discover the name of an object?::
* What's up with the comma operator's precedence?::
* Is there an equivalent of C’s "?;" ternary operator?: Is there an equivalent of C's "? " ternary operator?.
* 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: Core Language

11.2.2.1 為什麼當變數有值時我得到錯誤訊息 UnboundLocalError
...........................................................

It can be a surprise to get the UnboundLocalError 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.

In the example above you can access the outer scope variable by
declaring it global:

     >>> 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:
c44. 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: Core Language

11.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: 1249. 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: How do I share global variables across modules?,  Prev: Python 的區域變數和全域變數有什麼規則？,  Up: Core Language

11.2.2.3 Why do lambdas defined in a loop with different values all return the same result?
...........................................................................................

Assume you use a for loop to define a few different lambdas (or even
plain functions), e.g.:

     >>> 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

Note that this behaviour is not peculiar to lambdas, but applies to
regular functions too.


File: python.info,  Node: How do I share global variables across modules?,  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: Core Language

11.2.2.4 How do I share global variables across modules?
........................................................

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: How do I share global variables across modules?,  Up: Core Language

11.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. standard library modules – e.g.  ‘sys’, ‘os’, ‘getopt’, ‘re’

  2. third-party library modules (anything installed in Python’s
     site-packages directory) – e.g.  mx.DateTime, ZODB, PIL.Image, etc.

  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: f2b.


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: Core Language

11.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={}):
         ...

but:

     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: What is the difference between arguments and parameters?,  Prev: Why are default values shared between objects?,  Up: Core Language

11.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: What is the difference between arguments and parameters?,  Next: Why did changing list 'y' also change list 'x'?,  Prev: How can I pass optional or keyword parameters from one function to another?,  Up: Core Language

11.2.2.8 What is the difference between arguments and parameters?
.................................................................

*note Parameters: 1530. are defined by the names that appear in a
function definition, whereas *note arguments: 1528. are the values
actually passed to a function when calling it.  Parameters define what
types of arguments a function can accept.  For example, given the
function definition:

     def func(foo, bar=None, **kwargs):
         pass

`foo', `bar' and `kwargs' are parameters of ‘func’.  However, when
calling ‘func’, for example:

     func(42, bar=314, extra=somevar)

the values ‘42’, ‘314’, and ‘somevar’ are arguments.


File: python.info,  Node: Why did changing list 'y' also change list 'x'?,  Next: How do I write a function with output parameters call by reference ?,  Prev: What is the difference between arguments and parameters?,  Up: Core Language

11.2.2.9 Why did changing list ’y’ also change list ’x’?
........................................................

If you wrote code like:

     >>> x = []
     >>> y = x
     >>> y.append(10)
     >>> y
     [10]
     >>> x
     [10]

you might be wondering why appending an element to ‘y’ changed ‘x’ too.

There are two factors that produce this result:

  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. Lists are *note mutable: 122f, which means that you can change
     their content.

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: 1227, 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 ‘sorted(y)’) 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).

In other words:

   * If we have a mutable object (*note list: 263, *note dict: 1b9,
     *note set: b74, 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: 335, *note int: 185,
     *note tuple: 483, 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: ebf. operator, or the built-in function *note
id(): d8b.


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: Why did changing list 'y' also change list 'x'?,  Up: Core Language

11.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. By returning a tuple of the results:

          >>> 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: How do I copy an object in Python?,  Prev: How do I write a function with output parameters call by reference ?,  Up: Core Language

11.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

Or using a callable object:

     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)

Object can encapsulate state for several methods:

     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

Here ‘inc()’, ‘dec()’ and ‘reset()’ act like functions which share the
same counting variable.


File: python.info,  Node: How do I copy an object in Python?,  Next: How can I find the methods or attributes of an object?,  Prev: How do you make a higher order function in Python?,  Up: Core Language

11.2.2.12 How do I copy an object in Python?
............................................

In general, try *note copy.copy(): 3d0. or *note copy.deepcopy(): 3d1.
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(): 44b. method:

     newdict = olddict.copy()

Sequences can be copied by slicing:

     new_l = l[:]


File: python.info,  Node: How can I find the methods or attributes of an object?,  Next: How can my code discover the name of an object?,  Prev: How do I copy an object in Python?,  Up: Core Language

11.2.2.13 How can I find the methods or attributes of an object?
................................................................

For an instance x of a user-defined class, ‘dir(x)’ returns an
alphabetized list of the names containing the instance attributes and
methods and attributes defined by its class.


File: python.info,  Node: How can my code discover the name of an object?,  Next: What's up with the comma operator's precedence?,  Prev: How can I find the methods or attributes of an object?,  Up: Core Language

11.2.2.14 How can my code discover the name of an object?
.........................................................

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.

In comp.lang.python, Fredrik Lundh once gave an excellent analogy in
answer to this question:

     The same way as you get the name of that cat you found on your
     porch: the cat (object) itself cannot tell you its name, and it
     doesn’t really care – so the only way to find out what it’s called
     is to ask all your neighbours (namespaces) if it’s their cat
     (object)...

     ....and don’t be surprised if you’ll find that it’s known by many
     names, or no name at all!


File: python.info,  Node: What's up with the comma operator's precedence?,  Next: Is there an equivalent of C's "? " ternary operator?,  Prev: How can my code discover the name of an object?,  Up: Core Language

11.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"

not:

     "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: Is there an equivalent of C's "? " ternary operator?,  Next: Is it possible to write obfuscated one-liners in Python?,  Prev: What's up with the comma operator's precedence?,  Up: Core Language

11.2.2.16 Is there an equivalent of C’s "?:" ternary operator?
..............................................................

Yes, there is.  The syntax is as follows:

     [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: Is there an equivalent of C's "? " ternary operator?,  Up: Core Language

11.2.2.17 Is it possible to write obfuscated one-liners in Python?
..................................................................

Yes.  Usually this is done by nesting *note lambda: c34. within
‘lambda’.  See the following three examples, due to 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+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

Don’t try this at home, kids!


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: Core Language

11.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(): 153. 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(): 153. 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: Numbers and strings,  Next: Performance<4>,  Prev: Core Language,  Up: 程式開發常見問答集

11.2.3 Numbers and strings
--------------------------

* Menu:

* How do I specify hexadecimal and octal integers?::
* Why does -22 // 10 return -3?::
* How do I convert a string to a number?::
* How do I convert a number to a string?::
* 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?.
* What does 'UnicodeDecodeError' or 'UnicodeEncodeError' error mean?::


File: python.info,  Node: How do I specify hexadecimal and octal integers?,  Next: Why does -22 // 10 return -3?,  Up: Numbers and strings

11.2.3.1 How do I specify hexadecimal and octal integers?
.........................................................

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: Why does -22 // 10 return -3?,  Next: How do I convert a string to a number?,  Prev: How do I specify hexadecimal and octal integers?,  Up: Numbers and strings

11.2.3.2 Why does -22 // 10 return -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)

then integer division has to return the floor.  C also requires that
identity to hold, and then compilers that truncate ‘i // j’ need to make
‘i % j’ have the same sign as ‘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 convert a string to a number?,  Next: How do I convert a number to a string?,  Prev: Why does -22 // 10 return -3?,  Up: Numbers and strings

11.2.3.3 How do I convert a string to a number?
...............................................

For integers, use the built-in *note int(): 185. type constructor, e.g.
‘int('144') == 144’.  Similarly, *note float(): 188. converts to
floating-point, e.g.  ‘float('144') == 144.0’.

By default, these interpret the number as decimal, so that ‘int('0144')
== 144’ and ‘int('0x144')’ raises *note ValueError: 1fc.  ‘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(): b95. if all you need is
to convert strings to numbers.  *note eval(): b95. 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(): b95. 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: How do I convert a number to a string?,  Next: How do I modify a string in place?,  Prev: How do I convert a string to a number?,  Up: Numbers and strings

11.2.3.4 How do I convert a number to a string?
...............................................

To convert, e.g., the number 144 to the string ’144’, use the built-in
type constructor *note str(): 335.  If you want a hexadecimal or octal
representation, use the built-in functions *note hex(): c6b. or *note
oct(): c6a.  For fancy formatting, see the *note Formatted string
literals: 15d. and *note Format String Syntax: d1f. 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: How do I convert a number to a string?,  Up: Numbers and strings

11.2.3.5 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: 832.
object or the *note array: 7. 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('u', s)
     >>> print(a)
     array('u', 'Hello, world')
     >>> a[0] = 'y'
     >>> print(a)
     array('u', '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: Numbers and strings

11.2.3.6 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

   * Use the built-in function *note getattr(): 44d.:

          import foo
          getattr(foo, 'bar')()

     Note that *note getattr(): 44d. 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()

   * Use *note locals(): 45a. or *note eval(): b95. to resolve the
     function name:

          def myFunc():
              print("hello")

          fname = "myFunc"

          f = locals()[fname]
          f()

          f = eval(fname)
          f()

     Note: Using *note eval(): b95. is slow and dangerous.  If you don’t
     have absolute control over the contents of the string, someone
     could pass a string that resulted in an arbitrary function being
     executed.


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: Numbers and strings

11.2.3.7 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: What does 'UnicodeDecodeError' or 'UnicodeEncodeError' error mean?,  Prev: Is there an equivalent to Perl's chomp for removing trailing newlines from strings?,  Up: Numbers and strings

11.2.3.8 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(): 7a6.
method of string objects and then convert decimal strings to numeric
values using *note int(): 185. or *note float(): 188.  ‘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: What does 'UnicodeDecodeError' or 'UnicodeEncodeError' error mean?,  Prev: Is there a scanf or sscanf equivalent?,  Up: Numbers and strings

11.2.3.9 What does ’UnicodeDecodeError’ or ’UnicodeEncodeError’ error mean?
...........................................................................

See the *note Unicode HOWTO: c41.


File: python.info,  Node: Performance<4>,  Next: Sequences Tuples/Lists,  Prev: Numbers and strings,  Up: 程式開發常見問答集

11.2.4 Performance
------------------

* Menu:

* My program is too slow. How do I speed it up?: My program is too slow How do I speed it up?.
* What is the most efficient way to concatenate many strings together?::


File: python.info,  Node: My program is too slow How do I speed it up?,  Next: What is the most efficient way to concatenate many strings together?,  Up: Performance<4>

11.2.4.1 My program is too slow. How do I speed it up?
......................................................

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: 143b.

   * 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: d4.
     module).

   * Writing benchmark scripts will allow you to iterate quickly when
     searching for improvements (see the *note timeit: 10c. 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
     內建型態: 1619. and the *note collections: 1e. 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(): 44a.
     built-in method or the related *note sorted(): 449. function to do
     sorting (and see the *note 如何排序: 1606. 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: 1202. yourself.

也參考
......

The wiki page devoted to performance tips(2).

   ---------- Footnotes ----------

   (1) http://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: My program is too slow How do I speed it up?,  Up: Performance<4>

11.2.4.2 What is the most efficient way to concatenate many strings together?
.............................................................................

*note str: 335. and *note bytes: 336. 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: 335. objects, the recommended idiom is to
place them into a list and call *note str.join(): 1637. 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: 832.)

To accumulate many *note bytes: 336. objects, the recommended idiom is
to extend a *note bytearray: 337. 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: Objects,  Prev: Performance<4>,  Up: 程式開發常見問答集

11.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 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

11.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(): 483. 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

11.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

11.2.5.3 How do I iterate over a sequence in reverse order?
...........................................................

Use the *note reversed(): 18f. 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

11.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: 142e.) 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

11.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

11.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 the Numeric extensions and others 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 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.


File: python.info,  Node: How do I create a multidimensional list?,  Next: How do I apply a method to a sequence of objects?,  Prev: How do you make an array in Python?,  Up: Sequences Tuples/Lists

11.2.5.7 How do I create a multidimensional list?
.................................................

You probably tried to make a multidimensional array like this:

     >>> A = [[None] * 2] * 3

This looks correct if you print it:

     >>> 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) http://www.numpy.org/


File: python.info,  Node: How do I apply a method 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

11.2.5.8 How do I apply a method to a sequence of objects?
..........................................................

Use a list comprehension:

     result = [obj.method() for obj in mylist]


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 to a sequence of objects?,  Up: Sequences Tuples/Lists

11.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 ‘__iadd__’ 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]

This is equivalent to:

     >>> 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

11.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(): 44a. 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

11.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']

An alternative for the last step is:

     >>> result = []
     >>> for p in pairs: result.append(p[1])

If you find this more legible, you might prefer to use this instead of
the final list comprehension.  However, it is almost twice as slow for
long lists.  Why?  First, the ‘append()’ operation has to reallocate
memory, and while it uses some tricks to avoid doing that each time, it
still has to do it occasionally, and that costs quite a bit.  Second,
the expression "result.append" requires an extra attribute lookup, and
third, there’s a speed reduction from having to make all those function
calls.


File: python.info,  Node: Objects,  Next: Modules<2>,  Prev: Sequences Tuples/Lists,  Up: 程式開發常見問答集

11.2.6 Objects
--------------

* Menu:

* What is a class?::
* What is a 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 overrides 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?.


File: python.info,  Node: What is a class?,  Next: What is a method?,  Up: Objects

11.2.6.1 What is a 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: What is a method?,  Next: What is self?,  Prev: What is a class?,  Up: Objects

11.2.6.2 What is a 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: What is a method?,  Up: Objects

11.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)’.

See also *note Why must ’self’ be used explicitly in method definitions
and calls?: 4276.


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: Objects

11.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 ‘isinstance(obj, cls)’.  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 most programs do not use *note isinstance(): 454. 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 overrides it?,  Prev: How do I check if an object is an instance of a given class or of a subclass of it?,  Up: Objects

11.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 ‘__getattr__’ method; consult *note the language reference: 143e.
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__(): e31. method too, and it must do so carefully.  The
basic implementation of *note __setattr__(): e31. is roughly equivalent
to the following:

     class X:
         ...
         def __setattr__(self, name, value):
             self.__dict__[name] = value
         ...

Most *note __setattr__(): e31. implementations must modify
‘self.__dict__’ 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 overrides it?,  Next: How can I organize my code to make it easier to change the base class?,  Prev: What is delegation?,  Up: Objects

11.2.6.6 How do I call a method defined in a base class from a derived class that overrides it?
...............................................................................................

Use the built-in *note super(): 4e7. function:

     class Derived(Base):
         def meth(self):
             super(Derived, self).meth()

For version prior to 3.0, you may be using classic classes: For a class
definition such as ‘class Derived(Base): ...’ you can call method
‘meth()’ defined in ‘Base’ (or one of ‘Base’’s base classes) as
‘Base.meth(self, arguments...)’.  Here, ‘Base.meth’ is an unbound
method, so you need to provide the ‘self’ argument.


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 overrides it?,  Up: Objects

11.2.6.7 How can I organize my code to make it easier to change the base class?
...............................................................................

You could define an alias for the base class, assign the real base class
to it before your class definition, and use the alias throughout your
class.  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:

     BaseAlias = <real base class>

     class Derived(BaseAlias):
         def meth(self):
             BaseAlias.meth(self)
             ...


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: Objects

11.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

Static methods are possible:

     class C:
         @staticmethod
         def static(arg1, arg2, arg3):
             # No 'self' parameter!
             ...

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: Objects

11.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.

In C++ you’d write

     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: Objects

11.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.

This doesn’t guarantee privacy: an outside user can still deliberately
access the "_classname__spam" attribute, and private values are visible
in the object’s ‘__dict__’.  Many Python programmers never bother to use
private variable names at all.


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: Objects

11.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 del statement does not necessarily call *note __del__(): 924. – it
simply decrements the object’s reference count, and if this reaches zero
*note __del__(): 924. 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 *note __del__(): 924. 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 *note __del__(): 924.
methods are executed is arbitrary.  You can run *note gc.collect(): 22f.
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 *note __del__(): 924. directly – *note
__del__(): 924. 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:
129. 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 *note __del__(): 924. method raises an exception, a
warning message is printed to *note sys.stderr: 314.


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: Objects

11.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?,  Prev: How do I get a list of all instances of a given class?,  Up: Objects

11.2.6.13 Why does the result of ‘id()’ appear to be not unique?
................................................................

The *note id(): d8b. 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: Modules<2>,  Prev: Objects,  Up: 程式開發常見問答集

11.2.7 Modules
--------------

* Menu:

* How do I create a .pyc file?: How do I create a pyc file?.
* How do I find the current module name?::
* How can I have modules that mutually import each other?::
* __import__(’x.y.z’) returns <module ’x’>; how do I get z?: __import__ 'x y z' returns <module 'x'>; how do I get z?.
* When I edit an imported module and reimport it, the changes don’t show up. Why does this happen?: When I edit an imported module and reimport it the changes don't show up Why does this happen?.


File: python.info,  Node: How do I create a pyc file?,  Next: How do I find the current module name?,  Up: Modules<2>

11.2.7.1 How do I create a .pyc file?
.....................................

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: d3e. 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: d8. and *note compileall: 21. modules.

The *note py_compile: d8. 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: 21. 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://www.python.org/dev/peps/pep-3147


File: python.info,  Node: How do I find the current module name?,  Next: How can I have modules that mutually import each other?,  Prev: How do I create a pyc file?,  Up: Modules<2>

11.2.7.2 How do I find the current module name?
...............................................

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' returns <module 'x'>; how do I get z?,  Prev: How do I find the current module name?,  Up: Modules<2>

11.2.7.3 How can I have modules that mutually import each other?
................................................................

Suppose you have the following modules:

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 is compiled and starts executing

   * foo imports bar

   * Empty globals for bar are created

   * bar is compiled and starts executing

   * bar imports foo (which is a no-op since there already is a module
     named foo)

   * 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.

There are (at least) three possible workarounds for this problem.

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 suggests performing steps in the following order in each
module:

   * exports (globals, functions, and classes that don’t need imported
     base classes)

   * ‘import’ statements

   * active code (including globals that are initialized from imported
     values).

van Rossum doesn’t like this approach much because the imports appear in
a strange place, but it does work.

Matthias Urlichs recommends restructuring your code so that the
recursive import is not necessary in the first place.

These solutions are not mutually exclusive.


File: python.info,  Node: __import__ 'x y z' returns <module 'x'>; how do I get z?,  Next: When I edit an imported module and reimport it the changes don't show up Why does this happen?,  Prev: How can I have modules that mutually import each other?,  Up: Modules<2>

11.2.7.4 __import__(’x.y.z’) returns <module ’x’>; how do I get z?
..................................................................

Consider using the convenience function *note import_module(): b18. from
*note importlib: 9b. instead:

     z = importlib.import_module('x.y.z')


File: python.info,  Node: When I edit an imported module and reimport it the changes don't show up Why does this happen?,  Prev: __import__ 'x y z' returns <module 'x'>; how do I get z?,  Up: Modules<2>

11.2.7.5 When I edit an imported module and reimport it, the changes don’t show up. Why does this happen?
.........................................................................................................

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

The nature of the problem is made clear if you print out the "identity"
of the class objects:

     >>> hex(id(c.__class__))
     '0x7352a0'
     >>> hex(id(cls.C))
     '0x4198d0'


File: python.info,  Node: Design and History FAQ,  Next: 函式庫和擴充功能的常見問題,  Prev: 程式開發常見問答集,  Up: Python 常見問題

11.3 Design and History FAQ
===========================

* Menu:

* Why does Python use indentation for grouping of statements?::
* Why am I getting strange results with simple arithmetic operations?::
* 為何浮點數運算如此不精確?::
* 為何Python字串為不可變動::
* Why must 'self' be used explicitly in method definitions and calls?::
* Why can't I use an assignment in an expression?::
* Why does Python use methods for some functionality (e.g. list.index()) but functions for other (e.g. len(list))?: Why does Python use methods for some functionality e g list index but functions for other e g len list ?.
* Why is join() a string method instead of a list or tuple method?: Why is join a string method instead of a list or tuple method?.
* How fast are exceptions?::
* Why isn't there a switch or case statement in Python?::
* Can't you emulate threads in the interpreter instead of relying on an OS-specific thread implementation?::
* 為何lambda表示式不能包含在敘述內::
* Python可以被編譯成機器語言或C語言或其他種語言嗎?::
* Python如何管理記憶體?::
* 為何CPython不使用更多傳統的垃圾回收機制?::
* 當CPython結束時，為何所有的記憶體不會被釋放?::
* Why are there separate tuple and list data types?::
* How are lists implemented in CPython?::
* How are dictionaries implemented in CPython?::
* Why must dictionary keys be immutable?::
* 為何list.sort()不是回傳排序過的串列?: 為何list sort 不是回傳排序過的串列?.
* How do you specify and enforce an interface spec in Python?::
* 為何沒有goto語法?::
* Why can’t raw strings (r-strings) end with a backslash?: Why can't raw strings r-strings end with a backslash?.
* Why doesn't Python have a "with" statement for attribute assignments?::
* Why are colons required for the if/while/def/class statements?::
* Why does Python allow commas at the end of lists and tuples?::


File: python.info,  Node: Why does Python use indentation for grouping of statements?,  Next: Why am I getting strange results with simple arithmetic operations?,  Up: Design and History FAQ

11.3.1 Why does Python use indentation for grouping of statements?
------------------------------------------------------------------

Guido van Rossum believes that using indentation for grouping is
extremely elegant and contributes a lot to the clarity of the average
Python program.  Most people learn to love this feature after a while.

Since there are no begin/end brackets there cannot be a disagreement
between grouping perceived by the parser and the human reader.
Occasionally C programmers will encounter a fragment of code like this:

     if (x <= y)
             x++;
             y--;
     z++;

Only the ‘x++’ statement is executed if the condition is true, but the
indentation leads you to believe otherwise.  Even experienced C
programmers will sometimes stare at it a long time wondering why ‘y’ is
being decremented even for ‘x > y’.

Because there are no begin/end brackets, Python is much less prone to
coding-style conflicts.  In C there are many different ways to place the
braces.  If you’re used to reading and writing code that uses one style,
you will feel at least slightly uneasy when reading (or being required
to write) another style.

Many coding styles place begin/end brackets on a line by themselves.
This makes programs considerably longer and wastes valuable screen
space, making it harder to get a good overview of a program.  Ideally, a
function should fit on one screen (say, 20–30 lines).  20 lines of
Python can do a lot more work than 20 lines of C. This is not solely due
to the lack of begin/end brackets – the lack of declarations and the
high-level data types are also responsible – but the indentation-based
syntax certainly helps.


File: python.info,  Node: Why am I getting strange results with simple arithmetic operations?,  Next: 為何浮點數運算如此不精確?,  Prev: Why does Python use indentation for grouping of statements?,  Up: Design and History FAQ

11.3.2 Why am I getting strange results with simple arithmetic operations?
--------------------------------------------------------------------------

請見下一個問題。


File: python.info,  Node: 為何浮點數運算如此不精確?,  Next: 為何Python字串為不可變動,  Prev: Why am I getting strange results with simple arithmetic operations?,  Up: Design and History FAQ

11.3.3 為何浮點數運算如此不精確?
--------------------------------

Users are often surprised by results like this:

     >>> 1.2 - 1.0
     0.19999999999999996

and think it is a bug in Python.  It’s not.  This has little to do with
Python, and much more to do with how the underlying platform handles
floating-point numbers.

The *note float: 188. type in CPython uses a C ‘double’ for storage.  A
*note float: 188. object’s value is stored in binary floating-point with
a fixed precision (typically 53 bits) and Python uses C operations,
which in turn rely on the hardware implementation in the processor, to
perform floating-point operations.  This means that as far as
floating-point operations are concerned, Python behaves like many
popular languages including C and Java.

Many numbers that can be written easily in decimal notation cannot be
expressed exactly in binary floating-point.  For example, after:

     >>> x = 1.2

the value stored for ‘x’ is a (very good) approximation to the decimal
value ‘1.2’, but is not exactly equal to it.  On a typical machine, the
actual stored value is:

     1.0011001100110011001100110011001100110011001100110011 (binary)

which is exactly:

     1.1999999999999999555910790149937383830547332763671875 (decimal)

The typical precision of 53 bits provides Python floats with 15–16
decimal digits of accuracy.

For a fuller explanation, please see the *note floating point
arithmetic: 1327. chapter in the Python tutorial.


File: python.info,  Node: 為何Python字串為不可變動,  Next: Why must 'self' be used explicitly in method definitions and calls?,  Prev: 為何浮點數運算如此不精確?,  Up: Design and History FAQ

11.3.4 為何Python字串為不可變動
-------------------------------

有許多優點。

One is performance: knowing that a string is immutable means we can
allocate space for it at creation time, and the storage requirements are
fixed and unchanging.  This is also one of the reasons for the
distinction between tuples and lists.

Another advantage is that strings in Python are considered as
"elemental" as numbers.  No amount of activity will change the value 8
to anything else, and in Python, no amount of activity will change the
string "eight" to anything else.


File: python.info,  Node: Why must 'self' be used explicitly in method definitions and calls?,  Next: Why can't I use an assignment in an expression?,  Prev: 為何Python字串為不可變動,  Up: Design and History FAQ

11.3.5 Why must ’self’ be used explicitly in method definitions and calls?
--------------------------------------------------------------------------

此構想從Modula-3而來。有許多原因可以說是非常實用。

First, it’s more obvious that you are using a method or instance
attribute instead of a local variable.  Reading ‘self.x’ or
‘self.meth()’ makes it absolutely clear that an instance variable or
method is used even if you don’t know the class definition by heart.  In
C++, you can sort of tell by the lack of a local variable declaration
(assuming globals are rare or easily recognizable) – but in Python,
there are no local variable declarations, so you’d have to look up the
class definition to be sure.  Some C++ and Java coding standards call
for instance attributes to have an ‘m_’ prefix, so this explicitness is
still useful in those languages, too.

Second, it means that no special syntax is necessary if you want to
explicitly reference or call the method from a particular class.  In
C++, if you want to use a method from a base class which is overridden
in a derived class, you have to use the ‘::’ operator – in Python you
can write ‘baseclass.methodname(self, <argument list>)’.  This is
particularly useful for *note __init__(): d63. methods, and in general
in cases where a derived class method wants to extend the base class
method of the same name and thus has to call the base class method
somehow.

Finally, for instance variables it solves a syntactic problem with
assignment: since local variables in Python are (by definition!)  those
variables to which a value is assigned in a function body (and that
aren’t explicitly declared global), there has to be some way to tell the
interpreter that an assignment was meant to assign to an instance
variable instead of to a local variable, and it should preferably be
syntactic (for efficiency reasons).  C++ does this through declarations,
but Python doesn’t have declarations and it would be a pity having to
introduce them just for this purpose.  Using the explicit ‘self.var’
solves this nicely.  Similarly, for using instance variables, having to
write ‘self.var’ means that references to unqualified names inside a
method don’t have to search the instance’s directories.  To put it
another way, local variables and instance variables live in two
different namespaces, and you need to tell Python which namespace to
use.


File: python.info,  Node: Why can't I use an assignment in an expression?,  Next: Why does Python use methods for some functionality e g list index but functions for other e g len list ?,  Prev: Why must 'self' be used explicitly in method definitions and calls?,  Up: Design and History FAQ

11.3.6 Why can’t I use an assignment in an expression?
------------------------------------------------------

Starting in Python 3.8, you can!

Assignment expressions using the walrus operator ‘:=’ assign a variable
in an expression:

     while chunk := fp.read(200):
        print(chunk)

See PEP 572(1) for more information.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0572


File: python.info,  Node: Why does Python use methods for some functionality e g list index but functions for other e g len list ?,  Next: Why is join a string method instead of a list or tuple method?,  Prev: Why can't I use an assignment in an expression?,  Up: Design and History FAQ

11.3.7 Why does Python use methods for some functionality (e.g. list.index()) but functions for other (e.g. len(list))?
-----------------------------------------------------------------------------------------------------------------------

As Guido said:

     (a) For some operations, prefix notation just reads better than
     postfix – prefix (and infix!)  operations have a long tradition in
     mathematics which likes notations where the visuals help the
     mathematician thinking about a problem.  Compare the easy with
     which we rewrite a formula like x*(a+b) into x*a + x*b to the
     clumsiness of doing the same thing using a raw OO notation.

     (b) When I read code that says len(x) I `know' that it is asking
     for the length of something.  This tells me two things: the result
     is an integer, and the argument is some kind of container.  To the
     contrary, when I read x.len(), I have to already know that x is
     some kind of container implementing an interface or inheriting from
     a class that has a standard len().  Witness the confusion we
     occasionally have when a class that is not implementing a mapping
     has a get() or keys() method, or something that isn’t a file has a
     write() method.

— ‘https://mail.python.org/pipermail/python-3000/2006-November/004643.html’


File: python.info,  Node: Why is join a string method instead of a list or tuple method?,  Next: How fast are exceptions?,  Prev: Why does Python use methods for some functionality e g list index but functions for other e g len list ?,  Up: Design and History FAQ

11.3.8 Why is join() a string method instead of a list or tuple method?
-----------------------------------------------------------------------

Strings became much more like other standard types starting in Python
1.6, when methods were added which give the same functionality that has
always been available using the functions of the string module.  Most of
these new methods have been widely accepted, but the one which appears
to make some programmers feel uncomfortable is:

     ", ".join(['1', '2', '4', '8', '16'])

which gives the result:

     "1, 2, 4, 8, 16"

There are two common arguments against this usage.

The first runs along the lines of: "It looks really ugly using a method
of a string literal (string constant)", to which the answer is that it
might, but a string literal is just a fixed value.  If the methods are
to be allowed on names bound to strings there is no logical reason to
make them unavailable on literals.

The second objection is typically cast as: "I am really telling a
sequence to join its members together with a string constant".  Sadly,
you aren’t.  For some reason there seems to be much less difficulty with
having *note split(): 7a6. as a string method, since in that case it is
easy to see that

     "1, 2, 4, 8, 16".split(", ")

is an instruction to a string literal to return the substrings delimited
by the given separator (or, by default, arbitrary runs of white space).

*note join(): 1637. is a string method because in using it you are
telling the separator string to iterate over a sequence of strings and
insert itself between adjacent elements.  This method can be used with
any argument which obeys the rules for sequence objects, including any
new classes you might define yourself.  Similar methods exist for bytes
and bytearray objects.


File: python.info,  Node: How fast are exceptions?,  Next: Why isn't there a switch or case statement in Python?,  Prev: Why is join a string method instead of a list or tuple method?,  Up: Design and History FAQ

11.3.9 How fast are exceptions?
-------------------------------

A try/except block is extremely efficient if no exceptions are raised.
Actually catching an exception is expensive.  In versions of Python
prior to 2.0 it was common to use this idiom:

     try:
         value = mydict[key]
     except KeyError:
         mydict[key] = getvalue(key)
         value = mydict[key]

This only made sense when you expected the dict to have the key almost
all the time.  If that wasn’t the case, you coded it like this:

     if key in mydict:
         value = mydict[key]
     else:
         value = mydict[key] = getvalue(key)

For this specific case, you could also use ‘value = dict.setdefault(key,
getvalue(key))’, but only if the ‘getvalue()’ call is cheap enough
because it is evaluated in all cases.


File: python.info,  Node: Why isn't there a switch or case statement in Python?,  Next: Can't you emulate threads in the interpreter instead of relying on an OS-specific thread implementation?,  Prev: How fast are exceptions?,  Up: Design and History FAQ

11.3.10 Why isn’t there a switch or case statement in Python?
-------------------------------------------------------------

You can do this easily enough with a sequence of ‘if... elif... elif...
else’.  There have been some proposals for switch statement syntax, but
there is no consensus (yet) on whether and how to do range tests.  See
PEP 275(1) for complete details and the current status.

For cases where you need to choose from a very large number of
possibilities, you can create a dictionary mapping case values to
functions to call.  For example:

     def function_1(...):
         ...

     functions = {'a': function_1,
                  'b': function_2,
                  'c': self.method_1, ...}

     func = functions[value]
     func()

For calling methods on objects, you can simplify yet further by using
the *note getattr(): 44d. built-in to retrieve methods with a particular
name:

     def visit_a(self, ...):
         ...
     ...

     def dispatch(self, value):
         method_name = 'visit_' + str(value)
         method = getattr(self, method_name)
         method()

It’s suggested that you use a prefix for the method names, such as
‘visit_’ in this example.  Without such a prefix, if values are coming
from an untrusted source, an attacker would be able to call any method
on your object.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0275


File: python.info,  Node: Can't you emulate threads in the interpreter instead of relying on an OS-specific thread implementation?,  Next: 為何lambda表示式不能包含在敘述內,  Prev: Why isn't there a switch or case statement in Python?,  Up: Design and History FAQ

11.3.11 Can’t you emulate threads in the interpreter instead of relying on an OS-specific thread implementation?
----------------------------------------------------------------------------------------------------------------

Answer 1: Unfortunately, the interpreter pushes at least one C stack
frame for each Python stack frame.  Also, extensions can call back into
Python at almost random moments.  Therefore, a complete threads
implementation requires thread support for C.

Answer 2: Fortunately, there is Stackless Python(1), which has a
completely redesigned interpreter loop that avoids the C stack.

   ---------- Footnotes ----------

   (1) https://github.com/stackless-dev/stackless/wiki


File: python.info,  Node: 為何lambda表示式不能包含在敘述內,  Next: Python可以被編譯成機器語言或C語言或其他種語言嗎?,  Prev: Can't you emulate threads in the interpreter instead of relying on an OS-specific thread implementation?,  Up: Design and History FAQ

11.3.12 為何lambda表示式不能包含在敘述內
----------------------------------------

Python lambda expressions cannot contain statements because Python’s
syntactic framework can’t handle statements nested inside expressions.
However, in Python, this is not a serious problem.  Unlike lambda forms
in other languages, where they add functionality, Python lambdas are
only a shorthand notation if you’re too lazy to define a function.

Functions are already first class objects in Python, and can be declared
in a local scope.  Therefore the only advantage of using a lambda
instead of a locally-defined function is that you don’t need to invent a
name for the function – but that’s just a local variable to which the
function object (which is exactly the same type of object that a lambda
expression yields) is assigned!


File: python.info,  Node: Python可以被編譯成機器語言或C語言或其他種語言嗎?,  Next: Python如何管理記憶體?,  Prev: 為何lambda表示式不能包含在敘述內,  Up: Design and History FAQ

11.3.13 Python可以被編譯成機器語言或C語言或其他種語言嗎?
--------------------------------------------------------

Cython(1) compiles a modified version of Python with optional
annotations into C extensions.  Nuitka(2) is an up-and-coming compiler
of Python into C++ code, aiming to support the full Python language.
For compiling to Java you can consider VOC(3).

   ---------- Footnotes ----------

   (1) http://cython.org/

   (2) http://www.nuitka.net/

   (3) https://voc.readthedocs.io


File: python.info,  Node: Python如何管理記憶體?,  Next: 為何CPython不使用更多傳統的垃圾回收機制?,  Prev: Python可以被編譯成機器語言或C語言或其他種語言嗎?,  Up: Design and History FAQ

11.3.14 Python如何管理記憶體?
-----------------------------

The details of Python memory management depend on the implementation.
The standard implementation of Python, *note CPython: 143b, uses
reference counting to detect inaccessible objects, and another mechanism
to collect reference cycles, periodically executing a cycle detection
algorithm which looks for inaccessible cycles and deletes the objects
involved.  The *note gc: 86. module provides functions to perform a
garbage collection, obtain debugging statistics, and tune the
collector’s parameters.

Other implementations (such as Jython(1) or PyPy(2)), however, can rely
on a different mechanism such as a full-blown garbage collector.  This
difference can cause some subtle porting problems if your Python code
depends on the behavior of the reference counting implementation.

In some Python implementations, the following code (which is fine in
CPython) will probably run out of file descriptors:

     for file in very_long_list_of_files:
         f = open(file)
         c = f.read(1)

Indeed, using CPython’s reference counting and destructor scheme, each
new assignment to `f' closes the previous file.  With a traditional GC,
however, those file objects will only get collected (and closed) at
varying and possibly long intervals.

If you want to write code that will work with any Python implementation,
you should explicitly close the file or use the *note with: 6ee.
statement; this will work regardless of memory management scheme:

     for file in very_long_list_of_files:
         with open(file) as f:
             c = f.read(1)

   ---------- Footnotes ----------

   (1) http://www.jython.org

   (2) http://www.pypy.org


File: python.info,  Node: 為何CPython不使用更多傳統的垃圾回收機制?,  Next: 當CPython結束時，為何所有的記憶體不會被釋放?,  Prev: Python如何管理記憶體?,  Up: Design and History FAQ

11.3.15 為何CPython不使用更多傳統的垃圾回收機制?
------------------------------------------------

For one thing, this is not a C standard feature and hence it’s not
portable.  (Yes, we know about the Boehm GC library.  It has bits of
assembler code for `most' common platforms, not for all of them, and
although it is mostly transparent, it isn’t completely transparent;
patches are required to get Python to work with it.)

Traditional GC also becomes a problem when Python is embedded into other
applications.  While in a standalone Python it’s fine to replace the
standard malloc() and free() with versions provided by the GC library,
an application embedding Python may want to have its `own' substitute
for malloc() and free(), and may not want Python’s.  Right now, CPython
works with anything that implements malloc() and free() properly.


File: python.info,  Node: 當CPython結束時，為何所有的記憶體不會被釋放?,  Next: Why are there separate tuple and list data types?,  Prev: 為何CPython不使用更多傳統的垃圾回收機制?,  Up: Design and History FAQ

11.3.16 當CPython結束時，為何所有的記憶體不會被釋放?
----------------------------------------------------

Objects referenced from the global namespaces of Python modules are not
always deallocated when Python exits.  This may happen if there are
circular references.  There are also certain bits of memory that are
allocated by the C library that are impossible to free (e.g.  a tool
like Purify will complain about these).  Python is, however, aggressive
about cleaning up memory on exit and does try to destroy every single
object.

If you want to force Python to delete certain things on deallocation use
the *note atexit: c. module to run a function that will force those
deletions.


File: python.info,  Node: Why are there separate tuple and list data types?,  Next: How are lists implemented in CPython?,  Prev: 當CPython結束時，為何所有的記憶體不會被釋放?,  Up: Design and History FAQ

11.3.17 Why are there separate tuple and list data types?
---------------------------------------------------------

Lists and tuples, while similar in many respects, are generally used in
fundamentally different ways.  Tuples can be thought of as being similar
to Pascal records or C structs; they’re small collections of related
data which may be of different types which are operated on as a group.
For example, a Cartesian coordinate is appropriately represented as a
tuple of two or three numbers.

Lists, on the other hand, are more like arrays in other languages.  They
tend to hold a varying number of objects all of which have the same type
and which are operated on one-by-one.  For example, ‘os.listdir('.')’
returns a list of strings representing the files in the current
directory.  Functions which operate on this output would generally not
break if you added another file or two to the directory.

Tuples are immutable, meaning that once a tuple has been created, you
can’t replace any of its elements with a new value.  Lists are mutable,
meaning that you can always change a list’s elements.  Only immutable
elements can be used as dictionary keys, and hence only tuples and not
lists can be used as keys.


File: python.info,  Node: How are lists implemented in CPython?,  Next: How are dictionaries implemented in CPython?,  Prev: Why are there separate tuple and list data types?,  Up: Design and History FAQ

11.3.18 How are lists implemented in CPython?
---------------------------------------------

CPython’s lists are really variable-length arrays, not Lisp-style linked
lists.  The implementation uses a contiguous array of references to
other objects, and keeps a pointer to this array and the array’s length
in a list head structure.

This makes indexing a list ‘a[i]’ an operation whose cost is independent
of the size of the list or the value of the index.

When items are appended or inserted, the array of references is resized.
Some cleverness is applied to improve the performance of appending items
repeatedly; when the array must be grown, some extra space is allocated
so the next few times don’t require an actual resize.


File: python.info,  Node: How are dictionaries implemented in CPython?,  Next: Why must dictionary keys be immutable?,  Prev: How are lists implemented in CPython?,  Up: Design and History FAQ

11.3.19 How are dictionaries implemented in CPython?
----------------------------------------------------

CPython’s dictionaries are implemented as resizable hash tables.
Compared to B-trees, this gives better performance for lookup (the most
common operation by far) under most circumstances, and the
implementation is simpler.

Dictionaries work by computing a hash code for each key stored in the
dictionary using the *note hash(): 9c9. built-in function.  The hash
code varies widely depending on the key and a per-process seed; for
example, "Python" could hash to -539294296 while "python", a string that
differs by a single bit, could hash to 1142331976.  The hash code is
then used to calculate a location in an internal array where the value
will be stored.  Assuming that you’re storing keys that all have
different hash values, this means that dictionaries take constant time –
O(1), in Big-O notation – to retrieve a key.


File: python.info,  Node: Why must dictionary keys be immutable?,  Next: 為何list sort 不是回傳排序過的串列?,  Prev: How are dictionaries implemented in CPython?,  Up: Design and History FAQ

11.3.20 Why must dictionary keys be immutable?
----------------------------------------------

The hash table implementation of dictionaries uses a hash value
calculated from the key value to find the key.  If the key were a
mutable object, its value could change, and thus its hash could also
change.  But since whoever changes the key object can’t tell that it was
being used as a dictionary key, it can’t move the entry around in the
dictionary.  Then, when you try to look up the same object in the
dictionary it won’t be found because its hash value is different.  If
you tried to look up the old value it wouldn’t be found either, because
the value of the object found in that hash bin would be different.

If you want a dictionary indexed with a list, simply convert the list to
a tuple first; the function ‘tuple(L)’ creates a tuple with the same
entries as the list ‘L’.  Tuples are immutable and can therefore be used
as dictionary keys.

Some unacceptable solutions that have been proposed:

   - Hash lists by their address (object ID). This doesn’t work because
     if you construct a new list with the same value it won’t be found;
     e.g.:

          mydict = {[1, 2]: '12'}
          print(mydict[[1, 2]])

     would raise a *note KeyError: 2c8. exception because the id of the
     ‘[1, 2]’ used in the second line differs from that in the first
     line.  In other words, dictionary keys should be compared using
     ‘==’, not using *note is: ebf.

   - Make a copy when using a list as a key.  This doesn’t work because
     the list, being a mutable object, could contain a reference to
     itself, and then the copying code would run into an infinite loop.

   - Allow lists as keys but tell the user not to modify them.  This
     would allow a class of hard-to-track bugs in programs when you
     forgot or modified a list by accident.  It also invalidates an
     important invariant of dictionaries: every value in ‘d.keys()’ is
     usable as a key of the dictionary.

   - Mark lists as read-only once they are used as a dictionary key.
     The problem is that it’s not just the top-level object that could
     change its value; you could use a tuple containing a list as a key.
     Entering anything as a key into a dictionary would require marking
     all objects reachable from there as read-only – and again,
     self-referential objects could cause an infinite loop.

There is a trick to get around this if you need to, but use it at your
own risk: You can wrap a mutable structure inside a class instance which
has both a *note __eq__(): 344. and a *note __hash__(): 345. method.
You must then make sure that the hash value for all such wrapper objects
that reside in a dictionary (or other hash based structure), remain
fixed while the object is in the dictionary (or other structure).

     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

Note that the hash computation is complicated by the possibility that
some members of the list may be unhashable and also by the possibility
of arithmetic overflow.

Furthermore it must always be the case that if ‘o1 == o2’ (ie
‘o1.__eq__(o2) is True’) then ‘hash(o1) == hash(o2)’ (ie, ‘o1.__hash__()
== o2.__hash__()’), regardless of whether the object is in a dictionary
or not.  If you fail to meet these restrictions dictionaries and other
hash based structures will misbehave.

In the case of ListWrapper, whenever the wrapper object is in a
dictionary the wrapped list must not change to avoid anomalies.  Don’t
do this unless you are prepared to think hard about the requirements and
the consequences of not meeting them correctly.  Consider yourself
warned.


File: python.info,  Node: 為何list sort 不是回傳排序過的串列?,  Next: How do you specify and enforce an interface spec in Python?,  Prev: Why must dictionary keys be immutable?,  Up: Design and History FAQ

11.3.21 為何list.sort()不是回傳排序過的串列?
--------------------------------------------

In situations where performance matters, making a copy of the list just
to sort it would be wasteful.  Therefore, *note list.sort(): 44a. sorts
the list in place.  In order to remind you of that fact, it does not
return the sorted list.  This way, you won’t be fooled into accidentally
overwriting a list when you need a sorted copy but also need to keep the
unsorted version around.

If you want to return a new list, use the built-in *note sorted(): 449.
function instead.  This function creates a new list from a provided
iterable, sorts it and returns it.  For example, here’s how to iterate
over the keys of a dictionary in sorted order:

     for key in sorted(mydict):
         ...  # do whatever with mydict[key]...


File: python.info,  Node: How do you specify and enforce an interface spec in Python?,  Next: 為何沒有goto語法?,  Prev: 為何list sort 不是回傳排序過的串列?,  Up: Design and History FAQ

11.3.22 How do you specify and enforce an interface spec in Python?
-------------------------------------------------------------------

An interface specification for a module as provided by languages such as
C++ and Java describes the prototypes for the methods and functions of
the module.  Many feel that compile-time enforcement of interface
specifications helps in the construction of large programs.

Python 2.6 adds an *note abc: 4. module that lets you define Abstract
Base Classes (ABCs).  You can then use *note isinstance(): 454. and
*note issubclass(): 455. to check whether an instance or a class
implements a particular ABC. The *note collections.abc: 1f. module
defines a set of useful ABCs such as *note Iterable: 1957, *note
Container: 1955, and *note MutableMapping: 9f4.

For Python, many of the advantages of interface specifications can be
obtained by an appropriate test discipline for components.

A good test suite for a module can both provide a regression test and
serve as a module interface specification and a set of examples.  Many
Python modules can be run as a script to provide a simple "self test."
Even modules which use complex external interfaces can often be tested
in isolation using trivial "stub" emulations of the external interface.
The *note doctest: 67. and *note unittest: 11c. modules or third-party
test frameworks can be used to construct exhaustive test suites that
exercise every line of code in a module.

An appropriate testing discipline can help build large complex
applications in Python as well as having interface specifications would.
In fact, it can be better because an interface specification cannot test
certain properties of a program.  For example, the ‘append()’ method is
expected to add new elements to the end of some internal list; an
interface specification cannot test that your ‘append()’ implementation
will actually do this correctly, but it’s trivial to check this property
in a test suite.

Writing test suites is very helpful, and you might want to design your
code with an eye to making it easily tested.  One increasingly popular
technique, test-directed development, calls for writing parts of the
test suite first, before you write any of the actual code.  Of course
Python allows you to be sloppy and not write test cases at all.


File: python.info,  Node: 為何沒有goto語法?,  Next: Why can't raw strings r-strings end with a backslash?,  Prev: How do you specify and enforce an interface spec in Python?,  Up: Design and History FAQ

11.3.23 為何沒有goto語法?
-------------------------

In the 1970s people realized that unrestricted goto could lead to messy
"spaghetti" code that was hard to understand and revise.  In a
high-level language, it is also unneeded as long as there are ways to
branch (in Python, with ‘if’ statements and ‘or’, ‘and’, and ‘if-else’
expressions) and loop (with ‘while’ and ‘for’ statements, possibly
containing ‘continue’ and ‘break’).

One can also use exceptions to provide a "structured goto" that works
even across function calls.  Many feel that exceptions can conveniently
emulate all reasonable uses of the "go" or "goto" constructs of C,
Fortran, and other languages.  For example:

     class label(Exception): pass  # declare a label

     try:
         ...
         if condition: raise label()  # goto label
         ...
     except label:  # where to goto
         pass
     ...

This doesn’t allow you to jump into the middle of a loop, but that’s
usually considered an abuse of goto anyway.  Use sparingly.


File: python.info,  Node: Why can't raw strings r-strings end with a backslash?,  Next: Why doesn't Python have a "with" statement for attribute assignments?,  Prev: 為何沒有goto語法?,  Up: Design and History FAQ

11.3.24 Why can’t raw strings (r-strings) end with a backslash?
---------------------------------------------------------------

More precisely, they can’t end with an odd number of backslashes: the
unpaired backslash at the end escapes the closing quote character,
leaving an unterminated string.

Raw strings were designed to ease creating input for processors (chiefly
regular expression engines) that want to do their own backslash escape
processing.  Such processors consider an unmatched trailing backslash to
be an error anyway, so raw strings disallow that.  In return, they allow
you to pass on the string quote character by escaping it with a
backslash.  These rules work well when r-strings are used for their
intended purpose.

If you’re trying to build Windows pathnames, note that all Windows
system calls accept forward slashes too:

     f = open("/mydir/file.txt")  # works fine!

If you’re trying to build a pathname for a DOS command, try e.g.  one of

     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: Why doesn't Python have a "with" statement for attribute assignments?,  Next: Why are colons required for the if/while/def/class statements?,  Prev: Why can't raw strings r-strings end with a backslash?,  Up: Design and History FAQ

11.3.25 Why doesn’t Python have a "with" statement for attribute assignments?
-----------------------------------------------------------------------------

Python has a ’with’ statement that wraps the execution of a block,
calling code on the entrance and exit from the block.  Some language
have a construct that looks like this:

     with obj:
         a = 1               # equivalent to obj.a = 1
         total = total + 1   # obj.total = obj.total + 1

In Python, such a construct would be ambiguous.

Other languages, such as Object Pascal, Delphi, and C++, use static
types, so it’s possible to know, in an unambiguous way, what member is
being assigned to.  This is the main point of static typing – the
compiler `always' knows the scope of every variable at compile time.

Python uses dynamic types.  It is impossible to know in advance which
attribute will be referenced at runtime.  Member attributes may be added
or removed from objects on the fly.  This makes it impossible to know,
from a simple reading, what attribute is being referenced: a local one,
a global one, or a member attribute?

For instance, take the following incomplete snippet:

     def foo(a):
         with a:
             print(x)

The snippet assumes that "a" must have a member attribute called "x".
However, there is nothing in Python that tells the interpreter this.
What should happen if "a" is, let us say, an integer?  If there is a
global variable named "x", will it be used inside the with block?  As
you see, the dynamic nature of Python makes such choices much harder.

The primary benefit of "with" and similar language features (reduction
of code volume) can, however, easily be achieved in Python by
assignment.  Instead of:

     function(args).mydict[index][index].a = 21
     function(args).mydict[index][index].b = 42
     function(args).mydict[index][index].c = 63

write this:

     ref = function(args).mydict[index][index]
     ref.a = 21
     ref.b = 42
     ref.c = 63

This also has the side-effect of increasing execution speed because name
bindings are resolved at run-time in Python, and the second version only
needs to perform the resolution once.


File: python.info,  Node: Why are colons required for the if/while/def/class statements?,  Next: Why does Python allow commas at the end of lists and tuples?,  Prev: Why doesn't Python have a "with" statement for attribute assignments?,  Up: Design and History FAQ

11.3.26 Why are colons required for the if/while/def/class statements?
----------------------------------------------------------------------

The colon is required primarily to enhance readability (one of the
results of the experimental ABC language).  Consider this:

     if a == b
         print(a)

versus

     if a == b:
         print(a)

Notice how the second one is slightly easier to read.  Notice further
how a colon sets off the example in this FAQ answer; it’s a standard
usage in English.

Another minor reason is that the colon makes it easier for editors with
syntax highlighting; they can look for colons to decide when indentation
needs to be increased instead of having to do a more elaborate parsing
of the program text.


File: python.info,  Node: Why does Python allow commas at the end of lists and tuples?,  Prev: Why are colons required for the if/while/def/class statements?,  Up: Design and History FAQ

11.3.27 Why does Python allow commas at the end of lists and tuples?
--------------------------------------------------------------------

Python lets you add a trailing comma at the end of lists, tuples, and
dictionaries:

     [1, 2, 3,]
     ('a', 'b', 'c',)
     d = {
         "A": [1, 5],
         "B": [6, 7],  # last trailing comma is optional but good style
     }

這有許多原因可被允許。

When you have a literal value for a list, tuple, or dictionary spread
across multiple lines, it’s easier to add more elements because you
don’t have to remember to add a comma to the previous line.  The lines
can also be reordered without creating a syntax error.

Accidentally omitting the comma can lead to errors that are hard to
diagnose.  For example:

     x = [
       "fee",
       "fie"
       "foo",
       "fum"
     ]

This list looks like it has four elements, but it actually contains
three: "fee", "fiefoo" and "fum".  Always adding the comma avoids this
source of error.

Allowing the trailing comma may also make programmatic code generation
easier.


File: python.info,  Node: 函式庫和擴充功能的常見問題,  Next: Extending/Embedding FAQ,  Prev: Design and History FAQ,  Up: Python 常見問題

11.4 函式庫和擴充功能的常見問題
===============================

* Menu:

* 常見函式問題::
* 一般性的工作::
* Threads::
* Input and Output::
* Network/Internet Programming::
* Databases::
* Mathematics and Numerics::


File: python.info,  Node: 常見函式問題,  Next: 一般性的工作,  Up: 函式庫和擴充功能的常見問題

11.4.1 常見函式問題
-------------------

* Menu:

* How do I find a module or application to perform task X?::
* 哪裡可以找到math.py (socket.py, regex.py, 等...) 原始檔案: 哪裡可以找到math py socket py regex py 等 原始檔案.
* 我如何使Python script 執行在Unix ?::
* Is there a curses/termcap package for Python?::
* Is there an equivalent to C’s onexit() in Python?: Is there an equivalent to C's onexit in Python?.
* Why don't my signal handlers work?::


File: python.info,  Node: How do I find a module or application to perform task X?,  Next: 哪裡可以找到math py socket py regex py 等 原始檔案,  Up: 常見函式問題

11.4.1.1 How do I find a module or application to perform task X?
.................................................................

Check *note the Library Reference: 1200. 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: How do I find a module or application to perform task X?,  Up: 常見函式問題

11.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. modules written in C and dynamically loaded (.dll, .pyd, .so, .sl,
     etc);

  3. modules written in C and linked with the interpreter; to get a list
     of these, type:

          import sys
          print(sys.builtin_module_names)


File: python.info,  Node: 我如何使Python script 執行在Unix ?,  Next: Is there a curses/termcap package for Python?,  Prev: 哪裡可以找到math py socket py regex py 等 原始檔案,  Up: 常見函式問題

11.4.1.3 我如何使Python script 執行在Unix ?
...........................................

你需要作兩件事:腳本程式必須可以被執行而且第一行必須"#!"開頭後面接上
Python直譯器的路徑

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: Is there a curses/termcap package for Python?,  Next: Is there an equivalent to C's onexit in Python?,  Prev: 我如何使Python script 執行在Unix ?,  Up: 常見函式問題

11.4.1.4 Is there a curses/termcap package for Python?
......................................................

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: 2c. 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.

For Windows: use the consolelib module(2).

   ---------- Footnotes ----------

   (1) https://github.com/python/cpython/tree/3.8/Modules

   (2) http://effbot.org/zone/console-index.htm


File: python.info,  Node: Is there an equivalent to C's onexit in Python?,  Next: Why don't my signal handlers work?,  Prev: Is there a curses/termcap package for Python?,  Up: 常見函式問題

11.4.1.5 Is there an equivalent to C’s onexit() in Python?
..........................................................

The *note atexit: c. module provides a register function that is similar
to C’s ‘onexit()’.


File: python.info,  Node: Why don't my signal handlers work?,  Prev: Is there an equivalent to C's onexit in Python?,  Up: 常見函式問題

11.4.1.6 Why don’t my signal handlers work?
...........................................

The most common problem is that the signal handler is declared with the
wrong argument list.  It is called as

     handler(signum, frame)

so it should be declared with two arguments:

     def handler(signum, frame):
         ...


File: python.info,  Node: 一般性的工作,  Next: Threads,  Prev: 常見函式問題,  Up: 函式庫和擴充功能的常見問題

11.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: 一般性的工作

11.4.2.1 我如何測試Python程式
.............................

Python comes with two testing frameworks.  The *note doctest: 67. 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: 11c. 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()

在你的程式主模組的底端

Once your program is organized as a tractable collection of functions
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: 一般性的工作

11.4.2.2 How do I create documentation from doc strings?
........................................................

The *note pydoc: da. 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) http://epydoc.sourceforge.net/

   (2) http://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: 一般性的工作

11.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: Threads,  Next: Input and Output,  Prev: 一般性的工作,  Up: 函式庫和擴充功能的常見問題

11.4.3 Threads
--------------

* Menu:

* How do I program using threads?::
* None of my threads seem to run; why?: None of my threads seem to run why?.
* How do I parcel out work among a bunch of worker threads?::
* What kinds of global value mutation are thread-safe?::
* Can't we get rid of the Global Interpreter Lock?::


File: python.info,  Node: How do I program using threads?,  Next: None of my threads seem to run why?,  Up: Threads

11.4.3.1 How do I program using threads?
........................................

Be sure to use the *note threading: 10a. module and not the *note
_thread: 3. module.  The *note threading: 10a. module builds convenient
abstractions on top of the low-level primitives provided by the *note
_thread: 3. module.

Aahz has a set of slides from his threading tutorial that are helpful;
see ‘http://www.pythoncraft.com/OSCON2001/’.


File: python.info,  Node: None of my threads seem to run why?,  Next: How do I parcel out work among a bunch of worker threads?,  Prev: How do I program using threads?,  Up: Threads

11.4.3.2 None of my threads seem to run: why?
.............................................

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():
685, it’s better to use some kind of semaphore mechanism.  One idea is
to use the *note queue: db. 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: None of my threads seem to run why?,  Up: Threads

11.4.3.3 How do I parcel out work among a bunch of worker threads?
..................................................................

The easiest way is to use the new *note concurrent.futures: 22. module,
especially the *note ThreadPoolExecutor: 27b. class.

Or, if you want fine control over the dispatching algorithm, you can
write your own logic manually.  Use the *note queue: db. module to
create a queue containing a list of jobs.  The *note Queue: d1d. 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.currentThread(), end=' ')
                 print('queue empty')
                 break
             else:
                 print('Worker', threading.currentThread(), 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:
d1d. class provides a featureful interface.


File: python.info,  Node: What kinds of global value mutation are thread-safe?,  Next: Can't we get rid of the Global Interpreter Lock?,  Prev: How do I parcel out work among a bunch of worker threads?,  Up: Threads

11.4.3.4 What kinds of global value mutation are thread-safe?
.............................................................

A *note global interpreter lock: 50b. (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(): bf0.  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()

These aren’t:

     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__(): 924. 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: Can't we get rid of the Global Interpreter Lock?,  Prev: What kinds of global value mutation are thread-safe?,  Up: Threads

11.4.3.5 Can’t we get rid of the Global Interpreter Lock?
.........................................................

The *note global interpreter lock: 50b. (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.

Back 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 recently did
a similar experiment in his python-safethread(1) project.
Unfortunately, both 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.

This 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: 2a5. class in the new *note concurrent.futures: 22.
module provides an easy way of doing so; the *note multiprocessing: b8.
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: 145. and *note hashlib: 8d. already do this.

It has been suggested that the GIL should be a per-interpreter-state
lock rather than truly global; interpreters then wouldn’t be able to
share objects.  Unfortunately, this isn’t likely to happen either.  It
would be a tremendous amount of work, because many object
implementations currently have global state.  For example, small
integers and short strings are cached; these caches would have to be
moved to the interpreter state.  Other object types have their own free
list; these free lists would have to be moved to the interpreter state.
And so on.

And I doubt that it can even be done in finite time, because the same
problem exists for 3rd party extensions.  It is likely that 3rd party
extensions are being written at a faster rate than you can convert them
to store all their global state in the interpreter state.

And finally, once you have multiple interpreters not sharing any state,
what have you gained over running each interpreter in a separate
process?

   ---------- Footnotes ----------

   (1) https://code.google.com/archive/p/python-safethread


File: python.info,  Node: Input and Output,  Next: Network/Internet Programming,  Prev: Threads,  Up: 函式庫和擴充功能的常見問題

11.4.4 Input and Output
-----------------------

* Menu:

* How do I delete a file? (And other file questions...): How do I delete a file? And other file questions.
* How do I copy a file?::
* How do I read (or write) binary data?: How do I read or write binary data?.
* 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?.
* How do I access the serial (RS232) port?: How do I access the serial RS232 port?.
* Why doesn’t closing sys.stdout (stdin, stderr) really close it?: Why doesn't closing sys stdout stdin stderr really close it?.


File: python.info,  Node: How do I delete a file? And other file questions,  Next: How do I copy a file?,  Up: Input and Output

11.4.4.1 How do I delete a file? (And other file questions...)
..............................................................

Use ‘os.remove(filename)’ or ‘os.unlink(filename)’; for documentation,
see the *note os: c5. module.  The two functions are identical; *note
unlink(): a41. is simply the name of the Unix system call for this
function.

To remove a directory, use *note os.rmdir(): a3f.; use *note os.mkdir():
a3b. 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(): 21d.

To rename a file, use ‘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(): 66a, where `fd' is the file descriptor (a small integer).

The *note shutil: ea. module also contains a number of functions to work
on files including *note copyfile(): 259, *note copytree(): 21b, and
*note rmtree(): 21d.


File: python.info,  Node: How do I copy a file?,  Next: How do I read or write binary data?,  Prev: How do I delete a file? And other file questions,  Up: Input and Output

11.4.4.2 How do I copy a file?
..............................

The *note shutil: ea. module contains a *note copyfile(): 259. function.
Note that on MacOS 9 it doesn’t copy the resource fork and Finder info.


File: python.info,  Node: How do I read or write binary data?,  Next: I can't seem to use os read on a pipe created with os popen ; why?,  Prev: How do I copy a file?,  Up: Input and Output

11.4.4.3 How do I read (or write) binary data?
..............................................

To read or write complex binary data formats, it’s best to use the *note
struct: f9. 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: 7. module.

     備註: To read and write binary data, it is mandatory to open the
     file in binary mode (here, passing ‘"rb"’ to *note open(): 4f5.).
     If you use ‘"r"’ instead (the default), the file will be open in
     text mode and ‘f.read()’ will return *note str: 335. objects rather
     than *note bytes: 336. objects.


File: python.info,  Node: I can't seem to use os read on a pipe created with os popen ; why?,  Next: How do I access the serial RS232 port?,  Prev: How do I read or write binary data?,  Up: Input and Output

11.4.4.4 I can’t seem to use os.read() on a pipe created with os.popen(); why?
..............................................................................

*note os.read(): 66d. is a low-level function which takes a file
descriptor, a small integer representing the opened file.  *note
os.popen(): 2aa. creates a high-level file object, the same type
returned by the built-in *note open(): 4f5. function.  Thus, to read `n'
bytes from a pipe `p' created with *note os.popen(): 2aa, you need to
use ‘p.read(n)’.


File: python.info,  Node: How do I access the serial RS232 port?,  Next: Why doesn't closing sys stdout stdin stderr really close it?,  Prev: I can't seem to use os read on a pipe created with os popen ; why?,  Up: Input and Output

11.4.4.5 How do I access the serial (RS232) port?
.................................................

For Win32, POSIX (Linux, BSD, etc.), Jython:

     ‘http://pyserial.sourceforge.net’

For Unix, see a Usenet post by Mitch Chapman:

     ‘https://groups.google.com/groups?selm=34A04430.CF9@ohioee.com’


File: python.info,  Node: Why doesn't closing sys stdout stdin stderr really close it?,  Prev: How do I access the serial RS232 port?,  Up: Input and Output

11.4.4.6 Why doesn’t closing sys.stdout (stdin, stderr) really close it?
........................................................................

Python *note file objects: b47. are a high-level layer of abstraction on
low-level C file descriptors.

For most file objects you create in Python via the built-in *note
open(): 4f5. 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(): 3d7.:

     os.close(stdin.fileno())
     os.close(stdout.fileno())
     os.close(stderr.fileno())

Or you can use the numeric constants 0, 1 and 2, respectively.


File: python.info,  Node: Network/Internet Programming,  Next: Databases,  Prev: Input and Output,  Up: 函式庫和擴充功能的常見問題

11.4.5 Network/Internet Programming
-----------------------------------

* Menu:

* What WWW tools are there for Python?::
* How can I mimic CGI form submission (METHOD=POST)?: How can I mimic CGI form submission METHOD=POST ?.
* What module should I use to help with generating HTML?::
* How do I send mail from a Python script?::
* 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: What WWW tools are there for Python?,  Next: How can I mimic CGI form submission METHOD=POST ?,  Up: Network/Internet Programming

11.4.5.1 What WWW tools are there for Python?
.............................................

See the chapters titled *note Internet Protocols and Support: 2bd0. and
*note Internet Data Handling: 27d5. 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’.

Cameron Laird maintains a useful set of pages about Python web
technologies at ‘http://phaseit.net/claird/comp.lang.python/web_python’.


File: python.info,  Node: How can I mimic CGI form submission METHOD=POST ?,  Next: What module should I use to help with generating HTML?,  Prev: What WWW tools are there for Python?,  Up: Network/Internet Programming

11.4.5.2 How can I mimic CGI form submission (METHOD=POST)?
...........................................................

I would like to retrieve web pages that are the result of POSTing a
form.  Is there existing code that would let me do this easily?

Yes.  Here’s a simple example that uses urllib.request:

     #!/usr/local/bin/python

     import urllib.request

     # build the query string
     qs = "First=Josephine&MI=Q&Last=Public"

     # connect and send the server a path
     req = urllib.request.urlopen('http://www.some-server.out-there'
                                  '/cgi-bin/some-cgi-script', data=qs)
     with req:
         msg, hdrs = req.read(), req.info()

Note that in general for percent-encoded POST operations, query strings
must be quoted using *note urllib.parse.urlencode(): 790.  For example,
to send ‘name=Guy Steele, Jr.’:

     >>> import urllib.parse
     >>> urllib.parse.urlencode({'name': 'Guy Steele, Jr.'})
     'name=Guy+Steele%2C+Jr.'

也參考
......

*note 如何使用urllib套件取得網路資源: 2cb3. for extensive examples.


File: python.info,  Node: What module should I use to help with generating HTML?,  Next: How do I send mail from a Python script?,  Prev: How can I mimic CGI form submission METHOD=POST ?,  Up: Network/Internet Programming

11.4.5.3 What module should I use to help with generating 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: How do I send mail from a Python script?,  Next: How do I avoid blocking in the connect method of a socket?,  Prev: What module should I use to help with generating HTML?,  Up: Network/Internet Programming

11.4.5.4 How do I send mail from a Python script?
.................................................

Use the standard library module *note smtplib: ee.

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: How do I send mail from a Python script?,  Up: Network/Internet Programming

11.4.5.5 How do I avoid blocking in the connect() method of a socket?
.....................................................................

The *note select: e6. module is commonly used to help with asynchronous
I/O on sockets.

To prevent the TCP connect from blocking, you can set the socket to
non-blocking mode.  Then when you do the ‘connect()’, 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 ‘connect_ex()’ method to avoid creating an exception.
It will just return the errno value.  To poll, you can call
‘connect_ex()’ again later – ‘0’ or ‘errno.EISCONN’ indicate that you’re
connected – or you can pass this socket to select to check if it’s
writable.

     備註: The *note asyncore: b. module presents a framework-like
     approach to the problem of writing non-blocking networking code.
     The third-party Twisted(1) library is a popular and feature-rich
     alternative.

   ---------- Footnotes ----------

   (1) https://twistedmatrix.com/trac/


File: python.info,  Node: Databases,  Next: Mathematics and Numerics,  Prev: Network/Internet Programming,  Up: 函式庫和擴充功能的常見問題

11.4.6 Databases
----------------

* Menu:

* Are there any interfaces to database packages in Python?::
* How do you implement persistent objects in Python?::


File: python.info,  Node: Are there any interfaces to database packages in Python?,  Next: How do you implement persistent objects in Python?,  Up: Databases

11.4.6.1 Are there any interfaces to database packages in Python?
.................................................................

有的

Interfaces to disk-based hashes such as *note DBM: 35. and *note GDBM:
34. are also included with standard Python.  There is also the *note
sqlite3: f3. 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: Are there any interfaces to database packages in Python?,  Up: Databases

11.4.6.2 How do you implement persistent objects in Python?
...........................................................

The *note pickle: cb. 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: e8. library module uses pickle and
(g)dbm to create persistent mappings containing arbitrary Python
objects.


File: python.info,  Node: Mathematics and Numerics,  Prev: Databases,  Up: 函式庫和擴充功能的常見問題

11.4.7 Mathematics and Numerics
-------------------------------

* Menu:

* How do I generate random numbers in Python?::


File: python.info,  Node: How do I generate random numbers in Python?,  Up: Mathematics and Numerics

11.4.7.1 How do I generate random numbers in Python?
....................................................

The standard module *note random: dd. implements a random number
generator.  Usage is simple:

     import random
     random.random()

This returns a random floating point number in the range [0, 1).

There are also many other specialized generators in this module, such
as:

   * ‘randrange(a, b)’ chooses an integer in the range [a, b).

   * ‘uniform(a, b)’ chooses a floating point number in the range [a,
     b).

   * ‘normalvariate(mean, sdev)’ samples the normal (Gaussian)
     distribution.

Some higher-level functions operate on sequences directly, such as:

   * ‘choice(S)’ chooses random element from a given sequence

   * ‘shuffle(L)’ shuffles a list in-place, i.e.  permutes it randomly

There’s also a ‘Random’ class you can instantiate to create independent
multiple random number generators.


File: python.info,  Node: Extending/Embedding FAQ,  Next: FAQ：在 Windows 使用 Python,  Prev: 函式庫和擴充功能的常見問題,  Up: Python 常見問題

11.5 Extending/Embedding FAQ
============================

* Menu:

* Can I create my own functions in C?::
* Can I create my own functions in C++?::
* Writing C is hard; are there any alternatives?::
* How can I execute arbitrary Python statements from C?::
* How can I evaluate an arbitrary Python expression from C?::
* How do I extract C values from a Python object?::
* How do I use Py_BuildValue() to create a tuple of arbitrary length?: How do I use Py_BuildValue to create a tuple of arbitrary length?.
* How do I call an object's method from C?::
* How do I catch the output from PyErr_Print() (or anything that prints to stdout/stderr)?: How do I catch the output from PyErr_Print or anything that prints to stdout/stderr ?.
* How do I access a module written in Python from C?::
* How do I interface to C++ objects from Python?::
* I added a module using the Setup file and the make fails; why?::
* How do I debug an extension?::
* I want to compile a Python module on my Linux system, but some files are missing. Why?: I want to compile a Python module on my Linux system but some files are missing Why?.
* How do I tell "incomplete input" from "invalid input"?::
* How do I find undefined g++ symbols __builtin_new or __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: Can I create my own functions in C?,  Next: Can I create my own functions in C++?,  Up: Extending/Embedding FAQ

11.5.1 Can I create my own functions in C?
------------------------------------------

Yes, you can create built-in modules containing functions, variables,
exceptions and even new types in C. This is explained in the document
*note Extending and Embedding the Python Interpreter: 1202.

Most intermediate or advanced Python books will also cover this topic.


File: python.info,  Node: Can I create my own functions in C++?,  Next: Writing C is hard; are there any alternatives?,  Prev: Can I create my own functions in C?,  Up: Extending/Embedding FAQ

11.5.2 Can I create my own functions in 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: Writing C is hard; are there any alternatives?,  Next: How can I execute arbitrary Python statements from C?,  Prev: Can I create my own functions in C++?,  Up: Extending/Embedding FAQ

11.5.3 Writing C is hard; are there any alternatives?
-----------------------------------------------------

There are a number of alternatives to writing your own C extensions,
depending on what you’re trying to do.

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) http://cython.org

   (2) https://www.cosc.canterbury.ac.nz/greg.ewing/python/Pyrex/

   (3) http://www.swig.org

   (4) https://riverbankcomputing.com/software/sip/intro

   (5) http://cxx.sourceforge.net/

   (6) http://www.boost.org/libs/python/doc/index.html

   (7) https://github.com/scipy/weave


File: python.info,  Node: How can I execute arbitrary Python statements from C?,  Next: How can I evaluate an arbitrary Python expression from C?,  Prev: Writing C is hard; are there any alternatives?,  Up: Extending/Embedding FAQ

11.5.4 How can I execute arbitrary Python statements from C?
------------------------------------------------------------

The highest-level function to do this is *note PyRun_SimpleString():
3b81. 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: 45d.).  If you want
more control, use *note PyRun_String(): fb8.; see the source for *note
PyRun_SimpleString(): 3b81. in ‘Python/pythonrun.c’.


File: python.info,  Node: How can I evaluate an arbitrary Python expression from C?,  Next: How do I extract C values from a Python object?,  Prev: How can I execute arbitrary Python statements from C?,  Up: Extending/Embedding FAQ

11.5.5 How can I evaluate an arbitrary Python expression from C?
----------------------------------------------------------------

Call the function *note PyRun_String(): fb8. from the previous question
with the start symbol *note Py_eval_input: 3bdd.; it parses an
expression, evaluates it and returns its value.


File: python.info,  Node: How do I extract C values from a Python object?,  Next: How do I use Py_BuildValue to create a tuple of arbitrary length?,  Prev: How can I evaluate an arbitrary Python expression from C?,  Up: Extending/Embedding FAQ

11.5.6 How do I extract C values from a Python object?
------------------------------------------------------

That depends on the object’s type.  If it’s a tuple, *note
PyTuple_Size(): 3e38. returns its length and *note PyTuple_GetItem():
3b16. returns the item at a specified index.  Lists have similar
functions, ‘PyListSize()’ and *note PyList_GetItem(): 3b17.

For bytes, *note PyBytes_Size(): 3dc3. returns its length and *note
PyBytes_AsStringAndSize(): 3dc7. 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.

To test the type of an object, first make sure it isn’t ‘NULL’, and then
use *note PyBytes_Check(): d24, *note PyTuple_Check(): 3e34, *note
PyList_Check(): 3e49, etc.

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(): 3cef, *note
PySequence_GetItem(): 1053, etc.  as well as many other useful protocols
such as numbers (*note PyNumber_Index(): 3ce9. et al.)  and mappings in
the PyMapping APIs.


File: python.info,  Node: How do I use Py_BuildValue to create a tuple of arbitrary length?,  Next: How do I call an object's method from C?,  Prev: How do I extract C values from a Python object?,  Up: Extending/Embedding FAQ

11.5.7 How do I use Py_BuildValue() to create a tuple of arbitrary length?
--------------------------------------------------------------------------

You can’t.  Use *note PyTuple_Pack(): 3e37. instead.


File: python.info,  Node: How do I call an object's method from C?,  Next: How do I catch the output from PyErr_Print or anything that prints to stdout/stderr ?,  Prev: How do I use Py_BuildValue to create a tuple of arbitrary length?,  Up: Extending/Embedding FAQ

11.5.8 How do I call an object’s method from C?
-----------------------------------------------

The *note PyObject_CallMethod(): 3cba. 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(): 2cf, 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():
267.’ing the return value.

To call, e.g., a file object’s "seek" method with arguments 10, 0
(assuming the file object pointer is "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(): 3b09. `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: How do I catch the output from PyErr_Print or anything that prints to stdout/stderr ?,  Next: How do I access a module written in Python from C?,  Prev: How do I call an object's method from C?,  Up: Extending/Embedding FAQ

11.5.9 How do I catch the output from PyErr_Print() (or anything that prints to stdout/stderr)?
-----------------------------------------------------------------------------------------------

In Python code, define an object that supports the ‘write()’ method.
Assign this object to *note sys.stdout: 313. and *note sys.stderr: 314.
Call print_error, or just allow the standard traceback mechanism to
work.  Then, the output will go wherever your ‘write()’ method sends it.

The easiest way to do this is to use the *note io.StringIO: 832. class:

     >>> 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: How do I access a module written in Python from C?,  Next: How do I interface to C++ objects from Python?,  Prev: How do I catch the output from PyErr_Print or anything that prints to stdout/stderr ?,  Up: Extending/Embedding FAQ

11.5.10 How do I access a module written in Python from C?
----------------------------------------------------------

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: f2b.), 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: f2b.

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(): 3cb1. to assign to variables in
the module also works.


File: python.info,  Node: How do I interface to C++ objects from Python?,  Next: I added a module using the Setup file and the make fails; why?,  Prev: How do I access a module written in Python from C?,  Up: Extending/Embedding FAQ

11.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:
1202.  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.

For C++ libraries, see *note Writing C is hard; are there any
alternatives?: 42cd.


File: python.info,  Node: I added a module using the Setup file and the make fails; why?,  Next: How do I debug an extension?,  Prev: How do I interface to C++ objects from Python?,  Up: Extending/Embedding FAQ

11.5.12 I added a module using the Setup file and the make fails; why?
----------------------------------------------------------------------

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: How do I debug an extension?,  Next: I want to compile a Python module on my Linux system but some files are missing Why?,  Prev: I added a module using the Setup file and the make fails; why?,  Up: Extending/Embedding FAQ

11.5.13 How do I debug an extension?
------------------------------------

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

Then, when you run 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: I want to compile a Python module on my Linux system but some files are missing Why?,  Next: How do I tell "incomplete input" from "invalid input"?,  Prev: How do I debug an extension?,  Up: Extending/Embedding FAQ

11.5.14 I want to compile a Python module on my Linux system, but some files are missing. Why?
----------------------------------------------------------------------------------------------

Most packaged versions of Python don’t include the
‘/usr/lib/python2.`x'/config/’ directory, which contains various files
required for compiling Python extensions.

For Red Hat, install the python-devel RPM to get the necessary files.

For Debian, run ‘apt-get install python-dev’.


File: python.info,  Node: How do I tell "incomplete input" from "invalid input"?,  Next: How do I find undefined g++ symbols __builtin_new or __pure_virtual?,  Prev: I want to compile a Python module on my Linux system but some files are missing Why?,  Up: Extending/Embedding FAQ

11.5.15 How do I tell "incomplete input" from "invalid input"?
--------------------------------------------------------------

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.

In Python you can use the *note codeop: 1d. module, which approximates
the parser’s behavior sufficiently.  IDLE uses this, for example.

The easiest way to do it in C is to call *note PyRun_InteractiveLoop():
3bc4. (perhaps in a separate thread) and let the Python interpreter
handle the input for you.  You can also set the *note
PyOS_ReadlineFunctionPointer(): 971. to point at your custom input
function.  See ‘Modules/readline.c’ and ‘Parser/myreadline.c’ for more
hints.

However sometimes you have to run the embedded Python interpreter in the
same thread as your rest application and you can’t allow the *note
PyRun_InteractiveLoop(): 3bc4. to stop while waiting for user input.
The one solution then is to call ‘PyParser_ParseString()’ and test for
‘e.error’ equal to ‘E_EOF’, which means the input is incomplete.  Here’s
a sample code fragment, untested, inspired by code from Alex Farber:

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>
     #include <node.h>
     #include <errcode.h>
     #include <grammar.h>
     #include <parsetok.h>
     #include <compile.h>

     int testcomplete(char *code)
       /* code should end in \n */
       /* return -1 for error, 0 for incomplete, 1 for complete */
     {
       node *n;
       perrdetail e;

       n = PyParser_ParseString(code, &_PyParser_Grammar,
                                Py_file_input, &e);
       if (n == NULL) {
         if (e.error == E_EOF)
           return 0;
         return -1;
       }

       PyNode_Free(n);
       return 1;
     }

Another solution is trying to compile the received string with *note
Py_CompileString(): 3bd5.  If it compiles without errors, try to execute
the returned code object by calling *note PyEval_EvalCode(): 3bd9.
Otherwise save the input for later.  If the compilation fails, find out
if it’s an error or just more input is required - by extracting the
message string from the exception tuple and comparing it to the string
"unexpected EOF while parsing".  Here is a complete example using the
GNU readline library (you may want to ignore `SIGINT' while calling
readline()):

     #include <stdio.h>
     #include <readline.h>

     #define PY_SSIZE_T_CLEAN
     #include <Python.h>
     #include <object.h>
     #include <compile.h>
     #include <eval.h>

     int main (int argc, char* argv[])
     {
       int i, j, done = 0;                          /* lengths of line, code */
       char ps1[] = ">>> ";
       char ps2[] = "... ";
       char *prompt = ps1;
       char *msg, *line, *code = NULL;
       PyObject *src, *glb, *loc;
       PyObject *exc, *val, *trb, *obj, *dum;

       Py_Initialize ();
       loc = PyDict_New ();
       glb = PyDict_New ();
       PyDict_SetItemString (glb, "__builtins__", PyEval_GetBuiltins ());

       while (!done)
       {
         line = readline (prompt);

         if (NULL == line)                          /* Ctrl-D pressed */
         {
           done = 1;
         }
         else
         {
           i = strlen (line);

           if (i > 0)
             add_history (line);                    /* save non-empty lines */

           if (NULL == code)                        /* nothing in code yet */
             j = 0;
           else
             j = strlen (code);

           code = realloc (code, i + j + 2);
           if (NULL == code)                        /* out of memory */
             exit (1);

           if (0 == j)                              /* code was empty, so */
             code[0] = '\0';                        /* keep strncat happy */

           strncat (code, line, i);                 /* append line to code */
           code[i + j] = '\n';                      /* append '\n' to code */
           code[i + j + 1] = '\0';

           src = Py_CompileString (code, "<stdin>", Py_single_input);

           if (NULL != src)                         /* compiled just fine - */
           {
             if (ps1  == prompt ||                  /* ">>> " or */
                 '\n' == code[i + j - 1])           /* "... " and double '\n' */
             {                                               /* so execute it */
               dum = PyEval_EvalCode (src, glb, loc);
               Py_XDECREF (dum);
               Py_XDECREF (src);
               free (code);
               code = NULL;
               if (PyErr_Occurred ())
                 PyErr_Print ();
               prompt = ps1;
             }
           }                                        /* syntax error or E_EOF? */
           else if (PyErr_ExceptionMatches (PyExc_SyntaxError))
           {
             PyErr_Fetch (&exc, &val, &trb);        /* clears exception! */

             if (PyArg_ParseTuple (val, "sO", &msg, &obj) &&
                 !strcmp (msg, "unexpected EOF while parsing")) /* E_EOF */
             {
               Py_XDECREF (exc);
               Py_XDECREF (val);
               Py_XDECREF (trb);
               prompt = ps2;
             }
             else                                   /* some other syntax error */
             {
               PyErr_Restore (exc, val, trb);
               PyErr_Print ();
               free (code);
               code = NULL;
               prompt = ps1;
             }
           }
           else                                     /* some non-syntax error */
           {
             PyErr_Print ();
             free (code);
             code = NULL;
             prompt = ps1;
           }

           free (line);
         }
       }

       Py_XDECREF(glb);
       Py_XDECREF(loc);
       Py_Finalize();
       exit(0);
     }


File: python.info,  Node: How do I find undefined g++ symbols __builtin_new or __pure_virtual?,  Next: Can I create an object class with some methods implemented in C and others in Python e g through inheritance ?,  Prev: How do I tell "incomplete input" from "invalid input"?,  Up: Extending/Embedding FAQ

11.5.16 How do I find undefined g++ symbols __builtin_new or __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: How do I find undefined g++ symbols __builtin_new or __pure_virtual?,  Up: Extending/Embedding FAQ

11.5.17 Can I create an object class with some methods implemented in C and others in Python (e.g. through inheritance)?
------------------------------------------------------------------------------------------------------------------------

Yes, you can inherit from built-in classes such as *note int: 185, *note
list: 263, *note dict: 1b9, etc.

The Boost Python Library (BPL,
‘http://www.boost.org/libs/python/doc/index.html’) provides a way of
doing this from C++ (i.e.  you can inherit from an extension class
written in C++ using the BPL).


File: python.info,  Node: FAQ：在 Windows 使用 Python,  Next: 圖形化使用者界面常見問答集,  Prev: Extending/Embedding FAQ,  Up: Python 常見問題

11.6 FAQ：在 Windows 使用 Python
================================

* Menu:

* 在 Windows 作業系統裡我想執行 Python 程式，要怎麼做？::
* How do I make Python scripts executable?::
* Why does Python sometimes take so long to start?::
* How do I make an executable from a Python script?::
* Is a *.pyd file the same as a DLL?: Is a * pyd file the same as a DLL?.
* How can I embed Python into a Windows application?::
* How do I keep editors from inserting tabs into my Python source?::
* How do I check for a keypress without blocking?::


File: python.info,  Node: 在 Windows 作業系統裡我想執行 Python 程式，要怎麼做？,  Next: How do I make Python scripts executable?,  Up: FAQ：在 Windows 使用 Python

11.6.1 在 Windows 作業系統裡我想執行 Python 程式，要怎麼做？
------------------------------------------------------------

這個問題的答案可能有點複雜。如果你經常使用「命令提示字元」執行程式，那這
對你來說不會是什麼難事。如果不然，那就需要更仔細的說明了。

Unless you use some sort of integrated development environment, you will
end up `typing' Windows commands into what is variously referred to as a
"DOS window" or "Command prompt window".  Usually you can create such a
window from your search bar by searching for ‘cmd’.  You should be able
to recognize when you have started such a window because you will see a
Windows "command prompt", which usually looks like this:

     C:\>

The letter may be different, and there might be other things after it,
so you might just as easily see something like:

     D:\YourName\Projects\Python>

depending on how your computer has been set up and what else you have
recently done with it.  Once you have started such a window, you are
well on the way to running Python programs.

You need to realize that your Python scripts have to be processed by
another program called the Python `interpreter'.  The interpreter reads
your script, compiles it into bytecodes, and then executes the bytecodes
to run your program.  So, how do you arrange for the interpreter to
handle your Python?

First, you need to make sure that your command window recognises the
word "py" as an instruction to start the interpreter.  If you have
opened a command window, you should try entering the command ‘py’ and
hitting return:

     C:\Users\YourName> py

You should then see something like:

     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.
     >>>

You have started the interpreter in "interactive mode".  That means you
can enter Python statements or expressions interactively and have them
executed or evaluated while you wait.  This is one of Python’s strongest
features.  Check it by entering a few expressions of your choice and
seeing the results:

     >>> print("Hello")
     Hello
     >>> "Hello" * 3
     'HelloHelloHello'

Many people use the interactive mode as a convenient yet highly
programmable calculator.  When you want to end your interactive Python
session, call the *note exit(): 1614. function or hold the ‘Ctrl’ key
down while you enter a ‘Z’, then hit the "‘Enter’" key to get back to
your Windows command prompt.

You may also find that you have a Start-menu entry such as Start ‣
Programs ‣ Python 3.x ‣ Python (command line) that results in you seeing
the ‘>>>’ prompt in a new window.  If so, the window will disappear
after you call the *note exit(): 1614. function or enter the ‘Ctrl-Z’
character; Windows is running a single "python" command in the window,
and closes it when you terminate the interpreter.

Now that we know the ‘py’ command is recognized, you can give your
Python script to it.  You’ll have to give either an absolute or a
relative path to the Python script.  Let’s say your Python script is
located in your desktop and is named ‘hello.py’, and your command prompt
is nicely opened in your home directory so you’re seeing something
similar to:

     C:\Users\YourName>

So now you’ll ask the ‘py’ command to give your script to Python by
typing ‘py’ followed by your script path:

     C:\Users\YourName> py Desktop\hello.py
     hello


File: python.info,  Node: How do I make Python scripts executable?,  Next: Why does Python sometimes take so long to start?,  Prev: 在 Windows 作業系統裡我想執行 Python 程式，要怎麼做？,  Up: FAQ：在 Windows 使用 Python

11.6.2 How do I make Python scripts executable?
-----------------------------------------------

On Windows, the standard Python installer already associates the .py
extension with a file type (Python.File) and gives that file type an
open command that runs the interpreter (‘D:\Program
Files\Python\python.exe "%1" %*’).  This is enough to make scripts
executable from the command prompt as ’foo.py’.  If you’d rather be able
to execute the script by simple typing ’foo’ with no extension you need
to add .py to the PATHEXT environment variable.


File: python.info,  Node: Why does Python sometimes take so long to start?,  Next: How do I make an executable from a Python script?,  Prev: How do I make Python scripts executable?,  Up: FAQ：在 Windows 使用 Python

11.6.3 Why does Python sometimes take so long to start?
-------------------------------------------------------

Usually Python starts very quickly on Windows, but occasionally there
are bug reports that Python suddenly begins to take a long time to start
up.  This is made even more puzzling because Python will work fine on
other Windows systems which appear to be configured identically.

The problem may be caused by a misconfiguration of virus checking
software on the problem machine.  Some virus scanners have been known to
introduce startup overhead of two orders of magnitude when the scanner
is configured to monitor all reads from the filesystem.  Try checking
the configuration of virus scanning software on your systems to ensure
that they are indeed configured identically.  McAfee, when configured to
scan all file system read activity, is a particular offender.


File: python.info,  Node: How do I make an executable from a Python script?,  Next: Is a * pyd file the same as a DLL?,  Prev: Why does Python sometimes take so long to start?,  Up: FAQ：在 Windows 使用 Python

11.6.4 How do I make an executable from a Python script?
--------------------------------------------------------

See cx_Freeze(1) and py2exe(2), both are distutils extensions that allow
you to create console and GUI executables from Python code.

   ---------- Footnotes ----------

   (1) https://cx-freeze.readthedocs.io/en/latest/

   (2) http://www.py2exe.org/


File: python.info,  Node: Is a * pyd file the same as a DLL?,  Next: How can I embed Python into a Windows application?,  Prev: How do I make an executable from a Python script?,  Up: FAQ：在 Windows 使用 Python

11.6.5 Is a ‘*.pyd’ file the same as a DLL?
-------------------------------------------

Yes, .pyd files are dll’s, but there are a few differences.  If you have
a DLL named ‘foo.pyd’, then it must have a function ‘PyInit_foo()’.  You
can then write Python "import foo", and Python will search for foo.pyd
(as well as foo.py, foo.pyc) and if it finds it, will attempt to call
‘PyInit_foo()’ to initialize it.  You do not link your .exe with
foo.lib, as that would cause Windows to require the DLL to be present.

Note that the search path for foo.pyd is PYTHONPATH, not the same as the
path that Windows uses to search for foo.dll.  Also, foo.pyd need not be
present to run your program, whereas if you linked your program with a
dll, the dll is required.  Of course, foo.pyd is required if you want to
say ‘import foo’.  In a DLL, linkage is declared in the source code with
‘__declspec(dllexport)’.  In a .pyd, linkage is defined in a list of
available functions.


File: python.info,  Node: How can I embed Python into a Windows application?,  Next: How do I keep editors from inserting tabs into my Python source?,  Prev: Is a * pyd file the same as a DLL?,  Up: FAQ：在 Windows 使用 Python

11.6.6 How can I embed Python into a Windows application?
---------------------------------------------------------

Embedding the Python interpreter in a Windows app can be summarized as
follows:

  1. Do _not_ build Python into your .exe file directly.  On Windows,
     Python must be a DLL to handle importing modules that are
     themselves DLL’s.  (This is the first key undocumented fact.)
     Instead, link to ‘python`NN'.dll’; it is typically installed in
     ‘C:\Windows\System’.  `NN' is the Python version, a number such as
     "33" for Python 3.3.

     You can link to Python in two different ways.  Load-time linking
     means linking against ‘python`NN'.lib’, while run-time linking
     means linking against ‘python`NN'.dll’.  (General note:
     ‘python`NN'.lib’ is the so-called "import lib" corresponding to
     ‘python`NN'.dll’.  It merely defines symbols for the linker.)

     Run-time linking greatly simplifies link options; everything
     happens at run time.  Your code must load ‘python`NN'.dll’ using
     the Windows ‘LoadLibraryEx()’ routine.  The code must also use
     access routines and data in ‘python`NN'.dll’ (that is, Python’s C
     API’s) using pointers obtained by the Windows ‘GetProcAddress()’
     routine.  Macros can make using these pointers transparent to any C
     code that calls routines in Python’s C API.

     Borland note: convert ‘python`NN'.lib’ to OMF format using
     Coff2Omf.exe first.

  2. If you use SWIG, it is easy to create a Python "extension module"
     that will make the app’s data and methods available to Python.
     SWIG will handle just about all the grungy details for you.  The
     result is C code that you link `into' your .exe file (!)  You do
     _not_ have to create a DLL file, and this also simplifies linking.

  3. SWIG will create an init function (a C function) whose name depends
     on the name of the extension module.  For example, if the name of
     the module is leo, the init function will be called initleo().  If
     you use SWIG shadow classes, as you should, the init function will
     be called initleoc().  This initializes a mostly hidden helper
     class used by the shadow class.

     The reason you can link the C code in step 2 into your .exe file is
     that calling the initialization function is equivalent to importing
     the module into Python!  (This is the second key undocumented
     fact.)

  4. In short, you can use the following code to initialize the Python
     interpreter with your extension module.

          #include "python.h"
          ...
          Py_Initialize();  // Initialize Python.
          initmyAppc();  // Initialize (import) the helper class.
          PyRun_SimpleString("import myApp");  // Import the shadow class.

  5. There are two problems with Python’s C API which will become
     apparent if you use a compiler other than MSVC, the compiler used
     to build pythonNN.dll.

     Problem 1: The so-called "Very High Level" functions that take FILE
     * arguments will not work in a multi-compiler environment because
     each compiler’s notion of a struct FILE will be different.  From an
     implementation standpoint these are very _low_ level functions.

     Problem 2: SWIG generates the following code when generating
     wrappers to void functions:

          Py_INCREF(Py_None);
          _resultobj = Py_None;
          return _resultobj;

     Alas, Py_None is a macro that expands to a reference to a complex
     data structure called _Py_NoneStruct inside pythonNN.dll.  Again,
     this code will fail in a mult-compiler environment.  Replace such
     code by:

          return Py_BuildValue("");

     It may be possible to use SWIG’s ‘%typemap’ command to make the
     change automatically, though I have not been able to get this to
     work (I’m a complete SWIG newbie).

  6. Using a Python shell script to put up a Python interpreter window
     from inside your Windows app is not a good idea; the resulting
     window will be independent of your app’s windowing system.  Rather,
     you (or the wxPythonWindow class) should create a "native"
     interpreter window.  It is easy to connect that window to the
     Python interpreter.  You can redirect Python’s i/o to _any_ object
     that supports read and write, so all you need is a Python object
     (defined in your extension module) that contains read() and write()
     methods.


File: python.info,  Node: How do I keep editors from inserting tabs into my Python source?,  Next: How do I check for a keypress without blocking?,  Prev: How can I embed Python into a Windows application?,  Up: FAQ：在 Windows 使用 Python

11.6.7 How do I keep editors from inserting tabs into my Python source?
-----------------------------------------------------------------------

The FAQ does not recommend using tabs, and the Python style guide, PEP
8(1), recommends 4 spaces for distributed Python code; this is also the
Emacs python-mode default.

Under any editor, mixing tabs and spaces is a bad idea.  MSVC is no
different in this respect, and is easily configured to use spaces: Take
Tools ‣ Options ‣ Tabs, and for file type "Default" set "Tab size" and
"Indent size" to 4, and select the "Insert spaces" radio button.

Python raises *note IndentationError: e7d. or *note TabError: e7c. if
mixed tabs and spaces are causing problems in leading whitespace.  You
may also run the *note tabnanny: 101. module to check a directory tree
in batch mode.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0008


File: python.info,  Node: How do I check for a keypress without blocking?,  Prev: How do I keep editors from inserting tabs into my Python source?,  Up: FAQ：在 Windows 使用 Python

11.6.8 How do I check for a keypress without blocking?
------------------------------------------------------

Use the *note msvcrt: b7. module.  This is a standard Windows-specific
extension module.  It defines a function ‘kbhit()’ which checks whether
a keyboard hit is present, and ‘getch()’ which gets one character
without echoing it.


File: python.info,  Node: 圖形化使用者界面常見問答集,  Next: 為什麼Python被安裝在我的機器上?常見問答集,  Prev: FAQ：在 Windows 使用 Python,  Up: Python 常見問題

11.7 圖形化使用者界面常見問答集
===============================

* Menu:

* 常見圖形化使用者界面(GUI) 問題: 常見圖形化使用者界面 GUI 問題.
* What platform-independent GUI toolkits exist for Python?::
* What platform-specific GUI toolkits exist for Python?::
* Tkinter questions::


File: python.info,  Node: 常見圖形化使用者界面 GUI 問題,  Next: What platform-independent GUI toolkits exist for Python?,  Up: 圖形化使用者界面常見問答集

11.7.1 常見圖形化使用者界面(GUI) 問題
-------------------------------------


File: python.info,  Node: What platform-independent GUI toolkits exist for Python?,  Next: What platform-specific GUI toolkits exist for Python?,  Prev: 常見圖形化使用者界面 GUI 問題,  Up: 圖形化使用者界面常見問答集

11.7.2 What platform-independent GUI toolkits exist for Python?
---------------------------------------------------------------

Depending on what platform(s) you are aiming at, there are several.
Some of them haven’t been ported to Python 3 yet.  At least *note
Tkinter: 42ed. and *note Qt: 42ee. are known to be Python 3-compatible.

* Menu:

* Tkinter::
* wxWidgets::
* Qt::
* Gtk+::
* Kivy::
* FLTK::
* 開放圖形庫(OpenGL): 開放圖形庫 OpenGL.


File: python.info,  Node: Tkinter,  Next: wxWidgets,  Up: What platform-independent GUI toolkits exist for Python?

11.7.2.1 Tkinter
................

Standard builds of Python include an object-oriented interface to the
Tcl/Tk widget set, called *note tkinter: 3171.  This is probably the
easiest to install (since it comes included with most binary
distributions(1) of Python) and use.  For more info about Tk, including
pointers to the source, see the Tcl/Tk home page(2).  Tcl/Tk is fully
portable to the Mac OS X, Windows, and Unix platforms.

   ---------- Footnotes ----------

   (1) https://www.python.org/downloads/

   (2) https://www.tcl.tk


File: python.info,  Node: wxWidgets,  Next: Qt,  Prev: Tkinter,  Up: What platform-independent GUI toolkits exist for Python?

11.7.2.2 wxWidgets
..................

wxWidgets (‘https://www.wxwidgets.org’) is a free, portable GUI class
library written in C++ that provides a native look and feel on a number
of platforms, with Windows, Mac OS X, GTK, X11, all listed as current
stable targets.  Language bindings are available for a number of
languages including Python, Perl, Ruby, etc.

wxPython(1) is the Python binding for wxwidgets.  While it often lags
slightly behind the official wxWidgets releases, it also offers a number
of features via pure Python extensions that are not available in other
language bindings.  There is an active wxPython user and developer
community.

Both wxWidgets and wxPython are free, open source, software with
permissive licences that allow their use in commercial products as well
as in freeware or shareware.

   ---------- Footnotes ----------

   (1) https://www.wxpython.org


File: python.info,  Node: Qt,  Next: Gtk+,  Prev: wxWidgets,  Up: What platform-independent GUI toolkits exist for Python?

11.7.2.3 Qt
...........

There are bindings available for the Qt toolkit (using either PyQt(1) or
PySide(2)) and for KDE (PyKDE4(3)).  PyQt is currently more mature than
PySide, but you must buy a PyQt license from Riverbank Computing(4) if
you want to write proprietary applications.  PySide is free for all
applications.

Qt 4.5 upwards is licensed under the LGPL license; also, commercial
licenses are available from The Qt Company(5).

   ---------- Footnotes ----------

   (1) https://riverbankcomputing.com/software/pyqt/intro

   (2) https://wiki.qt.io/PySide

   (3) https://techbase.kde.org/Languages/Python/Using_PyKDE_4

   (4) https://www.riverbankcomputing.com/commercial/license-faq

   (5) https://www.qt.io/licensing/


File: python.info,  Node: Gtk+,  Next: Kivy,  Prev: Qt,  Up: What platform-independent GUI toolkits exist for Python?

11.7.2.4 Gtk+
.............

The GObject introspection bindings(1) for Python allow you to write GTK+
3 applications.  There is also a Python GTK+ 3 Tutorial(2).

The older PyGtk bindings for the Gtk+ 2 toolkit(3) have been implemented
by James Henstridge; see <‘http://www.pygtk.org’>.

   ---------- Footnotes ----------

   (1) https://wiki.gnome.org/Projects/PyGObject

   (2) https://python-gtk-3-tutorial.readthedocs.io

   (3) https://www.gtk.org


File: python.info,  Node: Kivy,  Next: FLTK,  Prev: Gtk+,  Up: What platform-independent GUI toolkits exist for Python?

11.7.2.5 Kivy
.............

Kivy(1) is a cross-platform GUI library supporting both desktop
operating systems (Windows, macOS, Linux) and mobile devices (Android,
iOS). It is written in Python and Cython, and can use a range of
windowing backends.

Kivy is free and open source software distributed under the MIT license.

   ---------- Footnotes ----------

   (1) https://kivy.org/


File: python.info,  Node: FLTK,  Next: 開放圖形庫 OpenGL,  Prev: Kivy,  Up: What platform-independent GUI toolkits exist for Python?

11.7.2.6 FLTK
.............

Python bindings for the FLTK toolkit(1), a simple yet powerful and
mature cross-platform windowing system, are available from the PyFLTK
project(2).

   ---------- Footnotes ----------

   (1) http://www.fltk.org

   (2) http://pyfltk.sourceforge.net


File: python.info,  Node: 開放圖形庫 OpenGL,  Prev: FLTK,  Up: What platform-independent GUI toolkits exist for Python?

11.7.2.7 開放圖形庫(OpenGL)
...........................

For OpenGL bindings, see PyOpenGL(1).

   ---------- Footnotes ----------

   (1) http://pyopengl.sourceforge.net


File: python.info,  Node: What platform-specific GUI toolkits exist for Python?,  Next: Tkinter questions,  Prev: What platform-independent GUI toolkits exist for Python?,  Up: 圖形化使用者界面常見問答集

11.7.3 What platform-specific GUI toolkits exist for Python?
------------------------------------------------------------

By installing the PyObjc Objective-C bridge(1), Python programs can use
Mac OS X’s Cocoa libraries.

*note Pythonwin: 42df. by Mark Hammond includes an interface to the
Microsoft Foundation Classes and a Python programming environment that’s
written mostly in Python using the MFC classes.

   ---------- Footnotes ----------

   (1) https://pypi.org/project/pyobjc/


File: python.info,  Node: Tkinter questions,  Prev: What platform-specific GUI toolkits exist for Python?,  Up: 圖形化使用者界面常見問答集

11.7.4 Tkinter questions
------------------------

* Menu:

* How do I freeze Tkinter applications?::
* Can I have Tk events handled while waiting for I/O?::
* I can’t get key bindings to work in Tkinter; why?: I can't get key bindings to work in Tkinter why?.


File: python.info,  Node: How do I freeze Tkinter applications?,  Next: Can I have Tk events handled while waiting for I/O?,  Up: Tkinter questions

11.7.4.1 How do I freeze Tkinter applications?
..............................................

Freeze is a tool to create stand-alone applications.  When freezing
Tkinter applications, the applications will not be truly stand-alone, as
the application will still need the Tcl and Tk libraries.

One solution is to ship the application with the Tcl and Tk libraries,
and point to them at run-time using the ‘TCL_LIBRARY’ and ‘TK_LIBRARY’
environment variables.

To get truly stand-alone applications, the Tcl scripts that form the
library have to be integrated into the application as well.  One tool
supporting that is SAM (stand-alone modules), which is part of the Tix
distribution (‘http://tix.sourceforge.net/’).

Build Tix with SAM enabled, perform the appropriate call to
‘Tclsam_init()’, etc.  inside Python’s ‘Modules/tkappinit.c’, and link
with libtclsam and libtksam (you might include the Tix libraries as
well).


File: python.info,  Node: Can I have Tk events handled while waiting for I/O?,  Next: I can't get key bindings to work in Tkinter why?,  Prev: How do I freeze Tkinter applications?,  Up: Tkinter questions

11.7.4.2 Can I have Tk events handled while waiting for I/O?
............................................................

On platforms other than Windows, yes, and you don’t even need threads!
But you’ll have to restructure your I/O code a bit.  Tk has the
equivalent of Xt’s ‘XtAddInput()’ call, which allows you to register a
callback function which will be called from the Tk mainloop when I/O is
possible on a file descriptor.  See *note File Handlers: 318b.


File: python.info,  Node: I can't get key bindings to work in Tkinter why?,  Prev: Can I have Tk events handled while waiting for I/O?,  Up: Tkinter questions

11.7.4.3 I can’t get key bindings to work in Tkinter: why?
..........................................................

An often-heard complaint is that event handlers bound to events with the
‘bind()’ method don’t get handled even when the appropriate key is
pressed.

The most common cause is that the widget to which the binding applies
doesn’t have "keyboard focus".  Check out the Tk documentation for the
focus command.  Usually a widget is given the keyboard focus by clicking
in it (but not for labels; see the takefocus option).


File: python.info,  Node: 為什麼Python被安裝在我的機器上?常見問答集,  Prev: 圖形化使用者界面常見問答集,  Up: Python 常見問題

11.8 為什麼Python被安裝在我的機器上?常見問答集
==============================================

* Menu:

* 什麼是Python?: 什麼是Python?<2>.
* 為什麼Python被安裝在我的機器上?::
* 我能夠自行刪除Python嗎?::


File: python.info,  Node: 什麼是Python?<2>,  Next: 為什麼Python被安裝在我的機器上?,  Up: 為什麼Python被安裝在我的機器上?常見問答集

11.8.1 什麼是Python?
--------------------

Python是一種程式語言。它被使用於不同種類的應用程式中。因為Python屬於容易
學習的語言，它被使用在一些高中和學院中作為介紹程式語言的工具；但它也被專
業的軟體開發人員所使用，例如：Google，美國太空總署與 盧卡斯電影公司。

若你希望學習更多關於Python語言，可以從"Python初學者指引"網站
<‘https://wiki.python.org/moin/BeginnersGuide’>‘ 進行閱讀。


File: python.info,  Node: 為什麼Python被安裝在我的機器上?,  Next: 我能夠自行刪除Python嗎?,  Prev: 什麼是Python?<2>,  Up: 為什麼Python被安裝在我的機器上?常見問答集

11.8.2 為什麼Python被安裝在我的機器上?
--------------------------------------

若你發現曾安裝Python於系統中，但不記得何時安裝過，以下有幾種可能的方法可
以得知。

   * 也許其他使用此電腦的使用者希望學習撰寫程式並且安裝Python；你必須指
     出誰曾經使用此機器且可能安裝過。

   * 第三方應用程式安裝於機器中可能以Python語言撰寫並且安裝Python。有許
     多類似的應用程式，從GUI 程式 到網路伺服器和管理者腳本。

   * 一些安裝Windows的機器也被安裝Python。截至目前此文件交付，我們得知HP
     出廠的機器預設安裝Python。顯然的HP管理工具程式是透過Python語言所撰
     寫。

   * 許多相容於Unix 系統，例如：Mac OS X 和 一些 Linux 發行版本預設安裝
     Python ；安裝時被包含在基本安裝功能內。


File: python.info,  Node: 我能夠自行刪除Python嗎?,  Prev: 為什麼Python被安裝在我的機器上?,  Up: 為什麼Python被安裝在我的機器上?常見問答集

11.8.3 我能夠自行刪除Python嗎?
------------------------------

需要依據Python的安裝方式決定。

若有人不小心安裝了Python，可自行移除移除它。 Windows作業系統中，請於控制
台中尋找新增/移除程式進行反安裝。

若Python是透過第三方元件應用程式被安裝時，也可自行移除，不過請小心該應用
程式將無法正常執行。你應該使用應用程式反安裝功能而非自行刪除Python目錄

當作業系統預設安裝Python，不建議移除它。對你而言某些工具程式是重要不可或
缺的，若自行移除它，透過Python撰寫的工具程式將無法正常執行。重新安裝整個
系統仍需再次處理這些事情。


File: python.info,  Node: Glossary,  Next: 關於這些說明文件,  Prev: Python 常見問題,  Up: Top

12 Glossary
***********

‘>>>’

     The default Python prompt of the interactive shell.  Often seen for
     code examples which can be executed interactively in the
     interpreter.

‘...’

     Can refer to:

        * The default Python prompt of the interactive 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.

        * The *note Ellipsis: 1611. built-in constant.

2to3

     A tool that tries to convert Python 2.x code to Python 3.x code by
     handling most of the incompatibilities which can be detected by
     parsing the source and traversing the parse tree.

     2to3 is available in the standard library as *note lib2to3: a8.; a
     standalone entry point is provided as ‘Tools/scripts/2to3’.  See
     *note 2to3 - 自動將 Python 2的程式碼轉成 Python 3: c7b.

abstract base class

     Abstract base classes complement *note duck-typing: 4300. by
     providing a way to define interfaces when other techniques like
     *note hasattr(): 44c. would be clumsy or subtly wrong (for example
     with *note magic methods: 1441.).  ABCs introduce virtual
     subclasses, which are classes that don’t inherit from a class but
     are still recognized by *note isinstance(): 454. and *note
     issubclass(): 455.; see the *note abc: 4. module documentation.
     Python comes with many built-in ABCs for data structures (in the
     *note collections.abc: 1f. module), numbers (in the *note numbers:
     c2. module), streams (in the *note io: a2. module), import finders
     and loaders (in the *note importlib.abc: 9c. module).  You can
     create your own ABCs with the *note abc: 4. module.

annotation

     A label associated with a variable, a class attribute or a function
     parameter or return value, used by convention as a *note type hint:
     4302.

     Annotations of local variables cannot be accessed at runtime, but
     annotations of global variables, class attributes, and functions
     are stored in the ‘__annotations__’ special attribute of modules,
     classes, and functions, respectively.

     See *note variable annotation: 624, *note function annotation:
     1262, PEP 484(1) and PEP 526(2), which describe this functionality.

argument

     A value passed to a *note function: 1527. (or *note method: 4303.)
     when calling the function.  There are two kinds of argument:

        * `keyword argument': an argument preceded by an identifier
          (e.g.  ‘name=’) in a function call or passed as a value in a
          dictionary preceded by ‘**’.  For example, ‘3’ and ‘5’ are
          both keyword arguments in the following calls to *note
          complex(): 18a.:

               complex(real=3, imag=5)
               complex(**{'real': 3, 'imag': 5})

        * `positional argument': an argument that is not a keyword
          argument.  Positional arguments can appear at the beginning of
          an argument list and/or be passed as elements of an *note
          iterable: bb1. preceded by ‘*’.  For example, ‘3’ and ‘5’ are
          both positional arguments in the following calls:

               complex(3, 5)
               complex(*(3, 5))

     Arguments are assigned to the named local variables in a function
     body.  See the *note Calls: 651. section for the rules governing
     this assignment.  Syntactically, any expression can be used to
     represent an argument; the evaluated value is assigned to the local
     variable.

     See also the *note parameter: 1530. glossary entry, the FAQ
     question on *note the difference between arguments and parameters:
     424c, and PEP 362(3).

asynchronous context manager

     An object which controls the environment seen in an *note async
     with: 648. statement by defining *note __aenter__(): 149d. and
     *note __aexit__(): 149e. methods.  Introduced by PEP 492(4).

asynchronous generator

     A function which returns an *note asynchronous generator iterator:
     3634.  It looks like a coroutine function defined with *note async
     def: 285. except that it contains *note yield: 190. expressions for
     producing a series of values usable in an *note async for: 2e4.
     loop.

     Usually refers to an asynchronous generator function, but may refer
     to an `asynchronous generator iterator' in some contexts.  In cases
     where the intended meaning isn’t clear, using the full terms avoids
     ambiguity.

     An asynchronous generator function may contain *note await: 1a4.
     expressions as well as *note async for: 2e4, and *note async with:
     648. statements.

asynchronous generator iterator

     An object created by a *note asynchronous generator: 1508.
     function.

     This is an *note asynchronous iterator: 64a. which when called
     using the *note __anext__(): 149a. method returns an awaitable
     object which will execute the body of the asynchronous generator
     function until the next *note yield: 190. expression.

     Each *note yield: 190. temporarily suspends processing, remembering
     the location execution state (including local variables and pending
     try-statements).  When the `asynchronous generator iterator'
     effectively resumes with another awaitable returned by *note
     __anext__(): 149a, it picks up where it left off.  See PEP 492(5)
     and PEP 525(6).

asynchronous iterable

     An object, that can be used in an *note async for: 2e4. statement.
     Must return an *note asynchronous iterator: 64a. from its *note
     __aiter__(): 48c. method.  Introduced by PEP 492(7).

asynchronous iterator

     An object that implements the *note __aiter__(): 48c. and *note
     __anext__(): 149a. methods.  ‘__anext__’ must return an *note
     awaitable: 51e. object.  *note async for: 2e4. resolves the
     awaitables returned by an asynchronous iterator’s *note
     __anext__(): 149a. method until it raises a *note
     StopAsyncIteration: 1017. exception.  Introduced by PEP 492(8).

attribute

     A value associated with an object which is referenced by name using
     dotted expressions.  For example, if an object `o' has an attribute
     `a' it would be referenced as `o.a'.

awaitable

     An object that can be used in an *note await: 1a4. expression.  Can
     be a *note coroutine: 1a7. or an object with an *note __await__():
     647. method.  See also PEP 492(9).

BDFL

     Benevolent Dictator For Life, a.k.a.  Guido van Rossum(10),
     Python’s creator.

binary file

     A *note file object: b47. able to read and write *note bytes-like
     objects: 5ed.  Examples of binary files are files opened in binary
     mode (‘'rb'’, ‘'wb'’ or ‘'rb+'’), ‘sys.stdin.buffer’,
     ‘sys.stdout.buffer’, and instances of *note io.BytesIO: 7a0. and
     *note gzip.GzipFile: 6e2.

     See also *note text file: 12aa. for a file object able to read and
     write *note str: 335. objects.

bytes-like object

     An object that supports the *note Buffer Protocol: 15ec. and can
     export a C-*note contiguous: 16ba. buffer.  This includes all *note
     bytes: 336, *note bytearray: 337, and *note array.array: 456.
     objects, as well as many common *note memoryview: 25d. objects.
     Bytes-like objects can be used for various operations that work
     with binary data; these include compression, saving to a binary
     file, and sending over a socket.

     Some operations need the binary data to be mutable.  The
     documentation often refers to these as "read-write bytes-like
     objects".  Example mutable buffer objects include *note bytearray:
     337. and a *note memoryview: 25d. of a *note bytearray: 337.  Other
     operations require the binary data to be stored in immutable
     objects ("read-only bytes-like objects"); examples of these include
     *note bytes: 336. and a *note memoryview: 25d. of a *note bytes:
     336. object.

bytecode

     Python source code is compiled into bytecode, the internal
     representation of a Python program in the CPython interpreter.  The
     bytecode is also cached in ‘.pyc’ files so that executing the same
     file is faster the second time (recompilation from source to
     bytecode can be avoided).  This "intermediate language" is said to
     run on a *note virtual machine: 2789. that executes the machine
     code corresponding to each bytecode.  Do note that bytecodes are
     not expected to work between different Python virtual machines, nor
     to be stable between Python releases.

     A list of bytecode instructions can be found in the documentation
     for *note the dis module: 389f.

callback

     A subroutine function which is passed as an argument to be executed
     at some point in the future.

class

     A template for creating user-defined objects.  Class definitions
     normally contain method definitions which operate on instances of
     the class.

class variable

     A variable defined in a class and intended to be modified only at
     class level (i.e., not in an instance of the class).

coercion

     The implicit conversion of an instance of one type to another
     during an operation which involves two arguments of the same type.
     For example, ‘int(3.15)’ converts the floating point number to the
     integer ‘3’, but in ‘3+4.5’, each argument is of a different type
     (one int, one float), and both must be converted to the same type
     before they can be added or it will raise a *note TypeError: 193.
     Without coercion, all arguments of even compatible types would have
     to be normalized to the same value by the programmer, e.g.,
     ‘float(3)+4.5’ rather than just ‘3+4.5’.

complex number

     An extension of the familiar real number system in which all
     numbers are expressed as a sum of a real part and an imaginary
     part.  Imaginary numbers are real multiples of the imaginary unit
     (the square root of ‘-1’), often written ‘i’ in mathematics or ‘j’
     in engineering.  Python has built-in support for complex numbers,
     which are written with this latter notation; the imaginary part is
     written with a ‘j’ suffix, e.g., ‘3+1j’.  To get access to complex
     equivalents of the *note math: b2. module, use *note cmath: 19.
     Use of complex numbers is a fairly advanced mathematical feature.
     If you’re not aware of a need for them, it’s almost certain you can
     safely ignore them.

context manager

     An object which controls the environment seen in a *note with: 6ee.
     statement by defining *note __enter__(): c9a. and *note __exit__():
     c9b. methods.  See PEP 343(11).

context variable

     A variable which can have different values depending on its
     context.  This is similar to Thread-Local Storage in which each
     execution thread may have a different value for a variable.
     However, with context variables, there may be several contexts in
     one execution thread and the main usage for context variables is to
     keep track of variables in concurrent asynchronous tasks.  See
     *note contextvars: 25.

contiguous

     A buffer is considered contiguous exactly if it is either
     `C-contiguous' or `Fortran contiguous'.  Zero-dimensional buffers
     are C and Fortran contiguous.  In one-dimensional arrays, the items
     must be laid out in memory next to each other, in order of
     increasing indexes starting from zero.  In multidimensional
     C-contiguous arrays, the last index varies the fastest when
     visiting items in order of memory address.  However, in Fortran
     contiguous arrays, the first index varies the fastest.

coroutine

     Coroutines are a more generalized form of subroutines.  Subroutines
     are entered at one point and exited at another point.  Coroutines
     can be entered, exited, and resumed at many different points.  They
     can be implemented with the *note async def: 285. statement.  See
     also PEP 492(12).

coroutine function

     A function which returns a *note coroutine: 1a7. object.  A
     coroutine function may be defined with the *note async def: 285.
     statement, and may contain *note await: 1a4, *note async for: 2e4,
     and *note async with: 648. keywords.  These were introduced by PEP
     492(13).

CPython

     The canonical implementation of the Python programming language, as
     distributed on python.org(14).  The term "CPython" is used when
     necessary to distinguish this implementation from others such as
     Jython or IronPython.

decorator

     A function returning another function, usually applied as a
     function transformation using the ‘@wrapper’ syntax.  Common
     examples for decorators are *note classmethod(): 1d9. and *note
     staticmethod(): 1da.

     The decorator syntax is merely syntactic sugar, the following two
     function definitions are semantically equivalent:

          def f(...):
              ...
          f = staticmethod(f)

          @staticmethod
          def f(...):
              ...

     The same concept exists for classes, but is less commonly used
     there.  See the documentation for *note function definitions: 1261.
     and *note class definitions: c6f. for more about decorators.

descriptor

     Any object which defines the methods *note __get__(): 1440, *note
     __set__(): 1444, or *note __delete__(): 1445.  When a class
     attribute is a descriptor, its special binding behavior is
     triggered upon attribute lookup.  Normally, using `a.b' to get, set
     or delete an attribute looks up the object named `b' in the class
     dictionary for `a', but if `b' is a descriptor, the respective
     descriptor method gets called.  Understanding descriptors is a key
     to a deep understanding of Python because they are the basis for
     many features including functions, methods, properties, class
     methods, static methods, and reference to super classes.

     For more information about descriptors’ methods, see *note
     Implementing Descriptors: 4ee.

dictionary

     An associative array, where arbitrary keys are mapped to values.
     The keys can be any object with *note __hash__(): 345. and *note
     __eq__(): 344. methods.  Called a hash in Perl.

dictionary comprehension

     A compact way to process all or part of the elements in an iterable
     and return a dictionary with the results.  ‘results = {n: n ** 2
     for n in range(10)}’ generates a dictionary containing key ‘n’
     mapped to value ‘n ** 2’.  See *note Displays for lists, sets and
     dictionaries: 14f0.

dictionary view

     The objects returned from *note dict.keys(): c2f, *note
     dict.values(): c31, and *note dict.items(): c30. are called
     dictionary views.  They provide a dynamic view on the dictionary’s
     entries, which means that when the dictionary changes, the view
     reflects these changes.  To force the dictionary view to become a
     full list use ‘list(dictview)’.  See *note Dictionary view objects:
     16db.

docstring

     A string literal which appears as the first expression in a class,
     function or module.  While ignored when the suite is executed, it
     is recognized by the compiler and put into the ‘__doc__’ attribute
     of the enclosing class, function or module.  Since it is available
     via introspection, it is the canonical place for documentation of
     the object.

duck-typing

     A programming style which does not look at an object’s type to
     determine if it has the right interface; instead, the method or
     attribute is simply called or used ("If it looks like a duck and
     quacks like a duck, it must be a duck.")  By emphasizing interfaces
     rather than specific types, well-designed code improves its
     flexibility by allowing polymorphic substitution.  Duck-typing
     avoids tests using *note type(): 60d. or *note isinstance(): 454.
     (Note, however, that duck-typing can be complemented with *note
     abstract base classes: b38.)  Instead, it typically employs *note
     hasattr(): 44c. tests or *note EAFP: 1f51. programming.

EAFP

     Easier to ask for forgiveness than permission.  This common Python
     coding style assumes the existence of valid keys or attributes and
     catches exceptions if the assumption proves false.  This clean and
     fast style is characterized by the presence of many *note try: d77.
     and *note except: b43. statements.  The technique contrasts with
     the *note LBYL: 430c. style common to many other languages such as
     C.

expression

     A piece of syntax which can be evaluated to some value.  In other
     words, an expression is an accumulation of expression elements like
     literals, names, attribute access, operators or function calls
     which all return a value.  In contrast to many other languages, not
     all language constructs are expressions.  There are also *note
     statement: 1b97.s which cannot be used as expressions, such as
     *note while: 1232.  Assignments are also statements, not
     expressions.

extension module

     A module written in C or C++, using Python’s C API to interact with
     the core and with user code.

f-string

     String literals prefixed with ‘'f'’ or ‘'F'’ are commonly called
     "f-strings" which is short for *note formatted string literals:
     15d.  See also PEP 498(15).

file object

     An object exposing a file-oriented API (with methods such as
     ‘read()’ or ‘write()’) to an underlying resource.  Depending on the
     way it was created, a file object can mediate access to a real
     on-disk file or to another type of storage or communication device
     (for example standard input/output, in-memory buffers, sockets,
     pipes, etc.).  File objects are also called `file-like objects' or
     `streams'.

     There are actually three categories of file objects: raw *note
     binary files: 1caa, buffered *note binary files: 1caa. and *note
     text files: 12aa.  Their interfaces are defined in the *note io:
     a2. module.  The canonical way to create a file object is by using
     the *note open(): 4f5. function.

file-like object

     A synonym for *note file object: b47.

finder

     An object that tries to find the *note loader: 14c0. for a module
     that is being imported.

     Since Python 3.3, there are two types of finder: *note meta path
     finders: 9b6. for use with *note sys.meta_path: 5eb, and *note path
     entry finders: 9b7. for use with *note sys.path_hooks: 961.

     See PEP 302(16), PEP 420(17) and PEP 451(18) for much more detail.

floor division

     Mathematical division that rounds down to nearest integer.  The
     floor division operator is ‘//’.  For example, the expression ‘11
     // 4’ evaluates to ‘2’ in contrast to the ‘2.75’ returned by float
     true division.  Note that ‘(-11) // 4’ is ‘-3’ because that is
     ‘-2.75’ rounded `downward'.  See PEP 238(19).

function

     A series of statements which returns some value to a caller.  It
     can also be passed zero or more *note arguments: 1528. which may be
     used in the execution of the body.  See also *note parameter: 1530,
     *note method: 4303, and the *note Function definitions: 1261.
     section.

function annotation

     An *note annotation: 4301. of a function parameter or return value.

     Function annotations are usually used for *note type hints: 4302.:
     for example, this function is expected to take two *note int: 185.
     arguments and is also expected to have an *note int: 185. return
     value:

          def sum_two_numbers(a: int, b: int) -> int:
             return a + b

     Function annotation syntax is explained in section *note Function
     definitions: 1261.

     See *note variable annotation: 624. and PEP 484(20), which describe
     this functionality.

__future__

     A pseudo-module which programmers can use to enable new language
     features which are not compatible with the current interpreter.

     By importing the *note __future__: 0. module and evaluating its
     variables, you can see when a new feature was first added to the
     language and when it becomes the default:

          >>> import __future__
          >>> __future__.division
          _Feature((2, 2, 0, 'alpha', 2), (3, 0, 0, 'alpha', 0), 8192)

garbage collection

     The process of freeing memory when it is not used anymore.  Python
     performs garbage collection via reference counting and a cyclic
     garbage collector that is able to detect and break reference
     cycles.  The garbage collector can be controlled using the *note
     gc: 86. module.

generator

     A function which returns a *note generator iterator: 45c.  It looks
     like a normal function except that it contains *note yield: 190.
     expressions for producing a series of values usable in a for-loop
     or that can be retrieved one at a time with the *note next(): 687.
     function.

     Usually refers to a generator function, but may refer to a
     `generator iterator' in some contexts.  In cases where the intended
     meaning isn’t clear, using the full terms avoids ambiguity.

generator iterator

     An object created by a *note generator: 9a7. function.

     Each *note yield: 190. temporarily suspends processing, remembering
     the location execution state (including local variables and pending
     try-statements).  When the `generator iterator' resumes, it picks
     up where it left off (in contrast to functions which start fresh on
     every invocation).

generator expression

     An expression that returns an iterator.  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

     A function composed of multiple functions implementing the same
     operation for different types.  Which implementation should be used
     during a call is determined by the dispatch algorithm.

     See also the *note single dispatch: 1cc. glossary entry, the *note
     functools.singledispatch(): 38f. decorator, and PEP 443(21).

GIL

     See *note global interpreter lock: 50b.

global interpreter lock

     The mechanism used by the *note CPython: 143b. interpreter to
     assure that only one thread executes Python *note bytecode: 619. at
     a time.  This simplifies the CPython implementation by making the
     object model (including critical built-in types such as *note dict:
     1b9.) implicitly safe against concurrent access.  Locking the
     entire interpreter makes it easier for the interpreter to be
     multi-threaded, at the expense of much of the parallelism afforded
     by multi-processor machines.

     However, some extension modules, either standard or third-party,
     are designed so as to release the GIL when doing
     computationally-intensive tasks such as compression or hashing.
     Also, the GIL is always released when doing I/O.

     Past efforts to create a "free-threaded" interpreter (one which
     locks shared data at a much finer granularity) have not been
     successful because performance suffered in the common
     single-processor case.  It is believed that overcoming this
     performance issue would make the implementation much more
     complicated and therefore costlier to maintain.

hash-based pyc

     A bytecode cache file that uses the hash rather than the
     last-modified time of the corresponding source file to determine
     its validity.  See *note Cached bytecode invalidation: 32e.

hashable

     An object is `hashable' if it has a hash value which never changes
     during its lifetime (it needs a *note __hash__(): 345. method), and
     can be compared to other objects (it needs an *note __eq__(): 344.
     method).  Hashable objects which compare equal must have the same
     hash value.

     Hashability makes an object usable as a dictionary key and a set
     member, because these data structures use the hash value
     internally.

     Most of Python’s immutable built-in objects are hashable; mutable
     containers (such as lists or dictionaries) are not; immutable
     containers (such as tuples and frozensets) are only hashable if
     their elements are hashable.  Objects which are instances of
     user-defined classes are hashable by default.  They all compare
     unequal (except with themselves), and their hash value is derived
     from their *note id(): d8b.

IDLE

     An Integrated Development Environment for Python.  IDLE is a basic
     editor and interpreter environment which ships with the standard
     distribution of Python.

immutable

     An object with a fixed value.  Immutable objects include numbers,
     strings and tuples.  Such an object cannot be altered.  A new
     object has to be created if a different value has to be stored.
     They play an important role in places where a constant hash value
     is needed, for example as a key in a dictionary.

import path

     A list of locations (or *note path entries: 14d4.) that are
     searched by the *note path based finder: 14c5. for modules to
     import.  During import, this list of locations usually comes from
     *note sys.path: 48d, but for subpackages it may also come from the
     parent package’s ‘__path__’ attribute.

importing

     The process by which Python code in one module is made available to
     Python code in another module.

importer

     An object that both finds and loads a module; both a *note finder:
     14bf. and *note loader: 14c0. object.

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)’).

interpreted

     Python is an interpreted language, as opposed to a compiled one,
     though the distinction can be blurry because of the presence of the
     bytecode compiler.  This means that source files can be run
     directly without explicitly creating an executable which is then
     run.  Interpreted languages typically have a shorter
     development/debug cycle than compiled ones, though their programs
     generally also run more slowly.  See also *note interactive: 4311.

interpreter shutdown

     When asked to shut down, the Python interpreter enters a special
     phase where it gradually releases all allocated resources, such as
     modules and various critical internal structures.  It also makes
     several calls to the *note garbage collector: ecd.  This can
     trigger the execution of code in user-defined destructors or
     weakref callbacks.  Code executed during the shutdown phase can
     encounter various exceptions as the resources it relies on may not
     function anymore (common examples are library modules or the
     warnings machinery).

     The main reason for interpreter shutdown is that the ‘__main__’
     module or the script being run has finished executing.

iterable

     An object capable of returning its members one at a time.  Examples
     of iterables include all sequence types (such as *note list: 263,
     *note str: 335, and *note tuple: 483.) and some non-sequence types
     like *note dict: 1b9, *note file objects: b47, and objects of any
     classes you define with an *note __iter__(): 514. method or with a
     *note __getitem__(): 27d. method that implements *note Sequence:
     122d. semantics.

     Iterables can be used in a *note for: c35. loop and in many other
     places where a sequence is needed (*note zip(): c37, *note map():
     c32, ...).  When an iterable object is passed as an argument to the
     built-in function *note iter(): d2c, it returns an iterator for the
     object.  This iterator is good for one pass over the set of values.
     When using iterables, it is usually not necessary to call *note
     iter(): d2c. or deal with iterator objects yourself.  The ‘for’
     statement does that automatically for you, creating a temporary
     unnamed variable to hold the iterator for the duration of the loop.
     See also *note iterator: 1040, *note sequence: 122d, and *note
     generator: 9a7.

iterator

     An object representing a stream of data.  Repeated calls to the
     iterator’s *note __next__(): c69. method (or passing it to the
     built-in function *note next(): 687.) return successive items in
     the stream.  When no more data are available a *note StopIteration:
     48b. exception is raised instead.  At this point, the iterator
     object is exhausted and any further calls to its ‘__next__()’
     method just raise *note StopIteration: 48b. again.  Iterators are
     required to have an *note __iter__(): 514. method that returns the
     iterator object itself so every iterator is also iterable and may
     be used in most places where other iterables are accepted.  One
     notable exception is code which attempts multiple iteration passes.
     A container object (such as a *note list: 263.) produces a fresh
     new iterator each time you pass it to the *note iter(): d2c.
     function or use it in a *note for: c35. loop.  Attempting this with
     an iterator will just return the same exhausted iterator object
     used in the previous iteration pass, making it appear like an empty
     container.

     More information can be found in *note Iterator Types: 1461.

key function

     A key function or collation function is a callable that returns a
     value used for sorting or ordering.  For example, *note
     locale.strxfrm(): 3088. is used to produce a sort key that is aware
     of locale specific sort conventions.

     A number of tools in Python accept key functions to control how
     elements are ordered or grouped.  They include *note min(): 80e,
     *note max(): 80f, *note sorted(): 449, *note list.sort(): 44a,
     *note heapq.merge(): 6e4, *note heapq.nsmallest(): 1969, *note
     heapq.nlargest(): 1968, and *note itertools.groupby(): 1b47.

     There are several ways to create a key function.  For example.  the
     *note str.lower(): 1648. method can serve as a key function for
     case insensitive sorts.  Alternatively, a key function can be built
     from a *note lambda: c34. expression such as ‘lambda r: (r[0],
     r[2])’.  Also, the *note operator: c3. module provides three key
     function constructors: *note attrgetter(): 720, *note itemgetter():
     262, and *note methodcaller(): 721.  See the *note Sorting HOW TO:
     1606. for examples of how to create and use key functions.

keyword argument

     See *note argument: 1528.

lambda

     An anonymous inline function consisting of a single *note
     expression: 3628. which is evaluated when the function is called.
     The syntax to create a lambda function is ‘lambda [parameters]:
     expression’

LBYL

     Look before you leap.  This coding style explicitly tests for
     pre-conditions before making calls or lookups.  This style
     contrasts with the *note EAFP: 1f51. approach and is characterized
     by the presence of many *note if: dec. statements.

     In a multi-threaded environment, the LBYL approach can risk
     introducing a race condition between "the looking" and "the
     leaping".  For example, the code, ‘if key in mapping: return
     mapping[key]’ can fail if another thread removes `key' from
     `mapping' after the test, but before the lookup.  This issue can be
     solved with locks or by using the EAFP approach.

list

     A built-in Python *note sequence: 122d.  Despite its name it is
     more akin to an array in other languages than to a linked list
     since access to elements is O(1).

list comprehension

     A compact way to process all or part of the elements in a sequence
     and return a list with the results.  ‘result = ['{:#04x}'.format(x)
     for x in range(256) if x % 2 == 0]’ generates a list of strings
     containing even hex numbers (0x..)  in the range from 0 to 255.
     The *note if: dec. clause is optional.  If omitted, all elements in
     ‘range(256)’ are processed.

loader

     An object that loads a module.  It must define a method named
     ‘load_module()’.  A loader is typically returned by a *note finder:
     14bf.  See PEP 302(22) for details and *note importlib.abc.Loader:
     7c7. for an *note abstract base class: b38.

magic method

     An informal synonym for *note special method: 3663.

mapping

     A container object that supports arbitrary key lookups and
     implements the methods specified in the *note Mapping: 1949. or
     *note MutableMapping: 9f4. *note abstract base classes: 192c.
     Examples include *note dict: 1b9, *note collections.defaultdict:
     b3f, *note collections.OrderedDict: 1ba. and *note
     collections.Counter: 9df.

meta path finder

     A *note finder: 14bf. returned by a search of *note sys.meta_path:
     5eb.  Meta path finders are related to, but different from *note
     path entry finders: 9b7.

     See *note importlib.abc.MetaPathFinder: 9b8. for the methods that
     meta path finders implement.

metaclass

     The class of a class.  Class definitions create a class name, a
     class dictionary, and a list of base classes.  The metaclass is
     responsible for taking those three arguments and creating the
     class.  Most object oriented programming languages provide a
     default implementation.  What makes Python special is that it is
     possible to create custom metaclasses.  Most users never need this
     tool, but when the need arises, metaclasses can provide powerful,
     elegant solutions.  They have been used for logging attribute
     access, adding thread-safety, tracking object creation,
     implementing singletons, and many other tasks.

     More information can be found in *note Metaclasses: 144d.

method

     A function which is defined inside a class body.  If called as an
     attribute of an instance of that class, the method will get the
     instance object as its first *note argument: 1528. (which is
     usually called ‘self’).  See *note function: 1527. and *note nested
     scope: 15f0.

method resolution order

     Method Resolution Order is the order in which base classes are
     searched for a member during lookup.  See The Python 2.3 Method
     Resolution Order(23) for details of the algorithm used by the
     Python interpreter since the 2.3 release.

module

     An object that serves as an organizational unit of Python code.
     Modules have a namespace containing arbitrary Python objects.
     Modules are loaded into Python by the process of *note importing:
     14b3.

     See also *note package: ebb.

module spec

     A namespace containing the import-related information used to load
     a module.  An instance of *note importlib.machinery.ModuleSpec:
     14cb.

MRO

     See *note method resolution order: 1609.

mutable

     Mutable objects can change their value but keep their *note id():
     d8b.  See also *note immutable: 1227.

named tuple

     The term "named tuple" applies to any type or class that inherits
     from tuple and whose indexable elements are also accessible using
     named attributes.  The type or class may have other features as
     well.

     Several built-in types are named tuples, including the values
     returned by *note time.localtime(): f52. and *note os.stat(): 1f2.
     Another example is *note sys.float_info: fc6.:

          >>> 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

     Some named tuples are built-in types (such as the above examples).
     Alternatively, a named tuple can be created from a regular class
     definition that inherits from *note tuple: 483. and that defines
     named fields.  Such a class can be written by hand or it can be
     created with the factory function *note collections.namedtuple():
     1b8.  The latter technique also adds some extra methods that may
     not be found in hand-written or built-in named tuples.

namespace

     The place where a variable is stored.  Namespaces are implemented
     as dictionaries.  There are the local, global and built-in
     namespaces as well as nested namespaces in objects (in methods).
     Namespaces support modularity by preventing naming conflicts.  For
     instance, the functions *note builtins.open: 4f5. and *note
     os.open(): 66a. are distinguished by their namespaces.  Namespaces
     also aid readability and maintainability by making it clear which
     module implements a function.  For instance, writing *note
     random.seed(): c0d. or *note itertools.islice(): 3a7. makes it
     clear that those functions are implemented by the *note random: dd.
     and *note itertools: a4. modules, respectively.

namespace package

     A PEP 420(24) *note package: ebb. which serves only as a container
     for subpackages.  Namespace packages may have no physical
     representation, and specifically are not like a *note regular
     package: 14b7. because they have no ‘__init__.py’ file.

     See also *note module: 14b2.

nested scope

     The ability to refer to a variable in an enclosing definition.  For
     instance, a function defined inside another function can refer to
     variables in the outer function.  Note that nested scopes by
     default work only for reference and not for assignment.  Local
     variables both read and write in the innermost scope.  Likewise,
     global variables read and write to the global namespace.  The *note
     nonlocal: c44. allows writing to outer scopes.

new-style class

     Old name for the flavor of classes now used for all class objects.
     In earlier Python versions, only new-style classes could use
     Python’s newer, versatile features like *note __slots__: e32,
     descriptors, properties, *note __getattribute__(): 44e, class
     methods, and static methods.

object

     Any data with state (attributes or value) and defined behavior
     (methods).  Also the ultimate base class of any *note new-style
     class: 1cb2.

package

     A Python *note module: 14b2. which can contain submodules or
     recursively, subpackages.  Technically, a package is a Python
     module with an ‘__path__’ attribute.

     See also *note regular package: 14b7. and *note namespace package:
     14b8.

parameter

     A named entity in a *note function: 1527. (or method) definition
     that specifies an *note argument: 1528. (or in some cases,
     arguments) that the function can accept.  There are five kinds of
     parameter:

        * `positional-or-keyword': specifies an argument that can be
          passed either *note positionally: 1528. or as a *note keyword
          argument: 1528.  This is the default kind of parameter, for
          example `foo' and `bar' in the following:

               def func(foo, bar=None): ...

        * `positional-only': specifies an argument that can be supplied
          only by position.  Positional-only parameters can be defined
          by including a ‘/’ character in the parameter list of the
          function definition after them, for example `posonly1' and
          `posonly2' in the following:

               def func(posonly1, posonly2, /, positional_or_keyword): ...

        * `keyword-only': specifies an argument that can be supplied
          only by keyword.  Keyword-only parameters can be defined by
          including a single var-positional parameter or bare ‘*’ in the
          parameter list of the function definition before them, for
          example `kw_only1' and `kw_only2' in the following:

               def func(arg, *, kw_only1, kw_only2): ...

        * `var-positional': specifies that an arbitrary sequence of
          positional arguments can be provided (in addition to any
          positional arguments already accepted by other parameters).
          Such a parameter can be defined by prepending the parameter
          name with ‘*’, for example `args' in the following:

               def func(*args, **kwargs): ...

        * `var-keyword': specifies that arbitrarily many keyword
          arguments can be provided (in addition to any keyword
          arguments already accepted by other parameters).  Such a
          parameter can be defined by prepending the parameter name with
          ‘**’, for example `kwargs' in the example above.

     Parameters can specify both optional and required arguments, as
     well as default values for some optional arguments.

     See also the *note argument: 1528. glossary entry, the FAQ question
     on *note the difference between arguments and parameters: 424c, the
     *note inspect.Parameter: 6f9. class, the *note Function
     definitions: 1261. section, and PEP 362(25).

path entry

     A single location on the *note import path: 14c2. which the *note
     path based finder: 14c5. consults to find modules for importing.

path entry finder

     A *note finder: 14bf. returned by a callable on *note
     sys.path_hooks: 961. (i.e.  a *note path entry hook: 14d6.) which
     knows how to locate modules given a *note path entry: 14d4.

     See *note importlib.abc.PathEntryFinder: 9b9. for the methods that
     path entry finders implement.

path entry hook

     A callable on the ‘sys.path_hook’ list which returns a *note path
     entry finder: 9b7. if it knows how to find modules on a specific
     *note path entry: 14d4.

path based finder

     One of the default *note meta path finders: 9b6. which searches an
     *note import path: 14c2. for modules.

path-like object

     An object representing a file system path.  A path-like object is
     either a *note str: 335. or *note bytes: 336. object representing a
     path, or an object implementing the *note os.PathLike: 4f0.
     protocol.  An object that supports the *note os.PathLike: 4f0.
     protocol can be converted to a *note str: 335. or *note bytes: 336.
     file system path by calling the *note os.fspath(): 4f2. function;
     *note os.fsdecode(): 4f3. and *note os.fsencode(): 4f4. can be used
     to guarantee a *note str: 335. or *note bytes: 336. result instead,
     respectively.  Introduced by PEP 519(26).

PEP

     Python Enhancement Proposal.  A PEP is a design document providing
     information to the Python community, or describing a new feature
     for Python or its processes or environment.  PEPs should provide a
     concise technical specification and a rationale for proposed
     features.

     PEPs are intended to be the primary mechanisms for proposing major
     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.

     See PEP 1(27).

portion

     A set of files in a single directory (possibly stored in a zip
     file) that contribute to a namespace package, as defined in PEP
     420(28).

positional argument

     See *note argument: 1528.

provisional API

     A provisional API is one which has been deliberately excluded from
     the standard library’s backwards compatibility guarantees.  While
     major changes to such interfaces are not expected, as long as they
     are marked provisional, backwards incompatible changes (up to and
     including removal of the interface) may occur if deemed necessary
     by core developers.  Such changes will not be made gratuitously –
     they will occur only if serious fundamental flaws are uncovered
     that were missed prior to the inclusion of the API.

     Even for provisional APIs, backwards incompatible changes are seen
     as a "solution of last resort" - every attempt will still be made
     to find a backwards compatible resolution to any identified
     problems.

     This process allows the standard library to continue to evolve over
     time, without locking in problematic design errors for extended
     periods of time.  See PEP 411(29) for more details.

provisional package

     See *note provisional API: 34d.

Python 3000

     Nickname for the Python 3.x release line (coined long ago when the
     release of version 3 was something in the distant future.)  This is
     also abbreviated "Py3k".

Pythonic

     An idea or piece of code which closely follows the most common
     idioms of the Python language, rather than implementing code using
     concepts common to other languages.  For example, a common idiom in
     Python is to loop over all elements of an iterable using a *note
     for: c35. statement.  Many other languages don’t have this type of
     construct, so people unfamiliar with Python sometimes use a
     numerical counter instead:

          for i in range(len(food)):
              print(food[i])

     As opposed to the cleaner, Pythonic method:

          for piece in food:
              print(piece)

qualified name

     A dotted name showing the "path" from a module’s global scope to a
     class, function or method defined in that module, as defined in PEP
     3155(30).  For top-level functions and classes, the qualified name
     is the same as the object’s name:

          >>> class C:
          ...     class D:
          ...         def meth(self):
          ...             pass
          ...
          >>> C.__qualname__
          'C'
          >>> C.D.__qualname__
          'C.D'
          >>> C.D.meth.__qualname__
          'C.D.meth'

     When used to refer to modules, the `fully qualified name' means the
     entire dotted path to the module, including any parent packages,
     e.g.  ‘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.  Reference counting is
     generally not visible to Python code, but it is a key element of
     the *note CPython: 143b. implementation.  The *note sys: fe. module
     defines a *note getrefcount(): 3632. function that programmers can
     call to return the reference count for a particular object.

regular package

     A traditional *note package: ebb, such as a directory containing an
     ‘__init__.py’ file.

     See also *note namespace package: 14b8.

__slots__

     A declaration inside a class that saves memory by pre-declaring
     space for instance attributes and eliminating instance
     dictionaries.  Though popular, the technique is somewhat tricky to
     get right and is best reserved for rare cases where there are large
     numbers of instances in a memory-critical application.

sequence

     An *note iterable: bb1. which supports efficient element access
     using integer indices via the *note __getitem__(): 27d. special
     method and defines a *note __len__(): dd0. method that returns the
     length of the sequence.  Some built-in sequence types are *note
     list: 263, *note str: 335, *note tuple: 483, and *note bytes: 336.
     Note that *note dict: 1b9. also supports *note __getitem__(): 27d.
     and *note __len__(): dd0, but is considered a mapping rather than a
     sequence because the lookups use arbitrary *note immutable: 1227.
     keys rather than integers.

     The *note collections.abc.Sequence: 1635. abstract base class
     defines a much richer interface that goes beyond just *note
     __getitem__(): 27d. and *note __len__(): dd0, adding ‘count()’,
     ‘index()’, *note __contains__(): d2d, and *note __reversed__():
     534.  Types that implement this expanded interface can be
     registered explicitly using *note register(): 9d6.

set comprehension

     A compact way to process all or part of the elements in an iterable
     and return a set with the results.  ‘results = {c for c in
     'abracadabra' if c not in 'abc'}’ generates the set of strings
     ‘{'r', 'd'}’.  See *note Displays for lists, sets and dictionaries:
     14f0.

single dispatch

     A form of *note generic function: 1cb. dispatch where the
     implementation is chosen based on the type of a single argument.

slice

     An object usually containing a portion of a *note sequence: 122d.
     A slice is created using the subscript notation, ‘[]’ with colons
     between numbers when several are given, such as in
     ‘variable_name[1:3:5]’.  The bracket (subscript) notation uses
     *note slice: e09. objects internally.

special method

     A method that is called implicitly by Python to execute a certain
     operation on a type, such as addition.  Such methods have names
     starting and ending with double underscores.  Special methods are
     documented in *note Special method names: 513.

statement

     A statement is part of a suite (a "block" of code).  A statement is
     either an *note expression: 3628. or one of several constructs with
     a keyword, such as *note if: dec, *note while: 1232. or *note for:
     c35.

text encoding

     A codec which encodes Unicode strings to bytes.

text file

     A *note file object: b47. able to read and write *note str: 335.
     objects.  Often, a text file actually accesses a byte-oriented
     datastream and handles the *note text encoding: 1600.
     automatically.  Examples of text files are files opened in text
     mode (‘'r'’ or ‘'w'’), *note sys.stdin: 312, *note sys.stdout: 313,
     and instances of *note io.StringIO: 832.

     See also *note binary file: 1caa. for a file object able to read
     and write *note bytes-like objects: 5ed.

triple-quoted string

     A string which is bound by three instances of either a quotation
     mark (") or an apostrophe (’).  While they don’t provide any
     functionality not available with single-quoted strings, they are
     useful for a number of reasons.  They allow you to include
     unescaped single and double quotes within a string and they can
     span multiple lines without the use of the continuation character,
     making them especially useful when writing docstrings.

type

     The type of a Python object determines what kind of object it is;
     every object has a type.  An object’s type is accessible as its
     *note __class__: e0f. attribute or can be retrieved with
     ‘type(obj)’.

type alias

     A synonym for a type, created by assigning the type to an
     identifier.

     Type aliases are useful for simplifying *note type hints: 4302.
     For example:

          from typing import List, Tuple

          def remove_gray_shades(
                  colors: List[Tuple[int, int, int]]) -> List[Tuple[int, int, int]]:
              pass

     could be made more readable like this:

          from typing import List, Tuple

          Color = Tuple[int, int, int]

          def remove_gray_shades(colors: List[Color]) -> List[Color]:
              pass

     See *note typing: 11a. and PEP 484(31), which describe this
     functionality.

type hint

     An *note annotation: 4301. that specifies the expected type for a
     variable, a class attribute, or a function parameter or return
     value.

     Type hints are optional and are not enforced by Python but they are
     useful to static type analysis tools, and aid IDEs with code
     completion and refactoring.

     Type hints of global variables, class attributes, and functions,
     but not local variables, can be accessed using *note
     typing.get_type_hints(): 30f.

     See *note typing: 11a. and PEP 484(32), which describe this
     functionality.

universal newlines

     A manner of interpreting text streams in which all of the following
     are recognized as ending a line: the Unix end-of-line convention
     ‘'\n'’, the Windows convention ‘'\r\n'’, and the old Macintosh
     convention ‘'\r'’.  See PEP 278(33) and PEP 3116(34), as well as
     *note bytes.splitlines(): 16a8. for an additional use.

variable annotation

     An *note annotation: 4301. of a variable or a class attribute.

     When annotating a variable or a class attribute, assignment is
     optional:

          class C:
              field: 'annotation'

     Variable annotations are usually used for *note type hints: 4302.:
     for example this variable is expected to take *note int: 185.
     values:

          count: int = 0

     Variable annotation syntax is explained in section *note Annotated
     assignment statements: 157b.

     See *note function annotation: 1262, PEP 484(35) and PEP 526(36),
     which describe this functionality.

virtual environment

     A cooperatively isolated runtime environment that allows Python
     users and applications to install and upgrade Python distribution
     packages without interfering with the behaviour of other Python
     applications running on the same system.

     See also *note venv: 126.

virtual machine

     A computer defined entirely in software.  Python’s virtual machine
     executes the *note bytecode: 619. emitted by the bytecode compiler.

Zen of Python

     Listing of Python design principles and philosophies that are
     helpful in understanding and using the language.  The listing can
     be found by typing "‘import this’" at the interactive prompt.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0484

   (2) https://www.python.org/dev/peps/pep-0526

   (3) https://www.python.org/dev/peps/pep-0362

   (4) https://www.python.org/dev/peps/pep-0492

   (5) https://www.python.org/dev/peps/pep-0492

   (6) https://www.python.org/dev/peps/pep-0525

   (7) https://www.python.org/dev/peps/pep-0492

   (8) https://www.python.org/dev/peps/pep-0492

   (9) https://www.python.org/dev/peps/pep-0492

   (10) https://gvanrossum.github.io/

   (11) https://www.python.org/dev/peps/pep-0343

   (12) https://www.python.org/dev/peps/pep-0492

   (13) https://www.python.org/dev/peps/pep-0492

   (14) https://www.python.org

   (15) https://www.python.org/dev/peps/pep-0498

   (16) https://www.python.org/dev/peps/pep-0302

   (17) https://www.python.org/dev/peps/pep-0420

   (18) https://www.python.org/dev/peps/pep-0451

   (19) https://www.python.org/dev/peps/pep-0238

   (20) https://www.python.org/dev/peps/pep-0484

   (21) https://www.python.org/dev/peps/pep-0443

   (22) https://www.python.org/dev/peps/pep-0302

   (23) https://www.python.org/download/releases/2.3/mro/

   (24) https://www.python.org/dev/peps/pep-0420

   (25) https://www.python.org/dev/peps/pep-0362

   (26) https://www.python.org/dev/peps/pep-0519

   (27) https://www.python.org/dev/peps/pep-0001

   (28) https://www.python.org/dev/peps/pep-0420

   (29) https://www.python.org/dev/peps/pep-0411

   (30) https://www.python.org/dev/peps/pep-3155

   (31) https://www.python.org/dev/peps/pep-0484

   (32) https://www.python.org/dev/peps/pep-0484

   (33) https://www.python.org/dev/peps/pep-0278

   (34) https://www.python.org/dev/peps/pep-3116

   (35) https://www.python.org/dev/peps/pep-0484

   (36) https://www.python.org/dev/peps/pep-0526


File: python.info,  Node: 關於這些說明文件,  Next: 處理 Bug,  Prev: Glossary,  Up: Top

13 關於這些說明文件
*******************

這些說明文件是透過 Sphinx(1) （一個專為 Python 說明文件所撰寫的文件處理
器）將使用 reStructuredText(2) 撰寫的原始檔轉換而成。

如同 Python 自身，透過自願者的努力下產出文件與封裝後自動化執行工具。若想
要回報臭蟲，請見 *note 處理 Bug: 3b90. 頁面，內含相關資訊。我們永遠歡迎
新的自願者加入！

致謝：

   * Fred L. Drake, Jr.，原始 Python 文件工具集的創造者以及一大部份內容
     的作者。

   * 創造 reStructuredText 和 Docutils 工具組的 Docutils(3) 專案；

   * Fredrik Lundh 先生，Sphinx 從他的 Alternative Python Reference(4) 計
     劃中獲得許多的好主意。

* Menu:

* Python 文件的貢獻者們::

   ---------- Footnotes ----------

   (1) http://sphinx-doc.org/

   (2) http://docutils.sourceforge.net/rst.html

   (3) http://docutils.sourceforge.net/

   (4) http://effbot.org/zone/pyref.htm


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.8/Misc/ACKS


File: python.info,  Node: 處理 Bug,  Next: 版權宣告,  Prev: 關於這些說明文件,  Up: Top

14 處理 Bug
***********

Python 已經是一個以穩定著稱的成熟程式語言。為了維持「穩定」此信譽，開發
者們想知道任何您發現的缺失。

有時候自己直接修復 bug 並且送出一個修正給 Python 會比較快，因為這樣會加
速流程而且不會困擾到太多人。學習如何*note 貢獻給 Python: 4325.。

* Menu:

* 說明文件錯誤::
* 使用 Python 議題追蹤::
* 開始讓自己貢獻 Python::


File: python.info,  Node: 說明文件錯誤,  Next: 使用 Python 議題追蹤,  Up: 處理 Bug

14.1 說明文件錯誤
=================

If you find a bug in this documentation or would like to propose an
improvement, please submit a bug report on the *note tracker: 4327.  If
you have a suggestion on how to fix it, include that as well.

If you’re short on time, you can also email documentation bug reports to
<docs@python.org> (behavioral bugs can be sent to
<python-list@python.org>).  ’docs@’ is a mailing list run by volunteers;
your request will be noticed, though it may take a while to be
processed.

也參考
......

Documentation bugs(1)

     A list of documentation bugs that have been submitted to the Python
     issue tracker.

Issue Tracking(2)

     Overview of the process involved in reporting an improvement on the
     tracker.

Helping with Documentation(3)

     Comprehensive guide for individuals that are interested in
     contributing to Python documentation.

   ---------- Footnotes ----------

   (1) 
https://bugs.python.org/issue?@filter=status&@filter=components&components=4&status=1&@columns=id,activity,title,status&@sort=-activity

   (2) https://devguide.python.org/tracker/

   (3) 
https://devguide.python.org/docquality/#helping-with-documentation


File: python.info,  Node: 使用 Python 議題追蹤,  Next: 開始讓自己貢獻 Python,  Prev: 說明文件錯誤,  Up: 處理 Bug

14.2 使用 Python 議題追蹤
=========================

Bug reports for Python itself should be submitted via the Python Bug
Tracker (‘https://bugs.python.org/’).  The bug tracker offers a Web form
which allows pertinent information to be entered and submitted to the
developers.

The first step in filing a report is to determine whether the problem
has already been reported.  The advantage in doing so, aside from saving
the developers time, is that you learn what has been done to fix it; it
may be that the problem has already been fixed for the next release, or
additional information is needed (in which case you are welcome to
provide it if you can!).  To do this, search the bug database using the
search box on the top of the page.

If the problem you’re reporting is not already in the bug tracker, go
back to the Python Bug Tracker and log in.  If you don’t already have a
tracker account, select the "Register" link or, if you use OpenID, one
of the OpenID provider logos in the sidebar.  It is not possible to
submit a bug report anonymously.

Being now logged in, you can submit a bug.  Select the "Create New" link
in the sidebar to open the bug reporting form.

The submission form has a number of fields.  For the "Title" field,
enter a `very' short description of the problem; less than ten words is
good.  In the "Type" field, select the type of your problem; also select
the "Component" and "Versions" to which the bug relates.

In the "Comment" field, describe the problem in detail, including what
you expected to happen and what did happen.  Be sure to include whether
any extension modules were involved, and what hardware and software
platform you were using (including version information as appropriate).

Each bug report will be assigned to a developer who will determine what
needs to be done to correct the problem.  You will receive an update
each time action is taken on the bug.

也參考
......

How to Report Bugs Effectively(1)

     Article which goes into some detail about how to create a useful
     bug report.  This describes what kind of information is useful and
     why it is useful.

Bug Report Writing Guidelines(2)

     Information about writing a good bug report.  Some of this is
     specific to the Mozilla project, but describes general good
     practices.

   ---------- Footnotes ----------

   (1) https://www.chiark.greenend.org.uk/~sgtatham/bugs.html

   (2) 
https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines


File: python.info,  Node: 開始讓自己貢獻 Python,  Prev: 使用 Python 議題追蹤,  Up: 處理 Bug

14.3 開始讓自己貢獻 Python
==========================

Beyond just reporting bugs that you find, you are also welcome to submit
patches to fix them.  You can find more information on how to get
started patching Python in the Python Developer’s Guide(1).  If you have
questions, the core-mentorship mailing list(2) is a friendly place to
get answers to any and all questions pertaining to the process of fixing
issues in 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-2021 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 歷史與授權: 432d.。


File: python.info,  Node: 歷史與授權,  Next: 發布 Python 模組（舊版）,  Prev: 版權宣告,  Up: Top

16 歷史與授權
*************

* Menu:

* History of the software::
* Terms and conditions for accessing or otherwise using Python::
* Licenses and Acknowledgements for Incorporated Software::


File: python.info,  Node: History of the software,  Next: Terms and conditions for accessing or otherwise using Python,  Up: 歷史與授權

16.1 History of the software
============================

Python was created in the early 1990s by Guido van Rossum at Stichting
Mathematisch Centrum (CWI, see ‘https://www.cwi.nl/’) in the Netherlands
as a successor of a language called ABC. Guido remains Python’s
principal author, although it includes many contributions from others.

In 1995, Guido continued his work on Python at the Corporation for
National Research Initiatives (CNRI, see
‘https://www.cnri.reston.va.us/’) in Reston, Virginia where he released
several versions of the software.

In May 2000, Guido and the Python core development team moved to
BeOpen.com to form the BeOpen PythonLabs team.  In October of the same
year, the PythonLabs team moved to Digital Creations (now Zope
Corporation; see ‘https://www.zope.org/’).  In 2001, the Python Software
Foundation (PSF, see ‘https://www.python.org/psf/’) was formed, a
non-profit organization created specifically to own Python-related
Intellectual Property.  Zope Corporation is a sponsoring member of the
PSF.

All Python releases are Open Source (see ‘https://opensource.org/’ for
the Open Source Definition).  Historically, most, but not all, Python
releases have also been GPL-compatible; the table below summarizes the
various releases.

Release              Derived from       Year             Owner            GPL compatible?
                                                                          
------------------------------------------------------------------------------------------------
                                                                          
0.9.0 thru 1.2       n/a                1991-1995        CWI              yes
                                                                          
                                                                          
1.3 thru 1.5.2       1.2                1995-1999        CNRI             yes
                                                                          
                                                                          
1.6                  1.5.2              2000             CNRI             no
                                                                          
                                                                          
2.0                  1.6                2000             BeOpen.com       no
                                                                          
                                                                          
1.6.1                1.6                2001             CNRI             no
                                                                          
                                                                          
2.1                  2.0+1.6.1          2001             PSF              no
                                                                          
                                                                          
2.0.1                2.0+1.6.1          2001             PSF              yes
                                                                          
                                                                          
2.1.1                2.1+2.0.1          2001             PSF              yes
                                                                          
                                                                          
2.1.2                2.1.1              2002             PSF              yes
                                                                          
                                                                          
2.1.3                2.1.2              2002             PSF              yes
                                                                          
                                                                          
2.2 and above        2.1.1              2001-now         PSF              yes
                                                                          

     備註: GPL-compatible doesn’t mean that we’re distributing Python
     under the GPL. All Python licenses, unlike the GPL, let you
     distribute a modified version without making your changes open
     source.  The GPL-compatible licenses make it possible to combine
     Python with other software that is released under the GPL; the
     others don’t.

Thanks to the many outside volunteers who have worked under Guido’s
direction to make these releases possible.


File: python.info,  Node: Terms and conditions for accessing or otherwise using Python,  Next: Licenses and Acknowledgements for Incorporated Software,  Prev: History of the software,  Up: 歷史與授權

16.2 Terms and conditions for accessing or otherwise using Python
=================================================================

Python software and documentation are licensed under the *note PSF
License Agreement: 4332.

Starting with Python 3.8.6, examples, recipes, and other code in the
documentation are dual licensed under the PSF License Agreement and the
*note Zero-Clause BSD license: 4333.

Some software incorporated into Python is under different licenses.  The
licenses are listed with code falling under that license.  See *note
Licenses and Acknowledgements for Incorporated Software: 4334. for an
incomplete list of these licenses.

* Menu:

* PSF LICENSE AGREEMENT FOR PYTHON 3.8.11: PSF LICENSE AGREEMENT FOR PYTHON 3 8 11.
* BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0: BEOPEN COM LICENSE AGREEMENT FOR PYTHON 2 0.
* CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1: CNRI LICENSE AGREEMENT FOR PYTHON 1 6 1.
* CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2: CWI LICENSE AGREEMENT FOR PYTHON 0 9 0 THROUGH 1 2.
* ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON 3.8.11 DOCUMENTATION: ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON 3 8 11 DOCUMENTATION.


File: python.info,  Node: PSF LICENSE AGREEMENT FOR PYTHON 3 8 11,  Next: BEOPEN COM LICENSE AGREEMENT FOR PYTHON 2 0,  Up: Terms and conditions for accessing or otherwise using Python

16.2.1 PSF LICENSE AGREEMENT FOR PYTHON 3.8.11
----------------------------------------------

     1. This LICENSE AGREEMENT is between the Python Software Foundation ("PSF"), and
        the Individual or Organization ("Licensee") accessing and otherwise using Python
        3.8.11 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.8.11 alone or in any derivative
        version, provided, however, that PSF's License Agreement and PSF's notice of
        copyright, i.e., "Copyright © 2001-2021 Python Software Foundation; All Rights
        Reserved" are retained in Python 3.8.11 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.8.11 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.8.11.

     4. PSF is making Python 3.8.11 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.8.11 WILL NOT INFRINGE ANY THIRD PARTY RIGHTS.

     5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON 3.8.11
        FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS A RESULT OF
        MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 3.8.11, 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.8.11, Licensee agrees
        to be bound by the terms and conditions of this License Agreement.


File: python.info,  Node: BEOPEN COM LICENSE AGREEMENT FOR PYTHON 2 0,  Next: CNRI LICENSE AGREEMENT FOR PYTHON 1 6 1,  Prev: PSF LICENSE AGREEMENT FOR PYTHON 3 8 11,  Up: Terms and conditions for accessing or otherwise using Python

16.2.2 BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
--------------------------------------------------

BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 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: CNRI LICENSE AGREEMENT FOR PYTHON 1 6 1,  Next: CWI LICENSE AGREEMENT FOR PYTHON 0 9 0 THROUGH 1 2,  Prev: BEOPEN COM LICENSE AGREEMENT FOR PYTHON 2 0,  Up: Terms and conditions for accessing or otherwise using Python

16.2.3 CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
----------------------------------------------

     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: CWI LICENSE AGREEMENT FOR PYTHON 0 9 0 THROUGH 1 2,  Next: ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON 3 8 11 DOCUMENTATION,  Prev: CNRI LICENSE AGREEMENT FOR PYTHON 1 6 1,  Up: Terms and conditions for accessing or otherwise using Python

16.2.4 CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
---------------------------------------------------------

     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: ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON 3 8 11 DOCUMENTATION,  Prev: CWI LICENSE AGREEMENT FOR PYTHON 0 9 0 THROUGH 1 2,  Up: Terms and conditions for accessing or otherwise using Python

16.2.5 ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON 3.8.11 DOCUMENTATION
--------------------------------------------------------------------------

     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: Licenses and Acknowledgements for Incorporated Software,  Prev: Terms and conditions for accessing or otherwise using Python,  Up: 歷史與授權

16.3 Licenses and Acknowledgements for Incorporated Software
============================================================

This section is an incomplete, but growing list of licenses and
acknowledgements for third-party software incorporated in the Python
distribution.

* Menu:

* Mersenne Twister::
* Sockets: Sockets<2>.
* Asynchronous socket services::
* Cookie management::
* Execution tracing::
* UUencode and UUdecode functions::
* XML Remote Procedure Calls::
* test_epoll::
* Select kqueue::
* SipHash24::
* strtod and dtoa::
* OpenSSL::
* expat::
* libffi::
* zlib: zlib<3>.
* cfuhash::
* libmpdec::
* W3C C14N test suite::


File: python.info,  Node: Mersenne Twister,  Next: Sockets<2>,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.1 Mersenne Twister
-----------------------

The ‘_random’ module includes code based on a download from
‘http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/MT2002/emt19937ar.html’.
The following are the verbatim comments from the original code:

     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: Asynchronous socket services,  Prev: Mersenne Twister,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.2 Sockets
--------------

The *note socket: f0. module uses the functions, ‘getaddrinfo()’, and
‘getnameinfo()’, which are coded in separate source files from the WIDE
Project, ‘http://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: Asynchronous socket services,  Next: Cookie management,  Prev: Sockets<2>,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.3 Asynchronous socket services
-----------------------------------

The *note asynchat: 9. and *note asyncore: b. modules contain the
following notice:

     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 management,  Next: Execution tracing,  Prev: Asynchronous socket services,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.4 Cookie management
------------------------

The *note http.cookies: 96. module contains the following notice:

     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: Execution tracing,  Next: UUencode and UUdecode functions,  Prev: Cookie management,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.5 Execution tracing
------------------------

The *note trace: 113. module contains the following notice:

     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 and UUdecode functions,  Next: XML Remote Procedure Calls,  Prev: Execution tracing,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.6 UUencode and UUdecode functions
--------------------------------------

The *note uu: 124. module 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 Remote Procedure Calls,  Next: test_epoll,  Prev: UUencode and UUdecode functions,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.7 XML Remote Procedure Calls
---------------------------------

The *note xmlrpc.client: 140. module contains the following notice:

         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 Remote Procedure Calls,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.8 test_epoll
-----------------

The ‘test_epoll’ module contains the following notice:

     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: Licenses and Acknowledgements for Incorporated Software

16.3.9 Select kqueue
--------------------

The *note select: e6. module contains the following notice for the
kqueue interface:

     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 and dtoa,  Prev: Select kqueue,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.10 SipHash24
-----------------

The file ‘Python/pyhash.c’ contains Marek Majkowski’ implementation of
Dan Bernstein’s SipHash24 algorithm.  It contains the following note:

     <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 and dtoa,  Next: OpenSSL,  Prev: SipHash24,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.11 strtod and dtoa
-----------------------

The file ‘Python/dtoa.c’, which supplies C functions dtoa and strtod for
conversion of C doubles to and from strings, is derived from the file of
the same name by David M. Gay, currently available from
‘http://www.netlib.org/fp/’.  The original file, as retrieved on March
16, 2009, contains the following copyright and licensing notice:

     /****************************************************************
      *
      * 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,  Next: expat,  Prev: strtod and dtoa,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.12 OpenSSL
---------------

The modules *note hashlib: 8d, *note posix: d2, *note ssl: f4, *note
crypt: 29. use the OpenSSL library for added performance if made
available by the operating system.  Additionally, the Windows and Mac OS
X installers for Python may include a copy of the OpenSSL libraries, so
we include a copy of the OpenSSL license here:

      LICENSE ISSUES
      ==============

      The OpenSSL toolkit stays under a dual license, i.e. both the conditions of
      the OpenSSL License and the original SSLeay license apply to the toolkit.
      See below for the actual license texts. Actually both licenses are BSD-style
      Open Source licenses. In case of any license issues related to OpenSSL
      please contact openssl-core@openssl.org.

      OpenSSL License
      ---------------

        /* ====================================================================
         * Copyright (c) 1998-2008 The OpenSSL 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. All advertising materials mentioning features or use of this
         *    software must display the following acknowledgment:
         *    "This product includes software developed by the OpenSSL Project
         *    for use in the OpenSSL Toolkit. (http://www.openssl.org/)"
         *
         * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to
         *    endorse or promote products derived from this software without
         *    prior written permission. For written permission, please contact
         *    openssl-core@openssl.org.
         *
         * 5. Products derived from this software may not be called "OpenSSL"
         *    nor may "OpenSSL" appear in their names without prior written
         *    permission of the OpenSSL Project.
         *
         * 6. Redistributions of any form whatsoever must retain the following
         *    acknowledgment:
         *    "This product includes software developed by the OpenSSL Project
         *    for use in the OpenSSL Toolkit (http://www.openssl.org/)"
         *
         * THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY
         * EXPRESSED 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 OpenSSL PROJECT OR
         * ITS 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.
         * ====================================================================
         *
         * This product includes cryptographic software written by Eric Young
         * (eay@cryptsoft.com).  This product includes software written by Tim
         * Hudson (tjh@cryptsoft.com).
         *
         */

     Original SSLeay License
     -----------------------

        /* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
         * All rights reserved.
         *
         * This package is an SSL implementation written
         * by Eric Young (eay@cryptsoft.com).
         * The implementation was written so as to conform with Netscapes SSL.
         *
         * This library is free for commercial and non-commercial use as long as
         * the following conditions are aheared to.  The following conditions
         * apply to all code found in this distribution, be it the RC4, RSA,
         * lhash, DES, etc., code; not just the SSL code.  The SSL documentation
         * included with this distribution is covered by the same copyright terms
         * except that the holder is Tim Hudson (tjh@cryptsoft.com).
         *
         * Copyright remains Eric Young's, and as such any Copyright notices in
         * the code are not to be removed.
         * If this package is used in a product, Eric Young should be given attribution
         * as the author of the parts of the library used.
         * This can be in the form of a textual message at program startup or
         * in documentation (online or textual) provided with the package.
         *
         * 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 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. All advertising materials mentioning features or use of this software
         *    must display the following acknowledgement:
         *    "This product includes cryptographic software written by
         *     Eric Young (eay@cryptsoft.com)"
         *    The word 'cryptographic' can be left out if the rouines from the library
         *    being used are not cryptographic related :-).
         * 4. If you include any Windows specific code (or a derivative thereof) from
         *    the apps directory (application code) you must include an acknowledgement:
         *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
         *
         * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``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.
         *
         * The licence and distribution terms for any publically available version or
         * derivative of this code cannot be changed.  i.e. this code cannot simply be
         * copied and put under another distribution licence
         * [including the GNU Public Licence.]
         */


File: python.info,  Node: expat,  Next: libffi,  Prev: OpenSSL,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.13 expat
-------------

The ‘pyexpat’ extension is built using an included copy of the expat
sources unless the build is configured ‘--with-system-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: Licenses and Acknowledgements for Incorporated Software

16.3.14 libffi
--------------

The ‘_ctypes’ extension is built using an included copy of the libffi
sources unless the build is configured ‘--with-system-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: Licenses and Acknowledgements for Incorporated Software

16.3.15 zlib
------------

The *note zlib: 145. extension is built using an included copy of the
zlib sources if the zlib version found on the system is too old to be
used for the build:

     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: Licenses and Acknowledgements for Incorporated Software

16.3.16 cfuhash
---------------

The implementation of the hash table used by the *note tracemalloc: 115.
is based on the cfuhash project:

     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 test suite,  Prev: cfuhash,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.17 libmpdec
----------------

The ‘_decimal’ module is built using an included copy of the libmpdec
library unless the build is configured ‘--with-system-libmpdec’:

     Copyright (c) 2008-2016 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 test suite,  Prev: libmpdec,  Up: Licenses and Acknowledgements for Incorporated Software

16.3.18 W3C C14N test suite
---------------------------

The C14N 2.0 test suite in the *note test: 106. package
(‘Lib/test/xmltestdata/c14n-20/’) was retrieved from the W3C website at
‘https://www.w3.org/TR/xml-c14n2-testcases/’ and is distributed under
the 3-clause BSD license:

     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: 發布 Python 模組（舊版）,  Next: 安裝 Python 模組（舊版）,  Prev: 歷史與授權,  Up: Top

17 發布 Python 模組（舊版）
***************************


Authors: Greg Ward, Anthony Baxter


Email: <distutils-sig@python.org>

也參考
......

*note 發布 Python 模組: 7fb.

     The up to date module distribution documentations

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

     備註: This guide only covers the basic tools for building and
     distributing extensions that are provided as part of this version
     of Python.  Third party tools offer easier to use and more secure
     alternatives.  Refer to the quick recommendations section(1) in the
     Python Packaging User Guide for more information.

This document describes the Python Distribution Utilities ("Distutils")
from the module developer’s point of view, describing the underlying
capabilities that ‘setuptools’ builds on to allow Python developers to
make Python modules and extensions readily available to a wider
audience.

* Menu:

* An Introduction to Distutils::
* Writing the Setup Script::
* Writing the Setup Configuration File::
* Creating a Source Distribution::
* Creating Built Distributions::
* Distutils Examples::
* Extending Distutils::
* 指令參照::
* API參照::

   ---------- Footnotes ----------

   (1) https://packaging.python.org/guides/tool-recommendations/


File: python.info,  Node: An Introduction to Distutils,  Next: Writing the Setup Script,  Up: 發布 Python 模組（舊版）

17.1 An Introduction to Distutils
=================================

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

This document covers using the Distutils to distribute your Python
modules, concentrating on the role of developer/distributor: if you’re
looking for information on installing Python modules, you should refer
to the *note 安裝 Python 模組（舊版）: 7fc. chapter.

* Menu:

* Concepts & Terminology::
* A Simple Example: A Simple Example<2>.
* General Python terminology::
* Distutils-specific terminology::


File: python.info,  Node: Concepts & Terminology,  Next: A Simple Example<2>,  Up: An Introduction to Distutils

17.1.1 Concepts & Terminology
-----------------------------

Using the Distutils is quite simple, both for module developers and for
users/administrators installing third-party modules.  As a developer,
your responsibilities (apart from writing solid, well-documented and
well-tested code, of course!)  are:

   * write a setup script (‘setup.py’ by convention)

   * (optional) write a setup configuration file

   * create a source distribution

   * (optional) create one or more built (binary) distributions

Each of these tasks is covered in this document.

Not all module developers have access to a multitude of platforms, so
it’s not always feasible to expect them to create a multitude of built
distributions.  It is hoped that a class of intermediaries, called
`packagers', will arise to address this need.  Packagers will take
source distributions released by module developers, build them on one or
more platforms, and release the resulting built distributions.  Thus,
users on the most popular platforms will be able to install most popular
Python module distributions in the most natural way for their platform,
without having to run a single setup script or compile a line of code.


File: python.info,  Node: A Simple Example<2>,  Next: General Python terminology,  Prev: Concepts & Terminology,  Up: An Introduction to Distutils

17.1.2 A Simple Example
-----------------------

The setup script is usually quite simple, although since it’s written in
Python, there are no arbitrary limits to what you can do with it, though
you should be careful about putting arbitrarily expensive operations in
your setup script.  Unlike, say, Autoconf-style configure scripts, the
setup script may be run multiple times in the course of building and
installing your module distribution.

If all you want to do is distribute a module called ‘foo’, contained in
a file ‘foo.py’, then your setup script can be as simple as this:

     from distutils.core import setup
     setup(name='foo',
           version='1.0',
           py_modules=['foo'],
           )

Some observations:

   * most information that you supply to the Distutils is supplied as
     keyword arguments to the ‘setup()’ function

   * those keyword arguments fall into two categories: package metadata
     (name, version number) and information about what’s in the package
     (a list of pure Python modules, in this case)

   * modules are specified by module name, not filename (the same will
     hold true for packages and extensions)

   * it’s recommended that you supply a little more metadata, in
     particular your name, email address and a URL for the project (see
     section *note Writing the Setup Script: 4356. for an example)

To create a source distribution for this module, you would create a
setup script, ‘setup.py’, containing the above code, and run this
command from a terminal:

     python setup.py sdist

For Windows, open a command prompt window (Start ‣ Accessories) and
change the command to:

     setup.py sdist

‘sdist’ will create an archive file (e.g., tarball on Unix, ZIP file on
Windows) containing your setup script ‘setup.py’, and your module
‘foo.py’.  The archive file will be named ‘foo-1.0.tar.gz’ (or ‘.zip’),
and will unpack into a directory ‘foo-1.0’.

If an end-user wishes to install your ‘foo’ module, all they have to do
is download ‘foo-1.0.tar.gz’ (or ‘.zip’), unpack it, and—from the
‘foo-1.0’ directory—run

     python setup.py install

which will ultimately copy ‘foo.py’ to the appropriate directory for
third-party modules in their Python installation.

This simple example demonstrates some fundamental concepts of the
Distutils.  First, both developers and installers have the same basic
user interface, i.e.  the setup script.  The difference is which
Distutils `commands' they use: the ‘sdist’ command is almost exclusively
for module developers, while ‘install’ is more often for installers
(although most developers will want to install their own code
occasionally).

If you want to make things really easy for your users, you can create
one or more built distributions for them.  For instance, if you are
running on a Windows machine, and want to make things easy for other
Windows users, you can create an executable installer (the most
appropriate type of built distribution for this platform) with the
‘bdist_wininst’ command.  For example:

     python setup.py bdist_wininst

will create an executable installer, ‘foo-1.0.win32.exe’, in the current
directory.

Other useful built distribution formats are RPM, implemented by the
‘bdist_rpm’ command, Solaris ‘pkgtool’ (‘bdist_pkgtool’), and HP-UX
‘swinstall’ (‘bdist_sdux’).  For example, the following command will
create an RPM file called ‘foo-1.0.noarch.rpm’:

     python setup.py bdist_rpm

(The ‘bdist_rpm’ command uses the ‘rpm’ executable, therefore this has
to be run on an RPM-based system such as Red Hat Linux, SuSE Linux, or
Mandrake Linux.)

You can find out what distribution formats are available at any time by
running

     python setup.py bdist --help-formats


File: python.info,  Node: General Python terminology,  Next: Distutils-specific terminology,  Prev: A Simple Example<2>,  Up: An Introduction to Distutils

17.1.3 General Python terminology
---------------------------------

If you’re reading this document, you probably have a good idea of what
modules, extensions, and so forth are.  Nevertheless, just to be sure
that everyone is operating from a common starting point, we offer the
following glossary of common Python terms:

module

     the basic unit of code reusability in Python: a block of code
     imported by some other code.  Three types of modules concern us
     here: pure Python modules, extension modules, and packages.

pure Python module

     a module written in Python and contained in a single ‘.py’ file
     (and possibly associated ‘.pyc’ files).  Sometimes referred to as a
     "pure module."

extension module

     a module written in the low-level language of the Python
     implementation: C/C++ for Python, Java for Jython.  Typically
     contained in a single dynamically loadable pre-compiled file, e.g.
     a shared object (‘.so’) file for Python extensions on Unix, a DLL
     (given the ‘.pyd’ extension) for Python extensions on Windows, or a
     Java class file for Jython extensions.  (Note that currently, the
     Distutils only handles C/C++ extensions for Python.)

package

     a module that contains other modules; typically contained in a
     directory in the filesystem and distinguished from other
     directories by the presence of a file ‘__init__.py’.

root package

     the root of the hierarchy of packages.  (This isn’t really a
     package, since it doesn’t have an ‘__init__.py’ file.  But we have
     to call it something.)  The vast majority of the standard library
     is in the root package, as are many small, standalone third-party
     modules that don’t belong to a larger module collection.  Unlike
     regular packages, modules in the root package can be found in many
     directories: in fact, every directory listed in ‘sys.path’
     contributes modules to the root package.


File: python.info,  Node: Distutils-specific terminology,  Prev: General Python terminology,  Up: An Introduction to Distutils

17.1.4 Distutils-specific terminology
-------------------------------------

The following terms apply more specifically to the domain of
distributing Python modules using the Distutils:

module distribution

     a collection of Python modules distributed together as a single
     downloadable resource and meant to be installed `en masse'.
     Examples of some well-known module distributions are NumPy, SciPy,
     Pillow, or mxBase.  (This would be called a `package', except that
     term is already taken in the Python context: a single module
     distribution may contain zero, one, or many Python packages.)

pure module distribution

     a module distribution that contains only pure Python modules and
     packages.  Sometimes referred to as a "pure distribution."

non-pure module distribution

     a module distribution that contains at least one extension module.
     Sometimes referred to as a "non-pure distribution."

distribution root

     the top-level directory of your source tree (or source
     distribution); the directory where ‘setup.py’ exists.  Generally
     ‘setup.py’ will be run from this directory.


File: python.info,  Node: Writing the Setup Script,  Next: Writing the Setup Configuration File,  Prev: An Introduction to Distutils,  Up: 發布 Python 模組（舊版）

17.2 Writing the Setup Script
=============================

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

The setup script is the centre of all activity in building,
distributing, and installing modules using the Distutils.  The main
purpose of the setup script is to describe your module distribution to
the Distutils, so that the various commands that operate on your modules
do the right thing.  As we saw in section *note A Simple Example: 4355.
above, the setup script consists mainly of a call to ‘setup()’, and most
information supplied to the Distutils by the module developer is
supplied as keyword arguments to ‘setup()’.

Here’s a slightly more involved example, which we’ll follow for the next
couple of sections: the Distutils’ own setup script.  (Keep in mind that
although the Distutils are included with Python 1.6 and later, they also
have an independent existence so that Python 1.5.2 users can use them to
install other module distributions.  The Distutils’ own setup script,
shown here, is used to install the package into Python 1.5.2.)

     #!/usr/bin/env python

     from distutils.core import setup

     setup(name='Distutils',
           version='1.0',
           description='Python Distribution Utilities',
           author='Greg Ward',
           author_email='gward@python.net',
           url='https://www.python.org/sigs/distutils-sig/',
           packages=['distutils', 'distutils.command'],
          )

There are only two differences between this and the trivial one-file
distribution presented in section *note A Simple Example: 4355.: more
metadata, and the specification of pure Python modules by package,
rather than by module.  This is important since the Distutils consist of
a couple of dozen modules split into (so far) two packages; an explicit
list of every module would be tedious to generate and difficult to
maintain.  For more information on the additional meta-data, see section
*note Additional meta-data: 435d.

Note that any pathnames (files or directories) supplied in the setup
script should be written using the Unix convention, i.e.
slash-separated.  The Distutils will take care of converting this
platform-neutral representation into whatever is appropriate on your
current platform before actually using the pathname.  This makes your
setup script portable across operating systems, which of course is one
of the major goals of the Distutils.  In this spirit, all pathnames in
this document are slash-separated.

This, of course, only applies to pathnames given to Distutils functions.
If you, for example, use standard Python functions such as *note
glob.glob(): 5cb. or *note os.listdir(): a46. to specify files, you
should be careful to write portable code instead of hardcoding path
separators:

     glob.glob(os.path.join('mydir', 'subdir', '*.html'))
     os.listdir(os.path.join('mydir', 'subdir'))

* Menu:

* Listing whole packages::
* Listing individual modules::
* Describing extension modules::
* Relationships between Distributions and Packages::
* Installing Scripts::
* Installing Package Data::
* Installing Additional Files::
* Additional meta-data::
* Debugging the setup script::


File: python.info,  Node: Listing whole packages,  Next: Listing individual modules,  Up: Writing the Setup Script

17.2.1 Listing whole packages
-----------------------------

The ‘packages’ option tells the Distutils to process (build, distribute,
install, etc.)  all pure Python modules found in each package mentioned
in the ‘packages’ list.  In order to do this, of course, there has to be
a correspondence between package names and directories in the
filesystem.  The default correspondence is the most obvious one, i.e.
package *note distutils: 39. is found in the directory ‘distutils’
relative to the distribution root.  Thus, when you say ‘packages =
['foo']’ in your setup script, you are promising that the Distutils will
find a file ‘foo/__init__.py’ (which might be spelled differently on
your system, but you get the idea) relative to the directory where your
setup script lives.  If you break this promise, the Distutils will issue
a warning but still process the broken package anyway.

If you use a different convention to lay out your source directory,
that’s no problem: you just have to supply the ‘package_dir’ option to
tell the Distutils about your convention.  For example, say you keep all
Python source under ‘lib’, so that modules in the "root package" (i.e.,
not in any package at all) are in ‘lib’, modules in the ‘foo’ package
are in ‘lib/foo’, and so forth.  Then you would put

     package_dir = {'': 'lib'}

in your setup script.  The keys to this dictionary are package names,
and an empty package name stands for the root package.  The values are
directory names relative to your distribution root.  In this case, when
you say ‘packages = ['foo']’, you are promising that the file
‘lib/foo/__init__.py’ exists.

Another possible convention is to put the ‘foo’ package right in ‘lib’,
the ‘foo.bar’ package in ‘lib/bar’, etc.  This would be written in the
setup script as

     package_dir = {'foo': 'lib'}

A ‘package: dir’ entry in the ‘package_dir’ dictionary implicitly
applies to all packages below `package', so the ‘foo.bar’ case is
automatically handled here.  In this example, having ‘packages = ['foo',
'foo.bar']’ tells the Distutils to look for ‘lib/__init__.py’ and
‘lib/bar/__init__.py’.  (Keep in mind that although ‘package_dir’
applies recursively, you must explicitly list all packages in
‘packages’: the Distutils will `not' recursively scan your source tree
looking for any directory with an ‘__init__.py’ file.)


File: python.info,  Node: Listing individual modules,  Next: Describing extension modules,  Prev: Listing whole packages,  Up: Writing the Setup Script

17.2.2 Listing individual modules
---------------------------------

For a small module distribution, you might prefer to list all modules
rather than listing packages—especially the case of a single module that
goes in the "root package" (i.e., no package at all).  This simplest
case was shown in section *note A Simple Example: 4355.; here is a
slightly more involved example:

     py_modules = ['mod1', 'pkg.mod2']

This describes two modules, one of them in the "root" package, the other
in the ‘pkg’ package.  Again, the default package/directory layout
implies that these two modules can be found in ‘mod1.py’ and
‘pkg/mod2.py’, and that ‘pkg/__init__.py’ exists as well.  And again,
you can override the package/directory correspondence using the
‘package_dir’ option.


File: python.info,  Node: Describing extension modules,  Next: Relationships between Distributions and Packages,  Prev: Listing individual modules,  Up: Writing the Setup Script

17.2.3 Describing extension modules
-----------------------------------

Just as writing Python extension modules is a bit more complicated than
writing pure Python modules, describing them to the Distutils is a bit
more complicated.  Unlike pure modules, it’s not enough just to list
modules or packages and expect the Distutils to go out and find the
right files; you have to specify the extension name, source file(s), and
any compile/link requirements (include directories, libraries to link
with, etc.).

All of this is done through another keyword argument to ‘setup()’, the
‘ext_modules’ option.  ‘ext_modules’ is just a list of *note Extension:
4364. instances, each of which describes a single extension module.
Suppose your distribution includes a single extension, called ‘foo’ and
implemented by ‘foo.c’.  If no additional instructions to the
compiler/linker are needed, describing this extension is quite simple:

     Extension('foo', ['foo.c'])

The ‘Extension’ class can be imported from *note distutils.core: 54.
along with ‘setup()’.  Thus, the setup script for a module distribution
that contains only this one extension and nothing else might be:

     from distutils.core import setup, Extension
     setup(name='foo',
           version='1.0',
           ext_modules=[Extension('foo', ['foo.c'])],
           )

The ‘Extension’ class (actually, the underlying extension-building
machinery implemented by the ‘build_ext’ command) supports a great deal
of flexibility in describing Python extensions, which is explained in
the following sections.

* Menu:

* Extension names and packages::
* Extension source files::
* Preprocessor options::
* Library options::
* Other options::


File: python.info,  Node: Extension names and packages,  Next: Extension source files,  Up: Describing extension modules

17.2.3.1 Extension names and packages
.....................................

The first argument to the *note Extension: 4364. constructor is always
the name of the extension, including any package names.  For example,

     Extension('foo', ['src/foo1.c', 'src/foo2.c'])

describes an extension that lives in the root package, while

     Extension('pkg.foo', ['src/foo1.c', 'src/foo2.c'])

describes the same extension in the ‘pkg’ package.  The source files and
resulting object code are identical in both cases; the only difference
is where in the filesystem (and therefore where in Python’s namespace
hierarchy) the resulting extension lives.

If you have a number of extensions all in the same package (or all under
the same base package), use the ‘ext_package’ keyword argument to
‘setup()’.  For example,

     setup(...,
           ext_package='pkg',
           ext_modules=[Extension('foo', ['foo.c']),
                        Extension('subpkg.bar', ['bar.c'])],
          )

will compile ‘foo.c’ to the extension ‘pkg.foo’, and ‘bar.c’ to
‘pkg.subpkg.bar’.


File: python.info,  Node: Extension source files,  Next: Preprocessor options,  Prev: Extension names and packages,  Up: Describing extension modules

17.2.3.2 Extension source files
...............................

The second argument to the *note Extension: 4364. constructor is a list
of source files.  Since the Distutils currently only support C, C++, and
Objective-C extensions, these are normally C/C++/Objective-C source
files.  (Be sure to use appropriate extensions to distinguish C++ source
files: ‘.cc’ and ‘.cpp’ seem to be recognized by both Unix and Windows
compilers.)

However, you can also include SWIG interface (‘.i’) files in the list;
the ‘build_ext’ command knows how to deal with SWIG extensions: it will
run SWIG on the interface file and compile the resulting C/C++ file into
your extension.

This warning notwithstanding, options to SWIG can be currently passed
like this:

     setup(...,
           ext_modules=[Extension('_foo', ['foo.i'],
                                  swig_opts=['-modern', '-I../include'])],
           py_modules=['foo'],
          )

Or on the commandline like this:

     > python setup.py build_ext --swig-opts="-modern -I../include"

On some platforms, you can include non-source files that are processed
by the compiler and included in your extension.  Currently, this just
means Windows message text (‘.mc’) files and resource definition (‘.rc’)
files for Visual C++.  These will be compiled to binary resource
(‘.res’) files and linked into the executable.


File: python.info,  Node: Preprocessor options,  Next: Library options,  Prev: Extension source files,  Up: Describing extension modules

17.2.3.3 Preprocessor options
.............................

Three optional arguments to *note Extension: 4364. will help if you need
to specify include directories to search or preprocessor macros to
define/undefine: ‘include_dirs’, ‘define_macros’, and ‘undef_macros’.

For example, if your extension requires header files in the ‘include’
directory under your distribution root, use the ‘include_dirs’ option:

     Extension('foo', ['foo.c'], include_dirs=['include'])

You can specify absolute directories there; if you know that your
extension will only be built on Unix systems with X11R6 installed to
‘/usr’, you can get away with

     Extension('foo', ['foo.c'], include_dirs=['/usr/include/X11'])

You should avoid this sort of non-portable usage if you plan to
distribute your code: it’s probably better to write C code like

     #include <X11/Xlib.h>

If you need to include header files from some other Python extension,
you can take advantage of the fact that header files are installed in a
consistent way by the Distutils ‘install_headers’ command.  For example,
the Numerical Python header files are installed (on a standard Unix
installation) to ‘/usr/local/include/python1.5/Numerical’.  (The exact
location will differ according to your platform and Python
installation.)  Since the Python include
directory—‘/usr/local/include/python1.5’ in this case—is always included
in the search path when building Python extensions, the best approach is
to write C code like

     #include <Numerical/arrayobject.h>

If you must put the ‘Numerical’ include directory right into your header
search path, though, you can find that directory using the Distutils
*note distutils.sysconfig: 62. module:

     from distutils.sysconfig import get_python_inc
     incdir = os.path.join(get_python_inc(plat_specific=1), 'Numerical')
     setup(...,
           Extension(..., include_dirs=[incdir]),
           )

Even though this is quite portable—it will work on any Python
installation, regardless of platform—it’s probably easier to just write
your C code in the sensible way.

You can define and undefine pre-processor macros with the
‘define_macros’ and ‘undef_macros’ options.  ‘define_macros’ takes a
list of ‘(name, value)’ tuples, where ‘name’ is the name of the macro to
define (a string) and ‘value’ is its value: either a string or ‘None’.
(Defining a macro ‘FOO’ to ‘None’ is the equivalent of a bare ‘#define
FOO’ in your C source: with most compilers, this sets ‘FOO’ to the
string ‘1’.)  ‘undef_macros’ is just a list of macros to undefine.

For example:

     Extension(...,
               define_macros=[('NDEBUG', '1'),
                              ('HAVE_STRFTIME', None)],
               undef_macros=['HAVE_FOO', 'HAVE_BAR'])

is the equivalent of having this at the top of every C source file:

     #define NDEBUG 1
     #define HAVE_STRFTIME
     #undef HAVE_FOO
     #undef HAVE_BAR


File: python.info,  Node: Library options,  Next: Other options,  Prev: Preprocessor options,  Up: Describing extension modules

17.2.3.4 Library options
........................

You can also specify the libraries to link against when building your
extension, and the directories to search for those libraries.  The
‘libraries’ option is a list of libraries to link against,
‘library_dirs’ is a list of directories to search for libraries at
link-time, and ‘runtime_library_dirs’ is a list of directories to search
for shared (dynamically loaded) libraries at run-time.

For example, if you need to link against libraries known to be in the
standard library search path on target systems

     Extension(...,
               libraries=['gdbm', 'readline'])

If you need to link with libraries in a non-standard location, you’ll
have to include the location in ‘library_dirs’:

     Extension(...,
               library_dirs=['/usr/X11R6/lib'],
               libraries=['X11', 'Xt'])

(Again, this sort of non-portable construct should be avoided if you
intend to distribute your code.)


File: python.info,  Node: Other options,  Prev: Library options,  Up: Describing extension modules

17.2.3.5 Other options
......................

There are still some other options which can be used to handle special
cases.

The ‘optional’ option is a boolean; if it is true, a build failure in
the extension will not abort the build process, but instead simply not
install the failing extension.

The ‘extra_objects’ option is a list of object files to be passed to the
linker.  These files must not have extensions, as the default extension
for the compiler is used.

‘extra_compile_args’ and ‘extra_link_args’ can be used to specify
additional command line options for the respective compiler and linker
command lines.

‘export_symbols’ is only useful on Windows.  It can contain a list of
symbols (functions or variables) to be exported.  This option is not
needed when building compiled extensions: Distutils will automatically
add ‘initmodule’ to the list of exported symbols.

The ‘depends’ option is a list of files that the extension depends on
(for example header files).  The build command will call the compiler on
the sources to rebuild extension if any on this files has been modified
since the previous build.


File: python.info,  Node: Relationships between Distributions and Packages,  Next: Installing Scripts,  Prev: Describing extension modules,  Up: Writing the Setup Script

17.2.4 Relationships between Distributions and Packages
-------------------------------------------------------

A distribution may relate to packages in three specific ways:

  1. It can require packages or modules.

  2. It can provide packages or modules.

  3. It can obsolete packages or modules.

These relationships can be specified using keyword arguments to the
*note distutils.core.setup(): 3b71. function.

Dependencies on other Python modules and packages can be specified by
supplying the `requires' keyword argument to ‘setup()’.  The value must
be a list of strings.  Each string specifies a package that is required,
and optionally what versions are sufficient.

To specify that any version of a module or package is required, the
string should consist entirely of the module or package name.  Examples
include ‘'mymodule'’ and ‘'xml.parsers.expat'’.

If specific versions are required, a sequence of qualifiers can be
supplied in parentheses.  Each qualifier may consist of a comparison
operator and a version number.  The accepted comparison operators are:

     <    >    ==
     <=   >=   !=

These can be combined by using multiple qualifiers separated by commas
(and optional whitespace).  In this case, all of the qualifiers must be
matched; a logical AND is used to combine the evaluations.

Let’s look at a bunch of examples:

Requires Expression           Explanation
                              
---------------------------------------------------------------------------------
                              
‘==1.0’                       Only version ‘1.0’ is compatible
                              
                              
‘>1.0, !=1.5.1, <2.0’         Any version after ‘1.0’ and before ‘2.0’ is
                              compatible, except ‘1.5.1’
                              

Now that we can specify dependencies, we also need to be able to specify
what we provide that other distributions can require.  This is done
using the `provides' keyword argument to ‘setup()’.  The value for this
keyword is a list of strings, each of which names a Python module or
package, and optionally identifies the version.  If the version is not
specified, it is assumed to match that of the distribution.

Some examples:

Provides Expression       Explanation
                          
-----------------------------------------------------------------------------
                          
‘mypkg’                   Provide ‘mypkg’, using the distribution version
                          
                          
‘mypkg (1.1)’             Provide ‘mypkg’ version 1.1, regardless of the
                          distribution version
                          

A package can declare that it obsoletes other packages using the
`obsoletes' keyword argument.  The value for this is similar to that of
the `requires' keyword: a list of strings giving module or package
specifiers.  Each specifier consists of a module or package name
optionally followed by one or more version qualifiers.  Version
qualifiers are given in parentheses after the module or package name.

The versions identified by the qualifiers are those that are obsoleted
by the distribution being described.  If no qualifiers are given, all
versions of the named module or package are understood to be obsoleted.


File: python.info,  Node: Installing Scripts,  Next: Installing Package Data,  Prev: Relationships between Distributions and Packages,  Up: Writing the Setup Script

17.2.5 Installing Scripts
-------------------------

So far we have been dealing with pure and non-pure Python modules, which
are usually not run by themselves but imported by scripts.

Scripts are files containing Python source code, intended to be started
from the command line.  Scripts don’t require Distutils to do anything
very complicated.  The only clever feature is that if the first line of
the script starts with ‘#!’ and contains the word "python", the
Distutils will adjust the first line to refer to the current interpreter
location.  By default, it is replaced with the current interpreter
location.  The ‘--executable’ (or ‘-e’) option will allow the
interpreter path to be explicitly overridden.

The ‘scripts’ option simply is a list of files to be handled in this
way.  From the PyXML setup script:

     setup(...,
           scripts=['scripts/xmlproc_parse', 'scripts/xmlproc_val']
           )

3.1 版更變: All the scripts will also be added to the ‘MANIFEST’ file if
no template is provided.  See *note Specifying the files to distribute:
3b74.


File: python.info,  Node: Installing Package Data,  Next: Installing Additional Files,  Prev: Installing Scripts,  Up: Writing the Setup Script

17.2.6 Installing Package Data
------------------------------

Often, additional files need to be installed into a package.  These
files are often data that’s closely related to the package’s
implementation, or text files containing documentation that might be of
interest to programmers using the package.  These files are called
`package data'.

Package data can be added to packages using the ‘package_data’ keyword
argument to the ‘setup()’ function.  The value must be a mapping from
package name to a list of relative path names that should be copied into
the package.  The paths are interpreted as relative to the directory
containing the package (information from the ‘package_dir’ mapping is
used if appropriate); that is, the files are expected to be part of the
package in the source directories.  They may contain glob patterns as
well.

The path names may contain directory portions; any necessary directories
will be created in the installation.

For example, if a package should contain a subdirectory with several
data files, the files can be arranged like this in the source tree:

     setup.py
     src/
         mypkg/
             __init__.py
             module.py
             data/
                 tables.dat
                 spoons.dat
                 forks.dat

The corresponding call to ‘setup()’ might be:

     setup(...,
           packages=['mypkg'],
           package_dir={'mypkg': 'src/mypkg'},
           package_data={'mypkg': ['data/*.dat']},
           )

3.1 版更變: All the files that match ‘package_data’ will be added to the
‘MANIFEST’ file if no template is provided.  See *note Specifying the
files to distribute: 3b74.


File: python.info,  Node: Installing Additional Files,  Next: Additional meta-data,  Prev: Installing Package Data,  Up: Writing the Setup Script

17.2.7 Installing Additional Files
----------------------------------

The ‘data_files’ option can be used to specify additional files needed
by the module distribution: configuration files, message catalogs, data
files, anything which doesn’t fit in the previous categories.

‘data_files’ specifies a sequence of (`directory', `files') pairs in the
following way:

     setup(...,
           data_files=[('bitmaps', ['bm/b1.gif', 'bm/b2.gif']),
                       ('config', ['cfg/data.cfg'])],
          )

Each (`directory', `files') pair in the sequence specifies the
installation directory and the files to install there.

Each file name in `files' is interpreted relative to the ‘setup.py’
script at the top of the package source distribution.  Note that you can
specify the directory where the data files will be installed, but you
cannot rename the data files themselves.

The `directory' should be a relative path.  It is interpreted relative
to the installation prefix (Python’s ‘sys.prefix’ for system
installations; ‘site.USER_BASE’ for user installations).  Distutils
allows `directory' to be an absolute installation path, but this is
discouraged since it is incompatible with the wheel packaging format.
No directory information from `files' is used to determine the final
location of the installed file; only the name of the file is used.

You can specify the ‘data_files’ options as a simple sequence of files
without specifying a target directory, but this is not recommended, and
the ‘install’ command will print a warning in this case.  To install
data files directly in the target directory, an empty string should be
given as the directory.

3.1 版更變: All the files that match ‘data_files’ will be added to the
‘MANIFEST’ file if no template is provided.  See *note Specifying the
files to distribute: 3b74.


File: python.info,  Node: Additional meta-data,  Next: Debugging the setup script,  Prev: Installing Additional Files,  Up: Writing the Setup Script

17.2.8 Additional meta-data
---------------------------

The setup script may include additional meta-data beyond the name and
version.  This information includes:

Meta-Data                  描述                            Value                 註解
                                                                                 
----------------------------------------------------------------------------------------------
                                                                                 
‘name’                     name of the package             short string          (1)
                                                                                 
                                                                                 
‘version’                  version of this release         short string          (1)(2)
                                                                                 
                                                                                 
‘author’                   package author’s name           short string          (3)
                                                                                 
                                                                                 
‘author_email’             email address of the package    email address         (3)
                           author                                                
                           
                                                                                 
‘maintainer’               package maintainer’s name       short string          (3)
                                                                                 
                                                                                 
‘maintainer_email’         email address of the package    email address         (3)
                           maintainer                                            
                           
                                                                                 
‘url’                      home page for the package       URL                   (1)
                                                                                 
                                                                                 
‘description’              short, summary description of   short string
                           the package                     
                           
                                                                                 
‘long_description’         longer description of the       long string           (4)
                           package                                               
                           
                                                                                 
‘download_url’             location where the package      URL
                           may be downloaded               
                           
                                                                                 
‘classifiers’              a list of classifiers           list of strings       (6)(7)
                                                                                 
                                                                                 
‘platforms’                a list of platforms             list of strings       (6)(8)
                                                                                 
                                                                                 
‘keywords’                 a list of keywords              list of strings       (6)(8)
                                                                                 
                                                                                 
‘license’                  license for the package         short string          (5)
                                                                                 

註解：

  1. These fields are required.

  2. It is recommended that versions take the form
     `major.minor[.patch[.sub]]'.

  3. Either the author or the maintainer must be identified.  If
     maintainer is provided, distutils lists it as the author in
     ‘PKG-INFO’.

  4. The ‘long_description’ field is used by PyPI when you publish a
     package, to build its project page.

  5. The ‘license’ field is a text indicating the license covering the
     package where the license is not a selection from the "License"
     Trove classifiers.  See the ‘Classifier’ field.  Notice that
     there’s a ‘licence’ distribution option which is deprecated but
     still acts as an alias for ‘license’.

  6. This field must be a list.

  7. The valid classifiers are listed on PyPI(1).

  8. To preserve backward compatibility, this field also accepts a
     string.  If you pass a comma-separated string ‘'foo, bar'’, it will
     be converted to ‘['foo', 'bar']’, Otherwise, it will be converted
     to a list of one string.

’short string’

     A single line of text, not more than 200 characters.

’long string’

     Multiple lines of plain text in reStructuredText format (see
     ‘http://docutils.sourceforge.net/’).

’list of strings’

     See below.

Encoding the version information is an art in itself.  Python packages
generally adhere to the version format `major.minor[.patch][sub]'.  The
major number is 0 for initial, experimental releases of software.  It is
incremented for releases that represent major milestones in a package.
The minor number is incremented when important new features are added to
the package.  The patch number increments when bug-fix releases are
made.  Additional trailing version information is sometimes used to
indicate sub-releases.  These are "a1,a2,...,aN" (for alpha releases,
where functionality and API may change), "b1,b2,...,bN" (for beta
releases, which only fix bugs) and "pr1,pr2,...,prN" (for final
pre-release release testing).  Some examples:

0.1.0

     the first, experimental release of a package

1.0.1a2

     the second alpha release of the first patch version of 1.0

‘classifiers’ must be specified in a list:

     setup(...,
           classifiers=[
               'Development Status :: 4 - Beta',
               'Environment :: Console',
               'Environment :: Web Environment',
               'Intended Audience :: End Users/Desktop',
               'Intended Audience :: Developers',
               'Intended Audience :: System Administrators',
               'License :: OSI Approved :: Python Software Foundation License',
               'Operating System :: MacOS :: MacOS X',
               'Operating System :: Microsoft :: Windows',
               'Operating System :: POSIX',
               'Programming Language :: Python',
               'Topic :: Communications :: Email',
               'Topic :: Office/Business',
               'Topic :: Software Development :: Bug Tracking',
               ],
           )

3.7 版更變: *note setup: 3b71. now warns when ‘classifiers’, ‘keywords’
or ‘platforms’ fields are not specified as a list or a string.

   ---------- Footnotes ----------

   (1) https://pypi.org/classifiers


File: python.info,  Node: Debugging the setup script,  Prev: Additional meta-data,  Up: Writing the Setup Script

17.2.9 Debugging the setup script
---------------------------------

Sometimes things go wrong, and the setup script doesn’t do what the
developer wants.

Distutils catches any exceptions when running the setup script, and
print a simple error message before the script is terminated.  The
motivation for this behaviour is to not confuse administrators who don’t
know much about Python and are trying to install a package.  If they get
a big long traceback from deep inside the guts of Distutils, they may
think the package or the Python installation is broken because they
don’t read all the way down to the bottom and see that it’s a permission
problem.

On the other hand, this doesn’t help the developer to find the cause of
the failure.  For this purpose, the ‘DISTUTILS_DEBUG’ environment
variable can be set to anything except an empty string, and distutils
will now print detailed information about what it is doing, dump the
full traceback when an exception occurs, and print the whole command
line when an external program (like a C compiler) fails.


File: python.info,  Node: Writing the Setup Configuration File,  Next: Creating a Source Distribution,  Prev: Writing the Setup Script,  Up: 發布 Python 模組（舊版）

17.3 Writing the Setup Configuration File
=========================================

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

Often, it’s not possible to write down everything needed to build a
distribution `a priori': you may need to get some information from the
user, or from the user’s system, in order to proceed.  As long as that
information is fairly simple—a list of directories to search for C
header files or libraries, for example—then providing a configuration
file, ‘setup.cfg’, for users to edit is a cheap and easy way to solicit
it.  Configuration files also let you provide default values for any
command option, which the installer can then override either on the
command-line or by editing the config file.

The setup configuration file is a useful middle-ground between the setup
script—which, ideally, would be opaque to installers (1)—and the
command-line to the setup script, which is outside of your control and
entirely up to the installer.  In fact, ‘setup.cfg’ (and any other
Distutils configuration files present on the target system) are
processed after the contents of the setup script, but before the
command-line.  This has several useful consequences:

   * installers can override some of what you put in ‘setup.py’ by
     editing ‘setup.cfg’

   * you can provide non-standard defaults for options that are not
     easily set in ‘setup.py’

   * installers can override anything in ‘setup.cfg’ using the
     command-line options to ‘setup.py’

The basic syntax of the configuration file is simple:

     [command]
     option=value
     ...

where `command' is one of the Distutils commands (e.g.  ‘build_py’,
‘install’), and `option' is one of the options that command supports.
Any number of options can be supplied for each command, and any number
of command sections can be included in the file.  Blank lines are
ignored, as are comments, which run from a ‘'#'’ character until the end
of the line.  Long option values can be split across multiple lines
simply by indenting the continuation lines.

You can find out the list of options supported by a particular command
with the universal ‘--help’ option, e.g.

     $ python setup.py --help build_ext
     [...]
     Options for 'build_ext' command:
       --build-lib (-b)     directory for compiled extension modules
       --build-temp (-t)    directory for temporary files (build by-products)
       --inplace (-i)       ignore build-lib and put compiled extensions into the
                            source directory alongside your pure Python modules
       --include-dirs (-I)  list of directories to search for header files
       --define (-D)        C preprocessor macros to define
       --undef (-U)         C preprocessor macros to undefine
       --swig-opts          list of SWIG command line options
     [...]

Note that an option spelled ‘--foo-bar’ on the command-line is spelled
‘foo_bar’ in configuration files.  For example, say you want your
extensions to be built "in-place"—that is, you have an extension
‘pkg.ext’, and you want the compiled extension file (‘ext.so’ on Unix,
say) to be put in the same source directory as your pure Python modules
‘pkg.mod1’ and ‘pkg.mod2’.  You can always use the ‘--inplace’ option on
the command-line to ensure this:

     python setup.py build_ext --inplace

But this requires that you always specify the ‘build_ext’ command
explicitly, and remember to provide ‘--inplace’.  An easier way is to
"set and forget" this option, by encoding it in ‘setup.cfg’, the
configuration file for this distribution:

     [build_ext]
     inplace=1

This will affect all builds of this module distribution, whether or not
you explicitly specify ‘build_ext’.  If you include ‘setup.cfg’ in your
source distribution, it will also affect end-user builds—which is
probably a bad idea for this option, since always building extensions
in-place would break installation of the module distribution.  In
certain peculiar cases, though, modules are built right in their
installation directory, so this is conceivably a useful ability.
(Distributing extensions that expect to be built in their installation
directory is almost always a bad idea, though.)

Another example: certain commands take a lot of options that don’t
change from run to run; for example, ‘bdist_rpm’ needs to know
everything required to generate a "spec" file for creating an RPM
distribution.  Some of this information comes from the setup script, and
some is automatically generated by the Distutils (such as the list of
files installed).  But some of it has to be supplied as options to
‘bdist_rpm’, which would be very tedious to do on the command-line for
every run.  Hence, here is a snippet from the Distutils’ own
‘setup.cfg’:

     [bdist_rpm]
     release = 1
     packager = Greg Ward <gward@python.net>
     doc_files = CHANGES.txt
                 README.txt
                 USAGE.txt
                 doc/
                 examples/

Note that the ‘doc_files’ option is simply a whitespace-separated string
split across multiple lines for readability.

也參考
......

*note Syntax of config files: 4378. in "Installing Python Modules"

     More information on the configuration files is available in the
     manual for system administrators.

註解
....

   ---------- Footnotes ----------

   (1) (1) This ideal probably won’t be achieved until
auto-configuration is fully supported by the Distutils.


File: python.info,  Node: Creating a Source Distribution,  Next: Creating Built Distributions,  Prev: Writing the Setup Configuration File,  Up: 發布 Python 模組（舊版）

17.4 Creating a Source Distribution
===================================

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

As shown in section *note A Simple Example: 4355, you use the ‘sdist’
command to create a source distribution.  In the simplest case,

     python setup.py sdist

(assuming you haven’t specified any ‘sdist’ options in the setup script
or config file), ‘sdist’ creates the archive of the default format for
the current platform.  The default format is a gzip’ed tar file
(‘.tar.gz’) on Unix, and ZIP file on Windows.

You can specify as many formats as you like using the ‘--formats’
option, for example:

     python setup.py sdist --formats=gztar,zip

to create a gzipped tarball and a zip file.  The available formats are:

Format          描述                          註解
                                              
------------------------------------------------------------
                                              
‘zip’           zip file (‘.zip’)             (1),(3)
                                              
                                              
‘gztar’         gzip’ed tar file              (2)
                (‘.tar.gz’)                   
                
                                              
‘bztar’         bzip2’ed tar file
                (‘.tar.bz2’)
                
                                              
‘xztar’         xz’ed tar file (‘.tar.xz’)
                
                                              
‘ztar’          compressed tar file           (4)
                (‘.tar.Z’)                    
                
                                              
‘tar’           tar file (‘.tar’)
                

3.5 版更變: Added support for the ‘xztar’ format.

註解：

  1. default on Windows

  2. default on Unix

  3. requires either external ‘zip’ utility or *note zipfile: 143.
     module (part of the standard Python library since Python 1.6)

  4. requires the ‘compress’ program.  Notice that this format is now
     pending for deprecation and will be removed in the future versions
     of Python.

When using any ‘tar’ format (‘gztar’, ‘bztar’, ‘xztar’, ‘ztar’ or
‘tar’), under Unix you can specify the ‘owner’ and ‘group’ names that
will be set for each member of the archive.

For example, if you want all files of the archive to be owned by root:

     python setup.py sdist --owner=root --group=root

* Menu:

* Specifying the files to distribute::
* Manifest-related options::


File: python.info,  Node: Specifying the files to distribute,  Next: Manifest-related options,  Up: Creating a Source Distribution

17.4.1 Specifying the files to distribute
-----------------------------------------

If you don’t supply an explicit list of files (or instructions on how to
generate one), the ‘sdist’ command puts a minimal default set into the
source distribution:

   * all Python source files implied by the ‘py_modules’ and ‘packages’
     options

   * all C source files mentioned in the ‘ext_modules’ or ‘libraries’
     options

   * scripts identified by the ‘scripts’ option See *note Installing
     Scripts: 436b.

   * anything that looks like a test script: ‘test/test*.py’ (currently,
     the Distutils don’t do anything with test scripts except include
     them in source distributions, but in the future there will be a
     standard for testing Python module distributions)

   * Any of the standard README files (‘README’, ‘README.txt’, or
     ‘README.rst’), ‘setup.py’ (or whatever you called your setup
     script), and ‘setup.cfg’.

   * all files that matches the ‘package_data’ metadata.  See *note
     Installing Package Data: 436d.

   * all files that matches the ‘data_files’ metadata.  See *note
     Installing Additional Files: 436f.

Sometimes this is enough, but usually you will want to specify
additional files to distribute.  The typical way to do this is to write
a `manifest template', called ‘MANIFEST.in’ by default.  The manifest
template is just a list of instructions for how to generate your
manifest file, ‘MANIFEST’, which is the exact list of files to include
in your source distribution.  The ‘sdist’ command processes this
template and generates a manifest based on its instructions and what it
finds in the filesystem.

If you prefer to roll your own manifest file, the format is simple: one
filename per line, regular files (or symlinks to them) only.  If you do
supply your own ‘MANIFEST’, you must specify everything: the default set
of files described above does not apply in this case.

3.1 版更變: An existing generated ‘MANIFEST’ will be regenerated without
‘sdist’ comparing its modification time to the one of ‘MANIFEST.in’ or
‘setup.py’.

3.1.3 版更變: ‘MANIFEST’ files start with a comment indicating they are
generated.  Files without this comment are not overwritten or removed.

3.2.2 版更變: ‘sdist’ will read a ‘MANIFEST’ file if no ‘MANIFEST.in’
exists, like it used to do.

3.7 版更變: ‘README.rst’ is now included in the list of distutils
standard READMEs.

The manifest template has one command per line, where each command
specifies a set of files to include or exclude from the source
distribution.  For an example, again we turn to the Distutils’ own
manifest template:

     include *.txt
     recursive-include examples *.txt *.py
     prune examples/sample?/build

The meanings should be fairly clear: include all files in the
distribution root matching ‘*.txt’, all files anywhere under the
‘examples’ directory matching ‘*.txt’ or ‘*.py’, and exclude all
directories matching ‘examples/sample?/build’.  All of this is done
`after' the standard include set, so you can exclude files from the
standard set with explicit instructions in the manifest template.  (Or,
you can use the ‘--no-defaults’ option to disable the standard set
entirely.)  There are several other commands available in the manifest
template mini-language; see section *note Creating a source
distribution; the sdist command: 437d.

The order of commands in the manifest template matters: initially, we
have the list of default files as described above, and each command in
the template adds to or removes from that list of files.  Once we have
fully processed the manifest template, we remove files that should not
be included in the source distribution:

   * all files in the Distutils "build" tree (default ‘build/’)

   * all files in directories named ‘RCS’, ‘CVS’, ‘.svn’, ‘.hg’, ‘.git’,
     ‘.bzr’ or ‘_darcs’

Now we have our complete list of files, which is written to the manifest
for future reference, and then used to build the source distribution
archive(s).

You can disable the default set of included files with the
‘--no-defaults’ option, and you can disable the standard exclude set
with ‘--no-prune’.

Following the Distutils’ own manifest template, let’s trace how the
‘sdist’ command builds the list of files to include in the Distutils
source distribution:

  1. include all Python source files in the ‘distutils’ and
     ‘distutils/command’ subdirectories (because packages corresponding
     to those two directories were mentioned in the ‘packages’ option in
     the setup script—see section *note Writing the Setup Script: 4356.)

  2. include ‘README.txt’, ‘setup.py’, and ‘setup.cfg’ (standard files)

  3. include ‘test/test*.py’ (standard files)

  4. include ‘*.txt’ in the distribution root (this will find
     ‘README.txt’ a second time, but such redundancies are weeded out
     later)

  5. include anything matching ‘*.txt’ or ‘*.py’ in the sub-tree under
     ‘examples’,

  6. exclude all files in the sub-trees starting at directories matching
     ‘examples/sample?/build’—this may exclude files included by the
     previous two steps, so it’s important that the ‘prune’ command in
     the manifest template comes after the ‘recursive-include’ command

  7. exclude the entire ‘build’ tree, and any ‘RCS’, ‘CVS’, ‘.svn’,
     ‘.hg’, ‘.git’, ‘.bzr’ and ‘_darcs’ directories

Just like in the setup script, file and directory names in the manifest
template should always be slash-separated; the Distutils will take care
of converting them to the standard representation on your platform.
That way, the manifest template is portable across operating systems.


File: python.info,  Node: Manifest-related options,  Prev: Specifying the files to distribute,  Up: Creating a Source Distribution

17.4.2 Manifest-related options
-------------------------------

The normal course of operations for the ‘sdist’ command is as follows:

   * if the manifest file (‘MANIFEST’ by default) exists and the first
     line does not have a comment indicating it is generated from
     ‘MANIFEST.in’, then it is used as is, unaltered

   * if the manifest file doesn’t exist or has been previously
     automatically generated, read ‘MANIFEST.in’ and create the manifest

   * if neither ‘MANIFEST’ nor ‘MANIFEST.in’ exist, create a manifest
     with just the default file set

   * use the list of files now in ‘MANIFEST’ (either just generated or
     read in) to create the source distribution archive(s)

There are a couple of options that modify this behaviour.  First, use
the ‘--no-defaults’ and ‘--no-prune’ to disable the standard "include"
and "exclude" sets.

Second, you might just want to (re)generate the manifest, but not create
a source distribution:

     python setup.py sdist --manifest-only

‘-o’ is a shortcut for ‘--manifest-only’.


File: python.info,  Node: Creating Built Distributions,  Next: Distutils Examples,  Prev: Creating a Source Distribution,  Up: 發布 Python 模組（舊版）

17.5 Creating Built Distributions
=================================

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

A "built distribution" is what you’re probably used to thinking of
either as a "binary package" or an "installer" (depending on your
background).  It’s not necessarily binary, though, because it might
contain only Python source code and/or byte-code; and we don’t call it a
package, because that word is already spoken for in Python.  (And
"installer" is a term specific to the world of mainstream desktop
systems.)

A built distribution is how you make life as easy as possible for
installers of your module distribution: for users of RPM-based Linux
systems, it’s a binary RPM; for Windows users, it’s an executable
installer; for Debian-based Linux users, it’s a Debian package; and so
forth.  Obviously, no one person will be able to create built
distributions for every platform under the sun, so the Distutils are
designed to enable module developers to concentrate on their
specialty—writing code and creating source distributions—while an
intermediary species called `packagers' springs up to turn source
distributions into built distributions for as many platforms as there
are packagers.

Of course, the module developer could be their own packager; or the
packager could be a volunteer "out there" somewhere who has access to a
platform which the original developer does not; or it could be software
periodically grabbing new source distributions and turning them into
built distributions for as many platforms as the software has access to.
Regardless of who they are, a packager uses the setup script and the
‘bdist’ command family to generate built distributions.

As a simple example, if I run the following command in the Distutils
source tree:

     python setup.py bdist

then the Distutils builds my module distribution (the Distutils itself
in this case), does a "fake" installation (also in the ‘build’
directory), and creates the default type of built distribution for my
platform.  The default format for built distributions is a "dumb" tar
file on Unix, and a simple executable installer on Windows.  (That tar
file is considered "dumb" because it has to be unpacked in a specific
location to work.)

Thus, the above command on a Unix system creates
‘Distutils-1.0.`plat'.tar.gz’; unpacking this tarball from the right
place installs the Distutils just as though you had downloaded the
source distribution and run ‘python setup.py install’.  (The "right
place" is either the root of the filesystem or Python’s ‘`prefix'’
directory, depending on the options given to the ‘bdist_dumb’ command;
the default is to make dumb distributions relative to ‘`prefix'’.)

Obviously, for pure Python distributions, this isn’t any simpler than
just running ‘python setup.py install’—but for non-pure distributions,
which include extensions that would need to be compiled, it can mean the
difference between someone being able to use your extensions or not.
And creating "smart" built distributions, such as an RPM package or an
executable installer for Windows, is far more convenient for users even
if your distribution doesn’t include any extensions.

The ‘bdist’ command has a ‘--formats’ option, similar to the ‘sdist’
command, which you can use to select the types of built distribution to
generate: for example,

     python setup.py bdist --format=zip

would, when run on a Unix system, create
‘Distutils-1.0.`plat'.zip’—again, this archive would be unpacked from
the root directory to install the Distutils.

The available formats for built distributions are:

Format            描述                               註解
                                                     
-------------------------------------------------------------------
                                                     
‘gztar’           gzipped tar file (‘.tar.gz’)       (1)
                                                     
                                                     
‘bztar’           bzipped tar file (‘.tar.bz2’)
                  
                                                     
‘xztar’           xzipped tar file (‘.tar.xz’)
                  
                                                     
‘ztar’            compressed tar file (‘.tar.Z’)     (3)
                                                     
                                                     
‘tar’             tar file (‘.tar’)
                  
                                                     
‘zip’             zip file (‘.zip’)                  (2),(4)
                                                     
                                                     
‘rpm’             RPM                                (5)
                                                     
                                                     
‘pkgtool’         Solaris ‘pkgtool’
                  
                                                     
‘sdux’            HP-UX ‘swinstall’
                  
                                                     
‘wininst’         self-extracting ZIP file for       (4)
                  Windows                            
                  
                                                     
‘msi’             Microsoft Installer.
                  

3.5 版更變: Added support for the ‘xztar’ format.

註解：

  1. default on Unix

  2. default on Windows

  3. requires external ‘compress’ utility.

  4. requires either external ‘zip’ utility or *note zipfile: 143.
     module (part of the standard Python library since Python 1.6)

  5. requires external ‘rpm’ utility, version 3.0.4 or better (use ‘rpm
     --version’ to find out which version you have)

You don’t have to use the ‘bdist’ command with the ‘--formats’ option;
you can also use the command that directly implements the format you’re
interested in.  Some of these ‘bdist’ "sub-commands" actually generate
several similar formats; for instance, the ‘bdist_dumb’ command
generates all the "dumb" archive formats (‘tar’, ‘gztar’, ‘bztar’,
‘xztar’, ‘ztar’, and ‘zip’), and ‘bdist_rpm’ generates both binary and
source RPMs.  The ‘bdist’ sub-commands, and the formats generated by
each, are:

Command                        Formats
                               
-------------------------------------------------------------------------
                               
‘bdist_dumb’                   tar, gztar, bztar, xztar, ztar, zip
                               
                               
‘bdist_rpm’                    rpm, srpm
                               
                               
‘bdist_wininst’                wininst
                               
                               
‘bdist_msi’                    msi
                               

     備註: bdist_wininst is deprecated since Python 3.8.

The following sections give details on the individual ‘bdist_*’
commands.

* Menu:

* Creating RPM packages::
* Creating Windows Installers::
* Cross-compiling on Windows::
* Vista User Access Control (UAC): Vista User Access Control UAC.


File: python.info,  Node: Creating RPM packages,  Next: Creating Windows Installers,  Up: Creating Built Distributions

17.5.1 Creating RPM packages
----------------------------

The RPM format is used by many popular Linux distributions, including
Red Hat, SuSE, and Mandrake.  If one of these (or any of the other
RPM-based Linux distributions) is your usual environment, creating RPM
packages for other users of that same distribution is trivial.
Depending on the complexity of your module distribution and differences
between Linux distributions, you may also be able to create RPMs that
work on different RPM-based distributions.

The usual way to create an RPM of your module distribution is to run the
‘bdist_rpm’ command:

     python setup.py bdist_rpm

or the ‘bdist’ command with the ‘--format’ option:

     python setup.py bdist --formats=rpm

The former allows you to specify RPM-specific options; the latter allows
you to easily specify multiple formats in one run.  If you need to do
both, you can explicitly specify multiple ‘bdist_*’ commands and their
options:

     python setup.py bdist_rpm --packager="John Doe <jdoe@example.org>" \
                     bdist_wininst --target-version="2.0"

Creating RPM packages is driven by a ‘.spec’ file, much as using the
Distutils is driven by the setup script.  To make your life easier, the
‘bdist_rpm’ command normally creates a ‘.spec’ file based on the
information you supply in the setup script, on the command line, and in
any Distutils configuration files.  Various options and sections in the
‘.spec’ file are derived from options in the setup script as follows:

RPM ‘.spec’ file option or section             Distutils setup script option
                                               
--------------------------------------------------------------------------------------------------
                                               
Name                                           ‘name’
                                               
                                               
Summary (in preamble)                          ‘description’
                                               
                                               
Version                                        ‘version’
                                               
                                               
Vendor                                         ‘author’ and ‘author_email’, or — & ‘maintainer’
                                               and ‘maintainer_email’
                                               
                                               
版權宣告                                       ‘license’
                                               
                                               
Url                                            ‘url’
                                               
                                               
%description (section)                         ‘long_description’
                                               

Additionally, there are many options in ‘.spec’ files that don’t have
corresponding options in the setup script.  Most of these are handled
through options to the ‘bdist_rpm’ command as follows:

RPM ‘.spec’ file option or          ‘bdist_rpm’ option                default value
section                                                               

----------------------------------------------------------------------------------------------------
                                                                      
Release                             ‘release’                         "1"
                                                                      
                                                                      
Group                               ‘group’                           "Development/Libraries"
                                                                      
                                                                      
Vendor                              ‘vendor’                          (see above)
                                                                      
                                                                      
Packager                            ‘packager’                        (none)
                                                                      
                                                                      
Provides                            ‘provides’                        (none)
                                                                      
                                                                      
Requires                            ‘requires’                        (none)
                                                                      
                                                                      
Conflicts                           ‘conflicts’                       (none)
                                                                      
                                                                      
Obsoletes                           ‘obsoletes’                       (none)
                                                                      
                                                                      
Distribution                        ‘distribution_name’               (none)
                                                                      
                                                                      
BuildRequires                       ‘build_requires’                  (none)
                                                                      
                                                                      
Icon                                ‘icon’                            (none)
                                                                      

Obviously, supplying even a few of these options on the command-line
would be tedious and error-prone, so it’s usually best to put them in
the setup configuration file, ‘setup.cfg’—see section *note Writing the
Setup Configuration File: 4375.  If you distribute or package many
Python module distributions, you might want to put options that apply to
all of them in your personal Distutils configuration file
(‘~/.pydistutils.cfg’).  If you want to temporarily disable this file,
you can pass the ‘--no-user-cfg’ option to ‘setup.py’.

There are three steps to building a binary RPM package, all of which are
handled automatically by the Distutils:

  1. create a ‘.spec’ file, which describes the package (analogous to
     the Distutils setup script; in fact, much of the information in the
     setup script winds up in the ‘.spec’ file)

  2. create the source RPM

  3. create the "binary" RPM (which may or may not contain binary code,
     depending on whether your module distribution contains Python
     extensions)

Normally, RPM bundles the last two steps together; when you use the
Distutils, all three steps are typically bundled together.

If you wish, you can separate these three steps.  You can use the
‘--spec-only’ option to make ‘bdist_rpm’ just create the ‘.spec’ file
and exit; in this case, the ‘.spec’ file will be written to the
"distribution directory"—normally ‘dist/’, but customizable with the
‘--dist-dir’ option.  (Normally, the ‘.spec’ file winds up deep in the
"build tree," in a temporary directory created by ‘bdist_rpm’.)


File: python.info,  Node: Creating Windows Installers,  Next: Cross-compiling on Windows,  Prev: Creating RPM packages,  Up: Creating Built Distributions

17.5.2 Creating Windows Installers
----------------------------------

     警告: bdist_wininst is deprecated since Python 3.8.

Executable installers are the natural format for binary distributions on
Windows.  They display a nice graphical user interface, display some
information about the module distribution to be installed taken from the
metadata in the setup script, let the user select a few options, and
start or cancel the installation.

Since the metadata is taken from the setup script, creating Windows
installers is usually as easy as running:

     python setup.py bdist_wininst

or the ‘bdist’ command with the ‘--formats’ option:

     python setup.py bdist --formats=wininst

If you have a pure module distribution (only containing pure Python
modules and packages), the resulting installer will be version
independent and have a name like ‘foo-1.0.win32.exe’.  Note that
creating ‘wininst’ binary distributions in only supported on Windows
systems.

If you have a non-pure distribution, the extensions can only be created
on a Windows platform, and will be Python version dependent.  The
installer filename will reflect this and now has the form
‘foo-1.0.win32-py2.0.exe’.  You have to create a separate installer for
every Python version you want to support.

The installer will try to compile pure modules into *note bytecode: 619.
after installation on the target system in normal and optimizing mode.
If you don’t want this to happen for some reason, you can run the
‘bdist_wininst’ command with the ‘--no-target-compile’ and/or the
‘--no-target-optimize’ option.

By default the installer will display the cool "Python Powered" logo
when it is run, but you can also supply your own 152x261 bitmap which
must be a Windows ‘.bmp’ file with the ‘--bitmap’ option.

The installer will also display a large title on the desktop background
window when it is run, which is constructed from the name of your
distribution and the version number.  This can be changed to another
text by using the ‘--title’ option.

The installer file will be written to the "distribution directory" —
normally ‘dist/’, but customizable with the ‘--dist-dir’ option.


File: python.info,  Node: Cross-compiling on Windows,  Next: Vista User Access Control UAC,  Prev: Creating Windows Installers,  Up: Creating Built Distributions

17.5.3 Cross-compiling on Windows
---------------------------------

Starting with Python 2.6, distutils is capable of cross-compiling
between Windows platforms.  In practice, this means that with the
correct tools installed, you can use a 32bit version of Windows to
create 64bit extensions and vice-versa.

To build for an alternate platform, specify the ‘--plat-name’ option to
the build command.  Valid values are currently ’win32’, and ’win-amd64’.
For example, on a 32bit version of Windows, you could execute:

     python setup.py build --plat-name=win-amd64

to build a 64bit version of your extension.  The Windows Installers also
support this option, so the command:

     python setup.py build --plat-name=win-amd64 bdist_wininst

would create a 64bit installation executable on your 32bit version of
Windows.

To cross-compile, you must download the Python source code and
cross-compile Python itself for the platform you are targeting - it is
not possible from a binary installation of Python (as the .lib etc file
for other platforms are not included.)  In practice, this means the user
of a 32 bit operating system will need to use Visual Studio 2008 to open
the ‘PCbuild/PCbuild.sln’ solution in the Python source tree and build
the "x64" configuration of the ’pythoncore’ project before
cross-compiling extensions is possible.

Note that by default, Visual Studio 2008 does not install 64bit
compilers or tools.  You may need to reexecute the Visual Studio setup
process and select these tools (using Control Panel->[Add/Remove]
Programs is a convenient way to check or modify your existing install.)

* Menu:

* The Postinstallation script::


File: python.info,  Node: The Postinstallation script,  Up: Cross-compiling on Windows

17.5.3.1 The Postinstallation script
....................................

Starting with Python 2.3, a postinstallation script can be specified
with the ‘--install-script’ option.  The basename of the script must be
specified, and the script filename must also be listed in the scripts
argument to the setup function.

This script will be run at installation time on the target system after
all the files have been copied, with ‘argv[1]’ set to ‘-install’, and
again at uninstallation time before the files are removed with ‘argv[1]’
set to ‘-remove’.

The installation script runs embedded in the windows installer, every
output (‘sys.stdout’, ‘sys.stderr’) is redirected into a buffer and will
be displayed in the GUI after the script has finished.

Some functions especially useful in this context are available as
additional built-in functions in the installation script.

 -- 函式: directory_created (path)
 -- 函式: file_created (path)

     These functions should be called when a directory or file is
     created by the postinstall script at installation time.  It will
     register `path' with the uninstaller, so that it will be removed
     when the distribution is uninstalled.  To be safe, directories are
     only removed if they are empty.

 -- 函式: get_special_folder_path (csidl_string)

     This function can be used to retrieve special folder locations on
     Windows like the Start Menu or the Desktop.  It returns the full
     path to the folder.  `csidl_string' must be one of the following
     strings:

          "CSIDL_APPDATA"

          "CSIDL_COMMON_STARTMENU"
          "CSIDL_STARTMENU"

          "CSIDL_COMMON_DESKTOPDIRECTORY"
          "CSIDL_DESKTOPDIRECTORY"

          "CSIDL_COMMON_STARTUP"
          "CSIDL_STARTUP"

          "CSIDL_COMMON_PROGRAMS"
          "CSIDL_PROGRAMS"

          "CSIDL_FONTS"

     If the folder cannot be retrieved, *note OSError: 1d4. is raised.

     Which folders are available depends on the exact Windows version,
     and probably also the configuration.  For details refer to
     Microsoft’s documentation of the ‘SHGetSpecialFolderPath()’
     function.

 -- 函式: create_shortcut (target, description, filename[, arguments[,
          workdir[, iconpath[, iconindex]]]])

     This function creates a shortcut.  `target' is the path to the
     program to be started by the shortcut.  `description' is the
     description of the shortcut.  `filename' is the title of the
     shortcut that the user will see.  `arguments' specifies the command
     line arguments, if any.  `workdir' is the working directory for the
     program.  `iconpath' is the file containing the icon for the
     shortcut, and `iconindex' is the index of the icon in the file
     `iconpath'.  Again, for details consult the Microsoft documentation
     for the ‘IShellLink’ interface.


File: python.info,  Node: Vista User Access Control UAC,  Prev: Cross-compiling on Windows,  Up: Creating Built Distributions

17.5.4 Vista User Access Control (UAC)
--------------------------------------

Starting with Python 2.6, bdist_wininst supports a
‘--user-access-control’ option.  The default is ’none’ (meaning no UAC
handling is done), and other valid values are ’auto’ (meaning prompt for
UAC elevation if Python was installed for all users) and ’force’
(meaning always prompt for elevation).

     備註: bdist_wininst is deprecated since Python 3.8.


File: python.info,  Node: Distutils Examples,  Next: Extending Distutils,  Prev: Creating Built Distributions,  Up: 發布 Python 模組（舊版）

17.6 Distutils Examples
=======================

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

This chapter provides a number of basic examples to help get started
with distutils.  Additional information about using distutils can be
found in the Distutils Cookbook.

也參考
......

Distutils Cookbook(1)

     Collection of recipes showing how to achieve more control over
     distutils.

* Menu:

* Pure Python distribution (by module): Pure Python distribution by module.
* Pure Python distribution (by package): Pure Python distribution by package.
* Single extension module::
* Checking a package::
* Reading the metadata::

   ---------- Footnotes ----------

   (1) https://wiki.python.org/moin/Distutils/Cookbook


File: python.info,  Node: Pure Python distribution by module,  Next: Pure Python distribution by package,  Up: Distutils Examples

17.6.1 Pure Python distribution (by module)
-------------------------------------------

If you’re just distributing a couple of modules, especially if they
don’t live in a particular package, you can specify them individually
using the ‘py_modules’ option in the setup script.

In the simplest case, you’ll have two files to worry about: a setup
script and the single module you’re distributing, ‘foo.py’ in this
example:

     <root>/
             setup.py
             foo.py

(In all diagrams in this section, `<root>' will refer to the
distribution root directory.)  A minimal setup script to describe this
situation would be:

     from distutils.core import setup
     setup(name='foo',
           version='1.0',
           py_modules=['foo'],
           )

Note that the name of the distribution is specified independently with
the ‘name’ option, and there’s no rule that says it has to be the same
as the name of the sole module in the distribution (although that’s
probably a good convention to follow).  However, the distribution name
is used to generate filenames, so you should stick to letters, digits,
underscores, and hyphens.

Since ‘py_modules’ is a list, you can of course specify multiple
modules, eg.  if you’re distributing modules ‘foo’ and ‘bar’, your setup
might look like this:

     <root>/
             setup.py
             foo.py
             bar.py

and the setup script might be

     from distutils.core import setup
     setup(name='foobar',
           version='1.0',
           py_modules=['foo', 'bar'],
           )

You can put module source files into another directory, but if you have
enough modules to do that, it’s probably easier to specify modules by
package rather than listing them individually.


File: python.info,  Node: Pure Python distribution by package,  Next: Single extension module,  Prev: Pure Python distribution by module,  Up: Distutils Examples

17.6.2 Pure Python distribution (by package)
--------------------------------------------

If you have more than a couple of modules to distribute, especially if
they are in multiple packages, it’s probably easier to specify whole
packages rather than individual modules.  This works even if your
modules are not in a package; you can just tell the Distutils to process
modules from the root package, and that works the same as any other
package (except that you don’t have to have an ‘__init__.py’ file).

The setup script from the last example could also be written as

     from distutils.core import setup
     setup(name='foobar',
           version='1.0',
           packages=[''],
           )

(The empty string stands for the root package.)

If those two files are moved into a subdirectory, but remain in the root
package, e.g.:

     <root>/
             setup.py
             src/      foo.py
                       bar.py

then you would still specify the root package, but you have to tell the
Distutils where source files in the root package live:

     from distutils.core import setup
     setup(name='foobar',
           version='1.0',
           package_dir={'': 'src'},
           packages=[''],
           )

More typically, though, you will want to distribute multiple modules in
the same package (or in sub-packages).  For example, if the ‘foo’ and
‘bar’ modules belong in package ‘foobar’, one way to layout your source
tree is

     <root>/
             setup.py
             foobar/
                      __init__.py
                      foo.py
                      bar.py

This is in fact the default layout expected by the Distutils, and the
one that requires the least work to describe in your setup script:

     from distutils.core import setup
     setup(name='foobar',
           version='1.0',
           packages=['foobar'],
           )

If you want to put modules in directories not named for their package,
then you need to use the ‘package_dir’ option again.  For example, if
the ‘src’ directory holds modules in the ‘foobar’ package:

     <root>/
             setup.py
             src/
                      __init__.py
                      foo.py
                      bar.py

an appropriate setup script would be

     from distutils.core import setup
     setup(name='foobar',
           version='1.0',
           package_dir={'foobar': 'src'},
           packages=['foobar'],
           )

Or, you might put modules from your main package right in the
distribution root:

     <root>/
             setup.py
             __init__.py
             foo.py
             bar.py

in which case your setup script would be

     from distutils.core import setup
     setup(name='foobar',
           version='1.0',
           package_dir={'foobar': ''},
           packages=['foobar'],
           )

(The empty string also stands for the current directory.)

If you have sub-packages, they must be explicitly listed in ‘packages’,
but any entries in ‘package_dir’ automatically extend to sub-packages.
(In other words, the Distutils does `not' scan your source tree, trying
to figure out which directories correspond to Python packages by looking
for ‘__init__.py’ files.)  Thus, if the default layout grows a
sub-package:

     <root>/
             setup.py
             foobar/
                      __init__.py
                      foo.py
                      bar.py
                      subfoo/
                                __init__.py
                                blah.py

then the corresponding setup script would be

     from distutils.core import setup
     setup(name='foobar',
           version='1.0',
           packages=['foobar', 'foobar.subfoo'],
           )


File: python.info,  Node: Single extension module,  Next: Checking a package,  Prev: Pure Python distribution by package,  Up: Distutils Examples

17.6.3 Single extension module
------------------------------

Extension modules are specified using the ‘ext_modules’ option.
‘package_dir’ has no effect on where extension source files are found;
it only affects the source for pure Python modules.  The simplest case,
a single extension module in a single C source file, is:

     <root>/
             setup.py
             foo.c

If the ‘foo’ extension belongs in the root package, the setup script for
this could be

     from distutils.core import setup
     from distutils.extension import Extension
     setup(name='foobar',
           version='1.0',
           ext_modules=[Extension('foo', ['foo.c'])],
           )

If the extension actually belongs in a package, say ‘foopkg’, then

With exactly the same source tree layout, this extension can be put in
the ‘foopkg’ package simply by changing the name of the extension:

     from distutils.core import setup
     from distutils.extension import Extension
     setup(name='foobar',
           version='1.0',
           ext_modules=[Extension('foopkg.foo', ['foo.c'])],
           )


File: python.info,  Node: Checking a package,  Next: Reading the metadata,  Prev: Single extension module,  Up: Distutils Examples

17.6.4 Checking a package
-------------------------

The ‘check’ command allows you to verify if your package meta-data meet
the minimum requirements to build a distribution.

To run it, just call it using your ‘setup.py’ script.  If something is
missing, ‘check’ will display a warning.

Let’s take an example with a simple script:

     from distutils.core import setup

     setup(name='foobar')

Running the ‘check’ command will display some warnings:

     $ python setup.py check
     running check
     warning: check: missing required meta-data: version, url
     warning: check: missing meta-data: either (author and author_email) or
              (maintainer and maintainer_email) must be supplied

If you use the reStructuredText syntax in the ‘long_description’ field
and docutils(1) is installed you can check if the syntax is fine with
the ‘check’ command, using the ‘restructuredtext’ option.

For example, if the ‘setup.py’ script is changed like this:

     from distutils.core import setup

     desc = """\
     My description
     ==============

     This is the description of the ``foobar`` package.
     """

     setup(name='foobar', version='1', author='tarek',
         author_email='tarek@ziade.org',
         url='http://example.com', long_description=desc)

Where the long description is broken, ‘check’ will be able to detect it
by using the ‘docutils’ parser:

     $ python setup.py check --restructuredtext
     running check
     warning: check: Title underline too short. (line 2)
     warning: check: Could not finish the parsing.

   ---------- Footnotes ----------

   (1) http://docutils.sourceforge.net


File: python.info,  Node: Reading the metadata,  Prev: Checking a package,  Up: Distutils Examples

17.6.5 Reading the metadata
---------------------------

The *note distutils.core.setup(): 3b71. function provides a command-line
interface that allows you to query the metadata fields of a project
through the ‘setup.py’ script of a given project:

     $ python setup.py --name
     distribute

This call reads the ‘name’ metadata by running the *note
distutils.core.setup(): 3b71. function.  Although, when a source or
binary distribution is created with Distutils, the metadata fields are
written in a static file called ‘PKG-INFO’.  When a Distutils-based
project is installed in Python, the ‘PKG-INFO’ file is copied alongside
the modules and packages of the distribution under
‘NAME-VERSION-pyX.X.egg-info’, where ‘NAME’ is the name of the project,
‘VERSION’ its version as defined in the Metadata, and ‘pyX.X’ the major
and minor version of Python like ‘2.7’ or ‘3.2’.

You can read back this static file, by using the
‘distutils.dist.DistributionMetadata’ class and its ‘read_pkg_file()’
method:

     >>> from distutils.dist import DistributionMetadata
     >>> metadata = DistributionMetadata()
     >>> metadata.read_pkg_file(open('distribute-0.6.8-py2.7.egg-info'))
     >>> metadata.name
     'distribute'
     >>> metadata.version
     '0.6.8'
     >>> metadata.description
     'Easily download, build, install, upgrade, and uninstall Python packages'

Notice that the class can also be instantiated with a metadata file path
to loads its values:

     >>> pkg_info_path = 'distribute-0.6.8-py2.7.egg-info'
     >>> DistributionMetadata(pkg_info_path).name
     'distribute'


File: python.info,  Node: Extending Distutils,  Next: 指令參照,  Prev: Distutils Examples,  Up: 發布 Python 模組（舊版）

17.7 Extending Distutils
========================

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

Distutils can be extended in various ways.  Most extensions take the
form of new commands or replacements for existing commands.  New
commands may be written to support new types of platform-specific
packaging, for example, while replacements for existing commands may be
made to modify details of how the command operates on a package.

Most extensions of the distutils are made within ‘setup.py’ scripts that
want to modify existing commands; many simply add a few file extensions
that should be copied into packages in addition to ‘.py’ files as a
convenience.

Most distutils command implementations are subclasses of the *note
distutils.cmd.Command: 439e. class.  New commands may directly inherit
from ‘Command’, while replacements often derive from ‘Command’
indirectly, directly subclassing the command they are replacing.
Commands are required to derive from ‘Command’.

* Menu:

* Integrating new commands::
* Adding new distribution types::


File: python.info,  Node: Integrating new commands,  Next: Adding new distribution types,  Up: Extending Distutils

17.7.1 Integrating new commands
-------------------------------

There are different ways to integrate new command implementations into
distutils.  The most difficult is to lobby for the inclusion of the new
features in distutils itself, and wait for (and require) a version of
Python that provides that support.  This is really hard for many
reasons.

The most common, and possibly the most reasonable for most needs, is to
include the new implementations with your ‘setup.py’ script, and cause
the *note distutils.core.setup(): 3b71. function use them:

     from distutils.command.build_py import build_py as _build_py
     from distutils.core import setup

     class build_py(_build_py):
         """Specialized Python source builder."""

         # implement whatever needs to be different...

     setup(cmdclass={'build_py': build_py},
           ...)

This approach is most valuable if the new implementations must be used
to use a particular package, as everyone interested in the package will
need to have the new command implementation.

Beginning with Python 2.4, a third option is available, intended to
allow new commands to be added which can support existing ‘setup.py’
scripts without requiring modifications to the Python installation.
This is expected to allow third-party extensions to provide support for
additional packaging systems, but the commands can be used for anything
distutils commands can be used for.  A new configuration option,
‘command_packages’ (command-line option ‘--command-packages’), can be
used to specify additional packages to be searched for modules
implementing commands.  Like all distutils options, this can be
specified on the command line or in a configuration file.  This option
can only be set in the ‘[global]’ section of a configuration file, or
before any commands on the command line.  If set in a configuration
file, it can be overridden from the command line; setting it to an empty
string on the command line causes the default to be used.  This should
never be set in a configuration file provided with a package.

This new option can be used to add any number of packages to the list of
packages searched for command implementations; multiple package names
should be separated by commas.  When not specified, the search is only
performed in the *note distutils.command: 3e. package.  When ‘setup.py’
is run with the option ‘--command-packages distcmds,buildcmds’, however,
the packages *note distutils.command: 3e, ‘distcmds’, and ‘buildcmds’
will be searched in that order.  New commands are expected to be
implemented in modules of the same name as the command by classes
sharing the same name.  Given the example command line option above, the
command ‘bdist_openpkg’ could be implemented by the class
‘distcmds.bdist_openpkg.bdist_openpkg’ or
‘buildcmds.bdist_openpkg.bdist_openpkg’.


File: python.info,  Node: Adding new distribution types,  Prev: Integrating new commands,  Up: Extending Distutils

17.7.2 Adding new distribution types
------------------------------------

Commands that create distributions (files in the ‘dist/’ directory) need
to add ‘(command, filename)’ pairs to ‘self.distribution.dist_files’ so
that ‘upload’ can upload it to PyPI. The `filename' in the pair contains
no path information, only the name of the file itself.  In dry-run mode,
pairs should still be added to represent what would have been created.


File: python.info,  Node: 指令參照,  Next: API參照,  Prev: Extending Distutils,  Up: 發布 Python 模組（舊版）

17.8 指令參照
=============

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

* Menu:

* Installing modules; the install command family: Installing modules the install command family.
* Creating a source distribution; the sdist command: Creating a source distribution the sdist command.


File: python.info,  Node: Installing modules the install command family,  Next: Creating a source distribution the sdist command,  Up: 指令參照

17.8.1 Installing modules: the ‘install’ command family
-------------------------------------------------------

The install command ensures that the build commands have been run and
then runs the subcommands ‘install_lib’, ‘install_data’ and
‘install_scripts’.

* Menu:

* install_data::
* install_scripts::


File: python.info,  Node: install_data,  Next: install_scripts,  Up: Installing modules the install command family

17.8.1.1 ‘install_data’
.......................

This command installs all data files provided with the distribution.


File: python.info,  Node: install_scripts,  Prev: install_data,  Up: Installing modules the install command family

17.8.1.2 ‘install_scripts’
..........................

This command installs all (Python) scripts in the distribution.


File: python.info,  Node: Creating a source distribution the sdist command,  Prev: Installing modules the install command family,  Up: 指令參照

17.8.2 Creating a source distribution: the ‘sdist’ command
----------------------------------------------------------

The manifest template commands are:

Command                                         描述
                                                
----------------------------------------------------------------------------------------------------
                                                
‘include pat1 pat2 ...’                         include all files matching any of the listed
                                                patterns
                                                
                                                
‘exclude pat1 pat2 ...’                         exclude all files matching any of the listed
                                                patterns
                                                
                                                
‘recursive-include dir pat1 pat2 ...’           include all files under `dir' matching any of the
                                                listed patterns
                                                
                                                
‘recursive-exclude dir pat1 pat2 ...’           exclude all files under `dir' matching any of the
                                                listed patterns
                                                
                                                
‘global-include pat1 pat2 ...’                  include all files anywhere in the source tree
                                                matching — & any of the listed patterns
                                                
                                                
‘global-exclude pat1 pat2 ...’                  exclude all files anywhere in the source tree
                                                matching — & any of the listed patterns
                                                
                                                
‘prune dir’                                     exclude all files under `dir'
                                                
                                                
‘graft dir’                                     include all files under `dir'
                                                

The patterns here are Unix-style "glob" patterns: ‘*’ matches any
sequence of regular filename characters, ‘?’ matches any single regular
filename character, and ‘[range]’ matches any of the characters in
`range' (e.g., ‘a-z’, ‘a-zA-Z’, ‘a-f0-9_.’).  The definition of "regular
filename character" is platform-specific: on Unix it is anything except
slash; on Windows anything except backslash or colon.


File: python.info,  Node: API參照,  Prev: 指令參照,  Up: 發布 Python 模組（舊版）

17.9 API參照
============

也參考
......

New and changed setup.py arguments in setuptools(1)

     The ‘setuptools’ project adds new capabilities to the ‘setup’
     function and other APIs, makes the API consistent across different
     Python versions, and is hence recommended over using ‘distutils’
     directly.

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

* Menu:

* distutils.core: distutils core --- Core Distutils functionality. Core Distutils functionality
* distutils.ccompiler: distutils ccompiler --- CCompiler base class. CCompiler base class
* distutils.unixccompiler: distutils unixccompiler --- Unix C Compiler. Unix C Compiler
* distutils.msvccompiler: distutils msvccompiler --- Microsoft Compiler. Microsoft Compiler
* distutils.bcppcompiler: distutils bcppcompiler --- Borland Compiler. Borland Compiler
* distutils.cygwincompiler: distutils cygwincompiler --- Cygwin Compiler. Cygwin Compiler
* distutils.archive_util: distutils archive_util --- Archiving utilities. Archiving utilities
* distutils.dep_util: distutils dep_util --- Dependency checking. Dependency checking
* distutils.dir_util: distutils dir_util --- Directory tree operations. Directory tree operations
* distutils.file_util: distutils file_util --- Single file operations. Single file operations
* distutils.util: distutils util --- Miscellaneous other utility functions. Miscellaneous other utility functions
* distutils.dist: distutils dist --- The Distribution class. The Distribution class
* distutils.extension: distutils extension --- The Extension class. The Extension class
* distutils.debug: distutils debug --- Distutils debug mode. Distutils debug mode
* distutils.errors: distutils errors --- Distutils exceptions. Distutils exceptions
* distutils.fancy_getopt: distutils fancy_getopt --- Wrapper around the standard getopt module. Wrapper around the standard getopt module
* distutils.filelist: distutils filelist --- The FileList class. The FileList class
* distutils.log: distutils log --- Simple PEP 282-style logging. Simple PEP 282-style logging
* distutils.spawn: distutils spawn --- Spawn a sub-process. Spawn a sub-process
* distutils.sysconfig: distutils sysconfig --- System configuration information. System configuration information
* distutils.text_file: distutils text_file --- The TextFile class. The TextFile class
* distutils.version: distutils version --- Version number classes. Version number classes
* distutils.cmd: distutils cmd --- Abstract base class for Distutils commands. Abstract base class for Distutils commands
* Creating a new Distutils command::
* distutils.command: distutils command --- Individual Distutils commands. Individual Distutils commands
* distutils.command.bdist: distutils command bdist --- Build a binary installer. Build a binary installer
* distutils.command.bdist_packager: distutils command bdist_packager --- Abstract base class for packagers. Abstract base class for packagers
* distutils.command.bdist_dumb: distutils command bdist_dumb --- Build a "dumb" installer. Build a "dumb" installer
* distutils.command.bdist_msi: distutils command bdist_msi --- Build a Microsoft Installer binary package. Build a Microsoft Installer binary package
* distutils.command.bdist_rpm: distutils command bdist_rpm --- Build a binary distribution as a Redhat RPM and SRPM. Build a binary distribution as a Redhat RPM and
                               SRPM
* distutils.command.bdist_wininst: distutils command bdist_wininst --- Build a Windows installer. Build a Windows installer
* distutils.command.sdist: distutils command sdist --- Build a source distribution. Build a source distribution
* distutils.command.build: distutils command build --- Build all files of a package. Build all files of a package
* distutils.command.build_clib: distutils command build_clib --- Build any C libraries in a package. Build any C libraries in a package
* distutils.command.build_ext: distutils command build_ext --- Build any extensions in a package. Build any extensions in a package
* distutils.command.build_py: distutils command build_py --- Build the py/ pyc files of a package. Build the .py/.pyc files of a package
* distutils.command.build_scripts: distutils command build_scripts --- Build the scripts of a package. Build the scripts of a package
* distutils.command.clean: distutils command clean --- Clean a package build area. Clean a package build area
* distutils.command.config: distutils command config --- Perform package configuration. Perform package configuration
* distutils.command.install: distutils command install --- Install a package. Install a package
* distutils.command.install_data: distutils command install_data --- Install data files from a package. Install data files from a package
* distutils.command.install_headers: distutils command install_headers --- Install C/C++ header files from a package. Install C/C++ header files from a package
* distutils.command.install_lib: distutils command install_lib --- Install library files from a package. Install library files from a package
* distutils.command.install_scripts: distutils command install_scripts --- Install script files from a package. Install script files from a package
* distutils.command.register: distutils command register --- Register a module with the Python Package Index. Register a module with the Python Package Index
* distutils.command.check: distutils command check --- Check the meta-data of a package. Check the meta-data of a package

   ---------- Footnotes ----------

   (1) 
https://setuptools.readthedocs.io/en/latest/setuptools.html#new-and-changed-setup-keywords


File: python.info,  Node: distutils core --- Core Distutils functionality,  Next: distutils ccompiler --- CCompiler base class,  Up: API參照

17.9.1 ‘distutils.core’ — Core Distutils functionality
------------------------------------------------------

The *note distutils.core: 54. module is the only module that needs to be
installed to use the Distutils.  It provides the *note setup(): 3b71.
(which is called from the setup script).  Indirectly provides the
‘distutils.dist.Distribution’ and *note distutils.cmd.Command: 439e.
class.

 -- 函式: distutils.core.setup (arguments)

     The basic do-everything function that does most everything you
     could ever ask for from a Distutils method.

     The setup function takes a large number of arguments.  These are
     laid out in the following table.

     argument name            value                                type
                                                                   
     --------------------------------------------------------------------------------------------------------------------------------
                                                                   
     `name'                   The name of the package              a string
                                                                   
                                                                   
     `version'                The version number of the package;   a string
                              see *note distutils.version: 66.     
                              
                                                                   
     `description'            A single line describing the         a string
                              package                              
                              
                                                                   
     `long_description'       Longer description of the package    a string
                                                                   
                                                                   
     `author'                 The name of the package author       a string
                                                                   
                                                                   
     `author_email'           The email address of the package     a string
                              author                               
                              
                                                                   
     `maintainer'             The name of the current              a string
                              maintainer, if different from the    
                              author.  Note that if the
                              maintainer is provided, distutils
                              will use it as the author in
                              ‘PKG-INFO’
                              
                                                                   
     `maintainer_email'       The email address of the current     a string
                              maintainer, if different from the    
                              author
                              
                                                                   
     `url'                    A URL for the package (homepage)     a string
                                                                   
                                                                   
     `download_url'           A URL to download the package        a string
                                                                   
                                                                   
     `packages'               A list of Python packages that       a list of strings
                              distutils will manipulate            
                              
                                                                   
     `py_modules'             A list of Python modules that        a list of strings
                              distutils will manipulate            
                              
                                                                   
     `scripts'                A list of standalone script files    a list of strings
                              to be built and installed            
                              
                                                                   
     `ext_modules'            A list of Python extensions to be    a list of instances of *note distutils.core.Extension: 4364.
                              built                                
                              
                                                                   
     `classifiers'            A list of categories for the         a list of strings; valid classifiers are listed on PyPI(1).
                              package                              
                              
                                                                   
     `distclass'              the *note Distribution: 43af.        a subclass of *note distutils.core.Distribution: 43af.
                              class to use                         
                              
                                                                   
     `script_name'            The name of the setup.py script -    a string
                              defaults to ‘sys.argv[0]’            
                              
                                                                   
     `script_args'            Arguments to supply to the setup     a list of strings
                              script                               
                              
                                                                   
     `options'                default options for the setup        a dictionary
                              script                               
                              
                                                                   
     `license'                The license for the package          a string
                                                                   
                                                                   
     `keywords'               Descriptive meta-data, see PEP       a list of strings or a comma-separated string
                              314(2)                               
                              
                                                                   
     `platforms'                                                   a list of strings or a comma-separated string
                                                                   
                                                                   
     `cmdclass'               A mapping of command names to        a dictionary
                              *note Command: 43b0. subclasses      
                              
                                                                   
     `data_files'             A list of data files to install      a list
                                                                   
                                                                   
     `package_dir'            A mapping of package to directory    a dictionary
                              names                                
                              

 -- 函式: distutils.core.run_setup (script_name[, script_args=None,
          stop_after='run'])

     Run a setup script in a somewhat controlled environment, and return
     the ‘distutils.dist.Distribution’ instance that drives things.
     This is useful if you need to find out the distribution meta-data
     (passed as keyword args from `script' to *note setup(): 3b71.), or
     the contents of the config files or command-line.

     `script_name' is a file that will be read and run with *note
     exec(): c49.  ‘sys.argv[0]’ will be replaced with `script' for the
     duration of the call.  `script_args' is a list of strings; if
     supplied, ‘sys.argv[1:]’ will be replaced by `script_args' for the
     duration of the call.

     `stop_after' tells *note setup(): 3b71. when to stop processing;
     possible values:

     value               description
                         
     ----------------------------------------------------------------------
                         
     `init'              Stop after the *note Distribution: 43af.
                         instance has been created and populated with
                         the keyword arguments to *note setup(): 3b71.
                         
                         
     `config'            Stop after config files have been parsed (and
                         their data stored in the
                         *note Distribution: 43af. instance)
                         
                         
     `commandline'       Stop after the command-line (‘sys.argv[1:]’ or
                         `script_args') have been parsed (and the data
                         stored in the *note Distribution: 43af.
                         instance.)
                         
                         
     `run'               Stop after all commands have been run (the same
                         as if *note setup(): 3b71. had been called in
                         the usual way).  This is the default value.
                         

In addition, the *note distutils.core: 54. module exposed a number of
classes that live elsewhere.

   * ‘Extension’ from *note distutils.extension: 5b.

   * *note Command: 439e. from *note distutils.cmd: 3d.

   * ‘Distribution’ from *note distutils.dist: 59.

A short description of each of these follows, but see the relevant
module for the full reference.

 -- 類別: distutils.core.Extension

     The Extension class describes a single C or C++ extension module in
     a setup script.  It accepts the following keyword arguments in its
     constructor:

     argument name                value                                type
                                                                       
     --------------------------------------------------------------------------------------------------
                                                                       
     `name'                       the full name of the extension,      a string
                                  including any packages — ie.         
                                  `not' a filename or pathname, but
                                  Python dotted name
                                  
                                                                       
     `sources'                    list of source filenames, relative   a list of strings
                                  to the distribution root (where      
                                  the setup script lives), in Unix
                                  form (slash-separated) for
                                  portability.  Source files may be
                                  C, C++, SWIG (.i),
                                  platform-specific resource files,
                                  or whatever else is recognized by
                                  the ‘build_ext’ command as source
                                  for a Python extension.
                                  
                                                                       
     `include_dirs'               list of directories to search for    a list of strings
                                  C/C++ header files (in Unix form     
                                  for portability)
                                  
                                                                       
     `define_macros'              list of macros to define; each       a list of tuples
                                  macro is defined using a 2-tuple     
                                  ‘(name, value)’, where `value' is
                                  either the string to define it to
                                  or ‘None’ to define it without a
                                  particular value (equivalent of
                                  ‘#define FOO’ in source or ‘-DFOO’
                                  on Unix C compiler command line)
                                  
                                                                       
     `undef_macros'               list of macros to undefine           a list of strings
                                  explicitly                           
                                  
                                                                       
     `library_dirs'               list of directories to search for    a list of strings
                                  C/C++ libraries at link time         
                                  
                                                                       
     `libraries'                  list of library names (not           a list of strings
                                  filenames or paths) to link          
                                  against
                                  
                                                                       
     `runtime_library_dirs'       list of directories to search for    a list of strings
                                  C/C++ libraries at run time (for     
                                  shared extensions, this is when
                                  the extension is loaded)
                                  
                                                                       
     `extra_objects'              list of extra files to link with     a list of strings
                                  (eg.  object files not implied by    
                                  ’sources’, static library that
                                  must be explicitly specified,
                                  binary resource files, etc.)
                                  
                                                                       
     `extra_compile_args'         any extra platform- and              a list of strings
                                  compiler-specific information to     
                                  use when compiling the source
                                  files in ’sources’.  For platforms
                                  and compilers where a command line
                                  makes sense, this is typically a
                                  list of command-line arguments,
                                  but for other platforms it could
                                  be anything.
                                  
                                                                       
     `extra_link_args'            any extra platform- and              a list of strings
                                  compiler-specific information to     
                                  use when linking object files
                                  together to create the extension
                                  (or to create a new static Python
                                  interpreter).  Similar
                                  interpretation as for
                                  ’extra_compile_args’.
                                  
                                                                       
     `export_symbols'             list of symbols to be exported       a list of strings
                                  from a shared extension.  Not used   
                                  on all platforms, and not
                                  generally necessary for Python
                                  extensions, which typically export
                                  exactly one symbol: ‘init’ +
                                  extension_name.
                                  
                                                                       
     `depends'                    list of files that the extension     a list of strings
                                  depends on                           
                                  
                                                                       
     `language'                   extension language (i.e.  ‘'c'’,     a string
                                  ‘'c++'’, ‘'objc'’).  Will be         
                                  detected from the source
                                  extensions if not provided.
                                  
                                                                       
     `optional'                   specifies that a build failure in    a boolean
                                  the extension should not abort the   
                                  build process, but simply skip the
                                  extension.
                                  

     3.8 版更變: On Unix, C extensions are no longer linked to libpython
     except on Android and Cygwin.

 -- 類別: distutils.core.Distribution

     A *note Distribution: 43af. describes how to build, install and
     package up a Python software package.

     See the *note setup(): 3b71. function for a list of keyword
     arguments accepted by the Distribution constructor.  *note setup():
     3b71. creates a Distribution instance.

     3.7 版更變: *note Distribution: 43af. now warns if ‘classifiers’,
     ‘keywords’ and ‘platforms’ fields are not specified as a list or a
     string.

 -- 類別: distutils.core.Command

     A *note Command: 43b0. class (or rather, an instance of one of its
     subclasses) implement a single distutils command.

   ---------- Footnotes ----------

   (1) https://pypi.org/classifiers

   (2) https://www.python.org/dev/peps/pep-0314


File: python.info,  Node: distutils ccompiler --- CCompiler base class,  Next: distutils unixccompiler --- Unix C Compiler,  Prev: distutils core --- Core Distutils functionality,  Up: API參照

17.9.2 ‘distutils.ccompiler’ — CCompiler base class
---------------------------------------------------

This module provides the abstract base class for the *note CCompiler:
43b3. classes.  A *note CCompiler: 43b3. instance can be used for all
the compile and link steps needed to build a single project.  Methods
are provided to set options for the compiler — macro definitions,
include directories, link path, libraries and the like.

This module provides the following functions.

 -- 函式: distutils.ccompiler.gen_lib_options (compiler, library_dirs,
          runtime_library_dirs, libraries)

     Generate linker options for searching library directories and
     linking with specific libraries.  `libraries' and `library_dirs'
     are, respectively, lists of library names (not filenames!)  and
     search directories.  Returns a list of command-line options
     suitable for use with some compiler (depending on the two format
     strings passed in).

 -- 函式: distutils.ccompiler.gen_preprocess_options (macros,
          include_dirs)

     Generate C pre-processor options (‘-D’, ‘-U’, ‘-I’) as used by at
     least two types of compilers: the typical Unix compiler and Visual
     C++.  `macros' is the usual thing, a list of 1- or 2-tuples, where
     ‘(name,)’ means undefine (‘-U’) macro `name', and ‘(name, value)’
     means define (‘-D’) macro `name' to `value'.  `include_dirs' is
     just a list of directory names to be added to the header file
     search path (‘-I’).  Returns a list of command-line options
     suitable for either Unix compilers or Visual C++.

 -- 函式: distutils.ccompiler.get_default_compiler (osname, platform)

     Determine the default compiler to use for the given platform.

     `osname' should be one of the standard Python OS names (i.e.  the
     ones returned by ‘os.name’) and `platform' the common value
     returned by ‘sys.platform’ for the platform in question.

     The default values are ‘os.name’ and ‘sys.platform’ in case the
     parameters are not given.

 -- 函式: distutils.ccompiler.new_compiler (plat=None, compiler=None,
          verbose=0, dry_run=0, force=0)

     Factory function to generate an instance of some CCompiler subclass
     for the supplied platform/compiler combination.  `plat' defaults to
     ‘os.name’ (eg.  ‘'posix'’, ‘'nt'’), and `compiler' defaults to the
     default compiler for that platform.  Currently only ‘'posix'’ and
     ‘'nt'’ are supported, and the default compilers are "traditional
     Unix interface" (‘UnixCCompiler’ class) and Visual C++
     (‘MSVCCompiler’ class).  Note that it’s perfectly possible to ask
     for a Unix compiler object under Windows, and a Microsoft compiler
     object under Unix—if you supply a value for `compiler', `plat' is
     ignored.

 -- 函式: distutils.ccompiler.show_compilers ()

     Print list of available compilers (used by the ‘--help-compiler’
     options to ‘build’, ‘build_ext’, ‘build_clib’).

 -- 類別: distutils.ccompiler.CCompiler ([verbose=0, dry_run=0,
          force=0])

     The abstract base class *note CCompiler: 43b3. defines the
     interface that must be implemented by real compiler classes.  The
     class also has some utility methods used by several compiler
     classes.

     The basic idea behind a compiler abstraction class is that each
     instance can be used for all the compile/link steps in building a
     single project.  Thus, attributes common to all of those compile
     and link steps — include directories, macros to define, libraries
     to link against, etc.  — are attributes of the compiler instance.
     To allow for variability in how individual files are treated, most
     of those attributes may be varied on a per-compilation or per-link
     basis.

     The constructor for each subclass creates an instance of the
     Compiler object.  Flags are `verbose' (show verbose output),
     `dry_run' (don’t actually execute the steps) and `force' (rebuild
     everything, regardless of dependencies).  All of these flags
     default to ‘0’ (off).  Note that you probably don’t want to
     instantiate *note CCompiler: 43b3. or one of its subclasses
     directly - use the ‘distutils.CCompiler.new_compiler()’ factory
     function instead.

     The following methods allow you to manually alter compiler options
     for the instance of the Compiler class.

      -- 成員函式: add_include_dir (dir)

          Add `dir' to the list of directories that will be searched for
          header files.  The compiler is instructed to search
          directories in the order in which they are supplied by
          successive calls to *note add_include_dir(): 43b9.

      -- 成員函式: set_include_dirs (dirs)

          Set the list of directories that will be searched to `dirs' (a
          list of strings).  Overrides any preceding calls to *note
          add_include_dir(): 43b9.; subsequent calls to *note
          add_include_dir(): 43b9. add to the list passed to *note
          set_include_dirs(): 43ba.  This does not affect any list of
          standard include directories that the compiler may search by
          default.

      -- 成員函式: add_library (libname)

          Add `libname' to the list of libraries that will be included
          in all links driven by this compiler object.  Note that
          `libname' should *not* be the name of a file containing a
          library, but the name of the library itself: the actual
          filename will be inferred by the linker, the compiler, or the
          compiler class (depending on the platform).

          The linker will be instructed to link against libraries in the
          order they were supplied to *note add_library(): 43bb. and/or
          *note set_libraries(): 43bc.  It is perfectly valid to
          duplicate library names; the linker will be instructed to link
          against libraries as many times as they are mentioned.

      -- 成員函式: set_libraries (libnames)

          Set the list of libraries to be included in all links driven
          by this compiler object to `libnames' (a list of strings).
          This does not affect any standard system libraries that the
          linker may include by default.

      -- 成員函式: add_library_dir (dir)

          Add `dir' to the list of directories that will be searched for
          libraries specified to *note add_library(): 43bb. and *note
          set_libraries(): 43bc.  The linker will be instructed to
          search for libraries in the order they are supplied to *note
          add_library_dir(): 43bd. and/or *note set_library_dirs():
          43be.

      -- 成員函式: set_library_dirs (dirs)

          Set the list of library search directories to `dirs' (a list
          of strings).  This does not affect any standard library search
          path that the linker may search by default.

      -- 成員函式: add_runtime_library_dir (dir)

          Add `dir' to the list of directories that will be searched for
          shared libraries at runtime.

      -- 成員函式: set_runtime_library_dirs (dirs)

          Set the list of directories to search for shared libraries at
          runtime to `dirs' (a list of strings).  This does not affect
          any standard search path that the runtime linker may search by
          default.

      -- 成員函式: define_macro (name[, value=None])

          Define a preprocessor macro for all compilations driven by
          this compiler object.  The optional parameter `value' should
          be a string; if it is not supplied, then the macro will be
          defined without an explicit value and the exact outcome
          depends on the compiler used.

      -- 成員函式: undefine_macro (name)

          Undefine a preprocessor macro for all compilations driven by
          this compiler object.  If the same macro is defined by *note
          define_macro(): 43c1. and undefined by *note undefine_macro():
          43c2. the last call takes precedence (including multiple
          redefinitions or undefinitions).  If the macro is
          redefined/undefined on a per-compilation basis (ie.  in the
          call to *note compile(): 1b5.), then that takes precedence.

      -- 成員函式: add_link_object (object)

          Add `object' to the list of object files (or analogues, such
          as explicitly named library files or the output of "resource
          compilers") to be included in every link driven by this
          compiler object.

      -- 成員函式: set_link_objects (objects)

          Set the list of object files (or analogues) to be included in
          every link to `objects'.  This does not affect any standard
          object files that the linker may include by default (such as
          system libraries).

     The following methods implement methods for autodetection of
     compiler options, providing some functionality similar to GNU
     ‘autoconf’.

      -- 成員函式: detect_language (sources)

          Detect the language of a given file, or list of files.  Uses
          the instance attributes ‘language_map’ (a dictionary), and
          ‘language_order’ (a list) to do the job.

      -- 成員函式: find_library_file (dirs, lib[, debug=0])

          Search the specified list of directories for a static or
          shared library file `lib' and return the full path to that
          file.  If `debug' is true, look for a debugging version (if
          that makes sense on the current platform).  Return ‘None’ if
          `lib' wasn’t found in any of the specified directories.

      -- 成員函式: has_function (funcname[, includes=None,
               include_dirs=None, libraries=None, library_dirs=None])

          Return a boolean indicating whether `funcname' is supported on
          the current platform.  The optional arguments can be used to
          augment the compilation environment by providing additional
          include files and paths and libraries and paths.

      -- 成員函式: library_dir_option (dir)

          Return the compiler option to add `dir' to the list of
          directories searched for libraries.

      -- 成員函式: library_option (lib)

          Return the compiler option to add `lib' to the list of
          libraries linked into the shared library or executable.

      -- 成員函式: runtime_library_dir_option (dir)

          Return the compiler option to add `dir' to the list of
          directories searched for runtime libraries.

      -- 成員函式: set_executables (**args)

          Define the executables (and options for them) that will be run
          to perform the various stages of compilation.  The exact set
          of executables that may be specified here depends on the
          compiler class (via the ’executables’ class attribute), but
          most will have:

          attribute          description
                             
          ------------------------------------------------------------------
                             
          `compiler'         the C/C++ compiler
                             
                             
          `linker_so'        linker used to create shared objects and
                             libraries
                             
                             
          `linker_exe'       linker used to create binary executables
                             
                             
          `archiver'         static library creator
                             

          On platforms with a command-line (Unix, DOS/Windows), each of
          these is a string that will be split into executable name and
          (optional) list of arguments.  (Splitting the string is done
          similarly to how Unix shells operate: words are delimited by
          spaces, but quotes and backslashes can override this.  See
          *note distutils.util.split_quoted(): 43cc.)

     The following methods invoke stages in the build process.

      -- 成員函式: compile (sources[, output_dir=None, macros=None,
               include_dirs=None, debug=0, extra_preargs=None,
               extra_postargs=None, depends=None])

          Compile one or more source files.  Generates object files
          (e.g.  transforms a ‘.c’ file to a ‘.o’ file.)

          `sources' must be a list of filenames, most likely C/C++
          files, but in reality anything that can be handled by a
          particular compiler and compiler class (eg.  ‘MSVCCompiler’
          can handle resource files in `sources').  Return a list of
          object filenames, one per source filename in `sources'.
          Depending on the implementation, not all source files will
          necessarily be compiled, but all corresponding object
          filenames will be returned.

          If `output_dir' is given, object files will be put under it,
          while retaining their original path component.  That is,
          ‘foo/bar.c’ normally compiles to ‘foo/bar.o’ (for a Unix
          implementation); if `output_dir' is `build', then it would
          compile to ‘build/foo/bar.o’.

          `macros', if given, must be a list of macro definitions.  A
          macro definition is either a ‘(name, value)’ 2-tuple or a
          ‘(name,)’ 1-tuple.  The former defines a macro; if the value
          is ‘None’, the macro is defined without an explicit value.
          The 1-tuple case undefines a macro.  Later
          definitions/redefinitions/undefinitions take precedence.

          `include_dirs', if given, must be a list of strings, the
          directories to add to the default include file search path for
          this compilation only.

          `debug' is a boolean; if true, the compiler will be instructed
          to output debug symbols in (or alongside) the object file(s).

          `extra_preargs' and `extra_postargs' are
          implementation-dependent.  On platforms that have the notion
          of a command-line (e.g.  Unix, DOS/Windows), they are most
          likely lists of strings: extra command-line arguments to
          prepend/append to the compiler command line.  On other
          platforms, consult the implementation class documentation.  In
          any event, they are intended as an escape hatch for those
          occasions when the abstract compiler framework doesn’t cut the
          mustard.

          `depends', if given, is a list of filenames that all targets
          depend on.  If a source file is older than any file in
          depends, then the source file will be recompiled.  This
          supports dependency tracking, but only at a coarse
          granularity.

          Raises ‘CompileError’ on failure.

      -- 成員函式: create_static_lib (objects, output_libname[,
               output_dir=None, debug=0, target_lang=None])

          Link a bunch of stuff together to create a static library
          file.  The "bunch of stuff" consists of the list of object
          files supplied as `objects', the extra object files supplied
          to *note add_link_object(): 43c3. and/or *note
          set_link_objects(): 43c4, the libraries supplied to *note
          add_library(): 43bb. and/or *note set_libraries(): 43bc, and
          the libraries supplied as `libraries' (if any).

          `output_libname' should be a library name, not a filename; the
          filename will be inferred from the library name.  `output_dir'
          is the directory where the library file will be put.

          `debug' is a boolean; if true, debugging information will be
          included in the library (note that on most platforms, it is
          the compile step where this matters: the `debug' flag is
          included here just for consistency).

          `target_lang' is the target language for which the given
          objects are being compiled.  This allows specific linkage time
          treatment of certain languages.

          Raises ‘LibError’ on failure.

      -- 成員函式: link (target_desc, objects, output_filename[,
               output_dir=None, libraries=None, library_dirs=None,
               runtime_library_dirs=None, export_symbols=None, debug=0,
               extra_preargs=None, extra_postargs=None, build_temp=None,
               target_lang=None])

          Link a bunch of stuff together to create an executable or
          shared library file.

          The "bunch of stuff" consists of the list of object files
          supplied as `objects'.  `output_filename' should be a
          filename.  If `output_dir' is supplied, `output_filename' is
          relative to it (i.e.  `output_filename' can provide directory
          components if needed).

          `libraries' is a list of libraries to link against.  These are
          library names, not filenames, since they’re translated into
          filenames in a platform-specific way (eg.  `foo' becomes
          ‘libfoo.a’ on Unix and ‘foo.lib’ on DOS/Windows).  However,
          they can include a directory component, which means the linker
          will look in that specific directory rather than searching all
          the normal locations.

          `library_dirs', if supplied, should be a list of directories
          to search for libraries that were specified as bare library
          names (ie.  no directory component).  These are on top of the
          system default and those supplied to *note add_library_dir():
          43bd. and/or *note set_library_dirs(): 43be.
          `runtime_library_dirs' is a list of directories that will be
          embedded into the shared library and used to search for other
          shared libraries that *it* depends on at run-time.  (This may
          only be relevant on Unix.)

          `export_symbols' is a list of symbols that the shared library
          will export.  (This appears to be relevant only on Windows.)

          `debug' is as for *note compile(): 1b5. and *note
          create_static_lib(): 43ce, with the slight distinction that it
          actually matters on most platforms (as opposed to *note
          create_static_lib(): 43ce, which includes a `debug' flag
          mostly for form’s sake).

          `extra_preargs' and `extra_postargs' are as for *note
          compile(): 1b5. (except of course that they supply
          command-line arguments for the particular linker being used).

          `target_lang' is the target language for which the given
          objects are being compiled.  This allows specific linkage time
          treatment of certain languages.

          Raises ‘LinkError’ on failure.

      -- 成員函式: link_executable (objects, output_progname[,
               output_dir=None, libraries=None, library_dirs=None,
               runtime_library_dirs=None, debug=0, extra_preargs=None,
               extra_postargs=None, target_lang=None])

          Link an executable.  `output_progname' is the name of the file
          executable, while `objects' are a list of object filenames to
          link in.  Other arguments are as for the *note link(): 43cf.
          method.

      -- 成員函式: link_shared_lib (objects, output_libname[,
               output_dir=None, libraries=None, library_dirs=None,
               runtime_library_dirs=None, export_symbols=None, debug=0,
               extra_preargs=None, extra_postargs=None, build_temp=None,
               target_lang=None])

          Link a shared library.  `output_libname' is the name of the
          output library, while `objects' is a list of object filenames
          to link in.  Other arguments are as for the *note link():
          43cf. method.

      -- 成員函式: link_shared_object (objects, output_filename[,
               output_dir=None, libraries=None, library_dirs=None,
               runtime_library_dirs=None, export_symbols=None, debug=0,
               extra_preargs=None, extra_postargs=None, build_temp=None,
               target_lang=None])

          Link a shared object.  `output_filename' is the name of the
          shared object that will be created, while `objects' is a list
          of object filenames to link in.  Other arguments are as for
          the *note link(): 43cf. method.

      -- 成員函式: preprocess (source[, output_file=None, macros=None,
               include_dirs=None, extra_preargs=None,
               extra_postargs=None])

          Preprocess a single C/C++ source file, named in `source'.
          Output will be written to file named `output_file', or
          `stdout' if `output_file' not supplied.  `macros' is a list of
          macro definitions as for *note compile(): 1b5, which will
          augment the macros set with *note define_macro(): 43c1. and
          *note undefine_macro(): 43c2.  `include_dirs' is a list of
          directory names that will be added to the default list, in the
          same way as *note add_include_dir(): 43b9.

          Raises ‘PreprocessError’ on failure.

     The following utility methods are defined by the *note CCompiler:
     43b3. class, for use by the various concrete subclasses.

      -- 成員函式: executable_filename (basename[, strip_dir=0,
               output_dir=''])

          Returns the filename of the executable for the given
          `basename'.  Typically for non-Windows platforms this is the
          same as the basename, while Windows will get a ‘.exe’ added.

      -- 成員函式: library_filename (libname[, lib_type='static',
               strip_dir=0, output_dir=''])

          Returns the filename for the given library name on the current
          platform.  On Unix a library with `lib_type' of ‘'static'’
          will typically be of the form ‘liblibname.a’, while a
          `lib_type' of ‘'dynamic'’ will be of the form ‘liblibname.so’.

      -- 成員函式: object_filenames (source_filenames[, strip_dir=0,
               output_dir=''])

          Returns the name of the object files for the given source
          files.  `source_filenames' should be a list of filenames.

      -- 成員函式: shared_object_filename (basename[, strip_dir=0,
               output_dir=''])

          Returns the name of a shared object file for the given file
          name `basename'.

      -- 成員函式: execute (func, args[, msg=None, level=1])

          Invokes *note distutils.util.execute(): 43d9.  This method
          invokes a Python function `func' with the given arguments
          `args', after logging and taking into account the `dry_run'
          flag.

      -- 成員函式: spawn (cmd)

          Invokes ‘distutils.util.spawn()’.  This invokes an external
          process to run the given command.

      -- 成員函式: mkpath (name[, mode=511])

          Invokes *note distutils.dir_util.mkpath(): 43dc.  This creates
          a directory and any missing ancestor directories.

      -- 成員函式: move_file (src, dst)

          Invokes *note distutils.file_util.move_file(): 43de.  Renames
          `src' to `dst'.

      -- 成員函式: announce (msg[, level=1])

          Write a message using ‘distutils.log.debug()’.

      -- 成員函式: warn (msg)

          Write a warning message `msg' to standard error.

      -- 成員函式: debug_print (msg)

          If the `debug' flag is set on this *note CCompiler: 43b3.
          instance, print `msg' to standard output, otherwise do
          nothing.


File: python.info,  Node: distutils unixccompiler --- Unix C Compiler,  Next: distutils msvccompiler --- Microsoft Compiler,  Prev: distutils ccompiler --- CCompiler base class,  Up: API參照

17.9.3 ‘distutils.unixccompiler’ — Unix C Compiler
--------------------------------------------------

This module provides the ‘UnixCCompiler’ class, a subclass of
‘CCompiler’ that handles the typical Unix-style command-line C compiler:

   * macros defined with ‘-Dname[=value]’

   * macros undefined with ‘-Uname’

   * include search directories specified with ‘-Idir’

   * libraries specified with ‘-llib’

   * library search directories specified with ‘-Ldir’

   * compile handled by ‘cc’ (or similar) executable with ‘-c’ option:
     compiles ‘.c’ to ‘.o’

   * link static library handled by ‘ar’ command (possibly with
     ‘ranlib’)

   * link shared library handled by ‘cc’ ‘-shared’


File: python.info,  Node: distutils msvccompiler --- Microsoft Compiler,  Next: distutils bcppcompiler --- Borland Compiler,  Prev: distutils unixccompiler --- Unix C Compiler,  Up: API參照

17.9.4 ‘distutils.msvccompiler’ — Microsoft Compiler
----------------------------------------------------

This module provides ‘MSVCCompiler’, an implementation of the abstract
‘CCompiler’ class for Microsoft Visual Studio.  Typically, extension
modules need to be compiled with the same compiler that was used to
compile Python.  For Python 2.3 and earlier, the compiler was Visual
Studio 6.  For Python 2.4 and 2.5, the compiler is Visual Studio .NET
2003.

‘MSVCCompiler’ will normally choose the right compiler, linker etc.  on
its own.  To override this choice, the environment variables
`DISTUTILS_USE_SDK' and `MSSdk' must be both set.  `MSSdk' indicates
that the current environment has been setup by the SDK’s ‘SetEnv.Cmd’
script, or that the environment variables had been registered when the
SDK was installed; `DISTUTILS_USE_SDK' indicates that the distutils user
has made an explicit choice to override the compiler selection by
‘MSVCCompiler’.


File: python.info,  Node: distutils bcppcompiler --- Borland Compiler,  Next: distutils cygwincompiler --- Cygwin Compiler,  Prev: distutils msvccompiler --- Microsoft Compiler,  Up: API參照

17.9.5 ‘distutils.bcppcompiler’ — Borland Compiler
--------------------------------------------------

This module provides ‘BorlandCCompiler’, a subclass of the abstract
‘CCompiler’ class for the Borland C++ compiler.


File: python.info,  Node: distutils cygwincompiler --- Cygwin Compiler,  Next: distutils archive_util --- Archiving utilities,  Prev: distutils bcppcompiler --- Borland Compiler,  Up: API參照

17.9.6 ‘distutils.cygwincompiler’ — Cygwin Compiler
---------------------------------------------------

This module provides the ‘CygwinCCompiler’ class, a subclass of
‘UnixCCompiler’ that handles the Cygwin port of the GNU C compiler to
Windows.  It also contains the Mingw32CCompiler class which handles the
mingw32 port of GCC (same as cygwin in no-cygwin mode).


File: python.info,  Node: distutils archive_util --- Archiving utilities,  Next: distutils dep_util --- Dependency checking,  Prev: distutils cygwincompiler --- Cygwin Compiler,  Up: API參照

17.9.7 ‘distutils.archive_util’ — Archiving utilities
-----------------------------------------------------

This module provides a few functions for creating archive files, such as
tarballs or zipfiles.

 -- 函式: distutils.archive_util.make_archive (base_name, format[,
          root_dir=None, base_dir=None, verbose=0, dry_run=0])

     Create an archive file (eg.  ‘zip’ or ‘tar’).  `base_name' is the
     name of the file to create, minus any format-specific extension;
     `format' is the archive format: one of ‘zip’, ‘tar’, ‘gztar’,
     ‘bztar’, ‘xztar’, or ‘ztar’.  `root_dir' is a directory that will
     be the root directory of the archive; ie.  we typically ‘chdir’
     into `root_dir' before creating the archive.  `base_dir' is the
     directory where we start archiving from; ie.  `base_dir' will be
     the common prefix of all files and directories in the archive.
     `root_dir' and `base_dir' both default to the current directory.
     Returns the name of the archive file.

     3.5 版更變: Added support for the ‘xztar’ format.

 -- 函式: distutils.archive_util.make_tarball (base_name, base_dir[,
          compress='gzip', verbose=0, dry_run=0])

     ’Create an (optional compressed) archive as a tar file from all
     files in and under `base_dir'.  `compress' must be ‘'gzip'’ (the
     default), ‘'bzip2'’, ‘'xz'’, ‘'compress'’, or ‘None’.  For the
     ‘'compress'’ method the compression utility named by ‘compress’
     must be on the default program search path, so this is probably
     Unix-specific.  The output tar file will be named ‘base_dir.tar’,
     possibly plus the appropriate compression extension (‘.gz’, ‘.bz2’,
     ‘.xz’ or ‘.Z’).  Return the output filename.

     3.5 版更變: Added support for the ‘xz’ compression.

 -- 函式: distutils.archive_util.make_zipfile (base_name, base_dir[,
          verbose=0, dry_run=0])

     Create a zip file from all files in and under `base_dir'.  The
     output zip file will be named `base_name' + ‘.zip’.  Uses either
     the *note zipfile: 143. Python module (if available) or the InfoZIP
     ‘zip’ utility (if installed and found on the default search path).
     If neither tool is available, raises ‘DistutilsExecError’.  Returns
     the name of the output zip file.


File: python.info,  Node: distutils dep_util --- Dependency checking,  Next: distutils dir_util --- Directory tree operations,  Prev: distutils archive_util --- Archiving utilities,  Up: API參照

17.9.8 ‘distutils.dep_util’ — Dependency checking
-------------------------------------------------

This module provides functions for performing simple, timestamp-based
dependency of files and groups of files; also, functions based entirely
on such timestamp dependency analysis.

 -- 函式: distutils.dep_util.newer (source, target)

     Return true if `source' exists and is more recently modified than
     `target', or if `source' exists and `target' doesn’t.  Return false
     if both exist and `target' is the same age or newer than `source'.
     Raise ‘DistutilsFileError’ if `source' does not exist.

 -- 函式: distutils.dep_util.newer_pairwise (sources, targets)

     Walk two filename lists in parallel, testing if each source is
     newer than its corresponding target.  Return a pair of lists
     (`sources', `targets') where source is newer than target, according
     to the semantics of *note newer(): 43eb.

 -- 函式: distutils.dep_util.newer_group (sources, target[,
          missing='error'])

     Return true if `target' is out-of-date with respect to any file
     listed in `sources'.  In other words, if `target' exists and is
     newer than every file in `sources', return false; otherwise return
     true.  `missing' controls what we do when a source file is missing;
     the default (‘'error'’) is to blow up with an *note OSError: 1d4.
     from inside *note os.stat(): 1f2.; if it is ‘'ignore'’, we silently
     drop any missing source files; if it is ‘'newer'’, any missing
     source files make us assume that `target' is out-of-date (this is
     handy in "dry-run" mode: it’ll make you pretend to carry out
     commands that wouldn’t work because inputs are missing, but that
     doesn’t matter because you’re not actually going to run the
     commands).


File: python.info,  Node: distutils dir_util --- Directory tree operations,  Next: distutils file_util --- Single file operations,  Prev: distutils dep_util --- Dependency checking,  Up: API參照

17.9.9 ‘distutils.dir_util’ — Directory tree operations
-------------------------------------------------------

This module provides functions for operating on directories and trees of
directories.

 -- 函式: distutils.dir_util.mkpath (name[, mode=0o777, verbose=0,
          dry_run=0])

     Create a directory and any missing ancestor directories.  If the
     directory already exists (or if `name' is the empty string, which
     means the current directory, which of course exists), then do
     nothing.  Raise ‘DistutilsFileError’ if unable to create some
     directory along the way (eg.  some sub-path exists, but is a file
     rather than a directory).  If `verbose' is true, print a one-line
     summary of each mkdir to stdout.  Return the list of directories
     actually created.

 -- 函式: distutils.dir_util.create_tree (base_dir, files[, mode=0o777,
          verbose=0, dry_run=0])

     Create all the empty directories under `base_dir' needed to put
     `files' there.  `base_dir' is just the name of a directory which
     doesn’t necessarily exist yet; `files' is a list of filenames to be
     interpreted relative to `base_dir'.  `base_dir' + the directory
     portion of every file in `files' will be created if it doesn’t
     already exist.  `mode', `verbose' and `dry_run' flags are as for
     *note mkpath(): 43dc.

 -- 函式: distutils.dir_util.copy_tree (src, dst[, preserve_mode=1,
          preserve_times=1, preserve_symlinks=0, update=0, verbose=0,
          dry_run=0])

     Copy an entire directory tree `src' to a new location `dst'.  Both
     `src' and `dst' must be directory names.  If `src' is not a
     directory, raise ‘DistutilsFileError’.  If `dst' does not exist, it
     is created with *note mkpath(): 43dc.  The end result of the copy
     is that every file in `src' is copied to `dst', and directories
     under `src' are recursively copied to `dst'.  Return the list of
     files that were copied or might have been copied, using their
     output name.  The return value is unaffected by `update' or
     `dry_run': it is simply the list of all files under `src', with the
     names changed to be under `dst'.

     `preserve_mode' and `preserve_times' are the same as for *note
     distutils.file_util.copy_file(): 43f1.; note that they only apply
     to regular files, not to directories.  If `preserve_symlinks' is
     true, symlinks will be copied as symlinks (on platforms that
     support them!); otherwise (the default), the destination of the
     symlink will be copied.  `update' and `verbose' are the same as for
     ‘copy_file()’.

     Files in `src' that begin with ‘.nfs’ are skipped (more information
     on these files is available in answer D2 of the NFS FAQ page(1)).

     3.3.1 版更變: NFS files are ignored.

 -- 函式: distutils.dir_util.remove_tree (directory[, verbose=0,
          dry_run=0])

     Recursively remove `directory' and all files and directories
     underneath it.  Any errors are ignored (apart from being reported
     to ‘sys.stdout’ if `verbose' is true).

   ---------- Footnotes ----------

   (1) http://nfs.sourceforge.net/#section_d


File: python.info,  Node: distutils file_util --- Single file operations,  Next: distutils util --- Miscellaneous other utility functions,  Prev: distutils dir_util --- Directory tree operations,  Up: API參照

17.9.10 ‘distutils.file_util’ — Single file operations
------------------------------------------------------

This module contains some utility functions for operating on individual
files.

 -- 函式: distutils.file_util.copy_file (src, dst[, preserve_mode=1,
          preserve_times=1, update=0, link=None, verbose=0, dry_run=0])

     Copy file `src' to `dst'.  If `dst' is a directory, then `src' is
     copied there with the same name; otherwise, it must be a filename.
     (If the file exists, it will be ruthlessly clobbered.)  If
     `preserve_mode' is true (the default), the file’s mode (type and
     permission bits, or whatever is analogous on the current platform)
     is copied.  If `preserve_times' is true (the default), the
     last-modified and last-access times are copied as well.  If
     `update' is true, `src' will only be copied if `dst' does not
     exist, or if `dst' does exist but is older than `src'.

     `link' allows you to make hard links (using *note os.link(): a3a.)
     or symbolic links (using *note os.symlink(): a40.) instead of
     copying: set it to ‘'hard'’ or ‘'sym'’; if it is ‘None’ (the
     default), files are copied.  Don’t set `link' on systems that don’t
     support it: *note copy_file(): 43f1. doesn’t check if hard or
     symbolic linking is available.  It uses ‘_copy_file_contents()’ to
     copy file contents.

     Return a tuple ‘(dest_name, copied)’: `dest_name' is the actual
     name of the output file, and `copied' is true if the file was
     copied (or would have been copied, if `dry_run' true).

 -- 函式: distutils.file_util.move_file (src, dst[, verbose, dry_run])

     Move file `src' to `dst'.  If `dst' is a directory, the file will
     be moved into it with the same name; otherwise, `src' is just
     renamed to `dst'.  Returns the new full name of the file.

          警告: Handles cross-device moves on Unix using *note
          copy_file(): 43f1.  What about other systems?

 -- 函式: distutils.file_util.write_file (filename, contents)

     Create a file called `filename' and write `contents' (a sequence of
     strings without line terminators) to it.


File: python.info,  Node: distutils util --- Miscellaneous other utility functions,  Next: distutils dist --- The Distribution class,  Prev: distutils file_util --- Single file operations,  Up: API參照

17.9.11 ‘distutils.util’ — Miscellaneous other utility functions
----------------------------------------------------------------

This module contains other assorted bits and pieces that don’t fit into
any other utility module.

 -- 函式: distutils.util.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
     ’os.uname()’), 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’

     For non-POSIX platforms, currently just returns ‘sys.platform’.

     For Mac OS X systems the OS version reflects the minimal version on
     which binaries will run (that is, the value of
     ‘MACOSX_DEPLOYMENT_TARGET’ during the build of Python), not the OS
     version of the current system.

     For universal binary builds on Mac OS X the architecture value
     reflects the universal binary status instead of the architecture of
     the current processor.  For 32-bit universal binaries the
     architecture is ‘fat’, for 64-bit universal binaries the
     architecture is ‘fat64’, and for 4-way universal binaries the
     architecture is ‘universal’.  Starting from Python 2.7 and Python
     3.2 the architecture ‘fat3’ is used for a 3-way universal build
     (ppc, i386, x86_64) and ‘intel’ is used for a universal build with
     the i386 and x86_64 architectures

     Examples of returned values on Mac OS X:

        * ‘macosx-10.3-ppc’

        * ‘macosx-10.3-fat’

        * ‘macosx-10.5-universal’

        * ‘macosx-10.6-intel’

 -- 函式: distutils.util.convert_path (pathname)

     Return ’pathname’ as a name that will work on the native
     filesystem, i.e.  split it on ’/’ and put it back together again
     using the current directory separator.  Needed because filenames in
     the setup script are always supplied in Unix style, and have to be
     converted to the local convention before we can actually use them
     in the filesystem.  Raises *note ValueError: 1fc. on non-Unix-ish
     systems if `pathname' either starts or ends with a slash.

 -- 函式: distutils.util.change_root (new_root, pathname)

     Return `pathname' with `new_root' prepended.  If `pathname' is
     relative, this is equivalent to ‘os.path.join(new_root,pathname)’
     Otherwise, it requires making `pathname' relative and then joining
     the two, which is tricky on DOS/Windows.

 -- 函式: distutils.util.check_environ ()

     Ensure that ’os.environ’ has all the environment variables we
     guarantee that users can use in config files, command-line options,
     etc.  Currently this includes:

        * ‘HOME’ - user’s home directory (Unix only)

        * ‘PLAT’ - description of the current platform, including
          hardware and OS (see *note get_platform(): 43f6.)

 -- 函式: distutils.util.subst_vars (s, local_vars)

     Perform shell/Perl-style variable substitution on `s'.  Every
     occurrence of ‘$’ followed by a name is considered a variable, and
     variable is substituted by the value found in the `local_vars'
     dictionary, or in ‘os.environ’ if it’s not in `local_vars'.
     `os.environ' is first checked/augmented to guarantee that it
     contains certain values: see *note check_environ(): 43f9.  Raise
     *note ValueError: 1fc. for any variables not found in either
     `local_vars' or ‘os.environ’.

     Note that this is not a fully-fledged string interpolation
     function.  A valid ‘$variable’ can consist only of upper and lower
     case letters, numbers and an underscore.  No { } or ( ) style
     quoting is available.

 -- 函式: distutils.util.split_quoted (s)

     Split a string up according to Unix shell-like rules for quotes and
     backslashes.  In short: words are delimited by spaces, as long as
     those spaces are not escaped by a backslash, or inside a quoted
     string.  Single and double quotes are equivalent, and the quote
     characters can be backslash-escaped.  The backslash is stripped
     from any two-character escape sequence, leaving only the escaped
     character.  The quote characters are stripped from any quoted
     string.  Returns a list of words.

 -- 函式: distutils.util.execute (func, args[, msg=None, verbose=0,
          dry_run=0])

     Perform some action that affects the outside world (for instance,
     writing to the filesystem).  Such actions are special because they
     are disabled by the `dry_run' flag.  This method takes care of all
     that bureaucracy for you; all you have to do is supply the function
     to call and an argument tuple for it (to embody the "external
     action" being performed), and an optional message to print.

 -- 函式: distutils.util.strtobool (val)

     Convert a string representation of truth to true (1) or false (0).

     True values are ‘y’, ‘yes’, ‘t’, ‘true’, ‘on’ and ‘1’; false values
     are ‘n’, ‘no’, ‘f’, ‘false’, ‘off’ and ‘0’.  Raises *note
     ValueError: 1fc. if `val' is anything else.

 -- 函式: distutils.util.byte_compile (py_files[, optimize=0, force=0,
          prefix=None, base_dir=None, verbose=1, dry_run=0,
          direct=None])

     Byte-compile a collection of Python source files to ‘.pyc’ files in
     a ‘__pycache__’ subdirectory (see PEP 3147(1) and PEP 488(2)).
     `py_files' is a list of files to compile; any files that don’t end
     in ‘.py’ are silently skipped.  `optimize' must be one of the
     following:

        * ‘0’ - don’t optimize

        * ‘1’ - normal optimization (like ‘python -O’)

        * ‘2’ - extra optimization (like ‘python -OO’)

     If `force' is true, all files are recompiled regardless of
     timestamps.

     The source filename encoded in each *note bytecode: 619. file
     defaults to the filenames listed in `py_files'; you can modify
     these with `prefix' and `basedir'.  `prefix' is a string that will
     be stripped off of each source filename, and `base_dir' is a
     directory name that will be prepended (after `prefix' is stripped).
     You can supply either or both (or neither) of `prefix' and
     `base_dir', as you wish.

     If `dry_run' is true, doesn’t actually do anything that would
     affect the filesystem.

     Byte-compilation is either done directly in this interpreter
     process with the standard *note py_compile: d8. module, or
     indirectly by writing a temporary script and executing it.
     Normally, you should let *note byte_compile(): 43fc. figure out to
     use direct compilation or not (see the source for details).  The
     `direct' flag is used by the script generated in indirect mode;
     unless you know what you’re doing, leave it set to ‘None’.

     3.2.3 版更變: Create ‘.pyc’ files with an *note import magic tag:
     3ade. in their name, in a ‘__pycache__’ subdirectory instead of
     files without tag in the current directory.

     3.5 版更變: Create ‘.pyc’ files according to PEP 488(3).

 -- 函式: distutils.util.rfc822_escape (header)

     Return a version of `header' escaped for inclusion in an RFC 822(4)
     header, by ensuring there are 8 spaces space after each newline.
     Note that it does no other modification of the string.

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-3147

   (2) https://www.python.org/dev/peps/pep-0488

   (3) https://www.python.org/dev/peps/pep-0488

   (4) https://tools.ietf.org/html/rfc822.html


File: python.info,  Node: distutils dist --- The Distribution class,  Next: distutils extension --- The Extension class,  Prev: distutils util --- Miscellaneous other utility functions,  Up: API參照

17.9.12 ‘distutils.dist’ — The Distribution class
-------------------------------------------------

This module provides the *note Distribution: 43af. class, which
represents the module distribution being built/installed/distributed.


File: python.info,  Node: distutils extension --- The Extension class,  Next: distutils debug --- Distutils debug mode,  Prev: distutils dist --- The Distribution class,  Up: API參照

17.9.13 ‘distutils.extension’ — The Extension class
---------------------------------------------------

This module provides the ‘Extension’ class, used to describe C/C++
extension modules in setup scripts.


File: python.info,  Node: distutils debug --- Distutils debug mode,  Next: distutils errors --- Distutils exceptions,  Prev: distutils extension --- The Extension class,  Up: API參照

17.9.14 ‘distutils.debug’ — Distutils debug mode
------------------------------------------------

This module provides the DEBUG flag.


File: python.info,  Node: distutils errors --- Distutils exceptions,  Next: distutils fancy_getopt --- Wrapper around the standard getopt module,  Prev: distutils debug --- Distutils debug mode,  Up: API參照

17.9.15 ‘distutils.errors’ — Distutils exceptions
-------------------------------------------------

Provides exceptions used by the Distutils modules.  Note that Distutils
modules may raise standard exceptions; in particular, SystemExit is
usually raised for errors that are obviously the end-user’s fault (eg.
bad command-line arguments).

This module is safe to use in ‘from ... import *’ mode; it only exports
symbols whose names start with ‘Distutils’ and end with ‘Error’.


File: python.info,  Node: distutils fancy_getopt --- Wrapper around the standard getopt module,  Next: distutils filelist --- The FileList class,  Prev: distutils errors --- Distutils exceptions,  Up: API參照

17.9.16 ‘distutils.fancy_getopt’ — Wrapper around the standard getopt module
----------------------------------------------------------------------------

This module provides a wrapper around the standard *note getopt: 87.
module that provides the following additional features:

   * short and long options are tied together

   * options have help strings, so *note fancy_getopt(): 4403. could
     potentially create a complete usage summary

   * options set attributes of a passed-in object

   * boolean options can have "negative aliases" — eg.  if ‘--quiet’ is
     the "negative alias" of ‘--verbose’, then ‘--quiet’ on the command
     line sets `verbose' to false.

 -- 函式: distutils.fancy_getopt.fancy_getopt (options, negative_opt,
          object, args)

     Wrapper function.  `options' is a list of ‘(long_option,
     short_option, help_string)’ 3-tuples as described in the
     constructor for *note FancyGetopt: 4404.  `negative_opt' should be
     a dictionary mapping option names to option names, both the key and
     value should be in the `options' list.  `object' is an object which
     will be used to store values (see the *note getopt(): 87. method of
     the *note FancyGetopt: 4404. class).  `args' is the argument list.
     Will use ‘sys.argv[1:]’ if you pass ‘None’ as `args'.

 -- 函式: distutils.fancy_getopt.wrap_text (text, width)

     Wraps `text' to less than `width' wide.

 -- 類別: distutils.fancy_getopt.FancyGetopt ([option_table=None])

     The option_table is a list of 3-tuples: ‘(long_option,
     short_option, help_string)’

     If an option takes an argument, its `long_option' should have ‘'='’
     appended; `short_option' should just be a single character, no
     ‘':'’ in any case.  `short_option' should be ‘None’ if a
     `long_option' doesn’t have a corresponding `short_option'.  All
     option tuples must have long options.

The *note FancyGetopt: 4404. class provides the following methods:

 -- 成員函式: FancyGetopt.getopt ([args=None, object=None])

     Parse command-line options in args.  Store as attributes on
     `object'.

     If `args' is ‘None’ or not supplied, uses ‘sys.argv[1:]’.  If
     `object' is ‘None’ or not supplied, creates a new ‘OptionDummy’
     instance, stores option values there, and returns a tuple ‘(args,
     object)’.  If `object' is supplied, it is modified in place and
     *note getopt(): 87. just returns `args'; in both cases, the
     returned `args' is a modified copy of the passed-in `args' list,
     which is left untouched.

 -- 成員函式: FancyGetopt.get_option_order ()

     Returns the list of ‘(option, value)’ tuples processed by the
     previous run of *note getopt(): 87. Raises *note RuntimeError: 2bb.
     if *note getopt(): 87. hasn’t been called yet.

 -- 成員函式: FancyGetopt.generate_help ([header=None])

     Generate help text (a list of strings, one per suggested line of
     output) from the option table for this *note FancyGetopt: 4404.
     object.

     If supplied, prints the supplied `header' at the top of the help.


File: python.info,  Node: distutils filelist --- The FileList class,  Next: distutils log --- Simple PEP 282-style logging,  Prev: distutils fancy_getopt --- Wrapper around the standard getopt module,  Up: API參照

17.9.17 ‘distutils.filelist’ — The FileList class
-------------------------------------------------

This module provides the ‘FileList’ class, used for poking about the
filesystem and building lists of files.


File: python.info,  Node: distutils log --- Simple PEP 282-style logging,  Next: distutils spawn --- Spawn a sub-process,  Prev: distutils filelist --- The FileList class,  Up: API參照

17.9.18 ‘distutils.log’ — Simple `PEP 282'-style logging
--------------------------------------------------------


File: python.info,  Node: distutils spawn --- Spawn a sub-process,  Next: distutils sysconfig --- System configuration information,  Prev: distutils log --- Simple PEP 282-style logging,  Up: API參照

17.9.19 ‘distutils.spawn’ — Spawn a sub-process
-----------------------------------------------

This module provides the ‘spawn()’ function, a front-end to various
platform-specific functions for launching another program in a
sub-process.  Also provides ‘find_executable()’ to search the path for a
given executable name.


File: python.info,  Node: distutils sysconfig --- System configuration information,  Next: distutils text_file --- The TextFile class,  Prev: distutils spawn --- Spawn a sub-process,  Up: API參照

17.9.20 ‘distutils.sysconfig’ — System configuration information
----------------------------------------------------------------

The *note distutils.sysconfig: 62. module provides access to Python’s
low-level configuration information.  The specific configuration
variables available depend heavily on the platform and configuration.
The specific variables depend on the build process for the specific
version of Python being run; the variables are those found in the
‘Makefile’ and configuration header that are installed with Python on
Unix systems.  The configuration header is called ‘pyconfig.h’ for
Python versions starting with 2.2, and ‘config.h’ for earlier versions
of Python.

Some additional functions are provided which perform some useful
manipulations for other parts of the *note distutils: 39. package.

 -- Data: distutils.sysconfig.PREFIX

     The result of ‘os.path.normpath(sys.prefix)’.

 -- Data: distutils.sysconfig.EXEC_PREFIX

     The result of ‘os.path.normpath(sys.exec_prefix)’.

 -- 函式: distutils.sysconfig.get_config_var (name)

     Return the value of a single variable.  This is equivalent to
     ‘get_config_vars().get(name)’.

 -- 函式: distutils.sysconfig.get_config_vars (...)

     Return a set of variable definitions.  If there are no arguments,
     this returns a dictionary mapping names of configuration variables
     to values.  If arguments are provided, they should be strings, and
     the return value will be a sequence giving the associated values.
     If a given name does not have a corresponding value, ‘None’ will be
     included for that variable.

 -- 函式: distutils.sysconfig.get_config_h_filename ()

     Return the full path name of the configuration header.  For Unix,
     this will be the header generated by the ‘configure’ script; for
     other platforms the header will have been supplied directly by the
     Python source distribution.  The file is a platform-specific text
     file.

 -- 函式: distutils.sysconfig.get_makefile_filename ()

     Return the full path name of the ‘Makefile’ used to build Python.
     For Unix, this will be a file generated by the ‘configure’ script;
     the meaning for other platforms will vary.  The file is a
     platform-specific text file, if it exists.  This function is only
     useful on POSIX platforms.

 -- 函式: distutils.sysconfig.get_python_inc ([plat_specific[, prefix]])

     Return the directory for either the general or platform-dependent C
     include files.  If `plat_specific' is true, the platform-dependent
     include directory is returned; if false or omitted, the
     platform-independent directory is returned.  If `prefix' is given,
     it is used as either the prefix instead of *note PREFIX: 440d, or
     as the exec-prefix instead of *note EXEC_PREFIX: 440e. if
     `plat_specific' is true.

 -- 函式: distutils.sysconfig.get_python_lib ([plat_specific[,
          standard_lib[, prefix]]])

     Return the directory for either the general or platform-dependent
     library installation.  If `plat_specific' is true, the
     platform-dependent include directory is returned; if false or
     omitted, the platform-independent directory is returned.  If
     `prefix' is given, it is used as either the prefix instead of *note
     PREFIX: 440d, or as the exec-prefix instead of *note EXEC_PREFIX:
     440e. if `plat_specific' is true.  If `standard_lib' is true, the
     directory for the standard library is returned rather than the
     directory for the installation of third-party extensions.

The following function is only intended for use within the *note
distutils: 39. package.

 -- 函式: distutils.sysconfig.customize_compiler (compiler)

     Do any platform-specific customization of a *note
     distutils.ccompiler.CCompiler: 43b3. instance.

     This function is only needed on Unix at this time, but should be
     called consistently to support forward-compatibility.  It inserts
     the information that varies across Unix flavors and is stored in
     Python’s ‘Makefile’.  This information includes the selected
     compiler, compiler and linker options, and the extension used by
     the linker for shared objects.

This function is even more special-purpose, and should only be used from
Python’s own build procedures.

 -- 函式: distutils.sysconfig.set_python_build ()

     Inform the *note distutils.sysconfig: 62. module that it is being
     used as part of the build process for Python.  This changes a lot
     of relative locations for files, allowing them to be located in the
     build area rather than in an installed Python.


File: python.info,  Node: distutils text_file --- The TextFile class,  Next: distutils version --- Version number classes,  Prev: distutils sysconfig --- System configuration information,  Up: API參照

17.9.21 ‘distutils.text_file’ — The TextFile class
--------------------------------------------------

This module provides the *note TextFile: 4418. class, which gives an
interface to text files that (optionally) takes care of stripping
comments, ignoring blank lines, and joining lines with backslashes.

 -- 類別: distutils.text_file.TextFile ([filename=None, file=None,
          **options])

     This class provides a file-like object that takes care of all the
     things you commonly want to do when processing a text file that has
     some line-by-line syntax: strip comments (as long as ‘#’ is your
     comment character), skip blank lines, join adjacent lines by
     escaping the newline (ie.  backslash at end of line), strip leading
     and/or trailing whitespace.  All of these are optional and
     independently controllable.

     The class provides a *note warn(): 4419. method so you can generate
     warning messages that report physical line number, even if the
     logical line in question spans multiple physical lines.  Also
     provides *note unreadline(): 441a. for implementing line-at-a-time
     lookahead.

     *note TextFile: 4418. instances are create with either `filename',
     `file', or both.  *note RuntimeError: 2bb. is raised if both are
     ‘None’.  `filename' should be a string, and `file' a file object
     (or something that provides *note readline(): df. and *note
     close(): 441b. methods).  It is recommended that you supply at
     least `filename', so that *note TextFile: 4418. can include it in
     warning messages.  If `file' is not supplied, *note TextFile: 4418.
     creates its own using the *note open(): 4f5. built-in function.

     The options are all boolean, and affect the values returned by
     *note readline(): df.

     option name            description                          default
                                                                 
     --------------------------------------------------------------------------
                                                                 
     `strip_comments'       strip from ‘'#'’ to end-of-line,     true
                            as well as any whitespace leading    
                            up to the ‘'#'’—unless it is
                            escaped by a backslash
                            
                                                                 
     `lstrip_ws'            strip leading whitespace from each   false
                            line before returning it             
                            
                                                                 
     `rstrip_ws'            strip trailing whitespace            true
                            (including line terminator!)  from   
                            each line before returning it.
                            
                                                                 
     `skip_blanks'          skip lines that are empty *after*    true
                            stripping comments and whitespace.   
                            (If both lstrip_ws and rstrip_ws
                            are false, then some lines may
                            consist of solely whitespace:
                            these will *not* be skipped, even
                            if `skip_blanks' is true.)
                            
                                                                 
     `join_lines'           if a backslash is the last           false
                            non-newline character on a line      
                            after stripping comments and
                            whitespace, join the following
                            line to it to form one logical
                            line; if N consecutive lines end
                            with a backslash, then N+1
                            physical lines will be joined to
                            form one logical line.
                            
                                                                 
     `collapse_join'        strip leading whitespace from        false
                            lines that are joined to their       
                            predecessor; only matters if
                            ‘(join_lines and not lstrip_ws)’
                            

     Note that since `rstrip_ws' can strip the trailing newline, the
     semantics of *note readline(): df. must differ from those of the
     built-in file object’s *note readline(): df. method!  In
     particular, *note readline(): df. returns ‘None’ for end-of-file:
     an empty string might just be a blank line (or an all-whitespace
     line), if `rstrip_ws' is true but `skip_blanks' is not.

      -- 成員函式: open (filename)

          Open a new file `filename'.  This overrides any `file' or
          `filename' constructor arguments.

      -- 成員函式: close ()

          Close the current file and forget everything we know about it
          (including the filename and the current line number).

      -- 成員函式: warn (msg[, line=None])

          Print (to stderr) a warning message tied to the current
          logical line in the current file.  If the current logical line
          in the file spans multiple physical lines, the warning refers
          to the whole range, such as ‘"lines 3-5"’.  If `line' is
          supplied, it overrides the current line number; it may be a
          list or tuple to indicate a range of physical lines, or an
          integer for a single physical line.

      -- 成員函式: readline ()

          Read and return a single logical line from the current file
          (or from an internal buffer if lines have previously been
          "unread" with *note unreadline(): 441a.).  If the `join_lines'
          option is true, this may involve reading multiple physical
          lines concatenated into a single string.  Updates the current
          line number, so calling *note warn(): 4419. after *note
          readline(): df. emits a warning about the physical line(s)
          just read.  Returns ‘None’ on end-of-file, since the empty
          string can occur if `rstrip_ws' is true but `strip_blanks' is
          not.

      -- 成員函式: readlines ()

          Read and return the list of all logical lines remaining in the
          current file.  This updates the current line number to the
          last line of the file.

      -- 成員函式: unreadline (line)

          Push `line' (a string) onto an internal buffer that will be
          checked by future *note readline(): df. calls.  Handy for
          implementing a parser with line-at-a-time lookahead.  Note
          that lines that are "unread" with *note unreadline(): 441a.
          are not subsequently re-cleansed (whitespace stripped, or
          whatever) when read with *note readline(): df.  If multiple
          calls are made to *note unreadline(): 441a. before a call to
          *note readline(): df, the lines will be returned most in most
          recent first order.


File: python.info,  Node: distutils version --- Version number classes,  Next: distutils cmd --- Abstract base class for Distutils commands,  Prev: distutils text_file --- The TextFile class,  Up: API參照

17.9.22 ‘distutils.version’ — Version number classes
----------------------------------------------------


File: python.info,  Node: distutils cmd --- Abstract base class for Distutils commands,  Next: Creating a new Distutils command,  Prev: distutils version --- Version number classes,  Up: API參照

17.9.23 ‘distutils.cmd’ — Abstract base class for Distutils commands
--------------------------------------------------------------------

This module supplies the abstract base class *note Command: 439e.

 -- 類別: distutils.cmd.Command (dist)

     Abstract base class for defining command classes, the "worker bees"
     of the Distutils.  A useful analogy for command classes is to think
     of them as subroutines with local variables called `options'.  The
     options are declared in *note initialize_options(): 4421. and
     defined (given their final values) in *note finalize_options():
     4422, both of which must be defined by every command class.  The
     distinction between the two is necessary because option values
     might come from the outside world (command line, config file, ...),
     and any options dependent on other options must be computed after
     these outside influences have been processed — hence *note
     finalize_options(): 4422.  The body of the subroutine, where it
     does all its work based on the values of its options, is the *note
     run(): 4423. method, which must also be implemented by every
     command class.

     The class constructor takes a single argument `dist', a *note
     Distribution: 43af. instance.


File: python.info,  Node: Creating a new Distutils command,  Next: distutils command --- Individual Distutils commands,  Prev: distutils cmd --- Abstract base class for Distutils commands,  Up: API參照

17.9.24 Creating a new Distutils command
----------------------------------------

This section outlines the steps to create a new Distutils command.

A new command lives in a module in the *note distutils.command: 3e.
package.  There is a sample template in that directory called
‘command_template’.  Copy this file to a new module with the same name
as the new command you’re implementing.  This module should implement a
class with the same name as the module (and the command).  So, for
instance, to create the command ‘peel_banana’ (so that users can run
‘setup.py peel_banana’), you’d copy ‘command_template’ to
‘distutils/command/peel_banana.py’, then edit it so that it’s
implementing the class ‘peel_banana’, a subclass of *note
distutils.cmd.Command: 439e.

Subclasses of *note Command: 439e. must define the following methods.

 -- 成員函式: Command.initialize_options ()

     Set default values for all the options that this command supports.
     Note that these defaults may be overridden by other commands, by
     the setup script, by config files, or by the command-line.  Thus,
     this is not the place to code dependencies between options;
     generally, *note initialize_options(): 4421. implementations are
     just a bunch of ‘self.foo = None’ assignments.

 -- 成員函式: Command.finalize_options ()

     Set final values for all the options that this command supports.
     This is always called as late as possible, ie.  after any option
     assignments from the command-line or from other commands have been
     done.  Thus, this is the place to code option dependencies: if
     `foo' depends on `bar', then it is safe to set `foo' from `bar' as
     long as `foo' still has the same value it was assigned in *note
     initialize_options(): 4421.

 -- 成員函式: Command.run ()

     A command’s raison d’etre: carry out the action it exists to
     perform, controlled by the options initialized in *note
     initialize_options(): 4421, customized by other commands, the setup
     script, the command-line, and config files, and finalized in *note
     finalize_options(): 4422.  All terminal output and filesystem
     interaction should be done by *note run(): 4423.

 -- 屬性: Command.sub_commands

     `sub_commands' formalizes the notion of a "family" of commands,
     e.g.  ‘install’ as the parent with sub-commands ‘install_lib’,
     ‘install_headers’, etc.  The parent of a family of commands defines
     `sub_commands' as a class attribute; it’s a list of 2-tuples
     ‘(command_name, predicate)’, with `command_name' a string and
     `predicate' a function, a string or ‘None’.  `predicate' is a
     method of the parent command that determines whether the
     corresponding command is applicable in the current situation.
     (E.g.  ‘install_headers’ is only applicable if we have any C header
     files to install.)  If `predicate' is ‘None’, that command is
     always applicable.

     `sub_commands' is usually defined at the `end' of a class, because
     predicates can be methods of the class, so they must already have
     been defined.  The canonical example is the ‘install’ command.


File: python.info,  Node: distutils command --- Individual Distutils commands,  Next: distutils command bdist --- Build a binary installer,  Prev: Creating a new Distutils command,  Up: API參照

17.9.25 ‘distutils.command’ — Individual Distutils commands
-----------------------------------------------------------


File: python.info,  Node: distutils command bdist --- Build a binary installer,  Next: distutils command bdist_packager --- Abstract base class for packagers,  Prev: distutils command --- Individual Distutils commands,  Up: API參照

17.9.26 ‘distutils.command.bdist’ — Build a binary installer
------------------------------------------------------------


File: python.info,  Node: distutils command bdist_packager --- Abstract base class for packagers,  Next: distutils command bdist_dumb --- Build a "dumb" installer,  Prev: distutils command bdist --- Build a binary installer,  Up: API參照

17.9.27 ‘distutils.command.bdist_packager’ — Abstract base class for packagers
------------------------------------------------------------------------------


File: python.info,  Node: distutils command bdist_dumb --- Build a "dumb" installer,  Next: distutils command bdist_msi --- Build a Microsoft Installer binary package,  Prev: distutils command bdist_packager --- Abstract base class for packagers,  Up: API參照

17.9.28 ‘distutils.command.bdist_dumb’ — Build a "dumb" installer
-----------------------------------------------------------------


File: python.info,  Node: distutils command bdist_msi --- Build a Microsoft Installer binary package,  Next: distutils command bdist_rpm --- Build a binary distribution as a Redhat RPM and SRPM,  Prev: distutils command bdist_dumb --- Build a "dumb" installer,  Up: API參照

17.9.29 ‘distutils.command.bdist_msi’ — Build a Microsoft Installer binary package
----------------------------------------------------------------------------------

 -- 類別: distutils.command.bdist_msi.bdist_msi

     Builds a Windows Installer(1) (.msi) binary package.

     In most cases, the ‘bdist_msi’ installer is a better choice than
     the ‘bdist_wininst’ installer, because it provides better support
     for Win64 platforms, allows administrators to perform
     non-interactive installations, and allows installation through
     group policies.

   ---------- Footnotes ----------

   (1) https://msdn.microsoft.com/en-us/library/cc185688(VS.85).aspx


File: python.info,  Node: distutils command bdist_rpm --- Build a binary distribution as a Redhat RPM and SRPM,  Next: distutils command bdist_wininst --- Build a Windows installer,  Prev: distutils command bdist_msi --- Build a Microsoft Installer binary package,  Up: API參照

17.9.30 ‘distutils.command.bdist_rpm’ — Build a binary distribution as a Redhat RPM and SRPM
--------------------------------------------------------------------------------------------


File: python.info,  Node: distutils command bdist_wininst --- Build a Windows installer,  Next: distutils command sdist --- Build a source distribution,  Prev: distutils command bdist_rpm --- Build a binary distribution as a Redhat RPM and SRPM,  Up: API參照

17.9.31 ‘distutils.command.bdist_wininst’ — Build a Windows installer
---------------------------------------------------------------------

3.8 版後已棄用: Use bdist_wheel (wheel packages) instead.


File: python.info,  Node: distutils command sdist --- Build a source distribution,  Next: distutils command build --- Build all files of a package,  Prev: distutils command bdist_wininst --- Build a Windows installer,  Up: API參照

17.9.32 ‘distutils.command.sdist’ — Build a source distribution
---------------------------------------------------------------


File: python.info,  Node: distutils command build --- Build all files of a package,  Next: distutils command build_clib --- Build any C libraries in a package,  Prev: distutils command sdist --- Build a source distribution,  Up: API參照

17.9.33 ‘distutils.command.build’ — Build all files of a package
----------------------------------------------------------------


File: python.info,  Node: distutils command build_clib --- Build any C libraries in a package,  Next: distutils command build_ext --- Build any extensions in a package,  Prev: distutils command build --- Build all files of a package,  Up: API參照

17.9.34 ‘distutils.command.build_clib’ — Build any C libraries in a package
---------------------------------------------------------------------------


File: python.info,  Node: distutils command build_ext --- Build any extensions in a package,  Next: distutils command build_py --- Build the py/ pyc files of a package,  Prev: distutils command build_clib --- Build any C libraries in a package,  Up: API參照

17.9.35 ‘distutils.command.build_ext’ — Build any extensions in a package
-------------------------------------------------------------------------


File: python.info,  Node: distutils command build_py --- Build the py/ pyc files of a package,  Next: distutils command build_scripts --- Build the scripts of a package,  Prev: distutils command build_ext --- Build any extensions in a package,  Up: API參照

17.9.36 ‘distutils.command.build_py’ — Build the .py/.pyc files of a package
----------------------------------------------------------------------------

 -- 類別: distutils.command.build_py.build_py

 -- 類別: distutils.command.build_py.build_py_2to3

     Alternative implementation of build_py which also runs the 2to3
     conversion library on each .py file that is going to be installed.
     To use this in a setup.py file for a distribution that is designed
     to run with both Python 2.x and 3.x, add:

          try:
              from distutils.command.build_py import build_py_2to3 as build_py
          except ImportError:
              from distutils.command.build_py import build_py

     to your setup.py, and later:

          cmdclass = {'build_py': build_py}

     to the invocation of setup().


File: python.info,  Node: distutils command build_scripts --- Build the scripts of a package,  Next: distutils command clean --- Clean a package build area,  Prev: distutils command build_py --- Build the py/ pyc files of a package,  Up: API參照

17.9.37 ‘distutils.command.build_scripts’ — Build the scripts of a package
--------------------------------------------------------------------------


File: python.info,  Node: distutils command clean --- Clean a package build area,  Next: distutils command config --- Perform package configuration,  Prev: distutils command build_scripts --- Build the scripts of a package,  Up: API參照

17.9.38 ‘distutils.command.clean’ — Clean a package build area
--------------------------------------------------------------

This command removes the temporary files created by ‘build’ and its
subcommands, like intermediary compiled object files.  With the ‘--all’
option, the complete build directory will be removed.

Extension modules built *note in place: 4377. will not be cleaned, as
they are not in the build directory.


File: python.info,  Node: distutils command config --- Perform package configuration,  Next: distutils command install --- Install a package,  Prev: distutils command clean --- Clean a package build area,  Up: API參照

17.9.39 ‘distutils.command.config’ — Perform package configuration
------------------------------------------------------------------


File: python.info,  Node: distutils command install --- Install a package,  Next: distutils command install_data --- Install data files from a package,  Prev: distutils command config --- Perform package configuration,  Up: API參照

17.9.40 ‘distutils.command.install’ — Install a package
-------------------------------------------------------


File: python.info,  Node: distutils command install_data --- Install data files from a package,  Next: distutils command install_headers --- Install C/C++ header files from a package,  Prev: distutils command install --- Install a package,  Up: API參照

17.9.41 ‘distutils.command.install_data’ — Install data files from a package
----------------------------------------------------------------------------


File: python.info,  Node: distutils command install_headers --- Install C/C++ header files from a package,  Next: distutils command install_lib --- Install library files from a package,  Prev: distutils command install_data --- Install data files from a package,  Up: API參照

17.9.42 ‘distutils.command.install_headers’ — Install C/C++ header files from a package
---------------------------------------------------------------------------------------


File: python.info,  Node: distutils command install_lib --- Install library files from a package,  Next: distutils command install_scripts --- Install script files from a package,  Prev: distutils command install_headers --- Install C/C++ header files from a package,  Up: API參照

17.9.43 ‘distutils.command.install_lib’ — Install library files from a package
------------------------------------------------------------------------------


File: python.info,  Node: distutils command install_scripts --- Install script files from a package,  Next: distutils command register --- Register a module with the Python Package Index,  Prev: distutils command install_lib --- Install library files from a package,  Up: API參照

17.9.44 ‘distutils.command.install_scripts’ — Install script files from a package
---------------------------------------------------------------------------------


File: python.info,  Node: distutils command register --- Register a module with the Python Package Index,  Next: distutils command check --- Check the meta-data of a package,  Prev: distutils command install_scripts --- Install script files from a package,  Up: API參照

17.9.45 ‘distutils.command.register’ — Register a module with the Python Package Index
--------------------------------------------------------------------------------------

The ‘register’ command registers the package with the Python Package
Index.  This is described in more detail in PEP 301(1).

   ---------- Footnotes ----------

   (1) https://www.python.org/dev/peps/pep-0301


File: python.info,  Node: distutils command check --- Check the meta-data of a package,  Prev: distutils command register --- Register a module with the Python Package Index,  Up: API參照

17.9.46 ‘distutils.command.check’ — Check the meta-data of a package
--------------------------------------------------------------------

The ‘check’ command performs some tests on the meta-data of a package.
For example, it verifies that all required meta-data are provided as the
arguments passed to the ‘setup()’ function.


File: python.info,  Node: 安裝 Python 模組（舊版）,  Next: Python 模組索引,  Prev: 發布 Python 模組（舊版）,  Up: Top

18 安裝 Python 模組（舊版）
***************************


Author: Greg Ward

也參考
......

*note 安裝 Python 模組: 7fa.

     The up to date module installation documentation.  For regular
     Python usage, you almost certainly want that document rather than
     this one.

     備註: This document is being retained solely until the ‘setuptools’
     documentation at
     ‘https://setuptools.readthedocs.io/en/latest/setuptools.html’
     independently covers all of the relevant information currently
     included here.

     備註: This guide only covers the basic tools for building and
     distributing extensions that are provided as part of this version
     of Python.  Third party tools offer easier to use and more secure
     alternatives.  Refer to the quick recommendations section(1) in the
     Python Packaging User Guide for more information.

* Menu:

* 簡介: 簡介<16>.
* Standard Build and Install::
* Alternate Installation::
* Custom Installation::
* Distutils Configuration Files::
* Building Extensions; Tips and Tricks: Building Extensions Tips and Tricks.

   ---------- Footnotes ----------

   (1) https://packaging.python.org/guides/tool-recommendations/


File: python.info,  Node: 簡介<16>,  Next: Standard Build and Install,  Up: 安裝 Python 模組（舊版）

18.1 簡介
=========

In Python 2.0, the ‘distutils’ API was first added to the standard
library.  This provided Linux distro maintainers with a standard way of
converting Python projects into Linux distro packages, and system
administrators with a standard way of installing them directly onto
target systems.

In the many years since Python 2.0 was released, tightly coupling the
build system and package installer to the language runtime release cycle
has turned out to be problematic, and it is now recommended that
projects use the ‘pip’ package installer and the ‘setuptools’ build
system, rather than using ‘distutils’ directly.

See *note 安裝 Python 模組: 7fa. and *note 發布 Python 模組: 7fb. for
more details.

This legacy documentation is being retained only until we’re confident
that the ‘setuptools’ documentation covers everything needed.

* Menu:

* Distutils based source distributions::


File: python.info,  Node: Distutils based source distributions,  Up: 簡介<16>

18.1.1 Distutils based source distributions
-------------------------------------------

If you download a module source distribution, you can tell pretty
quickly if it was packaged and distributed in the standard way, i.e.
using the Distutils.  First, the distribution’s name and version number
will be featured prominently in the name of the downloaded archive, e.g.
‘foo-1.0.tar.gz’ or ‘widget-0.9.7.zip’.  Next, the archive will unpack
into a similarly-named directory: ‘foo-1.0’ or ‘widget-0.9.7’.
Additionally, the distribution will contain a setup script ‘setup.py’,
and a file named ‘README.txt’ or possibly just ‘README’, which should
explain that building and installing the module distribution is a simple
matter of running one command from a terminal:

     python setup.py install

For Windows, this command should be run from a command prompt window
(Start ‣ Accessories):

     setup.py install

If all these things are true, then you already know how to build and
install the modules you’ve just downloaded: Run the command above.
Unless you need to install things in a non-standard way or customize the
build process, you don’t really need this manual.  Or rather, the above
command is everything you need to get out of this manual.


File: python.info,  Node: Standard Build and Install,  Next: Alternate Installation,  Prev: 簡介<16>,  Up: 安裝 Python 模組（舊版）

18.2 Standard Build and Install
===============================

As described in section *note Distutils based source distributions:
4444, building and installing a module distribution using the Distutils
is usually one simple command to run from a terminal:

     python setup.py install

* Menu:

* Platform variations::
* Splitting the job up::
* How building works::
* How installation works::


File: python.info,  Node: Platform variations,  Next: Splitting the job up,  Up: Standard Build and Install

18.2.1 Platform variations
--------------------------

You should always run the setup command from the distribution root
directory, i.e.  the top-level subdirectory that the module source
distribution unpacks into.  For example, if you’ve just downloaded a
module source distribution ‘foo-1.0.tar.gz’ onto a Unix system, the
normal thing to do is:

     gunzip -c foo-1.0.tar.gz | tar xf -    # unpacks into directory foo-1.0
     cd foo-1.0
     python setup.py install

On Windows, you’d probably download ‘foo-1.0.zip’.  If you downloaded
the archive file to ‘C:\Temp’, then it would unpack into
‘C:\Temp\foo-1.0’; you can use either an archive manipulator with a
graphical user interface (such as WinZip) or a command-line tool (such
as ‘unzip’ or ‘pkunzip’) to unpack the archive.  Then, open a command
prompt window and run:

     cd c:\Temp\foo-1.0
     python setup.py install


File: python.info,  Node: Splitting the job up,  Next: How building works,  Prev: Platform variations,  Up: Standard Build and Install

18.2.2 Splitting the job up
---------------------------

Running ‘setup.py install’ builds and installs all modules in one run.
If you prefer to work incrementally—especially useful if you want to
customize the build process, or if things are going wrong—you can use
the setup script to do one thing at a time.  This is particularly
helpful when the build and install will be done by different users—for
example, you might want to build a module distribution and hand it off
to a system administrator for installation (or do it yourself, with
super-user privileges).

For example, you can build everything in one step, and then install
everything in a second step, by invoking the setup script twice:

     python setup.py build
     python setup.py install

If you do this, you will notice that running the ‘install’ command first
runs the ‘build’ command, which—in this case—quickly notices that it has
nothing to do, since everything in the ‘build’ directory is up-to-date.

You may not need this ability to break things down often if all you do
is install modules downloaded off the ’net, but it’s very handy for more
advanced tasks.  If you get into distributing your own Python modules
and extensions, you’ll run lots of individual Distutils commands on
their own.


File: python.info,  Node: How building works,  Next: How installation works,  Prev: Splitting the job up,  Up: Standard Build and Install

18.2.3 How building works
-------------------------

As implied above, the ‘build’ command is responsible for putting the
files to install into a `build directory'.  By default, this is ‘build’
under the distribution root; if you’re excessively concerned with speed,
or want to keep the source tree pristine, you can change the build
directory with the ‘--build-base’ option.  For example:

     python setup.py build --build-base=/path/to/pybuild/foo-1.0

(Or you could do this permanently with a directive in your system or
personal Distutils configuration file; see section *note Distutils
Configuration Files: 444d.)  Normally, this isn’t necessary.

The default layout for the build tree is as follows:

     --- build/ --- lib/
     or
     --- build/ --- lib.<plat>/
                    temp.<plat>/

where ‘<plat>’ expands to a brief description of the current OS/hardware
platform and Python version.  The first form, with just a ‘lib’
directory, is used for "pure module distributions"—that is, module
distributions that include only pure Python modules.  If a module
distribution contains any extensions (modules written in C/C++), then
the second form, with two ‘<plat>’ directories, is used.  In that case,
the ‘temp.`plat'’ directory holds temporary files generated by the
compile/link process that don’t actually get installed.  In either case,
the ‘lib’ (or ‘lib.`plat'’) directory contains all Python modules (pure
Python and extensions) that will be installed.

In the future, more directories will be added to handle Python scripts,
documentation, binary executables, and whatever else is needed to handle
the job of installing Python modules and applications.


File: python.info,  Node: How installation works,  Prev: How building works,  Up: Standard Build and Install

18.2.4 How installation works
-----------------------------

After the ‘build’ command runs (whether you run it explicitly, or the
‘install’ command does it for you), the work of the ‘install’ command is
relatively simple: all it has to do is copy everything under ‘build/lib’
(or ‘build/lib.`plat'’) to your chosen installation directory.

If you don’t choose an installation directory—i.e., if you just run
‘setup.py install’—then the ‘install’ command installs to the standard
location for third-party Python modules.  This location varies by
platform and by how you built/installed Python itself.  On Unix (and Mac
OS X, which is also Unix-based), it also depends on whether the module
distribution being installed is pure Python or contains extensions
("non-pure"):

Platform              Standard installation location                            Default value                                          註解
                                                                                                                                       
---------------------------------------------------------------------------------------------------------------------------------------------------
                                                                                                                                       
Unix (pure)           ‘`prefix'/lib/python`X.Y'/site-packages’                  ‘/usr/local/lib/python`X.Y'/site-packages’             (1)
                                                                                                                                       
                                                                                                                                       
Unix (non-pure)       ‘`exec-prefix'/lib/python`X.Y'/site-packages’             ‘/usr/local/lib/python`X.Y'/site-packages’             (1)
                                                                                                                                       
                                                                                                                                       
Windows               ‘`prefix'\Lib\site-packages’                              ‘C:\Python`XY'\Lib\site-packages’                      (2)
                                                                                                                                       

註解：

  1. Most Linux distributions include Python as a standard part of the
     system, so ‘`prefix'’ and ‘`exec-prefix'’ are usually both ‘/usr’
     on Linux.  If you build Python yourself on Linux (or any Unix-like
     system), the default ‘`prefix'’ and ‘`exec-prefix'’ are
     ‘/usr/local’.

  2. The default installation directory on Windows was ‘C:\Program
     Files\Python’ under Python 1.6a1, 1.5.2, and earlier.

‘`prefix'’ and ‘`exec-prefix'’ stand for the directories that Python is
installed to, and where it finds its libraries at run-time.  They are
always the same under Windows, and very often the same under Unix and
Mac OS X. You can find out what your Python installation uses for
‘`prefix'’ and ‘`exec-prefix'’ by running Python in interactive mode and
typing a few simple commands.  Under Unix, just type ‘python’ at the
shell prompt.  Under Windows, choose Start ‣ Programs ‣ Python X.Y ‣
Python (command line).  Once the interpreter is started, you type Python
code at the prompt.  For example, on my Linux system, I type the three
Python statements shown below, and get the output as shown, to find out
my ‘`prefix'’ and ‘`exec-prefix'’:

     Python 2.4 (#26, Aug  7 2004, 17:19:02)
     Type "help", "copyright", "credits" or "license" for more information.
     >>> import sys
     >>> sys.prefix
     '/usr'
     >>> sys.exec_prefix
     '/usr'

A few other placeholders are used in this document: ‘`X.Y'’ stands for
the version of Python, for example ‘3.2’; ‘`abiflags'’ will be replaced
by the value of *note sys.abiflags: 265. or the empty string for
platforms which don’t define ABI flags; ‘`distname'’ will be replaced by
the name of the module distribution being installed.  Dots and
capitalization are important in the paths; for example, a value that
uses ‘python3.2’ on UNIX will typically use ‘Python32’ on Windows.

If you don’t want to install modules to the standard location, or if you
don’t have permission to write there, then you need to read about
alternate installations in section *note Alternate Installation: 4450.
If you want to customize your installation directories more heavily, see
section *note Custom Installation: 4451. on custom installations.


File: python.info,  Node: Alternate Installation,  Next: Custom Installation,  Prev: Standard Build and Install,  Up: 安裝 Python 模組（舊版）

18.3 Alternate Installation
===========================

Often, it is necessary or desirable to install modules to a location
other than the standard location for third-party Python modules.  For
example, on a Unix system you might not have permission to write to the
standard third-party module directory.  Or you might wish to try out a
module before making it a standard part of your local Python
installation.  This is especially true when upgrading a distribution
already present: you want to make sure your existing base of scripts
still works with the new version before actually upgrading.

The Distutils ‘install’ command is designed to make installing module
distributions to an alternate location simple and painless.  The basic
idea is that you supply a base directory for the installation, and the
‘install’ command picks a set of directories (called an `installation
scheme') under this base directory in which to install files.  The
details differ across platforms, so read whichever of the following
sections applies to you.

Note that the various alternate installation schemes are mutually
exclusive: you can pass ‘--user’, or ‘--home’, or ‘--prefix’ and
‘--exec-prefix’, or ‘--install-base’ and ‘--install-platbase’, but you
can’t mix from these groups.

* Menu:

* Alternate installation; the user scheme: Alternate installation the user scheme.
* Alternate installation; the home scheme: Alternate installation the home scheme.
* Alternate installation; Unix (the prefix scheme): Alternate installation Unix the prefix scheme.
* Alternate installation; Windows (the prefix scheme): Alternate installation Windows the prefix scheme.


File: python.info,  Node: Alternate installation the user scheme,  Next: Alternate installation the home scheme,  Up: Alternate Installation

18.3.1 Alternate installation: the 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.  It is enabled with a simple option:

     python setup.py install --user

Files will be installed into subdirectories of *note site.USER_BASE:
135d. (written as ‘`userbase'’ hereafter).  This scheme installs pure
Python modules and extension modules in the same location (also known as
*note site.USER_SITE: 134b.).  Here are the values for UNIX, including
Mac OS X:

Type of file        Installation directory
                    
------------------------------------------------------------------------------------
                    
modules             ‘`userbase'/lib/python`X.Y'/site-packages’
                    
                    
scripts             ‘`userbase'/bin’
                    
                    
data                ‘`userbase'’
                    
                    
C headers           ‘`userbase'/include/python`X.Y'`abiflags'/`distname'’
                    

And here are the values used on Windows:

Type of file        Installation directory
                    
------------------------------------------------------------------------------------
                    
modules             ‘`userbase'\Python`XY'\site-packages’
                    
                    
scripts             ‘`userbase'\Python`XY'\Scripts’
                    
                    
data                ‘`userbase'’
                    
                    
C headers           ‘`userbase'\Python`XY'\Include{distname}’
                    

The advantage of using this scheme compared to the other ones described
below is that the user site-packages directory is under normal
conditions always included in *note sys.path: 48d. (see *note site: ec.
for more information), which means that there is no additional step to
perform after running the ‘setup.py’ script to finalize the
installation.

The ‘build_ext’ command also has a ‘--user’ option to add
‘`userbase'/include’ to the compiler search path for header files and
‘`userbase'/lib’ to the compiler search path for libraries as well as to
the runtime search path for shared C libraries (rpath).


File: python.info,  Node: Alternate installation the home scheme,  Next: Alternate installation Unix the prefix scheme,  Prev: Alternate installation the user scheme,  Up: Alternate Installation

18.3.2 Alternate installation: the 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.

Installing a new module distribution is as simple as

     python setup.py install --home=<dir>

where you can supply any directory you like for the ‘--home’ option.  On
Unix, lazy typists can just type a tilde (‘~’); the ‘install’ command
will expand this to your home directory:

     python setup.py install --home=~

To make Python find the distributions installed with this scheme, you
may have to *note modify Python’s search path: 4456. or edit
‘sitecustomize’ (see *note site: ec.) to call *note site.addsitedir():
3710. or edit *note sys.path: 48d.

The ‘--home’ option defines the installation base directory.  Files are
installed to the following directories under the installation base as
follows:

Type of file        Installation directory
                    
------------------------------------------------------------------------------------
                    
modules             ‘`home'/lib/python’
                    
                    
scripts             ‘`home'/bin’
                    
                    
data                ‘`home'’
                    
                    
C headers           ‘`home'/include/python/`distname'’
                    

(Mentally replace slashes with backslashes if you’re on Windows.)


File: python.info,  Node: Alternate installation Unix the prefix scheme,  Next: Alternate installation Windows the prefix scheme,  Prev: Alternate installation the home scheme,  Up: Alternate Installation

18.3.3 Alternate installation: Unix (the 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'’.  This can be done with

     /usr/bin/python setup.py install --prefix=/usr/local

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'’.  This could be done with

     /usr/local/bin/python setup.py install --prefix=/mnt/@server/export

In either case, the ‘--prefix’ option defines the installation base, and
the ‘--exec-prefix’ option defines the platform-specific installation
base, which is used for platform-specific files.  (Currently, this just
means non-pure module distributions, but could be expanded to C
libraries, binary executables, etc.)  If ‘--exec-prefix’ is not
supplied, it defaults to ‘--prefix’.  Files are installed as follows:

Type of file          Installation directory
                      
-------------------------------------------------------------------------------------
                      
Python modules        ‘`prefix'/lib/python`X.Y'/site-packages’
                      
                      
extension modules     ‘`exec-prefix'/lib/python`X.Y'/site-packages’
                      
                      
scripts               ‘`prefix'/bin’
                      
                      
data                  ‘`prefix'’
                      
                      
C headers             ‘`prefix'/include/python`X.Y'`abiflags'/`distname'’
                      

There is no requirement that ‘--prefix’ or ‘--exec-prefix’ actually
point to an alternate Python installation; if the directories listed
above do not already exist, they are created at installation time.

Incidentally, the real reason the prefix scheme is important is simply
that a standard Unix installation uses the prefix scheme, but with
‘--prefix’ and ‘--exec-prefix’ supplied by Python itself as ‘sys.prefix’
and ‘sys.exec_prefix’.  Thus, you might think you’ll never use the
prefix scheme, but every time you run ‘python setup.py install’ without
any other options, you’re using it.

Note that installing extensions to an alternate Python installation has
no effect on how those extensions are built: in particular, the Python
header files (‘Python.h’ and friends) installed with the Python
interpreter used to run the setup script will be used in compiling
extensions.  It is your responsibility to ensure that the interpreter
used to run extensions installed in this way is compatible with the
interpreter used to build them.  The best way to do this is to ensure
that the two interpreters are the same version of Python (possibly
different builds, or possibly copies of the same build).  (Of course, if
your ‘--prefix’ and ‘--exec-prefix’ don’t even point to an alternate
Python installation, this is immaterial.)


File: python.info,  Node: Alternate installation Windows the prefix scheme,  Prev: Alternate installation Unix the prefix scheme,  Up: Alternate Installation

18.3.4 Alternate installation: Windows (the prefix scheme)
----------------------------------------------------------

Windows has no concept of a user’s home directory, and since the
standard Python installation under Windows is simpler than under Unix,
the ‘--prefix’ option has traditionally been used to install additional
packages in separate locations on Windows.

     python setup.py install --prefix="\Temp\Python"

to install modules to the ‘\Temp\Python’ directory on the current drive.

The installation base is defined by the ‘--prefix’ option; the
‘--exec-prefix’ option is not supported under Windows, which means that
pure Python modules and extension modules are installed into the same
location.  Files are installed as follows:

Type of file        Installation directory
                    
-----------------------------------------------------------------------------------
                    
modules             ‘`prefix'\Lib\site-packages’
                    
                    
scripts             ‘`prefix'\Scripts’
                    
                    
data                ‘`prefix'’
                    
                    
C headers           ‘`prefix'\Include{distname}’
                    


File: python.info,  Node: Custom Installation,  Next: Distutils Configuration Files,  Prev: Alternate Installation,  Up: 安裝 Python 模組（舊版）

18.4 Custom Installation
========================

Sometimes, the alternate installation schemes described in section *note
Alternate Installation: 4450. just don’t do what you want.  You might
want to tweak just one or two directories while keeping everything under
the same base directory, or you might want to completely redefine the
installation scheme.  In either case, you’re creating a `custom
installation scheme'.

To create a custom installation scheme, you start with one of the
alternate schemes and override some of the installation directories used
for the various types of files, using these options:

Type of file               Override option
                           
-------------------------------------------------------
                           
Python modules             ‘--install-purelib’
                           
                           
extension modules          ‘--install-platlib’
                           
                           
all modules                ‘--install-lib’
                           
                           
scripts                    ‘--install-scripts’
                           
                           
data                       ‘--install-data’
                           
                           
C headers                  ‘--install-headers’
                           

These override options can be relative, absolute, or explicitly defined
in terms of one of the installation base directories.  (There are two
installation base directories, and they are normally the same—they only
differ when you use the Unix "prefix scheme" and supply different
‘--prefix’ and ‘--exec-prefix’ options; using ‘--install-lib’ will
override values computed or given for ‘--install-purelib’ and
‘--install-platlib’, and is recommended for schemes that don’t make a
difference between Python and extension modules.)

For example, say you’re installing a module distribution to your home
directory under Unix—but you want scripts to go in ‘~/scripts’ rather
than ‘~/bin’.  As you might expect, you can override this directory with
the ‘--install-scripts’ option; in this case, it makes most sense to
supply a relative path, which will be interpreted relative to the
installation base directory (your home directory, in this case):

     python setup.py install --home=~ --install-scripts=scripts

Another Unix example: suppose your Python installation was built and
installed with a prefix of ‘/usr/local/python’, so under a standard
installation scripts will wind up in ‘/usr/local/python/bin’.  If you
want them in ‘/usr/local/bin’ instead, you would supply this absolute
directory for the ‘--install-scripts’ option:

     python setup.py install --install-scripts=/usr/local/bin

(This performs an installation using the "prefix scheme", where the
prefix is whatever your Python interpreter was installed with—
‘/usr/local/python’ in this case.)

If you maintain Python on Windows, you might want third-party modules to
live in a subdirectory of ‘`prefix'’, rather than right in ‘`prefix'’
itself.  This is almost as easy as customizing the script installation
directory—you just have to remember that there are two types of modules
to worry about, Python and extension modules, which can conveniently be
both controlled by one option:

     python setup.py install --install-lib=Site

The specified installation directory is relative to ‘`prefix'’.  Of
course, you also have to ensure that this directory is in Python’s
module search path, such as by putting a ‘.pth’ file in a site directory
(see *note site: ec.).  See section *note Modifying Python’s Search
Path: 4456. to find out how to modify Python’s search path.

If you want to define an entire installation scheme, you just have to
supply all of the installation directory options.  The recommended way
to do this is to supply relative paths; for example, if you want to
maintain all Python module-related files under ‘python’ in your home
directory, and you want a separate directory for each platform that you
use your home directory from, you might define the following
installation scheme:

     python setup.py install --home=~ \
                             --install-purelib=python/lib \
                             --install-platlib=python/lib.$PLAT \
                             --install-scripts=python/scripts
                             --install-data=python/data

or, equivalently,

     python setup.py install --home=~/python \
                             --install-purelib=lib \
                             --install-platlib='lib.$PLAT' \
                             --install-scripts=scripts
                             --install-data=data

‘$PLAT’ is not (necessarily) an environment variable—it will be expanded
by the Distutils as it parses your command line options, just as it does
when parsing your configuration file(s).

Obviously, specifying the entire installation scheme every time you
install a new module distribution would be very tedious.  Thus, you can
put these options into your Distutils config file (see section *note
Distutils Configuration Files: 444d.):

     [install]
     install-base=$HOME
     install-purelib=python/lib
     install-platlib=python/lib.$PLAT
     install-scripts=python/scripts
     install-data=python/data

or, equivalently,

     [install]
     install-base=$HOME/python
     install-purelib=lib
     install-platlib=lib.$PLAT
     install-scripts=scripts
     install-data=data

Note that these two are `not' equivalent if you supply a different
installation base directory when you run the setup script.  For example,

     python setup.py install --install-base=/tmp

would install pure modules to ‘/tmp/python/lib’ in the first case, and
to ‘/tmp/lib’ in the second case.  (For the second case, you probably
want to supply an installation base of ‘/tmp/python’.)

You probably noticed the use of ‘$HOME’ and ‘$PLAT’ in the sample
configuration file input.  These are Distutils configuration variables,
which bear a strong resemblance to environment variables.  In fact, you
can use environment variables in config files on platforms that have
such a notion but the Distutils additionally define a few extra
variables that may not be in your environment, such as ‘$PLAT’.  (And of
course, on systems that don’t have environment variables, such as Mac OS
9, the configuration variables supplied by the Distutils are the only
ones you can use.)  See section *note Distutils Configuration Files:
444d. for details.

     備註: When a *note virtual environment: 35f9. is activated, any
     options that change the installation path will be ignored from all
     distutils configuration files to prevent inadvertently installing
     projects outside of the virtual environment.

* Menu:

* Modifying Python's Search Path::


File: python.info,  Node: Modifying Python's Search Path,  Up: Custom Installation

18.4.1 Modifying Python’s Search Path
-------------------------------------

When the Python interpreter executes an *note import: c22. statement, it
searches for both Python code and extension modules along a search path.
A default value for the path is configured into the Python binary when
the interpreter is built.  You can determine the path by importing the
*note sys: fe. module and printing the value of ‘sys.path’.

     $ python
     Python 2.2 (#11, Oct  3 2002, 13:31:27)
     [GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-112)] on linux2
     Type "help", "copyright", "credits" or "license" for more information.
     >>> import sys
     >>> sys.path
     ['', '/usr/local/lib/python2.3', '/usr/local/lib/python2.3/plat-linux2',
      '/usr/local/lib/python2.3/lib-tk', '/usr/local/lib/python2.3/lib-dynload',
      '/usr/local/lib/python2.3/site-packages']
     >>>

The null string in ‘sys.path’ represents the current working directory.

The expected convention for locally installed packages is to put them in
the ‘`...'/site-packages/’ directory, but you may want to install Python
modules into some arbitrary directory.  For example, your site may have
a convention of keeping all software related to the web server under
‘/www’.  Add-on Python modules might then belong in ‘/www/python’, and
in order to import them, this directory must be added to ‘sys.path’.
There are several different ways to add the directory.

The most convenient way is to add a path configuration file to a
directory that’s already on Python’s path, usually to the
‘.../site-packages/’ directory.  Path configuration files have an
extension of ‘.pth’, and each line must contain a single path that will
be appended to ‘sys.path’.  (Because the new paths are appended to
‘sys.path’, modules in the added directories will not override standard
modules.  This means you can’t use this mechanism for installing fixed
versions of standard modules.)

Paths can be absolute or relative, in which case they’re relative to the
directory containing the ‘.pth’ file.  See the documentation of the
*note site: ec. module for more information.

A slightly less convenient way is to edit the ‘site.py’ file in Python’s
standard library, and modify ‘sys.path’.  ‘site.py’ is automatically
imported when the Python interpreter is executed, unless the *note -S:
b29. switch is supplied to suppress this behaviour.  So you could simply
edit ‘site.py’ and add two lines to it:

     import sys
     sys.path.append('/www/python/')

However, if you reinstall the same major version of Python (perhaps when
upgrading from 2.2 to 2.2.2, for example) ‘site.py’ will be overwritten
by the stock version.  You’d have to remember that it was modified and
save a copy before doing the installation.

There are two environment variables that can modify ‘sys.path’.  *note
PYTHONHOME: 4db. sets an alternate value for the prefix of the Python
installation.  For example, if *note PYTHONHOME: 4db. is set to
‘/www/python’, the search path will be set to ‘['',
'/www/python/lib/pythonX.Y/', '/www/python/lib/pythonX.Y/plat-linux2',
...]’.

The *note PYTHONPATH: 958. variable can be set to a list of paths that
will be added to the beginning of ‘sys.path’.  For example, if *note
PYTHONPATH: 958. is set to ‘/www/python:/opt/py’, the search path will
begin with ‘['/www/python', '/opt/py']’.  (Note that directories must
exist in order to be added to ‘sys.path’; the *note site: ec. module
removes paths that don’t exist.)

Finally, ‘sys.path’ is just a regular Python list, so any Python
application can modify it by adding or removing entries.


File: python.info,  Node: Distutils Configuration Files,  Next: Building Extensions Tips and Tricks,  Prev: Custom Installation,  Up: 安裝 Python 模組（舊版）

18.5 Distutils Configuration Files
==================================

As mentioned above, you can use Distutils configuration files to record
personal or site preferences for any Distutils options.  That is, any
option to any command can be stored in one of two or three (depending on
your platform) configuration files, which will be consulted before the
command-line is parsed.  This means that configuration files will
override default values, and the command-line will in turn override
configuration files.  Furthermore, if multiple configuration files
apply, values from "earlier" files are overridden by "later" files.

* Menu:

* Location and names of config files::
* Syntax of config files::


File: python.info,  Node: Location and names of config files,  Next: Syntax of config files,  Up: Distutils Configuration Files

18.5.1 Location and names of config files
-----------------------------------------

The names and locations of the configuration files vary slightly across
platforms.  On Unix and Mac OS X, the three configuration files (in the
order they are processed) are:

Type of file       Location and filename                                          註解
                                                                                  
----------------------------------------------------------------------------------------------
                                                                                  
system             ‘`prefix'/lib/python`ver'/distutils/distutils.cfg’             (1)
                                                                                  
                                                                                  
personal           ‘$HOME/.pydistutils.cfg’                                       (2)
                                                                                  
                                                                                  
local              ‘setup.cfg’                                                    (3)
                                                                                  

And on Windows, the configuration files are:

Type of file       Location and filename                                 註解
                                                                         
-------------------------------------------------------------------------------------
                                                                         
system             ‘`prefix'\Lib\distutils\distutils.cfg’                (4)
                                                                         
                                                                         
personal           ‘%HOME%\pydistutils.cfg’                              (5)
                                                                         
                                                                         
local              ‘setup.cfg’                                           (3)
                                                                         

On all platforms, the "personal" file can be temporarily disabled by
passing the ‘–no-user-cfg’ option.

註解：

  1. Strictly speaking, the system-wide configuration file lives in the
     directory where the Distutils are installed; under Python 1.6 and
     later on Unix, this is as shown.  For Python 1.5.2, the Distutils
     will normally be installed to
     ‘`prefix'/lib/python1.5/site-packages/distutils’, so the system
     configuration file should be put there under Python 1.5.2.

  2. On Unix, if the ‘HOME’ environment variable is not defined, the
     user’s home directory will be determined with the ‘getpwuid()’
     function from the standard *note pwd: d7. module.  This is done by
     the *note os.path.expanduser(): 1ff. function used by Distutils.

  3. I.e., in the current directory (usually the location of the setup
     script).

  4. (See also note (1).)  Under Python 1.6 and later, Python’s default
     "installation prefix" is ‘C:\Python’, so the system configuration
     file is normally ‘C:\Python\Lib\distutils\distutils.cfg’.  Under
     Python 1.5.2, the default prefix was ‘C:\Program Files\Python’, and
     the Distutils were not part of the standard library—so the system
     configuration file would be ‘C:\Program
     Files\Python\distutils\distutils.cfg’ in a standard Python 1.5.2
     installation under Windows.

  5. On Windows, if the ‘HOME’ environment variable is not defined,
     ‘USERPROFILE’ then ‘HOMEDRIVE’ and ‘HOMEPATH’ will be tried.  This
     is done by the *note os.path.expanduser(): 1ff. function used by
     Distutils.


File: python.info,  Node: Syntax of config files,  Prev: Location and names of config files,  Up: Distutils Configuration Files

18.5.2 Syntax of config files
-----------------------------

The Distutils configuration files all have the same syntax.  The config
files are grouped into sections.  There is one section for each
Distutils command, plus a ‘global’ section for global options that
affect every command.  Each section consists of one option per line,
specified as ‘option=value’.

For example, the following is a complete config file that just forces
all commands to run quietly by default:

     [global]
     verbose=0

If this is installed as the system config file, it will affect all
processing of any Python module distribution by any user on the current
system.  If it is installed as your personal config file (on systems
that support them), it will affect only module distributions processed
by you.  And if it is used as the ‘setup.cfg’ for a particular module
distribution, it affects only that distribution.

You could override the default "build base" directory and make the
‘build*’ commands always forcibly rebuild all files with the following:

     [build]
     build-base=blib
     force=1

which corresponds to the command-line arguments

     python setup.py build --build-base=blib --force

except that including the ‘build’ command on the command-line means that
command will be run.  Including a particular command in config files has
no such implication; it only means that if the command is run, the
options in the config file will apply.  (Or if other commands that
derive values from it are run, they will use the values in the config
file.)

You can find out the complete list of options for any command using the
‘--help’ option, e.g.:

     python setup.py build --help

and you can find out the complete list of global options by using
‘--help’ without a command:

     python setup.py --help

See also the "Reference" section of the "Distributing Python Modules"
manual.


File: python.info,  Node: Building Extensions Tips and Tricks,  Prev: Distutils Configuration Files,  Up: 安裝 Python 模組（舊版）

18.6 Building Extensions: Tips and Tricks
=========================================

Whenever possible, the Distutils try to use the configuration
information made available by the Python interpreter used to run the
‘setup.py’ script.  For example, the same compiler and linker flags used
to compile Python will also be used for compiling extensions.  Usually
this will work well, but in complicated situations this might be
inappropriate.  This section discusses how to override the usual
Distutils behaviour.

* Menu:

* Tweaking compiler/linker flags::
* Using non-Microsoft compilers on Windows::


File: python.info,  Node: Tweaking compiler/linker flags,  Next: Using non-Microsoft compilers on Windows,  Up: Building Extensions Tips and Tricks

18.6.1 Tweaking compiler/linker flags
-------------------------------------

Compiling a Python extension written in C or C++ will sometimes require
specifying custom flags for the compiler and linker in order to use a
particular library or produce a special kind of object code.  This is
especially true if the extension hasn’t been tested on your platform, or
if you’re trying to cross-compile Python.

In the most general case, the extension author might have foreseen that
compiling the extensions would be complicated, and provided a ‘Setup’
file for you to edit.  This will likely only be done if the module
distribution contains many separate extension modules, or if they often
require elaborate sets of compiler flags in order to work.

A ‘Setup’ file, if present, is parsed in order to get a list of
extensions to build.  Each line in a ‘Setup’ describes a single module.
Lines have the following structure:

     module ... [sourcefile ...] [cpparg ...] [library ...]

Let’s examine each of the fields in turn.

   * `module' is the name of the extension module to be built, and
     should be a valid Python identifier.  You can’t just change this in
     order to rename a module (edits to the source code would also be
     needed), so this should be left alone.

   * `sourcefile' is anything that’s likely to be a source code file, at
     least judging by the filename.  Filenames ending in ‘.c’ are
     assumed to be written in C, filenames ending in ‘.C’, ‘.cc’, and
     ‘.c++’ are assumed to be C++, and filenames ending in ‘.m’ or ‘.mm’
     are assumed to be in Objective C.

   * `cpparg' is an argument for the C preprocessor, and is anything
     starting with ‘-I’, ‘-D’, ‘-U’ or ‘-C’.

   * `library' is anything ending in ‘.a’ or beginning with ‘-l’ or
     ‘-L’.

If a particular platform requires a special library on your platform,
you can add it by editing the ‘Setup’ file and running ‘python setup.py
build’.  For example, if the module defined by the line

     foo foomodule.c

must be linked with the math library ‘libm.a’ on your platform, simply
add ‘-lm’ to the line:

     foo foomodule.c -lm

Arbitrary switches intended for the compiler or the linker can be
supplied with the ‘-Xcompiler’ `arg' and ‘-Xlinker’ `arg' options:

     foo foomodule.c -Xcompiler -o32 -Xlinker -shared -lm

The next option after ‘-Xcompiler’ and ‘-Xlinker’ will be appended to
the proper command line, so in the above example the compiler will be
passed the ‘-o32’ option, and the linker will be passed ‘-shared’.  If a
compiler option requires an argument, you’ll have to supply multiple
‘-Xcompiler’ options; for example, to pass ‘-x c++’ the ‘Setup’ file
would have to contain ‘-Xcompiler -x -Xcompiler c++’.

Compiler flags can also be supplied through setting the ‘CFLAGS’
environment variable.  If set, the contents of ‘CFLAGS’ will be added to
the compiler flags specified in the ‘Setup’ file.


File: python.info,  Node: Using non-Microsoft compilers on Windows,  Prev: Tweaking compiler/linker flags,  Up: Building Extensions Tips and Tricks

18.6.2 Using non-Microsoft compilers on Windows
-----------------------------------------------

* Menu:

* Borland/CodeGear C++::
* GNU C / Cygwin / MinGW::


File: python.info,  Node: Borland/CodeGear C++,  Next: GNU C / Cygwin / MinGW,  Up: Using non-Microsoft compilers on Windows

18.6.2.1 Borland/CodeGear C++
.............................

This subsection describes the necessary steps to use Distutils with the
Borland C++ compiler version 5.5.  First you have to know that Borland’s
object file format (OMF) is different from the format used by the Python
version you can download from the Python or ActiveState Web site.
(Python is built with Microsoft Visual C++, which uses COFF as the
object file format.)  For this reason you have to convert Python’s
library ‘python25.lib’ into the Borland format.  You can do this as
follows:

     coff2omf python25.lib python25_bcpp.lib

The ‘coff2omf’ program comes with the Borland compiler.  The file
‘python25.lib’ is in the ‘Libs’ directory of your Python installation.
If your extension uses other libraries (zlib, ...)  you have to convert
them too.

The converted files have to reside in the same directories as the normal
libraries.

How does Distutils manage to use these libraries with their changed
names?  If the extension needs a library (eg.  ‘foo’) Distutils checks
first if it finds a library with suffix ‘_bcpp’ (eg.  ‘foo_bcpp.lib’)
and then uses this library.  In the case it doesn’t find such a special
library it uses the default name (‘foo.lib’.)  (1)

To let Distutils compile your extension with Borland C++ you now have to
type:

     python setup.py build --compiler=bcpp

If you want to use the Borland C++ compiler as the default, you could
specify this in your personal or system-wide configuration file for
Distutils (see section *note Distutils Configuration Files: 444d.)

也參考
......

C++Builder Compiler(2)

     Information about the free C++ compiler from Borland, including
     links to the download pages.

Creating Python Extensions Using Borland’s Free Compiler(3)

     Document describing how to use Borland’s free command-line C++
     compiler to build Python.

   ---------- Footnotes ----------

   (1) (1) This also means you could replace all existing COFF-libraries
with OMF-libraries of the same name.

   (2) https://www.embarcadero.com/products

   (3) http://www.cyberus.ca/~g_will/pyExtenDL.shtml


File: python.info,  Node: GNU C / Cygwin / MinGW,  Prev: Borland/CodeGear C++,  Up: Using non-Microsoft compilers on Windows

18.6.2.2 GNU C / Cygwin / MinGW
...............................

This section describes the necessary steps to use Distutils with the GNU
C/C++ compilers in their Cygwin and MinGW distributions.  (1) For a
Python interpreter that was built with Cygwin, everything should work
without any of these following steps.

Not all extensions can be built with MinGW or Cygwin, but many can.
Extensions most likely to not work are those that use C++ or depend on
Microsoft Visual C extensions.

To let Distutils compile your extension with Cygwin you have to type:

     python setup.py build --compiler=cygwin

and for Cygwin in no-cygwin mode (2) or for MinGW type:

     python setup.py build --compiler=mingw32

If you want to use any of these options/compilers as default, you should
consider writing it in your personal or system-wide configuration file
for Distutils (see section *note Distutils Configuration Files: 444d.)

* Menu:

* Older Versions of Python and MinGW::

   ---------- Footnotes ----------

   (1) (2) Check ‘https://www.sourceware.org/cygwin/’ for more
information

   (2) (3) Then you have no POSIX emulation available, but you also
don’t need ‘cygwin1.dll’.


File: python.info,  Node: Older Versions of Python and MinGW,  Up: GNU C / Cygwin / MinGW

18.6.2.3 Older Versions of Python and MinGW
...........................................

The following instructions only apply if you’re using a version of
Python inferior to 2.4.1 with a MinGW inferior to 3.0.0 (with
binutils-2.13.90-20030111-1).

These compilers require some special libraries.  This task is more
complex than for Borland’s C++, because there is no program to convert
the library.  First you have to create a list of symbols which the
Python DLL exports.  (You can find a good program for this task at
‘https://sourceforge.net/projects/mingw/files/MinGW/Extension/pexports/’).

     pexports python25.dll >python25.def

The location of an installed ‘python25.dll’ will depend on the
installation options and the version and language of Windows.  In a
"just for me" installation, it will appear in the root of the
installation directory.  In a shared installation, it will be located in
the system directory.

Then you can create from these information an import library for gcc.

     /cygwin/bin/dlltool --dllname python25.dll --def python25.def --output-lib libpython25.a

The resulting library has to be placed in the same directory as
‘python25.lib’.  (Should be the ‘libs’ directory under your Python
installation directory.)

If your extension uses other libraries (zlib,...)  you might have to
convert them too.  The converted files have to reside in the same
directories as the normal libraries do.

也參考
......

Building Python modules on MS Windows platform with MinGW(1)

     Information about building the required libraries for the MinGW
     environment.

註解
....

   ---------- Footnotes ----------

   (1) http://old.zope.org/Members/als/tips/win32_mingw_modules


File: python.info,  Node: Python 模組索引,  Next: 索引,  Prev: 安裝 Python 模組（舊版）,  Up: Top

Python 模組索引
***************

* Menu:

* __future__: 0. Future statement definitions
* __main__: 1. The environment where the top-level script is run.
* _dummy_thread: 2. Drop-in replacement for the _thread module.
* _thread: 3. Low-level threading API.
* abc: 4. Abstract base classes according to :pep:‘3119‘.
* aifc: 5. Read and write audio files in AIFF or AIFC format.
* argparse: 6. Command-line option and argument parsing library.
* array: 7. Space efficient arrays of uniformly typed numeric
                        values.
* ast: 8. Abstract Syntax Tree classes and manipulation.
* asynchat: 9. Support for asynchronous command/response protocols.
* asyncio: a. Asynchronous I/O.
* asyncore: b. A base class for developing asynchronous socket
                        handling services.
* atexit: c. Register and execute cleanup functions.
* audioop: d. Manipulate raw audio data.
* base64: e. RFC 3548: Base16, Base32, Base64 Data
                        Encodings; Base85 and Ascii85
* bdb: f. Debugger framework.
* binascii: 10. Tools for converting between binary and various ASCII-
                        encoded binary representations.
* binhex: 11. Encode and decode files in binhex4 format.
* bisect: 12. Array bisection algorithms for binary searching.
* builtins: 13. The module that provides the built-in namespace.
* bz2: 14. Interfaces for bzip2 compression and decompression.
* calendar: 15. Functions for working with calendars, including
                        some emulation of the Unix cal program.
* cgi: 16. Helpers for running Python scripts via the Common
                        Gateway Interface.
* cgitb: 17. Configurable traceback handler for CGI scripts.
* chunk: 18. Module to read IFF chunks.
* cmath: 19. Mathematical functions for complex numbers.
* cmd: 1a. Build line-oriented command interpreters.
* code: 1b. Facilities to implement read-eval-print loops.
* codecs: 1c. Encode and decode data and streams.
* codeop: 1d. Compile (possibly incomplete) Python code.
* collections: 1e. Container datatypes
* collections.abc: 1f. Abstract base classes for containers
* colorsys: 20. Conversion functions between RGB and other color
                        systems.
* compileall: 21. Tools for byte-compiling all Python source files in a
                        directory tree.
* concurrent.futures: 22. Execute computations concurrently using threads or
                        processes.
* configparser: 23. Configuration file parser.
* contextlib: 24. Utilities for with-statement contexts.
* contextvars: 25. Context Variables
* copy: 26. Shallow and deep copy operations.
* copyreg: 27. Register pickle support functions.
* cProfile: 28.
* crypt: 29. The crypt() function used to check Unix passwords.
* csv: 2a. Write and read tabular data to and from delimited
                        files.
* ctypes: 2b. A foreign function library for Python.
* curses: 2c. An interface to the curses library, providing
                        portable terminal handling.
* curses.ascii: 2d. Constants and set-membership functions for ASCII
                        characters.
* curses.panel: 2e. A panel stack extension that adds depth to curses
                        windows.
* curses.textpad: 2f. Emacs-like input editing in a curses window.
* dataclasses: 30. Generate special methods on user-defined classes.
* datetime: 31. Basic date and time types.
* dbm: 32. Interfaces to various Unix "database" formats.
* dbm.dumb: 33. Portable implementation of the simple DBM interface.
* dbm.gnu: 34. GNU’s reinterpretation of dbm.
* dbm.ndbm: 35. The standard "database" interface, based on
                        ndbm.
* decimal: 36. Implementation of the General Decimal Arithmetic
                        Specification.
* difflib: 37. Helpers for computing differences between objects.
* dis: 38. Disassembler for Python bytecode.
* distutils: 39. Support for building and installing Python modules
                        into an existing Python installation.
* distutils.archive_util: 3a. Utility functions for creating archive files
                          (tarballs, zip files, ...)
* distutils.bcppcompiler: 3b.
* distutils.ccompiler: 3c. Abstract CCompiler class
* distutils.cmd: 3d. Provides the abstract base class
                        :class:‘~distutils.cmd.Command‘. This class is
                        subclassed by the modules in the distutils.command
                        subpackage.
* distutils.command: 3e. Contains one module for each standard Distutils
                        command.
* distutils.command.bdist: 3f. Build a binary installer for a package
* distutils.command.bdist_dumb: 40. Build a "dumb" installer - a simple archive of
                                files
* distutils.command.bdist_msi: 41. Build a binary distribution as a Windows MSI
                               file
* distutils.command.bdist_packager: 42. Abstract base class for packagers
* distutils.command.bdist_rpm: 43. Build a binary distribution as a Redhat RPM and
                               SRPM
* distutils.command.bdist_wininst: 44. Build a Windows installer
* distutils.command.build: 45. Build all files of a package
* distutils.command.build_clib: 46. Build any C libraries in a package
* distutils.command.build_ext: 47. Build any extensions in a package
* distutils.command.build_py: 48. Build the .py/.pyc files of a package
* distutils.command.build_scripts: 49. Build the scripts of a package
* distutils.command.check: 4a. Check the meta-data of a package
* distutils.command.clean: 4b. Clean a package build area
* distutils.command.config: 4c. Perform package configuration
* distutils.command.install: 4d. Install a package
* distutils.command.install_data: 4e. Install data files from a package
* distutils.command.install_headers: 4f. Install C/C++ header files from a package
* distutils.command.install_lib: 50. Install library files from a package
* distutils.command.install_scripts: 51. Install script files from a package
* distutils.command.register: 52. Register a module with the Python Package Index
* distutils.command.sdist: 53. Build a source distribution
* distutils.core: 54. The core Distutils functionality
* distutils.cygwinccompiler: 55.
* distutils.debug: 56. Provides the debug flag for distutils
* distutils.dep_util: 57. Utility functions for simple dependency checking
* distutils.dir_util: 58. Utility functions for operating on directories and
                        directory trees
* distutils.dist: 59. Provides the Distribution class, which
                        represents the module distribution being
                        built/installed/distributed
* distutils.errors: 5a. Provides standard distutils exceptions
* distutils.extension: 5b. Provides the Extension class, used to describe
                        C/C++ extension modules in setup scripts
* distutils.fancy_getopt: 5c. Additional getopt functionality
* distutils.file_util: 5d. Utility functions for operating on single files
* distutils.filelist: 5e. The FileList class, used for poking about the
                        file system and building lists of files.
* distutils.log: 5f. A simple logging mechanism, :pep:‘282‘-style
* distutils.msvccompiler: 60. Microsoft Compiler
* distutils.spawn: 61. Provides the spawn() function
* distutils.sysconfig: 62. Low-level access to configuration information of the
                        Python interpreter.
* distutils.text_file: 63. Provides the TextFile class, a simple interface
                        to text files
* distutils.unixccompiler: 64. UNIX C Compiler
* distutils.util: 65. Miscellaneous other utility functions
* distutils.version: 66. Implements classes that represent module version
                        numbers.
* doctest: 67. Test pieces of code within docstrings.
* dummy_threading: 68. Drop-in replacement for the threading module.
* email: 69. Package supporting the parsing,
                        manipulating, and generating email messages.
* email.charset: 6a. Character Sets
* email.contentmanager: 6b. Storing and Retrieving Content from MIME Parts
* email.encoders: 6c. Encoders for email message payloads.
* email.errors: 6d. The exception classes used by the email package.
* email.generator: 6e. Generate flat text email messages from a message
                        structure.
* email.header: 6f. Representing non-ASCII headers
* email.headerregistry: 70. Automatic Parsing of headers based on the field name
* email.iterators: 71. Iterate over a message object tree.
* email.message: 72. The base class representing email messages.
* email.mime: 73. Build MIME messages.
* email.parser: 74. Parse flat text email messages to produce a message
                        object structure.
* email.policy: 75. Controlling the parsing and generating of messages
* email.utils: 76. Miscellaneous email package utilities.
* encodings.idna: 77. Internationalized Domain Names implementation
* encodings.mbcs: 78. Windows ANSI codepage
* encodings.utf_8_sig: 79. UTF-8 codec with BOM signature
* ensurepip: 7a. Bootstrapping the "pip" installer into an existing
                        Python installation or virtual environment.
* enum: 7b. Implementation of an enumeration class.
* errno: 7c. Standard errno system symbols.
* faulthandler: 7d. Dump the Python traceback.
* fcntl: 7e. The fcntl() and ioctl() system calls.
* filecmp: 7f. Compare files efficiently.
* fileinput: 80. Loop over standard input or a list of files.
* fnmatch: 81. Unix shell style filename pattern matching.
* formatter: 82. Generic output formatter and device interface.
* fractions: 83. Rational numbers.
* ftplib: 84. FTP protocol client (requires sockets).
* functools: 85. Higher-order functions and operations on callable
                        objects.
* gc: 86. Interface to the cycle-detecting garbage collector.
* getopt: 87. Portable parser for command line options; support both
                        short and long option names.
* getpass: 88. Portable reading of passwords and retrieval of the
                        userid.
* gettext: 89. Multilingual internationalization services.
* glob: 8a. Unix shell style pathname pattern expansion.
* grp: 8b. The group database (getgrnam() and friends).
* gzip: 8c. Interfaces for gzip compression and decompression
                        using file objects.
* hashlib: 8d. Secure hash and message digest algorithms.
* heapq: 8e. Heap queue algorithm (a.k.a. priority queue).
* hmac: 8f. Keyed-Hashing for Message Authentication (HMAC)
                        implementation
* html: 90. Helpers for manipulating HTML.
* html.entities: 91. Definitions of HTML general entities.
* html.parser: 92. A simple parser that can handle HTML and XHTML.
* http: 93. HTTP status codes and messages
* http.client: 94. HTTP and HTTPS protocol client (requires sockets).
* http.cookiejar: 95. Classes for automatic handling of HTTP cookies.
* http.cookies: 96. Support for HTTP state management (cookies).
* http.server: 97. HTTP server and request handlers.
* imaplib: 98. IMAP4 protocol client (requires sockets).
* imghdr: 99. Determine the type of image contained in a file or
                        byte stream.
* imp: 9a. Access the implementation of the import statement.
* importlib: 9b. The implementation of the import machinery.
* importlib.abc: 9c. Abstract base classes related to import
* importlib.machinery: 9d. Importers and path hooks
* importlib.metadata: 9e. The implementation of the importlib metadata.
* importlib.resources: 9f. Package resource reading, opening, and
                        access
* importlib.util: a0. Utility code for importers
* inspect: a1. Extract information and source code from live objects.
* io: a2. Core tools for working with streams.
* ipaddress: a3. IPv4/IPv6 manipulation library.
* itertools: a4. Functions creating iterators for efficient looping.
* json: a5. Encode and decode the JSON format.
* json.tool: a6. A command line to validate and pretty-print JSON.
* keyword: a7. Test whether a string is a keyword in Python.
* lib2to3: a8. The 2to3 library
* linecache: a9. Provides random access to individual lines from text
                        files.
* locale: aa. Internationalization services.
* logging: ab. Flexible event logging system for applications.
* logging.config: ac. Configuration of the logging module.
* logging.handlers: ad. Handlers for the logging module.
* lzma: ae. A Python wrapper for the liblzma compression library.
* mailbox: af. Manipulate mailboxes in various formats
* mailcap: b0. Mailcap file handling.
* marshal: b1. Convert Python objects to streams of bytes and back
                        (with different constraints).
* math: b2. Mathematical functions (sin() etc.).
* mimetypes: b3. Mapping of filename extensions to MIME types.
* mmap: b4. Interface to memory-mapped files for Unix and Windows.
* modulefinder: b5. Find modules used by a script.
* msilib: b6. Creation of Microsoft Installer files, and CAB
                        files.
* msvcrt: b7. Miscellaneous useful routines from the MS VC++
                        runtime.
* multiprocessing: b8. Process-based parallelism.
* multiprocessing.connection: b9. API for dealing with sockets.
* multiprocessing.dummy: ba. Dumb wrapper around threading.
* multiprocessing.managers: bb. Share data between process with shared objects.
* multiprocessing.pool: bc. Create pools of processes.
* multiprocessing.shared_memory: bd. Provides shared memory for direct access
                                 across processes.
* multiprocessing.sharedctypes: be. Allocate ctypes objects from shared memory.
* netrc: bf. Loading of .netrc files.
* nis: c0. Interface to Sun’s NIS (Yellow Pages) library.
* nntplib: c1. NNTP protocol client (requires sockets).
* numbers: c2. Numeric abstract base classes (Complex,
                        Real, Integral, etc.).
* operator: c3. Functions corresponding to the standard operators.
* optparse: c4. Command-line option parsing library.
* os: c5. Miscellaneous operating system interfaces.
* os.path: c6. Operations on pathnames.
* ossaudiodev: c7. Access to OSS-compatible audio devices.
* parser: c8. Access parse trees for Python source code.
* pathlib: c9. Object-oriented filesystem paths
* pdb: ca. The Python debugger for interactive interpreters.
* pickle: cb. Convert Python objects to streams of bytes and back.
* pickletools: cc. Contains extensive comments about the pickle protocols
                        and pickle-machine opcodes, as well as some
                        useful functions.
* pipes: cd. A Python interface to Unix shell pipelines.
* pkgutil: ce. Utilities for the import system.
* platform: cf. Retrieves as much platform identifying data as
                        possible.
* plistlib: d0. Generate and parse Mac OS X plist files.
* poplib: d1. POP3 protocol client (requires sockets).
* posix: d2. The most common POSIX system calls (normally used via
                        module os).
* pprint: d3. Data pretty printer.
* profile: d4. Python source profiler.
* pstats: d5. Statistics object for use with the profiler.
* pty: d6. Pseudo-Terminal Handling for Linux.
* pwd: d7. The password database (getpwnam() and friends).
* py_compile: d8. Generate byte-code files from Python source files.
* pyclbr: d9. Supports information extraction for a Python module
                        browser.
* pydoc: da. Documentation generator and online help system.
* queue: db. A synchronized queue class.
* quopri: dc. Encode and decode files using the MIME quoted-
                        printable encoding.
* random: dd. Generate pseudo-random numbers with various common
                        distributions.
* re: de. Regular expression operations.
* readline: df. GNU readline support for Python.
* reprlib: e0. Alternate repr() implementation with size limits.
* resource: e1. An interface to provide resource usage information on
                        the current process.
* rlcompleter: e2. Python identifier completion, suitable for the
                        GNU readline library.
* runpy: e3. Locate and run Python modules without importing them
                        first.
* sched: e4. General purpose event scheduler.
* secrets: e5. Generate secure random numbers for managing secrets.
* select: e6. Wait for I/O completion on multiple streams.
* selectors: e7. High-level I/O multiplexing.
* shelve: e8. Python object persistence.
* shlex: e9. Simple lexical analysis for Unix shell-like languages.
* shutil: ea. High-level file operations, including copying.
* signal: eb. Set handlers for asynchronous events.
* site: ec. Module responsible for site-specific configuration.
* smtpd: ed. A SMTP server implementation in Python.
* smtplib: ee. SMTP protocol client (requires sockets).
* sndhdr: ef. Determine type of a sound file.
* socket: f0. Low-level networking interface.
* socketserver: f1. A framework for network servers.
* spwd: f2. The shadow password database (getspnam() and friends).
* sqlite3: f3. A DB-API 2.0 implementation using SQLite 3.x.
* ssl: f4. TLS/SSL wrapper for socket objects
* stat: f5. Utilities for interpreting the results of
                        os.stat(), os.lstat() and os.fstat().
* statistics: f6. Mathematical statistics functions
* string: f7. Common string operations.
* stringprep: f8. String preparation, as per RFC 3453
* struct: f9. Interpret bytes as packed binary data.
* subprocess: fa. Subprocess management.
* sunau: fb. Provide an interface to the Sun AU sound format.
* symbol: fc. Constants representing internal nodes of the parse
                        tree.
* symtable: fd. Interface to the compiler’s internal symbol tables.
* sys: fe. Access system-specific parameters and functions.
* sysconfig: ff. Python’s configuration information
* syslog: 100. An interface to the Unix syslog library routines.
* tabnanny: 101. Tool for detecting white space related problems in
                        Python source files in a directory tree.
* tarfile: 102. Read and write tar-format archive files.
* telnetlib: 103. Telnet client class.
* tempfile: 104. Generate temporary files and directories.
* termios: 105. POSIX style tty control.
* test: 106. Regression tests package containing the testing suite
                        for Python.
* test.support: 107. Support for Python’s regression test suite.
* test.support.script_helper: 108. Support for Python’s script execution tests.
* textwrap: 109. Text wrapping and filling
* threading: 10a. Thread-based parallelism.
* time: 10b. Time access and conversions.
* timeit: 10c. Measure the execution time of small code snippets.
* tkinter: 10d. Interface to Tcl/Tk for graphical user interfaces
* tkinter.scrolledtext: 10e. Text widget with a vertical scroll bar.
* tkinter.tix: 10f. Tk Extension Widgets for Tkinter
* tkinter.ttk: 110. Tk themed widget set
* token: 111. Constants representing terminal nodes of the parse
                        tree.
* tokenize: 112. Lexical scanner for Python source code.
* trace: 113. Trace or track Python statement execution.
* traceback: 114. Print or retrieve a stack traceback.
* tracemalloc: 115. Trace memory allocations.
* tty: 116. Utility functions that perform common terminal control
                        operations.
* turtle: 117. An educational framework for simple graphics
                        applications
* turtledemo: 118. A viewer for example turtle scripts
* types: 119. Names for built-in types.
* typing: 11a. Support for type hints (see :pep:‘484‘).
* unicodedata: 11b. Access the Unicode Database.
* unittest: 11c. Unit testing framework for Python.
* unittest.mock: 11d. Mock object library.
* urllib: 11e.
* urllib.error: 11f. Exception classes raised by urllib.request.
* urllib.parse: 120. Parse URLs into or assemble them from components.
* urllib.request: 121. Extensible library for opening URLs.
* urllib.response: 122. Response classes used by urllib.
* urllib.robotparser: 123. Load a robots.txt file and answer questions about
                        fetchability of other URLs.
* uu: 124. Encode and decode files in uuencode format.
* uuid: 125. UUID objects (universally unique identifiers)
                        according to RFC 4122
* venv: 126. Creation of virtual environments.
* warnings: 127. Issue warning messages and control their disposition.
* wave: 128. Provide an interface to the WAV sound format.
* weakref: 129. Support for weak references and weak dictionaries.
* webbrowser: 12a. Easy-to-use controller for Web browsers.
* winreg: 12b. Routines and objects for manipulating the Windows
                        registry.
* winsound: 12c. Access to the sound-playing machinery for Windows.
* wsgiref: 12d. WSGI Utilities and Reference Implementation.
* wsgiref.handlers: 12e. WSGI server/gateway base classes.
* wsgiref.headers: 12f. WSGI response header tools.
* wsgiref.simple_server: 130. A simple WSGI HTTP server.
* wsgiref.util: 131. WSGI environment utilities.
* wsgiref.validate: 132. WSGI conformance checker.
* xdrlib: 133. Encoders and decoders for the External Data
                        Representation (XDR).
* xml: 134. Package containing XML processing modules
* xml.dom: 135. Document Object Model API for Python.
* xml.dom.minidom: 136. Minimal Document Object Model (DOM) implementation.
* xml.dom.pulldom: 137. Support for building partial DOM trees from SAX
                        events.
* xml.etree.ElementTree: 138. Implementation of the ElementTree API.
* xml.parsers.expat: 139. An interface to the Expat non-validating XML parser.
* xml.parsers.expat.errors: 13a.
* xml.parsers.expat.model: 13b.
* xml.sax: 13c. Package containing SAX2 base classes and convenience
                        functions.
* xml.sax.handler: 13d. Base classes for SAX event handlers.
* xml.sax.saxutils: 13e. Convenience functions and classes for use with SAX.
* xml.sax.xmlreader: 13f. Interface which SAX-compliant XML parsers must
                        implement.
* xmlrpc.client: 140. XML-RPC client access.
* xmlrpc.server: 141. Basic XML-RPC server implementations.
* zipapp: 142. Manage executable Python zip archives
* zipfile: 143. Read and write ZIP-format archive files.
* zipimport: 144. Support for importing Python modules from ZIP
                        archives.
* zlib: 145. Low-level interface to compression and decompression
                        routines compatible with gzip.


File: python.info,  Node: 索引,  Prev: Python 模組索引,  Up: Top

索引
****

[index]
* Menu:

* ! (exclamation); in a command interpreter: Cmd Objects.    (line   27)
* ! (exclamation); in curses module:     curses ascii --- Utilities for ASCII characters.
                                                             (line  226)
* ! (exclamation); in formatted string literal: String literal concatenation.
                                                             (line   24)
* ! (exclamation); in glob-style wildcards: glob --- Unix style pathname pattern expansion.
                                                             (line   10)
* ! (exclamation); in glob-style wildcards <1>: fnmatch --- Unix filename pattern matching.
                                                             (line   15)
* ! (exclamation); in string formatting: Format String Syntax.
                                                             (line   13)
* ! (exclamation); in struct format strings: Byte Order Size and Alignment.
                                                             (line   10)
* ! (pdb command):                       Debugger Commands.  (line  311)
* " (double quote); string literal:      Literals.           (line    8)
* """; string literal:                   String and Bytes literals.
                                                             (line   36)
* # (hash); comment:                     一個非正式的 Python 簡介.
                                                             (line   12)
* # (hash); comment <1>:                 Comments.           (line    6)
* # (hash); comment <2>:                 site --- Site-specific configuration hook.
                                                             (line   44)
* # (hash); in doctests:                 Option Flags.       (line  183)
* # (hash); in printf-style formatting:  printf-style String Formatting.
                                                             (line   66)
* # (hash); in printf-style formatting <1>: printf-style Bytes Formatting.
                                                             (line   63)
* # (hash); in regular expressions:      Module Contents.    (line  123)
* # (hash); in string formatting:        Format Specification Mini-Language.
                                                             (line   87)
* # (hash); source encoding declaration: Encoding declarations.
                                                             (line    6)
* $ (dollar); environment variables expansion: os path --- Common pathname manipulations.
                                                             (line  157)
* $ (dollar); in regular expressions:    Regular Expression Syntax.
                                                             (line   57)
* $ (dollar); in template strings:       Template strings.   (line   13)
* $ (dollar); interpolation in configuration files: Interpolation of values.
                                                             (line   40)
* % (percent); datetime format:          timezone Objects.   (line   71)
* % (percent); datetime format <1>:      Functions<2>.       (line  230)
* % (percent); datetime format <2>:      Functions<2>.       (line  362)
* % (percent); environment variables expansion (Windows): os path --- Common pathname manipulations.
                                                             (line  157)
* % (percent); environment variables expansion (Windows) <1>: Functions<11>.
                                                             (line  233)
* % (percent); interpolation in configuration files: Interpolation of values.
                                                             (line   10)
* % (percent); printf-style formatting:  printf-style String Formatting.
                                                             (line    6)
* % (percent); printf-style formatting <1>: printf-style Bytes Formatting.
                                                             (line    6)
* %=; augmented assignment:              Augmented assignment statements.
                                                             (line    6)
* &=; augmented assignment:              Augmented assignment statements.
                                                             (line    6)
* ’ (single quote); string literal:      Literals.           (line    8)
* ’’’; string literal:                   String and Bytes literals.
                                                             (line   36)
* () (parentheses); call:                Slicings.           (line   38)
* () (parentheses); class definition:    Class definitions.  (line    6)
* () (parentheses); function definition: Function definitions.
                                                             (line    6)
* () (parentheses); generator expression: Generator expressions.
                                                             (line    6)
* () (parentheses); in assignment target list: Assignment statements.
                                                             (line   35)
* () (parentheses); in printf-style formatting: printf-style String Formatting.
                                                             (line   26)
* () (parentheses); in printf-style formatting <1>: printf-style Bytes Formatting.
                                                             (line   23)
* () (parentheses); in regular expressions: Regular Expression Syntax.
                                                             (line  198)
* () (parentheses); tuple display:       Parenthesized forms.
                                                             (line    6)
* (?!; in regular expressions:           Regular Expression Syntax.
                                                             (line  315)
* (?#; in regular expressions:           Regular Expression Syntax.
                                                             (line  304)
* (?; in regular expressions:            Regular Expression Syntax.
                                                             (line  207)
* (?;; in regular expressions:           Regular Expression Syntax.
                                                             (line  231)
* (?<!; in regular expressions:          Regular Expression Syntax.
                                                             (line  348)
* (?<=; in regular expressions:          Regular Expression Syntax.
                                                             (line  321)
* (?=; in regular expressions:           Regular Expression Syntax.
                                                             (line  308)
* (?P<; in regular expressions:          Regular Expression Syntax.
                                                             (line  266)
* (?P=; in regular expressions:          Regular Expression Syntax.
                                                             (line  299)
* * (asterisk); function definition:     Function definitions.
                                                             (line   78)
* * (asterisk); import statement:        The import statement.
                                                             (line   79)
* * (asterisk); in argparse module:      nargs.              (line   56)
* * (asterisk); in assignment target list: Assignment statements.
                                                             (line   35)
* * (asterisk); in AST grammar:          Node classes.       (line   22)
* * (asterisk); in expression lists:     Expression lists.   (line   16)
* * (asterisk); in function calls:       Arbitrary Argument Lists.
                                                             (line    6)
* * (asterisk); in function calls <1>:   Calls.              (line   74)
* * (asterisk); in glob-style wildcards: glob --- Unix style pathname pattern expansion.
                                                             (line   10)
* * (asterisk); in glob-style wildcards <1>: fnmatch --- Unix filename pattern matching.
                                                             (line   15)
* * (asterisk); in printf-style formatting: printf-style String Formatting.
                                                             (line   26)
* * (asterisk); in printf-style formatting <1>: printf-style Bytes Formatting.
                                                             (line   23)
* * (asterisk); in regular expressions:  Regular Expression Syntax.
                                                             (line   68)
* **; function definition:               Function definitions.
                                                             (line   78)
* **; in dictionary displays:            Dictionary displays.
                                                             (line   23)
* **; in function calls:                 Unpacking Argument Lists.
                                                             (line   19)
* **; in function calls <1>:             Calls.              (line  100)
* **; in glob-style wildcards:           glob --- Unix style pathname pattern expansion.
                                                             (line   41)
* **=; augmented assignment:             Augmented assignment statements.
                                                             (line    6)
* *=; augmented assignment:              Augmented assignment statements.
                                                             (line    6)
* *?; in regular expressions:            Regular Expression Syntax.
                                                             (line   85)
* + (plus); binary operator:             Binary arithmetic operations.
                                                             (line   60)
* + (plus); binary operator <1>:         Numeric Types --- int float complex.
                                                             (line   27)
* + (plus); in argparse module:          nargs.              (line   68)
* + (plus); in doctests:                 Option Flags.       (line  183)
* + (plus); in printf-style formatting:  printf-style String Formatting.
                                                             (line   66)
* + (plus); in printf-style formatting <1>: printf-style Bytes Formatting.
                                                             (line   63)
* + (plus); in regular expressions:      Regular Expression Syntax.
                                                             (line   74)
* + (plus); in string formatting:        Format Specification Mini-Language.
                                                             (line   71)
* + (plus); unary operator:              Unary arithmetic and bitwise operations.
                                                             (line   13)
* + (plus); unary operator <1>:          Numeric Types --- int float complex.
                                                             (line   27)
* +=; augmented assignment:              Augmented assignment statements.
                                                             (line    6)
* +?; in regular expressions:            Regular Expression Syntax.
                                                             (line   85)
* , (comma):                             Parenthesized forms.
                                                             (line   20)
* , (comma); argument list:              Slicings.           (line   38)
* , (comma); expression list:            List displays.      (line    6)
* , (comma); expression list <1>:        Set displays.       (line    6)
* , (comma); expression list <2>:        Expression lists.   (line    6)
* , (comma); expression list <3>:        The assert statement.
                                                             (line    6)
* , (comma); expression list <4>:        Class definitions.  (line    6)
* , (comma); identifier list:            The global statement.
                                                             (line    6)
* , (comma); identifier list <1>:        The nonlocal statement.
                                                             (line    6)
* , (comma); import statement:           The import statement.
                                                             (line    6)
* , (comma); in dictionary displays:     Dictionary displays.
                                                             (line    6)
* , (comma); in string formatting:       Format Specification Mini-Language.
                                                             (line   99)
* , (comma); in target list:             Assignment statements.
                                                             (line   35)
* , (comma); parameter list:             Function definitions.
                                                             (line    6)
* , (comma); slicing:                    Slicings.           (line    6)
* , (comma); with statement:             The with statement. (line    6)
* - (minus); binary operator:            Binary arithmetic operations.
                                                             (line   66)
* - (minus); binary operator <1>:        Numeric Types --- int float complex.
                                                             (line   27)
* - (minus); in doctests:                Option Flags.       (line  182)
* - (minus); in glob-style wildcards:    glob --- Unix style pathname pattern expansion.
                                                             (line   10)
* - (minus); in glob-style wildcards <1>: fnmatch --- Unix filename pattern matching.
                                                             (line   15)
* - (minus); in printf-style formatting: printf-style String Formatting.
                                                             (line   66)
* - (minus); in printf-style formatting <1>: printf-style Bytes Formatting.
                                                             (line   63)
* - (minus); in regular expressions:     Regular Expression Syntax.
                                                             (line  143)
* - (minus); in string formatting:       Format Specification Mini-Language.
                                                             (line   71)
* - (minus); unary operator:             Unary arithmetic and bitwise operations.
                                                             (line   10)
* - (minus); unary operator <1>:         Numeric Types --- int float complex.
                                                             (line   27)
* -=; augmented assignment:              Augmented assignment statements.
                                                             (line    6)
* ->; function annotations:              Function Annotations.
                                                             (line    6)
* ->; function annotations <1>:          Function definitions.
                                                             (line   94)
* . (dot); attribute reference:          Attribute references.
                                                             (line    6)
* . (dot); in glob-style wildcards:      glob --- Unix style pathname pattern expansion.
                                                             (line   10)
* . (dot); in numeric literal:           Integer literals.   (line   40)
* . (dot); in pathnames:                 Miscellaneous System Information.
                                                             (line   81)
* . (dot); in pathnames <1>:             Miscellaneous System Information.
                                                             (line  109)
* . (dot); in printf-style formatting:   printf-style String Formatting.
                                                             (line   26)
* . (dot); in printf-style formatting <1>: printf-style Bytes Formatting.
                                                             (line   23)
* . (dot); in regular expressions:       Regular Expression Syntax.
                                                             (line   46)
* . (dot); in string formatting:         Format String Syntax.
                                                             (line   13)
* . (dot); in Tkinter:                   A Very Quick Look at Tcl/Tk.
                                                             (line   44)
* ...:                                   Glossary.           (line   10)
* ...; ellipsis literal:                 The standard type hierarchy.
                                                             (line   41)
* ...; ellipsis literal <1>:             內建常數.           (line   52)
* ...; ellipsis literal <2>:             The Null Object.    (line   12)
* ...; in doctests:                      Option Flags.       (line   49)
* ...; interpreter prompt:               How are Docstring Examples Recognized?.
                                                             (line   26)
* ...; interpreter prompt <1>:           sys --- System-specific parameters and functions.
                                                             (line 1189)
* ...; placeholder:                      textwrap --- Text wrapping and filling.
                                                             (line  266)
* ...; placeholder <1>:                  pprint --- Data pretty printer.
                                                             (line   27)
* ...; placeholder <2>:                  reprlib --- Alternate repr implementation.
                                                             (line   41)
* ..; in pathnames:                      Miscellaneous System Information.
                                                             (line   87)
* .ini; file:                            configparser --- Configuration file parser.
                                                             (line    8)
* .pdbrc; file:                          Debugger Commands.  (line   37)
* / (slash); function definition:        Function definitions.
                                                             (line   78)
* / (slash); in pathnames:               Miscellaneous System Information.
                                                             (line   93)
* / (slash); in pathnames <1>:           Miscellaneous System Information.
                                                             (line  102)
* //=; augmented assignment:             Augmented assignment statements.
                                                             (line    6)
* /=; augmented assignment:              Augmented assignment statements.
                                                             (line    6)
* 0b; integer literal:                   Numeric literals.   (line   14)
* 0o; integer literal:                   Numeric literals.   (line   14)
* 0x; integer literal:                   Numeric literals.   (line   14)
* 2-digit years:                         time --- Time access and conversions.
                                                             (line   35)
* 2to3:                                  Glossary.           (line   23)
* ; (colon); annotated variable:         Annotated assignment statements.
                                                             (line    6)
* ; (colon); compound statement:         The if statement.   (line    6)
* ; (colon); compound statement <1>:     The while statement.
                                                             (line    6)
* ; (colon); compound statement <2>:     The for statement.  (line    6)
* ; (colon); compound statement <3>:     The try statement.  (line    6)
* ; (colon); compound statement <4>:     The with statement. (line    6)
* ; (colon); compound statement <5>:     Function definitions.
                                                             (line    6)
* ; (colon); compound statement <6>:     Class definitions.  (line    6)
* ; (colon); function annotations:       Function Annotations.
                                                             (line    6)
* ; (colon); function annotations <1>:   Function definitions.
                                                             (line   94)
* ; (colon); in dictionary expressions:  Dictionary displays.
                                                             (line    6)
* ; (colon); in formatted string literal: String literal concatenation.
                                                             (line   24)
* ; (colon); in SQL statements:          Cursor Objects.     (line   11)
* ; (colon); in string formatting:       Format String Syntax.
                                                             (line   13)
* ; (colon); lambda expression:          Lambdas.            (line    6)
* ; (colon); path separator (POSIX):     Miscellaneous System Information.
                                                             (line  115)
* ; (colon); slicing:                    Slicings.           (line    6)
* ; (semicolon):                         Compound statements.
                                                             (line   18)
* ; (semicolon) <1>:                     Miscellaneous System Information.
                                                             (line  115)
* < (less); in string formatting:        Format Specification Mini-Language.
                                                             (line   42)
* < (less); in struct format strings:    Byte Order Size and Alignment.
                                                             (line   10)
* <<=; augmented assignment:             Augmented assignment statements.
                                                             (line    6)
* <BLANKLINE>:                           Option Flags.       (line   30)
* = (equals); assignment statement:      Assignment statements.
                                                             (line    6)
* = (equals); class definition:          Metaclasses.        (line    6)
* = (equals); for help in debugging using string literals: String literal concatenation.
                                                             (line   23)
* = (equals); function definition:       Function definitions.
                                                             (line   53)
* = (equals); in function calls:         Slicings.           (line   37)
* = (equals); in string formatting:      Format Specification Mini-Language.
                                                             (line   42)
* = (equals); in struct format strings:  Byte Order Size and Alignment.
                                                             (line   10)
* > (greater); in string formatting:     Format Specification Mini-Language.
                                                             (line   42)
* > (greater); in struct format strings: Byte Order Size and Alignment.
                                                             (line   10)
* >>=; augmented assignment:             Augmented assignment statements.
                                                             (line    6)
* >>>:                                   Glossary.           (line    6)
* >>>; interpreter prompt:               How are Docstring Examples Recognized?.
                                                             (line   26)
* >>>; interpreter prompt <1>:           sys --- System-specific parameters and functions.
                                                             (line 1189)
* ? (question mark); in a command interpreter: Cmd Objects.  (line   27)
* ? (question mark); in argparse module: nargs.              (line   23)
* ? (question mark); in AST grammar:     Node classes.       (line   22)
* ? (question mark); in glob-style wildcards: glob --- Unix style pathname pattern expansion.
                                                             (line   10)
* ? (question mark); in glob-style wildcards <1>: fnmatch --- Unix filename pattern matching.
                                                             (line   15)
* ? (question mark); in regular expressions: Regular Expression Syntax.
                                                             (line   80)
* ? (question mark); in SQL statements:  Cursor Objects.     (line   11)
* ? (question mark); in struct format strings: Format Characters.
                                                             (line   86)
* ? (question mark); in struct format strings <1>: Format Characters.
                                                             (line  161)
* ? (question mark); replacement character: Error Handlers.  (line   28)
* ??; in regular expressions:            Regular Expression Syntax.
                                                             (line   85)
* @ (at); class definition:              Class definitions.  (line   44)
* @ (at); function definition:           Function definitions.
                                                             (line   33)
* @ (at); in struct format strings:      Byte Order Size and Alignment.
                                                             (line   10)
* [] (square brackets); in assignment target list: Assignment statements.
                                                             (line   35)
* [] (square brackets); in glob-style wildcards: glob --- Unix style pathname pattern expansion.
                                                             (line   10)
* [] (square brackets); in glob-style wildcards <1>: fnmatch --- Unix filename pattern matching.
                                                             (line   15)
* [] (square brackets); in regular expressions: Regular Expression Syntax.
                                                             (line  136)
* [] (square brackets); in string formatting: Format String Syntax.
                                                             (line   13)
* [] (square brackets); list expression: List displays.      (line    6)
* [] (square brackets); subscription:    Subscriptions.      (line    6)
* \ (backslash); escape sequence:        String and Bytes literals.
                                                             (line   72)
* \ (backslash); escape sequence <1>:    Error Handlers.     (line   28)
* \ (backslash); in pathnames (Windows): Miscellaneous System Information.
                                                             (line   93)
* \ (backslash); in regular expressions: Regular Expression Syntax.
                                                             (line  121)
* \ (backslash); in regular expressions <1>: Regular Expression Syntax.
                                                             (line  155)
* \ (backslash); in regular expressions <2>: Regular Expression Syntax.
                                                             (line  372)
* \a; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \A; in regular expressions:            Regular Expression Syntax.
                                                             (line  384)
* \a; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* \b; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \b; in regular expressions:            Regular Expression Syntax.
                                                             (line  388)
* \B; in regular expressions:            Regular Expression Syntax.
                                                             (line  405)
* \b; in regular expressions <1>:        Regular Expression Syntax.
                                                             (line  484)
* \d; in regular expressions:            Regular Expression Syntax.
                                                             (line  416)
* \D; in regular expressions:            Regular Expression Syntax.
                                                             (line  429)
* \f; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \f; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* \g; in regular expressions:            Module Contents.    (line  282)
* \n; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \N; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \N; escape sequence <1>:               Error Handlers.     (line   28)
* \n; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* \N; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* \r; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \r; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* \s; in regular expressions:            Regular Expression Syntax.
                                                             (line  435)
* \S; in regular expressions:            Regular Expression Syntax.
                                                             (line  450)
* \t; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \t; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* \u; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \U; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \u; escape sequence <1>:               Error Handlers.     (line   28)
* \U; escape sequence <1>:               Error Handlers.     (line   28)
* \u; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* \U; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* \v; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \v; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* \w; in regular expressions:            Regular Expression Syntax.
                                                             (line  456)
* \W; in regular expressions:            Regular Expression Syntax.
                                                             (line  472)
* \x; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \x; escape sequence <1>:               Error Handlers.     (line   28)
* \x; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* \Z; in regular expressions:            Regular Expression Syntax.
                                                             (line  480)
* \\; escape sequence:                   String and Bytes literals.
                                                             (line   72)
* \\; in regular expressions:            Regular Expression Syntax.
                                                             (line  484)
* ^ (caret); in curses module:           curses ascii --- Utilities for ASCII characters.
                                                             (line  226)
* ^ (caret); in regular expressions:     Regular Expression Syntax.
                                                             (line   52)
* ^ (caret); in regular expressions <1>: Regular Expression Syntax.
                                                             (line  160)
* ^ (caret); in string formatting:       Format Specification Mini-Language.
                                                             (line   42)
* ^ (caret); marker:                     What About Exceptions?.
                                                             (line   93)
* ^ (caret); marker <1>:                 traceback --- Print or retrieve a stack traceback.
                                                             (line   46)
* ^=; augmented assignment:              Augmented assignment statements.
                                                             (line    6)
* _ (underscore); gettext:               GNU gettext API.    (line   42)
* _ (underscore); in numeric literal:    Numeric literals.   (line   13)
* _ (underscore); in numeric literal <1>: Integer literals.  (line   39)
* _ (underscore); in string formatting:  Format Specification Mini-Language.
                                                             (line  105)
* _, identifiers:                        Keywords.           (line   18)
* _anonymous_ (ctypes.Structure 的屬性): Structured data types.
                                                             (line   74)
* _asdict() (collections.somenamedtuple 的方法): namedtuple Factory Function for Tuples with Named Fields.
                                                             (line  107)
* _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_type_cache() (於 sys 模組中):   sys --- System-specific parameters and functions.
                                                             (line  158)
* _current_frames() (於 sys 模組中):     sys --- System-specific parameters and functions.
                                                             (line  167)
* _debugmallocstats() (於 sys 模組中):   sys --- System-specific parameters and functions.
                                                             (line  224)
* _dummy_thread (模組):                  _dummy_thread --- Drop-in replacement for the _thread module.
                                                             (line    6)
* _enablelegacywindowsfsencoding() (於 sys 模組中): sys --- System-specific parameters and functions.
                                                             (line 1448)
* _exit() (於 os 模組中):                Process Management. (line  120)
* _fields (ast.AST 的屬性):              Node classes.       (line   22)
* _fields (collections.somenamedtuple 的屬性): namedtuple Factory Function for Tuples with Named Fields.
                                                             (line  137)
* _fields_ (ctypes.Structure 的屬性):    Structured data types.
                                                             (line   31)
* _field_defaults (collections.somenamedtuple 的屬性): namedtuple Factory Function for Tuples with Named Fields.
                                                             (line  150)
* _flush() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line  116)
* _frozen (C 型態):                      匯入模組<2>.        (line  257)
* _FuncPtr (ctypes 中的類別):            Foreign functions.  (line   12)
* _getframe() (於 sys 模組中):           sys --- System-specific parameters and functions.
                                                             (line  722)
* _getvalue() (multiprocessing.managers.BaseProxy 的方法): Proxy Objects.
                                                             (line  138)
* _get_child_mock() (unittest.mock.Mock 的方法): The Mock Class.
                                                             (line  286)
* _handle (ctypes.PyDLL 的屬性):         Loading shared libraries.
                                                             (line  145)
* _inittab (C 型態):                     匯入模組<2>.        (line  289)
* _length_ (ctypes.Array 的屬性):        Arrays and pointers.
                                                             (line   18)
* _make() (collections.somenamedtuple 的類別成員): namedtuple Factory Function for Tuples with Named Fields.
                                                             (line   98)
* _makeResult() (unittest.TextTestRunner 的方法): Loading and running tests.
                                                             (line  465)
* _name (ctypes.PyDLL 的屬性):           Loading shared libraries.
                                                             (line  149)
* _objects (ctypes._CData 的屬性):       Data types.         (line   83)
* _pack_ (ctypes.Structure 的屬性):      Structured data types.
                                                             (line   67)
* _parse() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   21)
* _Pointer (ctypes 中的類別):            Arrays and pointers.
                                                             (line   31)
* _PyBytes_Resize (C 函式):              Bytes Objects<2>.   (line  180)
* _PyCFunctionFast (C 型態):             通用物件結構.       (line  109)
* _PyCFunctionFastWithKeywords (C 型態): 通用物件結構.       (line  114)
* _PyImport_Fini (C 函式):               匯入模組<2>.        (line  235)
* _PyImport_Init (C 函式):               匯入模組<2>.        (line  227)
* _PyObject_FastCallDict (C 函式):       Object Protocol.    (line  400)
* _PyObject_New (C 函式):                Allocating Objects on the Heap.
                                                             (line    6)
* _PyObject_NewVar (C 函式):             Allocating Objects on the Heap.
                                                             (line    9)
* _PyObject_Vectorcall (C 函式):         Object Protocol.    (line  345)
* _PyTuple_Resize (C 函式):              元組（Tuple）物件.  (line   88)
* _Py_c_diff (C 函式):                   Complex Numbers as C Structures.
                                                             (line   27)
* _Py_c_neg (C 函式):                    Complex Numbers as C Structures.
                                                             (line   32)
* _Py_c_pow (C 函式):                    Complex Numbers as C Structures.
                                                             (line   51)
* _Py_c_prod (C 函式):                   Complex Numbers as C Structures.
                                                             (line   37)
* _Py_c_quot (C 函式):                   Complex Numbers as C Structures.
                                                             (line   42)
* _Py_c_sum (C 函式):                    Complex Numbers as C Structures.
                                                             (line   22)
* _Py_InitializeMain (C 函式):           Multi-Phase Initialization Private Provisional API.
                                                             (line   44)
* _Py_NoneStruct (C 變數):               Allocating Objects on the Heap.
                                                             (line   57)
* _Py_TPFLAGS_HAVE_VECTORCALL (內建變數): PyTypeObject Slots.
                                                             (line  626)
* _replace() (collections.somenamedtuple 的方法): namedtuple Factory Function for Tuples with Named Fields.
                                                             (line  125)
* _setroot() (xml.etree.ElementTree.ElementTree 的方法): ElementTree Objects.
                                                             (line   15)
* _SimpleCData (ctypes 中的類別):        Fundamental data types<2>.
                                                             (line    6)
* _structure() (於 email.iterators 模組中): email iterators Iterators.
                                                             (line   44)
* _thread (模組):                        _thread --- Low-level threading API.
                                                             (line    6)
* _type_ (ctypes.Array 的屬性):          Arrays and pointers.
                                                             (line   24)
* _type_ (ctypes._Pointer 的屬性):       Arrays and pointers.
                                                             (line   46)
* _write() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line  108)
* _xoptions (於 sys 模組中):             sys --- System-specific parameters and functions.
                                                             (line 1678)
* __, identifiers:                       Keywords.           (line   17)
* __abs__() (object 的方法):             Emulating numeric types.
                                                             (line  111)
* __abs__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line   73)
* __add__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __add__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line   78)
* __aenter__() (object 的方法):          Asynchronous Context Managers.
                                                             (line   12)
* __aexit__() (object 的方法):           Asynchronous Context Managers.
                                                             (line   17)
* __aiter__() (object 的方法):           Asynchronous Iterators.
                                                             (line   12)
* __all__:                               Importing * From a Package.
                                                             (line    6)
* __all__ (optional module attribute):   The import statement.
                                                             (line   83)
* __all__ (package variable):            匯入模組<2>.        (line    7)
* __and__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __and__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line   83)
* __anext__() (agen 的方法):             Asynchronous generator-iterator methods.
                                                             (line   10)
* __anext__() (object 的方法):           Asynchronous Iterators.
                                                             (line   16)
* __annotations__ (class attribute):     The standard type hierarchy.
                                                             (line  587)
* __annotations__ (function attribute):  The standard type hierarchy.
                                                             (line  303)
* __annotations__ (module attribute):    The standard type hierarchy.
                                                             (line  535)
* __await__() (object 的方法):           Awaitable Objects.  (line   15)
* __bases__ (class attribute):           The standard type hierarchy.
                                                             (line  587)
* __bases__ (class 的屬性):              Special Attributes. (line   19)
* __bool__() (object method):            Emulating container types.
                                                             (line   39)
* __bool__() (object 的方法):            Basic customization.
                                                             (line  302)
* __breakpointhook__ (於 sys 模組中):    sys --- System-specific parameters and functions.
                                                             (line  336)
* __bytes__() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  127)
* __bytes__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  138)
* __bytes__() (object 的方法):           Basic customization.
                                                             (line  144)
* __cached__:                            Import-related module attributes.
                                                             (line   69)
* __callback__ (weakref.ref 的屬性):     weakref --- Weak references.
                                                             (line  121)
* __call__() (email.headerregistry.HeaderRegistry 的方法): email headerregistry Custom Header Objects.
                                                             (line  389)
* __call__() (object method):            Calls.              (line  147)
* __call__() (object 的方法):            Emulating callable objects.
                                                             (line    6)
* __call__() (weakref.finalize 的方法):  weakref --- Weak references.
                                                             (line  251)
* __cause__ (exception attribute):       The raise statement.
                                                             (line   30)
* __cause__ (traceback.TracebackException 的屬性): TracebackException Objects.
                                                             (line   21)
* __ceil__() (fractions.Fraction 的方法): fractions --- Rational numbers.
                                                             (line  157)
* __ceil__() (object 的方法):            Emulating numeric types.
                                                             (line  141)
* __classcell__ (class namespace entry): Creating the class object.
                                                             (line    6)
* __class_getitem__() (object 的類別成員): Emulating generic types.
                                                             (line    9)
* __class__ (instance attribute):        The standard type hierarchy.
                                                             (line  624)
* __class__ (instance 的屬性):           Special Attributes. (line   15)
* __class__ (method cell):               Creating the class object.
                                                             (line    6)
* __class__ (module attribute):          Customizing module attribute access.
                                                             (line    6)
* __class__ (unittest.mock.Mock 的屬性): The Mock Class.     (line  537)
* __closure__ (function attribute):      The standard type hierarchy.
                                                             (line  303)
* __code__ (function attribute):         The standard type hierarchy.
                                                             (line  303)
* __code__ (function object attribute):  Code Objects.       (line    6)
* __complex__() (object 的方法):         Emulating numeric types.
                                                             (line  119)
* __concat__() (於 operator 模組中):     operator --- Standard operators as functions.
                                                             (line  172)
* __contains__() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  177)
* __contains__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  300)
* __contains__() (mailbox.Mailbox 的方法): Mailbox objects.  (line  195)
* __contains__() (object 的方法):        Emulating container types.
                                                             (line  148)
* __contains__() (於 operator 模組中):   operator --- Standard operators as functions.
                                                             (line  177)
* __context__ (exception attribute):     The raise statement.
                                                             (line   30)
* __context__ (traceback.TracebackException 的屬性): TracebackException Objects.
                                                             (line   25)
* __copy__() (copy protocol):            copy --- Shallow and deep copy operations.
                                                             (line   73)
* __debug__:                             The assert statement.
                                                             (line   21)
* __debug__ (內建變數):                  內建常數.           (line   58)
* __deepcopy__() (copy protocol):        copy --- Shallow and deep copy operations.
                                                             (line   73)
* __defaults__ (function attribute):     The standard type hierarchy.
                                                             (line  303)
* __delattr__() (object 的方法):         Customizing attribute access.
                                                             (line   68)
* __delete__() (object 的方法):          Implementing Descriptors.
                                                             (line   40)
* __delitem__() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  224)
* __delitem__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  334)
* __delitem__() (mailbox.Mailbox 的方法): Mailbox objects.   (line   76)
* __delitem__() (mailbox.MH 的方法):     MH.                 (line   76)
* __delitem__() (object 的方法):         Emulating container types.
                                                             (line  102)
* __delitem__() (於 operator 模組中):    operator --- Standard operators as functions.
                                                             (line  187)
* __del__() (io.IOBase 的方法):          I/O Base Classes.   (line  163)
* __del__() (object 的方法):             Basic customization.
                                                             (line   54)
* __dict__ (class attribute):            The standard type hierarchy.
                                                             (line  587)
* __dict__ (function attribute):         The standard type hierarchy.
                                                             (line  303)
* __dict__ (instance attribute):         The standard type hierarchy.
                                                             (line  624)
* __dict__ (module attribute):           The standard type hierarchy.
                                                             (line  546)
* __dict__ (module attribute) <1>:       模組物件模組.       (line   42)
* __dict__ (object 的屬性):              Special Attributes. (line   10)
* __dir__ (module attribute):            Customizing module attribute access.
                                                             (line    6)
* __dir__() (object 的方法):             Customizing attribute access.
                                                             (line   77)
* __dir__() (unittest.mock.Mock 的方法): The Mock Class.     (line  277)
* __displayhook__ (於 sys 模組中):       sys --- System-specific parameters and functions.
                                                             (line  336)
* __divmod__() (object 的方法):          Emulating numeric types.
                                                             (line   11)
* __doc__ (class attribute):             The standard type hierarchy.
                                                             (line  587)
* __doc__ (function attribute):          The standard type hierarchy.
                                                             (line  303)
* __doc__ (method attribute):            The standard type hierarchy.
                                                             (line  390)
* __doc__ (module attribute):            The standard type hierarchy.
                                                             (line  535)
* __doc__ (module attribute) <1>:        模組物件模組.       (line   23)
* __doc__ (types.ModuleType 的屬性):     Standard Interpreter Types.
                                                             (line  126)
* __enter__() (contextmanager 的方法):   Context Manager Types.
                                                             (line   12)
* __enter__() (object 的方法):           With Statement Context Managers.
                                                             (line   21)
* __enter__() (winreg.PyHKEY 的方法):    Registry Handle Objects.
                                                             (line   56)
* __eq__() (email.charset.Charset 的方法): email charset Representing character sets.
                                                             (line  150)
* __eq__() (email.header.Header 的方法): email header Internationalized headers.
                                                             (line  169)
* __eq__() (instance method):            Comparisons<2>.     (line   50)
* __eq__() (memoryview 的方法):          Memory Views.       (line  107)
* __eq__() (object 的方法):              Basic customization.
                                                             (line  173)
* __eq__() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line   24)
* __excepthook__ (於 sys 模組中):        sys --- System-specific parameters and functions.
                                                             (line  336)
* __exit__() (contextmanager 的方法):    Context Manager Types.
                                                             (line   32)
* __exit__() (object 的方法):            With Statement Context Managers.
                                                             (line   27)
* __exit__() (winreg.PyHKEY 的方法):     Registry Handle Objects.
                                                             (line   56)
* __file__:                              Import-related module attributes.
                                                             (line   67)
* __file__ (module attribute):           The standard type hierarchy.
                                                             (line  535)
* __file__ (module attribute) <1>:       模組物件模組.       (line   23)
* __file__ (module attribute) <2>:       模組物件模組.       (line   81)
* __float__() (object 的方法):           Emulating numeric types.
                                                             (line  119)
* __floordiv__() (object 的方法):        Emulating numeric types.
                                                             (line   11)
* __floordiv__() (於 operator 模組中):   operator --- Standard operators as functions.
                                                             (line   88)
* __floor__() (fractions.Fraction 的方法): fractions --- Rational numbers.
                                                             (line  147)
* __floor__() (object 的方法):           Emulating numeric types.
                                                             (line  141)
* __format__:                            內建函式.           (line  642)
* __format__() (datetime.date 的方法):   date Objects.       (line  274)
* __format__() (datetime.datetime 的方法): datetime Objects. (line  705)
* __format__() (datetime.time 的方法):   time Objects.       (line  215)
* __format__() (object 的方法):          Basic customization.
                                                             (line  150)
* __fspath__() (os.PathLike 的方法):     Process Parameters. (line  120)
* __func__ (method attribute):           The standard type hierarchy.
                                                             (line  390)
* __future__:                            Glossary.           (line  484)
* __future__ (模組):                     __future__ --- Future statement definitions.
                                                             (line    6)
* __future__; future statement:          Future statements.  (line    6)
* __getattribute__() (object 的方法):    Customizing attribute access.
                                                             (line   32)
* __getattr__ (module attribute):        Customizing module attribute access.
                                                             (line    6)
* __getattr__() (object 的方法):         Customizing attribute access.
                                                             (line   10)
* __getitem__() (email.headerregistry.HeaderRegistry 的方法): email headerregistry Custom Header Objects.
                                                             (line  384)
* __getitem__() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  187)
* __getitem__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  309)
* __getitem__() (mailbox.Mailbox 的方法): Mailbox objects.   (line  140)
* __getitem__() (mapping object method): Special method names.
                                                             (line    6)
* __getitem__() (object 的方法):         Emulating container types.
                                                             (line   76)
* __getitem__() (re.Match 的方法):       Match Objects.      (line   82)
* __getitem__() (於 operator 模組中):    operator --- Standard operators as functions.
                                                             (line  192)
* __getnewargs_ex__() (object 的方法):   Pickling Class Instances.
                                                             (line   29)
* __getnewargs__() (object 的方法):      Pickling Class Instances.
                                                             (line   47)
* __getstate__() (copy protocol):        Handling Stateful Objects.
                                                             (line    6)
* __getstate__() (object 的方法):        Pickling Class Instances.
                                                             (line   61)
* __get__() (object 的方法):             Implementing Descriptors.
                                                             (line   13)
* __ge__() (instance method):            Comparisons<2>.     (line   50)
* __ge__() (object 的方法):              Basic customization.
                                                             (line  173)
* __ge__() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line   24)
* __globals__ (function attribute):      The standard type hierarchy.
                                                             (line  303)
* __gt__() (instance method):            Comparisons<2>.     (line   50)
* __gt__() (object 的方法):              Basic customization.
                                                             (line  173)
* __gt__() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line   24)
* __hash__() (object 的方法):            Basic customization.
                                                             (line  221)
* __iadd__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __iadd__() (於 operator 模組中):       In-place Operators. (line   36)
* __iand__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __iand__() (於 operator 模組中):       In-place Operators. (line   41)
* __iconcat__() (於 operator 模組中):    In-place Operators. (line   46)
* __ifloordiv__() (object 的方法):       Emulating numeric types.
                                                             (line   77)
* __ifloordiv__() (於 operator 模組中):  In-place Operators. (line   52)
* __ilshift__() (object 的方法):         Emulating numeric types.
                                                             (line   77)
* __ilshift__() (於 operator 模組中):    In-place Operators. (line   57)
* __imatmul__() (object 的方法):         Emulating numeric types.
                                                             (line   77)
* __imatmul__() (於 operator 模組中):    In-place Operators. (line   72)
* __imod__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __imod__() (於 operator 模組中):       In-place Operators. (line   62)
* __import__() (內建函式):               內建函式.           (line 1770)
* __import__() (於 importlib 模組中):    Functions<10>.      (line    6)
* __imul__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __imul__() (於 operator 模組中):       In-place Operators. (line   67)
* __index__() (object 的方法):           Emulating numeric types.
                                                             (line  127)
* __index__() (於 operator 模組中):      operator --- Standard operators as functions.
                                                             (line   93)
* __init_subclass__() (object 的類別成員): Customizing class creation.
                                                             (line   13)
* __init__() (difflib.HtmlDiff 的方法):  difflib --- Helpers for computing deltas.
                                                             (line   91)
* __init__() (logging.Handler 的方法):   Handler Objects.    (line   13)
* __init__() (logging.logging.Formatter 的方法): Formatters. (line   13)
* __init__() (object 的方法):            Basic customization.
                                                             (line   38)
* __instancecheck__() (class 的方法):    Customizing instance and subclass checks.
                                                             (line   15)
* __interactivehook__ (於 sys 模組中):   sys --- System-specific parameters and functions.
                                                             (line  955)
* __int__() (object 的方法):             Emulating numeric types.
                                                             (line  119)
* __invert__() (object 的方法):          Emulating numeric types.
                                                             (line  111)
* __invert__() (於 operator 模組中):     operator --- Standard operators as functions.
                                                             (line   98)
* __inv__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line   98)
* __ior__() (object 的方法):             Emulating numeric types.
                                                             (line   77)
* __ior__() (於 operator 模組中):        In-place Operators. (line   79)
* __ipow__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __ipow__() (於 operator 模組中):       In-place Operators. (line   84)
* __irshift__() (object 的方法):         Emulating numeric types.
                                                             (line   77)
* __irshift__() (於 operator 模組中):    In-place Operators. (line   89)
* __isub__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __isub__() (於 operator 模組中):       In-place Operators. (line   94)
* __iter__() (container 的方法):         Iterator Types.     (line   14)
* __iter__() (iterator 的方法):          Iterator Types.     (line   29)
* __iter__() (mailbox.Mailbox 的方法):   Mailbox objects.    (line  114)
* __iter__() (object 的方法):            Emulating container types.
                                                             (line  116)
* __iter__() (unittest.TestSuite 的方法): Grouping tests.    (line   60)
* __itruediv__() (object 的方法):        Emulating numeric types.
                                                             (line   77)
* __itruediv__() (於 operator 模組中):   In-place Operators. (line   99)
* __ixor__() (object 的方法):            Emulating numeric types.
                                                             (line   77)
* __ixor__() (於 operator 模組中):       In-place Operators. (line  104)
* __kwdefaults__ (function attribute):   The standard type hierarchy.
                                                             (line  303)
* __length_hint__() (object 的方法):     Emulating container types.
                                                             (line   52)
* __len__() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  173)
* __len__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  296)
* __len__() (mailbox.Mailbox 的方法):    Mailbox objects.    (line  200)
* __len__() (mapping object method):     Basic customization.
                                                             (line  304)
* __len__() (object 的方法):             Emulating container types.
                                                             (line   37)
* __le__() (instance method):            Comparisons<2>.     (line   50)
* __le__() (object 的方法):              Basic customization.
                                                             (line  173)
* __le__() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line   24)
* __loader__:                            Import-related module attributes.
                                                             (line   16)
* __loader__ (module attribute):         模組物件模組.       (line   23)
* __loader__ (types.ModuleType 的屬性):  Standard Interpreter Types.
                                                             (line  130)
* __lshift__() (object 的方法):          Emulating numeric types.
                                                             (line   11)
* __lshift__() (於 operator 模組中):     operator --- Standard operators as functions.
                                                             (line  106)
* __lt__() (instance method):            Comparisons<2>.     (line   50)
* __lt__() (object 的方法):              Basic customization.
                                                             (line  173)
* __lt__() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line   24)
* __main__ (模組):                       __main__ --- Top-level script environment.
                                                             (line    6)
* __matmul__() (object 的方法):          Emulating numeric types.
                                                             (line   11)
* __matmul__() (於 operator 模組中):     operator --- Standard operators as functions.
                                                             (line  121)
* __missing__():                         Mapping Types --- dict.
                                                             (line   96)
* __missing__() (collections.defaultdict 的方法): defaultdict objects.
                                                             (line   22)
* __missing__() (object 的方法):         Emulating container types.
                                                             (line  111)
* __module__ (class attribute):          The standard type hierarchy.
                                                             (line  587)
* __module__ (function attribute):       The standard type hierarchy.
                                                             (line  303)
* __module__ (method attribute):         The standard type hierarchy.
                                                             (line  390)
* __mod__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __mod__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  111)
* __mro__ (class 的屬性):                Special Attributes. (line   35)
* __mul__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __mul__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  116)
* __name__:                              Import-related module attributes.
                                                             (line   10)
* __name__ (class attribute):            The standard type hierarchy.
                                                             (line  587)
* __name__ (definition 的屬性):          Special Attributes. (line   23)
* __name__ (function attribute):         The standard type hierarchy.
                                                             (line  303)
* __name__ (method attribute):           The standard type hierarchy.
                                                             (line  390)
* __name__ (module attribute):           The standard type hierarchy.
                                                             (line  535)
* __name__ (module attribute) <1>:       模組物件模組.       (line   23)
* __name__ (module attribute) <2>:       模組物件模組.       (line   55)
* __name__ (types.ModuleType 的屬性):    Standard Interpreter Types.
                                                             (line  148)
* __neg__() (object 的方法):             Emulating numeric types.
                                                             (line  111)
* __neg__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  128)
* __new__() (object 的方法):             Basic customization.
                                                             (line    6)
* __next__() (csv.csvreader 的方法):     Reader Objects.     (line    9)
* __next__() (generator 的方法):         Generator-iterator methods.
                                                             (line   12)
* __next__() (iterator 的方法):          Iterator Types.     (line   37)
* __ne__() (email.charset.Charset 的方法): email charset Representing character sets.
                                                             (line  155)
* __ne__() (email.header.Header 的方法): email header Internationalized headers.
                                                             (line  174)
* __ne__() (instance method):            Comparisons<2>.     (line   50)
* __ne__() (object 的方法):              Basic customization.
                                                             (line  173)
* __ne__() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line   24)
* __not__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line   49)
* __or__() (object 的方法):              Emulating numeric types.
                                                             (line   11)
* __or__() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line  133)
* __package__:                           Import-related module attributes.
                                                             (line   23)
* __package__ (module attribute):        模組物件模組.       (line   23)
* __package__ (types.ModuleType 的屬性): Standard Interpreter Types.
                                                             (line  153)
* __path__:                              Import-related module attributes.
                                                             (line   56)
* __pos__() (object 的方法):             Emulating numeric types.
                                                             (line  111)
* __pos__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  138)
* __pow__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __pow__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  143)
* __prepare__ (metaclass method):        Preparing the class namespace.
                                                             (line    6)
* __qualname__ (definition 的屬性):      Special Attributes. (line   28)
* __radd__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __rand__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __rdivmod__() (object 的方法):         Emulating numeric types.
                                                             (line   41)
* __reduce_ex__() (object 的方法):       Pickling Class Instances.
                                                             (line  161)
* __reduce__() (object 的方法):          Pickling Class Instances.
                                                             (line  106)
* __repr__() (multiprocessing.managers.BaseProxy 的方法): Proxy Objects.
                                                             (line  145)
* __repr__() (netrc.netrc 的方法):       netrc Objects.      (line   16)
* __repr__() (object 的方法):            Basic customization.
                                                             (line  113)
* __reversed__() (object 的方法):        Emulating container types.
                                                             (line  127)
* __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 --- Rational numbers.
                                                             (line  162)
* __round__() (object 的方法):           Emulating numeric types.
                                                             (line  141)
* __rpow__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __rrshift__() (object 的方法):         Emulating numeric types.
                                                             (line   41)
* __rshift__() (object 的方法):          Emulating numeric types.
                                                             (line   11)
* __rshift__() (於 operator 模組中):     operator --- Standard operators as functions.
                                                             (line  148)
* __rsub__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __rtruediv__() (object 的方法):        Emulating numeric types.
                                                             (line   41)
* __rxor__() (object 的方法):            Emulating numeric types.
                                                             (line   41)
* __self__ (method attribute):           The standard type hierarchy.
                                                             (line  390)
* __setattr__() (object 的方法):         Customizing attribute access.
                                                             (line   53)
* __setitem__() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  202)
* __setitem__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  320)
* __setitem__() (mailbox.Mailbox 的方法): Mailbox objects.   (line   90)
* __setitem__() (mailbox.Maildir 的方法): Maildir.           (line   91)
* __setitem__() (object 的方法):         Emulating container types.
                                                             (line   93)
* __setitem__() (於 operator 模組中):    operator --- Standard operators as functions.
                                                             (line  201)
* __setstate__() (copy protocol):        Handling Stateful Objects.
                                                             (line    6)
* __setstate__() (object 的方法):        Pickling Class Instances.
                                                             (line   70)
* __set_name__() (object 的方法):        Implementing Descriptors.
                                                             (line   45)
* __set__() (object 的方法):             Implementing Descriptors.
                                                             (line   31)
* __slots__:                             Glossary.           (line 1142)
* __spec__:                              Import-related module attributes.
                                                             (line   40)
* __spec__ (types.ModuleType 的屬性):    Standard Interpreter Types.
                                                             (line  174)
* __stderr__ (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line 1525)
* __stdin__ (於 sys 模組中):             sys --- System-specific parameters and functions.
                                                             (line 1525)
* __stdout__ (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line 1525)
* __str__() (datetime.date 的方法):      date Objects.       (line  247)
* __str__() (datetime.datetime 的方法):  datetime Objects.   (line  675)
* __str__() (datetime.time 的方法):      time Objects.       (line  205)
* __str__() (email.charset.Charset 的方法): email charset Representing character sets.
                                                             (line  145)
* __str__() (email.header.Header 的方法): email header Internationalized headers.
                                                             (line  158)
* __str__() (email.headerregistry.Address 的方法): email headerregistry Custom Header Objects.
                                                             (line  447)
* __str__() (email.headerregistry.Group 的方法): email headerregistry Custom Header Objects.
                                                             (line  481)
* __str__() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line   94)
* __str__() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  101)
* __str__() (multiprocessing.managers.BaseProxy 的方法): Proxy Objects.
                                                             (line  149)
* __str__() (object 的方法):             Basic customization.
                                                             (line  129)
* __subclasscheck__() (class 的方法):    Customizing instance and subclass checks.
                                                             (line   21)
* __subclasses__() (class 的方法):       Special Attributes. (line   46)
* __subclasshook__() (abc.ABCMeta 的方法): abc --- Abstract Base Classes.
                                                             (line   92)
* __sub__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __sub__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  153)
* __suppress_context__ (traceback.TracebackException 的屬性): TracebackException Objects.
                                                             (line   30)
* __traceback__ (exception attribute):   The raise statement.
                                                             (line    6)
* __truediv__() (object 的方法):         Emulating numeric types.
                                                             (line   11)
* __truediv__() (於 operator 模組中):    operator --- Standard operators as functions.
                                                             (line  158)
* __trunc__() (object 的方法):           Emulating numeric types.
                                                             (line  141)
* __unraisablehook__ (於 sys 模組中):    sys --- System-specific parameters and functions.
                                                             (line  336)
* __xor__() (object 的方法):             Emulating numeric types.
                                                             (line   11)
* __xor__() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  164)
* {} (curly brackets); dictionary expression: Dictionary displays.
                                                             (line    6)
* {} (curly brackets); in formatted string literal: String literal concatenation.
                                                             (line   24)
* {} (curly brackets); in regular expressions: Regular Expression Syntax.
                                                             (line   95)
* {} (curly brackets); in string formatting: Format String Syntax.
                                                             (line   13)
* {} (curly brackets); set expression:   Set displays.       (line    6)
* | (vertical bar); in regular expressions: Regular Expression Syntax.
                                                             (line  185)
* |=; augmented assignment:              Augmented assignment statements.
                                                             (line    6)
* ~ (tilde); home directory expansion:   os path --- Common pathname manipulations.
                                                             (line  134)
* A (於 re 模組中):                      Module Contents.    (line   44)
* a-LAW:                                 audioop --- Manipulate raw audio data.
                                                             (line   17)
* A-LAW:                                 aifc --- Read and write AIFF and AIFC files.
                                                             (line  159)
* A-LAW <1>:                             sndhdr --- Determine type of sound file.
                                                             (line    8)
* a2b_base64() (於 binascii 模組中):     binascii --- Convert between binary and ASCII.
                                                             (line   41)
* a2b_hex() (於 binascii 模組中):        binascii --- Convert between binary and ASCII.
                                                             (line  159)
* a2b_hqx() (於 binascii 模組中):        binascii --- Convert between binary and ASCII.
                                                             (line   76)
* a2b_qp() (於 binascii 模組中):         binascii --- Convert between binary and ASCII.
                                                             (line   55)
* a2b_uu() (於 binascii 模組中):         binascii --- Convert between binary and ASCII.
                                                             (line   26)
* a85decode() (於 base64 模組中):        base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  159)
* a85encode() (於 base64 模組中):        base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  136)
* ABC (abc 中的類別):                    abc --- Abstract Base Classes.
                                                             (line   26)
* abc (模組):                            abc --- Abstract Base Classes.
                                                             (line    6)
* ABCMeta (abc 中的類別):                abc --- Abstract Base Classes.
                                                             (line   52)
* abiflags (於 sys 模組中):              sys --- System-specific parameters and functions.
                                                             (line   12)
* abort():                               行程（Process）控制.
                                                             (line    8)
* abort() (asyncio.DatagramTransport 的方法): Datagram Transports.
                                                             (line   15)
* abort() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line    6)
* abort() (ftplib.FTP 的方法):           FTP Objects.        (line   61)
* abort() (threading.Barrier 的方法):    Barrier Objects.    (line   82)
* abort() (於 os 模組中):                Process Management. (line   16)
* above() (curses.panel.Panel 的方法):   Panel Objects.      (line   13)
* ABOVE_NORMAL_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   52)
* abs() (decimal.Context 的方法):        Context objects.    (line  230)
* abs() (內建函式):                      內建函式.           (line   55)
* abs() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line   73)
* abspath() (於 os.path 模組中):         os path --- Common pathname manipulations.
                                                             (line   54)
* abstract base class:                   Glossary.           (line   32)
* AbstractAsyncContextManager (contextlib 中的類別): Utilities.
                                                             (line   19)
* AbstractBasicAuthHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  331)
* AbstractChildWatcher (asyncio 中的類別): Process Watchers. (line   39)
* abstractclassmethod() (於 abc 模組中): abc --- Abstract Base Classes.
                                                             (line  237)
* AbstractContextManager (contextlib 中的類別): Utilities.   (line    8)
* AbstractDigestAuthHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  370)
* AbstractEventLoop (asyncio 中的類別):  Event Loop Implementations.
                                                             (line   40)
* AbstractEventLoopPolicy (asyncio 中的類別): Policy Objects.
                                                             (line    8)
* AbstractFormatter (formatter 中的類別): Formatter Implementations.
                                                             (line   18)
* abstractmethod() (於 abc 模組中):      abc --- Abstract Base Classes.
                                                             (line  161)
* abstractproperty() (於 abc 模組中):    abc --- Abstract Base Classes.
                                                             (line  279)
* AbstractSet (typing 中的類別):         Classes functions and decorators.
                                                             (line  209)
* abstractstaticmethod() (於 abc 模組中): abc --- Abstract Base Classes.
                                                             (line  258)
* AbstractWriter (formatter 中的類別):   Writer Implementations.
                                                             (line   16)
* accept() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  230)
* accept() (multiprocessing.connection.Listener 的方法): Listeners and Clients.
                                                             (line   84)
* accept() (socket.socket 的方法):       Socket Objects.     (line   13)
* access() (於 os 模組中):               Files and Directories.
                                                             (line   51)
* accumulate() (於 itertools 模組中):    Itertool functions. (line   10)
* aclose() (agen 的方法):                Asynchronous generator-iterator methods.
                                                             (line   55)
* aclose() (contextlib.AsyncExitStack 的方法): Utilities.    (line  477)
* acos() (於 cmath 模組中):              Trigonometric functions<2>.
                                                             (line    6)
* acos() (於 math 模組中):               Trigonometric functions.
                                                             (line    6)
* acosh() (於 cmath 模組中):             Hyperbolic functions<2>.
                                                             (line    6)
* acosh() (於 math 模組中):              Hyperbolic functions.
                                                             (line    9)
* acquire() (asyncio.Condition 的方法):  Condition.          (line   48)
* acquire() (asyncio.Lock 的方法):       Lock.               (line   36)
* acquire() (asyncio.Semaphore 的方法):  Semaphore.          (line   43)
* 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 Objects.      (line   35)
* acquire() (threading.Semaphore 的方法): Semaphore Objects. (line   34)
* acquire() (_thread.lock 的方法):       _thread --- Low-level threading API.
                                                             (line  125)
* acquire_lock() (於 imp 模組中):        imp --- Access the import internals.
                                                             (line  275)
* Action (argparse 中的類別):            Action classes.     (line   11)
* action (optparse.Option 的屬性):       Option attributes.  (line   11)
* ACTIONS (optparse.Option 的屬性):      Adding new actions. (line   31)
* active_children() (於 multiprocessing 模組中): Miscellaneous<3>.
                                                             (line    6)
* active_count() (於 threading 模組中):  threading --- Thread-based parallelism.
                                                             (line   32)
* add() (decimal.Context 的方法):        Context objects.    (line  234)
* add() (frozenset 的方法):              Set Types --- set frozenset.
                                                             (line  195)
* add() (mailbox.Mailbox 的方法):        Mailbox objects.    (line   59)
* add() (mailbox.Maildir 的方法):        Maildir.            (line   91)
* add() (msilib.RadioButtonGroup 的方法): GUI classes.       (line   34)
* add() (pstats.Stats 的方法):           The Stats Class.    (line   49)
* add() (tarfile.TarFile 的方法):        TarFile Objects.    (line  198)
* add() (tkinter.ttk.Notebook 的方法):   ttk Notebook.       (line    8)
* add() (於 audioop 模組中):             audioop --- Manipulate raw audio data.
                                                             (line   31)
* add() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line   78)
* addAsyncCleanup() (unittest.IsolatedAsyncioTestCase 的方法): Test cases.
                                                             (line  836)
* addaudithook() (於 sys 模組中):        sys --- System-specific parameters and functions.
                                                             (line   23)
* addch() (curses.window 的方法):        Window Objects.     (line    9)
* addClassCleanup() (unittest.TestCase 的類別成員): Test cases.
                                                             (line  772)
* addCleanup() (unittest.TestCase 的方法): Test cases.       (line  742)
* addcomponent() (turtle.Shape 的方法):  Public classes.     (line   65)
* addError() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  351)
* addExpectedFailure() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  387)
* addFailure() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  362)
* addfile() (tarfile.TarFile 的方法):    TarFile Objects.    (line  216)
* addFilter() (logging.Handler 的方法):  Handler Objects.    (line   52)
* addFilter() (logging.Logger 的方法):   Logger Objects.     (line  251)
* addHandler() (logging.Logger 的方法):  Logger Objects.     (line  268)
* addition:                              Binary arithmetic operations.
                                                             (line   60)
* addLevelName() (於 logging 模組中):    Module-Level Functions.
                                                             (line  190)
* addModuleCleanup() (於 unittest 模組中): setUpModule and tearDownModule.
                                                             (line   22)
* addnstr() (curses.window 的方法):      Window Objects.     (line   23)
* AddPackagePath() (於 modulefinder 模組中): modulefinder --- Find modules used by a script.
                                                             (line   16)
* addr (smtpd.SMTPChannel 的屬性):       SMTPChannel Objects.
                                                             (line   52)
* Address (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  402)
* address (email.headerregistry.SingleAddressHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  222)
* address (multiprocessing.connection.Listener 的屬性): Listeners and Clients.
                                                             (line   99)
* address (multiprocessing.managers.BaseManager 的屬性): Managers.
                                                             (line  120)
* addresses (email.headerregistry.AddressHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  195)
* addresses (email.headerregistry.Group 的屬性): email headerregistry Custom Header Objects.
                                                             (line  476)
* AddressHeader (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  180)
* addressof() (於 ctypes 模組中):        Utility functions.  (line    6)
* AddressValueError:                     Custom Exceptions.  (line    9)
* address_exclude() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  160)
* address_exclude() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  342)
* address_family (socketserver.BaseServer 的屬性): Server Objects<2>.
                                                             (line   65)
* address_string() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  323)
* addr_spec (email.headerregistry.Address 的屬性): email headerregistry Custom Header Objects.
                                                             (line  441)
* addshape() (於 turtle 模組中):         Settings and special methods.
                                                             (line   70)
* addsitedir() (於 site 模組中):         Module contents<3>. (line   50)
* addSkip() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  379)
* addstr() (curses.window 的方法):       Window Objects.     (line   31)
* addSubTest() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  405)
* addSuccess() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  373)
* addTest() (unittest.TestSuite 的方法): Grouping tests.     (line   25)
* addTests() (unittest.TestSuite 的方法): Grouping tests.    (line   30)
* addTypeEqualityFunc() (unittest.TestCase 的方法): Test cases.
                                                             (line  560)
* addUnexpectedSuccess() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  397)
* add_alias() (於 email.charset 模組中): email charset Representing character sets.
                                                             (line  193)
* add_alternative() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  639)
* add_argument() (argparse.ArgumentParser 的方法): The add_argument method.
                                                             (line    6)
* add_argument_group() (argparse.ArgumentParser 的方法): Argument groups.
                                                             (line    6)
* add_attachment() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  651)
* add_cgi_vars() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line  132)
* add_charset() (於 email.charset 模組中): email charset Representing character sets.
                                                             (line  164)
* add_child_handler() (asyncio.AbstractChildWatcher 的方法): Process Watchers.
                                                             (line   41)
* add_codec() (於 email.charset 模組中): email charset Representing character sets.
                                                             (line  202)
* add_cookie_header() (http.cookiejar.CookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line   11)
* add_data() (於 msilib 模組中):         msilib --- Read and write Microsoft Installer files.
                                                             (line   74)
* add_dll_directory() (於 os 模組中):    Process Management. (line   24)
* add_done_callback() (asyncio.Future 的方法): Future Object.
                                                             (line   76)
* add_done_callback() (asyncio.Task 的方法): Task Object.    (line  147)
* add_done_callback() (concurrent.futures.Future 的方法): Future Objects.
                                                             (line   70)
* add_fallback() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   28)
* add_file() (msilib.Directory 的方法):  Directory Objects.  (line   30)
* add_flag() (mailbox.MaildirMessage 的方法): MaildirMessage.
                                                             (line   76)
* add_flag() (mailbox.mboxMessage 的方法): mboxMessage.      (line   79)
* add_flag() (mailbox.MMDFMessage 的方法): MMDFMessage.      (line   78)
* add_flowing_data() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line   43)
* add_folder() (mailbox.Maildir 的方法): Maildir.            (line   71)
* add_folder() (mailbox.MH 的方法):      MH.                 (line   42)
* add_get_handler() (email.contentmanager.ContentManager 的方法): email contentmanager Managing MIME Content.
                                                             (line   75)
* add_handler() (urllib.request.OpenerDirector 的方法): OpenerDirector Objects.
                                                             (line    8)
* add_header() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  258)
* add_header() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  368)
* add_header() (urllib.request.Request 的方法): Request Objects.
                                                             (line   77)
* add_header() (wsgiref.headers.Headers 的方法): wsgiref headers -- WSGI response header tools.
                                                             (line   61)
* add_history() (於 readline 模組中):    History list.       (line   38)
* add_hor_rule() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line   36)
* add_include_dir() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line   95)
* add_label() (mailbox.BabylMessage 的方法): BabylMessage.   (line   55)
* add_label_data() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line   59)
* add_library() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  112)
* add_library_dir() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  134)
* add_line_break() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line   31)
* add_link_object() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  179)
* add_literal_data() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line   53)
* add_mutually_exclusive_group() (argparse.ArgumentParser 的方法): Mutual exclusion.
                                                             (line    6)
* add_option() (optparse.OptionParser 的方法): Defining options.
                                                             (line   14)
* add_parent() (urllib.request.BaseHandler 的方法): BaseHandler Objects.
                                                             (line   10)
* add_password() (urllib.request.HTTPPasswordMgr 的方法): HTTPPasswordMgr Objects.
                                                             (line    9)
* add_password() (urllib.request.HTTPPasswordMgrWithPriorAuth 的方法): HTTPPasswordMgrWithPriorAuth Objects.
                                                             (line   10)
* add_reader() (asyncio.loop 的方法):    Watching file descriptors.
                                                             (line    6)
* add_related() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  626)
* add_runtime_library_dir() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  149)
* add_section() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line   86)
* add_section() (configparser.RawConfigParser 的方法): RawConfigParser Objects.
                                                             (line   26)
* add_sequence() (mailbox.MHMessage 的方法): MHMessage.      (line   41)
* add_set_handler() (email.contentmanager.ContentManager 的方法): email contentmanager Managing MIME Content.
                                                             (line   80)
* add_signal_handler() (asyncio.loop 的方法): Unix signals.  (line    6)
* add_stream() (於 msilib 模組中):       msilib --- Read and write Microsoft Installer files.
                                                             (line  104)
* add_subparsers() (argparse.ArgumentParser 的方法): Sub-commands.
                                                             (line    6)
* add_tables() (於 msilib 模組中):       msilib --- Read and write Microsoft Installer files.
                                                             (line   95)
* add_type() (於 mimetypes 模組中):      mimetypes --- Map filenames to MIME types.
                                                             (line  106)
* add_unredirected_header() (urllib.request.Request 的方法): Request Objects.
                                                             (line   88)
* add_writer() (asyncio.loop 的方法):    Watching file descriptors.
                                                             (line   16)
* adjusted() (decimal.Decimal 的方法):   Decimal objects.    (line  113)
* adler32() (於 zlib 模組中):            zlib --- Compression compatible with gzip.
                                                             (line   28)
* ADPCM, Intel/DVI:                      audioop --- Manipulate raw audio data.
                                                             (line   17)
* adpcm2lin() (於 audioop 模組中):       audioop --- Manipulate raw audio data.
                                                             (line   38)
* AF_ALG (於 socket 模組中):             Constants<8>.       (line  183)
* AF_CAN (於 socket 模組中):             Constants<8>.       (line   93)
* AF_INET (於 socket 模組中):            Constants<8>.       (line   11)
* AF_INET6 (於 socket 模組中):           Constants<8>.       (line   11)
* AF_LINK (於 socket 模組中):            Constants<8>.       (line  207)
* AF_PACKET (於 socket 模組中):          Constants<8>.       (line  144)
* AF_QIPCRTR (於 socket 模組中):         Constants<8>.       (line  235)
* AF_RDS (於 socket 模組中):             Constants<8>.       (line  154)
* AF_UNIX (於 socket 模組中):            Constants<8>.       (line   11)
* AF_VSOCK (於 socket 模組中):           Constants<8>.       (line  194)
* aifc (模組):                           aifc --- Read and write AIFF and AIFC files.
                                                             (line    6)
* aifc() (aifc.aifc 的方法):             aifc --- Read and write AIFF and AIFC files.
                                                             (line  133)
* AIFF:                                  aifc --- Read and write AIFF and AIFC files.
                                                             (line    8)
* AIFF <1>:                              chunk --- Read IFF chunked data.
                                                             (line    8)
* aiff() (aifc.aifc 的方法):             aifc --- Read and write AIFF and AIFC files.
                                                             (line  127)
* AIFF-C:                                aifc --- Read and write AIFF and AIFC files.
                                                             (line    8)
* AIFF-C <1>:                            chunk --- Read IFF chunked data.
                                                             (line    8)
* alarm() (於 signal 模組中):            Module contents<2>. (line  224)
* alaw2lin() (於 audioop 模組中):        audioop --- Manipulate raw audio data.
                                                             (line   45)
* AlertDescription (ssl 中的類別):       Constants<9>.       (line  490)
* ALERT_DESCRIPTION_HANDSHAKE_FAILURE (於 ssl 模組中): Constants<9>.
                                                             (line  476)
* ALERT_DESCRIPTION_INTERNAL_ERROR (於 ssl 模組中): Constants<9>.
                                                             (line  476)
* algorithms_available (於 hashlib 模組中): Hash algorithms. (line   81)
* algorithms_guaranteed (於 hashlib 模組中): Hash algorithms.
                                                             (line   72)
* alias (pdb command):                   Debugger Commands.  (line  283)
* alignment() (於 ctypes 模組中):        Utility functions.  (line   14)
* alive (weakref.finalize 的屬性):       weakref --- Weak references.
                                                             (line  268)
* all() (內建函式):                      內建函式.           (line   62)
* allocate_lock() (於 _thread 模組中):   _thread --- Low-level threading API.
                                                             (line   67)
* allocfunc (C 型態):                    Slot Type typedefs. (line    6)
* allowed_domains() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy Objects.
                                                             (line   65)
* allow_reuse_address (socketserver.BaseServer 的屬性): Server Objects<2>.
                                                             (line   92)
* all_errors (於 ftplib 模組中):         ftplib --- FTP protocol client.
                                                             (line  133)
* all_features (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line   90)
* all_frames (tracemalloc.Filter 的屬性): Filter.            (line   57)
* all_properties (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line  122)
* all_suffixes() (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   54)
* all_tasks() (asyncio.Task 的類別成員): Task Object.        (line  231)
* all_tasks() (於 asyncio 模組中):       Introspection.      (line   16)
* alt() (於 curses.ascii 模組中):        curses ascii --- Utilities for ASCII characters.
                                                             (line  218)
* altsep (於 os 模組中):                 Miscellaneous System Information.
                                                             (line  102)
* altzone (於 time 模組中):              Timezone Constants. (line    6)
* ALT_DIGITS (於 locale 模組中):         locale --- Internationalization services.
                                                             (line  296)
* ALWAYS_EQ (於 test.support 模組中):    test support --- Utilities for the Python test suite.
                                                             (line  145)
* ALWAYS_TYPED_ACTIONS (optparse.Option 的屬性): Adding new actions.
                                                             (line   43)
* AMPER (於 token 模組中):               token --- Constants used with Python parse trees.
                                                             (line  102)
* AMPEREQUAL (於 token 模組中):          token --- Constants used with Python parse trees.
                                                             (line  190)
* and_() (於 operator 模組中):           operator --- Standard operators as functions.
                                                             (line   83)
* annotated; assignment:                 Annotated assignment statements.
                                                             (line    6)
* annotation:                            Glossary.           (line   47)
* annotation (inspect.Parameter 的屬性): Introspecting callables with the Signature object.
                                                             (line  174)
* announce() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  502)
* anonymous; function:                   Lambdas.            (line    6)
* answer_challenge() (於 multiprocessing.connection 模組中): Listeners and Clients.
                                                             (line   25)
* anticipate_failure() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  567)
* Any (於 typing 模組中):                Classes functions and decorators.
                                                             (line  771)
* ANY (於 unittest.mock 模組中):         ANY.                (line    6)
* any() (內建函式):                      內建函式.           (line   73)
* AnyStr (於 typing 模組中):             Classes functions and decorators.
                                                             (line  948)
* api_version (於 sys 模組中):           sys --- System-specific parameters and functions.
                                                             (line 1642)
* apop() (poplib.POP3 的方法):           POP3 Objects.       (line   41)
* APPDATA:                               PEP 370 Per-user site-packages Directory.
                                                             (line   26)
* append() (array.array 的方法):         array --- 高效率的數值型態陣列.
                                                             (line  106)
* append() (collections.deque 的方法):   deque objects.      (line   35)
* append() (email.header.Header 的方法): email header Internationalized headers.
                                                             (line   96)
* append() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line   33)
* append() (msilib.CAB 的方法):          CAB Objects.        (line   15)
* append() (pipes.Template 的方法):      Template Objects.   (line   22)
* append() (sequence method):            Mutable Sequence Types.
                                                             (line   16)
* append() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line   87)
* appendChild() (xml.dom.Node 的方法):   Node Objects.       (line  115)
* appendleft() (collections.deque 的方法): deque objects.    (line   39)
* append_history_file() (於 readline 模組中): History file.  (line   20)
* application_uri() (於 wsgiref.util 模組中): wsgiref util -- WSGI environment utilities.
                                                             (line   32)
* apply (2to3 fixer):                    Fixers.             (line   10)
* apply() (multiprocessing.pool.Pool 的方法): Process Pools. (line   63)
* apply_async() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line   71)
* apply_defaults() (inspect.BoundArguments 的方法): Introspecting callables with the Signature object.
                                                             (line  311)
* architecture() (於 platform 模組中):   Cross Platform.     (line    6)
* archive (zipimport.zipimporter 的屬性): zipimporter Objects.
                                                             (line   69)
* aRepr (於 reprlib 模組中):             reprlib --- Alternate repr implementation.
                                                             (line   24)
* argparse (模組):                       argparse --- Parser for command-line options arguments and sub-commands.
                                                             (line    6)
* args (BaseException 的屬性):           Base classes.       (line   17)
* args (functools.partial 的屬性):       partial Objects.    (line   15)
* args (inspect.BoundArguments 的屬性):  Introspecting callables with the Signature object.
                                                             (line  297)
* args (pdb command):                    Debugger Commands.  (line  229)
* args (subprocess.CompletedProcess 的屬性): Using the subprocess Module.
                                                             (line   96)
* args (subprocess.Popen 的屬性):        Popen Objects.      (line   97)
* args_from_interpreter_flags() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  391)
* argtypes (ctypes._FuncPtr 的屬性):     Foreign functions.  (line   36)
* argument:                              Glossary.           (line   62)
* argument; call semantics:              Slicings.           (line   38)
* argument; difference from parameter:   How can I pass optional or keyword parameters from one function to another?.
                                                             (line   17)
* argument; function definition:         Function definitions.
                                                             (line   53)
* ArgumentDefaultsHelpFormatter (argparse 中的類別): formatter_class.
                                                             (line   10)
* ArgumentError:                         Foreign functions.  (line   83)
* ArgumentParser (argparse 中的類別):    ArgumentParser objects.
                                                             (line    6)
* arguments (inspect.BoundArguments 的屬性): Introspecting callables with the Signature object.
                                                             (line  281)
* argv (in module sys):                  Process-wide parameters.
                                                             (line  217)
* argv (於 sys 模組中):                  sys --- System-specific parameters and functions.
                                                             (line   56)
* arithmetic:                            Numeric Types --- int float complex.
                                                             (line   27)
* arithmetic; conversion:                Arithmetic conversions.
                                                             (line    6)
* ArithmeticError:                       Base classes.       (line   43)
* array (array 中的類別):                array --- 高效率的數值型態陣列.
                                                             (line   71)
* Array (ctypes 中的類別):               Arrays and pointers.
                                                             (line    6)
* array (模組):                          array --- 高效率的數值型態陣列.
                                                             (line    6)
* Array() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  195)
* Array() (於 multiprocessing 模組中):   Shared ctypes Objects.
                                                             (line   42)
* Array() (於 multiprocessing.sharedctypes 模組中): The multiprocessing sharedctypes module.
                                                             (line   51)
* arrays:                                array --- 高效率的數值型態陣列.
                                                             (line    6)
* arraysize (sqlite3.Cursor 的屬性):     Cursor Objects.     (line  213)
* article() (nntplib.NNTP 的方法):       Methods<3>.         (line  241)
* as; except clause:                     The try statement.  (line   40)
* as; import statement:                  The import statement.
                                                             (line   38)
* as; with statement:                    The with statement. (line    6)
* ASCII:                                 Notation.           (line   31)
* ASCII <1>:                             Literals.           (line    8)
* ASCII (於 re 模組中):                  Module Contents.    (line   44)
* ascii() (內建函式):                    內建函式.           (line   84)
* ascii() (於 curses.ascii 模組中):      curses ascii --- Utilities for ASCII characters.
                                                             (line  209)
* ascii_letters (於 string 模組中):      String constants.   (line    8)
* ascii_lowercase (於 string 模組中):    String constants.   (line   14)
* ascii_uppercase (於 string 模組中):    String constants.   (line   19)
* asctime() (於 time 模組中):            Functions<2>.       (line    6)
* asdict() (於 dataclasses 模組中):      Module-level decorators classes and functions.
                                                             (line  269)
* asend() (agen 的方法):                 Asynchronous generator-iterator methods.
                                                             (line   28)
* asin() (於 cmath 模組中):              Trigonometric functions<2>.
                                                             (line   13)
* asin() (於 math 模組中):               Trigonometric functions.
                                                             (line   10)
* asinh() (於 cmath 模組中):             Hyperbolic functions<2>.
                                                             (line   12)
* asinh() (於 math 模組中):              Hyperbolic functions.
                                                             (line   13)
* assertAlmostEqual() (unittest.TestCase 的方法): Test cases.
                                                             (line  482)
* assertCountEqual() (unittest.TestCase 的方法): Test cases. (line  539)
* assertDictEqual() (unittest.TestCase 的方法): Test cases.  (line  648)
* assertEqual() (unittest.TestCase 的方法): Test cases.      (line  177)
* assertFalse() (unittest.TestCase 的方法): Test cases.      (line  201)
* assertGreater() (unittest.TestCase 的方法): Test cases.    (line  506)
* assertGreaterEqual() (unittest.TestCase 的方法): Test cases.
                                                             (line  506)
* assertIn() (unittest.TestCase 的方法): Test cases.         (line  228)
* AssertionError:                        Concrete exceptions.
                                                             (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  506)
* assertLessEqual() (unittest.TestCase 的方法): Test cases.  (line  506)
* assertListEqual() (unittest.TestCase 的方法): Test cases.  (line  625)
* assertLogs() (unittest.TestCase 的方法): Test cases.       (line  403)
* assertMultiLineEqual() (unittest.TestCase 的方法): Test cases.
                                                             (line  600)
* assertNotAlmostEqual() (unittest.TestCase 的方法): Test cases.
                                                             (line  482)
* assertNotEqual() (unittest.TestCase 的方法): Test cases.   (line  196)
* assertNotIn() (unittest.TestCase 的方法): Test cases.      (line  228)
* assertNotIsInstance() (unittest.TestCase 的方法): Test cases.
                                                             (line  235)
* assertNotRegex() (unittest.TestCase 的方法): Test cases.   (line  519)
* assertRaises() (unittest.TestCase 的方法): Test cases.     (line  270)
* assertRaisesRegex() (unittest.TestCase 的方法): Test cases.
                                                             (line  311)
* assertRegex() (unittest.TestCase 的方法): Test cases.      (line  519)
* asserts (2to3 fixer):                  Fixers.             (line   15)
* assertSequenceEqual() (unittest.TestCase 的方法): Test cases.
                                                             (line  610)
* assertSetEqual() (unittest.TestCase 的方法): Test cases.   (line  636)
* assertTrue() (unittest.TestCase 的方法): Test cases.       (line  201)
* assertTupleEqual() (unittest.TestCase 的方法): Test cases. (line  625)
* assertWarns() (unittest.TestCase 的方法): Test cases.      (line  337)
* assertWarnsRegex() (unittest.TestCase 的方法): Test cases. (line  378)
* assert_any_await() (unittest.mock.AsyncMock 的方法): The Mock Class.
                                                             (line  809)
* assert_any_call() (unittest.mock.Mock 的方法): The Mock Class.
                                                             (line  147)
* assert_awaited() (unittest.mock.AsyncMock 的方法): The Mock Class.
                                                             (line  739)
* assert_awaited_once() (unittest.mock.AsyncMock 的方法): The Mock Class.
                                                             (line  759)
* assert_awaited_once_with() (unittest.mock.AsyncMock 的方法): The Mock Class.
                                                             (line  792)
* assert_awaited_with() (unittest.mock.AsyncMock 的方法): The Mock Class.
                                                             (line  775)
* assert_called() (unittest.mock.Mock 的方法): The Mock Class.
                                                             (line   95)
* assert_called_once() (unittest.mock.Mock 的方法): The Mock Class.
                                                             (line  106)
* assert_called_once_with() (unittest.mock.Mock 的方法): The Mock Class.
                                                             (line  133)
* assert_called_with() (unittest.mock.Mock 的方法): The Mock Class.
                                                             (line  123)
* assert_has_awaits() (unittest.mock.AsyncMock 的方法): The Mock Class.
                                                             (line  826)
* assert_has_calls() (unittest.mock.Mock 的方法): The Mock Class.
                                                             (line  163)
* assert_line_data() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line  143)
* assert_not_awaited() (unittest.mock.AsyncMock 的方法): The Mock Class.
                                                             (line  853)
* assert_not_called() (unittest.mock.Mock 的方法): The Mock Class.
                                                             (line  184)
* assert_python_failure() (於 test.support.script_helper 模組中): test support script_helper --- Utilities for the Python execution tests.
                                                             (line   49)
* assert_python_ok() (於 test.support.script_helper 模組中): test support script_helper --- Utilities for the Python execution tests.
                                                             (line   36)
* assignment; statement:                 The standard type hierarchy.
                                                             (line  192)
* assignment; statement <1>:             Assignment statements.
                                                             (line    6)
* AST (ast 中的類別):                    Node classes.       (line    6)
* ast (模組):                            ast --- Abstract Syntax Trees.
                                                             (line    6)
* astimezone() (datetime.datetime 的方法): datetime Objects. (line  425)
* astuple() (於 dataclasses 模組中):     Module-level decorators classes and functions.
                                                             (line  294)
* ASYNC (於 token 模組中):               token --- Constants used with Python parse trees.
                                                             (line  246)
* async for; in comprehensions:          Displays for lists sets and dictionaries.
                                                             (line   14)
* AsyncContextManager (typing 中的類別): Classes functions and decorators.
                                                             (line  340)
* asynccontextmanager() (於 contextlib 模組中): Utilities.   (line   91)
* AsyncExitStack (contextlib 中的類別):  Utilities.          (line  453)
* AsyncGenerator (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  244)
* AsyncGenerator (typing 中的類別):      Classes functions and decorators.
                                                             (line  422)
* AsyncGeneratorType (於 types 模組中):  Standard Interpreter Types.
                                                             (line   43)
* asynchat (模組):                       asynchat --- Asynchronous socket command/response handler.
                                                             (line    6)
* asynchronous context manager:          Glossary.           (line   94)
* asynchronous generator:                Glossary.           (line  100)
* asynchronous generator iterator:       Glossary.           (line  117)
* asynchronous generator; asynchronous iterator: The standard type hierarchy.
                                                             (line  466)
* asynchronous generator; function:      The standard type hierarchy.
                                                             (line  466)
* asynchronous iterable:                 Glossary.           (line  134)
* asynchronous iterator:                 Glossary.           (line  140)
* asyncio (模組):                        asyncio --- Asynchronous I/O.
                                                             (line    6)
* asyncio.subprocess.DEVNULL (於 asyncio 模組中): Constants<7>.
                                                             (line   23)
* asyncio.subprocess.PIPE (於 asyncio 模組中): Constants<7>. (line    6)
* asyncio.subprocess.Process (asyncio 中的類別): Interacting with Subprocesses.
                                                             (line   11)
* asyncio.subprocess.STDOUT (於 asyncio 模組中): Constants<7>.
                                                             (line   17)
* AsyncIterable (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  230)
* AsyncIterable (typing 中的類別):       Classes functions and decorators.
                                                             (line  320)
* AsyncIterator (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  237)
* AsyncIterator (typing 中的類別):       Classes functions and decorators.
                                                             (line  326)
* AsyncMock (unittest.mock 中的類別):    The Mock Class.     (line  667)
* asyncore (模組):                       asyncore --- Asynchronous socket handler.
                                                             (line    6)
* AsyncResult (multiprocessing.pool 中的類別): Process Pools.
                                                             (line  191)
* asyncSetUp() (unittest.IsolatedAsyncioTestCase 的方法): Test cases.
                                                             (line  812)
* asyncTearDown() (unittest.IsolatedAsyncioTestCase 的方法): Test cases.
                                                             (line  821)
* async_chat (asynchat 中的類別):        asynchat --- Asynchronous socket command/response handler.
                                                             (line   28)
* async_chat.ac_in_buffer_size (於 asynchat 模組中): asynchat --- Asynchronous socket command/response handler.
                                                             (line   47)
* async_chat.ac_out_buffer_size (於 asynchat 模組中): asynchat --- Asynchronous socket command/response handler.
                                                             (line   51)
* as_bytes() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  105)
* as_bytes() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  106)
* as_completed() (於 asyncio 模組中):    Waiting Primitives. (line   86)
* as_completed() (於 concurrent.futures 模組中): Module Functions.
                                                             (line   43)
* as_integer_ratio() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  121)
* as_integer_ratio() (float 的方法):     Additional Methods on Float.
                                                             (line    9)
* as_integer_ratio() (fractions.Fraction 的方法): fractions --- Rational numbers.
                                                             (line   97)
* as_integer_ratio() (int 的方法):       Additional Methods on Integer Types.
                                                             (line   98)
* AS_IS (於 formatter 模組中):           The Formatter Interface.
                                                             (line   12)
* as_posix() (pathlib.PurePath 的方法):  Methods and properties.
                                                             (line  142)
* as_string() (email.message.EmailMessage 的方法): email message Representing an 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.PurePath 的方法):    Methods and properties.
                                                             (line  153)
* AT (於 token 模組中):                  token --- Constants used with Python parse trees.
                                                             (line  222)
* atan() (於 cmath 模組中):              Trigonometric functions<2>.
                                                             (line   18)
* atan() (於 math 模組中):               Trigonometric functions.
                                                             (line   14)
* atan2() (於 math 模組中):              Trigonometric functions.
                                                             (line   18)
* atanh() (於 cmath 模組中):             Hyperbolic functions<2>.
                                                             (line   19)
* atanh() (於 math 模組中):              Hyperbolic functions.
                                                             (line   17)
* ATEQUAL (於 token 模組中):             token --- Constants used with Python parse trees.
                                                             (line  226)
* atexit (weakref.finalize 的屬性):      weakref --- Weak references.
                                                             (line  273)
* atexit (模組):                         atexit --- Exit handlers.
                                                             (line    6)
* athrow() (agen 的方法):                Asynchronous generator-iterator methods.
                                                             (line   43)
* atof() (於 locale 模組中):             locale --- Internationalization services.
                                                             (line  446)
* atoi() (於 locale 模組中):             locale --- Internationalization services.
                                                             (line  451)
* atom:                                  Atoms.              (line    6)
* attach() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  167)
* attach_loop() (asyncio.AbstractChildWatcher 的方法): Process Watchers.
                                                             (line   59)
* attach_mock() (unittest.mock.Mock 的方法): The Mock Class. (line  235)
* AttlistDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  208)
* attrgetter() (於 operator 模組中):     operator --- Standard operators as functions.
                                                             (line  221)
* attrib (xml.etree.ElementTree.Element 的屬性): Element Objects.
                                                             (line   45)
* attribute:                             The standard type hierarchy.
                                                             (line   13)
* attribute <1>:                         Glossary.           (line  149)
* attribute; assignment:                 Assignment statements.
                                                             (line    6)
* attribute; assignment <1>:             Assignment statements.
                                                             (line   78)
* attribute; deletion:                   The del statement<2>.
                                                             (line   20)
* attribute; reference:                  Attribute references.
                                                             (line    6)
* AttributeError:                        Concrete exceptions.
                                                             (line   12)
* attributes (xml.dom.Node 的屬性):      Node Objects.       (line   26)
* AttributesImpl (xml.sax.xmlreader 中的類別): xml sax xmlreader --- Interface for XML parsers.
                                                             (line   69)
* AttributesNSImpl (xml.sax.xmlreader 中的類別): xml sax xmlreader --- Interface for XML parsers.
                                                             (line   80)
* attroff() (curses.window 的方法):      Window Objects.     (line   53)
* attron() (curses.window 的方法):       Window Objects.     (line   58)
* attrset() (curses.window 的方法):      Window Objects.     (line   63)
* at_eof() (asyncio.StreamReader 的方法): StreamReader.      (line   64)
* Audio Interchange File Format:         aifc --- Read and write AIFF and AIFC files.
                                                             (line    8)
* Audio Interchange File Format <1>:     chunk --- Read IFF chunked data.
                                                             (line    8)
* AUDIODEV:                              ossaudiodev --- Access to OSS-compatible audio devices.
                                                             (line   54)
* audioop (模組):                        audioop --- Manipulate raw audio data.
                                                             (line    6)
* AUDIO_FILE_ENCODING_ADPCM_G721 (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   98)
* AUDIO_FILE_ENCODING_ADPCM_G722 (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   98)
* AUDIO_FILE_ENCODING_ADPCM_G723_3 (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   98)
* AUDIO_FILE_ENCODING_ADPCM_G723_5 (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   98)
* AUDIO_FILE_ENCODING_ALAW_8 (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   88)
* AUDIO_FILE_ENCODING_DOUBLE (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   98)
* AUDIO_FILE_ENCODING_FLOAT (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   98)
* AUDIO_FILE_ENCODING_LINEAR_16 (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   88)
* AUDIO_FILE_ENCODING_LINEAR_24 (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   88)
* AUDIO_FILE_ENCODING_LINEAR_32 (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   88)
* AUDIO_FILE_ENCODING_LINEAR_8 (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   88)
* AUDIO_FILE_ENCODING_MULAW_8 (於 sunau 模組中): sunau --- Read and write Sun AU files.
                                                             (line   88)
* AUDIO_FILE_MAGIC (於 sunau 模組中):    sunau --- Read and write Sun AU files.
                                                             (line   82)
* audit events:                          Debugging and Profiling.
                                                             (line   11)
* audit() (於 sys 模組中):               sys --- System-specific parameters and functions.
                                                             (line   74)
* auditing:                              sys --- System-specific parameters and functions.
                                                             (line   76)
* augmented; assignment:                 Augmented assignment statements.
                                                             (line    6)
* auth() (ftplib.FTP_TLS 的方法):        FTP_TLS Objects.    (line   14)
* auth() (smtplib.SMTP 的方法):          SMTP Objects.       (line  141)
* authenticate() (imaplib.IMAP4 的方法): IMAP4 Objects.      (line   37)
* AuthenticationError:                   Process and exceptions.
                                                             (line  216)
* authenticators() (netrc.netrc 的方法): netrc Objects.      (line    8)
* authkey (multiprocessing.Process 的屬性): Process and exceptions.
                                                             (line  118)
* auto (enum 中的類別):                  Module Contents<2>. (line   39)
* autorange() (timeit.Timer 的方法):     Python Interface.   (line   89)
* avg() (於 audioop 模組中):             audioop --- Manipulate raw audio data.
                                                             (line   51)
* avgpp() (於 audioop 模組中):           audioop --- Manipulate raw audio data.
                                                             (line   55)
* avoids_symlink_attacks (shutil.rmtree 的屬性): Directory and files operations.
                                                             (line  293)
* AWAIT (於 token 模組中):               token --- Constants used with Python parse trees.
                                                             (line  244)
* await; in comprehensions:              Displays for lists sets and dictionaries.
                                                             (line   45)
* awaitable:                             Glossary.           (line  155)
* Awaitable (collections.abc 中的類別):  Collections Abstract Base Classes.
                                                             (line  194)
* Awaitable (typing 中的類別):           Classes functions and decorators.
                                                             (line  298)
* await_args (unittest.mock.AsyncMock 的屬性): The Mock Class.
                                                             (line  882)
* await_args_list (unittest.mock.AsyncMock 的屬性): The Mock Class.
                                                             (line  900)
* await_count (unittest.mock.AsyncMock 的屬性): The Mock Class.
                                                             (line  866)
* b"; bytes literal:                     String and Bytes literals.
                                                             (line   43)
* b’; bytes literal:                     String and Bytes literals.
                                                             (line   43)
* b16decode() (於 base64 模組中):        base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  124)
* b16encode() (於 base64 模組中):        base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  119)
* b2a_base64() (於 binascii 模組中):     binascii --- Convert between binary and ASCII.
                                                             (line   46)
* b2a_hex() (於 binascii 模組中):        binascii --- Convert between binary and ASCII.
                                                             (line  130)
* b2a_hqx() (於 binascii 模組中):        binascii --- Convert between binary and ASCII.
                                                             (line   99)
* b2a_qp() (於 binascii 模組中):         binascii --- Convert between binary and ASCII.
                                                             (line   62)
* b2a_uu() (於 binascii 模組中):         binascii --- Convert between binary and ASCII.
                                                             (line   32)
* b32decode() (於 base64 模組中):        base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   99)
* b32encode() (於 base64 模組中):        base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   94)
* b64decode() (於 base64 模組中):        base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   51)
* b64encode() (於 base64 模組中):        base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   39)
* b85decode() (於 base64 模組中):        base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  191)
* b85encode() (於 base64 模組中):        base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  180)
* Babyl (mailbox 中的類別):              Babyl.              (line    6)
* BabylMessage (mailbox 中的類別):       BabylMessage.       (line    6)
* back() (於 turtle 模組中):             Turtle motion.      (line   24)
* backslash character:                   Explicit line joining.
                                                             (line    6)
* backslashreplace_errors() (於 codecs 模組中): Error Handlers.
                                                             (line  151)
* backup() (sqlite3.Connection 的方法):  Connection Objects. (line  402)
* backward() (於 turtle 模組中):         Turtle motion.      (line   24)
* BadGzipFile:                           gzip --- Support for gzip files.
                                                             (line   62)
* BadStatusLine:                         http client --- HTTP protocol client.
                                                             (line  173)
* BadZipFile:                            zipfile --- Work with ZIP archives.
                                                             (line   24)
* BadZipfile:                            zipfile --- Work with ZIP archives.
                                                             (line   30)
* Balloon (tkinter.tix 中的類別):        Basic Widgets.      (line    6)
* Barrier (multiprocessing 中的類別):    Synchronization primitives.
                                                             (line   13)
* Barrier (threading 中的類別):          Barrier Objects.    (line   36)
* Barrier() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  143)
* base64 (模組):                         base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line    6)
* base64; encoding:                      base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line    8)
* BaseCGIHandler (wsgiref.handlers 中的類別): wsgiref handlers -- server/gateway base classes.
                                                             (line   53)
* BaseCookie (http.cookies 中的類別):    http cookies --- HTTP state management.
                                                             (line   38)
* BaseException:                         Base classes.       (line    9)
* BaseHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  271)
* BaseHandler (wsgiref.handlers 中的類別): wsgiref handlers -- server/gateway base classes.
                                                             (line   88)
* BaseHeader (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line   37)
* BaseHTTPRequestHandler (http.server 中的類別): http server --- HTTP servers.
                                                             (line   46)
* BaseManager (multiprocessing.managers 中的類別): Managers. (line   23)
* basename() (於 os.path 模組中):        os path --- Common pathname manipulations.
                                                             (line   62)
* 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<2>.  (line    6)
* basestring (2to3 fixer):               Fixers.             (line   60)
* BaseTransport (asyncio 中的類別):      Transports Hierarchy.
                                                             (line    6)
* base_exec_prefix (於 sys 模組中):      sys --- System-specific parameters and functions.
                                                             (line  105)
* base_prefix (於 sys 模組中):           sys --- System-specific parameters and functions.
                                                             (line  119)
* basicConfig() (於 logging 模組中):     Module-Level Functions.
                                                             (line  244)
* BasicContext (decimal 中的類別):       Context objects.    (line   47)
* BasicInterpolation (configparser 中的類別): Interpolation of values.
                                                             (line   10)
* BasicTestRunner (test.support 中的類別): test support --- Utilities for the Python test suite.
                                                             (line 1101)
* baudrate() (於 curses 模組中):         Functions<3>.       (line   18)
* bbox() (tkinter.ttk.Treeview 的方法):  ttk Treeview.       (line    8)
* BDADDR_ANY (於 socket 模組中):         Constants<8>.       (line  218)
* BDADDR_LOCAL (於 socket 模組中):       Constants<8>.       (line  218)
* Bdb (bdb 中的類別):                    bdb --- Debugger framework.
                                                             (line   79)
* bdb (模組):                            bdb --- Debugger framework.
                                                             (line    6)
* BdbQuit:                               bdb --- Debugger framework.
                                                             (line   15)
* BDFL:                                  Glossary.           (line  161)
* bdist_msi (distutils.command.bdist_msi 中的類別): distutils command bdist_msi --- Build a Microsoft Installer binary package.
                                                             (line    6)
* beep() (於 curses 模組中):             Functions<3>.       (line   26)
* Beep() (於 winsound 模組中):           winsound --- Sound-playing interface for Windows.
                                                             (line   12)
* BEFORE_ASYNC_WITH (opcode):            Python Bytecode Instructions.
                                                             (line  295)
* begin_fill() (於 turtle 模組中):       Filling.            (line   16)
* BEGIN_FINALLY (opcode):                Python Bytecode Instructions.
                                                             (line  406)
* begin_poly() (於 turtle 模組中):       Special Turtle methods.
                                                             (line    6)
* below() (curses.panel.Panel 的方法):   Panel Objects.      (line   17)
* BELOW_NORMAL_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   59)
* benchmarking:                          Functions<2>.       (line  182)
* benchmarking <1>:                      Functions<2>.       (line  200)
* benchmarking <2>:                      Functions<2>.       (line  479)
* Benchmarking:                          timeit --- Measure execution time of small code snippets.
                                                             (line    8)
* betavariate() (於 random 模組中):      Real-valued distributions.
                                                             (line   33)
* bgcolor() (於 turtle 模組中):          Window control.     (line    6)
* bgpic() (於 turtle 模組中):            Window control.     (line   21)
* bias() (於 audioop 模組中):            audioop --- Manipulate raw audio data.
                                                             (line   61)
* bidirectional() (於 unicodedata 模組中): unicodedata --- Unicode Database.
                                                             (line   54)
* bigaddrspacetest() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  675)
* BigEndianStructure (ctypes 中的類別):  Structured data types.
                                                             (line   10)
* bigmemtest() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  659)
* bin() (內建函式):                      內建函式.           (line   92)
* Binary (msilib 中的類別):              msilib --- Read and write Microsoft Installer files.
                                                             (line   89)
* Binary (xmlrpc.client 中的類別):       Binary Objects.     (line    6)
* binary file:                           Glossary.           (line  166)
* binary literal:                        Numeric literals.   (line    6)
* binary mode:                           內建函式.           (line 1215)
* binary semaphores:                     _thread --- Low-level threading API.
                                                             (line    6)
* binary; arithmetic; operation:         Binary arithmetic operations.
                                                             (line    6)
* binary; bitwise; operation:            Binary bitwise operations.
                                                             (line    6)
* binary; literals:                      Numeric Types --- int float complex.
                                                             (line   19)
* binaryfunc (C 型態):                   Slot Type typedefs. (line  111)
* BinaryIO (typing 中的類別):            Classes functions and decorators.
                                                             (line  470)
* BINARY_ADD (opcode):                   Python Bytecode Instructions.
                                                             (line  157)
* BINARY_AND (opcode):                   Python Bytecode Instructions.
                                                             (line  177)
* BINARY_FLOOR_DIVIDE (opcode):          Python Bytecode Instructions.
                                                             (line  145)
* BINARY_LSHIFT (opcode):                Python Bytecode Instructions.
                                                             (line  169)
* BINARY_MATRIX_MULTIPLY (opcode):       Python Bytecode Instructions.
                                                             (line  139)
* BINARY_MODULO (opcode):                Python Bytecode Instructions.
                                                             (line  153)
* BINARY_MULTIPLY (opcode):              Python Bytecode Instructions.
                                                             (line  135)
* BINARY_OR (opcode):                    Python Bytecode Instructions.
                                                             (line  185)
* BINARY_POWER (opcode):                 Python Bytecode Instructions.
                                                             (line  131)
* BINARY_RSHIFT (opcode):                Python Bytecode Instructions.
                                                             (line  173)
* BINARY_SUBSCR (opcode):                Python Bytecode Instructions.
                                                             (line  165)
* BINARY_SUBTRACT (opcode):              Python Bytecode Instructions.
                                                             (line  161)
* BINARY_TRUE_DIVIDE (opcode):           Python Bytecode Instructions.
                                                             (line  149)
* BINARY_XOR (opcode):                   Python Bytecode Instructions.
                                                             (line  181)
* binascii (模組):                       binascii --- Convert between binary and ASCII.
                                                             (line    6)
* bind (widgets):                        Bindings and Events.
                                                             (line    6)
* bind() (asyncore.dispatcher 的方法):   asyncore --- Asynchronous socket handler.
                                                             (line  221)
* bind() (inspect.Signature 的方法):     Introspecting callables with the Signature object.
                                                             (line   95)
* bind() (socket.socket 的方法):         Socket Objects.     (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)
* bind_partial() (inspect.Signature 的方法): Introspecting callables with the Signature object.
                                                             (line  102)
* bind_port() (於 test.support 模組中):  test support --- Utilities for the Python test suite.
                                                             (line  803)
* bind_textdomain_codeset() (於 gettext 模組中): GNU gettext API.
                                                             (line   26)
* bind_unix_socket() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  820)
* binhex (模組):                         binhex --- Encode and decode binhex4 files.
                                                             (line    6)
* binhex() (於 binhex 模組中):           binhex --- Encode and decode binhex4 files.
                                                             (line   16)
* bisect (模組):                         bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line    6)
* bisect() (於 bisect 模組中):           bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   30)
* bisect_left() (於 bisect 模組中):      bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   18)
* bisect_right() (於 bisect 模組中):     bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   30)
* bitmap() (msilib.Dialog 的方法):       GUI classes.        (line   60)
* bitwise; and:                          Binary bitwise operations.
                                                             (line   12)
* bitwise; operations:                   Bitwise Operations on Integer Types.
                                                             (line    6)
* bitwise; or:                           Binary bitwise operations.
                                                             (line   18)
* bitwise; xor:                          Binary bitwise operations.
                                                             (line   15)
* bit_length() (int 的方法):             Additional Methods on Integer Types.
                                                             (line    9)
* bk() (於 turtle 模組中):               Turtle motion.      (line   24)
* bkgd() (curses.window 的方法):         Window Objects.     (line   68)
* bkgdset() (curses.window 的方法):      Window Objects.     (line   80)
* blake2b() (於 hashlib 模組中):         Creating hash objects.
                                                             (line    8)
* blake2b, blake2s:                      BLAKE2.             (line    6)
* blake2b.MAX_DIGEST_SIZE (於 hashlib 模組中): Constants<5>. (line   24)
* blake2b.MAX_KEY_SIZE (於 hashlib 模組中): Constants<5>.    (line   18)
* blake2b.PERSON_SIZE (於 hashlib 模組中): Constants<5>.     (line   12)
* blake2b.SALT_SIZE (於 hashlib 模組中): Constants<5>.       (line    6)
* blake2s() (於 hashlib 模組中):         Creating hash objects.
                                                             (line   13)
* blake2s.MAX_DIGEST_SIZE (於 hashlib 模組中): Constants<5>. (line   26)
* blake2s.MAX_KEY_SIZE (於 hashlib 模組中): Constants<5>.    (line   20)
* blake2s.PERSON_SIZE (於 hashlib 模組中): Constants<5>.     (line   14)
* blake2s.SALT_SIZE (於 hashlib 模組中): Constants<5>.       (line    8)
* blank line:                            Blank lines.        (line    6)
* block:                                 Structure of a program.
                                                             (line    6)
* blocked_domains() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy Objects.
                                                             (line   52)
* BlockingIOError:                       OS exceptions.      (line    9)
* BlockingIOError <1>:                   High-level Module Interface.
                                                             (line   38)
* blocksize (http.client.HTTPConnection 的屬性): HTTPConnection Objects.
                                                             (line  114)
* block_size (hmac.HMAC 的屬性):         hmac --- Keyed-Hashing for Message Authentication.
                                                             (line   93)
* BNF:                                   Notation.           (line    6)
* BNF <1>:                               Expressions.        (line    6)
* body() (nntplib.NNTP 的方法):          Methods<3>.         (line  272)
* body_encode() (email.charset.Charset 的方法): email charset Representing character sets.
                                                             (line  135)
* body_encoding (email.charset.Charset 的屬性): email charset Representing character sets.
                                                             (line   67)
* body_line_iterator() (於 email.iterators 模組中): email iterators Iterators.
                                                             (line   14)
* BOM (於 codecs 模組中):                codecs --- Codec registry and base classes.
                                                             (line  241)
* BOM_BE (於 codecs 模組中):             codecs --- Codec registry and base classes.
                                                             (line  241)
* BOM_LE (於 codecs 模組中):             codecs --- Codec registry and base classes.
                                                             (line  241)
* BOM_UTF16 (於 codecs 模組中):          codecs --- Codec registry and base classes.
                                                             (line  241)
* BOM_UTF16_BE (於 codecs 模組中):       codecs --- Codec registry and base classes.
                                                             (line  241)
* BOM_UTF16_LE (於 codecs 模組中):       codecs --- Codec registry and base classes.
                                                             (line  241)
* BOM_UTF32 (於 codecs 模組中):          codecs --- Codec registry and base classes.
                                                             (line  241)
* BOM_UTF32_BE (於 codecs 模組中):       codecs --- Codec registry and base classes.
                                                             (line  241)
* BOM_UTF32_LE (於 codecs 模組中):       codecs --- Codec registry and base classes.
                                                             (line  241)
* BOM_UTF8 (於 codecs 模組中):           codecs --- Codec registry and base classes.
                                                             (line  241)
* bool (內建類別):                       內建函式.           (line  114)
* Boolean; operation:                    Boolean operations. (line    6)
* Boolean; operations:                   Truth Value Testing.
                                                             (line    6)
* Boolean; operations <1>:               Boolean Operations --- and or not.
                                                             (line    6)
* Boolean; type:                         內建函式.           (line  124)
* Boolean; values:                       Boolean Values.     (line   15)
* BOOLEAN_STATES (configparser.ConfigParser 的屬性): Customizing Parser Behaviour.
                                                             (line  245)
* bootstrap() (於 ensurepip 模組中):     Module API.         (line   13)
* border() (curses.window 的方法):       Window Objects.     (line   91)
* bottom() (curses.panel.Panel 的方法):  Panel Objects.      (line   21)
* bottom_panel() (於 curses.panel 模組中): Functions<4>.     (line    8)
* BoundArguments (inspect 中的類別):     Introspecting callables with the Signature object.
                                                             (line  275)
* BoundaryError:                         email errors Exception and Defect classes.
                                                             (line   38)
* BoundedSemaphore (asyncio 中的類別):   BoundedSemaphore.   (line    6)
* BoundedSemaphore (multiprocessing 中的類別): Synchronization primitives.
                                                             (line   19)
* BoundedSemaphore (threading 中的類別): Semaphore Objects.  (line   69)
* BoundedSemaphore() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  150)
* box() (curses.window 的方法):          Window Objects.     (line  130)
* bpformat() (bdb.Breakpoint 的方法):    bdb --- Debugger framework.
                                                             (line   55)
* bpprint() (bdb.Breakpoint 的方法):     bdb --- Debugger framework.
                                                             (line   74)
* break (pdb command):                   Debugger Commands.  (line   71)
* Breakpoint (bdb 中的類別):             bdb --- Debugger framework.
                                                             (line   22)
* breakpoint() (內建函式):               內建函式.           (line  126)
* breakpointhook() (於 sys 模組中):      sys --- System-specific parameters and functions.
                                                             (line  187)
* breakpoints:                           Help menu Shell and Editor.
                                                             (line   29)
* break_anywhere() (bdb.Bdb 的方法):     bdb --- Debugger framework.
                                                             (line  204)
* break_here() (bdb.Bdb 的方法):         bdb --- Debugger framework.
                                                             (line  197)
* break_long_words (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  238)
* break_on_hyphens (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  248)
* broadcast_address (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   91)
* broadcast_address (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  311)
* broken (threading.Barrier 的屬性):     Barrier Objects.    (line  101)
* BrokenBarrierError:                    Barrier Objects.    (line  106)
* BrokenExecutor:                        Exception classes.  (line   14)
* BrokenPipeError:                       OS exceptions.      (line   37)
* BrokenProcessPool:                     Exception classes.  (line   37)
* BrokenThreadPool:                      Exception classes.  (line   29)
* BROWSER:                               webbrowser --- Convenient Web-browser controller.
                                                             (line   20)
* BROWSER <1>:                           webbrowser --- Convenient Web-browser controller.
                                                             (line   95)
* BsdDbShelf (shelve 中的類別):          Restrictions.       (line   52)
* buf (multiprocessing.shared_memory.SharedMemory 的屬性): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line   87)
* buffer (2to3 fixer):                   Fixers.             (line   64)
* buffer (io.TextIOBase 的屬性):         Text I/O<2>.        (line   30)
* buffer (unittest.TestResult 的屬性):   Loading and running tests.
                                                             (line  276)
* buffer interface; (see buffer protocol): Iterator Protocol.
                                                             (line   45)
* buffer object; (see buffer protocol):  Iterator Protocol.  (line   44)
* buffer protocol:                       Iterator Protocol.  (line   45)
* buffer protocol; binary sequence types: printf-style String Formatting.
                                                             (line  189)
* buffer protocol; str (built-in class): Text Sequence Type --- str.
                                                             (line   60)
* buffer size, I/O:                      內建函式.           (line 1215)
* BufferedIOBase (io 中的類別):          I/O Base Classes.   (line  222)
* BufferedProtocol (asyncio 中的類別):   Base Protocols.     (line   15)
* BufferedRandom (io 中的類別):          Buffered Streams.   (line  134)
* BufferedReader (io 中的類別):          Buffered Streams.   (line   56)
* BufferedRWPair (io 中的類別):          Buffered Streams.   (line  147)
* BufferedWriter (io 中的類別):          Buffered Streams.   (line   95)
* BufferError:                           Base classes.       (line   49)
* BufferingHandler (logging.handlers 中的類別): MemoryHandler.
                                                             (line   19)
* BufferTooShort:                        Process and exceptions.
                                                             (line  208)
* buffer_info() (array.array 的方法):    array --- 高效率的數值型態陣列.
                                                             (line  110)
* buffer_size (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line   84)
* buffer_text (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line   91)
* buffer_updated() (asyncio.BufferedProtocol 的方法): Buffered Streaming Protocols.
                                                             (line   35)
* buffer_used (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line  100)
* bufsize() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line  211)
* BUILD_CONST_KEY_MAP (opcode):          Python Bytecode Instructions.
                                                             (line  557)
* BUILD_LIST (opcode):                   Python Bytecode Instructions.
                                                             (line  540)
* BUILD_LIST_UNPACK (opcode):            Python Bytecode Instructions.
                                                             (line  589)
* BUILD_MAP (opcode):                    Python Bytecode Instructions.
                                                             (line  548)
* BUILD_MAP_UNPACK (opcode):             Python Bytecode Instructions.
                                                             (line  605)
* BUILD_MAP_UNPACK_WITH_CALL (opcode):   Python Bytecode Instructions.
                                                             (line  613)
* build_opener() (於 urllib.request 模組中): urllib request --- Extensible library for opening URLs.
                                                             (line  125)
* build_py (distutils.command.build_py 中的類別): distutils command build_py --- Build the py/ pyc files of a package.
                                                             (line    6)
* build_py_2to3 (distutils.command.build_py 中的類別): distutils command build_py --- Build the py/ pyc files of a package.
                                                             (line    8)
* BUILD_SET (opcode):                    Python Bytecode Instructions.
                                                             (line  544)
* BUILD_SET_UNPACK (opcode):             Python Bytecode Instructions.
                                                             (line  597)
* BUILD_SLICE (opcode):                  Python Bytecode Instructions.
                                                             (line  859)
* BUILD_STRING (opcode):                 Python Bytecode Instructions.
                                                             (line  566)
* BUILD_TUPLE (opcode):                  Python Bytecode Instructions.
                                                             (line  535)
* BUILD_TUPLE_UNPACK (opcode):           Python Bytecode Instructions.
                                                             (line  573)
* BUILD_TUPLE_UNPACK_WITH_CALL (opcode): Python Bytecode Instructions.
                                                             (line  581)
* built-in function; call:               Calls.              (line  132)
* built-in method; call:                 Calls.              (line  132)
* built-in; method:                      The standard type hierarchy.
                                                             (line  497)
* built-in; types:                       內建型態.           (line    9)
* BuiltinFunctionType (於 types 模組中): Standard Interpreter Types.
                                                             (line   81)
* BuiltinImporter (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line   64)
* BuiltinMethodType (於 types 模組中):   Standard Interpreter Types.
                                                             (line   81)
* builtins (模組):                       builtins --- Built-in objects.
                                                             (line    6)
* builtin_module_names (於 sys 模組中):  sys --- System-specific parameters and functions.
                                                             (line  140)
* ButtonBox (tkinter.tix 中的類別):      Basic Widgets.      (line   13)
* bye() (於 turtle 模組中):              Methods specific to Screen not inherited from TurtleScreen.
                                                             (line    6)
* byref() (於 ctypes 模組中):            Utility functions.  (line   19)
* byte:                                  The standard type hierarchy.
                                                             (line  183)
* bytearray:                             The standard type hierarchy.
                                                             (line  207)
* bytearray (內建類別):                  Bytearray Objects.  (line    9)
* 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:                              The standard type hierarchy.
                                                             (line  648)
* bytecode <1>:                          Glossary.           (line  196)
* Bytecode (dis 中的類別):               Bytecode analysis.  (line   12)
* Bytecode.codeobj (於 dis 模組中):      Bytecode analysis.  (line   39)
* Bytecode.first_line (於 dis 模組中):   Bytecode analysis.  (line   43)
* BYTECODE_SUFFIXES (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   38)
* byteorder (於 sys 模組中):             sys --- System-specific parameters and functions.
                                                             (line  133)
* bytes:                                 The standard type hierarchy.
                                                             (line  183)
* bytes (uuid.UUID 的屬性):              uuid --- UUID objects according to RFC 4122.
                                                             (line   84)
* bytes (內建類別):                      Bytes Objects.      (line   12)
* bytes literal:                         Literals.           (line    8)
* bytes-like object:                     Glossary.           (line  177)
* 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 (built-in class):           Text Sequence Type --- str.
                                                             (line   60)
* BytesFeedParser (email.parser 中的類別): FeedParser API.   (line   28)
* BytesGenerator (email.generator 中的類別): email generator Generating MIME documents.
                                                             (line   43)
* BytesHeaderParser (email.parser 中的類別): Parser API.     (line   66)
* BytesIO (io 中的類別):                 Buffered Streams.   (line    9)
* BytesParser (email.parser 中的類別):   Parser API.         (line   17)
* ByteString (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  159)
* ByteString (typing 中的類別):          Classes functions and decorators.
                                                             (line  237)
* byteswap() (array.array 的方法):       array --- 高效率的數值型態陣列.
                                                             (line  123)
* byteswap() (於 audioop 模組中):        audioop --- Manipulate raw audio data.
                                                             (line   66)
* BytesWarning:                          Warnings.           (line   54)
* bytes_le (uuid.UUID 的屬性):           uuid --- UUID objects according to RFC 4122.
                                                             (line   89)
* byte_compile() (於 distutils.util 模組中): distutils util --- Miscellaneous other utility functions.
                                                             (line  127)
* bz2 (模組):                            bz2 --- Support for bzip2 compression.
                                                             (line    6)
* 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   72)
* C-contiguous:                          shape strides suboffsets.
                                                             (line   26)
* C-contiguous <1>:                      Glossary.           (line  273)
* C14NWriterTarget (xml.etree.ElementTree 中的類別): TreeBuilder Objects.
                                                             (line   93)
* C; language:                           The standard type hierarchy.
                                                             (line    6)
* C; language <1>:                       The standard type hierarchy.
                                                             (line  107)
* C; language <2>:                       The standard type hierarchy.
                                                             (line  484)
* C; language <3>:                       Comparisons.        (line    6)
* C; language <4>:                       Numeric Types --- int float complex.
                                                             (line    6)
* C; language <5>:                       Numeric Types --- int float complex.
                                                             (line  104)
* C; structures:                         struct --- Interpret bytes as packed binary data.
                                                             (line    8)
* CAB (msilib 中的類別):                 CAB Objects.        (line    6)
* cached (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  395)
* cached_property() (於 functools 模組中): functools --- Higher-order functions and operations on callable objects.
                                                             (line   16)
* CacheFTPHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  429)
* cache_from_source() (於 imp 模組中):   imp --- Access the import internals.
                                                             (line  203)
* cache_from_source() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   21)
* calcobjsize() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  530)
* calcsize() (於 struct 模組中):         Functions and Exceptions.
                                                             (line   55)
* calcvobjsize() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  535)
* Calendar (calendar 中的類別):          calendar --- General calendar-related functions.
                                                             (line   27)
* calendar (模組):                       calendar --- General calendar-related functions.
                                                             (line    6)
* calendar() (於 calendar 模組中):       calendar --- General calendar-related functions.
                                                             (line  349)
* call:                                  Slicings.           (line   38)
* call() (於 subprocess 模組中):         Older high-level API.
                                                             (line   10)
* call() (於 unittest.mock 模組中):      call.               (line    6)
* call; instance:                        Emulating callable objects.
                                                             (line    8)
* Callable (collections.abc 中的類別):   Collections Abstract Base Classes.
                                                             (line  116)
* Callable (於 typing 模組中):           Classes functions and decorators.
                                                             (line  861)
* callable() (內建函式):                 內建函式.           (line  193)
* CallableProxyType (於 weakref 模組中): weakref --- Weak references.
                                                             (line  296)
* callback:                              Glossary.           (line  211)
* callback (optparse.Option 的屬性):     Option attributes.  (line   60)
* callback() (contextlib.ExitStack 的方法): Utilities.       (line  414)
* callbacks (於 gc 模組中):              gc --- Garbage Collector interface.
                                                             (line  228)
* callback_args (optparse.Option 的屬性): Option attributes. (line   66)
* callback_kwargs (optparse.Option 的屬性): Option attributes.
                                                             (line   66)
* called (unittest.mock.Mock 的屬性):    The Mock Class.     (line  296)
* CalledProcessError:                    Using the subprocess Module.
                                                             (line  190)
* calloc():                              總覽<2>.            (line   33)
* call_args (unittest.mock.Mock 的屬性): The Mock Class.     (line  415)
* call_args_list (unittest.mock.Mock 的屬性): The Mock Class.
                                                             (line  459)
* call_at() (asyncio.loop 的方法):       Scheduling delayed callbacks.
                                                             (line   37)
* call_count (unittest.mock.Mock 的屬性): The Mock Class.    (line  308)
* call_exception_handler() (asyncio.loop 的方法): Error Handling API.
                                                             (line   37)
* CALL_FINALLY (opcode):                 Python Bytecode Instructions.
                                                             (line  702)
* CALL_FUNCTION (opcode):                Python Bytecode Instructions.
                                                             (line  768)
* CALL_FUNCTION_EX (opcode):             Python Bytecode Instructions.
                                                             (line  797)
* CALL_FUNCTION_KW (opcode):             Python Bytecode Instructions.
                                                             (line  781)
* call_later() (asyncio.loop 的方法):    Scheduling delayed callbacks.
                                                             (line   10)
* call_list() (unittest.mock.call 的方法): call.             (line   20)
* CALL_METHOD (opcode):                  Python Bytecode Instructions.
                                                             (line  827)
* call_soon() (asyncio.loop 的方法):     Scheduling callbacks.
                                                             (line    6)
* call_soon_threadsafe() (asyncio.loop 的方法): Scheduling callbacks.
                                                             (line   23)
* call_tracing() (於 sys 模組中):        sys --- System-specific parameters and functions.
                                                             (line  147)
* cancel() (asyncio.Future 的方法):      Future Object.      (line  108)
* cancel() (asyncio.Handle 的方法):      Callback Handles.   (line   11)
* cancel() (asyncio.Task 的方法):        Task Object.        (line   51)
* cancel() (concurrent.futures.Future 的方法): Future Objects.
                                                             (line   16)
* cancel() (sched.scheduler 的方法):     Scheduler Objects.  (line   41)
* cancel() (threading.Timer 的方法):     Timer Objects.      (line   35)
* cancelled() (asyncio.Future 的方法):   Future Object.      (line   66)
* cancelled() (asyncio.Handle 的方法):   Callback Handles.   (line   16)
* cancelled() (asyncio.Task 的方法):     Task Object.        (line  103)
* cancelled() (concurrent.futures.Future 的方法): Future Objects.
                                                             (line   24)
* CancelledError:                        Exception classes.  (line    6)
* CancelledError <1>:                    Exceptions<8>.      (line   17)
* cancel_dump_traceback_later() (於 faulthandler 模組中): Dumping the tracebacks after a timeout.
                                                             (line   29)
* cancel_join_thread() (multiprocessing.Queue 的方法): Pipes and Queues.
                                                             (line  181)
* CannotSendHeader:                      http client --- HTTP protocol client.
                                                             (line  165)
* CannotSendRequest:                     http client --- HTTP protocol client.
                                                             (line  161)
* canonic() (bdb.Bdb 的方法):            bdb --- Debugger framework.
                                                             (line   99)
* canonical() (decimal.Context 的方法):  Context objects.    (line  238)
* canonical() (decimal.Decimal 的方法):  Decimal objects.    (line  140)
* canonicalize() (於 xml.etree.ElementTree 模組中): Functions<6>.
                                                             (line    6)
* CAN_BCM (於 socket 模組中):            Constants<8>.       (line  107)
* can_change_color() (於 curses 模組中): Functions<3>.       (line   30)
* can_fetch() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- Parser for robots txt.
                                                             (line   33)
* CAN_ISOTP (於 socket 模組中):          Constants<8>.       (line  135)
* CAN_RAW_FD_FRAMES (於 socket 模組中):  Constants<8>.       (line  122)
* can_symlink() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  545)
* can_write_eof() (asyncio.StreamWriter 的方法): StreamWriter.
                                                             (line   47)
* can_write_eof() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   14)
* can_xattr() (於 test.support 模組中):  test support --- Utilities for the Python test suite.
                                                             (line  549)
* capa() (poplib.POP3 的方法):           POP3 Objects.       (line   24)
* capitalize() (bytearray 的方法):       Bytes and Bytearray Operations.
                                                             (line  402)
* capitalize() (bytes 的方法):           Bytes and Bytearray Operations.
                                                             (line  402)
* capitalize() (str 的方法):             String Methods<2>.  (line   22)
* captured_stderr() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  401)
* captured_stdin() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  401)
* captured_stdout() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  401)
* captureWarnings() (於 logging 模組中): Integration with the warnings module.
                                                             (line    9)
* capwords() (於 string 模組中):         Helper functions.   (line    6)
* casefold() (str 的方法):               String Methods<2>.  (line   31)
* cast() (memoryview 的方法):            Memory Views.       (line  267)
* cast() (於 ctypes 模組中):             Utility functions.  (line   33)
* cast() (於 typing 模組中):             Classes functions and decorators.
                                                             (line  616)
* cat() (於 nis 模組中):                 nis --- Interface to Sun's NIS Yellow Pages.
                                                             (line   29)
* catch_threading_exception() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  825)
* catch_unraisable_exception() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  860)
* catch_warnings (warnings 中的類別):    Available Context Managers.
                                                             (line    6)
* category() (於 unicodedata 模組中):    unicodedata --- Unicode Database.
                                                             (line   49)
* cbreak() (於 curses 模組中):           Functions<3>.       (line   35)
* CC:                                    New Improved and Deprecated Modules<4>.
                                                             (line   58)
* ccc() (ftplib.FTP_TLS 的方法):         FTP_TLS Objects.    (line   23)
* CCompiler (distutils.ccompiler 中的類別): distutils ccompiler --- CCompiler base class.
                                                             (line   66)
* cdf() (statistics.NormalDist 的方法):  NormalDist objects. (line   80)
* CDLL (ctypes 中的類別):                Loading shared libraries.
                                                             (line    9)
* ceil() (in module math):               Numeric Types --- int float complex.
                                                             (line  104)
* ceil() (於 math 模組中):               Number-theoretic and representation functions.
                                                             (line    6)
* CellType (於 types 模組中):            Standard Interpreter Types.
                                                             (line   70)
* center() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line  235)
* center() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line  235)
* center() (str 的方法):                 String Methods<2>.  (line   47)
* CertificateError:                      Exceptions<11>.     (line   94)
* certificates:                          SSL Contexts.       (line  673)
* CERT_NONE (於 ssl 模組中):             Constants<9>.       (line   11)
* CERT_OPTIONAL (於 ssl 模組中):         Constants<9>.       (line   25)
* CERT_REQUIRED (於 ssl 模組中):         Constants<9>.       (line   43)
* cert_store_stats() (ssl.SSLContext 的方法): SSL Contexts.  (line   67)
* cert_time_to_seconds() (於 ssl 模組中): Certificate handling.
                                                             (line   48)
* CFLAGS:                                New Improved and Deprecated Modules<4>.
                                                             (line   58)
* CFLAGS <1>:                            Tweaking compiler/linker flags.
                                                             (line   66)
* CFLAGS <2>:                            Tweaking compiler/linker flags.
                                                             (line   67)
* CFUNCTYPE() (於 ctypes 模組中):        Function prototypes.
                                                             (line   15)
* cgi (模組):                            cgi --- Common Gateway Interface support.
                                                             (line    6)
* CGI; debugging:                        Debugging CGI scripts.
                                                             (line    6)
* CGI; exceptions:                       cgitb --- Traceback manager for CGI scripts.
                                                             (line    8)
* CGI; protocol:                         cgi --- Common Gateway Interface support.
                                                             (line    8)
* CGI; security:                         Caring about security.
                                                             (line    6)
* CGI; tracebacks:                       cgitb --- Traceback manager for CGI scripts.
                                                             (line    8)
* CGIHandler (wsgiref.handlers 中的類別): wsgiref handlers -- server/gateway base classes.
                                                             (line   11)
* CGIHTTPRequestHandler (http.server 中的類別): http server --- HTTP servers.
                                                             (line  448)
* cgitb (模組):                          cgitb --- Traceback manager for CGI scripts.
                                                             (line    6)
* CGIXMLRPCRequestHandler (xmlrpc.server 中的類別): xmlrpc server --- Basic XML-RPC servers.
                                                             (line   45)
* cgi_directories (http.server.CGIHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  474)
* chain() (於 itertools 模組中):         Itertool functions. (line   85)
* chaining; comparisons:                 Comparisons.        (line   17)
* chaining; comparisons <1>:             Comparisons<2>.     (line    6)
* ChainMap (collections 中的類別):       ChainMap objects.   (line   16)
* ChainMap (typing 中的類別):            Classes functions and decorators.
                                                             (line  382)
* change_cwd() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  435)
* change_root() (於 distutils.util 模組中): distutils util --- Miscellaneous other utility functions.
                                                             (line   64)
* channels() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line  130)
* CHANNEL_BINDING_TYPES (於 ssl 模組中): Constants<9>.       (line  437)
* channel_class (smtpd.SMTPServer 的屬性): SMTPServer Objects.
                                                             (line   80)
* character:                             The standard type hierarchy.
                                                             (line  156)
* character <1>:                         Subscriptions.      (line   38)
* character <2>:                         unicodedata --- Unicode Database.
                                                             (line    6)
* CharacterDataHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  240)
* characters() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line  129)
* characters_written (BlockingIOError 的屬性): OS exceptions.
                                                             (line   18)
* Charset (email.charset 中的類別):      email charset Representing character sets.
                                                             (line   24)
* charset() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   83)
* CHAR_MAX (於 locale 模組中):           locale --- Internationalization services.
                                                             (line  502)
* chdir() (於 os 模組中):                Files and Directories.
                                                             (line  115)
* check (lzma.LZMADecompressor 的屬性):  Compressing and decompressing data in memory.
                                                             (line  159)
* check() (imaplib.IMAP4 的方法):        IMAP4 Objects.      (line   58)
* check() (於 tabnanny 模組中):          tabnanny --- Detection of ambiguous indentation.
                                                             (line   17)
* checkbox() (msilib.Dialog 的方法):     GUI classes.        (line   78)
* checkcache() (於 linecache 模組中):    linecache --- Random access to text lines.
                                                             (line   43)
* CHECKED_HASH (py_compile.PycInvalidationMode 的屬性): py_compile --- Compile Python source files.
                                                             (line  108)
* checkfuncname() (於 bdb 模組中):       bdb --- Debugger framework.
                                                             (line  386)
* CheckList (tkinter.tix 中的類別):      Hierarchical ListBox.
                                                             (line   13)
* checksizeof() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  540)
* checksum; Cyclic Redundancy Check:     zlib --- Compression compatible with gzip.
                                                             (line  115)
* check_call() (於 subprocess 模組中):   Older high-level API.
                                                             (line   36)
* check_environ() (於 distutils.util 模組中): distutils util --- Miscellaneous other utility functions.
                                                             (line   71)
* check_free_after_iterating() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  955)
* check_hostname (ssl.SSLContext 的屬性): SSL Contexts.      (line  493)
* check_impl_detail() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  287)
* check_no_resource_warning() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  364)
* check_output() (doctest.OutputChecker 的方法): OutputChecker objects.
                                                             (line   17)
* check_output() (於 subprocess 模組中): Older high-level API.
                                                             (line   64)
* check_returncode() (subprocess.CompletedProcess 的方法): Using the subprocess Module.
                                                             (line  125)
* check_syntax_error() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  685)
* check_syntax_warning() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  696)
* check_unused_args() (string.Formatter 的方法): Custom String Formatting.
                                                             (line   91)
* check_warnings() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  296)
* check__all__() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  967)
* chflags() (於 os 模組中):              Files and Directories.
                                                             (line  134)
* chgat() (curses.window 的方法):        Window Objects.     (line  136)
* childNodes (xml.dom.Node 的屬性):      Node Objects.       (line   49)
* ChildProcessError:                     OS exceptions.      (line   24)
* children (pyclbr.Class 的屬性):        Class Objects<2>.   (line   31)
* children (pyclbr.Function 的屬性):     函式物件.           (line   31)
* chmod() (pathlib.Path 的方法):         Methods<2>.         (line   47)
* chmod() (於 os 模組中):                Files and Directories.
                                                             (line  175)
* choice() (於 random 模組中):           Functions for sequences.
                                                             (line    6)
* choice() (於 secrets 模組中):          Random numbers.     (line   15)
* choices (optparse.Option 的屬性):      Option attributes.  (line   55)
* choices() (於 random 模組中):          Functions for sequences.
                                                             (line   11)
* chown() (於 os 模組中):                Files and Directories.
                                                             (line  236)
* chown() (於 shutil 模組中):            Directory and files operations.
                                                             (line  353)
* chr() (內建函式):                      內建函式.           (line  205)
* chroot() (於 os 模組中):               Files and Directories.
                                                             (line  259)
* Chunk (chunk 中的類別):                chunk --- Read IFF chunked data.
                                                             (line   49)
* chunk (模組):                          chunk --- Read IFF chunked data.
                                                             (line    6)
* cipher() (ssl.SSLSocket 的方法):       SSL Sockets.        (line  207)
* cipher; DES:                           crypt --- Function to check Unix passwords.
                                                             (line    8)
* circle() (於 turtle 模組中):           Turtle motion.      (line  177)
* CIRCUMFLEX (於 token 模組中):          token --- Constants used with Python parse trees.
                                                             (line  154)
* CIRCUMFLEXEQUAL (於 token 模組中):     token --- Constants used with Python parse trees.
                                                             (line  198)
* Clamped (decimal 中的類別):            Signals.            (line   20)
* class:                                 Glossary.           (line  216)
* Class (symtable 中的類別):             Examining Symbol Tables.
                                                             (line   93)
* Class browser:                         File menu Shell and Editor.
                                                             (line   22)
* class instance; attribute:             The standard type hierarchy.
                                                             (line  599)
* class instance; attribute; assignment: The standard type hierarchy.
                                                             (line  615)
* class instance; call:                  Calls.              (line  141)
* class object; call:                    The standard type hierarchy.
                                                             (line  572)
* class object; call <1>:                The standard type hierarchy.
                                                             (line  584)
* class object; call <2>:                Calls.              (line  137)
* class variable:                        Glossary.           (line  222)
* class; attribute:                      The standard type hierarchy.
                                                             (line  572)
* class; attribute; assignment:          The standard type hierarchy.
                                                             (line  581)
* class; body:                           Executing the class body.
                                                             (line    6)
* class; constructor:                    Basic customization.
                                                             (line   40)
* class; definition:                     The return statement.
                                                             (line    6)
* class; definition <1>:                 Class definitions.  (line    6)
* class; instance:                       The standard type hierarchy.
                                                             (line  599)
* class; name:                           Class definitions.  (line    6)
* classmethod() (內建函式):              內建函式.           (line  216)
* ClassMethodDescriptorType (於 types 模組中): Standard Interpreter Types.
                                                             (line  110)
* ClassVar (於 typing 模組中):           Classes functions and decorators.
                                                             (line  901)
* clause:                                Compound statements.
                                                             (line   18)
* CLD_CONTINUED (於 os 模組中):          Process Management. (line  758)
* CLD_DUMPED (於 os 模組中):             Process Management. (line  758)
* CLD_EXITED (於 os 模組中):             Process Management. (line  758)
* CLD_TRAPPED (於 os 模組中):            Process Management. (line  758)
* clean() (mailbox.Maildir 的方法):      Maildir.            (line   82)
* cleandoc() (於 inspect 模組中):        Retrieving source code.
                                                             (line   65)
* CleanImport (test.support 中的類別):   test support --- Utilities for the Python test suite.
                                                             (line 1059)
* cleanup functions:                     行程（Process）控制.
                                                             (line   26)
* clear (pdb command):                   Debugger Commands.  (line   93)
* Clear Breakpoint:                      Help menu Shell and Editor.
                                                             (line   30)
* clear() (asyncio.Event 的方法):        Event.              (line   59)
* clear() (collections.deque 的方法):    deque objects.      (line   43)
* clear() (curses.window 的方法):        Window Objects.     (line  152)
* clear() (dict 的方法):                 Mapping Types --- dict.
                                                             (line  142)
* clear() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  667)
* clear() (frame 的方法):                The standard type hierarchy.
                                                             (line  743)
* clear() (frozenset 的方法):            Set Types --- set frozenset.
                                                             (line  213)
* clear() (http.cookiejar.CookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line   77)
* clear() (mailbox.Mailbox 的方法):      Mailbox objects.    (line  204)
* clear() (sequence method):             Mutable Sequence Types.
                                                             (line   16)
* clear() (threading.Event 的方法):      Event Objects.      (line   33)
* clear() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line   58)
* clear() (於 turtle 模組中):            Window control.     (line   39)
* clearcache() (於 linecache 模組中):    linecache --- Random access to text lines.
                                                             (line   38)
* ClearData() (msilib.Record 的方法):    Record Objects.     (line   37)
* clearok() (curses.window 的方法):      Window Objects.     (line  157)
* clearscreen() (於 turtle 模組中):      Window control.     (line   39)
* clearstamp() (於 turtle 模組中):       Turtle motion.      (line  249)
* clearstamps() (於 turtle 模組中):      Turtle motion.      (line  268)
* clear_all_breaks() (bdb.Bdb 的方法):   bdb --- Debugger framework.
                                                             (line  305)
* clear_all_file_breaks() (bdb.Bdb 的方法): bdb --- Debugger framework.
                                                             (line  300)
* clear_bpbynumber() (bdb.Bdb 的方法):   bdb --- Debugger framework.
                                                             (line  294)
* clear_break() (bdb.Bdb 的方法):        bdb --- Debugger framework.
                                                             (line  289)
* clear_cache() (於 filecmp 模組中):     filecmp --- File and Directory Comparisons.
                                                             (line   53)
* clear_content() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  671)
* clear_flags() (decimal.Context 的方法): Context objects.   (line  152)
* clear_frames() (於 traceback 模組中):  traceback --- Print or retrieve a stack traceback.
                                                             (line  150)
* clear_history() (於 readline 模組中):  History list.       (line    8)
* clear_session_cookies() (http.cookiejar.CookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line   89)
* clear_traces() (於 tracemalloc 模組中): Functions<9>.      (line    6)
* clear_traps() (decimal.Context 的方法): Context objects.   (line  156)
* Client() (於 multiprocessing.connection 模組中): Listeners and Clients.
                                                             (line   34)
* client_address (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line   66)
* CLOCK_BOOTTIME (於 time 模組中):       Clock ID Constants. (line    9)
* clock_getres() (於 time 模組中):       Functions<2>.       (line   38)
* clock_gettime() (於 time 模組中):      Functions<2>.       (line   48)
* clock_gettime_ns() (於 time 模組中):   Functions<2>.       (line   58)
* 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_PROCESS_CPUTIME_ID (於 time 模組中): Clock ID Constants.
                                                             (line   53)
* CLOCK_PROF (於 time 模組中):           Clock ID Constants. (line   61)
* CLOCK_REALTIME (於 time 模組中):       Clock ID Constants. (line  100)
* clock_settime() (於 time 模組中):      Functions<2>.       (line   67)
* clock_settime_ns() (於 time 模組中):   Functions<2>.       (line   76)
* CLOCK_THREAD_CPUTIME_ID (於 time 模組中): Clock ID Constants.
                                                             (line   69)
* CLOCK_UPTIME (於 time 模組中):         Clock ID Constants. (line   77)
* CLOCK_UPTIME_RAW (於 time 模組中):     Clock ID Constants. (line   87)
* clone() (email.generator.BytesGenerator 的方法): email generator Generating MIME documents.
                                                             (line  112)
* clone() (email.generator.Generator 的方法): email generator Generating MIME documents.
                                                             (line  208)
* clone() (email.policy.Policy 的方法):  email policy Policy Objects.
                                                             (line  207)
* clone() (pipes.Template 的方法):       Template Objects.   (line   12)
* clone() (於 turtle 模組中):            Special Turtle methods.
                                                             (line   32)
* cloneNode() (xml.dom.Node 的方法):     Node Objects.       (line  147)
* close() (aifc.aifc 的方法):            aifc --- Read and write AIFF and AIFC files.
                                                             (line  115)
* close() (asyncio.AbstractChildWatcher 的方法): Process Watchers.
                                                             (line   77)
* close() (asyncio.BaseTransport 的方法): Base Transport.    (line    6)
* close() (asyncio.loop 的方法):         Running and stopping the loop.
                                                             (line   43)
* close() (asyncio.Server 的方法):       Server Objects.     (line   29)
* close() (asyncio.StreamWriter 的方法): StreamWriter.       (line   37)
* close() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   59)
* close() (asyncore.dispatcher 的方法):  asyncore --- Asynchronous socket handler.
                                                             (line  242)
* close() (chunk.Chunk 的方法):          chunk --- Read IFF chunked data.
                                                             (line   78)
* close() (contextlib.ExitStack 的方法): Utilities.          (line  446)
* close() (coroutine 的方法):            Coroutine Objects.  (line   45)
* close() (dbm.dumb.dumbdbm 的方法):     dbm dumb --- Portable DBM implementation.
                                                             (line   83)
* close() (dbm.gnu.gdbm 的方法):         dbm gnu --- GNU's reinterpretation of dbm.
                                                             (line  118)
* close() (dbm.ndbm.ndbm 的方法):        dbm ndbm --- Interface based on ndbm.
                                                             (line   66)
* close() (distutils.text_file.TextFile 的方法): distutils text_file --- The TextFile class.
                                                             (line   96)
* close() (email.parser.BytesFeedParser 的方法): FeedParser API.
                                                             (line   64)
* close() (ftplib.FTP 的方法):           FTP Objects.        (line  246)
* close() (generator 的方法):            Generator-iterator methods.
                                                             (line   47)
* close() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line   15)
* close() (http.client.HTTPConnection 的方法): HTTPConnection Objects.
                                                             (line  110)
* close() (imaplib.IMAP4 的方法):        IMAP4 Objects.      (line   62)
* close() (in module os):                Sub-interpreter support.
                                                             (line   76)
* close() (io.IOBase 的方法):            I/O Base Classes.   (line   49)
* close() (logging.FileHandler 的方法):  FileHandler.        (line   23)
* close() (logging.Handler 的方法):      Handler Objects.    (line   73)
* close() (logging.handlers.MemoryHandler 的方法): MemoryHandler.
                                                             (line   55)
* close() (logging.handlers.NTEventLogHandler 的方法): NTEventLogHandler.
                                                             (line   29)
* close() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   20)
* close() (logging.handlers.SysLogHandler 的方法): SysLogHandler.
                                                             (line   39)
* close() (mailbox.Mailbox 的方法):      Mailbox objects.    (line  262)
* close() (mailbox.Maildir 的方法):      Maildir.            (line  113)
* close() (mailbox.MH 的方法):           MH.                 (line  104)
* close() (mmap.mmap 的方法):            mmap --- Memory-mapped file support.
                                                             (line  165)
* Close() (msilib.Database 的方法):      Database Objects.   (line   22)
* Close() (msilib.View 的方法):          View Objects.       (line   35)
* close() (multiprocessing.connection.Connection 的方法): Connection Objects<2>.
                                                             (line   35)
* close() (multiprocessing.connection.Listener 的方法): Listeners and Clients.
                                                             (line   91)
* close() (multiprocessing.pool.Pool 的方法): Process Pools. (line  168)
* close() (multiprocessing.Process 的方法): Process and exceptions.
                                                             (line  173)
* close() (multiprocessing.Queue 的方法): Pipes and Queues.  (line  162)
* close() (multiprocessing.shared_memory.SharedMemory 的方法): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line   65)
* close() (os.scandir 的方法):           Files and Directories.
                                                             (line  777)
* close() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line   22)
* close() (ossaudiodev.oss_mixer_device 的方法): Mixer Device Objects.
                                                             (line    8)
* 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   71)
* close() (socket.socket 的方法):        Socket Objects.     (line   39)
* close() (sqlite3.Connection 的方法):   Connection Objects. (line   45)
* close() (sqlite3.Cursor 的方法):       Cursor Objects.     (line  169)
* close() (sunau.AU_read 的方法):        AU_read Objects.    (line    9)
* close() (sunau.AU_write 的方法):       AU_write Objects.   (line   57)
* close() (tarfile.TarFile 的方法):      TarFile Objects.    (line  246)
* close() (telnetlib.Telnet 的方法):     Telnet Objects.     (line   89)
* close() (urllib.request.BaseHandler 的方法): BaseHandler Objects.
                                                             (line   14)
* close() (wave.Wave_read 的方法):       Wave_read Objects.  (line    9)
* close() (wave.Wave_write 的方法):      Wave_write Objects. (line   23)
* Close() (winreg.PyHKEY 的方法):        Registry Handle Objects.
                                                             (line   34)
* close() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder Objects.
                                                             (line   28)
* close() (xml.etree.ElementTree.XMLParser 的方法): XMLParser Objects.
                                                             (line   20)
* close() (xml.etree.ElementTree.XMLPullParser 的方法): XMLPullParser Objects.
                                                             (line   22)
* close() (xml.sax.xmlreader.IncrementalParser 的方法): IncrementalParser Objects.
                                                             (line   13)
* close() (zipfile.ZipFile 的方法):      ZipFile Objects.    (line   86)
* close() (於 fileinput 模組中):         fileinput --- Iterate over lines from multiple input streams.
                                                             (line  127)
* close() (於 os 模組中):                File Descriptor Operations.
                                                             (line   21)
* close() (於 socket 模組中):            Other functions<2>. (line    9)
* closed (http.client.HTTPResponse 的屬性): HTTPResponse Objects.
                                                             (line   65)
* closed (io.IOBase 的屬性):             I/O Base Classes.   (line   59)
* closed (mmap.mmap 的屬性):             mmap --- Memory-mapped file support.
                                                             (line  171)
* closed (ossaudiodev.oss_audio_device 的屬性): Audio Device Objects.
                                                             (line  227)
* 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 模組中):         Functions<11>.      (line    8)
* closelog() (於 syslog 模組中):         syslog --- Unix syslog library routines.
                                                             (line   59)
* closerange() (於 os 模組中):           File Descriptor Operations.
                                                             (line   32)
* close_connection (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line   75)
* close_when_done() (asynchat.async_chat 的方法): asynchat --- Asynchronous socket command/response handler.
                                                             (line   73)
* closing() (於 contextlib 模組中):      Utilities.          (line  121)
* clrtobot() (curses.window 的方法):     Window Objects.     (line  162)
* clrtoeol() (curses.window 的方法):     Window Objects.     (line  168)
* cmath (模組):                          cmath --- Mathematical functions for complex numbers.
                                                             (line    6)
* Cmd (cmd 中的類別):                    cmd --- Support for line-oriented command interpreters.
                                                             (line   15)
* cmd (subprocess.CalledProcessError 的屬性): Using the subprocess Module.
                                                             (line  201)
* cmd (subprocess.TimeoutExpired 的屬性): Using the subprocess Module.
                                                             (line  164)
* cmd (模組):                            cmd --- Support for line-oriented command interpreters.
                                                             (line    6)
* cmdloop() (cmd.Cmd 的方法):            Cmd Objects.        (line    8)
* cmdqueue (cmd.Cmd 的屬性):             Cmd Objects.        (line  135)
* cmp() (於 filecmp 模組中):             filecmp --- File and Directory Comparisons.
                                                             (line   16)
* cmpfiles() (於 filecmp 模組中):        filecmp --- File and Directory Comparisons.
                                                             (line   33)
* cmp_op (於 dis 模組中):                Opcode collections. (line   17)
* cmp_to_key() (於 functools 模組中):    functools --- Higher-order functions and operations on callable objects.
                                                             (line   48)
* CMSG_LEN() (於 socket 模組中):         Other functions<2>. (line  294)
* CMSG_SPACE() (於 socket 模組中):       Other functions<2>. (line  309)
* code (SystemExit 的屬性):              Concrete exceptions.
                                                             (line  321)
* code (urllib.error.HTTPError 的屬性):  urllib error --- Exception classes raised by urllib request.
                                                             (line   38)
* code (xml.etree.ElementTree.ParseError 的屬性): Exceptions<13>.
                                                             (line   14)
* code (xml.parsers.expat.ExpatError 的屬性): ExpatError Exceptions.
                                                             (line    9)
* code (模組):                           code --- Interpreter base classes.
                                                             (line    6)
* code object:                           The standard type hierarchy.
                                                             (line  648)
* code object <1>:                       Methods.            (line   42)
* code object <2>:                       marshal --- Internal Python object serialization.
                                                             (line   30)
* code object <3>:                       Cell 物件.          (line   51)
* code; block:                           Execution model.    (line    6)
* CodecInfo (codecs 中的類別):           codecs --- Codec registry and base classes.
                                                             (line   58)
* Codecs:                                codecs --- Codec registry and base classes.
                                                             (line    8)
* codecs (模組):                         codecs --- Codec registry and base classes.
                                                             (line    6)
* Codecs; decode:                        codecs --- Codec registry and base classes.
                                                             (line    8)
* Codecs; encode:                        codecs --- Codec registry and base classes.
                                                             (line    8)
* coded_value (http.cookies.Morsel 的屬性): Morsel Objects.  (line   56)
* codeop (模組):                         codeop --- Compile Python code.
                                                             (line    6)
* codepoint2name (於 html.entities 模組中): html entities --- Definitions of HTML general entities.
                                                             (line   35)
* codes (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   16)
* CODESET (於 locale 模組中):            locale --- Internationalization services.
                                                             (line  184)
* CodeType (types 中的類別):             Standard Interpreter Types.
                                                             (line   50)
* code_info() (於 dis 模組中):           Analysis functions. (line   11)
* coding; style:                         Intermezzo Coding Style.
                                                             (line    6)
* coercion:                              Glossary.           (line  227)
* collapse_addresses() (於 ipaddress 模組中): Other Module Level Functions.
                                                             (line   43)
* collapse_rfc2231_value() (於 email.utils 模組中): email utils Miscellaneous utilities.
                                                             (line  186)
* collect() (於 gc 模組中):              gc --- Garbage Collector interface.
                                                             (line   34)
* Collection (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  131)
* Collection (typing 中的類別):          Classes functions and decorators.
                                                             (line  203)
* collections (模組):                    collections --- 容器資料型態.
                                                             (line    6)
* collections.abc (模組):                collections abc --- Abstract Base Classes for Containers.
                                                             (line    6)
* collect_incoming_data() (asynchat.async_chat 的方法): asynchat --- Asynchronous socket command/response handler.
                                                             (line   78)
* colno (json.JSONDecodeError 的屬性):   例外<2>.            (line   27)
* colno (re.error 的屬性):               Module Contents.    (line  377)
* COLON (於 token 模組中):               token --- Constants used with Python parse trees.
                                                             (line   70)
* COLONEQUAL (於 token 模組中):          token --- Constants used with Python parse trees.
                                                             (line  238)
* color() (於 turtle 模組中):            Color control.      (line  104)
* colormode() (於 turtle 模組中):        Settings and special methods.
                                                             (line   33)
* colorsys (模組):                       colorsys --- Conversions between color systems.
                                                             (line    6)
* color_content() (於 curses 模組中):    Functions<3>.       (line   45)
* color_pair() (於 curses 模組中):       Functions<3>.       (line   53)
* COLS:                                  curses<2>.          (line    7)
* COLS <1>:                              Functions<3>.       (line  526)
* column() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line   35)
* COLUMNS:                               Functions<3>.       (line  550)
* COLUMNS <1>:                           Functions<3>.       (line  553)
* columns (os.terminal_size 的屬性):     Querying the size of a terminal.
                                                             (line   30)
* col_offset (ast.AST 的屬性):           Node classes.       (line   39)
* comb() (於 math 模組中):               Number-theoretic and representation functions.
                                                             (line   12)
* combinations() (於 itertools 模組中):  Itertool functions. (line  110)
* combinations_with_replacement() (於 itertools 模組中): Itertool functions.
                                                             (line  161)
* combine() (datetime.datetime 的類別成員): datetime Objects.
                                                             (line  170)
* combining() (於 unicodedata 模組中):   unicodedata --- Unicode Database.
                                                             (line   59)
* ComboBox (tkinter.tix 中的類別):       Basic Widgets.      (line   18)
* Combobox (tkinter.ttk 中的類別):       ttk Combobox.       (line    6)
* comma:                                 Parenthesized forms.
                                                             (line   20)
* COMMA (於 token 模組中):               token --- Constants used with Python parse trees.
                                                             (line   74)
* Command (distutils.cmd 中的類別):      distutils cmd --- Abstract base class for Distutils commands.
                                                             (line    8)
* Command (distutils.core 中的類別):     distutils core --- Core Distutils functionality.
                                                             (line  307)
* command (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line   88)
* command line:                          Complete Python programs.
                                                             (line   25)
* command line option; -?:               Generic options.    (line    6)
* command line option; -b:               Miscellaneous options.
                                                             (line    6)
* command line option; -B:               Miscellaneous options.
                                                             (line   16)
* command line option; -c <command>:     Interface options.  (line   36)
* command line option; –check-hash-based-pycs default|always|never: Miscellaneous options.
                                                             (line   21)
* command line option; -d:               Miscellaneous options.
                                                             (line   35)
* command line option; -E:               Miscellaneous options.
                                                             (line   40)
* command line option; -h:               Generic options.    (line    6)
* command line option; –help:            Generic options.    (line    6)
* command line option; -i:               Miscellaneous options.
                                                             (line   45)
* command line option; -I:               Miscellaneous options.
                                                             (line   56)
* command line option; -J:               Options you shouldn't use.
                                                             (line    6)
* command line option; -m <module-name>: Interface options.  (line   50)
* command line option; -O:               Miscellaneous options.
                                                             (line   66)
* command line option; -OO:              Miscellaneous options.
                                                             (line   75)
* command line option; -q:               Miscellaneous options.
                                                             (line   83)
* command line option; -R:               Miscellaneous options.
                                                             (line   90)
* command line option; -s:               Miscellaneous options.
                                                             (line  115)
* command line option; -S:               Miscellaneous options.
                                                             (line  125)
* command line option; -u:               Miscellaneous options.
                                                             (line  133)
* command line option; -V:               Generic options.    (line   12)
* command line option; -v:               Miscellaneous options.
                                                             (line  143)
* command line option; –version:         Generic options.    (line   12)
* command line option; -W arg:           Miscellaneous options.
                                                             (line  150)
* command line option; -x:               Miscellaneous options.
                                                             (line  189)
* command line option; -X:               Miscellaneous options.
                                                             (line  194)
* CommandCompiler (codeop 中的類別):     codeop --- Compile Python code.
                                                             (line   64)
* commands (pdb command):                Debugger Commands.  (line  126)
* comment:                               Comments.           (line    6)
* comment (http.cookiejar.Cookie 的屬性): Cookie Objects<2>. (line   58)
* comment (zipfile.ZipFile 的屬性):      ZipFile Objects.    (line  306)
* comment (zipfile.ZipInfo 的屬性):      ZipInfo Objects.    (line   88)
* COMMENT (於 token 模組中):             token --- Constants used with Python parse trees.
                                                             (line  261)
* comment() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder Objects.
                                                             (line   49)
* Comment() (於 xml.etree.ElementTree 模組中): Functions<6>. (line   72)
* commenters (shlex.shlex 的屬性):       shlex Objects.      (line   85)
* CommentHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  295)
* comment_url (http.cookiejar.Cookie 的屬性): Cookie Objects<2>.
                                                             (line   63)
* commit() (msilib.CAB 的方法):          CAB Objects.        (line   24)
* Commit() (msilib.Database 的方法):     Database Objects.   (line   11)
* commit() (sqlite3.Connection 的方法):  Connection Objects. (line   32)
* common (filecmp.dircmp 的屬性):        The dircmp class.   (line   59)
* Common Gateway Interface:              cgi --- Common Gateway Interface support.
                                                             (line    8)
* commonpath() (於 os.path 模組中):      os path --- Common pathname manipulations.
                                                             (line   73)
* commonprefix() (於 os.path 模組中):    os path --- Common pathname manipulations.
                                                             (line   87)
* common_dirs (filecmp.dircmp 的屬性):   The dircmp class.   (line   71)
* common_files (filecmp.dircmp 的屬性):  The dircmp class.   (line   75)
* common_funny (filecmp.dircmp 的屬性):  The dircmp class.   (line   79)
* common_types (於 mimetypes 模組中):    mimetypes --- Map filenames to MIME types.
                                                             (line  143)
* communicate() (asyncio.asyncio.subprocess.Process 的方法): Interacting with Subprocesses.
                                                             (line   50)
* communicate() (subprocess.Popen 的方法): Popen Objects.    (line   35)
* compare() (decimal.Context 的方法):    Context objects.    (line  242)
* compare() (decimal.Decimal 的方法):    Decimal objects.    (line  146)
* compare() (difflib.Differ 的方法):     Differ Objects.     (line   38)
* compare_digest() (於 hmac 模組中):     hmac --- Keyed-Hashing for Message Authentication.
                                                             (line  108)
* compare_digest() (於 secrets 模組中):  Other functions.    (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  629)
* compare_signal() (decimal.Context 的方法): Context objects.
                                                             (line  246)
* compare_signal() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  157)
* compare_to() (tracemalloc.Snapshot 的方法): Snapshot.      (line   13)
* compare_total() (decimal.Context 的方法): Context objects. (line  250)
* compare_total() (decimal.Decimal 的方法): Decimal objects. (line  164)
* compare_total_mag() (decimal.Context 的方法): Context objects.
                                                             (line  254)
* compare_total_mag() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  189)
* comparison:                            Comparisons.        (line    6)
* comparisons:                           Basic customization.
                                                             (line  180)
* COMPARISON_FLAGS (於 doctest 模組中):  Option Flags.       (line  115)
* Compat32 (email.policy 中的類別):      email policy Policy Objects.
                                                             (line  547)
* compat32 (於 email.policy 模組中):     email policy Policy Objects.
                                                             (line  602)
* Compile (codeop 中的類別):             codeop --- Compile Python code.
                                                             (line   55)
* compile() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  268)
* compile() (parser.ST 的方法):          ST Objects.         (line   17)
* compile() (內建函式):                  內建函式.           (line  243)
* compile() (於 py_compile 模組中):      py_compile --- Compile Python source files.
                                                             (line   24)
* compile() (於 re 模組中):              Module Contents.    (line   14)
* compileall (模組):                     compileall --- Byte-compile Python libraries.
                                                             (line    6)
* compileall command line option; -b:    Command-line use.   (line   52)
* compileall command line option; -d destdir: Command-line use.
                                                             (line   32)
* compileall command line option; -f:    Command-line use.   (line   22)
* compileall command line option; -i list: Command-line use. (line   46)
* compileall command line option; –invalidation-mode [timestamp|checked-hash|unchecked-hash]: Command-line use.
                                                             (line   73)
* compileall command line option; -j N:  Command-line use.   (line   67)
* compileall command line option; -l:    Command-line use.   (line   17)
* compileall command line option; -q:    Command-line use.   (line   26)
* compileall command line option; -r:    Command-line use.   (line   60)
* compileall command line option; -x regex: Command-line use.
                                                             (line   40)
* compileall command line option; directory ...: Command-line use.
                                                             (line    9)
* compileall command line option; file ...: Command-line use.
                                                             (line    9)
* compilest() (於 parser 模組中):        Converting ST Objects.
                                                             (line   43)
* compile_command() (於 code 模組中):    code --- Interpreter base classes.
                                                             (line   47)
* compile_command() (於 codeop 模組中):  codeop --- Compile Python code.
                                                             (line   29)
* compile_dir() (於 compileall 模組中):  Public functions.   (line    6)
* compile_file() (於 compileall 模組中): Public functions.   (line   74)
* compile_path() (於 compileall 模組中): Public functions.   (line  120)
* complete() (rlcompleter.Completer 的方法): Completer Objects.
                                                             (line    8)
* completedefault() (cmd.Cmd 的方法):    Cmd Objects.        (line   80)
* CompletedProcess (subprocess 中的類別): Using the subprocess Module.
                                                             (line   91)
* complete_statement() (於 sqlite3 模組中): Module functions and constants.
                                                             (line  147)
* Complex (numbers 中的類別):            The numeric tower.  (line    6)
* complex (內建類別):                    內建函式.           (line  326)
* complex literal:                       Numeric literals.   (line    6)
* complex number:                        Glossary.           (line  239)
* complex number; literals:              Numeric Types --- int float complex.
                                                             (line   19)
* complex; number:                       The standard type hierarchy.
                                                             (line  119)
* compound; statement:                   Compound statements.
                                                             (line    6)
* comprehensions:                        Displays for lists sets and dictionaries.
                                                             (line    6)
* compress() (bz2.BZ2Compressor 的方法): Incremental de compression.
                                                             (line   15)
* compress() (lzma.LZMACompressor 的方法): Compressing and decompressing data in memory.
                                                             (line   81)
* compress() (zlib.Compress 的方法):     zlib --- Compression compatible with gzip.
                                                             (line  195)
* compress() (於 bz2 模組中):            One-shot de compression.
                                                             (line    6)
* compress() (於 gzip 模組中):           gzip --- Support for gzip files.
                                                             (line  169)
* compress() (於 itertools 模組中):      Itertool functions. (line  212)
* compress() (於 lzma 模組中):           Compressing and decompressing data in memory.
                                                             (line  183)
* compress() (於 zlib 模組中):           zlib --- Compression compatible with gzip.
                                                             (line   45)
* compressed (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line   52)
* compressed (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line  107)
* compressed (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  147)
* compressed (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  319)
* compression() (ssl.SSLSocket 的方法):  SSL Sockets.        (line  225)
* CompressionError:                      tarfile --- Read and write tar archive files.
                                                             (line  190)
* compressobj() (於 zlib 模組中):        zlib --- Compression compatible with gzip.
                                                             (line   59)
* compress_size (zipfile.ZipInfo 的屬性): ZipInfo Objects.   (line  139)
* compress_type (zipfile.ZipInfo 的屬性): ZipInfo Objects.   (line   84)
* COMSPEC:                               Process Management. (line  664)
* COMSPEC <1>:                           Popen Constructor.  (line   90)
* concat() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line  172)
* concatenation; operation:              Common Sequence Operations.
                                                             (line   21)
* concurrent.futures (模組):             concurrent futures --- Launching parallel tasks.
                                                             (line    6)
* Condition (asyncio 中的類別):          Condition.          (line    6)
* Condition (multiprocessing 中的類別):  Synchronization primitives.
                                                             (line   32)
* condition (pdb command):               Debugger Commands.  (line  119)
* Condition (threading 中的類別):        Condition Objects.  (line   72)
* condition() (msilib.Control 的方法):   GUI classes.        (line   24)
* Condition() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  155)
* Conditional; expression:               Boolean operations. (line    6)
* conditional; expression:               Conditional expressions.
                                                             (line    6)
* ConfigParser (configparser 中的類別):  ConfigParser Objects.
                                                             (line    6)
* configparser (模組):                   configparser --- Configuration file parser.
                                                             (line    6)
* configuration information:             sysconfig --- Provide access to Python's configuration information.
                                                             (line   10)
* configuration; file:                   configparser --- Configuration file parser.
                                                             (line    8)
* configure() (tkinter.ttk.Style 的方法): Ttk Styling.       (line   24)
* configure_mock() (unittest.mock.Mock 的方法): The Mock Class.
                                                             (line  242)
* confstr() (於 os 模組中):              Miscellaneous System Information.
                                                             (line    6)
* confstr_names (於 os 模組中):          Miscellaneous System Information.
                                                             (line   28)
* conjugate() (complex number method):   Numeric Types --- int float complex.
                                                             (line   94)
* conjugate() (decimal.Decimal 的方法):  Decimal objects.    (line  201)
* conjugate() (numbers.Complex 的方法):  The numeric tower.  (line   23)
* conn (smtpd.SMTPChannel 的屬性):       SMTPChannel Objects.
                                                             (line   48)
* connect() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  193)
* connect() (ftplib.FTP 的方法):         FTP Objects.        (line   22)
* connect() (http.client.HTTPConnection 的方法): HTTPConnection Objects.
                                                             (line  104)
* connect() (multiprocessing.managers.BaseManager 的方法): Managers.
                                                             (line   59)
* connect() (smtplib.SMTP 的方法):       SMTP Objects.       (line   33)
* connect() (socket.socket 的方法):      Socket Objects.     (line   60)
* connect() (於 sqlite3 模組中):         Module functions and constants.
                                                             (line   55)
* Connection (multiprocessing.connection 中的類別): Connection Objects<2>.
                                                             (line   13)
* Connection (sqlite3 中的類別):         Connection Objects. (line    6)
* connection (sqlite3.Cursor 的屬性):    Cursor Objects.     (line  229)
* ConnectionAbortedError:                OS exceptions.      (line   44)
* ConnectionError:                       OS exceptions.      (line   29)
* ConnectionRefusedError:                OS exceptions.      (line   50)
* ConnectionResetError:                  OS exceptions.      (line   56)
* connection_lost() (asyncio.BaseProtocol 的方法): Base Protocol.
                                                             (line   23)
* connection_made() (asyncio.BaseProtocol 的方法): Base Protocol.
                                                             (line   15)
* ConnectRegistry() (於 winreg 模組中):  Functions<11>.      (line   17)
* connect_accepted_socket() (asyncio.loop 的方法): Creating network servers.
                                                             (line  114)
* connect_ex() (socket.socket 的方法):   Socket Objects.     (line   82)
* connect_read_pipe() (asyncio.loop 的方法): Working with pipes.
                                                             (line    6)
* connect_write_pipe() (asyncio.loop 的方法): Working with pipes.
                                                             (line   22)
* const (optparse.Option 的屬性):        Option attributes.  (line   50)
* constant:                              Literals.           (line    6)
* constructor() (於 copyreg 模組中):     copyreg --- Register pickle support functions.
                                                             (line   17)
* consumed (asyncio.LimitOverrunError 的屬性): Exceptions<8>.
                                                             (line   65)
* container:                             Objects values and types.
                                                             (line   67)
* container <1>:                         The standard type hierarchy.
                                                             (line  572)
* Container (collections.abc 中的類別):  Collections Abstract Base Classes.
                                                             (line  104)
* Container (typing 中的類別):           Classes functions and decorators.
                                                             (line  191)
* container; iteration over:             Iterator Types.     (line    6)
* contains() (於 operator 模組中):       operator --- Standard operators as functions.
                                                             (line  177)
* ContentDispositionHeader (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  280)
* ContentHandler (xml.sax.handler 中的類別): xml sax handler --- Base classes for SAX handlers.
                                                             (line   18)
* ContentManager (email.contentmanager 中的類別): email contentmanager Managing MIME Content.
                                                             (line   12)
* contents (ctypes._Pointer 的屬性):     Arrays and pointers.
                                                             (line   50)
* contents() (importlib.abc.ResourceReader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  330)
* contents() (於 importlib.resources 模組中): importlib resources -- Resources.
                                                             (line  127)
* ContentTooShortError:                  urllib error --- Exception classes raised by urllib request.
                                                             (line   56)
* ContentTransferEncoding (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  290)
* ContentTypeHeader (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  267)
* content_disposition (email.headerregistry.ContentDispositionHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  285)
* content_manager (email.policy.EmailPolicy 的屬性): email policy Policy Objects.
                                                             (line  402)
* content_type (email.headerregistry.ContentTypeHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  272)
* Context (contextvars 中的類別):        Manual Context Management.
                                                             (line   20)
* Context (decimal 中的類別):            Context objects.    (line   96)
* context (ssl.SSLSocket 的屬性):        SSL Sockets.        (line  316)
* context management protocol:           Context Manager Types.
                                                             (line    6)
* context manager:                       With Statement Context Managers.
                                                             (line   14)
* context manager <1>:                   Context Manager Types.
                                                             (line    6)
* context manager <2>:                   Glossary.           (line  253)
* context variable:                      Glossary.           (line  259)
* ContextDecorator (contextlib 中的類別): Utilities.         (line  264)
* contextlib (模組):                     contextlib --- Utilities for with-statement contexts.
                                                             (line    6)
* ContextManager (typing 中的類別):      Classes functions and decorators.
                                                             (line  332)
* contextmanager() (於 contextlib 模組中): Utilities.        (line   30)
* ContextVar (contextvars 中的類別):     Context Variables.  (line    6)
* contextvars (模組):                    contextvars --- Context Variables.
                                                             (line    6)
* contextvars.Token (contextvars 中的類別): Context Variables.
                                                             (line   75)
* context_diff() (於 difflib 模組中):    difflib --- Helpers for computing deltas.
                                                             (line  158)
* contiguous:                            shape strides suboffsets.
                                                             (line   26)
* contiguous <1>:                        Glossary.           (line  269)
* contiguous (memoryview 的屬性):        Memory Views.       (line  478)
* continue (pdb command):                Debugger Commands.  (line  192)
* Control (msilib 中的類別):             GUI classes.        (line   11)
* Control (tkinter.tix 中的類別):        Basic Widgets.      (line   24)
* control() (msilib.Dialog 的方法):      GUI classes.        (line   47)
* control() (select.kqueue 的方法):      Kqueue Objects.     (line   22)
* controlnames (於 curses.ascii 模組中): curses ascii --- Utilities for ASCII characters.
                                                             (line  237)
* controls() (ossaudiodev.oss_mixer_device 的方法): Mixer Device Objects.
                                                             (line   22)
* ConversionError:                       Exceptions<5>.      (line   13)
* convert_arg_line_to_args() (argparse.ArgumentParser 的方法): Customizing file parsing.
                                                             (line    6)
* convert_field() (string.Formatter 的方法): Custom String Formatting.
                                                             (line  108)
* convert_path() (於 distutils.util 模組中): distutils util --- Miscellaneous other utility functions.
                                                             (line   54)
* Cookie (http.cookiejar 中的類別):      http cookiejar --- Cookie handling for HTTP clients.
                                                             (line  109)
* CookieError:                           http cookies --- HTTP state management.
                                                             (line   33)
* CookieJar (http.cookiejar 中的類別):   http cookiejar --- Cookie handling for HTTP clients.
                                                             (line   45)
* cookiejar (urllib.request.HTTPCookieProcessor 的屬性): HTTPCookieProcessor Objects.
                                                             (line    8)
* CookiePolicy (http.cookiejar 中的類別): http cookiejar --- Cookie handling for HTTP clients.
                                                             (line   73)
* Coordinated Universal Time:            time --- Time access and conversions.
                                                             (line   40)
* Copy:                                  Help menu Shell and Editor.
                                                             (line   30)
* copy (模組):                           copy --- Shallow and deep copy operations.
                                                             (line    6)
* copy() (collections.deque 的方法):     deque objects.      (line   47)
* copy() (contextvars.Context 的方法):   Manual Context Management.
                                                             (line   70)
* copy() (decimal.Context 的方法):       Context objects.    (line  162)
* copy() (dict 的方法):                  Mapping Types --- dict.
                                                             (line  146)
* copy() (frozenset 的方法):             Set Types --- set frozenset.
                                                             (line  123)
* copy() (hashlib.hash 的方法):          Hash algorithms.    (line  141)
* copy() (hmac.HMAC 的方法):             hmac --- Keyed-Hashing for Message Authentication.
                                                             (line   81)
* copy() (http.cookies.Morsel 的方法):   Morsel Objects.     (line  102)
* copy() (imaplib.IMAP4 的方法):         IMAP4 Objects.      (line   68)
* copy() (pipes.Template 的方法):        Template Objects.   (line   48)
* copy() (sequence method):              Mutable Sequence Types.
                                                             (line   16)
* copy() (types.MappingProxyType 的方法): Standard Interpreter Types.
                                                             (line  245)
* copy() (zlib.Compress 的方法):         zlib --- Compression compatible with gzip.
                                                             (line  216)
* copy() (zlib.Decompress 的方法):       zlib --- Compression compatible with gzip.
                                                             (line  284)
* copy() (於 copy 模組中):               copy --- Shallow and deep copy operations.
                                                             (line   18)
* copy() (於 multiprocessing.sharedctypes 模組中): The multiprocessing sharedctypes module.
                                                             (line   83)
* copy() (於 shutil 模組中):             Directory and files operations.
                                                             (line  121)
* copy2() (於 shutil 模組中):            Directory and files operations.
                                                             (line  152)
* copy; protocol:                        Pickling Class Instances.
                                                             (line   93)
* copyfile() (於 shutil 模組中):         Directory and files operations.
                                                             (line   17)
* copyfileobj() (於 shutil 模組中):      Directory and files operations.
                                                             (line    6)
* copying files:                         shutil --- High-level file operations.
                                                             (line    8)
* copymode() (於 shutil 模組中):         Directory and files operations.
                                                             (line   59)
* copyreg (模組):                        copyreg --- Register pickle support functions.
                                                             (line    6)
* copyright (in module sys):             Process-wide parameters.
                                                             (line  188)
* copyright (內建變數):                  Constants added by the site module.
                                                             (line   18)
* copyright (於 sys 模組中):             sys --- System-specific parameters and functions.
                                                             (line  153)
* copysign() (於 math 模組中):           Number-theoretic and representation functions.
                                                             (line   30)
* copystat() (於 shutil 模組中):         Directory and files operations.
                                                             (line   77)
* copytree() (於 shutil 模組中):         Directory and files operations.
                                                             (line  191)
* copy_abs() (decimal.Context 的方法):   Context objects.    (line  259)
* copy_abs() (decimal.Decimal 的方法):   Decimal objects.    (line  206)
* copy_context() (於 contextvars 模組中): Manual Context Management.
                                                             (line    6)
* copy_decimal() (decimal.Context 的方法): Context objects.  (line  166)
* copy_file() (於 distutils.file_util 模組中): distutils file_util --- Single file operations.
                                                             (line    9)
* copy_file_range() (於 os 模組中):      File Descriptor Operations.
                                                             (line   44)
* copy_location() (於 ast 模組中):       ast Helpers.        (line   96)
* copy_negate() (decimal.Context 的方法): Context objects.   (line  263)
* copy_negate() (decimal.Decimal 的方法): Decimal objects.   (line  212)
* copy_sign() (decimal.Context 的方法):  Context objects.    (line  267)
* copy_sign() (decimal.Decimal 的方法):  Decimal objects.    (line  218)
* copy_tree() (於 distutils.dir_util 模組中): distutils dir_util --- Directory tree operations.
                                                             (line   32)
* coroutine:                             Special method lookup.
                                                             (line   74)
* coroutine <1>:                         Yield expressions.  (line   50)
* coroutine <2>:                         Glossary.           (line  280)
* Coroutine (collections.abc 中的類別):  Collections Abstract Base Classes.
                                                             (line  212)
* Coroutine (typing 中的類別):           Classes functions and decorators.
                                                             (line  304)
* coroutine function:                    Glossary.           (line  288)
* coroutine() (於 asyncio 模組中):       Generator-based Coroutines.
                                                             (line   16)
* coroutine() (於 types 模組中):         Coroutine Utility Functions.
                                                             (line    6)
* coroutine; function:                   The standard type hierarchy.
                                                             (line  457)
* CoroutineType (於 types 模組中):       Standard Interpreter Types.
                                                             (line   36)
* cos() (於 cmath 模組中):               Trigonometric functions<2>.
                                                             (line   25)
* cos() (於 math 模組中):                Trigonometric functions.
                                                             (line   28)
* cosh() (於 cmath 模組中):              Hyperbolic functions<2>.
                                                             (line   26)
* cosh() (於 math 模組中):               Hyperbolic functions.
                                                             (line   21)
* count (tracemalloc.Statistic 的屬性):  Statistic.          (line   15)
* count (tracemalloc.StatisticDiff 的屬性): StatisticDiff.   (line   15)
* count() (array.array 的方法):          array --- 高效率的數值型態陣列.
                                                             (line  129)
* count() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line   36)
* count() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line   36)
* count() (collections.deque 的方法):    deque objects.      (line   53)
* count() (multiprocessing.shared_memory.ShareableList 的方法): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line  264)
* count() (sequence method):             Common Sequence Operations.
                                                             (line   21)
* count() (str 的方法):                  String Methods<2>.  (line   54)
* count() (於 itertools 模組中):         Itertool functions. (line  225)
* Counter (collections 中的類別):        Counter 物件.       (line   22)
* Counter (typing 中的類別):             Classes functions and decorators.
                                                             (line  374)
* countOf() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  183)
* countTestCases() (unittest.TestCase 的方法): Test cases.   (line  708)
* countTestCases() (unittest.TestSuite 的方法): Grouping tests.
                                                             (line   55)
* count_diff (tracemalloc.StatisticDiff 的屬性): StatisticDiff.
                                                             (line   20)
* CoverageResults (trace 中的類別):      Programmatic Interface.
                                                             (line   47)
* co_argcount (code object attribute):   The standard type hierarchy.
                                                             (line  661)
* CO_ASYNC_GENERATOR (於 inspect 模組中): Code Objects Bit Flags.
                                                             (line   56)
* co_cellvars (code object attribute):   The standard type hierarchy.
                                                             (line  661)
* co_code (code object attribute):       The standard type hierarchy.
                                                             (line  661)
* co_consts (code object attribute):     The standard type hierarchy.
                                                             (line  661)
* CO_COROUTINE (於 inspect 模組中):      Code Objects Bit Flags.
                                                             (line   39)
* co_filename (code object attribute):   The standard type hierarchy.
                                                             (line  661)
* co_firstlineno (code object attribute): The standard type hierarchy.
                                                             (line  661)
* co_flags (code object attribute):      The standard type hierarchy.
                                                             (line  661)
* co_freevars (code object attribute):   The standard type hierarchy.
                                                             (line  661)
* CO_FUTURE_DIVISION (C 變數):           The Very High Level Layer.
                                                             (line  420)
* CO_GENERATOR (於 inspect 模組中):      Code Objects Bit Flags.
                                                             (line   30)
* CO_ITERABLE_COROUTINE (於 inspect 模組中): Code Objects Bit Flags.
                                                             (line   47)
* co_kwonlyargcount (code object attribute): The standard type hierarchy.
                                                             (line  661)
* co_lnotab (code object attribute):     The standard type hierarchy.
                                                             (line  661)
* co_name (code object attribute):       The standard type hierarchy.
                                                             (line  661)
* co_names (code object attribute):      The standard type hierarchy.
                                                             (line  661)
* CO_NESTED (於 inspect 模組中):         Code Objects Bit Flags.
                                                             (line   26)
* CO_NEWLOCALS (於 inspect 模組中):      Code Objects Bit Flags.
                                                             (line   13)
* co_nlocals (code object attribute):    The standard type hierarchy.
                                                             (line  661)
* CO_NOFREE (於 inspect 模組中):         Code Objects Bit Flags.
                                                             (line   35)
* CO_OPTIMIZED (於 inspect 模組中):      Code Objects Bit Flags.
                                                             (line    9)
* co_posonlyargcount (code object attribute): The standard type hierarchy.
                                                             (line  661)
* co_stacksize (code object attribute):  The standard type hierarchy.
                                                             (line  661)
* CO_VARARGS (於 inspect 模組中):        Code Objects Bit Flags.
                                                             (line   18)
* CO_VARKEYWORDS (於 inspect 模組中):    Code Objects Bit Flags.
                                                             (line   22)
* co_varnames (code object attribute):   The standard type hierarchy.
                                                             (line  661)
* CPP:                                   New Improved and Deprecated Modules<4>.
                                                             (line   59)
* CPPFLAGS:                              New Improved and Deprecated Modules<4>.
                                                             (line   59)
* cProfile (模組):                       profile and cProfile Module Reference.
                                                             (line    6)
* CPU time:                              Functions<2>.       (line  200)
* CPU time <1>:                          Functions<2>.       (line  479)
* cpu_count() (於 multiprocessing 模組中): Miscellaneous<3>. (line   13)
* cpu_count() (於 os 模組中):            Miscellaneous System Information.
                                                             (line   37)
* CPython:                               Glossary.           (line  296)
* cpython_only() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  632)
* crawl_delay() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- Parser for robots txt.
                                                             (line   50)
* CRC (zipfile.ZipInfo 的屬性):          ZipInfo Objects.    (line  135)
* crc32() (於 binascii 模組中):          binascii --- Convert between binary and ASCII.
                                                             (line  112)
* crc32() (於 zlib 模組中):              zlib --- Compression compatible with gzip.
                                                             (line  113)
* crc_hqx() (於 binascii 模組中):        binascii --- Convert between binary and ASCII.
                                                             (line  105)
* create() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line   72)
* create() (venv.EnvBuilder 的方法):     API<2>.             (line   49)
* create() (於 venv 模組中):             API<2>.             (line  155)
* 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 Objects.
                                                             (line   16)
* createDocumentType() (xml.dom.DOMImplementation 的方法): DOMImplementation Objects.
                                                             (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 模組中):        Functions<11>.      (line   35)
* CreateKeyEx() (於 winreg 模組中):      Functions<11>.      (line   63)
* createLock() (logging.Handler 的方法): Handler Objects.    (line   20)
* createLock() (logging.NullHandler 的方法): NullHandler.    (line   24)
* createProcessingInstruction() (xml.dom.Document 的方法): Document Objects.
                                                             (line   40)
* CreateRecord() (於 msilib 模組中):     msilib --- Read and write Microsoft Installer files.
                                                             (line   55)
* createSocket() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   72)
* createTextNode() (xml.dom.Document 的方法): Document Objects.
                                                             (line   28)
* create_aggregate() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line  108)
* create_archive() (於 zipapp 模組中):   Python API.         (line    8)
* create_autospec() (於 unittest.mock 模組中): create_autospec.
                                                             (line    6)
* CREATE_BREAKAWAY_FROM_JOB (於 subprocess 模組中): Windows Constants.
                                                             (line  124)
* create_collation() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line  146)
* create_configuration() (venv.EnvBuilder 的方法): API<2>.   (line   86)
* create_connection() (asyncio.loop 的方法): Opening network connections.
                                                             (line    6)
* create_connection() (於 socket 模組中): Creating sockets.  (line   77)
* create_datagram_endpoint() (asyncio.loop 的方法): Opening network connections.
                                                             (line  134)
* create_decimal() (decimal.Context 的方法): Context objects.
                                                             (line  170)
* create_decimal_from_float() (decimal.Context 的方法): Context objects.
                                                             (line  194)
* create_default_context() (於 ssl 模組中): Context creation.
                                                             (line    9)
* CREATE_DEFAULT_ERROR_MODE (於 subprocess 模組中): Windows Constants.
                                                             (line  114)
* create_empty_file() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  237)
* create_function() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line   73)
* create_future() (asyncio.loop 的方法): Creating Futures and Tasks.
                                                             (line    6)
* create_module (C 函式):                Multi-phase initialization.
                                                             (line   67)
* create_module() (importlib.abc.Loader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  166)
* create_module() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  311)
* CREATE_NEW_CONSOLE (於 subprocess 模組中): Windows Constants.
                                                             (line   38)
* CREATE_NEW_PROCESS_GROUP (於 subprocess 模組中): Windows Constants.
                                                             (line   43)
* CREATE_NO_WINDOW (於 subprocess 模組中): Windows Constants.
                                                             (line   99)
* create_server() (asyncio.loop 的方法): Creating network servers.
                                                             (line    6)
* create_server() (於 socket 模組中):    Creating sockets.   (line  101)
* create_shortcut() (內建函式):          The Postinstallation script.
                                                             (line   62)
* create_socket() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  184)
* create_static_lib() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  322)
* create_stats() (profile.Profile 的方法): profile and cProfile Module Reference.
                                                             (line   86)
* create_string_buffer() (於 ctypes 模組中): Utility functions.
                                                             (line   40)
* create_subprocess_exec() (於 asyncio 模組中): Creating Subprocesses.
                                                             (line    6)
* create_subprocess_shell() (於 asyncio 模組中): Creating Subprocesses.
                                                             (line   25)
* create_system (zipfile.ZipInfo 的屬性): ZipInfo Objects.   (line   99)
* create_task() (asyncio.loop 的方法):   Creating Futures and Tasks.
                                                             (line   17)
* create_task() (於 asyncio 模組中):     Creating Tasks.     (line    6)
* create_tree() (於 distutils.dir_util 模組中): distutils dir_util --- Directory tree operations.
                                                             (line   21)
* create_unicode_buffer() (於 ctypes 模組中): Utility functions.
                                                             (line   58)
* create_unix_connection() (asyncio.loop 的方法): Opening network connections.
                                                             (line  211)
* create_unix_server() (asyncio.loop 的方法): Creating network servers.
                                                             (line   92)
* create_version (zipfile.ZipInfo 的屬性): ZipInfo Objects.  (line  103)
* credits (內建變數):                    Constants added by the site module.
                                                             (line   18)
* critical() (logging.Logger 的方法):    Logger Objects.     (line  234)
* critical() (於 logging 模組中):        Module-Level Functions.
                                                             (line  138)
* CRNCYSTR (於 locale 模組中):           locale --- Internationalization services.
                                                             (line  257)
* cross() (於 audioop 模組中):           audioop --- Manipulate raw audio data.
                                                             (line   74)
* crypt (模組):                          crypt --- Function to check Unix passwords.
                                                             (line    6)
* crypt() (於 crypt 模組中):             Module Functions<2>.
                                                             (line    8)
* crypt(3):                              crypt --- Function to check Unix passwords.
                                                             (line    8)
* crypt(3) <1>:                          crypt --- Function to check Unix passwords.
                                                             (line   16)
* crypt(3) <2>:                          Module Functions<2>.
                                                             (line   32)
* cryptography:                          Cryptographic Services.
                                                             (line    6)
* cssclasses (calendar.HTMLCalendar 的屬性): calendar --- General calendar-related functions.
                                                             (line  193)
* cssclasses_weekday_head (calendar.HTMLCalendar 的屬性): calendar --- General calendar-related functions.
                                                             (line  213)
* cssclass_month (calendar.HTMLCalendar 的屬性): calendar --- General calendar-related functions.
                                                             (line  227)
* cssclass_month_head (calendar.HTMLCalendar 的屬性): calendar --- General calendar-related functions.
                                                             (line  220)
* cssclass_noday (calendar.HTMLCalendar 的屬性): calendar --- General calendar-related functions.
                                                             (line  206)
* cssclass_year (calendar.HTMLCalendar 的屬性): calendar --- General calendar-related functions.
                                                             (line  234)
* cssclass_year_head (calendar.HTMLCalendar 的屬性): calendar --- General calendar-related functions.
                                                             (line  241)
* csv:                                   csv --- CSV File Reading and Writing.
                                                             (line    8)
* csv (模組):                            csv --- CSV File Reading and Writing.
                                                             (line    6)
* cte (email.headerregistry.ContentTransferEncoding 的屬性): email headerregistry Custom Header Objects.
                                                             (line  294)
* ctermid() (於 os 模組中):              Process Parameters. (line    9)
* cte_type (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  159)
* ctime() (datetime.date 的方法):        date Objects.       (line  251)
* ctime() (datetime.datetime 的方法):    datetime Objects.   (line  680)
* ctime() (於 time 模組中):              Functions<2>.       (line   85)
* ctrl() (於 curses.ascii 模組中):       curses ascii --- Utilities for ASCII characters.
                                                             (line  213)
* CTRL_BREAK_EVENT (於 signal 模組中):   Module contents<2>. (line  155)
* CTRL_C_EVENT (於 signal 模組中):       Module contents<2>. (line  146)
* ctypes (模組):                         ctypes --- A foreign function library for Python.
                                                             (line    6)
* curdir (於 os 模組中):                 Miscellaneous System Information.
                                                             (line   81)
* currency() (於 locale 模組中):         locale --- Internationalization services.
                                                             (line  418)
* current() (tkinter.ttk.Combobox 的方法): ttk Combobox.     (line    8)
* CurrentByteIndex (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line  157)
* CurrentColumnNumber (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line  161)
* currentframe() (於 inspect 模組中):    The interpreter stack.
                                                             (line   72)
* CurrentLineNumber (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line  165)
* current_process() (於 multiprocessing 模組中): Miscellaneous<3>.
                                                             (line   28)
* current_task() (asyncio.Task 的類別成員): Task Object.     (line  243)
* current_task() (於 asyncio 模組中):    Introspection.      (line    6)
* current_thread() (於 threading 模組中): threading --- Thread-based parallelism.
                                                             (line   38)
* curses (模組):                         curses --- Terminal handling for character-cell displays.
                                                             (line    6)
* curses.ascii (模組):                   curses ascii --- Utilities for ASCII characters.
                                                             (line    6)
* curses.panel (模組):                   curses panel --- A panel stack extension for curses.
                                                             (line    6)
* curses.textpad (模組):                 curses textpad --- Text input widget for curses programs.
                                                             (line    6)
* Cursor (sqlite3 中的類別):             Cursor Objects.     (line    6)
* cursor() (sqlite3.Connection 的方法):  Connection Objects. (line   26)
* cursyncup() (curses.window 的方法):    Window Objects.     (line  172)
* curs_set() (於 curses 模組中):         Functions<3>.       (line   61)
* customize_compiler() (於 distutils.sysconfig 模組中): distutils sysconfig --- System configuration information.
                                                             (line   83)
* Cut:                                   Help menu Shell and Editor.
                                                             (line   30)
* cwd() (ftplib.FTP 的方法):             FTP Objects.        (line  213)
* cwd() (pathlib.Path 的類別成員):       Methods<2>.         (line   17)
* cycle() (於 itertools 模組中):         Itertool functions. (line  247)
* Cyclic Redundancy Check:               zlib --- Compression compatible with gzip.
                                                             (line  115)
* c_bool (ctypes 中的類別):              Fundamental data types<2>.
                                                             (line  202)
* C_BUILTIN (於 imp 模組中):             imp --- Access the import internals.
                                                             (line  331)
* 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 (memoryview 的屬性):      Memory Views.       (line  464)
* c_double (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line   65)
* C_EXTENSION (於 imp 模組中):           imp --- Access the import internals.
                                                             (line  319)
* 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_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_ubyte (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  134)
* c_uint (ctypes 中的類別):              Fundamental data types<2>.
                                                             (line  140)
* c_uint16 (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  152)
* c_uint32 (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  157)
* c_uint64 (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  162)
* c_uint8 (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  147)
* c_ulong (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  167)
* c_ulonglong (ctypes 中的類別):         Fundamental data types<2>.
                                                             (line  172)
* c_ushort (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  178)
* c_void_p (ctypes 中的類別):            Fundamental data types<2>.
                                                             (line  184)
* c_wchar (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  189)
* c_wchar_p (ctypes 中的類別):           Fundamental data types<2>.
                                                             (line  196)
* daemon (multiprocessing.Process 的屬性): Process and exceptions.
                                                             (line   87)
* daemon (threading.Thread 的屬性):      Thread Objects.     (line  184)
* dangling; else:                        Compound statements.
                                                             (line   54)
* data:                                  Objects values and types.
                                                             (line    6)
* data (collections.UserDict 的屬性):    UserDict objects.   (line   24)
* data (collections.UserList 的屬性):    UserList objects.   (line   29)
* data (collections.UserString 的屬性):  UserString objects. (line   24)
* Data (plistlib 中的類別):              plistlib --- Generate and parse Mac OS X plist files.
                                                             (line  168)
* 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 Objects.
                                                             (line   14)
* data (xml.dom.Text 的屬性):            Text and CDATASection Objects.
                                                             (line   15)
* data (xmlrpc.client.Binary 的屬性):    Binary Objects.     (line   12)
* data() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder Objects.
                                                             (line   33)
* data; tabular:                         csv --- CSV File Reading and Writing.
                                                             (line    8)
* data; type:                            The standard type hierarchy.
                                                             (line    6)
* DatabaseError:                         Exceptions<3>.      (line   15)
* databases:                             dbm dumb --- Portable DBM implementation.
                                                             (line    8)
* dataclass() (於 dataclasses 模組中):   Module-level decorators classes and functions.
                                                             (line    6)
* dataclasses (模組):                    dataclasses --- Data Classes.
                                                             (line    6)
* DatagramHandler (logging.handlers 中的類別): DatagramHandler.
                                                             (line   10)
* DatagramProtocol (asyncio 中的類別):   Base Protocols.     (line   20)
* DatagramRequestHandler (socketserver 中的類別): Request Handler Objects.
                                                             (line   42)
* DatagramTransport (asyncio 中的類別):  Transports Hierarchy.
                                                             (line   43)
* datagram_received() (asyncio.DatagramProtocol 的方法): Datagram Protocols.
                                                             (line    9)
* DataHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  419)
* data_open() (urllib.request.DataHandler 的方法): DataHandler Objects.
                                                             (line    6)
* data_received() (asyncio.Protocol 的方法): Streaming Protocols.
                                                             (line   13)
* date (datetime 中的類別):              date Objects.       (line   13)
* date() (datetime.datetime 的方法):     datetime Objects.   (line  390)
* date() (nntplib.NNTP 的方法):          Methods<3>.         (line  298)
* DateHeader (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  136)
* datetime (datetime 中的類別):          datetime Objects.   (line   17)
* datetime (email.headerregistry.DateHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  145)
* DateTime (xmlrpc.client 中的類別):     日期時間物件.       (line    6)
* datetime (模組):                       datetime --- Basic date and time types.
                                                             (line    6)
* date_time (zipfile.ZipInfo 的屬性):    ZipInfo Objects.    (line   54)
* date_time_string() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  310)
* datum:                                 Dictionary displays.
                                                             (line    6)
* day (datetime.date 的屬性):            date Objects.       (line  110)
* day (datetime.datetime 的屬性):        datetime Objects.   (line  272)
* daylight (於 time 模組中):             Timezone Constants. (line   13)
* Daylight Saving Time:                  time --- Time access and conversions.
                                                             (line   44)
* day_abbr (於 calendar 模組中):         calendar --- General calendar-related functions.
                                                             (line  371)
* day_name (於 calendar 模組中):         calendar --- General calendar-related functions.
                                                             (line  366)
* DbfilenameShelf (shelve 中的類別):     Restrictions.       (line   64)
* dbm (模組):                            dbm --- Interfaces to Unix "databases".
                                                             (line    6)
* dbm.dumb (模組):                       dbm dumb --- Portable DBM implementation.
                                                             (line    6)
* dbm.gnu (模組):                        dbm gnu --- GNU's reinterpretation of dbm.
                                                             (line    6)
* dbm.ndbm (模組):                       dbm ndbm --- Interface based on ndbm.
                                                             (line    6)
* dcgettext() (於 locale 模組中):        Access to message catalogs.
                                                             (line   10)
* deallocation, object:                  Finalization and De-allocation.
                                                             (line    6)
* debug (imaplib.IMAP4 的屬性):          IMAP4 Objects.      (line  382)
* debug (pdb command):                   Debugger Commands.  (line  335)
* debug (shlex.shlex 的屬性):            shlex Objects.      (line  161)
* debug (zipfile.ZipFile 的屬性):        ZipFile Objects.    (line  300)
* DEBUG (於 re 模組中):                  Module Contents.    (line   58)
* debug() (logging.Logger 的方法):       Logger Objects.     (line  118)
* debug() (pipes.Template 的方法):       Template Objects.   (line   16)
* 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   44)
* debugger:                              Debug menu Shell window only.
                                                             (line   15)
* debugger <1>:                          sys --- System-specific parameters and functions.
                                                             (line  743)
* debugger <2>:                          sys --- System-specific parameters and functions.
                                                             (line 1309)
* debugger; configuration; file:         Debugger Commands.  (line   37)
* debugging:                             pdb --- The Python Debugger.
                                                             (line    8)
* debugging; assertions:                 The assert statement.
                                                             (line    6)
* DebuggingServer (smtpd 中的類別):      DebuggingServer Objects.
                                                             (line    6)
* debuglevel (http.client.HTTPResponse 的屬性): HTTPResponse Objects.
                                                             (line   59)
* DebugRunner (doctest 中的類別):        Debugging.          (line  168)
* DEBUG_BYTECODE_SUFFIXES (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   20)
* DEBUG_COLLECTABLE (於 gc 模組中):      gc --- Garbage Collector interface.
                                                             (line  272)
* DEBUG_LEAK (於 gc 模組中):             gc --- Garbage Collector interface.
                                                             (line  291)
* debug_print() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  510)
* DEBUG_SAVEALL (於 gc 模組中):          gc --- Garbage Collector interface.
                                                             (line  285)
* debug_src() (於 doctest 模組中):       Debugging.          (line  147)
* DEBUG_STATS (於 gc 模組中):            gc --- Garbage Collector interface.
                                                             (line  267)
* DEBUG_UNCOLLECTABLE (於 gc 模組中):    gc --- Garbage Collector interface.
                                                             (line  276)
* Decimal (decimal 中的類別):            Decimal objects.    (line    6)
* decimal (模組):                        decimal --- Decimal fixed point and floating point arithmetic.
                                                             (line    6)
* decimal literal:                       Numeric literals.   (line    6)
* decimal() (於 unicodedata 模組中):     unicodedata --- Unicode Database.
                                                             (line   31)
* DecimalException (decimal 中的類別):   Signals.            (line   28)
* decode (codecs.CodecInfo 的屬性):      codecs --- Codec registry and base classes.
                                                             (line   69)
* decode() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line   49)
* decode() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line   49)
* decode() (codecs.Codec 的方法):        Stateless Encoding and Decoding.
                                                             (line   26)
* decode() (codecs.IncrementalDecoder 的方法): IncrementalDecoder Objects.
                                                             (line   28)
* decode() (json.JSONDecoder 的方法):    Encoders and Decoders.
                                                             (line   84)
* decode() (xmlrpc.client.Binary 的方法): Binary Objects.    (line   20)
* decode() (xmlrpc.client.DateTime 的方法): 日期時間物件.    (line   13)
* decode() (於 base64 模組中):           base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  201)
* decode() (於 codecs 模組中):           codecs --- Codec registry and base classes.
                                                             (line   34)
* decode() (於 quopri 模組中):           quopri --- Encode and decode MIME quoted-printable data.
                                                             (line   19)
* decode() (於 uu 模組中):               uu --- Encode and decode uuencode files.
                                                             (line   37)
* decodebytes() (於 base64 模組中):      base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  208)
* DecodedGenerator (email.generator 中的類別): email generator Generating MIME documents.
                                                             (line  232)
* decodestring() (於 base64 模組中):     base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  216)
* decodestring() (於 quopri 模組中):     quopri --- Encode and decode MIME quoted-printable data.
                                                             (line   41)
* decode_header() (於 email.header 模組中): email header Internationalized headers.
                                                             (line  182)
* decode_header() (於 nntplib 模組中):   Utility functions<2>.
                                                             (line    8)
* decode_params() (於 email.utils 模組中): email utils Miscellaneous utilities.
                                                             (line  203)
* decode_rfc2231() (於 email.utils 模組中): email utils Miscellaneous utilities.
                                                             (line  174)
* decode_source() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   72)
* decomposition() (於 unicodedata 模組中): unicodedata --- Unicode Database.
                                                             (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 --- Compression compatible with gzip.
                                                             (line  254)
* decompress() (於 bz2 模組中):          One-shot de compression.
                                                             (line   16)
* decompress() (於 gzip 模組中):         gzip --- Support for gzip files.
                                                             (line  179)
* decompress() (於 lzma 模組中):         Compressing and decompressing data in memory.
                                                             (line  192)
* decompress() (於 zlib 模組中):         zlib --- Compression compatible with gzip.
                                                             (line  129)
* decompressobj() (於 zlib 模組中):      zlib --- Compression compatible with gzip.
                                                             (line  172)
* decorator:                             Glossary.           (line  303)
* DEDENT (於 token 模組中):              token --- Constants used with Python parse trees.
                                                             (line   52)
* DEDENT token:                          Indentation.        (line   33)
* DEDENT token <1>:                      Compound statements.
                                                             (line   54)
* dedent() (於 textwrap 模組中):         textwrap --- Text wrapping and filling.
                                                             (line   65)
* deepcopy() (於 copy 模組中):           copy --- Shallow and deep copy operations.
                                                             (line   22)
* default (inspect.Parameter 的屬性):    Introspecting callables with the Signature object.
                                                             (line  168)
* default (optparse.Option 的屬性):      Option attributes.  (line   36)
* default (於 email.policy 模組中):      email policy Policy Objects.
                                                             (line  487)
* DEFAULT (於 unittest.mock 模組中):     DEFAULT.            (line    6)
* default() (cmd.Cmd 的方法):            Cmd Objects.        (line   74)
* default() (json.JSONEncoder 的方法):   Encoders and Decoders.
                                                             (line  192)
* default; parameter; value:             Function definitions.
                                                             (line   53)
* DefaultContext (decimal 中的類別):     Context objects.    (line   72)
* DefaultCookiePolicy (http.cookiejar 中的類別): http cookiejar --- Cookie handling for HTTP clients.
                                                             (line   78)
* defaultdict (collections 中的類別):    defaultdict objects.
                                                             (line    6)
* DefaultDict (typing 中的類別):         Classes functions and decorators.
                                                             (line  360)
* DefaultEventLoopPolicy (asyncio 中的類別): Policy Objects. (line   50)
* DefaultHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  310)
* DefaultHandlerExpand() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  317)
* defaults() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line   77)
* DefaultSelector (selectors 中的類別):  Classes<3>.         (line  161)
* defaultTestLoader (於 unittest 模組中): Loading and running tests.
                                                             (line  429)
* defaultTestResult() (unittest.TestCase 的方法): Test cases.
                                                             (line  713)
* DEFAULT_BUFFER_SIZE (於 io 模組中):    High-level Module Interface.
                                                             (line    6)
* default_bufsize (於 xml.dom.pulldom 模組中): xml dom pulldom --- Support for building partial DOM trees.
                                                             (line  103)
* default_exception_handler() (asyncio.loop 的方法): Error Handling API.
                                                             (line   26)
* default_factory (collections.defaultdict 的屬性): defaultdict objects.
                                                             (line   49)
* DEFAULT_FORMAT (於 tarfile 模組中):    tarfile --- Read and write tar archive files.
                                                             (line  233)
* DEFAULT_IGNORES (於 filecmp 模組中):   The dircmp class.   (line  105)
* default_open() (urllib.request.BaseHandler 的方法): BaseHandler Objects.
                                                             (line   30)
* DEFAULT_PROTOCOL (於 pickle 模組中):   Module Interface.   (line   21)
* default_timer() (於 timeit 模組中):    Python Interface.   (line   31)
* defects (email.headerregistry.BaseHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line   52)
* defects (email.message.EmailMessage 的屬性): email message Representing an email message.
                                                             (line  711)
* defects (email.message.Message 的屬性): email message Message Representing an email message using the compat32 API.
                                                             (line  725)
* define_macro() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  161)
* defpath (於 os 模組中):                Miscellaneous System Information.
                                                             (line  121)
* DefragResult (urllib.parse 中的類別):  Structured Parse Results.
                                                             (line   40)
* DefragResultBytes (urllib.parse 中的類別): Structured Parse Results.
                                                             (line   65)
* def_prog_mode() (於 curses 模組中):    Functions<3>.       (line   70)
* def_shell_mode() (於 curses 模組中):   Functions<3>.       (line   77)
* degrees() (於 math 模組中):            Angular conversion. (line    6)
* degrees() (於 turtle 模組中):          Settings for measurement.
                                                             (line    6)
* delattr() (內建函式):                  內建函式.           (line  357)
* delay() (於 turtle 模組中):            Animation control.  (line    6)
* delayload (http.cookiejar.FileCookieJar 的屬性): CookieJar and FileCookieJar Objects.
                                                             (line  158)
* delay_output() (於 curses 模組中):     Functions<3>.       (line   85)
* delch() (curses.window 的方法):        Window Objects.     (line  177)
* dele() (poplib.POP3 的方法):           POP3 Objects.       (line   67)
* delete() (ftplib.FTP 的方法):          FTP Objects.        (line  206)
* delete() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line   76)
* delete() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line   79)
* deleteacl() (imaplib.IMAP4 的方法):    IMAP4 Objects.      (line   80)
* deletefilehandler() (tkinter.Widget.tk 的方法): File Handlers.
                                                             (line   37)
* DeleteKey() (於 winreg 模組中):        Functions<11>.      (line  102)
* DeleteKeyEx() (於 winreg 模組中):      Functions<11>.      (line  124)
* deleteln() (curses.window 的方法):     Window Objects.     (line  181)
* deleteMe() (bdb.Breakpoint 的方法):    bdb --- Debugger framework.
                                                             (line   41)
* DeleteValue() (於 winreg 模組中):      Functions<11>.      (line  165)
* DELETE_ATTR (opcode):                  Python Bytecode Instructions.
                                                             (line  515)
* DELETE_DEREF (opcode):                 Python Bytecode Instructions.
                                                             (line  749)
* DELETE_FAST (opcode):                  Python Bytecode Instructions.
                                                             (line  719)
* DELETE_GLOBAL (opcode):                Python Bytecode Instructions.
                                                             (line  523)
* DELETE_NAME (opcode):                  Python Bytecode Instructions.
                                                             (line  489)
* DELETE_SUBSCR (opcode):                Python Bytecode Instructions.
                                                             (line  254)
* deletion; target:                      The del statement<2>.
                                                             (line    6)
* deletion; target; list:                The del statement<2>.
                                                             (line    6)
* delimiter (csv.Dialect 的屬性):        Dialects and Formatting Parameters.
                                                             (line   19)
* delimiters:                            Delimiters.         (line    6)
* delitem() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  187)
* deliver_challenge() (於 multiprocessing.connection 模組中): Listeners and Clients.
                                                             (line   15)
* delocalize() (於 locale 模組中):       locale --- Internationalization services.
                                                             (line  439)
* del_param() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  381)
* del_param() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  543)
* demo_app() (於 wsgiref.simple_server 模組中): wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line   36)
* denominator (fractions.Fraction 的屬性): fractions --- Rational numbers.
                                                             (line   93)
* denominator (numbers.Rational 的屬性): The numeric tower.  (line   51)
* DeprecationWarning:                    Warnings.           (line   17)
* deque (collections 中的類別):          deque objects.      (line    6)
* Deque (typing 中的類別):               Classes functions and decorators.
                                                             (line  247)
* dequeue() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   45)
* derwin() (curses.window 的方法):       Window Objects.     (line  186)
* DER_cert_to_PEM_cert() (於 ssl 模組中): Certificate handling.
                                                             (line   91)
* descrgetfunc (C 型態):                 Slot Type typedefs. (line   78)
* description (inspect.Parameter.kind 的屬性): Introspecting callables with the Signature object.
                                                             (line  233)
* description (sqlite3.Cursor 的屬性):   Cursor Objects.     (line  219)
* description() (nntplib.NNTP 的方法):   Methods<3>.         (line  149)
* descriptions() (nntplib.NNTP 的方法):  Methods<3>.         (line  135)
* descriptor:                            Glossary.           (line  325)
* descrsetfunc (C 型態):                 Slot Type typedefs. (line   83)
* dest (optparse.Option 的屬性):         Option attributes.  (line   27)
* destructor:                            Basic customization.
                                                             (line   56)
* destructor <1>:                        Assignment statements.
                                                             (line   73)
* destructor (C 型態):                   Slot Type typedefs. (line   24)
* detach() (io.BufferedIOBase 的方法):   I/O Base Classes.   (line  255)
* detach() (io.TextIOBase 的方法):       Text I/O<2>.        (line   37)
* detach() (socket.socket 的方法):       Socket Objects.     (line   94)
* detach() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line   85)
* detach() (weakref.finalize 的方法):    weakref --- Weak references.
                                                             (line  257)
* Detach() (winreg.PyHKEY 的方法):       Registry Handle Objects.
                                                             (line   40)
* DETACHED_PROCESS (於 subprocess 模組中): Windows Constants.
                                                             (line  106)
* detect_api_mismatch() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  929)
* detect_encoding() (於 tokenize 模組中): Tokenizing Input.  (line   77)
* detect_language() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  197)
* deterministic profiling:               Introduction to the profilers.
                                                             (line    6)
* device_encoding() (於 os 模組中):      File Descriptor Operations.
                                                             (line   67)
* devnull (於 os 模組中):                Miscellaneous System Information.
                                                             (line  136)
* DEVNULL (於 subprocess 模組中):        Using the subprocess Module.
                                                             (line  132)
* devpoll() (於 select 模組中):          select --- Waiting for I/O completion.
                                                             (line   31)
* DevpollSelector (selectors 中的類別):  Classes<3>.         (line  184)
* dgettext() (於 gettext 模組中):        GNU gettext API.    (line   49)
* dgettext() (於 locale 模組中):         Access to message catalogs.
                                                             (line    8)
* Dialect (csv 中的類別):                Module Contents<3>. (line  174)
* dialect (csv.csvreader 的屬性):        Reader Objects.     (line   18)
* dialect (csv.csvwriter 的屬性):        Writer Objects.     (line   31)
* Dialog (msilib 中的類別):              GUI classes.        (line   40)
* dict (2to3 fixer):                     Fixers.             (line   70)
* Dict (typing 中的類別):                Classes functions and decorators.
                                                             (line  349)
* dict (內建類別):                       Mapping Types --- dict.
                                                             (line   27)
* dict() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  204)
* dictConfig() (於 logging.config 模組中): Configuration functions.
                                                             (line   13)
* dictionary:                            Glossary.           (line  341)
* dictionary comprehension:              Glossary.           (line  347)
* dictionary view:                       Glossary.           (line  355)
* dictionary; comprehensions:            Dictionary displays.
                                                             (line    6)
* dictionary; display:                   Dictionary displays.
                                                             (line    6)
* DictReader (csv 中的類別):             Module Contents<3>. (line  102)
* DictWriter (csv 中的類別):             Module Contents<3>. (line  141)
* Differ (difflib 中的類別):             difflib --- Helpers for computing deltas.
                                                             (line   50)
* difference() (frozenset 的方法):       Set Types --- set frozenset.
                                                             (line  109)
* difference_update() (frozenset 的方法): Set Types --- set frozenset.
                                                             (line  182)
* difflib (模組):                        difflib --- Helpers for computing deltas.
                                                             (line    6)
* diff_bytes() (於 difflib 模組中):      difflib --- Helpers for computing deltas.
                                                             (line  340)
* diff_files (filecmp.dircmp 的屬性):    The dircmp class.   (line   90)
* digest() (hashlib.hash 的方法):        Hash algorithms.    (line  128)
* digest() (hashlib.shake 的方法):       SHAKE variable length digests.
                                                             (line   11)
* digest() (hmac.HMAC 的方法):           hmac --- Keyed-Hashing for Message Authentication.
                                                             (line   55)
* digest() (於 hmac 模組中):             hmac --- Keyed-Hashing for Message Authentication.
                                                             (line   30)
* digest_size (hmac.HMAC 的屬性):        hmac --- Keyed-Hashing for Message Authentication.
                                                             (line   89)
* digit() (於 unicodedata 模組中):       unicodedata --- Unicode Database.
                                                             (line   37)
* digits (於 string 模組中):             String constants.   (line   24)
* dir() (ftplib.FTP 的方法):             FTP Objects.        (line  189)
* dir() (內建函式):                      內建函式.           (line  379)
* dircmp (filecmp 中的類別):             The dircmp class.   (line    6)
* directory (http.server.SimpleHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  356)
* Directory (msilib 中的類別):           Directory Objects.  (line    6)
* directory; changing:                   Files and Directories.
                                                             (line  117)
* directory; creating:                   Files and Directories.
                                                             (line  451)
* directory; deleting:                   Directory and files operations.
                                                             (line  257)
* directory; deleting <1>:               Files and Directories.
                                                             (line  638)
* directory; traversal:                  Files and Directories.
                                                             (line 1483)
* directory; traversal <1>:              Files and Directories.
                                                             (line 1579)
* directory; walking:                    Files and Directories.
                                                             (line 1483)
* directory; walking <1>:                Files and Directories.
                                                             (line 1579)
* directory_created() (內建函式):        The Postinstallation script.
                                                             (line   23)
* DirEntry (os 中的類別):                Files and Directories.
                                                             (line  814)
* DirList (tkinter.tix 中的類別):        File Selectors.     (line    6)
* dirname() (於 os.path 模組中):         os path --- Common pathname manipulations.
                                                             (line  105)
* DirSelectBox (tkinter.tix 中的類別):   File Selectors.     (line   26)
* DirSelectDialog (tkinter.tix 中的類別): File Selectors.    (line   20)
* DirsOnSysPath (test.support 中的類別): test support --- Utilities for the Python test suite.
                                                             (line 1068)
* DirTree (tkinter.tix 中的類別):        File Selectors.     (line   13)
* dis (模組):                            dis --- Python bytecode的反組譯器.
                                                             (line    6)
* dis() (dis.Bytecode 的方法):           Bytecode analysis.  (line   47)
* dis() (於 dis 模組中):                 Analysis functions. (line   40)
* dis() (於 pickletools 模組中):         Programmatic Interface<2>.
                                                             (line    6)
* disable (pdb command):                 Debugger Commands.  (line  100)
* disable() (bdb.Breakpoint 的方法):     bdb --- Debugger framework.
                                                             (line   51)
* disable() (profile.Profile 的方法):    profile and cProfile Module Reference.
                                                             (line   82)
* disable() (於 faulthandler 模組中):    Fault handler state.
                                                             (line   22)
* disable() (於 gc 模組中):              gc --- Garbage Collector interface.
                                                             (line   26)
* disable() (於 logging 模組中):         Module-Level Functions.
                                                             (line  167)
* DisableReflectionKey() (於 winreg 模組中): Functions<11>.  (line  486)
* disable_faulthandler() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  469)
* disable_gc() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  481)
* disable_interspersed_args() (optparse.OptionParser 的方法): Querying and manipulating your option parser.
                                                             (line   10)
* disassemble() (於 dis 模組中):         Analysis functions. (line   81)
* discard (http.cookiejar.Cookie 的屬性): Cookie Objects<2>. (line   54)
* discard() (frozenset 的方法):          Set Types --- set frozenset.
                                                             (line  204)
* discard() (mailbox.Mailbox 的方法):    Mailbox objects.    (line   76)
* discard() (mailbox.MH 的方法):         MH.                 (line   76)
* discard_buffers() (asynchat.async_chat 的方法): asynchat --- Asynchronous socket command/response handler.
                                                             (line   84)
* disco() (於 dis 模組中):               Analysis functions. (line   81)
* discover() (unittest.TestLoader 的方法): Loading and running tests.
                                                             (line  117)
* disk_usage() (於 shutil 模組中):       Directory and files operations.
                                                             (line  340)
* dispatcher (asyncore 中的類別):        asyncore --- Asynchronous socket handler.
                                                             (line   67)
* dispatcher_with_send (asyncore 中的類別): asyncore --- Asynchronous socket handler.
                                                             (line  249)
* dispatch_call() (bdb.Bdb 的方法):      bdb --- Debugger framework.
                                                             (line  157)
* dispatch_exception() (bdb.Bdb 的方法): bdb --- Debugger framework.
                                                             (line  177)
* dispatch_line() (bdb.Bdb 的方法):      bdb --- Debugger framework.
                                                             (line  147)
* dispatch_return() (bdb.Bdb 的方法):    bdb --- Debugger framework.
                                                             (line  167)
* dispatch_table (pickle.Pickler 的屬性): Module Interface.  (line  176)
* display (pdb command):                 Debugger Commands.  (line  257)
* displayhook() (於 sys 模組中):         sys --- System-specific parameters and functions.
                                                             (line  244)
* display_name (email.headerregistry.Address 的屬性): email headerregistry Custom Header Objects.
                                                             (line  426)
* display_name (email.headerregistry.Group 的屬性): email headerregistry Custom Header Objects.
                                                             (line  470)
* dist() (於 math 模組中):               Trigonometric functions.
                                                             (line   32)
* distance() (於 turtle 模組中):         Tell Turtle's state.
                                                             (line   68)
* distb() (於 dis 模組中):               Analysis functions. (line   70)
* Distribution (distutils.core 中的類別): distutils core --- Core Distutils functionality.
                                                             (line  294)
* distutils (模組):                      distutils --- Building and installing Python modules.
                                                             (line    6)
* distutils.archive_util (模組):         distutils archive_util --- Archiving utilities.
                                                             (line    6)
* distutils.bcppcompiler (模組):         distutils bcppcompiler --- Borland Compiler.
                                                             (line    6)
* distutils.ccompiler (模組):            distutils ccompiler --- CCompiler base class.
                                                             (line    6)
* distutils.cmd (模組):                  distutils cmd --- Abstract base class for Distutils commands.
                                                             (line    6)
* distutils.command (模組):              distutils command --- Individual Distutils commands.
                                                             (line    5)
* distutils.command.bdist (模組):        distutils command bdist --- Build a binary installer.
                                                             (line    5)
* distutils.command.bdist_dumb (模組):   distutils command bdist_dumb --- Build a "dumb" installer.
                                                             (line    5)
* distutils.command.bdist_msi (模組):    distutils command bdist_msi --- Build a Microsoft Installer binary package.
                                                             (line    6)
* distutils.command.bdist_packager (模組): distutils command bdist_packager --- Abstract base class for packagers.
                                                             (line    5)
* distutils.command.bdist_rpm (模組):    distutils command bdist_rpm --- Build a binary distribution as a Redhat RPM and SRPM.
                                                             (line    5)
* distutils.command.bdist_wininst (模組): distutils command bdist_wininst --- Build a Windows installer.
                                                             (line    6)
* distutils.command.build (模組):        distutils command build --- Build all files of a package.
                                                             (line    5)
* distutils.command.build_clib (模組):   distutils command build_clib --- Build any C libraries in a package.
                                                             (line    5)
* distutils.command.build_ext (模組):    distutils command build_ext --- Build any extensions in a package.
                                                             (line    5)
* distutils.command.build_py (模組):     distutils command build_py --- Build the py/ pyc files of a package.
                                                             (line    6)
* distutils.command.build_scripts (模組): distutils command build_scripts --- Build the scripts of a package.
                                                             (line    5)
* distutils.command.check (模組):        distutils command check --- Check the meta-data of a package.
                                                             (line    6)
* distutils.command.clean (模組):        distutils command clean --- Clean a package build area.
                                                             (line    6)
* distutils.command.config (模組):       distutils command config --- Perform package configuration.
                                                             (line    5)
* distutils.command.install (模組):      distutils command install --- Install a package.
                                                             (line    5)
* distutils.command.install_data (模組): distutils command install_data --- Install data files from a package.
                                                             (line    5)
* distutils.command.install_headers (模組): distutils command install_headers --- Install C/C++ header files from a package.
                                                             (line    5)
* distutils.command.install_lib (模組):  distutils command install_lib --- Install library files from a package.
                                                             (line    5)
* distutils.command.install_scripts (模組): distutils command install_scripts --- Install script files from a package.
                                                             (line    5)
* distutils.command.register (模組):     distutils command register --- Register a module with the Python Package Index.
                                                             (line    6)
* distutils.command.sdist (模組):        distutils command sdist --- Build a source distribution.
                                                             (line    5)
* distutils.core (模組):                 distutils core --- Core Distutils functionality.
                                                             (line    6)
* distutils.cygwinccompiler (模組):      distutils cygwincompiler --- Cygwin Compiler.
                                                             (line    6)
* distutils.debug (模組):                distutils debug --- Distutils debug mode.
                                                             (line    6)
* distutils.dep_util (模組):             distutils dep_util --- Dependency checking.
                                                             (line    6)
* distutils.dir_util (模組):             distutils dir_util --- Directory tree operations.
                                                             (line    6)
* distutils.dist (模組):                 distutils dist --- The Distribution class.
                                                             (line    6)
* distutils.errors (模組):               distutils errors --- Distutils exceptions.
                                                             (line    6)
* distutils.extension (模組):            distutils extension --- The Extension class.
                                                             (line    6)
* distutils.fancy_getopt (模組):         distutils fancy_getopt --- Wrapper around the standard getopt module.
                                                             (line    6)
* distutils.filelist (模組):             distutils filelist --- The FileList class.
                                                             (line    6)
* distutils.file_util (模組):            distutils file_util --- Single file operations.
                                                             (line    6)
* distutils.log (模組):                  distutils log --- Simple PEP 282-style logging.
                                                             (line    5)
* distutils.msvccompiler (模組):         distutils msvccompiler --- Microsoft Compiler.
                                                             (line    6)
* distutils.spawn (模組):                distutils spawn --- Spawn a sub-process.
                                                             (line    6)
* distutils.sysconfig (模組):            distutils sysconfig --- System configuration information.
                                                             (line    6)
* distutils.text_file (模組):            distutils text_file --- The TextFile class.
                                                             (line    6)
* distutils.unixccompiler (模組):        distutils unixccompiler --- Unix C Compiler.
                                                             (line    6)
* distutils.util (模組):                 distutils util --- Miscellaneous other utility functions.
                                                             (line    6)
* distutils.version (模組):              distutils version --- Version number classes.
                                                             (line    5)
* DISTUTILS_DEBUG:                       Debugging the setup script.
                                                             (line   19)
* divide() (decimal.Context 的方法):     Context objects.    (line  271)
* divide_int() (decimal.Context 的方法): Context objects.    (line  275)
* division:                              Binary arithmetic operations.
                                                             (line   28)
* DivisionByZero (decimal 中的類別):     Signals.            (line   33)
* divmod() (decimal.Context 的方法):     Context objects.    (line  279)
* divmod() (內建函式):                   內建函式.           (line  437)
* DllCanUnloadNow() (於 ctypes 模組中):  Utility functions.  (line   76)
* DllGetClassObject() (於 ctypes 模組中): Utility functions. (line   82)
* dllhandle (於 sys 模組中):             sys --- System-specific parameters and functions.
                                                             (line  238)
* dngettext() (於 gettext 模組中):       GNU gettext API.    (line   68)
* dnpgettext() (於 gettext 模組中):      GNU gettext API.    (line   79)
* doc (json.JSONDecodeError 的屬性):     例外<2>.            (line   15)
* DocCGIXMLRPCRequestHandler (xmlrpc.server 中的類別): Documenting XMLRPC server.
                                                             (line   22)
* DocFileSuite() (於 doctest 模組中):    Unittest API.       (line   24)
* doClassCleanups() (unittest.TestCase 的類別成員): Test cases.
                                                             (line  788)
* doCleanups() (unittest.TestCase 的方法): Test cases.       (line  756)
* docmd() (smtplib.SMTP 的方法):         SMTP Objects.       (line   17)
* docstring:                             Class definitions.  (line    6)
* docstring <1>:                         Glossary.           (line  365)
* docstring (doctest.DocTest 的屬性):    DocTest Objects.    (line   49)
* docstrings:                            定義函式 function.  (line   20)
* docstrings <1>:                        說明文件字串.       (line    6)
* DocTest (doctest 中的類別):            DocTest Objects.    (line    6)
* doctest (模組):                        doctest --- Test interactive Python examples.
                                                             (line    6)
* DocTestFailure:                        Debugging.          (line  186)
* DocTestFinder (doctest 中的類別):      DocTestFinder objects.
                                                             (line    6)
* DocTestParser (doctest 中的類別):      DocTestParser objects.
                                                             (line    6)
* DocTestRunner (doctest 中的類別):      DocTestRunner objects.
                                                             (line    6)
* DocTestSuite() (於 doctest 模組中):    Unittest API.       (line   99)
* doctype() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder Objects.
                                                             (line   66)
* documentation string:                  The standard type hierarchy.
                                                             (line  702)
* documentation strings:                 定義函式 function.  (line   20)
* documentation strings <1>:             說明文件字串.       (line    6)
* documentation; generation:             pydoc --- Documentation generator and online help system.
                                                             (line    8)
* documentation; online:                 pydoc --- Documentation generator and online help system.
                                                             (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)
* doc_header (cmd.Cmd 的屬性):           Cmd Objects.        (line  147)
* domain (email.headerregistry.Address 的屬性): email headerregistry Custom Header Objects.
                                                             (line  437)
* domain (tracemalloc.DomainFilter 的屬性): DomainFilter.    (line   20)
* domain (tracemalloc.Filter 的屬性):    Filter.             (line   30)
* domain (tracemalloc.Trace 的屬性):     Trace.              (line   15)
* DomainFilter (tracemalloc 中的類別):   DomainFilter.       (line    6)
* DomainLiberal (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line  156)
* DomainRFC2965Match (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line  149)
* DomainStrict (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line  161)
* DomainStrictNoDots (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line  136)
* DomainStrictNonDomain (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line  142)
* domain_initial_dot (http.cookiejar.Cookie 的屬性): Cookie Objects<2>.
                                                             (line   86)
* domain_return_ok() (http.cookiejar.CookiePolicy 的方法): CookiePolicy Objects.
                                                             (line   27)
* domain_specified (http.cookiejar.Cookie 的屬性): Cookie Objects<2>.
                                                             (line   82)
* DOMEventStream (xml.dom.pulldom 中的類別): DOMEventStream Objects.
                                                             (line    6)
* DOMException:                          Exceptions<14>.     (line   18)
* doModuleCleanups() (於 unittest 模組中): setUpModule and tearDownModule.
                                                             (line   35)
* DomstringSizeErr:                      Exceptions<14>.     (line   23)
* done() (asyncio.Future 的方法):        Future Object.      (line   58)
* done() (asyncio.Task 的方法):          Task Object.        (line  112)
* done() (concurrent.futures.Future 的方法): Future Objects. (line   33)
* done() (xdrlib.Unpacker 的方法):       Unpacker Objects.   (line   26)
* done() (於 turtle 模組中):             Using screen events.
                                                             (line  106)
* DONT_ACCEPT_BLANKLINE (於 doctest 模組中): Option Flags.   (line   30)
* DONT_ACCEPT_TRUE_FOR_1 (於 doctest 模組中): Option Flags.  (line   18)
* dont_write_bytecode (於 sys 模組中):   sys --- System-specific parameters and functions.
                                                             (line  280)
* doRollover() (logging.handlers.RotatingFileHandler 的方法): RotatingFileHandler.
                                                             (line   38)
* doRollover() (logging.handlers.TimedRotatingFileHandler 的方法): TimedRotatingFileHandler.
                                                             (line  101)
* DOT (於 token 模組中):                 token --- Constants used with Python parse trees.
                                                             (line  118)
* dot() (於 turtle 模組中):              Turtle motion.      (line  218)
* DOTALL (於 re 模組中):                 Module Contents.    (line  113)
* doublequote (csv.Dialect 的屬性):      Dialects and Formatting Parameters.
                                                             (line   24)
* DOUBLESLASH (於 token 模組中):         token --- Constants used with Python parse trees.
                                                             (line  214)
* DOUBLESLASHEQUAL (於 token 模組中):    token --- Constants used with Python parse trees.
                                                             (line  218)
* DOUBLESTAR (於 token 模組中):          token --- Constants used with Python parse trees.
                                                             (line  166)
* DOUBLESTAREQUAL (於 token 模組中):     token --- Constants used with Python parse trees.
                                                             (line  210)
* doupdate() (於 curses 模組中):         Functions<3>.       (line   89)
* down (pdb command):                    Debugger Commands.  (line   61)
* down() (於 turtle 模組中):             Drawing state.      (line    6)
* do_clear() (bdb.Bdb 的方法):           bdb --- Debugger framework.
                                                             (line  234)
* do_command() (curses.textpad.Textbox 的方法): Textbox objects.
                                                             (line   30)
* do_GET() (http.server.SimpleHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  371)
* do_handshake() (ssl.SSLSocket 的方法): SSL Sockets.        (line  119)
* do_HEAD() (http.server.SimpleHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  364)
* do_POST() (http.server.CGIHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  482)
* dpgettext() (於 gettext 模組中):       GNU gettext API.    (line   75)
* drain() (asyncio.StreamWriter 的方法): StreamWriter.       (line   66)
* dropwhile() (於 itertools 模組中):     Itertool functions. (line  266)
* drop_whitespace (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  190)
* dst() (datetime.datetime 的方法):      datetime Objects.   (line  484)
* dst() (datetime.time 的方法):          time Objects.       (line  233)
* dst() (datetime.timezone 的方法):      timezone Objects.   (line   57)
* dst() (datetime.tzinfo 的方法):        tzinfo Objects.     (line   65)
* DTDHandler (xml.sax.handler 中的類別): xml sax handler --- Base classes for SAX handlers.
                                                             (line   24)
* duck-typing:                           Glossary.           (line  374)
* DumbWriter (formatter 中的類別):       Writer Implementations.
                                                             (line   22)
* dummy_threading (模組):                dummy_threading --- Drop-in replacement for the threading module.
                                                             (line    6)
* dump() (pickle.Pickler 的方法):        Module Interface.   (line  155)
* dump() (tracemalloc.Snapshot 的方法):  Snapshot.           (line   29)
* dump() (於 ast 模組中):                ast Helpers.        (line  199)
* dump() (於 json 模組中):               Basic Usage.        (line    6)
* dump() (於 marshal 模組中):            marshal --- Internal Python object serialization.
                                                             (line   47)
* dump() (於 pickle 模組中):             Module Interface.   (line   35)
* dump() (於 plistlib 模組中):           plistlib --- Generate and parse Mac OS X plist files.
                                                             (line   84)
* dump() (於 xml.etree.ElementTree 模組中): Functions<6>.    (line   86)
* dumps() (於 json 模組中):              Basic Usage.        (line   76)
* dumps() (於 marshal 模組中):           marshal --- Internal Python object serialization.
                                                             (line   72)
* dumps() (於 pickle 模組中):            Module Interface.   (line   47)
* dumps() (於 plistlib 模組中):          plistlib --- Generate and parse Mac OS X plist files.
                                                             (line  114)
* dumps() (於 xmlrpc.client 模組中):     Convenience Functions.
                                                             (line    6)
* dump_stats() (profile.Profile 的方法): profile and cProfile Module Reference.
                                                             (line   96)
* dump_stats() (pstats.Stats 的方法):    The Stats Class.    (line   59)
* dump_traceback() (於 faulthandler 模組中): Dumping the traceback.
                                                             (line    6)
* dump_traceback_later() (於 faulthandler 模組中): Dumping the tracebacks after a timeout.
                                                             (line    6)
* dup() (socket.socket 的方法):          Socket Objects.     (line  102)
* dup() (於 os 模組中):                  File Descriptor Operations.
                                                             (line   73)
* dup2() (於 os 模組中):                 File Descriptor Operations.
                                                             (line   84)
* DuplicateOptionError:                  Exceptions<4>.      (line   24)
* DuplicateSectionError:                 Exceptions<4>.      (line   14)
* DUP_TOP (opcode):                      Python Bytecode Instructions.
                                                             (line   79)
* DUP_TOP_TWO (opcode):                  Python Bytecode Instructions.
                                                             (line   85)
* dwFlags (subprocess.STARTUPINFO 的屬性): Windows Popen Helpers.
                                                             (line   19)
* DynamicClassAttribute() (於 types 模組中): Additional Utility Classes and Functions.
                                                             (line   38)
* D_FMT (於 locale 模組中):              locale --- Internationalization services.
                                                             (line  195)
* D_T_FMT (於 locale 模組中):            locale --- Internationalization services.
                                                             (line  189)
* e (於 cmath 模組中):                   Constants<3>.       (line   10)
* e (於 math 模組中):                    Constants<2>.       (line   11)
* E2BIG (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line   55)
* e; in numeric literal:                 Integer literals.   (line   40)
* EACCES (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line   79)
* EADDRINUSE (於 errno 模組中):          errno --- Standard errno system symbols.
                                                             (line  419)
* EADDRNOTAVAIL (於 errno 模組中):       errno --- Standard errno system symbols.
                                                             (line  423)
* EADV (於 errno 模組中):                errno --- Standard errno system symbols.
                                                             (line  299)
* EAFNOSUPPORT (於 errno 模組中):        errno --- Standard errno system symbols.
                                                             (line  415)
* EAFP:                                  Glossary.           (line  387)
* EAGAIN (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line   71)
* EALREADY (於 errno 模組中):            errno --- Standard errno system symbols.
                                                             (line  483)
* east_asian_width() (於 unicodedata 模組中): unicodedata --- Unicode Database.
                                                             (line   64)
* EBADE (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line  235)
* EBADF (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line   63)
* EBADFD (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  335)
* EBADMSG (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  323)
* EBADR (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line  239)
* EBADRQC (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  251)
* EBADSLT (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  255)
* EBFONT (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  263)
* EBUSY (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line   91)
* ECHILD (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line   67)
* echo() (於 curses 模組中):             Functions<3>.       (line  105)
* echochar() (curses.window 的方法):     Window Objects.     (line  196)
* ECHRNG (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  203)
* ECOMM (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line  307)
* ECONNABORTED (於 errno 模組中):        errno --- Standard errno system symbols.
                                                             (line  439)
* ECONNREFUSED (於 errno 模組中):        errno --- Standard errno system symbols.
                                                             (line  471)
* ECONNRESET (於 errno 模組中):          errno --- Standard errno system symbols.
                                                             (line  443)
* EDEADLK (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  167)
* EDEADLOCK (於 errno 模組中):           errno --- Standard errno system symbols.
                                                             (line  259)
* EDESTADDRREQ (於 errno 模組中):        errno --- Standard errno system symbols.
                                                             (line  383)
* edit() (curses.textpad.Textbox 的方法): Textbox objects.   (line   19)
* EDOM (於 errno 模組中):                errno --- Standard errno system symbols.
                                                             (line  159)
* EDOTDOT (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  319)
* EDQUOT (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  515)
* EEXIST (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line   95)
* EFAULT (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line   83)
* EFBIG (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line  135)
* effective() (於 bdb 模組中):           bdb --- Debugger framework.
                                                             (line  397)
* ehlo() (smtplib.SMTP 的方法):          SMTP Objects.       (line   58)
* ehlo_or_helo_if_needed() (smtplib.SMTP 的方法): SMTP Objects.
                                                             (line   75)
* EHOSTDOWN (於 errno 模組中):           errno --- Standard errno system symbols.
                                                             (line  475)
* EHOSTUNREACH (於 errno 模組中):        errno --- Standard errno system symbols.
                                                             (line  479)
* EIDRM (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line  199)
* EILSEQ (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  363)
* EINPROGRESS (於 errno 模組中):         errno --- Standard errno system symbols.
                                                             (line  487)
* EINTR (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line   38)
* EINVAL (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  115)
* EIO (於 errno 模組中):                 errno --- Standard errno system symbols.
                                                             (line   47)
* EISCONN (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  451)
* EISDIR (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  111)
* EISNAM (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  507)
* EL2HLT (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  231)
* EL2NSYNC (於 errno 模組中):            errno --- Standard errno system symbols.
                                                             (line  207)
* EL3HLT (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  211)
* EL3RST (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  215)
* Element (xml.etree.ElementTree 中的類別): Element Objects. (line    6)
* ElementDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  202)
* elements() (collections.Counter 的方法): Counter 物件.     (line   63)
* ElementTree (xml.etree.ElementTree 中的類別): ElementTree Objects.
                                                             (line    6)
* element_create() (tkinter.ttk.Style 的方法): Ttk Styling.  (line  131)
* element_names() (tkinter.ttk.Style 的方法): Ttk Styling.   (line  183)
* element_options() (tkinter.ttk.Style 的方法): Ttk Styling. (line  187)
* ELIBACC (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  343)
* ELIBBAD (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  347)
* ELIBEXEC (於 errno 模組中):            errno --- Standard errno system symbols.
                                                             (line  359)
* ELIBMAX (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  355)
* ELIBSCN (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  351)
* Ellinghouse, Lance:                    uu --- Encode and decode uuencode files.
                                                             (line   20)
* Ellipsis (內建變數):                   內建常數.           (line   52)
* ELLIPSIS (於 doctest 模組中):          Option Flags.       (line   49)
* ELLIPSIS (於 token 模組中):            token --- Constants used with Python parse trees.
                                                             (line  234)
* ELNRNG (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  219)
* ELOOP (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line  187)
* else; conditional expression:          Conditional expressions.
                                                             (line    6)
* email (模組):                          email --- An email and MIME handling package.
                                                             (line    6)
* email.charset (模組):                  email charset Representing character sets.
                                                             (line    6)
* email.contentmanager (模組):           email contentmanager Managing MIME Content.
                                                             (line    6)
* email.encoders (模組):                 email encoders Encoders.
                                                             (line    6)
* email.errors (模組):                   email errors Exception and Defect classes.
                                                             (line    6)
* email.generator (模組):                email generator Generating MIME documents.
                                                             (line    6)
* email.header (模組):                   email header Internationalized headers.
                                                             (line    6)
* email.headerregistry (模組):           email headerregistry Custom Header Objects.
                                                             (line    6)
* email.iterators (模組):                email iterators Iterators.
                                                             (line    6)
* email.message (模組):                  email message Representing an email message.
                                                             (line    6)
* email.mime (模組):                     email mime Creating email and MIME objects from scratch.
                                                             (line    6)
* email.parser (模組):                   email parser Parsing email messages.
                                                             (line    6)
* email.policy (模組):                   email policy Policy Objects.
                                                             (line    6)
* email.utils (模組):                    email utils Miscellaneous utilities.
                                                             (line    6)
* EmailMessage (email.message 中的類別): email message Representing an email message.
                                                             (line   52)
* EmailPolicy (email.policy 中的類別):   email policy Policy Objects.
                                                             (line  343)
* EMFILE (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  123)
* emit() (logging.FileHandler 的方法):   FileHandler.        (line   27)
* emit() (logging.Handler 的方法):       Handler Objects.    (line  107)
* emit() (logging.handlers.BufferingHandler 的方法): MemoryHandler.
                                                             (line   24)
* emit() (logging.handlers.DatagramHandler 的方法): DatagramHandler.
                                                             (line   20)
* emit() (logging.handlers.HTTPHandler 的方法): HTTPHandler. (line   36)
* emit() (logging.handlers.NTEventLogHandler 的方法): NTEventLogHandler.
                                                             (line   38)
* emit() (logging.handlers.QueueHandler 的方法): QueueHandler.
                                                             (line   31)
* emit() (logging.handlers.RotatingFileHandler 的方法): RotatingFileHandler.
                                                             (line   42)
* emit() (logging.handlers.SMTPHandler 的方法): SMTPHandler. (line   35)
* emit() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   24)
* emit() (logging.handlers.SysLogHandler 的方法): SysLogHandler.
                                                             (line   43)
* emit() (logging.handlers.TimedRotatingFileHandler 的方法): TimedRotatingFileHandler.
                                                             (line  105)
* emit() (logging.handlers.WatchedFileHandler 的方法): WatchedFileHandler.
                                                             (line   46)
* emit() (logging.NullHandler 的方法):   NullHandler.        (line   16)
* emit() (logging.StreamHandler 的方法): StreamHandler.      (line   17)
* EMLINK (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  151)
* Empty:                                 queue --- A synchronized queue class.
                                                             (line   82)
* empty (inspect.Parameter 的屬性):      Introspecting callables with the Signature object.
                                                             (line  151)
* empty (inspect.Signature 的屬性):      Introspecting callables with the Signature object.
                                                             (line   73)
* empty() (asyncio.Queue 的方法):        Queue.              (line   28)
* empty() (multiprocessing.Queue 的方法): Pipes and Queues.  (line  108)
* empty() (multiprocessing.SimpleQueue 的方法): Pipes and Queues.
                                                             (line  208)
* empty() (queue.Queue 的方法):          Queue Objects.      (line   15)
* empty() (queue.SimpleQueue 的方法):    SimpleQueue Objects.
                                                             (line   14)
* empty() (sched.scheduler 的方法):      Scheduler Objects.  (line   47)
* empty; list:                           List displays.      (line    6)
* empty; tuple:                          The standard type hierarchy.
                                                             (line  172)
* empty; tuple <1>:                      Parenthesized forms.
                                                             (line   16)
* emptyline() (cmd.Cmd 的方法):          Cmd Objects.        (line   68)
* EMPTY_NAMESPACE (於 xml.dom 模組中):   Module Contents<4>. (line   35)
* EMSGSIZE (於 errno 模組中):            errno --- Standard errno system symbols.
                                                             (line  387)
* EMULTIHOP (於 errno 模組中):           errno --- Standard errno system symbols.
                                                             (line  315)
* enable (pdb command):                  Debugger Commands.  (line  107)
* enable() (bdb.Breakpoint 的方法):      bdb --- Debugger framework.
                                                             (line   47)
* enable() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line   84)
* enable() (profile.Profile 的方法):     profile and cProfile Module Reference.
                                                             (line   78)
* enable() (於 cgitb 模組中):            cgitb --- Traceback manager for CGI scripts.
                                                             (line   30)
* enable() (於 faulthandler 模組中):     Fault handler state.
                                                             (line    6)
* enable() (於 gc 模組中):               gc --- Garbage Collector interface.
                                                             (line   22)
* EnableReflectionKey() (於 winreg 模組中): Functions<11>.   (line  504)
* enable_callback_tracebacks() (於 sqlite3 模組中): Module functions and constants.
                                                             (line  189)
* enable_interspersed_args() (optparse.OptionParser 的方法): Querying and manipulating your option parser.
                                                             (line   31)
* enable_load_extension() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line  249)
* enable_traversal() (tkinter.ttk.Notebook 的方法): ttk Notebook.
                                                             (line   75)
* ENABLE_USER_SITE (於 site 模組中):     Module contents<3>. (line   10)
* ENAMETOOLONG (於 errno 模組中):        errno --- Standard errno system symbols.
                                                             (line  171)
* ENAVAIL (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  503)
* enclose() (curses.window 的方法):      Window Objects.     (line  201)
* encode (codecs.CodecInfo 的屬性):      codecs --- Codec registry and base classes.
                                                             (line   69)
* encode() (codecs.Codec 的方法):        Stateless Encoding and Decoding.
                                                             (line    9)
* encode() (codecs.IncrementalEncoder 的方法): IncrementalEncoder Objects.
                                                             (line   28)
* encode() (email.header.Header 的方法): email header Internationalized headers.
                                                             (line  125)
* encode() (json.JSONEncoder 的方法):    Encoders and Decoders.
                                                             (line  211)
* encode() (str 的方法):                 String Methods<2>.  (line   60)
* encode() (xmlrpc.client.Binary 的方法): Binary Objects.    (line   25)
* encode() (xmlrpc.client.DateTime 的方法): 日期時間物件.    (line   17)
* encode() (於 base64 模組中):           base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  222)
* encode() (於 codecs 模組中):           codecs --- Codec registry and base classes.
                                                             (line   23)
* encode() (於 quopri 模組中):           quopri --- Encode and decode MIME quoted-printable data.
                                                             (line   29)
* encode() (於 uu 模組中):               uu --- Encode and decode uuencode files.
                                                             (line   25)
* encodebytes() (於 base64 模組中):      base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  232)
* EncodedFile() (於 codecs 模組中):      codecs --- Codec registry and base classes.
                                                             (line  194)
* encodePriority() (logging.handlers.SysLogHandler 的方法): SysLogHandler.
                                                             (line   76)
* encodestring() (於 base64 模組中):     base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  242)
* encodestring() (於 quopri 模組中):     quopri --- Encode and decode MIME quoted-printable data.
                                                             (line   46)
* encode_7or8bit() (於 email.encoders 模組中): email encoders Encoders.
                                                             (line   57)
* encode_base64() (於 email.encoders 模組中): email encoders Encoders.
                                                             (line   49)
* encode_noop() (於 email.encoders 模組中): email encoders Encoders.
                                                             (line   63)
* encode_quopri() (於 email.encoders 模組中): email encoders Encoders.
                                                             (line   42)
* encode_rfc2231() (於 email.utils 模組中): email utils Miscellaneous utilities.
                                                             (line  178)
* encoding (curses.window 的屬性):       Window Objects.     (line  208)
* encoding (io.TextIOBase 的屬性):       Text I/O<2>.        (line   15)
* encoding (UnicodeError 的屬性):        Concrete exceptions.
                                                             (line  359)
* ENCODING (於 tarfile 模組中):          tarfile --- Read and write tar archive files.
                                                             (line  212)
* ENCODING (於 token 模組中):            token --- Constants used with Python parse trees.
                                                             (line  272)
* encoding declarations (source file):   Encoding declarations.
                                                             (line    6)
* encodings.idna (模組):                 encodings idna --- Internationalized Domain Names in Applications.
                                                             (line    6)
* encodings.mbcs (模組):                 encodings mbcs --- Windows ANSI codepage.
                                                             (line    6)
* encodings.utf_8_sig (模組):            encodings utf_8_sig --- UTF-8 codec with BOM signature.
                                                             (line    6)
* encodings_map (mimetypes.MimeTypes 的屬性): MimeTypes Objects.
                                                             (line   33)
* encodings_map (於 mimetypes 模組中):   mimetypes --- Map filenames to MIME types.
                                                             (line  135)
* end (UnicodeError 的屬性):             Concrete exceptions.
                                                             (line  375)
* end() (re.Match 的方法):               Match Objects.      (line  131)
* end() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder Objects.
                                                             (line   38)
* EndCdataSectionHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  306)
* EndDoctypeDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  197)
* endDocument() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line   40)
* endElement() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line   95)
* EndElementHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  232)
* endElementNS() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line  121)
* endheaders() (http.client.HTTPConnection 的方法): HTTPConnection Objects.
                                                             (line  142)
* ENDMARKER (於 token 模組中):           token --- Constants used with Python parse trees.
                                                             (line   40)
* EndNamespaceDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  285)
* endpos (re.Match 的屬性):              Match Objects.      (line  170)
* endPrefixMapping() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line   73)
* endswith() (bytearray 的方法):         Bytes and Bytearray Operations.
                                                             (line   67)
* endswith() (bytes 的方法):             Bytes and Bytearray Operations.
                                                             (line   67)
* endswith() (str 的方法):               String Methods<2>.  (line   74)
* endwin() (於 curses 模組中):           Functions<3>.       (line  110)
* END_ASYNC_FOR (opcode):                Python Bytecode Instructions.
                                                             (line  284)
* end_col_offset (ast.AST 的屬性):       Node classes.       (line   39)
* end_fill() (於 turtle 模組中):         Filling.            (line   20)
* END_FINALLY (opcode):                  Python Bytecode Instructions.
                                                             (line  415)
* end_headers() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  265)
* end_lineno (ast.AST 的屬性):           Node classes.       (line   39)
* end_ns() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder Objects.
                                                             (line   85)
* end_paragraph() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line   26)
* end_poly() (於 turtle 模組中):         Special Turtle methods.
                                                             (line   11)
* ENETDOWN (於 errno 模組中):            errno --- Standard errno system symbols.
                                                             (line  427)
* ENETRESET (於 errno 模組中):           errno --- Standard errno system symbols.
                                                             (line  435)
* ENETUNREACH (於 errno 模組中):         errno --- Standard errno system symbols.
                                                             (line  431)
* ENFILE (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  119)
* ENOANO (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  247)
* ENOBUFS (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  447)
* ENOCSI (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  227)
* ENODATA (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  271)
* ENODEV (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  103)
* ENOENT (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line   30)
* ENOEXEC (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line   59)
* ENOLCK (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  175)
* ENOLINK (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  295)
* ENOMEM (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line   75)
* ENOMSG (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  195)
* ENONET (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  283)
* ENOPKG (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  287)
* ENOPROTOOPT (於 errno 模組中):         errno --- Standard errno system symbols.
                                                             (line  395)
* ENOSPC (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  139)
* ENOSR (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line  279)
* ENOSTR (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  267)
* ENOSYS (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  179)
* ENOTBLK (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line   87)
* ENOTCONN (於 errno 模組中):            errno --- Standard errno system symbols.
                                                             (line  455)
* ENOTDIR (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  107)
* ENOTEMPTY (於 errno 模組中):           errno --- Standard errno system symbols.
                                                             (line  183)
* ENOTNAM (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  499)
* ENOTSOCK (於 errno 模組中):            errno --- Standard errno system symbols.
                                                             (line  379)
* ENOTTY (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  127)
* ENOTUNIQ (於 errno 模組中):            errno --- Standard errno system symbols.
                                                             (line  331)
* enqueue() (logging.handlers.QueueHandler 的方法): QueueHandler.
                                                             (line   53)
* enqueue_sentinel() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   86)
* ensurepip (模組):                      ensurepip --- Bootstrapping the pip installer.
                                                             (line    6)
* ensure_directories() (venv.EnvBuilder 的方法): API<2>.     (line   77)
* ensure_future() (於 asyncio 模組中):   Future Functions.   (line   19)
* enter() (sched.scheduler 的方法):      Scheduler Objects.  (line   30)
* enterabs() (sched.scheduler 的方法):   Scheduler Objects.  (line    9)
* enter_async_context() (contextlib.AsyncExitStack 的方法): Utilities.
                                                             (line  463)
* enter_context() (contextlib.ExitStack 的方法): Utilities.  (line  382)
* entities (xml.dom.DocumentType 的屬性): DocumentType Objects.
                                                             (line   38)
* EntityDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  258)
* entitydefs (於 html.entities 模組中):  html entities --- Definitions of HTML general entities.
                                                             (line   25)
* EntityResolver (xml.sax.handler 中的類別): xml sax handler --- Base classes for SAX handlers.
                                                             (line   31)
* Enum (enum 中的類別):                  Module Contents<2>. (line   11)
* enum (模組):                           enum --- Support for enumerations.
                                                             (line    6)
* enumerate() (內建函式):                內建函式.           (line  449)
* enumerate() (於 threading 模組中):     threading --- Thread-based parallelism.
                                                             (line  107)
* EnumKey() (於 winreg 模組中):          Functions<11>.      (line  177)
* EnumValue() (於 winreg 模組中):        Functions<11>.      (line  196)
* enum_certificates() (於 ssl 模組中):   Certificate handling.
                                                             (line  129)
* enum_crls() (於 ssl 模組中):           Certificate handling.
                                                             (line  152)
* EnvBuilder (venv 中的類別):            API<2>.             (line   11)
* environ (於 os 模組中):                Process Parameters. (line   16)
* environ (於 posix 模組中):             Notable Module Contents.
                                                             (line    9)
* environb (於 os 模組中):               Process Parameters. (line   55)
* environment:                           Resolution of names.
                                                             (line   12)
* environment variables; deleting:       Process Parameters. (line  501)
* environment variables; setting:        Process Parameters. (line  318)
* EnvironmentError:                      Concrete exceptions.
                                                             (line  411)
* Environments; virtual:                 venv --- Creation of virtual environments.
                                                             (line   10)
* EnvironmentVarGuard (test.support 中的類別): test support --- Utilities for the Python test suite.
                                                             (line 1024)
* ENXIO (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line   51)
* eof (bz2.BZ2Decompressor 的屬性):      Incremental de compression.
                                                             (line   72)
* eof (lzma.LZMADecompressor 的屬性):    Compressing and decompressing data in memory.
                                                             (line  165)
* eof (shlex.shlex 的屬性):              shlex Objects.      (line  177)
* eof (ssl.MemoryBIO 的屬性):            Memory BIO Support<2>.
                                                             (line  143)
* eof (zlib.Decompress 的屬性):          zlib --- Compression compatible with gzip.
                                                             (line  244)
* EOFError:                              Concrete exceptions.
                                                             (line   19)
* EOFError (built-in exception):         檔案（File）物件.   (line   42)
* eof_received() (asyncio.BufferedProtocol 的方法): Buffered Streaming Protocols.
                                                             (line   42)
* eof_received() (asyncio.Protocol 的方法): Streaming Protocols.
                                                             (line   30)
* EOPNOTSUPP (於 errno 模組中):          errno --- Standard errno system symbols.
                                                             (line  407)
* EOVERFLOW (於 errno 模組中):           errno --- Standard errno system symbols.
                                                             (line  327)
* EPERM (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line   26)
* EPFNOSUPPORT (於 errno 模組中):        errno --- Standard errno system symbols.
                                                             (line  411)
* epilogue (email.message.EmailMessage 的屬性): email message Representing an email message.
                                                             (line  703)
* epilogue (email.message.Message 的屬性): email message Message Representing an email message using the compat32 API.
                                                             (line  715)
* EPIPE (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line  155)
* epoch:                                 time --- Time access and conversions.
                                                             (line   18)
* epoll() (於 select 模組中):            select --- Waiting for I/O completion.
                                                             (line   49)
* EpollSelector (selectors 中的類別):    Classes<3>.         (line  175)
* EPROTO (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  311)
* EPROTONOSUPPORT (於 errno 模組中):     errno --- Standard errno system symbols.
                                                             (line  399)
* EPROTOTYPE (於 errno 模組中):          errno --- Standard errno system symbols.
                                                             (line  391)
* eq() (於 operator 模組中):             operator --- Standard operators as functions.
                                                             (line   24)
* EQEQUAL (於 token 模組中):             token --- Constants used with Python parse trees.
                                                             (line  134)
* EQUAL (於 token 模組中):               token --- Constants used with Python parse trees.
                                                             (line  114)
* ERA (於 locale 模組中):                locale --- Internationalization services.
                                                             (line  264)
* ERANGE (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  163)
* erase() (curses.window 的方法):        Window Objects.     (line  218)
* erasechar() (於 curses 模組中):        Functions<3>.       (line  114)
* ERA_D_FMT (於 locale 模組中):          locale --- Internationalization services.
                                                             (line  286)
* ERA_D_T_FMT (於 locale 模組中):        locale --- Internationalization services.
                                                             (line  281)
* ERA_T_FMT (於 locale 模組中):          locale --- Internationalization services.
                                                             (line  291)
* EREMCHG (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  339)
* EREMOTE (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  291)
* EREMOTEIO (於 errno 模組中):           errno --- Standard errno system symbols.
                                                             (line  511)
* ERESTART (於 errno 模組中):            errno --- Standard errno system symbols.
                                                             (line  367)
* erf() (於 math 模組中):                Special functions.  (line    6)
* erfc() (於 math 模組中):               Special functions.  (line   20)
* EROFS (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line  147)
* ERR (於 curses 模組中):                Constants<6>.       (line    8)
* errcheck (ctypes._FuncPtr 的屬性):     Foreign functions.  (line   59)
* errcode (xmlrpc.client.ProtocolError 的屬性): ProtocolError Objects.
                                                             (line   17)
* errmsg (xmlrpc.client.ProtocolError 的屬性): ProtocolError Objects.
                                                             (line   21)
* errno (OSError 的屬性):                Concrete exceptions.
                                                             (line  134)
* errno (模組):                          errno --- Standard errno system symbols.
                                                             (line    6)
* error:                                 Module Contents.    (line  351)
* error <1>:                             Functions and Exceptions.
                                                             (line    8)
* Error:                                 copy --- Shallow and deep copy operations.
                                                             (line   26)
* Error <1>:                             Directory and files operations.
                                                             (line  398)
* error <2>:                             dbm --- Interfaces to Unix "databases".
                                                             (line   16)
* error <3>:                             dbm gnu --- GNU's reinterpretation of dbm.
                                                             (line   21)
* error <4>:                             dbm ndbm --- Interface based on ndbm.
                                                             (line   21)
* error <5>:                             dbm dumb --- Portable DBM implementation.
                                                             (line   24)
* Error <2>:                             Exceptions<3>.      (line   10)
* error <6>:                             zlib --- Compression compatible with gzip.
                                                             (line   24)
* Error <3>:                             Module Contents<3>. (line  263)
* Error <4>:                             Exceptions<4>.      (line    6)
* Error <5>:                             Exceptions<5>.      (line    8)
* error <7>:                             os --- Miscellaneous operating system interfaces.
                                                             (line   42)
* error <8>:                             getopt --- C-style parser for command line options.
                                                             (line   85)
* error <9>:                             Functions<3>.       (line    8)
* error <10>:                            _thread --- Low-level threading API.
                                                             (line   20)
* error <11>:                            Exceptions<10>.     (line    6)
* error <12>:                            select --- Waiting for I/O completion.
                                                             (line   24)
* Error <6>:                             Exceptions<12>.     (line    9)
* Error <7>:                             binhex --- Encode and decode binhex4 files.
                                                             (line   33)
* Error <8>:                             binascii --- Convert between binary and ASCII.
                                                             (line  172)
* Error <9>:                             uu --- Encode and decode uuencode files.
                                                             (line   51)
* error <13>:                            xml parsers expat --- Fast XML parsing using Expat.
                                                             (line   31)
* Error <10>:                            webbrowser --- Convenient Web-browser controller.
                                                             (line   44)
* error <14>:                            audioop --- Manipulate raw audio data.
                                                             (line   26)
* Error <11>:                            sunau --- Read and write Sun AU files.
                                                             (line   75)
* Error <12>:                            wave --- Read and write WAV files.
                                                             (line   55)
* Error <13>:                            locale --- Internationalization services.
                                                             (line   22)
* error <15>:                            resource --- Resource usage information.
                                                             (line   17)
* error <16>:                            nis --- Interface to Sun's NIS Yellow Pages.
                                                             (line   54)
* error handling:                        Exceptions.         (line    6)
* error() (argparse.ArgumentParser 的方法): Exiting methods. (line   18)
* error() (logging.Logger 的方法):       Logger Objects.     (line  229)
* error() (urllib.request.OpenerDirector 的方法): OpenerDirector Objects.
                                                             (line   58)
* error() (xml.sax.handler.ErrorHandler 的方法): ErrorHandler Objects.
                                                             (line   16)
* error() (於 logging 模組中):           Module-Level Functions.
                                                             (line  133)
* ErrorByteIndex (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line  132)
* ErrorCode (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line  136)
* errorcode (於 errno 模組中):           errno --- Standard errno system symbols.
                                                             (line   13)
* ErrorColumnNumber (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line  142)
* ErrorHandler (xml.sax.handler 中的類別): xml sax handler --- Base classes for SAX handlers.
                                                             (line   38)
* ErrorLineNumber (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line  146)
* errors:                                Exceptions.         (line    6)
* errors (io.TextIOBase 的屬性):         Text I/O<2>.        (line   20)
* errors (unittest.TestLoader 的屬性):   Loading and running tests.
                                                             (line   17)
* errors (unittest.TestResult 的屬性):   Loading and running tests.
                                                             (line  236)
* Errors; logging:                       logging --- Logging facility for Python.
                                                             (line    8)
* ErrorString() (於 xml.parsers.expat 模組中): xml parsers expat --- Fast XML parsing using Expat.
                                                             (line   42)
* ERRORTOKEN (於 token 模組中):          token --- Constants used with Python parse trees.
                                                             (line  252)
* error_body (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  259)
* error_content_type (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  151)
* error_headers (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  252)
* error_leader() (shlex.shlex 的方法):   shlex Objects.      (line   69)
* error_message_format (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  143)
* error_output() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line  224)
* error_perm:                            ftplib --- FTP protocol client.
                                                             (line  122)
* error_proto:                           ftplib --- FTP protocol client.
                                                             (line  127)
* error_proto <1>:                       poplib --- POP3 protocol client.
                                                             (line   82)
* error_received() (asyncio.DatagramProtocol 的方法): Datagram Protocols.
                                                             (line   15)
* error_reply:                           ftplib --- FTP protocol client.
                                                             (line  112)
* error_status (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  246)
* error_temp:                            ftplib --- FTP protocol client.
                                                             (line  117)
* escape (shlex.shlex 的屬性):           shlex Objects.      (line  110)
* escape sequence:                       String and Bytes literals.
                                                             (line   72)
* escape() (於 glob 模組中):             glob --- Unix style pathname pattern expansion.
                                                             (line   62)
* escape() (於 html 模組中):             html --- HyperText Markup Language support.
                                                             (line   12)
* escape() (於 re 模組中):               Module Contents.    (line  314)
* escape() (於 xml.sax.saxutils 模組中): xml sax saxutils --- SAX Utilities.
                                                             (line   14)
* escapechar (csv.Dialect 的屬性):       Dialects and Formatting Parameters.
                                                             (line   35)
* escapedquotes (shlex.shlex 的屬性):    shlex Objects.      (line  122)
* ESHUTDOWN (於 errno 模組中):           errno --- Standard errno system symbols.
                                                             (line  459)
* ESOCKTNOSUPPORT (於 errno 模組中):     errno --- Standard errno system symbols.
                                                             (line  403)
* ESPIPE (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  143)
* ESRCH (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line   34)
* ESRMNT (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  303)
* ESTALE (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  491)
* ESTRPIPE (於 errno 模組中):            errno --- Standard errno system symbols.
                                                             (line  371)
* ETIME (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line  275)
* ETIMEDOUT (於 errno 模組中):           errno --- Standard errno system symbols.
                                                             (line  467)
* Etiny() (decimal.Context 的方法):      Context objects.    (line  213)
* ETOOMANYREFS (於 errno 模組中):        errno --- Standard errno system symbols.
                                                             (line  463)
* Etop() (decimal.Context 的方法):       Context objects.    (line  219)
* ETXTBSY (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  131)
* EUCLEAN (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  495)
* EUNATCH (於 errno 模組中):             errno --- Standard errno system symbols.
                                                             (line  223)
* EUSERS (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  375)
* eval() (內建函式):                     內建函式.           (line  472)
* 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 --- Event scheduler.
                                                             (line    8)
* event() (msilib.Control 的方法):       GUI classes.        (line   16)
* Event() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  165)
* events (selectors.SelectorKey 的屬性): Classes<3>.         (line   44)
* events (widgets):                      Bindings and Events.
                                                             (line    6)
* EWOULDBLOCK (於 errno 模組中):         errno --- Standard errno system symbols.
                                                             (line  191)
* Example (doctest 中的類別):            Example Objects.    (line    6)
* example (doctest.DocTestFailure 的屬性): Debugging.        (line  200)
* example (doctest.UnexpectedException 的屬性): Debugging.   (line  221)
* examples (doctest.DocTest 的屬性):     DocTest Objects.    (line   17)
* excel (csv 中的類別):                  Module Contents<3>. (line  181)
* excel_tab (csv 中的類別):              Module Contents<3>. (line  187)
* except (2to3 fixer):                   Fixers.             (line   82)
* excepthook() (in module sys):          cgitb --- Traceback manager for CGI scripts.
                                                             (line   33)
* excepthook() (於 sys 模組中):          sys --- System-specific parameters and functions.
                                                             (line  309)
* excepthook() (於 threading 模組中):    threading --- Thread-based parallelism.
                                                             (line   45)
* exception:                             Exceptions.         (line    6)
* exception <1>:                         The raise statement.
                                                             (line    6)
* Exception:                             Base classes.       (line   37)
* EXCEPTION (於 tkinter 模組中):         File Handlers.      (line   41)
* exception handler:                     Exceptions.         (line    6)
* exception() (asyncio.Future 的方法):   Future Object.      (line  116)
* exception() (asyncio.Task 的方法):     Task Object.        (line  133)
* exception() (concurrent.futures.Future 的方法): Future Objects.
                                                             (line   54)
* exception() (logging.Logger 的方法):   Logger Objects.     (line  244)
* exception() (於 logging 模組中):       Module-Level Functions.
                                                             (line  143)
* exception; chaining:                   The raise statement.
                                                             (line   30)
* exception; handler:                    The standard type hierarchy.
                                                             (line  759)
* exceptions; in CGI scripts:            cgitb --- Traceback manager for CGI scripts.
                                                             (line    8)
* exclusive; or:                         Binary bitwise operations.
                                                             (line   15)
* exc_info (doctest.UnexpectedException 的屬性): Debugging.  (line  225)
* exc_info (in module sys):              The standard type hierarchy.
                                                             (line  759)
* exc_info() (in module sys):            Exceptions<16>.     (line   45)
* exc_info() (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line  352)
* exc_msg (doctest.Example 的屬性):      Example Objects.    (line   31)
* exc_type (traceback.TracebackException 的屬性): TracebackException Objects.
                                                             (line   38)
* EXDEV (於 errno 模組中):               errno --- Standard errno system symbols.
                                                             (line   99)
* exec (2to3 fixer):                     Fixers.             (line   86)
* exec() (內建函式):                     內建函式.           (line  518)
* execfile (2to3 fixer):                 Fixers.             (line   90)
* execl() (於 os 模組中):                Process Management. (line   53)
* execle() (於 os 模組中):               Process Management. (line   53)
* execlp() (於 os 模組中):               Process Management. (line   53)
* execlpe() (於 os 模組中):              Process Management. (line   53)
* executable (in module sys):            Process-wide parameters.
                                                             (line  111)
* executable (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line  391)
* Executable Zip Files:                  zipapp --- Manage executable Python zip archives.
                                                             (line   10)
* executable_filename() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  450)
* execute() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  480)
* Execute() (msilib.View 的方法):        View Objects.       (line    6)
* execute() (sqlite3.Connection 的方法): Connection Objects. (line   52)
* execute() (sqlite3.Cursor 的方法):     Cursor Objects.     (line   11)
* execute() (於 distutils.util 模組中):  distutils util --- Miscellaneous other utility functions.
                                                             (line  109)
* executemany() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line   59)
* executemany() (sqlite3.Cursor 的方法): Cursor Objects.     (line   46)
* executescript() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line   66)
* executescript() (sqlite3.Cursor 的方法): Cursor Objects.   (line  100)
* execution model:                       Execution model.    (line    6)
* execution; frame:                      Structure of a program.
                                                             (line   16)
* execution; frame <1>:                  Class definitions.  (line    6)
* execution; stack:                      The standard type hierarchy.
                                                             (line  759)
* ExecutionLoader (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  440)
* Executor (concurrent.futures 中的類別): Executor Objects.  (line    6)
* execv() (於 os 模組中):                Process Management. (line   53)
* execve() (於 os 模組中):               Process Management. (line   53)
* execvp() (於 os 模組中):               Process Management. (line   53)
* execvpe() (於 os 模組中):              Process Management. (line   53)
* exec_module (C 函式):                  Multi-phase initialization.
                                                             (line  102)
* exec_module() (importlib.abc.InspectLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  428)
* exec_module() (importlib.abc.Loader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  177)
* exec_module() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  572)
* exec_module() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  318)
* exec_prefix:                           Python-related paths and files.
                                                             (line    7)
* exec_prefix <1>:                       Include Files.      (line   37)
* exec_prefix <2>:                       Include Files.      (line   48)
* EXEC_PREFIX (於 distutils.sysconfig 模組中): distutils sysconfig --- System configuration information.
                                                             (line   23)
* exec_prefix (於 sys 模組中):           sys --- System-specific parameters and functions.
                                                             (line  374)
* ExFileSelectBox (tkinter.tix 中的類別): File Selectors.    (line   34)
* EXFULL (於 errno 模組中):              errno --- Standard errno system symbols.
                                                             (line  243)
* exists() (pathlib.Path 的方法):        Methods<2>.         (line   58)
* exists() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line   95)
* exists() (zipfile.Path 的方法):        Path Objects.       (line   48)
* exists() (於 os.path 模組中):          os path --- Common pathname manipulations.
                                                             (line  113)
* exit (內建變數):                       Constants added by the site module.
                                                             (line   11)
* exit():                                行程（Process）控制.
                                                             (line   17)
* exit() (argparse.ArgumentParser 的方法): Exiting methods.  (line    6)
* exit() (於 sys 模組中):                sys --- System-specific parameters and functions.
                                                             (line  398)
* exit() (於 _thread 模組中):            _thread --- Low-level threading API.
                                                             (line   62)
* exitcode (multiprocessing.Process 的屬性): Process and exceptions.
                                                             (line  112)
* exitfunc (2to3 fixer):                 Fixers.             (line   96)
* exitonclick() (於 turtle 模組中):      Methods specific to Screen not inherited from TurtleScreen.
                                                             (line   10)
* ExitStack (contextlib 中的類別):       Utilities.          (line  342)
* exp() (decimal.Context 的方法):        Context objects.    (line  284)
* exp() (decimal.Decimal 的方法):        Decimal objects.    (line  231)
* exp() (於 cmath 模組中):               Power and logarithmic functions<2>.
                                                             (line    6)
* exp() (於 math 模組中):                Power and logarithmic functions.
                                                             (line    6)
* expand() (re.Match 的方法):            Match Objects.      (line   17)
* ExpandEnvironmentStrings() (於 winreg 模組中): Functions<11>.
                                                             (line  233)
* expandNode() (xml.dom.pulldom.DOMEventStream 的方法): DOMEventStream Objects.
                                                             (line   21)
* expandtabs() (bytearray 的方法):       Bytes and Bytearray Operations.
                                                             (line  413)
* expandtabs() (bytes 的方法):           Bytes and Bytearray Operations.
                                                             (line  413)
* expandtabs() (str 的方法):             String Methods<2>.  (line   81)
* expanduser() (pathlib.Path 的方法):    Methods<2>.         (line   75)
* expanduser() (於 os.path 模組中):      os path --- Common pathname manipulations.
                                                             (line  134)
* expandvars() (於 os.path 模組中):      os path --- Common pathname manipulations.
                                                             (line  157)
* expand_tabs (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  156)
* Expat:                                 xml parsers expat --- Fast XML parsing using Expat.
                                                             (line   12)
* ExpatError:                            xml parsers expat --- Fast XML parsing using Expat.
                                                             (line   25)
* expect() (telnetlib.Telnet 的方法):    Telnet Objects.     (line  121)
* expected (asyncio.IncompleteReadError 的屬性): Exceptions<8>.
                                                             (line   50)
* expectedFailure() (於 unittest 模組中): Skipping tests and expected failures.
                                                             (line   98)
* expectedFailures (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  256)
* expires (http.cookiejar.Cookie 的屬性): Cookie Objects<2>. (line   49)
* exploded (ipaddress.IPv4Address 的屬性): Address objects.  (line   54)
* exploded (ipaddress.IPv4Network 的屬性): Network objects.  (line  109)
* exploded (ipaddress.IPv6Address 的屬性): Address objects.  (line  155)
* exploded (ipaddress.IPv6Network 的屬性): Network objects.  (line  321)
* expm1() (於 math 模組中):              Power and logarithmic functions.
                                                             (line   12)
* expovariate() (於 random 模組中):      Real-valued distributions.
                                                             (line   38)
* expr() (於 parser 模組中):             Creating ST Objects.
                                                             (line   10)
* expression:                            Expressions.        (line    6)
* expression <1>:                        Glossary.           (line  397)
* 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)
* expunge() (imaplib.IMAP4 的方法):      IMAP4 Objects.      (line   93)
* extend() (array.array 的方法):         array --- 高效率的數值型態陣列.
                                                             (line  133)
* extend() (collections.deque 的方法):   deque objects.      (line   59)
* extend() (sequence method):            Mutable Sequence Types.
                                                             (line   16)
* extend() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line   93)
* ExtendedContext (decimal 中的類別):    Context objects.    (line   58)
* ExtendedInterpolation (configparser 中的類別): Interpolation of values.
                                                             (line   40)
* EXTENDED_ARG (opcode):                 Python Bytecode Instructions.
                                                             (line  866)
* extendleft() (collections.deque 的方法): deque objects.    (line   64)
* extend_path() (於 pkgutil 模組中):     pkgutil --- Package extension utility.
                                                             (line   19)
* Extension (distutils.core 中的類別):   distutils core --- Core Distutils functionality.
                                                             (line  176)
* extension module:                      Glossary.           (line  408)
* extension; module:                     The standard type hierarchy.
                                                             (line    6)
* ExtensionFileLoader (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  292)
* extensions_map (http.server.SimpleHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  348)
* EXTENSION_SUFFIXES (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   47)
* External Data Representation:          Data stream format. (line    6)
* External Data Representation <1>:      xdrlib --- Encode and decode XDR data.
                                                             (line    8)
* ExternalClashError:                    Exceptions<12>.     (line   25)
* ExternalEntityParserCreate() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line   44)
* ExternalEntityRefHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  333)
* external_attr (zipfile.ZipInfo 的屬性): ZipInfo Objects.   (line  127)
* extra (zipfile.ZipInfo 的屬性):        ZipInfo Objects.    (line   93)
* extract() (tarfile.TarFile 的方法):    TarFile Objects.    (line  161)
* extract() (traceback.StackSummary 的類別成員): StackSummary Objects.
                                                             (line   13)
* extract() (zipfile.ZipFile 的方法):    ZipFile Objects.    (line  158)
* extractall() (tarfile.TarFile 的方法): TarFile Objects.    (line  135)
* extractall() (zipfile.ZipFile 的方法): ZipFile Objects.    (line  185)
* ExtractError:                          tarfile --- Read and write tar archive files.
                                                             (line  200)
* extractfile() (tarfile.TarFile 的方法): TarFile Objects.   (line  189)
* extract_cookies() (http.cookiejar.CookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line   30)
* extract_stack() (於 traceback 模組中): traceback --- Print or retrieve a stack traceback.
                                                             (line   96)
* extract_tb() (於 traceback 模組中):    traceback --- Print or retrieve a stack traceback.
                                                             (line   83)
* extract_version (zipfile.ZipInfo 的屬性): ZipInfo Objects. (line  107)
* extsep (於 os 模組中):                 Miscellaneous System Information.
                                                             (line  109)
* EX_CANTCREAT (於 os 模組中):           Process Management. (line  202)
* EX_CONFIG (於 os 模組中):              Process Management. (line  238)
* EX_DATAERR (於 os 模組中):             Process Management. (line  151)
* EX_IOERR (於 os 模組中):               Process Management. (line  209)
* EX_NOHOST (於 os 模組中):              Process Management. (line  170)
* EX_NOINPUT (於 os 模組中):             Process Management. (line  157)
* EX_NOPERM (於 os 模組中):              Process Management. (line  231)
* EX_NOTFOUND (於 os 模組中):            Process Management. (line  245)
* EX_NOUSER (於 os 模組中):              Process Management. (line  164)
* EX_OK (於 os 模組中):                  Process Management. (line  138)
* EX_OSERR (於 os 模組中):               Process Management. (line  188)
* EX_OSFILE (於 os 模組中):              Process Management. (line  195)
* EX_PROTOCOL (於 os 模組中):            Process Management. (line  224)
* EX_SOFTWARE (於 os 模組中):            Process Management. (line  182)
* EX_TEMPFAIL (於 os 模組中):            Process Management. (line  216)
* EX_UNAVAILABLE (於 os 模組中):         Process Management. (line  176)
* EX_USAGE (於 os 模組中):               Process Management. (line  144)
* f"; formatted string literal:          String and Bytes literals.
                                                             (line   62)
* f’; formatted string literal:          String and Bytes literals.
                                                             (line   62)
* f-string:                              String literal concatenation.
                                                             (line   24)
* f-string <1>:                          Glossary.           (line  413)
* fabs() (於 math 模組中):               Number-theoretic and representation functions.
                                                             (line   36)
* factorial() (於 math 模組中):          Number-theoretic and representation functions.
                                                             (line   40)
* factory() (importlib.util.LazyLoader 的類別成員): importlib util -- Utility code for importers.
                                                             (line  255)
* fail() (unittest.TestCase 的方法):     Test cases.         (line  660)
* failfast (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  287)
* failureException (unittest.TestCase 的屬性): Test cases.   (line  665)
* failures (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  242)
* FAIL_FAST (於 doctest 模組中):         Option Flags.       (line  151)
* FakePath (test.support 中的類別):      test support --- Utilities for the Python test suite.
                                                             (line 1111)
* False:                                 The standard type hierarchy.
                                                             (line   93)
* false:                                 Truth Value Testing.
                                                             (line    6)
* False <1>:                             Truth Value Testing.
                                                             (line   23)
* False <2>:                             Boolean Values.     (line   15)
* False (Built-in object):               Truth Value Testing.
                                                             (line   15)
* False (內建變數):                      內建常數.           (line    8)
* family (socket.socket 的屬性):         Socket Objects.     (line  594)
* FancyGetopt (distutils.fancy_getopt 中的類別): distutils fancy_getopt --- Wrapper around the standard getopt module.
                                                             (line   36)
* FancyURLopener (urllib.request 中的類別): Legacy interface.
                                                             (line  147)
* fancy_getopt() (於 distutils.fancy_getopt 模組中): distutils fancy_getopt --- Wrapper around the standard getopt module.
                                                             (line   20)
* fast (pickle.Pickler 的屬性):          Module Interface.   (line  214)
* FastChildWatcher (asyncio 中的類別):   Process Watchers.   (line  132)
* fatalError() (xml.sax.handler.ErrorHandler 的方法): ErrorHandler Objects.
                                                             (line   24)
* Fault (xmlrpc.client 中的類別):        Fault Objects.      (line    6)
* faultCode (xmlrpc.client.Fault 的屬性): Fault Objects.     (line   11)
* faulthandler (模組):                   faulthandler --- Dump the Python traceback.
                                                             (line    6)
* faultString (xmlrpc.client.Fault 的屬性): Fault Objects.   (line   15)
* fchdir() (於 os 模組中):               Files and Directories.
                                                             (line  267)
* fchmod() (於 os 模組中):               File Descriptor Operations.
                                                             (line   96)
* fchown() (於 os 模組中):               File Descriptor Operations.
                                                             (line  107)
* FCICreate() (於 msilib 模組中):        msilib --- Read and write Microsoft Installer files.
                                                             (line   26)
* fcntl (模組):                          fcntl --- The fcntl and ioctl system calls.
                                                             (line    6)
* fcntl() (於 fcntl 模組中):             fcntl --- The fcntl and ioctl system calls.
                                                             (line   28)
* fd (selectors.SelectorKey 的屬性):     Classes<3>.         (line   40)
* fd() (於 turtle 模組中):               Turtle motion.      (line    6)
* fdatasync() (於 os 模組中):            File Descriptor Operations.
                                                             (line  119)
* fdopen() (於 os 模組中):               File Object Creation.
                                                             (line    9)
* fd_count() (於 test.support 模組中):   test support --- Utilities for the Python test suite.
                                                             (line  242)
* Feature (msilib 中的類別):             Features<3>.        (line    6)
* feature_external_ges (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line   76)
* feature_external_pes (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line   83)
* feature_namespaces (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line   48)
* feature_namespace_prefixes (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line   55)
* feature_string_interning (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line   62)
* feature_validation (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line   69)
* feed() (email.parser.BytesFeedParser 的方法): FeedParser API.
                                                             (line   55)
* feed() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line    8)
* feed() (xml.etree.ElementTree.XMLParser 的方法): XMLParser Objects.
                                                             (line   27)
* feed() (xml.etree.ElementTree.XMLPullParser 的方法): XMLPullParser Objects.
                                                             (line   18)
* feed() (xml.sax.xmlreader.IncrementalParser 的方法): IncrementalParser Objects.
                                                             (line    9)
* FeedParser (email.parser 中的類別):    FeedParser API.     (line   70)
* fetch() (imaplib.IMAP4 的方法):        IMAP4 Objects.      (line   99)
* Fetch() (msilib.View 的方法):          View Objects.       (line   18)
* fetchall() (sqlite3.Cursor 的方法):    Cursor Objects.     (line  162)
* fetchmany() (sqlite3.Cursor 的方法):   Cursor Objects.     (line  142)
* fetchone() (sqlite3.Cursor 的方法):    Cursor Objects.     (line  137)
* fflags (select.kevent 的屬性):         Kevent Objects.     (line   90)
* Field (dataclasses 中的類別):          Module-level decorators classes and functions.
                                                             (line  241)
* field() (於 dataclasses 模組中):       Module-level decorators classes and functions.
                                                             (line  153)
* fieldnames (csv.csvreader 的屬性):     Reader Objects.     (line   30)
* fields (uuid.UUID 的屬性):             uuid --- UUID objects according to RFC 4122.
                                                             (line   94)
* fields() (於 dataclasses 模組中):      Module-level decorators classes and functions.
                                                             (line  261)
* field_size_limit() (於 csv 模組中):    Module Contents<3>. (line   95)
* file (pyclbr.Class 的屬性):            Class Objects<2>.   (line    9)
* file (pyclbr.Function 的屬性):         函式物件.           (line    9)
* file object:                           Glossary.           (line  419)
* file object; io module:                總覽.               (line    6)
* file object; open() built-in function: 內建函式.           (line 1021)
* file-like object:                      Glossary.           (line  435)
* file; byte-code:                       py_compile --- Compile Python source files.
                                                             (line    8)
* file; byte-code <1>:                   imp --- Access the import internals.
                                                             (line   19)
* file; copying:                         shutil --- High-level file operations.
                                                             (line    8)
* file; large files:                     Large File Support. (line    6)
* file; mime.types:                      mimetypes --- Map filenames to MIME types.
                                                             (line  123)
* file; modes:                           內建函式.           (line 1045)
* filecmp (模組):                        filecmp --- File and Directory Comparisons.
                                                             (line    6)
* fileConfig() (於 logging.config 模組中): Configuration functions.
                                                             (line   61)
* FileCookieJar (http.cookiejar 中的類別): http cookiejar --- Cookie handling for HTTP clients.
                                                             (line   56)
* FileEntry (tkinter.tix 中的類別):      File Selectors.     (line   50)
* FileExistsError:                       OS exceptions.      (line   61)
* FileFinder (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  152)
* FileHandler (logging 中的類別):        FileHandler.        (line   10)
* FileHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  415)
* FileInput (fileinput 中的類別):        fileinput --- Iterate over lines from multiple input streams.
                                                             (line  134)
* fileinput (模組):                      fileinput --- Iterate over lines from multiple input streams.
                                                             (line    6)
* FileIO (io 中的類別):                  Raw File I/O.       (line    6)
* filelineno() (於 fileinput 模組中):    fileinput --- Iterate over lines from multiple input streams.
                                                             (line   99)
* FileLoader (importlib.abc 中的類別):   importlib abc -- Abstract base classes related to import.
                                                             (line  459)
* filemode() (於 stat 模組中):           stat --- Interpreting stat results.
                                                             (line  121)
* filename (doctest.DocTest 的屬性):     DocTest Objects.    (line   36)
* filename (http.cookiejar.FileCookieJar 的屬性): CookieJar and FileCookieJar Objects.
                                                             (line  153)
* filename (OSError 的屬性):             Concrete exceptions.
                                                             (line  156)
* filename (SyntaxError 的屬性):         Concrete exceptions.
                                                             (line  256)
* filename (traceback.TracebackException 的屬性): TracebackException Objects.
                                                             (line   42)
* filename (tracemalloc.Frame 的屬性):   Frame.              (line   13)
* filename (zipfile.ZipFile 的屬性):     ZipFile Objects.    (line  296)
* filename (zipfile.ZipInfo 的屬性):     ZipInfo Objects.    (line   50)
* filename() (於 fileinput 模組中):      fileinput --- Iterate over lines from multiple input streams.
                                                             (line   81)
* filename2 (OSError 的屬性):            Concrete exceptions.
                                                             (line  156)
* filenames; pathname expansion:         glob --- Unix style pathname pattern expansion.
                                                             (line    8)
* filenames; wildcard expansion:         fnmatch --- Unix filename pattern matching.
                                                             (line    8)
* filename_only (於 tabnanny 模組中):    tabnanny --- Detection of ambiguous indentation.
                                                             (line   31)
* filename_pattern (tracemalloc.Filter 的屬性): Filter.      (line   53)
* fileno() (http.client.HTTPResponse 的方法): HTTPResponse Objects.
                                                             (line   36)
* fileno() (io.IOBase 的方法):           I/O Base Classes.   (line   63)
* fileno() (multiprocessing.connection.Connection 的方法): Connection Objects<2>.
                                                             (line   31)
* fileno() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line   28)
* fileno() (ossaudiodev.oss_mixer_device 的方法): Mixer Device Objects.
                                                             (line   14)
* 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 Objects.     (line  110)
* fileno() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line   14)
* fileno() (telnetlib.Telnet 的方法):    Telnet Objects.     (line   97)
* fileno() (於 fileinput 模組中):        fileinput --- Iterate over lines from multiple input streams.
                                                             (line   86)
* FileNotFoundError:                     OS exceptions.      (line   66)
* fileobj (selectors.SelectorKey 的屬性): Classes<3>.        (line   36)
* FileSelectBox (tkinter.tix 中的類別):  File Selectors.     (line   42)
* FileType (argparse 中的類別):          FileType objects.   (line    6)
* FileWrapper (wsgiref.util 中的類別):   wsgiref util -- WSGI environment utilities.
                                                             (line  114)
* FILE_ATTRIBUTE_ARCHIVE (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_COMPRESSED (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_DEVICE (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_DIRECTORY (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_ENCRYPTED (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_HIDDEN (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_INTEGRITY_STREAM (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_NORMAL (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_NOT_CONTENT_INDEXED (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_NO_SCRUB_DATA (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_OFFLINE (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_READONLY (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_REPARSE_POINT (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_SPARSE_FILE (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_SYSTEM (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_TEMPORARY (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* FILE_ATTRIBUTE_VIRTUAL (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  394)
* file_created() (內建函式):             The Postinstallation script.
                                                             (line   23)
* file_dispatcher (asyncore 中的類別):   asyncore --- Asynchronous socket handler.
                                                             (line  255)
* file_open() (urllib.request.FileHandler 的方法): FileHandler Objects.
                                                             (line    6)
* file_size (zipfile.ZipInfo 的屬性):    ZipInfo Objects.    (line  143)
* file_wrapper (asyncore 中的類別):      asyncore --- Asynchronous socket handler.
                                                             (line  265)
* fill() (textwrap.TextWrapper 的方法):  textwrap --- Text wrapping and filling.
                                                             (line  285)
* fill() (於 textwrap 模組中):           textwrap --- Text wrapping and filling.
                                                             (line   29)
* fillcolor() (於 turtle 模組中):        Color control.      (line   58)
* filling() (於 turtle 模組中):          Filling.            (line    6)
* filter (2to3 fixer):                   Fixers.             (line  101)
* Filter (logging 中的類別):             Filter Objects.     (line   13)
* filter (select.kevent 的屬性):         Kevent Objects.     (line   15)
* Filter (tracemalloc 中的類別):         Filter.             (line    6)
* filter() (logging.Filter 的方法):      Filter Objects.     (line   20)
* filter() (logging.Handler 的方法):     Handler Objects.    (line   60)
* filter() (logging.Logger 的方法):      Logger Objects.     (line  259)
* filter() (內建函式):                   內建函式.           (line  564)
* filter() (於 curses 模組中):           Functions<3>.       (line  121)
* filter() (於 fnmatch 模組中):          fnmatch --- Unix filename pattern matching.
                                                             (line   65)
* filterfalse() (於 itertools 模組中):   Itertool functions. (line  284)
* filterwarnings() (於 warnings 模組中): Available Functions.
                                                             (line   76)
* FILTER_DIR (於 unittest.mock 模組中):  FILTER_DIR.         (line    6)
* filter_traces() (tracemalloc.Snapshot 的方法): Snapshot.   (line   35)
* Final (於 typing 模組中):              Classes functions and decorators.
                                                             (line  929)
* final() (於 typing 模組中):            Classes functions and decorators.
                                                             (line  689)
* finalization, of objects:              Finalization and De-allocation.
                                                             (line    6)
* finalize (weakref 中的類別):           weakref --- Weak references.
                                                             (line  224)
* finalizer:                             Basic customization.
                                                             (line   56)
* finalize_options() (distutils.cmd.Command 的方法): Creating a new Distutils command.
                                                             (line   30)
* find() (bytearray 的方法):             Bytes and Bytearray Operations.
                                                             (line   78)
* find() (bytes 的方法):                 Bytes and Bytearray Operations.
                                                             (line   78)
* find() (doctest.DocTestFinder 的方法): DocTestFinder objects.
                                                             (line   32)
* find() (mmap.mmap 的方法):             mmap --- Memory-mapped file support.
                                                             (line  177)
* find() (str 的方法):                   String Methods<2>.  (line  102)
* find() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  101)
* find() (xml.etree.ElementTree.ElementTree 的方法): ElementTree Objects.
                                                             (line   21)
* find() (於 gettext 模組中):            Class-based API.    (line   14)
* findall() (re.Pattern 的方法):         Regular Expression Objects.
                                                             (line   79)
* findall() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  110)
* findall() (xml.etree.ElementTree.ElementTree 的方法): ElementTree Objects.
                                                             (line   26)
* findall() (於 re 模組中):              Module Contents.    (line  219)
* findCaller() (logging.Logger 的方法):  Logger Objects.     (line  276)
* finder:                                Finders and loaders.
                                                             (line    6)
* finder <1>:                            Glossary.           (line  439)
* Finder (importlib.abc 中的類別):       importlib abc -- Abstract base classes related to import.
                                                             (line   28)
* finder; find_spec:                     The meta path.      (line    6)
* findfactor() (於 audioop 模組中):      audioop --- Manipulate raw audio data.
                                                             (line   79)
* findfile() (於 test.support 模組中):   test support --- Utilities for the Python test suite.
                                                             (line  228)
* findfit() (於 audioop 模組中):         audioop --- Manipulate raw audio data.
                                                             (line   88)
* finditer() (re.Pattern 的方法):        Regular Expression Objects.
                                                             (line   85)
* finditer() (於 re 模組中):             Module Contents.    (line  231)
* findlabels() (於 dis 模組中):          Analysis functions. (line  136)
* findlinestarts() (於 dis 模組中):      Analysis functions. (line  125)
* findmatch() (於 mailcap 模組中):       mailcap --- Mailcap file handling.
                                                             (line   24)
* findmax() (於 audioop 模組中):         audioop --- Manipulate raw audio data.
                                                             (line   99)
* findtext() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  119)
* findtext() (xml.etree.ElementTree.ElementTree 的方法): ElementTree Objects.
                                                             (line   31)
* find_class() (pickle protocol):        Restricting Globals.
                                                             (line    6)
* find_class() (pickle.Unpickler 的方法): Module Interface.  (line  286)
* find_library() (於 ctypes.util 模組中): Utility functions. (line   89)
* find_library_file() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  203)
* find_loader() (importlib.abc.PathEntryFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  118)
* find_loader() (importlib.machinery.FileFinder 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  189)
* find_loader() (於 importlib 模組中):   Functions<10>.      (line   40)
* find_loader() (於 pkgutil 模組中):     pkgutil --- Package extension utility.
                                                             (line   77)
* find_longest_match() (difflib.SequenceMatcher 的方法): SequenceMatcher Objects.
                                                             (line   64)
* find_module() (imp.NullImporter 的方法): imp --- Access the import internals.
                                                             (line  353)
* find_module() (importlib.abc.Finder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line   35)
* find_module() (importlib.abc.MetaPathFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line   67)
* find_module() (importlib.abc.PathEntryFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  141)
* find_module() (importlib.machinery.PathFinder 的類別成員): importlib machinery -- Importers and path hooks.
                                                             (line  133)
* find_module() (zipimport.zipimporter 的方法): zipimporter Objects.
                                                             (line   19)
* find_module() (於 imp 模組中):         imp --- Access the import internals.
                                                             (line   41)
* find_msvcrt() (於 ctypes.util 模組中): Utility functions.  (line   98)
* find_spec() (importlib.abc.MetaPathFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line   52)
* find_spec() (importlib.abc.PathEntryFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  105)
* find_spec() (importlib.machinery.FileFinder 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  182)
* find_spec() (importlib.machinery.PathFinder 的類別成員): importlib machinery -- Importers and path hooks.
                                                             (line  111)
* find_spec() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   97)
* find_unused_port() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  887)
* find_user_password() (urllib.request.HTTPPasswordMgr 的方法): HTTPPasswordMgr Objects.
                                                             (line   16)
* find_user_password() (urllib.request.HTTPPasswordMgrWithPriorAuth 的方法): HTTPPasswordMgrWithPriorAuth Objects.
                                                             (line   19)
* finish() (socketserver.BaseRequestHandler 的方法): Request Handler Objects.
                                                             (line   35)
* finish_request() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line  125)
* firstChild (xml.dom.Node 的屬性):      Node Objects.       (line   54)
* firstkey() (dbm.gnu.gdbm 的方法):      dbm gnu --- GNU's reinterpretation of dbm.
                                                             (line   85)
* firstweekday() (於 calendar 模組中):   calendar --- General calendar-related functions.
                                                             (line  297)
* fix_missing_locations() (於 ast 模組中): ast Helpers.      (line   81)
* fix_sentence_endings (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  211)
* Flag (enum 中的類別):                  Module Contents<2>. (line   28)
* flags (re.Pattern 的屬性):             Regular Expression Objects.
                                                             (line  101)
* flags (select.kevent 的屬性):          Kevent Objects.     (line   52)
* flags (於 sys 模組中):                 sys --- System-specific parameters and functions.
                                                             (line  429)
* flag_bits (zipfile.ZipInfo 的屬性):    ZipInfo Objects.    (line  115)
* flash() (於 curses 模組中):            Functions<3>.       (line  132)
* flatten() (email.generator.BytesGenerator 的方法): email generator Generating MIME documents.
                                                             (line   80)
* flatten() (email.generator.Generator 的方法): email generator Generating MIME documents.
                                                             (line  175)
* flattening; objects:                   pickle --- Python object serialization.
                                                             (line    8)
* float (內建類別):                      內建函式.           (line  581)
* floating point literal:                Numeric literals.   (line    6)
* floating point; literals:              Numeric Types --- int float complex.
                                                             (line   19)
* floating point; number:                The standard type hierarchy.
                                                             (line  107)
* FloatingPointError:                    Concrete exceptions.
                                                             (line   26)
* FloatOperation (decimal 中的類別):     Signals.            (line  100)
* float_info (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line  498)
* float_repr_style (於 sys 模組中):      sys --- System-specific parameters and functions.
                                                             (line  577)
* flock() (於 fcntl 模組中):             fcntl --- The fcntl and ioctl system calls.
                                                             (line  108)
* floor division:                        Glossary.           (line  450)
* floor() (in module math):              Numeric Types --- int float complex.
                                                             (line  104)
* floor() (於 math 模組中):              Number-theoretic and representation functions.
                                                             (line   45)
* floordiv() (於 operator 模組中):       operator --- Standard operators as functions.
                                                             (line   88)
* flush() (bz2.BZ2Compressor 的方法):    Incremental de compression.
                                                             (line   25)
* flush() (formatter.writer 的方法):     The Writer Interface.
                                                             (line   13)
* flush() (io.BufferedWriter 的方法):    Buffered Streams.   (line  121)
* flush() (io.IOBase 的方法):            I/O Base Classes.   (line   69)
* flush() (logging.Handler 的方法):      Handler Objects.    (line   68)
* flush() (logging.handlers.BufferingHandler 的方法): MemoryHandler.
                                                             (line   30)
* flush() (logging.handlers.MemoryHandler 的方法): MemoryHandler.
                                                             (line   60)
* flush() (logging.StreamHandler 的方法): StreamHandler.     (line   25)
* flush() (lzma.LZMACompressor 的方法):  Compressing and decompressing data in memory.
                                                             (line   91)
* flush() (mailbox.Mailbox 的方法):      Mailbox objects.    (line  242)
* flush() (mailbox.Maildir 的方法):      Maildir.            (line  102)
* flush() (mailbox.MH 的方法):           MH.                 (line   99)
* flush() (mmap.mmap 的方法):            mmap --- Memory-mapped file support.
                                                             (line  187)
* flush() (zlib.Compress 的方法):        zlib --- Compression compatible with gzip.
                                                             (line  203)
* flush() (zlib.Decompress 的方法):      zlib --- Compression compatible with gzip.
                                                             (line  274)
* flushinp() (於 curses 模組中):         Functions<3>.       (line  139)
* FlushKey() (於 winreg 模組中):         Functions<11>.      (line  244)
* flush_headers() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  274)
* flush_softspace() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line   83)
* fma() (decimal.Context 的方法):        Context objects.    (line  288)
* fma() (decimal.Decimal 的方法):        Decimal objects.    (line  269)
* fmean() (於 statistics 模組中):        函式細節.           (line   50)
* fmod() (於 math 模組中):               Number-theoretic and representation functions.
                                                             (line   51)
* FMT_BINARY (於 plistlib 模組中):       plistlib --- Generate and parse Mac OS X plist files.
                                                             (line  198)
* FMT_XML (於 plistlib 模組中):          plistlib --- Generate and parse Mac OS X plist files.
                                                             (line  192)
* fnmatch (模組):                        fnmatch --- Unix filename pattern matching.
                                                             (line    6)
* fnmatch() (於 fnmatch 模組中):         fnmatch --- Unix filename pattern matching.
                                                             (line   40)
* fnmatchcase() (於 fnmatch 模組中):     fnmatch --- Unix filename pattern matching.
                                                             (line   59)
* focus() (tkinter.ttk.Treeview 的方法): ttk Treeview.       (line   99)
* fold (datetime.datetime 的屬性):       datetime Objects.   (line  298)
* fold (datetime.time 的屬性):           time Objects.       (line   71)
* fold() (email.headerregistry.BaseHeader 的方法): email headerregistry Custom Header Objects.
                                                             (line   72)
* fold() (email.policy.Compat32 的方法): email policy Policy Objects.
                                                             (line  584)
* fold() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  450)
* fold() (email.policy.Policy 的方法):   email policy Policy Objects.
                                                             (line  319)
* fold_binary() (email.policy.Compat32 的方法): email policy Policy Objects.
                                                             (line  592)
* fold_binary() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  470)
* fold_binary() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  334)
* for; in comprehensions:                Displays for lists sets and dictionaries.
                                                             (line   14)
* forget() (tkinter.ttk.Notebook 的方法): ttk Notebook.      (line   18)
* forget() (於 test.support 模組中):     test support --- Utilities for the Python test suite.
                                                             (line  162)
* fork() (於 os 模組中):                 Process Management. (line  251)
* fork() (於 pty 模組中):                pty --- Pseudo-terminal utilities.
                                                             (line   20)
* ForkingMixIn (socketserver 中的類別):  Server Creation Notes.
                                                             (line   28)
* ForkingTCPServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   62)
* ForkingUDPServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   62)
* forkpty() (於 os 模組中):              Process Management. (line  270)
* Form (tkinter.tix 中的類別):           Form Geometry Manager.
                                                             (line    9)
* format (memoryview 的屬性):            Memory Views.       (line  414)
* format (multiprocessing.shared_memory.ShareableList 的屬性): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line  273)
* format (struct.Struct 的屬性):         Classes<2>.         (line   55)
* format() (built-in function); __str__() (object method): Basic customization.
                                                             (line  129)
* format() (logging.Formatter 的方法):   Formatter Objects.  (line   48)
* format() (logging.Handler 的方法):     Handler Objects.    (line  102)
* format() (pprint.PrettyPrinter 的方法): PrettyPrinter Objects.
                                                             (line   40)
* format() (str 的方法):                 String Methods<2>.  (line  116)
* format() (string.Formatter 的方法):    Custom String Formatting.
                                                             (line   17)
* format() (traceback.StackSummary 的方法): StackSummary Objects.
                                                             (line   36)
* format() (traceback.TracebackException 的方法): TracebackException Objects.
                                                             (line   73)
* format() (tracemalloc.Traceback 的方法): Traceback.        (line   25)
* format() (內建函式):                   內建函式.           (line  642)
* format() (於 locale 模組中):           locale --- Internationalization services.
                                                             (line  407)
* formataddr() (於 email.utils 模組中):  email utils Miscellaneous utilities.
                                                             (line   67)
* formatargspec() (於 inspect 模組中):   Classes and functions<2>.
                                                             (line   91)
* formatargvalues() (於 inspect 模組中): Classes and functions<2>.
                                                             (line  120)
* formatdate() (於 email.utils 模組中):  email utils Miscellaneous utilities.
                                                             (line  139)
* FormatError:                           Exceptions<12>.     (line   32)
* FormatError() (於 ctypes 模組中):      Utility functions.  (line  108)
* formatException() (logging.Formatter 的方法): Formatter Objects.
                                                             (line  109)
* formatmonth() (calendar.HTMLCalendar 的方法): calendar --- General calendar-related functions.
                                                             (line  169)
* formatmonth() (calendar.TextCalendar 的方法): calendar --- General calendar-related functions.
                                                             (line  134)
* formatStack() (logging.Formatter 的方法): Formatter Objects.
                                                             (line  117)
* formatted string literal:              String literal concatenation.
                                                             (line   24)
* Formatter (logging 中的類別):          Formatter Objects.  (line   26)
* Formatter (string 中的類別):           Custom String Formatting.
                                                             (line   13)
* formatter (模組):                      formatter --- Generic output formatting.
                                                             (line    6)
* formatTime() (logging.Formatter 的方法): Formatter Objects.
                                                             (line   72)
* formatting, string (%):                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   67)
* formatyear() (calendar.HTMLCalendar 的方法): calendar --- General calendar-related functions.
                                                             (line  175)
* formatyear() (calendar.TextCalendar 的方法): calendar --- General calendar-related functions.
                                                             (line  148)
* formatyearpage() (calendar.HTMLCalendar 的方法): calendar --- General calendar-related functions.
                                                             (line  180)
* format_datetime() (於 email.utils 模組中): email utils Miscellaneous utilities.
                                                             (line  160)
* format_exc() (於 traceback 模組中):    traceback --- Print or retrieve a stack traceback.
                                                             (line  137)
* format_exception() (於 traceback 模組中): traceback --- Print or retrieve a stack traceback.
                                                             (line  124)
* format_exception_only() (traceback.TracebackException 的方法): TracebackException Objects.
                                                             (line   88)
* format_exception_only() (於 traceback 模組中): traceback --- Print or retrieve a stack traceback.
                                                             (line  113)
* format_field() (string.Formatter 的方法): Custom String Formatting.
                                                             (line  102)
* format_help() (argparse.ArgumentParser 的方法): Printing help.
                                                             (line   30)
* format_list() (於 traceback 模組中):   traceback --- Print or retrieve a stack traceback.
                                                             (line  103)
* format_map() (str 的方法):             String Methods<2>.  (line  146)
* format_stack() (於 traceback 模組中):  traceback --- Print or retrieve a stack traceback.
                                                             (line  146)
* format_stack_entry() (bdb.Bdb 的方法): bdb --- Debugger framework.
                                                             (line  344)
* format_string() (於 locale 模組中):    locale --- Internationalization services.
                                                             (line  390)
* format_tb() (於 traceback 模組中):     traceback --- Print or retrieve a stack traceback.
                                                             (line  142)
* format_usage() (argparse.ArgumentParser 的方法): Printing help.
                                                             (line   25)
* FORMAT_VALUE (opcode):                 Python Bytecode Instructions.
                                                             (line  874)
* Fortran contiguous:                    shape strides suboffsets.
                                                             (line   25)
* Fortran contiguous <1>:                Glossary.           (line  273)
* forward() (於 turtle 模組中):          Turtle motion.      (line    6)
* ForwardRef (typing 中的類別):          Classes functions and decorators.
                                                             (line  595)
* FOR_ITER (opcode):                     Python Bytecode Instructions.
                                                             (line  685)
* found_terminator() (asynchat.async_chat 的方法): asynchat --- Asynchronous socket command/response handler.
                                                             (line   89)
* fpathconf() (於 os 模組中):            File Descriptor Operations.
                                                             (line  128)
* fqdn (smtpd.SMTPChannel 的屬性):       SMTPChannel Objects.
                                                             (line   90)
* Fraction (fractions 中的類別):         fractions --- Rational numbers.
                                                             (line   16)
* fractions (模組):                      fractions --- Rational numbers.
                                                             (line    6)
* frame (tkinter.scrolledtext.ScrolledText 的屬性): tkinter scrolledtext --- Scrolled Text Widget.
                                                             (line   24)
* Frame (tracemalloc 中的類別):          Frame.              (line    6)
* FrameSummary (traceback 中的類別):     FrameSummary Objects.
                                                             (line   11)
* FrameType (於 types 模組中):           Standard Interpreter Types.
                                                             (line  190)
* free():                                總覽<2>.            (line   33)
* free; variable:                        Binding of names.   (line   26)
* freefunc (C 型態):                     Slot Type typedefs. (line   37)
* freeze utility:                        匯入模組<2>.        (line  259)
* freeze() (於 gc 模組中):               gc --- Garbage Collector interface.
                                                             (line  182)
* freeze_support() (於 multiprocessing 模組中): Miscellaneous<3>.
                                                             (line   43)
* frexp() (於 math 模組中):              Number-theoretic and representation functions.
                                                             (line   67)
* from; import statement:                Binding of names.   (line    9)
* from; import statement <1>:            The import statement.
                                                             (line   51)
* from; yield from expression:           Yield expressions.  (line   62)
* frombuf() (tarfile.TarInfo 的類別成員): TarInfo Objects.   (line   19)
* frombytes() (array.array 的方法):      array --- 高效率的數值型態陣列.
                                                             (line  140)
* fromfd() (select.epoll 的方法):        Edge and Level Trigger Polling epoll Objects.
                                                             (line   77)
* fromfd() (select.kqueue 的方法):       Kqueue Objects.     (line   18)
* fromfd() (於 socket 模組中):           Creating sockets.   (line  144)
* fromfile() (array.array 的方法):       array --- 高效率的數值型態陣列.
                                                             (line  148)
* fromhex() (bytearray 的類別成員):      Bytearray Objects.  (line   36)
* fromhex() (bytes 的類別成員):          Bytes Objects.      (line   62)
* fromhex() (float 的類別成員):          Additional Methods on Float.
                                                             (line   39)
* fromisocalendar() (datetime.date 的類別成員): date Objects.
                                                             (line   77)
* fromisocalendar() (datetime.datetime 的類別成員): datetime Objects.
                                                             (line  222)
* fromisoformat() (datetime.date 的類別成員): date Objects.  (line   63)
* fromisoformat() (datetime.datetime 的類別成員): datetime Objects.
                                                             (line  187)
* fromisoformat() (datetime.time 的類別成員): time Objects.  (line  113)
* fromkeys() (collections.Counter 的方法): Counter 物件.     (line  103)
* fromkeys() (dict 的類別成員):          Mapping Types --- dict.
                                                             (line  150)
* fromlist() (array.array 的方法):       array --- 高效率的數值型態陣列.
                                                             (line  155)
* fromordinal() (datetime.date 的類別成員): date Objects.    (line   54)
* fromordinal() (datetime.datetime 的類別成員): datetime Objects.
                                                             (line  161)
* fromshare() (於 socket 模組中):        Creating sockets.   (line  161)
* fromstring() (array.array 的方法):     array --- 高效率的數值型態陣列.
                                                             (line  160)
* fromstring() (於 xml.etree.ElementTree 模組中): Functions<6>.
                                                             (line   99)
* fromstringlist() (於 xml.etree.ElementTree 模組中): Functions<6>.
                                                             (line  107)
* fromtarfile() (tarfile.TarInfo 的類別成員): TarInfo Objects.
                                                             (line   26)
* fromtimestamp() (datetime.date 的類別成員): date Objects.  (line   35)
* fromtimestamp() (datetime.datetime 的類別成員): datetime Objects.
                                                             (line   93)
* fromunicode() (array.array 的方法):    array --- 高效率的數值型態陣列.
                                                             (line  166)
* fromutc() (datetime.timezone 的方法):  timezone Objects.   (line   61)
* fromutc() (datetime.tzinfo 的方法):    tzinfo Objects.     (line  163)
* from_address() (ctypes._CData 的方法): Data types.         (line   42)
* from_buffer() (ctypes._CData 的方法):  Data types.         (line   19)
* from_buffer_copy() (ctypes._CData 的方法): Data types.     (line   31)
* from_bytes() (int 的類別成員):         Additional Methods on Integer Types.
                                                             (line   67)
* from_callable() (inspect.Signature 的類別成員): Introspecting callables with the Signature object.
                                                             (line  126)
* from_decimal() (fractions.Fraction 的方法): fractions --- Rational numbers.
                                                             (line  115)
* from_exception() (traceback.TracebackException 的類別成員): TracebackException Objects.
                                                             (line   63)
* from_file() (zipfile.ZipInfo 的類別成員): ZipInfo Objects. (line   14)
* from_float() (decimal.Decimal 的方法): Decimal objects.    (line  242)
* from_float() (fractions.Fraction 的方法): fractions --- Rational numbers.
                                                             (line  104)
* from_iterable() (itertools.chain 的類別成員): Itertool functions.
                                                             (line   98)
* from_list() (traceback.StackSummary 的類別成員): StackSummary Objects.
                                                             (line   29)
* from_param() (ctypes._CData 的方法):   Data types.         (line   51)
* from_samples() (statistics.NormalDist 的類別成員): NormalDist objects.
                                                             (line   45)
* from_traceback() (dis.Bytecode 的類別成員): Bytecode analysis.
                                                             (line   33)
* FrozenImporter (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line   77)
* FrozenInstanceError:                   Exceptions<15>.     (line    6)
* FrozenSet (typing 中的類別):           Classes functions and decorators.
                                                             (line  278)
* frozenset (內建類別):                  Set Types --- set frozenset.
                                                             (line   33)
* fsdecode() (於 os 模組中):             Process Parameters. (line   88)
* fsencode() (於 os 模組中):             Process Parameters. (line   75)
* fspath() (於 os 模組中):               Process Parameters. (line  101)
* fstat() (於 os 模組中):                File Descriptor Operations.
                                                             (line  150)
* fstatvfs() (於 os 模組中):             File Descriptor Operations.
                                                             (line  162)
* fstring:                               String literal concatenation.
                                                             (line   24)
* fsum() (於 math 模組中):               Number-theoretic and representation functions.
                                                             (line   75)
* fsync() (於 os 模組中):                File Descriptor Operations.
                                                             (line  170)
* fs_is_case_insensitive() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  924)
* FS_NONASCII (於 test.support 模組中):  test support --- Utilities for the Python test suite.
                                                             (line   48)
* FTP:                                   urllib request Restrictions.
                                                             (line   37)
* FTP (ftplib 中的類別):                 ftplib --- FTP protocol client.
                                                             (line   39)
* FTP; ftplib (standard module):         ftplib --- FTP protocol client.
                                                             (line    8)
* FTP; protocol:                         urllib request Restrictions.
                                                             (line    6)
* FTP; protocol <1>:                     ftplib --- FTP protocol client.
                                                             (line    8)
* FTPHandler (urllib.request 中的類別):  urllib request --- Extensible library for opening URLs.
                                                             (line  425)
* ftplib (模組):                         ftplib --- FTP protocol client.
                                                             (line    6)
* ftp_open() (urllib.request.FTPHandler 的方法): FTPHandler Objects.
                                                             (line    6)
* FTP_TLS (ftplib 中的類別):             ftplib --- FTP protocol client.
                                                             (line   71)
* ftruncate() (於 os 模組中):            File Descriptor Operations.
                                                             (line  183)
* Full:                                  queue --- A synchronized queue class.
                                                             (line   88)
* full() (asyncio.Queue 的方法):         Queue.              (line   32)
* full() (multiprocessing.Queue 的方法): Pipes and Queues.   (line  114)
* full() (queue.Queue 的方法):           Queue Objects.      (line   22)
* fullmatch() (re.Pattern 的方法):       Regular Expression Objects.
                                                             (line   56)
* fullmatch() (於 re 模組中):            Module Contents.    (line  167)
* full_url (urllib.request.Request 的屬性): Request Objects. (line   11)
* func (functools.partial 的屬性):       partial Objects.    (line    9)
* funcattrs (2to3 fixer):                Fixers.             (line  105)
* function:                              Glossary.           (line  458)
* Function (symtable 中的類別):          Examining Symbol Tables.
                                                             (line   66)
* function annotation:                   Glossary.           (line  466)
* function; annotations:                 Function Annotations.
                                                             (line    6)
* function; annotations <1>:             Function definitions.
                                                             (line   94)
* function; argument:                    The standard type hierarchy.
                                                             (line  291)
* function; call:                        The standard type hierarchy.
                                                             (line  291)
* function; call <1>:                    Calls.              (line  123)
* function; call <2>:                    Calls.              (line  132)
* function; definition:                  The return statement.
                                                             (line    6)
* function; definition <1>:              Function definitions.
                                                             (line    6)
* function; generator:                   The yield statement.
                                                             (line    6)
* function; name:                        Function definitions.
                                                             (line    6)
* function; name <1>:                    Function definitions.
                                                             (line    6)
* FunctionTestCase (unittest 中的類別):  Test cases.         (line  891)
* FunctionType (於 types 模組中):        Standard Interpreter Types.
                                                             (line   19)
* functools (模組):                      functools --- Higher-order functions and operations on callable objects.
                                                             (line    6)
* funny_files (filecmp.dircmp 的屬性):   The dircmp class.   (line   95)
* future (2to3 fixer):                   Fixers.             (line  111)
* Future (asyncio 中的類別):             Future Object.      (line    6)
* Future (concurrent.futures 中的類別):  Future Objects.     (line   10)
* future; statement:                     Future statements.  (line    6)
* FutureWarning:                         Warnings.           (line   40)
* fwalk() (於 os 模組中):                Files and Directories.
                                                             (line 1576)
* f_back (frame attribute):              The standard type hierarchy.
                                                             (line  712)
* f_builtins (frame attribute):          The standard type hierarchy.
                                                             (line  712)
* f_code (frame attribute):              The standard type hierarchy.
                                                             (line  712)
* f_contiguous (memoryview 的屬性):      Memory Views.       (line  471)
* f_globals (frame attribute):           The standard type hierarchy.
                                                             (line  712)
* f_lasti (frame attribute):             The standard type hierarchy.
                                                             (line  712)
* f_lineno (frame attribute):            The standard type hierarchy.
                                                             (line  724)
* f_locals (frame attribute):            The standard type hierarchy.
                                                             (line  712)
* F_LOCK (於 os 模組中):                 File Descriptor Operations.
                                                             (line  228)
* F_OK (於 os 模組中):                   Files and Directories.
                                                             (line  106)
* F_TEST (於 os 模組中):                 File Descriptor Operations.
                                                             (line  228)
* F_TLOCK (於 os 模組中):                File Descriptor Operations.
                                                             (line  228)
* f_trace (frame attribute):             The standard type hierarchy.
                                                             (line  724)
* f_trace_lines (frame attribute):       The standard type hierarchy.
                                                             (line  724)
* f_trace_opcodes (frame attribute):     The standard type hierarchy.
                                                             (line  724)
* F_ULOCK (於 os 模組中):                File Descriptor Operations.
                                                             (line  228)
* G.722:                                 aifc --- Read and write AIFF and AIFC files.
                                                             (line  159)
* gaierror:                              Exceptions<10>.     (line   26)
* gamma() (於 math 模組中):              Special functions.  (line   29)
* gammavariate() (於 random 模組中):     Real-valued distributions.
                                                             (line   46)
* garbage (於 gc 模組中):                gc --- Garbage Collector interface.
                                                             (line  210)
* garbage collection:                    Objects values and types.
                                                             (line   37)
* garbage collection <1>:                Glossary.           (line  498)
* gather() (curses.textpad.Textbox 的方法): Textbox objects. (line  109)
* gather() (於 asyncio 模組中):          Running Tasks Concurrently.
                                                             (line    6)
* gauss() (於 random 模組中):            Real-valued distributions.
                                                             (line   57)
* gc (模組):                             gc --- Garbage Collector interface.
                                                             (line    6)
* gcd() (於 fractions 模組中):           fractions --- Rational numbers.
                                                             (line  173)
* gcd() (於 math 模組中):                Number-theoretic and representation functions.
                                                             (line   95)
* gc_collect() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  473)
* ge() (於 operator 模組中):             operator --- Standard operators as functions.
                                                             (line   24)
* generate_help() (distutils.fancy_getopt.FancyGetopt 的方法): distutils fancy_getopt --- Wrapper around the standard getopt module.
                                                             (line   68)
* generate_tokens() (於 tokenize 模組中): Tokenizing Input.  (line   38)
* generator:                             Glossary.           (line  507)
* generator <1>:                         Glossary.           (line  507)
* Generator (collections.abc 中的類別):  Collections Abstract Base Classes.
                                                             (line  150)
* Generator (email.generator 中的類別):  email generator Generating MIME documents.
                                                             (line  140)
* Generator (typing 中的類別):           Classes functions and decorators.
                                                             (line  390)
* generator expression:                  Glossary.           (line  529)
* generator expression <1>:              Glossary.           (line  529)
* generator iterator:                    Glossary.           (line  517)
* generator; expression:                 Generator expressions.
                                                             (line    6)
* generator; function:                   The standard type hierarchy.
                                                             (line  443)
* generator; function <1>:               Yield expressions.  (line    6)
* generator; function <2>:               The yield statement.
                                                             (line    6)
* generator; iterator:                   The standard type hierarchy.
                                                             (line  443)
* generator; iterator <1>:               The yield statement.
                                                             (line    6)
* GeneratorExit:                         Concrete exceptions.
                                                             (line   30)
* GeneratorType (於 types 模組中):       Standard Interpreter Types.
                                                             (line   31)
* Generic (typing 中的類別):             Classes functions and decorators.
                                                             (line   47)
* generic function:                      Glossary.           (line  538)
* generic; special; attribute:           The standard type hierarchy.
                                                             (line   13)
* generic_visit() (ast.NodeVisitor 的方法): ast Helpers.     (line  136)
* genops() (於 pickletools 模組中):      Programmatic Interface<2>.
                                                             (line   22)
* gen_lib_options() (於 distutils.ccompiler 模組中): distutils ccompiler --- CCompiler base class.
                                                             (line   14)
* gen_preprocess_options() (於 distutils.ccompiler 模組中): distutils ccompiler --- CCompiler base class.
                                                             (line   24)
* gen_uuid() (於 msilib 模組中):         msilib --- Read and write Microsoft Installer files.
                                                             (line  109)
* geometric_mean() (於 statistics 模組中): 函式細節.         (line   64)
* get() (asyncio.Queue 的方法):          Queue.              (line   40)
* get() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  187)
* get() (contextvars.Context 的方法):    Manual Context Management.
                                                             (line   85)
* get() (contextvars.ContextVar 的方法): Context Variables.  (line   30)
* get() (dict 的方法):                   Mapping Types --- dict.
                                                             (line  162)
* get() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  243)
* get() (email.message.Message 的方法):  email message Message Representing an email message using the compat32 API.
                                                             (line  353)
* get() (mailbox.Mailbox 的方法):        Mailbox objects.    (line  140)
* get() (multiprocessing.pool.AsyncResult 的方法): Process Pools.
                                                             (line  196)
* get() (multiprocessing.Queue 的方法):  Pipes and Queues.   (line  139)
* get() (multiprocessing.SimpleQueue 的方法): Pipes and Queues.
                                                             (line  212)
* get() (ossaudiodev.oss_mixer_device 的方法): Mixer Device Objects.
                                                             (line   59)
* get() (queue.Queue 的方法):            Queue Objects.      (line   44)
* get() (queue.SimpleQueue 的方法):      SimpleQueue Objects.
                                                             (line   40)
* get() (tkinter.ttk.Combobox 的方法):   ttk Combobox.       (line   15)
* get() (tkinter.ttk.Spinbox 的方法):    ttk Spinbox.        (line    8)
* get() (types.MappingProxyType 的方法): Standard Interpreter Types.
                                                             (line  249)
* get() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line   64)
* get() (於 webbrowser 模組中):          webbrowser --- Convenient Web-browser controller.
                                                             (line   77)
* getacl() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line  106)
* getaddresses() (於 email.utils 模組中): email utils Miscellaneous utilities.
                                                             (line   81)
* getaddrinfo() (asyncio.loop 的方法):   DNS.                (line    6)
* getaddrinfo() (於 socket 模組中):      Other functions<2>. (line   17)
* getallocatedblocks() (於 sys 模組中):  sys --- System-specific parameters and functions.
                                                             (line  589)
* getandroidapilevel() (於 sys 模組中):  sys --- System-specific parameters and functions.
                                                             (line  604)
* getannotation() (imaplib.IMAP4 的方法): IMAP4 Objects.     (line  111)
* getargspec() (於 inspect 模組中):      Classes and functions<2>.
                                                             (line   17)
* getargvalues() (於 inspect 模組中):    Classes and functions<2>.
                                                             (line   80)
* getatime() (於 os.path 模組中):        os path --- Common pathname manipulations.
                                                             (line  169)
* getattr() (內建函式):                  內建函式.           (line  675)
* getattrfunc (C 型態):                  Slot Type typedefs. (line   53)
* getAttribute() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   31)
* getAttributeNode() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   37)
* getAttributeNodeNS() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   47)
* getAttributeNS() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   41)
* getattrofunc (C 型態):                 Slot Type typedefs. (line   63)
* getattr_static() (於 inspect 模組中):  Fetching attributes statically.
                                                             (line   16)
* GetBase() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line   31)
* getbegyx() (curses.window 的方法):     Window Objects.     (line  222)
* getbkgd() (curses.window 的方法):      Window Objects.     (line  226)
* getblocking() (socket.socket 的方法):  Socket Objects.     (line  153)
* getboolean() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  221)
* getbuffer() (io.BytesIO 的方法):       Buffered Streams.   (line   21)
* getbufferproc (C 型態):                Slot Type typedefs. (line  105)
* getByteStream() (xml.sax.xmlreader.InputSource 的方法): InputSource Objects.
                                                             (line   48)
* getcallargs() (於 inspect 模組中):     Classes and functions<2>.
                                                             (line  139)
* getcanvas() (於 turtle 模組中):        Settings and special methods.
                                                             (line   54)
* getcapabilities() (nntplib.NNTP 的方法): Methods<3>.       (line   34)
* getcaps() (於 mailcap 模組中):         mailcap --- Mailcap file handling.
                                                             (line   62)
* getch() (curses.window 的方法):        Window Objects.     (line  231)
* getch() (於 msvcrt 模組中):            Console I/O.        (line   10)
* getCharacterStream() (xml.sax.xmlreader.InputSource 的方法): InputSource Objects.
                                                             (line   64)
* getche() (於 msvcrt 模組中):           Console I/O.        (line   25)
* getcheckinterval() (於 sys 模組中):    sys --- System-specific parameters and functions.
                                                             (line  612)
* getChild() (logging.Logger 的方法):    Logger Objects.     (line  106)
* getchildren() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  130)
* getclasstree() (於 inspect 模組中):    Classes and functions<2>.
                                                             (line    6)
* getclosurevars() (於 inspect 模組中):  Classes and functions<2>.
                                                             (line  169)
* GetColumnInfo() (msilib.View 的方法):  View Objects.       (line   12)
* getColumnNumber() (xml.sax.xmlreader.Locator 的方法): Locator Objects.
                                                             (line    8)
* getcomments() (於 inspect 模組中):     Retrieving source code.
                                                             (line   17)
* getcompname() (aifc.aifc 的方法):      aifc --- Read and write AIFF and AIFC files.
                                                             (line   72)
* getcompname() (sunau.AU_read 的方法):  AU_read Objects.    (line   35)
* getcompname() (wave.Wave_read 的方法): Wave_read Objects.  (line   35)
* getcomptype() (aifc.aifc 的方法):      aifc --- Read and write AIFF and AIFC files.
                                                             (line   66)
* getcomptype() (sunau.AU_read 的方法):  AU_read Objects.    (line   30)
* getcomptype() (wave.Wave_read 的方法): Wave_read Objects.  (line   31)
* getContentHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   21)
* getcontext() (於 decimal 模組中):      Context objects.    (line   14)
* getcoroutinelocals() (於 inspect 模組中): Current State of Generators and Coroutines.
                                                             (line   73)
* getcoroutinestate() (於 inspect 模組中): Current State of Generators and Coroutines.
                                                             (line   28)
* getctime() (於 os.path 模組中):        os path --- Common pathname manipulations.
                                                             (line  185)
* getcwd() (於 os 模組中):               Files and Directories.
                                                             (line  279)
* getcwdb() (於 os 模組中):              Files and Directories.
                                                             (line  283)
* getcwdu (2to3 fixer):                  Fixers.             (line  115)
* getdecoder() (於 codecs 模組中):       codecs --- Codec registry and base classes.
                                                             (line  107)
* getdefaultencoding() (於 sys 模組中):  sys --- System-specific parameters and functions.
                                                             (line  619)
* getdefaultlocale() (於 locale 模組中): locale --- Internationalization services.
                                                             (line  301)
* getdefaulttimeout() (於 socket 模組中): Other functions<2>.
                                                             (line  329)
* getdlopenflags() (於 sys 模組中):      sys --- System-specific parameters and functions.
                                                             (line  624)
* getdoc() (於 inspect 模組中):          Retrieving source code.
                                                             (line    6)
* getDOMImplementation() (於 xml.dom 模組中): Module Contents<4>.
                                                             (line   17)
* getDTDHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   30)
* getEffectiveLevel() (logging.Logger 的方法): Logger Objects.
                                                             (line   97)
* getegid() (於 os 模組中):              Process Parameters. (line  163)
* getElementsByTagName() (xml.dom.Document 的方法): Document Objects.
                                                             (line   61)
* getElementsByTagName() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   14)
* getElementsByTagNameNS() (xml.dom.Document 的方法): Document Objects.
                                                             (line   66)
* getElementsByTagNameNS() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   18)
* getencoder() (於 codecs 模組中):       codecs --- Codec registry and base classes.
                                                             (line   99)
* getEncoding() (xml.sax.xmlreader.InputSource 的方法): InputSource Objects.
                                                             (line   32)
* getEntityResolver() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   39)
* getenv() (於 os 模組中):               Process Parameters. (line  128)
* getenvb() (於 os 模組中):              Process Parameters. (line  140)
* getErrorHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   50)
* geteuid() (於 os 模組中):              Process Parameters. (line  171)
* getEvent() (xml.dom.pulldom.DOMEventStream 的方法): DOMEventStream Objects.
                                                             (line   11)
* getEventCategory() (logging.handlers.NTEventLogHandler 的方法): NTEventLogHandler.
                                                             (line   43)
* getEventType() (logging.handlers.NTEventLogHandler 的方法): NTEventLogHandler.
                                                             (line   49)
* getException() (xml.sax.SAXException 的方法): SAXException Objects.
                                                             (line   13)
* getFeature() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   69)
* GetFieldCount() (msilib.Record 的方法): Record Objects.    (line    6)
* getfile() (於 inspect 模組中):         Retrieving source code.
                                                             (line   26)
* getfilesystemencodeerrors() (於 sys 模組中): sys --- System-specific parameters and functions.
                                                             (line  669)
* getfilesystemencoding() (於 sys 模組中): sys --- System-specific parameters and functions.
                                                             (line  633)
* getfirst() (cgi.FieldStorage 的方法):  Higher Level Interface.
                                                             (line   56)
* getfloat() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  214)
* getfmts() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line   77)
* getfqdn() (於 socket 模組中):          Other functions<2>. (line   70)
* getframeinfo() (於 inspect 模組中):    The interpreter stack.
                                                             (line   46)
* getframerate() (aifc.aifc 的方法):     aifc --- Read and write AIFF and AIFC files.
                                                             (line   58)
* getframerate() (sunau.AU_read 的方法): AU_read Objects.    (line   22)
* getframerate() (wave.Wave_read 的方法): Wave_read Objects. (line   23)
* getfullargspec() (於 inspect 模組中):  Classes and functions<2>.
                                                             (line   36)
* getgeneratorlocals() (於 inspect 模組中): Current State of Generators and Coroutines.
                                                             (line   53)
* getgeneratorstate() (於 inspect 模組中): Current State of Generators and Coroutines.
                                                             (line   12)
* getgid() (於 os 模組中):               Process Parameters. (line  177)
* getgrall() (於 grp 模組中):            grp --- The group database.
                                                             (line   57)
* getgrgid() (於 grp 模組中):            grp --- The group database.
                                                             (line   42)
* getgrnam() (於 grp 模組中):            grp --- The group database.
                                                             (line   52)
* getgrouplist() (於 os 模組中):         Process Parameters. (line  183)
* getgroups() (於 os 模組中):            Process Parameters. (line  193)
* getheader() (http.client.HTTPResponse 的方法): HTTPResponse Objects.
                                                             (line   24)
* getheaders() (http.client.HTTPResponse 的方法): HTTPResponse Objects.
                                                             (line   32)
* gethostbyaddr() (in module socket):    Process Parameters. (line  471)
* gethostbyaddr() (於 socket 模組中):    Other functions<2>. (line  119)
* gethostbyname() (於 socket 模組中):    Other functions<2>. (line   80)
* gethostbyname_ex() (於 socket 模組中): Other functions<2>. (line   93)
* gethostname() (in module socket):      Process Parameters. (line  471)
* gethostname() (於 socket 模組中):      Other functions<2>. (line  108)
* getincrementaldecoder() (於 codecs 模組中): codecs --- Codec registry and base classes.
                                                             (line  123)
* getincrementalencoder() (於 codecs 模組中): codecs --- Codec registry and base classes.
                                                             (line  115)
* getinfo() (zipfile.ZipFile 的方法):    ZipFile Objects.    (line   91)
* getinnerframes() (於 inspect 模組中):  The interpreter stack.
                                                             (line   62)
* GetInputContext() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line   37)
* getint() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  207)
* GetInteger() (msilib.Record 的方法):   Record Objects.     (line   11)
* getitem() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  192)
* getiterator() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  135)
* getiterator() (xml.etree.ElementTree.ElementTree 的方法): ElementTree Objects.
                                                             (line   36)
* getiterfunc (C 型態):                  Slot Type typedefs. (line   95)
* getitimer() (於 signal 模組中):        Module contents<2>. (line  370)
* getkey() (curses.window 的方法):       Window Objects.     (line  246)
* GetLastError() (於 ctypes 模組中):     Utility functions.  (line  114)
* getLength() (xml.sax.xmlreader.Attributes 的方法): The Attributes Interface.
                                                             (line   11)
* getLevelName() (於 logging 模組中):    Module-Level Functions.
                                                             (line  203)
* getline() (於 linecache 模組中):       linecache --- Random access to text lines.
                                                             (line   23)
* getLineNumber() (xml.sax.xmlreader.Locator 的方法): Locator Objects.
                                                             (line   12)
* getlist() (cgi.FieldStorage 的方法):   Higher Level Interface.
                                                             (line   67)
* getloadavg() (於 os 模組中):           Miscellaneous System Information.
                                                             (line   48)
* getlocale() (於 locale 模組中):        locale --- Internationalization services.
                                                             (line  326)
* getLogger() (於 logging 模組中):       Module-Level Functions.
                                                             (line    9)
* getLoggerClass() (於 logging 模組中):  Module-Level Functions.
                                                             (line   21)
* getlogin() (於 os 模組中):             Process Parameters. (line  216)
* getLogRecordFactory() (於 logging 模組中): Module-Level Functions.
                                                             (line   32)
* getmark() (aifc.aifc 的方法):          aifc --- Read and write AIFF and AIFC files.
                                                             (line   91)
* getmark() (sunau.AU_read 的方法):      AU_read Objects.    (line   77)
* getmark() (wave.Wave_read 的方法):     Wave_read Objects.  (line   62)
* getmarkers() (aifc.aifc 的方法):       aifc --- Read and write AIFF and AIFC files.
                                                             (line   84)
* getmarkers() (sunau.AU_read 的方法):   AU_read Objects.    (line   73)
* getmarkers() (wave.Wave_read 的方法):  Wave_read Objects.  (line   58)
* getmaxyx() (curses.window 的方法):     Window Objects.     (line  253)
* getmember() (tarfile.TarFile 的方法):  TarFile Objects.    (line  100)
* getmembers() (tarfile.TarFile 的方法): TarFile Objects.    (line  108)
* getmembers() (於 inspect 模組中):      Types and members.  (line  276)
* getMessage() (logging.LogRecord 的方法): LogRecord Objects.
                                                             (line   56)
* getMessage() (xml.sax.SAXException 的方法): SAXException Objects.
                                                             (line    9)
* getMessageID() (logging.handlers.NTEventLogHandler 的方法): NTEventLogHandler.
                                                             (line   60)
* getmodule() (於 inspect 模組中):       Retrieving source code.
                                                             (line   32)
* getmodulename() (於 inspect 模組中):   Types and members.  (line  289)
* getmouse() (於 curses 模組中):         Functions<3>.       (line  145)
* getmro() (於 inspect 模組中):          Classes and functions<2>.
                                                             (line  131)
* getmtime() (於 os.path 模組中):        os path --- Common pathname manipulations.
                                                             (line  176)
* getname() (chunk.Chunk 的方法):        chunk --- Read IFF chunked data.
                                                             (line   69)
* getName() (threading.Thread 的方法):   Thread Objects.     (line  142)
* getNameByQName() (xml.sax.xmlreader.AttributesNS 的方法): The AttributesNS Interface.
                                                             (line   16)
* getnameinfo() (asyncio.loop 的方法):   DNS.                (line   11)
* getnameinfo() (於 socket 模組中):      Other functions<2>. (line  133)
* getnames() (tarfile.TarFile 的方法):   TarFile Objects.    (line  114)
* getNames() (xml.sax.xmlreader.Attributes 的方法): The Attributes Interface.
                                                             (line   15)
* getnchannels() (aifc.aifc 的方法):     aifc --- Read and write AIFF and AIFC files.
                                                             (line   50)
* getnchannels() (sunau.AU_read 的方法): AU_read Objects.    (line   14)
* getnchannels() (wave.Wave_read 的方法): Wave_read Objects. (line   15)
* getnframes() (aifc.aifc 的方法):       aifc --- Read and write AIFF and AIFC files.
                                                             (line   62)
* getnframes() (sunau.AU_read 的方法):   AU_read Objects.    (line   26)
* getnframes() (wave.Wave_read 的方法):  Wave_read Objects.  (line   27)
* getnode:                               uuid --- UUID objects according to RFC 4122.
                                                             (line  178)
* getnode() (於 uuid 模組中):            uuid --- UUID objects according to RFC 4122.
                                                             (line  160)
* getopt (模組):                         getopt --- C-style parser for command line options.
                                                             (line    6)
* getopt() (distutils.fancy_getopt.FancyGetopt 的方法): distutils fancy_getopt --- Wrapper around the standard getopt module.
                                                             (line   49)
* getopt() (於 getopt 模組中):           getopt --- C-style parser for command line options.
                                                             (line   25)
* GetoptError:                           getopt --- C-style parser for command line options.
                                                             (line   74)
* getouterframes() (於 inspect 模組中):  The interpreter stack.
                                                             (line   52)
* getoutput() (於 subprocess 模組中):    Legacy Shell Invocation Functions.
                                                             (line   41)
* getpagesize() (於 resource 模組中):    Resource Usage.     (line  101)
* getparams() (aifc.aifc 的方法):        aifc --- Read and write AIFF and AIFC files.
                                                             (line   78)
* getparams() (sunau.AU_read 的方法):    AU_read Objects.    (line   41)
* getparams() (wave.Wave_read 的方法):   Wave_read Objects.  (line   40)
* getparyx() (curses.window 的方法):     Window Objects.     (line  257)
* getpass (模組):                        getpass --- Portable password input.
                                                             (line    6)
* getpass() (於 getpass 模組中):         getpass --- Portable password input.
                                                             (line   12)
* GetPassWarning:                        getpass --- Portable password input.
                                                             (line   29)
* getpeercert() (ssl.SSLSocket 的方法):  SSL Sockets.        (line  137)
* getpeername() (socket.socket 的方法):  Socket Objects.     (line  127)
* getpen() (於 turtle 模組中):           Special Turtle methods.
                                                             (line   40)
* getpgid() (於 os 模組中):              Process Parameters. (line  227)
* getpgrp() (於 os 模組中):              Process Parameters. (line  235)
* getpid() (於 os 模組中):               Process Parameters. (line  241)
* getpos() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line   28)
* getppid() (於 os 模組中):              Process Parameters. (line  245)
* getpreferredencoding() (於 locale 模組中): locale --- Internationalization services.
                                                             (line  337)
* getpriority() (於 os 模組中):          Process Parameters. (line  256)
* getprofile() (於 sys 模組中):          sys --- System-specific parameters and functions.
                                                             (line  737)
* GetProperty() (msilib.SummaryInformation 的方法): Summary Information Objects.
                                                             (line    6)
* getProperty() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   83)
* GetPropertyCount() (msilib.SummaryInformation 的方法): Summary Information Objects.
                                                             (line   17)
* getprotobyname() (於 socket 模組中):   Other functions<2>. (line  151)
* getproxies() (於 urllib.request 模組中): urllib request --- Extensible library for opening URLs.
                                                             (line  160)
* getPublicId() (xml.sax.xmlreader.InputSource 的方法): InputSource Objects.
                                                             (line   10)
* getPublicId() (xml.sax.xmlreader.Locator 的方法): Locator Objects.
                                                             (line   16)
* getpwall() (於 pwd 模組中):            pwd --- The password database.
                                                             (line   65)
* getpwnam() (於 pwd 模組中):            pwd --- The password database.
                                                             (line   61)
* getpwuid() (於 pwd 模組中):            pwd --- The password database.
                                                             (line   57)
* getQNameByName() (xml.sax.xmlreader.AttributesNS 的方法): The AttributesNS Interface.
                                                             (line   20)
* getQNames() (xml.sax.xmlreader.AttributesNS 的方法): The AttributesNS Interface.
                                                             (line   24)
* getquota() (imaplib.IMAP4 的方法):     IMAP4 Objects.      (line  116)
* getquotaroot() (imaplib.IMAP4 的方法): IMAP4 Objects.      (line  121)
* getrandbits() (於 random 模組中):      Bookkeeping functions.
                                                             (line   41)
* getrandom() (於 os 模組中):            Random numbers<2>.  (line    6)
* getreader() (於 codecs 模組中):        codecs --- Codec registry and base classes.
                                                             (line  131)
* getrecursionlimit() (於 sys 模組中):   sys --- System-specific parameters and functions.
                                                             (line  686)
* getrefcount() (於 sys 模組中):         sys --- System-specific parameters and functions.
                                                             (line  680)
* getresgid() (於 os 模組中):            Process Parameters. (line  291)
* getresponse() (http.client.HTTPConnection 的方法): HTTPConnection Objects.
                                                             (line   58)
* getresuid() (於 os 模組中):            Process Parameters. (line  282)
* getrlimit() (於 resource 模組中):      Resource Limits.    (line   24)
* getroot() (xml.etree.ElementTree.ElementTree 的方法): ElementTree Objects.
                                                             (line   41)
* getrusage() (於 resource 模組中):      Resource Usage.     (line    8)
* getsample() (於 audioop 模組中):       audioop --- Manipulate raw audio data.
                                                             (line  108)
* getsampwidth() (aifc.aifc 的方法):     aifc --- Read and write AIFF and AIFC files.
                                                             (line   54)
* getsampwidth() (sunau.AU_read 的方法): AU_read Objects.    (line   18)
* getsampwidth() (wave.Wave_read 的方法): Wave_read Objects. (line   19)
* getscreen() (於 turtle 模組中):        Special Turtle methods.
                                                             (line   51)
* getservbyname() (於 socket 模組中):    Other functions<2>. (line  160)
* getservbyport() (於 socket 模組中):    Other functions<2>. (line  169)
* GetSetDescriptorType (於 types 模組中): Standard Interpreter Types.
                                                             (line  198)
* getshapes() (於 turtle 模組中):        Settings and special methods.
                                                             (line   63)
* getsid() (於 os 模組中):               Process Parameters. (line  432)
* getsignal() (於 signal 模組中):        Module contents<2>. (line  238)
* getsitepackages() (於 site 模組中):    Module contents<3>. (line   55)
* getsize() (chunk.Chunk 的方法):        chunk --- Read IFF chunked data.
                                                             (line   74)
* getsize() (於 os.path 模組中):         os path --- Common pathname manipulations.
                                                             (line  196)
* getsizeof() (於 sys 模組中):           sys --- System-specific parameters and functions.
                                                             (line  693)
* getsockname() (socket.socket 的方法):  Socket Objects.     (line  135)
* getsockopt() (socket.socket 的方法):   Socket Objects.     (line  141)
* getsource() (於 inspect 模組中):       Retrieving source code.
                                                             (line   55)
* getsourcefile() (於 inspect 模組中):   Retrieving source code.
                                                             (line   36)
* getsourcelines() (於 inspect 模組中):  Retrieving source code.
                                                             (line   42)
* getspall() (於 spwd 模組中):           spwd --- The shadow password database.
                                                             (line   66)
* getspnam() (於 spwd 模組中):           spwd --- The shadow password database.
                                                             (line   59)
* getstate() (codecs.IncrementalDecoder 的方法): IncrementalDecoder Objects.
                                                             (line   44)
* getstate() (codecs.IncrementalEncoder 的方法): IncrementalEncoder Objects.
                                                             (line   42)
* getstate() (於 random 模組中):         Bookkeeping functions.
                                                             (line   28)
* getstatusoutput() (於 subprocess 模組中): Legacy Shell Invocation Functions.
                                                             (line   11)
* getstr() (curses.window 的方法):       Window Objects.     (line  263)
* GetString() (msilib.Record 的方法):    Record Objects.     (line   16)
* getSubject() (logging.handlers.SMTPHandler 的方法): SMTPHandler.
                                                             (line   39)
* GetSummaryInformation() (msilib.Database 的方法): Database Objects.
                                                             (line   16)
* getswitchinterval() (於 sys 模組中):   sys --- System-specific parameters and functions.
                                                             (line  715)
* getSystemId() (xml.sax.xmlreader.InputSource 的方法): InputSource Objects.
                                                             (line   18)
* getSystemId() (xml.sax.xmlreader.Locator 的方法): Locator Objects.
                                                             (line   20)
* getsyx() (於 curses 模組中):           Functions<3>.       (line  159)
* gettarinfo() (tarfile.TarFile 的方法): TarFile Objects.    (line  224)
* gettempdir() (於 tempfile 模組中):     tempfile --- Generate temporary files and directories.
                                                             (line  225)
* gettempdirb() (於 tempfile 模組中):    tempfile --- Generate temporary files and directories.
                                                             (line  253)
* gettempprefix() (於 tempfile 模組中):  tempfile --- Generate temporary files and directories.
                                                             (line  259)
* gettempprefixb() (於 tempfile 模組中): tempfile --- Generate temporary files and directories.
                                                             (line  264)
* getTestCaseNames() (unittest.TestLoader 的方法): Loading and running tests.
                                                             (line  111)
* gettext (模組):                        gettext --- Multilingual internationalization services.
                                                             (line    6)
* gettext() (gettext.GNUTranslations 的方法): The GNUTranslations class.
                                                             (line   38)
* gettext() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   35)
* gettext() (於 gettext 模組中):         GNU gettext API.    (line   42)
* gettext() (於 locale 模組中):          Access to message catalogs.
                                                             (line    6)
* gettimeout() (socket.socket 的方法):   Socket Objects.     (line  162)
* gettrace() (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line  741)
* getturtle() (於 turtle 模組中):        Special Turtle methods.
                                                             (line   40)
* getType() (xml.sax.xmlreader.Attributes 的方法): The Attributes Interface.
                                                             (line   19)
* getuid() (於 os 模組中):               Process Parameters. (line  300)
* geturl() (urllib.parse.urllib.parse.SplitResult 的方法): Structured Parse Results.
                                                             (line   12)
* getuser() (於 getpass 模組中):         getpass --- Portable password input.
                                                             (line   34)
* getuserbase() (於 site 模組中):        Module contents<3>. (line   61)
* getusersitepackages() (於 site 模組中): Module contents<3>.
                                                             (line   69)
* getvalue() (io.BytesIO 的方法):        Buffered Streams.   (line   38)
* getvalue() (io.StringIO 的方法):       Text I/O<2>.        (line  211)
* 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   20)
* getwche() (於 msvcrt 模組中):          Console I/O.        (line   30)
* getweakrefcount() (於 weakref 模組中): weakref --- Weak references.
                                                             (line  146)
* getweakrefs() (於 weakref 模組中):     weakref --- Weak references.
                                                             (line  151)
* getwelcome() (ftplib.FTP 的方法):      FTP Objects.        (line   42)
* getwelcome() (nntplib.NNTP 的方法):    Methods<3>.         (line   28)
* getwelcome() (poplib.POP3 的方法):     POP3 Objects.       (line   20)
* getwin() (於 curses 模組中):           Functions<3>.       (line  165)
* getwindowsversion() (於 sys 模組中):   sys --- System-specific parameters and functions.
                                                             (line  752)
* getwriter() (於 codecs 模組中):        codecs --- Codec registry and base classes.
                                                             (line  139)
* getxattr() (於 os 模組中):             Linux extended attributes.
                                                             (line   10)
* getyx() (curses.window 的方法):        Window Objects.     (line  274)
* GET_AITER (opcode):                    Python Bytecode Instructions.
                                                             (line  268)
* get_all() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  252)
* get_all() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  362)
* get_all() (wsgiref.headers.Headers 的方法): wsgiref headers -- WSGI response header tools.
                                                             (line   51)
* get_all_breaks() (bdb.Bdb 的方法):     bdb --- Debugger framework.
                                                             (line  332)
* get_all_start_methods() (於 multiprocessing 模組中): Miscellaneous<3>.
                                                             (line   70)
* GET_ANEXT (opcode):                    Python Bytecode Instructions.
                                                             (line  277)
* get_app() (wsgiref.simple_server.WSGIServer 的方法): wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line   66)
* get_archive_formats() (於 shutil 模組中): Archiving operations.
                                                             (line   57)
* get_args() (於 typing 模組中):         Classes functions and decorators.
                                                             (line  640)
* get_asyncgen_hooks() (於 sys 模組中):  sys --- System-specific parameters and functions.
                                                             (line  805)
* get_attribute() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  798)
* GET_AWAITABLE (opcode):                Python Bytecode Instructions.
                                                             (line  260)
* get_begidx() (於 readline 模組中):     Completion.         (line   40)
* get_blocking() (於 os 模組中):         File Descriptor Operations.
                                                             (line  196)
* get_body() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  516)
* get_body_encoding() (email.charset.Charset 的方法): email charset Representing character sets.
                                                             (line   96)
* get_boundary() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  402)
* get_boundary() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  580)
* get_bpbynumber() (bdb.Bdb 的方法):     bdb --- Debugger framework.
                                                             (line  309)
* get_break() (bdb.Bdb 的方法):          bdb --- Debugger framework.
                                                             (line  318)
* get_breaks() (bdb.Bdb 的方法):         bdb --- Debugger framework.
                                                             (line  322)
* get_buffer() (asyncio.BufferedProtocol 的方法): Buffered Streaming Protocols.
                                                             (line   23)
* get_buffer() (xdrlib.Packer 的方法):   Packer Objects.     (line    8)
* get_buffer() (xdrlib.Unpacker 的方法): Unpacker Objects.   (line   22)
* get_bytes() (mailbox.Mailbox 的方法):  Mailbox objects.    (line  159)
* get_cache_token() (於 abc 模組中):     abc --- Abstract Base Classes.
                                                             (line  322)
* get_ca_certs() (ssl.SSLContext 的方法): SSL Contexts.      (line  158)
* get_channel_binding() (ssl.SSLSocket 的方法): SSL Sockets. (line  236)
* get_charset() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  265)
* get_charsets() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  430)
* get_charsets() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  614)
* get_children() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   62)
* get_children() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line   19)
* get_child_watcher() (asyncio.AbstractEventLoopPolicy 的方法): Policy Objects.
                                                             (line   33)
* get_child_watcher() (於 asyncio 模組中): Process Watchers. (line   25)
* get_ciphers() (ssl.SSLContext 的方法): SSL Contexts.       (line  172)
* get_clock_info() (於 time 模組中):     Functions<2>.       (line   97)
* get_close_matches() (於 difflib 模組中): difflib --- Helpers for computing deltas.
                                                             (line  205)
* get_code() (importlib.abc.InspectLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  376)
* get_code() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  567)
* get_code() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  330)
* get_code() (importlib.machinery.SourcelessFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  273)
* get_code() (zipimport.zipimporter 的方法): zipimporter Objects.
                                                             (line   28)
* get_completer() (於 readline 模組中):  Completion.         (line   29)
* get_completer_delims() (於 readline 模組中): Completion.   (line   48)
* get_completion_type() (於 readline 模組中): Completion.    (line   34)
* get_config_h_filename() (於 distutils.sysconfig 模組中): distutils sysconfig --- System configuration information.
                                                             (line   41)
* get_config_h_filename() (於 sysconfig 模組中): Other functions<3>.
                                                             (line   68)
* get_config_var() (於 distutils.sysconfig 模組中): distutils sysconfig --- System configuration information.
                                                             (line   27)
* get_config_var() (於 sysconfig 模組中): Configuration variables.
                                                             (line   26)
* get_config_vars() (於 distutils.sysconfig 模組中): distutils sysconfig --- System configuration information.
                                                             (line   32)
* get_config_vars() (於 sysconfig 模組中): Configuration variables.
                                                             (line   16)
* get_content() (email.contentmanager.ContentManager 的方法): email contentmanager Managing MIME Content.
                                                             (line   19)
* get_content() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  581)
* get_content() (於 email.contentmanager 模組中): Content Manager Instances.
                                                             (line   24)
* get_content_charset() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  423)
* get_content_charset() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  603)
* get_content_disposition() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  453)
* get_content_disposition() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  628)
* get_content_maintype() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  322)
* get_content_maintype() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  432)
* get_content_subtype() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  328)
* get_content_subtype() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  438)
* get_content_type() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  306)
* get_content_type() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  416)
* get_context() (於 multiprocessing 模組中): Miscellaneous<3>.
                                                             (line   80)
* get_coro() (asyncio.Task 的方法):      Task Object.        (line  203)
* get_coroutine_origin_tracking_depth() (於 sys 模組中): sys --- System-specific parameters and functions.
                                                             (line  819)
* get_count() (於 gc 模組中):            gc --- Garbage Collector interface.
                                                             (line  110)
* get_current_history_length() (於 readline 模組中): History list.
                                                             (line   14)
* get_data() (importlib.abc.FileLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  490)
* get_data() (importlib.abc.ResourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  357)
* get_data() (zipimport.zipimporter 的方法): zipimporter Objects.
                                                             (line   33)
* get_data() (於 pkgutil 模組中):        pkgutil --- Package extension utility.
                                                             (line  201)
* get_date() (mailbox.MaildirMessage 的方法): MaildirMessage.
                                                             (line   92)
* get_debug() (asyncio.loop 的方法):     Enabling debug mode.
                                                             (line    6)
* get_debug() (於 gc 模組中):            gc --- Garbage Collector interface.
                                                             (line   55)
* get_default() (argparse.ArgumentParser 的方法): Parser defaults.
                                                             (line   33)
* get_default_compiler() (於 distutils.ccompiler 模組中): distutils ccompiler --- CCompiler base class.
                                                             (line   36)
* get_default_domain() (於 nis 模組中):  nis --- Interface to Sun's NIS Yellow Pages.
                                                             (line   48)
* get_default_type() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  333)
* get_default_type() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  443)
* get_default_verify_paths() (於 ssl 模組中): Certificate handling.
                                                             (line  101)
* get_dialect() (於 csv 模組中):         Module Contents<3>. (line   85)
* get_docstring() (於 ast 模組中):       ast Helpers.        (line   61)
* get_doctest() (doctest.DocTestParser 的方法): DocTestParser objects.
                                                             (line   13)
* get_endidx() (於 readline 模組中):     Completion.         (line   40)
* get_environ() (wsgiref.simple_server.WSGIRequestHandler 的方法): wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line   88)
* get_errno() (於 ctypes 模組中):        Utility functions.  (line  121)
* get_event_loop() (asyncio.AbstractEventLoopPolicy 的方法): Policy Objects.
                                                             (line   12)
* get_event_loop() (於 asyncio 模組中):  Event Loop.         (line   39)
* get_event_loop_policy() (於 asyncio 模組中): Getting and Setting the Policy.
                                                             (line    9)
* get_examples() (doctest.DocTestParser 的方法): DocTestParser objects.
                                                             (line   22)
* get_exception_handler() (asyncio.loop 的方法): Error Handling API.
                                                             (line   19)
* get_exec_path() (於 os 模組中):        Process Parameters. (line  153)
* get_extra_info() (asyncio.BaseTransport 的方法): Base Transport.
                                                             (line   20)
* get_extra_info() (asyncio.StreamWriter 的方法): StreamWriter.
                                                             (line   61)
* get_field() (string.Formatter 的方法): Custom String Formatting.
                                                             (line   55)
* get_file() (mailbox.Babyl 的方法):     Babyl.              (line   49)
* get_file() (mailbox.Mailbox 的方法):   Mailbox objects.    (line  175)
* get_file() (mailbox.Maildir 的方法):   Maildir.            (line  119)
* get_file() (mailbox.mbox 的方法):      mbox.               (line   33)
* get_file() (mailbox.MH 的方法):        MH.                 (line   93)
* get_file() (mailbox.MMDF 的方法):      MMDF.               (line   29)
* get_filename() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  392)
* get_filename() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  570)
* get_filename() (importlib.abc.ExecutionLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  446)
* get_filename() (importlib.abc.FileLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  486)
* get_filename() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  338)
* get_filename() (zipimport.zipimporter 的方法): zipimporter Objects.
                                                             (line   41)
* get_file_breaks() (bdb.Bdb 的方法):    bdb --- Debugger framework.
                                                             (line  327)
* 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 的方法): Maildir.            (line   65)
* get_folder() (mailbox.MH 的方法):      MH.                 (line   36)
* get_frees() (symtable.Function 的方法): Examining Symbol Tables.
                                                             (line   88)
* get_freeze_count() (於 gc 模組中):     gc --- Garbage Collector interface.
                                                             (line  201)
* get_from() (mailbox.mboxMessage 的方法): mboxMessage.      (line   47)
* get_from() (mailbox.MMDFMessage 的方法): MMDFMessage.      (line   46)
* get_full_url() (urllib.request.Request 的方法): Request Objects.
                                                             (line  104)
* get_globals() (symtable.Function 的方法): Examining Symbol Tables.
                                                             (line   80)
* get_grouped_opcodes() (difflib.SequenceMatcher 的方法): SequenceMatcher Objects.
                                                             (line  166)
* get_handle_inheritable() (於 os 模組中): Inheritance of File Descriptors.
                                                             (line   32)
* get_header() (urllib.request.Request 的方法): Request Objects.
                                                             (line  118)
* get_history_item() (於 readline 模組中): History list.     (line   20)
* get_history_length() (於 readline 模組中): History file.   (line   30)
* get_id() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   15)
* get_ident() (於 threading 模組中):     threading --- Thread-based parallelism.
                                                             (line   84)
* get_ident() (於 _thread 模組中):       _thread --- Low-level threading API.
                                                             (line   72)
* get_identifiers() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   48)
* get_importer() (於 pkgutil 模組中):    pkgutil --- Package extension utility.
                                                             (line   92)
* get_info() (mailbox.MaildirMessage 的方法): MaildirMessage.
                                                             (line  102)
* get_inheritable() (socket.socket 的方法): Socket Objects.  (line  119)
* get_inheritable() (於 os 模組中):      Inheritance of File Descriptors.
                                                             (line   23)
* get_instructions() (於 dis 模組中):    Analysis functions. (line  110)
* get_interpreter() (於 zipapp 模組中):  Python API.         (line   82)
* GET_ITER (opcode):                     Python Bytecode Instructions.
                                                             (line  113)
* 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  129)
* get_lineno() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   26)
* get_line_buffer() (於 readline 模組中): Line buffer.       (line    8)
* get_loader() (於 pkgutil 模組中):      pkgutil --- Package extension utility.
                                                             (line  106)
* get_locals() (symtable.Function 的方法): Examining Symbol Tables.
                                                             (line   76)
* get_logger() (於 multiprocessing 模組中): Logging<2>.      (line   11)
* get_loop() (asyncio.Future 的方法):    Future Object.      (line  129)
* get_loop() (asyncio.Server 的方法):    Server Objects.     (line   41)
* get_magic() (於 imp 模組中):           imp --- Access the import internals.
                                                             (line   17)
* get_makefile_filename() (於 distutils.sysconfig 模組中): distutils sysconfig --- System configuration information.
                                                             (line   49)
* get_makefile_filename() (於 sysconfig 模組中): Other functions<3>.
                                                             (line   72)
* get_map() (selectors.BaseSelector 的方法): Classes<3>.     (line  153)
* get_matching_blocks() (difflib.SequenceMatcher 的方法): SequenceMatcher Objects.
                                                             (line  105)
* get_message() (mailbox.Mailbox 的方法): Mailbox objects.   (line  152)
* get_method() (urllib.request.Request 的方法): Request Objects.
                                                             (line   67)
* get_methods() (symtable.Class 的方法): Examining Symbol Tables.
                                                             (line   98)
* get_mixed_type_key() (於 ipaddress 模組中): Other Module Level Functions.
                                                             (line   56)
* get_name() (asyncio.Task 的方法):      Task Object.        (line  209)
* get_name() (symtable.Symbol 的方法):   Examining Symbol Tables.
                                                             (line  108)
* get_name() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   19)
* get_namespace() (symtable.Symbol 的方法): Examining Symbol Tables.
                                                             (line  179)
* get_namespaces() (symtable.Symbol 的方法): Examining Symbol Tables.
                                                             (line  175)
* get_native_id() (於 threading 模組中): threading --- Thread-based parallelism.
                                                             (line   94)
* get_native_id() (於 _thread 模組中):   _thread --- Low-level threading API.
                                                             (line   80)
* get_nonlocals() (symtable.Function 的方法): Examining Symbol Tables.
                                                             (line   84)
* get_nonstandard_attr() (http.cookiejar.Cookie 的方法): Cookie Objects<2>.
                                                             (line   98)
* get_nowait() (asyncio.Queue 的方法):   Queue.              (line   45)
* get_nowait() (multiprocessing.Queue 的方法): Pipes and Queues.
                                                             (line  154)
* get_nowait() (queue.Queue 的方法):     Queue Objects.      (line   61)
* get_nowait() (queue.SimpleQueue 的方法): SimpleQueue Objects.
                                                             (line   51)
* get_objects() (於 gc 模組中):          gc --- Garbage Collector interface.
                                                             (line   59)
* get_object_traceback() (於 tracemalloc 模組中): Functions<9>.
                                                             (line   12)
* get_opcodes() (difflib.SequenceMatcher 的方法): SequenceMatcher Objects.
                                                             (line  123)
* get_option() (optparse.OptionParser 的方法): Querying and manipulating your option parser.
                                                             (line   37)
* get_option_group() (optparse.OptionParser 的方法): Grouping Options.
                                                             (line  103)
* get_option_order() (distutils.fancy_getopt.FancyGetopt 的方法): distutils fancy_getopt --- Wrapper around the standard getopt module.
                                                             (line   62)
* get_origin() (於 typing 模組中):       Classes functions and decorators.
                                                             (line  638)
* get_original_stdout() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  380)
* get_osfhandle() (於 msvcrt 模組中):    File Operations.    (line   55)
* get_output_charset() (email.charset.Charset 的方法): email charset Representing character sets.
                                                             (line  111)
* get_param() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  478)
* get_parameters() (symtable.Function 的方法): Examining Symbol Tables.
                                                             (line   71)
* get_params() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  457)
* get_path() (於 sysconfig 模組中):      Installation paths. (line   67)
* get_paths() (於 sysconfig 模組中):     Installation paths. (line   97)
* get_path_names() (於 sysconfig 模組中): Installation paths.
                                                             (line   62)
* get_payload() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  180)
* get_pid() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line    6)
* get_pipe_transport() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   10)
* get_platform() (於 distutils.util 模組中): distutils util --- Miscellaneous other utility functions.
                                                             (line    9)
* get_platform() (於 sysconfig 模組中):  Other functions<3>. (line   11)
* get_poly() (於 turtle 模組中):         Special Turtle methods.
                                                             (line   17)
* get_position() (xdrlib.Unpacker 的方法): Unpacker Objects. (line   12)
* get_protocol() (asyncio.BaseTransport 的方法): Base Transport.
                                                             (line   87)
* get_python_inc() (於 distutils.sysconfig 模組中): distutils sysconfig --- System configuration information.
                                                             (line   57)
* get_python_lib() (於 distutils.sysconfig 模組中): distutils sysconfig --- System configuration information.
                                                             (line   67)
* get_python_version() (於 sysconfig 模組中): Other functions<3>.
                                                             (line    6)
* get_recsrc() (ossaudiodev.oss_mixer_device 的方法): Mixer Device Objects.
                                                             (line   83)
* get_referents() (於 gc 模組中):        gc --- Garbage Collector interface.
                                                             (line  142)
* get_referrers() (於 gc 模組中):        gc --- Garbage Collector interface.
                                                             (line  120)
* get_request() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line  131)
* get_returncode() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   29)
* get_running_loop() (於 asyncio 模組中): Event Loop.        (line   29)
* get_scheme() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line  187)
* get_scheme_names() (於 sysconfig 模組中): Installation paths.
                                                             (line   57)
* get_sequences() (mailbox.MH 的方法):   MH.                 (line   53)
* get_sequences() (mailbox.MHMessage 的方法): MHMessage.     (line   32)
* get_server() (multiprocessing.managers.BaseManager 的方法): Managers.
                                                             (line   46)
* get_server_certificate() (於 ssl 模組中): Certificate handling.
                                                             (line   71)
* get_shapepoly() (於 turtle 模組中):    Appearance.         (line  188)
* get_socket() (telnetlib.Telnet 的方法): Telnet Objects.    (line   93)
* get_source() (importlib.abc.InspectLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  390)
* get_source() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  584)
* get_source() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  334)
* get_source() (importlib.machinery.SourcelessFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  278)
* get_source() (zipimport.zipimporter 的方法): zipimporter Objects.
                                                             (line   49)
* get_source_segment() (於 ast 模組中):  ast Helpers.        (line   70)
* get_special_folder_path() (內建函式):  The Postinstallation script.
                                                             (line   32)
* get_stack() (asyncio.Task 的方法):     Task Object.        (line  167)
* get_stack() (bdb.Bdb 的方法):          bdb --- Debugger framework.
                                                             (line  339)
* get_starttag_text() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line   32)
* get_start_method() (於 multiprocessing 模組中): Miscellaneous<3>.
                                                             (line   92)
* get_stats() (於 gc 模組中):            gc --- Garbage Collector interface.
                                                             (line   70)
* get_stderr() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line  127)
* get_stderr() (wsgiref.simple_server.WSGIRequestHandler 的方法): wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line   98)
* get_stdin() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line  122)
* get_string() (mailbox.Mailbox 的方法): Mailbox objects.    (line  167)
* get_subdir() (mailbox.MaildirMessage 的方法): MaildirMessage.
                                                             (line   47)
* get_suffixes() (於 imp 模組中):        imp --- Access the import internals.
                                                             (line   26)
* get_symbols() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   57)
* get_tag() (於 imp 模組中):             imp --- Access the import internals.
                                                             (line  242)
* get_task_factory() (asyncio.loop 的方法): Creating Futures and Tasks.
                                                             (line   42)
* 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_terminator() (asynchat.async_chat 的方法): asynchat --- Asynchronous socket command/response handler.
                                                             (line   97)
* get_threshold() (於 gc 模組中):        gc --- Garbage Collector interface.
                                                             (line  115)
* get_token() (shlex.shlex 的方法):      shlex Objects.      (line    8)
* get_traceback_limit() (於 tracemalloc 模組中): Functions<9>.
                                                             (line   22)
* get_traced_memory() (於 tracemalloc 模組中): Functions<9>. (line   32)
* get_tracemalloc_memory() (於 tracemalloc 模組中): Functions<9>.
                                                             (line   38)
* get_type() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   10)
* get_type_hints() (於 typing 模組中):   Classes functions and decorators.
                                                             (line  625)
* get_unixfrom() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  150)
* get_unixfrom() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  162)
* get_unpack_formats() (於 shutil 模組中): Archiving operations.
                                                             (line  147)
* get_usage() (optparse.OptionParser 的方法): Other methods. (line   22)
* get_value() (string.Formatter 的方法): Custom String Formatting.
                                                             (line   65)
* get_version() (optparse.OptionParser 的方法): Printing a version string.
                                                             (line   34)
* get_visible() (mailbox.BabylMessage 的方法): BabylMessage. (line   63)
* get_wch() (curses.window 的方法):      Window Objects.     (line  238)
* 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  117)
* gid (tarfile.TarInfo 的屬性):          TarInfo Objects.    (line   76)
* GIL:                                   Glossary.           (line  546)
* glob (模組):                           glob --- Unix style pathname pattern expansion.
                                                             (line    6)
* glob() (msilib.Directory 的方法):      Directory Objects.  (line   40)
* glob() (pathlib.Path 的方法):          Methods<2>.         (line   86)
* glob() (於 glob 模組中):               glob --- Unix style pathname pattern expansion.
                                                             (line   29)
* global interpreter lock:               Thread State and the Global Interpreter Lock.
                                                             (line    6)
* global interpreter lock <1>:           Glossary.           (line  550)
* global; name; binding:                 The global statement.
                                                             (line    6)
* global; namespace:                     The standard type hierarchy.
                                                             (line  303)
* globals() (內建函式):                  內建函式.           (line  684)
* globs (doctest.DocTest 的屬性):        DocTest Objects.    (line   22)
* gmtime() (於 time 模組中):             Functions<2>.       (line  131)
* gname (tarfile.TarInfo 的屬性):        TarInfo Objects.    (line   84)
* GNOME:                                 The Catalog constructor.
                                                             (line    6)
* GNUTranslations (gettext 中的類別):    The GNUTranslations class.
                                                             (line   33)
* GNU_FORMAT (於 tarfile 模組中):        tarfile --- Read and write tar archive files.
                                                             (line  225)
* gnu_getopt() (於 getopt 模組中):       getopt --- C-style parser for command line options.
                                                             (line   62)
* got (doctest.DocTestFailure 的屬性):   Debugging.          (line  204)
* goto() (於 turtle 模組中):             Turtle motion.      (line   74)
* grammar:                               Notation.           (line    6)
* Graphical User Interface:              以 Tk 打造 GUI.     (line    6)
* GREATER (於 token 模組中):             token --- Constants used with Python parse trees.
                                                             (line  110)
* GREATEREQUAL (於 token 模組中):        token --- Constants used with Python parse trees.
                                                             (line  146)
* Greenwich Mean Time:                   time --- Time access and conversions.
                                                             (line   40)
* GRND_NONBLOCK (於 os 模組中):          Random numbers<2>.  (line   73)
* GRND_RANDOM (於 os 模組中):            Random numbers<2>.  (line   86)
* Group (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  457)
* group() (nntplib.NNTP 的方法):         Methods<3>.         (line  158)
* group() (pathlib.Path 的方法):         Methods<2>.         (line  109)
* group() (re.Match 的方法):             Match Objects.      (line   28)
* groupby() (於 itertools 模組中):       Itertool functions. (line  298)
* groupdict() (re.Match 的方法):         Match Objects.      (line  120)
* groupindex (re.Pattern 的屬性):        Regular Expression Objects.
                                                             (line  112)
* grouping:                              Indentation.        (line    6)
* groups (email.headerregistry.AddressHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  188)
* groups (re.Pattern 的屬性):            Regular Expression Objects.
                                                             (line  108)
* groups() (re.Match 的方法):            Match Objects.      (line   97)
* grp (模組):                            grp --- The group database.
                                                             (line    6)
* gt() (於 operator 模組中):             operator --- Standard operators as functions.
                                                             (line   24)
* guess_all_extensions() (mimetypes.MimeTypes 的方法): MimeTypes Objects.
                                                             (line   65)
* guess_all_extensions() (於 mimetypes 模組中): mimetypes --- Map filenames to MIME types.
                                                             (line   51)
* guess_extension() (mimetypes.MimeTypes 的方法): MimeTypes Objects.
                                                             (line   55)
* guess_extension() (於 mimetypes 模組中): mimetypes --- Map filenames to MIME types.
                                                             (line   63)
* guess_scheme() (於 wsgiref.util 模組中): wsgiref util -- WSGI environment utilities.
                                                             (line   12)
* guess_type() (mimetypes.MimeTypes 的方法): MimeTypes Objects.
                                                             (line   60)
* guess_type() (於 mimetypes 模組中):    mimetypes --- Map filenames to MIME types.
                                                             (line   24)
* GUI:                                   以 Tk 打造 GUI.     (line    6)
* gzip (模組):                           gzip --- Support for gzip files.
                                                             (line    6)
* gzip command line option; –best:       Command line options.
                                                             (line   14)
* gzip command line option; -d:          Command line options.
                                                             (line   18)
* gzip command line option; –decompress: Command line options.
                                                             (line   18)
* gzip command line option; –fast:       Command line options.
                                                             (line   10)
* gzip command line option; -h:          Command line options.
                                                             (line   22)
* gzip command line option; –help:       Command line options.
                                                             (line   22)
* gzip command line option; file:        Command line options.
                                                             (line    6)
* GzipFile (gzip 中的類別):              gzip --- Support for gzip files.
                                                             (line   70)
* halfdelay() (於 curses 模組中):        Functions<3>.       (line  195)
* Handle (asyncio 中的類別):             Callback Handles.   (line    6)
* handle an exception:                   Exceptions.         (line    6)
* handle() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  184)
* handle() (logging.Handler 的方法):     Handler Objects.    (line   81)
* handle() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   62)
* handle() (logging.Logger 的方法):      Logger Objects.     (line  291)
* handle() (logging.NullHandler 的方法): NullHandler.        (line   20)
* handle() (socketserver.BaseRequestHandler 的方法): Request Handler Objects.
                                                             (line   20)
* handle() (wsgiref.simple_server.WSGIRequestHandler 的方法): wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line  103)
* handleError() (logging.Handler 的方法): Handler Objects.   (line   88)
* handleError() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   33)
* Handler (logging 中的類別):            Handler Objects.    (line   11)
* handler() (於 cgitb 模組中):           cgitb --- Traceback manager for CGI scripts.
                                                             (line   66)
* handle_accept() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  143)
* handle_accepted() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  153)
* handle_charref() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line   93)
* handle_close() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  134)
* handle_comment() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line  102)
* handle_connect() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  128)
* handle_data() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line   80)
* handle_decl() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line  115)
* handle_defect() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  218)
* handle_endtag() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line   64)
* handle_entityref() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line   86)
* handle_error() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  138)
* handle_error() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line  137)
* handle_expect_100() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  197)
* handle_expt() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  122)
* handle_one_request() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  191)
* handle_pi() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line  123)
* handle_read() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  107)
* handle_request() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line   21)
* handle_request() (xmlrpc.server.CGIXMLRPCRequestHandler 的方法): CGIXMLRPCRequestHandler.
                                                             (line   51)
* handle_startendtag() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line   71)
* handle_starttag() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line   45)
* handle_timeout() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line  147)
* handle_write() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  112)
* harmonic_mean() (於 statistics 模組中): 函式細節.          (line   84)
* hasattr() (內建函式):                  內建函式.           (line  691)
* hasAttribute() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   22)
* hasAttributeNS() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   26)
* hasAttributes() (xml.dom.Node 的方法): Node Objects.       (line   94)
* hasChildNodes() (xml.dom.Node 的方法): Node Objects.       (line   98)
* hascompare (於 dis 模組中):            Opcode collections. (line   49)
* hasconst (於 dis 模組中):              Opcode collections. (line   21)
* hasFeature() (xml.dom.DOMImplementation 的方法): DOMImplementation Objects.
                                                             (line   11)
* hasfree (於 dis 模組中):               Opcode collections. (line   25)
* hash character:                        Comments.           (line    6)
* hash() (內建函式):                     內建函式.           (line  698)
* hash-based pyc:                        Glossary.           (line  573)
* hash.block_size (於 hashlib 模組中):   Hash algorithms.    (line   99)
* hash.digest_size (於 hashlib 模組中):  Hash algorithms.    (line   95)
* hashable:                              Dictionary displays.
                                                             (line   37)
* hashable <1>:                          Glossary.           (line  579)
* Hashable (collections.abc 中的類別):   Collections Abstract Base Classes.
                                                             (line  108)
* Hashable (typing 中的類別):            Classes functions and decorators.
                                                             (line  195)
* hasHandlers() (logging.Logger 的方法): Logger Objects.     (line  306)
* hashfunc (C 型態):                     Slot Type typedefs. (line   87)
* hashlib (模組):                        hashlib --- Secure hashes and message digests.
                                                             (line    6)
* hash_info (於 sys 模組中):             sys --- System-specific parameters and functions.
                                                             (line  829)
* hasjabs (於 dis 模組中):               Opcode collections. (line   41)
* hasjrel (於 dis 模組中):               Opcode collections. (line   37)
* haslocal (於 dis 模組中):              Opcode collections. (line   45)
* hasname (於 dis 模組中):               Opcode collections. (line   33)
* HAS_ALPN (於 ssl 模組中):              Constants<9>.       (line  354)
* has_children() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   39)
* has_colors() (於 curses 模組中):       Functions<3>.       (line  171)
* has_dualstack_ipv6() (於 socket 模組中): Creating sockets. (line  137)
* HAS_ECDH (於 ssl 模組中):              Constants<9>.       (line  370)
* has_exec() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   44)
* has_extn() (smtplib.SMTP 的方法):      SMTP Objects.       (line   85)
* has_function() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  211)
* has_header() (csv.Sniffer 的方法):     Module Contents<3>. (line  216)
* has_header() (urllib.request.Request 的方法): Request Objects.
                                                             (line   92)
* has_ic() (於 curses 模組中):           Functions<3>.       (line  176)
* has_il() (於 curses 模組中):           Functions<3>.       (line  183)
* has_ipv6 (於 socket 模組中):           Constants<8>.       (line  213)
* has_key (2to3 fixer):                  Fixers.             (line  119)
* has_key() (於 curses 模組中):          Functions<3>.       (line  190)
* has_location (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  410)
* HAS_NEVER_CHECK_COMMON_NAME (於 ssl 模組中): Constants<9>. (line  362)
* has_nonstandard_attr() (http.cookiejar.Cookie 的方法): Cookie Objects<2>.
                                                             (line   94)
* HAS_NPN (於 ssl 模組中):               Constants<9>.       (line  385)
* has_option() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  106)
* has_option() (optparse.OptionParser 的方法): Querying and manipulating your option parser.
                                                             (line   42)
* has_section() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line   97)
* HAS_SNI (於 ssl 模組中):               Constants<9>.       (line  378)
* HAS_SSLv2 (於 ssl 模組中):             Constants<9>.       (line  395)
* HAS_SSLv3 (於 ssl 模組中):             Constants<9>.       (line  402)
* has_ticket (ssl.SSLSession 的屬性):    SSL session.        (line   20)
* HAS_TLSv1 (於 ssl 模組中):             Constants<9>.       (line  409)
* HAS_TLSv1_1 (於 ssl 模組中):           Constants<9>.       (line  416)
* HAS_TLSv1_2 (於 ssl 模組中):           Constants<9>.       (line  423)
* HAS_TLSv1_3 (於 ssl 模組中):           Constants<9>.       (line  430)
* HAVE_ARGUMENT (opcode):                Python Bytecode Instructions.
                                                             (line  899)
* HAVE_CONTEXTVAR (於 decimal 模組中):   Constants<4>.       (line   32)
* HAVE_DOCSTRINGS (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  137)
* HAVE_THREADS (於 decimal 模組中):      Constants<4>.       (line   25)
* HCI_DATA_DIR (於 socket 模組中):       Constants<8>.       (line  226)
* HCI_FILTER (於 socket 模組中):         Constants<8>.       (line  226)
* HCI_TIME_STAMP (於 socket 模組中):     Constants<8>.       (line  226)
* head() (nntplib.NNTP 的方法):          Methods<3>.         (line  266)
* Header (email.header 中的類別):        email header Internationalized headers.
                                                             (line   60)
* HeaderError:                           tarfile --- Read and write tar archive files.
                                                             (line  205)
* HeaderParseError:                      email errors Exception and Defect classes.
                                                             (line   26)
* HeaderParser (email.parser 中的類別):  Parser API.         (line  104)
* HeaderRegistry (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  299)
* headers (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  104)
* headers (urllib.error.HTTPError 的屬性): urllib error --- Exception classes raised by urllib request.
                                                             (line   49)
* Headers (wsgiref.headers 中的類別):    wsgiref headers -- WSGI response header tools.
                                                             (line    9)
* headers (xmlrpc.client.ProtocolError 的屬性): ProtocolError Objects.
                                                             (line   25)
* header_encode() (email.charset.Charset 的方法): email charset Representing character sets.
                                                             (line  118)
* header_encode_lines() (email.charset.Charset 的方法): email charset Representing character sets.
                                                             (line  125)
* header_encoding (email.charset.Charset 的屬性): email charset Representing character sets.
                                                             (line   59)
* header_factory (email.policy.EmailPolicy 的屬性): email policy Policy Objects.
                                                             (line  391)
* header_fetch_parse() (email.policy.Compat32 的方法): email policy Policy Objects.
                                                             (line  578)
* header_fetch_parse() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  441)
* header_fetch_parse() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  302)
* header_items() (urllib.request.Request 的方法): Request Objects.
                                                             (line  123)
* header_max_count() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  418)
* header_max_count() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  243)
* header_offset (zipfile.ZipInfo 的屬性): ZipInfo Objects.   (line  131)
* header_source_parse() (email.policy.Compat32 的方法): email policy Policy Objects.
                                                             (line  566)
* header_source_parse() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  424)
* header_source_parse() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  265)
* header_store_parse() (email.policy.Compat32 的方法): email policy Policy Objects.
                                                             (line  574)
* header_store_parse() (email.policy.EmailPolicy 的方法): email policy Policy Objects.
                                                             (line  432)
* header_store_parse() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  286)
* heading() (tkinter.ttk.Treeview 的方法): ttk Treeview.     (line  105)
* heading() (於 turtle 模組中):          Tell Turtle's state.
                                                             (line   58)
* heapify() (於 heapq 模組中):           heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   48)
* heapmin() (於 msvcrt 模組中):          Other Functions.    (line    6)
* heappop() (於 heapq 模組中):           heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   36)
* heappush() (於 heapq 模組中):          heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   32)
* heappushpop() (於 heapq 模組中):       heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   42)
* heapq (模組):                          heapq --- 堆積佇列 heap queue 演算法.
                                                             (line    6)
* heapreplace() (於 heapq 模組中):       heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   52)
* helo() (smtplib.SMTP 的方法):          SMTP Objects.       (line   47)
* help (optparse.Option 的屬性):         Option attributes.  (line   72)
* help (pdb command):                    Debugger Commands.  (line   47)
* help() (nntplib.NNTP 的方法):          Methods<3>.         (line  214)
* help() (內建函式):                     內建函式.           (line  711)
* help; online:                          pydoc --- Documentation generator and online help system.
                                                             (line    8)
* herror:                                Exceptions<10>.     (line   13)
* hex (uuid.UUID 的屬性):                uuid --- UUID objects according to RFC 4122.
                                                             (line  127)
* hex() (bytearray 的方法):              Bytearray Objects.  (line   52)
* hex() (bytes 的方法):                  Bytes Objects.      (line   78)
* hex() (float 的方法):                  Additional Methods on Float.
                                                             (line   33)
* hex() (memoryview 的方法):             Memory Views.       (line  182)
* hex() (內建函式):                      內建函式.           (line  733)
* hexadecimal literal:                   Numeric literals.   (line    6)
* hexadecimal; literals:                 Numeric Types --- int float complex.
                                                             (line   19)
* hexbin() (於 binhex 模組中):           binhex --- Encode and decode binhex4 files.
                                                             (line   23)
* hexdigest() (hashlib.hash 的方法):     Hash algorithms.    (line  134)
* hexdigest() (hashlib.shake 的方法):    SHAKE variable length digests.
                                                             (line   17)
* hexdigest() (hmac.HMAC 的方法):        hmac --- Keyed-Hashing for Message Authentication.
                                                             (line   68)
* hexdigits (於 string 模組中):          String constants.   (line   28)
* hexlify() (於 binascii 模組中):        binascii --- Convert between binary and ASCII.
                                                             (line  130)
* hexversion (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line  869)
* hidden() (curses.panel.Panel 的方法):  Panel Objects.      (line   25)
* hide() (curses.panel.Panel 的方法):    Panel Objects.      (line   30)
* hide() (tkinter.ttk.Notebook 的方法):  ttk Notebook.       (line   23)
* hideturtle() (於 turtle 模組中):       Visibility.         (line    6)
* hide_cookie2 (http.cookiejar.CookiePolicy 的屬性): CookiePolicy Objects.
                                                             (line   76)
* HierarchyRequestErr:                   Exceptions<14>.     (line   29)
* HIGHEST_PROTOCOL (於 pickle 模組中):   Module Interface.   (line   14)
* HIGH_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   66)
* 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  279)
* HList (tkinter.tix 中的類別):          Hierarchical ListBox.
                                                             (line    6)
* hls_to_rgb() (於 colorsys 模組中):     colorsys --- Conversions between color systems.
                                                             (line   40)
* hmac (模組):                           hmac --- Keyed-Hashing for Message Authentication.
                                                             (line    6)
* HOME:                                  os path.            (line   15)
* HOME <1>:                              Changes in the Python API.
                                                             (line  116)
* HOME <2>:                              Windows<9>.         (line   13)
* HOME <3>:                              Windows<9>.         (line   16)
* HOME <4>:                              os path --- Common pathname manipulations.
                                                             (line  139)
* HOME <5>:                              os path --- Common pathname manipulations.
                                                             (line  155)
* HOME <6>:                              distutils util --- Miscellaneous other utility functions.
                                                             (line   77)
* HOME <7>:                              Location and names of config files.
                                                             (line   50)
* HOME <8>:                              Location and names of config files.
                                                             (line   67)
* home() (pathlib.Path 的類別成員):      Methods<2>.         (line   25)
* home() (於 turtle 模組中):             Turtle motion.      (line  161)
* HOMEDRIVE:                             os path --- Common pathname manipulations.
                                                             (line  146)
* HOMEDRIVE <1>:                         Location and names of config files.
                                                             (line   68)
* HOMEPATH:                              os path --- Common pathname manipulations.
                                                             (line  146)
* HOMEPATH <1>:                          Location and names of config files.
                                                             (line   68)
* hooks; import:                         Import hooks.       (line    6)
* hooks; meta:                           Import hooks.       (line    6)
* hooks; path:                           Import hooks.       (line    6)
* hook_compressed() (於 fileinput 模組中): fileinput --- Iterate over lines from multiple input streams.
                                                             (line  188)
* hook_encoded() (於 fileinput 模組中):  fileinput --- Iterate over lines from multiple input streams.
                                                             (line  199)
* 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  630)
* hosts (netrc.netrc 的屬性):            netrc Objects.      (line   23)
* hosts() (ipaddress.IPv4Network 的方法): Network objects.   (line  136)
* hosts() (ipaddress.IPv6Network 的方法): Network objects.   (line  331)
* hour (datetime.datetime 的屬性):       datetime Objects.   (line  277)
* hour (datetime.time 的屬性):           time Objects.       (line   50)
* HRESULT (ctypes 中的類別):             Fundamental data types<2>.
                                                             (line  208)
* 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 --- Conversions between color systems.
                                                             (line   48)
* ht() (於 turtle 模組中):               Visibility.         (line    6)
* HTML:                                  html parser --- Simple HTML and XHTML parser.
                                                             (line    8)
* HTML <1>:                              urllib request Restrictions.
                                                             (line   29)
* html (模組):                           html --- HyperText Markup Language support.
                                                             (line    6)
* html() (於 cgitb 模組中):              cgitb --- Traceback manager for CGI scripts.
                                                             (line   57)
* html.entities (模組):                  html entities --- Definitions of HTML general entities.
                                                             (line    6)
* html.parser (模組):                    html parser --- Simple HTML and XHTML parser.
                                                             (line    6)
* html5 (於 html.entities 模組中):       html entities --- Definitions of HTML general entities.
                                                             (line   14)
* HTMLCalendar (calendar 中的類別):      calendar --- General calendar-related functions.
                                                             (line  163)
* HtmlDiff (difflib 中的類別):           difflib --- Helpers for computing deltas.
                                                             (line   81)
* HTMLParser (html.parser 中的類別):     html parser --- Simple HTML and XHTML parser.
                                                             (line   14)
* htonl() (於 socket 模組中):            Other functions<2>. (line  198)
* htons() (於 socket 模組中):            Other functions<2>. (line  205)
* HTTP (於 email.policy 模組中):         email policy Policy Objects.
                                                             (line  508)
* http (模組):                           http --- HTTP modules.
                                                             (line    6)
* http.client (模組):                    http client --- HTTP protocol client.
                                                             (line    6)
* http.cookiejar (模組):                 http cookiejar --- Cookie handling for HTTP clients.
                                                             (line    6)
* http.cookies (模組):                   http cookies --- HTTP state management.
                                                             (line    6)
* http.server (模組):                    http server --- HTTP servers.
                                                             (line    6)
* HTTP; http (standard module):          http --- HTTP modules.
                                                             (line    8)
* HTTP; http.client (standard module):   http client --- HTTP protocol client.
                                                             (line    8)
* HTTP; protocol:                        cgi --- Common Gateway Interface support.
                                                             (line    8)
* HTTP; protocol <1>:                    urllib request Restrictions.
                                                             (line    6)
* HTTP; protocol <2>:                    urllib request Restrictions.
                                                             (line   29)
* HTTP; protocol <3>:                    http --- HTTP modules.
                                                             (line    8)
* HTTP; protocol <4>:                    http client --- HTTP protocol client.
                                                             (line    8)
* HTTP; protocol <5>:                    http server --- HTTP servers.
                                                             (line    8)
* HTTPBasicAuthHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  354)
* HTTPConnection (http.client 中的類別): http client --- HTTP protocol client.
                                                             (line   26)
* HTTPCookieProcessor (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  285)
* httpd:                                 http server --- HTTP servers.
                                                             (line    8)
* HTTPDefaultErrorHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  276)
* HTTPDigestAuthHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  378)
* HTTPError:                             urllib error --- Exception classes raised by urllib request.
                                                             (line   30)
* HTTPErrorProcessor (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  438)
* HTTPException:                         http client --- HTTP protocol client.
                                                             (line  127)
* HTTPHandler (logging.handlers 中的類別): HTTPHandler.      (line   10)
* HTTPHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  402)
* HTTPPasswordMgr (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  311)
* HTTPPasswordMgrWithDefaultRealm (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  315)
* HTTPPasswordMgrWithPriorAuth (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  321)
* HTTPRedirectHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  281)
* HTTPResponse (http.client 中的類別):   http client --- HTTP protocol client.
                                                             (line   96)
* HTTPSConnection (http.client 中的類別): http client --- HTTP protocol client.
                                                             (line   57)
* HTTPServer (http.server 中的類別):     http server --- HTTP servers.
                                                             (line   25)
* HTTPSHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  406)
* HTTPStatus (http 中的類別):            http --- HTTP modules.
                                                             (line   28)
* https_open() (urllib.request.HTTPSHandler 的方法): HTTPSHandler Objects.
                                                             (line    6)
* HTTPS_PORT (於 http.client 模組中):    http client --- HTTP protocol client.
                                                             (line  200)
* https_response() (urllib.request.HTTPErrorProcessor 的方法): HTTPErrorProcessor Objects.
                                                             (line   18)
* http_error_301() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler Objects.
                                                             (line   35)
* http_error_302() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler Objects.
                                                             (line   42)
* http_error_303() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler Objects.
                                                             (line   48)
* http_error_307() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler Objects.
                                                             (line   54)
* http_error_401() (urllib.request.HTTPBasicAuthHandler 的方法): HTTPBasicAuthHandler Objects.
                                                             (line    6)
* http_error_401() (urllib.request.HTTPDigestAuthHandler 的方法): HTTPDigestAuthHandler Objects.
                                                             (line    6)
* http_error_407() (urllib.request.ProxyBasicAuthHandler 的方法): ProxyBasicAuthHandler Objects.
                                                             (line    6)
* http_error_407() (urllib.request.ProxyDigestAuthHandler 的方法): ProxyDigestAuthHandler Objects.
                                                             (line    6)
* http_error_auth_reqed() (urllib.request.AbstractBasicAuthHandler 的方法): AbstractBasicAuthHandler Objects.
                                                             (line    6)
* http_error_auth_reqed() (urllib.request.AbstractDigestAuthHandler 的方法): AbstractDigestAuthHandler Objects.
                                                             (line    6)
* http_error_default() (urllib.request.BaseHandler 的方法): BaseHandler Objects.
                                                             (line   65)
* http_open() (urllib.request.HTTPHandler 的方法): HTTPHandler Objects.
                                                             (line    6)
* HTTP_PORT (於 http.client 模組中):     http client --- HTTP protocol client.
                                                             (line  196)
* http_proxy:                            urllib request --- Extensible library for opening URLs.
                                                             (line   85)
* http_proxy <1>:                        Examples<21>.       (line   97)
* http_proxy <2>:                        Basic Authentication.
                                                             (line   62)
* http_response() (urllib.request.HTTPErrorProcessor 的方法): HTTPErrorProcessor Objects.
                                                             (line    6)
* http_version (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  299)
* hypot() (於 math 模組中):              Trigonometric functions.
                                                             (line   44)
* I (於 re 模組中):                      Module Contents.    (line   63)
* I/O control; buffering:                內建函式.           (line 1215)
* I/O control; buffering <1>:            Socket Objects.     (line  199)
* iadd() (於 operator 模組中):           In-place Operators. (line   36)
* iand() (於 operator 模組中):           In-place Operators. (line   41)
* iconcat() (於 operator 模組中):        In-place Operators. (line   46)
* id (ssl.SSLSession 的屬性):            SSL session.        (line   12)
* id() (unittest.TestCase 的方法):       Test cases.         (line  723)
* id() (內建函式):                       內建函式.           (line  764)
* idcok() (curses.window 的方法):        Window Objects.     (line  286)
* ident (select.kevent 的屬性):          Kevent Objects.     (line    8)
* ident (threading.Thread 的屬性):       Thread Objects.     (line  148)
* identchars (cmd.Cmd 的屬性):           Cmd Objects.        (line  127)
* identifier:                            Identifiers and keywords.
                                                             (line    6)
* identifier <1>:                        Identifiers Names.  (line    6)
* identify() (tkinter.ttk.Notebook 的方法): ttk Notebook.    (line   32)
* identify() (tkinter.ttk.Treeview 的方法): ttk Treeview.    (line  143)
* identify() (tkinter.ttk.Widget 的方法): ttk Widget.        (line   11)
* identify_column() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  153)
* identify_element() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  182)
* identify_region() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  160)
* identify_row() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  149)
* identity of an object:                 Objects values and types.
                                                             (line   11)
* identity; test:                        Membership test operations.
                                                             (line   40)
* idioms (2to3 fixer):                   Fixers.             (line  123)
* IDLE:                                  IDLE<54>.           (line    8)
* IDLE <1>:                              Glossary.           (line  599)
* IDLESTARTUP:                           IDLE<27>.           (line  176)
* IDLESTARTUP <1>:                       IDLE<31>.           (line    9)
* IDLESTARTUP <2>:                       IDLE<37>.           (line    9)
* IDLESTARTUP <3>:                       Startup and code execution.
                                                             (line    7)
* IDLE_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   73)
* idlok() (curses.window 的方法):        Window Objects.     (line  294)
* if; conditional expression:            Conditional expressions.
                                                             (line    6)
* if; in comprehensions:                 Displays for lists sets and dictionaries.
                                                             (line   14)
* ifloordiv() (於 operator 模組中):      In-place Operators. (line   52)
* if_indextoname() (於 socket 模組中):   Other functions<2>. (line  398)
* if_nameindex() (於 socket 模組中):     Other functions<2>. (line  355)
* if_nametoindex() (於 socket 模組中):   Other functions<2>. (line  380)
* iglob() (於 glob 模組中):              glob --- Unix style pathname pattern expansion.
                                                             (line   54)
* ignorableWhitespace() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line  150)
* ignore (pdb command):                  Debugger Commands.  (line  111)
* IGNORECASE (於 re 模組中):             Module Contents.    (line   63)
* ignore_errors() (於 codecs 模組中):    Error Handlers.     (line  140)
* IGNORE_EXCEPTION_DETAIL (於 doctest 模組中): Option Flags. (line   58)
* ignore_patterns() (於 shutil 模組中):  Directory and files operations.
                                                             (line  184)
* ihave() (nntplib.NNTP 的方法):         Methods<3>.         (line  291)
* IISCGIHandler (wsgiref.handlers 中的類別): wsgiref handlers -- server/gateway base classes.
                                                             (line   24)
* ilshift() (於 operator 模組中):        In-place Operators. (line   57)
* imag (numbers.Complex 的屬性):         The numeric tower.  (line   19)
* imaginary literal:                     Numeric literals.   (line    6)
* imap() (multiprocessing.pool.Pool 的方法): Process Pools.  (line  126)
* IMAP4 (imaplib 中的類別):              imaplib --- IMAP4 protocol client.
                                                             (line   20)
* IMAP4.abort:                           imaplib --- IMAP4 protocol client.
                                                             (line   48)
* IMAP4.error:                           imaplib --- IMAP4 protocol client.
                                                             (line   43)
* IMAP4.readonly:                        imaplib --- IMAP4 protocol client.
                                                             (line   55)
* IMAP4; protocol:                       imaplib --- IMAP4 protocol client.
                                                             (line    8)
* IMAP4_SSL (imaplib 中的類別):          imaplib --- IMAP4 protocol client.
                                                             (line   64)
* IMAP4_SSL; protocol:                   imaplib --- IMAP4 protocol client.
                                                             (line    8)
* IMAP4_stream (imaplib 中的類別):       imaplib --- IMAP4 protocol client.
                                                             (line   97)
* IMAP4_stream; protocol:                imaplib --- IMAP4 protocol client.
                                                             (line    8)
* imaplib (模組):                        imaplib --- IMAP4 protocol client.
                                                             (line    6)
* imap_unordered() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line  141)
* imatmul() (於 operator 模組中):        In-place Operators. (line   72)
* imghdr (模組):                         imghdr --- Determine the type of an image.
                                                             (line    6)
* immedok() (curses.window 的方法):      Window Objects.     (line  300)
* immutable:                             Glossary.           (line  605)
* 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; types:            Immutable Sequence Types.
                                                             (line    6)
* imod() (於 operator 模組中):           In-place Operators. (line   62)
* imp (模組):                            imp --- Access the import internals.
                                                             (line    6)
* ImpImporter (pkgutil 中的類別):        pkgutil --- Package extension utility.
                                                             (line   53)
* implementation (於 sys 模組中):        sys --- System-specific parameters and functions.
                                                             (line  892)
* ImpLoader (pkgutil 中的類別):          pkgutil --- Package extension utility.
                                                             (line   69)
* impl_detail() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  636)
* import (2to3 fixer):                   Fixers.             (line  139)
* import hooks:                          Import hooks.       (line    6)
* import machinery:                      The import system.  (line    6)
* import path:                           Glossary.           (line  613)
* importer:                              Glossary.           (line  626)
* ImportError:                           Concrete exceptions.
                                                             (line   38)
* importing:                             Glossary.           (line  621)
* importlib (模組):                      importlib --- The implementation of import.
                                                             (line    6)
* importlib.abc (模組):                  importlib abc -- Abstract base classes related to import.
                                                             (line    6)
* importlib.machinery (模組):            importlib machinery -- Importers and path hooks.
                                                             (line    6)
* importlib.metadata (模組):             Using importlib metadata.
                                                             (line    6)
* importlib.resources (模組):            importlib resources -- Resources.
                                                             (line    6)
* importlib.util (模組):                 importlib util -- Utility code for importers.
                                                             (line    6)
* imports (2to3 fixer):                  Fixers.             (line  143)
* imports2 (2to3 fixer):                 Fixers.             (line  147)
* ImportWarning:                         Warnings.           (line   46)
* import_fresh_module() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  732)
* IMPORT_FROM (opcode):                  Python Bytecode Instructions.
                                                             (line  643)
* import_module() (於 importlib 模組中): Functions<10>.      (line   15)
* import_module() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  717)
* IMPORT_NAME (opcode):                  Python Bytecode Instructions.
                                                             (line  634)
* IMPORT_STAR (opcode):                  Python Bytecode Instructions.
                                                             (line  366)
* ImproperConnectionState:               http client --- HTTP protocol client.
                                                             (line  157)
* imul() (於 operator 模組中):           In-place Operators. (line   67)
* inch() (curses.window 的方法):         Window Objects.     (line  308)
* inclusive (tracemalloc.DomainFilter 的屬性): DomainFilter. (line   12)
* inclusive (tracemalloc.Filter 的屬性): Filter.             (line   38)
* inclusive; or:                         Binary bitwise operations.
                                                             (line   18)
* Incomplete:                            binascii --- Convert between binary and ASCII.
                                                             (line  176)
* IncompleteRead:                        http client --- HTTP protocol client.
                                                             (line  153)
* IncompleteReadError:                   Exceptions<8>.      (line   42)
* IncrementalDecoder (codecs 中的類別):  IncrementalDecoder Objects.
                                                             (line   11)
* incrementaldecoder (codecs.CodecInfo 的屬性): codecs --- Codec registry and base classes.
                                                             (line   78)
* IncrementalEncoder (codecs 中的類別):  IncrementalEncoder Objects.
                                                             (line   11)
* incrementalencoder (codecs.CodecInfo 的屬性): codecs --- Codec registry and base classes.
                                                             (line   78)
* IncrementalNewlineDecoder (io 中的類別): Text I/O<2>.      (line  233)
* IncrementalParser (xml.sax.xmlreader 中的類別): xml sax xmlreader --- Interface for XML parsers.
                                                             (line   20)
* increment_lineno() (於 ast 模組中):    ast Helpers.        (line   90)
* incr_item():                           Exceptions<16>.     (line   78)
* incr_item() <1>:                       Exceptions<16>.     (line  123)
* indent (doctest.Example 的屬性):       Example Objects.    (line   47)
* INDENT (於 token 模組中):              token --- Constants used with Python parse trees.
                                                             (line   50)
* INDENT token:                          Indentation.        (line   33)
* indent() (於 textwrap 模組中):         textwrap --- Text wrapping and filling.
                                                             (line   91)
* indentation:                           Indentation.        (line    6)
* IndentationError:                      Concrete exceptions.
                                                             (line  275)
* index operation:                       The standard type hierarchy.
                                                             (line  127)
* index() (array.array 的方法):          array --- 高效率的數值型態陣列.
                                                             (line  173)
* index() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line   99)
* index() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line   99)
* index() (collections.deque 的方法):    deque objects.      (line   70)
* index() (multiprocessing.shared_memory.ShareableList 的方法): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line  268)
* index() (sequence method):             Common Sequence Operations.
                                                             (line   21)
* index() (str 的方法):                  String Methods<2>.  (line  161)
* index() (tkinter.ttk.Notebook 的方法): ttk Notebook.       (line   37)
* index() (tkinter.ttk.Treeview 的方法): ttk Treeview.       (line  188)
* index() (於 operator 模組中):          operator --- Standard operators as functions.
                                                             (line   93)
* IndexError:                            Concrete exceptions.
                                                             (line   59)
* indexOf() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  197)
* IndexSizeErr:                          Exceptions<14>.     (line   34)
* indices() (slice 的方法):              The standard type hierarchy.
                                                             (line  814)
* inet_aton() (於 socket 模組中):        Other functions<2>. (line  218)
* inet_ntoa() (於 socket 模組中):        Other functions<2>. (line  238)
* inet_ntop() (於 socket 模組中):        Other functions<2>. (line  273)
* inet_pton() (於 socket 模組中):        Other functions<2>. (line  254)
* Inexact (decimal 中的類別):            Signals.            (line   42)
* inf (於 cmath 模組中):                 Constants<3>.       (line   20)
* inf (於 math 模組中):                  Constants<2>.       (line   26)
* infile (shlex.shlex 的屬性):           shlex Objects.      (line  139)
* Infinity:                              內建函式.           (line  583)
* infj (於 cmath 模組中):                Constants<3>.       (line   26)
* info() (dis.Bytecode 的方法):          Bytecode analysis.  (line   53)
* info() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   78)
* info() (logging.Logger 的方法):        Logger Objects.     (line  215)
* info() (於 logging 模組中):            Module-Level Functions.
                                                             (line  119)
* infolist() (zipfile.ZipFile 的方法):   ZipFile Objects.    (line   98)
* inheritance:                           Class definitions.  (line    6)
* ini file:                              configparser --- Configuration file parser.
                                                             (line    8)
* init() (於 mimetypes 模組中):          mimetypes --- Map filenames to MIME types.
                                                             (line   78)
* inited (於 mimetypes 模組中):          mimetypes --- Map filenames to MIME types.
                                                             (line  116)
* initgroups() (於 os 模組中):           Process Parameters. (line  306)
* initialize_options() (distutils.cmd.Command 的方法): Creating a new Distutils command.
                                                             (line   21)
* initial_indent (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  199)
* initproc (C 型態):                     Slot Type typedefs. (line   45)
* initscr() (於 curses 模組中):          Functions<3>.       (line  229)
* init_color() (於 curses 模組中):       Functions<3>.       (line  204)
* init_database() (於 msilib 模組中):    msilib --- Read and write Microsoft Installer files.
                                                             (line   60)
* init_pair() (於 curses 模組中):        Functions<3>.       (line  216)
* inode() (os.DirEntry 的方法):          Files and Directories.
                                                             (line  865)
* INPLACE_ADD (opcode):                  Python Bytecode Instructions.
                                                             (line  222)
* INPLACE_AND (opcode):                  Python Bytecode Instructions.
                                                             (line  238)
* INPLACE_FLOOR_DIVIDE (opcode):         Python Bytecode Instructions.
                                                             (line  210)
* INPLACE_LSHIFT (opcode):               Python Bytecode Instructions.
                                                             (line  230)
* INPLACE_MATRIX_MULTIPLY (opcode):      Python Bytecode Instructions.
                                                             (line  204)
* INPLACE_MODULO (opcode):               Python Bytecode Instructions.
                                                             (line  218)
* INPLACE_MULTIPLY (opcode):             Python Bytecode Instructions.
                                                             (line  200)
* INPLACE_OR (opcode):                   Python Bytecode Instructions.
                                                             (line  246)
* INPLACE_POWER (opcode):                Python Bytecode Instructions.
                                                             (line  196)
* INPLACE_RSHIFT (opcode):               Python Bytecode Instructions.
                                                             (line  234)
* INPLACE_SUBTRACT (opcode):             Python Bytecode Instructions.
                                                             (line  226)
* INPLACE_TRUE_DIVIDE (opcode):          Python Bytecode Instructions.
                                                             (line  214)
* INPLACE_XOR (opcode):                  Python Bytecode Instructions.
                                                             (line  242)
* input:                                 Expression input.   (line    6)
* input (2to3 fixer):                    Fixers.             (line  153)
* input() (內建函式):                    內建函式.           (line  777)
* input() (於 fileinput 模組中):         fileinput --- Iterate over lines from multiple input streams.
                                                             (line   54)
* InputOnly (tkinter.tix 中的類別):      Miscellaneous Widgets.
                                                             (line    6)
* InputSource (xml.sax.xmlreader 中的類別): xml sax xmlreader --- Interface for XML parsers.
                                                             (line   51)
* input_charset (email.charset.Charset 的屬性): email charset Representing character sets.
                                                             (line   53)
* input_codec (email.charset.Charset 的屬性): email charset Representing character sets.
                                                             (line   82)
* inquiry (C 型態):                      Supporting Cyclic Garbage Collection.
                                                             (line  133)
* insch() (curses.window 的方法):        Window Objects.     (line  314)
* insdelln() (curses.window 的方法):     Window Objects.     (line  321)
* insert() (array.array 的方法):         array --- 高效率的數值型態陣列.
                                                             (line  177)
* insert() (collections.deque 的方法):   deque objects.      (line   78)
* insert() (sequence method):            Mutable Sequence Types.
                                                             (line   16)
* insert() (tkinter.ttk.Notebook 的方法): ttk Notebook.      (line   42)
* insert() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line  193)
* insert() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  140)
* insertBefore() (xml.dom.Node 的方法):  Node Objects.       (line  121)
* insertln() (curses.window 的方法):     Window Objects.     (line  329)
* insert_text() (於 readline 模組中):    Line buffer.        (line   13)
* insnstr() (curses.window 的方法):      Window Objects.     (line  334)
* insort() (於 bisect 模組中):           bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   47)
* insort_left() (於 bisect 模組中):      bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   40)
* insort_right() (於 bisect 模組中):     bisect --- 陣列二分演算法 Array bisection algorithm.
                                                             (line   47)
* inspect (模組):                        inspect --- Inspect live objects.
                                                             (line    6)
* inspect command line option; –details: Command Line Interface<3>.
                                                             (line   13)
* InspectLoader (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  371)
* insstr() (curses.window 的方法):       Window Objects.     (line  345)
* install() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line  100)
* install() (於 gettext 模組中):         Class-based API.    (line   72)
* installHandler() (於 unittest 模組中): Signal Handling.    (line   29)
* install_opener() (於 urllib.request 模組中): urllib request --- Extensible library for opening URLs.
                                                             (line  116)
* install_scripts() (venv.EnvBuilder 的方法): API<2>.        (line  125)
* instance; call:                        Calls.              (line  147)
* instate() (tkinter.ttk.Widget 的方法): ttk Widget.         (line   18)
* instr() (curses.window 的方法):        Window Objects.     (line  355)
* instream (shlex.shlex 的屬性):         shlex Objects.      (line  145)
* Instruction (dis 中的類別):            Python Bytecode Instructions.
                                                             (line   10)
* Instruction.arg (於 dis 模組中):       Python Bytecode Instructions.
                                                             (line   24)
* Instruction.argrepr (於 dis 模組中):   Python Bytecode Instructions.
                                                             (line   32)
* Instruction.argval (於 dis 模組中):    Python Bytecode Instructions.
                                                             (line   28)
* Instruction.is_jump_target (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   44)
* Instruction.offset (於 dis 模組中):    Python Bytecode Instructions.
                                                             (line   36)
* Instruction.opcode (於 dis 模組中):    Python Bytecode Instructions.
                                                             (line   14)
* Instruction.opname (於 dis 模組中):    Python Bytecode Instructions.
                                                             (line   20)
* Instruction.starts_line (於 dis 模組中): Python Bytecode Instructions.
                                                             (line   40)
* int (uuid.UUID 的屬性):                uuid --- UUID objects according to RFC 4122.
                                                             (line  131)
* int (內建類別):                        內建函式.           (line  800)
* Int2AP() (於 imaplib 模組中):          imaplib --- IMAP4 protocol client.
                                                             (line  111)
* integer:                               The standard type hierarchy.
                                                             (line  156)
* integer literal:                       Numeric literals.   (line    6)
* integer; literals:                     Numeric Types --- int float complex.
                                                             (line   19)
* integer; representation:               The standard type hierarchy.
                                                             (line  101)
* Integral (numbers 中的類別):           The numeric tower.  (line   55)
* Integrated Development Environment:    IDLE<54>.           (line    8)
* IntegrityError:                        Exceptions<3>.      (line   19)
* Intel/DVI ADPCM:                       audioop --- Manipulate raw audio data.
                                                             (line   17)
* IntEnum (enum 中的類別):               Module Contents<2>. (line   16)
* interact (pdb command):                Debugger Commands.  (line  275)
* interact() (code.InteractiveConsole 的方法): Interactive Console Objects.
                                                             (line   10)
* interact() (telnetlib.Telnet 的方法):  Telnet Objects.     (line  113)
* interact() (於 code 模組中):           code --- Interpreter base classes.
                                                             (line   32)
* interactive:                           Glossary.           (line  631)
* interactive mode:                      Complete Python programs.
                                                             (line   19)
* InteractiveConsole (code 中的類別):    code --- Interpreter base classes.
                                                             (line   25)
* InteractiveInterpreter (code 中的類別): code --- Interpreter base classes.
                                                             (line   15)
* intern (2to3 fixer):                   Fixers.             (line  157)
* intern() (於 sys 模組中):              sys --- System-specific parameters and functions.
                                                             (line  969)
* internal type:                         The standard type hierarchy.
                                                             (line  644)
* Internaldate2tuple() (於 imaplib 模組中): imaplib --- IMAP4 protocol client.
                                                             (line  105)
* internalSubset (xml.dom.DocumentType 的屬性): DocumentType Objects.
                                                             (line   27)
* internal_attr (zipfile.ZipInfo 的屬性): ZipInfo Objects.   (line  123)
* Internet:                              Internet Protocols and Support.
                                                             (line    6)
* interpolated string literal:           String literal concatenation.
                                                             (line   24)
* interpolation, string (%):             printf-style String Formatting.
                                                             (line    6)
* interpolation; bytearray (%):          printf-style Bytes Formatting.
                                                             (line    6)
* interpolation; bytes (%):              printf-style Bytes Formatting.
                                                             (line    6)
* InterpolationDepthError:               Exceptions<4>.      (line   42)
* InterpolationError:                    Exceptions<4>.      (line   37)
* InterpolationMissingOptionError:       Exceptions<4>.      (line   49)
* InterpolationSyntaxError:              Exceptions<4>.      (line   54)
* interpreted:                           Glossary.           (line  640)
* interpreter:                           Top-level components.
                                                             (line    6)
* interpreter lock:                      Thread State and the Global Interpreter Lock.
                                                             (line    6)
* interpreter prompts:                   sys --- System-specific parameters and functions.
                                                             (line 1189)
* interpreter shutdown:                  Glossary.           (line  650)
* interpreter_requires_environment() (於 test.support.script_helper 模組中): test support script_helper --- Utilities for the Python execution tests.
                                                             (line    9)
* interrupt() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line  187)
* InterruptedError:                      OS exceptions.      (line   71)
* interrupt_main() (於 _thread 模組中):  _thread --- Low-level threading API.
                                                             (line   52)
* intersection() (frozenset 的方法):     Set Types --- set frozenset.
                                                             (line  102)
* intersection_update() (frozenset 的方法): Set Types --- set frozenset.
                                                             (line  175)
* IntFlag (enum 中的類別):               Module Contents<2>. (line   21)
* intro (cmd.Cmd 的屬性):                Cmd Objects.        (line  142)
* int_info (於 sys 模組中):              sys --- System-specific parameters and functions.
                                                             (line  935)
* InuseAttributeErr:                     Exceptions<14>.     (line   39)
* inv() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line   98)
* InvalidAccessErr:                      Exceptions<14>.     (line   44)
* invalidate_caches() (importlib.abc.MetaPathFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line   85)
* invalidate_caches() (importlib.abc.PathEntryFinder 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  148)
* invalidate_caches() (importlib.machinery.FileFinder 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  194)
* invalidate_caches() (importlib.machinery.PathFinder 的類別成員): importlib machinery -- Importers and path hooks.
                                                             (line  139)
* invalidate_caches() (於 importlib 模組中): Functions<10>.  (line   61)
* InvalidCharacterErr:                   Exceptions<14>.     (line   49)
* InvalidModificationErr:                Exceptions<14>.     (line   57)
* InvalidOperation (decimal 中的類別):   Signals.            (line   50)
* InvalidStateErr:                       Exceptions<14>.     (line   61)
* InvalidStateError:                     Exception classes.  (line   22)
* InvalidStateError <1>:                 Exceptions<8>.      (line   28)
* InvalidURL:                            http client --- HTTP protocol client.
                                                             (line  136)
* inversion:                             Unary arithmetic and bitwise operations.
                                                             (line   15)
* invert() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line   98)
* invocation:                            The standard type hierarchy.
                                                             (line  291)
* inv_cdf() (statistics.NormalDist 的方法): NormalDist objects.
                                                             (line   86)
* in_dll() (ctypes._CData 的方法):       Data types.         (line   63)
* in_table_a1() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line   40)
* in_table_b1() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line   45)
* in_table_c11() (於 stringprep 模組中): stringprep --- Internet String Preparation.
                                                             (line   60)
* in_table_c11_c12() (於 stringprep 模組中): stringprep --- Internet String Preparation.
                                                             (line   69)
* in_table_c12() (於 stringprep 模組中): stringprep --- Internet String Preparation.
                                                             (line   64)
* in_table_c21() (於 stringprep 模組中): stringprep --- Internet String Preparation.
                                                             (line   74)
* in_table_c21_c22() (於 stringprep 模組中): stringprep --- Internet String Preparation.
                                                             (line   84)
* in_table_c22() (於 stringprep 模組中): stringprep --- Internet String Preparation.
                                                             (line   79)
* in_table_c3() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line   89)
* in_table_c4() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line   93)
* in_table_c5() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line   98)
* in_table_c6() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line  102)
* in_table_c7() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line  107)
* in_table_c8() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line  112)
* in_table_c9() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line  117)
* in_table_d1() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line  121)
* in_table_d2() (於 stringprep 模組中):  stringprep --- Internet String Preparation.
                                                             (line  126)
* in_transaction (sqlite3.Connection 的屬性): Connection Objects.
                                                             (line   18)
* IO (typing 中的類別):                  Classes functions and decorators.
                                                             (line  470)
* io (模組):                             io --- Core tools for working with streams.
                                                             (line    6)
* IOBase (io 中的類別):                  I/O Base Classes.   (line    6)
* ioctl() (socket.socket 的方法):        Socket Objects.     (line  168)
* ioctl() (於 fcntl 模組中):             fcntl --- The fcntl and ioctl system calls.
                                                             (line   54)
* IOCTL_VM_SOCKETS_GET_LOCAL_CID (於 socket 模組中): Constants<8>.
                                                             (line  194)
* IOError:                               Concrete exceptions.
                                                             (line  413)
* ior() (於 operator 模組中):            In-place Operators. (line   79)
* IO_REPARSE_TAG_APPEXECLINK (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  418)
* IO_REPARSE_TAG_MOUNT_POINT (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  418)
* IO_REPARSE_TAG_SYMLINK (於 stat 模組中): stat --- Interpreting stat results.
                                                             (line  418)
* ip (ipaddress.IPv4Interface 的屬性):   Interface objects.  (line   19)
* ip (ipaddress.IPv6Interface 的屬性):   Interface objects.  (line   74)
* ipaddress (模組):                      ipaddress --- IPv4/IPv6 manipulation library.
                                                             (line    6)
* ipow() (於 operator 模組中):           In-place Operators. (line   84)
* IPv4Address (ipaddress 中的類別):      Address objects.    (line   13)
* IPv4Interface (ipaddress 中的類別):    Interface objects.  (line    9)
* IPv4Network (ipaddress 中的類別):      Network objects.    (line   13)
* ipv4_mapped (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  195)
* IPv6Address (ipaddress 中的類別):      Address objects.    (line  124)
* IPv6Interface (ipaddress 中的類別):    Interface objects.  (line   64)
* IPv6Network (ipaddress 中的類別):      Network objects.    (line  253)
* IPV6_ENABLED (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line   83)
* ip_address() (於 ipaddress 模組中):    Convenience factory functions.
                                                             (line    9)
* ip_interface() (於 ipaddress 模組中):  Convenience factory functions.
                                                             (line   37)
* ip_network() (於 ipaddress 模組中):    Convenience factory functions.
                                                             (line   23)
* irshift() (於 operator 模組中):        In-place Operators. (line   89)
* isabs() (於 os.path 模組中):           os path --- Common pathname manipulations.
                                                             (line  203)
* isabstract() (於 inspect 模組中):      Types and members.  (line  418)
* IsADirectoryError:                     OS exceptions.      (line   81)
* isalnum() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  440)
* isalnum() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  440)
* isalnum() (str 的方法):                String Methods<2>.  (line  166)
* isalnum() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  131)
* isalpha() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  458)
* isalpha() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  458)
* isalpha() (str 的方法):                String Methods<2>.  (line  173)
* isalpha() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  136)
* isascii() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  473)
* isascii() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  473)
* isascii() (str 的方法):                String Methods<2>.  (line  183)
* isascii() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  141)
* isasyncgen() (於 inspect 模組中):      Types and members.  (line  388)
* isasyncgenfunction() (於 inspect 模組中): Types and members.
                                                             (line  371)
* isatty() (chunk.Chunk 的方法):         chunk --- Read IFF chunked data.
                                                             (line   88)
* isatty() (io.IOBase 的方法):           I/O Base Classes.   (line   74)
* isatty() (於 os 模組中):               File Descriptor Operations.
                                                             (line  208)
* isawaitable() (於 inspect 模組中):     Types and members.  (line  352)
* isblank() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  145)
* isblk() (tarfile.TarInfo 的方法):      TarInfo Objects.    (line  120)
* isbuiltin() (於 inspect 模組中):       Types and members.  (line  408)
* ischr() (tarfile.TarInfo 的方法):      TarInfo Objects.    (line  116)
* isclass() (於 inspect 模組中):         Types and members.  (line  308)
* isclose() (於 cmath 模組中):           Classification functions.
                                                             (line   23)
* isclose() (於 math 模組中):            Number-theoretic and representation functions.
                                                             (line  104)
* iscntrl() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  149)
* iscode() (於 inspect 模組中):          Types and members.  (line  404)
* iscoroutine() (於 asyncio 模組中):     Generator-based Coroutines.
                                                             (line   36)
* iscoroutine() (於 inspect 模組中):     Types and members.  (line  345)
* iscoroutinefunction() (於 asyncio 模組中): Generator-based Coroutines.
                                                             (line   43)
* iscoroutinefunction() (於 inspect 模組中): Types and members.
                                                             (line  334)
* isctrl() (於 curses.ascii 模組中):     curses ascii --- Utilities for ASCII characters.
                                                             (line  190)
* isDaemon() (threading.Thread 的方法):  Thread Objects.     (line  197)
* isdatadescriptor() (於 inspect 模組中): Types and members. (line  440)
* isdecimal() (str 的方法):              String Methods<2>.  (line  191)
* isdev() (tarfile.TarInfo 的方法):      TarInfo Objects.    (line  128)
* isdigit() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  481)
* isdigit() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  481)
* isdigit() (str 的方法):                String Methods<2>.  (line  199)
* isdigit() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  154)
* isdir() (tarfile.TarInfo 的方法):      TarInfo Objects.    (line  104)
* isdir() (於 os.path 模組中):           os path --- Common pathname manipulations.
                                                             (line  219)
* isdisjoint() (frozenset 的方法):       Set Types --- set frozenset.
                                                             (line   68)
* isdown() (於 turtle 模組中):           Drawing state.      (line   86)
* iselement() (於 xml.etree.ElementTree 模組中): Functions<6>.
                                                             (line  117)
* isenabled() (於 gc 模組中):            gc --- Garbage Collector interface.
                                                             (line   30)
* isEnabledFor() (logging.Logger 的方法): Logger Objects.    (line   89)
* isendwin() (於 curses 模組中):         Functions<3>.       (line  242)
* ISEOF() (於 token 模組中):             token --- Constants used with Python parse trees.
                                                             (line   34)
* isexpr() (parser.ST 的方法):           ST Objects.         (line   21)
* isexpr() (於 parser 模組中):           Queries on ST Objects.
                                                             (line   12)
* isfifo() (tarfile.TarInfo 的方法):     TarInfo Objects.    (line  124)
* isfile() (tarfile.TarInfo 的方法):     TarInfo Objects.    (line   96)
* isfile() (於 os.path 模組中):          os path --- Common pathname manipulations.
                                                             (line  211)
* isfinite() (於 cmath 模組中):          Classification functions.
                                                             (line    6)
* isfinite() (於 math 模組中):           Number-theoretic and representation functions.
                                                             (line  137)
* isfirstline() (於 fileinput 模組中):   fileinput --- Iterate over lines from multiple input streams.
                                                             (line  106)
* isframe() (於 inspect 模組中):         Types and members.  (line  400)
* isfunction() (於 inspect 模組中):      Types and members.  (line  317)
* isfuture() (於 asyncio 模組中):        Future Functions.   (line    6)
* isgenerator() (於 inspect 模組中):     Types and members.  (line  330)
* isgeneratorfunction() (於 inspect 模組中): Types and members.
                                                             (line  322)
* isgetsetdescriptor() (於 inspect 模組中): Types and members.
                                                             (line  453)
* isgraph() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  159)
* isidentifier() (str 的方法):           String Methods<2>.  (line  209)
* isinf() (於 cmath 模組中):             Classification functions.
                                                             (line   13)
* isinf() (於 math 模組中):              Number-theoretic and representation functions.
                                                             (line  144)
* isinstance (2to3 fixer):               Fixers.             (line  161)
* isinstance() (內建函式):               內建函式.           (line  841)
* iskeyword() (於 keyword 模組中):       keyword --- Testing for Python keywords.
                                                             (line   13)
* isleap() (於 calendar 模組中):         calendar --- General calendar-related functions.
                                                             (line  301)
* islice() (於 itertools 模組中):        Itertool functions. (line  355)
* islink() (於 os.path 模組中):          os path --- Common pathname manipulations.
                                                             (line  227)
* islnk() (tarfile.TarInfo 的方法):      TarInfo Objects.    (line  112)
* islower() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  495)
* islower() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  495)
* islower() (str 的方法):                String Methods<2>.  (line  227)
* islower() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  163)
* ismemberdescriptor() (於 inspect 模組中): Types and members.
                                                             (line  462)
* ismeta() (於 curses.ascii 模組中):     curses ascii --- Utilities for ASCII characters.
                                                             (line  194)
* ismethod() (於 inspect 模組中):        Types and members.  (line  313)
* ismethoddescriptor() (於 inspect 模組中): Types and members.
                                                             (line  422)
* ismodule() (於 inspect 模組中):        Types and members.  (line  304)
* ismount() (於 os.path 模組中):         os path --- Common pathname manipulations.
                                                             (line  235)
* isnan() (於 cmath 模組中):             Classification functions.
                                                             (line   18)
* isnan() (於 math 模組中):              Number-theoretic and representation functions.
                                                             (line  149)
* ISNONTERMINAL() (於 token 模組中):     token --- Constants used with Python parse trees.
                                                             (line   30)
* isnumeric() (str 的方法):              String Methods<2>.  (line  233)
* isocalendar() (datetime.date 的方法):  date Objects.       (line  213)
* isocalendar() (datetime.datetime 的方法): datetime Objects.
                                                             (line  593)
* isoformat() (datetime.date 的方法):    date Objects.       (line  236)
* isoformat() (datetime.datetime 的方法): datetime Objects.  (line  598)
* isoformat() (datetime.time 的方法):    time Objects.       (line  151)
* IsolatedAsyncioTestCase (unittest 中的類別): Test cases.   (line  805)
* isolation_level (sqlite3.Connection 的屬性): Connection Objects.
                                                             (line   11)
* isoweekday() (datetime.date 的方法):   date Objects.       (line  206)
* isoweekday() (datetime.datetime 的方法): datetime Objects. (line  587)
* isprint() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  167)
* isprintable() (str 的方法):            String Methods<2>.  (line  243)
* ispunct() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  171)
* isqrt() (於 math 模組中):              Number-theoretic and representation functions.
                                                             (line  154)
* isreadable() (pprint.PrettyPrinter 的方法): PrettyPrinter Objects.
                                                             (line   24)
* isreadable() (於 pprint 模組中):       pprint --- Data pretty printer.
                                                             (line  130)
* isrecursive() (pprint.PrettyPrinter 的方法): PrettyPrinter Objects.
                                                             (line   32)
* isrecursive() (於 pprint 模組中):      pprint --- Data pretty printer.
                                                             (line  139)
* isreg() (tarfile.TarInfo 的方法):      TarInfo Objects.    (line  100)
* isReservedKey() (http.cookies.Morsel 的方法): Morsel Objects.
                                                             (line   68)
* isroutine() (於 inspect 模組中):       Types and members.  (line  413)
* isSameNode() (xml.dom.Node 的方法):    Node Objects.       (line  102)
* isspace() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  512)
* isspace() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  512)
* isspace() (str 的方法):                String Methods<2>.  (line  255)
* isspace() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  176)
* isstdin() (於 fileinput 模組中):       fileinput --- Iterate over lines from multiple input streams.
                                                             (line  111)
* issubclass() (內建函式):               內建函式.           (line  852)
* issubset() (frozenset 的方法):         Set Types --- set frozenset.
                                                             (line   74)
* issuite() (parser.ST 的方法):          ST Objects.         (line   25)
* issuite() (於 parser 模組中):          Queries on ST Objects.
                                                             (line   22)
* issuperset() (frozenset 的方法):       Set Types --- set frozenset.
                                                             (line   85)
* issym() (tarfile.TarInfo 的方法):      TarInfo Objects.    (line  108)
* ISTERMINAL() (於 token 模組中):        token --- Constants used with Python parse trees.
                                                             (line   26)
* istitle() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  520)
* istitle() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  520)
* istitle() (str 的方法):                String Methods<2>.  (line  265)
* istraceback() (於 inspect 模組中):     Types and members.  (line  396)
* isub() (於 operator 模組中):           In-place Operators. (line   94)
* isupper() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  534)
* isupper() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  534)
* isupper() (str 的方法):                String Methods<2>.  (line  272)
* isupper() (於 curses.ascii 模組中):    curses ascii --- Utilities for ASCII characters.
                                                             (line  181)
* isvisible() (於 turtle 模組中):        Visibility.         (line   22)
* isxdigit() (於 curses.ascii 模組中):   curses ascii --- Utilities for ASCII characters.
                                                             (line  185)
* is_() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line   63)
* is_absolute() (pathlib.PurePath 的方法): Methods and properties.
                                                             (line  165)
* is_active() (asyncio.AbstractChildWatcher 的方法): Process Watchers.
                                                             (line   68)
* is_alive() (multiprocessing.Process 的方法): Process and exceptions.
                                                             (line   79)
* is_alive() (threading.Thread 的方法):  Thread Objects.     (line  175)
* is_android (於 test.support 模組中):   test support --- Utilities for the Python test suite.
                                                             (line   40)
* is_annotated() (symtable.Symbol 的方法): Examining Symbol Tables.
                                                             (line  142)
* is_assigned() (symtable.Symbol 的方法): Examining Symbol Tables.
                                                             (line  153)
* is_attachment() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  444)
* is_authenticated() (urllib.request.HTTPPasswordMgrWithPriorAuth 的方法): HTTPPasswordMgrWithPriorAuth Objects.
                                                             (line   30)
* is_blocked() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy Objects.
                                                             (line   60)
* is_block_device() (pathlib.Path 的方法): Methods<2>.       (line  169)
* is_canonical() (decimal.Context 的方法): Context objects.  (line  292)
* is_canonical() (decimal.Decimal 的方法): Decimal objects.  (line  277)
* IS_CHARACTER_JUNK() (於 difflib 模組中): difflib --- Helpers for computing deltas.
                                                             (line  366)
* is_char_device() (pathlib.Path 的方法): Methods<2>.        (line  178)
* is_check_supported() (於 lzma 模組中): Miscellaneous<2>.   (line    6)
* is_closed() (asyncio.loop 的方法):     Running and stopping the loop.
                                                             (line   39)
* is_closing() (asyncio.BaseTransport 的方法): Base Transport.
                                                             (line   16)
* is_closing() (asyncio.StreamWriter 的方法): StreamWriter.  (line   81)
* is_dataclass() (於 dataclasses 模組中): Module-level decorators classes and functions.
                                                             (line  373)
* is_declared_global() (symtable.Symbol 的方法): Examining Symbol Tables.
                                                             (line  133)
* is_dir() (os.DirEntry 的方法):         Files and Directories.
                                                             (line  876)
* is_dir() (pathlib.Path 的方法):        Methods<2>.         (line  114)
* is_dir() (zipfile.Path 的方法):        Path Objects.       (line   40)
* is_dir() (zipfile.ZipInfo 的方法):     ZipInfo Objects.    (line   42)
* is_enabled() (於 faulthandler 模組中): Fault handler state.
                                                             (line   27)
* is_expired() (http.cookiejar.Cookie 的方法): Cookie Objects<2>.
                                                             (line  109)
* is_fifo() (pathlib.Path 的方法):       Methods<2>.         (line  161)
* is_file() (os.DirEntry 的方法):        Files and Directories.
                                                             (line  905)
* is_file() (pathlib.Path 的方法):       Methods<2>.         (line  123)
* is_file() (zipfile.Path 的方法):       Path Objects.       (line   44)
* is_finalizing() (於 sys 模組中):       sys --- System-specific parameters and functions.
                                                             (line  984)
* is_finite() (decimal.Context 的方法):  Context objects.    (line  296)
* is_finite() (decimal.Decimal 的方法):  Decimal objects.    (line  284)
* is_free() (symtable.Symbol 的方法):    Examining Symbol Tables.
                                                             (line  148)
* is_global (ipaddress.IPv4Address 的屬性): Address objects. (line   97)
* is_global (ipaddress.IPv6Address 的屬性): Address objects. (line  175)
* is_global() (symtable.Symbol 的方法):  Examining Symbol Tables.
                                                             (line  125)
* is_hop_by_hop() (於 wsgiref.util 模組中): wsgiref util -- WSGI environment utilities.
                                                             (line  109)
* is_imported() (symtable.Symbol 的方法): Examining Symbol Tables.
                                                             (line  116)
* is_infinite() (decimal.Context 的方法): Context objects.   (line  300)
* is_infinite() (decimal.Decimal 的方法): Decimal objects.   (line  289)
* is_integer() (float 的方法):           Additional Methods on Float.
                                                             (line   16)
* is_jython (於 test.support 模組中):    test support --- Utilities for the Python test suite.
                                                             (line   36)
* is_linetouched() (curses.window 的方法): Window Objects.   (line  365)
* IS_LINE_JUNK() (於 difflib 模組中):    difflib --- Helpers for computing deltas.
                                                             (line  359)
* is_link_local (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line  119)
* is_link_local (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   80)
* is_link_local (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  183)
* is_link_local (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  307)
* is_local() (symtable.Symbol 的方法):   Examining Symbol Tables.
                                                             (line  138)
* is_loopback (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line  114)
* is_loopback (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   78)
* is_loopback (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  181)
* is_loopback (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  305)
* is_mount() (pathlib.Path 的方法):      Methods<2>.         (line  132)
* is_multicast (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line   86)
* is_multicast (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   70)
* is_multicast (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  171)
* is_multicast (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  297)
* is_multipart() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  132)
* is_multipart() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  145)
* is_namespace() (symtable.Symbol 的方法): Examining Symbol Tables.
                                                             (line  157)
* is_nan() (decimal.Context 的方法):     Context objects.    (line  304)
* is_nan() (decimal.Decimal 的方法):     Decimal objects.    (line  294)
* is_nested() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   35)
* is_nonlocal() (symtable.Symbol 的方法): Examining Symbol Tables.
                                                             (line  129)
* is_normal() (decimal.Context 的方法):  Context objects.    (line  309)
* is_normal() (decimal.Decimal 的方法):  Decimal objects.    (line  299)
* is_normalized() (於 unicodedata 模組中): unicodedata --- Unicode Database.
                                                             (line  117)
* is_not() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line   67)
* is_not_allowed() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy Objects.
                                                             (line   74)
* is_optimized() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   31)
* is_package() (importlib.abc.InspectLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  402)
* is_package() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  589)
* is_package() (importlib.machinery.ExtensionFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  325)
* is_package() (importlib.machinery.SourceFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  224)
* is_package() (importlib.machinery.SourcelessFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  268)
* is_package() (zipimport.zipimporter 的方法): zipimporter Objects.
                                                             (line   56)
* is_parameter() (symtable.Symbol 的方法): Examining Symbol Tables.
                                                             (line  121)
* is_private (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line   91)
* is_private (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   72)
* is_private (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  173)
* is_private (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  299)
* is_python_build() (於 sysconfig 模組中): Other functions<3>.
                                                             (line   50)
* is_qnan() (decimal.Context 的方法):    Context objects.    (line  314)
* is_qnan() (decimal.Decimal 的方法):    Decimal objects.    (line  305)
* is_reading() (asyncio.ReadTransport 的方法): Read-only Transports.
                                                             (line    6)
* is_referenced() (symtable.Symbol 的方法): Examining Symbol Tables.
                                                             (line  112)
* is_reserved (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line  110)
* is_reserved (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   76)
* is_reserved (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  179)
* is_reserved (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  303)
* is_reserved() (pathlib.PurePath 的方法): Methods and properties.
                                                             (line  184)
* is_resource() (importlib.abc.ResourceReader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  324)
* is_resource() (於 importlib.resources 模組中): importlib resources -- Resources.
                                                             (line  120)
* is_resource_enabled() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  197)
* is_running() (asyncio.loop 的方法):    Running and stopping the loop.
                                                             (line   35)
* is_safe (uuid.UUID 的屬性):            uuid --- UUID objects according to RFC 4122.
                                                             (line  151)
* is_serving() (asyncio.Server 的方法):  Server Objects.     (line   89)
* is_set() (asyncio.Event 的方法):       Event.              (line   66)
* is_set() (threading.Event 的方法):     Event Objects.      (line   23)
* is_signed() (decimal.Context 的方法):  Context objects.    (line  319)
* is_signed() (decimal.Decimal 的方法):  Decimal objects.    (line  310)
* is_site_local (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  187)
* is_site_local (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  357)
* is_snan() (decimal.Context 的方法):    Context objects.    (line  323)
* is_snan() (decimal.Decimal 的方法):    Decimal objects.    (line  316)
* is_socket() (pathlib.Path 的方法):     Methods<2>.         (line  152)
* is_subnormal() (decimal.Context 的方法): Context objects.  (line  328)
* is_subnormal() (decimal.Decimal 的方法): Decimal objects.  (line  321)
* is_symlink() (os.DirEntry 的方法):     Files and Directories.
                                                             (line  921)
* is_symlink() (pathlib.Path 的方法):    Methods<2>.         (line  144)
* is_tarfile() (於 tarfile 模組中):      tarfile --- Read and write tar archive files.
                                                             (line  174)
* is_term_resized() (於 curses 模組中):  Functions<3>.       (line  237)
* is_tracing() (於 tracemalloc 模組中):  Functions<9>.       (line   43)
* is_tracked() (於 gc 模組中):           gc --- Garbage Collector interface.
                                                             (line  157)
* is_unspecified (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line  105)
* is_unspecified (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   74)
* is_unspecified (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  177)
* is_unspecified (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  301)
* is_wintouched() (curses.window 的方法): Window Objects.    (line  372)
* is_zero() (decimal.Context 的方法):    Context objects.    (line  332)
* is_zero() (decimal.Decimal 的方法):    Decimal objects.    (line  326)
* is_zipfile() (於 zipfile 模組中):      zipfile --- Work with ZIP archives.
                                                             (line   71)
* item selection:                        The standard type hierarchy.
                                                             (line  127)
* item() (tkinter.ttk.Treeview 的方法):  ttk Treeview.       (line  212)
* item() (xml.dom.NamedNodeMap 的方法):  NamedNodeMap Objects.
                                                             (line   12)
* item() (xml.dom.NodeList 的方法):      NodeList Objects.   (line   15)
* itemgetter() (於 operator 模組中):     operator --- Standard operators as functions.
                                                             (line  258)
* items() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  234)
* items() (contextvars.Context 的方法):  Manual Context Management.
                                                             (line  108)
* items() (dict 的方法):                 Mapping Types --- dict.
                                                             (line  168)
* items() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  238)
* items() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  348)
* items() (mailbox.Mailbox 的方法):      Mailbox objects.    (line  129)
* items() (types.MappingProxyType 的方法): Standard Interpreter Types.
                                                             (line  256)
* items() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line   71)
* itemsize (array.array 的屬性):         array --- 高效率的數值型態陣列.
                                                             (line  102)
* itemsize (memoryview 的屬性):          Memory Views.       (line  426)
* ItemsView (collections.abc 中的類別):  Collections Abstract Base Classes.
                                                             (line  187)
* ItemsView (typing 中的類別):           Classes functions and decorators.
                                                             (line  290)
* iter() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  146)
* iter() (xml.etree.ElementTree.ElementTree 的方法): ElementTree Objects.
                                                             (line   45)
* iter() (內建函式):                     內建函式.           (line  860)
* iterable:                              Glossary.           (line  665)
* Iterable (collections.abc 中的類別):   Collections Abstract Base Classes.
                                                             (line  120)
* Iterable (typing 中的類別):            Classes functions and decorators.
                                                             (line  147)
* iterable; unpacking:                   Expression lists.   (line   16)
* iterator:                              Glossary.           (line  687)
* Iterator (collections.abc 中的類別):   Collections Abstract Base Classes.
                                                             (line  137)
* Iterator (typing 中的類別):            Classes functions and decorators.
                                                             (line  151)
* iterator protocol:                     Iterator Types.     (line    6)
* iterdecode() (於 codecs 模組中):       codecs --- Codec registry and base classes.
                                                             (line  225)
* iterdir() (pathlib.Path 的方法):       Methods<2>.         (line  187)
* iterdir() (zipfile.Path 的方法):       Path Objects.       (line   36)
* iterdump() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line  384)
* iterencode() (json.JSONEncoder 的方法): Encoders and Decoders.
                                                             (line  219)
* iterencode() (於 codecs 模組中):       codecs --- Codec registry and base classes.
                                                             (line  213)
* iterfind() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  157)
* iterfind() (xml.etree.ElementTree.ElementTree 的方法): ElementTree Objects.
                                                             (line   52)
* iteritems() (mailbox.Mailbox 的方法):  Mailbox objects.    (line  129)
* iterkeys() (mailbox.Mailbox 的方法):   Mailbox objects.    (line  107)
* itermonthdates() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line   45)
* itermonthdays() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line   53)
* itermonthdays2() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line   61)
* itermonthdays3() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line   69)
* itermonthdays4() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line   79)
* iternextfunc (C 型態):                 Slot Type typedefs. (line   99)
* iterparse() (於 xml.etree.ElementTree 模組中): Functions<6>.
                                                             (line  123)
* itertext() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  166)
* itertools (2to3 fixer):                Fixers.             (line  174)
* itertools (模組):                      itertools --- Functions creating iterators for efficient looping.
                                                             (line    6)
* itertools_imports (2to3 fixer):        Fixers.             (line  168)
* itervalues() (mailbox.Mailbox 的方法): Mailbox objects.    (line  114)
* iterweekdays() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line   39)
* iter_attachments() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  559)
* iter_child_nodes() (於 ast 模組中):    ast Helpers.        (line  107)
* iter_fields() (於 ast 模組中):         ast Helpers.        (line  102)
* iter_importers() (於 pkgutil 模組中):  pkgutil --- Package extension utility.
                                                             (line  123)
* iter_modules() (於 pkgutil 模組中):    pkgutil --- Package extension utility.
                                                             (line  141)
* iter_parts() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  575)
* iter_unpack() (struct.Struct 的方法):  Classes<2>.         (line   47)
* iter_unpack() (於 struct 模組中):      Functions and Exceptions.
                                                             (line   42)
* ItimerError:                           Module contents<2>. (line  211)
* ITIMER_PROF (於 signal 模組中):        Module contents<2>. (line  178)
* ITIMER_REAL (於 signal 模組中):        Module contents<2>. (line  168)
* ITIMER_VIRTUAL (於 signal 模組中):     Module contents<2>. (line  173)
* itruediv() (於 operator 模組中):       In-place Operators. (line   99)
* ixor() (於 operator 模組中):           In-place Operators. (line  104)
* j; in numeric literal:                 Floating point literals.
                                                             (line   28)
* Jansen, Jack:                          uu --- Encode and decode uuencode files.
                                                             (line   20)
* Java; language:                        The standard type hierarchy.
                                                             (line  107)
* java_ver() (於 platform 模組中):       Java Platform.      (line    6)
* join() (asyncio.Queue 的方法):         Queue.              (line   50)
* join() (bytearray 的方法):             Bytes and Bytearray Operations.
                                                             (line  111)
* join() (bytes 的方法):                 Bytes and Bytearray Operations.
                                                             (line  111)
* join() (multiprocessing.JoinableQueue 的方法): Pipes and Queues.
                                                             (line  241)
* join() (multiprocessing.pool.Pool 的方法): Process Pools.  (line  180)
* join() (multiprocessing.Process 的方法): Process and exceptions.
                                                             (line   51)
* join() (queue.Queue 的方法):           Queue Objects.      (line   83)
* join() (str 的方法):                   String Methods<2>.  (line  278)
* join() (threading.Thread 的方法):      Thread Objects.     (line  110)
* join() (於 os.path 模組中):            os path --- Common pathname manipulations.
                                                             (line  253)
* join() (於 shlex 模組中):              shlex --- Simple lexical analysis.
                                                             (line   30)
* JoinableQueue (multiprocessing 中的類別): Pipes and Queues.
                                                             (line  220)
* joinpath() (pathlib.PurePath 的方法):  Methods and properties.
                                                             (line  198)
* join_thread() (multiprocessing.Queue 的方法): Pipes and Queues.
                                                             (line  169)
* join_thread() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  786)
* json (模組):                           json --- JSON encoder and decoder.
                                                             (line    6)
* json.tool (模組):                      Command Line Interface<2>.
                                                             (line    6)
* json.tool command line option; -h:     Command line options<2>.
                                                             (line   41)
* json.tool command line option; –help:  Command line options<2>.
                                                             (line   41)
* json.tool command line option; –json-lines: Command line options<2>.
                                                             (line   35)
* json.tool command line option; –sort-keys: Command line options<2>.
                                                             (line   29)
* json.tool command line option; infile: Command line options<2>.
                                                             (line    6)
* json.tool command line option; outfile: Command line options<2>.
                                                             (line   24)
* JSONDecodeError:                       例外<2>.            (line    6)
* JSONDecoder (json 中的類別):           Encoders and Decoders.
                                                             (line    6)
* JSONEncoder (json 中的類別):           Encoders and Decoders.
                                                             (line  101)
* js_output() (http.cookies.BaseCookie 的方法): Cookie Objects.
                                                             (line   32)
* js_output() (http.cookies.Morsel 的方法): Morsel Objects.  (line   79)
* jump (pdb command):                    Debugger Commands.  (line  196)
* JUMP_ABSOLUTE (opcode):                Python Bytecode Instructions.
                                                             (line  681)
* JUMP_FORWARD (opcode):                 Python Bytecode Instructions.
                                                             (line  649)
* JUMP_IF_FALSE_OR_POP (opcode):         Python Bytecode Instructions.
                                                             (line  674)
* JUMP_IF_TRUE_OR_POP (opcode):          Python Bytecode Instructions.
                                                             (line  667)
* kbhit() (於 msvcrt 模組中):            Console I/O.        (line    6)
* KDEDIR:                                webbrowser --- Convenient Web-browser controller.
                                                             (line  183)
* kevent() (於 select 模組中):           select --- Waiting for I/O completion.
                                                             (line  101)
* key:                                   Dictionary displays.
                                                             (line    6)
* key (http.cookies.Morsel 的屬性):      Morsel Objects.     (line   60)
* key function:                          Glossary.           (line  709)
* key/datum pair:                        Dictionary displays.
                                                             (line    6)
* KeyboardInterrupt:                     Concrete exceptions.
                                                             (line   70)
* KeyboardInterrupt (built-in exception): Signal Handling<2>.
                                                             (line    8)
* KeyboardInterrupt (built-in exception) <1>: Signal Handling<2>.
                                                             (line   20)
* KeyError:                              Concrete exceptions.
                                                             (line   65)
* keylog_filename (ssl.SSLContext 的屬性): SSL Contexts.     (line  529)
* keyname() (於 curses 模組中):          Functions<3>.       (line  247)
* keypad() (curses.window 的方法):       Window Objects.     (line  377)
* keyrefs() (weakref.WeakKeyDictionary 的方法): weakref --- Weak references.
                                                             (line  172)
* keys() (contextvars.Context 的方法):   Manual Context Management.
                                                             (line  100)
* keys() (dict 的方法):                  Mapping Types --- dict.
                                                             (line  173)
* keys() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  230)
* keys() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  340)
* keys() (mailbox.Mailbox 的方法):       Mailbox objects.    (line  107)
* keys() (sqlite3.Row 的方法):           Row Objects.        (line   18)
* keys() (types.MappingProxyType 的方法): Standard Interpreter Types.
                                                             (line  261)
* keys() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line   76)
* KeysView (collections.abc 中的類別):   Collections Abstract Base Classes.
                                                             (line  187)
* KeysView (typing 中的類別):            Classes functions and decorators.
                                                             (line  286)
* keyword:                               Keywords.           (line    6)
* keyword (模組):                        keyword --- Testing for Python keywords.
                                                             (line    6)
* keyword argument:                      Glossary.           (line  731)
* keywords (functools.partial 的屬性):   partial Objects.    (line   20)
* KEY_ALL_ACCESS (於 winreg 模組中):     Access Rights.      (line    8)
* KEY_CREATE_LINK (於 winreg 模組中):    Access Rights.      (line   51)
* KEY_CREATE_SUB_KEY (於 winreg 模組中): Access Rights.      (line   38)
* KEY_ENUMERATE_SUB_KEYS (於 winreg 模組中): Access Rights.  (line   42)
* KEY_EXECUTE (於 winreg 模組中):        Access Rights.      (line   26)
* KEY_NOTIFY (於 winreg 模組中):         Access Rights.      (line   46)
* KEY_QUERY_VALUE (於 winreg 模組中):    Access Rights.      (line   30)
* KEY_READ (於 winreg 模組中):           Access Rights.      (line   20)
* KEY_SET_VALUE (於 winreg 模組中):      Access Rights.      (line   34)
* KEY_WOW64_32KEY (於 winreg 模組中):    64-bit Specific.    (line   13)
* KEY_WOW64_64KEY (於 winreg 模組中):    64-bit Specific.    (line    8)
* KEY_WRITE (於 winreg 模組中):          Access Rights.      (line   15)
* kill() (asyncio.asyncio.subprocess.Process 的方法): Interacting with Subprocesses.
                                                             (line  100)
* kill() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   35)
* kill() (multiprocessing.Process 的方法): Process and exceptions.
                                                             (line  166)
* kill() (subprocess.Popen 的方法):      Popen Objects.      (line   89)
* kill() (於 os 模組中):                 Process Management. (line  287)
* killchar() (於 curses 模組中):         Functions<3>.       (line  257)
* killpg() (於 os 模組中):               Process Management. (line  309)
* kill_python() (於 test.support.script_helper 模組中): test support script_helper --- Utilities for the Python execution tests.
                                                             (line   66)
* kind (inspect.Parameter 的屬性):       Introspecting callables with the Signature object.
                                                             (line  180)
* knownfiles (於 mimetypes 模組中):      mimetypes --- Map filenames to MIME types.
                                                             (line  121)
* kqueue() (於 select 模組中):           select --- Waiting for I/O completion.
                                                             (line   91)
* KqueueSelector (selectors 中的類別):   Classes<3>.         (line  195)
* kwargs (inspect.BoundArguments 的屬性): Introspecting callables with the Signature object.
                                                             (line  302)
* kwlist (於 keyword 模組中):            keyword --- Testing for Python keywords.
                                                             (line   17)
* L (於 re 模組中):                      Module Contents.    (line   81)
* LabelEntry (tkinter.tix 中的類別):     Basic Widgets.      (line   31)
* LabelFrame (tkinter.tix 中的類別):     Basic Widgets.      (line   37)
* lambda:                                Glossary.           (line  735)
* lambda; expression:                    Lambdas.            (line    6)
* lambda; expression <1>:                Function definitions.
                                                             (line  109)
* lambda; form:                          Lambdas.            (line    6)
* LambdaType (於 types 模組中):          Standard Interpreter Types.
                                                             (line   19)
* LANG:                                  GNU gettext API.    (line   21)
* LANG <1>:                              Class-based API.    (line   26)
* LANG <2>:                              locale --- Internationalization services.
                                                             (line   49)
* LANG <3>:                              locale --- Internationalization services.
                                                             (line  310)
* LANG <4>:                              locale --- Internationalization services.
                                                             (line  314)
* LANGUAGE:                              GNU gettext API.    (line   20)
* LANGUAGE <1>:                          Class-based API.    (line   25)
* large files:                           Large File Support. (line    6)
* LARGEST (於 test.support 模組中):      test support --- Utilities for the Python test suite.
                                                             (line  150)
* LargeZipFile:                          zipfile --- Work with ZIP archives.
                                                             (line   37)
* last() (nntplib.NNTP 的方法):          Methods<3>.         (line  237)
* lastChild (xml.dom.Node 的屬性):       Node Objects.       (line   59)
* lastcmd (cmd.Cmd 的屬性):              Cmd Objects.        (line  131)
* lastgroup (re.Match 的屬性):           Match Objects.      (line  185)
* lastindex (re.Match 的屬性):           Match Objects.      (line  177)
* lastResort (於 logging 模組中):        Module-Level Attributes.
                                                             (line    6)
* lastrowid (sqlite3.Cursor 的屬性):     Cursor Objects.     (line  199)
* last_accepted (multiprocessing.connection.Listener 的屬性): Listeners and Clients.
                                                             (line  103)
* last_traceback (in module sys):        The standard type hierarchy.
                                                             (line  759)
* last_traceback (於 sys 模組中):        sys --- System-specific parameters and functions.
                                                             (line  991)
* last_type (於 sys 模組中):             sys --- System-specific parameters and functions.
                                                             (line  991)
* last_value (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line  991)
* layout() (tkinter.ttk.Style 的方法):   Ttk Styling.        (line   96)
* lazycache() (於 linecache 模組中):     linecache --- Random access to text lines.
                                                             (line   50)
* LazyLoader (importlib.util 中的類別):  importlib util -- Utility code for importers.
                                                             (line  225)
* LBRACE (於 token 模組中):              token --- Constants used with Python parse trees.
                                                             (line  126)
* LBYL:                                  Glossary.           (line  742)
* lchflags() (於 os 模組中):             Files and Directories.
                                                             (line  291)
* lchmod() (pathlib.Path 的方法):        Methods<2>.         (line  208)
* lchmod() (於 os 模組中):               Files and Directories.
                                                             (line  305)
* lchown() (於 os 模組中):               Files and Directories.
                                                             (line  320)
* LC_ALL:                                GNU gettext API.    (line   20)
* LC_ALL <1>:                            Class-based API.    (line   25)
* LC_ALL (於 locale 模組中):             locale --- Internationalization services.
                                                             (line  493)
* LC_COLLATE (於 locale 模組中):         locale --- Internationalization services.
                                                             (line  462)
* LC_CTYPE (於 locale 模組中):           locale --- Internationalization services.
                                                             (line  456)
* LC_MESSAGES:                           GNU gettext API.    (line   20)
* LC_MESSAGES <1>:                       Class-based API.    (line   26)
* LC_MESSAGES (於 locale 模組中):        locale --- Internationalization services.
                                                             (line  478)
* LC_MONETARY (於 locale 模組中):        locale --- Internationalization services.
                                                             (line  473)
* LC_NUMERIC (於 locale 模組中):         locale --- Internationalization services.
                                                             (line  485)
* LC_TIME (於 locale 模組中):            locale --- Internationalization services.
                                                             (line  468)
* LDCXXSHARED:                           Build and C API Changes<8>.
                                                             (line  153)
* ldexp() (於 math 模組中):              Number-theoretic and representation functions.
                                                             (line  167)
* LDFLAGS:                               New Improved and Deprecated Modules<4>.
                                                             (line   59)
* ldgettext() (於 gettext 模組中):       GNU gettext API.    (line   90)
* ldngettext() (於 gettext 模組中):      GNU gettext API.    (line   94)
* le() (於 operator 模組中):             operator --- Standard operators as functions.
                                                             (line   24)
* leading whitespace:                    Indentation.        (line    6)
* leapdays() (於 calendar 模組中):       calendar --- General calendar-related functions.
                                                             (line  306)
* leaveok() (curses.window 的方法):      Window Objects.     (line  384)
* left (filecmp.dircmp 的屬性):          The dircmp class.   (line   41)
* left() (於 turtle 模組中):             Turtle motion.      (line   57)
* LEFTSHIFT (於 token 模組中):           token --- Constants used with Python parse trees.
                                                             (line  158)
* LEFTSHIFTEQUAL (於 token 模組中):      token --- Constants used with Python parse trees.
                                                             (line  202)
* left_list (filecmp.dircmp 的屬性):     The dircmp class.   (line   49)
* left_only (filecmp.dircmp 的屬性):     The dircmp class.   (line   63)
* len() (內建函式):                      內建函式.           (line  887)
* lenfunc (C 型態):                      Slot Type typedefs. (line  103)
* length (xml.dom.NamedNodeMap 的屬性):  NamedNodeMap Objects.
                                                             (line    8)
* length (xml.dom.NodeList 的屬性):      NodeList Objects.   (line   21)
* length_hint() (於 operator 模組中):    operator --- Standard operators as functions.
                                                             (line  206)
* LESS (於 token 模組中):                token --- Constants used with Python parse trees.
                                                             (line  106)
* LESSEQUAL (於 token 模組中):           token --- Constants used with Python parse trees.
                                                             (line  142)
* lexical analysis:                      Lexical analysis.   (line    6)
* lexical definitions:                   Notation.           (line   31)
* lexists() (於 os.path 模組中):         os path --- Common pathname manipulations.
                                                             (line  126)
* lgamma() (於 math 模組中):             Special functions.  (line   35)
* lgettext() (gettext.GNUTranslations 的方法): The GNUTranslations class.
                                                             (line   93)
* lgettext() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   63)
* lgettext() (於 gettext 模組中):        GNU gettext API.    (line   88)
* lib2to3 (模組):                        lib2to3 - 2to3's library.
                                                             (line    6)
* libc_ver() (於 platform 模組中):       Unix Platforms.     (line    6)
* library (ssl.SSLError 的屬性):         Exceptions<11>.     (line   19)
* library (於 dbm.ndbm 模組中):          dbm ndbm --- Interface based on ndbm.
                                                             (line   27)
* LibraryLoader (ctypes 中的類別):       Loading shared libraries.
                                                             (line  158)
* library_dir_option() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  219)
* library_filename() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  458)
* library_option() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  224)
* license (內建變數):                    Constants added by the site module.
                                                             (line   24)
* LifoQueue (asyncio 中的類別):          LIFO Queue.         (line    6)
* LifoQueue (queue 中的類別):            queue --- A synchronized queue class.
                                                             (line   42)
* light-weight processes:                _thread --- Low-level threading API.
                                                             (line    6)
* LimitOverrunError:                     Exceptions<8>.      (line   59)
* limit_denominator() (fractions.Fraction 的方法): fractions --- Rational numbers.
                                                             (line  125)
* lin2adpcm() (於 audioop 模組中):       audioop --- Manipulate raw audio data.
                                                             (line  112)
* lin2alaw() (於 audioop 模組中):        audioop --- Manipulate raw audio data.
                                                             (line  126)
* lin2lin() (於 audioop 模組中):         audioop --- Manipulate raw audio data.
                                                             (line  133)
* lin2ulaw() (於 audioop 模組中):        audioop --- Manipulate raw audio data.
                                                             (line  148)
* 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() (msilib.Dialog 的方法):         GUI classes.        (line   64)
* line-buffered I/O:                     內建函式.           (line 1215)
* linecache (模組):                      linecache --- Random access to text lines.
                                                             (line    6)
* lineno (ast.AST 的屬性):               Node classes.       (line   39)
* lineno (doctest.DocTest 的屬性):       DocTest Objects.    (line   42)
* lineno (doctest.Example 的屬性):       Example Objects.    (line   41)
* lineno (json.JSONDecodeError 的屬性):  例外<2>.            (line   23)
* lineno (pyclbr.Class 的屬性):          Class Objects<2>.   (line   21)
* lineno (pyclbr.Function 的屬性):       函式物件.           (line   21)
* lineno (re.error 的屬性):              Module Contents.    (line  373)
* lineno (shlex.shlex 的屬性):           shlex Objects.      (line  168)
* lineno (SyntaxError 的屬性):           Concrete exceptions.
                                                             (line  260)
* lineno (traceback.TracebackException 的屬性): TracebackException Objects.
                                                             (line   46)
* lineno (tracemalloc.Filter 的屬性):    Filter.             (line   48)
* lineno (tracemalloc.Frame 的屬性):     Frame.              (line   17)
* lineno (xml.parsers.expat.ExpatError 的屬性): ExpatError Exceptions.
                                                             (line   27)
* lineno() (於 fileinput 模組中):        fileinput --- Iterate over lines from multiple input streams.
                                                             (line   92)
* LINES:                                 curses<2>.          (line    6)
* LINES <1>:                             Functions<3>.       (line  125)
* LINES <2>:                             Functions<3>.       (line  526)
* LINES <3>:                             Functions<3>.       (line  550)
* LINES <4>:                             Functions<3>.       (line  552)
* lines (os.terminal_size 的屬性):       Querying the size of a terminal.
                                                             (line   34)
* linesep (email.policy.Policy 的屬性):  email policy Policy Objects.
                                                             (line  152)
* linesep (於 os 模組中):                Miscellaneous System Information.
                                                             (line  127)
* lineterminator (csv.Dialect 的屬性):   Dialects and Formatting Parameters.
                                                             (line   43)
* LineTooLong:                           http client --- HTTP protocol client.
                                                             (line  178)
* line_buffering (io.TextIOWrapper 的屬性): Text I/O<2>.     (line  161)
* line_num (csv.csvreader 的屬性):       Reader Objects.     (line   22)
* link() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  348)
* link() (於 os 模組中):                 Files and Directories.
                                                             (line  334)
* linkname (tarfile.TarInfo 的屬性):     TarInfo Objects.    (line   67)
* link_executable() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  400)
* link_shared_lib() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  410)
* link_shared_object() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  421)
* link_to() (pathlib.Path 的方法):       Methods<2>.         (line  406)
* list:                                  Glossary.           (line  756)
* list (pdb command):                    Debugger Commands.  (line  206)
* List (typing 中的類別):                Classes functions and decorators.
                                                             (line  255)
* list (內建類別):                       List（串列）<2>.    (line   10)
* list comprehension:                    Glossary.           (line  762)
* list() (imaplib.IMAP4 的方法):         IMAP4 Objects.      (line  126)
* list() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  213)
* list() (nntplib.NNTP 的方法):          Methods<3>.         (line  104)
* list() (poplib.POP3 的方法):           POP3 Objects.       (line   56)
* list() (tarfile.TarFile 的方法):       TarFile Objects.    (line  119)
* list; comprehensions:                  List displays.      (line    6)
* list; display:                         List displays.      (line    6)
* listdir() (於 os 模組中):              Files and Directories.
                                                             (line  356)
* listen() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  214)
* listen() (socket.socket 的方法):       Socket Objects.     (line  186)
* listen() (於 logging.config 模組中):   Configuration functions.
                                                             (line  106)
* listen() (於 turtle 模組中):           Using screen events.
                                                             (line    6)
* Listener (multiprocessing.connection 中的類別): Listeners and Clients.
                                                             (line   50)
* listMethods() (xmlrpc.client.ServerProxy.system 的方法): ServerProxy Objects.
                                                             (line   17)
* ListNoteBook (tkinter.tix 中的類別):   Manager Widgets.    (line   13)
* listxattr() (於 os 模組中):            Linux extended attributes.
                                                             (line   26)
* LIST_APPEND (opcode):                  Python Bytecode Instructions.
                                                             (line  322)
* list_dialects() (於 csv 模組中):       Module Contents<3>. (line   91)
* list_folders() (mailbox.Maildir 的方法): Maildir.          (line   61)
* list_folders() (mailbox.MH 的方法):    MH.                 (line   32)
* literal:                               Literals.           (line    6)
* literal <1>:                           Literals<2>.        (line    6)
* Literal (於 typing 模組中):            Classes functions and decorators.
                                                             (line  878)
* literal_eval() (於 ast 模組中):        ast Helpers.        (line   43)
* LittleEndianStructure (ctypes 中的類別): Structured data types.
                                                             (line   14)
* ljust() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  247)
* ljust() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  247)
* ljust() (str 的方法):                  String Methods<2>.  (line  286)
* 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  222)
* LMTP (smtplib 中的類別):               smtplib --- SMTP protocol client.
                                                             (line   98)
* ln() (decimal.Context 的方法):         Context objects.    (line  336)
* ln() (decimal.Decimal 的方法):         Decimal objects.    (line  331)
* LNAME:                                 getpass --- Portable password input.
                                                             (line   38)
* lngettext() (gettext.GNUTranslations 的方法): The GNUTranslations class.
                                                             (line   95)
* lngettext() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   65)
* lngettext() (於 gettext 模組中):       GNU gettext API.    (line   92)
* load() (http.cookiejar.FileCookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line  125)
* load() (http.cookies.BaseCookie 的方法): Cookie Objects.   (line   40)
* load() (pickle.Unpickler 的方法):      Module Interface.   (line  267)
* load() (tracemalloc.Snapshot 的類別成員): Snapshot.        (line   50)
* load() (於 json 模組中):               Basic Usage.        (line   92)
* load() (於 marshal 模組中):            marshal --- Internal Python object serialization.
                                                             (line   60)
* load() (於 pickle 模組中):             Module Interface.   (line   58)
* load() (於 plistlib 模組中):           plistlib --- Generate and parse Mac OS X plist files.
                                                             (line   43)
* loader:                                Finders and loaders.
                                                             (line    6)
* loader <1>:                            Glossary.           (line  771)
* Loader (importlib.abc 中的類別):       importlib abc -- Abstract base classes related to import.
                                                             (line  155)
* loader (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  366)
* LoadError:                             http cookiejar --- Cookie handling for HTTP clients.
                                                             (line   34)
* loader_state (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  390)
* LoadKey() (於 winreg 模組中):          Functions<11>.      (line  263)
* LoadLibrary() (ctypes.LibraryLoader 的方法): Loading shared libraries.
                                                             (line  169)
* loads() (於 json 模組中):              Basic Usage.        (line  147)
* loads() (於 marshal 模組中):           marshal --- Internal Python object serialization.
                                                             (line   82)
* loads() (於 pickle 模組中):            Module Interface.   (line   76)
* loads() (於 plistlib 模組中):          plistlib --- Generate and parse Mac OS X plist files.
                                                             (line   76)
* loads() (於 xmlrpc.client 模組中):     Convenience Functions.
                                                             (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)
* LOAD_ATTR (opcode):                    Python Bytecode Instructions.
                                                             (line  625)
* LOAD_BUILD_CLASS (opcode):             Python Bytecode Instructions.
                                                             (line  433)
* load_cert_chain() (ssl.SSLContext 的方法): SSL Contexts.   (line   80)
* LOAD_CLASSDEREF (opcode):              Python Bytecode Instructions.
                                                             (line  736)
* LOAD_CLOSURE (opcode):                 Python Bytecode Instructions.
                                                             (line  723)
* LOAD_CONST (opcode):                   Python Bytecode Instructions.
                                                             (line  527)
* load_default_certs() (ssl.SSLContext 的方法): SSL Contexts.
                                                             (line  111)
* LOAD_DEREF (opcode):                   Python Bytecode Instructions.
                                                             (line  730)
* load_dh_params() (ssl.SSLContext 的方法): SSL Contexts.    (line  356)
* load_extension() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line  290)
* LOAD_FAST (opcode):                    Python Bytecode Instructions.
                                                             (line  710)
* LOAD_GLOBAL (opcode):                  Python Bytecode Instructions.
                                                             (line  692)
* LOAD_METHOD (opcode):                  Python Bytecode Instructions.
                                                             (line  816)
* load_module() (importlib.abc.FileLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  480)
* load_module() (importlib.abc.InspectLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  434)
* load_module() (importlib.abc.Loader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  189)
* load_module() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  578)
* load_module() (importlib.machinery.SourceFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  239)
* load_module() (importlib.machinery.SourcelessFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  283)
* load_module() (zipimport.zipimporter 的方法): zipimporter Objects.
                                                             (line   62)
* load_module() (於 imp 模組中):         imp --- Access the import internals.
                                                             (line   90)
* LOAD_NAME (opcode):                    Python Bytecode Instructions.
                                                             (line  531)
* load_package_tests() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  909)
* load_verify_locations() (ssl.SSLContext 的方法): SSL Contexts.
                                                             (line  129)
* local (threading 中的類別):            Thread-Local Data.  (line   15)
* localcontext() (於 decimal 模組中):    Context objects.    (line   25)
* LOCALE (於 re 模組中):                 Module Contents.    (line   81)
* locale (模組):                         locale --- Internationalization services.
                                                             (line    6)
* localeconv() (於 locale 模組中):       locale --- Internationalization services.
                                                             (line   53)
* LocaleHTMLCalendar (calendar 中的類別): calendar --- General calendar-related functions.
                                                             (line  272)
* LocaleTextCalendar (calendar 中的類別): calendar --- General calendar-related functions.
                                                             (line  264)
* localName (xml.dom.Attr 的屬性):       Attr Objects.       (line   13)
* localName (xml.dom.Node 的屬性):       Node Objects.       (line   64)
* locals() (內建函式):                   內建函式.           (line  899)
* localtime() (於 email.utils 模組中):   email utils Miscellaneous utilities.
                                                             (line   13)
* localtime() (於 time 模組中):          Functions<2>.       (line  141)
* Locator (xml.sax.xmlreader 中的類別):  xml sax xmlreader --- Interface for XML parsers.
                                                             (line   43)
* Lock (asyncio 中的類別):               Lock.               (line    6)
* Lock (multiprocessing 中的類別):       Synchronization primitives.
                                                             (line   45)
* Lock (threading 中的類別):             Lock Objects.       (line   33)
* lock() (mailbox.Babyl 的方法):         Babyl.              (line   59)
* lock() (mailbox.Mailbox 的方法):       Mailbox objects.    (line  249)
* lock() (mailbox.Maildir 的方法):       Maildir.            (line  107)
* lock() (mailbox.mbox 的方法):          mbox.               (line   39)
* lock() (mailbox.MH 的方法):            MH.                 (line   84)
* lock() (mailbox.MMDF 的方法):          MMDF.               (line   35)
* Lock() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  170)
* lock, interpreter:                     Thread State and the Global Interpreter Lock.
                                                             (line    6)
* locked() (asyncio.Condition 的方法):   Condition.          (line   64)
* locked() (asyncio.Lock 的方法):        Lock.               (line   59)
* locked() (asyncio.Semaphore 的方法):   Semaphore.          (line   51)
* locked() (threading.Lock 的方法):      Lock Objects.       (line   87)
* locked() (_thread.lock 的方法):        _thread --- Low-level threading API.
                                                             (line  155)
* lockf() (於 fcntl 模組中):             fcntl --- The fcntl and ioctl system calls.
                                                             (line  120)
* lockf() (於 os 模組中):                File Descriptor Operations.
                                                             (line  213)
* locking() (於 msvcrt 模組中):          File Operations.    (line    6)
* LockType (於 _thread 模組中):          _thread --- Low-level threading API.
                                                             (line   27)
* lock_held() (於 imp 模組中):           imp --- Access the import internals.
                                                             (line  255)
* log() (logging.Logger 的方法):         Logger Objects.     (line  239)
* log() (於 cmath 模組中):               Power and logarithmic functions<2>.
                                                             (line   11)
* log() (於 logging 模組中):             Module-Level Functions.
                                                             (line  150)
* log() (於 math 模組中):                Power and logarithmic functions.
                                                             (line   28)
* log10() (decimal.Context 的方法):      Context objects.    (line  340)
* log10() (decimal.Decimal 的方法):      Decimal objects.    (line  337)
* log10() (於 cmath 模組中):             Power and logarithmic functions<2>.
                                                             (line   18)
* log10() (於 math 模組中):              Power and logarithmic functions.
                                                             (line   55)
* log1p() (於 math 模組中):              Power and logarithmic functions.
                                                             (line   36)
* log2() (於 math 模組中):               Power and logarithmic functions.
                                                             (line   41)
* logb() (decimal.Context 的方法):       Context objects.    (line  344)
* logb() (decimal.Decimal 的方法):       Decimal objects.    (line  343)
* Logger (logging 中的類別):             Logger Objects.     (line   23)
* LoggerAdapter (logging 中的類別):      LoggerAdapter Objects.
                                                             (line   11)
* logging (模組):                        logging --- Logging facility for Python.
                                                             (line    6)
* logging.config (模組):                 logging config --- Logging configuration.
                                                             (line    6)
* logging.handlers (模組):               logging handlers --- Logging handlers.
                                                             (line    6)
* logical line:                          Logical lines.      (line    6)
* logical_and() (decimal.Context 的方法): Context objects.   (line  348)
* logical_and() (decimal.Decimal 的方法): Decimal objects.   (line  351)
* logical_invert() (decimal.Context 的方法): Context objects.
                                                             (line  353)
* logical_invert() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  357)
* logical_or() (decimal.Context 的方法): Context objects.    (line  357)
* logical_or() (decimal.Decimal 的方法): Decimal objects.    (line  362)
* logical_xor() (decimal.Context 的方法): Context objects.   (line  362)
* logical_xor() (decimal.Decimal 的方法): Decimal objects.   (line  368)
* login() (ftplib.FTP 的方法):           FTP Objects.        (line   48)
* login() (imaplib.IMAP4 的方法):        IMAP4 Objects.      (line  132)
* login() (nntplib.NNTP 的方法):         Methods<3>.         (line   48)
* login() (smtplib.SMTP 的方法):         SMTP Objects.       (line  102)
* login_cram_md5() (imaplib.IMAP4 的方法): IMAP4 Objects.    (line  137)
* LOGNAME:                               Process Parameters. (line  221)
* LOGNAME <1>:                           getpass --- Portable password input.
                                                             (line   38)
* lognormvariate() (於 random 模組中):   Real-valued distributions.
                                                             (line   63)
* logout() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line  143)
* LogRecord (logging 中的類別):          LogRecord Objects.  (line   11)
* log_date_time_string() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  319)
* log_error() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  288)
* log_exception() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line  208)
* log_message() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  294)
* log_request() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  281)
* log_to_stderr() (於 multiprocessing 模組中): Logging<2>.   (line   24)
* long (2to3 fixer):                     Fixers.             (line  181)
* longMessage (unittest.TestCase 的屬性): Test cases.        (line  674)
* longname() (於 curses 模組中):         Functions<3>.       (line  264)
* LONG_MAX:                              整數物件.           (line  105)
* lookup() (symtable.SymbolTable 的方法): Examining Symbol Tables.
                                                             (line   52)
* lookup() (tkinter.ttk.Style 的方法):   Ttk Styling.        (line   81)
* lookup() (於 codecs 模組中):           codecs --- Codec registry and base classes.
                                                             (line   47)
* lookup() (於 unicodedata 模組中):      unicodedata --- Unicode Database.
                                                             (line   16)
* LookupError:                           Base classes.       (line   54)
* lookup_error() (於 codecs 模組中):     Error Handlers.     (line  117)
* loop control; target:                  The break statement.
                                                             (line   12)
* loop() (於 asyncore 模組中):           asyncore --- Asynchronous socket handler.
                                                             (line   49)
* loop; over mutable sequence:           The for statement.  (line   44)
* loop; statement:                       The break statement.
                                                             (line    6)
* loop; statement <1>:                   The continue statement.
                                                             (line    6)
* loop; statement <2>:                   The while statement.
                                                             (line    6)
* loop; statement <3>:                   The for statement.  (line    6)
* lower() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  552)
* lower() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  552)
* lower() (str 的方法):                  String Methods<2>.  (line  293)
* LPAR (於 token 模組中):                token --- Constants used with Python parse trees.
                                                             (line   54)
* lpAttributeList (subprocess.STARTUPINFO 的屬性): Windows Popen Helpers.
                                                             (line   60)
* lru_cache() (於 functools 模組中):     functools --- Higher-order functions and operations on callable objects.
                                                             (line   73)
* lseek() (於 os 模組中):                File Descriptor Operations.
                                                             (line  239)
* lshift() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line  106)
* LSQB (於 token 模組中):                token --- Constants used with Python parse trees.
                                                             (line   62)
* lstat() (pathlib.Path 的方法):         Methods<2>.         (line  214)
* lstat() (於 os 模組中):                Files and Directories.
                                                             (line  393)
* lstrip() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line  259)
* lstrip() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line  259)
* lstrip() (str 的方法):                 String Methods<2>.  (line  301)
* lsub() (imaplib.IMAP4 的方法):         IMAP4 Objects.      (line  150)
* lt() (於 operator 模組中):             operator --- Standard operators as functions.
                                                             (line   24)
* lt() (於 turtle 模組中):               Turtle motion.      (line   57)
* LWPCookieJar (http.cookiejar 中的類別): FileCookieJar subclasses and co-operation with web browsers.
                                                             (line   28)
* lzma (模組):                           lzma --- Compression using the LZMA algorithm.
                                                             (line    6)
* LZMACompressor (lzma 中的類別):        Compressing and decompressing data in memory.
                                                             (line    6)
* LZMADecompressor (lzma 中的類別):      Compressing and decompressing data in memory.
                                                             (line  100)
* LZMAError:                             lzma --- Compression using the LZMA algorithm.
                                                             (line   24)
* LZMAFile (lzma 中的類別):              Reading and writing compressed files.
                                                             (line   44)
* M (於 re 模組中):                      Module Contents.    (line  101)
* machine() (於 platform 模組中):        Cross Platform.     (line   37)
* macros (netrc.netrc 的屬性):           netrc Objects.      (line   29)
* mac_ver() (於 platform 模組中):        Mac OS Platform.    (line    6)
* madvise() (mmap.mmap 的方法):          mmap --- Memory-mapped file support.
                                                             (line  205)
* 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_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)
* magic method:                          Glossary.           (line  778)
* magic; method:                         Glossary.           (line  782)
* MagicMock (unittest.mock 中的類別):    Magic Mock.         (line    9)
* MAGIC_NUMBER (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   13)
* Mailbox (mailbox 中的類別):            Mailbox objects.    (line    6)
* mailbox (模組):                        mailbox --- Manipulate mailboxes in various formats.
                                                             (line    6)
* mailcap (模組):                        mailcap --- Mailcap file handling.
                                                             (line    6)
* Maildir (mailbox 中的類別):            Maildir.            (line    6)
* MaildirMessage (mailbox 中的類別):     MaildirMessage.     (line    6)
* mailfrom (smtpd.SMTPChannel 的屬性):   SMTPChannel Objects.
                                                             (line   74)
* MailmanProxy (smtpd 中的類別):         MailmanProxy Objects.
                                                             (line    6)
* main():                                Process-wide parameters.
                                                             (line    9)
* main() <1>:                            Process-wide parameters.
                                                             (line   36)
* main() <2>:                            Process-wide parameters.
                                                             (line  217)
* main() (於 py_compile 模組中):         py_compile --- Compile Python source files.
                                                             (line  124)
* main() (於 site 模組中):               Module contents<3>. (line   41)
* main() (於 unittest 模組中):           Loading and running tests.
                                                             (line  488)
* mainloop() (於 turtle 模組中):         Using screen events.
                                                             (line  106)
* maintype (email.headerregistry.ContentTypeHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  276)
* main_thread() (於 threading 模組中):   threading --- Thread-based parallelism.
                                                             (line  114)
* major (email.headerregistry.MIMEVersionHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  247)
* major() (於 os 模組中):                Files and Directories.
                                                             (line  528)
* makedev() (於 os 模組中):              Files and Directories.
                                                             (line  538)
* makedirs() (於 os 模組中):             Files and Directories.
                                                             (line  449)
* makeelement() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  174)
* makefile() (socket method):            The standard type hierarchy.
                                                             (line  629)
* makefile() (socket.socket 的方法):     Socket Objects.     (line  196)
* makeLogRecord() (於 logging 模組中):   Module-Level Functions.
                                                             (line  236)
* makePickle() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   45)
* makeRecord() (logging.Logger 的方法):  Logger Objects.     (line  300)
* makeSocket() (logging.handlers.DatagramHandler 的方法): DatagramHandler.
                                                             (line   28)
* makeSocket() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   39)
* maketrans() (bytearray 的靜態成員):    Bytes and Bytearray Operations.
                                                             (line  121)
* maketrans() (bytes 的靜態成員):        Bytes and Bytearray Operations.
                                                             (line  121)
* maketrans() (str 的靜態成員):          String Methods<2>.  (line  314)
* make_alternative() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  606)
* make_archive() (於 distutils.archive_util 模組中): distutils archive_util --- Archiving utilities.
                                                             (line    9)
* make_archive() (於 shutil 模組中):     Archiving operations.
                                                             (line   14)
* make_bad_fd() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  680)
* make_cookies() (http.cookiejar.CookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line   60)
* make_dataclass() (於 dataclasses 模組中): Module-level decorators classes and functions.
                                                             (line  309)
* make_file() (difflib.HtmlDiff 的方法): difflib --- Helpers for computing deltas.
                                                             (line  111)
* MAKE_FUNCTION (opcode):                Python Bytecode Instructions.
                                                             (line  839)
* make_header() (於 email.header 模組中): email header Internationalized headers.
                                                             (line  199)
* make_legacy_pyc() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  190)
* make_mixed() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  616)
* make_msgid() (於 email.utils 模組中):  email utils Miscellaneous utilities.
                                                             (line   29)
* make_parser() (於 xml.sax 模組中):     xml sax --- Support for SAX2 parsers.
                                                             (line   28)
* make_pkg() (於 test.support.script_helper 模組中): test support script_helper --- Utilities for the Python execution tests.
                                                             (line   86)
* make_related() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  597)
* make_script() (於 test.support.script_helper 模組中): test support script_helper --- Utilities for the Python execution tests.
                                                             (line   71)
* make_server() (於 wsgiref.simple_server 模組中): wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line   14)
* make_table() (difflib.HtmlDiff 的方法): difflib --- Helpers for computing deltas.
                                                             (line  143)
* make_tarball() (於 distutils.archive_util 模組中): distutils archive_util --- Archiving utilities.
                                                             (line   25)
* make_zipfile() (於 distutils.archive_util 模組中): distutils archive_util --- Archiving utilities.
                                                             (line   39)
* make_zip_pkg() (於 test.support.script_helper 模組中): test support script_helper --- Utilities for the Python execution tests.
                                                             (line   91)
* make_zip_script() (於 test.support.script_helper 模組中): test support script_helper --- Utilities for the Python execution tests.
                                                             (line   78)
* malloc():                              總覽<2>.            (line   33)
* mangle_from_ (email.policy.Compat32 的屬性): email policy Policy Objects.
                                                             (line  559)
* mangle_from_ (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  186)
* map (2to3 fixer):                      Fixers.             (line  185)
* map() (concurrent.futures.Executor 的方法): Executor Objects.
                                                             (line   22)
* map() (multiprocessing.pool.Pool 的方法): Process Pools.   (line   90)
* map() (tkinter.ttk.Style 的方法):      Ttk Styling.        (line   48)
* map() (內建函式):                      內建函式.           (line  911)
* mapLogRecord() (logging.handlers.HTTPHandler 的方法): HTTPHandler.
                                                             (line   27)
* mapping:                               Glossary.           (line  782)
* Mapping (collections.abc 中的類別):    Collections Abstract Base Classes.
                                                             (line  182)
* Mapping (typing 中的類別):             Classes functions and decorators.
                                                             (line  217)
* mapping() (msilib.Control 的方法):     GUI classes.        (line   20)
* MappingProxyType (types 中的類別):     Standard Interpreter Types.
                                                             (line  217)
* MappingView (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  187)
* MappingView (typing 中的類別):         Classes functions and decorators.
                                                             (line  282)
* mapPriority() (logging.handlers.SysLogHandler 的方法): SysLogHandler.
                                                             (line  182)
* maps (collections.ChainMap 的屬性):    ChainMap objects.   (line   39)
* maps() (於 nis 模組中):                nis --- Interface to Sun's NIS Yellow Pages.
                                                             (line   41)
* MAP_ADD (opcode):                      Python Bytecode Instructions.
                                                             (line  327)
* map_async() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line  107)
* map_table_b2() (於 stringprep 模組中): stringprep --- Internet String Preparation.
                                                             (line   50)
* map_table_b3() (於 stringprep 模組中): stringprep --- Internet String Preparation.
                                                             (line   55)
* map_to_type() (email.headerregistry.HeaderRegistry 的方法): email headerregistry Custom Header Objects.
                                                             (line  376)
* marshal (模組):                        marshal --- Internal Python object serialization.
                                                             (line    6)
* marshalling; objects:                  pickle --- Python object serialization.
                                                             (line    8)
* masking; operations:                   Bitwise Operations on Integer Types.
                                                             (line    6)
* Match (typing 中的類別):               Classes functions and decorators.
                                                             (line  478)
* match() (pathlib.PurePath 的方法):     Methods and properties.
                                                             (line  212)
* match() (re.Pattern 的方法):           Regular Expression Objects.
                                                             (line   37)
* match() (於 nis 模組中):               nis --- Interface to Sun's NIS Yellow Pages.
                                                             (line   16)
* match() (於 re 模組中):                Module Contents.    (line  152)
* Matcher (test.support 中的類別):       test support --- Utilities for the Python test suite.
                                                             (line 1085)
* matches() (test.support.Matcher 的方法): test support --- Utilities for the Python test suite.
                                                             (line 1087)
* match_hostname() (於 ssl 模組中):      Certificate handling.
                                                             (line    6)
* match_test() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  246)
* match_value() (test.support.Matcher 的方法): test support --- Utilities for the Python test suite.
                                                             (line 1091)
* math (模組):                           math --- Mathematical functions.
                                                             (line    6)
* matmul() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line  121)
* matrix multiplication:                 Binary arithmetic operations.
                                                             (line   23)
* max (datetime.date 的屬性):            date Objects.       (line   91)
* max (datetime.datetime 的屬性):        datetime Objects.   (line  252)
* max (datetime.time 的屬性):            time Objects.       (line   37)
* max (datetime.timedelta 的屬性):       timedelta Objects.  (line   78)
* max() (decimal.Context 的方法):        Context objects.    (line  367)
* max() (decimal.Decimal 的方法):        Decimal objects.    (line  374)
* max() (內建函式):                      內建函式.           (line  921)
* max() (於 audioop 模組中):             audioop --- Manipulate raw audio data.
                                                             (line  155)
* maxarray (reprlib.Repr 的屬性):        Repr Objects.       (line   15)
* maxdeque (reprlib.Repr 的屬性):        Repr Objects.       (line   15)
* maxdict (reprlib.Repr 的屬性):         Repr Objects.       (line   15)
* maxDiff (unittest.TestCase 的屬性):    Test cases.         (line  691)
* maxfrozenset (reprlib.Repr 的屬性):    Repr Objects.       (line   15)
* MAXIMUM_SUPPORTED (ssl.TLSVersion 的屬性): Constants<9>.   (line  531)
* maximum_version (ssl.SSLContext 的屬性): SSL Contexts.     (line  542)
* maxlen (collections.deque 的屬性):     deque objects.      (line  120)
* maxlevel (reprlib.Repr 的屬性):        Repr Objects.       (line   10)
* maxlist (reprlib.Repr 的屬性):         Repr Objects.       (line   15)
* maxlong (reprlib.Repr 的屬性):         Repr Objects.       (line   27)
* maxother (reprlib.Repr 的屬性):        Repr Objects.       (line   40)
* maxpp() (於 audioop 模組中):           audioop --- Manipulate raw audio data.
                                                             (line  160)
* maxset (reprlib.Repr 的屬性):          Repr Objects.       (line   15)
* maxsize (asyncio.Queue 的屬性):        Queue.              (line   24)
* maxsize (於 sys 模組中):               sys --- System-specific parameters and functions.
                                                             (line 1007)
* maxstring (reprlib.Repr 的屬性):       Repr Objects.       (line   32)
* maxtuple (reprlib.Repr 的屬性):        Repr Objects.       (line   15)
* maxunicode (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line 1013)
* MAXYEAR (於 datetime 模組中):          Constants.          (line   13)
* max_count (email.headerregistry.BaseHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line   60)
* MAX_EMAX (於 decimal 模組中):          Constants<4>.       (line   16)
* MAX_INTERPOLATION_DEPTH (於 configparser 模組中): ConfigParser Objects.
                                                             (line  319)
* max_lines (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  258)
* max_line_length (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  145)
* max_mag() (decimal.Context 的方法):    Context objects.    (line  371)
* max_mag() (decimal.Decimal 的方法):    Decimal objects.    (line  381)
* max_memuse (於 test.support 模組中):   test support --- Utilities for the Python test suite.
                                                             (line  122)
* MAX_PREC (於 decimal 模組中):          Constants<4>.       (line   13)
* max_prefixlen (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line   43)
* max_prefixlen (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   65)
* max_prefixlen (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  169)
* max_prefixlen (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  295)
* MAX_Py_ssize_t (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  118)
* mbox (mailbox 中的類別):               mbox.               (line    6)
* mboxMessage (mailbox 中的類別):        mboxMessage.        (line    6)
* MB_ICONASTERISK (於 winsound 模組中):  winsound --- Sound-playing interface for Windows.
                                                             (line  128)
* MB_ICONEXCLAMATION (於 winsound 模組中): winsound --- Sound-playing interface for Windows.
                                                             (line  132)
* MB_ICONHAND (於 winsound 模組中):      winsound --- Sound-playing interface for Windows.
                                                             (line  136)
* MB_ICONQUESTION (於 winsound 模組中):  winsound --- Sound-playing interface for Windows.
                                                             (line  140)
* MB_OK (於 winsound 模組中):            winsound --- Sound-playing interface for Windows.
                                                             (line  144)
* mean (statistics.NormalDist 的屬性):   NormalDist objects. (line   21)
* mean() (於 statistics 模組中):         函式細節.           (line   10)
* median (statistics.NormalDist 的屬性): NormalDist objects. (line   26)
* median() (於 statistics 模組中):       函式細節.           (line  121)
* median_grouped() (於 statistics 模組中): 函式細節.         (line  184)
* median_high() (於 statistics 模組中):  函式細節.           (line  166)
* median_low() (於 statistics 模組中):   函式細節.           (line  148)
* MemberDescriptorType (於 types 模組中): Standard Interpreter Types.
                                                             (line  206)
* membership; test:                      Membership test operations.
                                                             (line   37)
* memfd_create() (於 os 模組中):         Files and Directories.
                                                             (line 1633)
* memmove() (於 ctypes 模組中):          Utility functions.  (line  137)
* MemoryBIO (ssl 中的類別):              Memory BIO Support<2>.
                                                             (line  134)
* MemoryError:                           Concrete exceptions.
                                                             (line   78)
* MemoryHandler (logging.handlers 中的類別): MemoryHandler.  (line   40)
* memoryview (內建類別):                 Memory Views.       (line   10)
* memset() (於 ctypes 模組中):           Utility functions.  (line  143)
* merge() (於 heapq 模組中):             heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   67)
* Message (email.message 中的類別):      email message Message Representing an email message using the compat32 API.
                                                             (line   49)
* Message (mailbox 中的類別):            Message objects.    (line    6)
* message digest, MD5:                   hashlib --- Secure hashes and message digests.
                                                             (line    8)
* MessageBeep() (於 winsound 模組中):    winsound --- Sound-playing interface for Windows.
                                                             (line   31)
* MessageClass (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  165)
* MessageError:                          email errors Exception and Defect classes.
                                                             (line   13)
* MessageParseError:                     email errors Exception and Defect classes.
                                                             (line   19)
* messages (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line   22)
* message_factory (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  195)
* message_from_binary_file() (於 email 模組中): Parser API.  (line  127)
* message_from_bytes() (於 email 模組中): Parser API.        (line  114)
* message_from_file() (於 email 模組中): Parser API.         (line  150)
* message_from_string() (於 email 模組中): Parser API.       (line  140)
* meta hooks:                            Import hooks.       (line    6)
* meta path finder:                      Glossary.           (line  791)
* meta() (於 curses 模組中):             Functions<3>.       (line  271)
* metaclass:                             Metaclasses.        (line    6)
* metaclass <1>:                         Glossary.           (line  800)
* metaclass (2to3 fixer):                Fixers.             (line  191)
* metaclass hint:                        Determining the appropriate metaclass.
                                                             (line    6)
* MetaPathFinder (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line   45)
* metavar (optparse.Option 的屬性):      Option attributes.  (line   80)
* MetavarTypeHelpFormatter (argparse 中的類別): formatter_class.
                                                             (line   10)
* meta_path (於 sys 模組中):             sys --- System-specific parameters and functions.
                                                             (line 1022)
* Meter (tkinter.tix 中的類別):          Basic Widgets.      (line   44)
* method:                                Glossary.           (line  815)
* method (urllib.request.Request 的屬性): Request Objects.   (line   51)
* method resolution order:               Glossary.           (line  823)
* method; call:                          Calls.              (line  132)
* methodattrs (2to3 fixer):              Fixers.             (line  196)
* methodcaller() (於 operator 模組中):   operator --- Standard operators as functions.
                                                             (line  307)
* MethodDescriptorType (於 types 模組中): Standard Interpreter Types.
                                                             (line  103)
* methodHelp() (xmlrpc.client.ServerProxy.system 的方法): ServerProxy Objects.
                                                             (line   43)
* methods (pyclbr.Class 的屬性):         Class Objects<2>.   (line   46)
* methods (於 crypt 模組中):             Module Attributes.  (line    8)
* methodSignature() (xmlrpc.client.ServerProxy.system 的方法): ServerProxy Objects.
                                                             (line   22)
* MethodType (in module types):          函式（Function）物件.
                                                             (line   14)
* MethodType (in module types) <1>:      Method Objects<2>.  (line   12)
* MethodType (於 types 模組中):          Standard Interpreter Types.
                                                             (line   77)
* MethodWrapperType (於 types 模組中):   Standard Interpreter Types.
                                                             (line   96)
* METHOD_BLOWFISH (於 crypt 模組中):     Hashing Methods.    (line   22)
* method_calls (unittest.mock.Mock 的屬性): The Mock Class.  (line  482)
* METHOD_CRYPT (於 crypt 模組中):        Hashing Methods.    (line   34)
* METHOD_MD5 (於 crypt 模組中):          Hashing Methods.    (line   29)
* METHOD_SHA256 (於 crypt 模組中):       Hashing Methods.    (line   17)
* METHOD_SHA512 (於 crypt 模組中):       Hashing Methods.    (line   11)
* METH_CLASS (內建變數):                 通用物件結構.       (line  225)
* METH_COEXIST (內建變數):               通用物件結構.       (line  242)
* METH_FASTCALL (內建變數):              通用物件結構.       (line  176)
* METH_NOARGS (內建變數):                通用物件結構.       (line  203)
* METH_O (內建變數):                     通用物件結構.       (line  212)
* METH_STATIC (內建變數):                通用物件結構.       (line  232)
* METH_VARARGS (內建變數):               通用物件結構.       (line  157)
* MFD_ALLOW_SEALING (於 os 模組中):      Files and Directories.
                                                             (line 1652)
* MFD_CLOEXEC (於 os 模組中):            Files and Directories.
                                                             (line 1652)
* MFD_HUGETLB (於 os 模組中):            Files and Directories.
                                                             (line 1652)
* MFD_HUGE_16GB (於 os 模組中):          Files and Directories.
                                                             (line 1652)
* MFD_HUGE_16MB (於 os 模組中):          Files and Directories.
                                                             (line 1652)
* MFD_HUGE_1GB (於 os 模組中):           Files and Directories.
                                                             (line 1652)
* MFD_HUGE_1MB (於 os 模組中):           Files and Directories.
                                                             (line 1652)
* MFD_HUGE_256MB (於 os 模組中):         Files and Directories.
                                                             (line 1652)
* MFD_HUGE_2GB (於 os 模組中):           Files and Directories.
                                                             (line 1652)
* MFD_HUGE_2MB (於 os 模組中):           Files and Directories.
                                                             (line 1652)
* MFD_HUGE_32MB (於 os 模組中):          Files and Directories.
                                                             (line 1652)
* MFD_HUGE_512KB (於 os 模組中):         Files and Directories.
                                                             (line 1652)
* MFD_HUGE_512MB (於 os 模組中):         Files and Directories.
                                                             (line 1652)
* MFD_HUGE_64KB (於 os 模組中):          Files and Directories.
                                                             (line 1652)
* MFD_HUGE_8MB (於 os 模組中):           Files and Directories.
                                                             (line 1652)
* MFD_HUGE_MASK (於 os 模組中):          Files and Directories.
                                                             (line 1652)
* MFD_HUGE_SHIFT (於 os 模組中):         Files and Directories.
                                                             (line 1652)
* MH (mailbox 中的類別):                 MH.                 (line    6)
* MHMessage (mailbox 中的類別):          MHMessage.          (line    6)
* microsecond (datetime.datetime 的屬性): datetime Objects.  (line  289)
* microsecond (datetime.time 的屬性):    time Objects.       (line   62)
* MIME; base64 encoding:                 base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line    8)
* MIME; content type:                    mimetypes --- Map filenames to MIME types.
                                                             (line    8)
* MIME; headers:                         mimetypes --- Map filenames to MIME types.
                                                             (line   26)
* MIME; headers <1>:                     cgi --- Common Gateway Interface support.
                                                             (line    8)
* MIME; quoted-printable encoding:       quopri --- Encode and decode MIME quoted-printable data.
                                                             (line    8)
* MIMEApplication (email.mime.application 中的類別): email mime Creating email and MIME objects from scratch.
                                                             (line   95)
* MIMEAudio (email.mime.audio 中的類別): email mime Creating email and MIME objects from scratch.
                                                             (line  125)
* MIMEBase (email.mime.base 中的類別):   email mime Creating email and MIME objects from scratch.
                                                             (line   30)
* MIMEImage (email.mime.image 中的類別): email mime Creating email and MIME objects from scratch.
                                                             (line  158)
* MIMEMessage (email.mime.message 中的類別): email mime Creating email and MIME objects from scratch.
                                                             (line  191)
* MIMEMultipart (email.mime.multipart 中的類別): email mime Creating email and MIME objects from scratch.
                                                             (line   66)
* MIMENonMultipart (email.mime.nonmultipart 中的類別): email mime Creating email and MIME objects from scratch.
                                                             (line   55)
* MIMEPart (email.message 中的類別):     email message Representing an email message.
                                                             (line  717)
* MIMEText (email.mime.text 中的類別):   email mime Creating email and MIME objects from scratch.
                                                             (line  209)
* MimeTypes (mimetypes 中的類別):        MimeTypes Objects.  (line   10)
* mimetypes (模組):                      mimetypes --- Map filenames to MIME types.
                                                             (line    6)
* MIMEVersionHeader (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  234)
* min (datetime.date 的屬性):            date Objects.       (line   87)
* min (datetime.datetime 的屬性):        datetime Objects.   (line  247)
* min (datetime.time 的屬性):            time Objects.       (line   33)
* min (datetime.timedelta 的屬性):       timedelta Objects.  (line   73)
* min() (decimal.Context 的方法):        Context objects.    (line  375)
* min() (decimal.Decimal 的方法):        Decimal objects.    (line  386)
* min() (內建函式):                      內建函式.           (line  953)
* MINEQUAL (於 token 模組中):            token --- Constants used with Python parse trees.
                                                             (line  174)
* MINIMUM_SUPPORTED (ssl.TLSVersion 的屬性): Constants<9>.   (line  529)
* minimum_version (ssl.SSLContext 的屬性): SSL Contexts.     (line  563)
* minmax() (於 audioop 模組中):          audioop --- Manipulate raw audio data.
                                                             (line  164)
* minor (email.headerregistry.MIMEVersionHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  251)
* minor() (於 os 模組中):                Files and Directories.
                                                             (line  533)
* minus:                                 Unary arithmetic and bitwise operations.
                                                             (line   10)
* MINUS (於 token 模組中):               token --- Constants used with Python parse trees.
                                                             (line   86)
* minus() (decimal.Context 的方法):      Context objects.    (line  383)
* minute (datetime.datetime 的屬性):     datetime Objects.   (line  281)
* minute (datetime.time 的屬性):         time Objects.       (line   54)
* MINYEAR (於 datetime 模組中):          Constants.          (line    8)
* MIN_EMIN (於 decimal 模組中):          Constants<4>.       (line   19)
* MIN_ETINY (於 decimal 模組中):         Constants<4>.       (line   22)
* min_mag() (decimal.Context 的方法):    Context objects.    (line  379)
* min_mag() (decimal.Decimal 的方法):    Decimal objects.    (line  393)
* mirrored() (於 unicodedata 模組中):    unicodedata --- Unicode Database.
                                                             (line   69)
* misc_header (cmd.Cmd 的屬性):          Cmd Objects.        (line  152)
* MISSING (contextvars.contextvars.Token.Token 的屬性): Context Variables.
                                                             (line   94)
* MissingSectionHeaderError:             Exceptions<4>.      (line   60)
* missing_compiler_executable() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  960)
* MISSING_C_DOCSTRINGS (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  132)
* MIXERDEV:                              ossaudiodev --- Access to OSS-compatible audio devices.
                                                             (line   74)
* mkd() (ftplib.FTP 的方法):             FTP Objects.        (line  217)
* mkdir() (pathlib.Path 的方法):         Methods<2>.         (line  220)
* mkdir() (於 os 模組中):                Files and Directories.
                                                             (line  424)
* mkdtemp() (於 tempfile 模組中):        tempfile --- Generate temporary files and directories.
                                                             (line  198)
* mkfifo() (於 os 模組中):               Files and Directories.
                                                             (line  487)
* mknod() (於 os 模組中):                Files and Directories.
                                                             (line  508)
* mkpath() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  492)
* mkpath() (於 distutils.dir_util 模組中): distutils dir_util --- Directory tree operations.
                                                             (line    9)
* mksalt() (於 crypt 模組中):            Module Functions<2>.
                                                             (line   39)
* mkstemp() (於 tempfile 模組中):        tempfile --- Generate temporary files and directories.
                                                             (line  141)
* mktemp() (於 tempfile 模組中):         Deprecated functions and variables.
                                                             (line   15)
* mktime() (於 time 模組中):             Functions<2>.       (line  148)
* mktime_tz() (於 email.utils 模組中):   email utils Miscellaneous utilities.
                                                             (line  133)
* mlsd() (ftplib.FTP 的方法):            FTP Objects.        (line  165)
* mmap (mmap 中的類別):                  mmap --- Memory-mapped file support.
                                                             (line   48)
* mmap (模組):                           mmap --- Memory-mapped file support.
                                                             (line    6)
* MMDF (mailbox 中的類別):               MMDF.               (line    6)
* MMDFMessage (mailbox 中的類別):        MMDFMessage.        (line    6)
* Mock (unittest.mock 中的類別):         The Mock Class.     (line   24)
* mock_add_spec() (unittest.mock.Mock 的方法): The Mock Class.
                                                             (line  226)
* mock_calls (unittest.mock.Mock 的屬性): The Mock Class.    (line  500)
* mock_open() (於 unittest.mock 模組中): mock_open.          (line    6)
* mod() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line  111)
* mode (io.FileIO 的屬性):               Raw File I/O.       (line   57)
* mode (ossaudiodev.oss_audio_device 的屬性): Audio Device Objects.
                                                             (line  235)
* mode (statistics.NormalDist 的屬性):   NormalDist objects. (line   31)
* mode (tarfile.TarInfo 的屬性):         TarInfo Objects.    (line   55)
* mode() (於 statistics 模組中):         函式細節.           (line  229)
* mode() (於 turtle 模組中):             Settings and special methods.
                                                             (line    6)
* modf() (於 math 模組中):               Number-theoretic and representation functions.
                                                             (line  172)
* modified() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- Parser for robots txt.
                                                             (line   45)
* Modify() (msilib.View 的方法):         View Objects.       (line   23)
* 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:                                Glossary.           (line  830)
* module (pyclbr.Class 的屬性):          Class Objects<2>.   (line   13)
* module (pyclbr.Function 的屬性):       函式物件.           (line   13)
* module spec:                           Finders and loaders.
                                                             (line    6)
* module spec <1>:                       Glossary.           (line  839)
* module; importing:                     The import statement.
                                                             (line    6)
* module; namespace:                     The standard type hierarchy.
                                                             (line  535)
* module; search; path:                  The Module Search Path.
                                                             (line    6)
* module; search; path <1>:              linecache --- Random access to text lines.
                                                             (line   30)
* module; search; path <2>:              sys --- System-specific parameters and functions.
                                                             (line 1062)
* module; search; path <3>:              site --- Site-specific configuration hook.
                                                             (line   14)
* module; search; path <4>:              嵌入式Python.       (line   12)
* module; search; path <5>:              Initializing and finalizing the interpreter.
                                                             (line    8)
* module; search; path <6>:              Process-wide parameters.
                                                             (line  120)
* module; search; path <7>:              Process-wide parameters.
                                                             (line  133)
* ModuleFinder (modulefinder 中的類別):  modulefinder --- Find modules used by a script.
                                                             (line   26)
* modulefinder (模組):                   modulefinder --- Find modules used by a script.
                                                             (line    6)
* ModuleInfo (pkgutil 中的類別):         pkgutil --- Package extension utility.
                                                             (line   13)
* ModuleNotFoundError:                   Concrete exceptions.
                                                             (line   51)
* modules (in module sys):               匯入模組<2>.        (line    7)
* modules (in module sys) <1>:           Initializing and finalizing the interpreter.
                                                             (line    8)
* modules (modulefinder.ModuleFinder 的屬性): modulefinder --- Find modules used by a script.
                                                             (line   49)
* modules (於 sys 模組中):               sys --- System-specific parameters and functions.
                                                             (line 1052)
* ModuleSpec (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  344)
* modules_cleanup() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  772)
* modules_setup() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  768)
* ModuleType (in module types):          模組物件模組.       (line    8)
* ModuleType (types 中的類別):           Standard Interpreter Types.
                                                             (line  117)
* module_for_loader() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  133)
* module_from_spec() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  117)
* module_repr() (importlib.abc.Loader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  263)
* modulo:                                Binary arithmetic operations.
                                                             (line   35)
* monotonic() (於 time 模組中):          Functions<2>.       (line  161)
* monotonic_ns() (於 time 模組中):       Functions<2>.       (line  174)
* month (datetime.date 的屬性):          date Objects.       (line  106)
* month (datetime.datetime 的屬性):      datetime Objects.   (line  268)
* month() (於 calendar 模組中):          calendar --- General calendar-related functions.
                                                             (line  339)
* monthcalendar() (於 calendar 模組中):  calendar --- General calendar-related functions.
                                                             (line  328)
* monthdatescalendar() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line   89)
* monthdays2calendar() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line   95)
* monthdayscalendar() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line  101)
* monthrange() (於 calendar 模組中):     calendar --- General calendar-related functions.
                                                             (line  323)
* month_abbr (於 calendar 模組中):       calendar --- General calendar-related functions.
                                                             (line  383)
* month_name (於 calendar 模組中):       calendar --- General calendar-related functions.
                                                             (line  376)
* Morsel (http.cookies 中的類別):        Morsel Objects.     (line    6)
* most_common() (collections.Counter 的方法): Counter 物件.  (line   74)
* mouseinterval() (於 curses 模組中):    Functions<3>.       (line  276)
* mousemask() (於 curses 模組中):        Functions<3>.       (line  283)
* move() (curses.panel.Panel 的方法):    Panel Objects.      (line   35)
* move() (curses.window 的方法):         Window Objects.     (line  393)
* move() (mmap.mmap 的方法):             mmap --- Memory-mapped file support.
                                                             (line  218)
* move() (tkinter.ttk.Treeview 的方法):  ttk Treeview.       (line  221)
* move() (於 shutil 模組中):             Directory and files operations.
                                                             (line  302)
* move_file() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  497)
* move_file() (於 distutils.file_util 模組中): distutils file_util --- Single file operations.
                                                             (line   34)
* move_to_end() (collections.OrderedDict 的方法): OrderedDict objects.
                                                             (line   53)
* MozillaCookieJar (http.cookiejar 中的類別): FileCookieJar subclasses and co-operation with web browsers.
                                                             (line    9)
* MRO:                                   Glossary.           (line  845)
* mro() (class 的方法):                  Special Attributes. (line   40)
* msg (http.client.HTTPResponse 的屬性): HTTPResponse Objects.
                                                             (line   40)
* msg (json.JSONDecodeError 的屬性):     例外<2>.            (line   11)
* msg (re.error 的屬性):                 Module Contents.    (line  360)
* msg (traceback.TracebackException 的屬性): TracebackException Objects.
                                                             (line   59)
* msg() (telnetlib.Telnet 的方法):       Telnet Objects.     (line   78)
* msi:                                   msilib --- Read and write Microsoft Installer files.
                                                             (line    8)
* msilib (模組):                         msilib --- Read and write Microsoft Installer files.
                                                             (line    6)
* msvcrt (模組):                         msvcrt --- Useful routines from the MS VC++ runtime.
                                                             (line    6)
* mtime (gzip.GzipFile 的屬性):          gzip --- Support for gzip files.
                                                             (line  139)
* mtime (tarfile.TarInfo 的屬性):        TarInfo Objects.    (line   51)
* mtime() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- Parser for robots txt.
                                                             (line   39)
* mt_interact() (telnetlib.Telnet 的方法): Telnet Objects.   (line  117)
* mul() (於 audioop 模組中):             audioop --- Manipulate raw audio data.
                                                             (line  169)
* mul() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line  116)
* MultiCall (xmlrpc.client 中的類別):    MultiCall Objects.  (line    9)
* MULTILINE (於 re 模組中):              Module Contents.    (line  101)
* MultiLoopChildWatcher (asyncio 中的類別): Process Watchers.
                                                             (line  100)
* multimode() (於 statistics 模組中):    函式細節.           (line  257)
* MultipartConversionError:              email errors Exception and Defect classes.
                                                             (line   42)
* multiplication:                        Binary arithmetic operations.
                                                             (line   16)
* multiply() (decimal.Context 的方法):   Context objects.    (line  388)
* multiprocessing (模組):                multiprocessing --- Process-based parallelism.
                                                             (line    6)
* multiprocessing.connection (模組):     Listeners and Clients.
                                                             (line    6)
* multiprocessing.dummy (模組):          The multiprocessing dummy module.
                                                             (line    6)
* multiprocessing.Manager() (於 multiprocessing.sharedctypes 模組中): Managers.
                                                             (line   12)
* multiprocessing.managers (模組):       Managers.           (line   18)
* multiprocessing.pool (模組):           Process Pools.      (line    6)
* multiprocessing.sharedctypes (模組):   The multiprocessing sharedctypes module.
                                                             (line    6)
* multiprocessing.shared_memory (模組):  multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line    6)
* mutable:                               Glossary.           (line  849)
* mutable object:                        Objects values and types.
                                                             (line   11)
* mutable sequence; loop over:           The for statement.  (line   44)
* mutable; sequence; types:              Mutable Sequence Types.
                                                             (line    6)
* MutableMapping (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  182)
* MutableMapping (typing 中的類別):      Classes functions and decorators.
                                                             (line  225)
* MutableSequence (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  159)
* MutableSequence (typing 中的類別):     Classes functions and decorators.
                                                             (line  233)
* MutableSet (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  177)
* MutableSet (typing 中的類別):          Classes functions and decorators.
                                                             (line  213)
* mvderwin() (curses.window 的方法):     Window Objects.     (line  397)
* mvwin() (curses.window 的方法):        Window Objects.     (line  404)
* myrights() (imaplib.IMAP4 的方法):     IMAP4 Objects.      (line  157)
* name:                                  Identifiers and keywords.
                                                             (line    6)
* name <1>:                              Binding of names.   (line    6)
* name <2>:                              Identifiers Names.  (line    6)
* name (codecs.CodecInfo 的屬性):        codecs --- Codec registry and base classes.
                                                             (line   65)
* name (contextvars.ContextVar 的屬性):  Context Variables.  (line   24)
* name (doctest.DocTest 的屬性):         DocTest Objects.    (line   30)
* name (email.headerregistry.BaseHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line   45)
* name (hashlib.hash 的屬性):            Hash algorithms.    (line  105)
* name (hmac.HMAC 的屬性):               hmac --- Keyed-Hashing for Message Authentication.
                                                             (line   99)
* name (http.cookiejar.Cookie 的屬性):   Cookie Objects<2>.  (line   28)
* name (importlib.abc.FileLoader 的屬性): importlib abc -- Abstract base classes related to import.
                                                             (line  472)
* name (importlib.machinery.ExtensionFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  303)
* name (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  360)
* name (importlib.machinery.SourceFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  216)
* name (importlib.machinery.SourcelessFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  260)
* name (inspect.Parameter 的屬性):       Introspecting callables with the Signature object.
                                                             (line  156)
* name (io.FileIO 的屬性):               Raw File I/O.       (line   61)
* name (multiprocessing.Process 的屬性): Process and exceptions.
                                                             (line   67)
* name (multiprocessing.shared_memory.SharedMemory 的屬性): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line   91)
* name (os.DirEntry 的屬性):             Files and Directories.
                                                             (line  840)
* name (ossaudiodev.oss_audio_device 的屬性): Audio Device Objects.
                                                             (line  231)
* name (pyclbr.Class 的屬性):            Class Objects<2>.   (line   17)
* name (pyclbr.Function 的屬性):         函式物件.           (line   17)
* name (tarfile.TarInfo 的屬性):         TarInfo Objects.    (line   43)
* name (threading.Thread 的屬性):        Thread Objects.     (line  136)
* name (xml.dom.Attr 的屬性):            Attr Objects.       (line    8)
* name (xml.dom.DocumentType 的屬性):    DocumentType Objects.
                                                             (line   33)
* name (zipfile.Path 的屬性):            Path Objects.       (line   22)
* name (於 os 模組中):                   os --- Miscellaneous operating system interfaces.
                                                             (line   46)
* NAME (於 token 模組中):                token --- Constants used with Python parse trees.
                                                             (line   42)
* name() (於 unicodedata 模組中):        unicodedata --- Unicode Database.
                                                             (line   25)
* name2codepoint (於 html.entities 模組中): html entities --- Definitions of HTML general entities.
                                                             (line   30)
* name; binding:                         The import statement.
                                                             (line    6)
* name; binding <1>:                     The import statement.
                                                             (line   51)
* name; binding <2>:                     Function definitions.
                                                             (line    6)
* name; binding <3>:                     Function definitions.
                                                             (line    6)
* name; binding <4>:                     Class definitions.  (line    6)
* name; mangling:                        Private Variables.  (line   13)
* name; mangling <1>:                    Identifiers Names.  (line   14)
* Named Shared Memory:                   multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line   10)
* named tuple:                           Glossary.           (line  854)
* NamedTemporaryFile() (於 tempfile 模組中): tempfile --- Generate temporary files and directories.
                                                             (line   71)
* NamedTuple (typing 中的類別):          Classes functions and decorators.
                                                             (line  487)
* namedtuple() (於 collections 模組中):  namedtuple Factory Function for Tuples with Named Fields.
                                                             (line   11)
* NameError:                             Concrete exceptions.
                                                             (line   89)
* NameError (built-in exception):        Resolution of names.
                                                             (line   16)
* namelist() (zipfile.ZipFile 的方法):   ZipFile Objects.    (line  105)
* 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  157)
* namespace:                             Naming and binding. (line    6)
* namespace <1>:                         Glossary.           (line  880)
* Namespace (argparse 中的類別):         The Namespace object.
                                                             (line    6)
* Namespace (multiprocessing.managers 中的類別): Managers.   (line  225)
* namespace package:                     Glossary.           (line  894)
* namespace() (imaplib.IMAP4 的方法):    IMAP4 Objects.      (line  162)
* Namespace() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  175)
* NamespaceErr:                          Exceptions<14>.     (line   66)
* namespaceURI (xml.dom.Node 的屬性):    Node Objects.       (line   74)
* NAMESPACE_DNS (於 uuid 模組中):        uuid --- UUID objects according to RFC 4122.
                                                             (line  203)
* NAMESPACE_OID (於 uuid 模組中):        uuid --- UUID objects according to RFC 4122.
                                                             (line  212)
* NAMESPACE_URL (於 uuid 模組中):        uuid --- UUID objects according to RFC 4122.
                                                             (line  208)
* NAMESPACE_X500 (於 uuid 模組中):       uuid --- UUID objects according to RFC 4122.
                                                             (line  216)
* NaN:                                   內建函式.           (line  583)
* nan (於 cmath 模組中):                 Constants<3>.       (line   33)
* nan (於 math 模組中):                  Constants<2>.       (line   33)
* nanj (於 cmath 模組中):                Constants<3>.       (line   40)
* NannyNag:                              tabnanny --- Detection of ambiguous indentation.
                                                             (line   37)
* napms() (於 curses 模組中):            Functions<3>.       (line  292)
* nargs (optparse.Option 的屬性):        Option attributes.  (line   42)
* native_id (threading.Thread 的屬性):   Thread Objects.     (line  156)
* nbytes (memoryview 的屬性):            Memory Views.       (line  373)
* ncurses_version (於 curses 模組中):    Constants<6>.       (line   23)
* ndiff() (於 difflib 模組中):           difflib --- Helpers for computing deltas.
                                                             (line  233)
* ndim (memoryview 的屬性):              Memory Views.       (line  439)
* ne (2to3 fixer):                       Fixers.             (line  201)
* ne() (於 operator 模組中):             operator --- Standard operators as functions.
                                                             (line   24)
* needs_input (bz2.BZ2Decompressor 的屬性): Incremental de compression.
                                                             (line   85)
* needs_input (lzma.LZMADecompressor 的屬性): Compressing and decompressing data in memory.
                                                             (line  175)
* neg() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line  128)
* negation:                              Unary arithmetic and bitwise operations.
                                                             (line   10)
* nested scope:                          Glossary.           (line  903)
* netmask (ipaddress.IPv4Network 的屬性): Network objects.   (line  101)
* netmask (ipaddress.IPv6Network 的屬性): Network objects.   (line  315)
* NetmaskValueError:                     Custom Exceptions.  (line   13)
* netrc (netrc 中的類別):                netrc --- netrc file processing.
                                                             (line   13)
* netrc (模組):                          netrc --- netrc file processing.
                                                             (line    6)
* NetrcParseError:                       netrc --- netrc file processing.
                                                             (line   36)
* netscape (http.cookiejar.CookiePolicy 的屬性): CookiePolicy Objects.
                                                             (line   68)
* network (ipaddress.IPv4Interface 的屬性): Interface objects.
                                                             (line   28)
* network (ipaddress.IPv6Interface 的屬性): Interface objects.
                                                             (line   76)
* Network News Transfer Protocol:        nntplib --- NNTP protocol client.
                                                             (line    8)
* network_address (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line   86)
* network_address (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  309)
* new() (於 hashlib 模組中):             Hash algorithms.    (line   55)
* new() (於 hmac 模組中):                hmac --- Keyed-Hashing for Message Authentication.
                                                             (line   12)
* new-style class:                       Glossary.           (line  913)
* newer() (於 distutils.dep_util 模組中): distutils dep_util --- Dependency checking.
                                                             (line   10)
* newer_group() (於 distutils.dep_util 模組中): distutils dep_util --- Dependency checking.
                                                             (line   24)
* newer_pairwise() (於 distutils.dep_util 模組中): distutils dep_util --- Dependency checking.
                                                             (line   17)
* newfunc (C 型態):                      Slot Type typedefs. (line   41)
* newgroups() (nntplib.NNTP 的方法):     Methods<3>.         (line   80)
* NEWLINE (於 token 模組中):             token --- Constants used with Python parse trees.
                                                             (line   48)
* NEWLINE token:                         Logical lines.      (line    6)
* NEWLINE token <1>:                     Compound statements.
                                                             (line   54)
* newlines (io.TextIOBase 的屬性):       Text I/O<2>.        (line   24)
* newnews() (nntplib.NNTP 的方法):       Methods<3>.         (line   95)
* newpad() (於 curses 模組中):           Functions<3>.       (line  296)
* NewType() (於 typing 模組中):          Classes functions and decorators.
                                                             (line  605)
* newwin() (於 curses 模組中):           Functions<3>.       (line  316)
* new_alignment() (formatter.writer 的方法): The Writer Interface.
                                                             (line   17)
* new_child() (collections.ChainMap 的方法): ChainMap objects.
                                                             (line   46)
* new_class() (於 types 模組中):         Dynamic Type Creation.
                                                             (line    6)
* new_compiler() (於 distutils.ccompiler 模組中): distutils ccompiler --- CCompiler base class.
                                                             (line   47)
* new_event_loop() (asyncio.AbstractEventLoopPolicy 的方法): Policy Objects.
                                                             (line   27)
* new_event_loop() (於 asyncio 模組中):  Event Loop.         (line   61)
* new_font() (formatter.writer 的方法):  The Writer Interface.
                                                             (line   25)
* new_margin() (formatter.writer 的方法): The Writer Interface.
                                                             (line   35)
* new_module() (於 imp 模組中):          imp --- Access the import internals.
                                                             (line  124)
* new_panel() (於 curses.panel 模組中):  Functions<4>.       (line   12)
* new_spacing() (formatter.writer 的方法): The Writer Interface.
                                                             (line   42)
* new_styles() (formatter.writer 的方法): The Writer Interface.
                                                             (line   46)
* next (2to3 fixer):                     Fixers.             (line  205)
* next (pdb command):                    Debugger Commands.  (line  168)
* next() (nntplib.NNTP 的方法):          Methods<3>.         (line  233)
* next() (tarfile.TarFile 的方法):       TarFile Objects.    (line  129)
* next() (tkinter.ttk.Treeview 的方法):  ttk Treeview.       (line  232)
* next() (內建函式):                     內建函式.           (line  980)
* nextfile() (於 fileinput 模組中):      fileinput --- Iterate over lines from multiple input streams.
                                                             (line  116)
* nextkey() (dbm.gnu.gdbm 的方法):       dbm gnu --- GNU's reinterpretation of dbm.
                                                             (line   93)
* nextSibling (xml.dom.Node 的屬性):     Node Objects.       (line   42)
* next_minus() (decimal.Context 的方法): Context objects.    (line  392)
* next_minus() (decimal.Decimal 的方法): Decimal objects.    (line  398)
* next_plus() (decimal.Context 的方法):  Context objects.    (line  396)
* next_plus() (decimal.Decimal 的方法):  Decimal objects.    (line  404)
* next_toward() (decimal.Context 的方法): Context objects.   (line  400)
* next_toward() (decimal.Decimal 的方法): Decimal objects.   (line  410)
* ngettext() (gettext.GNUTranslations 的方法): The GNUTranslations class.
                                                             (line   47)
* ngettext() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   41)
* ngettext() (於 gettext 模組中):        GNU gettext API.    (line   54)
* nice() (於 os 模組中):                 Process Management. (line  318)
* nis (模組):                            nis --- Interface to Sun's NIS Yellow Pages.
                                                             (line    6)
* NL (於 token 模組中):                  token --- Constants used with Python parse trees.
                                                             (line  265)
* nl() (於 curses 模組中):               Functions<3>.       (line  326)
* nlargest() (於 heapq 模組中):          heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   90)
* nlst() (ftplib.FTP 的方法):            FTP Objects.        (line  179)
* nl_langinfo() (於 locale 模組中):      locale --- Internationalization services.
                                                             (line  172)
* NNTP (nntplib 中的類別):               nntplib --- NNTP protocol client.
                                                             (line   54)
* NNTP; protocol:                        nntplib --- NNTP protocol client.
                                                             (line    8)
* NNTPDataError:                         nntplib --- NNTP protocol client.
                                                             (line  152)
* NNTPError:                             nntplib --- NNTP protocol client.
                                                             (line  121)
* nntplib (模組):                        nntplib --- NNTP protocol client.
                                                             (line    6)
* NNTPPermanentError:                    nntplib --- NNTP protocol client.
                                                             (line  142)
* NNTPProtocolError:                     nntplib --- NNTP protocol client.
                                                             (line  147)
* NNTPReplyError:                        nntplib --- NNTP protocol client.
                                                             (line  132)
* NNTPTemporaryError:                    nntplib --- NNTP protocol client.
                                                             (line  137)
* nntp_implementation (nntplib.NNTP 的屬性): Attributes.     (line   14)
* NNTP_SSL (nntplib 中的類別):           nntplib --- NNTP protocol client.
                                                             (line   92)
* nntp_version (nntplib.NNTP 的屬性):    Attributes.         (line    6)
* nocbreak() (於 curses 模組中):         Functions<3>.       (line  332)
* NoDataAllowedErr:                      Exceptions<14>.     (line   83)
* node() (於 platform 模組中):           Cross Platform.     (line   42)
* nodelay() (curses.window 的方法):      Window Objects.     (line  408)
* nodeName (xml.dom.Node 的屬性):        Node Objects.       (line   79)
* NodeTransformer (ast 中的類別):        ast Helpers.        (line  154)
* nodeType (xml.dom.Node 的屬性):        Node Objects.       (line    8)
* nodeValue (xml.dom.Node 的屬性):       Node Objects.       (line   88)
* NodeVisitor (ast 中的類別):            ast Helpers.        (line  119)
* noecho() (於 curses 模組中):           Functions<3>.       (line  337)
* NOEXPR (於 locale 模組中):             locale --- Internationalization services.
                                                             (line  251)
* NoModificationAllowedErr:              Exceptions<14>.     (line   88)
* nonblock() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line   72)
* NonCallableMagicMock (unittest.mock 中的類別): Magic Mock. (line   21)
* NonCallableMock (unittest.mock 中的類別): The Mock Class.  (line  558)
* None (Built-in object):                Truth Value Testing.
                                                             (line   15)
* None (內建變數):                       內建常數.           (line   18)
* nonl() (於 curses 模組中):             Functions<3>.       (line  341)
* nonzero (2to3 fixer):                  Fixers.             (line  211)
* noop() (imaplib.IMAP4 的方法):         IMAP4 Objects.      (line  166)
* noop() (poplib.POP3 的方法):           POP3 Objects.       (line   78)
* NoOptionError:                         Exceptions<4>.      (line   32)
* NOP (opcode):                          Python Bytecode Instructions.
                                                             (line   55)
* noqiflush() (於 curses 模組中):        Functions<3>.       (line  351)
* noraw() (於 curses 模組中):            Functions<3>.       (line  359)
* NoReturn (於 typing 模組中):           Classes functions and decorators.
                                                             (line  779)
* NormalDist (statistics 中的類別):      NormalDist objects. (line   13)
* normalize() (decimal.Context 的方法):  Context objects.    (line  404)
* normalize() (decimal.Decimal 的方法):  Decimal objects.    (line  418)
* normalize() (xml.dom.Node 的方法):     Node Objects.       (line  141)
* normalize() (於 locale 模組中):        locale --- Internationalization services.
                                                             (line  356)
* normalize() (於 unicodedata 模組中):   unicodedata --- Unicode Database.
                                                             (line   81)
* NORMALIZE_WHITESPACE (於 doctest 模組中): Option Flags.    (line   39)
* normalvariate() (於 random 模組中):    Real-valued distributions.
                                                             (line   70)
* NORMAL_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   80)
* normcase() (於 os.path 模組中):        os path --- Common pathname manipulations.
                                                             (line  274)
* normpath() (於 os.path 模組中):        os path --- Common pathname manipulations.
                                                             (line  283)
* NoSectionError:                        Exceptions<4>.      (line   10)
* NoSuchMailboxError:                    Exceptions<12>.     (line   13)
* NotADirectoryError:                    OS exceptions.      (line   86)
* notation:                              Notation.           (line    6)
* notationDecl() (xml.sax.handler.DTDHandler 的方法): DTDHandler Objects.
                                                             (line    8)
* NotationDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  272)
* notations (xml.dom.DocumentType 的屬性): DocumentType Objects.
                                                             (line   46)
* NotConnected:                          http client --- HTTP protocol client.
                                                             (line  132)
* NoteBook (tkinter.tix 中的類別):       Manager Widgets.    (line   22)
* Notebook (tkinter.ttk 中的類別):       ttk Notebook.       (line    6)
* NotEmptyError:                         Exceptions<12>.     (line   20)
* NOTEQUAL (於 token 模組中):            token --- Constants used with Python parse trees.
                                                             (line  138)
* NotFoundErr:                           Exceptions<14>.     (line   72)
* notify() (asyncio.Condition 的方法):   Condition.          (line   55)
* notify() (threading.Condition 的方法): Condition Objects.  (line  151)
* notify_all() (asyncio.Condition 的方法): Condition.        (line   68)
* notify_all() (threading.Condition 的方法): Condition Objects.
                                                             (line  171)
* notimeout() (curses.window 的方法):    Window Objects.     (line  412)
* NotImplemented (內建變數):             內建常數.           (line   25)
* NotImplementedError:                   Concrete exceptions.
                                                             (line   95)
* NotStandaloneHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  323)
* NotSupportedErr:                       Exceptions<14>.     (line   78)
* NotSupportedError:                     Exceptions<3>.      (line   40)
* not_() (於 operator 模組中):           operator --- Standard operators as functions.
                                                             (line   49)
* noutrefresh() (curses.window 的方法):  Window Objects.     (line  420)
* now() (datetime.datetime 的類別成員):  datetime Objects.   (line   60)
* no_proxy:                              urllib request --- Extensible library for opening URLs.
                                                             (line  302)
* no_tracing() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  642)
* no_type_check() (於 typing 模組中):    Classes functions and decorators.
                                                             (line  714)
* no_type_check_decorator() (於 typing 模組中): Classes functions and decorators.
                                                             (line  724)
* npgettext() (gettext.GNUTranslations 的方法): The GNUTranslations class.
                                                             (line   79)
* npgettext() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   55)
* npgettext() (於 gettext 模組中):       GNU gettext API.    (line   77)
* NSIG (於 signal 模組中):               Module contents<2>. (line  164)
* nsmallest() (於 heapq 模組中):         heapq --- 堆積佇列 heap queue 演算法.
                                                             (line   98)
* NTEventLogHandler (logging.handlers 中的類別): NTEventLogHandler.
                                                             (line   11)
* ntohl() (於 socket 模組中):            Other functions<2>. (line  178)
* ntohs() (於 socket 模組中):            Other functions<2>. (line  185)
* ntransfercmd() (ftplib.FTP 的方法):    FTP Objects.        (line  157)
* NT_OFFSET (於 token 模組中):           token --- Constants used with Python parse trees.
                                                             (line  256)
* null; operation:                       The pass statement. (line    6)
* null; operation <1>:                   The pass statement. (line    6)
* nullcontext() (於 contextlib 模組中):  Utilities.          (line  147)
* NullFormatter (formatter 中的類別):    Formatter Implementations.
                                                             (line   10)
* NullHandler (logging 中的類別):        NullHandler.        (line   12)
* NullImporter (imp 中的類別):           imp --- Access the import internals.
                                                             (line  343)
* NullTranslations (gettext 中的類別):   The NullTranslations class.
                                                             (line   13)
* NullWriter (formatter 中的類別):       Writer Implementations.
                                                             (line   10)
* number:                                Numeric literals.   (line    6)
* Number (numbers 中的類別):             numbers --- Numeric abstract base classes.
                                                             (line   15)
* NUMBER (於 token 模組中):              token --- Constants used with Python parse trees.
                                                             (line   44)
* numbers (模組):                        numbers --- Numeric abstract base classes.
                                                             (line    6)
* number_class() (decimal.Context 的方法): Context objects.  (line  408)
* number_class() (decimal.Decimal 的方法): Decimal objects.  (line  427)
* numerator (fractions.Fraction 的屬性): fractions --- Rational numbers.
                                                             (line   89)
* numerator (numbers.Rational 的屬性):   The numeric tower.  (line   47)
* numeric literal:                       Numeric literals.   (line    6)
* numeric() (於 unicodedata 模組中):     unicodedata --- Unicode Database.
                                                             (line   43)
* numeric; conversions:                  Numeric Types --- int float complex.
                                                             (line  104)
* numeric; literals:                     Numeric Types --- int float complex.
                                                             (line   19)
* Numerical Python:                      內建函式.           (line 1483)
* numinput() (於 turtle 模組中):         Input methods.      (line   22)
* numliterals (2to3 fixer):              Fixers.             (line  215)
* num_addresses (ipaddress.IPv4Network 的屬性): Network objects.
                                                             (line  128)
* num_addresses (ipaddress.IPv6Network 的屬性): Network objects.
                                                             (line  327)
* num_tickets (ssl.SSLContext 的屬性):   SSL Contexts.       (line  573)
* N_TOKENS (於 token 模組中):            token --- Constants used with Python parse trees.
                                                             (line  254)
* n_waiting (threading.Barrier 的屬性):  Barrier Objects.    (line   97)
* obj (memoryview 的屬性):               Memory Views.       (line  362)
* object:                                Objects values and types.
                                                             (line    6)
* object <1>:                            Glossary.           (line  921)
* object (UnicodeError 的屬性):          Concrete exceptions.
                                                             (line  367)
* object (內建類別):                     內建函式.           (line  987)
* object.__slots__ (內建變數):           __slots__.          (line   13)
* object; code:                          The standard type hierarchy.
                                                             (line  648)
* object; code <1>:                      Methods.            (line   43)
* object; code <2>:                      marshal --- Internal Python object serialization.
                                                             (line   30)
* object; code <3>:                      Cell 物件.          (line   52)
* object; deallocation:                  Finalization and De-allocation.
                                                             (line    6)
* object; finalization:                  Finalization and De-allocation.
                                                             (line    6)
* object; numeric:                       Comparisons<2>.     (line   43)
* objects; comparing:                    Comparisons<2>.     (line   43)
* object_filenames() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  466)
* objobjargproc (C 型態):                Slot Type typedefs. (line  122)
* objobjproc (C 型態):                   Slot Type typedefs. (line  120)
* obufcount() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line  215)
* obuffree() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line  220)
* oct() (內建函式):                      內建函式.           (line  997)
* octal literal:                         Numeric literals.   (line    6)
* octal; literals:                       Numeric Types --- int float complex.
                                                             (line   19)
* octdigits (於 string 模組中):          String constants.   (line   32)
* offset (SyntaxError 的屬性):           Concrete exceptions.
                                                             (line  265)
* offset (traceback.TracebackException 的屬性): TracebackException Objects.
                                                             (line   54)
* offset (xml.parsers.expat.ExpatError 的屬性): ExpatError Exceptions.
                                                             (line   32)
* OK (於 curses 模組中):                 Constants<6>.       (line   13)
* old_value (contextvars.contextvars.Token.Token 的屬性): Context Variables.
                                                             (line   87)
* OleDLL (ctypes 中的類別):              Loading shared libraries.
                                                             (line   32)
* onclick() (於 turtle 模組中):          Using screen events.
                                                             (line   56)
* ondrag() (於 turtle 模組中):           Using events.       (line   57)
* onecmd() (cmd.Cmd 的方法):             Cmd Objects.        (line   57)
* 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 --- Constants used with Python parse trees.
                                                             (line  242)
* open() (distutils.text_file.TextFile 的方法): distutils text_file --- The TextFile class.
                                                             (line   91)
* open() (imaplib.IMAP4 的方法):         IMAP4 Objects.      (line  170)
* open() (pathlib.Path 的方法):          Methods<2>.         (line  245)
* open() (pipes.Template 的方法):        Template Objects.   (line   42)
* open() (tarfile.TarFile 的類別成員):   TarFile Objects.    (line   95)
* open() (telnetlib.Telnet 的方法):      Telnet Objects.     (line   65)
* open() (urllib.request.OpenerDirector 的方法): OpenerDirector Objects.
                                                             (line   46)
* open() (urllib.request.URLopener 的方法): Legacy interface.
                                                             (line   98)
* open() (webbrowser.controller 的方法): Browser Controller Objects.
                                                             (line    9)
* open() (zipfile.Path 的方法):          Path Objects.       (line   26)
* open() (zipfile.ZipFile 的方法):       ZipFile Objects.    (line  109)
* open() (內建函式):                     內建函式.           (line 1021)
* open() (於 aifc 模組中):               aifc --- Read and write AIFF and AIFC files.
                                                             (line   30)
* open() (於 bz2 模組中):                De compression of files.
                                                             (line    6)
* open() (於 codecs 模組中):             codecs --- Codec registry and base classes.
                                                             (line  167)
* open() (於 dbm 模組中):                dbm --- Interfaces to Unix "databases".
                                                             (line   35)
* open() (於 dbm.dumb 模組中):           dbm dumb --- Portable DBM implementation.
                                                             (line   30)
* open() (於 dbm.gnu 模組中):            dbm gnu --- GNU's reinterpretation of dbm.
                                                             (line   27)
* open() (於 dbm.ndbm 模組中):           dbm ndbm --- Interface based on ndbm.
                                                             (line   31)
* open() (於 gzip 模組中):               gzip --- Support for gzip files.
                                                             (line   28)
* open() (於 io 模組中):                 High-level Module Interface.
                                                             (line   12)
* open() (於 lzma 模組中):               Reading and writing compressed files.
                                                             (line    6)
* open() (於 os 模組中):                 File Descriptor Operations.
                                                             (line  258)
* open() (於 ossaudiodev 模組中):        ossaudiodev --- Access to OSS-compatible audio devices.
                                                             (line   42)
* open() (於 shelve 模組中):             shelve --- Python object persistence.
                                                             (line   17)
* open() (於 sunau 模組中):              sunau --- Read and write Sun AU files.
                                                             (line   48)
* open() (於 tarfile 模組中):            tarfile --- Read and write tar archive files.
                                                             (line   35)
* open() (於 tokenize 模組中):           Tokenizing Input.   (line  100)
* open() (於 wave 模組中):               wave --- Read and write WAV files.
                                                             (line   17)
* open() (於 webbrowser 模組中):         webbrowser --- Convenient Web-browser controller.
                                                             (line   50)
* OpenDatabase() (於 msilib 模組中):     msilib --- Read and write Microsoft Installer files.
                                                             (line   45)
* OpenerDirector (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  265)
* openfp() (於 sunau 模組中):            sunau --- Read and write Sun AU files.
                                                             (line   66)
* openfp() (於 wave 模組中):             wave --- Read and write WAV files.
                                                             (line   48)
* OpenKey() (於 winreg 模組中):          Functions<11>.      (line  291)
* OpenKeyEx() (於 winreg 模組中):        Functions<11>.      (line  291)
* openlog() (於 syslog 模組中):          syslog --- Unix syslog library routines.
                                                             (line   36)
* openmixer() (於 ossaudiodev 模組中):   ossaudiodev --- Access to OSS-compatible audio devices.
                                                             (line   70)
* openpty() (於 os 模組中):              File Descriptor Operations.
                                                             (line  349)
* openpty() (於 pty 模組中):             pty --- Pseudo-terminal utilities.
                                                             (line   29)
* OpenSSL; (use in module hashlib):      Hash algorithms.    (line   21)
* OpenSSL; (use in module ssl):          ssl --- TLS/SSL wrapper for socket objects.
                                                             (line    8)
* OPENSSL_VERSION (於 ssl 模組中):       Constants<9>.       (line  445)
* OPENSSL_VERSION_INFO (於 ssl 模組中):  Constants<9>.       (line  455)
* OPENSSL_VERSION_NUMBER (於 ssl 模組中): Constants<9>.      (line  465)
* OpenView() (msilib.Database 的方法):   Database Objects.   (line    6)
* open_binary() (於 importlib.resources 模組中): importlib resources -- Resources.
                                                             (line   53)
* open_code() (於 io 模組中):            High-level Module Interface.
                                                             (line   22)
* open_connection() (於 asyncio 模組中): Streams.            (line   42)
* open_new() (webbrowser.controller 的方法): Browser Controller Objects.
                                                             (line   15)
* open_new() (於 webbrowser 模組中):     webbrowser --- Convenient Web-browser controller.
                                                             (line   67)
* open_new_tab() (webbrowser.controller 的方法): Browser Controller Objects.
                                                             (line   21)
* open_new_tab() (於 webbrowser 模組中): webbrowser --- Convenient Web-browser controller.
                                                             (line   72)
* open_osfhandle() (於 msvcrt 模組中):   File Operations.    (line   44)
* open_resource() (importlib.abc.ResourceReader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  309)
* open_text() (於 importlib.resources 模組中): importlib resources -- Resources.
                                                             (line   64)
* open_unix_connection() (於 asyncio 模組中): Streams.       (line   98)
* open_unknown() (urllib.request.URLopener 的方法): Legacy interface.
                                                             (line  109)
* open_urlresource() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  713)
* OperationalError:                      Exceptions<3>.      (line   32)
* operations on; dictionary; type:       Mapping Types --- dict.
                                                             (line    6)
* operations on; integer; types:         Bitwise Operations on Integer Types.
                                                             (line    6)
* operations on; list; type:             Mutable Sequence Types.
                                                             (line   16)
* operations on; mapping; types:         Mapping Types --- dict.
                                                             (line    6)
* operations on; numeric; types:         Numeric Types --- int float complex.
                                                             (line   94)
* operations on; sequence; types:        Common Sequence Operations.
                                                             (line   21)
* operations on; sequence; types <1>:    Mutable Sequence Types.
                                                             (line   16)
* operator (2to3 fixer):                 Fixers.             (line  219)
* operator (模組):                       operator --- Standard operators as functions.
                                                             (line    6)
* operator; + (plus):                    Unary arithmetic and bitwise operations.
                                                             (line   13)
* operator; + (plus) <1>:                Binary arithmetic operations.
                                                             (line   60)
* operator; + (plus) <2>:                Numeric Types --- int float complex.
                                                             (line   27)
* operator; - (minus):                   Unary arithmetic and bitwise operations.
                                                             (line   10)
* operator; - (minus) <1>:               Binary arithmetic operations.
                                                             (line   66)
* operator; - (minus) <2>:               Numeric Types --- int float complex.
                                                             (line   27)
* operator; comparison:                  Comparisons<2>.     (line    6)
* operator; overloading:                 Special method names.
                                                             (line    6)
* operator; precedence:                  Operator precedence.
                                                             (line    6)
* operators:                             Operators.          (line    6)
* opmap (於 dis 模組中):                 Opcode collections. (line   13)
* opname (於 dis 模組中):                Opcode collections. (line    9)
* optimize() (於 pickletools 模組中):    Programmatic Interface<2>.
                                                             (line   31)
* OPTIMIZED_BYTECODE_SUFFIXES (於 importlib.machinery 模組中): importlib machinery -- Importers and path hooks.
                                                             (line   29)
* optim_args_from_interpreter_flags() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  396)
* Optional (於 typing 模組中):           Classes functions and decorators.
                                                             (line  826)
* OptionGroup (optparse 中的類別):       Grouping Options.   (line   12)
* OptionMenu (tkinter.tix 中的類別):     Basic Widgets.      (line   49)
* OptionParser (optparse 中的類別):      Creating the parser.
                                                             (line    9)
* options (doctest.Example 的屬性):      Example Objects.    (line   53)
* Options (ssl 中的類別):                Constants<9>.       (line  336)
* options (ssl.SSLContext 的屬性):       SSL Contexts.       (line  584)
* options() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  102)
* optionxform() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  278)
* optparse (模組):                       optparse --- Parser for command line options.
                                                             (line    6)
* OP_ALL (於 ssl 模組中):                Constants<9>.       (line  207)
* OP_CIPHER_SERVER_PREFERENCE (於 ssl 模組中): Constants<9>. (line  294)
* OP_ENABLE_MIDDLEBOX_COMPAT (於 ssl 模組中): Constants<9>.  (line  318)
* OP_IGNORE_UNEXPECTED_EOF (於 ssl 模組中): Constants<9>.    (line  346)
* OP_NO_COMPRESSION (於 ssl 模組中):     Constants<9>.       (line  327)
* OP_NO_RENEGOTIATION (於 ssl 模組中):   Constants<9>.       (line  284)
* OP_NO_SSLv2 (於 ssl 模組中):           Constants<9>.       (line  215)
* OP_NO_SSLv3 (於 ssl 模組中):           Constants<9>.       (line  225)
* OP_NO_TICKET (於 ssl 模組中):          Constants<9>.       (line  340)
* OP_NO_TLSv1 (於 ssl 模組中):           Constants<9>.       (line  235)
* OP_NO_TLSv1_1 (於 ssl 模組中):         Constants<9>.       (line  247)
* OP_NO_TLSv1_2 (於 ssl 模組中):         Constants<9>.       (line  258)
* OP_NO_TLSv1_3 (於 ssl 模組中):         Constants<9>.       (line  269)
* OP_SINGLE_DH_USE (於 ssl 模組中):      Constants<9>.       (line  302)
* OP_SINGLE_ECDH_USE (於 ssl 模組中):    Constants<9>.       (line  310)
* ord() (內建函式):                      內建函式.           (line 1262)
* OrderedDict (collections 中的類別):    OrderedDict objects.
                                                             (line   39)
* OrderedDict (typing 中的類別):         Classes functions and decorators.
                                                             (line  367)
* ordered_attributes (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line  107)
* origin (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  373)
* origin_req_host (urllib.request.Request 的屬性): Request Objects.
                                                             (line   30)
* origin_server (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  287)
* or_() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line  133)
* os (模組):                             os --- Miscellaneous operating system interfaces.
                                                             (line    6)
* os.path (模組):                        os path --- Common pathname manipulations.
                                                             (line    6)
* OSError:                               Concrete exceptions.
                                                             (line  113)
* ossaudiodev (模組):                    ossaudiodev --- Access to OSS-compatible audio devices.
                                                             (line    6)
* OSSAudioError:                         ossaudiodev --- Access to OSS-compatible audio devices.
                                                             (line   29)
* os_environ (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  165)
* output:                                Expression statements.
                                                             (line   17)
* output (subprocess.CalledProcessError 的屬性): Using the subprocess Module.
                                                             (line  205)
* output (subprocess.TimeoutExpired 的屬性): Using the subprocess Module.
                                                             (line  172)
* output (unittest.TestCase 的屬性):     Test cases.         (line  431)
* output() (http.cookies.BaseCookie 的方法): Cookie Objects. (line   24)
* output() (http.cookies.Morsel 的方法): Morsel Objects.     (line   72)
* OutputChecker (doctest 中的類別):      OutputChecker objects.
                                                             (line    6)
* OutputString() (http.cookies.Morsel 的方法): Morsel Objects.
                                                             (line   87)
* output_charset (email.charset.Charset 的屬性): email charset Representing character sets.
                                                             (line   74)
* output_charset() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   87)
* output_codec (email.charset.Charset 的屬性): email charset Representing character sets.
                                                             (line   88)
* output_difference() (doctest.OutputChecker 的方法): OutputChecker objects.
                                                             (line   27)
* over() (nntplib.NNTP 的方法):          Methods<3>.         (line  167)
* Overflow (decimal 中的類別):           Signals.            (line   67)
* OverflowError:                         Concrete exceptions.
                                                             (line  176)
* OverflowError (built-in exception):    整數物件.           (line  105)
* OverflowError (built-in exception) <1>: 整數物件.          (line  141)
* OverflowError (built-in exception) <2>: 整數物件.          (line  180)
* OverflowError (built-in exception) <3>: 整數物件.          (line  191)
* OverflowError (built-in exception) <4>: 整數物件.          (line  202)
* OverflowError (built-in exception) <5>: 整數物件.          (line  214)
* overlap() (statistics.NormalDist 的方法): NormalDist objects.
                                                             (line   96)
* overlaps() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  155)
* overlaps() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  340)
* overlay() (curses.window 的方法):      Window Objects.     (line  427)
* overload() (於 typing 模組中):         Classes functions and decorators.
                                                             (line  659)
* overwrite() (curses.window 的方法):    Window Objects.     (line  440)
* owner() (pathlib.Path 的方法):         Methods<2>.         (line  257)
* O_APPEND (於 os 模組中):               File Descriptor Operations.
                                                             (line  301)
* O_ASYNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  333)
* O_BINARY (於 os 模組中):               File Descriptor Operations.
                                                             (line  323)
* O_CLOEXEC (於 os 模組中):              File Descriptor Operations.
                                                             (line  311)
* O_CREAT (於 os 模組中):                File Descriptor Operations.
                                                             (line  301)
* O_DIRECT (於 os 模組中):               File Descriptor Operations.
                                                             (line  333)
* O_DIRECTORY (於 os 模組中):            File Descriptor Operations.
                                                             (line  333)
* O_DSYNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  311)
* O_EXCL (於 os 模組中):                 File Descriptor Operations.
                                                             (line  301)
* O_EXLOCK (於 os 模組中):               File Descriptor Operations.
                                                             (line  333)
* O_NDELAY (於 os 模組中):               File Descriptor Operations.
                                                             (line  311)
* O_NOATIME (於 os 模組中):              File Descriptor Operations.
                                                             (line  333)
* O_NOCTTY (於 os 模組中):               File Descriptor Operations.
                                                             (line  311)
* O_NOFOLLOW (於 os 模組中):             File Descriptor Operations.
                                                             (line  333)
* O_NOINHERIT (於 os 模組中):            File Descriptor Operations.
                                                             (line  323)
* O_NONBLOCK (於 os 模組中):             File Descriptor Operations.
                                                             (line  311)
* O_PATH (於 os 模組中):                 File Descriptor Operations.
                                                             (line  333)
* O_RANDOM (於 os 模組中):               File Descriptor Operations.
                                                             (line  323)
* O_RDONLY (於 os 模組中):               File Descriptor Operations.
                                                             (line  301)
* O_RDWR (於 os 模組中):                 File Descriptor Operations.
                                                             (line  301)
* O_RSYNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  311)
* O_SEQUENTIAL (於 os 模組中):           File Descriptor Operations.
                                                             (line  323)
* O_SHLOCK (於 os 模組中):               File Descriptor Operations.
                                                             (line  333)
* O_SHORT_LIVED (於 os 模組中):          File Descriptor Operations.
                                                             (line  323)
* O_SYNC (於 os 模組中):                 File Descriptor Operations.
                                                             (line  311)
* O_TEMPORARY (於 os 模組中):            File Descriptor Operations.
                                                             (line  323)
* O_TEXT (於 os 模組中):                 File Descriptor Operations.
                                                             (line  323)
* O_TMPFILE (於 os 模組中):              File Descriptor Operations.
                                                             (line  333)
* O_TRUNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  301)
* O_WRONLY (於 os 模組中):               File Descriptor Operations.
                                                             (line  301)
* p (pdb command):                       Debugger Commands.  (line  233)
* pack() (mailbox.MH 的方法):            MH.                 (line   64)
* pack() (struct.Struct 的方法):         Classes<2>.         (line   25)
* pack() (於 struct 模組中):             Functions and Exceptions.
                                                             (line   13)
* package:                               Packages<2>.        (line    6)
* package <1>:                           site --- Site-specific configuration hook.
                                                             (line   63)
* package <2>:                           Glossary.           (line  927)
* Package (於 importlib.resources 模組中): importlib resources -- Resources.
                                                             (line   37)
* package variable; __all__:             匯入模組<2>.        (line    7)
* package; namespace:                    Namespace packages. (line    6)
* package; portion:                      Namespace packages. (line    6)
* package; regular:                      Regular packages.   (line    6)
* packed (ipaddress.IPv4Address 的屬性): Address objects.    (line   65)
* packed (ipaddress.IPv6Address 的屬性): Address objects.    (line  163)
* Packer (xdrlib 中的類別):              xdrlib --- Encode and decode XDR data.
                                                             (line   18)
* packing (widgets):                     The Packer.         (line    6)
* packing; binary; data:                 struct --- Interpret bytes as packed binary data.
                                                             (line    8)
* pack_array() (xdrlib.Packer 的方法):   Packer Objects.     (line   86)
* pack_bytes() (xdrlib.Packer 的方法):   Packer Objects.     (line   54)
* pack_double() (xdrlib.Packer 的方法):  Packer Objects.     (line   26)
* pack_farray() (xdrlib.Packer 的方法):  Packer Objects.     (line   78)
* pack_float() (xdrlib.Packer 的方法):   Packer Objects.     (line   22)
* pack_fopaque() (xdrlib.Packer 的方法): Packer Objects.     (line   38)
* pack_fstring() (xdrlib.Packer 的方法): Packer Objects.     (line   32)
* pack_into() (struct.Struct 的方法):    Classes<2>.         (line   30)
* pack_into() (於 struct 模組中):        Functions and Exceptions.
                                                             (line   19)
* pack_list() (xdrlib.Packer 的方法):    Packer Objects.     (line   61)
* pack_opaque() (xdrlib.Packer 的方法):  Packer Objects.     (line   49)
* pack_string() (xdrlib.Packer 的方法):  Packer Objects.     (line   43)
* PAGER:                                 pydoc --- Documentation generator and online help system.
                                                             (line   47)
* pair_content() (於 curses 模組中):     Functions<3>.       (line  364)
* pair_number() (於 curses 模組中):      Functions<3>.       (line  370)
* PanedWindow (tkinter.tix 中的類別):    Manager Widgets.    (line    6)
* parameter:                             Glossary.           (line  936)
* Parameter (inspect 中的類別):          Introspecting callables with the Signature object.
                                                             (line  142)
* parameter; call semantics:             Calls.              (line   25)
* parameter; difference from argument:   How can I pass optional or keyword parameters from one function to another?.
                                                             (line   16)
* parameter; function definition:        The with statement. (line  103)
* ParameterizedMIMEHeader (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  255)
* parameters (inspect.Signature 的屬性): Introspecting callables with the Signature object.
                                                             (line   78)
* params (email.headerregistry.ParameterizedMIMEHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  263)
* pardir (於 os 模組中):                 Miscellaneous System Information.
                                                             (line   87)
* paren (2to3 fixer):                    Fixers.             (line  251)
* parent (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  401)
* parent (pyclbr.Class 的屬性):          Class Objects<2>.   (line   25)
* parent (pyclbr.Function 的屬性):       函式物件.           (line   25)
* parent (urllib.request.BaseHandler 的屬性): BaseHandler Objects.
                                                             (line   25)
* parent() (tkinter.ttk.Treeview 的方法): ttk Treeview.      (line  237)
* parenthesized form:                    Parenthesized forms.
                                                             (line    6)
* parentNode (xml.dom.Node 的屬性):      Node Objects.       (line   17)
* parents (collections.ChainMap 的屬性): ChainMap objects.   (line   59)
* parent_process() (於 multiprocessing 模組中): Miscellaneous<3>.
                                                             (line   35)
* paretovariate() (於 random 模組中):    Real-valued distributions.
                                                             (line   83)
* parse() (doctest.DocTestParser 的方法): DocTestParser objects.
                                                             (line   29)
* parse() (email.parser.BytesParser 的方法): Parser API.     (line   33)
* parse() (email.parser.Parser 的方法):  Parser API.         (line   84)
* parse() (string.Formatter 的方法):     Custom String Formatting.
                                                             (line   40)
* parse() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- Parser for robots txt.
                                                             (line   29)
* parse() (xml.etree.ElementTree.ElementTree 的方法): ElementTree Objects.
                                                             (line   59)
* Parse() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line    8)
* parse() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line    8)
* parse() (於 ast 模組中):               ast Helpers.        (line    9)
* parse() (於 cgi 模組中):               Functions<8>.       (line    9)
* parse() (於 xml.dom.minidom 模組中):   xml dom minidom --- Minimal DOM implementation.
                                                             (line   36)
* parse() (於 xml.dom.pulldom 模組中):   xml dom pulldom --- Support for building partial DOM trees.
                                                             (line   85)
* parse() (於 xml.etree.ElementTree 模組中): Functions<6>.   (line  159)
* parse() (於 xml.sax 模組中):           xml sax --- Support for SAX2 parsers.
                                                             (line   39)
* parseaddr() (於 email.utils 模組中):   email utils Miscellaneous utilities.
                                                             (line   59)
* parsebytes() (email.parser.BytesParser 的方法): Parser API.
                                                             (line   53)
* parsedate() (於 email.utils 模組中):   email utils Miscellaneous utilities.
                                                             (line   96)
* parsedate_to_datetime() (於 email.utils 模組中): email utils Miscellaneous utilities.
                                                             (line  119)
* parsedate_tz() (於 email.utils 模組中): email utils Miscellaneous utilities.
                                                             (line  108)
* ParseError (xml.etree.ElementTree 中的類別): Exceptions<13>.
                                                             (line    6)
* ParseFile() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line   16)
* ParseFlags() (於 imaplib 模組中):      imaplib --- IMAP4 protocol client.
                                                             (line  116)
* parser:                                Lexical analysis.   (line    6)
* Parser (email.parser 中的類別):        Parser API.         (line   74)
* parser (模組):                         parser --- Access Python parse trees.
                                                             (line    6)
* ParserCreate() (於 xml.parsers.expat 模組中): xml parsers expat --- Fast XML parsing using Expat.
                                                             (line   46)
* ParserError:                           Exceptions and Error Handling.
                                                             (line   11)
* ParseResult (urllib.parse 中的類別):   Structured Parse Results.
                                                             (line   48)
* ParseResultBytes (urllib.parse 中的類別): Structured Parse Results.
                                                             (line   73)
* parsestr() (email.parser.Parser 的方法): Parser API.       (line   94)
* parseString() (於 xml.dom.minidom 模組中): xml dom minidom --- Minimal DOM implementation.
                                                             (line   49)
* parseString() (於 xml.dom.pulldom 模組中): xml dom pulldom --- Support for building partial DOM trees.
                                                             (line   98)
* parseString() (於 xml.sax 模組中):     xml sax --- Support for SAX2 parsers.
                                                             (line   50)
* parse_and_bind() (於 readline 模組中): Init file.          (line    8)
* parse_args() (argparse.ArgumentParser 的方法): The parse_args method.
                                                             (line    6)
* PARSE_COLNAMES (於 sqlite3 模組中):    Module functions and constants.
                                                             (line   38)
* parse_config_h() (於 sysconfig 模組中): Other functions<3>.
                                                             (line   57)
* PARSE_DECLTYPES (於 sqlite3 模組中):   Module functions and constants.
                                                             (line   25)
* parse_header() (於 cgi 模組中):        Functions<8>.       (line   40)
* parse_headers() (於 http.client 模組中): http client --- HTTP protocol client.
                                                             (line  107)
* 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_multipart() (於 cgi 模組中):     Functions<8>.       (line   19)
* parse_qs() (於 urllib.parse 模組中):   URL Parsing.        (line  139)
* parse_qsl() (於 urllib.parse 模組中):  URL Parsing.        (line  185)
* parsing; Python source code:           parser --- Access Python parse trees.
                                                             (line    6)
* ParsingError:                          Exceptions<4>.      (line   65)
* partial (asyncio.IncompleteReadError 的屬性): Exceptions<8>.
                                                             (line   54)
* partial() (imaplib.IMAP4 的方法):      IMAP4 Objects.      (line  182)
* partial() (於 functools 模組中):       functools --- Higher-order functions and operations on callable objects.
                                                             (line  214)
* partialmethod (functools 中的類別):    functools --- Higher-order functions and operations on callable objects.
                                                             (line  245)
* parties (threading.Barrier 的屬性):    Barrier Objects.    (line   93)
* partition() (bytearray 的方法):        Bytes and Bytearray Operations.
                                                             (line  132)
* partition() (bytes 的方法):            Bytes and Bytearray Operations.
                                                             (line  132)
* partition() (str 的方法):              String Methods<2>.  (line  330)
* pass_() (poplib.POP3 的方法):          POP3 Objects.       (line   36)
* Paste:                                 Help menu Shell and Editor.
                                                             (line   30)
* patch() (於 test.support 模組中):      test support --- Utilities for the Python test suite.
                                                             (line  942)
* patch() (於 unittest.mock 模組中):     patch.              (line   10)
* 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 methods start and stop.
                                                             (line   70)
* PATH:                                  Changes in the Python API.
                                                             (line  143)
* 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>:                              Security<18>.       (line   16)
* PATH <5>:                              Security<18>.       (line   20)
* PATH <6>:                              The Module Search Path.
                                                             (line   16)
* PATH <7>:                              Executable Python Scripts.
                                                             (line   11)
* PATH <8>:                              Environment variables.
                                                             (line   27)
* PATH <9>:                              Miscellaneous.      (line   16)
* PATH <10>:                             Installation steps. (line   31)
* PATH <11>:                             Installation steps. (line   54)
* PATH <12>:                             安裝排除使用者介面. (line   56)
* PATH <13>:                             Excursus Setting environment variables.
                                                             (line   23)
* PATH <14>:                             Excursus Setting environment variables.
                                                             (line   35)
* PATH <15>:                             Finding the Python executable.
                                                             (line   14)
* PATH <16>:                             Finding the Python executable.
                                                             (line   21)
* PATH <17>:                             Finding the Python executable.
                                                             (line   22)
* PATH <18>:                             Python Launcher for Windows.
                                                             (line   13)
* PATH <19>:                             From the command-line.
                                                             (line    9)
* PATH <20>:                             From the command-line.
                                                             (line   38)
* PATH <21>:                             Shebang Lines.      (line   48)
* PATH <22>:                             Shebang Lines.      (line   50)
* PATH <23>:                             Process Management. (line   45)
* PATH <24>:                             Process Management. (line   86)
* PATH <25>:                             Process Management. (line   89)
* PATH <26>:                             Process Management. (line   92)
* PATH <27>:                             Process Management. (line  453)
* PATH <28>:                             Process Management. (line  539)
* PATH <29>:                             Process Management. (line  543)
* PATH <30>:                             Process Management. (line  545)
* PATH <31>:                             Miscellaneous System Information.
                                                             (line  118)
* PATH <32>:                             webbrowser --- Convenient Web-browser controller.
                                                             (line  213)
* PATH <33>:                             Installing your CGI script on a Unix system.
                                                             (line   29)
* PATH <34>:                             Common problems and solutions.
                                                             (line   23)
* PATH <35>:                             site --- Site-specific configuration hook.
                                                             (line   58)
* PATH <36>:                             嵌入式Python.       (line   31)
* PATH <37>:                             嵌入式Python.       (line   37)
* PATH <38>:                             我如何使Python script 執行在Unix ?.
                                                             (line   23)
* PATH <39>:                             我如何使Python script 執行在Unix ?.
                                                             (line   27)
* path (http.cookiejar.Cookie 的屬性):   Cookie Objects<2>.  (line   41)
* path (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line   92)
* path (importlib.abc.FileLoader 的屬性): importlib abc -- Abstract base classes related to import.
                                                             (line  476)
* path (importlib.machinery.ExtensionFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  307)
* path (importlib.machinery.FileFinder 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  178)
* path (importlib.machinery.SourceFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  220)
* path (importlib.machinery.SourcelessFileLoader 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  264)
* path (in module sys):                  嵌入式Python.       (line   12)
* path (in module sys) <1>:              Initializing and finalizing the interpreter.
                                                             (line    8)
* path (in module sys) <2>:              Process-wide parameters.
                                                             (line  120)
* path (in module sys) <3>:              Process-wide parameters.
                                                             (line  133)
* path (os.DirEntry 的屬性):             Files and Directories.
                                                             (line  850)
* Path (pathlib 中的類別):               Concrete paths.     (line   11)
* Path (zipfile 中的類別):               Path Objects.       (line    6)
* path (於 sys 模組中):                  sys --- System-specific parameters and functions.
                                                             (line 1060)
* path based finder:                     The Path Based Finder.
                                                             (line    6)
* path based finder <1>:                 Glossary.           (line 1008)
* Path browser:                          File menu Shell and Editor.
                                                             (line   22)
* path entry:                            Glossary.           (line  988)
* path entry finder:                     Glossary.           (line  993)
* path entry hook:                       Glossary.           (line 1002)
* path hooks:                            Import hooks.       (line    6)
* path() (於 importlib.resources 模組中): importlib resources -- Resources.
                                                             (line  105)
* path-like object:                      Glossary.           (line 1013)
* path; configuration; file:             site --- Site-specific configuration hook.
                                                             (line   63)
* path; operations:                      pathlib --- Object-oriented filesystem paths.
                                                             (line   10)
* path; operations <1>:                  os path --- Common pathname manipulations.
                                                             (line    9)
* pathconf() (於 os 模組中):             Files and Directories.
                                                             (line  543)
* pathconf_names (於 os 模組中):         Files and Directories.
                                                             (line  567)
* PathEntryFinder (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line   95)
* PATHEXT:                               Other Improvements<2>.
                                                             (line   30)
* PATHEXT <1>:                           Library<6>.         (line  117)
* PATHEXT <2>:                           安裝排除使用者介面. (line   57)
* PathFinder (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  102)
* pathlib (模組):                        pathlib --- Object-oriented filesystem paths.
                                                             (line    6)
* PathLike (os 中的類別):                Process Parameters. (line  113)
* pathname2url() (於 urllib.request 模組中): urllib request --- Extensible library for opening URLs.
                                                             (line  147)
* pathsep (於 os 模組中):                Miscellaneous System Information.
                                                             (line  115)
* path_hook() (importlib.machinery.FileFinder 的類別成員): importlib machinery -- Importers and path hooks.
                                                             (line  198)
* path_hooks (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line 1085)
* path_importer_cache (於 sys 模組中):   sys --- System-specific parameters and functions.
                                                             (line 1094)
* path_mtime() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  541)
* path_return_ok() (http.cookiejar.CookiePolicy 的方法): CookiePolicy Objects.
                                                             (line   56)
* path_stats() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  519)
* path_stats() (importlib.machinery.SourceFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  229)
* pattern (re.error 的屬性):             Module Contents.    (line  364)
* pattern (re.Pattern 的屬性):           Regular Expression Objects.
                                                             (line  118)
* Pattern (typing 中的類別):             Classes functions and decorators.
                                                             (line  478)
* pause() (於 signal 模組中):            Module contents<2>. (line  265)
* pause_reading() (asyncio.ReadTransport 的方法): Read-only Transports.
                                                             (line   12)
* pause_writing() (asyncio.BaseProtocol 的方法): Base Protocol.
                                                             (line   40)
* PAX_FORMAT (於 tarfile 模組中):        tarfile --- Read and write tar archive files.
                                                             (line  229)
* pax_headers (tarfile.TarFile 的屬性):  TarFile Objects.    (line  251)
* pax_headers (tarfile.TarInfo 的屬性):  TarInfo Objects.    (line   88)
* pbkdf2_hmac() (於 hashlib 模組中):     Key derivation.     (line   11)
* pd() (於 turtle 模組中):               Drawing state.      (line    6)
* Pdb (class in pdb):                    pdb --- The Python Debugger.
                                                             (line   17)
* Pdb (pdb 中的類別):                    pdb --- The Python Debugger.
                                                             (line  144)
* pdb (模組):                            pdb --- The Python Debugger.
                                                             (line    6)
* pdf() (statistics.NormalDist 的方法):  NormalDist objects. (line   68)
* peek() (bz2.BZ2File 的方法):           De compression of files.
                                                             (line   76)
* peek() (gzip.GzipFile 的方法):         gzip --- Support for gzip files.
                                                             (line  124)
* peek() (io.BufferedReader 的方法):     Buffered Streams.   (line   73)
* peek() (lzma.LZMAFile 的方法):         Reading and writing compressed files.
                                                             (line   84)
* peek() (weakref.finalize 的方法):      weakref --- Weak references.
                                                             (line  263)
* peer (smtpd.SMTPChannel 的屬性):       SMTPChannel Objects.
                                                             (line   95)
* PEM_cert_to_DER_cert() (於 ssl 模組中): Certificate handling.
                                                             (line   96)
* 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  311)
* PendingDeprecationWarning:             Warnings.           (line   22)
* pendown() (於 turtle 模組中):          Drawing state.      (line    6)
* pensize() (於 turtle 模組中):          Drawing state.      (line   18)
* penup() (於 turtle 模組中):            Drawing state.      (line   12)
* PEP:                                   Glossary.           (line 1025)
* PERCENT (於 token 模組中):             token --- Constants used with Python parse trees.
                                                             (line  122)
* PERCENTEQUAL (於 token 模組中):        token --- Constants used with Python parse trees.
                                                             (line  186)
* Performance:                           timeit --- Measure execution time of small code snippets.
                                                             (line    8)
* perf_counter() (於 time 模組中):       Functions<2>.       (line  180)
* perf_counter_ns() (於 time 模組中):    Functions<2>.       (line  191)
* perm() (於 math 模組中):               Number-theoretic and representation functions.
                                                             (line  177)
* PermissionError:                       OS exceptions.      (line   92)
* permutations() (於 itertools 模組中):  Itertool functions. (line  400)
* Persist() (msilib.SummaryInformation 的方法): Summary Information Objects.
                                                             (line   29)
* persistence:                           pickle --- Python object serialization.
                                                             (line    8)
* persistent; objects:                   pickle --- Python object serialization.
                                                             (line    8)
* persistent_id (pickle protocol):       Persistence of External Objects.
                                                             (line    6)
* persistent_id() (pickle.Pickler 的方法): Module Interface. (line  160)
* persistent_load (pickle protocol):     Persistence of External Objects.
                                                             (line    6)
* persistent_load() (pickle.Unpickler 的方法): Module Interface.
                                                             (line  274)
* pformat() (pprint.PrettyPrinter 的方法): PrettyPrinter Objects.
                                                             (line    8)
* pformat() (於 pprint 模組中):          pprint --- Data pretty printer.
                                                             (line   81)
* PF_CAN (於 socket 模組中):             Constants<8>.       (line   93)
* PF_PACKET (於 socket 模組中):          Constants<8>.       (line  144)
* PF_RDS (於 socket 模組中):             Constants<8>.       (line  154)
* pgettext() (gettext.GNUTranslations 的方法): The GNUTranslations class.
                                                             (line   68)
* pgettext() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   47)
* pgettext() (於 gettext 模組中):        GNU gettext API.    (line   73)
* PGO (於 test.support 模組中):          test support --- Utilities for the Python test suite.
                                                             (line   91)
* phase() (於 cmath 模組中):             Conversions to and from polar coordinates.
                                                             (line   22)
* 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   72)
* pi (於 cmath 模組中):                  Constants<3>.       (line    6)
* pi (於 math 模組中):                   Constants<2>.       (line    6)
* pi() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder Objects.
                                                             (line   56)
* pickle (模組):                         pickle --- Python object serialization.
                                                             (line    6)
* pickle() (於 copyreg 模組中):          copyreg --- Register pickle support functions.
                                                             (line   23)
* PickleBuffer (pickle 中的類別):        Module Interface.   (line  301)
* PickleError:                           Module Interface.   (line   95)
* Pickler (pickle 中的類別):             Module Interface.   (line  121)
* pickletools (模組):                    pickletools --- Tools for pickle developers.
                                                             (line    6)
* pickletools command line option; -a:   Command line options<3>.
                                                             (line    6)
* pickletools command line option; –annotate: Command line options<3>.
                                                             (line    6)
* pickletools command line option; –indentlevel=<num>: Command line options<3>.
                                                             (line   14)
* pickletools command line option; -l:   Command line options<3>.
                                                             (line   14)
* pickletools command line option; -m:   Command line options<3>.
                                                             (line   18)
* pickletools command line option; –memo: Command line options<3>.
                                                             (line   18)
* pickletools command line option; -o:   Command line options<3>.
                                                             (line   10)
* pickletools command line option; –output=<file>: Command line options<3>.
                                                             (line   10)
* pickletools command line option; -p:   Command line options<3>.
                                                             (line   23)
* pickletools command line option; –preamble=<preamble>: Command line options<3>.
                                                             (line   23)
* pickling; objects:                     pickle --- Python object serialization.
                                                             (line    8)
* PicklingError:                         Module Interface.   (line  100)
* pid (asyncio.asyncio.subprocess.Process 的屬性): Interacting with Subprocesses.
                                                             (line  132)
* pid (multiprocessing.Process 的屬性):  Process and exceptions.
                                                             (line  107)
* pid (subprocess.Popen 的屬性):         Popen Objects.      (line  138)
* PIPE (於 subprocess 模組中):           Using the subprocess Module.
                                                             (line  140)
* Pipe() (於 multiprocessing 模組中):    Pipes and Queues.   (line   74)
* pipe() (於 os 模組中):                 File Descriptor Operations.
                                                             (line  360)
* pipe2() (於 os 模組中):                File Descriptor Operations.
                                                             (line  370)
* pipes (模組):                          pipes --- Interface to shell pipelines.
                                                             (line    6)
* PIPE_BUF (於 select 模組中):           select --- Waiting for I/O completion.
                                                             (line  155)
* 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 --- Utilities for the Python test suite.
                                                             (line   95)
* PIP_USER:                              Windows<15>.        (line    7)
* pkgutil (模組):                        pkgutil --- Package extension utility.
                                                             (line    6)
* PKG_DIRECTORY (於 imp 模組中):         imp --- Access the import internals.
                                                             (line  325)
* placeholder (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  266)
* PLAT:                                  distutils util --- Miscellaneous other utility functions.
                                                             (line   79)
* platform (in module sys):              Process-wide parameters.
                                                             (line  172)
* platform (於 sys 模組中):              sys --- System-specific parameters and functions.
                                                             (line 1107)
* platform (模組):                       platform --- Access to underlying platform's identifying data.
                                                             (line    6)
* platform() (於 platform 模組中):       Cross Platform.     (line   47)
* PlaySound() (於 winsound 模組中):      winsound --- Sound-playing interface for Windows.
                                                             (line   20)
* plist; file:                           plistlib --- Generate and parse Mac OS X plist files.
                                                             (line    8)
* plistlib (模組):                       plistlib --- Generate and parse Mac OS X plist files.
                                                             (line    6)
* plock() (於 os 模組中):                Process Management. (line  325)
* plus:                                  Unary arithmetic and bitwise operations.
                                                             (line   13)
* PLUS (於 token 模組中):                token --- Constants used with Python parse trees.
                                                             (line   82)
* plus() (decimal.Context 的方法):       Context objects.    (line  412)
* PLUSEQUAL (於 token 模組中):           token --- Constants used with Python parse trees.
                                                             (line  170)
* pm() (於 pdb 模組中):                  pdb --- The Python Debugger.
                                                             (line  134)
* POINTER() (於 ctypes 模組中):          Utility functions.  (line  149)
* pointer() (於 ctypes 模組中):          Utility functions.  (line  155)
* polar() (於 cmath 模組中):             Conversions to and from polar coordinates.
                                                             (line   42)
* Policy (email.policy 中的類別):        email policy Policy Objects.
                                                             (line  128)
* poll() (multiprocessing.connection.Connection 的方法): Connection Objects<2>.
                                                             (line   42)
* poll() (select.devpoll 的方法):        /dev/poll Polling Objects.
                                                             (line   65)
* poll() (select.epoll 的方法):          Edge and Level Trigger Polling epoll Objects.
                                                             (line   93)
* poll() (select.poll 的方法):           Polling Objects.    (line   77)
* poll() (subprocess.Popen 的方法):      Popen Objects.      (line    8)
* poll() (於 select 模組中):             select --- Waiting for I/O completion.
                                                             (line   83)
* PollSelector (selectors 中的類別):     Classes<3>.         (line  171)
* Pool (multiprocessing.pool 中的類別):  Process Pools.      (line    9)
* pop() (array.array 的方法):            array --- 高效率的數值型態陣列.
                                                             (line  181)
* pop() (collections.deque 的方法):      deque objects.      (line   87)
* pop() (dict 的方法):                   Mapping Types --- dict.
                                                             (line  178)
* pop() (frozenset 的方法):              Set Types --- set frozenset.
                                                             (line  208)
* pop() (mailbox.Mailbox 的方法):        Mailbox objects.    (line  208)
* pop() (sequence method):               Mutable Sequence Types.
                                                             (line   16)
* POP3 (poplib 中的類別):                poplib --- POP3 protocol client.
                                                             (line   29)
* POP3; protocol:                        poplib --- POP3 protocol client.
                                                             (line    8)
* POP3_SSL (poplib 中的類別):            poplib --- POP3 protocol client.
                                                             (line   45)
* Popen (subprocess 中的類別):           Popen Constructor.  (line   11)
* popen() (in module os):                The standard type hierarchy.
                                                             (line  629)
* popen() (in module os) <1>:            select --- Waiting for I/O completion.
                                                             (line  136)
* popen() (於 os 模組中):                Process Management. (line  332)
* popitem() (collections.OrderedDict 的方法): OrderedDict objects.
                                                             (line   46)
* popitem() (dict 的方法):               Mapping Types --- dict.
                                                             (line  184)
* popitem() (mailbox.Mailbox 的方法):    Mailbox objects.    (line  217)
* popleft() (collections.deque 的方法):  deque objects.      (line   92)
* poplib (模組):                         poplib --- POP3 protocol client.
                                                             (line    6)
* PopupMenu (tkinter.tix 中的類別):      Basic Widgets.      (line   53)
* pop_alignment() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line   97)
* pop_all() (contextlib.ExitStack 的方法): Utilities.        (line  426)
* POP_BLOCK (opcode):                    Python Bytecode Instructions.
                                                             (line  372)
* POP_EXCEPT (opcode):                   Python Bytecode Instructions.
                                                             (line  377)
* POP_FINALLY (opcode):                  Python Bytecode Instructions.
                                                             (line  385)
* pop_font() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line  109)
* POP_JUMP_IF_FALSE (opcode):            Python Bytecode Instructions.
                                                             (line  660)
* POP_JUMP_IF_TRUE (opcode):             Python Bytecode Instructions.
                                                             (line  653)
* pop_margin() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line  121)
* pop_source() (shlex.shlex 的方法):     shlex Objects.      (line   63)
* pop_style() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line  132)
* POP_TOP (opcode):                      Python Bytecode Instructions.
                                                             (line   59)
* port (http.cookiejar.Cookie 的屬性):   Cookie Objects<2>.  (line   36)
* portion:                               Glossary.           (line 1041)
* port_specified (http.cookiejar.Cookie 的屬性): Cookie Objects<2>.
                                                             (line   77)
* pos (json.JSONDecodeError 的屬性):     例外<2>.            (line   19)
* pos (re.error 的屬性):                 Module Contents.    (line  368)
* pos (re.Match 的屬性):                 Match Objects.      (line  163)
* pos() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line  138)
* pos() (於 turtle 模組中):              Tell Turtle's state.
                                                             (line    6)
* position (xml.etree.ElementTree.ParseError 的屬性): Exceptions<13>.
                                                             (line   20)
* position() (於 turtle 模組中):         Tell Turtle's state.
                                                             (line    6)
* positional argument:                   Glossary.           (line 1047)
* posix (模組):                          posix --- The most common POSIX system calls.
                                                             (line    6)
* POSIX Shared Memory:                   multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line   10)
* POSIX; I/O control:                    termios --- POSIX style tty control.
                                                             (line    6)
* POSIXLY_CORRECT:                       getopt --- C-style parser for command line options.
                                                             (line   71)
* PosixPath (pathlib 中的類別):          Concrete paths.     (line   22)
* posix_fadvise() (於 os 模組中):        File Descriptor Operations.
                                                             (line  390)
* POSIX_FADV_DONTNEED (於 os 模組中):    File Descriptor Operations.
                                                             (line  404)
* POSIX_FADV_NOREUSE (於 os 模組中):     File Descriptor Operations.
                                                             (line  404)
* POSIX_FADV_NORMAL (於 os 模組中):      File Descriptor Operations.
                                                             (line  404)
* POSIX_FADV_RANDOM (於 os 模組中):      File Descriptor Operations.
                                                             (line  404)
* POSIX_FADV_SEQUENTIAL (於 os 模組中):  File Descriptor Operations.
                                                             (line  404)
* POSIX_FADV_WILLNEED (於 os 模組中):    File Descriptor Operations.
                                                             (line  404)
* posix_fallocate() (於 os 模組中):      File Descriptor Operations.
                                                             (line  381)
* posix_spawn() (於 os 模組中):          Process Management. (line  355)
* posix_spawnp() (於 os 模組中):         Process Management. (line  445)
* POSIX_SPAWN_CLOSE (於 os 模組中):      Process Management. (line  383)
* POSIX_SPAWN_DUP2 (於 os 模組中):       Process Management. (line  389)
* POSIX_SPAWN_OPEN (於 os 模組中):       Process Management. (line  377)
* post() (nntplib.NNTP 的方法):          Methods<3>.         (line  278)
* post() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line  176)
* postcmd() (cmd.Cmd 的方法):            Cmd Objects.        (line   96)
* postloop() (cmd.Cmd 的方法):           Cmd Objects.        (line  114)
* post_handshake_auth (ssl.SSLContext 的屬性): SSL Contexts. (line  602)
* post_mortem() (於 pdb 模組中):         pdb --- The Python Debugger.
                                                             (line  127)
* post_setup() (venv.EnvBuilder 的方法): API<2>.             (line  104)
* pow() (內建函式):                      內建函式.           (line 1269)
* pow() (於 math 模組中):                Power and logarithmic functions.
                                                             (line   60)
* pow() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line  143)
* power() (decimal.Context 的方法):      Context objects.    (line  418)
* power; operation:                      The power operator. (line    6)
* pp (pdb command):                      Debugger Commands.  (line  242)
* pp() (於 pprint 模組中):               pprint --- Data pretty printer.
                                                             (line   93)
* pprint (模組):                         pprint --- Data pretty printer.
                                                             (line    6)
* pprint() (pprint.PrettyPrinter 的方法): PrettyPrinter Objects.
                                                             (line   14)
* pprint() (於 pprint 模組中):           pprint --- Data pretty printer.
                                                             (line  103)
* prcal() (於 calendar 模組中):          calendar --- General calendar-related functions.
                                                             (line  344)
* pread() (於 os 模組中):                File Descriptor Operations.
                                                             (line  418)
* preadv() (於 os 模組中):               File Descriptor Operations.
                                                             (line  431)
* preamble (email.message.EmailMessage 的屬性): email message Representing an email message.
                                                             (line  679)
* preamble (email.message.Message 的屬性): email message Message Representing an email message using the compat32 API.
                                                             (line  691)
* precmd() (cmd.Cmd 的方法):             Cmd Objects.        (line   86)
* prefix:                                Python-related paths and files.
                                                             (line    7)
* prefix <1>:                            Include Files.      (line   37)
* prefix <2>:                            Include Files.      (line   40)
* prefix <3>:                            Include Files.      (line   47)
* prefix (xml.dom.Attr 的屬性):          Attr Objects.       (line   18)
* prefix (xml.dom.Node 的屬性):          Node Objects.       (line   69)
* prefix (zipimport.zipimporter 的屬性): zipimporter Objects.
                                                             (line   74)
* PREFIX (於 distutils.sysconfig 模組中): distutils sysconfig --- System configuration information.
                                                             (line   19)
* prefix (於 sys 模組中):                sys --- System-specific parameters and functions.
                                                             (line 1169)
* PREFIXES (於 site 模組中):             Module contents<3>. (line    6)
* prefixlen (ipaddress.IPv4Network 的屬性): Network objects. (line  132)
* prefixlen (ipaddress.IPv6Network 的屬性): Network objects. (line  329)
* preloop() (cmd.Cmd 的方法):            Cmd Objects.        (line  108)
* prepare() (logging.handlers.QueueHandler 的方法): QueueHandler.
                                                             (line   40)
* prepare() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   53)
* prepare_class() (於 types 模組中):     Dynamic Type Creation.
                                                             (line   22)
* prepare_input_source() (於 xml.sax.saxutils 模組中): xml sax saxutils --- SAX Utilities.
                                                             (line   77)
* prepend() (pipes.Template 的方法):     Template Objects.   (line   37)
* preprocess() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  432)
* PrettyPrinter (pprint 中的類別):       pprint --- Data pretty printer.
                                                             (line   27)
* prev() (tkinter.ttk.Treeview 的方法):  ttk Treeview.       (line  242)
* previousSibling (xml.dom.Node 的屬性): Node Objects.       (line   32)
* primary:                               Primaries.          (line    6)
* print (2to3 fixer):                    Fixers.             (line  257)
* print() (built-in function); __str__() (object method): Basic customization.
                                                             (line  129)
* print() (內建函式):                    內建函式.           (line 1304)
* printable (於 string 模組中):          String constants.   (line   41)
* printdir() (zipfile.ZipFile 的方法):   ZipFile Objects.    (line  207)
* printf-style formatting:               printf-style String Formatting.
                                                             (line    6)
* printf-style formatting <1>:           printf-style Bytes Formatting.
                                                             (line    6)
* print_callees() (pstats.Stats 的方法): The Stats Class.    (line  217)
* print_callers() (pstats.Stats 的方法): The Stats Class.    (line  196)
* print_directory() (於 cgi 模組中):     Functions<8>.       (line   59)
* print_environ() (於 cgi 模組中):       Functions<8>.       (line   51)
* print_environ_usage() (於 cgi 模組中): Functions<8>.       (line   63)
* print_exc() (timeit.Timer 的方法):     Python Interface.   (line  131)
* print_exc() (於 traceback 模組中):     traceback --- Print or retrieve a stack traceback.
                                                             (line   60)
* print_exception() (於 traceback 模組中): traceback --- Print or retrieve a stack traceback.
                                                             (line   33)
* PRINT_EXPR (opcode):                   Python Bytecode Instructions.
                                                             (line  311)
* print_form() (於 cgi 模組中):          Functions<8>.       (line   55)
* print_help() (argparse.ArgumentParser 的方法): Printing help.
                                                             (line   16)
* print_last() (於 traceback 模組中):    traceback --- Print or retrieve a stack traceback.
                                                             (line   65)
* print_stack() (asyncio.Task 的方法):   Task Object.        (line  189)
* print_stack() (於 traceback 模組中):   traceback --- Print or retrieve a stack traceback.
                                                             (line   72)
* print_stats() (profile.Profile 的方法): profile and cProfile Module Reference.
                                                             (line   91)
* print_stats() (pstats.Stats 的方法):   The Stats Class.    (line  164)
* print_tb() (於 traceback 模組中):      traceback --- Print or retrieve a stack traceback.
                                                             (line   22)
* print_usage() (argparse.ArgumentParser 的方法): Printing help.
                                                             (line   10)
* print_usage() (optparse.OptionParser 的方法): Other methods.
                                                             (line   15)
* print_version() (optparse.OptionParser 的方法): Printing a version string.
                                                             (line   26)
* PriorityQueue (asyncio 中的類別):      Priority Queue.     (line    6)
* PriorityQueue (queue 中的類別):        queue --- A synchronized queue class.
                                                             (line   50)
* PRIO_PGRP (於 os 模組中):              Process Parameters. (line  271)
* PRIO_PROCESS (於 os 模組中):           Process Parameters. (line  271)
* PRIO_USER (於 os 模組中):              Process Parameters. (line  271)
* private; names:                        Identifiers Names.  (line   14)
* prlimit() (於 resource 模組中):        Resource Limits.    (line   56)
* prmonth() (calendar.TextCalendar 的方法): calendar --- General calendar-related functions.
                                                             (line  143)
* prmonth() (於 calendar 模組中):        calendar --- General calendar-related functions.
                                                             (line  335)
* ProactorEventLoop (asyncio 中的類別):  Event Loop Implementations.
                                                             (line   29)
* procedure; call:                       Expression statements.
                                                             (line   17)
* Process (multiprocessing 中的類別):    Process and exceptions.
                                                             (line    6)
* process() (logging.LoggerAdapter 的方法): LoggerAdapter Objects.
                                                             (line   16)
* process; group:                        Process Parameters. (line  179)
* process; group <1>:                    Process Parameters. (line  237)
* process; id:                           Process Parameters. (line  243)
* process; id of parent:                 Process Parameters. (line  247)
* process; killing:                      Process Management. (line  289)
* process; killing <1>:                  Process Management. (line  311)
* process; scheduling priority:          Process Parameters. (line  258)
* process; scheduling priority <1>:      Process Parameters. (line  389)
* process; signalling:                   Process Management. (line  289)
* process; signalling <1>:               Process Management. (line  311)
* ProcessError:                          Process and exceptions.
                                                             (line  204)
* processes, light-weight:               _thread --- Low-level threading API.
                                                             (line    6)
* processingInstruction() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line  164)
* ProcessingInstruction() (於 xml.etree.ElementTree 模組中): Functions<6>.
                                                             (line  166)
* ProcessingInstructionHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  236)
* ProcessLookupError:                    OS exceptions.      (line   98)
* processor time:                        Functions<2>.       (line  200)
* processor time <1>:                    Functions<2>.       (line  479)
* processor() (於 platform 模組中):      Cross Platform.     (line   68)
* ProcessPoolExecutor (concurrent.futures 中的類別): ProcessPoolExecutor.
                                                             (line   21)
* process_exited() (asyncio.SubprocessProtocol 的方法): Subprocess Protocols.
                                                             (line   26)
* process_message() (smtpd.SMTPServer 的方法): SMTPServer Objects.
                                                             (line   41)
* process_request() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line  156)
* process_time() (於 time 模組中):       Functions<2>.       (line  198)
* process_time_ns() (於 time 模組中):    Functions<2>.       (line  208)
* process_tokens() (於 tabnanny 模組中): tabnanny --- Detection of ambiguous indentation.
                                                             (line   42)
* prod() (於 math 模組中):               Number-theoretic and representation functions.
                                                             (line  194)
* product() (於 itertools 模組中):       Itertool functions. (line  461)
* Profile (profile 中的類別):            profile and cProfile Module Reference.
                                                             (line   35)
* profile (模組):                        profile and cProfile Module Reference.
                                                             (line    6)
* profile function:                      threading --- Thread-based parallelism.
                                                             (line  131)
* profile function <1>:                  sys --- System-specific parameters and functions.
                                                             (line  739)
* profile function <2>:                  sys --- System-specific parameters and functions.
                                                             (line 1227)
* profiler:                              sys --- System-specific parameters and functions.
                                                             (line  739)
* profiler <1>:                          sys --- System-specific parameters and functions.
                                                             (line 1227)
* profiling, deterministic:              Introduction to the profilers.
                                                             (line    6)
* program:                               Complete Python programs.
                                                             (line    6)
* ProgrammingError:                      Exceptions<3>.      (line   25)
* Progressbar (tkinter.ttk 中的類別):    ttk Progressbar.    (line    6)
* prompt (cmd.Cmd 的屬性):               Cmd Objects.        (line  123)
* prompts, interpreter:                  sys --- System-specific parameters and functions.
                                                             (line 1189)
* prompt_user_passwd() (urllib.request.FancyURLopener 的方法): Legacy interface.
                                                             (line  184)
* propagate (logging.Logger 的屬性):     Logger Objects.     (line   25)
* property (內建類別):                   內建函式.           (line 1329)
* property list:                         plistlib --- Generate and parse Mac OS X plist files.
                                                             (line    8)
* PropertyMock (unittest.mock 中的類別): The Mock Class.     (line  627)
* property_declaration_handler (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line  101)
* property_dom_node (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line  108)
* property_lexical_handler (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line   94)
* property_xml_string (於 xml.sax.handler 模組中): xml sax handler --- Base classes for SAX handlers.
                                                             (line  115)
* proto (socket.socket 的屬性):          Socket Objects.     (line  602)
* Protocol (asyncio 中的類別):           Base Protocols.     (line   10)
* protocol (ssl.SSLContext 的屬性):      SSL Contexts.       (line  625)
* Protocol (typing 中的類別):            Classes functions and decorators.
                                                             (line   71)
* protocol; context management:          Context Manager Types.
                                                             (line    6)
* protocol; iterator:                    Iterator Types.     (line    6)
* protocol; Telnet:                      telnetlib --- Telnet client.
                                                             (line    8)
* ProtocolError (xmlrpc.client 中的類別): ProtocolError Objects.
                                                             (line    6)
* PROTOCOL_SSLv2 (於 ssl 模組中):        Constants<9>.       (line  149)
* PROTOCOL_SSLv23 (於 ssl 模組中):       Constants<9>.       (line  143)
* PROTOCOL_SSLv3 (於 ssl 模組中):        Constants<9>.       (line  161)
* PROTOCOL_TLS (於 ssl 模組中):          Constants<9>.       (line  118)
* PROTOCOL_TLSv1 (於 ssl 模組中):        Constants<9>.       (line  175)
* PROTOCOL_TLSv1_1 (於 ssl 模組中):      Constants<9>.       (line  183)
* PROTOCOL_TLSv1_2 (於 ssl 模組中):      Constants<9>.       (line  194)
* PROTOCOL_TLS_CLIENT (於 ssl 模組中):   Constants<9>.       (line  126)
* PROTOCOL_TLS_SERVER (於 ssl 模組中):   Constants<9>.       (line  135)
* protocol_version (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  156)
* PROTOCOL_VERSION (imaplib.IMAP4 的屬性): IMAP4 Objects.    (line  377)
* prot_c() (ftplib.FTP_TLS 的方法):      FTP_TLS Objects.    (line   35)
* prot_p() (ftplib.FTP_TLS 的方法):      FTP_TLS Objects.    (line   31)
* provisional API:                       Glossary.           (line 1051)
* provisional package:                   Glossary.           (line 1071)
* proxy() (於 weakref 模組中):           weakref --- Weak references.
                                                             (line  130)
* proxyauth() (imaplib.IMAP4 的方法):    IMAP4 Objects.      (line  187)
* ProxyBasicAuthHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  363)
* ProxyDigestAuthHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  395)
* ProxyHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  289)
* ProxyType (於 weakref 模組中):         weakref --- Weak references.
                                                             (line  292)
* ProxyTypes (於 weakref 模組中):        weakref --- Weak references.
                                                             (line  300)
* pryear() (calendar.TextCalendar 的方法): calendar --- General calendar-related functions.
                                                             (line  158)
* ps1 (於 sys 模組中):                   sys --- System-specific parameters and functions.
                                                             (line 1186)
* ps2 (於 sys 模組中):                   sys --- System-specific parameters and functions.
                                                             (line 1186)
* pstats (模組):                         The Stats Class.    (line    7)
* pstdev() (於 statistics 模組中):       函式細節.           (line  271)
* pthreads:                              _thread --- Low-level threading API.
                                                             (line   16)
* pthread_getcpuclockid() (於 time 模組中): Functions<2>.    (line   21)
* pthread_kill() (於 signal 模組中):     Module contents<2>. (line  282)
* pthread_sigmask() (於 signal 模組中):  Module contents<2>. (line  311)
* pty (模組):                            pty --- Pseudo-terminal utilities.
                                                             (line    6)
* pu() (於 turtle 模組中):               Drawing state.      (line   12)
* publicId (xml.dom.DocumentType 的屬性): DocumentType Objects.
                                                             (line   17)
* PullDom (xml.dom.pulldom 中的類別):    xml dom pulldom --- Support for building partial DOM trees.
                                                             (line   77)
* punctuation (於 string 模組中):        String constants.   (line   36)
* punctuation_chars (shlex.shlex 的屬性): shlex Objects.     (line  182)
* PurePath (pathlib 中的類別):           Pure paths.         (line   10)
* PurePath.anchor (於 pathlib 模組中):   Methods and properties.
                                                             (line   40)
* PurePath.drive (於 pathlib 模組中):    Methods and properties.
                                                             (line    8)
* PurePath.name (於 pathlib 模組中):     Methods and properties.
                                                             (line   94)
* PurePath.parent (於 pathlib 模組中):   Methods and properties.
                                                             (line   66)
* PurePath.parents (於 pathlib 模組中):  Methods and properties.
                                                             (line   53)
* PurePath.parts (於 pathlib 模組中):    Accessing individual parts.
                                                             (line    9)
* PurePath.root (於 pathlib 模組中):     Methods and properties.
                                                             (line   24)
* PurePath.stem (於 pathlib 模組中):     Methods and properties.
                                                             (line  131)
* PurePath.suffix (於 pathlib 模組中):   Methods and properties.
                                                             (line  109)
* PurePath.suffixes (於 pathlib 模組中): Methods and properties.
                                                             (line  120)
* PurePosixPath (pathlib 中的類別):      Pure paths.         (line   68)
* PureProxy (smtpd 中的類別):            PureProxy Objects.  (line    6)
* PureWindowsPath (pathlib 中的類別):    Pure paths.         (line   78)
* purge() (於 re 模組中):                Module Contents.    (line  347)
* Purpose.CLIENT_AUTH (於 ssl 模組中):   Constants<9>.       (line  506)
* Purpose.SERVER_AUTH (於 ssl 模組中):   Constants<9>.       (line  497)
* push() (asynchat.async_chat 的方法):   asynchat --- Asynchronous socket command/response handler.
                                                             (line  101)
* push() (code.InteractiveConsole 的方法): Interactive Console Objects.
                                                             (line   27)
* push() (contextlib.ExitStack 的方法):  Utilities.          (line  393)
* pushbutton() (msilib.Dialog 的方法):   GUI classes.        (line   68)
* push_alignment() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line   90)
* push_async_callback() (contextlib.AsyncExitStack 的方法): Utilities.
                                                             (line  473)
* push_async_exit() (contextlib.AsyncExitStack 的方法): Utilities.
                                                             (line  468)
* push_font() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line  101)
* push_margin() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line  113)
* push_source() (shlex.shlex 的方法):    shlex Objects.      (line   56)
* push_style() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line  125)
* push_token() (shlex.shlex 的方法):     shlex Objects.      (line   16)
* push_with_producer() (asynchat.async_chat 的方法): asynchat --- Asynchronous socket command/response handler.
                                                             (line  109)
* put() (asyncio.Queue 的方法):          Queue.              (line   62)
* put() (multiprocessing.Queue 的方法):  Pipes and Queues.   (line  120)
* put() (multiprocessing.SimpleQueue 的方法): Pipes and Queues.
                                                             (line  216)
* put() (queue.Queue 的方法):            Queue Objects.      (line   29)
* put() (queue.SimpleQueue 的方法):      SimpleQueue Objects.
                                                             (line   20)
* putch() (於 msvcrt 模組中):            Console I/O.        (line   35)
* putenv() (於 os 模組中):               Process Parameters. (line  316)
* putheader() (http.client.HTTPConnection 的方法): HTTPConnection Objects.
                                                             (line  135)
* putp() (於 curses 模組中):             Functions<3>.       (line  376)
* putrequest() (http.client.HTTPConnection 的方法): HTTPConnection Objects.
                                                             (line  124)
* putwch() (於 msvcrt 模組中):           Console I/O.        (line   39)
* putwin() (curses.window 的方法):       Window Objects.     (line  453)
* put_nowait() (asyncio.Queue 的方法):   Queue.              (line   67)
* put_nowait() (multiprocessing.Queue 的方法): Pipes and Queues.
                                                             (line  135)
* put_nowait() (queue.Queue 的方法):     Queue Objects.      (line   40)
* put_nowait() (queue.SimpleQueue 的方法): SimpleQueue Objects.
                                                             (line   35)
* pvariance() (於 statistics 模組中):    函式細節.           (line  280)
* pwd (模組):                            pwd --- The password database.
                                                             (line    6)
* pwd() (ftplib.FTP 的方法):             FTP Objects.        (line  221)
* pwrite() (於 os 模組中):               File Descriptor Operations.
                                                             (line  489)
* pwritev() (於 os 模組中):              File Descriptor Operations.
                                                             (line  500)
* PyAnySet_Check (C 函式):               Set Objects.        (line   55)
* PyAnySet_CheckExact (C 函式):          Set Objects.        (line   60)
* PyArg_Parse (C 函式):                  API Functions.      (line   49)
* PyArg_ParseTuple (C 函式):             API Functions.      (line    6)
* PyArg_ParseTuple():                    Extracting Parameters in Extension Functions.
                                                             (line    6)
* PyArg_ParseTupleAndKeywords (C 函式):  API Functions.      (line   20)
* PyArg_ParseTupleAndKeywords():         Keyword Parameters for Extension Functions.
                                                             (line    6)
* PyArg_UnpackTuple (C 函式):            API Functions.      (line   60)
* PyArg_ValidateKeywordArguments (C 函式): API Functions.    (line   40)
* PyArg_VaParse (C 函式):                API Functions.      (line   13)
* PyArg_VaParseTupleAndKeywords (C 函式): API Functions.     (line   33)
* PyASCIIObject (C 型態):                Unicode Type.       (line   29)
* PyAsyncMethods (C 型態):               Async Object Structures.
                                                             (line    8)
* PyAsyncMethods.am_aiter (C 成員函數):  Async Object Structures.
                                                             (line   34)
* PyAsyncMethods.am_anext (C 成員函數):  Async Object Structures.
                                                             (line   46)
* PyAsyncMethods.am_await (C 成員函數):  Async Object Structures.
                                                             (line   22)
* PyBool_Check (C 函式):                 布林物件.           (line   11)
* PyBool_FromLong (C 函式):              布林物件.           (line   37)
* PyBufferProcs:                         Buffer Protocol.    (line   20)
* PyBufferProcs (C 型態):                Buffer Object Structures.
                                                             (line    6)
* PyBufferProcs.bf_getbuffer (C 成員函數): Buffer Object Structures.
                                                             (line   12)
* PyBufferProcs.bf_releasebuffer (C 成員函數): Buffer Object Structures.
                                                             (line   60)
* PyBuffer_FillContiguousStrides (C 函式): Buffer-related functions.
                                                             (line   78)
* PyBuffer_FillInfo (C 函式):            Buffer-related functions.
                                                             (line   87)
* PyBuffer_FromContiguous (C 函式):      Buffer-related functions.
                                                             (line   59)
* PyBuffer_GetPointer (C 函式):          Buffer-related functions.
                                                             (line   53)
* PyBuffer_IsContiguous (C 函式):        Buffer-related functions.
                                                             (line   46)
* PyBuffer_Release (C 函式):             Buffer-related functions.
                                                             (line   32)
* PyBuffer_SizeFromFormat (C 函式):      Buffer-related functions.
                                                             (line   41)
* PyBuffer_ToContiguous (C 函式):        Buffer-related functions.
                                                             (line   67)
* PyBUF_ANY_CONTIGUOUS (C 巨集):         contiguity requests.
                                                             (line   20)
* PyBUF_CONTIG (C 巨集):                 compound requests.  (line   36)
* PyBUF_CONTIG_RO (C 巨集):              compound requests.  (line   39)
* PyBUF_C_CONTIGUOUS (C 巨集):           contiguity requests.
                                                             (line   14)
* PyBUF_FORMAT (C 巨集):                 readonly format.    (line   14)
* PyBUF_FULL (C 巨集):                   compound requests.  (line   18)
* PyBUF_FULL_RO (C 巨集):                compound requests.  (line   21)
* PyBUF_F_CONTIGUOUS (C 巨集):           contiguity requests.
                                                             (line   17)
* PyBUF_INDIRECT (C 巨集):               shape strides suboffsets.
                                                             (line   14)
* PyBUF_ND (C 巨集):                     shape strides suboffsets.
                                                             (line   20)
* PyBUF_RECORDS (C 巨集):                compound requests.  (line   24)
* PyBUF_RECORDS_RO (C 巨集):             compound requests.  (line   27)
* PyBUF_SIMPLE (C 巨集):                 shape strides suboffsets.
                                                             (line   23)
* PyBUF_STRIDED (C 巨集):                compound requests.  (line   30)
* PyBUF_STRIDED_RO (C 巨集):             compound requests.  (line   33)
* PyBUF_STRIDES (C 巨集):                shape strides suboffsets.
                                                             (line   17)
* PyBUF_WRITABLE (C 巨集):               readonly format.    (line    6)
* PyByteArrayObject (C 型態):            Byte Array Objects. (line    6)
* PyByteArray_AsString (C 函式):         Direct API functions.
                                                             (line   23)
* PyByteArray_AS_STRING (C 函式):        Macros.             (line    8)
* PyByteArray_Check (C 函式):            Type check macros.  (line    6)
* PyByteArray_CheckExact (C 函式):       Type check macros.  (line   11)
* PyByteArray_Concat (C 函式):           Direct API functions.
                                                             (line   15)
* PyByteArray_FromObject (C 函式):       Direct API functions.
                                                             (line    6)
* PyByteArray_FromStringAndSize (C 函式): Direct API functions.
                                                             (line   10)
* PyByteArray_GET_SIZE (C 函式):         Macros.             (line   12)
* PyByteArray_Resize (C 函式):           Direct API functions.
                                                             (line   29)
* PyByteArray_Size (C 函式):             Direct API functions.
                                                             (line   19)
* PyByteArray_Type (C 變數):             Byte Array Objects. (line   11)
* PyBytesObject (C 型態):                Bytes Objects<2>.   (line    9)
* PyBytes_AsString (C 函式):             Bytes Objects<2>.   (line  125)
* PyBytes_AsStringAndSize (C 函式):      Bytes Objects<2>.   (line  142)
* PyBytes_AS_STRING (C 函式):            Bytes Objects<2>.   (line  137)
* PyBytes_Check (C 函式):                Bytes Objects<2>.   (line   20)
* PyBytes_CheckExact (C 函式):           Bytes Objects<2>.   (line   25)
* PyBytes_Concat (C 函式):               Bytes Objects<2>.   (line  164)
* PyBytes_ConcatAndDel (C 函式):         Bytes Objects<2>.   (line  173)
* PyBytes_FromFormat (C 函式):           Bytes Objects<2>.   (line   43)
* PyBytes_FromFormatV (C 函式):          Bytes Objects<2>.   (line  106)
* PyBytes_FromObject (C 函式):           Bytes Objects<2>.   (line  112)
* PyBytes_FromString (C 函式):           Bytes Objects<2>.   (line   30)
* PyBytes_FromStringAndSize (C 函式):    Bytes Objects<2>.   (line   35)
* PyBytes_GET_SIZE (C 函式):             Bytes Objects<2>.   (line  120)
* PyBytes_Size (C 函式):                 Bytes Objects<2>.   (line  116)
* PyBytes_Type (C 變數):                 Bytes Objects<2>.   (line   14)
* pycache_prefix (於 sys 模組中):        sys --- System-specific parameters and functions.
                                                             (line  288)
* PyCallable_Check (C 函式):             Object Protocol.    (line  248)
* PyCallIter_Check (C 函式):             迭代器（Iterator）物件.
                                                             (line   34)
* PyCallIter_New (C 函式):               迭代器（Iterator）物件.
                                                             (line   38)
* PyCallIter_Type (C 變數):              迭代器（Iterator）物件.
                                                             (line   28)
* PyCapsule (C 型態):                    Capsules<2>.        (line   11)
* PyCapsule_CheckExact (C 函式):         Capsules<2>.        (line   29)
* PyCapsule_Destructor (C 型態):         Capsules<2>.        (line   20)
* PyCapsule_GetContext (C 函式):         Capsules<2>.        (line   76)
* PyCapsule_GetDestructor (C 函式):      Capsules<2>.        (line   65)
* PyCapsule_GetName (C 函式):            Capsules<2>.        (line   86)
* PyCapsule_GetPointer (C 函式):         Capsules<2>.        (line   54)
* PyCapsule_Import (C 函式):             Capsules<2>.        (line   96)
* PyCapsule_IsValid (C 函式):            Capsules<2>.        (line  110)
* PyCapsule_New (C 函式):                Capsules<2>.        (line   33)
* PyCapsule_SetContext (C 函式):         Capsules<2>.        (line  125)
* PyCapsule_SetDestructor (C 函式):      Capsules<2>.        (line  132)
* PyCapsule_SetName (C 函式):            Capsules<2>.        (line  141)
* PyCapsule_SetPointer (C 函式):         Capsules<2>.        (line  150)
* PyCellObject (C 型態):                 Cell 物件.          (line   16)
* PyCell_Check (C 函式):                 Cell 物件.          (line   24)
* PyCell_Get (C 函式):                   Cell 物件.          (line   32)
* PyCell_GET (C 函式):                   Cell 物件.          (line   35)
* PyCell_New (C 函式):                   Cell 物件.          (line   28)
* PyCell_Set (C 函式):                   Cell 物件.          (line   40)
* PyCell_SET (C 函式):                   Cell 物件.          (line   47)
* PyCell_Type (C 變數):                  Cell 物件.          (line   20)
* PyCFunction (C 型態):                  通用物件結構.       (line   95)
* PyCFunctionWithKeywords (C 型態):      通用物件結構.       (line  104)
* PycInvalidationMode (py_compile 中的類別): py_compile --- Compile Python source files.
                                                             (line   91)
* pyclbr (模組):                         pyclbr --- Python module browser support.
                                                             (line    6)
* PyCodec_BackslashReplaceErrors (C 函式): Registry API for Unicode encoding error handlers.
                                                             (line   49)
* PyCodec_Decode (C 函式):               Codec registry and support functions.
                                                             (line   29)
* PyCodec_Decoder (C 函式):              Codec lookup API.   (line   15)
* PyCodec_Encode (C 函式):               Codec registry and support functions.
                                                             (line   19)
* PyCodec_Encoder (C 函式):              Codec lookup API.   (line   11)
* PyCodec_IgnoreErrors (C 函式):         Registry API for Unicode encoding error handlers.
                                                             (line   37)
* PyCodec_IncrementalDecoder (C 函式):   Codec lookup API.   (line   24)
* PyCodec_IncrementalEncoder (C 函式):   Codec lookup API.   (line   19)
* PyCodec_KnownEncoding (C 函式):        Codec registry and support functions.
                                                             (line   14)
* PyCodec_LookupError (C 函式):          Registry API for Unicode encoding error handlers.
                                                             (line   28)
* PyCodec_NameReplaceErrors (C 函式):    Registry API for Unicode encoding error handlers.
                                                             (line   53)
* PyCodec_Register (C 函式):             Codec registry and support functions.
                                                             (line    6)
* PyCodec_RegisterError (C 函式):        Registry API for Unicode encoding error handlers.
                                                             (line    6)
* PyCodec_ReplaceErrors (C 函式):        Registry API for Unicode encoding error handlers.
                                                             (line   41)
* PyCodec_StreamReader (C 函式):         Codec lookup API.   (line   29)
* PyCodec_StreamWriter (C 函式):         Codec lookup API.   (line   35)
* PyCodec_StrictErrors (C 函式):         Registry API for Unicode encoding error handlers.
                                                             (line   34)
* PyCodec_XMLCharRefReplaceErrors (C 函式): Registry API for Unicode encoding error handlers.
                                                             (line   45)
* PyCodeObject (C 型態):                 Code Objects<2>.    (line   10)
* PyCode_Check (C 函式):                 Code Objects<2>.    (line   20)
* PyCode_GetNumFree (C 函式):            Code Objects<2>.    (line   24)
* PyCode_New (C 函式):                   Code Objects<2>.    (line   28)
* PyCode_NewEmpty (C 函式):              Code Objects<2>.    (line   56)
* PyCode_NewWithPosOnlyArgs (C 函式):    Code Objects<2>.    (line   43)
* PyCode_Type (C 變數):                  Code Objects<2>.    (line   15)
* PyCompactUnicodeObject (C 型態):       Unicode Type.       (line   29)
* PyCompileError:                        py_compile --- Compile Python source files.
                                                             (line   19)
* PyCompilerFlags (C 型態):              The Very High Level Layer.
                                                             (line  394)
* PyCompilerFlags.cf_feature_version (C 成員函數): The Very High Level Layer.
                                                             (line  410)
* PyCompilerFlags.cf_flags (C 成員函數): The Very High Level Layer.
                                                             (line  406)
* PyComplexObject (C 型態):              Complex Numbers as Python Objects.
                                                             (line    6)
* PyComplex_AsCComplex (C 函式):         Complex Numbers as Python Objects.
                                                             (line   43)
* PyComplex_Check (C 函式):              Complex Numbers as Python Objects.
                                                             (line   17)
* PyComplex_CheckExact (C 函式):         Complex Numbers as Python Objects.
                                                             (line   22)
* PyComplex_FromCComplex (C 函式):       Complex Numbers as Python Objects.
                                                             (line   27)
* PyComplex_FromDoubles (C 函式):        Complex Numbers as Python Objects.
                                                             (line   31)
* PyComplex_ImagAsDouble (C 函式):       Complex Numbers as Python Objects.
                                                             (line   39)
* PyComplex_RealAsDouble (C 函式):       Complex Numbers as Python Objects.
                                                             (line   35)
* PyComplex_Type (C 變數):               Complex Numbers as Python Objects.
                                                             (line   11)
* PyConfig (C 型態):                     PyConfig.           (line    6)
* PyConfig.argv (C 成員函數):            PyConfig.           (line   99)
* PyConfig.base_executable (C 成員函數): PyConfig.           (line  111)
* PyConfig.base_exec_prefix (C 成員函數): PyConfig.          (line  107)
* PyConfig.base_prefix (C 成員函數):     PyConfig.           (line  116)
* PyConfig.buffered_stdio (C 成員函數):  PyConfig.           (line  120)
* PyConfig.bytes_warning (C 成員函數):   PyConfig.           (line  127)
* PyConfig.check_hash_pycs_mode (C 成員函數): PyConfig.      (line  134)
* PyConfig.configure_c_stdio (C 成員函數): PyConfig.         (line  144)
* PyConfig.dev_mode (C 成員函數):        PyConfig.           (line  150)
* PyConfig.dump_refs (C 成員函數):       PyConfig.           (line  154)
* PyConfig.executable (C 成員函數):      PyConfig.           (line  165)
* PyConfig.exec_prefix (C 成員函數):     PyConfig.           (line  161)
* PyConfig.faulthandler (C 成員函數):    PyConfig.           (line  169)
* PyConfig.filesystem_encoding (C 成員函數): PyConfig.       (line  174)
* PyConfig.filesystem_errors (C 成員函數): PyConfig.         (line  178)
* PyConfig.hash_seed (C 成員函數):       PyConfig.           (line  183)
* PyConfig.home (C 成員函數):            PyConfig.           (line  193)
* PyConfig.import_time (C 成員函數):     PyConfig.           (line  200)
* PyConfig.inspect (C 成員函數):         PyConfig.           (line  204)
* PyConfig.install_signal_handlers (C 成員函數): PyConfig.   (line  208)
* PyConfig.interactive (C 成員函數):     PyConfig.           (line  212)
* PyConfig.isolated (C 成員函數):        PyConfig.           (line  216)
* PyConfig.legacy_windows_stdio (C 成員函數): PyConfig.      (line  230)
* PyConfig.malloc_stats (C 成員函數):    PyConfig.           (line  239)
* PyConfig.module_search_paths (C 成員函數): PyConfig.       (line  255)
* PyConfig.module_search_paths_set (C 成員函數): PyConfig.   (line  257)
* PyConfig.optimization_level (C 成員函數): PyConfig.        (line  264)
* PyConfig.parser_debug (C 成員函數):    PyConfig.           (line  280)
* PyConfig.parse_argv (C 成員函數):      PyConfig.           (line  274)
* PyConfig.pathconfig_warnings (C 成員函數): PyConfig.       (line  285)
* PyConfig.prefix (C 成員函數):          PyConfig.           (line  291)
* PyConfig.program_name (C 成員函數):    PyConfig.           (line  295)
* PyConfig.pycache_prefix (C 成員函數):  PyConfig.           (line  300)
* PyConfig.pythonpath_env (C 成員函數):  PyConfig.           (line  247)
* PyConfig.quiet (C 成員函數):           PyConfig.           (line  306)
* PyConfig.run_command (C 成員函數):     PyConfig.           (line  311)
* PyConfig.run_filename (C 成員函數):    PyConfig.           (line  316)
* PyConfig.run_module (C 成員函數):      PyConfig.           (line  320)
* PyConfig.show_alloc_count (C 成員函數): PyConfig.          (line  325)
* PyConfig.show_ref_count (C 成員函數):  PyConfig.           (line  333)
* PyConfig.site_import (C 成員函數):     PyConfig.           (line  342)
* PyConfig.skip_source_first_line (C 成員函數): PyConfig.    (line  346)
* PyConfig.stdio_encoding (C 成員函數):  PyConfig.           (line  350)
* PyConfig.stdio_errors (C 成員函數):    PyConfig.           (line  352)
* PyConfig.tracemalloc (C 成員函數):     PyConfig.           (line  357)
* PyConfig.user_site_directory (C 成員函數): PyConfig.       (line  365)
* PyConfig.use_environment (C 成員函數): PyConfig.           (line  361)
* PyConfig.use_hash_seed (C 成員函數):   PyConfig.           (line  185)
* PyConfig.verbose (C 成員函數):         PyConfig.           (line  369)
* PyConfig.warnoptions (C 成員函數):     PyConfig.           (line  373)
* PyConfig.write_bytecode (C 成員函數):  PyConfig.           (line  384)
* PyConfig.xoptions (C 成員函數):        PyConfig.           (line  391)
* PyConfig_Clear (C 函式):               PyConfig.           (line   69)
* PyConfig_InitIsolatedConfig (C 函式):  PyConfig.           (line   17)
* PyConfig_InitPythonConfig (C 函式):    PyConfig.           (line   12)
* PyConfig_Read (C 函式):                PyConfig.           (line   61)
* PyConfig_SetArgv (C 函式):             PyConfig.           (line   37)
* PyConfig_SetBytesArgv (C 函式):        PyConfig.           (line   44)
* PyConfig_SetBytesString (C 函式):      PyConfig.           (line   29)
* PyConfig_SetString (C 函式):           PyConfig.           (line   22)
* PyConfig_SetWideStringList (C 函式):   PyConfig.           (line   52)
* PyContext (C 型態):                    Context Variables Objects.
                                                             (line   24)
* PyContextToken (C 型態):               Context Variables Objects.
                                                             (line   34)
* PyContextToken_CheckExact (C 函式):    Context Variables Objects.
                                                             (line   62)
* PyContextToken_Type (C 變數):          Context Variables Objects.
                                                             (line   46)
* PyContextVar (C 型態):                 Context Variables Objects.
                                                             (line   29)
* PyContextVar_CheckExact (C 函式):      Context Variables Objects.
                                                             (line   57)
* PyContextVar_Get (C 函式):             Context Variables Objects.
                                                             (line  106)
* PyContextVar_New (C 函式):             Context Variables Objects.
                                                             (line   99)
* PyContextVar_Reset (C 函式):           Context Variables Objects.
                                                             (line  129)
* PyContextVar_Set (C 函式):             Context Variables Objects.
                                                             (line  124)
* PyContextVar_Type (C 變數):            Context Variables Objects.
                                                             (line   42)
* PyContext_CheckExact (C 函式):         Context Variables Objects.
                                                             (line   52)
* PyContext_ClearFreeList (C 函式):      Context Variables Objects.
                                                             (line   92)
* PyContext_Copy (C 函式):               Context Variables Objects.
                                                             (line   73)
* PyContext_CopyCurrent (C 函式):        Context Variables Objects.
                                                             (line   77)
* PyContext_Enter (C 函式):              Context Variables Objects.
                                                             (line   81)
* PyContext_Exit (C 函式):               Context Variables Objects.
                                                             (line   86)
* PyContext_New (C 函式):                Context Variables Objects.
                                                             (line   69)
* PyContext_Type (C 變數):               Context Variables Objects.
                                                             (line   38)
* PyCoroObject (C 型態):                 Coroutine Objects<2>.
                                                             (line   11)
* PyCoro_CheckExact (C 函式):            Coroutine Objects<2>.
                                                             (line   19)
* PyCoro_New (C 函式):                   Coroutine Objects<2>.
                                                             (line   24)
* PyCoro_Type (C 變數):                  Coroutine Objects<2>.
                                                             (line   15)
* PyDateTime_Check (C 函式):             DateTime 物件.      (line   35)
* PyDateTime_CheckExact (C 函式):        DateTime 物件.      (line   40)
* PyDateTime_DATE_GET_HOUR (C 函式):     DateTime 物件.      (line  156)
* PyDateTime_DATE_GET_MICROSECOND (C 函式): DateTime 物件.   (line  168)
* PyDateTime_DATE_GET_MINUTE (C 函式):   DateTime 物件.      (line  160)
* PyDateTime_DATE_GET_SECOND (C 函式):   DateTime 物件.      (line  164)
* PyDateTime_DELTA_GET_DAYS (C 函式):    DateTime 物件.      (line  196)
* PyDateTime_DELTA_GET_MICROSECONDS (C 函式): DateTime 物件. (line  208)
* PyDateTime_DELTA_GET_SECONDS (C 函式): DateTime 物件.      (line  202)
* PyDateTime_FromDateAndTime (C 函式):   DateTime 物件.      (line   81)
* PyDateTime_FromDateAndTimeAndFold (C 函式): DateTime 物件. (line   88)
* PyDateTime_FromTimestamp (C 函式):     DateTime 物件.      (line  216)
* PyDateTime_GET_DAY (C 函式):           DateTime 物件.      (line  148)
* PyDateTime_GET_MONTH (C 函式):         DateTime 物件.      (line  144)
* PyDateTime_GET_YEAR (C 函式):          DateTime 物件.      (line  140)
* PyDateTime_TimeZone_UTC (C 變數):      DateTime 物件.      (line   16)
* PyDateTime_TIME_GET_HOUR (C 函式):     DateTime 物件.      (line  176)
* PyDateTime_TIME_GET_MICROSECOND (C 函式): DateTime 物件.   (line  188)
* PyDateTime_TIME_GET_MINUTE (C 函式):   DateTime 物件.      (line  180)
* PyDateTime_TIME_GET_SECOND (C 函式):   DateTime 物件.      (line  184)
* PyDate_Check (C 函式):                 DateTime 物件.      (line   25)
* PyDate_CheckExact (C 函式):            DateTime 物件.      (line   30)
* PyDate_FromDate (C 函式):              DateTime 物件.      (line   77)
* PyDate_FromTimestamp (C 函式):         DateTime 物件.      (line  221)
* PyDelta_Check (C 函式):                DateTime 物件.      (line   55)
* PyDelta_CheckExact (C 函式):           DateTime 物件.      (line   60)
* PyDelta_FromDSU (C 函式):              DateTime 物件.      (line  110)
* PyDescr_IsData (C 函式):               修飾器物件.         (line   38)
* PyDescr_NewClassMethod (C 函式):       修飾器物件.         (line   33)
* PyDescr_NewGetSet (C 函式):            修飾器物件.         (line   13)
* PyDescr_NewMember (C 函式):            修飾器物件.         (line   18)
* PyDescr_NewMethod (C 函式):            修飾器物件.         (line   23)
* PyDescr_NewWrapper (C 函式):           修飾器物件.         (line   28)
* PyDictObject (C 型態):                 字典物件.           (line    6)
* PyDictProxy_New (C 函式):              字典物件.           (line   27)
* PyDict_Check (C 函式):                 字典物件.           (line   15)
* PyDict_CheckExact (C 函式):            字典物件.           (line   19)
* PyDict_Clear (C 函式):                 字典物件.           (line   33)
* PyDict_ClearFreeList (C 函式):         字典物件.           (line  215)
* PyDict_Contains (C 函式):              字典物件.           (line   37)
* PyDict_Copy (C 函式):                  字典物件.           (line   43)
* PyDict_DelItem (C 函式):               字典物件.           (line   64)
* PyDict_DelItemString (C 函式):         字典物件.           (line   71)
* PyDict_GetItem (C 函式):               字典物件.           (line   77)
* PyDict_GetItemString (C 函式):         字典物件.           (line   93)
* PyDict_GetItemWithError (C 函式):      字典物件.           (line   86)
* PyDict_Items (C 函式):                 字典物件.           (line  117)
* PyDict_Keys (C 函式):                  字典物件.           (line  121)
* PyDict_Merge (C 函式):                 字典物件.           (line  182)
* PyDict_MergeFromSeq2 (C 函式):         字典物件.           (line  200)
* PyDict_New (C 函式):                   字典物件.           (line   23)
* PyDict_Next (C 函式):                  字典物件.           (line  134)
* PyDict_SetDefault (C 函式):            字典物件.           (line  104)
* PyDict_SetItem (C 函式):               字典物件.           (line   47)
* PyDict_SetItemString (C 函式):         字典物件.           (line   55)
* PyDict_Size (C 函式):                  字典物件.           (line  129)
* PyDict_Type (C 變數):                  字典物件.           (line   10)
* PyDict_Update (C 函式):                字典物件.           (line  192)
* PyDict_Values (C 函式):                字典物件.           (line  125)
* PyDLL (ctypes 中的類別):               Loading shared libraries.
                                                             (line   61)
* pydoc (模組):                          pydoc --- Documentation generator and online help system.
                                                             (line    6)
* PyDoc_STR (C 巨集):                    Useful macros.      (line   99)
* PyDoc_STRVAR (C 巨集):                 Useful macros.      (line   81)
* PyErr_BadArgument (C 函式):            Raising exceptions. (line   44)
* PyErr_BadInternalCall (C 函式):        Raising exceptions. (line  190)
* PyErr_CheckSignals (C 函式):           Signal Handling<2>. (line    6)
* PyErr_Clear (C 函式):                  Printing and clearing.
                                                             (line    6)
* PyErr_Clear():                         Exceptions<16>.     (line   25)
* PyErr_Clear() <1>:                     Exceptions<16>.     (line  123)
* PyErr_ExceptionMatches (C 函式):       Querying the error indicator.
                                                             (line   20)
* PyErr_ExceptionMatches():              Exceptions<16>.     (line  123)
* PyErr_Fetch (C 函式):                  Querying the error indicator.
                                                             (line   35)
* PyErr_Fetch():                         Finalization and De-allocation.
                                                             (line   21)
* PyErr_Format (C 函式):                 Raising exceptions. (line   24)
* PyErr_FormatV (C 函式):                Raising exceptions. (line   32)
* PyErr_GetExcInfo (C 函式):             Querying the error indicator.
                                                             (line   96)
* PyErr_GivenExceptionMatches (C 函式):  Querying the error indicator.
                                                             (line   26)
* PyErr_NewException (C 函式):           Exception Classes.  (line    6)
* PyErr_NewExceptionWithDoc (C 函式):    Exception Classes.  (line   23)
* PyErr_NoMemory (C 函式):               Raising exceptions. (line   50)
* PyErr_NormalizeException (C 函式):     Querying the error indicator.
                                                             (line   77)
* PyErr_Occurred (C 函式):               Querying the error indicator.
                                                             (line    6)
* PyErr_Occurred():                      Exceptions<16>.     (line   12)
* PyErr_Print (C 函式):                  Printing and clearing.
                                                             (line   26)
* PyErr_PrintEx (C 函式):                Printing and clearing.
                                                             (line   11)
* PyErr_ResourceWarning (C 函式):        Issuing warnings.   (line   79)
* PyErr_Restore (C 函式):                Querying the error indicator.
                                                             (line   58)
* PyErr_Restore():                       Finalization and De-allocation.
                                                             (line   21)
* PyErr_SetExcFromWindowsErr (C 函式):   Raising exceptions. (line  110)
* PyErr_SetExcFromWindowsErrWithFilename (C 函式): Raising exceptions.
                                                             (line  148)
* PyErr_SetExcFromWindowsErrWithFilenameObject (C 函式): Raising exceptions.
                                                             (line  127)
* PyErr_SetExcFromWindowsErrWithFilenameObjects (C 函式): Raising exceptions.
                                                             (line  136)
* PyErr_SetExcInfo (C 函式):             Querying the error indicator.
                                                             (line  114)
* PyErr_SetFromErrno (C 函式):           Raising exceptions. (line   56)
* PyErr_SetFromErrnoWithFilename (C 函式): Raising exceptions.
                                                             (line   89)
* PyErr_SetFromErrnoWithFilenameObject (C 函式): Raising exceptions.
                                                             (line   71)
* PyErr_SetFromErrnoWithFilenameObjects (C 函式): Raising exceptions.
                                                             (line   79)
* PyErr_SetFromWindowsErr (C 函式):      Raising exceptions. (line   96)
* PyErr_SetFromWindowsErrWithFilename (C 函式): Raising exceptions.
                                                             (line  118)
* PyErr_SetImportError (C 函式):         Raising exceptions. (line  156)
* PyErr_SetImportErrorSubclass (C 函式): Issuing warnings.   (line   42)
* PyErr_SetInterrupt (C 函式):           Signal Handling<2>. (line   18)
* PyErr_SetNone (C 函式):                Raising exceptions. (line   40)
* PyErr_SetObject (C 函式):              Raising exceptions. (line   18)
* PyErr_SetString (C 函式):              Raising exceptions. (line   10)
* PyErr_SetString():                     Exceptions<16>.     (line   25)
* PyErr_SyntaxLocation (C 函式):         Raising exceptions. (line  185)
* PyErr_SyntaxLocationEx (C 函式):       Raising exceptions. (line  176)
* PyErr_SyntaxLocationObject (C 函式):   Raising exceptions. (line  166)
* PyErr_WarnEx (C 函式):                 Issuing warnings.   (line   19)
* PyErr_WarnExplicit (C 函式):           Issuing warnings.   (line   62)
* PyErr_WarnExplicitObject (C 函式):     Issuing warnings.   (line   50)
* PyErr_WarnFormat (C 函式):             Issuing warnings.   (line   70)
* PyErr_WriteUnraisable (C 函式):        Printing and clearing.
                                                             (line   30)
* PyEval_AcquireLock (C 函式):           Low-level API.      (line  133)
* PyEval_AcquireThread (C 函式):         Low-level API.      (line  100)
* PyEval_AcquireThread():                High-level API.     (line   29)
* PyEval_EvalCode (C 函式):              The Very High Level Layer.
                                                             (line  327)
* PyEval_EvalCodeEx (C 函式):            The Very High Level Layer.
                                                             (line  334)
* PyEval_EvalFrame (C 函式):             The Very High Level Layer.
                                                             (line  353)
* PyEval_EvalFrameEx (C 函式):           The Very High Level Layer.
                                                             (line  358)
* PyEval_GetBuiltins (C 函式):           Reflection.         (line    6)
* PyEval_GetFrame (C 函式):              Reflection.         (line   21)
* PyEval_GetFuncDesc (C 函式):           Reflection.         (line   34)
* PyEval_GetFuncName (C 函式):           Reflection.         (line   29)
* PyEval_GetGlobals (C 函式):            Reflection.         (line   16)
* PyEval_GetLocals (C 函式):             Reflection.         (line   11)
* PyEval_InitThreads (C 函式):           High-level API.     (line   27)
* PyEval_InitThreads():                  Initializing and finalizing the interpreter.
                                                             (line    8)
* PyEval_MergeCompilerFlags (C 函式):    The Very High Level Layer.
                                                             (line  371)
* PyEval_ReleaseLock (C 函式):           Low-level API.      (line  155)
* PyEval_ReleaseThread (C 函式):         Low-level API.      (line  122)
* PyEval_ReleaseThread():                High-level API.     (line   29)
* PyEval_RestoreThread (C 函式):         High-level API.     (line   61)
* PyEval_RestoreThread():                Releasing the GIL from extension code.
                                                             (line   33)
* PyEval_RestoreThread() <1>:            High-level API.     (line   29)
* PyEval_SaveThread (C 函式):            High-level API.     (line   54)
* PyEval_SaveThread():                   Releasing the GIL from extension code.
                                                             (line   33)
* PyEval_SaveThread() <1>:               High-level API.     (line   29)
* PyEval_SetProfile (C 函式):            Profiling and Tracing.
                                                             (line  116)
* PyEval_SetTrace (C 函式):              Profiling and Tracing.
                                                             (line  126)
* PyEval_ThreadsInitialized (C 函式):    High-level API.     (line   44)
* PyException_GetCause (C 函式):         Exception Objects.  (line   30)
* PyException_GetContext (C 函式):       Exception Objects.  (line   17)
* PyException_GetTraceback (C 函式):     Exception Objects.  (line    6)
* PyException_SetCause (C 函式):         Exception Objects.  (line   36)
* PyException_SetContext (C 函式):       Exception Objects.  (line   24)
* PyException_SetTraceback (C 函式):     Exception Objects.  (line   12)
* PyExc_ArithmeticError:                 Standard Exceptions.
                                                             (line   11)
* PyExc_AssertionError:                  Standard Exceptions.
                                                             (line   11)
* PyExc_AttributeError:                  Standard Exceptions.
                                                             (line   11)
* PyExc_BaseException:                   Standard Exceptions.
                                                             (line   11)
* PyExc_BlockingIOError:                 Standard Exceptions.
                                                             (line   11)
* PyExc_BrokenPipeError:                 Standard Exceptions.
                                                             (line   11)
* PyExc_BufferError:                     Standard Exceptions.
                                                             (line   11)
* PyExc_BytesWarning:                    Standard Warning Categories.
                                                             (line   11)
* PyExc_ChildProcessError:               Standard Exceptions.
                                                             (line   11)
* PyExc_ConnectionAbortedError:          Standard Exceptions.
                                                             (line   11)
* PyExc_ConnectionError:                 Standard Exceptions.
                                                             (line   11)
* PyExc_ConnectionRefusedError:          Standard Exceptions.
                                                             (line   11)
* PyExc_ConnectionResetError:            Standard Exceptions.
                                                             (line   11)
* PyExc_DeprecationWarning:              Standard Warning Categories.
                                                             (line   11)
* PyExc_EnvironmentError:                Standard Exceptions.
                                                             (line  189)
* PyExc_EOFError:                        Standard Exceptions.
                                                             (line   11)
* PyExc_Exception:                       Standard Exceptions.
                                                             (line   11)
* PyExc_FileExistsError:                 Standard Exceptions.
                                                             (line   11)
* PyExc_FileNotFoundError:               Standard Exceptions.
                                                             (line   11)
* PyExc_FloatingPointError:              Standard Exceptions.
                                                             (line   11)
* PyExc_FutureWarning:                   Standard Warning Categories.
                                                             (line   11)
* PyExc_GeneratorExit:                   Standard Exceptions.
                                                             (line   11)
* PyExc_ImportError:                     Standard Exceptions.
                                                             (line   11)
* PyExc_ImportWarning:                   Standard Warning Categories.
                                                             (line   11)
* PyExc_IndentationError:                Standard Exceptions.
                                                             (line   11)
* PyExc_IndexError:                      Standard Exceptions.
                                                             (line   11)
* PyExc_InterruptedError:                Standard Exceptions.
                                                             (line   11)
* PyExc_IOError:                         Standard Exceptions.
                                                             (line  189)
* PyExc_IsADirectoryError:               Standard Exceptions.
                                                             (line   11)
* PyExc_KeyboardInterrupt:               Standard Exceptions.
                                                             (line   11)
* PyExc_KeyError:                        Standard Exceptions.
                                                             (line   11)
* PyExc_LookupError:                     Standard Exceptions.
                                                             (line   11)
* PyExc_MemoryError:                     Standard Exceptions.
                                                             (line   11)
* PyExc_ModuleNotFoundError:             Standard Exceptions.
                                                             (line   11)
* PyExc_NameError:                       Standard Exceptions.
                                                             (line   11)
* PyExc_NotADirectoryError:              Standard Exceptions.
                                                             (line   11)
* PyExc_NotImplementedError:             Standard Exceptions.
                                                             (line   11)
* PyExc_OSError:                         Standard Exceptions.
                                                             (line   11)
* PyExc_OverflowError:                   Standard Exceptions.
                                                             (line   11)
* PyExc_PendingDeprecationWarning:       Standard Warning Categories.
                                                             (line   11)
* PyExc_PermissionError:                 Standard Exceptions.
                                                             (line   11)
* PyExc_ProcessLookupError:              Standard Exceptions.
                                                             (line   11)
* PyExc_RecursionError:                  Standard Exceptions.
                                                             (line   11)
* PyExc_ReferenceError:                  Standard Exceptions.
                                                             (line   11)
* PyExc_ResourceWarning:                 Standard Warning Categories.
                                                             (line   11)
* PyExc_RuntimeError:                    Standard Exceptions.
                                                             (line   11)
* PyExc_RuntimeWarning:                  Standard Warning Categories.
                                                             (line   11)
* PyExc_StopAsyncIteration:              Standard Exceptions.
                                                             (line   11)
* PyExc_StopIteration:                   Standard Exceptions.
                                                             (line   11)
* PyExc_SyntaxError:                     Standard Exceptions.
                                                             (line   11)
* PyExc_SyntaxWarning:                   Standard Warning Categories.
                                                             (line   11)
* PyExc_SystemError:                     Standard Exceptions.
                                                             (line   11)
* PyExc_SystemExit:                      Standard Exceptions.
                                                             (line   11)
* PyExc_TabError:                        Standard Exceptions.
                                                             (line   11)
* PyExc_TimeoutError:                    Standard Exceptions.
                                                             (line   11)
* PyExc_TypeError:                       Standard Exceptions.
                                                             (line   11)
* PyExc_UnboundLocalError:               Standard Exceptions.
                                                             (line   11)
* PyExc_UnicodeDecodeError:              Standard Exceptions.
                                                             (line   11)
* PyExc_UnicodeEncodeError:              Standard Exceptions.
                                                             (line   11)
* PyExc_UnicodeError:                    Standard Exceptions.
                                                             (line   11)
* PyExc_UnicodeTranslateError:           Standard Exceptions.
                                                             (line   11)
* PyExc_UnicodeWarning:                  Standard Warning Categories.
                                                             (line   11)
* PyExc_UserWarning:                     Standard Warning Categories.
                                                             (line   11)
* PyExc_ValueError:                      Standard Exceptions.
                                                             (line   11)
* PyExc_Warning:                         Standard Warning Categories.
                                                             (line   11)
* PyExc_WindowsError:                    Standard Exceptions.
                                                             (line  189)
* PyExc_ZeroDivisionError:               Standard Exceptions.
                                                             (line   11)
* PyFile_FromFd (C 函式):                檔案（File）物件.   (line   15)
* PyFile_GetLine (C 函式):               檔案（File）物件.   (line   41)
* PyFile_SetOpenCodeHook (C 函式):       檔案（File）物件.   (line   55)
* PyFile_WriteObject (C 函式):           檔案（File）物件.   (line   84)
* PyFile_WriteString (C 函式):           檔案（File）物件.   (line   92)
* PyFloatObject (C 型態):                浮點數（Floating Point）物件.
                                                             (line    6)
* PyFloat_AsDouble (C 函式):             浮點數（Floating Point）物件.
                                                             (line   35)
* PyFloat_AS_DOUBLE (C 函式):            浮點數（Floating Point）物件.
                                                             (line   47)
* PyFloat_Check (C 函式):                浮點數（Floating Point）物件.
                                                             (line   17)
* PyFloat_CheckExact (C 函式):           浮點數（Floating Point）物件.
                                                             (line   22)
* PyFloat_ClearFreeList (C 函式):        浮點數（Floating Point）物件.
                                                             (line   68)
* PyFloat_FromDouble (C 函式):           浮點數（Floating Point）物件.
                                                             (line   31)
* PyFloat_FromString (C 函式):           浮點數（Floating Point）物件.
                                                             (line   27)
* PyFloat_GetInfo (C 函式):              浮點數（Floating Point）物件.
                                                             (line   52)
* PyFloat_GetMax (C 函式):               浮點數（Floating Point）物件.
                                                             (line   58)
* PyFloat_GetMin (C 函式):               浮點數（Floating Point）物件.
                                                             (line   63)
* PyFloat_Type (C 變數):                 浮點數（Floating Point）物件.
                                                             (line   11)
* PyFrameObject (C 型態):                The Very High Level Layer.
                                                             (line  348)
* PyFrame_GetLineNumber (C 函式):        Reflection.         (line   25)
* PyFrozenSet_Check (C 函式):            Set Objects.        (line   50)
* PyFrozenSet_CheckExact (C 函式):       Set Objects.        (line   65)
* PyFrozenSet_New (C 函式):              Set Objects.        (line   78)
* PyFrozenSet_Type (C 變數):             Set Objects.        (line   36)
* PyFunctionObject (C 型態):             函式（Function）物件.
                                                             (line    8)
* PyFunction_Check (C 函式):             函式（Function）物件.
                                                             (line   18)
* PyFunction_GetAnnotations (C 函式):    函式（Function）物件.
                                                             (line   83)
* PyFunction_GetClosure (C 函式):        函式（Function）物件.
                                                             (line   71)
* PyFunction_GetCode (C 函式):           函式（Function）物件.
                                                             (line   44)
* PyFunction_GetDefaults (C 函式):       函式（Function）物件.
                                                             (line   58)
* PyFunction_GetGlobals (C 函式):        函式（Function）物件.
                                                             (line   48)
* PyFunction_GetModule (C 函式):         函式（Function）物件.
                                                             (line   52)
* PyFunction_New (C 函式):               函式（Function）物件.
                                                             (line   23)
* PyFunction_NewWithQualName (C 函式):   函式（Function）物件.
                                                             (line   33)
* PyFunction_SetAnnotations (C 函式):    函式（Function）物件.
                                                             (line   87)
* PyFunction_SetClosure (C 函式):        函式（Function）物件.
                                                             (line   76)
* PyFunction_SetDefaults (C 函式):       函式（Function）物件.
                                                             (line   63)
* PyFunction_Type (C 變數):              函式（Function）物件.
                                                             (line   12)
* PYFUNCTYPE() (於 ctypes 模組中):       Function prototypes.
                                                             (line   34)
* PyGenObject (C 型態):                  產生器物件.         (line   11)
* PyGen_Check (C 函式):                  產生器物件.         (line   19)
* PyGen_CheckExact (C 函式):             產生器物件.         (line   23)
* PyGen_New (C 函式):                    產生器物件.         (line   28)
* PyGen_NewWithQualName (C 函式):        產生器物件.         (line   33)
* PyGen_Type (C 變數):                   產生器物件.         (line   15)
* PyGetSetDef (C 型態):                  通用物件結構.       (line  358)
* PyGILState_Check (C 函式):             High-level API.     (line  140)
* PyGILState_Ensure (C 函式):            High-level API.     (line   90)
* PyGILState_GetThisThreadState (C 函式): High-level API.    (line  132)
* PyGILState_Release (C 函式):           High-level API.     (line  121)
* PyImport_AddModule (C 函式):           匯入模組<2>.        (line  109)
* PyImport_AddModuleObject (C 函式):     匯入模組<2>.        (line   93)
* PyImport_AppendInittab (C 函式):       匯入模組<2>.        (line  278)
* PyImport_Cleanup (C 函式):             匯入模組<2>.        (line  231)
* PyImport_ExecCodeModule (C 函式):      匯入模組<2>.        (line  114)
* PyImport_ExecCodeModuleEx (C 函式):    匯入模組<2>.        (line  150)
* PyImport_ExecCodeModuleObject (C 函式): 匯入模組<2>.       (line  160)
* PyImport_ExecCodeModuleWithPathnames (C 函式): 匯入模組<2>.
                                                             (line  171)
* PyImport_ExtendInittab (C 函式):       匯入模組<2>.        (line  304)
* PyImport_FrozenModules (C 變數):       匯入模組<2>.        (line  270)
* PyImport_GetImporter (C 函式):         匯入模組<2>.        (line  216)
* PyImport_GetMagicNumber (C 函式):      匯入模組<2>.        (line  185)
* PyImport_GetMagicTag (C 函式):         匯入模組<2>.        (line  194)
* PyImport_GetModule (C 函式):           匯入模組<2>.        (line  208)
* PyImport_GetModuleDict (C 函式):       匯入模組<2>.        (line  203)
* PyImport_Import (C 函式):              匯入模組<2>.        (line   78)
* PyImport_ImportFrozenModule (C 函式):  匯入模組<2>.        (line  252)
* PyImport_ImportFrozenModuleObject (C 函式): 匯入模組<2>.   (line  239)
* PyImport_ImportModule (C 函式):        匯入模組<2>.        (line    6)
* PyImport_ImportModuleEx (C 函式):      匯入模組<2>.        (line   34)
* PyImport_ImportModuleLevel (C 函式):   匯入模組<2>.        (line   68)
* PyImport_ImportModuleLevelObject (C 函式): 匯入模組<2>.    (line   51)
* PyImport_ImportModuleNoBlock (C 函式): 匯入模組<2>.        (line   25)
* PyImport_ReloadModule (C 函式):        匯入模組<2>.        (line   88)
* PyIndex_Check (C 函式):                Number Protocol.    (line  258)
* PyInit_modulename (C 函式):            Building C and C++ Extensions.
                                                             (line   16)
* PyInstanceMethod_Check (C 函式):       實體方法物件.       (line   15)
* PyInstanceMethod_Function (C 函式):    實體方法物件.       (line   25)
* PyInstanceMethod_GET_FUNCTION (C 函式): 實體方法物件.      (line   29)
* PyInstanceMethod_New (C 函式):         實體方法物件.       (line   20)
* PyInstanceMethod_Type (C 變數):        實體方法物件.       (line   10)
* PyInterpreterState (C 型態):           High-level API.     (line    9)
* PyInterpreterState_Clear (C 函式):     Low-level API.      (line   21)
* PyInterpreterState_Delete (C 函式):    Low-level API.      (line   29)
* PyInterpreterState_GetDict (C 函式):   Low-level API.      (line   61)
* PyInterpreterState_GetID (C 函式):     Low-level API.      (line   53)
* PyInterpreterState_Head (C 函式):      Advanced Debugger Support.
                                                             (line    9)
* PyInterpreterState_Main (C 函式):      Advanced Debugger Support.
                                                             (line   14)
* PyInterpreterState_New (C 函式):       Low-level API.      (line   12)
* PyInterpreterState_Next (C 函式):      Advanced Debugger Support.
                                                             (line   18)
* PyInterpreterState_ThreadHead (C 函式): Advanced Debugger Support.
                                                             (line   25)
* PyIter_Check (C 函式):                 Iterator Protocol.  (line    8)
* PyIter_Next (C 函式):                  Iterator Protocol.  (line   12)
* PyListObject (C 型態):                 List（串列）物件.   (line    6)
* PyList_Append (C 函式):                List（串列）物件.   (line   90)
* PyList_AsTuple (C 函式):               List（串列）物件.   (line  125)
* PyList_Check (C 函式):                 List（串列）物件.   (line   17)
* PyList_CheckExact (C 函式):            List（串列）物件.   (line   22)
* PyList_ClearFreeList (C 函式):         List（串列）物件.   (line  131)
* PyList_GetItem (C 函式):               List（串列）物件.   (line   46)
* PyList_GetItem():                      Reference Count Details.
                                                             (line  117)
* PyList_GetSlice (C 函式):              List（串列）物件.   (line   96)
* PyList_GET_ITEM (C 函式):              List（串列）物件.   (line   53)
* PyList_GET_SIZE (C 函式):              List（串列）物件.   (line   42)
* PyList_Insert (C 函式):                List（串列）物件.   (line   82)
* PyList_New (C 函式):                   List（串列）物件.   (line   27)
* PyList_Reverse (C 函式):               List（串列）物件.   (line  120)
* PyList_SetItem (C 函式):               List（串列）物件.   (line   57)
* PyList_SetItem():                      Reference Count Details.
                                                             (line   26)
* PyList_SetSlice (C 函式):              List（串列）物件.   (line  105)
* PyList_SET_ITEM (C 函式):              List（串列）物件.   (line   69)
* PyList_Size (C 函式):                  List（串列）物件.   (line   37)
* PyList_Sort (C 函式):                  List（串列）物件.   (line  115)
* PyList_Type (C 變數):                  List（串列）物件.   (line   11)
* PyLongObject (C 型態):                 整數物件.           (line   13)
* PyLong_AsDouble (C 函式):              整數物件.           (line  261)
* PyLong_AsLong (C 函式):                整數物件.           (line  103)
* PyLong_AsLongAndOverflow (C 函式):     整數物件.           (line  120)
* PyLong_AsLongLong (C 函式):            整數物件.           (line  139)
* PyLong_AsLongLongAndOverflow (C 函式): 整數物件.           (line  156)
* PyLong_AsSize_t (C 函式):              整數物件.           (line  200)
* PyLong_AsSsize_t (C 函式):             整數物件.           (line  178)
* PyLong_AsUnsignedLong (C 函式):        整數物件.           (line  189)
* PyLong_AsUnsignedLongLong (C 函式):    整數物件.           (line  211)
* PyLong_AsUnsignedLongLongMask (C 函式): 整數物件.          (line  243)
* PyLong_AsUnsignedLongMask (C 函式):    整數物件.           (line  226)
* PyLong_AsVoidPtr (C 函式):             整數物件.           (line  272)
* PyLong_Check (C 函式):                 整數物件.           (line   24)
* PyLong_CheckExact (C 函式):            整數物件.           (line   29)
* PyLong_FromDouble (C 函式):            整數物件.           (line   64)
* PyLong_FromLong (C 函式):              整數物件.           (line   34)
* PyLong_FromLongLong (C 函式):          整數物件.           (line   56)
* PyLong_FromSize_t (C 函式):            整數物件.           (line   52)
* PyLong_FromSsize_t (C 函式):           整數物件.           (line   48)
* PyLong_FromString (C 函式):            整數物件.           (line   68)
* PyLong_FromUnicode (C 函式):           整數物件.           (line   83)
* PyLong_FromUnicodeObject (C 函式):     整數物件.           (line   92)
* PyLong_FromUnsignedLong (C 函式):      整數物件.           (line   44)
* PyLong_FromUnsignedLongLong (C 函式):  整數物件.           (line   60)
* PyLong_FromVoidPtr (C 函式):           整數物件.           (line   98)
* PyLong_Type (C 變數):                  整數物件.           (line   18)
* PyMappingMethods (C 型態):             Mapping Object Structures.
                                                             (line    6)
* PyMappingMethods.mp_ass_subscript (C 成員函數): Mapping Object Structures.
                                                             (line   25)
* PyMappingMethods.mp_length (C 成員函數): Mapping Object Structures.
                                                             (line   11)
* PyMappingMethods.mp_subscript (C 成員函數): Mapping Object Structures.
                                                             (line   17)
* PyMapping_Check (C 函式):              Mapping Protocol.   (line    9)
* PyMapping_DelItem (C 函式):            Mapping Protocol.   (line   39)
* PyMapping_DelItemString (C 函式):      Mapping Protocol.   (line   45)
* PyMapping_GetItemString (C 函式):      Mapping Protocol.   (line   23)
* PyMapping_HasKey (C 函式):             Mapping Protocol.   (line   51)
* PyMapping_HasKeyString (C 函式):       Mapping Protocol.   (line   61)
* PyMapping_Items (C 函式):              Mapping Protocol.   (line   84)
* PyMapping_Keys (C 函式):               Mapping Protocol.   (line   72)
* PyMapping_Length (C 函式):             Mapping Protocol.   (line   17)
* PyMapping_SetItemString (C 函式):      Mapping Protocol.   (line   30)
* PyMapping_Size (C 函式):               Mapping Protocol.   (line   17)
* PyMapping_Values (C 函式):             Mapping Protocol.   (line   78)
* PyMarshal_ReadLastObjectFromFile (C 函式): Data marshalling support.
                                                             (line   68)
* PyMarshal_ReadLongFromFile (C 函式):   Data marshalling support.
                                                             (line   42)
* PyMarshal_ReadObjectFromFile (C 函式): Data marshalling support.
                                                             (line   60)
* PyMarshal_ReadObjectFromString (C 函式): Data marshalling support.
                                                             (line   83)
* PyMarshal_ReadShortFromFile (C 函式):  Data marshalling support.
                                                             (line   51)
* PyMarshal_WriteLongToFile (C 函式):    Data marshalling support.
                                                             (line   20)
* PyMarshal_WriteObjectToFile (C 函式):  Data marshalling support.
                                                             (line   27)
* PyMarshal_WriteObjectToString (C 函式): Data marshalling support.
                                                             (line   33)
* PyMemAllocatorDomain (C 型態):         Customize Memory Allocators.
                                                             (line   36)
* PyMemAllocatorEx (C 型態):             Customize Memory Allocators.
                                                             (line    8)
* PyMemberDef (C 型態):                  通用物件結構.       (line  255)
* PyMemoryView_Check (C 函式):           MemoryView objects. (line   39)
* PyMemoryView_FromBuffer (C 函式):      MemoryView objects. (line   25)
* PyMemoryView_FromMemory (C 函式):      MemoryView objects. (line   17)
* PyMemoryView_FromObject (C 函式):      MemoryView objects. (line   10)
* PyMemoryView_GetContiguous (C 函式):   MemoryView objects. (line   30)
* PyMemoryView_GET_BASE (C 函式):        MemoryView objects. (line   51)
* PyMemoryView_GET_BUFFER (C 函式):      MemoryView objects. (line   44)
* PyMem_Calloc (C 函式):                 Memory Interface.   (line   27)
* PyMem_Del (C 函式):                    Memory Interface.   (line   85)
* PYMEM_DOMAIN_MEM (C 巨集):             Customize Memory Allocators.
                                                             (line   52)
* PYMEM_DOMAIN_OBJ (C 巨集):             Customize Memory Allocators.
                                                             (line   64)
* PYMEM_DOMAIN_RAW (C 巨集):             Customize Memory Allocators.
                                                             (line   40)
* PyMem_Free (C 函式):                   Memory Interface.   (line   56)
* PyMem_GetAllocator (C 函式):           Customize Memory Allocators.
                                                             (line   76)
* PyMem_Malloc (C 函式):                 Memory Interface.   (line   18)
* PyMem_New (C 函式):                    Memory Interface.   (line   69)
* PyMem_RawCalloc (C 函式):              Raw Memory Interface.
                                                             (line   24)
* PyMem_RawFree (C 函式):                Raw Memory Interface.
                                                             (line   53)
* PyMem_RawMalloc (C 函式):              Raw Memory Interface.
                                                             (line   15)
* PyMem_RawRealloc (C 函式):             Raw Memory Interface.
                                                             (line   36)
* PyMem_Realloc (C 函式):                Memory Interface.   (line   39)
* PyMem_Resize (C 函式):                 Memory Interface.   (line   75)
* PyMem_SetAllocator (C 函式):           Customize Memory Allocators.
                                                             (line   82)
* PyMem_SetupDebugHooks (C 函式):        Customize Memory Allocators.
                                                             (line   99)
* PyMethodDef (C 型態):                  通用物件結構.       (line  119)
* PyMethod_Check (C 函式):               Method Objects<2>.  (line   16)
* PyMethod_ClearFreeList (C 函式):       Method Objects<2>.  (line   43)
* PyMethod_Function (C 函式):            Method Objects<2>.  (line   27)
* PyMethod_GET_FUNCTION (C 函式):        Method Objects<2>.  (line   31)
* PyMethod_GET_SELF (C 函式):            Method Objects<2>.  (line   39)
* PyMethod_New (C 函式):                 Method Objects<2>.  (line   21)
* PyMethod_Self (C 函式):                Method Objects<2>.  (line   35)
* PyMethod_Type (C 變數):                Method Objects<2>.  (line   10)
* PyModuleDef (C 型態):                  Initializing C modules.
                                                             (line   17)
* PyModuleDef.m_base (C 成員函數):       Initializing C modules.
                                                             (line   23)
* PyModuleDef.m_clear (C 成員函數):      Initializing C modules.
                                                             (line   82)
* PyModuleDef.m_doc (C 成員函數):        Initializing C modules.
                                                             (line   31)
* PyModuleDef.m_free (C 成員函數):       Initializing C modules.
                                                             (line   90)
* PyModuleDef.m_methods (C 成員函數):    Initializing C modules.
                                                             (line   57)
* PyModuleDef.m_name (C 成員函數):       Initializing C modules.
                                                             (line   27)
* PyModuleDef.m_reload (C 成員函數):     Initializing C modules.
                                                             (line   72)
* PyModuleDef.m_size (C 成員函數):       Initializing C modules.
                                                             (line   36)
* PyModuleDef.m_slots (C 成員函數):      Initializing C modules.
                                                             (line   63)
* PyModuleDef.m_traverse (C 成員函數):   Initializing C modules.
                                                             (line   74)
* PyModuleDef_Init (C 函式):             Multi-phase initialization.
                                                             (line   33)
* PyModuleDef_Slot (C 型態):             Multi-phase initialization.
                                                             (line   45)
* PyModuleDef_Slot.slot (C 成員函數):    Multi-phase initialization.
                                                             (line   47)
* PyModuleDef_Slot.value (C 成員函數):   Multi-phase initialization.
                                                             (line   51)
* PyModule_AddFunctions (C 函式):        Low-level module creation functions.
                                                             (line   52)
* PyModule_AddIntConstant (C 函式):      Support functions.  (line   35)
* PyModule_AddIntMacro (C 函式):         Support functions.  (line   51)
* PyModule_AddObject (C 函式):           Support functions.  (line   11)
* PyModule_AddStringConstant (C 函式):   Support functions.  (line   42)
* PyModule_AddStringMacro (C 函式):      Support functions.  (line   58)
* PyModule_Check (C 函式):               模組物件模組.       (line   12)
* PyModule_CheckExact (C 函式):          模組物件模組.       (line   17)
* PyModule_Create (C 函式):              Single-phase initialization.
                                                             (line   10)
* PyModule_Create2 (C 函式):             Single-phase initialization.
                                                             (line   16)
* PyModule_ExecDef (C 函式):             Low-level module creation functions.
                                                             (line   36)
* PyModule_FromDefAndSpec (C 函式):      Low-level module creation functions.
                                                             (line   11)
* PyModule_FromDefAndSpec2 (C 函式):     Low-level module creation functions.
                                                             (line   21)
* PyModule_GetDef (C 函式):              模組物件模組.       (line   74)
* PyModule_GetDict (C 函式):             模組物件模組.       (line   41)
* PyModule_GetFilename (C 函式):         模組物件模組.       (line   90)
* PyModule_GetFilenameObject (C 函式):   模組物件模組.       (line   80)
* PyModule_GetName (C 函式):             模組物件模組.       (line   63)
* PyModule_GetNameObject (C 函式):       模組物件模組.       (line   54)
* PyModule_GetState (C 函式):            模組物件模組.       (line   68)
* PyModule_New (C 函式):                 模組物件模組.       (line   36)
* PyModule_NewObject (C 函式):           模組物件模組.       (line   22)
* PyModule_SetDocString (C 函式):        Low-level module creation functions.
                                                             (line   43)
* PyModule_Type (C 變數):                模組物件模組.       (line    6)
* PyNumberMethods (C 型態):              Number Object Structures.
                                                             (line    6)
* PyNumberMethods.nb_absolute (C 成員函數): Number Object Structures.
                                                             (line   85)
* PyNumberMethods.nb_add (C 成員函數):   Number Object Structures.
                                                             (line   69)
* PyNumberMethods.nb_and (C 成員函數):   Number Object Structures.
                                                             (line   95)
* PyNumberMethods.nb_bool (C 成員函數):  Number Object Structures.
                                                             (line   87)
* PyNumberMethods.nb_divmod (C 成員函數): Number Object Structures.
                                                             (line   77)
* PyNumberMethods.nb_float (C 成員函數): Number Object Structures.
                                                             (line  105)
* PyNumberMethods.nb_floor_divide (C 成員函數): Number Object Structures.
                                                             (line  127)
* PyNumberMethods.nb_index (C 成員函數): Number Object Structures.
                                                             (line  135)
* PyNumberMethods.nb_inplace_add (C 成員函數): Number Object Structures.
                                                             (line  107)
* PyNumberMethods.nb_inplace_and (C 成員函數): Number Object Structures.
                                                             (line  121)
* PyNumberMethods.nb_inplace_floor_divide (C 成員函數): Number Object Structures.
                                                             (line  131)
* PyNumberMethods.nb_inplace_lshift (C 成員函數): Number Object Structures.
                                                             (line  117)
* PyNumberMethods.nb_inplace_matrix_multiply (C 成員函數): Number Object Structures.
                                                             (line  139)
* PyNumberMethods.nb_inplace_multiply (C 成員函數): Number Object Structures.
                                                             (line  111)
* PyNumberMethods.nb_inplace_or (C 成員函數): Number Object Structures.
                                                             (line  125)
* PyNumberMethods.nb_inplace_power (C 成員函數): Number Object Structures.
                                                             (line  115)
* PyNumberMethods.nb_inplace_remainder (C 成員函數): Number Object Structures.
                                                             (line  113)
* PyNumberMethods.nb_inplace_rshift (C 成員函數): Number Object Structures.
                                                             (line  119)
* PyNumberMethods.nb_inplace_subtract (C 成員函數): Number Object Structures.
                                                             (line  109)
* PyNumberMethods.nb_inplace_true_divide (C 成員函數): Number Object Structures.
                                                             (line  133)
* PyNumberMethods.nb_inplace_xor (C 成員函數): Number Object Structures.
                                                             (line  123)
* PyNumberMethods.nb_int (C 成員函數):   Number Object Structures.
                                                             (line  101)
* PyNumberMethods.nb_invert (C 成員函數): Number Object Structures.
                                                             (line   89)
* PyNumberMethods.nb_lshift (C 成員函數): Number Object Structures.
                                                             (line   91)
* PyNumberMethods.nb_matrix_multiply (C 成員函數): Number Object Structures.
                                                             (line  137)
* PyNumberMethods.nb_multiply (C 成員函數): Number Object Structures.
                                                             (line   73)
* PyNumberMethods.nb_negative (C 成員函數): Number Object Structures.
                                                             (line   81)
* PyNumberMethods.nb_or (C 成員函數):    Number Object Structures.
                                                             (line   99)
* PyNumberMethods.nb_positive (C 成員函數): Number Object Structures.
                                                             (line   83)
* PyNumberMethods.nb_power (C 成員函數): Number Object Structures.
                                                             (line   79)
* PyNumberMethods.nb_remainder (C 成員函數): Number Object Structures.
                                                             (line   75)
* PyNumberMethods.nb_reserved (C 成員函數): Number Object Structures.
                                                             (line  103)
* PyNumberMethods.nb_rshift (C 成員函數): Number Object Structures.
                                                             (line   93)
* PyNumberMethods.nb_subtract (C 成員函數): Number Object Structures.
                                                             (line   71)
* PyNumberMethods.nb_true_divide (C 成員函數): Number Object Structures.
                                                             (line  129)
* PyNumberMethods.nb_xor (C 成員函數):   Number Object Structures.
                                                             (line   97)
* PyNumber_Absolute (C 函式):            Number Protocol.    (line   81)
* PyNumber_Add (C 函式):                 Number Protocol.    (line   13)
* PyNumber_And (C 函式):                 Number Protocol.    (line  102)
* PyNumber_AsSsize_t (C 函式):           Number Protocol.    (line  244)
* PyNumber_Check (C 函式):               Number Protocol.    (line    6)
* PyNumber_Divmod (C 函式):              Number Protocol.    (line   54)
* PyNumber_Float (C 函式):               Number Protocol.    (line  224)
* PyNumber_FloorDivide (C 函式):         Number Protocol.    (line   36)
* PyNumber_Index (C 函式):               Number Protocol.    (line  231)
* PyNumber_InPlaceAdd (C 函式):          Number Protocol.    (line  117)
* PyNumber_InPlaceAnd (C 函式):          Number Protocol.    (line  199)
* PyNumber_InPlaceFloorDivide (C 函式):  Number Protocol.    (line  147)
* PyNumber_InPlaceLshift (C 函式):       Number Protocol.    (line  185)
* PyNumber_InPlaceMatrixMultiply (C 函式): Number Protocol.  (line  137)
* PyNumber_InPlaceMultiply (C 函式):     Number Protocol.    (line  130)
* PyNumber_InPlaceOr (C 函式):           Number Protocol.    (line  211)
* PyNumber_InPlacePower (C 函式):        Number Protocol.    (line  173)
* PyNumber_InPlaceRemainder (C 函式):    Number Protocol.    (line  166)
* PyNumber_InPlaceRshift (C 函式):       Number Protocol.    (line  192)
* PyNumber_InPlaceSubtract (C 函式):     Number Protocol.    (line  123)
* PyNumber_InPlaceTrueDivide (C 函式):   Number Protocol.    (line  155)
* PyNumber_InPlaceXor (C 函式):          Number Protocol.    (line  205)
* PyNumber_Invert (C 函式):              Number Protocol.    (line   87)
* PyNumber_Long (C 函式):                Number Protocol.    (line  217)
* PyNumber_Lshift (C 函式):              Number Protocol.    (line   92)
* PyNumber_MatrixMultiply (C 函式):      Number Protocol.    (line   28)
* PyNumber_Multiply (C 函式):            Number Protocol.    (line   23)
* PyNumber_Negative (C 函式):            Number Protocol.    (line   72)
* PyNumber_Or (C 函式):                  Number Protocol.    (line  112)
* PyNumber_Positive (C 函式):            Number Protocol.    (line   77)
* PyNumber_Power (C 函式):               Number Protocol.    (line   61)
* PyNumber_Remainder (C 函式):           Number Protocol.    (line   49)
* PyNumber_Rshift (C 函式):              Number Protocol.    (line   97)
* PyNumber_Subtract (C 函式):            Number Protocol.    (line   18)
* PyNumber_ToBase (C 函式):              Number Protocol.    (line  236)
* PyNumber_TrueDivide (C 函式):          Number Protocol.    (line   41)
* PyNumber_Xor (C 函式):                 Number Protocol.    (line  107)
* PyObject (C 型態):                     通用物件結構.       (line   17)
* PyObject.ob_refcnt (C 成員函數):       PyObject Slots.     (line   30)
* PyObject.ob_type (C 成員函數):         PyObject Slots.     (line   43)
* PyObject._ob_next (C 成員函數):        PyObject Slots.     (line   13)
* PyObject._ob_prev (C 成員函數):        PyObject Slots.     (line   13)
* PyObjectArenaAllocator (C 型態):       Customize pymalloc Arena Allocator.
                                                             (line    8)
* PyObject_AsCharBuffer (C 函式):        Old Buffer Protocol.
                                                             (line   21)
* PyObject_ASCII (C 函式):               Object Protocol.    (line  177)
* PyObject_AsFileDescriptor (C 函式):    檔案（File）物件.   (line   33)
* PyObject_AsReadBuffer (C 函式):        Old Buffer Protocol.
                                                             (line   31)
* PyObject_AsWriteBuffer (C 函式):       Old Buffer Protocol.
                                                             (line   50)
* PyObject_Bytes (C 函式):               Object Protocol.    (line  197)
* PyObject_Call (C 函式):                Object Protocol.    (line  253)
* PyObject_CallFunction (C 函式):        Object Protocol.    (line  279)
* PyObject_CallFunctionObjArgs (C 函式): Object Protocol.    (line  320)
* PyObject_CallMethod (C 函式):          Object Protocol.    (line  298)
* PyObject_CallMethodObjArgs (C 函式):   Object Protocol.    (line  333)
* PyObject_CallObject (C 函式):          Object Protocol.    (line  268)
* PyObject_CallObject():                 Calling Python Functions from C.
                                                             (line   64)
* PyObject_Calloc (C 函式):              Object allocators.  (line   24)
* PyObject_CheckBuffer (C 函式):         Buffer-related functions.
                                                             (line    6)
* PyObject_CheckReadBuffer (C 函式):     Old Buffer Protocol.
                                                             (line   40)
* PyObject_Del (C 函式):                 Allocating Objects on the Heap.
                                                             (line   49)
* PyObject_DelAttr (C 函式):             Object Protocol.    (line  109)
* PyObject_DelAttrString (C 函式):       Object Protocol.    (line  115)
* PyObject_DelItem (C 函式):             Object Protocol.    (line  497)
* PyObject_Dir (C 函式):                 Object Protocol.    (line  503)
* PyObject_Free (C 函式):                Object allocators.  (line   53)
* PyObject_GC_Del (C 函式):              Supporting Cyclic Garbage Collection.
                                                             (line   70)
* PyObject_GC_New (C 函式):              Supporting Cyclic Garbage Collection.
                                                             (line   34)
* PyObject_GC_NewVar (C 函式):           Supporting Cyclic Garbage Collection.
                                                             (line   39)
* PyObject_GC_Resize (C 函式):           Supporting Cyclic Garbage Collection.
                                                             (line   46)
* PyObject_GC_Track (C 函式):            Supporting Cyclic Garbage Collection.
                                                             (line   53)
* PyObject_GC_UnTrack (C 函式):          Supporting Cyclic Garbage Collection.
                                                             (line   75)
* PyObject_GenericGetAttr (C 函式):      Object Protocol.    (line   62)
* PyObject_GenericGetDict (C 函式):      Object Protocol.    (line  122)
* PyObject_GenericSetAttr (C 函式):      Object Protocol.    (line   96)
* PyObject_GenericSetDict (C 函式):      Object Protocol.    (line  130)
* PyObject_GetArenaAllocator (C 函式):   Customize pymalloc Arena Allocator.
                                                             (line   26)
* PyObject_GetAttr (C 函式):             Object Protocol.    (line   48)
* PyObject_GetAttrString (C 函式):       Object Protocol.    (line   55)
* PyObject_GetBuffer (C 函式):           Buffer-related functions.
                                                             (line   13)
* PyObject_GetItem (C 函式):             Object Protocol.    (line  484)
* PyObject_GetIter (C 函式):             Object Protocol.    (line  512)
* PyObject_HasAttr (C 函式):             Object Protocol.    (line   25)
* PyObject_HasAttrString (C 函式):       Object Protocol.    (line   36)
* PyObject_Hash (C 函式):                Object Protocol.    (line  420)
* PyObject_HashNotImplemented (C 函式):  Object Protocol.    (line  429)
* PyObject_HEAD (C 巨集):                通用物件結構.       (line   37)
* PyObject_HEAD_INIT (C 巨集):           通用物件結構.       (line   78)
* PyObject_Init (C 函式):                Allocating Objects on the Heap.
                                                             (line   14)
* PyObject_InitVar (C 函式):             Allocating Objects on the Heap.
                                                             (line   22)
* PyObject_IsInstance (C 函式):          Object Protocol.    (line  226)
* PyObject_IsSubclass (C 函式):          Object Protocol.    (line  206)
* PyObject_IsTrue (C 函式):              Object Protocol.    (line  436)
* PyObject_Length (C 函式):              Object Protocol.    (line  465)
* PyObject_LengthHint (C 函式):          Object Protocol.    (line  473)
* PyObject_Malloc (C 函式):              Object allocators.  (line   15)
* PyObject_New (C 函式):                 Allocating Objects on the Heap.
                                                             (line   29)
* PyObject_NewVar (C 函式):              Allocating Objects on the Heap.
                                                             (line   37)
* PyObject_Not (C 函式):                 Object Protocol.    (line  442)
* PyObject_Print (C 函式):               Object Protocol.    (line   17)
* PyObject_Realloc (C 函式):             Object allocators.  (line   36)
* PyObject_Repr (C 函式):                Object Protocol.    (line  166)
* PyObject_RichCompare (C 函式):         Object Protocol.    (line  139)
* PyObject_RichCompareBool (C 函式):     Object Protocol.    (line  150)
* PyObject_SetArenaAllocator (C 函式):   Customize pymalloc Arena Allocator.
                                                             (line   31)
* PyObject_SetAttr (C 函式):             Object Protocol.    (line   73)
* PyObject_SetAttrString (C 函式):       Object Protocol.    (line   85)
* PyObject_SetItem (C 函式):             Object Protocol.    (line  489)
* PyObject_Size (C 函式):                Object Protocol.    (line  465)
* PyObject_Str (C 函式):                 Object Protocol.    (line  187)
* PyObject_Type (C 函式):                Object Protocol.    (line  448)
* PyObject_TypeCheck (C 函式):           Object Protocol.    (line  460)
* PyObject_VAR_HEAD (C 巨集):            通用物件結構.       (line   47)
* PyOS_AfterFork (C 函式):               作業系統工具.       (line   75)
* PyOS_AfterFork_Child (C 函式):         作業系統工具.       (line   53)
* PyOS_AfterFork_Parent (C 函式):        作業系統工具.       (line   39)
* PyOS_BeforeFork (C 函式):              作業系統工具.       (line   26)
* PyOS_CheckStack (C 函式):              作業系統工具.       (line   85)
* PyOS_double_to_string (C 函式):        字串轉換與格式化.   (line   87)
* PyOS_FSPath (C 函式):                  作業系統工具.       (line    6)
* PyOS_getsig (C 函式):                  作業系統工具.       (line   93)
* PyOS_InputHook (C 變數):               The Very High Level Layer.
                                                             (line  161)
* PyOS_ReadlineFunctionPointer (C 變數): The Very High Level Layer.
                                                             (line  171)
* PyOS_setsig (C 函式):                  作業系統工具.       (line  100)
* PyOS_snprintf (C 函式):                字串轉換與格式化.   (line    8)
* PyOS_stricmp (C 函式):                 字串轉換與格式化.   (line  123)
* PyOS_string_to_double (C 函式):        字串轉換與格式化.   (line   53)
* PyOS_strnicmp (C 函式):                字串轉換與格式化.   (line  128)
* PyOS_vsnprintf (C 函式):               字串轉換與格式化.   (line   15)
* PyParser_SimpleParseFile (C 函式):     The Very High Level Layer.
                                                             (line  217)
* PyParser_SimpleParseFileFlags (C 函式): The Very High Level Layer.
                                                             (line  225)
* PyParser_SimpleParseString (C 函式):   The Very High Level Layer.
                                                             (line  192)
* PyParser_SimpleParseStringFlags (C 函式): The Very High Level Layer.
                                                             (line  200)
* PyParser_SimpleParseStringFlagsFilename (C 函式): The Very High Level Layer.
                                                             (line  207)
* PyPI; (see Python Package Index (PyPI)): Installing the tools.
                                                             (line   25)
* PyPreConfig (C 型態):                  PyPreConfig.        (line    6)
* PyPreConfig.allocator (C 成員函數):    PyPreConfig.        (line   32)
* PyPreConfig.coerce_c_locale (C 成員函數): PyPreConfig.     (line   68)
* PyPreConfig.coerce_c_locale_warn (C 成員函數): PyPreConfig.
                                                             (line   73)
* PyPreConfig.configure_locale (C 成員函數): PyPreConfig.    (line   62)
* PyPreConfig.dev_mode (C 成員函數):     PyPreConfig.        (line   77)
* PyPreConfig.isolated (C 成員函數):     PyPreConfig.        (line   81)
* PyPreConfig.legacy_windows_fs_encoding (C 成員函數): PyPreConfig.
                                                             (line   85)
* PyPreConfig.parse_argv (C 成員函數):   PyPreConfig.        (line   94)
* PyPreConfig.use_environment (C 成員函數): PyPreConfig.     (line  101)
* PyPreConfig.utf8_mode (C 成員函數):    PyPreConfig.        (line  105)
* PyPreConfig_InitIsolatedConfig (C 函式): PyPreConfig.      (line   24)
* PyPreConfig_InitPythonConfig (C 函式): PyPreConfig.        (line   18)
* PyProperty_Type (C 變數):              修飾器物件.         (line    9)
* PyRun_AnyFile (C 函式):                The Very High Level Layer.
                                                             (line   48)
* PyRun_AnyFileEx (C 函式):              The Very High Level Layer.
                                                             (line   61)
* PyRun_AnyFileExFlags (C 函式):         The Very High Level Layer.
                                                             (line   67)
* PyRun_AnyFileFlags (C 函式):           The Very High Level Layer.
                                                             (line   54)
* PyRun_File (C 函式):                   The Very High Level Layer.
                                                             (line  252)
* PyRun_FileEx (C 函式):                 The Very High Level Layer.
                                                             (line  258)
* PyRun_FileExFlags (C 函式):            The Very High Level Layer.
                                                             (line  273)
* PyRun_FileFlags (C 函式):              The Very High Level Layer.
                                                             (line  264)
* PyRun_InteractiveLoop (C 函式):        The Very High Level Layer.
                                                             (line  146)
* PyRun_InteractiveLoopFlags (C 函式):   The Very High Level Layer.
                                                             (line  152)
* PyRun_InteractiveOne (C 函式):         The Very High Level Layer.
                                                             (line  125)
* PyRun_InteractiveOneFlags (C 函式):    The Very High Level Layer.
                                                             (line  131)
* PyRun_SimpleFile (C 函式):             The Very High Level Layer.
                                                             (line  100)
* PyRun_SimpleFileEx (C 函式):           The Very High Level Layer.
                                                             (line  105)
* PyRun_SimpleFileExFlags (C 函式):      The Very High Level Layer.
                                                             (line  111)
* PyRun_SimpleString (C 函式):           The Very High Level Layer.
                                                             (line   79)
* PyRun_SimpleStringFlags (C 函式):      The Very High Level Layer.
                                                             (line   85)
* PyRun_String (C 函式):                 The Very High Level Layer.
                                                             (line  232)
* PyRun_StringFlags (C 函式):            The Very High Level Layer.
                                                             (line  239)
* PySeqIter_Check (C 函式):              迭代器（Iterator）物件.
                                                             (line   18)
* PySeqIter_New (C 函式):                迭代器（Iterator）物件.
                                                             (line   22)
* PySeqIter_Type (C 變數):               迭代器（Iterator）物件.
                                                             (line   12)
* PySequenceMethods (C 型態):            Sequence Object Structures.
                                                             (line    6)
* PySequenceMethods.sq_ass_item (C 成員函數): Sequence Object Structures.
                                                             (line   45)
* PySequenceMethods.sq_concat (C 成員函數): Sequence Object Structures.
                                                             (line   18)
* PySequenceMethods.sq_contains (C 成員函數): Sequence Object Structures.
                                                             (line   54)
* PySequenceMethods.sq_inplace_concat (C 成員函數): Sequence Object Structures.
                                                             (line   61)
* PySequenceMethods.sq_inplace_repeat (C 成員函數): Sequence Object Structures.
                                                             (line   71)
* PySequenceMethods.sq_item (C 成員函數): Sequence Object Structures.
                                                             (line   31)
* PySequenceMethods.sq_length (C 成員函數): Sequence Object Structures.
                                                             (line   11)
* PySequenceMethods.sq_repeat (C 成員函數): Sequence Object Structures.
                                                             (line   24)
* PySequence_Check (C 函式):             Sequence Protocol.  (line    6)
* PySequence_Concat (C 函式):            Sequence Protocol.  (line   20)
* PySequence_Contains (C 函式):          Sequence Protocol.  (line   95)
* PySequence_Count (C 函式):             Sequence Protocol.  (line   88)
* PySequence_DelItem (C 函式):           Sequence Protocol.  (line   67)
* PySequence_DelSlice (C 函式):          Sequence Protocol.  (line   80)
* PySequence_Fast (C 函式):              Sequence Protocol.  (line  122)
* PySequence_Fast_GET_ITEM (C 函式):     Sequence Protocol.  (line  144)
* PySequence_Fast_GET_SIZE (C 函式):     Sequence Protocol.  (line  136)
* PySequence_Fast_ITEMS (C 函式):        Sequence Protocol.  (line  150)
* PySequence_GetItem (C 函式):           Sequence Protocol.  (line   44)
* PySequence_GetItem():                  Reference Count Details.
                                                             (line  117)
* PySequence_GetSlice (C 函式):          Sequence Protocol.  (line   49)
* PySequence_Index (C 函式):             Sequence Protocol.  (line  101)
* PySequence_InPlaceConcat (C 函式):     Sequence Protocol.  (line   30)
* PySequence_InPlaceRepeat (C 函式):     Sequence Protocol.  (line   37)
* PySequence_ITEM (C 函式):              Sequence Protocol.  (line  160)
* PySequence_Length (C 函式):            Sequence Protocol.  (line   14)
* PySequence_List (C 函式):              Sequence Protocol.  (line  107)
* PySequence_Repeat (C 函式):            Sequence Protocol.  (line   25)
* PySequence_SetItem (C 函式):           Sequence Protocol.  (line   56)
* PySequence_SetSlice (C 函式):          Sequence Protocol.  (line   72)
* PySequence_Size (C 函式):              Sequence Protocol.  (line   14)
* PySequence_Tuple (C 函式):             Sequence Protocol.  (line  113)
* PySetObject (C 型態):                  Set Objects.        (line   19)
* PySet_Add (C 函式):                    Set Objects.        (line  108)
* PySet_Check (C 函式):                  Set Objects.        (line   45)
* PySet_Clear (C 函式):                  Set Objects.        (line  140)
* PySet_ClearFreeList (C 函式):          Set Objects.        (line  144)
* PySet_Contains (C 函式):               Set Objects.        (line   99)
* PySet_Discard (C 函式):                Set Objects.        (line  123)
* PySet_GET_SIZE (C 函式):               Set Objects.        (line   95)
* PySet_New (C 函式):                    Set Objects.        (line   70)
* PySet_Pop (C 函式):                    Set Objects.        (line  133)
* PySet_Size (C 函式):                   Set Objects.        (line   88)
* PySet_Type (C 變數):                   Set Objects.        (line   31)
* PySignal_SetWakeupFd (C 函式):         Signal Handling<2>. (line   28)
* PySlice_AdjustIndices (C 函式):        切片物件.           (line   99)
* PySlice_Check (C 函式):                切片物件.           (line   11)
* PySlice_GetIndices (C 函式):           切片物件.           (line   25)
* PySlice_GetIndicesEx (C 函式):         切片物件.           (line   43)
* PySlice_New (C 函式):                  切片物件.           (line   15)
* PySlice_Type (C 變數):                 切片物件.           (line    6)
* PySlice_Unpack (C 函式):               切片物件.           (line   85)
* PyState_AddModule (C 函式):            Module lookup.      (line   23)
* PyState_FindModule (C 函式):           Module lookup.      (line   15)
* PyState_RemoveModule (C 函式):         Module lookup.      (line   44)
* PyStatus (C 型態):                     PyStatus.           (line    6)
* PyStatus.err_msg (C 成員函數):         PyStatus.           (line   20)
* PyStatus.exitcode (C 成員函數):        PyStatus.           (line   16)
* PyStatus.func (C 成員函數):            PyStatus.           (line   24)
* PyStatus_Error (C 函式):               PyStatus.           (line   34)
* PyStatus_Exception (C 函式):           PyStatus.           (line   48)
* PyStatus_Exit (C 函式):                PyStatus.           (line   42)
* PyStatus_IsError (C 函式):             PyStatus.           (line   54)
* PyStatus_IsExit (C 函式):              PyStatus.           (line   58)
* PyStatus_NoMemory (C 函式):            PyStatus.           (line   38)
* PyStatus_Ok (C 函式):                  PyStatus.           (line   30)
* PyStructSequence_Desc (C 型態):        Struct Sequence Objects.
                                                             (line   34)
* PyStructSequence_Field (C 型態):       Struct Sequence Objects.
                                                             (line   57)
* PyStructSequence_GetItem (C 函式):     Struct Sequence Objects.
                                                             (line   86)
* PyStructSequence_GET_ITEM (C 函式):    Struct Sequence Objects.
                                                             (line   92)
* PyStructSequence_InitType (C 函式):    Struct Sequence Objects.
                                                             (line   19)
* PyStructSequence_InitType2 (C 函式):   Struct Sequence Objects.
                                                             (line   25)
* PyStructSequence_New (C 函式):         Struct Sequence Objects.
                                                             (line   81)
* PyStructSequence_NewType (C 函式):     Struct Sequence Objects.
                                                             (line   11)
* PyStructSequence_SetItem (C 函式):     Struct Sequence Objects.
                                                             (line   98)
* PyStructSequence_SET_ITEM (C 函式):    Struct Sequence Objects.
                                                             (line  108)
* PyStructSequence_UnnamedField (C 變數): Struct Sequence Objects.
                                                             (line   77)
* PySys_AddAuditHook (C 函式):           系統函式.           (line  127)
* PySys_AddWarnOption (C 函式):          系統函式.           (line   27)
* PySys_AddWarnOptionUnicode (C 函式):   系統函式.           (line   33)
* PySys_AddXOption (C 函式):             系統函式.           (line   87)
* PySys_Audit (C 函式):                  系統函式.           (line  103)
* PySys_FormatStderr (C 函式):           系統函式.           (line   80)
* PySys_FormatStdout (C 函式):           系統函式.           (line   72)
* PySys_GetObject (C 函式):              系統函式.           (line   11)
* PySys_GetXOptions (C 函式):            系統函式.           (line   96)
* PySys_ResetWarnOptions (C 函式):       系統函式.           (line   22)
* PySys_SetArgv (C 函式):                Process-wide parameters.
                                                             (line  255)
* PySys_SetArgv():                       Initializing and finalizing the interpreter.
                                                             (line    8)
* PySys_SetArgvEx (C 函式):              Process-wide parameters.
                                                             (line  214)
* PySys_SetArgvEx():                     嵌入式Python.       (line   17)
* PySys_SetArgvEx() <1>:                 Initializing and finalizing the interpreter.
                                                             (line    8)
* PySys_SetObject (C 函式):              系統函式.           (line   16)
* PySys_SetPath (C 函式):                系統函式.           (line   43)
* PySys_WriteStderr (C 函式):            系統函式.           (line   67)
* PySys_WriteStdout (C 函式):            系統函式.           (line   49)
* Python 3000:                           Glossary.           (line 1075)
* Python Editor:                         IDLE<54>.           (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>: Glossary.         (line 1041)
* Python Enhancement Proposals; PEP 100: Unicode<2>.         (line   15)
* Python Enhancement Proposals; PEP 11:  PEP 538 Legacy C Locale Coercion.
                                                             (line   19)
* Python Enhancement Proposals; PEP 11 <1>: Unsupported Operating Systems.
                                                             (line    6)
* Python Enhancement Proposals; PEP 11 <2>: Library Changes. (line   15)
* Python Enhancement Proposals; PEP 11 <3>: Build<26>.       (line   14)
* Python Enhancement Proposals; PEP 11 <4>: 在 Windows 上使用 Python.
                                                             (line   18)
* Python Enhancement Proposals; PEP 11 <5>: 其他平台.        (line    8)
* 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 --- Weak references.
                                                             (line  309)
* 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>: Other Language Changes<12>.
                                                             (line   12)
* Python Enhancement Proposals; PEP 218 <2>: PEP 218 A Standard Set Datatype.
                                                             (line   80)
* 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>: __future__ --- Future statement definitions.
                                                             (line   71)
* 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 Iterators.  (line  124)
* Python Enhancement Proposals; PEP 235: 簡介<11>.           (line   37)
* 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 237: Integers.           (line    6)
* Python Enhancement Proposals; PEP 237 <1>: PEP 237 Unifying Long Integers and Integers.
                                                             (line   22)
* Python Enhancement Proposals; PEP 237 <2>: Other Language Changes<12>.
                                                             (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  182)
* Python Enhancement Proposals; PEP 237 <5>: printf-style Bytes Formatting.
                                                             (line  189)
* Python Enhancement Proposals; PEP 238: Integers.           (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>: __future__ --- Future statement definitions.
                                                             (line   77)
* Python Enhancement Proposals; PEP 238 <5>: The Very High Level Layer.
                                                             (line  423)
* Python Enhancement Proposals; PEP 238 <6>: Glossary.       (line  458)
* Python Enhancement Proposals; PEP 241: PEP 241 Metadata in Python Packages.
                                                             (line   15)
* Python Enhancement Proposals; PEP 241 <1>: PEP 241 Metadata in Python Packages.
                                                             (line   28)
* Python Enhancement Proposals; PEP 241 <2>: PEP 241 Metadata in Python Packages.
                                                             (line   35)
* Python Enhancement Proposals; PEP 243: PEP 241 Metadata in Python Packages.
                                                             (line   39)
* Python Enhancement Proposals; PEP 247: hmac<2>.            (line   20)
* Python Enhancement Proposals; PEP 249: The sqlite3 package.
                                                             (line   18)
* Python Enhancement Proposals; PEP 249 <1>: The sqlite3 package.
                                                             (line  110)
* Python Enhancement Proposals; PEP 249 <2>: sqlite3 --- DB-API 2 0 interface for SQLite databases.
                                                             (line   18)
* Python Enhancement Proposals; PEP 249 <3>: sqlite3 --- DB-API 2 0 interface for SQLite databases.
                                                             (line  113)
* Python Enhancement Proposals; PEP 252: Related Links.      (line   17)
* Python Enhancement Proposals; PEP 252 <1>: Related Links.  (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>: Related Links.  (line   17)
* Python Enhancement Proposals; PEP 253 <3>: Related Links.  (line   19)
* Python Enhancement Proposals; PEP 253 <4>: Related Links.  (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   87)
* Python Enhancement Proposals; PEP 255 <5>: __future__ --- Future statement definitions.
                                                             (line   74)
* Python Enhancement Proposals; PEP 261: Unicode Changes.    (line   18)
* Python Enhancement Proposals; PEP 261 <1>: Unicode Changes.
                                                             (line   61)
* Python Enhancement Proposals; PEP 263: Other Language Changes<11>.
                                                             (line   98)
* Python Enhancement Proposals; PEP 263 <1>: PEP 263 Source Code Encodings.
                                                             (line   29)
* Python Enhancement Proposals; PEP 263 <2>: 簡介<11>.       (line   41)
* Python Enhancement Proposals; PEP 263 <3>: Tokenizing Input.
                                                             (line   35)
* Python Enhancement Proposals; PEP 263 <4>: Tokenizing Input.
                                                             (line   89)
* Python Enhancement Proposals; PEP 263 <5>: Unicode Literals in Python Source Code.
                                                             (line   48)
* Python Enhancement Proposals; PEP 264: Other Changes and Fixes<3>.
                                                             (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 --- Import modules from Zip archives.
                                                             (line   42)
* Python Enhancement Proposals; PEP 273 <3>: zipimport --- Import modules from Zip archives.
                                                             (line   45)
* Python Enhancement Proposals; PEP 274: New Syntax.         (line   38)
* Python Enhancement Proposals; PEP 275: Why isn't there a switch or case statement in Python?.
                                                             (line    8)
* 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>: Glossary.       (line 1287)
* Python Enhancement Proposals; PEP 279: PEP 279 enumerate.  (line   27)
* Python Enhancement Proposals; PEP 282: PEP 282 The logging Package.
                                                             (line  101)
* Python Enhancement Proposals; PEP 282 <1>: PEP 282 The logging Package.
                                                             (line  107)
* Python Enhancement Proposals; PEP 282 <2>: Archiving operations.
                                                             (line   45)
* Python Enhancement Proposals; PEP 282 <3>: Integration with the warnings module.
                                                             (line   36)
* Python Enhancement Proposals; PEP 282 <4>: distutils log --- Simple PEP 282-style logging.
                                                             (line    6)
* 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   56)
* Python Enhancement Proposals; PEP 289 <1>: Other Language Changes<12>.
                                                             (line   15)
* Python Enhancement Proposals; PEP 289 <2>: Python documentation.
                                                             (line   12)
* Python Enhancement Proposals; PEP 292: PEP 292 Simpler String Substitutions.
                                                             (line   45)
* Python Enhancement Proposals; PEP 292 <1>: Template strings.
                                                             (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 301 <1>: distutils command register --- Register a module with the Python Package Index.
                                                             (line    7)
* Python Enhancement Proposals; PEP 302: Using importlib as the Implementation of Import.
                                                             (line   13)
* Python Enhancement Proposals; PEP 302 <1>: Visible Changes.
                                                             (line   18)
* Python Enhancement Proposals; PEP 302 <2>: Porting Python code.
                                                             (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  289)
* 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>: The import system.
                                                             (line   42)
* Python Enhancement Proposals; PEP 302 <10>: References.    (line   10)
* Python Enhancement Proposals; PEP 302 <11>: 內建函式.      (line 1781)
* Python Enhancement Proposals; PEP 302 <12>: linecache --- Random access to text lines.
                                                             (line   31)
* Python Enhancement Proposals; PEP 302 <13>: sys --- System-specific parameters and functions.
                                                             (line 1092)
* Python Enhancement Proposals; PEP 302 <14>: sys --- System-specific parameters and functions.
                                                             (line 1102)
* Python Enhancement Proposals; PEP 302 <15>: zipimport --- Import modules from Zip archives.
                                                             (line   47)
* Python Enhancement Proposals; PEP 302 <16>: zipimport --- Import modules from Zip archives.
                                                             (line   49)
* Python Enhancement Proposals; PEP 302 <17>: pkgutil --- Package extension utility.
                                                             (line   55)
* Python Enhancement Proposals; PEP 302 <18>: pkgutil --- Package extension utility.
                                                             (line   57)
* Python Enhancement Proposals; PEP 302 <19>: pkgutil --- Package extension utility.
                                                             (line   58)
* Python Enhancement Proposals; PEP 302 <20>: pkgutil --- Package extension utility.
                                                             (line   66)
* Python Enhancement Proposals; PEP 302 <21>: pkgutil --- Package extension utility.
                                                             (line   74)
* Python Enhancement Proposals; PEP 302 <22>: pkgutil --- Package extension utility.
                                                             (line   87)
* Python Enhancement Proposals; PEP 302 <23>: pkgutil --- Package extension utility.
                                                             (line  103)
* Python Enhancement Proposals; PEP 302 <24>: pkgutil --- Package extension utility.
                                                             (line  118)
* Python Enhancement Proposals; PEP 302 <25>: pkgutil --- Package extension utility.
                                                             (line  138)
* Python Enhancement Proposals; PEP 302 <26>: pkgutil --- Package extension utility.
                                                             (line  159)
* Python Enhancement Proposals; PEP 302 <27>: pkgutil --- Package extension utility.
                                                             (line  198)
* Python Enhancement Proposals; PEP 302 <28>: runpy --- Locating and executing Python modules.
                                                             (line   32)
* Python Enhancement Proposals; PEP 302 <29>: 簡介<11>.      (line   45)
* Python Enhancement Proposals; PEP 302 <30>: importlib abc -- Abstract base classes related to import.
                                                             (line   38)
* Python Enhancement Proposals; PEP 302 <31>: importlib abc -- Abstract base classes related to import.
                                                             (line  157)
* Python Enhancement Proposals; PEP 302 <32>: importlib abc -- Abstract base classes related to import.
                                                             (line  351)
* Python Enhancement Proposals; PEP 302 <33>: importlib abc -- Abstract base classes related to import.
                                                             (line  374)
* Python Enhancement Proposals; PEP 302 <34>: importlib abc -- Abstract base classes related to import.
                                                             (line  444)
* Python Enhancement Proposals; PEP 302 <35>: imp --- Access the import internals.
                                                             (line  345)
* Python Enhancement Proposals; PEP 302 <36>: Glossary.      (line  450)
* Python Enhancement Proposals; PEP 302 <37>: Glossary.      (line  777)
* Python Enhancement Proposals; PEP 305: PEP 305 Comma-separated Files.
                                                             (line   42)
* Python Enhancement Proposals; PEP 305 <1>: csv --- CSV File Reading and Writing.
                                                             (line   38)
* 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   17)
* 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    6)
* Python Enhancement Proposals; PEP 3101 <1>: PEP 3101 A New Approach To String Formatting.
                                                             (line    9)
* Python Enhancement Proposals; PEP 3101 <2>: PEP 3101 Advanced String Formatting.
                                                             (line  162)
* Python Enhancement Proposals; PEP 3101 <3>: Custom String Formatting.
                                                             (line    8)
* Python Enhancement Proposals; PEP 3101 <4>: Custom String Formatting.
                                                             (line   60)
* Python Enhancement Proposals; PEP 3102: New Syntax.        (line   13)
* Python Enhancement Proposals; PEP 3104: New Syntax.        (line   24)
* Python Enhancement Proposals; PEP 3104 <1>: The nonlocal statement.
                                                             (line   26)
* 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>: __future__ --- Future statement definitions.
                                                             (line   87)
* 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>: Function definitions.
                                                             (line  128)
* Python Enhancement Proposals; PEP 3108: Library Changes.   (line    7)
* Python Enhancement Proposals; PEP 3108 <1>: Library Changes.
                                                             (line   17)
* Python Enhancement Proposals; PEP 3108 <2>: Library Changes.
                                                             (line   95)
* Python Enhancement Proposals; PEP 3109: Changed Syntax.    (line    6)
* Python Enhancement Proposals; PEP 3109 <1>: Changes To Exceptions.
                                                             (line   29)
* Python Enhancement Proposals; PEP 3110: Changed Syntax.    (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>: __future__ --- Future statement definitions.
                                                             (line   90)
* Python Enhancement Proposals; PEP 3113: Removed Syntax.    (line    6)
* Python Enhancement Proposals; PEP 3114: Operators And Special Methods.
                                                             (line   19)
* Python Enhancement Proposals; PEP 3115: types<4>.          (line   10)
* Python Enhancement Proposals; PEP 3115 <1>: Changed Syntax.
                                                             (line   18)
* Python Enhancement Proposals; PEP 3115 <2>: Preparing the class namespace.
                                                             (line   21)
* Python Enhancement Proposals; PEP 3115 <3>: Class definitions.
                                                             (line   71)
* Python Enhancement Proposals; PEP 3115 <4>: Dynamic Type Creation.
                                                             (line   53)
* Python Enhancement Proposals; PEP 3116: Optimizations<7>.  (line    8)
* Python Enhancement Proposals; PEP 3116 <1>: PEP 3116 New I/O Library.
                                                             (line   69)
* Python Enhancement Proposals; PEP 3116 <2>: Glossary.      (line 1287)
* 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 changes.   (line   29)
* Python Enhancement Proposals; PEP 3118 <3>: Build and C API Changes<4>.
                                                             (line    8)
* Python Enhancement Proposals; PEP 3118 <4>: Build and C API Changes<7>.
                                                             (line   12)
* Python Enhancement Proposals; PEP 3118 <5>: PEP 3118 Revised Buffer Protocol.
                                                             (line   46)
* Python Enhancement Proposals; PEP 3118 <6>: Library<39>.   (line   99)
* Python Enhancement Proposals; PEP 3118 <7>: Library<44>.   (line   61)
* Python Enhancement Proposals; PEP 3118 <8>: Library<87>.   (line  956)
* Python Enhancement Proposals; PEP 3118 <9>: Memory Views.  (line  109)
* 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>: Collections Abstract Base Classes.
                                                             (line  316)
* Python Enhancement Proposals; PEP 3119 <3>: abc --- Abstract Base Classes.
                                                             (line   11)
* Python Enhancement Proposals; PEP 3119 <4>: Object Protocol.
                                                             (line  217)
* Python Enhancement Proposals; PEP 3119 <5>: Object Protocol.
                                                             (line  237)
* Python Enhancement Proposals; PEP 3120: Text Vs Data Instead Of Unicode Vs 8-bit.
                                                             (line  107)
* Python Enhancement Proposals; PEP 3120 <1>: Lexical analysis.
                                                             (line   12)
* Python Enhancement Proposals; PEP 3120 <2>: 簡介<11>.      (line   77)
* Python Enhancement Proposals; PEP 3121: Build and C API Changes<7>.
                                                             (line   14)
* Python Enhancement Proposals; PEP 3121 <1>: Initializing C modules.
                                                             (line   55)
* Python Enhancement Proposals; PEP 3123: Build and C API Changes<7>.
                                                             (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>: Class definitions.
                                                             (line   77)
* Python Enhancement Proposals; PEP 3131: Text Vs Data Instead Of Unicode Vs 8-bit.
                                                             (line  109)
* Python Enhancement Proposals; PEP 3131 <1>: Identifiers and keywords.
                                                             (line   10)
* Python Enhancement Proposals; PEP 3131 <2>: Identifiers and keywords.
                                                             (line   19)
* Python Enhancement Proposals; PEP 3132: New Syntax.        (line   28)
* Python Enhancement Proposals; PEP 3132 <1>: Assignment statements.
                                                             (line  159)
* Python Enhancement Proposals; PEP 3134: Changed Syntax.    (line    6)
* Python Enhancement Proposals; PEP 3134 <1>: Changes To Exceptions.
                                                             (line   40)
* Python Enhancement Proposals; PEP 3134 <2>: Changes To Exceptions.
                                                             (line   60)
* Python Enhancement Proposals; PEP 3135: Builtins.          (line    6)
* Python Enhancement Proposals; PEP 3135 <1>: Creating the class object.
                                                             (line   54)
* 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 314 <1>: distutils core --- Core Distutils functionality.
                                                             (line  103)
* Python Enhancement Proposals; PEP 3141: PEP 3141 A Type Hierarchy for Numbers.
                                                             (line   43)
* Python Enhancement Proposals; PEP 3141 <1>: numbers --- Numeric abstract base classes.
                                                             (line   10)
* Python Enhancement Proposals; PEP 3141 <2>: abc --- Abstract Base Classes.
                                                             (line   12)
* Python Enhancement Proposals; PEP 3144: ipaddress<4>.      (line   10)
* Python Enhancement Proposals; PEP 3147: PEP 421 Adding sys implementation.
                                                             (line   21)
* Python Enhancement Proposals; PEP 3147 <1>: PEP 3147 PYC Repository Directories.
                                                             (line   69)
* Python Enhancement Proposals; PEP 3147 <2>: "Compiled" Python files.
                                                             (line   47)
* Python Enhancement Proposals; PEP 3147 <3>: Import-related module attributes.
                                                             (line   79)
* Python Enhancement Proposals; PEP 3147 <4>: test support --- Utilities for the Python test suite.
                                                             (line  192)
* Python Enhancement Proposals; PEP 3147 <5>: runpy --- Locating and executing Python modules.
                                                             (line   87)
* Python Enhancement Proposals; PEP 3147 <6>: 簡介<11>.      (line   81)
* 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 --- Compile Python source files.
                                                             (line   30)
* Python Enhancement Proposals; PEP 3147 <11>: py_compile --- Compile Python source files.
                                                             (line   69)
* Python Enhancement Proposals; PEP 3147 <12>: Command-line use.
                                                             (line   56)
* Python Enhancement Proposals; PEP 3147 <13>: Public functions.
                                                             (line   36)
* Python Enhancement Proposals; PEP 3147 <14>: Public functions.
                                                             (line   97)
* Python Enhancement Proposals; PEP 3147 <15>: imp --- Access the import internals.
                                                             (line  198)
* Python Enhancement Proposals; PEP 3147 <16>: imp --- Access the import internals.
                                                             (line  205)
* Python Enhancement Proposals; PEP 3147 <17>: imp --- Access the import internals.
                                                             (line  228)
* Python Enhancement Proposals; PEP 3147 <18>: imp --- Access the import internals.
                                                             (line  232)
* Python Enhancement Proposals; PEP 3147 <19>: imp --- Access the import internals.
                                                             (line  244)
* Python Enhancement Proposals; PEP 3147 <20>: 匯入模組<2>.  (line  196)
* Python Enhancement Proposals; PEP 3147 <21>: How do I create a pyc file?.
                                                             (line   12)
* Python Enhancement Proposals; PEP 3147 <22>: distutils util --- Miscellaneous other utility functions.
                                                             (line  132)
* Python Enhancement Proposals; PEP 3148: PEP 3148 The concurrent futures module.
                                                             (line   51)
* Python Enhancement Proposals; PEP 3148 <1>: Module Functions.
                                                             (line   61)
* Python Enhancement Proposals; PEP 3149: PEP 3149 ABI Version Tagged so Files.
                                                             (line   33)
* Python Enhancement Proposals; PEP 3149 <1>: Core and Builtins<70>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 3149 <2>: sys --- System-specific parameters and functions.
                                                             (line   15)
* Python Enhancement Proposals; PEP 3151: PEP 3151 Reworking the OS and IO exception hierarchy.
                                                             (line   84)
* Python Enhancement Proposals; PEP 3151 <1>: OS exceptions. (line  113)
* Python Enhancement Proposals; PEP 3151 <2>: Exceptions<10>.
                                                             (line   10)
* Python Enhancement Proposals; PEP 3151 <3>: select --- Waiting for I/O completion.
                                                             (line   28)
* Python Enhancement Proposals; PEP 3151 <4>: resource --- Resource usage information.
                                                             (line   21)
* Python Enhancement Proposals; PEP 3151 <5>: Standard Exceptions.
                                                             (line  181)
* Python Enhancement Proposals; PEP 3154: Summary -- Release Highlights<2>.
                                                             (line   57)
* Python Enhancement Proposals; PEP 3154 <1>: pickle<4>.     (line   16)
* Python Enhancement Proposals; PEP 3154 <2>: Library<28>.   (line 1284)
* 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   62)
* Python Enhancement Proposals; PEP 3155 <1>: Glossary.      (line 1104)
* Python Enhancement Proposals; PEP 3156: Summary -- Release Highlights<2>.
                                                             (line   31)
* Python Enhancement Proposals; PEP 3156 <1>: Summary -- Release Highlights<2>.
                                                             (line   44)
* Python Enhancement Proposals; PEP 3156 <2>: asyncio<6>.    (line    6)
* Python Enhancement Proposals; PEP 3156 <3>: asyncio<6>.    (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>: Other Language Changes<12>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 318 <3>: Class definitions.
                                                             (line   80)
* Python Enhancement Proposals; PEP 322: PEP 322 Reverse Iteration.
                                                             (line   35)
* Python Enhancement Proposals; PEP 322 <1>: Other Language Changes<12>.
                                                             (line   13)
* Python Enhancement Proposals; PEP 324: PEP 324 New subprocess Module.
                                                             (line   86)
* Python Enhancement Proposals; PEP 324 <1>: subprocess --- Subprocess management.
                                                             (line   25)
* Python Enhancement Proposals; PEP 325: PEP 342 New Generator Features.
                                                             (line  147)
* Python Enhancement Proposals; PEP 327: The Context type.   (line   56)
* Python Enhancement Proposals; PEP 328: Porting Python code.
                                                             (line   36)
* Python Enhancement Proposals; PEP 328 <1>: Removed Syntax. (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>: Other Language Changes<12>.
                                                             (line   21)
* Python Enhancement Proposals; PEP 328 <6>: References.     (line   20)
* Python Enhancement Proposals; PEP 328 <7>: 內建函式.       (line 1799)
* Python Enhancement Proposals; PEP 328 <8>: __future__ --- Future statement definitions.
                                                             (line   80)
* Python Enhancement Proposals; PEP 328 <9>: 簡介<11>.       (line   49)
* Python Enhancement Proposals; PEP 331: PEP 331 Locale-Independent Float/String Conversions.
                                                             (line   38)
* Python Enhancement Proposals; PEP 333: The wsgiref package.
                                                             (line    8)
* Python Enhancement Proposals; PEP 333 <1>: The wsgiref package.
                                                             (line   31)
* Python Enhancement Proposals; PEP 3333: PEP 3333 Python Web Server Gateway Interface v1 0 1.
                                                             (line   50)
* Python Enhancement Proposals; PEP 3333 <1>: wsgiref --- WSGI Utilities and Reference Implementation.
                                                             (line   24)
* Python Enhancement Proposals; PEP 3333 <2>: wsgiref util -- WSGI environment utilities.
                                                             (line    8)
* Python Enhancement Proposals; PEP 3333 <3>: wsgiref util -- WSGI environment utilities.
                                                             (line   10)
* Python Enhancement Proposals; PEP 3333 <4>: wsgiref util -- WSGI environment utilities.
                                                             (line   28)
* Python Enhancement Proposals; PEP 3333 <5>: wsgiref util -- WSGI environment utilities.
                                                             (line   74)
* Python Enhancement Proposals; PEP 3333 <6>: wsgiref headers -- WSGI response header tools.
                                                             (line   12)
* Python Enhancement Proposals; PEP 3333 <7>: wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line   21)
* Python Enhancement Proposals; PEP 3333 <8>: wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line   96)
* Python Enhancement Proposals; PEP 3333 <9>: wsgiref validate --- WSGI conformance checker.
                                                             (line   13)
* Python Enhancement Proposals; PEP 3333 <10>: wsgiref validate --- WSGI conformance checker.
                                                             (line   41)
* Python Enhancement Proposals; PEP 3333 <11>: wsgiref handlers -- server/gateway base classes.
                                                             (line  233)
* Python Enhancement Proposals; PEP 3333 <12>: wsgiref handlers -- server/gateway base classes.
                                                             (line  249)
* Python Enhancement Proposals; PEP 3333 <13>: wsgiref handlers -- server/gateway base classes.
                                                             (line  256)
* Python Enhancement Proposals; PEP 3333 <14>: wsgiref handlers -- server/gateway base classes.
                                                             (line  265)
* Python Enhancement Proposals; PEP 3333 <15>: wsgiref handlers -- server/gateway base classes.
                                                             (line  307)
* Python Enhancement Proposals; PEP 338: PEP 338 Executing Modules as Scripts.
                                                             (line   21)
* Python Enhancement Proposals; PEP 338 <1>: Interface options.
                                                             (line  100)
* Python Enhancement Proposals; PEP 338 <2>: References.     (line   24)
* Python Enhancement Proposals; PEP 338 <3>: runpy --- Locating and executing Python modules.
                                                             (line  169)
* Python Enhancement Proposals; PEP 339: Build and C API Changes<10>.
                                                             (line   45)
* 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   92)
* Python Enhancement Proposals; PEP 342 <4>: Collections Abstract Base Classes.
                                                             (line  152)
* Python Enhancement Proposals; PEP 342 <5>: Passing values into a generator.
                                                             (line   25)
* Python Enhancement Proposals; PEP 342 <6>: Python documentation.
                                                             (line   14)
* Python Enhancement Proposals; PEP 343: The contextlib module.
                                                             (line   64)
* Python Enhancement Proposals; PEP 343 <1>: PEP 342 New Generator Features.
                                                             (line  129)
* Python Enhancement Proposals; PEP 343 <2>: The contextlib module<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   98)
* Python Enhancement Proposals; PEP 343 <5>: Using a context manager as a function decorator.
                                                             (line   51)
* Python Enhancement Proposals; PEP 343 <6>: __future__ --- Future statement definitions.
                                                             (line   84)
* Python Enhancement Proposals; PEP 343 <7>: Glossary.       (line  259)
* Python Enhancement Proposals; PEP 347: Build and C API Changes<10>.
                                                             (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: PEP 353 Using ssize_t as the index type.
                                                             (line   48)
* Python Enhancement Proposals; PEP 353 <1>: PEP 353 Using ssize_t as the index type.
                                                             (line   54)
* Python Enhancement Proposals; PEP 353 <2>: Build and C API Changes<10>.
                                                             (line   20)
* Python Enhancement Proposals; PEP 356: What's New in Python 2 5.
                                                             (line   10)
* Python Enhancement Proposals; PEP 357: PEP 357 The '__index__' method.
                                                             (line   39)
* Python Enhancement Proposals; PEP 361: What's New in Python 2 6.
                                                             (line   10)
* Python Enhancement Proposals; PEP 362: PEP 362 Function Signature Object.
                                                             (line   19)
* Python Enhancement Proposals; PEP 362 <1>: Introspecting callables with the Signature object.
                                                             (line  342)
* Python Enhancement Proposals; PEP 362 <2>: Glossary.       (line   94)
* Python Enhancement Proposals; PEP 362 <3>: Glossary.       (line  988)
* Python Enhancement Proposals; PEP 366: Visible Changes.    (line   24)
* Python Enhancement Proposals; PEP 366 <1>: Import-related module attributes.
                                                             (line   30)
* Python Enhancement Proposals; PEP 366 <2>: Import-related module attributes.
                                                             (line   34)
* 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 --- Locating and executing Python modules.
                                                             (line  173)
* Python Enhancement Proposals; PEP 366 <6>: 簡介<11>.       (line   53)
* Python Enhancement Proposals; PEP 370: PEP 370 Per-user site-packages Directory.
                                                             (line   36)
* Python Enhancement Proposals; PEP 370 <1>: Miscellaneous options.
                                                             (line  123)
* Python Enhancement Proposals; PEP 370 <2>: Environment variables.
                                                             (line  168)
* Python Enhancement Proposals; PEP 370 <3>: Environment variables.
                                                             (line  180)
* Python Enhancement Proposals; PEP 370 <4>: Command Line Interface<4>.
                                                             (line   37)
* Python Enhancement Proposals; PEP 371: PEP 371 The multiprocessing Package.
                                                             (line  145)
* Python Enhancement Proposals; PEP 372: PEP 372 Ordered Dictionaries.
                                                             (line   31)
* Python Enhancement Proposals; PEP 372 <1>: PEP 372 Adding an Ordered Dictionary to collections.
                                                             (line   97)
* Python Enhancement Proposals; PEP 373: The Future for 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 Mini-Language.
                                                             (line  103)
* Python Enhancement Proposals; PEP 380: PEP 380 Syntax for Delegating to a Subgenerator.
                                                             (line   66)
* Python Enhancement Proposals; PEP 380 <1>: Yield expressions.
                                                             (line   97)
* Python Enhancement Proposals; PEP 383: Error Handlers.     (line   58)
* Python Enhancement Proposals; PEP 383 <1>: Socket families.
                                                             (line   15)
* Python Enhancement Proposals; PEP 383 <2>: Locale Encoding.
                                                             (line   15)
* Python Enhancement Proposals; PEP 383 <3>: Locale Encoding.
                                                             (line   53)
* Python Enhancement Proposals; PEP 383 <4>: File System Encoding.
                                                             (line    9)
* Python Enhancement Proposals; PEP 384: PEP 384 Defining a Stable ABI.
                                                             (line   24)
* Python Enhancement Proposals; PEP 384 <1>: Stable Application Binary Interface.
                                                             (line   36)
* Python Enhancement Proposals; PEP 385: Code Repository.    (line   13)
* Python Enhancement Proposals; PEP 389: PEP 389 Argparse Command Line Parsing Module.
                                                             (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   94)
* Python Enhancement Proposals; PEP 392: What's New In Python 3 2.
                                                             (line   16)
* Python Enhancement Proposals; PEP 393: PEP 393 Flexible String Representation.
                                                             (line   16)
* Python Enhancement Proposals; PEP 393 <1>: Functionality.  (line    6)
* Python Enhancement Proposals; PEP 393 <2>: Performance and resource usage.
                                                             (line   29)
* Python Enhancement Proposals; PEP 393 <3>: Optimizations<5>.
                                                             (line    8)
* Python Enhancement Proposals; PEP 393 <4>: Build and C API Changes<4>.
                                                             (line   12)
* Python Enhancement Proposals; PEP 393 <5>: Deprecated Python modules functions and methods<4>.
                                                             (line   10)
* Python Enhancement Proposals; PEP 393 <6>: Deprecated functions and types of the C API<3>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 393 <7>: Porting C code. (line   17)
* Python Enhancement Proposals; PEP 393 <8>: Encodings and Unicode.
                                                             (line    7)
* Python Enhancement Proposals; PEP 393 <9>: sys --- System-specific parameters and functions.
                                                             (line 1018)
* Python Enhancement Proposals; PEP 393 <10>: Unicode Objects.
                                                             (line    6)
* Python Enhancement Proposals; PEP 393 <11>: Deprecated Py_UNICODE APIs.
                                                             (line    8)
* Python Enhancement Proposals; PEP 395: Open issues.        (line   18)
* 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 Python Launcher for Windows.
                                                             (line   31)
* Python Enhancement Proposals; PEP 397 <2>: Python Launcher for Windows.
                                                             (line   18)
* Python Enhancement Proposals; PEP 397 <3>: Creating virtual environments.
                                                             (line  194)
* Python Enhancement Proposals; PEP 398: What's New In Python 3 3.
                                                             (line   13)
* Python Enhancement Proposals; PEP 4:   Library Changes.    (line   13)
* Python Enhancement Proposals; PEP 405: PEP 405 Virtual Environments.
                                                             (line   22)
* Python Enhancement Proposals; PEP 405 <1>: venv --- Creation of virtual environments.
                                                             (line   19)
* Python Enhancement Proposals; PEP 409: PEP 409 Suppressing exception context.
                                                             (line   63)
* Python Enhancement Proposals; PEP 411: sys --- System-specific parameters and functions.
                                                             (line  817)
* Python Enhancement Proposals; PEP 411 <1>: sys --- System-specific parameters and functions.
                                                             (line  827)
* Python Enhancement Proposals; PEP 411 <2>: sys --- System-specific parameters and functions.
                                                             (line 1426)
* Python Enhancement Proposals; PEP 411 <3>: sys --- System-specific parameters and functions.
                                                             (line 1446)
* Python Enhancement Proposals; PEP 411 <4>: Glossary.       (line 1071)
* Python Enhancement Proposals; PEP 412: PEP 412 Key-Sharing Dictionary.
                                                             (line   15)
* Python Enhancement Proposals; PEP 414: PEP 414 Explicit Unicode literals.
                                                             (line   17)
* Python Enhancement Proposals; PEP 414 <1>: String and Bytes literals.
                                                             (line   60)
* Python Enhancement Proposals; PEP 418: time<5>.            (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<55>.
                                                             (line   56)
* Python Enhancement Proposals; PEP 420 <3>: Core and Builtins<60>.
                                                             (line  114)
* Python Enhancement Proposals; PEP 420 <4>: The import system.
                                                             (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>: 簡介<11>.      (line   57)
* Python Enhancement Proposals; PEP 420 <12>: Glossary.      (line  450)
* Python Enhancement Proposals; PEP 420 <13>: Glossary.      (line  898)
* Python Enhancement Proposals; PEP 420 <14>: Glossary.      (line 1046)
* Python Enhancement Proposals; PEP 421: SimpleNamespace.    (line   16)
* Python Enhancement Proposals; PEP 421 <1>: sys --- System-specific parameters and functions.
                                                             (line  928)
* Python Enhancement Proposals; PEP 421 <2>: sys --- System-specific parameters and functions.
                                                             (line  933)
* Python Enhancement Proposals; PEP 424: Other Language Changes<5>.
                                                             (line   57)
* Python Enhancement Proposals; PEP 424 <1>: operator<2>.    (line    8)
* Python Enhancement Proposals; PEP 427: Key terms.          (line   36)
* Python Enhancement Proposals; PEP 428: Summary -- Release Highlights<2>.
                                                             (line   39)
* Python Enhancement Proposals; PEP 428 <1>: pathlib<5>.     (line   17)
* Python Enhancement Proposals; PEP 428 <2>: pathlib --- Object-oriented filesystem paths.
                                                             (line   39)
* Python Enhancement Proposals; PEP 429: What's New In Python 3 4.
                                                             (line   16)
* Python Enhancement Proposals; PEP 432: Other CPython implementation changes.
                                                             (line    7)
* Python Enhancement Proposals; PEP 432 <1>: Core and Builtins<38>.
                                                             (line  313)
* 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 435: Summary -- Release Highlights<2>.
                                                             (line   36)
* Python Enhancement Proposals; PEP 435 <1>: enum<5>.        (line    6)
* Python Enhancement Proposals; PEP 435 <2>: enum<5>.        (line   15)
* Python Enhancement Proposals; PEP 436: Summary -- Release Highlights<2>.
                                                             (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: Summary -- Release Highlights<2>.
                                                             (line  113)
* Python Enhancement Proposals; PEP 442 <1>: Summary -- Release Highlights<2>.
                                                             (line  115)
* Python Enhancement Proposals; PEP 442 <2>: PEP 442 Safe Object Finalization.
                                                             (line    6)
* Python Enhancement Proposals; PEP 442 <3>: PEP 442 Safe Object Finalization.
                                                             (line   21)
* Python Enhancement Proposals; PEP 442 <4>: gc --- Garbage Collector interface.
                                                             (line  225)
* Python Enhancement Proposals; PEP 442 <5>: Finalization and De-allocation.
                                                             (line   77)
* Python Enhancement Proposals; PEP 442 <6>: PyTypeObject Slots.
                                                             (line 1385)
* Python Enhancement Proposals; PEP 443: Summary -- Release Highlights<2>.
                                                             (line   55)
* Python Enhancement Proposals; PEP 443 <1>: functools<4>.   (line   22)
* Python Enhancement Proposals; PEP 443 <2>: Glossary.       (line  546)
* Python Enhancement Proposals; PEP 445: Summary -- Release Highlights<2>.
                                                             (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<2>.
                                                             (line   14)
* Python Enhancement Proposals; PEP 446 <1>: Summary -- Release Highlights<2>.
                                                             (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 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<44>.
                                                             (line   10)
* Python Enhancement Proposals; PEP 448 <3>: Documentation<48>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 448 <4>: Core and Builtins<63>.
                                                             (line   12)
* Python Enhancement Proposals; PEP 448 <5>: Core and Builtins<66>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 448 <6>: Dictionary displays.
                                                             (line   29)
* Python Enhancement Proposals; PEP 448 <7>: Calls.          (line  113)
* Python Enhancement Proposals; PEP 448 <8>: Expression lists.
                                                             (line   22)
* Python Enhancement Proposals; PEP 450: Summary -- Release Highlights<2>.
                                                             (line   47)
* Python Enhancement Proposals; PEP 450 <1>: statistics<3>.  (line    6)
* Python Enhancement Proposals; PEP 450 <2>: statistics<3>.  (line   14)
* Python Enhancement Proposals; PEP 451: PEP 489 Multi-phase extension module initialization.
                                                             (line    7)
* Python Enhancement Proposals; PEP 451 <1>: Summary -- Release Highlights<2>.
                                                             (line   22)
* Python Enhancement Proposals; PEP 451 <2>: PEP 451 A ModuleSpec Type for the Import System.
                                                             (line    6)
* Python Enhancement Proposals; PEP 451 <3>: Core and Builtins<55>.
                                                             (line   76)
* Python Enhancement Proposals; PEP 451 <4>: References.     (line   26)
* Python Enhancement Proposals; PEP 451 <5>: sys --- System-specific parameters and functions.
                                                             (line 1047)
* Python Enhancement Proposals; PEP 451 <6>: pkgutil --- Package extension utility.
                                                             (line   90)
* Python Enhancement Proposals; PEP 451 <7>: pkgutil --- Package extension utility.
                                                             (line  121)
* Python Enhancement Proposals; PEP 451 <8>: runpy --- Locating and executing Python modules.
                                                             (line   90)
* Python Enhancement Proposals; PEP 451 <9>: runpy --- Locating and executing Python modules.
                                                             (line  162)
* Python Enhancement Proposals; PEP 451 <10>: runpy --- Locating and executing Python modules.
                                                             (line  177)
* Python Enhancement Proposals; PEP 451 <11>: 簡介<11>.      (line   61)
* Python Enhancement Proposals; PEP 451 <12>: Multi-phase initialization.
                                                             (line   71)
* Python Enhancement Proposals; PEP 451 <13>: Glossary.      (line  450)
* Python Enhancement Proposals; PEP 453: Summary -- Release Highlights<2>.
                                                             (line   12)
* Python Enhancement Proposals; PEP 453 <1>: Summary -- Release Highlights<2>.
                                                             (line   34)
* Python Enhancement Proposals; PEP 453 <2>: Bootstrapping pip By Default.
                                                             (line    6)
* Python Enhancement Proposals; PEP 453 <3>: Documentation Changes.
                                                             (line   20)
* Python Enhancement Proposals; PEP 453 <4>: ensurepip.      (line    7)
* Python Enhancement Proposals; PEP 453 <5>: venv<4>.        (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   20)
* Python Enhancement Proposals; PEP 453 <10>: ensurepip --- Bootstrapping the pip installer.
                                                             (line   33)
* Python Enhancement Proposals; PEP 454: Summary -- Release Highlights<2>.
                                                             (line   50)
* Python Enhancement Proposals; PEP 454 <1>: tracemalloc<3>. (line    6)
* Python Enhancement Proposals; PEP 454 <2>: tracemalloc<3>. (line   22)
* Python Enhancement Proposals; PEP 456: Summary -- Release Highlights<2>.
                                                             (line   75)
* Python Enhancement Proposals; PEP 456 <1>: PEP 456 Secure and Interchangeable Hash Algorithm.
                                                             (line    6)
* 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   45)
* Python Enhancement Proposals; PEP 465 <2>: Build and C API Changes<3>.
                                                             (line   43)
* Python Enhancement Proposals; PEP 465 <3>: Tools/Demos<36>.
                                                             (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<47>.    (line   87)
* Python Enhancement Proposals; PEP 468 <2>: OrderedDict objects.
                                                             (line   85)
* 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<86>.    (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<4>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 475 <3>: Library<37>.    (line  229)
* Python Enhancement Proposals; PEP 475 <4>: Library<84>.    (line  143)
* Python Enhancement Proposals; PEP 475 <5>: 內建函式.       (line 1249)
* Python Enhancement Proposals; PEP 475 <6>: OS exceptions.  (line   78)
* Python Enhancement Proposals; PEP 475 <7>: File Descriptor Operations.
                                                             (line  291)
* Python Enhancement Proposals; PEP 475 <8>: File Descriptor Operations.
                                                             (line  567)
* Python Enhancement Proposals; PEP 475 <9>: File Descriptor Operations.
                                                             (line  685)
* Python Enhancement Proposals; PEP 475 <10>: Process Management.
                                                             (line  804)
* Python Enhancement Proposals; PEP 475 <11>: Functions<2>.  (line  228)
* Python Enhancement Proposals; PEP 475 <12>: Socket Objects.
                                                             (line   28)
* Python Enhancement Proposals; PEP 475 <13>: Socket Objects.
                                                             (line   80)
* Python Enhancement Proposals; PEP 475 <14>: Socket Objects.
                                                             (line  234)
* Python Enhancement Proposals; PEP 475 <15>: Socket Objects.
                                                             (line  248)
* Python Enhancement Proposals; PEP 475 <16>: Socket Objects.
                                                             (line  323)
* Python Enhancement Proposals; PEP 475 <17>: Socket Objects.
                                                             (line  395)
* Python Enhancement Proposals; PEP 475 <18>: Socket Objects.
                                                             (line  414)
* Python Enhancement Proposals; PEP 475 <19>: Socket Objects.
                                                             (line  433)
* Python Enhancement Proposals; PEP 475 <20>: Socket Objects.
                                                             (line  475)
* Python Enhancement Proposals; PEP 475 <21>: select --- Waiting for I/O completion.
                                                             (line  152)
* 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   99)
* 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>: Module contents<2>.
                                                             (line  516)
* Python Enhancement Proposals; PEP 475 <28>: Module contents<2>.
                                                             (line  534)
* 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 5 有什麼新功能.
                                                             (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<28>.    (line 1272)
* Python Enhancement Proposals; PEP 479 <4>: Library<32>.    (line   52)
* Python Enhancement Proposals; PEP 479 <5>: Core and Builtins<34>.
                                                             (line   34)
* Python Enhancement Proposals; PEP 479 <6>: Library<40>.    (line   95)
* Python Enhancement Proposals; PEP 479 <7>: Library<54>.    (line   80)
* Python Enhancement Proposals; PEP 479 <8>: Library<67>.    (line  326)
* Python Enhancement Proposals; PEP 479 <9>: Concrete exceptions.
                                                             (line  233)
* Python Enhancement Proposals; PEP 479 <10>: Concrete exceptions.
                                                             (line  235)
* Python Enhancement Proposals; PEP 479 <11>: __future__ --- Future statement definitions.
                                                             (line   93)
* Python Enhancement Proposals; PEP 483: PEP 484 - Type Hints.
                                                             (line   47)
* Python Enhancement Proposals; PEP 483 <1>: typing --- Support for type hints.
                                                             (line   21)
* Python Enhancement Proposals; PEP 484: ast.                (line   17)
* Python Enhancement Proposals; PEP 484 <1>: ast.            (line   20)
* Python Enhancement Proposals; PEP 484 <2>: PEP 560 Core Support for typing module and Generic Types.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <3>: PEP 526 Syntax for variable annotations.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <4>: PEP 484 - Type Hints.
                                                             (line   16)
* Python Enhancement Proposals; PEP 484 <5>: PEP 484 - Type Hints.
                                                             (line   41)
* Python Enhancement Proposals; PEP 484 <6>: Function Annotations.
                                                             (line    8)
* Python Enhancement Proposals; PEP 484 <7>: Emulating generic types.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <8>: Annotated assignment statements.
                                                             (line   45)
* Python Enhancement Proposals; PEP 484 <9>: Function definitions.
                                                             (line  132)
* Python Enhancement Proposals; PEP 484 <10>: typing --- Support for type hints.
                                                             (line   16)
* Python Enhancement Proposals; PEP 484 <11>: typing --- Support for type hints.
                                                             (line   20)
* Python Enhancement Proposals; PEP 484 <12>: NewType.       (line   64)
* Python Enhancement Proposals; PEP 484 <13>: Nominal vs structural subtyping.
                                                             (line    6)
* Python Enhancement Proposals; PEP 484 <14>: Nominal vs structural subtyping.
                                                             (line   14)
* Python Enhancement Proposals; PEP 484 <15>: Classes functions and decorators.
                                                             (line   40)
* Python Enhancement Proposals; PEP 484 <16>: Classes functions and decorators.
                                                             (line   45)
* Python Enhancement Proposals; PEP 484 <17>: Classes functions and decorators.
                                                             (line  134)
* Python Enhancement Proposals; PEP 484 <18>: Classes functions and decorators.
                                                             (line  686)
* Python Enhancement Proposals; PEP 484 <19>: ast Helpers.   (line   16)
* Python Enhancement Proposals; PEP 484 <20>: ast Helpers.   (line   26)
* Python Enhancement Proposals; PEP 484 <21>: Glossary.      (line   61)
* Python Enhancement Proposals; PEP 484 <22>: Glossary.      (line  483)
* Python Enhancement Proposals; PEP 484 <23>: Glossary.      (line 1262)
* Python Enhancement Proposals; PEP 484 <24>: Glossary.      (line 1279)
* Python Enhancement Proposals; PEP 484 <25>: Glossary.      (line 1309)
* 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<82>.    (line   10)
* Python Enhancement Proposals; PEP 485 <3>: Number-theoretic and representation functions.
                                                             (line  135)
* Python Enhancement Proposals; PEP 485 <4>: Classification functions.
                                                             (line   54)
* 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<50>.    (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<3>.
                                                             (line  104)
* Python Enhancement Proposals; PEP 487 <4>: Documentation<34>.
                                                             (line   52)
* Python Enhancement Proposals; PEP 487 <5>: Documentation<41>.
                                                             (line    8)
* Python Enhancement Proposals; PEP 487 <6>: Core and Builtins<52>.
                                                             (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<4>.
                                                             (line   79)
* Python Enhancement Proposals; PEP 488 <3>: Core and Builtins<70>.
                                                             (line   15)
* Python Enhancement Proposals; PEP 488 <4>: Miscellaneous options.
                                                             (line   71)
* Python Enhancement Proposals; PEP 488 <5>: Miscellaneous options.
                                                             (line   73)
* Python Enhancement Proposals; PEP 488 <6>: Miscellaneous options.
                                                             (line   79)
* Python Enhancement Proposals; PEP 488 <7>: Miscellaneous options.
                                                             (line   81)
* Python Enhancement Proposals; PEP 488 <8>: test support --- Utilities for the Python test suite.
                                                             (line  192)
* Python Enhancement Proposals; PEP 488 <9>: 簡介<11>.       (line   65)
* 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 --- Compile Python source files.
                                                             (line   31)
* Python Enhancement Proposals; PEP 488 <13>: distutils util --- Miscellaneous other utility functions.
                                                             (line  132)
* Python Enhancement Proposals; PEP 488 <14>: distutils util --- Miscellaneous other utility functions.
                                                             (line  169)
* 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>: 簡介<11>.       (line   69)
* Python Enhancement Proposals; PEP 489 <4>: importlib machinery -- Importers and path hooks.
                                                             (line   74)
* Python Enhancement Proposals; PEP 489 <5>: importlib machinery -- Importers and path hooks.
                                                             (line  314)
* Python Enhancement Proposals; PEP 489 <6>: importlib machinery -- Importers and path hooks.
                                                             (line  320)
* Python Enhancement Proposals; PEP 489 <7>: The Module's Method Table and Initialization Function.
                                                             (line  129)
* Python Enhancement Proposals; PEP 489 <8>: Building C and C++ Extensions.
                                                             (line   40)
* Python Enhancement Proposals; PEP 489 <9>: Multi-phase initialization.
                                                             (line  107)
* Python Enhancement Proposals; PEP 492: PEP 525 Asynchronous Generators.
                                                             (line    6)
* Python Enhancement Proposals; PEP 492 <1>: New Keywords.   (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<2>.
                                                             (line    7)
* Python Enhancement Proposals; PEP 492 <5>: Changes in the C API<4>.
                                                             (line   25)
* Python Enhancement Proposals; PEP 492 <6>: Core and Builtins<37>.
                                                             (line   99)
* Python Enhancement Proposals; PEP 492 <7>: Library<58>.    (line   36)
* Python Enhancement Proposals; PEP 492 <8>: Library<70>.    (line   16)
* Python Enhancement Proposals; PEP 492 <9>: Core and Builtins<67>.
                                                             (line   14)
* Python Enhancement Proposals; PEP 492 <10>: Awaitable Objects.
                                                             (line   27)
* Python Enhancement Proposals; PEP 492 <11>: Yield expressions.
                                                             (line  104)
* Python Enhancement Proposals; PEP 492 <12>: The async with statement.
                                                             (line   45)
* Python Enhancement Proposals; PEP 492 <13>: Collections Abstract Base Classes.
                                                             (line  247)
* Python Enhancement Proposals; PEP 492 <14>: Code Objects Bit Flags.
                                                             (line   42)
* Python Enhancement Proposals; PEP 492 <15>: Code Objects Bit Flags.
                                                             (line   51)
* Python Enhancement Proposals; PEP 492 <16>: Glossary.      (line  100)
* Python Enhancement Proposals; PEP 492 <17>: Glossary.      (line  133)
* Python Enhancement Proposals; PEP 492 <18>: Glossary.      (line  140)
* Python Enhancement Proposals; PEP 492 <19>: Glossary.      (line  149)
* Python Enhancement Proposals; PEP 492 <20>: Glossary.      (line  161)
* Python Enhancement Proposals; PEP 492 <21>: Glossary.      (line  288)
* Python Enhancement Proposals; PEP 492 <22>: Glossary.      (line  295)
* Python Enhancement Proposals; PEP 493: PEP 493 HTTPS verification migration tools for Python 2 7.
                                                             (line    6)
* Python Enhancement Proposals; PEP 494: What's New In 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<53>.    (line   96)
* 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<55>.
                                                             (line  284)
* Python Enhancement Proposals; PEP 498 <3>: Formatted string literals.
                                                             (line  141)
* Python Enhancement Proposals; PEP 498 <4>: Glossary.       (line  419)
* Python Enhancement Proposals; PEP 5:   PEP 230 Warning Framework.
                                                             (line   66)
* Python Enhancement Proposals; PEP 5 <1>: Is it reasonable to propose incompatible changes to Python?.
                                                             (line   14)
* Python Enhancement Proposals; PEP 506: secrets.            (line   19)
* Python Enhancement Proposals; PEP 506 <1>: Library<60>.    (line   60)
* Python Enhancement Proposals; PEP 506 <2>: secrets --- Generate secure random numbers for managing secrets.
                                                             (line   24)
* Python Enhancement Proposals; PEP 511: Changes in the Python API<3>.
                                                             (line   32)
* Python Enhancement Proposals; PEP 514: Windows<40>.        (line    8)
* Python Enhancement Proposals; PEP 515: PEP 515 Underscores in Numeric Literals.
                                                             (line    6)
* Python Enhancement Proposals; PEP 515 <1>: PEP 515 Underscores in Numeric Literals.
                                                             (line   32)
* Python Enhancement Proposals; PEP 515 <2>: Core and Builtins<51>.
                                                             (line   15)
* Python Enhancement Proposals; PEP 515 <3>: Core and Builtins<51>.
                                                             (line   43)
* Python Enhancement Proposals; PEP 515 <4>: Format Specification Mini-Language.
                                                             (line  111)
* Python Enhancement Proposals; PEP 519: PEP 519 Adding a file system path protocol.
                                                             (line   62)
* Python Enhancement Proposals; PEP 519 <1>: Library<53>.    (line    6)
* Python Enhancement Proposals; PEP 519 <2>: Core and Builtins<54>.
                                                             (line   19)
* Python Enhancement Proposals; PEP 519 <3>: Library<58>.    (line   16)
* Python Enhancement Proposals; PEP 519 <4>: Library<58>.    (line   27)
* Python Enhancement Proposals; PEP 519 <5>: Library<58>.    (line   29)
* Python Enhancement Proposals; PEP 519 <6>: C API<32>.      (line    6)
* Python Enhancement Proposals; PEP 519 <7>: Glossary.       (line 1025)
* Python Enhancement Proposals; PEP 520: PEP 520 Preserving Class Attribute Definition Order.
                                                             (line   17)
* Python Enhancement Proposals; PEP 523: PEP 523 Adding a frame evaluation API to CPython.
                                                             (line   12)
* Python Enhancement Proposals; PEP 523 <1>: PEP 523 Adding a frame evaluation API to CPython.
                                                             (line   26)
* Python Enhancement Proposals; PEP 523 <2>: Tools/Demos<18>.
                                                             (line    7)
* Python Enhancement Proposals; PEP 523 <3>: Tools/Demos<22>.
                                                             (line    7)
* Python Enhancement Proposals; PEP 523 <4>: Core and Builtins<51>.
                                                             (line   83)
* Python Enhancement Proposals; PEP 524: Summary -- Release highlights<2>.
                                                             (line   77)
* Python Enhancement Proposals; PEP 524 <1>: os<3>.          (line   20)
* Python Enhancement Proposals; PEP 524 <2>: os<3>.          (line   25)
* Python Enhancement Proposals; PEP 524 <3>: Library<52>.    (line  150)
* Python Enhancement Proposals; PEP 524 <4>: Library<52>.    (line  154)
* Python Enhancement Proposals; PEP 524 <5>: Random numbers<2>.
                                                             (line   42)
* Python Enhancement Proposals; PEP 525: PEP 525 Asynchronous Generators.
                                                             (line   23)
* Python Enhancement Proposals; PEP 525 <1>: Core and Builtins<51>.
                                                             (line   49)
* Python Enhancement Proposals; PEP 525 <2>: Yield expressions.
                                                             (line  102)
* Python Enhancement Proposals; PEP 525 <3>: Collections Abstract Base Classes.
                                                             (line  247)
* Python Enhancement Proposals; PEP 525 <4>: sys --- System-specific parameters and functions.
                                                             (line  814)
* Python Enhancement Proposals; PEP 525 <5>: sys --- System-specific parameters and functions.
                                                             (line 1421)
* Python Enhancement Proposals; PEP 525 <6>: Code Objects Bit Flags.
                                                             (line   60)
* Python Enhancement Proposals; PEP 525 <7>: Glossary.       (line  134)
* Python Enhancement Proposals; PEP 526: ast.                (line   18)
* Python Enhancement Proposals; PEP 526 <1>: PEP 563 Postponed Evaluation of Annotations.
                                                             (line    8)
* Python Enhancement Proposals; PEP 526 <2>: PEP 526 Syntax for variable annotations.
                                                             (line   30)
* Python Enhancement Proposals; PEP 526 <3>: typing<2>.      (line   23)
* Python Enhancement Proposals; PEP 526 <4>: Core and Builtins<51>.
                                                             (line   51)
* Python Enhancement Proposals; PEP 526 <5>: Annotated assignment statements.
                                                             (line   39)
* Python Enhancement Proposals; PEP 526 <6>: Function definitions.
                                                             (line  136)
* Python Enhancement Proposals; PEP 526 <7>: typing --- Support for type hints.
                                                             (line   17)
* Python Enhancement Proposals; PEP 526 <8>: Classes functions and decorators.
                                                             (line  534)
* Python Enhancement Proposals; PEP 526 <9>: Classes functions and decorators.
                                                             (line  571)
* Python Enhancement Proposals; PEP 526 <10>: Classes functions and decorators.
                                                             (line  905)
* Python Enhancement Proposals; PEP 526 <11>: dataclasses --- Data Classes.
                                                             (line   16)
* Python Enhancement Proposals; PEP 526 <12>: Class variables.
                                                             (line    8)
* Python Enhancement Proposals; PEP 526 <13>: ast Helpers.   (line   16)
* Python Enhancement Proposals; PEP 526 <14>: Glossary.      (line   61)
* Python Enhancement Proposals; PEP 526 <15>: Glossary.      (line 1309)
* Python Enhancement Proposals; PEP 528: PEP 528 Change Windows console encoding to UTF-8.
                                                             (line   17)
* Python Enhancement Proposals; PEP 528 <1>: UTF-8 mode.     (line   42)
* Python Enhancement Proposals; PEP 528 <2>: Global configuration variables.
                                                             (line  105)
* Python Enhancement Proposals; PEP 529: Changes in the Python API.
                                                             (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>: Library<23>.    (line   22)
* Python Enhancement Proposals; PEP 529 <3>: Windows<35>.    (line   14)
* Python Enhancement Proposals; PEP 529 <4>: Environment variables.
                                                             (line  306)
* Python Enhancement Proposals; PEP 529 <5>: UTF-8 mode.     (line   45)
* Python Enhancement Proposals; PEP 529 <6>: Files and Directories.
                                                             (line  288)
* Python Enhancement Proposals; PEP 529 <7>: sys --- System-specific parameters and functions.
                                                             (line  664)
* Python Enhancement Proposals; PEP 529 <8>: sys --- System-specific parameters and functions.
                                                             (line 1460)
* Python Enhancement Proposals; PEP 529 <9>: File System Encoding.
                                                             (line    9)
* Python Enhancement Proposals; PEP 529 <10>: Global configuration variables.
                                                             (line   93)
* 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<51>.
                                                             (line  145)
* Python Enhancement Proposals; PEP 530 <3>: Displays for lists sets and dictionaries.
                                                             (line   53)
* 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<24>.
                                                             (line   68)
* Python Enhancement Proposals; PEP 538 <5>: Documentation<25>.
                                                             (line    6)
* Python Enhancement Proposals; PEP 538 <6>: Core and Builtins<38>.
                                                             (line  135)
* Python Enhancement Proposals; PEP 538 <7>: Environment variables.
                                                             (line  375)
* Python Enhancement Proposals; PEP 538 <8>: 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<21>.      (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<35>.
                                                             (line   63)
* Python Enhancement Proposals; PEP 540 <3>: Environment variables.
                                                             (line  444)
* Python Enhancement Proposals; PEP 540 <4>: Python Configuration.
                                                             (line   13)
* Python Enhancement Proposals; PEP 544: typing.             (line   32)
* Python Enhancement Proposals; PEP 544 <1>: typing --- Support for type hints.
                                                             (line   17)
* Python Enhancement Proposals; PEP 544 <2>: Nominal vs structural subtyping.
                                                             (line   23)
* Python Enhancement Proposals; PEP 544 <3>: Classes functions and decorators.
                                                             (line   92)
* Python Enhancement Proposals; PEP 545: PEP 545 Python Documentation Translations.
                                                             (line    6)
* Python Enhancement Proposals; PEP 545 <1>: PEP 545 Python Documentation Translations.
                                                             (line   20)
* Python Enhancement Proposals; PEP 552: PEP 552 Hash-based pyc Files.
                                                             (line   15)
* Python Enhancement Proposals; PEP 552 <1>: PEP 552 Hash-based pyc Files.
                                                             (line   35)
* Python Enhancement Proposals; PEP 552 <2>: Library<28>.    (line  798)
* Python Enhancement Proposals; PEP 552 <3>: Core and Builtins<35>.
                                                             (line   75)
* Python Enhancement Proposals; PEP 552 <4>: 簡介<11>.       (line   73)
* Python Enhancement Proposals; PEP 552 <5>: py_compile --- Compile Python source files.
                                                             (line   81)
* Python Enhancement Proposals; PEP 552 <6>: PyConfig.       (line  137)
* Python Enhancement Proposals; PEP 553: PEP 553 Built-in breakpoint.
                                                             (line   20)
* Python Enhancement Proposals; PEP 553 <1>: Core and Builtins<37>.
                                                             (line   73)
* Python Enhancement Proposals; PEP 557: dataclasses.        (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.          (line   12)
* Python Enhancement Proposals; PEP 560 <2>: Core and Builtins<35>.
                                                             (line   66)
* Python Enhancement Proposals; PEP 560 <3>: Resolving MRO entries.
                                                             (line   15)
* Python Enhancement Proposals; PEP 560 <4>: Emulating generic types.
                                                             (line   22)
* Python Enhancement Proposals; PEP 560 <5>: Dynamic Type Creation.
                                                             (line   59)
* Python Enhancement Proposals; PEP 560 <6>: Dynamic Type Creation.
                                                             (line   73)
* Python Enhancement Proposals; PEP 562: PEP 562 Customization of Access to Module Attributes.
                                                             (line   16)
* Python Enhancement Proposals; PEP 562 <1>: Library<35>.    (line   63)
* Python Enhancement Proposals; PEP 562 <2>: Core and Builtins<35>.
                                                             (line   69)
* Python Enhancement Proposals; PEP 562 <3>: Customizing module attribute access.
                                                             (line   52)
* Python Enhancement Proposals; PEP 563: PEP 563 Postponed Evaluation of Annotations.
                                                             (line   51)
* Python Enhancement Proposals; PEP 563 <1>: Future statements.
                                                             (line   34)
* Python Enhancement Proposals; PEP 563 <2>: Function definitions.
                                                             (line  141)
* Python Enhancement Proposals; PEP 563 <3>: __future__ --- Future statement definitions.
                                                             (line   97)
* 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<2>.        (line    6)
* Python Enhancement Proposals; PEP 564 <3>: Library<37>.    (line  300)
* Python Enhancement Proposals; PEP 565: PEP 565 Show DeprecationWarning in __main__.
                                                             (line   41)
* Python Enhancement Proposals; PEP 566: Using importlib metadata.
                                                             (line   24)
* Python Enhancement Proposals; PEP 566 <1>: Distributions.  (line   28)
* Python Enhancement Proposals; PEP 567: contextvars.        (line   20)
* Python Enhancement Proposals; PEP 567 <1>: asyncio<2>.     (line   19)
* Python Enhancement Proposals; PEP 567 <2>: Documentation<24>.
                                                             (line   86)
* Python Enhancement Proposals; PEP 567 <3>: Documentation<26>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 567 <4>: Core and Builtins<34>.
                                                             (line   63)
* Python Enhancement Proposals; PEP 567 <5>: contextvars --- Context Variables.
                                                             (line   18)
* Python Enhancement Proposals; PEP 567 <6>: Scheduling callbacks.
                                                             (line   31)
* Python Enhancement Proposals; PEP 567 <7>: Scheduling delayed callbacks.
                                                             (line   30)
* Python Enhancement Proposals; PEP 567 <8>: Scheduling delayed callbacks.
                                                             (line   48)
* Python Enhancement Proposals; PEP 567 <9>: Future Object.  (line   99)
* Python Enhancement Proposals; PEP 570: Positional-only parameters.
                                                             (line   70)
* Python Enhancement Proposals; PEP 570 <1>: Changes in the Python API.
                                                             (line  159)
* Python Enhancement Proposals; PEP 570 <2>: Core and Builtins<25>.
                                                             (line   36)
* Python Enhancement Proposals; PEP 570 <3>: Function definitions.
                                                             (line   92)
* Python Enhancement Proposals; PEP 572: Assignment expressions.
                                                             (line   41)
* Python Enhancement Proposals; PEP 572 <1>: CPython bytecode changes.
                                                             (line   28)
* Python Enhancement Proposals; PEP 572 <2>: Documentation<11>.
                                                             (line   13)
* Python Enhancement Proposals; PEP 572 <3>: Core and Builtins<21>.
                                                             (line   18)
* Python Enhancement Proposals; PEP 572 <4>: Core and Builtins<28>.
                                                             (line   92)
* Python Enhancement Proposals; PEP 572 <5>: Dictionary displays.
                                                             (line   47)
* Python Enhancement Proposals; PEP 572 <6>: Assignment expressions<2>.
                                                             (line   22)
* Python Enhancement Proposals; PEP 572 <7>: Why can't I use an assignment in an expression?.
                                                             (line   14)
* 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>: Example<4>.     (line   63)
* Python Enhancement Proposals; PEP 578: PEP 578 Python Runtime Audit Hooks.
                                                             (line   12)
* Python Enhancement Proposals; PEP 578 <1>: Audit events table.
                                                             (line    8)
* Python Enhancement Proposals; PEP 578 <2>: sys --- System-specific parameters and functions.
                                                             (line   44)
* Python Enhancement Proposals; PEP 578 <3>: 系統函式.       (line  151)
* Python Enhancement Proposals; PEP 586: typing.             (line   18)
* Python Enhancement Proposals; PEP 586 <1>: typing --- Support for type hints.
                                                             (line   17)
* Python Enhancement Proposals; PEP 586 <2>: Classes functions and decorators.
                                                             (line  896)
* Python Enhancement Proposals; PEP 587: PEP 587 Python Initialization Configuration.
                                                             (line    6)
* Python Enhancement Proposals; PEP 587 <1>: PEP 587 Python Initialization Configuration.
                                                             (line   83)
* Python Enhancement Proposals; PEP 587 <2>: Core and Builtins<20>.
                                                             (line   12)
* Python Enhancement Proposals; PEP 587 <3>: C API<12>.      (line    6)
* Python Enhancement Proposals; PEP 587 <4>: Python Initialization Configuration.
                                                             (line   81)
* Python Enhancement Proposals; PEP 589: typing.             (line    8)
* Python Enhancement Proposals; PEP 589 <1>: typing --- Support for type hints.
                                                             (line   17)
* Python Enhancement Proposals; PEP 589 <2>: Classes functions and decorators.
                                                             (line  590)
* Python Enhancement Proposals; PEP 590: Vectorcall a fast calling protocol for CPython.
                                                             (line   14)
* Python Enhancement Proposals; PEP 590 <1>: C API<12>.      (line   17)
* Python Enhancement Proposals; PEP 591: typing.             (line   25)
* Python Enhancement Proposals; PEP 591 <1>: typing --- Support for type hints.
                                                             (line   17)
* Python Enhancement Proposals; PEP 591 <2>: Classes functions and decorators.
                                                             (line  709)
* Python Enhancement Proposals; PEP 591 <3>: Classes functions and decorators.
                                                             (line  943)
* Python Enhancement Proposals; PEP 6:   How does the Python version numbering scheme work?.
                                                             (line    9)
* Python Enhancement Proposals; PEP 602: Python穩定性如何.   (line    8)
* Python Enhancement Proposals; PEP 623: Documentation<3>.   (line   19)
* Python Enhancement Proposals; PEP 623 <1>: Unicode Objects.
                                                             (line   33)
* Python Enhancement Proposals; PEP 628: cmath.              (line    7)
* Python Enhancement Proposals; PEP 628 <1>: math<3>.        (line    7)
* Python Enhancement Proposals; PEP 628 <2>: Library<53>.    (line   32)
* Python Enhancement Proposals; PEP 7:   Build and C API Changes<2>.
                                                             (line    9)
* Python Enhancement Proposals; PEP 7 <1>: Coding standards. (line    7)
* Python Enhancement Proposals; PEP 7 <2>: Useful macros.    (line   87)
* Python Enhancement Proposals; PEP 7 <3>: Useful macros.    (line  105)
* Python Enhancement Proposals; PEP 8:   Library Changes.    (line   26)
* Python Enhancement Proposals; PEP 8 <1>: Library<37>.      (line  125)
* Python Enhancement Proposals; PEP 8 <2>: IDLE<53>.         (line   81)
* Python Enhancement Proposals; PEP 8 <3>: Intermezzo Coding Style.
                                                             (line   13)
* Python Enhancement Proposals; PEP 8 <4>: Editors and IDEs. (line    7)
* Python Enhancement Proposals; PEP 8 <5>: Value comparisons.
                                                             (line   61)
* Python Enhancement Proposals; PEP 8 <6>: Using real Argument Clinic converters instead of "legacy converters".
                                                             (line   50)
* Python Enhancement Proposals; PEP 8 <7>: Are there coding standards or a style guide for Python programs?.
                                                             (line    7)
* Python Enhancement Proposals; PEP 8 <8>: How do I keep editors from inserting tabs into my Python source?.
                                                             (line    6)
* Python Package Index (PyPI):           Installing the tools.
                                                             (line   26)
* PYTHON*:                               Other Improvements<2>.
                                                             (line    9)
* PYTHON* <1>:                           Interface options.  (line   80)
* PYTHON* <2>:                           Interface options.  (line  139)
* PYTHON* <3>:                           Miscellaneous options.
                                                             (line   42)
* PYTHON* <4>:                           Miscellaneous options.
                                                             (line   60)
* PYTHON* <5>:                           Global configuration variables.
                                                             (line   56)
* PYTHONASYNCIODEBUG:                    Enabling debug mode.
                                                             (line   10)
* PYTHONASYNCIODEBUG <1>:                Debug Mode.         (line   11)
* PYTHONBREAKPOINT:                      PEP 553 Built-in breakpoint.
                                                             (line   13)
* PYTHONBREAKPOINT <1>:                  sys --- System-specific parameters and functions.
                                                             (line  202)
* PYTHONBREAKPOINT <2>:                  sys --- System-specific parameters and functions.
                                                             (line  216)
* PYTHONBREAKPOINT <3>:                  sys --- System-specific parameters and functions.
                                                             (line  220)
* PYTHONCASEOK:                          PEP 235 Importing Modules on Case-Insensitive Platforms.
                                                             (line   17)
* PYTHONCOERCECLOCALE:                   PEP 538 Legacy C Locale Coercion.
                                                             (line   13)
* PYTHONCOERCECLOCALE <1>:               Environment variables.
                                                             (line  437)
* PYTHONCOERCECLOCALE <2>:               Python Configuration.
                                                             (line   15)
* PYTHONDEBUG:                           Miscellaneous options.
                                                             (line   38)
* PYTHONDEBUG <1>:                       Global configuration variables.
                                                             (line   28)
* PYTHONDEVMODE:                         Development Runtime Mode -X dev.
                                                             (line    6)
* PYTHONDEVMODE <1>:                     test support script_helper --- Utilities for the Python execution tests.
                                                             (line  103)
* PYTHONDOCS:                            pydoc --- Documentation generator and online help system.
                                                             (line   85)
* PYTHONDONTWRITEBYTECODE:               Interpreter Changes<2>.
                                                             (line   16)
* PYTHONDONTWRITEBYTECODE <1>:           New and Improved Modules<2>.
                                                             (line  625)
* PYTHONDONTWRITEBYTECODE <2>:           Miscellaneous options.
                                                             (line   19)
* PYTHONDONTWRITEBYTECODE <3>:           sys --- System-specific parameters and functions.
                                                             (line  285)
* PYTHONDONTWRITEBYTECODE <4>:           Global configuration variables.
                                                             (line   36)
* PYTHONDONTWRITEBYTECODE <5>:           How do I create a pyc file?.
                                                             (line   21)
* PYTHONDUMPREFS:                        Debug build uses the same ABI as release build.
                                                             (line   14)
* PYTHONDUMPREFS <1>:                    Build<15>.          (line   54)
* PYTHONDUMPREFS <2>:                    PyObject Slots.     (line   24)
* PYTHONFAULTHANDLER:                    faulthandler<3>.    (line   11)
* PYTHONFAULTHANDLER <1>:                faulthandler --- Dump the Python traceback.
                                                             (line   14)
* PYTHONHASHSEED:                        Builtin functions and types.
                                                             (line   17)
* PYTHONHASHSEED <1>:                    Porting Python code.
                                                             (line    6)
* PYTHONHASHSEED <2>:                    Core and Builtins<35>.
                                                             (line   30)
* PYTHONHASHSEED <3>:                    Miscellaneous options.
                                                             (line   92)
* PYTHONHASHSEED <4>:                    Miscellaneous options.
                                                             (line  108)
* PYTHONHASHSEED <5>:                    Environment variables.
                                                             (line  129)
* PYTHONHASHSEED <6>:                    Basic customization.
                                                             (line  298)
* PYTHONHASHSEED <7>:                    Global configuration variables.
                                                             (line   48)
* PYTHONHASHSEED <8>:                    Global configuration variables.
                                                             (line   51)
* PYTHONHOME:                            Summary -- Release highlights<2>.
                                                             (line  107)
* PYTHONHOME <1>:                        Miscellaneous options.
                                                             (line   43)
* PYTHONHOME <2>:                        Environment variables.
                                                             (line   19)
* PYTHONHOME <3>:                        Environment variables.
                                                             (line   21)
* PYTHONHOME <4>:                        Environment variables.
                                                             (line   38)
* PYTHONHOME <5>:                        Finding modules.    (line   50)
* PYTHONHOME <6>:                        Finding modules.    (line   68)
* PYTHONHOME <7>:                        Finding modules.    (line  102)
* PYTHONHOME <8>:                        test support script_helper --- Utilities for the Python execution tests.
                                                             (line   24)
* PYTHONHOME <9>:                        嵌入式Python.       (line   38)
* PYTHONHOME <10>:                       嵌入式Python.       (line   44)
* PYTHONHOME <11>:                       Global configuration variables.
                                                             (line   57)
* PYTHONHOME <12>:                       Process-wide parameters.
                                                             (line  269)
* PYTHONHOME <13>:                       Process-wide parameters.
                                                             (line  283)
* PYTHONHOME <14>:                       PyConfig.           (line  197)
* PYTHONHOME <15>:                       Modifying Python's Search Path.
                                                             (line   60)
* PYTHONHOME <16>:                       Modifying Python's Search Path.
                                                             (line   62)
* Pythonic:                              Glossary.           (line 1081)
* PYTHONINSPECT:                         Other Changes and Fixes<2>.
                                                             (line   13)
* PYTHONINSPECT <1>:                     Miscellaneous options.
                                                             (line   53)
* PYTHONINSPECT <2>:                     Global configuration variables.
                                                             (line   68)
* PYTHONIOENCODING:                      Other Improvements<2>.
                                                             (line   75)
* PYTHONIOENCODING <1>:                  Interpreter Changes<2>.
                                                             (line   23)
* PYTHONIOENCODING <2>:                  Environment variables.
                                                             (line  358)
* PYTHONIOENCODING <3>:                  Environment variables.
                                                             (line  425)
* PYTHONIOENCODING <4>:                  sys --- System-specific parameters and functions.
                                                             (line 1502)
* PYTHONIOENCODING <5>:                  Process-wide parameters.
                                                             (line   14)
* PYTHONIOENCODING <6>:                  Process-wide parameters.
                                                             (line   18)
* PYTHONLEGACYWINDOWSFSENCODING:         PEP 529 Change Windows filesystem encoding to UTF-8.
                                                             (line   18)
* PYTHONLEGACYWINDOWSFSENCODING <1>:     sys --- System-specific parameters and functions.
                                                             (line 1454)
* PYTHONLEGACYWINDOWSFSENCODING <2>:     Global configuration variables.
                                                             (line   90)
* PYTHONLEGACYWINDOWSSTDIO:              PEP 528 Change Windows console encoding to UTF-8.
                                                             (line   12)
* PYTHONLEGACYWINDOWSSTDIO <1>:          Environment variables.
                                                             (line  156)
* PYTHONLEGACYWINDOWSSTDIO <2>:          sys --- System-specific parameters and functions.
                                                             (line 1506)
* PYTHONLEGACYWINDOWSSTDIO <3>:          Global configuration variables.
                                                             (line  102)
* PYTHONMALLOC:                          PYTHONMALLOC environment variable.
                                                             (line    6)
* PYTHONMALLOC <1>:                      Changes in the C API<3>.
                                                             (line    9)
* PYTHONMALLOC <2>:                      Core and Builtins<55>.
                                                             (line   91)
* PYTHONMALLOC <3>:                      Environment variables.
                                                             (line  286)
* PYTHONMALLOC <4>:                      總覽<2>.            (line   75)
* PYTHONMALLOC <5>:                      Default Memory Allocators.
                                                             (line   26)
* PYTHONMALLOC <6>:                      Customize Memory Allocators.
                                                             (line  129)
* PYTHONMALLOCSTATS:                     Core and Builtins<55>.
                                                             (line   97)
* PYTHONMALLOCSTATS <1>:                 總覽<2>.            (line   78)
* PYTHONNOUSERSITE:                      PEP 370 Per-user site-packages Directory.
                                                             (line   30)
* PYTHONNOUSERSITE <1>:                  Module contents<3>. (line   15)
* PYTHONNOUSERSITE <2>:                  Global configuration variables.
                                                             (line  124)
* PYTHONOPTIMIZE:                        Miscellaneous options.
                                                             (line   71)
* PYTHONOPTIMIZE <1>:                    Global configuration variables.
                                                             (line  129)
* PYTHONPATH:                            Changes in 'python' Command Behavior<2>.
                                                             (line    8)
* PYTHONPATH <1>:                        Changes in 'python' Command Behavior<2>.
                                                             (line    9)
* PYTHONPATH <2>:                        The Module Search Path.
                                                             (line   15)
* PYTHONPATH <3>:                        Standard Modules.   (line   34)
* PYTHONPATH <4>:                        Standard Modules.   (line   35)
* PYTHONPATH <5>:                        Miscellaneous options.
                                                             (line   42)
* PYTHONPATH <6>:                        Environment variables.
                                                             (line   32)
* PYTHONPATH <7>:                        Environment variables.
                                                             (line   39)
* PYTHONPATH <8>:                        Environment variables.
                                                             (line   42)
* PYTHONPATH <9>:                        Excursus Setting environment variables.
                                                             (line   38)
* PYTHONPATH <10>:                       Finding modules.    (line   36)
* PYTHONPATH <11>:                       Finding modules.    (line   59)
* PYTHONPATH <12>:                       Finding modules.    (line  102)
* PYTHONPATH <13>:                       設定.               (line    6)
* PYTHONPATH <14>:                       Path entry finders. (line    6)
* PYTHONPATH <15>:                       Installing your CGI script on a Unix system.
                                                             (line   29)
* PYTHONPATH <16>:                       test support script_helper --- Utilities for the Python execution tests.
                                                             (line   25)
* PYTHONPATH <17>:                       sys --- System-specific parameters and functions.
                                                             (line 1063)
* PYTHONPATH <18>:                       sys --- System-specific parameters and functions.
                                                             (line 1073)
* PYTHONPATH <19>:                       Building C and C++ Extensions.
                                                             (line    9)
* PYTHONPATH <20>:                       嵌入式Python.       (line   39)
* PYTHONPATH <21>:                       嵌入式Python.       (line   44)
* PYTHONPATH <22>:                       Global configuration variables.
                                                             (line   56)
* PYTHONPATH <23>:                       PyConfig.           (line  252)
* PYTHONPATH <24>:                       Modifying Python's Search Path.
                                                             (line   67)
* PYTHONPATH <25>:                       Modifying Python's Search Path.
                                                             (line   68)
* PYTHONPROFILEIMPORTTIME:               Other Language Changes<2>.
                                                             (line   47)
* PYTHONPROFILEIMPORTTIME <1>:           Core and Builtins<37>.
                                                             (line   67)
* PYTHONPROFILEIMPORTTIME <2>:           Miscellaneous options.
                                                             (line  221)
* PYTHONPYCACHEPREFIX:                   Parallel filesystem cache for compiled bytecode files.
                                                             (line    6)
* PYTHONPYCACHEPREFIX <1>:               Core and Builtins<28>.
                                                             (line  402)
* PYTHONPYCACHEPREFIX <2>:               Miscellaneous options.
                                                             (line  255)
* PYTHONPYCACHEPREFIX <3>:               sys --- System-specific parameters and functions.
                                                             (line  303)
* PYTHONSHOWALLOCCOUNT:                  Two new environment variables for debug mode.
                                                             (line   11)
* PYTHONSHOWREFCOUNT:                    Two new environment variables for debug mode.
                                                             (line    7)
* PYTHONSTARTUP:                         sys<6>.             (line   17)
* PYTHONSTARTUP <1>:                     sys<6>.             (line   21)
* PYTHONSTARTUP <2>:                     IDLE<27>.           (line  176)
* PYTHONSTARTUP <3>:                     IDLE<31>.           (line    9)
* PYTHONSTARTUP <4>:                     IDLE<37>.           (line    9)
* PYTHONSTARTUP <5>:                     The Interactive Startup File.
                                                             (line    8)
* PYTHONSTARTUP <6>:                     Miscellaneous options.
                                                             (line   50)
* PYTHONSTARTUP <7>:                     Example.            (line   10)
* PYTHONSTARTUP <8>:                     Startup and code execution.
                                                             (line    7)
* PYTHONSTARTUP <9>:                     sys --- System-specific parameters and functions.
                                                             (line  959)
* PYTHONSTARTUP <10>:                    Readline configuration.
                                                             (line   12)
* PYTHONTRACEMALLOC:                     tracemalloc --- Trace memory allocations.
                                                             (line   25)
* PYTHONTRACEMALLOC <1>:                 tracemalloc --- Trace memory allocations.
                                                             (line   32)
* PYTHONTRACEMALLOC <2>:                 Functions<9>.       (line   68)
* PYTHONUNBUFFERED:                      Miscellaneous options.
                                                             (line  138)
* PYTHONUNBUFFERED <1>:                  Global configuration variables.
                                                             (line  145)
* PYTHONUSERBASE:                        PEP 370 Per-user site-packages Directory.
                                                             (line   23)
* PYTHONUSERBASE <1>:                    Module contents<3>. (line   39)
* PYTHONUSERBASE <2>:                    Module contents<3>. (line   65)
* PYTHONUSERSITE:                        test support script_helper --- Utilities for the Python execution tests.
                                                             (line   25)
* PYTHONUTF8:                            PEP 540 Forced UTF-8 Runtime Mode.
                                                             (line    6)
* PYTHONUTF8 <1>:                        Miscellaneous options.
                                                             (line  250)
* PYTHONUTF8 <2>:                        Environment variables.
                                                             (line  368)
* PYTHONUTF8 <3>:                        UTF-8 mode.         (line   17)
* PYTHONUTF8 <4>:                        sys --- System-specific parameters and functions.
                                                             (line 1504)
* PYTHONUTF8 <5>:                        Python Configuration.
                                                             (line   14)
* PYTHONVERBOSE:                         Miscellaneous options.
                                                             (line  149)
* PYTHONVERBOSE <1>:                     Global configuration variables.
                                                             (line  156)
* PYTHONWARNINGS:                        warnings.           (line   21)
* PYTHONWARNINGS <1>:                    Other Language Changes<7>.
                                                             (line  158)
* PYTHONWARNINGS <2>:                    Changes to the Handling of Deprecation Warnings.
                                                             (line   25)
* PYTHONWARNINGS <3>:                    Interpreter Changes.
                                                             (line    6)
* PYTHONWARNINGS <4>:                    Miscellaneous options.
                                                             (line  167)
* PYTHONWARNINGS <5>:                    Describing Warning Filters.
                                                             (line    7)
* PYTHONWARNINGS <6>:                    Describing Warning Filters.
                                                             (line   21)
* PYTHONWARNINGS <7>:                    Default Warning Filter.
                                                             (line    7)
* python_branch() (於 platform 模組中):  Cross Platform.     (line   87)
* python_build() (於 platform 模組中):   Cross Platform.     (line   77)
* python_compiler() (於 platform 模組中): Cross Platform.    (line   82)
* PYTHON_DOM:                            Module Contents<4>. (line   23)
* python_implementation() (於 platform 模組中): Cross Platform.
                                                             (line   91)
* python_is_optimized() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  203)
* python_revision() (於 platform 模組中): Cross Platform.    (line   96)
* python_version() (於 platform 模組中): Cross Platform.     (line  101)
* python_version_tuple() (於 platform 模組中): Cross Platform.
                                                             (line  108)
* PyThreadState:                         Thread State and the Global Interpreter Lock.
                                                             (line   23)
* PyThreadState <1>:                     Thread State and the Global Interpreter Lock.
                                                             (line   23)
* PyThreadState (C 型態):                High-level API.     (line   21)
* PyThreadState_Clear (C 函式):          Low-level API.      (line   42)
* PyThreadState_Delete (C 函式):         Low-level API.      (line   47)
* PyThreadState_Get (C 函式):            High-level API.     (line   75)
* PyThreadState_GetDict (C 函式):        Low-level API.      (line   75)
* PyThreadState_New (C 函式):            Low-level API.      (line   35)
* PyThreadState_Next (C 函式):           Advanced Debugger Support.
                                                             (line   32)
* PyThreadState_SetAsyncExc (C 函式):    Low-level API.      (line   84)
* PyThreadState_Swap (C 函式):           High-level API.     (line   81)
* PyThread_create_key (C 函式):          Thread Local Storage TLS API.
                                                             (line   18)
* PyThread_delete_key (C 函式):          Thread Local Storage TLS API.
                                                             (line   20)
* PyThread_delete_key_value (C 函式):    Thread Local Storage TLS API.
                                                             (line   26)
* PyThread_get_key_value (C 函式):       Thread Local Storage TLS API.
                                                             (line   24)
* PyThread_ReInitTLS (C 函式):           Thread Local Storage TLS API.
                                                             (line   28)
* PyThread_set_key_value (C 函式):       Thread Local Storage TLS API.
                                                             (line   22)
* PyThread_tss_alloc (C 函式):           Dynamic Allocation. (line   11)
* PyThread_tss_create (C 函式):          Methods<4>.         (line   16)
* PyThread_tss_delete (C 函式):          Methods<4>.         (line   24)
* PyThread_tss_free (C 函式):            Dynamic Allocation. (line   17)
* PyThread_tss_get (C 函式):             Methods<4>.         (line   39)
* PyThread_tss_is_created (C 函式):      Methods<4>.         (line   11)
* PyThread_tss_set (C 函式):             Methods<4>.         (line   33)
* PyTimeZone_FromOffset (C 函式):        DateTime 物件.      (line  118)
* PyTimeZone_FromOffsetAndName (C 函式): DateTime 物件.      (line  126)
* PyTime_Check (C 函式):                 DateTime 物件.      (line   45)
* PyTime_CheckExact (C 函式):            DateTime 物件.      (line   50)
* PyTime_FromTime (C 函式):              DateTime 物件.      (line   97)
* PyTime_FromTimeAndFold (C 函式):       DateTime 物件.      (line  102)
* PyTraceMalloc_Track (C 函式):          tracemalloc C API.  (line    8)
* PyTraceMalloc_Untrack (C 函式):        tracemalloc C API.  (line   20)
* PyTrace_CALL (C 變數):                 Profiling and Tracing.
                                                             (line   61)
* PyTrace_C_CALL (C 變數):               Profiling and Tracing.
                                                             (line   93)
* PyTrace_C_EXCEPTION (C 變數):          Profiling and Tracing.
                                                             (line   98)
* PyTrace_C_RETURN (C 變數):             Profiling and Tracing.
                                                             (line  103)
* PyTrace_EXCEPTION (C 變數):            Profiling and Tracing.
                                                             (line   69)
* PyTrace_LINE (C 變數):                 Profiling and Tracing.
                                                             (line   81)
* PyTrace_OPCODE (C 變數):               Profiling and Tracing.
                                                             (line  108)
* PyTrace_RETURN (C 變數):               Profiling and Tracing.
                                                             (line   88)
* PyTupleObject (C 型態):                元組（Tuple）物件.  (line    6)
* PyTuple_Check (C 函式):                元組（Tuple）物件.  (line   17)
* PyTuple_CheckExact (C 函式):           元組（Tuple）物件.  (line   22)
* PyTuple_ClearFreeList (C 函式):        元組（Tuple）物件.  (line  103)
* PyTuple_GetItem (C 函式):              元組（Tuple）物件.  (line   48)
* PyTuple_GetSlice (C 函式):             元組（Tuple）物件.  (line   57)
* PyTuple_GET_ITEM (C 函式):             元組（Tuple）物件.  (line   53)
* PyTuple_GET_SIZE (C 函式):             元組（Tuple）物件.  (line   43)
* PyTuple_New (C 函式):                  元組（Tuple）物件.  (line   27)
* PyTuple_Pack (C 函式):                 元組（Tuple）物件.  (line   31)
* PyTuple_SetItem (C 函式):              元組（Tuple）物件.  (line   65)
* PyTuple_SetItem():                     Reference Count Details.
                                                             (line   26)
* PyTuple_SET_ITEM (C 函式):             元組（Tuple）物件.  (line   76)
* PyTuple_Size (C 函式):                 元組（Tuple）物件.  (line   38)
* PyTuple_Type (C 變數):                 元組（Tuple）物件.  (line   11)
* PyTypeObject (C 型態):                 Type Objects<2>.    (line    6)
* PyTypeObject.tp_alloc (C 成員函數):    PyTypeObject Slots. (line 1170)
* PyTypeObject.tp_allocs (C 成員函數):   PyTypeObject Slots. (line 1392)
* PyTypeObject.tp_as_async (C 成員函數): PyTypeObject Slots. (line  239)
* PyTypeObject.tp_as_buffer (C 成員函數): PyTypeObject Slots.
                                                             (line  439)
* PyTypeObject.tp_as_mapping (C 成員函數): PyTypeObject Slots.
                                                             (line  301)
* PyTypeObject.tp_as_number (C 成員函數): PyTypeObject Slots.
                                                             (line  279)
* PyTypeObject.tp_as_sequence (C 成員函數): PyTypeObject Slots.
                                                             (line  290)
* PyTypeObject.tp_base (C 成員函數):     PyTypeObject Slots. (line  983)
* PyTypeObject.tp_bases (C 成員函數):    PyTypeObject Slots. (line 1281)
* PyTypeObject.tp_basicsize (C 成員函數): PyTypeObject Slots.
                                                             (line   47)
* PyTypeObject.tp_cache (C 成員函數):    PyTypeObject Slots. (line 1303)
* PyTypeObject.tp_call (C 成員函數):     PyTypeObject Slots. (line  349)
* PyTypeObject.tp_clear (C 成員函數):    PyTypeObject Slots. (line  720)
* PyTypeObject.tp_dealloc (C 成員函數):  PyTypeObject Slots. (line   99)
* PyTypeObject.tp_del (C 成員函數):      PyTypeObject Slots. (line 1328)
* PyTypeObject.tp_descr_get (C 成員函數): PyTypeObject Slots.
                                                             (line 1040)
* PyTypeObject.tp_descr_set (C 成員函數): PyTypeObject Slots.
                                                             (line 1052)
* PyTypeObject.tp_dict (C 成員函數):     PyTypeObject Slots. (line 1015)
* PyTypeObject.tp_dictoffset (C 成員函數): PyTypeObject Slots.
                                                             (line 1067)
* PyTypeObject.tp_doc (C 成員函數):      PyTypeObject Slots. (line  648)
* PyTypeObject.tp_finalize (C 成員函數): PyTypeObject Slots. (line 1340)
* PyTypeObject.tp_flags (C 成員函數):    PyTypeObject Slots. (line  450)
* PyTypeObject.tp_free (C 成員函數):     PyTypeObject Slots. (line 1229)
* PyTypeObject.tp_frees (C 成員函數):    PyTypeObject Slots. (line 1396)
* PyTypeObject.tp_getattr (C 成員函數):  PyTypeObject Slots. (line  200)
* PyTypeObject.tp_getattro (C 成員函數): PyTypeObject Slots. (line  387)
* PyTypeObject.tp_getset (C 成員函數):   PyTypeObject Slots. (line  968)
* PyTypeObject.tp_hash (C 成員函數):     PyTypeObject Slots. (line  312)
* PyTypeObject.tp_init (C 成員函數):     PyTypeObject Slots. (line 1133)
* PyTypeObject.tp_is_gc (C 成員函數):    PyTypeObject Slots. (line 1252)
* PyTypeObject.tp_itemsize (C 成員函數): PyTypeObject Slots. (line   47)
* PyTypeObject.tp_iter (C 成員函數):     PyTypeObject Slots. (line  900)
* PyTypeObject.tp_iternext (C 成員函數): PyTypeObject Slots. (line  916)
* PyTypeObject.tp_maxalloc (C 成員函數): PyTypeObject Slots. (line 1400)
* PyTypeObject.tp_members (C 成員函數):  PyTypeObject Slots. (line  953)
* PyTypeObject.tp_methods (C 成員函數):  PyTypeObject Slots. (line  938)
* PyTypeObject.tp_mro (C 成員函數):      PyTypeObject Slots. (line 1292)
* PyTypeObject.tp_name (C 成員函數):     PyTypeObject Slots. (line   12)
* PyTypeObject.tp_new (C 成員函數):      PyTypeObject Slots. (line 1193)
* PyTypeObject.tp_next (C 成員函數):     PyTypeObject Slots. (line 1409)
* PyTypeObject.tp_prev (C 成員函數):     PyTypeObject Slots. (line 1404)
* PyTypeObject.tp_repr (C 成員函數):     PyTypeObject Slots. (line  253)
* PyTypeObject.tp_richcompare (C 成員函數): PyTypeObject Slots.
                                                             (line  789)
* PyTypeObject.tp_setattr (C 成員函數):  PyTypeObject Slots. (line  219)
* PyTypeObject.tp_setattro (C 成員函數): PyTypeObject Slots. (line  412)
* PyTypeObject.tp_str (C 成員函數):      PyTypeObject Slots. (line  361)
* PyTypeObject.tp_subclasses (C 成員函數): PyTypeObject Slots.
                                                             (line 1311)
* PyTypeObject.tp_traverse (C 成員函數): PyTypeObject Slots. (line  658)
* PyTypeObject.tp_vectorcall_offset (C 成員函數): PyTypeObject Slots.
                                                             (line  141)
* PyTypeObject.tp_version_tag (C 成員函數): PyTypeObject Slots.
                                                             (line 1332)
* PyTypeObject.tp_weaklist (C 成員函數): PyTypeObject Slots. (line 1319)
* PyTypeObject.tp_weaklistoffset (C 成員函數): PyTypeObject Slots.
                                                             (line  864)
* PyType_Check (C 函式):                 Type Objects<2>.    (line   15)
* PyType_CheckExact (C 函式):            Type Objects<2>.    (line   21)
* PyType_ClearCache (C 函式):            Type Objects<2>.    (line   26)
* PyType_FromSpec (C 函式):              Creating Heap-Allocated Types.
                                                             (line   26)
* PyType_FromSpecWithBases (C 函式):     Creating Heap-Allocated Types.
                                                             (line    9)
* PyType_GenericAlloc (C 函式):          Type Objects<2>.    (line   68)
* PyType_GenericNew (C 函式):            Type Objects<2>.    (line   76)
* PyType_GetFlags (C 函式):              Type Objects<2>.    (line   30)
* PyType_GetSlot (C 函式):               Type Objects<2>.    (line   89)
* PyType_HasFeature (C 函式):            Type Objects<2>.    (line   49)
* PyType_IsSubtype (C 函式):             Type Objects<2>.    (line   59)
* PyType_IS_GC (C 函式):                 Type Objects<2>.    (line   54)
* PyType_Modified (C 函式):              Type Objects<2>.    (line   43)
* PyType_Ready (C 函式):                 Type Objects<2>.    (line   82)
* PyType_Slot (C 型態):                  Creating Heap-Allocated Types.
                                                             (line   59)
* PyType_Slot.PyType_Slot.pfunc (C 成員函數): Creating Heap-Allocated Types.
                                                             (line  109)
* PyType_Slot.PyType_Slot.slot (C 成員函數): Creating Heap-Allocated Types.
                                                             (line   64)
* PyType_Spec (C 型態):                  Creating Heap-Allocated Types.
                                                             (line   30)
* PyType_Spec.PyType_Spec.basicsize (C 成員函數): Creating Heap-Allocated Types.
                                                             (line   39)
* PyType_Spec.PyType_Spec.flags (C 成員函數): Creating Heap-Allocated Types.
                                                             (line   47)
* PyType_Spec.PyType_Spec.itemsize (C 成員函數): Creating Heap-Allocated Types.
                                                             (line   41)
* PyType_Spec.PyType_Spec.name (C 成員函數): Creating Heap-Allocated Types.
                                                             (line   34)
* PyType_Spec.PyType_Spec.slots (C 成員函數): Creating Heap-Allocated Types.
                                                             (line   54)
* PyType_Type (C 變數):                  Type Objects<2>.    (line   10)
* PyTZInfo_Check (C 函式):               DateTime 物件.      (line   65)
* PyTZInfo_CheckExact (C 函式):          DateTime 物件.      (line   70)
* PyUnicodeDecodeError_Create (C 函式):  Unicode Exception Objects.
                                                             (line    9)
* PyUnicodeDecodeError_GetEncoding (C 函式): Unicode Exception Objects.
                                                             (line   45)
* PyUnicodeDecodeError_GetEnd (C 函式):  Unicode Exception Objects.
                                                             (line   83)
* PyUnicodeDecodeError_GetObject (C 函式): Unicode Exception Objects.
                                                             (line   50)
* PyUnicodeDecodeError_GetReason (C 函式): Unicode Exception Objects.
                                                             (line  106)
* PyUnicodeDecodeError_GetStart (C 函式): Unicode Exception Objects.
                                                             (line   56)
* PyUnicodeDecodeError_SetEnd (C 函式):  Unicode Exception Objects.
                                                             (line   95)
* PyUnicodeDecodeError_SetReason (C 函式): Unicode Exception Objects.
                                                             (line  112)
* PyUnicodeDecodeError_SetStart (C 函式): Unicode Exception Objects.
                                                             (line   70)
* PyUnicodeEncodeError_Create (C 函式):  Unicode Exception Objects.
                                                             (line   18)
* PyUnicodeEncodeError_GetEncoding (C 函式): Unicode Exception Objects.
                                                             (line   45)
* PyUnicodeEncodeError_GetEnd (C 函式):  Unicode Exception Objects.
                                                             (line   83)
* PyUnicodeEncodeError_GetObject (C 函式): Unicode Exception Objects.
                                                             (line   50)
* PyUnicodeEncodeError_GetReason (C 函式): Unicode Exception Objects.
                                                             (line  106)
* PyUnicodeEncodeError_GetStart (C 函式): Unicode Exception Objects.
                                                             (line   56)
* PyUnicodeEncodeError_SetEnd (C 函式):  Unicode Exception Objects.
                                                             (line   95)
* PyUnicodeEncodeError_SetReason (C 函式): Unicode Exception Objects.
                                                             (line  112)
* PyUnicodeEncodeError_SetStart (C 函式): Unicode Exception Objects.
                                                             (line   70)
* PyUnicodeObject (C 型態):              Unicode Type.       (line   29)
* PyUnicodeTranslateError_Create (C 函式): Unicode Exception Objects.
                                                             (line   31)
* PyUnicodeTranslateError_GetEnd (C 函式): Unicode Exception Objects.
                                                             (line   83)
* PyUnicodeTranslateError_GetObject (C 函式): Unicode Exception Objects.
                                                             (line   50)
* PyUnicodeTranslateError_GetReason (C 函式): Unicode Exception Objects.
                                                             (line  106)
* PyUnicodeTranslateError_GetStart (C 函式): Unicode Exception Objects.
                                                             (line   56)
* PyUnicodeTranslateError_SetEnd (C 函式): Unicode Exception Objects.
                                                             (line   95)
* PyUnicodeTranslateError_SetReason (C 函式): Unicode Exception Objects.
                                                             (line  112)
* PyUnicodeTranslateError_SetStart (C 函式): Unicode Exception Objects.
                                                             (line   70)
* PyUnicode_1BYTE_DATA (C 函式):         Unicode Type.       (line   80)
* PyUnicode_1BYTE_KIND (C 巨集):         Unicode Type.       (line   93)
* PyUnicode_2BYTE_DATA (C 函式):         Unicode Type.       (line   80)
* PyUnicode_2BYTE_KIND (C 巨集):         Unicode Type.       (line   93)
* PyUnicode_4BYTE_DATA (C 函式):         Unicode Type.       (line   80)
* PyUnicode_4BYTE_KIND (C 巨集):         Unicode Type.       (line   93)
* PyUnicode_AsASCIIString (C 函式):      ASCII Codecs.       (line   15)
* PyUnicode_AsCharmapString (C 函式):    Character Map Codecs.
                                                             (line   30)
* PyUnicode_AsEncodedString (C 函式):    Generic Codecs.     (line   17)
* PyUnicode_AsLatin1String (C 函式):     Latin-1 Codecs.     (line   16)
* PyUnicode_AsMBCSString (C 函式):       MBCS codecs for Windows.
                                                             (line   27)
* PyUnicode_AsRawUnicodeEscapeString (C 函式): Raw-Unicode-Escape Codecs.
                                                             (line   15)
* PyUnicode_AsUCS4 (C 函式):             Creating and accessing Unicode strings.
                                                             (line  246)
* PyUnicode_AsUCS4Copy (C 函式):         Creating and accessing Unicode strings.
                                                             (line  257)
* PyUnicode_AsUnicode (C 函式):          Deprecated Py_UNICODE APIs.
                                                             (line   35)
* PyUnicode_AsUnicodeAndSize (C 函式):   Deprecated Py_UNICODE APIs.
                                                             (line   64)
* PyUnicode_AsUnicodeCopy (C 函式):      Deprecated Py_UNICODE APIs.
                                                             (line   81)
* PyUnicode_AsUnicodeEscapeString (C 函式): Unicode-Escape Codecs.
                                                             (line   15)
* PyUnicode_AsUTF16String (C 函式):      UTF-16 Codecs.      (line   49)
* PyUnicode_AsUTF32String (C 函式):      UTF-32 Codecs.      (line   48)
* PyUnicode_AsUTF8 (C 函式):             UTF-8 Codecs.       (line   52)
* PyUnicode_AsUTF8AndSize (C 函式):      UTF-8 Codecs.       (line   29)
* PyUnicode_AsUTF8String (C 函式):       UTF-8 Codecs.       (line   24)
* PyUnicode_AsWideChar (C 函式):         wchar_t Support.    (line   16)
* PyUnicode_AsWideCharString (C 函式):   wchar_t Support.    (line   30)
* PyUnicode_AS_DATA (C 函式):            Unicode Type.       (line  184)
* PyUnicode_AS_UNICODE (C 函式):         Unicode Type.       (line  184)
* PyUnicode_Check (C 函式):              Unicode Type.       (line   48)
* PyUnicode_CheckExact (C 函式):         Unicode Type.       (line   53)
* PyUnicode_ClearFreeList (C 函式):      Unicode Type.       (line  160)
* PyUnicode_Compare (C 函式):            Methods and Slot Functions.
                                                             (line   86)
* PyUnicode_CompareWithASCIIString (C 函式): Methods and Slot Functions.
                                                             (line   94)
* PyUnicode_Concat (C 函式):             Methods and Slot Functions.
                                                             (line   12)
* PyUnicode_Contains (C 函式):           Methods and Slot Functions.
                                                             (line  125)
* PyUnicode_CopyCharacters (C 函式):     Creating and accessing Unicode strings.
                                                             (line  188)
* PyUnicode_Count (C 函式):              Methods and Slot Functions.
                                                             (line   73)
* PyUnicode_DATA (C 函式):               Unicode Type.       (line  114)
* PyUnicode_Decode (C 函式):             Generic Codecs.     (line    8)
* PyUnicode_DecodeASCII (C 函式):        ASCII Codecs.       (line    9)
* PyUnicode_DecodeCharmap (C 函式):      Character Map Codecs.
                                                             (line   15)
* PyUnicode_DecodeFSDefault (C 函式):    File System Encoding.
                                                             (line   65)
* PyUnicode_DecodeFSDefaultAndSize (C 函式): File System Encoding.
                                                             (line   43)
* PyUnicode_DecodeLatin1 (C 函式):       Latin-1 Codecs.     (line   10)
* PyUnicode_DecodeLocale (C 函式):       Locale Encoding.    (line   38)
* PyUnicode_DecodeLocaleAndSize (C 函式): Locale Encoding.   (line    9)
* PyUnicode_DecodeMBCS (C 函式):         MBCS codecs for Windows.
                                                             (line   12)
* PyUnicode_DecodeMBCSStateful (C 函式): MBCS codecs for Windows.
                                                             (line   18)
* PyUnicode_DecodeRawUnicodeEscape (C 函式): Raw-Unicode-Escape Codecs.
                                                             (line    8)
* PyUnicode_DecodeUnicodeEscape (C 函式): Unicode-Escape Codecs.
                                                             (line    8)
* PyUnicode_DecodeUTF16 (C 函式):        UTF-16 Codecs.      (line    8)
* PyUnicode_DecodeUTF16Stateful (C 函式): UTF-16 Codecs.     (line   36)
* PyUnicode_DecodeUTF32 (C 函式):        UTF-32 Codecs.      (line    8)
* PyUnicode_DecodeUTF32Stateful (C 函式): UTF-32 Codecs.     (line   35)
* PyUnicode_DecodeUTF7 (C 函式):         UTF-7 Codecs.       (line    8)
* PyUnicode_DecodeUTF7Stateful (C 函式): UTF-7 Codecs.       (line   14)
* PyUnicode_DecodeUTF8 (C 函式):         UTF-8 Codecs.       (line    8)
* PyUnicode_DecodeUTF8Stateful (C 函式): UTF-8 Codecs.       (line   14)
* PyUnicode_Encode (C 函式):             Generic Codecs.     (line   26)
* PyUnicode_EncodeASCII (C 函式):        ASCII Codecs.       (line   20)
* PyUnicode_EncodeCharmap (C 函式):      Character Map Codecs.
                                                             (line   44)
* PyUnicode_EncodeCodePage (C 函式):     MBCS codecs for Windows.
                                                             (line   32)
* PyUnicode_EncodeFSDefault (C 函式):    File System Encoding.
                                                             (line   78)
* PyUnicode_EncodeLatin1 (C 函式):       Latin-1 Codecs.     (line   22)
* PyUnicode_EncodeLocale (C 函式):       Locale Encoding.    (line   47)
* PyUnicode_EncodeMBCS (C 函式):         MBCS codecs for Windows.
                                                             (line   41)
* PyUnicode_EncodeRawUnicodeEscape (C 函式): Raw-Unicode-Escape Codecs.
                                                             (line   22)
* PyUnicode_EncodeUnicodeEscape (C 函式): Unicode-Escape Codecs.
                                                             (line   22)
* PyUnicode_EncodeUTF16 (C 函式):        UTF-16 Codecs.      (line   55)
* PyUnicode_EncodeUTF32 (C 函式):        UTF-32 Codecs.      (line   54)
* PyUnicode_EncodeUTF7 (C 函式):         UTF-7 Codecs.       (line   24)
* PyUnicode_EncodeUTF8 (C 函式):         UTF-8 Codecs.       (line   62)
* PyUnicode_Fill (C 函式):               Creating and accessing Unicode strings.
                                                             (line  201)
* PyUnicode_Find (C 函式):               Methods and Slot Functions.
                                                             (line   46)
* PyUnicode_FindChar (C 函式):           Methods and Slot Functions.
                                                             (line   57)
* PyUnicode_Format (C 函式):             Methods and Slot Functions.
                                                             (line  120)
* PyUnicode_FromEncodedObject (C 函式):  Creating and accessing Unicode strings.
                                                             (line  164)
* PyUnicode_FromFormat (C 函式):         Creating and accessing Unicode strings.
                                                             (line   48)
* PyUnicode_FromFormatV (C 函式):        Creating and accessing Unicode strings.
                                                             (line  157)
* PyUnicode_FromKindAndData (C 函式):    Creating and accessing Unicode strings.
                                                             (line   20)
* PyUnicode_FromObject (C 函式):         Deprecated Py_UNICODE APIs.
                                                             (line  106)
* PyUnicode_FromString (C 函式):         Creating and accessing Unicode strings.
                                                             (line   44)
* PyUnicode_FromString():                字典物件.           (line   59)
* PyUnicode_FromStringAndSize (C 函式):  Creating and accessing Unicode strings.
                                                             (line   30)
* PyUnicode_FromUnicode (C 函式):        Deprecated Py_UNICODE APIs.
                                                             (line   13)
* PyUnicode_FromWideChar (C 函式):       wchar_t Support.    (line    8)
* PyUnicode_FSConverter (C 函式):        File System Encoding.
                                                             (line   13)
* PyUnicode_FSDecoder (C 函式):          File System Encoding.
                                                             (line   30)
* PyUnicode_GetLength (C 函式):          Creating and accessing Unicode strings.
                                                             (line  182)
* PyUnicode_GetSize (C 函式):            Deprecated Py_UNICODE APIs.
                                                             (line   96)
* PyUnicode_GET_DATA_SIZE (C 函式):      Unicode Type.       (line  174)
* PyUnicode_GET_LENGTH (C 函式):         Unicode Type.       (line   72)
* PyUnicode_GET_SIZE (C 函式):           Unicode Type.       (line  164)
* PyUnicode_InternFromString (C 函式):   Methods and Slot Functions.
                                                             (line  147)
* PyUnicode_InternInPlace (C 函式):      Methods and Slot Functions.
                                                             (line  134)
* PyUnicode_Join (C 函式):               Methods and Slot Functions.
                                                             (line   32)
* PyUnicode_KIND (C 函式):               Unicode Type.       (line  105)
* PyUnicode_MAX_CHAR_VALUE (C 巨集):     Unicode Type.       (line  151)
* PyUnicode_New (C 函式):                Creating and accessing Unicode strings.
                                                             (line    9)
* PyUnicode_READ (C 函式):               Unicode Type.       (line  134)
* PyUnicode_ReadChar (C 函式):           Creating and accessing Unicode strings.
                                                             (line  229)
* PyUnicode_READY (C 函式):              Unicode Type.       (line   58)
* PyUnicode_READ_CHAR (C 函式):          Unicode Type.       (line  143)
* PyUnicode_Replace (C 函式):            Methods and Slot Functions.
                                                             (line   79)
* PyUnicode_RichCompare (C 函式):        Methods and Slot Functions.
                                                             (line  106)
* PyUnicode_Split (C 函式):              Methods and Slot Functions.
                                                             (line   16)
* PyUnicode_Splitlines (C 函式):         Methods and Slot Functions.
                                                             (line   26)
* PyUnicode_Substring (C 函式):          Creating and accessing Unicode strings.
                                                             (line  238)
* PyUnicode_Tailmatch (C 函式):          Methods and Slot Functions.
                                                             (line   37)
* PyUnicode_TransformDecimalToASCII (C 函式): Deprecated Py_UNICODE APIs.
                                                             (line   52)
* PyUnicode_Translate (C 函式):          Character Map Codecs.
                                                             (line   59)
* PyUnicode_TranslateCharmap (C 函式):   Character Map Codecs.
                                                             (line   76)
* PyUnicode_Type (C 變數):               Unicode Type.       (line   40)
* PyUnicode_WCHAR_KIND (C 巨集):         Unicode Type.       (line   93)
* PyUnicode_WRITE (C 函式):              Unicode Type.       (line  121)
* PyUnicode_WriteChar (C 函式):          Creating and accessing Unicode strings.
                                                             (line  215)
* PyVarObject (C 型態):                  通用物件結構.       (line   28)
* PyVarObject.ob_size (C 成員函數):      PyVarObject Slots.  (line    6)
* PyVarObject_HEAD_INIT (C 巨集):        通用物件結構.       (line   86)
* PyVectorcall_Call (C 函式):            PyTypeObject Slots. (line  164)
* PyVectorcall_NARGS (C 函式):           Object Protocol.    (line  392)
* PyWeakref_Check (C 函式):              弱參照物件.         (line   11)
* PyWeakref_CheckProxy (C 函式):         弱參照物件.         (line   19)
* PyWeakref_CheckRef (C 函式):           弱參照物件.         (line   15)
* PyWeakref_GetObject (C 函式):          弱參照物件.         (line   50)
* PyWeakref_GET_OBJECT (C 函式):         弱參照物件.         (line   60)
* PyWeakref_NewProxy (C 函式):           弱參照物件.         (line   36)
* PyWeakref_NewRef (C 函式):             弱參照物件.         (line   23)
* PyWideStringList (C 型態):             PyWideStringList.   (line    6)
* PyWideStringList.items (C 成員函數):   PyWideStringList.   (line   41)
* PyWideStringList.length (C 成員函數):  PyWideStringList.   (line   37)
* PyWideStringList_Append (C 函式):      PyWideStringList.   (line   15)
* PyWideStringList_Insert (C 函式):      PyWideStringList.   (line   22)
* PyWrapper_New (C 函式):                修飾器物件.         (line   44)
* PyZipFile (zipfile 中的類別):          PyZipFile Objects.  (line   10)
* Py_ABS (C 巨集):                       Useful macros.      (line   21)
* Py_AddPendingCall (C 函式):            Asynchronous Notifications.
                                                             (line   10)
* Py_AddPendingCall():                   Asynchronous Notifications.
                                                             (line   12)
* Py_AtExit (C 函式):                    行程（Process）控制.
                                                             (line   24)
* Py_BEGIN_ALLOW_THREADS:                Releasing the GIL from extension code.
                                                             (line   21)
* Py_BEGIN_ALLOW_THREADS (C 巨集):       High-level API.     (line  156)
* Py_BLOCK_THREADS (C 巨集):             High-level API.     (line  170)
* Py_buffer (C 型態):                    Buffer structure.   (line   25)
* Py_buffer.buf (C 成員函數):            Buffer structure.   (line   27)
* Py_buffer.format (C 成員函數):         Buffer structure.   (line   87)
* Py_buffer.internal (C 成員函數):       Buffer structure.   (line  154)
* Py_buffer.itemsize (C 成員函數):       Buffer structure.   (line   67)
* Py_buffer.len (C 成員函數):            Buffer structure.   (line   50)
* Py_buffer.ndim (C 成員函數):           Buffer structure.   (line   96)
* Py_buffer.obj (C 成員函數):            Buffer structure.   (line   38)
* Py_buffer.readonly (C 成員函數):       Buffer structure.   (line   62)
* Py_buffer.shape (C 成員函數):          Buffer structure.   (line  109)
* Py_buffer.strides (C 成員函數):        Buffer structure.   (line  122)
* Py_buffer.suboffsets (C 成員函數):     Buffer structure.   (line  135)
* Py_BuildValue (C 函式):                Building values.    (line    6)
* Py_BytesMain (C 函式):                 The Very High Level Layer.
                                                             (line   41)
* Py_BytesWarningFlag (C 變數):          Global configuration variables.
                                                             (line   15)
* Py_CHARMASK (C 巨集):                  Useful macros.      (line   52)
* Py_CLEAR (C 函式):                     參照計數.           (line   47)
* py_compile (模組):                     py_compile --- Compile Python source files.
                                                             (line    6)
* PY_COMPILED (於 imp 模組中):           imp --- Access the import internals.
                                                             (line  313)
* Py_CompileString (C 函式):             The Very High Level Layer.
                                                             (line  284)
* Py_CompileString():                    The Very High Level Layer.
                                                             (line  378)
* Py_CompileString() <1>:                The Very High Level Layer.
                                                             (line  383)
* Py_CompileString() <2>:                The Very High Level Layer.
                                                             (line  390)
* Py_CompileStringExFlags (C 函式):      The Very High Level Layer.
                                                             (line  317)
* Py_CompileStringFlags (C 函式):        The Very High Level Layer.
                                                             (line  290)
* Py_CompileStringObject (C 函式):       The Very High Level Layer.
                                                             (line  297)
* Py_complex (C 型態):                   Complex Numbers as C Structures.
                                                             (line   10)
* Py_DebugFlag (C 變數):                 Global configuration variables.
                                                             (line   23)
* Py_DecodeLocale (C 函式):              作業系統工具.       (line  107)
* Py_DECREF (C 函式):                    參照計數.           (line   20)
* Py_DECREF():                           Reference Counts<2>.
                                                             (line   17)
* Py_DEPRECATED (C 巨集):                Useful macros.      (line   70)
* Py_DontWriteBytecodeFlag (C 變數):     Global configuration variables.
                                                             (line   31)
* Py_Ellipsis (C 變數):                  Ellipsis Object.    (line    6)
* Py_EncodeLocale (C 函式):              作業系統工具.       (line  160)
* Py_EndInterpreter (C 函式):            Sub-interpreter support.
                                                             (line   76)
* Py_END_ALLOW_THREADS:                  Releasing the GIL from extension code.
                                                             (line   21)
* Py_END_ALLOW_THREADS (C 巨集):         High-level API.     (line  163)
* Py_EnterRecursiveCall (C 函式):        Recursion Control.  (line   11)
* Py_eval_input (C 變數):                The Very High Level Layer.
                                                             (line  376)
* Py_Exit (C 函式):                      行程（Process）控制.
                                                             (line   15)
* Py_ExitStatusException (C 函式):       PyStatus.           (line   62)
* Py_False (C 變數):                     布林物件.           (line   15)
* Py_FatalError (C 函式):                行程（Process）控制.
                                                             (line    6)
* Py_FatalError():                       Process-wide parameters.
                                                             (line  217)
* Py_FdIsInteractive (C 函式):           作業系統工具.       (line   17)
* Py_file_input (C 變數):                The Very High Level Layer.
                                                             (line  381)
* Py_Finalize (C 函式):                  Initializing and finalizing the interpreter.
                                                             (line   78)
* Py_FinalizeEx (C 函式):                Initializing and finalizing the interpreter.
                                                             (line   39)
* Py_FinalizeEx():                       行程（Process）控制.
                                                             (line   17)
* Py_FinalizeEx() <1>:                   行程（Process）控制.
                                                             (line   26)
* Py_FinalizeEx() <2>:                   Initializing and finalizing the interpreter.
                                                             (line    8)
* Py_FinalizeEx() <3>:                   Sub-interpreter support.
                                                             (line   49)
* Py_FinalizeEx() <4>:                   Sub-interpreter support.
                                                             (line   78)
* PY_FROZEN (於 imp 模組中):             imp --- Access the import internals.
                                                             (line  337)
* Py_FrozenFlag (C 變數):                Global configuration variables.
                                                             (line   39)
* Py_GetBuildInfo (C 函式):              Process-wide parameters.
                                                             (line  203)
* Py_GetCompiler (C 函式):               Process-wide parameters.
                                                             (line  192)
* Py_GetCopyright (C 函式):              Process-wide parameters.
                                                             (line  181)
* Py_GETENV (C 巨集):                    Useful macros.      (line   57)
* Py_GetExecPrefix (C 函式):             Process-wide parameters.
                                                             (line   71)
* Py_GetExecPrefix():                    嵌入式Python.       (line   42)
* Py_GetPath (C 函式):                   Process-wide parameters.
                                                             (line  118)
* Py_GetPath():                          嵌入式Python.       (line   42)
* Py_GetPath() <1>:                      Process-wide parameters.
                                                             (line   36)
* Py_GetPath() <2>:                      Process-wide parameters.
                                                             (line  133)
* Py_GetPlatform (C 函式):               Process-wide parameters.
                                                             (line  170)
* Py_GetPrefix (C 函式):                 Process-wide parameters.
                                                             (line   57)
* Py_GetPrefix():                        嵌入式Python.       (line   42)
* Py_GetProgramFullPath (C 函式):        Process-wide parameters.
                                                             (line  109)
* Py_GetProgramFullPath():               嵌入式Python.       (line   42)
* Py_GetProgramName (C 函式):            Process-wide parameters.
                                                             (line   51)
* Py_GetPythonHome (C 函式):             Process-wide parameters.
                                                             (line  280)
* Py_GetVersion (C 函式):                Process-wide parameters.
                                                             (line  157)
* Py_HashRandomizationFlag (C 變數):     Global configuration variables.
                                                             (line   46)
* Py_IgnoreEnvironmentFlag (C 變數):     Global configuration variables.
                                                             (line   54)
* Py_INCREF (C 函式):                    參照計數.           (line    9)
* Py_INCREF():                           Reference Counts<2>.
                                                             (line   17)
* Py_Initialize (C 函式):                Initializing and finalizing the interpreter.
                                                             (line    6)
* Py_Initialize():                       嵌入式Python.       (line   12)
* Py_Initialize() <1>:                   Process-wide parameters.
                                                             (line    9)
* Py_Initialize() <2>:                   Process-wide parameters.
                                                             (line   36)
* Py_Initialize() <3>:                   Sub-interpreter support.
                                                             (line   49)
* Py_InitializeEx (C 函式):              Initializing and finalizing the interpreter.
                                                             (line   26)
* Py_InitializeFromConfig (C 函式):      Initialization with PyConfig.
                                                             (line    8)
* Py_InspectFlag (C 變數):               Global configuration variables.
                                                             (line   61)
* Py_InteractiveFlag (C 變數):           Global configuration variables.
                                                             (line   71)
* Py_IsInitialized (C 函式):             Initializing and finalizing the interpreter.
                                                             (line   32)
* Py_IsInitialized():                    嵌入式Python.       (line   51)
* Py_IsolatedFlag (C 變數):              Global configuration variables.
                                                             (line   75)
* Py_LeaveRecursiveCall (C 函式):        Recursion Control.  (line   29)
* Py_LegacyWindowsFSEncodingFlag (C 變數): Global configuration variables.
                                                             (line   85)
* Py_LegacyWindowsStdioFlag (C 變數):    Global configuration variables.
                                                             (line   97)
* Py_Main (C 函式):                      The Very High Level Layer.
                                                             (line   24)
* Py_MAX (C 巨集):                       Useful macros.      (line   33)
* Py_MEMBER_SIZE (C 巨集):               Useful macros.      (line   46)
* Py_MIN (C 巨集):                       Useful macros.      (line   27)
* Py_mod_create (C 巨集):                Multi-phase initialization.
                                                             (line   61)
* Py_mod_exec (C 巨集):                  Multi-phase initialization.
                                                             (line   95)
* Py_NewInterpreter (C 函式):            Sub-interpreter support.
                                                             (line   24)
* Py_None (C 變數):                      The None Object.    (line   11)
* Py_NoSiteFlag (C 變數):                Global configuration variables.
                                                             (line  109)
* Py_NotImplemented (C 變數):            Object Protocol.    (line    6)
* Py_NoUserSiteDirectory (C 變數):       Global configuration variables.
                                                             (line  119)
* py_object (ctypes 中的類別):           Fundamental data types<2>.
                                                             (line  213)
* Py_OptimizeFlag (C 變數):              Global configuration variables.
                                                             (line  127)
* Py_PreInitialize (C 函式):             Preinitialization with PyPreConfig.
                                                             (line    8)
* Py_PreInitializeFromArgs (C 函式):     Preinitialization with PyPreConfig.
                                                             (line   18)
* Py_PreInitializeFromBytesArgs (C 函式): Preinitialization with PyPreConfig.
                                                             (line   12)
* Py_PRINT_RAW:                          檔案（File）物件.   (line   87)
* PY_PYTHON:                             Customizing default Python versions.
                                                             (line   18)
* Py_QuietFlag (C 變數):                 Global configuration variables.
                                                             (line  132)
* Py_REFCNT (C 巨集):                    通用物件結構.       (line   64)
* Py_ReprEnter (C 函式):                 Recursion Control.  (line   41)
* Py_ReprLeave (C 函式):                 Recursion Control.  (line   59)
* Py_RETURN_FALSE (C 巨集):              布林物件.           (line   27)
* Py_RETURN_NONE (C 巨集):               The None Object.    (line   17)
* Py_RETURN_NOTIMPLEMENTED (C 巨集):     Object Protocol.    (line   11)
* Py_RETURN_RICHCOMPARE (C 巨集):        PyTypeObject Slots. (line  833)
* Py_RETURN_TRUE (C 巨集):               布林物件.           (line   32)
* Py_RunMain (C 函式):                   Py_RunMain.         (line    6)
* Py_SetPath (C 函式):                   Process-wide parameters.
                                                             (line  131)
* Py_SetPath():                          Process-wide parameters.
                                                             (line  120)
* Py_SetProgramName (C 函式):            Process-wide parameters.
                                                             (line   34)
* Py_SetProgramName():                   嵌入式Python.       (line   42)
* Py_SetProgramName() <1>:               Initializing and finalizing the interpreter.
                                                             (line    8)
* Py_SetProgramName() <2>:               Process-wide parameters.
                                                             (line   53)
* Py_SetProgramName() <3>:               Process-wide parameters.
                                                             (line  111)
* Py_SetPythonHome (C 函式):             Process-wide parameters.
                                                             (line  266)
* Py_SetStandardStreamEncoding (C 函式): Process-wide parameters.
                                                             (line    6)
* Py_single_input (C 變數):              The Very High Level Layer.
                                                             (line  388)
* Py_SIZE (C 巨集):                      通用物件結構.       (line   71)
* PY_SOURCE (於 imp 模組中):             imp --- Access the import internals.
                                                             (line  307)
* PY_SSIZE_T_MAX:                        整數物件.           (line  180)
* Py_STRINGIFY (C 巨集):                 Useful macros.      (line   39)
* Py_TPFLAGS_BASETYPE (內建變數):        PyTypeObject Slots. (line  505)
* Py_TPFLAGS_BASE_EXC_SUBCLASS (內建變數): PyTypeObject Slots.
                                                             (line  602)
* Py_TPFLAGS_BYTES_SUBCLASS (內建變數):  PyTypeObject Slots. (line  596)
* Py_TPFLAGS_DEFAULT (內建變數):         PyTypeObject Slots. (line  554)
* Py_TPFLAGS_DICT_SUBCLASS (內建變數):   PyTypeObject Slots. (line  600)
* Py_TPFLAGS_HAVE_FINALIZE (內建變數):   PyTypeObject Slots. (line  615)
* Py_TPFLAGS_HAVE_GC (內建變數):         PyTypeObject Slots. (line  533)
* Py_TPFLAGS_HEAPTYPE (內建變數):        PyTypeObject Slots. (line  490)
* Py_TPFLAGS_LIST_SUBCLASS (內建變數):   PyTypeObject Slots. (line  592)
* Py_TPFLAGS_LONG_SUBCLASS (內建變數):   PyTypeObject Slots. (line  590)
* Py_TPFLAGS_METHOD_DESCRIPTOR (內建變數): PyTypeObject Slots.
                                                             (line  566)
* Py_TPFLAGS_READY (內建變數):           PyTypeObject Slots. (line  515)
* Py_TPFLAGS_READYING (內建變數):        PyTypeObject Slots. (line  524)
* Py_TPFLAGS_TUPLE_SUBCLASS (內建變數):  PyTypeObject Slots. (line  594)
* Py_TPFLAGS_TYPE_SUBCLASS (內建變數):   PyTypeObject Slots. (line  604)
* Py_TPFLAGS_UNICODE_SUBCLASS (內建變數): PyTypeObject Slots.
                                                             (line  598)
* Py_tracefunc (C 型態):                 Profiling and Tracing.
                                                             (line   18)
* Py_True (C 變數):                      布林物件.           (line   21)
* Py_tss_NEEDS_INIT (C 巨集):            Thread Specific Storage TSS API.
                                                             (line   28)
* Py_tss_t (C 型態):                     Thread Specific Storage TSS API.
                                                             (line   17)
* Py_TYPE (C 巨集):                      通用物件結構.       (line   57)
* Py_UCS1 (C 型態):                      Unicode Type.       (line    9)
* Py_UCS2 (C 型態):                      Unicode Type.       (line    9)
* Py_UCS4 (C 型態):                      Unicode Type.       (line    9)
* Py_UNBLOCK_THREADS (C 巨集):           High-level API.     (line  176)
* Py_UnbufferedStdioFlag (C 變數):       Global configuration variables.
                                                             (line  141)
* Py_UNICODE (C 型態):                   Unicode Type.       (line   20)
* Py_UNICODE_ISALNUM (C 函式):           Unicode Character Properties.
                                                             (line   52)
* Py_UNICODE_ISALPHA (C 函式):           Unicode Character Properties.
                                                             (line   47)
* Py_UNICODE_ISDECIMAL (C 函式):         Unicode Character Properties.
                                                             (line   35)
* Py_UNICODE_ISDIGIT (C 函式):           Unicode Character Properties.
                                                             (line   39)
* Py_UNICODE_ISLINEBREAK (C 函式):       Unicode Character Properties.
                                                             (line   30)
* Py_UNICODE_ISLOWER (C 函式):           Unicode Character Properties.
                                                             (line   15)
* Py_UNICODE_ISNUMERIC (C 函式):         Unicode Character Properties.
                                                             (line   43)
* Py_UNICODE_ISPRINTABLE (C 函式):       Unicode Character Properties.
                                                             (line   57)
* Py_UNICODE_ISSPACE (C 函式):           Unicode Character Properties.
                                                             (line   10)
* Py_UNICODE_ISTITLE (C 函式):           Unicode Character Properties.
                                                             (line   25)
* Py_UNICODE_ISUPPER (C 函式):           Unicode Character Properties.
                                                             (line   20)
* Py_UNICODE_IS_HIGH_SURROGATE (C 巨集): Unicode Character Properties.
                                                             (line  111)
* Py_UNICODE_IS_LOW_SURROGATE (C 巨集):  Unicode Character Properties.
                                                             (line  115)
* Py_UNICODE_IS_SURROGATE (C 巨集):      Unicode Character Properties.
                                                             (line  107)
* Py_UNICODE_JOIN_SURROGATES (C 巨集):   Unicode Character Properties.
                                                             (line  119)
* Py_UNICODE_TODECIMAL (C 函式):         Unicode Character Properties.
                                                             (line   88)
* Py_UNICODE_TODIGIT (C 函式):           Unicode Character Properties.
                                                             (line   94)
* Py_UNICODE_TOLOWER (C 函式):           Unicode Character Properties.
                                                             (line   70)
* Py_UNICODE_TONUMERIC (C 函式):         Unicode Character Properties.
                                                             (line  100)
* Py_UNICODE_TOTITLE (C 函式):           Unicode Character Properties.
                                                             (line   82)
* Py_UNICODE_TOUPPER (C 函式):           Unicode Character Properties.
                                                             (line   76)
* Py_UNREACHABLE (C 巨集):               Useful macros.      (line   11)
* Py_UNUSED (C 巨集):                    Useful macros.      (line   62)
* Py_VaBuildValue (C 函式):              Building values.    (line  200)
* PY_VECTORCALL_ARGUMENTS_OFFSET (C 巨集): Object Protocol.  (line  378)
* Py_VerboseFlag (C 變數):               Global configuration variables.
                                                             (line  148)
* Py_VISIT (C 函式):                     Supporting Cyclic Garbage Collection.
                                                             (line  116)
* Py_XDECREF (C 函式):                   參照計數.           (line   40)
* Py_XDECREF():                          Exceptions<16>.     (line  123)
* Py_XINCREF (C 函式):                   參照計數.           (line   15)
* P_ALL (於 os 模組中):                  Process Management. (line  736)
* P_DETACH (於 os 模組中):               Process Management. (line  599)
* P_NOWAIT (於 os 模組中):               Process Management. (line  579)
* P_NOWAITO (於 os 模組中):              Process Management. (line  579)
* P_OVERLAY (於 os 模組中):              Process Management. (line  599)
* P_PGID (於 os 模組中):                 Process Management. (line  736)
* P_PID (於 os 模組中):                  Process Management. (line  736)
* P_WAIT (於 os 模組中):                 Process Management. (line  589)
* qiflush() (於 curses 模組中):          Functions<3>.       (line  382)
* QName (xml.etree.ElementTree 中的類別): QName Objects.     (line    6)
* qsize() (asyncio.Queue 的方法):        Queue.              (line   74)
* qsize() (multiprocessing.Queue 的方法): Pipes and Queues.  (line   98)
* qsize() (queue.Queue 的方法):          Queue Objects.      (line    9)
* qsize() (queue.SimpleQueue 的方法):    SimpleQueue Objects.
                                                             (line    9)
* qualified name:                        Glossary.           (line 1100)
* quantiles() (statistics.NormalDist 的方法): NormalDist objects.
                                                             (line  103)
* quantiles() (於 statistics 模組中):    函式細節.           (line  400)
* quantize() (decimal.Context 的方法):   Context objects.    (line  459)
* quantize() (decimal.Decimal 的方法):   Decimal objects.    (line  461)
* QueryInfoKey() (於 winreg 模組中):     Functions<11>.      (line  323)
* QueryReflectionKey() (於 winreg 模組中): Functions<11>.    (line  520)
* QueryValue() (於 winreg 模組中):       Functions<11>.      (line  352)
* QueryValueEx() (於 winreg 模組中):     Functions<11>.      (line  372)
* Queue (asyncio 中的類別):              Queue.              (line    6)
* Queue (multiprocessing 中的類別):      Pipes and Queues.   (line   84)
* Queue (queue 中的類別):                queue --- A synchronized queue class.
                                                             (line   34)
* queue (sched.scheduler 的屬性):        Scheduler Objects.  (line   74)
* queue (模組):                          queue --- A synchronized queue class.
                                                             (line    6)
* Queue() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  180)
* QueueEmpty:                            Exceptions<7>.      (line    6)
* QueueFull:                             Exceptions<7>.      (line   11)
* QueueHandler (logging.handlers 中的類別): QueueHandler.    (line   21)
* QueueListener (logging.handlers 中的類別): QueueListener.  (line   25)
* quick_ratio() (difflib.SequenceMatcher 的方法): SequenceMatcher Objects.
                                                             (line  202)
* quit (pdb command):                    Debugger Commands.  (line  331)
* quit (內建變數):                       Constants added by the site module.
                                                             (line   11)
* quit() (ftplib.FTP 的方法):            FTP Objects.        (line  237)
* quit() (nntplib.NNTP 的方法):          Methods<3>.         (line   22)
* quit() (poplib.POP3 的方法):           POP3 Objects.       (line   82)
* quit() (smtplib.SMTP 的方法):          SMTP Objects.       (line  342)
* quopri (模組):                         quopri --- Encode and decode MIME quoted-printable data.
                                                             (line    6)
* quote() (於 email.utils 模組中):       email utils Miscellaneous utilities.
                                                             (line   47)
* quote() (於 shlex 模組中):             shlex --- Simple lexical analysis.
                                                             (line   44)
* quote() (於 urllib.parse 模組中):      URL Quoting.        (line   13)
* quoteattr() (於 xml.sax.saxutils 模組中): xml sax saxutils --- SAX Utilities.
                                                             (line   34)
* quotechar (csv.Dialect 的屬性):        Dialects and Formatting Parameters.
                                                             (line   52)
* quoted-printable; encoding:            quopri --- Encode and decode MIME quoted-printable data.
                                                             (line    8)
* quotes (shlex.shlex 的屬性):           shlex Objects.      (line  115)
* QUOTE_ALL (於 csv 模組中):             Module Contents<3>. (line  232)
* quote_from_bytes() (於 urllib.parse 模組中): URL Quoting.  (line   51)
* QUOTE_MINIMAL (於 csv 模組中):         Module Contents<3>. (line  236)
* QUOTE_NONE (於 csv 模組中):            Module Contents<3>. (line  250)
* QUOTE_NONNUMERIC (於 csv 模組中):      Module Contents<3>. (line  242)
* quote_plus() (於 urllib.parse 模組中): URL Quoting.        (line   40)
* quoting (csv.Dialect 的屬性):          Dialects and Formatting Parameters.
                                                             (line   58)
* r"; raw string literal:                String and Bytes literals.
                                                             (line   48)
* r’; raw string literal:                String and Bytes literals.
                                                             (line   48)
* radians() (於 math 模組中):            Angular conversion. (line   10)
* radians() (於 turtle 模組中):          Settings for measurement.
                                                             (line   28)
* RadioButtonGroup (msilib 中的類別):    GUI classes.        (line   29)
* radiogroup() (msilib.Dialog 的方法):   GUI classes.        (line   73)
* radix() (decimal.Context 的方法):      Context objects.    (line  464)
* radix() (decimal.Decimal 的方法):      Decimal objects.    (line  489)
* RADIXCHAR (於 locale 模組中):          locale --- Internationalization services.
                                                             (line  232)
* raise (2to3 fixer):                    Fixers.             (line  261)
* raise an exception:                    Exceptions.         (line    6)
* raise_on_defect (email.policy.Policy 的屬性): email policy Policy Objects.
                                                             (line  180)
* raise_signal() (於 signal 模組中):     Module contents<2>. (line  276)
* RAISE_VARARGS (opcode):                Python Bytecode Instructions.
                                                             (line  756)
* raising; exception:                    The raise statement.
                                                             (line    6)
* randbelow() (於 secrets 模組中):       Random numbers.     (line   19)
* randbits() (於 secrets 模組中):        Random numbers.     (line   23)
* randint() (於 random 模組中):          Functions for integers.
                                                             (line   23)
* Random (random 中的類別):              Alternative Generator.
                                                             (line    6)
* random (模組):                         random --- Generate pseudo-random numbers.
                                                             (line    6)
* random() (於 random 模組中):           Real-valued distributions.
                                                             (line   11)
* randrange() (於 random 模組中):        Functions for integers.
                                                             (line    6)
* RAND_add() (於 ssl 模組中):            Random generation.  (line   66)
* RAND_bytes() (於 ssl 模組中):          Random generation.  (line    6)
* RAND_egd() (於 ssl 模組中):            Random generation.  (line   50)
* RAND_pseudo_bytes() (於 ssl 模組中):   Random generation.  (line   23)
* RAND_status() (於 ssl 模組中):         Random generation.  (line   43)
* range (內建類別):                      Ranges.             (line   10)
* RARROW (於 token 模組中):              token --- Constants used with Python parse trees.
                                                             (line  230)
* ratecv() (於 audioop 模組中):          audioop --- Manipulate raw audio data.
                                                             (line  175)
* ratio() (difflib.SequenceMatcher 的方法): SequenceMatcher Objects.
                                                             (line  178)
* Rational (numbers 中的類別):           The numeric tower.  (line   41)
* raw (io.BufferedIOBase 的屬性):        I/O Base Classes.   (line  248)
* raw string:                            String and Bytes literals.
                                                             (line   36)
* raw() (pickle.PickleBuffer 的方法):    Module Interface.   (line  317)
* raw() (於 curses 模組中):              Functions<3>.       (line  389)
* RawArray() (於 multiprocessing.sharedctypes 模組中): The multiprocessing sharedctypes module.
                                                             (line   16)
* RawConfigParser (configparser 中的類別): RawConfigParser Objects.
                                                             (line    6)
* RawDescriptionHelpFormatter (argparse 中的類別): formatter_class.
                                                             (line   10)
* RawIOBase (io 中的類別):               I/O Base Classes.   (line  169)
* RawPen (turtle 中的類別):              Public classes.     (line    6)
* RawTextHelpFormatter (argparse 中的類別): formatter_class. (line   10)
* RawTurtle (turtle 中的類別):           Public classes.     (line    6)
* RawValue() (於 multiprocessing.sharedctypes 模組中): The multiprocessing sharedctypes module.
                                                             (line   33)
* raw_data_manager (於 email.contentmanager 模組中): Content Manager Instances.
                                                             (line   11)
* raw_decode() (json.JSONDecoder 的方法): Encoders and Decoders.
                                                             (line   92)
* raw_input (2to3 fixer):                Fixers.             (line  268)
* raw_input() (code.InteractiveConsole 的方法): Interactive Console Objects.
                                                             (line   43)
* RBRACE (於 token 模組中):              token --- Constants used with Python parse trees.
                                                             (line  130)
* rcpttos (smtpd.SMTPChannel 的屬性):    SMTPChannel Objects.
                                                             (line   79)
* re (re.Match 的屬性):                  Match Objects.      (line  190)
* re (模組):                             re --- Regular expression operations.
                                                             (line    6)
* read() (asyncio.StreamReader 的方法):  StreamReader.       (line   15)
* read() (chunk.Chunk 的方法):           chunk --- Read IFF chunked data.
                                                             (line  105)
* read() (codecs.StreamReader 的方法):   StreamReader Objects.
                                                             (line   34)
* read() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  113)
* read() (http.client.HTTPResponse 的方法): HTTPResponse Objects.
                                                             (line   13)
* read() (imaplib.IMAP4 的方法):         IMAP4 Objects.      (line  192)
* read() (io.BufferedIOBase 的方法):     I/O Base Classes.   (line  269)
* read() (io.BufferedReader 的方法):     Buffered Streams.   (line   80)
* read() (io.RawIOBase 的方法):          I/O Base Classes.   (line  182)
* read() (io.TextIOBase 的方法):         Text I/O<2>.        (line   52)
* read() (mimetypes.MimeTypes 的方法):   MimeTypes Objects.  (line   70)
* read() (mmap.mmap 的方法):             mmap --- Memory-mapped file support.
                                                             (line  225)
* read() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line   32)
* read() (ssl.MemoryBIO 的方法):         Memory BIO Support<2>.
                                                             (line  148)
* read() (ssl.SSLSocket 的方法):         SSL Sockets.        (line   71)
* read() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- Parser for robots txt.
                                                             (line   25)
* read() (zipfile.ZipFile 的方法):       ZipFile Objects.    (line  215)
* read() (於 os 模組中):                 File Descriptor Operations.
                                                             (line  549)
* read1() (io.BufferedIOBase 的方法):    I/O Base Classes.   (line  286)
* read1() (io.BufferedReader 的方法):    Buffered Streams.   (line   86)
* read1() (io.BytesIO 的方法):           Buffered Streams.   (line   43)
* READABLE (於 tkinter 模組中):          File Handlers.      (line   41)
* readable() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  164)
* readable() (io.IOBase 的方法):         I/O Base Classes.   (line   79)
* readall() (io.RawIOBase 的方法):       I/O Base Classes.   (line  197)
* reader() (於 csv 模組中):              Module Contents<3>. (line    8)
* ReadError:                             tarfile --- Read and write tar archive files.
                                                             (line  185)
* readexactly() (asyncio.StreamReader 的方法): StreamReader. (line   34)
* readfp() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  299)
* readfp() (mimetypes.MimeTypes 的方法): MimeTypes Objects.  (line   78)
* readframes() (aifc.aifc 的方法):       aifc --- Read and write AIFF and AIFC files.
                                                             (line   96)
* readframes() (sunau.AU_read 的方法):   AU_read Objects.    (line   47)
* readframes() (wave.Wave_read 的方法):  Wave_read Objects.  (line   46)
* readinto() (http.client.HTTPResponse 的方法): HTTPResponse Objects.
                                                             (line   17)
* readinto() (io.BufferedIOBase 的方法): I/O Base Classes.   (line  297)
* readinto() (io.RawIOBase 的方法):      I/O Base Classes.   (line  202)
* readinto1() (io.BufferedIOBase 的方法): I/O Base Classes.  (line  310)
* readinto1() (io.BytesIO 的方法):       Buffered Streams.   (line   49)
* readline (模組):                       readline --- GNU readline interface.
                                                             (line    6)
* readline() (asyncio.StreamReader 的方法): StreamReader.    (line   23)
* readline() (codecs.StreamReader 的方法): StreamReader Objects.
                                                             (line   60)
* readline() (distutils.text_file.TextFile 的方法): distutils text_file --- The TextFile class.
                                                             (line  111)
* readline() (imaplib.IMAP4 的方法):     IMAP4 Objects.      (line  197)
* readline() (io.IOBase 的方法):         I/O Base Classes.   (line   84)
* readline() (io.TextIOBase 的方法):     Text I/O<2>.        (line   58)
* readline() (mmap.mmap 的方法):         mmap --- Memory-mapped file support.
                                                             (line  240)
* readlines() (codecs.StreamReader 的方法): StreamReader Objects.
                                                             (line   71)
* readlines() (distutils.text_file.TextFile 的方法): distutils text_file --- The TextFile class.
                                                             (line  124)
* readlines() (io.IOBase 的方法):        I/O Base Classes.   (line   93)
* readlink() (於 os 模組中):             Files and Directories.
                                                             (line  576)
* readmodule() (於 pyclbr 模組中):       pyclbr --- Python module browser support.
                                                             (line   19)
* readmodule_ex() (於 pyclbr 模組中):    pyclbr --- Python module browser support.
                                                             (line   31)
* READONLY:                              Generic Attribute Management.
                                                             (line   92)
* readonly (memoryview 的屬性):          Memory Views.       (line  410)
* readPlist() (於 plistlib 模組中):      plistlib --- Generate and parse Mac OS X plist files.
                                                             (line  125)
* readPlistFromBytes() (於 plistlib 模組中): plistlib --- Generate and parse Mac OS X plist files.
                                                             (line  148)
* ReadTransport (asyncio 中的類別):      Transports Hierarchy.
                                                             (line   20)
* readuntil() (asyncio.StreamReader 的方法): StreamReader.   (line   43)
* readv() (於 os 模組中):                File Descriptor Operations.
                                                             (line  629)
* ready() (multiprocessing.pool.AsyncResult 的方法): Process Pools.
                                                             (line  209)
* read_all() (telnetlib.Telnet 的方法):  Telnet Objects.     (line   17)
* read_binary() (於 importlib.resources 模組中): importlib resources -- Resources.
                                                             (line   80)
* read_byte() (mmap.mmap 的方法):        mmap --- Memory-mapped file support.
                                                             (line  235)
* read_bytes() (pathlib.Path 的方法):    Methods<2>.         (line  262)
* read_bytes() (zipfile.Path 的方法):    Path Objects.       (line   59)
* read_dict() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  171)
* read_eager() (telnetlib.Telnet 的方法): Telnet Objects.    (line   35)
* read_environ() (於 wsgiref.handlers 模組中): wsgiref handlers -- server/gateway base classes.
                                                             (line  305)
* read_events() (xml.etree.ElementTree.XMLPullParser 的方法): XMLPullParser Objects.
                                                             (line   29)
* read_file() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  149)
* read_history_file() (於 readline 模組中): History file.    (line    8)
* read_init_file() (於 readline 模組中): Init file.          (line   13)
* read_lazy() (telnetlib.Telnet 的方法): Telnet Objects.     (line   43)
* read_mime_types() (於 mimetypes 模組中): mimetypes --- Map filenames to MIME types.
                                                             (line   98)
* READ_RESTRICTED:                       Generic Attribute Management.
                                                             (line   92)
* read_sb_data() (telnetlib.Telnet 的方法): Telnet Objects.  (line   59)
* read_some() (telnetlib.Telnet 的方法): Telnet Objects.     (line   21)
* read_string() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  161)
* read_text() (pathlib.Path 的方法):     Methods<2>.         (line  275)
* read_text() (zipfile.Path 的方法):     Path Objects.       (line   53)
* read_text() (於 importlib.resources 模組中): importlib resources -- Resources.
                                                             (line   91)
* read_token() (shlex.shlex 的方法):     shlex Objects.      (line   20)
* read_until() (telnetlib.Telnet 的方法): Telnet Objects.    (line    8)
* read_very_eager() (telnetlib.Telnet 的方法): Telnet Objects.
                                                             (line   27)
* read_very_lazy() (telnetlib.Telnet 的方法): Telnet Objects.
                                                             (line   51)
* read_windows_registry() (mimetypes.MimeTypes 的方法): MimeTypes Objects.
                                                             (line   86)
* Real (numbers 中的類別):               The numeric tower.  (line   28)
* real (numbers.Complex 的屬性):         The numeric tower.  (line   15)
* Real Media File Format:                chunk --- Read IFF chunked data.
                                                             (line    8)
* realloc():                             總覽<2>.            (line   33)
* realpath() (於 os.path 模組中):        os path --- Common pathname manipulations.
                                                             (line  294)
* REALTIME_PRIORITY_CLASS (於 subprocess 模組中): Windows Constants.
                                                             (line   87)
* real_max_memuse (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  127)
* real_quick_ratio() (difflib.SequenceMatcher 的方法): SequenceMatcher Objects.
                                                             (line  207)
* reap_children() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  791)
* reap_threads() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  654)
* reason (http.client.HTTPResponse 的屬性): HTTPResponse Objects.
                                                             (line   55)
* reason (ssl.SSLError 的屬性):          Exceptions<11>.     (line   27)
* reason (UnicodeError 的屬性):          Concrete exceptions.
                                                             (line  363)
* reason (urllib.error.HTTPError 的屬性): urllib error --- Exception classes raised by urllib request.
                                                             (line   45)
* reason (urllib.error.URLError 的屬性): urllib error --- Exception classes raised by urllib request.
                                                             (line   22)
* reattach() (tkinter.ttk.Treeview 的方法): ttk Treeview.    (line  247)
* rebinding; name:                       Assignment statements.
                                                             (line    6)
* reccontrols() (ossaudiodev.oss_mixer_device 的方法): Mixer Device Objects.
                                                             (line   53)
* received_data (smtpd.SMTPChannel 的屬性): SMTPChannel Objects.
                                                             (line   84)
* received_lines (smtpd.SMTPChannel 的屬性): SMTPChannel Objects.
                                                             (line   57)
* recent() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line  202)
* reconfigure() (io.TextIOWrapper 的方法): Text I/O<2>.      (line  172)
* records (unittest.TestCase 的屬性):    Test cases.         (line  426)
* record_original_stdout() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  375)
* rect() (於 cmath 模組中):              Conversions to and from polar coordinates.
                                                             (line   48)
* rectangle() (於 curses.textpad 模組中): curses textpad --- Text input widget for curses programs.
                                                             (line   15)
* RecursionError:                        Concrete exceptions.
                                                             (line  186)
* recursive_repr() (於 reprlib 模組中):  reprlib --- Alternate repr implementation.
                                                             (line   41)
* recv() (asyncore.dispatcher 的方法):   asyncore --- Asynchronous socket handler.
                                                             (line  203)
* recv() (multiprocessing.connection.Connection 的方法): Connection Objects<2>.
                                                             (line   24)
* recv() (socket.socket 的方法):         Socket Objects.     (line  219)
* recvfrom() (socket.socket 的方法):     Socket Objects.     (line  236)
* recvfrom_into() (socket.socket 的方法): Socket Objects.    (line  362)
* recvmsg() (socket.socket 的方法):      Socket Objects.     (line  254)
* recvmsg_into() (socket.socket 的方法): Socket Objects.     (line  325)
* recv_bytes() (multiprocessing.connection.Connection 的方法): Connection Objects<2>.
                                                             (line   65)
* recv_bytes_into() (multiprocessing.connection.Connection 的方法): Connection Objects<2>.
                                                             (line   79)
* recv_into() (socket.socket 的方法):    Socket Objects.     (line  372)
* redirect_request() (urllib.request.HTTPRedirectHandler 的方法): HTTPRedirectHandler Objects.
                                                             (line   15)
* redirect_stderr() (於 contextlib 模組中): Utilities.       (line  255)
* redirect_stdout() (於 contextlib 模組中): Utilities.       (line  216)
* redisplay() (於 readline 模組中):      Line buffer.        (line   19)
* redrawln() (curses.window 的方法):     Window Objects.     (line  459)
* redrawwin() (curses.window 的方法):    Window Objects.     (line  465)
* reduce (2to3 fixer):                   Fixers.             (line  272)
* reduce() (於 functools 模組中):        functools --- Higher-order functions and operations on callable objects.
                                                             (line  290)
* reducer_override() (pickle.Pickler 的方法): Module Interface.
                                                             (line  200)
* ref (weakref 中的類別):                weakref --- Weak references.
                                                             (line   85)
* refcount_test() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  647)
* reference count:                       Glossary.           (line 1127)
* reference counting:                    Objects values and types.
                                                             (line   37)
* ReferenceError:                        Concrete exceptions.
                                                             (line  195)
* ReferenceType (於 weakref 模組中):     weakref --- Weak references.
                                                             (line  288)
* refold_source (email.policy.EmailPolicy 的屬性): email policy Policy Objects.
                                                             (line  371)
* refresh() (curses.window 的方法):      Window Objects.     (line  470)
* register() (abc.ABCMeta 的方法):       abc --- Abstract Base Classes.
                                                             (line   69)
* register() (multiprocessing.managers.BaseManager 的方法): Managers.
                                                             (line   75)
* 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 --- Exit handlers.
                                                             (line   22)
* register() (於 codecs 模組中):         codecs --- Codec registry and base classes.
                                                             (line  150)
* register() (於 faulthandler 模組中):   Dumping the traceback on a user signal.
                                                             (line    6)
* register() (於 webbrowser 模組中):     webbrowser --- Convenient Web-browser controller.
                                                             (line   83)
* registerDOMImplementation() (於 xml.dom 模組中): Module Contents<4>.
                                                             (line    8)
* registerResult() (於 unittest 模組中): Signal Handling.    (line   35)
* register_adapter() (於 sqlite3 模組中): Module functions and constants.
                                                             (line  140)
* register_archive_format() (於 shutil 模組中): Archiving operations.
                                                             (line   81)
* register_at_fork() (於 os 模組中):     Process Management. (line  464)
* register_converter() (於 sqlite3 模組中): Module functions and constants.
                                                             (line  131)
* register_defect() (email.policy.Policy 的方法): email policy Policy Objects.
                                                             (line  229)
* register_dialect() (於 csv 模組中):    Module Contents<3>. (line   70)
* register_error() (於 codecs 模組中):   Error Handlers.     (line   88)
* register_function() (xmlrpc.server.CGIXMLRPCRequestHandler 的方法): CGIXMLRPCRequestHandler.
                                                             (line    9)
* register_function() (xmlrpc.server.SimpleXMLRPCServer 的方法): SimpleXMLRPCServer Objects.
                                                             (line   10)
* register_instance() (xmlrpc.server.CGIXMLRPCRequestHandler 的方法): CGIXMLRPCRequestHandler.
                                                             (line   26)
* register_instance() (xmlrpc.server.SimpleXMLRPCServer 的方法): SimpleXMLRPCServer Objects.
                                                             (line   27)
* register_introspection_functions() (xmlrpc.server.CGIXMLRPCRequestHandler 的方法): CGIXMLRPCRequestHandler.
                                                             (line   41)
* register_introspection_functions() (xmlrpc.server.SimpleXMLRPCServer 的方法): SimpleXMLRPCServer Objects.
                                                             (line   55)
* register_multicall_functions() (xmlrpc.server.CGIXMLRPCRequestHandler 的方法): CGIXMLRPCRequestHandler.
                                                             (line   47)
* register_multicall_functions() (xmlrpc.server.SimpleXMLRPCServer 的方法): SimpleXMLRPCServer Objects.
                                                             (line   60)
* register_namespace() (於 xml.etree.ElementTree 模組中): Functions<6>.
                                                             (line  181)
* register_optionflag() (於 doctest 模組中): Option Flags.   (line  172)
* register_shape() (於 turtle 模組中):   Settings and special methods.
                                                             (line   70)
* register_unpack_format() (於 shutil 模組中): Archiving operations.
                                                             (line  126)
* regular package:                       Glossary.           (line 1135)
* 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)
* relative; import:                      The import statement.
                                                             (line   98)
* relative; URL:                         urllib parse --- Parse URLs into components.
                                                             (line    8)
* relative_to() (pathlib.PurePath 的方法): Methods and properties.
                                                             (line  242)
* release() (asyncio.Condition 的方法):  Condition.          (line   79)
* release() (asyncio.Lock 的方法):       Lock.               (line   50)
* release() (asyncio.Semaphore 的方法):  Semaphore.          (line   55)
* release() (logging.Handler 的方法):    Handler Objects.    (line   31)
* release() (memoryview 的方法):         Memory Views.       (line  233)
* release() (multiprocessing.Lock 的方法): Synchronization primitives.
                                                             (line   91)
* release() (multiprocessing.RLock 的方法): Synchronization primitives.
                                                             (line  147)
* release() (pickle.PickleBuffer 的方法): Module Interface.  (line  325)
* release() (threading.Condition 的方法): Condition Objects. (line   91)
* release() (threading.Lock 的方法):     Lock Objects.       (line   73)
* release() (threading.RLock 的方法):    RLock Objects.      (line   66)
* release() (threading.Semaphore 的方法): Semaphore Objects. (line   63)
* release() (_thread.lock 的方法):       _thread --- Low-level threading API.
                                                             (line  150)
* release() (於 platform 模組中):        Cross Platform.     (line  116)
* releasebufferproc (C 型態):            Slot Type typedefs. (line  107)
* release_lock() (於 imp 模組中):        imp --- Access the import internals.
                                                             (line  293)
* reload (2to3 fixer):                   Fixers.             (line  276)
* reload() (於 imp 模組中):              imp --- Access the import internals.
                                                             (line  132)
* reload() (於 importlib 模組中):        Functions<10>.      (line   72)
* relpath() (於 os.path 模組中):         os path --- Common pathname manipulations.
                                                             (line  309)
* remainder() (decimal.Context 的方法):  Context objects.    (line  468)
* remainder() (於 math 模組中):          Number-theoretic and representation functions.
                                                             (line  205)
* remainder_near() (decimal.Context 的方法): Context objects.
                                                             (line  475)
* remainder_near() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  495)
* RemoteDisconnected:                    http client --- HTTP protocol client.
                                                             (line  183)
* remove() (array.array 的方法):         array --- 高效率的數值型態陣列.
                                                             (line  186)
* remove() (collections.deque 的方法):   deque objects.      (line   97)
* remove() (frozenset 的方法):           Set Types --- set frozenset.
                                                             (line  199)
* remove() (mailbox.Mailbox 的方法):     Mailbox objects.    (line   76)
* remove() (mailbox.MH 的方法):          MH.                 (line   76)
* remove() (sequence method):            Mutable Sequence Types.
                                                             (line   16)
* remove() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line  180)
* remove() (於 os 模組中):               Files and Directories.
                                                             (line  612)
* removeAttribute() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   52)
* removeAttributeNode() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   57)
* removeAttributeNS() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   62)
* removeChild() (xml.dom.Node 的方法):   Node Objects.       (line  128)
* removedirs() (於 os 模組中):           Files and Directories.
                                                             (line  636)
* removeFilter() (logging.Handler 的方法): Handler Objects.  (line   56)
* removeFilter() (logging.Logger 的方法): Logger Objects.    (line  255)
* removeHandler() (logging.Logger 的方法): Logger Objects.   (line  272)
* removeHandler() (於 unittest 模組中):  Signal Handling.    (line   52)
* removeResult() (於 unittest 模組中):   Signal Handling.    (line   46)
* removexattr() (於 os 模組中):          Linux extended attributes.
                                                             (line   41)
* remove_child_handler() (asyncio.AbstractChildWatcher 的方法): Process Watchers.
                                                             (line   52)
* remove_done_callback() (asyncio.Future 的方法): Future Object.
                                                             (line  101)
* remove_done_callback() (asyncio.Task 的方法): Task Object. (line  157)
* 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 的方法): Maildir.         (line   76)
* remove_folder() (mailbox.MH 的方法):   MH.                 (line   47)
* remove_header() (urllib.request.Request 的方法): Request Objects.
                                                             (line   97)
* remove_history_item() (於 readline 模組中): History list.  (line   26)
* remove_label() (mailbox.BabylMessage 的方法): BabylMessage.
                                                             (line   59)
* remove_option() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  265)
* remove_option() (optparse.OptionParser 的方法): Querying and manipulating your option parser.
                                                             (line   47)
* remove_pyc() (msilib.Directory 的方法): Directory Objects. (line   46)
* remove_reader() (asyncio.loop 的方法): Watching file descriptors.
                                                             (line   12)
* remove_section() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  272)
* remove_sequence() (mailbox.MHMessage 的方法): MHMessage.   (line   46)
* remove_signal_handler() (asyncio.loop 的方法): Unix signals.
                                                             (line   26)
* remove_tree() (於 distutils.dir_util 模組中): distutils dir_util --- Directory tree operations.
                                                             (line   60)
* remove_writer() (asyncio.loop 的方法): Watching file descriptors.
                                                             (line   25)
* rename() (ftplib.FTP 的方法):          FTP Objects.        (line  202)
* rename() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line  207)
* rename() (pathlib.Path 的方法):        Methods<2>.         (line  290)
* rename() (於 os 模組中):               Files and Directories.
                                                             (line  653)
* renames (2to3 fixer):                  Fixers.             (line  280)
* renames() (於 os 模組中):              Files and Directories.
                                                             (line  687)
* reopenIfNeeded() (logging.handlers.WatchedFileHandler 的方法): WatchedFileHandler.
                                                             (line   37)
* reorganize() (dbm.gnu.gdbm 的方法):    dbm gnu --- GNU's reinterpretation of dbm.
                                                             (line  104)
* repeat() (timeit.Timer 的方法):        Python Interface.   (line  107)
* repeat() (於 itertools 模組中):        Itertool functions. (line  493)
* repeat() (於 timeit 模組中):           Python Interface.   (line   18)
* repetition; operation:                 Common Sequence Operations.
                                                             (line   21)
* replace() (bytearray 的方法):          Bytes and Bytearray Operations.
                                                             (line  145)
* replace() (bytes 的方法):              Bytes and Bytearray Operations.
                                                             (line  145)
* replace() (curses.panel.Panel 的方法): Panel Objects.      (line   39)
* replace() (datetime.date 的方法):      date Objects.       (line  166)
* replace() (datetime.datetime 的方法):  datetime Objects.   (line  412)
* replace() (datetime.time 的方法):      time Objects.       (line  139)
* replace() (inspect.Parameter 的方法):  Introspecting callables with the Signature object.
                                                             (line  252)
* replace() (inspect.Signature 的方法):  Introspecting callables with the Signature object.
                                                             (line  110)
* replace() (pathlib.Path 的方法):       Methods<2>.         (line  313)
* replace() (str 的方法):                String Methods<2>.  (line  338)
* replace() (types.CodeType 的方法):     Standard Interpreter Types.
                                                             (line   63)
* replace() (於 dataclasses 模組中):     Module-level decorators classes and functions.
                                                             (line  345)
* replace() (於 os 模組中):              Files and Directories.
                                                             (line  705)
* replaceChild() (xml.dom.Node 的方法):  Node Objects.       (line  135)
* ReplacePackage() (於 modulefinder 模組中): modulefinder --- Find modules used by a script.
                                                             (line   21)
* replace_errors() (於 codecs 模組中):   Error Handlers.     (line  133)
* replace_header() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  299)
* replace_header() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  409)
* replace_history_item() (於 readline 模組中): History list. (line   32)
* replace_whitespace (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  171)
* report() (filecmp.dircmp 的方法):      The dircmp class.   (line   18)
* report() (modulefinder.ModuleFinder 的方法): modulefinder --- Find modules used by a script.
                                                             (line   38)
* REPORTING_FLAGS (於 doctest 模組中):   Option Flags.       (line  164)
* REPORT_CDIFF (於 doctest 模組中):      Option Flags.       (line  126)
* report_failure() (doctest.DocTestRunner 的方法): DocTestRunner objects.
                                                             (line   70)
* report_full_closure() (filecmp.dircmp 的方法): The dircmp class.
                                                             (line   28)
* REPORT_NDIFF (於 doctest 模組中):      Option Flags.       (line  131)
* REPORT_ONLY_FIRST_FAILURE (於 doctest 模組中): Option Flags.
                                                             (line  140)
* report_partial_closure() (filecmp.dircmp 的方法): The dircmp class.
                                                             (line   23)
* report_start() (doctest.DocTestRunner 的方法): DocTestRunner objects.
                                                             (line   48)
* report_success() (doctest.DocTestRunner 的方法): DocTestRunner objects.
                                                             (line   59)
* REPORT_UDIFF (於 doctest 模組中):      Option Flags.       (line  121)
* report_unexpected_exception() (doctest.DocTestRunner 的方法): DocTestRunner objects.
                                                             (line   81)
* repr (2to3 fixer):                     Fixers.             (line  284)
* Repr (reprlib 中的類別):               reprlib --- Alternate repr implementation.
                                                             (line   17)
* repr() (built-in function); __repr__() (object method): Basic customization.
                                                             (line  113)
* repr() (reprlib.Repr 的方法):          Repr Objects.       (line   47)
* repr() (內建函式):                     內建函式.           (line 1415)
* repr() (於 reprlib 模組中):            reprlib --- Alternate repr implementation.
                                                             (line   31)
* repr1() (reprlib.Repr 的方法):         Repr Objects.       (line   52)
* reprfunc (C 型態):                     Slot Type typedefs. (line   49)
* reprlib (模組):                        reprlib --- Alternate repr implementation.
                                                             (line    6)
* Request (urllib.request 中的類別):     urllib request --- Extensible library for opening URLs.
                                                             (line  182)
* request() (http.client.HTTPConnection 的方法): HTTPConnection Objects.
                                                             (line    8)
* RequestHandlerClass (socketserver.BaseServer 的屬性): Server Objects<2>.
                                                             (line   71)
* requestline (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line   81)
* request_queue_size (socketserver.BaseServer 的屬性): Server Objects<2>.
                                                             (line   98)
* request_rate() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- Parser for robots txt.
                                                             (line   60)
* request_uri() (於 wsgiref.util 模組中): wsgiref util -- WSGI environment utilities.
                                                             (line   25)
* request_version (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line   99)
* requires() (於 test.support 模組中):   test support --- Utilities for the Python test suite.
                                                             (line  211)
* requires_bz2() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  616)
* requires_docstrings() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  628)
* requires_freebsd_version() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  586)
* requires_gzip() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  612)
* requires_IEEE_754() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  604)
* requires_linux_version() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  592)
* requires_lzma() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  620)
* requires_mac_version() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  598)
* requires_resource() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  624)
* requires_zlib() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  608)
* reserved (zipfile.ZipInfo 的屬性):     ZipInfo Objects.    (line  111)
* reserved word:                         Keywords.           (line    6)
* RESERVED_FUTURE (於 uuid 模組中):      uuid --- UUID objects according to RFC 4122.
                                                             (line  236)
* RESERVED_MICROSOFT (於 uuid 模組中):   uuid --- UUID objects according to RFC 4122.
                                                             (line  232)
* RESERVED_NCS (於 uuid 模組中):         uuid --- UUID objects according to RFC 4122.
                                                             (line  224)
* reset() (bdb.Bdb 的方法):              bdb --- Debugger framework.
                                                             (line  106)
* reset() (codecs.IncrementalDecoder 的方法): IncrementalDecoder Objects.
                                                             (line   40)
* reset() (codecs.IncrementalEncoder 的方法): IncrementalEncoder Objects.
                                                             (line   35)
* reset() (codecs.StreamReader 的方法):  StreamReader Objects.
                                                             (line   83)
* reset() (codecs.StreamWriter 的方法):  StreamWriter Objects.
                                                             (line   41)
* reset() (contextvars.ContextVar 的方法): Context Variables.
                                                             (line   58)
* reset() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line   23)
* reset() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line  169)
* reset() (pipes.Template 的方法):       Template Objects.   (line    8)
* reset() (threading.Barrier 的方法):    Barrier Objects.    (line   71)
* reset() (xdrlib.Packer 的方法):        Packer Objects.     (line   12)
* reset() (xdrlib.Unpacker 的方法):      Unpacker Objects.   (line    8)
* reset() (xml.dom.pulldom.DOMEventStream 的方法): DOMEventStream Objects.
                                                             (line   37)
* reset() (xml.sax.xmlreader.IncrementalParser 的方法): IncrementalParser Objects.
                                                             (line   19)
* reset() (於 turtle 模組中):            Window control.     (line   51)
* resetbuffer() (code.InteractiveConsole 的方法): Interactive Console Objects.
                                                             (line   39)
* resetlocale() (於 locale 模組中):      locale --- Internationalization services.
                                                             (line  367)
* resetscreen() (於 turtle 模組中):      Window control.     (line   51)
* resetty() (於 curses 模組中):          Functions<3>.       (line  405)
* resetwarnings() (於 warnings 模組中):  Available Functions.
                                                             (line   98)
* reset_mock() (unittest.mock.AsyncMock 的方法): The Mock Class.
                                                             (line  860)
* reset_mock() (unittest.mock.Mock 的方法): The Mock Class.  (line  198)
* reset_prog_mode() (於 curses 模組中):  Functions<3>.       (line  395)
* reset_shell_mode() (於 curses 模組中): Functions<3>.       (line  400)
* resize() (curses.window 的方法):       Window Objects.     (line  489)
* resize() (mmap.mmap 的方法):           mmap --- Memory-mapped file support.
                                                             (line  245)
* resize() (於 ctypes 模組中):           Utility functions.  (line  163)
* resizemode() (於 turtle 模組中):       Appearance.         (line   24)
* resizeterm() (於 curses 模組中):       Functions<3>.       (line  420)
* resize_term() (於 curses 模組中):      Functions<3>.       (line  410)
* resolution (datetime.date 的屬性):     date Objects.       (line   95)
* resolution (datetime.datetime 的屬性): datetime Objects.   (line  257)
* resolution (datetime.time 的屬性):     time Objects.       (line   42)
* resolution (datetime.timedelta 的屬性): timedelta Objects. (line   84)
* resolve() (pathlib.Path 的方法):       Methods<2>.         (line  325)
* resolveEntity() (xml.sax.handler.EntityResolver 的方法): EntityResolver Objects.
                                                             (line    6)
* resolve_bases() (於 types 模組中):     Dynamic Type Creation.
                                                             (line   57)
* resolve_name() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   80)
* Resource (於 importlib.resources 模組中): importlib resources -- Resources.
                                                             (line   45)
* resource (模組):                       resource --- Resource usage information.
                                                             (line    6)
* ResourceDenied:                        test support --- Utilities for the Python test suite.
                                                             (line   22)
* ResourceLoader (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  348)
* ResourceReader (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  277)
* ResourceWarning:                       Warnings.           (line   59)
* resource_path() (importlib.abc.ResourceReader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  317)
* response (nntplib.NNTPError 的屬性):   nntplib --- NNTP protocol client.
                                                             (line  127)
* response() (imaplib.IMAP4 的方法):     IMAP4 Objects.      (line  211)
* ResponseNotReady:                      http client --- HTTP protocol client.
                                                             (line  169)
* responses (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  171)
* responses (於 http.client 模組中):     http client --- HTTP protocol client.
                                                             (line  204)
* restart (pdb command):                 Debugger Commands.  (line  322)
* restore() (於 difflib 模組中):         difflib --- Helpers for computing deltas.
                                                             (line  274)
* RESTRICTED:                            Generic Attribute Management.
                                                             (line   92)
* restricted; execution:                 Builtins and restricted execution.
                                                             (line    6)
* restype (ctypes._FuncPtr 的屬性):      Foreign functions.  (line   22)
* result() (asyncio.Future 的方法):      Future Object.      (line   27)
* result() (asyncio.Task 的方法):        Task Object.        (line  119)
* result() (concurrent.futures.Future 的方法): Future Objects.
                                                             (line   38)
* results() (trace.Trace 的方法):        Programmatic Interface.
                                                             (line   40)
* resume_reading() (asyncio.ReadTransport 的方法): Read-only Transports.
                                                             (line   21)
* resume_writing() (asyncio.BaseProtocol 的方法): Base Protocol.
                                                             (line   44)
* retr() (poplib.POP3 的方法):           POP3 Objects.       (line   62)
* retrbinary() (ftplib.FTP 的方法):      FTP Objects.        (line   84)
* retrieve() (urllib.request.URLopener 的方法): Legacy interface.
                                                             (line  113)
* retrlines() (ftplib.FTP 的方法):       FTP Objects.        (line   96)
* return (pdb command):                  Debugger Commands.  (line  188)
* returncode (asyncio.asyncio.subprocess.Process 的屬性): Interacting with Subprocesses.
                                                             (line  140)
* returncode (subprocess.CalledProcessError 的屬性): Using the subprocess Module.
                                                             (line  196)
* returncode (subprocess.CompletedProcess 的屬性): Using the subprocess Module.
                                                             (line  101)
* returncode (subprocess.Popen 的屬性):  Popen Objects.      (line  145)
* return_annotation (inspect.Signature 的屬性): Introspecting callables with the Signature object.
                                                             (line   89)
* return_ok() (http.cookiejar.CookiePolicy 的方法): CookiePolicy Objects.
                                                             (line   18)
* RETURN_VALUE (opcode):                 Python Bytecode Instructions.
                                                             (line  342)
* return_value (unittest.mock.Mock 的屬性): The Mock Class.  (line  321)
* retval (pdb command):                  Debugger Commands.  (line  341)
* reverse() (array.array 的方法):        array --- 高效率的數值型態陣列.
                                                             (line  190)
* reverse() (collections.deque 的方法):  deque objects.      (line  102)
* reverse() (sequence method):           Mutable Sequence Types.
                                                             (line   16)
* reverse() (於 audioop 模組中):         audioop --- Manipulate raw audio data.
                                                             (line  188)
* reversed() (內建函式):                 內建函式.           (line 1427)
* reverse_order() (pstats.Stats 的方法): The Stats Class.    (line  157)
* reverse_pointer (ipaddress.IPv4Address 的屬性): Address objects.
                                                             (line   71)
* reverse_pointer (ipaddress.IPv6Address 的屬性): Address objects.
                                                             (line  165)
* Reversible (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  143)
* Reversible (typing 中的類別):          Classes functions and decorators.
                                                             (line  155)
* revert() (http.cookiejar.FileCookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line  141)
* rewind() (aifc.aifc 的方法):           aifc --- Read and write AIFF and AIFC files.
                                                             (line  102)
* rewind() (sunau.AU_read 的方法):       AU_read Objects.    (line   53)
* rewind() (wave.Wave_read 的方法):      Wave_read Objects.  (line   51)
* rfc2109 (http.cookiejar.Cookie 的屬性): Cookie Objects<2>. (line   68)
* rfc2109_as_netscape (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line   83)
* rfc2965 (http.cookiejar.CookiePolicy 的屬性): CookiePolicy Objects.
                                                             (line   72)
* rfc822_escape() (於 distutils.util 模組中): distutils util --- Miscellaneous other utility functions.
                                                             (line  171)
* RFC; RFC 1014:                         xdrlib --- Encode and decode XDR data.
                                                             (line   11)
* RFC; RFC 1014 <1>:                     xdrlib --- Encode and decode XDR data.
                                                             (line   32)
* RFC; RFC 1123:                         Functions<2>.       (line  615)
* RFC; RFC 1321:                         hashlib --- Secure hashes and message digests.
                                                             (line   13)
* RFC; RFC 1422:                         Certificates.       (line   38)
* RFC; RFC 1422 <1>:                     LibreSSL support.   (line   29)
* RFC; RFC 1521:                         base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  266)
* RFC; RFC 1521 <1>:                     quopri --- Encode and decode MIME quoted-printable data.
                                                             (line   11)
* RFC; RFC 1521 <2>:                     quopri --- Encode and decode MIME quoted-printable data.
                                                             (line   37)
* RFC; RFC 1522:                         binascii --- Convert between binary and ASCII.
                                                             (line   71)
* RFC; RFC 1522 <1>:                     quopri --- Encode and decode MIME quoted-printable data.
                                                             (line   25)
* RFC; RFC 1522 <2>:                     quopri --- Encode and decode MIME quoted-printable data.
                                                             (line   39)
* RFC; RFC 1524:                         mailcap --- Mailcap file handling.
                                                             (line   19)
* RFC; RFC 1524 <1>:                     mailcap --- Mailcap file handling.
                                                             (line   38)
* RFC; RFC 1730:                         imaplib --- IMAP4 protocol client.
                                                             (line   14)
* RFC; RFC 1738:                         URL Quoting.        (line  180)
* RFC; RFC 1750:                         Random generation.  (line   70)
* RFC; RFC 1766:                         locale --- Internationalization services.
                                                             (line  322)
* RFC; RFC 1766 <1>:                     locale --- Internationalization services.
                                                             (line  333)
* RFC; RFC 1808:                         urllib.             (line   23)
* RFC; RFC 1808 <1>:                     URL Parsing.        (line   33)
* RFC; RFC 1808 <2>:                     URL Quoting.        (line  174)
* RFC; RFC 1832:                         xdrlib --- Encode and decode XDR data.
                                                             (line   36)
* RFC; RFC 1832 <1>:                     xdrlib --- Encode and decode XDR data.
                                                             (line   38)
* RFC; RFC 1869:                         smtplib --- SMTP protocol client.
                                                             (line   13)
* RFC; RFC 1869 <1>:                     smtplib --- SMTP protocol client.
                                                             (line  181)
* RFC; RFC 1870:                         smtpd<3>.           (line    7)
* RFC; RFC 1870 <1>:                     smtpd --- SMTP Server.
                                                             (line   26)
* RFC; RFC 1870 <2>:                     SMTPChannel Objects.
                                                             (line  125)
* RFC; RFC 1939:                         poplib --- POP3 protocol client.
                                                             (line   11)
* RFC; RFC 1939 <1>:                     poplib --- POP3 protocol client.
                                                             (line   13)
* RFC; RFC 2033:                         New and Improved Modules<2>.
                                                             (line  569)
* RFC; RFC 2045:                         email --- An email and MIME handling package.
                                                             (line   16)
* RFC; RFC 2045 <1>:                     email message Representing an email message.
                                                             (line  314)
* RFC; RFC 2045 <2>:                     email message Representing an email message.
                                                             (line  316)
* RFC; RFC 2045 <3>:                     email message Representing an email message.
                                                             (line  319)
* RFC; RFC 2045 <4>:                     email headerregistry Custom Header Objects.
                                                             (line  239)
* RFC; RFC 2045 <5>:                     email headerregistry Custom Header Objects.
                                                             (line  297)
* RFC; RFC 2045 <6>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  422)
* RFC; RFC 2045 <7>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  426)
* RFC; RFC 2045 <8>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  429)
* RFC; RFC 2045 <9>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  526)
* RFC; RFC 2045 <10>:                    email header Internationalized headers.
                                                             (line   31)
* RFC; RFC 2045 <11>:                    base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   26)
* RFC; RFC 2045 <12>:                    base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   27)
* RFC; RFC 2045 <13>:                    base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  230)
* RFC; RFC 2045 <14>:                    base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  238)
* RFC; RFC 2045#section-6.8:             Binary Objects.     (line   31)
* RFC; RFC 2046:                         email --- An email and MIME handling package.
                                                             (line   16)
* RFC; RFC 2046 <1>:                     Content Manager Instances.
                                                             (line   85)
* RFC; RFC 2046 <2>:                     email header Internationalized headers.
                                                             (line   32)
* RFC; RFC 2047:                         PEP 3333 Python Web Server Gateway Interface v1 0 1.
                                                             (line   21)
* RFC; RFC 2047 <1>:                     email<5>.           (line   27)
* RFC; RFC 2047 <2>:                     email --- An email and MIME handling package.
                                                             (line   16)
* RFC; RFC 2047 <3>:                     email policy Policy Objects.
                                                             (line  347)
* RFC; RFC 2047 <4>:                     email policy Policy Objects.
                                                             (line  353)
* RFC; RFC 2047 <5>:                     email headerregistry Custom Header Objects.
                                                             (line   78)
* RFC; RFC 2047 <6>:                     email headerregistry Custom Header Objects.
                                                             (line  123)
* RFC; RFC 2047 <7>:                     email headerregistry Custom Header Objects.
                                                             (line  128)
* RFC; RFC 2047 <8>:                     email header Internationalized headers.
                                                             (line   32)
* RFC; RFC 2047 <9>:                     email header Internationalized headers.
                                                             (line   55)
* RFC; RFC 2047 <10>:                    email header Internationalized headers.
                                                             (line  117)
* RFC; RFC 2047 <11>:                    email header Internationalized headers.
                                                             (line  141)
* RFC; RFC 2047 <12>:                    email utils Miscellaneous utilities.
                                                             (line   74)
* RFC; RFC 2060:                         imaplib --- IMAP4 protocol client.
                                                             (line   13)
* RFC; RFC 2060 <1>:                     IMAP4 Objects.      (line  311)
* RFC; RFC 2068:                         http cookies --- HTTP state management.
                                                             (line   16)
* RFC; RFC 2104:                         New and Improved Modules<3>.
                                                             (line   35)
* RFC; RFC 2104 <1>:                     hmac --- Keyed-Hashing for Message Authentication.
                                                             (line   10)
* RFC; RFC 2109:                         http cookies --- HTTP state management.
                                                             (line   15)
* RFC; RFC 2109 <1>:                     http cookies --- HTTP state management.
                                                             (line   35)
* RFC; RFC 2109 <2>:                     http cookies --- HTTP state management.
                                                             (line   65)
* RFC; RFC 2109 <3>:                     Morsel Objects.     (line    8)
* RFC; RFC 2109 <4>:                     Morsel Objects.     (line   11)
* RFC; RFC 2109 <5>:                     Morsel Objects.     (line   98)
* RFC; RFC 2109 <6>:                     Morsel Objects.     (line  110)
* RFC; RFC 2109 <7>:                     http cookiejar --- Cookie handling for HTTP clients.
                                                             (line   17)
* RFC; RFC 2109 <8>:                     http cookiejar --- Cookie handling for HTTP clients.
                                                             (line   99)
* RFC; RFC 2109 <9>:                     http cookiejar --- Cookie handling for HTTP clients.
                                                             (line  111)
* RFC; RFC 2109 <10>:                    http cookiejar --- Cookie handling for HTTP clients.
                                                             (line  138)
* RFC; RFC 2109 <11>:                    DefaultCookiePolicy Objects.
                                                             (line   86)
* RFC; RFC 2109 <12>:                    Cookie Objects<2>.  (line   11)
* RFC; RFC 2109 <13>:                    Cookie Objects<2>.  (line   23)
* RFC; RFC 2109 <14>:                    Cookie Objects<2>.  (line   70)
* RFC; RFC 2183:                         email --- An email and MIME handling package.
                                                             (line   16)
* RFC; RFC 2183 <1>:                     email message Representing an email message.
                                                             (line  458)
* RFC; RFC 2183 <2>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  633)
* RFC; RFC 2231:                         email --- An email and MIME handling package.
                                                             (line   16)
* RFC; RFC 2231 <1>:                     email message Representing an email message.
                                                             (line  278)
* RFC; RFC 2231 <2>:                     email message Representing an email message.
                                                             (line  281)
* RFC; RFC 2231 <3>:                     email message Representing an email message.
                                                             (line  363)
* RFC; RFC 2231 <4>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  385)
* RFC; RFC 2231 <5>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  389)
* RFC; RFC 2231 <6>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  491)
* RFC; RFC 2231 <7>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  499)
* RFC; RFC 2231 <8>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  533)
* RFC; RFC 2231 <9>:                     email header Internationalized headers.
                                                             (line   32)
* RFC; RFC 2231 <10>:                    email utils Miscellaneous utilities.
                                                             (line  176)
* RFC; RFC 2231 <11>:                    email utils Miscellaneous utilities.
                                                             (line  180)
* RFC; RFC 2231 <12>:                    email utils Miscellaneous utilities.
                                                             (line  189)
* RFC; RFC 2231 <13>:                    email utils Miscellaneous utilities.
                                                             (line  196)
* RFC; RFC 2231 <14>:                    email utils Miscellaneous utilities.
                                                             (line  205)
* RFC; RFC 2295:                         HTTP status codes.  (line  175)
* RFC; RFC 2342:                         New and Improved Modules<3>.
                                                             (line   93)
* RFC; RFC 2342 <1>:                     IMAP4 Objects.      (line  164)
* RFC; RFC 2368:                         URL Quoting.        (line  170)
* RFC; RFC 2373:                         Address objects.    (line   89)
* RFC; RFC 2373 <1>:                     Address objects.    (line  108)
* RFC; RFC 2373 <2>:                     Address objects.    (line  117)
* RFC; RFC 2396:                         urllib parse<2>.    (line    6)
* RFC; RFC 2396 <1>:                     urllib.             (line   24)
* RFC; RFC 2396 <2>:                     URL Parsing.        (line  244)
* RFC; RFC 2396 <3>:                     URL Quoting.        (line   24)
* RFC; RFC 2396 <4>:                     URL Quoting.        (line  165)
* RFC; RFC 2397:                         DataHandler Objects.
                                                             (line    9)
* RFC; RFC 2449:                         POP3 Objects.       (line   26)
* RFC; RFC 2487:                         New and Improved Modules<3>.
                                                             (line   85)
* RFC; RFC 2518:                         HTTP status codes.  (line   19)
* RFC; RFC 2595:                         poplib --- POP3 protocol client.
                                                             (line   14)
* RFC; RFC 2595 <1>:                     POP3 Objects.       (line  115)
* RFC; RFC 2616:                         PEP 3333 Python Web Server Gateway Interface v1 0 1.
                                                             (line   20)
* RFC; RFC 2616 <1>:                     wsgiref util -- WSGI environment utilities.
                                                             (line  112)
* RFC; RFC 2616 <2>:                     wsgiref validate --- WSGI conformance checker.
                                                             (line   27)
* RFC; RFC 2616 <3>:                     HTTPRedirectHandler Objects.
                                                             (line    8)
* RFC; RFC 2616 <4>:                     HTTPRedirectHandler Objects.
                                                             (line   28)
* RFC; RFC 2616 <5>:                     Legacy interface.   (line  164)
* RFC; RFC 2616 <6>:                     urllib error --- Exception classes raised by urllib request.
                                                             (line   40)
* RFC; RFC 2616 <7>:                     簡介<15>.           (line   29)
* RFC; RFC 2616 <8>:                     HTTPError.          (line   15)
* RFC; RFC 2616 <9>:                     Error Codes.        (line   12)
* RFC; RFC 2732:                         urllib parse<3>.    (line   10)
* RFC; RFC 2732 <1>:                     New and Improved Modules.
                                                             (line  638)
* RFC; RFC 2732 <2>:                     URL Quoting.        (line  161)
* RFC; RFC 2774:                         HTTP status codes.  (line  184)
* RFC; RFC 2818:                         ssl<9>.             (line   16)
* RFC; RFC 2818 <1>:                     Certificate handling.
                                                             (line   11)
* RFC; RFC 2821:                         email --- An email and MIME handling package.
                                                             (line   12)
* RFC; RFC 2822:                         New and Improved Modules<3>.
                                                             (line   97)
* RFC; RFC 2822 <1>:                     標準模組庫.         (line   13)
* RFC; RFC 2822 <2>:                     Functions<2>.       (line  346)
* RFC; RFC 2822 <3>:                     Functions<2>.       (line  616)
* RFC; RFC 2822 <4>:                     email message Message Representing an email message using the compat32 API.
                                                             (line  274)
* RFC; RFC 2822 <5>:                     email header Internationalized headers.
                                                             (line   20)
* RFC; RFC 2822 <6>:                     email header Internationalized headers.
                                                             (line   23)
* RFC; RFC 2822 <7>:                     email header Internationalized headers.
                                                             (line   31)
* RFC; RFC 2822 <8>:                     email header Internationalized headers.
                                                             (line   88)
* RFC; RFC 2822 <9>:                     email header Internationalized headers.
                                                             (line  116)
* RFC; RFC 2822 <10>:                    email header Internationalized headers.
                                                             (line  134)
* RFC; RFC 2822 <11>:                    email utils Miscellaneous utilities.
                                                             (line   31)
* RFC; RFC 2822 <12>:                    email utils Miscellaneous utilities.
                                                             (line   98)
* RFC; RFC 2822 <13>:                    email utils Miscellaneous utilities.
                                                             (line  101)
* RFC; RFC 2822 <14>:                    email utils Miscellaneous utilities.
                                                             (line  223)
* RFC; RFC 2822 <15>:                    email utils Miscellaneous utilities.
                                                             (line  142)
* RFC; RFC 2822 <16>:                    Message objects.    (line   17)
* RFC; RFC 2822 <17>:                    http client --- HTTP protocol client.
                                                             (line  111)
* RFC; RFC 2822 <18>:                    http server --- HTTP servers.
                                                             (line  111)
* RFC; RFC 2964:                         http cookiejar --- Cookie handling for HTTP clients.
                                                             (line  151)
* RFC; RFC 2965:                         urllib request --- Extensible library for opening URLs.
                                                             (line  225)
* RFC; RFC 2965 <1>:                     urllib request --- Extensible library for opening URLs.
                                                             (line  233)
* RFC; RFC 2965 <2>:                     Request Objects.    (line   49)
* RFC; RFC 2965 <3>:                     http cookiejar --- Cookie handling for HTTP clients.
                                                             (line   16)
* RFC; RFC 2965 <4>:                     http cookiejar --- Cookie handling for HTTP clients.
                                                             (line   99)
* RFC; RFC 2965 <5>:                     http cookiejar --- Cookie handling for HTTP clients.
                                                             (line  111)
* RFC; RFC 2965 <6>:                     http cookiejar --- Cookie handling for HTTP clients.
                                                             (line  140)
* RFC; RFC 2965 <7>:                     http cookiejar --- Cookie handling for HTTP clients.
                                                             (line  142)
* RFC; RFC 2965 <8>:                     http cookiejar --- Cookie handling for HTTP clients.
                                                             (line  149)
* RFC; RFC 2965 <9>:                     FileCookieJar subclasses and co-operation with web browsers.
                                                             (line   16)
* RFC; RFC 2965 <10>:                    CookiePolicy Objects.
                                                             (line   74)
* RFC; RFC 2965 <11>:                    CookiePolicy Objects.
                                                             (line   79)
* RFC; RFC 2965 <12>:                    DefaultCookiePolicy Objects.
                                                             (line    8)
* RFC; RFC 2965 <13>:                    DefaultCookiePolicy Objects.
                                                             (line   90)
* RFC; RFC 2965 <14>:                    DefaultCookiePolicy Objects.
                                                             (line  101)
* RFC; RFC 2965 <15>:                    DefaultCookiePolicy Objects.
                                                             (line  105)
* RFC; RFC 2965 <16>:                    DefaultCookiePolicy Objects.
                                                             (line  114)
* RFC; RFC 2965 <17>:                    DefaultCookiePolicy Objects.
                                                             (line  151)
* RFC; RFC 2965 <18>:                    Cookie Objects<2>.  (line   23)
* RFC; RFC 2965 <19>:                    Examples<24>.       (line   25)
* RFC; RFC 2980:                         nntplib --- NNTP protocol client.
                                                             (line   13)
* RFC; RFC 2980 <1>:                     Methods<3>.         (line  317)
* RFC; RFC 3056:                         Address objects.    (line  205)
* RFC; RFC 3171:                         Address objects.    (line   88)
* RFC; RFC 3207:                         New and Improved Modules<2>.
                                                             (line  574)
* RFC; RFC 3229:                         HTTP status codes.  (line   49)
* RFC; RFC 3280:                         SSL Sockets.        (line  150)
* RFC; RFC 3330:                         Address objects.    (line  116)
* RFC; RFC 3339:                         Displaying the date/time in messages.
                                                             (line   18)
* RFC; RFC 3454:                         stringprep --- Internet String Preparation.
                                                             (line   17)
* RFC; RFC 3454 <1>:                     stringprep --- Internet String Preparation.
                                                             (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 3492:                         Text Encodings.     (line   36)
* RFC; RFC 3492 <1>:                     encodings idna --- Internationalized Domain Names in Applications.
                                                             (line    7)
* RFC; RFC 3493:                         Example<8>.         (line  227)
* RFC; RFC 3501:                         IMAP4 Objects.      (line  322)
* RFC; RFC 3542:                         Library<28>.        (line  352)
* RFC; RFC 3542 <1>:                     Other functions<2>. (line  299)
* RFC; RFC 3548:                         New Improved and Deprecated Modules<3>.
                                                             (line   16)
* RFC; RFC 3548 <1>:                     base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   11)
* RFC; RFC 3548 <2>:                     base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   14)
* RFC; RFC 3548 <3>:                     base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   20)
* RFC; RFC 3548 <4>:                     base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line  108)
* RFC; RFC 3548 <5>:                     binascii --- Convert between binary and ASCII.
                                                             (line   50)
* RFC; RFC 3659:                         FTP Objects.        (line  168)
* RFC; RFC 3879:                         Address objects.    (line  190)
* RFC; RFC 3927:                         Address objects.    (line  121)
* RFC; RFC 3977:                         nntplib --- NNTP protocol client.
                                                             (line   13)
* RFC; RFC 3977 <1>:                     Attributes.         (line   10)
* RFC; RFC 3977 <2>:                     Methods<3>.         (line   36)
* RFC; RFC 3977 <3>:                     Methods<3>.         (line  138)
* RFC; RFC 3977 <4>:                     Methods<3>.         (line  318)
* RFC; RFC 3986:                         urllib parse.       (line    7)
* RFC; RFC 3986 <1>:                     urllib parse<2>.    (line    6)
* RFC; RFC 3986 <2>:                     urllib.             (line   22)
* RFC; RFC 3986 <3>:                     New and Improved Modules.
                                                             (line  617)
* RFC; RFC 3986 <4>:                     Porting to Python 2 7.
                                                             (line   80)
* RFC; RFC 3986 <5>:                     URL Parsing.        (line  130)
* RFC; RFC 3986 <6>:                     URL Parsing.        (line  346)
* RFC; RFC 3986 <7>:                     URL Quoting.        (line   24)
* RFC; RFC 3986 <8>:                     URL Quoting.        (line  153)
* RFC; RFC 3986 <9>:                     http server --- HTTP servers.
                                                             (line   96)
* RFC; RFC 4086:                         LibreSSL support.   (line   33)
* RFC; RFC 4122:                         New Improved and Removed Modules.
                                                             (line  417)
* RFC; RFC 4122 <1>:                     New Improved and Removed Modules.
                                                             (line  422)
* RFC; RFC 4122 <2>:                     uuid --- UUID objects according to RFC 4122.
                                                             (line    6)
* RFC; RFC 4122 <3>:                     uuid --- UUID objects according to RFC 4122.
                                                             (line   13)
* RFC; RFC 4122 <4>:                     uuid --- UUID objects according to RFC 4122.
                                                             (line   71)
* RFC; RFC 4122 <5>:                     uuid --- UUID objects according to RFC 4122.
                                                             (line  137)
* RFC; RFC 4122 <6>:                     uuid --- UUID objects according to RFC 4122.
                                                             (line  166)
* RFC; RFC 4122 <7>:                     uuid --- UUID objects according to RFC 4122.
                                                             (line  230)
* RFC; RFC 4122 <8>:                     uuid --- UUID objects according to RFC 4122.
                                                             (line  243)
* RFC; RFC 4180:                         csv --- CSV File Reading and Writing.
                                                             (line   13)
* RFC; RFC 4193:                         Address objects.    (line  192)
* RFC; RFC 4217:                         ftplib --- FTP protocol client.
                                                             (line   76)
* RFC; RFC 4291:                         Address objects.    (line  135)
* RFC; RFC 4380:                         Address objects.    (line  212)
* RFC; RFC 4627:                         json --- JSON encoder and decoder.
                                                             (line   11)
* RFC; RFC 4627 <1>:                     Top-level Non-Object Non-Array Values.
                                                             (line    6)
* RFC; RFC 4642:                         nntplib --- NNTP protocol client.
                                                             (line  104)
* RFC; RFC 4918:                         HTTP status codes.  (line   43)
* RFC; RFC 4918 <1>:                     HTTP status codes.  (line  133)
* RFC; RFC 4918 <2>:                     HTTP status codes.  (line  136)
* RFC; RFC 4918 <3>:                     HTTP status codes.  (line  139)
* RFC; RFC 4918 <4>:                     HTTP status codes.  (line  178)
* RFC; RFC 4954:                         SMTP Objects.       (line  135)
* RFC; RFC 4954 <1>:                     SMTP Objects.       (line  158)
* RFC; RFC 5161:                         imaplib.            (line   11)
* RFC; RFC 5161 <1>:                     IMAP4 Objects.      (line   86)
* RFC; RFC 5246:                         Constants<9>.       (line  481)
* RFC; RFC 5246 <1>:                     LibreSSL support.   (line   41)
* RFC; RFC 5280:                         Other Changes.      (line   20)
* RFC; RFC 5280 <1>:                     Changes in the Python API<4>.
                                                             (line   95)
* RFC; RFC 5280 <2>:                     Certificate handling.
                                                             (line   11)
* RFC; RFC 5280 <3>:                     Certificate handling.
                                                             (line   64)
* RFC; RFC 5280 <4>:                     LibreSSL support.   (line   37)
* RFC; RFC 5321:                         smtpd<3>.           (line    6)
* RFC; RFC 5321 <1>:                     email headerregistry Custom Header Objects.
                                                             (line  453)
* RFC; RFC 5321 <2>:                     smtpd --- SMTP Server.
                                                             (line   26)
* RFC; RFC 5321 <3>:                     SMTPServer Objects. (line   50)
* RFC; RFC 5321 <4>:                     SMTPServer Objects. (line   78)
* RFC; RFC 5322:                         email --- An email and MIME handling package.
                                                             (line   15)
* RFC; RFC 5322 <1>:                     email message Representing an email message.
                                                             (line   20)
* RFC; RFC 5322 <2>:                     email message Representing an email message.
                                                             (line   31)
* RFC; RFC 5322 <3>:                     Parser API.         (line   40)
* RFC; RFC 5322 <4>:                     email generator Generating MIME documents.
                                                             (line  102)
* RFC; RFC 5322 <5>:                     email generator Generating MIME documents.
                                                             (line  195)
* RFC; RFC 5322 <6>:                     email policy Policy Objects.
                                                             (line  148)
* RFC; RFC 5322 <7>:                     email policy Policy Objects.
                                                             (line  326)
* RFC; RFC 5322 <8>:                     email policy Policy Objects.
                                                             (line  347)
* RFC; RFC 5322 <9>:                     email policy Policy Objects.
                                                             (line  353)
* RFC; RFC 5322 <10>:                    email policy Policy Objects.
                                                             (line  365)
* RFC; RFC 5322 <11>:                    email policy Policy Objects.
                                                             (line  398)
* RFC; RFC 5322 <12>:                    email errors Exception and Defect classes.
                                                             (line   28)
* RFC; RFC 5322 <13>:                    email headerregistry Custom Header Objects.
                                                             (line   16)
* RFC; RFC 5322 <14>:                    email headerregistry Custom Header Objects.
                                                             (line  117)
* RFC; RFC 5322 <15>:                    email headerregistry Custom Header Objects.
                                                             (line  122)
* RFC; RFC 5322 <16>:                    email headerregistry Custom Header Objects.
                                                             (line  123)
* RFC; RFC 5322 <17>:                    email headerregistry Custom Header Objects.
                                                             (line  138)
* RFC; RFC 5322 <18>:                    email headerregistry Custom Header Objects.
                                                             (line  159)
* RFC; RFC 5322 <19>:                    email headerregistry Custom Header Objects.
                                                             (line  416)
* RFC; RFC 5322 <20>:                    email headerregistry Custom Header Objects.
                                                             (line  450)
* RFC; RFC 5322 <21>:                    email headerregistry Custom Header Objects.
                                                             (line  483)
* RFC; RFC 5322 <22>:                    email message Message Representing an email message using the compat32 API.
                                                             (line   21)
* RFC; RFC 5322 <23>:                    SMTP Objects.       (line  316)
* RFC; RFC 5424:                         SysLogHandler.      (line   53)
* 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#section-6:               Inserting a BOM into messages sent to a SysLogHandler.
                                                             (line    9)
* RFC; RFC 5735:                         Address objects.    (line  107)
* RFC; RFC 5842:                         HTTP status codes.  (line   46)
* RFC; RFC 5842 <1>:                     HTTP status codes.  (line  181)
* RFC; RFC 5891:                         encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   11)
* RFC; RFC 5895:                         encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   11)
* RFC; RFC 5929:                         SSL Sockets.        (line  245)
* RFC; RFC 6066:                         Constants<9>.       (line  381)
* RFC; RFC 6066 <1>:                     SSL Contexts.       (line  294)
* RFC; RFC 6066 <2>:                     LibreSSL support.   (line   45)
* RFC; RFC 6125:                         Certificate handling.
                                                             (line   11)
* RFC; RFC 6125 <1>:                     Certificate handling.
                                                             (line   29)
* RFC; RFC 6152:                         smtpd.              (line   17)
* RFC; RFC 6152 <1>:                     SMTPServer Objects. (line   35)
* RFC; RFC 6531:                         email<2>.           (line   19)
* RFC; RFC 6531 <1>:                     smtpd.              (line   23)
* RFC; RFC 6531 <2>:                     smtplib.            (line   15)
* RFC; RFC 6531 <3>:                     email message Representing an email message.
                                                             (line  102)
* RFC; RFC 6531 <4>:                     email policy Policy Objects.
                                                             (line  369)
* RFC; RFC 6531 <5>:                     smtplib --- SMTP protocol client.
                                                             (line   62)
* RFC; RFC 6531 <6>:                     smtpd --- SMTP Server.
                                                             (line   26)
* RFC; RFC 6531 <7>:                     SMTPServer Objects. (line   26)
* RFC; RFC 6531 <8>:                     SMTPChannel Objects.
                                                             (line   21)
* RFC; RFC 6532:                         email<2>.           (line   18)
* RFC; RFC 6532 <1>:                     email --- An email and MIME handling package.
                                                             (line   15)
* RFC; RFC 6532 <2>:                     email message Representing an email message.
                                                             (line   20)
* RFC; RFC 6532 <3>:                     Parser API.         (line   41)
* RFC; RFC 6532 <4>:                     email policy Policy Objects.
                                                             (line  367)
* RFC; RFC 6585:                         HTTP status codes.  (line  145)
* RFC; RFC 6585 <1>:                     HTTP status codes.  (line  148)
* RFC; RFC 6585 <2>:                     HTTP status codes.  (line  151)
* RFC; RFC 6585 <3>:                     HTTP status codes.  (line  187)
* RFC; RFC 6855:                         imaplib.            (line   12)
* RFC; RFC 6855 <1>:                     imaplib.            (line   14)
* RFC; RFC 6855 <2>:                     IMAP4 Objects.      (line   88)
* RFC; RFC 6855 <3>:                     IMAP4 Objects.      (line   90)
* RFC; RFC 6856:                         poplib.             (line    6)
* RFC; RFC 6856 <1>:                     POP3 Objects.       (line  108)
* RFC; RFC 7159:                         json --- JSON encoder and decoder.
                                                             (line   10)
* RFC; RFC 7159 <1>:                     Standard Compliance and Interoperability.
                                                             (line    6)
* RFC; RFC 7159 <2>:                     Top-level Non-Object Non-Array Values.
                                                             (line    9)
* RFC; RFC 7230:                         urllib request --- Extensible library for opening URLs.
                                                             (line  197)
* RFC; RFC 7230 <1>:                     HTTPConnection Objects.
                                                             (line  150)
* RFC; RFC 7231:                         HTTP status codes.  (line   13)
* RFC; RFC 7231 <1>:                     HTTP status codes.  (line   16)
* RFC; RFC 7231 <2>:                     HTTP status codes.  (line   22)
* RFC; RFC 7231 <3>:                     HTTP status codes.  (line   25)
* RFC; RFC 7231 <4>:                     HTTP status codes.  (line   28)
* RFC; RFC 7231 <5>:                     HTTP status codes.  (line   31)
* RFC; RFC 7231 <6>:                     HTTP status codes.  (line   34)
* RFC; RFC 7231 <7>:                     HTTP status codes.  (line   37)
* RFC; RFC 7231 <8>:                     HTTP status codes.  (line   52)
* RFC; RFC 7231 <9>:                     HTTP status codes.  (line   55)
* RFC; RFC 7231 <10>:                    HTTP status codes.  (line   58)
* RFC; RFC 7231 <11>:                    HTTP status codes.  (line   61)
* RFC; RFC 7231 <12>:                    HTTP status codes.  (line   67)
* RFC; RFC 7231 <13>:                    HTTP status codes.  (line   70)
* RFC; RFC 7231 <14>:                    HTTP status codes.  (line   76)
* RFC; RFC 7231 <15>:                    HTTP status codes.  (line   82)
* RFC; RFC 7231 <16>:                    HTTP status codes.  (line   85)
* RFC; RFC 7231 <17>:                    HTTP status codes.  (line   88)
* RFC; RFC 7231 <18>:                    HTTP status codes.  (line   91)
* RFC; RFC 7231 <19>:                    HTTP status codes.  (line   94)
* RFC; RFC 7231 <20>:                    HTTP status codes.  (line  100)
* RFC; RFC 7231 <21>:                    HTTP status codes.  (line  103)
* RFC; RFC 7231 <22>:                    HTTP status codes.  (line  106)
* RFC; RFC 7231 <23>:                    HTTP status codes.  (line  109)
* RFC; RFC 7231 <24>:                    HTTP status codes.  (line  115)
* RFC; RFC 7231 <25>:                    HTTP status codes.  (line  118)
* RFC; RFC 7231 <26>:                    HTTP status codes.  (line  121)
* RFC; RFC 7231 <27>:                    HTTP status codes.  (line  127)
* RFC; RFC 7231 <28>:                    HTTP status codes.  (line  142)
* RFC; RFC 7231 <29>:                    HTTP status codes.  (line  157)
* RFC; RFC 7231 <30>:                    HTTP status codes.  (line  160)
* RFC; RFC 7231 <31>:                    HTTP status codes.  (line  163)
* RFC; RFC 7231 <32>:                    HTTP status codes.  (line  166)
* RFC; RFC 7231 <33>:                    HTTP status codes.  (line  169)
* RFC; RFC 7231 <34>:                    HTTP status codes.  (line  172)
* RFC; RFC 7232:                         HTTP status codes.  (line   64)
* RFC; RFC 7232 <1>:                     HTTP status codes.  (line  112)
* RFC; RFC 7233:                         HTTP status codes.  (line   40)
* RFC; RFC 7233 <1>:                     HTTP status codes.  (line  124)
* RFC; RFC 7235:                         HTTP status codes.  (line   79)
* RFC; RFC 7235 <1>:                     HTTP status codes.  (line   97)
* RFC; RFC 7238:                         HTTP status codes.  (line   73)
* RFC; RFC 7301:                         Application-Layer Protocol Negotiation Support.
                                                             (line   10)
* RFC; RFC 7301 <1>:                     Constants<9>.       (line  358)
* RFC; RFC 7301 <2>:                     SSL Contexts.       (line  259)
* RFC; RFC 7525:                         LibreSSL support.   (line   53)
* RFC; RFC 7540:                         HTTP status codes.  (line  130)
* RFC; RFC 7693:                         BLAKE2.             (line    6)
* RFC; RFC 7725:                         HTTP status codes.  (line  154)
* RFC; RFC 7914:                         Key derivation.     (line   48)
* RFC; RFC 821:                          smtplib --- SMTP protocol client.
                                                             (line   12)
* RFC; RFC 821 <1>:                      smtplib --- SMTP protocol client.
                                                             (line  176)
* RFC; RFC 822:                          New and Improved Modules<3>.
                                                             (line   97)
* RFC; RFC 822 <1>:                      Functions<2>.       (line  610)
* RFC; RFC 822 <2>:                      Functions<2>.       (line  613)
* RFC; RFC 822 <3>:                      email Examples.     (line   36)
* RFC; RFC 822 <4>:                      email header Internationalized headers.
                                                             (line   21)
* RFC; RFC 822 <5>:                      HTTPConnection Objects.
                                                             (line  137)
* RFC; RFC 822 <6>:                      SMTP Objects.       (line   94)
* RFC; RFC 822 <7>:                      SMTP Objects.       (line  231)
* RFC; RFC 822 <8>:                      SMTP Objects.       (line  232)
* RFC; RFC 822 <9>:                      SMTP Example.       (line   10)
* RFC; RFC 822 <10>:                     The GNUTranslations class.
                                                             (line   13)
* RFC; RFC 822 <11>:                     distutils util --- Miscellaneous other utility functions.
                                                             (line  173)
* RFC; RFC 8305:                         Opening network connections.
                                                             (line   77)
* RFC; RFC 8305 <1>:                     Opening network connections.
                                                             (line   86)
* RFC; RFC 854:                          telnetlib --- Telnet client.
                                                             (line   11)
* RFC; RFC 854 <1>:                      telnetlib --- Telnet client.
                                                             (line   58)
* RFC; RFC 959:                          ftplib --- FTP protocol client.
                                                             (line   16)
* RFC; RFC 959 <1>:                      FTP Objects.        (line  148)
* RFC; RFC 977:                          nntplib --- NNTP protocol client.
                                                             (line   13)
* RFC_4122 (於 uuid 模組中):             uuid --- UUID objects according to RFC 4122.
                                                             (line  228)
* rfile (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  113)
* rfind() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  159)
* rfind() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  159)
* rfind() (mmap.mmap 的方法):            mmap --- Memory-mapped file support.
                                                             (line  251)
* rfind() (str 的方法):                  String Methods<2>.  (line  344)
* rgb_to_hls() (於 colorsys 模組中):     colorsys --- Conversions between color systems.
                                                             (line   36)
* rgb_to_hsv() (於 colorsys 模組中):     colorsys --- Conversions between color systems.
                                                             (line   44)
* rgb_to_yiq() (於 colorsys 模組中):     colorsys --- Conversions between color systems.
                                                             (line   28)
* rglob() (pathlib.Path 的方法):         Methods<2>.         (line  352)
* richcmpfunc (C 型態):                  Slot Type typedefs. (line   91)
* right (filecmp.dircmp 的屬性):         The dircmp class.   (line   45)
* right() (於 turtle 模組中):            Turtle motion.      (line   40)
* RIGHTSHIFT (於 token 模組中):          token --- Constants used with Python parse trees.
                                                             (line  162)
* RIGHTSHIFTEQUAL (於 token 模組中):     token --- Constants used with Python parse trees.
                                                             (line  206)
* right_list (filecmp.dircmp 的屬性):    The dircmp class.   (line   54)
* right_only (filecmp.dircmp 的屬性):    The dircmp class.   (line   67)
* rindex() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line  173)
* rindex() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line  173)
* rindex() (str 的方法):                 String Methods<2>.  (line  351)
* rjust() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  282)
* rjust() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  282)
* rjust() (str 的方法):                  String Methods<2>.  (line  356)
* rlcompleter (模組):                    rlcompleter --- Completion function for GNU readline.
                                                             (line    6)
* rlecode_hqx() (於 binascii 模組中):    binascii --- Convert between binary and ASCII.
                                                             (line   94)
* rledecode_hqx() (於 binascii 模組中):  binascii --- Convert between binary and ASCII.
                                                             (line   83)
* RLIMIT_AS (於 resource 模組中):        Resource Limits.    (line  147)
* RLIMIT_CORE (於 resource 模組中):      Resource Limits.    (line   92)
* RLIMIT_CPU (於 resource 模組中):       Resource Limits.    (line   99)
* RLIMIT_DATA (於 resource 模組中):      Resource Limits.    (line  111)
* RLIMIT_FSIZE (於 resource 模組中):     Resource Limits.    (line  107)
* RLIMIT_MEMLOCK (於 resource 模組中):   Resource Limits.    (line  139)
* RLIMIT_MSGQUEUE (於 resource 模組中):  Resource Limits.    (line  152)
* RLIMIT_NICE (於 resource 模組中):      Resource Limits.    (line  160)
* RLIMIT_NOFILE (於 resource 模組中):    Resource Limits.    (line  130)
* RLIMIT_NPROC (於 resource 模組中):     Resource Limits.    (line  126)
* RLIMIT_NPTS (於 resource 模組中):      Resource Limits.    (line  215)
* RLIMIT_OFILE (於 resource 模組中):     Resource Limits.    (line  135)
* RLIMIT_RSS (於 resource 模組中):       Resource Limits.    (line  121)
* RLIMIT_RTPRIO (於 resource 模組中):    Resource Limits.    (line  169)
* RLIMIT_RTTIME (於 resource 模組中):    Resource Limits.    (line  177)
* RLIMIT_SBSIZE (於 resource 模組中):    Resource Limits.    (line  194)
* RLIMIT_SIGPENDING (於 resource 模組中): Resource Limits.   (line  186)
* RLIMIT_STACK (於 resource 模組中):     Resource Limits.    (line  115)
* RLIMIT_SWAP (於 resource 模組中):      Resource Limits.    (line  204)
* RLIMIT_VMEM (於 resource 模組中):      Resource Limits.    (line  143)
* RLIM_INFINITY (於 resource 模組中):    Resource Limits.    (line   20)
* RLock (multiprocessing 中的類別):      Synchronization primitives.
                                                             (line  101)
* RLock (threading 中的類別):            RLock Objects.      (line   23)
* RLock() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  185)
* rmd() (ftplib.FTP 的方法):             FTP Objects.        (line  225)
* rmdir() (pathlib.Path 的方法):         Methods<2>.         (line  364)
* rmdir() (於 os 模組中):                Files and Directories.
                                                             (line  726)
* rmdir() (於 test.support 模組中):      test support --- Utilities for the Python test suite.
                                                             (line  177)
* RMFF:                                  chunk --- Read IFF chunked data.
                                                             (line    8)
* rms() (於 audioop 模組中):             audioop --- Manipulate raw audio data.
                                                             (line  193)
* rmtree() (於 shutil 模組中):           Directory and files operations.
                                                             (line  255)
* rmtree() (於 test.support 模組中):     test support --- Utilities for the Python test suite.
                                                             (line  183)
* RobotFileParser (urllib.robotparser 中的類別): urllib robotparser --- Parser for robots txt.
                                                             (line   16)
* robots.txt:                            urllib robotparser --- Parser for robots txt.
                                                             (line    8)
* rollback() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line   40)
* rotate() (collections.deque 的方法):   deque objects.      (line  109)
* rotate() (decimal.Context 的方法):     Context objects.    (line  481)
* rotate() (decimal.Decimal 的方法):     Decimal objects.    (line  514)
* rotate() (logging.handlers.BaseRotatingHandler 的方法): BaseRotatingHandler.
                                                             (line   57)
* RotatingFileHandler (logging.handlers 中的類別): RotatingFileHandler.
                                                             (line    9)
* rotation_filename() (logging.handlers.BaseRotatingHandler 的方法): BaseRotatingHandler.
                                                             (line   41)
* rotator (logging.handlers.BaseRotatingHandler 的屬性): BaseRotatingHandler.
                                                             (line   32)
* ROT_FOUR (opcode):                     Python Bytecode Instructions.
                                                             (line   72)
* ROT_THREE (opcode):                    Python Bytecode Instructions.
                                                             (line   67)
* ROT_TWO (opcode):                      Python Bytecode Instructions.
                                                             (line   63)
* round() (內建函式):                    內建函式.           (line 1434)
* Rounded (decimal 中的類別):            Signals.            (line   77)
* 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)
* Row (sqlite3 中的類別):                Row Objects.        (line    6)
* rowcount (sqlite3.Cursor 的屬性):      Cursor Objects.     (line  178)
* row_factory (sqlite3.Connection 的屬性): Connection Objects.
                                                             (line  300)
* RPAR (於 token 模組中):                token --- Constants used with Python parse trees.
                                                             (line   58)
* rpartition() (bytearray 的方法):       Bytes and Bytearray Operations.
                                                             (line  185)
* rpartition() (bytes 的方法):           Bytes and Bytearray Operations.
                                                             (line  185)
* rpartition() (str 的方法):             String Methods<2>.  (line  363)
* rpc_paths (xmlrpc.server.SimpleXMLRPCRequestHandler 的屬性): SimpleXMLRPCServer Objects.
                                                             (line   64)
* rpop() (poplib.POP3 的方法):           POP3 Objects.       (line   46)
* rset() (poplib.POP3 的方法):           POP3 Objects.       (line   74)
* rshift() (於 operator 模組中):         operator --- Standard operators as functions.
                                                             (line  148)
* rsplit() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line  294)
* rsplit() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line  294)
* rsplit() (str 的方法):                 String Methods<2>.  (line  371)
* RSQB (於 token 模組中):                token --- Constants used with Python parse trees.
                                                             (line   66)
* rstrip() (bytearray 的方法):           Bytes and Bytearray Operations.
                                                             (line  305)
* rstrip() (bytes 的方法):               Bytes and Bytearray Operations.
                                                             (line  305)
* rstrip() (str 的方法):                 String Methods<2>.  (line  380)
* rt() (於 turtle 模組中):               Turtle motion.      (line   40)
* RTLD_DEEPBIND (於 os 模組中):          Miscellaneous System Information.
                                                             (line  141)
* RTLD_GLOBAL (於 os 模組中):            Miscellaneous System Information.
                                                             (line  141)
* RTLD_LAZY (於 os 模組中):              Miscellaneous System Information.
                                                             (line  141)
* RTLD_LOCAL (於 os 模組中):             Miscellaneous System Information.
                                                             (line  141)
* RTLD_NODELETE (於 os 模組中):          Miscellaneous System Information.
                                                             (line  141)
* RTLD_NOLOAD (於 os 模組中):            Miscellaneous System Information.
                                                             (line  141)
* RTLD_NOW (於 os 模組中):               Miscellaneous System Information.
                                                             (line  141)
* ruler (cmd.Cmd 的屬性):                Cmd Objects.        (line  164)
* run (pdb command):                     Debugger Commands.  (line  322)
* Run script:                            Format menu Editor window only.
                                                             (line   53)
* run() (bdb.Bdb 的方法):                bdb --- Debugger framework.
                                                             (line  363)
* run() (contextvars.Context 的方法):    Manual Context Management.
                                                             (line   31)
* run() (distutils.cmd.Command 的方法):  Creating a new Distutils command.
                                                             (line   40)
* run() (doctest.DocTestRunner 的方法):  DocTestRunner objects.
                                                             (line   95)
* run() (multiprocessing.Process 的方法): Process and exceptions.
                                                             (line   33)
* run() (pdb.Pdb 的方法):                pdb --- The Python Debugger.
                                                             (line  178)
* run() (profile.Profile 的方法):        profile and cProfile Module Reference.
                                                             (line  100)
* run() (sched.scheduler 的方法):        Scheduler Objects.  (line   51)
* run() (test.support.BasicTestRunner 的方法): test support --- Utilities for the Python test suite.
                                                             (line 1103)
* run() (threading.Thread 的方法):       Thread Objects.     (line  100)
* run() (trace.Trace 的方法):            Programmatic Interface.
                                                             (line   22)
* run() (unittest.IsolatedAsyncioTestCase 的方法): Test cases.
                                                             (line  841)
* run() (unittest.TestCase 的方法):      Test cases.         (line   83)
* run() (unittest.TestSuite 的方法):     Grouping tests.     (line   41)
* run() (unittest.TextTestRunner 的方法): Loading and running tests.
                                                             (line  480)
* run() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line   98)
* run() (於 asyncio 模組中):             Running an asyncio Program.
                                                             (line    6)
* run() (於 pdb 模組中):                 pdb --- The Python Debugger.
                                                             (line   91)
* run() (於 profile 模組中):             profile and cProfile Module Reference.
                                                             (line    9)
* run() (於 subprocess 模組中):          Using the subprocess Module.
                                                             (line   15)
* runcall() (bdb.Bdb 的方法):            bdb --- Debugger framework.
                                                             (line  380)
* runcall() (pdb.Pdb 的方法):            pdb --- The Python Debugger.
                                                             (line  178)
* runcall() (profile.Profile 的方法):    profile and cProfile Module Reference.
                                                             (line  109)
* runcall() (於 pdb 模組中):             pdb --- The Python Debugger.
                                                             (line  110)
* runcode() (code.InteractiveInterpreter 的方法): Interactive Interpreter Objects.
                                                             (line   33)
* runctx() (bdb.Bdb 的方法):             bdb --- Debugger framework.
                                                             (line  375)
* runctx() (profile.Profile 的方法):     profile and cProfile Module Reference.
                                                             (line  104)
* runctx() (trace.Trace 的方法):         Programmatic Interface.
                                                             (line   28)
* runctx() (於 profile 模組中):          profile and cProfile Module Reference.
                                                             (line   23)
* runeval() (bdb.Bdb 的方法):            bdb --- Debugger framework.
                                                             (line  369)
* runeval() (pdb.Pdb 的方法):            pdb --- The Python Debugger.
                                                             (line  178)
* runeval() (於 pdb 模組中):             pdb --- The Python Debugger.
                                                             (line  103)
* runfunc() (trace.Trace 的方法):        Programmatic Interface.
                                                             (line   35)
* running() (concurrent.futures.Future 的方法): Future Objects.
                                                             (line   28)
* runpy (模組):                          runpy --- Locating and executing Python modules.
                                                             (line    6)
* runsource() (code.InteractiveInterpreter 的方法): Interactive Interpreter Objects.
                                                             (line    6)
* RuntimeError:                          Concrete exceptions.
                                                             (line  203)
* RuntimeWarning:                        Warnings.           (line   36)
* runtime_checkable() (於 typing 模組中): Classes functions and decorators.
                                                             (line  750)
* runtime_library_dir_option() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  229)
* run_coroutine_threadsafe() (於 asyncio 模組中): Scheduling From Other Threads.
                                                             (line    6)
* run_docstring_examples() (於 doctest 模組中): Basic API.   (line  128)
* run_doctest() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  270)
* run_forever() (asyncio.loop 的方法):   Running and stopping the loop.
                                                             (line   16)
* run_in_executor() (asyncio.loop 的方法): Executing code in thread or process pools.
                                                             (line    6)
* run_in_subinterp() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  950)
* run_module() (於 runpy 模組中):        runpy --- Locating and executing Python modules.
                                                             (line   27)
* run_path() (於 runpy 模組中):          runpy --- Locating and executing Python modules.
                                                             (line   94)
* run_python_until_end() (於 test.support.script_helper 模組中): test support script_helper --- Utilities for the Python execution tests.
                                                             (line   29)
* run_script() (modulefinder.ModuleFinder 的方法): modulefinder --- Find modules used by a script.
                                                             (line   44)
* run_setup() (於 distutils.core 模組中): distutils core --- Core Distutils functionality.
                                                             (line  121)
* run_unittest() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  254)
* run_until_complete() (asyncio.loop 的方法): Running and stopping the loop.
                                                             (line    6)
* run_with_locale() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  573)
* run_with_tz() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  581)
* 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_DSYNC (於 os 模組中):              File Descriptor Operations.
                                                             (line  529)
* RWF_HIPRI (於 os 模組中):              File Descriptor Operations.
                                                             (line  476)
* RWF_NOWAIT (於 os 模組中):             File Descriptor Operations.
                                                             (line  461)
* RWF_SYNC (於 os 模組中):               File Descriptor Operations.
                                                             (line  539)
* R_OK (於 os 模組中):                   Files and Directories.
                                                             (line  106)
* S (於 re 模組中):                      Module Contents.    (line  113)
* safe (uuid.SafeUUID 的屬性):           uuid --- UUID objects according to RFC 4122.
                                                             (line   31)
* SafeChildWatcher (asyncio 中的類別):   Process Watchers.   (line  118)
* saferepr() (於 pprint 模組中):         pprint --- Data pretty printer.
                                                             (line  145)
* SafeUUID (uuid 中的類別):              uuid --- UUID objects according to RFC 4122.
                                                             (line   27)
* safe_substitute() (string.Template 的方法): Template strings.
                                                             (line   50)
* samefile() (pathlib.Path 的方法):      Methods<2>.         (line  368)
* samefile() (於 os.path 模組中):        os path --- Common pathname manipulations.
                                                             (line  324)
* SameFileError:                         Directory and files operations.
                                                             (line   52)
* sameopenfile() (於 os.path 模組中):    os path --- Common pathname manipulations.
                                                             (line  340)
* samestat() (於 os.path 模組中):        os path --- Common pathname manipulations.
                                                             (line  351)
* same_files (filecmp.dircmp 的屬性):    The dircmp class.   (line   85)
* same_quantum() (decimal.Context 的方法): Context objects.  (line  485)
* same_quantum() (decimal.Decimal 的方法): Decimal objects.  (line  526)
* sample() (於 random 模組中):           Functions for sequences.
                                                             (line   67)
* samples() (statistics.NormalDist 的方法): NormalDist objects.
                                                             (line   58)
* save() (http.cookiejar.FileCookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line  105)
* SAVEDCWD (於 test.support 模組中):     test support --- Utilities for the Python test suite.
                                                             (line   87)
* SaveKey() (於 winreg 模組中):          Functions<11>.      (line  399)
* SaveSignals (test.support 中的類別):   test support --- Utilities for the Python test suite.
                                                             (line 1080)
* savetty() (於 curses 模組中):          Functions<3>.       (line  427)
* SAX2DOM (xml.dom.pulldom 中的類別):    xml dom pulldom --- Support for building partial DOM trees.
                                                             (line   81)
* SAXException:                          xml sax --- Support for SAX2 parsers.
                                                             (line   86)
* SAXNotRecognizedException:             xml sax --- Support for SAX2 parsers.
                                                             (line  111)
* SAXNotSupportedException:              xml sax --- Support for SAX2 parsers.
                                                             (line  118)
* SAXParseException:                     xml sax --- Support for SAX2 parsers.
                                                             (line  103)
* scaleb() (decimal.Context 的方法):     Context objects.    (line  489)
* scaleb() (decimal.Decimal 的方法):     Decimal objects.    (line  536)
* scandir() (於 os 模組中):              Files and Directories.
                                                             (line  743)
* scanf():                               Simulating scanf.   (line    6)
* sched (模組):                          sched --- Event scheduler.
                                                             (line    6)
* scheduler (sched 中的類別):            sched --- Event scheduler.
                                                             (line   13)
* SCHED_BATCH (於 os 模組中):            Interface to the scheduler.
                                                             (line   19)
* SCHED_FIFO (於 os 模組中):             Interface to the scheduler.
                                                             (line   32)
* 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_get_priority_max() (於 os 模組中): Interface to the scheduler.
                                                             (line   63)
* sched_get_priority_min() (於 os 模組中): Interface to the scheduler.
                                                             (line   58)
* 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)
* schema (於 msilib 模組中):             Precomputed tables. (line   10)
* scope:                                 Naming and binding. (line    6)
* scope <1>:                             Resolution of names.
                                                             (line    6)
* Screen (turtle 中的類別):              Public classes.     (line   30)
* screensize() (於 turtle 模組中):       Window control.     (line   61)
* script_from_examples() (於 doctest 模組中): Debugging.     (line   72)
* scroll() (curses.window 的方法):       Window Objects.     (line  497)
* ScrolledCanvas (turtle 中的類別):      Public classes.     (line   34)
* scrollok() (curses.window 的方法):     Window Objects.     (line  501)
* scrypt() (於 hashlib 模組中):          Key derivation.     (line   44)
* seal() (於 unittest.mock 模組中):      Sealing mocks.      (line    6)
* search() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line  216)
* search() (re.Pattern 的方法):          Regular Expression Objects.
                                                             (line    9)
* search() (於 re 模組中):               Module Contents.    (line  143)
* second (datetime.datetime 的屬性):     datetime Objects.   (line  285)
* second (datetime.time 的屬性):         time Objects.       (line   58)
* seconds since the epoch:               time --- Time access and conversions.
                                                             (line   25)
* secrets (模組):                        secrets --- Generate secure random numbers for managing secrets.
                                                             (line    6)
* SECTCRE (configparser.ConfigParser 的屬性): Customizing Parser Behaviour.
                                                             (line  300)
* sections() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line   81)
* secure (http.cookiejar.Cookie 的屬性): Cookie Objects<2>.  (line   45)
* secure hash algorithm, SHA1, SHA224, SHA256, SHA384, SHA512: hashlib --- Secure hashes and message digests.
                                                             (line    8)
* Secure Sockets Layer:                  ssl --- TLS/SSL wrapper for socket objects.
                                                             (line    8)
* see() (tkinter.ttk.Treeview 的方法):   ttk Treeview.       (line  251)
* seed() (於 random 模組中):             Bookkeeping functions.
                                                             (line    6)
* seek() (chunk.Chunk 的方法):           chunk --- Read IFF chunked data.
                                                             (line   92)
* seek() (io.IOBase 的方法):             I/O Base Classes.   (line  104)
* seek() (io.TextIOBase 的方法):         Text I/O<2>.        (line   66)
* seek() (mmap.mmap 的方法):             mmap --- Memory-mapped file support.
                                                             (line  261)
* seekable() (io.IOBase 的方法):         I/O Base Classes.   (line  129)
* SEEK_CUR (於 os 模組中):               File Descriptor Operations.
                                                             (line  248)
* SEEK_END (於 os 模組中):               File Descriptor Operations.
                                                             (line  248)
* SEEK_SET (於 os 模組中):               File Descriptor Operations.
                                                             (line  248)
* seen_greeting (smtpd.SMTPChannel 的屬性): SMTPChannel Objects.
                                                             (line   69)
* Select (tkinter.tix 中的類別):         Basic Widgets.      (line   59)
* select (模組):                         select --- Waiting for I/O completion.
                                                             (line    6)
* select() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line  233)
* select() (selectors.BaseSelector 的方法): Classes<3>.      (line  108)
* select() (tkinter.ttk.Notebook 的方法): ttk Notebook.      (line   53)
* select() (於 select 模組中):           select --- Waiting for I/O completion.
                                                             (line  108)
* selected_alpn_protocol() (ssl.SSLSocket 的方法): SSL Sockets.
                                                             (line  251)
* selected_npn_protocol() (ssl.SSLSocket 的方法): SSL Sockets.
                                                             (line  261)
* selection() (tkinter.ttk.Treeview 的方法): ttk Treeview.   (line  259)
* selection_add() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  274)
* selection_remove() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  281)
* selection_set() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  267)
* selection_toggle() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  288)
* selector (urllib.request.Request 的屬性): Request Objects. (line   34)
* SelectorEventLoop (asyncio 中的類別):  Event Loop Implementations.
                                                             (line   12)
* SelectorKey (selectors 中的類別):      Classes<3>.         (line   29)
* selectors (模組):                      selectors --- High-level I/O multiplexing.
                                                             (line    6)
* SelectSelector (selectors 中的類別):   Classes<3>.         (line  167)
* Semaphore (asyncio 中的類別):          Semaphore.          (line    6)
* Semaphore (multiprocessing 中的類別):  Synchronization primitives.
                                                             (line  166)
* Semaphore (threading 中的類別):        Semaphore Objects.  (line   19)
* Semaphore() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  190)
* semaphores, binary:                    _thread --- Low-level threading API.
                                                             (line    6)
* SEMI (於 token 模組中):                token --- Constants used with Python parse trees.
                                                             (line   78)
* send() (asyncore.dispatcher 的方法):   asyncore --- Asynchronous socket handler.
                                                             (line  199)
* send() (coroutine 的方法):             Coroutine Objects.  (line   23)
* send() (generator 的方法):             Generator-iterator methods.
                                                             (line   27)
* send() (http.client.HTTPConnection 的方法): HTTPConnection Objects.
                                                             (line  169)
* send() (imaplib.IMAP4 的方法):         IMAP4 Objects.      (line  240)
* send() (logging.handlers.DatagramHandler 的方法): DatagramHandler.
                                                             (line   34)
* send() (logging.handlers.SocketHandler 的方法): SocketHandler.
                                                             (line   63)
* send() (multiprocessing.connection.Connection 的方法): Connection Objects<2>.
                                                             (line   15)
* send() (socket.socket 的方法):         Socket Objects.     (line  381)
* sendall() (socket.socket 的方法):      Socket Objects.     (line  397)
* sendcmd() (ftplib.FTP 的方法):         FTP Objects.        (line   66)
* sendfile() (asyncio.loop 的方法):      Transferring files. (line    6)
* sendfile() (socket.socket 的方法):     Socket Objects.     (line  488)
* sendfile() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line  274)
* sendfile() (於 os 模組中):             File Descriptor Operations.
                                                             (line  569)
* SendfileNotAvailableError:             Exceptions<8>.      (line   35)
* sendmail() (smtplib.SMTP 的方法):      SMTP Objects.       (line  228)
* sendmsg() (socket.socket 的方法):      Socket Objects.     (line  435)
* sendmsg_afalg() (socket.socket 的方法): Socket Objects.    (line  477)
* sendto() (asyncio.DatagramTransport 的方法): Datagram Transports.
                                                             (line    6)
* sendto() (socket.socket 的方法):       Socket Objects.     (line  416)
* send_bytes() (multiprocessing.connection.Connection 的方法): Connection Objects<2>.
                                                             (line   54)
* send_error() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  208)
* send_flowing_data() (formatter.writer 的方法): The Writer Interface.
                                                             (line   76)
* send_header() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  243)
* send_hor_rule() (formatter.writer 的方法): The Writer Interface.
                                                             (line   68)
* send_label_data() (formatter.writer 的方法): The Writer Interface.
                                                             (line   92)
* send_line_break() (formatter.writer 的方法): The Writer Interface.
                                                             (line   54)
* send_literal_data() (formatter.writer 的方法): The Writer Interface.
                                                             (line   83)
* send_message() (smtplib.SMTP 的方法):  SMTP Objects.       (line  306)
* send_paragraph() (formatter.writer 的方法): The Writer Interface.
                                                             (line   58)
* send_response() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  228)
* send_response_only() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  255)
* send_signal() (asyncio.asyncio.subprocess.Process 的方法): Interacting with Subprocesses.
                                                             (line   81)
* send_signal() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   44)
* send_signal() (subprocess.Popen 的方法): Popen Objects.    (line   74)
* sentinel (multiprocessing.Process 的屬性): Process and exceptions.
                                                             (line  133)
* sentinel (於 unittest.mock 模組中):    sentinel.           (line    6)
* sep (於 os 模組中):                    Miscellaneous System Information.
                                                             (line   93)
* sequence:                              Glossary.           (line 1150)
* Sequence (collections.abc 中的類別):   Collections Abstract Base Classes.
                                                             (line  159)
* Sequence (typing 中的類別):            Classes functions and decorators.
                                                             (line  229)
* sequence (於 msilib 模組中):           Precomputed tables. (line   16)
* sequence2st() (於 parser 模組中):      Creating ST Objects.
                                                             (line   26)
* sequence; item:                        Subscriptions.      (line    6)
* sequence; iteration:                   Iterator Types.     (line    6)
* SequenceMatcher (difflib 中的類別):    SequenceMatcher Objects.
                                                             (line    8)
* serializing; objects:                  pickle --- Python object serialization.
                                                             (line    8)
* Server (asyncio 中的類別):             Server Objects.     (line   12)
* server (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line   71)
* ServerProxy (xmlrpc.client 中的類別):  xmlrpc client --- XML-RPC client access.
                                                             (line   24)
* server_activate() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line  164)
* server_address (socketserver.BaseServer 的屬性): Server Objects<2>.
                                                             (line   76)
* server_bind() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line  170)
* server_close() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line   61)
* server_hostname (ssl.SSLSocket 的屬性): SSL Sockets.       (line  333)
* server_side (ssl.SSLSocket 的屬性):    SSL Sockets.        (line  326)
* server_software (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  175)
* server_version (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  129)
* server_version (http.server.SimpleHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  343)
* serve_forever() (asyncio.Server 的方法): Server Objects.   (line   63)
* serve_forever() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line   32)
* service_actions() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line   45)
* session (ssl.SSLSocket 的屬性):        SSL Sockets.        (line  346)
* session_reused (ssl.SSLSocket 的屬性): SSL Sockets.        (line  356)
* session_stats() (ssl.SSLContext 的方法): SSL Contexts.     (line  481)
* Set (collections.abc 中的類別):        Collections Abstract Base Classes.
                                                             (line  177)
* Set (typing 中的類別):                 Classes functions and decorators.
                                                             (line  272)
* set (內建類別):                        Set Types --- set frozenset.
                                                             (line   33)
* Set Breakpoint:                        Help menu Shell and Editor.
                                                             (line   30)
* set comprehension:                     Glossary.           (line 1169)
* set() (asyncio.Event 的方法):          Event.              (line   52)
* set() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  249)
* set() (configparser.RawConfigParser 的方法): RawConfigParser Objects.
                                                             (line   37)
* set() (contextvars.ContextVar 的方法): Context Variables.  (line   46)
* set() (http.cookies.Morsel 的方法):    Morsel Objects.     (line   64)
* set() (ossaudiodev.oss_mixer_device 的方法): Mixer Device Objects.
                                                             (line   71)
* set() (test.support.EnvironmentVarGuard 的方法): test support --- Utilities for the Python test suite.
                                                             (line 1035)
* set() (threading.Event 的方法):        Event Objects.      (line   27)
* set() (tkinter.ttk.Combobox 的方法):   ttk Combobox.       (line   19)
* set() (tkinter.ttk.Spinbox 的方法):    ttk Spinbox.        (line   12)
* set() (tkinter.ttk.Treeview 的方法):   ttk Treeview.       (line  295)
* set() (xml.etree.ElementTree.Element 的方法): Element Objects.
                                                             (line   81)
* set; comprehensions:                   Set displays.       (line    6)
* set; display:                          Set displays.       (line    6)
* setacl() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line  247)
* setannotation() (imaplib.IMAP4 的方法): IMAP4 Objects.     (line  252)
* setattr() (內建函式):                  內建函式.           (line 1470)
* setattrfunc (C 型態):                  Slot Type typedefs. (line   57)
* setAttribute() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   67)
* setAttributeNode() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   71)
* setAttributeNodeNS() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   79)
* setAttributeNS() (xml.dom.Element 的方法): Element Objects<2>.
                                                             (line   87)
* setattrofunc (C 型態):                 Slot Type typedefs. (line   69)
* SetBase() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line   22)
* setblocking() (socket.socket 的方法):  Socket Objects.     (line  512)
* setByteStream() (xml.sax.xmlreader.InputSource 的方法): InputSource Objects.
                                                             (line   36)
* setcbreak() (於 tty 模組中):           tty --- Terminal control functions.
                                                             (line   24)
* setCharacterStream() (xml.sax.xmlreader.InputSource 的方法): InputSource Objects.
                                                             (line   55)
* setcheckinterval() (於 sys 模組中):    sys --- System-specific parameters and functions.
                                                             (line 1197)
* setcomptype() (aifc.aifc 的方法):      aifc --- Read and write AIFF and AIFC files.
                                                             (line  157)
* setcomptype() (sunau.AU_write 的方法): AU_write Objects.   (line   28)
* setcomptype() (wave.Wave_write 的方法): Wave_write Objects.
                                                             (line   51)
* setContentHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   25)
* setcontext() (於 decimal 模組中):      Context objects.    (line   18)
* setDaemon() (threading.Thread 的方法): Thread Objects.     (line  197)
* setdefault() (dict 的方法):            Mapping Types --- dict.
                                                             (line  205)
* setdefault() (http.cookies.Morsel 的方法): Morsel Objects. (line  108)
* setdefaulttimeout() (於 socket 模組中): Other functions<2>.
                                                             (line  336)
* setdlopenflags() (於 sys 模組中):      sys --- System-specific parameters and functions.
                                                             (line 1212)
* setDocumentLocator() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line   10)
* setDTDHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   34)
* setegid() (於 os 模組中):              Process Parameters. (line  338)
* setEncoding() (xml.sax.xmlreader.InputSource 的方法): InputSource Objects.
                                                             (line   22)
* setEntityResolver() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   43)
* setErrorHandler() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   54)
* seteuid() (於 os 模組中):              Process Parameters. (line  344)
* setFeature() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   76)
* setfirstweekday() (於 calendar 模組中): calendar --- General calendar-related functions.
                                                             (line  287)
* setfmt() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line  122)
* setFormatter() (logging.Handler 的方法): Handler Objects.  (line   48)
* setframerate() (aifc.aifc 的方法):     aifc --- Read and write AIFF and AIFC files.
                                                             (line  147)
* setframerate() (sunau.AU_write 的方法): AU_write Objects.  (line   19)
* setframerate() (wave.Wave_write 的方法): Wave_write Objects.
                                                             (line   38)
* setgid() (於 os 模組中):               Process Parameters. (line  350)
* setgroups() (於 os 模組中):            Process Parameters. (line  356)
* seth() (於 turtle 模組中):             Turtle motion.      (line  132)
* setheading() (於 turtle 模組中):       Turtle motion.      (line  132)
* sethostname() (於 socket 模組中):      Other functions<2>. (line  343)
* SetInteger() (msilib.Record 的方法):   Record Objects.     (line   32)
* setitem() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  201)
* setitimer() (於 signal 模組中):        Module contents<2>. (line  348)
* setLevel() (logging.Handler 的方法):   Handler Objects.    (line   35)
* setLevel() (logging.Logger 的方法):    Logger Objects.     (line   50)
* setLocale() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   60)
* setlocale() (於 locale 模組中):        locale --- Internationalization services.
                                                             (line   27)
* setLoggerClass() (於 logging 模組中):  Module-Level Functions.
                                                             (line  343)
* setlogmask() (於 syslog 模組中):       syslog --- Unix syslog library routines.
                                                             (line   73)
* setLogRecordFactory() (於 logging 模組中): Module-Level Functions.
                                                             (line  355)
* setmark() (aifc.aifc 的方法):          aifc --- Read and write AIFF and AIFC files.
                                                             (line  175)
* setMaxConns() (urllib.request.CacheFTPHandler 的方法): CacheFTPHandler Objects.
                                                             (line   13)
* setmode() (於 msvcrt 模組中):          File Operations.    (line   38)
* setName() (threading.Thread 的方法):   Thread Objects.     (line  142)
* setnchannels() (aifc.aifc 的方法):     aifc --- Read and write AIFF and AIFC files.
                                                             (line  139)
* setnchannels() (sunau.AU_write 的方法): AU_write Objects.  (line    9)
* setnchannels() (wave.Wave_write 的方法): Wave_write Objects.
                                                             (line   30)
* setnframes() (aifc.aifc 的方法):       aifc --- Read and write AIFF and AIFC files.
                                                             (line  151)
* setnframes() (sunau.AU_write 的方法):  AU_write Objects.   (line   23)
* setnframes() (wave.Wave_write 的方法): Wave_write Objects. (line   45)
* SetParamEntityParsing() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line   54)
* setparameters() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line  186)
* setparams() (aifc.aifc 的方法):        aifc --- Read and write AIFF and AIFC files.
                                                             (line  167)
* setparams() (sunau.AU_write 的方法):   AU_write Objects.   (line   33)
* setparams() (wave.Wave_write 的方法):  Wave_write Objects. (line   56)
* setpassword() (zipfile.ZipFile 的方法): ZipFile Objects.   (line  211)
* setpgid() (於 os 模組中):              Process Parameters. (line  379)
* setpgrp() (於 os 模組中):              Process Parameters. (line  371)
* setpos() (aifc.aifc 的方法):           aifc --- Read and write AIFF and AIFC files.
                                                             (line  107)
* setpos() (sunau.AU_read 的方法):       AU_read Objects.    (line   60)
* setpos() (wave.Wave_read 的方法):      Wave_read Objects.  (line   69)
* setpos() (於 turtle 模組中):           Turtle motion.      (line   74)
* setposition() (於 turtle 模組中):      Turtle motion.      (line   74)
* setpriority() (於 os 模組中):          Process Parameters. (line  387)
* setprofile() (於 sys 模組中):          sys --- System-specific parameters and functions.
                                                             (line 1225)
* setprofile() (於 threading 模組中):    threading --- Thread-based parallelism.
                                                             (line  129)
* SetProperty() (msilib.SummaryInformation 的方法): Summary Information Objects.
                                                             (line   22)
* setProperty() (xml.sax.xmlreader.XMLReader 的方法): XMLReader Objects.
                                                             (line   90)
* setPublicId() (xml.sax.xmlreader.InputSource 的方法): InputSource Objects.
                                                             (line    6)
* setquota() (imaplib.IMAP4 的方法):     IMAP4 Objects.      (line  257)
* setraw() (於 tty 模組中):              tty --- Terminal control functions.
                                                             (line   18)
* setrecursionlimit() (於 sys 模組中):   sys --- System-specific parameters and functions.
                                                             (line 1277)
* setregid() (於 os 模組中):             Process Parameters. (line  404)
* setresgid() (於 os 模組中):            Process Parameters. (line  410)
* setresuid() (於 os 模組中):            Process Parameters. (line  418)
* setreuid() (於 os 模組中):             Process Parameters. (line  426)
* setrlimit() (於 resource 模組中):      Resource Limits.    (line   31)
* setsampwidth() (aifc.aifc 的方法):     aifc --- Read and write AIFF and AIFC files.
                                                             (line  143)
* setsampwidth() (sunau.AU_write 的方法): AU_write Objects.  (line   13)
* setsampwidth() (wave.Wave_write 的方法): Wave_write Objects.
                                                             (line   34)
* setscrreg() (curses.window 的方法):    Window Objects.     (line  511)
* setsid() (於 os 模組中):               Process Parameters. (line  439)
* setsockopt() (socket.socket 的方法):   Socket Objects.     (line  545)
* setstate() (codecs.IncrementalDecoder 的方法): IncrementalDecoder Objects.
                                                             (line   60)
* setstate() (codecs.IncrementalEncoder 的方法): IncrementalEncoder Objects.
                                                             (line   51)
* setstate() (於 random 模組中):         Bookkeeping functions.
                                                             (line   34)
* setStream() (logging.StreamHandler 的方法): StreamHandler. (line   32)
* SetStream() (msilib.Record 的方法):    Record Objects.     (line   26)
* SetString() (msilib.Record 的方法):    Record Objects.     (line   21)
* setswitchinterval() (in module sys):   Thread State and the Global Interpreter Lock.
                                                             (line   15)
* setswitchinterval() (於 sys 模組中):   sys --- System-specific parameters and functions.
                                                             (line 1294)
* setswitchinterval() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  281)
* setSystemId() (xml.sax.xmlreader.InputSource 的方法): InputSource Objects.
                                                             (line   14)
* setsyx() (於 curses 模組中):           Functions<3>.       (line  432)
* setTarget() (logging.handlers.MemoryHandler 的方法): MemoryHandler.
                                                             (line   67)
* settiltangle() (於 turtle 模組中):     Appearance.         (line  118)
* settimeout() (socket.socket 的方法):   Socket Objects.     (line  529)
* setTimeout() (urllib.request.CacheFTPHandler 的方法): CacheFTPHandler Objects.
                                                             (line    9)
* settrace() (於 sys 模組中):            sys --- System-specific parameters and functions.
                                                             (line 1307)
* settrace() (於 threading 模組中):      threading --- Thread-based parallelism.
                                                             (line  122)
* setuid() (於 os 模組中):               Process Parameters. (line  446)
* setundobuffer() (於 turtle 模組中):    Special Turtle methods.
                                                             (line   61)
* setup() (socketserver.BaseRequestHandler 的方法): Request Handler Objects.
                                                             (line   14)
* setUp() (unittest.TestCase 的方法):    Test cases.         (line   33)
* setup() (於 distutils.core 模組中):    distutils core --- Core Distutils functionality.
                                                             (line   12)
* setup() (於 turtle 模組中):            Methods specific to Screen not inherited from TurtleScreen.
                                                             (line   20)
* setUpClass() (unittest.TestCase 的方法): Test cases.       (line   55)
* setupterm() (於 curses 模組中):        Functions<3>.       (line  437)
* SETUP_ANNOTATIONS (opcode):            Python Bytecode Instructions.
                                                             (line  357)
* SETUP_ASYNC_WITH (opcode):             Python Bytecode Instructions.
                                                             (line  303)
* setup_environ() (wsgiref.handlers.BaseHandler 的方法): wsgiref handlers -- server/gateway base classes.
                                                             (line  195)
* SETUP_FINALLY (opcode):                Python Bytecode Instructions.
                                                             (line  696)
* setup_python() (venv.EnvBuilder 的方法): API<2>.           (line   91)
* setup_scripts() (venv.EnvBuilder 的方法): API<2>.          (line   99)
* setup_testing_defaults() (於 wsgiref.util 模組中): wsgiref util -- WSGI environment utilities.
                                                             (line   68)
* SETUP_WITH (opcode):                   Python Bytecode Instructions.
                                                             (line  438)
* SetValue() (於 winreg 模組中):         Functions<11>.      (line  423)
* SetValueEx() (於 winreg 模組中):       Functions<11>.      (line  454)
* setworldcoordinates() (於 turtle 模組中): Window control.  (line   87)
* setx() (於 turtle 模組中):             Turtle motion.      (line  104)
* setxattr() (於 os 模組中):             Linux extended attributes.
                                                             (line   57)
* sety() (於 turtle 模組中):             Turtle motion.      (line  118)
* SET_ADD (opcode):                      Python Bytecode Instructions.
                                                             (line  317)
* set_all():                             Reference Count Details.
                                                             (line   98)
* set_allowed_domains() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy Objects.
                                                             (line   70)
* set_alpn_protocols() (ssl.SSLContext 的方法): SSL Contexts.
                                                             (line  253)
* set_app() (wsgiref.simple_server.WSGIServer 的方法): wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line   61)
* set_asyncgen_hooks() (於 sys 模組中):  sys --- System-specific parameters and functions.
                                                             (line 1403)
* set_authorizer() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line  193)
* set_auto_history() (於 readline 模組中): History list.     (line   43)
* set_blocked_domains() (http.cookiejar.DefaultCookiePolicy 的方法): DefaultCookiePolicy Objects.
                                                             (line   56)
* set_blocking() (於 os 模組中):         File Descriptor Operations.
                                                             (line  605)
* set_boundary() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  410)
* set_boundary() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  588)
* set_break() (bdb.Bdb 的方法):          bdb --- Debugger framework.
                                                             (line  281)
* set_charset() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  235)
* set_children() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line   25)
* set_child_watcher() (asyncio.AbstractEventLoopPolicy 的方法): Policy Objects.
                                                             (line   42)
* set_child_watcher() (於 asyncio 模組中): Process Watchers. (line   29)
* set_ciphers() (ssl.SSLContext 的方法): SSL Contexts.       (line  239)
* set_completer() (於 readline 模組中):  Completion.         (line   14)
* set_completer_delims() (於 readline 模組中): Completion.   (line   48)
* set_completion_display_matches_hook() (於 readline 模組中): Completion.
                                                             (line   57)
* set_content() (email.contentmanager.ContentManager 的方法): email contentmanager Managing MIME Content.
                                                             (line   40)
* set_content() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  589)
* set_content() (於 email.contentmanager 模組中): Content Manager Instances.
                                                             (line   35)
* set_continue() (bdb.Bdb 的方法):       bdb --- Debugger framework.
                                                             (line  266)
* set_cookie() (http.cookiejar.CookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line   72)
* set_cookie_if_ok() (http.cookiejar.CookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line   68)
* set_coroutine_origin_tracking_depth() (於 sys 模組中): sys --- System-specific parameters and functions.
                                                             (line 1428)
* set_current() (msilib.Feature 的方法): Features<3>.        (line   14)
* set_data() (importlib.abc.SourceLoader 的方法): importlib abc -- Abstract base classes related to import.
                                                             (line  554)
* set_data() (importlib.machinery.SourceFileLoader 的方法): importlib machinery -- Importers and path hooks.
                                                             (line  234)
* set_date() (mailbox.MaildirMessage 的方法): MaildirMessage.
                                                             (line   97)
* set_debug() (asyncio.loop 的方法):     Enabling debug mode.
                                                             (line   14)
* set_debug() (於 gc 模組中):            gc --- Garbage Collector interface.
                                                             (line   48)
* set_debuglevel() (ftplib.FTP 的方法):  FTP Objects.        (line   13)
* set_debuglevel() (http.client.HTTPConnection 的方法): HTTPConnection Objects.
                                                             (line   70)
* set_debuglevel() (nntplib.NNTP 的方法): Methods<3>.        (line  307)
* set_debuglevel() (poplib.POP3 的方法): POP3 Objects.       (line   11)
* set_debuglevel() (smtplib.SMTP 的方法): SMTP Objects.      (line    8)
* set_debuglevel() (telnetlib.Telnet 的方法): Telnet Objects.
                                                             (line   84)
* set_defaults() (argparse.ArgumentParser 的方法): Parser defaults.
                                                             (line    6)
* set_defaults() (optparse.OptionParser 的方法): Other methods.
                                                             (line   27)
* set_default_executor() (asyncio.loop 的方法): Executing code in thread or process pools.
                                                             (line   65)
* set_default_type() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  340)
* set_default_type() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  450)
* set_default_verify_paths() (ssl.SSLContext 的方法): SSL Contexts.
                                                             (line  230)
* set_ecdh_curve() (ssl.SSLContext 的方法): SSL Contexts.    (line  369)
* set_errno() (於 ctypes 模組中):        Utility functions.  (line  171)
* set_event_loop() (asyncio.AbstractEventLoopPolicy 的方法): Policy Objects.
                                                             (line   23)
* set_event_loop() (於 asyncio 模組中):  Event Loop.         (line   57)
* set_event_loop_policy() (於 asyncio 模組中): Getting and Setting the Policy.
                                                             (line   13)
* set_exception() (asyncio.Future 的方法): Future Object.    (line   51)
* set_exception() (concurrent.futures.Future 的方法): Future Objects.
                                                             (line  123)
* set_exception_handler() (asyncio.loop 的方法): Error Handling API.
                                                             (line    8)
* set_executable() (於 multiprocessing 模組中): Miscellaneous<3>.
                                                             (line  107)
* set_executables() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  234)
* set_flags() (mailbox.MaildirMessage 的方法): MaildirMessage.
                                                             (line   72)
* set_flags() (mailbox.mboxMessage 的方法): mboxMessage.     (line   72)
* set_flags() (mailbox.MMDFMessage 的方法): MMDFMessage.     (line   71)
* set_from() (mailbox.mboxMessage 的方法): mboxMessage.      (line   53)
* set_from() (mailbox.MMDFMessage 的方法): MMDFMessage.      (line   52)
* set_handle_inheritable() (於 os 模組中): Inheritance of File Descriptors.
                                                             (line   38)
* set_history_length() (於 readline 模組中): History file.   (line   30)
* set_include_dirs() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  102)
* set_info() (mailbox.MaildirMessage 的方法): MaildirMessage.
                                                             (line  108)
* set_inheritable() (socket.socket 的方法): Socket Objects.  (line  505)
* set_inheritable() (於 os 模組中):      Inheritance of File Descriptors.
                                                             (line   28)
* set_labels() (mailbox.BabylMessage 的方法): BabylMessage.  (line   51)
* set_last_error() (於 ctypes 模組中):   Utility functions.  (line  180)
* set_libraries() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  127)
* set_library_dirs() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  143)
* set_link_objects() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  186)
* set_literal (2to3 fixer):              Fixers.             (line  288)
* set_loader() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  168)
* set_match_tests() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  250)
* set_memlimit() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  370)
* set_name() (asyncio.Task 的方法):      Task Object.        (line  219)
* set_next() (bdb.Bdb 的方法):           bdb --- Debugger framework.
                                                             (line  248)
* set_nonstandard_attr() (http.cookiejar.Cookie 的方法): Cookie Objects<2>.
                                                             (line  103)
* set_npn_protocols() (ssl.SSLContext 的方法): SSL Contexts. (line  273)
* set_ok() (http.cookiejar.CookiePolicy 的方法): CookiePolicy Objects.
                                                             (line    9)
* set_option_negotiation_callback() (telnetlib.Telnet 的方法): Telnet Objects.
                                                             (line  143)
* set_output_charset() (gettext.NullTranslations 的方法): The NullTranslations class.
                                                             (line   94)
* set_package() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  183)
* set_param() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  349)
* set_param() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  518)
* set_pasv() (ftplib.FTP 的方法):        FTP Objects.        (line  107)
* set_payload() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  225)
* set_policy() (http.cookiejar.CookieJar 的方法): CookieJar and FileCookieJar Objects.
                                                             (line   56)
* set_position() (xdrlib.Unpacker 的方法): Unpacker Objects. (line   16)
* set_pre_input_hook() (於 readline 模組中): Startup hooks.  (line   14)
* set_progress_handler() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line  217)
* set_protocol() (asyncio.BaseTransport 的方法): Base Transport.
                                                             (line   80)
* set_proxy() (urllib.request.Request 的方法): Request Objects.
                                                             (line  112)
* set_python_build() (於 distutils.sysconfig 模組中): distutils sysconfig --- System configuration information.
                                                             (line   98)
* set_quit() (bdb.Bdb 的方法):           bdb --- Debugger framework.
                                                             (line  271)
* set_recsrc() (ossaudiodev.oss_mixer_device 的方法): Mixer Device Objects.
                                                             (line   88)
* set_result() (asyncio.Future 的方法):  Future Object.      (line   44)
* set_result() (concurrent.futures.Future 的方法): Future Objects.
                                                             (line  111)
* set_return() (bdb.Bdb 的方法):         bdb --- Debugger framework.
                                                             (line  252)
* set_running_or_notify_cancel() (concurrent.futures.Future 的方法): Future Objects.
                                                             (line   89)
* set_runtime_library_dirs() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  154)
* set_seq1() (difflib.SequenceMatcher 的方法): SequenceMatcher Objects.
                                                             (line   54)
* set_seq2() (difflib.SequenceMatcher 的方法): SequenceMatcher Objects.
                                                             (line   59)
* set_seqs() (difflib.SequenceMatcher 的方法): SequenceMatcher Objects.
                                                             (line   44)
* set_sequences() (mailbox.MH 的方法):   MH.                 (line   58)
* set_sequences() (mailbox.MHMessage 的方法): MHMessage.     (line   37)
* set_servername_callback (ssl.SSLContext 的屬性): SSL Contexts.
                                                             (line  340)
* set_server_documentation() (xmlrpc.server.DocCGIXMLRPCRequestHandler 的方法): DocCGIXMLRPCRequestHandler.
                                                             (line   24)
* set_server_documentation() (xmlrpc.server.DocXMLRPCServer 的方法): DocXMLRPCServer Objects.
                                                             (line   24)
* set_server_name() (xmlrpc.server.DocCGIXMLRPCRequestHandler 的方法): DocCGIXMLRPCRequestHandler.
                                                             (line   18)
* set_server_name() (xmlrpc.server.DocXMLRPCServer 的方法): DocXMLRPCServer Objects.
                                                             (line   18)
* set_server_title() (xmlrpc.server.DocCGIXMLRPCRequestHandler 的方法): DocCGIXMLRPCRequestHandler.
                                                             (line   13)
* set_server_title() (xmlrpc.server.DocXMLRPCServer 的方法): DocXMLRPCServer Objects.
                                                             (line   13)
* set_spacing() (formatter.formatter 的方法): The Formatter Interface.
                                                             (line  139)
* set_startup_hook() (於 readline 模組中): Startup hooks.    (line    6)
* set_start_method() (於 multiprocessing 模組中): Miscellaneous<3>.
                                                             (line  120)
* set_step() (bdb.Bdb 的方法):           bdb --- Debugger framework.
                                                             (line  244)
* set_subdir() (mailbox.MaildirMessage 的方法): MaildirMessage.
                                                             (line   58)
* set_task_factory() (asyncio.loop 的方法): Creating Futures and Tasks.
                                                             (line   31)
* set_terminator() (asynchat.async_chat 的方法): asynchat --- Asynchronous socket command/response handler.
                                                             (line  117)
* set_threshold() (於 gc 模組中):        gc --- Garbage Collector interface.
                                                             (line   89)
* set_trace() (bdb.Bdb 的方法):          bdb --- Debugger framework.
                                                             (line  261)
* set_trace() (pdb.Pdb 的方法):          pdb --- The Python Debugger.
                                                             (line  178)
* set_trace() (於 bdb 模組中):           bdb --- Debugger framework.
                                                             (line  404)
* set_trace() (於 pdb 模組中):           pdb --- The Python Debugger.
                                                             (line  117)
* set_trace_callback() (sqlite3.Connection 的方法): Connection Objects.
                                                             (line  231)
* set_tunnel() (http.client.HTTPConnection 的方法): HTTPConnection Objects.
                                                             (line   80)
* set_type() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  552)
* set_unittest_reportflags() (於 doctest 模組中): Unittest API.
                                                             (line  165)
* set_unixfrom() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  144)
* set_unixfrom() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  157)
* set_until() (bdb.Bdb 的方法):          bdb --- Debugger framework.
                                                             (line  256)
* set_url() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- Parser for robots txt.
                                                             (line   21)
* set_usage() (optparse.OptionParser 的方法): Other methods. (line    8)
* set_userptr() (curses.panel.Panel 的方法): Panel Objects.  (line   43)
* set_visible() (mailbox.BabylMessage 的方法): BabylMessage. (line   68)
* set_wakeup_fd() (於 signal 模組中):    Module contents<2>. (line  377)
* set_write_buffer_limits() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   33)
* SF_APPEND (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line  374)
* SF_ARCHIVED (於 stat 模組中):          stat --- Interpreting stat results.
                                                             (line  366)
* SF_IMMUTABLE (於 stat 模組中):         stat --- Interpreting stat results.
                                                             (line  370)
* SF_MNOWAIT (於 os 模組中):             File Descriptor Operations.
                                                             (line  618)
* SF_NODISKIO (於 os 模組中):            File Descriptor Operations.
                                                             (line  618)
* SF_NOUNLINK (於 stat 模組中):          stat --- Interpreting stat results.
                                                             (line  378)
* SF_SNAPSHOT (於 stat 模組中):          stat --- Interpreting stat results.
                                                             (line  382)
* SF_SYNC (於 os 模組中):                File Descriptor Operations.
                                                             (line  618)
* shape (memoryview 的屬性):             Memory Views.       (line  444)
* Shape (turtle 中的類別):               Public classes.     (line   43)
* shape() (於 turtle 模組中):            Appearance.         (line    6)
* shapesize() (於 turtle 模組中):        Appearance.         (line   52)
* shapetransform() (於 turtle 模組中):   Appearance.         (line  157)
* share() (socket.socket 的方法):        Socket Objects.     (line  574)
* ShareableList (multiprocessing.shared_memory 中的類別): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line  243)
* ShareableList() (multiprocessing.managers.SharedMemoryManager 的方法): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line  203)
* Shared Memory:                         multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line   10)
* SharedMemory (multiprocessing.shared_memory 中的類別): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line   33)
* SharedMemory() (multiprocessing.managers.SharedMemoryManager 的方法): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line  198)
* SharedMemoryManager (multiprocessing.managers 中的類別): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line  171)
* shared_ciphers() (ssl.SSLSocket 的方法): SSL Sockets.      (line  214)
* shared_object_filename() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  473)
* shearfactor() (於 turtle 模組中):      Appearance.         (line   84)
* Shelf (shelve 中的類別):               Restrictions.       (line   23)
* shelve (模組):                         shelve --- Python object persistence.
                                                             (line    6)
* shield() (於 asyncio 模組中):          Shielding From Cancellation.
                                                             (line    6)
* shift() (decimal.Context 的方法):      Context objects.    (line  494)
* shift() (decimal.Decimal 的方法):      Decimal objects.    (line  542)
* shifting; operation:                   Shifting operations.
                                                             (line    6)
* shifting; operations:                  Bitwise Operations on Integer Types.
                                                             (line    6)
* shift_path_info() (於 wsgiref.util 模組中): wsgiref util -- WSGI environment utilities.
                                                             (line   38)
* shlex (shlex 中的類別):                shlex --- Simple lexical analysis.
                                                             (line   82)
* shlex (模組):                          shlex --- Simple lexical analysis.
                                                             (line    6)
* shm (multiprocessing.shared_memory.ShareableList 的屬性): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line  278)
* shortDescription() (unittest.TestCase 的方法): Test cases. (line  729)
* shorten() (於 textwrap 模組中):        textwrap --- Text wrapping and filling.
                                                             (line   40)
* shouldFlush() (logging.handlers.BufferingHandler 的方法): MemoryHandler.
                                                             (line   35)
* shouldFlush() (logging.handlers.MemoryHandler 的方法): MemoryHandler.
                                                             (line   71)
* shouldStop (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  267)
* show() (curses.panel.Panel 的方法):    Panel Objects.      (line   49)
* showsyntaxerror() (code.InteractiveInterpreter 的方法): Interactive Interpreter Objects.
                                                             (line   44)
* showtraceback() (code.InteractiveInterpreter 的方法): Interactive Interpreter Objects.
                                                             (line   53)
* showturtle() (於 turtle 模組中):       Visibility.         (line   15)
* showwarning() (於 warnings 模組中):    Available Functions.
                                                             (line   55)
* show_code() (於 dis 模組中):           Analysis functions. (line   26)
* show_compilers() (於 distutils.ccompiler 模組中): distutils ccompiler --- CCompiler base class.
                                                             (line   61)
* shuffle() (於 random 模組中):          Functions for sequences.
                                                             (line   49)
* shutdown() (concurrent.futures.Executor 的方法): Executor Objects.
                                                             (line   57)
* shutdown() (imaplib.IMAP4 的方法):     IMAP4 Objects.      (line  262)
* shutdown() (multiprocessing.managers.BaseManager 的方法): Managers.
                                                             (line   67)
* shutdown() (socket.socket 的方法):     Socket Objects.     (line  567)
* shutdown() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line   54)
* shutdown() (於 logging 模組中):        Module-Level Functions.
                                                             (line  332)
* shutdown_asyncgens() (asyncio.loop 的方法): Running and stopping the loop.
                                                             (line   56)
* shutil (模組):                         shutil --- High-level file operations.
                                                             (line    6)
* side_effect (unittest.mock.Mock 的屬性): The Mock Class.   (line  347)
* SIGABRT (於 signal 模組中):            Module contents<2>. (line   28)
* SIGALRM (於 signal 模組中):            Module contents<2>. (line   32)
* SIGBREAK (於 signal 模組中):           Module contents<2>. (line   38)
* SIGBUS (於 signal 模組中):             Module contents<2>. (line   44)
* SIGCHLD (於 signal 模組中):            Module contents<2>. (line   50)
* SIGCLD (於 signal 模組中):             Module contents<2>. (line   56)
* SIGCONT (於 signal 模組中):            Module contents<2>. (line   60)
* SIGFPE (於 signal 模組中):             Module contents<2>. (line   66)
* SIGHUP (於 signal 模組中):             Module contents<2>. (line   76)
* SIGILL (於 signal 模組中):             Module contents<2>. (line   83)
* SIGINT:                                Signal Handling<2>. (line    8)
* SIGINT <1>:                            Signal Handling<2>. (line   20)
* SIGINT (於 signal 模組中):             Module contents<2>. (line   87)
* siginterrupt() (於 signal 模組中):     Module contents<2>. (line  419)
* SIGKILL (於 signal 模組中):            Module contents<2>. (line   93)
* signal (模組):                         signal --- Set handlers for asynchronous events.
                                                             (line    6)
* signal() (於 signal 模組中):           Module contents<2>. (line  433)
* Signature (inspect 中的類別):          Introspecting callables with the Signature object.
                                                             (line   50)
* signature (inspect.BoundArguments 的屬性): Introspecting callables with the Signature object.
                                                             (line  307)
* signature() (於 inspect 模組中):       Introspecting callables with the Signature object.
                                                             (line   12)
* sigpending() (於 signal 模組中):       Module contents<2>. (line  460)
* SIGPIPE (於 signal 模組中):            Module contents<2>. (line  101)
* SIGSEGV (於 signal 模組中):            Module contents<2>. (line  109)
* SIGTERM (於 signal 模組中):            Module contents<2>. (line  113)
* sigtimedwait() (於 signal 模組中):     Module contents<2>. (line  518)
* SIGUSR1 (於 signal 模組中):            Module contents<2>. (line  117)
* SIGUSR2 (於 signal 模組中):            Module contents<2>. (line  123)
* sigwait() (於 signal 模組中):          Module contents<2>. (line  474)
* sigwaitinfo() (於 signal 模組中):      Module contents<2>. (line  490)
* SIGWINCH (於 signal 模組中):           Module contents<2>. (line  129)
* SIG_BLOCK (於 signal 模組中):          Module contents<2>. (line  186)
* SIG_DFL (於 signal 模組中):            Module contents<2>. (line   15)
* SIG_IGN (於 signal 模組中):            Module contents<2>. (line   23)
* SIG_SETMASK (於 signal 模組中):        Module contents<2>. (line  201)
* SIG_UNBLOCK (於 signal 模組中):        Module contents<2>. (line  193)
* Simple Mail Transfer Protocol:         smtplib --- SMTP protocol client.
                                                             (line    8)
* simple; statement:                     Simple statements.  (line    6)
* SimpleCookie (http.cookies 中的類別):  http cookies --- HTTP state management.
                                                             (line   48)
* simplefilter() (於 warnings 模組中):   Available Functions.
                                                             (line   89)
* SimpleHandler (wsgiref.handlers 中的類別): wsgiref handlers -- server/gateway base classes.
                                                             (line   70)
* SimpleHTTPRequestHandler (http.server 中的類別): http server --- HTTP servers.
                                                             (line  330)
* SimpleNamespace (types 中的類別):      Additional Utility Classes and Functions.
                                                             (line    6)
* SimpleQueue (multiprocessing 中的類別): Pipes and Queues.  (line  203)
* SimpleQueue (queue 中的類別):          queue --- A synchronized queue class.
                                                             (line   75)
* SimpleXMLRPCRequestHandler (xmlrpc.server 中的類別): xmlrpc server --- Basic XML-RPC servers.
                                                             (line   58)
* SimpleXMLRPCServer (xmlrpc.server 中的類別): xmlrpc server --- Basic XML-RPC servers.
                                                             (line   19)
* sin() (於 cmath 模組中):               Trigonometric functions<2>.
                                                             (line   29)
* sin() (於 math 模組中):                Trigonometric functions.
                                                             (line   57)
* single dispatch:                       Glossary.           (line 1177)
* SingleAddressHeader (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  217)
* singledispatch() (於 functools 模組中): functools --- Higher-order functions and operations on callable objects.
                                                             (line  318)
* singledispatchmethod (functools 中的類別): functools --- Higher-order functions and operations on callable objects.
                                                             (line  435)
* singleton; tuple:                      The standard type hierarchy.
                                                             (line  172)
* sinh() (於 cmath 模組中):              Hyperbolic functions<2>.
                                                             (line   30)
* sinh() (於 math 模組中):               Hyperbolic functions.
                                                             (line   25)
* SIO_KEEPALIVE_VALS (於 socket 模組中): Constants<8>.       (line  167)
* SIO_LOOPBACK_FAST_PATH (於 socket 模組中): Constants<8>.   (line  167)
* SIO_RCVALL (於 socket 模組中):         Constants<8>.       (line  167)
* site (模組):                           site --- Site-specific configuration hook.
                                                             (line    6)
* site command line option; –user-base:  Command Line Interface<4>.
                                                             (line   18)
* site command line option; –user-site:  Command Line Interface<4>.
                                                             (line   22)
* site-packages; directory:              site --- Site-specific configuration hook.
                                                             (line   24)
* site_maps() (urllib.robotparser.RobotFileParser 的方法): urllib robotparser --- Parser for robots txt.
                                                             (line   71)
* sixtofour (ipaddress.IPv6Address 的屬性): Address objects. (line  202)
* size (multiprocessing.shared_memory.SharedMemory 的屬性): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line   96)
* size (struct.Struct 的屬性):           Classes<2>.         (line   62)
* size (tarfile.TarInfo 的屬性):         TarInfo Objects.    (line   47)
* size (tracemalloc.Statistic 的屬性):   Statistic.          (line   19)
* size (tracemalloc.StatisticDiff 的屬性): StatisticDiff.    (line   26)
* size (tracemalloc.Trace 的屬性):       Trace.              (line   23)
* size() (ftplib.FTP 的方法):            FTP Objects.        (line  229)
* size() (mmap.mmap 的方法):             mmap --- Memory-mapped file support.
                                                             (line  269)
* Sized (collections.abc 中的類別):      Collections Abstract Base Classes.
                                                             (line  112)
* Sized (typing 中的類別):               Classes functions and decorators.
                                                             (line  199)
* sizeof() (於 ctypes 模組中):           Utility functions.  (line  189)
* size_diff (tracemalloc.StatisticDiff 的屬性): StatisticDiff.
                                                             (line   32)
* SIZE_MAX:                              整數物件.           (line  202)
* SKIP (於 doctest 模組中):              Option Flags.       (line  103)
* skip() (chunk.Chunk 的方法):           chunk --- Read IFF chunked data.
                                                             (line  113)
* skip() (於 unittest 模組中):           Skipping tests and expected failures.
                                                             (line   85)
* skipIf() (於 unittest 模組中):         Skipping tests and expected failures.
                                                             (line   90)
* skipinitialspace (csv.Dialect 的屬性): Dialects and Formatting Parameters.
                                                             (line   65)
* skipped (unittest.TestResult 的屬性):  Loading and running tests.
                                                             (line  249)
* skippedEntity() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line  176)
* SkipTest:                              Skipping tests and expected failures.
                                                             (line  104)
* skipTest() (unittest.TestCase 的方法): Test cases.         (line   97)
* skipUnless() (於 unittest 模組中):     Skipping tests and expected failures.
                                                             (line   94)
* skip_unless_bind_unix_socket() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  562)
* skip_unless_symlink() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  553)
* skip_unless_xattr() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  558)
* SLASH (於 token 模組中):               token --- Constants used with Python parse trees.
                                                             (line   94)
* SLASHEQUAL (於 token 模組中):          token --- Constants used with Python parse trees.
                                                             (line  182)
* slave() (nntplib.NNTP 的方法):         Methods<3>.         (line  303)
* sleep() (於 asyncio 模組中):           Sleeping.           (line    6)
* sleep() (於 time 模組中):              Functions<2>.       (line  215)
* slice:                                 Slicings.           (line    6)
* slice <1>:                             Glossary.           (line 1182)
* slice (內建類別):                      內建函式.           (line 1479)
* slice; assignment:                     Mutable Sequence Types.
                                                             (line   16)
* slice; operation:                      Common Sequence Operations.
                                                             (line   21)
* slicing:                               The standard type hierarchy.
                                                             (line  133)
* slicing <1>:                           The standard type hierarchy.
                                                             (line  192)
* slicing <2>:                           Slicings.           (line    6)
* slicing; assignment:                   Assignment statements.
                                                             (line  126)
* SMALLEST (於 test.support 模組中):     test support --- Utilities for the Python test suite.
                                                             (line  155)
* SMTP (smtplib 中的類別):               smtplib --- SMTP protocol client.
                                                             (line   16)
* SMTP (於 email.policy 模組中):         email policy Policy Objects.
                                                             (line  493)
* SMTP; protocol:                        smtplib --- SMTP protocol client.
                                                             (line    8)
* SMTPAuthenticationError:               smtplib --- SMTP protocol client.
                                                             (line  168)
* SMTPChannel (smtpd 中的類別):          SMTPChannel Objects.
                                                             (line    6)
* SMTPConnectError:                      smtplib --- SMTP protocol client.
                                                             (line  153)
* smtpd (模組):                          smtpd --- SMTP Server.
                                                             (line    6)
* SMTPDataError:                         smtplib --- SMTP protocol client.
                                                             (line  149)
* SMTPException:                         smtplib --- SMTP protocol client.
                                                             (line  115)
* SMTPHandler (logging.handlers 中的類別): SMTPHandler.      (line   10)
* SMTPHeloError:                         smtplib --- SMTP protocol client.
                                                             (line  158)
* smtplib (模組):                        smtplib --- SMTP protocol client.
                                                             (line    6)
* SMTPNotSupportedError:                 smtplib --- SMTP protocol client.
                                                             (line  162)
* SMTPRecipientsRefused:                 smtplib --- SMTP protocol client.
                                                             (line  142)
* SMTPResponseException:                 smtplib --- SMTP protocol client.
                                                             (line  128)
* SMTPSenderRefused:                     smtplib --- SMTP protocol client.
                                                             (line  136)
* SMTPServer (smtpd 中的類別):           SMTPServer Objects. (line    6)
* SMTPServerDisconnected:                smtplib --- SMTP protocol client.
                                                             (line  122)
* SMTPUTF8 (於 email.policy 模組中):     email policy Policy Objects.
                                                             (line  499)
* smtp_server (smtpd.SMTPChannel 的屬性): SMTPChannel Objects.
                                                             (line   44)
* SMTP_SSL (smtplib 中的類別):           smtplib --- SMTP protocol client.
                                                             (line   65)
* smtp_state (smtpd.SMTPChannel 的屬性): SMTPChannel Objects.
                                                             (line   63)
* Snapshot (tracemalloc 中的類別):       Snapshot.           (line    6)
* sndhdr (模組):                         sndhdr --- Determine type of sound file.
                                                             (line    6)
* SND_ALIAS (於 winsound 模組中):        winsound --- Sound-playing interface for Windows.
                                                             (line   47)
* SND_ASYNC (於 winsound 模組中):        winsound --- Sound-playing interface for Windows.
                                                             (line  109)
* SND_FILENAME (於 winsound 模組中):     winsound --- Sound-playing interface for Windows.
                                                             (line   42)
* SND_LOOP (於 winsound 模組中):         winsound --- Sound-playing interface for Windows.
                                                             (line   88)
* SND_MEMORY (於 winsound 模組中):       winsound --- Sound-playing interface for Windows.
                                                             (line   94)
* SND_NODEFAULT (於 winsound 模組中):    winsound --- Sound-playing interface for Windows.
                                                             (line  113)
* SND_NOSTOP (於 winsound 模組中):       winsound --- Sound-playing interface for Windows.
                                                             (line  118)
* SND_NOWAIT (於 winsound 模組中):       winsound --- Sound-playing interface for Windows.
                                                             (line  122)
* SND_PURGE (於 winsound 模組中):        winsound --- Sound-playing interface for Windows.
                                                             (line  103)
* sniff() (csv.Sniffer 的方法):          Module Contents<3>. (line  209)
* Sniffer (csv 中的類別):                Module Contents<3>. (line  202)
* sni_callback (ssl.SSLContext 的屬性):  SSL Contexts.       (line  289)
* socket (socketserver.BaseServer 的屬性): Server Objects<2>.
                                                             (line   85)
* socket (模組):                         socket --- Low-level networking interface.
                                                             (line    6)
* socket() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line  268)
* socket() (in module socket):           select --- Waiting for I/O completion.
                                                             (line  136)
* socket() (於 socket 模組中):           Creating sockets.   (line    8)
* SocketHandler (logging.handlers 中的類別): SocketHandler.  (line   10)
* socketpair() (於 socket 模組中):       Creating sockets.   (line   59)
* sockets (asyncio.Server 的屬性):       Server Objects.     (line   99)
* socketserver (模組):                   socketserver --- A framework for network servers.
                                                             (line    6)
* SocketType (於 socket 模組中):         Creating sockets.   (line  171)
* socket_type (socketserver.BaseServer 的屬性): Server Objects<2>.
                                                             (line  108)
* sock_accept() (asyncio.loop 的方法):   Working with socket objects directly.
                                                             (line   72)
* SOCK_CLOEXEC (於 socket 模組中):       Constants<8>.       (line   32)
* sock_connect() (asyncio.loop 的方法):  Working with socket objects directly.
                                                             (line   53)
* SOCK_DGRAM (於 socket 模組中):         Constants<8>.       (line   21)
* SOCK_MAX_SIZE (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  100)
* SOCK_NONBLOCK (於 socket 模組中):      Constants<8>.       (line   32)
* SOCK_RAW (於 socket 模組中):           Constants<8>.       (line   21)
* SOCK_RDM (於 socket 模組中):           Constants<8>.       (line   21)
* sock_recv() (asyncio.loop 的方法):     Working with socket objects directly.
                                                             (line   12)
* sock_recv_into() (asyncio.loop 的方法): Working with socket objects directly.
                                                             (line   25)
* sock_sendall() (asyncio.loop 的方法):  Working with socket objects directly.
                                                             (line   36)
* sock_sendfile() (asyncio.loop 的方法): Working with socket objects directly.
                                                             (line   94)
* SOCK_SEQPACKET (於 socket 模組中):     Constants<8>.       (line   21)
* SOCK_STREAM (於 socket 模組中):        Constants<8>.       (line   21)
* SOL_ALG (於 socket 模組中):            Constants<8>.       (line  183)
* SOL_RDS (於 socket 模組中):            Constants<8>.       (line  154)
* SOMAXCONN (於 socket 模組中):          Constants<8>.       (line   48)
* sort() (imaplib.IMAP4 的方法):         IMAP4 Objects.      (line  272)
* sort() (list 的方法):                  List（串列）<2>.    (line   39)
* sortdict() (於 test.support 模組中):   test support --- Utilities for the Python test suite.
                                                             (line  224)
* sorted() (內建函式):                   內建函式.           (line 1495)
* sortTestMethodsUsing (unittest.TestLoader 的屬性): Loading and running tests.
                                                             (line  185)
* sort_stats() (pstats.Stats 的方法):    The Stats Class.    (line   67)
* source (doctest.Example 的屬性):       Example Objects.    (line   17)
* source (pdb command):                  Debugger Commands.  (line  251)
* source (shlex.shlex 的屬性):           shlex Objects.      (line  150)
* source character set:                  Encoding declarations.
                                                             (line    6)
* SourceFileLoader (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  208)
* sourcehook() (shlex.shlex 的方法):     shlex Objects.      (line   26)
* SourcelessFileLoader (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line  248)
* SourceLoader (importlib.abc 中的類別): importlib abc -- Abstract base classes related to import.
                                                             (line  494)
* SOURCE_DATE_EPOCH:                     py_compile<2>.      (line    7)
* SOURCE_DATE_EPOCH <1>:                 Library<28>.        (line  453)
* SOURCE_DATE_EPOCH <2>:                 Build<23>.          (line   15)
* SOURCE_DATE_EPOCH <3>:                 py_compile --- Compile Python source files.
                                                             (line   65)
* SOURCE_DATE_EPOCH <4>:                 py_compile --- Compile Python source files.
                                                             (line   81)
* SOURCE_DATE_EPOCH <5>:                 py_compile --- Compile Python source files.
                                                             (line   85)
* SOURCE_DATE_EPOCH <6>:                 Command-line use.   (line   84)
* source_from_cache() (於 imp 模組中):   imp --- Access the import internals.
                                                             (line  226)
* source_from_cache() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line   58)
* source_hash() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  217)
* 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  411)
* space:                                 Indentation.        (line    6)
* space; in printf-style formatting:     printf-style String Formatting.
                                                             (line   66)
* space; in printf-style formatting <1>: printf-style Bytes Formatting.
                                                             (line   63)
* space; in string formatting:           Format Specification Mini-Language.
                                                             (line   71)
* span() (re.Match 的方法):              Match Objects.      (line  156)
* spawn() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  487)
* spawn() (於 pty 模組中):               pty --- Pseudo-terminal utilities.
                                                             (line   36)
* spawnl() (於 os 模組中):               Process Management. (line  500)
* spawnle() (於 os 模組中):              Process Management. (line  500)
* spawnlp() (於 os 模組中):              Process Management. (line  500)
* spawnlpe() (於 os 模組中):             Process Management. (line  500)
* spawnv() (於 os 模組中):               Process Management. (line  500)
* spawnve() (於 os 模組中):              Process Management. (line  500)
* spawnvp() (於 os 模組中):              Process Management. (line  500)
* spawnvpe() (於 os 模組中):             Process Management. (line  500)
* spawn_python() (於 test.support.script_helper 模組中): test support script_helper --- Utilities for the Python execution tests.
                                                             (line   58)
* special method:                        Glossary.           (line 1190)
* special; attribute:                    The standard type hierarchy.
                                                             (line   13)
* special; method:                       Glossary.           (line 1194)
* specified_attributes (xml.parsers.expat.xmlparser 的屬性): XMLParser Objects<2>.
                                                             (line  117)
* spec_from_file_location() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  205)
* spec_from_loader() (於 importlib.util 模組中): importlib util -- Utility code for importers.
                                                             (line  194)
* speed() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line  137)
* speed() (於 turtle 模組中):            Turtle motion.      (line  302)
* Spinbox (tkinter.ttk 中的類別):        ttk Spinbox.        (line    6)
* split() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  328)
* split() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  328)
* split() (re.Pattern 的方法):           Regular Expression Objects.
                                                             (line   74)
* split() (str 的方法):                  String Methods<2>.  (line  393)
* split() (於 os.path 模組中):           os path --- Common pathname manipulations.
                                                             (line  365)
* split() (於 re 模組中):                Module Contents.    (line  176)
* split() (於 shlex 模組中):             shlex --- Simple lexical analysis.
                                                             (line   17)
* splitdrive() (於 os.path 模組中):      os path --- Common pathname manipulations.
                                                             (line  380)
* splitext() (於 os.path 模組中):        os path --- Common pathname manipulations.
                                                             (line  401)
* splitlines() (bytearray 的方法):       Bytes and Bytearray Operations.
                                                             (line  571)
* splitlines() (bytes 的方法):           Bytes and Bytearray Operations.
                                                             (line  571)
* splitlines() (str 的方法):             String Methods<2>.  (line  433)
* SplitResult (urllib.parse 中的類別):   Structured Parse Results.
                                                             (line   55)
* SplitResultBytes (urllib.parse 中的類別): Structured Parse Results.
                                                             (line   82)
* split_quoted() (於 distutils.util 模組中): distutils util --- Miscellaneous other utility functions.
                                                             (line   98)
* SpooledTemporaryFile() (於 tempfile 模組中): tempfile --- Generate temporary files and directories.
                                                             (line   93)
* sprintf-style formatting:              printf-style String Formatting.
                                                             (line    6)
* sprintf-style formatting <1>:          printf-style Bytes Formatting.
                                                             (line    6)
* spwd (模組):                           spwd --- The shadow password database.
                                                             (line    6)
* sqlite3 (模組):                        sqlite3 --- DB-API 2 0 interface for SQLite databases.
                                                             (line    6)
* sqlite_version (於 sqlite3 模組中):    Module functions and constants.
                                                             (line   16)
* sqlite_version_info (於 sqlite3 模組中): Module functions and constants.
                                                             (line   20)
* sqrt() (decimal.Context 的方法):       Context objects.    (line  498)
* sqrt() (decimal.Decimal 的方法):       Decimal objects.    (line  553)
* sqrt() (於 cmath 模組中):              Power and logarithmic functions<2>.
                                                             (line   23)
* sqrt() (於 math 模組中):               Power and logarithmic functions.
                                                             (line   74)
* ssizeargfunc (C 型態):                 Slot Type typedefs. (line  116)
* ssizeobjargproc (C 型態):              Slot Type typedefs. (line  118)
* SSL:                                   ssl --- TLS/SSL wrapper for socket objects.
                                                             (line    8)
* ssl (模組):                            ssl --- TLS/SSL wrapper for socket objects.
                                                             (line    6)
* SSLCertVerificationError:              Exceptions<11>.     (line   79)
* SSLContext (ssl 中的類別):             SSL Contexts.       (line   14)
* SSLEOFError:                           Exceptions<11>.     (line   71)
* SSLError:                              Exceptions<11>.     (line    6)
* SSLErrorNumber (ssl 中的類別):         Constants<9>.       (line  515)
* SSLKEYLOGFILE:                         Context creation.   (line   33)
* SSLKEYLOGFILE <1>:                     Context creation.   (line   66)
* SSLObject (ssl 中的類別):              Memory BIO Support<2>.
                                                             (line   30)
* sslobject_class (ssl.SSLContext 的屬性): SSL Contexts.     (line  472)
* SSLSession (ssl 中的類別):             SSL session.        (line    8)
* SSLSocket (ssl 中的類別):              SSL Sockets.        (line    6)
* sslsocket_class (ssl.SSLContext 的屬性): SSL Contexts.     (line  446)
* SSLSyscallError:                       Exceptions<11>.     (line   62)
* SSLv3 (ssl.TLSVersion 的屬性):         Constants<9>.       (line  537)
* SSLWantReadError:                      Exceptions<11>.     (line   44)
* SSLWantWriteError:                     Exceptions<11>.     (line   53)
* SSLZeroReturnError:                    Exceptions<11>.     (line   35)
* SSL_CERT_FILE:                         LibreSSL support.   (line   15)
* SSL_CERT_PATH:                         LibreSSL support.   (line   15)
* ssl_version (ftplib.FTP_TLS 的屬性):   FTP_TLS Objects.    (line    9)
* st() (於 turtle 模組中):               Visibility.         (line   15)
* st2list() (於 parser 模組中):          Converting ST Objects.
                                                             (line   11)
* st2tuple() (於 parser 模組中):         Converting ST Objects.
                                                             (line   31)
* stack (traceback.TracebackException 的屬性): TracebackException Objects.
                                                             (line   34)
* stack viewer:                          Debug menu Shell window only.
                                                             (line   15)
* stack() (於 inspect 模組中):           The interpreter stack.
                                                             (line   82)
* stack; trace:                          The standard type hierarchy.
                                                             (line  759)
* stackable; streams:                    codecs --- Codec registry and base classes.
                                                             (line    8)
* StackSummary (traceback 中的類別):     StackSummary Objects.
                                                             (line   11)
* stack_effect() (於 dis 模組中):        Analysis functions. (line  141)
* stack_size() (於 threading 模組中):    threading --- Thread-based parallelism.
                                                             (line  136)
* stack_size() (於 _thread 模組中):      _thread --- Low-level threading API.
                                                             (line   93)
* stamp() (於 turtle 模組中):            Turtle motion.      (line  238)
* Standard C:                            String and Bytes literals.
                                                             (line   72)
* standard input:                        Complete Python programs.
                                                             (line   25)
* standard; output:                      Expression statements.
                                                             (line   17)
* standarderror (2to3 fixer):            Fixers.             (line  293)
* standard_b64decode() (於 base64 模組中): base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   75)
* standard_b64encode() (於 base64 模組中): base64 —— Base16、Base32、Base64、Base85 資料編碼.
                                                             (line   70)
* standend() (curses.window 的方法):     Window Objects.     (line  516)
* standout() (curses.window 的方法):     Window Objects.     (line  521)
* STAR (於 token 模組中):                token --- Constants used with Python parse trees.
                                                             (line   90)
* STAREQUAL (於 token 模組中):           token --- Constants used with Python parse trees.
                                                             (line  178)
* starmap() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line  148)
* starmap() (於 itertools 模組中):       Itertool functions. (line  518)
* starmap_async() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line  159)
* start (range 的屬性):                  Ranges.             (line   60)
* start (slice object attribute):        The standard type hierarchy.
                                                             (line  808)
* start (slice object attribute) <1>:    Slicings.           (line   26)
* start (UnicodeError 的屬性):           Concrete exceptions.
                                                             (line  371)
* start() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   70)
* start() (multiprocessing.managers.BaseManager 的方法): Managers.
                                                             (line   40)
* start() (multiprocessing.Process 的方法): Process and exceptions.
                                                             (line   43)
* start() (re.Match 的方法):             Match Objects.      (line  131)
* start() (threading.Thread 的方法):     Thread Objects.     (line   89)
* start() (tkinter.ttk.Progressbar 的方法): ttk Progressbar. (line    8)
* start() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder Objects.
                                                             (line   43)
* start() (於 tracemalloc 模組中):       Functions<9>.       (line   50)
* StartCdataSectionHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  300)
* StartDoctypeDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  186)
* startDocument() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line   32)
* startElement() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line   82)
* StartElementHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  224)
* startElementNS() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line  102)
* startfile() (於 os 模組中):            Process Management. (line  611)
* STARTF_USESHOWWINDOW (於 subprocess 模組中): Windows Constants.
                                                             (line   33)
* STARTF_USESTDHANDLES (於 subprocess 模組中): Windows Constants.
                                                             (line   27)
* StartNamespaceDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  279)
* startPrefixMapping() (xml.sax.handler.ContentHandler 的方法): ContentHandler Objects.
                                                             (line   49)
* startswith() (bytearray 的方法):       Bytes and Bytearray Operations.
                                                             (line  198)
* startswith() (bytes 的方法):           Bytes and Bytearray Operations.
                                                             (line  198)
* startswith() (str 的方法):             String Methods<2>.  (line  505)
* startTest() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  330)
* startTestRun() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  339)
* starttls() (imaplib.IMAP4 的方法):     IMAP4 Objects.      (line  291)
* starttls() (nntplib.NNTP 的方法):      Methods<3>.         (line   62)
* starttls() (smtplib.SMTP 的方法):      SMTP Objects.       (line  185)
* STARTUPINFO (subprocess 中的類別):     Windows Popen Helpers.
                                                             (line    9)
* start_color() (於 curses 模組中):      Functions<3>.       (line  445)
* start_component() (msilib.Directory 的方法): Directory Objects.
                                                             (line   20)
* start_new_thread() (於 _thread 模組中): _thread --- Low-level threading API.
                                                             (line   31)
* start_ns() (xml.etree.ElementTree.TreeBuilder 的方法): TreeBuilder Objects.
                                                             (line   75)
* start_server() (於 asyncio 模組中):    Streams.            (line   65)
* start_serving() (asyncio.Server 的方法): Server Objects.   (line   47)
* start_threads() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  525)
* start_tls() (asyncio.loop 的方法):     TLS Upgrade.        (line    6)
* start_unix_server() (於 asyncio 模組中): Streams.          (line  118)
* stat (模組):                           stat --- Interpreting stat results.
                                                             (line    6)
* stat() (nntplib.NNTP 的方法):          Methods<3>.         (line  219)
* stat() (os.DirEntry 的方法):           Files and Directories.
                                                             (line  940)
* stat() (pathlib.Path 的方法):          Methods<2>.         (line   35)
* stat() (poplib.POP3 的方法):           POP3 Objects.       (line   51)
* stat() (於 os 模組中):                 Files and Directories.
                                                             (line  969)
* state() (tkinter.ttk.Widget 的方法):   ttk Widget.         (line   25)
* statement:                             Glossary.           (line 1197)
* statement grouping:                    Indentation.        (line    6)
* statement; assignment, annotated:      Annotated assignment statements.
                                                             (line    6)
* statement; assignment, augmented:      Augmented assignment statements.
                                                             (line    6)
* staticmethod() (內建函式):             內建函式.           (line 1521)
* Statistic (tracemalloc 中的類別):      Statistic.          (line    6)
* StatisticDiff (tracemalloc 中的類別):  StatisticDiff.      (line    6)
* statistics (模組):                     statistics --- 數學統計函式.
                                                             (line    6)
* statistics() (tracemalloc.Snapshot 的方法): Snapshot.      (line   56)
* StatisticsError:                       Exceptions<2>.      (line    8)
* Stats (pstats 中的類別):               The Stats Class.    (line    9)
* status (http.client.HTTPResponse 的屬性): HTTPResponse Objects.
                                                             (line   51)
* status() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line  304)
* statvfs() (於 os 模組中):              Files and Directories.
                                                             (line 1229)
* stat_result (os 中的類別):             Files and Directories.
                                                             (line 1024)
* StdButtonBox (tkinter.tix 中的類別):   Basic Widgets.      (line   65)
* stderr (asyncio.asyncio.subprocess.Process 的屬性): Interacting with Subprocesses.
                                                             (line  120)
* stderr (in module sys):                The standard type hierarchy.
                                                             (line  629)
* stderr (in module sys) <1>:            Sub-interpreter support.
                                                             (line   26)
* stderr (subprocess.CalledProcessError 的屬性): Using the subprocess Module.
                                                             (line  214)
* stderr (subprocess.CompletedProcess 的屬性): Using the subprocess Module.
                                                             (line  119)
* stderr (subprocess.Popen 的屬性):      Popen Objects.      (line  123)
* stderr (subprocess.TimeoutExpired 的屬性): Using the subprocess Module.
                                                             (line  181)
* stderr (於 sys 模組中):                sys --- System-specific parameters and functions.
                                                             (line 1462)
* stdev (statistics.NormalDist 的屬性):  NormalDist objects. (line   35)
* stdev() (於 statistics 模組中):        函式細節.           (line  335)
* stdin (asyncio.asyncio.subprocess.Process 的屬性): Interacting with Subprocesses.
                                                             (line  110)
* stdin (in module sys):                 The standard type hierarchy.
                                                             (line  629)
* stdin (in module sys) <1>:             Sub-interpreter support.
                                                             (line   26)
* stdin (subprocess.Popen 的屬性):       Popen Objects.      (line  104)
* stdin (於 sys 模組中):                 sys --- System-specific parameters and functions.
                                                             (line 1462)
* stdin; stdout; sdterr:                 Process-wide parameters.
                                                             (line    9)
* stdio:                                 The standard type hierarchy.
                                                             (line  629)
* stdout (asyncio.asyncio.subprocess.Process 的屬性): Interacting with Subprocesses.
                                                             (line  115)
* stdout (in module sys):                The standard type hierarchy.
                                                             (line  629)
* stdout (in module sys) <1>:            Sub-interpreter support.
                                                             (line   26)
* stdout (subprocess.CalledProcessError 的屬性): Using the subprocess Module.
                                                             (line  210)
* stdout (subprocess.CompletedProcess 的屬性): Using the subprocess Module.
                                                             (line  109)
* stdout (subprocess.Popen 的屬性):      Popen Objects.      (line  113)
* stdout (subprocess.TimeoutExpired 的屬性): Using the subprocess Module.
                                                             (line  177)
* STDOUT (於 subprocess 模組中):         Using the subprocess Module.
                                                             (line  147)
* stdout (於 sys 模組中):                sys --- System-specific parameters and functions.
                                                             (line 1462)
* STD_ERROR_HANDLE (於 subprocess 模組中): Windows Constants.
                                                             (line   18)
* STD_INPUT_HANDLE (於 subprocess 模組中): Windows Constants.
                                                             (line    8)
* STD_OUTPUT_HANDLE (於 subprocess 模組中): Windows Constants.
                                                             (line   13)
* step (pdb command):                    Debugger Commands.  (line  162)
* step (range 的屬性):                   Ranges.             (line   69)
* step (slice object attribute):         The standard type hierarchy.
                                                             (line  808)
* step (slice object attribute) <1>:     Slicings.           (line   26)
* step() (tkinter.ttk.Progressbar 的方法): ttk Progressbar.  (line   15)
* stereocontrols() (ossaudiodev.oss_mixer_device 的方法): Mixer Device Objects.
                                                             (line   43)
* stls() (poplib.POP3 的方法):           POP3 Objects.       (line  113)
* stop (range 的屬性):                   Ranges.             (line   65)
* stop (slice object attribute):         The standard type hierarchy.
                                                             (line  808)
* stop (slice object attribute) <1>:     Slicings.           (line   26)
* stop() (asyncio.loop 的方法):          Running and stopping the loop.
                                                             (line   31)
* stop() (logging.handlers.QueueListener 的方法): QueueListener.
                                                             (line   77)
* stop() (tkinter.ttk.Progressbar 的方法): ttk Progressbar.  (line   21)
* stop() (unittest.TestResult 的方法):   Loading and running tests.
                                                             (line  310)
* stop() (於 tracemalloc 模組中):        Functions<9>.       (line   76)
* StopAsyncIteration:                    Concrete exceptions.
                                                             (line  239)
* StopIteration:                         Concrete exceptions.
                                                             (line  209)
* stopListening() (於 logging.config 模組中): Configuration functions.
                                                             (line  163)
* stopTest() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  334)
* stopTestRun() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  345)
* stop_here() (bdb.Bdb 的方法):          bdb --- Debugger framework.
                                                             (line  191)
* storbinary() (ftplib.FTP 的方法):      FTP Objects.        (line  112)
* store() (imaplib.IMAP4 的方法):        IMAP4 Objects.      (line  308)
* STORE_ACTIONS (optparse.Option 的屬性): Adding new actions.
                                                             (line   35)
* STORE_ATTR (opcode):                   Python Bytecode Instructions.
                                                             (line  510)
* STORE_DEREF (opcode):                  Python Bytecode Instructions.
                                                             (line  744)
* STORE_FAST (opcode):                   Python Bytecode Instructions.
                                                             (line  715)
* STORE_GLOBAL (opcode):                 Python Bytecode Instructions.
                                                             (line  519)
* STORE_NAME (opcode):                   Python Bytecode Instructions.
                                                             (line  483)
* STORE_SUBSCR (opcode):                 Python Bytecode Instructions.
                                                             (line  250)
* storlines() (ftplib.FTP 的方法):       FTP Objects.        (line  126)
* str (built-in class); (see also string): Ranges.           (line  125)
* str (內建類別):                        Text Sequence Type --- str.
                                                             (line   44)
* str() (於 locale 模組中):              locale --- Internationalization services.
                                                             (line  433)
* strcoll() (於 locale 模組中):          locale --- Internationalization services.
                                                             (line  375)
* StreamError:                           tarfile --- Read and write tar archive files.
                                                             (line  195)
* StreamHandler (logging 中的類別):      StreamHandler.      (line   11)
* StreamReader (asyncio 中的類別):       StreamReader.       (line    6)
* StreamReader (codecs 中的類別):        StreamReader Objects.
                                                             (line   10)
* streamreader (codecs.CodecInfo 的屬性): codecs --- Codec registry and base classes.
                                                             (line   87)
* StreamReaderWriter (codecs 中的類別):  StreamReaderWriter Objects.
                                                             (line   12)
* StreamRecoder (codecs 中的類別):       StreamRecoder Objects.
                                                             (line   13)
* StreamRequestHandler (socketserver 中的類別): Request Handler Objects.
                                                             (line   42)
* streams:                               codecs --- Codec registry and base classes.
                                                             (line    8)
* StreamWriter (asyncio 中的類別):       StreamWriter.       (line    6)
* StreamWriter (codecs 中的類別):        StreamWriter Objects.
                                                             (line   10)
* streamwriter (codecs.CodecInfo 的屬性): codecs --- Codec registry and base classes.
                                                             (line   87)
* strerror (OSError 的屬性):             Concrete exceptions.
                                                             (line  150)
* strerror():                            Raising exceptions. (line   57)
* strerror() (於 os 模組中):             Process Parameters. (line  452)
* strftime() (datetime.date 的方法):     date Objects.       (line  267)
* strftime() (datetime.datetime 的方法): datetime Objects.   (line  699)
* strftime() (datetime.time 的方法):     time Objects.       (line  209)
* strftime() (於 time 模組中):           Functions<2>.       (line  230)
* strict (csv.Dialect 的屬性):           Dialects and Formatting Parameters.
                                                             (line   70)
* strict (於 email.policy 模組中):       email policy Policy Objects.
                                                             (line  514)
* strict_domain (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line   95)
* strict_errors() (於 codecs 模組中):    Error Handlers.     (line  128)
* strict_ns_domain (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line  117)
* strict_ns_set_initial_dollar (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line  122)
* strict_ns_set_path (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line  127)
* strict_ns_unverifiable (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line  112)
* strict_rfc2965_unverifiable (http.cookiejar.DefaultCookiePolicy 的屬性): DefaultCookiePolicy Objects.
                                                             (line  103)
* strides (memoryview 的屬性):           Memory Views.       (line  451)
* string (re.Match 的屬性):              Match Objects.      (line  195)
* STRING (於 token 模組中):              token --- Constants used with Python parse trees.
                                                             (line   46)
* string (模組):                         string --- Common string operations.
                                                             (line    6)
* string literal:                        Literals.           (line    8)
* string; conversion:                    Basic customization.
                                                             (line  150)
* string; conversion <1>:                Expression statements.
                                                             (line   17)
* string; format() (built-in function):  內建函式.           (line  642)
* string; formatted literal:             String literal concatenation.
                                                             (line   24)
* string; formatting, printf:            printf-style String Formatting.
                                                             (line    6)
* string; immutable sequences:           The standard type hierarchy.
                                                             (line  154)
* string; interpolated literal:          String literal concatenation.
                                                             (line   24)
* string; interpolation, printf:         printf-style String Formatting.
                                                             (line    6)
* string; item:                          Subscriptions.      (line   38)
* string; methods:                       Text Sequence Type --- str.
                                                             (line   85)
* string; object representation:         Finalization and De-allocation.
                                                             (line   79)
* string; PyObject_Str (C function):     Object Protocol.    (line  187)
* string; str (built-in class):          Text Sequence Type --- str.
                                                             (line   44)
* string; str() (built-in function):     內建函式.           (line 1554)
* string; text sequence type:            Ranges.             (line  125)
* string; __format__() (object method):  Basic customization.
                                                             (line  150)
* string; __str__() (object method):     Basic customization.
                                                             (line  129)
* StringIO (io 中的類別):                Text I/O<2>.        (line  192)
* stringprep (模組):                     stringprep --- Internet String Preparation.
                                                             (line    6)
* strings, documentation:                定義函式 function.  (line   20)
* strings, documentation <1>:            說明文件字串.       (line    6)
* string_at() (於 ctypes 模組中):        Utility functions.  (line  194)
* strip() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  374)
* strip() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  374)
* strip() (str 的方法):                  String Methods<2>.  (line  512)
* stripspaces (curses.textpad.Textbox 的屬性): Textbox objects.
                                                             (line  115)
* strip_dirs() (pstats.Stats 的方法):    The Stats Class.    (line   34)
* strip_python_strerr() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  385)
* strptime() (datetime.datetime 的類別成員): datetime Objects.
                                                             (line  231)
* strptime() (於 time 模組中):           Functions<2>.       (line  362)
* strsignal() (於 signal 模組中):        Module contents<2>. (line  249)
* strtobool() (於 distutils.util 模組中): distutils util --- Miscellaneous other utility functions.
                                                             (line  119)
* Struct (struct 中的類別):              Classes<2>.         (line    8)
* struct (模組):                         struct --- Interpret bytes as packed binary data.
                                                             (line    6)
* Structure (ctypes 中的類別):           Structured data types.
                                                             (line   21)
* struct_time (time 中的類別):           Functions<2>.       (line  396)
* strxfrm() (於 locale 模組中):          locale --- Internationalization services.
                                                             (line  382)
* STType (於 parser 模組中):             ST Objects.         (line   10)
* Style (tkinter.ttk 中的類別):          Ttk Styling.        (line   20)
* st_atime (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1069)
* ST_ATIME (於 stat 模組中):             stat --- Interpreting stat results.
                                                             (line  163)
* st_atime_ns (os.stat_result 的屬性):   Files and Directories.
                                                             (line 1085)
* st_birthtime (os.stat_result 的屬性):  Files and Directories.
                                                             (line 1153)
* st_blksize (os.stat_result 的屬性):    Files and Directories.
                                                             (line 1131)
* st_blocks (os.stat_result 的屬性):     Files and Directories.
                                                             (line 1126)
* st_creator (os.stat_result 的屬性):    Files and Directories.
                                                             (line 1171)
* st_ctime (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1077)
* ST_CTIME (於 stat 模組中):             stat --- Interpreting stat results.
                                                             (line  171)
* st_ctime_ns (os.stat_result 的屬性):   Files and Directories.
                                                             (line 1095)
* st_dev (os.stat_result 的屬性):        Files and Directories.
                                                             (line 1045)
* ST_DEV (於 stat 模組中):               stat --- Interpreting stat results.
                                                             (line  142)
* st_file_attributes (os.stat_result 的屬性): Files and Directories.
                                                             (line 1181)
* st_flags (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1141)
* st_fstype (os.stat_result 的屬性):     Files and Directories.
                                                             (line 1160)
* st_gen (os.stat_result 的屬性):        Files and Directories.
                                                             (line 1149)
* st_gid (os.stat_result 的屬性):        Files and Directories.
                                                             (line 1057)
* ST_GID (於 stat 模組中):               stat --- Interpreting stat results.
                                                             (line  154)
* st_ino (os.stat_result 的屬性):        Files and Directories.
                                                             (line 1036)
* ST_INO (於 stat 模組中):               stat --- Interpreting stat results.
                                                             (line  138)
* st_mode (os.stat_result 的屬性):       Files and Directories.
                                                             (line 1032)
* ST_MODE (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  134)
* st_mtime (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1073)
* ST_MTIME (於 stat 模組中):             stat --- Interpreting stat results.
                                                             (line  167)
* st_mtime_ns (os.stat_result 的屬性):   Files and Directories.
                                                             (line 1090)
* st_nlink (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1049)
* ST_NLINK (於 stat 模組中):             stat --- Interpreting stat results.
                                                             (line  146)
* st_rdev (os.stat_result 的屬性):       Files and Directories.
                                                             (line 1137)
* st_reparse_tag (os.stat_result 的屬性): Files and Directories.
                                                             (line 1188)
* st_rsize (os.stat_result 的屬性):      Files and Directories.
                                                             (line 1167)
* st_size (os.stat_result 的屬性):       Files and Directories.
                                                             (line 1061)
* ST_SIZE (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  158)
* st_type (os.stat_result 的屬性):       Files and Directories.
                                                             (line 1175)
* st_uid (os.stat_result 的屬性):        Files and Directories.
                                                             (line 1053)
* ST_UID (於 stat 模組中):               stat --- Interpreting stat results.
                                                             (line  150)
* sub() (re.Pattern 的方法):             Regular Expression Objects.
                                                             (line   91)
* sub() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line  153)
* sub() (於 re 模組中):                  Module Contents.    (line  241)
* subclassing; immutable types:          Basic customization.
                                                             (line    8)
* subdirs (filecmp.dircmp 的屬性):       The dircmp class.   (line  100)
* SubElement() (於 xml.etree.ElementTree 模組中): Functions<6>.
                                                             (line  191)
* submit() (concurrent.futures.Executor 的方法): Executor Objects.
                                                             (line   12)
* submodule_search_locations (importlib.machinery.ModuleSpec 的屬性): importlib machinery -- Importers and path hooks.
                                                             (line  383)
* subn() (re.Pattern 的方法):            Regular Expression Objects.
                                                             (line   96)
* subn() (於 re 模組中):                 Module Contents.    (line  305)
* subnets() (ipaddress.IPv4Network 的方法): Network objects. (line  173)
* subnets() (ipaddress.IPv6Network 的方法): Network objects. (line  344)
* subnet_of() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  215)
* subnet_of() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  348)
* Subnormal (decimal 中的類別):          Signals.            (line   86)
* suboffsets (memoryview 的屬性):        Memory Views.       (line  459)
* subpad() (curses.window 的方法):       Window Objects.     (line  525)
* subprocess (模組):                     subprocess --- Subprocess management.
                                                             (line    6)
* SubprocessError:                       Using the subprocess Module.
                                                             (line  153)
* SubprocessProtocol (asyncio 中的類別): Base Protocols.     (line   24)
* SubprocessTransport (asyncio 中的類別): Transports Hierarchy.
                                                             (line   50)
* subprocess_exec() (asyncio.loop 的方法): Running Subprocesses.
                                                             (line   15)
* subprocess_shell() (asyncio.loop 的方法): Running Subprocesses.
                                                             (line  112)
* subscribe() (imaplib.IMAP4 的方法):    IMAP4 Objects.      (line  332)
* subscript; assignment:                 Mutable Sequence Types.
                                                             (line   16)
* subscript; operation:                  Common Sequence Operations.
                                                             (line   21)
* subscription:                          The standard type hierarchy.
                                                             (line  127)
* subscription <1>:                      The standard type hierarchy.
                                                             (line  192)
* subscription <2>:                      The standard type hierarchy.
                                                             (line  249)
* subscription <3>:                      Subscriptions.      (line    6)
* subscription; assignment:              Assignment statements.
                                                             (line  103)
* subsequent_indent (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  205)
* substitute() (string.Template 的方法): Template strings.   (line   40)
* subst_vars() (於 distutils.util 模組中): distutils util --- Miscellaneous other utility functions.
                                                             (line   82)
* subTest() (unittest.TestCase 的方法):  Test cases.         (line  105)
* subtract() (collections.Counter 的方法): Counter 物件.     (line   85)
* subtract() (decimal.Context 的方法):   Context objects.    (line  502)
* subtraction:                           Binary arithmetic operations.
                                                             (line   66)
* subtype (email.headerregistry.ContentTypeHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  278)
* subwin() (curses.window 的方法):       Window Objects.     (line  532)
* sub_commands (distutils.cmd.Command 的屬性): Creating a new Distutils command.
                                                             (line   49)
* successful() (multiprocessing.pool.AsyncResult 的方法): Process Pools.
                                                             (line  213)
* suffix_map (mimetypes.MimeTypes 的屬性): MimeTypes Objects.
                                                             (line   23)
* suffix_map (於 mimetypes 模組中):      mimetypes --- Map filenames to MIME types.
                                                             (line  127)
* suite:                                 Compound statements.
                                                             (line   18)
* suite() (於 parser 模組中):            Creating ST Objects.
                                                             (line   18)
* suiteClass (unittest.TestLoader 的屬性): Loading and running tests.
                                                             (line  191)
* sum() (內建函式):                      內建函式.           (line 1565)
* summarize() (doctest.DocTestRunner 的方法): DocTestRunner objects.
                                                             (line  116)
* summarize_address_range() (於 ipaddress 模組中): Other Module Level Functions.
                                                             (line   27)
* sum_list():                            Reference Count Details.
                                                             (line  143)
* sum_sequence():                        Reference Count Details.
                                                             (line  170)
* sum_sequence() <1>:                    Exceptions<16>.     (line   65)
* sunau (模組):                          sunau --- Read and write Sun AU files.
                                                             (line    6)
* super (pyclbr.Class 的屬性):           Class Objects<2>.   (line   38)
* super() (內建函式):                    內建函式.           (line 1581)
* supernet() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  199)
* supernet() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  346)
* supernet_of() (ipaddress.IPv4Network 的方法): Network objects.
                                                             (line  226)
* supernet_of() (ipaddress.IPv6Network 的方法): Network objects.
                                                             (line  350)
* SupportsAbs (typing 中的類別):         Classes functions and decorators.
                                                             (line  181)
* SupportsBytes (typing 中的類別):       Classes functions and decorators.
                                                             (line  171)
* SupportsComplex (typing 中的類別):     Classes functions and decorators.
                                                             (line  167)
* SupportsFloat (typing 中的類別):       Classes functions and decorators.
                                                             (line  163)
* SupportsIndex (typing 中的類別):       Classes functions and decorators.
                                                             (line  175)
* SupportsInt (typing 中的類別):         Classes functions and decorators.
                                                             (line  159)
* SupportsRound (typing 中的類別):       Classes functions and decorators.
                                                             (line  186)
* supports_bytes_environ (於 os 模組中): Process Parameters. (line  458)
* supports_dir_fd (於 os 模組中):        Files and Directories.
                                                             (line 1271)
* supports_effective_ids (於 os 模組中): Files and Directories.
                                                             (line 1296)
* supports_fd (於 os 模組中):            Files and Directories.
                                                             (line 1315)
* supports_follow_symlinks (於 os 模組中): Files and Directories.
                                                             (line 1334)
* supports_unicode_filenames (於 os.path 模組中): os path --- Common pathname manipulations.
                                                             (line  410)
* suppress() (於 contextlib 模組中):     Utilities.          (line  178)
* SuppressCrashReport (test.support 中的類別): test support --- Utilities for the Python test suite.
                                                             (line 1044)
* swapcase() (bytearray 的方法):         Bytes and Bytearray Operations.
                                                             (line  595)
* swapcase() (bytes 的方法):             Bytes and Bytearray Operations.
                                                             (line  595)
* swapcase() (str 的方法):               String Methods<2>.  (line  536)
* swap_attr() (於 test.support 模組中):  test support --- Utilities for the Python test suite.
                                                             (line  486)
* swap_item() (於 test.support 模組中):  test support --- Utilities for the Python test suite.
                                                             (line  503)
* SW_HIDE (於 subprocess 模組中):        Windows Constants.  (line   23)
* Symbol (symtable 中的類別):            Examining Symbol Tables.
                                                             (line  103)
* symbol (模組):                         symbol --- Constants used with Python parse trees.
                                                             (line    6)
* SymbolTable (symtable 中的類別):       Examining Symbol Tables.
                                                             (line    6)
* symlink() (於 os 模組中):              Files and Directories.
                                                             (line 1357)
* symlink_to() (pathlib.Path 的方法):    Methods<2>.         (line  387)
* symmetric_difference() (frozenset 的方法): Set Types --- set frozenset.
                                                             (line  116)
* symmetric_difference_update() (frozenset 的方法): Set Types --- set frozenset.
                                                             (line  188)
* symtable (模組):                       symtable --- Access to the compiler's symbol tables.
                                                             (line    6)
* symtable() (於 symtable 模組中):       Generating Symbol Tables.
                                                             (line    6)
* sym_name (於 symbol 模組中):           symbol --- Constants used with Python parse trees.
                                                             (line   19)
* sync() (dbm.dumb.dumbdbm 的方法):      dbm dumb --- Portable DBM implementation.
                                                             (line   78)
* sync() (dbm.gnu.gdbm 的方法):          dbm gnu --- GNU's reinterpretation of dbm.
                                                             (line  113)
* sync() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line  162)
* sync() (shelve.Shelf 的方法):          shelve --- Python object persistence.
                                                             (line   63)
* sync() (於 os 模組中):                 Files and Directories.
                                                             (line 1398)
* syncdown() (curses.window 的方法):     Window Objects.     (line  542)
* synchronized() (於 multiprocessing.sharedctypes 模組中): The multiprocessing sharedctypes module.
                                                             (line   88)
* SyncManager (multiprocessing.managers 中的類別): Managers. (line  133)
* syncok() (curses.window 的方法):       Window Objects.     (line  548)
* syncup() (curses.window 的方法):       Window Objects.     (line  553)
* syntax:                                Notation.           (line    6)
* SyntaxErr:                             Exceptions<14>.     (line   93)
* SyntaxError:                           Concrete exceptions.
                                                             (line  246)
* SyntaxWarning:                         Warnings.           (line   32)
* sys (模組):                            sys --- System-specific parameters and functions.
                                                             (line    6)
* sys.exc_info:                          The standard type hierarchy.
                                                             (line  759)
* sys.last_traceback:                    The standard type hierarchy.
                                                             (line  759)
* 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:                            The standard type hierarchy.
                                                             (line  629)
* sys.stdin:                             The standard type hierarchy.
                                                             (line  629)
* sys.stdout:                            The standard type hierarchy.
                                                             (line  629)
* sysconf() (於 os 模組中):              Miscellaneous System Information.
                                                             (line   56)
* sysconfig (模組):                      sysconfig --- Provide access to Python's configuration information.
                                                             (line    6)
* sysconf_names (於 os 模組中):          Miscellaneous System Information.
                                                             (line   66)
* syslog (模組):                         syslog --- Unix syslog library routines.
                                                             (line    6)
* syslog() (於 syslog 模組中):           syslog --- Unix syslog library routines.
                                                             (line   18)
* SysLogHandler (logging.handlers 中的類別): SysLogHandler.  (line   10)
* system() (於 os 模組中):               Process Management. (line  647)
* system() (於 platform 模組中):         Cross Platform.     (line  121)
* SystemError:                           Concrete exceptions.
                                                             (line  285)
* SystemError (built-in exception):      模組物件模組.       (line   55)
* SystemError (built-in exception) <1>:  模組物件模組.       (line   81)
* SystemExit:                            Concrete exceptions.
                                                             (line  299)
* SystemExit (built-in exception):       Exceptions.         (line   26)
* systemId (xml.dom.DocumentType 的屬性): DocumentType Objects.
                                                             (line   22)
* SystemRandom (random 中的類別):        Alternative Generator.
                                                             (line   11)
* SystemRandom (secrets 中的類別):       Random numbers.     (line    9)
* SystemRoot:                            Popen Constructor.  (line  233)
* system_alias() (於 platform 模組中):   Cross Platform.     (line  127)
* system_must_validate_cert() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  219)
* sys_exc (2to3 fixer):                  Fixers.             (line  297)
* sys_version (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  136)
* S_ENFMT (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  317)
* S_IEXEC (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  331)
* S_IFBLK (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  206)
* S_IFCHR (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  214)
* S_IFDIR (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  210)
* S_IFDOOR (於 stat 模組中):             stat --- Interpreting stat results.
                                                             (line  222)
* S_IFIFO (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  218)
* S_IFLNK (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  198)
* S_IFMT() (於 stat 模組中):             stat --- Interpreting stat results.
                                                             (line   78)
* S_IFPORT (於 stat 模組中):             stat --- Interpreting stat results.
                                                             (line  228)
* S_IFREG (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  202)
* S_IFSOCK (於 stat 模組中):             stat --- Interpreting stat results.
                                                             (line  194)
* S_IFWHT (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  234)
* S_IMODE() (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line   71)
* S_IREAD (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  323)
* S_IRGRP (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  289)
* S_IROTH (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  305)
* S_IRUSR (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  273)
* S_IRWXG (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  285)
* S_IRWXO (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  301)
* S_IRWXU (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  269)
* S_ISBLK() (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line   30)
* S_ISCHR() (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line   25)
* S_ISDIR() (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line   21)
* S_ISDOOR() (於 stat 模組中):           stat --- Interpreting stat results.
                                                             (line   50)
* S_ISFIFO() (於 stat 模組中):           stat --- Interpreting stat results.
                                                             (line   38)
* S_ISGID (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  251)
* S_ISLNK() (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line   42)
* S_ISPORT() (於 stat 模組中):           stat --- Interpreting stat results.
                                                             (line   56)
* S_ISREG() (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line   34)
* S_ISSOCK() (於 stat 模組中):           stat --- Interpreting stat results.
                                                             (line   46)
* S_ISUID (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  247)
* S_ISVTX (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  262)
* S_ISWHT() (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line   62)
* S_IWGRP (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  293)
* S_IWOTH (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  309)
* S_IWRITE (於 stat 模組中):             stat --- Interpreting stat results.
                                                             (line  327)
* S_IWUSR (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  277)
* S_IXGRP (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  297)
* S_IXOTH (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  313)
* S_IXUSR (於 stat 模組中):              stat --- Interpreting stat results.
                                                             (line  281)
* tab:                                   Indentation.        (line    6)
* tab() (tkinter.ttk.Notebook 的方法):   ttk Notebook.       (line   62)
* TabError:                              Concrete exceptions.
                                                             (line  280)
* tabnanny (模組):                       tabnanny --- Detection of ambiguous indentation.
                                                             (line    6)
* tabs() (tkinter.ttk.Notebook 的方法):  ttk Notebook.       (line   71)
* tabsize (textwrap.TextWrapper 的屬性): textwrap --- Text wrapping and filling.
                                                             (line  162)
* tag (xml.etree.ElementTree.Element 的屬性): Element Objects.
                                                             (line   16)
* tagName (xml.dom.Element 的屬性):      Element Objects<2>. (line    9)
* tag_bind() (tkinter.ttk.Treeview 的方法): ttk Treeview.    (line  303)
* tag_configure() (tkinter.ttk.Treeview 的方法): ttk Treeview.
                                                             (line  309)
* tag_has() (tkinter.ttk.Treeview 的方法): ttk Treeview.     (line  319)
* tail (xml.etree.ElementTree.Element 的屬性): Element Objects.
                                                             (line   21)
* takewhile() (於 itertools 模組中):     Itertool functions. (line  533)
* take_snapshot() (於 tracemalloc 模組中): Functions<9>.     (line   88)
* tan() (於 cmath 模組中):               Trigonometric functions<2>.
                                                             (line   33)
* tan() (於 math 模組中):                Trigonometric functions.
                                                             (line   61)
* tanh() (於 cmath 模組中):              Hyperbolic functions<2>.
                                                             (line   34)
* tanh() (於 math 模組中):               Hyperbolic functions.
                                                             (line   29)
* TarError:                              tarfile --- Read and write tar archive files.
                                                             (line  181)
* TarFile (tarfile 中的類別):            TarFile Objects.    (line   22)
* tarfile (模組):                        tarfile --- Read and write tar archive files.
                                                             (line    6)
* tarfile command line option; -c <tarfile> <source1> ... <sourceN>: Command-line options<2>.
                                                             (line   11)
* tarfile command line option; –create <tarfile> <source1> ... <sourceN>: Command-line options<2>.
                                                             (line   11)
* tarfile command line option; -e <tarfile> [<output_dir>]: Command-line options<2>.
                                                             (line   16)
* tarfile command line option; –extract <tarfile> [<output_dir>]: Command-line options<2>.
                                                             (line   16)
* tarfile command line option; -l <tarfile>: Command-line options<2>.
                                                             (line    6)
* tarfile command line option; –list <tarfile>: Command-line options<2>.
                                                             (line    6)
* tarfile command line option; -t <tarfile>: Command-line options<2>.
                                                             (line   22)
* tarfile command line option; –test <tarfile>: Command-line options<2>.
                                                             (line   22)
* tarfile command line option; -v:       Command-line options<2>.
                                                             (line   27)
* tarfile command line option; –verbose: Command-line options<2>.
                                                             (line   27)
* target:                                Assignment statements.
                                                             (line   27)
* target (xml.dom.ProcessingInstruction 的屬性): ProcessingInstruction Objects.
                                                             (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 Objects.    (line   15)
* Task (asyncio 中的類別):               Task Object.        (line    6)
* task_done() (asyncio.Queue 的方法):    Queue.              (line   78)
* task_done() (multiprocessing.JoinableQueue 的方法): Pipes and Queues.
                                                             (line  226)
* task_done() (queue.Queue 的方法):      Queue Objects.      (line   68)
* tau (於 cmath 模組中):                 Constants<3>.       (line   14)
* tau (於 math 模組中):                  Constants<2>.       (line   16)
* tbreak (pdb command):                  Debugger Commands.  (line   88)
* tb_frame (traceback attribute):        The standard type hierarchy.
                                                             (line  782)
* tb_lasti (traceback attribute):        The standard type hierarchy.
                                                             (line  782)
* tb_lineno (traceback attribute):       The standard type hierarchy.
                                                             (line  782)
* tb_locals (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  294)
* tb_next (traceback attribute):         The standard type hierarchy.
                                                             (line  794)
* tcdrain() (於 termios 模組中):         termios --- POSIX style tty control.
                                                             (line   53)
* tcflow() (於 termios 模組中):          termios --- POSIX style tty control.
                                                             (line   64)
* tcflush() (於 termios 模組中):         termios --- POSIX style tty control.
                                                             (line   58)
* tcgetattr() (於 termios 模組中):       termios --- POSIX style tty control.
                                                             (line   26)
* tcgetpgrp() (於 os 模組中):            File Descriptor Operations.
                                                             (line  646)
* Tcl() (於 tkinter 模組中):             Tkinter Modules.    (line   33)
* TCL_LIBRARY:                           How do I freeze Tkinter applications?.
                                                             (line   11)
* TCPServer (socketserver 中的類別):     socketserver --- A framework for network servers.
                                                             (line   15)
* tcsendbreak() (於 termios 模組中):     termios --- POSIX style tty control.
                                                             (line   47)
* tcsetattr() (於 termios 模組中):       termios --- POSIX style tty control.
                                                             (line   37)
* tcsetpgrp() (於 os 模組中):            File Descriptor Operations.
                                                             (line  653)
* tearDown() (unittest.TestCase 的方法): Test cases.         (line   41)
* tearDownClass() (unittest.TestCase 的方法): Test cases.    (line   69)
* tee() (於 itertools 模組中):           Itertool functions. (line  546)
* tell() (aifc.aifc 的方法):             aifc --- Read and write AIFF and AIFC files.
                                                             (line  111)
* tell() (chunk.Chunk 的方法):           chunk --- Read IFF chunked data.
                                                             (line  101)
* tell() (io.IOBase 的方法):             I/O Base Classes.   (line  135)
* tell() (io.TextIOBase 的方法):         Text I/O<2>.        (line   88)
* tell() (mmap.mmap 的方法):             mmap --- Memory-mapped file support.
                                                             (line  274)
* tell() (sunau.AU_read 的方法):         AU_read Objects.    (line   65)
* tell() (sunau.AU_write 的方法):        AU_write Objects.   (line   39)
* tell() (wave.Wave_read 的方法):        Wave_read Objects.  (line   73)
* tell() (wave.Wave_write 的方法):       Wave_write Objects. (line   62)
* Telnet (telnetlib 中的類別):           telnetlib --- Telnet client.
                                                             (line   25)
* telnetlib (模組):                      telnetlib --- Telnet client.
                                                             (line    6)
* TEMP:                                  tempfile --- Generate temporary files and directories.
                                                             (line  236)
* tempdir (於 tempfile 模組中):          tempfile --- Generate temporary files and directories.
                                                             (line  278)
* tempfile (模組):                       tempfile --- Generate temporary files and directories.
                                                             (line    6)
* Template (pipes 中的類別):             pipes --- Interface to shell pipelines.
                                                             (line   19)
* Template (string 中的類別):            Template strings.   (line   35)
* template (string.Template 的屬性):     Template strings.   (line   70)
* temporary; file:                       tempfile --- Generate temporary files and directories.
                                                             (line    8)
* temporary; file name:                  tempfile --- Generate temporary files and directories.
                                                             (line    8)
* TemporaryDirectory() (於 tempfile 模組中): tempfile --- Generate temporary files and directories.
                                                             (line  118)
* TemporaryFile() (於 tempfile 模組中):  tempfile --- Generate temporary files and directories.
                                                             (line   28)
* temp_cwd() (於 test.support 模組中):   test support --- Utilities for the Python test suite.
                                                             (line  444)
* temp_dir() (於 test.support 模組中):   test support --- Utilities for the Python test suite.
                                                             (line  425)
* temp_umask() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  458)
* teredo (ipaddress.IPv6Address 的屬性): Address objects.    (line  209)
* TERM:                                  Functions<3>.       (line  440)
* TERM <1>:                              Functions<3>.       (line  467)
* termattrs() (於 curses 模組中):        Functions<3>.       (line  459)
* terminal_size (os 中的類別):           Querying the size of a terminal.
                                                             (line   25)
* terminate() (asyncio.asyncio.subprocess.Process 的方法): Interacting with Subprocesses.
                                                             (line   90)
* terminate() (asyncio.SubprocessTransport 的方法): Subprocess Transports.
                                                             (line   49)
* terminate() (multiprocessing.pool.Pool 的方法): Process Pools.
                                                             (line  174)
* terminate() (multiprocessing.Process 的方法): Process and exceptions.
                                                             (line  149)
* terminate() (subprocess.Popen 的方法): Popen Objects.      (line   83)
* termination model:                     Exceptions.         (line   20)
* termios (模組):                        termios --- POSIX style tty control.
                                                             (line    6)
* termname() (於 curses 模組中):         Functions<3>.       (line  465)
* ternary; operator:                     Conditional expressions.
                                                             (line    6)
* ternaryfunc (C 型態):                  Slot Type typedefs. (line  113)
* test (doctest.DocTestFailure 的屬性):  Debugging.          (line  195)
* test (doctest.UnexpectedException 的屬性): Debugging.      (line  216)
* test (模組):                           test --- Regression tests package for Python.
                                                             (line    6)
* test() (於 cgi 模組中):                Functions<8>.       (line   45)
* test.support (模組):                   test support --- Utilities for the Python test suite.
                                                             (line    6)
* test.support.script_helper (模組):     test support script_helper --- Utilities for the Python execution tests.
                                                             (line    6)
* TestCase (unittest 中的類別):          Test cases.         (line    6)
* TestFailed:                            test support --- Utilities for the Python test suite.
                                                             (line   16)
* testfile() (於 doctest 模組中):        Basic API.          (line   12)
* TESTFN (於 test.support 模組中):       test support --- Utilities for the Python test suite.
                                                             (line   52)
* TESTFN_ENCODING (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line   62)
* TESTFN_NONASCII (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line   78)
* TESTFN_UNDECODABLE (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line   72)
* TESTFN_UNENCODABLE (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line   66)
* TESTFN_UNICODE (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line   58)
* TestHandler (test.support 中的類別):   test support --- Utilities for the Python test suite.
                                                             (line 1107)
* TestLoader (unittest 中的類別):        Loading and running tests.
                                                             (line    6)
* testMethodPrefix (unittest.TestLoader 的屬性): Loading and running tests.
                                                             (line  177)
* testmod() (於 doctest 模組中):         Basic API.          (line   90)
* testNamePatterns (unittest.TestLoader 的屬性): Loading and running tests.
                                                             (line  199)
* TestResult (unittest 中的類別):        Loading and running tests.
                                                             (line  216)
* tests (於 imghdr 模組中):              imghdr --- Determine the type of an image.
                                                             (line   75)
* testsource() (於 doctest 模組中):      Debugging.          (line  106)
* testsRun (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  272)
* TestSuite (unittest 中的類別):         Grouping tests.     (line    6)
* testzip() (zipfile.ZipFile 的方法):    ZipFile Objects.    (line  232)
* TEST_DATA_DIR (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  114)
* TEST_HOME_DIR (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  110)
* TEST_HTTP_URL (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  141)
* TEST_SUPPORT_DIR (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  105)
* text (SyntaxError 的屬性):             Concrete exceptions.
                                                             (line  271)
* text (traceback.TracebackException 的屬性): TracebackException Objects.
                                                             (line   50)
* Text (typing 中的類別):                Classes functions and decorators.
                                                             (line  456)
* text (xml.etree.ElementTree.Element 的屬性): Element Objects.
                                                             (line   21)
* text (於 msilib 模組中):               Precomputed tables. (line   23)
* text encoding:                         Glossary.           (line 1204)
* text file:                             Glossary.           (line 1208)
* text mode:                             內建函式.           (line 1215)
* text() (msilib.Dialog 的方法):         GUI classes.        (line   56)
* text() (於 cgitb 模組中):              cgitb --- Traceback manager for CGI scripts.
                                                             (line   48)
* Textbox (curses.textpad 中的類別):     Textbox objects.    (line    8)
* TextCalendar (calendar 中的類別):      calendar --- General calendar-related functions.
                                                             (line  128)
* textdomain() (於 gettext 模組中):      GNU gettext API.    (line   36)
* textdomain() (於 locale 模組中):       Access to message catalogs.
                                                             (line   12)
* TextFile (distutils.text_file 中的類別): distutils text_file --- The TextFile class.
                                                             (line   10)
* textinput() (於 turtle 模組中):        Input methods.      (line    6)
* TextIO (typing 中的類別):              Classes functions and decorators.
                                                             (line  470)
* TextIOBase (io 中的類別):              Text I/O<2>.        (line    6)
* TextIOWrapper (io 中的類別):           Text I/O<2>.        (line   99)
* TextTestResult (unittest 中的類別):    Loading and running tests.
                                                             (line  421)
* TextTestRunner (unittest 中的類別):    Loading and running tests.
                                                             (line  435)
* textwrap (模組):                       textwrap --- Text wrapping and filling.
                                                             (line    6)
* TextWrapper (textwrap 中的類別):       textwrap --- Text wrapping and filling.
                                                             (line  129)
* text_factory (sqlite3.Connection 的屬性): Connection Objects.
                                                             (line  335)
* theme_create() (tkinter.ttk.Style 的方法): Ttk Styling.    (line  191)
* theme_names() (tkinter.ttk.Style 的方法): Ttk Styling.     (line  239)
* theme_settings() (tkinter.ttk.Style 的方法): Ttk Styling.  (line  201)
* theme_use() (tkinter.ttk.Style 的方法): Ttk Styling.       (line  243)
* THOUSEP (於 locale 模組中):            locale --- Internationalization services.
                                                             (line  236)
* Thread (threading 中的類別):           Thread Objects.     (line   57)
* thread() (imaplib.IMAP4 的方法):       IMAP4 Objects.      (line  336)
* ThreadedChildWatcher (asyncio 中的類別): Process Watchers. (line   84)
* threading (模組):                      threading --- Thread-based parallelism.
                                                             (line    6)
* ThreadingHTTPServer (http.server 中的類別): http server --- HTTP servers.
                                                             (line   32)
* ThreadingMixIn (socketserver 中的類別): Server Creation Notes.
                                                             (line   28)
* ThreadingTCPServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   62)
* ThreadingUDPServer (socketserver 中的類別): Server Creation Notes.
                                                             (line   62)
* threading_cleanup() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  781)
* threading_setup() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  777)
* ThreadPool (multiprocessing.pool 中的類別): The multiprocessing dummy module.
                                                             (line   16)
* ThreadPoolExecutor (concurrent.futures 中的類別): ThreadPoolExecutor.
                                                             (line   39)
* threads; POSIX:                        _thread --- Low-level threading API.
                                                             (line   16)
* thread_info (於 sys 模組中):           sys --- System-specific parameters and functions.
                                                             (line 1546)
* thread_time() (於 time 模組中):        Functions<2>.       (line  477)
* thread_time_ns() (於 time 模組中):     Functions<2>.       (line  491)
* throw (2to3 fixer):                    Fixers.             (line  302)
* throw() (coroutine 的方法):            Coroutine Objects.  (line   34)
* throw() (generator 的方法):            Generator-iterator methods.
                                                             (line   38)
* ticket_lifetime_hint (ssl.SSLSession 的屬性): SSL session. (line   18)
* tigetflag() (於 curses 模組中):        Functions<3>.       (line  470)
* tigetnum() (於 curses 模組中):         Functions<3>.       (line  477)
* tigetstr() (於 curses 模組中):         Functions<3>.       (line  484)
* TILDE (於 token 模組中):               token --- Constants used with Python parse trees.
                                                             (line  150)
* tilt() (於 turtle 模組中):             Appearance.         (line  102)
* tiltangle() (於 turtle 模組中):        Appearance.         (line  137)
* time (datetime 中的類別):              time Objects.       (line   10)
* time (ssl.SSLSession 的屬性):          SSL session.        (line   14)
* time (模組):                           time --- Time access and conversions.
                                                             (line    6)
* time() (asyncio.loop 的方法):          Scheduling delayed callbacks.
                                                             (line   55)
* time() (datetime.datetime 的方法):     datetime Objects.   (line  394)
* time() (於 time 模組中):               Functions<2>.       (line  454)
* Time2Internaldate() (於 imaplib 模組中): imaplib --- IMAP4 protocol client.
                                                             (line  120)
* timedelta (datetime 中的類別):         timedelta Objects.  (line    9)
* TimedRotatingFileHandler (logging.handlers 中的類別): TimedRotatingFileHandler.
                                                             (line   10)
* timegm() (於 calendar 模組中):         calendar --- General calendar-related functions.
                                                             (line  355)
* timeit (模組):                         timeit --- Measure execution time of small code snippets.
                                                             (line    6)
* timeit command line option; -h:        命令執行列介面.     (line   44)
* timeit command line option; –help:     命令執行列介面.     (line   44)
* timeit command line option; -n N:      命令執行列介面.     (line   13)
* timeit command line option; –number=N: 命令執行列介面.     (line   13)
* timeit command line option; -p:        命令執行列介面.     (line   25)
* timeit command line option; –process:  命令執行列介面.     (line   25)
* timeit command line option; -r N:      命令執行列介面.     (line   17)
* timeit command line option; –repeat=N: 命令執行列介面.     (line   17)
* timeit command line option; -s S:      命令執行列介面.     (line   21)
* timeit command line option; –setup=S:  命令執行列介面.     (line   21)
* timeit command line option; -u:        命令執行列介面.     (line   33)
* timeit command line option; –unit=U:   命令執行列介面.     (line   33)
* timeit command line option; -v:        命令執行列介面.     (line   40)
* timeit command line option; –verbose:  命令執行列介面.     (line   40)
* timeit() (timeit.Timer 的方法):        Python Interface.   (line   68)
* timeit() (於 timeit 模組中):           Python Interface.   (line    8)
* timeout:                               Exceptions<10>.     (line   38)
* timeout (socketserver.BaseServer 的屬性): Server Objects<2>.
                                                             (line  114)
* timeout (ssl.SSLSession 的屬性):       SSL session.        (line   16)
* timeout (subprocess.TimeoutExpired 的屬性): Using the subprocess Module.
                                                             (line  168)
* timeout() (curses.window 的方法):      Window Objects.     (line  558)
* TimeoutError:                          OS exceptions.      (line  103)
* TimeoutError <1>:                      Process and exceptions.
                                                             (line  220)
* TimeoutError <2>:                      Exception classes.  (line   10)
* TimeoutError <3>:                      Exceptions<8>.      (line   10)
* TimeoutExpired:                        Using the subprocess Module.
                                                             (line  159)
* TIMEOUT_MAX (於 threading 模組中):     threading --- Thread-based parallelism.
                                                             (line  160)
* TIMEOUT_MAX (於 _thread 模組中):       _thread --- Low-level threading API.
                                                             (line  115)
* Timer (threading 中的類別):            Timer Objects.      (line   25)
* Timer (timeit 中的類別):               Python Interface.   (line   38)
* TimerHandle (asyncio 中的類別):        Callback Handles.   (line   22)
* times() (於 os 模組中):                Process Management. (line  680)
* TIMESTAMP (py_compile.PycInvalidationMode 的屬性): py_compile --- Compile Python source files.
                                                             (line  101)
* timestamp() (datetime.datetime 的方法): datetime Objects.  (line  545)
* timetuple() (datetime.date 的方法):    date Objects.       (line  179)
* timetuple() (datetime.datetime 的方法): datetime Objects.  (line  500)
* timetz() (datetime.datetime 的方法):   datetime Objects.   (line  403)
* timezone (datetime 中的類別):          timezone Objects.   (line   14)
* timezone (於 time 模組中):             Timezone Constants. (line   17)
* time_ns() (於 time 模組中):            Functions<2>.       (line  498)
* title() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  620)
* title() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  620)
* title() (str 的方法):                  String Methods<2>.  (line  542)
* title() (於 turtle 模組中):            Methods specific to Screen not inherited from TurtleScreen.
                                                             (line   49)
* Tix:                                   tkinter tix --- Extension widgets for Tk.
                                                             (line    8)
* tixCommand (tkinter.tix 中的類別):     Tix Commands.       (line    6)
* tix_addbitmapdir() (tkinter.tix.tixCommand 的方法): Tix Commands.
                                                             (line   47)
* tix_cget() (tkinter.tix.tixCommand 的方法): Tix Commands.  (line   32)
* tix_configure() (tkinter.tix.tixCommand 的方法): Tix Commands.
                                                             (line   20)
* tix_filedialog() (tkinter.tix.tixCommand 的方法): Tix Commands.
                                                             (line   57)
* tix_getbitmap() (tkinter.tix.tixCommand 的方法): Tix Commands.
                                                             (line   37)
* tix_getimage() (tkinter.tix.tixCommand 的方法): Tix Commands.
                                                             (line   68)
* tix_option_get() (tkinter.tix.tixCommand 的方法): Tix Commands.
                                                             (line   82)
* tix_resetoptions() (tkinter.tix.tixCommand 的方法): Tix Commands.
                                                             (line   86)
* Tk:                                    以 Tk 打造 GUI.     (line    6)
* Tk (tkinter 中的類別):                 Tkinter Modules.    (line   25)
* Tk (tkinter.tix 中的類別):             Using Tix.          (line    6)
* Tk Option Data Types:                  Tk Option Data Types.
                                                             (line    6)
* Tkinter:                               以 Tk 打造 GUI.     (line    6)
* tkinter (模組):                        tkinter --- Python interface to Tcl/Tk.
                                                             (line    6)
* tkinter.scrolledtext (模組):           tkinter scrolledtext --- Scrolled Text Widget.
                                                             (line    6)
* tkinter.tix (模組):                    tkinter tix --- Extension widgets for Tk.
                                                             (line    6)
* tkinter.ttk (模組):                    tkinter ttk --- Tk themed widgets.
                                                             (line    6)
* TK_LIBRARY:                            How do I freeze Tkinter applications?.
                                                             (line   11)
* TList (tkinter.tix 中的類別):          Tabular ListBox.    (line    6)
* TLS:                                   ssl --- TLS/SSL wrapper for socket objects.
                                                             (line    8)
* TLSv1 (ssl.TLSVersion 的屬性):         Constants<9>.       (line  539)
* TLSv1_1 (ssl.TLSVersion 的屬性):       Constants<9>.       (line  541)
* TLSv1_2 (ssl.TLSVersion 的屬性):       Constants<9>.       (line  543)
* TLSv1_3 (ssl.TLSVersion 的屬性):       Constants<9>.       (line  545)
* TLSVersion (ssl 中的類別):             Constants<9>.       (line  521)
* TMP:                                   tempfile --- Generate temporary files and directories.
                                                             (line  238)
* TMPDIR:                                tempfile --- Generate temporary files and directories.
                                                             (line  234)
* ToASCII() (於 encodings.idna 模組中):  encodings idna --- Internationalized Domain Names in Applications.
                                                             (line   55)
* tobuf() (tarfile.TarInfo 的方法):      TarInfo Objects.    (line   31)
* tobytes() (array.array 的方法):        array --- 高效率的數值型態陣列.
                                                             (line  194)
* tobytes() (memoryview 的方法):         Memory Views.       (line  157)
* today() (datetime.date 的類別成員):    date Objects.       (line   29)
* today() (datetime.datetime 的類別成員): datetime Objects.  (line   47)
* tofile() (array.array 的方法):         array --- 高效率的數值型態陣列.
                                                             (line  202)
* token:                                 Lexical analysis.   (line    6)
* token (shlex.shlex 的屬性):            shlex Objects.      (line  172)
* token (模組):                          token --- Constants used with Python parse trees.
                                                             (line    6)
* TokenError:                            Tokenizing Input.   (line  107)
* tokenize (模組):                       tokenize --- Tokenizer for Python source.
                                                             (line    6)
* tokenize command line option; -e:      Command-Line Usage<2>.
                                                             (line   19)
* tokenize command line option; –exact:  Command-Line Usage<2>.
                                                             (line   19)
* tokenize command line option; -h:      Command-Line Usage<2>.
                                                             (line   15)
* tokenize command line option; –help:   Command-Line Usage<2>.
                                                             (line   15)
* tokenize() (於 tokenize 模組中):       Tokenizing Input.   (line    8)
* token_bytes() (於 secrets 模組中):     Generating tokens.  (line   10)
* token_hex() (於 secrets 模組中):       Generating tokens.  (line   19)
* token_urlsafe() (於 secrets 模組中):   Generating tokens.  (line   28)
* tok_name (於 token 模組中):            token --- Constants used with Python parse trees.
                                                             (line   20)
* tolist() (array.array 的方法):         array --- 高效率的數值型態陣列.
                                                             (line  207)
* tolist() (memoryview 的方法):          Memory Views.       (line  198)
* tolist() (parser.ST 的方法):           ST Objects.         (line   29)
* tomono() (於 audioop 模組中):          audioop --- Manipulate raw audio data.
                                                             (line  200)
* toordinal() (datetime.date 的方法):    date Objects.       (line  194)
* toordinal() (datetime.datetime 的方法): datetime Objects.  (line  540)
* top() (curses.panel.Panel 的方法):     Panel Objects.      (line   53)
* top() (poplib.POP3 的方法):            POP3 Objects.       (line   86)
* toprettyxml() (xml.dom.minidom.Node 的方法): DOM Objects.  (line   58)
* top_panel() (於 curses.panel 模組中):  Functions<4>.       (line   19)
* toreadonly() (memoryview 的方法):      Memory Views.       (line  214)
* tostereo() (於 audioop 模組中):        audioop --- Manipulate raw audio data.
                                                             (line  206)
* tostring() (array.array 的方法):       array --- 高效率的數值型態陣列.
                                                             (line  211)
* tostring() (於 xml.etree.ElementTree 模組中): Functions<6>.
                                                             (line  204)
* tostringlist() (於 xml.etree.ElementTree 模組中): Functions<6>.
                                                             (line  226)
* total_changes (sqlite3.Connection 的屬性): Connection Objects.
                                                             (line  378)
* total_ordering() (於 functools 模組中): functools --- Higher-order functions and operations on callable objects.
                                                             (line  172)
* total_seconds() (datetime.timedelta 的方法): timedelta Objects.
                                                             (line  245)
* totuple() (parser.ST 的方法):          ST Objects.         (line   33)
* touch() (pathlib.Path 的方法):         Methods<2>.         (line  418)
* touchline() (curses.window 的方法):    Window Objects.     (line  568)
* touchwin() (curses.window 的方法):     Window Objects.     (line  575)
* tounicode() (array.array 的方法):      array --- 高效率的數值型態陣列.
                                                             (line  217)
* 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 Objects.        (line   43)
* to_bytes() (int 的方法):               Additional Methods on Integer Types.
                                                             (line   35)
* to_eng_string() (decimal.Context 的方法): Context objects. (line  506)
* to_eng_string() (decimal.Decimal 的方法): Decimal objects. (line  557)
* to_integral() (decimal.Decimal 的方法): Decimal objects.   (line  570)
* to_integral_exact() (decimal.Context 的方法): Context objects.
                                                             (line  516)
* to_integral_exact() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  576)
* to_integral_value() (decimal.Decimal 的方法): Decimal objects.
                                                             (line  584)
* to_sci_string() (decimal.Context 的方法): Context objects. (line  520)
* tparm() (於 curses 模組中):            Functions<3>.       (line  491)
* Trace (trace 中的類別):                Programmatic Interface.
                                                             (line    6)
* Trace (tracemalloc 中的類別):          Trace.              (line    6)
* trace (模組):                          trace --- Trace or track Python statement execution.
                                                             (line    6)
* trace command line option; -c:         Main options.       (line   12)
* trace command line option; -C:         Modifiers.          (line   11)
* trace command line option; –count:     Main options.       (line   12)
* trace command line option; –coverdir=<dir>: Modifiers.     (line   11)
* trace command line option; -f:         Modifiers.          (line    6)
* trace command line option; –file=<file>: Modifiers.        (line    6)
* trace command line option; -g:         Modifiers.          (line   33)
* trace command line option; –help:      Command-Line Usage. (line   15)
* trace command line option; –ignore-dir=<dir>: Filters.     (line   14)
* trace command line option; –ignore-module=<mod>: Filters.  (line    8)
* trace command line option; -l:         Main options.       (line   23)
* trace command line option; –listfuncs: Main options.       (line   23)
* trace command line option; -m:         Modifiers.          (line   17)
* trace command line option; –missing:   Modifiers.          (line   17)
* trace command line option; –no-report: Modifiers.          (line   27)
* trace command line option; -r:         Main options.       (line   27)
* trace command line option; -R:         Modifiers.          (line   27)
* trace command line option; –report:    Main options.       (line   27)
* trace command line option; -s:         Modifiers.          (line   22)
* trace command line option; –summary:   Modifiers.          (line   22)
* trace command line option; -t:         Main options.       (line   19)
* trace command line option; -T:         Main options.       (line   33)
* trace command line option; –timing:    Modifiers.          (line   33)
* trace command line option; –trace:     Main options.       (line   19)
* trace command line option; –trackcalls: Main options.      (line   33)
* trace command line option; –version:   Command-Line Usage. (line   19)
* trace function:                        threading --- Thread-based parallelism.
                                                             (line  124)
* trace function <1>:                    sys --- System-specific parameters and functions.
                                                             (line  743)
* trace function <2>:                    sys --- System-specific parameters and functions.
                                                             (line 1309)
* trace() (於 inspect 模組中):           The interpreter stack.
                                                             (line   91)
* Traceback (tracemalloc 中的類別):      Traceback.          (line    6)
* traceback (tracemalloc.Statistic 的屬性): Statistic.       (line   23)
* traceback (tracemalloc.StatisticDiff 的屬性): StatisticDiff.
                                                             (line   38)
* traceback (tracemalloc.Trace 的屬性):  Trace.              (line   27)
* traceback (模組):                      traceback --- Print or retrieve a stack traceback.
                                                             (line    6)
* TracebackException (traceback 中的類別): TracebackException Objects.
                                                             (line   11)
* tracebacklimit (於 sys 模組中):        sys --- System-specific parameters and functions.
                                                             (line 1580)
* tracebacks; in CGI scripts:            cgitb --- Traceback manager for CGI scripts.
                                                             (line    8)
* TracebackType (types 中的類別):        Standard Interpreter Types.
                                                             (line  182)
* traceback_limit (tracemalloc.Snapshot 的屬性): Snapshot.   (line   83)
* traceback_limit (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  218)
* tracemalloc (模組):                    tracemalloc --- Trace memory allocations.
                                                             (line    6)
* tracer() (於 turtle 模組中):           Animation control.  (line   23)
* traces (tracemalloc.Snapshot 的屬性):  Snapshot.           (line   89)
* trace_dispatch() (bdb.Bdb 的方法):     bdb --- Debugger framework.
                                                             (line  111)
* trailing; comma:                       Expression lists.   (line   24)
* transfercmd() (ftplib.FTP 的方法):     FTP Objects.        (line  135)
* TransientResource (test.support 中的類別): test support --- Utilities for the Python test suite.
                                                             (line 1015)
* transient_internet() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  462)
* translate() (bytearray 的方法):        Bytes and Bytearray Operations.
                                                             (line  210)
* translate() (bytes 的方法):            Bytes and Bytearray Operations.
                                                             (line  210)
* translate() (str 的方法):              String Methods<2>.  (line  573)
* translate() (於 fnmatch 模組中):       fnmatch --- Unix filename pattern matching.
                                                             (line   71)
* translation() (於 gettext 模組中):     Class-based API.    (line   44)
* Transport (asyncio 中的類別):          Transports Hierarchy.
                                                             (line   29)
* transport (asyncio.StreamWriter 的屬性): StreamWriter.     (line   57)
* Transport Layer Security:              ssl --- TLS/SSL wrapper for socket objects.
                                                             (line    8)
* traverseproc (C 型態):                 Supporting Cyclic Garbage Collection.
                                                             (line  101)
* Tree (tkinter.tix 中的類別):           Hierarchical ListBox.
                                                             (line   20)
* TreeBuilder (xml.etree.ElementTree 中的類別): TreeBuilder Objects.
                                                             (line    6)
* Treeview (tkinter.ttk 中的類別):       ttk Treeview.       (line    6)
* triangular() (於 random 模組中):       Real-valued distributions.
                                                             (line   25)
* triple-quoted string:                  String and Bytes literals.
                                                             (line   36)
* triple-quoted string <1>:              Glossary.           (line 1220)
* True:                                  The standard type hierarchy.
                                                             (line   93)
* true:                                  Truth Value Testing.
                                                             (line   10)
* True <1>:                              Truth Value Testing.
                                                             (line   23)
* True <2>:                              Boolean Values.     (line   15)
* True (內建變數):                       內建常數.           (line   13)
* truediv() (於 operator 模組中):        operator --- Standard operators as functions.
                                                             (line  158)
* trunc() (in module math):              Numeric Types --- int float complex.
                                                             (line  104)
* trunc() (於 math 模組中):              Number-theoretic and representation functions.
                                                             (line  227)
* truncate() (io.IOBase 的方法):         I/O Base Classes.   (line  139)
* truncate() (於 os 模組中):             Files and Directories.
                                                             (line 1406)
* truth() (於 operator 模組中):          operator --- Standard operators as functions.
                                                             (line   57)
* truth; value:                          Truth Value Testing.
                                                             (line    6)
* ttk:                                   tkinter ttk --- Tk themed widgets.
                                                             (line    8)
* tty (模組):                            tty --- Terminal control functions.
                                                             (line    6)
* tty; I/O control:                      termios --- POSIX style tty control.
                                                             (line    6)
* ttyname() (於 os 模組中):              File Descriptor Operations.
                                                             (line  661)
* tuple (內建類別):                      Tuples.             (line   12)
* Tuple (於 typing 模組中):              Classes functions and decorators.
                                                             (line  847)
* tuple2st() (於 parser 模組中):         Creating ST Objects.
                                                             (line   51)
* tuple_params (2to3 fixer):             Fixers.             (line  306)
* Turtle (turtle 中的類別):              Public classes.     (line   16)
* turtle (模組):                         turtle --- 龜圖學.  (line    6)
* turtledemo (模組):                     turtledemo --- Demo scripts.
                                                             (line    6)
* turtles() (於 turtle 模組中):          Settings and special methods.
                                                             (line   95)
* TurtleScreen (turtle 中的類別):        Public classes.     (line   22)
* turtlesize() (於 turtle 模組中):       Appearance.         (line   52)
* type:                                  The standard type hierarchy.
                                                             (line    6)
* type <1>:                              Glossary.           (line 1230)
* type (optparse.Option 的屬性):         Option attributes.  (line   19)
* type (socket.socket 的屬性):           Socket Objects.     (line  598)
* type (tarfile.TarInfo 的屬性):         TarInfo Objects.    (line   59)
* Type (typing 中的類別):                Classes functions and decorators.
                                                             (line  105)
* type (urllib.request.Request 的屬性):  Request Objects.    (line   21)
* type (內建類別):                       內建函式.           (line 1660)
* type alias:                            Glossary.           (line 1237)
* type hint:                             Glossary.           (line 1263)
* type of an object:                     Objects values and types.
                                                             (line   11)
* type; hierarchy:                       The standard type hierarchy.
                                                             (line    6)
* typeahead() (於 curses 模組中):        Functions<3>.       (line  499)
* typecode (array.array 的屬性):         array --- 高效率的數值型態陣列.
                                                             (line   98)
* typecodes (於 array 模組中):           array --- 高效率的數值型態陣列.
                                                             (line   85)
* TypedDict (typing 中的類別):           Classes functions and decorators.
                                                             (line  548)
* TYPED_ACTIONS (optparse.Option 的屬性): Adding new actions.
                                                             (line   39)
* typed_subpart_iterator() (於 email.iterators 模組中): email iterators Iterators.
                                                             (line   26)
* TypeError:                             Concrete exceptions.
                                                             (line  326)
* types (2to3 fixer):                    Fixers.             (line  311)
* TYPES (optparse.Option 的屬性):        Adding new types.   (line   11)
* types (模組):                          types --- Dynamic type creation and names for built-in types.
                                                             (line    6)
* types, internal:                       The standard type hierarchy.
                                                             (line  644)
* types_map (mimetypes.MimeTypes 的屬性): MimeTypes Objects. (line   39)
* types_map (於 mimetypes 模組中):       mimetypes --- Map filenames to MIME types.
                                                             (line  139)
* types_map_inv (mimetypes.MimeTypes 的屬性): MimeTypes Objects.
                                                             (line   47)
* TypeVar (typing 中的類別):             Classes functions and decorators.
                                                             (line    8)
* TYPE_CHECKER (optparse.Option 的屬性): Adding new types.   (line   16)
* TYPE_CHECKING (於 typing 模組中):      Classes functions and decorators.
                                                             (line  964)
* type_check_only() (於 typing 模組中):  Classes functions and decorators.
                                                             (line  732)
* TYPE_COMMENT (於 token 模組中):        token --- Constants used with Python parse trees.
                                                             (line  250)
* TYPE_IGNORE (於 token 模組中):         token --- Constants used with Python parse trees.
                                                             (line  248)
* typing (模組):                         typing --- Support for type hints.
                                                             (line    6)
* TZ:                                    Functions<2>.       (line  508)
* TZ <1>:                                Functions<2>.       (line  509)
* TZ <2>:                                Functions<2>.       (line  517)
* TZ <3>:                                Functions<2>.       (line  522)
* TZ <4>:                                Functions<2>.       (line  524)
* TZ <5>:                                Functions<2>.       (line  584)
* tzinfo (datetime 中的類別):            tzinfo Objects.     (line    6)
* tzinfo (datetime.datetime 的屬性):     datetime Objects.   (line  293)
* tzinfo (datetime.time 的屬性):         time Objects.       (line   66)
* tzname (於 time 模組中):               Timezone Constants. (line   23)
* tzname() (datetime.datetime 的方法):   datetime Objects.   (line  494)
* tzname() (datetime.time 的方法):       time Objects.       (line  243)
* tzname() (datetime.timezone 的方法):   timezone Objects.   (line   42)
* tzname() (datetime.tzinfo 的方法):     tzinfo Objects.     (line  123)
* tzset() (於 time 模組中):              Functions<2>.       (line  505)
* T_FMT (於 locale 模組中):              locale --- Internationalization services.
                                                             (line  201)
* T_FMT_AMPM (於 locale 模組中):         locale --- Internationalization services.
                                                             (line  207)
* u"; string literal:                    Literals.           (line    8)
* u’; string literal:                    Literals.           (line    8)
* u-LAW:                                 audioop --- Manipulate raw audio data.
                                                             (line   17)
* u-LAW <1>:                             aifc --- Read and write AIFF and AIFC files.
                                                             (line  159)
* u-LAW <2>:                             sndhdr --- Determine type of sound file.
                                                             (line    8)
* ucd_3_2_0 (於 unicodedata 模組中):     unicodedata --- Unicode Database.
                                                             (line  131)
* udata (select.kevent 的屬性):          Kevent Objects.     (line  179)
* UDPServer (socketserver 中的類別):     socketserver --- A framework for network servers.
                                                             (line   25)
* UF_APPEND (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line  346)
* UF_COMPRESSED (於 stat 模組中):        stat --- Interpreting stat results.
                                                             (line  358)
* UF_HIDDEN (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line  362)
* UF_IMMUTABLE (於 stat 模組中):         stat --- Interpreting stat results.
                                                             (line  342)
* UF_NODUMP (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line  338)
* UF_NOUNLINK (於 stat 模組中):          stat --- Interpreting stat results.
                                                             (line  354)
* UF_OPAQUE (於 stat 模組中):            stat --- Interpreting stat results.
                                                             (line  350)
* UID (plistlib 中的類別):               plistlib --- Generate and parse Mac OS X plist files.
                                                             (line  179)
* uid (tarfile.TarInfo 的屬性):          TarInfo Objects.    (line   72)
* uid() (imaplib.IMAP4 的方法):          IMAP4 Objects.      (line  359)
* uidl() (poplib.POP3 的方法):           POP3 Objects.       (line   98)
* ulaw2lin() (於 audioop 模組中):        audioop --- Manipulate raw audio data.
                                                             (line  213)
* ULONG_MAX:                             整數物件.           (line  191)
* umask() (於 os 模組中):                Process Parameters. (line  465)
* unalias (pdb command):                 Debugger Commands.  (line  307)
* uname (tarfile.TarInfo 的屬性):        TarInfo Objects.    (line   80)
* uname() (於 os 模組中):                Process Parameters. (line  469)
* uname() (於 platform 模組中):          Cross Platform.     (line  138)
* unary; arithmetic; operation:          Unary arithmetic and bitwise operations.
                                                             (line    6)
* unary; bitwise; operation:             Unary arithmetic and bitwise operations.
                                                             (line    6)
* unaryfunc (C 型態):                    Slot Type typedefs. (line  109)
* UNARY_INVERT (opcode):                 Python Bytecode Instructions.
                                                             (line  109)
* UNARY_NEGATIVE (opcode):               Python Bytecode Instructions.
                                                             (line  101)
* UNARY_NOT (opcode):                    Python Bytecode Instructions.
                                                             (line  105)
* UNARY_POSITIVE (opcode):               Python Bytecode Instructions.
                                                             (line   97)
* unbinding; name:                       The del statement<2>.
                                                             (line   15)
* UnboundLocalError:                     Resolution of names.
                                                             (line   16)
* UnboundLocalError <1>:                 Concrete exceptions.
                                                             (line  344)
* unbuffered I/O:                        內建函式.           (line 1215)
* UNC paths; and os.makedirs():          Files and Directories.
                                                             (line  451)
* UNCHECKED_HASH (py_compile.PycInvalidationMode 的屬性): py_compile --- Compile Python source files.
                                                             (line  114)
* unconsumed_tail (zlib.Decompress 的屬性): zlib --- Compression compatible with gzip.
                                                             (line  235)
* unctrl() (於 curses 模組中):           Functions<3>.       (line  511)
* unctrl() (於 curses.ascii 模組中):     curses ascii --- Utilities for ASCII characters.
                                                             (line  226)
* undefine_macro() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  169)
* Underflow (decimal 中的類別):          Signals.            (line   93)
* undisplay (pdb command):               Debugger Commands.  (line  267)
* undo() (於 turtle 模組中):             Turtle motion.      (line  291)
* undobufferentries() (於 turtle 模組中): Special Turtle methods.
                                                             (line   74)
* undoc_header (cmd.Cmd 的屬性):         Cmd Objects.        (line  158)
* unescape() (於 html 模組中):           html --- HyperText Markup Language support.
                                                             (line   23)
* unescape() (於 xml.sax.saxutils 模組中): xml sax saxutils --- SAX Utilities.
                                                             (line   24)
* UnexpectedException:                   Debugging.          (line  208)
* unexpectedSuccesses (unittest.TestResult 的屬性): Loading and running tests.
                                                             (line  262)
* unfreeze() (於 gc 模組中):             gc --- Garbage Collector interface.
                                                             (line  194)
* ungetch() (於 curses 模組中):          Functions<3>.       (line  518)
* ungetch() (於 msvcrt 模組中):          Console I/O.        (line   44)
* ungetmouse() (於 curses 模組中):       Functions<3>.       (line  540)
* ungetwch() (於 msvcrt 模組中):         Console I/O.        (line   50)
* unget_wch() (於 curses 模組中):        Functions<3>.       (line  531)
* unhexlify() (於 binascii 模組中):      binascii --- Convert between binary and ASCII.
                                                             (line  159)
* Unicode:                               The standard type hierarchy.
                                                             (line  156)
* Unicode <1>:                           unicodedata --- Unicode Database.
                                                             (line    6)
* Unicode <2>:                           codecs --- Codec registry and base classes.
                                                             (line    8)
* unicode (2to3 fixer):                  Fixers.             (line  316)
* Unicode Consortium:                    String and Bytes literals.
                                                             (line   36)
* Unicode; database:                     unicodedata --- Unicode Database.
                                                             (line    6)
* unicodedata (模組):                    unicodedata --- Unicode Database.
                                                             (line    6)
* UnicodeDecodeError:                    Concrete exceptions.
                                                             (line  384)
* UnicodeEncodeError:                    Concrete exceptions.
                                                             (line  379)
* UnicodeError:                          Concrete exceptions.
                                                             (line  350)
* UnicodeTranslateError:                 Concrete exceptions.
                                                             (line  389)
* UnicodeWarning:                        Warnings.           (line   50)
* unidata_version (於 unicodedata 模組中): unicodedata --- Unicode Database.
                                                             (line  127)
* unified_diff() (於 difflib 模組中):    difflib --- Helpers for computing deltas.
                                                             (line  296)
* uniform() (於 random 模組中):          Real-valued distributions.
                                                             (line   16)
* UnimplementedFileMode:                 http client --- HTTP protocol client.
                                                             (line  149)
* Union (ctypes 中的類別):               Structured data types.
                                                             (line    6)
* Union (於 typing 模組中):              Classes functions and decorators.
                                                             (line  793)
* union() (frozenset 的方法):            Set Types --- set frozenset.
                                                             (line   96)
* unique() (於 enum 模組中):             Ensuring unique enumeration values.
                                                             (line   10)
* unittest (模組):                       unittest --- 單元測試框架.
                                                             (line    6)
* unittest command line option; -b:      命令列模式選項.     (line    8)
* unittest command line option; –buffer: 命令列模式選項.     (line    8)
* unittest command line option; -c:      命令列模式選項.     (line   14)
* unittest command line option; –catch:  命令列模式選項.     (line   14)
* unittest command line option; -f:      命令列模式選項.     (line   22)
* unittest command line option; –failfast: 命令列模式選項.   (line   22)
* unittest command line option; -k:      命令列模式選項.     (line   26)
* unittest command line option; –locals: 命令列模式選項.     (line   43)
* unittest-discover command line option; -p: Test Discovery（測試探索）.
                                                             (line   33)
* unittest-discover command line option; –pattern pattern: Test Discovery（測試探索）.
                                                             (line   33)
* unittest-discover command line option; -s: Test Discovery（測試探索）.
                                                             (line   29)
* unittest-discover command line option; –start-directory directory: Test Discovery（測試探索）.
                                                             (line   29)
* unittest-discover command line option; -t: Test Discovery（測試探索）.
                                                             (line   37)
* unittest-discover command line option; –top-level-directory directory: Test Discovery（測試探索）.
                                                             (line   37)
* unittest-discover command line option; -v: Test Discovery（測試探索）.
                                                             (line   25)
* unittest-discover command line option; –verbose: Test Discovery（測試探索）.
                                                             (line   25)
* unittest.mock (模組):                  unittest mock --- mock object library.
                                                             (line    6)
* universal newlines:                    Glossary.           (line 1280)
* universal newlines; bytearray.splitlines method: Bytes and Bytearray Operations.
                                                             (line  571)
* universal newlines; bytes.splitlines method: Bytes and Bytearray Operations.
                                                             (line  571)
* universal newlines; csv.reader function: Module Contents<3>.
                                                             (line    8)
* universal newlines; importlib.abc.InspectLoader.get_source method: importlib abc -- Abstract base classes related to import.
                                                             (line  387)
* universal newlines; io.IncrementalNewlineDecoder class: Text I/O<2>.
                                                             (line  233)
* universal newlines; io.TextIOWrapper class: Text I/O<2>.   (line  123)
* universal newlines; open() built-in function: 內建函式.    (line 1153)
* universal newlines; str.splitlines method: String Methods<2>.
                                                             (line  433)
* universal newlines; subprocess module: 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  138)
* 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)
* UNIX:                                  Complete Python programs.
                                                             (line   25)
* UNIX; file control:                    fcntl --- The fcntl and ioctl system calls.
                                                             (line    6)
* UNIX; I/O control:                     fcntl --- The fcntl and ioctl system calls.
                                                             (line    6)
* UnixDatagramServer (socketserver 中的類別): socketserver --- A framework for network servers.
                                                             (line   32)
* UnixStreamServer (socketserver 中的類別): socketserver --- A framework for network servers.
                                                             (line   32)
* unix_dialect (csv 中的類別):           Module Contents<3>. (line  193)
* unix_shell (於 test.support 模組中):   test support --- Utilities for the Python test suite.
                                                             (line   44)
* unknown (uuid.SafeUUID 的屬性):        uuid --- UUID objects according to RFC 4122.
                                                             (line   40)
* UnknownHandler (urllib.request 中的類別): urllib request --- Extensible library for opening URLs.
                                                             (line  434)
* UnknownProtocol:                       http client --- HTTP protocol client.
                                                             (line  141)
* UnknownTransferEncoding:               http client --- HTTP protocol client.
                                                             (line  145)
* unknown_decl() (html.parser.HTMLParser 的方法): HTMLParser Methods.
                                                             (line  137)
* unknown_open() (urllib.request.BaseHandler 的方法): BaseHandler Objects.
                                                             (line   55)
* unknown_open() (urllib.request.UnknownHandler 的方法): UnknownHandler Objects.
                                                             (line    6)
* unlink() (multiprocessing.shared_memory.SharedMemory 的方法): multiprocessing shared_memory --- Provides shared memory for direct access across processes.
                                                             (line   73)
* unlink() (pathlib.Path 的方法):        Methods<2>.         (line  427)
* unlink() (xml.dom.minidom.Node 的方法): DOM Objects.       (line   10)
* unlink() (於 os 模組中):               Files and Directories.
                                                             (line 1424)
* unlink() (於 test.support 模組中):     test support --- Utilities for the Python test suite.
                                                             (line  171)
* unload() (於 test.support 模組中):     test support --- Utilities for the Python test suite.
                                                             (line  167)
* unlock() (mailbox.Babyl 的方法):       Babyl.              (line   59)
* unlock() (mailbox.Mailbox 的方法):     Mailbox objects.    (line  258)
* unlock() (mailbox.Maildir 的方法):     Maildir.            (line  107)
* unlock() (mailbox.mbox 的方法):        mbox.               (line   39)
* unlock() (mailbox.MH 的方法):          MH.                 (line   84)
* unlock() (mailbox.MMDF 的方法):        MMDF.               (line   35)
* unpack() (struct.Struct 的方法):       Classes<2>.         (line   35)
* unpack() (於 struct 模組中):           Functions and Exceptions.
                                                             (line   26)
* Unpacker (xdrlib 中的類別):            xdrlib --- Encode and decode XDR data.
                                                             (line   24)
* unpacking; dictionary:                 Dictionary displays.
                                                             (line   23)
* unpacking; in function calls:          Calls.              (line   74)
* unpack_archive() (於 shutil 模組中):   Archiving operations.
                                                             (line  105)
* unpack_array() (xdrlib.Unpacker 的方法): Unpacker Objects. (line   91)
* unpack_bytes() (xdrlib.Unpacker 的方法): Unpacker Objects. (line   70)
* unpack_double() (xdrlib.Unpacker 的方法): Unpacker Objects.
                                                             (line   40)
* UNPACK_EX (opcode):                    Python Bytecode Instructions.
                                                             (line  499)
* unpack_farray() (xdrlib.Unpacker 的方法): Unpacker Objects.
                                                             (line   85)
* unpack_float() (xdrlib.Unpacker 的方法): Unpacker Objects. (line   36)
* unpack_fopaque() (xdrlib.Unpacker 的方法): Unpacker Objects.
                                                             (line   54)
* unpack_from() (struct.Struct 的方法):  Classes<2>.         (line   41)
* unpack_from() (於 struct 模組中):      Functions and Exceptions.
                                                             (line   34)
* unpack_fstring() (xdrlib.Unpacker 的方法): Unpacker Objects.
                                                             (line   48)
* unpack_list() (xdrlib.Unpacker 的方法): Unpacker Objects.  (line   77)
* unpack_opaque() (xdrlib.Unpacker 的方法): Unpacker Objects.
                                                             (line   65)
* UNPACK_SEQUENCE (opcode):              Python Bytecode Instructions.
                                                             (line  494)
* unpack_string() (xdrlib.Unpacker 的方法): Unpacker Objects.
                                                             (line   59)
* unparsedEntityDecl() (xml.sax.handler.DTDHandler 的方法): DTDHandler Objects.
                                                             (line   12)
* UnparsedEntityDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  249)
* Unpickler (pickle 中的類別):           Module Interface.   (line  226)
* UnpicklingError:                       Module Interface.   (line  108)
* unquote() (於 email.utils 模組中):     email utils Miscellaneous utilities.
                                                             (line   52)
* unquote() (於 urllib.parse 模組中):    URL Quoting.        (line   59)
* unquote_plus() (於 urllib.parse 模組中): URL Quoting.      (line   75)
* unquote_to_bytes() (於 urllib.parse 模組中): URL Quoting.  (line   85)
* unraisablehook() (於 sys 模組中):      sys --- System-specific parameters and functions.
                                                             (line 1588)
* unreachable object:                    Objects values and types.
                                                             (line   37)
* unreadline() (distutils.text_file.TextFile 的方法): distutils text_file --- The TextFile class.
                                                             (line  130)
* unrecognized escape sequence:          String and Bytes literals.
                                                             (line  155)
* 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 --- Exit handlers.
                                                             (line   43)
* unregister() (於 faulthandler 模組中): Dumping the traceback on a user signal.
                                                             (line   23)
* unregister_archive_format() (於 shutil 模組中): Archiving operations.
                                                             (line  100)
* unregister_dialect() (於 csv 模組中):  Module Contents<3>. (line   79)
* unregister_unpack_format() (於 shutil 模組中): Archiving operations.
                                                             (line  143)
* unsafe (uuid.SafeUUID 的屬性):         uuid --- UUID objects according to RFC 4122.
                                                             (line   36)
* unset() (test.support.EnvironmentVarGuard 的方法): test support --- Utilities for the Python test suite.
                                                             (line 1040)
* unsetenv() (於 os 模組中):             Process Parameters. (line  499)
* UnstructuredHeader (email.headerregistry 中的類別): email headerregistry Custom Header Objects.
                                                             (line  115)
* unsubscribe() (imaplib.IMAP4 的方法):  IMAP4 Objects.      (line  366)
* UnsupportedOperation:                  High-level Module Interface.
                                                             (line   43)
* until (pdb command):                   Debugger Commands.  (line  177)
* untokenize() (於 tokenize 模組中):     Tokenizing Input.   (line   57)
* untouchwin() (curses.window 的方法):   Window Objects.     (line  580)
* 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 --- Compression compatible with gzip.
                                                             (line  227)
* unverifiable (urllib.request.Request 的屬性): Request Objects.
                                                             (line   46)
* unwrap() (ssl.SSLSocket 的方法):       SSL Sockets.        (line  270)
* unwrap() (於 inspect 模組中):          Classes and functions<2>.
                                                             (line  185)
* unwrap() (於 urllib.parse 模組中):     URL Parsing.        (line  375)
* up (pdb command):                      Debugger Commands.  (line   66)
* up() (於 turtle 模組中):               Drawing state.      (line   12)
* update() (collections.Counter 的方法): Counter 物件.       (line  108)
* update() (dict 的方法):                Mapping Types --- dict.
                                                             (line  211)
* update() (frozenset 的方法):           Set Types --- set frozenset.
                                                             (line  169)
* update() (hashlib.hash 的方法):        Hash algorithms.    (line  117)
* update() (hmac.HMAC 的方法):           hmac --- Keyed-Hashing for Message Authentication.
                                                             (line   46)
* update() (http.cookies.Morsel 的方法): Morsel Objects.     (line   94)
* update() (mailbox.Mailbox 的方法):     Mailbox objects.    (line  227)
* update() (mailbox.Maildir 的方法):     Maildir.            (line   91)
* update() (trace.CoverageResults 的方法): Programmatic Interface.
                                                             (line   52)
* update() (於 turtle 模組中):           Animation control.  (line   46)
* update_authenticated() (urllib.request.HTTPPasswordMgrWithPriorAuth 的方法): HTTPPasswordMgrWithPriorAuth Objects.
                                                             (line   24)
* update_lines_cols() (於 curses 模組中): Functions<3>.      (line  524)
* update_panels() (於 curses.panel 模組中): Functions<4>.    (line   23)
* update_visible() (mailbox.BabylMessage 的方法): BabylMessage.
                                                             (line   76)
* update_wrapper() (於 functools 模組中): functools --- Higher-order functions and operations on callable objects.
                                                             (line  484)
* upper() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  663)
* upper() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  663)
* upper() (str 的方法):                  String Methods<2>.  (line  591)
* urandom() (於 os 模組中):              Random numbers<2>.  (line   29)
* URL:                                   cgi --- Common Gateway Interface support.
                                                             (line    8)
* URL <1>:                               urllib parse --- Parse URLs into components.
                                                             (line    8)
* URL <2>:                               urllib robotparser --- Parser for robots txt.
                                                             (line    8)
* URL <3>:                               http server --- HTTP servers.
                                                             (line    8)
* url (xmlrpc.client.ProtocolError 的屬性): ProtocolError Objects.
                                                             (line   13)
* url2pathname() (於 urllib.request 模組中): urllib request --- Extensible library for opening URLs.
                                                             (line  154)
* URL; parsing:                          urllib parse --- Parse URLs into components.
                                                             (line    8)
* urlcleanup() (於 urllib.request 模組中): Legacy interface. (line   62)
* urldefrag() (於 urllib.parse 模組中):  URL Parsing.        (line  349)
* urlencode() (於 urllib.parse 模組中):  URL Quoting.        (line   97)
* URLError:                              urllib error --- Exception classes raised by urllib request.
                                                             (line   17)
* urljoin() (於 urllib.parse 模組中):    URL Parsing.        (line  319)
* urllib (2to3 fixer):                   Fixers.             (line  320)
* urllib (模組):                         urllib --- URL handling modules.
                                                             (line    6)
* urllib.error (模組):                   urllib error --- Exception classes raised by urllib request.
                                                             (line    6)
* urllib.parse (模組):                   urllib parse --- Parse URLs into components.
                                                             (line    6)
* urllib.request (模組):                 urllib request --- Extensible library for opening URLs.
                                                             (line    6)
* urllib.response (模組):                urllib response --- Response classes used by urllib.
                                                             (line    6)
* urllib.robotparser (模組):             urllib robotparser --- Parser for robots txt.
                                                             (line    6)
* urlopen() (於 urllib.request 模組中):  urllib request --- Extensible library for opening URLs.
                                                             (line   22)
* 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   80)
* urlsplit() (於 urllib.parse 模組中):   URL Parsing.        (line  237)
* urlunparse() (於 urllib.parse 模組中): URL Parsing.        (line  229)
* urlunsplit() (於 urllib.parse 模組中): URL Parsing.        (line  310)
* urn (uuid.UUID 的屬性):                uuid --- UUID objects according to RFC 4122.
                                                             (line  135)
* UseForeignDTD() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line   63)
* USER:                                  getpass --- Portable password input.
                                                             (line   38)
* user() (poplib.POP3 的方法):           POP3 Objects.       (line   31)
* user-defined; function:                The standard type hierarchy.
                                                             (line  296)
* user-defined; function; call:          Calls.              (line  123)
* user-defined; method:                  The standard type hierarchy.
                                                             (line  387)
* user; effective id:                    Process Parameters. (line  173)
* user; id:                              Process Parameters. (line  302)
* user; id, setting:                     Process Parameters. (line  448)
* UserDict (collections 中的類別):       UserDict objects.   (line   12)
* UserList (collections 中的類別):       UserList objects.   (line   16)
* USERNAME:                              Process Parameters. (line  221)
* USERNAME <1>:                          getpass --- Portable password input.
                                                             (line   39)
* username (email.headerregistry.Address 的屬性): email headerregistry Custom Header Objects.
                                                             (line  432)
* USERPROFILE:                           os path.            (line   14)
* USERPROFILE <1>:                       Changes in the Python API.
                                                             (line  115)
* USERPROFILE <2>:                       Windows<9>.         (line   13)
* USERPROFILE <3>:                       os path --- Common pathname manipulations.
                                                             (line  145)
* USERPROFILE <4>:                       Location and names of config files.
                                                             (line   67)
* userptr() (curses.panel.Panel 的方法): Panel Objects.      (line   57)
* UserString (collections 中的類別):     UserString objects. (line   12)
* UserWarning:                           Warnings.           (line   13)
* USER_BASE:                             New and Improved Modules.
                                                             (line  469)
* USER_BASE (於 site 模組中):            Module contents<3>. (line   30)
* user_call() (bdb.Bdb 的方法):          bdb --- Debugger framework.
                                                             (line  212)
* user_exception() (bdb.Bdb 的方法):     bdb --- Debugger framework.
                                                             (line  229)
* user_line() (bdb.Bdb 的方法):          bdb --- Debugger framework.
                                                             (line  218)
* user_return() (bdb.Bdb 的方法):        bdb --- Debugger framework.
                                                             (line  224)
* USER_SITE (於 site 模組中):            Module contents<3>. (line   19)
* use_default_colors() (於 curses 模組中): Functions<3>.     (line  555)
* use_env() (於 curses 模組中):          Functions<3>.       (line  545)
* use_rawinput (cmd.Cmd 的屬性):         Cmd Objects.        (line  169)
* USTAR_FORMAT (於 tarfile 模組中):      tarfile --- Read and write tar archive files.
                                                             (line  221)
* UTC:                                   time --- Time access and conversions.
                                                             (line   40)
* utc (datetime.timezone 的屬性):        timezone Objects.   (line   68)
* utcfromtimestamp() (datetime.datetime 的類別成員): datetime Objects.
                                                             (line  124)
* utcnow() (datetime.datetime 的類別成員): datetime Objects. (line   77)
* utcoffset() (datetime.datetime 的方法): datetime Objects.  (line  474)
* utcoffset() (datetime.time 的方法):    time Objects.       (line  223)
* utcoffset() (datetime.timezone 的方法): timezone Objects.  (line   30)
* utcoffset() (datetime.tzinfo 的方法):  tzinfo Objects.     (line   38)
* utctimetuple() (datetime.datetime 的方法): datetime Objects.
                                                             (line  519)
* utf8 (email.policy.EmailPolicy 的屬性): email policy Policy Objects.
                                                             (line  363)
* utf8() (poplib.POP3 的方法):           POP3 Objects.       (line  105)
* utf8_enabled (imaplib.IMAP4 的屬性):   IMAP4 Objects.      (line  388)
* utime() (於 os 模組中):                Files and Directories.
                                                             (line 1438)
* uu (模組):                             uu --- Encode and decode uuencode files.
                                                             (line    6)
* UUID (uuid 中的類別):                  uuid --- UUID objects according to RFC 4122.
                                                             (line   45)
* uuid (模組):                           uuid --- UUID objects according to RFC 4122.
                                                             (line    6)
* uuid1:                                 uuid --- UUID objects according to RFC 4122.
                                                             (line  186)
* uuid1() (於 uuid 模組中):              uuid --- UUID objects according to RFC 4122.
                                                             (line  178)
* uuid3:                                 uuid --- UUID objects according to RFC 4122.
                                                             (line  191)
* uuid3() (於 uuid 模組中):              uuid --- UUID objects according to RFC 4122.
                                                             (line  186)
* uuid4:                                 uuid --- UUID objects according to RFC 4122.
                                                             (line  195)
* uuid4() (於 uuid 模組中):              uuid --- UUID objects according to RFC 4122.
                                                             (line  191)
* uuid5:                                 uuid --- UUID objects according to RFC 4122.
                                                             (line  200)
* uuid5() (於 uuid 模組中):              uuid --- UUID objects according to RFC 4122.
                                                             (line  195)
* UuidCreate() (於 msilib 模組中):       msilib --- Read and write Microsoft Installer files.
                                                             (line   39)
* v4_int_to_packed() (於 ipaddress 模組中): Other Module Level Functions.
                                                             (line    8)
* v6_int_to_packed() (於 ipaddress 模組中): Other Module Level Functions.
                                                             (line   20)
* validator() (於 wsgiref.validate 模組中): wsgiref validate --- WSGI conformance checker.
                                                             (line   22)
* valid_signals() (於 signal 模組中):    Module contents<2>. (line  257)
* value (ctypes._SimpleCData 的屬性):    Fundamental data types<2>.
                                                             (line   17)
* value (http.cookiejar.Cookie 的屬性):  Cookie Objects<2>.  (line   32)
* value (http.cookies.Morsel 的屬性):    Morsel Objects.     (line   52)
* value (xml.dom.Attr 的屬性):           Attr Objects.       (line   23)
* value of an object:                    Objects values and types.
                                                             (line   11)
* Value() (multiprocessing.managers.SyncManager 的方法): Managers.
                                                             (line  199)
* Value() (於 multiprocessing 模組中):   Shared ctypes Objects.
                                                             (line    9)
* Value() (於 multiprocessing.sharedctypes 模組中): The multiprocessing sharedctypes module.
                                                             (line   67)
* ValueError:                            Concrete exceptions.
                                                             (line  394)
* valuerefs() (weakref.WeakValueDictionary 的方法): weakref --- Weak references.
                                                             (line  186)
* values() (contextvars.Context 的方法): Manual Context Management.
                                                             (line  104)
* values() (dict 的方法):                Mapping Types --- dict.
                                                             (line  222)
* values() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  234)
* values() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  344)
* values() (mailbox.Mailbox 的方法):     Mailbox objects.    (line  114)
* values() (types.MappingProxyType 的方法): Standard Interpreter Types.
                                                             (line  265)
* ValuesView (collections.abc 中的類別): Collections Abstract Base Classes.
                                                             (line  187)
* ValuesView (typing 中的類別):          Classes functions and decorators.
                                                             (line  294)
* value_decode() (http.cookies.BaseCookie 的方法): Cookie Objects.
                                                             (line    6)
* value_encode() (http.cookies.BaseCookie 的方法): Cookie Objects.
                                                             (line   13)
* var (contextvars.contextvars.Token.Token 的屬性): Context Variables.
                                                             (line   82)
* variable annotation:                   Glossary.           (line 1288)
* variance (statistics.NormalDist 的屬性): NormalDist objects.
                                                             (line   40)
* variance() (於 statistics 模組中):     函式細節.           (line  344)
* variant (uuid.UUID 的屬性):            uuid --- UUID objects according to RFC 4122.
                                                             (line  139)
* vars() (內建函式):                     內建函式.           (line 1701)
* vbar (tkinter.scrolledtext.ScrolledText 的屬性): tkinter scrolledtext --- Scrolled Text Widget.
                                                             (line   28)
* VBAR (於 token 模組中):                token --- Constants used with Python parse trees.
                                                             (line   98)
* VBAREQUAL (於 token 模組中):           token --- Constants used with Python parse trees.
                                                             (line  194)
* Vec2D (turtle 中的類別):               Public classes.     (line   85)
* vectorcallfunc (C 型態):               Slot Type typedefs. (line   26)
* venv (模組):                           venv --- Creation of virtual environments.
                                                             (line    6)
* VERBOSE (於 re 模組中):                Module Contents.    (line  120)
* verbose (於 tabnanny 模組中):          tabnanny --- Detection of ambiguous indentation.
                                                             (line   26)
* verbose (於 test.support 模組中):      test support --- Utilities for the Python test suite.
                                                             (line   30)
* verify() (smtplib.SMTP 的方法):        SMTP Objects.       (line   91)
* VerifyFlags (ssl 中的類別):            Constants<9>.       (line  112)
* VerifyMode (ssl 中的類別):             Constants<9>.       (line   64)
* verify_client_post_handshake() (ssl.SSLSocket 的方法): SSL Sockets.
                                                             (line  279)
* verify_code (ssl.SSLCertVerificationError 的屬性): Exceptions<11>.
                                                             (line   86)
* VERIFY_CRL_CHECK_CHAIN (於 ssl 模組中): Constants<9>.      (line   89)
* VERIFY_CRL_CHECK_LEAF (於 ssl 模組中): Constants<9>.       (line   78)
* VERIFY_DEFAULT (於 ssl 模組中):        Constants<9>.       (line   70)
* verify_flags (ssl.SSLContext 的屬性):  SSL Contexts.       (line  644)
* verify_message (ssl.SSLCertVerificationError 的屬性): Exceptions<11>.
                                                             (line   90)
* verify_mode (ssl.SSLContext 的屬性):   SSL Contexts.       (line  660)
* verify_request() (socketserver.BaseServer 的方法): Server Objects<2>.
                                                             (line  175)
* VERIFY_X509_STRICT (於 ssl 模組中):    Constants<9>.       (line   96)
* VERIFY_X509_TRUSTED_FIRST (於 ssl 模組中): Constants<9>.   (line  103)
* version (email.headerregistry.MIMEVersionHeader 的屬性): email headerregistry Custom Header Objects.
                                                             (line  242)
* version (http.client.HTTPResponse 的屬性): HTTPResponse Objects.
                                                             (line   46)
* version (http.cookiejar.Cookie 的屬性): Cookie Objects<2>. (line   20)
* version (in module sys):               Process-wide parameters.
                                                             (line  164)
* version (in module sys) <1>:           Process-wide parameters.
                                                             (line  199)
* version (in module sys) <2>:           Process-wide parameters.
                                                             (line  210)
* version (ipaddress.IPv4Address 的屬性): Address objects.   (line   39)
* version (ipaddress.IPv4Network 的屬性): Network objects.   (line   63)
* version (ipaddress.IPv6Address 的屬性): Address objects.   (line  167)
* version (ipaddress.IPv6Network 的屬性): Network objects.   (line  293)
* version (urllib.request.URLopener 的屬性): Legacy interface.
                                                             (line  139)
* version (uuid.UUID 的屬性):            uuid --- UUID objects according to RFC 4122.
                                                             (line  146)
* version (於 curses 模組中):            Constants<6>.       (line   18)
* version (於 marshal 模組中):           marshal --- Internal Python object serialization.
                                                             (line   90)
* version (於 sqlite3 模組中):           Module functions and constants.
                                                             (line    6)
* version (於 sys 模組中):               sys --- System-specific parameters and functions.
                                                             (line 1633)
* version() (ssl.SSLSocket 的方法):      SSL Sockets.        (line  301)
* version() (於 ensurepip 模組中):       Module API.         (line    8)
* version() (於 platform 模組中):        Cross Platform.     (line  133)
* version_info (於 sqlite3 模組中):      Module functions and constants.
                                                             (line   11)
* version_info (於 sys 模組中):          sys --- System-specific parameters and functions.
                                                             (line 1648)
* version_string() (http.server.BaseHTTPRequestHandler 的方法): http server --- HTTP servers.
                                                             (line  304)
* vformat() (string.Formatter 的方法):   Custom String Formatting.
                                                             (line   26)
* virtual environment:                   Glossary.           (line 1310)
* virtual machine:                       Glossary.           (line 1319)
* VIRTUAL_ENV:                           Creating virtual environments.
                                                             (line  128)
* visit() (ast.NodeVisitor 的方法):      ast Helpers.        (line  129)
* visitproc (C 型態):                    Supporting Cyclic Garbage Collection.
                                                             (line   90)
* vline() (curses.window 的方法):        Window Objects.     (line  585)
* voidcmd() (ftplib.FTP 的方法):         FTP Objects.        (line   74)
* volume (zipfile.ZipInfo 的屬性):       ZipInfo Objects.    (line  119)
* vonmisesvariate() (於 random 模組中):  Real-valued distributions.
                                                             (line   75)
* wait() (asyncio.asyncio.subprocess.Process 的方法): Interacting with Subprocesses.
                                                             (line   38)
* wait() (asyncio.Condition 的方法):     Condition.          (line   86)
* wait() (asyncio.Event 的方法):         Event.              (line   45)
* wait() (multiprocessing.pool.AsyncResult 的方法): Process Pools.
                                                             (line  204)
* 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   39)
* wait() (於 asyncio 模組中):            Waiting Primitives. (line    6)
* wait() (於 concurrent.futures 模組中): Module Functions.   (line    6)
* wait() (於 multiprocessing.connection 模組中): Listeners and Clients.
                                                             (line  113)
* wait() (於 os 模組中):                 Process Management. (line  709)
* wait3() (於 os 模組中):                Process Management. (line  806)
* wait4() (於 os 模組中):                Process Management. (line  817)
* waitid() (於 os 模組中):               Process Management. (line  719)
* waitpid() (於 os 模組中):              Process Management. (line  770)
* wait_closed() (asyncio.Server 的方法): Server Objects.     (line   95)
* wait_closed() (asyncio.StreamWriter 的方法): StreamWriter. (line   88)
* wait_for() (asyncio.Condition 的方法): Condition.          (line   98)
* wait_for() (threading.Condition 的方法): Condition Objects.
                                                             (line  127)
* wait_for() (於 asyncio 模組中):        Timeouts.           (line    6)
* wait_threads_exit() (於 test.support 模組中): test support --- Utilities for the Python test suite.
                                                             (line  520)
* walk() (email.message.EmailMessage 的方法): email message Representing an email message.
                                                             (line  465)
* walk() (email.message.Message 的方法): email message Message Representing an email message using the compat32 API.
                                                             (line  637)
* walk() (於 ast 模組中):                ast Helpers.        (line  112)
* walk() (於 os 模組中):                 Files and Directories.
                                                             (line 1481)
* walk_packages() (於 pkgutil 模組中):   pkgutil --- Package extension utility.
                                                             (line  162)
* walk_stack() (於 traceback 模組中):    traceback --- Print or retrieve a stack traceback.
                                                             (line  157)
* walk_tb() (於 traceback 模組中):       traceback --- Print or retrieve a stack traceback.
                                                             (line  166)
* want (doctest.Example 的屬性):         Example Objects.    (line   23)
* warn() (distutils.ccompiler.CCompiler 的方法): distutils ccompiler --- CCompiler base class.
                                                             (line  506)
* warn() (distutils.text_file.TextFile 的方法): distutils text_file --- The TextFile class.
                                                             (line  101)
* warn() (於 warnings 模組中):           Available Functions.
                                                             (line    6)
* Warning:                               Warnings.           (line    9)
* Warning <1>:                           Exceptions<3>.      (line    6)
* warning() (logging.Logger 的方法):     Logger Objects.     (line  220)
* warning() (xml.sax.handler.ErrorHandler 的方法): ErrorHandler Objects.
                                                             (line   29)
* warning() (於 logging 模組中):         Module-Level Functions.
                                                             (line  124)
* warnings:                              warnings --- Warning control.
                                                             (line    8)
* warnings (模組):                       warnings --- Warning control.
                                                             (line    6)
* WarningsRecorder (test.support 中的類別): test support --- Utilities for the Python test suite.
                                                             (line 1096)
* warnoptions (於 sys 模組中):           sys --- System-specific parameters and functions.
                                                             (line 1661)
* warn_explicit() (於 warnings 模組中):  Available Functions.
                                                             (line   32)
* wasSuccessful() (unittest.TestResult 的方法): Loading and running tests.
                                                             (line  301)
* WatchedFileHandler (logging.handlers 中的類別): WatchedFileHandler.
                                                             (line   24)
* wave (模組):                           wave --- Read and write WAV files.
                                                             (line    6)
* WCONTINUED (於 os 模組中):             Process Management. (line  836)
* WCOREDUMP() (於 os 模組中):            Process Management. (line  856)
* WeakKeyDictionary (weakref 中的類別):  weakref --- Weak references.
                                                             (line  156)
* WeakMethod (weakref 中的類別):         weakref --- Weak references.
                                                             (line  195)
* weakref (模組):                        weakref --- Weak references.
                                                             (line    6)
* WeakSet (weakref 中的類別):            weakref --- Weak references.
                                                             (line  190)
* WeakValueDictionary (weakref 中的類別): weakref --- Weak references.
                                                             (line  176)
* webbrowser (模組):                     webbrowser --- Convenient Web-browser controller.
                                                             (line    6)
* weekday() (datetime.date 的方法):      date Objects.       (line  200)
* weekday() (datetime.datetime 的方法):  datetime Objects.   (line  581)
* weekday() (於 calendar 模組中):        calendar --- General calendar-related functions.
                                                             (line  313)
* weekheader() (於 calendar 模組中):     calendar --- General calendar-related functions.
                                                             (line  318)
* weibullvariate() (於 random 模組中):   Real-valued distributions.
                                                             (line   87)
* WEXITED (於 os 模組中):                Process Management. (line  747)
* WEXITSTATUS() (於 os 模組中):          Process Management. (line  902)
* wfile (http.server.BaseHTTPRequestHandler 的屬性): http server --- HTTP servers.
                                                             (line  118)
* what() (於 imghdr 模組中):             imghdr --- Determine the type of an image.
                                                             (line   15)
* what() (於 sndhdr 模組中):             sndhdr --- Determine type of sound file.
                                                             (line   25)
* whathdr() (於 sndhdr 模組中):          sndhdr --- Determine type of sound file.
                                                             (line   33)
* whatis (pdb command):                  Debugger Commands.  (line  247)
* when() (asyncio.TimerHandle 的方法):   Callback Handles.   (line   29)
* where (pdb command):                   Debugger Commands.  (line   55)
* which() (於 shutil 模組中):            Directory and files operations.
                                                             (line  369)
* whichdb() (於 dbm 模組中):             dbm --- Interfaces to Unix "databases".
                                                             (line   23)
* whitespace (shlex.shlex 的屬性):       shlex Objects.      (line  104)
* whitespace (於 string 模組中):         String constants.   (line   47)
* whitespace_split (shlex.shlex 的屬性): shlex Objects.      (line  128)
* Widget (tkinter.ttk 中的類別):         ttk Widget.         (line    9)
* width (textwrap.TextWrapper 的屬性):   textwrap --- Text wrapping and filling.
                                                             (line  149)
* width() (於 turtle 模組中):            Drawing state.      (line   18)
* WIFCONTINUED() (於 os 模組中):         Process Management. (line  866)
* WIFEXITED() (於 os 模組中):            Process Management. (line  894)
* WIFSIGNALED() (於 os 模組中):          Process Management. (line  887)
* WIFSTOPPED() (於 os 模組中):           Process Management. (line  876)
* win32_edition() (於 platform 模組中):  Windows Platform.   (line   19)
* win32_is_iot() (於 platform 模組中):   Windows Platform.   (line   27)
* win32_ver() (於 platform 模組中):      Windows Platform.   (line    6)
* WinDLL (ctypes 中的類別):              Loading shared libraries.
                                                             (line   46)
* window manager (widgets):              The Window Manager. (line    6)
* window() (curses.panel.Panel 的方法):  Panel Objects.      (line   62)
* Windows:                               Complete Python programs.
                                                             (line   25)
* Windows ini file:                      configparser --- Configuration file parser.
                                                             (line    8)
* WindowsError:                          Concrete exceptions.
                                                             (line  415)
* WindowsPath (pathlib 中的類別):        Concrete paths.     (line   32)
* WindowsProactorEventLoopPolicy (asyncio 中的類別): Policy Objects.
                                                             (line   68)
* WindowsRegistryFinder (importlib.machinery 中的類別): importlib machinery -- Importers and path hooks.
                                                             (line   88)
* WindowsSelectorEventLoopPolicy (asyncio 中的類別): Policy Objects.
                                                             (line   61)
* window_height() (於 turtle 模組中):    Settings and special methods.
                                                             (line  102)
* window_width() (於 turtle 模組中):     Settings and special methods.
                                                             (line  109)
* winerror (OSError 的屬性):             Concrete exceptions.
                                                             (line  138)
* WinError() (於 ctypes 模組中):         Utility functions.  (line  203)
* WINFUNCTYPE() (於 ctypes 模組中):      Function prototypes.
                                                             (line   25)
* winreg (模組):                         winreg --- Windows registry access.
                                                             (line    6)
* WinSock:                               select --- Waiting for I/O completion.
                                                             (line  144)
* winsound (模組):                       winsound --- Sound-playing interface for Windows.
                                                             (line    6)
* winver (於 sys 模組中):                sys --- System-specific parameters and functions.
                                                             (line 1667)
* WITH_CLEANUP_FINISH (opcode):          Python Bytecode Instructions.
                                                             (line  468)
* WITH_CLEANUP_START (opcode):           Python Bytecode Instructions.
                                                             (line  452)
* 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 的方法): Methods and properties.
                                                             (line  259)
* 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 --- Utilities for the Python test suite.
                                                             (line  207)
* with_suffix() (pathlib.PurePath 的方法): Methods and properties.
                                                             (line  275)
* with_traceback() (BaseException 的方法): Base classes.     (line   25)
* WNOHANG (於 os 模組中):                Process Management. (line  828)
* WNOWAIT (於 os 模組中):                Process Management. (line  747)
* wordchars (shlex.shlex 的屬性):        shlex Objects.      (line   91)
* World Wide Web:                        Internet Protocols and Support.
                                                             (line    6)
* World Wide Web <1>:                    urllib parse --- Parse URLs into components.
                                                             (line    8)
* World Wide Web <2>:                    urllib robotparser --- Parser for robots txt.
                                                             (line    8)
* wrap() (textwrap.TextWrapper 的方法):  textwrap --- Text wrapping and filling.
                                                             (line  276)
* wrap() (於 textwrap 模組中):           textwrap --- Text wrapping and filling.
                                                             (line   16)
* wrapper() (於 curses 模組中):          Functions<3>.       (line  564)
* WrapperDescriptorType (於 types 模組中): Standard Interpreter Types.
                                                             (line   88)
* wraps() (於 functools 模組中):         functools --- Higher-order functions and operations on callable objects.
                                                             (line  531)
* wrap_bio() (ssl.SSLContext 的方法):    SSL Contexts.       (line  455)
* wrap_future() (於 asyncio 模組中):     Future Functions.   (line   44)
* wrap_socket() (ssl.SSLContext 的方法): SSL Contexts.       (line  391)
* wrap_socket() (於 ssl 模組中):         Certificate handling.
                                                             (line  167)
* wrap_text() (於 distutils.fancy_getopt 模組中): distutils fancy_getopt --- Wrapper around the standard getopt module.
                                                             (line   32)
* WRITABLE (於 tkinter 模組中):          File Handlers.      (line   41)
* writable() (asyncore.dispatcher 的方法): asyncore --- Asynchronous socket handler.
                                                             (line  172)
* writable() (io.IOBase 的方法):         I/O Base Classes.   (line  151)
* write() (asyncio.StreamWriter 的方法): StreamWriter.       (line   15)
* write() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   61)
* write() (code.InteractiveInterpreter 的方法): Interactive Interpreter Objects.
                                                             (line   63)
* write() (codecs.StreamWriter 的方法):  StreamWriter Objects.
                                                             (line   31)
* write() (configparser.ConfigParser 的方法): ConfigParser Objects.
                                                             (line  256)
* write() (email.generator.BytesGenerator 的方法): email generator Generating MIME documents.
                                                             (line  118)
* write() (email.generator.Generator 的方法): email generator Generating MIME documents.
                                                             (line  214)
* write() (io.BufferedIOBase 的方法):    I/O Base Classes.   (line  323)
* write() (io.BufferedWriter 的方法):    Buffered Streams.   (line  127)
* write() (io.RawIOBase 的方法):         I/O Base Classes.   (line  210)
* write() (io.TextIOBase 的方法):        Text I/O<2>.        (line   94)
* write() (mmap.mmap 的方法):            mmap --- Memory-mapped file support.
                                                             (line  278)
* write() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line   39)
* write() (ssl.MemoryBIO 的方法):        Memory BIO Support<2>.
                                                             (line  153)
* write() (ssl.SSLSocket 的方法):        SSL Sockets.        (line   90)
* write() (telnetlib.Telnet 的方法):     Telnet Objects.     (line  101)
* write() (xml.etree.ElementTree.ElementTree 的方法): ElementTree Objects.
                                                             (line   67)
* write() (zipfile.ZipFile 的方法):      ZipFile Objects.    (line  242)
* write() (於 os 模組中):                File Descriptor Operations.
                                                             (line  669)
* write() (於 turtle 模組中):            More drawing control.
                                                             (line   29)
* writeall() (ossaudiodev.oss_audio_device 的方法): Audio Device Objects.
                                                             (line   50)
* writeframes() (aifc.aifc 的方法):      aifc --- Read and write AIFF and AIFC files.
                                                             (line  186)
* writeframes() (sunau.AU_write 的方法): AU_write Objects.   (line   51)
* writeframes() (wave.Wave_write 的方法): Wave_write Objects.
                                                             (line   74)
* writeframesraw() (aifc.aifc 的方法):   aifc --- Read and write AIFF and AIFC files.
                                                             (line  193)
* writeframesraw() (sunau.AU_write 的方法): AU_write Objects.
                                                             (line   45)
* writeframesraw() (wave.Wave_write 的方法): Wave_write Objects.
                                                             (line   68)
* writeheader() (csv.DictWriter 的方法): Writer Objects.     (line   37)
* writelines() (asyncio.StreamWriter 的方法): StreamWriter.  (line   26)
* writelines() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   68)
* writelines() (codecs.StreamWriter 的方法): StreamWriter Objects.
                                                             (line   35)
* writelines() (io.IOBase 的方法):       I/O Base Classes.   (line  157)
* writePlist() (於 plistlib 模組中):     plistlib --- Generate and parse Mac OS X plist files.
                                                             (line  141)
* writePlistToBytes() (於 plistlib 模組中): plistlib --- Generate and parse Mac OS X plist files.
                                                             (line  160)
* writepy() (zipfile.PyZipFile 的方法):  PyZipFile Objects.  (line   20)
* writer (formatter.formatter 的屬性):   The Formatter Interface.
                                                             (line   22)
* writer() (於 csv 模組中):              Module Contents<3>. (line   40)
* writerow() (csv.csvwriter 的方法):     Writer Objects.     (line   15)
* writerows() (csv.csvwriter 的方法):    Writer Objects.     (line   23)
* writestr() (zipfile.ZipFile 的方法):   ZipFile Objects.    (line  265)
* WriteTransport (asyncio 中的類別):     Transports Hierarchy.
                                                             (line   11)
* writev() (於 os 模組中):               File Descriptor Operations.
                                                             (line  687)
* writexml() (xml.dom.minidom.Node 的方法): DOM Objects.     (line   27)
* write_byte() (mmap.mmap 的方法):       mmap --- Memory-mapped file support.
                                                             (line  293)
* write_bytes() (pathlib.Path 的方法):   Methods<2>.         (line  440)
* write_docstringdict() (於 turtle 模組中): Translation of docstrings into different languages.
                                                             (line   10)
* write_eof() (asyncio.StreamWriter 的方法): StreamWriter.   (line   52)
* write_eof() (asyncio.WriteTransport 的方法): Write-only Transports.
                                                             (line   75)
* write_eof() (ssl.MemoryBIO 的方法):    Memory BIO Support<2>.
                                                             (line  161)
* write_file() (於 distutils.file_util 模組中): distutils file_util --- Single file operations.
                                                             (line   43)
* write_history_file() (於 readline 模組中): History file.   (line   14)
* WRITE_RESTRICTED:                      Generic Attribute Management.
                                                             (line   92)
* write_results() (trace.CoverageResults 的方法): Programmatic Interface.
                                                             (line   57)
* write_text() (pathlib.Path 的方法):    Methods<2>.         (line  455)
* write_through (io.TextIOWrapper 的屬性): Text I/O<2>.      (line  165)
* writing; values:                       Expression statements.
                                                             (line   17)
* WrongDocumentErr:                      Exceptions<14>.     (line   97)
* wsgiref (模組):                        wsgiref --- WSGI Utilities and Reference Implementation.
                                                             (line    6)
* wsgiref.handlers (模組):               wsgiref handlers -- server/gateway base classes.
                                                             (line    6)
* wsgiref.headers (模組):                wsgiref headers -- WSGI response header tools.
                                                             (line    6)
* wsgiref.simple_server (模組):          wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line    6)
* wsgiref.util (模組):                   wsgiref util -- WSGI environment utilities.
                                                             (line    6)
* wsgiref.validate (模組):               wsgiref validate --- WSGI conformance checker.
                                                             (line    6)
* WSGIRequestHandler (wsgiref.simple_server 中的類別): wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line   75)
* WSGIServer (wsgiref.simple_server 中的類別): wsgiref simple_server -- a simple WSGI HTTP server.
                                                             (line   45)
* wsgi_file_wrapper (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  268)
* wsgi_multiprocess (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  152)
* wsgi_multithread (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  145)
* wsgi_run_once (wsgiref.handlers.BaseHandler 的屬性): wsgiref handlers -- server/gateway base classes.
                                                             (line  159)
* wShowWindow (subprocess.STARTUPINFO 的屬性): Windows Popen Helpers.
                                                             (line   49)
* WSTOPPED (於 os 模組中):               Process Management. (line  747)
* WSTOPSIG() (於 os 模組中):             Process Management. (line  911)
* wstring_at() (於 ctypes 模組中):       Utility functions.  (line  214)
* ws_comma (2to3 fixer):                 Fixers.             (line  325)
* WTERMSIG() (於 os 模組中):             Process Management. (line  920)
* WUNTRACED (於 os 模組中):              Process Management. (line  844)
* WWW:                                   Internet Protocols and Support.
                                                             (line    6)
* WWW <1>:                               urllib parse --- Parse URLs into components.
                                                             (line    8)
* WWW <2>:                               urllib robotparser --- Parser for robots txt.
                                                             (line    8)
* WWW; server:                           cgi --- Common Gateway Interface support.
                                                             (line    8)
* WWW; server <1>:                       http server --- HTTP servers.
                                                             (line    8)
* W_OK (於 os 模組中):                   Files and Directories.
                                                             (line  106)
* X (於 re 模組中):                      Module Contents.    (line  120)
* X509 certificate:                      SSL Contexts.       (line  672)
* xatom() (imaplib.IMAP4 的方法):        IMAP4 Objects.      (line  370)
* 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)
* XDR:                                   xdrlib --- Encode and decode XDR data.
                                                             (line    8)
* xdrlib (模組):                         xdrlib --- Encode and decode XDR data.
                                                             (line    6)
* xhdr() (nntplib.NNTP 的方法):          Methods<3>.         (line  320)
* XHTML:                                 html parser --- Simple HTML and XHTML parser.
                                                             (line    8)
* XHTML_NAMESPACE (於 xml.dom 模組中):   Module Contents<4>. (line   53)
* xml (模組):                            XML 處理模組.       (line    6)
* XML() (於 xml.etree.ElementTree 模組中): Functions<6>.     (line  252)
* xml.dom (模組):                        xml dom --- The Document Object Model API.
                                                             (line    6)
* xml.dom.minidom (模組):                xml dom minidom --- Minimal DOM implementation.
                                                             (line    6)
* xml.dom.pulldom (模組):                xml dom pulldom --- Support for building partial DOM trees.
                                                             (line    6)
* xml.etree.ElementInclude.default_loader() (於 xml.etree.ElementTree 模組中): Functions<7>.
                                                             (line    6)
* xml.etree.ElementInclude.include() (於 xml.etree.ElementTree 模組中): Functions<7>.
                                                             (line   17)
* xml.etree.ElementTree (模組):          xml etree ElementTree --- The ElementTree XML API.
                                                             (line    6)
* xml.parsers.expat (模組):              xml parsers expat --- Fast XML parsing using Expat.
                                                             (line    6)
* xml.parsers.expat.errors (模組):       Expat error constants.
                                                             (line    6)
* xml.parsers.expat.model (模組):        Content Model Descriptions.
                                                             (line    6)
* xml.sax (模組):                        xml sax --- Support for SAX2 parsers.
                                                             (line    6)
* xml.sax.handler (模組):                xml sax handler --- Base classes for SAX handlers.
                                                             (line    6)
* xml.sax.saxutils (模組):               xml sax saxutils --- SAX Utilities.
                                                             (line    6)
* xml.sax.xmlreader (模組):              xml sax xmlreader --- Interface for XML parsers.
                                                             (line    6)
* xmlcharrefreplace_errors() (於 codecs 模組中): Error Handlers.
                                                             (line  145)
* XmlDeclHandler() (xml.parsers.expat.xmlparser 的方法): XMLParser Objects<2>.
                                                             (line  175)
* XMLFilterBase (xml.sax.saxutils 中的類別): xml sax saxutils --- SAX Utilities.
                                                             (line   68)
* XMLGenerator (xml.sax.saxutils 中的類別): xml sax saxutils --- SAX Utilities.
                                                             (line   52)
* XMLID() (於 xml.etree.ElementTree 模組中): Functions<6>.   (line  260)
* XMLNS_NAMESPACE (於 xml.dom 模組中):   Module Contents<4>. (line   47)
* XMLParser (xml.etree.ElementTree 中的類別): XMLParser Objects.
                                                             (line    6)
* XMLParserType (於 xml.parsers.expat 模組中): xml parsers expat --- Fast XML parsing using Expat.
                                                             (line   35)
* XMLPullParser (xml.etree.ElementTree 中的類別): XMLPullParser Objects.
                                                             (line    6)
* XMLReader (xml.sax.xmlreader 中的類別): xml sax xmlreader --- Interface for XML parsers.
                                                             (line   16)
* xmlrpc.client (模組):                  xmlrpc client --- XML-RPC client access.
                                                             (line    6)
* xmlrpc.server (模組):                  xmlrpc server --- Basic XML-RPC servers.
                                                             (line    6)
* XML_ERROR_ABORTED (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  180)
* 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_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_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_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_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_SUSPENDED (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  169)
* XML_ERROR_SUSPEND_PE (於 xml.parsers.expat.errors 模組中): Expat error constants.
                                                             (line  190)
* 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 模組中):     Module Contents<4>. (line   42)
* xor() (於 operator 模組中):            operator --- Standard operators as functions.
                                                             (line  164)
* xover() (nntplib.NNTP 的方法):         Methods<3>.         (line  336)
* xpath() (nntplib.NNTP 的方法):         Methods<3>.         (line  344)
* xrange (2to3 fixer):                   Fixers.             (line  330)
* xreadlines (2to3 fixer):               Fixers.             (line  335)
* xview() (tkinter.ttk.Treeview 的方法): ttk Treeview.       (line  327)
* X_OK (於 os 模組中):                   Files and Directories.
                                                             (line  106)
* ycor() (於 turtle 模組中):             Tell Turtle's state.
                                                             (line   46)
* year (datetime.date 的屬性):           date Objects.       (line  102)
* year (datetime.datetime 的屬性):       datetime Objects.   (line  264)
* Year 2038:                             time --- Time access and conversions.
                                                             (line   30)
* yeardatescalendar() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line  106)
* yeardays2calendar() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line  114)
* yeardayscalendar() (calendar.Calendar 的方法): calendar --- General calendar-related functions.
                                                             (line  121)
* YESEXPR (於 locale 模組中):            locale --- Internationalization services.
                                                             (line  241)
* yield; examples:                       Generator-iterator methods.
                                                             (line   57)
* yield; expression:                     Yield expressions.  (line    6)
* yield; yield from (in What’s New):     PEP 3151 Reworking the OS and IO exception hierarchy.
                                                             (line   87)
* YIELD_FROM (opcode):                   Python Bytecode Instructions.
                                                             (line  350)
* YIELD_VALUE (opcode):                  Python Bytecode Instructions.
                                                             (line  346)
* yiq_to_rgb() (於 colorsys 模組中):     colorsys --- Conversions between color systems.
                                                             (line   32)
* yview() (tkinter.ttk.Treeview 的方法): ttk Treeview.       (line  331)
* Zen of Python:                         Glossary.           (line 1325)
* ZeroDivisionError:                     Concrete exceptions.
                                                             (line  401)
* zfill() (bytearray 的方法):            Bytes and Bytearray Operations.
                                                             (line  682)
* zfill() (bytes 的方法):                Bytes and Bytearray Operations.
                                                             (line  682)
* zfill() (str 的方法):                  String Methods<2>.  (line  602)
* zip (2to3 fixer):                      Fixers.             (line  339)
* zip() (內建函式):                      內建函式.           (line 1721)
* zipapp (模組):                         zipapp --- Manage executable Python zip archives.
                                                             (line    6)
* zipapp command line option; -c:        命令執行列介面<2>.  (line   45)
* zipapp command line option; –compress: 命令執行列介面<2>.  (line   45)
* zipapp command line option; -h:        命令執行列介面<2>.  (line   61)
* zipapp command line option; –help:     命令執行列介面<2>.  (line   61)
* zipapp command line option; –info:     命令執行列介面<2>.  (line   55)
* zipapp command line option; -m <mainfn>: 命令執行列介面<2>.
                                                             (line   35)
* zipapp command line option; –main=<mainfn>: 命令執行列介面<2>.
                                                             (line   35)
* zipapp command line option; -o <output>: 命令執行列介面<2>.
                                                             (line   18)
* zipapp command line option; –output=<output>: 命令執行列介面<2>.
                                                             (line   18)
* zipapp command line option; -p <interpreter>: 命令執行列介面<2>.
                                                             (line   29)
* zipapp command line option; –python=<interpreter>: 命令執行列介面<2>.
                                                             (line   29)
* ZipFile (zipfile 中的類別):            ZipFile Objects.    (line    6)
* zipfile (模組):                        zipfile --- Work with ZIP archives.
                                                             (line    6)
* zipfile command line option; -c <zipfile> <source1> ... <sourceN>: Command-line options.
                                                             (line   11)
* zipfile command line option; –create <zipfile> <source1> ... <sourceN>: Command-line options.
                                                             (line   11)
* zipfile command line option; -e <zipfile> <output_dir>: Command-line options.
                                                             (line   16)
* zipfile command line option; –extract <zipfile> <output_dir>: Command-line options.
                                                             (line   16)
* zipfile command line option; -l <zipfile>: Command-line options.
                                                             (line    6)
* zipfile command line option; –list <zipfile>: Command-line options.
                                                             (line    6)
* zipfile command line option; -t <zipfile>: Command-line options.
                                                             (line   21)
* zipfile command line option; –test <zipfile>: Command-line options.
                                                             (line   21)
* zipimport (模組):                      zipimport --- Import modules from Zip archives.
                                                             (line    6)
* zipimporter (zipimport 中的類別):      zipimporter Objects.
                                                             (line    8)
* ZipImportError:                        zipimport --- Import modules from Zip archives.
                                                             (line   55)
* ZipInfo (zipfile 中的類別):            zipfile --- Work with ZIP archives.
                                                             (line   58)
* ZIP_BZIP2 (於 zipfile 模組中):         zipfile --- Work with ZIP archives.
                                                             (line   88)
* ZIP_DEFLATED (於 zipfile 模組中):      zipfile --- Work with ZIP archives.
                                                             (line   83)
* zip_longest() (於 itertools 模組中):   Itertool functions. (line  586)
* ZIP_LZMA (於 zipfile 模組中):          zipfile --- Work with ZIP archives.
                                                             (line   95)
* ZIP_STORED (於 zipfile 模組中):        zipfile --- Work with ZIP archives.
                                                             (line   79)
* zlib (模組):                           zlib --- Compression compatible with gzip.
                                                             (line    6)
* ZLIB_RUNTIME_VERSION (於 zlib 模組中): zlib --- Compression compatible with gzip.
                                                             (line  304)
* ZLIB_VERSION (於 zlib 模組中):         zlib --- Compression compatible with gzip.
                                                             (line  297)
* 例外; AssertionError:                  The assert statement.
                                                             (line   21)
* 例外; AttributeError:                  Attribute references.
                                                             (line   10)
* 例外; GeneratorExit:                   Generator-iterator methods.
                                                             (line   47)
* 例外; GeneratorExit <1>:               Asynchronous generator-iterator methods.
                                                             (line   55)
* 例外; ImportError:                     The import statement.
                                                             (line    6)
* 例外; NameError:                       Identifiers Names.  (line   10)
* 例外; StopAsyncIteration:              Asynchronous generator-iterator methods.
                                                             (line   10)
* 例外; StopIteration:                   Generator-iterator methods.
                                                             (line   12)
* 例外; StopIteration <1>:               The yield statement.
                                                             (line    6)
* 例外; TypeError:                       Unary arithmetic and bitwise operations.
                                                             (line   19)
* 例外; ValueError:                      Shifting operations.
                                                             (line   15)
* 例外; ZeroDivisionError:               Binary arithmetic operations.
                                                             (line   28)
* 內建函式; abs:                         Emulating numeric types.
                                                             (line  116)
* 內建函式; abs <1>:                     Number Protocol.    (line   82)
* 內建函式; ascii:                       Object Protocol.    (line  178)
* 內建函式; bytes:                       Basic customization.
                                                             (line  146)
* 內建函式; bytes <1>:                   Object Protocol.    (line  198)
* 內建函式; chr:                         The standard type hierarchy.
                                                             (line  156)
* 內建函式; classmethod:                 通用物件結構.       (line  227)
* 內建函式; compile:                     The global statement.
                                                             (line   27)
* 內建函式; compile <1>:                 Code Objects.       (line    6)
* 內建函式; compile <2>:                 Standard Interpreter Types.
                                                             (line   52)
* 內建函式; compile <3>:                 Queries on ST Objects.
                                                             (line   14)
* 內建函式; compile <4>:                 匯入模組<2>.        (line  117)
* 內建函式; complex:                     Emulating numeric types.
                                                             (line  123)
* 內建函式; complex <1>:                 Numeric Types --- int float complex.
                                                             (line   27)
* 內建函式; divmod:                      Emulating numeric types.
                                                             (line   26)
* 內建函式; divmod <1>:                  Emulating numeric types.
                                                             (line   56)
* 內建函式; divmod <2>:                  Number Protocol.    (line   55)
* 內建函式; eval:                        The global statement.
                                                             (line   27)
* 內建函式; eval <1>:                    Expression input.   (line    6)
* 內建函式; eval <2>:                    Code Objects.       (line   17)
* 內建函式; eval <3>:                    pprint --- Data pretty printer.
                                                             (line  132)
* 內建函式; eval <4>:                    PrettyPrinter Objects.
                                                             (line   26)
* 內建函式; eval <5>:                    Converting ST Objects.
                                                             (line   45)
* 內建函式; exec:                        The global statement.
                                                             (line   27)
* 內建函式; exec <1>:                    內建函式.           (line  518)
* 內建函式; exec <2>:                    Code Objects.       (line   17)
* 內建函式; exec <3>:                    Converting ST Objects.
                                                             (line   45)
* 內建函式; float:                       Emulating numeric types.
                                                             (line  123)
* 內建函式; float <1>:                   Numeric Types --- int float complex.
                                                             (line   27)
* 內建函式; float <2>:                   Number Protocol.    (line  225)
* 內建函式; hash:                        Basic customization.
                                                             (line  223)
* 內建函式; hash <1>:                    Immutable Sequence Types.
                                                             (line    6)
* 內建函式; hash <2>:                    Object Protocol.    (line  422)
* 內建函式; hash <3>:                    PyTypeObject Slots. (line  314)
* 內建函式; help:                        作業系統介面.       (line   18)
* 內建函式; id:                          Objects values and types.
                                                             (line   11)
* 內建函式; int:                         Emulating numeric types.
                                                             (line  123)
* 內建函式; int <1>:                     Numeric Types --- int float complex.
                                                             (line   27)
* 內建函式; int <2>:                     Number Protocol.    (line  218)
* 內建函式; len:                         The standard type hierarchy.
                                                             (line  127)
* 內建函式; len <1>:                     The standard type hierarchy.
                                                             (line  219)
* 內建函式; len <2>:                     The standard type hierarchy.
                                                             (line  249)
* 內建函式; len <3>:                     Emulating container types.
                                                             (line   39)
* 內建函式; len <4>:                     Common Sequence Operations.
                                                             (line   21)
* 內建函式; len <5>:                     Mapping Types --- dict.
                                                             (line    6)
* 內建函式; len <6>:                     Object Protocol.    (line  468)
* 內建函式; len <7>:                     Sequence Protocol.  (line   17)
* 內建函式; len <8>:                     Mapping Protocol.   (line   20)
* 內建函式; len <9>:                     List（串列）物件.   (line   39)
* 內建函式; len <10>:                    字典物件.           (line  131)
* 內建函式; len <11>:                    Set Objects.        (line   90)
* 內建函式; max:                         Common Sequence Operations.
                                                             (line   21)
* 內建函式; min:                         Common Sequence Operations.
                                                             (line   21)
* 內建函式; open:                        Reading and Writing Files.
                                                             (line    6)
* 內建函式; open <1>:                    The standard type hierarchy.
                                                             (line  629)
* 內建函式; ord:                         The standard type hierarchy.
                                                             (line  156)
* 內建函式; pow:                         Emulating numeric types.
                                                             (line   26)
* 內建函式; pow <1>:                     Emulating numeric types.
                                                             (line   26)
* 內建函式; pow <2>:                     Emulating numeric types.
                                                             (line   56)
* 內建函式; pow <3>:                     Emulating numeric types.
                                                             (line   66)
* 內建函式; pow <4>:                     Number Protocol.    (line   64)
* 內建函式; pow <5>:                     Number Protocol.    (line  175)
* 內建函式; print:                       Basic customization.
                                                             (line  150)
* 內建函式; range:                       The for statement.  (line   38)
* 內建函式; repr:                        Expression statements.
                                                             (line   17)
* 內建函式; repr <1>:                    Finalization and De-allocation.
                                                             (line   78)
* 內建函式; repr <2>:                    Object Protocol.    (line  167)
* 內建函式; repr <3>:                    PyTypeObject Slots. (line  255)
* 內建函式; round:                       Emulating numeric types.
                                                             (line  146)
* 內建函式; slice:                       The standard type hierarchy.
                                                             (line  804)
* 內建函式; slice <1>:                   Python Bytecode Instructions.
                                                             (line  861)
* 內建函式; staticmethod:                通用物件結構.       (line  234)
* 內建函式; tuple:                       Sequence Protocol.  (line  114)
* 內建函式; tuple <1>:                   List（串列）物件.   (line  126)
* 內建函式; type:                        Objects values and types.
                                                             (line   11)
* 內建函式; type <1>:                    Metaclasses.        (line    6)
* 內建函式; type <2>:                    Type Objects.       (line    6)
* 內建函式; type <3>:                    Object Protocol.    (line  449)
* 內建函式; __import__:                  匯入模組<2>.        (line   37)
* 模組; array:                           The standard type hierarchy.
                                                             (line  213)
* 模組; array <1>:                       Binary Sequence Types --- bytes bytearray memoryview.
                                                             (line    6)
* 模組; base64:                          binascii --- Convert between binary and ASCII.
                                                             (line    6)
* 模組; bdb:                             pdb --- The Python Debugger.
                                                             (line   17)
* 模組; binhex:                          binascii --- Convert between binary and ASCII.
                                                             (line    6)
* 模組; builtins:                        The dir Function.   (line   43)
* 模組; builtins <1>:                    Complete Python programs.
                                                             (line    6)
* 模組; builtins <2>:                    嵌入式Python.       (line   12)
* 模組; builtins <3>:                    Initializing and finalizing the interpreter.
                                                             (line    8)
* 模組; builtins <4>:                    Sub-interpreter support.
                                                             (line   26)
* 模組; cmd:                             pdb --- The Python Debugger.
                                                             (line   17)
* 模組; copy:                            copyreg --- Register pickle support functions.
                                                             (line    8)
* 模組; crypt:                           pwd --- The password database.
                                                             (line   43)
* 模組; dbm.gnu:                         The standard type hierarchy.
                                                             (line  280)
* 模組; dbm.gnu <1>:                     Restrictions.       (line    6)
* 模組; dbm.ndbm:                        The standard type hierarchy.
                                                             (line  280)
* 模組; dbm.ndbm <1>:                    Restrictions.       (line    6)
* 模組; errno:                           Concrete exceptions.
                                                             (line  117)
* 模組; glob:                            fnmatch --- Unix filename pattern matching.
                                                             (line   34)
* 模組; imp:                             內建函式.           (line 1773)
* 模組; io:                              The standard type hierarchy.
                                                             (line  629)
* 模組; json:                            Saving structured data with json.
                                                             (line    6)
* 模組; math:                            Numeric Types --- int float complex.
                                                             (line  104)
* 模組; math <1>:                        Constants<3>.       (line   47)
* 模組; os:                              posix --- The most common POSIX system calls.
                                                             (line   12)
* 模組; pickle:                          copy --- Shallow and deep copy operations.
                                                             (line   68)
* 模組; pickle <1>:                      copyreg --- Register pickle support functions.
                                                             (line    8)
* 模組; pickle <2>:                      shelve --- Python object persistence.
                                                             (line    8)
* 模組; pickle <3>:                      marshal --- Internal Python object serialization.
                                                             (line   15)
* 模組; pty:                             File Descriptor Operations.
                                                             (line  351)
* 模組; pwd:                             os path --- Common pathname manipulations.
                                                             (line  139)
* 模組; pyexpat:                         xml parsers expat --- Fast XML parsing using Expat.
                                                             (line   20)
* 模組; re:                              String Methods<2>.  (line    6)
* 模組; re <1>:                          fnmatch --- Unix filename pattern matching.
                                                             (line    8)
* 模組; shelve:                          marshal --- Internal Python object serialization.
                                                             (line   15)
* 模組; signal:                          _thread --- Low-level threading API.
                                                             (line  172)
* 模組; signal <1>:                      Signal Handling<2>. (line    8)
* 模組; sitecustomize:                   site --- Site-specific configuration hook.
                                                             (line   93)
* 模組; socket:                          Internet Protocols and Support.
                                                             (line    6)
* 模組; stat:                            Files and Directories.
                                                             (line  995)
* 模組; string:                          locale --- Internationalization services.
                                                             (line  458)
* 模組; struct:                          Socket Objects.     (line  551)
* 模組; sys:                             Standard Modules.   (line    6)
* 模組; sys <1>:                         The try statement.  (line   69)
* 模組; sys <2>:                         Complete Python programs.
                                                             (line    6)
* 模組; sys <3>:                         內建函式.           (line 1215)
* 模組; sys <4>:                         嵌入式Python.       (line   12)
* 模組; sys <5>:                         Initializing and finalizing the interpreter.
                                                             (line    8)
* 模組; sys <6>:                         Sub-interpreter support.
                                                             (line   26)
* 模組; types:                           Type Objects.       (line    6)
* 模組; urllib.request:                  http client --- HTTP protocol client.
                                                             (line    8)
* 模組; usercustomize:                   site --- Site-specific configuration hook.
                                                             (line  104)
* 模組; uu:                              binascii --- Convert between binary and ASCII.
                                                             (line    6)
* 模組; _locale:                         locale --- Internationalization services.
                                                             (line   16)
* 模組; _thread:                         High-level API.     (line   44)
* 模組; __main__:                        Resolution of names.
                                                             (line   50)
* 模組; __main__ <1>:                    Complete Python programs.
                                                             (line    6)
* 模組; __main__ <2>:                    Complete Python programs.
                                                             (line   19)
* 模組; __main__ <3>:                    runpy --- Locating and executing Python modules.
                                                             (line   30)
* 模組; __main__ <4>:                    runpy --- Locating and executing Python modules.
                                                             (line   96)
* 模組; __main__ <5>:                    嵌入式Python.       (line   12)
* 模組; __main__ <6>:                    Initializing and finalizing the interpreter.
                                                             (line    8)
* 模組; __main__ <7>:                    Sub-interpreter support.
                                                             (line   26)
* 物件; asynchronous-generator:          Asynchronous generator functions.
                                                             (line   55)
* 物件; Boolean:                         The standard type hierarchy.
                                                             (line   93)
* 物件; Boolean <1>:                     Numeric Types --- int float complex.
                                                             (line    6)
* 物件; built-in function:               The standard type hierarchy.
                                                             (line  484)
* 物件; built-in function <1>:           Calls.              (line  132)
* 物件; built-in method:                 The standard type hierarchy.
                                                             (line  497)
* 物件; built-in method <1>:             Calls.              (line  132)
* 物件; bytearray:                       Mutable Sequence Types.
                                                             (line    6)
* 物件; bytearray <1>:                   Binary Sequence Types --- bytes bytearray memoryview.
                                                             (line    6)
* 物件; bytearray <2>:                   Bytearray Objects.  (line    6)
* 物件; bytearray <3>:                   Byte Array Objects. (line    6)
* 物件; bytes:                           Binary Sequence Types --- bytes bytearray memoryview.
                                                             (line    6)
* 物件; bytes <1>:                       Bytes Objects.      (line    6)
* 物件; bytes <2>:                       Bytes Objects<2>.   (line    9)
* 物件; callable:                        The standard type hierarchy.
                                                             (line  291)
* 物件; callable <1>:                    Slicings.           (line   38)
* 物件; Capsule:                         Capsules<2>.        (line    6)
* 物件; class:                           The standard type hierarchy.
                                                             (line  572)
* 物件; class <1>:                       Calls.              (line  137)
* 物件; class <2>:                       Class definitions.  (line    6)
* 物件; class instance:                  The standard type hierarchy.
                                                             (line  572)
* 物件; class instance <1>:              The standard type hierarchy.
                                                             (line  599)
* 物件; class instance <2>:              Calls.              (line  141)
* 物件; complex:                         The standard type hierarchy.
                                                             (line  119)
* 物件; complex number:                  Numeric Types --- int float complex.
                                                             (line    6)
* 物件; complex number <1>:              Complex Number Objects.
                                                             (line    6)
* 物件; dictionary:                      The standard type hierarchy.
                                                             (line  260)
* 物件; dictionary <1>:                  The standard type hierarchy.
                                                             (line  572)
* 物件; dictionary <2>:                  Basic customization.
                                                             (line  223)
* 物件; dictionary <3>:                  Dictionary displays.
                                                             (line    6)
* 物件; dictionary <4>:                  Subscriptions.      (line    6)
* 物件; dictionary <5>:                  Assignment statements.
                                                             (line  116)
* 物件; dictionary <6>:                  Mapping Types --- dict.
                                                             (line    6)
* 物件; dictionary <7>:                  字典物件.           (line    6)
* 物件; Ellipsis:                        The standard type hierarchy.
                                                             (line   41)
* 物件; file:                            Reading and Writing Files.
                                                             (line    6)
* 物件; file <1>:                        檔案（File）物件.   (line    6)
* 物件; floating point:                  The standard type hierarchy.
                                                             (line  107)
* 物件; floating point <1>:              Numeric Types --- int float complex.
                                                             (line    6)
* 物件; floating point <2>:              浮點數（Floating Point）物件.
                                                             (line    6)
* 物件; frame:                           The standard type hierarchy.
                                                             (line  708)
* 物件; frozenset:                       The standard type hierarchy.
                                                             (line  242)
* 物件; frozenset <1>:                   Set Objects.        (line    6)
* 物件; function:                        The standard type hierarchy.
                                                             (line  296)
* 物件; function <1>:                    The standard type hierarchy.
                                                             (line  484)
* 物件; function <2>:                    Calls.              (line  123)
* 物件; function <3>:                    Calls.              (line  132)
* 物件; function <4>:                    Function definitions.
                                                             (line    6)
* 物件; function <5>:                    函式（Function）物件.
                                                             (line    6)
* 物件; generator:                       The standard type hierarchy.
                                                             (line  686)
* 物件; generator <1>:                   Generator expressions.
                                                             (line    6)
* 物件; generator <2>:                   Yield expressions.  (line  107)
* 物件; immutable:                       The standard type hierarchy.
                                                             (line  146)
* 物件; immutable sequence:              The standard type hierarchy.
                                                             (line  146)
* 物件; instance:                        The standard type hierarchy.
                                                             (line  572)
* 物件; instance <1>:                    The standard type hierarchy.
                                                             (line  599)
* 物件; instance <2>:                    Calls.              (line  141)
* 物件; instancemethod:                  實體方法物件.       (line    6)
* 物件; integer:                         The standard type hierarchy.
                                                             (line   77)
* 物件; integer <1>:                     Numeric Types --- int float complex.
                                                             (line    6)
* 物件; integer <2>:                     整數物件.           (line    6)
* 物件; io.StringIO:                     Text Sequence Type --- str.
                                                             (line   35)
* 物件; list:                            The standard type hierarchy.
                                                             (line  200)
* 物件; list <1>:                        List displays.      (line    6)
* 物件; list <2>:                        Attribute references.
                                                             (line   10)
* 物件; list <3>:                        Subscriptions.      (line    6)
* 物件; list <4>:                        Slicings.           (line    6)
* 物件; list <5>:                        Assignment statements.
                                                             (line  108)
* 物件; list <6>:                        Mutable Sequence Types.
                                                             (line    6)
* 物件; list <7>:                        List（串列）<2>.    (line    6)
* 物件; list <8>:                        List（串列）物件.   (line    6)
* 物件; long integer:                    整數物件.           (line    6)
* 物件; mapping:                         The standard type hierarchy.
                                                             (line  249)
* 物件; mapping <1>:                     The standard type hierarchy.
                                                             (line  620)
* 物件; mapping <2>:                     Subscriptions.      (line    6)
* 物件; mapping <3>:                     Assignment statements.
                                                             (line  116)
* 物件; mapping <4>:                     Mapping Types --- dict.
                                                             (line    6)
* 物件; mapping <5>:                     Container Objects.  (line    6)
* 物件; memoryview:                      Binary Sequence Types --- bytes bytearray memoryview.
                                                             (line    6)
* 物件; memoryview <1>:                  Ellipsis Object.    (line   11)
* 物件; method:                          Instance Objects.   (line   31)
* 物件; method <1>:                      The standard type hierarchy.
                                                             (line  387)
* 物件; method <2>:                      The standard type hierarchy.
                                                             (line  497)
* 物件; method <3>:                      Calls.              (line  132)
* 物件; method <4>:                      Methods.            (line    6)
* 物件; method <5>:                      Method Objects<2>.  (line    6)
* 物件; module:                          The standard type hierarchy.
                                                             (line  520)
* 物件; module <1>:                      Attribute references.
                                                             (line   10)
* 物件; module <2>:                      模組物件模組.       (line    6)
* 物件; mutable:                         The standard type hierarchy.
                                                             (line  192)
* 物件; mutable <1>:                     Assignment statements.
                                                             (line    6)
* 物件; mutable <2>:                     Assignment statements.
                                                             (line  103)
* 物件; mutable sequence:                The standard type hierarchy.
                                                             (line  192)
* 物件; None:                            The standard type hierarchy.
                                                             (line   20)
* 物件; None <1>:                        Expression statements.
                                                             (line   17)
* 物件; None <2>:                        The None Object.    (line    6)
* 物件; NotImplemented:                  The standard type hierarchy.
                                                             (line   28)
* 物件; numeric:                         The standard type hierarchy.
                                                             (line   47)
* 物件; numeric <1>:                     The standard type hierarchy.
                                                             (line  620)
* 物件; numeric <2>:                     Numeric Types --- int float complex.
                                                             (line    6)
* 物件; numeric <3>:                     Numeric Objects.    (line    6)
* 物件; range:                           Ranges.             (line    6)
* 物件; sequence:                        The standard type hierarchy.
                                                             (line  127)
* 物件; sequence <1>:                    The standard type hierarchy.
                                                             (line  620)
* 物件; sequence <2>:                    Subscriptions.      (line    6)
* 物件; sequence <3>:                    Slicings.           (line    6)
* 物件; sequence <4>:                    Membership test operations.
                                                             (line   37)
* 物件; sequence <5>:                    Assignment statements.
                                                             (line  108)
* 物件; sequence <6>:                    The for statement.  (line    6)
* 物件; sequence <7>:                    Common Sequence Operations.
                                                             (line    6)
* 物件; sequence <8>:                    Sequence Objects.   (line    6)
* 物件; set:                             The standard type hierarchy.
                                                             (line  236)
* 物件; set <1>:                         Set displays.       (line    6)
* 物件; set <2>:                         Set Types --- set frozenset.
                                                             (line    6)
* 物件; set <3>:                         Set Objects.        (line    6)
* 物件; set type:                        The standard type hierarchy.
                                                             (line  219)
* 物件; slice:                           Emulating container types.
                                                             (line   64)
* 物件; socket:                          socket --- Low-level networking interface.
                                                             (line   17)
* 物件; string:                          Subscriptions.      (line    6)
* 物件; string <1>:                      Slicings.           (line    6)
* 物件; string <2>:                      Ranges.             (line  124)
* 物件; traceback:                       The standard type hierarchy.
                                                             (line  759)
* 物件; traceback <1>:                   The raise statement.
                                                             (line   21)
* 物件; traceback <2>:                   The try statement.  (line   69)
* 物件; traceback <3>:                   sys --- System-specific parameters and functions.
                                                             (line  365)
* 物件; traceback <4>:                   traceback --- Print or retrieve a stack traceback.
                                                             (line   16)
* 物件; tuple:                           The standard type hierarchy.
                                                             (line  172)
* 物件; tuple <1>:                       Subscriptions.      (line    6)
* 物件; tuple <2>:                       Slicings.           (line    6)
* 物件; tuple <3>:                       Expression lists.   (line   11)
* 物件; tuple <4>:                       Immutable Sequence Types.
                                                             (line    6)
* 物件; tuple <5>:                       Tuples.             (line    6)
* 物件; tuple <6>:                       元組（Tuple）物件.  (line    6)
* 物件; type:                            內建函式.           (line 1664)
* 物件; type <1>:                        Objects Types and Reference Counts.
                                                             (line    6)
* 物件; type <2>:                        Type Objects<2>.    (line    6)
* 物件; user-defined function:           The standard type hierarchy.
                                                             (line  296)
* 物件; user-defined function <1>:       Calls.              (line  123)
* 物件; user-defined function <2>:       Function definitions.
                                                             (line    6)
* 物件; user-defined method:             The standard type hierarchy.
                                                             (line  387)
* 環境變數; APPDATA:                     PEP 370 Per-user site-packages Directory.
                                                             (line   26)
* 環境變數; AUDIODEV:                    ossaudiodev --- Access to OSS-compatible audio devices.
                                                             (line   54)
* 環境變數; BROWSER:                     webbrowser --- Convenient Web-browser controller.
                                                             (line   20)
* 環境變數; BROWSER <1>:                 webbrowser --- Convenient Web-browser controller.
                                                             (line   95)
* 環境變數; CC:                          New Improved and Deprecated Modules<4>.
                                                             (line   58)
* 環境變數; CFLAGS:                      New Improved and Deprecated Modules<4>.
                                                             (line   58)
* 環境變數; CFLAGS <1>:                  Tweaking compiler/linker flags.
                                                             (line   66)
* 環境變數; CFLAGS <2>:                  Tweaking compiler/linker flags.
                                                             (line   67)
* 環境變數; COLS:                        curses<2>.          (line    7)
* 環境變數; COLS <1>:                    Functions<3>.       (line  526)
* 環境變數; COLUMNS:                     Functions<3>.       (line  550)
* 環境變數; COLUMNS <1>:                 Functions<3>.       (line  553)
* 環境變數; COMSPEC:                     Process Management. (line  664)
* 環境變數; COMSPEC <1>:                 Popen Constructor.  (line   90)
* 環境變數; CPP:                         New Improved and Deprecated Modules<4>.
                                                             (line   59)
* 環境變數; CPPFLAGS:                    New Improved and Deprecated Modules<4>.
                                                             (line   59)
* 環境變數; DISTUTILS_DEBUG:             Debugging the setup script.
                                                             (line   19)
* 環境變數; exec_prefix:                 Python-related paths and files.
                                                             (line    7)
* 環境變數; exec_prefix <1>:             Include Files.      (line   37)
* 環境變數; exec_prefix <2>:             Include Files.      (line   48)
* 環境變數; HOME:                        os path.            (line   15)
* 環境變數; HOME <1>:                    Changes in the Python API.
                                                             (line  116)
* 環境變數; HOME <2>:                    Windows<9>.         (line   13)
* 環境變數; HOME <3>:                    Windows<9>.         (line   16)
* 環境變數; HOME <4>:                    os path --- Common pathname manipulations.
                                                             (line  139)
* 環境變數; HOME <5>:                    os path --- Common pathname manipulations.
                                                             (line  155)
* 環境變數; HOME <6>:                    distutils util --- Miscellaneous other utility functions.
                                                             (line   77)
* 環境變數; HOME <7>:                    Location and names of config files.
                                                             (line   50)
* 環境變數; HOME <8>:                    Location and names of config files.
                                                             (line   67)
* 環境變數; HOMEDRIVE:                   os path --- Common pathname manipulations.
                                                             (line  146)
* 環境變數; HOMEDRIVE <1>:               Location and names of config files.
                                                             (line   68)
* 環境變數; HOMEPATH:                    os path --- Common pathname manipulations.
                                                             (line  146)
* 環境變數; HOMEPATH <1>:                Location and names of config files.
                                                             (line   68)
* 環境變數; http_proxy:                  urllib request --- Extensible library for opening URLs.
                                                             (line   85)
* 環境變數; http_proxy <1>:              Examples<21>.       (line   97)
* 環境變數; http_proxy <2>:              Basic Authentication.
                                                             (line   62)
* 環境變數; IDLESTARTUP:                 IDLE<27>.           (line  176)
* 環境變數; IDLESTARTUP <1>:             IDLE<31>.           (line    9)
* 環境變數; IDLESTARTUP <2>:             IDLE<37>.           (line    9)
* 環境變數; IDLESTARTUP <3>:             Startup and code execution.
                                                             (line    7)
* 環境變數; KDEDIR:                      webbrowser --- Convenient Web-browser controller.
                                                             (line  183)
* 環境變數; LANG:                        GNU gettext API.    (line   21)
* 環境變數; LANG <1>:                    Class-based API.    (line   26)
* 環境變數; LANG <2>:                    locale --- Internationalization services.
                                                             (line   49)
* 環境變數; LANG <3>:                    locale --- Internationalization services.
                                                             (line  310)
* 環境變數; LANG <4>:                    locale --- Internationalization services.
                                                             (line  314)
* 環境變數; 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<8>.
                                                             (line  153)
* 環境變數; LDFLAGS:                     New Improved and Deprecated Modules<4>.
                                                             (line   59)
* 環境變數; LINES:                       curses<2>.          (line    6)
* 環境變數; LINES <1>:                   Functions<3>.       (line  125)
* 環境變數; LINES <2>:                   Functions<3>.       (line  526)
* 環境變數; LINES <3>:                   Functions<3>.       (line  550)
* 環境變數; LINES <4>:                   Functions<3>.       (line  552)
* 環境變數; LNAME:                       getpass --- Portable password input.
                                                             (line   38)
* 環境變數; LOGNAME:                     Process Parameters. (line  221)
* 環境變數; LOGNAME <1>:                 getpass --- Portable password input.
                                                             (line   38)
* 環境變數; MIXERDEV:                    ossaudiodev --- Access to OSS-compatible audio devices.
                                                             (line   74)
* 環境變數; no_proxy:                    urllib request --- Extensible library for opening URLs.
                                                             (line  302)
* 環境變數; PAGER:                       pydoc --- Documentation generator and online help system.
                                                             (line   47)
* 環境變數; PATH:                        Changes in the Python API.
                                                             (line  143)
* 環境變數; 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>:                    Security<18>.       (line   16)
* 環境變數; PATH <5>:                    Security<18>.       (line   20)
* 環境變數; PATH <6>:                    The Module Search Path.
                                                             (line   16)
* 環境變數; PATH <7>:                    Executable Python Scripts.
                                                             (line   11)
* 環境變數; PATH <8>:                    Environment variables.
                                                             (line   27)
* 環境變數; PATH <9>:                    Miscellaneous.      (line   16)
* 環境變數; PATH <10>:                   Installation steps. (line   31)
* 環境變數; PATH <11>:                   Installation steps. (line   54)
* 環境變數; PATH <12>:                   安裝排除使用者介面. (line   56)
* 環境變數; PATH <13>:                   Excursus Setting environment variables.
                                                             (line   23)
* 環境變數; PATH <14>:                   Excursus Setting environment variables.
                                                             (line   35)
* 環境變數; PATH <15>:                   Finding the Python executable.
                                                             (line   14)
* 環境變數; PATH <16>:                   Finding the Python executable.
                                                             (line   21)
* 環境變數; PATH <17>:                   Finding the Python executable.
                                                             (line   22)
* 環境變數; PATH <18>:                   Python Launcher for Windows.
                                                             (line   13)
* 環境變數; PATH <19>:                   From the command-line.
                                                             (line    9)
* 環境變數; PATH <20>:                   From the command-line.
                                                             (line   38)
* 環境變數; PATH <21>:                   Shebang Lines.      (line   48)
* 環境變數; PATH <22>:                   Shebang Lines.      (line   50)
* 環境變數; PATH <23>:                   Process Management. (line   45)
* 環境變數; PATH <24>:                   Process Management. (line   86)
* 環境變數; PATH <25>:                   Process Management. (line   89)
* 環境變數; PATH <26>:                   Process Management. (line   92)
* 環境變數; PATH <27>:                   Process Management. (line  453)
* 環境變數; PATH <28>:                   Process Management. (line  539)
* 環境變數; PATH <29>:                   Process Management. (line  543)
* 環境變數; PATH <30>:                   Process Management. (line  545)
* 環境變數; PATH <31>:                   Miscellaneous System Information.
                                                             (line  118)
* 環境變數; PATH <32>:                   webbrowser --- Convenient Web-browser controller.
                                                             (line  213)
* 環境變數; PATH <33>:                   Installing your CGI script on a Unix system.
                                                             (line   29)
* 環境變數; PATH <34>:                   Common problems and solutions.
                                                             (line   23)
* 環境變數; PATH <35>:                   site --- Site-specific configuration hook.
                                                             (line   58)
* 環境變數; PATH <36>:                   嵌入式Python.       (line   31)
* 環境變數; PATH <37>:                   嵌入式Python.       (line   37)
* 環境變數; PATH <38>:                   我如何使Python script 執行在Unix ?.
                                                             (line   23)
* 環境變數; PATH <39>:                   我如何使Python script 執行在Unix ?.
                                                             (line   27)
* 環境變數; PATHEXT:                     Other Improvements<2>.
                                                             (line   30)
* 環境變數; PATHEXT <1>:                 Library<6>.         (line  117)
* 環境變數; PATHEXT <2>:                 安裝排除使用者介面. (line   57)
* 環境變數; PIP_USER:                    Windows<15>.        (line    7)
* 環境變數; PLAT:                        distutils util --- Miscellaneous other utility functions.
                                                             (line   79)
* 環境變數; POSIXLY_CORRECT:             getopt --- C-style parser for command line options.
                                                             (line   71)
* 環境變數; prefix:                      Python-related paths and files.
                                                             (line    7)
* 環境變數; prefix <1>:                  Include Files.      (line   37)
* 環境變數; prefix <2>:                  Include Files.      (line   40)
* 環境變數; prefix <3>:                  Include Files.      (line   47)
* 環境變數; PYTHON*:                     Other Improvements<2>.
                                                             (line    9)
* 環境變數; PYTHON* <1>:                 Interface options.  (line   80)
* 環境變數; PYTHON* <2>:                 Interface options.  (line  139)
* 環境變數; PYTHON* <3>:                 Miscellaneous options.
                                                             (line   42)
* 環境變數; PYTHON* <4>:                 Miscellaneous options.
                                                             (line   60)
* 環境變數; PYTHON* <5>:                 Global configuration variables.
                                                             (line   56)
* 環境變數; PYTHONASYNCIODEBUG:          Environment variables.
                                                             (line  238)
* 環境變數; PYTHONASYNCIODEBUG <1>:      Enabling debug mode.
                                                             (line   10)
* 環境變數; PYTHONASYNCIODEBUG <2>:      Debug Mode.         (line   11)
* 環境變數; PYTHONBREAKPOINT:            PEP 553 Built-in breakpoint.
                                                             (line   13)
* 環境變數; PYTHONBREAKPOINT <1>:        Environment variables.
                                                             (line   66)
* 環境變數; PYTHONBREAKPOINT <2>:        sys --- System-specific parameters and functions.
                                                             (line  202)
* 環境變數; PYTHONBREAKPOINT <3>:        sys --- System-specific parameters and functions.
                                                             (line  216)
* 環境變數; PYTHONBREAKPOINT <4>:        sys --- System-specific parameters and functions.
                                                             (line  220)
* 環境變數; PYTHONCASEOK:                PEP 235 Importing Modules on Case-Insensitive Platforms.
                                                             (line   17)
* 環境變數; PYTHONCASEOK <1>:            Environment variables.
                                                             (line  104)
* 環境變數; PYTHONCOERCECLOCALE:         PEP 538 Legacy C Locale Coercion.
                                                             (line   13)
* 環境變數; PYTHONCOERCECLOCALE <1>:     Environment variables.
                                                             (line  321)
* 環境變數; PYTHONCOERCECLOCALE <2>:     Environment variables.
                                                             (line  437)
* 環境變數; PYTHONCOERCECLOCALE <3>:     Python Configuration.
                                                             (line   15)
* 環境變數; PYTHONDEBUG:                 Miscellaneous options.
                                                             (line   38)
* 環境變數; PYTHONDEBUG <1>:             Environment variables.
                                                             (line   79)
* 環境變數; PYTHONDEBUG <2>:             Global configuration variables.
                                                             (line   28)
* 環境變數; PYTHONDEVMODE:               Development Runtime Mode -X dev.
                                                             (line    6)
* 環境變數; PYTHONDEVMODE <1>:           Environment variables.
                                                             (line  377)
* 環境變數; PYTHONDEVMODE <2>:           test support script_helper --- Utilities for the Python execution tests.
                                                             (line  103)
* 環境變數; PYTHONDOCS:                  pydoc --- Documentation generator and online help system.
                                                             (line   85)
* 環境變數; PYTHONDONTWRITEBYTECODE:     Interpreter Changes<2>.
                                                             (line   16)
* 環境變數; PYTHONDONTWRITEBYTECODE <1>: New and Improved Modules<2>.
                                                             (line  625)
* 環境變數; PYTHONDONTWRITEBYTECODE <2>: Miscellaneous options.
                                                             (line   19)
* 環境變數; PYTHONDONTWRITEBYTECODE <3>: Environment variables.
                                                             (line  109)
* 環境變數; PYTHONDONTWRITEBYTECODE <4>: sys --- System-specific parameters and functions.
                                                             (line  285)
* 環境變數; PYTHONDONTWRITEBYTECODE <5>: Global configuration variables.
                                                             (line   36)
* 環境變數; PYTHONDONTWRITEBYTECODE <6>: How do I create a pyc file?.
                                                             (line   21)
* 環境變數; PYTHONDUMPREFS:              Debug build uses the same ABI as release build.
                                                             (line   14)
* 環境變數; PYTHONDUMPREFS <1>:          Build<15>.          (line   54)
* 環境變數; PYTHONDUMPREFS <2>:          Debug-mode variables.
                                                             (line   14)
* 環境變數; PYTHONDUMPREFS <3>:          PyObject Slots.     (line   24)
* 環境變數; PYTHONEXECUTABLE:            Environment variables.
                                                             (line  182)
* 環境變數; PYTHONFAULTHANDLER:          faulthandler<3>.    (line   11)
* 環境變數; PYTHONFAULTHANDLER <1>:      Environment variables.
                                                             (line  209)
* 環境變數; PYTHONFAULTHANDLER <2>:      faulthandler --- Dump the Python traceback.
                                                             (line   14)
* 環境變數; PYTHONHASHSEED:              Builtin functions and types.
                                                             (line   17)
* 環境變數; PYTHONHASHSEED <1>:          Porting Python code.
                                                             (line    6)
* 環境變數; PYTHONHASHSEED <2>:          Core and Builtins<35>.
                                                             (line   30)
* 環境變數; PYTHONHASHSEED <3>:          Miscellaneous options.
                                                             (line   92)
* 環境變數; PYTHONHASHSEED <4>:          Miscellaneous options.
                                                             (line  108)
* 環境變數; PYTHONHASHSEED <5>:          Environment variables.
                                                             (line  124)
* 環境變數; PYTHONHASHSEED <6>:          Environment variables.
                                                             (line  129)
* 環境變數; PYTHONHASHSEED <7>:          Basic customization.
                                                             (line  298)
* 環境變數; PYTHONHASHSEED <8>:          Global configuration variables.
                                                             (line   48)
* 環境變數; PYTHONHASHSEED <9>:          Global configuration variables.
                                                             (line   51)
* 環境變數; PYTHONHOME:                  Summary -- Release highlights<2>.
                                                             (line  107)
* 環境變數; PYTHONHOME <1>:              Miscellaneous options.
                                                             (line   43)
* 環境變數; PYTHONHOME <2>:              Environment variables.
                                                             (line   11)
* 環境變數; PYTHONHOME <3>:              Environment variables.
                                                             (line   19)
* 環境變數; PYTHONHOME <4>:              Environment variables.
                                                             (line   21)
* 環境變數; PYTHONHOME <5>:              Environment variables.
                                                             (line   38)
* 環境變數; PYTHONHOME <6>:              Finding modules.    (line   50)
* 環境變數; PYTHONHOME <7>:              Finding modules.    (line   68)
* 環境變數; PYTHONHOME <8>:              Finding modules.    (line  102)
* 環境變數; PYTHONHOME <9>:              test support script_helper --- Utilities for the Python execution tests.
                                                             (line   24)
* 環境變數; PYTHONHOME <10>:             嵌入式Python.       (line   38)
* 環境變數; PYTHONHOME <11>:             嵌入式Python.       (line   44)
* 環境變數; PYTHONHOME <12>:             Global configuration variables.
                                                             (line   57)
* 環境變數; PYTHONHOME <13>:             Process-wide parameters.
                                                             (line  269)
* 環境變數; PYTHONHOME <14>:             Process-wide parameters.
                                                             (line  283)
* 環境變數; PYTHONHOME <15>:             PyConfig.           (line  197)
* 環境變數; PYTHONHOME <16>:             Modifying Python's Search Path.
                                                             (line   60)
* 環境變數; PYTHONHOME <17>:             Modifying Python's Search Path.
                                                             (line   62)
* 環境變數; PYTHONINSPECT:               Other Changes and Fixes<2>.
                                                             (line   13)
* 環境變數; PYTHONINSPECT <1>:           Miscellaneous options.
                                                             (line   53)
* 環境變數; PYTHONINSPECT <2>:           Environment variables.
                                                             (line   85)
* 環境變數; PYTHONINSPECT <3>:           Global configuration variables.
                                                             (line   68)
* 環境變數; PYTHONIOENCODING:            Other Improvements<2>.
                                                             (line   75)
* 環境變數; PYTHONIOENCODING <1>:        Interpreter Changes<2>.
                                                             (line   23)
* 環境變數; PYTHONIOENCODING <2>:        Environment variables.
                                                             (line  142)
* 環境變數; PYTHONIOENCODING <3>:        Environment variables.
                                                             (line  358)
* 環境變數; PYTHONIOENCODING <4>:        Environment variables.
                                                             (line  425)
* 環境變數; PYTHONIOENCODING <5>:        sys --- System-specific parameters and functions.
                                                             (line 1502)
* 環境變數; PYTHONIOENCODING <6>:        Process-wide parameters.
                                                             (line   14)
* 環境變數; PYTHONIOENCODING <7>:        Process-wide parameters.
                                                             (line   18)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING: PEP 529 Change Windows filesystem encoding to UTF-8.
                                                             (line   18)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <1>: Environment variables.
                                                             (line  294)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <2>: sys --- System-specific parameters and functions.
                                                             (line 1454)
* 環境變數; PYTHONLEGACYWINDOWSFSENCODING <3>: Global configuration variables.
                                                             (line   90)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO:    PEP 528 Change Windows console encoding to UTF-8.
                                                             (line   12)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO <1>: Environment variables.
                                                             (line  156)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO <2>: Environment variables.
                                                             (line  308)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO <3>: sys --- System-specific parameters and functions.
                                                             (line 1506)
* 環境變數; PYTHONLEGACYWINDOWSSTDIO <4>: Global configuration variables.
                                                             (line  102)
* 環境變數; PYTHONMALLOC:                PYTHONMALLOC environment variable.
                                                             (line    6)
* 環境變數; PYTHONMALLOC <1>:            Changes in the C API<3>.
                                                             (line    9)
* 環境變數; PYTHONMALLOC <2>:            Core and Builtins<55>.
                                                             (line   91)
* 環境變數; PYTHONMALLOC <3>:            Environment variables.
                                                             (line  245)
* 環境變數; PYTHONMALLOC <4>:            Environment variables.
                                                             (line  286)
* 環境變數; PYTHONMALLOC <5>:            總覽<2>.            (line   75)
* 環境變數; PYTHONMALLOC <6>:            Default Memory Allocators.
                                                             (line   26)
* 環境變數; PYTHONMALLOC <7>:            Customize Memory Allocators.
                                                             (line  129)
* 環境變數; PYTHONMALLOCSTATS:           Core and Builtins<55>.
                                                             (line   97)
* 環境變數; PYTHONMALLOCSTATS <1>:       Environment variables.
                                                             (line  280)
* 環境變數; PYTHONMALLOCSTATS <2>:       總覽<2>.            (line   78)
* 環境變數; PYTHONNOUSERSITE:            PEP 370 Per-user site-packages Directory.
                                                             (line   30)
* 環境變數; PYTHONNOUSERSITE <1>:        Environment variables.
                                                             (line  160)
* 環境變數; PYTHONNOUSERSITE <2>:        Module contents<3>. (line   15)
* 環境變數; PYTHONNOUSERSITE <3>:        Global configuration variables.
                                                             (line  124)
* 環境變數; PYTHONOPTIMIZE:              Miscellaneous options.
                                                             (line   71)
* 環境變數; PYTHONOPTIMIZE <1>:          Environment variables.
                                                             (line   60)
* 環境變數; PYTHONOPTIMIZE <2>:          Global configuration variables.
                                                             (line  129)
* 環境變數; PYTHONPATH:                  Changes in 'python' Command Behavior<2>.
                                                             (line    8)
* 環境變數; PYTHONPATH <1>:              Changes in 'python' Command Behavior<2>.
                                                             (line    9)
* 環境變數; PYTHONPATH <2>:              The Module Search Path.
                                                             (line   15)
* 環境變數; PYTHONPATH <3>:              Standard Modules.   (line   34)
* 環境變數; PYTHONPATH <4>:              Standard Modules.   (line   35)
* 環境變數; PYTHONPATH <5>:              Miscellaneous options.
                                                             (line   42)
* 環境變數; PYTHONPATH <6>:              Environment variables.
                                                             (line   24)
* 環境變數; PYTHONPATH <7>:              Environment variables.
                                                             (line   32)
* 環境變數; PYTHONPATH <8>:              Environment variables.
                                                             (line   39)
* 環境變數; PYTHONPATH <9>:              Environment variables.
                                                             (line   42)
* 環境變數; PYTHONPATH <10>:             Excursus Setting environment variables.
                                                             (line   38)
* 環境變數; PYTHONPATH <11>:             Finding modules.    (line   36)
* 環境變數; PYTHONPATH <12>:             Finding modules.    (line   59)
* 環境變數; PYTHONPATH <13>:             Finding modules.    (line  102)
* 環境變數; PYTHONPATH <14>:             設定.               (line    6)
* 環境變數; PYTHONPATH <15>:             Installing your CGI script on a Unix system.
                                                             (line   29)
* 環境變數; PYTHONPATH <16>:             test support script_helper --- Utilities for the Python execution tests.
                                                             (line   25)
* 環境變數; PYTHONPATH <17>:             sys --- System-specific parameters and functions.
                                                             (line 1063)
* 環境變數; PYTHONPATH <18>:             sys --- System-specific parameters and functions.
                                                             (line 1073)
* 環境變數; PYTHONPATH <19>:             Building C and C++ Extensions.
                                                             (line    9)
* 環境變數; PYTHONPATH <20>:             嵌入式Python.       (line   39)
* 環境變數; PYTHONPATH <21>:             嵌入式Python.       (line   44)
* 環境變數; PYTHONPATH <22>:             Global configuration variables.
                                                             (line   56)
* 環境變數; PYTHONPATH <23>:             PyConfig.           (line  252)
* 環境變數; PYTHONPATH <24>:             Modifying Python's Search Path.
                                                             (line   67)
* 環境變數; PYTHONPATH <25>:             Modifying Python's Search Path.
                                                             (line   68)
* 環境變數; PYTHONPROFILEIMPORTTIME:     Other Language Changes<2>.
                                                             (line   47)
* 環境變數; PYTHONPROFILEIMPORTTIME <1>: Core and Builtins<37>.
                                                             (line   67)
* 環境變數; PYTHONPROFILEIMPORTTIME <2>: Miscellaneous options.
                                                             (line  221)
* 環境變數; PYTHONPROFILEIMPORTTIME <3>: Environment variables.
                                                             (line  230)
* 環境變數; PYTHONPYCACHEPREFIX:         Parallel filesystem cache for compiled bytecode files.
                                                             (line    6)
* 環境變數; PYTHONPYCACHEPREFIX <1>:     Core and Builtins<28>.
                                                             (line  402)
* 環境變數; PYTHONPYCACHEPREFIX <2>:     Miscellaneous options.
                                                             (line  255)
* 環境變數; PYTHONPYCACHEPREFIX <3>:     Environment variables.
                                                             (line  115)
* 環境變數; PYTHONPYCACHEPREFIX <4>:     sys --- System-specific parameters and functions.
                                                             (line  303)
* 環境變數; PYTHONSHOWALLOCCOUNT:        Two new environment variables for debug mode.
                                                             (line   11)
* 環境變數; PYTHONSHOWREFCOUNT:          Two new environment variables for debug mode.
                                                             (line    7)
* 環境變數; PYTHONSTARTUP:               sys<6>.             (line   17)
* 環境變數; PYTHONSTARTUP <1>:           sys<6>.             (line   21)
* 環境變數; PYTHONSTARTUP <2>:           IDLE<27>.           (line  176)
* 環境變數; PYTHONSTARTUP <3>:           IDLE<31>.           (line    9)
* 環境變數; PYTHONSTARTUP <4>:           IDLE<37>.           (line    9)
* 環境變數; PYTHONSTARTUP <5>:           The Interactive Startup File.
                                                             (line    8)
* 環境變數; PYTHONSTARTUP <6>:           Miscellaneous options.
                                                             (line   50)
* 環境變數; PYTHONSTARTUP <7>:           Environment variables.
                                                             (line   46)
* 環境變數; PYTHONSTARTUP <8>:           Example.            (line   10)
* 環境變數; PYTHONSTARTUP <9>:           Startup and code execution.
                                                             (line    7)
* 環境變數; PYTHONSTARTUP <10>:          sys --- System-specific parameters and functions.
                                                             (line  959)
* 環境變數; PYTHONSTARTUP <11>:          Readline configuration.
                                                             (line   12)
* 環境變數; PYTHONTHREADDEBUG:           Debug-mode variables.
                                                             (line    8)
* 環境變數; PYTHONTRACEMALLOC:           Environment variables.
                                                             (line  219)
* 環境變數; PYTHONTRACEMALLOC <1>:       tracemalloc --- Trace memory allocations.
                                                             (line   25)
* 環境變數; PYTHONTRACEMALLOC <2>:       tracemalloc --- Trace memory allocations.
                                                             (line   32)
* 環境變數; PYTHONTRACEMALLOC <3>:       Functions<9>.       (line   68)
* 環境變數; PYTHONUNBUFFERED:            Miscellaneous options.
                                                             (line  138)
* 環境變數; PYTHONUNBUFFERED <1>:        Environment variables.
                                                             (line   93)
* 環境變數; PYTHONUNBUFFERED <2>:        Global configuration variables.
                                                             (line  145)
* 環境變數; PYTHONUSERBASE:              PEP 370 Per-user site-packages Directory.
                                                             (line   23)
* 環境變數; PYTHONUSERBASE <1>:          Environment variables.
                                                             (line  170)
* 環境變數; PYTHONUSERBASE <2>:          Module contents<3>. (line   39)
* 環境變數; PYTHONUSERBASE <3>:          Module contents<3>. (line   65)
* 環境變數; PYTHONUSERSITE:              test support script_helper --- Utilities for the Python execution tests.
                                                             (line   25)
* 環境變數; PYTHONUTF8:                  PEP 540 Forced UTF-8 Runtime Mode.
                                                             (line    6)
* 環境變數; PYTHONUTF8 <1>:              Miscellaneous options.
                                                             (line  250)
* 環境變數; PYTHONUTF8 <2>:              Environment variables.
                                                             (line  368)
* 環境變數; PYTHONUTF8 <3>:              Environment variables.
                                                             (line  385)
* 環境變數; PYTHONUTF8 <4>:              UTF-8 mode.         (line   17)
* 環境變數; PYTHONUTF8 <5>:              sys --- System-specific parameters and functions.
                                                             (line 1504)
* 環境變數; PYTHONUTF8 <6>:              Python Configuration.
                                                             (line   14)
* 環境變數; PYTHONVERBOSE:               Miscellaneous options.
                                                             (line  149)
* 環境變數; PYTHONVERBOSE <1>:           Environment variables.
                                                             (line   98)
* 環境變數; PYTHONVERBOSE <2>:           Global configuration variables.
                                                             (line  156)
* 環境變數; PYTHONWARNINGS:              warnings.           (line   21)
* 環境變數; PYTHONWARNINGS <1>:          Other Language Changes<7>.
                                                             (line  158)
* 環境變數; PYTHONWARNINGS <2>:          Changes to the Handling of Deprecation Warnings.
                                                             (line   25)
* 環境變數; PYTHONWARNINGS <3>:          Interpreter Changes.
                                                             (line    6)
* 環境變數; PYTHONWARNINGS <4>:          Miscellaneous options.
                                                             (line  167)
* 環境變數; PYTHONWARNINGS <5>:          Environment variables.
                                                             (line  188)
* 環境變數; PYTHONWARNINGS <6>:          Describing Warning Filters.
                                                             (line    7)
* 環境變數; PYTHONWARNINGS <7>:          Describing Warning Filters.
                                                             (line   21)
* 環境變數; PYTHONWARNINGS <8>:          Default Warning Filter.
                                                             (line    7)
* 環境變數; PYTHON_DOM:                  Module Contents<4>. (line   23)
* 環境變數; PY_PYTHON:                   Customizing default Python versions.
                                                             (line   18)
* 環境變數; SOURCE_DATE_EPOCH:           py_compile<2>.      (line    7)
* 環境變數; SOURCE_DATE_EPOCH <1>:       Library<28>.        (line  453)
* 環境變數; SOURCE_DATE_EPOCH <2>:       Build<23>.          (line   15)
* 環境變數; SOURCE_DATE_EPOCH <3>:       py_compile --- Compile Python source files.
                                                             (line   65)
* 環境變數; SOURCE_DATE_EPOCH <4>:       py_compile --- Compile Python source files.
                                                             (line   81)
* 環境變數; SOURCE_DATE_EPOCH <5>:       py_compile --- Compile Python source files.
                                                             (line   85)
* 環境變數; SOURCE_DATE_EPOCH <6>:       Command-line use.   (line   84)
* 環境變數; SSLKEYLOGFILE:               Context creation.   (line   33)
* 環境變數; SSLKEYLOGFILE <1>:           Context creation.   (line   66)
* 環境變數; SSL_CERT_FILE:               LibreSSL support.   (line   15)
* 環境變數; SSL_CERT_PATH:               LibreSSL support.   (line   15)
* 環境變數; SystemRoot:                  Popen Constructor.  (line  233)
* 環境變數; TCL_LIBRARY:                 How do I freeze Tkinter applications?.
                                                             (line   11)
* 環境變數; TEMP:                        tempfile --- Generate temporary files and directories.
                                                             (line  236)
* 環境變數; TERM:                        Functions<3>.       (line  440)
* 環境變數; TERM <1>:                    Functions<3>.       (line  467)
* 環境變數; TK_LIBRARY:                  How do I freeze Tkinter applications?.
                                                             (line   11)
* 環境變數; TMP:                         tempfile --- Generate temporary files and directories.
                                                             (line  238)
* 環境變數; TMPDIR:                      tempfile --- Generate temporary files and directories.
                                                             (line  234)
* 環境變數; TZ:                          Functions<2>.       (line  508)
* 環境變數; TZ <1>:                      Functions<2>.       (line  509)
* 環境變數; TZ <2>:                      Functions<2>.       (line  517)
* 環境變數; TZ <3>:                      Functions<2>.       (line  522)
* 環境變數; TZ <4>:                      Functions<2>.       (line  524)
* 環境變數; TZ <5>:                      Functions<2>.       (line  584)
* 環境變數; USER:                        getpass --- Portable password input.
                                                             (line   38)
* 環境變數; USERNAME:                    Process Parameters. (line  221)
* 環境變數; USERNAME <1>:                getpass --- Portable password input.
                                                             (line   39)
* 環境變數; USERPROFILE:                 os path.            (line   14)
* 環境變數; USERPROFILE <1>:             Changes in the Python API.
                                                             (line  115)
* 環境變數; USERPROFILE <2>:             Windows<9>.         (line   13)
* 環境變數; USERPROFILE <3>:             os path --- Common pathname manipulations.
                                                             (line  145)
* 環境變數; USERPROFILE <4>:             Location and names of config files.
                                                             (line   67)
* 環境變數; USER_BASE:                   New and Improved Modules.
                                                             (line  469)
* 環境變數; VIRTUAL_ENV:                 Creating virtual environments.
                                                             (line  128)
* 運算子; !=:                            Comparisons.        (line    6)
* 運算子; != <1>:                        Comparisons<2>.     (line    6)
* 運算子; % (percent):                   Binary arithmetic operations.
                                                             (line   35)
* 運算子; % (percent) <1>:               Numeric Types --- int float complex.
                                                             (line   27)
* 運算子; & (ampersand):                 Binary bitwise operations.
                                                             (line   12)
* 運算子; & (ampersand) <1>:             Bitwise Operations on Integer Types.
                                                             (line    6)
* 運算子; * (asterisk):                  Binary arithmetic operations.
                                                             (line   16)
* 運算子; * (asterisk) <1>:              Numeric Types --- int float complex.
                                                             (line   27)
* 運算子; **:                            The power operator. (line    6)
* 運算子; ** <1>:                        Numeric Types --- int float complex.
                                                             (line   27)
* 運算子; / (slash):                     Binary arithmetic operations.
                                                             (line   28)
* 運算子; / (slash) <1>:                 Numeric Types --- int float complex.
                                                             (line   27)
* 運算子; //:                            Binary arithmetic operations.
                                                             (line   28)
* 運算子; // <1>:                        Numeric Types --- int float complex.
                                                             (line   27)
* 運算子; < (less):                      Comparisons.        (line    6)
* 運算子; < (less) <1>:                  Comparisons<2>.     (line    6)
* 運算子; <<:                            Shifting operations.
                                                             (line    6)
* 運算子; << <1>:                        Bitwise Operations on Integer Types.
                                                             (line    6)
* 運算子; <=:                            Comparisons.        (line    6)
* 運算子; <= <1>:                        Comparisons<2>.     (line    6)
* 運算子; ==:                            Comparisons.        (line    6)
* 運算子; == <1>:                        Comparisons<2>.     (line    6)
* 運算子; > (greater):                   Comparisons.        (line    6)
* 運算子; > (greater) <1>:               Comparisons<2>.     (line    6)
* 運算子; >=:                            Comparisons.        (line    6)
* 運算子; >= <1>:                        Comparisons<2>.     (line    6)
* 運算子; >>:                            Shifting operations.
                                                             (line    6)
* 運算子; >> <1>:                        Bitwise Operations on Integer Types.
                                                             (line    6)
* 運算子; @ (at):                        Binary arithmetic operations.
                                                             (line   23)
* 運算子; and:                           Boolean operations. (line   21)
* 運算子; and <1>:                       Truth Value Testing.
                                                             (line   23)
* 運算子; and <2>:                       Boolean Operations --- and or not.
                                                             (line   22)
* 運算子; in:                            Membership test operations.
                                                             (line   37)
* 運算子; in <1>:                        Comparisons<2>.     (line   64)
* 運算子; in <2>:                        Common Sequence Operations.
                                                             (line   21)
* 運算子; is:                            Membership test operations.
                                                             (line   40)
* 運算子; is <1>:                        Comparisons<2>.     (line    6)
* 運算子; is not:                        Membership test operations.
                                                             (line   40)
* 運算子; is not <1>:                    Comparisons<2>.     (line    6)
* 運算子; not:                           Boolean operations. (line   18)
* 運算子; not <1>:                       Boolean Operations --- and or not.
                                                             (line   22)
* 運算子; not in:                        Membership test operations.
                                                             (line   37)
* 運算子; not in <1>:                    Comparisons<2>.     (line   64)
* 運算子; not in <2>:                    Common Sequence Operations.
                                                             (line   21)
* 運算子; or:                            Boolean operations. (line   25)
* 運算子; or <1>:                        Truth Value Testing.
                                                             (line   23)
* 運算子; or <2>:                        Boolean Operations --- and or not.
                                                             (line   22)
* 運算子; ^ (caret):                     Binary bitwise operations.
                                                             (line   15)
* 運算子; ^ (caret) <1>:                 Bitwise Operations on Integer Types.
                                                             (line    6)
* 運算子; | (vertical bar):              Binary bitwise operations.
                                                             (line   18)
* 運算子; | (vertical bar) <1>:          Bitwise Operations on Integer Types.
                                                             (line    6)
* 運算子; ~ (tilde):                     Unary arithmetic and bitwise operations.
                                                             (line   15)
* 運算子; ~ (tilde) <1>:                 Bitwise Operations on Integer Types.
                                                             (line    6)
* 關鍵字; as:                            The import statement.
                                                             (line    6)
* 關鍵字; as <1>:                        The try statement.  (line    6)
* 關鍵字; as <2>:                        The with statement. (line    6)
* 關鍵字; async:                         Coroutine function definition.
                                                             (line    9)
* 關鍵字; await:                         Calls.              (line  149)
* 關鍵字; await <1>:                     Coroutine function definition.
                                                             (line    9)
* 關鍵字; elif:                          The if statement.   (line    6)
* 關鍵字; else:                          The break statement.
                                                             (line   12)
* 關鍵字; else <1>:                      The if statement.   (line    6)
* 關鍵字; else <2>:                      The while statement.
                                                             (line    6)
* 關鍵字; else <3>:                      The for statement.  (line    6)
* 關鍵字; else <4>:                      The try statement.  (line    6)
* 關鍵字; else <5>:                      The try statement.  (line   79)
* 關鍵字; except:                        The try statement.  (line    6)
* 關鍵字; finally:                       The return statement.
                                                             (line   17)
* 關鍵字; finally <1>:                   The break statement.
                                                             (line   18)
* 關鍵字; finally <2>:                   The continue statement.
                                                             (line    6)
* 關鍵字; finally <3>:                   The try statement.  (line    6)
* 關鍵字; finally <4>:                   The try statement.  (line   85)
* 關鍵字; from:                          Yield expressions.  (line    6)
* 關鍵字; from <1>:                      The import statement.
                                                             (line    6)
* 關鍵字; in:                            The for statement.  (line    6)
* 關鍵字; yield:                         Yield expressions.  (line    6)
* 陳述式; assert:                        The assert statement.
                                                             (line    6)
* 陳述式; assert <1>:                    Concrete exceptions.
                                                             (line   10)
* 陳述式; async def:                     Coroutines<2>.      (line    8)
* 陳述式; async for:                     Coroutine function definition.
                                                             (line   26)
* 陳述式; async with:                    The async for statement.
                                                             (line   43)
* 陳述式; break:                         The break statement.
                                                             (line    6)
* 陳述式; break <1>:                     The while statement.
                                                             (line   17)
* 陳述式; break <2>:                     The for statement.  (line   22)
* 陳述式; break <3>:                     The try statement.  (line   79)
* 陳述式; break <4>:                     The try statement.  (line  108)
* 陳述式; class:                         Class definitions.  (line    6)
* 陳述式; continue:                      The continue statement.
                                                             (line    6)
* 陳述式; continue <1>:                  The while statement.
                                                             (line   17)
* 陳述式; continue <2>:                  The for statement.  (line   22)
* 陳述式; continue <3>:                  The try statement.  (line   79)
* 陳述式; continue <4>:                  The try statement.  (line  108)
* 陳述式; def:                           Function definitions.
                                                             (line    6)
* 陳述式; del:                           Basic customization.
                                                             (line   56)
* 陳述式; del <1>:                       The del statement<2>.
                                                             (line    6)
* 陳述式; del <2>:                       Mutable Sequence Types.
                                                             (line   16)
* 陳述式; del <3>:                       Mapping Types --- dict.
                                                             (line    6)
* 陳述式; except:                        內建的例外.         (line    6)
* 陳述式; for:                           for Statements.     (line    6)
* 陳述式; for <1>:                       The break statement.
                                                             (line    6)
* 陳述式; for <2>:                       The continue statement.
                                                             (line    6)
* 陳述式; for <3>:                       The for statement.  (line    6)
* 陳述式; global:                        The del statement<2>.
                                                             (line   15)
* 陳述式; global <1>:                    The global statement.
                                                             (line    6)
* 陳述式; if:                            The if statement.   (line    6)
* 陳述式; if <1>:                        Truth Value Testing.
                                                             (line    6)
* 陳述式; import:                        The standard type hierarchy.
                                                             (line  520)
* 陳述式; import <1>:                    The import statement.
                                                             (line    6)
* 陳述式; import <2>:                    內建函式.           (line 1773)
* 陳述式; import <3>:                    site --- Site-specific configuration hook.
                                                             (line   44)
* 陳述式; import <4>:                    imp --- Access the import internals.
                                                             (line   11)
* 陳述式; nonlocal:                      The nonlocal statement.
                                                             (line    6)
* 陳述式; pass:                          The pass statement. (line    6)
* 陳述式; raise:                         The raise statement.
                                                             (line    6)
* 陳述式; raise <1>:                     內建的例外.         (line   14)
* 陳述式; return:                        The return statement.
                                                             (line    6)
* 陳述式; return <1>:                    The try statement.  (line   79)
* 陳述式; return <2>:                    The try statement.  (line  108)
* 陳述式; try:                           The standard type hierarchy.
                                                             (line  782)
* 陳述式; try <1>:                       The try statement.  (line    6)
* 陳述式; try <2>:                       內建的例外.         (line    6)
* 陳述式; while:                         The break statement.
                                                             (line    6)
* 陳述式; while <1>:                     The continue statement.
                                                             (line    6)
* 陳述式; while <2>:                     The while statement.
                                                             (line    6)
* 陳述式; while <3>:                     Truth Value Testing.
                                                             (line    6)
* 陳述式; with:                          With Statement Context Managers.
                                                             (line   14)
* 陳述式; with <1>:                      The with statement. (line    6)
* 陳述式; yield:                         The yield statement.
                                                             (line    6)

                                                             
                                                             



Tag Table:
Node: Top340
Ref: contents doc543
Ref: 146543
Node: Python 有什麼新功能？195010
Ref: whatsnew/index doc195112
Ref: 147195112
Ref: whatsnew/index python-documentation-contents195112
Ref: 148195112
Ref: whatsnew/index what-s-new-in-python195112
Ref: 149195112
Ref: whatsnew/index whatsnew-index195112
Ref: 14a195112
Node: What's New In Python 3 8196447
Ref: whatsnew/3 8 doc196569
Ref: 14b196569
Ref: whatsnew/3 8 what-s-new-in-python-3-8196569
Ref: 14c196569
Node: Summary -- Release highlights197599
Ref: whatsnew/3 8 summary-release-highlights197710
Ref: 14e197710
Node: New Features197783
Ref: whatsnew/3 8 new-features197925
Ref: 14f197925
Node: Assignment expressions198531
Ref: whatsnew/3 8 assignment-expressions198637
Ref: 150198637
Ref: Assignment expressions-Footnote-1200139
Ref: Assignment expressions-Footnote-2200236
Ref: Assignment expressions-Footnote-3200285
Node: Positional-only parameters200328
Ref: whatsnew/3 8 positional-only-parameters200496
Ref: 152200496
Ref: Positional-only parameters-Footnote-1203178
Ref: Positional-only parameters-Footnote-2203230
Ref: Positional-only parameters-Footnote-3203279
Node: Parallel filesystem cache for compiled bytecode files203322
Ref: whatsnew/3 8 parallel-filesystem-cache-for-compiled-bytecode-files203514
Ref: 154203514
Ref: Parallel filesystem cache for compiled bytecode files-Footnote-1204156
Node: Debug build uses the same ABI as release build204199
Ref: whatsnew/3 8 debug-build-uses-the-same-abi-as-release-build204431
Ref: 159204431
Ref: Debug build uses the same ABI as release build-Footnote-1206766
Ref: Debug build uses the same ABI as release build-Footnote-2206809
Ref: Debug build uses the same ABI as release build-Footnote-3206852
Ref: Debug build uses the same ABI as release build-Footnote-4206895
Node: f-strings support = for self-documenting expressions and debugging206938
Ref: whatsnew/3 8 f-strings-support-for-self-documenting-expressions-and-debugging207151
Ref: 15b207151
Ref: f-strings support = for self-documenting expressions and debugging-Footnote-1208240
Node: PEP 578 Python Runtime Audit Hooks208283
Ref: whatsnew/3 8 pep-578-python-runtime-audit-hooks208493
Ref: 15e208493
Ref: PEP 578 Python Runtime Audit Hooks-Footnote-1208976
Node: PEP 587 Python Initialization Configuration209025
Ref: whatsnew/3 8 pep-587-python-initialization-configuration209215
Ref: 15f209215
Ref: PEP 587 Python Initialization Configuration-Footnote-1211202
Ref: PEP 587 Python Initialization Configuration-Footnote-2211251
Ref: PEP 587 Python Initialization Configuration-Footnote-3211300
Node: Vectorcall a fast calling protocol for CPython211343
Ref: whatsnew/3 8 vectorcall-a-fast-calling-protocol-for-cpython211546
Ref: 17f211546
Ref: Vectorcall a fast calling protocol for CPython-Footnote-1212102
Ref: Vectorcall a fast calling protocol for CPython-Footnote-2212151
Node: Pickle protocol 5 with out-of-band data buffers212194
Ref: whatsnew/3 8 pickle-protocol-5-with-out-of-band-data-buffers212345
Ref: 180212345
Ref: Pickle protocol 5 with out-of-band data buffers-Footnote-1213097
Ref: Pickle protocol 5 with out-of-band data buffers-Footnote-2213146
Ref: Pickle protocol 5 with out-of-band data buffers-Footnote-3213195
Node: Other Language Changes213238
Ref: whatsnew/3 8 other-language-changes213362
Ref: 181213362
Ref: Other Language Changes-Footnote-1220739
Ref: Other Language Changes-Footnote-2220782
Ref: Other Language Changes-Footnote-3220825
Ref: Other Language Changes-Footnote-4220868
Ref: Other Language Changes-Footnote-5220911
Ref: Other Language Changes-Footnote-6220954
Ref: Other Language Changes-Footnote-7220997
Ref: Other Language Changes-Footnote-8221040
Ref: Other Language Changes-Footnote-9221083
Ref: Other Language Changes-Footnote-10221126
Ref: Other Language Changes-Footnote-11221170
Ref: Other Language Changes-Footnote-12221216
Ref: Other Language Changes-Footnote-13221260
Ref: Other Language Changes-Footnote-14221330
Ref: Other Language Changes-Footnote-15221390
Ref: Other Language Changes-Footnote-16221434
Ref: Other Language Changes-Footnote-17221478
Node: New Modules221522
Ref: whatsnew/3 8 new-modules221650
Ref: 19e221650
Ref: New Modules-Footnote-1222728
Node: Improved Modules222771
Ref: whatsnew/3 8 improved-modules222890
Ref: 19f222890
Node: ast223514
Ref: whatsnew/3 8 ast223586
Ref: 1a0223586
Ref: ast-Footnote-1224614
Ref: ast-Footnote-2224657
Ref: ast-Footnote-3224706
Ref: ast-Footnote-4224755
Ref: ast-Footnote-5224804
Node: asyncio224847
Ref: whatsnew/3 8 asyncio224936
Ref: 1a5224936
Ref: asyncio-Footnote-1228087
Ref: asyncio-Footnote-2228130
Ref: asyncio-Footnote-3228173
Ref: asyncio-Footnote-4228216
Ref: asyncio-Footnote-5228259
Ref: asyncio-Footnote-6228302
Ref: asyncio-Footnote-7228345
Ref: asyncio-Footnote-8228388
Ref: asyncio-Footnote-9228431
Ref: asyncio-Footnote-10228484
Node: builtins228528
Ref: whatsnew/3 8 builtins228625
Ref: 1b4228625
Ref: builtins-Footnote-1229124
Node: collections229167
Ref: whatsnew/3 8 collections229265
Ref: 1b6229265
Ref: collections-Footnote-1229787
Node: cProfile229830
Ref: whatsnew/3 8 cprofile229923
Ref: 1bb229923
Ref: cProfile-Footnote-1230273
Node: csv230316
Ref: whatsnew/3 8 csv230404
Ref: 1bd230404
Ref: csv-Footnote-1230721
Node: curses230764
Ref: whatsnew/3 8 curses230850
Ref: 1bf230850
Ref: curses-Footnote-1231094
Node: ctypes231137
Ref: whatsnew/3 8 ctypes231228
Ref: 1c1231228
Ref: ctypes-Footnote-1231717
Node: datetime231760
Ref: whatsnew/3 8 datetime231854
Ref: 1c4231854
Ref: datetime-Footnote-1232282
Node: functools232325
Ref: whatsnew/3 8 functools232415
Ref: 1c7232415
Ref: functools-Footnote-1233957
Ref: functools-Footnote-2234000
Ref: functools-Footnote-3234043
Node: gc234086
Ref: whatsnew/3 8 gc234175
Ref: 1cd234175
Ref: gc-Footnote-1234408
Node: gettext234451
Ref: whatsnew/3 8 gettext234535
Ref: 1cf234535
Ref: gettext-Footnote-1234736
Node: gzip234778
Ref: whatsnew/3 8 gzip234876
Ref: 1d1234876
Ref: gzip-Footnote-1235293
Ref: gzip-Footnote-2235336
Node: IDLE and idlelib235378
Ref: whatsnew/3 8 idle-and-idlelib235476
Ref: 1d5235476
Ref: IDLE and idlelib-Footnote-1237441
Ref: IDLE and idlelib-Footnote-2237486
Ref: IDLE and idlelib-Footnote-3237528
Ref: IDLE and idlelib-Footnote-4237571
Ref: IDLE and idlelib-Footnote-5237614
Ref: IDLE and idlelib-Footnote-6237657
Ref: IDLE and idlelib-Footnote-7237699
Ref: IDLE and idlelib-Footnote-8237742
Node: inspect237785
Ref: whatsnew/3 8 inspect237881
Ref: 1d6237881
Ref: inspect-Footnote-1238647
Node: io238690
Ref: whatsnew/3 8 io238779
Ref: 1db238779
Ref: io-Footnote-1239115
Node: itertools239158
Ref: whatsnew/3 8 itertools239249
Ref: 1dd239249
Ref: itertools-Footnote-1239627
Node: json tool239670
Ref: whatsnew/3 8 json-tool239766
Ref: 1df239766
Ref: json tool-Footnote-1239973
Node: logging240016
Ref: whatsnew/3 8 logging240107
Ref: 1e0240107
Ref: logging-Footnote-1240823
Node: math240866
Ref: whatsnew/3 8 math240952
Ref: 1e2240952
Ref: math-Footnote-1242701
Ref: math-Footnote-2242744
Ref: math-Footnote-3242787
Ref: math-Footnote-4242830
Ref: math-Footnote-5242873
Ref: math-Footnote-6242916
Ref: math-Footnote-7242959
Ref: math-Footnote-8243002
Node: mmap243045
Ref: whatsnew/3 8 mmap243139
Ref: 1ec243139
Ref: mmap-Footnote-1243369
Node: multiprocessing243412
Ref: whatsnew/3 8 multiprocessing243504
Ref: 1ef243504
Ref: multiprocessing-Footnote-1243808
Ref: multiprocessing-Footnote-2243851
Node: os243894
Ref: whatsnew/3 8 os243989
Ref: 1f0243989
Ref: os-Footnote-1245493
Ref: os-Footnote-2245536
Ref: os-Footnote-3245579
Node: os path245622
Ref: whatsnew/3 8 os-path245709
Ref: 1f6245709
Ref: os path-Footnote-1246732
Ref: os path-Footnote-2246775
Ref: os path-Footnote-3246818
Node: pathlib246861
Ref: whatsnew/3 8 pathlib246952
Ref: 201246952
Ref: pathlib-Footnote-1247678
Ref: pathlib-Footnote-2247721
Node: pickle247764
Ref: whatsnew/3 8 pickle247856
Ref: 20d247856
Ref: pickle-Footnote-1248194
Node: plistlib248237
Ref: whatsnew/3 8 plistlib248328
Ref: 210248328
Ref: plistlib-Footnote-1248566
Node: pprint248609
Ref: whatsnew/3 8 pprint248704
Ref: 212248704
Ref: pprint-Footnote-1249769
Node: py_compile249812
Ref: whatsnew/3 8 py-compile249904
Ref: 215249904
Ref: py_compile-Footnote-1250093
Node: shlex250136
Ref: whatsnew/3 8 shlex250228
Ref: 217250228
Ref: shlex-Footnote-1250432
Node: shutil250475
Ref: whatsnew/3 8 shutil250563
Ref: 21a250563
Ref: shutil-Footnote-1251217
Ref: shutil-Footnote-2251260
Ref: shutil-Footnote-3251303
Node: socket251346
Ref: whatsnew/3 8 socket251432
Ref: 21e251432
Ref: socket-Footnote-1252007
Ref: socket-Footnote-2252050
Node: ssl252093
Ref: whatsnew/3 8 ssl252183
Ref: 224252183
Ref: ssl-Footnote-1252445
Node: statistics252488
Ref: whatsnew/3 8 statistics252575
Ref: 227252575
Ref: statistics-Footnote-1254306
Ref: statistics-Footnote-2254349
Ref: statistics-Footnote-3254392
Ref: statistics-Footnote-4254435
Ref: statistics-Footnote-5254478
Node: sys254521
Ref: whatsnew/3 8 sys254612
Ref: 22d254612
Ref: sys-Footnote-1255051
Node: tarfile255094
Ref: whatsnew/3 8 tarfile255184
Ref: 230255184
Ref: tarfile-Footnote-1255603
Node: threading255646
Ref: whatsnew/3 8 threading255741
Ref: 231255741
Ref: threading-Footnote-1256477
Ref: threading-Footnote-2256522
Node: tokenize256565
Ref: whatsnew/3 8 tokenize256660
Ref: 237256660
Ref: tokenize-Footnote-1256986
Node: tkinter257029
Ref: whatsnew/3 8 tkinter257119
Ref: 238257119
Ref: tkinter-Footnote-1257662
Ref: tkinter-Footnote-2257705
Ref: tkinter-Footnote-3257748
Node: time257791
Ref: whatsnew/3 8 time257879
Ref: 239257879
Ref: time-Footnote-1258058
Node: typing258101
Ref: whatsnew/3 8 typing258193
Ref: 23b258193
Ref: typing-Footnote-1259659
Ref: typing-Footnote-2259708
Ref: typing-Footnote-3259757
Ref: typing-Footnote-4259806
Node: unicodedata259855
Ref: whatsnew/3 8 unicodedata259951
Ref: 246259951
Ref: unicodedata-Footnote-1260380
Ref: unicodedata-Footnote-2260441
Ref: unicodedata-Footnote-3260484
Node: unittest260527
Ref: whatsnew/3 8 unittest260621
Ref: 248260621
Ref: unittest-Footnote-1261911
Ref: unittest-Footnote-2261954
Ref: unittest-Footnote-3261997
Ref: unittest-Footnote-4262040
Node: venv262083
Ref: whatsnew/3 8 venv262173
Ref: 24f262173
Ref: venv-Footnote-1262425
Node: weakref262468
Ref: whatsnew/3 8 weakref262553
Ref: 250262553
Ref: weakref-Footnote-1262846
Node: xml262889
Ref: whatsnew/3 8 xml262976
Ref: 252262976
Ref: xml-Footnote-1264150
Ref: xml-Footnote-2264193
Ref: xml-Footnote-3264236
Ref: xml-Footnote-4264279
Ref: xml-Footnote-5264322
Node: xmlrpc264365
Ref: whatsnew/3 8 xmlrpc264436
Ref: 255264436
Ref: xmlrpc-Footnote-1264828
Node: Optimizations264871
Ref: whatsnew/3 8 optimizations265002
Ref: 257265002
Ref: Optimizations-Footnote-1269353
Ref: Optimizations-Footnote-2269396
Ref: Optimizations-Footnote-3269439
Ref: Optimizations-Footnote-4269482
Ref: Optimizations-Footnote-5269525
Ref: Optimizations-Footnote-6269568
Ref: Optimizations-Footnote-7269611
Ref: Optimizations-Footnote-8269654
Ref: Optimizations-Footnote-9269697
Ref: Optimizations-Footnote-10269740
Ref: Optimizations-Footnote-11269784
Ref: Optimizations-Footnote-12269828
Ref: Optimizations-Footnote-13269872
Node: Build and C API Changes269916
Ref: whatsnew/3 8 build-and-c-api-changes270041
Ref: 264270041
Ref: Build and C API Changes-Footnote-1275632
Ref: Build and C API Changes-Footnote-2275675
Ref: Build and C API Changes-Footnote-3275718
Ref: Build and C API Changes-Footnote-4275761
Ref: Build and C API Changes-Footnote-5275804
Ref: Build and C API Changes-Footnote-6275847
Ref: Build and C API Changes-Footnote-7275890
Ref: Build and C API Changes-Footnote-8275933
Ref: Build and C API Changes-Footnote-9275976
Ref: Build and C API Changes-Footnote-10276019
Ref: Build and C API Changes-Footnote-11276063
Ref: Build and C API Changes-Footnote-12276107
Node: Deprecated276151
Ref: whatsnew/3 8 deprecated276287
Ref: 278276287
Ref: Deprecated-Footnote-1282151
Ref: Deprecated-Footnote-2282194
Ref: Deprecated-Footnote-3282237
Ref: Deprecated-Footnote-4282280
Ref: Deprecated-Footnote-5282322
Ref: Deprecated-Footnote-6282365
Ref: Deprecated-Footnote-7282408
Ref: Deprecated-Footnote-8282451
Ref: Deprecated-Footnote-9282494
Ref: Deprecated-Footnote-10282537
Ref: Deprecated-Footnote-11282581
Ref: Deprecated-Footnote-12282625
Ref: Deprecated-Footnote-13282669
Node: API and Feature Removals282713
Ref: whatsnew/3 8 api-and-feature-removals282847
Ref: 2a9282847
Ref: API and Feature Removals-Footnote-1285677
Ref: API and Feature Removals-Footnote-2285720
Ref: API and Feature Removals-Footnote-3285763
Ref: API and Feature Removals-Footnote-4285806
Ref: API and Feature Removals-Footnote-5285849
Ref: API and Feature Removals-Footnote-6285892
Ref: API and Feature Removals-Footnote-7285935
Ref: API and Feature Removals-Footnote-8285978
Ref: API and Feature Removals-Footnote-9286021
Ref: API and Feature Removals-Footnote-10286064
Ref: API and Feature Removals-Footnote-11286108
Node: Porting to Python 3 8286152
Ref: whatsnew/3 8 porting-to-python-3-8286307
Ref: 2af286307
Node: Changes in Python behavior286618
Ref: whatsnew/3 8 changes-in-python-behavior286736
Ref: 2b0286736
Ref: Changes in Python behavior-Footnote-1289116
Ref: Changes in Python behavior-Footnote-2289159
Ref: Changes in Python behavior-Footnote-3289202
Ref: Changes in Python behavior-Footnote-4289245
Ref: Changes in Python behavior-Footnote-5289288
Ref: Changes in Python behavior-Footnote-6289331
Node: Changes in the Python API289374
Ref: whatsnew/3 8 changes-in-the-python-api289521
Ref: 2b8289521
Ref: whatsnew/3 8 bpo-36085-whatsnew296475
Ref: 2cb296475
Ref: Changes in the Python API-Footnote-1298025
Ref: Changes in the Python API-Footnote-2298074
Ref: Changes in the Python API-Footnote-3298117
Ref: Changes in the Python API-Footnote-4298160
Ref: Changes in the Python API-Footnote-5298203
Ref: Changes in the Python API-Footnote-6298246
Ref: Changes in the Python API-Footnote-7298289
Ref: Changes in the Python API-Footnote-8298332
Ref: Changes in the Python API-Footnote-9298375
Ref: Changes in the Python API-Footnote-10298418
Ref: Changes in the Python API-Footnote-11298462
Ref: Changes in the Python API-Footnote-12298506
Ref: Changes in the Python API-Footnote-13298550
Ref: Changes in the Python API-Footnote-14298594
Ref: Changes in the Python API-Footnote-15298638
Ref: Changes in the Python API-Footnote-16298682
Ref: Changes in the Python API-Footnote-17298726
Ref: Changes in the Python API-Footnote-18298769
Ref: Changes in the Python API-Footnote-19298813
Ref: Changes in the Python API-Footnote-20298857
Ref: Changes in the Python API-Footnote-21298901
Ref: Changes in the Python API-Footnote-22298945
Ref: Changes in the Python API-Footnote-23298989
Ref: Changes in the Python API-Footnote-24299033
Ref: Changes in the Python API-Footnote-25299077
Ref: Changes in the Python API-Footnote-26299121
Ref: Changes in the Python API-Footnote-27299165
Node: Changes in the C API299215
Ref: whatsnew/3 8 changes-in-the-c-api299360
Ref: 2cc299360
Ref: Changes in the C API-Footnote-1305192
Ref: Changes in the C API-Footnote-2305235
Ref: Changes in the C API-Footnote-3305278
Ref: Changes in the C API-Footnote-4305321
Ref: Changes in the C API-Footnote-5305364
Ref: Changes in the C API-Footnote-6305407
Ref: Changes in the C API-Footnote-7305450
Ref: Changes in the C API-Footnote-8305493
Node: CPython bytecode changes305536
Ref: whatsnew/3 8 cpython-bytecode-changes305671
Ref: 2db305671
Ref: CPython bytecode changes-Footnote-1307033
Ref: CPython bytecode changes-Footnote-2307076
Ref: CPython bytecode changes-Footnote-3307119
Ref: CPython bytecode changes-Footnote-4307168
Node: Demos and Tools307211
Ref: whatsnew/3 8 demos-and-tools307317
Ref: 2e6307317
Ref: Demos and Tools-Footnote-1310614
Ref: Demos and Tools-Footnote-2310657
Ref: Demos and Tools-Footnote-3310785
Node: Notable changes in Python 3 8 1310835
Ref: whatsnew/3 8 notable-changes-in-python-3-8-1310997
Ref: 2e7310997
Ref: Notable changes in Python 3 8 1-Footnote-1311508
Node: Notable changes in Python 3 8 2311551
Ref: whatsnew/3 8 notable-changes-in-python-3-8-2311723
Ref: 2e9311723
Ref: Notable changes in Python 3 8 2-Footnote-1312046
Node: Notable changes in Python 3 8 3312089
Ref: whatsnew/3 8 notable-changes-in-python-3-8-3312261
Ref: 2ea312261
Ref: Notable changes in Python 3 8 3-Footnote-1312649
Node: Notable changes in Python 3 8 8312692
Ref: whatsnew/3 8 notable-changes-in-python-3-8-8312864
Ref: 2eb312864
Ref: Notable changes in Python 3 8 8-Footnote-1313594
Node: Notable changes in Python 3 8 9313637
Ref: whatsnew/3 8 notable-changes-in-python-3-8-9313810
Ref: 2f0313810
Ref: Notable changes in Python 3 8 9-Footnote-1314282
Node: Notable changes in Python 3 8 10314325
Ref: whatsnew/3 8 notable-changes-in-python-3-8-10314502
Ref: 2f2314502
Node: macOS 11 0 Big Sur and Apple Silicon Mac support314697
Ref: whatsnew/3 8 macos-11-0-big-sur-and-apple-silicon-mac-support314814
Ref: 2f3314814
Ref: macOS 11 0 Big Sur and Apple Silicon Mac support-Footnote-1315788
Node: Notable changes in Python 3 8 10<2>315831
Ref: whatsnew/3 8 id1315968
Ref: 2f4315968
Node: urllib parse316089
Ref: whatsnew/3 8 urllib-parse316173
Ref: 2f5316173
Ref: urllib parse-Footnote-1316703
Ref: urllib parse-Footnote-2316752
Node: What's New In Python 3 7316795
Ref: whatsnew/3 7 doc316950
Ref: 2f6316950
Ref: whatsnew/3 7 what-s-new-in-python-3-7316950
Ref: 2f7316950
Node: Summary -- Release Highlights318198
Ref: whatsnew/3 7 summary-release-highlights318312
Ref: 2f8318312
Ref: Summary -- Release Highlights-Footnote-1320465
Ref: Summary -- Release Highlights-Footnote-2320545
Ref: Summary -- Release Highlights-Footnote-3320581
Ref: Summary -- Release Highlights-Footnote-4320617
Node: New Features<2>320653
Ref: whatsnew/3 7 new-features320801
Ref: 30d320801
Node: PEP 563 Postponed Evaluation of Annotations321899
Ref: whatsnew/3 7 pep-563-postponed-evaluation-of-annotations322035
Ref: 30e322035
Ref: whatsnew/3 7 whatsnew37-pep563322035
Ref: 2f9322035
Ref: PEP 563 Postponed Evaluation of Annotations-Footnote-1323798
Ref: PEP 563 Postponed Evaluation of Annotations-Footnote-2323847
Ref: PEP 563 Postponed Evaluation of Annotations-Footnote-3323896
Node: PEP 538 Legacy C Locale Coercion323945
Ref: whatsnew/3 7 pep-538-legacy-c-locale-coercion324123
Ref: 310324123
Ref: whatsnew/3 7 whatsnew37-pep538324123
Ref: 304324123
Ref: PEP 538 Legacy C Locale Coercion-Footnote-1326505
Ref: PEP 538 Legacy C Locale Coercion-Footnote-2326554
Ref: PEP 538 Legacy C Locale Coercion-Footnote-3326603
Ref: PEP 538 Legacy C Locale Coercion-Footnote-4326652
Node: PEP 540 Forced UTF-8 Runtime Mode326701
Ref: whatsnew/3 7 pep-540-forced-utf-8-runtime-mode326863
Ref: 315326863
Ref: whatsnew/3 7 whatsnew37-pep540326863
Ref: 305326863
Ref: PEP 540 Forced UTF-8 Runtime Mode-Footnote-1328418
Ref: PEP 540 Forced UTF-8 Runtime Mode-Footnote-2328467
Ref: PEP 540 Forced UTF-8 Runtime Mode-Footnote-3328516
Node: PEP 553 Built-in breakpoint328565
Ref: whatsnew/3 7 pep-553-built-in-breakpoint328737
Ref: 317328737
Ref: whatsnew/3 7 whatsnew37-pep553328737
Ref: 2fd328737
Ref: PEP 553 Built-in breakpoint-Footnote-1329575
Node: PEP 539 New C API for Thread-Local Storage329624
Ref: whatsnew/3 7 pep-539-new-c-api-for-thread-local-storage329815
Ref: 31a329815
Ref: whatsnew/3 7 whatsnew37-pep539329815
Ref: 309329815
Ref: PEP 539 New C API for Thread-Local Storage-Footnote-1331333
Ref: PEP 539 New C API for Thread-Local Storage-Footnote-2331382
Node: PEP 562 Customization of Access to Module Attributes331431
Ref: whatsnew/3 7 pep-562-customization-of-access-to-module-attributes331648
Ref: 31e331648
Ref: whatsnew/3 7 whatsnew37-pep562331648
Ref: 2ff331648
Ref: PEP 562 Customization of Access to Module Attributes-Footnote-1332234
Node: PEP 564 New Time Functions With Nanosecond Resolution332283
Ref: whatsnew/3 7 pep-564-new-time-functions-with-nanosecond-resolution332501
Ref: 321332501
Ref: whatsnew/3 7 whatsnew37-pep564332501
Ref: 303332501
Ref: PEP 564 New Time Functions With Nanosecond Resolution-Footnote-1333582
Ref: PEP 564 New Time Functions With Nanosecond Resolution-Footnote-2333631
Ref: PEP 564 New Time Functions With Nanosecond Resolution-Footnote-3333716
Node: PEP 565 Show DeprecationWarning in __main__333765
Ref: whatsnew/3 7 pep-565-show-deprecationwarning-in-main333987
Ref: 329333987
Ref: whatsnew/3 7 whatsnew37-pep565333987
Ref: 308333987
Ref: PEP 565 Show DeprecationWarning in __main__-Footnote-1335918
Node: PEP 560 Core Support for typing module and Generic Types335967
Ref: whatsnew/3 7 pep-560-core-support-for-typing-module-and-generic-types336164
Ref: 32b336164
Ref: whatsnew/3 7 whatsnew37-pep560336164
Ref: 300336164
Ref: PEP 560 Core Support for typing module and Generic Types-Footnote-1337118
Ref: PEP 560 Core Support for typing module and Generic Types-Footnote-2337167
Node: PEP 552 Hash-based pyc Files337216
Ref: whatsnew/3 7 pep-552-hash-based-pyc-files337411
Ref: 32d337411
Ref: whatsnew/3 7 whatsnew37-pep552337411
Ref: 306337411
Ref: PEP 552 Hash-based pyc Files-Footnote-1339080
Ref: PEP 552 Hash-based pyc Files-Footnote-2339121
Ref: PEP 552 Hash-based pyc Files-Footnote-3339170
Node: PEP 545 Python Documentation Translations339219
Ref: whatsnew/3 7 pep-545-python-documentation-translations339389
Ref: 32f339389
Ref: whatsnew/3 7 whatsnew37-pep545339389
Ref: 30a339389
Ref: PEP 545 Python Documentation Translations-Footnote-1339972
Ref: PEP 545 Python Documentation Translations-Footnote-2340021
Node: Development Runtime Mode -X dev340070
Ref: whatsnew/3 7 development-runtime-mode-x-dev340203
Ref: 330340203
Ref: whatsnew/3 7 whatsnew37-devmode340203
Ref: 307340203
Node: Other Language Changes<2>340671
Ref: whatsnew/3 7 other-language-changes340804
Ref: 332340804
Ref: Other Language Changes<2>-Footnote-1343193
Ref: Other Language Changes<2>-Footnote-2343236
Ref: Other Language Changes<2>-Footnote-3343279
Ref: Other Language Changes<2>-Footnote-4343322
Ref: Other Language Changes<2>-Footnote-5343365
Ref: Other Language Changes<2>-Footnote-6343408
Ref: Other Language Changes<2>-Footnote-7343451
Ref: Other Language Changes<2>-Footnote-8343494
Ref: Other Language Changes<2>-Footnote-9343537
Ref: Other Language Changes<2>-Footnote-10343580
Node: New Modules<2>343624
Ref: whatsnew/3 7 new-modules343761
Ref: 33e343761
Node: contextvars343884
Ref: whatsnew/3 7 contextvars343966
Ref: 33f343966
Ref: whatsnew/3 7 whatsnew37-pep567343966
Ref: 2fa343966
Ref: contextvars-Footnote-1344694
Node: dataclasses344743
Ref: whatsnew/3 7 dataclasses344853
Ref: 341344853
Ref: whatsnew/3 7 whatsnew37-pep557344853
Ref: 2fb344853
Ref: dataclasses-Footnote-1345523
Node: importlib resources345572
Ref: whatsnew/3 7 importlib-resources345662
Ref: 346345662
Ref: whatsnew/3 7 whatsnew37-importlib-resources345662
Ref: 2fc345662
Ref: importlib resources-Footnote-1346409
Ref: importlib resources-Footnote-2346452
Node: Improved Modules<2>346513
Ref: whatsnew/3 7 improved-modules346638
Ref: 348346638
Node: argparse347792
Ref: whatsnew/3 7 argparse347875
Ref: 349347875
Ref: argparse-Footnote-1348109
Node: asyncio<2>348152
Ref: whatsnew/3 7 asyncio348252
Ref: 34b348252
Ref: whatsnew/3 7 whatsnew37-asyncio348252
Ref: 302348252
Ref: asyncio<2>-Footnote-1354554
Ref: asyncio<2>-Footnote-2354597
Ref: asyncio<2>-Footnote-3354646
Ref: asyncio<2>-Footnote-4354689
Ref: asyncio<2>-Footnote-5354732
Ref: asyncio<2>-Footnote-6354775
Ref: asyncio<2>-Footnote-7354818
Ref: asyncio<2>-Footnote-8354861
Ref: asyncio<2>-Footnote-9354904
Ref: asyncio<2>-Footnote-10354947
Ref: asyncio<2>-Footnote-11354991
Ref: asyncio<2>-Footnote-12355035
Ref: asyncio<2>-Footnote-13355079
Ref: asyncio<2>-Footnote-14355123
Ref: asyncio<2>-Footnote-15355167
Ref: asyncio<2>-Footnote-16355211
Ref: asyncio<2>-Footnote-17355255
Ref: asyncio<2>-Footnote-18355299
Ref: asyncio<2>-Footnote-19355343
Ref: asyncio<2>-Footnote-20355387
Ref: asyncio<2>-Footnote-21355431
Ref: asyncio<2>-Footnote-22355475
Ref: asyncio<2>-Footnote-23355519
Ref: asyncio<2>-Footnote-24355563
Node: binascii355607
Ref: whatsnew/3 7 binascii355707
Ref: 371355707
Ref: binascii-Footnote-1355986
Node: calendar356029
Ref: whatsnew/3 7 calendar356133
Ref: 373356133
Ref: calendar-Footnote-1356383
Node: collections<2>356426
Ref: whatsnew/3 7 collections356532
Ref: 375356532
Ref: collections<2>-Footnote-1356723
Node: compileall356766
Ref: whatsnew/3 7 compileall356882
Ref: 376356882
Ref: compileall-Footnote-1357279
Node: concurrent futures357322
Ref: whatsnew/3 7 concurrent-futures357434
Ref: 378357434
Ref: concurrent futures-Footnote-1357876
Ref: concurrent futures-Footnote-2357919
Node: contextlib357962
Ref: whatsnew/3 7 contextlib358075
Ref: 379358075
Ref: contextlib-Footnote-1358605
Ref: contextlib-Footnote-2358648
Ref: contextlib-Footnote-3358691
Ref: contextlib-Footnote-4358734
Node: cProfile<2>358777
Ref: whatsnew/3 7 cprofile358877
Ref: 37f358877
Ref: cProfile<2>-Footnote-1359103
Node: crypt359146
Ref: whatsnew/3 7 crypt359247
Ref: 380359247
Ref: crypt-Footnote-1359579
Ref: crypt-Footnote-2359622
Node: datetime<2>359665
Ref: whatsnew/3 7 datetime359758
Ref: 382359758
Ref: datetime<2>-Footnote-1360169
Ref: datetime<2>-Footnote-2360212
Node: dbm360254
Ref: whatsnew/3 7 dbm360349
Ref: 386360349
Node: decimal360494
Ref: whatsnew/3 7 decimal360581
Ref: 387360581
Ref: decimal-Footnote-1360802
Node: dis360845
Ref: whatsnew/3 7 dis360938
Ref: 388360938
Ref: dis-Footnote-1361341
Node: distutils361384
Ref: whatsnew/3 7 distutils361474
Ref: 38a361474
Ref: distutils-Footnote-1361722
Node: enum361765
Ref: whatsnew/3 7 enum361864
Ref: 38b361864
Ref: enum-Footnote-1362532
Ref: enum-Footnote-2362575
Node: functools<2>362618
Ref: whatsnew/3 7 functools362713
Ref: 38e362713
Ref: functools<2>-Footnote-1362942
Node: gc<2>362985
Ref: whatsnew/3 7 gc363080
Ref: 390363080
Ref: gc<2>-Footnote-1363619
Node: hmac363662
Ref: whatsnew/3 7 hmac363756
Ref: 394363756
Ref: hmac-Footnote-1364014
Node: http client364057
Ref: whatsnew/3 7 http-client364157
Ref: 396364157
Ref: http client-Footnote-1364414
Node: http server364457
Ref: whatsnew/3 7 http-server364569
Ref: 399364569
Ref: http server-Footnote-1365447
Ref: http server-Footnote-2365490
Ref: http server-Footnote-3365533
Node: idlelib and IDLE365576
Ref: whatsnew/3 7 idlelib-and-idle365686
Ref: 39c365686
Ref: idlelib and IDLE-Footnote-1368691
Ref: idlelib and IDLE-Footnote-2368734
Ref: idlelib and IDLE-Footnote-3368779
Ref: idlelib and IDLE-Footnote-4368822
Ref: idlelib and IDLE-Footnote-5368865
Ref: idlelib and IDLE-Footnote-6368908
Ref: idlelib and IDLE-Footnote-7368951
Ref: idlelib and IDLE-Footnote-8368994
Ref: idlelib and IDLE-Footnote-9369037
Ref: idlelib and IDLE-Footnote-10369080
Ref: idlelib and IDLE-Footnote-11369126
Ref: idlelib and IDLE-Footnote-12369169
Ref: idlelib and IDLE-Footnote-13369213
Node: importlib369257
Ref: whatsnew/3 7 importlib369361
Ref: 39d369361
Ref: importlib-Footnote-1370232
Ref: importlib-Footnote-2370275
Ref: importlib-Footnote-3370318
Node: io<2>370361
Ref: whatsnew/3 7 io370458
Ref: 3a1370458
Ref: io<2>-Footnote-1370723
Ref: io<2>-Footnote-2370766
Node: ipaddress370809
Ref: whatsnew/3 7 ipaddress370909
Ref: 3a3370909
Ref: ipaddress-Footnote-1371229
Node: itertools<2>371272
Ref: whatsnew/3 7 itertools371373
Ref: 3a6371373
Ref: itertools<2>-Footnote-1371610
Node: locale371653
Ref: whatsnew/3 7 locale371755
Ref: 3a8371755
Ref: locale-Footnote-1372169
Node: logging<2>372212
Ref: whatsnew/3 7 logging372309
Ref: 3ab372309
Ref: logging<2>-Footnote-1372833
Ref: logging<2>-Footnote-2372876
Ref: logging<2>-Footnote-3372919
Node: math<2>372962
Ref: whatsnew/3 7 math373062
Ref: 3af373062
Ref: math<2>-Footnote-1373275
Node: mimetypes373318
Ref: whatsnew/3 7 mimetypes373414
Ref: 3b1373414
Ref: mimetypes-Footnote-1373629
Node: msilib373672
Ref: whatsnew/3 7 msilib373779
Ref: 3b2373779
Ref: msilib-Footnote-1374002
Node: multiprocessing<2>374045
Ref: whatsnew/3 7 multiprocessing374148
Ref: 3b4374148
Ref: multiprocessing<2>-Footnote-1374795
Ref: multiprocessing<2>-Footnote-2374838
Ref: multiprocessing<2>-Footnote-3374881
Node: os<2>374924
Ref: whatsnew/3 7 os375031
Ref: 3b8375031
Ref: os<2>-Footnote-1376329
Ref: os<2>-Footnote-2376372
Ref: os<2>-Footnote-3376415
Ref: os<2>-Footnote-4376458
Ref: os<2>-Footnote-5376501
Ref: os<2>-Footnote-6376544
Ref: os<2>-Footnote-7376587
Node: pathlib<2>376630
Ref: whatsnew/3 7 pathlib376722
Ref: 3c5376722
Ref: pathlib<2>-Footnote-1376982
Node: pdb377025
Ref: whatsnew/3 7 pdb377125
Ref: 3c6377125
Ref: pdb-Footnote-1377535
Ref: pdb-Footnote-2377578
Node: py_compile<2>377621
Ref: whatsnew/3 7 py-compile377716
Ref: 3c8377716
Ref: py_compile<2>-Footnote-1378170
Ref: py_compile<2>-Footnote-2378211
Node: pydoc378254
Ref: whatsnew/3 7 pydoc378351
Ref: 3c9378351
Ref: pydoc-Footnote-1378575
Node: queue378618
Ref: whatsnew/3 7 queue378704
Ref: 3ca378704
Ref: queue-Footnote-1378909
Node: re378952
Ref: whatsnew/3 7 re379039
Ref: 3cc379039
Ref: re-Footnote-1380115
Ref: re-Footnote-2380158
Ref: re-Footnote-3380201
Ref: re-Footnote-4380244
Ref: re-Footnote-5380287
Node: signal380330
Ref: whatsnew/3 7 signal380421
Ref: 3d2380421
Ref: signal-Footnote-1380740
Node: socket<2>380783
Ref: whatsnew/3 7 socket380884
Ref: 3d4380884
Ref: socket<2>-Footnote-1381972
Ref: socket<2>-Footnote-2382015
Ref: socket<2>-Footnote-3382058
Ref: socket<2>-Footnote-4382101
Ref: socket<2>-Footnote-5382144
Ref: socket<2>-Footnote-6382187
Node: socketserver382230
Ref: whatsnew/3 7 socketserver382332
Ref: 3d9382332
Node: sqlite3382808
Ref: whatsnew/3 7 sqlite3382907
Ref: 3dc382907
Ref: sqlite3-Footnote-1383349
Ref: sqlite3-Footnote-2383392
Node: ssl<2>383435
Ref: whatsnew/3 7 ssl383528
Ref: 3e0383528
Ref: ssl<2>-Footnote-1386579
Ref: ssl<2>-Footnote-2386622
Ref: ssl<2>-Footnote-3386665
Ref: ssl<2>-Footnote-4386708
Ref: ssl<2>-Footnote-5386751
Ref: ssl<2>-Footnote-6386794
Ref: ssl<2>-Footnote-7386837
Ref: ssl<2>-Footnote-8386880
Ref: ssl<2>-Footnote-9386923
Ref: ssl<2>-Footnote-10386966
Ref: ssl<2>-Footnote-11387010
Ref: ssl<2>-Footnote-12387054
Ref: ssl<2>-Footnote-13387098
Node: string387142
Ref: whatsnew/3 7 string387238
Ref: 3ef387238
Ref: string-Footnote-1387515
Node: subprocess387560
Ref: whatsnew/3 7 subprocess387656
Ref: 3f1387656
Ref: subprocess-Footnote-1388978
Ref: subprocess-Footnote-2389021
Ref: subprocess-Footnote-3389064
Ref: subprocess-Footnote-4389107
Node: sys<2>389150
Ref: whatsnew/3 7 sys389247
Ref: 3f5389247
Ref: sys<2>-Footnote-1389987
Ref: sys<2>-Footnote-2390030
Ref: sys<2>-Footnote-3390073
Node: time<2>390116
Ref: whatsnew/3 7 time390213
Ref: 3f9390213
Ref: time<2>-Footnote-1391423
Ref: time<2>-Footnote-2391472
Node: tkinter<2>391515
Ref: whatsnew/3 7 tkinter391617
Ref: 401391617
Ref: tkinter<2>-Footnote-1391798
Node: tracemalloc391841
Ref: whatsnew/3 7 tracemalloc391941
Ref: 403391941
Ref: tracemalloc-Footnote-1392407
Node: types392450
Ref: whatsnew/3 7 types392554
Ref: 406392554
Ref: types-Footnote-1393069
Ref: types-Footnote-2393112
Ref: types-Footnote-3393155
Ref: types-Footnote-4393204
Node: unicodedata<2>393247
Ref: whatsnew/3 7 unicodedata393351
Ref: 40c393351
Ref: unicodedata<2>-Footnote-1393554
Node: unittest<2>393609
Ref: whatsnew/3 7 unittest393721
Ref: 40d393721
Ref: unittest<2>-Footnote-1394126
Node: unittest mock394169
Ref: whatsnew/3 7 unittest-mock394282
Ref: 40e394282
Ref: unittest mock-Footnote-1394800
Ref: unittest mock-Footnote-2394843
Node: urllib parse<2>394886
Ref: whatsnew/3 7 urllib-parse394990
Ref: 411394990
Ref: urllib parse<2>-Footnote-1395303
Ref: urllib parse<2>-Footnote-2395352
Ref: urllib parse<2>-Footnote-3395401
Node: uu395444
Ref: whatsnew/3 7 uu395539
Ref: 413395539
Ref: uu-Footnote-1395811
Node: uuid395854
Ref: whatsnew/3 7 uuid395942
Ref: 415395942
Ref: uuid-Footnote-1396582
Ref: uuid-Footnote-2396625
Node: warnings396668
Ref: whatsnew/3 7 warnings396763
Ref: 419396763
Ref: warnings-Footnote-1398217
Ref: warnings-Footnote-2398260
Ref: warnings-Footnote-3398303
Ref: warnings-Footnote-4398346
Node: xml etree398389
Ref: whatsnew/3 7 xml-etree398493
Ref: 41e398493
Ref: xml etree-Footnote-1398834
Node: xmlrpc server398877
Ref: whatsnew/3 7 xmlrpc-server398979
Ref: 420398979
Ref: xmlrpc server-Footnote-1399188
Node: zipapp399230
Ref: whatsnew/3 7 zipapp399330
Ref: 421399330
Ref: zipapp-Footnote-1399854
Ref: zipapp-Footnote-2399897
Node: zipfile399940
Ref: whatsnew/3 7 zipfile400018
Ref: 423400018
Ref: zipfile-Footnote-1400383
Ref: zipfile-Footnote-2400426
Node: C API Changes400469
Ref: whatsnew/3 7 c-api-changes400593
Ref: 425400593
Ref: C API Changes-Footnote-1405105
Ref: C API Changes-Footnote-2405148
Ref: C API Changes-Footnote-3405191
Ref: C API Changes-Footnote-4405234
Ref: C API Changes-Footnote-5405277
Ref: C API Changes-Footnote-6405320
Ref: C API Changes-Footnote-7405363
Ref: C API Changes-Footnote-8405406
Ref: C API Changes-Footnote-9405449
Ref: C API Changes-Footnote-10405492
Ref: C API Changes-Footnote-11405536
Ref: C API Changes-Footnote-12405580
Ref: C API Changes-Footnote-13405624
Ref: C API Changes-Footnote-14405668
Ref: C API Changes-Footnote-15405712
Ref: C API Changes-Footnote-16405755
Ref: C API Changes-Footnote-17405799
Ref: C API Changes-Footnote-18405843
Ref: C API Changes-Footnote-19405887
Ref: C API Changes-Footnote-20405931
Node: Build Changes405975
Ref: whatsnew/3 7 build-changes406096
Ref: 446406096
Ref: Build Changes-Footnote-1407230
Ref: Build Changes-Footnote-2407273
Ref: Build Changes-Footnote-3407316
Node: Optimizations<2>407359
Ref: whatsnew/3 7 optimizations407503
Ref: 447407503
Ref: whatsnew/3 7 whatsnew37-perf407503
Ref: 30b407503
Ref: whatsnew/3 7 whatsnew37-asyncio-perf408197
Ref: 34c408197
Ref: Optimizations<2>-Footnote-1412747
Ref: Optimizations<2>-Footnote-2412790
Ref: Optimizations<2>-Footnote-3412833
Ref: Optimizations<2>-Footnote-4412876
Ref: Optimizations<2>-Footnote-5412919
Ref: Optimizations<2>-Footnote-6412962
Ref: Optimizations<2>-Footnote-7413005
Ref: Optimizations<2>-Footnote-8413048
Ref: Optimizations<2>-Footnote-9413091
Ref: Optimizations<2>-Footnote-10413134
Ref: Optimizations<2>-Footnote-11413178
Ref: Optimizations<2>-Footnote-12413222
Ref: Optimizations<2>-Footnote-13413266
Ref: Optimizations<2>-Footnote-14413310
Ref: Optimizations<2>-Footnote-15413354
Ref: Optimizations<2>-Footnote-16413398
Ref: Optimizations<2>-Footnote-17413442
Ref: Optimizations<2>-Footnote-18413486
Ref: Optimizations<2>-Footnote-19413530
Ref: Optimizations<2>-Footnote-20413574
Ref: Optimizations<2>-Footnote-21413618
Ref: Optimizations<2>-Footnote-22413662
Ref: Optimizations<2>-Footnote-23413706
Ref: Optimizations<2>-Footnote-24413750
Ref: Optimizations<2>-Footnote-25413794
Ref: Optimizations<2>-Footnote-26413838
Ref: Optimizations<2>-Footnote-27413882
Ref: Optimizations<2>-Footnote-28413926
Ref: Optimizations<2>-Footnote-29413970
Ref: Optimizations<2>-Footnote-30414014
Node: Other CPython Implementation Changes414058
Ref: whatsnew/3 7 other-cpython-implementation-changes414215
Ref: 459414215
Ref: Other CPython Implementation Changes-Footnote-1415616
Ref: Other CPython Implementation Changes-Footnote-2415659
Ref: Other CPython Implementation Changes-Footnote-3415702
Ref: Other CPython Implementation Changes-Footnote-4415745
Ref: Other CPython Implementation Changes-Footnote-5415788
Node: Deprecated Python Behavior415831
Ref: whatsnew/3 7 deprecated-python-behavior416019
Ref: 45b416019
Ref: Deprecated Python Behavior-Footnote-1417128
Ref: Deprecated Python Behavior-Footnote-2417171
Node: Deprecated Python modules functions and methods417214
Ref: whatsnew/3 7 deprecated-python-modules-functions-and-methods417409
Ref: 45e417409
Node: aifc417807
Ref: whatsnew/3 7 aifc417914
Ref: 45f417914
Ref: aifc-Footnote-1418140
Node: asyncio<3>418183
Ref: whatsnew/3 7 id2418313
Ref: 461418313
Ref: whatsnew/3 7 whatsnew37-asyncio-deprecated418313
Ref: 370418313
Ref: asyncio<3>-Footnote-1418849
Ref: asyncio<3>-Footnote-2418892
Node: collections<3>418935
Ref: whatsnew/3 7 id3419067
Ref: 462419067
Ref: collections<3>-Footnote-1419446
Node: dbm<2>419489
Ref: whatsnew/3 7 id4419618
Ref: 463419618
Ref: dbm<2>-Footnote-1420019
Node: enum<2>420062
Ref: whatsnew/3 7 id5420187
Ref: 464420187
Ref: enum<2>-Footnote-1420637
Node: gettext<2>420680
Ref: whatsnew/3 7 gettext420811
Ref: 465420811
Ref: gettext<2>-Footnote-1421056
Node: importlib<2>421099
Ref: whatsnew/3 7 id6421232
Ref: 466421232
Ref: importlib<2>-Footnote-1421758
Node: locale<2>421801
Ref: whatsnew/3 7 id7421931
Ref: 46c421931
Ref: locale<2>-Footnote-1422140
Node: macpath422183
Ref: whatsnew/3 7 macpath422313
Ref: 46e422313
Ref: macpath-Footnote-1422503
Node: threading<2>422545
Ref: whatsnew/3 7 threading422675
Ref: 46f422675
Ref: threading<2>-Footnote-1422983
Node: socket<3>423026
Ref: whatsnew/3 7 id8423155
Ref: 470423155
Ref: socket<3>-Footnote-1423500
Node: ssl<3>423543
Ref: whatsnew/3 7 id9423665
Ref: 473423665
Ref: ssl<3>-Footnote-1423883
Node: sunau423926
Ref: whatsnew/3 7 sunau424045
Ref: 475424045
Ref: sunau-Footnote-1424284
Node: sys<3>424327
Ref: whatsnew/3 7 id10424444
Ref: 478424444
Ref: sys<3>-Footnote-1424761
Node: wave424804
Ref: whatsnew/3 7 wave424907
Ref: 479424907
Ref: wave-Footnote-1425142
Node: Deprecated functions and types of the C API425185
Ref: whatsnew/3 7 deprecated-functions-and-types-of-the-c-api425379
Ref: 47c425379
Ref: Deprecated functions and types of the C API-Footnote-1426037
Ref: Deprecated functions and types of the C API-Footnote-2426080
Node: Platform Support Removals426123
Ref: whatsnew/3 7 id11426297
Ref: 47e426297
Ref: whatsnew/3 7 platform-support-removals426297
Ref: 3e4426297
Ref: Platform Support Removals-Footnote-1427693
Ref: Platform Support Removals-Footnote-2427756
Node: API and Feature Removals<2>427835
Ref: whatsnew/3 7 api-and-feature-removals427981
Ref: 47f427981
Ref: API and Feature Removals<2>-Footnote-1430950
Ref: API and Feature Removals<2>-Footnote-2430993
Ref: API and Feature Removals<2>-Footnote-3431036
Node: Module Removals431079
Ref: whatsnew/3 7 module-removals431220
Ref: 487431220
Ref: Module Removals-Footnote-1431555
Node: Windows-only Changes431598
Ref: whatsnew/3 7 windows-only-changes431733
Ref: 488431733
Ref: Windows-only Changes-Footnote-1432610
Ref: Windows-only Changes-Footnote-2432653
Node: Porting to Python 3 7432696
Ref: whatsnew/3 7 porting-to-python-3-7432847
Ref: 489432847
Ref: whatsnew/3 7 porting-to-python-37432847
Ref: 30c432847
Node: Changes in Python Behavior433309
Ref: whatsnew/3 7 changes-in-python-behavior433430
Ref: 48a433430
Ref: Changes in Python Behavior-Footnote-1435296
Ref: Changes in Python Behavior-Footnote-2435339
Ref: Changes in Python Behavior-Footnote-3435388
Ref: Changes in Python Behavior-Footnote-4435431
Ref: Changes in Python Behavior-Footnote-5435474
Ref: Changes in Python Behavior-Footnote-6435517
Node: Changes in the Python API<2>435560
Ref: whatsnew/3 7 changes-in-the-python-api435713
Ref: 48e435713
Ref: Changes in the Python API<2>-Footnote-1445264
Ref: Changes in the Python API<2>-Footnote-2445307
Ref: Changes in the Python API<2>-Footnote-3445350
Ref: Changes in the Python API<2>-Footnote-4445393
Ref: Changes in the Python API<2>-Footnote-5445436
Ref: Changes in the Python API<2>-Footnote-6445479
Ref: Changes in the Python API<2>-Footnote-7445522
Ref: Changes in the Python API<2>-Footnote-8445565
Ref: Changes in the Python API<2>-Footnote-9445608
Ref: Changes in the Python API<2>-Footnote-10445651
Ref: Changes in the Python API<2>-Footnote-11445695
Ref: Changes in the Python API<2>-Footnote-12445739
Ref: Changes in the Python API<2>-Footnote-13445783
Ref: Changes in the Python API<2>-Footnote-14445827
Ref: Changes in the Python API<2>-Footnote-15445870
Ref: Changes in the Python API<2>-Footnote-16445914
Ref: Changes in the Python API<2>-Footnote-17445958
Ref: Changes in the Python API<2>-Footnote-18446002
Ref: Changes in the Python API<2>-Footnote-19446046
Ref: Changes in the Python API<2>-Footnote-20446090
Ref: Changes in the Python API<2>-Footnote-21446134
Ref: Changes in the Python API<2>-Footnote-22446178
Ref: Changes in the Python API<2>-Footnote-23446222
Ref: Changes in the Python API<2>-Footnote-24446266
Ref: Changes in the Python API<2>-Footnote-25446310
Ref: Changes in the Python API<2>-Footnote-26446354
Ref: Changes in the Python API<2>-Footnote-27446398
Ref: Changes in the Python API<2>-Footnote-28446442
Ref: Changes in the Python API<2>-Footnote-29446486
Ref: Changes in the Python API<2>-Footnote-30446530
Node: Changes in the C API<2>446574
Ref: whatsnew/3 7 changes-in-the-c-api446728
Ref: 4b0446728
Ref: Changes in the C API<2>-Footnote-1447364
Node: CPython bytecode changes<2>447407
Ref: whatsnew/3 7 cpython-bytecode-changes447556
Ref: 4b1447556
Ref: CPython bytecode changes<2>-Footnote-1447908
Ref: CPython bytecode changes<2>-Footnote-2447951
Node: Windows-only Changes<2>447994
Ref: whatsnew/3 7 id12448156
Ref: 4b4448156
Ref: Windows-only Changes<2>-Footnote-1448477
Node: Other CPython implementation changes448520
Ref: whatsnew/3 7 id13448646
Ref: 4b6448646
Ref: Other CPython implementation changes-Footnote-1450994
Ref: Other CPython implementation changes-Footnote-2451043
Ref: Other CPython implementation changes-Footnote-3451086
Node: Notable changes in Python 3 7 1451129
Ref: whatsnew/3 7 notable-changes-in-python-3-7-1451291
Ref: 4bb451291
Ref: Notable changes in Python 3 7 1-Footnote-1452231
Ref: Notable changes in Python 3 7 1-Footnote-2452274
Ref: Notable changes in Python 3 7 1-Footnote-3452317
Node: Notable changes in Python 3 7 2452360
Ref: whatsnew/3 7 notable-changes-in-python-3-7-2452532
Ref: 4c0452532
Node: Notable changes in Python 3 7 6453027
Ref: whatsnew/3 7 notable-changes-in-python-3-7-6453200
Ref: 4c1453200
Ref: Notable changes in Python 3 7 6-Footnote-1453711
Node: Notable changes in Python 3 7 10453754
Ref: whatsnew/3 7 notable-changes-in-python-3-7-10453887
Ref: 4c2453887
Ref: Notable changes in Python 3 7 10-Footnote-1454619
Node: What's New In Python 3 6454662
Ref: whatsnew/3 6 doc454822
Ref: 4c3454822
Ref: whatsnew/3 6 what-s-new-in-python-3-6454822
Ref: 4c4454822
Ref: What's New In Python 3 6-Footnote-1456079
Ref: What's New In Python 3 6-Footnote-2456139
Node: Summary -- Release highlights<2>456188
Ref: whatsnew/3 6 summary-release-highlights456305
Ref: 4c5456305
Ref: Summary -- Release highlights<2>-Footnote-1460542
Ref: Summary -- Release highlights<2>-Footnote-2460622
Ref: Summary -- Release highlights<2>-Footnote-3460712
Node: New Features<3>460761
Ref: whatsnew/3 6 new-features460912
Ref: 4dc460912
Ref: whatsnew/3 6 pypy-dict-implementation460912
Ref: 4dd460912
Node: PEP 498 Formatted string literals462322
Ref: whatsnew/3 6 pep-498-formatted-string-literals462455
Ref: 4de462455
Ref: whatsnew/3 6 whatsnew36-pep498462455
Ref: 4c6462455
Ref: PEP 498 Formatted string literals-Footnote-1463438
Ref: PEP 498 Formatted string literals-Footnote-2463487
Node: PEP 526 Syntax for variable annotations463536
Ref: whatsnew/3 6 pep-526-syntax-for-variable-annotations463717
Ref: 4e1463717
Ref: whatsnew/3 6 whatsnew36-pep526463717
Ref: 4c8463717
Ref: PEP 526 Syntax for variable annotations-Footnote-1464960
Ref: PEP 526 Syntax for variable annotations-Footnote-2465009
Ref: PEP 526 Syntax for variable annotations-Footnote-3465058
Ref: PEP 526 Syntax for variable annotations-Footnote-4465092
Node: PEP 515 Underscores in Numeric Literals465133
Ref: whatsnew/3 6 pep-515-underscores-in-numeric-literals465312
Ref: 4e2465312
Ref: whatsnew/3 6 whatsnew36-pep515465312
Ref: 4c7465312
Ref: PEP 515 Underscores in Numeric Literals-Footnote-1466380
Ref: PEP 515 Underscores in Numeric Literals-Footnote-2466429
Node: PEP 525 Asynchronous Generators466478
Ref: whatsnew/3 6 pep-525-asynchronous-generators466653
Ref: 4e4466653
Ref: whatsnew/3 6 whatsnew36-pep525466653
Ref: 4c9466653
Ref: PEP 525 Asynchronous Generators-Footnote-1467487
Ref: PEP 525 Asynchronous Generators-Footnote-2467536
Node: PEP 530 Asynchronous Comprehensions467585
Ref: whatsnew/3 6 pep-530-asynchronous-comprehensions467768
Ref: 4e5467768
Ref: whatsnew/3 6 whatsnew36-pep530467768
Ref: 4ca467768
Ref: PEP 530 Asynchronous Comprehensions-Footnote-1468325
Ref: PEP 530 Asynchronous Comprehensions-Footnote-2468374
Node: PEP 487 Simpler customization of class creation468423
Ref: whatsnew/3 6 pep-487-simpler-customization-of-class-creation468615
Ref: 4e6468615
Ref: whatsnew/3 6 whatsnew36-pep487468615
Ref: 4cd468615
Ref: PEP 487 Simpler customization of class creation-Footnote-1469706
Node: PEP 487 Descriptor Protocol Enhancements469755
Ref: whatsnew/3 6 pep-487-descriptor-protocol-enhancements469954
Ref: 4eb469954
Ref: whatsnew/3 6 whatsnew36-pep487-descriptors469954
Ref: 4ec469954
Ref: PEP 487 Descriptor Protocol Enhancements-Footnote-1471204
Ref: PEP 487 Descriptor Protocol Enhancements-Footnote-2471253
Node: PEP 519 Adding a file system path protocol471302
Ref: whatsnew/3 6 pep-519-adding-a-file-system-path-protocol471487
Ref: 4ef471487
Ref: whatsnew/3 6 whatsnew36-pep519471487
Ref: 4d2471487
Ref: PEP 519 Adding a file system path protocol-Footnote-1474313
Node: PEP 495 Local Time Disambiguation474362
Ref: whatsnew/3 6 pep-495-local-time-disambiguation474558
Ref: 4f7474558
Ref: whatsnew/3 6 whatsnew36-pep495474558
Ref: 4d3474558
Ref: PEP 495 Local Time Disambiguation-Footnote-1475970
Ref: PEP 495 Local Time Disambiguation-Footnote-2476019
Node: PEP 529 Change Windows filesystem encoding to UTF-8476068
Ref: whatsnew/3 6 pep-529-change-windows-filesystem-encoding-to-utf-8476270
Ref: 4fa476270
Ref: whatsnew/3 6 whatsnew36-pep529476270
Ref: 4d9476270
Ref: PEP 529 Change Windows filesystem encoding to UTF-8-Footnote-1477300
Node: PEP 528 Change Windows console encoding to UTF-8477349
Ref: whatsnew/3 6 pep-528-change-windows-console-encoding-to-utf-8477569
Ref: 4fe477569
Ref: whatsnew/3 6 whatsnew36-pep528477569
Ref: 4d8477569
Ref: PEP 528 Change Windows console encoding to UTF-8-Footnote-1478271
Node: PEP 520 Preserving Class Attribute Definition Order478320
Ref: whatsnew/3 6 pep-520-preserving-class-attribute-definition-order478530
Ref: 500478530
Ref: whatsnew/3 6 whatsnew36-pep520478530
Ref: 4ce478530
Ref: PEP 520 Preserving Class Attribute Definition Order-Footnote-1479169
Node: PEP 468 Preserving Keyword Argument Order479218
Ref: whatsnew/3 6 pep-468-preserving-keyword-argument-order479403
Ref: 503479403
Ref: whatsnew/3 6 whatsnew36-pep468479403
Ref: 4cf479403
Ref: PEP 468 Preserving Keyword Argument Order-Footnote-1479763
Node: New dict implementation479812
Ref: whatsnew/3 6 new-dict-implementation479994
Ref: 504479994
Ref: whatsnew/3 6 whatsnew36-compactdict479994
Ref: 4cc479994
Ref: New dict implementation-Footnote-1480968
Ref: New dict implementation-Footnote-2481048
Ref: New dict implementation-Footnote-3481138
Ref: New dict implementation-Footnote-4481181
Node: PEP 523 Adding a frame evaluation API to CPython481261
Ref: whatsnew/3 6 pep-523-adding-a-frame-evaluation-api-to-cpython481435
Ref: 505481435
Ref: whatsnew/3 6 whatsnew36-pep523481435
Ref: 506481435
Ref: PEP 523 Adding a frame evaluation API to CPython-Footnote-1482605
Ref: PEP 523 Adding a frame evaluation API to CPython-Footnote-2482654
Node: PYTHONMALLOC environment variable482703
Ref: whatsnew/3 6 pythonmalloc-environment-variable482890
Ref: 507482890
Ref: whatsnew/3 6 whatsnew36-pythonmalloc482890
Ref: 4d1482890
Ref: PYTHONMALLOC environment variable-Footnote-1486073
Ref: PYTHONMALLOC environment variable-Footnote-2486116
Node: DTrace and SystemTap probing support486159
Ref: whatsnew/3 6 dtrace-and-systemtap-probing-support486289
Ref: 510486289
Ref: whatsnew/3 6 whatsnew36-tracing486289
Ref: 4d0486289
Ref: DTrace and SystemTap probing support-Footnote-1487120
Node: Other Language Changes<3>487163
Ref: whatsnew/3 6 other-language-changes487296
Ref: 512487296
Ref: Other Language Changes<3>-Footnote-1488681
Ref: Other Language Changes<3>-Footnote-2488724
Ref: Other Language Changes<3>-Footnote-3488767
Ref: Other Language Changes<3>-Footnote-4488810
Node: New Modules<3>488853
Ref: whatsnew/3 6 new-modules488990
Ref: 516488990
Node: secrets489049
Ref: whatsnew/3 6 secrets489107
Ref: 517489107
Ref: whatsnew/3 6 whatsnew36-pep506489107
Ref: 4cb489107
Ref: secrets-Footnote-1489788
Node: Improved Modules<3>489837
Ref: whatsnew/3 6 improved-modules489965
Ref: 518489965
Node: array491346
Ref: whatsnew/3 6 array491422
Ref: 519491422
Ref: array-Footnote-1491715
Node: ast<2>491758
Ref: whatsnew/3 6 ast491853
Ref: 51a491853
Ref: ast<2>-Footnote-1492096
Node: asyncio<4>492139
Ref: whatsnew/3 6 asyncio492240
Ref: 51b492240
Ref: asyncio<4>-Footnote-1495580
Ref: asyncio<4>-Footnote-2495623
Ref: asyncio<4>-Footnote-3495668
Ref: asyncio<4>-Footnote-4495711
Ref: asyncio<4>-Footnote-5495754
Ref: asyncio<4>-Footnote-6495797
Ref: asyncio<4>-Footnote-7495840
Ref: asyncio<4>-Footnote-8495883
Ref: asyncio<4>-Footnote-9495926
Ref: asyncio<4>-Footnote-10495969
Ref: asyncio<4>-Footnote-11496013
Ref: asyncio<4>-Footnote-12496057
Node: binascii<2>496101
Ref: whatsnew/3 6 binascii496201
Ref: 527496201
Ref: binascii<2>-Footnote-1496486
Node: cmath496529
Ref: whatsnew/3 6 cmath496633
Ref: 529496633
Ref: cmath-Footnote-1497104
Ref: cmath-Footnote-2497147
Ref: cmath-Footnote-3497196
Node: collections<4>497239
Ref: whatsnew/3 6 collections497353
Ref: 531497353
Ref: collections<4>-Footnote-1498454
Ref: collections<4>-Footnote-2498497
Ref: collections<4>-Footnote-3498540
Ref: collections<4>-Footnote-4498583
Ref: collections<4>-Footnote-5498626
Ref: collections<4>-Footnote-6498669
Node: concurrent futures<2>498712
Ref: whatsnew/3 6 concurrent-futures498834
Ref: 537498834
Ref: concurrent futures<2>-Footnote-1499164
Node: contextlib<2>499207
Ref: whatsnew/3 6 contextlib499326
Ref: 538499326
Ref: contextlib<2>-Footnote-1499822
Node: datetime<3>499865
Ref: whatsnew/3 6 datetime499973
Ref: 53b499973
Ref: datetime<3>-Footnote-1500990
Ref: datetime<3>-Footnote-2501033
Ref: datetime<3>-Footnote-3501076
Ref: datetime<3>-Footnote-4501119
Node: decimal<2>501162
Ref: whatsnew/3 6 decimal501269
Ref: 53f501269
Ref: decimal<2>-Footnote-1501682
Node: distutils<2>501725
Ref: whatsnew/3 6 distutils501826
Ref: 541501826
Ref: distutils<2>-Footnote-1502200
Node: email502243
Ref: whatsnew/3 6 email502343
Ref: 542502343
Ref: email-Footnote-1503259
Ref: email-Footnote-2503302
Ref: email-Footnote-3503345
Node: encodings503388
Ref: whatsnew/3 6 encodings503483
Ref: 548503483
Ref: encodings-Footnote-1503778
Node: enum<3>503821
Ref: whatsnew/3 6 enum503923
Ref: 549503923
Ref: enum<3>-Footnote-1504671
Node: faulthandler504714
Ref: whatsnew/3 6 faulthandler504816
Ref: 54c504816
Ref: faulthandler-Footnote-1505079
Node: fileinput505122
Ref: whatsnew/3 6 fileinput505224
Ref: 54e505224
Ref: fileinput-Footnote-1505412
Node: hashlib505455
Ref: whatsnew/3 6 hashlib505559
Ref: 550505559
Ref: hashlib-Footnote-1506577
Ref: hashlib-Footnote-2506620
Ref: hashlib-Footnote-3506663
Ref: hashlib-Footnote-4506706
Node: http client<2>506749
Ref: whatsnew/3 6 http-client506863
Ref: 553506863
Ref: http client<2>-Footnote-1507123
Node: idlelib and IDLE<2>507166
Ref: whatsnew/3 6 idlelib-and-idle507285
Ref: 556507285
Ref: idlelib and IDLE<2>-Footnote-1510759
Ref: idlelib and IDLE<2>-Footnote-2510802
Ref: idlelib and IDLE<2>-Footnote-3510845
Ref: idlelib and IDLE<2>-Footnote-4510890
Ref: idlelib and IDLE<2>-Footnote-5510933
Ref: idlelib and IDLE<2>-Footnote-6510976
Ref: idlelib and IDLE<2>-Footnote-7511019
Ref: idlelib and IDLE<2>-Footnote-8511062
Ref: idlelib and IDLE<2>-Footnote-9511105
Ref: idlelib and IDLE<2>-Footnote-10511148
Ref: idlelib and IDLE<2>-Footnote-11511192
Node: importlib<3>511238
Ref: whatsnew/3 6 importlib511353
Ref: 557511353
Ref: importlib<3>-Footnote-1512180
Node: inspect<2>512223
Ref: whatsnew/3 6 inspect512323
Ref: 55f512323
Ref: inspect<2>-Footnote-1513104
Ref: inspect<2>-Footnote-2513147
Node: json513190
Ref: whatsnew/3 6 json513288
Ref: 563513288
Ref: json-Footnote-1513560
Node: logging<3>513603
Ref: whatsnew/3 6 logging513698
Ref: 566513698
Ref: logging<3>-Footnote-1513962
Node: math<3>514005
Ref: whatsnew/3 6 math514114
Ref: 568514114
Ref: math<3>-Footnote-1514346
Ref: math<3>-Footnote-2514389
Node: multiprocessing<3>514438
Ref: whatsnew/3 6 multiprocessing514542
Ref: 569514542
Ref: multiprocessing<3>-Footnote-1514765
Node: os<3>514807
Ref: whatsnew/3 6 os514914
Ref: 56b514914
Ref: os<3>-Footnote-1515914
Ref: os<3>-Footnote-2515957
Ref: os<3>-Footnote-3516006
Node: pathlib<3>516055
Ref: whatsnew/3 6 pathlib516150
Ref: 56f516150
Ref: pathlib<3>-Footnote-1516384
Node: pdb<2>516427
Ref: whatsnew/3 6 pdb516526
Ref: 570516526
Node: pickle<2>516683
Ref: whatsnew/3 6 pickle516783
Ref: 572516783
Ref: pickle<2>-Footnote-1517100
Node: pickletools517143
Ref: whatsnew/3 6 pickletools517245
Ref: 574517245
Ref: pickletools-Footnote-1517473
Node: pydoc<2>517516
Ref: whatsnew/3 6 pydoc517615
Ref: 576517615
Ref: pydoc<2>-Footnote-1518009
Ref: pydoc<2>-Footnote-2518051
Node: random518094
Ref: whatsnew/3 6 random518187
Ref: 578518187
Ref: random-Footnote-1518442
Node: re<2>518485
Ref: whatsnew/3 6 re518578
Ref: 57a518578
Ref: re<2>-Footnote-1519283
Ref: re<2>-Footnote-2519327
Ref: re<2>-Footnote-3519370
Node: readline519413
Ref: whatsnew/3 6 readline519511
Ref: 57b519511
Ref: readline-Footnote-1519742
Node: rlcompleter519785
Ref: whatsnew/3 6 rlcompleter519886
Ref: 57d519886
Ref: rlcompleter-Footnote-1520190
Ref: rlcompleter-Footnote-2520233
Node: shlex<2>520276
Ref: whatsnew/3 6 shlex520373
Ref: 57e520373
Ref: shlex<2>-Footnote-1520663
Node: site520708
Ref: whatsnew/3 6 site520804
Ref: 581520804
Ref: site-Footnote-1521068
Node: sqlite3<2>521111
Ref: whatsnew/3 6 sqlite3521208
Ref: 582521208
Ref: sqlite3<2>-Footnote-1521411
Node: socket<4>521454
Ref: whatsnew/3 6 socket521562
Ref: 584521562
Ref: socket<4>-Footnote-1522524
Ref: socket<4>-Footnote-2522567
Ref: socket<4>-Footnote-3522610
Ref: socket<4>-Footnote-4522653
Node: socketserver<2>522696
Ref: whatsnew/3 6 socketserver522800
Ref: 58b522800
Ref: socketserver<2>-Footnote-1523429
Ref: socketserver<2>-Footnote-2523472
Node: ssl<4>523515
Ref: whatsnew/3 6 ssl523623
Ref: 58f523623
Ref: ssl<4>-Footnote-1524819
Ref: ssl<4>-Footnote-2524862
Ref: ssl<4>-Footnote-3524905
Ref: ssl<4>-Footnote-4524948
Ref: ssl<4>-Footnote-5524991
Ref: ssl<4>-Footnote-6525034
Ref: ssl<4>-Footnote-7525077
Node: statistics<2>525120
Ref: whatsnew/3 6 statistics525219
Ref: 593525219
Ref: statistics<2>-Footnote-1525409
Node: struct525452
Ref: whatsnew/3 6 struct525558
Ref: 595525558
Ref: struct-Footnote-1525789
Node: subprocess<2>525832
Ref: whatsnew/3 6 subprocess525931
Ref: 596525931
Ref: subprocess<2>-Footnote-1526624
Ref: subprocess<2>-Footnote-2526667
Node: sys<4>526709
Ref: whatsnew/3 6 sys526811
Ref: 598526811
Ref: sys<4>-Footnote-1527412
Ref: sys<4>-Footnote-2527455
Node: telnetlib527498
Ref: whatsnew/3 6 telnetlib527594
Ref: 59b527594
Ref: telnetlib-Footnote-1527765
Node: time<3>527808
Ref: whatsnew/3 6 time527904
Ref: 59d527904
Node: timeit528043
Ref: whatsnew/3 6 timeit528140
Ref: 59f528140
Ref: timeit-Footnote-1528600
Ref: timeit-Footnote-2528642
Node: tkinter<3>528685
Ref: whatsnew/3 6 tkinter528784
Ref: 5a2528784
Ref: tkinter<3>-Footnote-1529210
Node: traceback529253
Ref: whatsnew/3 6 traceback529360
Ref: 5a3529360
Ref: whatsnew/3 6 whatsnew36-traceback529360
Ref: 515529360
Ref: traceback-Footnote-1529995
Node: tracemalloc<2>530038
Ref: whatsnew/3 6 tracemalloc530144
Ref: 5a4530144
Ref: tracemalloc<2>-Footnote-1530505
Node: typing<2>530548
Ref: whatsnew/3 6 typing530659
Ref: 5a6530659
Ref: whatsnew/3 6 whatsnew36-typing530659
Ref: 4d4530659
Ref: typing<2>-Footnote-1532311
Ref: typing<2>-Footnote-2532361
Ref: typing<2>-Footnote-3532404
Ref: typing<2>-Footnote-4532447
Ref: typing<2>-Footnote-5532496
Ref: typing<2>-Footnote-6532546
Ref: typing<2>-Footnote-7532598
Node: unicodedata<3>532650
Ref: whatsnew/3 6 unicodedata532763
Ref: 5ab532763
Ref: unicodedata<3>-Footnote-1532951
Node: unittest mock<2>533001
Ref: whatsnew/3 6 unittest-mock533119
Ref: 5ac533119
Ref: unittest mock<2>-Footnote-1533636
Ref: unittest mock<2>-Footnote-2533679
Node: urllib request533722
Ref: whatsnew/3 6 urllib-request533844
Ref: 5b0533844
Ref: urllib request-Footnote-1534209
Node: urllib robotparser534252
Ref: whatsnew/3 6 urllib-robotparser534365
Ref: 5b1534365
Ref: urllib robotparser-Footnote-1534610
Node: venv<2>534653
Ref: whatsnew/3 6 venv534763
Ref: 5b3534763
Ref: venv<2>-Footnote-1535050
Node: warnings<2>535093
Ref: whatsnew/3 6 warnings535191
Ref: 5b4535191
Ref: warnings<2>-Footnote-1536462
Ref: warnings<2>-Footnote-2536505
Node: winreg536548
Ref: whatsnew/3 6 winreg536647
Ref: 5b6536647
Ref: winreg-Footnote-1536820
Node: winsound536863
Ref: whatsnew/3 6 winsound536964
Ref: 5b8536964
Ref: winsound-Footnote-1537163
Node: xmlrpc client537206
Ref: whatsnew/3 6 xmlrpc-client537311
Ref: 5bc537311
Ref: xmlrpc client-Footnote-1537604
Node: zipfile<2>537647
Ref: whatsnew/3 6 zipfile537748
Ref: 5bd537748
Ref: zipfile<2>-Footnote-1538282
Ref: zipfile<2>-Footnote-2538325
Node: zlib538368
Ref: whatsnew/3 6 zlib538447
Ref: 5c2538447
Ref: zlib-Footnote-1538703
Ref: zlib-Footnote-2538746
Node: Optimizations<3>538789
Ref: whatsnew/3 6 optimizations538929
Ref: 5c5538929
Ref: Optimizations<3>-Footnote-1542798
Ref: Optimizations<3>-Footnote-2542841
Ref: Optimizations<3>-Footnote-3542884
Ref: Optimizations<3>-Footnote-4542927
Ref: Optimizations<3>-Footnote-5542970
Ref: Optimizations<3>-Footnote-6543013
Ref: Optimizations<3>-Footnote-7543056
Ref: Optimizations<3>-Footnote-8543099
Ref: Optimizations<3>-Footnote-9543142
Ref: Optimizations<3>-Footnote-10543185
Ref: Optimizations<3>-Footnote-11543229
Ref: Optimizations<3>-Footnote-12543273
Ref: Optimizations<3>-Footnote-13543317
Ref: Optimizations<3>-Footnote-14543361
Ref: Optimizations<3>-Footnote-15543405
Ref: Optimizations<3>-Footnote-16543449
Ref: Optimizations<3>-Footnote-17543493
Ref: Optimizations<3>-Footnote-18543537
Ref: Optimizations<3>-Footnote-19543581
Ref: Optimizations<3>-Footnote-20543625
Ref: Optimizations<3>-Footnote-21543669
Node: Build and C API Changes<2>543713
Ref: whatsnew/3 6 build-and-c-api-changes543852
Ref: 5cd543852
Ref: Build and C API Changes<2>-Footnote-1546305
Ref: Build and C API Changes<2>-Footnote-2546354
Ref: Build and C API Changes<2>-Footnote-3546397
Ref: Build and C API Changes<2>-Footnote-4546440
Ref: Build and C API Changes<2>-Footnote-5546483
Ref: Build and C API Changes<2>-Footnote-6546525
Ref: Build and C API Changes<2>-Footnote-7546568
Ref: Build and C API Changes<2>-Footnote-8546611
Ref: Build and C API Changes<2>-Footnote-9546654
Ref: Build and C API Changes<2>-Footnote-10546697
Node: Other Improvements546741
Ref: whatsnew/3 6 other-improvements546877
Ref: 5d5546877
Node: Deprecated<2>547248
Ref: whatsnew/3 6 deprecated547365
Ref: 5d9547365
Node: New Keywords547686
Ref: whatsnew/3 6 new-keywords547783
Ref: 5da547783
Ref: New Keywords-Footnote-1548176
Node: Deprecated Python behavior548225
Ref: whatsnew/3 6 deprecated-python-behavior548381
Ref: 5db548381
Ref: Deprecated Python behavior-Footnote-1549588
Ref: Deprecated Python behavior-Footnote-2549631
Ref: Deprecated Python behavior-Footnote-3549674
Node: Deprecated Python modules functions and methods<2>549717
Ref: whatsnew/3 6 deprecated-python-modules-functions-and-methods549907
Ref: 5de549907
Node: asynchat550216
Ref: whatsnew/3 6 asynchat550328
Ref: 5df550328
Ref: asynchat-Footnote-1550516
Node: asyncore550559
Ref: whatsnew/3 6 asyncore550686
Ref: 5e0550686
Ref: asyncore-Footnote-1550874
Node: dbm<3>550917
Ref: whatsnew/3 6 dbm551048
Ref: 5e1551048
Ref: dbm<3>-Footnote-1551408
Node: distutils<3>551451
Ref: whatsnew/3 6 id2551577
Ref: 5e2551577
Ref: distutils<3>-Footnote-1551897
Node: grp551940
Ref: whatsnew/3 6 grp552072
Ref: 5e3552072
Ref: grp-Footnote-1552270
Node: importlib<4>552313
Ref: whatsnew/3 6 id3552438
Ref: 5e5552438
Node: os<4>553092
Ref: whatsnew/3 6 id4553219
Ref: 5ec553219
Ref: os<4>-Footnote-1553513
Ref: os<4>-Footnote-2553556
Node: re<3>553599
Ref: whatsnew/3 6 id5553720
Ref: 5ee553720
Ref: re<3>-Footnote-1554046
Node: ssl<5>554089
Ref: whatsnew/3 6 id6554215
Ref: 5ef554215
Ref: ssl<5>-Footnote-1555010
Ref: ssl<5>-Footnote-2555053
Ref: ssl<5>-Footnote-3555096
Node: tkinter<4>555139
Ref: whatsnew/3 6 id7555267
Ref: 5f0555267
Node: venv<3>555428
Ref: whatsnew/3 6 id8555541
Ref: 5f1555541
Ref: venv<3>-Footnote-1555892
Node: Deprecated functions and types of the C API<2>555935
Ref: whatsnew/3 6 deprecated-functions-and-types-of-the-c-api556123
Ref: 5f2556123
Node: Deprecated Build Options556472
Ref: whatsnew/3 6 deprecated-build-options556601
Ref: 5f4556601
Node: Removed557042
Ref: whatsnew/3 6 removed557162
Ref: 5f5557162
Node: API and Feature Removals<3>557260
Ref: whatsnew/3 6 api-and-feature-removals557331
Ref: 5f6557331
Ref: API and Feature Removals<3>-Footnote-1559423
Ref: API and Feature Removals<3>-Footnote-2559466
Node: Porting to Python 3 6559539
Ref: whatsnew/3 6 porting-to-python-3-6559677
Ref: 5fa559677
Node: Changes in 'python' Command Behavior560059
Ref: whatsnew/3 6 changes-in-python-command-behavior560190
Ref: 5fb560190
Ref: Changes in 'python' Command Behavior-Footnote-1560670
Node: Changes in the Python API<3>560713
Ref: whatsnew/3 6 changes-in-the-python-api560876
Ref: 5fc560876
Ref: Changes in the Python API<3>-Footnote-1570999
Ref: Changes in the Python API<3>-Footnote-2571041
Ref: Changes in the Python API<3>-Footnote-3571090
Ref: Changes in the Python API<3>-Footnote-4571133
Ref: Changes in the Python API<3>-Footnote-5571176
Ref: Changes in the Python API<3>-Footnote-6571219
Ref: Changes in the Python API<3>-Footnote-7571262
Ref: Changes in the Python API<3>-Footnote-8571305
Ref: Changes in the Python API<3>-Footnote-9571348
Ref: Changes in the Python API<3>-Footnote-10571391
Ref: Changes in the Python API<3>-Footnote-11571435
Ref: Changes in the Python API<3>-Footnote-12571485
Ref: Changes in the Python API<3>-Footnote-13571529
Ref: Changes in the Python API<3>-Footnote-14571573
Ref: Changes in the Python API<3>-Footnote-15571617
Ref: Changes in the Python API<3>-Footnote-16571661
Ref: Changes in the Python API<3>-Footnote-17571704
Ref: Changes in the Python API<3>-Footnote-18571748
Ref: Changes in the Python API<3>-Footnote-19571792
Ref: Changes in the Python API<3>-Footnote-20571836
Node: Changes in the C API<3>571880
Ref: whatsnew/3 6 changes-in-the-c-api572034
Ref: 616572034
Ref: Changes in the C API<3>-Footnote-1572688
Ref: Changes in the C API<3>-Footnote-2572731
Node: CPython bytecode changes<3>572773
Ref: whatsnew/3 6 cpython-bytecode-changes572890
Ref: 618572890
Ref: CPython bytecode changes<3>-Footnote-1574546
Ref: CPython bytecode changes<3>-Footnote-2574589
Ref: CPython bytecode changes<3>-Footnote-3574632
Ref: CPython bytecode changes<3>-Footnote-4574675
Ref: CPython bytecode changes<3>-Footnote-5574718
Ref: CPython bytecode changes<3>-Footnote-6574761
Ref: CPython bytecode changes<3>-Footnote-7574804
Ref: CPython bytecode changes<3>-Footnote-8574847
Ref: CPython bytecode changes<3>-Footnote-9574890
Node: Notable changes in Python 3 6 2574933
Ref: whatsnew/3 6 notable-changes-in-python-3-6-2575095
Ref: 625575095
Node: New make regen-all build target575259
Ref: whatsnew/3 6 new-make-regen-all-build-target575401
Ref: 626575401
Ref: New make regen-all build target-Footnote-1576186
Ref: New make regen-all build target-Footnote-2576253
Node: Removal of make touch build target576296
Ref: whatsnew/3 6 removal-of-make-touch-build-target576438
Ref: 627576438
Ref: Removal of make touch build target-Footnote-1576859
Node: Notable changes in Python 3 6 4576902
Ref: whatsnew/3 6 notable-changes-in-python-3-6-4577074
Ref: 628577074
Ref: Notable changes in Python 3 6 4-Footnote-1577447
Ref: Notable changes in Python 3 6 4-Footnote-2577490
Node: Notable changes in Python 3 6 5577533
Ref: whatsnew/3 6 notable-changes-in-python-3-6-5577705
Ref: 629577705
Ref: Notable changes in Python 3 6 5-Footnote-1578008
Node: Notable changes in Python 3 6 7578051
Ref: whatsnew/3 6 notable-changes-in-python-3-6-7578224
Ref: 62a578224
Ref: Notable changes in Python 3 6 7-Footnote-1578601
Node: Notable changes in Python 3 6 10578644
Ref: whatsnew/3 6 notable-changes-in-python-3-6-10578818
Ref: 62b578818
Ref: Notable changes in Python 3 6 10-Footnote-1579331
Node: Notable changes in Python 3 6 13579374
Ref: whatsnew/3 6 notable-changes-in-python-3-6-13579508
Ref: 62c579508
Ref: Notable changes in Python 3 6 13-Footnote-1580240
Node: Python 3 5 有什麼新功能580283
Ref: whatsnew/3 5 doc580443
Ref: 62d580443
Ref: whatsnew/3 5 what-s-new-in-python-3-5580443
Ref: 62e580443
Ref: Python 3 5 有什麼新功能-Footnote-1581378
Ref: Python 3 5 有什麼新功能-Footnote-2581438
Node: Summary -- Release highlights<3>581487
Ref: whatsnew/3 5 summary-release-highlights581609
Ref: 62f581609
Ref: Summary -- Release highlights<3>-Footnote-1585343
Ref: Summary -- Release highlights<3>-Footnote-2585385
Ref: Summary -- Release highlights<3>-Footnote-3585428
Ref: Summary -- Release highlights<3>-Footnote-4585471
Ref: Summary -- Release highlights<3>-Footnote-5585514
Ref: Summary -- Release highlights<3>-Footnote-6585557
Ref: Summary -- Release highlights<3>-Footnote-7585600
Node: New Features<4>585643
Ref: whatsnew/3 5 new-features585799
Ref: 642585799
Node: PEP 492 - Coroutines with async and await syntax586890
Ref: whatsnew/3 5 pep-492-coroutines-with-async-and-await-syntax587061
Ref: 643587061
Ref: whatsnew/3 5 whatsnew-pep-492587061
Ref: 630587061
Ref: PEP 492 - Coroutines with async and await syntax-Footnote-1590132
Ref: PEP 492 - Coroutines with async and await syntax-Footnote-2590181
Node: PEP 465 - A dedicated infix operator for matrix multiplication590230
Ref: whatsnew/3 5 pep-465-a-dedicated-infix-operator-for-matrix-multiplication590456
Ref: 64c590456
Ref: whatsnew/3 5 whatsnew-pep-465590456
Ref: 631590456
Ref: PEP 465 - A dedicated infix operator for matrix multiplication-Footnote-1591858
Ref: PEP 465 - A dedicated infix operator for matrix multiplication-Footnote-2591907
Node: PEP 448 - Additional Unpacking Generalizations591956
Ref: whatsnew/3 5 pep-448-additional-unpacking-generalizations592194
Ref: 650592194
Ref: whatsnew/3 5 whatsnew-pep-448592194
Ref: 632592194
Ref: PEP 448 - Additional Unpacking Generalizations-Footnote-1593286
Ref: PEP 448 - Additional Unpacking Generalizations-Footnote-2593335
Node: PEP 461 - percent formatting support for bytes and bytearray593384
Ref: whatsnew/3 5 pep-461-percent-formatting-support-for-bytes-and-bytearray593580
Ref: 654593580
Ref: whatsnew/3 5 whatsnew-pep-461593580
Ref: 635593580
Ref: PEP 461 - percent formatting support for bytes and bytearray-Footnote-1595115
Ref: PEP 461 - percent formatting support for bytes and bytearray-Footnote-2595164
Node: PEP 484 - Type Hints595213
Ref: whatsnew/3 5 pep-484-type-hints595434
Ref: 656595434
Ref: whatsnew/3 5 whatsnew-pep-484595434
Ref: 633595434
Ref: PEP 484 - Type Hints-Footnote-1597080
Ref: PEP 484 - Type Hints-Footnote-2597129
Ref: PEP 484 - Type Hints-Footnote-3597178
Ref: PEP 484 - Type Hints-Footnote-4597207
Ref: PEP 484 - Type Hints-Footnote-5597256
Node: PEP 471 - os scandir function -- a better and faster directory iterator597305
Ref: whatsnew/3 5 pep-471-os-scandir-function-a-better-and-faster-directory-iterator597511
Ref: 658597511
Ref: whatsnew/3 5 whatsnew-pep-471597511
Ref: 63e597511
Ref: PEP 471 - os scandir function -- a better and faster directory iterator-Footnote-1598866
Ref: PEP 471 - os scandir function -- a better and faster directory iterator-Footnote-2598915
Node: PEP 475 Retry system calls failing with EINTR598964
Ref: whatsnew/3 5 pep-475-retry-system-calls-failing-with-eintr599205
Ref: 65b599205
Ref: whatsnew/3 5 whatsnew-pep-475599205
Ref: 65c599205
Ref: PEP 475 Retry system calls failing with EINTR-Footnote-1602268
Ref: PEP 475 Retry system calls failing with EINTR-Footnote-2602317
Node: PEP 479 Change StopIteration handling inside generators602366
Ref: whatsnew/3 5 pep-479-change-stopiteration-handling-inside-generators602587
Ref: 686602587
Ref: whatsnew/3 5 whatsnew-pep-479602587
Ref: 5dc602587
Ref: PEP 479 Change StopIteration handling inside generators-Footnote-1604516
Ref: PEP 479 Change StopIteration handling inside generators-Footnote-2604565
Node: PEP 485 A function for testing approximate equality604614
Ref: whatsnew/3 5 pep-485-a-function-for-testing-approximate-equality604852
Ref: 689604852
Ref: whatsnew/3 5 whatsnew-pep-485604852
Ref: 68a604852
Ref: PEP 485 A function for testing approximate equality-Footnote-1606030
Ref: PEP 485 A function for testing approximate equality-Footnote-2606079
Node: PEP 486 Make the Python Launcher aware of virtual environments606128
Ref: whatsnew/3 5 pep-486-make-the-python-launcher-aware-of-virtual-environments606343
Ref: 68d606343
Ref: whatsnew/3 5 whatsnew-pep-486606343
Ref: 68e606343
Ref: PEP 486 Make the Python Launcher aware of virtual environments-Footnote-1606916
Ref: PEP 486 Make the Python Launcher aware of virtual environments-Footnote-2606965
Ref: PEP 486 Make the Python Launcher aware of virtual environments-Footnote-3607014
Node: PEP 488 Elimination of PYO files607063
Ref: whatsnew/3 5 pep-488-elimination-of-pyo-files607278
Ref: 68f607278
Ref: whatsnew/3 5 whatsnew-pep-488607278
Ref: 63a607278
Ref: PEP 488 Elimination of PYO files-Footnote-1608143
Ref: PEP 488 Elimination of PYO files-Footnote-2608192
Node: PEP 489 Multi-phase extension module initialization608241
Ref: whatsnew/3 5 pep-489-multi-phase-extension-module-initialization608385
Ref: 692608385
Ref: whatsnew/3 5 whatsnew-pep-489608385
Ref: 63b608385
Ref: PEP 489 Multi-phase extension module initialization-Footnote-1609147
Ref: PEP 489 Multi-phase extension module initialization-Footnote-2609196
Ref: PEP 489 Multi-phase extension module initialization-Footnote-3609245
Node: Other Language Changes<4>609294
Ref: whatsnew/3 5 other-language-changes609432
Ref: 693609432
Ref: Other Language Changes<4>-Footnote-1610430
Ref: Other Language Changes<4>-Footnote-2610473
Ref: Other Language Changes<4>-Footnote-3610516
Ref: Other Language Changes<4>-Footnote-4610559
Ref: Other Language Changes<4>-Footnote-5610602
Ref: Other Language Changes<4>-Footnote-6610645
Ref: Other Language Changes<4>-Footnote-7610688
Node: New Modules<4>610731
Ref: whatsnew/3 5 new-modules610873
Ref: 695610873
Node: typing<3>610962
Ref: whatsnew/3 5 typing611040
Ref: 696611040
Node: zipapp<2>611251
Ref: whatsnew/3 5 whatsnew-zipapp611329
Ref: 634611329
Ref: whatsnew/3 5 zipapp611329
Ref: 697611329
Ref: zipapp<2>-Footnote-1612038
Ref: zipapp<2>-Footnote-2612087
Ref: zipapp<2>-Footnote-3612132
Ref: zipapp<2>-Footnote-4612175
Node: Improved Modules<4>612224
Ref: whatsnew/3 5 improved-modules612367
Ref: 698612367
Node: argparse<2>613931
Ref: whatsnew/3 5 argparse614017
Ref: 699614017
Ref: argparse<2>-Footnote-1614340
Node: asyncio<5>614383
Ref: whatsnew/3 5 asyncio614481
Ref: 69d614481
Ref: asyncio<5>-Footnote-1617959
Ref: asyncio<5>-Footnote-2618002
Ref: asyncio<5>-Footnote-3618045
Node: bz2618090
Ref: whatsnew/3 5 bz2618180
Ref: 6a7618180
Ref: bz2-Footnote-1618435
Node: cgi618478
Ref: whatsnew/3 5 cgi618566
Ref: 6a9618566
Ref: cgi-Footnote-1618761
Node: cmath<2>618804
Ref: whatsnew/3 5 cmath618893
Ref: 6aa618893
Ref: cmath<2>-Footnote-1619107
Node: code619150
Ref: whatsnew/3 5 code619250
Ref: 6ab619250
Ref: code-Footnote-1619501
Node: collections<5>619544
Ref: whatsnew/3 5 collections619651
Ref: 6ad619651
Ref: whatsnew/3 5 whatsnew-ordereddict619692
Ref: 63c619692
Ref: collections<5>-Footnote-1620971
Ref: collections<5>-Footnote-2621014
Ref: collections<5>-Footnote-3621057
Ref: collections<5>-Footnote-4621100
Ref: collections<5>-Footnote-5621143
Node: collections abc621186
Ref: whatsnew/3 5 collections-abc621302
Ref: 6b9621302
Ref: collections abc-Footnote-1621972
Ref: collections abc-Footnote-2622015
Ref: collections abc-Footnote-3622058
Ref: collections abc-Footnote-4622101
Node: compileall<2>622148
Ref: whatsnew/3 5 compileall622271
Ref: 6bf622271
Ref: compileall<2>-Footnote-1623148
Ref: compileall<2>-Footnote-2623191
Ref: compileall<2>-Footnote-3623234
Node: concurrent futures<3>623277
Ref: whatsnew/3 5 concurrent-futures623397
Ref: 6c2623397
Ref: concurrent futures<3>-Footnote-1623899
Ref: concurrent futures<3>-Footnote-2623942
Node: configparser623985
Ref: whatsnew/3 5 configparser624105
Ref: 6c4624105
Ref: configparser-Footnote-1625056
Node: contextlib<3>625099
Ref: whatsnew/3 5 contextlib625204
Ref: 6c5625204
Ref: contextlib<3>-Footnote-1625814
Node: csv<2>625857
Ref: whatsnew/3 5 csv625959
Ref: 6c8625959
Ref: csv<2>-Footnote-1626163
Node: curses<2>626206
Ref: whatsnew/3 5 curses626301
Ref: 6ca626301
Ref: curses<2>-Footnote-1626582
Node: dbm<4>626624
Ref: whatsnew/3 5 dbm626720
Ref: 6cc626720
Ref: dbm<4>-Footnote-1626923
Node: difflib626966
Ref: whatsnew/3 5 difflib627065
Ref: 6cd627065
Ref: difflib-Footnote-1627601
Ref: difflib-Footnote-2627643
Node: distutils<4>627686
Ref: whatsnew/3 5 distutils627786
Ref: 6d0627786
Ref: distutils<4>-Footnote-1628241
Ref: distutils<4>-Footnote-2628283
Node: doctest628326
Ref: whatsnew/3 5 doctest628427
Ref: 6d1628427
Ref: doctest-Footnote-1628712
Node: email<2>628755
Ref: whatsnew/3 5 email628851
Ref: 6d4628851
Ref: email<2>-Footnote-1629962
Ref: email<2>-Footnote-2630005
Ref: email<2>-Footnote-3630048
Ref: email<2>-Footnote-4630097
Ref: email<2>-Footnote-5630146
Ref: email<2>-Footnote-6630189
Node: enum<4>630232
Ref: whatsnew/3 5 enum630336
Ref: 6da630336
Ref: enum<4>-Footnote-1630727
Node: faulthandler<2>630770
Ref: whatsnew/3 5 faulthandler630878
Ref: 6db630878
Ref: faulthandler<2>-Footnote-1631190
Node: functools<3>631233
Ref: whatsnew/3 5 functools631338
Ref: 6df631338
Ref: whatsnew/3 5 whatsnew-lrucache631377
Ref: 63f631377
Ref: functools<3>-Footnote-1631603
Node: glob631646
Ref: whatsnew/3 5 glob631743
Ref: 6e0631743
Ref: glob-Footnote-1631995
Node: gzip<2>632038
Ref: whatsnew/3 5 gzip632128
Ref: 6e1632128
Ref: gzip<2>-Footnote-1632353
Node: heapq632396
Ref: whatsnew/3 5 heapq632486
Ref: 6e3632486
Ref: heapq-Footnote-1633126
Node: http633169
Ref: whatsnew/3 5 http633266
Ref: 6e6633266
Ref: http-Footnote-1633512
Node: http client<3>633555
Ref: whatsnew/3 5 http-client633666
Ref: 6e8633666
Ref: http client<3>-Footnote-1634410
Node: idlelib and IDLE<3>634452
Ref: whatsnew/3 5 idlelib-and-idle634566
Ref: 6ec634566
Node: imaplib634960
Ref: whatsnew/3 5 imaplib635066
Ref: 6ed635066
Ref: imaplib-Footnote-1635945
Ref: imaplib-Footnote-2635987
Ref: imaplib-Footnote-3636036
Ref: imaplib-Footnote-4636085
Ref: imaplib-Footnote-5636134
Ref: imaplib-Footnote-6636177
Node: imghdr636220
Ref: whatsnew/3 5 imghdr636319
Ref: 6f1636319
Ref: imghdr-Footnote-1636613
Ref: imghdr-Footnote-2636644
Ref: imghdr-Footnote-3636687
Ref: imghdr-Footnote-4636730
Node: importlib<5>636773
Ref: whatsnew/3 5 importlib636875
Ref: 6f3636875
Ref: importlib<5>-Footnote-1637710
Ref: importlib<5>-Footnote-2637753
Ref: importlib<5>-Footnote-3637796
Node: inspect<3>637839
Ref: whatsnew/3 5 inspect637940
Ref: 6f7637940
Ref: inspect<3>-Footnote-1639497
Ref: inspect<3>-Footnote-2639540
Ref: inspect<3>-Footnote-3639583
Ref: inspect<3>-Footnote-4639626
Ref: inspect<3>-Footnote-5639669
Ref: inspect<3>-Footnote-6639712
Ref: inspect<3>-Footnote-7639755
Ref: inspect<3>-Footnote-8639798
Node: io<3>639841
Ref: whatsnew/3 5 io639942
Ref: 705639942
Ref: io<3>-Footnote-1640240
Node: ipaddress<2>640283
Ref: whatsnew/3 5 ipaddress640381
Ref: 709640381
Ref: ipaddress<2>-Footnote-1641409
Ref: ipaddress<2>-Footnote-2641452
Node: json<2>641495
Ref: whatsnew/3 5 json641597
Ref: 70a641597
Ref: json<2>-Footnote-1642097
Ref: json<2>-Footnote-2642140
Node: linecache642183
Ref: whatsnew/3 5 linecache642282
Ref: 70c642282
Ref: linecache-Footnote-1642692
Node: locale<3>642735
Ref: whatsnew/3 5 locale642837
Ref: 70f642837
Ref: locale<3>-Footnote-1643402
Node: logging<4>643445
Ref: whatsnew/3 5 logging643542
Ref: 711643542
Ref: logging<4>-Footnote-1644512
Ref: logging<4>-Footnote-2644555
Node: lzma644598
Ref: whatsnew/3 5 lzma644693
Ref: 718644693
Ref: lzma-Footnote-1644955
Node: math<4>644998
Ref: whatsnew/3 5 math645101
Ref: 71a645101
Ref: math<4>-Footnote-1645649
Ref: math<4>-Footnote-2645692
Ref: math<4>-Footnote-3645735
Node: multiprocessing<4>645778
Ref: whatsnew/3 5 multiprocessing645885
Ref: 71d645885
Ref: multiprocessing<4>-Footnote-1646135
Node: operator646178
Ref: whatsnew/3 5 operator646283
Ref: 71f646283
Ref: operator-Footnote-1646688
Ref: operator-Footnote-2646731
Node: os<5>646774
Ref: whatsnew/3 5 os646871
Ref: 724646871
Ref: os<5>-Footnote-1648719
Ref: os<5>-Footnote-2648762
Ref: os<5>-Footnote-3648805
Ref: os<5>-Footnote-4648848
Ref: os<5>-Footnote-5648891
Ref: os<5>-Footnote-6648934
Node: pathlib<4>648977
Ref: whatsnew/3 5 pathlib649075
Ref: 72c649075
Ref: pathlib<4>-Footnote-1650546
Ref: pathlib<4>-Footnote-2650589
Ref: pathlib<4>-Footnote-3650632
Ref: pathlib<4>-Footnote-4650675
Ref: pathlib<4>-Footnote-5650718
Node: pickle<3>650761
Ref: whatsnew/3 5 pickle650860
Ref: 735650860
Ref: pickle<3>-Footnote-1651176
Node: poplib651219
Ref: whatsnew/3 5 poplib651313
Ref: 736651313
Ref: poplib-Footnote-1651555
Ref: poplib-Footnote-2651604
Node: re<4>651647
Ref: whatsnew/3 5 re651743
Ref: 738651743
Ref: re<4>-Footnote-1652979
Ref: re<4>-Footnote-2653021
Ref: re<4>-Footnote-3653064
Ref: re<4>-Footnote-4653109
Node: readline<2>653152
Ref: whatsnew/3 5 readline653251
Ref: 740653251
Ref: readline<2>-Footnote-1653514
Node: selectors653557
Ref: whatsnew/3 5 selectors653660
Ref: 742653660
Ref: selectors-Footnote-1653882
Node: shutil<2>653925
Ref: whatsnew/3 5 shutil654026
Ref: 743654026
Ref: shutil<2>-Footnote-1654505
Ref: shutil<2>-Footnote-2654548
Node: signal<2>654590
Ref: whatsnew/3 5 signal654687
Ref: 744654687
Ref: signal<2>-Footnote-1655150
Ref: signal<2>-Footnote-2655193
Node: smtpd655236
Ref: whatsnew/3 5 smtpd655331
Ref: 745655331
Ref: smtpd-Footnote-1657015
Ref: smtpd-Footnote-2657058
Ref: smtpd-Footnote-3657107
Ref: smtpd-Footnote-4657150
Ref: smtpd-Footnote-5657199
Ref: smtpd-Footnote-6657242
Node: smtplib657285
Ref: whatsnew/3 5 smtplib657377
Ref: 746657377
Ref: smtplib-Footnote-1657998
Ref: smtplib-Footnote-2658041
Ref: smtplib-Footnote-3658084
Ref: smtplib-Footnote-4658133
Node: sndhdr658176
Ref: whatsnew/3 5 sndhdr658272
Ref: 74b658272
Ref: sndhdr-Footnote-1658487
Node: socket<5>658530
Ref: whatsnew/3 5 socket658625
Ref: 74e658625
Ref: socket<5>-Footnote-1659596
Ref: socket<5>-Footnote-2659639
Ref: socket<5>-Footnote-3659682
Ref: socket<5>-Footnote-4659725
Node: ssl<6>659768
Ref: whatsnew/3 5 ssl659867
Ref: 752659867
Node: Memory BIO Support659996
Ref: whatsnew/3 5 memory-bio-support660112
Ref: 753660112
Ref: whatsnew/3 5 whatsnew-sslmemorybio660112
Ref: 63d660112
Ref: Memory BIO Support-Footnote-1660991
Node: Application-Layer Protocol Negotiation Support661034
Ref: whatsnew/3 5 application-layer-protocol-negotiation-support661172
Ref: 755661172
Ref: Application-Layer Protocol Negotiation Support-Footnote-1661877
Ref: Application-Layer Protocol Negotiation Support-Footnote-2661920
Node: Other Changes661969
Ref: whatsnew/3 5 other-changes662080
Ref: 759662080
Ref: Other Changes-Footnote-1663673
Ref: Other Changes-Footnote-2663716
Ref: Other Changes-Footnote-3663759
Ref: Other Changes-Footnote-4663802
Ref: Other Changes-Footnote-5663851
Ref: Other Changes-Footnote-6663894
Ref: Other Changes-Footnote-7663937
Ref: Other Changes-Footnote-8663980
Node: sqlite3<3>664023
Ref: whatsnew/3 5 sqlite3664126
Ref: 762664126
Ref: sqlite3<3>-Footnote-1664455
Ref: sqlite3<3>-Footnote-2664498
Node: subprocess<3>664541
Ref: whatsnew/3 5 subprocess664644
Ref: 764664644
Ref: whatsnew/3 5 whatsnew-subprocess664644
Ref: 640664644
Ref: subprocess<3>-Footnote-1665658
Node: sys<5>665701
Ref: whatsnew/3 5 sys665803
Ref: 766665803
Ref: sys<5>-Footnote-1666453
Ref: sys<5>-Footnote-2666496
Node: sysconfig666539
Ref: whatsnew/3 5 sysconfig666638
Ref: 769666638
Ref: sysconfig-Footnote-1666871
Node: tarfile<2>666914
Ref: whatsnew/3 5 tarfile667019
Ref: 76a667019
Ref: tarfile<2>-Footnote-1667930
Ref: tarfile<2>-Footnote-2667973
Ref: tarfile<2>-Footnote-3668016
Node: threading<3>668059
Ref: whatsnew/3 5 threading668162
Ref: 770668162
Ref: threading<3>-Footnote-1668414
Node: time<4>668457
Ref: whatsnew/3 5 time668559
Ref: 773668559
Ref: time<4>-Footnote-1668736
Node: timeit<2>668779
Ref: whatsnew/3 5 timeit668879
Ref: 775668879
Ref: timeit<2>-Footnote-1669346
Ref: timeit<2>-Footnote-2669389
Node: tkinter<5>669431
Ref: whatsnew/3 5 tkinter669536
Ref: 777669536
Ref: tkinter<5>-Footnote-1669868
Node: traceback<2>669911
Ref: whatsnew/3 5 traceback670015
Ref: 778670015
Ref: whatsnew/3 5 whatsnew-traceback670015
Ref: 641670015
Ref: traceback<2>-Footnote-1670598
Ref: traceback<2>-Footnote-2670641
Ref: traceback<2>-Footnote-3670684
Node: types<2>670727
Ref: whatsnew/3 5 types670835
Ref: 780670835
Ref: types<2>-Footnote-1671279
Ref: types<2>-Footnote-2671322
Node: unicodedata<4>671365
Ref: whatsnew/3 5 unicodedata671472
Ref: 783671472
Ref: unicodedata<4>-Footnote-1671624
Node: unittest<3>671674
Ref: whatsnew/3 5 unittest671789
Ref: 784671789
Ref: unittest<3>-Footnote-1672583
Ref: unittest<3>-Footnote-2672626
Ref: unittest<3>-Footnote-3672669
Node: unittest mock<3>672712
Ref: whatsnew/3 5 unittest-mock672819
Ref: 788672819
Ref: unittest mock<3>-Footnote-1673760
Ref: unittest mock<3>-Footnote-2673803
Ref: unittest mock<3>-Footnote-3673846
Ref: unittest mock<3>-Footnote-4673889
Ref: unittest mock<3>-Footnote-5673932
Ref: unittest mock<3>-Footnote-6673975
Node: urllib674018
Ref: whatsnew/3 5 urllib674121
Ref: 78e674121
Ref: urllib-Footnote-1675281
Ref: urllib-Footnote-2675324
Ref: urllib-Footnote-3675366
Ref: urllib-Footnote-4675409
Ref: urllib-Footnote-5675452
Ref: urllib-Footnote-6675501
Ref: urllib-Footnote-7675550
Ref: urllib-Footnote-8675599
Node: wsgiref675642
Ref: whatsnew/3 5 wsgiref675738
Ref: 793675738
Ref: wsgiref-Footnote-1675976
Node: xmlrpc<2>676018
Ref: whatsnew/3 5 xmlrpc676115
Ref: 795676115
Ref: xmlrpc<2>-Footnote-1676485
Ref: xmlrpc<2>-Footnote-2676528
Node: xml sax676571
Ref: whatsnew/3 5 xml-sax676671
Ref: 796676671
Ref: xml sax-Footnote-1677004
Ref: xml sax-Footnote-2677046
Node: zipfile<3>677089
Ref: whatsnew/3 5 zipfile677171
Ref: 799677171
Ref: zipfile<3>-Footnote-1677511
Ref: zipfile<3>-Footnote-2677554
Node: Other module-level changes677597
Ref: whatsnew/3 5 other-module-level-changes677742
Ref: 79a677742
Ref: Other module-level changes-Footnote-1678073
Node: Optimizations<4>678116
Ref: whatsnew/3 5 optimizations678268
Ref: 79b678268
Ref: Optimizations<4>-Footnote-1681325
Ref: Optimizations<4>-Footnote-2681368
Ref: Optimizations<4>-Footnote-3681411
Ref: Optimizations<4>-Footnote-4681454
Ref: Optimizations<4>-Footnote-5681497
Ref: Optimizations<4>-Footnote-6681540
Ref: Optimizations<4>-Footnote-7681583
Ref: Optimizations<4>-Footnote-8681626
Ref: Optimizations<4>-Footnote-9681669
Ref: Optimizations<4>-Footnote-10681712
Ref: Optimizations<4>-Footnote-11681756
Ref: Optimizations<4>-Footnote-12681800
Ref: Optimizations<4>-Footnote-13681844
Ref: Optimizations<4>-Footnote-14681888
Ref: Optimizations<4>-Footnote-15681932
Ref: Optimizations<4>-Footnote-16681976
Ref: Optimizations<4>-Footnote-17682020
Ref: Optimizations<4>-Footnote-18682064
Ref: Optimizations<4>-Footnote-19682108
Ref: Optimizations<4>-Footnote-20682152
Node: Build and C API Changes<3>682196
Ref: whatsnew/3 5 build-and-c-api-changes682335
Ref: 7a9682335
Ref: Build and C API Changes<3>-Footnote-1685885
Ref: Build and C API Changes<3>-Footnote-2685928
Ref: Build and C API Changes<3>-Footnote-3685971
Ref: Build and C API Changes<3>-Footnote-4686014
Ref: Build and C API Changes<3>-Footnote-5686057
Ref: Build and C API Changes<3>-Footnote-6686100
Ref: Build and C API Changes<3>-Footnote-7686149
Ref: Build and C API Changes<3>-Footnote-8686192
Ref: Build and C API Changes<3>-Footnote-9686235
Ref: Build and C API Changes<3>-Footnote-10686284
Node: Deprecated<3>686323
Ref: whatsnew/3 5 deprecated686456
Ref: 7b5686456
Node: New Keywords<2>686733
Ref: whatsnew/3 5 new-keywords686836
Ref: 7b6686836
Ref: New Keywords<2>-Footnote-1687110
Node: Deprecated Python Behavior<2>687159
Ref: whatsnew/3 5 deprecated-python-behavior687300
Ref: 7b7687300
Node: Unsupported Operating Systems687715
Ref: whatsnew/3 5 unsupported-operating-systems687891
Ref: 7b8687891
Ref: Unsupported Operating Systems-Footnote-1688132
Node: Deprecated Python modules functions and methods<3>688181
Ref: whatsnew/3 5 deprecated-python-modules-functions-and-methods688319
Ref: 7b9688319
Ref: Deprecated Python modules functions and methods<3>-Footnote-1691257
Ref: Deprecated Python modules functions and methods<3>-Footnote-2691300
Ref: Deprecated Python modules functions and methods<3>-Footnote-3691342
Ref: Deprecated Python modules functions and methods<3>-Footnote-4691385
Ref: Deprecated Python modules functions and methods<3>-Footnote-5691428
Ref: Deprecated Python modules functions and methods<3>-Footnote-6691471
Ref: Deprecated Python modules functions and methods<3>-Footnote-7691514
Ref: Deprecated Python modules functions and methods<3>-Footnote-8691557
Node: Removed<2>691600
Ref: whatsnew/3 5 removed691728
Ref: 7bf691728
Node: API and Feature Removals<4>691826
Ref: whatsnew/3 5 api-and-feature-removals691900
Ref: 7c0691900
Ref: API and Feature Removals<4>-Footnote-1692757
Ref: API and Feature Removals<4>-Footnote-2692799
Node: Porting to Python 3 5692842
Ref: whatsnew/3 5 porting-to-python-3-5692988
Ref: 7c1692988
Node: Changes in Python behavior<2>693333
Ref: whatsnew/3 5 changes-in-python-behavior693457
Ref: 7c2693457
Node: Changes in the Python API<4>693867
Ref: whatsnew/3 5 changes-in-the-python-api694023
Ref: 7c3694023
Ref: Changes in the Python API<4>-Footnote-1700937
Ref: Changes in the Python API<4>-Footnote-2700986
Ref: Changes in the Python API<4>-Footnote-3701029
Ref: Changes in the Python API<4>-Footnote-4701072
Ref: Changes in the Python API<4>-Footnote-5701115
Ref: Changes in the Python API<4>-Footnote-6701158
Ref: Changes in the Python API<4>-Footnote-7701201
Ref: Changes in the Python API<4>-Footnote-8701244
Ref: Changes in the Python API<4>-Footnote-9701287
Ref: Changes in the Python API<4>-Footnote-10701330
Ref: Changes in the Python API<4>-Footnote-11701374
Ref: Changes in the Python API<4>-Footnote-12701418
Ref: Changes in the Python API<4>-Footnote-13701461
Ref: Changes in the Python API<4>-Footnote-14701511
Ref: Changes in the Python API<4>-Footnote-15701561
Ref: Changes in the Python API<4>-Footnote-16701605
Ref: Changes in the Python API<4>-Footnote-17701649
Ref: Changes in the Python API<4>-Footnote-18701693
Node: Changes in the C API<4>701736
Ref: whatsnew/3 5 changes-in-the-c-api701854
Ref: 7ce701854
Ref: Changes in the C API<4>-Footnote-1703126
Ref: Changes in the C API<4>-Footnote-2703169
Ref: Changes in the C API<4>-Footnote-3703212
Node: Notable changes in Python 3 5 4703261
Ref: whatsnew/3 5 notable-changes-in-python-3-5-4703388
Ref: 7d3703388
Node: New make regen-all build target<2>703625
Ref: whatsnew/3 5 new-make-regen-all-build-target703773
Ref: 7d4703773
Ref: New make regen-all build target<2>-Footnote-1704558
Ref: New make regen-all build target<2>-Footnote-2704625
Node: Removal of make touch build target<2>704668
Ref: whatsnew/3 5 removal-of-make-touch-build-target704816
Ref: 7d5704816
Ref: Removal of make touch build target<2>-Footnote-1705237
Node: What's New In Python 3 4705280
Ref: whatsnew/3 4 doc705440
Ref: 7d6705440
Ref: whatsnew/3 4 what-s-new-in-python-3-4705440
Ref: 7d7705440
Ref: What's New In Python 3 4-Footnote-1706168
Ref: What's New In Python 3 4-Footnote-2706228
Node: Summary -- Release Highlights<2>706277
Ref: whatsnew/3 4 summary-release-highlights706394
Ref: 7d8706394
Ref: Summary -- Release Highlights<2>-Footnote-1710690
Ref: Summary -- Release Highlights<2>-Footnote-2710739
Ref: Summary -- Release Highlights<2>-Footnote-3710788
Ref: Summary -- Release Highlights<2>-Footnote-4710831
Ref: Summary -- Release Highlights<2>-Footnote-5710880
Ref: Summary -- Release Highlights<2>-Footnote-6710923
Ref: Summary -- Release Highlights<2>-Footnote-7710972
Ref: Summary -- Release Highlights<2>-Footnote-8711021
Ref: Summary -- Release Highlights<2>-Footnote-9711070
Ref: Summary -- Release Highlights<2>-Footnote-10711119
Ref: Summary -- Release Highlights<2>-Footnote-11711169
Ref: Summary -- Release Highlights<2>-Footnote-12711219
Ref: Summary -- Release Highlights<2>-Footnote-13711269
Ref: Summary -- Release Highlights<2>-Footnote-14711319
Ref: Summary -- Release Highlights<2>-Footnote-15711369
Ref: Summary -- Release Highlights<2>-Footnote-16711412
Ref: Summary -- Release Highlights<2>-Footnote-17711456
Ref: Summary -- Release Highlights<2>-Footnote-18711506
Ref: Summary -- Release Highlights<2>-Footnote-19711556
Ref: Summary -- Release Highlights<2>-Footnote-20711600
Ref: Summary -- Release Highlights<2>-Footnote-21711646
Ref: Summary -- Release Highlights<2>-Footnote-22711696
Ref: Summary -- Release Highlights<2>-Footnote-23711746
Ref: Summary -- Release Highlights<2>-Footnote-24711790
Ref: Summary -- Release Highlights<2>-Footnote-25711840
Node: New Features<5>711890
Ref: whatsnew/3 4 new-features712030
Ref: 7f4712030
Node: PEP 453 Explicit Bootstrapping of PIP in Python Installations712520
Ref: whatsnew/3 4 pep-453-explicit-bootstrapping-of-pip-in-python-installations712700
Ref: 7f5712700
Ref: whatsnew/3 4 whatsnew-pep-453712700
Ref: 7d9712700
Node: Bootstrapping pip By Default712912
Ref: whatsnew/3 4 bootstrapping-pip-by-default713068
Ref: 7f6713068
Ref: Bootstrapping pip By Default-Footnote-1715970
Ref: Bootstrapping pip By Default-Footnote-2716019
Node: Documentation Changes716114
Ref: whatsnew/3 4 documentation-changes716270
Ref: 7f9716270
Ref: Documentation Changes-Footnote-1717186
Ref: Documentation Changes-Footnote-2717223
Node: PEP 446 Newly Created File Descriptors Are Non-Inheritable717272
Ref: whatsnew/3 4 pep-446-newly-created-file-descriptors-are-non-inheritable717491
Ref: 7fe717491
Ref: whatsnew/3 4 whatsnew-pep-446717491
Ref: 7da717491
Ref: PEP 446 Newly Created File Descriptors Are Non-Inheritable-Footnote-1718508
Ref: PEP 446 Newly Created File Descriptors Are Non-Inheritable-Footnote-2718557
Node: Improvements to Codec Handling718606
Ref: whatsnew/3 4 codec-handling-improvements718811
Ref: 7dc718811
Ref: whatsnew/3 4 improvements-to-codec-handling718811
Ref: 806718811
Ref: Improvements to Codec Handling-Footnote-1723017
Ref: Improvements to Codec Handling-Footnote-2723059
Ref: Improvements to Codec Handling-Footnote-3723102
Ref: Improvements to Codec Handling-Footnote-4723145
Node: PEP 451 A ModuleSpec Type for the Import System723188
Ref: whatsnew/3 4 pep-451-a-modulespec-type-for-the-import-system723360
Ref: 80b723360
Ref: whatsnew/3 4 whatsnew-pep-451723360
Ref: 7dd723360
Ref: PEP 451 A ModuleSpec Type for the Import System-Footnote-1724311
Ref: PEP 451 A ModuleSpec Type for the Import System-Footnote-2724360
Node: Other Language Changes<5>724440
Ref: whatsnew/3 4 other-language-changes724573
Ref: 80d724573
Ref: Other Language Changes<5>-Footnote-1727210
Ref: Other Language Changes<5>-Footnote-2727253
Ref: Other Language Changes<5>-Footnote-3727296
Ref: Other Language Changes<5>-Footnote-4727339
Ref: Other Language Changes<5>-Footnote-5727384
Ref: Other Language Changes<5>-Footnote-6727427
Ref: Other Language Changes<5>-Footnote-7727470
Ref: Other Language Changes<5>-Footnote-8727513
Ref: Other Language Changes<5>-Footnote-9727556
Ref: Other Language Changes<5>-Footnote-10727599
Ref: Other Language Changes<5>-Footnote-11727643
Ref: Other Language Changes<5>-Footnote-12727693
Node: New Modules<5>727737
Ref: whatsnew/3 4 new-modules727864
Ref: 812727864
Node: asyncio<6>728075
Ref: whatsnew/3 4 asyncio728154
Ref: 813728154
Ref: whatsnew/3 4 whatsnew-asyncio728154
Ref: 7df728154
Ref: asyncio<6>-Footnote-1728747
Ref: asyncio<6>-Footnote-2728796
Node: ensurepip728845
Ref: whatsnew/3 4 ensurepip728940
Ref: 814728940
Ref: whatsnew/3 4 whatsnew-ensurepip728940
Ref: 7e0728940
Ref: ensurepip-Footnote-1730212
Node: enum<5>730261
Ref: whatsnew/3 4 enum730356
Ref: 815730356
Ref: whatsnew/3 4 whatsnew-enum730356
Ref: 7e1730356
Ref: enum<5>-Footnote-1730925
Ref: enum<5>-Footnote-2730974
Node: pathlib<5>731023
Ref: whatsnew/3 4 pathlib731121
Ref: 816731121
Ref: whatsnew/3 4 whatsnew-pathlib731121
Ref: 7e2731121
Ref: pathlib<5>-Footnote-1731738
Node: selectors<2>731787
Ref: whatsnew/3 4 selectors731891
Ref: 817731891
Ref: whatsnew/3 4 whatsnew-selectors731891
Ref: 7e3731891
Ref: selectors<2>-Footnote-1732149
Node: statistics<3>732198
Ref: whatsnew/3 4 statistics732306
Ref: 818732306
Ref: whatsnew/3 4 whatsnew-statistics732306
Ref: 7e4732306
Ref: statistics<3>-Footnote-1732770
Ref: statistics<3>-Footnote-2732819
Node: tracemalloc<3>732868
Ref: whatsnew/3 4 tracemalloc732955
Ref: 819732955
Ref: whatsnew/3 4 whatsnew-tracemalloc732955
Ref: 7e5732955
Ref: tracemalloc<3>-Footnote-1733619
Ref: tracemalloc<3>-Footnote-2733668
Node: Improved Modules<5>733717
Ref: whatsnew/3 4 improved-modules733859
Ref: 81a733859
Node: abc735171
Ref: whatsnew/3 4 abc735246
Ref: 81b735246
Ref: abc-Footnote-1735767
Ref: abc-Footnote-2735810
Node: aifc<2>735853
Ref: whatsnew/3 4 aifc735948
Ref: 81f735948
Ref: aifc<2>-Footnote-1736586
Ref: aifc<2>-Footnote-2736629
Ref: aifc<2>-Footnote-3736672
Node: argparse<3>736714
Ref: whatsnew/3 4 argparse736813
Ref: 824736813
Ref: argparse<3>-Footnote-1737059
Node: audioop737102
Ref: whatsnew/3 4 audioop737200
Ref: 826737200
Ref: audioop-Footnote-1737739
Ref: audioop-Footnote-2737782
Ref: audioop-Footnote-3737825
Node: base64737868
Ref: whatsnew/3 4 base64737969
Ref: 828737969
Ref: base64-Footnote-1738800
Ref: base64-Footnote-2738843
Node: collections<6>738886
Ref: whatsnew/3 4 collections738988
Ref: 82d738988
Ref: collections<6>-Footnote-1739318
Node: colorsys739361
Ref: whatsnew/3 4 colorsys739470
Ref: 82f739470
Ref: colorsys-Footnote-1739838
Node: contextlib<4>739881
Ref: whatsnew/3 4 contextlib739982
Ref: 830739982
Ref: contextlib<4>-Footnote-1741167
Ref: contextlib<4>-Footnote-2741210
Ref: contextlib<4>-Footnote-3741253
Node: dbm<5>741296
Ref: whatsnew/3 4 dbm741395
Ref: 834741395
Ref: dbm<5>-Footnote-1741742
Node: dis<2>741785
Ref: whatsnew/3 4 dis741881
Ref: 836741881
Ref: dis<2>-Footnote-1744480
Ref: dis<2>-Footnote-2744523
Ref: dis<2>-Footnote-3744566
Node: doctest<2>744609
Ref: whatsnew/3 4 doctest744707
Ref: 840744707
Ref: doctest<2>-Footnote-1745475
Ref: doctest<2>-Footnote-2745518
Ref: doctest<2>-Footnote-3745561
Node: email<3>745603
Ref: whatsnew/3 4 email745702
Ref: 843745702
Ref: whatsnew/3 4 whatsnew-email-contentmanager746950
Ref: 7e9746950
Ref: email<3>-Footnote-1747879
Ref: email<3>-Footnote-2747922
Ref: email<3>-Footnote-3747965
Ref: email<3>-Footnote-4748008
Node: filecmp748051
Ref: whatsnew/3 4 filecmp748152
Ref: 84b748152
Ref: filecmp-Footnote-1748898
Ref: filecmp-Footnote-2748941
Node: functools<4>748984
Ref: whatsnew/3 4 functools749082
Ref: 84f749082
Ref: whatsnew/3 4 whatsnew-singledispatch749529
Ref: 7e6749529
Ref: functools<4>-Footnote-1750487
Ref: functools<4>-Footnote-2750529
Ref: functools<4>-Footnote-3750578
Ref: functools<4>-Footnote-4750621
Node: gc<3>750664
Ref: whatsnew/3 4 gc750762
Ref: 852750762
Ref: gc<3>-Footnote-1751028
Node: glob<2>751071
Ref: whatsnew/3 4 glob751167
Ref: 854751167
Ref: glob<2>-Footnote-1751471
Node: hashlib<2>751513
Ref: whatsnew/3 4 hashlib751611
Ref: 856751611
Ref: hashlib<2>-Footnote-1752244
Ref: hashlib<2>-Footnote-2752289
Ref: hashlib<2>-Footnote-3752332
Node: hmac<2>752375
Ref: whatsnew/3 4 hmac752470
Ref: 858752470
Ref: hmac<2>-Footnote-1753496
Ref: hmac<2>-Footnote-2753539
Ref: hmac<2>-Footnote-3753582
Ref: hmac<2>-Footnote-4753631
Node: html753674
Ref: whatsnew/3 4 html753766
Ref: 85e753766
Ref: html-Footnote-1754523
Ref: html-Footnote-2754565
Ref: html-Footnote-3754608
Node: http<2>754651
Ref: whatsnew/3 4 http754755
Ref: 860754755
Ref: http<2>-Footnote-1755396
Ref: http<2>-Footnote-2755439
Node: idlelib and IDLE<4>755482
Ref: whatsnew/3 4 idlelib-and-idle755594
Ref: 863755594
Node: importlib<6>755988
Ref: whatsnew/3 4 importlib756103
Ref: 864756103
Ref: importlib<6>-Footnote-1758104
Ref: importlib<6>-Footnote-2758147
Ref: importlib<6>-Footnote-3758190
Ref: importlib<6>-Footnote-4758233
Ref: importlib<6>-Footnote-5758276
Ref: importlib<6>-Footnote-6758319
Ref: importlib<6>-Footnote-7758362
Node: inspect<4>758405
Ref: whatsnew/3 4 inspect758513
Ref: 86c758513
Ref: inspect<4>-Footnote-1760227
Ref: inspect<4>-Footnote-2760270
Ref: inspect<4>-Footnote-3760313
Ref: inspect<4>-Footnote-4760356
Ref: inspect<4>-Footnote-5760399
Ref: inspect<4>-Footnote-6760442
Node: ipaddress<3>760485
Ref: whatsnew/3 4 ipaddress760591
Ref: 870760591
Ref: ipaddress<3>-Footnote-1761117
Node: logging<5>761160
Ref: whatsnew/3 4 logging761263
Ref: 872761263
Ref: logging<5>-Footnote-1762393
Ref: logging<5>-Footnote-2762435
Ref: logging<5>-Footnote-3762478
Node: marshal762521
Ref: whatsnew/3 4 marshal762619
Ref: 878762619
Ref: whatsnew/3 4 whatsnew-marshal-3762619
Ref: 7de762619
Ref: marshal-Footnote-1763294
Ref: marshal-Footnote-2763337
Node: mmap<2>763380
Ref: whatsnew/3 4 mmap763486
Ref: 879763486
Ref: mmap<2>-Footnote-1763649
Node: multiprocessing<5>763691
Ref: whatsnew/3 4 multiprocessing763801
Ref: 87a763801
Ref: whatsnew/3 4 whatsnew-multiprocessing-no-fork763852
Ref: 7e8763852
Ref: multiprocessing<5>-Footnote-1765664
Ref: multiprocessing<5>-Footnote-2765706
Ref: multiprocessing<5>-Footnote-3765749
Ref: multiprocessing<5>-Footnote-4765791
Node: operator<2>765834
Ref: whatsnew/3 4 operator765942
Ref: 881765942
Ref: operator<2>-Footnote-1766493
Ref: operator<2>-Footnote-2766542
Ref: operator<2>-Footnote-3766585
Node: os<6>766628
Ref: whatsnew/3 4 os766724
Ref: 883766724
Ref: os<6>-Footnote-1768169
Ref: os<6>-Footnote-2768212
Ref: os<6>-Footnote-3768255
Ref: os<6>-Footnote-4768297
Node: pdb<3>768340
Ref: whatsnew/3 4 pdb768434
Ref: 88a768434
Ref: pdb<3>-Footnote-1769428
Ref: pdb<3>-Footnote-2769471
Node: pickle<4>769514
Ref: whatsnew/3 4 pickle769614
Ref: 88d769614
Ref: whatsnew/3 4 whatsnew-protocol-4769614
Ref: 7e7769614
Ref: pickle<4>-Footnote-1770208
Node: plistlib<2>770257
Ref: whatsnew/3 4 plistlib770360
Ref: 88f770360
Ref: plistlib<2>-Footnote-1770894
Node: poplib<2>770937
Ref: whatsnew/3 4 poplib771040
Ref: 896771040
Ref: poplib<2>-Footnote-1771428
Node: pprint<2>771470
Ref: whatsnew/3 4 pprint771565
Ref: 899771565
Ref: pprint<2>-Footnote-1772183
Ref: pprint<2>-Footnote-2772226
Node: pty772269
Ref: whatsnew/3 4 pty772363
Ref: 89c772363
Node: pydoc<3>772554
Ref: whatsnew/3 4 pydoc772644
Ref: 89e772644
Ref: pydoc<3>-Footnote-1773699
Ref: pydoc<3>-Footnote-2773742
Node: re<5>773785
Ref: whatsnew/3 4 re773880
Ref: 89f773880
Ref: re<5>-Footnote-1774621
Ref: re<5>-Footnote-2774664
Ref: re<5>-Footnote-3774707
Node: resource774750
Ref: whatsnew/3 4 resource774843
Ref: 8a3774843
Ref: resource-Footnote-1775694
Ref: resource-Footnote-2775737
Ref: resource-Footnote-3775780
Node: select775823
Ref: whatsnew/3 4 select775917
Ref: 8ad775917
Ref: select-Footnote-1776424
Ref: select-Footnote-2776467
Node: shelve776510
Ref: whatsnew/3 4 shelve776605
Ref: 8b4776605
Ref: shelve-Footnote-1776875
Node: shutil<3>776918
Ref: whatsnew/3 4 shutil777015
Ref: 8b6777015
Ref: shutil<3>-Footnote-1777386
Node: smtpd<2>777431
Ref: whatsnew/3 4 smtpd777532
Ref: 8b9777532
Ref: smtpd<2>-Footnote-1777908
Node: smtplib<2>777951
Ref: whatsnew/3 4 smtplib778052
Ref: 8bb778052
Ref: smtplib<2>-Footnote-1778412
Node: socket<6>778454
Ref: whatsnew/3 4 socket778557
Ref: 8bd778557
Ref: socket<6>-Footnote-1779334
Ref: socket<6>-Footnote-2779377
Node: sqlite3<4>779419
Ref: whatsnew/3 4 sqlite3779518
Ref: 8c2779518
Ref: sqlite3<4>-Footnote-1779807
Ref: sqlite3<4>-Footnote-2779847
Node: ssl<7>779890
Ref: whatsnew/3 4 ssl779984
Ref: 8c3779984
Ref: whatsnew/3 4 whatsnew-tls-11-12780011
Ref: 7ec780011
Ref: whatsnew/3 4 whatsnew34-sslcontext780281
Ref: 7ef780281
Ref: whatsnew/3 4 whatsnew34-win-cert-store782951
Ref: 7ed782951
Ref: whatsnew/3 4 whatsnew34-sni783205
Ref: 7ee783205
Ref: ssl<7>-Footnote-1783654
Ref: ssl<7>-Footnote-2783697
Ref: ssl<7>-Footnote-3783740
Ref: ssl<7>-Footnote-4783783
Ref: ssl<7>-Footnote-5783826
Ref: ssl<7>-Footnote-6783869
Ref: ssl<7>-Footnote-7783911
Ref: ssl<7>-Footnote-8783954
Ref: ssl<7>-Footnote-9783997
Ref: ssl<7>-Footnote-10784039
Node: stat784083
Ref: whatsnew/3 4 stat784176
Ref: 8d7784176
Ref: stat-Footnote-1784647
Ref: stat-Footnote-2784690
Node: struct<2>784733
Ref: whatsnew/3 4 struct784833
Ref: 8dc784833
Ref: struct<2>-Footnote-1785163
Node: subprocess<4>785206
Ref: whatsnew/3 4 subprocess785310
Ref: 8df785310
Ref: subprocess<4>-Footnote-1785754
Ref: subprocess<4>-Footnote-2785797
Node: sunau<2>785840
Ref: whatsnew/3 4 sunau785941
Ref: 8e2785941
Ref: sunau<2>-Footnote-1786746
Ref: sunau<2>-Footnote-2786789
Ref: sunau<2>-Footnote-3786832
Ref: sunau<2>-Footnote-4786875
Node: sys<6>786917
Ref: whatsnew/3 4 sys787015
Ref: 8e6787015
Ref: sys<6>-Footnote-1788293
Ref: sys<6>-Footnote-2788336
Node: tarfile<3>788378
Ref: whatsnew/3 4 tarfile788476
Ref: 8ec788476
Ref: tarfile<3>-Footnote-1788793
Node: textwrap788836
Ref: whatsnew/3 4 textwrap788940
Ref: 8ee788940
Ref: textwrap-Footnote-1789639
Ref: textwrap-Footnote-2789682
Node: threading<4>789725
Ref: whatsnew/3 4 threading789831
Ref: 8f3789831
Ref: threading<4>-Footnote-1790174
Node: traceback<3>790217
Ref: whatsnew/3 4 traceback790323
Ref: 8f5790323
Ref: traceback<3>-Footnote-1790636
Node: types<3>790681
Ref: whatsnew/3 4 types790784
Ref: 8f7790784
Ref: types<3>-Footnote-1791288
Node: urllib<2>791331
Ref: whatsnew/3 4 urllib791433
Ref: 8f9791433
Ref: urllib<2>-Footnote-1792747
Ref: urllib<2>-Footnote-2792790
Ref: urllib<2>-Footnote-3792833
Ref: urllib<2>-Footnote-4792876
Ref: urllib<2>-Footnote-5792919
Ref: urllib<2>-Footnote-6792962
Node: unittest<4>793005
Ref: whatsnew/3 4 unittest793106
Ref: 903793106
Ref: unittest<4>-Footnote-1796256
Ref: unittest<4>-Footnote-2796299
Ref: unittest<4>-Footnote-3796342
Ref: unittest<4>-Footnote-4796385
Ref: unittest<4>-Footnote-5796428
Ref: unittest<4>-Footnote-6796471
Ref: unittest<4>-Footnote-7796514
Ref: unittest<4>-Footnote-8796557
Ref: unittest<4>-Footnote-9796600
Node: venv<4>796643
Ref: whatsnew/3 4 venv796742
Ref: 90c796742
Ref: venv<4>-Footnote-1797298
Ref: venv<4>-Footnote-2797341
Ref: venv<4>-Footnote-3797384
Node: wave<2>797433
Ref: whatsnew/3 4 wave797531
Ref: 90f797531
Ref: wave<2>-Footnote-1798166
Ref: wave<2>-Footnote-2798209
Ref: wave<2>-Footnote-3798252
Ref: wave<2>-Footnote-4798294
Node: weakref<2>798336
Ref: whatsnew/3 4 weakref798439
Ref: 913798439
Ref: weakref<2>-Footnote-1799058
Ref: weakref<2>-Footnote-2799101
Ref: weakref<2>-Footnote-3799144
Node: xml etree<2>799187
Ref: whatsnew/3 4 xml-etree799293
Ref: 917799293
Ref: xml etree<2>-Footnote-1800030
Ref: xml etree<2>-Footnote-2800073
Node: zipfile<4>800116
Ref: whatsnew/3 4 zipfile800203
Ref: 91e800203
Ref: zipfile<4>-Footnote-1800732
Ref: zipfile<4>-Footnote-2800775
Node: CPython Implementation Changes800818
Ref: whatsnew/3 4 cpython-implementation-changes800959
Ref: 921800959
Node: PEP 445 Customization of CPython Memory Allocators801489
Ref: whatsnew/3 4 pep-445-customization-of-cpython-memory-allocators801647
Ref: 922801647
Ref: whatsnew/3 4 whatsnew-pep-445801647
Ref: 7f2801647
Ref: PEP 445 Customization of CPython Memory Allocators-Footnote-1802041
Ref: PEP 445 Customization of CPython Memory Allocators-Footnote-2802090
Node: PEP 442 Safe Object Finalization802139
Ref: whatsnew/3 4 pep-442-safe-object-finalization802355
Ref: 923802355
Ref: whatsnew/3 4 whatsnew-pep-442802355
Ref: 7f1802355
Ref: PEP 442 Safe Object Finalization-Footnote-1803221
Ref: PEP 442 Safe Object Finalization-Footnote-2803270
Node: PEP 456 Secure and Interchangeable Hash Algorithm803319
Ref: whatsnew/3 4 pep-456-secure-and-interchangeable-hash-algorithm803508
Ref: 925803508
Ref: whatsnew/3 4 whatsnew-pep-456803508
Ref: 7ea803508
Ref: PEP 456 Secure and Interchangeable Hash Algorithm-Footnote-1804454
Ref: PEP 456 Secure and Interchangeable Hash Algorithm-Footnote-2804503
Node: PEP 436 Argument Clinic804546
Ref: whatsnew/3 4 pep-436-argument-clinic804732
Ref: 927804732
Ref: whatsnew/3 4 whatsnew-pep-436804732
Ref: 7f3804732
Ref: PEP 436 Argument Clinic-Footnote-1805835
Ref: PEP 436 Argument Clinic-Footnote-2805884
Node: Other Build and C API Changes805933
Ref: whatsnew/3 4 other-build-and-c-api-changes806091
Ref: 928806091
Ref: Other Build and C API Changes-Footnote-1808175
Ref: Other Build and C API Changes-Footnote-2808218
Ref: Other Build and C API Changes-Footnote-3808261
Ref: Other Build and C API Changes-Footnote-4808306
Ref: Other Build and C API Changes-Footnote-5808348
Ref: Other Build and C API Changes-Footnote-6808391
Ref: Other Build and C API Changes-Footnote-7808464
Ref: Other Build and C API Changes-Footnote-8808528
Ref: Other Build and C API Changes-Footnote-9808571
Node: Other Improvements<2>808614
Ref: whatsnew/3 4 other-improvements808774
Ref: 92e808774
Ref: whatsnew/3 4 other-improvements-3-4808774
Ref: 92f808774
Ref: whatsnew/3 4 whatsnew-isolated-mode808829
Ref: 7db808829
Ref: Other Improvements<2>-Footnote-1812950
Ref: Other Improvements<2>-Footnote-2812993
Ref: Other Improvements<2>-Footnote-3813035
Ref: Other Improvements<2>-Footnote-4813078
Ref: Other Improvements<2>-Footnote-5813121
Ref: Other Improvements<2>-Footnote-6813164
Ref: Other Improvements<2>-Footnote-7813207
Ref: Other Improvements<2>-Footnote-8813302
Ref: Other Improvements<2>-Footnote-9813355
Ref: Other Improvements<2>-Footnote-10813398
Ref: Other Improvements<2>-Footnote-11813442
Ref: Other Improvements<2>-Footnote-12813486
Ref: Other Improvements<2>-Footnote-13813536
Ref: Other Improvements<2>-Footnote-14813580
Ref: Other Improvements<2>-Footnote-15813624
Ref: Other Improvements<2>-Footnote-16813668
Ref: Other Improvements<2>-Footnote-17813712
Ref: Other Improvements<2>-Footnote-18813762
Ref: Other Improvements<2>-Footnote-19813806
Ref: Other Improvements<2>-Footnote-20813850
Ref: Other Improvements<2>-Footnote-21813894
Node: Significant Optimizations813938
Ref: whatsnew/3 4 significant-optimizations814060
Ref: 935814060
Ref: Significant Optimizations-Footnote-1816863
Ref: Significant Optimizations-Footnote-2816906
Ref: Significant Optimizations-Footnote-3816949
Ref: Significant Optimizations-Footnote-4816992
Ref: Significant Optimizations-Footnote-5817035
Ref: Significant Optimizations-Footnote-6817078
Ref: Significant Optimizations-Footnote-7817121
Ref: Significant Optimizations-Footnote-8817163
Ref: Significant Optimizations-Footnote-9817206
Ref: Significant Optimizations-Footnote-10817249
Ref: Significant Optimizations-Footnote-11817293
Ref: Significant Optimizations-Footnote-12817337
Ref: Significant Optimizations-Footnote-13817381
Node: Deprecated<4>817425
Ref: whatsnew/3 4 deprecated817557
Ref: 93a817557
Ref: whatsnew/3 4 deprecated-3-4817557
Ref: 80c817557
Node: Deprecations in the Python API817997
Ref: whatsnew/3 4 deprecations-in-the-python-api818105
Ref: 93b818105
Node: Deprecated Features821867
Ref: whatsnew/3 4 deprecated-features821975
Ref: 94e821975
Ref: Deprecated Features-Footnote-1822354
Ref: Deprecated Features-Footnote-2822397
Node: Removed<3>822440
Ref: whatsnew/3 4 removed822563
Ref: 950822563
Node: Operating Systems No Longer Supported822719
Ref: whatsnew/3 4 operating-systems-no-longer-supported822839
Ref: 951822839
Ref: Operating Systems No Longer Supported-Footnote-1823252
Ref: Operating Systems No Longer Supported-Footnote-2823295
Ref: Operating Systems No Longer Supported-Footnote-3823338
Node: API and Feature Removals<5>823381
Ref: whatsnew/3 4 api-and-feature-removals823523
Ref: 952823523
Ref: API and Feature Removals<5>-Footnote-1825969
Ref: API and Feature Removals<5>-Footnote-2826005
Ref: API and Feature Removals<5>-Footnote-3826048
Ref: API and Feature Removals<5>-Footnote-4826091
Ref: API and Feature Removals<5>-Footnote-5826134
Ref: API and Feature Removals<5>-Footnote-6826177
Ref: API and Feature Removals<5>-Footnote-7826219
Node: Code Cleanups826262
Ref: whatsnew/3 4 code-cleanups826358
Ref: 955826358
Ref: Code Cleanups-Footnote-1827021
Node: Porting to Python 3 4827064
Ref: whatsnew/3 4 porting-to-python-3-4827190
Ref: 956827190
Node: Changes in 'python' Command Behavior<2>827557
Ref: whatsnew/3 4 changes-in-python-command-behavior827691
Ref: 957827691
Ref: Changes in 'python' Command Behavior<2>-Footnote-1828802
Node: Changes in the Python API<5>828845
Ref: whatsnew/3 4 changes-in-the-python-api829011
Ref: 959829011
Ref: Changes in the Python API<5>-Footnote-1842393
Ref: Changes in the Python API<5>-Footnote-2842436
Ref: Changes in the Python API<5>-Footnote-3842479
Ref: Changes in the Python API<5>-Footnote-4842522
Ref: Changes in the Python API<5>-Footnote-5842565
Ref: Changes in the Python API<5>-Footnote-6842608
Ref: Changes in the Python API<5>-Footnote-7842651
Ref: Changes in the Python API<5>-Footnote-8842694
Ref: Changes in the Python API<5>-Footnote-9842736
Ref: Changes in the Python API<5>-Footnote-10842779
Ref: Changes in the Python API<5>-Footnote-11842823
Ref: Changes in the Python API<5>-Footnote-12842867
Ref: Changes in the Python API<5>-Footnote-13842911
Ref: Changes in the Python API<5>-Footnote-14842955
Ref: Changes in the Python API<5>-Footnote-15842999
Ref: Changes in the Python API<5>-Footnote-16843043
Ref: Changes in the Python API<5>-Footnote-17843087
Ref: Changes in the Python API<5>-Footnote-18843131
Ref: Changes in the Python API<5>-Footnote-19843175
Ref: Changes in the Python API<5>-Footnote-20843219
Ref: Changes in the Python API<5>-Footnote-21843263
Ref: Changes in the Python API<5>-Footnote-22843307
Ref: Changes in the Python API<5>-Footnote-23843351
Ref: Changes in the Python API<5>-Footnote-24843394
Node: Changes in the C API<5>843438
Ref: whatsnew/3 4 changes-in-the-c-api843556
Ref: 96b843556
Ref: Changes in the C API<5>-Footnote-1845316
Ref: Changes in the C API<5>-Footnote-2845359
Node: Changed in 3 4 3845402
Ref: whatsnew/3 4 changed-in-3-4-3845509
Ref: 977845509
Node: PEP 476 Enabling certificate verification by default for stdlib http clients845725
Ref: whatsnew/3 4 pep-476845854
Ref: 978845854
Ref: whatsnew/3 4 pep-476-enabling-certificate-verification-by-default-for-stdlib-http-clients845854
Ref: 979845854
Node: What's New In Python 3 3846853
Ref: whatsnew/3 3 doc847008
Ref: 97a847008
Ref: whatsnew/3 3 what-s-new-in-python-3-3847008
Ref: 97b847008
Ref: What's New In Python 3 3-Footnote-1848942
Ref: What's New In Python 3 3-Footnote-2849002
Node: Summary -- Release highlights<4>849051
Ref: whatsnew/3 3 summary-release-highlights849181
Ref: 97c849181
Node: PEP 405 Virtual Environments850510
Ref: whatsnew/3 3 pep-405850684
Ref: 97e850684
Ref: whatsnew/3 3 pep-405-virtual-environments850684
Ref: 986850684
Ref: PEP 405 Virtual Environments-Footnote-1851671
Node: PEP 420 Implicit Namespace Packages851720
Ref: whatsnew/3 3 pep-420-implicit-namespace-packages851934
Ref: 987851934
Ref: PEP 420 Implicit Namespace Packages-Footnote-1852444
Ref: PEP 420 Implicit Namespace Packages-Footnote-2852493
Node: PEP 3118 New memoryview implementation and buffer protocol documentation852542
Ref: whatsnew/3 3 pep-3118-new-memoryview-implementation-and-buffer-protocol-documentation852766
Ref: 988852766
Ref: whatsnew/3 3 pep-3118-update852766
Ref: 989852766
Ref: PEP 3118 New memoryview implementation and buffer protocol documentation-Footnote-1853896
Node: Features853945
Ref: whatsnew/3 3 features854082
Ref: 98a854082
Ref: Features-Footnote-1854882
Node: API changes854925
Ref: whatsnew/3 3 api-changes855062
Ref: 98b855062
Ref: API changes-Footnote-1856076
Ref: API changes-Footnote-2856119
Node: PEP 393 Flexible String Representation856168
Ref: whatsnew/3 3 pep-393856392
Ref: 981856392
Ref: whatsnew/3 3 pep-393-flexible-string-representation856392
Ref: 98e856392
Ref: PEP 393 Flexible String Representation-Footnote-1857451
Node: Functionality857500
Ref: whatsnew/3 3 functionality857627
Ref: 98f857627
Ref: Functionality-Footnote-1859074
Ref: Functionality-Footnote-2859123
Node: Performance and resource usage859166
Ref: whatsnew/3 3 performance-and-resource-usage859293
Ref: 991859293
Ref: Performance and resource usage-Footnote-1860523
Node: PEP 397 Python Launcher for Windows860572
Ref: whatsnew/3 3 pep-397860776
Ref: 992860776
Ref: whatsnew/3 3 pep-397-python-launcher-for-windows860776
Ref: 993860776
Ref: PEP 397 Python Launcher for Windows-Footnote-1862313
Ref: PEP 397 Python Launcher for Windows-Footnote-2862355
Node: PEP 3151 Reworking the OS and IO exception hierarchy862404
Ref: whatsnew/3 3 pep-3151862617
Ref: 97f862617
Ref: whatsnew/3 3 pep-3151-reworking-the-os-and-io-exception-hierarchy862617
Ref: 996862617
Ref: PEP 3151 Reworking the OS and IO exception hierarchy-Footnote-1865185
Node: PEP 380 Syntax for Delegating to a Subgenerator865234
Ref: whatsnew/3 3 pep-380865449
Ref: 97d865449
Ref: whatsnew/3 3 pep-380-syntax-for-delegating-to-a-subgenerator865449
Ref: 9a6865449
Ref: PEP 380 Syntax for Delegating to a Subgenerator-Footnote-1867891
Node: PEP 409 Suppressing exception context867940
Ref: whatsnew/3 3 pep-409-suppressing-exception-context868136
Ref: 9a8868136
Ref: PEP 409 Suppressing exception context-Footnote-1870223
Node: PEP 414 Explicit Unicode literals870272
Ref: whatsnew/3 3 pep-414-explicit-unicode-literals870470
Ref: 9a9870470
Ref: PEP 414 Explicit Unicode literals-Footnote-1871178
Node: PEP 3155 Qualified name for classes and functions871227
Ref: whatsnew/3 3 pep-3155-qualified-name-for-classes-and-functions871418
Ref: 9aa871418
Ref: PEP 3155 Qualified name for classes and functions-Footnote-1873005
Node: PEP 412 Key-Sharing Dictionary873054
Ref: whatsnew/3 3 pep-412873245
Ref: 982873245
Ref: whatsnew/3 3 pep-412-key-sharing-dictionary873245
Ref: 9ab873245
Ref: PEP 412 Key-Sharing Dictionary-Footnote-1873763
Node: PEP 362 Function Signature Object873812
Ref: whatsnew/3 3 pep-362-function-signature-object873987
Ref: 9ac873987
Ref: PEP 362 Function Signature Object-Footnote-1874880
Node: PEP 421 Adding sys implementation874929
Ref: whatsnew/3 3 pep-421-adding-sys-implementation875121
Ref: 9ae875121
Ref: PEP 421 Adding sys implementation-Footnote-1876335
Node: SimpleNamespace876384
Ref: whatsnew/3 3 simplenamespace876469
Ref: 9b0876469
Ref: SimpleNamespace-Footnote-1877086
Node: Using importlib as the Implementation of Import877135
Ref: whatsnew/3 3 importlib877319
Ref: 980877319
Ref: whatsnew/3 3 using-importlib-as-the-implementation-of-import877319
Ref: 9b2877319
Ref: Using importlib as the Implementation of Import-Footnote-1878596
Ref: Using importlib as the Implementation of Import-Footnote-2878638
Ref: Using importlib as the Implementation of Import-Footnote-3878681
Ref: Using importlib as the Implementation of Import-Footnote-4878724
Ref: Using importlib as the Implementation of Import-Footnote-5878767
Node: New APIs878816
Ref: whatsnew/3 3 new-apis878932
Ref: 9b5878932
Node: Visible Changes880774
Ref: whatsnew/3 3 visible-changes880890
Ref: 9bf880890
Ref: Visible Changes-Footnote-1882744
Ref: Visible Changes-Footnote-2882793
Node: Other Language Changes<6>882842
Ref: whatsnew/3 3 other-language-changes883020
Ref: 9c1883020
Ref: Other Language Changes<6>-Footnote-1884980
Ref: Other Language Changes<6>-Footnote-2885023
Ref: Other Language Changes<6>-Footnote-3885066
Ref: Other Language Changes<6>-Footnote-4885109
Ref: Other Language Changes<6>-Footnote-5885152
Ref: Other Language Changes<6>-Footnote-6885195
Ref: Other Language Changes<6>-Footnote-7885238
Ref: Other Language Changes<6>-Footnote-8885281
Node: A Finer-Grained Import Lock885324
Ref: whatsnew/3 3 a-finer-grained-import-lock885482
Ref: 9c5885482
Ref: A Finer-Grained Import Lock-Footnote-1886225
Node: Builtin functions and types886267
Ref: whatsnew/3 3 builtin-functions-and-types886414
Ref: 9c7886414
Ref: Builtin functions and types-Footnote-1887647
Node: New Modules<6>887689
Ref: whatsnew/3 3 new-modules887828
Ref: 9cb887828
Node: faulthandler<3>887954
Ref: whatsnew/3 3 faulthandler888041
Ref: 9cc888041
Node: ipaddress<4>888966
Ref: whatsnew/3 3 ipaddress889069
Ref: 9ce889069
Ref: ipaddress<4>-Footnote-1889413
Node: lzma<2>889462
Ref: whatsnew/3 3 lzma889541
Ref: 9cf889541
Ref: lzma<2>-Footnote-1889853
Node: Improved Modules<6>889895
Ref: whatsnew/3 3 improved-modules890023
Ref: 9d0890023
Node: abc<2>891290
Ref: whatsnew/3 3 abc891369
Ref: 9d1891369
Ref: abc<2>-Footnote-1892401
Ref: abc<2>-Footnote-2892444
Node: array<2>892487
Ref: whatsnew/3 3 array892584
Ref: 9d7892584
Ref: array<2>-Footnote-1892822
Node: base64<2>892867
Ref: whatsnew/3 3 base64892969
Ref: 9d8892969
Ref: base64<2>-Footnote-1893267
Node: binascii<3>893310
Ref: whatsnew/3 3 binascii893410
Ref: 9d9893410
Ref: binascii<3>-Footnote-1893664
Node: bz2<2>893707
Ref: whatsnew/3 3 bz2893804
Ref: 9da893804
Ref: bz2<2>-Footnote-1894775
Ref: bz2<2>-Footnote-2894817
Node: codecs894859
Ref: whatsnew/3 3 codecs894959
Ref: 9dd894959
Ref: codecs-Footnote-1896279
Ref: codecs-Footnote-2896322
Ref: codecs-Footnote-3896365
Node: collections<7>896408
Ref: whatsnew/3 3 collections896515
Ref: 9de896515
Ref: collections<7>-Footnote-1897280
Ref: collections<7>-Footnote-2897323
Ref: collections<7>-Footnote-3897366
Ref: collections<7>-Footnote-4897409
Node: contextlib<5>897452
Ref: whatsnew/3 3 contextlib897561
Ref: 9e0897561
Ref: contextlib<5>-Footnote-1898155
Node: crypt<2>898198
Ref: whatsnew/3 3 crypt898302
Ref: 9e1898302
Ref: crypt<2>-Footnote-1898515
Node: curses<3>898558
Ref: whatsnew/3 3 curses898660
Ref: 9e2898660
Ref: curses<3>-Footnote-1899518
Node: datetime<4>899560
Ref: whatsnew/3 3 datetime899664
Ref: 9e6899664
Ref: datetime<4>-Footnote-1900382
Node: decimal<3>900425
Ref: whatsnew/3 3 decimal900528
Ref: 9e8900528
Ref: whatsnew/3 3 new-decimal900528
Ref: 983900528
Ref: decimal<3>-Footnote-1902231
Node: Features<2>902273
Ref: whatsnew/3 3 id1902354
Ref: 9e9902354
Node: API changes<2>902726
Ref: whatsnew/3 3 id2902807
Ref: 9ec902807
Node: email<4>905581
Ref: whatsnew/3 3 email905679
Ref: 9f7905679
Ref: whatsnew/3 3 new-email905679
Ref: 984905679
Node: Policy Framework905808
Ref: whatsnew/3 3 policy-framework905916
Ref: 9f8905916
Node: Provisional Policy with New Header API908924
Ref: whatsnew/3 3 provisional-policy-with-new-header-api909058
Ref: 9fc909058
Node: Other API Changes913694
Ref: whatsnew/3 3 other-api-changes913803
Ref: a00913803
Node: ftplib914694
Ref: whatsnew/3 3 ftplib914794
Ref: a07914794
Ref: ftplib-Footnote-1915701
Ref: ftplib-Footnote-2915743
Ref: ftplib-Footnote-3915786
Node: functools<5>915829
Ref: whatsnew/3 3 functools915926
Ref: a0d915926
Ref: functools<5>-Footnote-1916272
Node: gc<4>916315
Ref: whatsnew/3 3 gc916413
Ref: a0e916413
Node: hmac<3>916585
Ref: whatsnew/3 3 hmac916678
Ref: a10916678
Ref: hmac<3>-Footnote-1916942
Node: http<3>916985
Ref: whatsnew/3 3 http917080
Ref: a12917080
Ref: http<3>-Footnote-1917758
Ref: http<3>-Footnote-2917800
Ref: http<3>-Footnote-3917843
Node: html<2>917886
Ref: whatsnew/3 3 html917984
Ref: a19917984
Ref: html<2>-Footnote-1918982
Ref: html<2>-Footnote-2919025
Ref: html<2>-Footnote-3919068
Ref: html<2>-Footnote-4919111
Ref: html<2>-Footnote-5919154
Ref: html<2>-Footnote-6919197
Ref: html<2>-Footnote-7919242
Ref: html<2>-Footnote-8919286
Ref: html<2>-Footnote-9919329
Ref: html<2>-Footnote-10919372
Ref: html<2>-Footnote-11919418
Ref: html<2>-Footnote-12919463
Ref: html<2>-Footnote-13919507
Ref: html<2>-Footnote-14919551
Ref: html<2>-Footnote-15919594
Ref: html<2>-Footnote-16919638
Node: imaplib<2>919682
Ref: whatsnew/3 3 imaplib919783
Ref: a1b919783
Ref: imaplib<2>-Footnote-1920023
Node: inspect<5>920065
Ref: whatsnew/3 3 inspect920164
Ref: a1d920164
Ref: inspect<5>-Footnote-1920874
Ref: inspect<5>-Footnote-2920917
Node: io<4>920960
Ref: whatsnew/3 3 io921061
Ref: a20921061
Ref: io<4>-Footnote-1921708
Node: itertools<3>921751
Ref: whatsnew/3 3 itertools921852
Ref: a21921852
Node: logging<6>922008
Ref: whatsnew/3 3 logging922111
Ref: a22922111
Node: math<5>922562
Ref: whatsnew/3 3 math922660
Ref: a24922660
Ref: math<5>-Footnote-1922883
Node: mmap<3>922926
Ref: whatsnew/3 3 mmap923032
Ref: a26923032
Ref: mmap<3>-Footnote-1923367
Node: multiprocessing<6>923410
Ref: whatsnew/3 3 multiprocessing923516
Ref: a28923516
Ref: multiprocessing<6>-Footnote-1924666
Ref: multiprocessing<6>-Footnote-2924709
Ref: multiprocessing<6>-Footnote-3924751
Ref: multiprocessing<6>-Footnote-4924793
Node: nntplib924836
Ref: whatsnew/3 3 nntplib924940
Ref: a30924940
Ref: nntplib-Footnote-1925503
Node: os<7>925545
Ref: whatsnew/3 3 os925637
Ref: a32925637
Ref: os<7>-Footnote-1933007
Ref: os<7>-Footnote-2933050
Ref: os<7>-Footnote-3933092
Ref: os<7>-Footnote-4933135
Ref: os<7>-Footnote-5933178
Ref: os<7>-Footnote-6933221
Ref: os<7>-Footnote-7933263
Ref: os<7>-Footnote-8933306
Ref: os<7>-Footnote-9933349
Ref: os<7>-Footnote-10933392
Ref: os<7>-Footnote-11933435
Node: pdb<4>933479
Ref: whatsnew/3 3 pdb933573
Ref: a6c933573
Ref: pdb<4>-Footnote-1933854
Node: pickle<5>933897
Ref: whatsnew/3 3 pickle933994
Ref: a6d933994
Ref: pickle<5>-Footnote-1934262
Node: pydoc<4>934305
Ref: whatsnew/3 3 pydoc934401
Ref: a6f934401
Node: re<6>934598
Ref: whatsnew/3 3 re934690
Ref: a70934690
Ref: re<6>-Footnote-1934884
Node: sched934926
Ref: whatsnew/3 3 sched935019
Ref: a71935019
Ref: sched-Footnote-1936151
Ref: sched-Footnote-2936194
Ref: sched-Footnote-3936236
Ref: sched-Footnote-4936279
Ref: sched-Footnote-5936322
Node: select<2>936365
Ref: whatsnew/3 3 select936461
Ref: a76936461
Ref: select<2>-Footnote-1936724
Node: shlex<3>936766
Ref: whatsnew/3 3 shlex936866
Ref: a77936866
Node: shutil<4>937177
Ref: whatsnew/3 3 shutil937277
Ref: a79937277
Ref: shutil<4>-Footnote-1939143
Ref: shutil<4>-Footnote-2939186
Ref: shutil<4>-Footnote-3939229
Ref: shutil<4>-Footnote-4939272
Ref: shutil<4>-Footnote-5939315
Ref: shutil<4>-Footnote-6939358
Ref: shutil<4>-Footnote-7939401
Ref: shutil<4>-Footnote-8939443
Node: signal<3>939485
Ref: whatsnew/3 3 signal939585
Ref: a7d939585
Ref: signal<3>-Footnote-1940650
Node: smtpd<3>940692
Ref: whatsnew/3 3 smtpd940793
Ref: a84940793
Ref: smtpd<3>-Footnote-1941279
Ref: smtpd<3>-Footnote-2941328
Ref: smtpd<3>-Footnote-3941377
Node: smtplib<3>941419
Ref: whatsnew/3 3 smtplib941520
Ref: a85941520
Ref: smtplib<3>-Footnote-1942271
Ref: smtplib<3>-Footnote-2942314
Ref: smtplib<3>-Footnote-3942357
Node: socket<7>942399
Ref: whatsnew/3 3 socket942507
Ref: a8a942507
Ref: socket<7>-Footnote-1943749
Ref: socket<7>-Footnote-2943791
Ref: socket<7>-Footnote-3943834
Ref: socket<7>-Footnote-4943877
Node: socketserver<3>943920
Ref: whatsnew/3 3 socketserver944028
Ref: a8d944028
Ref: socketserver<3>-Footnote-1944401
Node: sqlite3<5>944444
Ref: whatsnew/3 3 sqlite3944549
Ref: a91944549
Ref: sqlite3<5>-Footnote-1944824
Node: ssl<8>944867
Ref: whatsnew/3 3 ssl944964
Ref: a93944964
Ref: ssl<8>-Footnote-1947181
Ref: ssl<8>-Footnote-2947224
Ref: ssl<8>-Footnote-3947267
Ref: ssl<8>-Footnote-4947310
Ref: ssl<8>-Footnote-5947353
Ref: ssl<8>-Footnote-6947396
Ref: ssl<8>-Footnote-7947439
Ref: ssl<8>-Footnote-8947482
Ref: ssl<8>-Footnote-9947525
Ref: ssl<8>-Footnote-10947568
Ref: ssl<8>-Footnote-11947612
Node: stat<2>947656
Ref: whatsnew/3 3 stat947752
Ref: aa1947752
Ref: stat<2>-Footnote-1948047
Node: struct<3>948090
Ref: whatsnew/3 3 struct948193
Ref: aa3948193
Ref: struct<3>-Footnote-1948440
Node: subprocess<5>948482
Ref: whatsnew/3 3 subprocess948584
Ref: aa4948584
Ref: subprocess<5>-Footnote-1948919
Ref: subprocess<5>-Footnote-2948961
Node: sys<7>949003
Ref: whatsnew/3 3 sys949106
Ref: aa6949106
Ref: sys<7>-Footnote-1949324
Node: tarfile<4>949367
Ref: whatsnew/3 3 tarfile949465
Ref: aa9949465
Ref: tarfile<4>-Footnote-1949673
Node: tempfile949715
Ref: whatsnew/3 3 tempfile949818
Ref: aaa949818
Ref: tempfile-Footnote-1950045
Node: textwrap<2>950087
Ref: whatsnew/3 3 textwrap950192
Ref: aac950192
Ref: textwrap<2>-Footnote-1950437
Node: threading<5>950480
Ref: whatsnew/3 3 threading950584
Ref: aae950584
Ref: threading<5>-Footnote-1951515
Ref: threading<5>-Footnote-2951558
Node: time<5>951600
Ref: whatsnew/3 3 time951701
Ref: ab5951701
Ref: time<5>-Footnote-1952668
Ref: time<5>-Footnote-2952717
Node: types<4>952760
Ref: whatsnew/3 3 types952860
Ref: aba952860
Ref: types<4>-Footnote-1953196
Ref: types<4>-Footnote-2953239
Ref: types<4>-Footnote-3953288
Node: unittest<5>953331
Ref: whatsnew/3 3 unittest953433
Ref: abe953433
Ref: unittest<5>-Footnote-1953846
Node: urllib<3>953889
Ref: whatsnew/3 3 urllib953993
Ref: ac5953993
Ref: urllib<3>-Footnote-1954345
Node: webbrowser954390
Ref: whatsnew/3 3 webbrowser954504
Ref: ac7954504
Ref: webbrowser-Footnote-1955042
Ref: webbrowser-Footnote-2955085
Node: xml etree ElementTree955128
Ref: whatsnew/3 3 xml-etree-elementtree955240
Ref: ac8955240
Node: zlib<2>955759
Ref: whatsnew/3 3 zlib955852
Ref: aca955852
Ref: zlib<2>-Footnote-1956324
Ref: zlib<2>-Footnote-2956367
Node: Optimizations<5>956410
Ref: whatsnew/3 3 optimizations956550
Ref: acd956550
Ref: Optimizations<5>-Footnote-1957361
Ref: Optimizations<5>-Footnote-2957410
Ref: Optimizations<5>-Footnote-3957453
Ref: Optimizations<5>-Footnote-4957496
Node: Build and C API Changes<4>957539
Ref: whatsnew/3 3 build-and-c-api-changes957673
Ref: 98c957673
Ref: Build and C API Changes<4>-Footnote-1959546
Ref: Build and C API Changes<4>-Footnote-2959595
Ref: Build and C API Changes<4>-Footnote-3959644
Node: Deprecated<5>959687
Ref: whatsnew/3 3 deprecated959826
Ref: aec959826
Node: Unsupported Operating Systems<2>960163
Ref: whatsnew/3 3 unsupported-operating-systems960304
Ref: aed960304
Node: Deprecated Python modules functions and methods<4>960658
Ref: whatsnew/3 3 deprecated-python-modules-functions-and-methods960854
Ref: aee960854
Ref: Deprecated Python modules functions and methods<4>-Footnote-1963192
Ref: Deprecated Python modules functions and methods<4>-Footnote-2963234
Ref: Deprecated Python modules functions and methods<4>-Footnote-3963283
Ref: Deprecated Python modules functions and methods<4>-Footnote-4963326
Ref: Deprecated Python modules functions and methods<4>-Footnote-5963369
Node: Deprecated functions and types of the C API<3>963412
Ref: whatsnew/3 3 deprecated-functions-and-types-of-the-c-api963595
Ref: af2963595
Ref: Deprecated functions and types of the C API<3>-Footnote-1966735
Node: Deprecated features966784
Ref: whatsnew/3 3 deprecated-features966908
Ref: b15966908
Node: Porting to Python 3 3967131
Ref: whatsnew/3 3 porting-to-python-3-3967235
Ref: b16967235
Node: Porting Python code967512
Ref: whatsnew/3 3 porting-python-code967612
Ref: 9b4967612
Ref: whatsnew/3 3 portingpythoncode967612
Ref: b17967612
Ref: Porting Python code-Footnote-1974640
Ref: Porting Python code-Footnote-2974683
Ref: Porting Python code-Footnote-3974726
Ref: Porting Python code-Footnote-4974769
Ref: Porting Python code-Footnote-5974818
Ref: Porting Python code-Footnote-6974867
Ref: Porting Python code-Footnote-7974909
Ref: Porting Python code-Footnote-8974954
Ref: Porting Python code-Footnote-9974997
Ref: Porting Python code-Footnote-10975039
Node: Porting C code975083
Ref: whatsnew/3 3 porting-c-code975213
Ref: 98d975213
Ref: Porting C code-Footnote-1976705
Node: Building C extensions976754
Ref: whatsnew/3 3 building-c-extensions976892
Ref: b27976892
Ref: Building C extensions-Footnote-1977490
Node: Command Line Switch Changes977533
Ref: whatsnew/3 3 command-line-switch-changes977648
Ref: b28977648
Ref: Command Line Switch Changes-Footnote-1978213
Ref: Command Line Switch Changes-Footnote-2978256
Node: What's New In Python 3 2978299
Ref: whatsnew/3 2 doc978454
Ref: b2a978454
Ref: whatsnew/3 2 what-s-new-in-python-3-2978454
Ref: b2b978454
Ref: What's New In Python 3 2-Footnote-1979801
Ref: What's New In Python 3 2-Footnote-2979900
Node: PEP 384 Defining a Stable ABI979949
Ref: whatsnew/3 2 pep-384-defining-a-stable-abi980092
Ref: b2c980092
Ref: PEP 384 Defining a Stable ABI-Footnote-1981182
Node: PEP 389 Argparse Command Line Parsing Module981231
Ref: whatsnew/3 2 pep-389-argparse-command-line-parsing-module981433
Ref: b2d981433
Ref: PEP 389 Argparse Command Line Parsing Module-Footnote-1985558
Node: PEP 391 Dictionary Based Configuration for Logging985607
Ref: whatsnew/3 2 pep-391-dictionary-based-configuration-for-logging985818
Ref: b2f985818
Ref: PEP 391 Dictionary Based Configuration for Logging-Footnote-1988108
Node: PEP 3148 The concurrent futures module988157
Ref: whatsnew/3 2 pep-3148-the-concurrent-futures-module988359
Ref: b31988359
Ref: PEP 3148 The concurrent futures module-Footnote-1991056
Node: PEP 3147 PYC Repository Directories991105
Ref: whatsnew/3 2 pep-3147-pyc-repository-directories991293
Ref: b36991293
Ref: PEP 3147 PYC Repository Directories-Footnote-1994338
Node: PEP 3149 ABI Version Tagged so Files994387
Ref: whatsnew/3 2 pep-3149-abi-version-tagged-so-files994588
Ref: b39994588
Ref: PEP 3149 ABI Version Tagged so Files-Footnote-1995825
Node: PEP 3333 Python Web Server Gateway Interface v1 0 1995874
Ref: whatsnew/3 2 pep-3333-python-web-server-gateway-interface-v1-0-1996065
Ref: b3a996065
Ref: PEP 3333 Python Web Server Gateway Interface v1 0 1-Footnote-1998426
Ref: PEP 3333 Python Web Server Gateway Interface v1 0 1-Footnote-2998475
Ref: PEP 3333 Python Web Server Gateway Interface v1 0 1-Footnote-3998524
Node: Other Language Changes<7>998573
Ref: whatsnew/3 2 other-language-changes998763
Ref: b3d998763
Ref: Other Language Changes<7>-Footnote-11008262
Ref: Other Language Changes<7>-Footnote-21008304
Ref: Other Language Changes<7>-Footnote-31008346
Ref: Other Language Changes<7>-Footnote-41008391
Ref: Other Language Changes<7>-Footnote-51008433
Ref: Other Language Changes<7>-Footnote-61008475
Ref: Other Language Changes<7>-Footnote-71008517
Ref: Other Language Changes<7>-Footnote-81008559
Ref: Other Language Changes<7>-Footnote-91008601
Ref: Other Language Changes<7>-Footnote-101008643
Ref: Other Language Changes<7>-Footnote-111008687
Ref: Other Language Changes<7>-Footnote-121008732
Ref: Other Language Changes<7>-Footnote-131008775
Ref: Other Language Changes<7>-Footnote-141008818
Ref: Other Language Changes<7>-Footnote-151008862
Ref: Other Language Changes<7>-Footnote-161008906
Node: New Improved and Deprecated Modules1008949
Ref: whatsnew/3 2 new-improved-and-deprecated-modules1009103
Ref: b4a1009103
Node: email<5>1011129
Ref: whatsnew/3 2 email1011229
Ref: b4b1011229
Ref: email<5>-Footnote-11013203
Ref: email<5>-Footnote-21013252
Ref: email<5>-Footnote-31013294
Node: elementtree1013337
Ref: whatsnew/3 2 elementtree1013458
Ref: b531013458
Ref: elementtree-Footnote-11014936
Ref: elementtree-Footnote-21014992
Node: functools<6>1015034
Ref: whatsnew/3 2 functools1015159
Ref: b5a1015159
Ref: functools<6>-Footnote-11018614
Ref: functools<6>-Footnote-21018666
Ref: functools<6>-Footnote-31018718
Ref: functools<6>-Footnote-41018761
Ref: functools<6>-Footnote-51018804
Ref: functools<6>-Footnote-61018846
Ref: functools<6>-Footnote-71018888
Ref: functools<6>-Footnote-81018930
Node: itertools<4>1018982
Ref: whatsnew/3 2 itertools1019110
Ref: b5c1019110
Node: collections<8>1019800
Ref: whatsnew/3 2 collections1019928
Ref: b5e1019928
Ref: collections<8>-Footnote-11022170
Ref: collections<8>-Footnote-21022230
Node: threading<6>1022277
Ref: whatsnew/3 2 threading1022410
Ref: b631022410
Ref: threading<6>-Footnote-11025171
Ref: threading<6>-Footnote-21025232
Ref: threading<6>-Footnote-31025330
Ref: threading<6>-Footnote-41025402
Node: datetime and time1025444
Ref: whatsnew/3 2 datetime-and-time1025570
Ref: b671025570
Ref: datetime and time-Footnote-11028358
Ref: datetime and time-Footnote-21028403
Ref: datetime and time-Footnote-31028445
Ref: datetime and time-Footnote-41028487
Ref: datetime and time-Footnote-51028529
Ref: datetime and time-Footnote-61028574
Ref: datetime and time-Footnote-71028616
Node: math<6>1028659
Ref: whatsnew/3 2 math1028779
Ref: b6b1028779
Ref: math<6>-Footnote-11030656
Node: abc<3>1030709
Ref: whatsnew/3 2 abc1030817
Ref: b701030817
Ref: abc<3>-Footnote-11031439
Node: io<5>1031481
Ref: whatsnew/3 2 io1031589
Ref: b711031589
Ref: io<5>-Footnote-11032754
Node: reprlib1032796
Ref: whatsnew/3 2 reprlib1032908
Ref: b731032908
Ref: reprlib-Footnote-11033893
Ref: reprlib-Footnote-21033935
Node: logging<7>1033977
Ref: whatsnew/3 2 logging1034090
Ref: b761034090
Node: csv<3>1035929
Ref: whatsnew/3 2 csv1036048
Ref: b7d1036048
Ref: csv<3>-Footnote-11036909
Ref: csv<3>-Footnote-21036951
Node: contextlib<6>1036996
Ref: whatsnew/3 2 contextlib1037126
Ref: b811037126
Ref: contextlib<6>-Footnote-11039339
Node: decimal and fractions1039381
Ref: whatsnew/3 2 decimal-and-fractions1039508
Ref: b841039508
Ref: decimal and fractions-Footnote-11041930
Ref: decimal and fractions-Footnote-21041972
Ref: decimal and fractions-Footnote-31042014
Ref: decimal and fractions-Footnote-41042056
Ref: decimal and fractions-Footnote-51042098
Ref: decimal and fractions-Footnote-61042140
Node: ftp1042182
Ref: whatsnew/3 2 ftp1042301
Ref: b881042301
Ref: ftp-Footnote-11043643
Ref: ftp-Footnote-21043685
Ref: ftp-Footnote-31043727
Ref: ftp-Footnote-41043769
Node: popen1043811
Ref: whatsnew/3 2 popen1043918
Ref: b891043918
Ref: popen-Footnote-11044223
Ref: popen-Footnote-21044265
Node: select<3>1044308
Ref: whatsnew/3 2 select1044428
Ref: b8a1044428
Ref: select<3>-Footnote-11044859
Node: gzip and zipfile1044901
Ref: whatsnew/3 2 gzip-and-zipfile1045026
Ref: b8c1045026
Ref: gzip and zipfile-Footnote-11046581
Ref: gzip and zipfile-Footnote-21046623
Ref: gzip and zipfile-Footnote-31046665
Ref: gzip and zipfile-Footnote-41046710
Ref: gzip and zipfile-Footnote-51046752
Ref: gzip and zipfile-Footnote-61046794
Node: tarfile<5>1046836
Ref: whatsnew/3 2 tarfile1046962
Ref: b901046962
Ref: tarfile<5>-Footnote-11048533
Node: hashlib<3>1048575
Ref: whatsnew/3 2 hashlib1048691
Ref: b931048691
Ref: hashlib<3>-Footnote-11049446
Node: ast<3>1049488
Ref: whatsnew/3 2 ast1049599
Ref: b941049599
Node: os<8>1050536
Ref: whatsnew/3 2 os1050646
Ref: b961050646
Node: shutil<5>1051415
Ref: whatsnew/3 2 shutil1051529
Ref: b9a1051529
Node: sqlite3<6>1053696
Ref: whatsnew/3 2 sqlite31053812
Ref: b9d1053812
Ref: sqlite3<6>-Footnote-11054457
Node: html<3>1054499
Ref: whatsnew/3 2 html1054615
Ref: ba01054615
Node: socket<8>1054901
Ref: whatsnew/3 2 socket1055013
Ref: ba11055013
Ref: socket<8>-Footnote-11055655
Ref: socket<8>-Footnote-21055697
Node: ssl<9>1055739
Ref: whatsnew/3 2 ssl1055848
Ref: ba41055848
Ref: ssl<9>-Footnote-11057942
Ref: ssl<9>-Footnote-21057991
Ref: ssl<9>-Footnote-31058076
Ref: ssl<9>-Footnote-41058118
Ref: ssl<9>-Footnote-51058160
Ref: ssl<9>-Footnote-61058202
Ref: ssl<9>-Footnote-71058244
Ref: ssl<9>-Footnote-81058286
Ref: ssl<9>-Footnote-91058328
Node: nntp1058370
Ref: whatsnew/3 2 nntp1058482
Ref: ba91058482
Ref: nntp-Footnote-11059052
Ref: nntp-Footnote-21059094
Node: certificates1059136
Ref: whatsnew/3 2 certificates1059252
Ref: bac1059252
Ref: certificates-Footnote-11059647
Node: imaplib<3>1059689
Ref: whatsnew/3 2 imaplib1059815
Ref: bae1059815
Ref: imaplib<3>-Footnote-11060086
Node: http client<4>1060128
Ref: whatsnew/3 2 http-client1060253
Ref: bb01060253
Ref: http client<4>-Footnote-11061675
Node: unittest<6>1061718
Ref: whatsnew/3 2 unittest1061842
Ref: bb31061842
Ref: unittest<6>-Footnote-11066615
Ref: unittest<6>-Footnote-21066658
Ref: unittest<6>-Footnote-31066700
Node: random<2>1066742
Ref: whatsnew/3 2 random1066861
Ref: bbf1066861
Ref: random<2>-Footnote-11067523
Node: poplib<3>1067565
Ref: whatsnew/3 2 poplib1067684
Ref: bc51067684
Ref: poplib<3>-Footnote-11068036
Node: asyncore<2>1068078
Ref: whatsnew/3 2 asyncore1068199
Ref: bc71068199
Ref: asyncore<2>-Footnote-11068675
Node: tempfile<2>1068717
Ref: whatsnew/3 2 tempfile1068839
Ref: bcc1068839
Ref: tempfile<2>-Footnote-11069246
Node: inspect<6>1069288
Ref: whatsnew/3 2 inspect1069407
Ref: bce1069407
Ref: inspect<6>-Footnote-11070765
Node: pydoc<5>1070808
Ref: whatsnew/3 2 pydoc1070922
Ref: bd11070922
Ref: pydoc<5>-Footnote-11071239
Node: dis<3>1071281
Ref: whatsnew/3 2 dis1071391
Ref: bd21071391
Ref: dis<3>-Footnote-11073539
Node: dbm<6>1073581
Ref: whatsnew/3 2 dbm1073692
Ref: bd41073692
Ref: dbm<6>-Footnote-11073879
Node: ctypes<2>1073921
Ref: whatsnew/3 2 ctypes1074033
Ref: bd51074033
Node: site<2>1074149
Ref: whatsnew/3 2 site1074267
Ref: bd71074267
Ref: site<2>-Footnote-11075496
Node: sysconfig<2>1075538
Ref: whatsnew/3 2 sysconfig1075653
Ref: bdb1075653
Node: pdb<5>1077878
Ref: whatsnew/3 2 pdb1078001
Ref: bdf1078001
Node: configparser<2>1078899
Ref: whatsnew/3 2 configparser1079025
Ref: be01079025
Node: urllib parse<3>1081889
Ref: whatsnew/3 2 urllib-parse1082016
Ref: be21082016
Ref: urllib parse<3>-Footnote-11084024
Ref: urllib parse<3>-Footnote-21084067
Ref: urllib parse<3>-Footnote-31084116
Ref: urllib parse<3>-Footnote-41084158
Ref: urllib parse<3>-Footnote-51084200
Node: mailbox1084242
Ref: whatsnew/3 2 mailbox1084364
Ref: be61084364
Ref: mailbox-Footnote-11085936
Node: turtledemo1085978
Ref: whatsnew/3 2 turtledemo1086076
Ref: bed1086076
Ref: turtledemo-Footnote-11086511
Node: Multi-threading1086554
Ref: whatsnew/3 2 multi-threading1086699
Ref: bee1086699
Ref: Multi-threading-Footnote-11088328
Ref: Multi-threading-Footnote-21088407
Ref: Multi-threading-Footnote-31088449
Ref: Multi-threading-Footnote-41088493
Node: Optimizations<6>1088535
Ref: whatsnew/3 2 optimizations1088652
Ref: bf21088652
Ref: Optimizations<6>-Footnote-11092087
Ref: Optimizations<6>-Footnote-21092129
Ref: Optimizations<6>-Footnote-31092171
Ref: Optimizations<6>-Footnote-41092213
Ref: Optimizations<6>-Footnote-51092259
Ref: Optimizations<6>-Footnote-61092301
Ref: Optimizations<6>-Footnote-71092343
Ref: Optimizations<6>-Footnote-81092386
Ref: Optimizations<6>-Footnote-91092428
Ref: Optimizations<6>-Footnote-101092470
Ref: Optimizations<6>-Footnote-111092513
Ref: Optimizations<6>-Footnote-121092556
Ref: Optimizations<6>-Footnote-131092599
Ref: Optimizations<6>-Footnote-141092645
Ref: Optimizations<6>-Footnote-151092688
Ref: Optimizations<6>-Footnote-161092732
Node: Unicode1092775
Ref: whatsnew/3 2 unicode1092883
Ref: bf51092883
Ref: Unicode-Footnote-11093433
Ref: Unicode-Footnote-21093483
Ref: Unicode-Footnote-31093527
Node: Codecs1093598
Ref: whatsnew/3 2 codecs1093703
Ref: bf61093703
Ref: Codecs-Footnote-11094632
Node: Documentation1094677
Ref: whatsnew/3 2 documentation1094779
Ref: bf71094779
Ref: Documentation-Footnote-11096417
Ref: Documentation-Footnote-21096485
Ref: Documentation-Footnote-31096561
Ref: Documentation-Footnote-41096603
Node: IDLE1096645
Ref: whatsnew/3 2 idle1096756
Ref: bfb1096756
Ref: IDLE-Footnote-11097140
Ref: IDLE-Footnote-21097182
Node: Code Repository1097224
Ref: whatsnew/3 2 code-repository1097348
Ref: bfc1097348
Ref: Code Repository-Footnote-11097954
Ref: Code Repository-Footnote-21097993
Ref: Code Repository-Footnote-31098042
Ref: Code Repository-Footnote-41098096
Node: Build and C API Changes<5>1098140
Ref: whatsnew/3 2 build-and-c-api-changes1098281
Ref: bfd1098281
Ref: Build and C API Changes<5>-Footnote-11102418
Ref: Build and C API Changes<5>-Footnote-21102461
Ref: Build and C API Changes<5>-Footnote-31102503
Ref: Build and C API Changes<5>-Footnote-41102545
Ref: Build and C API Changes<5>-Footnote-51102587
Ref: Build and C API Changes<5>-Footnote-61102629
Ref: Build and C API Changes<5>-Footnote-71102671
Ref: Build and C API Changes<5>-Footnote-81102713
Ref: Build and C API Changes<5>-Footnote-91102755
Ref: Build and C API Changes<5>-Footnote-101102797
Ref: Build and C API Changes<5>-Footnote-111102840
Ref: Build and C API Changes<5>-Footnote-121102883
Ref: Build and C API Changes<5>-Footnote-131102926
Ref: Build and C API Changes<5>-Footnote-141102988
Ref: Build and C API Changes<5>-Footnote-151103068
Node: Porting to Python 3 21103125
Ref: whatsnew/3 2 porting-to-python-3-21103242
Ref: c061103242
Ref: Porting to Python 3 2-Footnote-11110061
Ref: Porting to Python 3 2-Footnote-21110103
Ref: Porting to Python 3 2-Footnote-31110145
Ref: Porting to Python 3 2-Footnote-41110190
Ref: Porting to Python 3 2-Footnote-51110233
Ref: Porting to Python 3 2-Footnote-61110276
Ref: Porting to Python 3 2-Footnote-71110319
Node: What's New In Python 3 11110361
Ref: whatsnew/3 1 doc1110516
Ref: c181110516
Ref: whatsnew/3 1 what-s-new-in-python-3-11110516
Ref: c191110516
Node: PEP 372 Ordered Dictionaries1111142
Ref: whatsnew/3 1 pep-372-ordered-dictionaries1111288
Ref: c1a1111288
Ref: PEP 372 Ordered Dictionaries-Footnote-11112836
Ref: PEP 372 Ordered Dictionaries-Footnote-21112863
Node: PEP 378 Format Specifier for Thousands Separator1112912
Ref: whatsnew/3 1 pep-378-format-specifier-for-thousands-separator1113092
Ref: c1b1113092
Ref: PEP 378 Format Specifier for Thousands Separator-Footnote-11114330
Node: Other Language Changes<8>1114379
Ref: whatsnew/3 1 other-language-changes1114569
Ref: c1c1114569
Ref: Other Language Changes<8>-Footnote-11119366
Ref: Other Language Changes<8>-Footnote-21119411
Ref: Other Language Changes<8>-Footnote-31119453
Ref: Other Language Changes<8>-Footnote-41119495
Ref: Other Language Changes<8>-Footnote-51119537
Ref: Other Language Changes<8>-Footnote-61119582
Ref: Other Language Changes<8>-Footnote-71119624
Node: New Improved and Deprecated Modules<2>1119666
Ref: whatsnew/3 1 new-improved-and-deprecated-modules1119824
Ref: c1d1119824
Ref: New Improved and Deprecated Modules<2>-Footnote-11128348
Ref: New Improved and Deprecated Modules<2>-Footnote-21128393
Ref: New Improved and Deprecated Modules<2>-Footnote-31128435
Ref: New Improved and Deprecated Modules<2>-Footnote-41128477
Ref: New Improved and Deprecated Modules<2>-Footnote-51128519
Ref: New Improved and Deprecated Modules<2>-Footnote-61128561
Ref: New Improved and Deprecated Modules<2>-Footnote-71128610
Ref: New Improved and Deprecated Modules<2>-Footnote-81128652
Ref: New Improved and Deprecated Modules<2>-Footnote-91128694
Ref: New Improved and Deprecated Modules<2>-Footnote-101128736
Ref: New Improved and Deprecated Modules<2>-Footnote-111128779
Ref: New Improved and Deprecated Modules<2>-Footnote-121128822
Ref: New Improved and Deprecated Modules<2>-Footnote-131128865
Node: Optimizations<7>1128908
Ref: whatsnew/3 1 optimizations1129048
Ref: c231129048
Ref: Optimizations<7>-Footnote-11131225
Ref: Optimizations<7>-Footnote-21131274
Ref: Optimizations<7>-Footnote-31131316
Ref: Optimizations<7>-Footnote-41131358
Ref: Optimizations<7>-Footnote-51131400
Ref: Optimizations<7>-Footnote-61131425
Ref: Optimizations<7>-Footnote-71131467
Node: IDLE<2>1131509
Ref: whatsnew/3 1 idle1131637
Ref: c241131637
Ref: IDLE<2>-Footnote-11131852
Node: Build and C API Changes<6>1131894
Ref: whatsnew/3 1 build-and-c-api-changes1132027
Ref: c251132027
Ref: Build and C API Changes<6>-Footnote-11134252
Ref: Build and C API Changes<6>-Footnote-21134294
Ref: Build and C API Changes<6>-Footnote-31134336
Ref: Build and C API Changes<6>-Footnote-41134378
Ref: Build and C API Changes<6>-Footnote-51134420
Node: Porting to Python 3 11134462
Ref: whatsnew/3 1 porting-to-python-3-11134579
Ref: c291134579
Node: What's New In Python 3 01135709
Ref: whatsnew/3 0 doc1135864
Ref: c2a1135864
Ref: whatsnew/3 0 what-s-new-in-python-3-01135864
Ref: c2b1135864
Node: Common Stumbling Blocks1137667
Ref: whatsnew/3 0 common-stumbling-blocks1137786
Ref: c2c1137786
Node: Print Is A Function1138154
Ref: whatsnew/3 0 print-is-a-function1138278
Ref: c2d1138278
Ref: Print Is A Function-Footnote-11139958
Node: Views And Iterators Instead Of Lists1140007
Ref: whatsnew/3 0 views-and-iterators-instead-of-lists1140160
Ref: c2e1140160
Node: Ordering Comparisons1141996
Ref: whatsnew/3 0 ordering-comparisons1142138
Ref: c381142138
Node: Integers1143585
Ref: whatsnew/3 0 integers1143731
Ref: c3a1143731
Ref: Integers-Footnote-11144949
Ref: Integers-Footnote-21144998
Node: Text Vs Data Instead Of Unicode Vs 8-bit1145047
Ref: whatsnew/3 0 text-vs-data-instead-of-unicode-vs-8-bit1145164
Ref: c3b1145164
Ref: Text Vs Data Instead Of Unicode Vs 8-bit-Footnote-11151744
Ref: Text Vs Data Instead Of Unicode Vs 8-bit-Footnote-21151793
Ref: Text Vs Data Instead Of Unicode Vs 8-bit-Footnote-31151842
Node: Overview Of Syntax Changes1151891
Ref: whatsnew/3 0 overview-of-syntax-changes1152056
Ref: c421152056
Node: New Syntax1152266
Ref: whatsnew/3 0 new-syntax1152362
Ref: c431152362
Ref: New Syntax-Footnote-11154908
Ref: New Syntax-Footnote-21154957
Ref: New Syntax-Footnote-31155006
Ref: New Syntax-Footnote-41155055
Ref: New Syntax-Footnote-51155104
Node: Changed Syntax1155153
Ref: whatsnew/3 0 changed-syntax1155272
Ref: c461155272
Ref: Changed Syntax-Footnote-11156965
Ref: Changed Syntax-Footnote-21157014
Ref: Changed Syntax-Footnote-31157063
Ref: Changed Syntax-Footnote-41157112
Node: Removed Syntax1157161
Ref: whatsnew/3 0 removed-syntax1157261
Ref: c481157261
Ref: Removed Syntax-Footnote-11158451
Ref: Removed Syntax-Footnote-21158500
Node: Changes Already Present In Python 2 61158549
Ref: whatsnew/3 0 changes-already-present-in-python-2-61158706
Ref: c4b1158706
Node: Library Changes1162539
Ref: whatsnew/3 0 library-changes1162714
Ref: c5e1162714
Ref: Library Changes-Footnote-11168938
Ref: Library Changes-Footnote-21168987
Ref: Library Changes-Footnote-31169036
Ref: Library Changes-Footnote-41169085
Ref: Library Changes-Footnote-51169134
Ref: Library Changes-Footnote-61169183
Node: PEP 3101 A New Approach To String Formatting1169232
Ref: whatsnew/3 0 pep-3101-a-new-approach-to-string-formatting1169391
Ref: c621169391
Ref: PEP 3101 A New Approach To String Formatting-Footnote-11169843
Node: Changes To Exceptions1169892
Ref: whatsnew/3 0 changes-to-exceptions1170063
Ref: c631170063
Ref: Changes To Exceptions-Footnote-11173567
Ref: Changes To Exceptions-Footnote-21173616
Ref: Changes To Exceptions-Footnote-31173665
Ref: Changes To Exceptions-Footnote-41173714
Ref: Changes To Exceptions-Footnote-51173763
Node: Miscellaneous Other Changes1173812
Ref: whatsnew/3 0 miscellaneous-other-changes1173965
Ref: c651173965
Node: Operators And Special Methods1174091
Ref: whatsnew/3 0 operators-and-special-methods1174201
Ref: c661174201
Ref: Operators And Special Methods-Footnote-11175837
Node: Builtins1175886
Ref: whatsnew/3 0 builtins1175996
Ref: c6e1175996
Ref: Builtins-Footnote-11178467
Ref: Builtins-Footnote-21178516
Node: Build and C API Changes<7>1178565
Ref: whatsnew/3 0 build-and-c-api-changes1178708
Ref: c761178708
Ref: Build and C API Changes<7>-Footnote-11179741
Ref: Build and C API Changes<7>-Footnote-21179790
Ref: Build and C API Changes<7>-Footnote-31179839
Node: Performance1179888
Ref: whatsnew/3 0 performance1180025
Ref: c791180025
Node: Porting To Python 3 01180344
Ref: whatsnew/3 0 porting-to-python-3-01180446
Ref: c7a1180446
Node: What's New in Python 2 71182045
Ref: whatsnew/2 7 doc1182200
Ref: c7d1182200
Ref: whatsnew/2 7 what-s-new-in-python-2-71182200
Ref: c7e1182200
Node: The Future for Python 2 x1184659
Ref: whatsnew/2 7 the-future-for-python-2-x1184801
Ref: c7f1184801
Ref: whatsnew/2 7 whatsnew27-python311184801
Ref: c801184801
Ref: The Future for Python 2 x-Footnote-11188153
Ref: The Future for Python 2 x-Footnote-21188202
Node: Changes to the Handling of Deprecation Warnings1188239
Ref: whatsnew/2 7 changes-to-the-handling-of-deprecation-warnings1188409
Ref: c831188409
Ref: Changes to the Handling of Deprecation Warnings-Footnote-11189984
Node: Python 3 1 Features1190026
Ref: whatsnew/2 7 python-3-1-features1190222
Ref: c841190222
Node: PEP 372 Adding an Ordered Dictionary to collections1192141
Ref: whatsnew/2 7 pep-03721192341
Ref: c851192341
Ref: whatsnew/2 7 pep-372-adding-an-ordered-dictionary-to-collections1192341
Ref: c881192341
Ref: PEP 372 Adding an Ordered Dictionary to collections-Footnote-11195944
Ref: PEP 372 Adding an Ordered Dictionary to collections-Footnote-21195971
Node: PEP 378 Format Specifier for Thousands Separator<2>1196020
Ref: whatsnew/2 7 pep-03781196254
Ref: c861196254
Ref: whatsnew/2 7 pep-378-format-specifier-for-thousands-separator1196254
Ref: c8a1196254
Ref: PEP 378 Format Specifier for Thousands Separator<2>-Footnote-11197762
Node: PEP 389 The argparse Module for Parsing Command Lines1197811
Ref: whatsnew/2 7 pep-389-the-argparse-module-for-parsing-command-lines1198044
Ref: c8b1198044
Ref: PEP 389 The argparse Module for Parsing Command Lines-Footnote-11202067
Node: PEP 391 Dictionary-Based Configuration For Logging1202116
Ref: whatsnew/2 7 pep-391-dictionary-based-configuration-for-logging1202323
Ref: c8c1202323
Ref: PEP 391 Dictionary-Based Configuration For Logging-Footnote-11206182
Node: PEP 3106 Dictionary Views1206231
Ref: whatsnew/2 7 pep-3106-dictionary-views1206415
Ref: c921206415
Ref: PEP 3106 Dictionary Views-Footnote-11208531
Ref: PEP 3106 Dictionary Views-Footnote-21208580
Node: PEP 3137 The memoryview Object1208622
Ref: whatsnew/2 7 pep-3137-the-memoryview-object1208781
Ref: c931208781
Ref: PEP 3137 The memoryview Object-Footnote-11210445
Ref: PEP 3137 The memoryview Object-Footnote-21210494
Node: Other Language Changes<9>1210536
Ref: whatsnew/2 7 other-language-changes1210694
Ref: c941210694
Ref: Other Language Changes<9>-Footnote-11220642
Ref: Other Language Changes<9>-Footnote-21220684
Ref: Other Language Changes<9>-Footnote-31220726
Ref: Other Language Changes<9>-Footnote-41220768
Ref: Other Language Changes<9>-Footnote-51220810
Ref: Other Language Changes<9>-Footnote-61220852
Ref: Other Language Changes<9>-Footnote-71220894
Ref: Other Language Changes<9>-Footnote-81220936
Ref: Other Language Changes<9>-Footnote-91220978
Ref: Other Language Changes<9>-Footnote-101221020
Ref: Other Language Changes<9>-Footnote-111221063
Ref: Other Language Changes<9>-Footnote-121221106
Ref: Other Language Changes<9>-Footnote-131221149
Ref: Other Language Changes<9>-Footnote-141221192
Ref: Other Language Changes<9>-Footnote-151221238
Ref: Other Language Changes<9>-Footnote-161221281
Ref: Other Language Changes<9>-Footnote-171221324
Ref: Other Language Changes<9>-Footnote-181221367
Ref: Other Language Changes<9>-Footnote-191221413
Ref: Other Language Changes<9>-Footnote-201221456
Ref: Other Language Changes<9>-Footnote-211221499
Ref: Other Language Changes<9>-Footnote-221221542
Ref: Other Language Changes<9>-Footnote-231221585
Ref: Other Language Changes<9>-Footnote-241221628
Node: Interpreter Changes1221671
Ref: whatsnew/2 7 interpreter-changes1221777
Ref: c971221777
Ref: whatsnew/2 7 new-27-interpreter1221777
Ref: c981221777
Ref: Interpreter Changes-Footnote-11222431
Node: Optimizations<8>1222473
Ref: whatsnew/2 7 optimizations1222579
Ref: c991222579
Ref: Optimizations<8>-Footnote-11227426
Ref: Optimizations<8>-Footnote-21227468
Ref: Optimizations<8>-Footnote-31227510
Ref: Optimizations<8>-Footnote-41227552
Ref: Optimizations<8>-Footnote-51227594
Ref: Optimizations<8>-Footnote-61227636
Ref: Optimizations<8>-Footnote-71227681
Ref: Optimizations<8>-Footnote-81227723
Ref: Optimizations<8>-Footnote-91227765
Ref: Optimizations<8>-Footnote-101227807
Ref: Optimizations<8>-Footnote-111227850
Ref: Optimizations<8>-Footnote-121227893
Ref: Optimizations<8>-Footnote-131227936
Node: New and Improved Modules1227979
Ref: whatsnew/2 7 new-and-improved-modules1228133
Ref: c9c1228133
Ref: New and Improved Modules-Footnote-11263306
Ref: New and Improved Modules-Footnote-21263348
Ref: New and Improved Modules-Footnote-31263390
Ref: New and Improved Modules-Footnote-41263443
Ref: New and Improved Modules-Footnote-51263485
Ref: New and Improved Modules-Footnote-61263527
Ref: New and Improved Modules-Footnote-71263572
Ref: New and Improved Modules-Footnote-81263614
Ref: New and Improved Modules-Footnote-91263656
Ref: New and Improved Modules-Footnote-101263698
Ref: New and Improved Modules-Footnote-111263741
Ref: New and Improved Modules-Footnote-121263784
Ref: New and Improved Modules-Footnote-131263827
Ref: New and Improved Modules-Footnote-141263867
Ref: New and Improved Modules-Footnote-151263910
Ref: New and Improved Modules-Footnote-161263953
Ref: New and Improved Modules-Footnote-171263996
Ref: New and Improved Modules-Footnote-181264039
Ref: New and Improved Modules-Footnote-191264082
Ref: New and Improved Modules-Footnote-201264125
Ref: New and Improved Modules-Footnote-211264168
Ref: New and Improved Modules-Footnote-221264211
Ref: New and Improved Modules-Footnote-231264254
Ref: New and Improved Modules-Footnote-241264297
Ref: New and Improved Modules-Footnote-251264340
Ref: New and Improved Modules-Footnote-261264383
Ref: New and Improved Modules-Footnote-271264429
Ref: New and Improved Modules-Footnote-281264472
Ref: New and Improved Modules-Footnote-291264515
Ref: New and Improved Modules-Footnote-301264558
Ref: New and Improved Modules-Footnote-311264601
Ref: New and Improved Modules-Footnote-321264644
Ref: New and Improved Modules-Footnote-331264687
Ref: New and Improved Modules-Footnote-341264730
Ref: New and Improved Modules-Footnote-351264773
Ref: New and Improved Modules-Footnote-361264816
Ref: New and Improved Modules-Footnote-371264859
Ref: New and Improved Modules-Footnote-381264902
Ref: New and Improved Modules-Footnote-391264945
Ref: New and Improved Modules-Footnote-401264988
Ref: New and Improved Modules-Footnote-411265031
Ref: New and Improved Modules-Footnote-421265074
Ref: New and Improved Modules-Footnote-431265117
Ref: New and Improved Modules-Footnote-441265160
Ref: New and Improved Modules-Footnote-451265203
Ref: New and Improved Modules-Footnote-461265246
Ref: New and Improved Modules-Footnote-471265289
Ref: New and Improved Modules-Footnote-481265332
Ref: New and Improved Modules-Footnote-491265378
Ref: New and Improved Modules-Footnote-501265421
Ref: New and Improved Modules-Footnote-511265464
Ref: New and Improved Modules-Footnote-521265507
Ref: New and Improved Modules-Footnote-531265550
Ref: New and Improved Modules-Footnote-541265593
Ref: New and Improved Modules-Footnote-551265636
Ref: New and Improved Modules-Footnote-561265679
Ref: New and Improved Modules-Footnote-571265722
Ref: New and Improved Modules-Footnote-581265765
Ref: New and Improved Modules-Footnote-591265808
Ref: New and Improved Modules-Footnote-601265851
Ref: New and Improved Modules-Footnote-611265894
Ref: New and Improved Modules-Footnote-621265937
Ref: New and Improved Modules-Footnote-631265980
Ref: New and Improved Modules-Footnote-641266023
Ref: New and Improved Modules-Footnote-651266066
Ref: New and Improved Modules-Footnote-661266109
Ref: New and Improved Modules-Footnote-671266152
Ref: New and Improved Modules-Footnote-681266195
Ref: New and Improved Modules-Footnote-691266238
Ref: New and Improved Modules-Footnote-701266284
Ref: New and Improved Modules-Footnote-711266327
Ref: New and Improved Modules-Footnote-721266370
Ref: New and Improved Modules-Footnote-731266456
Ref: New and Improved Modules-Footnote-741266499
Ref: New and Improved Modules-Footnote-751266542
Ref: New and Improved Modules-Footnote-761266585
Ref: New and Improved Modules-Footnote-771266628
Ref: New and Improved Modules-Footnote-781266671
Ref: New and Improved Modules-Footnote-791266717
Ref: New and Improved Modules-Footnote-801266760
Ref: New and Improved Modules-Footnote-811266803
Ref: New and Improved Modules-Footnote-821266846
Ref: New and Improved Modules-Footnote-831266889
Ref: New and Improved Modules-Footnote-841266932
Ref: New and Improved Modules-Footnote-851266975
Ref: New and Improved Modules-Footnote-861267021
Ref: New and Improved Modules-Footnote-871267067
Ref: New and Improved Modules-Footnote-881267110
Ref: New and Improved Modules-Footnote-891267160
Ref: New and Improved Modules-Footnote-901267210
Ref: New and Improved Modules-Footnote-911267253
Ref: New and Improved Modules-Footnote-921267296
Ref: New and Improved Modules-Footnote-931267339
Ref: New and Improved Modules-Footnote-941267382
Ref: New and Improved Modules-Footnote-951267425
Ref: New and Improved Modules-Footnote-961267468
Ref: New and Improved Modules-Footnote-971267511
Node: New module importlib1267554
Ref: whatsnew/2 7 importlib-section1267664
Ref: c871267664
Ref: whatsnew/2 7 new-module-importlib1267664
Ref: cc11267664
Node: New module sysconfig1269204
Ref: whatsnew/2 7 new-module-sysconfig1269348
Ref: cc21269348
Node: ttk Themed Widgets for Tk1270674
Ref: whatsnew/2 7 ttk-themed-widgets-for-tk1270821
Ref: cc51270821
Ref: ttk Themed Widgets for Tk-Footnote-11271889
Ref: ttk Themed Widgets for Tk-Footnote-21271931
Node: Updated module unittest1271973
Ref: whatsnew/2 7 unittest-section1272130
Ref: cc61272130
Ref: whatsnew/2 7 updated-module-unittest1272130
Ref: cc71272130
Ref: Updated module unittest-Footnote-11280984
Ref: Updated module unittest-Footnote-21281010
Ref: Updated module unittest-Footnote-31281047
Ref: Updated module unittest-Footnote-41281089
Ref: Updated module unittest-Footnote-51281131
Ref: Updated module unittest-Footnote-61281176
Ref: Updated module unittest-Footnote-71281218
Ref: Updated module unittest-Footnote-81281260
Ref: Updated module unittest-Footnote-91281302
Ref: Updated module unittest-Footnote-101281344
Ref: Updated module unittest-Footnote-111281387
Ref: Updated module unittest-Footnote-121281430
Ref: Updated module unittest-Footnote-131281473
Ref: Updated module unittest-Footnote-141281516
Node: Updated module ElementTree 1 31281559
Ref: whatsnew/2 7 elementtree-section1281682
Ref: cea1281682
Ref: whatsnew/2 7 updated-module-elementtree-1-31281682
Ref: ceb1281682
Ref: Updated module ElementTree 1 3-Footnote-11285625
Node: Build and C API Changes<8>1285667
Ref: whatsnew/2 7 build-and-c-api-changes1285819
Ref: ced1285819
Ref: Build and C API Changes<8>-Footnote-11294482
Ref: Build and C API Changes<8>-Footnote-21294552
Ref: Build and C API Changes<8>-Footnote-31294594
Ref: Build and C API Changes<8>-Footnote-41294636
Ref: Build and C API Changes<8>-Footnote-51294678
Ref: Build and C API Changes<8>-Footnote-61294720
Ref: Build and C API Changes<8>-Footnote-71294762
Ref: Build and C API Changes<8>-Footnote-81294804
Ref: Build and C API Changes<8>-Footnote-91294873
Ref: Build and C API Changes<8>-Footnote-101294915
Ref: Build and C API Changes<8>-Footnote-111294958
Ref: Build and C API Changes<8>-Footnote-121295001
Ref: Build and C API Changes<8>-Footnote-131295044
Ref: Build and C API Changes<8>-Footnote-141295090
Ref: Build and C API Changes<8>-Footnote-151295136
Ref: Build and C API Changes<8>-Footnote-161295179
Ref: Build and C API Changes<8>-Footnote-171295222
Ref: Build and C API Changes<8>-Footnote-181295265
Ref: Build and C API Changes<8>-Footnote-191295308
Ref: Build and C API Changes<8>-Footnote-201295351
Ref: Build and C API Changes<8>-Footnote-211295397
Ref: Build and C API Changes<8>-Footnote-221295440
Node: Capsules1295483
Ref: whatsnew/2 7 capsules1295592
Ref: cf31295592
Ref: whatsnew/2 7 whatsnew27-capsules1295592
Ref: cf41295592
Ref: Capsules-Footnote-11297591
Node: Port-Specific Changes Windows1297633
Ref: whatsnew/2 7 port-specific-changes-windows1297781
Ref: cf71297781
Ref: Port-Specific Changes Windows-Footnote-11299473
Ref: Port-Specific Changes Windows-Footnote-21299515
Ref: Port-Specific Changes Windows-Footnote-31299557
Ref: Port-Specific Changes Windows-Footnote-41299599
Ref: Port-Specific Changes Windows-Footnote-51299644
Ref: Port-Specific Changes Windows-Footnote-61299686
Node: Port-Specific Changes Mac OS X1299728
Ref: whatsnew/2 7 port-specific-changes-mac-os-x1299897
Ref: cf91299897
Ref: Port-Specific Changes Mac OS X-Footnote-11300932
Ref: Port-Specific Changes Mac OS X-Footnote-21300974
Node: Port-Specific Changes FreeBSD1301017
Ref: whatsnew/2 7 port-specific-changes-freebsd1301148
Ref: cfa1301148
Ref: Port-Specific Changes FreeBSD-Footnote-11301508
Node: Other Changes and Fixes1301550
Ref: whatsnew/2 7 other-changes-and-fixes1301699
Ref: cfb1301699
Ref: Other Changes and Fixes-Footnote-11303887
Ref: Other Changes and Fixes-Footnote-21303929
Ref: Other Changes and Fixes-Footnote-31303974
Ref: Other Changes and Fixes-Footnote-41304016
Ref: Other Changes and Fixes-Footnote-51304058
Node: Porting to Python 2 71304100
Ref: whatsnew/2 7 porting-to-python-2-71304276
Ref: cfc1304276
Ref: Porting to Python 2 7-Footnote-11309840
Ref: Porting to Python 2 7-Footnote-21309882
Ref: Porting to Python 2 7-Footnote-31309924
Ref: Porting to Python 2 7-Footnote-41309966
Ref: Porting to Python 2 7-Footnote-51310008
Ref: Porting to Python 2 7-Footnote-61310050
Ref: Porting to Python 2 7-Footnote-71310092
Ref: Porting to Python 2 7-Footnote-81310134
Ref: Porting to Python 2 7-Footnote-91310176
Ref: Porting to Python 2 7-Footnote-101310218
Ref: Porting to Python 2 7-Footnote-111310261
Ref: Porting to Python 2 7-Footnote-121310304
Ref: Porting to Python 2 7-Footnote-131310347
Ref: Porting to Python 2 7-Footnote-141310397
Node: New Features Added to Python 2 7 Maintenance Releases1310440
Ref: whatsnew/2 7 new-features-added-to-python-2-7-maintenance-releases1310609
Ref: cfd1310609
Ref: whatsnew/2 7 py27-maintenance-enhancements1310609
Ref: c811310609
Node: Two new environment variables for debug mode1312074
Ref: whatsnew/2 7 two-new-environment-variables-for-debug-mode1312268
Ref: cfe1312268
Ref: Two new environment variables for debug mode-Footnote-11312945
Ref: Two new environment variables for debug mode-Footnote-21312988
Node: PEP 434 IDLE Enhancement Exception for All Branches1313031
Ref: whatsnew/2 7 pep-434-idle-enhancement-exception-for-all-branches1313286
Ref: cff1313286
Ref: PEP 434 IDLE Enhancement Exception for All Branches-Footnote-11313806
Node: PEP 466 Network Security Enhancements for Python 2 71313855
Ref: whatsnew/2 7 pep-466-network-security-enhancements-for-python-2-71314114
Ref: d001314114
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-11316339
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-21316388
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-31316437
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-41316480
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-51316523
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-61316572
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-71316615
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-81316658
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-91316707
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-101316750
Ref: PEP 466 Network Security Enhancements for Python 2 7-Footnote-111316794
Node: PEP 477 Backport ensurepip PEP 453 to Python 2 71316838
Ref: whatsnew/2 7 pep-477-backport-ensurepip-pep-453-to-python-2-71317125
Ref: d031317125
Ref: PEP 477 Backport ensurepip PEP 453 to Python 2 7-Footnote-11317621
Ref: PEP 477 Backport ensurepip PEP 453 to Python 2 7-Footnote-21317670
Node: Bootstrapping pip By Default<2>1317719
Ref: whatsnew/2 7 bootstrapping-pip-by-default1317868
Ref: d041317868
Ref: Bootstrapping pip By Default<2>-Footnote-11319536
Ref: Bootstrapping pip By Default<2>-Footnote-21319585
Node: Documentation Changes<2>1319683
Ref: whatsnew/2 7 documentation-changes1319832
Ref: d051319832
Ref: whatsnew/2 7 id11319832
Ref: d061319832
Ref: Documentation Changes<2>-Footnote-11320752
Ref: Documentation Changes<2>-Footnote-21320788
Node: PEP 476 Enabling certificate verification by default for stdlib http clients<2>1320837
Ref: whatsnew/2 7 pep-476-enabling-certificate-verification-by-default-for-stdlib-http-clients1321129
Ref: d071321129
Ref: PEP 476 Enabling certificate verification by default for stdlib http clients<2>-Footnote-11322210
Node: PEP 493 HTTPS verification migration tools for Python 2 71322259
Ref: whatsnew/2 7 pep-493-https-verification-migration-tools-for-python-2-71322537
Ref: d081322537
Ref: PEP 493 HTTPS verification migration tools for Python 2 7-Footnote-11323701
Node: New make regen-all build target<3>1323750
Ref: whatsnew/2 7 new-make-regen-all-build-target1323986
Ref: d091323986
Ref: New make regen-all build target<3>-Footnote-11324774
Ref: New make regen-all build target<3>-Footnote-21324841
Node: Removal of make touch build target<3>1324884
Ref: whatsnew/2 7 removal-of-make-touch-build-target1325054
Ref: d0a1325054
Ref: Removal of make touch build target<3>-Footnote-11325480
Node: Acknowledgements1325523
Ref: whatsnew/2 7 acknowledgements1325662
Ref: d0b1325662
Ref: whatsnew/2 7 acks271325662
Ref: d0c1325662
Node: What's New in Python 2 61325935
Ref: whatsnew/2 6 doc1326090
Ref: d0d1326090
Ref: whatsnew/2 6 what-s-new-in-python-2-61326090
Ref: d0e1326090
Ref: whatsnew/2 6 whats-new-in-2-61326090
Ref: c4c1326090
Ref: What's New in Python 2 6-Footnote-11329145
Node: Python 3 01329194
Ref: whatsnew/2 6 python-3-01329308
Ref: d0f1329308
Ref: Python 3 0-Footnote-11331421
Ref: Python 3 0-Footnote-21331470
Node: Changes to the Development Process1331519
Ref: whatsnew/2 6 changes-to-the-development-process1331670
Ref: d101331670
Node: New Issue Tracker Roundup1332188
Ref: whatsnew/2 6 new-issue-tracker-roundup1332347
Ref: d111332347
Ref: New Issue Tracker Roundup-Footnote-11334389
Ref: New Issue Tracker Roundup-Footnote-21334438
Ref: New Issue Tracker Roundup-Footnote-31334469
Ref: New Issue Tracker Roundup-Footnote-41334509
Ref: New Issue Tracker Roundup-Footnote-51334544
Node: New Documentation Format reStructuredText Using Sphinx1334585
Ref: whatsnew/2 6 new-documentation-format-restructuredtext-using-sphinx1334744
Ref: d121334744
Ref: New Documentation Format reStructuredText Using Sphinx-Footnote-11336853
Ref: New Documentation Format reStructuredText Using Sphinx-Footnote-21336912
Ref: New Documentation Format reStructuredText Using Sphinx-Footnote-31336961
Ref: New Documentation Format reStructuredText Using Sphinx-Footnote-41336992
Node: PEP 343 The 'with' statement1337032
Ref: whatsnew/2 6 pep-03431337225
Ref: c4d1337225
Ref: whatsnew/2 6 pep-343-the-with-statement1337225
Ref: d131337225
Node: Writing Context Managers1340499
Ref: whatsnew/2 6 new-26-context-managers1340618
Ref: c4e1340618
Ref: whatsnew/2 6 writing-context-managers1340618
Ref: d141340618
Node: The contextlib module1345127
Ref: whatsnew/2 6 new-module-contextlib1345246
Ref: c4f1345246
Ref: whatsnew/2 6 the-contextlib-module1345246
Ref: d151345246
Ref: The contextlib module-Footnote-11347743
Node: PEP 366 Explicit Relative Imports From a Main Module1347792
Ref: whatsnew/2 6 pep-03661347991
Ref: c501347991
Ref: whatsnew/2 6 pep-366-explicit-relative-imports-from-a-main-module1347991
Ref: d161347991
Node: PEP 370 Per-user site-packages Directory1348754
Ref: whatsnew/2 6 pep-03701348960
Ref: c511348960
Ref: whatsnew/2 6 pep-370-per-user-site-packages-directory1348960
Ref: d181348960
Ref: PEP 370 Per-user site-packages Directory-Footnote-11350418
Node: PEP 371 The multiprocessing Package1350467
Ref: whatsnew/2 6 pep-03711350656
Ref: c521350656
Ref: whatsnew/2 6 pep-371-the-multiprocessing-package1350656
Ref: d1c1350656
Ref: PEP 371 The multiprocessing Package-Footnote-11355794
Node: PEP 3101 Advanced String Formatting1355843
Ref: whatsnew/2 6 pep-31011356020
Ref: c531356020
Ref: whatsnew/2 6 pep-3101-advanced-string-formatting1356020
Ref: d1e1356020
Ref: PEP 3101 Advanced String Formatting-Footnote-11361732
Node: PEP 3105 print As a Function1361781
Ref: whatsnew/2 6 pep-31051361958
Ref: c541361958
Ref: whatsnew/2 6 pep-3105-print-as-a-function1361958
Ref: d201361958
Ref: PEP 3105 print As a Function-Footnote-11363111
Node: PEP 3110 Exception-Handling Changes1363160
Ref: whatsnew/2 6 pep-31101363324
Ref: c551363324
Ref: whatsnew/2 6 pep-3110-exception-handling-changes1363324
Ref: d211363324
Ref: PEP 3110 Exception-Handling Changes-Footnote-11364908
Node: PEP 3112 Byte Literals1364957
Ref: whatsnew/2 6 pep-31121365117
Ref: c561365117
Ref: whatsnew/2 6 pep-3112-byte-literals1365117
Ref: d221365117
Ref: PEP 3112 Byte Literals-Footnote-11368130
Node: PEP 3116 New I/O Library1368179
Ref: whatsnew/2 6 pep-31161368336
Ref: c571368336
Ref: whatsnew/2 6 pep-3116-new-i-o-library1368336
Ref: d281368336
Ref: PEP 3116 New I/O Library-Footnote-11371961
Node: PEP 3118 Revised Buffer Protocol1372010
Ref: whatsnew/2 6 pep-31181372175
Ref: c581372175
Ref: whatsnew/2 6 pep-3118-revised-buffer-protocol1372175
Ref: d291372175
Ref: PEP 3118 Revised Buffer Protocol-Footnote-11374313
Node: PEP 3119 Abstract Base Classes1374362
Ref: whatsnew/2 6 pep-31191374546
Ref: c591374546
Ref: whatsnew/2 6 pep-3119-abstract-base-classes1374546
Ref: d2b1374546
Ref: PEP 3119 Abstract Base Classes-Footnote-11379910
Node: PEP 3127 Integer Literal Support and Syntax1379959
Ref: whatsnew/2 6 pep-31271380136
Ref: c5a1380136
Ref: whatsnew/2 6 pep-3127-integer-literal-support-and-syntax1380136
Ref: d2e1380136
Ref: PEP 3127 Integer Literal Support and Syntax-Footnote-11381468
Node: PEP 3129 Class Decorators1381517
Ref: whatsnew/2 6 pep-31291381701
Ref: c5b1381701
Ref: whatsnew/2 6 pep-3129-class-decorators1381701
Ref: d2f1381701
Ref: PEP 3129 Class Decorators-Footnote-11382100
Node: PEP 3141 A Type Hierarchy for Numbers1382149
Ref: whatsnew/2 6 pep-31411382316
Ref: c5c1382316
Ref: whatsnew/2 6 pep-3141-a-type-hierarchy-for-numbers1382316
Ref: d301382316
Ref: PEP 3141 A Type Hierarchy for Numbers-Footnote-11384516
Ref: PEP 3141 A Type Hierarchy for Numbers-Footnote-21384565
Ref: PEP 3141 A Type Hierarchy for Numbers-Footnote-31384663
Node: The fractions Module1384748
Ref: whatsnew/2 6 the-fractions-module1384842
Ref: d341384842
Node: Other Language Changes<10>1386449
Ref: whatsnew/2 6 other-language-changes1386618
Ref: d351386618
Ref: Other Language Changes<10>-Footnote-11395467
Ref: Other Language Changes<10>-Footnote-21395512
Ref: Other Language Changes<10>-Footnote-31395554
Ref: Other Language Changes<10>-Footnote-41395599
Ref: Other Language Changes<10>-Footnote-51395641
Ref: Other Language Changes<10>-Footnote-61395683
Ref: Other Language Changes<10>-Footnote-71395725
Ref: Other Language Changes<10>-Footnote-81395767
Ref: Other Language Changes<10>-Footnote-91395809
Ref: Other Language Changes<10>-Footnote-101395851
Ref: Other Language Changes<10>-Footnote-111395894
Ref: Other Language Changes<10>-Footnote-121395937
Ref: Other Language Changes<10>-Footnote-131395983
Ref: Other Language Changes<10>-Footnote-141396029
Ref: Other Language Changes<10>-Footnote-151396075
Ref: Other Language Changes<10>-Footnote-161396121
Node: Optimizations<9>1396167
Ref: whatsnew/2 6 optimizations1396277
Ref: d391396277
Ref: Optimizations<9>-Footnote-11399133
Ref: Optimizations<9>-Footnote-21399178
Ref: Optimizations<9>-Footnote-31399223
Ref: Optimizations<9>-Footnote-41399265
Node: Interpreter Changes<2>1399307
Ref: whatsnew/2 6 interpreter-changes1399417
Ref: d3a1399417
Ref: whatsnew/2 6 new-26-interpreter1399417
Ref: d3b1399417
Node: New and Improved Modules<2>1400991
Ref: whatsnew/2 6 new-and-improved-modules1401148
Ref: d3f1401148
Ref: New and Improved Modules<2>-Footnote-11443556
Ref: New and Improved Modules<2>-Footnote-21443601
Ref: New and Improved Modules<2>-Footnote-31443654
Ref: New and Improved Modules<2>-Footnote-41443696
Ref: New and Improved Modules<2>-Footnote-51443740
Ref: New and Improved Modules<2>-Footnote-61443782
Ref: New and Improved Modules<2>-Footnote-71443827
Ref: New and Improved Modules<2>-Footnote-81443869
Ref: New and Improved Modules<2>-Footnote-91443922
Ref: New and Improved Modules<2>-Footnote-101443967
Ref: New and Improved Modules<2>-Footnote-111444013
Ref: New and Improved Modules<2>-Footnote-121444059
Ref: New and Improved Modules<2>-Footnote-131444102
Ref: New and Improved Modules<2>-Footnote-141444145
Ref: New and Improved Modules<2>-Footnote-151444190
Ref: New and Improved Modules<2>-Footnote-161444233
Ref: New and Improved Modules<2>-Footnote-171444279
Ref: New and Improved Modules<2>-Footnote-181444322
Ref: New and Improved Modules<2>-Footnote-191444368
Ref: New and Improved Modules<2>-Footnote-201444414
Ref: New and Improved Modules<2>-Footnote-211444460
Ref: New and Improved Modules<2>-Footnote-221444505
Ref: New and Improved Modules<2>-Footnote-231444551
Ref: New and Improved Modules<2>-Footnote-241444597
Ref: New and Improved Modules<2>-Footnote-251444640
Ref: New and Improved Modules<2>-Footnote-261444683
Ref: New and Improved Modules<2>-Footnote-271444729
Ref: New and Improved Modules<2>-Footnote-281444775
Ref: New and Improved Modules<2>-Footnote-291444820
Ref: New and Improved Modules<2>-Footnote-301444863
Ref: New and Improved Modules<2>-Footnote-311444906
Ref: New and Improved Modules<2>-Footnote-321444949
Ref: New and Improved Modules<2>-Footnote-331444992
Ref: New and Improved Modules<2>-Footnote-341445035
Ref: New and Improved Modules<2>-Footnote-351445078
Ref: New and Improved Modules<2>-Footnote-361445121
Ref: New and Improved Modules<2>-Footnote-371445171
Ref: New and Improved Modules<2>-Footnote-381445216
Ref: New and Improved Modules<2>-Footnote-391445266
Ref: New and Improved Modules<2>-Footnote-401445311
Ref: New and Improved Modules<2>-Footnote-411445354
Ref: New and Improved Modules<2>-Footnote-421445399
Ref: New and Improved Modules<2>-Footnote-431445445
Ref: New and Improved Modules<2>-Footnote-441445488
Ref: New and Improved Modules<2>-Footnote-451445531
Ref: New and Improved Modules<2>-Footnote-461445574
Ref: New and Improved Modules<2>-Footnote-471445620
Ref: New and Improved Modules<2>-Footnote-481445663
Ref: New and Improved Modules<2>-Footnote-491445706
Ref: New and Improved Modules<2>-Footnote-501445752
Ref: New and Improved Modules<2>-Footnote-511445795
Ref: New and Improved Modules<2>-Footnote-521445841
Ref: New and Improved Modules<2>-Footnote-531445884
Ref: New and Improved Modules<2>-Footnote-541445930
Ref: New and Improved Modules<2>-Footnote-551445973
Ref: New and Improved Modules<2>-Footnote-561446019
Ref: New and Improved Modules<2>-Footnote-571446062
Ref: New and Improved Modules<2>-Footnote-581446108
Ref: New and Improved Modules<2>-Footnote-591446154
Ref: New and Improved Modules<2>-Footnote-601446197
Ref: New and Improved Modules<2>-Footnote-611446240
Ref: New and Improved Modules<2>-Footnote-621446285
Ref: New and Improved Modules<2>-Footnote-631446331
Node: The ast module1446377
Ref: whatsnew/2 6 the-ast-module1446490
Ref: d4f1446490
Node: The future_builtins module1449151
Ref: whatsnew/2 6 the-future-builtins-module1449315
Ref: d501449315
Node: The json module JavaScript Object Notation1450430
Ref: whatsnew/2 6 the-json-module-javascript-object-notation1450622
Ref: d521450622
Node: The plistlib module A Property-List Parser1451634
Ref: whatsnew/2 6 the-plistlib-module-a-property-list-parser1451819
Ref: d531451819
Node: ctypes Enhancements1453190
Ref: whatsnew/2 6 ctypes-enhancements1453353
Ref: d541453353
Ref: ctypes Enhancements-Footnote-11455120
Ref: ctypes Enhancements-Footnote-21455165
Node: Improved SSL Support1455207
Ref: whatsnew/2 6 improved-ssl-support1455319
Ref: d551455319
Ref: Improved SSL Support-Footnote-11456271
Node: Deprecations and Removals1456304
Ref: whatsnew/2 6 deprecations-and-removals1456461
Ref: d561456461
Ref: Deprecations and Removals-Footnote-11458316
Node: Build and C API Changes<9>1458365
Ref: whatsnew/2 6 build-and-c-api-changes1458516
Ref: d581458516
Ref: Build and C API Changes<9>-Footnote-11464545
Ref: Build and C API Changes<9>-Footnote-21464587
Ref: Build and C API Changes<9>-Footnote-31464632
Ref: Build and C API Changes<9>-Footnote-41464674
Ref: Build and C API Changes<9>-Footnote-51464716
Node: Port-Specific Changes Windows<2>1464761
Ref: whatsnew/2 6 port-specific-changes-windows1464898
Ref: d5f1464898
Ref: Port-Specific Changes Windows<2>-Footnote-11467300
Ref: Port-Specific Changes Windows<2>-Footnote-21467344
Ref: Port-Specific Changes Windows<2>-Footnote-31467389
Node: Port-Specific Changes Mac OS X<2>1467431
Ref: whatsnew/2 6 port-specific-changes-mac-os-x1467603
Ref: d601467603
Ref: Port-Specific Changes Mac OS X<2>-Footnote-11468874
Node: Port-Specific Changes IRIX1468919
Ref: whatsnew/2 6 port-specific-changes-irix1469050
Ref: d611469050
Node: Porting to Python 2 61469569
Ref: whatsnew/2 6 porting-to-python-2-61469714
Ref: d621469714
Ref: Porting to Python 2 6-Footnote-11473139
Ref: Porting to Python 2 6-Footnote-21473184
Ref: Porting to Python 2 6-Footnote-31473229
Node: Acknowledgements<2>1473274
Ref: whatsnew/2 6 acknowledgements1473384
Ref: d651473384
Ref: whatsnew/2 6 acks1473384
Ref: d661473384
Node: What's New in Python 2 51473726
Ref: whatsnew/2 5 doc1473881
Ref: d671473881
Ref: whatsnew/2 5 what-s-new-in-python-2-51473881
Ref: d681473881
Ref: What's New in Python 2 5-Footnote-11477476
Node: PEP 308 Conditional Expressions1477525
Ref: whatsnew/2 5 pep-3081477662
Ref: d691477662
Ref: whatsnew/2 5 pep-308-conditional-expressions1477662
Ref: d6e1477662
Ref: PEP 308 Conditional Expressions-Footnote-11481142
Ref: PEP 308 Conditional Expressions-Footnote-21481191
Node: PEP 309 Partial Function Application1481240
Ref: whatsnew/2 5 pep-3091481436
Ref: d6f1481436
Ref: whatsnew/2 5 pep-309-partial-function-application1481436
Ref: d701481436
Ref: PEP 309 Partial Function Application-Footnote-11484278
Node: PEP 314 Metadata for Python Software Packages v1 11484327
Ref: whatsnew/2 5 pep-3141484529
Ref: d711484529
Ref: whatsnew/2 5 pep-314-metadata-for-python-software-packages-v1-11484529
Ref: d721484529
Ref: PEP 314 Metadata for Python Software Packages v1 1-Footnote-11486362
Node: PEP 328 Absolute and Relative Imports1486411
Ref: whatsnew/2 5 pep-3281486613
Ref: d6c1486613
Ref: whatsnew/2 5 pep-328-absolute-and-relative-imports1486613
Ref: d731486613
Ref: PEP 328 Absolute and Relative Imports-Footnote-11490424
Ref: PEP 328 Absolute and Relative Imports-Footnote-21490473
Node: PEP 338 Executing Modules as Scripts1490522
Ref: whatsnew/2 5 pep-3381490708
Ref: d741490708
Ref: whatsnew/2 5 pep-338-executing-modules-as-scripts1490708
Ref: d751490708
Ref: PEP 338 Executing Modules as Scripts-Footnote-11491602
Node: PEP 341 Unified try/except/finally1491651
Ref: whatsnew/2 5 pep-3411491830
Ref: d6d1491830
Ref: whatsnew/2 5 pep-341-unified-try-except-finally1491830
Ref: d761491830
Ref: PEP 341 Unified try/except/finally-Footnote-11493596
Node: PEP 342 New Generator Features1493645
Ref: whatsnew/2 5 pep-3421493819
Ref: d6b1493819
Ref: whatsnew/2 5 pep-342-new-generator-features1493819
Ref: d781493819
Ref: PEP 342 New Generator Features-Footnote-11500435
Ref: PEP 342 New Generator Features-Footnote-21500484
Ref: PEP 342 New Generator Features-Footnote-31500533
Ref: PEP 342 New Generator Features-Footnote-41500582
Ref: PEP 342 New Generator Features-Footnote-51500631
Node: PEP 343 The 'with' statement<2>1500680
Ref: whatsnew/2 5 pep-3431500859
Ref: d6a1500859
Ref: whatsnew/2 5 pep-343-the-with-statement1500859
Ref: d791500859
Node: Writing Context Managers<2>1503881
Ref: whatsnew/2 5 new-25-context-managers1504009
Ref: d7a1504009
Ref: whatsnew/2 5 writing-context-managers1504009
Ref: d7b1504009
Node: The contextlib module<2>1508401
Ref: whatsnew/2 5 contextlibmod1508529
Ref: d7c1508529
Ref: whatsnew/2 5 the-contextlib-module1508529
Ref: d7d1508529
Ref: The contextlib module<2>-Footnote-11511017
Node: PEP 352 Exceptions as New-Style Classes1511066
Ref: whatsnew/2 5 pep-3521511254
Ref: d7e1511254
Ref: whatsnew/2 5 pep-352-exceptions-as-new-style-classes1511254
Ref: d7f1511254
Ref: PEP 352 Exceptions as New-Style Classes-Footnote-11513735
Node: PEP 353 Using ssize_t as the index type1513784
Ref: whatsnew/2 5 pep-3531513971
Ref: d811513971
Ref: whatsnew/2 5 pep-353-using-ssize-t-as-the-index-type1513971
Ref: d821513971
Ref: PEP 353 Using ssize_t as the index type-Footnote-11516882
Ref: PEP 353 Using ssize_t as the index type-Footnote-21516931
Node: PEP 357 The '__index__' method1516980
Ref: whatsnew/2 5 pep-3571517154
Ref: d841517154
Ref: whatsnew/2 5 pep-357-the-index-method1517154
Ref: d851517154
Ref: PEP 357 The '__index__' method-Footnote-11518881
Node: Other Language Changes<11>1518930
Ref: whatsnew/2 5 other-lang1519097
Ref: d871519097
Ref: whatsnew/2 5 other-language-changes1519097
Ref: d881519097
Ref: Other Language Changes<11>-Footnote-11526051
Node: Interactive Interpreter Changes1526100
Ref: whatsnew/2 5 interactive1526220
Ref: d8e1526220
Ref: whatsnew/2 5 interactive-interpreter-changes1526220
Ref: d8f1526220
Node: Optimizations<10>1527000
Ref: whatsnew/2 5 optimizations1527120
Ref: d921527120
Ref: whatsnew/2 5 opts1527120
Ref: d931527120
Node: New Improved and Removed Modules1530934
Ref: whatsnew/2 5 modules1531098
Ref: d941531098
Ref: whatsnew/2 5 new-improved-and-removed-modules1531098
Ref: d951531098
Ref: New Improved and Removed Modules-Footnote-11555590
Ref: New Improved and Removed Modules-Footnote-21555639
Ref: New Improved and Removed Modules-Footnote-31555688
Node: The ctypes package1555737
Ref: whatsnew/2 5 module-ctypes1555856
Ref: da21555856
Ref: whatsnew/2 5 the-ctypes-package1555856
Ref: da31555856
Node: The ElementTree package1559072
Ref: whatsnew/2 5 module-etree1559219
Ref: da41559219
Ref: whatsnew/2 5 the-elementtree-package1559219
Ref: da51559219
Node: The hashlib package1564430
Ref: whatsnew/2 5 module-hashlib1564578
Ref: da61564578
Ref: whatsnew/2 5 the-hashlib-package1564578
Ref: da71564578
Node: The sqlite3 package1566162
Ref: whatsnew/2 5 module-sqlite1566306
Ref: da81566306
Ref: whatsnew/2 5 the-sqlite3-package1566306
Ref: da91566306
Ref: The sqlite3 package-Footnote-11570314
Ref: The sqlite3 package-Footnote-21570363
Node: The wsgiref package1570412
Ref: whatsnew/2 5 module-wsgiref1570528
Ref: daa1570528
Ref: whatsnew/2 5 the-wsgiref-package1570528
Ref: dab1570528
Ref: The wsgiref package-Footnote-11571448
Ref: The wsgiref package-Footnote-21571497
Node: Build and C API Changes<10>1571546
Ref: whatsnew/2 5 build-and-c-api-changes1571705
Ref: dac1571705
Ref: whatsnew/2 5 build-api1571705
Ref: dad1571705
Ref: Build and C API Changes<10>-Footnote-11578724
Ref: Build and C API Changes<10>-Footnote-21578773
Ref: Build and C API Changes<10>-Footnote-31578822
Node: Port-Specific Changes1578871
Ref: whatsnew/2 5 port-specific-changes1578956
Ref: db71578956
Ref: whatsnew/2 5 ports1578956
Ref: db81578956
Ref: Port-Specific Changes-Footnote-11579633
Node: Porting to Python 2 51579675
Ref: whatsnew/2 5 porting1579821
Ref: db91579821
Ref: whatsnew/2 5 porting-to-python-2-51579821
Ref: dba1579821
Ref: Porting to Python 2 5-Footnote-11582644
Node: Acknowledgements<3>1582693
Ref: whatsnew/2 5 acknowledgements1582803
Ref: dbb1582803
Node: What's New in Python 2 41583297
Ref: whatsnew/2 4 doc1583452
Ref: dbc1583452
Ref: whatsnew/2 4 what-s-new-in-python-2-41583452
Ref: dbd1583452
Node: PEP 218 Built-In Set Objects1585557
Ref: whatsnew/2 4 pep-218-built-in-set-objects1585698
Ref: dbe1585698
Ref: PEP 218 Built-In Set Objects-Footnote-11587933
Node: PEP 237 Unifying Long Integers and Integers1587982
Ref: whatsnew/2 4 pep-237-unifying-long-integers-and-integers1588161
Ref: dbf1588161
Ref: PEP 237 Unifying Long Integers and Integers-Footnote-11589201
Node: PEP 289 Generator Expressions1589250
Ref: whatsnew/2 4 pep-289-generator-expressions1589437
Ref: dc01589437
Ref: PEP 289 Generator Expressions-Footnote-11591708
Node: PEP 292 Simpler String Substitutions1591757
Ref: whatsnew/2 4 pep-292-simpler-string-substitutions1591945
Ref: dc11591945
Ref: PEP 292 Simpler String Substitutions-Footnote-11593739
Node: PEP 318 Decorators for Functions and Methods1593788
Ref: whatsnew/2 4 pep-318-decorators-for-functions-and-methods1593972
Ref: dc21593972
Ref: PEP 318 Decorators for Functions and Methods-Footnote-11598488
Ref: PEP 318 Decorators for Functions and Methods-Footnote-21598537
Node: PEP 322 Reverse Iteration1598586
Ref: whatsnew/2 4 pep-322-reverse-iteration1598763
Ref: dc41598763
Ref: PEP 322 Reverse Iteration-Footnote-11599724
Node: PEP 324 New subprocess Module1599773
Ref: whatsnew/2 4 pep-324-new-subprocess-module1599931
Ref: dc51599931
Ref: PEP 324 New subprocess Module-Footnote-11603694
Node: PEP 327 Decimal Data Type1603743
Ref: whatsnew/2 4 pep-327-decimal-data-type1603902
Ref: dc71603902
Node: Why is Decimal needed?1604480
Ref: whatsnew/2 4 why-is-decimal-needed1604589
Ref: dc81604589
Node: The Decimal type1607179
Ref: whatsnew/2 4 the-decimal-type1607313
Ref: dc91607313
Node: The Context type1610485
Ref: whatsnew/2 4 the-context-type1610588
Ref: dca1610588
Ref: The Context type-Footnote-11613196
Node: PEP 328 Multi-line Imports1613245
Ref: whatsnew/2 4 pep-328-multi-line-imports1613426
Ref: dcb1613426
Ref: PEP 328 Multi-line Imports-Footnote-11614919
Node: PEP 331 Locale-Independent Float/String Conversions1614968
Ref: whatsnew/2 4 pep-331-locale-independent-float-string-conversions1615150
Ref: dcc1615150
Ref: PEP 331 Locale-Independent Float/String Conversions-Footnote-11616889
Node: Other Language Changes<12>1616938
Ref: whatsnew/2 4 other-language-changes1617132
Ref: dcd1617132
Ref: Other Language Changes<12>-Footnote-11624114
Ref: Other Language Changes<12>-Footnote-21624163
Ref: Other Language Changes<12>-Footnote-31624212
Ref: Other Language Changes<12>-Footnote-41624261
Ref: Other Language Changes<12>-Footnote-51624310
Ref: Other Language Changes<12>-Footnote-61624359
Node: Optimizations<11>1624408
Ref: whatsnew/2 4 optimizations1624488
Ref: dcf1624488
Node: New Improved and Deprecated Modules<3>1627243
Ref: whatsnew/2 4 new-improved-and-deprecated-modules1627413
Ref: dd11627413
Ref: New Improved and Deprecated Modules<3>-Footnote-11644700
Node: cookielib1644749
Ref: whatsnew/2 4 cookielib1644852
Ref: dd31644852
Node: doctest<3>1645771
Ref: whatsnew/2 4 doctest1645874
Ref: dd41645874
Node: Build and C API Changes<11>1648608
Ref: whatsnew/2 4 build-and-c-api-changes1648773
Ref: dda1648773
Node: Port-Specific Changes<2>1651395
Ref: whatsnew/2 4 port-specific-changes1651483
Ref: de11651483
Node: Porting to Python 2 41651662
Ref: whatsnew/2 4 porting-to-python-2-41651808
Ref: de21651808
Node: Acknowledgements<4>1653776
Ref: whatsnew/2 4 acknowledgements1653886
Ref: de41653886
Ref: whatsnew/2 4 acks1653886
Ref: de51653886
Node: What's New in Python 2 31654219
Ref: whatsnew/2 3 doc1654374
Ref: de61654374
Ref: whatsnew/2 3 what-s-new-in-python-2-31654374
Ref: de71654374
Node: PEP 218 A Standard Set Datatype1657393
Ref: whatsnew/2 3 pep-218-a-standard-set-datatype1657519
Ref: de91657519
Ref: PEP 218 A Standard Set Datatype-Footnote-11660009
Node: PEP 255 Simple Generators1660058
Ref: whatsnew/2 3 pep-255-simple-generators1660222
Ref: dea1660222
Ref: whatsnew/2 3 section-generators1660222
Ref: deb1660222
Ref: PEP 255 Simple Generators-Footnote-11666391
Ref: PEP 255 Simple Generators-Footnote-21666440
Node: PEP 263 Source Code Encodings1666489
Ref: whatsnew/2 3 pep-263-source-code-encodings1666665
Ref: ded1666665
Ref: whatsnew/2 3 section-encodings1666665
Ref: dee1666665
Ref: PEP 263 Source Code Encodings-Footnote-11667876
Node: PEP 273 Importing Modules from ZIP Archives1667925
Ref: whatsnew/2 3 pep-273-importing-modules-from-zip-archives1668124
Ref: def1668124
Ref: PEP 273 Importing Modules from ZIP Archives-Footnote-11670156
Ref: PEP 273 Importing Modules from ZIP Archives-Footnote-21670205
Ref: PEP 273 Importing Modules from ZIP Archives-Footnote-31670254
Node: PEP 277 Unicode file name support for Windows NT1670303
Ref: whatsnew/2 3 pep-277-unicode-file-name-support-for-windows-nt1670506
Ref: df11670506
Ref: PEP 277 Unicode file name support for Windows NT-Footnote-11671983
Node: PEP 278 Universal Newline Support1672032
Ref: whatsnew/2 3 pep-278-universal-newline-support1672209
Ref: df31672209
Ref: PEP 278 Universal Newline Support-Footnote-11673723
Node: PEP 279 enumerate1673772
Ref: whatsnew/2 3 pep-279-enumerate1673928
Ref: df41673928
Ref: whatsnew/2 3 section-enumerate1673928
Ref: df51673928
Ref: PEP 279 enumerate-Footnote-11674783
Node: PEP 282 The logging Package1674832
Ref: whatsnew/2 3 pep-282-the-logging-package1674977
Ref: df61674977
Ref: PEP 282 The logging Package-Footnote-11679670
Ref: PEP 282 The logging Package-Footnote-21679719
Node: PEP 285 A Boolean Type1679768
Ref: whatsnew/2 3 pep-285-a-boolean-type1679934
Ref: df71679934
Ref: whatsnew/2 3 section-bool1679934
Ref: df81679934
Ref: PEP 285 A Boolean Type-Footnote-11682382
Ref: PEP 285 A Boolean Type-Footnote-21682431
Node: PEP 293 Codec Error Handling Callbacks1682480
Ref: whatsnew/2 3 pep-293-codec-error-handling-callbacks1682667
Ref: df91682667
Ref: PEP 293 Codec Error Handling Callbacks-Footnote-11684191
Node: PEP 301 Package Index and Metadata for Distutils1684240
Ref: whatsnew/2 3 pep-301-package-index-and-metadata-for-distutils1684429
Ref: dfc1684429
Ref: whatsnew/2 3 section-pep3011684429
Ref: dfd1684429
Ref: PEP 301 Package Index and Metadata for Distutils-Footnote-11686072
Ref: PEP 301 Package Index and Metadata for Distutils-Footnote-21686108
Node: PEP 302 New Import Hooks1686157
Ref: whatsnew/2 3 pep-302-new-import-hooks1686337
Ref: dfe1686337
Ref: whatsnew/2 3 section-pep3021686337
Ref: df01686337
Ref: PEP 302 New Import Hooks-Footnote-11688943
Ref: PEP 302 New Import Hooks-Footnote-21688992
Ref: PEP 302 New Import Hooks-Footnote-31689041
Node: PEP 305 Comma-separated Files1689090
Ref: whatsnew/2 3 pep-305-comma-separated-files1689249
Ref: dff1689249
Ref: whatsnew/2 3 section-pep3051689249
Ref: e001689249
Ref: PEP 305 Comma-separated Files-Footnote-11690724
Node: PEP 307 Pickle Enhancements1690773
Ref: whatsnew/2 3 pep-307-pickle-enhancements1690923
Ref: e021690923
Ref: whatsnew/2 3 section-pep3071690923
Ref: e031690923
Ref: PEP 307 Pickle Enhancements-Footnote-11692893
Ref: PEP 307 Pickle Enhancements-Footnote-21692942
Ref: PEP 307 Pickle Enhancements-Footnote-31692991
Node: Extended Slices1693040
Ref: whatsnew/2 3 extended-slices1693187
Ref: e071693187
Ref: whatsnew/2 3 section-slices1693187
Ref: e081693187
Node: Other Language Changes<13>1696571
Ref: whatsnew/2 3 other-language-changes1696729
Ref: e0a1696729
Ref: Other Language Changes<13>-Footnote-11704513
Ref: Other Language Changes<13>-Footnote-21704585
Node: String Changes1704639
Ref: whatsnew/2 3 string-changes1704742
Ref: e101704742
Node: Optimizations<12>1707195
Ref: whatsnew/2 3 optimizations1707298
Ref: e111707298
Node: New Improved and Deprecated Modules<4>1708745
Ref: whatsnew/2 3 new-improved-and-deprecated-modules1708927
Ref: e131708927
Ref: New Improved and Deprecated Modules<4>-Footnote-11733527
Node: Date/Time Type1733566
Ref: whatsnew/2 3 date-time-type1733683
Ref: e171733683
Node: The optparse Module1735947
Ref: whatsnew/2 3 the-optparse-module1736064
Ref: e181736064
Node: Pymalloc A Specialized Object Allocator1738124
Ref: whatsnew/2 3 pymalloc-a-specialized-object-allocator1738307
Ref: e191738307
Ref: whatsnew/2 3 section-pymalloc1738307
Ref: e1a1738307
Node: Build and C API Changes<12>1742192
Ref: whatsnew/2 3 build-and-c-api-changes1742363
Ref: e1c1742363
Node: Port-Specific Changes<3>1745785
Ref: whatsnew/2 3 port-specific-changes1745873
Ref: e211745873
Node: Other Changes and Fixes<2>1747108
Ref: whatsnew/2 3 other-changes-and-fixes1747261
Ref: e221747261
Ref: whatsnew/2 3 section-other1747261
Ref: e121747261
Node: Porting to Python 2 31749735
Ref: whatsnew/2 3 porting-to-python-2-31749880
Ref: e251749880
Node: Acknowledgements<5>1752688
Ref: whatsnew/2 3 acknowledgements1752798
Ref: e261752798
Ref: whatsnew/2 3 acks1752798
Ref: e271752798
Node: What's New in Python 2 21753419
Ref: whatsnew/2 2 doc1753574
Ref: e281753574
Ref: whatsnew/2 2 what-s-new-in-python-2-21753574
Ref: e291753574
Node: 簡介1754303
Ref: whatsnew/2 2 introduction1754418
Ref: e2a1754418
Ref: 簡介-Footnote-11755372
Ref: 簡介-Footnote-21755421
Node: PEPs 252 and 253 Type and Class Changes1755470
Ref: whatsnew/2 2 peps-252-and-253-type-and-class-changes1755611
Ref: e2b1755611
Node: Old and New Classes1759039
Ref: whatsnew/2 2 old-and-new-classes1759154
Ref: e2d1759154
Ref: Old and New Classes-Footnote-11761559
Node: Descriptors1761608
Ref: whatsnew/2 2 descriptors1761769
Ref: e2e1761769
Node: Multiple Inheritance The Diamond Rule1765629
Ref: whatsnew/2 2 multiple-inheritance-the-diamond-rule1765787
Ref: e2f1765787
Ref: Multiple Inheritance The Diamond Rule-Footnote-11768672
Node: Attribute Access1768721
Ref: whatsnew/2 2 attribute-access1768881
Ref: e301768881
Node: Related Links1772698
Ref: whatsnew/2 2 related-links1772812
Ref: e331772812
Ref: whatsnew/2 2 sect-rellinks1772812
Ref: e2c1772812
Ref: Related Links-Footnote-11774305
Ref: Related Links-Footnote-21774354
Ref: Related Links-Footnote-31774403
Ref: Related Links-Footnote-41774452
Ref: Related Links-Footnote-51774501
Node: PEP 234 Iterators1774550
Ref: whatsnew/2 2 pep-234-iterators1774713
Ref: e341774713
Ref: PEP 234 Iterators-Footnote-11779600
Node: PEP 255 Simple Generators<2>1779649
Ref: whatsnew/2 2 pep-255-simple-generators1779819
Ref: e371779819
Ref: PEP 255 Simple Generators<2>-Footnote-11785866
Ref: PEP 255 Simple Generators<2>-Footnote-21785915
Node: PEP 237 Unifying Long Integers and Integers<2>1785964
Ref: whatsnew/2 2 pep-237-unifying-long-integers-and-integers1786155
Ref: e381786155
Ref: PEP 237 Unifying Long Integers and Integers<2>-Footnote-11787879
Node: PEP 238 Changing the Division Operator1787928
Ref: whatsnew/2 2 pep-238-changing-the-division-operator1788106
Ref: e391788106
Ref: PEP 238 Changing the Division Operator-Footnote-11791745
Ref: PEP 238 Changing the Division Operator-Footnote-21791794
Ref: PEP 238 Changing the Division Operator-Footnote-31791843
Node: Unicode Changes1791892
Ref: whatsnew/2 2 unicode-changes1792045
Ref: e3b1792045
Ref: Unicode Changes-Footnote-11794669
Ref: Unicode Changes-Footnote-21794718
Node: PEP 227 Nested Scopes1794767
Ref: whatsnew/2 2 pep-227-nested-scopes1794909
Ref: e3d1794909
Ref: PEP 227 Nested Scopes-Footnote-11799246
Node: New and Improved Modules<3>1799295
Ref: whatsnew/2 2 new-and-improved-modules1799451
Ref: e3e1799451
Ref: New and Improved Modules<3>-Footnote-11806069
Ref: New and Improved Modules<3>-Footnote-21806118
Ref: New and Improved Modules<3>-Footnote-31806167
Ref: New and Improved Modules<3>-Footnote-41806216
Ref: New and Improved Modules<3>-Footnote-51806265
Node: Interpreter Changes and Fixes1806313
Ref: whatsnew/2 2 interpreter-changes-and-fixes1806474
Ref: e3f1806474
Node: Other Changes and Fixes<3>1811231
Ref: whatsnew/2 2 other-changes-and-fixes1811384
Ref: e511811384
Ref: Other Changes and Fixes<3>-Footnote-11818038
Node: Acknowledgements<6>1818087
Ref: whatsnew/2 2 acknowledgements1818202
Ref: e541818202
Node: What's New in Python 2 11818803
Ref: whatsnew/2 1 doc1818958
Ref: e551818958
Ref: whatsnew/2 1 what-s-new-in-python-2-11818958
Ref: e561818958
Node: 簡介<2>1819951
Ref: whatsnew/2 1 introduction1820054
Ref: e571820054
Node: PEP 227 Nested Scopes<2>1821136
Ref: whatsnew/2 1 pep-227-nested-scopes1821277
Ref: e581821277
Ref: PEP 227 Nested Scopes<2>-Footnote-11825637
Ref: PEP 227 Nested Scopes<2>-Footnote-21825686
Ref: PEP 227 Nested Scopes<2>-Footnote-31825735
Node: PEP 236 __future__ Directives1825784
Ref: whatsnew/2 1 pep-236-future-directives1825940
Ref: e591825940
Ref: PEP 236 __future__ Directives-Footnote-11827176
Node: PEP 207 Rich Comparisons1827225
Ref: whatsnew/2 1 pep-207-rich-comparisons1827382
Ref: e5a1827382
Ref: PEP 207 Rich Comparisons-Footnote-11830776
Ref: PEP 207 Rich Comparisons-Footnote-21830825
Node: PEP 230 Warning Framework1830874
Ref: whatsnew/2 1 pep-230-warning-framework1831026
Ref: e5c1831026
Ref: PEP 230 Warning Framework-Footnote-11834305
Ref: PEP 230 Warning Framework-Footnote-21834354
Node: PEP 229 New Build System1834403
Ref: whatsnew/2 1 pep-229-new-build-system1834554
Ref: e5e1834554
Ref: PEP 229 New Build System-Footnote-11836473
Node: PEP 205 Weak References1836522
Ref: whatsnew/2 1 pep-205-weak-references1836675
Ref: e5f1836675
Ref: PEP 205 Weak References-Footnote-11839787
Node: PEP 232 Function Attributes1839836
Ref: whatsnew/2 1 pep-232-function-attributes1840020
Ref: e601840020
Ref: PEP 232 Function Attributes-Footnote-11841530
Node: PEP 235 Importing Modules on Case-Insensitive Platforms1841579
Ref: whatsnew/2 1 pep-235-importing-modules-on-case-insensitive-platforms1841772
Ref: e611841772
Node: PEP 217 Interactive Display Hook1842675
Ref: whatsnew/2 1 pep-217-interactive-display-hook1842867
Ref: e631842867
Ref: PEP 217 Interactive Display Hook-Footnote-11843794
Node: PEP 208 New Coercion Model1843843
Ref: whatsnew/2 1 pep-208-new-coercion-model1844015
Ref: e651844015
Ref: PEP 208 New Coercion Model-Footnote-11845636
Node: PEP 241 Metadata in Python Packages1845685
Ref: whatsnew/2 1 pep-241-metadata-in-python-packages1845852
Ref: e661845852
Ref: PEP 241 Metadata in Python Packages-Footnote-11847894
Ref: PEP 241 Metadata in Python Packages-Footnote-21847943
Ref: PEP 241 Metadata in Python Packages-Footnote-31847992
Ref: PEP 241 Metadata in Python Packages-Footnote-41848041
Node: New and Improved Modules<4>1848090
Ref: whatsnew/2 1 new-and-improved-modules1848257
Ref: e671848257
Node: Other Changes and Fixes<4>1854089
Ref: whatsnew/2 1 other-changes-and-fixes1854240
Ref: e6a1854240
Node: Acknowledgements<7>1860174
Ref: whatsnew/2 1 acknowledgements1860289
Ref: e6b1860289
Node: What's New in Python 2 01860580
Ref: whatsnew/2 0 doc1860738
Ref: e6c1860738
Ref: whatsnew/2 0 what-s-new-in-python-2-01860738
Ref: e6d1860738
Node: 簡介<3>1861422
Ref: whatsnew/2 0 introduction1861523
Ref: e6e1861523
Node: What About Python 1 6?1862393
Ref: whatsnew/2 0 what-about-python-1-61862526
Ref: e6f1862526
Node: New Development Process1863767
Ref: whatsnew/2 0 new-development-process1863901
Ref: e701863901
Ref: New Development Process-Footnote-11869033
Ref: New Development Process-Footnote-21869082
Ref: New Development Process-Footnote-31869131
Node: Unicode<2>1869180
Ref: whatsnew/2 0 unicode1869334
Ref: e711869334
Ref: Unicode<2>-Footnote-11875504
Node: 串列綜合運算（List Comprehension）1875553
Ref: whatsnew/2 0 list-comprehensions1875704
Ref: e721875704
Node: Augmented Assignment1879473
Ref: whatsnew/2 0 augmented-assignment1879628
Ref: e731879628
Node: String Methods1881174
Ref: whatsnew/2 0 string-methods1881315
Ref: e761881315
Node: Garbage Collection of Cycles1883168
Ref: whatsnew/2 0 garbage-collection-of-cycles1883307
Ref: e771883307
Node: Other Core Changes1886646
Ref: whatsnew/2 0 other-core-changes1886785
Ref: e781886785
Node: Minor Language Changes1887070
Ref: whatsnew/2 0 minor-language-changes1887185
Ref: e791887185
Node: Changes to Built-in Functions1892264
Ref: whatsnew/2 0 changes-to-built-in-functions1892379
Ref: e7e1892379
Node: Porting to 2 01894661
Ref: whatsnew/2 0 porting-to-2-01894799
Ref: e811894799
Node: Extending/Embedding Changes1900118
Ref: whatsnew/2 0 extending-embedding-changes1900278
Ref: e821900278
Node: Distutils Making Modules Easy to Install1904100
Ref: whatsnew/2 0 distutils-making-modules-easy-to-install1904257
Ref: e831904257
Node: XML Modules1907605
Ref: whatsnew/2 0 xml-modules1907749
Ref: e841907749
Node: SAX2 Support1908648
Ref: whatsnew/2 0 sax2-support1908728
Ref: e851908728
Node: DOM Support1910366
Ref: whatsnew/2 0 dom-support1910476
Ref: e861910476
Node: Relationship to PyXML1913304
Ref: whatsnew/2 0 relationship-to-pyxml1913393
Ref: e871913393
Node: Module changes1914683
Ref: whatsnew/2 0 module-changes1914798
Ref: e881914798
Node: New modules1917270
Ref: whatsnew/2 0 new-modules1917391
Ref: e891917391
Node: IDLE Improvements1921383
Ref: whatsnew/2 0 idle-improvements1921520
Ref: e8b1921520
Node: Deleted and Deprecated Modules1922643
Ref: whatsnew/2 0 deleted-and-deprecated-modules1922788
Ref: e8c1922788
Node: Acknowledgements<8>1923540
Ref: whatsnew/2 0 acknowledgements1923659
Ref: e8d1923659
Ref: Acknowledgements<8>-Footnote-11924254
Ref: Acknowledgements<8>-Footnote-21924293
Node: Changelog（更動日誌）1924356
Ref: whatsnew/changelog doc1924481
Ref: e8e1924481
Ref: whatsnew/changelog changelog1924481
Ref: 14d1924481
Ref: whatsnew/changelog id11924481
Ref: e8f1924481
Node: Python 3 8 11 final1929092
Ref: whatsnew/changelog python-3-8-11-final1929203
Ref: e901929203
Node: Security1929343
Ref: whatsnew/changelog security1929433
Ref: e911929433
Ref: Security-Footnote-11930110
Ref: Security-Footnote-21930153
Ref: Security-Footnote-31930196
Node: Core and Builtins1930239
Ref: whatsnew/changelog core-and-builtins1930345
Ref: e921930345
Ref: Core and Builtins-Footnote-11930574
Node: Library1930617
Ref: whatsnew/changelog library1930706
Ref: e931930706
Ref: Library-Footnote-11930938
Node: Python 3 8 10 final1930981
Ref: whatsnew/changelog python-3-8-10-final1931119
Ref: e941931119
Node: Security<2>1931397
Ref: whatsnew/changelog id21931493
Ref: e951931493
Ref: Security<2>-Footnote-11932409
Ref: Security<2>-Footnote-21932452
Ref: Security<2>-Footnote-31932495
Node: Core and Builtins<2>1932538
Ref: whatsnew/changelog id31932653
Ref: e981932653
Ref: Core and Builtins<2>-Footnote-11933124
Ref: Core and Builtins<2>-Footnote-21933167
Node: Library<2>1933210
Ref: whatsnew/changelog id41933330
Ref: e991933330
Ref: Library<2>-Footnote-11936943
Ref: Library<2>-Footnote-21936986
Ref: Library<2>-Footnote-31937029
Ref: Library<2>-Footnote-41937072
Ref: Library<2>-Footnote-51937115
Ref: Library<2>-Footnote-61937158
Ref: Library<2>-Footnote-71937201
Ref: Library<2>-Footnote-81937244
Ref: Library<2>-Footnote-91937287
Ref: Library<2>-Footnote-101937330
Ref: Library<2>-Footnote-111937374
Ref: Library<2>-Footnote-121937418
Ref: Library<2>-Footnote-131937462
Ref: Library<2>-Footnote-141937506
Ref: Library<2>-Footnote-151937550
Ref: Library<2>-Footnote-161937594
Ref: Library<2>-Footnote-171937638
Ref: Library<2>-Footnote-181937682
Ref: Library<2>-Footnote-191937726
Ref: Library<2>-Footnote-201937770
Ref: Library<2>-Footnote-211937814
Ref: Library<2>-Footnote-221937858
Node: Documentation<2>1937902
Ref: whatsnew/changelog documentation1938007
Ref: e9f1938007
Ref: Documentation<2>-Footnote-11938457
Ref: Documentation<2>-Footnote-21938500
Ref: Documentation<2>-Footnote-31938543
Node: Tests1938586
Ref: whatsnew/changelog tests1938688
Ref: ea01938688
Ref: Tests-Footnote-11939249
Ref: Tests-Footnote-21939292
Ref: Tests-Footnote-31939335
Node: Windows1939378
Ref: whatsnew/changelog windows1939469
Ref: ea11939469
Ref: Windows-Footnote-11940289
Ref: Windows-Footnote-21940332
Ref: Windows-Footnote-31940375
Ref: Windows-Footnote-41940418
Ref: Windows-Footnote-51940461
Node: macOS1940504
Ref: whatsnew/changelog macos1940597
Ref: ea41940597
Ref: macOS-Footnote-11941623
Ref: macOS-Footnote-21941666
Ref: macOS-Footnote-31941709
Node: IDLE<3>1941752
Ref: whatsnew/changelog idle1941843
Ref: ea51941843
Ref: IDLE<3>-Footnote-11942025
Node: C API1942068
Ref: whatsnew/changelog c-api1942145
Ref: ea61942145
Ref: C API-Footnote-11942550
Node: Python 3 8 9 final1942593
Ref: whatsnew/changelog python-3-8-9-final1942730
Ref: ea71942730
Node: Security<3>1943012
Ref: whatsnew/changelog id51943107
Ref: ea81943107
Ref: Security<3>-Footnote-11944186
Ref: Security<3>-Footnote-21944229
Ref: Security<3>-Footnote-31944272
Node: Core and Builtins<3>1944315
Ref: whatsnew/changelog id61944429
Ref: eab1944429
Ref: Core and Builtins<3>-Footnote-11945154
Ref: Core and Builtins<3>-Footnote-21945197
Ref: Core and Builtins<3>-Footnote-31945240
Node: Library<3>1945283
Ref: whatsnew/changelog id71945402
Ref: eac1945402
Ref: Library<3>-Footnote-11946902
Ref: Library<3>-Footnote-21946945
Ref: Library<3>-Footnote-31946988
Ref: Library<3>-Footnote-41947031
Ref: Library<3>-Footnote-51947074
Ref: Library<3>-Footnote-61947117
Ref: Library<3>-Footnote-71947160
Ref: Library<3>-Footnote-81947203
Ref: Library<3>-Footnote-91947246
Node: Documentation<3>1947289
Ref: whatsnew/changelog id81947396
Ref: eae1947396
Ref: Documentation<3>-Footnote-11948137
Ref: Documentation<3>-Footnote-21948180
Ref: Documentation<3>-Footnote-31948223
Ref: Documentation<3>-Footnote-41948266
Ref: Documentation<3>-Footnote-51948309
Node: Tests<2>1948358
Ref: whatsnew/changelog id91948460
Ref: eaf1948460
Ref: Tests<2>-Footnote-11948763
Ref: Tests<2>-Footnote-21948806
Node: Build1948849
Ref: whatsnew/changelog build1948943
Ref: eb01948943
Ref: Build-Footnote-11949209
Ref: Build-Footnote-21949252
Node: macOS<2>1949295
Ref: whatsnew/changelog id101949388
Ref: eb11949388
Ref: macOS<2>-Footnote-11949527
Node: IDLE<4>1949570
Ref: whatsnew/changelog id111949649
Ref: eb21949649
Ref: IDLE<4>-Footnote-11950091
Ref: IDLE<4>-Footnote-21950134
Node: Python 3 8 8 final1950177
Ref: whatsnew/changelog python-3-8-8-final1950327
Ref: eb31950327
Node: Python 3 8 8 release candidate 11950453
Ref: whatsnew/changelog python-3-8-8-release-candidate-11950603
Ref: eb41950603
Node: Security<4>1950980
Ref: whatsnew/changelog id121951089
Ref: eb51951089
Ref: Security<4>-Footnote-11951478
Ref: Security<4>-Footnote-21951521
Node: Core and Builtins<4>1951564
Ref: whatsnew/changelog id131951692
Ref: eb81951692
Ref: Core and Builtins<4>-Footnote-11952410
Node: Library<4>1952453
Ref: whatsnew/changelog id141952586
Ref: eb91952586
Ref: Library<4>-Footnote-11955093
Ref: Library<4>-Footnote-21955136
Ref: Library<4>-Footnote-31955179
Ref: Library<4>-Footnote-41955222
Ref: Library<4>-Footnote-51955265
Ref: Library<4>-Footnote-61955308
Ref: Library<4>-Footnote-71955351
Ref: Library<4>-Footnote-81955394
Ref: Library<4>-Footnote-91955437
Ref: Library<4>-Footnote-101955480
Ref: Library<4>-Footnote-111955524
Ref: Library<4>-Footnote-121955568
Ref: Library<4>-Footnote-131955612
Ref: Library<4>-Footnote-141955656
Ref: Library<4>-Footnote-151955700
Ref: Library<4>-Footnote-161955744
Ref: Library<4>-Footnote-171955788
Node: Documentation<4>1955832
Ref: whatsnew/changelog id151955953
Ref: ec11955953
Ref: Documentation<4>-Footnote-11956280
Ref: Documentation<4>-Footnote-21956323
Node: Tests<3>1956366
Ref: whatsnew/changelog id161956485
Ref: ec21956485
Ref: Tests<3>-Footnote-11956782
Ref: Tests<3>-Footnote-21956825
Node: Build<2>1956868
Ref: whatsnew/changelog id171956981
Ref: ec31956981
Ref: Build<2>-Footnote-11957111
Node: Windows<2>1957154
Ref: whatsnew/changelog id181957267
Ref: ec41957267
Ref: Windows<2>-Footnote-11957478
Ref: Windows<2>-Footnote-21957521
Node: macOS<3>1957564
Ref: whatsnew/changelog id191957676
Ref: ec51957676
Ref: macOS<3>-Footnote-11957880
Ref: macOS<3>-Footnote-21957923
Node: IDLE<5>1957966
Ref: whatsnew/changelog id201958079
Ref: ec61958079
Ref: IDLE<5>-Footnote-11958824
Ref: IDLE<5>-Footnote-21958867
Ref: IDLE<5>-Footnote-31958910
Ref: IDLE<5>-Footnote-41958953
Ref: IDLE<5>-Footnote-51958996
Node: Tools/Demos1959039
Ref: whatsnew/changelog tools-demos1959152
Ref: ec71959152
Ref: Tools/Demos-Footnote-11959351
Node: C API<2>1959394
Ref: whatsnew/changelog id211959491
Ref: ec81959491
Ref: C API<2>-Footnote-11959859
Ref: C API<2>-Footnote-21959902
Node: Python 3 8 7 final1959945
Ref: whatsnew/changelog python-3-8-7-final1960109
Ref: eca1960109
Node: Core and Builtins<5>1960351
Ref: whatsnew/changelog id221960445
Ref: ecb1960445
Ref: Core and Builtins<5>-Footnote-11961455
Ref: Core and Builtins<5>-Footnote-21961498
Node: Library<5>1961541
Ref: whatsnew/changelog id231961660
Ref: ecf1961660
Ref: Library<5>-Footnote-11963416
Ref: Library<5>-Footnote-21963459
Ref: Library<5>-Footnote-31963502
Ref: Library<5>-Footnote-41963545
Ref: Library<5>-Footnote-51963588
Ref: Library<5>-Footnote-61963631
Ref: Library<5>-Footnote-71963674
Ref: Library<5>-Footnote-81963717
Ref: Library<5>-Footnote-91963760
Ref: Library<5>-Footnote-101963803
Ref: Library<5>-Footnote-111963847
Node: Documentation<5>1963891
Ref: whatsnew/changelog id241963998
Ref: ed11963998
Ref: Documentation<5>-Footnote-11964183
Node: Build<3>1964226
Ref: whatsnew/changelog id251964337
Ref: ed31964337
Ref: Build<3>-Footnote-11964885
Ref: Build<3>-Footnote-21964928
Node: Tools/Demos<2>1964971
Ref: whatsnew/changelog id261965057
Ref: ed41965057
Ref: Tools/Demos<2>-Footnote-11965261
Node: Python 3 8 7 release candidate 11965304
Ref: whatsnew/changelog python-3-8-7-release-candidate-11965454
Ref: ed51965454
Node: Security<5>1965815
Ref: whatsnew/changelog id271965924
Ref: ed61965924
Ref: Security<5>-Footnote-11966563
Ref: Security<5>-Footnote-21966606
Ref: Security<5>-Footnote-31966649
Node: Core and Builtins<6>1966692
Ref: whatsnew/changelog id281966820
Ref: ed71966820
Ref: Core and Builtins<6>-Footnote-11967889
Ref: Core and Builtins<6>-Footnote-21967932
Ref: Core and Builtins<6>-Footnote-31967975
Ref: Core and Builtins<6>-Footnote-41968018
Ref: Core and Builtins<6>-Footnote-51968061
Node: Library<6>1968104
Ref: whatsnew/changelog id291968237
Ref: ed91968237
Ref: Library<6>-Footnote-11973961
Ref: Library<6>-Footnote-21974004
Ref: Library<6>-Footnote-31974047
Ref: Library<6>-Footnote-41974090
Ref: Library<6>-Footnote-51974133
Ref: Library<6>-Footnote-61974176
Ref: Library<6>-Footnote-71974219
Ref: Library<6>-Footnote-81974262
Ref: Library<6>-Footnote-91974305
Ref: Library<6>-Footnote-101974348
Ref: Library<6>-Footnote-111974392
Ref: Library<6>-Footnote-121974436
Ref: Library<6>-Footnote-131974480
Ref: Library<6>-Footnote-141974524
Ref: Library<6>-Footnote-151974568
Ref: Library<6>-Footnote-161974612
Ref: Library<6>-Footnote-171974656
Ref: Library<6>-Footnote-181974700
Ref: Library<6>-Footnote-191974744
Ref: Library<6>-Footnote-201974788
Ref: Library<6>-Footnote-211974832
Ref: Library<6>-Footnote-221974904
Ref: Library<6>-Footnote-231974948
Ref: Library<6>-Footnote-241974992
Ref: Library<6>-Footnote-251975036
Ref: Library<6>-Footnote-261975080
Ref: Library<6>-Footnote-271975124
Ref: Library<6>-Footnote-281975168
Ref: Library<6>-Footnote-291975212
Ref: Library<6>-Footnote-301975256
Ref: Library<6>-Footnote-311975300
Ref: Library<6>-Footnote-321975344
Ref: Library<6>-Footnote-331975388
Ref: Library<6>-Footnote-341975432
Node: Documentation<6>1975476
Ref: whatsnew/changelog id301975597
Ref: ee11975597
Ref: Documentation<6>-Footnote-11976077
Ref: Documentation<6>-Footnote-21976120
Ref: Documentation<6>-Footnote-31976163
Ref: Documentation<6>-Footnote-41976206
Node: Tests<4>1976249
Ref: whatsnew/changelog id311976368
Ref: ee21976368
Ref: Tests<4>-Footnote-11977649
Ref: Tests<4>-Footnote-21977692
Ref: Tests<4>-Footnote-31977735
Ref: Tests<4>-Footnote-41977778
Ref: Tests<4>-Footnote-51977821
Ref: Tests<4>-Footnote-61977864
Ref: Tests<4>-Footnote-71977907
Ref: Tests<4>-Footnote-81977950
Ref: Tests<4>-Footnote-91977993
Node: Build<4>1978036
Ref: whatsnew/changelog id321978149
Ref: ee31978149
Ref: Build<4>-Footnote-11978539
Node: Windows<3>1978582
Ref: whatsnew/changelog id331978695
Ref: ee41978695
Ref: Windows<3>-Footnote-11979108
Ref: Windows<3>-Footnote-21979151
Ref: Windows<3>-Footnote-31979194
Ref: Windows<3>-Footnote-41979237
Node: macOS<4>1979280
Ref: whatsnew/changelog id341979392
Ref: ee51979392
Ref: macOS<4>-Footnote-11979789
Ref: macOS<4>-Footnote-21979832
Ref: macOS<4>-Footnote-31979875
Node: IDLE<6>1979918
Ref: whatsnew/changelog id351980028
Ref: ee61980028
Ref: IDLE<6>-Footnote-11980859
Ref: IDLE<6>-Footnote-21980902
Ref: IDLE<6>-Footnote-31980945
Ref: IDLE<6>-Footnote-41980988
Ref: IDLE<6>-Footnote-51981031
Ref: IDLE<6>-Footnote-61981074
Node: C API<3>1981117
Ref: whatsnew/changelog id361981210
Ref: ee71981210
Ref: C API<3>-Footnote-11981401
Node: Python 3 8 6 final1981444
Ref: whatsnew/changelog python-3-8-6-final1981608
Ref: ee81981608
Node: Core and Builtins<7>1981859
Ref: whatsnew/changelog id371981953
Ref: ee91981953
Ref: Core and Builtins<7>-Footnote-11982139
Node: Library<7>1982182
Ref: whatsnew/changelog id381982301
Ref: eea1982301
Ref: Library<7>-Footnote-11983599
Ref: Library<7>-Footnote-21983642
Ref: Library<7>-Footnote-31983685
Ref: Library<7>-Footnote-41983728
Ref: Library<7>-Footnote-51983771
Ref: Library<7>-Footnote-61983814
Ref: Library<7>-Footnote-71983857
Ref: Library<7>-Footnote-81983900
Ref: Library<7>-Footnote-91983943
Node: Documentation<7>1983986
Ref: whatsnew/changelog id391984093
Ref: eeb1984093
Ref: Documentation<7>-Footnote-11984499
Ref: Documentation<7>-Footnote-21984542
Node: Tests<5>1984585
Ref: whatsnew/changelog id401984692
Ref: eec1984692
Ref: Tests<5>-Footnote-11984833
Node: Windows<4>1984876
Ref: whatsnew/changelog id411984974
Ref: eed1984974
Ref: Windows<4>-Footnote-11985137
Node: IDLE<7>1985180
Ref: whatsnew/changelog id421985261
Ref: eee1985261
Ref: IDLE<7>-Footnote-11985490
Ref: IDLE<7>-Footnote-21985533
Node: Python 3 8 6 release candidate 11985576
Ref: whatsnew/changelog python-3-8-6-release-candidate-11985726
Ref: eef1985726
Node: Core and Builtins<8>1986005
Ref: whatsnew/changelog id431986113
Ref: ef01986113
Ref: Core and Builtins<8>-Footnote-11986578
Ref: Core and Builtins<8>-Footnote-21986621
Ref: Core and Builtins<8>-Footnote-31986664
Node: Library<8>1986707
Ref: whatsnew/changelog id441986840
Ref: ef21986840
Ref: Library<8>-Footnote-11989293
Ref: Library<8>-Footnote-21989336
Ref: Library<8>-Footnote-31989379
Ref: Library<8>-Footnote-41989422
Ref: Library<8>-Footnote-51989465
Ref: Library<8>-Footnote-61989508
Ref: Library<8>-Footnote-71989551
Ref: Library<8>-Footnote-81989594
Ref: Library<8>-Footnote-91989637
Ref: Library<8>-Footnote-101989680
Ref: Library<8>-Footnote-111989724
Ref: Library<8>-Footnote-121989768
Ref: Library<8>-Footnote-131989812
Ref: Library<8>-Footnote-141989856
Ref: Library<8>-Footnote-151989900
Ref: Library<8>-Footnote-161989944
Ref: Library<8>-Footnote-171989988
Ref: Library<8>-Footnote-181990032
Ref: Library<8>-Footnote-191990076
Node: Documentation<8>1990120
Ref: whatsnew/changelog id451990243
Ref: ef41990243
Ref: Documentation<8>-Footnote-11991025
Ref: Documentation<8>-Footnote-21991068
Ref: Documentation<8>-Footnote-31991111
Ref: Documentation<8>-Footnote-41991154
Ref: Documentation<8>-Footnote-51991197
Node: Windows<5>1991240
Ref: whatsnew/changelog id461991360
Ref: ef61991360
Ref: Windows<5>-Footnote-11991571
Ref: Windows<5>-Footnote-21991614
Node: IDLE<8>1991657
Ref: whatsnew/changelog id471991769
Ref: ef71991769
Ref: IDLE<8>-Footnote-11992127
Ref: IDLE<8>-Footnote-21992170
Node: C API<4>1992213
Ref: whatsnew/changelog id481992306
Ref: ef81992306
Ref: C API<4>-Footnote-11992498
Node: Python 3 8 5 final1992541
Ref: whatsnew/changelog python-3-8-5-final1992691
Ref: ef91992691
Node: Security<6>1992965
Ref: whatsnew/changelog id491993060
Ref: efa1993060
Ref: Security<6>-Footnote-11993384
Ref: Security<6>-Footnote-21993427
Ref: Security<6>-Footnote-31993470
Node: Core and Builtins<9>1993513
Ref: whatsnew/changelog id501993627
Ref: efb1993627
Ref: Core and Builtins<9>-Footnote-11993958
Node: Library<9>1994001
Ref: whatsnew/changelog id511994120
Ref: efc1994120
Ref: Library<9>-Footnote-11994457
Ref: Library<9>-Footnote-21994500
Node: Documentation<9>1994543
Ref: whatsnew/changelog id521994650
Ref: efd1994650
Ref: Documentation<9>-Footnote-11994847
Node: Build<5>1994890
Ref: whatsnew/changelog id531994995
Ref: efe1994995
Ref: Build<5>-Footnote-11995202
Node: macOS<5>1995245
Ref: whatsnew/changelog id541995341
Ref: eff1995341
Ref: macOS<5>-Footnote-11995475
Node: IDLE<9>1995518
Ref: whatsnew/changelog id551995597
Ref: f001995597
Ref: IDLE<9>-Footnote-11995769
Node: Python 3 8 4 final1995812
Ref: whatsnew/changelog python-3-8-4-final1995962
Ref: f011995962
Node: Security<7>1996166
Ref: whatsnew/changelog id561996262
Ref: f021996262
Ref: Security<7>-Footnote-11996566
Ref: Security<7>-Footnote-21996609
Node: Core and Builtins<10>1996652
Ref: whatsnew/changelog id571996768
Ref: f031996768
Ref: Core and Builtins<10>-Footnote-11997652
Ref: Core and Builtins<10>-Footnote-21997695
Ref: Core and Builtins<10>-Footnote-31997738
Ref: Core and Builtins<10>-Footnote-41997781
Ref: Core and Builtins<10>-Footnote-51997824
Node: Library<10>1997867
Ref: whatsnew/changelog id581997980
Ref: f041997980
Ref: Library<10>-Footnote-11998653
Ref: Library<10>-Footnote-21998696
Ref: Library<10>-Footnote-31998739
Ref: Library<10>-Footnote-41998782
Node: IDLE<10>1998825
Ref: whatsnew/changelog id591998908
Ref: f051998908
Ref: IDLE<10>-Footnote-11999200
Ref: IDLE<10>-Footnote-21999243
Node: Python 3 8 4 release candidate 11999286
Ref: whatsnew/changelog python-3-8-4-release-candidate-11999436
Ref: f061999436
Node: Security<8>1999779
Ref: whatsnew/changelog id601999889
Ref: f071999889
Ref: Security<8>-Footnote-12000434
Ref: Security<8>-Footnote-22000477
Node: Core and Builtins<11>2000520
Ref: whatsnew/changelog id612000650
Ref: f082000650
Ref: Core and Builtins<11>-Footnote-12002140
Ref: Core and Builtins<11>-Footnote-22002183
Ref: Core and Builtins<11>-Footnote-32002226
Ref: Core and Builtins<11>-Footnote-42002269
Ref: Core and Builtins<11>-Footnote-52002312
Ref: Core and Builtins<11>-Footnote-62002355
Ref: Core and Builtins<11>-Footnote-72002398
Ref: Core and Builtins<11>-Footnote-82002441
Node: Library<11>2002484
Ref: whatsnew/changelog id622002611
Ref: f0c2002611
Ref: Library<11>-Footnote-12007112
Ref: Library<11>-Footnote-22007155
Ref: Library<11>-Footnote-32007198
Ref: Library<11>-Footnote-42007241
Ref: Library<11>-Footnote-52007284
Ref: Library<11>-Footnote-62007327
Ref: Library<11>-Footnote-72007370
Ref: Library<11>-Footnote-82007413
Ref: Library<11>-Footnote-92007456
Ref: Library<11>-Footnote-102007499
Ref: Library<11>-Footnote-112007543
Ref: Library<11>-Footnote-122007587
Ref: Library<11>-Footnote-132007631
Ref: Library<11>-Footnote-142007675
Ref: Library<11>-Footnote-152007719
Ref: Library<11>-Footnote-162007763
Ref: Library<11>-Footnote-172007807
Ref: Library<11>-Footnote-182007851
Ref: Library<11>-Footnote-192007895
Ref: Library<11>-Footnote-202007939
Ref: Library<11>-Footnote-212007983
Ref: Library<11>-Footnote-222008027
Ref: Library<11>-Footnote-232008071
Ref: Library<11>-Footnote-242008115
Ref: Library<11>-Footnote-252008159
Ref: Library<11>-Footnote-262008203
Ref: Library<11>-Footnote-272008247
Ref: Library<11>-Footnote-282008291
Ref: Library<11>-Footnote-292008335
Node: Tests<6>2008379
Ref: whatsnew/changelog id632008493
Ref: f102008493
Ref: Tests<6>-Footnote-12009722
Ref: Tests<6>-Footnote-22009765
Ref: Tests<6>-Footnote-32009808
Ref: Tests<6>-Footnote-42009851
Ref: Tests<6>-Footnote-52009894
Ref: Tests<6>-Footnote-62009937
Ref: Tests<6>-Footnote-72009980
Node: Build<6>2010023
Ref: whatsnew/changelog id642010136
Ref: f122010136
Ref: Build<6>-Footnote-12010372
Ref: Build<6>-Footnote-22010415
Node: Windows<6>2010458
Ref: whatsnew/changelog id652010571
Ref: f132010571
Ref: Windows<6>-Footnote-12011460
Ref: Windows<6>-Footnote-22011503
Ref: Windows<6>-Footnote-32011546
Ref: Windows<6>-Footnote-42011589
Ref: Windows<6>-Footnote-52011632
Ref: Windows<6>-Footnote-62011675
Node: macOS<6>2011718
Ref: whatsnew/changelog id662011831
Ref: f172011831
Ref: macOS<6>-Footnote-12012590
Ref: macOS<6>-Footnote-22012633
Ref: macOS<6>-Footnote-32012676
Ref: macOS<6>-Footnote-42012719
Node: IDLE<11>2012762
Ref: whatsnew/changelog id672012879
Ref: f182012879
Ref: IDLE<11>-Footnote-12013197
Ref: IDLE<11>-Footnote-22013240
Ref: IDLE<11>-Footnote-32013283
Node: Tools/Demos<3>2013326
Ref: whatsnew/changelog id682013426
Ref: f192013426
Ref: Tools/Demos<3>-Footnote-12013811
Ref: Tools/Demos<3>-Footnote-22013854
Node: Python 3 8 3 final2013897
Ref: whatsnew/changelog python-3-8-3-final2014061
Ref: f1a2014061
Node: Core and Builtins<12>2014300
Ref: whatsnew/changelog id692014396
Ref: f1b2014396
Ref: Core and Builtins<12>-Footnote-12014982
Ref: Core and Builtins<12>-Footnote-22015025
Ref: Core and Builtins<12>-Footnote-32015068
Node: Library<12>2015111
Ref: whatsnew/changelog id702015233
Ref: f1c2015233
Ref: Library<12>-Footnote-12015873
Ref: Library<12>-Footnote-22015916
Ref: Library<12>-Footnote-32015959
Ref: Library<12>-Footnote-42016002
Node: Documentation<10>2016045
Ref: whatsnew/changelog id712016156
Ref: f1e2016156
Ref: Documentation<10>-Footnote-12016406
Ref: Documentation<10>-Footnote-22016449
Node: Windows<7>2016492
Ref: whatsnew/changelog id722016600
Ref: f1f2016600
Ref: Windows<7>-Footnote-12016766
Node: C API<5>2016809
Ref: whatsnew/changelog id732016891
Ref: f202016891
Ref: C API<5>-Footnote-12017143
Node: Python 3 8 3 release candidate 12017186
Ref: whatsnew/changelog python-3-8-3-release-candidate-12017336
Ref: f212017336
Node: Security<9>2017734
Ref: whatsnew/changelog id742017844
Ref: f222017844
Ref: Security<9>-Footnote-12018561
Ref: Security<9>-Footnote-22018604
Ref: Security<9>-Footnote-32018647
Node: Core and Builtins<13>2018690
Ref: whatsnew/changelog id752018820
Ref: f232018820
Ref: Core and Builtins<13>-Footnote-12020667
Ref: Core and Builtins<13>-Footnote-22020710
Ref: Core and Builtins<13>-Footnote-32020753
Ref: Core and Builtins<13>-Footnote-42020796
Ref: Core and Builtins<13>-Footnote-52020839
Ref: Core and Builtins<13>-Footnote-62020882
Ref: Core and Builtins<13>-Footnote-72020925
Ref: Core and Builtins<13>-Footnote-82020968
Ref: Core and Builtins<13>-Footnote-92021011
Node: Library<13>2021054
Ref: whatsnew/changelog id762021190
Ref: f252021190
Ref: Library<13>-Footnote-12027110
Ref: Library<13>-Footnote-22027153
Ref: Library<13>-Footnote-32027196
Ref: Library<13>-Footnote-42027239
Ref: Library<13>-Footnote-52027282
Ref: Library<13>-Footnote-62027325
Ref: Library<13>-Footnote-72027368
Ref: Library<13>-Footnote-82027411
Ref: Library<13>-Footnote-92027454
Ref: Library<13>-Footnote-102027497
Ref: Library<13>-Footnote-112027541
Ref: Library<13>-Footnote-122027585
Ref: Library<13>-Footnote-132027629
Ref: Library<13>-Footnote-142027673
Ref: Library<13>-Footnote-152027717
Ref: Library<13>-Footnote-162027761
Ref: Library<13>-Footnote-172027805
Ref: Library<13>-Footnote-182027849
Ref: Library<13>-Footnote-192027893
Ref: Library<13>-Footnote-202027937
Ref: Library<13>-Footnote-212027981
Ref: Library<13>-Footnote-222028025
Ref: Library<13>-Footnote-232028069
Ref: Library<13>-Footnote-242028113
Ref: Library<13>-Footnote-252028157
Ref: Library<13>-Footnote-262028201
Ref: Library<13>-Footnote-272028245
Ref: Library<13>-Footnote-282028289
Ref: Library<13>-Footnote-292028333
Ref: Library<13>-Footnote-302028377
Ref: Library<13>-Footnote-312028421
Node: Documentation<11>2028465
Ref: whatsnew/changelog id772028588
Ref: f2f2028588
Ref: Documentation<11>-Footnote-12029618
Ref: Documentation<11>-Footnote-22029661
Ref: Documentation<11>-Footnote-32029704
Ref: Documentation<11>-Footnote-42029747
Ref: Documentation<11>-Footnote-52029796
Ref: Documentation<11>-Footnote-62029839
Ref: Documentation<11>-Footnote-72029882
Ref: Documentation<11>-Footnote-82029925
Ref: Documentation<11>-Footnote-92029968
Ref: Documentation<11>-Footnote-102030011
Node: Tests<7>2030055
Ref: whatsnew/changelog id782030175
Ref: f322030175
Ref: Tests<7>-Footnote-12031497
Ref: Tests<7>-Footnote-22031540
Ref: Tests<7>-Footnote-32031583
Ref: Tests<7>-Footnote-42031626
Ref: Tests<7>-Footnote-52031669
Ref: Tests<7>-Footnote-62031712
Ref: Tests<7>-Footnote-72031755
Ref: Tests<7>-Footnote-82031797
Ref: Tests<7>-Footnote-92031840
Node: Build<7>2031883
Ref: whatsnew/changelog id792031996
Ref: f352031996
Ref: Build<7>-Footnote-12032480
Ref: Build<7>-Footnote-22032523
Ref: Build<7>-Footnote-32032566
Ref: Build<7>-Footnote-42032609
Node: Windows<8>2032652
Ref: whatsnew/changelog id802032765
Ref: f362032765
Ref: Windows<8>-Footnote-12033707
Ref: Windows<8>-Footnote-22033750
Ref: Windows<8>-Footnote-32033793
Ref: Windows<8>-Footnote-42033836
Ref: Windows<8>-Footnote-52033879
Ref: Windows<8>-Footnote-62033922
Ref: Windows<8>-Footnote-72033965
Node: macOS<7>2034008
Ref: whatsnew/changelog id812034121
Ref: f372034121
Ref: macOS<7>-Footnote-12034324
Ref: macOS<7>-Footnote-22034367
Node: IDLE<12>2034410
Ref: whatsnew/changelog id822034527
Ref: f382034527
Ref: IDLE<12>-Footnote-12035362
Ref: IDLE<12>-Footnote-22035405
Ref: IDLE<12>-Footnote-32035448
Ref: IDLE<12>-Footnote-42035491
Ref: IDLE<12>-Footnote-52035534
Ref: IDLE<12>-Footnote-62035577
Node: Tools/Demos<4>2035620
Ref: whatsnew/changelog id832035737
Ref: f392035737
Ref: Tools/Demos<4>-Footnote-12036383
Ref: Tools/Demos<4>-Footnote-22036426
Ref: Tools/Demos<4>-Footnote-32036469
Node: C API<6>2036512
Ref: whatsnew/changelog id842036612
Ref: f3a2036612
Ref: C API<6>-Footnote-12037354
Ref: C API<6>-Footnote-22037397
Ref: C API<6>-Footnote-32037440
Ref: C API<6>-Footnote-42037483
Node: Python 3 8 2 final2037526
Ref: whatsnew/changelog python-3-8-2-final2037690
Ref: f3e2037690
Node: Core and Builtins<14>2037905
Ref: whatsnew/changelog id852038001
Ref: f3f2038001
Ref: Core and Builtins<14>-Footnote-12038461
Ref: Core and Builtins<14>-Footnote-22038504
Node: Library<14>2038547
Ref: whatsnew/changelog id862038669
Ref: f402038669
Ref: Library<14>-Footnote-12039360
Ref: Library<14>-Footnote-22039403
Ref: Library<14>-Footnote-32039446
Ref: Library<14>-Footnote-42039489
Node: Documentation<12>2039532
Ref: whatsnew/changelog id872039641
Ref: f412039641
Ref: Documentation<12>-Footnote-12040081
Ref: Documentation<12>-Footnote-22040124
Ref: Documentation<12>-Footnote-32040167
Node: IDLE<13>2040210
Ref: whatsnew/changelog id882040299
Ref: f422040299
Ref: IDLE<13>-Footnote-12040433
Node: Python 3 8 2 release candidate 22040476
Ref: whatsnew/changelog python-3-8-2-release-candidate-22040640
Ref: f432040640
Node: Security<10>2040873
Ref: whatsnew/changelog id892040984
Ref: f442040984
Ref: Security<10>-Footnote-12041250
Node: Core and Builtins<15>2041293
Ref: whatsnew/changelog id902041424
Ref: f452041424
Ref: Core and Builtins<15>-Footnote-12042041
Ref: Core and Builtins<15>-Footnote-22042084
Ref: Core and Builtins<15>-Footnote-32042127
Ref: Core and Builtins<15>-Footnote-42042170
Ref: Core and Builtins<15>-Footnote-52042213
Node: Library<15>2042256
Ref: whatsnew/changelog id912042383
Ref: f472042383
Ref: Library<15>-Footnote-12043429
Ref: Library<15>-Footnote-22043472
Ref: Library<15>-Footnote-32043515
Ref: Library<15>-Footnote-42043558
Ref: Library<15>-Footnote-52043601
Ref: Library<15>-Footnote-62043644
Node: IDLE<14>2043737
Ref: whatsnew/changelog id922043834
Ref: f482043834
Ref: IDLE<14>-Footnote-12043990
Node: Python 3 8 2 release candidate 12044033
Ref: whatsnew/changelog python-3-8-2-release-candidate-12044197
Ref: f492044197
Node: Security<11>2044527
Ref: whatsnew/changelog id932044638
Ref: f4a2044638
Ref: Security<11>-Footnote-12044918
Ref: Security<11>-Footnote-22044961
Node: Core and Builtins<16>2045004
Ref: whatsnew/changelog id942045135
Ref: f4b2045135
Ref: Core and Builtins<16>-Footnote-12046640
Ref: Core and Builtins<16>-Footnote-22046683
Ref: Core and Builtins<16>-Footnote-32046726
Ref: Core and Builtins<16>-Footnote-42046769
Ref: Core and Builtins<16>-Footnote-52046812
Ref: Core and Builtins<16>-Footnote-62046855
Ref: Core and Builtins<16>-Footnote-72046898
Ref: Core and Builtins<16>-Footnote-82046941
Ref: Core and Builtins<16>-Footnote-92046984
Ref: Core and Builtins<16>-Footnote-102047027
Ref: Core and Builtins<16>-Footnote-112047071
Node: Library<16>2047115
Ref: whatsnew/changelog id952047251
Ref: f4d2047251
Ref: Library<16>-Footnote-12051601
Ref: Library<16>-Footnote-22051644
Ref: Library<16>-Footnote-32051687
Ref: Library<16>-Footnote-42051730
Ref: Library<16>-Footnote-52051773
Ref: Library<16>-Footnote-62051816
Ref: Library<16>-Footnote-72051859
Ref: Library<16>-Footnote-82051902
Ref: Library<16>-Footnote-92051945
Ref: Library<16>-Footnote-102051988
Ref: Library<16>-Footnote-112052032
Ref: Library<16>-Footnote-122052076
Ref: Library<16>-Footnote-132052120
Ref: Library<16>-Footnote-142052164
Ref: Library<16>-Footnote-152052208
Ref: Library<16>-Footnote-162052252
Ref: Library<16>-Footnote-172052296
Ref: Library<16>-Footnote-182052340
Ref: Library<16>-Footnote-192052384
Ref: Library<16>-Footnote-202052428
Ref: Library<16>-Footnote-212052472
Ref: Library<16>-Footnote-222052516
Ref: Library<16>-Footnote-232052560
Ref: Library<16>-Footnote-242052604
Ref: Library<16>-Footnote-252052648
Ref: Library<16>-Footnote-262052692
Ref: Library<16>-Footnote-272052736
Node: Documentation<13>2052780
Ref: whatsnew/changelog id962052903
Ref: f502052903
Ref: Documentation<13>-Footnote-12053758
Ref: Documentation<13>-Footnote-22053801
Ref: Documentation<13>-Footnote-32053844
Ref: Documentation<13>-Footnote-42053887
Ref: Documentation<13>-Footnote-52053930
Ref: Documentation<13>-Footnote-62054003
Node: Tests<8>2054045
Ref: whatsnew/changelog id972054165
Ref: f512054165
Ref: Tests<8>-Footnote-12054634
Ref: Tests<8>-Footnote-22054677
Node: Build<8>2054720
Ref: whatsnew/changelog id982054833
Ref: f532054833
Ref: Build<8>-Footnote-12055032
Node: Windows<9>2055075
Ref: whatsnew/changelog id992055188
Ref: f542055188
Ref: Windows<9>-Footnote-12055929
Ref: Windows<9>-Footnote-22055972
Ref: Windows<9>-Footnote-32056015
Ref: Windows<9>-Footnote-42056058
Ref: Windows<9>-Footnote-52056101
Node: IDLE<15>2056144
Ref: whatsnew/changelog id1002056240
Ref: f552056240
Ref: IDLE<15>-Footnote-12056985
Ref: IDLE<15>-Footnote-22057028
Ref: IDLE<15>-Footnote-32057071
Ref: IDLE<15>-Footnote-42057114
Ref: IDLE<15>-Footnote-52057157
Ref: IDLE<15>-Footnote-62057200
Node: Python 3 8 1 final2057243
Ref: whatsnew/changelog python-3-8-1-final2057407
Ref: f562057407
Node: Core and Builtins<17>2057648
Ref: whatsnew/changelog id1012057744
Ref: f572057744
Ref: Core and Builtins<17>-Footnote-12058449
Ref: Core and Builtins<17>-Footnote-22058492
Ref: Core and Builtins<17>-Footnote-32058535
Node: Library<17>2058578
Ref: whatsnew/changelog id1022058691
Ref: f582058691
Ref: Library<17>-Footnote-12059222
Ref: Library<17>-Footnote-22059265
Ref: Library<17>-Footnote-32059308
Node: Tests<9>2059351
Ref: whatsnew/changelog id1032059454
Ref: f592059454
Ref: Tests<9>-Footnote-12059652
Node: Windows<10>2059695
Ref: whatsnew/changelog id1042059795
Ref: f5a2059795
Ref: Windows<10>-Footnote-12059948
Node: macOS<8>2059991
Ref: whatsnew/changelog id1052060091
Ref: f5b2060091
Ref: macOS<8>-Footnote-12060261
Node: IDLE<16>2060304
Ref: whatsnew/changelog id1062060384
Ref: f5c2060384
Ref: IDLE<16>-Footnote-12060666
Ref: IDLE<16>-Footnote-22060709
Node: Python 3 8 1 release candidate 12060752
Ref: whatsnew/changelog python-3-8-1-release-candidate-12060902
Ref: f5d2060902
Node: Security<12>2061272
Ref: whatsnew/changelog id1072061383
Ref: f5e2061383
Ref: Security<12>-Footnote-12062565
Ref: Security<12>-Footnote-22062608
Ref: Security<12>-Footnote-32062651
Ref: Security<12>-Footnote-42062694
Ref: Security<12>-Footnote-52062737
Ref: Security<12>-Footnote-62062780
Ref: Security<12>-Footnote-72062823
Node: Core and Builtins<18>2062866
Ref: whatsnew/changelog id1082062997
Ref: f5f2062997
Ref: Core and Builtins<18>-Footnote-12064359
Ref: Core and Builtins<18>-Footnote-22064402
Ref: Core and Builtins<18>-Footnote-32064445
Ref: Core and Builtins<18>-Footnote-42064488
Ref: Core and Builtins<18>-Footnote-52064531
Ref: Core and Builtins<18>-Footnote-62064574
Ref: Core and Builtins<18>-Footnote-72064617
Ref: Core and Builtins<18>-Footnote-82064660
Ref: Core and Builtins<18>-Footnote-92064703
Node: Library<18>2064746
Ref: whatsnew/changelog id1092064882
Ref: f602064882
Ref: Library<18>-Footnote-12070254
Ref: Library<18>-Footnote-22070297
Ref: Library<18>-Footnote-32070340
Ref: Library<18>-Footnote-42070383
Ref: Library<18>-Footnote-52070426
Ref: Library<18>-Footnote-62070469
Ref: Library<18>-Footnote-72070512
Ref: Library<18>-Footnote-82070555
Ref: Library<18>-Footnote-92070598
Ref: Library<18>-Footnote-102070641
Ref: Library<18>-Footnote-112070685
Ref: Library<18>-Footnote-122070729
Ref: Library<18>-Footnote-132070773
Ref: Library<18>-Footnote-142070817
Ref: Library<18>-Footnote-152070861
Ref: Library<18>-Footnote-162070905
Ref: Library<18>-Footnote-172070949
Ref: Library<18>-Footnote-182070993
Ref: Library<18>-Footnote-192071037
Ref: Library<18>-Footnote-202071081
Ref: Library<18>-Footnote-212071125
Ref: Library<18>-Footnote-222071169
Ref: Library<18>-Footnote-232071213
Ref: Library<18>-Footnote-242071257
Ref: Library<18>-Footnote-252071301
Ref: Library<18>-Footnote-262071345
Ref: Library<18>-Footnote-272071389
Ref: Library<18>-Footnote-282071433
Ref: Library<18>-Footnote-292071477
Ref: Library<18>-Footnote-302071521
Ref: Library<18>-Footnote-312071565
Ref: Library<18>-Footnote-322071609
Ref: Library<18>-Footnote-332071653
Node: Documentation<14>2071697
Ref: whatsnew/changelog id1102071821
Ref: f622071821
Ref: Documentation<14>-Footnote-12072481
Ref: Documentation<14>-Footnote-22072524
Ref: Documentation<14>-Footnote-32072567
Ref: Documentation<14>-Footnote-42072610
Node: Tests<10>2072653
Ref: whatsnew/changelog id1112072774
Ref: f632072774
Ref: Tests<10>-Footnote-12074135
Ref: Tests<10>-Footnote-22074178
Ref: Tests<10>-Footnote-32074221
Ref: Tests<10>-Footnote-42074264
Ref: Tests<10>-Footnote-52074307
Ref: Tests<10>-Footnote-62074350
Ref: Tests<10>-Footnote-72074393
Node: Build<9>2074436
Ref: whatsnew/changelog id1122074551
Ref: f652074551
Ref: Build<9>-Footnote-12075161
Ref: Build<9>-Footnote-22075204
Ref: Build<9>-Footnote-32075247
Ref: Build<9>-Footnote-42075290
Node: Windows<11>2075333
Ref: whatsnew/changelog id1132075447
Ref: f662075447
Ref: Windows<11>-Footnote-12075999
Ref: Windows<11>-Footnote-22076042
Ref: Windows<11>-Footnote-32076085
Ref: Windows<11>-Footnote-42076128
Ref: Windows<11>-Footnote-52076171
Node: macOS<9>2076214
Ref: whatsnew/changelog id1142076328
Ref: f672076328
Ref: macOS<9>-Footnote-12076636
Node: IDLE<17>2076679
Ref: whatsnew/changelog id1152076790
Ref: f682076790
Ref: IDLE<17>-Footnote-12077512
Ref: IDLE<17>-Footnote-22077555
Ref: IDLE<17>-Footnote-32077598
Ref: IDLE<17>-Footnote-42077641
Ref: IDLE<17>-Footnote-52077683
Node: C API<7>2077726
Ref: whatsnew/changelog id1162077820
Ref: f692077820
Ref: C API<7>-Footnote-12078407
Ref: C API<7>-Footnote-22078450
Ref: C API<7>-Footnote-32078493
Node: Python 3 8 0 final2078536
Ref: whatsnew/changelog python-3-8-0-final2078700
Ref: f6b2078700
Node: Core and Builtins<19>2079009
Ref: whatsnew/changelog id1172079105
Ref: f6c2079105
Ref: Core and Builtins<19>-Footnote-12079801
Ref: Core and Builtins<19>-Footnote-22079844
Node: Library<19>2079887
Ref: whatsnew/changelog id1182080009
Ref: f6d2080009
Ref: Library<19>-Footnote-12081377
Ref: Library<19>-Footnote-22081420
Ref: Library<19>-Footnote-32081463
Ref: Library<19>-Footnote-42081506
Ref: Library<19>-Footnote-52081549
Ref: Library<19>-Footnote-62081592
Ref: Library<19>-Footnote-72081635
Node: Documentation<15>2081678
Ref: whatsnew/changelog id1192081788
Ref: f732081788
Ref: Documentation<15>-Footnote-12081962
Node: Tests<11>2082005
Ref: whatsnew/changelog id1202082115
Ref: f742082115
Ref: Tests<11>-Footnote-12082554
Node: Windows<12>2082597
Ref: whatsnew/changelog id1212082698
Ref: f752082698
Ref: Windows<12>-Footnote-12082991
Ref: Windows<12>-Footnote-22083034
Ref: Windows<12>-Footnote-32083077
Node: IDLE<18>2083120
Ref: whatsnew/changelog id1222083226
Ref: f762083226
Ref: IDLE<18>-Footnote-12083525
Node: Tools/Demos<5>2083568
Ref: whatsnew/changelog id1232083671
Ref: f772083671
Ref: Tools/Demos<5>-Footnote-12084027
Ref: Tools/Demos<5>-Footnote-22084070
Node: C API<8>2084113
Ref: whatsnew/changelog id1242084199
Ref: f792084199
Ref: C API<8>-Footnote-12084527
Node: Python 3 8 0 release candidate 12084570
Ref: whatsnew/changelog python-3-8-0-release-candidate-12084721
Ref: f7a2084721
Node: Security<13>2085124
Ref: whatsnew/changelog id1252085235
Ref: f7b2085235
Ref: Security<13>-Footnote-12085884
Ref: Security<13>-Footnote-22085927
Ref: Security<13>-Footnote-32085970
Ref: Security<13>-Footnote-42086013
Node: Core and Builtins<20>2086056
Ref: whatsnew/changelog id1262086187
Ref: f7d2086187
Ref: Core and Builtins<20>-Footnote-12088752
Ref: Core and Builtins<20>-Footnote-22088795
Ref: Core and Builtins<20>-Footnote-32088838
Ref: Core and Builtins<20>-Footnote-42088887
Ref: Core and Builtins<20>-Footnote-52088930
Ref: Core and Builtins<20>-Footnote-62088973
Ref: Core and Builtins<20>-Footnote-72089016
Ref: Core and Builtins<20>-Footnote-82089059
Ref: Core and Builtins<20>-Footnote-92089102
Ref: Core and Builtins<20>-Footnote-102089145
Ref: Core and Builtins<20>-Footnote-112089189
Ref: Core and Builtins<20>-Footnote-122089233
Ref: Core and Builtins<20>-Footnote-132089277
Ref: Core and Builtins<20>-Footnote-142089321
Ref: Core and Builtins<20>-Footnote-152089365
Node: Library<20>2089409
Ref: whatsnew/changelog id1272089545
Ref: f7e2089545
Ref: Library<20>-Footnote-12098653
Ref: Library<20>-Footnote-22098696
Ref: Library<20>-Footnote-32098739
Ref: Library<20>-Footnote-42098782
Ref: Library<20>-Footnote-52098825
Ref: Library<20>-Footnote-62098868
Ref: Library<20>-Footnote-72098911
Ref: Library<20>-Footnote-82098954
Ref: Library<20>-Footnote-92098997
Ref: Library<20>-Footnote-102099040
Ref: Library<20>-Footnote-112099084
Ref: Library<20>-Footnote-122099128
Ref: Library<20>-Footnote-132099172
Ref: Library<20>-Footnote-142099216
Ref: Library<20>-Footnote-152099260
Ref: Library<20>-Footnote-162099304
Ref: Library<20>-Footnote-172099348
Ref: Library<20>-Footnote-182099392
Ref: Library<20>-Footnote-192099436
Ref: Library<20>-Footnote-202099480
Ref: Library<20>-Footnote-212099524
Ref: Library<20>-Footnote-222099568
Ref: Library<20>-Footnote-232099612
Ref: Library<20>-Footnote-242099656
Ref: Library<20>-Footnote-252099700
Ref: Library<20>-Footnote-262099744
Ref: Library<20>-Footnote-272099788
Ref: Library<20>-Footnote-282099832
Ref: Library<20>-Footnote-292099876
Ref: Library<20>-Footnote-302099920
Ref: Library<20>-Footnote-312099964
Ref: Library<20>-Footnote-322100072
Ref: Library<20>-Footnote-332100116
Ref: Library<20>-Footnote-342100160
Ref: Library<20>-Footnote-352100204
Ref: Library<20>-Footnote-362100248
Ref: Library<20>-Footnote-372100292
Ref: Library<20>-Footnote-382100336
Ref: Library<20>-Footnote-392100380
Ref: Library<20>-Footnote-402100424
Ref: Library<20>-Footnote-412100468
Ref: Library<20>-Footnote-422100512
Ref: Library<20>-Footnote-432100556
Ref: Library<20>-Footnote-442100600
Ref: Library<20>-Footnote-452100644
Ref: Library<20>-Footnote-462100688
Ref: Library<20>-Footnote-472100732
Ref: Library<20>-Footnote-482100776
Ref: Library<20>-Footnote-492100820
Ref: Library<20>-Footnote-502100864
Ref: Library<20>-Footnote-512100908
Ref: Library<20>-Footnote-522100952
Ref: Library<20>-Footnote-532100996
Ref: Library<20>-Footnote-542101040
Ref: Library<20>-Footnote-552101084
Ref: Library<20>-Footnote-562101128
Ref: Library<20>-Footnote-572101172
Ref: Library<20>-Footnote-582101216
Ref: Library<20>-Footnote-592101260
Node: Documentation<16>2101304
Ref: whatsnew/changelog id1282101428
Ref: f822101428
Ref: Documentation<16>-Footnote-12102705
Ref: Documentation<16>-Footnote-22102748
Ref: Documentation<16>-Footnote-32102791
Ref: Documentation<16>-Footnote-42102834
Ref: Documentation<16>-Footnote-52102877
Ref: Documentation<16>-Footnote-62102920
Ref: Documentation<16>-Footnote-72102963
Ref: Documentation<16>-Footnote-82103006
Ref: Documentation<16>-Footnote-92103049
Ref: Documentation<16>-Footnote-102103092
Node: Tests<12>2103136
Ref: whatsnew/changelog id1292103258
Ref: f842103258
Ref: Tests<12>-Footnote-12105483
Ref: Tests<12>-Footnote-22105526
Ref: Tests<12>-Footnote-32105569
Ref: Tests<12>-Footnote-42105612
Ref: Tests<12>-Footnote-52105655
Ref: Tests<12>-Footnote-62105698
Ref: Tests<12>-Footnote-72105741
Ref: Tests<12>-Footnote-82105784
Ref: Tests<12>-Footnote-92105827
Ref: Tests<12>-Footnote-102105870
Ref: Tests<12>-Footnote-112105914
Ref: Tests<12>-Footnote-122105958
Ref: Tests<12>-Footnote-132106002
Node: Build<10>2106046
Ref: whatsnew/changelog id1302106162
Ref: f862106162
Ref: Build<10>-Footnote-12107446
Ref: Build<10>-Footnote-22107489
Ref: Build<10>-Footnote-32107532
Ref: Build<10>-Footnote-42107575
Ref: Build<10>-Footnote-52107618
Node: Windows<13>2107661
Ref: whatsnew/changelog id1312107777
Ref: f872107777
Ref: Windows<13>-Footnote-12109731
Ref: Windows<13>-Footnote-22109774
Ref: Windows<13>-Footnote-32109817
Ref: Windows<13>-Footnote-42109860
Ref: Windows<13>-Footnote-52109903
Ref: Windows<13>-Footnote-62109946
Ref: Windows<13>-Footnote-72109989
Ref: Windows<13>-Footnote-82110032
Ref: Windows<13>-Footnote-92110075
Ref: Windows<13>-Footnote-102110118
Ref: Windows<13>-Footnote-112110162
Ref: Windows<13>-Footnote-122110206
Ref: Windows<13>-Footnote-132110250
Ref: Windows<13>-Footnote-142110294
Ref: Windows<13>-Footnote-152110338
Ref: Windows<13>-Footnote-162110382
Ref: Windows<13>-Footnote-172110426
Node: macOS<10>2110470
Ref: whatsnew/changelog id1322110585
Ref: f892110585
Ref: macOS<10>-Footnote-12110818
Ref: macOS<10>-Footnote-22110861
Node: IDLE<19>2110904
Ref: whatsnew/changelog id1332111022
Ref: f8a2111022
Ref: IDLE<19>-Footnote-12112175
Ref: IDLE<19>-Footnote-22112218
Ref: IDLE<19>-Footnote-32112261
Ref: IDLE<19>-Footnote-42112304
Ref: IDLE<19>-Footnote-52112347
Ref: IDLE<19>-Footnote-62112390
Node: Tools/Demos<6>2112433
Ref: whatsnew/changelog id1342112550
Ref: f8b2112550
Ref: Tools/Demos<6>-Footnote-12112856
Ref: Tools/Demos<6>-Footnote-22112899
Node: C API<9>2112942
Ref: whatsnew/changelog id1352113042
Ref: f8c2113042
Ref: C API<9>-Footnote-12113767
Ref: C API<9>-Footnote-22113810
Ref: C API<9>-Footnote-32113853
Ref: C API<9>-Footnote-42113896
Node: Python 3 8 0 beta 42113939
Ref: whatsnew/changelog python-3-8-0-beta-42114091
Ref: f902114091
Node: Security<14>2114469
Ref: whatsnew/changelog id1362114567
Ref: f912114567
Ref: Security<14>-Footnote-12114850
Node: Core and Builtins<21>2114893
Ref: whatsnew/changelog id1372115011
Ref: f922115011
Ref: Core and Builtins<21>-Footnote-12116442
Ref: Core and Builtins<21>-Footnote-22116485
Ref: Core and Builtins<21>-Footnote-32116528
Ref: Core and Builtins<21>-Footnote-42116571
Ref: Core and Builtins<21>-Footnote-52116614
Ref: Core and Builtins<21>-Footnote-62116657
Ref: Core and Builtins<21>-Footnote-72116706
Ref: Core and Builtins<21>-Footnote-82116749
Ref: Core and Builtins<21>-Footnote-92116792
Node: Library<21>2116835
Ref: whatsnew/changelog id1382116958
Ref: f932116958
Ref: Library<21>-Footnote-12122996
Ref: Library<21>-Footnote-22123039
Ref: Library<21>-Footnote-32123082
Ref: Library<21>-Footnote-42123125
Ref: Library<21>-Footnote-52123168
Ref: Library<21>-Footnote-62123211
Ref: Library<21>-Footnote-72123254
Ref: Library<21>-Footnote-82123297
Ref: Library<21>-Footnote-92123340
Ref: Library<21>-Footnote-102123383
Ref: Library<21>-Footnote-112123427
Ref: Library<21>-Footnote-122123471
Ref: Library<21>-Footnote-132123515
Ref: Library<21>-Footnote-142123559
Ref: Library<21>-Footnote-152123603
Ref: Library<21>-Footnote-162123647
Ref: Library<21>-Footnote-172123691
Ref: Library<21>-Footnote-182123735
Ref: Library<21>-Footnote-192123779
Ref: Library<21>-Footnote-202123823
Ref: Library<21>-Footnote-212123867
Ref: Library<21>-Footnote-222123911
Ref: Library<21>-Footnote-232123955
Ref: Library<21>-Footnote-242123999
Ref: Library<21>-Footnote-252124043
Ref: Library<21>-Footnote-262124087
Ref: Library<21>-Footnote-272124131
Ref: Library<21>-Footnote-282124175
Ref: Library<21>-Footnote-292124219
Ref: Library<21>-Footnote-302124263
Ref: Library<21>-Footnote-312124307
Ref: Library<21>-Footnote-322124351
Ref: Library<21>-Footnote-332124395
Ref: Library<21>-Footnote-342124439
Ref: Library<21>-Footnote-352124483
Ref: Library<21>-Footnote-362124527
Ref: Library<21>-Footnote-372124571
Ref: Library<21>-Footnote-382124615
Node: Documentation<17>2124659
Ref: whatsnew/changelog id1392124770
Ref: f952124770
Ref: Documentation<17>-Footnote-12125545
Ref: Documentation<17>-Footnote-22125588
Ref: Documentation<17>-Footnote-32125631
Ref: Documentation<17>-Footnote-42125674
Ref: Documentation<17>-Footnote-52125717
Ref: Documentation<17>-Footnote-62125760
Node: Tests<13>2125803
Ref: whatsnew/changelog id1402125912
Ref: f962125912
Ref: Tests<13>-Footnote-12126074
Node: Build<11>2126117
Ref: whatsnew/changelog id1412126220
Ref: f972126220
Ref: Build<11>-Footnote-12126503
Node: Windows<14>2126546
Ref: whatsnew/changelog id1422126649
Ref: f982126649
Ref: Windows<14>-Footnote-12128131
Ref: Windows<14>-Footnote-22128174
Ref: Windows<14>-Footnote-32128216
Ref: Windows<14>-Footnote-42128258
Ref: Windows<14>-Footnote-52128301
Ref: Windows<14>-Footnote-62128344
Ref: Windows<14>-Footnote-72128387
Ref: Windows<14>-Footnote-82128430
Ref: Windows<14>-Footnote-92128473
Node: macOS<11>2128516
Ref: whatsnew/changelog id1432128618
Ref: f9a2128618
Ref: macOS<11>-Footnote-12128882
Node: IDLE<20>2128925
Ref: whatsnew/changelog id1442129030
Ref: f9b2129030
Ref: IDLE<20>-Footnote-12129595
Ref: IDLE<20>-Footnote-22129638
Ref: IDLE<20>-Footnote-32129681
Ref: IDLE<20>-Footnote-42129724
Ref: IDLE<20>-Footnote-52129767
Node: Tools/Demos<7>2129810
Ref: whatsnew/changelog id1452129915
Ref: f9c2129915
Ref: Tools/Demos<7>-Footnote-12130237
Ref: Tools/Demos<7>-Footnote-22130280
Node: C API<10>2130323
Ref: whatsnew/changelog id1462130411
Ref: f9d2130411
Ref: C API<10>-Footnote-12130717
Ref: C API<10>-Footnote-22130760
Node: Python 3 8 0 beta 32130803
Ref: whatsnew/changelog python-3-8-0-beta-32130942
Ref: f9e2130942
Node: Security<15>2131280
Ref: whatsnew/changelog id1472131378
Ref: f9f2131378
Ref: Security<15>-Footnote-12131569
Node: Core and Builtins<22>2131612
Ref: whatsnew/changelog id1482131730
Ref: fa02131730
Ref: Core and Builtins<22>-Footnote-12132133
Ref: Core and Builtins<22>-Footnote-22132176
Node: Library<22>2132219
Ref: whatsnew/changelog id1492132342
Ref: fa12132342
Ref: Library<22>-Footnote-12135314
Ref: Library<22>-Footnote-22135357
Ref: Library<22>-Footnote-32135431
Ref: Library<22>-Footnote-42135474
Ref: Library<22>-Footnote-52135517
Ref: Library<22>-Footnote-62135560
Ref: Library<22>-Footnote-72135603
Ref: Library<22>-Footnote-82135646
Ref: Library<22>-Footnote-92135689
Ref: Library<22>-Footnote-102135732
Ref: Library<22>-Footnote-112135776
Ref: Library<22>-Footnote-122135820
Ref: Library<22>-Footnote-132135864
Ref: Library<22>-Footnote-142135908
Ref: Library<22>-Footnote-152135952
Ref: Library<22>-Footnote-162135996
Node: Documentation<18>2136040
Ref: whatsnew/changelog id1502136151
Ref: fa62136151
Ref: Documentation<18>-Footnote-12137299
Ref: Documentation<18>-Footnote-22137342
Ref: Documentation<18>-Footnote-32137385
Ref: Documentation<18>-Footnote-42137428
Ref: Documentation<18>-Footnote-52137471
Ref: Documentation<18>-Footnote-62137514
Ref: Documentation<18>-Footnote-72137557
Ref: Documentation<18>-Footnote-82137600
Node: Tests<14>2137643
Ref: whatsnew/changelog id1512137752
Ref: fa72137752
Ref: Tests<14>-Footnote-12138421
Ref: Tests<14>-Footnote-22138464
Ref: Tests<14>-Footnote-32138507
Ref: Tests<14>-Footnote-42138550
Node: Build<12>2138593
Ref: whatsnew/changelog id1522138696
Ref: fa92138696
Ref: Build<12>-Footnote-12139461
Node: Windows<15>2139504
Ref: whatsnew/changelog id1532139606
Ref: faa2139606
Ref: Windows<15>-Footnote-12139806
Node: IDLE<21>2139849
Ref: whatsnew/changelog id1542139956
Ref: fab2139956
Ref: IDLE<21>-Footnote-12141435
Ref: IDLE<21>-Footnote-22141478
Ref: IDLE<21>-Footnote-32141521
Ref: IDLE<21>-Footnote-42141564
Ref: IDLE<21>-Footnote-52141607
Ref: IDLE<21>-Footnote-62141650
Ref: IDLE<21>-Footnote-72141693
Ref: IDLE<21>-Footnote-82141736
Ref: IDLE<21>-Footnote-92141779
Node: Tools/Demos<8>2141822
Ref: whatsnew/changelog id1552141909
Ref: fac2141909
Ref: Tools/Demos<8>-Footnote-12142071
Node: Python 3 8 0 beta 22142114
Ref: whatsnew/changelog python-3-8-0-beta-22142253
Ref: fad2142253
Node: Security<16>2142600
Ref: whatsnew/changelog id1562142698
Ref: fae2142698
Ref: Security<16>-Footnote-12143810
Ref: Security<16>-Footnote-22143853
Ref: Security<16>-Footnote-32143896
Ref: Security<16>-Footnote-42143939
Ref: Security<16>-Footnote-52143982
Node: Core and Builtins<23>2144025
Ref: whatsnew/changelog id1572144143
Ref: fb02144143
Ref: Core and Builtins<23>-Footnote-12145865
Ref: Core and Builtins<23>-Footnote-22145908
Ref: Core and Builtins<23>-Footnote-32145951
Ref: Core and Builtins<23>-Footnote-42145994
Ref: Core and Builtins<23>-Footnote-52146037
Ref: Core and Builtins<23>-Footnote-62146080
Ref: Core and Builtins<23>-Footnote-72146123
Ref: Core and Builtins<23>-Footnote-82146166
Ref: Core and Builtins<23>-Footnote-92146209
Ref: Core and Builtins<23>-Footnote-102146252
Ref: Core and Builtins<23>-Footnote-112146296
Ref: Core and Builtins<23>-Footnote-122146340
Node: Library<23>2146384
Ref: whatsnew/changelog id1582146507
Ref: fb12146507
Ref: Library<23>-Footnote-12152200
Ref: Library<23>-Footnote-22152243
Ref: Library<23>-Footnote-32152286
Ref: Library<23>-Footnote-42152329
Ref: Library<23>-Footnote-52152372
Ref: Library<23>-Footnote-62152415
Ref: Library<23>-Footnote-72152464
Ref: Library<23>-Footnote-82152507
Ref: Library<23>-Footnote-92152550
Ref: Library<23>-Footnote-102152593
Ref: Library<23>-Footnote-112152637
Ref: Library<23>-Footnote-122152681
Ref: Library<23>-Footnote-132152725
Ref: Library<23>-Footnote-142152769
Ref: Library<23>-Footnote-152152813
Ref: Library<23>-Footnote-162152857
Ref: Library<23>-Footnote-172152901
Ref: Library<23>-Footnote-182152945
Ref: Library<23>-Footnote-192152989
Ref: Library<23>-Footnote-202153033
Ref: Library<23>-Footnote-212153077
Ref: Library<23>-Footnote-222153121
Ref: Library<23>-Footnote-232153165
Ref: Library<23>-Footnote-242153209
Ref: Library<23>-Footnote-252153253
Ref: Library<23>-Footnote-262153297
Ref: Library<23>-Footnote-272153341
Ref: Library<23>-Footnote-282153385
Ref: Library<23>-Footnote-292153429
Ref: Library<23>-Footnote-302153473
Ref: Library<23>-Footnote-312153517
Ref: Library<23>-Footnote-322153561
Ref: Library<23>-Footnote-332153605
Ref: Library<23>-Footnote-342153649
Ref: Library<23>-Footnote-352153693
Ref: Library<23>-Footnote-362153737
Node: Documentation<19>2153780
Ref: whatsnew/changelog id1592153891
Ref: fb32153891
Ref: Documentation<19>-Footnote-12154144
Node: Tests<15>2154187
Ref: whatsnew/changelog id1602154296
Ref: fb52154296
Ref: Tests<15>-Footnote-12156865
Ref: Tests<15>-Footnote-22156908
Ref: Tests<15>-Footnote-32156951
Ref: Tests<15>-Footnote-42156994
Ref: Tests<15>-Footnote-52157037
Ref: Tests<15>-Footnote-62157080
Ref: Tests<15>-Footnote-72157123
Ref: Tests<15>-Footnote-82157166
Ref: Tests<15>-Footnote-92157209
Ref: Tests<15>-Footnote-102157252
Ref: Tests<15>-Footnote-112157296
Ref: Tests<15>-Footnote-122157340
Ref: Tests<15>-Footnote-132157384
Ref: Tests<15>-Footnote-142157428
Ref: Tests<15>-Footnote-152157472
Ref: Tests<15>-Footnote-162157516
Ref: Tests<15>-Footnote-172157560
Node: Build<13>2157604
Ref: whatsnew/changelog id1612157707
Ref: fb72157707
Ref: Build<13>-Footnote-12157980
Node: Windows<16>2158023
Ref: whatsnew/changelog id1622158126
Ref: fb92158126
Ref: Windows<16>-Footnote-12158817
Ref: Windows<16>-Footnote-22158860
Ref: Windows<16>-Footnote-32158903
Ref: Windows<16>-Footnote-42158946
Ref: Windows<16>-Footnote-52158989
Ref: Windows<16>-Footnote-62159032
Node: macOS<12>2159075
Ref: whatsnew/changelog id1632159177
Ref: fba2159177
Ref: macOS<12>-Footnote-12159651
Ref: macOS<12>-Footnote-22159694
Ref: macOS<12>-Footnote-32159737
Node: IDLE<22>2159780
Ref: whatsnew/changelog id1642159880
Ref: fbb2159880
Ref: IDLE<22>-Footnote-12161022
Ref: IDLE<22>-Footnote-22161065
Ref: IDLE<22>-Footnote-32161108
Ref: IDLE<22>-Footnote-42161151
Ref: IDLE<22>-Footnote-52161194
Ref: IDLE<22>-Footnote-62161237
Node: C API<11>2161279
Ref: whatsnew/changelog id1652161361
Ref: fbc2161361
Ref: C API<11>-Footnote-12162537
Ref: C API<11>-Footnote-22162580
Ref: C API<11>-Footnote-32162623
Ref: C API<11>-Footnote-42162666
Ref: C API<11>-Footnote-52162709
Ref: C API<11>-Footnote-62162752
Ref: C API<11>-Footnote-72162795
Ref: C API<11>-Footnote-82162838
Node: Python 3 8 0 beta 12162881
Ref: whatsnew/changelog python-3-8-0-beta-12163021
Ref: fbf2163021
Node: Security<17>2163399
Ref: whatsnew/changelog id1662163497
Ref: fc02163497
Ref: Security<17>-Footnote-12164088
Ref: Security<17>-Footnote-22164131
Ref: Security<17>-Footnote-32164174
Node: Core and Builtins<24>2164217
Ref: whatsnew/changelog id1672164335
Ref: fc12164335
Ref: Core and Builtins<24>-Footnote-12172400
Ref: Core and Builtins<24>-Footnote-22172443
Ref: Core and Builtins<24>-Footnote-32172486
Ref: Core and Builtins<24>-Footnote-42172529
Ref: Core and Builtins<24>-Footnote-52172572
Ref: Core and Builtins<24>-Footnote-62172615
Ref: Core and Builtins<24>-Footnote-72172658
Ref: Core and Builtins<24>-Footnote-82172701
Ref: Core and Builtins<24>-Footnote-92172744
Ref: Core and Builtins<24>-Footnote-102172787
Ref: Core and Builtins<24>-Footnote-112172831
Ref: Core and Builtins<24>-Footnote-122172875
Ref: Core and Builtins<24>-Footnote-132172919
Ref: Core and Builtins<24>-Footnote-142172963
Ref: Core and Builtins<24>-Footnote-152173007
Ref: Core and Builtins<24>-Footnote-162173051
Ref: Core and Builtins<24>-Footnote-172173095
Ref: Core and Builtins<24>-Footnote-182173139
Ref: Core and Builtins<24>-Footnote-192173182
Ref: Core and Builtins<24>-Footnote-202173226
Ref: Core and Builtins<24>-Footnote-212173270
Ref: Core and Builtins<24>-Footnote-222173314
Ref: Core and Builtins<24>-Footnote-232173357
Ref: Core and Builtins<24>-Footnote-242173401
Ref: Core and Builtins<24>-Footnote-252173445
Ref: Core and Builtins<24>-Footnote-262173489
Ref: Core and Builtins<24>-Footnote-272173533
Ref: Core and Builtins<24>-Footnote-282173577
Ref: Core and Builtins<24>-Footnote-292173621
Ref: Core and Builtins<24>-Footnote-302173665
Ref: Core and Builtins<24>-Footnote-312173709
Ref: Core and Builtins<24>-Footnote-322173753
Ref: Core and Builtins<24>-Footnote-332173797
Ref: Core and Builtins<24>-Footnote-342173841
Ref: Core and Builtins<24>-Footnote-352173885
Ref: Core and Builtins<24>-Footnote-362173929
Ref: Core and Builtins<24>-Footnote-372173973
Ref: Core and Builtins<24>-Footnote-382174017
Ref: Core and Builtins<24>-Footnote-392174061
Ref: Core and Builtins<24>-Footnote-402174105
Ref: Core and Builtins<24>-Footnote-412174149
Ref: Core and Builtins<24>-Footnote-422174193
Ref: Core and Builtins<24>-Footnote-432174237
Ref: Core and Builtins<24>-Footnote-442174281
Node: Library<24>2174325
Ref: whatsnew/changelog id1682174448
Ref: fc72174448
Ref: Library<24>-Footnote-12192739
Ref: Library<24>-Footnote-22192782
Ref: Library<24>-Footnote-32192825
Ref: Library<24>-Footnote-42192868
Ref: Library<24>-Footnote-52192911
Ref: Library<24>-Footnote-62192954
Ref: Library<24>-Footnote-72192997
Ref: Library<24>-Footnote-82193040
Ref: Library<24>-Footnote-92193083
Ref: Library<24>-Footnote-102193126
Ref: Library<24>-Footnote-112193170
Ref: Library<24>-Footnote-122193214
Ref: Library<24>-Footnote-132193258
Ref: Library<24>-Footnote-142193302
Ref: Library<24>-Footnote-152193346
Ref: Library<24>-Footnote-162193390
Ref: Library<24>-Footnote-172193434
Ref: Library<24>-Footnote-182193478
Ref: Library<24>-Footnote-192193522
Ref: Library<24>-Footnote-202193566
Ref: Library<24>-Footnote-212193610
Ref: Library<24>-Footnote-222193654
Ref: Library<24>-Footnote-232193698
Ref: Library<24>-Footnote-242193742
Ref: Library<24>-Footnote-252193788
Ref: Library<24>-Footnote-262193832
Ref: Library<24>-Footnote-272193876
Ref: Library<24>-Footnote-282193920
Ref: Library<24>-Footnote-292193964
Ref: Library<24>-Footnote-302194008
Ref: Library<24>-Footnote-312194052
Ref: Library<24>-Footnote-322194096
Ref: Library<24>-Footnote-332194140
Ref: Library<24>-Footnote-342194184
Ref: Library<24>-Footnote-352194228
Ref: Library<24>-Footnote-362194272
Ref: Library<24>-Footnote-372194316
Ref: Library<24>-Footnote-382194360
Ref: Library<24>-Footnote-392194404
Ref: Library<24>-Footnote-402194448
Ref: Library<24>-Footnote-412194492
Ref: Library<24>-Footnote-422194536
Ref: Library<24>-Footnote-432194580
Ref: Library<24>-Footnote-442194624
Ref: Library<24>-Footnote-452194668
Ref: Library<24>-Footnote-462194712
Ref: Library<24>-Footnote-472194756
Ref: Library<24>-Footnote-482194800
Ref: Library<24>-Footnote-492194844
Ref: Library<24>-Footnote-502194888
Ref: Library<24>-Footnote-512194932
Ref: Library<24>-Footnote-522194976
Ref: Library<24>-Footnote-532195020
Ref: Library<24>-Footnote-542195064
Ref: Library<24>-Footnote-552195108
Ref: Library<24>-Footnote-562195152
Ref: Library<24>-Footnote-572195196
Ref: Library<24>-Footnote-582195240
Ref: Library<24>-Footnote-592195284
Ref: Library<24>-Footnote-602195328
Ref: Library<24>-Footnote-612195372
Ref: Library<24>-Footnote-622195416
Ref: Library<24>-Footnote-632195460
Ref: Library<24>-Footnote-642195504
Ref: Library<24>-Footnote-652195548
Ref: Library<24>-Footnote-662195592
Ref: Library<24>-Footnote-672195636
Ref: Library<24>-Footnote-682195680
Ref: Library<24>-Footnote-692195723
Ref: Library<24>-Footnote-702195767
Ref: Library<24>-Footnote-712195810
Ref: Library<24>-Footnote-722195854
Ref: Library<24>-Footnote-732195898
Ref: Library<24>-Footnote-742195942
Ref: Library<24>-Footnote-752195986
Ref: Library<24>-Footnote-762196030
Ref: Library<24>-Footnote-772196074
Ref: Library<24>-Footnote-782196118
Ref: Library<24>-Footnote-792196162
Ref: Library<24>-Footnote-802196206
Ref: Library<24>-Footnote-812196250
Ref: Library<24>-Footnote-822196294
Ref: Library<24>-Footnote-832196338
Ref: Library<24>-Footnote-842196382
Ref: Library<24>-Footnote-852196426
Ref: Library<24>-Footnote-862196470
Ref: Library<24>-Footnote-872196514
Ref: Library<24>-Footnote-882196558
Ref: Library<24>-Footnote-892196602
Ref: Library<24>-Footnote-902196646
Ref: Library<24>-Footnote-912196690
Ref: Library<24>-Footnote-922196734
Ref: Library<24>-Footnote-932196778
Ref: Library<24>-Footnote-942196822
Ref: Library<24>-Footnote-952196866
Ref: Library<24>-Footnote-962196910
Ref: Library<24>-Footnote-972196954
Ref: Library<24>-Footnote-982196998
Ref: Library<24>-Footnote-992197042
Ref: Library<24>-Footnote-1002197086
Ref: Library<24>-Footnote-1012197131
Ref: Library<24>-Footnote-1022197176
Ref: Library<24>-Footnote-1032197221
Ref: Library<24>-Footnote-1042197266
Ref: Library<24>-Footnote-1052197311
Ref: Library<24>-Footnote-1062197356
Ref: Library<24>-Footnote-1072197401
Node: Documentation<20>2197446
Ref: whatsnew/changelog id1692197557
Ref: fd52197557
Ref: Documentation<20>-Footnote-12199646
Ref: Documentation<20>-Footnote-22199689
Ref: Documentation<20>-Footnote-32199732
Ref: Documentation<20>-Footnote-42199775
Ref: Documentation<20>-Footnote-52199818
Ref: Documentation<20>-Footnote-62199861
Ref: Documentation<20>-Footnote-72199904
Ref: Documentation<20>-Footnote-82199947
Ref: Documentation<20>-Footnote-92199990
Ref: Documentation<20>-Footnote-102200033
Ref: Documentation<20>-Footnote-112200077
Ref: Documentation<20>-Footnote-122200121
Ref: Documentation<20>-Footnote-132200165
Ref: Documentation<20>-Footnote-142200209
Node: Tests<16>2200253
Ref: whatsnew/changelog id1702200362
Ref: fd62200362
Ref: Tests<16>-Footnote-12201995
Ref: Tests<16>-Footnote-22202038
Ref: Tests<16>-Footnote-32202081
Ref: Tests<16>-Footnote-42202124
Ref: Tests<16>-Footnote-52202167
Ref: Tests<16>-Footnote-62202210
Ref: Tests<16>-Footnote-72202253
Ref: Tests<16>-Footnote-82202296
Ref: Tests<16>-Footnote-92202339
Ref: Tests<16>-Footnote-102202382
Node: Build<14>2202426
Ref: whatsnew/changelog id1712202529
Ref: fd82202529
Ref: Build<14>-Footnote-12203741
Ref: Build<14>-Footnote-22203784
Node: Windows<17>2203827
Ref: whatsnew/changelog id1722203930
Ref: fd92203930
Ref: Windows<17>-Footnote-12204356
Ref: Windows<17>-Footnote-22204399
Ref: Windows<17>-Footnote-32204442
Ref: Windows<17>-Footnote-42204485
Node: macOS<13>2204528
Ref: whatsnew/changelog id1732204630
Ref: fda2204630
Ref: macOS<13>-Footnote-12204932
Node: IDLE<23>2204975
Ref: whatsnew/changelog id1742205080
Ref: fdb2205080
Ref: IDLE<23>-Footnote-12205682
Ref: IDLE<23>-Footnote-22205725
Ref: IDLE<23>-Footnote-32205768
Ref: IDLE<23>-Footnote-42205811
Ref: IDLE<23>-Footnote-52205854
Ref: IDLE<23>-Footnote-62205897
Node: Tools/Demos<9>2205940
Ref: whatsnew/changelog id1752206045
Ref: fdc2206045
Ref: Tools/Demos<9>-Footnote-12206244
Node: C API<12>2206287
Ref: whatsnew/changelog id1762206375
Ref: fdd2206375
Ref: C API<12>-Footnote-12207710
Ref: C API<12>-Footnote-22207753
Ref: C API<12>-Footnote-32207802
Ref: C API<12>-Footnote-42207845
Ref: C API<12>-Footnote-52207888
Ref: C API<12>-Footnote-62207931
Ref: C API<12>-Footnote-72207980
Ref: C API<12>-Footnote-82208023
Ref: C API<12>-Footnote-92208066
Node: Python 3 8 0 alpha 42208109
Ref: whatsnew/changelog python-3-8-0-alpha-42208250
Ref: fdf2208250
Node: Security<18>2208631
Ref: whatsnew/changelog id1772208730
Ref: fe02208730
Ref: Security<18>-Footnote-12209612
Ref: Security<18>-Footnote-22209655
Ref: Security<18>-Footnote-32209698
Node: Core and Builtins<25>2209741
Ref: whatsnew/changelog id1782209860
Ref: fe12209860
Ref: Core and Builtins<25>-Footnote-12213152
Ref: Core and Builtins<25>-Footnote-22213195
Ref: Core and Builtins<25>-Footnote-32213238
Ref: Core and Builtins<25>-Footnote-42213281
Ref: Core and Builtins<25>-Footnote-52213324
Ref: Core and Builtins<25>-Footnote-62213367
Ref: Core and Builtins<25>-Footnote-72213410
Ref: Core and Builtins<25>-Footnote-82213453
Ref: Core and Builtins<25>-Footnote-92213496
Ref: Core and Builtins<25>-Footnote-102213545
Ref: Core and Builtins<25>-Footnote-112213589
Ref: Core and Builtins<25>-Footnote-122213633
Ref: Core and Builtins<25>-Footnote-132213677
Ref: Core and Builtins<25>-Footnote-142213721
Ref: Core and Builtins<25>-Footnote-152213765
Ref: Core and Builtins<25>-Footnote-162213809
Ref: Core and Builtins<25>-Footnote-172213853
Ref: Core and Builtins<25>-Footnote-182213897
Ref: Core and Builtins<25>-Footnote-192213941
Ref: Core and Builtins<25>-Footnote-202213985
Node: Library<25>2214029
Ref: whatsnew/changelog id1792214153
Ref: fe22214153
Ref: Library<25>-Footnote-12223460
Ref: Library<25>-Footnote-22223503
Ref: Library<25>-Footnote-32223546
Ref: Library<25>-Footnote-42223589
Ref: Library<25>-Footnote-52223634
Ref: Library<25>-Footnote-62223677
Ref: Library<25>-Footnote-72223720
Ref: Library<25>-Footnote-82223763
Ref: Library<25>-Footnote-92223806
Ref: Library<25>-Footnote-102223849
Ref: Library<25>-Footnote-112223893
Ref: Library<25>-Footnote-122223937
Ref: Library<25>-Footnote-132223981
Ref: Library<25>-Footnote-142224025
Ref: Library<25>-Footnote-152224069
Ref: Library<25>-Footnote-162224113
Ref: Library<25>-Footnote-172224157
Ref: Library<25>-Footnote-182224201
Ref: Library<25>-Footnote-192224245
Ref: Library<25>-Footnote-202224289
Ref: Library<25>-Footnote-212224333
Ref: Library<25>-Footnote-222224377
Ref: Library<25>-Footnote-232224421
Ref: Library<25>-Footnote-242224465
Ref: Library<25>-Footnote-252224509
Ref: Library<25>-Footnote-262224553
Ref: Library<25>-Footnote-272224597
Ref: Library<25>-Footnote-282224641
Ref: Library<25>-Footnote-292224685
Ref: Library<25>-Footnote-302224729
Ref: Library<25>-Footnote-312224773
Ref: Library<25>-Footnote-322224817
Ref: Library<25>-Footnote-332224861
Ref: Library<25>-Footnote-342224905
Ref: Library<25>-Footnote-352224949
Ref: Library<25>-Footnote-362224993
Ref: Library<25>-Footnote-372225037
Ref: Library<25>-Footnote-382225081
Ref: Library<25>-Footnote-392225125
Ref: Library<25>-Footnote-402225169
Ref: Library<25>-Footnote-412225213
Ref: Library<25>-Footnote-422225257
Ref: Library<25>-Footnote-432225301
Ref: Library<25>-Footnote-442225345
Ref: Library<25>-Footnote-452225389
Ref: Library<25>-Footnote-462225433
Ref: Library<25>-Footnote-472225477
Ref: Library<25>-Footnote-482225521
Ref: Library<25>-Footnote-492225565
Ref: Library<25>-Footnote-502225609
Ref: Library<25>-Footnote-512225653
Ref: Library<25>-Footnote-522225697
Ref: Library<25>-Footnote-532225741
Ref: Library<25>-Footnote-542225785
Node: Documentation<21>2225829
Ref: whatsnew/changelog id1802225941
Ref: fe72225941
Ref: Documentation<21>-Footnote-12227390
Ref: Documentation<21>-Footnote-22227433
Ref: Documentation<21>-Footnote-32227476
Ref: Documentation<21>-Footnote-42227519
Ref: Documentation<21>-Footnote-52227562
Ref: Documentation<21>-Footnote-62227601
Ref: Documentation<21>-Footnote-72227644
Ref: Documentation<21>-Footnote-82227687
Ref: Documentation<21>-Footnote-92227730
Ref: Documentation<21>-Footnote-102227773
Ref: Documentation<21>-Footnote-112227817
Ref: Documentation<21>-Footnote-122227861
Node: Tests<17>2227905
Ref: whatsnew/changelog id1812228015
Ref: fe82228015
Ref: Tests<17>-Footnote-12230265
Ref: Tests<17>-Footnote-22230308
Ref: Tests<17>-Footnote-32230351
Ref: Tests<17>-Footnote-42230394
Ref: Tests<17>-Footnote-52230437
Ref: Tests<17>-Footnote-62230480
Ref: Tests<17>-Footnote-72230523
Ref: Tests<17>-Footnote-82230566
Ref: Tests<17>-Footnote-92230609
Ref: Tests<17>-Footnote-102230652
Ref: Tests<17>-Footnote-112230696
Ref: Tests<17>-Footnote-122230740
Ref: Tests<17>-Footnote-132230784
Ref: Tests<17>-Footnote-142230828
Ref: Tests<17>-Footnote-152230872
Node: Build<15>2230916
Ref: whatsnew/changelog id1822231020
Ref: fea2231020
Ref: Build<15>-Footnote-12234171
Ref: Build<15>-Footnote-22234214
Ref: Build<15>-Footnote-32234257
Ref: Build<15>-Footnote-42234300
Ref: Build<15>-Footnote-52234343
Ref: Build<15>-Footnote-62234386
Ref: Build<15>-Footnote-72234429
Ref: Build<15>-Footnote-82234472
Ref: Build<15>-Footnote-92234515
Ref: Build<15>-Footnote-102234558
Ref: Build<15>-Footnote-112234602
Ref: Build<15>-Footnote-122234646
Ref: Build<15>-Footnote-132234690
Node: Windows<18>2234734
Ref: whatsnew/changelog id1832234838
Ref: feb2234838
Ref: Windows<18>-Footnote-12237490
Ref: Windows<18>-Footnote-22237533
Ref: Windows<18>-Footnote-32237576
Ref: Windows<18>-Footnote-42237619
Ref: Windows<18>-Footnote-52237662
Ref: Windows<18>-Footnote-62237705
Ref: Windows<18>-Footnote-72237748
Ref: Windows<18>-Footnote-82237791
Ref: Windows<18>-Footnote-92237834
Ref: Windows<18>-Footnote-102237877
Ref: Windows<18>-Footnote-112237921
Ref: Windows<18>-Footnote-122237965
Node: macOS<14>2238009
Ref: whatsnew/changelog id1842238112
Ref: fec2238112
Ref: macOS<14>-Footnote-12238426
Ref: macOS<14>-Footnote-22238469
Node: IDLE<24>2238512
Ref: whatsnew/changelog id1852238619
Ref: fed2238619
Ref: IDLE<24>-Footnote-12238866
Node: Tools/Demos<10>2238909
Ref: whatsnew/changelog id1862239016
Ref: fee2239016
Ref: Tools/Demos<10>-Footnote-12239170
Node: C API<13>2239213
Ref: whatsnew/changelog id1872239303
Ref: fef2239303
Ref: C API<13>-Footnote-12241303
Ref: C API<13>-Footnote-22241346
Ref: C API<13>-Footnote-32241389
Ref: C API<13>-Footnote-42241432
Ref: C API<13>-Footnote-52241475
Ref: C API<13>-Footnote-62241518
Node: Python 3 8 0 alpha 32241561
Ref: whatsnew/changelog python-3-8-0-alpha-32241703
Ref: ff12241703
Node: Security<19>2242064
Ref: whatsnew/changelog id1882242163
Ref: ff22242163
Ref: Security<19>-Footnote-12242726
Ref: Security<19>-Footnote-22242769
Node: Core and Builtins<26>2242812
Ref: whatsnew/changelog id1892242931
Ref: ff42242931
Ref: Core and Builtins<26>-Footnote-12246512
Ref: Core and Builtins<26>-Footnote-22246555
Ref: Core and Builtins<26>-Footnote-32246598
Ref: Core and Builtins<26>-Footnote-42246641
Ref: Core and Builtins<26>-Footnote-52246684
Ref: Core and Builtins<26>-Footnote-62246727
Ref: Core and Builtins<26>-Footnote-72246770
Ref: Core and Builtins<26>-Footnote-82246813
Ref: Core and Builtins<26>-Footnote-92246856
Ref: Core and Builtins<26>-Footnote-102246899
Ref: Core and Builtins<26>-Footnote-112246943
Ref: Core and Builtins<26>-Footnote-122246987
Ref: Core and Builtins<26>-Footnote-132247031
Ref: Core and Builtins<26>-Footnote-142247075
Ref: Core and Builtins<26>-Footnote-152247119
Ref: Core and Builtins<26>-Footnote-162247163
Ref: Core and Builtins<26>-Footnote-172247207
Ref: Core and Builtins<26>-Footnote-182247251
Ref: Core and Builtins<26>-Footnote-192247295
Ref: Core and Builtins<26>-Footnote-202247339
Ref: Core and Builtins<26>-Footnote-212247383
Ref: Core and Builtins<26>-Footnote-222247427
Node: Library<26>2247471
Ref: whatsnew/changelog id1902247595
Ref: ff62247595
Ref: Library<26>-Footnote-12253222
Ref: Library<26>-Footnote-22253265
Ref: Library<26>-Footnote-32253308
Ref: Library<26>-Footnote-42253351
Ref: Library<26>-Footnote-52253394
Ref: Library<26>-Footnote-62253437
Ref: Library<26>-Footnote-72253480
Ref: Library<26>-Footnote-82253523
Ref: Library<26>-Footnote-92253566
Ref: Library<26>-Footnote-102253609
Ref: Library<26>-Footnote-112253653
Ref: Library<26>-Footnote-122253697
Ref: Library<26>-Footnote-132253741
Ref: Library<26>-Footnote-142253785
Ref: Library<26>-Footnote-152253829
Ref: Library<26>-Footnote-162253873
Ref: Library<26>-Footnote-172253917
Ref: Library<26>-Footnote-182253961
Ref: Library<26>-Footnote-192254005
Ref: Library<26>-Footnote-202254049
Ref: Library<26>-Footnote-212254093
Ref: Library<26>-Footnote-222254137
Ref: Library<26>-Footnote-232254181
Ref: Library<26>-Footnote-242254225
Ref: Library<26>-Footnote-252254269
Ref: Library<26>-Footnote-262254313
Ref: Library<26>-Footnote-272254357
Ref: Library<26>-Footnote-282254401
Ref: Library<26>-Footnote-292254445
Ref: Library<26>-Footnote-302254489
Ref: Library<26>-Footnote-312254533
Ref: Library<26>-Footnote-322254577
Ref: Library<26>-Footnote-332254621
Ref: Library<26>-Footnote-342254665
Ref: Library<26>-Footnote-352254709
Ref: Library<26>-Footnote-362254753
Ref: Library<26>-Footnote-372254797
Node: Documentation<22>2254841
Ref: whatsnew/changelog id1912254953
Ref: ff82254953
Ref: Documentation<22>-Footnote-12255524
Ref: Documentation<22>-Footnote-22255567
Ref: Documentation<22>-Footnote-32255610
Node: Tests<18>2255653
Ref: whatsnew/changelog id1922255763
Ref: ff92255763
Ref: Tests<18>-Footnote-12256275
Ref: Tests<18>-Footnote-22256318
Ref: Tests<18>-Footnote-32256361
Node: Build<16>2256404
Ref: whatsnew/changelog id1932256508
Ref: ffa2256508
Ref: Build<16>-Footnote-12257028
Ref: Build<16>-Footnote-22257071
Ref: Build<16>-Footnote-32257114
Ref: Build<16>-Footnote-42257157
Node: Windows<19>2257200
Ref: whatsnew/changelog id1942257303
Ref: ffb2257303
Ref: Windows<19>-Footnote-12257754
Ref: Windows<19>-Footnote-22257797
Ref: Windows<19>-Footnote-32257840
Node: IDLE<25>2257883
Ref: whatsnew/changelog id1952257992
Ref: ffc2257992
Ref: IDLE<25>-Footnote-12259101
Ref: IDLE<25>-Footnote-22259144
Ref: IDLE<25>-Footnote-32259187
Ref: IDLE<25>-Footnote-42259230
Ref: IDLE<25>-Footnote-52259273
Ref: IDLE<25>-Footnote-62259316
Ref: IDLE<25>-Footnote-72259359
Ref: IDLE<25>-Footnote-82259402
Ref: IDLE<25>-Footnote-92259445
Node: Tools/Demos<11>2259488
Ref: whatsnew/changelog id1962259595
Ref: ffd2259595
Ref: Tools/Demos<11>-Footnote-12259808
Ref: Tools/Demos<11>-Footnote-22259851
Node: C API<14>2259894
Ref: whatsnew/changelog id1972259984
Ref: ffe2259984
Ref: C API<14>-Footnote-12260376
Ref: C API<14>-Footnote-22260419
Node: Python 3 8 0 alpha 22260462
Ref: whatsnew/changelog python-3-8-0-alpha-22260604
Ref: fff2260604
Node: Core and Builtins<27>2260867
Ref: whatsnew/changelog id1982260965
Ref: 10002260965
Ref: Core and Builtins<27>-Footnote-12264110
Ref: Core and Builtins<27>-Footnote-22264153
Ref: Core and Builtins<27>-Footnote-32264196
Ref: Core and Builtins<27>-Footnote-42264239
Ref: Core and Builtins<27>-Footnote-52264282
Ref: Core and Builtins<27>-Footnote-62264327
Ref: Core and Builtins<27>-Footnote-72264370
Ref: Core and Builtins<27>-Footnote-82264413
Ref: Core and Builtins<27>-Footnote-92264456
Ref: Core and Builtins<27>-Footnote-102264499
Ref: Core and Builtins<27>-Footnote-112264543
Ref: Core and Builtins<27>-Footnote-122264587
Ref: Core and Builtins<27>-Footnote-132264631
Ref: Core and Builtins<27>-Footnote-142264675
Ref: Core and Builtins<27>-Footnote-152264719
Ref: Core and Builtins<27>-Footnote-162264763
Ref: Core and Builtins<27>-Footnote-172264807
Node: Library<27>2264851
Ref: whatsnew/changelog id1992264975
Ref: 10022264975
Ref: Library<27>-Footnote-12268688
Ref: Library<27>-Footnote-22268731
Ref: Library<27>-Footnote-32268774
Ref: Library<27>-Footnote-42268817
Ref: Library<27>-Footnote-52268860
Ref: Library<27>-Footnote-62268903
Ref: Library<27>-Footnote-72268946
Ref: Library<27>-Footnote-82268989
Ref: Library<27>-Footnote-92269032
Ref: Library<27>-Footnote-102269075
Ref: Library<27>-Footnote-112269119
Ref: Library<27>-Footnote-122269163
Ref: Library<27>-Footnote-132269207
Ref: Library<27>-Footnote-142269251
Ref: Library<27>-Footnote-152269295
Ref: Library<27>-Footnote-162269339
Ref: Library<27>-Footnote-172269383
Node: Documentation<23>2269427
Ref: whatsnew/changelog id2002269539
Ref: 10062269539
Ref: Documentation<23>-Footnote-12269917
Ref: Documentation<23>-Footnote-22269960
Ref: Documentation<23>-Footnote-32270003
Node: Tests<19>2270046
Ref: whatsnew/changelog id2012270158
Ref: 10072270158
Ref: Tests<19>-Footnote-12271534
Ref: Tests<19>-Footnote-22271577
Ref: Tests<19>-Footnote-32271620
Ref: Tests<19>-Footnote-42271663
Ref: Tests<19>-Footnote-52271706
Ref: Tests<19>-Footnote-62271749
Ref: Tests<19>-Footnote-72271792
Ref: Tests<19>-Footnote-82271835
Node: Windows<20>2271878
Ref: whatsnew/changelog id2022271981
Ref: 10092271981
Ref: Windows<20>-Footnote-12272578
Ref: Windows<20>-Footnote-22272621
Ref: Windows<20>-Footnote-32272664
Ref: Windows<20>-Footnote-42272707
Ref: Windows<20>-Footnote-52272750
Node: IDLE<26>2272793
Ref: whatsnew/changelog id2032272878
Ref: 100a2272878
Ref: IDLE<26>-Footnote-12273184
Ref: IDLE<26>-Footnote-22273227
Ref: IDLE<26>-Footnote-32273270
Node: Python 3 8 0 alpha 12273313
Ref: whatsnew/changelog python-3-8-0-alpha-12273453
Ref: 100b2273453
Node: Security<20>2273834
Ref: whatsnew/changelog id2042273933
Ref: 100c2273933
Ref: Security<20>-Footnote-12276253
Ref: Security<20>-Footnote-22276296
Ref: Security<20>-Footnote-32276339
Ref: Security<20>-Footnote-42276382
Ref: Security<20>-Footnote-52276425
Ref: Security<20>-Footnote-62276468
Ref: Security<20>-Footnote-72276511
Ref: Security<20>-Footnote-82276554
Ref: Security<20>-Footnote-92276597
Ref: Security<20>-Footnote-102276640
Ref: Security<20>-Footnote-112276684
Ref: Security<20>-Footnote-122276728
Node: Core and Builtins<28>2276772
Ref: whatsnew/changelog id2052276891
Ref: 100f2276891
Ref: Core and Builtins<28>-Footnote-12303016
Ref: Core and Builtins<28>-Footnote-22303059
Ref: Core and Builtins<28>-Footnote-32303102
Ref: Core and Builtins<28>-Footnote-42303145
Ref: Core and Builtins<28>-Footnote-52303188
Ref: Core and Builtins<28>-Footnote-62303231
Ref: Core and Builtins<28>-Footnote-72303274
Ref: Core and Builtins<28>-Footnote-82303317
Ref: Core and Builtins<28>-Footnote-92303360
Ref: Core and Builtins<28>-Footnote-102303403
Ref: Core and Builtins<28>-Footnote-112303447
Ref: Core and Builtins<28>-Footnote-122303491
Ref: Core and Builtins<28>-Footnote-132303535
Ref: Core and Builtins<28>-Footnote-142303579
Ref: Core and Builtins<28>-Footnote-152303623
Ref: Core and Builtins<28>-Footnote-162303667
Ref: Core and Builtins<28>-Footnote-172303711
Ref: Core and Builtins<28>-Footnote-182303755
Ref: Core and Builtins<28>-Footnote-192303799
Ref: Core and Builtins<28>-Footnote-202303843
Ref: Core and Builtins<28>-Footnote-212303887
Ref: Core and Builtins<28>-Footnote-222303931
Ref: Core and Builtins<28>-Footnote-232303975
Ref: Core and Builtins<28>-Footnote-242304019
Ref: Core and Builtins<28>-Footnote-252304063
Ref: Core and Builtins<28>-Footnote-262304113
Ref: Core and Builtins<28>-Footnote-272304157
Ref: Core and Builtins<28>-Footnote-282304201
Ref: Core and Builtins<28>-Footnote-292304245
Ref: Core and Builtins<28>-Footnote-302304289
Ref: Core and Builtins<28>-Footnote-312304333
Ref: Core and Builtins<28>-Footnote-322304377
Ref: Core and Builtins<28>-Footnote-332304421
Ref: Core and Builtins<28>-Footnote-342304465
Ref: Core and Builtins<28>-Footnote-352304509
Ref: Core and Builtins<28>-Footnote-362304553
Ref: Core and Builtins<28>-Footnote-372304597
Ref: Core and Builtins<28>-Footnote-382304641
Ref: Core and Builtins<28>-Footnote-392304685
Ref: Core and Builtins<28>-Footnote-402304729
Ref: Core and Builtins<28>-Footnote-412304773
Ref: Core and Builtins<28>-Footnote-422304817
Ref: Core and Builtins<28>-Footnote-432304861
Ref: Core and Builtins<28>-Footnote-442304905
Ref: Core and Builtins<28>-Footnote-452304949
Ref: Core and Builtins<28>-Footnote-462304993
Ref: Core and Builtins<28>-Footnote-472305037
Ref: Core and Builtins<28>-Footnote-482305081
Ref: Core and Builtins<28>-Footnote-492305125
Ref: Core and Builtins<28>-Footnote-502305169
Ref: Core and Builtins<28>-Footnote-512305213
Ref: Core and Builtins<28>-Footnote-522305257
Ref: Core and Builtins<28>-Footnote-532305301
Ref: Core and Builtins<28>-Footnote-542305345
Ref: Core and Builtins<28>-Footnote-552305389
Ref: Core and Builtins<28>-Footnote-562305433
Ref: Core and Builtins<28>-Footnote-572305477
Ref: Core and Builtins<28>-Footnote-582305521
Ref: Core and Builtins<28>-Footnote-592305565
Ref: Core and Builtins<28>-Footnote-602305608
Ref: Core and Builtins<28>-Footnote-612305652
Ref: Core and Builtins<28>-Footnote-622305696
Ref: Core and Builtins<28>-Footnote-632305740
Ref: Core and Builtins<28>-Footnote-642305784
Ref: Core and Builtins<28>-Footnote-652305828
Ref: Core and Builtins<28>-Footnote-662305872
Ref: Core and Builtins<28>-Footnote-672305916
Ref: Core and Builtins<28>-Footnote-682305960
Ref: Core and Builtins<28>-Footnote-692306004
Ref: Core and Builtins<28>-Footnote-702306048
Ref: Core and Builtins<28>-Footnote-712306092
Ref: Core and Builtins<28>-Footnote-722306136
Ref: Core and Builtins<28>-Footnote-732306180
Ref: Core and Builtins<28>-Footnote-742306224
Ref: Core and Builtins<28>-Footnote-752306268
Ref: Core and Builtins<28>-Footnote-762306312
Ref: Core and Builtins<28>-Footnote-772306356
Ref: Core and Builtins<28>-Footnote-782306400
Ref: Core and Builtins<28>-Footnote-792306444
Ref: Core and Builtins<28>-Footnote-802306488
Ref: Core and Builtins<28>-Footnote-812306532
Ref: Core and Builtins<28>-Footnote-822306576
Ref: Core and Builtins<28>-Footnote-832306620
Ref: Core and Builtins<28>-Footnote-842306664
Ref: Core and Builtins<28>-Footnote-852306708
Ref: Core and Builtins<28>-Footnote-862306752
Ref: Core and Builtins<28>-Footnote-872306796
Ref: Core and Builtins<28>-Footnote-882306840
Ref: Core and Builtins<28>-Footnote-892306884
Ref: Core and Builtins<28>-Footnote-902306928
Ref: Core and Builtins<28>-Footnote-912306972
Ref: Core and Builtins<28>-Footnote-922307016
Ref: Core and Builtins<28>-Footnote-932307060
Ref: Core and Builtins<28>-Footnote-942307104
Ref: Core and Builtins<28>-Footnote-952307148
Ref: Core and Builtins<28>-Footnote-962307192
Ref: Core and Builtins<28>-Footnote-972307238
Ref: Core and Builtins<28>-Footnote-982307282
Ref: Core and Builtins<28>-Footnote-992307326
Ref: Core and Builtins<28>-Footnote-1002307370
Ref: Core and Builtins<28>-Footnote-1012307415
Ref: Core and Builtins<28>-Footnote-1022307460
Ref: Core and Builtins<28>-Footnote-1032307505
Ref: Core and Builtins<28>-Footnote-1042307550
Ref: Core and Builtins<28>-Footnote-1052307595
Ref: Core and Builtins<28>-Footnote-1062307640
Ref: Core and Builtins<28>-Footnote-1072307685
Ref: Core and Builtins<28>-Footnote-1082307730
Ref: Core and Builtins<28>-Footnote-1092307775
Ref: Core and Builtins<28>-Footnote-1102307820
Ref: Core and Builtins<28>-Footnote-1112307865
Ref: Core and Builtins<28>-Footnote-1122307910
Ref: Core and Builtins<28>-Footnote-1132307955
Ref: Core and Builtins<28>-Footnote-1142308000
Ref: Core and Builtins<28>-Footnote-1152308045
Ref: Core and Builtins<28>-Footnote-1162308090
Ref: Core and Builtins<28>-Footnote-1172308135
Ref: Core and Builtins<28>-Footnote-1182308180
Ref: Core and Builtins<28>-Footnote-1192308225
Ref: Core and Builtins<28>-Footnote-1202308270
Ref: Core and Builtins<28>-Footnote-1212308315
Ref: Core and Builtins<28>-Footnote-1222308360
Ref: Core and Builtins<28>-Footnote-1232308405
Ref: Core and Builtins<28>-Footnote-1242308450
Ref: Core and Builtins<28>-Footnote-1252308495
Ref: Core and Builtins<28>-Footnote-1262308540
Ref: Core and Builtins<28>-Footnote-1272308585
Ref: Core and Builtins<28>-Footnote-1282308630
Ref: Core and Builtins<28>-Footnote-1292308675
Ref: Core and Builtins<28>-Footnote-1302308720
Ref: Core and Builtins<28>-Footnote-1312308765
Ref: Core and Builtins<28>-Footnote-1322308810
Ref: Core and Builtins<28>-Footnote-1332308855
Ref: Core and Builtins<28>-Footnote-1342308900
Ref: Core and Builtins<28>-Footnote-1352308945
Ref: Core and Builtins<28>-Footnote-1362308990
Ref: Core and Builtins<28>-Footnote-1372309035
Ref: Core and Builtins<28>-Footnote-1382309080
Ref: Core and Builtins<28>-Footnote-1392309125
Ref: Core and Builtins<28>-Footnote-1402309170
Ref: Core and Builtins<28>-Footnote-1412309215
Ref: Core and Builtins<28>-Footnote-1422309260
Ref: Core and Builtins<28>-Footnote-1432309305
Ref: Core and Builtins<28>-Footnote-1442309350
Ref: Core and Builtins<28>-Footnote-1452309395
Ref: Core and Builtins<28>-Footnote-1462309440
Ref: Core and Builtins<28>-Footnote-1472309485
Ref: Core and Builtins<28>-Footnote-1482309530
Ref: Core and Builtins<28>-Footnote-1492309575
Ref: Core and Builtins<28>-Footnote-1502309620
Ref: Core and Builtins<28>-Footnote-1512309665
Ref: Core and Builtins<28>-Footnote-1522309710
Ref: Core and Builtins<28>-Footnote-1532309755
Ref: Core and Builtins<28>-Footnote-1542309800
Ref: Core and Builtins<28>-Footnote-1552309845
Ref: Core and Builtins<28>-Footnote-1562309890
Ref: Core and Builtins<28>-Footnote-1572309935
Ref: Core and Builtins<28>-Footnote-1582309980
Ref: Core and Builtins<28>-Footnote-1592310025
Ref: Core and Builtins<28>-Footnote-1602310070
Ref: Core and Builtins<28>-Footnote-1612310115
Ref: Core and Builtins<28>-Footnote-1622310160
Node: Library<28>2310205
Ref: whatsnew/changelog id2062310329
Ref: 10192310329
Ref: Library<28>-Footnote-12381499
Ref: Library<28>-Footnote-22381542
Ref: Library<28>-Footnote-32381585
Ref: Library<28>-Footnote-42381628
Ref: Library<28>-Footnote-52381671
Ref: Library<28>-Footnote-62381714
Ref: Library<28>-Footnote-72381757
Ref: Library<28>-Footnote-82381800
Ref: Library<28>-Footnote-92381843
Ref: Library<28>-Footnote-102381886
Ref: Library<28>-Footnote-112381930
Ref: Library<28>-Footnote-122381974
Ref: Library<28>-Footnote-132382018
Ref: Library<28>-Footnote-142382062
Ref: Library<28>-Footnote-152382106
Ref: Library<28>-Footnote-162382150
Ref: Library<28>-Footnote-172382194
Ref: Library<28>-Footnote-182382238
Ref: Library<28>-Footnote-192382282
Ref: Library<28>-Footnote-202382326
Ref: Library<28>-Footnote-212382370
Ref: Library<28>-Footnote-222382414
Ref: Library<28>-Footnote-232382458
Ref: Library<28>-Footnote-242382502
Ref: Library<28>-Footnote-252382546
Ref: Library<28>-Footnote-262382590
Ref: Library<28>-Footnote-272382634
Ref: Library<28>-Footnote-282382678
Ref: Library<28>-Footnote-292382722
Ref: Library<28>-Footnote-302382766
Ref: Library<28>-Footnote-312382810
Ref: Library<28>-Footnote-322382854
Ref: Library<28>-Footnote-332382898
Ref: Library<28>-Footnote-342382942
Ref: Library<28>-Footnote-352382986
Ref: Library<28>-Footnote-362383030
Ref: Library<28>-Footnote-372383074
Ref: Library<28>-Footnote-382383118
Ref: Library<28>-Footnote-392383162
Ref: Library<28>-Footnote-402383206
Ref: Library<28>-Footnote-412383250
Ref: Library<28>-Footnote-422383294
Ref: Library<28>-Footnote-432383338
Ref: Library<28>-Footnote-442383382
Ref: Library<28>-Footnote-452383426
Ref: Library<28>-Footnote-462383470
Ref: Library<28>-Footnote-472383514
Ref: Library<28>-Footnote-482383558
Ref: Library<28>-Footnote-492383602
Ref: Library<28>-Footnote-502383646
Ref: Library<28>-Footnote-512383690
Ref: Library<28>-Footnote-522383734
Ref: Library<28>-Footnote-532383778
Ref: Library<28>-Footnote-542383822
Ref: Library<28>-Footnote-552383866
Ref: Library<28>-Footnote-562383910
Ref: Library<28>-Footnote-572383954
Ref: Library<28>-Footnote-582383998
Ref: Library<28>-Footnote-592384042
Ref: Library<28>-Footnote-602384086
Ref: Library<28>-Footnote-612384130
Ref: Library<28>-Footnote-622384174
Ref: Library<28>-Footnote-632384218
Ref: Library<28>-Footnote-642384262
Ref: Library<28>-Footnote-652384306
Ref: Library<28>-Footnote-662384350
Ref: Library<28>-Footnote-672384394
Ref: Library<28>-Footnote-682384438
Ref: Library<28>-Footnote-692384482
Ref: Library<28>-Footnote-702384526
Ref: Library<28>-Footnote-712384570
Ref: Library<28>-Footnote-722384614
Ref: Library<28>-Footnote-732384658
Ref: Library<28>-Footnote-742384702
Ref: Library<28>-Footnote-752384746
Ref: Library<28>-Footnote-762384790
Ref: Library<28>-Footnote-772384834
Ref: Library<28>-Footnote-782384878
Ref: Library<28>-Footnote-792384922
Ref: Library<28>-Footnote-802384966
Ref: Library<28>-Footnote-812385010
Ref: Library<28>-Footnote-822385054
Ref: Library<28>-Footnote-832385098
Ref: Library<28>-Footnote-842385142
Ref: Library<28>-Footnote-852385186
Ref: Library<28>-Footnote-862385230
Ref: Library<28>-Footnote-872385274
Ref: Library<28>-Footnote-882385318
Ref: Library<28>-Footnote-892385362
Ref: Library<28>-Footnote-902385406
Ref: Library<28>-Footnote-912385450
Ref: Library<28>-Footnote-922385494
Ref: Library<28>-Footnote-932385538
Ref: Library<28>-Footnote-942385588
Ref: Library<28>-Footnote-952385632
Ref: Library<28>-Footnote-962385676
Ref: Library<28>-Footnote-972385720
Ref: Library<28>-Footnote-982385764
Ref: Library<28>-Footnote-992385808
Ref: Library<28>-Footnote-1002385852
Ref: Library<28>-Footnote-1012385897
Ref: Library<28>-Footnote-1022385942
Ref: Library<28>-Footnote-1032385987
Ref: Library<28>-Footnote-1042386032
Ref: Library<28>-Footnote-1052386077
Ref: Library<28>-Footnote-1062386122
Ref: Library<28>-Footnote-1072386167
Ref: Library<28>-Footnote-1082386212
Ref: Library<28>-Footnote-1092386257
Ref: Library<28>-Footnote-1102386302
Ref: Library<28>-Footnote-1112386347
Ref: Library<28>-Footnote-1122386392
Ref: Library<28>-Footnote-1132386437
Ref: Library<28>-Footnote-1142386482
Ref: Library<28>-Footnote-1152386527
Ref: Library<28>-Footnote-1162386572
Ref: Library<28>-Footnote-1172386617
Ref: Library<28>-Footnote-1182386662
Ref: Library<28>-Footnote-1192386707
Ref: Library<28>-Footnote-1202386752
Ref: Library<28>-Footnote-1212386797
Ref: Library<28>-Footnote-1222386842
Ref: Library<28>-Footnote-1232386887
Ref: Library<28>-Footnote-1242386932
Ref: Library<28>-Footnote-1252386977
Ref: Library<28>-Footnote-1262387021
Ref: Library<28>-Footnote-1272387066
Ref: Library<28>-Footnote-1282387111
Ref: Library<28>-Footnote-1292387156
Ref: Library<28>-Footnote-1302387201
Ref: Library<28>-Footnote-1312387246
Ref: Library<28>-Footnote-1322387291
Ref: Library<28>-Footnote-1332387336
Ref: Library<28>-Footnote-1342387381
Ref: Library<28>-Footnote-1352387426
Ref: Library<28>-Footnote-1362387471
Ref: Library<28>-Footnote-1372387515
Ref: Library<28>-Footnote-1382387560
Ref: Library<28>-Footnote-1392387605
Ref: Library<28>-Footnote-1402387650
Ref: Library<28>-Footnote-1412387695
Ref: Library<28>-Footnote-1422387740
Ref: Library<28>-Footnote-1432387785
Ref: Library<28>-Footnote-1442387830
Ref: Library<28>-Footnote-1452387875
Ref: Library<28>-Footnote-1462387920
Ref: Library<28>-Footnote-1472387965
Ref: Library<28>-Footnote-1482388010
Ref: Library<28>-Footnote-1492388055
Ref: Library<28>-Footnote-1502388100
Ref: Library<28>-Footnote-1512388145
Ref: Library<28>-Footnote-1522388190
Ref: Library<28>-Footnote-1532388235
Ref: Library<28>-Footnote-1542388280
Ref: Library<28>-Footnote-1552388324
Ref: Library<28>-Footnote-1562388369
Ref: Library<28>-Footnote-1572388414
Ref: Library<28>-Footnote-1582388459
Ref: Library<28>-Footnote-1592388504
Ref: Library<28>-Footnote-1602388549
Ref: Library<28>-Footnote-1612388594
Ref: Library<28>-Footnote-1622388639
Ref: Library<28>-Footnote-1632388684
Ref: Library<28>-Footnote-1642388729
Ref: Library<28>-Footnote-1652388773
Ref: Library<28>-Footnote-1662388818
Ref: Library<28>-Footnote-1672388863
Ref: Library<28>-Footnote-1682388908
Ref: Library<28>-Footnote-1692388953
Ref: Library<28>-Footnote-1702388998
Ref: Library<28>-Footnote-1712389043
Ref: Library<28>-Footnote-1722389088
Ref: Library<28>-Footnote-1732389133
Ref: Library<28>-Footnote-1742389177
Ref: Library<28>-Footnote-1752389222
Ref: Library<28>-Footnote-1762389267
Ref: Library<28>-Footnote-1772389312
Ref: Library<28>-Footnote-1782389357
Ref: Library<28>-Footnote-1792389402
Ref: Library<28>-Footnote-1802389446
Ref: Library<28>-Footnote-1812389491
Ref: Library<28>-Footnote-1822389536
Ref: Library<28>-Footnote-1832389581
Ref: Library<28>-Footnote-1842389626
Ref: Library<28>-Footnote-1852389671
Ref: Library<28>-Footnote-1862389716
Ref: Library<28>-Footnote-1872389761
Ref: Library<28>-Footnote-1882389806
Ref: Library<28>-Footnote-1892389851
Ref: Library<28>-Footnote-1902389896
Ref: Library<28>-Footnote-1912389941
Ref: Library<28>-Footnote-1922389986
Ref: Library<28>-Footnote-1932390031
Ref: Library<28>-Footnote-1942390076
Ref: Library<28>-Footnote-1952390121
Ref: Library<28>-Footnote-1962390166
Ref: Library<28>-Footnote-1972390211
Ref: Library<28>-Footnote-1982390256
Ref: Library<28>-Footnote-1992390301
Ref: Library<28>-Footnote-2002390346
Ref: Library<28>-Footnote-2012390391
Ref: Library<28>-Footnote-2022390437
Ref: Library<28>-Footnote-2032390482
Ref: Library<28>-Footnote-2042390527
Ref: Library<28>-Footnote-2052390572
Ref: Library<28>-Footnote-2062390617
Ref: Library<28>-Footnote-2072390662
Ref: Library<28>-Footnote-2082390707
Ref: Library<28>-Footnote-2092390752
Ref: Library<28>-Footnote-2102390797
Ref: Library<28>-Footnote-2112390842
Ref: Library<28>-Footnote-2122390887
Ref: Library<28>-Footnote-2132390938
Ref: Library<28>-Footnote-2142390983
Ref: Library<28>-Footnote-2152391028
Ref: Library<28>-Footnote-2162391073
Ref: Library<28>-Footnote-2172391118
Ref: Library<28>-Footnote-2182391163
Ref: Library<28>-Footnote-2192391208
Ref: Library<28>-Footnote-2202391253
Ref: Library<28>-Footnote-2212391298
Ref: Library<28>-Footnote-2222391343
Ref: Library<28>-Footnote-2232391388
Ref: Library<28>-Footnote-2242391433
Ref: Library<28>-Footnote-2252391478
Ref: Library<28>-Footnote-2262391523
Ref: Library<28>-Footnote-2272391568
Ref: Library<28>-Footnote-2282391613
Ref: Library<28>-Footnote-2292391658
Ref: Library<28>-Footnote-2302391703
Ref: Library<28>-Footnote-2312391748
Ref: Library<28>-Footnote-2322391793
Ref: Library<28>-Footnote-2332391838
Ref: Library<28>-Footnote-2342391883
Ref: Library<28>-Footnote-2352391928
Ref: Library<28>-Footnote-2362391973
Ref: Library<28>-Footnote-2372392018
Ref: Library<28>-Footnote-2382392063
Ref: Library<28>-Footnote-2392392108
Ref: Library<28>-Footnote-2402392153
Ref: Library<28>-Footnote-2412392198
Ref: Library<28>-Footnote-2422392243
Ref: Library<28>-Footnote-2432392288
Ref: Library<28>-Footnote-2442392333
Ref: Library<28>-Footnote-2452392378
Ref: Library<28>-Footnote-2462392423
Ref: Library<28>-Footnote-2472392468
Ref: Library<28>-Footnote-2482392513
Ref: Library<28>-Footnote-2492392558
Ref: Library<28>-Footnote-2502392603
Ref: Library<28>-Footnote-2512392648
Ref: Library<28>-Footnote-2522392693
Ref: Library<28>-Footnote-2532392738
Ref: Library<28>-Footnote-2542392783
Ref: Library<28>-Footnote-2552392828
Ref: Library<28>-Footnote-2562392873
Ref: Library<28>-Footnote-2572392918
Ref: Library<28>-Footnote-2582392963
Ref: Library<28>-Footnote-2592393008
Ref: Library<28>-Footnote-2602393052
Ref: Library<28>-Footnote-2612393097
Ref: Library<28>-Footnote-2622393142
Ref: Library<28>-Footnote-2632393187
Ref: Library<28>-Footnote-2642393232
Ref: Library<28>-Footnote-2652393277
Ref: Library<28>-Footnote-2662393322
Ref: Library<28>-Footnote-2672393367
Ref: Library<28>-Footnote-2682393412
Ref: Library<28>-Footnote-2692393457
Ref: Library<28>-Footnote-2702393502
Ref: Library<28>-Footnote-2712393547
Ref: Library<28>-Footnote-2722393592
Ref: Library<28>-Footnote-2732393637
Ref: Library<28>-Footnote-2742393682
Ref: Library<28>-Footnote-2752393727
Ref: Library<28>-Footnote-2762393772
Ref: Library<28>-Footnote-2772393817
Ref: Library<28>-Footnote-2782393862
Ref: Library<28>-Footnote-2792393907
Ref: Library<28>-Footnote-2802393952
Ref: Library<28>-Footnote-2812393997
Ref: Library<28>-Footnote-2822394042
Ref: Library<28>-Footnote-2832394087
Ref: Library<28>-Footnote-2842394132
Ref: Library<28>-Footnote-2852394177
Ref: Library<28>-Footnote-2862394222
Ref: Library<28>-Footnote-2872394267
Ref: Library<28>-Footnote-2882394312
Ref: Library<28>-Footnote-2892394357
Ref: Library<28>-Footnote-2902394402
Ref: Library<28>-Footnote-2912394447
Ref: Library<28>-Footnote-2922394492
Ref: Library<28>-Footnote-2932394537
Ref: Library<28>-Footnote-2942394582
Ref: Library<28>-Footnote-2952394627
Ref: Library<28>-Footnote-2962394672
Ref: Library<28>-Footnote-2972394717
Ref: Library<28>-Footnote-2982394762
Ref: Library<28>-Footnote-2992394807
Ref: Library<28>-Footnote-3002394852
Ref: Library<28>-Footnote-3012394897
Ref: Library<28>-Footnote-3022394942
Ref: Library<28>-Footnote-3032394987
Ref: Library<28>-Footnote-3042395032
Ref: Library<28>-Footnote-3052395077
Ref: Library<28>-Footnote-3062395122
Ref: Library<28>-Footnote-3072395167
Ref: Library<28>-Footnote-3082395212
Ref: Library<28>-Footnote-3092395257
Ref: Library<28>-Footnote-3102395302
Ref: Library<28>-Footnote-3112395347
Ref: Library<28>-Footnote-3122395392
Ref: Library<28>-Footnote-3132395437
Ref: Library<28>-Footnote-3142395482
Ref: Library<28>-Footnote-3152395527
Ref: Library<28>-Footnote-3162395572
Ref: Library<28>-Footnote-3172395617
Ref: Library<28>-Footnote-3182395662
Ref: Library<28>-Footnote-3192395707
Ref: Library<28>-Footnote-3202395752
Ref: Library<28>-Footnote-3212395797
Ref: Library<28>-Footnote-3222395842
Ref: Library<28>-Footnote-3232395887
Ref: Library<28>-Footnote-3242395932
Ref: Library<28>-Footnote-3252395977
Ref: Library<28>-Footnote-3262396022
Ref: Library<28>-Footnote-3272396067
Ref: Library<28>-Footnote-3282396113
Ref: Library<28>-Footnote-3292396158
Ref: Library<28>-Footnote-3302396203
Ref: Library<28>-Footnote-3312396248
Ref: Library<28>-Footnote-3322396293
Ref: Library<28>-Footnote-3332396338
Ref: Library<28>-Footnote-3342396383
Ref: Library<28>-Footnote-3352396428
Ref: Library<28>-Footnote-3362396473
Ref: Library<28>-Footnote-3372396518
Ref: Library<28>-Footnote-3382396563
Ref: Library<28>-Footnote-3392396608
Ref: Library<28>-Footnote-3402396653
Ref: Library<28>-Footnote-3412396698
Ref: Library<28>-Footnote-3422396743
Ref: Library<28>-Footnote-3432396788
Ref: Library<28>-Footnote-3442396833
Ref: Library<28>-Footnote-3452396884
Ref: Library<28>-Footnote-3462396929
Ref: Library<28>-Footnote-3472396974
Ref: Library<28>-Footnote-3482397019
Ref: Library<28>-Footnote-3492397070
Ref: Library<28>-Footnote-3502397115
Ref: Library<28>-Footnote-3512397160
Ref: Library<28>-Footnote-3522397205
Ref: Library<28>-Footnote-3532397250
Ref: Library<28>-Footnote-3542397295
Ref: Library<28>-Footnote-3552397340
Ref: Library<28>-Footnote-3562397385
Ref: Library<28>-Footnote-3572397430
Ref: Library<28>-Footnote-3582397475
Ref: Library<28>-Footnote-3592397520
Ref: Library<28>-Footnote-3602397565
Ref: Library<28>-Footnote-3612397610
Ref: Library<28>-Footnote-3622397655
Ref: Library<28>-Footnote-3632397700
Ref: Library<28>-Footnote-3642397745
Ref: Library<28>-Footnote-3652397790
Ref: Library<28>-Footnote-3662397835
Ref: Library<28>-Footnote-3672397880
Ref: Library<28>-Footnote-3682397925
Ref: Library<28>-Footnote-3692397970
Ref: Library<28>-Footnote-3702398015
Ref: Library<28>-Footnote-3712398060
Ref: Library<28>-Footnote-3722398105
Ref: Library<28>-Footnote-3732398150
Ref: Library<28>-Footnote-3742398195
Ref: Library<28>-Footnote-3752398240
Ref: Library<28>-Footnote-3762398285
Ref: Library<28>-Footnote-3772398330
Ref: Library<28>-Footnote-3782398375
Ref: Library<28>-Footnote-3792398420
Ref: Library<28>-Footnote-3802398465
Ref: Library<28>-Footnote-3812398510
Ref: Library<28>-Footnote-3822398555
Ref: Library<28>-Footnote-3832398600
Ref: Library<28>-Footnote-3842398645
Ref: Library<28>-Footnote-3852398690
Ref: Library<28>-Footnote-3862398735
Ref: Library<28>-Footnote-3872398780
Ref: Library<28>-Footnote-3882398825
Ref: Library<28>-Footnote-3892398870
Ref: Library<28>-Footnote-3902398915
Ref: Library<28>-Footnote-3912398960
Ref: Library<28>-Footnote-3922399005
Ref: Library<28>-Footnote-3932399050
Ref: Library<28>-Footnote-3942399095
Ref: Library<28>-Footnote-3952399140
Ref: Library<28>-Footnote-3962399185
Ref: Library<28>-Footnote-3972399230
Ref: Library<28>-Footnote-3982399275
Ref: Library<28>-Footnote-3992399320
Ref: Library<28>-Footnote-4002399365
Ref: Library<28>-Footnote-4012399410
Ref: Library<28>-Footnote-4022399455
Ref: Library<28>-Footnote-4032399500
Ref: Library<28>-Footnote-4042399545
Ref: Library<28>-Footnote-4052399590
Ref: Library<28>-Footnote-4062399635
Ref: Library<28>-Footnote-4072399680
Ref: Library<28>-Footnote-4082399725
Ref: Library<28>-Footnote-4092399770
Ref: Library<28>-Footnote-4102399815
Ref: Library<28>-Footnote-4112399860
Ref: Library<28>-Footnote-4122399905
Ref: Library<28>-Footnote-4132399950
Ref: Library<28>-Footnote-4142399995
Ref: Library<28>-Footnote-4152400040
Ref: Library<28>-Footnote-4162400085
Ref: Library<28>-Footnote-4172400130
Ref: Library<28>-Footnote-4182400175
Ref: Library<28>-Footnote-4192400220
Ref: Library<28>-Footnote-4202400265
Ref: Library<28>-Footnote-4212400310
Ref: Library<28>-Footnote-4222400354
Ref: Library<28>-Footnote-4232400399
Ref: Library<28>-Footnote-4242400444
Ref: Library<28>-Footnote-4252400489
Ref: Library<28>-Footnote-4262400534
Ref: Library<28>-Footnote-4272400579
Ref: Library<28>-Footnote-4282400624
Ref: Library<28>-Footnote-4292400669
Ref: Library<28>-Footnote-4302400714
Ref: Library<28>-Footnote-4312400759
Ref: Library<28>-Footnote-4322400804
Ref: Library<28>-Footnote-4332400849
Ref: Library<28>-Footnote-4342400894
Ref: Library<28>-Footnote-4352400939
Ref: Library<28>-Footnote-4362400984
Node: Documentation<24>2401029
Ref: whatsnew/changelog id2072401141
Ref: 10442401141
Ref: Documentation<24>-Footnote-12407851
Ref: Documentation<24>-Footnote-22407894
Ref: Documentation<24>-Footnote-32407937
Ref: Documentation<24>-Footnote-42407980
Ref: Documentation<24>-Footnote-52408023
Ref: Documentation<24>-Footnote-62408066
Ref: Documentation<24>-Footnote-72408109
Ref: Documentation<24>-Footnote-82408152
Ref: Documentation<24>-Footnote-92408195
Ref: Documentation<24>-Footnote-102408238
Ref: Documentation<24>-Footnote-112408282
Ref: Documentation<24>-Footnote-122408326
Ref: Documentation<24>-Footnote-132408370
Ref: Documentation<24>-Footnote-142408414
Ref: Documentation<24>-Footnote-152408458
Ref: Documentation<24>-Footnote-162408502
Ref: Documentation<24>-Footnote-172408546
Ref: Documentation<24>-Footnote-182408590
Ref: Documentation<24>-Footnote-192408634
Ref: Documentation<24>-Footnote-202408678
Ref: Documentation<24>-Footnote-212408722
Ref: Documentation<24>-Footnote-222408766
Ref: Documentation<24>-Footnote-232408810
Ref: Documentation<24>-Footnote-242408860
Ref: Documentation<24>-Footnote-252408904
Ref: Documentation<24>-Footnote-262408948
Ref: Documentation<24>-Footnote-272408992
Ref: Documentation<24>-Footnote-282409036
Ref: Documentation<24>-Footnote-292409080
Ref: Documentation<24>-Footnote-302409130
Ref: Documentation<24>-Footnote-312409174
Ref: Documentation<24>-Footnote-322409218
Ref: Documentation<24>-Footnote-332409262
Ref: Documentation<24>-Footnote-342409306
Ref: Documentation<24>-Footnote-352409350
Ref: Documentation<24>-Footnote-362409394
Ref: Documentation<24>-Footnote-372409438
Ref: Documentation<24>-Footnote-382409482
Ref: Documentation<24>-Footnote-392409526
Ref: Documentation<24>-Footnote-402409570
Ref: Documentation<24>-Footnote-412409614
Ref: Documentation<24>-Footnote-422409658
Ref: Documentation<24>-Footnote-432409702
Ref: Documentation<24>-Footnote-442409746
Ref: Documentation<24>-Footnote-452409790
Ref: Documentation<24>-Footnote-462409834
Ref: Documentation<24>-Footnote-472409878
Ref: Documentation<24>-Footnote-482409922
Ref: Documentation<24>-Footnote-492409966
Ref: Documentation<24>-Footnote-502410010
Ref: Documentation<24>-Footnote-512410053
Ref: Documentation<24>-Footnote-522410097
Ref: Documentation<24>-Footnote-532410141
Ref: Documentation<24>-Footnote-542410185
Ref: Documentation<24>-Footnote-552410229
Ref: Documentation<24>-Footnote-562410273
Ref: Documentation<24>-Footnote-572410316
Ref: Documentation<24>-Footnote-582410360
Ref: Documentation<24>-Footnote-592410404
Node: Tests<20>2410448
Ref: whatsnew/changelog id2082410558
Ref: 10472410558
Ref: Tests<20>-Footnote-12418156
Ref: Tests<20>-Footnote-22418199
Ref: Tests<20>-Footnote-32418242
Ref: Tests<20>-Footnote-42418285
Ref: Tests<20>-Footnote-52418328
Ref: Tests<20>-Footnote-62418371
Ref: Tests<20>-Footnote-72418414
Ref: Tests<20>-Footnote-82418457
Ref: Tests<20>-Footnote-92418500
Ref: Tests<20>-Footnote-102418543
Ref: Tests<20>-Footnote-112418587
Ref: Tests<20>-Footnote-122418631
Ref: Tests<20>-Footnote-132418675
Ref: Tests<20>-Footnote-142418719
Ref: Tests<20>-Footnote-152418763
Ref: Tests<20>-Footnote-162418807
Ref: Tests<20>-Footnote-172418851
Ref: Tests<20>-Footnote-182418895
Ref: Tests<20>-Footnote-192418939
Ref: Tests<20>-Footnote-202418983
Ref: Tests<20>-Footnote-212419027
Ref: Tests<20>-Footnote-222419071
Ref: Tests<20>-Footnote-232419115
Ref: Tests<20>-Footnote-242419159
Ref: Tests<20>-Footnote-252419203
Ref: Tests<20>-Footnote-262419247
Ref: Tests<20>-Footnote-272419291
Ref: Tests<20>-Footnote-282419335
Ref: Tests<20>-Footnote-292419379
Ref: Tests<20>-Footnote-302419423
Ref: Tests<20>-Footnote-312419467
Ref: Tests<20>-Footnote-322419511
Ref: Tests<20>-Footnote-332419555
Ref: Tests<20>-Footnote-342419599
Ref: Tests<20>-Footnote-352419643
Ref: Tests<20>-Footnote-362419687
Ref: Tests<20>-Footnote-372419731
Ref: Tests<20>-Footnote-382419775
Ref: Tests<20>-Footnote-392419819
Ref: Tests<20>-Footnote-402419863
Ref: Tests<20>-Footnote-412419907
Ref: Tests<20>-Footnote-422419951
Ref: Tests<20>-Footnote-432419995
Ref: Tests<20>-Footnote-442420039
Ref: Tests<20>-Footnote-452420083
Ref: Tests<20>-Footnote-462420127
Ref: Tests<20>-Footnote-472420171
Ref: Tests<20>-Footnote-482420215
Node: Build<17>2420259
Ref: whatsnew/changelog id2092420363
Ref: 10492420363
Ref: Build<17>-Footnote-12425476
Ref: Build<17>-Footnote-22425519
Ref: Build<17>-Footnote-32425562
Ref: Build<17>-Footnote-42425605
Ref: Build<17>-Footnote-52425648
Ref: Build<17>-Footnote-62425691
Ref: Build<17>-Footnote-72425734
Ref: Build<17>-Footnote-82425777
Ref: Build<17>-Footnote-92425820
Ref: Build<17>-Footnote-102425863
Ref: Build<17>-Footnote-112425907
Ref: Build<17>-Footnote-122425951
Ref: Build<17>-Footnote-132425995
Ref: Build<17>-Footnote-142426039
Ref: Build<17>-Footnote-152426083
Ref: Build<17>-Footnote-162426127
Ref: Build<17>-Footnote-172426171
Ref: Build<17>-Footnote-182426215
Ref: Build<17>-Footnote-192426259
Ref: Build<17>-Footnote-202426303
Ref: Build<17>-Footnote-212426347
Ref: Build<17>-Footnote-222426391
Ref: Build<17>-Footnote-232426435
Ref: Build<17>-Footnote-242426478
Ref: Build<17>-Footnote-252426522
Ref: Build<17>-Footnote-262426566
Ref: Build<17>-Footnote-272426610
Ref: Build<17>-Footnote-282426654
Ref: Build<17>-Footnote-292426698
Ref: Build<17>-Footnote-302426742
Ref: Build<17>-Footnote-312426786
Ref: Build<17>-Footnote-322426830
Ref: Build<17>-Footnote-332426874
Ref: Build<17>-Footnote-342426918
Ref: Build<17>-Footnote-352426962
Ref: Build<17>-Footnote-362427006
Ref: Build<17>-Footnote-372427050
Node: Windows<21>2427094
Ref: whatsnew/changelog id2102427198
Ref: 104a2427198
Ref: Windows<21>-Footnote-12431621
Ref: Windows<21>-Footnote-22431664
Ref: Windows<21>-Footnote-32431707
Ref: Windows<21>-Footnote-42431750
Ref: Windows<21>-Footnote-52431793
Ref: Windows<21>-Footnote-62431836
Ref: Windows<21>-Footnote-72431879
Ref: Windows<21>-Footnote-82431922
Ref: Windows<21>-Footnote-92431965
Ref: Windows<21>-Footnote-102432008
Ref: Windows<21>-Footnote-112432052
Ref: Windows<21>-Footnote-122432096
Ref: Windows<21>-Footnote-132432140
Ref: Windows<21>-Footnote-142432184
Ref: Windows<21>-Footnote-152432228
Ref: Windows<21>-Footnote-162432272
Ref: Windows<21>-Footnote-172432316
Ref: Windows<21>-Footnote-182432360
Ref: Windows<21>-Footnote-192432404
Ref: Windows<21>-Footnote-202432448
Ref: Windows<21>-Footnote-212432492
Ref: Windows<21>-Footnote-222432536
Ref: Windows<21>-Footnote-232432580
Ref: Windows<21>-Footnote-242432624
Ref: Windows<21>-Footnote-252432668
Ref: Windows<21>-Footnote-262432712
Ref: Windows<21>-Footnote-272432756
Ref: Windows<21>-Footnote-282432800
Ref: Windows<21>-Footnote-292432844
Ref: Windows<21>-Footnote-302432888
Ref: Windows<21>-Footnote-312432932
Ref: Windows<21>-Footnote-322432976
Ref: Windows<21>-Footnote-332433020
Ref: Windows<21>-Footnote-342433064
Ref: Windows<21>-Footnote-352433108
Ref: Windows<21>-Footnote-362433152
Ref: Windows<21>-Footnote-372433196
Ref: Windows<21>-Footnote-382433240
Ref: Windows<21>-Footnote-392433284
Ref: Windows<21>-Footnote-402433328
Node: macOS<15>2433371
Ref: whatsnew/changelog id2112433474
Ref: 104b2433474
Ref: macOS<15>-Footnote-12435081
Ref: macOS<15>-Footnote-22435124
Ref: macOS<15>-Footnote-32435167
Ref: macOS<15>-Footnote-42435210
Ref: macOS<15>-Footnote-52435253
Ref: macOS<15>-Footnote-62435296
Ref: macOS<15>-Footnote-72435339
Ref: macOS<15>-Footnote-82435382
Ref: macOS<15>-Footnote-92435425
Ref: macOS<15>-Footnote-102435468
Node: IDLE<27>2435512
Ref: whatsnew/changelog id2122435619
Ref: 104c2435619
Ref: IDLE<27>-Footnote-12444031
Ref: IDLE<27>-Footnote-22444074
Ref: IDLE<27>-Footnote-32444117
Ref: IDLE<27>-Footnote-42444160
Ref: IDLE<27>-Footnote-52444203
Ref: IDLE<27>-Footnote-62444246
Ref: IDLE<27>-Footnote-72444289
Ref: IDLE<27>-Footnote-82444332
Ref: IDLE<27>-Footnote-92444375
Ref: IDLE<27>-Footnote-102444418
Ref: IDLE<27>-Footnote-112444462
Ref: IDLE<27>-Footnote-122444506
Ref: IDLE<27>-Footnote-132444550
Ref: IDLE<27>-Footnote-142444594
Ref: IDLE<27>-Footnote-152444638
Ref: IDLE<27>-Footnote-162444682
Ref: IDLE<27>-Footnote-172444726
Ref: IDLE<27>-Footnote-182444770
Ref: IDLE<27>-Footnote-192444814
Ref: IDLE<27>-Footnote-202444858
Ref: IDLE<27>-Footnote-212444902
Ref: IDLE<27>-Footnote-222444946
Ref: IDLE<27>-Footnote-232444990
Ref: IDLE<27>-Footnote-242445034
Ref: IDLE<27>-Footnote-252445078
Ref: IDLE<27>-Footnote-262445122
Ref: IDLE<27>-Footnote-272445166
Ref: IDLE<27>-Footnote-282445212
Ref: IDLE<27>-Footnote-292445256
Ref: IDLE<27>-Footnote-302445300
Ref: IDLE<27>-Footnote-312445344
Ref: IDLE<27>-Footnote-322445388
Ref: IDLE<27>-Footnote-332445432
Ref: IDLE<27>-Footnote-342445476
Ref: IDLE<27>-Footnote-352445520
Ref: IDLE<27>-Footnote-362445564
Ref: IDLE<27>-Footnote-372445608
Ref: IDLE<27>-Footnote-382445652
Ref: IDLE<27>-Footnote-392445696
Ref: IDLE<27>-Footnote-402445740
Ref: IDLE<27>-Footnote-412445784
Ref: IDLE<27>-Footnote-422445828
Ref: IDLE<27>-Footnote-432445872
Ref: IDLE<27>-Footnote-442445916
Ref: IDLE<27>-Footnote-452445960
Ref: IDLE<27>-Footnote-462446004
Ref: IDLE<27>-Footnote-472446048
Ref: IDLE<27>-Footnote-482446092
Ref: IDLE<27>-Footnote-492446136
Ref: IDLE<27>-Footnote-502446180
Ref: IDLE<27>-Footnote-512446224
Ref: IDLE<27>-Footnote-522446268
Ref: IDLE<27>-Footnote-532446312
Ref: IDLE<27>-Footnote-542446356
Ref: IDLE<27>-Footnote-552446400
Ref: IDLE<27>-Footnote-562446444
Ref: IDLE<27>-Footnote-572446488
Ref: IDLE<27>-Footnote-582446532
Ref: IDLE<27>-Footnote-592446576
Node: Tools/Demos<12>2446620
Ref: whatsnew/changelog id2132446727
Ref: 104d2446727
Ref: Tools/Demos<12>-Footnote-12448376
Ref: Tools/Demos<12>-Footnote-22448419
Ref: Tools/Demos<12>-Footnote-32448462
Ref: Tools/Demos<12>-Footnote-42448505
Ref: Tools/Demos<12>-Footnote-52448548
Ref: Tools/Demos<12>-Footnote-62448591
Ref: Tools/Demos<12>-Footnote-72448634
Ref: Tools/Demos<12>-Footnote-82448677
Ref: Tools/Demos<12>-Footnote-92448720
Ref: Tools/Demos<12>-Footnote-102448763
Ref: Tools/Demos<12>-Footnote-112448807
Ref: Tools/Demos<12>-Footnote-122448851
Node: C API<15>2448895
Ref: whatsnew/changelog id2142448985
Ref: 104e2448985
Ref: C API<15>-Footnote-12452389
Ref: C API<15>-Footnote-22452432
Ref: C API<15>-Footnote-32452475
Ref: C API<15>-Footnote-42452518
Ref: C API<15>-Footnote-52452561
Ref: C API<15>-Footnote-62452604
Ref: C API<15>-Footnote-72452647
Ref: C API<15>-Footnote-82452690
Ref: C API<15>-Footnote-92452733
Ref: C API<15>-Footnote-102452776
Ref: C API<15>-Footnote-112452820
Ref: C API<15>-Footnote-122452864
Ref: C API<15>-Footnote-132452908
Ref: C API<15>-Footnote-142452952
Ref: C API<15>-Footnote-152452996
Ref: C API<15>-Footnote-162453040
Ref: C API<15>-Footnote-172453084
Ref: C API<15>-Footnote-182453128
Ref: C API<15>-Footnote-192453172
Ref: C API<15>-Footnote-202453216
Ref: C API<15>-Footnote-212453260
Ref: C API<15>-Footnote-222453304
Node: Python 3 7 0 final2453348
Ref: whatsnew/changelog python-3-7-0-final2453500
Ref: 10582453500
Node: Library<29>2453637
Ref: whatsnew/changelog id2152453721
Ref: 10592453721
Ref: Library<29>-Footnote-12453891
Node: C API<16>2453934
Ref: whatsnew/changelog id2162454018
Ref: 105b2454018
Ref: C API<16>-Footnote-12454229
Node: Python 3 7 0 release candidate 12454272
Ref: whatsnew/changelog python-3-7-0-release-candidate-12454423
Ref: 105c2454423
Node: Core and Builtins<29>2454710
Ref: whatsnew/changelog id2172454820
Ref: 105d2454820
Ref: Core and Builtins<29>-Footnote-12455464
Ref: Core and Builtins<29>-Footnote-22455507
Ref: Core and Builtins<29>-Footnote-32455550
Ref: Core and Builtins<29>-Footnote-42455593
Node: Library<30>2455636
Ref: whatsnew/changelog id2182455772
Ref: 105e2455772
Ref: Library<30>-Footnote-12457470
Ref: Library<30>-Footnote-22457513
Ref: Library<30>-Footnote-32457556
Ref: Library<30>-Footnote-42457599
Ref: Library<30>-Footnote-52457642
Ref: Library<30>-Footnote-62457685
Ref: Library<30>-Footnote-72457728
Ref: Library<30>-Footnote-82457771
Ref: Library<30>-Footnote-92457814
Ref: Library<30>-Footnote-102457857
Ref: Library<30>-Footnote-112457901
Ref: Library<30>-Footnote-122457945
Ref: Library<30>-Footnote-132457989
Node: Documentation<25>2458033
Ref: whatsnew/changelog id2192458157
Ref: 105f2458157
Ref: Documentation<25>-Footnote-12458664
Ref: Documentation<25>-Footnote-22458707
Ref: Documentation<25>-Footnote-32458756
Ref: Documentation<25>-Footnote-42458799
Node: Build<18>2458842
Ref: whatsnew/changelog id2202458966
Ref: 10602458966
Ref: Build<18>-Footnote-12459228
Node: Windows<22>2459270
Ref: whatsnew/changelog id2212459385
Ref: 10612459385
Ref: Windows<22>-Footnote-12459542
Node: IDLE<28>2459585
Ref: whatsnew/changelog id2222459682
Ref: 10622459682
Ref: IDLE<28>-Footnote-12460902
Ref: IDLE<28>-Footnote-22460945
Ref: IDLE<28>-Footnote-32460988
Ref: IDLE<28>-Footnote-42461031
Ref: IDLE<28>-Footnote-52461074
Ref: IDLE<28>-Footnote-62461117
Node: Python 3 7 0 beta 52461160
Ref: whatsnew/changelog python-3-7-0-beta-52461312
Ref: 10632461312
Node: Core and Builtins<30>2461589
Ref: whatsnew/changelog id2232461686
Ref: 10642461686
Ref: Core and Builtins<30>-Footnote-12463206
Ref: Core and Builtins<30>-Footnote-22463249
Ref: Core and Builtins<30>-Footnote-32463292
Ref: Core and Builtins<30>-Footnote-42463335
Ref: Core and Builtins<30>-Footnote-52463378
Ref: Core and Builtins<30>-Footnote-62463421
Ref: Core and Builtins<30>-Footnote-72463464
Ref: Core and Builtins<30>-Footnote-82463507
Ref: Core and Builtins<30>-Footnote-92463550
Node: Library<31>2463593
Ref: whatsnew/changelog id2242463716
Ref: 10652463716
Ref: Library<31>-Footnote-12469331
Ref: Library<31>-Footnote-22469374
Ref: Library<31>-Footnote-32469417
Ref: Library<31>-Footnote-42469460
Ref: Library<31>-Footnote-52469503
Ref: Library<31>-Footnote-62469546
Ref: Library<31>-Footnote-72469589
Ref: Library<31>-Footnote-82469632
Ref: Library<31>-Footnote-92469675
Ref: Library<31>-Footnote-102469718
Ref: Library<31>-Footnote-112469762
Ref: Library<31>-Footnote-122469806
Ref: Library<31>-Footnote-132469850
Ref: Library<31>-Footnote-142469894
Ref: Library<31>-Footnote-152469938
Ref: Library<31>-Footnote-162469982
Ref: Library<31>-Footnote-172470026
Ref: Library<31>-Footnote-182470070
Ref: Library<31>-Footnote-192470114
Ref: Library<31>-Footnote-202470158
Ref: Library<31>-Footnote-212470202
Ref: Library<31>-Footnote-222470246
Ref: Library<31>-Footnote-232470290
Ref: Library<31>-Footnote-242470334
Ref: Library<31>-Footnote-252470378
Ref: Library<31>-Footnote-262470422
Ref: Library<31>-Footnote-272470466
Ref: Library<31>-Footnote-282470510
Ref: Library<31>-Footnote-292470554
Ref: Library<31>-Footnote-302470598
Ref: Library<31>-Footnote-312470642
Ref: Library<31>-Footnote-322470686
Ref: Library<31>-Footnote-332470730
Ref: Library<31>-Footnote-342470774
Ref: Library<31>-Footnote-352470818
Ref: Library<31>-Footnote-362470862
Ref: Library<31>-Footnote-372470906
Ref: Library<31>-Footnote-382470950
Node: Documentation<26>2470994
Ref: whatsnew/changelog id2252471105
Ref: 10662471105
Ref: Documentation<26>-Footnote-12471581
Ref: Documentation<26>-Footnote-22471624
Ref: Documentation<26>-Footnote-32471667
Ref: Documentation<26>-Footnote-42471716
Ref: Documentation<26>-Footnote-52471759
Ref: Documentation<26>-Footnote-62471802
Node: Tests<21>2471845
Ref: whatsnew/changelog id2262471954
Ref: 10672471954
Ref: Tests<21>-Footnote-12472303
Ref: Tests<21>-Footnote-22472346
Node: Build<19>2472389
Ref: whatsnew/changelog id2272472490
Ref: 10682472490
Ref: Build<19>-Footnote-12472969
Ref: Build<19>-Footnote-22473012
Ref: Build<19>-Footnote-32473055
Node: macOS<16>2473098
Ref: whatsnew/changelog id2282473198
Ref: 10692473198
Ref: macOS<16>-Footnote-12473440
Node: IDLE<29>2473483
Ref: whatsnew/changelog id2292473565
Ref: 106a2473565
Ref: IDLE<29>-Footnote-12473844
Ref: IDLE<29>-Footnote-22473887
Ref: IDLE<29>-Footnote-32473930
Node: Python 3 7 0 beta 42473973
Ref: whatsnew/changelog python-3-7-0-beta-42474112
Ref: 106b2474112
Node: Core and Builtins<31>2474445
Ref: whatsnew/changelog id2302474542
Ref: 106c2474542
Ref: Core and Builtins<31>-Footnote-12475676
Ref: Core and Builtins<31>-Footnote-22475719
Ref: Core and Builtins<31>-Footnote-32475762
Ref: Core and Builtins<31>-Footnote-42475805
Ref: Core and Builtins<31>-Footnote-52475848
Ref: Core and Builtins<31>-Footnote-62475891
Ref: Core and Builtins<31>-Footnote-72475934
Node: Library<32>2475977
Ref: whatsnew/changelog id2312476100
Ref: 106d2476100
Ref: Library<32>-Footnote-12478943
Ref: Library<32>-Footnote-22478986
Ref: Library<32>-Footnote-32479029
Ref: Library<32>-Footnote-42479072
Ref: Library<32>-Footnote-52479116
Ref: Library<32>-Footnote-62479159
Ref: Library<32>-Footnote-72479202
Ref: Library<32>-Footnote-82479245
Ref: Library<32>-Footnote-92479288
Ref: Library<32>-Footnote-102479331
Ref: Library<32>-Footnote-112479375
Ref: Library<32>-Footnote-122479419
Ref: Library<32>-Footnote-132479463
Ref: Library<32>-Footnote-142479507
Ref: Library<32>-Footnote-152479551
Ref: Library<32>-Footnote-162479595
Ref: Library<32>-Footnote-172479639
Ref: Library<32>-Footnote-182479689
Ref: Library<32>-Footnote-192479733
Ref: Library<32>-Footnote-202479777
Ref: Library<32>-Footnote-212479821
Ref: Library<32>-Footnote-222479865
Node: Documentation<27>2479909
Ref: whatsnew/changelog id2322480020
Ref: 106e2480020
Ref: Documentation<27>-Footnote-12480771
Ref: Documentation<27>-Footnote-22480814
Ref: Documentation<27>-Footnote-32480857
Ref: Documentation<27>-Footnote-42480900
Ref: Documentation<27>-Footnote-52480943
Ref: Documentation<27>-Footnote-62480985
Node: Tests<22>2481028
Ref: whatsnew/changelog id2332481137
Ref: 106f2481137
Ref: Tests<22>-Footnote-12481353
Node: Build<20>2481396
Ref: whatsnew/changelog id2342481499
Ref: 10702481499
Ref: Build<20>-Footnote-12482189
Ref: Build<20>-Footnote-22482232
Ref: Build<20>-Footnote-32482275
Ref: Build<20>-Footnote-42482318
Ref: Build<20>-Footnote-52482361
Node: Windows<23>2482404
Ref: whatsnew/changelog id2352482507
Ref: 10712482507
Ref: Windows<23>-Footnote-12482648
Node: macOS<17>2482691
Ref: whatsnew/changelog id2362482793
Ref: 10722482793
Ref: macOS<17>-Footnote-12482934
Node: IDLE<30>2482977
Ref: whatsnew/changelog id2372483083
Ref: 10732483083
Ref: IDLE<30>-Footnote-12483673
Ref: IDLE<30>-Footnote-22483716
Node: Tools/Demos<13>2483759
Ref: whatsnew/changelog id2382483847
Ref: 10742483847
Ref: Tools/Demos<13>-Footnote-12484455
Ref: Tools/Demos<13>-Footnote-22484498
Ref: Tools/Demos<13>-Footnote-32484541
Ref: Tools/Demos<13>-Footnote-42484584
Node: Python 3 7 0 beta 32484627
Ref: whatsnew/changelog python-3-7-0-beta-32484766
Ref: 10752484766
Node: Security<21>2485145
Ref: whatsnew/changelog id2392485243
Ref: 10762485243
Ref: Security<21>-Footnote-12485866
Ref: Security<21>-Footnote-22485909
Ref: Security<21>-Footnote-32485952
Node: Core and Builtins<32>2485995
Ref: whatsnew/changelog id2402486113
Ref: 10772486113
Ref: Core and Builtins<32>-Footnote-12487319
Ref: Core and Builtins<32>-Footnote-22487362
Ref: Core and Builtins<32>-Footnote-32487405
Ref: Core and Builtins<32>-Footnote-42487448
Ref: Core and Builtins<32>-Footnote-52487491
Ref: Core and Builtins<32>-Footnote-62487534
Ref: Core and Builtins<32>-Footnote-72487577
Node: Library<33>2487620
Ref: whatsnew/changelog id2412487743
Ref: 10782487743
Ref: Library<33>-Footnote-12491806
Ref: Library<33>-Footnote-22491849
Ref: Library<33>-Footnote-32491892
Ref: Library<33>-Footnote-42491935
Ref: Library<33>-Footnote-52491978
Ref: Library<33>-Footnote-62492021
Ref: Library<33>-Footnote-72492064
Ref: Library<33>-Footnote-82492107
Ref: Library<33>-Footnote-92492150
Ref: Library<33>-Footnote-102492193
Ref: Library<33>-Footnote-112492237
Ref: Library<33>-Footnote-122492281
Ref: Library<33>-Footnote-132492325
Ref: Library<33>-Footnote-142492369
Ref: Library<33>-Footnote-152492413
Ref: Library<33>-Footnote-162492457
Ref: Library<33>-Footnote-172492501
Ref: Library<33>-Footnote-182492545
Ref: Library<33>-Footnote-192492589
Ref: Library<33>-Footnote-202492633
Ref: Library<33>-Footnote-212492677
Ref: Library<33>-Footnote-222492721
Ref: Library<33>-Footnote-232492765
Ref: Library<33>-Footnote-242492809
Ref: Library<33>-Footnote-252492853
Ref: Library<33>-Footnote-262492897
Ref: Library<33>-Footnote-272492941
Node: Documentation<28>2492985
Ref: whatsnew/changelog id2422493096
Ref: 10792493096
Ref: Documentation<28>-Footnote-12493733
Ref: Documentation<28>-Footnote-22493776
Ref: Documentation<28>-Footnote-32493819
Ref: Documentation<28>-Footnote-42493862
Ref: Documentation<28>-Footnote-52493905
Node: Tests<23>2493948
Ref: whatsnew/changelog id2432494057
Ref: 107a2494057
Ref: Tests<23>-Footnote-12494390
Ref: Tests<23>-Footnote-22494433
Ref: Tests<23>-Footnote-32494476
Node: Build<21>2494519
Ref: whatsnew/changelog id2442494622
Ref: 107b2494622
Ref: Build<21>-Footnote-12494759
Node: Windows<24>2494802
Ref: whatsnew/changelog id2452494905
Ref: 107c2494905
Ref: Windows<24>-Footnote-12495184
Ref: Windows<24>-Footnote-22495227
Node: macOS<18>2495270
Ref: whatsnew/changelog id2462495372
Ref: 107d2495372
Ref: macOS<18>-Footnote-12495804
Node: IDLE<31>2495847
Ref: whatsnew/changelog id2472495953
Ref: 107e2495953
Ref: IDLE<31>-Footnote-12496667
Ref: IDLE<31>-Footnote-22496710
Node: Tools/Demos<14>2496753
Ref: whatsnew/changelog id2482496859
Ref: 107f2496859
Ref: Tools/Demos<14>-Footnote-12497089
Node: C API<17>2497132
Ref: whatsnew/changelog id2492497221
Ref: 10802497221
Ref: C API<17>-Footnote-12497605
Ref: C API<17>-Footnote-22497648
Node: Python 3 7 0 beta 22497691
Ref: whatsnew/changelog python-3-7-0-beta-22497830
Ref: 10812497830
Node: Security<22>2498189
Ref: whatsnew/changelog id2502498287
Ref: 10822498287
Ref: Security<22>-Footnote-12498472
Node: Core and Builtins<33>2498515
Ref: whatsnew/changelog id2512498633
Ref: 10832498633
Ref: Core and Builtins<33>-Footnote-12499464
Ref: Core and Builtins<33>-Footnote-22499507
Ref: Core and Builtins<33>-Footnote-32499550
Ref: Core and Builtins<33>-Footnote-42499593
Ref: Core and Builtins<33>-Footnote-52499636
Ref: Core and Builtins<33>-Footnote-62499679
Ref: Core and Builtins<33>-Footnote-72499722
Node: Library<34>2499765
Ref: whatsnew/changelog id2522499888
Ref: 10842499888
Ref: Library<34>-Footnote-12506271
Ref: Library<34>-Footnote-22506314
Ref: Library<34>-Footnote-32506357
Ref: Library<34>-Footnote-42506400
Ref: Library<34>-Footnote-52506443
Ref: Library<34>-Footnote-62506486
Ref: Library<34>-Footnote-72506529
Ref: Library<34>-Footnote-82506572
Ref: Library<34>-Footnote-92506615
Ref: Library<34>-Footnote-102506658
Ref: Library<34>-Footnote-112506702
Ref: Library<34>-Footnote-122506746
Ref: Library<34>-Footnote-132506790
Ref: Library<34>-Footnote-142506834
Ref: Library<34>-Footnote-152506878
Ref: Library<34>-Footnote-162506922
Ref: Library<34>-Footnote-172506966
Ref: Library<34>-Footnote-182507010
Ref: Library<34>-Footnote-192507054
Ref: Library<34>-Footnote-202507098
Ref: Library<34>-Footnote-212507142
Ref: Library<34>-Footnote-222507186
Ref: Library<34>-Footnote-232507230
Ref: Library<34>-Footnote-242507274
Ref: Library<34>-Footnote-252507318
Ref: Library<34>-Footnote-262507362
Ref: Library<34>-Footnote-272507406
Ref: Library<34>-Footnote-282507450
Ref: Library<34>-Footnote-292507494
Ref: Library<34>-Footnote-302507538
Ref: Library<34>-Footnote-312507582
Ref: Library<34>-Footnote-322507626
Ref: Library<34>-Footnote-332507670
Ref: Library<34>-Footnote-342507714
Node: Documentation<29>2507758
Ref: whatsnew/changelog id2532507869
Ref: 10852507869
Ref: Documentation<29>-Footnote-12508839
Ref: Documentation<29>-Footnote-22508882
Ref: Documentation<29>-Footnote-32508925
Ref: Documentation<29>-Footnote-42508968
Ref: Documentation<29>-Footnote-52509011
Ref: Documentation<29>-Footnote-62509054
Ref: Documentation<29>-Footnote-72509096
Ref: Documentation<29>-Footnote-82509139
Node: Tests<24>2509182
Ref: whatsnew/changelog id2542509291
Ref: 10862509291
Ref: Tests<24>-Footnote-12509434
Node: Build<22>2509477
Ref: whatsnew/changelog id2552509580
Ref: 10872509580
Ref: Build<22>-Footnote-12509721
Node: Windows<25>2509764
Ref: whatsnew/changelog id2562509867
Ref: 10882509867
Ref: Windows<25>-Footnote-12510603
Ref: Windows<25>-Footnote-22510646
Ref: Windows<25>-Footnote-32510689
Ref: Windows<25>-Footnote-42510732
Ref: Windows<25>-Footnote-52510775
Ref: Windows<25>-Footnote-62510818
Node: macOS<19>2510861
Ref: whatsnew/changelog id2572510963
Ref: 10892510963
Ref: macOS<19>-Footnote-12511098
Node: IDLE<32>2511141
Ref: whatsnew/changelog id2582511247
Ref: 108a2511247
Ref: IDLE<32>-Footnote-12512090
Ref: IDLE<32>-Footnote-22512133
Ref: IDLE<32>-Footnote-32512176
Ref: IDLE<32>-Footnote-42512219
Ref: IDLE<32>-Footnote-52512262
Ref: IDLE<32>-Footnote-62512305
Node: Tools/Demos<15>2512348
Ref: whatsnew/changelog id2592512436
Ref: 108b2512436
Ref: Tools/Demos<15>-Footnote-12512655
Node: Python 3 7 0 beta 12512698
Ref: whatsnew/changelog python-3-7-0-beta-12512838
Ref: 108c2512838
Node: Core and Builtins<34>2513141
Ref: whatsnew/changelog id2602513238
Ref: 108d2513238
Ref: Core and Builtins<34>-Footnote-12516668
Ref: Core and Builtins<34>-Footnote-22516711
Ref: Core and Builtins<34>-Footnote-32516754
Ref: Core and Builtins<34>-Footnote-42516797
Ref: Core and Builtins<34>-Footnote-52516840
Ref: Core and Builtins<34>-Footnote-62516883
Ref: Core and Builtins<34>-Footnote-72516926
Ref: Core and Builtins<34>-Footnote-82516969
Ref: Core and Builtins<34>-Footnote-92517012
Ref: Core and Builtins<34>-Footnote-102517061
Ref: Core and Builtins<34>-Footnote-112517105
Ref: Core and Builtins<34>-Footnote-122517149
Ref: Core and Builtins<34>-Footnote-132517193
Ref: Core and Builtins<34>-Footnote-142517237
Ref: Core and Builtins<34>-Footnote-152517281
Ref: Core and Builtins<34>-Footnote-162517325
Ref: Core and Builtins<34>-Footnote-172517369
Ref: Core and Builtins<34>-Footnote-182517413
Ref: Core and Builtins<34>-Footnote-192517463
Ref: Core and Builtins<34>-Footnote-202517507
Ref: Core and Builtins<34>-Footnote-212517551
Ref: Core and Builtins<34>-Footnote-222517595
Ref: Core and Builtins<34>-Footnote-232517639
Node: Library<35>2517683
Ref: whatsnew/changelog id2612517806
Ref: 108e2517806
Ref: Library<35>-Footnote-12525190
Ref: Library<35>-Footnote-22525233
Ref: Library<35>-Footnote-32525276
Ref: Library<35>-Footnote-42525319
Ref: Library<35>-Footnote-52525362
Ref: Library<35>-Footnote-62525405
Ref: Library<35>-Footnote-72525448
Ref: Library<35>-Footnote-82525491
Ref: Library<35>-Footnote-92525534
Ref: Library<35>-Footnote-102525577
Ref: Library<35>-Footnote-112525621
Ref: Library<35>-Footnote-122525665
Ref: Library<35>-Footnote-132525709
Ref: Library<35>-Footnote-142525753
Ref: Library<35>-Footnote-152525797
Ref: Library<35>-Footnote-162525841
Ref: Library<35>-Footnote-172525885
Ref: Library<35>-Footnote-182525929
Ref: Library<35>-Footnote-192525979
Ref: Library<35>-Footnote-202526023
Ref: Library<35>-Footnote-212526067
Ref: Library<35>-Footnote-222526111
Ref: Library<35>-Footnote-232526155
Ref: Library<35>-Footnote-242526199
Ref: Library<35>-Footnote-252526243
Ref: Library<35>-Footnote-262526287
Ref: Library<35>-Footnote-272526331
Ref: Library<35>-Footnote-282526375
Ref: Library<35>-Footnote-292526419
Ref: Library<35>-Footnote-302526463
Ref: Library<35>-Footnote-312526507
Ref: Library<35>-Footnote-322526551
Ref: Library<35>-Footnote-332526595
Ref: Library<35>-Footnote-342526639
Ref: Library<35>-Footnote-352526683
Ref: Library<35>-Footnote-362526727
Ref: Library<35>-Footnote-372526771
Ref: Library<35>-Footnote-382526815
Ref: Library<35>-Footnote-392526859
Ref: Library<35>-Footnote-402526903
Ref: Library<35>-Footnote-412526947
Ref: Library<35>-Footnote-422526991
Ref: Library<35>-Footnote-432527035
Ref: Library<35>-Footnote-442527079
Ref: Library<35>-Footnote-452527123
Ref: Library<35>-Footnote-462527167
Ref: Library<35>-Footnote-472527211
Node: Documentation<30>2527255
Ref: whatsnew/changelog id2622527366
Ref: 10912527366
Ref: Documentation<30>-Footnote-12527907
Ref: Documentation<30>-Footnote-22527950
Ref: Documentation<30>-Footnote-32527993
Node: Tests<25>2528036
Ref: whatsnew/changelog id2632528145
Ref: 10922528145
Ref: Tests<25>-Footnote-12529053
Ref: Tests<25>-Footnote-22529096
Ref: Tests<25>-Footnote-32529139
Ref: Tests<25>-Footnote-42529182
Ref: Tests<25>-Footnote-52529225
Ref: Tests<25>-Footnote-62529268
Node: Build<23>2529311
Ref: whatsnew/changelog id2642529414
Ref: 10932529414
Ref: Build<23>-Footnote-12530017
Ref: Build<23>-Footnote-22530060
Ref: Build<23>-Footnote-32530103
Ref: Build<23>-Footnote-42530146
Node: Windows<26>2530189
Ref: whatsnew/changelog id2652530292
Ref: 10942530292
Ref: Windows<26>-Footnote-12530673
Ref: Windows<26>-Footnote-22530716
Ref: Windows<26>-Footnote-32530759
Node: macOS<20>2530802
Ref: whatsnew/changelog id2662530905
Ref: 10952530905
Ref: macOS<20>-Footnote-12531427
Ref: macOS<20>-Footnote-22531470
Node: C API<18>2531513
Ref: whatsnew/changelog id2672531596
Ref: 10962531596
Ref: C API<18>-Footnote-12531917
Ref: C API<18>-Footnote-22531960
Node: Python 3 7 0 alpha 42532003
Ref: whatsnew/changelog python-3-7-0-alpha-42532144
Ref: 10972532144
Node: Core and Builtins<35>2532441
Ref: whatsnew/changelog id2682532539
Ref: 10982532539
Ref: Core and Builtins<35>-Footnote-12536045
Ref: Core and Builtins<35>-Footnote-22536088
Ref: Core and Builtins<35>-Footnote-32536131
Ref: Core and Builtins<35>-Footnote-42536174
Ref: Core and Builtins<35>-Footnote-52536217
Ref: Core and Builtins<35>-Footnote-62536260
Ref: Core and Builtins<35>-Footnote-72536303
Ref: Core and Builtins<35>-Footnote-82536346
Ref: Core and Builtins<35>-Footnote-92536389
Ref: Core and Builtins<35>-Footnote-102536432
Ref: Core and Builtins<35>-Footnote-112536476
Ref: Core and Builtins<35>-Footnote-122536520
Ref: Core and Builtins<35>-Footnote-132536564
Ref: Core and Builtins<35>-Footnote-142536608
Ref: Core and Builtins<35>-Footnote-152536652
Ref: Core and Builtins<35>-Footnote-162536696
Ref: Core and Builtins<35>-Footnote-172536740
Ref: Core and Builtins<35>-Footnote-182536784
Ref: Core and Builtins<35>-Footnote-192536828
Ref: Core and Builtins<35>-Footnote-202536878
Ref: Core and Builtins<35>-Footnote-212536922
Ref: Core and Builtins<35>-Footnote-222536972
Ref: Core and Builtins<35>-Footnote-232537016
Ref: Core and Builtins<35>-Footnote-242537066
Ref: Core and Builtins<35>-Footnote-252537110
Ref: Core and Builtins<35>-Footnote-262537154
Ref: Core and Builtins<35>-Footnote-272537204
Node: Library<36>2537248
Ref: whatsnew/changelog id2692537372
Ref: 109a2537372
Ref: Library<36>-Footnote-12545384
Ref: Library<36>-Footnote-22545427
Ref: Library<36>-Footnote-32545470
Ref: Library<36>-Footnote-42545513
Ref: Library<36>-Footnote-52545556
Ref: Library<36>-Footnote-62545599
Ref: Library<36>-Footnote-72545642
Ref: Library<36>-Footnote-82545685
Ref: Library<36>-Footnote-92545728
Ref: Library<36>-Footnote-102545771
Ref: Library<36>-Footnote-112545815
Ref: Library<36>-Footnote-122545859
Ref: Library<36>-Footnote-132545903
Ref: Library<36>-Footnote-142545947
Ref: Library<36>-Footnote-152545991
Ref: Library<36>-Footnote-162546035
Ref: Library<36>-Footnote-172546079
Ref: Library<36>-Footnote-182546123
Ref: Library<36>-Footnote-192546167
Ref: Library<36>-Footnote-202546211
Ref: Library<36>-Footnote-212546255
Ref: Library<36>-Footnote-222546299
Ref: Library<36>-Footnote-232546343
Ref: Library<36>-Footnote-242546387
Ref: Library<36>-Footnote-252546431
Ref: Library<36>-Footnote-262546475
Ref: Library<36>-Footnote-272546519
Ref: Library<36>-Footnote-282546563
Ref: Library<36>-Footnote-292546607
Ref: Library<36>-Footnote-302546651
Ref: Library<36>-Footnote-312546695
Ref: Library<36>-Footnote-322546739
Ref: Library<36>-Footnote-332546783
Ref: Library<36>-Footnote-342546827
Ref: Library<36>-Footnote-352546871
Ref: Library<36>-Footnote-362546915
Ref: Library<36>-Footnote-372546959
Ref: Library<36>-Footnote-382547003
Ref: Library<36>-Footnote-392547047
Ref: Library<36>-Footnote-402547091
Ref: Library<36>-Footnote-412547135
Ref: Library<36>-Footnote-422547179
Ref: Library<36>-Footnote-432547223
Ref: Library<36>-Footnote-442547267
Ref: Library<36>-Footnote-452547311
Ref: Library<36>-Footnote-462547355
Ref: Library<36>-Footnote-472547399
Ref: Library<36>-Footnote-482547443
Ref: Library<36>-Footnote-492547487
Ref: Library<36>-Footnote-502547531
Ref: Library<36>-Footnote-512547575
Ref: Library<36>-Footnote-522547619
Ref: Library<36>-Footnote-532547663
Ref: Library<36>-Footnote-542547707
Node: Documentation<31>2547751
Ref: whatsnew/changelog id2702547863
Ref: 109d2547863
Ref: Documentation<31>-Footnote-12548033
Node: Tests<26>2548076
Ref: whatsnew/changelog id2712548188
Ref: 109e2548188
Ref: Tests<26>-Footnote-12548583
Ref: Tests<26>-Footnote-22548626
Node: Windows<27>2548669
Ref: whatsnew/changelog id2722548779
Ref: 109f2548779
Ref: Windows<27>-Footnote-12548978
Node: Tools/Demos<16>2549021
Ref: whatsnew/changelog id2732549131
Ref: 10a02549131
Ref: Tools/Demos<16>-Footnote-12549413
Node: C API<19>2549456
Ref: whatsnew/changelog id2742549546
Ref: 10a12549546
Ref: C API<19>-Footnote-12550207
Ref: C API<19>-Footnote-22550250
Ref: C API<19>-Footnote-32550293
Ref: C API<19>-Footnote-42550336
Node: Python 3 7 0 alpha 32550379
Ref: whatsnew/changelog python-3-7-0-alpha-32550521
Ref: 10a22550521
Node: Core and Builtins<36>2550876
Ref: whatsnew/changelog id2752550974
Ref: 10a32550974
Ref: Core and Builtins<36>-Footnote-12556095
Ref: Core and Builtins<36>-Footnote-22556138
Ref: Core and Builtins<36>-Footnote-32556181
Ref: Core and Builtins<36>-Footnote-42556224
Ref: Core and Builtins<36>-Footnote-52556267
Ref: Core and Builtins<36>-Footnote-62556310
Ref: Core and Builtins<36>-Footnote-72556353
Ref: Core and Builtins<36>-Footnote-82556396
Ref: Core and Builtins<36>-Footnote-92556439
Ref: Core and Builtins<36>-Footnote-102556482
Ref: Core and Builtins<36>-Footnote-112556526
Ref: Core and Builtins<36>-Footnote-122556570
Ref: Core and Builtins<36>-Footnote-132556614
Ref: Core and Builtins<36>-Footnote-142556658
Ref: Core and Builtins<36>-Footnote-152556702
Ref: Core and Builtins<36>-Footnote-162556746
Ref: Core and Builtins<36>-Footnote-172556790
Ref: Core and Builtins<36>-Footnote-182556834
Ref: Core and Builtins<36>-Footnote-192556878
Ref: Core and Builtins<36>-Footnote-202556922
Ref: Core and Builtins<36>-Footnote-212556966
Ref: Core and Builtins<36>-Footnote-222557010
Node: Library<37>2557054
Ref: whatsnew/changelog id2762557178
Ref: 10a42557178
Ref: Library<37>-Footnote-12573241
Ref: Library<37>-Footnote-22573284
Ref: Library<37>-Footnote-32573327
Ref: Library<37>-Footnote-42573370
Ref: Library<37>-Footnote-52573413
Ref: Library<37>-Footnote-62573456
Ref: Library<37>-Footnote-72573499
Ref: Library<37>-Footnote-82573542
Ref: Library<37>-Footnote-92573586
Ref: Library<37>-Footnote-102573629
Ref: Library<37>-Footnote-112573673
Ref: Library<37>-Footnote-122573717
Ref: Library<37>-Footnote-132573761
Ref: Library<37>-Footnote-142573805
Ref: Library<37>-Footnote-152573849
Ref: Library<37>-Footnote-162573893
Ref: Library<37>-Footnote-172573937
Ref: Library<37>-Footnote-182573981
Ref: Library<37>-Footnote-192574025
Ref: Library<37>-Footnote-202574069
Ref: Library<37>-Footnote-212574113
Ref: Library<37>-Footnote-222574157
Ref: Library<37>-Footnote-232574201
Ref: Library<37>-Footnote-242574245
Ref: Library<37>-Footnote-252574289
Ref: Library<37>-Footnote-262574335
Ref: Library<37>-Footnote-272574379
Ref: Library<37>-Footnote-282574423
Ref: Library<37>-Footnote-292574467
Ref: Library<37>-Footnote-302574511
Ref: Library<37>-Footnote-312574555
Ref: Library<37>-Footnote-322574599
Ref: Library<37>-Footnote-332574649
Ref: Library<37>-Footnote-342574693
Ref: Library<37>-Footnote-352574737
Ref: Library<37>-Footnote-362574781
Ref: Library<37>-Footnote-372574825
Ref: Library<37>-Footnote-382574869
Ref: Library<37>-Footnote-392574913
Ref: Library<37>-Footnote-402574957
Ref: Library<37>-Footnote-412575001
Ref: Library<37>-Footnote-422575045
Ref: Library<37>-Footnote-432575089
Ref: Library<37>-Footnote-442575133
Ref: Library<37>-Footnote-452575177
Ref: Library<37>-Footnote-462575221
Ref: Library<37>-Footnote-472575264
Ref: Library<37>-Footnote-482575308
Ref: Library<37>-Footnote-492575352
Ref: Library<37>-Footnote-502575396
Ref: Library<37>-Footnote-512575440
Ref: Library<37>-Footnote-522575484
Ref: Library<37>-Footnote-532575528
Ref: Library<37>-Footnote-542575572
Ref: Library<37>-Footnote-552575616
Ref: Library<37>-Footnote-562575660
Ref: Library<37>-Footnote-572575704
Ref: Library<37>-Footnote-582575748
Ref: Library<37>-Footnote-592575792
Ref: Library<37>-Footnote-602575836
Ref: Library<37>-Footnote-612575880
Ref: Library<37>-Footnote-622575924
Ref: Library<37>-Footnote-632575974
Ref: Library<37>-Footnote-642576018
Ref: Library<37>-Footnote-652576062
Ref: Library<37>-Footnote-662576106
Ref: Library<37>-Footnote-672576150
Ref: Library<37>-Footnote-682576194
Ref: Library<37>-Footnote-692576238
Ref: Library<37>-Footnote-702576282
Ref: Library<37>-Footnote-712576326
Ref: Library<37>-Footnote-722576370
Ref: Library<37>-Footnote-732576414
Ref: Library<37>-Footnote-742576458
Ref: Library<37>-Footnote-752576502
Ref: Library<37>-Footnote-762576546
Ref: Library<37>-Footnote-772576590
Ref: Library<37>-Footnote-782576634
Ref: Library<37>-Footnote-792576678
Ref: Library<37>-Footnote-802576722
Ref: Library<37>-Footnote-812576766
Ref: Library<37>-Footnote-822576810
Ref: Library<37>-Footnote-832576860
Ref: Library<37>-Footnote-842576904
Ref: Library<37>-Footnote-852576948
Ref: Library<37>-Footnote-862576992
Ref: Library<37>-Footnote-872577036
Ref: Library<37>-Footnote-882577080
Ref: Library<37>-Footnote-892577124
Ref: Library<37>-Footnote-902577168
Ref: Library<37>-Footnote-912577212
Ref: Library<37>-Footnote-922577256
Ref: Library<37>-Footnote-932577300
Ref: Library<37>-Footnote-942577344
Ref: Library<37>-Footnote-952577388
Ref: Library<37>-Footnote-962577432
Ref: Library<37>-Footnote-972577476
Ref: Library<37>-Footnote-982577520
Node: Documentation<32>2577564
Ref: whatsnew/changelog id2772577676
Ref: 10aa2577676
Ref: Documentation<32>-Footnote-12577859
Node: Tests<27>2577902
Ref: whatsnew/changelog id2782578012
Ref: 10ab2578012
Ref: Tests<27>-Footnote-12579222
Ref: Tests<27>-Footnote-22579265
Ref: Tests<27>-Footnote-32579308
Ref: Tests<27>-Footnote-42579351
Ref: Tests<27>-Footnote-52579394
Ref: Tests<27>-Footnote-62579437
Ref: Tests<27>-Footnote-72579480
Node: Build<24>2579523
Ref: whatsnew/changelog id2792579627
Ref: 10ac2579627
Ref: Build<24>-Footnote-12580841
Ref: Build<24>-Footnote-22580884
Ref: Build<24>-Footnote-32580927
Ref: Build<24>-Footnote-42580970
Ref: Build<24>-Footnote-52581013
Ref: Build<24>-Footnote-62581056
Ref: Build<24>-Footnote-72581099
Ref: Build<24>-Footnote-82581142
Ref: Build<24>-Footnote-92581185
Ref: Build<24>-Footnote-102581228
Ref: Build<24>-Footnote-112581272
Ref: Build<24>-Footnote-122581316
Node: Windows<28>2581360
Ref: whatsnew/changelog id2802581464
Ref: 10ad2581464
Ref: Windows<28>-Footnote-12581997
Ref: Windows<28>-Footnote-22582039
Ref: Windows<28>-Footnote-32582082
Ref: Windows<28>-Footnote-42582125
Node: macOS<21>2582168
Ref: whatsnew/changelog id2812582271
Ref: 10ae2582271
Ref: macOS<21>-Footnote-12582405
Node: IDLE<33>2582448
Ref: whatsnew/changelog id2822582555
Ref: 10af2582555
Ref: IDLE<33>-Footnote-12584648
Ref: IDLE<33>-Footnote-22584691
Ref: IDLE<33>-Footnote-32584734
Ref: IDLE<33>-Footnote-42584777
Ref: IDLE<33>-Footnote-52584820
Ref: IDLE<33>-Footnote-62584863
Ref: IDLE<33>-Footnote-72584906
Ref: IDLE<33>-Footnote-82584949
Node: Tools/Demos<17>2584992
Ref: whatsnew/changelog id2832585099
Ref: 10b02585099
Ref: Tools/Demos<17>-Footnote-12585631
Ref: Tools/Demos<17>-Footnote-22585674
Node: C API<20>2585717
Ref: whatsnew/changelog id2842585807
Ref: 10b12585807
Ref: C API<20>-Footnote-12586935
Ref: C API<20>-Footnote-22586978
Ref: C API<20>-Footnote-32587021
Ref: C API<20>-Footnote-42587064
Ref: C API<20>-Footnote-52587107
Ref: C API<20>-Footnote-62587150
Node: Python 3 7 0 alpha 22587193
Ref: whatsnew/changelog python-3-7-0-alpha-22587335
Ref: 10b22587335
Node: Core and Builtins<37>2587594
Ref: whatsnew/changelog id2852587692
Ref: 10b32587692
Ref: Core and Builtins<37>-Footnote-12591891
Ref: Core and Builtins<37>-Footnote-22591934
Ref: Core and Builtins<37>-Footnote-32591977
Ref: Core and Builtins<37>-Footnote-42592020
Ref: Core and Builtins<37>-Footnote-52592063
Ref: Core and Builtins<37>-Footnote-62592106
Ref: Core and Builtins<37>-Footnote-72592149
Ref: Core and Builtins<37>-Footnote-82592192
Ref: Core and Builtins<37>-Footnote-92592235
Ref: Core and Builtins<37>-Footnote-102592278
Ref: Core and Builtins<37>-Footnote-112592322
Ref: Core and Builtins<37>-Footnote-122592366
Ref: Core and Builtins<37>-Footnote-132592410
Ref: Core and Builtins<37>-Footnote-142592454
Ref: Core and Builtins<37>-Footnote-152592498
Ref: Core and Builtins<37>-Footnote-162592542
Ref: Core and Builtins<37>-Footnote-172592586
Ref: Core and Builtins<37>-Footnote-182592630
Ref: Core and Builtins<37>-Footnote-192592674
Ref: Core and Builtins<37>-Footnote-202592718
Ref: Core and Builtins<37>-Footnote-212592768
Ref: Core and Builtins<37>-Footnote-222592812
Ref: Core and Builtins<37>-Footnote-232592856
Ref: Core and Builtins<37>-Footnote-242592900
Ref: Core and Builtins<37>-Footnote-252592944
Ref: Core and Builtins<37>-Footnote-262592988
Ref: Core and Builtins<37>-Footnote-272593032
Node: Library<38>2593082
Ref: whatsnew/changelog id2862593206
Ref: 10b62593206
Ref: Library<38>-Footnote-12597287
Ref: Library<38>-Footnote-22597330
Ref: Library<38>-Footnote-32597373
Ref: Library<38>-Footnote-42597416
Ref: Library<38>-Footnote-52597459
Ref: Library<38>-Footnote-62597502
Ref: Library<38>-Footnote-72597545
Ref: Library<38>-Footnote-82597588
Ref: Library<38>-Footnote-92597631
Ref: Library<38>-Footnote-102597674
Ref: Library<38>-Footnote-112597718
Ref: Library<38>-Footnote-122597762
Ref: Library<38>-Footnote-132597806
Ref: Library<38>-Footnote-142597850
Ref: Library<38>-Footnote-152597894
Ref: Library<38>-Footnote-162597938
Ref: Library<38>-Footnote-172597982
Ref: Library<38>-Footnote-182598026
Ref: Library<38>-Footnote-192598070
Ref: Library<38>-Footnote-202598114
Ref: Library<38>-Footnote-212598158
Ref: Library<38>-Footnote-222598202
Ref: Library<38>-Footnote-232598246
Ref: Library<38>-Footnote-242598290
Ref: Library<38>-Footnote-252598334
Ref: Library<38>-Footnote-262598378
Node: Documentation<33>2598422
Ref: whatsnew/changelog id2872598534
Ref: 10b82598534
Ref: Documentation<33>-Footnote-12598925
Ref: Documentation<33>-Footnote-22598968
Node: Build<25>2599011
Ref: whatsnew/changelog id2882599120
Ref: 10b92599120
Ref: Build<25>-Footnote-12599747
Ref: Build<25>-Footnote-22599790
Ref: Build<25>-Footnote-32599833
Ref: Build<25>-Footnote-42599876
Ref: Build<25>-Footnote-52599919
Ref: Build<25>-Footnote-62599962
Node: IDLE<34>2600005
Ref: whatsnew/changelog id2892600106
Ref: 10ba2600106
Ref: IDLE<34>-Footnote-12601412
Ref: IDLE<34>-Footnote-22601455
Ref: IDLE<34>-Footnote-32601498
Ref: IDLE<34>-Footnote-42601541
Ref: IDLE<34>-Footnote-52601584
Ref: IDLE<34>-Footnote-62601627
Node: C API<21>2601672
Ref: whatsnew/changelog id2902601755
Ref: 10bb2601755
Ref: C API<21>-Footnote-12602497
Ref: C API<21>-Footnote-22602540
Ref: C API<21>-Footnote-32602583
Ref: C API<21>-Footnote-42602626
Node: Python 3 7 0 alpha 12602675
Ref: whatsnew/changelog python-3-7-0-alpha-12602815
Ref: 10bc2602815
Node: Security<23>2603176
Ref: whatsnew/changelog id2912603275
Ref: 10bd2603275
Ref: Security<23>-Footnote-12604899
Ref: Security<23>-Footnote-22604942
Ref: Security<23>-Footnote-32604985
Ref: Security<23>-Footnote-42605028
Ref: Security<23>-Footnote-52605071
Ref: Security<23>-Footnote-62605114
Ref: Security<23>-Footnote-72605157
Node: Core and Builtins<38>2605200
Ref: whatsnew/changelog id2922605319
Ref: 10be2605319
Ref: Core and Builtins<38>-Footnote-12626212
Ref: Core and Builtins<38>-Footnote-22626255
Ref: Core and Builtins<38>-Footnote-32626298
Ref: Core and Builtins<38>-Footnote-42626341
Ref: Core and Builtins<38>-Footnote-52626384
Ref: Core and Builtins<38>-Footnote-62626427
Ref: Core and Builtins<38>-Footnote-72626470
Ref: Core and Builtins<38>-Footnote-82626513
Ref: Core and Builtins<38>-Footnote-92626556
Ref: Core and Builtins<38>-Footnote-102626599
Ref: Core and Builtins<38>-Footnote-112626643
Ref: Core and Builtins<38>-Footnote-122626687
Ref: Core and Builtins<38>-Footnote-132626731
Ref: Core and Builtins<38>-Footnote-142626775
Ref: Core and Builtins<38>-Footnote-152626819
Ref: Core and Builtins<38>-Footnote-162626863
Ref: Core and Builtins<38>-Footnote-172626907
Ref: Core and Builtins<38>-Footnote-182626951
Ref: Core and Builtins<38>-Footnote-192626995
Ref: Core and Builtins<38>-Footnote-202627039
Ref: Core and Builtins<38>-Footnote-212627083
Ref: Core and Builtins<38>-Footnote-222627127
Ref: Core and Builtins<38>-Footnote-232627171
Ref: Core and Builtins<38>-Footnote-242627215
Ref: Core and Builtins<38>-Footnote-252627259
Ref: Core and Builtins<38>-Footnote-262627303
Ref: Core and Builtins<38>-Footnote-272627347
Ref: Core and Builtins<38>-Footnote-282627391
Ref: Core and Builtins<38>-Footnote-292627435
Ref: Core and Builtins<38>-Footnote-302627479
Ref: Core and Builtins<38>-Footnote-312627523
Ref: Core and Builtins<38>-Footnote-322627567
Ref: Core and Builtins<38>-Footnote-332627611
Ref: Core and Builtins<38>-Footnote-342627655
Ref: Core and Builtins<38>-Footnote-352627699
Ref: Core and Builtins<38>-Footnote-362627749
Ref: Core and Builtins<38>-Footnote-372627793
Ref: Core and Builtins<38>-Footnote-382627837
Ref: Core and Builtins<38>-Footnote-392627881
Ref: Core and Builtins<38>-Footnote-402627925
Ref: Core and Builtins<38>-Footnote-412627969
Ref: Core and Builtins<38>-Footnote-422628013
Ref: Core and Builtins<38>-Footnote-432628057
Ref: Core and Builtins<38>-Footnote-442628101
Ref: Core and Builtins<38>-Footnote-452628145
Ref: Core and Builtins<38>-Footnote-462628189
Ref: Core and Builtins<38>-Footnote-472628233
Ref: Core and Builtins<38>-Footnote-482628277
Ref: Core and Builtins<38>-Footnote-492628321
Ref: Core and Builtins<38>-Footnote-502628365
Ref: Core and Builtins<38>-Footnote-512628409
Ref: Core and Builtins<38>-Footnote-522628453
Ref: Core and Builtins<38>-Footnote-532628497
Ref: Core and Builtins<38>-Footnote-542628541
Ref: Core and Builtins<38>-Footnote-552628585
Ref: Core and Builtins<38>-Footnote-562628629
Ref: Core and Builtins<38>-Footnote-572628673
Ref: Core and Builtins<38>-Footnote-582628717
Ref: Core and Builtins<38>-Footnote-592628761
Ref: Core and Builtins<38>-Footnote-602628805
Ref: Core and Builtins<38>-Footnote-612628849
Ref: Core and Builtins<38>-Footnote-622628893
Ref: Core and Builtins<38>-Footnote-632628937
Ref: Core and Builtins<38>-Footnote-642628981
Ref: Core and Builtins<38>-Footnote-652629025
Ref: Core and Builtins<38>-Footnote-662629069
Ref: Core and Builtins<38>-Footnote-672629113
Ref: Core and Builtins<38>-Footnote-682629157
Ref: Core and Builtins<38>-Footnote-692629201
Ref: Core and Builtins<38>-Footnote-702629245
Ref: Core and Builtins<38>-Footnote-712629289
Ref: Core and Builtins<38>-Footnote-722629333
Ref: Core and Builtins<38>-Footnote-732629377
Ref: Core and Builtins<38>-Footnote-742629421
Ref: Core and Builtins<38>-Footnote-752629465
Ref: Core and Builtins<38>-Footnote-762629509
Ref: Core and Builtins<38>-Footnote-772629553
Ref: Core and Builtins<38>-Footnote-782629597
Ref: Core and Builtins<38>-Footnote-792629641
Ref: Core and Builtins<38>-Footnote-802629685
Ref: Core and Builtins<38>-Footnote-812629729
Ref: Core and Builtins<38>-Footnote-822629773
Ref: Core and Builtins<38>-Footnote-832629817
Ref: Core and Builtins<38>-Footnote-842629861
Ref: Core and Builtins<38>-Footnote-852629905
Ref: Core and Builtins<38>-Footnote-862629949
Ref: Core and Builtins<38>-Footnote-872629993
Ref: Core and Builtins<38>-Footnote-882630037
Ref: Core and Builtins<38>-Footnote-892630081
Ref: Core and Builtins<38>-Footnote-902630125
Ref: Core and Builtins<38>-Footnote-912630175
Ref: Core and Builtins<38>-Footnote-922630219
Ref: Core and Builtins<38>-Footnote-932630263
Ref: Core and Builtins<38>-Footnote-942630307
Ref: Core and Builtins<38>-Footnote-952630351
Ref: Core and Builtins<38>-Footnote-962630395
Ref: Core and Builtins<38>-Footnote-972630439
Ref: Core and Builtins<38>-Footnote-982630483
Ref: Core and Builtins<38>-Footnote-992630527
Ref: Core and Builtins<38>-Footnote-1002630571
Ref: Core and Builtins<38>-Footnote-1012630616
Ref: Core and Builtins<38>-Footnote-1022630661
Ref: Core and Builtins<38>-Footnote-1032630706
Ref: Core and Builtins<38>-Footnote-1042630751
Ref: Core and Builtins<38>-Footnote-1052630796
Ref: Core and Builtins<38>-Footnote-1062630841
Ref: Core and Builtins<38>-Footnote-1072630886
Ref: Core and Builtins<38>-Footnote-1082630931
Ref: Core and Builtins<38>-Footnote-1092630976
Ref: Core and Builtins<38>-Footnote-1102631021
Ref: Core and Builtins<38>-Footnote-1112631066
Ref: Core and Builtins<38>-Footnote-1122631111
Ref: Core and Builtins<38>-Footnote-1132631156
Ref: Core and Builtins<38>-Footnote-1142631201
Ref: Core and Builtins<38>-Footnote-1152631246
Ref: Core and Builtins<38>-Footnote-1162631291
Ref: Core and Builtins<38>-Footnote-1172631336
Ref: Core and Builtins<38>-Footnote-1182631381
Ref: Core and Builtins<38>-Footnote-1192631426
Ref: Core and Builtins<38>-Footnote-1202631471
Ref: Core and Builtins<38>-Footnote-1212631516
Ref: Core and Builtins<38>-Footnote-1222631561
Ref: Core and Builtins<38>-Footnote-1232631606
Ref: Core and Builtins<38>-Footnote-1242631651
Ref: Core and Builtins<38>-Footnote-1252631696
Ref: Core and Builtins<38>-Footnote-1262631741
Ref: Core and Builtins<38>-Footnote-1272631786
Ref: Core and Builtins<38>-Footnote-1282631831
Ref: Core and Builtins<38>-Footnote-1292631876
Ref: Core and Builtins<38>-Footnote-1302631921
Ref: Core and Builtins<38>-Footnote-1312631966
Ref: Core and Builtins<38>-Footnote-1322632011
Ref: Core and Builtins<38>-Footnote-1332632056
Ref: Core and Builtins<38>-Footnote-1342632101
Ref: Core and Builtins<38>-Footnote-1352632146
Ref: Core and Builtins<38>-Footnote-1362632191
Ref: Core and Builtins<38>-Footnote-1372632236
Ref: Core and Builtins<38>-Footnote-1382632281
Ref: Core and Builtins<38>-Footnote-1392632326
Ref: Core and Builtins<38>-Footnote-1402632371
Ref: Core and Builtins<38>-Footnote-1412632416
Ref: Core and Builtins<38>-Footnote-1422632461
Ref: Core and Builtins<38>-Footnote-1432632506
Ref: Core and Builtins<38>-Footnote-1442632551
Ref: Core and Builtins<38>-Footnote-1452632596
Ref: Core and Builtins<38>-Footnote-1462632641
Ref: Core and Builtins<38>-Footnote-1472632686
Ref: Core and Builtins<38>-Footnote-1482632731
Node: Library<39>2632776
Ref: whatsnew/changelog id2932632900
Ref: 10c02632900
Ref: Library<39>-Footnote-12679515
Ref: Library<39>-Footnote-22679558
Ref: Library<39>-Footnote-32679601
Ref: Library<39>-Footnote-42679644
Ref: Library<39>-Footnote-52679687
Ref: Library<39>-Footnote-62679730
Ref: Library<39>-Footnote-72679773
Ref: Library<39>-Footnote-82679816
Ref: Library<39>-Footnote-92679859
Ref: Library<39>-Footnote-102679902
Ref: Library<39>-Footnote-112679946
Ref: Library<39>-Footnote-122679990
Ref: Library<39>-Footnote-132680034
Ref: Library<39>-Footnote-142680078
Ref: Library<39>-Footnote-152680122
Ref: Library<39>-Footnote-162680166
Ref: Library<39>-Footnote-172680210
Ref: Library<39>-Footnote-182680254
Ref: Library<39>-Footnote-192680298
Ref: Library<39>-Footnote-202680342
Ref: Library<39>-Footnote-212680386
Ref: Library<39>-Footnote-222680432
Ref: Library<39>-Footnote-232680476
Ref: Library<39>-Footnote-242680520
Ref: Library<39>-Footnote-252680564
Ref: Library<39>-Footnote-262680608
Ref: Library<39>-Footnote-272680658
Ref: Library<39>-Footnote-282680702
Ref: Library<39>-Footnote-292680746
Ref: Library<39>-Footnote-302680790
Ref: Library<39>-Footnote-312680834
Ref: Library<39>-Footnote-322680878
Ref: Library<39>-Footnote-332680922
Ref: Library<39>-Footnote-342680966
Ref: Library<39>-Footnote-352681009
Ref: Library<39>-Footnote-362681053
Ref: Library<39>-Footnote-372681097
Ref: Library<39>-Footnote-382681141
Ref: Library<39>-Footnote-392681185
Ref: Library<39>-Footnote-402681228
Ref: Library<39>-Footnote-412681272
Ref: Library<39>-Footnote-422681316
Ref: Library<39>-Footnote-432681360
Ref: Library<39>-Footnote-442681404
Ref: Library<39>-Footnote-452681448
Ref: Library<39>-Footnote-462681492
Ref: Library<39>-Footnote-472681536
Ref: Library<39>-Footnote-482681580
Ref: Library<39>-Footnote-492681624
Ref: Library<39>-Footnote-502681668
Ref: Library<39>-Footnote-512681712
Ref: Library<39>-Footnote-522681756
Ref: Library<39>-Footnote-532681799
Ref: Library<39>-Footnote-542681843
Ref: Library<39>-Footnote-552681887
Ref: Library<39>-Footnote-562681931
Ref: Library<39>-Footnote-572681975
Ref: Library<39>-Footnote-582682019
Ref: Library<39>-Footnote-592682063
Ref: Library<39>-Footnote-602682107
Ref: Library<39>-Footnote-612682151
Ref: Library<39>-Footnote-622682195
Ref: Library<39>-Footnote-632682239
Ref: Library<39>-Footnote-642682283
Ref: Library<39>-Footnote-652682327
Ref: Library<39>-Footnote-662682371
Ref: Library<39>-Footnote-672682415
Ref: Library<39>-Footnote-682682459
Ref: Library<39>-Footnote-692682503
Ref: Library<39>-Footnote-702682547
Ref: Library<39>-Footnote-712682591
Ref: Library<39>-Footnote-722682635
Ref: Library<39>-Footnote-732682678
Ref: Library<39>-Footnote-742682722
Ref: Library<39>-Footnote-752682766
Ref: Library<39>-Footnote-762682810
Ref: Library<39>-Footnote-772682854
Ref: Library<39>-Footnote-782682898
Ref: Library<39>-Footnote-792682942
Ref: Library<39>-Footnote-802682986
Ref: Library<39>-Footnote-812683030
Ref: Library<39>-Footnote-822683074
Ref: Library<39>-Footnote-832683118
Ref: Library<39>-Footnote-842683162
Ref: Library<39>-Footnote-852683206
Ref: Library<39>-Footnote-862683250
Ref: Library<39>-Footnote-872683294
Ref: Library<39>-Footnote-882683338
Ref: Library<39>-Footnote-892683382
Ref: Library<39>-Footnote-902683426
Ref: Library<39>-Footnote-912683470
Ref: Library<39>-Footnote-922683514
Ref: Library<39>-Footnote-932683558
Ref: Library<39>-Footnote-942683602
Ref: Library<39>-Footnote-952683646
Ref: Library<39>-Footnote-962683690
Ref: Library<39>-Footnote-972683734
Ref: Library<39>-Footnote-982683778
Ref: Library<39>-Footnote-992683822
Ref: Library<39>-Footnote-1002683866
Ref: Library<39>-Footnote-1012683911
Ref: Library<39>-Footnote-1022683956
Ref: Library<39>-Footnote-1032684001
Ref: Library<39>-Footnote-1042684046
Ref: Library<39>-Footnote-1052684091
Ref: Library<39>-Footnote-1062684136
Ref: Library<39>-Footnote-1072684181
Ref: Library<39>-Footnote-1082684226
Ref: Library<39>-Footnote-1092684271
Ref: Library<39>-Footnote-1102684316
Ref: Library<39>-Footnote-1112684361
Ref: Library<39>-Footnote-1122684406
Ref: Library<39>-Footnote-1132684451
Ref: Library<39>-Footnote-1142684496
Ref: Library<39>-Footnote-1152684541
Ref: Library<39>-Footnote-1162684586
Ref: Library<39>-Footnote-1172684630
Ref: Library<39>-Footnote-1182684675
Ref: Library<39>-Footnote-1192684720
Ref: Library<39>-Footnote-1202684765
Ref: Library<39>-Footnote-1212684810
Ref: Library<39>-Footnote-1222684855
Ref: Library<39>-Footnote-1232684900
Ref: Library<39>-Footnote-1242684945
Ref: Library<39>-Footnote-1252684990
Ref: Library<39>-Footnote-1262685035
Ref: Library<39>-Footnote-1272685080
Ref: Library<39>-Footnote-1282685125
Ref: Library<39>-Footnote-1292685170
Ref: Library<39>-Footnote-1302685215
Ref: Library<39>-Footnote-1312685260
Ref: Library<39>-Footnote-1322685305
Ref: Library<39>-Footnote-1332685350
Ref: Library<39>-Footnote-1342685395
Ref: Library<39>-Footnote-1352685440
Ref: Library<39>-Footnote-1362685485
Ref: Library<39>-Footnote-1372685530
Ref: Library<39>-Footnote-1382685575
Ref: Library<39>-Footnote-1392685620
Ref: Library<39>-Footnote-1402685665
Ref: Library<39>-Footnote-1412685710
Ref: Library<39>-Footnote-1422685755
Ref: Library<39>-Footnote-1432685800
Ref: Library<39>-Footnote-1442685845
Ref: Library<39>-Footnote-1452685890
Ref: Library<39>-Footnote-1462685935
Ref: Library<39>-Footnote-1472685979
Ref: Library<39>-Footnote-1482686024
Ref: Library<39>-Footnote-1492686069
Ref: Library<39>-Footnote-1502686114
Ref: Library<39>-Footnote-1512686159
Ref: Library<39>-Footnote-1522686204
Ref: Library<39>-Footnote-1532686249
Ref: Library<39>-Footnote-1542686294
Ref: Library<39>-Footnote-1552686339
Ref: Library<39>-Footnote-1562686384
Ref: Library<39>-Footnote-1572686429
Ref: Library<39>-Footnote-1582686474
Ref: Library<39>-Footnote-1592686519
Ref: Library<39>-Footnote-1602686564
Ref: Library<39>-Footnote-1612686609
Ref: Library<39>-Footnote-1622686654
Ref: Library<39>-Footnote-1632686699
Ref: Library<39>-Footnote-1642686744
Ref: Library<39>-Footnote-1652686789
Ref: Library<39>-Footnote-1662686834
Ref: Library<39>-Footnote-1672686879
Ref: Library<39>-Footnote-1682686924
Ref: Library<39>-Footnote-1692686969
Ref: Library<39>-Footnote-1702687013
Ref: Library<39>-Footnote-1712687058
Ref: Library<39>-Footnote-1722687103
Ref: Library<39>-Footnote-1732687148
Ref: Library<39>-Footnote-1742687193
Ref: Library<39>-Footnote-1752687238
Ref: Library<39>-Footnote-1762687283
Ref: Library<39>-Footnote-1772687328
Ref: Library<39>-Footnote-1782687373
Ref: Library<39>-Footnote-1792687418
Ref: Library<39>-Footnote-1802687463
Ref: Library<39>-Footnote-1812687507
Ref: Library<39>-Footnote-1822687552
Ref: Library<39>-Footnote-1832687597
Ref: Library<39>-Footnote-1842687642
Ref: Library<39>-Footnote-1852687687
Ref: Library<39>-Footnote-1862687732
Ref: Library<39>-Footnote-1872687776
Ref: Library<39>-Footnote-1882687821
Ref: Library<39>-Footnote-1892687866
Ref: Library<39>-Footnote-1902687911
Ref: Library<39>-Footnote-1912687956
Ref: Library<39>-Footnote-1922688001
Ref: Library<39>-Footnote-1932688046
Ref: Library<39>-Footnote-1942688091
Ref: Library<39>-Footnote-1952688136
Ref: Library<39>-Footnote-1962688181
Ref: Library<39>-Footnote-1972688226
Ref: Library<39>-Footnote-1982688271
Ref: Library<39>-Footnote-1992688316
Ref: Library<39>-Footnote-2002688361
Ref: Library<39>-Footnote-2012688406
Ref: Library<39>-Footnote-2022688451
Ref: Library<39>-Footnote-2032688496
Ref: Library<39>-Footnote-2042688541
Ref: Library<39>-Footnote-2052688586
Ref: Library<39>-Footnote-2062688631
Ref: Library<39>-Footnote-2072688676
Ref: Library<39>-Footnote-2082688721
Ref: Library<39>-Footnote-2092688766
Ref: Library<39>-Footnote-2102688811
Ref: Library<39>-Footnote-2112688856
Ref: Library<39>-Footnote-2122688901
Ref: Library<39>-Footnote-2132688946
Ref: Library<39>-Footnote-2142688991
Ref: Library<39>-Footnote-2152689036
Ref: Library<39>-Footnote-2162689081
Ref: Library<39>-Footnote-2172689126
Ref: Library<39>-Footnote-2182689171
Ref: Library<39>-Footnote-2192689216
Ref: Library<39>-Footnote-2202689261
Ref: Library<39>-Footnote-2212689306
Ref: Library<39>-Footnote-2222689351
Ref: Library<39>-Footnote-2232689396
Ref: Library<39>-Footnote-2242689441
Ref: Library<39>-Footnote-2252689485
Ref: Library<39>-Footnote-2262689530
Ref: Library<39>-Footnote-2272689575
Ref: Library<39>-Footnote-2282689620
Ref: Library<39>-Footnote-2292689665
Ref: Library<39>-Footnote-2302689710
Ref: Library<39>-Footnote-2312689755
Ref: Library<39>-Footnote-2322689800
Ref: Library<39>-Footnote-2332689845
Ref: Library<39>-Footnote-2342689890
Ref: Library<39>-Footnote-2352689935
Ref: Library<39>-Footnote-2362689980
Ref: Library<39>-Footnote-2372690025
Ref: Library<39>-Footnote-2382690070
Ref: Library<39>-Footnote-2392690115
Ref: Library<39>-Footnote-2402690160
Ref: Library<39>-Footnote-2412690205
Ref: Library<39>-Footnote-2422690250
Ref: Library<39>-Footnote-2432690295
Ref: Library<39>-Footnote-2442690340
Ref: Library<39>-Footnote-2452690385
Ref: Library<39>-Footnote-2462690430
Ref: Library<39>-Footnote-2472690475
Ref: Library<39>-Footnote-2482690520
Ref: Library<39>-Footnote-2492690565
Ref: Library<39>-Footnote-2502690610
Ref: Library<39>-Footnote-2512690655
Ref: Library<39>-Footnote-2522690700
Ref: Library<39>-Footnote-2532690745
Ref: Library<39>-Footnote-2542690790
Ref: Library<39>-Footnote-2552690835
Ref: Library<39>-Footnote-2562690880
Ref: Library<39>-Footnote-2572690925
Ref: Library<39>-Footnote-2582690970
Ref: Library<39>-Footnote-2592691015
Ref: Library<39>-Footnote-2602691060
Ref: Library<39>-Footnote-2612691105
Ref: Library<39>-Footnote-2622691150
Ref: Library<39>-Footnote-2632691195
Ref: Library<39>-Footnote-2642691240
Ref: Library<39>-Footnote-2652691285
Ref: Library<39>-Footnote-2662691330
Ref: Library<39>-Footnote-2672691375
Ref: Library<39>-Footnote-2682691420
Ref: Library<39>-Footnote-2692691465
Ref: Library<39>-Footnote-2702691510
Ref: Library<39>-Footnote-2712691555
Ref: Library<39>-Footnote-2722691600
Ref: Library<39>-Footnote-2732691656
Ref: Library<39>-Footnote-2742691701
Ref: Library<39>-Footnote-2752691746
Ref: Library<39>-Footnote-2762691791
Ref: Library<39>-Footnote-2772691836
Ref: Library<39>-Footnote-2782691881
Ref: Library<39>-Footnote-2792691926
Ref: Library<39>-Footnote-2802691971
Ref: Library<39>-Footnote-2812692016
Ref: Library<39>-Footnote-2822692061
Ref: Library<39>-Footnote-2832692106
Ref: Library<39>-Footnote-2842692151
Ref: Library<39>-Footnote-2852692196
Ref: Library<39>-Footnote-2862692241
Ref: Library<39>-Footnote-2872692286
Ref: Library<39>-Footnote-2882692331
Ref: Library<39>-Footnote-2892692376
Ref: Library<39>-Footnote-2902692421
Ref: Library<39>-Footnote-2912692466
Ref: Library<39>-Footnote-2922692511
Ref: Library<39>-Footnote-2932692556
Ref: Library<39>-Footnote-2942692601
Ref: Library<39>-Footnote-2952692646
Ref: Library<39>-Footnote-2962692691
Ref: Library<39>-Footnote-2972692736
Ref: Library<39>-Footnote-2982692781
Ref: Library<39>-Footnote-2992692826
Ref: Library<39>-Footnote-3002692871
Ref: Library<39>-Footnote-3012692916
Ref: Library<39>-Footnote-3022692961
Ref: Library<39>-Footnote-3032693006
Ref: Library<39>-Footnote-3042693051
Ref: Library<39>-Footnote-3052693096
Ref: Library<39>-Footnote-3062693141
Ref: Library<39>-Footnote-3072693186
Ref: Library<39>-Footnote-3082693231
Ref: Library<39>-Footnote-3092693276
Ref: Library<39>-Footnote-3102693321
Ref: Library<39>-Footnote-3112693366
Ref: Library<39>-Footnote-3122693411
Ref: Library<39>-Footnote-3132693456
Ref: Library<39>-Footnote-3142693501
Ref: Library<39>-Footnote-3152693546
Ref: Library<39>-Footnote-3162693591
Ref: Library<39>-Footnote-3172693636
Ref: Library<39>-Footnote-3182693681
Ref: Library<39>-Footnote-3192693726
Ref: Library<39>-Footnote-3202693771
Ref: Library<39>-Footnote-3212693816
Ref: Library<39>-Footnote-3222693861
Ref: Library<39>-Footnote-3232693906
Ref: Library<39>-Footnote-3242693951
Ref: Library<39>-Footnote-3252693996
Ref: Library<39>-Footnote-3262694041
Node: Documentation<34>2694086
Ref: whatsnew/changelog id2942694198
Ref: 10c12694198
Ref: Documentation<34>-Footnote-12696364
Ref: Documentation<34>-Footnote-22696407
Ref: Documentation<34>-Footnote-32696450
Ref: Documentation<34>-Footnote-42696493
Ref: Documentation<34>-Footnote-52696536
Ref: Documentation<34>-Footnote-62696579
Ref: Documentation<34>-Footnote-72696622
Ref: Documentation<34>-Footnote-82696665
Ref: Documentation<34>-Footnote-92696708
Ref: Documentation<34>-Footnote-102696751
Ref: Documentation<34>-Footnote-112696795
Ref: Documentation<34>-Footnote-122696839
Ref: Documentation<34>-Footnote-132696883
Ref: Documentation<34>-Footnote-142696927
Ref: Documentation<34>-Footnote-152696971
Ref: Documentation<34>-Footnote-162697015
Ref: Documentation<34>-Footnote-172697065
Node: Tests<28>2697109
Ref: whatsnew/changelog id2952697219
Ref: 10c42697219
Ref: Tests<28>-Footnote-12699969
Ref: Tests<28>-Footnote-22700012
Ref: Tests<28>-Footnote-32700055
Ref: Tests<28>-Footnote-42700098
Ref: Tests<28>-Footnote-52700141
Ref: Tests<28>-Footnote-62700184
Ref: Tests<28>-Footnote-72700227
Ref: Tests<28>-Footnote-82700270
Ref: Tests<28>-Footnote-92700313
Ref: Tests<28>-Footnote-102700356
Ref: Tests<28>-Footnote-112700400
Ref: Tests<28>-Footnote-122700444
Ref: Tests<28>-Footnote-132700488
Ref: Tests<28>-Footnote-142700532
Ref: Tests<28>-Footnote-152700576
Ref: Tests<28>-Footnote-162700620
Ref: Tests<28>-Footnote-172700664
Ref: Tests<28>-Footnote-182700708
Ref: Tests<28>-Footnote-192700752
Node: Build<26>2700796
Ref: whatsnew/changelog id2962700900
Ref: 10c52700900
Ref: Build<26>-Footnote-12705664
Ref: Build<26>-Footnote-22705707
Ref: Build<26>-Footnote-32705750
Ref: Build<26>-Footnote-42705793
Ref: Build<26>-Footnote-52705842
Ref: Build<26>-Footnote-62705885
Ref: Build<26>-Footnote-72705928
Ref: Build<26>-Footnote-82705971
Ref: Build<26>-Footnote-92706014
Ref: Build<26>-Footnote-102706057
Ref: Build<26>-Footnote-112706101
Ref: Build<26>-Footnote-122706145
Ref: Build<26>-Footnote-132706189
Ref: Build<26>-Footnote-142706233
Ref: Build<26>-Footnote-152706277
Ref: Build<26>-Footnote-162706321
Ref: Build<26>-Footnote-172706365
Ref: Build<26>-Footnote-182706409
Ref: Build<26>-Footnote-192706453
Ref: Build<26>-Footnote-202706497
Ref: Build<26>-Footnote-212706541
Ref: Build<26>-Footnote-222706585
Ref: Build<26>-Footnote-232706629
Ref: Build<26>-Footnote-242706673
Ref: Build<26>-Footnote-252706717
Ref: Build<26>-Footnote-262706761
Ref: Build<26>-Footnote-272706805
Ref: Build<26>-Footnote-282706849
Ref: Build<26>-Footnote-292706893
Ref: Build<26>-Footnote-302706937
Ref: Build<26>-Footnote-312706981
Ref: Build<26>-Footnote-322707025
Ref: Build<26>-Footnote-332707069
Ref: Build<26>-Footnote-342707113
Ref: Build<26>-Footnote-352707157
Ref: Build<26>-Footnote-362707201
Ref: Build<26>-Footnote-372707245
Node: Windows<29>2707289
Ref: whatsnew/changelog id2972707392
Ref: 10c62707392
Ref: Windows<29>-Footnote-12709878
Ref: Windows<29>-Footnote-22709921
Ref: Windows<29>-Footnote-32709964
Ref: Windows<29>-Footnote-42710007
Ref: Windows<29>-Footnote-52710050
Ref: Windows<29>-Footnote-62710093
Ref: Windows<29>-Footnote-72710136
Ref: Windows<29>-Footnote-82710179
Ref: Windows<29>-Footnote-92710222
Ref: Windows<29>-Footnote-102710265
Ref: Windows<29>-Footnote-112710309
Ref: Windows<29>-Footnote-122710353
Ref: Windows<29>-Footnote-132710397
Ref: Windows<29>-Footnote-142710441
Ref: Windows<29>-Footnote-152710485
Ref: Windows<29>-Footnote-162710529
Ref: Windows<29>-Footnote-172710573
Ref: Windows<29>-Footnote-182710617
Ref: Windows<29>-Footnote-192710661
Ref: Windows<29>-Footnote-202710705
Ref: Windows<29>-Footnote-212710749
Ref: Windows<29>-Footnote-222710793
Ref: Windows<29>-Footnote-232710837
Ref: Windows<29>-Footnote-242710881
Ref: Windows<29>-Footnote-252710925
Node: IDLE<35>2710969
Ref: whatsnew/changelog id2982711078
Ref: 10c72711078
Ref: IDLE<35>-Footnote-12721095
Ref: IDLE<35>-Footnote-22721138
Ref: IDLE<35>-Footnote-32721181
Ref: IDLE<35>-Footnote-42721224
Ref: IDLE<35>-Footnote-52721267
Ref: IDLE<35>-Footnote-62721310
Ref: IDLE<35>-Footnote-72721353
Ref: IDLE<35>-Footnote-82721396
Ref: IDLE<35>-Footnote-92721439
Ref: IDLE<35>-Footnote-102721482
Ref: IDLE<35>-Footnote-112721526
Ref: IDLE<35>-Footnote-122721570
Ref: IDLE<35>-Footnote-132721614
Ref: IDLE<35>-Footnote-142721658
Ref: IDLE<35>-Footnote-152721702
Ref: IDLE<35>-Footnote-162721746
Ref: IDLE<35>-Footnote-172721790
Ref: IDLE<35>-Footnote-182721834
Ref: IDLE<35>-Footnote-192721878
Ref: IDLE<35>-Footnote-202721922
Ref: IDLE<35>-Footnote-212721966
Ref: IDLE<35>-Footnote-222722010
Ref: IDLE<35>-Footnote-232722054
Ref: IDLE<35>-Footnote-242722098
Ref: IDLE<35>-Footnote-252722142
Ref: IDLE<35>-Footnote-262722186
Ref: IDLE<35>-Footnote-272722230
Ref: IDLE<35>-Footnote-282722274
Ref: IDLE<35>-Footnote-292722318
Ref: IDLE<35>-Footnote-302722362
Ref: IDLE<35>-Footnote-312722406
Ref: IDLE<35>-Footnote-322722450
Ref: IDLE<35>-Footnote-332722494
Ref: IDLE<35>-Footnote-342722538
Ref: IDLE<35>-Footnote-352722581
Ref: IDLE<35>-Footnote-362722625
Ref: IDLE<35>-Footnote-372722669
Ref: IDLE<35>-Footnote-382722713
Ref: IDLE<35>-Footnote-392722757
Ref: IDLE<35>-Footnote-402722801
Ref: IDLE<35>-Footnote-412722845
Ref: IDLE<35>-Footnote-422722889
Ref: IDLE<35>-Footnote-432722933
Ref: IDLE<35>-Footnote-442722976
Ref: IDLE<35>-Footnote-452723020
Ref: IDLE<35>-Footnote-462723064
Ref: IDLE<35>-Footnote-472723108
Ref: IDLE<35>-Footnote-482723152
Ref: IDLE<35>-Footnote-492723196
Ref: IDLE<35>-Footnote-502723240
Ref: IDLE<35>-Footnote-512723284
Node: Tools/Demos<18>2723328
Ref: whatsnew/changelog id2992723435
Ref: 10c82723435
Ref: Tools/Demos<18>-Footnote-12724930
Ref: Tools/Demos<18>-Footnote-22724973
Ref: Tools/Demos<18>-Footnote-32725022
Ref: Tools/Demos<18>-Footnote-42725065
Ref: Tools/Demos<18>-Footnote-52725108
Ref: Tools/Demos<18>-Footnote-62725151
Ref: Tools/Demos<18>-Footnote-72725194
Ref: Tools/Demos<18>-Footnote-82725237
Node: C API<22>2725280
Ref: whatsnew/changelog id3002725370
Ref: 10c92725370
Ref: C API<22>-Footnote-12728426
Ref: C API<22>-Footnote-22728469
Ref: C API<22>-Footnote-32728512
Ref: C API<22>-Footnote-42728555
Ref: C API<22>-Footnote-52728598
Ref: C API<22>-Footnote-62728640
Ref: C API<22>-Footnote-72728683
Ref: C API<22>-Footnote-82728726
Ref: C API<22>-Footnote-92728769
Ref: C API<22>-Footnote-102728812
Ref: C API<22>-Footnote-112728856
Ref: C API<22>-Footnote-122728900
Ref: C API<22>-Footnote-132728944
Ref: C API<22>-Footnote-142728988
Ref: C API<22>-Footnote-152729032
Node: Python 3 6 6 final2729076
Ref: whatsnew/changelog python-3-6-6-final2729228
Ref: 10ca2729228
Node: Python 3 6 6 release candidate 12729356
Ref: whatsnew/changelog python-3-6-6-release-candidate-12729506
Ref: 10cb2729506
Node: Core and Builtins<39>2729885
Ref: whatsnew/changelog id3012729995
Ref: 10cc2729995
Ref: Core and Builtins<39>-Footnote-12731577
Ref: Core and Builtins<39>-Footnote-22731620
Ref: Core and Builtins<39>-Footnote-32731663
Ref: Core and Builtins<39>-Footnote-42731706
Ref: Core and Builtins<39>-Footnote-52731749
Ref: Core and Builtins<39>-Footnote-62731792
Ref: Core and Builtins<39>-Footnote-72731835
Ref: Core and Builtins<39>-Footnote-82731878
Ref: Core and Builtins<39>-Footnote-92731921
Ref: Core and Builtins<39>-Footnote-102731964
Ref: Core and Builtins<39>-Footnote-112732008
Ref: Core and Builtins<39>-Footnote-122732052
Node: Library<40>2732096
Ref: whatsnew/changelog id3022732232
Ref: 10cd2732232
Ref: Library<40>-Footnote-12737711
Ref: Library<40>-Footnote-22737754
Ref: Library<40>-Footnote-32737797
Ref: Library<40>-Footnote-42737840
Ref: Library<40>-Footnote-52737883
Ref: Library<40>-Footnote-62737926
Ref: Library<40>-Footnote-72737969
Ref: Library<40>-Footnote-82738012
Ref: Library<40>-Footnote-92738055
Ref: Library<40>-Footnote-102738098
Ref: Library<40>-Footnote-112738142
Ref: Library<40>-Footnote-122738186
Ref: Library<40>-Footnote-132738230
Ref: Library<40>-Footnote-142738274
Ref: Library<40>-Footnote-152738318
Ref: Library<40>-Footnote-162738362
Ref: Library<40>-Footnote-172738406
Ref: Library<40>-Footnote-182738450
Ref: Library<40>-Footnote-192738494
Ref: Library<40>-Footnote-202738538
Ref: Library<40>-Footnote-212738582
Ref: Library<40>-Footnote-222738627
Ref: Library<40>-Footnote-232738671
Ref: Library<40>-Footnote-242738715
Ref: Library<40>-Footnote-252738759
Ref: Library<40>-Footnote-262738803
Ref: Library<40>-Footnote-272738847
Ref: Library<40>-Footnote-282738891
Ref: Library<40>-Footnote-292738941
Ref: Library<40>-Footnote-302738985
Ref: Library<40>-Footnote-312739029
Ref: Library<40>-Footnote-322739073
Ref: Library<40>-Footnote-332739117
Ref: Library<40>-Footnote-342739161
Ref: Library<40>-Footnote-352739205
Ref: Library<40>-Footnote-362739249
Ref: Library<40>-Footnote-372739293
Ref: Library<40>-Footnote-382739337
Ref: Library<40>-Footnote-392739381
Node: Documentation<35>2739425
Ref: whatsnew/changelog id3032739549
Ref: 10ce2739549
Ref: Documentation<35>-Footnote-12741040
Ref: Documentation<35>-Footnote-22741083
Ref: Documentation<35>-Footnote-32741126
Ref: Documentation<35>-Footnote-42741169
Ref: Documentation<35>-Footnote-52741212
Ref: Documentation<35>-Footnote-62741255
Ref: Documentation<35>-Footnote-72741298
Ref: Documentation<35>-Footnote-82741341
Ref: Documentation<35>-Footnote-92741384
Ref: Documentation<35>-Footnote-102741427
Ref: Documentation<35>-Footnote-112741471
Ref: Documentation<35>-Footnote-122741515
Ref: Documentation<35>-Footnote-132741558
Node: Tests<29>2741602
Ref: whatsnew/changelog id3042741724
Ref: 10cf2741724
Ref: Tests<29>-Footnote-12741946
Ref: Tests<29>-Footnote-22741989
Node: Build<27>2742032
Ref: whatsnew/changelog id3052742148
Ref: 10d02742148
Ref: Build<27>-Footnote-12742945
Ref: Build<27>-Footnote-22742987
Ref: Build<27>-Footnote-32743030
Ref: Build<27>-Footnote-42743073
Ref: Build<27>-Footnote-52743116
Node: Windows<30>2743159
Ref: whatsnew/changelog id3062743275
Ref: 10d12743275
Ref: Windows<30>-Footnote-12743412
Node: macOS<22>2743455
Ref: whatsnew/changelog id3072743570
Ref: 10d22743570
Ref: macOS<22>-Footnote-12743711
Node: IDLE<36>2743754
Ref: whatsnew/changelog id3082743873
Ref: 10d32743873
Ref: IDLE<36>-Footnote-12745942
Ref: IDLE<36>-Footnote-22745985
Ref: IDLE<36>-Footnote-32746028
Ref: IDLE<36>-Footnote-42746071
Ref: IDLE<36>-Footnote-52746114
Ref: IDLE<36>-Footnote-62746157
Ref: IDLE<36>-Footnote-72746200
Ref: IDLE<36>-Footnote-82746243
Ref: IDLE<36>-Footnote-92746286
Ref: IDLE<36>-Footnote-102746329
Ref: IDLE<36>-Footnote-112746373
Ref: IDLE<36>-Footnote-122746417
Node: Tools/Demos<19>2746461
Ref: whatsnew/changelog id3092746580
Ref: 10d42746580
Ref: Tools/Demos<19>-Footnote-12747335
Ref: Tools/Demos<19>-Footnote-22747378
Ref: Tools/Demos<19>-Footnote-32747421
Ref: Tools/Demos<19>-Footnote-42747464
Ref: Tools/Demos<19>-Footnote-52747507
Node: C API<23>2747550
Ref: whatsnew/changelog id3102747652
Ref: 10d52747652
Ref: C API<23>-Footnote-12747865
Node: Python 3 6 5 final2747908
Ref: whatsnew/changelog python-3-6-5-final2748072
Ref: 10d62748072
Node: Tests<30>2748205
Ref: whatsnew/changelog id3112748287
Ref: 10d72748287
Ref: Tests<30>-Footnote-12748441
Node: Build<28>2748484
Ref: whatsnew/changelog id3122748566
Ref: 10d82748566
Ref: Build<28>-Footnote-12748703
Node: Python 3 6 5 release candidate 12748746
Ref: whatsnew/changelog python-3-6-5-release-candidate-12748896
Ref: 10d92748896
Node: Security<24>2749301
Ref: whatsnew/changelog id3132749412
Ref: 10da2749412
Ref: Security<24>-Footnote-12749837
Ref: Security<24>-Footnote-22749880
Node: Core and Builtins<40>2749923
Ref: whatsnew/changelog id3142750054
Ref: 10db2750054
Ref: Core and Builtins<40>-Footnote-12752224
Ref: Core and Builtins<40>-Footnote-22752267
Ref: Core and Builtins<40>-Footnote-32752310
Ref: Core and Builtins<40>-Footnote-42752353
Ref: Core and Builtins<40>-Footnote-52752396
Ref: Core and Builtins<40>-Footnote-62752439
Ref: Core and Builtins<40>-Footnote-72752482
Ref: Core and Builtins<40>-Footnote-82752525
Ref: Core and Builtins<40>-Footnote-92752568
Ref: Core and Builtins<40>-Footnote-102752611
Ref: Core and Builtins<40>-Footnote-112752655
Ref: Core and Builtins<40>-Footnote-122752699
Ref: Core and Builtins<40>-Footnote-132752743
Ref: Core and Builtins<40>-Footnote-142752787
Node: Library<41>2752831
Ref: whatsnew/changelog id3152752967
Ref: 10dc2752967
Ref: Library<41>-Footnote-12758897
Ref: Library<41>-Footnote-22758940
Ref: Library<41>-Footnote-32758983
Ref: Library<41>-Footnote-42759026
Ref: Library<41>-Footnote-52759069
Ref: Library<41>-Footnote-62759112
Ref: Library<41>-Footnote-72759155
Ref: Library<41>-Footnote-82759198
Ref: Library<41>-Footnote-92759241
Ref: Library<41>-Footnote-102759284
Ref: Library<41>-Footnote-112759328
Ref: Library<41>-Footnote-122759372
Ref: Library<41>-Footnote-132759416
Ref: Library<41>-Footnote-142759460
Ref: Library<41>-Footnote-152759504
Ref: Library<41>-Footnote-162759548
Ref: Library<41>-Footnote-172759592
Ref: Library<41>-Footnote-182759636
Ref: Library<41>-Footnote-192759680
Ref: Library<41>-Footnote-202759724
Ref: Library<41>-Footnote-212759768
Ref: Library<41>-Footnote-222759812
Ref: Library<41>-Footnote-232759856
Ref: Library<41>-Footnote-242759900
Ref: Library<41>-Footnote-252759944
Ref: Library<41>-Footnote-262759988
Ref: Library<41>-Footnote-272760032
Ref: Library<41>-Footnote-282760076
Ref: Library<41>-Footnote-292760120
Ref: Library<41>-Footnote-302760164
Ref: Library<41>-Footnote-312760208
Ref: Library<41>-Footnote-322760252
Ref: Library<41>-Footnote-332760296
Ref: Library<41>-Footnote-342760340
Ref: Library<41>-Footnote-352760384
Ref: Library<41>-Footnote-362760428
Ref: Library<41>-Footnote-372760472
Ref: Library<41>-Footnote-382760516
Ref: Library<41>-Footnote-392760560
Ref: Library<41>-Footnote-402760604
Node: Documentation<36>2760648
Ref: whatsnew/changelog id3162760772
Ref: 10dd2760772
Ref: Documentation<36>-Footnote-12761626
Ref: Documentation<36>-Footnote-22761669
Ref: Documentation<36>-Footnote-32761712
Ref: Documentation<36>-Footnote-42761754
Ref: Documentation<36>-Footnote-52761797
Ref: Documentation<36>-Footnote-62761840
Node: Tests<31>2761883
Ref: whatsnew/changelog id3172762005
Ref: 10de2762005
Ref: Tests<31>-Footnote-12762666
Ref: Tests<31>-Footnote-22762709
Ref: Tests<31>-Footnote-32762752
Ref: Tests<31>-Footnote-42762795
Node: Build<29>2762838
Ref: whatsnew/changelog id3182762954
Ref: 10df2762954
Ref: Build<29>-Footnote-12763143
Node: Windows<31>2763186
Ref: whatsnew/changelog id3192763302
Ref: 10e02763302
Ref: Windows<31>-Footnote-12764252
Ref: Windows<31>-Footnote-22764295
Ref: Windows<31>-Footnote-32764338
Ref: Windows<31>-Footnote-42764381
Ref: Windows<31>-Footnote-52764424
Ref: Windows<31>-Footnote-62764467
Ref: Windows<31>-Footnote-72764510
Ref: Windows<31>-Footnote-82764553
Node: macOS<23>2764596
Ref: whatsnew/changelog id3202764711
Ref: 10e12764711
Ref: macOS<23>-Footnote-12765104
Node: IDLE<37>2765147
Ref: whatsnew/changelog id3212765266
Ref: 10e22765266
Ref: IDLE<37>-Footnote-12766756
Ref: IDLE<37>-Footnote-22766799
Ref: IDLE<37>-Footnote-32766842
Ref: IDLE<37>-Footnote-42766885
Ref: IDLE<37>-Footnote-52766928
Ref: IDLE<37>-Footnote-62766971
Ref: IDLE<37>-Footnote-72767014
Ref: IDLE<37>-Footnote-82767057
Node: Tools/Demos<20>2767100
Ref: whatsnew/changelog id3222767219
Ref: 10e32767219
Ref: Tools/Demos<20>-Footnote-12767639
Ref: Tools/Demos<20>-Footnote-22767682
Node: C API<24>2767725
Ref: whatsnew/changelog id3232767827
Ref: 10e42767827
Ref: C API<24>-Footnote-12768077
Node: Python 3 6 4 final2768120
Ref: whatsnew/changelog python-3-6-4-final2768284
Ref: 10e52768284
Node: Python 3 6 4 release candidate 12768433
Ref: whatsnew/changelog python-3-6-4-release-candidate-12768583
Ref: 10e62768583
Node: Core and Builtins<41>2768962
Ref: whatsnew/changelog id3242769072
Ref: 10e72769072
Ref: Core and Builtins<41>-Footnote-12773815
Ref: Core and Builtins<41>-Footnote-22773858
Ref: Core and Builtins<41>-Footnote-32773901
Ref: Core and Builtins<41>-Footnote-42773944
Ref: Core and Builtins<41>-Footnote-52773987
Ref: Core and Builtins<41>-Footnote-62774030
Ref: Core and Builtins<41>-Footnote-72774073
Ref: Core and Builtins<41>-Footnote-82774116
Ref: Core and Builtins<41>-Footnote-92774159
Ref: Core and Builtins<41>-Footnote-102774202
Ref: Core and Builtins<41>-Footnote-112774246
Ref: Core and Builtins<41>-Footnote-122774290
Ref: Core and Builtins<41>-Footnote-132774334
Ref: Core and Builtins<41>-Footnote-142774378
Ref: Core and Builtins<41>-Footnote-152774422
Ref: Core and Builtins<41>-Footnote-162774466
Ref: Core and Builtins<41>-Footnote-172774510
Ref: Core and Builtins<41>-Footnote-182774554
Ref: Core and Builtins<41>-Footnote-192774598
Ref: Core and Builtins<41>-Footnote-202774642
Ref: Core and Builtins<41>-Footnote-212774686
Ref: Core and Builtins<41>-Footnote-222774730
Ref: Core and Builtins<41>-Footnote-232774774
Ref: Core and Builtins<41>-Footnote-242774818
Node: Library<42>2774862
Ref: whatsnew/changelog id3252774998
Ref: 10e82774998
Ref: Library<42>-Footnote-12782333
Ref: Library<42>-Footnote-22782376
Ref: Library<42>-Footnote-32782419
Ref: Library<42>-Footnote-42782462
Ref: Library<42>-Footnote-52782505
Ref: Library<42>-Footnote-62782548
Ref: Library<42>-Footnote-72782591
Ref: Library<42>-Footnote-82782634
Ref: Library<42>-Footnote-92782677
Ref: Library<42>-Footnote-102782720
Ref: Library<42>-Footnote-112782764
Ref: Library<42>-Footnote-122782808
Ref: Library<42>-Footnote-132782852
Ref: Library<42>-Footnote-142782896
Ref: Library<42>-Footnote-152782940
Ref: Library<42>-Footnote-162782984
Ref: Library<42>-Footnote-172783027
Ref: Library<42>-Footnote-182783071
Ref: Library<42>-Footnote-192783115
Ref: Library<42>-Footnote-202783159
Ref: Library<42>-Footnote-212783203
Ref: Library<42>-Footnote-222783247
Ref: Library<42>-Footnote-232783291
Ref: Library<42>-Footnote-242783335
Ref: Library<42>-Footnote-252783379
Ref: Library<42>-Footnote-262783423
Ref: Library<42>-Footnote-272783467
Ref: Library<42>-Footnote-282783511
Ref: Library<42>-Footnote-292783555
Ref: Library<42>-Footnote-302783599
Ref: Library<42>-Footnote-312783643
Ref: Library<42>-Footnote-322783687
Ref: Library<42>-Footnote-332783731
Ref: Library<42>-Footnote-342783775
Ref: Library<42>-Footnote-352783819
Ref: Library<42>-Footnote-362783863
Ref: Library<42>-Footnote-372783907
Ref: Library<42>-Footnote-382783951
Ref: Library<42>-Footnote-392783995
Ref: Library<42>-Footnote-402784039
Ref: Library<42>-Footnote-412784083
Ref: Library<42>-Footnote-422784127
Ref: Library<42>-Footnote-432784171
Ref: Library<42>-Footnote-442784215
Ref: Library<42>-Footnote-452784259
Ref: Library<42>-Footnote-462784303
Ref: Library<42>-Footnote-472784347
Ref: Library<42>-Footnote-482784391
Ref: Library<42>-Footnote-492784435
Ref: Library<42>-Footnote-502784479
Ref: Library<42>-Footnote-512784523
Ref: Library<42>-Footnote-522784567
Node: Documentation<37>2784611
Ref: whatsnew/changelog id3262784735
Ref: 10e92784735
Ref: Documentation<37>-Footnote-12785224
Ref: Documentation<37>-Footnote-22785267
Ref: Documentation<37>-Footnote-32785310
Node: Tests<32>2785353
Ref: whatsnew/changelog id3272785475
Ref: 10ea2785475
Ref: Tests<32>-Footnote-12786147
Ref: Tests<32>-Footnote-22786190
Ref: Tests<32>-Footnote-32786233
Ref: Tests<32>-Footnote-42786276
Node: Build<30>2786319
Ref: whatsnew/changelog id3282786435
Ref: 10eb2786435
Ref: Build<30>-Footnote-12787339
Ref: Build<30>-Footnote-22787382
Ref: Build<30>-Footnote-32787425
Ref: Build<30>-Footnote-42787468
Ref: Build<30>-Footnote-52787511
Ref: Build<30>-Footnote-62787554
Ref: Build<30>-Footnote-72787597
Ref: Build<30>-Footnote-82787640
Ref: Build<30>-Footnote-92787683
Node: Windows<32>2787726
Ref: whatsnew/changelog id3292787842
Ref: 10ec2787842
Ref: Windows<32>-Footnote-12788160
Ref: Windows<32>-Footnote-22788202
Node: macOS<24>2788245
Ref: whatsnew/changelog id3302788360
Ref: 10ed2788360
Ref: macOS<24>-Footnote-12788494
Node: IDLE<38>2788537
Ref: whatsnew/changelog id3312788656
Ref: 10ee2788656
Ref: IDLE<38>-Footnote-12791993
Ref: IDLE<38>-Footnote-22792036
Ref: IDLE<38>-Footnote-32792079
Ref: IDLE<38>-Footnote-42792122
Ref: IDLE<38>-Footnote-52792165
Ref: IDLE<38>-Footnote-62792208
Ref: IDLE<38>-Footnote-72792251
Ref: IDLE<38>-Footnote-82792294
Ref: IDLE<38>-Footnote-92792337
Ref: IDLE<38>-Footnote-102792380
Ref: IDLE<38>-Footnote-112792424
Ref: IDLE<38>-Footnote-122792468
Ref: IDLE<38>-Footnote-132792512
Ref: IDLE<38>-Footnote-142792556
Node: Tools/Demos<21>2792602
Ref: whatsnew/changelog id3322792721
Ref: 10ef2792721
Ref: Tools/Demos<21>-Footnote-12793011
Node: C API<25>2793054
Ref: whatsnew/changelog id3332793156
Ref: 10f02793156
Ref: C API<25>-Footnote-12793884
Ref: C API<25>-Footnote-22793927
Ref: C API<25>-Footnote-32793970
Ref: C API<25>-Footnote-42794013
Node: Python 3 6 3 final2794056
Ref: whatsnew/changelog python-3-6-3-final2794220
Ref: 10f12794220
Node: Library<43>2794357
Ref: whatsnew/changelog id3342794441
Ref: 10f22794441
Ref: Library<43>-Footnote-12794654
Node: Build<31>2794697
Ref: whatsnew/changelog id3352794781
Ref: 10f42794781
Ref: Build<31>-Footnote-12795072
Ref: Build<31>-Footnote-22795115
Node: Python 3 6 3 release candidate 12795158
Ref: whatsnew/changelog python-3-6-3-release-candidate-12795308
Ref: 10f52795308
Node: Security<25>2795673
Ref: whatsnew/changelog id3362795784
Ref: 10f62795784
Ref: Security<25>-Footnote-12796090
Ref: Security<25>-Footnote-22796133
Node: Core and Builtins<42>2796176
Ref: whatsnew/changelog id3372796307
Ref: 10f72796307
Ref: Core and Builtins<42>-Footnote-12799854
Ref: Core and Builtins<42>-Footnote-22799897
Ref: Core and Builtins<42>-Footnote-32799940
Ref: Core and Builtins<42>-Footnote-42799983
Ref: Core and Builtins<42>-Footnote-52800026
Ref: Core and Builtins<42>-Footnote-62800069
Ref: Core and Builtins<42>-Footnote-72800112
Ref: Core and Builtins<42>-Footnote-82800155
Ref: Core and Builtins<42>-Footnote-92800198
Ref: Core and Builtins<42>-Footnote-102800241
Ref: Core and Builtins<42>-Footnote-112800285
Ref: Core and Builtins<42>-Footnote-122800329
Ref: Core and Builtins<42>-Footnote-132800373
Ref: Core and Builtins<42>-Footnote-142800417
Ref: Core and Builtins<42>-Footnote-152800461
Ref: Core and Builtins<42>-Footnote-162800505
Ref: Core and Builtins<42>-Footnote-172800549
Ref: Core and Builtins<42>-Footnote-182800593
Ref: Core and Builtins<42>-Footnote-192800637
Ref: Core and Builtins<42>-Footnote-202800681
Ref: Core and Builtins<42>-Footnote-212800725
Ref: Core and Builtins<42>-Footnote-222800769
Node: Library<44>2800813
Ref: whatsnew/changelog id3382800949
Ref: 10f82800949
Ref: Library<44>-Footnote-12806947
Ref: Library<44>-Footnote-22806990
Ref: Library<44>-Footnote-32807033
Ref: Library<44>-Footnote-42807076
Ref: Library<44>-Footnote-52807119
Ref: Library<44>-Footnote-62807162
Ref: Library<44>-Footnote-72807205
Ref: Library<44>-Footnote-82807248
Ref: Library<44>-Footnote-92807291
Ref: Library<44>-Footnote-102807334
Ref: Library<44>-Footnote-112807378
Ref: Library<44>-Footnote-122807422
Ref: Library<44>-Footnote-132807466
Ref: Library<44>-Footnote-142807510
Ref: Library<44>-Footnote-152807554
Ref: Library<44>-Footnote-162807597
Ref: Library<44>-Footnote-172807641
Ref: Library<44>-Footnote-182807685
Ref: Library<44>-Footnote-192807735
Ref: Library<44>-Footnote-202807779
Ref: Library<44>-Footnote-212807823
Ref: Library<44>-Footnote-222807867
Ref: Library<44>-Footnote-232807911
Ref: Library<44>-Footnote-242807955
Ref: Library<44>-Footnote-252807999
Ref: Library<44>-Footnote-262808043
Ref: Library<44>-Footnote-272808087
Ref: Library<44>-Footnote-282808131
Ref: Library<44>-Footnote-292808175
Ref: Library<44>-Footnote-302808219
Ref: Library<44>-Footnote-312808263
Ref: Library<44>-Footnote-322808307
Ref: Library<44>-Footnote-332808351
Ref: Library<44>-Footnote-342808395
Ref: Library<44>-Footnote-352808439
Ref: Library<44>-Footnote-362808483
Ref: Library<44>-Footnote-372808527
Ref: Library<44>-Footnote-382808571
Ref: Library<44>-Footnote-392808615
Ref: Library<44>-Footnote-402808659
Ref: Library<44>-Footnote-412808703
Ref: Library<44>-Footnote-422808747
Node: Documentation<38>2808791
Ref: whatsnew/changelog id3392808915
Ref: 10f92808915
Ref: Documentation<38>-Footnote-12809338
Ref: Documentation<38>-Footnote-22809381
Ref: Documentation<38>-Footnote-32809424
Node: Tests<33>2809467
Ref: whatsnew/changelog id3402809589
Ref: 10fa2809589
Ref: Tests<33>-Footnote-12810294
Ref: Tests<33>-Footnote-22810337
Ref: Tests<33>-Footnote-32810380
Ref: Tests<33>-Footnote-42810423
Node: Build<32>2810466
Ref: whatsnew/changelog id3412810582
Ref: 10fb2810582
Ref: Build<32>-Footnote-12810757
Node: Windows<33>2810800
Ref: whatsnew/changelog id3422810915
Ref: 10fc2810915
Ref: Windows<33>-Footnote-12811423
Ref: Windows<33>-Footnote-22811466
Ref: Windows<33>-Footnote-32811509
Ref: Windows<33>-Footnote-42811552
Node: IDLE<39>2811595
Ref: whatsnew/changelog id3432811716
Ref: 10fd2811716
Ref: IDLE<39>-Footnote-12820565
Ref: IDLE<39>-Footnote-22820608
Ref: IDLE<39>-Footnote-32820651
Ref: IDLE<39>-Footnote-42820694
Ref: IDLE<39>-Footnote-52820737
Ref: IDLE<39>-Footnote-62820780
Ref: IDLE<39>-Footnote-72820823
Ref: IDLE<39>-Footnote-82820866
Ref: IDLE<39>-Footnote-92820909
Ref: IDLE<39>-Footnote-102820952
Ref: IDLE<39>-Footnote-112820996
Ref: IDLE<39>-Footnote-122821040
Ref: IDLE<39>-Footnote-132821084
Ref: IDLE<39>-Footnote-142821128
Ref: IDLE<39>-Footnote-152821172
Ref: IDLE<39>-Footnote-162821216
Ref: IDLE<39>-Footnote-172821260
Ref: IDLE<39>-Footnote-182821304
Ref: IDLE<39>-Footnote-192821348
Ref: IDLE<39>-Footnote-202821392
Ref: IDLE<39>-Footnote-212821436
Ref: IDLE<39>-Footnote-222821480
Ref: IDLE<39>-Footnote-232821524
Ref: IDLE<39>-Footnote-242821568
Ref: IDLE<39>-Footnote-252821612
Ref: IDLE<39>-Footnote-262821656
Ref: IDLE<39>-Footnote-272821700
Ref: IDLE<39>-Footnote-282821744
Ref: IDLE<39>-Footnote-292821788
Ref: IDLE<39>-Footnote-302821832
Ref: IDLE<39>-Footnote-312821876
Ref: IDLE<39>-Footnote-322821920
Ref: IDLE<39>-Footnote-332821964
Ref: IDLE<39>-Footnote-342822008
Ref: IDLE<39>-Footnote-352822051
Ref: IDLE<39>-Footnote-362822095
Ref: IDLE<39>-Footnote-372822139
Ref: IDLE<39>-Footnote-382822183
Ref: IDLE<39>-Footnote-392822227
Ref: IDLE<39>-Footnote-402822271
Ref: IDLE<39>-Footnote-412822315
Ref: IDLE<39>-Footnote-422822359
Ref: IDLE<39>-Footnote-432822403
Node: Tools/Demos<22>2822446
Ref: whatsnew/changelog id3442822547
Ref: 10fe2822547
Ref: Tools/Demos<22>-Footnote-12823105
Ref: Tools/Demos<22>-Footnote-22823148
Node: Python 3 6 2 final2823197
Ref: whatsnew/changelog python-3-6-2-final2823361
Ref: 10ff2823361
Node: Python 3 6 2 release candidate 22823482
Ref: whatsnew/changelog python-3-6-2-release-candidate-22823646
Ref: 11002823646
Node: Security<26>2823793
Ref: whatsnew/changelog id3452823874
Ref: 11012823874
Ref: Security<26>-Footnote-12824981
Ref: Security<26>-Footnote-22825024
Ref: Security<26>-Footnote-32825067
Node: Python 3 6 2 release candidate 12825110
Ref: whatsnew/changelog python-3-6-2-release-candidate-12825274
Ref: 11022825274
Node: Core and Builtins<43>2825683
Ref: whatsnew/changelog id3462825793
Ref: 11032825793
Ref: Core and Builtins<43>-Footnote-12827786
Ref: Core and Builtins<43>-Footnote-22827829
Ref: Core and Builtins<43>-Footnote-32827872
Ref: Core and Builtins<43>-Footnote-42827915
Ref: Core and Builtins<43>-Footnote-52827958
Ref: Core and Builtins<43>-Footnote-62828001
Ref: Core and Builtins<43>-Footnote-72828044
Ref: Core and Builtins<43>-Footnote-82828087
Ref: Core and Builtins<43>-Footnote-92828130
Ref: Core and Builtins<43>-Footnote-102828173
Ref: Core and Builtins<43>-Footnote-112828217
Ref: Core and Builtins<43>-Footnote-122828261
Ref: Core and Builtins<43>-Footnote-132828305
Ref: Core and Builtins<43>-Footnote-142828349
Ref: Core and Builtins<43>-Footnote-152828393
Node: Library<45>2828437
Ref: whatsnew/changelog id3472828568
Ref: 11042828568
Ref: Library<45>-Footnote-12829702
Ref: Library<45>-Footnote-22829745
Ref: Library<45>-Footnote-32829788
Ref: Library<45>-Footnote-42829831
Ref: Library<45>-Footnote-52829874
Ref: Library<45>-Footnote-62829917
Ref: Library<45>-Footnote-72829960
Ref: Library<45>-Footnote-82830003
Node: Security<27>2830046
Ref: whatsnew/changelog id3482830167
Ref: 11052830167
Ref: Security<27>-Footnote-12830434
Node: Library<46>2830477
Ref: whatsnew/changelog id3492830595
Ref: 11062830595
Ref: Library<46>-Footnote-12837944
Ref: Library<46>-Footnote-22837987
Ref: Library<46>-Footnote-32838030
Ref: Library<46>-Footnote-42838073
Ref: Library<46>-Footnote-52838116
Ref: Library<46>-Footnote-62838159
Ref: Library<46>-Footnote-72838202
Ref: Library<46>-Footnote-82838245
Ref: Library<46>-Footnote-92838288
Ref: Library<46>-Footnote-102838331
Ref: Library<46>-Footnote-112838375
Ref: Library<46>-Footnote-122838419
Ref: Library<46>-Footnote-132838463
Ref: Library<46>-Footnote-142838507
Ref: Library<46>-Footnote-152838551
Ref: Library<46>-Footnote-162838595
Ref: Library<46>-Footnote-172838639
Ref: Library<46>-Footnote-182838683
Ref: Library<46>-Footnote-192838727
Ref: Library<46>-Footnote-202838771
Ref: Library<46>-Footnote-212838815
Ref: Library<46>-Footnote-222838859
Ref: Library<46>-Footnote-232838903
Ref: Library<46>-Footnote-242838947
Ref: Library<46>-Footnote-252838991
Ref: Library<46>-Footnote-262839035
Ref: Library<46>-Footnote-272839079
Ref: Library<46>-Footnote-282839123
Ref: Library<46>-Footnote-292839167
Ref: Library<46>-Footnote-302839211
Ref: Library<46>-Footnote-312839255
Ref: Library<46>-Footnote-322839299
Ref: Library<46>-Footnote-332839343
Ref: Library<46>-Footnote-342839387
Ref: Library<46>-Footnote-352839431
Ref: Library<46>-Footnote-362839475
Ref: Library<46>-Footnote-372839519
Ref: Library<46>-Footnote-382839563
Ref: Library<46>-Footnote-392839607
Ref: Library<46>-Footnote-402839651
Ref: Library<46>-Footnote-412839695
Ref: Library<46>-Footnote-422839739
Ref: Library<46>-Footnote-432839783
Ref: Library<46>-Footnote-442839827
Ref: Library<46>-Footnote-452839871
Ref: Library<46>-Footnote-462839915
Ref: Library<46>-Footnote-472839959
Ref: Library<46>-Footnote-482840002
Ref: Library<46>-Footnote-492840046
Ref: Library<46>-Footnote-502840090
Ref: Library<46>-Footnote-512840134
Ref: Library<46>-Footnote-522840178
Node: IDLE<40>2840222
Ref: whatsnew/changelog id3502840337
Ref: 11072840337
Ref: IDLE<40>-Footnote-12841342
Ref: IDLE<40>-Footnote-22841385
Ref: IDLE<40>-Footnote-32841428
Ref: IDLE<40>-Footnote-42841471
Ref: IDLE<40>-Footnote-52841514
Ref: IDLE<40>-Footnote-62841557
Node: C API<26>2841600
Ref: whatsnew/changelog id3512841713
Ref: 11082841713
Ref: C API<26>-Footnote-12841901
Node: Build<33>2841944
Ref: whatsnew/changelog id3522842066
Ref: 11092842066
Ref: Build<33>-Footnote-12842875
Ref: Build<33>-Footnote-22842918
Ref: Build<33>-Footnote-32842961
Ref: Build<33>-Footnote-42843004
Ref: Build<33>-Footnote-52843047
Node: Documentation<39>2843090
Ref: whatsnew/changelog id3532843218
Ref: 110a2843218
Ref: Documentation<39>-Footnote-12843947
Ref: Documentation<39>-Footnote-22843990
Ref: Documentation<39>-Footnote-32844033
Node: Tools/Demos<23>2844076
Ref: whatsnew/changelog id3542844204
Ref: 110b2844204
Ref: Tools/Demos<23>-Footnote-12844394
Node: Tests<34>2844437
Ref: whatsnew/changelog id3552844559
Ref: 110c2844559
Ref: Tests<34>-Footnote-12845218
Ref: Tests<34>-Footnote-22845261
Node: Windows<34>2845304
Ref: whatsnew/changelog id3562845402
Ref: 110d2845402
Ref: Windows<34>-Footnote-12845846
Ref: Windows<34>-Footnote-22845889
Node: Python 3 6 1 final2845932
Ref: whatsnew/changelog python-3-6-1-final2846096
Ref: 110e2846096
Node: Core and Builtins<44>2846253
Ref: whatsnew/changelog id3572846347
Ref: 110f2846347
Ref: Core and Builtins<44>-Footnote-12846966
Ref: Core and Builtins<44>-Footnote-22847009
Node: Build<34>2847052
Ref: whatsnew/changelog id3582847146
Ref: 11102847146
Ref: Build<34>-Footnote-12847328
Node: Python 3 6 1 release candidate 12847371
Ref: whatsnew/changelog python-3-6-1-release-candidate-12847521
Ref: 11112847521
Node: Core and Builtins<45>2847848
Ref: whatsnew/changelog id3592847958
Ref: 11122847958
Ref: Core and Builtins<45>-Footnote-12850790
Ref: Core and Builtins<45>-Footnote-22850833
Ref: Core and Builtins<45>-Footnote-32850876
Ref: Core and Builtins<45>-Footnote-42850919
Ref: Core and Builtins<45>-Footnote-52850962
Ref: Core and Builtins<45>-Footnote-62851005
Ref: Core and Builtins<45>-Footnote-72851048
Ref: Core and Builtins<45>-Footnote-82851091
Ref: Core and Builtins<45>-Footnote-92851134
Ref: Core and Builtins<45>-Footnote-102851177
Ref: Core and Builtins<45>-Footnote-112851221
Ref: Core and Builtins<45>-Footnote-122851265
Ref: Core and Builtins<45>-Footnote-132851309
Ref: Core and Builtins<45>-Footnote-142851353
Ref: Core and Builtins<45>-Footnote-152851397
Ref: Core and Builtins<45>-Footnote-162851441
Ref: Core and Builtins<45>-Footnote-172851485
Ref: Core and Builtins<45>-Footnote-182851529
Ref: Core and Builtins<45>-Footnote-192851573
Ref: Core and Builtins<45>-Footnote-202851617
Ref: Core and Builtins<45>-Footnote-212851661
Ref: Core and Builtins<45>-Footnote-222851705
Node: Library<47>2851749
Ref: whatsnew/changelog id3602851876
Ref: 11132851876
Ref: Library<47>-Footnote-12857515
Ref: Library<47>-Footnote-22857558
Ref: Library<47>-Footnote-32857601
Ref: Library<47>-Footnote-42857644
Ref: Library<47>-Footnote-52857687
Ref: Library<47>-Footnote-62857730
Ref: Library<47>-Footnote-72857773
Ref: Library<47>-Footnote-82857816
Ref: Library<47>-Footnote-92857859
Ref: Library<47>-Footnote-102857902
Ref: Library<47>-Footnote-112857946
Ref: Library<47>-Footnote-122857990
Ref: Library<47>-Footnote-132858034
Ref: Library<47>-Footnote-142858078
Ref: Library<47>-Footnote-152858122
Ref: Library<47>-Footnote-162858166
Ref: Library<47>-Footnote-172858210
Ref: Library<47>-Footnote-182858254
Ref: Library<47>-Footnote-192858298
Ref: Library<47>-Footnote-202858342
Ref: Library<47>-Footnote-212858386
Ref: Library<47>-Footnote-222858430
Ref: Library<47>-Footnote-232858474
Ref: Library<47>-Footnote-242858518
Ref: Library<47>-Footnote-252858562
Ref: Library<47>-Footnote-262858606
Ref: Library<47>-Footnote-272858650
Ref: Library<47>-Footnote-282858700
Ref: Library<47>-Footnote-292858744
Ref: Library<47>-Footnote-302858788
Ref: Library<47>-Footnote-312858832
Ref: Library<47>-Footnote-322858876
Ref: Library<47>-Footnote-332858920
Ref: Library<47>-Footnote-342858964
Ref: Library<47>-Footnote-352859008
Ref: Library<47>-Footnote-362859051
Ref: Library<47>-Footnote-372859095
Ref: Library<47>-Footnote-382859139
Ref: Library<47>-Footnote-392859183
Ref: Library<47>-Footnote-402859227
Ref: Library<47>-Footnote-412859271
Ref: Library<47>-Footnote-422859315
Ref: Library<47>-Footnote-432859359
Ref: Library<47>-Footnote-442859403
Node: IDLE<41>2859447
Ref: whatsnew/changelog id3612859564
Ref: 11142859564
Ref: IDLE<41>-Footnote-12859853
Ref: IDLE<41>-Footnote-22859896
Node: Windows<35>2859939
Ref: whatsnew/changelog id3622860054
Ref: 11152860054
Ref: Windows<35>-Footnote-12860701
Ref: Windows<35>-Footnote-22860744
Ref: Windows<35>-Footnote-32860787
Ref: Windows<35>-Footnote-42860830
Ref: Windows<35>-Footnote-52860873
Ref: Windows<35>-Footnote-62860922
Ref: Windows<35>-Footnote-72860965
Ref: Windows<35>-Footnote-82861008
Node: C API<27>2861051
Ref: whatsnew/changelog id3632861175
Ref: 11162861175
Ref: C API<27>-Footnote-12862001
Ref: C API<27>-Footnote-22862044
Ref: C API<27>-Footnote-32862087
Node: Documentation<40>2862130
Ref: whatsnew/changelog id3642862252
Ref: 11172862252
Ref: Documentation<40>-Footnote-12862789
Ref: Documentation<40>-Footnote-22862832
Ref: Documentation<40>-Footnote-32862875
Ref: Documentation<40>-Footnote-42862918
Node: Tests<35>2862961
Ref: whatsnew/changelog id3652863083
Ref: 11182863083
Ref: Tests<35>-Footnote-12864068
Ref: Tests<35>-Footnote-22864111
Ref: Tests<35>-Footnote-32864154
Ref: Tests<35>-Footnote-42864197
Ref: Tests<35>-Footnote-52864240
Node: Build<35>2864283
Ref: whatsnew/changelog id3662864379
Ref: 11192864379
Ref: Build<35>-Footnote-12865640
Ref: Build<35>-Footnote-22865683
Ref: Build<35>-Footnote-32865726
Ref: Build<35>-Footnote-42865769
Ref: Build<35>-Footnote-52865812
Ref: Build<35>-Footnote-62865855
Ref: Build<35>-Footnote-72865898
Ref: Build<35>-Footnote-82865941
Ref: Build<35>-Footnote-92865984
Ref: Build<35>-Footnote-102866027
Node: Python 3 6 0 final2866071
Ref: whatsnew/changelog python-3-6-0-final2866235
Ref: 111a2866235
Node: Python 3 6 0 release candidate 22866356
Ref: whatsnew/changelog python-3-6-0-release-candidate-22866520
Ref: 111b2866520
Node: Core and Builtins<46>2866761
Ref: whatsnew/changelog id3672866875
Ref: 111c2866875
Ref: Core and Builtins<46>-Footnote-12867260
Ref: Core and Builtins<46>-Footnote-22867303
Node: Tools/Demos<24>2867346
Ref: whatsnew/changelog id3682867480
Ref: 111d2867480
Ref: Tools/Demos<24>-Footnote-12867614
Node: Windows<36>2867657
Ref: whatsnew/changelog id3692867779
Ref: 111e2867779
Ref: Windows<36>-Footnote-12867905
Node: Build<36>2867948
Ref: whatsnew/changelog id3702868046
Ref: 111f2868046
Ref: Build<36>-Footnote-12868201
Node: Python 3 6 0 release candidate 12868244
Ref: whatsnew/changelog python-3-6-0-release-candidate-12868409
Ref: 11202868409
Node: Core and Builtins<47>2868686
Ref: whatsnew/changelog id3712868796
Ref: 11212868796
Ref: Core and Builtins<47>-Footnote-12869605
Ref: Core and Builtins<47>-Footnote-22869648
Ref: Core and Builtins<47>-Footnote-32869691
Ref: Core and Builtins<47>-Footnote-42869734
Node: Library<48>2869777
Ref: whatsnew/changelog id3722869905
Ref: 11222869905
Ref: Library<48>-Footnote-12870944
Ref: Library<48>-Footnote-22870987
Ref: Library<48>-Footnote-32871030
Ref: Library<48>-Footnote-42871073
Ref: Library<48>-Footnote-52871116
Ref: Library<48>-Footnote-62871159
Node: C API<28>2871202
Ref: whatsnew/changelog id3732871326
Ref: 11232871326
Ref: C API<28>-Footnote-12871484
Node: Documentation<41>2871527
Ref: whatsnew/changelog id3742871655
Ref: 11242871655
Ref: Documentation<41>-Footnote-12871995
Ref: Documentation<41>-Footnote-22872038
Node: Tools/Demos<25>2872087
Ref: whatsnew/changelog id3752872197
Ref: 11252872197
Ref: Tools/Demos<25>-Footnote-12872363
Node: Python 3 6 0 beta 42872406
Ref: whatsnew/changelog python-3-6-0-beta-42872558
Ref: 11262872558
Node: Core and Builtins<48>2872797
Ref: whatsnew/changelog id3762872894
Ref: 11272872894
Ref: Core and Builtins<48>-Footnote-12874446
Ref: Core and Builtins<48>-Footnote-22874489
Ref: Core and Builtins<48>-Footnote-32874532
Ref: Core and Builtins<48>-Footnote-42874575
Ref: Core and Builtins<48>-Footnote-52874618
Ref: Core and Builtins<48>-Footnote-62874661
Ref: Core and Builtins<48>-Footnote-72874704
Ref: Core and Builtins<48>-Footnote-82874747
Ref: Core and Builtins<48>-Footnote-92874790
Ref: Core and Builtins<48>-Footnote-102874833
Ref: Core and Builtins<48>-Footnote-112874877
Node: Library<49>2874921
Ref: whatsnew/changelog id3772875044
Ref: 11282875044
Ref: Library<49>-Footnote-12877046
Ref: Library<49>-Footnote-22877089
Ref: Library<49>-Footnote-32877132
Ref: Library<49>-Footnote-42877175
Ref: Library<49>-Footnote-52877218
Ref: Library<49>-Footnote-62877261
Ref: Library<49>-Footnote-72877304
Ref: Library<49>-Footnote-82877347
Ref: Library<49>-Footnote-92877390
Ref: Library<49>-Footnote-102877433
Ref: Library<49>-Footnote-112877477
Ref: Library<49>-Footnote-122877521
Ref: Library<49>-Footnote-132877565
Ref: Library<49>-Footnote-142877609
Ref: Library<49>-Footnote-152877653
Ref: Library<49>-Footnote-162877697
Ref: Library<49>-Footnote-172877741
Ref: Library<49>-Footnote-182877785
Node: Documentation<42>2877829
Ref: whatsnew/changelog id3782877940
Ref: 11292877940
Ref: Documentation<42>-Footnote-12878091
Node: Tests<36>2878134
Ref: whatsnew/changelog id3792878243
Ref: 112a2878243
Ref: Tests<36>-Footnote-12878505
Ref: Tests<36>-Footnote-22878548
Node: Build<37>2878591
Ref: whatsnew/changelog id3802878674
Ref: 112b2878674
Ref: Build<37>-Footnote-12879037
Ref: Build<37>-Footnote-22879080
Ref: Build<37>-Footnote-32879123
Node: Python 3 6 0 beta 32879166
Ref: whatsnew/changelog python-3-6-0-beta-32879305
Ref: 112c2879305
Node: Core and Builtins<49>2879532
Ref: whatsnew/changelog id3812879629
Ref: 112d2879629
Ref: Core and Builtins<49>-Footnote-12880532
Ref: Core and Builtins<49>-Footnote-22880575
Ref: Core and Builtins<49>-Footnote-32880618
Ref: Core and Builtins<49>-Footnote-42880661
Ref: Core and Builtins<49>-Footnote-52880704
Ref: Core and Builtins<49>-Footnote-62880747
Ref: Core and Builtins<49>-Footnote-72880790
Node: Library<50>2880833
Ref: whatsnew/changelog id3822880950
Ref: 112e2880950
Ref: Library<50>-Footnote-12883982
Ref: Library<50>-Footnote-22884025
Ref: Library<50>-Footnote-32884068
Ref: Library<50>-Footnote-42884111
Ref: Library<50>-Footnote-52884154
Ref: Library<50>-Footnote-62884197
Ref: Library<50>-Footnote-72884240
Ref: Library<50>-Footnote-82884283
Ref: Library<50>-Footnote-92884326
Ref: Library<50>-Footnote-102884369
Ref: Library<50>-Footnote-112884413
Ref: Library<50>-Footnote-122884457
Ref: Library<50>-Footnote-132884501
Ref: Library<50>-Footnote-142884545
Ref: Library<50>-Footnote-152884589
Ref: Library<50>-Footnote-162884633
Ref: Library<50>-Footnote-172884677
Ref: Library<50>-Footnote-182884721
Ref: Library<50>-Footnote-192884765
Ref: Library<50>-Footnote-202884809
Ref: Library<50>-Footnote-212884853
Ref: Library<50>-Footnote-222884897
Ref: Library<50>-Footnote-232884941
Ref: Library<50>-Footnote-242884985
Node: Windows<37>2885029
Ref: whatsnew/changelog id3832885134
Ref: 112f2885134
Ref: Windows<37>-Footnote-12885278
Node: Build<38>2885321
Ref: whatsnew/changelog id3842885424
Ref: 11302885424
Ref: Build<38>-Footnote-12885743
Ref: Build<38>-Footnote-22885786
Ref: Build<38>-Footnote-32885829
Node: Tests<37>2885872
Ref: whatsnew/changelog id3852885955
Ref: 11312885955
Ref: Tests<37>-Footnote-12886214
Ref: Tests<37>-Footnote-22886257
Node: Python 3 6 0 beta 22886300
Ref: whatsnew/changelog python-3-6-0-beta-22886439
Ref: 11322886439
Node: Core and Builtins<50>2886686
Ref: whatsnew/changelog id3862886783
Ref: 11332886783
Ref: Core and Builtins<50>-Footnote-12889523
Ref: Core and Builtins<50>-Footnote-22889566
Ref: Core and Builtins<50>-Footnote-32889609
Ref: Core and Builtins<50>-Footnote-42889652
Ref: Core and Builtins<50>-Footnote-52889695
Ref: Core and Builtins<50>-Footnote-62889738
Ref: Core and Builtins<50>-Footnote-72889781
Ref: Core and Builtins<50>-Footnote-82889824
Ref: Core and Builtins<50>-Footnote-92889867
Ref: Core and Builtins<50>-Footnote-102889910
Ref: Core and Builtins<50>-Footnote-112889954
Ref: Core and Builtins<50>-Footnote-122889998
Ref: Core and Builtins<50>-Footnote-132890042
Ref: Core and Builtins<50>-Footnote-142890086
Ref: Core and Builtins<50>-Footnote-152890130
Ref: Core and Builtins<50>-Footnote-162890174
Ref: Core and Builtins<50>-Footnote-172890218
Ref: Core and Builtins<50>-Footnote-182890262
Ref: Core and Builtins<50>-Footnote-192890306
Ref: Core and Builtins<50>-Footnote-202890350
Ref: Core and Builtins<50>-Footnote-212890394
Ref: Core and Builtins<50>-Footnote-222890438
Ref: Core and Builtins<50>-Footnote-232890482
Node: Library<51>2890526
Ref: whatsnew/changelog id3872890643
Ref: 11342890643
Ref: Library<51>-Footnote-12896429
Ref: Library<51>-Footnote-22896472
Ref: Library<51>-Footnote-32896515
Ref: Library<51>-Footnote-42896558
Ref: Library<51>-Footnote-52896601
Ref: Library<51>-Footnote-62896644
Ref: Library<51>-Footnote-72896687
Ref: Library<51>-Footnote-82896730
Ref: Library<51>-Footnote-92896773
Ref: Library<51>-Footnote-102896816
Ref: Library<51>-Footnote-112896860
Ref: Library<51>-Footnote-122896904
Ref: Library<51>-Footnote-132896948
Ref: Library<51>-Footnote-142896992
Ref: Library<51>-Footnote-152897036
Ref: Library<51>-Footnote-162897080
Ref: Library<51>-Footnote-172897124
Ref: Library<51>-Footnote-182897168
Ref: Library<51>-Footnote-192897212
Ref: Library<51>-Footnote-202897256
Ref: Library<51>-Footnote-212897300
Ref: Library<51>-Footnote-222897344
Ref: Library<51>-Footnote-232897388
Ref: Library<51>-Footnote-242897432
Ref: Library<51>-Footnote-252897476
Ref: Library<51>-Footnote-262897520
Ref: Library<51>-Footnote-272897564
Ref: Library<51>-Footnote-282897608
Ref: Library<51>-Footnote-292897652
Ref: Library<51>-Footnote-302897696
Ref: Library<51>-Footnote-312897740
Ref: Library<51>-Footnote-322897784
Ref: Library<51>-Footnote-332897828
Ref: Library<51>-Footnote-342897872
Ref: Library<51>-Footnote-352897916
Ref: Library<51>-Footnote-362897960
Ref: Library<51>-Footnote-372898004
Ref: Library<51>-Footnote-382898048
Ref: Library<51>-Footnote-392898092
Ref: Library<51>-Footnote-402898136
Ref: Library<51>-Footnote-412898180
Ref: Library<51>-Footnote-422898224
Ref: Library<51>-Footnote-432898268
Ref: Library<51>-Footnote-442898312
Ref: Library<51>-Footnote-452898356
Ref: Library<51>-Footnote-462898400
Ref: Library<51>-Footnote-472898444
Ref: Library<51>-Footnote-482898488
Node: Windows<38>2898532
Ref: whatsnew/changelog id3882898637
Ref: 11352898637
Ref: Windows<38>-Footnote-12899448
Ref: Windows<38>-Footnote-22899491
Ref: Windows<38>-Footnote-32899534
Ref: Windows<38>-Footnote-42899577
Ref: Windows<38>-Footnote-52899620
Ref: Windows<38>-Footnote-62899663
Ref: Windows<38>-Footnote-72899706
Ref: Windows<38>-Footnote-82899749
Ref: Windows<38>-Footnote-92899792
Ref: Windows<38>-Footnote-102899835
Node: C API<29>2899879
Ref: whatsnew/changelog id3892899982
Ref: 11362899982
Ref: C API<29>-Footnote-12900236
Node: Build<39>2900279
Ref: whatsnew/changelog id3902900380
Ref: 11372900380
Ref: Build<39>-Footnote-12900806
Ref: Build<39>-Footnote-22900849
Ref: Build<39>-Footnote-32900892
Node: Tests<38>2900935
Ref: whatsnew/changelog id3912901018
Ref: 11382901018
Ref: Tests<38>-Footnote-12901155
Node: Python 3 6 0 beta 12901198
Ref: whatsnew/changelog python-3-6-0-beta-12901338
Ref: 11392901338
Node: Core and Builtins<51>2901635
Ref: whatsnew/changelog id3922901732
Ref: 113a2901732
Ref: Core and Builtins<51>-Footnote-12907921
Ref: Core and Builtins<51>-Footnote-22907964
Ref: Core and Builtins<51>-Footnote-32908007
Ref: Core and Builtins<51>-Footnote-42908050
Ref: Core and Builtins<51>-Footnote-52908099
Ref: Core and Builtins<51>-Footnote-62908142
Ref: Core and Builtins<51>-Footnote-72908185
Ref: Core and Builtins<51>-Footnote-82908228
Ref: Core and Builtins<51>-Footnote-92908271
Ref: Core and Builtins<51>-Footnote-102908314
Ref: Core and Builtins<51>-Footnote-112908358
Ref: Core and Builtins<51>-Footnote-122908402
Ref: Core and Builtins<51>-Footnote-132908446
Ref: Core and Builtins<51>-Footnote-142908496
Ref: Core and Builtins<51>-Footnote-152908540
Ref: Core and Builtins<51>-Footnote-162908584
Ref: Core and Builtins<51>-Footnote-172908634
Ref: Core and Builtins<51>-Footnote-182908678
Ref: Core and Builtins<51>-Footnote-192908728
Ref: Core and Builtins<51>-Footnote-202908772
Ref: Core and Builtins<51>-Footnote-212908816
Ref: Core and Builtins<51>-Footnote-222908860
Ref: Core and Builtins<51>-Footnote-232908904
Ref: Core and Builtins<51>-Footnote-242908948
Ref: Core and Builtins<51>-Footnote-252908992
Ref: Core and Builtins<51>-Footnote-262909036
Ref: Core and Builtins<51>-Footnote-272909080
Ref: Core and Builtins<51>-Footnote-282909130
Ref: Core and Builtins<51>-Footnote-292909174
Ref: Core and Builtins<51>-Footnote-302909218
Ref: Core and Builtins<51>-Footnote-312909262
Ref: Core and Builtins<51>-Footnote-322909306
Ref: Core and Builtins<51>-Footnote-332909350
Ref: Core and Builtins<51>-Footnote-342909394
Ref: Core and Builtins<51>-Footnote-352909438
Ref: Core and Builtins<51>-Footnote-362909482
Ref: Core and Builtins<51>-Footnote-372909526
Ref: Core and Builtins<51>-Footnote-382909570
Ref: Core and Builtins<51>-Footnote-392909614
Ref: Core and Builtins<51>-Footnote-402909658
Ref: Core and Builtins<51>-Footnote-412909702
Ref: Core and Builtins<51>-Footnote-422909746
Ref: Core and Builtins<51>-Footnote-432909790
Ref: Core and Builtins<51>-Footnote-442909834
Ref: Core and Builtins<51>-Footnote-452909878
Ref: Core and Builtins<51>-Footnote-462909922
Ref: Core and Builtins<51>-Footnote-472909972
Node: Library<52>2910016
Ref: whatsnew/changelog id3932910130
Ref: 113b2910130
Ref: Library<52>-Footnote-12921090
Ref: Library<52>-Footnote-22921133
Ref: Library<52>-Footnote-32921176
Ref: Library<52>-Footnote-42921219
Ref: Library<52>-Footnote-52921262
Ref: Library<52>-Footnote-62921305
Ref: Library<52>-Footnote-72921348
Ref: Library<52>-Footnote-82921391
Ref: Library<52>-Footnote-92921434
Ref: Library<52>-Footnote-102921477
Ref: Library<52>-Footnote-112921521
Ref: Library<52>-Footnote-122921565
Ref: Library<52>-Footnote-132921609
Ref: Library<52>-Footnote-142921653
Ref: Library<52>-Footnote-152921697
Ref: Library<52>-Footnote-162921741
Ref: Library<52>-Footnote-172921785
Ref: Library<52>-Footnote-182921831
Ref: Library<52>-Footnote-192921875
Ref: Library<52>-Footnote-202921919
Ref: Library<52>-Footnote-212921963
Ref: Library<52>-Footnote-222922007
Ref: Library<52>-Footnote-232922051
Ref: Library<52>-Footnote-242922095
Ref: Library<52>-Footnote-252922139
Ref: Library<52>-Footnote-262922184
Ref: Library<52>-Footnote-272922228
Ref: Library<52>-Footnote-282922272
Ref: Library<52>-Footnote-292922316
Ref: Library<52>-Footnote-302922360
Ref: Library<52>-Footnote-312922404
Ref: Library<52>-Footnote-322922448
Ref: Library<52>-Footnote-332922492
Ref: Library<52>-Footnote-342922536
Ref: Library<52>-Footnote-352922580
Ref: Library<52>-Footnote-362922624
Ref: Library<52>-Footnote-372922668
Ref: Library<52>-Footnote-382922712
Ref: Library<52>-Footnote-392922756
Ref: Library<52>-Footnote-402922800
Ref: Library<52>-Footnote-412922844
Ref: Library<52>-Footnote-422922888
Ref: Library<52>-Footnote-432922938
Ref: Library<52>-Footnote-442922982
Ref: Library<52>-Footnote-452923032
Ref: Library<52>-Footnote-462923076
Ref: Library<52>-Footnote-472923120
Ref: Library<52>-Footnote-482923164
Ref: Library<52>-Footnote-492923208
Ref: Library<52>-Footnote-502923252
Ref: Library<52>-Footnote-512923296
Ref: Library<52>-Footnote-522923340
Ref: Library<52>-Footnote-532923384
Ref: Library<52>-Footnote-542923428
Ref: Library<52>-Footnote-552923472
Ref: Library<52>-Footnote-562923516
Ref: Library<52>-Footnote-572923560
Ref: Library<52>-Footnote-582923604
Ref: Library<52>-Footnote-592923648
Ref: Library<52>-Footnote-602923692
Ref: Library<52>-Footnote-612923736
Ref: Library<52>-Footnote-622923780
Ref: Library<52>-Footnote-632923824
Ref: Library<52>-Footnote-642923868
Ref: Library<52>-Footnote-652923912
Ref: Library<52>-Footnote-662923956
Ref: Library<52>-Footnote-672924000
Ref: Library<52>-Footnote-682924044
Ref: Library<52>-Footnote-692924088
Ref: Library<52>-Footnote-702924132
Ref: Library<52>-Footnote-712924176
Ref: Library<52>-Footnote-722924220
Ref: Library<52>-Footnote-732924264
Ref: Library<52>-Footnote-742924308
Ref: Library<52>-Footnote-752924352
Ref: Library<52>-Footnote-762924395
Ref: Library<52>-Footnote-772924438
Ref: Library<52>-Footnote-782924482
Ref: Library<52>-Footnote-792924526
Ref: Library<52>-Footnote-802924569
Ref: Library<52>-Footnote-812924613
Node: IDLE<42>2924657
Ref: whatsnew/changelog id3942924759
Ref: 113c2924759
Ref: IDLE<42>-Footnote-12925525
Ref: IDLE<42>-Footnote-22925568
Ref: IDLE<42>-Footnote-32925611
Ref: IDLE<42>-Footnote-42925654
Ref: IDLE<42>-Footnote-52925697
Ref: IDLE<42>-Footnote-62925740
Node: C API<30>2925783
Ref: whatsnew/changelog id3952925883
Ref: 113d2925883
Ref: C API<30>-Footnote-12926155
Ref: C API<30>-Footnote-22926198
Node: Tests<39>2926241
Ref: whatsnew/changelog id3962926342
Ref: 113e2926342
Ref: Tests<39>-Footnote-12926858
Ref: Tests<39>-Footnote-22926901
Ref: Tests<39>-Footnote-32926944
Ref: Tests<39>-Footnote-42926987
Node: Build<40>2927030
Ref: whatsnew/changelog id3972927137
Ref: 113f2927137
Ref: Build<40>-Footnote-12928522
Ref: Build<40>-Footnote-22928565
Ref: Build<40>-Footnote-32928608
Ref: Build<40>-Footnote-42928651
Ref: Build<40>-Footnote-52928694
Ref: Build<40>-Footnote-62928737
Ref: Build<40>-Footnote-72928780
Ref: Build<40>-Footnote-82928823
Ref: Build<40>-Footnote-92928866
Ref: Build<40>-Footnote-102928909
Ref: Build<40>-Footnote-112928953
Node: Tools/Demos<26>2928997
Ref: whatsnew/changelog id3982929106
Ref: 11402929106
Ref: Tools/Demos<26>-Footnote-12929381
Node: Windows<39>2929424
Ref: whatsnew/changelog id3992929515
Ref: 11412929515
Ref: Windows<39>-Footnote-12930484
Ref: Windows<39>-Footnote-22930527
Ref: Windows<39>-Footnote-32930570
Ref: Windows<39>-Footnote-42930612
Ref: Windows<39>-Footnote-52930655
Ref: Windows<39>-Footnote-62930698
Ref: Windows<39>-Footnote-72930740
Ref: Windows<39>-Footnote-82930783
Ref: Windows<39>-Footnote-92930826
Ref: Windows<39>-Footnote-102930869
Ref: Windows<39>-Footnote-112930913
Node: Python 3 6 0 alpha 42930957
Ref: whatsnew/changelog python-3-6-0-alpha-42931098
Ref: 11422931098
Node: Core and Builtins<52>2931345
Ref: whatsnew/changelog id4002931443
Ref: 11432931443
Ref: Core and Builtins<52>-Footnote-12933389
Ref: Core and Builtins<52>-Footnote-22933432
Ref: Core and Builtins<52>-Footnote-32933475
Ref: Core and Builtins<52>-Footnote-42933518
Ref: Core and Builtins<52>-Footnote-52933561
Ref: Core and Builtins<52>-Footnote-62933604
Ref: Core and Builtins<52>-Footnote-72933647
Ref: Core and Builtins<52>-Footnote-82933690
Ref: Core and Builtins<52>-Footnote-92933733
Ref: Core and Builtins<52>-Footnote-102933775
Ref: Core and Builtins<52>-Footnote-112933819
Ref: Core and Builtins<52>-Footnote-122933863
Ref: Core and Builtins<52>-Footnote-132933907
Ref: Core and Builtins<52>-Footnote-142933951
Node: Library<53>2934001
Ref: whatsnew/changelog id4012934116
Ref: 11442934116
Ref: Library<53>-Footnote-12938605
Ref: Library<53>-Footnote-22938648
Ref: Library<53>-Footnote-32938697
Ref: Library<53>-Footnote-42938740
Ref: Library<53>-Footnote-52938783
Ref: Library<53>-Footnote-62938826
Ref: Library<53>-Footnote-72938869
Ref: Library<53>-Footnote-82938912
Ref: Library<53>-Footnote-92938955
Ref: Library<53>-Footnote-102938998
Ref: Library<53>-Footnote-112939042
Ref: Library<53>-Footnote-122939092
Ref: Library<53>-Footnote-132939136
Ref: Library<53>-Footnote-142939180
Ref: Library<53>-Footnote-152939224
Ref: Library<53>-Footnote-162939268
Ref: Library<53>-Footnote-172939311
Ref: Library<53>-Footnote-182939355
Ref: Library<53>-Footnote-192939399
Ref: Library<53>-Footnote-202939443
Ref: Library<53>-Footnote-212939487
Ref: Library<53>-Footnote-222939531
Ref: Library<53>-Footnote-232939575
Ref: Library<53>-Footnote-242939619
Ref: Library<53>-Footnote-252939663
Ref: Library<53>-Footnote-262939707
Ref: Library<53>-Footnote-272939751
Ref: Library<53>-Footnote-282939795
Ref: Library<53>-Footnote-292939838
Ref: Library<53>-Footnote-302939882
Ref: Library<53>-Footnote-312939926
Ref: Library<53>-Footnote-322939970
Ref: Library<53>-Footnote-332940020
Ref: Library<53>-Footnote-342940064
Ref: Library<53>-Footnote-352940107
Ref: Library<53>-Footnote-362940151
Ref: Library<53>-Footnote-372940195
Ref: Library<53>-Footnote-382940239
Node: IDLE<43>2940283
Ref: whatsnew/changelog id4022940386
Ref: 11452940386
Ref: IDLE<43>-Footnote-12941710
Ref: IDLE<43>-Footnote-22941753
Ref: IDLE<43>-Footnote-32941796
Ref: IDLE<43>-Footnote-42941839
Ref: IDLE<43>-Footnote-52941882
Ref: IDLE<43>-Footnote-62941925
Ref: IDLE<43>-Footnote-72941968
Ref: IDLE<43>-Footnote-82942011
Node: Tests<40>2942054
Ref: whatsnew/changelog id4032942157
Ref: 11462942157
Ref: Tests<40>-Footnote-12942746
Ref: Tests<40>-Footnote-22942789
Ref: Tests<40>-Footnote-32942832
Ref: Tests<40>-Footnote-42942875
Node: Windows<40>2942918
Ref: whatsnew/changelog id4042943022
Ref: 11472943022
Ref: Windows<40>-Footnote-12943398
Ref: Windows<40>-Footnote-22943441
Ref: Windows<40>-Footnote-32943484
Ref: Windows<40>-Footnote-42943533
Ref: Windows<40>-Footnote-52943576
Node: Build<41>2943619
Ref: whatsnew/changelog id4052943705
Ref: 11482943705
Ref: Build<41>-Footnote-12944606
Ref: Build<41>-Footnote-22944649
Ref: Build<41>-Footnote-32944692
Ref: Build<41>-Footnote-42944735
Ref: Build<41>-Footnote-52944778
Ref: Build<41>-Footnote-62944821
Node: Python 3 6 0 alpha 32944864
Ref: whatsnew/changelog python-3-6-0-alpha-32945006
Ref: 11492945006
Node: Core and Builtins<53>2945417
Ref: whatsnew/changelog id4062945515
Ref: 114a2945515
Ref: Core and Builtins<53>-Footnote-12946262
Ref: Core and Builtins<53>-Footnote-22946305
Ref: Core and Builtins<53>-Footnote-32946348
Ref: Core and Builtins<53>-Footnote-42946391
Node: Library<54>2946434
Ref: whatsnew/changelog id4072946553
Ref: 114b2946553
Ref: Library<54>-Footnote-12950063
Ref: Library<54>-Footnote-22950106
Ref: Library<54>-Footnote-32950149
Ref: Library<54>-Footnote-42950192
Ref: Library<54>-Footnote-52950235
Ref: Library<54>-Footnote-62950278
Ref: Library<54>-Footnote-72950321
Ref: Library<54>-Footnote-82950364
Ref: Library<54>-Footnote-92950407
Ref: Library<54>-Footnote-102950450
Ref: Library<54>-Footnote-112950494
Ref: Library<54>-Footnote-122950538
Ref: Library<54>-Footnote-132950582
Ref: Library<54>-Footnote-142950626
Ref: Library<54>-Footnote-152950670
Ref: Library<54>-Footnote-162950714
Ref: Library<54>-Footnote-172950758
Ref: Library<54>-Footnote-182950802
Ref: Library<54>-Footnote-192950846
Ref: Library<54>-Footnote-202950890
Ref: Library<54>-Footnote-212950934
Node: Security<28>2950984
Ref: whatsnew/changelog id4082951093
Ref: 114c2951093
Ref: Security<28>-Footnote-12951382
Node: Library<55>2951425
Ref: whatsnew/changelog id4092951535
Ref: 114d2951535
Ref: Library<55>-Footnote-12951942
Ref: Library<55>-Footnote-22951985
Ref: Library<55>-Footnote-32952028
Node: Security<29>2952070
Ref: whatsnew/changelog id4102952179
Ref: 114e2952179
Ref: Security<29>-Footnote-12952343
Node: Library<56>2952386
Ref: whatsnew/changelog id4112952492
Ref: 114f2952492
Ref: Library<56>-Footnote-12952821
Ref: Library<56>-Footnote-22952864
Node: IDLE<44>2952907
Ref: whatsnew/changelog id4122953010
Ref: 11502953010
Ref: IDLE<44>-Footnote-12954672
Ref: IDLE<44>-Footnote-22954715
Ref: IDLE<44>-Footnote-32954758
Ref: IDLE<44>-Footnote-42954801
Ref: IDLE<44>-Footnote-52954844
Ref: IDLE<44>-Footnote-62954887
Ref: IDLE<44>-Footnote-72954930
Ref: IDLE<44>-Footnote-82954973
Ref: IDLE<44>-Footnote-92955016
Ref: IDLE<44>-Footnote-102955059
Node: C API<31>2955103
Ref: whatsnew/changelog id4132955204
Ref: 11512955204
Ref: C API<31>-Footnote-12955444
Node: Build<42>2955487
Ref: whatsnew/changelog id4142955595
Ref: 11522955595
Ref: Build<42>-Footnote-12956572
Ref: Build<42>-Footnote-22956615
Ref: Build<42>-Footnote-32956658
Ref: Build<42>-Footnote-42956701
Ref: Build<42>-Footnote-52956744
Node: Tools/Demos<27>2956787
Ref: whatsnew/changelog id4152956903
Ref: 11532956903
Ref: Tools/Demos<27>-Footnote-12957189
Ref: Tools/Demos<27>-Footnote-22957232
Node: Documentation<43>2957275
Ref: whatsnew/changelog id4162957391
Ref: 11542957391
Ref: Documentation<43>-Footnote-12957770
Ref: Documentation<43>-Footnote-22957813
Node: Tests<41>2957856
Ref: whatsnew/changelog id4172957948
Ref: 11552957948
Ref: Tests<41>-Footnote-12958118
Node: Python 3 6 0 alpha 22958161
Ref: whatsnew/changelog python-3-6-0-alpha-22958303
Ref: 11562958303
Node: Core and Builtins<54>2958762
Ref: whatsnew/changelog id4182958860
Ref: 11572958860
Ref: Core and Builtins<54>-Footnote-12960492
Ref: Core and Builtins<54>-Footnote-22960535
Ref: Core and Builtins<54>-Footnote-32960578
Ref: Core and Builtins<54>-Footnote-42960621
Ref: Core and Builtins<54>-Footnote-52960664
Ref: Core and Builtins<54>-Footnote-62960707
Ref: Core and Builtins<54>-Footnote-72960756
Ref: Core and Builtins<54>-Footnote-82960799
Ref: Core and Builtins<54>-Footnote-92960842
Ref: Core and Builtins<54>-Footnote-102960885
Ref: Core and Builtins<54>-Footnote-112960929
Ref: Core and Builtins<54>-Footnote-122960973
Node: Library<57>2961017
Ref: whatsnew/changelog id4192961136
Ref: 11582961136
Ref: Library<57>-Footnote-12961778
Ref: Library<57>-Footnote-22961821
Ref: Library<57>-Footnote-32961864
Ref: Library<57>-Footnote-42961907
Node: Security<30>2961950
Ref: whatsnew/changelog id4202962059
Ref: 11592962059
Ref: Security<30>-Footnote-12962295
Node: Library<58>2962338
Ref: whatsnew/changelog id4212962448
Ref: 115a2962448
Ref: Library<58>-Footnote-12964391
Ref: Library<58>-Footnote-22964434
Ref: Library<58>-Footnote-32964477
Ref: Library<58>-Footnote-42964520
Ref: Library<58>-Footnote-52964563
Ref: Library<58>-Footnote-62964612
Ref: Library<58>-Footnote-72964655
Ref: Library<58>-Footnote-82964698
Ref: Library<58>-Footnote-92964741
Ref: Library<58>-Footnote-102964790
Ref: Library<58>-Footnote-112964834
Ref: Library<58>-Footnote-122964884
Ref: Library<58>-Footnote-132964934
Ref: Library<58>-Footnote-142964978
Node: Security<31>2965022
Ref: whatsnew/changelog id4222965131
Ref: 115b2965131
Ref: Security<31>-Footnote-12965455
Node: Library<59>2965498
Ref: whatsnew/changelog id4232965604
Ref: 115c2965604
Ref: Library<59>-Footnote-12968359
Ref: Library<59>-Footnote-22968402
Ref: Library<59>-Footnote-32968445
Ref: Library<59>-Footnote-42968488
Ref: Library<59>-Footnote-52968531
Ref: Library<59>-Footnote-62968574
Ref: Library<59>-Footnote-72968617
Ref: Library<59>-Footnote-82968660
Ref: Library<59>-Footnote-92968703
Ref: Library<59>-Footnote-102968746
Ref: Library<59>-Footnote-112968790
Ref: Library<59>-Footnote-122968834
Ref: Library<59>-Footnote-132968878
Ref: Library<59>-Footnote-142968922
Ref: Library<59>-Footnote-152968966
Ref: Library<59>-Footnote-162969010
Ref: Library<59>-Footnote-172969054
Node: IDLE<45>2969098
Ref: whatsnew/changelog id4242969209
Ref: 115d2969209
Ref: IDLE<45>-Footnote-12971862
Ref: IDLE<45>-Footnote-22971904
Ref: IDLE<45>-Footnote-32971947
Ref: IDLE<45>-Footnote-42971990
Ref: IDLE<45>-Footnote-52972033
Ref: IDLE<45>-Footnote-62972076
Ref: IDLE<45>-Footnote-72972119
Ref: IDLE<45>-Footnote-82972162
Ref: IDLE<45>-Footnote-92972205
Ref: IDLE<45>-Footnote-102972248
Ref: IDLE<45>-Footnote-112972292
Ref: IDLE<45>-Footnote-122972336
Ref: IDLE<45>-Footnote-132972380
Ref: IDLE<45>-Footnote-142972424
Ref: IDLE<45>-Footnote-152972468
Ref: IDLE<45>-Footnote-162972512
Ref: IDLE<45>-Footnote-172972556
Ref: IDLE<45>-Footnote-182972600
Ref: IDLE<45>-Footnote-192972644
Node: Documentation<44>2972688
Ref: whatsnew/changelog id4252972797
Ref: 115e2972797
Ref: Documentation<44>-Footnote-12973240
Ref: Documentation<44>-Footnote-22973283
Ref: Documentation<44>-Footnote-32973326
Ref: Documentation<44>-Footnote-42973375
Node: Tests<42>2973418
Ref: whatsnew/changelog id4262973530
Ref: 115f2973530
Ref: Tests<42>-Footnote-12973910
Ref: Tests<42>-Footnote-22973953
Node: Windows<41>2973996
Ref: whatsnew/changelog id4272974100
Ref: 11602974100
Ref: Windows<41>-Footnote-12974384
Node: Build<43>2974427
Ref: whatsnew/changelog id4282974533
Ref: 11612974533
Ref: Build<43>-Footnote-12974812
Ref: Build<43>-Footnote-22974855
Node: Windows<42>2974898
Ref: whatsnew/changelog id4292975002
Ref: 11622975002
Ref: Windows<42>-Footnote-12975205
Node: C API<32>2975248
Ref: whatsnew/changelog id4302975358
Ref: 11632975358
Ref: C API<32>-Footnote-12975598
Ref: C API<32>-Footnote-22975641
Ref: C API<32>-Footnote-32975690
Node: Tools/Demos<28>2975733
Ref: whatsnew/changelog id4312975823
Ref: 11642975823
Ref: Tools/Demos<28>-Footnote-12976021
Node: Python 3 6 0 alpha 12976064
Ref: whatsnew/changelog python-3-6-0-alpha-12976204
Ref: 11652976204
Node: Core and Builtins<55>2976689
Ref: whatsnew/changelog id4322976787
Ref: 11662976787
Ref: Core and Builtins<55>-Footnote-12989960
Ref: Core and Builtins<55>-Footnote-22990003
Ref: Core and Builtins<55>-Footnote-32990046
Ref: Core and Builtins<55>-Footnote-42990089
Ref: Core and Builtins<55>-Footnote-52990132
Ref: Core and Builtins<55>-Footnote-62990175
Ref: Core and Builtins<55>-Footnote-72990218
Ref: Core and Builtins<55>-Footnote-82990261
Ref: Core and Builtins<55>-Footnote-92990304
Ref: Core and Builtins<55>-Footnote-102990347
Ref: Core and Builtins<55>-Footnote-112990391
Ref: Core and Builtins<55>-Footnote-122990435
Ref: Core and Builtins<55>-Footnote-132990479
Ref: Core and Builtins<55>-Footnote-142990523
Ref: Core and Builtins<55>-Footnote-152990567
Ref: Core and Builtins<55>-Footnote-162990611
Ref: Core and Builtins<55>-Footnote-172990661
Ref: Core and Builtins<55>-Footnote-182990705
Ref: Core and Builtins<55>-Footnote-192990749
Ref: Core and Builtins<55>-Footnote-202990793
Ref: Core and Builtins<55>-Footnote-212990837
Ref: Core and Builtins<55>-Footnote-222990881
Ref: Core and Builtins<55>-Footnote-232990925
Ref: Core and Builtins<55>-Footnote-242990975
Ref: Core and Builtins<55>-Footnote-252991019
Ref: Core and Builtins<55>-Footnote-262991063
Ref: Core and Builtins<55>-Footnote-272991107
Ref: Core and Builtins<55>-Footnote-282991151
Ref: Core and Builtins<55>-Footnote-292991195
Ref: Core and Builtins<55>-Footnote-302991239
Ref: Core and Builtins<55>-Footnote-312991283
Ref: Core and Builtins<55>-Footnote-322991327
Ref: Core and Builtins<55>-Footnote-332991371
Ref: Core and Builtins<55>-Footnote-342991415
Ref: Core and Builtins<55>-Footnote-352991459
Ref: Core and Builtins<55>-Footnote-362991503
Ref: Core and Builtins<55>-Footnote-372991546
Ref: Core and Builtins<55>-Footnote-382991590
Ref: Core and Builtins<55>-Footnote-392991634
Ref: Core and Builtins<55>-Footnote-402991678
Ref: Core and Builtins<55>-Footnote-412991722
Ref: Core and Builtins<55>-Footnote-422991766
Ref: Core and Builtins<55>-Footnote-432991810
Ref: Core and Builtins<55>-Footnote-442991854
Ref: Core and Builtins<55>-Footnote-452991898
Ref: Core and Builtins<55>-Footnote-462991942
Ref: Core and Builtins<55>-Footnote-472991986
Ref: Core and Builtins<55>-Footnote-482992030
Ref: Core and Builtins<55>-Footnote-492992074
Ref: Core and Builtins<55>-Footnote-502992118
Ref: Core and Builtins<55>-Footnote-512992162
Ref: Core and Builtins<55>-Footnote-522992206
Ref: Core and Builtins<55>-Footnote-532992249
Ref: Core and Builtins<55>-Footnote-542992293
Ref: Core and Builtins<55>-Footnote-552992337
Ref: Core and Builtins<55>-Footnote-562992381
Ref: Core and Builtins<55>-Footnote-572992425
Ref: Core and Builtins<55>-Footnote-582992469
Ref: Core and Builtins<55>-Footnote-592992513
Ref: Core and Builtins<55>-Footnote-602992557
Ref: Core and Builtins<55>-Footnote-612992601
Ref: Core and Builtins<55>-Footnote-622992645
Ref: Core and Builtins<55>-Footnote-632992689
Ref: Core and Builtins<55>-Footnote-642992733
Ref: Core and Builtins<55>-Footnote-652992777
Ref: Core and Builtins<55>-Footnote-662992821
Ref: Core and Builtins<55>-Footnote-672992865
Ref: Core and Builtins<55>-Footnote-682992909
Ref: Core and Builtins<55>-Footnote-692992953
Ref: Core and Builtins<55>-Footnote-702992997
Ref: Core and Builtins<55>-Footnote-712993041
Ref: Core and Builtins<55>-Footnote-722993085
Ref: Core and Builtins<55>-Footnote-732993129
Ref: Core and Builtins<55>-Footnote-742993173
Ref: Core and Builtins<55>-Footnote-752993217
Ref: Core and Builtins<55>-Footnote-762993261
Ref: Core and Builtins<55>-Footnote-772993305
Ref: Core and Builtins<55>-Footnote-782993349
Ref: Core and Builtins<55>-Footnote-792993392
Ref: Core and Builtins<55>-Footnote-802993436
Ref: Core and Builtins<55>-Footnote-812993486
Ref: Core and Builtins<55>-Footnote-822993530
Ref: Core and Builtins<55>-Footnote-832993574
Ref: Core and Builtins<55>-Footnote-842993618
Ref: Core and Builtins<55>-Footnote-852993662
Ref: Core and Builtins<55>-Footnote-862993706
Ref: Core and Builtins<55>-Footnote-872993750
Node: Library<60>2993794
Ref: whatsnew/changelog id4332993913
Ref: 11682993913
Ref: Library<60>-Footnote-12999081
Ref: Library<60>-Footnote-22999124
Ref: Library<60>-Footnote-32999167
Ref: Library<60>-Footnote-42999210
Ref: Library<60>-Footnote-52999253
Ref: Library<60>-Footnote-62999296
Ref: Library<60>-Footnote-72999339
Ref: Library<60>-Footnote-82999382
Ref: Library<60>-Footnote-92999425
Ref: Library<60>-Footnote-102999468
Ref: Library<60>-Footnote-112999512
Ref: Library<60>-Footnote-122999556
Ref: Library<60>-Footnote-132999600
Ref: Library<60>-Footnote-142999644
Ref: Library<60>-Footnote-152999688
Ref: Library<60>-Footnote-162999732
Ref: Library<60>-Footnote-172999776
Ref: Library<60>-Footnote-182999820
Ref: Library<60>-Footnote-192999870
Ref: Library<60>-Footnote-202999914
Ref: Library<60>-Footnote-212999958
Ref: Library<60>-Footnote-223000002
Ref: Library<60>-Footnote-233000046
Ref: Library<60>-Footnote-243000090
Ref: Library<60>-Footnote-253000134
Ref: Library<60>-Footnote-263000178
Ref: Library<60>-Footnote-273000222
Ref: Library<60>-Footnote-283000266
Ref: Library<60>-Footnote-293000310
Ref: Library<60>-Footnote-303000354
Ref: Library<60>-Footnote-313000398
Ref: Library<60>-Footnote-323000442
Ref: Library<60>-Footnote-333000486
Ref: Library<60>-Footnote-343000530
Ref: Library<60>-Footnote-353000574
Ref: Library<60>-Footnote-363000618
Node: Security<32>3000662
Ref: whatsnew/changelog id4343000771
Ref: 11693000771
Ref: Security<32>-Footnote-13001059
Node: Library<61>3001102
Ref: whatsnew/changelog id4353001212
Ref: 116a3001212
Ref: Library<61>-Footnote-13005925
Ref: Library<61>-Footnote-23005968
Ref: Library<61>-Footnote-33006011
Ref: Library<61>-Footnote-43006054
Ref: Library<61>-Footnote-53006097
Ref: Library<61>-Footnote-63006140
Ref: Library<61>-Footnote-73006183
Ref: Library<61>-Footnote-83006226
Ref: Library<61>-Footnote-93006269
Ref: Library<61>-Footnote-103006312
Ref: Library<61>-Footnote-113006356
Ref: Library<61>-Footnote-123006400
Ref: Library<61>-Footnote-133006444
Ref: Library<61>-Footnote-143006488
Ref: Library<61>-Footnote-153006532
Ref: Library<61>-Footnote-163006576
Ref: Library<61>-Footnote-173006620
Ref: Library<61>-Footnote-183006664
Ref: Library<61>-Footnote-193006708
Ref: Library<61>-Footnote-203006752
Ref: Library<61>-Footnote-213006796
Ref: Library<61>-Footnote-223006840
Ref: Library<61>-Footnote-233006884
Ref: Library<61>-Footnote-243006928
Ref: Library<61>-Footnote-253006972
Ref: Library<61>-Footnote-263007016
Ref: Library<61>-Footnote-273007060
Ref: Library<61>-Footnote-283007104
Ref: Library<61>-Footnote-293007148
Ref: Library<61>-Footnote-303007192
Ref: Library<61>-Footnote-313007236
Ref: Library<61>-Footnote-323007280
Node: Security<33>3007324
Ref: whatsnew/changelog id4363007433
Ref: 116c3007433
Ref: Security<33>-Footnote-13007620
Node: Library<62>3007663
Ref: whatsnew/changelog id4373007773
Ref: 116d3007773
Ref: Library<62>-Footnote-13011314
Ref: Library<62>-Footnote-23011357
Ref: Library<62>-Footnote-33011400
Ref: Library<62>-Footnote-43011443
Ref: Library<62>-Footnote-53011486
Ref: Library<62>-Footnote-63011529
Ref: Library<62>-Footnote-73011572
Ref: Library<62>-Footnote-83011615
Ref: Library<62>-Footnote-93011658
Ref: Library<62>-Footnote-103011701
Ref: Library<62>-Footnote-113011745
Ref: Library<62>-Footnote-123011789
Ref: Library<62>-Footnote-133011832
Ref: Library<62>-Footnote-143011876
Ref: Library<62>-Footnote-153011920
Ref: Library<62>-Footnote-163011964
Ref: Library<62>-Footnote-173012008
Ref: Library<62>-Footnote-183012052
Ref: Library<62>-Footnote-193012096
Ref: Library<62>-Footnote-203012140
Ref: Library<62>-Footnote-213012184
Ref: Library<62>-Footnote-223012228
Ref: Library<62>-Footnote-233012272
Ref: Library<62>-Footnote-243012316
Ref: Library<62>-Footnote-253012360
Node: Security<34>3012404
Ref: whatsnew/changelog id4383012513
Ref: 11703012513
Ref: Security<34>-Footnote-13012679
Node: Library<63>3012722
Ref: whatsnew/changelog id4393012828
Ref: 11713012828
Ref: Library<63>-Footnote-13030503
Ref: Library<63>-Footnote-23030546
Ref: Library<63>-Footnote-33030589
Ref: Library<63>-Footnote-43030632
Ref: Library<63>-Footnote-53030675
Ref: Library<63>-Footnote-63030718
Ref: Library<63>-Footnote-73030761
Ref: Library<63>-Footnote-83030804
Ref: Library<63>-Footnote-93030847
Ref: Library<63>-Footnote-103030890
Ref: Library<63>-Footnote-113030934
Ref: Library<63>-Footnote-123030978
Ref: Library<63>-Footnote-133031022
Ref: Library<63>-Footnote-143031066
Ref: Library<63>-Footnote-153031110
Ref: Library<63>-Footnote-163031154
Ref: Library<63>-Footnote-173031198
Ref: Library<63>-Footnote-183031242
Ref: Library<63>-Footnote-193031286
Ref: Library<63>-Footnote-203031330
Ref: Library<63>-Footnote-213031374
Ref: Library<63>-Footnote-223031418
Ref: Library<63>-Footnote-233031462
Ref: Library<63>-Footnote-243031506
Ref: Library<63>-Footnote-253031550
Ref: Library<63>-Footnote-263031594
Ref: Library<63>-Footnote-273031638
Ref: Library<63>-Footnote-283031682
Ref: Library<63>-Footnote-293031726
Ref: Library<63>-Footnote-303031770
Ref: Library<63>-Footnote-313031814
Ref: Library<63>-Footnote-323031858
Ref: Library<63>-Footnote-333031902
Ref: Library<63>-Footnote-343031946
Ref: Library<63>-Footnote-353031990
Ref: Library<63>-Footnote-363032034
Ref: Library<63>-Footnote-373032078
Ref: Library<63>-Footnote-383032122
Ref: Library<63>-Footnote-393032166
Ref: Library<63>-Footnote-403032210
Ref: Library<63>-Footnote-413032254
Ref: Library<63>-Footnote-423032298
Ref: Library<63>-Footnote-433032342
Ref: Library<63>-Footnote-443032386
Ref: Library<63>-Footnote-453032430
Ref: Library<63>-Footnote-463032474
Ref: Library<63>-Footnote-473032518
Ref: Library<63>-Footnote-483032562
Ref: Library<63>-Footnote-493032606
Ref: Library<63>-Footnote-503032650
Ref: Library<63>-Footnote-513032694
Ref: Library<63>-Footnote-523032737
Ref: Library<63>-Footnote-533032781
Ref: Library<63>-Footnote-543032825
Ref: Library<63>-Footnote-553032869
Ref: Library<63>-Footnote-563032913
Ref: Library<63>-Footnote-573032957
Ref: Library<63>-Footnote-583033000
Ref: Library<63>-Footnote-593033044
Ref: Library<63>-Footnote-603033088
Ref: Library<63>-Footnote-613033132
Ref: Library<63>-Footnote-623033176
Ref: Library<63>-Footnote-633033220
Ref: Library<63>-Footnote-643033264
Ref: Library<63>-Footnote-653033308
Ref: Library<63>-Footnote-663033352
Ref: Library<63>-Footnote-673033396
Ref: Library<63>-Footnote-683033439
Ref: Library<63>-Footnote-693033483
Ref: Library<63>-Footnote-703033527
Ref: Library<63>-Footnote-713033571
Ref: Library<63>-Footnote-723033615
Ref: Library<63>-Footnote-733033659
Ref: Library<63>-Footnote-743033703
Ref: Library<63>-Footnote-753033747
Ref: Library<63>-Footnote-763033791
Ref: Library<63>-Footnote-773033835
Ref: Library<63>-Footnote-783033879
Ref: Library<63>-Footnote-793033923
Ref: Library<63>-Footnote-803033967
Ref: Library<63>-Footnote-813034011
Ref: Library<63>-Footnote-823034055
Ref: Library<63>-Footnote-833034099
Ref: Library<63>-Footnote-843034143
Ref: Library<63>-Footnote-853034187
Ref: Library<63>-Footnote-863034231
Ref: Library<63>-Footnote-873034275
Ref: Library<63>-Footnote-883034319
Ref: Library<63>-Footnote-893034363
Ref: Library<63>-Footnote-903034407
Ref: Library<63>-Footnote-913034451
Ref: Library<63>-Footnote-923034495
Ref: Library<63>-Footnote-933034539
Ref: Library<63>-Footnote-943034583
Ref: Library<63>-Footnote-953034627
Ref: Library<63>-Footnote-963034671
Ref: Library<63>-Footnote-973034715
Ref: Library<63>-Footnote-983034759
Ref: Library<63>-Footnote-993034803
Ref: Library<63>-Footnote-1003034847
Ref: Library<63>-Footnote-1013034892
Ref: Library<63>-Footnote-1023034937
Ref: Library<63>-Footnote-1033034982
Ref: Library<63>-Footnote-1043035027
Ref: Library<63>-Footnote-1053035072
Ref: Library<63>-Footnote-1063035117
Ref: Library<63>-Footnote-1073035162
Ref: Library<63>-Footnote-1083035207
Ref: Library<63>-Footnote-1093035252
Ref: Library<63>-Footnote-1103035297
Ref: Library<63>-Footnote-1113035342
Ref: Library<63>-Footnote-1123035387
Ref: Library<63>-Footnote-1133035432
Ref: Library<63>-Footnote-1143035477
Ref: Library<63>-Footnote-1153035522
Ref: Library<63>-Footnote-1163035566
Ref: Library<63>-Footnote-1173035610
Ref: Library<63>-Footnote-1183035655
Ref: Library<63>-Footnote-1193035700
Ref: Library<63>-Footnote-1203035745
Ref: Library<63>-Footnote-1213035790
Ref: Library<63>-Footnote-1223035835
Ref: Library<63>-Footnote-1233035880
Ref: Library<63>-Footnote-1243035925
Ref: Library<63>-Footnote-1253035970
Ref: Library<63>-Footnote-1263036015
Ref: Library<63>-Footnote-1273036060
Ref: Library<63>-Footnote-1283036105
Ref: Library<63>-Footnote-1293036150
Ref: Library<63>-Footnote-1303036195
Ref: Library<63>-Footnote-1313036240
Node: IDLE<46>3036285
Ref: whatsnew/changelog id4403036396
Ref: 11723036396
Ref: IDLE<46>-Footnote-13041977
Ref: IDLE<46>-Footnote-23042020
Ref: IDLE<46>-Footnote-33042063
Ref: IDLE<46>-Footnote-43042106
Ref: IDLE<46>-Footnote-53042149
Ref: IDLE<46>-Footnote-63042192
Ref: IDLE<46>-Footnote-73042235
Ref: IDLE<46>-Footnote-83042278
Ref: IDLE<46>-Footnote-93042321
Ref: IDLE<46>-Footnote-103042364
Ref: IDLE<46>-Footnote-113042408
Ref: IDLE<46>-Footnote-123042452
Ref: IDLE<46>-Footnote-133042496
Ref: IDLE<46>-Footnote-143042540
Ref: IDLE<46>-Footnote-153042584
Ref: IDLE<46>-Footnote-163042628
Ref: IDLE<46>-Footnote-173042672
Ref: IDLE<46>-Footnote-183042716
Ref: IDLE<46>-Footnote-193042760
Ref: IDLE<46>-Footnote-203042804
Ref: IDLE<46>-Footnote-213042848
Ref: IDLE<46>-Footnote-223042892
Ref: IDLE<46>-Footnote-233042936
Ref: IDLE<46>-Footnote-243042980
Ref: IDLE<46>-Footnote-253043024
Ref: IDLE<46>-Footnote-263043068
Ref: IDLE<46>-Footnote-273043112
Ref: IDLE<46>-Footnote-283043156
Node: Documentation<45>3043200
Ref: whatsnew/changelog id4413043309
Ref: 11733043309
Ref: Documentation<45>-Footnote-13044095
Ref: Documentation<45>-Footnote-23044138
Ref: Documentation<45>-Footnote-33044180
Ref: Documentation<45>-Footnote-43044223
Ref: Documentation<45>-Footnote-53044266
Node: Tests<43>3044309
Ref: whatsnew/changelog id4423044419
Ref: 11743044419
Ref: Tests<43>-Footnote-13046170
Ref: Tests<43>-Footnote-23046213
Ref: Tests<43>-Footnote-33046256
Ref: Tests<43>-Footnote-43046299
Ref: Tests<43>-Footnote-53046342
Ref: Tests<43>-Footnote-63046385
Ref: Tests<43>-Footnote-73046428
Ref: Tests<43>-Footnote-83046471
Ref: Tests<43>-Footnote-93046514
Ref: Tests<43>-Footnote-103046557
Ref: Tests<43>-Footnote-113046601
Ref: Tests<43>-Footnote-123046645
Ref: Tests<43>-Footnote-133046689
Node: Build<44>3046733
Ref: whatsnew/changelog id4433046837
Ref: 11753046837
Ref: Build<44>-Footnote-13049569
Ref: Build<44>-Footnote-23049612
Ref: Build<44>-Footnote-33049655
Ref: Build<44>-Footnote-43049698
Ref: Build<44>-Footnote-53049741
Ref: Build<44>-Footnote-63049784
Ref: Build<44>-Footnote-73049827
Ref: Build<44>-Footnote-83049870
Ref: Build<44>-Footnote-93049913
Ref: Build<44>-Footnote-103049956
Ref: Build<44>-Footnote-113050000
Ref: Build<44>-Footnote-123050044
Ref: Build<44>-Footnote-133050088
Ref: Build<44>-Footnote-143050132
Ref: Build<44>-Footnote-153050176
Ref: Build<44>-Footnote-163050220
Ref: Build<44>-Footnote-173050264
Ref: Build<44>-Footnote-183050308
Ref: Build<44>-Footnote-193050352
Node: Windows<43>3050396
Ref: whatsnew/changelog id4443050506
Ref: 11763050506
Ref: Windows<43>-Footnote-13051156
Ref: Windows<43>-Footnote-23051199
Ref: Windows<43>-Footnote-33051242
Ref: Windows<43>-Footnote-43051285
Ref: Windows<43>-Footnote-53051328
Ref: Windows<43>-Footnote-63051371
Node: Tools/Demos<29>3051414
Ref: whatsnew/changelog id4453051524
Ref: 11773051524
Ref: Tools/Demos<29>-Footnote-13052316
Ref: Tools/Demos<29>-Footnote-23052359
Ref: Tools/Demos<29>-Footnote-33052402
Ref: Tools/Demos<29>-Footnote-43052445
Ref: Tools/Demos<29>-Footnote-53052488
Ref: Tools/Demos<29>-Footnote-63052531
Node: C API<33>3052574
Ref: whatsnew/changelog id4463052664
Ref: 11783052664
Ref: C API<33>-Footnote-13053153
Ref: C API<33>-Footnote-23053196
Node: Python 3 5 5 final3053239
Ref: whatsnew/changelog python-3-5-5-final3053391
Ref: 11793053391
Node: Python 3 5 5 release candidate 13053519
Ref: whatsnew/changelog python-3-5-5-release-candidate-13053669
Ref: 117a3053669
Node: Security<35>3053884
Ref: whatsnew/changelog id4473053995
Ref: 117b3053995
Ref: Security<35>-Footnote-13055263
Ref: Security<35>-Footnote-23055306
Ref: Security<35>-Footnote-33055349
Ref: Security<35>-Footnote-43055392
Ref: Security<35>-Footnote-53055435
Node: Core and Builtins<56>3055478
Ref: whatsnew/changelog id4483055609
Ref: 117c3055609
Ref: Core and Builtins<56>-Footnote-13055834
Node: Library<64>3055877
Ref: whatsnew/changelog id4493055987
Ref: 117d3055987
Ref: Library<64>-Footnote-13056514
Ref: Library<64>-Footnote-23056557
Node: Python 3 5 4 final3056600
Ref: whatsnew/changelog python-3-5-4-final3056764
Ref: 117e3056764
Node: Library<65>3056881
Ref: whatsnew/changelog id4503056947
Ref: 117f3056947
Ref: Library<65>-Footnote-13057146
Node: Python 3 5 4 release candidate 13057189
Ref: whatsnew/changelog python-3-5-4-release-candidate-13057339
Ref: 11803057339
Node: Security<36>3057674
Ref: whatsnew/changelog id4513057785
Ref: 11813057785
Ref: Security<36>-Footnote-13059084
Ref: Security<36>-Footnote-23059127
Ref: Security<36>-Footnote-33059170
Ref: Security<36>-Footnote-43059213
Node: Core and Builtins<57>3059256
Ref: whatsnew/changelog id4523059387
Ref: 11823059387
Ref: Core and Builtins<57>-Footnote-13061642
Ref: Core and Builtins<57>-Footnote-23061685
Ref: Core and Builtins<57>-Footnote-33061728
Ref: Core and Builtins<57>-Footnote-43061771
Ref: Core and Builtins<57>-Footnote-53061814
Ref: Core and Builtins<57>-Footnote-63061857
Ref: Core and Builtins<57>-Footnote-73061900
Ref: Core and Builtins<57>-Footnote-83061943
Ref: Core and Builtins<57>-Footnote-93061986
Ref: Core and Builtins<57>-Footnote-103062029
Ref: Core and Builtins<57>-Footnote-113062073
Ref: Core and Builtins<57>-Footnote-123062117
Ref: Core and Builtins<57>-Footnote-133062161
Ref: Core and Builtins<57>-Footnote-143062205
Ref: Core and Builtins<57>-Footnote-153062249
Node: Library<66>3062293
Ref: whatsnew/changelog id4533062429
Ref: 11833062429
Ref: Library<66>-Footnote-13072619
Ref: Library<66>-Footnote-23072662
Ref: Library<66>-Footnote-33072705
Ref: Library<66>-Footnote-43072748
Ref: Library<66>-Footnote-53072791
Ref: Library<66>-Footnote-63072834
Ref: Library<66>-Footnote-73072877
Ref: Library<66>-Footnote-83072920
Ref: Library<66>-Footnote-93072963
Ref: Library<66>-Footnote-103073006
Ref: Library<66>-Footnote-113073050
Ref: Library<66>-Footnote-123073094
Ref: Library<66>-Footnote-133073138
Ref: Library<66>-Footnote-143073182
Ref: Library<66>-Footnote-153073226
Ref: Library<66>-Footnote-163073270
Ref: Library<66>-Footnote-173073314
Ref: Library<66>-Footnote-183073358
Ref: Library<66>-Footnote-193073402
Ref: Library<66>-Footnote-203073446
Ref: Library<66>-Footnote-213073490
Ref: Library<66>-Footnote-223073534
Ref: Library<66>-Footnote-233073578
Ref: Library<66>-Footnote-243073622
Ref: Library<66>-Footnote-253073666
Ref: Library<66>-Footnote-263073710
Ref: Library<66>-Footnote-273073754
Ref: Library<66>-Footnote-283073798
Ref: Library<66>-Footnote-293073842
Ref: Library<66>-Footnote-303073886
Ref: Library<66>-Footnote-313073930
Ref: Library<66>-Footnote-323073974
Ref: Library<66>-Footnote-333074018
Ref: Library<66>-Footnote-343074062
Ref: Library<66>-Footnote-353074106
Ref: Library<66>-Footnote-363074150
Ref: Library<66>-Footnote-373074194
Ref: Library<66>-Footnote-383074238
Ref: Library<66>-Footnote-393074282
Ref: Library<66>-Footnote-403074326
Ref: Library<66>-Footnote-413074370
Ref: Library<66>-Footnote-423074414
Ref: Library<66>-Footnote-433074458
Ref: Library<66>-Footnote-443074502
Ref: Library<66>-Footnote-453074546
Ref: Library<66>-Footnote-463074590
Ref: Library<66>-Footnote-473074634
Ref: Library<66>-Footnote-483074678
Ref: Library<66>-Footnote-493074722
Ref: Library<66>-Footnote-503074766
Ref: Library<66>-Footnote-513074810
Ref: Library<66>-Footnote-523074854
Ref: Library<66>-Footnote-533074898
Ref: Library<66>-Footnote-543074942
Ref: Library<66>-Footnote-553074985
Ref: Library<66>-Footnote-563075029
Ref: Library<66>-Footnote-573075073
Ref: Library<66>-Footnote-583075117
Ref: Library<66>-Footnote-593075161
Ref: Library<66>-Footnote-603075205
Ref: Library<66>-Footnote-613075249
Ref: Library<66>-Footnote-623075293
Ref: Library<66>-Footnote-633075337
Ref: Library<66>-Footnote-643075381
Ref: Library<66>-Footnote-653075425
Ref: Library<66>-Footnote-663075469
Ref: Library<66>-Footnote-673075513
Ref: Library<66>-Footnote-683075557
Ref: Library<66>-Footnote-693075601
Ref: Library<66>-Footnote-703075645
Ref: Library<66>-Footnote-713075689
Ref: Library<66>-Footnote-723075733
Ref: Library<66>-Footnote-733075777
Ref: Library<66>-Footnote-743075821
Node: Documentation<46>3075865
Ref: whatsnew/changelog id4543075989
Ref: 11843075989
Ref: Documentation<46>-Footnote-13076699
Ref: Documentation<46>-Footnote-23076742
Ref: Documentation<46>-Footnote-33076785
Ref: Documentation<46>-Footnote-43076828
Ref: Documentation<46>-Footnote-53076871
Ref: Documentation<46>-Footnote-63076914
Node: Tests<44>3076957
Ref: whatsnew/changelog id4553077079
Ref: 11853077079
Ref: Tests<44>-Footnote-13079178
Ref: Tests<44>-Footnote-23079221
Ref: Tests<44>-Footnote-33079264
Ref: Tests<44>-Footnote-43079307
Ref: Tests<44>-Footnote-53079350
Ref: Tests<44>-Footnote-63079393
Ref: Tests<44>-Footnote-73079436
Ref: Tests<44>-Footnote-83079479
Ref: Tests<44>-Footnote-93079522
Node: Build<45>3079565
Ref: whatsnew/changelog id4563079681
Ref: 11863079681
Ref: Build<45>-Footnote-13080197
Ref: Build<45>-Footnote-23080240
Ref: Build<45>-Footnote-33080283
Node: Windows<44>3080326
Ref: whatsnew/changelog id4573080442
Ref: 11873080442
Ref: Windows<44>-Footnote-13080700
Ref: Windows<44>-Footnote-23080743
Node: C API<34>3080786
Ref: whatsnew/changelog id4583080884
Ref: 11883080884
Ref: C API<34>-Footnote-13081491
Ref: C API<34>-Footnote-23081534
Node: Python 3 5 3 final3081577
Ref: whatsnew/changelog python-3-5-3-final3081741
Ref: 11893081741
Node: Python 3 5 3 release candidate 13081886
Ref: whatsnew/changelog python-3-5-3-release-candidate-13082036
Ref: 118a3082036
Node: Core and Builtins<58>3082495
Ref: whatsnew/changelog id4593082605
Ref: 118b3082605
Ref: Core and Builtins<58>-Footnote-13088047
Ref: Core and Builtins<58>-Footnote-23088090
Ref: Core and Builtins<58>-Footnote-33088133
Ref: Core and Builtins<58>-Footnote-43088176
Ref: Core and Builtins<58>-Footnote-53088219
Ref: Core and Builtins<58>-Footnote-63088262
Ref: Core and Builtins<58>-Footnote-73088305
Ref: Core and Builtins<58>-Footnote-83088348
Ref: Core and Builtins<58>-Footnote-93088391
Ref: Core and Builtins<58>-Footnote-103088434
Ref: Core and Builtins<58>-Footnote-113088478
Ref: Core and Builtins<58>-Footnote-123088522
Ref: Core and Builtins<58>-Footnote-133088566
Ref: Core and Builtins<58>-Footnote-143088610
Ref: Core and Builtins<58>-Footnote-153088654
Ref: Core and Builtins<58>-Footnote-163088698
Ref: Core and Builtins<58>-Footnote-173088742
Ref: Core and Builtins<58>-Footnote-183088786
Ref: Core and Builtins<58>-Footnote-193088830
Ref: Core and Builtins<58>-Footnote-203088874
Ref: Core and Builtins<58>-Footnote-213088918
Ref: Core and Builtins<58>-Footnote-223088962
Ref: Core and Builtins<58>-Footnote-233089006
Ref: Core and Builtins<58>-Footnote-243089050
Ref: Core and Builtins<58>-Footnote-253089094
Ref: Core and Builtins<58>-Footnote-263089138
Ref: Core and Builtins<58>-Footnote-273089182
Ref: Core and Builtins<58>-Footnote-283089226
Ref: Core and Builtins<58>-Footnote-293089270
Ref: Core and Builtins<58>-Footnote-303089314
Ref: Core and Builtins<58>-Footnote-313089358
Ref: Core and Builtins<58>-Footnote-323089402
Ref: Core and Builtins<58>-Footnote-333089446
Ref: Core and Builtins<58>-Footnote-343089490
Ref: Core and Builtins<58>-Footnote-353089534
Ref: Core and Builtins<58>-Footnote-363089578
Ref: Core and Builtins<58>-Footnote-373089622
Ref: Core and Builtins<58>-Footnote-383089666
Ref: Core and Builtins<58>-Footnote-393089710
Ref: Core and Builtins<58>-Footnote-403089754
Ref: Core and Builtins<58>-Footnote-413089798
Ref: Core and Builtins<58>-Footnote-423089842
Ref: Core and Builtins<58>-Footnote-433089886
Node: Library<67>3089930
Ref: whatsnew/changelog id4603090061
Ref: 118c3090061
Ref: Library<67>-Footnote-13103065
Ref: Library<67>-Footnote-23103108
Ref: Library<67>-Footnote-33103151
Ref: Library<67>-Footnote-43103194
Ref: Library<67>-Footnote-53103237
Ref: Library<67>-Footnote-63103279
Ref: Library<67>-Footnote-73103322
Ref: Library<67>-Footnote-83103365
Ref: Library<67>-Footnote-93103408
Ref: Library<67>-Footnote-103103451
Ref: Library<67>-Footnote-113103495
Ref: Library<67>-Footnote-123103539
Ref: Library<67>-Footnote-133103583
Ref: Library<67>-Footnote-143103627
Ref: Library<67>-Footnote-153103671
Ref: Library<67>-Footnote-163103715
Ref: Library<67>-Footnote-173103759
Ref: Library<67>-Footnote-183103803
Ref: Library<67>-Footnote-193103847
Ref: Library<67>-Footnote-203103891
Ref: Library<67>-Footnote-213103935
Ref: Library<67>-Footnote-223103979
Ref: Library<67>-Footnote-233104023
Ref: Library<67>-Footnote-243104067
Ref: Library<67>-Footnote-253104111
Ref: Library<67>-Footnote-263104155
Ref: Library<67>-Footnote-273104199
Ref: Library<67>-Footnote-283104243
Ref: Library<67>-Footnote-293104287
Ref: Library<67>-Footnote-303104331
Ref: Library<67>-Footnote-313104375
Ref: Library<67>-Footnote-323104419
Ref: Library<67>-Footnote-333104465
Ref: Library<67>-Footnote-343104509
Ref: Library<67>-Footnote-353104553
Ref: Library<67>-Footnote-363104597
Ref: Library<67>-Footnote-373104641
Ref: Library<67>-Footnote-383104685
Ref: Library<67>-Footnote-393104729
Ref: Library<67>-Footnote-403104773
Ref: Library<67>-Footnote-413104817
Ref: Library<67>-Footnote-423104861
Ref: Library<67>-Footnote-433104905
Ref: Library<67>-Footnote-443104949
Ref: Library<67>-Footnote-453104993
Ref: Library<67>-Footnote-463105037
Ref: Library<67>-Footnote-473105081
Ref: Library<67>-Footnote-483105125
Ref: Library<67>-Footnote-493105169
Ref: Library<67>-Footnote-503105213
Ref: Library<67>-Footnote-513105257
Ref: Library<67>-Footnote-523105301
Ref: Library<67>-Footnote-533105345
Ref: Library<67>-Footnote-543105389
Ref: Library<67>-Footnote-553105433
Ref: Library<67>-Footnote-563105477
Ref: Library<67>-Footnote-573105521
Ref: Library<67>-Footnote-583105565
Ref: Library<67>-Footnote-593105609
Ref: Library<67>-Footnote-603105653
Ref: Library<67>-Footnote-613105697
Ref: Library<67>-Footnote-623105741
Ref: Library<67>-Footnote-633105785
Ref: Library<67>-Footnote-643105829
Ref: Library<67>-Footnote-653105873
Ref: Library<67>-Footnote-663105917
Ref: Library<67>-Footnote-673105961
Ref: Library<67>-Footnote-683106005
Ref: Library<67>-Footnote-693106049
Ref: Library<67>-Footnote-703106093
Ref: Library<67>-Footnote-713106137
Ref: Library<67>-Footnote-723106180
Ref: Library<67>-Footnote-733106224
Ref: Library<67>-Footnote-743106268
Ref: Library<67>-Footnote-753106312
Ref: Library<67>-Footnote-763106356
Ref: Library<67>-Footnote-773106400
Ref: Library<67>-Footnote-783106444
Ref: Library<67>-Footnote-793106488
Ref: Library<67>-Footnote-803106532
Ref: Library<67>-Footnote-813106576
Ref: Library<67>-Footnote-823106620
Ref: Library<67>-Footnote-833106664
Ref: Library<67>-Footnote-843106708
Ref: Library<67>-Footnote-853106752
Ref: Library<67>-Footnote-863106796
Ref: Library<67>-Footnote-873106840
Ref: Library<67>-Footnote-883106884
Ref: Library<67>-Footnote-893106928
Ref: Library<67>-Footnote-903106972
Ref: Library<67>-Footnote-913107016
Ref: Library<67>-Footnote-923107060
Ref: Library<67>-Footnote-933107104
Ref: Library<67>-Footnote-943107148
Ref: Library<67>-Footnote-953107192
Node: Security<37>3107242
Ref: whatsnew/changelog id4613107363
Ref: 118d3107363
Ref: Security<37>-Footnote-13107652
Node: Library<68>3107695
Ref: whatsnew/changelog id4623107817
Ref: 118e3107817
Ref: Library<68>-Footnote-13107991
Node: Security<38>3108034
Ref: whatsnew/changelog id4633108155
Ref: 118f3108155
Ref: Security<38>-Footnote-13108319
Node: Library<69>3108362
Ref: whatsnew/changelog id4643108480
Ref: 11903108480
Ref: Library<69>-Footnote-13111360
Ref: Library<69>-Footnote-23111403
Ref: Library<69>-Footnote-33111446
Ref: Library<69>-Footnote-43111489
Ref: Library<69>-Footnote-53111532
Ref: Library<69>-Footnote-63111575
Ref: Library<69>-Footnote-73111618
Ref: Library<69>-Footnote-83111661
Ref: Library<69>-Footnote-93111704
Ref: Library<69>-Footnote-103111747
Ref: Library<69>-Footnote-113111791
Ref: Library<69>-Footnote-123111835
Ref: Library<69>-Footnote-133111879
Ref: Library<69>-Footnote-143111923
Ref: Library<69>-Footnote-153111967
Ref: Library<69>-Footnote-163112011
Ref: Library<69>-Footnote-173112055
Ref: Library<69>-Footnote-183112099
Ref: Library<69>-Footnote-193112143
Ref: Library<69>-Footnote-203112187
Ref: Library<69>-Footnote-213112231
Ref: Library<69>-Footnote-223112275
Ref: Library<69>-Footnote-233112319
Ref: Library<69>-Footnote-243112363
Ref: Library<69>-Footnote-253112407
Ref: Library<69>-Footnote-263112451
Ref: Library<69>-Footnote-273112495
Ref: Library<69>-Footnote-283112539
Node: IDLE<47>3112583
Ref: whatsnew/changelog id4653112698
Ref: 11913112698
Ref: IDLE<47>-Footnote-13113947
Ref: IDLE<47>-Footnote-23113990
Ref: IDLE<47>-Footnote-33114033
Ref: IDLE<47>-Footnote-43114076
Ref: IDLE<47>-Footnote-53114119
Ref: IDLE<47>-Footnote-63114162
Ref: IDLE<47>-Footnote-73114205
Ref: IDLE<47>-Footnote-83114248
Node: C API<35>3114291
Ref: whatsnew/changelog id4663114412
Ref: 11923114412
Ref: C API<35>-Footnote-13114742
Ref: C API<35>-Footnote-23114785
Node: Documentation<47>3114828
Ref: whatsnew/changelog id4673114950
Ref: 11933114950
Ref: Documentation<47>-Footnote-13115101
Node: Tests<45>3115144
Ref: whatsnew/changelog id4683115272
Ref: 11943115272
Ref: Tests<45>-Footnote-13115961
Ref: Tests<45>-Footnote-23116004
Ref: Tests<45>-Footnote-33116047
Ref: Tests<45>-Footnote-43116090
Ref: Tests<45>-Footnote-53116133
Ref: Tests<45>-Footnote-63116176
Node: Tools/Demos<30>3116219
Ref: whatsnew/changelog id4693116341
Ref: 11953116341
Ref: Tools/Demos<30>-Footnote-13116821
Ref: Tools/Demos<30>-Footnote-23116864
Ref: Tools/Demos<30>-Footnote-33116907
Node: Windows<45>3116950
Ref: whatsnew/changelog id4703117072
Ref: 11963117072
Ref: Windows<45>-Footnote-13117574
Ref: Windows<45>-Footnote-23117617
Ref: Windows<45>-Footnote-33117660
Ref: Windows<45>-Footnote-43117703
Ref: Windows<45>-Footnote-53117746
Node: Build<46>3117789
Ref: whatsnew/changelog id4713117887
Ref: 11973117887
Ref: Build<46>-Footnote-13120594
Ref: Build<46>-Footnote-23120637
Ref: Build<46>-Footnote-33120680
Ref: Build<46>-Footnote-43120723
Ref: Build<46>-Footnote-53120766
Ref: Build<46>-Footnote-63120809
Ref: Build<46>-Footnote-73120852
Ref: Build<46>-Footnote-83120895
Ref: Build<46>-Footnote-93120938
Ref: Build<46>-Footnote-103120981
Ref: Build<46>-Footnote-113121025
Ref: Build<46>-Footnote-123121069
Ref: Build<46>-Footnote-133121113
Ref: Build<46>-Footnote-143121157
Ref: Build<46>-Footnote-153121201
Ref: Build<46>-Footnote-163121245
Ref: Build<46>-Footnote-173121289
Ref: Build<46>-Footnote-183121333
Ref: Build<46>-Footnote-193121377
Ref: Build<46>-Footnote-203121421
Ref: Build<46>-Footnote-213121465
Ref: Build<46>-Footnote-223121509
Node: Python 3 5 2 final3121553
Ref: whatsnew/changelog python-3-5-2-final3121717
Ref: 11983121717
Node: Core and Builtins<59>3121892
Ref: whatsnew/changelog id4723121986
Ref: 11993121986
Ref: Core and Builtins<59>-Footnote-13122144
Node: Tests<46>3122187
Ref: whatsnew/changelog id4733122298
Ref: 119a3122298
Ref: Tests<46>-Footnote-13122458
Node: IDLE<48>3122501
Ref: whatsnew/changelog id4743122582
Ref: 119b3122582
Ref: IDLE<48>-Footnote-13122736
Node: Python 3 5 2 release candidate 13122779
Ref: whatsnew/changelog python-3-5-2-release-candidate-13122929
Ref: 119c3122929
Node: Core and Builtins<60>3123518
Ref: whatsnew/changelog id4753123629
Ref: 119d3123629
Ref: Core and Builtins<60>-Footnote-13129476
Ref: Core and Builtins<60>-Footnote-23129519
Ref: Core and Builtins<60>-Footnote-33129562
Ref: Core and Builtins<60>-Footnote-43129605
Ref: Core and Builtins<60>-Footnote-53129648
Ref: Core and Builtins<60>-Footnote-63129691
Ref: Core and Builtins<60>-Footnote-73129734
Ref: Core and Builtins<60>-Footnote-83129777
Ref: Core and Builtins<60>-Footnote-93129820
Ref: Core and Builtins<60>-Footnote-103129863
Ref: Core and Builtins<60>-Footnote-113129907
Ref: Core and Builtins<60>-Footnote-123129951
Ref: Core and Builtins<60>-Footnote-133129995
Ref: Core and Builtins<60>-Footnote-143130039
Ref: Core and Builtins<60>-Footnote-153130083
Ref: Core and Builtins<60>-Footnote-163130127
Ref: Core and Builtins<60>-Footnote-173130171
Ref: Core and Builtins<60>-Footnote-183130214
Ref: Core and Builtins<60>-Footnote-193130258
Ref: Core and Builtins<60>-Footnote-203130302
Ref: Core and Builtins<60>-Footnote-213130346
Ref: Core and Builtins<60>-Footnote-223130390
Ref: Core and Builtins<60>-Footnote-233130434
Ref: Core and Builtins<60>-Footnote-243130478
Ref: Core and Builtins<60>-Footnote-253130522
Ref: Core and Builtins<60>-Footnote-263130566
Ref: Core and Builtins<60>-Footnote-273130610
Ref: Core and Builtins<60>-Footnote-283130654
Ref: Core and Builtins<60>-Footnote-293130698
Ref: Core and Builtins<60>-Footnote-303130742
Ref: Core and Builtins<60>-Footnote-313130786
Ref: Core and Builtins<60>-Footnote-323130836
Ref: Core and Builtins<60>-Footnote-333130880
Ref: Core and Builtins<60>-Footnote-343130924
Ref: Core and Builtins<60>-Footnote-353130968
Ref: Core and Builtins<60>-Footnote-363131012
Ref: Core and Builtins<60>-Footnote-373131056
Ref: Core and Builtins<60>-Footnote-383131100
Node: Security<39>3131144
Ref: whatsnew/changelog id4763131275
Ref: 119e3131275
Ref: Security<39>-Footnote-13131510
Node: Library<70>3131553
Ref: whatsnew/changelog id4773131675
Ref: 119f3131675
Ref: Library<70>-Footnote-13132851
Ref: Library<70>-Footnote-23132894
Ref: Library<70>-Footnote-33132937
Ref: Library<70>-Footnote-43132986
Ref: Library<70>-Footnote-53133029
Node: Security<40>3133072
Ref: whatsnew/changelog id4783133193
Ref: 11a03133193
Ref: Security<40>-Footnote-13133517
Node: Library<71>3133560
Ref: whatsnew/changelog id4793133682
Ref: 11a13133682
Ref: Library<71>-Footnote-13138406
Ref: Library<71>-Footnote-23138449
Ref: Library<71>-Footnote-33138492
Ref: Library<71>-Footnote-43138535
Ref: Library<71>-Footnote-53138578
Ref: Library<71>-Footnote-63138621
Ref: Library<71>-Footnote-73138664
Ref: Library<71>-Footnote-83138707
Ref: Library<71>-Footnote-93138750
Ref: Library<71>-Footnote-103138793
Ref: Library<71>-Footnote-113138837
Ref: Library<71>-Footnote-123138881
Ref: Library<71>-Footnote-133138925
Ref: Library<71>-Footnote-143138969
Ref: Library<71>-Footnote-153139013
Ref: Library<71>-Footnote-163139057
Ref: Library<71>-Footnote-173139101
Ref: Library<71>-Footnote-183139145
Ref: Library<71>-Footnote-193139189
Ref: Library<71>-Footnote-203139233
Ref: Library<71>-Footnote-213139277
Ref: Library<71>-Footnote-223139321
Ref: Library<71>-Footnote-233139365
Ref: Library<71>-Footnote-243139409
Ref: Library<71>-Footnote-253139453
Ref: Library<71>-Footnote-263139497
Ref: Library<71>-Footnote-273139541
Ref: Library<71>-Footnote-283139585
Ref: Library<71>-Footnote-293139629
Ref: Library<71>-Footnote-303139673
Ref: Library<71>-Footnote-313139717
Node: Security<41>3139761
Ref: whatsnew/changelog id4803139882
Ref: 11a23139882
Ref: Security<41>-Footnote-13140170
Node: Library<72>3140213
Ref: whatsnew/changelog id4813140335
Ref: 11a33140335
Ref: Library<72>-Footnote-13142407
Ref: Library<72>-Footnote-23142450
Ref: Library<72>-Footnote-33142493
Ref: Library<72>-Footnote-43142536
Ref: Library<72>-Footnote-53142579
Ref: Library<72>-Footnote-63142622
Ref: Library<72>-Footnote-73142665
Ref: Library<72>-Footnote-83142708
Ref: Library<72>-Footnote-93142751
Ref: Library<72>-Footnote-103142794
Ref: Library<72>-Footnote-113142838
Ref: Library<72>-Footnote-123142882
Ref: Library<72>-Footnote-133142926
Ref: Library<72>-Footnote-143142970
Ref: Library<72>-Footnote-153143014
Node: Security<42>3143058
Ref: whatsnew/changelog id4823143179
Ref: 11a43143179
Ref: Security<42>-Footnote-13143366
Node: Library<73>3143409
Ref: whatsnew/changelog id4833143531
Ref: 11a53143531
Ref: Library<73>-Footnote-13146084
Ref: Library<73>-Footnote-23146127
Ref: Library<73>-Footnote-33146170
Ref: Library<73>-Footnote-43146213
Ref: Library<73>-Footnote-53146256
Ref: Library<73>-Footnote-63146299
Ref: Library<73>-Footnote-73146342
Ref: Library<73>-Footnote-83146385
Ref: Library<73>-Footnote-93146428
Ref: Library<73>-Footnote-103146471
Ref: Library<73>-Footnote-113146514
Ref: Library<73>-Footnote-123146558
Ref: Library<73>-Footnote-133146602
Ref: Library<73>-Footnote-143146646
Ref: Library<73>-Footnote-153146690
Ref: Library<73>-Footnote-163146734
Ref: Library<73>-Footnote-173146778
Ref: Library<73>-Footnote-183146822
Ref: Library<73>-Footnote-193146866
Node: Security<43>3146910
Ref: whatsnew/changelog id4843147031
Ref: 11a63147031
Ref: Security<43>-Footnote-13147199
Node: Library<74>3147242
Ref: whatsnew/changelog id4853147360
Ref: 11a73147360
Ref: Library<74>-Footnote-13153852
Ref: Library<74>-Footnote-23153895
Ref: Library<74>-Footnote-33153938
Ref: Library<74>-Footnote-43153981
Ref: Library<74>-Footnote-53154024
Ref: Library<74>-Footnote-63154067
Ref: Library<74>-Footnote-73154110
Ref: Library<74>-Footnote-83154153
Ref: Library<74>-Footnote-93154196
Ref: Library<74>-Footnote-103154239
Ref: Library<74>-Footnote-113154283
Ref: Library<74>-Footnote-123154327
Ref: Library<74>-Footnote-133154371
Ref: Library<74>-Footnote-143154415
Ref: Library<74>-Footnote-153154459
Ref: Library<74>-Footnote-163154503
Ref: Library<74>-Footnote-173154547
Ref: Library<74>-Footnote-183154591
Ref: Library<74>-Footnote-193154635
Ref: Library<74>-Footnote-203154679
Ref: Library<74>-Footnote-213154723
Ref: Library<74>-Footnote-223154767
Ref: Library<74>-Footnote-233154811
Ref: Library<74>-Footnote-243154855
Ref: Library<74>-Footnote-253154899
Ref: Library<74>-Footnote-263154943
Ref: Library<74>-Footnote-273154987
Ref: Library<74>-Footnote-283155031
Ref: Library<74>-Footnote-293155075
Ref: Library<74>-Footnote-303155119
Ref: Library<74>-Footnote-313155163
Ref: Library<74>-Footnote-323155206
Ref: Library<74>-Footnote-333155250
Ref: Library<74>-Footnote-343155294
Ref: Library<74>-Footnote-353155338
Ref: Library<74>-Footnote-363155382
Ref: Library<74>-Footnote-373155426
Ref: Library<74>-Footnote-383155470
Ref: Library<74>-Footnote-393155514
Ref: Library<74>-Footnote-403155558
Ref: Library<74>-Footnote-413155602
Ref: Library<74>-Footnote-423155646
Ref: Library<74>-Footnote-433155690
Ref: Library<74>-Footnote-443155734
Ref: Library<74>-Footnote-453155778
Ref: Library<74>-Footnote-463155822
Ref: Library<74>-Footnote-473155866
Ref: Library<74>-Footnote-483155910
Ref: Library<74>-Footnote-493155954
Ref: Library<74>-Footnote-503155998
Node: IDLE<49>3156042
Ref: whatsnew/changelog id4863156165
Ref: 11a83156165
Ref: IDLE<49>-Footnote-13158528
Ref: IDLE<49>-Footnote-23158570
Ref: IDLE<49>-Footnote-33158613
Ref: IDLE<49>-Footnote-43158656
Ref: IDLE<49>-Footnote-53158699
Ref: IDLE<49>-Footnote-63158742
Ref: IDLE<49>-Footnote-73158785
Ref: IDLE<49>-Footnote-83158828
Ref: IDLE<49>-Footnote-93158871
Ref: IDLE<49>-Footnote-103158914
Ref: IDLE<49>-Footnote-113158958
Ref: IDLE<49>-Footnote-123159002
Ref: IDLE<49>-Footnote-133159046
Ref: IDLE<49>-Footnote-143159090
Ref: IDLE<49>-Footnote-153159134
Node: Documentation<48>3159178
Ref: whatsnew/changelog id4873159299
Ref: 11a93159299
Ref: Documentation<48>-Footnote-13160255
Ref: Documentation<48>-Footnote-23160298
Ref: Documentation<48>-Footnote-33160341
Ref: Documentation<48>-Footnote-43160390
Ref: Documentation<48>-Footnote-53160433
Ref: Documentation<48>-Footnote-63160475
Ref: Documentation<48>-Footnote-73160518
Ref: Documentation<48>-Footnote-83160561
Node: Tests<47>3160604
Ref: whatsnew/changelog id4883160726
Ref: 11aa3160726
Ref: Tests<47>-Footnote-13161601
Ref: Tests<47>-Footnote-23161644
Ref: Tests<47>-Footnote-33161687
Ref: Tests<47>-Footnote-43161730
Ref: Tests<47>-Footnote-53161773
Ref: Tests<47>-Footnote-63161816
Ref: Tests<47>-Footnote-73161859
Node: Build<47>3161902
Ref: whatsnew/changelog id4893162018
Ref: 11ab3162018
Ref: Build<47>-Footnote-13164546
Ref: Build<47>-Footnote-23164589
Ref: Build<47>-Footnote-33164632
Ref: Build<47>-Footnote-43164675
Ref: Build<47>-Footnote-53164718
Ref: Build<47>-Footnote-63164761
Ref: Build<47>-Footnote-73164804
Ref: Build<47>-Footnote-83164847
Ref: Build<47>-Footnote-93164890
Ref: Build<47>-Footnote-103164933
Ref: Build<47>-Footnote-113164977
Ref: Build<47>-Footnote-123165021
Ref: Build<47>-Footnote-133165065
Ref: Build<47>-Footnote-143165109
Ref: Build<47>-Footnote-153165153
Ref: Build<47>-Footnote-163165197
Ref: Build<47>-Footnote-173165241
Node: Windows<46>3165285
Ref: whatsnew/changelog id4903165407
Ref: 11ac3165407
Ref: Windows<46>-Footnote-13165989
Ref: Windows<46>-Footnote-23166032
Ref: Windows<46>-Footnote-33166075
Ref: Windows<46>-Footnote-43166118
Ref: Windows<46>-Footnote-53166161
Node: Tools/Demos<31>3166204
Ref: whatsnew/changelog id4913166328
Ref: 11ad3166328
Ref: Tools/Demos<31>-Footnote-13166952
Ref: Tools/Demos<31>-Footnote-23166995
Ref: Tools/Demos<31>-Footnote-33167038
Ref: Tools/Demos<31>-Footnote-43167081
Node: Windows<47>3167124
Ref: whatsnew/changelog id4923167228
Ref: 11ae3167228
Ref: Windows<47>-Footnote-13167431
Node: Python 3 5 1 final3167474
Ref: whatsnew/changelog python-3-5-1-final3167638
Ref: 11af3167638
Node: Core and Builtins<61>3167799
Ref: whatsnew/changelog id4933167895
Ref: 11b03167895
Ref: Core and Builtins<61>-Footnote-13168079
Node: Windows<48>3168122
Ref: whatsnew/changelog id4943168218
Ref: 11b13168218
Ref: Windows<48>-Footnote-13168408
Node: Python 3 5 1 release candidate 13168451
Ref: whatsnew/changelog python-3-5-1-release-candidate-13168601
Ref: 11b23168601
Node: Core and Builtins<62>3168940
Ref: whatsnew/changelog id4953169050
Ref: 11b33169050
Ref: Core and Builtins<62>-Footnote-13172182
Ref: Core and Builtins<62>-Footnote-23172225
Ref: Core and Builtins<62>-Footnote-33172268
Ref: Core and Builtins<62>-Footnote-43172311
Ref: Core and Builtins<62>-Footnote-53172354
Ref: Core and Builtins<62>-Footnote-63172397
Ref: Core and Builtins<62>-Footnote-73172440
Ref: Core and Builtins<62>-Footnote-83172483
Ref: Core and Builtins<62>-Footnote-93172526
Ref: Core and Builtins<62>-Footnote-103172569
Ref: Core and Builtins<62>-Footnote-113172613
Ref: Core and Builtins<62>-Footnote-123172657
Ref: Core and Builtins<62>-Footnote-133172701
Ref: Core and Builtins<62>-Footnote-143172745
Ref: Core and Builtins<62>-Footnote-153172789
Ref: Core and Builtins<62>-Footnote-163172833
Ref: Core and Builtins<62>-Footnote-173172877
Ref: Core and Builtins<62>-Footnote-183172921
Ref: Core and Builtins<62>-Footnote-193172965
Node: Library<75>3173009
Ref: whatsnew/changelog id4963173136
Ref: 11b43173136
Ref: Library<75>-Footnote-13183502
Ref: Library<75>-Footnote-23183545
Ref: Library<75>-Footnote-33183588
Ref: Library<75>-Footnote-43183631
Ref: Library<75>-Footnote-53183673
Ref: Library<75>-Footnote-63183716
Ref: Library<75>-Footnote-73183759
Ref: Library<75>-Footnote-83183802
Ref: Library<75>-Footnote-93183845
Ref: Library<75>-Footnote-103183888
Ref: Library<75>-Footnote-113183932
Ref: Library<75>-Footnote-123183976
Ref: Library<75>-Footnote-133184020
Ref: Library<75>-Footnote-143184064
Ref: Library<75>-Footnote-153184108
Ref: Library<75>-Footnote-163184152
Ref: Library<75>-Footnote-173184196
Ref: Library<75>-Footnote-183184240
Ref: Library<75>-Footnote-193184284
Ref: Library<75>-Footnote-203184328
Ref: Library<75>-Footnote-213184372
Ref: Library<75>-Footnote-223184416
Ref: Library<75>-Footnote-233184460
Ref: Library<75>-Footnote-243184504
Ref: Library<75>-Footnote-253184548
Ref: Library<75>-Footnote-263184592
Ref: Library<75>-Footnote-273184636
Ref: Library<75>-Footnote-283184680
Ref: Library<75>-Footnote-293184724
Ref: Library<75>-Footnote-303184768
Ref: Library<75>-Footnote-313184812
Ref: Library<75>-Footnote-323184856
Ref: Library<75>-Footnote-333184900
Ref: Library<75>-Footnote-343184944
Ref: Library<75>-Footnote-353184988
Ref: Library<75>-Footnote-363185032
Ref: Library<75>-Footnote-373185076
Ref: Library<75>-Footnote-383185120
Ref: Library<75>-Footnote-393185164
Ref: Library<75>-Footnote-403185208
Ref: Library<75>-Footnote-413185252
Ref: Library<75>-Footnote-423185296
Ref: Library<75>-Footnote-433185340
Ref: Library<75>-Footnote-443185384
Ref: Library<75>-Footnote-453185428
Ref: Library<75>-Footnote-463185472
Ref: Library<75>-Footnote-473185516
Ref: Library<75>-Footnote-483185560
Ref: Library<75>-Footnote-493185604
Ref: Library<75>-Footnote-503185648
Ref: Library<75>-Footnote-513185692
Ref: Library<75>-Footnote-523185736
Ref: Library<75>-Footnote-533185780
Ref: Library<75>-Footnote-543185824
Ref: Library<75>-Footnote-553185868
Ref: Library<75>-Footnote-563185912
Ref: Library<75>-Footnote-573185956
Ref: Library<75>-Footnote-583186000
Ref: Library<75>-Footnote-593186044
Ref: Library<75>-Footnote-603186088
Ref: Library<75>-Footnote-613186132
Ref: Library<75>-Footnote-623186176
Ref: Library<75>-Footnote-633186220
Ref: Library<75>-Footnote-643186264
Ref: Library<75>-Footnote-653186308
Ref: Library<75>-Footnote-663186352
Ref: Library<75>-Footnote-673186396
Ref: Library<75>-Footnote-683186440
Ref: Library<75>-Footnote-693186484
Ref: Library<75>-Footnote-703186528
Node: IDLE<50>3186572
Ref: whatsnew/changelog id4973186695
Ref: 11b53186695
Ref: IDLE<50>-Footnote-13191648
Ref: IDLE<50>-Footnote-23191691
Ref: IDLE<50>-Footnote-33191734
Ref: IDLE<50>-Footnote-43191777
Ref: IDLE<50>-Footnote-53191820
Ref: IDLE<50>-Footnote-63191863
Ref: IDLE<50>-Footnote-73191906
Ref: IDLE<50>-Footnote-83191949
Ref: IDLE<50>-Footnote-93191992
Ref: IDLE<50>-Footnote-103192035
Ref: IDLE<50>-Footnote-113192079
Ref: IDLE<50>-Footnote-123192123
Ref: IDLE<50>-Footnote-133192167
Ref: IDLE<50>-Footnote-143192211
Ref: IDLE<50>-Footnote-153192255
Ref: IDLE<50>-Footnote-163192299
Ref: IDLE<50>-Footnote-173192343
Ref: IDLE<50>-Footnote-183192387
Ref: IDLE<50>-Footnote-193192431
Ref: IDLE<50>-Footnote-203192475
Ref: IDLE<50>-Footnote-213192519
Ref: IDLE<50>-Footnote-223192563
Ref: IDLE<50>-Footnote-233192607
Ref: IDLE<50>-Footnote-243192651
Ref: IDLE<50>-Footnote-253192695
Node: Documentation<49>3192739
Ref: whatsnew/changelog id4983192860
Ref: 11b63192860
Ref: Documentation<49>-Footnote-13193933
Ref: Documentation<49>-Footnote-23193976
Ref: Documentation<49>-Footnote-33194019
Ref: Documentation<49>-Footnote-43194062
Ref: Documentation<49>-Footnote-53194105
Ref: Documentation<49>-Footnote-63194148
Node: Tests<48>3194191
Ref: whatsnew/changelog id4993194313
Ref: 11b73194313
Ref: Tests<48>-Footnote-13194820
Ref: Tests<48>-Footnote-23194863
Ref: Tests<48>-Footnote-33194906
Node: Build<48>3194949
Ref: whatsnew/changelog id5003195065
Ref: 11b83195065
Ref: Build<48>-Footnote-13195490
Ref: Build<48>-Footnote-23195533
Ref: Build<48>-Footnote-33195576
Node: Windows<49>3195619
Ref: whatsnew/changelog id5013195741
Ref: 11b93195741
Ref: Windows<49>-Footnote-13197014
Ref: Windows<49>-Footnote-23197057
Ref: Windows<49>-Footnote-33197100
Ref: Windows<49>-Footnote-43197143
Ref: Windows<49>-Footnote-53197186
Ref: Windows<49>-Footnote-63197229
Ref: Windows<49>-Footnote-73197272
Ref: Windows<49>-Footnote-83197315
Ref: Windows<49>-Footnote-93197358
Ref: Windows<49>-Footnote-103197401
Ref: Windows<49>-Footnote-113197445
Ref: Windows<49>-Footnote-123197489
Ref: Windows<49>-Footnote-133197533
Ref: Windows<49>-Footnote-143197577
Node: Tools/Demos<32>3197621
Ref: whatsnew/changelog id5023197725
Ref: 11ba3197725
Ref: Tools/Demos<32>-Footnote-13197875
Node: Python 3 5 0 final3197918
Ref: whatsnew/changelog python-3-5-0-final3198082
Ref: 11bb3198082
Node: Build<49>3198195
Ref: whatsnew/changelog id5033198259
Ref: 11bc3198259
Ref: Build<49>-Footnote-13198435
Node: Python 3 5 0 release candidate 43198478
Ref: whatsnew/changelog python-3-5-0-release-candidate-43198642
Ref: 11bd3198642
Node: Library<76>3198807
Ref: whatsnew/changelog id5043198905
Ref: 11be3198905
Ref: Library<76>-Footnote-13199034
Node: Build<50>3199077
Ref: whatsnew/changelog id5053199175
Ref: 11bf3199175
Ref: Build<50>-Footnote-13199357
Node: Python 3 5 0 release candidate 33199400
Ref: whatsnew/changelog python-3-5-0-release-candidate-33199578
Ref: 11c03199578
Node: Core and Builtins<63>3199767
Ref: whatsnew/changelog id5063199877
Ref: 11c13199877
Ref: Core and Builtins<63>-Footnote-13200245
Ref: Core and Builtins<63>-Footnote-23200288
Ref: Core and Builtins<63>-Footnote-33200331
Ref: Core and Builtins<63>-Footnote-43200374
Node: Library<77>3200423
Ref: whatsnew/changelog id5073200533
Ref: 11c23200533
Ref: Library<77>-Footnote-13201307
Ref: Library<77>-Footnote-23201350
Ref: Library<77>-Footnote-33201393
Ref: Library<77>-Footnote-43201436
Ref: Library<77>-Footnote-53201479
Node: Python 3 5 0 release candidate 23201522
Ref: whatsnew/changelog python-3-5-0-release-candidate-23201700
Ref: 11c33201700
Node: Core and Builtins<64>3201889
Ref: whatsnew/changelog id5083201999
Ref: 11c43201999
Ref: Core and Builtins<64>-Footnote-13202539
Ref: Core and Builtins<64>-Footnote-23202582
Ref: Core and Builtins<64>-Footnote-33202625
Node: Library<78>3202668
Ref: whatsnew/changelog id5093202778
Ref: 11c53202778
Ref: Library<78>-Footnote-13203059
Ref: Library<78>-Footnote-23203102
Ref: Library<78>-Footnote-33203145
Node: Python 3 5 0 release candidate 13203188
Ref: whatsnew/changelog python-3-5-0-release-candidate-13203353
Ref: 11c63203353
Node: Core and Builtins<65>3203616
Ref: whatsnew/changelog id5103203726
Ref: 11c73203726
Ref: Core and Builtins<65>-Footnote-13203904
Node: Library<79>3203947
Ref: whatsnew/changelog id5113204074
Ref: 11c83204074
Ref: Library<79>-Footnote-13205656
Ref: Library<79>-Footnote-23205699
Ref: Library<79>-Footnote-33205742
Ref: Library<79>-Footnote-43205785
Ref: Library<79>-Footnote-53205827
Ref: Library<79>-Footnote-63205870
Ref: Library<79>-Footnote-73205913
Ref: Library<79>-Footnote-83205956
Ref: Library<79>-Footnote-93205999
Ref: Library<79>-Footnote-103206042
Ref: Library<79>-Footnote-113206086
Ref: Library<79>-Footnote-123206130
Ref: Library<79>-Footnote-133206174
Ref: Library<79>-Footnote-143206218
Ref: Library<79>-Footnote-153206262
Node: IDLE<51>3206306
Ref: whatsnew/changelog id5123206429
Ref: 11c93206429
Ref: IDLE<51>-Footnote-13207174
Ref: IDLE<51>-Footnote-23207217
Ref: IDLE<51>-Footnote-33207260
Ref: IDLE<51>-Footnote-43207303
Node: Documentation<50>3207346
Ref: whatsnew/changelog id5133207467
Ref: 11ca3207467
Ref: Documentation<50>-Footnote-13208127
Ref: Documentation<50>-Footnote-23208170
Ref: Documentation<50>-Footnote-33208213
Ref: Documentation<50>-Footnote-43208256
Node: Tests<49>3208299
Ref: whatsnew/changelog id5143208403
Ref: 11cb3208403
Ref: Tests<49>-Footnote-13208641
Node: Python 3 5 0 beta 43208684
Ref: whatsnew/changelog python-3-5-0-beta-43208836
Ref: 11cc3208836
Node: Core and Builtins<66>3209019
Ref: whatsnew/changelog id5153209116
Ref: 11cd3209116
Ref: Core and Builtins<66>-Footnote-13209920
Ref: Core and Builtins<66>-Footnote-23209963
Ref: Core and Builtins<66>-Footnote-33210006
Ref: Core and Builtins<66>-Footnote-43210055
Ref: Core and Builtins<66>-Footnote-53210098
Ref: Core and Builtins<66>-Footnote-63210141
Ref: Core and Builtins<66>-Footnote-73210184
Ref: Core and Builtins<66>-Footnote-83210227
Node: Library<80>3210270
Ref: whatsnew/changelog id5163210385
Ref: 11ce3210385
Ref: Library<80>-Footnote-13212672
Ref: Library<80>-Footnote-23212715
Ref: Library<80>-Footnote-33212758
Ref: Library<80>-Footnote-43212801
Ref: Library<80>-Footnote-53212844
Ref: Library<80>-Footnote-63212887
Ref: Library<80>-Footnote-73212930
Ref: Library<80>-Footnote-83212973
Ref: Library<80>-Footnote-93213016
Ref: Library<80>-Footnote-103213059
Ref: Library<80>-Footnote-113213103
Ref: Library<80>-Footnote-123213147
Ref: Library<80>-Footnote-133213191
Ref: Library<80>-Footnote-143213235
Ref: Library<80>-Footnote-153213279
Ref: Library<80>-Footnote-163213323
Ref: Library<80>-Footnote-173213367
Ref: Library<80>-Footnote-183213411
Ref: Library<80>-Footnote-193213455
Node: Build<51>3213499
Ref: whatsnew/changelog id5173213584
Ref: 11cf3213584
Ref: Build<51>-Footnote-13213747
Node: Python 3 5 0 beta 33213790
Ref: whatsnew/changelog python-3-5-0-beta-33213929
Ref: 11d03213929
Node: Core and Builtins<67>3214168
Ref: whatsnew/changelog id5183214265
Ref: 11d13214265
Ref: Core and Builtins<67>-Footnote-13215590
Ref: Core and Builtins<67>-Footnote-23215633
Ref: Core and Builtins<67>-Footnote-33215676
Ref: Core and Builtins<67>-Footnote-43215719
Ref: Core and Builtins<67>-Footnote-53215768
Ref: Core and Builtins<67>-Footnote-63215811
Node: Library<81>3215854
Ref: whatsnew/changelog id5193215969
Ref: 11d23215969
Ref: Library<81>-Footnote-13217921
Ref: Library<81>-Footnote-23217964
Ref: Library<81>-Footnote-33218007
Ref: Library<81>-Footnote-43218050
Ref: Library<81>-Footnote-53218093
Ref: Library<81>-Footnote-63218136
Ref: Library<81>-Footnote-73218179
Ref: Library<81>-Footnote-83218222
Ref: Library<81>-Footnote-93218265
Ref: Library<81>-Footnote-103218308
Ref: Library<81>-Footnote-113218352
Ref: Library<81>-Footnote-123218396
Ref: Library<81>-Footnote-133218440
Ref: Library<81>-Footnote-143218484
Ref: Library<81>-Footnote-153218528
Ref: Library<81>-Footnote-163218572
Ref: Library<81>-Footnote-173218616
Ref: Library<81>-Footnote-183218660
Node: Tests<50>3218704
Ref: whatsnew/changelog id5203218815
Ref: 11d33218815
Ref: Tests<50>-Footnote-13219095
Ref: Tests<50>-Footnote-23219138
Node: Documentation<51>3219181
Ref: whatsnew/changelog id5213219290
Ref: 11d43219290
Ref: Documentation<51>-Footnote-13219628
Ref: Documentation<51>-Footnote-23219671
Node: Build<52>3219714
Ref: whatsnew/changelog id5223219805
Ref: 11d53219805
Ref: Build<52>-Footnote-13219968
Node: Python 3 5 0 beta 23220011
Ref: whatsnew/changelog python-3-5-0-beta-23220150
Ref: 11d63220150
Node: Core and Builtins<68>3220313
Ref: whatsnew/changelog id5233220410
Ref: 11d73220410
Ref: Core and Builtins<68>-Footnote-13221161
Ref: Core and Builtins<68>-Footnote-23221204
Ref: Core and Builtins<68>-Footnote-33221247
Ref: Core and Builtins<68>-Footnote-43221290
Ref: Core and Builtins<68>-Footnote-53221333
Node: Library<82>3221376
Ref: whatsnew/changelog id5243221473
Ref: 11d83221473
Ref: Library<82>-Footnote-13222178
Ref: Library<82>-Footnote-23222221
Ref: Library<82>-Footnote-33222264
Ref: Library<82>-Footnote-43222313
Ref: Library<82>-Footnote-53222355
Ref: Library<82>-Footnote-63222398
Ref: Library<82>-Footnote-73222441
Node: Python 3 5 0 beta 13222484
Ref: whatsnew/changelog python-3-5-0-beta-13222624
Ref: 11d93222624
Node: Core and Builtins<69>3222893
Ref: whatsnew/changelog id5253222990
Ref: 11da3222990
Ref: Core and Builtins<69>-Footnote-13224861
Ref: Core and Builtins<69>-Footnote-23224904
Ref: Core and Builtins<69>-Footnote-33224947
Ref: Core and Builtins<69>-Footnote-43224990
Ref: Core and Builtins<69>-Footnote-53225033
Ref: Core and Builtins<69>-Footnote-63225076
Ref: Core and Builtins<69>-Footnote-73225119
Ref: Core and Builtins<69>-Footnote-83225162
Ref: Core and Builtins<69>-Footnote-93225205
Ref: Core and Builtins<69>-Footnote-103225248
Ref: Core and Builtins<69>-Footnote-113225291
Ref: Core and Builtins<69>-Footnote-123225335
Ref: Core and Builtins<69>-Footnote-133225379
Ref: Core and Builtins<69>-Footnote-143225423
Ref: Core and Builtins<69>-Footnote-153225467
Ref: Core and Builtins<69>-Footnote-163225511
Ref: Core and Builtins<69>-Footnote-173225555
Ref: Core and Builtins<69>-Footnote-183225598
Ref: Core and Builtins<69>-Footnote-193225642
Node: Library<83>3225686
Ref: whatsnew/changelog id5263225800
Ref: 11db3225800
Ref: Library<83>-Footnote-13233456
Ref: Library<83>-Footnote-23233499
Ref: Library<83>-Footnote-33233542
Ref: Library<83>-Footnote-43233585
Ref: Library<83>-Footnote-53233628
Ref: Library<83>-Footnote-63233671
Ref: Library<83>-Footnote-73233714
Ref: Library<83>-Footnote-83233757
Ref: Library<83>-Footnote-93233800
Ref: Library<83>-Footnote-103233843
Ref: Library<83>-Footnote-113233886
Ref: Library<83>-Footnote-123233930
Ref: Library<83>-Footnote-133233974
Ref: Library<83>-Footnote-143234018
Ref: Library<83>-Footnote-153234061
Ref: Library<83>-Footnote-163234105
Ref: Library<83>-Footnote-173234149
Ref: Library<83>-Footnote-183234193
Ref: Library<83>-Footnote-193234237
Ref: Library<83>-Footnote-203234281
Ref: Library<83>-Footnote-213234325
Ref: Library<83>-Footnote-223234369
Ref: Library<83>-Footnote-233234413
Ref: Library<83>-Footnote-243234457
Ref: Library<83>-Footnote-253234501
Ref: Library<83>-Footnote-263234544
Ref: Library<83>-Footnote-273234588
Ref: Library<83>-Footnote-283234632
Ref: Library<83>-Footnote-293234676
Ref: Library<83>-Footnote-303234720
Ref: Library<83>-Footnote-313234764
Ref: Library<83>-Footnote-323234808
Ref: Library<83>-Footnote-333234852
Ref: Library<83>-Footnote-343234896
Ref: Library<83>-Footnote-353234940
Ref: Library<83>-Footnote-363234984
Ref: Library<83>-Footnote-373235028
Ref: Library<83>-Footnote-383235072
Ref: Library<83>-Footnote-393235116
Ref: Library<83>-Footnote-403235160
Ref: Library<83>-Footnote-413235204
Ref: Library<83>-Footnote-423235247
Ref: Library<83>-Footnote-433235291
Ref: Library<83>-Footnote-443235335
Ref: Library<83>-Footnote-453235379
Ref: Library<83>-Footnote-463235423
Ref: Library<83>-Footnote-473235467
Ref: Library<83>-Footnote-483235511
Ref: Library<83>-Footnote-493235555
Ref: Library<83>-Footnote-503235599
Ref: Library<83>-Footnote-513235643
Ref: Library<83>-Footnote-523235687
Ref: Library<83>-Footnote-533235731
Ref: Library<83>-Footnote-543235775
Ref: Library<83>-Footnote-553235819
Ref: Library<83>-Footnote-563235863
Node: IDLE<52>3235907
Ref: whatsnew/changelog id5273236009
Ref: 11dc3236009
Ref: IDLE<52>-Footnote-13236176
Node: Tests<51>3236219
Ref: whatsnew/changelog id5283236327
Ref: 11dd3236327
Ref: Tests<51>-Footnote-13236623
Ref: Tests<51>-Footnote-23236666
Node: Documentation<52>3236708
Ref: whatsnew/changelog id5293236823
Ref: 11de3236823
Ref: Documentation<52>-Footnote-13237228
Ref: Documentation<52>-Footnote-23237271
Ref: Documentation<52>-Footnote-33237314
Node: Tools/Demos<33>3237357
Ref: whatsnew/changelog id5303237454
Ref: 11df3237454
Ref: Tools/Demos<33>-Footnote-13237967
Ref: Tools/Demos<33>-Footnote-23238010
Ref: Tools/Demos<33>-Footnote-33238053
Ref: Tools/Demos<33>-Footnote-43238096
Node: Python 3 5 0 alpha 43238139
Ref: whatsnew/changelog python-3-5-0-alpha-43238280
Ref: 11e03238280
Node: Core and Builtins<70>3238537
Ref: whatsnew/changelog id5313238635
Ref: 11e13238635
Ref: Core and Builtins<70>-Footnote-13240002
Ref: Core and Builtins<70>-Footnote-23240045
Ref: Core and Builtins<70>-Footnote-33240094
Ref: Core and Builtins<70>-Footnote-43240137
Ref: Core and Builtins<70>-Footnote-53240180
Ref: Core and Builtins<70>-Footnote-63240229
Ref: Core and Builtins<70>-Footnote-73240272
Ref: Core and Builtins<70>-Footnote-83240315
Ref: Core and Builtins<70>-Footnote-93240358
Ref: Core and Builtins<70>-Footnote-103240401
Ref: Core and Builtins<70>-Footnote-113240445
Node: Library<84>3240489
Ref: whatsnew/changelog id5323240605
Ref: 11e23240605
Ref: Library<84>-Footnote-13247316
Ref: Library<84>-Footnote-23247359
Ref: Library<84>-Footnote-33247402
Ref: Library<84>-Footnote-43247444
Ref: Library<84>-Footnote-53247487
Ref: Library<84>-Footnote-63247530
Ref: Library<84>-Footnote-73247572
Ref: Library<84>-Footnote-83247615
Ref: Library<84>-Footnote-93247658
Ref: Library<84>-Footnote-103247701
Ref: Library<84>-Footnote-113247745
Ref: Library<84>-Footnote-123247789
Ref: Library<84>-Footnote-133247833
Ref: Library<84>-Footnote-143247877
Ref: Library<84>-Footnote-153247921
Ref: Library<84>-Footnote-163247965
Ref: Library<84>-Footnote-173248009
Ref: Library<84>-Footnote-183248053
Ref: Library<84>-Footnote-193248097
Ref: Library<84>-Footnote-203248141
Ref: Library<84>-Footnote-213248185
Ref: Library<84>-Footnote-223248229
Ref: Library<84>-Footnote-233248273
Ref: Library<84>-Footnote-243248317
Ref: Library<84>-Footnote-253248361
Ref: Library<84>-Footnote-263248405
Ref: Library<84>-Footnote-273248449
Ref: Library<84>-Footnote-283248493
Ref: Library<84>-Footnote-293248537
Ref: Library<84>-Footnote-303248581
Ref: Library<84>-Footnote-313248624
Ref: Library<84>-Footnote-323248668
Ref: Library<84>-Footnote-333248712
Ref: Library<84>-Footnote-343248756
Ref: Library<84>-Footnote-353248800
Ref: Library<84>-Footnote-363248844
Ref: Library<84>-Footnote-373248888
Ref: Library<84>-Footnote-383248932
Ref: Library<84>-Footnote-393248976
Ref: Library<84>-Footnote-403249020
Ref: Library<84>-Footnote-413249064
Ref: Library<84>-Footnote-423249108
Ref: Library<84>-Footnote-433249158
Ref: Library<84>-Footnote-443249202
Ref: Library<84>-Footnote-453249246
Ref: Library<84>-Footnote-463249290
Ref: Library<84>-Footnote-473249334
Ref: Library<84>-Footnote-483249378
Node: Build<53>3249422
Ref: whatsnew/changelog id5333249526
Ref: 11e33249526
Ref: Build<53>-Footnote-13249801
Ref: Build<53>-Footnote-23249844
Node: Tests<52>3249887
Ref: whatsnew/changelog id5343249995
Ref: 11e43249995
Ref: Tests<52>-Footnote-13250294
Ref: Tests<52>-Footnote-23250337
Node: Tools/Demos<34>3250380
Ref: whatsnew/changelog id5353250488
Ref: 11e53250488
Ref: Tools/Demos<34>-Footnote-13251516
Ref: Tools/Demos<34>-Footnote-23251559
Ref: Tools/Demos<34>-Footnote-33251602
Ref: Tools/Demos<34>-Footnote-43251645
Ref: Tools/Demos<34>-Footnote-53251688
Ref: Tools/Demos<34>-Footnote-63251731
Node: C API<36>3251774
Ref: whatsnew/changelog id5363251864
Ref: 11e63251864
Ref: C API<36>-Footnote-13252017
Node: Python 3 5 0 alpha 33252060
Ref: whatsnew/changelog python-3-5-0-alpha-33252202
Ref: 11e73252202
Node: Core and Builtins<71>3252439
Ref: whatsnew/changelog id5373252537
Ref: 11e83252537
Ref: Core and Builtins<71>-Footnote-13253331
Ref: Core and Builtins<71>-Footnote-23253374
Ref: Core and Builtins<71>-Footnote-33253417
Ref: Core and Builtins<71>-Footnote-43253460
Ref: Core and Builtins<71>-Footnote-53253503
Ref: Core and Builtins<71>-Footnote-63253546
Node: Library<85>3253589
Ref: whatsnew/changelog id5383253705
Ref: 11e93253705
Ref: Library<85>-Footnote-13260119
Ref: Library<85>-Footnote-23260162
Ref: Library<85>-Footnote-33260205
Ref: Library<85>-Footnote-43260248
Ref: Library<85>-Footnote-53260291
Ref: Library<85>-Footnote-63260334
Ref: Library<85>-Footnote-73260377
Ref: Library<85>-Footnote-83260420
Ref: Library<85>-Footnote-93260463
Ref: Library<85>-Footnote-103260506
Ref: Library<85>-Footnote-113260550
Ref: Library<85>-Footnote-123260594
Ref: Library<85>-Footnote-133260638
Ref: Library<85>-Footnote-143260682
Ref: Library<85>-Footnote-153260725
Ref: Library<85>-Footnote-163260769
Ref: Library<85>-Footnote-173260813
Ref: Library<85>-Footnote-183260857
Ref: Library<85>-Footnote-193260901
Ref: Library<85>-Footnote-203260945
Ref: Library<85>-Footnote-213260989
Ref: Library<85>-Footnote-223261033
Ref: Library<85>-Footnote-233261077
Ref: Library<85>-Footnote-243261121
Ref: Library<85>-Footnote-253261165
Ref: Library<85>-Footnote-263261209
Ref: Library<85>-Footnote-273261253
Ref: Library<85>-Footnote-283261297
Ref: Library<85>-Footnote-293261341
Ref: Library<85>-Footnote-303261385
Ref: Library<85>-Footnote-313261428
Ref: Library<85>-Footnote-323261472
Ref: Library<85>-Footnote-333261516
Ref: Library<85>-Footnote-343261560
Ref: Library<85>-Footnote-353261603
Ref: Library<85>-Footnote-363261647
Ref: Library<85>-Footnote-373261691
Ref: Library<85>-Footnote-383261735
Ref: Library<85>-Footnote-393261779
Ref: Library<85>-Footnote-403261823
Ref: Library<85>-Footnote-413261867
Ref: Library<85>-Footnote-423261911
Node: Build<54>3261955
Ref: whatsnew/changelog id5393262059
Ref: 11ea3262059
Ref: Build<54>-Footnote-13262202
Node: Tests<53>3262245
Ref: whatsnew/changelog id5403262353
Ref: 11eb3262353
Ref: Tests<53>-Footnote-13262576
Ref: Tests<53>-Footnote-23262619
Node: Tools/Demos<35>3262662
Ref: whatsnew/changelog id5413262752
Ref: 11ec3262752
Ref: Tools/Demos<35>-Footnote-13263019
Node: Python 3 5 0 alpha 23263062
Ref: whatsnew/changelog python-3-5-0-alpha-23263204
Ref: 11ed3263204
Node: Core and Builtins<72>3263433
Ref: whatsnew/changelog id5423263531
Ref: 11ee3263531
Ref: Core and Builtins<72>-Footnote-13263827
Node: Library<86>3263870
Ref: whatsnew/changelog id5433263986
Ref: 11ef3263986
Ref: Library<86>-Footnote-13268297
Ref: Library<86>-Footnote-23268340
Ref: Library<86>-Footnote-33268389
Ref: Library<86>-Footnote-43268432
Ref: Library<86>-Footnote-53268475
Ref: Library<86>-Footnote-63268518
Ref: Library<86>-Footnote-73268561
Ref: Library<86>-Footnote-83268604
Ref: Library<86>-Footnote-93268647
Ref: Library<86>-Footnote-103268689
Ref: Library<86>-Footnote-113268733
Ref: Library<86>-Footnote-123268777
Ref: Library<86>-Footnote-133268821
Ref: Library<86>-Footnote-143268865
Ref: Library<86>-Footnote-153268909
Ref: Library<86>-Footnote-163268953
Ref: Library<86>-Footnote-173268996
Ref: Library<86>-Footnote-183269041
Ref: Library<86>-Footnote-193269084
Ref: Library<86>-Footnote-203269128
Ref: Library<86>-Footnote-213269171
Ref: Library<86>-Footnote-223269215
Ref: Library<86>-Footnote-233269259
Ref: Library<86>-Footnote-243269303
Ref: Library<86>-Footnote-253269347
Ref: Library<86>-Footnote-263269391
Ref: Library<86>-Footnote-273269435
Ref: Library<86>-Footnote-283269479
Ref: Library<86>-Footnote-293269523
Ref: Library<86>-Footnote-303269567
Ref: Library<86>-Footnote-313269611
Ref: Library<86>-Footnote-323269655
Ref: Library<86>-Footnote-333269699
Ref: Library<86>-Footnote-343269743
Ref: Library<86>-Footnote-353269787
Ref: Library<86>-Footnote-363269831
Ref: Library<86>-Footnote-373269875
Node: Build<55>3269919
Ref: whatsnew/changelog id5443270023
Ref: 11f03270023
Ref: Build<55>-Footnote-13270288
Ref: Build<55>-Footnote-23270331
Node: C API<37>3270374
Ref: whatsnew/changelog id5453270478
Ref: 11f13270478
Ref: C API<37>-Footnote-13270658
Node: Windows<50>3270701
Ref: whatsnew/changelog id5463270787
Ref: 11f23270787
Ref: Windows<50>-Footnote-13271082
Ref: Windows<50>-Footnote-23271125
Ref: Windows<50>-Footnote-33271174
Node: Python 3 5 0 alpha 13271217
Ref: whatsnew/changelog python-3-5-0-alpha-13271330
Ref: 11f33271330
Node: Core and Builtins<73>3271665
Ref: whatsnew/changelog id5473271763
Ref: 11f43271763
Ref: Core and Builtins<73>-Footnote-13281653
Ref: Core and Builtins<73>-Footnote-23281696
Ref: Core and Builtins<73>-Footnote-33281739
Ref: Core and Builtins<73>-Footnote-43281782
Ref: Core and Builtins<73>-Footnote-53281825
Ref: Core and Builtins<73>-Footnote-63281868
Ref: Core and Builtins<73>-Footnote-73281911
Ref: Core and Builtins<73>-Footnote-83281954
Ref: Core and Builtins<73>-Footnote-93281997
Ref: Core and Builtins<73>-Footnote-103282040
Ref: Core and Builtins<73>-Footnote-113282084
Ref: Core and Builtins<73>-Footnote-123282128
Ref: Core and Builtins<73>-Footnote-133282172
Ref: Core and Builtins<73>-Footnote-143282216
Ref: Core and Builtins<73>-Footnote-153282260
Ref: Core and Builtins<73>-Footnote-163282304
Ref: Core and Builtins<73>-Footnote-173282348
Ref: Core and Builtins<73>-Footnote-183282392
Ref: Core and Builtins<73>-Footnote-193282436
Ref: Core and Builtins<73>-Footnote-203282480
Ref: Core and Builtins<73>-Footnote-213282524
Ref: Core and Builtins<73>-Footnote-223282568
Ref: Core and Builtins<73>-Footnote-233282612
Ref: Core and Builtins<73>-Footnote-243282656
Ref: Core and Builtins<73>-Footnote-253282700
Ref: Core and Builtins<73>-Footnote-263282744
Ref: Core and Builtins<73>-Footnote-273282788
Ref: Core and Builtins<73>-Footnote-283282832
Ref: Core and Builtins<73>-Footnote-293282876
Ref: Core and Builtins<73>-Footnote-303282920
Ref: Core and Builtins<73>-Footnote-313282964
Ref: Core and Builtins<73>-Footnote-323283008
Ref: Core and Builtins<73>-Footnote-333283052
Ref: Core and Builtins<73>-Footnote-343283098
Ref: Core and Builtins<73>-Footnote-353283142
Ref: Core and Builtins<73>-Footnote-363283186
Ref: Core and Builtins<73>-Footnote-373283230
Ref: Core and Builtins<73>-Footnote-383283274
Ref: Core and Builtins<73>-Footnote-393283318
Ref: Core and Builtins<73>-Footnote-403283362
Ref: Core and Builtins<73>-Footnote-413283406
Ref: Core and Builtins<73>-Footnote-423283450
Ref: Core and Builtins<73>-Footnote-433283494
Ref: Core and Builtins<73>-Footnote-443283538
Ref: Core and Builtins<73>-Footnote-453283582
Ref: Core and Builtins<73>-Footnote-463283626
Ref: Core and Builtins<73>-Footnote-473283670
Ref: Core and Builtins<73>-Footnote-483283714
Ref: Core and Builtins<73>-Footnote-493283758
Ref: Core and Builtins<73>-Footnote-503283802
Ref: Core and Builtins<73>-Footnote-513283846
Ref: Core and Builtins<73>-Footnote-523283890
Ref: Core and Builtins<73>-Footnote-533283934
Ref: Core and Builtins<73>-Footnote-543283978
Ref: Core and Builtins<73>-Footnote-553284022
Ref: Core and Builtins<73>-Footnote-563284066
Ref: Core and Builtins<73>-Footnote-573284110
Ref: Core and Builtins<73>-Footnote-583284154
Ref: Core and Builtins<73>-Footnote-593284198
Ref: Core and Builtins<73>-Footnote-603284242
Ref: Core and Builtins<73>-Footnote-613284286
Ref: Core and Builtins<73>-Footnote-623284330
Ref: Core and Builtins<73>-Footnote-633284374
Ref: Core and Builtins<73>-Footnote-643284418
Ref: Core and Builtins<73>-Footnote-653284462
Ref: Core and Builtins<73>-Footnote-663284506
Ref: Core and Builtins<73>-Footnote-673284549
Ref: Core and Builtins<73>-Footnote-683284593
Ref: Core and Builtins<73>-Footnote-693284637
Ref: Core and Builtins<73>-Footnote-703284681
Ref: Core and Builtins<73>-Footnote-713284725
Ref: Core and Builtins<73>-Footnote-723284769
Ref: Core and Builtins<73>-Footnote-733284812
Node: Library<87>3284856
Ref: whatsnew/changelog id5483284971
Ref: 11f53284971
Ref: Library<87>-Footnote-13337334
Ref: Library<87>-Footnote-23337377
Ref: Library<87>-Footnote-33337420
Ref: Library<87>-Footnote-43337463
Ref: Library<87>-Footnote-53337506
Ref: Library<87>-Footnote-63337549
Ref: Library<87>-Footnote-73337592
Ref: Library<87>-Footnote-83337635
Ref: Library<87>-Footnote-93337678
Ref: Library<87>-Footnote-103337721
Ref: Library<87>-Footnote-113337765
Ref: Library<87>-Footnote-123337809
Ref: Library<87>-Footnote-133337853
Ref: Library<87>-Footnote-143337897
Ref: Library<87>-Footnote-153337941
Ref: Library<87>-Footnote-163337985
Ref: Library<87>-Footnote-173338029
Ref: Library<87>-Footnote-183338073
Ref: Library<87>-Footnote-193338117
Ref: Library<87>-Footnote-203338161
Ref: Library<87>-Footnote-213338205
Ref: Library<87>-Footnote-223338249
Ref: Library<87>-Footnote-233338293
Ref: Library<87>-Footnote-243338337
Ref: Library<87>-Footnote-253338381
Ref: Library<87>-Footnote-263338425
Ref: Library<87>-Footnote-273338469
Ref: Library<87>-Footnote-283338513
Ref: Library<87>-Footnote-293338557
Ref: Library<87>-Footnote-303338601
Ref: Library<87>-Footnote-313338645
Ref: Library<87>-Footnote-323338689
Ref: Library<87>-Footnote-333338733
Ref: Library<87>-Footnote-343338777
Ref: Library<87>-Footnote-353338821
Ref: Library<87>-Footnote-363338865
Ref: Library<87>-Footnote-373338909
Ref: Library<87>-Footnote-383338953
Ref: Library<87>-Footnote-393338997
Ref: Library<87>-Footnote-403339041
Ref: Library<87>-Footnote-413339085
Ref: Library<87>-Footnote-423339129
Ref: Library<87>-Footnote-433339173
Ref: Library<87>-Footnote-443339217
Ref: Library<87>-Footnote-453339261
Ref: Library<87>-Footnote-463339305
Ref: Library<87>-Footnote-473339349
Ref: Library<87>-Footnote-483339393
Ref: Library<87>-Footnote-493339437
Ref: Library<87>-Footnote-503339481
Ref: Library<87>-Footnote-513339525
Ref: Library<87>-Footnote-523339569
Ref: Library<87>-Footnote-533339613
Ref: Library<87>-Footnote-543339657
Ref: Library<87>-Footnote-553339701
Ref: Library<87>-Footnote-563339747
Ref: Library<87>-Footnote-573339791
Ref: Library<87>-Footnote-583339835
Ref: Library<87>-Footnote-593339879
Ref: Library<87>-Footnote-603339923
Ref: Library<87>-Footnote-613339967
Ref: Library<87>-Footnote-623340011
Ref: Library<87>-Footnote-633340055
Ref: Library<87>-Footnote-643340099
Ref: Library<87>-Footnote-653340143
Ref: Library<87>-Footnote-663340187
Ref: Library<87>-Footnote-673340231
Ref: Library<87>-Footnote-683340275
Ref: Library<87>-Footnote-693340319
Ref: Library<87>-Footnote-703340363
Ref: Library<87>-Footnote-713340407
Ref: Library<87>-Footnote-723340451
Ref: Library<87>-Footnote-733340495
Ref: Library<87>-Footnote-743340539
Ref: Library<87>-Footnote-753340583
Ref: Library<87>-Footnote-763340627
Ref: Library<87>-Footnote-773340671
Ref: Library<87>-Footnote-783340715
Ref: Library<87>-Footnote-793340759
Ref: Library<87>-Footnote-803340803
Ref: Library<87>-Footnote-813340847
Ref: Library<87>-Footnote-823340891
Ref: Library<87>-Footnote-833340935
Ref: Library<87>-Footnote-843340979
Ref: Library<87>-Footnote-853341023
Ref: Library<87>-Footnote-863341067
Ref: Library<87>-Footnote-873341111
Ref: Library<87>-Footnote-883341155
Ref: Library<87>-Footnote-893341199
Ref: Library<87>-Footnote-903341243
Ref: Library<87>-Footnote-913341287
Ref: Library<87>-Footnote-923341331
Ref: Library<87>-Footnote-933341375
Ref: Library<87>-Footnote-943341419
Ref: Library<87>-Footnote-953341463
Ref: Library<87>-Footnote-963341506
Ref: Library<87>-Footnote-973341550
Ref: Library<87>-Footnote-983341594
Ref: Library<87>-Footnote-993341638
Ref: Library<87>-Footnote-1003341681
Ref: Library<87>-Footnote-1013341726
Ref: Library<87>-Footnote-1023341771
Ref: Library<87>-Footnote-1033341816
Ref: Library<87>-Footnote-1043341861
Ref: Library<87>-Footnote-1053341906
Ref: Library<87>-Footnote-1063341951
Ref: Library<87>-Footnote-1073341995
Ref: Library<87>-Footnote-1083342039
Ref: Library<87>-Footnote-1093342084
Ref: Library<87>-Footnote-1103342129
Ref: Library<87>-Footnote-1113342174
Ref: Library<87>-Footnote-1123342219
Ref: Library<87>-Footnote-1133342264
Ref: Library<87>-Footnote-1143342309
Ref: Library<87>-Footnote-1153342354
Ref: Library<87>-Footnote-1163342399
Ref: Library<87>-Footnote-1173342444
Ref: Library<87>-Footnote-1183342489
Ref: Library<87>-Footnote-1193342534
Ref: Library<87>-Footnote-1203342579
Ref: Library<87>-Footnote-1213342626
Ref: Library<87>-Footnote-1223342671
Ref: Library<87>-Footnote-1233342716
Ref: Library<87>-Footnote-1243342761
Ref: Library<87>-Footnote-1253342806
Ref: Library<87>-Footnote-1263342851
Ref: Library<87>-Footnote-1273342896
Ref: Library<87>-Footnote-1283342941
Ref: Library<87>-Footnote-1293342986
Ref: Library<87>-Footnote-1303343031
Ref: Library<87>-Footnote-1313343076
Ref: Library<87>-Footnote-1323343121
Ref: Library<87>-Footnote-1333343166
Ref: Library<87>-Footnote-1343343211
Ref: Library<87>-Footnote-1353343256
Ref: Library<87>-Footnote-1363343301
Ref: Library<87>-Footnote-1373343346
Ref: Library<87>-Footnote-1383343391
Ref: Library<87>-Footnote-1393343436
Ref: Library<87>-Footnote-1403343481
Ref: Library<87>-Footnote-1413343526
Ref: Library<87>-Footnote-1423343570
Ref: Library<87>-Footnote-1433343614
Ref: Library<87>-Footnote-1443343659
Ref: Library<87>-Footnote-1453343704
Ref: Library<87>-Footnote-1463343749
Ref: Library<87>-Footnote-1473343794
Ref: Library<87>-Footnote-1483343839
Ref: Library<87>-Footnote-1493343884
Ref: Library<87>-Footnote-1503343929
Ref: Library<87>-Footnote-1513343974
Ref: Library<87>-Footnote-1523344019
Ref: Library<87>-Footnote-1533344064
Ref: Library<87>-Footnote-1543344109
Ref: Library<87>-Footnote-1553344154
Ref: Library<87>-Footnote-1563344199
Ref: Library<87>-Footnote-1573344243
Ref: Library<87>-Footnote-1583344288
Ref: Library<87>-Footnote-1593344333
Ref: Library<87>-Footnote-1603344378
Ref: Library<87>-Footnote-1613344423
Ref: Library<87>-Footnote-1623344468
Ref: Library<87>-Footnote-1633344513
Ref: Library<87>-Footnote-1643344558
Ref: Library<87>-Footnote-1653344603
Ref: Library<87>-Footnote-1663344648
Ref: Library<87>-Footnote-1673344693
Ref: Library<87>-Footnote-1683344738
Ref: Library<87>-Footnote-1693344783
Ref: Library<87>-Footnote-1703344828
Ref: Library<87>-Footnote-1713344873
Ref: Library<87>-Footnote-1723344918
Ref: Library<87>-Footnote-1733344963
Ref: Library<87>-Footnote-1743345008
Ref: Library<87>-Footnote-1753345053
Ref: Library<87>-Footnote-1763345098
Ref: Library<87>-Footnote-1773345143
Ref: Library<87>-Footnote-1783345188
Ref: Library<87>-Footnote-1793345233
Ref: Library<87>-Footnote-1803345278
Ref: Library<87>-Footnote-1813345323
Ref: Library<87>-Footnote-1823345368
Ref: Library<87>-Footnote-1833345413
Ref: Library<87>-Footnote-1843345458
Ref: Library<87>-Footnote-1853345503
Ref: Library<87>-Footnote-1863345548
Ref: Library<87>-Footnote-1873345593
Ref: Library<87>-Footnote-1883345637
Ref: Library<87>-Footnote-1893345682
Ref: Library<87>-Footnote-1903345727
Ref: Library<87>-Footnote-1913345772
Ref: Library<87>-Footnote-1923345817
Ref: Library<87>-Footnote-1933345862
Ref: Library<87>-Footnote-1943345907
Ref: Library<87>-Footnote-1953345952
Ref: Library<87>-Footnote-1963345996
Ref: Library<87>-Footnote-1973346041
Ref: Library<87>-Footnote-1983346086
Ref: Library<87>-Footnote-1993346131
Ref: Library<87>-Footnote-2003346176
Ref: Library<87>-Footnote-2013346221
Ref: Library<87>-Footnote-2023346266
Ref: Library<87>-Footnote-2033346310
Ref: Library<87>-Footnote-2043346355
Ref: Library<87>-Footnote-2053346400
Ref: Library<87>-Footnote-2063346445
Ref: Library<87>-Footnote-2073346490
Ref: Library<87>-Footnote-2083346535
Ref: Library<87>-Footnote-2093346580
Ref: Library<87>-Footnote-2103346625
Ref: Library<87>-Footnote-2113346670
Ref: Library<87>-Footnote-2123346715
Ref: Library<87>-Footnote-2133346760
Ref: Library<87>-Footnote-2143346805
Ref: Library<87>-Footnote-2153346850
Ref: Library<87>-Footnote-2163346895
Ref: Library<87>-Footnote-2173346940
Ref: Library<87>-Footnote-2183346985
Ref: Library<87>-Footnote-2193347030
Ref: Library<87>-Footnote-2203347075
Ref: Library<87>-Footnote-2213347120
Ref: Library<87>-Footnote-2223347165
Ref: Library<87>-Footnote-2233347210
Ref: Library<87>-Footnote-2243347254
Ref: Library<87>-Footnote-2253347298
Ref: Library<87>-Footnote-2263347343
Ref: Library<87>-Footnote-2273347388
Ref: Library<87>-Footnote-2283347433
Ref: Library<87>-Footnote-2293347478
Ref: Library<87>-Footnote-2303347523
Ref: Library<87>-Footnote-2313347568
Ref: Library<87>-Footnote-2323347613
Ref: Library<87>-Footnote-2333347658
Ref: Library<87>-Footnote-2343347703
Ref: Library<87>-Footnote-2353347748
Ref: Library<87>-Footnote-2363347793
Ref: Library<87>-Footnote-2373347838
Ref: Library<87>-Footnote-2383347883
Ref: Library<87>-Footnote-2393347928
Ref: Library<87>-Footnote-2403347973
Ref: Library<87>-Footnote-2413348018
Ref: Library<87>-Footnote-2423348063
Ref: Library<87>-Footnote-2433348108
Ref: Library<87>-Footnote-2443348153
Ref: Library<87>-Footnote-2453348197
Ref: Library<87>-Footnote-2463348242
Ref: Library<87>-Footnote-2473348287
Ref: Library<87>-Footnote-2483348332
Ref: Library<87>-Footnote-2493348377
Ref: Library<87>-Footnote-2503348422
Ref: Library<87>-Footnote-2513348467
Ref: Library<87>-Footnote-2523348512
Ref: Library<87>-Footnote-2533348557
Ref: Library<87>-Footnote-2543348602
Ref: Library<87>-Footnote-2553348647
Ref: Library<87>-Footnote-2563348692
Ref: Library<87>-Footnote-2573348737
Ref: Library<87>-Footnote-2583348782
Ref: Library<87>-Footnote-2593348827
Ref: Library<87>-Footnote-2603348872
Ref: Library<87>-Footnote-2613348917
Ref: Library<87>-Footnote-2623348962
Ref: Library<87>-Footnote-2633349007
Ref: Library<87>-Footnote-2643349052
Ref: Library<87>-Footnote-2653349097
Ref: Library<87>-Footnote-2663349142
Ref: Library<87>-Footnote-2673349187
Ref: Library<87>-Footnote-2683349232
Ref: Library<87>-Footnote-2693349277
Ref: Library<87>-Footnote-2703349322
Ref: Library<87>-Footnote-2713349367
Ref: Library<87>-Footnote-2723349412
Ref: Library<87>-Footnote-2733349457
Ref: Library<87>-Footnote-2743349502
Ref: Library<87>-Footnote-2753349547
Ref: Library<87>-Footnote-2763349592
Ref: Library<87>-Footnote-2773349636
Ref: Library<87>-Footnote-2783349681
Ref: Library<87>-Footnote-2793349726
Ref: Library<87>-Footnote-2803349771
Ref: Library<87>-Footnote-2813349816
Ref: Library<87>-Footnote-2823349861
Ref: Library<87>-Footnote-2833349906
Ref: Library<87>-Footnote-2843349951
Ref: Library<87>-Footnote-2853349996
Ref: Library<87>-Footnote-2863350041
Ref: Library<87>-Footnote-2873350086
Ref: Library<87>-Footnote-2883350131
Ref: Library<87>-Footnote-2893350182
Ref: Library<87>-Footnote-2903350227
Ref: Library<87>-Footnote-2913350272
Ref: Library<87>-Footnote-2923350317
Ref: Library<87>-Footnote-2933350362
Ref: Library<87>-Footnote-2943350407
Ref: Library<87>-Footnote-2953350452
Ref: Library<87>-Footnote-2963350497
Ref: Library<87>-Footnote-2973350542
Ref: Library<87>-Footnote-2983350587
Ref: Library<87>-Footnote-2993350632
Ref: Library<87>-Footnote-3003350677
Ref: Library<87>-Footnote-3013350722
Ref: Library<87>-Footnote-3023350767
Ref: Library<87>-Footnote-3033350812
Ref: Library<87>-Footnote-3043350857
Ref: Library<87>-Footnote-3053350902
Ref: Library<87>-Footnote-3063350947
Ref: Library<87>-Footnote-3073350992
Ref: Library<87>-Footnote-3083351037
Ref: Library<87>-Footnote-3093351082
Ref: Library<87>-Footnote-3103351127
Ref: Library<87>-Footnote-3113351172
Ref: Library<87>-Footnote-3123351217
Ref: Library<87>-Footnote-3133351262
Ref: Library<87>-Footnote-3143351307
Ref: Library<87>-Footnote-3153351351
Ref: Library<87>-Footnote-3163351396
Ref: Library<87>-Footnote-3173351441
Ref: Library<87>-Footnote-3183351486
Ref: Library<87>-Footnote-3193351531
Ref: Library<87>-Footnote-3203351576
Ref: Library<87>-Footnote-3213351621
Ref: Library<87>-Footnote-3223351666
Ref: Library<87>-Footnote-3233351711
Ref: Library<87>-Footnote-3243351756
Ref: Library<87>-Footnote-3253351801
Ref: Library<87>-Footnote-3263351846
Ref: Library<87>-Footnote-3273351891
Ref: Library<87>-Footnote-3283351936
Ref: Library<87>-Footnote-3293351981
Ref: Library<87>-Footnote-3303352026
Ref: Library<87>-Footnote-3313352071
Ref: Library<87>-Footnote-3323352116
Ref: Library<87>-Footnote-3333352161
Ref: Library<87>-Footnote-3343352206
Ref: Library<87>-Footnote-3353352250
Ref: Library<87>-Footnote-3363352295
Ref: Library<87>-Footnote-3373352340
Ref: Library<87>-Footnote-3383352385
Ref: Library<87>-Footnote-3393352430
Ref: Library<87>-Footnote-3403352475
Ref: Library<87>-Footnote-3413352520
Ref: Library<87>-Footnote-3423352565
Ref: Library<87>-Footnote-3433352610
Ref: Library<87>-Footnote-3443352655
Ref: Library<87>-Footnote-3453352700
Ref: Library<87>-Footnote-3463352745
Ref: Library<87>-Footnote-3473352790
Ref: Library<87>-Footnote-3483352835
Ref: Library<87>-Footnote-3493352880
Ref: Library<87>-Footnote-3503352925
Ref: Library<87>-Footnote-3513352970
Ref: Library<87>-Footnote-3523353015
Ref: Library<87>-Footnote-3533353060
Ref: Library<87>-Footnote-3543353105
Ref: Library<87>-Footnote-3553353150
Ref: Library<87>-Footnote-3563353195
Ref: Library<87>-Footnote-3573353240
Ref: Library<87>-Footnote-3583353285
Ref: Library<87>-Footnote-3593353330
Ref: Library<87>-Footnote-3603353375
Ref: Library<87>-Footnote-3613353420
Ref: Library<87>-Footnote-3623353465
Ref: Library<87>-Footnote-3633353510
Ref: Library<87>-Footnote-3643353555
Ref: Library<87>-Footnote-3653353600
Ref: Library<87>-Footnote-3663353645
Ref: Library<87>-Footnote-3673353690
Ref: Library<87>-Footnote-3683353735
Ref: Library<87>-Footnote-3693353780
Ref: Library<87>-Footnote-3703353825
Ref: Library<87>-Footnote-3713353869
Ref: Library<87>-Footnote-3723353914
Ref: Library<87>-Footnote-3733353959
Ref: Library<87>-Footnote-3743354004
Ref: Library<87>-Footnote-3753354049
Ref: Library<87>-Footnote-3763354094
Ref: Library<87>-Footnote-3773354139
Ref: Library<87>-Footnote-3783354184
Ref: Library<87>-Footnote-3793354229
Ref: Library<87>-Footnote-3803354274
Ref: Library<87>-Footnote-3813354319
Ref: Library<87>-Footnote-3823354364
Ref: Library<87>-Footnote-3833354409
Ref: Library<87>-Footnote-3843354453
Ref: Library<87>-Footnote-3853354498
Ref: Library<87>-Footnote-3863354543
Ref: Library<87>-Footnote-3873354588
Ref: Library<87>-Footnote-3883354633
Ref: Library<87>-Footnote-3893354676
Ref: Library<87>-Footnote-3903354721
Ref: Library<87>-Footnote-3913354766
Ref: Library<87>-Footnote-3923354811
Ref: Library<87>-Footnote-3933354856
Ref: Library<87>-Footnote-3943354901
Ref: Library<87>-Footnote-3953354946
Ref: Library<87>-Footnote-3963354991
Node: IDLE<53>3355036
Ref: whatsnew/changelog id5493355139
Ref: 11f63355139
Ref: IDLE<53>-Footnote-13358627
Ref: IDLE<53>-Footnote-23358670
Ref: IDLE<53>-Footnote-33358713
Ref: IDLE<53>-Footnote-43358755
Ref: IDLE<53>-Footnote-53358798
Ref: IDLE<53>-Footnote-63358840
Ref: IDLE<53>-Footnote-73358883
Ref: IDLE<53>-Footnote-83358926
Ref: IDLE<53>-Footnote-93358969
Ref: IDLE<53>-Footnote-103359012
Ref: IDLE<53>-Footnote-113359056
Ref: IDLE<53>-Footnote-123359100
Ref: IDLE<53>-Footnote-133359144
Ref: IDLE<53>-Footnote-143359188
Ref: IDLE<53>-Footnote-153359232
Ref: IDLE<53>-Footnote-163359276
Ref: IDLE<53>-Footnote-173359320
Ref: IDLE<53>-Footnote-183359364
Ref: IDLE<53>-Footnote-193359408
Ref: IDLE<53>-Footnote-203359452
Ref: IDLE<53>-Footnote-213359496
Ref: IDLE<53>-Footnote-223359540
Ref: IDLE<53>-Footnote-233359584
Ref: IDLE<53>-Footnote-243359634
Ref: IDLE<53>-Footnote-253359678
Ref: IDLE<53>-Footnote-263359722
Node: Build<56>3359766
Ref: whatsnew/changelog id5503359867
Ref: 11f73359867
Ref: Build<56>-Footnote-13363277
Ref: Build<56>-Footnote-23363320
Ref: Build<56>-Footnote-33363363
Ref: Build<56>-Footnote-43363406
Ref: Build<56>-Footnote-53363449
Ref: Build<56>-Footnote-63363492
Ref: Build<56>-Footnote-73363535
Ref: Build<56>-Footnote-83363578
Ref: Build<56>-Footnote-93363621
Ref: Build<56>-Footnote-103363664
Ref: Build<56>-Footnote-113363708
Ref: Build<56>-Footnote-123363752
Ref: Build<56>-Footnote-133363796
Ref: Build<56>-Footnote-143363840
Ref: Build<56>-Footnote-153363884
Ref: Build<56>-Footnote-163363928
Ref: Build<56>-Footnote-173363972
Ref: Build<56>-Footnote-183364016
Ref: Build<56>-Footnote-193364060
Ref: Build<56>-Footnote-203364104
Ref: Build<56>-Footnote-213364148
Ref: Build<56>-Footnote-223364192
Ref: Build<56>-Footnote-233364236
Ref: Build<56>-Footnote-243364280
Ref: Build<56>-Footnote-253364324
Ref: Build<56>-Footnote-263364368
Node: C API<38>3364412
Ref: whatsnew/changelog id5513364522
Ref: 11f83364522
Ref: C API<38>-Footnote-13365887
Ref: C API<38>-Footnote-23365930
Ref: C API<38>-Footnote-33365973
Ref: C API<38>-Footnote-43366016
Ref: C API<38>-Footnote-53366059
Ref: C API<38>-Footnote-63366102
Ref: C API<38>-Footnote-73366145
Node: Documentation<53>3366188
Ref: whatsnew/changelog id5523366298
Ref: 11f93366298
Ref: Documentation<53>-Footnote-13368105
Ref: Documentation<53>-Footnote-23368148
Ref: Documentation<53>-Footnote-33368191
Ref: Documentation<53>-Footnote-43368234
Ref: Documentation<53>-Footnote-53368277
Ref: Documentation<53>-Footnote-63368319
Ref: Documentation<53>-Footnote-73368362
Ref: Documentation<53>-Footnote-83368405
Ref: Documentation<53>-Footnote-93368448
Ref: Documentation<53>-Footnote-103368491
Ref: Documentation<53>-Footnote-113368535
Node: Tests<54>3368579
Ref: whatsnew/changelog id5533368695
Ref: 11fa3368695
Ref: Tests<54>-Footnote-13372886
Ref: Tests<54>-Footnote-23372929
Ref: Tests<54>-Footnote-33372972
Ref: Tests<54>-Footnote-43373015
Ref: Tests<54>-Footnote-53373058
Ref: Tests<54>-Footnote-63373101
Ref: Tests<54>-Footnote-73373144
Ref: Tests<54>-Footnote-83373187
Ref: Tests<54>-Footnote-93373230
Ref: Tests<54>-Footnote-103373273
Ref: Tests<54>-Footnote-113373317
Ref: Tests<54>-Footnote-123373361
Ref: Tests<54>-Footnote-133373405
Ref: Tests<54>-Footnote-143373449
Ref: Tests<54>-Footnote-153373492
Ref: Tests<54>-Footnote-163373536
Ref: Tests<54>-Footnote-173373580
Ref: Tests<54>-Footnote-183373624
Ref: Tests<54>-Footnote-193373668
Ref: Tests<54>-Footnote-203373712
Ref: Tests<54>-Footnote-213373756
Ref: Tests<54>-Footnote-223373800
Ref: Tests<54>-Footnote-233373844
Ref: Tests<54>-Footnote-243373888
Ref: Tests<54>-Footnote-253373932
Ref: Tests<54>-Footnote-263373976
Ref: Tests<54>-Footnote-273374020
Ref: Tests<54>-Footnote-283374064
Ref: Tests<54>-Footnote-293374108
Ref: Tests<54>-Footnote-303374152
Ref: Tests<54>-Footnote-313374196
Ref: Tests<54>-Footnote-323374240
Ref: Tests<54>-Footnote-333374284
Ref: Tests<54>-Footnote-343374328
Ref: Tests<54>-Footnote-353374372
Ref: Tests<54>-Footnote-363374416
Ref: Tests<54>-Footnote-373374460
Node: Tools/Demos<36>3374504
Ref: whatsnew/changelog id5543374614
Ref: 11fb3374614
Ref: Tools/Demos<36>-Footnote-13376278
Ref: Tools/Demos<36>-Footnote-23376321
Ref: Tools/Demos<36>-Footnote-33376364
Ref: Tools/Demos<36>-Footnote-43376407
Ref: Tools/Demos<36>-Footnote-53376450
Ref: Tools/Demos<36>-Footnote-63376493
Ref: Tools/Demos<36>-Footnote-73376536
Ref: Tools/Demos<36>-Footnote-83376579
Ref: Tools/Demos<36>-Footnote-93376622
Ref: Tools/Demos<36>-Footnote-103376665
Ref: Tools/Demos<36>-Footnote-113376715
Ref: Tools/Demos<36>-Footnote-123376759
Ref: Tools/Demos<36>-Footnote-133376803
Node: Windows<51>3376847
Ref: whatsnew/changelog id5553376939
Ref: 11fc3376939
Ref: Windows<51>-Footnote-13378146
Ref: Windows<51>-Footnote-23378189
Ref: Windows<51>-Footnote-33378232
Ref: Windows<51>-Footnote-43378275
Ref: Windows<51>-Footnote-53378318
Ref: Windows<51>-Footnote-63378361
Ref: Windows<51>-Footnote-73378404
Node: Python 教學3378447
Ref: tutorial/index doc3378568
Ref: 11fd3378568
Ref: tutorial/index the-python-tutorial3378568
Ref: 11fe3378568
Ref: tutorial/index tutorial-index3378568
Ref: 11ff3378568
Node: 淺嘗滋味3381393
Ref: tutorial/appetite doc3381487
Ref: 12053381487
Ref: tutorial/appetite tut-intro3381487
Ref: 12063381487
Ref: tutorial/appetite whetting-your-appetite3381487
Ref: 12073381487
Node: 使用 Python 直譯器3385881
Ref: tutorial/interpreter doc3386016
Ref: 12083386016
Ref: tutorial/interpreter tut-using3386016
Ref: 12093386016
Ref: tutorial/interpreter using-the-python-interpreter3386016
Ref: 120a3386016
Node: 啟動直譯器3386127
Ref: tutorial/interpreter invoking-the-interpreter3386235
Ref: 120b3386235
Ref: tutorial/interpreter tut-invoking3386235
Ref: 120c3386235
Ref: 啟動直譯器-Footnote-13389092
Ref: 啟動直譯器-Footnote-23389258
Node: 傳遞引數3389319
Ref: tutorial/interpreter argument-passing3389404
Ref: 12113389404
Ref: tutorial/interpreter tut-argpassing3389404
Ref: 12123389404
Node: 互動模式3390234
Ref: tutorial/interpreter interactive-mode3390319
Ref: 12133390319
Ref: tutorial/interpreter tut-interactive3390319
Ref: 8e83390319
Node: 直譯器與它的環境3391318
Ref: tutorial/interpreter the-interpreter-and-its-environment3391426
Ref: 12153391426
Ref: tutorial/interpreter tut-interp3391426
Ref: 12163391426
Node: 原始碼的字元編碼 encoding3391565
Ref: tutorial/interpreter source-code-encoding3391659
Ref: 12173391659
Ref: tutorial/interpreter tut-source-encoding3391659
Ref: 12183391659
Node: 一個非正式的 Python 簡介3392899
Ref: tutorial/introduction doc3393046
Ref: 121a3393046
Ref: tutorial/introduction an-informal-introduction-to-python3393046
Ref: 121b3393046
Ref: tutorial/introduction tut-informal3393046
Ref: 121c3393046
Node: 把 Python 當作計算機使用3394285
Ref: tutorial/introduction tut-calculator3394425
Ref: 121f3394425
Ref: tutorial/introduction using-python-as-a-calculator3394425
Ref: 12203394425
Node: 數字 Number3394739
Ref: tutorial/introduction numbers3394843
Ref: 12213394843
Ref: tutorial/introduction tut-numbers3394843
Ref: 12223394843
Ref: 數字 Number-Footnote-13397838
Node: 字串 String3398057
Ref: tutorial/introduction strings3398186
Ref: 12253398186
Ref: tutorial/introduction tut-strings3398186
Ref: 12263398186
Ref: 字串 String-Footnote-13406007
Node: List（串列）3406276
Ref: tutorial/introduction lists3406383
Ref: 122b3406383
Ref: tutorial/introduction tut-lists3406383
Ref: 122c3406383
Node: 初探程式設計的前幾步3408996
Ref: tutorial/introduction first-steps-towards-programming3409136
Ref: 12303409136
Ref: tutorial/introduction tut-firststeps3409136
Ref: 12313409136
Ref: 初探程式設計的前幾步-Footnote-13412052
Node: 深入了解流程控制3412147
Ref: tutorial/controlflow doc3412283
Ref: 12333412283
Ref: tutorial/controlflow more-control-flow-tools3412283
Ref: 12343412283
Ref: tutorial/controlflow tut-morecontrol3412283
Ref: 12353412283
Node: if Statements3412835
Ref: tutorial/controlflow if-statements3412932
Ref: 12363412932
Ref: tutorial/controlflow tut-if3412932
Ref: 12373412932
Node: for Statements3413738
Ref: tutorial/controlflow for-statements3413856
Ref: 123a3413856
Ref: tutorial/controlflow tut-for3413856
Ref: 123b3413856
Node: range 函式3415105
Ref: tutorial/controlflow the-range-function3415265
Ref: 123c3415265
Ref: tutorial/controlflow tut-range3415265
Ref: 123d3415265
Node: break and continue Statements and else Clauses on Loops3417461
Ref: tutorial/controlflow break-and-continue-statements-and-else-clauses-on-loops3417622
Ref: 12403417622
Ref: tutorial/controlflow tut-break3417622
Ref: 12413417622
Node: pass Statements3419811
Ref: tutorial/controlflow pass-statements3419981
Ref: 12433419981
Ref: tutorial/controlflow tut-pass3419981
Ref: 12443419981
Node: 定義函式 function3420690
Ref: tutorial/controlflow defining-functions3420831
Ref: 12463420831
Ref: tutorial/controlflow tut-functions3420831
Ref: 12473420831
Ref: 定義函式 function-Footnote-13425611
Node: More on Defining Functions3425813
Ref: tutorial/controlflow more-on-defining-functions3425962
Ref: 124b3425962
Ref: tutorial/controlflow tut-defining3425962
Ref: 124c3425962
Node: Default Argument Values3426366
Ref: tutorial/controlflow default-argument-values3426478
Ref: 124d3426478
Ref: tutorial/controlflow tut-defaultargs3426478
Ref: 124e3426478
Node: Keyword Arguments3428489
Ref: tutorial/controlflow keyword-arguments3428628
Ref: 124f3428628
Ref: tutorial/controlflow tut-keywordargs3428628
Ref: 12503428628
Node: Special parameters3432375
Ref: tutorial/controlflow special-parameters3432515
Ref: 12523432515
Node: Positional-or-Keyword Arguments3433652
Ref: tutorial/controlflow positional-or-keyword-arguments3433773
Ref: 12533433773
Node: Positional-Only Parameters3433987
Ref: tutorial/controlflow positional-only-parameters3434139
Ref: 12543434139
Node: Keyword-Only Arguments3434773
Ref: tutorial/controlflow keyword-only-arguments3434911
Ref: 12553434911
Node: Function Examples3435162
Ref: tutorial/controlflow function-examples3435279
Ref: 12563435279
Node: Recap3438275
Ref: tutorial/controlflow recap3438361
Ref: 12573438361
Node: Arbitrary Argument Lists3439222
Ref: tutorial/controlflow arbitrary-argument-lists3439369
Ref: 12583439369
Ref: tutorial/controlflow tut-arbitraryargs3439369
Ref: 12593439369
Node: Unpacking Argument Lists3440418
Ref: tutorial/controlflow tut-unpacking-arguments3440565
Ref: 125a3440565
Ref: tutorial/controlflow unpacking-argument-lists3440565
Ref: 125b3440565
Node: Lambda Expressions3441798
Ref: tutorial/controlflow lambda-expressions3441939
Ref: 125c3441939
Ref: tutorial/controlflow tut-lambda3441939
Ref: 125d3441939
Node: 說明文件字串3442930
Ref: tutorial/controlflow documentation-strings3443067
Ref: 125e3443067
Ref: tutorial/controlflow tut-docstrings3443067
Ref: 12483443067
Node: Function Annotations3444981
Ref: tutorial/controlflow function-annotations3445091
Ref: 125f3445091
Ref: tutorial/controlflow tut-annotations3445091
Ref: 12603445091
Ref: Function Annotations-Footnote-13446306
Ref: Function Annotations-Footnote-23446355
Node: Intermezzo Coding Style3446404
Ref: tutorial/controlflow intermezzo-coding-style3446523
Ref: 12633446523
Ref: tutorial/controlflow tut-codingstyle3446523
Ref: 12643446523
Ref: Intermezzo Coding Style-Footnote-13448694
Node: 資料結構3448743
Ref: tutorial/datastructures doc3448853
Ref: 12663448853
Ref: tutorial/datastructures data-structures3448853
Ref: 12673448853
Ref: tutorial/datastructures tut-structures3448853
Ref: 123f3448853
Node: 進一步了解 List（串列）3449289
Ref: tutorial/datastructures more-on-lists3449396
Ref: 12683449396
Ref: tutorial/datastructures tut-morelists3449396
Ref: 12693449396
Ref: 進一步了解 List（串列）-Footnote-13453354
Node: 將 List 作為 Stack（堆疊）使用3453489
Ref: tutorial/datastructures tut-lists-as-stacks3453645
Ref: 126a3453645
Ref: tutorial/datastructures using-lists-as-stacks3453645
Ref: 126b3453645
Node: 將 List 作為 Queue（佇列）使用3454370
Ref: tutorial/datastructures tut-lists-as-queues3454578
Ref: 126c3454578
Ref: tutorial/datastructures using-lists-as-queues3454578
Ref: 126d3454578
Node: List Comprehensions（串列綜合運算）3455717
Ref: tutorial/datastructures list-comprehensions3455915
Ref: 126e3455915
Ref: tutorial/datastructures tut-listcomps3455915
Ref: 126f3455915
Node: 巢狀的 List Comprehensions3459205
Ref: tutorial/datastructures nested-list-comprehensions3459355
Ref: 12703459355
Node: The del statement3461108
Ref: tutorial/datastructures the-del-statement3461250
Ref: 12713461250
Ref: tutorial/datastructures tut-del3461250
Ref: 12723461250
Node: Tuples 和序列 Sequences3462116
Ref: tutorial/datastructures tuples-and-sequences3462237
Ref: 12743462237
Ref: tutorial/datastructures tut-tuples3462237
Ref: 12513462237
Node: 集合 Sets3465285
Ref: tutorial/datastructures sets3465411
Ref: 12763465411
Ref: tutorial/datastructures tut-sets3465411
Ref: 12773465411
Node: 字典（Dictionary）3467157
Ref: tutorial/datastructures dictionaries3467269
Ref: 12783467269
Ref: tutorial/datastructures tut-dictionaries3467269
Ref: 12793467269
Node: 迴圈技巧3470023
Ref: tutorial/datastructures looping-techniques3470145
Ref: 127a3470145
Ref: tutorial/datastructures tut-loopidioms3470145
Ref: 123e3470145
Node: 更多條件式主題3472208
Ref: tutorial/datastructures more-on-conditions3472344
Ref: 127b3472344
Ref: tutorial/datastructures tut-conditions3472344
Ref: 127c3472344
Node: 序列和其他資料結構之比較3474354
Ref: tutorial/datastructures comparing-sequences-and-other-types3474469
Ref: 127e3474469
Ref: tutorial/datastructures tut-comparing3474469
Ref: 127f3474469
Node: 模組3476030
Ref: tutorial/modules doc3476131
Ref: 12803476131
Ref: tutorial/modules modules3476131
Ref: 12813476131
Ref: tutorial/modules tut-modules3476131
Ref: 12823476131
Node: More on Modules3478651
Ref: tutorial/modules more-on-modules3478734
Ref: 12833478734
Ref: tutorial/modules tut-moremodules3478734
Ref: 12843478734
Ref: More on Modules-Footnote-13481848
Node: Executing modules as scripts3482056
Ref: tutorial/modules executing-modules-as-scripts3482167
Ref: 12853482167
Ref: tutorial/modules tut-modulesasscripts3482167
Ref: 12863482167
Node: The Module Search Path3483051
Ref: tutorial/modules the-module-search-path3483194
Ref: 12873483194
Ref: tutorial/modules tut-searchpath3483194
Ref: 12883483194
Node: "Compiled" Python files3484518
Ref: tutorial/modules compiled-python-files3484624
Ref: 128a3484624
Ref: "Compiled" Python files-Footnote-13486925
Node: Standard Modules3486974
Ref: tutorial/modules standard-modules3487082
Ref: 128b3487082
Ref: tutorial/modules tut-standardmodules3487082
Ref: 12893487082
Node: The dir Function3488542
Ref: tutorial/modules the-dir-function3488643
Ref: 128c3488643
Ref: tutorial/modules tut-dir3488643
Ref: 128d3488643
Node: Packages3492808
Ref: tutorial/modules packages3492884
Ref: 128e3492884
Ref: tutorial/modules tut-packages3492884
Ref: 128f3492884
Node: Importing * From a Package3497179
Ref: tutorial/modules importing-from-a-package3497283
Ref: 12903497283
Ref: tutorial/modules tut-pkg-import-star3497283
Ref: 12913497283
Node: Intra-package References3499925
Ref: tutorial/modules intra-package-references3500070
Ref: 12923500070
Node: Packages in Multiple Directories3501083
Ref: tutorial/modules packages-in-multiple-directories3501193
Ref: 12933501193
Node: 輸入和輸出3501735
Ref: tutorial/inputoutput doc3501839
Ref: 12953501839
Ref: tutorial/inputoutput input-and-output3501839
Ref: 12963501839
Ref: tutorial/inputoutput tut-io3501839
Ref: 12973501839
Node: 更華麗的輸出格式3502121
Ref: tutorial/inputoutput fancier-output-formatting3502231
Ref: 12983502231
Ref: tutorial/inputoutput tut-formatting3502231
Ref: 12993502231
Node: 格式化的字串文本 Formatted String Literals3506021
Ref: tutorial/inputoutput formatted-string-literals3506165
Ref: 129b3506165
Ref: tutorial/inputoutput tut-f-strings3506165
Ref: 129a3506165
Node: The String format Method3507773
Ref: tutorial/inputoutput the-string-format-method3507950
Ref: 129c3507950
Ref: tutorial/inputoutput tut-string-format3507950
Ref: 129d3507950
Node: Manual String Formatting3510619
Ref: tutorial/inputoutput manual-string-formatting3510767
Ref: 129e3510767
Node: Old string formatting3512296
Ref: tutorial/inputoutput old-string-formatting3512411
Ref: 12a33512411
Node: Reading and Writing Files3512962
Ref: tutorial/inputoutput reading-and-writing-files3513072
Ref: 12a43513072
Ref: tutorial/inputoutput tut-files3513072
Ref: 12a53513072
Node: Methods of File Objects3516080
Ref: tutorial/inputoutput methods-of-file-objects3516206
Ref: 12a63516206
Ref: tutorial/inputoutput tut-filemethods3516206
Ref: 12a73516206
Node: Saving structured data with json3519900
Ref: tutorial/inputoutput saving-structured-data-with-json3520026
Ref: 12a83520026
Ref: tutorial/inputoutput tut-json3520026
Ref: 12a93520026
Ref: Saving structured data with json-Footnote-13522673
Node: 錯誤和例外3522697
Ref: tutorial/errors doc3522802
Ref: 12ab3522802
Ref: tutorial/errors errors-and-exceptions3522802
Ref: 12ac3522802
Ref: tutorial/errors tut-errors3522802
Ref: 12ad3522802
Node: 語法錯誤3523229
Ref: tutorial/errors syntax-errors3523308
Ref: 12ae3523308
Ref: tutorial/errors tut-syntaxerrors3523308
Ref: 12af3523308
Node: 例外3524105
Ref: tutorial/errors exceptions3524205
Ref: 12b03524205
Ref: tutorial/errors tut-exceptions3524205
Ref: 12b13524205
Node: 處理例外3526026
Ref: tutorial/errors handling-exceptions3526132
Ref: 12b43526132
Ref: tutorial/errors tut-handling3526132
Ref: 12423526132
Node: Raising Exceptions3532012
Ref: tutorial/errors raising-exceptions3532135
Ref: 12b53532135
Ref: tutorial/errors tut-raising3532135
Ref: 12b63532135
Node: User-defined Exceptions3533277
Ref: tutorial/errors tut-userexceptions3533413
Ref: 12b73533413
Ref: tutorial/errors user-defined-exceptions3533413
Ref: 12b83533413
Node: Defining Clean-up Actions3535453
Ref: tutorial/errors defining-clean-up-actions3535598
Ref: 12b93535598
Ref: tutorial/errors tut-cleanup3535598
Ref: 12ba3535598
Node: Predefined Clean-up Actions3538725
Ref: tutorial/errors predefined-clean-up-actions3538838
Ref: 12bb3538838
Ref: tutorial/errors tut-cleanup-with3538838
Ref: 12bc3538838
Node: Classes3539957
Ref: tutorial/classes doc3540075
Ref: 12bd3540075
Ref: tutorial/classes classes3540075
Ref: 12be3540075
Ref: tutorial/classes tut-classes3540075
Ref: 124a3540075
Node: A Word About Names and Objects3542389
Ref: tutorial/classes a-word-about-names-and-objects3542500
Ref: 12c03542500
Ref: tutorial/classes tut-object3542500
Ref: 12c13542500
Node: Python Scopes and Namespaces3543422
Ref: tutorial/classes python-scopes-and-namespaces3543565
Ref: 12c23543565
Ref: tutorial/classes tut-scopes3543565
Ref: 12c33543565
Ref: Python Scopes and Namespaces-Footnote-13549644
Node: Scopes and Namespaces Example3550038
Ref: tutorial/classes scopes-and-namespaces-example3550132
Ref: 12c53550132
Ref: tutorial/classes tut-scopeexample3550132
Ref: 12c63550132
Node: A First Look at Classes3551497
Ref: tutorial/classes a-first-look-at-classes3551624
Ref: 12c73551624
Ref: tutorial/classes tut-firstclasses3551624
Ref: 12653551624
Node: Class Definition Syntax3551909
Ref: tutorial/classes class-definition-syntax3552014
Ref: 12c83552014
Ref: tutorial/classes tut-classdefinition3552014
Ref: 12c93552014
Node: Class Objects3553550
Ref: tutorial/classes class-objects3553680
Ref: 12ca3553680
Ref: tutorial/classes tut-classobjects3553680
Ref: 12cb3553680
Node: Instance Objects3555877
Ref: tutorial/classes instance-objects3555998
Ref: 12cc3555998
Ref: tutorial/classes tut-instanceobjects3555998
Ref: 12cd3555998
Node: Method Objects3557650
Ref: tutorial/classes method-objects3557786
Ref: 12ce3557786
Ref: tutorial/classes tut-methodobjects3557786
Ref: 12cf3557786
Node: Class and Instance Variables3559727
Ref: tutorial/classes class-and-instance-variables3559838
Ref: 12d03559838
Ref: tutorial/classes tut-class-and-instance-variables3559838
Ref: 12d13559838
Node: Random Remarks3561882
Ref: tutorial/classes random-remarks3561992
Ref: 12d23561992
Ref: tutorial/classes tut-remarks3561992
Ref: 12d33561992
Node: Inheritance3565815
Ref: tutorial/classes inheritance3565919
Ref: 12d43565919
Ref: tutorial/classes tut-inheritance3565919
Ref: 12d53565919
Node: Multiple Inheritance3568684
Ref: tutorial/classes multiple-inheritance3568752
Ref: 12d63568752
Ref: tutorial/classes tut-multiple3568752
Ref: 12d73568752
Node: Private Variables3570753
Ref: tutorial/classes private-variables3570856
Ref: 12d83570856
Ref: tutorial/classes tut-private3570856
Ref: 12bf3570856
Node: Odds and Ends3573540
Ref: tutorial/classes odds-and-ends3573641
Ref: 12d93573641
Ref: tutorial/classes tut-odds3573641
Ref: 12da3573641
Node: Iterators3574638
Ref: tutorial/classes iterators3574732
Ref: 12db3574732
Ref: tutorial/classes tut-iterators3574732
Ref: 12dc3574732
Node: Generators3577014
Ref: tutorial/classes generators3577116
Ref: 12dd3577116
Ref: tutorial/classes tut-generators3577116
Ref: 12de3577116
Node: Generator Expressions3578554
Ref: tutorial/classes generator-expressions3578638
Ref: 12e03578638
Ref: tutorial/classes tut-genexps3578638
Ref: 12e13578638
Node: Python 標準函式庫概覽3579638
Ref: tutorial/stdlib doc3579787
Ref: 12e23579787
Ref: tutorial/stdlib brief-tour-of-the-standard-library3579787
Ref: 12e33579787
Ref: tutorial/stdlib tut-brieftour3579787
Ref: 12e43579787
Node: 作業系統介面3580120
Ref: tutorial/stdlib operating-system-interface3580233
Ref: 12e53580233
Ref: tutorial/stdlib tut-os-interface3580233
Ref: 12e63580233
Node: 檔案之萬用字元3581386
Ref: tutorial/stdlib file-wildcards3581523
Ref: 12e73581523
Ref: tutorial/stdlib tut-file-wildcards3581523
Ref: 12e83581523
Node: 命令列引數3581772
Ref: tutorial/stdlib command-line-arguments3581930
Ref: 12e93581930
Ref: tutorial/stdlib tut-command-line-arguments3581930
Ref: 12ea3581930
Node: 錯誤輸出重新導向與程式終止3582974
Ref: tutorial/stdlib error-output-redirection-and-program-termination3583129
Ref: 12eb3583129
Ref: tutorial/stdlib tut-stderr3583129
Ref: 12ec3583129
Node: 字串樣式比對3583577
Ref: tutorial/stdlib string-pattern-matching3583729
Ref: 12ed3583729
Ref: tutorial/stdlib tut-string-pattern-matching3583729
Ref: 12ee3583729
Node: 數學相關3584366
Ref: tutorial/stdlib mathematics3584491
Ref: 12ef3584491
Ref: tutorial/stdlib tut-mathematics3584491
Ref: 12f03584491
Node: 網路存取3585600
Ref: tutorial/stdlib internet-access3585722
Ref: 12f13585722
Ref: tutorial/stdlib tut-internet-access3585722
Ref: 12f23585722
Node: 日期與時間3586726
Ref: tutorial/stdlib dates-and-times3586848
Ref: 12f33586848
Ref: tutorial/stdlib tut-dates-and-times3586848
Ref: 12f43586848
Node: 資料壓縮3587614
Ref: tutorial/stdlib data-compression3587736
Ref: 12f53587736
Ref: tutorial/stdlib tut-data-compression3587736
Ref: 12f63587736
Node: 效能量測3588245
Ref: tutorial/stdlib performance-measurement3588364
Ref: 12f73588364
Ref: tutorial/stdlib tut-performance-measurement3588364
Ref: 12f83588364
Node: 品質控管3589116
Ref: tutorial/stdlib quality-control3589238
Ref: 12f93589238
Ref: tutorial/stdlib tut-quality-control3589238
Ref: 12fa3589238
Node: 標準模組庫3590665
Ref: tutorial/stdlib batteries-included3590766
Ref: 12fb3590766
Ref: tutorial/stdlib tut-batteries-included3590766
Ref: 12fc3590766
Ref: 標準模組庫-Footnote-13592358
Node: Brief Tour of the Standard Library --- Part II3592407
Ref: tutorial/stdlib2 doc3592570
Ref: 12fd3592570
Ref: tutorial/stdlib2 brief-tour-of-the-standard-library-part-ii3592570
Ref: 12fe3592570
Ref: tutorial/stdlib2 tut-brieftourtwo3592570
Ref: 12ff3592570
Node: Output Formatting3593026
Ref: tutorial/stdlib2 output-formatting3593145
Ref: 13003593145
Ref: tutorial/stdlib2 tut-output-formatting3593145
Ref: 13013593145
Node: Templating3595254
Ref: tutorial/stdlib2 templating3595421
Ref: 13023595421
Ref: tutorial/stdlib2 tut-templating3595421
Ref: 13033595421
Node: Working with Binary Data Record Layouts3597976
Ref: tutorial/stdlib2 tut-binary-formats3598144
Ref: 13063598144
Ref: tutorial/stdlib2 working-with-binary-data-record-layouts3598144
Ref: 13073598144
Node: Multi-threading<2>3599319
Ref: tutorial/stdlib2 multi-threading3599484
Ref: 13093599484
Ref: tutorial/stdlib2 tut-multi-threading3599484
Ref: 130a3599484
Node: Logging3601427
Ref: tutorial/stdlib2 logging3601568
Ref: 130b3601568
Ref: tutorial/stdlib2 tut-logging3601568
Ref: 130c3601568
Node: Weak References3602736
Ref: tutorial/stdlib2 tut-weak-references3602887
Ref: 130d3602887
Ref: tutorial/stdlib2 weak-references3602887
Ref: 130e3602887
Node: Tools for Working with Lists3604643
Ref: tutorial/stdlib2 tools-for-working-with-lists3604820
Ref: 130f3604820
Ref: tutorial/stdlib2 tut-list-tools3604820
Ref: 13103604820
Node: Decimal Floating Point Arithmetic3607274
Ref: tutorial/stdlib2 decimal-floating-point-arithmetic3607427
Ref: 13113607427
Ref: tutorial/stdlib2 tut-decimal-fp3607427
Ref: 13123607427
Node: 虛擬環境與套件3609324
Ref: tutorial/venv doc3609492
Ref: 13133609492
Ref: tutorial/venv tut-venv3609492
Ref: 13143609492
Ref: tutorial/venv virtual-environments-and-packages3609492
Ref: 13153609492
Node: 簡介<4>3609619
Ref: tutorial/venv introduction3609713
Ref: 13163609713
Node: 建立虛擬環境3610897
Ref: tutorial/venv creating-virtual-environments3611020
Ref: 13183611020
Node: 用 pip 管理套件3612970
Ref: tutorial/venv managing-packages-with-pip3613075
Ref: 13193613075
Node: 現在可以來學習些什麼？3616774
Ref: tutorial/whatnow doc3616946
Ref: 131a3616946
Ref: tutorial/whatnow tut-whatnow3616946
Ref: 131b3616946
Ref: tutorial/whatnow what-now3616946
Ref: 131c3616946
Ref: 現在可以來學習些什麼？-Footnote-13620300
Node: Interactive Input Editing and History Substitution3620453
Ref: tutorial/interactive doc3620637
Ref: 131e3620637
Ref: tutorial/interactive interactive-input-editing-and-history-substitution3620637
Ref: 131f3620637
Ref: tutorial/interactive tut-interacting3620637
Ref: 120f3620637
Ref: Interactive Input Editing and History Substitution-Footnote-13621233
Node: Tab Completion and History Editing3621294
Ref: tutorial/interactive tab-completion-and-history-editing3621467
Ref: 13203621467
Ref: tutorial/interactive tut-keybindings3621467
Ref: 13213621467
Node: Alternatives to the Interactive Interpreter3622322
Ref: tutorial/interactive alternatives-to-the-interactive-interpreter3622495
Ref: 13223622495
Ref: tutorial/interactive tut-commentary3622495
Ref: 13233622495
Ref: Alternatives to the Interactive Interpreter-Footnote-13623389
Ref: Alternatives to the Interactive Interpreter-Footnote-23623418
Node: 浮點數運算：問題與限制3623463
Ref: tutorial/floatingpoint doc3623620
Ref: 13243623620
Ref: tutorial/floatingpoint bpython3623620
Ref: 13253623620
Ref: tutorial/floatingpoint floating-point-arithmetic-issues-and-limitations3623620
Ref: 13263623620
Ref: tutorial/floatingpoint tut-fp-issues3623620
Ref: 13273623620
Ref: 浮點數運算：問題與限制-Footnote-13631484
Node: Representation Error3631523
Ref: tutorial/floatingpoint representation-error3631613
Ref: 132a3631613
Ref: tutorial/floatingpoint tut-fp-error3631613
Ref: 132b3631613
Node: 附錄3634807
Ref: tutorial/appendix doc3634905
Ref: 132c3634905
Ref: tutorial/appendix appendix3634905
Ref: 132d3634905
Ref: tutorial/appendix tut-appendix3634905
Ref: 132e3634905
Node: 互動模式<2>3634971
Ref: tutorial/appendix interactive-mode3635029
Ref: 132f3635029
Ref: tutorial/appendix tut-interac3635029
Ref: 12143635029
Node: Error Handling3635188
Ref: tutorial/appendix error-handling3635288
Ref: 13303635288
Ref: tutorial/appendix tut-error3635288
Ref: 13313635288
Ref: Error Handling-Footnote-13636341
Node: Executable Python Scripts3636411
Ref: tutorial/appendix executable-python-scripts3636548
Ref: 13323636548
Ref: tutorial/appendix tut-scripts3636548
Ref: 12193636548
Node: The Interactive Startup File3637626
Ref: tutorial/appendix the-interactive-startup-file3637774
Ref: 13333637774
Ref: tutorial/appendix tut-startup3637774
Ref: 13343637774
Node: The Customization Modules3639210
Ref: tutorial/appendix the-customization-modules3639324
Ref: 13353639324
Ref: tutorial/appendix tut-customize3639324
Ref: 13363639324
Node: Python Setup and Usage3640240
Ref: using/index doc3640362
Ref: 13373640362
Ref: using/index python-setup-and-usage3640362
Ref: 13383640362
Ref: using/index using-index3640362
Ref: 13393640362
Node: Command line and environment3640792
Ref: using/cmdline doc3640918
Ref: 133a3640918
Ref: using/cmdline command-line-and-environment3640918
Ref: 133b3640918
Ref: using/cmdline using-on-general3640918
Ref: faf3640918
Node: Command line3641287
Ref: using/cmdline command-line3641394
Ref: 133d3641394
Ref: using/cmdline using-on-cmdline3641394
Ref: 9303641394
Node: Interface options3641786
Ref: using/cmdline interface-options3641876
Ref: 133e3641876
Ref: using/cmdline using-on-interface-options3641876
Ref: 133f3641876
Ref: using/cmdline cmdoption-c3643258
Ref: 12103643258
Ref: using/cmdline cmdoption-m3643831
Ref: 33c3643831
Ref: using/cmdline cmdarg-dash3646211
Ref: 13413646211
Ref: using/cmdline cmdarg-script3646627
Ref: 13423646627
Ref: Interface options-Footnote-13648459
Node: Generic options3648508
Ref: using/cmdline generic-options3648628
Ref: 13433648628
Ref: using/cmdline cmdoption3648677
Ref: d913648677
Ref: using/cmdline cmdoption-h3648698
Ref: 13443648698
Ref: using/cmdline cmdoption-help3648719
Ref: d903648719
Ref: using/cmdline cmdoption-v3648806
Ref: 5d73648806
Ref: using/cmdline cmdoption-version3648827
Ref: 5d63648827
Node: Miscellaneous options3649171
Ref: using/cmdline miscellaneous-options3649299
Ref: 13453649299
Ref: using/cmdline using-on-misc-options3649299
Ref: 9313649299
Ref: using/cmdline cmdoption-b3649360
Ref: 41a3649360
Ref: using/cmdline id13649688
Ref: d3d3649688
Ref: using/cmdline cmdoption-check-hash-based-pycs3649855
Ref: 13463649855
Ref: using/cmdline cmdoption-d3650555
Ref: 13473650555
Ref: using/cmdline cmdoption-e3650708
Ref: 100e3650708
Ref: using/cmdline cmdoption-i3650864
Ref: e243650864
Ref: using/cmdline id23651320
Ref: 100d3651320
Ref: using/cmdline cmdoption-o3651721
Ref: 6903651721
Ref: using/cmdline cmdoption-oo3652102
Ref: 6913652102
Ref: using/cmdline cmdoption-q3652399
Ref: 134a3652399
Ref: using/cmdline cmdoption-r3652533
Ref: 10993652533
Ref: using/cmdline cmdoption-s3653576
Ref: d1a3653576
Ref: using/cmdline id33653773
Ref: b293653773
Ref: using/cmdline cmdoption-u3654096
Ref: 134d3654096
Ref: using/cmdline id43654369
Ref: d8d3654369
Ref: using/cmdline using-on-warnings3654741
Ref: 13503654741
Ref: using/cmdline cmdoption-w3654741
Ref: 41c3654741
Ref: using/cmdline cmdoption-x3656351
Ref: 13533656351
Ref: using/cmdline id53656514
Ref: 1563656514
Ref: Miscellaneous options-Footnote-13660131
Ref: Miscellaneous options-Footnote-23660180
Ref: Miscellaneous options-Footnote-33660229
Ref: Miscellaneous options-Footnote-43660278
Ref: Miscellaneous options-Footnote-53660327
Node: Options you shouldn't use3660376
Ref: using/cmdline options-you-shouldn-t-use3660480
Ref: 13573660480
Ref: using/cmdline cmdoption-j3660551
Ref: d3c3660551
Ref: Options you shouldn't use-Footnote-13660646
Node: Environment variables3660677
Ref: using/cmdline environment-variables3660784
Ref: 13583660784
Ref: using/cmdline using-on-envvars3660784
Ref: 13593660784
Ref: using/cmdline envvar-PYTHONHOME3661077
Ref: 4db3661077
Ref: using/cmdline envvar-PYTHONPATH3661675
Ref: 9583661675
Ref: using/cmdline envvar-PYTHONSTARTUP3662730
Ref: 8ea3662730
Ref: using/cmdline envvar-PYTHONOPTIMIZE3663410
Ref: 13493663410
Ref: using/cmdline envvar-PYTHONBREAKPOINT3663640
Ref: 3193663640
Ref: using/cmdline envvar-PYTHONDEBUG3664245
Ref: 13483664245
Ref: using/cmdline envvar-PYTHONINSPECT3664474
Ref: e233664474
Ref: using/cmdline envvar-PYTHONUNBUFFERED3664749
Ref: 134e3664749
Ref: using/cmdline envvar-PYTHONVERBOSE3664892
Ref: 134f3664892
Ref: using/cmdline envvar-PYTHONCASEOK3665121
Ref: e623665121
Ref: using/cmdline envvar-PYTHONDONTWRITEBYTECODE3665272
Ref: d3e3665272
Ref: using/cmdline envvar-PYTHONPYCACHEPREFIX3665508
Ref: 1553665508
Ref: using/cmdline envvar-PYTHONHASHSEED3665839
Ref: 9ca3665839
Ref: using/cmdline envvar-PYTHONIOENCODING3666512
Ref: 9343666512
Ref: using/cmdline envvar-PYTHONNOUSERSITE3667309
Ref: d1b3667309
Ref: using/cmdline envvar-PYTHONUSERBASE3667543
Ref: d193667543
Ref: using/cmdline envvar-PYTHONEXECUTABLE3667896
Ref: 135f3667896
Ref: using/cmdline envvar-PYTHONWARNINGS3668101
Ref: 41d3668101
Ref: using/cmdline envvar-PYTHONFAULTHANDLER3669016
Ref: 9cd3669016
Ref: using/cmdline envvar-PYTHONTRACEMALLOC3669418
Ref: 13603669418
Ref: using/cmdline envvar-PYTHONPROFILEIMPORTTIME3669883
Ref: 33d3669883
Ref: using/cmdline envvar-PYTHONASYNCIODEBUG3670150
Ref: 13613670150
Ref: using/cmdline envvar-PYTHONMALLOC3670350
Ref: 5083670350
Ref: using/cmdline envvar-PYTHONMALLOCSTATS3671594
Ref: 11673671594
Ref: using/cmdline envvar-PYTHONLEGACYWINDOWSFSENCODING3672187
Ref: 4fc3672187
Ref: using/cmdline envvar-PYTHONLEGACYWINDOWSSTDIO3672693
Ref: 4ff3672693
Ref: using/cmdline envvar-PYTHONCOERCECLOCALE3673154
Ref: 3113673154
Ref: using/cmdline envvar-PYTHONDEVMODE3675872
Ref: 3313675872
Ref: using/cmdline envvar-PYTHONUTF83676085
Ref: 3163676085
Ref: Environment variables-Footnote-13678870
Ref: Environment variables-Footnote-23678919
Ref: Environment variables-Footnote-33678968
Ref: Environment variables-Footnote-43679017
Ref: Environment variables-Footnote-53679066
Node: Debug-mode variables3679115
Ref: using/cmdline debug-mode-variables3679193
Ref: 13683679193
Ref: using/cmdline envvar-PYTHONTHREADDEBUG3679324
Ref: 13693679324
Ref: using/cmdline envvar-PYTHONDUMPREFS3679488
Ref: 15a3679488
Node: Using Python on Unix platforms3679712
Ref: using/unix doc3679875
Ref: 136a3679875
Ref: using/unix using-on-unix3679875
Ref: 136b3679875
Ref: using/unix using-python-on-unix-platforms3679875
Ref: 136c3679875
Node: Getting and installing the latest version of Python3680085
Ref: using/unix getting-and-installing-the-latest-version-of-python3680227
Ref: 136d3680227
Node: On Linux3680413
Ref: using/unix on-linux3680540
Ref: 136e3680540
Node: On FreeBSD and OpenBSD3681456
Ref: using/unix on-freebsd-and-openbsd3681606
Ref: 136f3681606
Node: On OpenSolaris3682096
Ref: using/unix on-opensolaris3682229
Ref: 13703682229
Ref: On OpenSolaris-Footnote-13682449
Node: Building Python3682482
Ref: using/unix building-python3682663
Ref: 13713682663
Ref: using/unix building-python-on-unix3682663
Ref: 7f83682663
Ref: Building Python-Footnote-13683477
Ref: Building Python-Footnote-23683526
Ref: Building Python-Footnote-33683593
Node: Python-related paths and files3683655
Ref: using/unix python-related-paths-and-files3683798
Ref: 13723683798
Node: Miscellaneous3685368
Ref: using/unix miscellaneous3685487
Ref: 13733685487
Node: 在 Windows 上使用 Python3686045
Ref: using/windows doc3686210
Ref: 13743686210
Ref: using/windows using-on-windows3686210
Ref: 2da3686210
Ref: using/windows using-python-on-windows3686210
Ref: 13753686210
Ref: 在 Windows 上使用 Python-Footnote-13688495
Ref: 在 Windows 上使用 Python-Footnote-23688545
Node: The full installer3688594
Ref: using/windows the-full-installer3688713
Ref: 13793688713
Ref: using/windows windows-full3688713
Ref: 13763688713
Node: Installation steps3688917
Ref: using/windows installation-steps3689031
Ref: 137a3689031
Node: Removing the MAX_PATH Limitation3691110
Ref: using/windows max-path3691260
Ref: 4da3691260
Ref: using/windows removing-the-max-path-limitation3691260
Ref: 137c3691260
Node: 安裝排除使用者介面3692107
Ref: using/windows install-quiet-option3692260
Ref: 137d3692260
Ref: using/windows installing-without-ui3692260
Ref: 137e3692260
Node: 當安裝時不下載3701606
Ref: using/windows install-layout-option3701747
Ref: 137b3701747
Ref: using/windows installing-without-downloading3701747
Ref: 137f3701747
Node: Modifying an install3702717
Ref: using/windows modifying-an-install3702822
Ref: 13803702822
Node: The Microsoft Store package3703695
Ref: using/windows the-microsoft-store-package3703845
Ref: 13813703845
Ref: using/windows windows-store3703845
Ref: 120d3703845
Node: Known Issues3705990
Ref: using/windows known-issues3706066
Ref: 13823706066
Ref: Known Issues-Footnote-13706677
Node: The nuget org packages3706773
Ref: using/windows the-nuget-org-packages3706927
Ref: 13833706927
Ref: using/windows windows-nuget3706927
Ref: 13773706927
Ref: The nuget org packages-Footnote-13709205
Ref: The nuget org packages-Footnote-23709236
Ref: The nuget org packages-Footnote-33709282
Node: The embeddable package3709331
Ref: using/windows the-embeddable-package3709477
Ref: 13843709477
Ref: using/windows windows-embeddable3709477
Ref: 13783709477
Ref: The embeddable package-Footnote-13711498
Node: Python Application3711569
Ref: using/windows python-application3711668
Ref: 13853711668
Node: 嵌入 Python3713165
Ref: using/windows embedding-python3713264
Ref: 13863713264
Node: Alternative bundles3714044
Ref: using/windows alternative-bundles3714181
Ref: 13873714181
Ref: Alternative bundles-Footnote-13715045
Ref: Alternative bundles-Footnote-23715095
Ref: Alternative bundles-Footnote-33715138
Ref: Alternative bundles-Footnote-43715188
Node: 設定 Python3715225
Ref: using/windows configuring-python3715350
Ref: 13883715350
Node: Excursus Setting environment variables3715906
Ref: using/windows excursus-setting-environment-variables3716032
Ref: 13893716032
Ref: using/windows setting-envvars3716032
Ref: 120e3716032
Node: Finding the Python executable3718385
Ref: using/windows finding-the-python-executable3718511
Ref: 138a3718511
Ref: using/windows windows-path-mod3718511
Ref: 9953718511
Node: UTF-8 mode3719791
Ref: using/windows utf-8-mode3719924
Ref: 138b3719924
Ref: using/windows win-utf8-mode3719924
Ref: 138c3719924
Ref: UTF-8 mode-Footnote-13721721
Ref: UTF-8 mode-Footnote-23721770
Node: Python Launcher for Windows3721819
Ref: using/windows launcher3721954
Ref: 9943721954
Ref: using/windows python-launcher-for-windows3721954
Ref: 138d3721954
Ref: Python Launcher for Windows-Footnote-13722744
Node: 開始3722793
Ref: using/windows getting-started3722885
Ref: 138e3722885
Node: From the command-line3723030
Ref: using/windows from-the-command-line3723140
Ref: 138f3723140
Node: 虛擬環境（Virtual environment）3724347
Ref: using/windows virtual-environments3724479
Ref: 13903724479
Node: From a script3725001
Ref: using/windows from-a-script3725127
Ref: 13913725127
Node: 從檔案關聯3726169
Ref: using/windows from-file-associations3726249
Ref: 13923726249
Node: Shebang Lines3726807
Ref: using/windows shebang-lines3726934
Ref: 13933726934
Node: Arguments in shebang lines3728978
Ref: using/windows arguments-in-shebang-lines3729112
Ref: 13943729112
Node: Customization3729402
Ref: using/windows customization3729534
Ref: 13953729534
Node: Customization via INI files3729661
Ref: using/windows customization-via-ini-files3729782
Ref: 13963729782
Node: Customizing default Python versions3730532
Ref: using/windows customizing-default-python-versions3730653
Ref: 13973730653
Node: Diagnostics3734472
Ref: using/windows diagnostics3734569
Ref: 13983734569
Node: Finding modules3735002
Ref: using/windows finding-modules3735145
Ref: 4b53735145
Ref: using/windows id13735145
Ref: 13993735145
Node: Additional modules3741367
Ref: using/windows additional-modules3741508
Ref: 139a3741508
Node: PyWin323741922
Ref: using/windows pywin323742002
Ref: 139c3742002
Ref: PyWin32-Footnote-13742618
Ref: PyWin32-Footnote-23742659
Ref: PyWin32-Footnote-33742759
Ref: PyWin32-Footnote-43742833
Ref: PyWin32-Footnote-53742927
Ref: PyWin32-Footnote-63742985
Node: cx_Freeze3743034
Ref: using/windows cx-freeze3743129
Ref: 139d3743129
Ref: cx_Freeze-Footnote-13743486
Node: WConio3743538
Ref: using/windows wconio3743617
Ref: 139f3743617
Ref: WConio-Footnote-13743965
Node: 編譯 Python 在 Windows3744025
Ref: using/windows compiling-python-on-windows3744163
Ref: 13a03744163
Ref: 編譯 Python 在 Windows-Footnote-13745115
Ref: 編譯 Python 在 Windows-Footnote-23745164
Ref: 編譯 Python 在 Windows-Footnote-33745231
Node: 其他平台3745279
Ref: using/windows other-platforms3745390
Ref: 13a23745390
Ref: 其他平台-Footnote-13745952
Ref: 其他平台-Footnote-23746001
Ref: 其他平台-Footnote-33746042
Ref: 其他平台-Footnote-43746070
Ref: 其他平台-Footnote-53746158
Ref: 其他平台-Footnote-63746212
Node: 在麥金塔系統使用Python3746262
Ref: using/mac doc3746413
Ref: 13a33746413
Ref: using/mac using-on-mac3746413
Ref: 13a43746413
Ref: using/mac using-python-on-a-macintosh3746413
Ref: 13a53746413
Node: 取得和安裝MacPython3746985
Ref: using/mac getting-and-installing-macpython3747106
Ref: 13a63747106
Ref: using/mac getting-osx3747106
Ref: 13a73747106
Node: 如何執行Python腳本3749020
Ref: using/mac how-to-run-a-python-script3749153
Ref: 13a83749153
Node: 透過使用者圖形介面執行腳本3750624
Ref: using/mac osx-gui-scripts3750772
Ref: 13aa3750772
Ref: using/mac running-scripts-with-a-gui3750772
Ref: 13ab3750772
Node: 設定3751201
Ref: using/mac configuration3751316
Ref: 13ac3751316
Node: 整合化開發工具3751843
Ref: using/mac ide3752010
Ref: 13a93752010
Ref: using/mac the-ide3752010
Ref: 13ae3752010
Node: Installing Additional Python Packages3752245
Ref: using/mac installing-additional-python-packages3752435
Ref: 13af3752435
Ref: using/mac mac-package-manager3752435
Ref: 13ad3752435
Node: 圖形化使用者介面 GUI 程式開發於Mac3752835
Ref: using/mac gui-programming-on-the-mac3753035
Ref: 13b03753035
Node: 貢獻Python應用程式於 Mac3754085
Ref: using/mac distributing-python-applications-on-the-mac3754260
Ref: 13b13754260
Node: 其他資源3754530
Ref: using/mac other-resources3754649
Ref: 13b23754649
Node: Editors and IDEs3754936
Ref: using/editors doc3755050
Ref: 13b33755050
Ref: using/editors editors3755050
Ref: 13b43755050
Ref: using/editors editors-and-ides3755050
Ref: 13b53755050
Ref: Editors and IDEs-Footnote-13755389
Ref: Editors and IDEs-Footnote-23755438
Ref: Editors and IDEs-Footnote-33755489
Node: The Python Language Reference3755560
Ref: reference/index doc3755708
Ref: 13b63755708
Ref: reference/index reference-index3755708
Ref: 12013755708
Ref: reference/index the-python-language-reference3755708
Ref: 13b73755708
Node: 簡介<5>3756688
Ref: reference/introduction doc3756788
Ref: 13b83756788
Ref: reference/introduction id13756788
Ref: 13b93756788
Ref: reference/introduction introduction3756788
Ref: 13ba3756788
Node: Alternate Implementations3758580
Ref: reference/introduction alternate-implementations3758668
Ref: 13bb3758668
Ref: reference/introduction implementations3758668
Ref: 133c3758668
Ref: Alternate Implementations-Footnote-13760850
Ref: Alternate Implementations-Footnote-23760881
Ref: Alternate Implementations-Footnote-33760918
Ref: Alternate Implementations-Footnote-43760949
Node: Notation3760974
Ref: reference/introduction id23761062
Ref: 13bc3761062
Ref: reference/introduction notation3761062
Ref: 13bd3761062
Ref: reference/introduction grammar-token-name3761225
Ref: 13be3761225
Ref: reference/introduction grammar-token-lc-letter3761273
Ref: 13bf3761273
Node: Lexical analysis3763303
Ref: reference/lexical_analysis doc3763422
Ref: 13c03763422
Ref: reference/lexical_analysis lexical3763422
Ref: 13c13763422
Ref: reference/lexical_analysis lexical-analysis3763422
Ref: 13c23763422
Ref: Lexical analysis-Footnote-13764067
Node: Line structure3764116
Ref: reference/lexical_analysis id13764204
Ref: 13c33764204
Ref: reference/lexical_analysis line-structure3764204
Ref: 13c43764204
Node: Logical lines3764510
Ref: reference/lexical_analysis id23764597
Ref: 13c53764597
Ref: reference/lexical_analysis logical-lines3764597
Ref: 13c63764597
Node: Physical lines3764975
Ref: reference/lexical_analysis id33765079
Ref: 13c73765079
Ref: reference/lexical_analysis physical-lines3765079
Ref: 13c83765079
Node: Comments3765850
Ref: reference/lexical_analysis comments3765962
Ref: 13c93765962
Ref: reference/lexical_analysis id43765962
Ref: 13ca3765962
Node: Encoding declarations3766265
Ref: reference/lexical_analysis encoding-declarations3766384
Ref: 13cb3766384
Ref: reference/lexical_analysis encodings3766384
Ref: 13cc3766384
Node: Explicit line joining3767514
Ref: reference/lexical_analysis explicit-joining3767646
Ref: 13cd3767646
Ref: reference/lexical_analysis explicit-line-joining3767646
Ref: 13ce3767646
Node: Implicit line joining3768580
Ref: reference/lexical_analysis implicit-joining3768702
Ref: 13cf3768702
Ref: reference/lexical_analysis implicit-line-joining3768702
Ref: 13d03768702
Node: Blank lines3769538
Ref: reference/lexical_analysis blank-lines3769650
Ref: 13d13769650
Ref: reference/lexical_analysis id53769650
Ref: 13d23769650
Node: Indentation3770125
Ref: reference/lexical_analysis id63770241
Ref: 13d33770241
Ref: reference/lexical_analysis indentation3770241
Ref: 13d43770241
Node: Whitespace between tokens3773627
Ref: reference/lexical_analysis whitespace3773723
Ref: 13d53773723
Ref: reference/lexical_analysis whitespace-between-tokens3773723
Ref: 13d63773723
Node: Other tokens3774125
Ref: reference/lexical_analysis id73774246
Ref: 13d73774246
Ref: reference/lexical_analysis other-tokens3774246
Ref: 13d83774246
Node: Identifiers and keywords3774678
Ref: reference/lexical_analysis identifiers3774793
Ref: 13d93774793
Ref: reference/lexical_analysis identifiers-and-keywords3774793
Ref: 13da3774793
Ref: reference/lexical_analysis grammar-token-identifier3775688
Ref: 13db3775688
Ref: reference/lexical_analysis grammar-token-id-start3775734
Ref: 13dc3775734
Ref: reference/lexical_analysis grammar-token-id-continue3775883
Ref: 13dd3775883
Ref: reference/lexical_analysis grammar-token-xid-start3776031
Ref: 13de3776031
Ref: reference/lexical_analysis grammar-token-xid-continue3776138
Ref: 13df3776138
Ref: Identifiers and keywords-Footnote-13777137
Ref: Identifiers and keywords-Footnote-23777186
Ref: Identifiers and keywords-Footnote-33777235
Node: Keywords3777297
Ref: reference/lexical_analysis id83777406
Ref: 13e03777406
Ref: reference/lexical_analysis keywords3777406
Ref: 13e13777406
Node: Reserved classes of identifiers3778001
Ref: reference/lexical_analysis id-classes3778110
Ref: 13e23778110
Ref: reference/lexical_analysis reserved-classes-of-identifiers3778110
Ref: 13e33778110
Node: Literals3779747
Ref: reference/lexical_analysis id93779859
Ref: 13e53779859
Ref: reference/lexical_analysis literals3779859
Ref: 13e63779859
Node: String and Bytes literals3780154
Ref: reference/lexical_analysis string-and-bytes-literals3780261
Ref: 13e73780261
Ref: reference/lexical_analysis strings3780261
Ref: 13e83780261
Ref: reference/lexical_analysis grammar-token-stringliteral3780399
Ref: 13e93780399
Ref: reference/lexical_analysis grammar-token-stringprefix3780465
Ref: 13ea3780465
Ref: reference/lexical_analysis grammar-token-shortstring3780605
Ref: 13eb3780605
Ref: reference/lexical_analysis grammar-token-longstring3780682
Ref: 13ec3780682
Ref: reference/lexical_analysis grammar-token-shortstringitem3780765
Ref: 13ed3780765
Ref: reference/lexical_analysis grammar-token-longstringitem3780824
Ref: 13ee3780824
Ref: reference/lexical_analysis grammar-token-shortstringchar3780882
Ref: 13ef3780882
Ref: reference/lexical_analysis grammar-token-longstringchar3780965
Ref: 13f03780965
Ref: reference/lexical_analysis grammar-token-stringescapeseq3781024
Ref: 13f13781024
Ref: reference/lexical_analysis grammar-token-bytesliteral3781077
Ref: 13f23781077
Ref: reference/lexical_analysis grammar-token-bytesprefix3781137
Ref: 13f33781137
Ref: reference/lexical_analysis grammar-token-shortbytes3781227
Ref: 13f43781227
Ref: reference/lexical_analysis grammar-token-longbytes3781301
Ref: 13f53781301
Ref: reference/lexical_analysis grammar-token-shortbytesitem3781381
Ref: 13f63781381
Ref: reference/lexical_analysis grammar-token-longbytesitem3781437
Ref: 13f73781437
Ref: reference/lexical_analysis grammar-token-shortbyteschar3781492
Ref: 13f83781492
Ref: reference/lexical_analysis grammar-token-longbyteschar3781573
Ref: 13f93781573
Ref: reference/lexical_analysis grammar-token-bytesescapeseq3781630
Ref: 13fa3781630
Ref: String and Bytes literals-Footnote-13788995
Ref: String and Bytes literals-Footnote-23789044
Node: String literal concatenation3789119
Ref: reference/lexical_analysis string-concatenation3789260
Ref: 13fb3789260
Ref: reference/lexical_analysis string-literal-concatenation3789260
Ref: 13fc3789260
Node: Formatted string literals3790303
Ref: reference/lexical_analysis f-strings3790435
Ref: 15d3790435
Ref: reference/lexical_analysis formatted-string-literals3790435
Ref: 13fd3790435
Ref: reference/lexical_analysis grammar-token-f-string3791044
Ref: 13fe3791044
Ref: reference/lexical_analysis grammar-token-replacement-field3791121
Ref: 13ff3791121
Ref: reference/lexical_analysis grammar-token-f-expression3791210
Ref: 14003791210
Ref: reference/lexical_analysis grammar-token-conversion3791405
Ref: 14013791405
Ref: reference/lexical_analysis grammar-token-format-spec3791448
Ref: 14023791448
Ref: reference/lexical_analysis grammar-token-literal-char3791518
Ref: 14033791518
Ref: Formatted string literals-Footnote-13796637
Node: Numeric literals3796686
Ref: reference/lexical_analysis numbers3796806
Ref: 14043796806
Ref: reference/lexical_analysis numeric-literals3796806
Ref: 14053796806
Node: Integer literals3797240
Ref: reference/lexical_analysis integer-literals3797358
Ref: 14063797358
Ref: reference/lexical_analysis integers3797358
Ref: 14073797358
Ref: reference/lexical_analysis grammar-token-integer3797479
Ref: 14083797479
Ref: reference/lexical_analysis grammar-token-decinteger3797551
Ref: 14093797551
Ref: reference/lexical_analysis grammar-token-bininteger3797621
Ref: 140a3797621
Ref: reference/lexical_analysis grammar-token-octinteger3797677
Ref: 140b3797677
Ref: reference/lexical_analysis grammar-token-hexinteger3797733
Ref: 140c3797733
Ref: reference/lexical_analysis grammar-token-nonzerodigit3797789
Ref: 140d3797789
Ref: reference/lexical_analysis grammar-token-digit3797821
Ref: 140e3797821
Ref: reference/lexical_analysis grammar-token-bindigit3797853
Ref: 140f3797853
Ref: reference/lexical_analysis grammar-token-octdigit3797885
Ref: 14103797885
Ref: reference/lexical_analysis grammar-token-hexdigit3797917
Ref: 14113797917
Node: Floating point literals3798762
Ref: reference/lexical_analysis floating3798882
Ref: 14123798882
Ref: reference/lexical_analysis floating-point-literals3798882
Ref: 14133798882
Ref: reference/lexical_analysis grammar-token-floatnumber3799024
Ref: 14143799024
Ref: reference/lexical_analysis grammar-token-pointfloat3799074
Ref: 14153799074
Ref: reference/lexical_analysis grammar-token-exponentfloat3799134
Ref: 14163799134
Ref: reference/lexical_analysis grammar-token-digitpart3799191
Ref: 14173799191
Ref: reference/lexical_analysis grammar-token-fraction3799235
Ref: 14183799235
Ref: reference/lexical_analysis grammar-token-exponent3799272
Ref: 14193799272
Node: Imaginary literals3799829
Ref: reference/lexical_analysis imaginary3799924
Ref: 141a3799924
Ref: reference/lexical_analysis imaginary-literals3799924
Ref: 141b3799924
Ref: reference/lexical_analysis grammar-token-imagnumber3800051
Ref: 141c3800051
Node: Operators3800514
Ref: reference/lexical_analysis id113800612
Ref: 141d3800612
Ref: reference/lexical_analysis operators3800612
Ref: 141e3800612
Node: Delimiters3800849
Ref: reference/lexical_analysis delimiters3800930
Ref: 141f3800930
Ref: reference/lexical_analysis id123800930
Ref: 14203800930
Node: Data model3801859
Ref: reference/datamodel doc3801984
Ref: 14213801984
Ref: reference/datamodel data-model3801984
Ref: 14223801984
Ref: reference/datamodel datamodel3801984
Ref: f303801984
Node: Objects values and types3802152
Ref: reference/datamodel objects3802259
Ref: 14233802259
Ref: reference/datamodel objects-values-and-types3802259
Ref: 14243802259
Ref: Objects values and types-Footnote-13807054
Node: The standard type hierarchy3807285
Ref: reference/datamodel the-standard-type-hierarchy3807421
Ref: 14253807421
Ref: reference/datamodel types3807421
Ref: 14263807421
Ref: reference/datamodel frame-objects3843663
Ref: 14373843663
Ref: reference/datamodel frame clear3845558
Ref: 8103845558
Ref: reference/datamodel traceback-objects3846116
Ref: 33b3846116
Ref: reference/datamodel slice indices3848936
Ref: 9643848936
Node: Special method names3850708
Ref: reference/datamodel special-method-names3850830
Ref: 14383850830
Ref: reference/datamodel specialnames3850830
Ref: 5133850830
Ref: Special method names-Footnote-13852662
Node: Basic customization3852944
Ref: reference/datamodel basic-customization3853057
Ref: 14393853057
Ref: reference/datamodel customization3853057
Ref: 143a3853057
Ref: reference/datamodel object __new__3853114
Ref: 88e3853114
Ref: reference/datamodel object __init__3854694
Ref: d633854694
Ref: reference/datamodel object __del__3855559
Ref: 9243855559
Ref: reference/datamodel object __repr__3858696
Ref: 3433858696
Ref: reference/datamodel object __str__3859540
Ref: e3c3859540
Ref: reference/datamodel object __bytes__3860194
Ref: 143c3860194
Ref: reference/datamodel object __format__3860384
Ref: 9533860384
Ref: reference/datamodel richcmpfuncs3861477
Ref: 143d3861477
Ref: reference/datamodel object __lt__3861477
Ref: c393861477
Ref: reference/datamodel object __le__3861523
Ref: ca53861523
Ref: reference/datamodel object __eq__3861569
Ref: 3443861569
Ref: reference/datamodel object __ne__3861615
Ref: e5b3861615
Ref: reference/datamodel object __gt__3861661
Ref: ca63861661
Ref: reference/datamodel object __ge__3861707
Ref: ca73861707
Ref: reference/datamodel object __hash__3864229
Ref: 3453864229
Ref: reference/datamodel object __bool__3868440
Ref: c6d3868440
Node: Customizing attribute access3868896
Ref: reference/datamodel attribute-access3869044
Ref: 143e3869044
Ref: reference/datamodel customizing-attribute-access3869044
Ref: 143f3869044
Ref: reference/datamodel object __getattr__3869276
Ref: 31f3869276
Ref: reference/datamodel object __getattribute__3870528
Ref: 44e3870528
Ref: reference/datamodel object __setattr__3871629
Ref: e313871629
Ref: reference/datamodel object __delattr__3872308
Ref: 14353872308
Ref: reference/datamodel object __dir__3872698
Ref: 3203872698
Node: Customizing module attribute access3873032
Ref: reference/datamodel customizing-module-attribute-access3873165
Ref: 14423873165
Ref: Customizing module attribute access-Footnote-13875281
Node: Implementing Descriptors3875330
Ref: reference/datamodel descriptors3875492
Ref: 4ee3875492
Ref: reference/datamodel implementing-descriptors3875492
Ref: 14433875492
Ref: reference/datamodel object __get__3875968
Ref: 14403875968
Ref: reference/datamodel object __set__3876905
Ref: 14443876905
Ref: reference/datamodel object __delete__3877265
Ref: 14453877265
Ref: reference/datamodel object __set_name__3877407
Ref: 4ed3877407
Ref: Implementing Descriptors-Footnote-13878616
Node: Invoking Descriptors3878665
Ref: reference/datamodel descriptor-invocation3878801
Ref: 14463878801
Ref: reference/datamodel invoking-descriptors3878801
Ref: 14473878801
Node: __slots__3882007
Ref: reference/datamodel id33882110
Ref: 14483882110
Ref: reference/datamodel slots3882110
Ref: 14493882110
Ref: reference/datamodel object __slots__3882468
Ref: e323882468
Node: Notes on using __slots__3882821
Ref: reference/datamodel notes-on-using-slots3882891
Ref: 144a3882891
Node: Customizing class creation3885675
Ref: reference/datamodel class-customization3885844
Ref: 4ea3885844
Ref: reference/datamodel customizing-class-creation3885844
Ref: 144b3885844
Ref: reference/datamodel object __init_subclass__3886311
Ref: 4e83886311
Node: Metaclasses3887855
Ref: reference/datamodel id43887959
Ref: 144c3887959
Ref: reference/datamodel metaclasses3887959
Ref: 144d3887959
Node: Resolving MRO entries3889014
Ref: reference/datamodel resolving-mro-entries3889164
Ref: 144e3889164
Ref: Resolving MRO entries-Footnote-13889690
Node: Determining the appropriate metaclass3889739
Ref: reference/datamodel determining-the-appropriate-metaclass3889907
Ref: 144f3889907
Node: Preparing the class namespace3890838
Ref: reference/datamodel prepare3891009
Ref: 5023891009
Ref: reference/datamodel preparing-the-class-namespace3891009
Ref: 14503891009
Ref: Preparing the class namespace-Footnote-13891913
Node: Executing the class body3891962
Ref: reference/datamodel executing-the-class-body3892121
Ref: 14513892121
Node: Creating the class object3892856
Ref: reference/datamodel class-object-creation3893006
Ref: 4e93893006
Ref: reference/datamodel creating-the-class-object3893006
Ref: 14523893006
Ref: Creating the class object-Footnote-13895476
Node: Uses for metaclasses3895525
Ref: reference/datamodel uses-for-metaclasses3895642
Ref: 14533895642
Node: Customizing instance and subclass checks3895953
Ref: reference/datamodel customizing-instance-and-subclass-checks3896117
Ref: 14543896117
Ref: reference/datamodel class __instancecheck__3896603
Ref: 14553896603
Ref: reference/datamodel class __subclasscheck__3896838
Ref: 14563896838
Ref: Customizing instance and subclass checks-Footnote-13897796
Node: Emulating generic types3897845
Ref: reference/datamodel emulating-generic-types3898009
Ref: 14573898009
Ref: reference/datamodel object __class_getitem__3898207
Ref: 32c3898207
Ref: Emulating generic types-Footnote-13898740
Ref: Emulating generic types-Footnote-23898789
Node: Emulating callable objects3898838
Ref: reference/datamodel callable-types3898987
Ref: 14583898987
Ref: reference/datamodel emulating-callable-objects3898987
Ref: 14593898987
Ref: reference/datamodel object __call__3899060
Ref: 14333899060
Node: Emulating container types3899293
Ref: reference/datamodel emulating-container-types3899442
Ref: 145a3899442
Ref: reference/datamodel sequence-types3899442
Ref: 145b3899442
Ref: reference/datamodel object __len__3901652
Ref: dd03901652
Ref: reference/datamodel object __length_hint__3902396
Ref: 8113902396
Ref: reference/datamodel object __getitem__3903189
Ref: 27d3903189
Ref: reference/datamodel object __setitem__3904093
Ref: c673904093
Ref: reference/datamodel object __delitem__3904561
Ref: c683904561
Ref: reference/datamodel object __missing__3904993
Ref: b403904993
Ref: reference/datamodel object __iter__3905190
Ref: 5143905190
Ref: reference/datamodel object __reversed__3905674
Ref: 5343905674
Ref: reference/datamodel object __contains__3906664
Ref: d2d3906664
Node: Emulating numeric types3907234
Ref: reference/datamodel emulating-numeric-types3907388
Ref: 14643907388
Ref: reference/datamodel numeric-types3907388
Ref: 14653907388
Ref: reference/datamodel object __add__3907703
Ref: 145c3907703
Ref: reference/datamodel object __sub__3907750
Ref: 14663907750
Ref: reference/datamodel object __mul__3907797
Ref: 145e3907797
Ref: reference/datamodel object __matmul__3907844
Ref: 64d3907844
Ref: reference/datamodel object __truediv__3907894
Ref: 78b3907894
Ref: reference/datamodel object __floordiv__3907945
Ref: e3a3907945
Ref: reference/datamodel object __mod__3907997
Ref: 14673907997
Ref: reference/datamodel object __divmod__3908044
Ref: 78c3908044
Ref: reference/datamodel object __pow__3908094
Ref: 14683908094
Ref: reference/datamodel object __lshift__3908151
Ref: 14693908151
Ref: reference/datamodel object __rshift__3908201
Ref: 146a3908201
Ref: reference/datamodel object __and__3908251
Ref: 146b3908251
Ref: reference/datamodel object __xor__3908298
Ref: 146c3908298
Ref: reference/datamodel object __or__3908345
Ref: 146d3908345
Ref: reference/datamodel object __radd__3909334
Ref: 145d3909334
Ref: reference/datamodel object __rsub__3909382
Ref: 146e3909382
Ref: reference/datamodel object __rmul__3909430
Ref: 145f3909430
Ref: reference/datamodel object __rmatmul__3909478
Ref: 64e3909478
Ref: reference/datamodel object __rtruediv__3909529
Ref: 146f3909529
Ref: reference/datamodel object __rfloordiv__3909581
Ref: 14703909581
Ref: reference/datamodel object __rmod__3909634
Ref: 6b43909634
Ref: reference/datamodel object __rdivmod__3909682
Ref: 14713909682
Ref: reference/datamodel object __rpow__3909733
Ref: 14723909733
Ref: reference/datamodel object __rlshift__3909791
Ref: 14733909791
Ref: reference/datamodel object __rrshift__3909842
Ref: 14743909842
Ref: reference/datamodel object __rand__3909893
Ref: 14753909893
Ref: reference/datamodel object __rxor__3909941
Ref: 14763909941
Ref: reference/datamodel object __ror__3909989
Ref: 14773909989
Ref: reference/datamodel object __iadd__3911250
Ref: e743911250
Ref: reference/datamodel object __isub__3911298
Ref: e753911298
Ref: reference/datamodel object __imul__3911346
Ref: 14603911346
Ref: reference/datamodel object __imatmul__3911394
Ref: 64f3911394
Ref: reference/datamodel object __itruediv__3911445
Ref: 14783911445
Ref: reference/datamodel object __ifloordiv__3911497
Ref: 14793911497
Ref: reference/datamodel object __imod__3911550
Ref: 147a3911550
Ref: reference/datamodel object __ipow__3911598
Ref: 147b3911598
Ref: reference/datamodel object __ilshift__3911656
Ref: 147c3911656
Ref: reference/datamodel object __irshift__3911707
Ref: 147d3911707
Ref: reference/datamodel object __iand__3911758
Ref: 147e3911758
Ref: reference/datamodel object __ixor__3911806
Ref: 147f3911806
Ref: reference/datamodel object __ior__3911854
Ref: 14803911854
Ref: reference/datamodel object __neg__3913205
Ref: 14823913205
Ref: reference/datamodel object __pos__3913245
Ref: 14833913245
Ref: reference/datamodel object __abs__3913285
Ref: 14843913285
Ref: reference/datamodel object __invert__3913325
Ref: 14853913325
Ref: reference/datamodel object __complex__3913484
Ref: 18e3913484
Ref: reference/datamodel object __int__3913528
Ref: 18c3913528
Ref: reference/datamodel object __float__3913568
Ref: 18d3913568
Ref: reference/datamodel object __index__3913782
Ref: 18b3913782
Ref: reference/datamodel object __round__3914462
Ref: 14873914462
Ref: reference/datamodel object __trunc__3914515
Ref: 14883914515
Ref: reference/datamodel object __floor__3914557
Ref: 14893914557
Ref: reference/datamodel object __ceil__3914599
Ref: 148a3914599
Ref: Emulating numeric types-Footnote-13915168
Ref: Emulating numeric types-Footnote-23915483
Node: With Statement Context Managers3915712
Ref: reference/datamodel context-managers3915862
Ref: 148b3915862
Ref: reference/datamodel with-statement-context-managers3915862
Ref: 148c3915862
Ref: reference/datamodel object __enter__3916625
Ref: c9a3916625
Ref: reference/datamodel object __exit__3916881
Ref: c9b3916881
Ref: With Statement Context Managers-Footnote-13917770
Node: Special method lookup3917819
Ref: reference/datamodel special-lookup3917937
Ref: 14413917937
Ref: reference/datamodel special-method-lookup3917937
Ref: 148e3917937
Node: Coroutines3920658
Ref: reference/datamodel coroutines3920744
Ref: 148f3920744
Node: Awaitable Objects3920894
Ref: reference/datamodel awaitable-objects3920984
Ref: 14903920984
Ref: reference/datamodel object __await__3921465
Ref: 6473921465
Ref: Awaitable Objects-Footnote-13921884
Node: Coroutine Objects3921933
Ref: reference/datamodel coroutine-objects3922054
Ref: 14323922054
Ref: reference/datamodel id73922054
Ref: 14913922054
Ref: reference/datamodel coroutine send3922915
Ref: 14933922915
Ref: reference/datamodel coroutine throw3923460
Ref: 14953923460
Ref: reference/datamodel coroutine close3924062
Ref: 14973924062
Node: Asynchronous Iterators3924690
Ref: reference/datamodel async-iterators3924823
Ref: 64b3924823
Ref: reference/datamodel asynchronous-iterators3924823
Ref: 14993924823
Ref: reference/datamodel object __aiter__3925047
Ref: 48c3925047
Ref: reference/datamodel object __anext__3925143
Ref: 149a3925143
Node: Asynchronous Context Managers3926020
Ref: reference/datamodel async-context-managers3926127
Ref: 149b3926127
Ref: reference/datamodel asynchronous-context-managers3926127
Ref: 149c3926127
Ref: reference/datamodel object __aenter__3926432
Ref: 149d3926432
Ref: reference/datamodel object __aexit__3926597
Ref: 149e3926597
Node: Execution model3927089
Ref: reference/executionmodel doc3927215
Ref: 149f3927215
Ref: reference/executionmodel execmodel3927215
Ref: 14a03927215
Ref: reference/executionmodel execution-model3927215
Ref: 14a13927215
Node: Structure of a program3927331
Ref: reference/executionmodel prog-structure3927432
Ref: 14a23927432
Ref: reference/executionmodel structure-of-a-program3927432
Ref: 14a33927432
Node: Naming and binding3928337
Ref: reference/executionmodel naming3928457
Ref: 14a43928457
Ref: reference/executionmodel naming-and-binding3928457
Ref: 14a53928457
Node: Binding of names3928639
Ref: reference/executionmodel bind-names3928738
Ref: 14a63928738
Ref: reference/executionmodel binding-of-names3928738
Ref: 14a73928738
Node: Resolution of names3930224
Ref: reference/executionmodel resolution-of-names3930365
Ref: 14a83930365
Ref: reference/executionmodel resolve-names3930365
Ref: 14a93930365
Node: Builtins and restricted execution3933757
Ref: reference/executionmodel builtins-and-restricted-execution3933915
Ref: 14aa3933915
Ref: reference/executionmodel restrict-exec3933915
Ref: 14ab3933915
Node: Interaction with dynamic features3934760
Ref: reference/executionmodel dynamic-features3934890
Ref: 14ac3934890
Ref: reference/executionmodel interaction-with-dynamic-features3934890
Ref: 14ad3934890
Ref: Interaction with dynamic features-Footnote-13935682
Node: Exceptions3935824
Ref: reference/executionmodel exceptions3935913
Ref: 14ae3935913
Ref: reference/executionmodel id23935913
Ref: 14af3935913
Node: The import system3938083
Ref: reference/import doc3938210
Ref: 14b03938210
Ref: reference/import importsystem3938210
Ref: 14343938210
Ref: reference/import the-import-system3938210
Ref: 14b13938210
Ref: The import system-Footnote-13940850
Ref: The import system-Footnote-23940895
Ref: The import system-Footnote-33940944
Node: importlib<7>3940993
Ref: reference/import importlib3941079
Ref: 14b43941079
Node: Packages<2>3941454
Ref: reference/import packages3941558
Ref: 14b53941558
Node: Regular packages3942994
Ref: reference/import regular-packages3943085
Ref: 14b63943085
Node: Namespace packages3944297
Ref: reference/import namespace-packages3944388
Ref: 14b93944388
Ref: Namespace packages-Footnote-13945765
Node: Searching3945814
Ref: reference/import searching3945913
Ref: 14bb3945913
Node: The module cache3946738
Ref: reference/import the-module-cache3946828
Ref: 14bc3946828
Node: Finders and loaders3948387
Ref: reference/import finders-and-loaders3948498
Ref: 14bd3948498
Ref: reference/import id23948498
Ref: 14be3948498
Node: Import hooks3950245
Ref: reference/import import-hooks3950353
Ref: 14c33950353
Node: The meta path3951224
Ref: reference/import the-meta-path3951304
Ref: 14c43951304
Node: Loading3954294
Ref: reference/import loading3954403
Ref: 14c63954403
Ref: Loading-Footnote-13957690
Node: Loaders3958072
Ref: reference/import loaders3958142
Ref: 14c83958142
Node: Submodules3961365
Ref: reference/import submodules3961455
Ref: 14c93961455
Node: Module spec3962759
Ref: reference/import module-spec3962874
Ref: 14ca3962874
Node: Import-related module attributes3963711
Ref: reference/import import-mod-attrs3963831
Ref: 14c73963831
Ref: reference/import import-related-module-attributes3963831
Ref: 14cc3963831
Ref: reference/import __name__3964069
Ref: d173964069
Ref: reference/import __loader__3964264
Ref: 95b3964264
Ref: reference/import __package__3964577
Ref: 95a3964577
Ref: reference/import __spec__3965392
Ref: ebd3965392
Ref: reference/import __path__3965987
Ref: 12943965987
Ref: reference/import __file__3966476
Ref: ebc3966476
Ref: reference/import __cached__3966498
Ref: b373966498
Ref: Import-related module attributes-Footnote-13967484
Ref: Import-related module attributes-Footnote-23967533
Ref: Import-related module attributes-Footnote-33967582
Node: module __path__3967631
Ref: reference/import module-path3967752
Ref: 14d03967752
Ref: reference/import package-path-rules3967752
Ref: 14cf3967752
Ref: module __path__-Footnote-13968934
Ref: module __path__-Footnote-23968983
Node: Module reprs3969032
Ref: reference/import module-reprs3969149
Ref: 14d13969149
Node: Cached bytecode invalidation3970795
Ref: reference/import cached-bytecode-invalidation3970888
Ref: 14d23970888
Ref: reference/import pyc-invalidation3970888
Ref: 32e3970888
Node: The Path Based Finder3972226
Ref: reference/import the-path-based-finder3972362
Ref: 14d33972362
Node: Path entry finders3974866
Ref: reference/import path-entry-finders3974977
Ref: 14d53974977
Ref: Path entry finders-Footnote-13980034
Node: Path entry finder protocol3980292
Ref: reference/import path-entry-finder-protocol3980403
Ref: 14d73980403
Node: Replacing the standard import system3982554
Ref: reference/import replacing-the-standard-import-system3982707
Ref: 14d83982707
Node: Package Relative Imports3983710
Ref: reference/import package-relative-imports3983877
Ref: 14d93983877
Ref: reference/import relativeimports3983877
Ref: 14da3983877
Node: Special considerations for __main__3985080
Ref: reference/import special-considerations-for-main3985222
Ref: 14db3985222
Node: __main__ __spec__3985825
Ref: reference/import id53985914
Ref: 14dc3985914
Ref: reference/import main-spec3985914
Ref: 14ce3985914
Node: Open issues3987312
Ref: reference/import open-issues3987440
Ref: 14dd3987440
Ref: Open issues-Footnote-13988072
Node: References3988121
Ref: reference/import references3988205
Ref: 14de3988205
Ref: References-Footnote-13989451
Ref: References-Footnote-23989503
Ref: References-Footnote-33989552
Ref: References-Footnote-43989601
Ref: References-Footnote-53989650
Ref: References-Footnote-63989699
Ref: References-Footnote-73989748
Ref: References-Footnote-83989797
Ref: References-Footnote-93989846
Ref: References-Footnote-103989895
Node: Expressions3989945
Ref: reference/expressions doc3990074
Ref: 14df3990074
Ref: reference/expressions expressions3990074
Ref: 14e03990074
Ref: reference/expressions id13990074
Ref: 14e13990074
Ref: reference/expressions grammar-token-name3990368
Ref: 14e23990368
Node: Arithmetic conversions3990934
Ref: reference/expressions arithmetic-conversions3991018
Ref: 14e33991018
Ref: reference/expressions conversions3991018
Ref: 14e43991018
Node: Atoms3991717
Ref: reference/expressions atoms3991819
Ref: 14e53991819
Ref: reference/expressions id23991819
Ref: 14e63991819
Ref: reference/expressions grammar-token-atom3992066
Ref: 14e73992066
Ref: reference/expressions grammar-token-enclosure3992118
Ref: 14e83992118
Node: Identifiers Names3992545
Ref: reference/expressions atom-identifiers3992624
Ref: 13e43992624
Ref: reference/expressions identifiers-names3992624
Ref: 14e93992624
Node: Literals<2>3993918
Ref: reference/expressions atom-literals3994025
Ref: 14ea3994025
Ref: reference/expressions literals3994025
Ref: 14eb3994025
Ref: reference/expressions grammar-token-literal3994133
Ref: 14ec3994133
Node: Parenthesized forms3994840
Ref: reference/expressions parenthesized3994970
Ref: 14ed3994970
Ref: reference/expressions parenthesized-forms3994970
Ref: 14ee3994970
Ref: reference/expressions grammar-token-parenth-form3995105
Ref: 14ef3995105
Node: Displays for lists sets and dictionaries3995865
Ref: reference/expressions comprehensions3995997
Ref: 14f03995997
Ref: reference/expressions displays-for-lists-sets-and-dictionaries3995997
Ref: 14f13995997
Ref: reference/expressions grammar-token-comprehension3996439
Ref: 14f23996439
Ref: reference/expressions grammar-token-comp-for3996493
Ref: 14f33996493
Ref: reference/expressions grammar-token-comp-iter3996569
Ref: 14f43996569
Ref: reference/expressions grammar-token-comp-if3996611
Ref: 14f53996611
Ref: Displays for lists sets and dictionaries-Footnote-13998787
Node: List displays3998836
Ref: reference/expressions list-displays3998961
Ref: 14f63998961
Ref: reference/expressions lists3998961
Ref: 14f73998961
Ref: reference/expressions grammar-token-list-display3999093
Ref: 14f83999093
Node: Set displays3999539
Ref: reference/expressions set3999643
Ref: 14f93999643
Ref: reference/expressions set-displays3999643
Ref: 14fa3999643
Ref: reference/expressions grammar-token-set-display3999823
Ref: 14fb3999823
Node: Dictionary displays4000355
Ref: reference/expressions dict4000467
Ref: 6534000467
Ref: reference/expressions dictionary-displays4000467
Ref: 14fc4000467
Ref: reference/expressions grammar-token-dict-display4000618
Ref: 14fd4000618
Ref: reference/expressions grammar-token-key-datum-list4000692
Ref: 14fe4000692
Ref: reference/expressions grammar-token-key-datum4000753
Ref: 14ff4000753
Ref: reference/expressions grammar-token-dict-comprehension4000822
Ref: 15004000822
Ref: Dictionary displays-Footnote-14002618
Ref: Dictionary displays-Footnote-24002667
Node: Generator expressions4002716
Ref: reference/expressions generator-expressions4002833
Ref: 15014002833
Ref: reference/expressions genexpr4002833
Ref: 15024002833
Ref: reference/expressions grammar-token-generator-expression4002966
Ref: 15034002966
Node: Yield expressions4004890
Ref: reference/expressions yield-expressions4004979
Ref: 15044004979
Ref: reference/expressions yieldexpr4004979
Ref: 15054004979
Ref: reference/expressions grammar-token-yield-atom4005032
Ref: 15064005032
Ref: reference/expressions grammar-token-yield-expression4005083
Ref: 15074005083
Ref: Yield expressions-Footnote-14009949
Ref: Yield expressions-Footnote-24009998
Ref: Yield expressions-Footnote-34010047
Ref: Yield expressions-Footnote-44010096
Ref: Yield expressions-Footnote-54010145
Node: Generator-iterator methods4010194
Ref: reference/expressions generator-iterator-methods4010291
Ref: 150b4010291
Ref: reference/expressions generator-methods4010291
Ref: 14924010291
Ref: reference/expressions generator __next__4010633
Ref: 12df4010633
Ref: reference/expressions generator send4011402
Ref: 14944011402
Ref: reference/expressions generator throw4011986
Ref: 14964011986
Ref: reference/expressions generator close4012478
Ref: 14984012478
Node: Examples4013069
Ref: reference/expressions examples4013207
Ref: 150c4013207
Node: Asynchronous generator functions4014262
Ref: reference/expressions asynchronous-generator-functions4014413
Ref: 15094014413
Ref: reference/expressions id34014413
Ref: 150d4014413
Ref: Asynchronous generator functions-Footnote-14017481
Node: Asynchronous generator-iterator methods4017560
Ref: reference/expressions asynchronous-generator-iterator-methods4017694
Ref: 15114017694
Ref: reference/expressions asynchronous-generator-methods4017694
Ref: 15124017694
Ref: reference/expressions agen __anext__4017936
Ref: 150e4017936
Ref: reference/expressions agen asend4018873
Ref: 150f4018873
Ref: reference/expressions agen athrow4019740
Ref: 15134019740
Ref: reference/expressions agen aclose4020434
Ref: 15104020434
Node: Primaries4021455
Ref: reference/expressions id44021551
Ref: 15144021551
Ref: reference/expressions primaries4021551
Ref: 15154021551
Ref: reference/expressions grammar-token-primary4021673
Ref: 15164021673
Node: Attribute references4021819
Ref: reference/expressions attribute-references4021907
Ref: 15174021907
Ref: reference/expressions id54021907
Ref: 15184021907
Ref: reference/expressions grammar-token-attributeref4022036
Ref: 15194022036
Node: Subscriptions4022615
Ref: reference/expressions id64022720
Ref: 151a4022720
Ref: reference/expressions subscriptions4022720
Ref: 151b4022720
Ref: reference/expressions grammar-token-subscription4022867
Ref: 151c4022867
Node: Slicings4024392
Ref: reference/expressions id74024482
Ref: 151d4024482
Ref: reference/expressions slicings4024482
Ref: 151e4024482
Ref: reference/expressions grammar-token-slicing4024731
Ref: 151f4024731
Ref: reference/expressions grammar-token-slice-list4024780
Ref: 15204024780
Ref: reference/expressions grammar-token-slice-item4024837
Ref: 15214024837
Ref: reference/expressions grammar-token-proper-slice4024885
Ref: 15224024885
Ref: reference/expressions grammar-token-lower-bound4024956
Ref: 15234024956
Ref: reference/expressions grammar-token-upper-bound4024989
Ref: 15244024989
Ref: reference/expressions grammar-token-stride4025022
Ref: 15254025022
Node: Calls4026240
Ref: reference/expressions calls4026308
Ref: 6514026308
Ref: reference/expressions id84026308
Ref: 15264026308
Ref: reference/expressions grammar-token-call4026457
Ref: 15294026457
Ref: reference/expressions grammar-token-argument-list4026541
Ref: 152a4026541
Ref: reference/expressions grammar-token-positional-arguments4026805
Ref: 152b4026805
Ref: reference/expressions grammar-token-positional-item4026874
Ref: 152c4026874
Ref: reference/expressions grammar-token-starred-and-keywords4026943
Ref: 152d4026943
Ref: reference/expressions grammar-token-keywords-arguments4027076
Ref: 152e4027076
Ref: reference/expressions grammar-token-keyword-item4027211
Ref: 152f4027211
Ref: Calls-Footnote-14033235
Node: Await expression4033284
Ref: reference/expressions await4033393
Ref: 1a44033393
Ref: reference/expressions await-expression4033393
Ref: 15314033393
Ref: reference/expressions grammar-token-await-expr4033582
Ref: 15324033582
Node: The power operator4033638
Ref: reference/expressions power4033777
Ref: 15334033777
Ref: reference/expressions the-power-operator4033777
Ref: 15344033777
Ref: reference/expressions grammar-token-power4033974
Ref: 15354033974
Node: Unary arithmetic and bitwise operations4035024
Ref: reference/expressions unary4035175
Ref: 15364035175
Ref: reference/expressions unary-arithmetic-and-bitwise-operations4035175
Ref: 15374035175
Ref: reference/expressions grammar-token-u-expr4035337
Ref: 15384035337
Node: Binary arithmetic operations4035857
Ref: reference/expressions binary4036009
Ref: 15394036009
Ref: reference/expressions binary-arithmetic-operations4036009
Ref: 153a4036009
Ref: reference/expressions grammar-token-m-expr4036353
Ref: 153b4036353
Ref: reference/expressions grammar-token-a-expr4036509
Ref: 153c4036509
Ref: Binary arithmetic operations-Footnote-14039364
Ref: Binary arithmetic operations-Footnote-24039981
Node: Shifting operations4040268
Ref: reference/expressions shifting4040406
Ref: 153e4040406
Ref: reference/expressions shifting-operations4040406
Ref: 153f4040406
Ref: reference/expressions grammar-token-shift-expr4040536
Ref: 15404040536
Node: Binary bitwise operations4040900
Ref: reference/expressions binary-bitwise-operations4041021
Ref: 15414041021
Ref: reference/expressions bitwise4041021
Ref: 15424041021
Ref: reference/expressions grammar-token-and-expr4041156
Ref: 15434041156
Ref: reference/expressions grammar-token-xor-expr4041211
Ref: 15444041211
Ref: reference/expressions grammar-token-or-expr4041262
Ref: 15454041262
Node: Comparisons4041600
Ref: reference/expressions comparisons4041720
Ref: 15464041720
Ref: reference/expressions id114041720
Ref: 15474041720
Ref: reference/expressions grammar-token-comparison4042015
Ref: 15484042015
Ref: reference/expressions grammar-token-comp-operator4042071
Ref: 15494042071
Node: Value comparisons4043011
Ref: reference/expressions value-comparisons4043111
Ref: 154a4043111
Ref: reference/expressions in4050960
Ref: 7a84050960
Ref: reference/expressions not-in4050960
Ref: 14624050960
Ref: Value comparisons-Footnote-14050998
Ref: Value comparisons-Footnote-24051047
Node: Membership test operations4052150
Ref: reference/expressions membership-test-details4052279
Ref: 14634052279
Ref: reference/expressions membership-test-operations4052279
Ref: 154b4052279
Ref: reference/expressions is4054173
Ref: ebf4054173
Node: Identity comparisons4054173
Ref: reference/expressions identity-comparisons4054276
Ref: 154c4054276
Ref: reference/expressions is-not4054276
Ref: 154d4054276
Ref: reference/expressions booleans4054621
Ref: 154e4054621
Ref: reference/expressions and4054621
Ref: 154f4054621
Ref: reference/expressions or4054621
Ref: 15504054621
Ref: Identity comparisons-Footnote-14054659
Node: Boolean operations4054965
Ref: reference/expressions boolean-operations4055085
Ref: 15514055085
Ref: reference/expressions not4055085
Ref: 15524055085
Ref: reference/expressions grammar-token-or-test4055138
Ref: 15534055138
Ref: reference/expressions grammar-token-and-test4055189
Ref: 15544055189
Ref: reference/expressions grammar-token-not-test4055242
Ref: 15554055242
Node: Assignment expressions<2>4056685
Ref: reference/expressions assignment-expressions4056817
Ref: 15564056817
Ref: reference/expressions grammar-token-assignment-expression4056878
Ref: 15574056878
Ref: Assignment expressions<2>-Footnote-14057516
Node: Conditional expressions4057565
Ref: reference/expressions conditional-expressions4057686
Ref: 15594057686
Ref: reference/expressions if-expr4057686
Ref: 155a4057686
Ref: reference/expressions grammar-token-conditional-expression4057749
Ref: 155b4057749
Ref: reference/expressions grammar-token-expression4057822
Ref: 15584057822
Ref: reference/expressions grammar-token-expression-nocond4057891
Ref: 155c4057891
Ref: reference/expressions lambdas4058335
Ref: 155d4058335
Ref: Conditional expressions-Footnote-14058373
Node: Lambdas4058422
Ref: reference/expressions id144058534
Ref: 155e4058534
Ref: reference/expressions lambda4058534
Ref: c344058534
Ref: reference/expressions grammar-token-lambda-expr4058565
Ref: 155f4058565
Ref: reference/expressions grammar-token-lambda-expr-nocond4058634
Ref: 15604058634
Node: Expression lists4059182
Ref: reference/expressions expression-lists4059287
Ref: 15614059287
Ref: reference/expressions exprlists4059287
Ref: 6524059287
Ref: reference/expressions grammar-token-expression-list4059336
Ref: 150a4059336
Ref: reference/expressions grammar-token-starred-list4059399
Ref: 15624059399
Ref: reference/expressions grammar-token-starred-expression4059466
Ref: 15634059466
Ref: reference/expressions grammar-token-starred-item4059542
Ref: 15644059542
Ref: Expression lists-Footnote-14060508
Node: Evaluation order4060557
Ref: reference/expressions evalorder4060674
Ref: 15654060674
Ref: reference/expressions evaluation-order4060674
Ref: 15664060674
Node: Operator precedence4061189
Ref: reference/expressions operator-precedence4061281
Ref: 15674061281
Ref: reference/expressions operator-summary4061281
Ref: 15684061281
Ref: Operator precedence-Footnote-14065840
Ref: Operator precedence-Footnote-24065938
Node: Simple statements4066091
Ref: reference/simple_stmts doc4066222
Ref: 15694066222
Ref: reference/simple_stmts simple4066222
Ref: 156a4066222
Ref: reference/simple_stmts simple-statements4066222
Ref: 156b4066222
Ref: reference/simple_stmts grammar-token-simple-stmt4066446
Ref: 156c4066446
Node: Expression statements4067391
Ref: reference/simple_stmts expression-statements4067496
Ref: 156d4067496
Ref: reference/simple_stmts exprstmts4067496
Ref: 156e4067496
Ref: reference/simple_stmts grammar-token-expression-stmt4067886
Ref: 156f4067886
Node: Assignment statements4068313
Ref: reference/simple_stmts assignment4068447
Ref: 15704068447
Ref: reference/simple_stmts assignment-statements4068447
Ref: 15714068447
Ref: reference/simple_stmts grammar-token-assignment-stmt4068618
Ref: 15724068618
Ref: reference/simple_stmts grammar-token-target-list4068702
Ref: 15734068702
Ref: reference/simple_stmts grammar-token-target4068754
Ref: 15744068754
Ref: reference/simple_stmts attr-target-note4072391
Ref: 15754072391
Ref: Assignment statements-Footnote-14076447
Node: Augmented assignment statements4076496
Ref: reference/simple_stmts augassign4076625
Ref: 15764076625
Ref: reference/simple_stmts augmented-assignment-statements4076625
Ref: 15774076625
Ref: reference/simple_stmts grammar-token-augmented-assignment-stmt4076822
Ref: 15784076822
Ref: reference/simple_stmts grammar-token-augtarget4076910
Ref: 15794076910
Ref: reference/simple_stmts grammar-token-augop4076996
Ref: 157a4076996
Node: Annotated assignment statements4078738
Ref: reference/simple_stmts annassign4078867
Ref: 157b4078867
Ref: reference/simple_stmts annotated-assignment-statements4078867
Ref: 157c4078867
Ref: reference/simple_stmts grammar-token-annotated-assignment-stmt4079102
Ref: 157d4079102
Ref: Annotated assignment statements-Footnote-14081039
Ref: Annotated assignment statements-Footnote-24081088
Node: The assert statement4081137
Ref: reference/simple_stmts assert4081268
Ref: e0b4081268
Ref: reference/simple_stmts the-assert-statement4081268
Ref: 157e4081268
Ref: reference/simple_stmts grammar-token-assert-stmt4081418
Ref: 157f4081418
Node: The pass statement4082505
Ref: reference/simple_stmts pass4082635
Ref: 12454082635
Ref: reference/simple_stmts the-pass-statement4082635
Ref: 15804082635
Ref: reference/simple_stmts grammar-token-pass-stmt4082694
Ref: 15814082694
Node: The del statement<2>4083045
Ref: reference/simple_stmts del4083175
Ref: 12734083175
Ref: reference/simple_stmts the-del-statement4083175
Ref: 15824083175
Ref: reference/simple_stmts grammar-token-del-stmt4083232
Ref: 15834083232
Node: The return statement4084144
Ref: reference/simple_stmts return4084275
Ref: 1914084275
Ref: reference/simple_stmts the-return-statement4084275
Ref: 15844084275
Ref: reference/simple_stmts grammar-token-return-stmt4084338
Ref: 15854084338
Node: The yield statement4085463
Ref: reference/simple_stmts the-yield-statement4085593
Ref: 15864085593
Ref: reference/simple_stmts yield4085593
Ref: 1904085593
Ref: reference/simple_stmts grammar-token-yield-stmt4085654
Ref: 15874085654
Node: The raise statement4086489
Ref: reference/simple_stmts raise4086618
Ref: c474086618
Ref: reference/simple_stmts the-raise-statement4086618
Ref: 15884086618
Ref: reference/simple_stmts grammar-token-raise-stmt4086679
Ref: 15894086679
Node: The break statement4090231
Ref: reference/simple_stmts break4090363
Ref: 2dc4090363
Ref: reference/simple_stmts the-break-statement4090363
Ref: 158a4090363
Ref: reference/simple_stmts grammar-token-break-stmt4090424
Ref: 158b4090424
Node: The continue statement4091018
Ref: reference/simple_stmts continue4091151
Ref: 1824091151
Ref: reference/simple_stmts the-continue-statement4091151
Ref: 158c4091151
Ref: reference/simple_stmts grammar-token-continue-stmt4091220
Ref: 158d4091220
Ref: reference/simple_stmts import4091686
Ref: c224091686
Node: The import statement4091688
Ref: reference/simple_stmts from4091822
Ref: c4a4091822
Ref: reference/simple_stmts the-import-statement4091822
Ref: 158e4091822
Ref: reference/simple_stmts grammar-token-import-stmt4091887
Ref: 158f4091887
Ref: reference/simple_stmts grammar-token-module4092344
Ref: 15904092344
Ref: reference/simple_stmts grammar-token-relative-module4092398
Ref: 15914092398
Node: Future statements4097647
Ref: reference/simple_stmts future4097721
Ref: 15924097721
Ref: reference/simple_stmts future-statements4097721
Ref: 15934097721
Ref: reference/simple_stmts grammar-token-future-stmt4098247
Ref: 15944098247
Ref: reference/simple_stmts grammar-token-feature4098523
Ref: 15954098523
Ref: Future statements-Footnote-14101239
Ref: Future statements-Footnote-24101288
Node: The global statement4101337
Ref: reference/simple_stmts global4101471
Ref: 12494101471
Ref: reference/simple_stmts the-global-statement4101471
Ref: 15964101471
Ref: reference/simple_stmts grammar-token-global-stmt4101536
Ref: 15974101536
Node: The nonlocal statement4103085
Ref: reference/simple_stmts nonlocal4103190
Ref: c444103190
Ref: reference/simple_stmts the-nonlocal-statement4103190
Ref: 15984103190
Ref: reference/simple_stmts grammar-token-nonlocal-stmt4103259
Ref: 15994103259
Ref: The nonlocal statement-Footnote-14104233
Node: Compound statements4104282
Ref: reference/compound_stmts doc4104422
Ref: 159a4104422
Ref: reference/compound_stmts compound4104422
Ref: 159b4104422
Ref: reference/compound_stmts compound-statements4104422
Ref: 159c4104422
Ref: reference/compound_stmts grammar-token-compound-stmt4106192
Ref: 159d4106192
Ref: reference/compound_stmts grammar-token-suite4106549
Ref: 159e4106549
Ref: reference/compound_stmts grammar-token-statement4106625
Ref: 159f4106625
Ref: reference/compound_stmts grammar-token-stmt-list4106682
Ref: 15a04106682
Ref: reference/compound_stmts if4107208
Ref: dec4107208
Ref: reference/compound_stmts elif4107208
Ref: 12384107208
Node: The if statement4107407
Ref: reference/compound_stmts else4107507
Ref: 12394107507
Ref: reference/compound_stmts the-if-statement4107507
Ref: 15a14107507
Ref: reference/compound_stmts grammar-token-if-stmt4107627
Ref: 15a24107627
Node: The while statement4108175
Ref: reference/compound_stmts the-while-statement4108301
Ref: 15a34108301
Ref: reference/compound_stmts while4108301
Ref: 12324108301
Ref: reference/compound_stmts grammar-token-while-stmt4108461
Ref: 15a44108461
Node: The for statement4109061
Ref: reference/compound_stmts for4109188
Ref: c354109188
Ref: reference/compound_stmts the-for-statement4109188
Ref: 15a54109188
Ref: reference/compound_stmts grammar-token-for-stmt4109387
Ref: 15a64109387
Ref: reference/compound_stmts try4112149
Ref: d774112149
Ref: reference/compound_stmts except4112149
Ref: b434112149
Node: The try statement4112150
Ref: reference/compound_stmts finally4112276
Ref: 1834112276
Ref: reference/compound_stmts the-try-statement4112276
Ref: 15a74112276
Ref: reference/compound_stmts grammar-token-try-stmt4112440
Ref: 15a84112440
Ref: reference/compound_stmts grammar-token-try1-stmt4112481
Ref: 15a94112481
Ref: reference/compound_stmts grammar-token-try2-stmt4112667
Ref: 15aa4112667
Ref: reference/compound_stmts with4117928
Ref: 6ee4117928
Ref: The try statement-Footnote-14117964
Node: The with statement4118166
Ref: reference/compound_stmts as4118295
Ref: 15ab4118295
Ref: reference/compound_stmts the-with-statement4118295
Ref: 15ac4118295
Ref: reference/compound_stmts grammar-token-with-stmt4118662
Ref: 15ad4118662
Ref: reference/compound_stmts grammar-token-with-item4118725
Ref: 15ae4118725
Ref: reference/compound_stmts function4121564
Ref: 12614121564
Ref: The with statement-Footnote-14121600
Node: Function definitions4121649
Ref: reference/compound_stmts def4121778
Ref: dc34121778
Ref: reference/compound_stmts function-definitions4121778
Ref: 15af4121778
Ref: reference/compound_stmts grammar-token-funcdef4121951
Ref: 15b04121951
Ref: reference/compound_stmts grammar-token-decorators4122102
Ref: 15b14122102
Ref: reference/compound_stmts grammar-token-decorator4122148
Ref: 15b24122148
Ref: reference/compound_stmts grammar-token-dotted-name4122239
Ref: 15b34122239
Ref: reference/compound_stmts grammar-token-parameter-list4122303
Ref: 15b44122303
Ref: reference/compound_stmts grammar-token-parameter-list-no-posonly4122478
Ref: 15b54122478
Ref: reference/compound_stmts grammar-token-parameter-list-starargs4122639
Ref: 15b64122639
Ref: reference/compound_stmts grammar-token-parameter4122797
Ref: 15b74122797
Ref: reference/compound_stmts grammar-token-defparameter4122860
Ref: 15b84122860
Ref: reference/compound_stmts grammar-token-funcname4122922
Ref: 15b94122922
Ref: Function definitions-Footnote-14128805
Ref: Function definitions-Footnote-24129003
Ref: Function definitions-Footnote-34129052
Ref: Function definitions-Footnote-44129101
Ref: Function definitions-Footnote-54129150
Ref: Function definitions-Footnote-64129199
Node: Class definitions4129248
Ref: reference/compound_stmts class4129372
Ref: c6f4129372
Ref: reference/compound_stmts class-definitions4129372
Ref: 15bb4129372
Ref: reference/compound_stmts grammar-token-classdef4129520
Ref: 15bc4129520
Ref: reference/compound_stmts grammar-token-inheritance4129596
Ref: 15bd4129596
Ref: reference/compound_stmts grammar-token-classname4129641
Ref: 15be4129641
Ref: Class definitions-Footnote-14132353
Ref: Class definitions-Footnote-24132541
Ref: Class definitions-Footnote-34132590
Ref: Class definitions-Footnote-44132639
Node: Coroutines<2>4132688
Ref: reference/compound_stmts async4132783
Ref: 1a34132783
Ref: reference/compound_stmts coroutines4132783
Ref: 15bf4132783
Node: Coroutine function definition4132938
Ref: reference/compound_stmts async-def4133049
Ref: 2854133049
Ref: reference/compound_stmts coroutine-function-definition4133049
Ref: 15c04133049
Ref: reference/compound_stmts grammar-token-async-funcdef4133126
Ref: 15c14133126
Node: The async for statement4133984
Ref: reference/compound_stmts async-for4134128
Ref: 2e44134128
Ref: reference/compound_stmts the-async-for-statement4134128
Ref: 15c24134128
Ref: reference/compound_stmts grammar-token-async-for-stmt4134201
Ref: 15c34134201
Node: The async with statement4135129
Ref: reference/compound_stmts async-with4135235
Ref: 6484135235
Ref: reference/compound_stmts the-async-with-statement4135235
Ref: 15c44135235
Ref: reference/compound_stmts grammar-token-async-with-stmt4135310
Ref: 15c54135310
Ref: The async with statement-Footnote-14136453
Node: Top-level components4136502
Ref: reference/toplevel_components doc4136649
Ref: 15c64136649
Ref: reference/toplevel_components top-level4136649
Ref: 15c74136649
Ref: reference/toplevel_components top-level-components4136649
Ref: 15c84136649
Node: Complete Python programs4137042
Ref: reference/toplevel_components complete-python-programs4137142
Ref: 15c94137142
Ref: reference/toplevel_components programs4137142
Ref: 14cd4137142
Node: File input4138525
Ref: reference/toplevel_components file-input4138651
Ref: 15ca4138651
Ref: reference/toplevel_components id14138651
Ref: 15cb4138651
Ref: reference/toplevel_components grammar-token-file-input4138748
Ref: 15cc4138748
Node: Interactive input4139024
Ref: reference/toplevel_components interactive4139142
Ref: 15cd4139142
Ref: reference/toplevel_components interactive-input4139142
Ref: 15ce4139142
Ref: reference/toplevel_components grammar-token-interactive-input4139257
Ref: 15cf4139257
Node: Expression input4139490
Ref: reference/toplevel_components expression-input4139589
Ref: 15d04139589
Ref: reference/toplevel_components id24139589
Ref: 15d14139589
Ref: reference/toplevel_components grammar-token-eval-input4139791
Ref: 15d24139791
Node: 完整的語法規格書4139837
Ref: reference/grammar doc4139956
Ref: 15d34139956
Ref: reference/grammar full-grammar-specification4139956
Ref: 15d44139956
Node: Python 標準函式庫 Standard Library4150936
Ref: library/index doc4151108
Ref: 15d54151108
Ref: library/index library-index4151108
Ref: 12004151108
Ref: library/index the-python-standard-library4151108
Ref: 15d64151108
Ref: Python 標準函式庫 Standard Library-Footnote-14153444
Node: 簡介<6>4153469
Ref: library/intro doc4153575
Ref: 15d74153575
Ref: library/intro introduction4153575
Ref: 15d84153575
Ref: library/intro library-intro4153575
Ref: 15d94153575
Node: Notes on availability4156226
Ref: library/intro availability4156293
Ref: 13644156293
Ref: library/intro notes-on-availability4156293
Ref: 15da4156293
Node: 內建函式4156674
Ref: library/functions doc4156801
Ref: 15db4156801
Ref: library/functions built-in-funcs4156801
Ref: bf84156801
Ref: library/functions built-in-functions4156801
Ref: 15dc4156801
Ref: library/functions abs4161316
Ref: 12c44161316
Ref: library/functions all4161601
Ref: d8a4161601
Ref: library/functions any4161912
Ref: d894161912
Ref: library/functions ascii4162234
Ref: d514162234
Ref: library/functions bin4162590
Ref: c454162590
Ref: library/functions bool4163248
Ref: 1844163248
Ref: library/functions breakpoint4163832
Ref: 2fe4163832
Ref: library/functions func-bytearray4164658
Ref: 10c34164658
Ref: library/functions func-bytes4166046
Ref: 10c24166046
Ref: library/functions callable4166742
Ref: b494166742
Ref: library/functions chr4167291
Ref: 142d4167291
Ref: library/functions classmethod4167745
Ref: 1d94167745
Ref: library/functions compile4168736
Ref: 1b54168736
Ref: library/functions complex4172935
Ref: 18a4172935
Ref: library/functions delattr4174432
Ref: 15dd4174432
Ref: library/functions func-dict4174799
Ref: 15e04174799
Ref: library/functions dir4175259
Ref: d384175259
Ref: library/functions divmod4177998
Ref: 1534177998
Ref: library/functions enumerate4178637
Ref: de84178637
Ref: library/functions eval4179528
Ref: b954179528
Ref: library/functions exec4181850
Ref: c494181850
Ref: library/functions filter4184453
Ref: c334184453
Ref: library/functions float4185252
Ref: 1884185252
Ref: library/functions grammar-token-sign4185873
Ref: 15f24185873
Ref: library/functions grammar-token-infinity4185912
Ref: 15f34185912
Ref: library/functions grammar-token-nan4185960
Ref: 15f44185960
Ref: library/functions grammar-token-numeric-value4185995
Ref: 15f54185995
Ref: library/functions grammar-token-numeric-string4186053
Ref: 15f64186053
Ref: library/functions format4187528
Ref: 4e04187528
Ref: library/functions func-frozenset4188604
Ref: 15e44188604
Ref: library/functions getattr4189080
Ref: 44d4189080
Ref: library/functions globals4189541
Ref: 15e74189541
Ref: library/functions hasattr4189815
Ref: 44c4189815
Ref: library/functions hash4190152
Ref: 9c94190152
Ref: library/functions help4190738
Ref: 5774190738
Ref: library/functions hex4191779
Ref: c6b4191779
Ref: library/functions id4192843
Ref: d8b4192843
Ref: library/functions input4193293
Ref: c704193293
Ref: library/functions int4194145
Ref: 1854194145
Ref: library/functions isinstance4196183
Ref: 4544196183
Ref: library/functions issubclass4196769
Ref: 4554196769
Ref: library/functions iter4197153
Ref: d2c4197153
Ref: library/functions len4198524
Ref: 1514198524
Ref: library/functions func-list4198755
Ref: 15e54198755
Ref: library/functions locals4198989
Ref: 45a4198989
Ref: library/functions map4199516
Ref: c324199516
Ref: library/functions max4200040
Ref: 80f4200040
Ref: library/functions func-memoryview4201219
Ref: 15de4201219
Ref: library/functions min4201376
Ref: 80e4201376
Ref: library/functions next4202546
Ref: 6874202546
Ref: library/functions object4202812
Ref: 2b14202812
Ref: library/functions oct4203234
Ref: c6a4203234
Ref: library/functions open4203996
Ref: 4f54203996
Ref: library/functions filemodes4205487
Ref: 15fb4205487
Ref: library/functions open-newline-parameter4210655
Ref: 15fd4210655
Ref: library/functions ord4215682
Ref: 142c4215682
Ref: library/functions pow4216002
Ref: 19b4216002
Ref: library/functions print4217609
Ref: 88b4217609
Ref: library/functions property4218784
Ref: 1d84218784
Ref: library/functions func-range4221471
Ref: 15e64221471
Ref: library/functions repr4221734
Ref: 7d14221734
Ref: library/functions reversed4222339
Ref: 18f4222339
Ref: library/functions round4222652
Ref: c724222652
Ref: library/functions func-set4223946
Ref: 15df4223946
Ref: library/functions setattr4224405
Ref: 15e14224405
Ref: library/functions slice4224820
Ref: e094224820
Ref: library/functions sorted4225603
Ref: 4494225603
Ref: library/functions staticmethod4226673
Ref: 1da4226673
Ref: library/functions func-str4227910
Ref: 15e24227910
Ref: library/functions sum4228249
Ref: 1e64228249
Ref: library/functions super4228947
Ref: 4e74228947
Ref: library/functions func-tuple4232671
Ref: 15e34232671
Ref: library/functions type4232900
Ref: 60d4232900
Ref: library/functions vars4234587
Ref: 103c4234587
Ref: library/functions zip4235481
Ref: c374235481
Ref: library/functions __import__4237422
Ref: 6154237422
Ref: 內建函式-Footnote-14240601
Ref: 內建函式-Footnote-24240811
Ref: 內建函式-Footnote-34240860
Ref: 內建函式-Footnote-44240937
Ref: 內建函式-Footnote-54240986
Node: 內建常數4241035
Ref: library/constants doc4241165
Ref: 160e4241165
Ref: library/constants built-in-constants4241165
Ref: 160f4241165
Ref: library/constants built-in-consts4241165
Ref: 16104241165
Ref: library/constants False4241268
Ref: 38d4241268
Ref: library/constants True4241418
Ref: 49e4241418
Ref: library/constants None4241565
Ref: 1584241565
Ref: library/constants NotImplemented4241844
Ref: 8514241844
Ref: library/constants Ellipsis4243181
Ref: 16114243181
Ref: library/constants __debug__4243373
Ref: 10014243373
Node: Constants added by the site module4243841
Ref: library/constants constants-added-by-the-site-module4243924
Ref: 16124243924
Ref: library/constants quit4244292
Ref: 16134244292
Ref: library/constants exit4244319
Ref: 16144244319
Ref: library/constants copyright4244531
Ref: 16154244531
Ref: library/constants credits4244551
Ref: 16164244551
Ref: library/constants license4244672
Ref: 16174244672
Node: 內建型態4244895
Ref: library/stdtypes doc4245028
Ref: 16184245028
Ref: library/stdtypes bltin-types4245028
Ref: 16194245028
Ref: library/stdtypes built-in-types4245028
Ref: 161a4245028
Node: Truth Value Testing4246464
Ref: library/stdtypes truth4246574
Ref: 15e84246574
Ref: library/stdtypes truth-value-testing4246574
Ref: 161b4246574
Ref: Truth Value Testing-Footnote-14247647
Node: Boolean Operations --- and or not4247787
Ref: library/stdtypes boolean4247920
Ref: 161c4247920
Ref: library/stdtypes boolean-operations-and-or-not4247920
Ref: 161d4247920
Node: Comparisons<2>4249253
Ref: library/stdtypes comparisons4249402
Ref: 161e4249402
Ref: library/stdtypes stdcomparisons4249402
Ref: 161f4249402
Node: Numeric Types --- int float complex4251844
Ref: library/stdtypes numeric-types-int-float-complex4251974
Ref: 16204251974
Ref: library/stdtypes typesnumeric4251974
Ref: 12244251974
Ref: Numeric Types --- int float complex-Footnote-14260002
Node: Bitwise Operations on Integer Types4260121
Ref: library/stdtypes bitstring-ops4260272
Ref: 16214260272
Ref: library/stdtypes bitwise-operations-on-integer-types4260272
Ref: 16224260272
Node: Additional Methods on Integer Types4262630
Ref: library/stdtypes additional-methods-on-integer-types4262817
Ref: 16234262817
Ref: library/stdtypes int bit_length4263043
Ref: 16244263043
Ref: library/stdtypes int to_bytes4263962
Ref: 16254263962
Ref: library/stdtypes int from_bytes4265376
Ref: 16274265376
Ref: library/stdtypes int as_integer_ratio4266592
Ref: 1874266592
Node: Additional Methods on Float4266910
Ref: library/stdtypes additional-methods-on-float4267086
Ref: 16284267086
Ref: library/stdtypes float as_integer_ratio4267298
Ref: 13284267298
Ref: library/stdtypes float is_integer4267560
Ref: 16294267560
Ref: library/stdtypes float hex4268193
Ref: 13294268193
Ref: library/stdtypes float fromhex4268449
Ref: 162a4268449
Node: Hashing of numeric types4270095
Ref: library/stdtypes hashing-of-numeric-types4270227
Ref: 162b4270227
Ref: library/stdtypes numeric-hash4270227
Ref: 162c4270227
Node: Iterator Types4274485
Ref: library/stdtypes iterator-types4274636
Ref: 162d4274636
Ref: library/stdtypes typeiter4274636
Ref: 14614274636
Ref: library/stdtypes container __iter__4275018
Ref: 162e4275018
Ref: library/stdtypes iterator __iter__4275758
Ref: 162f4275758
Ref: library/stdtypes iterator __next__4276102
Ref: c694276102
Node: Generator Types4276878
Ref: library/stdtypes generator-types4276944
Ref: 16304276944
Ref: library/stdtypes id34276944
Ref: 16314276944
Node: Sequence Types --- list tuple range4277440
Ref: library/stdtypes sequence-types-list-tuple-range4277582
Ref: 16324277582
Ref: library/stdtypes typesseq4277582
Ref: 12754277582
Node: Common Sequence Operations4278071
Ref: library/stdtypes common-sequence-operations4278202
Ref: 16334278202
Ref: library/stdtypes typesseq-common4278202
Ref: 16344278202
Ref: Common Sequence Operations-Footnote-14286613
Node: Immutable Sequence Types4286696
Ref: library/stdtypes immutable-sequence-types4286858
Ref: 16394286858
Ref: library/stdtypes typesseq-immutable4286858
Ref: 163a4286858
Node: Mutable Sequence Types4287391
Ref: library/stdtypes mutable-sequence-types4287546
Ref: 163b4287546
Ref: library/stdtypes typesseq-mutable4287546
Ref: 15ea4287546
Node: List（串列）<2>4293211
Ref: library/stdtypes lists4293348
Ref: 163c4293348
Ref: library/stdtypes typesseq-list4293348
Ref: 15f94293348
Ref: library/stdtypes list4293549
Ref: 2634293549
Ref: library/stdtypes list sort4294737
Ref: 44a4294737
Node: Tuples4297058
Ref: library/stdtypes tuples4297179
Ref: 163d4297179
Ref: library/stdtypes typesseq-tuple4297179
Ref: 160c4297179
Ref: library/stdtypes tuple4297542
Ref: 4834297542
Node: Ranges4299098
Ref: library/stdtypes ranges4299191
Ref: 163e4299191
Ref: library/stdtypes typesseq-range4299191
Ref: 16044299191
Ref: library/stdtypes range4299380
Ref: 9c34299380
Ref: library/stdtypes range start4301352
Ref: 163f4301352
Ref: library/stdtypes range stop4301479
Ref: 16404301479
Ref: library/stdtypes range step4301547
Ref: 16414301547
Ref: Ranges-Footnote-14303530
Node: Text Sequence Type --- str4303582
Ref: library/stdtypes text-sequence-type-str4303762
Ref: 16424303762
Ref: library/stdtypes textseq4303762
Ref: 12284303762
Ref: library/stdtypes str4305412
Ref: 3354305412
Node: String Methods<2>4307548
Ref: library/stdtypes id54307667
Ref: 16444307667
Ref: library/stdtypes string-methods4307667
Ref: 12294307667
Ref: library/stdtypes str capitalize4308509
Ref: 16474308509
Ref: library/stdtypes str casefold4308867
Ref: 6b54308867
Ref: library/stdtypes str center4309491
Ref: 12a14309491
Ref: library/stdtypes str count4309769
Ref: 16494309769
Ref: library/stdtypes str encode4310011
Ref: c3c4310011
Ref: library/stdtypes str endswith4310747
Ref: 7cc4310747
Ref: library/stdtypes str expandtabs4311088
Ref: 164a4311088
Ref: library/stdtypes str find4312209
Ref: 7a44312209
Ref: library/stdtypes str format4312766
Ref: 4df4312766
Ref: library/stdtypes str format_map4314277
Ref: 6b64314277
Ref: library/stdtypes str index4314792
Ref: 164b4314792
Ref: library/stdtypes str isalnum4314944
Ref: 164c4314944
Ref: library/stdtypes str isalpha4315290
Ref: 164d4315290
Ref: library/stdtypes str isascii4315766
Ref: 3384315766
Ref: library/stdtypes str isdecimal4316010
Ref: 164e4316010
Ref: library/stdtypes str isdigit4316400
Ref: 164f4316400
Ref: library/stdtypes str isidentifier4316914
Ref: 16504316914
Ref: library/stdtypes str islower4317473
Ref: 16524317473
Ref: library/stdtypes str isnumeric4317663
Ref: 16534317663
Ref: library/stdtypes str isprintable4318149
Ref: 6b74318149
Ref: library/stdtypes str isspace4318765
Ref: 16544318765
Ref: library/stdtypes str istitle4319189
Ref: 16554319189
Ref: library/stdtypes str isupper4319476
Ref: 16564319476
Ref: library/stdtypes str join4319666
Ref: 16374319666
Ref: library/stdtypes str ljust4320000
Ref: 12a04320000
Ref: library/stdtypes str lower4320293
Ref: 16484320293
Ref: library/stdtypes str lstrip4320518
Ref: 16574320518
Ref: library/stdtypes str maketrans4321038
Ref: 6b84321038
Ref: library/stdtypes str partition4321773
Ref: 7a74321773
Ref: library/stdtypes str replace4322118
Ref: 16594322118
Ref: library/stdtypes str rfind4322365
Ref: 7a54322365
Ref: library/stdtypes str rindex4322668
Ref: 165a4322668
Ref: library/stdtypes str rjust4322829
Ref: 129f4322829
Ref: library/stdtypes str rpartition4323123
Ref: 165b4323123
Ref: library/stdtypes str rsplit4323468
Ref: 165c4323468
Ref: library/stdtypes str rstrip4323924
Ref: 165d4323924
Ref: library/stdtypes str split4324434
Ref: 7a64324434
Ref: library/stdtypes str splitlines4326099
Ref: 165e4326099
Ref: library/stdtypes str startswith4328732
Ref: 7cb4328732
Ref: library/stdtypes str strip4329075
Ref: 165f4329075
Ref: library/stdtypes str swapcase4330089
Ref: 16604330089
Ref: library/stdtypes str title4330312
Ref: 16614330312
Ref: library/stdtypes str translate4331371
Ref: 16584331371
Ref: library/stdtypes str upper4332283
Ref: 16634332283
Ref: library/stdtypes str zfill4332746
Ref: 12a24332746
Ref: String Methods<2>-Footnote-14333273
Ref: String Methods<2>-Footnote-24333437
Ref: String Methods<2>-Footnote-34333601
Ref: String Methods<2>-Footnote-44333765
Node: printf-style String Formatting4333929
Ref: library/stdtypes old-string-formatting4334048
Ref: 122a4334048
Ref: library/stdtypes printf-style-string-formatting4334048
Ref: 16644334048
Ref: printf-style String Formatting-Footnote-14343248
Ref: printf-style String Formatting-Footnote-24343379
Node: Binary Sequence Types --- bytes bytearray memoryview4343428
Ref: library/stdtypes binary-sequence-types-bytes-bytearray-memoryview4343600
Ref: 16664343600
Ref: library/stdtypes binaryseq4343600
Ref: 15ed4343600
Node: Bytes Objects4344292
Ref: library/stdtypes bytes-objects4344420
Ref: 16674344420
Ref: library/stdtypes typebytes4344420
Ref: 15ef4344420
Ref: library/stdtypes bytes4344760
Ref: 3364344760
Ref: library/stdtypes bytes fromhex4347016
Ref: 3334347016
Ref: library/stdtypes bytes hex4347620
Ref: 6364347620
Node: Bytearray Objects4349814
Ref: library/stdtypes bytearray-objects4349981
Ref: 16684349981
Ref: library/stdtypes typebytearray4349981
Ref: 15ee4349981
Ref: library/stdtypes bytearray4350121
Ref: 3374350121
Ref: library/stdtypes bytearray fromhex4351160
Ref: 3344351160
Ref: library/stdtypes bytearray hex4351793
Ref: 6374351793
Node: Bytes and Bytearray Operations4352839
Ref: library/stdtypes bytes-and-bytearray-operations4353022
Ref: 16694353022
Ref: library/stdtypes bytes-methods4353022
Ref: 15eb4353022
Ref: library/stdtypes bytes count4354244
Ref: 166a4354244
Ref: library/stdtypes bytearray count4354296
Ref: 166b4354296
Ref: library/stdtypes bytes decode4354756
Ref: c3d4354756
Ref: library/stdtypes bytearray decode4354823
Ref: 166c4354823
Ref: library/stdtypes bytes endswith4355708
Ref: 166d4355708
Ref: library/stdtypes bytearray endswith4355766
Ref: 166e4355766
Ref: library/stdtypes bytes find4356199
Ref: 166f4356199
Ref: library/stdtypes bytearray find4356250
Ref: 16704356250
Ref: library/stdtypes bytes index4357055
Ref: 16714357055
Ref: library/stdtypes bytearray index4357107
Ref: 16724357107
Ref: library/stdtypes bytes join4357478
Ref: 16384357478
Ref: library/stdtypes bytearray join4357518
Ref: 16734357518
Ref: library/stdtypes bytes maketrans4357960
Ref: c0e4357960
Ref: library/stdtypes bytearray maketrans4358012
Ref: c0f4358012
Ref: library/stdtypes bytes partition4358382
Ref: 16754358382
Ref: library/stdtypes bytearray partition4358422
Ref: 16764358422
Ref: library/stdtypes bytes replace4358915
Ref: 16774358915
Ref: library/stdtypes bytearray replace4358967
Ref: 16784358967
Ref: library/stdtypes bytes rfind4359495
Ref: 16794359495
Ref: library/stdtypes bytearray rfind4359547
Ref: 167a4359547
Ref: library/stdtypes bytes rindex4360074
Ref: 167b4360074
Ref: library/stdtypes bytearray rindex4360127
Ref: 167c4360127
Ref: library/stdtypes bytes rpartition4360507
Ref: 167d4360507
Ref: library/stdtypes bytearray rpartition4360548
Ref: 167e4360548
Ref: library/stdtypes bytes startswith4361041
Ref: 167f4361041
Ref: library/stdtypes bytearray startswith4361101
Ref: 16804361101
Ref: library/stdtypes bytes translate4361543
Ref: 16744361543
Ref: library/stdtypes bytearray translate4361600
Ref: c964361600
Ref: library/stdtypes bytes center4362613
Ref: 16814362613
Ref: library/stdtypes bytearray center4362664
Ref: 16824362664
Ref: library/stdtypes bytes ljust4363173
Ref: 16834363173
Ref: library/stdtypes bytearray ljust4363223
Ref: 16844363223
Ref: library/stdtypes bytes lstrip4363737
Ref: 16854363737
Ref: library/stdtypes bytearray lstrip4363778
Ref: 16864363778
Ref: library/stdtypes bytes rjust4364687
Ref: 16874364687
Ref: library/stdtypes bytearray rjust4364737
Ref: 16884364737
Ref: library/stdtypes bytes rsplit4365252
Ref: 16894365252
Ref: library/stdtypes bytearray rsplit4365307
Ref: 168a4365307
Ref: library/stdtypes bytes rstrip4365827
Ref: 168c4365827
Ref: library/stdtypes bytearray rstrip4365868
Ref: 168d4365868
Ref: library/stdtypes bytes split4366767
Ref: 168e4366767
Ref: library/stdtypes bytearray split4366821
Ref: 168b4366821
Ref: library/stdtypes bytes strip4368750
Ref: 168f4368750
Ref: library/stdtypes bytearray strip4368790
Ref: 16904368790
Ref: library/stdtypes bytes capitalize4369985
Ref: 16914369985
Ref: library/stdtypes bytearray capitalize4370023
Ref: 16924370023
Ref: library/stdtypes bytes expandtabs4370440
Ref: 16934370440
Ref: library/stdtypes bytearray expandtabs4370487
Ref: 16944370487
Ref: library/stdtypes bytes isalnum4371837
Ref: 16954371837
Ref: library/stdtypes bytearray isalnum4371872
Ref: 16964371872
Ref: library/stdtypes bytes isalpha4372440
Ref: 16974372440
Ref: library/stdtypes bytearray isalpha4372475
Ref: 16984372475
Ref: library/stdtypes bytes isascii4372918
Ref: 16994372918
Ref: library/stdtypes bytearray isascii4372953
Ref: 169a4372953
Ref: library/stdtypes bytes isdigit4373172
Ref: 169b4373172
Ref: library/stdtypes bytearray isdigit4373207
Ref: 169c4373207
Ref: library/stdtypes bytes islower4373585
Ref: 169d4373585
Ref: library/stdtypes bytearray islower4373620
Ref: 169e4373620
Ref: library/stdtypes bytes isspace4374164
Ref: 169f4374164
Ref: library/stdtypes bytearray isspace4374199
Ref: 16a04374199
Ref: library/stdtypes bytes istitle4374537
Ref: 16a14374537
Ref: library/stdtypes bytearray istitle4374572
Ref: 16a24374572
Ref: library/stdtypes bytes isupper4374947
Ref: 16a44374947
Ref: library/stdtypes bytearray isupper4374982
Ref: 16a54374982
Ref: library/stdtypes bytes lower4375542
Ref: 16a64375542
Ref: library/stdtypes bytearray lower4375575
Ref: 16a74375575
Ref: library/stdtypes bytes splitlines4376222
Ref: 16a84376222
Ref: library/stdtypes bytearray splitlines4376274
Ref: 16a94376274
Ref: library/stdtypes bytes swapcase4377229
Ref: 16aa4377229
Ref: library/stdtypes bytearray swapcase4377265
Ref: 16ab4377265
Ref: library/stdtypes bytes title4378203
Ref: 16a34378203
Ref: library/stdtypes bytearray title4378236
Ref: 16ac4378236
Ref: library/stdtypes bytes upper4379869
Ref: 16ad4379869
Ref: library/stdtypes bytearray upper4379902
Ref: 16ae4379902
Ref: library/stdtypes bytes zfill4380549
Ref: 16af4380549
Ref: library/stdtypes bytearray zfill4380587
Ref: 16b04380587
Node: printf-style Bytes Formatting4381305
Ref: library/stdtypes bytes-formatting4381483
Ref: 6554381483
Ref: library/stdtypes printf-style-bytes-formatting4381483
Ref: 16b14381483
Ref: printf-style Bytes Formatting-Footnote-14390973
Ref: printf-style Bytes Formatting-Footnote-24391104
Ref: printf-style Bytes Formatting-Footnote-34391153
Node: Memory Views4391202
Ref: library/stdtypes memory-views4391341
Ref: 16b24391341
Ref: library/stdtypes typememoryview4391341
Ref: 15fa4391341
Ref: library/stdtypes memoryview4391539
Ref: 25d4391539
Ref: library/stdtypes memoryview __eq__4395271
Ref: 16b64395271
Ref: library/stdtypes memoryview tobytes4397260
Ref: 16b74397260
Ref: library/stdtypes memoryview hex4398367
Ref: 6384398367
Ref: library/stdtypes memoryview tolist4398883
Ref: 16b34398883
Ref: library/stdtypes memoryview toreadonly4399442
Ref: 16b84399442
Ref: library/stdtypes memoryview release4400058
Ref: b424400058
Ref: library/stdtypes memoryview cast4401428
Ref: 16b94401428
Ref: library/stdtypes memoryview obj4404442
Ref: 16bb4404442
Ref: library/stdtypes memoryview nbytes4404675
Ref: 16bc4404675
Ref: library/stdtypes memoryview readonly4405796
Ref: 16bd4405796
Ref: library/stdtypes memoryview format4405885
Ref: 16b54405885
Ref: library/stdtypes memoryview itemsize4406411
Ref: 16b44406411
Ref: library/stdtypes memoryview ndim4406784
Ref: 16be4406784
Ref: library/stdtypes memoryview shape4406922
Ref: 16bf4406922
Ref: library/stdtypes memoryview strides4407155
Ref: 16c04407155
Ref: library/stdtypes memoryview suboffsets4407423
Ref: 16c14407423
Ref: library/stdtypes memoryview c_contiguous4407545
Ref: 16c24407545
Ref: library/stdtypes memoryview f_contiguous4407692
Ref: 16c34407692
Ref: library/stdtypes memoryview contiguous4407845
Ref: 16c44407845
Ref: Memory Views-Footnote-14408024
Node: Set Types --- set frozenset4408073
Ref: library/stdtypes set-types-set-frozenset4408241
Ref: 16c54408241
Ref: library/stdtypes types-set4408241
Ref: 15f74408241
Ref: library/stdtypes set4409791
Ref: b744409791
Ref: library/stdtypes frozenset4409820
Ref: bf34409820
Ref: library/stdtypes frozenset isdisjoint4410857
Ref: 16c64410857
Ref: library/stdtypes frozenset issubset4411071
Ref: 16c74411071
Ref: library/stdtypes frozenset issuperset4411368
Ref: 16c84411368
Ref: library/stdtypes frozenset union4411669
Ref: 16c94411669
Ref: library/stdtypes frozenset intersection4411822
Ref: 16ca4411822
Ref: library/stdtypes frozenset difference4411997
Ref: 16cb4411997
Ref: library/stdtypes frozenset symmetric_difference4412175
Ref: 16cc4412175
Ref: library/stdtypes frozenset copy4412359
Ref: 16cd4412359
Ref: library/stdtypes frozenset update4414606
Ref: 16ce4414606
Ref: library/stdtypes frozenset intersection_update4414750
Ref: 16cf4414750
Ref: library/stdtypes frozenset difference_update4414934
Ref: 16d04414934
Ref: library/stdtypes frozenset symmetric_difference_update4415091
Ref: 16d14415091
Ref: library/stdtypes frozenset add4415285
Ref: 16d24415285
Ref: library/stdtypes frozenset remove4415362
Ref: 16d34415362
Ref: library/stdtypes frozenset discard4415525
Ref: 16d44415525
Ref: library/stdtypes frozenset pop4415628
Ref: 16d54415628
Ref: library/stdtypes frozenset clear4415783
Ref: 16d64415783
Node: Mapping Types --- dict4416349
Ref: library/stdtypes mapping-types-dict4416486
Ref: 16d74416486
Ref: library/stdtypes typesmapping4416486
Ref: 3014416486
Ref: library/stdtypes dict4417719
Ref: 1b94417719
Ref: library/stdtypes dict clear4422038
Ref: 16d84422038
Ref: library/stdtypes dict copy4422120
Ref: 44b4422120
Ref: library/stdtypes dict fromkeys4422204
Ref: 16d94422204
Ref: library/stdtypes dict get4422752
Ref: 16da4422752
Ref: library/stdtypes dict items4423013
Ref: c304423013
Ref: library/stdtypes dict keys4423193
Ref: c2f4423193
Ref: library/stdtypes dict pop4423344
Ref: 16dc4423344
Ref: library/stdtypes dict popitem4423603
Ref: 16dd4423603
Ref: library/stdtypes dict setdefault4424371
Ref: 9c44424371
Ref: library/stdtypes dict update4424607
Ref: dce4424607
Ref: library/stdtypes dict values4425097
Ref: c314425097
Node: Dictionary view objects4427185
Ref: library/stdtypes dict-views4427267
Ref: 16db4427267
Ref: library/stdtypes dictionary-view-objects4427267
Ref: 16de4427267
Node: Context Manager Types4430146
Ref: library/stdtypes context-manager-types4430276
Ref: 16e04430276
Ref: library/stdtypes typecontextmanager4430276
Ref: 148d4430276
Ref: library/stdtypes contextmanager __enter__4430641
Ref: 16e14430641
Ref: library/stdtypes contextmanager __exit__4431646
Ref: 16e34431646
Node: Other Built-in Types4434038
Ref: library/stdtypes other-built-in-types4434164
Ref: 16e44434164
Ref: library/stdtypes typesother4434164
Ref: 16e54434164
Node: Modules4434558
Ref: library/stdtypes modules4434658
Ref: 16e64434658
Ref: library/stdtypes typesmodules4434658
Ref: 16e74434658
Node: Classes and Class Instances4435811
Ref: library/stdtypes classes-and-class-instances4435929
Ref: 16e84435929
Ref: library/stdtypes typesobjects4435929
Ref: 16e94435929
Node: Functions4436093
Ref: library/stdtypes functions4436211
Ref: 16ea4436211
Ref: library/stdtypes typesfunctions4436211
Ref: 16eb4436211
Node: Methods4436675
Ref: library/stdtypes methods4436778
Ref: 16ec4436778
Ref: library/stdtypes typesmethods4436778
Ref: 16ed4436778
Node: Code Objects4438549
Ref: library/stdtypes bltin-code-objects4438655
Ref: 16ee4438655
Ref: library/stdtypes code-objects4438655
Ref: 16ef4438655
Node: Type Objects4439492
Ref: library/stdtypes bltin-type-objects4439606
Ref: 160d4439606
Ref: library/stdtypes type-objects4439606
Ref: 16f04439606
Node: The Null Object4439957
Ref: library/stdtypes bltin-null-object4440078
Ref: 16f14440078
Ref: library/stdtypes the-null-object4440078
Ref: 16f24440078
Node: The Ellipsis Object4440393
Ref: library/stdtypes bltin-ellipsis-object4440527
Ref: 16f34440527
Ref: library/stdtypes the-ellipsis-object4440527
Ref: 16f44440527
Node: The NotImplemented Object4440895
Ref: library/stdtypes bltin-notimplemented-object4441028
Ref: 16f54441028
Ref: library/stdtypes the-notimplemented-object4441028
Ref: 16f64441028
Node: Boolean Values4441431
Ref: library/stdtypes bltin-boolean-values4441561
Ref: 15e94441561
Ref: library/stdtypes boolean-values4441561
Ref: 16f74441561
Node: Internal Objects4442184
Ref: library/stdtypes internal-objects4442280
Ref: 16f84442280
Ref: library/stdtypes typesinternal4442280
Ref: 16f94442280
Node: Special Attributes4442476
Ref: library/stdtypes special-attributes4442572
Ref: 16fa4442572
Ref: library/stdtypes specialattrs4442572
Ref: 16fb4442572
Ref: library/stdtypes object __dict__4442811
Ref: 5014442811
Ref: library/stdtypes instance __class__4442939
Ref: e0f4442939
Ref: library/stdtypes class __bases__4443022
Ref: e0e4443022
Ref: library/stdtypes definition __name__4443102
Ref: c6c4443102
Ref: library/stdtypes definition __qualname__4443222
Ref: 142f4443222
Ref: library/stdtypes class __mro__4443393
Ref: 160a4443393
Ref: library/stdtypes class mro4443544
Ref: 16fc4443544
Ref: library/stdtypes class __subclasses__4443784
Ref: 16fd4443784
Node: 內建的例外4444066
Ref: library/exceptions doc4444211
Ref: 16fe4444211
Ref: library/exceptions bltin-exceptions4444211
Ref: 12b34444211
Ref: library/exceptions built-in-exceptions4444211
Ref: 16ff4444211
Node: Base classes4447478
Ref: library/exceptions base-classes4447570
Ref: 17004447570
Ref: library/exceptions BaseException4447689
Ref: 1a94447689
Ref: library/exceptions BaseException args4448071
Ref: 17014448071
Ref: library/exceptions BaseException with_traceback4448436
Ref: 17024448436
Ref: library/exceptions Exception4448851
Ref: 1aa4448851
Ref: library/exceptions ArithmeticError4449032
Ref: 17034449032
Ref: library/exceptions BufferError4449258
Ref: 17054449258
Ref: library/exceptions LookupError4449367
Ref: 16624449367
Node: Concrete exceptions4449630
Ref: library/exceptions concrete-exceptions4449739
Ref: 17074449739
Ref: library/exceptions AssertionError4449862
Ref: 10334449862
Ref: library/exceptions AttributeError4449947
Ref: 3a04449947
Ref: library/exceptions EOFError4450214
Ref: c714450214
Ref: library/exceptions FloatingPointError4450488
Ref: 17044450488
Ref: library/exceptions GeneratorExit4450546
Ref: d374450546
Ref: library/exceptions ImportError4450865
Ref: 3394450865
Ref: library/exceptions ModuleNotFoundError4451424
Ref: 39f4451424
Ref: library/exceptions IndexError4451680
Ref: e7a4451680
Ref: library/exceptions KeyError4451904
Ref: 2c84451904
Ref: library/exceptions KeyboardInterrupt4452018
Ref: 1984452018
Ref: library/exceptions MemoryError4452405
Ref: ef14452405
Ref: library/exceptions NameError4452983
Ref: d804452983
Ref: library/exceptions NotImplementedError4453202
Ref: 6134453202
Ref: library/exceptions OSError4454047
Ref: 1d44454047
Ref: library/exceptions OSError errno4455060
Ref: 170a4455060
Ref: library/exceptions OSError winerror4455149
Ref: 170b4455149
Ref: library/exceptions OSError strerror4455725
Ref: 170c4455725
Ref: library/exceptions OSError filename4455958
Ref: 170d4455958
Ref: library/exceptions OSError filename24455984
Ref: 170e4455984
Ref: library/exceptions OverflowError4456941
Ref: 9654456941
Ref: library/exceptions RecursionError4457430
Ref: 6394457430
Ref: library/exceptions ReferenceError4457747
Ref: e524457747
Ref: library/exceptions RuntimeError4458070
Ref: 2bb4458070
Ref: library/exceptions StopIteration4458269
Ref: 48b4458269
Ref: library/exceptions StopAsyncIteration4459570
Ref: 10174459570
Ref: library/exceptions SyntaxError4459757
Ref: 45d4459757
Ref: library/exceptions SyntaxError filename4460148
Ref: 170f4460148
Ref: library/exceptions SyntaxError lineno4460237
Ref: 17104460237
Ref: library/exceptions SyntaxError offset4460408
Ref: 17114460408
Ref: library/exceptions SyntaxError text4460591
Ref: 17124460591
Ref: library/exceptions IndentationError4460669
Ref: e7d4460669
Ref: library/exceptions TabError4460819
Ref: e7c4460819
Ref: library/exceptions SystemError4460977
Ref: 6004460977
Ref: library/exceptions SystemExit4461617
Ref: 6014461617
Ref: library/exceptions SystemExit code4462910
Ref: 17144462910
Ref: library/exceptions TypeError4463049
Ref: 1934463049
Ref: library/exceptions UnboundLocalError4463875
Ref: e7b4463875
Ref: library/exceptions UnicodeError4464090
Ref: c404464090
Ref: library/exceptions UnicodeError encoding4464448
Ref: 17154464448
Ref: library/exceptions UnicodeError reason4464534
Ref: 17164464534
Ref: library/exceptions UnicodeError object4464616
Ref: 17174464616
Ref: library/exceptions UnicodeError start4464709
Ref: 17184464709
Ref: library/exceptions UnicodeError end4464798
Ref: 17194464798
Ref: library/exceptions UnicodeEncodeError4464891
Ref: 1fd4464891
Ref: library/exceptions UnicodeDecodeError4465040
Ref: 1fe4465040
Ref: library/exceptions UnicodeTranslateError4465189
Ref: 171a4465189
Ref: library/exceptions ValueError4465344
Ref: 1fc4465344
Ref: library/exceptions ZeroDivisionError4465593
Ref: 12b24465593
Ref: library/exceptions EnvironmentError4465947
Ref: 9984465947
Ref: library/exceptions IOError4465977
Ref: 9974465977
Ref: library/exceptions WindowsError4465998
Ref: 9994465998
Ref: Concrete exceptions-Footnote-14466121
Ref: Concrete exceptions-Footnote-24466170
Node: OS exceptions4466219
Ref: library/exceptions os-exceptions4466288
Ref: 17094466288
Ref: library/exceptions BlockingIOError4466449
Ref: 99c4466449
Ref: library/exceptions BlockingIOError characters_written4466802
Ref: 171b4466802
Ref: library/exceptions ChildProcessError4467054
Ref: 99d4467054
Ref: library/exceptions ConnectionError4467190
Ref: 6eb4467190
Ref: library/exceptions BrokenPipeError4467435
Ref: 9a24467435
Ref: library/exceptions ConnectionAbortedError4467731
Ref: 9a34467731
Ref: library/exceptions ConnectionRefusedError4467930
Ref: 9a44467930
Ref: library/exceptions ConnectionResetError4468129
Ref: 9a54468129
Ref: library/exceptions FileExistsError4468309
Ref: 95d4468309
Ref: library/exceptions FileNotFoundError4468462
Ref: 7c54468462
Ref: library/exceptions InterruptedError4468611
Ref: 65e4468611
Ref: library/exceptions IsADirectoryError4469005
Ref: 99e4469005
Ref: library/exceptions NotADirectoryError4469181
Ref: 99f4469181
Ref: library/exceptions PermissionError4469392
Ref: 6044469392
Ref: library/exceptions ProcessLookupError4469607
Ref: 9a04469607
Ref: library/exceptions TimeoutError4469736
Ref: 9a14469736
Ref: OS exceptions-Footnote-14470067
Ref: OS exceptions-Footnote-24470116
Node: Warnings4470165
Ref: library/exceptions warning-categories-as-exceptions4470281
Ref: 171c4470281
Ref: library/exceptions warnings4470281
Ref: 171d4470281
Ref: library/exceptions Warning4470442
Ref: 171f4470442
Ref: library/exceptions UserWarning4470504
Ref: 17204470504
Ref: library/exceptions DeprecationWarning4470583
Ref: 2794470583
Ref: library/exceptions PendingDeprecationWarning4470738
Ref: 27a4470738
Ref: library/exceptions SyntaxWarning4471129
Ref: 1924471129
Ref: library/exceptions RuntimeWarning4471208
Ref: 2c14471208
Ref: library/exceptions FutureWarning4471298
Ref: 32a4471298
Ref: library/exceptions ImportWarning4471482
Ref: 5dd4471482
Ref: library/exceptions UnicodeWarning4471582
Ref: d8c4471582
Ref: library/exceptions BytesWarning4471660
Ref: 4ba4471660
Ref: library/exceptions ResourceWarning4471776
Ref: 4d54471776
Node: Exception hierarchy4471932
Ref: library/exceptions exception-hierarchy4472020
Ref: 17214472020
Ref: library/text stringservices4474264
Ref: 16434474264
Node: Text Processing Services4474265
Ref: library/text doc4474418
Ref: 17224474418
Ref: library/text text-processing-services4474418
Ref: 17234474418
Ref: library/text textservices4474418
Ref: 16464474418
Node: string --- Common string operations4475492
Ref: library/string doc4475633
Ref: 17254475633
Ref: library/string module-string4475633
Ref: f74475633
Ref: library/string string-common-string-operations4475633
Ref: 17264475633
Ref: string --- Common string operations-Footnote-14476076
Node: String constants4476141
Ref: library/string string-constants4476262
Ref: 17274476262
Ref: library/string string ascii_letters4476356
Ref: c614476356
Ref: library/string string ascii_lowercase4476555
Ref: 17284476555
Ref: library/string string ascii_uppercase4476715
Ref: 17294476715
Ref: library/string string digits4476875
Ref: 172a4476875
Ref: library/string string hexdigits4476937
Ref: 172b4476937
Ref: library/string string octdigits4477014
Ref: 172c4477014
Ref: library/string string punctuation4477077
Ref: 172d4477077
Ref: library/string string printable4477252
Ref: 172e4477252
Ref: library/string string whitespace4477480
Ref: 172f4477480
Node: Custom String Formatting4477686
Ref: library/string custom-string-formatting4477836
Ref: 17304477836
Ref: library/string string-formatting4477836
Ref: 16454477836
Ref: library/string string Formatter4478283
Ref: 7ba4478283
Ref: library/string string Formatter format4478385
Ref: 4914478385
Ref: library/string string Formatter vformat4478743
Ref: 17314478743
Ref: library/string string Formatter parse4479460
Ref: 17324479460
Ref: library/string string Formatter get_field4480222
Ref: 17334480222
Ref: library/string string Formatter get_value4480769
Ref: 17344480769
Ref: library/string string Formatter check_unused_args4482011
Ref: 17354482011
Ref: library/string string Formatter format_field4482621
Ref: 17364482621
Ref: library/string string Formatter convert_field4482853
Ref: 17374482853
Ref: Custom String Formatting-Footnote-14483234
Ref: Custom String Formatting-Footnote-24483283
Node: Format String Syntax4483332
Ref: library/string format-string-syntax4483482
Ref: 17384483482
Ref: library/string formatstrings4483482
Ref: d1f4483482
Ref: library/string grammar-token-replacement-field4484279
Ref: 17394484279
Ref: library/string grammar-token-field-name4484367
Ref: 173a4484367
Ref: library/string grammar-token-arg-name4484454
Ref: 173b4484454
Ref: library/string grammar-token-attribute-name4484508
Ref: 173c4484508
Ref: library/string grammar-token-element-index4484551
Ref: 173d4484551
Ref: library/string grammar-token-index-string4484605
Ref: 173e4484605
Ref: library/string grammar-token-conversion4484673
Ref: 173f4484673
Ref: library/string grammar-token-format-spec4484721
Ref: 17404484721
Node: Format Specification Mini-Language4488699
Ref: library/string format-specification-mini-language4488814
Ref: 17424488814
Ref: library/string formatspec4488814
Ref: 4e34488814
Ref: library/string id14489707
Ref: 17434489707
Ref: library/string grammar-token-fill4489800
Ref: 17444489800
Ref: library/string grammar-token-align4489841
Ref: 17454489841
Ref: library/string grammar-token-sign4489888
Ref: 17464489888
Ref: library/string grammar-token-width4489929
Ref: 17474489929
Ref: library/string grammar-token-grouping-option4489961
Ref: 17484489961
Ref: library/string grammar-token-precision4489996
Ref: 17494489996
Ref: library/string grammar-token-type4490028
Ref: 174a4490028
Ref: Format Specification Mini-Language-Footnote-14502749
Ref: Format Specification Mini-Language-Footnote-24502798
Node: Format examples4502847
Ref: library/string format-examples4502962
Ref: 174b4502962
Ref: library/string formatexamples4502962
Ref: 17414502962
Node: Template strings4507490
Ref: library/string id24507632
Ref: 174c4507632
Ref: library/string template-strings4507632
Ref: 16654507632
Ref: library/string string Template4509093
Ref: 3f04509093
Ref: library/string string Template substitute4509214
Ref: 13044509214
Ref: library/string string Template safe_substitute4509705
Ref: 13054509705
Ref: library/string string Template template4510744
Ref: 174d4510744
Ref: Template strings-Footnote-14514506
Ref: Template strings-Footnote-24514555
Node: Helper functions4514606
Ref: library/string helper-functions4514719
Ref: 174e4514719
Ref: library/string string capwords4514770
Ref: 174f4514770
Node: re --- Regular expression operations4515254
Ref: library/re doc4515444
Ref: 17504515444
Ref: library/re module-re4515444
Ref: de4515444
Ref: library/re re-regular-expression-operations4515444
Ref: 17514515444
Ref: re --- Regular expression operations-Footnote-14518017
Ref: re --- Regular expression operations-Footnote-24518078
Node: Regular Expression Syntax4518118
Ref: library/re re-syntax4518240
Ref: 17524518240
Ref: library/re regular-expression-syntax4518240
Ref: 17534518240
Ref: Regular Expression Syntax-Footnote-14541783
Node: Module Contents4541825
Ref: library/re contents-of-module-re4541982
Ref: 175e4541982
Ref: library/re module-contents4541982
Ref: 175f4541982
Ref: library/re re compile4542388
Ref: 44f4542388
Ref: library/re re A4543516
Ref: 17584543516
Ref: library/re re ASCII4543531
Ref: 3cd4543531
Ref: library/re re DEBUG4544160
Ref: 17634544160
Ref: library/re re I4544275
Ref: 17594544275
Ref: library/re re IGNORECASE4544290
Ref: 17644544290
Ref: library/re re L4545279
Ref: 175a4545279
Ref: library/re re LOCALE4545294
Ref: 3ce4545294
Ref: library/re re M4546213
Ref: 175b4546213
Ref: library/re re MULTILINE4546228
Ref: 17574546228
Ref: library/re re S4546813
Ref: 175c4546813
Ref: library/re re DOTALL4546828
Ref: 17564546828
Ref: library/re re X4547064
Ref: 175d4547064
Ref: library/re re VERBOSE4547079
Ref: 17654547079
Ref: library/re re search4548095
Ref: bb74548095
Ref: library/re re match4548497
Ref: bb84548497
Ref: library/re re fullmatch4549146
Ref: 8a04549146
Ref: library/re re split4549471
Ref: 3cf4549471
Ref: library/re re findall4551320
Ref: 9684551320
Ref: library/re re finditer4551852
Ref: 17674551852
Ref: library/re re sub4552279
Ref: 4804552279
Ref: library/re re subn4555408
Ref: 7394555408
Ref: library/re re escape4555719
Ref: 49a4555719
Ref: library/re re purge4557185
Ref: 17684557185
Ref: library/re re error4557252
Ref: 73a4557252
Ref: library/re re error msg4557682
Ref: 73b4557682
Ref: library/re re error pattern4557746
Ref: 73c4557746
Ref: library/re re error pos4557815
Ref: 73d4557815
Ref: library/re re error lineno4557927
Ref: 73e4557927
Ref: library/re re error colno4558016
Ref: 73f4558016
Node: Regular Expression Objects4558156
Ref: library/re re-objects4558301
Ref: 8a14558301
Ref: library/re regular-expression-objects4558301
Ref: 17694558301
Ref: library/re re Pattern search4558455
Ref: 17624558455
Ref: library/re re Pattern match4559925
Ref: 17614559925
Ref: library/re re Pattern fullmatch4560790
Ref: 176a4560790
Ref: library/re re Pattern split4561591
Ref: 176b4561591
Ref: library/re re Pattern findall4561731
Ref: 176c4561731
Ref: library/re re Pattern finditer4561998
Ref: 176d4561998
Ref: library/re re Pattern sub4562268
Ref: 176e4562268
Ref: library/re re Pattern subn4562407
Ref: 176f4562407
Ref: library/re re Pattern flags4562548
Ref: 17704562548
Ref: library/re re Pattern groups4562812
Ref: 17714562812
Ref: library/re re Pattern groupindex4562893
Ref: 17724562893
Ref: library/re re Pattern pattern4563104
Ref: 17734563104
Node: Match Objects4563351
Ref: library/re id24563508
Ref: 17744563508
Ref: library/re match-objects4563508
Ref: 8a24563508
Ref: library/re re Match expand4563921
Ref: 17754563921
Ref: library/re re Match group4564435
Ref: 17764564435
Ref: library/re re Match __getitem__4566709
Ref: 17774566709
Ref: library/re re Match groups4567188
Ref: 17784567188
Ref: library/re re Match groupdict4568040
Ref: 17794568040
Ref: library/re re Match start4568513
Ref: 177a4568513
Ref: library/re re Match end4568553
Ref: 177b4568553
Ref: library/re re Match span4569606
Ref: 177c4569606
Ref: library/re re Match pos4569865
Ref: 177d4569865
Ref: library/re re Match endpos4570122
Ref: 177e4570122
Ref: library/re re Match lastindex4570373
Ref: 177f4570373
Ref: library/re re Match lastgroup4570769
Ref: 17804570769
Ref: library/re re Match re4570939
Ref: 17814570939
Ref: library/re re Match string4571103
Ref: 17824571103
Node: Regular Expression Examples4571329
Ref: library/re re-examples4571451
Ref: bf94571451
Ref: library/re regular-expression-examples4571451
Ref: 17834571451
Node: Checking for a Pair4571795
Ref: library/re checking-for-a-pair4571903
Ref: 17844571903
Node: Simulating scanf4573972
Ref: library/re simulating-scanf4574104
Ref: 17854574104
Node: search vs match4576172
Ref: library/re id34576303
Ref: 17864576303
Ref: library/re search-vs-match4576303
Ref: 17664576303
Node: Making a Phonebook4577517
Ref: library/re making-a-phonebook4577644
Ref: 17874577644
Node: Text Munging4579823
Ref: library/re text-munging4579954
Ref: 17884579954
Node: Finding all Adverbs4580774
Ref: library/re finding-all-adverbs4580926
Ref: 17894580926
Node: Finding all Adverbs and their Positions4581381
Ref: library/re finding-all-adverbs-and-their-positions4581540
Ref: 178a4581540
Node: Raw String Notation4582242
Ref: library/re raw-string-notation4582401
Ref: 178b4582401
Node: Writing a Tokenizer4583328
Ref: library/re writing-a-tokenizer4583439
Ref: 178c4583439
Ref: library/re frie094586810
Ref: 17544586810
Ref: Writing a Tokenizer-Footnote-14587090
Node: difflib --- Helpers for computing deltas4587145
Ref: library/difflib doc4587338
Ref: 178d4587338
Ref: library/difflib difflib-helpers-for-computing-deltas4587338
Ref: 178e4587338
Ref: library/difflib module-difflib4587338
Ref: 374587338
Ref: library/difflib difflib Differ4589815
Ref: 178f4589815
Ref: library/difflib difflib HtmlDiff4590943
Ref: 17904590943
Ref: library/difflib difflib HtmlDiff __init__4591314
Ref: 17914591314
Ref: library/difflib difflib HtmlDiff make_file4592133
Ref: 6ce4592133
Ref: library/difflib difflib HtmlDiff make_table4593807
Ref: 17934593807
Ref: library/difflib difflib context_diff4594395
Ref: 17944594395
Ref: library/difflib difflib get_close_matches4596335
Ref: 17984596335
Ref: library/difflib difflib ndiff4597493
Ref: 17924597493
Ref: library/difflib difflib restore4599141
Ref: 179b4599141
Ref: library/difflib difflib unified_diff4599882
Ref: 179d4599882
Ref: library/difflib difflib diff_bytes4601799
Ref: 6cf4601799
Ref: library/difflib difflib IS_LINE_JUNK4602687
Ref: 17994602687
Ref: library/difflib difflib IS_CHARACTER_JUNK4602987
Ref: 179a4602987
Ref: difflib --- Helpers for computing deltas-Footnote-14603644
Ref: difflib --- Helpers for computing deltas-Footnote-24603710
Ref: difflib --- Helpers for computing deltas-Footnote-34603799
Node: SequenceMatcher Objects4603831
Ref: library/difflib sequence-matcher4603964
Ref: 179e4603964
Ref: library/difflib sequencematcher-objects4603964
Ref: 179f4603964
Ref: library/difflib difflib SequenceMatcher4604090
Ref: 9544604090
Ref: library/difflib difflib SequenceMatcher set_seqs4605607
Ref: 17a04605607
Ref: library/difflib difflib SequenceMatcher set_seq14606031
Ref: 17a24606031
Ref: library/difflib difflib SequenceMatcher set_seq24606180
Ref: 17a14606180
Ref: library/difflib difflib SequenceMatcher find_longest_match4606329
Ref: 17a34606329
Ref: library/difflib difflib SequenceMatcher get_matching_blocks4608418
Ref: 17a44608418
Ref: library/difflib difflib SequenceMatcher get_opcodes4609341
Ref: 17a54609341
Ref: library/difflib difflib SequenceMatcher get_grouped_opcodes4611334
Ref: 17a64611334
Ref: library/difflib difflib SequenceMatcher ratio4611772
Ref: 17a74611772
Ref: library/difflib difflib SequenceMatcher quick_ratio4612803
Ref: 17a84612803
Ref: library/difflib difflib SequenceMatcher real_quick_ratio4612929
Ref: 17a94612929
Node: SequenceMatcher Examples4613446
Ref: library/difflib id14613602
Ref: 17aa4613602
Ref: library/difflib sequencematcher-examples4613602
Ref: 17ab4613602
Ref: SequenceMatcher Examples-Footnote-14615302
Node: Differ Objects4615355
Ref: library/difflib differ-objects4615502
Ref: 17ac4615502
Ref: library/difflib id24615502
Ref: 17ad4615502
Ref: library/difflib difflib Differ compare4616909
Ref: 179c4616909
Node: Differ Example4617439
Ref: library/difflib differ-example4617597
Ref: 17ae4617597
Ref: library/difflib differ-examples4617597
Ref: 17af4617597
Node: A command-line interface to difflib4619852
Ref: library/difflib a-command-line-interface-to-difflib4619987
Ref: 17b04619987
Ref: library/difflib difflib-interface4619987
Ref: 17974619987
Node: textwrap --- Text wrapping and filling4622742
Ref: library/textwrap doc4622931
Ref: 17b14622931
Ref: library/textwrap module-textwrap4622931
Ref: 1094622931
Ref: library/textwrap textwrap-text-wrapping-and-filling4622931
Ref: 17b24622931
Ref: library/textwrap textwrap wrap4623463
Ref: 17b34623463
Ref: library/textwrap textwrap fill4623962
Ref: 17b54623962
Ref: library/textwrap textwrap shorten4624320
Ref: 8f24624320
Ref: library/textwrap textwrap dedent4625451
Ref: 17ba4625451
Ref: library/textwrap textwrap indent4626385
Ref: aad4626385
Ref: library/textwrap textwrap TextWrapper4627717
Ref: 8ef4627717
Ref: library/textwrap textwrap TextWrapper width4628394
Ref: 17bc4628394
Ref: library/textwrap textwrap TextWrapper expand_tabs4628713
Ref: 17b74628713
Ref: library/textwrap textwrap TextWrapper tabsize4628913
Ref: 17b64628913
Ref: library/textwrap textwrap TextWrapper replace_whitespace4629196
Ref: 17b94629196
Ref: library/textwrap textwrap TextWrapper drop_whitespace4630160
Ref: 17b84630160
Ref: library/textwrap textwrap TextWrapper initial_indent4630571
Ref: 17bd4630571
Ref: library/textwrap textwrap TextWrapper subsequent_indent4630803
Ref: 17be4630803
Ref: library/textwrap textwrap TextWrapper fix_sentence_endings4631027
Ref: 17bf4631027
Ref: library/textwrap textwrap TextWrapper break_long_words4632235
Ref: 17bb4632235
Ref: library/textwrap textwrap TextWrapper break_on_hyphens4632722
Ref: 17c04632722
Ref: library/textwrap textwrap TextWrapper max_lines4633251
Ref: 8f04633251
Ref: library/textwrap textwrap TextWrapper placeholder4633491
Ref: 8f14633491
Ref: library/textwrap textwrap TextWrapper wrap4633800
Ref: 17b44633800
Ref: library/textwrap textwrap TextWrapper fill4634228
Ref: 17c14634228
Ref: textwrap --- Text wrapping and filling-Footnote-14634421
Node: unicodedata --- Unicode Database4634488
Ref: library/unicodedata doc4634679
Ref: 17c24634679
Ref: library/unicodedata module-unicodedata4634679
Ref: 11b4634679
Ref: library/unicodedata unicodedata-unicode-database4634679
Ref: 17c34634679
Ref: library/unicodedata unicodedata lookup4635201
Ref: 9c24635201
Ref: library/unicodedata unicodedata name4635507
Ref: 17c44635507
Ref: library/unicodedata unicodedata decimal4635731
Ref: 17c54635731
Ref: library/unicodedata unicodedata digit4635972
Ref: 17c64635972
Ref: library/unicodedata unicodedata numeric4636208
Ref: bfe4636208
Ref: library/unicodedata unicodedata category4636446
Ref: 17c74636446
Ref: library/unicodedata unicodedata bidirectional4636569
Ref: 17c84636569
Ref: library/unicodedata unicodedata combining4636759
Ref: 17c94636759
Ref: library/unicodedata unicodedata east_asian_width4636944
Ref: 17ca4636944
Ref: library/unicodedata unicodedata mirrored4637075
Ref: 17cb4637075
Ref: library/unicodedata unicodedata decomposition4637327
Ref: 17cc4637327
Ref: library/unicodedata unicodedata normalize4637540
Ref: 10b44637540
Ref: library/unicodedata unicodedata is_normalized4639400
Ref: 2474639400
Ref: library/unicodedata unicodedata unidata_version4639703
Ref: 17cd4639703
Ref: library/unicodedata unicodedata ucd_3_2_04639805
Ref: da14639805
Ref: unicodedata --- Unicode Database-Footnote-14640597
Ref: unicodedata --- Unicode Database-Footnote-24640646
Ref: unicodedata --- Unicode Database-Footnote-34640692
Ref: unicodedata --- Unicode Database-Footnote-44640767
Node: stringprep --- Internet String Preparation4640845
Ref: library/stringprep doc4641033
Ref: 17ce4641033
Ref: library/stringprep module-stringprep4641033
Ref: f84641033
Ref: library/stringprep stringprep-internet-string-preparation4641033
Ref: 17cf4641033
Ref: library/stringprep stringprep in_table_a14642939
Ref: 17d04642939
Ref: library/stringprep stringprep in_table_b14643074
Ref: 17d14643074
Ref: library/stringprep stringprep map_table_b24643198
Ref: 17d24643198
Ref: library/stringprep stringprep map_table_b34643353
Ref: 17d34643353
Ref: library/stringprep stringprep in_table_c114643520
Ref: 17d44643520
Ref: library/stringprep stringprep in_table_c124643638
Ref: 17d54643638
Ref: library/stringprep stringprep in_table_c11_c124643765
Ref: 17d64643765
Ref: library/stringprep stringprep in_table_c214643910
Ref: 17d74643910
Ref: library/stringprep stringprep in_table_c224644035
Ref: 17d84644035
Ref: library/stringprep stringprep in_table_c21_c224644164
Ref: 17d94644164
Ref: library/stringprep stringprep in_table_c34644311
Ref: 17da4644311
Ref: library/stringprep stringprep in_table_c44644415
Ref: 17db4644415
Ref: library/stringprep stringprep in_table_c54644538
Ref: 17dc4644538
Ref: library/stringprep stringprep in_table_c64644646
Ref: 17dd4644646
Ref: library/stringprep stringprep in_table_c74644772
Ref: 17de4644772
Ref: library/stringprep stringprep in_table_c84644912
Ref: 17df4644912
Ref: library/stringprep stringprep in_table_c94645053
Ref: 17e04645053
Ref: library/stringprep stringprep in_table_d14645164
Ref: 17e14645164
Ref: library/stringprep stringprep in_table_d24645312
Ref: 17e24645312
Ref: stringprep --- Internet String Preparation-Footnote-14645488
Ref: stringprep --- Internet String Preparation-Footnote-24645557
Ref: stringprep --- Internet String Preparation-Footnote-34645606
Node: readline --- GNU readline interface4645655
Ref: library/readline doc4645863
Ref: 17e34645863
Ref: library/readline module-readline4645863
Ref: df4645863
Ref: library/readline readline-gnu-readline-interface4645863
Ref: 17e44645863
Ref: readline --- GNU readline interface-Footnote-14647782
Node: Init file4647852
Ref: library/readline init-file4647953
Ref: 17e54647953
Ref: library/readline readline parse_and_bind4648063
Ref: 17e64648063
Ref: library/readline readline read_init_file4648242
Ref: 17e74648242
Node: Line buffer4648462
Ref: library/readline line-buffer4648584
Ref: 17e84648584
Ref: library/readline readline get_line_buffer4648678
Ref: 17e94648678
Ref: library/readline readline insert_text4648827
Ref: 17ea4648827
Ref: library/readline readline redisplay4649035
Ref: 17eb4649035
Node: History file4649238
Ref: library/readline history-file4649363
Ref: 17ec4649363
Ref: library/readline readline read_history_file4649458
Ref: 17ed4649458
Ref: library/readline readline write_history_file4649694
Ref: 17ee4649694
Ref: library/readline readline append_history_file4649949
Ref: 7414649949
Ref: library/readline readline get_history_length4650352
Ref: 17ef4650352
Ref: library/readline readline set_history_length4650395
Ref: 17f04650395
Node: History list4650756
Ref: library/readline history-list4650883
Ref: 17f14650883
Ref: library/readline readline clear_history4650985
Ref: 17f24650985
Ref: library/readline readline get_current_history_length4651231
Ref: 17f34651231
Ref: library/readline readline get_history_item4651494
Ref: 17f44651494
Ref: library/readline readline remove_history_item4651702
Ref: 17f54651702
Ref: library/readline readline replace_history_item4651920
Ref: 17f64651920
Ref: library/readline readline add_history4652149
Ref: 17f74652149
Ref: library/readline readline set_auto_history4652331
Ref: 57c4652331
Node: Startup hooks4652793
Ref: library/readline startup-hooks4652918
Ref: 17f84652918
Ref: library/readline readline set_startup_hook4652963
Ref: 17f94652963
Ref: library/readline readline set_pre_input_hook4653365
Ref: 17fa4653365
Node: Completion4653935
Ref: library/readline completion4654055
Ref: 17fb4654055
Ref: library/readline readline set_completer4654541
Ref: 17fc4654541
Ref: library/readline readline get_completer4655330
Ref: 17fd4655330
Ref: library/readline readline get_completion_type4655461
Ref: 17fe4655461
Ref: library/readline readline get_begidx4655659
Ref: 17ff4655659
Ref: library/readline readline get_endidx4655694
Ref: 18004655694
Ref: library/readline readline set_completer_delims4655950
Ref: 18014655950
Ref: library/readline readline get_completer_delims4656001
Ref: 18024656001
Ref: library/readline readline set_completion_display_matches_hook4656320
Ref: 18034656320
Node: Example4656907
Ref: library/readline example4657005
Ref: 18044657005
Ref: library/readline readline-example4657005
Ref: 18054657005
Node: rlcompleter --- Completion function for GNU readline4659645
Ref: library/rlcompleter doc4659802
Ref: 18074659802
Ref: library/rlcompleter module-rlcompleter4659802
Ref: e24659802
Ref: library/rlcompleter rlcompleter-completion-function-for-gnu-readline4659802
Ref: 18084659802
Ref: rlcompleter --- Completion function for GNU readline-Footnote-14661267
Node: Completer Objects4661337
Ref: library/rlcompleter completer-objects4661443
Ref: 18094661443
Ref: library/rlcompleter id14661443
Ref: 180a4661443
Ref: library/rlcompleter rlcompleter Completer complete4661542
Ref: 180b4661542
Node: Binary Data Services4662304
Ref: library/binary doc4662452
Ref: 180c4662452
Ref: library/binary binary-data-services4662452
Ref: 180d4662452
Ref: library/binary binaryservices4662452
Ref: 17244662452
Node: struct --- Interpret bytes as packed binary data4663302
Ref: library/struct doc4663458
Ref: 180e4663458
Ref: library/struct module-struct4663458
Ref: f94663458
Ref: library/struct struct-interpret-bytes-as-packed-binary-data4663458
Ref: 180f4663458
Ref: struct --- Interpret bytes as packed binary data-Footnote-14665267
Node: Functions and Exceptions4665332
Ref: library/struct functions-and-exceptions4665464
Ref: 18134665464
Ref: library/struct struct error4665590
Ref: cb94665590
Ref: library/struct struct pack4665713
Ref: c104665713
Ref: library/struct struct pack_into4665954
Ref: 18144665954
Ref: library/struct struct unpack4666252
Ref: 13084666252
Ref: library/struct struct unpack_from4666617
Ref: 18164666617
Ref: library/struct struct iter_unpack4667008
Ref: 8dd4667008
Ref: library/struct struct calcsize4667524
Ref: 18154667524
Node: Format Strings4667721
Ref: library/struct format-strings4667872
Ref: 18174667872
Ref: library/struct struct-format-strings4667872
Ref: 18104667872
Node: Byte Order Size and Alignment4668361
Ref: library/struct byte-order-size-and-alignment4668467
Ref: 18194668467
Ref: library/struct struct-alignment4668467
Ref: 18114668467
Ref: Byte Order Size and Alignment-Footnote-14671627
Node: Format Characters4671671
Ref: library/struct format-characters4671797
Ref: 18184671797
Ref: library/struct id14671797
Ref: 181b4671797
Ref: Format Characters-Footnote-14682744
Ref: Format Characters-Footnote-24682816
Node: Examples<2>4682892
Ref: library/struct examples4682980
Ref: 181c4682980
Ref: library/struct struct-examples4682980
Ref: 181a4682980
Node: Classes<2>4684694
Ref: library/struct classes4684812
Ref: 181d4684812
Ref: library/struct struct-objects4684812
Ref: 181e4684812
Ref: library/struct struct Struct4684908
Ref: 18124684908
Ref: library/struct struct Struct pack4685653
Ref: 181f4685653
Ref: library/struct struct Struct pack_into4685840
Ref: 18214685840
Ref: library/struct struct Struct unpack4686004
Ref: 18224686004
Ref: library/struct struct Struct unpack_from4686210
Ref: 18234686210
Ref: library/struct struct Struct iter_unpack4686474
Ref: 8de4686474
Ref: library/struct struct Struct format4686729
Ref: 4974686729
Ref: library/struct struct Struct size4686932
Ref: 18204686932
Node: codecs --- Codec registry and base classes4687130
Ref: library/codecs doc4687286
Ref: 18244687286
Ref: library/codecs codecs-codec-registry-and-base-classes4687286
Ref: 18254687286
Ref: library/codecs ietf-rfc-17004687286
Ref: 18264687286
Ref: library/codecs module-codecs4687286
Ref: 1c4687286
Ref: library/codecs codecs encode4688147
Ref: 8074688147
Ref: library/codecs codecs decode4688640
Ref: 8084688640
Ref: library/codecs codecs lookup4689198
Ref: 17064689198
Ref: library/codecs codecs CodecInfo4689694
Ref: 18284689694
Ref: library/codecs codecs CodecInfo name4689991
Ref: 18294689991
Ref: library/codecs codecs CodecInfo encode4690051
Ref: 182a4690051
Ref: library/codecs codecs CodecInfo decode4690075
Ref: 182b4690075
Ref: library/codecs codecs CodecInfo incrementalencoder4690450
Ref: 182f4690450
Ref: library/codecs codecs CodecInfo incrementaldecoder4690486
Ref: 18304690486
Ref: library/codecs codecs CodecInfo streamwriter4690822
Ref: 18334690822
Ref: library/codecs codecs CodecInfo streamreader4690852
Ref: 18344690852
Ref: library/codecs codecs getencoder4691303
Ref: 18374691303
Ref: library/codecs codecs getdecoder4691513
Ref: 18384691513
Ref: library/codecs codecs getincrementalencoder4691723
Ref: 18394691723
Ref: library/codecs codecs getincrementaldecoder4692027
Ref: 183a4692027
Ref: library/codecs codecs getreader4692331
Ref: 183b4692331
Ref: library/codecs codecs getwriter4692575
Ref: 183c4692575
Ref: library/codecs codecs register4692902
Ref: 183d4692902
Ref: library/codecs codecs open4693706
Ref: 13674693706
Ref: library/codecs codecs EncodedFile4694959
Ref: 183f4694959
Ref: library/codecs codecs iterencode4695813
Ref: 18404695813
Ref: library/codecs codecs iterdecode4696341
Ref: 18414696341
Ref: library/codecs codecs BOM4697061
Ref: 18424697061
Ref: library/codecs codecs BOM_BE4697082
Ref: 18434697082
Ref: library/codecs codecs BOM_LE4697106
Ref: 18444697106
Ref: library/codecs codecs BOM_UTF84697130
Ref: 18454697130
Ref: library/codecs codecs BOM_UTF164697156
Ref: 18464697156
Ref: library/codecs codecs BOM_UTF16_BE4697183
Ref: 18474697183
Ref: library/codecs codecs BOM_UTF16_LE4697213
Ref: 18484697213
Ref: library/codecs codecs BOM_UTF324697243
Ref: 18494697243
Ref: library/codecs codecs BOM_UTF32_BE4697270
Ref: 184a4697270
Ref: library/codecs codecs BOM_UTF32_LE4697300
Ref: 184b4697300
Ref: codecs --- Codec registry and base classes-Footnote-14698435
Node: Codec Base Classes4698500
Ref: library/codecs codec-base-classes4698627
Ref: 18274698627
Ref: library/codecs id14698627
Ref: 184c4698627
Ref: library/codecs surrogateescape4699220
Ref: 184d4699220
Node: Error Handlers4699357
Ref: library/codecs error-handlers4699466
Ref: 13664699466
Ref: library/codecs id24699466
Ref: 184e4699466
Ref: library/codecs codecs register_error4703528
Ref: dfa4703528
Ref: library/codecs codecs lookup_error4705067
Ref: dfb4705067
Ref: library/codecs codecs strict_errors4705360
Ref: 184f4705360
Ref: library/codecs codecs replace_errors4705529
Ref: 18514705529
Ref: library/codecs codecs ignore_errors4705831
Ref: 18504705831
Ref: library/codecs codecs xmlcharrefreplace_errors4706022
Ref: 18524706022
Ref: library/codecs codecs backslashreplace_errors4706286
Ref: 18534706286
Ref: library/codecs codecs namereplace_errors4706514
Ref: 18544706514
Ref: Error Handlers-Footnote-14706819
Node: Stateless Encoding and Decoding4706868
Ref: library/codecs codec-objects4707019
Ref: 182e4707019
Ref: library/codecs stateless-encoding-and-decoding4707019
Ref: 18554707019
Ref: library/codecs codecs Codec encode4707230
Ref: 182c4707230
Ref: library/codecs codecs Codec decode4707978
Ref: 182d4707978
Node: Incremental Encoding and Decoding4708911
Ref: library/codecs incremental-encoding-and-decoding4709076
Ref: 18564709076
Node: IncrementalEncoder Objects4709916
Ref: library/codecs incremental-encoder-objects4710047
Ref: 18594710047
Ref: library/codecs incrementalencoder-objects4710047
Ref: 185a4710047
Ref: library/codecs codecs IncrementalEncoder4710346
Ref: 18314710346
Ref: library/codecs codecs IncrementalEncoder encode4711132
Ref: 18574711132
Ref: library/codecs codecs IncrementalEncoder reset4711431
Ref: 185b4711431
Ref: library/codecs codecs IncrementalEncoder getstate4711706
Ref: 185c4711706
Ref: library/codecs codecs IncrementalEncoder setstate4712125
Ref: 185d4712125
Node: IncrementalDecoder Objects4712298
Ref: library/codecs incremental-decoder-objects4712429
Ref: 185e4712429
Ref: library/codecs incrementaldecoder-objects4712429
Ref: 185f4712429
Ref: library/codecs codecs IncrementalDecoder4712728
Ref: 18324712728
Ref: library/codecs codecs IncrementalDecoder decode4713514
Ref: 18584713514
Ref: library/codecs codecs IncrementalDecoder reset4714149
Ref: 18604714149
Ref: library/codecs codecs IncrementalDecoder getstate4714233
Ref: 18614714233
Ref: library/codecs codecs IncrementalDecoder setstate4715186
Ref: 18624715186
Node: Stream Encoding and Decoding4715358
Ref: library/codecs stream-encoding-and-decoding4715483
Ref: 18634715483
Node: StreamWriter Objects4715910
Ref: library/codecs stream-writer-objects4716024
Ref: 18644716024
Ref: library/codecs streamwriter-objects4716024
Ref: 18654716024
Ref: library/codecs codecs StreamWriter4716279
Ref: 18354716279
Ref: library/codecs codecs StreamWriter write4717237
Ref: 18664717237
Ref: library/codecs codecs StreamWriter writelines4717341
Ref: 18674717341
Ref: library/codecs codecs StreamWriter reset4717587
Ref: 18684717587
Node: StreamReader Objects4718065
Ref: library/codecs stream-reader-objects4718214
Ref: 18694718214
Ref: library/codecs streamreader-objects4718214
Ref: 186a4718214
Ref: library/codecs codecs StreamReader4718469
Ref: 18364718469
Ref: library/codecs codecs StreamReader read4719540
Ref: 186b4719540
Ref: library/codecs codecs StreamReader readline4720798
Ref: 186c4720798
Ref: library/codecs codecs StreamReader readlines4721149
Ref: 186d4721149
Ref: library/codecs codecs StreamReader reset4721600
Ref: 186e4721600
Node: StreamReaderWriter Objects4722000
Ref: library/codecs stream-reader-writer4722150
Ref: 186f4722150
Ref: library/codecs streamreaderwriter-objects4722150
Ref: 18704722150
Ref: library/codecs codecs StreamReaderWriter4722486
Ref: 183e4722486
Node: StreamRecoder Objects4723142
Ref: library/codecs stream-recoder-objects4723263
Ref: 18714723263
Ref: library/codecs streamrecoder-objects4723263
Ref: 18724723263
Ref: library/codecs codecs StreamRecoder4723613
Ref: fd24723613
Node: Encodings and Unicode4724743
Ref: library/codecs encodings-and-unicode4724897
Ref: 18734724897
Ref: library/codecs encodings-overview4724897
Ref: 18744724897
Ref: Encodings and Unicode-Footnote-14731584
Node: Standard Encodings4731633
Ref: library/codecs id34731794
Ref: 18754731794
Ref: library/codecs standard-encodings4731794
Ref: 6944731794
Node: Python Specific Encodings4753783
Ref: library/codecs python-specific-encodings4753988
Ref: 18764753988
Node: Text Encodings4754576
Ref: library/codecs text-encodings4754678
Ref: 18774754678
Ref: Text Encodings-Footnote-14758035
Ref: Text Encodings-Footnote-24758084
Node: Binary Transforms4758133
Ref: library/codecs binary-transforms4758259
Ref: 8094758259
Ref: library/codecs id44758259
Ref: 18784758259
Ref: Binary Transforms-Footnote-14761994
Node: Text Transforms4762139
Ref: library/codecs id64762242
Ref: 18814762242
Ref: library/codecs text-transforms4762242
Ref: 80a4762242
Node: encodings idna --- Internationalized Domain Names in Applications4762975
Ref: library/codecs encodings-idna-internationalized-domain-names-in-applications4763202
Ref: 18824763202
Ref: library/codecs module-encodings idna4763202
Ref: 774763202
Ref: library/codecs encodings idna nameprep4765854
Ref: 18834765854
Ref: library/codecs encodings idna ToASCII4766040
Ref: 18844766040
Ref: library/codecs encodings idna ToUnicode4766198
Ref: 18854766198
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-14766343
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-24766392
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-34766441
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-44766490
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-54766539
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-64766600
Ref: encodings idna --- Internationalized Domain Names in Applications-Footnote-74766649
Node: encodings mbcs --- Windows ANSI codepage4766698
Ref: library/codecs encodings-mbcs-windows-ansi-codepage4766954
Ref: 18864766954
Ref: library/codecs module-encodings mbcs4766954
Ref: 784766954
Node: encodings utf_8_sig --- UTF-8 codec with BOM signature4767334
Ref: library/codecs encodings-utf-8-sig-utf-8-codec-with-bom-signature4767516
Ref: 18874767516
Ref: library/codecs module-encodings utf_8_sig4767516
Ref: 794767516
Node: Data Types4767961
Ref: library/datatypes doc4768106
Ref: 18884768106
Ref: library/datatypes data-types4768106
Ref: 18894768106
Ref: library/datatypes datatypes4768106
Ref: 188a4768106
Node: datetime --- Basic date and time types4769820
Ref: library/datetime doc4769961
Ref: 188b4769961
Ref: library/datetime datetime-basic-date-and-time-types4769961
Ref: 188c4769961
Ref: library/datetime module-datetime4769961
Ref: 314769961
Ref: datetime --- Basic date and time types-Footnote-14770934
Ref: datetime --- Basic date and time types-Footnote-24771001
Node: Aware and Naive Objects4771052
Ref: library/datetime aware-and-naive-objects4771168
Ref: 188d4771168
Ref: library/datetime datetime-naive-aware4771168
Ref: 188e4771168
Ref: Aware and Naive Objects-Footnote-14773086
Node: Constants4773147
Ref: library/datetime constants4773287
Ref: 188f4773287
Ref: library/datetime datetime MINYEAR4773389
Ref: 18904773389
Ref: library/datetime datetime MAXYEAR4773549
Ref: 18914773549
Node: Available Types4773711
Ref: library/datetime available-types4773845
Ref: 18924773845
Node: Common Properties4775627
Ref: library/datetime common-properties4775747
Ref: 18a34775747
Node: Determining if an Object is Aware or Naive4776157
Ref: library/datetime determining-if-an-object-is-aware-or-naive4776277
Ref: 18a44776277
Node: timedelta Objects4777012
Ref: library/datetime datetime-timedelta4777149
Ref: 18a54777149
Ref: library/datetime timedelta-objects4777149
Ref: 18a64777149
Ref: library/datetime datetime timedelta4777308
Ref: 1964777308
Ref: library/datetime datetime timedelta min4779557
Ref: 18a74779557
Ref: library/datetime datetime timedelta max4779672
Ref: 18a84779672
Ref: library/datetime datetime timedelta resolution4779851
Ref: 18a94779851
Ref: library/datetime datetime timedelta total_seconds4787246
Ref: ca14787246
Node: Examples of usage timedelta4787772
Ref: library/datetime examples-of-usage-timedelta4787853
Ref: 18aa4787853
Node: date Objects4788794
Ref: library/datetime date-objects4788932
Ref: 18ab4788932
Ref: library/datetime datetime-date4788932
Ref: 18ac4788932
Ref: library/datetime datetime date4789254
Ref: 1944789254
Ref: library/datetime datetime date today4789674
Ref: 18ad4789674
Ref: library/datetime datetime date fromtimestamp4789823
Ref: 18ae4789823
Ref: library/datetime datetime date fromordinal4790758
Ref: 18af4790758
Ref: library/datetime datetime date fromisoformat4791097
Ref: 109c4791097
Ref: library/datetime datetime date fromisocalendar4791529
Ref: 1c54791529
Ref: library/datetime datetime date min4791825
Ref: 18b24791825
Ref: library/datetime datetime date max4791913
Ref: 18b34791913
Ref: library/datetime datetime date resolution4792001
Ref: 18b44792001
Ref: library/datetime datetime date year4792165
Ref: 18934792165
Ref: library/datetime datetime date month4792259
Ref: 18944792259
Ref: library/datetime datetime date day4792317
Ref: 18954792317
Ref: library/datetime datetime date replace4794807
Ref: 18b54794807
Ref: library/datetime datetime date timetuple4795198
Ref: 18b64795198
Ref: library/datetime datetime date toordinal4795698
Ref: 18b74795698
Ref: library/datetime datetime date weekday4795926
Ref: 18b84795926
Ref: library/datetime datetime date isoweekday4796157
Ref: 18b94796157
Ref: library/datetime datetime date isocalendar4796423
Ref: 18b14796423
Ref: library/datetime datetime date isoformat4797278
Ref: 18b04797278
Ref: library/datetime datetime date __str__4797573
Ref: 18ba4797573
Ref: library/datetime datetime date ctime4797681
Ref: 18bb4797681
Ref: library/datetime datetime date strftime4798161
Ref: 53d4798161
Ref: library/datetime datetime date __format__4798475
Ref: 18be4798475
Ref: date Objects-Footnote-14798939
Ref: date Objects-Footnote-24799248
Node: Examples of Usage date4799426
Ref: library/datetime examples-of-usage-date4799497
Ref: 18bf4799497
Node: datetime Objects4801389
Ref: library/datetime datetime-datetime4801522
Ref: 18c04801522
Ref: library/datetime datetime-objects4801522
Ref: 18c14801522
Ref: library/datetime datetime datetime4801971
Ref: 1954801971
Ref: library/datetime datetime datetime today4802833
Ref: 18c24802833
Ref: library/datetime datetime datetime now4803197
Ref: 10054803197
Ref: library/datetime datetime datetime utcnow4803884
Ref: 18c34803884
Ref: library/datetime datetime datetime fromtimestamp4804632
Ref: 10904804632
Ref: library/datetime datetime datetime utcfromtimestamp4806338
Ref: 18c44806338
Ref: library/datetime datetime datetime fromordinal4808006
Ref: 18c54808006
Ref: library/datetime datetime datetime combine4808417
Ref: 53e4808417
Ref: library/datetime datetime datetime fromisoformat4809203
Ref: 3834809203
Ref: library/datetime datetime datetime fromisocalendar4810730
Ref: 1c64810730
Ref: library/datetime datetime datetime strptime4811113
Ref: fb44811113
Ref: library/datetime datetime datetime min4811684
Ref: 18c74811684
Ref: library/datetime datetime datetime max4811813
Ref: 18c84811813
Ref: library/datetime datetime datetime resolution4811962
Ref: 18c94811962
Ref: library/datetime datetime datetime year4812154
Ref: 189b4812154
Ref: library/datetime datetime datetime month4812252
Ref: 189c4812252
Ref: library/datetime datetime datetime day4812314
Ref: 189d4812314
Ref: library/datetime datetime datetime hour4812422
Ref: 189e4812422
Ref: library/datetime datetime datetime minute4812475
Ref: 189f4812475
Ref: library/datetime datetime datetime second4812530
Ref: 18a04812530
Ref: library/datetime datetime datetime microsecond4812585
Ref: 18a14812585
Ref: library/datetime datetime datetime tzinfo4812650
Ref: 18a24812650
Ref: library/datetime datetime datetime fold4812808
Ref: 4f94812808
Ref: library/datetime datetime datetime date4817422
Ref: 18ca4817422
Ref: library/datetime datetime datetime time4817526
Ref: 18cb4817526
Ref: library/datetime datetime datetime timetz4817830
Ref: 18cc4817830
Ref: library/datetime datetime datetime replace4818117
Ref: 18cd4818117
Ref: library/datetime datetime datetime astimezone4818703
Ref: 1974818703
Ref: library/datetime datetime datetime utcoffset4821023
Ref: 18ce4821023
Ref: library/datetime datetime datetime dst4821414
Ref: 18cf4821414
Ref: library/datetime datetime datetime tzname4821793
Ref: 18d14821793
Ref: library/datetime datetime datetime timetuple4822032
Ref: 18d24822032
Ref: library/datetime datetime datetime utctimetuple4822891
Ref: 18d34822891
Ref: library/datetime datetime datetime toordinal4824023
Ref: 18d44824023
Ref: library/datetime datetime datetime timestamp4824171
Ref: 9e74824171
Ref: library/datetime datetime datetime weekday4825676
Ref: 18d54825676
Ref: library/datetime datetime datetime isoweekday4825886
Ref: 18d64825886
Ref: library/datetime datetime datetime isocalendar4826126
Ref: 18c64826126
Ref: library/datetime datetime datetime isoformat4826286
Ref: 3844826286
Ref: library/datetime datetime datetime __str__4829276
Ref: 18d74829276
Ref: library/datetime datetime datetime ctime4829421
Ref: 18d84829421
Ref: library/datetime datetime datetime strftime4830060
Ref: 53c4830060
Ref: library/datetime datetime datetime __format__4830310
Ref: 18d94830310
Ref: datetime Objects-Footnote-14830794
Node: Examples of Usage datetime4830882
Ref: library/datetime examples-of-usage-datetime4830961
Ref: 18da4830961
Node: time Objects4835289
Ref: library/datetime datetime-time4835424
Ref: 18db4835424
Ref: library/datetime time-objects4835424
Ref: 18dc4835424
Ref: library/datetime datetime time4835632
Ref: 4f84835632
Ref: library/datetime datetime time min4836298
Ref: 18dd4836298
Ref: library/datetime datetime time max4836394
Ref: 18de4836394
Ref: library/datetime datetime time resolution4836501
Ref: 18df4836501
Ref: library/datetime datetime time hour4836766
Ref: 18964836766
Ref: library/datetime datetime time minute4836815
Ref: 18974836815
Ref: library/datetime datetime time second4836866
Ref: 18984836866
Ref: library/datetime datetime time microsecond4836917
Ref: 18994836917
Ref: library/datetime datetime time tzinfo4836978
Ref: 189a4836978
Ref: library/datetime datetime time fold4837126
Ref: 18e04837126
Ref: library/datetime datetime time fromisoformat4839077
Ref: 109b4839077
Ref: library/datetime datetime time replace4839990
Ref: 18e24839990
Ref: library/datetime datetime time isoformat4840528
Ref: 18e14840528
Ref: library/datetime datetime time __str__4842545
Ref: 18e44842545
Ref: library/datetime datetime time strftime4842653
Ref: 18e54842653
Ref: library/datetime datetime time __format__4842890
Ref: 18e64842890
Ref: library/datetime datetime time utcoffset4843258
Ref: 18e34843258
Ref: library/datetime datetime time dst4843645
Ref: 18e74843645
Ref: library/datetime datetime time tzname4844021
Ref: 18e84844021
Ref: time Objects-Footnote-14844356
Node: Examples of Usage time4844399
Ref: library/datetime examples-of-usage-time4844470
Ref: 18e94844470
Node: tzinfo Objects4845352
Ref: library/datetime datetime-tzinfo4845487
Ref: 18ea4845487
Ref: library/datetime tzinfo-objects4845487
Ref: 18eb4845487
Ref: library/datetime datetime tzinfo4845544
Ref: 3854845544
Ref: library/datetime datetime tzinfo utcoffset4847187
Ref: 18ec4847187
Ref: library/datetime datetime tzinfo dst4848414
Ref: 18ed4848414
Ref: library/datetime datetime tzinfo tzname4850989
Ref: 18ee4850989
Ref: library/datetime datetime tzinfo fromutc4853106
Ref: 18d04853106
Ref: tzinfo Objects-Footnote-14865604
Ref: tzinfo Objects-Footnote-24865662
Node: timezone Objects4865702
Ref: library/datetime datetime-timezone4865855
Ref: 18f04865855
Ref: library/datetime timezone-objects4865855
Ref: 18f14865855
Ref: library/datetime datetime timezone4866275
Ref: a064866275
Ref: library/datetime datetime timezone utcoffset4866893
Ref: 18f24866893
Ref: library/datetime datetime timezone tzname4867280
Ref: 18f34867280
Ref: library/datetime datetime timezone dst4867955
Ref: 18f44867955
Ref: library/datetime datetime timezone fromutc4868025
Ref: 18f54868025
Ref: library/datetime datetime timezone utc4868226
Ref: 18ef4868226
Node: strftime and strptime Behavior4868306
Ref: library/datetime strftime-and-strptime-behavior4868436
Ref: 18f64868436
Ref: library/datetime strftime-strptime-behavior4868436
Ref: 18bd4868436
Node: strftime and strptime Format Codes4870621
Ref: library/datetime strftime-and-strptime-format-codes4870747
Ref: 18f74870747
Node: Technical Detail4880711
Ref: library/datetime technical-detail4880837
Ref: 18f84880837
Ref: Technical Detail-Footnote-14886461
Node: calendar --- General calendar-related functions4886571
Ref: library/calendar doc4886755
Ref: 18fa4886755
Ref: library/calendar calendar-general-calendar-related-functions4886755
Ref: 18fb4886755
Ref: library/calendar module-calendar4886755
Ref: 154886755
Ref: library/calendar calendar Calendar4887950
Ref: 18fd4887950
Ref: library/calendar calendar Calendar iterweekdays4888458
Ref: 18fe4888458
Ref: library/calendar calendar Calendar itermonthdates4888713
Ref: 4ab4888713
Ref: library/calendar calendar Calendar itermonthdays4889091
Ref: 19004889091
Ref: library/calendar calendar Calendar itermonthdays24889482
Ref: 19014889482
Ref: library/calendar calendar Calendar itermonthdays34889838
Ref: 4ac4889838
Ref: library/calendar calendar Calendar itermonthdays44890222
Ref: 4ad4890222
Ref: library/calendar calendar Calendar monthdatescalendar4890626
Ref: 19024890626
Ref: library/calendar calendar Calendar monthdays2calendar4890852
Ref: 19034890852
Ref: library/calendar calendar Calendar monthdayscalendar4891086
Ref: 19044891086
Ref: library/calendar calendar Calendar yeardatescalendar4891279
Ref: 19054891279
Ref: library/calendar calendar Calendar yeardays2calendar4891679
Ref: 19064891679
Ref: library/calendar calendar Calendar yeardayscalendar4892001
Ref: 19074892001
Ref: library/calendar calendar TextCalendar4892292
Ref: 19084892292
Ref: library/calendar calendar TextCalendar formatmonth4892477
Ref: 19094892477
Ref: library/calendar calendar TextCalendar prmonth4892932
Ref: 190a4892932
Ref: library/calendar calendar TextCalendar formatyear4893084
Ref: 190b4893084
Ref: library/calendar calendar TextCalendar pryear4893627
Ref: 190c4893627
Ref: library/calendar calendar HTMLCalendar4893788
Ref: 3744893788
Ref: library/calendar calendar HTMLCalendar formatmonth4893960
Ref: 190d4893960
Ref: library/calendar calendar HTMLCalendar formatyear4894216
Ref: 190e4894216
Ref: library/calendar calendar HTMLCalendar formatyearpage4894403
Ref: 190f4894403
Ref: library/calendar calendar HTMLCalendar cssclasses4895049
Ref: 19104895049
Ref: library/calendar calendar HTMLCalendar cssclass_noday4895460
Ref: 19114895460
Ref: library/calendar calendar HTMLCalendar cssclasses_weekday_head4895614
Ref: 19124895614
Ref: library/calendar calendar HTMLCalendar cssclass_month_head4895822
Ref: 19134895822
Ref: library/calendar calendar HTMLCalendar cssclass_month4896011
Ref: 19144896011
Ref: library/calendar calendar HTMLCalendar cssclass_year4896213
Ref: 19154896213
Ref: library/calendar calendar HTMLCalendar cssclass_year_head4896421
Ref: 19164896421
Ref: library/calendar calendar LocaleTextCalendar4897323
Ref: 19174897323
Ref: library/calendar calendar LocaleHTMLCalendar4897688
Ref: 19184897688
Ref: library/calendar calendar setfirstweekday4898379
Ref: 18fc4898379
Ref: library/calendar calendar firstweekday4898803
Ref: 18ff4898803
Ref: library/calendar calendar isleap4898911
Ref: 19194898911
Ref: library/calendar calendar leapdays4899037
Ref: 191a4899037
Ref: library/calendar calendar weekday4899260
Ref: 191b4899260
Ref: library/calendar calendar weekheader4899457
Ref: 191c4899457
Ref: library/calendar calendar monthrange4899615
Ref: 191d4899615
Ref: library/calendar calendar monthcalendar4899782
Ref: 191e4899782
Ref: library/calendar calendar prmonth4900061
Ref: 191f4900061
Ref: library/calendar calendar month4900191
Ref: 19204900191
Ref: library/calendar calendar prcal4900382
Ref: 19214900382
Ref: library/calendar calendar calendar4900524
Ref: 19224900524
Ref: library/calendar calendar timegm4900737
Ref: 19234900737
Ref: library/calendar calendar day_name4901211
Ref: 19244901211
Ref: library/calendar calendar day_abbr4901320
Ref: 19254901320
Ref: library/calendar calendar month_name4901441
Ref: 19264901441
Ref: library/calendar calendar month_abbr4901699
Ref: 19274901699
Ref: calendar --- General calendar-related functions-Footnote-14902231
Node: collections --- 容器資料型態4902298
Ref: library/collections doc4902500
Ref: 19284902500
Ref: library/collections collections-container-datatypes4902500
Ref: 19294902500
Ref: library/collections module-collections4902500
Ref: 1e4902500
Ref: collections --- 容器資料型態-Footnote-14904780
Node: ChainMap objects4904860
Ref: library/collections chainmap-objects4904970
Ref: 192d4904970
Ref: library/collections collections ChainMap4905355
Ref: 4ae4905355
Ref: library/collections collections ChainMap maps4906389
Ref: 192e4906389
Ref: library/collections collections ChainMap new_child4906689
Ref: 82e4906689
Ref: library/collections collections ChainMap parents4907324
Ref: 192f4907324
Ref: ChainMap objects-Footnote-14909173
Ref: ChainMap objects-Footnote-24909268
Ref: ChainMap objects-Footnote-34909315
Ref: ChainMap objects-Footnote-44909394
Ref: ChainMap objects-Footnote-54909447
Node: ChainMap Examples and Recipes4909500
Ref: library/collections chainmap-examples-and-recipes4909582
Ref: 19304909582
Node: Counter 物件4912696
Ref: library/collections counter-objects4912828
Ref: 19314912828
Ref: library/collections collections Counter4913515
Ref: 9df4913515
Ref: library/collections collections Counter elements4915483
Ref: c9f4915483
Ref: library/collections collections Counter most_common4915912
Ref: c9e4915912
Ref: library/collections collections Counter subtract4916378
Ref: b5f4916378
Ref: library/collections collections Counter fromkeys4917073
Ref: 19324917073
Ref: library/collections collections Counter update4917208
Ref: 19334917208
Ref: Counter 物件-Footnote-14921599
Ref: Counter 物件-Footnote-24921678
Ref: Counter 物件-Footnote-34921725
Node: deque objects4921818
Ref: library/collections deque-objects4921953
Ref: 19344921953
Ref: library/collections collections deque4922006
Ref: 5364922006
Ref: library/collections collections deque append4923442
Ref: 19354923442
Ref: library/collections collections deque appendleft4923528
Ref: 19364923528
Ref: library/collections collections deque clear4923617
Ref: 19374923617
Ref: library/collections collections deque copy4923722
Ref: 6b04923722
Ref: library/collections collections deque count4923830
Ref: b614923830
Ref: library/collections collections deque extend4923953
Ref: 19384923953
Ref: library/collections collections deque extendleft4924101
Ref: 19394924101
Ref: library/collections collections deque index4924354
Ref: 6ae4924354
Ref: library/collections collections deque insert4924630
Ref: 6af4924630
Ref: library/collections collections deque pop4924879
Ref: 193a4924879
Ref: library/collections collections deque popleft4925055
Ref: 193b4925055
Ref: library/collections collections deque remove4925234
Ref: 193c4925234
Ref: library/collections collections deque reverse4925381
Ref: b624925381
Ref: library/collections collections deque rotate4925537
Ref: 193d4925537
Ref: library/collections collections deque maxlen4925952
Ref: ca04925952
Node: deque Recipes4928598
Ref: library/collections deque-recipes4928661
Ref: 193e4928661
Ref: deque Recipes-Footnote-14931124
Node: defaultdict objects4931185
Ref: library/collections defaultdict-objects4931362
Ref: 193f4931362
Ref: library/collections collections defaultdict4931427
Ref: b3f4931427
Ref: library/collections collections defaultdict __missing__4932209
Ref: 19414932209
Ref: library/collections collections defaultdict default_factory4933404
Ref: 19404933404
Node: defaultdict Examples4933672
Ref: library/collections defaultdict-examples4933748
Ref: 19424933748
Node: namedtuple Factory Function for Tuples with Named Fields4936411
Ref: library/collections namedtuple-factory-function-for-tuples-with-named-fields4936594
Ref: 19434936594
Ref: library/collections collections namedtuple4936975
Ref: 1b84936975
Ref: library/collections collections somenamedtuple _make4940837
Ref: 19444940837
Ref: library/collections collections somenamedtuple _asdict4941074
Ref: 1b74941074
Ref: library/collections collections somenamedtuple _replace4941748
Ref: 19454941748
Ref: library/collections collections somenamedtuple _fields4942154
Ref: 19464942154
Ref: library/collections collections somenamedtuple _field_defaults4942647
Ref: 19474942647
Node: OrderedDict objects4945402
Ref: library/collections ordereddict-objects4945582
Ref: 19484945582
Ref: library/collections collections OrderedDict4947005
Ref: 1ba4947005
Ref: library/collections collections OrderedDict popitem4947200
Ref: c894947200
Ref: library/collections collections OrderedDict move_to_end4947464
Ref: b604947464
Ref: OrderedDict objects-Footnote-14948994
Ref: OrderedDict objects-Footnote-24949079
Node: OrderedDict Examples and Recipes4949128
Ref: library/collections ordereddict-examples-and-recipes4949216
Ref: 194b4949216
Node: UserDict objects4950556
Ref: library/collections userdict-objects4950696
Ref: 194c4950696
Ref: library/collections collections UserDict4951062
Ref: 192a4951062
Ref: library/collections collections UserDict data4951653
Ref: 194d4951653
Node: UserList objects4951778
Ref: library/collections userlist-objects4951917
Ref: 194e4951917
Ref: library/collections collections UserList4952432
Ref: 192b4952432
Ref: library/collections collections UserList data4953038
Ref: 194f4953038
Node: UserString objects4953829
Ref: library/collections userstring-objects4953943
Ref: 19504953943
Ref: library/collections collections UserString4954305
Ref: 6b24954305
Ref: library/collections collections UserString data4954900
Ref: 19514954900
Node: collections abc --- Abstract Base Classes for Containers4955188
Ref: library/collections abc doc4955386
Ref: 19524955386
Ref: library/collections abc collections-abc-abstract-base-classes-for-containers4955386
Ref: 19534955386
Ref: library/collections abc module-collections abc4955386
Ref: 1f4955386
Ref: collections abc --- Abstract Base Classes for Containers-Footnote-14955996
Node: Collections Abstract Base Classes4956072
Ref: library/collections abc collections-abstract-base-classes4956198
Ref: 192c4956198
Ref: library/collections abc id14956198
Ref: 19544956198
Ref: library/collections abc collections abc Container4965158
Ref: 19554965158
Ref: library/collections abc collections abc Hashable4965271
Ref: 19564965271
Ref: library/collections abc collections abc Sized4965379
Ref: 19594965379
Ref: library/collections abc collections abc Callable4965483
Ref: 195a4965483
Ref: library/collections abc collections abc Iterable4965592
Ref: 19574965592
Ref: library/collections abc collections abc Collection4966073
Ref: 5324966073
Ref: library/collections abc collections abc Iterator4966185
Ref: 19584966185
Ref: library/collections abc collections abc Reversible4966382
Ref: 5334966382
Ref: library/collections abc collections abc Generator4966539
Ref: 6ba4966539
Ref: library/collections abc collections abc Sequence4966856
Ref: 16354966856
Ref: library/collections abc collections abc MutableSequence4966893
Ref: 6b14966893
Ref: library/collections abc collections abc ByteString4966937
Ref: 195b4966937
Ref: library/collections abc collections abc Set4967665
Ref: 16df4967665
Ref: library/collections abc collections abc MutableSet4967697
Ref: 195c4967697
Ref: library/collections abc collections abc Mapping4967780
Ref: 19494967780
Ref: library/collections abc collections abc MutableMapping4967816
Ref: 9f44967816
Ref: library/collections abc collections abc MappingView4967918
Ref: 195d4967918
Ref: library/collections abc collections abc ItemsView4967958
Ref: 195e4967958
Ref: library/collections abc collections abc KeysView4967996
Ref: 195f4967996
Ref: library/collections abc collections abc ValuesView4968033
Ref: 19604968033
Ref: library/collections abc collections abc Awaitable4968140
Ref: 6bb4968140
Ref: library/collections abc collections abc Coroutine4968917
Ref: 6bc4968917
Ref: library/collections abc collections abc AsyncIterable4969812
Ref: 6be4969812
Ref: library/collections abc collections abc AsyncIterator4970005
Ref: 6bd4970005
Ref: library/collections abc collections abc AsyncGenerator4970218
Ref: 5354970218
Ref: Collections Abstract Base Classes-Footnote-14973257
Ref: Collections Abstract Base Classes-Footnote-24973306
Ref: Collections Abstract Base Classes-Footnote-34973355
Ref: Collections Abstract Base Classes-Footnote-44973404
Ref: Collections Abstract Base Classes-Footnote-54973457
Node: heapq --- 堆積佇列 heap queue 演算法4973506
Ref: library/heapq doc4973728
Ref: 19614973728
Ref: library/heapq heapq-heap-queue-algorithm4973728
Ref: 19624973728
Ref: library/heapq module-heapq4973728
Ref: 8e4973728
Ref: library/heapq heapq heappush4975276
Ref: 19644975276
Ref: library/heapq heapq heappop4975381
Ref: 19654975381
Ref: library/heapq heapq heappushpop4975637
Ref: 19664975637
Ref: library/heapq heapq heapify4975878
Ref: 19634975878
Ref: library/heapq heapq heapreplace4976000
Ref: 19674976000
Ref: library/heapq heapq merge4976841
Ref: 6e44976841
Ref: library/heapq heapq nlargest4977978
Ref: 19684977978
Ref: library/heapq heapq nsmallest4978374
Ref: 19694978374
Ref: heapq --- 堆積佇列 heap queue 演算法-Footnote-14979264
Node: 基礎範例4979328
Ref: library/heapq basic-examples4979469
Ref: 196a4979469
Ref: 基礎範例-Footnote-14980436
Node: 優先佇列 Priority Queue 實作細節4980483
Ref: library/heapq priority-queue-implementation-notes4980639
Ref: 196b4980639
Ref: 優先佇列 Priority Queue 實作細節-Footnote-14983567
Node: 原理4983620
Ref: library/heapq theory4983755
Ref: 196c4983755
Ref: 原理-Footnote-14987873
Node: bisect --- 陣列二分演算法 Array bisection algorithm4988529
Ref: library/bisect doc4988735
Ref: 196d4988735
Ref: library/bisect bisect-array-bisection-algorithm4988735
Ref: 196e4988735
Ref: library/bisect module-bisect4988735
Ref: 124988735
Ref: library/bisect bisect bisect_left4989449
Ref: 196f4989449
Ref: library/bisect bisect bisect_right4990101
Ref: 19704990101
Ref: library/bisect bisect bisect4990157
Ref: 19714990157
Ref: library/bisect bisect insort_left4990525
Ref: 19724990525
Ref: library/bisect bisect insort_right4990889
Ref: 19734990889
Ref: library/bisect bisect insort4990945
Ref: 19744990945
Ref: bisect --- 陣列二分演算法 Array bisection algorithm-Footnote-14991473
Ref: bisect --- 陣列二分演算法 Array bisection algorithm-Footnote-24991538
Node: Searching Sorted Lists4991608
Ref: library/bisect searching-sorted-lists4991748
Ref: 19754991748
Node: Other Examples4992970
Ref: library/bisect other-examples4993110
Ref: 19764993110
Ref: library/bisect bisect-example4993157
Ref: 19774993157
Node: array --- 高效率的數值型態陣列4994478
Ref: library/array doc4994668
Ref: 19784994668
Ref: library/array array-efficient-arrays-of-numeric-values4994668
Ref: 19794994668
Ref: library/array module-array4994668
Ref: 74994668
Ref: library/array array array4999119
Ref: 4564999119
Ref: library/array array typecodes4999824
Ref: 197e4999824
Ref: library/array array array typecode5000336
Ref: 197f5000336
Ref: library/array array array itemsize5000413
Ref: 19805000413
Ref: library/array array array append5000520
Ref: 19815000520
Ref: library/array array array buffer_info5000610
Ref: 19825000610
Ref: library/array array array byteswap5001487
Ref: 19835001487
Ref: library/array array array count5001768
Ref: 19845001768
Ref: library/array array array extend5001851
Ref: 197d5001851
Ref: library/array array array frombytes5002240
Ref: 197b5002240
Ref: library/array array array fromfile5002593
Ref: 19855002593
Ref: library/array array array fromlist5002908
Ref: 197a5002908
Ref: library/array array array fromstring5003110
Ref: 19865003110
Ref: library/array array array fromunicode5003297
Ref: 197c5003297
Ref: library/array array array index5003622
Ref: f115003622
Ref: library/array array array insert5003745
Ref: 19875003745
Ref: library/array array array pop5003885
Ref: 19885003885
Ref: library/array array array remove5004076
Ref: 19895004076
Ref: library/array array array reverse5004163
Ref: 198a5004163
Ref: library/array array array tobytes5004251
Ref: 198b5004251
Ref: library/array array array tofile5004579
Ref: 198c5004579
Ref: library/array array array tolist5004713
Ref: 198e5004713
Ref: library/array array array tostring5004806
Ref: 198d5004806
Ref: library/array array array tounicode5004989
Ref: 198f5004989
Ref: array --- 高效率的數值型態陣列-Footnote-15006432
Node: weakref --- Weak references5006468
Ref: library/weakref doc5006660
Ref: 19905006660
Ref: library/weakref module-weakref5006660
Ref: 1295006660
Ref: library/weakref weakref-weak-references5006660
Ref: 19915006660
Ref: library/weakref weakref ref5010440
Ref: 9155010440
Ref: library/weakref weakref ref __callback__5012251
Ref: 9165012251
Ref: library/weakref weakref proxy5012599
Ref: 2515012599
Ref: library/weakref weakref getweakrefcount5013449
Ref: 19955013449
Ref: library/weakref weakref getweakrefs5013580
Ref: 19965013580
Ref: library/weakref weakref WeakKeyDictionary5013712
Ref: 19925013712
Ref: library/weakref weakref WeakKeyDictionary keyrefs5014553
Ref: 19975014553
Ref: library/weakref weakref WeakValueDictionary5014662
Ref: 19935014662
Ref: library/weakref weakref WeakValueDictionary valuerefs5015039
Ref: 19985015039
Ref: library/weakref weakref WeakSet5015154
Ref: cbd5015154
Ref: library/weakref weakref WeakMethod5015339
Ref: 9145015339
Ref: library/weakref weakref finalize5016273
Ref: 29e5016273
Ref: library/weakref weakref finalize __call__5017573
Ref: 19995017573
Ref: library/weakref weakref finalize detach5017790
Ref: 199a5017790
Ref: library/weakref weakref finalize peek5017997
Ref: 199b5017997
Ref: library/weakref weakref finalize alive5018172
Ref: 199c5018172
Ref: library/weakref weakref finalize atexit5018284
Ref: 199d5018284
Ref: library/weakref weakref ReferenceType5018880
Ref: 199e5018880
Ref: library/weakref weakref ProxyType5018964
Ref: 199f5018964
Ref: library/weakref weakref CallableProxyType5019062
Ref: 19a05019062
Ref: library/weakref weakref ProxyTypes5019154
Ref: 19a15019154
Ref: weakref --- Weak references-Footnote-15019783
Ref: weakref --- Weak references-Footnote-25019849
Node: Weak Reference Objects5019898
Ref: library/weakref weak-reference-objects5020003
Ref: 19a25020003
Ref: library/weakref weakref-objects5020003
Ref: 19a35020003
Node: Example<2>5022523
Ref: library/weakref example5022654
Ref: 19a45022654
Ref: library/weakref weakref-example5022654
Ref: 19a55022654
Node: Finalizer Objects5023195
Ref: library/weakref finalize-examples5023345
Ref: 19a65023345
Ref: library/weakref finalizer-objects5023345
Ref: 19a75023345
Node: Comparing finalizers with __del__ methods5025196
Ref: library/weakref comparing-finalizers-with-del-methods5025327
Ref: 19a85025327
Node: types --- Dynamic type creation and names for built-in types5028153
Ref: library/types doc5028346
Ref: 19a95028346
Ref: library/types module-types5028346
Ref: 1195028346
Ref: library/types types-dynamic-type-creation-and-names-for-built-in-types5028346
Ref: 19aa5028346
Ref: types --- Dynamic type creation and names for built-in types-Footnote-15029147
Node: Dynamic Type Creation5029211
Ref: library/types dynamic-type-creation5029364
Ref: 19ab5029364
Ref: library/types types new_class5029425
Ref: library/types types prepare_class5030125
Ref: abd5030125
Ref: library/types types resolve_bases5031280
Ref: 40b5031280
Ref: Dynamic Type Creation-Footnote-15031946
Ref: Dynamic Type Creation-Footnote-25031995
Ref: Dynamic Type Creation-Footnote-35032044
Node: Standard Interpreter Types5032093
Ref: library/types standard-interpreter-types5032295
Ref: 19ac5032295
Ref: library/types types FunctionType5032849
Ref: 19ad5032849
Ref: library/types types LambdaType5032878
Ref: 19ae5032878
Ref: library/types types GeneratorType5033233
Ref: 19af5033233
Ref: library/types types CoroutineType5033359
Ref: 7825033359
Ref: library/types types AsyncGeneratorType5033512
Ref: 19b05033512
Ref: library/types types CodeType5033694
Ref: 1995033694
Ref: library/types types CodeType replace5034272
Ref: 19b15034272
Ref: library/types types CellType5034440
Ref: 14315034440
Ref: library/types types MethodType5034599
Ref: 19b25034599
Ref: library/types types BuiltinFunctionType5034686
Ref: 19b35034686
Ref: library/types types BuiltinMethodType5034722
Ref: 19b45034722
Ref: library/types types WrapperDescriptorType5034937
Ref: 4075034937
Ref: library/types types MethodWrapperType5035150
Ref: 4085035150
Ref: library/types types MethodDescriptorType5035349
Ref: 4095035349
Ref: library/types types ClassMethodDescriptorType5035502
Ref: 40a5035502
Ref: library/types types ModuleType5035685
Ref: 6f65035685
Ref: library/types types ModuleType __doc__5036051
Ref: 19b55036051
Ref: library/types types ModuleType __loader__5036155
Ref: 19b65036155
Ref: library/types types ModuleType __name__5036889
Ref: 19b85036889
Ref: library/types types ModuleType __package__5037029
Ref: 19ba5037029
Ref: library/types types ModuleType __spec__5038030
Ref: 19bc5038030
Ref: library/types types TracebackType5038251
Ref: 33a5038251
Ref: library/types types FrameType5038563
Ref: 19bd5038563
Ref: library/types types GetSetDescriptorType5038804
Ref: 19be5038804
Ref: library/types types MemberDescriptorType5039165
Ref: 19bf5039165
Ref: library/types types MappingProxyType5039683
Ref: abb5039683
Ref: library/types types MappingProxyType copy5040515
Ref: 19c05040515
Ref: library/types types MappingProxyType get5040607
Ref: 19c15040607
Ref: library/types types MappingProxyType items5040886
Ref: 19c25040886
Ref: library/types types MappingProxyType keys5041022
Ref: 19c35041022
Ref: library/types types MappingProxyType values5041119
Ref: 19c45041119
Node: Additional Utility Classes and Functions5041220
Ref: library/types additional-utility-classes-and-functions5041428
Ref: 19c55041428
Ref: library/types types SimpleNamespace5041527
Ref: 9b15041527
Ref: library/types types DynamicClassAttribute5042787
Ref: 8f85042787
Node: Coroutine Utility Functions5043440
Ref: library/types coroutine-utility-functions5043613
Ref: 19c65043613
Ref: library/types types coroutine5043686
Ref: 7815043686
Node: copy --- Shallow and deep copy operations5044506
Ref: library/copy doc5044702
Ref: 19c75044702
Ref: library/copy copy-shallow-and-deep-copy-operations5044702
Ref: 19c85044702
Ref: library/copy module-copy5044702
Ref: 265044702
Ref: library/copy copy copy5045257
Ref: 3d05045257
Ref: library/copy copy deepcopy5045320
Ref: 3d15045320
Ref: library/copy copy Error5045392
Ref: 19c95045392
Ref: library/copy shallow-vs-deep-copy5045456
Ref: 122e5045456
Ref: copy --- Shallow and deep copy operations-Footnote-15048098
Node: pprint --- Data pretty printer5048161
Ref: library/pprint doc5048338
Ref: 19ca5048338
Ref: library/pprint module-pprint5048338
Ref: d35048338
Ref: library/pprint pprint-data-pretty-printer5048338
Ref: 19cb5048338
Ref: library/pprint pprint PrettyPrinter5049332
Ref: 89a5049332
Ref: library/pprint pprint pformat5051987
Ref: 89b5051987
Ref: library/pprint pprint pp5052431
Ref: 2135052431
Ref: library/pprint pprint pprint5052852
Ref: 2145052852
Ref: library/pprint pprint isreadable5053913
Ref: 19cc5053913
Ref: library/pprint pprint isrecursive5054215
Ref: 19cd5054215
Ref: library/pprint pprint saferepr5054365
Ref: 19ce5054365
Ref: pprint --- Data pretty printer-Footnote-15054947
Node: PrettyPrinter Objects5055012
Ref: library/pprint id15055119
Ref: 19cf5055119
Ref: library/pprint prettyprinter-objects5055119
Ref: 19d05055119
Ref: library/pprint pprint PrettyPrinter pformat5055247
Ref: 19d15055247
Ref: library/pprint pprint PrettyPrinter pprint5055452
Ref: 19d25055452
Ref: library/pprint pprint PrettyPrinter isreadable5055845
Ref: 19d35055845
Ref: library/pprint pprint PrettyPrinter isrecursive5056249
Ref: 19d45056249
Ref: library/pprint pprint PrettyPrinter format5056571
Ref: 19d55056571
Node: Example<3>5057736
Ref: library/pprint example5057843
Ref: 19d65057843
Ref: library/pprint pprint-example5057843
Ref: 19d75057843
Ref: Example<3>-Footnote-15065153
Node: reprlib --- Alternate repr implementation5065178
Ref: library/reprlib doc5065347
Ref: 19d85065347
Ref: library/reprlib module-reprlib5065347
Ref: e05065347
Ref: library/reprlib reprlib-alternate-repr-implementation5065347
Ref: 19d95065347
Ref: library/reprlib reprlib Repr5065843
Ref: 19da5065843
Ref: library/reprlib reprlib aRepr5066128
Ref: 19db5066128
Ref: library/reprlib reprlib repr5066411
Ref: 19dc5066411
Ref: library/reprlib reprlib recursive_repr5066811
Ref: b755066811
Ref: reprlib --- Alternate repr implementation-Footnote-15067609
Node: Repr Objects5067675
Ref: library/reprlib id15067798
Ref: 19de5067798
Ref: library/reprlib repr-objects5067798
Ref: 19df5067798
Ref: library/reprlib reprlib Repr maxlevel5068039
Ref: 19e05068039
Ref: library/reprlib reprlib Repr maxdict5068160
Ref: 19e15068160
Ref: library/reprlib reprlib Repr maxlist5068185
Ref: 19e25068185
Ref: library/reprlib reprlib Repr maxtuple5068210
Ref: 19e35068210
Ref: library/reprlib reprlib Repr maxset5068236
Ref: 19e45068236
Ref: library/reprlib reprlib Repr maxfrozenset5068260
Ref: 19e55068260
Ref: library/reprlib reprlib Repr maxdeque5068290
Ref: 19e65068290
Ref: library/reprlib reprlib Repr maxarray5068316
Ref: 19e75068316
Ref: library/reprlib reprlib Repr maxlong5068541
Ref: 19e85068541
Ref: library/reprlib reprlib Repr maxstring5068707
Ref: 19e95068707
Ref: library/reprlib reprlib Repr maxother5069057
Ref: 19ea5069057
Ref: library/reprlib reprlib Repr repr5069333
Ref: 19dd5069333
Ref: library/reprlib reprlib Repr repr15069479
Ref: 19eb5069479
Node: Subclassing Repr Objects5070309
Ref: library/reprlib subclassing-repr-objects5070432
Ref: 19ec5070432
Ref: library/reprlib subclassing-reprs5070432
Ref: 19ed5070432
Node: enum --- Support for enumerations5071115
Ref: library/enum doc5071245
Ref: 19ee5071245
Ref: library/enum enum-support-for-enumerations5071245
Ref: 19ef5071245
Ref: library/enum module-enum5071245
Ref: 7b5071245
Ref: enum --- Support for enumerations-Footnote-15072442
Node: Module Contents<2>5072505
Ref: library/enum module-contents5072618
Ref: 19f05072618
Ref: library/enum enum Enum5072941
Ref: 38c5072941
Ref: library/enum enum IntEnum5073100
Ref: 5925073100
Ref: library/enum enum IntFlag5073226
Ref: 17605073226
Ref: library/enum enum Flag5073490
Ref: 54a5073490
Ref: library/enum enum auto5073788
Ref: 54b5073788
Node: Creating an Enum5073973
Ref: library/enum creating-an-enum5074158
Ref: 19f35074158
Node: Programmatic access to enumeration members and their attributes5076610
Ref: library/enum programmatic-access-to-enumeration-members-and-their-attributes5076812
Ref: 19f55076812
Node: Duplicating enum members and values5077570
Ref: library/enum duplicating-enum-members-and-values5077790
Ref: 19f65077790
Node: Ensuring unique enumeration values5078883
Ref: library/enum ensuring-unique-enumeration-values5079062
Ref: 19f75079062
Ref: library/enum enum unique5079361
Ref: 19f15079361
Node: Using automatic values5079906
Ref: library/enum using-automatic-values5080059
Ref: 19f85080059
Node: Iteration5081276
Ref: library/enum iteration5081409
Ref: 19f95081409
Node: Comparisons<3>5082271
Ref: library/enum comparisons5082428
Ref: 19fa5082428
Node: Allowed members and attributes of enumerations5083352
Ref: library/enum allowed-members-and-attributes-of-enumerations5083527
Ref: 19fc5083527
Node: Restricted Enum subclassing5085364
Ref: library/enum restricted-enum-subclassing5085533
Ref: 19fe5085533
Node: Pickling5086634
Ref: library/enum pickling5086771
Ref: 1a005086771
Node: Functional API5087417
Ref: library/enum functional-api5087547
Ref: 19f25087547
Node: Derived Enumerations5090797
Ref: library/enum derived-enumerations5090950
Ref: 1a025090950
Node: IntEnum5091067
Ref: library/enum intenum5091147
Ref: 19fb5091147
Node: IntFlag5092274
Ref: library/enum intflag5092367
Ref: 1a035092367
Node: Flag5093903
Ref: library/enum flag5093995
Ref: 1a045093995
Node: Others5096109
Ref: library/enum others5096185
Ref: 1a055096185
Node: When to use __new__ vs __init__5097986
Ref: library/enum when-to-use-new-vs-init5098145
Ref: 1a065098145
Node: Interesting examples5099263
Ref: library/enum interesting-examples5099426
Ref: 1a075099426
Node: Omitting values5099873
Ref: library/enum omitting-values5099965
Ref: 1a085099965
Node: Using auto5101017
Ref: library/enum using-auto5101100
Ref: 1a095101100
Node: Using object5101354
Ref: library/enum using-object5101472
Ref: 1a0a5101472
Node: Using a descriptive string5101738
Ref: library/enum using-a-descriptive-string5101868
Ref: 1a0b5101868
Node: Using a custom __new__5102191
Ref: library/enum using-a-custom-new5102300
Ref: 1a0c5102300
Node: OrderedEnum5104005
Ref: library/enum orderedenum5104123
Ref: 19ff5104123
Node: DuplicateFreeEnum5105305
Ref: library/enum duplicatefreeenum5105414
Ref: 1a0d5105414
Node: Planet5106495
Ref: library/enum planet5106603
Ref: 19fd5106603
Node: TimePeriod5107665
Ref: library/enum timeperiod5107747
Ref: 1a0e5107747
Node: How are Enums different?5108362
Ref: library/enum how-are-enums-different5108485
Ref: 19f45108485
Node: Enum Classes5108777
Ref: library/enum enum-classes5108885
Ref: 1a0f5108885
Node: Enum Members aka instances5109463
Ref: library/enum enum-members-aka-instances5109592
Ref: 1a105109592
Node: Finer Points5109988
Ref: library/enum finer-points5110096
Ref: 1a115110096
Node: Supported __dunder__ names5110340
Ref: library/enum supported-dunder-names5110448
Ref: 1a125110448
Node: Supported _sunder_ names5110871
Ref: library/enum supported-sunder-names5111004
Ref: 1a135111004
Node: Enum member type5112504
Ref: library/enum enum-member-type5112652
Ref: 1a145112652
Node: Boolean value of Enum classes and members5113358
Ref: library/enum boolean-value-of-enum-classes-and-members5113507
Ref: 1a155113507
Node: Enum classes with methods5114080
Ref: library/enum enum-classes-with-methods5114238
Ref: 1a165114238
Node: Combining members of Flag5114774
Ref: library/enum combining-members-of-flag5114882
Ref: 1a175114882
Node: 數值與數學模組5115502
Ref: library/numeric doc5115645
Ref: 1a185115645
Ref: library/numeric numeric5115645
Ref: 1a195115645
Ref: library/numeric numeric-and-mathematical-modules5115645
Ref: 1a1a5115645
Node: numbers --- Numeric abstract base classes5116774
Ref: library/numbers doc5116913
Ref: 1a1b5116913
Ref: library/numbers module-numbers5116913
Ref: c25116913
Ref: library/numbers numbers-numeric-abstract-base-classes5116913
Ref: 1a1c5116913
Ref: library/numbers numbers Number5117336
Ref: 14285117336
Ref: numbers --- Numeric abstract base classes-Footnote-15117633
Ref: numbers --- Numeric abstract base classes-Footnote-25117699
Node: The numeric tower5117748
Ref: library/numbers the-numeric-tower5117879
Ref: 1a1d5117879
Ref: library/numbers numbers Complex5117932
Ref: 142b5117932
Ref: library/numbers numbers Complex real5118374
Ref: 1a1e5118374
Ref: library/numbers numbers Complex imag5118464
Ref: 1a1f5118464
Ref: library/numbers numbers Complex conjugate5118559
Ref: 1a205118559
Ref: library/numbers numbers Real5118724
Ref: 142a5118724
Ref: library/numbers numbers Rational5119232
Ref: c5d5119232
Ref: library/numbers numbers Rational numerator5119470
Ref: 1a215119470
Ref: library/numbers numbers Rational denominator5119519
Ref: 1a225119519
Ref: library/numbers numbers Integral5119570
Ref: 14295119570
Node: Notes for type implementors5119906
Ref: library/numbers notes-for-type-implementors5120037
Ref: 1a235120037
Node: Adding More Numeric ABCs5120887
Ref: library/numbers adding-more-numeric-abcs5121022
Ref: 1a245121022
Node: Implementing the arithmetic operations5121368
Ref: library/numbers id15121503
Ref: 1a255121503
Ref: library/numbers implementing-the-arithmetic-operations5121503
Ref: 14275121503
Node: math --- Mathematical functions5126295
Ref: library/math doc5126495
Ref: 1a265126495
Ref: library/math math-mathematical-functions5126495
Ref: 1a275126495
Ref: library/math module-math5126495
Ref: b25126495
Node: Number-theoretic and representation functions5127665
Ref: library/math number-theoretic-and-representation-functions5127818
Ref: 1a285127818
Ref: library/math math ceil5127927
Ref: d325127927
Ref: library/math math comb5128157
Ref: 1e85128157
Ref: library/math math copysign5128764
Ref: d425128764
Ref: library/math math fabs5128976
Ref: 1a295128976
Ref: library/math math factorial5129043
Ref: 1eb5129043
Ref: library/math math floor5129192
Ref: d315129192
Ref: library/math math fmod5129418
Ref: 153d5129418
Ref: library/math math frexp5130402
Ref: 1a2a5130402
Ref: library/math math fsum5130761
Ref: d435130761
Ref: library/math math gcd5131598
Ref: 71b5131598
Ref: library/math math isclose5131901
Ref: 68b5131901
Ref: library/math math isfinite5133242
Ref: b6c5133242
Ref: library/math math isinf5133441
Ref: d405133441
Ref: library/math math isnan5133568
Ref: d415133568
Ref: library/math math isqrt5133684
Ref: 1e95133684
Ref: library/math math ldexp5134198
Ref: 1a2b5134198
Ref: library/math math modf5134331
Ref: 1a2c5134331
Ref: library/math math perm5134469
Ref: 1e75134469
Ref: library/math math prod5135006
Ref: 1e55135006
Ref: library/math math remainder5135378
Ref: 3b05135378
Ref: library/math math trunc5136400
Ref: d335136400
Ref: Number-theoretic and representation functions-Footnote-15137286
Ref: Number-theoretic and representation functions-Footnote-25137339
Node: Power and logarithmic functions5137388
Ref: library/math power-and-logarithmic-functions5137573
Ref: 1a2d5137573
Ref: library/math math exp5137654
Ref: cae5137654
Ref: library/math math expm15137871
Ref: b6d5137871
Ref: library/math math log5138480
Ref: e165138480
Ref: library/math math log1p5138713
Ref: d475138713
Ref: library/math math log25138874
Ref: a255138874
Ref: library/math math log105139209
Ref: 1a2e5139209
Ref: library/math math pow5139339
Ref: 1a2f5139339
Ref: library/math math sqrt5140033
Ref: 1ea5140033
Ref: Power and logarithmic functions-Footnote-15140133
Node: Trigonometric functions5140192
Ref: library/math trigonometric-functions5140350
Ref: 1a305140350
Ref: library/math math acos5140415
Ref: 1a315140415
Ref: library/math math asin5140490
Ref: 1a325140490
Ref: library/math math atan5140563
Ref: 1a335140563
Ref: library/math math atan25140639
Ref: 1a345140639
Ref: library/math math cos5141149
Ref: e155141149
Ref: library/math math dist5141215
Ref: 1e35141215
Ref: library/math math hypot5141540
Ref: 1e45141540
Ref: library/math math sin5142055
Ref: e145142055
Ref: library/math math tan5142119
Ref: 1a355142119
Node: Angular conversion5142186
Ref: library/math angular-conversion5142333
Ref: 1a365142333
Ref: library/math math degrees5142388
Ref: 1a375142388
Ref: library/math math radians5142467
Ref: 1a385142467
Node: Hyperbolic functions5142546
Ref: library/math hyperbolic-functions5142687
Ref: 1a395142687
Ref: library/math math acosh5142859
Ref: d445142859
Ref: library/math math asinh5142938
Ref: d455142938
Ref: library/math math atanh5143015
Ref: d465143015
Ref: library/math math cosh5143095
Ref: 1a3a5143095
Ref: library/math math sinh5143165
Ref: 1a3b5143165
Ref: library/math math tanh5143233
Ref: 1a3c5143233
Ref: Hyperbolic functions-Footnote-15143340
Node: Special functions5143398
Ref: library/math special-functions5143533
Ref: 1a3d5143533
Ref: library/math math erf5143586
Ref: 4575143586
Ref: library/math math erfc5144002
Ref: 4585144002
Ref: library/math math gamma5144297
Ref: b6e5144297
Ref: library/math math lgamma5144392
Ref: b6f5144392
Ref: Special functions-Footnote-15144573
Ref: Special functions-Footnote-25144626
Ref: Special functions-Footnote-35144718
Ref: Special functions-Footnote-45144771
Ref: Special functions-Footnote-55144830
Node: Constants<2>5144883
Ref: library/math constants5144989
Ref: 1a3e5144989
Ref: library/math math pi5145026
Ref: 1a3f5145026
Ref: library/math math e5145126
Ref: 1a405145126
Ref: library/math math tau5145224
Ref: 1a415145224
Ref: library/math math inf5145601
Ref: 52d5145601
Ref: library/math math nan5145788
Ref: 52e5145788
Ref: Constants<2>-Footnote-15147111
Ref: Constants<2>-Footnote-25147163
Node: cmath --- Mathematical functions for complex numbers5147191
Ref: library/cmath doc5147411
Ref: 1a425147411
Ref: library/cmath cmath-mathematical-functions-for-complex-numbers5147411
Ref: 1a435147411
Ref: library/cmath module-cmath5147411
Ref: 195147411
Node: Conversions to and from polar coordinates5148705
Ref: library/cmath conversions-to-and-from-polar-coordinates5148878
Ref: 1a445148878
Ref: library/cmath cmath phase5149730
Ref: 1a455149730
Ref: library/cmath cmath polar5150637
Ref: 1a465150637
Ref: library/cmath cmath rect5150888
Ref: 1a475150888
Node: Power and logarithmic functions<2>5151060
Ref: library/cmath power-and-logarithmic-functions5151268
Ref: 1a485151268
Ref: library/cmath cmath exp5151349
Ref: 1a495151349
Ref: library/cmath cmath log5151468
Ref: 1a4a5151468
Ref: library/cmath cmath log105151739
Ref: 1a4b5151739
Ref: library/cmath cmath sqrt5151868
Ref: 1a4c5151868
Node: Trigonometric functions<2>5151990
Ref: library/cmath trigonometric-functions5152180
Ref: 1a4d5152180
Ref: library/cmath cmath acos5152245
Ref: 1a4e5152245
Ref: library/cmath cmath asin5152512
Ref: 1a4f5152512
Ref: library/cmath cmath atan5152633
Ref: 1a505152633
Ref: library/cmath cmath cos5152935
Ref: 1a515152935
Ref: library/cmath cmath sin5152994
Ref: 1a525152994
Ref: library/cmath cmath tan5153051
Ref: 1a535153051
Node: Hyperbolic functions<2>5153111
Ref: library/cmath hyperbolic-functions5153291
Ref: 1a545153291
Ref: library/cmath cmath acosh5153350
Ref: 1a555153350
Ref: library/cmath cmath asinh5153540
Ref: 1a565153540
Ref: library/cmath cmath atanh5153855
Ref: 1a575153855
Ref: library/cmath cmath cosh5154152
Ref: 1a585154152
Ref: library/cmath cmath sinh5154223
Ref: 1a595154223
Ref: library/cmath cmath tanh5154292
Ref: 1a5a5154292
Node: Classification functions5154364
Ref: library/cmath classification-functions5154530
Ref: 1a5b5154530
Ref: library/cmath cmath isfinite5154597
Ref: 1a5c5154597
Ref: library/cmath cmath isinf5154765
Ref: 1a5d5154765
Ref: library/cmath cmath isnan5154914
Ref: 1a5e5154914
Ref: library/cmath cmath isclose5155057
Ref: 68c5155057
Ref: Classification functions-Footnote-15156435
Node: Constants<3>5156484
Ref: library/cmath constants5156618
Ref: 1a5f5156618
Ref: library/cmath cmath pi5156655
Ref: 1a605156655
Ref: library/cmath cmath e5156725
Ref: 1a615156725
Ref: library/cmath cmath tau5156793
Ref: 52a5156793
Ref: library/cmath cmath inf5156888
Ref: 52b5156888
Ref: library/cmath cmath infj5157008
Ref: 52f5157008
Ref: library/cmath cmath nan5157187
Ref: 52c5157187
Ref: library/cmath cmath nanj5157323
Ref: 5305157323
Node: decimal --- Decimal fixed point and floating point arithmetic5158731
Ref: library/decimal doc5158950
Ref: 1a625158950
Ref: library/decimal decimal-decimal-fixed-point-and-floating-point-arithmetic5158950
Ref: 1a635158950
Ref: library/decimal module-decimal5158950
Ref: 365158950
Ref: decimal --- Decimal fixed point and floating point arithmetic-Footnote-15164062
Ref: decimal --- Decimal fixed point and floating point arithmetic-Footnote-25164128
Node: Quick-start Tutorial5164181
Ref: library/decimal decimal-tutorial5164323
Ref: 1a735164323
Ref: library/decimal quick-start-tutorial5164323
Ref: 1a745164323
Node: Decimal objects5171528
Ref: library/decimal decimal-decimal5171694
Ref: 1a775171694
Ref: library/decimal decimal-objects5171694
Ref: 1a785171694
Ref: library/decimal decimal Decimal5171743
Ref: 1895171743
Ref: library/decimal decimal Decimal adjusted5176829
Ref: 1a795176829
Ref: library/decimal decimal Decimal as_integer_ratio5177186
Ref: 5405177186
Ref: library/decimal decimal Decimal as_tuple5177629
Ref: 1a7a5177629
Ref: library/decimal decimal Decimal canonical5177793
Ref: 1a7b5177793
Ref: library/decimal decimal Decimal compare5178038
Ref: 1a7c5178038
Ref: library/decimal decimal Decimal compare_signal5178477
Ref: 1a7d5178477
Ref: library/decimal decimal Decimal compare_total5178795
Ref: 1a7e5178795
Ref: library/decimal decimal Decimal compare_total_mag5180078
Ref: 1a7f5180078
Ref: library/decimal decimal Decimal conjugate5180689
Ref: 1a805180689
Ref: library/decimal decimal Decimal copy_abs5180828
Ref: 1a815180828
Ref: library/decimal decimal Decimal copy_negate5181048
Ref: 1a825181048
Ref: library/decimal decimal Decimal copy_sign5181265
Ref: 1a835181265
Ref: library/decimal decimal Decimal exp5181808
Ref: 9f25181808
Ref: library/decimal decimal Decimal from_float5182248
Ref: b855182248
Ref: library/decimal decimal Decimal fma5183356
Ref: 1a845183356
Ref: library/decimal decimal Decimal is_canonical5183606
Ref: 1a855183606
Ref: library/decimal decimal Decimal is_finite5183887
Ref: 1a865183887
Ref: library/decimal decimal Decimal is_infinite5184068
Ref: 1a875184068
Ref: library/decimal decimal Decimal is_nan5184241
Ref: 1a885184241
Ref: library/decimal decimal Decimal is_normal5184399
Ref: 1a895184399
Ref: library/decimal decimal Decimal is_qnan5184629
Ref: 1a8a5184629
Ref: library/decimal decimal Decimal is_signed5184774
Ref: 1a8b5184774
Ref: library/decimal decimal Decimal is_snan5184983
Ref: 1a8c5184983
Ref: library/decimal decimal Decimal is_subnormal5185131
Ref: 1a8d5185131
Ref: library/decimal decimal Decimal is_zero5185291
Ref: 1a8e5185291
Ref: library/decimal decimal Decimal ln5185453
Ref: 9f35185453
Ref: library/decimal decimal Decimal log105185667
Ref: 1a8f5185667
Ref: library/decimal decimal Decimal logb5185876
Ref: 1a905185876
Ref: library/decimal decimal Decimal logical_and5186269
Ref: 1a915186269
Ref: library/decimal decimal Decimal logical_invert5186540
Ref: 1a935186540
Ref: library/decimal decimal Decimal logical_or5186725
Ref: 1a945186725
Ref: library/decimal decimal Decimal logical_xor5186993
Ref: 1a955186993
Ref: library/decimal decimal Decimal max5187267
Ref: 1a965187267
Ref: library/decimal decimal Decimal max_mag5187577
Ref: 1a975187577
Ref: library/decimal decimal Decimal min5187764
Ref: 1a985187764
Ref: library/decimal decimal Decimal min_mag5188074
Ref: 1a995188074
Ref: library/decimal decimal Decimal next_minus5188261
Ref: 1a9a5188261
Ref: library/decimal decimal Decimal next_plus5188505
Ref: 1a9b5188505
Ref: library/decimal decimal Decimal next_toward5188748
Ref: 1a9c5188748
Ref: library/decimal decimal Decimal normalize5189121
Ref: 1a9d5189121
Ref: library/decimal decimal Decimal number_class5189583
Ref: 1a9e5189583
Ref: library/decimal decimal Decimal quantize5190759
Ref: 9f65190759
Ref: library/decimal decimal Decimal radix5192058
Ref: 1a9f5192058
Ref: library/decimal decimal Decimal remainder_near5192281
Ref: 1aa05192281
Ref: library/decimal decimal Decimal rotate5193131
Ref: 1aa15193131
Ref: library/decimal decimal Decimal same_quantum5193810
Ref: 1aa25193810
Ref: library/decimal decimal Decimal scaleb5194228
Ref: 1aa35194228
Ref: library/decimal decimal Decimal shift5194485
Ref: 1aa45194485
Ref: library/decimal decimal Decimal sqrt5195097
Ref: 1aa55195097
Ref: library/decimal decimal Decimal to_eng_string5195210
Ref: 1aa65195210
Ref: library/decimal decimal Decimal to_integral5195692
Ref: 1aa75195692
Ref: library/decimal decimal Decimal to_integral_exact5195928
Ref: 1aa95195928
Ref: library/decimal decimal Decimal to_integral_value5196364
Ref: 1aa85196364
Node: Logical operands5196724
Ref: library/decimal logical-operands5196792
Ref: 1aaa5196792
Ref: library/decimal logical-operands-label5196792
Ref: 1a925196792
Node: Context objects5197139
Ref: library/decimal context-objects5197297
Ref: 1aab5197297
Ref: library/decimal decimal-context5197297
Ref: 1aac5197297
Ref: library/decimal decimal getcontext5197681
Ref: 1a755197681
Ref: library/decimal decimal setcontext5197772
Ref: 1a765197772
Ref: library/decimal decimal localcontext5198004
Ref: 16e25198004
Ref: library/decimal decimal BasicContext5198927
Ref: 9ee5198927
Ref: library/decimal decimal ExtendedContext5199380
Ref: 9ef5199380
Ref: library/decimal decimal DefaultContext5200014
Ref: 9ed5200014
Ref: library/decimal decimal Context5201117
Ref: 9f55201117
Ref: library/decimal decimal Context clear_flags5204037
Ref: 1ab15204037
Ref: library/decimal decimal Context clear_traps5204123
Ref: 1ab25204123
Ref: library/decimal decimal Context copy5204238
Ref: 1ab35204238
Ref: library/decimal decimal Context copy_decimal5204316
Ref: 1ab45204316
Ref: library/decimal decimal Context create_decimal5204413
Ref: 9f15204413
Ref: library/decimal decimal Context create_decimal_from_float5205523
Ref: 1ab55205523
Ref: library/decimal decimal Context Etiny5206290
Ref: 1ab65206290
Ref: library/decimal decimal Context Etop5206526
Ref: 1ab75206526
Ref: library/decimal decimal Context abs5207038
Ref: 1ab85207038
Ref: library/decimal decimal Context add5207116
Ref: 1ab95207116
Ref: library/decimal decimal Context canonical5207193
Ref: ca25207193
Ref: library/decimal decimal Context compare5207279
Ref: 1aba5207279
Ref: library/decimal decimal Context compare_signal5207363
Ref: 1abb5207363
Ref: library/decimal decimal Context compare_total5207473
Ref: 1abc5207473
Ref: library/decimal decimal Context compare_total_mag5207588
Ref: 1abd5207588
Ref: library/decimal decimal Context copy_abs5207732
Ref: 1abe5207732
Ref: library/decimal decimal Context copy_negate5207826
Ref: 1abf5207826
Ref: library/decimal decimal Context copy_sign5207923
Ref: 1ac05207923
Ref: library/decimal decimal Context divide5208008
Ref: 1ac15208008
Ref: library/decimal decimal Context divide_int5208084
Ref: 1ac25208084
Ref: library/decimal decimal Context divmod5208189
Ref: 1ac35208189
Ref: library/decimal decimal Context exp5208312
Ref: 1ac45208312
Ref: library/decimal decimal Context fma5208377
Ref: 1ac55208377
Ref: library/decimal decimal Context is_canonical5208467
Ref: ca35208467
Ref: library/decimal decimal Context is_finite5208590
Ref: 1ac65208590
Ref: library/decimal decimal Context is_infinite5208707
Ref: 1ac75208707
Ref: library/decimal decimal Context is_nan5208828
Ref: 1ac85208828
Ref: library/decimal decimal Context is_normal5208960
Ref: 1ac95208960
Ref: library/decimal decimal Context is_qnan5209096
Ref: 1aca5209096
Ref: library/decimal decimal Context is_signed5209226
Ref: 1acb5209226
Ref: library/decimal decimal Context is_snan5209345
Ref: 1acc5209345
Ref: library/decimal decimal Context is_subnormal5209479
Ref: 1acd5209479
Ref: library/decimal decimal Context is_zero5209602
Ref: 1ace5209602
Ref: library/decimal decimal Context ln5209717
Ref: 1acf5209717
Ref: library/decimal decimal Context log105209806
Ref: 1ad05209806
Ref: library/decimal decimal Context logb5209889
Ref: 1ad15209889
Ref: library/decimal decimal Context logical_and5209995
Ref: 1ad25209995
Ref: library/decimal decimal Context logical_invert5210128
Ref: 1ad35210128
Ref: library/decimal decimal Context logical_or5210212
Ref: 1ad45210212
Ref: library/decimal decimal Context logical_xor5210343
Ref: 1ad55210343
Ref: library/decimal decimal Context max5210476
Ref: 1ad65210476
Ref: library/decimal decimal Context max_mag5210579
Ref: 1ad75210579
Ref: library/decimal decimal Context min5210686
Ref: 1ad85210686
Ref: library/decimal decimal Context min_mag5210789
Ref: 1ad95210789
Ref: library/decimal decimal Context minus5210896
Ref: 1ada5210896
Ref: library/decimal decimal Context multiply5211015
Ref: 1adb5211015
Ref: library/decimal decimal Context next_minus5211101
Ref: 1adc5211101
Ref: library/decimal decimal Context next_plus5211210
Ref: 1add5211210
Ref: library/decimal decimal Context next_toward5211318
Ref: 1ade5211318
Ref: library/decimal decimal Context normalize5211433
Ref: 1adf5211433
Ref: library/decimal decimal Context number_class5211516
Ref: 1ae05211516
Ref: library/decimal decimal Context plus5211611
Ref: 1ae15211611
Ref: library/decimal decimal Context power5211834
Ref: 1ae25211834
Ref: library/decimal decimal Context quantize5213662
Ref: 1ae35213662
Ref: library/decimal decimal Context radix5213791
Ref: 1ae45213791
Ref: library/decimal decimal Context remainder5213875
Ref: 1ae55213875
Ref: library/decimal decimal Context remainder_near5214076
Ref: 1ae65214076
Ref: library/decimal decimal Context rotate5214302
Ref: 1ae75214302
Ref: library/decimal decimal Context same_quantum5214393
Ref: 1ae85214393
Ref: library/decimal decimal Context scaleb5214511
Ref: 1ae95214511
Ref: library/decimal decimal Context shift5214635
Ref: 1aea5214635
Ref: library/decimal decimal Context sqrt5214725
Ref: 1aeb5214725
Ref: library/decimal decimal Context subtract5214828
Ref: 1aec5214828
Ref: library/decimal decimal Context to_eng_string5214922
Ref: 1aed5214922
Ref: library/decimal decimal Context to_integral_exact5215292
Ref: 1aee5215292
Ref: library/decimal decimal Context to_sci_string5215371
Ref: 1aef5215371
Node: Constants<4>5215481
Ref: library/decimal constants5215638
Ref: 1af05215638
Ref: library/decimal decimal-rounding-modes5215638
Ref: 1af15215638
Ref: library/decimal decimal MAX_PREC5216075
Ref: 1aad5216075
Ref: library/decimal decimal MAX_EMAX5216210
Ref: 1ab05216210
Ref: library/decimal decimal MIN_EMIN5216345
Ref: 1aaf5216345
Ref: library/decimal decimal MIN_ETINY5216481
Ref: 1af25216481
Ref: library/decimal decimal HAVE_THREADS5216609
Ref: 9eb5216609
Ref: library/decimal decimal HAVE_CONTEXTVAR5216751
Ref: 1af35216751
Node: Rounding modes5217104
Ref: library/decimal rounding-modes5217253
Ref: 1aae5217253
Ref: library/decimal decimal ROUND_CEILING5217300
Ref: 1a645217300
Ref: library/decimal decimal ROUND_DOWN5217369
Ref: 1a655217369
Ref: library/decimal decimal ROUND_FLOOR5217425
Ref: 1a665217425
Ref: library/decimal decimal ROUND_HALF_DOWN5217493
Ref: 1a675217493
Ref: library/decimal decimal ROUND_HALF_EVEN5217581
Ref: 1a685217581
Ref: library/decimal decimal ROUND_HALF_UP5217680
Ref: 1a695217680
Ref: library/decimal decimal ROUND_UP5217768
Ref: 1a6a5217768
Ref: library/decimal decimal ROUND_05UP5217824
Ref: 1a6b5217824
Node: Signals5217982
Ref: library/decimal decimal-signals5218139
Ref: 1af45218139
Ref: library/decimal signals5218139
Ref: 1af55218139
Ref: library/decimal decimal Clamped5218856
Ref: 1a6c5218856
Ref: library/decimal decimal DecimalException5219151
Ref: 1af65219151
Ref: library/decimal decimal DivisionByZero5219276
Ref: 1a6d5219276
Ref: library/decimal decimal Inexact5219615
Ref: 1a6e5219615
Ref: library/decimal decimal InvalidOperation5219891
Ref: 9f05219891
Ref: library/decimal decimal Overflow5220333
Ref: 1a715220333
Ref: library/decimal decimal Rounded5220737
Ref: 1a6f5220737
Ref: library/decimal decimal Subnormal5221076
Ref: 1a705221076
Ref: library/decimal decimal Underflow5221299
Ref: 1a725221299
Ref: library/decimal decimal FloatOperation5221525
Ref: 9ea5221525
Node: Floating Point Notes5222798
Ref: library/decimal decimal-notes5222961
Ref: 1af75222961
Ref: library/decimal floating-point-notes5222961
Ref: 1af85222961
Node: Mitigating round-off error with increased precision5223105
Ref: library/decimal mitigating-round-off-error-with-increased-precision5223236
Ref: 1af95223236
Node: Special values5224925
Ref: library/decimal special-values5225056
Ref: 1afa5225056
Node: Working with threads5228173
Ref: library/decimal decimal-threads5228336
Ref: 1afb5228336
Ref: library/decimal working-with-threads5228336
Ref: 1afc5228336
Node: Recipes5229709
Ref: library/decimal decimal-recipes5229863
Ref: 1afd5229863
Ref: library/decimal recipes5229863
Ref: 1afe5229863
Node: Decimal FAQ5234708
Ref: library/decimal decimal-faq5234833
Ref: 1aff5234833
Ref: library/decimal id15234833
Ref: 1b005234833
Ref: Decimal FAQ-Footnote-15241138
Ref: Decimal FAQ-Footnote-25241205
Ref: Decimal FAQ-Footnote-35241263
Node: fractions --- Rational numbers5241366
Ref: library/fractions doc5241574
Ref: 1b015241574
Ref: library/fractions fractions-rational-numbers5241574
Ref: 1b025241574
Ref: library/fractions module-fractions5241574
Ref: 835241574
Ref: library/fractions fractions Fraction5241954
Ref: 1865241954
Ref: library/fractions fractions Fraction numerator5245105
Ref: 1b045245105
Ref: library/fractions fractions Fraction denominator5245186
Ref: 1b055245186
Ref: library/fractions fractions Fraction as_integer_ratio5245271
Ref: 1b065245271
Ref: library/fractions fractions Fraction from_float5245467
Ref: b865245467
Ref: library/fractions fractions Fraction from_decimal5245934
Ref: b875245934
Ref: library/fractions fractions Fraction limit_denominator5246341
Ref: 1b035246341
Ref: library/fractions fractions Fraction __floor__5247221
Ref: 1b075247221
Ref: library/fractions fractions Fraction __ceil__5247527
Ref: 1b085247527
Ref: library/fractions fractions Fraction __round__5247713
Ref: 1b095247713
Ref: library/fractions fractions gcd5248195
Ref: 71c5248195
Ref: fractions --- Rational numbers-Footnote-15248784
Node: random --- Generate pseudo-random numbers5248852
Ref: library/random doc5249032
Ref: 1b0a5249032
Ref: library/random module-random5249032
Ref: dd5249032
Ref: library/random random-generate-pseudo-random-numbers5249032
Ref: 1b0b5249032
Ref: random --- Generate pseudo-random numbers-Footnote-15252016
Ref: random --- Generate pseudo-random numbers-Footnote-25252081
Node: Bookkeeping functions5252134
Ref: library/random bookkeeping-functions5252264
Ref: 1b0f5252264
Ref: library/random random seed5252325
Ref: c0d5252325
Ref: library/random random getstate5253204
Ref: 1b105253204
Ref: library/random random setstate5253400
Ref: 1b115253400
Ref: library/random random getrandbits5253676
Ref: 9385253676
Node: Functions for integers5254034
Ref: library/random functions-for-integers5254196
Ref: 1b125254196
Ref: library/random random randrange5254259
Ref: bc05254259
Ref: library/random random randint5254948
Ref: bc15254948
Node: Functions for sequences5255087
Ref: library/random functions-for-sequences5255253
Ref: 1b135255253
Ref: library/random random choice5255318
Ref: bc25255318
Ref: library/random random choices5255471
Ref: 5795255471
Ref: library/random random shuffle5257341
Ref: bc35257341
Ref: library/random random sample5258105
Ref: bc45258105
Node: Real-valued distributions5259172
Ref: library/random real-valued-distributions5259337
Ref: 1b145259337
Ref: library/random random random5259676
Ref: 1b0c5259676
Ref: library/random random uniform5259787
Ref: 1b155259787
Ref: library/random random triangular5260124
Ref: 1b165260124
Ref: library/random random betavariate5260479
Ref: 1b175260479
Ref: library/random random expovariate5260665
Ref: 1b185260665
Ref: library/random random gammavariate5261038
Ref: 1b195261038
Ref: library/random random gauss5261438
Ref: 1b1a5261438
Ref: library/random random lognormvariate5261660
Ref: 1b1c5261660
Ref: library/random random normalvariate5261957
Ref: 1b1b5261957
Ref: library/random random vonmisesvariate5262093
Ref: 1b1d5262093
Ref: library/random random paretovariate5262433
Ref: 1b1e5262433
Ref: library/random random weibullvariate5262535
Ref: 1b1f5262535
Node: Alternative Generator5262684
Ref: library/random alternative-generator5262850
Ref: 1b205262850
Ref: library/random random Random5262911
Ref: 1b0d5262911
Ref: library/random random SystemRandom5263061
Ref: 1b0e5263061
Node: Notes on Reproducibility5263559
Ref: library/random notes-on-reproducibility5263720
Ref: 1b215263720
Node: Examples and Recipes5264418
Ref: library/random examples-and-recipes5264549
Ref: 1b225264549
Ref: library/random random-examples5264549
Ref: b5d5264549
Ref: Examples and Recipes-Footnote-15269977
Ref: Examples and Recipes-Footnote-25270042
Ref: Examples and Recipes-Footnote-35270123
Ref: Examples and Recipes-Footnote-45270169
Ref: Examples and Recipes-Footnote-55270221
Ref: Examples and Recipes-Footnote-65270276
Ref: Examples and Recipes-Footnote-75270352
Ref: Examples and Recipes-Footnote-85270387
Ref: Examples and Recipes-Footnote-95270465
Node: statistics --- 數學統計函式5270500
Ref: library/statistics doc5270641
Ref: 1b235270641
Ref: library/statistics module-statistics5270641
Ref: f65270641
Ref: library/statistics statistics-mathematical-statistics-functions5270641
Ref: 1b245270641
Ref: statistics --- 數學統計函式-Footnote-15271913
Ref: statistics --- 數學統計函式-Footnote-25271982
Ref: statistics --- 數學統計函式-Footnote-35272008
Node: 平均值與中央位置量數5272039
Ref: library/statistics averages-and-measures-of-central-location5272171
Ref: 1b255272171
Node: 離度 spread 的測量5273670
Ref: library/statistics measures-of-spread5273823
Ref: 1b2a5273823
Node: 函式細節5274365
Ref: library/statistics function-details5274501
Ref: 1b2f5274501
Ref: library/statistics statistics mean5274691
Ref: 19a5274691
Ref: library/statistics statistics fmean5276293
Ref: 2285276293
Ref: library/statistics statistics geometric_mean5276702
Ref: 2295276702
Ref: library/statistics statistics harmonic_mean5277385
Ref: 5945277385
Ref: library/statistics statistics median5278851
Ref: 1b265278851
Ref: library/statistics statistics median_low5279840
Ref: 1b275279840
Ref: library/statistics statistics median_high5280479
Ref: 1b285280479
Ref: library/statistics statistics median_grouped5281115
Ref: 1b295281115
Ref: library/statistics statistics mode5282767
Ref: 2bc5282767
Ref: library/statistics statistics multimode5283922
Ref: 22a5283922
Ref: library/statistics statistics pstdev5284337
Ref: 1b2b5284337
Ref: library/statistics statistics pvariance5284635
Ref: 1b2c5284635
Ref: library/statistics statistics stdev5286901
Ref: 1b2d5286901
Ref: library/statistics statistics variance5287191
Ref: 1b2e5287191
Ref: library/statistics statistics quantiles5289456
Ref: 22b5289456
Ref: 函式細節-Footnote-15292212
Ref: 函式細節-Footnote-25292307
Node: Exceptions<2>5292387
Ref: library/statistics exceptions5292518
Ref: 1b315292518
Ref: library/statistics statistics StatisticsError5292589
Ref: 1b305292589
Node: NormalDist objects5292710
Ref: library/statistics normaldist-objects5292820
Ref: 1b325292820
Ref: library/statistics statistics NormalDist5293208
Ref: 22c5293208
Ref: library/statistics statistics NormalDist mean5293474
Ref: 1b335293474
Ref: library/statistics statistics NormalDist median5293592
Ref: 1b345293592
Ref: library/statistics statistics NormalDist mode5293703
Ref: 1b355293703
Ref: library/statistics statistics NormalDist stdev5293800
Ref: 1b365293800
Ref: library/statistics statistics NormalDist variance5293922
Ref: 1b375293922
Ref: library/statistics statistics NormalDist from_samples5294085
Ref: 1b385294085
Ref: library/statistics statistics NormalDist samples5294699
Ref: 1b395294699
Ref: library/statistics statistics NormalDist pdf5295110
Ref: 1b3a5295110
Ref: library/statistics statistics NormalDist cdf5295713
Ref: 1b3b5295713
Ref: library/statistics statistics NormalDist inv_cdf5295962
Ref: 1b3c5295962
Ref: library/statistics statistics NormalDist overlap5296407
Ref: 1b3d5296407
Ref: library/statistics statistics NormalDist quantiles5296669
Ref: 1b3e5296669
Ref: NormalDist objects-Footnote-15298334
Ref: NormalDist objects-Footnote-25298398
Ref: NormalDist objects-Footnote-35298458
Ref: NormalDist objects-Footnote-45298512
Ref: NormalDist objects-Footnote-55298569
Ref: NormalDist objects-Footnote-65298623
Ref: NormalDist objects-Footnote-75298668
Ref: NormalDist objects-Footnote-85298724
Ref: NormalDist objects-Footnote-95298781
Ref: NormalDist objects-Footnote-105298828
Ref: NormalDist objects-Footnote-115298896
Ref: NormalDist objects-Footnote-125298968
Ref: NormalDist objects-Footnote-135299025
Ref: NormalDist objects-Footnote-145299117
Ref: NormalDist objects-Footnote-155299164
Node: NormalDist Examples and Recipes5299249
Ref: library/statistics normaldist-examples-and-recipes5299335
Ref: 1b3f5299335
Ref: NormalDist Examples and Recipes-Footnote-15303905
Ref: NormalDist Examples and Recipes-Footnote-25303976
Ref: NormalDist Examples and Recipes-Footnote-35304023
Ref: NormalDist Examples and Recipes-Footnote-45304068
Ref: NormalDist Examples and Recipes-Footnote-55304125
Ref: NormalDist Examples and Recipes-Footnote-65304188
Ref: NormalDist Examples and Recipes-Footnote-75304269
Ref: NormalDist Examples and Recipes-Footnote-85304325
Node: 函式編程模組5304395
Ref: library/functional doc5304549
Ref: 1b405304549
Ref: library/functional functional-programming-modules5304549
Ref: 1b415304549
Node: itertools --- Functions creating iterators for efficient looping5305196
Ref: library/itertools doc5305395
Ref: 1b425305395
Ref: library/itertools itertools-functions-creating-iterators-for-efficient-looping5305395
Ref: 1b435305395
Ref: library/itertools module-itertools5305395
Ref: a45305395
Node: Itertool functions5315752
Ref: library/itertools itertool-functions5315897
Ref: 1b4a5315897
Ref: library/itertools itertools-functions5315897
Ref: 1b4b5315897
Ref: library/itertools itertools accumulate5316144
Ref: 1de5316144
Ref: library/itertools itertools chain5319640
Ref: 16085319640
Ref: library/itertools itertools chain from_iterable5320148
Ref: 1b455320148
Ref: library/itertools itertools combinations5320593
Ref: cab5320593
Ref: library/itertools itertools combinations_with_replacement5322564
Ref: c1e5322564
Ref: library/itertools itertools compress5324539
Ref: c1f5324539
Ref: library/itertools itertools count5325051
Ref: c205325051
Ref: library/itertools itertools cycle5325884
Ref: 1b445325884
Ref: library/itertools itertools dropwhile5326602
Ref: 1b465326602
Ref: library/itertools itertools filterfalse5327301
Ref: 15f15327301
Ref: library/itertools itertools groupby5327866
Ref: 1b475327866
Ref: library/itertools itertools islice5330600
Ref: 3a75330600
Ref: library/itertools itertools permutations5332684
Ref: ece5332684
Ref: library/itertools itertools product5335127
Ref: cac5335127
Ref: library/itertools itertools repeat5336501
Ref: 10b75336501
Ref: library/itertools itertools starmap5337369
Ref: a2d5337369
Ref: library/itertools itertools takewhile5338049
Ref: 1b485338049
Ref: library/itertools itertools tee5338489
Ref: 1b495338489
Ref: library/itertools itertools zip_longest5340216
Ref: c365340216
Ref: Itertool functions-Footnote-15341690
Node: Itertools Recipes5341748
Ref: library/itertools id15341893
Ref: 1b4d5341893
Ref: library/itertools itertools-recipes5341893
Ref: bfa5341893
Ref: Itertools Recipes-Footnote-15350929
Node: functools --- Higher-order functions and operations on callable objects5350978
Ref: library/functools doc5351230
Ref: 1b4e5351230
Ref: library/functools functools-higher-order-functions-and-operations-on-callable-objects5351230
Ref: 1b4f5351230
Ref: library/functools module-functools5351230
Ref: 855351230
Ref: library/functools functools cached_property5351773
Ref: 1c95351773
Ref: library/functools functools cmp_to_key5353076
Ref: b5b5353076
Ref: library/functools functools lru_cache5354114
Ref: 1c85354114
Ref: library/functools functools total_ordering5358192
Ref: 8505358192
Ref: library/functools functools partial5360089
Ref: 7cd5360089
Ref: library/functools functools partialmethod5361466
Ref: 29d5361466
Ref: library/functools functools reduce5363209
Ref: c745363209
Ref: library/functools functools singledispatch5364414
Ref: 38f5364414
Ref: library/functools functools singledispatchmethod5368604
Ref: 1ca5368604
Ref: library/functools functools update_wrapper5370224
Ref: 95f5370224
Ref: library/functools functools wraps5372642
Ref: 86f5372642
Ref: functools --- Higher-order functions and operations on callable objects-Footnote-15373938
Ref: functools --- Higher-order functions and operations on callable objects-Footnote-25374006
Ref: functools --- Higher-order functions and operations on callable objects-Footnote-35374070
Ref: functools --- Higher-order functions and operations on callable objects-Footnote-45374125
Ref: functools --- Higher-order functions and operations on callable objects-Footnote-55374183
Node: partial Objects5374226
Ref: library/functools id15374349
Ref: 1b515374349
Ref: library/functools partial-objects5374349
Ref: 1b505374349
Ref: library/functools functools partial func5374530
Ref: 1b525374530
Ref: library/functools functools partial args5374716
Ref: 1b535374716
Ref: library/functools functools partial keywords5374885
Ref: 1b545374885
Node: operator --- Standard operators as functions5375444
Ref: library/operator doc5375623
Ref: 1b555375623
Ref: library/operator module-operator5375623
Ref: c35375623
Ref: library/operator operator-standard-operators-as-functions5375623
Ref: 1b565375623
Ref: library/operator operator lt5376556
Ref: 1b575376556
Ref: library/operator operator le5376587
Ref: 1b585376587
Ref: library/operator operator eq5376618
Ref: 1b595376618
Ref: library/operator operator ne5376649
Ref: 1b5a5376649
Ref: library/operator operator ge5376680
Ref: 1b5b5376680
Ref: library/operator operator gt5376711
Ref: 1b5c5376711
Ref: library/operator operator __lt__5376742
Ref: 1b5d5376742
Ref: library/operator operator __le__5376777
Ref: 1b5e5376777
Ref: library/operator operator __eq__5376812
Ref: 1b5f5376812
Ref: library/operator operator __ne__5376847
Ref: 1b605376847
Ref: library/operator operator __ge__5376882
Ref: 1b615376882
Ref: library/operator operator __gt__5376917
Ref: 1b625376917
Ref: library/operator operator not_5377651
Ref: 1b635377651
Ref: library/operator operator __not__5377683
Ref: 1b645377683
Ref: library/operator operator truth5378002
Ref: 1b655378002
Ref: library/operator operator is_5378190
Ref: 1b665378190
Ref: library/operator operator is_not5378274
Ref: 1b675378274
Ref: library/operator operator abs5378429
Ref: 1b685378429
Ref: library/operator operator __abs__5378460
Ref: 1b695378460
Ref: library/operator operator add5378538
Ref: 1b6a5378538
Ref: library/operator operator __add__5378570
Ref: 1b6b5378570
Ref: library/operator operator and_5378658
Ref: 1b6c5378658
Ref: library/operator operator __and__5378691
Ref: 1b6d5378691
Ref: library/operator operator floordiv5378773
Ref: 1b6e5378773
Ref: library/operator operator __floordiv__5378810
Ref: 1b6f5378810
Ref: library/operator operator index5378879
Ref: 14865378879
Ref: library/operator operator __index__5378910
Ref: 1b705378910
Ref: library/operator operator inv5379024
Ref: 1b715379024
Ref: library/operator operator invert5379055
Ref: 1b725379055
Ref: library/operator operator __inv__5379089
Ref: 1b735379089
Ref: library/operator operator __invert__5379124
Ref: 1b745379124
Ref: library/operator operator lshift5379257
Ref: 1b755379257
Ref: library/operator operator __lshift__5379292
Ref: 1b765379292
Ref: library/operator operator mod5379370
Ref: 1b775379370
Ref: library/operator operator __mod__5379402
Ref: 1b785379402
Ref: library/operator operator mul5379465
Ref: 1b4c5379465
Ref: library/operator operator __mul__5379497
Ref: 1b795379497
Ref: library/operator operator matmul5379585
Ref: 7225379585
Ref: library/operator operator __matmul__5379620
Ref: 1b7a5379620
Ref: library/operator operator neg5379710
Ref: 1b7b5379710
Ref: library/operator operator __neg__5379741
Ref: 1b7c5379741
Ref: library/operator operator or_5379818
Ref: 1b7d5379818
Ref: library/operator operator __or__5379850
Ref: 1b7e5379850
Ref: library/operator operator pos5379930
Ref: 1b7f5379930
Ref: library/operator operator __pos__5379961
Ref: 1b805379961
Ref: library/operator operator pow5380039
Ref: 1b815380039
Ref: library/operator operator __pow__5380071
Ref: 1b825380071
Ref: library/operator operator rshift5380160
Ref: 1b835380160
Ref: library/operator operator __rshift__5380195
Ref: 1b845380195
Ref: library/operator operator sub5380274
Ref: 1b855380274
Ref: library/operator operator __sub__5380306
Ref: 1b865380306
Ref: library/operator operator truediv5380369
Ref: 1b875380369
Ref: library/operator operator __truediv__5380405
Ref: 1b885380405
Ref: library/operator operator xor5380548
Ref: 1b895380548
Ref: library/operator operator __xor__5380580
Ref: 1b8a5380580
Ref: library/operator operator concat5380751
Ref: 1b8b5380751
Ref: library/operator operator __concat__5380786
Ref: 1b8c5380786
Ref: library/operator operator contains5380878
Ref: f095380878
Ref: library/operator operator __contains__5380915
Ref: 1b8d5380915
Ref: library/operator operator countOf5381042
Ref: f0b5381042
Ref: library/operator operator delitem5381133
Ref: 1b8e5381133
Ref: library/operator operator __delitem__5381169
Ref: 1b8f5381169
Ref: library/operator operator getitem5381254
Ref: 1b905381254
Ref: library/operator operator __getitem__5381290
Ref: 1b915381290
Ref: library/operator operator indexOf5381375
Ref: f0a5381375
Ref: library/operator operator setitem5381477
Ref: 1b925381477
Ref: library/operator operator __setitem__5381516
Ref: 1b935381516
Ref: library/operator operator length_hint5381608
Ref: 8825381608
Ref: library/operator operator attrgetter5382176
Ref: 7205382176
Ref: library/operator operator itemgetter5383473
Ref: 2625383473
Ref: library/operator operator methodcaller5385227
Ref: 7215385227
Ref: operator --- Standard operators as functions-Footnote-15386024
Node: Mapping Operators to Functions5386091
Ref: library/operator mapping-operators-to-functions5386229
Ref: 1b945386229
Ref: library/operator operator-map5386229
Ref: 1b955386229
Node: In-place Operators5393653
Ref: library/operator in-place-operators5393791
Ref: 1b965393791
Ref: library/operator operator iadd5395095
Ref: 1b985395095
Ref: library/operator operator __iadd__5395128
Ref: 1b995395128
Ref: library/operator operator iand5395224
Ref: 1b9a5395224
Ref: library/operator operator __iand__5395257
Ref: 1b9b5395257
Ref: library/operator operator iconcat5395353
Ref: 1b9c5395353
Ref: library/operator operator __iconcat__5395389
Ref: 1b9d5395389
Ref: library/operator operator ifloordiv5395522
Ref: 1b9e5395522
Ref: library/operator operator __ifloordiv__5395560
Ref: 1b9f5395560
Ref: library/operator operator ilshift5395667
Ref: 1ba05395667
Ref: library/operator operator __ilshift__5395703
Ref: 1ba15395703
Ref: library/operator operator imod5395806
Ref: 1ba25395806
Ref: library/operator operator __imod__5395839
Ref: 1ba35395839
Ref: library/operator operator imul5395935
Ref: 1ba45395935
Ref: library/operator operator __imul__5395968
Ref: 1ba55395968
Ref: library/operator operator imatmul5396064
Ref: 7235396064
Ref: library/operator operator __imatmul__5396100
Ref: 1ba65396100
Ref: library/operator operator ior5396226
Ref: 1ba75396226
Ref: library/operator operator __ior__5396258
Ref: 1ba85396258
Ref: library/operator operator ipow5396352
Ref: 1ba95396352
Ref: library/operator operator __ipow__5396385
Ref: 1baa5396385
Ref: library/operator operator irshift5396482
Ref: 1bab5396482
Ref: library/operator operator __irshift__5396518
Ref: 1bac5396518
Ref: library/operator operator isub5396621
Ref: 1bad5396621
Ref: library/operator operator __isub__5396654
Ref: 1bae5396654
Ref: library/operator operator itruediv5396750
Ref: 1baf5396750
Ref: library/operator operator __itruediv__5396787
Ref: 1bb05396787
Ref: library/operator operator ixor5396891
Ref: 1bb15396891
Ref: library/operator operator __ixor__5396924
Ref: 1bb25396924
Node: 檔案與目錄存取5397020
Ref: library/filesys doc5397169
Ref: 1bb35397169
Ref: library/filesys file-and-directory-access5397169
Ref: 1bb45397169
Ref: library/filesys filesys5397169
Ref: 1bb55397169
Node: pathlib --- Object-oriented filesystem paths5398389
Ref: library/pathlib doc5398541
Ref: 1bb65398541
Ref: library/pathlib module-pathlib5398541
Ref: c95398541
Ref: library/pathlib pathlib-object-oriented-filesystem-paths5398541
Ref: 1bb75398541
Ref: pathlib --- Object-oriented filesystem paths-Footnote-15400236
Ref: pathlib --- Object-oriented filesystem paths-Footnote-25400302
Node: Basic use5400351
Ref: library/pathlib basic-use5400460
Ref: 1bbc5400460
Node: Pure paths5401406
Ref: library/pathlib id15401538
Ref: 1bbd5401538
Ref: library/pathlib pure-paths5401538
Ref: 1bb85401538
Ref: library/pathlib pathlib PurePath5401753
Ref: 10465401753
Ref: library/pathlib pathlib PurePosixPath5403928
Ref: 1bbe5403928
Ref: library/pathlib pathlib PureWindowsPath5404223
Ref: 1bbb5404223
Node: General properties5404817
Ref: library/pathlib general-properties5404903
Ref: 1bbf5404903
Node: Operators<2>5405755
Ref: library/pathlib operators5405876
Ref: 1bc05405876
Node: Accessing individual parts5407087
Ref: library/pathlib accessing-individual-parts5407212
Ref: 1bc15407212
Ref: library/pathlib pathlib PurePath parts5407371
Ref: 1bc25407371
Node: Methods and properties5407769
Ref: library/pathlib methods-and-properties5407873
Ref: 1bc35407873
Ref: library/pathlib pathlib PurePath drive5407996
Ref: 1bc45407996
Ref: library/pathlib pathlib PurePath root5408414
Ref: 1bc55408414
Ref: library/pathlib pathlib PurePath anchor5408802
Ref: 1bc65408802
Ref: library/pathlib pathlib PurePath parents5409164
Ref: 1bc75409164
Ref: library/pathlib pathlib PurePath parent5409528
Ref: 1bc85409528
Ref: library/pathlib pathlib PurePath name5410345
Ref: 1bca5410345
Ref: library/pathlib pathlib PurePath suffix5410733
Ref: 1bcb5410733
Ref: library/pathlib pathlib PurePath suffixes5411026
Ref: 1bcc5411026
Ref: library/pathlib pathlib PurePath stem5411336
Ref: 1bcd5411336
Ref: library/pathlib pathlib PurePath as_posix5411630
Ref: 1bce5411630
Ref: library/pathlib pathlib PurePath as_uri5411901
Ref: 1bcf5411901
Ref: library/pathlib pathlib PurePath is_absolute5412261
Ref: 1bd05412261
Ref: library/pathlib pathlib PurePath is_reserved5412859
Ref: 1bd15412859
Ref: library/pathlib pathlib PurePath joinpath5413337
Ref: 1bd25413337
Ref: library/pathlib pathlib PurePath match5413920
Ref: 1bd35413920
Ref: library/pathlib pathlib PurePath relative_to5414847
Ref: 1bd45414847
Ref: library/pathlib pathlib PurePath with_name5415515
Ref: 1bd55415515
Ref: library/pathlib pathlib PurePath with_suffix5416235
Ref: 10355416235
Node: Concrete paths5416911
Ref: library/pathlib concrete-paths5417074
Ref: 1bb95417074
Ref: library/pathlib id25417074
Ref: 1bd65417074
Ref: library/pathlib pathlib Path5417346
Ref: 2025417346
Ref: library/pathlib pathlib PosixPath5417731
Ref: 1bd75417731
Ref: library/pathlib pathlib WindowsPath5418042
Ref: 1bba5418042
Node: Methods<2>5419025
Ref: library/pathlib methods5419086
Ref: 1bd85419086
Ref: library/pathlib pathlib Path cwd5419684
Ref: 1bd95419684
Ref: library/pathlib pathlib Path home5419911
Ref: 7305419911
Ref: library/pathlib pathlib Path stat5420194
Ref: 1bda5420194
Ref: library/pathlib pathlib Path chmod5420548
Ref: 1bdb5420548
Ref: library/pathlib pathlib Path exists5420817
Ref: 2035420817
Ref: library/pathlib pathlib Path expanduser5421297
Ref: 72f5421297
Ref: library/pathlib pathlib Path glob5421622
Ref: 1bdc5421622
Ref: library/pathlib pathlib Path group5422523
Ref: 1bdd5422523
Ref: library/pathlib pathlib Path is_dir5422703
Ref: 2045422703
Ref: library/pathlib pathlib Path is_file5423050
Ref: 2055423050
Ref: library/pathlib pathlib Path is_mount5423404
Ref: 2065423404
Ref: library/pathlib pathlib Path is_symlink5423912
Ref: 2075423912
Ref: library/pathlib pathlib Path is_socket5424167
Ref: 20b5424167
Ref: library/pathlib pathlib Path is_fifo5424521
Ref: 20a5424521
Ref: library/pathlib pathlib Path is_block_device5424854
Ref: 2085424854
Ref: library/pathlib pathlib Path is_char_device5425216
Ref: 2095425216
Ref: library/pathlib pathlib Path iterdir5425585
Ref: 1bde5425585
Ref: library/pathlib pathlib Path lchmod5426344
Ref: 1bdf5426344
Ref: library/pathlib pathlib Path lstat5426539
Ref: 1be05426539
Ref: library/pathlib pathlib Path mkdir5426731
Ref: 72e5426731
Ref: library/pathlib pathlib Path open5427795
Ref: 1be15427795
Ref: library/pathlib pathlib Path owner5428154
Ref: 1be25428154
Ref: library/pathlib pathlib Path read_bytes5428333
Ref: 7345428333
Ref: library/pathlib pathlib Path read_text5428646
Ref: 7325428646
Ref: library/pathlib pathlib Path rename5429083
Ref: 1be35429083
Ref: library/pathlib pathlib Path replace5429898
Ref: 1be45429898
Ref: library/pathlib pathlib Path resolve5430399
Ref: 1bc95430399
Ref: library/pathlib pathlib Path rglob5431326
Ref: 1be55431326
Ref: library/pathlib pathlib Path rmdir5431727
Ref: 1be65431727
Ref: library/pathlib pathlib Path samefile5431819
Ref: 72d5431819
Ref: library/pathlib pathlib Path symlink_to5432374
Ref: 1be75432374
Ref: library/pathlib pathlib Path link_to5433037
Ref: 20c5433037
Ref: library/pathlib pathlib Path touch5433456
Ref: 1be85433456
Ref: library/pathlib pathlib Path unlink5433880
Ref: fd35433880
Ref: library/pathlib pathlib Path write_bytes5434372
Ref: 7335434372
Ref: library/pathlib pathlib Path write_text5434757
Ref: 7315434757
Node: Correspondence to tools in the os module5435235
Ref: library/pathlib correspondence-to-tools-in-the-os-module5435379
Ref: 1be95435379
Node: os path --- Common pathname manipulations5439684
Ref: library/os path doc5439905
Ref: 1bef5439905
Ref: library/os path module-os path5439905
Ref: c65439905
Ref: library/os path os-path-common-pathname-manipulations5439905
Ref: 1bf05439905
Ref: library/os path os path abspath5442295
Ref: cb55442295
Ref: library/os path os path basename5442610
Ref: 1bec5442610
Ref: library/os path os path commonpath5443110
Ref: 72a5443110
Ref: library/os path os path commonprefix5443611
Ref: 72b5443611
Ref: library/os path os path dirname5444250
Ref: 1bed5444250
Ref: library/os path os path exists5444511
Ref: 1f75444511
Ref: library/os path os path lexists5445079
Ref: 1f85445079
Ref: library/os path os path expanduser5445374
Ref: 1ff5445374
Ref: library/os path os path expandvars5446377
Ref: d495446377
Ref: library/os path os path getatime5446858
Ref: 1bf25446858
Ref: library/os path os path getmtime5447157
Ref: 1bf35447157
Ref: library/os path os path getctime5447522
Ref: 1bf45447522
Ref: library/os path os path getsize5448002
Ref: 1bf55448002
Ref: library/os path os path isabs5448221
Ref: 1beb5448221
Ref: library/os path os path isfile5448519
Ref: 1fa5448519
Ref: library/os path os path isdir5448813
Ref: 1f95448813
Ref: library/os path os path islink5449103
Ref: 1f55449103
Ref: library/os path os path ismount5449396
Ref: 1fb5449396
Ref: library/os path os path join5450271
Ref: f615450271
Ref: library/os path os path normcase5451316
Ref: 1bf65451316
Ref: library/os path os path normpath5451644
Ref: cb45451644
Ref: library/os path os path realpath5452138
Ref: 2005452138
Ref: library/os path os path relpath5452673
Ref: 1bea5452673
Ref: library/os path os path samefile5453236
Ref: 8875453236
Ref: library/os path os path sameopenfile5453769
Ref: 1bf85453769
Ref: library/os path os path samestat5454059
Ref: 8865454059
Ref: library/os path os path split5454592
Ref: 1bf15454592
Ref: library/os path os path splitdrive5455370
Ref: 4825455370
Ref: library/os path os path splitext5456256
Ref: 1bee5456256
Ref: library/os path os path supports_unicode_filenames5456643
Ref: df25456643
Ref: os path --- Common pathname manipulations-Footnote-15456851
Ref: os path --- Common pathname manipulations-Footnote-25456919
Node: fileinput --- Iterate over lines from multiple input streams5456984
Ref: library/fileinput doc5457195
Ref: 1bf95457195
Ref: library/fileinput fileinput-iterate-over-lines-from-multiple-input-streams5457195
Ref: 1bfa5457195
Ref: library/fileinput module-fileinput5457195
Ref: 805457195
Ref: library/fileinput fileinput input5459350
Ref: 2ae5459350
Ref: library/fileinput fileinput filename5460432
Ref: 1bfb5460432
Ref: library/fileinput fileinput fileno5460586
Ref: 1bfc5460586
Ref: library/fileinput fileinput lineno5460779
Ref: 1bfd5460779
Ref: library/fileinput fileinput filelineno5461050
Ref: 1bfe5461050
Ref: library/fileinput fileinput isfirstline5461314
Ref: 1bff5461314
Ref: library/fileinput fileinput isstdin5461464
Ref: 1c005461464
Ref: library/fileinput fileinput nextfile5461605
Ref: 1c015461605
Ref: library/fileinput fileinput close5462143
Ref: 1c025462143
Ref: library/fileinput fileinput FileInput5462312
Ref: 2805462312
Ref: library/fileinput fileinput hook_compressed5464891
Ref: 1c045464891
Ref: library/fileinput fileinput hook_encoded5465386
Ref: 54f5465386
Ref: fileinput --- Iterate over lines from multiple input streams-Footnote-15465795
Node: stat --- Interpreting stat results5465863
Ref: library/stat doc5466075
Ref: 1c055466075
Ref: library/stat module-stat5466075
Ref: f55466075
Ref: library/stat stat-interpreting-stat-results5466075
Ref: 1c065466075
Ref: library/stat stat S_ISDIR5466744
Ref: 1c075466744
Ref: library/stat stat S_ISCHR5466832
Ref: 1c085466832
Ref: library/stat stat S_ISBLK5466945
Ref: 1c095466945
Ref: library/stat stat S_ISREG5467049
Ref: 1c0a5467049
Ref: library/stat stat S_ISFIFO5467140
Ref: 1c0b5467140
Ref: library/stat stat S_ISLNK5467237
Ref: 1c0c5467237
Ref: library/stat stat S_ISSOCK5467329
Ref: 1c0d5467329
Ref: library/stat stat S_ISDOOR5467415
Ref: f6f5467415
Ref: library/stat stat S_ISPORT5467523
Ref: f705467523
Ref: library/stat stat S_ISWHT5467638
Ref: f715467638
Ref: library/stat stat S_IMODE5467839
Ref: 1c0e5467839
Ref: library/stat stat S_IFMT5468104
Ref: 1c0f5468104
Ref: library/stat stat filemode5469632
Ref: aa25469632
Ref: library/stat stat ST_MODE5470030
Ref: 8d85470030
Ref: library/stat stat ST_INO5470083
Ref: 1c105470083
Ref: library/stat stat ST_DEV5470126
Ref: 1c115470126
Ref: library/stat stat ST_NLINK5470180
Ref: 1c125470180
Ref: library/stat stat ST_UID5470241
Ref: 1c135470241
Ref: library/stat stat ST_GID5470292
Ref: 1c145470292
Ref: library/stat stat ST_SIZE5470344
Ref: 1c155470344
Ref: library/stat stat ST_ATIME5470456
Ref: 1c165470456
Ref: library/stat stat ST_MTIME5470508
Ref: 1c175470508
Ref: library/stat stat ST_CTIME5470566
Ref: 1c185470566
Ref: library/stat stat S_IFSOCK5471596
Ref: 1c195471596
Ref: library/stat stat S_IFLNK5471635
Ref: 1c1a5471635
Ref: library/stat stat S_IFREG5471680
Ref: 1c1b5471680
Ref: library/stat stat S_IFBLK5471724
Ref: 1c1c5471724
Ref: library/stat stat S_IFDIR5471768
Ref: 1c1d5471768
Ref: library/stat stat S_IFCHR5471809
Ref: 1c1e5471809
Ref: library/stat stat S_IFIFO5471857
Ref: 1c1f5471857
Ref: library/stat stat S_IFDOOR5471893
Ref: 8d95471893
Ref: library/stat stat S_IFPORT5471954
Ref: 8da5471954
Ref: library/stat stat S_IFWHT5472021
Ref: 8db5472021
Ref: library/stat stat S_ISUID5472339
Ref: 1c205472339
Ref: library/stat stat S_ISGID5472382
Ref: 1c215472382
Ref: library/stat stat S_ISVTX5472959
Ref: 1c245472959
Ref: library/stat stat S_IRWXU5473208
Ref: 1c255473208
Ref: library/stat stat S_IRUSR5473271
Ref: 1c265473271
Ref: library/stat stat S_IWUSR5473328
Ref: 1c275473328
Ref: library/stat stat S_IXUSR5473386
Ref: 1c285473386
Ref: library/stat stat S_IRWXG5473446
Ref: 1c295473446
Ref: library/stat stat S_IRGRP5473504
Ref: 1c2a5473504
Ref: library/stat stat S_IWGRP5473561
Ref: 1c2b5473561
Ref: library/stat stat S_IXGRP5473619
Ref: 1c225473619
Ref: library/stat stat S_IRWXO5473679
Ref: 1c2c5473679
Ref: library/stat stat S_IROTH5473757
Ref: 1c2d5473757
Ref: library/stat stat S_IWOTH5473816
Ref: 1c2e5473816
Ref: library/stat stat S_IXOTH5473876
Ref: 1c2f5473876
Ref: library/stat stat S_ENFMT5473938
Ref: 1c235473938
Ref: library/stat stat S_IREAD5474171
Ref: 1c305474171
Ref: library/stat stat S_IWRITE5474242
Ref: 1c315474242
Ref: library/stat stat S_IEXEC5474314
Ref: 1c325474314
Ref: library/stat stat UF_NODUMP5474471
Ref: 1c335474471
Ref: library/stat stat UF_IMMUTABLE5474525
Ref: 1c345474525
Ref: library/stat stat UF_APPEND5474589
Ref: 1c355474589
Ref: library/stat stat UF_OPAQUE5474655
Ref: 1c365474655
Ref: library/stat stat UF_NOUNLINK5474746
Ref: 1c375474746
Ref: library/stat stat UF_COMPRESSED5474820
Ref: 1c385474820
Ref: library/stat stat UF_HIDDEN5474904
Ref: 1c395474904
Ref: library/stat stat SF_ARCHIVED5474996
Ref: 1c3a5474996
Ref: library/stat stat SF_IMMUTABLE5475056
Ref: 1c3b5475056
Ref: library/stat stat SF_APPEND5475120
Ref: 1c3c5475120
Ref: library/stat stat SF_NOUNLINK5475186
Ref: 1c3d5475186
Ref: library/stat stat SF_SNAPSHOT5475260
Ref: 1c3e5475260
Ref: library/stat stat FILE_ATTRIBUTE_ARCHIVE5475657
Ref: 1c3f5475657
Ref: library/stat stat FILE_ATTRIBUTE_COMPRESSED5475695
Ref: 1c405475695
Ref: library/stat stat FILE_ATTRIBUTE_DEVICE5475736
Ref: 1c415475736
Ref: library/stat stat FILE_ATTRIBUTE_DIRECTORY5475773
Ref: 1c425475773
Ref: library/stat stat FILE_ATTRIBUTE_ENCRYPTED5475813
Ref: 1c435475813
Ref: library/stat stat FILE_ATTRIBUTE_HIDDEN5475853
Ref: 1c445475853
Ref: library/stat stat FILE_ATTRIBUTE_INTEGRITY_STREAM5475890
Ref: 1c455475890
Ref: library/stat stat FILE_ATTRIBUTE_NORMAL5475937
Ref: 1c465475937
Ref: library/stat stat FILE_ATTRIBUTE_NOT_CONTENT_INDEXED5475974
Ref: 1c475475974
Ref: library/stat stat FILE_ATTRIBUTE_NO_SCRUB_DATA5476024
Ref: 1c485476024
Ref: library/stat stat FILE_ATTRIBUTE_OFFLINE5476068
Ref: 1c495476068
Ref: library/stat stat FILE_ATTRIBUTE_READONLY5476106
Ref: 1c4a5476106
Ref: library/stat stat FILE_ATTRIBUTE_REPARSE_POINT5476145
Ref: 1c4b5476145
Ref: library/stat stat FILE_ATTRIBUTE_SPARSE_FILE5476189
Ref: 1c4c5476189
Ref: library/stat stat FILE_ATTRIBUTE_SYSTEM5476231
Ref: 1c4d5476231
Ref: library/stat stat FILE_ATTRIBUTE_TEMPORARY5476268
Ref: 1c4e5476268
Ref: library/stat stat FILE_ATTRIBUTE_VIRTUAL5476308
Ref: 1c4f5476308
Ref: library/stat stat IO_REPARSE_TAG_SYMLINK5476576
Ref: 1c505476576
Ref: library/stat stat IO_REPARSE_TAG_MOUNT_POINT5476614
Ref: 1c515476614
Ref: library/stat stat IO_REPARSE_TAG_APPEXECLINK5476656
Ref: 1c525476656
Ref: stat --- Interpreting stat results-Footnote-15476759
Ref: stat --- Interpreting stat results-Footnote-25476822
Node: filecmp --- File and Directory Comparisons5476902
Ref: library/filecmp doc5477107
Ref: 1c535477107
Ref: library/filecmp filecmp-file-and-directory-comparisons5477107
Ref: 1c545477107
Ref: library/filecmp module-filecmp5477107
Ref: 7f5477107
Ref: library/filecmp filecmp cmp5477576
Ref: 1c555477576
Ref: library/filecmp filecmp cmpfiles5478261
Ref: 1c565478261
Ref: library/filecmp filecmp clear_cache5479204
Ref: 84c5479204
Ref: filecmp --- File and Directory Comparisons-Footnote-15479515
Node: The dircmp class5479581
Ref: library/filecmp dircmp-objects5479676
Ref: 1c575479676
Ref: library/filecmp the-dircmp-class5479676
Ref: 1c585479676
Ref: library/filecmp filecmp dircmp5479737
Ref: 84e5479737
Ref: library/filecmp filecmp dircmp report5480273
Ref: 1c595480273
Ref: library/filecmp filecmp dircmp report_partial_closure5480396
Ref: 1c5a5480396
Ref: library/filecmp filecmp dircmp report_full_closure5480543
Ref: 1c5b5480543
Ref: library/filecmp filecmp dircmp left5481068
Ref: 1c5c5481068
Ref: library/filecmp filecmp dircmp right5481121
Ref: 1c5d5481121
Ref: library/filecmp filecmp dircmp left_list5481175
Ref: 1c5e5481175
Ref: library/filecmp filecmp dircmp right_list5481290
Ref: 1c5f5481290
Ref: library/filecmp filecmp dircmp common5481406
Ref: 1c605481406
Ref: library/filecmp filecmp dircmp left_only5481488
Ref: 1c615481488
Ref: library/filecmp filecmp dircmp right_only5481565
Ref: 1c625481565
Ref: library/filecmp filecmp dircmp common_dirs5481643
Ref: 1c635481643
Ref: library/filecmp filecmp dircmp common_files5481720
Ref: 1c645481720
Ref: library/filecmp filecmp dircmp common_funny5481789
Ref: 1c655481789
Ref: library/filecmp filecmp dircmp same_files5481989
Ref: 1c665481989
Ref: library/filecmp filecmp dircmp diff_files5482132
Ref: 1c675482132
Ref: library/filecmp filecmp dircmp funny_files5482294
Ref: 1c685482294
Ref: library/filecmp filecmp dircmp subdirs5482409
Ref: 1c695482409
Ref: library/filecmp filecmp DEFAULT_IGNORES5482542
Ref: 84d5482542
Node: tempfile --- Generate temporary files and directories5483221
Ref: library/tempfile doc5483438
Ref: 1c6a5483438
Ref: library/tempfile module-tempfile5483438
Ref: 1045483438
Ref: library/tempfile tempfile-generate-temporary-files-and-directories5483438
Ref: 1c6b5483438
Ref: library/tempfile tempfile TemporaryFile5484593
Ref: 1c6c5484593
Ref: library/tempfile tempfile NamedTemporaryFile5486626
Ref: d4e5486626
Ref: library/tempfile tempfile SpooledTemporaryFile5487784
Ref: aab5487784
Ref: library/tempfile tempfile TemporaryDirectory5488990
Ref: bcd5488990
Ref: library/tempfile tempfile mkstemp5489970
Ref: 1c6d5489970
Ref: library/tempfile tempfile mkdtemp5492827
Ref: 1c6e5492827
Ref: library/tempfile tempfile gettempdir5493916
Ref: 1c745493916
Ref: library/tempfile tempfile gettempdirb5494923
Ref: 1c765494923
Ref: library/tempfile tempfile gettempprefix5495058
Ref: 1c725495058
Ref: library/tempfile tempfile gettempprefixb5495215
Ref: 1c735495215
Ref: library/tempfile tempfile tempdir5495711
Ref: 1c755495711
Ref: tempfile --- Generate temporary files and directories-Footnote-15496237
Node: Examples<3>5496304
Ref: library/tempfile examples5496448
Ref: 1c775496448
Ref: library/tempfile tempfile-examples5496448
Ref: 1c705496448
Node: Deprecated functions and variables5497366
Ref: library/tempfile deprecated-functions-and-variables5497510
Ref: 1c785497510
Ref: library/tempfile tempfile mktemp5498140
Ref: 1c795498140
Node: glob --- Unix style pathname pattern expansion5499261
Ref: library/glob doc5499478
Ref: 1c7a5499478
Ref: library/glob glob-unix-style-pathname-pattern-expansion5499478
Ref: 1c7b5499478
Ref: library/glob module-glob5499478
Ref: 8a5499478
Ref: library/glob glob glob5500590
Ref: 5cb5500590
Ref: library/glob glob iglob5501838
Ref: 5cc5501838
Ref: library/glob glob escape5502148
Ref: 8555502148
Ref: glob --- Unix style pathname pattern expansion-Footnote-15503597
Node: fnmatch --- Unix filename pattern matching5503660
Ref: library/fnmatch doc5503865
Ref: 1c7f5503865
Ref: library/fnmatch fnmatch-unix-filename-pattern-matching5503865
Ref: 1c805503865
Ref: library/fnmatch module-fnmatch5503865
Ref: 815503865
Ref: library/fnmatch fnmatch fnmatch5505200
Ref: 1c7c5505200
Ref: library/fnmatch fnmatch fnmatchcase5505885
Ref: 1c825505885
Ref: library/fnmatch fnmatch filter5506130
Ref: 1c815506130
Ref: library/fnmatch fnmatch translate5506376
Ref: 10425506376
Ref: fnmatch --- Unix filename pattern matching-Footnote-15506953
Node: linecache --- Random access to text lines5507019
Ref: library/linecache doc5507215
Ref: 1c835507215
Ref: library/linecache linecache-random-access-to-text-lines5507215
Ref: 1c845507215
Ref: library/linecache module-linecache5507215
Ref: a95507215
Ref: library/linecache linecache getline5508045
Ref: 70e5508045
Ref: library/linecache linecache clearcache5508812
Ref: 1c875508812
Ref: library/linecache linecache checkcache5508979
Ref: 1c885508979
Ref: library/linecache linecache lazycache5509255
Ref: 70d5509255
Ref: linecache --- Random access to text lines-Footnote-15509798
Ref: linecache --- Random access to text lines-Footnote-25509866
Node: shutil --- High-level file operations5509915
Ref: library/shutil doc5510060
Ref: 1c895510060
Ref: library/shutil module-shutil5510060
Ref: ea5510060
Ref: library/shutil shutil-high-level-file-operations5510060
Ref: 1c8a5510060
Ref: shutil --- High-level file operations-Footnote-15511162
Node: Directory and files operations5511227
Ref: library/shutil directory-and-files-operations5511360
Ref: 1c8b5511360
Ref: library/shutil file-operations5511360
Ref: 1c8c5511360
Ref: library/shutil shutil copyfileobj5511443
Ref: 25e5511443
Ref: library/shutil shutil copyfile5512024
Ref: 2595512024
Ref: library/shutil shutil SameFileError5513596
Ref: 8b85513596
Ref: library/shutil shutil copymode5513761
Ref: 1c8d5513761
Ref: library/shutil shutil copystat5514644
Ref: a7c5514644
Ref: library/shutil shutil copy5516737
Ref: 25a5516737
Ref: library/shutil shutil copy25518148
Ref: 25b5518148
Ref: library/shutil shutil ignore_patterns5519642
Ref: 1c8f5519642
Ref: library/shutil shutil copytree5519942
Ref: 21b5519942
Ref: library/shutil shutil rmtree5523062
Ref: 21d5523062
Ref: library/shutil shutil rmtree avoids_symlink_attacks5524968
Ref: 1c905524968
Ref: library/shutil shutil move5525303
Ref: 25c5525303
Ref: library/shutil shutil disk_usage5527112
Ref: a7a5527112
Ref: library/shutil shutil chown5527542
Ref: a7b5527542
Ref: library/shutil shutil which5528024
Ref: edf5528024
Ref: library/shutil shutil Error5529328
Ref: 8b75529328
Node: Platform-dependent efficient copy operations5529661
Ref: library/shutil platform-dependent-efficient-copy-operations5529797
Ref: 1c915529797
Ref: library/shutil shutil-platform-dependent-efficient-copy-operations5529797
Ref: 25f5529797
Ref: Platform-dependent efficient copy operations-Footnote-15530900
Ref: Platform-dependent efficient copy operations-Footnote-25530943
Node: copytree example5530991
Ref: library/shutil copytree-example5531150
Ref: 1c925531150
Ref: library/shutil shutil-copytree-example5531150
Ref: 1c935531150
Node: rmtree example5533228
Ref: library/shutil rmtree-example5533334
Ref: 1c945533334
Ref: library/shutil shutil-rmtree-example5533334
Ref: 1c955533334
Node: Archiving operations5533881
Ref: library/shutil archiving-operations5534063
Ref: b9b5534063
Ref: library/shutil id15534063
Ref: 1c965534063
Ref: library/shutil shutil make_archive5534360
Ref: 21c5534360
Ref: library/shutil shutil get_archive_formats5536302
Ref: 1c985536302
Ref: library/shutil shutil register_archive_format5537142
Ref: 1c995537142
Ref: library/shutil shutil unregister_archive_format5537986
Ref: 1c9a5537986
Ref: library/shutil shutil unpack_archive5538119
Ref: b9c5538119
Ref: library/shutil shutil register_unpack_format5539048
Ref: 1c9b5539048
Ref: library/shutil shutil unregister_unpack_format5539809
Ref: 1c9d5539809
Ref: library/shutil shutil get_unpack_formats5539931
Ref: 1c9c5539931
Ref: Archiving operations-Footnote-15540882
Node: Archiving example5540931
Ref: library/shutil archiving-example5541045
Ref: 1c9e5541045
Ref: library/shutil shutil-archiving-example5541045
Ref: 1c9f5541045
Node: Archiving example with base_dir5542138
Ref: library/shutil archiving-example-with-base-dir5542252
Ref: 1ca05542252
Ref: library/shutil shutil-archiving-example-with-basedir5542252
Ref: 1c975542252
Node: Querying the size of the output terminal5543356
Ref: library/shutil querying-the-size-of-the-output-terminal5543499
Ref: 1ca15543499
Ref: library/shutil shutil get_terminal_size5543602
Ref: a4f5543602
Ref: Querying the size of the output terminal-Footnote-15545124
Node: Data Persistence5545206
Ref: library/persistence doc5545358
Ref: 1ca45545358
Ref: library/persistence data-persistence5545358
Ref: 1ca55545358
Ref: library/persistence other-environment-variables5545358
Ref: 1ca65545358
Ref: library/persistence persistence5545358
Ref: 1ca75545358
Node: pickle --- Python object serialization5546371
Ref: library/pickle doc5546516
Ref: 1ca85546516
Ref: library/pickle module-pickle5546516
Ref: cb5546516
Ref: library/pickle pickle-python-object-serialization5546516
Ref: 1ca95546516
Ref: pickle --- Python object serialization-Footnote-15548322
Ref: pickle --- Python object serialization-Footnote-25548387
Node: Relationship to other Python modules5548455
Ref: library/pickle relationship-to-other-python-modules5548593
Ref: 1cac5548593
Node: Comparison with marshal5548749
Ref: library/pickle comparison-with-marshal5548874
Ref: 1cad5548874
Node: Comparison with json5551102
Ref: library/pickle comparison-with-json5551227
Ref: 1cab5551227
Ref: library/pickle id25551227
Ref: 1cae5551227
Ref: Comparison with json-Footnote-15552391
Node: Data stream format5552415
Ref: library/pickle data-stream-format5552578
Ref: 1cb05552578
Ref: library/pickle pickle-protocols5552578
Ref: 5735552578
Ref: Data stream format-Footnote-15555546
Ref: Data stream format-Footnote-25555595
Ref: Data stream format-Footnote-35555644
Node: Module Interface5555693
Ref: library/pickle module-interface5555854
Ref: 1cb35555854
Ref: library/pickle pickle HIGHEST_PROTOCOL5556306
Ref: e055556306
Ref: library/pickle pickle DEFAULT_PROTOCOL5556578
Ref: 1cb65556578
Ref: library/pickle pickle dump5557068
Ref: 1cb55557068
Ref: library/pickle pickle dumps5557555
Ref: e045557555
Ref: library/pickle pickle load5557981
Ref: 5c75557981
Ref: library/pickle pickle loads5558718
Ref: 5c85558718
Ref: library/pickle pickle PickleError5559440
Ref: 1cb75559440
Ref: library/pickle pickle PicklingError5559571
Ref: 1cb85559571
Ref: library/pickle pickle UnpicklingError5559847
Ref: 1cba5559847
Ref: library/pickle pickle Pickler5560353
Ref: 20e5560353
Ref: library/pickle pickle Pickler dump5561899
Ref: 10415561899
Ref: library/pickle pickle Pickler persistent_id5562047
Ref: 1cbd5562047
Ref: library/pickle pickle Pickler dispatch_table5562729
Ref: a6e5562729
Ref: library/pickle pickle Pickler reducer_override5563888
Ref: 20f5563888
Ref: library/pickle pickle Pickler fast5564507
Ref: 1cc35564507
Ref: library/pickle pickle Unpickler5564989
Ref: 1cb45564989
Ref: library/pickle pickle Unpickler load5567085
Ref: 1cc55567085
Ref: library/pickle pickle Unpickler persistent_load5567386
Ref: 1cbe5567386
Ref: library/pickle pickle Unpickler find_class5567839
Ref: 1cc65567839
Ref: library/pickle pickle PickleBuffer5568524
Ref: 1cbb5568524
Ref: library/pickle pickle PickleBuffer raw5569141
Ref: 1cc85569141
Ref: library/pickle pickle PickleBuffer release5569490
Ref: 1cc95569490
Node: What can be pickled and unpickled?5569612
Ref: library/pickle pickle-picklable5569779
Ref: 1cb95569779
Ref: library/pickle what-can-be-pickled-and-unpickled5569779
Ref: 1cca5569779
Ref: What can be pickled and unpickled?-Footnote-15572503
Ref: What can be pickled and unpickled?-Footnote-25572639
Node: Pickling Class Instances5572779
Ref: library/pickle pickle-inst5572984
Ref: 1caf5572984
Ref: library/pickle pickling-class-instances5572984
Ref: 1ccb5572984
Ref: library/pickle object __getnewargs_ex__5573916
Ref: 1ccc5573916
Ref: library/pickle object __getnewargs__5574745
Ref: 6b35574745
Ref: library/pickle object __getstate__5575308
Ref: e065575308
Ref: library/pickle object __setstate__5575753
Ref: 19d5575753
Ref: library/pickle object __reduce__5577602
Ref: 19c5577602
Ref: library/pickle object __reduce_ex__5580467
Ref: 1a015580467
Ref: Pickling Class Instances-Footnote-15581134
Node: Persistence of External Objects5581233
Ref: library/pickle persistence-of-external-objects5581349
Ref: 1cce5581349
Ref: library/pickle pickle-persistent5581349
Ref: 1cbf5581349
Ref: Persistence of External Objects-Footnote-15586017
Node: Dispatch Tables5586281
Ref: library/pickle dispatch-tables5586431
Ref: 1ccf5586431
Ref: library/pickle pickle-dispatch5586431
Ref: 1cc15586431
Node: Handling Stateful Objects5587658
Ref: library/pickle handling-stateful-objects5587768
Ref: 1cd05587768
Ref: library/pickle pickle-state5587768
Ref: 1ccd5587768
Node: Custom Reduction for Types Functions and Other Objects5590055
Ref: library/pickle custom-reduction-for-types-functions-and-other-objects5590245
Ref: 1cd15590245
Ref: library/pickle reducer-override5590245
Ref: 1cc25590245
Node: Out-of-band Buffers5592337
Ref: library/pickle out-of-band-buffers5592522
Ref: 1cd25592522
Ref: library/pickle pickle-oob5592522
Ref: 1cbc5592522
Node: Provider API5593368
Ref: library/pickle provider-api5593457
Ref: 1cd35593457
Node: Consumer API5594064
Ref: library/pickle consumer-api5594172
Ref: 1cd45594172
Node: Example<4>5595474
Ref: library/pickle example5595561
Ref: 1cd55595561
Ref: Example<4>-Footnote-15597944
Node: Restricting Globals5597993
Ref: library/pickle pickle-restrict5598138
Ref: 1cc75598138
Ref: library/pickle restricting-globals5598138
Ref: 1cd65598138
Node: Performance<2>5600910
Ref: library/pickle performance5601047
Ref: 1cd75601047
Node: Examples<4>5601323
Ref: library/pickle examples5601432
Ref: 1cd85601432
Ref: library/pickle pickle-example5601432
Ref: 1cd95601432
Node: copyreg --- Register pickle support functions5602662
Ref: library/copyreg doc5602852
Ref: 1cda5602852
Ref: library/copyreg copyreg-register-pickle-support-functions5602852
Ref: 1cdb5602852
Ref: library/copyreg module-copyreg5602852
Ref: 275602852
Ref: library/copyreg copyreg constructor5603444
Ref: 1cdc5603444
Ref: library/copyreg copyreg pickle5603645
Ref: 1cc05603645
Ref: copyreg --- Register pickle support functions-Footnote-15604592
Node: Example<5>5604658
Ref: library/copyreg example5604750
Ref: 1cdd5604750
Node: shelve --- Python object persistence5605302
Ref: library/shelve doc5605502
Ref: 1cde5605502
Ref: library/shelve module-shelve5605502
Ref: e85605502
Ref: library/shelve shelve-python-object-persistence5605502
Ref: 1cdf5605502
Ref: library/shelve shelve open5606079
Ref: 1ce05606079
Ref: library/shelve shelve Shelf sync5608294
Ref: 1ce25608294
Ref: library/shelve shelve Shelf close5608621
Ref: 1ce35608621
Ref: shelve --- Python object persistence-Footnote-15609008
Ref: shelve --- Python object persistence-Footnote-25609073
Node: Restrictions5609126
Ref: library/shelve restrictions5609230
Ref: 1ce45609230
Ref: library/shelve shelve Shelf5610255
Ref: 8b55610255
Ref: library/shelve shelve BsdDbShelf5611474
Ref: 1ce55611474
Ref: library/shelve shelve DbfilenameShelf5612181
Ref: 1ce65612181
Ref: Restrictions-Footnote-15612797
Node: Example<6>5612850
Ref: library/shelve example5612954
Ref: 1ce75612954
Ref: library/shelve shelve-example5612954
Ref: 1ce15612954
Node: marshal --- Internal Python object serialization5614632
Ref: library/marshal doc5614825
Ref: 1ce85614825
Ref: library/marshal marshal-internal-python-object-serialization5614825
Ref: 1ce95614825
Ref: library/marshal module-marshal5614825
Ref: b15614825
Ref: library/marshal marshal dump5617223
Ref: 1cea5617223
Ref: library/marshal marshal load5617768
Ref: ff55617768
Ref: library/marshal marshal dumps5618319
Ref: 7a15618319
Ref: library/marshal marshal loads5618717
Ref: 1ceb5618717
Ref: library/marshal marshal version5619016
Ref: 1cec5619016
Ref: marshal --- Internal Python object serialization-Footnote-15619383
Node: dbm --- Interfaces to Unix "databases"5619755
Ref: library/dbm doc5619965
Ref: 1ced5619965
Ref: library/dbm dbm-interfaces-to-unix-databases5619965
Ref: 1cee5619965
Ref: library/dbm module-dbm5619965
Ref: 325619965
Ref: library/dbm dbm error5620471
Ref: 1cef5620471
Ref: library/dbm dbm whichdb5620740
Ref: 1cf05620740
Ref: library/dbm dbm open5621301
Ref: 8355621301
Ref: dbm --- Interfaces to Unix "databases"-Footnote-15624900
Ref: dbm --- Interfaces to Unix "databases"-Footnote-25624971
Node: dbm gnu --- GNU's reinterpretation of dbm5625024
Ref: library/dbm dbm-gnu-gnu-s-reinterpretation-of-dbm5625185
Ref: 1cf15625185
Ref: library/dbm module-dbm gnu5625185
Ref: 345625185
Ref: library/dbm dbm gnu error5626001
Ref: 2c65626001
Ref: library/dbm dbm gnu open5626202
Ref: 10365626202
Ref: library/dbm dbm gnu gdbm firstkey5628278
Ref: 1cf25628278
Ref: library/dbm dbm gnu gdbm nextkey5628628
Ref: 1cf35628628
Ref: library/dbm dbm gnu gdbm reorganize5629015
Ref: 1cf45629015
Ref: library/dbm dbm gnu gdbm sync5629464
Ref: 1cf55629464
Ref: library/dbm dbm gnu gdbm close5629635
Ref: 1cf65629635
Ref: dbm gnu --- GNU's reinterpretation of dbm-Footnote-15629751
Node: dbm ndbm --- Interface based on ndbm5629817
Ref: library/dbm dbm-ndbm-interface-based-on-ndbm5630027
Ref: 1cf75630027
Ref: library/dbm module-dbm ndbm5630027
Ref: 355630027
Ref: library/dbm dbm ndbm error5630775
Ref: 2c75630775
Ref: library/dbm dbm ndbm library5630978
Ref: 1cf85630978
Ref: library/dbm dbm ndbm open5631064
Ref: 10375631064
Ref: library/dbm dbm ndbm ndbm close5632347
Ref: 1cf95632347
Ref: dbm ndbm --- Interface based on ndbm-Footnote-15632463
Node: dbm dumb --- Portable DBM implementation5632530
Ref: library/dbm dbm-dumb-portable-dbm-implementation5632690
Ref: 1cfa5632690
Ref: library/dbm module-dbm dumb5632690
Ref: 335632690
Ref: library/dbm dbm dumb error5633517
Ref: 2c55633517
Ref: library/dbm dbm dumb open5633720
Ref: 2c05633720
Ref: library/dbm dbm dumb dumbdbm sync5635643
Ref: 1cfb5635643
Ref: library/dbm dbm dumb dumbdbm close5635812
Ref: 1cfc5635812
Ref: dbm dumb --- Portable DBM implementation-Footnote-15635934
Node: sqlite3 --- DB-API 2 0 interface for SQLite databases5636001
Ref: library/sqlite3 doc5636154
Ref: 1cfd5636154
Ref: library/sqlite3 module-sqlite35636154
Ref: f35636154
Ref: library/sqlite3 sqlite3-db-api-2-0-interface-for-sqlite-databases5636154
Ref: 1cfe5636154
Ref: sqlite3 --- DB-API 2 0 interface for SQLite databases-Footnote-15640501
Ref: sqlite3 --- DB-API 2 0 interface for SQLite databases-Footnote-25640565
Ref: sqlite3 --- DB-API 2 0 interface for SQLite databases-Footnote-35640614
Node: Module functions and constants5640663
Ref: library/sqlite3 module-functions-and-constants5640810
Ref: 1d035640810
Ref: library/sqlite3 sqlite3-module-contents5640810
Ref: 1d045640810
Ref: library/sqlite3 sqlite3 version5640891
Ref: 1d055640891
Ref: library/sqlite3 sqlite3 version_info5641025
Ref: 1d065641025
Ref: library/sqlite3 sqlite3 sqlite_version5641175
Ref: 1d075641175
Ref: library/sqlite3 sqlite3 sqlite_version_info5641279
Ref: 1d085641279
Ref: library/sqlite3 sqlite3 PARSE_DECLTYPES5641404
Ref: 1d095641404
Ref: library/sqlite3 sqlite3 PARSE_COLNAMES5641990
Ref: 1d0a5641990
Ref: library/sqlite3 sqlite3 connect5642880
Ref: 3df5642880
Ref: library/sqlite3 sqlite3 register_converter5646477
Ref: 1d0d5646477
Ref: library/sqlite3 sqlite3 register_adapter5646956
Ref: 1d0f5646956
Ref: library/sqlite3 sqlite3 complete_statement5647279
Ref: 1d105647279
Ref: library/sqlite3 sqlite3 enable_callback_tracebacks5648611
Ref: 1d115648611
Ref: Module functions and constants-Footnote-15649060
Node: Connection Objects5649100
Ref: library/sqlite3 connection-objects5649270
Ref: 1d125649270
Ref: library/sqlite3 sqlite3-connection-objects5649270
Ref: 1d135649270
Ref: library/sqlite3 sqlite3 Connection5649327
Ref: 3dd5649327
Ref: library/sqlite3 sqlite3 Connection isolation_level5649441
Ref: 1d0c5649441
Ref: library/sqlite3 sqlite3 Connection in_transaction5649735
Ref: 1d155649735
Ref: library/sqlite3 sqlite3 Connection cursor5649956
Ref: 1d165649956
Ref: library/sqlite3 sqlite3 Connection commit5650202
Ref: 1d175650202
Ref: library/sqlite3 sqlite3 Connection rollback5650601
Ref: 1d185650601
Ref: library/sqlite3 sqlite3 Connection close5650754
Ref: 1d195650754
Ref: library/sqlite3 sqlite3 Connection execute5651047
Ref: 1d1a5651047
Ref: library/sqlite3 sqlite3 Connection executemany5651349
Ref: 1d1b5651349
Ref: library/sqlite3 sqlite3 Connection executescript5651659
Ref: 1d1d5651659
Ref: library/sqlite3 sqlite3 Connection create_function5651966
Ref: fa35651966
Ref: library/sqlite3 sqlite3 Connection create_aggregate5653365
Ref: fa25653365
Ref: library/sqlite3 sqlite3 Connection create_collation5654703
Ref: 1d205654703
Ref: library/sqlite3 sqlite3 Connection interrupt5656315
Ref: 1d215656315
Ref: library/sqlite3 sqlite3 Connection set_authorizer5656561
Ref: fa45656561
Ref: library/sqlite3 sqlite3 Connection set_progress_handler5657919
Ref: fa55657919
Ref: library/sqlite3 sqlite3 Connection set_trace_callback5658583
Ref: a925658583
Ref: library/sqlite3 sqlite3 Connection enable_load_extension5659354
Ref: b9e5659354
Ref: library/sqlite3 sqlite3 Connection load_extension5661172
Ref: b9f5661172
Ref: library/sqlite3 sqlite3 Connection row_factory5661516
Ref: 1d235661516
Ref: library/sqlite3 sqlite3 Connection text_factory5662879
Ref: 1d245662879
Ref: library/sqlite3 sqlite3 Connection total_changes5664593
Ref: 1d255664593
Ref: library/sqlite3 sqlite3 Connection iterdump5664786
Ref: 1d265664786
Ref: library/sqlite3 sqlite3 Connection backup5665439
Ref: 3de5665439
Ref: Connection Objects-Footnote-15667856
Ref: Connection Objects-Footnote-25667902
Ref: Connection Objects-Footnote-35668201
Node: Cursor Objects5668500
Ref: library/sqlite3 cursor-objects5668651
Ref: 1d275668651
Ref: library/sqlite3 sqlite3-cursor-objects5668651
Ref: 1d285668651
Ref: library/sqlite3 sqlite3 Cursor5668700
Ref: 1cff5668700
Ref: library/sqlite3 sqlite3 Cursor execute5668812
Ref: 1d005668812
Ref: library/sqlite3 sqlite3 Cursor executemany5670095
Ref: 1d1c5670095
Ref: library/sqlite3 sqlite3 Cursor executescript5671881
Ref: 1d1e5671881
Ref: library/sqlite3 sqlite3 Cursor fetchone5673001
Ref: 1d015673001
Ref: library/sqlite3 sqlite3 Cursor fetchmany5673183
Ref: 1d2a5673183
Ref: library/sqlite3 sqlite3 Cursor fetchall5674166
Ref: 1d025674166
Ref: library/sqlite3 sqlite3 Cursor close5674456
Ref: 1d2b5674456
Ref: library/sqlite3 sqlite3 Cursor rowcount5674766
Ref: 1d2c5674766
Ref: library/sqlite3 sqlite3 Cursor lastrowid5675745
Ref: 5835675745
Ref: library/sqlite3 sqlite3 Cursor arraysize5676372
Ref: 1d2d5676372
Ref: library/sqlite3 sqlite3 Cursor description5676598
Ref: 1d0b5676598
Ref: library/sqlite3 sqlite3 Cursor connection5676976
Ref: 1d2e5676976
Node: Row Objects5677469
Ref: library/sqlite3 row-objects5677615
Ref: 1d2f5677615
Ref: library/sqlite3 sqlite3-row-objects5677615
Ref: 1d305677615
Ref: library/sqlite3 sqlite3 Row5677658
Ref: 7635677658
Ref: library/sqlite3 sqlite3 Row keys5678119
Ref: 1d315678119
Node: Exceptions<3>5679356
Ref: library/sqlite3 exceptions5679511
Ref: 1d325679511
Ref: library/sqlite3 sqlite3-exceptions5679511
Ref: 1d335679511
Ref: library/sqlite3 sqlite3 Warning5679552
Ref: 1d295679552
Ref: library/sqlite3 sqlite3 Error5679623
Ref: 1d345679623
Ref: library/sqlite3 sqlite3 DatabaseError5679759
Ref: 1d355679759
Ref: library/sqlite3 sqlite3 IntegrityError5679862
Ref: 1d365679862
Ref: library/sqlite3 sqlite3 ProgrammingError5680071
Ref: edd5680071
Ref: library/sqlite3 sqlite3 OperationalError5680338
Ref: 1d225680338
Ref: library/sqlite3 sqlite3 NotSupportedError5680699
Ref: 1d1f5680699
Node: SQLite and Python types5681042
Ref: library/sqlite3 sqlite-and-python-types5681210
Ref: 1d375681210
Ref: library/sqlite3 sqlite3-types5681210
Ref: 1d0e5681210
Node: 簡介<7>5681468
Ref: library/sqlite3 introduction5681613
Ref: 1d385681613
Node: Using adapters to store additional Python types in SQLite databases5683486
Ref: library/sqlite3 using-adapters-to-store-additional-python-types-in-sqlite-databases5683687
Ref: 1d395683687
Node: Letting your object adapt itself5684285
Ref: library/sqlite3 letting-your-object-adapt-itself5684461
Ref: 1d3a5684461
Node: Registering an adapter callable5685574
Ref: library/sqlite3 registering-an-adapter-callable5685750
Ref: 1d3b5685750
Node: Converting SQLite values to custom Python types5687066
Ref: library/sqlite3 converting-sqlite-values-to-custom-python-types5687289
Ref: 1d3c5687289
Node: Default adapters and converters5689920
Ref: library/sqlite3 default-adapters-and-converters5690067
Ref: 1d3d5690067
Node: Controlling Transactions5691617
Ref: library/sqlite3 controlling-transactions5691797
Ref: 1d3e5691797
Ref: library/sqlite3 sqlite3-controlling-transactions5691797
Ref: 1d145691797
Node: Using sqlite3 efficiently5693444
Ref: library/sqlite3 using-sqlite3-efficiently5693592
Ref: 1d3f5693592
Node: Using shortcut methods5693806
Ref: library/sqlite3 using-shortcut-methods5693944
Ref: 1d405693944
Node: Accessing columns by name instead of by index5695242
Ref: library/sqlite3 accessing-columns-by-name-instead-of-by-index5695430
Ref: 1d415695430
Node: Using the connection as a context manager5696154
Ref: library/sqlite3 using-the-connection-as-a-context-manager5696311
Ref: 1d425696311
Node: 資料壓縮與保存5697435
Ref: library/archiving doc5697578
Ref: 1cb15697578
Ref: library/archiving archiving5697578
Ref: 1d435697578
Ref: library/archiving data-compression-and-archiving5697578
Ref: 1d445697578
Node: zlib --- Compression compatible with gzip5698359
Ref: library/zlib doc5698498
Ref: 1d455698498
Ref: library/zlib module-zlib5698498
Ref: 1455698498
Ref: library/zlib zlib-compression-compatible-with-gzip5698498
Ref: 1d465698498
Ref: library/zlib zlib error5699463
Ref: 1d475699463
Ref: library/zlib zlib adler325699551
Ref: 1d485699551
Ref: library/zlib zlib compress5700453
Ref: 5c35700453
Ref: library/zlib zlib compressobj5701211
Ref: 1d495701211
Ref: library/zlib zlib crc325703920
Ref: 1d4a5703920
Ref: library/zlib zlib decompress5704737
Ref: 5c45704737
Ref: library/zlib decompress-wbits5705155
Ref: 1d4b5705155
Ref: library/zlib zlib decompressobj5706872
Ref: 1d4c5706872
Ref: library/zlib zlib Compress compress5707858
Ref: 1d4d5707858
Ref: library/zlib zlib Compress flush5708222
Ref: 1d4e5708222
Ref: library/zlib zlib Compress copy5708983
Ref: 1d4f5708983
Ref: library/zlib zlib Decompress unused_data5709348
Ref: 1d505709348
Ref: library/zlib zlib Decompress unconsumed_tail5709691
Ref: 1d515709691
Ref: library/zlib zlib Decompress eof5710142
Ref: acb5710142
Ref: library/zlib zlib Decompress decompress5710420
Ref: 1d525710420
Ref: library/zlib zlib Decompress flush5711439
Ref: 1d535711439
Ref: library/zlib zlib Decompress copy5711850
Ref: 1d545711850
Ref: library/zlib zlib ZLIB_VERSION5712325
Ref: 1d555712325
Ref: library/zlib zlib ZLIB_RUNTIME_VERSION5712579
Ref: acc5712579
Node: gzip --- Support for gzip files5713014
Ref: library/gzip doc5713199
Ref: 1d565713199
Ref: library/gzip gzip-support-for-gzip-files5713199
Ref: 1d575713199
Ref: library/gzip module-gzip5713199
Ref: 8c5713199
Ref: library/gzip gzip open5714194
Ref: 1d585714194
Ref: library/gzip gzip BadGzipFile5715691
Ref: 1d35715691
Ref: library/gzip gzip GzipFile5715931
Ref: 6e25715931
Ref: library/gzip gzip GzipFile peek5718753
Ref: b8d5718753
Ref: library/gzip gzip GzipFile mtime5719383
Ref: 1d595719383
Ref: library/gzip gzip compress5720651
Ref: 1d25720651
Ref: library/gzip gzip decompress5721022
Ref: b8e5721022
Ref: gzip --- Support for gzip files-Footnote-15721282
Node: Examples of usage5721345
Ref: library/gzip examples-of-usage5721461
Ref: 1d5e5721461
Ref: library/gzip gzip-usage-examples5721461
Ref: 1d5f5721461
Node: Command Line Interface5722378
Ref: library/gzip command-line-interface5722494
Ref: 1d605722494
Node: Command line options5722906
Ref: library/gzip command-line-options5722985
Ref: 1d615722985
Ref: library/gzip cmdoption-gzip-arg-file5723046
Ref: 1d625723046
Ref: library/gzip cmdoption-gzip-fast5723136
Ref: 1d635723136
Ref: library/gzip cmdoption-gzip-best5723229
Ref: 1d645723229
Ref: library/gzip cmdoption-gzip-d5723322
Ref: 1d655723322
Ref: library/gzip cmdoption-gzip-h5723391
Ref: 1d665723391
Node: bz2 --- Support for bzip2 compression5723450
Ref: library/bz2 doc5723639
Ref: 1d675723639
Ref: library/bz2 bz2-support-for-bzip2-compression5723639
Ref: 1d685723639
Ref: library/bz2 module-bz25723639
Ref: 145723639
Ref: bz2 --- Support for bzip2 compression-Footnote-15724679
Node: De compression of files5724741
Ref: library/bz2 de-compression-of-files5724873
Ref: 1d6b5724873
Ref: library/bz2 bz2 open5724942
Ref: 9db5724942
Ref: library/bz2 bz2 BZ2File5726352
Ref: 9365726352
Ref: library/bz2 bz2 BZ2File peek5727903
Ref: 1d6c5727903
Node: Incremental de compression5729291
Ref: library/bz2 incremental-de-compression5729455
Ref: 1d6d5729455
Ref: library/bz2 bz2 BZ2Compressor5729530
Ref: 1d695729530
Ref: library/bz2 bz2 BZ2Compressor compress5729871
Ref: 1d6e5729871
Ref: library/bz2 bz2 BZ2Compressor flush5730225
Ref: 1d6f5730225
Ref: library/bz2 bz2 BZ2Decompressor5730460
Ref: 1d6a5730460
Ref: library/bz2 bz2 BZ2Decompressor decompress5731014
Ref: 6a85731014
Ref: library/bz2 bz2 BZ2Decompressor eof5732369
Ref: 1d725732369
Ref: library/bz2 bz2 BZ2Decompressor unused_data5732488
Ref: 1d715732488
Ref: library/bz2 bz2 BZ2Decompressor needs_input5732707
Ref: 1d705732707
Node: One-shot de compression5732924
Ref: library/bz2 one-shot-de-compression5733085
Ref: 1d735733085
Ref: library/bz2 bz2 compress5733154
Ref: 187b5733154
Ref: library/bz2 bz2 decompress5733451
Ref: 9dc5733451
Node: Examples of usage<2>5733798
Ref: library/bz2 bz2-usage-examples5733924
Ref: 1d745733924
Ref: library/bz2 examples-of-usage5733924
Ref: 1d755733924
Node: lzma --- Compression using the LZMA algorithm5736836
Ref: library/lzma doc5737028
Ref: 1d765737028
Ref: library/lzma lzma-compression-using-the-lzma-algorithm5737028
Ref: 1d775737028
Ref: library/lzma module-lzma5737028
Ref: ae5737028
Ref: library/lzma lzma LZMAError5737867
Ref: 1d785737867
Ref: lzma --- Compression using the LZMA algorithm-Footnote-15738283
Node: Reading and writing compressed files5738346
Ref: library/lzma reading-and-writing-compressed-files5738517
Ref: 1d795738517
Ref: library/lzma lzma open5738610
Ref: 1d7a5738610
Ref: library/lzma lzma LZMAFile5740352
Ref: 9375740352
Ref: library/lzma lzma LZMAFile peek5742230
Ref: 1d7d5742230
Node: Compressing and decompressing data in memory5743087
Ref: library/lzma compressing-and-decompressing-data-in-memory5743283
Ref: 1d7e5743283
Ref: library/lzma lzma LZMACompressor5743392
Ref: 1d7c5743392
Ref: library/lzma lzma LZMACompressor compress5746473
Ref: 1d815746473
Ref: library/lzma lzma LZMACompressor flush5746952
Ref: 1d825746952
Ref: library/lzma lzma LZMADecompressor5747238
Ref: 1d7b5747238
Ref: library/lzma lzma LZMADecompressor decompress5748769
Ref: 7195748769
Ref: library/lzma lzma LZMADecompressor check5750127
Ref: 1d865750127
Ref: library/lzma lzma LZMADecompressor eof5750357
Ref: 1d875750357
Ref: library/lzma lzma LZMADecompressor unused_data5750447
Ref: 1d855750447
Ref: library/lzma lzma LZMADecompressor needs_input5750615
Ref: 1d845750615
Ref: library/lzma lzma compress5750832
Ref: 1d7f5750832
Ref: library/lzma lzma decompress5751176
Ref: 1d835751176
Node: Miscellaneous<2>5751681
Ref: library/lzma miscellaneous5751872
Ref: 1d885751872
Ref: library/lzma lzma is_check_supported5751919
Ref: 1d895751919
Node: Specifying custom filter chains5752279
Ref: library/lzma filter-chain-specs5752437
Ref: 1d805752437
Ref: library/lzma specifying-custom-filter-chains5752437
Ref: 1d8a5752437
Node: Examples<5>5755282
Ref: library/lzma examples5755415
Ref: 1d8b5755415
Node: zipfile --- Work with ZIP archives5756783
Ref: library/zipfile doc5756982
Ref: 1d8c5756982
Ref: library/zipfile module-zipfile5756982
Ref: 1435756982
Ref: library/zipfile zipfile-work-with-zip-archives5756982
Ref: 1d8d5756982
Ref: library/zipfile zipfile BadZipFile5757845
Ref: 1d8e5757845
Ref: library/zipfile zipfile BadZipfile5757943
Ref: 1d8f5757943
Ref: library/zipfile zipfile LargeZipFile5758092
Ref: 1d905758092
Ref: library/zipfile zipfile ZipInfo5758642
Ref: 5bf5758642
Ref: library/zipfile zipfile is_zipfile5759341
Ref: cbf5759341
Ref: library/zipfile zipfile ZIP_STORED5759623
Ref: 1d965759623
Ref: library/zipfile zipfile ZIP_DEFLATED5759716
Ref: 1d975759716
Ref: library/zipfile zipfile ZIP_BZIP25759862
Ref: 1d985759862
Ref: library/zipfile zipfile ZIP_LZMA5760023
Ref: 1d995760023
Ref: zipfile --- Work with ZIP archives-Footnote-15761028
Ref: zipfile --- Work with ZIP archives-Footnote-25761094
Ref: zipfile --- Work with ZIP archives-Footnote-35761162
Ref: zipfile --- Work with ZIP archives-Footnote-45761230
Node: ZipFile Objects5761263
Ref: library/zipfile id15761370
Ref: 1d9a5761370
Ref: library/zipfile zipfile-objects5761370
Ref: 1d915761370
Ref: library/zipfile zipfile ZipFile5761421
Ref: 4245761421
Ref: library/zipfile zipfile ZipFile close5765355
Ref: 1d9b5765355
Ref: library/zipfile zipfile ZipFile getinfo5765532
Ref: 1d935765532
Ref: library/zipfile zipfile ZipFile infolist5765797
Ref: 1d945765797
Ref: library/zipfile zipfile ZipFile namelist5766061
Ref: 1d9c5766061
Ref: library/zipfile zipfile ZipFile open5766148
Ref: 5c15766148
Ref: library/zipfile zipfile ZipFile extract5768516
Ref: 1da05768516
Ref: library/zipfile zipfile ZipFile extractall5769865
Ref: 1da15769865
Ref: library/zipfile zipfile ZipFile printdir5770870
Ref: 1da25770870
Ref: library/zipfile zipfile ZipFile setpassword5770978
Ref: 1da35770978
Ref: library/zipfile zipfile ZipFile read5771087
Ref: cbe5771087
Ref: library/zipfile zipfile ZipFile testzip5771986
Ref: 1da45771986
Ref: library/zipfile zipfile ZipFile write5772353
Ref: 6145772353
Ref: library/zipfile zipfile ZipFile writestr5773514
Ref: cc05773514
Ref: library/zipfile zipfile ZipFile filename5775139
Ref: 1da55775139
Ref: library/zipfile zipfile ZipFile debug5775197
Ref: 1da65775197
Ref: library/zipfile zipfile ZipFile comment5775414
Ref: 1da75775414
Node: Path Objects5775734
Ref: library/zipfile id25775867
Ref: 1da85775867
Ref: library/zipfile path-objects5775867
Ref: 1d925775867
Ref: library/zipfile zipfile Path5775912
Ref: f0f5775912
Ref: library/zipfile zipfile Path name5776459
Ref: 1da95776459
Ref: library/zipfile zipfile Path open5776514
Ref: 1daa5776514
Ref: library/zipfile zipfile Path iterdir5776900
Ref: 1dab5776900
Ref: library/zipfile zipfile Path is_dir5776990
Ref: 1dac5776990
Ref: library/zipfile zipfile Path is_file5777095
Ref: 1dad5777095
Ref: library/zipfile zipfile Path exists5777196
Ref: 1dae5777196
Ref: library/zipfile zipfile Path read_text5777330
Ref: 1daf5777330
Ref: library/zipfile zipfile Path read_bytes5777568
Ref: 1db05777568
Node: PyZipFile Objects5777644
Ref: library/zipfile id35777777
Ref: 1db15777777
Ref: library/zipfile pyzipfile-objects5777777
Ref: 1db25777777
Ref: library/zipfile zipfile PyZipFile5777979
Ref: 9205777979
Ref: library/zipfile zipfile PyZipFile writepy5778293
Ref: 91f5778293
Node: ZipInfo Objects5781106
Ref: library/zipfile id45781249
Ref: 1db35781249
Ref: library/zipfile zipinfo-objects5781249
Ref: 1d955781249
Ref: library/zipfile zipfile ZipInfo from_file5781617
Ref: 5be5781617
Ref: library/zipfile zipfile ZipInfo is_dir5782677
Ref: 5c05782677
Ref: library/zipfile zipfile ZipInfo filename5782881
Ref: 1db45782881
Ref: library/zipfile zipfile ZipInfo date_time5782950
Ref: 1db55782950
Ref: library/zipfile zipfile ZipInfo compress_type5783731
Ref: 1db65783731
Ref: library/zipfile zipfile ZipInfo comment5783816
Ref: 1db75783816
Ref: library/zipfile zipfile ZipInfo extra5783929
Ref: 1db85783929
Ref: library/zipfile zipfile ZipInfo create_system5784130
Ref: 1db95784130
Ref: library/zipfile zipfile ZipInfo create_version5784205
Ref: 1dba5784205
Ref: library/zipfile zipfile ZipInfo extract_version5784288
Ref: 1dbb5784288
Ref: library/zipfile zipfile ZipInfo reserved5784372
Ref: 1dbc5784372
Ref: library/zipfile zipfile ZipInfo flag_bits5784422
Ref: 1dbd5784422
Ref: library/zipfile zipfile ZipInfo volume5784474
Ref: 1dbe5784474
Ref: library/zipfile zipfile ZipInfo internal_attr5784538
Ref: 1dbf5784538
Ref: library/zipfile zipfile ZipInfo external_attr5784600
Ref: 1dc05784600
Ref: library/zipfile zipfile ZipInfo header_offset5784667
Ref: 1dc15784667
Ref: library/zipfile zipfile ZipInfo CRC5784740
Ref: 1dc25784740
Ref: library/zipfile zipfile ZipInfo compress_size5784804
Ref: 1dc35784804
Ref: library/zipfile zipfile ZipInfo file_size5784874
Ref: 1d9f5784874
Ref: ZipInfo Objects-Footnote-15784978
Node: Command-Line Interface5785046
Ref: library/zipfile command-line-interface5785194
Ref: 1dc45785194
Ref: library/zipfile zipfile-commandline5785194
Ref: 1dc55785194
Node: Command-line options5785967
Ref: library/zipfile command-line-options5786046
Ref: 1dc95786046
Ref: library/zipfile cmdoption-zipfile-l5786107
Ref: 1dc85786107
Ref: library/zipfile cmdoption-zipfile-list5786138
Ref: 1dca5786138
Ref: library/zipfile cmdoption-zipfile-c5786205
Ref: 1dc65786205
Ref: library/zipfile cmdoption-zipfile-create5786260
Ref: 1dcb5786260
Ref: library/zipfile cmdoption-zipfile-e5786362
Ref: 1dc75786362
Ref: library/zipfile cmdoption-zipfile-extract5786406
Ref: 1dcc5786406
Ref: library/zipfile cmdoption-zipfile-t5786503
Ref: 1dcd5786503
Ref: library/zipfile cmdoption-zipfile-test5786534
Ref: 1dce5786534
Node: Decompression pitfalls5786618
Ref: library/zipfile decompression-pitfalls5786742
Ref: 1dcf5786742
Node: From file itself5787025
Ref: library/zipfile from-file-itself5787132
Ref: 1dd05787132
Node: File System limitations5787311
Ref: library/zipfile file-system-limitations5787448
Ref: 1dd15787448
Node: Resources limitations5787750
Ref: library/zipfile resources-limitations5787883
Ref: 1dd25787883
Ref: Resources limitations-Footnote-15788170
Node: Interruption5788217
Ref: library/zipfile interruption5788358
Ref: 1dd35788358
Node: Default behaviors of extraction5788564
Ref: library/zipfile default-behaviors-of-extraction5788675
Ref: 1dd45788675
Node: tarfile --- Read and write tar archive files5788940
Ref: library/tarfile doc5789085
Ref: 1dd55789085
Ref: library/tarfile module-tarfile5789085
Ref: 1025789085
Ref: library/tarfile pkzip-application-note5789085
Ref: 1dd65789085
Ref: library/tarfile tarfile-read-and-write-tar-archive-files5789085
Ref: 1dd75789085
Ref: library/tarfile tarfile open5790338
Ref: 76b5790338
Ref: library/tarfile tarfile is_tarfile5796601
Ref: 1ddc5796601
Ref: library/tarfile tarfile TarError5796820
Ref: 1ddd5796820
Ref: library/tarfile tarfile ReadError5796907
Ref: 1dd95796907
Ref: library/tarfile tarfile CompressionError5797076
Ref: 1dda5797076
Ref: library/tarfile tarfile StreamError5797223
Ref: 1dde5797223
Ref: library/tarfile tarfile ExtractError5797359
Ref: 1ddf5797359
Ref: library/tarfile tarfile HeaderError5797526
Ref: 1de05797526
Ref: library/tarfile tarfile ENCODING5797708
Ref: 1de25797708
Ref: library/tarfile tarfile USTAR_FORMAT5798056
Ref: 1de45798056
Ref: library/tarfile tarfile GNU_FORMAT5798123
Ref: 1de55798123
Ref: library/tarfile tarfile PAX_FORMAT5798175
Ref: 1de65798175
Ref: library/tarfile tarfile DEFAULT_FORMAT5798238
Ref: 1de75798238
Ref: tarfile --- Read and write tar archive files-Footnote-15799078
Ref: tarfile --- Read and write tar archive files-Footnote-25799144
Node: TarFile Objects5799216
Ref: library/tarfile id15799336
Ref: 1de85799336
Ref: library/tarfile tarfile-objects5799336
Ref: 1dd85799336
Ref: library/tarfile tarfile TarFile5800202
Ref: b915800202
Ref: library/tarfile tarfile TarFile open5803563
Ref: 1deb5803563
Ref: library/tarfile tarfile TarFile getmember5803734
Ref: 1dec5803734
Ref: library/tarfile tarfile TarFile getmembers5804065
Ref: 76f5804065
Ref: library/tarfile tarfile TarFile getnames5804258
Ref: 1ded5804258
Ref: library/tarfile tarfile TarFile list5804425
Ref: 76e5804425
Ref: library/tarfile tarfile TarFile next5804872
Ref: 1dee5804872
Ref: library/tarfile tarfile TarFile extractall5805098
Ref: 76c5805098
Ref: library/tarfile tarfile TarFile extract5806396
Ref: 76d5806396
Ref: library/tarfile tarfile TarFile extractfile5807591
Ref: 1def5807591
Ref: library/tarfile tarfile TarFile add5807979
Ref: 4815807979
Ref: library/tarfile tarfile TarFile addfile5808873
Ref: 1df05808873
Ref: library/tarfile tarfile TarFile gettarinfo5809246
Ref: 1df15809246
Ref: library/tarfile tarfile TarFile close5810384
Ref: 1df55810384
Ref: library/tarfile tarfile TarFile pax_headers5810532
Ref: 1df65810532
Node: TarInfo Objects5810634
Ref: library/tarfile id25810788
Ref: 1df75810788
Ref: library/tarfile tarinfo-objects5810788
Ref: 1de95810788
Ref: library/tarfile tarfile TarInfo5811268
Ref: b925811268
Ref: library/tarfile tarfile TarInfo frombuf5811350
Ref: 1de15811350
Ref: library/tarfile tarfile TarInfo fromtarfile5811569
Ref: 1df85811569
Ref: library/tarfile tarfile TarInfo tobuf5811755
Ref: 1df95811755
Ref: library/tarfile tarfile TarInfo name5812191
Ref: 1df45812191
Ref: library/tarfile tarfile TarInfo size5812251
Ref: 1df35812251
Ref: library/tarfile tarfile TarInfo mtime5812298
Ref: 1dfa5812298
Ref: library/tarfile tarfile TarInfo mode5812358
Ref: 1dfb5812358
Ref: library/tarfile tarfile TarInfo type5812407
Ref: 1dfc5812407
Ref: library/tarfile tarfile TarInfo linkname5812782
Ref: 1dfd5812782
Ref: library/tarfile tarfile TarInfo uid5812947
Ref: 1dfe5812947
Ref: library/tarfile tarfile TarInfo gid5813033
Ref: 1dff5813033
Ref: library/tarfile tarfile TarInfo uname5813120
Ref: 1e005813120
Ref: library/tarfile tarfile TarInfo gname5813164
Ref: 1e015813164
Ref: library/tarfile tarfile TarInfo pax_headers5813209
Ref: 1e025813209
Ref: library/tarfile tarfile TarInfo isfile5813406
Ref: 1e035813406
Ref: library/tarfile tarfile TarInfo isreg5813520
Ref: 1e045813520
Ref: library/tarfile tarfile TarInfo isdir5813592
Ref: 1e055813592
Ref: library/tarfile tarfile TarInfo issym5813680
Ref: 1e065813680
Ref: library/tarfile tarfile TarInfo islnk5813772
Ref: 1e075813772
Ref: library/tarfile tarfile TarInfo ischr5813860
Ref: 1e085813860
Ref: library/tarfile tarfile TarInfo isblk5813955
Ref: 1e095813955
Ref: library/tarfile tarfile TarInfo isfifo5814046
Ref: 1e0a5814046
Ref: library/tarfile tarfile TarInfo isdev5814130
Ref: 1e0b5814130
Node: Command-Line Interface<2>5814257
Ref: library/tarfile command-line-interface5814407
Ref: 1e0c5814407
Ref: library/tarfile tarfile-commandline5814407
Ref: 8ed5814407
Node: Command-line options<2>5815359
Ref: library/tarfile command-line-options5815444
Ref: 1e105815444
Ref: library/tarfile cmdoption-tarfile-l5815505
Ref: 1e0f5815505
Ref: library/tarfile cmdoption-tarfile-list5815536
Ref: 1e115815536
Ref: library/tarfile cmdoption-tarfile-c5815603
Ref: 1e0d5815603
Ref: library/tarfile cmdoption-tarfile-create5815658
Ref: 1e125815658
Ref: library/tarfile cmdoption-tarfile-e5815760
Ref: 1e0e5815760
Ref: library/tarfile cmdoption-tarfile-extract5815806
Ref: 1e135815806
Ref: library/tarfile cmdoption-tarfile-t5815948
Ref: 1e145815948
Ref: library/tarfile cmdoption-tarfile-test5815979
Ref: 1e155815979
Ref: library/tarfile cmdoption-tarfile-v5816063
Ref: 1e165816063
Node: Examples<6>5816118
Ref: library/tarfile examples5816274
Ref: 1e175816274
Ref: library/tarfile tar-examples5816274
Ref: 1ddb5816274
Node: Supported tar formats5818147
Ref: library/tarfile supported-tar-formats5818292
Ref: 1e185818292
Ref: library/tarfile tar-formats5818292
Ref: 1de35818292
Node: Unicode issues5820514
Ref: library/tarfile tar-unicode5820639
Ref: 1dea5820639
Ref: library/tarfile unicode-issues5820639
Ref: 1e195820639
Node: 檔案格式5822612
Ref: library/fileformats doc5822761
Ref: 1e1b5822761
Ref: library/fileformats file-formats5822761
Ref: 1e1c5822761
Ref: library/fileformats fileformats5822761
Ref: 1e1d5822761
Node: csv --- CSV File Reading and Writing5823353
Ref: library/csv doc5823489
Ref: 1e1e5823489
Ref: library/csv csv-csv-file-reading-and-writing5823489
Ref: 1e1f5823489
Ref: library/csv module-csv5823489
Ref: 2a5823489
Ref: csv --- CSV File Reading and Writing-Footnote-15825389
Ref: csv --- CSV File Reading and Writing-Footnote-25825451
Ref: csv --- CSV File Reading and Writing-Footnote-35825500
Node: Module Contents<3>5825549
Ref: library/csv csv-contents5825683
Ref: 1e205825683
Ref: library/csv module-contents5825683
Ref: 1e215825683
Ref: library/csv csv reader5825794
Ref: ec05825794
Ref: library/csv csv writer5827462
Ref: e015827462
Ref: library/csv csv register_dialect5829217
Ref: 1e255829217
Ref: library/csv csv unregister_dialect5829688
Ref: 1e265829688
Ref: library/csv csv get_dialect5829893
Ref: 1e285829893
Ref: library/csv csv list_dialects5830122
Ref: 1e235830122
Ref: library/csv csv field_size_limit5830207
Ref: 1e295830207
Ref: library/csv csv DictReader5830440
Ref: 1be5830440
Ref: library/csv csv DictWriter5832014
Ref: b7f5832014
Ref: library/csv csv Dialect5833678
Ref: 1e225833678
Ref: library/csv csv excel5833922
Ref: 1e2a5833922
Ref: library/csv csv excel_tab5834106
Ref: 1e2b5834106
Ref: library/csv csv unix_dialect5834312
Ref: b7e5834312
Ref: library/csv csv Sniffer5834612
Ref: 1e2c5834612
Ref: library/csv csv Sniffer sniff5834782
Ref: 1e2d5834782
Ref: library/csv csv Sniffer has_header5835110
Ref: 1e2e5835110
Ref: library/csv csv QUOTE_ALL5835665
Ref: 1e2f5835665
Ref: library/csv csv QUOTE_MINIMAL5835754
Ref: 1e305835754
Ref: library/csv csv QUOTE_NONNUMERIC5835975
Ref: 1e315835975
Ref: library/csv csv QUOTE_NONE5836170
Ref: 1e325836170
Ref: library/csv csv Error5836669
Ref: 1e275836669
Ref: Module Contents<3>-Footnote-15836792
Ref: Module Contents<3>-Footnote-25837137
Node: Dialects and Formatting Parameters5837482
Ref: library/csv csv-fmt-params5837639
Ref: 1e245837639
Ref: library/csv dialects-and-formatting-parameters5837639
Ref: 1e335837639
Ref: library/csv csv Dialect delimiter5838431
Ref: 1e345838431
Ref: library/csv csv Dialect doublequote5838548
Ref: 1e355838548
Ref: library/csv csv Dialect escapechar5839017
Ref: 1e365839017
Ref: library/csv csv Dialect lineterminator5839394
Ref: 1e375839394
Ref: library/csv csv Dialect quotechar5839748
Ref: 1e385839748
Ref: library/csv csv Dialect quoting5839975
Ref: 1e395839975
Ref: library/csv csv Dialect skipinitialspace5840247
Ref: 1e3a5840247
Ref: library/csv csv Dialect strict5840413
Ref: 1e3b5840413
Node: Reader Objects5840550
Ref: library/csv reader-objects5840703
Ref: 1e3c5840703
Ref: library/csv csv csvreader __next__5840896
Ref: 1e3d5840896
Ref: library/csv csv csvreader dialect5841281
Ref: 1e3e5841281
Ref: library/csv csv csvreader line_num5841379
Ref: 1e3f5841379
Ref: library/csv csv csvreader fieldnames5841628
Ref: 1e405841628
Node: Writer Objects5841829
Ref: library/csv writer-objects5841959
Ref: 1e415841959
Ref: library/csv csv csvwriter writerow5842560
Ref: 6c95842560
Ref: library/csv csv csvwriter writerows5842870
Ref: 1e425842870
Ref: library/csv csv csvwriter dialect5843139
Ref: 1e435843139
Ref: library/csv csv DictWriter writeheader5843291
Ref: b805843291
Node: Examples<7>5843770
Ref: library/csv csv-examples5843877
Ref: 1e445843877
Ref: library/csv examples5843877
Ref: 1e455843877
Node: configparser --- Configuration file parser5845902
Ref: library/configparser doc5846078
Ref: 1e465846078
Ref: library/configparser configparser-configuration-file-parser5846078
Ref: 1e475846078
Ref: library/configparser module-configparser5846078
Ref: 235846078
Ref: configparser --- Configuration file parser-Footnote-15847373
Node: Quick Start5847444
Ref: library/configparser quick-start5847562
Ref: 1e485847562
Ref: Quick Start-Footnote-15850243
Ref: Quick Start-Footnote-25850449
Node: Supported Datatypes5850655
Ref: library/configparser supported-datatypes5850797
Ref: 1e4c5850797
Ref: Supported Datatypes-Footnote-15852119
Ref: Supported Datatypes-Footnote-25852325
Node: Fallback Values5852531
Ref: library/configparser fallback-values5852690
Ref: 1e505852690
Node: Supported INI File Structure5854188
Ref: library/configparser supported-ini-file-structure5854351
Ref: 1e495854351
Ref: Supported INI File Structure-Footnote-15856627
Ref: Supported INI File Structure-Footnote-25856833
Ref: Supported INI File Structure-Footnote-35857039
Ref: Supported INI File Structure-Footnote-45857245
Node: Interpolation of values5857451
Ref: library/configparser interpolation-of-values5857622
Ref: 1e515857622
Ref: library/configparser configparser BasicInterpolation5857858
Ref: 1e525857858
Ref: library/configparser configparser ExtendedInterpolation5859138
Ref: be15859138
Ref: Interpolation of values-Footnote-15860620
Node: Mapping Protocol Access5860826
Ref: library/configparser mapping-protocol-access5860997
Ref: 1e4a5860997
Ref: Mapping Protocol Access-Footnote-15863884
Node: Customizing Parser Behaviour5864090
Ref: library/configparser customizing-parser-behaviour5864257
Ref: 1e4b5864257
Ref: library/configparser configparser ConfigParser BOOLEAN_STATES5874982
Ref: 1e545874982
Ref: library/configparser configparser ConfigParser SECTCRE5877173
Ref: 1e555877173
Node: Legacy API Examples5878414
Ref: library/configparser legacy-api-examples5878578
Ref: 1e565878578
Node: ConfigParser Objects5882396
Ref: library/configparser configparser-objects5882555
Ref: 1e575882555
Ref: library/configparser id115882555
Ref: 1e585882555
Ref: library/configparser configparser ConfigParser5882616
Ref: 4af5882616
Ref: library/configparser configparser ConfigParser defaults5886375
Ref: 1e5b5886375
Ref: library/configparser configparser ConfigParser sections5886481
Ref: 1e5c5886481
Ref: library/configparser configparser ConfigParser add_section5886630
Ref: c095886630
Ref: library/configparser configparser ConfigParser has_section5887116
Ref: 1e5d5887116
Ref: library/configparser configparser ConfigParser options5887298
Ref: 1e5e5887298
Ref: library/configparser configparser ConfigParser has_option5887414
Ref: 1e5f5887414
Ref: library/configparser configparser ConfigParser read5887720
Ref: 10a95887720
Ref: library/configparser configparser ConfigParser read_file5889435
Ref: 1e605889435
Ref: library/configparser configparser ConfigParser read_string5889920
Ref: 1e625889920
Ref: library/configparser configparser ConfigParser read_dict5890271
Ref: 1e5a5890271
Ref: library/configparser configparser ConfigParser get5890970
Ref: c075890970
Ref: library/configparser configparser ConfigParser getint5891923
Ref: 1e4e5891923
Ref: library/configparser configparser ConfigParser getfloat5892217
Ref: 1e4f5892217
Ref: library/configparser configparser ConfigParser getboolean5892526
Ref: 1e4d5892526
Ref: library/configparser configparser ConfigParser items5893262
Ref: 1e635893262
Ref: library/configparser configparser ConfigParser set5893903
Ref: c085893903
Ref: library/configparser configparser ConfigParser write5894194
Ref: 1e535894194
Ref: library/configparser configparser ConfigParser remove_option5894641
Ref: 1e655894641
Ref: library/configparser configparser ConfigParser remove_section5894961
Ref: 1e665894961
Ref: library/configparser configparser ConfigParser optionxform5895179
Ref: 1e595895179
Ref: library/configparser configparser ConfigParser readfp5896158
Ref: 1e615896158
Ref: library/configparser configparser MAX_INTERPOLATION_DEPTH5896904
Ref: 1e675896904
Node: RawConfigParser Objects5897130
Ref: library/configparser id135897283
Ref: 1e685897283
Ref: library/configparser rawconfigparser-objects5897283
Ref: 1e695897283
Ref: library/configparser configparser RawConfigParser5897352
Ref: 8765897352
Ref: library/configparser configparser RawConfigParser add_section5898328
Ref: 1e6a5898328
Ref: library/configparser configparser RawConfigParser set5898808
Ref: 1e6b5898808
Node: Exceptions<4>5899641
Ref: library/configparser exceptions5899765
Ref: 1e6c5899765
Ref: library/configparser configparser Error5899808
Ref: 1e6d5899808
Ref: library/configparser configparser NoSectionError5899907
Ref: 1e645899907
Ref: library/configparser configparser DuplicateSectionError5900010
Ref: c0a5900010
Ref: library/configparser configparser DuplicateOptionError5900417
Ref: c0b5900417
Ref: library/configparser configparser NoOptionError5900774
Ref: 1e6e5900774
Ref: library/configparser configparser InterpolationError5900905
Ref: 1e6f5900905
Ref: library/configparser configparser InterpolationDepthError5901047
Ref: 1e705901047
Ref: library/configparser configparser InterpolationMissingOptionError5901304
Ref: 1e715901304
Ref: library/configparser configparser InterpolationSyntaxError5901490
Ref: 1e725901490
Ref: library/configparser configparser MissingSectionHeaderError5901715
Ref: 1e735901715
Ref: library/configparser configparser ParsingError5901857
Ref: 1e745901857
Node: netrc --- netrc file processing5902115
Ref: library/netrc doc5902292
Ref: 1e755902292
Ref: library/netrc module-netrc5902292
Ref: bf5902292
Ref: library/netrc netrc-netrc-file-processing5902292
Ref: 1e765902292
Ref: library/netrc netrc netrc5902611
Ref: 10a55902611
Ref: library/netrc netrc NetrcParseError5903855
Ref: 1e775903855
Ref: netrc --- netrc file processing-Footnote-15904322
Node: netrc Objects5904386
Ref: library/netrc id15904467
Ref: 1e785904467
Ref: library/netrc netrc-objects5904467
Ref: 1e795904467
Ref: library/netrc netrc netrc authenticators5904572
Ref: 1e7a5904572
Ref: library/netrc netrc netrc __repr__5904924
Ref: 1e7b5904924
Ref: library/netrc netrc netrc hosts5905154
Ref: 1e7c5905154
Ref: library/netrc netrc netrc macros5905349
Ref: 1e7d5905349
Node: xdrlib --- Encode and decode XDR data5905754
Ref: library/xdrlib doc5905941
Ref: 1e7e5905941
Ref: library/xdrlib module-xdrlib5905941
Ref: 1335905941
Ref: library/xdrlib xdrlib-encode-and-decode-xdr-data5905941
Ref: 1e7f5905941
Ref: library/xdrlib xdrlib Packer5906546
Ref: 1e805906546
Ref: library/xdrlib xdrlib Unpacker5906730
Ref: 1e815906730
Ref: xdrlib --- Encode and decode XDR data-Footnote-15907383
Ref: xdrlib --- Encode and decode XDR data-Footnote-25907448
Ref: xdrlib --- Encode and decode XDR data-Footnote-35907497
Ref: xdrlib --- Encode and decode XDR data-Footnote-45907546
Ref: xdrlib --- Encode and decode XDR data-Footnote-55907595
Node: Packer Objects5907644
Ref: library/xdrlib packer-objects5907757
Ref: 1e825907757
Ref: library/xdrlib xdr-packer-objects5907757
Ref: 1e835907757
Ref: library/xdrlib xdrlib Packer get_buffer5907865
Ref: 1e845907865
Ref: library/xdrlib xdrlib Packer reset5907956
Ref: 1e855907956
Ref: library/xdrlib xdrlib Packer pack_float5908398
Ref: 1e865908398
Ref: library/xdrlib xdrlib Packer pack_double5908507
Ref: 1e875908507
Ref: library/xdrlib xdrlib Packer pack_fstring5908689
Ref: 1e885908689
Ref: library/xdrlib xdrlib Packer pack_fopaque5908946
Ref: 1e895908946
Ref: library/xdrlib xdrlib Packer pack_string5909088
Ref: 1e8a5909088
Ref: library/xdrlib xdrlib Packer pack_opaque5909313
Ref: 1e8b5909313
Ref: library/xdrlib xdrlib Packer pack_bytes5909453
Ref: 1e8c5909453
Ref: library/xdrlib xdrlib Packer pack_list5909643
Ref: 1e8d5909643
Ref: library/xdrlib xdrlib Packer pack_farray5910339
Ref: 1e8e5910339
Ref: library/xdrlib xdrlib Packer pack_array5910707
Ref: 1e8f5910707
Node: Unpacker Objects5910964
Ref: library/xdrlib unpacker-objects5911099
Ref: 1e905911099
Ref: library/xdrlib xdr-unpacker-objects5911099
Ref: 1e915911099
Ref: library/xdrlib xdrlib Unpacker reset5911215
Ref: 1e925911215
Ref: library/xdrlib xdrlib Unpacker get_position5911310
Ref: 1e935911310
Ref: library/xdrlib xdrlib Unpacker set_position5911416
Ref: 1e945911416
Ref: library/xdrlib xdrlib Unpacker get_buffer5911631
Ref: 1e955911631
Ref: library/xdrlib xdrlib Unpacker done5911731
Ref: 1e965911731
Ref: library/xdrlib xdrlib Unpacker unpack_float5912124
Ref: 1e985912124
Ref: library/xdrlib xdrlib Unpacker unpack_double5912224
Ref: 1e995912224
Ref: library/xdrlib xdrlib Unpacker unpack_fstring5912447
Ref: 1e9a5912447
Ref: library/xdrlib xdrlib Unpacker unpack_fopaque5912664
Ref: 1e9b5912664
Ref: library/xdrlib xdrlib Unpacker unpack_string5912820
Ref: 1e9c5912820
Ref: library/xdrlib xdrlib Unpacker unpack_opaque5913063
Ref: 1e9d5913063
Ref: library/xdrlib xdrlib Unpacker unpack_bytes5913219
Ref: 1e9e5913219
Ref: library/xdrlib xdrlib Unpacker unpack_list5913426
Ref: 1e9f5913426
Ref: library/xdrlib xdrlib Unpacker unpack_farray5913837
Ref: 1ea05913837
Ref: library/xdrlib xdrlib Unpacker unpack_array5914114
Ref: 1ea15914114
Node: Exceptions<5>5914395
Ref: library/xdrlib exceptions5914507
Ref: 1ea25914507
Ref: library/xdrlib xdr-exceptions5914507
Ref: 1ea35914507
Ref: library/xdrlib xdrlib Error5914605
Ref: 1e975914605
Ref: library/xdrlib xdrlib ConversionError5914769
Ref: 1ea45914769
Node: plistlib --- Generate and parse Mac OS X plist files5915157
Ref: library/plistlib doc5915304
Ref: 1ea55915304
Ref: library/plistlib module-plistlib5915304
Ref: d05915304
Ref: library/plistlib plistlib-generate-and-parse-mac-os-x-plist-files5915304
Ref: 1ea65915304
Ref: library/plistlib plistlib load5916658
Ref: 8905916658
Ref: library/plistlib plistlib loads5917822
Ref: 8925917822
Ref: library/plistlib plistlib dump5918058
Ref: 8915918058
Ref: library/plistlib plistlib dumps5919152
Ref: 8935919152
Ref: library/plistlib plistlib readPlist5919485
Ref: 4845919485
Ref: library/plistlib plistlib writePlist5920103
Ref: 94a5920103
Ref: library/plistlib plistlib readPlistFromBytes5920351
Ref: 4855920351
Ref: library/plistlib plistlib writePlistToBytes5920760
Ref: 94b5920760
Ref: library/plistlib plistlib Data5920977
Ref: 94c5920977
Ref: library/plistlib plistlib UID5921377
Ref: 2115921377
Ref: library/plistlib plistlib FMT_XML5921780
Ref: 8945921780
Ref: library/plistlib plistlib FMT_BINARY5921870
Ref: 8955921870
Ref: plistlib --- Generate and parse Mac OS X plist files-Footnote-15922036
Ref: plistlib --- Generate and parse Mac OS X plist files-Footnote-25922103
Node: Examples<8>5922202
Ref: library/plistlib examples5922302
Ref: 1ea75922302
Node: Cryptographic Services5923044
Ref: library/crypto doc5923205
Ref: 1ea85923205
Ref: library/crypto crypto5923205
Ref: 1ea95923205
Ref: library/crypto cryptographic-services5923205
Ref: 1eaa5923205
Node: hashlib --- Secure hashes and message digests5923838
Ref: library/hashlib doc5924000
Ref: 1eab5924000
Ref: library/hashlib hashlib-secure-hashes-and-message-digests5924000
Ref: 1eac5924000
Ref: library/hashlib module-hashlib5924000
Ref: 8d5924000
Ref: hashlib --- Secure hashes and message digests-Footnote-15925010
Ref: hashlib --- Secure hashes and message digests-Footnote-25925076
Node: Hash algorithms5925125
Ref: library/hashlib hash-algorithms5925260
Ref: 1ead5925260
Ref: library/hashlib id15925260
Ref: 1eae5925260
Ref: library/hashlib hashlib new5927502
Ref: 1eaf5927502
Ref: library/hashlib hashlib algorithms_guaranteed5928203
Ref: d015928203
Ref: library/hashlib hashlib algorithms_available5928530
Ref: d025928530
Ref: library/hashlib hashlib hash digest_size5929064
Ref: 1eb05929064
Ref: library/hashlib hashlib hash block_size5929139
Ref: 1eb15929139
Ref: library/hashlib hashlib hash name5929273
Ref: 8575929273
Ref: library/hashlib hashlib hash update5929682
Ref: 1eb25929682
Ref: library/hashlib hashlib hash digest5930166
Ref: 1eb35930166
Ref: library/hashlib hashlib hash hexdigest5930412
Ref: 1eb45930412
Ref: library/hashlib hashlib hash copy5930689
Ref: 1eb55930689
Node: SHAKE variable length digests5930878
Ref: library/hashlib shake-variable-length-digests5931036
Ref: 1eb65931036
Ref: library/hashlib hashlib shake digest5931365
Ref: 102a5931365
Ref: library/hashlib hashlib shake hexdigest5931595
Ref: 102b5931595
Node: Key derivation5931879
Ref: library/hashlib key-derivation5932028
Ref: 1eb75932028
Ref: library/hashlib hashlib pbkdf2_hmac5932339
Ref: 7eb5932339
Ref: library/hashlib hashlib scrypt5933768
Ref: 4d75933768
Ref: Key derivation-Footnote-15934533
Ref: Key derivation-Footnote-25934595
Node: BLAKE25934644
Ref: library/hashlib blake25934755
Ref: 1eb85934755
Ref: BLAKE2-Footnote-15935477
Ref: BLAKE2-Footnote-25935504
Ref: BLAKE2-Footnote-35935553
Node: Creating hash objects5935631
Ref: library/hashlib creating-hash-objects5935716
Ref: 1eb95935716
Ref: library/hashlib hashlib blake2b5935843
Ref: 5515935843
Ref: library/hashlib hashlib blake2s5936045
Ref: 5525936045
Ref: Creating hash objects-Footnote-15938977
Node: Constants<5>5939024
Ref: library/hashlib constants5939129
Ref: 1eba5939129
Ref: library/hashlib hashlib blake2b SALT_SIZE5939168
Ref: 1ebb5939168
Ref: library/hashlib hashlib blake2s SALT_SIZE5939197
Ref: 1ebc5939197
Ref: library/hashlib hashlib blake2b PERSON_SIZE5939282
Ref: 1ebd5939282
Ref: library/hashlib hashlib blake2s PERSON_SIZE5939313
Ref: 1ebe5939313
Ref: library/hashlib hashlib blake2b MAX_KEY_SIZE5939418
Ref: 1ebf5939418
Ref: library/hashlib hashlib blake2s MAX_KEY_SIZE5939450
Ref: 1ec05939450
Ref: library/hashlib hashlib blake2b MAX_DIGEST_SIZE5939501
Ref: 1ec15939501
Ref: library/hashlib hashlib blake2s MAX_DIGEST_SIZE5939536
Ref: 1ec25939536
Node: Examples<9>5939627
Ref: library/hashlib examples5939718
Ref: 1ec35939718
Node: Simple hashing5939892
Ref: library/hashlib simple-hashing5939991
Ref: 1ec45939991
Node: Using different digest sizes5941413
Ref: library/hashlib using-different-digest-sizes5941534
Ref: 1ec55941534
Node: Keyed hashing5942675
Ref: library/hashlib keyed-hashing5942800
Ref: 1ec65942800
Ref: Keyed hashing-Footnote-15944811
Node: Randomized hashing5944889
Ref: library/hashlib randomized-hashing5945001
Ref: 1ec75945001
Ref: Randomized hashing-Footnote-15947604
Ref: Randomized hashing-Footnote-25947671
Node: Personalization5947702
Ref: library/hashlib personalization5947810
Ref: 1ec85947810
Ref: Personalization-Footnote-15949805
Node: Tree mode5949873
Ref: library/hashlib tree-mode5949954
Ref: 1ec95949954
Node: Credits5951205
Ref: library/hashlib credits5951275
Ref: 1eca5951275
Ref: Credits-Footnote-15953508
Ref: Credits-Footnote-25953535
Ref: Credits-Footnote-35953604
Ref: Credits-Footnote-45953638
Ref: Credits-Footnote-55953675
Ref: Credits-Footnote-65953718
Node: hmac --- Keyed-Hashing for Message Authentication5953761
Ref: library/hmac doc5953995
Ref: 1ecb5953995
Ref: library/hmac hmac-keyed-hashing-for-message-authentication5953995
Ref: 1ecc5953995
Ref: library/hmac module-hmac5953995
Ref: 8f5953995
Ref: library/hmac hmac new5954287
Ref: 8595954287
Ref: library/hmac hmac digest5955196
Ref: 3955955196
Ref: library/hmac hmac HMAC update5955833
Ref: 85a5955833
Ref: library/hmac hmac HMAC digest5956178
Ref: 1ecd5956178
Ref: library/hmac hmac HMAC hexdigest5956792
Ref: 1ece5956792
Ref: library/hmac hmac HMAC copy5957385
Ref: 1ecf5957385
Ref: library/hmac hmac HMAC digest_size5957625
Ref: 85d5957625
Ref: library/hmac hmac HMAC block_size5957709
Ref: 85b5957709
Ref: library/hmac hmac HMAC name5957824
Ref: 85c5957824
Ref: library/hmac hmac compare_digest5958012
Ref: a115958012
Ref: hmac --- Keyed-Hashing for Message Authentication-Footnote-15958831
Ref: hmac --- Keyed-Hashing for Message Authentication-Footnote-25958894
Node: secrets --- Generate secure random numbers for managing secrets5958943
Ref: library/secrets doc5959123
Ref: 1ed05959123
Ref: library/secrets module-secrets5959123
Ref: e55959123
Ref: library/secrets secrets-generate-secure-random-numbers-for-managing-secrets5959123
Ref: 1ed15959123
Ref: secrets --- Generate secure random numbers for managing secrets-Footnote-15959984
Ref: secrets --- Generate secure random numbers for managing secrets-Footnote-25960050
Node: Random numbers5960099
Ref: library/secrets random-numbers5960239
Ref: 1ed25960239
Ref: library/secrets secrets SystemRandom5960412
Ref: 1ed35960412
Ref: library/secrets secrets choice5960630
Ref: 1ed45960630
Ref: library/secrets secrets randbelow5960735
Ref: 1ed55960735
Ref: library/secrets secrets randbits5960819
Ref: 1ed65960819
Node: Generating tokens5960895
Ref: library/secrets generating-tokens5961059
Ref: 1ed75961059
Ref: library/secrets secrets token_bytes5961278
Ref: 1ed85961278
Ref: library/secrets secrets token_hex5961569
Ref: 1ed95961569
Ref: library/secrets secrets token_urlsafe5961903
Ref: 1eda5961903
Node: How many bytes should tokens use?5962331
Ref: library/secrets how-many-bytes-should-tokens-use5962418
Ref: 1edb5962418
Ref: How many bytes should tokens use?-Footnote-15963447
Node: Other functions5963504
Ref: library/secrets other-functions5963680
Ref: 1edc5963680
Ref: library/secrets secrets compare_digest5963731
Ref: 1edd5963731
Ref: Other functions-Footnote-15964022
Node: Recipes and best practices5964079
Ref: library/secrets recipes-and-best-practices5964229
Ref: 1ede5964229
Ref: Recipes and best practices-Footnote-15965971
Ref: Recipes and best practices-Footnote-25966026
Node: Generic Operating System Services5966056
Ref: library/allos doc5966225
Ref: 1edf5966225
Ref: library/allos allos5966225
Ref: 1ee05966225
Ref: library/allos generic-operating-system-services5966225
Ref: 1ee15966225
Node: os --- Miscellaneous operating system interfaces5968201
Ref: library/os doc5968370
Ref: 1ee25968370
Ref: library/os module-os5968370
Ref: c55968370
Ref: library/os os-miscellaneous-operating-system-interfaces5968370
Ref: 1ee35968370
Ref: library/os os error5970164
Ref: 1ee45970164
Ref: library/os os name5970249
Ref: 1ee55970249
Ref: library/os os-filenames5970691
Ref: 1e1a5970691
Ref: os --- Miscellaneous operating system interfaces-Footnote-15971096
Node: File Names Command Line Arguments and Environment Variables5971157
Ref: library/os file-names-command-line-arguments-and-environment-variables5971328
Ref: 1ee65971328
Ref: library/os filesystem-encoding5971328
Ref: 1ee75971328
Node: Process Parameters5972323
Ref: library/os os-procinfo5972523
Ref: 1ee85972523
Ref: library/os process-parameters5972523
Ref: 1ee95972523
Ref: library/os os ctermid5972677
Ref: 1eea5972677
Ref: library/os os environ5972832
Ref: b3c5972832
Ref: library/os os environb5974727
Ref: b995974727
Ref: library/os os fsencode5975305
Ref: 4f45975305
Ref: library/os os fsdecode5975722
Ref: 4f35975722
Ref: library/os os fspath5976143
Ref: 4f25976143
Ref: library/os os PathLike5976550
Ref: 4f05976550
Ref: library/os os PathLike __fspath__5976726
Ref: 4f15976726
Ref: library/os os getenv5977002
Ref: 1eed5977002
Ref: library/os os getenvb5977480
Ref: b985977480
Ref: library/os os get_exec_path5977862
Ref: 1eee5977862
Ref: library/os os getegid5978237
Ref: 1eef5978237
Ref: library/os os geteuid5978462
Ref: 1ef05978462
Ref: library/os os getgid5978584
Ref: 1ef15978584
Ref: library/os os getgrouplist5978704
Ref: a605978704
Ref: library/os os getgroups5979014
Ref: 1ef25979014
Ref: library/os os getlogin5980240
Ref: 1ef45980240
Ref: library/os os getpgid5980720
Ref: 1ef65980720
Ref: library/os os getpgrp5980943
Ref: 1ef75980943
Ref: library/os os getpid5981059
Ref: 1ef85981059
Ref: library/os os getppid5981122
Ref: 1ef95981122
Ref: library/os os getpriority5981481
Ref: a4b5981481
Ref: library/os os PRIO_PROCESS5982109
Ref: 1efa5982109
Ref: library/os os PRIO_PGRP5982135
Ref: 1efb5982135
Ref: library/os os PRIO_USER5982158
Ref: 1efc5982158
Ref: library/os os getresuid5982342
Ref: cb05982342
Ref: library/os os getresgid5982549
Ref: caf5982549
Ref: library/os os getuid5982757
Ref: 1efd5982757
Ref: library/os os initgroups5982873
Ref: cb35982873
Ref: library/os os putenv5983157
Ref: 1eeb5983157
Ref: library/os os setegid5984114
Ref: 1eff5984114
Ref: library/os os seteuid5984238
Ref: 1f005984238
Ref: library/os os setgid5984361
Ref: 1f015984361
Ref: library/os os setgroups5984472
Ref: 1ef35984472
Ref: library/os os setpgrp5985120
Ref: 1f025985120
Ref: library/os os setpgid5985354
Ref: 1f035985354
Ref: library/os os setpriority5985616
Ref: a4c5985616
Ref: library/os os setregid5986389
Ref: 1f045986389
Ref: library/os os setresgid5986530
Ref: cb15986530
Ref: library/os os setresuid5986710
Ref: cb25986710
Ref: library/os os setreuid5986889
Ref: 1f055986889
Ref: library/os os getsid5987029
Ref: 1f065987029
Ref: library/os os setsid5987185
Ref: f335987185
Ref: library/os os setuid5987338
Ref: 1f075987338
Ref: library/os os strerror5987449
Ref: 1f085987449
Ref: library/os os supports_bytes_environ5987690
Ref: b975987690
Ref: library/os os umask5987853
Ref: 1f095987853
Ref: library/os os uname5987949
Ref: a625987949
Ref: library/os os unsetenv5988990
Ref: d485988990
Node: File Object Creation5989725
Ref: library/os file-object-creation5989892
Ref: 1f0b5989892
Ref: library/os os-newstreams5989892
Ref: 1f0c5989892
Ref: library/os os fdopen5990067
Ref: 14365990067
Node: File Descriptor Operations5990392
Ref: library/os file-descriptor-operations5990562
Ref: 1f0d5990562
Ref: library/os os-fd-ops5990562
Ref: 1f0e5990562
Ref: library/os os close5991399
Ref: 3d75991399
Ref: library/os os closerange5991841
Ref: 1f115991841
Ref: library/os os copy_file_range5992185
Ref: 1f125992185
Ref: library/os os device_encoding5993208
Ref: 1f145993208
Ref: library/os os dup5993399
Ref: f995993399
Ref: library/os os dup25993752
Ref: 3c35993752
Ref: library/os os fchmod5994191
Ref: 6615994191
Ref: library/os os fchown5994595
Ref: 6625994595
Ref: library/os os fdatasync5995053
Ref: 6635995053
Ref: library/os os fpathconf5995284
Ref: 1f155995284
Ref: library/os os fstat5996311
Ref: 6645996311
Ref: library/os os fstatvfs5996568
Ref: 6655996568
Ref: library/os os fsync5996840
Ref: 6665996840
Ref: library/os os ftruncate5997323
Ref: 6675997323
Ref: library/os os get_blocking5997753
Ref: 7265997753
Ref: library/os os isatty5998089
Ref: 1f175998089
Ref: library/os os lockf5998238
Ref: a5f5998238
Ref: library/os os F_LOCK5998750
Ref: 1f185998750
Ref: library/os os F_TLOCK5998770
Ref: 1f195998770
Ref: library/os os F_ULOCK5998791
Ref: 1f1a5998791
Ref: library/os os F_TEST5998812
Ref: 1f1b5998812
Ref: library/os os lseek5998964
Ref: a635998964
Ref: library/os os SEEK_SET5999432
Ref: d995999432
Ref: library/os os SEEK_CUR5999454
Ref: d9a5999454
Ref: library/os os SEEK_END5999476
Ref: d9b5999476
Ref: library/os os open5999735
Ref: 66a5999735
Ref: library/os os O_RDONLY6001761
Ref: 1f1c6001761
Ref: library/os os O_WRONLY6001783
Ref: 1f1d6001783
Ref: library/os os O_RDWR6001805
Ref: 1f1f6001805
Ref: library/os os O_APPEND6001825
Ref: 1f206001825
Ref: library/os os O_CREAT6001847
Ref: 1f216001847
Ref: library/os os O_EXCL6001868
Ref: 1c716001868
Ref: library/os os O_TRUNC6001888
Ref: 1f226001888
Ref: library/os os O_DSYNC6001971
Ref: 1f236001971
Ref: library/os os O_RSYNC6001992
Ref: 1f246001992
Ref: library/os os O_SYNC6002013
Ref: 1f256002013
Ref: library/os os O_NDELAY6002033
Ref: 1f266002033
Ref: library/os os O_NONBLOCK6002055
Ref: 7286002055
Ref: library/os os O_NOCTTY6002079
Ref: 1f276002079
Ref: library/os os O_CLOEXEC6002101
Ref: 9c86002101
Ref: library/os os O_BINARY6002236
Ref: 1f1e6002236
Ref: library/os os O_NOINHERIT6002258
Ref: 1f286002258
Ref: library/os os O_SHORT_LIVED6002283
Ref: 1f296002283
Ref: library/os os O_TEMPORARY6002310
Ref: 1f2a6002310
Ref: library/os os O_RANDOM6002335
Ref: 1f2b6002335
Ref: library/os os O_SEQUENTIAL6002357
Ref: 1f2c6002357
Ref: library/os os O_TEXT6002383
Ref: 1f2d6002383
Ref: library/os os O_ASYNC6002461
Ref: 1f2e6002461
Ref: library/os os O_DIRECT6002482
Ref: 1f2f6002482
Ref: library/os os O_DIRECTORY6002504
Ref: 1f306002504
Ref: library/os os O_NOFOLLOW6002529
Ref: 1f316002529
Ref: library/os os O_NOATIME6002553
Ref: 1f326002553
Ref: library/os os O_PATH6002576
Ref: 8886002576
Ref: library/os os O_TMPFILE6002596
Ref: 8896002596
Ref: library/os os O_SHLOCK6002619
Ref: d9c6002619
Ref: library/os os O_EXLOCK6002641
Ref: d9d6002641
Ref: library/os os openpty6002918
Ref: 1f336002918
Ref: library/os os pipe6003352
Ref: 1f106003352
Ref: library/os os pipe26003676
Ref: a336003676
Ref: library/os os posix_fallocate6004063
Ref: 66c6004063
Ref: library/os os posix_fadvise6004317
Ref: 66b6004317
Ref: library/os os POSIX_FADV_NORMAL6004915
Ref: 1f346004915
Ref: library/os os POSIX_FADV_SEQUENTIAL6004946
Ref: 1f356004946
Ref: library/os os POSIX_FADV_RANDOM6004981
Ref: 1f366004981
Ref: library/os os POSIX_FADV_NOREUSE6005012
Ref: 1f376005012
Ref: library/os os POSIX_FADV_WILLNEED6005044
Ref: 1f386005044
Ref: library/os os POSIX_FADV_DONTNEED6005077
Ref: 1f396005077
Ref: library/os os pread6005310
Ref: 3be6005310
Ref: library/os os preadv6005693
Ref: 3bc6005693
Ref: library/os os RWF_NOWAIT6006744
Ref: 1f3b6006744
Ref: library/os os RWF_HIPRI6007251
Ref: 1f3a6007251
Ref: library/os os pwrite6007647
Ref: 3c16007647
Ref: library/os os pwritev6007927
Ref: 3bf6007927
Ref: library/os os RWF_DSYNC6008941
Ref: 1f3e6008941
Ref: library/os os RWF_SYNC6009215
Ref: 1f3f6009215
Ref: library/os os read6009487
Ref: 66d6009487
Ref: library/os os sendfile6010410
Ref: 35e6010410
Ref: library/os os set_blocking6011758
Ref: 7276011758
Ref: library/os os SF_NODISKIO6012120
Ref: 1f406012120
Ref: library/os os SF_MNOWAIT6012145
Ref: 1f416012145
Ref: library/os os SF_SYNC6012169
Ref: 1f426012169
Ref: library/os os readv6012353
Ref: 3bd6012353
Ref: library/os os tcgetpgrp6012965
Ref: 1f436012965
Ref: library/os os tcsetpgrp6013178
Ref: 1f446013178
Ref: library/os os ttyname6013405
Ref: 1f456013405
Ref: library/os os write6013654
Ref: 6736013654
Ref: library/os os writev6014484
Ref: 3c06014484
Ref: File Descriptor Operations-Footnote-16015174
Ref: File Descriptor Operations-Footnote-26015223
Ref: File Descriptor Operations-Footnote-36015286
Ref: File Descriptor Operations-Footnote-46015335
Node: Querying the size of a terminal6015384
Ref: library/os querying-the-size-of-a-terminal6015518
Ref: 1f466015518
Ref: library/os terminal-size6015518
Ref: 1f476015518
Ref: library/os os get_terminal_size6015620
Ref: a4e6015620
Ref: library/os os terminal_size6016255
Ref: 1ca36016255
Ref: library/os os terminal_size columns6016377
Ref: 1f486016377
Ref: library/os os terminal_size lines6016458
Ref: 1f496016458
Node: Inheritance of File Descriptors6016538
Ref: library/os fd-inheritance6016672
Ref: 7ff6016672
Ref: library/os inheritance-of-file-descriptors6016672
Ref: 1f4a6016672
Ref: library/os os get_inheritable6017629
Ref: 8006017629
Ref: library/os os set_inheritable6017750
Ref: 8016017750
Ref: library/os os get_handle_inheritable6017867
Ref: 8026017867
Ref: library/os os set_handle_inheritable6018027
Ref: 8036018027
Node: Files and Directories6018188
Ref: library/os files-and-directories6018356
Ref: 1f4c6018356
Ref: library/os os-file-dir6018356
Ref: 1eec6018356
Ref: library/os path-fd6018505
Ref: 3ba6018505
Ref: library/os dir-fd6019449
Ref: a346019449
Ref: library/os follow-symlinks6020164
Ref: a356020164
Ref: library/os os access6020748
Ref: a366020748
Ref: library/os os F_OK6023280
Ref: 1f4d6023280
Ref: library/os os R_OK6023298
Ref: 1f4e6023298
Ref: library/os os W_OK6023316
Ref: 1f4f6023316
Ref: library/os os X_OK6023334
Ref: 1f506023334
Ref: library/os os chdir6023523
Ref: a446023523
Ref: library/os os chflags6024182
Ref: a376024182
Ref: library/os os chmod6025235
Ref: a386025235
Ref: library/os os chown6026970
Ref: a396026970
Ref: library/os os chroot6027850
Ref: f466027850
Ref: library/os os fchdir6028045
Ref: 6606028045
Ref: library/os os getcwd6028447
Ref: fe36028447
Ref: library/os os getcwdb6028539
Ref: 2b96028539
Ref: library/os os lchflags6028835
Ref: 1f526028835
Ref: library/os os lchmod6029303
Ref: 102e6029303
Ref: library/os os lchown6029862
Ref: 1f536029862
Ref: library/os os link6030363
Ref: a3a6030363
Ref: library/os os listdir6031120
Ref: a466031120
Ref: library/os os lstat6032575
Ref: 1f36032575
Ref: library/os os mkdir6033641
Ref: a3b6033641
Ref: library/os mkdir-modebits6033843
Ref: 1f546033843
Ref: library/os os makedirs6034680
Ref: 3c26034680
Ref: library/os os mkfifo6036356
Ref: 6686036356
Ref: library/os os mknod6037221
Ref: 6696037221
Ref: library/os os major6038079
Ref: 1f576038079
Ref: library/os os minor6038245
Ref: 1f586038245
Ref: library/os os makedev6038411
Ref: 1f566038411
Ref: library/os os pathconf6038530
Ref: a476038530
Ref: library/os os pathconf_names6039616
Ref: 1f596039616
Ref: library/os os readlink6039939
Ref: 1f46039939
Ref: library/os os remove6041384
Ref: a3c6041384
Ref: library/os os removedirs6042301
Ref: 1f5a6042301
Ref: library/os os rename6043132
Ref: a3d6043132
Ref: library/os os renames6044613
Ref: 1f5b6044613
Ref: library/os os replace6045391
Ref: a3e6045391
Ref: library/os os rmdir6046245
Ref: a3f6046245
Ref: library/os os scandir6046867
Ref: 2606046867
Ref: library/os os scandir close6048641
Ref: 56c6048641
Ref: library/os os DirEntry6050153
Ref: 4f66050153
Ref: library/os os DirEntry name6051339
Ref: 1f5e6051339
Ref: library/os os DirEntry path6051707
Ref: 1f5f6051707
Ref: library/os os DirEntry inode6052439
Ref: 1f606052439
Ref: library/os os DirEntry is_dir6052804
Ref: 1f5c6052804
Ref: library/os os DirEntry is_file6054245
Ref: 65a6054245
Ref: library/os os DirEntry is_symlink6054974
Ref: 1f616054974
Ref: library/os os DirEntry stat6055831
Ref: 1f5d6055831
Ref: library/os os stat6057245
Ref: 1f26057245
Ref: library/os os stat_result6059804
Ref: 108f6059804
Ref: library/os os stat_result st_mode6060055
Ref: 1f626060055
Ref: library/os os stat_result st_ino6060147
Ref: 1f636060147
Ref: library/os os stat_result st_dev6060393
Ref: 1f646060393
Ref: library/os os stat_result st_nlink6060482
Ref: 1f656060482
Ref: library/os os stat_result st_uid6060542
Ref: 1f666060542
Ref: library/os os stat_result st_gid6060613
Ref: 1f676060613
Ref: library/os os stat_result st_size6060685
Ref: 1f686060685
Ref: library/os os stat_result st_atime6060936
Ref: 1f696060936
Ref: library/os os stat_result st_mtime6061023
Ref: 1d5b6061023
Ref: library/os os stat_result st_ctime6061124
Ref: 1f6a6061124
Ref: library/os os stat_result st_atime_ns6061318
Ref: 1f6b6061318
Ref: library/os os stat_result st_mtime_ns6061436
Ref: 1f6c6061436
Ref: library/os os stat_result st_ctime_ns6061568
Ref: 1f6d6061568
Ref: library/os os stat_result st_blocks6063017
Ref: 1f6e6063017
Ref: library/os os stat_result st_blksize6063188
Ref: 1f6f6063188
Ref: library/os os stat_result st_rdev6063383
Ref: 1f706063383
Ref: library/os os stat_result st_flags6063455
Ref: 1f716063455
Ref: library/os os stat_result st_gen6063677
Ref: 1f726063677
Ref: library/os os stat_result st_birthtime6063737
Ref: 1f736063737
Ref: library/os os stat_result st_fstype6063889
Ref: 3c46063889
Ref: library/os os stat_result st_rsize6064094
Ref: 1f746064094
Ref: library/os os stat_result st_creator6064155
Ref: 1f756064155
Ref: library/os os stat_result st_type6064216
Ref: 1f766064216
Ref: library/os os stat_result st_file_attributes6064335
Ref: 7256064335
Ref: library/os os stat_result st_reparse_tag6064639
Ref: 1f776064639
Ref: library/os os statvfs6066460
Ref: a486066460
Ref: library/os os supports_dir_fd6068445
Ref: a436068445
Ref: library/os os supports_effective_ids6069602
Ref: a4a6069602
Ref: library/os os supports_fd6070338
Ref: a496070338
Ref: library/os os supports_follow_symlinks6071158
Ref: 1c8e6071158
Ref: library/os os symlink6072290
Ref: a406072290
Ref: library/os os sync6073909
Ref: a5e6073909
Ref: library/os os truncate6074037
Ref: 7296074037
Ref: library/os os unlink6074536
Ref: a416074536
Ref: library/os os utime6075047
Ref: a426075047
Ref: library/os os walk6076897
Ref: 6596076897
Ref: library/os os fwalk6081918
Ref: 3b96081918
Ref: library/os os memfd_create6084335
Ref: 1f16084335
Ref: library/os os MFD_CLOEXEC6085205
Ref: 1f786085205
Ref: library/os os MFD_ALLOW_SEALING6085230
Ref: 1f796085230
Ref: library/os os MFD_HUGETLB6085261
Ref: 1f7a6085261
Ref: library/os os MFD_HUGE_SHIFT6085286
Ref: 1f7b6085286
Ref: library/os os MFD_HUGE_MASK6085314
Ref: 1f7c6085314
Ref: library/os os MFD_HUGE_64KB6085341
Ref: 1f7d6085341
Ref: library/os os MFD_HUGE_512KB6085368
Ref: 1f7e6085368
Ref: library/os os MFD_HUGE_1MB6085396
Ref: 1f7f6085396
Ref: library/os os MFD_HUGE_2MB6085422
Ref: 1f806085422
Ref: library/os os MFD_HUGE_8MB6085448
Ref: 1f816085448
Ref: library/os os MFD_HUGE_16MB6085474
Ref: 1f826085474
Ref: library/os os MFD_HUGE_32MB6085501
Ref: 1f836085501
Ref: library/os os MFD_HUGE_256MB6085528
Ref: 1f846085528
Ref: library/os os MFD_HUGE_512MB6085556
Ref: 1f856085556
Ref: library/os os MFD_HUGE_1GB6085584
Ref: 1f866085584
Ref: library/os os MFD_HUGE_2GB6085610
Ref: 1f876085610
Ref: library/os os MFD_HUGE_16GB6085636
Ref: 1f886085636
Ref: Files and Directories-Footnote-16085974
Ref: Files and Directories-Footnote-26086023
Ref: Files and Directories-Footnote-36086066
Ref: Files and Directories-Footnote-46086145
Ref: Files and Directories-Footnote-56086226
Ref: Files and Directories-Footnote-66086315
Ref: Files and Directories-Footnote-76086404
Node: Linux extended attributes6086462
Ref: library/os linux-extended-attributes6086545
Ref: 1f896086545
Ref: library/os os getxattr6086685
Ref: a506086685
Ref: library/os os listxattr6087333
Ref: a516087333
Ref: library/os os removexattr6087929
Ref: a526087929
Ref: library/os os setxattr6088579
Ref: a536088579
Ref: library/os os XATTR_SIZE_MAX6089780
Ref: 1f8c6089780
Ref: library/os os XATTR_CREATE6089916
Ref: 1f8b6089916
Ref: library/os os XATTR_REPLACE6090087
Ref: 1f8a6090087
Node: Process Management6090269
Ref: library/os os-process6090437
Ref: 1f8d6090437
Ref: library/os process-management6090437
Ref: 1f8e6090437
Ref: library/os os abort6091050
Ref: 1f906091050
Ref: library/os os add_dll_directory6091423
Ref: 1c36091423
Ref: library/os os execl6092568
Ref: 1f8f6092568
Ref: library/os os execle6092613
Ref: 1f916092613
Ref: library/os os execlp6092664
Ref: 1f926092664
Ref: library/os os execlpe6092710
Ref: 1f936092710
Ref: library/os os execv6092762
Ref: 1efe6092762
Ref: library/os os execve6092796
Ref: a456092796
Ref: library/os os execvp6092836
Ref: 1f946092836
Ref: library/os os execvpe6092871
Ref: 1f956092871
Ref: library/os os _exit6096054
Ref: 17136096054
Ref: library/os os EX_OK6096804
Ref: 1f966096804
Ref: library/os os EX_USAGE6096909
Ref: 1f976096909
Ref: library/os os EX_DATAERR6097091
Ref: 1f986097091
Ref: library/os os EX_NOINPUT6097212
Ref: 1f996097212
Ref: library/os os EX_NOUSER6097357
Ref: 1f9a6097357
Ref: library/os os EX_NOHOST6097479
Ref: 1f9b6097479
Ref: library/os os EX_UNAVAILABLE6097601
Ref: 1f9c6097601
Ref: library/os os EX_SOFTWARE6097736
Ref: 1f9d6097736
Ref: library/os os EX_OSERR6097869
Ref: 1f9e6097869
Ref: library/os os EX_OSFILE6098051
Ref: 1f9f6098051
Ref: library/os os EX_CANTCREAT6098232
Ref: 1fa06098232
Ref: library/os os EX_IOERR6098381
Ref: 1fa16098381
Ref: library/os os EX_TEMPFAIL6098528
Ref: 1fa26098528
Ref: library/os os EX_PROTOCOL6098802
Ref: 1fa36098802
Ref: library/os os EX_NOPERM6098965
Ref: 1fa46098965
Ref: library/os os EX_CONFIG6099171
Ref: 1fa56099171
Ref: library/os os EX_NOTFOUND6099314
Ref: 1fa66099314
Ref: library/os os fork6099447
Ref: 9666099447
Ref: library/os os forkpty6100107
Ref: 1fa76100107
Ref: library/os os kill6100827
Ref: cf86100827
Ref: library/os os killpg6101718
Ref: f346101718
Ref: library/os os nice6101951
Ref: a4d6101951
Ref: library/os os plock6102107
Ref: 1faa6102107
Ref: library/os os popen6102308
Ref: 2aa6102308
Ref: library/os os posix_spawn6103586
Ref: 2586103586
Ref: library/os os POSIX_SPAWN_OPEN6104590
Ref: 1fab6104590
Ref: library/os os POSIX_SPAWN_CLOSE6104763
Ref: 1fac6104763
Ref: library/os os POSIX_SPAWN_DUP26104886
Ref: 1fad6104886
Ref: library/os os posix_spawnp6107500
Ref: 101a6107500
Ref: library/os os register_at_fork6108212
Ref: 3bb6108212
Ref: library/os os spawnl6109623
Ref: 1f4b6109623
Ref: library/os os spawnle6109663
Ref: 1faf6109663
Ref: library/os os spawnlp6109709
Ref: 1fb06109709
Ref: library/os os spawnlpe6109750
Ref: 1fb16109750
Ref: library/os os spawnv6109797
Ref: 1fb26109797
Ref: library/os os spawnve6109838
Ref: 1fb36109838
Ref: library/os os spawnvp6109885
Ref: 1fb46109885
Ref: library/os os spawnvpe6109927
Ref: 1fb56109927
Ref: library/os os P_NOWAIT6113763
Ref: 1fb66113763
Ref: library/os os P_NOWAITO6113785
Ref: 1fb86113785
Ref: library/os os P_WAIT6114131
Ref: 1fb76114131
Ref: library/os os P_DETACH6114548
Ref: 1fb96114548
Ref: library/os os P_OVERLAY6114570
Ref: 1fba6114570
Ref: library/os os startfile6115062
Ref: 1fbb6115062
Ref: library/os os system6116761
Ref: dc66116761
Ref: library/os os times6118316
Ref: a616118316
Ref: library/os os wait6119335
Ref: 6706119335
Ref: library/os os waitid6119744
Ref: 6716119744
Ref: library/os os P_PID6120558
Ref: 1fbc6120558
Ref: library/os os P_PGID6120577
Ref: 1fbd6120577
Ref: library/os os P_ALL6120597
Ref: 1fbe6120597
Ref: library/os os WEXITED6120795
Ref: 1fbf6120795
Ref: library/os os WSTOPPED6120816
Ref: 1fc06120816
Ref: library/os os WNOWAIT6120838
Ref: 1fc36120838
Ref: library/os os CLD_EXITED6121038
Ref: 1fc46121038
Ref: library/os os CLD_DUMPED6121062
Ref: 1fc56121062
Ref: library/os os CLD_TRAPPED6121086
Ref: 1fc66121086
Ref: library/os os CLD_CONTINUED6121111
Ref: 1fc76121111
Ref: library/os os waitpid6121308
Ref: 6726121308
Ref: library/os os wait36123166
Ref: 66e6123166
Ref: library/os os wait46123661
Ref: 66f6123661
Ref: library/os os WNOHANG6124122
Ref: 1fc26124122
Ref: library/os os WCONTINUED6124360
Ref: 1fc16124360
Ref: library/os os WUNTRACED6124593
Ref: 1fc86124593
Ref: library/os os WCOREDUMP6125028
Ref: 1fc96125028
Ref: library/os os WIFCONTINUED6125295
Ref: 1fcb6125295
Ref: library/os os WIFSTOPPED6125611
Ref: 1fcd6125611
Ref: library/os os WIFSIGNALED6126001
Ref: 1fca6126001
Ref: library/os os WIFEXITED6126179
Ref: 1fce6126179
Ref: library/os os WEXITSTATUS6126446
Ref: 1fcf6126446
Ref: library/os os WSTOPSIG6126646
Ref: 1fd06126646
Ref: library/os os WTERMSIG6126864
Ref: 1fd16126864
Ref: Process Management-Footnote-16127142
Ref: Process Management-Footnote-26127214
Ref: Process Management-Footnote-36127323
Node: Interface to the scheduler6127372
Ref: library/os interface-to-the-scheduler6127551
Ref: 1fd26127551
Ref: library/os os SCHED_OTHER6127934
Ref: 1fd36127934
Ref: library/os os SCHED_BATCH6127997
Ref: 1fd46127997
Ref: library/os os SCHED_IDLE6128146
Ref: 1fd56128146
Ref: library/os os SCHED_SPORADIC6128240
Ref: 1fd66128240
Ref: library/os os SCHED_FIFO6128323
Ref: 1fd76128323
Ref: library/os os SCHED_RR6128394
Ref: 1fd86128394
Ref: library/os os SCHED_RESET_ON_FORK6128456
Ref: 1fd96128456
Ref: library/os os sched_param6128678
Ref: 1fae6128678
Ref: library/os os sched_param sched_priority6128971
Ref: 1fda6128971
Ref: library/os os sched_get_priority_min6129064
Ref: a556129064
Ref: library/os os sched_get_priority_max6129227
Ref: a546129227
Ref: library/os os sched_setscheduler6129390
Ref: a5c6129390
Ref: library/os os sched_getscheduler6129674
Ref: a586129674
Ref: library/os os sched_setparam6129894
Ref: a5b6129894
Ref: library/os os sched_getparam6130104
Ref: a576130104
Ref: library/os os sched_rr_get_interval6130302
Ref: a596130302
Ref: library/os os sched_yield6130472
Ref: a5d6130472
Ref: library/os os sched_setaffinity6130541
Ref: a5a6130541
Ref: library/os os sched_getaffinity6130802
Ref: a566130802
Node: Miscellaneous System Information6130954
Ref: library/os miscellaneous-system-information6131132
Ref: 1fdb6131132
Ref: library/os os-path6131132
Ref: 1fdc6131132
Ref: library/os os confstr6131219
Ref: 1fdd6131219
Ref: library/os os confstr_names6132252
Ref: 1fde6132252
Ref: library/os os cpu_count6132545
Ref: 8846132545
Ref: library/os os getloadavg6132867
Ref: 1fdf6132867
Ref: library/os os sysconf6133119
Ref: 1f3c6133119
Ref: library/os os sysconf_names6133538
Ref: 1fe06133538
Ref: library/os os curdir6134030
Ref: 1bf76134030
Ref: library/os os pardir6134231
Ref: 1f556134231
Ref: library/os os sep6134432
Ref: 1c7d6134432
Ref: library/os os altsep6134843
Ref: 1c7e6134843
Ref: library/os os extsep6135142
Ref: 1fe16135142
Ref: library/os os pathsep6135329
Ref: 135a6135329
Ref: library/os os defpath6135573
Ref: fe46135573
Ref: library/os os linesep6135782
Ref: 16016135782
Ref: library/os os devnull6136195
Ref: 101f6136195
Ref: library/os os RTLD_LAZY6136369
Ref: a646136369
Ref: library/os os RTLD_NOW6136392
Ref: a656136392
Ref: library/os os RTLD_GLOBAL6136414
Ref: a666136414
Ref: library/os os RTLD_LOCAL6136439
Ref: a676136439
Ref: library/os os RTLD_NODELETE6136463
Ref: a686136463
Ref: library/os os RTLD_NOLOAD6136490
Ref: a696136490
Ref: library/os os RTLD_DEEPBIND6136515
Ref: a6a6136515
Node: Random numbers<2>6136756
Ref: library/os random-numbers6136899
Ref: 1fe26136899
Ref: library/os os getrandom6136950
Ref: 56e6136950
Ref: library/os os urandom6137781
Ref: 4d66137781
Ref: library/os os GRND_NONBLOCK6139675
Ref: 1fe46139675
Ref: library/os os GRND_RANDOM6140146
Ref: 1fe36140146
Ref: Random numbers<2>-Footnote-16140363
Ref: Random numbers<2>-Footnote-26140425
Node: io --- Core tools for working with streams6140474
Ref: library/io doc6140688
Ref: 1fe56140688
Ref: library/io io-core-tools-for-working-with-streams6140688
Ref: 1fe66140688
Ref: library/io module-io6140688
Ref: a26140688
Ref: io --- Core tools for working with streams-Footnote-16141032
Node: 總覽6141093
Ref: library/io io-overview6141214
Ref: 15fc6141214
Ref: library/io overview6141214
Ref: 1fe76141214
Node: Text I/O6142456
Ref: library/io text-i-o6142526
Ref: 1fe86142526
Node: Binary I/O6143217
Ref: library/io binary-i-o6143303
Ref: 1fe96143303
Node: Raw I/O6144172
Ref: library/io raw-i-o6144241
Ref: 1fea6144241
Node: High-level Module Interface6144694
Ref: library/io high-level-module-interface6144839
Ref: 1feb6144839
Ref: library/io io DEFAULT_BUFFER_SIZE6144914
Ref: 15fe6144914
Ref: library/io io open6145149
Ref: 65f6145149
Ref: library/io io open_code6145587
Ref: f276145587
Ref: library/io io BlockingIOError6146252
Ref: 1fed6146252
Ref: library/io io UnsupportedOperation6146380
Ref: 1fee6146380
Node: Class hierarchy6146723
Ref: library/io class-hierarchy6146876
Ref: 1fef6146876
Node: I/O Base Classes6151541
Ref: library/io i-o-base-classes6151630
Ref: 1ff16151630
Ref: library/io io IOBase6151683
Ref: 1dc6151683
Ref: library/io io IOBase close6153597
Ref: 10136153597
Ref: library/io io IOBase closed6154013
Ref: 10146154013
Ref: library/io io IOBase fileno6154085
Ref: 1f0f6154085
Ref: library/io io IOBase flush6154312
Ref: 1ff26154312
Ref: library/io io IOBase isatty6154478
Ref: 15ff6154478
Ref: library/io io IOBase readable6154624
Ref: 1ff36154624
Ref: library/io io IOBase readline6154792
Ref: 17086154792
Ref: library/io io IOBase readlines6155167
Ref: 17956155167
Ref: library/io io IOBase seek6155632
Ref: 1d9d6155632
Ref: library/io io IOBase seekable6156630
Ref: 1ff46156630
Ref: library/io io IOBase tell6156868
Ref: 1d9e6156868
Ref: library/io io IOBase truncate6156947
Ref: caa6156947
Ref: library/io io IOBase writable6157509
Ref: 1ff56157509
Ref: library/io io IOBase writelines6157715
Ref: 17966157715
Ref: library/io io IOBase __del__6157941
Ref: 1ff66157941
Ref: library/io io RawIOBase6158165
Ref: a186158165
Ref: library/io io RawIOBase read6158669
Ref: 7076158669
Ref: library/io io RawIOBase readall6159356
Ref: 1ff76159356
Ref: library/io io RawIOBase readinto6159518
Ref: 7086159518
Ref: library/io io RawIOBase write6159862
Ref: 1ff86159862
Ref: library/io io BufferedIOBase6160504
Ref: 58d6160504
Ref: library/io io BufferedIOBase raw6161722
Ref: 1ffa6161722
Ref: library/io io BufferedIOBase detach6161989
Ref: 1ffb6161989
Ref: library/io io BufferedIOBase read6162427
Ref: 1d5d6162427
Ref: library/io io BufferedIOBase read16163238
Ref: 1d5c6163238
Ref: library/io io BufferedIOBase readinto6163724
Ref: 1ff96163724
Ref: library/io io BufferedIOBase readinto16164261
Ref: 7066164261
Ref: library/io io BufferedIOBase write6164757
Ref: 58e6164757
Node: Raw File I/O6165580
Ref: library/io raw-file-i-o6165694
Ref: 1ffc6165694
Ref: library/io io FileIO6165739
Ref: ca96165739
Ref: library/io io FileIO mode6168113
Ref: 1ffd6168113
Ref: library/io io FileIO name6168185
Ref: 1df26168185
Node: Buffered Streams6168327
Ref: library/io buffered-streams6168436
Ref: 1ffe6168436
Ref: library/io io BytesIO6168580
Ref: 7a06168580
Ref: library/io io BytesIO getbuffer6169064
Ref: b726169064
Ref: library/io io BytesIO getvalue6169637
Ref: 1d5a6169637
Ref: library/io io BytesIO read16169765
Ref: 1fff6169765
Ref: library/io io BytesIO readinto16169941
Ref: 20006169941
Ref: library/io io BufferedReader6170096
Ref: b8f6170096
Ref: library/io io BufferedReader peek6170896
Ref: 20016170896
Ref: library/io io BufferedReader read6171173
Ref: 20026171173
Ref: library/io io BufferedReader read16171375
Ref: 20036171375
Ref: library/io io BufferedWriter6171706
Ref: 16026171706
Ref: library/io io BufferedWriter flush6172780
Ref: 20046172780
Ref: library/io io BufferedWriter write6172970
Ref: 20056172970
Ref: library/io io BufferedRandom6173263
Ref: 16036173263
Ref: library/io io BufferedRWPair6173871
Ref: 1ff06173871
Node: Text I/O<2>6174811
Ref: library/io id16174899
Ref: 20066174899
Ref: library/io io TextIOBase6174938
Ref: c3e6174938
Ref: library/io io TextIOBase encoding6175282
Ref: 20076175282
Ref: library/io io TextIOBase errors6175439
Ref: 20086175439
Ref: library/io io TextIOBase newlines6175520
Ref: 20096175520
Ref: library/io io TextIOBase buffer6175761
Ref: c3f6175761
Ref: library/io io TextIOBase detach6176031
Ref: 200a6176031
Ref: library/io io TextIOBase read6176550
Ref: 200b6176550
Ref: library/io io TextIOBase readline6176761
Ref: 1c036176761
Ref: library/io io TextIOBase seek6177030
Ref: 200c6177030
Ref: library/io io TextIOBase tell6177998
Ref: 200d6177998
Ref: library/io io TextIOBase write6178208
Ref: 200e6178208
Ref: library/io io TextIOWrapper6178343
Ref: 5f86178343
Ref: library/io io TextIOWrapper line_buffering6181745
Ref: 20106181745
Ref: library/io io TextIOWrapper write_through6181824
Ref: 20116181824
Ref: library/io io TextIOWrapper reconfigure6181977
Ref: 3a26181977
Ref: library/io io StringIO6182756
Ref: 8326182756
Ref: library/io io StringIO getvalue6183642
Ref: 20126183642
Ref: library/io io IncrementalNewlineDecoder6184296
Ref: 20136184296
Node: Performance<3>6184479
Ref: library/io performance6184596
Ref: 20146184596
Node: Binary I/O<2>6184845
Ref: library/io id26184929
Ref: 20156184929
Node: Text I/O<3>6185581
Ref: library/io id36185692
Ref: 20166185692
Node: Multi-threading<3>6186269
Ref: library/io multi-threading6186377
Ref: 20176186377
Node: Reentrancy6186910
Ref: library/io reentrancy6186998
Ref: 20186186998
Node: time --- Time access and conversions6187790
Ref: library/time doc6188027
Ref: 20196188027
Ref: library/time module-time6188027
Ref: 10b6188027
Ref: library/time time-time-access-and-conversions6188027
Ref: 201a6188027
Ref: library/time epoch6188727
Ref: 201b6188727
Ref: time --- Time access and conversions-Footnote-16193075
Node: Functions<2>6193125
Ref: library/time functions6193237
Ref: 201c6193237
Ref: library/time time-functions6193237
Ref: 201d6193237
Ref: library/time time asctime6193276
Ref: b686193276
Ref: library/time time pthread_getcpuclockid6193942
Ref: 4006193942
Ref: library/time time clock_getres6194544
Ref: ab76194544
Ref: library/time time clock_gettime6194815
Ref: ab86194815
Ref: library/time time clock_gettime_ns6195079
Ref: 3236195079
Ref: library/time time clock_settime6195275
Ref: ab96195275
Ref: library/time time clock_settime_ns6195530
Ref: 3246195530
Ref: library/time time ctime6195729
Ref: 18bc6195729
Ref: library/time time get_clock_info6196294
Ref: ab66196294
Ref: library/time time gmtime6197421
Ref: b446197421
Ref: library/time time localtime6197898
Ref: f526197898
Ref: library/time time mktime6198185
Ref: b696198185
Ref: library/time time monotonic6198892
Ref: 7746198892
Ref: library/time time monotonic_ns6199351
Ref: 3256199351
Ref: library/time time perf_counter6199489
Ref: 2ab6199489
Ref: library/time time perf_counter_ns6199926
Ref: 3266199926
Ref: library/time time process_time6200075
Ref: 2ac6200075
Ref: library/time time process_time_ns6200487
Ref: 3276200487
Ref: library/time time sleep6200636
Ref: 6856200636
Ref: library/time time strftime6201387
Ref: b6a6201387
Ref: library/time time strptime6208467
Ref: d966208467
Ref: library/time time struct_time6210165
Ref: 59e6210165
Ref: library/time time time6212926
Ref: 3226212926
Ref: library/time time thread_time6214223
Ref: 3fe6214223
Ref: library/time time thread_time_ns6214769
Ref: 3ff6214769
Ref: library/time time time_ns6214916
Ref: 3286214916
Ref: library/time time tzset6215099
Ref: 20216215099
Ref: Functions<2>-Footnote-16219013
Ref: Functions<2>-Footnote-26219062
Ref: Functions<2>-Footnote-36219112
Ref: Functions<2>-Footnote-46219161
Ref: Functions<2>-Footnote-56219798
Ref: Functions<2>-Footnote-66219848
Node: Clock ID Constants6219896
Ref: library/time clock-id-constants6220035
Ref: 20226220035
Ref: library/time time-clock-id-constants6220035
Ref: 201f6220035
Ref: library/time time CLOCK_BOOTTIME6220195
Ref: 3fa6220195
Ref: library/time time CLOCK_HIGHRES6220676
Ref: 20236220676
Ref: library/time time CLOCK_MONOTONIC6221000
Ref: 3fb6221000
Ref: library/time time CLOCK_MONOTONIC_RAW6221200
Ref: 20246221200
Ref: library/time time CLOCK_PROCESS_CPUTIME_ID6221484
Ref: 20256221484
Ref: library/time time CLOCK_PROF6221642
Ref: 3fc6221642
Ref: library/time time CLOCK_THREAD_CPUTIME_ID6221817
Ref: 20266221817
Ref: library/time time CLOCK_UPTIME6221958
Ref: 3fd6221958
Ref: library/time time CLOCK_UPTIME_RAW6222243
Ref: 23a6222243
Ref: library/time time CLOCK_REALTIME6222639
Ref: 20206222639
Node: Timezone Constants6222826
Ref: library/time time-timezone-constants6222944
Ref: 20276222944
Ref: library/time timezone-constants6222944
Ref: 20286222944
Ref: library/time time altzone6223001
Ref: 20296223001
Ref: library/time time daylight6223289
Ref: 202a6223289
Ref: library/time time timezone6223375
Ref: 202b6223375
Ref: library/time time tzname6223573
Ref: 202c6223573
Node: argparse --- Parser for command-line options arguments and sub-commands6224771
Ref: library/argparse doc6225016
Ref: 202d6225016
Ref: library/argparse argparse-parser-for-command-line-options-arguments-and-sub-commands6225016
Ref: 202e6225016
Ref: library/argparse module-argparse6225016
Ref: 66225016
Ref: argparse --- Parser for command-line options arguments and sub-commands-Footnote-16226114
Node: Example<7>6226181
Ref: library/argparse example6226330
Ref: 20306226330
Node: Creating a parser6227947
Ref: library/argparse creating-a-parser6228036
Ref: 20316228036
Node: Adding arguments6228399
Ref: library/argparse adding-arguments6228514
Ref: 20326228514
Node: Parsing arguments6229661
Ref: library/argparse parsing-arguments6229750
Ref: 20356229750
Node: ArgumentParser objects6230480
Ref: library/argparse argumentparser-objects6230661
Ref: 20376230661
Ref: library/argparse argparse ArgumentParser6230726
Ref: 69a6230726
Node: prog6233157
Ref: library/argparse prog6233234
Ref: 20386233234
Node: usage6235096
Ref: library/argparse usage6235193
Ref: 20396235193
Node: description6236363
Ref: library/argparse description6236462
Ref: 203a6236462
Node: epilog6237225
Ref: library/argparse epilog6237326
Ref: 203b6237326
Node: parents6238105
Ref: library/argparse parents6238210
Ref: 203c6238210
Node: formatter_class6239666
Ref: library/argparse formatter-class6239777
Ref: 203d6239777
Ref: library/argparse argparse RawDescriptionHelpFormatter6239995
Ref: 20436239995
Ref: library/argparse argparse RawTextHelpFormatter6240044
Ref: 20446240044
Ref: library/argparse argparse ArgumentDefaultsHelpFormatter6240086
Ref: 20456240086
Ref: library/argparse argparse MetavarTypeHelpFormatter6240137
Ref: 20466240137
Node: prefix_chars6243655
Ref: library/argparse prefix-chars6243780
Ref: 203e6243780
Node: fromfile_prefix_chars6244518
Ref: library/argparse fromfile-prefix-chars6244644
Ref: 203f6244644
Node: argument_default6245919
Ref: library/argparse argument-default6246045
Ref: 20406246045
Node: allow_abbrev6246932
Ref: library/argparse allow-abbrev6247053
Ref: 69c6247053
Ref: library/argparse id16247053
Ref: 204b6247053
Node: conflict_handler6247702
Ref: library/argparse conflict-handler6247815
Ref: 20416247815
Node: add_help6249373
Ref: library/argparse add-help6249465
Ref: 20426249465
Node: The add_argument method6251043
Ref: library/argparse the-add-argument-method6251235
Ref: 204c6251235
Ref: library/argparse argparse ArgumentParser add_argument6251308
Ref: 20336251308
Node: name or flags6253104
Ref: library/argparse name-or-flags6253192
Ref: 204d6253192
Node: action6254341
Ref: library/argparse action6254443
Ref: 204e6254443
Node: nargs6260033
Ref: library/argparse nargs6260127
Ref: 204f6260127
Ref: library/argparse argparse-remainder6263915
Ref: 20576263915
Node: const6264737
Ref: library/argparse const6264832
Ref: 20506264832
Node: default6266027
Ref: library/argparse default6266121
Ref: 20516266121
Node: type6268039
Ref: library/argparse type6268135
Ref: 20476268135
Node: choices6270760
Ref: library/argparse choices6270857
Ref: 20526270857
Node: required6272347
Ref: library/argparse required6272444
Ref: 20536272444
Node: help6273406
Ref: library/argparse help6273503
Ref: 20546273503
Node: metavar6275615
Ref: library/argparse metavar6275708
Ref: 20556275708
Node: dest6277946
Ref: library/argparse dest6278049
Ref: 20486278049
Node: Action classes6279684
Ref: library/argparse action-classes6279771
Ref: 20586279771
Ref: library/argparse argparse Action6280053
Ref: 20566280053
Node: The parse_args method6281818
Ref: library/argparse the-parse-args-method6282003
Ref: 20596282003
Ref: library/argparse argparse ArgumentParser parse_args6282072
Ref: 20346282072
Node: Option value syntax6282954
Ref: library/argparse option-value-syntax6283057
Ref: 205c6283057
Node: Invalid arguments6284454
Ref: library/argparse invalid-arguments6284588
Ref: 205d6284588
Node: Arguments containing -6285573
Ref: library/argparse arguments-containing6285726
Ref: 205e6285726
Node: Argument abbreviations prefix matching6287731
Ref: library/argparse argument-abbreviations-prefix-matching6287882
Ref: 205f6287882
Ref: library/argparse prefix-matching6287882
Ref: 69b6287882
Node: Beyond sys argv6288810
Ref: library/argparse args6288959
Ref: 205a6288959
Ref: library/argparse beyond-sys-argv6288959
Ref: 20606288959
Node: The Namespace object6289909
Ref: library/argparse namespace6290011
Ref: 205b6290011
Ref: library/argparse the-namespace-object6290011
Ref: 20616290011
Ref: library/argparse argparse Namespace6290074
Ref: 20366290074
Node: Other utilities6291100
Ref: library/argparse other-utilities6291285
Ref: 20626291285
Node: Sub-commands6291557
Ref: library/argparse sub-commands6291646
Ref: 20636291646
Ref: library/argparse argparse ArgumentParser add_subparsers6291693
Ref: 4a96291693
Node: FileType objects6300580
Ref: library/argparse filetype-objects6300693
Ref: 20646300693
Ref: library/argparse argparse FileType6300748
Ref: 8256300748
Node: Argument groups6302197
Ref: library/argparse argument-groups6302314
Ref: 20656302314
Ref: library/argparse argparse ArgumentParser add_argument_group6302367
Ref: 20666302367
Node: Mutual exclusion6304462
Ref: library/argparse mutual-exclusion6304578
Ref: 20676304578
Ref: library/argparse argparse ArgumentParser add_mutually_exclusive_group6304633
Ref: 20686304633
Node: Parser defaults6306244
Ref: library/argparse parser-defaults6306358
Ref: 20696306358
Ref: library/argparse argparse ArgumentParser set_defaults6306411
Ref: 204a6306411
Ref: library/argparse argparse ArgumentParser get_default6307541
Ref: 206a6307541
Node: Printing help6307904
Ref: library/argparse printing-help6308017
Ref: 206b6308017
Ref: library/argparse argparse ArgumentParser print_usage6308246
Ref: 206c6308246
Ref: library/argparse argparse ArgumentParser print_help6308484
Ref: 206d6308484
Ref: library/argparse argparse ArgumentParser format_usage6308844
Ref: 206e6308844
Ref: library/argparse argparse ArgumentParser format_help6309029
Ref: 206f6309029
Node: Partial parsing6309248
Ref: library/argparse partial-parsing6309370
Ref: 20706309370
Ref: library/argparse argparse ArgumentParser parse_known_args6309423
Ref: 20716309423
Node: Customizing file parsing6310477
Ref: library/argparse customizing-file-parsing6310601
Ref: 20726310601
Ref: library/argparse argparse ArgumentParser convert_arg_line_to_args6310672
Ref: 20496310672
Node: Exiting methods6311583
Ref: library/argparse exiting-methods6311710
Ref: 20736311710
Ref: library/argparse argparse ArgumentParser exit6311763
Ref: 20746311763
Ref: library/argparse argparse ArgumentParser error6312301
Ref: 20756312301
Node: Intermixed parsing6312495
Ref: library/argparse intermixed-parsing6312589
Ref: 20766312589
Ref: library/argparse argparse ArgumentParser parse_intermixed_args6312648
Ref: 34a6312648
Ref: library/argparse argparse ArgumentParser parse_known_intermixed_args6312742
Ref: 20776312742
Node: Upgrading optparse code6314279
Ref: library/argparse id26314434
Ref: 20786314434
Ref: library/argparse upgrading-optparse-code6314434
Ref: b2e6314434
Node: getopt --- C-style parser for command line options6316932
Ref: library/getopt doc6317180
Ref: 207b6317180
Ref: library/getopt getopt-c-style-parser-for-command-line-options6317180
Ref: 207c6317180
Ref: library/getopt module-getopt6317180
Ref: 876317180
Ref: library/getopt getopt getopt6318194
Ref: 207d6318194
Ref: library/getopt getopt gnu_getopt6320381
Ref: 207f6320381
Ref: library/getopt getopt GetoptError6320959
Ref: 207e6320959
Ref: library/getopt getopt error6321536
Ref: 20806321536
Ref: getopt --- C-style parser for command line options-Footnote-16323974
Node: logging --- Logging facility for Python6324039
Ref: library/logging doc6324256
Ref: 20816324256
Ref: library/logging logging-logging-facility-for-python6324256
Ref: 20826324256
Ref: library/logging module-logging6324256
Ref: ab6324256
Ref: logging --- Logging facility for Python-Footnote-16326025
Node: Logger Objects6326101
Ref: library/logging logger6326214
Ref: 20836326214
Ref: library/logging logger-objects6326214
Ref: 20846326214
Ref: library/logging logging Logger6327307
Ref: 3ac6327307
Ref: library/logging logging Logger propagate6327335
Ref: 20866327335
Ref: library/logging logging Logger setLevel6328623
Ref: 20876328623
Ref: library/logging logging Logger isEnabledFor6330582
Ref: 208a6330582
Ref: library/logging logging Logger getEffectiveLevel6330931
Ref: 20896330931
Ref: library/logging logging Logger getChild6331408
Ref: c906331408
Ref: library/logging logging Logger debug6331911
Ref: 7156331911
Ref: library/logging logging Logger info6337068
Ref: 208d6337068
Ref: library/logging logging Logger warning6337253
Ref: 208f6337253
Ref: library/logging logging Logger error6337667
Ref: 20906337667
Ref: library/logging logging Logger critical6337854
Ref: 7146337854
Ref: library/logging logging Logger log6338047
Ref: 7126338047
Ref: library/logging logging Logger exception6338249
Ref: 7136338249
Ref: library/logging logging Logger addFilter6338570
Ref: 20916338570
Ref: library/logging logging Logger removeFilter6338675
Ref: 20926338675
Ref: library/logging logging Logger filter6338788
Ref: 20936338788
Ref: library/logging logging Logger addHandler6339231
Ref: 20946339231
Ref: library/logging logging Logger removeHandler6339334
Ref: 20956339334
Ref: library/logging logging Logger findCaller6339445
Ref: 20966339445
Ref: library/logging logging Logger handle6340253
Ref: 20976340253
Ref: library/logging logging Logger makeRecord6340658
Ref: 20986340658
Ref: library/logging logging Logger hasHandlers6340926
Ref: 20996340926
Node: Logging Levels6341540
Ref: library/logging levels6341677
Ref: 20886341677
Ref: library/logging logging-levels6341677
Ref: 209a6341677
Node: Handler Objects6342547
Ref: library/logging handler6342687
Ref: 209b6342687
Ref: library/logging handler-objects6342687
Ref: 209c6342687
Ref: library/logging logging Handler6343013
Ref: 208c6343013
Ref: library/logging logging Handler __init__6343042
Ref: 209d6343042
Ref: library/logging logging Handler createLock6343343
Ref: 209e6343343
Ref: library/logging logging Handler acquire6343537
Ref: 209f6343537
Ref: library/logging logging Handler release6343657
Ref: 20a06343657
Ref: library/logging logging Handler setLevel6343765
Ref: 20a16343765
Ref: library/logging logging Handler setFormatter6344334
Ref: 20a26344334
Ref: library/logging logging Handler addFilter6344447
Ref: 20a36344447
Ref: library/logging logging Handler removeFilter6344553
Ref: 20a46344553
Ref: library/logging logging Handler filter6344667
Ref: 20a56344667
Ref: library/logging logging Handler flush6345072
Ref: 20a66345072
Ref: library/logging logging Handler close6345246
Ref: 20a76345246
Ref: library/logging logging Handler handle6345610
Ref: 20a96345610
Ref: library/logging logging Handler handleError6345894
Ref: 20aa6345894
Ref: library/logging logging Handler format6346688
Ref: 20ac6346688
Ref: library/logging logging Handler emit6346862
Ref: 20ab6346862
Node: Formatter Objects6347182
Ref: library/logging formatter-objects6347322
Ref: 20ad6347322
Ref: library/logging id16347322
Ref: 20ae6347322
Ref: library/logging logging Formatter6348487
Ref: 208b6348487
Ref: library/logging logging Formatter format6349625
Ref: 20b26349625
Ref: library/logging logging Formatter formatTime6351045
Ref: 20b06351045
Ref: library/logging logging Formatter formatException6353337
Ref: 20b36353337
Ref: library/logging logging Formatter formatStack6353682
Ref: 20b46353682
Node: Filter Objects6353980
Ref: library/logging filter6354122
Ref: 20b66354122
Ref: library/logging filter-objects6354122
Ref: 20b76354122
Ref: library/logging logging Filter6354636
Ref: b7c6354636
Ref: library/logging logging Filter filter6354927
Ref: 20b86354927
Node: LogRecord Objects6356904
Ref: library/logging log-record6357049
Ref: 20bb6357049
Ref: library/logging logrecord-objects6357049
Ref: 20bc6357049
Ref: library/logging logging LogRecord6357342
Ref: 90b6357342
Ref: library/logging logging LogRecord getMessage6359166
Ref: 20be6359166
Node: LogRecord attributes6360661
Ref: library/logging id26360813
Ref: 20c16360813
Ref: library/logging logrecord-attributes6360813
Ref: 20af6360813
Node: LoggerAdapter Objects6368749
Ref: library/logging logger-adapter6368897
Ref: 20c36368897
Ref: library/logging loggeradapter-objects6368897
Ref: 20c46368897
Ref: library/logging logging LoggerAdapter6369177
Ref: c916369177
Ref: library/logging logging LoggerAdapter process6369371
Ref: 20c66369371
Node: Thread Safety6370581
Ref: library/logging thread-safety6370731
Ref: 20c76370731
Node: Module-Level Functions6371390
Ref: library/logging module-level-functions6371542
Ref: 20c86371542
Ref: library/logging logging getLogger6371700
Ref: 20856371700
Ref: library/logging logging getLoggerClass6372286
Ref: 20c96372286
Ref: library/logging logging getLogRecordFactory6372762
Ref: 20bf6372762
Ref: library/logging logging debug6373217
Ref: 208e6373217
Ref: library/logging logging info6377053
Ref: 20b96377053
Ref: library/logging logging warning6377229
Ref: 20cb6377229
Ref: library/logging logging error6377621
Ref: 20cc6377621
Ref: library/logging logging critical6377799
Ref: 20cd6377799
Ref: library/logging logging exception6377983
Ref: 20ce6377983
Ref: library/logging logging log6378288
Ref: 20cf6378288
Ref: library/logging logging disable6379216
Ref: ed06379216
Ref: library/logging logging addLevelName6380421
Ref: 20d06380421
Ref: library/logging logging getLevelName6381079
Ref: 20d26381079
Ref: library/logging logging makeLogRecord6382677
Ref: 20bd6382677
Ref: library/logging logging basicConfig6383040
Ref: 1e16383040
Ref: library/logging logging shutdown6387336
Ref: 20a86387336
Ref: library/logging logging setLoggerClass6387776
Ref: 20ca6387776
Ref: library/logging logging setLogRecordFactory6388408
Ref: 20c06388408
Ref: Module-Level Functions-Footnote-16389733
Node: Module-Level Attributes6389776
Ref: library/logging module-level-attributes6389951
Ref: 20d36389951
Ref: library/logging logging lastResort6390020
Ref: b7b6390020
Node: Integration with the warnings module6390616
Ref: library/logging integration-with-the-warnings-module6390760
Ref: 20d46390760
Ref: library/logging logging captureWarnings6390982
Ref: 20d56390982
Ref: Integration with the warnings module-Footnote-16392363
Ref: Integration with the warnings module-Footnote-26392412
Node: logging config --- Logging configuration6392465
Ref: library/logging config doc6392669
Ref: 20d66392669
Ref: library/logging config logging-config-logging-configuration6392669
Ref: 20d76392669
Ref: library/logging config module-logging config6392669
Ref: ac6392669
Ref: logging config --- Logging configuration-Footnote-16393289
Node: Configuration functions6393362
Ref: library/logging config configuration-functions6393502
Ref: 20d86393502
Ref: library/logging config logging-config-api6393502
Ref: c8d6393502
Ref: library/logging config logging config dictConfig6393944
Ref: b306393944
Ref: library/logging config logging config fileConfig6396058
Ref: 3ae6396058
Ref: library/logging config logging config listen6398269
Ref: 8776398269
Ref: library/logging config logging config stopListening6401600
Ref: 20dc6401600
Node: Configuration dictionary schema6401842
Ref: library/logging config configuration-dictionary-schema6402016
Ref: 20dd6402016
Ref: library/logging config logging-config-dictschema6402016
Ref: 20d96402016
Node: Dictionary Schema Details6402954
Ref: library/logging config dictionary-schema-details6403081
Ref: 20df6403081
Node: Incremental Configuration6408049
Ref: library/logging config incremental-configuration6408203
Ref: 20e36408203
Ref: library/logging config logging-config-dict-incremental6408203
Ref: 20e26408203
Node: Object connections6409648
Ref: library/logging config logging-config-dict-connections6409797
Ref: 20de6409797
Ref: library/logging config object-connections6409797
Ref: 20e46409797
Node: User-defined objects6412192
Ref: library/logging config logging-config-dict-userdef6412342
Ref: 20e06412342
Ref: library/logging config user-defined-objects6412342
Ref: 20e56412342
Node: Access to external objects6415608
Ref: library/logging config access-to-external-objects6415766
Ref: 20e66415766
Ref: library/logging config logging-config-dict-externalobj6415766
Ref: 20e76415766
Node: Access to internal objects6417065
Ref: library/logging config access-to-internal-objects6417241
Ref: 20e86417241
Ref: library/logging config logging-config-dict-internalobj6417241
Ref: 20e96417241
Node: Import resolution and custom importers6420595
Ref: library/logging config import-resolution-and-custom-importers6420736
Ref: 20eb6420736
Ref: library/logging config logging-import-resolution6420736
Ref: 20ec6420736
Node: Configuration file format6421714
Ref: library/logging config configuration-file-format6421856
Ref: 20ed6421856
Ref: library/logging config logging-config-fileformat6421856
Ref: 20da6421856
Node: logging handlers --- Logging handlers6429554
Ref: library/logging handlers doc6429754
Ref: 20ee6429754
Ref: library/logging handlers logging-handlers-logging-handlers6429754
Ref: 20ef6429754
Ref: library/logging handlers module-logging handlers6429754
Ref: ad6429754
Ref: logging handlers --- Logging handlers-Footnote-16430818
Node: StreamHandler6430894
Ref: library/logging handlers stream-handler6431001
Ref: 20f16431001
Ref: library/logging handlers streamhandler6431001
Ref: 20f26431001
Ref: library/logging handlers logging StreamHandler6431314
Ref: b7a6431314
Ref: library/logging handlers logging StreamHandler emit6431552
Ref: 20f36431552
Ref: library/logging handlers logging StreamHandler flush6431891
Ref: 20f46431891
Ref: library/logging handlers logging StreamHandler setStream6432190
Ref: 3ad6432190
Node: FileHandler6432979
Ref: library/logging handlers file-handler6433106
Ref: 20f56433106
Ref: library/logging handlers filehandler6433106
Ref: 20f66433106
Ref: library/logging handlers logging FileHandler6433340
Ref: 20f06433340
Ref: library/logging handlers logging FileHandler close6433982
Ref: 20f86433982
Ref: library/logging handlers logging FileHandler emit6434043
Ref: 20f76434043
Node: NullHandler6434124
Ref: library/logging handlers null-handler6434256
Ref: 20f96434256
Ref: library/logging handlers nullhandler6434256
Ref: 20fa6434256
Ref: library/logging handlers logging NullHandler6434512
Ref: c216434512
Ref: library/logging handlers logging NullHandler emit6434612
Ref: 20fb6434612
Ref: library/logging handlers logging NullHandler handle6434687
Ref: 20fc6434687
Ref: library/logging handlers logging NullHandler createLock6434764
Ref: 20fd6434764
Node: WatchedFileHandler6435052
Ref: library/logging handlers watched-file-handler6435192
Ref: 20ff6435192
Ref: library/logging handlers watchedfilehandler6435192
Ref: 21006435192
Ref: library/logging handlers logging handlers WatchedFileHandler6436207
Ref: 21016436207
Ref: library/logging handlers logging handlers WatchedFileHandler reopenIfNeeded6436872
Ref: 5676436872
Ref: library/logging handlers logging handlers WatchedFileHandler emit6437167
Ref: 21026437167
Node: BaseRotatingHandler6437341
Ref: library/logging handlers base-rotating-handler6437489
Ref: 21036437489
Ref: library/logging handlers baserotatinghandler6437489
Ref: 21046437489
Ref: library/logging handlers logging handlers BaseRotatingHandler6437876
Ref: 21056437876
Ref: library/logging handlers logging handlers BaseRotatingHandler namer6438053
Ref: 21066438053
Ref: library/logging handlers logging handlers BaseRotatingHandler rotator6438677
Ref: 21086438677
Ref: library/logging handlers logging handlers BaseRotatingHandler rotation_filename6438955
Ref: 21076438955
Ref: library/logging handlers logging handlers BaseRotatingHandler rotate6439514
Ref: 21096439514
Node: RotatingFileHandler6440824
Ref: library/logging handlers rotating-file-handler6440978
Ref: 210b6440978
Ref: library/logging handlers rotatingfilehandler6440978
Ref: 210c6440978
Ref: library/logging handlers logging handlers RotatingFileHandler6441170
Ref: 20e16441170
Ref: library/logging handlers logging handlers RotatingFileHandler doRollover6442964
Ref: 210e6442964
Ref: library/logging handlers logging handlers RotatingFileHandler emit6443050
Ref: 210d6443050
Node: TimedRotatingFileHandler6443188
Ref: library/logging handlers timed-rotating-file-handler6443336
Ref: 210f6443336
Ref: library/logging handlers timedrotatingfilehandler6443336
Ref: 21106443336
Ref: library/logging handlers logging handlers TimedRotatingFileHandler6443569
Ref: 8736443569
Ref: library/logging handlers logging handlers TimedRotatingFileHandler doRollover6448522
Ref: 21126448522
Ref: library/logging handlers logging handlers TimedRotatingFileHandler emit6448608
Ref: 21116448608
Node: SocketHandler6448741
Ref: library/logging handlers socket-handler6448885
Ref: 21136448885
Ref: library/logging handlers sockethandler6448885
Ref: 21146448885
Ref: library/logging handlers logging handlers SocketHandler6449097
Ref: 8746449097
Ref: library/logging handlers logging handlers SocketHandler close6449496
Ref: 21156449496
Ref: library/logging handlers logging handlers SocketHandler emit6449559
Ref: 21166449559
Ref: library/logging handlers logging handlers SocketHandler handleError6450000
Ref: 21176450000
Ref: library/logging handlers logging handlers SocketHandler makeSocket6450236
Ref: 21186450236
Ref: library/logging handlers logging handlers SocketHandler makePickle6450485
Ref: 21196450485
Ref: library/logging handlers logging handlers SocketHandler send6451301
Ref: 211a6451301
Ref: library/logging handlers logging handlers SocketHandler createSocket6451628
Ref: 211b6451628
Node: DatagramHandler6452834
Ref: library/logging handlers datagram-handler6452967
Ref: 211c6452967
Ref: library/logging handlers datagramhandler6452967
Ref: 211d6452967
Ref: library/logging handlers logging handlers DatagramHandler6453203
Ref: 8756453203
Ref: library/logging handlers logging handlers DatagramHandler emit6453606
Ref: 211e6453606
Ref: library/logging handlers logging handlers DatagramHandler makeSocket6453966
Ref: 211f6453966
Ref: library/logging handlers logging handlers DatagramHandler send6454158
Ref: 21206454158
Node: SysLogHandler6454379
Ref: library/logging handlers syslog-handler6454516
Ref: 21216454516
Ref: library/logging handlers sysloghandler6454516
Ref: 21226454516
Ref: library/logging handlers logging handlers SysLogHandler6454722
Ref: a236454722
Ref: library/logging handlers logging handlers SysLogHandler close6456377
Ref: 21236456377
Ref: library/logging handlers logging handlers SysLogHandler emit6456459
Ref: 21246456459
Ref: library/logging handlers logging handlers SysLogHandler encodePriority6458311
Ref: 21256458311
Ref: library/logging handlers logging handlers SysLogHandler mapPriority6462341
Ref: 21266462341
Ref: SysLogHandler-Footnote-16462837
Ref: SysLogHandler-Footnote-26462880
Ref: SysLogHandler-Footnote-36462929
Node: NTEventLogHandler6462972
Ref: library/logging handlers nt-eventlog-handler6463105
Ref: 21276463105
Ref: library/logging handlers nteventloghandler6463105
Ref: 21286463105
Ref: library/logging handlers logging handlers NTEventLogHandler6463440
Ref: 21296463440
Ref: library/logging handlers logging handlers NTEventLogHandler close6464502
Ref: 212a6464502
Ref: library/logging handlers logging handlers NTEventLogHandler emit6464910
Ref: 212b6464910
Ref: library/logging handlers logging handlers NTEventLogHandler getEventCategory6465074
Ref: 212c6465074
Ref: library/logging handlers logging handlers NTEventLogHandler getEventType6465282
Ref: 212d6465282
Ref: library/logging handlers logging handlers NTEventLogHandler getMessageID6465881
Ref: 212e6465881
Node: SMTPHandler6466317
Ref: library/logging handlers smtp-handler6466450
Ref: 212f6466450
Ref: library/logging handlers smtphandler6466450
Ref: 21306466450
Ref: library/logging handlers logging handlers SMTPHandler6466647
Ref: 21316466647
Ref: library/logging handlers logging handlers SMTPHandler emit6467899
Ref: 21326467899
Ref: library/logging handlers logging handlers SMTPHandler getSubject6468009
Ref: 21336468009
Node: MemoryHandler6468161
Ref: library/logging handlers memory-handler6468288
Ref: 21346468288
Ref: library/logging handlers memoryhandler6468288
Ref: 21356468288
Ref: library/logging handlers logging handlers BufferingHandler6468991
Ref: 21366468991
Ref: library/logging handlers logging handlers BufferingHandler emit6469188
Ref: 21376469188
Ref: library/logging handlers logging handlers BufferingHandler flush6469384
Ref: 21396469384
Ref: library/logging handlers logging handlers BufferingHandler shouldFlush6469543
Ref: 21386469543
Ref: library/logging handlers logging handlers MemoryHandler6469732
Ref: 20ea6469732
Ref: library/logging handlers logging handlers MemoryHandler close6470539
Ref: 213b6470539
Ref: library/logging handlers logging handlers MemoryHandler flush6470673
Ref: 213c6470673
Ref: library/logging handlers logging handlers MemoryHandler setTarget6470950
Ref: 213a6470950
Ref: library/logging handlers logging handlers MemoryHandler shouldFlush6471046
Ref: 213d6471046
Node: HTTPHandler6471178
Ref: library/logging handlers http-handler6471306
Ref: 213e6471306
Ref: library/logging handlers httphandler6471306
Ref: 213f6471306
Ref: library/logging handlers logging handlers HTTPHandler6471537
Ref: 7166471537
Ref: library/logging handlers logging handlers HTTPHandler mapLogRecord6472489
Ref: 21406472489
Ref: library/logging handlers logging handlers HTTPHandler emit6472951
Ref: 21416472951
Node: QueueHandler6473693
Ref: library/logging handlers queue-handler6473821
Ref: 21426473821
Ref: library/logging handlers queuehandler6473821
Ref: 21436473821
Ref: library/logging handlers logging handlers QueueHandler6474558
Ref: 21446474558
Ref: library/logging handlers logging handlers QueueHandler emit6475056
Ref: 21466475056
Ref: library/logging handlers logging handlers QueueHandler prepare6475541
Ref: 21476475541
Ref: library/logging handlers logging handlers QueueHandler enqueue6476094
Ref: 21456476094
Node: QueueListener6476346
Ref: library/logging handlers queue-listener6476454
Ref: 21486476454
Ref: library/logging handlers queuelistener6476454
Ref: 21496476454
Ref: library/logging handlers logging handlers QueueListener6477472
Ref: 7176477472
Ref: library/logging handlers logging handlers QueueListener dequeue6478511
Ref: 214a6478511
Ref: library/logging handlers logging handlers QueueListener prepare6478798
Ref: 214b6478798
Ref: library/logging handlers logging handlers QueueListener handle6479121
Ref: 214c6479121
Ref: library/logging handlers logging handlers QueueListener start6479389
Ref: 214d6479389
Ref: library/logging handlers logging handlers QueueListener stop6479558
Ref: 214e6479558
Ref: library/logging handlers logging handlers QueueListener enqueue_sentinel6479875
Ref: 214f6479875
Node: getpass --- Portable password input6480375
Ref: library/getpass doc6480591
Ref: 21506480591
Ref: library/getpass getpass-portable-password-input6480591
Ref: 21516480591
Ref: library/getpass module-getpass6480591
Ref: 886480591
Ref: library/getpass getpass getpass6480841
Ref: 21526480841
Ref: library/getpass getpass GetPassWarning6481690
Ref: 21536481690
Ref: library/getpass getpass getuser6481815
Ref: 1ef56481815
Ref: getpass --- Portable password input-Footnote-16482396
Node: curses --- Terminal handling for character-cell displays6482462
Ref: library/curses doc6482697
Ref: 21546482697
Ref: library/curses curses-terminal-handling-for-character-cell-displays6482697
Ref: 21556482697
Ref: library/curses module-curses6482697
Ref: 2c6482697
Ref: curses --- Terminal handling for character-cell displays-Footnote-16484924
Node: Functions<3>6484987
Ref: library/curses curses-functions6485115
Ref: 21576485115
Ref: library/curses functions6485115
Ref: 21586485115
Ref: library/curses curses error6485219
Ref: 21596485219
Ref: library/curses curses baudrate6485580
Ref: 215a6485580
Ref: library/curses curses beep6485930
Ref: 215b6485930
Ref: library/curses curses can_change_color6485994
Ref: 215c6485994
Ref: library/curses curses cbreak6486164
Ref: 215d6486164
Ref: library/curses curses color_content6486636
Ref: 215f6486636
Ref: library/curses curses color_pair6487017
Ref: 21606487017
Ref: library/curses curses curs_set6487390
Ref: 21626487390
Ref: library/curses curses def_prog_mode6487808
Ref: 21636487808
Ref: library/curses curses def_shell_mode6488126
Ref: 21656488126
Ref: library/curses curses delay_output6488462
Ref: 21676488462
Ref: library/curses curses doupdate6488550
Ref: 21686488550
Ref: library/curses curses echo6489373
Ref: 216c6489373
Ref: library/curses curses endwin6489507
Ref: 216d6489507
Ref: library/curses curses erasechar6489608
Ref: 216e6489608
Ref: library/curses curses filter6489874
Ref: 216f6489874
Ref: library/curses curses flash6490483
Ref: 21716490483
Ref: library/curses curses flushinp6490744
Ref: 21726490744
Ref: library/curses curses getmouse6490928
Ref: 21736490928
Ref: library/curses curses getsyx6491732
Ref: 21756491732
Ref: library/curses curses getwin6491941
Ref: 21776491941
Ref: library/curses curses has_colors6492175
Ref: 21786492175
Ref: library/curses curses has_ic6492305
Ref: 21796492305
Ref: library/curses curses has_il6492559
Ref: 217a6492559
Ref: library/curses curses has_key6492854
Ref: 217b6492854
Ref: library/curses curses halfdelay6493006
Ref: 217c6493006
Ref: library/curses curses init_color6493442
Ref: 217e6493442
Ref: library/curses curses init_pair6494097
Ref: 217f6494097
Ref: library/curses curses initscr6494816
Ref: 21706494816
Ref: library/curses curses is_term_resized6495091
Ref: 21826495091
Ref: library/curses curses isendwin6495260
Ref: 21846495260
Ref: library/curses curses keyname6495416
Ref: 21856495416
Ref: library/curses curses killchar6495945
Ref: 21866495945
Ref: library/curses curses longname6496214
Ref: 21876496214
Ref: library/curses curses meta6496487
Ref: 21886496487
Ref: library/curses curses mouseinterval6496642
Ref: 21896496642
Ref: library/curses curses mousemask6496939
Ref: 218a6496939
Ref: library/curses curses napms6497357
Ref: 218b6497357
Ref: library/curses curses newpad6497423
Ref: 218c6497423
Ref: library/curses curses newwin6498509
Ref: 218d6498509
Ref: library/curses curses nl6498872
Ref: 218e6498872
Ref: library/curses curses nocbreak6499085
Ref: 217d6499085
Ref: library/curses curses noecho6499200
Ref: 218f6499200
Ref: library/curses curses nonl6499297
Ref: 21906499297
Ref: library/curses curses noqiflush6499788
Ref: 21916499788
Ref: library/curses curses noraw6500176
Ref: 21926500176
Ref: library/curses curses pair_content6500285
Ref: 21936500285
Ref: library/curses curses pair_number6500509
Ref: 21616500509
Ref: library/curses curses putp6500699
Ref: 21946500699
Ref: library/curses curses qiflush6500943
Ref: 21956500943
Ref: library/curses curses raw6501207
Ref: 215e6501207
Ref: library/curses curses reset_prog_mode6501447
Ref: 21646501447
Ref: library/curses curses reset_shell_mode6501589
Ref: 21666501589
Ref: library/curses curses resetty6501731
Ref: 21966501731
Ref: library/curses curses resize_term6501871
Ref: 21836501871
Ref: library/curses curses resizeterm6502408
Ref: 21986502408
Ref: library/curses curses savetty6502679
Ref: 21976502679
Ref: library/curses curses setsyx6502812
Ref: 21996502812
Ref: library/curses curses setupterm6502980
Ref: 219a6502980
Ref: library/curses curses start_color6503395
Ref: 219b6503395
Ref: library/curses curses termattrs6504073
Ref: 219c6504073
Ref: library/curses curses termname6504301
Ref: 219d6504301
Ref: library/curses curses tigetflag6504448
Ref: 219e6504448
Ref: library/curses curses tigetnum6504762
Ref: 219f6504762
Ref: library/curses curses tigetstr6505076
Ref: 21a06505076
Ref: library/curses curses tparm6505380
Ref: 21a16505380
Ref: library/curses curses typeahead6505715
Ref: 21a26505715
Ref: library/curses curses unctrl6506302
Ref: 21a36506302
Ref: library/curses curses ungetch6506581
Ref: 21a46506581
Ref: library/curses curses update_lines_cols6506758
Ref: 6cb6506758
Ref: library/curses curses unget_wch6506913
Ref: 9e56506913
Ref: library/curses curses ungetmouse6507129
Ref: 21a56507129
Ref: library/curses curses use_env6507286
Ref: 21a66507286
Ref: library/curses curses use_default_colors6507794
Ref: 21806507794
Ref: library/curses curses wrapper6508225
Ref: 2a26508225
Node: Window Objects6509034
Ref: library/curses curses-window-objects6509183
Ref: 21816509183
Ref: library/curses window-objects6509183
Ref: 21a76509183
Ref: library/curses curses window addch6509365
Ref: 21a86509365
Ref: library/curses curses window addnstr6509982
Ref: 21a96509982
Ref: library/curses curses window addstr6510253
Ref: 216a6510253
Ref: library/curses curses window attroff6511267
Ref: 21aa6511267
Ref: library/curses curses window attron6511414
Ref: 21ab6511414
Ref: library/curses curses window attrset6511557
Ref: 21ac6511557
Ref: library/curses curses window bkgd6511707
Ref: 21ad6511707
Ref: library/curses curses window bkgdset6512158
Ref: 21ae6512158
Ref: library/curses curses window border6512730
Ref: 21af6512730
Ref: library/curses curses window box6514692
Ref: 21b06514692
Ref: library/curses curses window chgat6514926
Ref: 21b16514926
Ref: library/curses curses window clear6515574
Ref: 21b36515574
Ref: library/curses curses window clearok6515735
Ref: 21b56515735
Ref: library/curses curses window clrtobot6515886
Ref: 21b66515886
Ref: library/curses curses window clrtoeol6516089
Ref: 21b76516089
Ref: library/curses curses window cursyncup6516175
Ref: 21b86516175
Ref: library/curses curses window delch6516349
Ref: 21b96516349
Ref: library/curses curses window deleteln6516434
Ref: 21ba6516434
Ref: library/curses curses window derwin6516564
Ref: 21bb6516564
Ref: library/curses curses window echochar6516982
Ref: 21bd6516982
Ref: library/curses curses window enclose6517142
Ref: 21be6517142
Ref: library/curses curses window encoding6517452
Ref: 9e36517452
Ref: library/curses curses window erase6517831
Ref: 21b46517831
Ref: library/curses curses window getbegyx6517890
Ref: 21bf6517890
Ref: library/curses curses window getbkgd6518000
Ref: 21c06518000
Ref: library/curses curses window getch6518121
Ref: 21746518121
Ref: library/curses curses window get_wch6518447
Ref: 9e46518447
Ref: library/curses curses window getkey6518717
Ref: 21c16518717
Ref: library/curses curses window getmaxyx6519031
Ref: 21c26519031
Ref: library/curses curses window getparyx6519142
Ref: 21c36519142
Ref: library/curses curses window getstr6519352
Ref: 21c46519352
Ref: library/curses curses window getyx6519592
Ref: 21c56519592
Ref: library/curses curses window hline6519739
Ref: 21c66519739
Ref: library/curses curses window idcok6519937
Ref: 21c76519937
Ref: library/curses curses window idlok6520289
Ref: 21c86520289
Ref: library/curses curses window immedok6520488
Ref: 21c96520488
Ref: library/curses curses window inch6520843
Ref: 21ca6520843
Ref: library/curses curses window insch6521037
Ref: 21cb6521037
Ref: library/curses curses window insdelln6521263
Ref: 21cc6521263
Ref: library/curses curses window insertln6521648
Ref: 21cd6521648
Ref: library/curses curses window insnstr6521784
Ref: 21ce6521784
Ref: library/curses curses window insstr6522309
Ref: 21cf6522309
Ref: library/curses curses window instr6522740
Ref: 21d06522740
Ref: library/curses curses window is_linetouched6523148
Ref: 21d16523148
Ref: library/curses curses window is_wintouched6523437
Ref: 21d26523437
Ref: library/curses curses window keypad6523623
Ref: 21d36523623
Ref: library/curses curses window leaveok6523897
Ref: 21766523897
Ref: library/curses curses window move6524247
Ref: 21d46524247
Ref: library/curses curses window mvderwin6524336
Ref: 21d56524336
Ref: library/curses curses window mvwin6524619
Ref: 21d66524619
Ref: library/curses curses window nodelay6524741
Ref: 21d76524741
Ref: library/curses curses window notimeout6524856
Ref: 21d86524856
Ref: library/curses curses window noutrefresh6525126
Ref: 21696525126
Ref: library/curses curses window overlay6525406
Ref: 21d96525406
Ref: library/curses curses window overwrite6526061
Ref: 21da6526061
Ref: library/curses curses window putwin6526719
Ref: 21db6526719
Ref: library/curses curses window redrawln6526931
Ref: 21dc6526931
Ref: library/curses curses window redrawwin6527143
Ref: 21dd6527143
Ref: library/curses curses window refresh6527295
Ref: 216b6527295
Ref: library/curses curses window resize6528322
Ref: 21de6528322
Ref: library/curses curses window scroll6528680
Ref: 21df6528680
Ref: library/curses curses window scrollok6528794
Ref: 21e06528794
Ref: library/curses curses window setscrreg6529336
Ref: 21e16529336
Ref: library/curses curses window standend6529511
Ref: 21e26529511
Ref: library/curses curses window standout6529668
Ref: 21e36529668
Ref: library/curses curses window subpad6529744
Ref: 21e46529744
Ref: library/curses curses window subwin6529995
Ref: 21bc6529995
Ref: library/curses curses window syncdown6530365
Ref: 21e56530365
Ref: library/curses curses window syncok6530617
Ref: 21e66530617
Ref: library/curses curses window syncup6530786
Ref: 21e76530786
Ref: library/curses curses window timeout6530918
Ref: 21e86530918
Ref: library/curses curses window touchline6531427
Ref: 21b26531427
Ref: library/curses curses window touchwin6531741
Ref: 21e96531741
Ref: library/curses curses window untouchwin6531872
Ref: 21ea6531872
Ref: library/curses curses window vline6532011
Ref: 21eb6532011
Ref: Window Objects-Footnote-16532243
Node: Constants<6>6532286
Ref: library/curses constants6532414
Ref: 21ec6532414
Ref: library/curses curses ERR6532521
Ref: 21ed6532521
Ref: library/curses curses OK6532666
Ref: 21ee6532666
Ref: library/curses curses version6532809
Ref: 21ef6532809
Ref: library/curses curses ncurses_version6532946
Ref: 1c06532946
Node: curses textpad --- Text input widget for curses programs6551503
Ref: library/curses curses-textpad-text-input-widget-for-curses-programs6551750
Ref: 21f06551750
Ref: library/curses module-curses textpad6551750
Ref: 2f6551750
Ref: library/curses curses textpad rectangle6552340
Ref: 21f26552340
Node: Textbox objects6553061
Ref: library/curses curses-textpad-objects6553169
Ref: 21f36553169
Ref: library/curses textbox-objects6553169
Ref: 21f46553169
Ref: library/curses curses textpad Textbox6553285
Ref: 21f16553285
Ref: library/curses curses textpad Textbox edit6553765
Ref: 21f66553765
Ref: library/curses curses textpad Textbox do_command6554342
Ref: 21f76554342
Ref: library/curses curses textpad Textbox gather6557872
Ref: 21f86557872
Ref: library/curses curses textpad Textbox stripspaces6558071
Ref: 21f56558071
Node: curses ascii --- Utilities for ASCII characters6558479
Ref: library/curses ascii doc6558721
Ref: 21f96558721
Ref: library/curses ascii curses-ascii-utilities-for-ascii-characters6558721
Ref: 21fa6558721
Ref: library/curses ascii module-curses ascii6558721
Ref: 2d6558721
Ref: library/curses ascii curses ascii isalnum6562395
Ref: 21fb6562395
Ref: library/curses ascii curses ascii isalpha6562540
Ref: 21fc6562540
Ref: library/curses ascii curses ascii isascii6562683
Ref: 21fd6562683
Ref: library/curses ascii curses ascii isblank6562790
Ref: 21fe6562790
Ref: library/curses ascii curses ascii iscntrl6562901
Ref: 21ff6562901
Ref: library/curses ascii curses ascii isdigit6563025
Ref: 22006563025
Ref: library/curses ascii curses ascii isgraph6563187
Ref: 22016563187
Ref: library/curses ascii curses ascii islower6563286
Ref: 22026563286
Ref: library/curses ascii curses ascii isprint6563372
Ref: 22036563372
Ref: library/curses ascii curses ascii ispunct6563474
Ref: 22046563474
Ref: library/curses ascii curses ascii isspace6563615
Ref: 22056563615
Ref: library/curses ascii curses ascii isupper6563781
Ref: 22066563781
Ref: library/curses ascii curses ascii isxdigit6563863
Ref: 22076563863
Ref: library/curses ascii curses ascii isctrl6564004
Ref: 22086564004
Ref: library/curses ascii curses ascii ismeta6564111
Ref: 22096564111
Ref: library/curses ascii curses ascii ascii6564709
Ref: 220a6564709
Ref: library/curses ascii curses ascii ctrl6564814
Ref: 220b6564814
Ref: library/curses ascii curses ascii alt6564980
Ref: 220c6564980
Ref: library/curses ascii curses ascii unctrl6565250
Ref: 220d6565250
Ref: library/curses ascii curses ascii controlnames6565803
Ref: 220e6565803
Node: curses panel --- A panel stack extension for curses6566049
Ref: library/curses panel doc6566296
Ref: 220f6566296
Ref: library/curses panel curses-panel-a-panel-stack-extension-for-curses6566296
Ref: 22106566296
Ref: library/curses panel module-curses panel6566296
Ref: 2e6566296
Node: Functions<4>6566774
Ref: library/curses panel cursespanel-functions6566896
Ref: 22116566896
Ref: library/curses panel functions6566896
Ref: 22126566896
Ref: library/curses panel curses panel bottom_panel6567006
Ref: 22136567006
Ref: library/curses panel curses panel new_panel6567099
Ref: 22146567099
Ref: library/curses panel curses panel top_panel6567399
Ref: 22156567399
Ref: library/curses panel curses panel update_panels6567486
Ref: 22166567486
Node: Panel Objects6567695
Ref: library/curses panel curses-panel-objects6567817
Ref: 22176567817
Ref: library/curses panel panel-objects6567817
Ref: 22186567817
Ref: library/curses panel curses panel Panel above6568173
Ref: 22196568173
Ref: library/curses panel curses panel Panel below6568256
Ref: 221a6568256
Ref: library/curses panel curses panel Panel bottom6568339
Ref: 221b6568339
Ref: library/curses panel curses panel Panel hidden6568423
Ref: 221c6568423
Ref: library/curses panel curses panel Panel hide6568549
Ref: 221d6568549
Ref: library/curses panel curses panel Panel move6568689
Ref: 221e6568689
Ref: library/curses panel curses panel Panel replace6568787
Ref: 221f6568787
Ref: library/curses panel curses panel Panel set_userptr6568897
Ref: 22206568897
Ref: library/curses panel curses panel Panel show6569097
Ref: 22216569097
Ref: library/curses panel curses panel Panel top6569186
Ref: 22226569186
Ref: library/curses panel curses panel Panel userptr6569260
Ref: 22236569260
Ref: library/curses panel curses panel Panel window6569381
Ref: 22246569381
Node: platform --- Access to underlying platform's identifying data6569475
Ref: library/platform doc6569714
Ref: 22256569714
Ref: library/platform module-platform6569714
Ref: cf6569714
Ref: library/platform platform-access-to-underlying-platform-s-identifying-data6569714
Ref: 22266569714
Ref: platform --- Access to underlying platform's identifying data-Footnote-16570211
Node: Cross Platform6570278
Ref: library/platform cross-platform6570412
Ref: 22276570412
Ref: library/platform platform architecture6570463
Ref: 101b6570463
Ref: library/platform platform machine6571800
Ref: 22286571800
Ref: library/platform platform node6571954
Ref: 22296571954
Ref: library/platform platform platform6572127
Ref: 10206572127
Ref: library/platform platform processor6573051
Ref: 222b6573051
Ref: library/platform platform python_build6573370
Ref: 222c6573370
Ref: library/platform platform python_compiler6573515
Ref: 222d6573515
Ref: library/platform platform python_branch6573636
Ref: 222e6573636
Ref: library/platform platform python_implementation6573748
Ref: 222f6573748
Ref: library/platform platform python_revision6573950
Ref: 22306573950
Ref: library/platform platform python_version6574071
Ref: 22316574071
Ref: library/platform platform python_version_tuple6574318
Ref: 22326574318
Ref: library/platform platform release6574596
Ref: 22336574596
Ref: library/platform platform system6574769
Ref: 22346574769
Ref: library/platform platform system_alias6574979
Ref: 222a6574979
Ref: library/platform platform version6575260
Ref: 22356575260
Ref: library/platform platform uname6575435
Ref: 101e6575435
Node: Java Platform6576112
Ref: library/platform java-platform6576271
Ref: 22366576271
Ref: library/platform platform java_ver6576320
Ref: 22376576320
Node: Windows Platform6576789
Ref: library/platform windows-platform6576949
Ref: 22386576949
Ref: library/platform platform win32_ver6577004
Ref: f1d6577004
Ref: library/platform platform win32_edition6577691
Ref: 22396577691
Ref: library/platform platform win32_is_iot6577960
Ref: 223a6577960
Node: Mac OS Platform6578148
Ref: library/platform mac-os-platform6578309
Ref: 223b6578309
Ref: library/platform platform mac_ver6578362
Ref: 10216578362
Node: Unix Platforms6578742
Ref: library/platform unix-platforms6578878
Ref: 223c6578878
Ref: library/platform platform libc_ver6578929
Ref: 101d6578929
Node: errno --- Standard errno system symbols6579544
Ref: library/errno doc6579780
Ref: 223d6579780
Ref: library/errno errno-standard-errno-system-symbols6579780
Ref: 223e6579780
Ref: library/errno module-errno6579780
Ref: 7c6579780
Ref: library/errno errno errorcode6580192
Ref: 223f6580192
Ref: library/errno errno EPERM6580713
Ref: 22406580713
Ref: library/errno errno ENOENT6580766
Ref: 22416580766
Ref: library/errno errno ESRCH6580822
Ref: 22426580822
Ref: library/errno errno EINTR6580867
Ref: 65d6580867
Ref: library/errno errno EIO6581022
Ref: 22436581022
Ref: library/errno errno ENXIO6581059
Ref: 22446581059
Ref: library/errno errno E2BIG6581114
Ref: 22456581114
Ref: library/errno errno ENOEXEC6581161
Ref: 22466581161
Ref: library/errno errno EBADF6581210
Ref: 22476581210
Ref: library/errno errno ECHILD6581255
Ref: 22486581255
Ref: library/errno errno EAGAIN6581304
Ref: 1f3d6581304
Ref: library/errno errno ENOMEM6581344
Ref: 22496581344
Ref: library/errno errno EACCES6581388
Ref: 224a6581388
Ref: library/errno errno EFAULT6581436
Ref: 224b6581436
Ref: library/errno errno ENOTBLK6581478
Ref: 224c6581478
Ref: library/errno errno EBUSY6581531
Ref: 224d6581531
Ref: library/errno errno EEXIST6581584
Ref: 224e6581584
Ref: library/errno errno EXDEV6581626
Ref: 1f136581626
Ref: library/errno errno ENODEV6581673
Ref: 224f6581673
Ref: library/errno errno ENOTDIR6581718
Ref: 22506581718
Ref: library/errno errno EISDIR6581765
Ref: 22516581765
Ref: library/errno errno EINVAL6581810
Ref: fce6581810
Ref: library/errno errno ENFILE6581857
Ref: 22526581857
Ref: library/errno errno EMFILE6581907
Ref: 22536581907
Ref: library/errno errno ENOTTY6581957
Ref: 22546581957
Ref: library/errno errno ETXTBSY6582004
Ref: 22556582004
Ref: library/errno errno EFBIG6582050
Ref: 22566582050
Ref: library/errno errno ENOSPC6582094
Ref: 22576582094
Ref: library/errno errno ESPIPE6582148
Ref: 22586582148
Ref: library/errno errno EROFS6582191
Ref: 22596582191
Ref: library/errno errno EMLINK6582242
Ref: 225a6582242
Ref: library/errno errno EPIPE6582287
Ref: 225b6582287
Ref: library/errno errno EDOM6582328
Ref: 225c6582328
Ref: library/errno errno ERANGE6582392
Ref: 225d6582392
Ref: library/errno errno EDEADLK6582452
Ref: 225e6582452
Ref: library/errno errno ENAMETOOLONG6582513
Ref: 225f6582513
Ref: library/errno errno ENOLCK6582568
Ref: 22606582568
Ref: library/errno errno ENOSYS6582624
Ref: 22616582624
Ref: library/errno errno ENOTEMPTY6582679
Ref: 22626582679
Ref: library/errno errno ELOOP6582732
Ref: 22636582732
Ref: library/errno errno EWOULDBLOCK6582797
Ref: 22646582797
Ref: library/errno errno ENOMSG6582854
Ref: 22656582854
Ref: library/errno errno EIDRM6582911
Ref: 22666582911
Ref: library/errno errno ECHRNG6582959
Ref: 22676582959
Ref: library/errno errno EL2NSYNC6583017
Ref: 22686583017
Ref: library/errno errno EL3HLT6583074
Ref: 22696583074
Ref: library/errno errno EL3RST6583119
Ref: 226a6583119
Ref: library/errno errno ELNRNG6583163
Ref: 226b6583163
Ref: library/errno errno EUNATCH6583218
Ref: 226c6583218
Ref: library/errno errno ENOCSI6583278
Ref: 226d6583278
Ref: library/errno errno EL2HLT6583335
Ref: 226e6583335
Ref: library/errno errno EBADE6583380
Ref: 226f6583380
Ref: library/errno errno EBADR6583426
Ref: 22706583426
Ref: library/errno errno EXFULL6583482
Ref: 22716583482
Ref: library/errno errno ENOANO6583526
Ref: 22726583526
Ref: library/errno errno EBADRQC6583565
Ref: 22736583565
Ref: library/errno errno EBADSLT6583617
Ref: 22746583617
Ref: library/errno errno EDEADLOCK6583661
Ref: 22756583661
Ref: library/errno errno EBFONT6583722
Ref: 22766583722
Ref: library/errno errno ENOSTR6583773
Ref: 22776583773
Ref: library/errno errno ENODATA6583823
Ref: 22786583823
Ref: library/errno errno ETIME6583872
Ref: 22796583872
Ref: library/errno errno ENOSR6583915
Ref: 227a6583915
Ref: library/errno errno ENONET6583969
Ref: 227b6583969
Ref: library/errno errno ENOPKG6584029
Ref: 227c6584029
Ref: library/errno errno EREMOTE6584081
Ref: 227d6584081
Ref: library/errno errno ENOLINK6584129
Ref: 227e6584129
Ref: library/errno errno EADV6584182
Ref: 227f6584182
Ref: library/errno errno ESRMNT6584226
Ref: 22806584226
Ref: library/errno errno ECOMM6584270
Ref: 22816584270
Ref: library/errno errno EPROTO6584327
Ref: 22826584327
Ref: library/errno errno EMULTIHOP6584372
Ref: 22836584372
Ref: library/errno errno EDOTDOT6584424
Ref: 22846584424
Ref: library/errno errno EBADMSG6584474
Ref: 22856584474
Ref: library/errno errno EOVERFLOW6584524
Ref: 22866584524
Ref: library/errno errno ENOTUNIQ6584595
Ref: 22876584595
Ref: library/errno errno EBADFD6584654
Ref: 22886584654
Ref: library/errno errno EREMCHG6584713
Ref: 22896584713
Ref: library/errno errno ELIBACC6584767
Ref: 228a6584767
Ref: library/errno errno ELIBBAD6584837
Ref: 228b6584837
Ref: library/errno errno ELIBSCN6584905
Ref: 228c6584905
Ref: library/errno errno ELIBMAX6584968
Ref: 228d6584968
Ref: library/errno errno ELIBEXEC6585047
Ref: 228e6585047
Ref: library/errno errno EILSEQ6585117
Ref: 228f6585117
Ref: library/errno errno ERESTART6585169
Ref: 22906585169
Ref: library/errno errno ESTRPIPE6585245
Ref: 22916585245
Ref: library/errno errno EUSERS6585296
Ref: 22926585296
Ref: library/errno errno ENOTSOCK6585341
Ref: 22936585341
Ref: library/errno errno EDESTADDRREQ6585404
Ref: 22946585404
Ref: library/errno errno EMSGSIZE6585469
Ref: 22956585469
Ref: library/errno errno EPROTOTYPE6585518
Ref: 22966585518
Ref: library/errno errno ENOPROTOOPT6585583
Ref: 22976585583
Ref: library/errno errno EPROTONOSUPPORT6585641
Ref: 22986585641
Ref: library/errno errno ESOCKTNOSUPPORT6585703
Ref: 22996585703
Ref: library/errno errno EOPNOTSUPP6585768
Ref: 229a6585768
Ref: library/errno errno EPFNOSUPPORT6585848
Ref: 229b6585848
Ref: library/errno errno EAFNOSUPPORT6585914
Ref: 229c6585914
Ref: library/errno errno EADDRINUSE6585991
Ref: 229d6585991
Ref: library/errno errno EADDRNOTAVAIL6586048
Ref: 229e6586048
Ref: library/errno errno ENETDOWN6586117
Ref: 229f6586117
Ref: library/errno errno ENETUNREACH6586165
Ref: fe96586165
Ref: library/errno errno ENETRESET6586223
Ref: 22a06586223
Ref: library/errno errno ECONNABORTED6586300
Ref: 22a16586300
Ref: library/errno errno ECONNRESET6586369
Ref: 22a26586369
Ref: library/errno errno ENOBUFS6586428
Ref: 22a36586428
Ref: library/errno errno EISCONN6586485
Ref: 22a46586485
Ref: library/errno errno ENOTCONN6586556
Ref: 22a56586556
Ref: library/errno errno ESHUTDOWN6586624
Ref: 22a66586624
Ref: library/errno errno ETOOMANYREFS6586703
Ref: 22a76586703
Ref: library/errno errno ETIMEDOUT6586774
Ref: 22a86586774
Ref: library/errno errno ECONNREFUSED6586828
Ref: 22a96586828
Ref: library/errno errno EHOSTDOWN6586883
Ref: 22aa6586883
Ref: library/errno errno EHOSTUNREACH6586929
Ref: 22ab6586929
Ref: library/errno errno EALREADY6586982
Ref: 22ac6586982
Ref: library/errno errno EINPROGRESS6587044
Ref: 22ad6587044
Ref: library/errno errno ESTALE6587105
Ref: 22ae6587105
Ref: library/errno errno EUCLEAN6587157
Ref: 22af6587157
Ref: library/errno errno ENOTNAM6587213
Ref: 22b06587213
Ref: library/errno errno ENAVAIL6587272
Ref: 22b16587272
Ref: library/errno errno EISNAM6587333
Ref: 22b26587333
Ref: library/errno errno EREMOTEIO6587384
Ref: 22b36587384
Ref: library/errno errno EDQUOT6587434
Ref: 22b46587434
Node: ctypes --- A foreign function library for Python6587479
Ref: library/ctypes doc6587645
Ref: 22b56587645
Ref: library/ctypes ctypes-a-foreign-function-library-for-python6587645
Ref: 22b66587645
Ref: library/ctypes module-ctypes6587645
Ref: 2b6587645
Node: ctypes tutorial6588098
Ref: library/ctypes ctypes-ctypes-tutorial6588223
Ref: 22b76588223
Ref: library/ctypes ctypes-tutorial6588223
Ref: 22b86588223
Node: Loading dynamic link libraries6589592
Ref: library/ctypes ctypes-loading-dynamic-link-libraries6589719
Ref: 22bb6589719
Ref: library/ctypes loading-dynamic-link-libraries6589719
Ref: 22bc6589719
Node: Accessing functions from loaded dlls6591758
Ref: library/ctypes accessing-functions-from-loaded-dlls6591911
Ref: 22bd6591911
Ref: library/ctypes ctypes-accessing-functions-from-loaded-dlls6591911
Ref: 22be6591911
Node: Calling functions6594166
Ref: library/ctypes calling-functions6594311
Ref: 22bf6594311
Ref: library/ctypes ctypes-calling-functions6594311
Ref: 22c06594311
Node: Fundamental data types6596783
Ref: library/ctypes ctypes-fundamental-data-types6596919
Ref: 22c16596919
Ref: library/ctypes fundamental-data-types6596919
Ref: 22c26596919
Node: Calling functions continued6604963
Ref: library/ctypes calling-functions-continued6605131
Ref: 22d36605131
Ref: library/ctypes ctypes-calling-functions-continued6605131
Ref: 22d46605131
Node: Calling functions with your own custom data types6606215
Ref: library/ctypes calling-functions-with-your-own-custom-data-types6606419
Ref: 22d56606419
Ref: library/ctypes ctypes-calling-functions-with-own-custom-data-types6606419
Ref: 22d66606419
Node: Specifying the required argument types function prototypes6607262
Ref: library/ctypes ctypes-specifying-required-argument-types6607451
Ref: 22d76607451
Ref: library/ctypes specifying-the-required-argument-types-function-prototypes6607451
Ref: 22d86607451
Node: Return types6609277
Ref: library/ctypes ctypes-return-types6609468
Ref: 22d96609468
Ref: library/ctypes return-types6609468
Ref: 22da6609468
Node: Passing pointers or passing parameters by reference6612097
Ref: library/ctypes ctypes-passing-pointers6612251
Ref: 22dc6612251
Ref: library/ctypes passing-pointers-or-passing-parameters-by-reference6612251
Ref: 22dd6612251
Node: Structures and unions6613345
Ref: library/ctypes ctypes-structures-unions6613527
Ref: 22e06613527
Ref: library/ctypes structures-and-unions6613527
Ref: 22e16613527
Ref: library/ctypes ctypes-structureunion-alignment-byte-order6615613
Ref: 22e46615613
Node: Structure/union alignment and byte order6615940
Ref: library/ctypes structure-union-alignment-and-byte-order6616106
Ref: 22e56616106
Node: Bit fields in structures and unions6616886
Ref: library/ctypes bit-fields-in-structures-and-unions6617037
Ref: 22e86617037
Ref: library/ctypes ctypes-bit-fields-in-structures-unions6617037
Ref: 22e96617037
Node: Arrays6617624
Ref: library/ctypes arrays6617743
Ref: 22ea6617743
Ref: library/ctypes ctypes-arrays6617743
Ref: 22eb6617743
Node: Pointers6619032
Ref: library/ctypes ctypes-pointers6619132
Ref: 22ec6619132
Ref: library/ctypes pointers6619132
Ref: 22ed6619132
Node: Type conversions6621795
Ref: library/ctypes ctypes-type-conversions6621905
Ref: 22f06621905
Ref: library/ctypes type-conversions6621905
Ref: 22f16621905
Node: Incomplete Types6624507
Ref: library/ctypes ctypes-incomplete-types6624627
Ref: 22f26624627
Ref: library/ctypes incomplete-types6624627
Ref: 22f36624627
Node: Callback functions6626236
Ref: library/ctypes callback-functions6626375
Ref: 22f46626375
Ref: library/ctypes ctypes-callback-functions6626375
Ref: 22f56626375
Node: Accessing values exported from dlls6630251
Ref: library/ctypes accessing-values-exported-from-dlls6630383
Ref: 22f96630383
Ref: library/ctypes ctypes-accessing-values-exported-from-dlls6630383
Ref: 22fa6630383
Node: Surprises6633186
Ref: library/ctypes ctypes-surprises6633325
Ref: 22fd6633325
Ref: library/ctypes surprises6633325
Ref: 22fe6633325
Node: Variable-sized data types6635502
Ref: library/ctypes ctypes-variable-sized-data-types6635597
Ref: 22ff6635597
Ref: library/ctypes variable-sized-data-types6635597
Ref: 23006635597
Node: ctypes reference6637000
Ref: library/ctypes ctypes-ctypes-reference6637125
Ref: 23026637125
Ref: library/ctypes ctypes-reference6637125
Ref: 23036637125
Node: Finding shared libraries6637436
Ref: library/ctypes ctypes-finding-shared-libraries6637546
Ref: 23046637546
Ref: library/ctypes finding-shared-libraries6637546
Ref: 23056637546
Node: Loading shared libraries6640062
Ref: library/ctypes ctypes-loading-shared-libraries6640198
Ref: 23066640198
Ref: library/ctypes loading-shared-libraries6640198
Ref: 23076640198
Ref: library/ctypes ctypes CDLL6640401
Ref: 1c26640401
Ref: library/ctypes ctypes OleDLL6641434
Ref: 23086641434
Ref: library/ctypes ctypes WinDLL6642116
Ref: 230a6642116
Ref: library/ctypes ctypes PyDLL6642788
Ref: 230b6642788
Ref: library/ctypes ctypes PyDLL _handle6646503
Ref: 23106646503
Ref: library/ctypes ctypes PyDLL _name6646582
Ref: 23116646582
Ref: library/ctypes ctypes LibraryLoader6646921
Ref: 23126646921
Ref: library/ctypes ctypes LibraryLoader LoadLibrary6647387
Ref: 23136647387
Ref: Loading shared libraries-Footnote-16648968
Node: Foreign functions6649034
Ref: library/ctypes ctypes-foreign-functions6649165
Ref: 23146649165
Ref: library/ctypes foreign-functions6649165
Ref: 23156649165
Ref: library/ctypes ctypes _FuncPtr6649579
Ref: 23166649579
Ref: library/ctypes ctypes _FuncPtr restype6649881
Ref: 23176649881
Ref: library/ctypes ctypes _FuncPtr argtypes6650574
Ref: 23196650574
Ref: library/ctypes ctypes _FuncPtr errcheck6651810
Ref: 23186651810
Ref: library/ctypes ctypes ArgumentError6652791
Ref: 231a6652791
Node: Function prototypes6653428
Ref: library/ctypes ctypes-function-prototypes6653552
Ref: 231b6653552
Ref: library/ctypes function-prototypes6653552
Ref: 231c6653552
Ref: library/ctypes ctypes CFUNCTYPE6654135
Ref: 22f66654135
Ref: library/ctypes ctypes WINFUNCTYPE6654644
Ref: 22f76654644
Ref: library/ctypes ctypes PYFUNCTYPE6655094
Ref: 231d6655094
Node: Utility functions6660717
Ref: library/ctypes ctypes-utility-functions6660834
Ref: 231e6660834
Ref: library/ctypes utility-functions6660834
Ref: 231f6660834
Ref: library/ctypes ctypes addressof6660893
Ref: 23206660893
Ref: library/ctypes ctypes alignment6661134
Ref: 23216661134
Ref: library/ctypes ctypes byref6661292
Ref: 22de6661292
Ref: library/ctypes ctypes cast6661804
Ref: 10186661804
Ref: library/ctypes ctypes create_string_buffer6662096
Ref: 22d26662096
Ref: library/ctypes ctypes create_unicode_buffer6662899
Ref: fb26662899
Ref: library/ctypes ctypes DllCanUnloadNow6663716
Ref: 23226663716
Ref: library/ctypes ctypes DllGetClassObject6663959
Ref: 23236663959
Ref: library/ctypes ctypes util find_library6664217
Ref: 60f6664217
Ref: library/ctypes ctypes util find_msvcrt6664607
Ref: 23246664607
Ref: library/ctypes ctypes FormatError6665061
Ref: 23256665061
Ref: library/ctypes ctypes GetLastError6665298
Ref: 22db6665298
Ref: library/ctypes ctypes get_errno6665570
Ref: 230c6665570
Ref: library/ctypes ctypes get_last_error6665820
Ref: 230e6665820
Ref: library/ctypes ctypes memmove6666093
Ref: 23266666093
Ref: library/ctypes ctypes memset6666335
Ref: 23276666335
Ref: library/ctypes ctypes POINTER6666586
Ref: 22ef6666586
Ref: library/ctypes ctypes pointer6666832
Ref: 22df6666832
Ref: library/ctypes ctypes resize6667150
Ref: 23016667150
Ref: library/ctypes ctypes set_errno6667486
Ref: 230d6667486
Ref: library/ctypes ctypes set_last_error6667791
Ref: 230f6667791
Ref: library/ctypes ctypes sizeof6668119
Ref: 23286668119
Ref: library/ctypes ctypes string_at6668288
Ref: 23296668288
Ref: library/ctypes ctypes WinError6668655
Ref: 232a6668655
Ref: library/ctypes ctypes wstring_at6669125
Ref: 232b6669125
Node: Data types6669542
Ref: library/ctypes ctypes-data-types6669665
Ref: 232c6669665
Ref: library/ctypes data-types6669665
Ref: 232d6669665
Ref: library/ctypes ctypes _CData6669710
Ref: 10b56669710
Ref: library/ctypes ctypes _CData from_buffer6670346
Ref: 23306670346
Ref: library/ctypes ctypes _CData from_buffer_copy6670938
Ref: 23316670938
Ref: library/ctypes ctypes _CData from_address6671488
Ref: 23326671488
Ref: library/ctypes ctypes _CData from_param6671839
Ref: 23336671839
Ref: library/ctypes ctypes _CData in_dll6672399
Ref: 23346672399
Ref: library/ctypes ctypes _CData _b_base_6672701
Ref: 23356672701
Ref: library/ctypes ctypes _CData _b_needsfree_6673003
Ref: 23366673003
Ref: library/ctypes ctypes _CData _objects6673174
Ref: 232e6673174
Node: Fundamental data types<2>6673483
Ref: library/ctypes ctypes-fundamental-data-types-26673610
Ref: 23376673610
Ref: library/ctypes id16673610
Ref: 23386673610
Ref: library/ctypes ctypes _SimpleCData6673679
Ref: 23396673679
Ref: library/ctypes ctypes _SimpleCData value6674153
Ref: 233a6674153
Ref: library/ctypes ctypes c_byte6675505
Ref: 22c66675505
Ref: library/ctypes ctypes c_char6675724
Ref: 22c46675724
Ref: library/ctypes ctypes c_char_p6675971
Ref: 22d06675971
Ref: library/ctypes ctypes c_double6676273
Ref: eb66676273
Ref: library/ctypes ctypes c_longdouble6676409
Ref: eb76676409
Ref: library/ctypes ctypes c_float6676662
Ref: 22cf6676662
Ref: library/ctypes ctypes c_int6676796
Ref: 22b96676796
Ref: library/ctypes ctypes c_int86677067
Ref: 233b6677067
Ref: library/ctypes ctypes c_int166677197
Ref: 233c6677197
Ref: library/ctypes ctypes c_int326677330
Ref: 233d6677330
Ref: library/ctypes ctypes c_int646677461
Ref: 233e6677461
Ref: library/ctypes ctypes c_long6677597
Ref: 22ba6677597
Ref: library/ctypes ctypes c_longlong6677768
Ref: 22cc6677768
Ref: library/ctypes ctypes c_short6677953
Ref: 22c86677953
Ref: library/ctypes ctypes c_size_t6678126
Ref: 22ce6678126
Ref: library/ctypes ctypes c_ssize_t6678201
Ref: bd66678201
Ref: library/ctypes ctypes c_ubyte6678302
Ref: 22c76678302
Ref: library/ctypes ctypes c_uint6678523
Ref: 22ca6678523
Ref: library/ctypes ctypes c_uint86678799
Ref: 233f6678799
Ref: library/ctypes ctypes c_uint166678933
Ref: 23406678933
Ref: library/ctypes ctypes c_uint326679070
Ref: 23416679070
Ref: library/ctypes ctypes c_uint646679205
Ref: 23426679205
Ref: library/ctypes ctypes c_ulong6679345
Ref: 22cb6679345
Ref: library/ctypes ctypes c_ulonglong6679519
Ref: 22cd6679519
Ref: library/ctypes ctypes c_ushort6679707
Ref: 22c96679707
Ref: library/ctypes ctypes c_void_p6679888
Ref: 22d16679888
Ref: library/ctypes ctypes c_wchar6680060
Ref: 22c56680060
Ref: library/ctypes ctypes c_wchar_p6680326
Ref: e9e6680326
Ref: library/ctypes ctypes c_bool6680541
Ref: 22c36680541
Ref: library/ctypes ctypes HRESULT6680769
Ref: 23096680769
Ref: library/ctypes ctypes py_object6680931
Ref: 23436680931
Node: Structured data types6681328
Ref: library/ctypes ctypes-structured-data-types6681464
Ref: 23446681464
Ref: library/ctypes structured-data-types6681464
Ref: 23456681464
Ref: library/ctypes ctypes Union6681531
Ref: 22e36681531
Ref: library/ctypes ctypes BigEndianStructure6681630
Ref: 22e66681630
Ref: library/ctypes ctypes LittleEndianStructure6681752
Ref: 22e76681752
Ref: library/ctypes ctypes Structure6682011
Ref: 22e26682011
Ref: library/ctypes ctypes Structure _fields_6682436
Ref: 23466682436
Ref: library/ctypes ctypes Structure _pack_6684027
Ref: 23476684027
Ref: library/ctypes ctypes Structure _anonymous_6684312
Ref: 23486684312
Node: Arrays and pointers6686665
Ref: library/ctypes arrays-and-pointers6686767
Ref: 23496686767
Ref: library/ctypes ctypes-arrays-pointers6686767
Ref: 234a6686767
Ref: library/ctypes ctypes Array6686830
Ref: 10116686830
Ref: library/ctypes ctypes Array _length_6687341
Ref: 234b6687341
Ref: library/ctypes ctypes Array _type_6687566
Ref: 234c6687566
Ref: library/ctypes ctypes _Pointer6687761
Ref: 234d6687761
Ref: library/ctypes ctypes _Pointer _type_6688420
Ref: 234e6688420
Ref: library/ctypes ctypes _Pointer contents6688487
Ref: 22ee6688487
Node: Concurrent Execution6688674
Ref: library/concurrency doc6688862
Ref: 234f6688862
Ref: library/concurrency concurrency6688862
Ref: 23506688862
Ref: library/concurrency concurrent-execution6688862
Ref: 23516688862
Node: threading --- Thread-based parallelism6690337
Ref: library/threading doc6690486
Ref: 23526690486
Ref: library/threading module-threading6690486
Ref: 10a6690486
Ref: library/threading threading-thread-based-parallelism6690486
Ref: 23536690486
Ref: library/threading threading active_count6691700
Ref: 23546691700
Ref: library/threading threading current_thread6691911
Ref: 23566691911
Ref: library/threading threading excepthook6692227
Ref: 2326692227
Ref: library/threading threading get_ident6693556
Ref: ab46693556
Ref: library/threading threading get_native_id6693946
Ref: 2346693946
Ref: library/threading threading enumerate6694403
Ref: 23556694403
Ref: library/threading threading main_thread6694720
Ref: 8f46694720
Ref: library/threading threading settrace6694941
Ref: 23576694941
Ref: library/threading threading setprofile6695206
Ref: 23586695206
Ref: library/threading threading stack_size6695477
Ref: 23596695477
Ref: library/threading threading TIMEOUT_MAX6696770
Ref: 235a6696770
Ref: threading --- Thread-based parallelism-Footnote-16698125
Node: Thread-Local Data6698193
Ref: library/threading thread-local-data6698308
Ref: 235c6698308
Ref: library/threading threading local6698660
Ref: 22f86698660
Node: Thread Objects6698857
Ref: library/threading id16698993
Ref: 235d6698993
Ref: library/threading thread-objects6698993
Ref: 235e6698993
Ref: library/threading threading Thread6701659
Ref: 2366701659
Ref: library/threading threading Thread start6702881
Ref: 20db6702881
Ref: library/threading threading Thread run6703264
Ref: 2336703264
Ref: library/threading threading Thread join6703682
Ref: b656703682
Ref: library/threading threading Thread name6704968
Ref: 23606704968
Ref: library/threading threading Thread getName6705183
Ref: 23626705183
Ref: library/threading threading Thread setName6705217
Ref: 23636705217
Ref: library/threading threading Thread ident6705357
Ref: 201e6705357
Ref: library/threading threading Thread native_id6705745
Ref: 2356705745
Ref: library/threading threading Thread is_alive6706602
Ref: 235f6706602
Ref: library/threading threading Thread daemon6706946
Ref: 23616706946
Ref: library/threading threading Thread isDaemon6707526
Ref: 23646707526
Ref: library/threading threading Thread setDaemon6707561
Ref: 23656707561
Node: Lock Objects6707705
Ref: library/threading id26707837
Ref: 23666707837
Ref: library/threading lock-objects6707837
Ref: 23676707837
Ref: library/threading threading Lock6709246
Ref: 236a6709246
Ref: library/threading threading Lock acquire6709649
Ref: 7716709649
Ref: library/threading threading Lock release6710968
Ref: 23686710968
Ref: library/threading threading Lock locked6711459
Ref: 236b6711459
Node: RLock Objects6711541
Ref: library/threading id36711676
Ref: 236c6711676
Ref: library/threading rlock-objects6711676
Ref: 236d6711676
Ref: library/threading threading RLock6712578
Ref: bf46712578
Ref: library/threading threading RLock acquire6713101
Ref: 7726713101
Ref: library/threading threading RLock release6714625
Ref: 236e6714625
Node: Condition Objects6715324
Ref: library/threading condition-objects6715464
Ref: 236f6715464
Ref: library/threading id46715464
Ref: 23706715464
Ref: library/threading threading Condition6718589
Ref: aaf6718589
Ref: library/threading threading Condition acquire6719124
Ref: 23716719124
Ref: library/threading threading Condition release6719342
Ref: 23726719342
Ref: library/threading threading Condition wait6719531
Ref: 235b6719531
Ref: library/threading threading Condition wait_for6721049
Ref: 23756721049
Ref: library/threading threading Condition notify6722025
Ref: 23736722025
Ref: library/threading threading Condition notify_all6722933
Ref: 23746722933
Node: Semaphore Objects6723278
Ref: library/threading id56723418
Ref: 23766723418
Ref: library/threading semaphore-objects6723418
Ref: 23776723418
Ref: library/threading threading Semaphore6724114
Ref: ab06724114
Ref: library/threading threading Semaphore acquire6724795
Ref: bf16724795
Ref: library/threading threading Semaphore release6726081
Ref: 23786726081
Ref: library/threading threading BoundedSemaphore6726328
Ref: ab16726328
Node: Semaphore Example6726883
Ref: library/threading semaphore-example6726954
Ref: 23796726954
Ref: library/threading semaphore-examples6726954
Ref: 237a6726954
Node: Event Objects6727823
Ref: library/threading event-objects6727959
Ref: 237b6727959
Ref: library/threading id66727959
Ref: 237c6727959
Ref: library/threading threading Event6728360
Ref: ab26728360
Ref: library/threading threading Event is_set6728742
Ref: 237f6728742
Ref: library/threading threading Event set6728847
Ref: 237d6728847
Ref: library/threading threading Event clear6729080
Ref: 237e6729080
Ref: library/threading threading Event wait6729314
Ref: cbc6729314
Node: Timer Objects6730176
Ref: library/threading id76730310
Ref: 23806730310
Ref: library/threading timer-objects6730310
Ref: 23816730310
Ref: library/threading threading Timer6731059
Ref: ab36731059
Ref: library/threading threading Timer cancel6731500
Ref: 23826731500
Node: Barrier Objects6731696
Ref: library/threading barrier-objects6731876
Ref: 23836731876
Ref: library/threading threading Barrier6732829
Ref: b646732829
Ref: library/threading threading Barrier wait6733174
Ref: 23846733174
Ref: library/threading threading Barrier reset6734327
Ref: 23856734327
Ref: library/threading threading Barrier abort6734769
Ref: 23866734769
Ref: library/threading threading Barrier parties6735264
Ref: 23876735264
Ref: library/threading threading Barrier n_waiting6735353
Ref: 23886735353
Ref: library/threading threading Barrier broken6735448
Ref: 23896735448
Ref: library/threading threading BrokenBarrierError6735562
Ref: b666735562
Node: Using locks conditions and semaphores in the with statement6735736
Ref: library/threading using-locks-conditions-and-semaphores-in-the-with-statement6735894
Ref: 238a6735894
Ref: library/threading with-locks6735894
Ref: 23696735894
Node: multiprocessing --- Process-based parallelism6736739
Ref: library/multiprocessing doc6736988
Ref: 238b6736988
Ref: library/multiprocessing module-multiprocessing6736988
Ref: b86736988
Ref: library/multiprocessing multiprocessing-process-based-parallelism6736988
Ref: 238c6736988
Ref: multiprocessing --- Process-based parallelism-Footnote-16737343
Node: 簡介<8>6737415
Ref: library/multiprocessing introduction6737524
Ref: 238d6737524
Node: The Process class6739043
Ref: library/multiprocessing the-process-class6739141
Ref: 238e6739141
Node: Contexts and start methods6740322
Ref: library/multiprocessing contexts-and-start-methods6740465
Ref: 23916740465
Ref: library/multiprocessing multiprocessing-start-methods6740538
Ref: 87b6740538
Ref: Contexts and start methods-Footnote-16744989
Node: Exchanging objects between processes6745032
Ref: library/multiprocessing exchanging-objects-between-processes6745191
Ref: 23946745191
Node: Synchronization between processes6746909
Ref: library/multiprocessing synchronization-between-processes6747073
Ref: 23976747073
Node: Sharing state between processes6747794
Ref: library/multiprocessing sharing-state-between-processes6747945
Ref: 23986747945
Node: Using a pool of workers6751030
Ref: library/multiprocessing using-a-pool-of-workers6751139
Ref: 23a36751139
Node: Reference6754258
Ref: library/multiprocessing reference6754398
Ref: 23a46754398
Node: Process and exceptions6754927
Ref: library/multiprocessing process-and-exceptions6755020
Ref: 23a56755020
Ref: library/multiprocessing multiprocessing Process6755093
Ref: 3b76755093
Ref: library/multiprocessing multiprocessing Process run6756454
Ref: 23926756454
Ref: library/multiprocessing multiprocessing Process start6756872
Ref: 238f6756872
Ref: library/multiprocessing multiprocessing Process join6757127
Ref: 23a86757127
Ref: library/multiprocessing multiprocessing Process name6757855
Ref: 23a66757855
Ref: library/multiprocessing multiprocessing Process is_alive6758317
Ref: 23aa6758317
Ref: library/multiprocessing multiprocessing Process daemon6758559
Ref: 23a76758559
Ref: library/multiprocessing multiprocessing Process pid6759437
Ref: 23ab6759437
Ref: library/multiprocessing multiprocessing Process exitcode6759559
Ref: 23a96759559
Ref: library/multiprocessing multiprocessing Process authkey6759784
Ref: 23ac6759784
Ref: library/multiprocessing multiprocessing Process sentinel6760309
Ref: a2a6760309
Ref: library/multiprocessing multiprocessing Process terminate6760937
Ref: 23ae6760937
Ref: library/multiprocessing multiprocessing Process kill6761744
Ref: 3b66761744
Ref: library/multiprocessing multiprocessing Process close6761903
Ref: 3b56761903
Ref: library/multiprocessing multiprocessing ProcessError6763145
Ref: 23af6763145
Ref: library/multiprocessing multiprocessing BufferTooShort6763254
Ref: 23b06763254
Ref: library/multiprocessing multiprocessing AuthenticationError6763560
Ref: 23b16763560
Ref: library/multiprocessing multiprocessing TimeoutError6763661
Ref: 23b26763661
Node: Pipes and Queues6763768
Ref: library/multiprocessing pipes-and-queues6763886
Ref: 23b36763886
Ref: library/multiprocessing multiprocessing Pipe6767311
Ref: 23966767311
Ref: library/multiprocessing multiprocessing Queue6767731
Ref: 23956767731
Ref: library/multiprocessing multiprocessing Queue qsize6768330
Ref: 23c16768330
Ref: library/multiprocessing multiprocessing Queue empty6768686
Ref: 23bc6768686
Ref: library/multiprocessing multiprocessing Queue full6768889
Ref: 23c26768889
Ref: library/multiprocessing multiprocessing Queue put6769090
Ref: 10316769090
Ref: library/multiprocessing multiprocessing Queue put_nowait6769905
Ref: 23c36769905
Ref: library/multiprocessing multiprocessing Queue get6769994
Ref: 10326769994
Ref: library/multiprocessing multiprocessing Queue get_nowait6770779
Ref: 23bd6770779
Ref: library/multiprocessing multiprocessing Queue close6771031
Ref: 23c46771031
Ref: library/multiprocessing multiprocessing Queue join_thread6771333
Ref: 23c56771333
Ref: library/multiprocessing multiprocessing Queue cancel_join_thread6771890
Ref: 23be6771890
Ref: library/multiprocessing multiprocessing SimpleQueue6773043
Ref: 23b46773043
Ref: library/multiprocessing multiprocessing SimpleQueue empty6773180
Ref: 23c66773180
Ref: library/multiprocessing multiprocessing SimpleQueue get6773288
Ref: 23c76773288
Ref: library/multiprocessing multiprocessing SimpleQueue put6773372
Ref: 23c86773372
Ref: library/multiprocessing multiprocessing JoinableQueue6773445
Ref: 23b56773445
Ref: library/multiprocessing multiprocessing JoinableQueue task_done6773666
Ref: 23b86773666
Ref: library/multiprocessing multiprocessing JoinableQueue join6774360
Ref: 23c96774360
Ref: Pipes and Queues-Footnote-16774870
Node: Miscellaneous<3>6774912
Ref: library/multiprocessing miscellaneous6775029
Ref: 23ca6775029
Ref: library/multiprocessing multiprocessing active_children6775078
Ref: 23cb6775078
Ref: library/multiprocessing multiprocessing cpu_count6775289
Ref: 8856775289
Ref: library/multiprocessing multiprocessing current_process6775667
Ref: 23cc6775667
Ref: library/multiprocessing multiprocessing parent_process6775863
Ref: 23cd6775863
Ref: library/multiprocessing multiprocessing freeze_support6776126
Ref: 23ce6776126
Ref: library/multiprocessing multiprocessing get_all_start_methods6777160
Ref: 87c6777160
Ref: library/multiprocessing multiprocessing get_context6777574
Ref: 87f6777574
Ref: library/multiprocessing multiprocessing get_start_method6778004
Ref: 87d6778004
Ref: library/multiprocessing multiprocessing set_executable6778601
Ref: 23cf6778601
Ref: library/multiprocessing multiprocessing set_start_method6779054
Ref: 87e6779054
Node: Connection Objects<2>6779716
Ref: library/multiprocessing connection-objects6779843
Ref: 23d06779843
Ref: library/multiprocessing multiprocessing connection Connection6780162
Ref: 23c06780162
Ref: library/multiprocessing multiprocessing connection Connection send6780213
Ref: 23d26780213
Ref: library/multiprocessing multiprocessing connection Connection recv6780546
Ref: 23d36780546
Ref: library/multiprocessing multiprocessing connection Connection fileno6780844
Ref: 23d46780844
Ref: library/multiprocessing multiprocessing connection Connection close6780950
Ref: 23d56780950
Ref: library/multiprocessing multiprocessing connection Connection poll6781108
Ref: 23d66781108
Ref: library/multiprocessing multiprocessing connection Connection send_bytes6781600
Ref: 23d76781600
Ref: library/multiprocessing multiprocessing connection Connection recv_bytes6782065
Ref: 23d86782065
Ref: library/multiprocessing multiprocessing connection Connection recv_bytes_into6782702
Ref: 23d96782702
Node: Synchronization primitives6785210
Ref: library/multiprocessing synchronization-primitives6785342
Ref: 23da6785342
Ref: library/multiprocessing multiprocessing Barrier6785713
Ref: 23a26785713
Ref: library/multiprocessing multiprocessing BoundedSemaphore6785870
Ref: 239f6785870
Ref: library/multiprocessing multiprocessing Condition6786374
Ref: 23a06786374
Ref: library/multiprocessing multiprocessing Event6786695
Ref: 23a16786695
Ref: library/multiprocessing multiprocessing Lock6786775
Ref: 239c6786775
Ref: library/multiprocessing multiprocessing Lock acquire6787619
Ref: 23db6787619
Ref: library/multiprocessing multiprocessing Lock release6789151
Ref: 23dc6789151
Ref: library/multiprocessing multiprocessing RLock6789526
Ref: 239d6789526
Ref: library/multiprocessing multiprocessing RLock acquire6790258
Ref: 23dd6790258
Ref: library/multiprocessing multiprocessing RLock release6791913
Ref: 23de6791913
Ref: library/multiprocessing multiprocessing Semaphore6792897
Ref: 239e6792897
Ref: Synchronization primitives-Footnote-16794329
Node: Shared ctypes Objects6794371
Ref: library/multiprocessing shared-ctypes-objects6794490
Ref: 23df6794490
Ref: library/multiprocessing multiprocessing Value6794667
Ref: 23996794667
Ref: library/multiprocessing multiprocessing Array6796090
Ref: 239a6796090
Node: The multiprocessing sharedctypes module6797527
Ref: library/multiprocessing module-multiprocessing sharedctypes6797624
Ref: be6797624
Ref: library/multiprocessing the-multiprocessing-sharedctypes-module6797624
Ref: 23e06797624
Ref: library/multiprocessing multiprocessing sharedctypes RawArray6798257
Ref: 23e16798257
Ref: library/multiprocessing multiprocessing sharedctypes RawValue6799084
Ref: 23e36799084
Ref: library/multiprocessing multiprocessing sharedctypes Array6799866
Ref: 23e26799866
Ref: library/multiprocessing multiprocessing sharedctypes Value6800627
Ref: 23e46800627
Ref: library/multiprocessing multiprocessing sharedctypes copy6801372
Ref: 23e56801372
Ref: library/multiprocessing multiprocessing sharedctypes synchronized6801532
Ref: 71e6801532
Node: Managers6804537
Ref: library/multiprocessing managers6804643
Ref: 23e66804643
Ref: library/multiprocessing multiprocessing-managers6804643
Ref: 23b96804643
Ref: library/multiprocessing multiprocessing sharedctypes multiprocessing Manager6804993
Ref: 23e76804993
Ref: library/multiprocessing module-multiprocessing managers6805311
Ref: bb6805311
Ref: library/multiprocessing multiprocessing managers BaseManager6805501
Ref: 23e96805501
Ref: library/multiprocessing multiprocessing managers BaseManager start6806221
Ref: 23ea6806221
Ref: library/multiprocessing multiprocessing managers BaseManager get_server6806462
Ref: 23eb6806462
Ref: library/multiprocessing multiprocessing managers BaseManager connect6807012
Ref: 23ed6807012
Ref: library/multiprocessing multiprocessing managers BaseManager shutdown6807299
Ref: 23ee6807299
Ref: library/multiprocessing multiprocessing managers BaseManager register6807541
Ref: 23ef6807541
Ref: library/multiprocessing multiprocessing managers BaseManager address6809851
Ref: 23ec6809851
Ref: library/multiprocessing multiprocessing managers SyncManager6810370
Ref: 23e86810370
Ref: library/multiprocessing multiprocessing managers SyncManager Barrier6810806
Ref: 23f26810806
Ref: library/multiprocessing multiprocessing managers SyncManager BoundedSemaphore6810999
Ref: 23f36810999
Ref: library/multiprocessing multiprocessing managers SyncManager Condition6811160
Ref: 23f46811160
Ref: library/multiprocessing multiprocessing managers SyncManager Event6811520
Ref: 23f56811520
Ref: library/multiprocessing multiprocessing managers SyncManager Lock6811652
Ref: 23f66811652
Ref: library/multiprocessing multiprocessing managers SyncManager Namespace6811783
Ref: 23f76811783
Ref: library/multiprocessing multiprocessing managers SyncManager Queue6811914
Ref: 23f86811914
Ref: library/multiprocessing multiprocessing managers SyncManager RLock6812051
Ref: 23f96812051
Ref: library/multiprocessing multiprocessing managers SyncManager Semaphore6812183
Ref: 23fa6812183
Ref: library/multiprocessing multiprocessing managers SyncManager Array6812330
Ref: 23fb6812330
Ref: library/multiprocessing multiprocessing managers SyncManager Value6812435
Ref: 23fc6812435
Ref: library/multiprocessing multiprocessing managers SyncManager dict6812586
Ref: 23fd6812586
Ref: library/multiprocessing multiprocessing managers SyncManager list6812785
Ref: 23fe6812785
Ref: library/multiprocessing multiprocessing managers Namespace6813195
Ref: 239b6813195
Node: Customized managers6813977
Ref: library/multiprocessing customized-managers6814072
Ref: 23ff6814072
Node: Using a remote manager6814844
Ref: library/multiprocessing using-a-remote-manager6814939
Ref: 24006814939
Node: Proxy Objects6817080
Ref: library/multiprocessing multiprocessing-proxy-objects6817178
Ref: 56a6817178
Ref: library/multiprocessing proxy-objects6817178
Ref: 24016817178
Ref: library/multiprocessing multiprocessing managers BaseProxy6820439
Ref: 23f06820439
Ref: library/multiprocessing multiprocessing managers BaseProxy _callmethod6820561
Ref: 23f16820561
Ref: library/multiprocessing multiprocessing managers BaseProxy _getvalue6822148
Ref: 24026822148
Ref: library/multiprocessing multiprocessing managers BaseProxy __repr__6822314
Ref: 24036822314
Ref: library/multiprocessing multiprocessing managers BaseProxy __str__6822406
Ref: 24046822406
Node: Cleanup6822517
Ref: library/multiprocessing cleanup6822574
Ref: 24056822574
Node: Process Pools6822863
Ref: library/multiprocessing module-multiprocessing pool6822974
Ref: bc6822974
Ref: library/multiprocessing process-pools6822974
Ref: 24066822974
Ref: library/multiprocessing multiprocessing pool Pool6823135
Ref: 8806823135
Ref: library/multiprocessing multiprocessing pool Pool apply6825741
Ref: 24096825741
Ref: library/multiprocessing multiprocessing pool Pool apply_async6826118
Ref: 240a6826118
Ref: library/multiprocessing multiprocessing pool Pool map6826976
Ref: a2e6826976
Ref: library/multiprocessing multiprocessing pool Pool map_async6827766
Ref: a2f6827766
Ref: library/multiprocessing multiprocessing pool Pool imap6828626
Ref: 240c6828626
Ref: library/multiprocessing multiprocessing pool Pool imap_unordered6829342
Ref: 240d6829342
Ref: library/multiprocessing multiprocessing pool Pool starmap6829670
Ref: a2b6829670
Ref: library/multiprocessing multiprocessing pool Pool starmap_async6830026
Ref: a2c6830026
Ref: library/multiprocessing multiprocessing pool Pool close6830381
Ref: 24076830381
Ref: library/multiprocessing multiprocessing pool Pool terminate6830574
Ref: 24086830574
Ref: library/multiprocessing multiprocessing pool Pool join6830814
Ref: 240e6830814
Ref: library/multiprocessing multiprocessing pool AsyncResult6831262
Ref: 240b6831262
Ref: library/multiprocessing multiprocessing pool AsyncResult get6831420
Ref: 240f6831420
Ref: library/multiprocessing multiprocessing pool AsyncResult wait6831791
Ref: 24106831791
Ref: library/multiprocessing multiprocessing pool AsyncResult ready6831921
Ref: 24116831921
Ref: library/multiprocessing multiprocessing pool AsyncResult successful6832004
Ref: 24126832004
Node: Listeners and Clients6833285
Ref: library/multiprocessing listeners-and-clients6833402
Ref: 24136833402
Ref: library/multiprocessing module-multiprocessing connection6833402
Ref: b96833402
Ref: library/multiprocessing multiprocessing-listeners-clients6833402
Ref: 23d16833402
Ref: library/multiprocessing multiprocessing connection deliver_challenge6833938
Ref: 24146833938
Ref: library/multiprocessing multiprocessing connection answer_challenge6834342
Ref: 24156834342
Ref: library/multiprocessing multiprocessing connection Client6834654
Ref: 24166834654
Ref: library/multiprocessing multiprocessing connection Listener6835406
Ref: 24186835406
Ref: library/multiprocessing multiprocessing connection Listener accept6837169
Ref: 24196837169
Ref: library/multiprocessing multiprocessing connection Listener close6837457
Ref: 241a6837457
Ref: library/multiprocessing multiprocessing connection Listener address6837763
Ref: 241b6837763
Ref: library/multiprocessing multiprocessing connection Listener last_accepted6837856
Ref: 241c6837856
Ref: library/multiprocessing multiprocessing connection wait6838267
Ref: a296838267
Node: Address Formats6842293
Ref: library/multiprocessing address-formats6842366
Ref: 241d6842366
Ref: library/multiprocessing multiprocessing-address-formats6842366
Ref: 24176842366
Node: Authentication keys6843087
Ref: library/multiprocessing authentication-keys6843201
Ref: 241e6843201
Ref: library/multiprocessing multiprocessing-auth-keys6843201
Ref: 23ad6843201
Node: Logging<2>6844385
Ref: library/multiprocessing logging6844510
Ref: 241f6844510
Ref: library/multiprocessing multiprocessing get_logger6844778
Ref: 24206844778
Ref: library/multiprocessing multiprocessing log_to_stderr6845288
Ref: 24216845288
Node: The multiprocessing dummy module6846297
Ref: library/multiprocessing module-multiprocessing dummy6846394
Ref: ba6846394
Ref: library/multiprocessing the-multiprocessing-dummy-module6846394
Ref: 24226846394
Ref: library/multiprocessing multiprocessing pool ThreadPool6846918
Ref: ed26846918
Node: Programming guidelines6848754
Ref: library/multiprocessing multiprocessing-programming6848897
Ref: 23906848897
Ref: library/multiprocessing programming-guidelines6848897
Ref: 24236848897
Node: All start methods6849145
Ref: library/multiprocessing all-start-methods6849268
Ref: 24246849268
Ref: All start methods-Footnote-16855352
Ref: All start methods-Footnote-26855394
Ref: All start methods-Footnote-36855436
Node: The spawn and forkserver start methods6855478
Ref: library/multiprocessing the-spawn-and-forkserver-start-methods6855601
Ref: 24256855601
Node: Examples<10>6857674
Ref: library/multiprocessing examples6857799
Ref: 24266857799
Ref: library/multiprocessing multiprocessing-examples6857799
Ref: 23bf6857799
Node: multiprocessing shared_memory --- Provides shared memory for direct access across processes6866710
Ref: library/multiprocessing shared_memory doc6866943
Ref: 24276866943
Ref: library/multiprocessing shared_memory module-multiprocessing shared_memory6866943
Ref: bd6866943
Ref: library/multiprocessing shared_memory multiprocessing-shared-memory-provides-shared-memory-for-direct-access-across-processes6866943
Ref: 24286866943
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory6868499
Ref: 23936868499
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory close6870175
Ref: 24296870175
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory unlink6870537
Ref: 242a6870537
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory buf6871323
Ref: 242b6871323
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory name6871409
Ref: 242c6871409
Ref: library/multiprocessing shared_memory multiprocessing shared_memory SharedMemory size6871517
Ref: 242d6871517
Ref: library/multiprocessing shared_memory multiprocessing managers SharedMemoryManager6874604
Ref: 242e6874604
Ref: library/multiprocessing shared_memory multiprocessing managers SharedMemoryManager SharedMemory6876020
Ref: 242f6876020
Ref: library/multiprocessing shared_memory multiprocessing managers SharedMemoryManager ShareableList6876182
Ref: 24306876182
Ref: library/multiprocessing shared_memory multiprocessing shared_memory ShareableList6878034
Ref: 24316878034
Ref: library/multiprocessing shared_memory multiprocessing shared_memory ShareableList count6879210
Ref: 24326879210
Ref: library/multiprocessing shared_memory multiprocessing shared_memory ShareableList index6879309
Ref: 24336879309
Ref: library/multiprocessing shared_memory multiprocessing shared_memory ShareableList format6879475
Ref: 24346879475
Ref: library/multiprocessing shared_memory multiprocessing shared_memory ShareableList shm6879626
Ref: 24356879626
Ref: multiprocessing shared_memory --- Provides shared memory for direct access across processes-Footnote-16881299
Ref: multiprocessing shared_memory --- Provides shared memory for direct access across processes-Footnote-26881388
Node: The concurrent package6881419
Ref: library/concurrent doc6881654
Ref: 24366881654
Ref: library/concurrent the-concurrent-package6881654
Ref: 24376881654
Node: concurrent futures --- Launching parallel tasks6881842
Ref: library/concurrent futures doc6882022
Ref: 24386882022
Ref: library/concurrent futures concurrent-futures-launching-parallel-tasks6882022
Ref: 24396882022
Ref: library/concurrent futures module-concurrent futures6882022
Ref: 226882022
Ref: concurrent futures --- Launching parallel tasks-Footnote-16882864
Ref: concurrent futures --- Launching parallel tasks-Footnote-26882949
Node: Executor Objects6883035
Ref: library/concurrent futures executor-objects6883162
Ref: 243b6883162
Ref: library/concurrent futures concurrent futures Executor6883215
Ref: 243a6883215
Ref: library/concurrent futures concurrent futures Executor submit6883415
Ref: 2a46883415
Ref: library/concurrent futures concurrent futures Executor map6883861
Ref: 6c36883861
Ref: library/concurrent futures concurrent futures Executor shutdown6885519
Ref: b336885519
Node: ThreadPoolExecutor6887190
Ref: library/concurrent futures threadpoolexecutor6887345
Ref: 243d6887345
Ref: library/concurrent futures concurrent futures ThreadPoolExecutor6888413
Ref: 27b6888413
Node: ThreadPoolExecutor Example6890164
Ref: library/concurrent futures id16890245
Ref: 243f6890245
Ref: library/concurrent futures threadpoolexecutor-example6890245
Ref: b346890245
Node: ProcessPoolExecutor6891444
Ref: library/concurrent futures processpoolexecutor6891597
Ref: 24406891597
Ref: library/concurrent futures concurrent futures ProcessPoolExecutor6892331
Ref: 2a56892331
Node: ProcessPoolExecutor Example6894120
Ref: library/concurrent futures id26894203
Ref: 24426894203
Ref: library/concurrent futures processpoolexecutor-example6894203
Ref: b356894203
Node: Future Objects6895109
Ref: library/concurrent futures future-objects6895260
Ref: 24436895260
Ref: library/concurrent futures concurrent futures Future6895469
Ref: b326895469
Ref: library/concurrent futures concurrent futures Future cancel6895709
Ref: 24446895709
Ref: library/concurrent futures concurrent futures Future cancelled6896054
Ref: 24456896054
Ref: library/concurrent futures concurrent futures Future running6896170
Ref: 24466896170
Ref: library/concurrent futures concurrent futures Future done6896324
Ref: 24476896324
Ref: library/concurrent futures concurrent futures Future result6896470
Ref: 24486896470
Ref: library/concurrent futures concurrent futures Future exception6897210
Ref: 24496897210
Ref: library/concurrent futures concurrent futures Future add_done_callback6897955
Ref: 244a6897955
Ref: library/concurrent futures concurrent futures Future set_running_or_notify_cancel6898857
Ref: 244b6898857
Ref: library/concurrent futures concurrent futures Future set_result6899952
Ref: 244d6899952
Ref: library/concurrent futures concurrent futures Future set_exception6900405
Ref: 244e6900405
Node: Module Functions6900893
Ref: library/concurrent futures module-functions6901042
Ref: 24506901042
Ref: library/concurrent futures concurrent futures wait6901095
Ref: 244c6901095
Ref: library/concurrent futures concurrent futures as_completed6902997
Ref: 10f36902997
Ref: Module Functions-Footnote-16904051
Node: Exception classes6904100
Ref: library/concurrent futures exception-classes6904226
Ref: 24516904226
Ref: library/concurrent futures concurrent futures CancelledError6904281
Ref: 1ab6904281
Ref: library/concurrent futures concurrent futures TimeoutError6904369
Ref: 243c6904369
Ref: library/concurrent futures concurrent futures BrokenExecutor6904478
Ref: 24526904478
Ref: library/concurrent futures concurrent futures InvalidStateError6904729
Ref: 244f6904729
Ref: library/concurrent futures concurrent futures thread BrokenThreadPool6904906
Ref: 243e6904906
Ref: library/concurrent futures concurrent futures process BrokenProcessPool6905153
Ref: 24416905153
Node: subprocess --- Subprocess management6905508
Ref: library/subprocess doc6905691
Ref: 24536905691
Ref: library/subprocess module-subprocess6905691
Ref: fa6905691
Ref: library/subprocess subprocess-subprocess-management6905691
Ref: 24546905691
Ref: subprocess --- Subprocess management-Footnote-16906632
Ref: subprocess --- Subprocess management-Footnote-26906701
Node: Using the subprocess Module6906750
Ref: library/subprocess using-the-subprocess-module6906882
Ref: 24556906882
Ref: library/subprocess subprocess run6907350
Ref: 3f26907350
Ref: library/subprocess subprocess CompletedProcess6911112
Ref: 7656911112
Ref: library/subprocess subprocess CompletedProcess args6911246
Ref: 245a6911246
Ref: library/subprocess subprocess CompletedProcess returncode6911365
Ref: 245b6911365
Ref: library/subprocess subprocess CompletedProcess stdout6911636
Ref: 245c6911636
Ref: library/subprocess subprocess CompletedProcess stderr6912064
Ref: 245d6912064
Ref: library/subprocess subprocess CompletedProcess check_returncode6912303
Ref: 245e6912303
Ref: library/subprocess subprocess DEVNULL6912471
Ref: aa56912471
Ref: library/subprocess subprocess PIPE6912713
Ref: 3f36912713
Ref: library/subprocess subprocess STDOUT6912977
Ref: 245f6912977
Ref: library/subprocess subprocess SubprocessError6913184
Ref: 24606913184
Ref: library/subprocess subprocess TimeoutExpired6913308
Ref: 24596913308
Ref: library/subprocess subprocess TimeoutExpired cmd6913464
Ref: 24616913464
Ref: library/subprocess subprocess TimeoutExpired timeout6913547
Ref: 24626913547
Ref: library/subprocess subprocess TimeoutExpired output6913604
Ref: 24636913604
Ref: library/subprocess subprocess TimeoutExpired stdout6913772
Ref: 24646913772
Ref: library/subprocess subprocess TimeoutExpired stderr6913864
Ref: 24656913864
Ref: library/subprocess subprocess CalledProcessError6914093
Ref: cba6914093
Ref: library/subprocess subprocess CalledProcessError returncode6914310
Ref: 24676914310
Ref: library/subprocess subprocess CalledProcessError cmd6914475
Ref: 24686914475
Ref: library/subprocess subprocess CalledProcessError output6914558
Ref: 24696914558
Ref: library/subprocess subprocess CalledProcessError stdout6914726
Ref: 246a6914726
Ref: library/subprocess subprocess CalledProcessError stderr6914818
Ref: 246b6914818
Node: Frequently Used Arguments6915114
Ref: library/subprocess frequently-used-arguments6915229
Ref: 24576915229
Ref: library/subprocess id16915229
Ref: 246c6915229
Node: Popen Constructor6919389
Ref: library/subprocess popen-constructor6919526
Ref: 24716919526
Ref: library/subprocess subprocess Popen6919821
Ref: 2ba6919821
Ref: Popen Constructor-Footnote-16933479
Node: Exceptions<6>6933539
Ref: library/subprocess exceptions6933642
Ref: 24816933642
Node: Security Considerations6934633
Ref: library/subprocess security-considerations6934787
Ref: 24706934787
Ref: Security Considerations-Footnote-16935515
Node: Popen Objects6935585
Ref: library/subprocess popen-objects6935733
Ref: 24826935733
Ref: library/subprocess subprocess Popen poll6935850
Ref: 24836935850
Ref: library/subprocess subprocess Popen wait6936016
Ref: 5976936016
Ref: library/subprocess subprocess Popen communicate6936946
Ref: 24586936946
Ref: library/subprocess subprocess Popen send_signal6938696
Ref: 24846938696
Ref: library/subprocess subprocess Popen terminate6939046
Ref: 24856939046
Ref: library/subprocess subprocess Popen kill6939258
Ref: 24866939258
Ref: library/subprocess subprocess Popen args6939498
Ref: 24876939498
Ref: library/subprocess subprocess Popen stdin6939676
Ref: 246d6939676
Ref: library/subprocess subprocess Popen stdout6940104
Ref: 246e6940104
Ref: library/subprocess subprocess Popen stderr6940604
Ref: 246f6940604
Ref: library/subprocess subprocess Popen pid6941365
Ref: 24886941365
Ref: library/subprocess subprocess Popen returncode6941544
Ref: 24806941544
Node: Windows Popen Helpers6941892
Ref: library/subprocess windows-popen-helpers6942037
Ref: 24896942037
Ref: library/subprocess subprocess STARTUPINFO6942191
Ref: 24736942191
Ref: library/subprocess subprocess STARTUPINFO dwFlags6942602
Ref: 248a6942602
Ref: library/subprocess subprocess STARTUPINFO hStdInput6942913
Ref: 248b6942913
Ref: library/subprocess subprocess STARTUPINFO hStdOutput6943232
Ref: 248d6943232
Ref: library/subprocess subprocess STARTUPINFO hStdError6943540
Ref: 248e6943540
Ref: library/subprocess subprocess STARTUPINFO wShowWindow6943845
Ref: 248f6943845
Ref: library/subprocess subprocess STARTUPINFO lpAttributeList6944334
Ref: 49f6944334
Ref: Windows Popen Helpers-Footnote-16945581
Ref: Windows Popen Helpers-Footnote-26945653
Ref: Windows Popen Helpers-Footnote-36945725
Node: Windows Constants6945814
Ref: library/subprocess windows-constants6945889
Ref: 24926945889
Ref: library/subprocess subprocess STD_INPUT_HANDLE6946011
Ref: 24936946011
Ref: library/subprocess subprocess STD_OUTPUT_HANDLE6946148
Ref: 24946946148
Ref: library/subprocess subprocess STD_ERROR_HANDLE6946296
Ref: 24956946296
Ref: library/subprocess subprocess SW_HIDE6946442
Ref: 24916946442
Ref: library/subprocess subprocess STARTF_USESTDHANDLES6946531
Ref: 248c6946531
Ref: library/subprocess subprocess STARTF_USESHOWWINDOW6946762
Ref: 24906946762
Ref: library/subprocess subprocess CREATE_NEW_CONSOLE6946915
Ref: 24746946915
Ref: library/subprocess subprocess CREATE_NEW_PROCESS_GROUP6947062
Ref: 24756947062
Ref: library/subprocess subprocess ABOVE_NORMAL_PRIORITY_CLASS6947384
Ref: 24766947384
Ref: library/subprocess subprocess BELOW_NORMAL_PRIORITY_CLASS6947586
Ref: 24776947586
Ref: library/subprocess subprocess HIGH_PRIORITY_CLASS6947787
Ref: 24786947787
Ref: library/subprocess subprocess IDLE_PRIORITY_CLASS6947971
Ref: 24796947971
Ref: library/subprocess subprocess NORMAL_PRIORITY_CLASS6948165
Ref: 247a6948165
Ref: library/subprocess subprocess REALTIME_PRIORITY_CLASS6948365
Ref: 247b6948365
Ref: library/subprocess subprocess CREATE_NO_WINDOW6948893
Ref: 247c6948893
Ref: library/subprocess subprocess DETACHED_PROCESS6949073
Ref: 247d6949073
Ref: library/subprocess subprocess CREATE_DEFAULT_ERROR_MODE6949325
Ref: 247e6949325
Ref: library/subprocess subprocess CREATE_BREAKAWAY_FROM_JOB6949723
Ref: 247f6949723
Node: Older high-level API6949918
Ref: library/subprocess call-function-trio6950102
Ref: 24566950102
Ref: library/subprocess older-high-level-api6950102
Ref: 24966950102
Ref: library/subprocess subprocess call6950350
Ref: 3f46950350
Ref: library/subprocess subprocess check_call6951395
Ref: 24666951395
Ref: library/subprocess subprocess check_output6952597
Ref: 8e06952597
Node: Replacing Older Functions with the subprocess Module6954790
Ref: library/subprocess replacing-older-functions-with-the-subprocess-module6954986
Ref: 24976954986
Ref: library/subprocess subprocess-replacements6954986
Ref: aef6954986
Node: Replacing /bin/sh shell command substitution6956143
Ref: library/subprocess replacing-bin-sh-shell-command-substitution6956309
Ref: 24986956309
Node: Replacing shell pipeline6956514
Ref: library/subprocess replacing-shell-pipeline6956708
Ref: 24996956708
Node: Replacing os system6957357
Ref: library/subprocess replacing-os-system6957536
Ref: 249a6957536
Node: Replacing the os spawn family6958174
Ref: library/subprocess replacing-the-os-spawn-family6958367
Ref: 249b6958367
Node: Replacing os popen os popen2 os popen36958998
Ref: library/subprocess replacing-os-popen-os-popen2-os-popen36959214
Ref: 249c6959214
Node: Replacing functions from the popen2 module6960509
Ref: library/subprocess replacing-functions-from-the-popen2-module6960687
Ref: 249d6960687
Node: Legacy Shell Invocation Functions6962003
Ref: library/subprocess legacy-shell-invocation-functions6962185
Ref: 249e6962185
Ref: library/subprocess subprocess getstatusoutput6962549
Ref: 8e16962549
Ref: library/subprocess subprocess getoutput6963717
Ref: 249f6963717
Node: 註解6964153
Ref: library/subprocess notes6964274
Ref: 24a06964274
Node: Converting an argument sequence to a string on Windows6964376
Ref: library/subprocess converting-an-argument-sequence-to-a-string-on-windows6964473
Ref: 24a16964473
Ref: library/subprocess converting-argument-sequence6964473
Ref: 24726964473
Node: sched --- Event scheduler6965632
Ref: library/sched doc6965804
Ref: 24a26965804
Ref: library/sched module-sched6965804
Ref: e46965804
Ref: library/sched sched-event-scheduler6965804
Ref: 24a36965804
Ref: library/sched sched scheduler6966074
Ref: a736966074
Ref: sched --- Event scheduler-Footnote-16967704
Node: Scheduler Objects6967768
Ref: library/sched id16967847
Ref: 24a46967847
Ref: library/sched scheduler-objects6967847
Ref: 24a56967847
Ref: library/sched sched scheduler enterabs6967978
Ref: a756967978
Ref: library/sched sched scheduler enter6968850
Ref: a746968850
Ref: library/sched sched scheduler cancel6969247
Ref: 24a66969247
Ref: library/sched sched scheduler empty6969440
Ref: 24a76969440
Ref: library/sched sched scheduler run6969531
Ref: a726969531
Ref: library/sched sched scheduler queue6970580
Ref: 24a86970580
Node: queue --- A synchronized queue class6970836
Ref: library/queue doc6971005
Ref: 24a96971005
Ref: library/queue module-queue6971005
Ref: db6971005
Ref: library/queue queue-a-synchronized-queue-class6971005
Ref: 24aa6971005
Ref: library/queue queue Queue6972324
Ref: d1d6972324
Ref: library/queue queue LifoQueue6972689
Ref: 24ab6972689
Ref: library/queue queue PriorityQueue6973058
Ref: 24ac6973058
Ref: library/queue queue SimpleQueue6974054
Ref: 3cb6974054
Ref: library/queue queue Empty6974227
Ref: 23ba6974227
Ref: library/queue queue Full6974409
Ref: 23bb6974409
Ref: queue --- A synchronized queue class-Footnote-16974677
Node: Queue Objects6974741
Ref: library/queue queue-objects6974855
Ref: 24b16974855
Ref: library/queue queueobjects6974855
Ref: 24b26974855
Ref: library/queue queue Queue qsize6975034
Ref: 24b36975034
Ref: library/queue queue Queue empty6975269
Ref: 24b46975269
Ref: library/queue queue Queue full6975604
Ref: 24b56975604
Ref: library/queue queue Queue put6975935
Ref: 24af6975935
Ref: library/queue queue Queue put_nowait6976533
Ref: 24b06976533
Ref: library/queue queue Queue get6976620
Ref: 24ad6976620
Ref: library/queue queue Queue get_nowait6977530
Ref: 24ae6977530
Ref: library/queue queue Queue task_done6977729
Ref: 23b66977729
Ref: library/queue queue Queue join6978381
Ref: 23b76978381
Node: SimpleQueue Objects6979436
Ref: library/queue simplequeue-objects6979550
Ref: 24b66979550
Ref: library/queue queue SimpleQueue qsize6979686
Ref: 24b76979686
Ref: library/queue queue SimpleQueue empty6979858
Ref: 24b86979858
Ref: library/queue queue SimpleQueue put6980081
Ref: 24b96980081
Ref: library/queue queue SimpleQueue put_nowait6980852
Ref: 24ba6980852
Ref: library/queue queue SimpleQueue get6981007
Ref: 24bb6981007
Ref: library/queue queue SimpleQueue get_nowait6981595
Ref: 24bc6981595
Node: contextvars --- Context Variables6982048
Ref: library/contextvars doc6982227
Ref: 24bd6982227
Ref: library/contextvars contextvars-context-variables6982227
Ref: 24be6982227
Ref: library/contextvars module-contextvars6982227
Ref: 256982227
Ref: contextvars --- Context Variables-Footnote-16983082
Node: Context Variables6983131
Ref: library/contextvars context-variables6983252
Ref: 24c26983252
Ref: library/contextvars contextvars ContextVar6983307
Ref: 24bf6983307
Ref: library/contextvars contextvars ContextVar name6984015
Ref: 24c46984015
Ref: library/contextvars contextvars ContextVar get6984137
Ref: 24c36984137
Ref: library/contextvars contextvars ContextVar set6984630
Ref: 24c56984630
Ref: library/contextvars contextvars ContextVar reset6985032
Ref: 24c76985032
Ref: library/contextvars contextvars contextvars Token6985559
Ref: 24c66985559
Ref: library/contextvars contextvars contextvars Token Token var6985834
Ref: 24c86985834
Ref: library/contextvars contextvars contextvars Token Token old_value6985975
Ref: 24c96985975
Ref: library/contextvars contextvars contextvars Token Token MISSING6986263
Ref: 24ca6986263
Node: Manual Context Management6986353
Ref: library/contextvars manual-context-management6986498
Ref: 24cb6986498
Ref: library/contextvars contextvars copy_context6986569
Ref: 24c06986569
Ref: library/contextvars contextvars Context6987043
Ref: 24c16987043
Ref: library/contextvars contextvars Context run6987382
Ref: 24cc6987382
Ref: library/contextvars contextvars Context copy6988815
Ref: 24cd6988815
Ref: library/contextvars contextvars Context get6989264
Ref: 24ce6989264
Ref: library/contextvars contextvars Context keys6989712
Ref: 24cf6989712
Ref: library/contextvars contextvars Context values6989809
Ref: 24d06989809
Ref: library/contextvars contextvars Context items6989918
Ref: 24d16989918
Node: asyncio support6990063
Ref: library/contextvars asyncio-support6990182
Ref: 24d26990182
Node: _thread --- Low-level threading API6991757
Ref: library/_thread doc6991960
Ref: 24d36991960
Ref: library/_thread module-_thread6991960
Ref: 36991960
Ref: library/_thread thread-low-level-threading-api6991960
Ref: 24d46991960
Ref: library/_thread _thread error6992668
Ref: 24d56992668
Ref: library/_thread _thread LockType6992824
Ref: 24d66992824
Ref: library/_thread _thread start_new_thread6992892
Ref: fca6992892
Ref: library/_thread _thread interrupt_main6993773
Ref: 24d76993773
Ref: library/_thread _thread exit6994154
Ref: 24db6994154
Ref: library/_thread _thread allocate_lock6994301
Ref: 24dc6994301
Ref: library/_thread _thread get_ident6994447
Ref: 24dd6994447
Ref: library/_thread _thread get_native_id6994811
Ref: 24de6994811
Ref: library/_thread _thread stack_size6995266
Ref: 24df6995266
Ref: library/_thread _thread TIMEOUT_MAX6996507
Ref: 24e06996507
Ref: library/_thread _thread lock acquire6996785
Ref: 24e16996785
Ref: library/_thread _thread lock release6997856
Ref: 24e26997856
Ref: library/_thread _thread lock locked6998004
Ref: 24e36998004
Node: _dummy_thread --- Drop-in replacement for the _thread module6999407
Ref: library/_dummy_thread doc6999641
Ref: 24e46999641
Ref: library/_dummy_thread dummy-thread-drop-in-replacement-for-the-thread-module6999641
Ref: 24e56999641
Ref: library/_dummy_thread module-_dummy_thread6999641
Ref: 26999641
Ref: _dummy_thread --- Drop-in replacement for the _thread module-Footnote-17000430
Node: dummy_threading --- Drop-in replacement for the threading module7000502
Ref: library/dummy_threading doc7000692
Ref: 24e67000692
Ref: library/dummy_threading dummy-threading-drop-in-replacement-for-the-threading-module7000692
Ref: 24e77000692
Ref: library/dummy_threading module-dummy_threading7000692
Ref: 687000692
Ref: dummy_threading --- Drop-in replacement for the threading module-Footnote-17001463
Node: Networking and Interprocess Communication7001537
Ref: library/ipc doc7001714
Ref: 24e87001714
Ref: library/ipc ipc7001714
Ref: 24e97001714
Ref: library/ipc networking-and-interprocess-communication7001714
Ref: 24ea7001714
Node: asyncio --- Asynchronous I/O7002959
Ref: library/asyncio doc7003115
Ref: 24eb7003115
Ref: library/asyncio asyncio-asynchronous-i-o7003115
Ref: 24ec7003115
Ref: library/asyncio module-asyncio7003115
Ref: a7003115
Node: Coroutines and Tasks7004919
Ref: library/asyncio-task doc7005020
Ref: 24f67005020
Ref: library/asyncio-task coroutines-and-tasks7005020
Ref: 24f77005020
Node: Coroutines<3>7005478
Ref: library/asyncio-task coroutine7005567
Ref: 24ed7005567
Ref: library/asyncio-task coroutines7005567
Ref: 24f87005567
Node: Awaitables7007972
Ref: library/asyncio-task asyncio-awaitables7008096
Ref: 24f97008096
Ref: library/asyncio-task awaitables7008096
Ref: 24fa7008096
Node: Running an asyncio Program7010726
Ref: library/asyncio-task running-an-asyncio-program7010851
Ref: 24fd7010851
Ref: library/asyncio-task asyncio run7010924
Ref: 1a67010924
Ref: Running an asyncio Program-Footnote-17011866
Node: Creating Tasks7011940
Ref: library/asyncio-task creating-tasks7012063
Ref: 24fe7012063
Ref: library/asyncio-task asyncio create_task7012112
Ref: 1af7012112
Node: Sleeping7013079
Ref: library/asyncio-task sleeping7013202
Ref: 24ff7013202
Ref: library/asyncio-task asyncio sleep7013239
Ref: 2867013239
Ref: library/asyncio-task asyncio-example-sleep7013623
Ref: 25007013623
Node: Running Tasks Concurrently7014128
Ref: library/asyncio-task running-tasks-concurrently7014264
Ref: 25017014264
Ref: library/asyncio-task asyncio gather7014337
Ref: 2877014337
Ref: library/asyncio-task asyncio-example-gather7015727
Ref: 25027015727
Node: Shielding From Cancellation7017376
Ref: library/asyncio-task shielding-from-cancellation7017512
Ref: 25037017512
Ref: library/asyncio-task asyncio shield7017587
Ref: 2887017587
Node: Timeouts7018764
Ref: library/asyncio-task timeouts7018892
Ref: 25057018892
Ref: library/asyncio-task asyncio wait_for7018929
Ref: 2897018929
Ref: library/asyncio-task asyncio-example-waitfor7019780
Ref: 25077019780
Node: Waiting Primitives7020453
Ref: library/asyncio-task waiting-primitives7020583
Ref: 25087020583
Ref: library/asyncio-task asyncio wait7020642
Ref: 28a7020642
Ref: library/asyncio-task asyncio-example-wait-coroutine7022920
Ref: 25097022920
Ref: library/asyncio-task asyncio as_completed7023818
Ref: 28b7023818
Node: Scheduling From Other Threads7024451
Ref: library/asyncio-task scheduling-from-other-threads7024586
Ref: 250a7024586
Ref: library/asyncio-task asyncio run_coroutine_threadsafe7024667
Ref: 51f7024667
Node: Introspection7026096
Ref: library/asyncio-task introspection7026224
Ref: 250c7026224
Ref: library/asyncio-task asyncio current_task7026273
Ref: 3557026273
Ref: library/asyncio-task asyncio all_tasks7026546
Ref: 3567026546
Node: Task Object7026800
Ref: library/asyncio-task task-object7026925
Ref: 250d7026925
Ref: library/asyncio-task asyncio Task7026970
Ref: 1ae7026970
Ref: library/asyncio-task asyncio Task cancel7028964
Ref: 25047028964
Ref: library/asyncio-task asyncio-example-task-cancel7029683
Ref: 25127029683
Ref: library/asyncio-task asyncio Task cancelled7030940
Ref: 250e7030940
Ref: library/asyncio-task asyncio Task done7031256
Ref: 25137031256
Ref: library/asyncio-task asyncio Task result7031478
Ref: 25147031478
Ref: library/asyncio-task asyncio Task exception7031972
Ref: 25167031972
Ref: library/asyncio-task asyncio Task add_done_callback7032465
Ref: 25177032465
Ref: library/asyncio-task asyncio Task remove_done_callback7032786
Ref: 25187032786
Ref: library/asyncio-task asyncio Task get_stack7033090
Ref: 251a7033090
Ref: library/asyncio-task asyncio Task print_stack7034092
Ref: 251b7034092
Ref: library/asyncio-task asyncio Task get_coro7034590
Ref: 1ad7034590
Ref: library/asyncio-task asyncio Task get_name7034726
Ref: 1b27034726
Ref: library/asyncio-task asyncio Task set_name7035002
Ref: 1b17035002
Ref: library/asyncio-task asyncio Task all_tasks7035340
Ref: 3587035340
Ref: library/asyncio-task asyncio Task current_task7035834
Ref: 3577035834
Node: Generator-based Coroutines7036266
Ref: library/asyncio-task asyncio-generator-based-coro7036369
Ref: 24fb7036369
Ref: library/asyncio-task generator-based-coroutines7036369
Ref: 251c7036369
Ref: library/asyncio-task asyncio coroutine7036842
Ref: 2837036842
Ref: library/asyncio-task asyncio iscoroutine7037406
Ref: 251d7037406
Ref: library/asyncio-task asyncio iscoroutinefunction7037650
Ref: 251e7037650
Node: Streams7037965
Ref: library/asyncio-stream doc7038101
Ref: 251f7038101
Ref: library/asyncio-stream asyncio-streams7038101
Ref: 24ee7038101
Ref: library/asyncio-stream streams7038101
Ref: 25207038101
Ref: library/asyncio-stream asyncio-example-stream7038438
Ref: 25217038438
Ref: library/asyncio-stream asyncio open_connection7039184
Ref: 3687039184
Ref: library/asyncio-stream asyncio start_server7040104
Ref: 3697040104
Ref: library/asyncio-stream asyncio open_unix_connection7041396
Ref: 25237041396
Ref: library/asyncio-stream asyncio start_unix_server7042025
Ref: 25257042025
Ref: Streams-Footnote-17042739
Node: StreamReader7042813
Ref: library/asyncio-stream streamreader7042890
Ref: 25267042890
Ref: library/asyncio-stream asyncio StreamReader7042937
Ref: fcf7042937
Ref: library/asyncio-stream asyncio StreamReader read7043221
Ref: 25277043221
Ref: library/asyncio-stream asyncio StreamReader readline7043508
Ref: 25287043508
Ref: library/asyncio-stream asyncio StreamReader readexactly7043866
Ref: 5247043866
Ref: library/asyncio-stream asyncio StreamReader readuntil7044167
Ref: 5237044167
Ref: library/asyncio-stream asyncio StreamReader at_eof7045019
Ref: 252b7045019
Node: StreamWriter7045148
Ref: library/asyncio-stream streamwriter7045246
Ref: 252c7045246
Ref: library/asyncio-stream asyncio StreamWriter7045293
Ref: fd07045293
Ref: library/asyncio-stream asyncio StreamWriter write7045576
Ref: 252d7045576
Ref: library/asyncio-stream asyncio StreamWriter writelines7045952
Ref: 252e7045952
Ref: library/asyncio-stream asyncio StreamWriter close7046351
Ref: 252f7046351
Ref: library/asyncio-stream asyncio StreamWriter can_write_eof7046614
Ref: 25307046614
Ref: library/asyncio-stream asyncio StreamWriter write_eof7046791
Ref: 25317046791
Ref: library/asyncio-stream asyncio StreamWriter transport7046925
Ref: 25327046925
Ref: library/asyncio-stream asyncio StreamWriter get_extra_info7047005
Ref: 25337047005
Ref: library/asyncio-stream asyncio StreamWriter drain7047185
Ref: 25347047185
Ref: library/asyncio-stream asyncio StreamWriter is_closing7047784
Ref: 35c7047784
Ref: library/asyncio-stream asyncio StreamWriter wait_closed7047949
Ref: 35b7047949
Node: Examples<11>7048187
Ref: library/asyncio-stream examples7048264
Ref: 25227048264
Node: TCP echo client using streams7048461
Ref: library/asyncio-stream asyncio-tcp-echo-client-streams7048577
Ref: 25357048577
Ref: library/asyncio-stream tcp-echo-client-using-streams7048577
Ref: 25367048577
Node: TCP echo server using streams7049298
Ref: library/asyncio-stream asyncio-tcp-echo-server-streams7049439
Ref: 25387049439
Ref: library/asyncio-stream tcp-echo-server-using-streams7049439
Ref: 25397049439
Node: Get HTTP headers7050412
Ref: library/asyncio-stream get-http-headers7050578
Ref: 253b7050578
Node: Register an open socket to wait for data using streams7051813
Ref: library/asyncio-stream asyncio-example-create-connection-streams7051941
Ref: 253c7051941
Ref: library/asyncio-stream register-an-open-socket-to-wait-for-data-using-streams7051941
Ref: 253d7051941
Node: Synchronization Primitives7053329
Ref: library/asyncio-sync doc7053457
Ref: 25417053457
Ref: library/asyncio-sync asyncio-sync7053457
Ref: 24f17053457
Ref: library/asyncio-sync synchronization-primitives7053457
Ref: 25427053457
Ref: Synchronization Primitives-Footnote-17054498
Node: Lock7054570
Ref: library/asyncio-sync lock7054651
Ref: 25437054651
Ref: library/asyncio-sync asyncio Lock7054682
Ref: 28c7054682
Ref: library/asyncio-sync asyncio Lock acquire7055395
Ref: 25447055395
Ref: library/asyncio-sync asyncio Lock release7055895
Ref: 25457055895
Ref: library/asyncio-sync asyncio Lock locked7056118
Ref: 25467056118
Node: Event7056206
Ref: library/asyncio-sync event7056305
Ref: 25477056305
Ref: library/asyncio-sync asyncio Event7056338
Ref: 28d7056338
Ref: library/asyncio-sync asyncio-example-sync-event7056918
Ref: 254b7056918
Ref: library/asyncio-sync asyncio Event wait7057547
Ref: 254a7057547
Ref: library/asyncio-sync asyncio Event set7057763
Ref: 25487057763
Ref: library/asyncio-sync asyncio Event clear7057909
Ref: 25497057909
Ref: library/asyncio-sync asyncio Event is_set7058105
Ref: 254c7058105
Node: Condition7058189
Ref: library/asyncio-sync condition7058293
Ref: 254d7058293
Ref: library/asyncio-sync asyncio Condition7058334
Ref: 28e7058334
Ref: library/asyncio-sync asyncio Condition acquire7059616
Ref: 254e7059616
Ref: library/asyncio-sync asyncio Condition notify7059825
Ref: 254f7059825
Ref: library/asyncio-sync asyncio Condition locked7060190
Ref: 25507060190
Ref: library/asyncio-sync asyncio Condition notify_all7060289
Ref: 25517060289
Ref: library/asyncio-sync asyncio Condition release7060673
Ref: 25527060673
Ref: library/asyncio-sync asyncio Condition wait7060841
Ref: 25537060841
Ref: library/asyncio-sync asyncio Condition wait_for7061317
Ref: 25547061317
Node: Semaphore7061577
Ref: library/asyncio-sync semaphore7061692
Ref: 25557061692
Ref: library/asyncio-sync asyncio Semaphore7061733
Ref: 28f7061733
Ref: library/asyncio-sync asyncio Semaphore acquire7062895
Ref: 25567062895
Ref: library/asyncio-sync asyncio Semaphore locked7063189
Ref: 25587063189
Ref: library/asyncio-sync asyncio Semaphore release7063299
Ref: 25577063299
Node: BoundedSemaphore7063619
Ref: library/asyncio-sync boundedsemaphore7063716
Ref: 25597063716
Ref: library/asyncio-sync asyncio BoundedSemaphore7063771
Ref: 2907063771
Node: Subprocesses7064474
Ref: library/asyncio-subprocess doc7064601
Ref: 255a7064601
Ref: library/asyncio-subprocess asyncio-subprocess7064601
Ref: 24ef7064601
Ref: library/asyncio-subprocess subprocesses7064601
Ref: 255b7064601
Ref: library/asyncio-subprocess asyncio-example-subprocess-shell7064889
Ref: 255c7064889
Ref: Subprocesses-Footnote-17066185
Ref: Subprocesses-Footnote-27066263
Node: Creating Subprocesses7066346
Ref: library/asyncio-subprocess creating-subprocesses7066437
Ref: 255e7066437
Ref: library/asyncio-subprocess asyncio create_subprocess_exec7066502
Ref: 2927066502
Ref: library/asyncio-subprocess asyncio create_subprocess_shell7067156
Ref: 2937067156
Ref: Creating Subprocesses-Footnote-17068745
Node: Constants<7>7068815
Ref: library/asyncio-subprocess constants7068944
Ref: 25667068944
Ref: library/asyncio-subprocess asyncio asyncio subprocess PIPE7068985
Ref: 25677068985
Ref: library/asyncio-subprocess asyncio asyncio subprocess STDOUT7069429
Ref: 256b7069429
Ref: library/asyncio-subprocess asyncio asyncio subprocess DEVNULL7069615
Ref: 256c7069615
Node: Interacting with Subprocesses7069896
Ref: library/asyncio-subprocess interacting-with-subprocesses7069995
Ref: 256d7069995
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process7070326
Ref: 255f7070326
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process wait7071305
Ref: 256f7071305
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process communicate7071822
Ref: 256e7071822
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process send_signal7073064
Ref: 25727073064
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process terminate7073464
Ref: 25737073464
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process kill7073759
Ref: 25757073759
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process stdin7074003
Ref: 25687074003
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process stdout7074161
Ref: 25697074161
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process stderr7074322
Ref: 256a7074322
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process pid7074820
Ref: 25767074820
Ref: library/asyncio-subprocess asyncio asyncio subprocess Process returncode7075056
Ref: 25717075056
Node: Subprocess and Threads7075411
Ref: library/asyncio-subprocess asyncio-subprocess-threads7075520
Ref: 25707075520
Ref: library/asyncio-subprocess subprocess-and-threads7075520
Ref: 25777075520
Node: Examples<12>7076380
Ref: library/asyncio-subprocess examples7076489
Ref: 255d7076489
Ref: library/asyncio-subprocess asyncio-example-create-subprocess-exec7076673
Ref: 257b7076673
Node: Queues7077474
Ref: library/asyncio-queue doc7077588
Ref: 257d7077588
Ref: library/asyncio-queue asyncio-queues7077588
Ref: 24f07077588
Ref: library/asyncio-queue queues7077588
Ref: 257e7077588
Ref: Queues-Footnote-17078279
Node: Queue7078352
Ref: library/asyncio-queue queue7078423
Ref: 25807078423
Ref: library/asyncio-queue asyncio Queue7078456
Ref: 2917078456
Ref: library/asyncio-queue asyncio Queue maxsize7079115
Ref: 25837079115
Ref: library/asyncio-queue asyncio Queue empty7079190
Ref: 25847079190
Ref: library/asyncio-queue asyncio Queue full7079298
Ref: 25857079298
Ref: library/asyncio-queue asyncio Queue get7079560
Ref: 25817079560
Ref: library/asyncio-queue asyncio Queue get_nowait7079717
Ref: 25867079717
Ref: library/asyncio-queue asyncio Queue join7079859
Ref: 6a47079859
Ref: library/asyncio-queue asyncio Queue put7080363
Ref: 25887080363
Ref: library/asyncio-queue asyncio Queue put_nowait7080540
Ref: 25897080540
Ref: library/asyncio-queue asyncio Queue qsize7080730
Ref: 25827080730
Ref: library/asyncio-queue asyncio Queue task_done7080815
Ref: 6a57080815
Node: Priority Queue7081504
Ref: library/asyncio-queue priority-queue7081594
Ref: 258b7081594
Ref: library/asyncio-queue asyncio PriorityQueue7081645
Ref: 258c7081645
Node: LIFO Queue7081853
Ref: library/asyncio-queue lifo-queue7081951
Ref: 258d7081951
Ref: library/asyncio-queue asyncio LifoQueue7081994
Ref: 258e7081994
Node: Exceptions<7>7082138
Ref: library/asyncio-queue exceptions7082234
Ref: 258f7082234
Ref: library/asyncio-queue asyncio QueueEmpty7082277
Ref: 25877082277
Ref: library/asyncio-queue asyncio QueueFull7082416
Ref: 258a7082416
Node: Examples<13>7082570
Ref: library/asyncio-queue examples7082647
Ref: 257f7082647
Ref: library/asyncio-queue asyncio-example-queue-dist7082686
Ref: 25907082686
Node: Exceptions<8>7084444
Ref: library/asyncio-exceptions doc7084556
Ref: 25917084556
Ref: library/asyncio-exceptions asyncio-exceptions7084556
Ref: 25927084556
Ref: library/asyncio-exceptions exceptions7084556
Ref: 25937084556
Ref: library/asyncio-exceptions asyncio TimeoutError7084712
Ref: 25067084712
Ref: library/asyncio-exceptions asyncio CancelledError7084909
Ref: 1a87084909
Ref: library/asyncio-exceptions asyncio InvalidStateError7085252
Ref: 25157085252
Ref: library/asyncio-exceptions asyncio SendfileNotAvailableError7085488
Ref: 25947085488
Ref: library/asyncio-exceptions asyncio IncompleteReadError7085666
Ref: ede7085666
Ref: library/asyncio-exceptions asyncio IncompleteReadError expected7085878
Ref: 25957085878
Ref: library/asyncio-exceptions asyncio IncompleteReadError partial7085970
Ref: 25297085970
Ref: library/asyncio-exceptions asyncio LimitOverrunError7086090
Ref: 252a7086090
Ref: library/asyncio-exceptions asyncio LimitOverrunError consumed7086249
Ref: 25967086249
Ref: Exceptions<8>-Footnote-17086365
Node: Event Loop7086443
Ref: library/asyncio-eventloop doc7086556
Ref: 25977086556
Ref: library/asyncio-eventloop event-loop7086556
Ref: 25987086556
Ref: library/asyncio-eventloop asyncio get_running_loop7087386
Ref: 3597087386
Ref: library/asyncio-eventloop asyncio get_event_loop7087667
Ref: 35a7087667
Ref: library/asyncio-eventloop asyncio set_event_loop7088385
Ref: 25997088385
Ref: library/asyncio-eventloop asyncio new_event_loop7088496
Ref: 259a7088496
Ref: Event Loop-Footnote-17089763
Ref: Event Loop-Footnote-27089836
Node: Event Loop Methods7089915
Ref: library/asyncio-eventloop asyncio-event-loop7090005
Ref: 6497090005
Ref: library/asyncio-eventloop event-loop-methods7090005
Ref: 259c7090005
Node: Running and stopping the loop7090588
Ref: library/asyncio-eventloop running-and-stopping-the-loop7090701
Ref: 25a27090701
Ref: library/asyncio-eventloop asyncio loop run_until_complete7090782
Ref: 51d7090782
Ref: library/asyncio-eventloop asyncio loop run_forever7091104
Ref: 25a37091104
Ref: library/asyncio-eventloop asyncio loop stop7091830
Ref: 5257091830
Ref: library/asyncio-eventloop asyncio loop is_running7091889
Ref: 25a47091889
Ref: library/asyncio-eventloop asyncio loop is_closed7091991
Ref: 6a07091991
Ref: library/asyncio-eventloop asyncio loop close7092082
Ref: 25a57092082
Ref: library/asyncio-eventloop asyncio loop shutdown_asyncgens7092493
Ref: 5267092493
Node: Scheduling callbacks7093181
Ref: library/asyncio-eventloop scheduling-callbacks7093331
Ref: 25a67093331
Ref: library/asyncio-eventloop asyncio loop call_soon7093394
Ref: 34e7093394
Ref: library/asyncio-eventloop asyncio loop call_soon_threadsafe7094074
Ref: 34f7094074
Ref: library/asyncio-eventloop asyncio-pass-keywords7094461
Ref: 25a87094461
Ref: Scheduling callbacks-Footnote-17094958
Node: Scheduling delayed callbacks7095007
Ref: library/asyncio-eventloop asyncio-delayed-calls7095154
Ref: 25a97095154
Ref: library/asyncio-eventloop scheduling-delayed-callbacks7095154
Ref: 25aa7095154
Ref: library/asyncio-eventloop asyncio loop call_later7095387
Ref: 3507095387
Ref: library/asyncio-eventloop asyncio loop call_at7096547
Ref: 3517096547
Ref: library/asyncio-eventloop asyncio loop time7097290
Ref: 25ab7097290
Ref: Scheduling delayed callbacks-Footnote-17097724
Ref: Scheduling delayed callbacks-Footnote-27097773
Node: Creating Futures and Tasks7097822
Ref: library/asyncio-eventloop creating-futures-and-tasks7097976
Ref: 25ac7097976
Ref: library/asyncio-eventloop asyncio loop create_future7098051
Ref: 5217098051
Ref: library/asyncio-eventloop asyncio loop create_task7098411
Ref: 1b07098411
Ref: library/asyncio-eventloop asyncio loop set_task_factory7098927
Ref: 6a27098927
Ref: library/asyncio-eventloop asyncio loop get_task_factory7099403
Ref: 6a37099403
Node: Opening network connections7099519
Ref: library/asyncio-eventloop opening-network-connections7099669
Ref: 25ad7099669
Ref: library/asyncio-eventloop asyncio loop create_connection7099746
Ref: 1b37099746
Ref: library/asyncio-eventloop asyncio loop create_datagram_endpoint7105536
Ref: 2e87105536
Ref: library/asyncio-eventloop asyncio loop create_unix_connection7108966
Ref: 25247108966
Ref: Opening network connections-Footnote-17109926
Ref: Opening network connections-Footnote-27109975
Node: Creating network servers7110024
Ref: library/asyncio-eventloop creating-network-servers7110166
Ref: 25b77110166
Ref: library/asyncio-eventloop asyncio loop create_server7110237
Ref: 3627110237
Ref: library/asyncio-eventloop asyncio loop create_unix_server7113846
Ref: 3637113846
Ref: library/asyncio-eventloop asyncio loop connect_accepted_socket7114700
Ref: 36a7114700
Node: Transferring files7115732
Ref: library/asyncio-eventloop transferring-files7115858
Ref: 25b87115858
Ref: library/asyncio-eventloop asyncio loop sendfile7115917
Ref: 25b97115917
Node: TLS Upgrade7116979
Ref: library/asyncio-eventloop tls-upgrade7117106
Ref: 25ba7117106
Ref: library/asyncio-eventloop asyncio loop start_tls7117151
Ref: 3537117151
Node: Watching file descriptors7118379
Ref: library/asyncio-eventloop watching-file-descriptors7118524
Ref: 25bb7118524
Ref: library/asyncio-eventloop asyncio loop add_reader7118597
Ref: 25407118597
Ref: library/asyncio-eventloop asyncio loop remove_reader7118821
Ref: 25bc7118821
Ref: library/asyncio-eventloop asyncio loop add_writer7118934
Ref: 25bd7118934
Ref: library/asyncio-eventloop asyncio loop remove_writer7119260
Ref: 25be7119260
Node: Working with socket objects directly7119461
Ref: library/asyncio-eventloop working-with-socket-objects-directly7119598
Ref: 25c07119598
Ref: library/asyncio-eventloop asyncio loop sock_recv7120049
Ref: 4a37120049
Ref: library/asyncio-eventloop asyncio loop sock_recv_into7120510
Ref: 3547120510
Ref: library/asyncio-eventloop asyncio loop sock_sendall7120821
Ref: 4a47120821
Ref: library/asyncio-eventloop asyncio loop sock_connect7121570
Ref: 6a67121570
Ref: library/asyncio-eventloop asyncio loop sock_accept7122187
Ref: 4a57122187
Ref: library/asyncio-eventloop asyncio loop sock_sendfile7123002
Ref: 35d7123002
Node: DNS7124207
Ref: library/asyncio-eventloop dns7124337
Ref: 25c17124337
Ref: library/asyncio-eventloop asyncio loop getaddrinfo7124366
Ref: 4a67124366
Ref: library/asyncio-eventloop asyncio loop getnameinfo7124538
Ref: 4a77124538
Node: Working with pipes7124920
Ref: library/asyncio-eventloop working-with-pipes7125026
Ref: 25c47125026
Ref: library/asyncio-eventloop asyncio loop connect_read_pipe7125085
Ref: 25627125085
Ref: library/asyncio-eventloop asyncio loop connect_write_pipe7125666
Ref: 25637125666
Node: Unix signals7126511
Ref: library/asyncio-eventloop unix-signals7126655
Ref: 25c77126655
Ref: library/asyncio-eventloop asyncio loop add_signal_handler7126702
Ref: 24f37126702
Ref: library/asyncio-eventloop asyncio loop remove_signal_handler7127496
Ref: 25c87127496
Node: Executing code in thread or process pools7127806
Ref: library/asyncio-eventloop executing-code-in-thread-or-process-pools7127950
Ref: 25c97127950
Ref: library/asyncio-eventloop asyncio loop run_in_executor7128055
Ref: 24fc7128055
Ref: library/asyncio-eventloop asyncio loop set_default_executor7130196
Ref: 27c7130196
Node: Error Handling API7130677
Ref: library/asyncio-eventloop error-handling-api7130828
Ref: 25ca7130828
Ref: library/asyncio-eventloop asyncio loop set_exception_handler7130953
Ref: 25cb7130953
Ref: library/asyncio-eventloop asyncio loop get_exception_handler7131487
Ref: 5227131487
Ref: library/asyncio-eventloop asyncio loop default_exception_handler7131665
Ref: 25cd7131665
Ref: library/asyncio-eventloop asyncio loop call_exception_handler7132046
Ref: 25cc7132046
Node: Enabling debug mode7132933
Ref: library/asyncio-eventloop enabling-debug-mode7133063
Ref: 25ce7133063
Ref: library/asyncio-eventloop asyncio loop get_debug7133124
Ref: 69f7133124
Ref: library/asyncio-eventloop asyncio loop set_debug7133385
Ref: 69e7133385
Node: Running Subprocesses7133651
Ref: library/asyncio-eventloop running-subprocesses7133754
Ref: 25cf7133754
Ref: library/asyncio-eventloop asyncio loop subprocess_exec7134216
Ref: 24f27134216
Ref: library/asyncio-eventloop asyncio loop subprocess_shell7138214
Ref: 25607138214
Ref: Running Subprocesses-Footnote-17139538
Node: Callback Handles7139608
Ref: library/asyncio-eventloop callback-handles7139721
Ref: 259d7139721
Ref: library/asyncio-eventloop asyncio Handle7139776
Ref: 10a77139776
Ref: library/asyncio-eventloop asyncio Handle cancel7139922
Ref: 25d27139922
Ref: library/asyncio-eventloop asyncio Handle cancelled7140081
Ref: 36b7140081
Ref: library/asyncio-eventloop asyncio TimerHandle7140207
Ref: 259e7140207
Ref: library/asyncio-eventloop asyncio TimerHandle when7140404
Ref: 3677140404
Node: Server Objects7140653
Ref: library/asyncio-eventloop server-objects7140774
Ref: 259f7140774
Ref: library/asyncio-eventloop asyncio Server7141042
Ref: 3617141042
Ref: library/asyncio-eventloop asyncio Server close7141597
Ref: 25d37141597
Ref: library/asyncio-eventloop asyncio Server get_loop7141995
Ref: 3607141995
Ref: library/asyncio-eventloop asyncio Server start_serving7142128
Ref: 3647142128
Ref: library/asyncio-eventloop asyncio Server serve_forever7142756
Ref: 3657142756
Ref: library/asyncio-eventloop asyncio Server is_serving7143657
Ref: 3667143657
Ref: library/asyncio-eventloop asyncio Server wait_closed7143797
Ref: 25d47143797
Ref: library/asyncio-eventloop asyncio Server sockets7143911
Ref: 4a87143911
Node: Event Loop Implementations7144216
Ref: library/asyncio-eventloop asyncio-event-loops7144333
Ref: 25d57144333
Ref: library/asyncio-eventloop event-loop-implementations7144333
Ref: 25a07144333
Ref: library/asyncio-eventloop asyncio SelectorEventLoop7144661
Ref: 25787144661
Ref: library/asyncio-eventloop asyncio ProactorEventLoop7145178
Ref: 1ac7145178
Ref: library/asyncio-eventloop asyncio AbstractEventLoop7145413
Ref: 25d67145413
Ref: Event Loop Implementations-Footnote-17145709
Node: Examples<14>7145795
Ref: library/asyncio-eventloop examples7145889
Ref: 25a17145889
Node: Hello World with call_soon7146488
Ref: library/asyncio-eventloop asyncio-example-lowlevel-helloworld7146612
Ref: 25d77146612
Ref: library/asyncio-eventloop hello-world-with-call-soon7146612
Ref: 25d87146612
Node: Display the current date with call_later7147385
Ref: library/asyncio-eventloop asyncio-example-call-later7147557
Ref: 25d97147557
Ref: library/asyncio-eventloop display-the-current-date-with-call-later7147557
Ref: 25da7147557
Node: Watch a file descriptor for read events7148548
Ref: library/asyncio-eventloop asyncio-example-watch-fd7148736
Ref: 253f7148736
Ref: library/asyncio-eventloop watch-a-file-descriptor-for-read-events7148736
Ref: 25db7148736
Node: Set signal handlers for SIGINT and SIGTERM7150055
Ref: library/asyncio-eventloop asyncio-example-unix-signals7150194
Ref: 25dc7150194
Ref: library/asyncio-eventloop set-signal-handlers-for-sigint-and-sigterm7150194
Ref: 25dd7150194
Node: Futures7151109
Ref: library/asyncio-future doc7151233
Ref: 25de7151233
Ref: library/asyncio-future asyncio-futures7151233
Ref: 24f57151233
Ref: library/asyncio-future futures7151233
Ref: 25df7151233
Ref: Futures-Footnote-17151600
Ref: Futures-Footnote-27151674
Node: Future Functions7151754
Ref: library/asyncio-future future-functions7151836
Ref: 25e07151836
Ref: library/asyncio-future asyncio isfuture7151891
Ref: 25e17151891
Ref: library/asyncio-future asyncio ensure_future7152193
Ref: 51c7152193
Ref: library/asyncio-future asyncio wrap_future7153120
Ref: 25e27153120
Node: Future Object7153279
Ref: library/asyncio-future future-object7153361
Ref: 25e37153361
Ref: library/asyncio-future asyncio Future7153410
Ref: 4487153410
Ref: library/asyncio-future asyncio Future result7154319
Ref: 25e47154319
Ref: library/asyncio-future asyncio Future set_result7154940
Ref: 250f7154940
Ref: library/asyncio-future asyncio Future set_exception7155141
Ref: 25107155141
Ref: library/asyncio-future asyncio Future done7155350
Ref: 25e57155350
Ref: library/asyncio-future asyncio Future cancelled7155620
Ref: 25e67155620
Ref: library/asyncio-future asyncio Future add_done_callback7155931
Ref: 3527155931
Ref: library/asyncio-future asyncio Future remove_done_callback7156916
Ref: 25197156916
Ref: library/asyncio-future asyncio Future cancel7157154
Ref: 25117157154
Ref: library/asyncio-future asyncio Future exception7157443
Ref: 25e77157443
Ref: library/asyncio-future asyncio Future get_loop7157893
Ref: 35f7157893
Ref: library/asyncio-future asyncio-example-future7158022
Ref: 25e87158022
Ref: Future Object-Footnote-17160056
Node: Transports and Protocols7160105
Ref: library/asyncio-protocol doc7160227
Ref: 25e97160227
Ref: library/asyncio-protocol asyncio-transports-protocols7160227
Ref: 24f47160227
Ref: library/asyncio-protocol transports-and-protocols7160227
Ref: 25ea7160227
Node: Transports7162595
Ref: library/asyncio-protocol asyncio-transport7162684
Ref: 25b17162684
Ref: library/asyncio-protocol transports7162684
Ref: 25eb7162684
Ref: Transports-Footnote-17163426
Node: Transports Hierarchy7163504
Ref: library/asyncio-protocol transports-hierarchy7163594
Ref: 25f47163594
Ref: library/asyncio-protocol asyncio BaseTransport7163657
Ref: 25ed7163657
Ref: library/asyncio-protocol asyncio WriteTransport7163787
Ref: 25c67163787
Ref: library/asyncio-protocol asyncio ReadTransport7164119
Ref: 25c57164119
Ref: library/asyncio-protocol asyncio Transport7164447
Ref: 25ee7164447
Ref: library/asyncio-protocol asyncio DatagramTransport7165051
Ref: 25ef7165051
Ref: library/asyncio-protocol asyncio SubprocessTransport7165295
Ref: 25d17165295
Node: Base Transport7165622
Ref: library/asyncio-protocol base-transport7165741
Ref: 25f57165741
Ref: library/asyncio-protocol asyncio BaseTransport close7165792
Ref: 25f67165792
Ref: library/asyncio-protocol asyncio BaseTransport is_closing7166169
Ref: 5207166169
Ref: library/asyncio-protocol asyncio BaseTransport get_extra_info7166282
Ref: 2c97166282
Ref: library/asyncio-protocol asyncio BaseTransport set_protocol7168445
Ref: 25fb7168445
Ref: library/asyncio-protocol asyncio BaseTransport get_protocol7168636
Ref: 25fc7168636
Node: Read-only Transports7168720
Ref: library/asyncio-protocol read-only-transports7168840
Ref: 25fd7168840
Ref: library/asyncio-protocol asyncio ReadTransport is_reading7168903
Ref: 36c7168903
Ref: library/asyncio-protocol asyncio ReadTransport pause_reading7169038
Ref: 36e7169038
Ref: library/asyncio-protocol asyncio ReadTransport resume_reading7169404
Ref: 36d7169404
Node: Write-only Transports7169739
Ref: library/asyncio-protocol write-only-transports7169864
Ref: 25ff7169864
Ref: library/asyncio-protocol asyncio WriteTransport abort7169929
Ref: 26007169929
Ref: library/asyncio-protocol asyncio WriteTransport can_write_eof7170274
Ref: 26017170274
Ref: library/asyncio-protocol asyncio WriteTransport get_write_buffer_size7170437
Ref: 26037170437
Ref: library/asyncio-protocol asyncio WriteTransport get_write_buffer_limits7170570
Ref: 6a17170570
Ref: library/asyncio-protocol asyncio WriteTransport set_write_buffer_limits7170888
Ref: 26047170888
Ref: library/asyncio-protocol asyncio WriteTransport write7172316
Ref: 26077172316
Ref: library/asyncio-protocol asyncio WriteTransport writelines7172521
Ref: 26087172521
Ref: library/asyncio-protocol asyncio WriteTransport write_eof7172811
Ref: 26027172811
Node: Datagram Transports7173106
Ref: library/asyncio-protocol datagram-transports7173232
Ref: 26097173232
Ref: library/asyncio-protocol asyncio DatagramTransport sendto7173293
Ref: 260a7173293
Ref: library/asyncio-protocol asyncio DatagramTransport abort7173677
Ref: 260b7173677
Node: Subprocess Transports7174025
Ref: library/asyncio-protocol asyncio-subprocess-transports7174121
Ref: 25647174121
Ref: library/asyncio-protocol subprocess-transports7174121
Ref: 260c7174121
Ref: library/asyncio-protocol asyncio SubprocessTransport get_pid7174186
Ref: 260d7174186
Ref: library/asyncio-protocol asyncio SubprocessTransport get_pipe_transport7174290
Ref: 260e7174290
Ref: library/asyncio-protocol asyncio SubprocessTransport get_returncode7175042
Ref: 260f7175042
Ref: library/asyncio-protocol asyncio SubprocessTransport kill7175284
Ref: 26107175284
Ref: library/asyncio-protocol asyncio SubprocessTransport send_signal7175551
Ref: 26127175551
Ref: library/asyncio-protocol asyncio SubprocessTransport terminate7175716
Ref: 26117175716
Ref: library/asyncio-protocol asyncio SubprocessTransport close7176022
Ref: 26137176022
Node: Protocols7176254
Ref: library/asyncio-protocol asyncio-protocol7176364
Ref: 25b07176364
Ref: library/asyncio-protocol protocols7176364
Ref: 25ec7176364
Ref: Protocols-Footnote-17177157
Node: Base Protocols7177234
Ref: library/asyncio-protocol base-protocols7177316
Ref: 26147177316
Ref: library/asyncio-protocol asyncio BaseProtocol7177367
Ref: 25f07177367
Ref: library/asyncio-protocol asyncio Protocol7177460
Ref: 25f17177460
Ref: library/asyncio-protocol asyncio BufferedProtocol7177594
Ref: 2ca7177594
Ref: library/asyncio-protocol asyncio DatagramProtocol7177751
Ref: 25f27177751
Ref: library/asyncio-protocol asyncio SubprocessProtocol7177868
Ref: 25d07177868
Node: Base Protocol7178035
Ref: library/asyncio-protocol base-protocol7178145
Ref: 26157178145
Ref: library/asyncio-protocol asyncio BaseProtocol connection_made7178468
Ref: 25b27178468
Ref: library/asyncio-protocol asyncio BaseProtocol connection_lost7178728
Ref: 25f77178728
Ref: library/asyncio-protocol asyncio BaseProtocol pause_writing7179277
Ref: 26057179277
Ref: library/asyncio-protocol asyncio BaseProtocol resume_writing7179399
Ref: 26067179399
Node: Streaming Protocols7179869
Ref: library/asyncio-protocol streaming-protocols7179993
Ref: 26167179993
Ref: library/asyncio-protocol asyncio Protocol data_received7180403
Ref: 25fe7180403
Ref: library/asyncio-protocol asyncio Protocol eof_received7181090
Ref: 26177181090
Node: Buffered Streaming Protocols7181960
Ref: library/asyncio-protocol buffered-streaming-protocols7182089
Ref: 26187182089
Ref: library/asyncio-protocol asyncio BufferedProtocol get_buffer7182953
Ref: 26197182953
Ref: library/asyncio-protocol asyncio BufferedProtocol buffer_updated7183433
Ref: 261a7183433
Ref: library/asyncio-protocol asyncio BufferedProtocol eof_received7183640
Ref: 261b7183640
Node: Datagram Protocols7184218
Ref: library/asyncio-protocol datagram-protocols7184348
Ref: 261c7184348
Ref: library/asyncio-protocol asyncio DatagramProtocol datagram_received7184546
Ref: 261d7184546
Ref: library/asyncio-protocol asyncio DatagramProtocol error_received7184817
Ref: 261e7184817
Node: Subprocess Protocols7185760
Ref: library/asyncio-protocol asyncio-subprocess-protocols7185853
Ref: 25657185853
Ref: library/asyncio-protocol subprocess-protocols7185853
Ref: 261f7185853
Ref: library/asyncio-protocol asyncio SubprocessProtocol pipe_data_received7186089
Ref: 26207186089
Ref: library/asyncio-protocol asyncio SubprocessProtocol pipe_connection_lost7186368
Ref: 26217186368
Ref: library/asyncio-protocol asyncio SubprocessProtocol process_exited7186584
Ref: 26227186584
Node: Examples<15>7186688
Ref: library/asyncio-protocol examples7186779
Ref: 25f37186779
Node: TCP Echo Server7187034
Ref: library/asyncio-protocol asyncio-example-tcp-echo-server-protocol7187122
Ref: 253a7187122
Ref: library/asyncio-protocol tcp-echo-server7187122
Ref: 26237187122
Node: TCP Echo Client7188405
Ref: library/asyncio-protocol asyncio-example-tcp-echo-client-protocol7188517
Ref: 25377188517
Ref: library/asyncio-protocol tcp-echo-client7188517
Ref: 26247188517
Node: UDP Echo Server7190074
Ref: library/asyncio-protocol asyncio-udp-echo-server-protocol7190186
Ref: 25b67190186
Ref: library/asyncio-protocol udp-echo-server7190186
Ref: 26257190186
Node: UDP Echo Client7191332
Ref: library/asyncio-protocol asyncio-udp-echo-client-protocol7191456
Ref: 25b57191456
Ref: library/asyncio-protocol udp-echo-client7191456
Ref: 26267191456
Node: Connecting Existing Sockets7192988
Ref: library/asyncio-protocol asyncio-example-create-connection7193140
Ref: 253e7193140
Ref: library/asyncio-protocol connecting-existing-sockets7193140
Ref: 26277193140
Node: loop subprocess_exec and SubprocessProtocol7195051
Ref: library/asyncio-protocol asyncio-example-subprocess-proto7195179
Ref: 257c7195179
Ref: library/asyncio-protocol loop-subprocess-exec-and-subprocessprotocol7195179
Ref: 26287195179
Node: Policies7196980
Ref: library/asyncio-policy doc7197111
Ref: 26297197111
Ref: library/asyncio-policy asyncio-policies7197111
Ref: 259b7197111
Ref: library/asyncio-policy policies7197111
Ref: 262a7197111
Node: Getting and Setting the Policy7197897
Ref: library/asyncio-policy getting-and-setting-the-policy7197995
Ref: 262c7197995
Ref: library/asyncio-policy asyncio get_event_loop_policy7198166
Ref: 262d7198166
Ref: library/asyncio-policy asyncio set_event_loop_policy7198258
Ref: 262e7198258
Node: Policy Objects7198437
Ref: library/asyncio-policy policy-objects7198560
Ref: 262f7198560
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy7198677
Ref: 262b7198677
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy get_event_loop7198773
Ref: 26307198773
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy set_event_loop7199059
Ref: 26317199059
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy new_event_loop7199170
Ref: 26327199170
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy get_child_watcher7199321
Ref: 26337199321
Ref: library/asyncio-policy asyncio AbstractEventLoopPolicy set_child_watcher7199563
Ref: 26357199563
Ref: library/asyncio-policy asyncio DefaultEventLoopPolicy7199774
Ref: 26367199774
Ref: library/asyncio-policy asyncio WindowsSelectorEventLoopPolicy7200172
Ref: 26377200172
Ref: library/asyncio-policy asyncio WindowsProactorEventLoopPolicy7200382
Ref: 26387200382
Node: Process Watchers7200591
Ref: library/asyncio-policy asyncio-watchers7200699
Ref: 25797200699
Ref: library/asyncio-policy process-watchers7200699
Ref: 26397200699
Ref: library/asyncio-policy asyncio get_child_watcher7201570
Ref: 263d7201570
Ref: library/asyncio-policy asyncio set_child_watcher7201675
Ref: 263e7201675
Ref: library/asyncio-policy asyncio AbstractChildWatcher7202107
Ref: 26347202107
Ref: library/asyncio-policy asyncio AbstractChildWatcher add_child_handler7202149
Ref: 263f7202149
Ref: library/asyncio-policy asyncio AbstractChildWatcher remove_child_handler7202548
Ref: 26407202548
Ref: library/asyncio-policy asyncio AbstractChildWatcher attach_loop7202805
Ref: 26417202805
Ref: library/asyncio-policy asyncio AbstractChildWatcher is_active7203075
Ref: 26427203075
Ref: library/asyncio-policy asyncio AbstractChildWatcher close7203315
Ref: 26437203315
Ref: library/asyncio-policy asyncio ThreadedChildWatcher7203480
Ref: 257a7203480
Ref: library/asyncio-policy asyncio MultiLoopChildWatcher7203949
Ref: 263a7203949
Ref: library/asyncio-policy asyncio SafeChildWatcher7204607
Ref: 263b7204607
Ref: library/asyncio-policy asyncio FastChildWatcher7205197
Ref: 263c7205197
Node: Custom Policies7205666
Ref: library/asyncio-policy custom-policies7205751
Ref: 26447205751
Node: Platform Support7206358
Ref: library/asyncio-platforms doc7206485
Ref: 26457206485
Ref: library/asyncio-platforms asyncio-platform-support7206485
Ref: 25bf7206485
Ref: library/asyncio-platforms platform-support7206485
Ref: 26467206485
Node: All Platforms7206795
Ref: library/asyncio-platforms all-platforms7206881
Ref: 26477206881
Node: Windows<52>7207045
Ref: library/asyncio-platforms windows7207149
Ref: 26487207149
Ref: Windows<52>-Footnote-17208970
Ref: Windows<52>-Footnote-27209053
Ref: Windows<52>-Footnote-37209135
Ref: Windows<52>-Footnote-47209216
Node: Subprocess Support on Windows7209281
Ref: library/asyncio-platforms asyncio-windows-subprocess7209358
Ref: 25617209358
Ref: library/asyncio-platforms subprocess-support-on-windows7209358
Ref: 264a7209358
Node: macOS<25>7209741
Ref: library/asyncio-platforms macos7209823
Ref: 264b7209823
Node: High-level API Index7210455
Ref: library/asyncio-api-index doc7210593
Ref: 264d7210593
Ref: library/asyncio-api-index high-level-api-index7210593
Ref: 264e7210593
Node: Tasks7210870
Ref: library/asyncio-api-index tasks7210950
Ref: 264f7210950
Node: Queues<2>7213723
Ref: library/asyncio-api-index queues7213827
Ref: 26507213827
Node: Subprocesses<2>7214646
Ref: library/asyncio-api-index subprocesses7214755
Ref: 26517214755
Node: Streams<2>7215317
Ref: library/asyncio-api-index streams7215432
Ref: 26527215432
Node: Synchronization7216867
Ref: library/asyncio-api-index synchronization7216980
Ref: 26537216980
Node: Exceptions<9>7218117
Ref: library/asyncio-api-index exceptions7218211
Ref: 26547218211
Node: Low-level API Index7219173
Ref: library/asyncio-llapi-index doc7219318
Ref: 26557219318
Ref: library/asyncio-llapi-index low-level-api-index7219318
Ref: 26567219318
Node: Obtaining the Event Loop7219590
Ref: library/asyncio-llapi-index obtaining-the-event-loop7219700
Ref: 26577219700
Node: Event Loop Methods<2>7220813
Ref: library/asyncio-llapi-index event-loop-methods7220945
Ref: 26587220945
Node: Transports<2>7232476
Ref: library/asyncio-llapi-index transports7232596
Ref: 26597232596
Node: Protocols<2>7238428
Ref: library/asyncio-llapi-index protocols7238546
Ref: 265a7238546
Node: Event Loop Policies7242069
Ref: library/asyncio-llapi-index event-loop-policies7242165
Ref: 265b7242165
Node: Developing with asyncio7242994
Ref: library/asyncio-dev doc7243110
Ref: 265c7243110
Ref: library/asyncio-dev asyncio-dev7243110
Ref: 265d7243110
Ref: library/asyncio-dev developing-with-asyncio7243110
Ref: 265e7243110
Node: Debug Mode7243517
Ref: library/asyncio-dev asyncio-debug-mode7243626
Ref: 13557243626
Ref: library/asyncio-dev debug-mode7243626
Ref: 265f7243626
Node: Concurrency and Multithreading7245245
Ref: library/asyncio-dev asyncio-multithreading7245384
Ref: 250b7245384
Ref: library/asyncio-dev concurrency-and-multithreading7245384
Ref: 26627245384
Node: Running Blocking Code7247696
Ref: library/asyncio-dev asyncio-handle-blocking7247835
Ref: 26637247835
Ref: library/asyncio-dev running-blocking-code7247835
Ref: 26647247835
Node: Logging<3>7248330
Ref: library/asyncio-dev asyncio-logger7248470
Ref: 26607248470
Ref: library/asyncio-dev logging7248470
Ref: 26657248470
Node: Detect never-awaited coroutines7248751
Ref: library/asyncio-dev asyncio-coroutine-not-scheduled7248903
Ref: 26617248903
Ref: library/asyncio-dev detect-never-awaited-coroutines7248903
Ref: 26667248903
Node: Detect never-retrieved exceptions7249912
Ref: library/asyncio-dev detect-never-retrieved-exceptions7250045
Ref: 26677250045
Ref: Detect never-retrieved exceptions-Footnote-17251657
Node: socket --- Low-level networking interface7251721
Ref: library/socket doc7251928
Ref: 26687251928
Ref: library/socket module-socket7251928
Ref: f07251928
Ref: library/socket socket-low-level-networking-interface7251928
Ref: 26697251928
Ref: socket --- Low-level networking interface-Footnote-17253244
Node: Socket families7253309
Ref: library/socket socket-families7253426
Ref: 266a7253426
Ref: library/socket host-port7254599
Ref: 266b7254599
Ref: Socket families-Footnote-17262524
Node: Module contents7262573
Ref: library/socket module-contents7262713
Ref: 26717262713
Node: Exceptions<10>7262920
Ref: library/socket exceptions7263007
Ref: 26727263007
Ref: library/socket socket error7263048
Ref: 99a7263048
Ref: library/socket socket herror7263223
Ref: 26737263223
Ref: library/socket socket gaierror7263828
Ref: 26747263828
Ref: library/socket socket timeout7264416
Ref: c137264416
Ref: Exceptions<10>-Footnote-17264890
Node: Constants<8>7264939
Ref: library/socket constants7265047
Ref: 26767265047
Ref: library/socket socket AF_UNIX7265233
Ref: 25b47265233
Ref: library/socket socket AF_INET7265258
Ref: 25ae7265258
Ref: library/socket socket AF_INET67265283
Ref: 25af7265283
Ref: library/socket socket SOCK_STREAM7265597
Ref: c8f7265597
Ref: library/socket socket SOCK_DGRAM7265626
Ref: c8e7265626
Ref: library/socket socket SOCK_RAW7265654
Ref: 26777265654
Ref: library/socket socket SOCK_RDM7265680
Ref: 26787265680
Ref: library/socket socket SOCK_SEQPACKET7265706
Ref: 26797265706
Ref: library/socket socket SOCK_CLOEXEC7266005
Ref: 49c7266005
Ref: library/socket socket SOCK_NONBLOCK7266035
Ref: 49b7266035
Ref: library/socket socket SOMAXCONN7266462
Ref: 7517266462
Ref: library/socket socket AF_CAN7267553
Ref: 266c7267553
Ref: library/socket socket PF_CAN7267577
Ref: 267a7267577
Ref: library/socket socket CAN_BCM7267834
Ref: 8be7267834
Ref: library/socket socket CAN_RAW_FD_FRAMES7268257
Ref: 7ca7268257
Ref: library/socket socket CAN_ISOTP7268669
Ref: 266d7268669
Ref: library/socket socket AF_PACKET7268917
Ref: 266e7268917
Ref: library/socket socket PF_PACKET7268944
Ref: 267b7268944
Ref: library/socket socket AF_RDS7269159
Ref: 267c7269159
Ref: library/socket socket PF_RDS7269183
Ref: 267d7269183
Ref: library/socket socket SOL_RDS7269207
Ref: 267e7269207
Ref: library/socket socket SIO_RCVALL7269444
Ref: 267f7269444
Ref: library/socket socket SIO_KEEPALIVE_VALS7269472
Ref: 26807269472
Ref: library/socket socket SIO_LOOPBACK_FAST_PATH7269508
Ref: 5867269508
Ref: library/socket socket AF_ALG7269918
Ref: 5897269918
Ref: library/socket socket SOL_ALG7269942
Ref: 26817269942
Ref: library/socket socket AF_VSOCK7270106
Ref: 3d87270106
Ref: library/socket socket IOCTL_VM_SOCKETS_GET_LOCAL_CID7270132
Ref: 26827270132
Ref: library/socket socket AF_LINK7270341
Ref: 8bf7270341
Ref: library/socket socket has_ipv67270434
Ref: 26837270434
Ref: library/socket socket BDADDR_ANY7270566
Ref: 26847270566
Ref: library/socket socket BDADDR_LOCAL7270594
Ref: 26857270594
Ref: library/socket socket HCI_FILTER7270863
Ref: 26867270863
Ref: library/socket socket HCI_TIME_STAMP7270891
Ref: 26877270891
Ref: library/socket socket HCI_DATA_DIR7270923
Ref: 26887270923
Ref: library/socket socket AF_QIPCRTR7271191
Ref: 266f7271191
Ref: Constants<8>-Footnote-17271423
Node: Functions<5>7271474
Ref: library/socket functions7271559
Ref: 26897271559
Node: Creating sockets7271668
Ref: library/socket creating-sockets7271760
Ref: 268a7271760
Ref: library/socket socket socket7271877
Ref: 6797271877
Ref: library/socket socket socketpair7274249
Ref: 4867274249
Ref: library/socket socket create_connection7274952
Ref: ba37274952
Ref: library/socket socket create_server7276100
Ref: 21f7276100
Ref: library/socket socket has_dualstack_ipv67277874
Ref: 2207277874
Ref: library/socket socket fromfd7278065
Ref: 268c7278065
Ref: library/socket socket fromshare7278936
Ref: 4987278936
Ref: library/socket socket SocketType7279186
Ref: 268e7279186
Node: Other functions<2>7279339
Ref: library/socket other-functions7279431
Ref: 268f7279431
Ref: library/socket socket close7279558
Ref: 3d67279558
Ref: library/socket socket getaddrinfo7279826
Ref: 25c27279826
Ref: library/socket socket getfqdn7282549
Ref: 26907282549
Ref: library/socket socket gethostbyname7283062
Ref: 26917283062
Ref: library/socket socket gethostbyname_ex7283659
Ref: ea37283659
Ref: library/socket socket gethostname7284430
Ref: 1f0a7284430
Ref: library/socket socket gethostbyaddr7284814
Ref: ea27284814
Ref: library/socket socket getnameinfo7285507
Ref: 25c37285507
Ref: library/socket socket getprotobyname7286226
Ref: 26927286226
Ref: library/socket socket getservbyname7286674
Ref: 26937286674
Ref: library/socket socket getservbyport7287083
Ref: 26947287083
Ref: library/socket socket ntohl7287478
Ref: 26957287478
Ref: library/socket socket ntohs7287733
Ref: 4727287733
Ref: library/socket socket htonl7288280
Ref: 26967288280
Ref: library/socket socket htons7288535
Ref: 4717288535
Ref: library/socket socket inet_aton7289082
Ref: 26977289082
Ref: library/socket socket inet_ntoa7290017
Ref: 26987290017
Ref: library/socket socket inet_pton7290830
Ref: 8c07290830
Ref: library/socket socket inet_ntop7291654
Ref: 8c17291654
Ref: library/socket socket CMSG_LEN7292653
Ref: 10267292653
Ref: library/socket socket CMSG_SPACE7293324
Ref: 10257293324
Ref: library/socket socket getdefaulttimeout7294214
Ref: 268d7294214
Ref: library/socket socket setdefaulttimeout7294490
Ref: 26757294490
Ref: library/socket socket sethostname7294776
Ref: a8c7294776
Ref: library/socket socket if_nameindex7295103
Ref: 2217295103
Ref: library/socket socket if_nametoindex7295882
Ref: 2227295882
Ref: library/socket socket if_indextoname7296314
Ref: 2237296314
Ref: Other functions<2>-Footnote-17296784
Node: Socket Objects7296833
Ref: library/socket id17296982
Ref: 26997296982
Ref: library/socket socket-objects7296982
Ref: 268b7296982
Ref: library/socket socket socket accept7297325
Ref: 67a7297325
Ref: library/socket socket socket bind7298079
Ref: 269a7298079
Ref: library/socket socket socket close7298385
Ref: 6057298385
Ref: library/socket socket socket connect7299379
Ref: 67b7299379
Ref: library/socket socket socket connect_ex7300448
Ref: 269c7300448
Ref: library/socket socket socket detach7301029
Ref: ba27301029
Ref: library/socket socket socket dup7301274
Ref: 269d7301274
Ref: library/socket socket socket fileno7301453
Ref: 269e7301453
Ref: library/socket socket socket get_inheritable7301820
Ref: 8047301820
Ref: library/socket socket socket getpeername7302086
Ref: 25f87302086
Ref: library/socket socket socket getsockname7302431
Ref: 25f97302431
Ref: library/socket socket socket getsockopt7302686
Ref: 5877302686
Ref: library/socket socket socket getblocking7303388
Ref: 3d57303388
Ref: library/socket socket socket gettimeout7303614
Ref: 269f7303614
Ref: library/socket socket socket ioctl7303867
Ref: 5857303867
Ref: library/socket socket socket listen7304501
Ref: 7507304501
Ref: library/socket socket socket makefile7304924
Ref: b1e7304924
Ref: library/socket socket socket recv7306047
Ref: 67c7306047
Ref: library/socket socket socket recvfrom7306842
Ref: 67d7306842
Ref: library/socket socket socket recvmsg7307766
Ref: 67e7307766
Ref: library/socket socket socket recvmsg_into7311693
Ref: a8b7311693
Ref: library/socket socket socket recvfrom_into7313340
Ref: cb87313340
Ref: library/socket socket socket recv_into7313880
Ref: cb77313880
Ref: library/socket socket socket send7314333
Ref: 67f7314333
Ref: library/socket socket socket sendall7315143
Ref: 6807315143
Ref: library/socket socket socket sendto7316105
Ref: 6827316105
Ref: library/socket socket socket sendmsg7316938
Ref: 6817316938
Ref: library/socket socket socket sendmsg_afalg7319099
Ref: 58a7319099
Ref: library/socket socket socket sendfile7319441
Ref: 74f7319441
Ref: library/socket socket socket set_inheritable7320349
Ref: 8057320349
Ref: library/socket socket socket setblocking7320533
Ref: 1f167320533
Ref: library/socket socket socket settimeout7321102
Ref: 26707321102
Ref: library/socket socket socket setsockopt7321835
Ref: 5887321835
Ref: library/socket socket socket shutdown7322908
Ref: 269b7322908
Ref: library/socket socket socket share7323210
Ref: 4997323210
Ref: library/socket socket socket family7324080
Ref: 26a37324080
Ref: library/socket socket socket type7324132
Ref: 49d7324132
Ref: library/socket socket socket proto7324180
Ref: 26a47324180
Ref: Socket Objects-Footnote-17324269
Ref: Socket Objects-Footnote-27324318
Ref: Socket Objects-Footnote-37324367
Ref: Socket Objects-Footnote-47324441
Ref: Socket Objects-Footnote-57324490
Ref: Socket Objects-Footnote-67324539
Ref: Socket Objects-Footnote-77324588
Ref: Socket Objects-Footnote-87324637
Ref: Socket Objects-Footnote-97324686
Ref: Socket Objects-Footnote-107324735
Node: Notes on socket timeouts7324785
Ref: library/socket notes-on-socket-timeouts7324929
Ref: 26a57324929
Ref: library/socket socket-timeouts7324929
Ref: 26a27324929
Node: Timeouts and the connect method7326288
Ref: library/socket timeouts-and-the-connect-method7326419
Ref: 26a67326419
Node: Timeouts and the accept method7326894
Ref: library/socket timeouts-and-the-accept-method7327025
Ref: 26a77327025
Node: Example<8>7327766
Ref: library/socket example7327887
Ref: 26a87327887
Ref: library/socket socket-example7327887
Ref: 26a97327887
Ref: Example<8>-Footnote-17335627
Node: ssl --- TLS/SSL wrapper for socket objects7335676
Ref: library/ssl doc7335892
Ref: 26aa7335892
Ref: library/ssl module-ssl7335892
Ref: f47335892
Ref: library/ssl ssl-tls-ssl-wrapper-for-socket-objects7335892
Ref: 26ab7335892
Ref: ssl --- TLS/SSL wrapper for socket objects-Footnote-17338474
Node: Functions Constants and Exceptions7338536
Ref: library/ssl functions-constants-and-exceptions7338669
Ref: 26ac7338669
Node: Socket creation7338917
Ref: library/ssl socket-creation7339028
Ref: 26ad7339028
Node: Context creation7340795
Ref: library/ssl context-creation7340929
Ref: 26ae7340929
Ref: library/ssl ssl create_default_context7341071
Ref: 8c67341071
Ref: Context creation-Footnote-17343888
Node: Exceptions<11>7343933
Ref: library/ssl exceptions7344069
Ref: 26b47344069
Ref: library/ssl ssl SSLError7344110
Ref: c147344110
Ref: library/ssl ssl SSLError library7344670
Ref: a9d7344670
Ref: library/ssl ssl SSLError reason7344943
Ref: a9e7344943
Ref: library/ssl ssl SSLZeroReturnError7345197
Ref: 26b57345197
Ref: library/ssl ssl SSLWantReadError7345486
Ref: 75b7345486
Ref: library/ssl ssl SSLWantWriteError7345788
Ref: 75c7345788
Ref: library/ssl ssl SSLSyscallError7346087
Ref: 26b77346087
Ref: library/ssl ssl SSLEOFError7346371
Ref: 26b87346371
Ref: library/ssl ssl SSLCertVerificationError7346634
Ref: 3e27346634
Ref: library/ssl ssl SSLCertVerificationError verify_code7346793
Ref: 26b97346793
Ref: library/ssl ssl SSLCertVerificationError verify_message7346894
Ref: 26ba7346894
Ref: library/ssl ssl CertificateError7346989
Ref: 26bb7346989
Node: Random generation7347176
Ref: library/ssl random-generation7347316
Ref: 26bc7347316
Ref: library/ssl ssl RAND_bytes7347371
Ref: a947347371
Ref: library/ssl ssl RAND_pseudo_bytes7348039
Ref: a957348039
Ref: library/ssl ssl RAND_status7348876
Ref: 26bd7348876
Ref: library/ssl ssl RAND_egd7349201
Ref: 26bf7349201
Ref: library/ssl ssl RAND_add7349856
Ref: 26be7349856
Ref: Random generation-Footnote-17350282
Ref: Random generation-Footnote-27350376
Node: Certificate handling7350425
Ref: library/ssl certificate-handling7350563
Ref: 26c07350563
Ref: library/ssl ssl match_hostname7350624
Ref: 3e17350624
Ref: library/ssl ssl cert_time_to_seconds7352525
Ref: 75d7352525
Ref: library/ssl ssl get_server_certificate7353408
Ref: a9f7353408
Ref: library/ssl ssl DER_cert_to_PEM_cert7354399
Ref: 26c27354399
Ref: library/ssl ssl PEM_cert_to_DER_cert7354579
Ref: 26c37354579
Ref: library/ssl ssl get_default_verify_paths7354757
Ref: 8c77354757
Ref: library/ssl ssl enum_certificates7355759
Ref: 8d37355759
Ref: library/ssl ssl enum_crls7356632
Ref: 8d47356632
Ref: library/ssl ssl wrap_socket7357159
Ref: 4747357159
Ref: Certificate handling-Footnote-17358641
Ref: Certificate handling-Footnote-27358690
Ref: Certificate handling-Footnote-37358739
Ref: Certificate handling-Footnote-47358788
Ref: Certificate handling-Footnote-57358837
Node: Constants<9>7358886
Ref: library/ssl constants7358998
Ref: 26c67358998
Ref: library/ssl ssl CERT_NONE7359161
Ref: 26c77359161
Ref: library/ssl ssl CERT_OPTIONAL7359778
Ref: 26c97359778
Ref: library/ssl ssl CERT_REQUIRED7360683
Ref: 26b27360683
Ref: library/ssl ssl VerifyMode7361808
Ref: 26cb7361808
Ref: library/ssl ssl VERIFY_DEFAULT7361923
Ref: 8cc7361923
Ref: library/ssl ssl VERIFY_CRL_CHECK_LEAF7362174
Ref: 8cd7362174
Ref: library/ssl ssl VERIFY_CRL_CHECK_CHAIN7362617
Ref: 8ce7362617
Ref: library/ssl ssl VERIFY_X509_STRICT7362821
Ref: 8cf7362821
Ref: library/ssl ssl VERIFY_X509_TRUSTED_FIRST7362999
Ref: 26cc7362999
Ref: library/ssl ssl VerifyFlags7363286
Ref: 26cd7363286
Ref: library/ssl ssl PROTOCOL_TLS7363405
Ref: 26af7363405
Ref: library/ssl ssl PROTOCOL_TLS_CLIENT7363625
Ref: 26c87363625
Ref: library/ssl ssl PROTOCOL_TLS_SERVER7363937
Ref: 26ce7363937
Ref: library/ssl ssl PROTOCOL_SSLv237364151
Ref: 26cf7364151
Ref: library/ssl ssl PROTOCOL_SSLv27364290
Ref: 26d07364290
Ref: library/ssl ssl PROTOCOL_SSLv37364640
Ref: 26c17364640
Ref: library/ssl ssl PROTOCOL_TLSv17365122
Ref: 26d17365122
Ref: library/ssl ssl PROTOCOL_TLSv1_17365412
Ref: 8c47365412
Ref: library/ssl ssl PROTOCOL_TLSv1_27365777
Ref: 8c57365777
Ref: library/ssl ssl OP_ALL7366268
Ref: 26d27366268
Ref: library/ssl ssl OP_NO_SSLv27366523
Ref: ba57366523
Ref: library/ssl ssl OP_NO_SSLv37366813
Ref: 26b07366813
Ref: library/ssl ssl OP_NO_TLSv17367103
Ref: 26d37367103
Ref: library/ssl ssl OP_NO_TLSv1_17367531
Ref: 26d47367531
Ref: library/ssl ssl OP_NO_TLSv1_27367902
Ref: 26d57367902
Ref: library/ssl ssl OP_NO_TLSv1_37368273
Ref: 26d67368273
Ref: library/ssl ssl OP_NO_RENEGOTIATION7368853
Ref: 26d77368853
Ref: library/ssl ssl OP_CIPHER_SERVER_PREFERENCE7369132
Ref: aa07369132
Ref: library/ssl ssl OP_SINGLE_DH_USE7369361
Ref: 26d87369361
Ref: library/ssl ssl OP_SINGLE_ECDH_USE7369613
Ref: 26d97369613
Ref: library/ssl ssl OP_ENABLE_MIDDLEBOX_COMPAT7369869
Ref: 26da7369869
Ref: library/ssl ssl OP_NO_COMPRESSION7370144
Ref: a9b7370144
Ref: library/ssl ssl Options7370399
Ref: 26db7370399
Ref: library/ssl ssl OP_NO_TICKET7370486
Ref: 26dc7370486
Ref: library/ssl ssl OP_IGNORE_UNEXPECTED_EOF7370598
Ref: e9a7370598
Ref: library/ssl ssl HAS_ALPN7370782
Ref: 7587370782
Ref: library/ssl ssl HAS_NEVER_CHECK_COMMON_NAME7370987
Ref: 26dd7370987
Ref: library/ssl ssl HAS_ECDH7371221
Ref: 26de7371221
Ref: library/ssl ssl HAS_SNI7371476
Ref: 26df7371476
Ref: library/ssl ssl HAS_NPN7371655
Ref: 26e07371655
Ref: library/ssl ssl HAS_SSLv27372004
Ref: 26e17372004
Ref: library/ssl ssl HAS_SSLv37372139
Ref: 26e27372139
Ref: library/ssl ssl HAS_TLSv17372274
Ref: 26e37372274
Ref: library/ssl ssl HAS_TLSv1_17372409
Ref: 3ee7372409
Ref: library/ssl ssl HAS_TLSv1_27372546
Ref: 26e47372546
Ref: library/ssl ssl HAS_TLSv1_37372683
Ref: 26e57372683
Ref: library/ssl ssl CHANNEL_BINDING_TYPES7372820
Ref: 26e67372820
Ref: library/ssl ssl OPENSSL_VERSION7373036
Ref: ba67373036
Ref: library/ssl ssl OPENSSL_VERSION_INFO7373246
Ref: ba77373246
Ref: library/ssl ssl OPENSSL_VERSION_NUMBER7373470
Ref: ba87373470
Ref: library/ssl ssl ALERT_DESCRIPTION_HANDSHAKE_FAILURE7373737
Ref: 26e77373737
Ref: library/ssl ssl ALERT_DESCRIPTION_INTERNAL_ERROR7373787
Ref: 26e87373787
Ref: library/ssl ssl AlertDescription7374177
Ref: 26e97374177
Ref: library/ssl ssl Purpose SERVER_AUTH7374316
Ref: 8d17374316
Ref: library/ssl ssl Purpose CLIENT_AUTH7374627
Ref: 8d27374627
Ref: library/ssl ssl SSLErrorNumber7374938
Ref: 26ea7374938
Ref: library/ssl ssl TLSVersion7375062
Ref: 26eb7375062
Ref: library/ssl ssl TLSVersion MINIMUM_SUPPORTED7375276
Ref: 26ec7375276
Ref: library/ssl ssl TLSVersion MAXIMUM_SUPPORTED7375318
Ref: 26ed7375318
Ref: library/ssl ssl TLSVersion SSLv37375538
Ref: 26ee7375538
Ref: library/ssl ssl TLSVersion TLSv17375568
Ref: 26ef7375568
Ref: library/ssl ssl TLSVersion TLSv1_17375598
Ref: 26f07375598
Ref: library/ssl ssl TLSVersion TLSv1_27375630
Ref: 26f17375630
Ref: library/ssl ssl TLSVersion TLSv1_37375662
Ref: 26f27375662
Ref: Constants<9>-Footnote-17375756
Ref: Constants<9>-Footnote-27375805
Ref: Constants<9>-Footnote-37375854
Ref: Constants<9>-Footnote-47375932
Ref: Constants<9>-Footnote-57375981
Node: SSL Sockets7376074
Ref: library/ssl ssl-sockets7376228
Ref: 26f37376228
Ref: library/ssl ssl SSLSocket7376271
Ref: 3e77376271
Ref: library/ssl ssl SSLSocket read7378412
Ref: 7607378412
Ref: library/ssl ssl SSLSocket write7379215
Ref: 7617379215
Ref: library/ssl ssl SSLSocket do_handshake7380430
Ref: 75f7380430
Ref: library/ssl ssl SSLSocket getpeercert7381173
Ref: 8d67381173
Ref: library/ssl ssl SSLSocket cipher7384767
Ref: 25fa7384767
Ref: library/ssl ssl SSLSocket shared_ciphers7385057
Ref: 75e7385057
Ref: library/ssl ssl SSLSocket compression7385542
Ref: a9a7385542
Ref: library/ssl ssl SSLSocket get_channel_binding7385891
Ref: a997385891
Ref: library/ssl ssl SSLSocket selected_alpn_protocol7386528
Ref: 7577386528
Ref: library/ssl ssl SSLSocket selected_npn_protocol7386943
Ref: 26f67386943
Ref: library/ssl ssl SSLSocket unwrap7387301
Ref: 26f47387301
Ref: library/ssl ssl SSLSocket verify_client_post_handshake7387730
Ref: 2267387730
Ref: library/ssl ssl SSLSocket version7388614
Ref: 75a7388614
Ref: library/ssl ssl SSLSocket pending7389029
Ref: 26f77389029
Ref: library/ssl ssl SSLSocket context7389173
Ref: 26f57389173
Ref: library/ssl ssl SSLSocket server_side7389516
Ref: 26f87389516
Ref: library/ssl ssl SSLSocket server_hostname7389681
Ref: 3e57389681
Ref: library/ssl ssl SSLSocket session7390171
Ref: 26f97390171
Ref: library/ssl ssl SSLSocket session_reused7390522
Ref: 26fa7390522
Ref: SSL Sockets-Footnote-17390620
Ref: SSL Sockets-Footnote-27390669
Node: SSL Contexts7390718
Ref: library/ssl ssl-contexts7390850
Ref: 26fb7390850
Ref: library/ssl ssl SSLContext7391192
Ref: 3e97391192
Ref: library/ssl ssl SSLContext cert_store_stats7395170
Ref: 8c97395170
Ref: library/ssl ssl SSLContext load_cert_chain7395578
Ref: a967395578
Ref: library/ssl ssl SSLContext load_default_certs7397201
Ref: 8d07397201
Ref: library/ssl ssl SSLContext load_verify_locations7398035
Ref: 7f07398035
Ref: library/ssl ssl SSLContext get_ca_certs7399358
Ref: 8ca7399358
Ref: library/ssl ssl SSLContext get_ciphers7399995
Ref: 5917399995
Ref: library/ssl ssl SSLContext set_default_verify_paths7402141
Ref: 8c87402141
Ref: library/ssl ssl SSLContext set_ciphers7402612
Ref: 26c57402612
Ref: library/ssl ssl SSLContext set_alpn_protocols7403268
Ref: 7567403268
Ref: library/ssl ssl SSLContext set_npn_protocols7404160
Ref: a9c7404160
Ref: library/ssl ssl SSLContext sni_callback7404833
Ref: ead7404833
Ref: library/ssl ssl SSLContext set_servername_callback7407396
Ref: 8d57407396
Ref: library/ssl ssl SSLContext load_dh_params7408071
Ref: a977408071
Ref: library/ssl ssl SSLContext set_ecdh_curve7408618
Ref: a987408618
Ref: library/ssl ssl SSLContext wrap_socket7409348
Ref: 3ea7409348
Ref: library/ssl ssl SSLContext sslsocket_class7412114
Ref: 26fd7412114
Ref: library/ssl ssl SSLContext wrap_bio7412405
Ref: 3eb7412405
Ref: library/ssl ssl SSLContext sslobject_class7413132
Ref: 26fe7413132
Ref: library/ssl ssl SSLContext session_stats7413420
Ref: 26ff7413420
Ref: library/ssl ssl SSLContext check_hostname7413891
Ref: 26ca7413891
Ref: library/ssl ssl SSLContext keylog_filename7415465
Ref: 26b37415465
Ref: library/ssl ssl SSLContext maximum_version7415970
Ref: 3ed7415970
Ref: library/ssl ssl SSLContext minimum_version7416950
Ref: 3ec7416950
Ref: library/ssl ssl SSLContext num_tickets7417281
Ref: 27007417281
Ref: library/ssl ssl SSLContext options7417625
Ref: 26c47417625
Ref: library/ssl ssl SSLContext post_handshake_auth7418362
Ref: 2257418362
Ref: library/ssl ssl SSLContext protocol7419342
Ref: 27017419342
Ref: library/ssl ssl SSLContext hostname_checks_common_name7419475
Ref: 3e37419475
Ref: library/ssl ssl SSLContext verify_flags7419959
Ref: 8cb7419959
Ref: library/ssl ssl SSLContext verify_mode7420529
Ref: 26b17420529
Ref: SSL Contexts-Footnote-17421023
Ref: SSL Contexts-Footnote-27421181
Ref: SSL Contexts-Footnote-37421272
Ref: SSL Contexts-Footnote-47421364
Ref: SSL Contexts-Footnote-57421522
Ref: SSL Contexts-Footnote-67421613
Ref: SSL Contexts-Footnote-77421705
Ref: SSL Contexts-Footnote-87421793
Ref: SSL Contexts-Footnote-97421858
Ref: SSL Contexts-Footnote-107421907
Ref: SSL Contexts-Footnote-117421986
Ref: SSL Contexts-Footnote-127422036
Ref: SSL Contexts-Footnote-137422113
Node: Certificates7422190
Ref: library/ssl certificates7422323
Ref: 27027422323
Ref: library/ssl ssl-certificates7422323
Ref: 26fc7422323
Ref: Certificates-Footnote-17424660
Node: Certificate chains7424709
Ref: library/ssl certificate-chains7424800
Ref: 27037424800
Node: CA certificates7426067
Ref: library/ssl ca-certificates7426195
Ref: 27047426195
Node: Combined key and certificate7426781
Ref: library/ssl combined-key-and-certificate7426915
Ref: 27057426915
Node: Self-signed certificates7427561
Ref: library/ssl self-signed-certificates7427671
Ref: 27067427671
Node: Examples<16>7429369
Ref: library/ssl examples7429519
Ref: 27077429519
Node: Testing for SSL support7429648
Ref: library/ssl testing-for-ssl-support7429750
Ref: 27087429750
Node: Client-side operation7430064
Ref: library/ssl client-side-operation7430196
Ref: 27097430196
Node: Server-side operation7434938
Ref: library/ssl server-side-operation7435038
Ref: 270a7435038
Node: Notes on non-blocking sockets7437048
Ref: library/ssl notes-on-non-blocking-sockets7437207
Ref: 270b7437207
Ref: library/ssl ssl-nonblocking7437207
Ref: 26b67437207
Node: Memory BIO Support<2>7440085
Ref: library/ssl memory-bio-support7440243
Ref: 270d7440243
Ref: library/ssl ssl SSLObject7441353
Ref: 3e87441353
Ref: library/ssl ssl MemoryBIO7445104
Ref: 7547445104
Ref: library/ssl ssl MemoryBIO pending7445233
Ref: 270e7445233
Ref: library/ssl ssl MemoryBIO eof7445329
Ref: 270f7445329
Ref: library/ssl ssl MemoryBIO read7445456
Ref: 27107445456
Ref: library/ssl ssl MemoryBIO write7445620
Ref: 27117445620
Ref: library/ssl ssl MemoryBIO write_eof7445908
Ref: 27127445908
Node: SSL session7446206
Ref: library/ssl ssl-session7446358
Ref: 27137446358
Ref: library/ssl ssl SSLSession7446422
Ref: 5907446422
Ref: library/ssl ssl SSLSession id7446500
Ref: 27147446500
Ref: library/ssl ssl SSLSession time7446521
Ref: 27157446521
Ref: library/ssl ssl SSLSession timeout7446544
Ref: 27167446544
Ref: library/ssl ssl SSLSession ticket_lifetime_hint7446570
Ref: 27177446570
Ref: library/ssl ssl SSLSession has_ticket7446609
Ref: 27187446609
Node: Security considerations7446638
Ref: library/ssl security-considerations7446776
Ref: 27197446776
Ref: library/ssl ssl-security7446776
Ref: 25b37446776
Node: Best defaults7446914
Ref: library/ssl best-defaults7447011
Ref: 271a7447011
Node: Manual settings7448172
Ref: library/ssl manual-settings7448294
Ref: 271b7448294
Node: Verifying certificates7448427
Ref: library/ssl verifying-certificates7448527
Ref: 271c7448527
Node: Protocol versions7449781
Ref: library/ssl protocol-versions7449906
Ref: 271d7449906
Node: Cipher selection7450707
Ref: library/ssl cipher-selection7450801
Ref: 271e7450801
Ref: Cipher selection-Footnote-17451457
Node: Multi-processing7451542
Ref: library/ssl multi-processing7451642
Ref: 271f7451642
Node: TLS 1 37452197
Ref: library/ssl ssl-tlsv1-37452340
Ref: 3e67452340
Ref: library/ssl tls-1-37452340
Ref: 27207452340
Node: LibreSSL support7453509
Ref: library/ssl libressl-support7453620
Ref: 27217453620
Ref: library/ssl ssl-libressl7453620
Ref: 27227453620
Ref: LibreSSL support-Footnote-17455243
Ref: LibreSSL support-Footnote-27455309
Ref: LibreSSL support-Footnote-37455358
Ref: LibreSSL support-Footnote-47455407
Ref: LibreSSL support-Footnote-57455456
Ref: LibreSSL support-Footnote-67455505
Ref: LibreSSL support-Footnote-77455554
Ref: LibreSSL support-Footnote-87455630
Ref: LibreSSL support-Footnote-97455679
Node: select --- Waiting for I/O completion7455737
Ref: library/select doc7455953
Ref: 27237455953
Ref: library/select module-select7455953
Ref: e67455953
Ref: library/select select-waiting-for-i-o-completion7455953
Ref: 27247455953
Ref: library/select select error7456963
Ref: 99b7456963
Ref: library/select select devpoll7457138
Ref: 8b07457138
Ref: library/select select epoll7457840
Ref: 8ae7457840
Ref: library/select select poll7459297
Ref: 270c7459297
Ref: library/select select kqueue7459614
Ref: 27287459614
Ref: library/select select kevent7459937
Ref: 272a7459937
Ref: library/select select select7460212
Ref: 6787460212
Ref: library/select select PIPE_BUF7462468
Ref: b8b7462468
Ref: select --- Waiting for I/O completion-Footnote-17463159
Ref: select --- Waiting for I/O completion-Footnote-27463208
Node: /dev/poll Polling Objects7463257
Ref: library/select dev-poll-polling-objects7463409
Ref: 272c7463409
Ref: library/select devpoll-objects7463409
Ref: 27257463409
Ref: library/select select devpoll close7463763
Ref: 8b27463763
Ref: library/select select devpoll closed7463878
Ref: 8b37463878
Ref: library/select select devpoll fileno7463980
Ref: 8b17463980
Ref: library/select select devpoll register7464104
Ref: 272d7464104
Ref: library/select select devpoll modify7465093
Ref: 272e7465093
Ref: library/select select devpoll unregister7465307
Ref: 272f7465307
Ref: library/select select devpoll poll7465670
Ref: 6747465670
Ref: /dev/poll Polling Objects-Footnote-17466810
Node: Edge and Level Trigger Polling epoll Objects7466859
Ref: library/select edge-and-level-trigger-polling-epoll-objects7467035
Ref: 27307467035
Ref: library/select epoll-objects7467035
Ref: 27267467035
Ref: library/select select epoll close7469901
Ref: 8af7469901
Ref: library/select select epoll closed7469996
Ref: 27317469996
Ref: library/select select epoll fileno7470070
Ref: 27327470070
Ref: library/select select epoll fromfd7470164
Ref: 27337470164
Ref: library/select select epoll register7470260
Ref: 27347470260
Ref: library/select select epoll modify7470366
Ref: 27357470366
Ref: library/select select epoll unregister7470457
Ref: 27367470457
Ref: library/select select epoll poll7470563
Ref: 6757470563
Ref: Edge and Level Trigger Polling epoll Objects-Footnote-17470962
Node: Polling Objects7471011
Ref: library/select poll-objects7471176
Ref: 27277471176
Ref: library/select polling-objects7471176
Ref: 27377471176
Ref: library/select select poll register7471743
Ref: 27387471743
Ref: library/select select poll modify7473726
Ref: 27397473726
Ref: library/select select poll unregister7474033
Ref: 273a7474033
Ref: library/select select poll poll7474428
Ref: 6777474428
Ref: Polling Objects-Footnote-17475571
Node: Kqueue Objects7475620
Ref: library/select id17475755
Ref: 273b7475755
Ref: library/select kqueue-objects7475755
Ref: 27297475755
Ref: library/select select kqueue close7475804
Ref: 273c7475804
Ref: library/select select kqueue closed7475901
Ref: 273d7475901
Ref: library/select select kqueue fileno7475977
Ref: 273e7475977
Ref: library/select select kqueue fromfd7476072
Ref: 273f7476072
Ref: library/select select kqueue control7476169
Ref: 6767476169
Ref: Kqueue Objects-Footnote-17476817
Node: Kevent Objects7476866
Ref: library/select id27476977
Ref: 27407476977
Ref: library/select kevent-objects7476977
Ref: 272b7476977
Ref: library/select select kevent ident7477092
Ref: 27417477092
Ref: library/select select kevent filter7477391
Ref: 27427477391
Ref: library/select select kevent flags7479170
Ref: 27437479170
Ref: library/select select kevent fflags7480828
Ref: 27447480828
Ref: library/select select kevent data7484570
Ref: 27457484570
Ref: library/select select kevent udata7484623
Ref: 27467484623
Node: selectors --- High-level I/O multiplexing7484675
Ref: library/selectors doc7484889
Ref: 27477484889
Ref: library/selectors module-selectors7484889
Ref: e77484889
Ref: library/selectors selectors-high-level-i-o-multiplexing7484889
Ref: 27487484889
Ref: selectors --- High-level I/O multiplexing-Footnote-17485233
Node: 簡介<9>7485301
Ref: library/selectors introduction7485407
Ref: 27497485407
Node: Classes<3>7486556
Ref: library/selectors classes7486683
Ref: 274c7486683
Ref: library/selectors selectors SelectorKey7487462
Ref: 274d7487462
Ref: library/selectors selectors SelectorKey fileobj7487741
Ref: 274e7487741
Ref: library/selectors selectors SelectorKey fd7487802
Ref: 274f7487802
Ref: library/selectors selectors SelectorKey events7487862
Ref: 27507487862
Ref: library/selectors selectors SelectorKey data7487950
Ref: 27517487950
Ref: library/selectors selectors BaseSelector7488113
Ref: 274a7488113
Ref: library/selectors selectors BaseSelector register7488790
Ref: 27527488790
Ref: library/selectors selectors BaseSelector unregister7489450
Ref: 27537489450
Ref: library/selectors selectors BaseSelector modify7490076
Ref: 4507490076
Ref: library/selectors selectors BaseSelector select7490682
Ref: 27547490682
Ref: library/selectors selectors BaseSelector close7491980
Ref: 27557491980
Ref: library/selectors selectors BaseSelector get_key7492204
Ref: 27567492204
Ref: library/selectors selectors BaseSelector get_map7492497
Ref: 27577492497
Ref: library/selectors selectors DefaultSelector7492772
Ref: 274b7492772
Ref: library/selectors selectors SelectSelector7492981
Ref: 26497492981
Ref: library/selectors selectors PollSelector7493069
Ref: 4527493069
Ref: library/selectors selectors EpollSelector7493154
Ref: 4517493154
Ref: library/selectors selectors EpollSelector fileno7493240
Ref: 27587493240
Ref: library/selectors selectors DevpollSelector7493386
Ref: 4537493386
Ref: library/selectors selectors DevpollSelector fileno7493476
Ref: 27597493476
Ref: library/selectors selectors KqueueSelector7493648
Ref: 264c7493648
Ref: library/selectors selectors KqueueSelector fileno7493737
Ref: 275a7493737
Ref: Classes<3>-Footnote-17493921
Node: Examples<17>7493970
Ref: library/selectors examples7494079
Ref: 275b7494079
Node: asyncore --- Asynchronous socket handler7495106
Ref: library/asyncore doc7495340
Ref: 275c7495340
Ref: library/asyncore asyncore-asynchronous-socket-handler7495340
Ref: 275d7495340
Ref: library/asyncore module-asyncore7495340
Ref: b7495340
Ref: library/asyncore asyncore loop7497623
Ref: 275e7497623
Ref: library/asyncore asyncore dispatcher7498651
Ref: bc87498651
Ref: library/asyncore asyncore dispatcher handle_read7500566
Ref: 27617500566
Ref: library/asyncore asyncore dispatcher handle_write7500733
Ref: 27627500733
Ref: library/asyncore asyncore dispatcher handle_expt7501115
Ref: 27637501115
Ref: library/asyncore asyncore dispatcher handle_connect7501333
Ref: 27647501333
Ref: library/asyncore asyncore dispatcher handle_close7501582
Ref: 27657501582
Ref: library/asyncore asyncore dispatcher handle_error7501667
Ref: 27667501667
Ref: library/asyncore asyncore dispatcher handle_accept7501840
Ref: bca7501840
Ref: library/asyncore asyncore dispatcher handle_accepted7502216
Ref: bc97502216
Ref: library/asyncore asyncore dispatcher readable7502708
Ref: 275f7502708
Ref: library/asyncore asyncore dispatcher writable7503066
Ref: 27607503066
Ref: library/asyncore asyncore dispatcher create_socket7503579
Ref: 27687503579
Ref: library/asyncore asyncore dispatcher connect7503965
Ref: 27677503965
Ref: library/asyncore asyncore dispatcher send7504172
Ref: 27697504172
Ref: library/asyncore asyncore dispatcher recv7504270
Ref: 276a7504270
Ref: library/asyncore asyncore dispatcher listen7504723
Ref: 276b7504723
Ref: library/asyncore asyncore dispatcher bind7505000
Ref: 276c7505000
Ref: library/asyncore asyncore dispatcher accept7505445
Ref: bcb7505445
Ref: library/asyncore asyncore dispatcher close7506093
Ref: 276d7506093
Ref: library/asyncore asyncore dispatcher_with_send7506387
Ref: 276e7506387
Ref: library/asyncore asyncore file_dispatcher7506619
Ref: 276f7506619
Ref: library/asyncore asyncore file_wrapper7507050
Ref: 27707507050
Ref: asyncore --- Asynchronous socket handler-Footnote-17507567
Node: asyncore Example basic HTTP client7507634
Ref: library/asyncore asyncore-example-17507788
Ref: 27717507788
Ref: library/asyncore asyncore-example-basic-http-client7507788
Ref: 27727507788
Node: asyncore Example basic echo server7508798
Ref: library/asyncore asyncore-example-27508952
Ref: 27737508952
Ref: library/asyncore asyncore-example-basic-echo-server7508952
Ref: 27747508952
Node: asynchat --- Asynchronous socket command/response handler7509879
Ref: library/asynchat doc7510119
Ref: 27757510119
Ref: library/asynchat asynchat-asynchronous-socket-command-response-handler7510119
Ref: 27767510119
Ref: library/asynchat module-asynchat7510119
Ref: 97510119
Ref: library/asynchat asynchat async_chat7511323
Ref: 8ba7511323
Ref: library/asynchat asynchat async_chat ac_in_buffer_size7512239
Ref: 27797512239
Ref: library/asynchat asynchat async_chat ac_out_buffer_size7512341
Ref: 277a7512341
Ref: library/asynchat asynchat async_chat close_when_done7513536
Ref: 277c7513536
Ref: library/asynchat asynchat async_chat collect_incoming_data7513722
Ref: 27777513722
Ref: library/asynchat asynchat async_chat discard_buffers7513960
Ref: 277d7513960
Ref: library/asynchat asynchat async_chat found_terminator7514133
Ref: 27787514133
Ref: library/asynchat asynchat async_chat get_terminator7514488
Ref: 277e7514488
Ref: library/asynchat asynchat async_chat push7514590
Ref: 277f7514590
Ref: library/asynchat asynchat async_chat push_with_producer7514933
Ref: 27807514933
Ref: library/asynchat asynchat async_chat set_terminator7515288
Ref: 277b7515288
Ref: asynchat --- Asynchronous socket command/response handler-Footnote-17516379
Node: asynchat Example7516446
Ref: library/asynchat asynchat-example7516556
Ref: 27817516556
Ref: library/asynchat id17516556
Ref: 27827516556
Node: signal --- Set handlers for asynchronous events7518905
Ref: library/signal doc7519140
Ref: 27837519140
Ref: library/signal module-signal7519140
Ref: eb7519140
Ref: library/signal signal-set-handlers-for-asynchronous-events7519140
Ref: 27847519140
Node: General rules7519502
Ref: library/signal general-rules7519626
Ref: 27857519626
Node: Execution of Python signal handlers7520442
Ref: library/signal execution-of-python-signal-handlers7520555
Ref: 27887520555
Node: Signals and threads7521714
Ref: library/signal id17521827
Ref: 278c7521827
Ref: library/signal signals-and-threads7521827
Ref: 278d7521827
Node: Module contents<2>7522253
Ref: library/signal module-contents7522396
Ref: 278e7522396
Ref: library/signal signal SIG_DFL7522900
Ref: 24d97522900
Ref: library/signal signal SIG_IGN7523232
Ref: 24da7523232
Ref: library/signal signal SIGABRT7523353
Ref: 27937523353
Ref: library/signal signal SIGALRM7523419
Ref: 27947523419
Ref: library/signal signal SIGBREAK7523524
Ref: 27957523524
Ref: library/signal signal SIGBUS7523639
Ref: 27967523639
Ref: library/signal signal SIGCHLD7523740
Ref: 27877523740
Ref: library/signal signal SIGCLD7523848
Ref: 27977523848
Ref: library/signal signal SIGCONT7523909
Ref: 1fcc7523909
Ref: library/signal signal SIGFPE7524028
Ref: 278a7524028
Ref: library/signal signal SIGHUP7524265
Ref: 27987524265
Ref: library/signal signal SIGILL7524413
Ref: 27997524413
Ref: library/signal signal SIGINT7524465
Ref: 24d87524465
Ref: library/signal signal SIGKILL7524595
Ref: 279a7524595
Ref: library/signal signal SIGPIPE7524727
Ref: 27867524727
Ref: library/signal signal SIGSEGV7524888
Ref: 278b7524888
Ref: library/signal signal SIGTERM7524966
Ref: 25747524966
Ref: library/signal signal SIGUSR17525018
Ref: 279b7525018
Ref: library/signal signal SIGUSR27525112
Ref: 279c7525112
Ref: library/signal signal SIGWINCH7525206
Ref: 279d7525206
Ref: library/signal signal CTRL_C_EVENT7525863
Ref: 1fa87525863
Ref: library/signal signal CTRL_BREAK_EVENT7526090
Ref: 1fa97526090
Ref: library/signal signal NSIG7526325
Ref: 279e7526325
Ref: library/signal signal ITIMER_REAL7526409
Ref: 279f7526409
Ref: library/signal signal ITIMER_VIRTUAL7526541
Ref: 27a07526541
Ref: library/signal signal ITIMER_PROF7526687
Ref: 27a17526687
Ref: library/signal signal SIG_BLOCK7527026
Ref: 278f7527026
Ref: library/signal signal SIG_UNBLOCK7527206
Ref: 27907527206
Ref: library/signal signal SIG_SETMASK7527395
Ref: 27917527395
Ref: library/signal signal ItimerError7527643
Ref: 27a27527643
Ref: library/signal signal alarm7528161
Ref: 27a57528161
Ref: library/signal signal getsignal7528803
Ref: 27927528803
Ref: library/signal signal strsignal7529373
Ref: 10347529373
Ref: library/signal signal valid_signals7529619
Ref: 27a67529619
Ref: library/signal signal pause7529858
Ref: 27a77529858
Ref: library/signal signal raise_signal7530243
Ref: 27a87530243
Ref: library/signal signal pthread_kill7530372
Ref: a7f7530372
Ref: library/signal signal pthread_sigmask7531568
Ref: a7e7531568
Ref: library/signal signal setitimer7532984
Ref: 27a37532984
Ref: library/signal signal getitimer7534001
Ref: 27a47534001
Ref: library/signal signal set_wakeup_fd7534159
Ref: 3d37534159
Ref: library/signal signal siginterrupt7536296
Ref: a837536296
Ref: library/signal signal signal7536898
Ref: a827536898
Ref: library/signal signal sigpending7538358
Ref: a807538358
Ref: library/signal signal sigwait7538813
Ref: a817538813
Ref: library/signal signal sigwaitinfo7539387
Ref: 6847539387
Ref: library/signal signal sigtimedwait7540638
Ref: 6837540638
Ref: Module contents<2>-Footnote-17541394
Ref: Module contents<2>-Footnote-27541443
Node: Example<9>7541492
Ref: library/signal example7541637
Ref: 27a97541637
Ref: library/signal signal-example7541637
Ref: 27aa7541637
Node: Note on SIGPIPE7542536
Ref: library/signal note-on-sigpipe7542654
Ref: 27ab7542654
Node: mmap --- Memory-mapped file support7544068
Ref: library/mmap doc7544237
Ref: 27ac7544237
Ref: library/mmap mmap-memory-mapped-file-support7544237
Ref: 27ad7544237
Ref: library/mmap module-mmap7544237
Ref: b47544237
Ref: library/mmap mmap mmap7546666
Ref: 1ed7546666
Ref: library/mmap mmap mmap close7551681
Ref: 27ae7551681
Ref: library/mmap mmap mmap closed7551898
Ref: 27af7551898
Ref: library/mmap mmap mmap find7551997
Ref: 27b07551997
Ref: library/mmap mmap mmap flush7552424
Ref: 2c47552424
Ref: library/mmap mmap mmap madvise7553310
Ref: 1ee7553310
Ref: library/mmap mmap mmap move7553880
Ref: 27b27553880
Ref: library/mmap mmap mmap read7554164
Ref: a277554164
Ref: library/mmap mmap mmap read_byte7554613
Ref: 27b37554613
Ref: library/mmap mmap mmap readline7554767
Ref: 27b47554767
Ref: library/mmap mmap mmap resize7554913
Ref: 27b57554913
Ref: library/mmap mmap mmap rfind7555167
Ref: 27b67555167
Ref: library/mmap mmap mmap seek7555596
Ref: 27b77555596
Ref: library/mmap mmap mmap size7555988
Ref: 27b87555988
Ref: library/mmap mmap mmap tell7556133
Ref: 27b97556133
Ref: library/mmap mmap mmap write7556226
Ref: 27ba7556226
Ref: library/mmap mmap mmap write_byte7556911
Ref: 27bb7556911
Node: MADV_* Constants7557263
Ref: library/mmap madv-constants7557351
Ref: 27bc7557351
Ref: library/mmap madvise-constants7557351
Ref: 27b17557351
Ref: library/mmap mmap MADV_NORMAL7557404
Ref: 27bd7557404
Ref: library/mmap mmap MADV_RANDOM7557431
Ref: 27be7557431
Ref: library/mmap mmap MADV_SEQUENTIAL7557458
Ref: 27bf7557458
Ref: library/mmap mmap MADV_WILLNEED7557489
Ref: 27c07557489
Ref: library/mmap mmap MADV_DONTNEED7557518
Ref: 27c17557518
Ref: library/mmap mmap MADV_REMOVE7557547
Ref: 27c27557547
Ref: library/mmap mmap MADV_DONTFORK7557574
Ref: 27c37557574
Ref: library/mmap mmap MADV_DOFORK7557603
Ref: 27c47557603
Ref: library/mmap mmap MADV_HWPOISON7557630
Ref: 27c57557630
Ref: library/mmap mmap MADV_MERGEABLE7557659
Ref: 27c67557659
Ref: library/mmap mmap MADV_UNMERGEABLE7557689
Ref: 27c77557689
Ref: library/mmap mmap MADV_SOFT_OFFLINE7557721
Ref: 27c87557721
Ref: library/mmap mmap MADV_HUGEPAGE7557754
Ref: 27c97557754
Ref: library/mmap mmap MADV_NOHUGEPAGE7557783
Ref: 27ca7557783
Ref: library/mmap mmap MADV_DONTDUMP7557814
Ref: 27cb7557814
Ref: library/mmap mmap MADV_DODUMP7557843
Ref: 27cc7557843
Ref: library/mmap mmap MADV_FREE7557870
Ref: 27cd7557870
Ref: library/mmap mmap MADV_NOSYNC7557895
Ref: 27ce7557895
Ref: library/mmap mmap MADV_AUTOSYNC7557922
Ref: 27cf7557922
Ref: library/mmap mmap MADV_NOCORE7557951
Ref: 27d07557951
Ref: library/mmap mmap MADV_CORE7557978
Ref: 27d17557978
Ref: library/mmap mmap MADV_PROTECT7558003
Ref: 27d27558003
Node: Internet Data Handling7558236
Ref: library/netdata doc7558427
Ref: 27d37558427
Ref: library/netdata internet-data-handling7558427
Ref: 27d47558427
Ref: library/netdata netdata7558427
Ref: 27d57558427
Node: email --- An email and MIME handling package7559442
Ref: library/email doc7559587
Ref: 27d67559587
Ref: library/email email-an-email-and-mime-handling-package7559587
Ref: 27d77559587
Ref: library/email module-email7559587
Ref: 697559587
Ref: email --- An email and MIME handling package-Footnote-17566330
Ref: email --- An email and MIME handling package-Footnote-27566403
Ref: email --- An email and MIME handling package-Footnote-37566452
Ref: email --- An email and MIME handling package-Footnote-47566501
Ref: email --- An email and MIME handling package-Footnote-57566550
Ref: email --- An email and MIME handling package-Footnote-67566599
Ref: email --- An email and MIME handling package-Footnote-77566648
Ref: email --- An email and MIME handling package-Footnote-87566697
Ref: email --- An email and MIME handling package-Footnote-97566746
Node: email message Representing an email message7566795
Ref: library/email message doc7566963
Ref: 27d87566963
Ref: library/email message email-message-representing-an-email-message7566963
Ref: 27d97566963
Ref: library/email message module-email message7566963
Ref: 727566963
Ref: library/email message email message EmailMessage7569449
Ref: 5477569449
Ref: library/email message email message EmailMessage as_string7569931
Ref: 27dc7569931
Ref: library/email message email message EmailMessage __str__7571758
Ref: 27dd7571758
Ref: library/email message email message EmailMessage as_bytes7572214
Ref: 27de7572214
Ref: library/email message email message EmailMessage __bytes__7573382
Ref: 27df7573382
Ref: library/email message email message EmailMessage is_multipart7573564
Ref: 27e07573564
Ref: library/email message email message EmailMessage set_unixfrom7574251
Ref: 27e17574251
Ref: library/email message email message EmailMessage get_unixfrom7574479
Ref: 27e37574479
Ref: library/email message email message EmailMessage __len__7575617
Ref: 27e57575617
Ref: library/email message email message EmailMessage __contains__7575721
Ref: 27e67575721
Ref: library/email message email message EmailMessage __getitem__7576117
Ref: 27e77576117
Ref: library/email message email message EmailMessage __setitem__7576840
Ref: 27ea7576840
Ref: library/email message email message EmailMessage __delitem__7577879
Ref: 27eb7577879
Ref: library/email message email message EmailMessage keys7578111
Ref: 27e47578111
Ref: library/email message email message EmailMessage values7578211
Ref: 27ec7578211
Ref: library/email message email message EmailMessage items7578307
Ref: 27ed7578307
Ref: library/email message email message EmailMessage get7578444
Ref: 27ee7578444
Ref: library/email message email message EmailMessage get_all7578799
Ref: 27e87578799
Ref: library/email message email message EmailMessage add_header7579042
Ref: 27ef7579042
Ref: library/email message email message EmailMessage replace_header7581012
Ref: 27f07581012
Ref: library/email message email message EmailMessage get_content_type7581324
Ref: 27f17581324
Ref: library/email message email message EmailMessage get_content_maintype7582214
Ref: 27f37582214
Ref: library/email message email message EmailMessage get_content_subtype7582426
Ref: 27f47582426
Ref: library/email message email message EmailMessage get_default_type7582625
Ref: 27f27582625
Ref: library/email message email message EmailMessage set_default_type7582951
Ref: 27f57582951
Ref: library/email message email message EmailMessage set_param7583399
Ref: 27f67583399
Ref: library/email message email message EmailMessage del_param7585010
Ref: 27f77585010
Ref: library/email message email message EmailMessage get_filename7585467
Ref: 27f87585467
Ref: library/email message email message EmailMessage get_boundary7586012
Ref: 27fa7586012
Ref: library/email message email message EmailMessage set_boundary7586382
Ref: 27fb7586382
Ref: library/email message email message EmailMessage get_content_charset7587056
Ref: 27fd7587056
Ref: library/email message email message EmailMessage get_charsets7587364
Ref: 27fe7587364
Ref: library/email message email message EmailMessage is_attachment7588063
Ref: 27ff7588063
Ref: library/email message email message EmailMessage get_content_disposition7588417
Ref: 28017588417
Ref: library/email message email message EmailMessage walk7588896
Ref: 28027588896
Ref: library/email message email message EmailMessage get_body7590915
Ref: 28037590915
Ref: library/email message email message EmailMessage iter_attachments7593051
Ref: 28047593051
Ref: library/email message email message EmailMessage iter_parts7594027
Ref: 28057594027
Ref: library/email message email message EmailMessage get_content7594246
Ref: 28067594246
Ref: library/email message email message EmailMessage set_content7594662
Ref: 28087594662
Ref: library/email message email message EmailMessage make_related7595078
Ref: 280a7595078
Ref: library/email message email message EmailMessage make_alternative7595572
Ref: 280b7595572
Ref: library/email message email message EmailMessage make_mixed7596097
Ref: 280c7596097
Ref: library/email message email message EmailMessage add_related7596642
Ref: 280d7596642
Ref: library/email message email message EmailMessage add_alternative7597405
Ref: 280f7597405
Ref: library/email message email message EmailMessage add_attachment7598101
Ref: 28107598101
Ref: library/email message email message EmailMessage clear7599092
Ref: 28117599092
Ref: library/email message email message EmailMessage clear_content7599179
Ref: 28127599179
Ref: library/email message email message EmailMessage preamble7599445
Ref: 28137599445
Ref: library/email message email message EmailMessage epilogue7600704
Ref: 28147600704
Ref: library/email message email message EmailMessage defects7601047
Ref: 28157601047
Ref: library/email message email message MIMEPart7601286
Ref: 8487601286
Ref: email message Representing an email message-Footnote-17601653
Ref: email message Representing an email message-Footnote-27601725
Ref: email message Representing an email message-Footnote-37601925
Ref: email message Representing an email message-Footnote-47601974
Ref: email message Representing an email message-Footnote-57602023
Ref: email message Representing an email message-Footnote-67602072
Ref: email message Representing an email message-Footnote-77602121
Ref: email message Representing an email message-Footnote-87602170
Ref: email message Representing an email message-Footnote-97602219
Ref: email message Representing an email message-Footnote-107602268
Ref: email message Representing an email message-Footnote-117602318
Ref: email message Representing an email message-Footnote-127602368
Ref: email message Representing an email message-Footnote-137602418
Node: email parser Parsing email messages7602468
Ref: library/email parser doc7602686
Ref: 28167602686
Ref: library/email parser email-parser-parsing-email-messages7602686
Ref: 28177602686
Ref: library/email parser module-email parser7602686
Ref: 747602686
Ref: email parser Parsing email messages-Footnote-17605071
Node: FeedParser API7605142
Ref: library/email parser feedparser-api7605247
Ref: 28197605247
Ref: library/email parser email parser BytesFeedParser7606540
Ref: b4e7606540
Ref: library/email parser email parser BytesFeedParser feed7607715
Ref: 281a7607715
Ref: library/email parser email parser BytesFeedParser close7608156
Ref: 281b7608156
Ref: library/email parser email parser FeedParser7608402
Ref: 28187608402
Node: Parser API7608852
Ref: library/email parser parser-api7608982
Ref: 281c7608982
Ref: library/email parser email parser BytesParser7609710
Ref: b4f7609710
Ref: library/email parser email parser BytesParser parse7610355
Ref: 281d7610355
Ref: library/email parser email parser BytesParser parsebytes7611401
Ref: 281e7611401
Ref: library/email parser email parser BytesHeaderParser7611911
Ref: a017611911
Ref: library/email parser email parser Parser7612128
Ref: b1d7612128
Ref: library/email parser email parser Parser parse7612451
Ref: 281f7612451
Ref: library/email parser email parser Parser parsestr7612895
Ref: 28207612895
Ref: library/email parser email parser HeaderParser7613330
Ref: a027613330
Ref: library/email parser email message_from_bytes7613728
Ref: b4c7613728
Ref: library/email parser email message_from_binary_file7614182
Ref: b4d7614182
Ref: library/email parser email message_from_string7614642
Ref: 28217614642
Ref: library/email parser email message_from_file7615026
Ref: 28227615026
Ref: Parser API-Footnote-17615731
Ref: Parser API-Footnote-27615780
Node: Additional notes7615829
Ref: library/email parser additional-notes7615936
Ref: 28237615936
Node: email generator Generating MIME documents7617478
Ref: library/email generator doc7617680
Ref: 28247617680
Ref: library/email generator email-generator-generating-mime-documents7617680
Ref: 28257617680
Ref: library/email generator module-email generator7617680
Ref: 6e7617680
Ref: library/email generator email generator BytesGenerator7619799
Ref: b527619799
Ref: library/email generator email generator BytesGenerator flatten7621686
Ref: 28267621686
Ref: library/email generator email generator BytesGenerator clone7623514
Ref: 28297623514
Ref: library/email generator email generator BytesGenerator write7623718
Ref: 28277623718
Ref: library/email generator email generator Generator7624771
Ref: b517624771
Ref: library/email generator email generator Generator flatten7626600
Ref: 282a7626600
Ref: library/email generator email generator Generator clone7628357
Ref: 282c7628357
Ref: library/email generator email generator Generator write7628548
Ref: 282b7628548
Ref: library/email generator email generator DecodedGenerator7629463
Ref: 5437629463
Ref: email generator Generating MIME documents-Footnote-17630890
Ref: email generator Generating MIME documents-Footnote-27630964
Ref: email generator Generating MIME documents-Footnote-37631457
Ref: email generator Generating MIME documents-Footnote-47631509
Ref: email generator Generating MIME documents-Footnote-57631558
Ref: email generator Generating MIME documents-Footnote-67631610
Node: email policy Policy Objects7631659
Ref: library/email policy doc7631867
Ref: 282d7631867
Ref: library/email policy email-policy-policy-objects7631867
Ref: 282e7631867
Ref: library/email policy module-email policy7631867
Ref: 757631867
Ref: library/email policy email policy Policy7637820
Ref: 9f97637820
Ref: library/email policy email policy Policy max_line_length7638641
Ref: 282f7638641
Ref: library/email policy email policy Policy linesep7638944
Ref: 28307638944
Ref: library/email policy email policy Policy cte_type7639210
Ref: 28287639210
Ref: library/email policy email policy Policy raise_on_defect7640314
Ref: 28327640314
Ref: library/email policy email policy Policy mangle_from_7640555
Ref: 6d57640555
Ref: library/email policy email policy Policy message_factory7640903
Ref: 5447640903
Ref: library/email policy email policy Policy clone7641335
Ref: 9fb7641335
Ref: library/email policy email policy Policy handle_defect7641815
Ref: 28347641815
Ref: library/email policy email policy Policy register_defect7642300
Ref: 28337642300
Ref: library/email policy email policy Policy header_max_count7642999
Ref: 28357642999
Ref: library/email policy email policy Policy header_source_parse7644067
Ref: 28367644067
Ref: library/email policy email policy Policy header_store_parse7645086
Ref: 28377645086
Ref: library/email policy email policy Policy header_fetch_parse7645853
Ref: 28387645853
Ref: library/email policy email policy Policy fold7646682
Ref: 28397646682
Ref: library/email policy email policy Policy fold_binary7647400
Ref: 28317647400
Ref: library/email policy email policy EmailPolicy7647740
Ref: 9fd7647740
Ref: library/email policy email policy EmailPolicy utf87648569
Ref: 6d77648569
Ref: library/email policy email policy EmailPolicy refold_source7648958
Ref: 283a7648958
Ref: library/email policy email policy EmailPolicy header_factory7649750
Ref: 283b7649750
Ref: library/email policy email policy EmailPolicy content_manager7650358
Ref: 8497650358
Ref: library/email policy email policy EmailPolicy header_max_count7651062
Ref: 283d7651062
Ref: library/email policy email policy EmailPolicy header_source_parse7651274
Ref: 283f7651274
Ref: library/email policy email policy EmailPolicy header_store_parse7651665
Ref: 28407651665
Ref: library/email policy email policy EmailPolicy header_fetch_parse7652152
Ref: 28417652152
Ref: library/email policy email policy EmailPolicy fold7652584
Ref: 28427652584
Ref: library/email policy email policy EmailPolicy fold_binary7653753
Ref: 28437653753
Ref: library/email policy email policy default7654578
Ref: 27db7654578
Ref: library/email policy email policy SMTP7654788
Ref: 28447654788
Ref: library/email policy email policy SMTPUTF87654990
Ref: 28457654990
Ref: library/email policy email policy HTTP7655404
Ref: 28467655404
Ref: library/email policy email policy strict7655596
Ref: 28477655596
Ref: library/email policy email policy Compat327657023
Ref: 9fa7657023
Ref: library/email policy email policy Compat32 mangle_from_7657555
Ref: 28487657555
Ref: library/email policy email policy Compat32 header_source_parse7657740
Ref: 28497657740
Ref: library/email policy email policy Compat32 header_store_parse7658131
Ref: 284a7658131
Ref: library/email policy email policy Compat32 header_fetch_parse7658243
Ref: 284b7658243
Ref: library/email policy email policy Compat32 fold7658491
Ref: 284d7658491
Ref: library/email policy email policy Compat32 fold_binary7658840
Ref: 284e7658840
Ref: library/email policy email policy compat327659376
Ref: 5457659376
Ref: email policy Policy Objects-Footnote-17659579
Ref: email policy Policy Objects-Footnote-27659650
Ref: email policy Policy Objects-Footnote-37659699
Ref: email policy Policy Objects-Footnote-47659748
Ref: email policy Policy Objects-Footnote-57659797
Ref: email policy Policy Objects-Footnote-67659846
Ref: email policy Policy Objects-Footnote-77659895
Ref: email policy Policy Objects-Footnote-87659944
Ref: email policy Policy Objects-Footnote-97660017
Ref: email policy Policy Objects-Footnote-107660066
Ref: email policy Policy Objects-Footnote-117660116
Ref: email policy Policy Objects-Footnote-127660166
Node: email errors Exception and Defect classes7660216
Ref: library/email errors doc7660425
Ref: 284f7660425
Ref: library/email errors email-errors-exception-and-defect-classes7660425
Ref: 28507660425
Ref: library/email errors module-email errors7660425
Ref: 6d7660425
Ref: library/email errors email errors MessageError7660729
Ref: 28517660729
Ref: library/email errors email errors MessageParseError7660967
Ref: 28527660967
Ref: library/email errors email errors HeaderParseError7661240
Ref: 27fc7661240
Ref: library/email errors email errors BoundaryError7661880
Ref: 28537661880
Ref: library/email errors email errors MultipartConversionError7661957
Ref: 28547661957
Ref: email errors Exception and Defect classes-Footnote-17665264
Ref: email errors Exception and Defect classes-Footnote-27665335
Node: email headerregistry Custom Header Objects7665384
Ref: library/email headerregistry doc7665608
Ref: 28577665608
Ref: library/email headerregistry email-headerregistry-custom-header-objects7665608
Ref: 28587665608
Ref: library/email headerregistry module-email headerregistry7665608
Ref: 707665608
Ref: library/email headerregistry email headerregistry BaseHeader7667372
Ref: 27e97667372
Ref: library/email headerregistry email headerregistry BaseHeader name7667686
Ref: 285b7667686
Ref: library/email headerregistry email headerregistry BaseHeader defects7667934
Ref: 285c7667934
Ref: library/email headerregistry email headerregistry BaseHeader max_count7668283
Ref: 283e7668283
Ref: library/email headerregistry email headerregistry BaseHeader fold7668797
Ref: 285d7668797
Ref: library/email headerregistry email headerregistry UnstructuredHeader7670994
Ref: 285a7670994
Ref: library/email headerregistry email headerregistry DateHeader7672070
Ref: 285e7672070
Ref: library/email headerregistry email headerregistry DateHeader datetime7672430
Ref: 285f7672430
Ref: library/email headerregistry email headerregistry AddressHeader7673995
Ref: 28607673995
Ref: library/email headerregistry email headerregistry AddressHeader groups7674280
Ref: 28617674280
Ref: library/email headerregistry email headerregistry AddressHeader addresses7674592
Ref: 28647674592
Ref: library/email headerregistry email headerregistry SingleAddressHeader7675747
Ref: 28667675747
Ref: library/email headerregistry email headerregistry SingleAddressHeader address7675889
Ref: 28677675889
Ref: library/email headerregistry email headerregistry MIMEVersionHeader7676418
Ref: 28687676418
Ref: library/email headerregistry email headerregistry MIMEVersionHeader version7676811
Ref: 28697676811
Ref: library/email headerregistry email headerregistry MIMEVersionHeader major7676935
Ref: 286a7676935
Ref: library/email headerregistry email headerregistry MIMEVersionHeader minor7677009
Ref: 286b7677009
Ref: library/email headerregistry email headerregistry ParameterizedMIMEHeader7677083
Ref: 286c7677083
Ref: library/email headerregistry email headerregistry ParameterizedMIMEHeader params7677467
Ref: 286d7677467
Ref: library/email headerregistry email headerregistry ContentTypeHeader7677561
Ref: 286e7677561
Ref: library/email headerregistry email headerregistry ContentTypeHeader content_type7677713
Ref: 286f7677713
Ref: library/email headerregistry email headerregistry ContentTypeHeader maintype7677816
Ref: 28707677816
Ref: library/email headerregistry email headerregistry ContentTypeHeader subtype7677843
Ref: 28717677843
Ref: library/email headerregistry email headerregistry ContentDispositionHeader7677869
Ref: 28727677869
Ref: library/email headerregistry email headerregistry ContentDispositionHeader content_disposition7678035
Ref: 28737678035
Ref: library/email headerregistry email headerregistry ContentTransferEncoding7678169
Ref: 28747678169
Ref: library/email headerregistry email headerregistry ContentTransferEncoding cte7678285
Ref: 28757678285
Ref: library/email headerregistry email headerregistry HeaderRegistry7678451
Ref: 28597678451
Ref: library/email headerregistry email headerregistry HeaderRegistry map_to_type7680172
Ref: 28767680172
Ref: library/email headerregistry email headerregistry HeaderRegistry __getitem__7680513
Ref: 28777680513
Ref: library/email headerregistry email headerregistry HeaderRegistry __call__7680642
Ref: 28787680642
Ref: library/email headerregistry email headerregistry Address7681290
Ref: 28657681290
Ref: library/email headerregistry email headerregistry Address display_name7682136
Ref: 28797682136
Ref: library/email headerregistry email headerregistry Address username7682359
Ref: 287a7682359
Ref: library/email headerregistry email headerregistry Address domain7682476
Ref: 287b7682476
Ref: library/email headerregistry email headerregistry Address addr_spec7682553
Ref: 287c7682553
Ref: library/email headerregistry email headerregistry Address __str__7682768
Ref: 287d7682768
Ref: library/email headerregistry email headerregistry Group7683213
Ref: 28627683213
Ref: library/email headerregistry email headerregistry Group display_name7683753
Ref: 28637683753
Ref: library/email headerregistry email headerregistry Group addresses7684005
Ref: 287e7684005
Ref: library/email headerregistry email headerregistry Group __str__7684150
Ref: 287f7684150
Ref: email headerregistry Custom Header Objects-Footnote-17684596
Ref: email headerregistry Custom Header Objects-Footnote-27684676
Ref: email headerregistry Custom Header Objects-Footnote-37684748
Ref: email headerregistry Custom Header Objects-Footnote-47684797
Ref: email headerregistry Custom Header Objects-Footnote-57684846
Ref: email headerregistry Custom Header Objects-Footnote-67684895
Ref: email headerregistry Custom Header Objects-Footnote-77684944
Ref: email headerregistry Custom Header Objects-Footnote-87684993
Ref: email headerregistry Custom Header Objects-Footnote-97685042
Ref: email headerregistry Custom Header Objects-Footnote-107685091
Ref: email headerregistry Custom Header Objects-Footnote-117685141
Ref: email headerregistry Custom Header Objects-Footnote-127685191
Ref: email headerregistry Custom Header Objects-Footnote-137685241
Ref: email headerregistry Custom Header Objects-Footnote-147685291
Ref: email headerregistry Custom Header Objects-Footnote-157685341
Ref: email headerregistry Custom Header Objects-Footnote-167685391
Ref: email headerregistry Custom Header Objects-Footnote-177685441
Node: email contentmanager Managing MIME Content7685491
Ref: library/email contentmanager doc7685688
Ref: 28807685688
Ref: library/email contentmanager email-contentmanager-managing-mime-content7685688
Ref: 28817685688
Ref: library/email contentmanager module-email contentmanager7685688
Ref: 6b7685688
Ref: library/email contentmanager email contentmanager ContentManager7685943
Ref: 28827685943
Ref: library/email contentmanager email contentmanager ContentManager get_content7686233
Ref: 28077686233
Ref: library/email contentmanager email contentmanager ContentManager set_content7687093
Ref: 28097687093
Ref: library/email contentmanager email contentmanager ContentManager add_get_handler7688722
Ref: 28847688722
Ref: library/email contentmanager email contentmanager ContentManager add_set_handler7688920
Ref: 28867688920
Ref: email contentmanager Managing MIME Content-Footnote-17689291
Ref: email contentmanager Managing MIME Content-Footnote-27689371
Node: Content Manager Instances7689443
Ref: library/email contentmanager content-manager-instances7689547
Ref: 28887689547
Ref: library/email contentmanager email contentmanager raw_data_manager7689887
Ref: 283c7689887
Ref: library/email contentmanager email contentmanager get_content7690617
Ref: 28857690617
Ref: library/email contentmanager email contentmanager set_content7691222
Ref: 28877691222
Ref: Content Manager Instances-Footnote-17695661
Node: email Examples7695710
Ref: library/email examples doc7695939
Ref: 28897695939
Ref: library/email examples email-examples7695939
Ref: 84a7695939
Ref: library/email examples id17695939
Ref: 288a7695939
Ref: email Examples-Footnote-17710604
Ref: email Examples-Footnote-27710652
Node: email message Message Representing an email message using the compat32 API7710738
Ref: library/email compat32-message doc7710980
Ref: 288b7710980
Ref: library/email compat32-message compat32-message7710980
Ref: 27da7710980
Ref: library/email compat32-message email-message-message-representing-an-email-message-using-the-compat32-api7710980
Ref: 288c7710980
Ref: library/email compat32-message email message Message7713537
Ref: 5467713537
Ref: library/email compat32-message email message Message as_string7714062
Ref: 8447714062
Ref: library/email compat32-message email message Message __str__7716208
Ref: 288d7716208
Ref: library/email compat32-message email message Message as_bytes7716379
Ref: 8457716379
Ref: library/email compat32-message email message Message __bytes__7717939
Ref: 8467717939
Ref: library/email compat32-message email message Message is_multipart7718148
Ref: 28007718148
Ref: library/email compat32-message email message Message set_unixfrom7718826
Ref: 288e7718826
Ref: library/email compat32-message email message Message get_unixfrom7718972
Ref: 288f7718972
Ref: library/email compat32-message email message Message attach7719135
Ref: 280e7719135
Ref: library/email compat32-message email message Message get_payload7719759
Ref: b507719759
Ref: library/email compat32-message email message Message set_payload7722416
Ref: 28907722416
Ref: library/email compat32-message email message Message set_charset7722890
Ref: 28917722890
Ref: library/email compat32-message email message Message get_charset7724655
Ref: 28927724655
Ref: library/email compat32-message email message Message __len__7726113
Ref: 28947726113
Ref: library/email compat32-message email message Message __contains__7726217
Ref: 28957726217
Ref: library/email compat32-message email message Message __getitem__7726593
Ref: 28967726593
Ref: library/email compat32-message email message Message __setitem__7727134
Ref: 28987727134
Ref: library/email compat32-message email message Message __delitem__7727697
Ref: 28997727697
Ref: library/email compat32-message email message Message keys7727929
Ref: 28937727929
Ref: library/email compat32-message email message Message values7728029
Ref: 289a7728029
Ref: library/email compat32-message email message Message items7728125
Ref: 289b7728125
Ref: library/email compat32-message email message Message get7728262
Ref: 289c7728262
Ref: library/email compat32-message email message Message get_all7728592
Ref: 28977728592
Ref: library/email compat32-message email message Message add_header7728835
Ref: 289d7728835
Ref: library/email compat32-message email message Message replace_header7730807
Ref: 289e7730807
Ref: library/email compat32-message email message Message get_content_type7731102
Ref: 289f7731102
Ref: library/email compat32-message email message Message get_content_maintype7731966
Ref: 28a17731966
Ref: library/email compat32-message email message Message get_content_subtype7732178
Ref: 28a27732178
Ref: library/email compat32-message email message Message get_default_type7732377
Ref: 28a07732377
Ref: library/email compat32-message email message Message set_default_type7732703
Ref: 28a37732703
Ref: library/email compat32-message email message Message get_params7732996
Ref: 28a47732996
Ref: library/email compat32-message email message Message get_param7734058
Ref: 28a57734058
Ref: library/email compat32-message email message Message set_param7736066
Ref: 8477736066
Ref: library/email compat32-message email message Message del_param7737330
Ref: 28a77737330
Ref: library/email compat32-message email message Message set_type7737792
Ref: 28a87737792
Ref: library/email compat32-message email message Message get_filename7738671
Ref: 28a97738671
Ref: library/email compat32-message email message Message get_boundary7739216
Ref: 28aa7739216
Ref: library/email compat32-message email message Message set_boundary7739586
Ref: 28ab7739586
Ref: library/email compat32-message email message Message get_content_charset7740407
Ref: 28ac7740407
Ref: library/email compat32-message email message Message get_charsets7740901
Ref: 28ad7740901
Ref: library/email compat32-message email message Message get_content_disposition7741609
Ref: 6d67741609
Ref: library/email compat32-message email message Message walk7741976
Ref: 28ae7741976
Ref: library/email compat32-message email message Message preamble7744102
Ref: 28af7744102
Ref: library/email compat32-message email message Message epilogue7745361
Ref: 28b07745361
Ref: library/email compat32-message email message Message defects7745756
Ref: 28b17745756
Ref: email message Message Representing an email message using the compat32 API-Footnote-17746031
Ref: email message Message Representing an email message using the compat32 API-Footnote-27746080
Ref: email message Message Representing an email message using the compat32 API-Footnote-37746129
Ref: email message Message Representing an email message using the compat32 API-Footnote-47746178
Ref: email message Message Representing an email message using the compat32 API-Footnote-57746227
Ref: email message Message Representing an email message using the compat32 API-Footnote-67746276
Ref: email message Message Representing an email message using the compat32 API-Footnote-77746325
Ref: email message Message Representing an email message using the compat32 API-Footnote-87746374
Ref: email message Message Representing an email message using the compat32 API-Footnote-97746423
Ref: email message Message Representing an email message using the compat32 API-Footnote-107746472
Ref: email message Message Representing an email message using the compat32 API-Footnote-117746522
Ref: email message Message Representing an email message using the compat32 API-Footnote-127746572
Node: email mime Creating email and MIME objects from scratch7746622
Ref: library/email mime doc7746888
Ref: 28b27746888
Ref: library/email mime email-mime-creating-email-and-mime-objects-from-scratch7746888
Ref: 28b37746888
Ref: library/email mime module-email mime7746888
Ref: 737746888
Ref: library/email mime email mime base MIMEBase7748124
Ref: 28b47748124
Ref: library/email mime email mime nonmultipart MIMENonMultipart7749259
Ref: 28557749259
Ref: library/email mime email mime multipart MIMEMultipart7749752
Ref: 28b57749752
Ref: library/email mime email mime application MIMEApplication7751057
Ref: 28b67751057
Ref: library/email mime email mime audio MIMEAudio7752391
Ref: 28b77752391
Ref: library/email mime email mime image MIMEImage7753970
Ref: 28567753970
Ref: library/email mime email mime message MIMEMessage7755560
Ref: 28b87755560
Ref: library/email mime email mime text MIMEText7756236
Ref: 6d87756236
Ref: email mime Creating email and MIME objects from scratch-Footnote-17757848
Node: email header Internationalized headers7757915
Ref: library/email header doc7758148
Ref: 28b97758148
Ref: library/email header email-header-internationalized-headers7758148
Ref: 28ba7758148
Ref: library/email header module-email header7758148
Ref: 6f7758148
Ref: library/email header email header Header7760845
Ref: 284c7760845
Ref: library/email header email header Header append7762718
Ref: 28bb7762718
Ref: library/email header email header Header encode7764058
Ref: 28bc7764058
Ref: library/email header email header Header __str__7765696
Ref: 28bd7765696
Ref: library/email header email header Header __eq__7766182
Ref: 28be7766182
Ref: library/email header email header Header __ne__7766324
Ref: 28bf7766324
Ref: library/email header email header decode_header7766554
Ref: 9fe7766554
Ref: library/email header email header make_header7767208
Ref: 9ff7767208
Ref: email header Internationalized headers-Footnote-17767903
Ref: email header Internationalized headers-Footnote-27767974
Ref: email header Internationalized headers-Footnote-37768023
Ref: email header Internationalized headers-Footnote-47768071
Ref: email header Internationalized headers-Footnote-57768120
Ref: email header Internationalized headers-Footnote-67768169
Ref: email header Internationalized headers-Footnote-77768218
Ref: email header Internationalized headers-Footnote-87768267
Ref: email header Internationalized headers-Footnote-97768316
Ref: email header Internationalized headers-Footnote-107768365
Ref: email header Internationalized headers-Footnote-117768415
Ref: email header Internationalized headers-Footnote-127768465
Ref: email header Internationalized headers-Footnote-137768515
Ref: email header Internationalized headers-Footnote-147768565
Ref: email header Internationalized headers-Footnote-157768615
Node: email charset Representing character sets7768665
Ref: library/email charset doc7768866
Ref: 28c07768866
Ref: library/email charset email-charset-representing-character-sets7768866
Ref: 28c17768866
Ref: library/email charset module-email charset7768866
Ref: 6a7768866
Ref: library/email charset email charset Charset7769677
Ref: 6d97769677
Ref: library/email charset email charset Charset input_charset7771203
Ref: 28c27771203
Ref: library/email charset email charset Charset header_encoding7771456
Ref: 28c37771456
Ref: library/email charset email charset Charset body_encoding7771839
Ref: 28c47771839
Ref: library/email charset email charset Charset output_charset7772113
Ref: 28c57772113
Ref: library/email charset email charset Charset input_codec7772449
Ref: 28c67772449
Ref: library/email charset email charset Charset output_codec7772660
Ref: 28c77772660
Ref: library/email charset email charset Charset get_body_encoding7772969
Ref: 28c87772969
Ref: library/email charset email charset Charset get_output_charset7773692
Ref: 28c97773692
Ref: library/email charset email charset Charset header_encode7773902
Ref: 28ca7773902
Ref: library/email charset email charset Charset header_encode_lines7774116
Ref: 28cb7774116
Ref: library/email charset email charset Charset body_encode7774555
Ref: 28cc7774555
Ref: library/email charset email charset Charset __str__7774893
Ref: 28cd7774893
Ref: library/email charset email charset Charset __eq__7775070
Ref: 28ce7775070
Ref: library/email charset email charset Charset __ne__7775212
Ref: 28cf7775212
Ref: library/email charset email charset add_charset7775512
Ref: 28d07775512
Ref: library/email charset email charset add_alias7776835
Ref: 28d27776835
Ref: library/email charset email charset add_codec7777159
Ref: 28d17777159
Ref: email charset Representing character sets-Footnote-17777551
Node: email encoders Encoders7777623
Ref: library/email encoders doc7777821
Ref: 28d37777821
Ref: library/email encoders email-encoders-encoders7777821
Ref: 28d47777821
Ref: library/email encoders module-email encoders7777821
Ref: 6c7777821
Ref: library/email encoders email encoders encode_quopri7779507
Ref: 28d57779507
Ref: library/email encoders email encoders encode_base647779833
Ref: 28d67779833
Ref: library/email encoders email encoders encode_7or8bit7780227
Ref: 28d77780227
Ref: library/email encoders email encoders encode_noop7780485
Ref: 28d87780485
Ref: email encoders Encoders-Footnote-17780676
Ref: email encoders Encoders-Footnote-27780749
Node: email utils Miscellaneous utilities7780870
Ref: library/email utils doc7781052
Ref: 28d97781052
Ref: library/email utils email-utils-miscellaneous-utilities7781052
Ref: 28da7781052
Ref: library/email utils module-email utils7781052
Ref: 767781052
Ref: library/email utils email utils localtime7781348
Ref: a057781348
Ref: library/email utils email utils make_msgid7782167
Ref: 28db7782167
Ref: library/email utils email utils quote7783053
Ref: 28dc7783053
Ref: library/email utils email utils unquote7783230
Ref: 27f97783230
Ref: library/email utils email utils parseaddr7783498
Ref: 28dd7783498
Ref: library/email utils email utils formataddr7783855
Ref: b1a7783855
Ref: library/email utils email utils getaddresses7784525
Ref: 28de7784525
Ref: library/email utils email utils parsedate7785161
Ref: 28df7785161
Ref: library/email utils email utils parsedate_tz7785788
Ref: 28e07785788
Ref: library/email utils email utils parsedate_to_datetime7786365
Ref: a047786365
Ref: library/email utils email utils mktime_tz7787072
Ref: 28e17787072
Ref: library/email utils email utils formatdate7787307
Ref: 28e27787307
Ref: library/email utils email utils format_datetime7788250
Ref: a037788250
Ref: library/email utils email utils decode_rfc22317788930
Ref: 28e37788930
Ref: library/email utils email utils encode_rfc22317789028
Ref: 28e47789028
Ref: library/email utils email utils collapse_rfc2231_value7789424
Ref: 28a67789424
Ref: library/email utils email utils decode_params7790276
Ref: 28e57790276
Ref: email utils Miscellaneous utilities-Footnote-17790530
Ref: email utils Miscellaneous utilities-Footnote-27790600
Ref: email utils Miscellaneous utilities-Footnote-37790649
Ref: email utils Miscellaneous utilities-Footnote-47790698
Ref: email utils Miscellaneous utilities-Footnote-57790747
Ref: email utils Miscellaneous utilities-Footnote-67790796
Ref: email utils Miscellaneous utilities-Footnote-77791063
Ref: email utils Miscellaneous utilities-Footnote-87791112
Ref: email utils Miscellaneous utilities-Footnote-97791161
Ref: email utils Miscellaneous utilities-Footnote-107791210
Ref: email utils Miscellaneous utilities-Footnote-117791260
Ref: email utils Miscellaneous utilities-Footnote-127791310
Node: email iterators Iterators7791360
Ref: library/email iterators doc7791510
Ref: 28e67791510
Ref: library/email iterators email-iterators-iterators7791510
Ref: 28e77791510
Ref: library/email iterators module-email iterators7791510
Ref: 717791510
Ref: library/email iterators email iterators body_line_iterator7791910
Ref: 28e87791910
Ref: library/email iterators email iterators typed_subpart_iterator7792485
Ref: 28e97792485
Ref: library/email iterators email iterators _structure7793201
Ref: 28ea7793201
Ref: email iterators Iterators-Footnote-17794778
Node: json --- JSON encoder and decoder7794852
Ref: library/json doc7795039
Ref: 28eb7795039
Ref: library/json json-json-encoder-and-decoder7795039
Ref: 28ec7795039
Ref: library/json module-json7795039
Ref: a57795039
Ref: json --- JSON encoder and decoder-Footnote-17799236
Ref: json --- JSON encoder and decoder-Footnote-27799308
Ref: json --- JSON encoder and decoder-Footnote-37799332
Ref: json --- JSON encoder and decoder-Footnote-47799381
Ref: json --- JSON encoder and decoder-Footnote-57799430
Ref: json --- JSON encoder and decoder-Footnote-67799509
Ref: json --- JSON encoder and decoder-Footnote-77799558
Ref: json --- JSON encoder and decoder-Footnote-87799824
Node: Basic Usage7799849
Ref: library/json basic-usage7799960
Ref: 28ee7799960
Ref: library/json json dump7800003
Ref: 6097800003
Ref: library/json json dumps7803499
Ref: 60a7803499
Ref: library/json json load7804324
Ref: 5647804324
Ref: library/json json loads7806900
Ref: 5657806900
Ref: Basic Usage-Footnote-17807809
Node: Encoders and Decoders7807840
Ref: library/json encoders-and-decoders7807969
Ref: 28f17807969
Ref: library/json json JSONDecoder7808032
Ref: 60c7808032
Ref: library/json json-to-py-table7808287
Ref: 28f07808287
Ref: library/json json JSONDecoder decode7811164
Ref: 28f27811164
Ref: library/json json JSONDecoder raw_decode7811422
Ref: 28f37811422
Ref: library/json json JSONEncoder7811792
Ref: 60b7811792
Ref: library/json py-to-json-table7812094
Ref: 28ef7812094
Ref: library/json json JSONEncoder default7816346
Ref: 28f47816346
Ref: library/json json JSONEncoder encode7817041
Ref: 28f57817041
Ref: library/json json JSONEncoder iterencode7817292
Ref: 28f67817292
Node: 例外<2>7817559
Ref: library/json exceptions7817717
Ref: 28f77817717
Ref: library/json json JSONDecodeError7817748
Ref: 70b7817748
Ref: library/json json JSONDecodeError msg7817886
Ref: 28f87817886
Ref: library/json json JSONDecodeError doc7817950
Ref: 28f97817950
Ref: library/json json JSONDecodeError pos7818015
Ref: 28fa7818015
Ref: library/json json JSONDecodeError lineno7818095
Ref: 28fb7818095
Ref: library/json json JSONDecodeError colno7818164
Ref: 28fc7818164
Node: Standard Compliance and Interoperability7818258
Ref: library/json standard-compliance-and-interoperability7818420
Ref: 28fd7818420
Ref: Standard Compliance and Interoperability-Footnote-17819570
Ref: Standard Compliance and Interoperability-Footnote-27819619
Node: Character Encodings7819698
Ref: library/json character-encodings7819833
Ref: 28fe7819833
Node: Infinite and NaN Number Values7821164
Ref: library/json infinite-and-nan-number-values7821339
Ref: 28ff7821339
Node: Repeated Names Within an Object7822127
Ref: library/json repeated-names-within-an-object7822320
Ref: 29007822320
Node: Top-level Non-Object Non-Array Values7822843
Ref: library/json top-level-non-object-non-array-values7823032
Ref: 29017823032
Ref: Top-level Non-Object Non-Array Values-Footnote-17823686
Ref: Top-level Non-Object Non-Array Values-Footnote-27823735
Node: Implementation Limitations7823784
Ref: library/json implementation-limitations7823933
Ref: 29027823933
Node: Command Line Interface<2>7824879
Ref: library/json command-line-interface7825023
Ref: 29037825023
Ref: library/json json-commandline7825023
Ref: 28ed7825023
Ref: library/json module-json tool7825023
Ref: a67825023
Ref: Command Line Interface<2>-Footnote-17825942
Node: Command line options<2>7826010
Ref: library/json command-line-options7826095
Ref: 29057826095
Ref: library/json cmdoption-json-tool-arg-infile7826158
Ref: 29067826158
Ref: library/json cmdoption-json-tool-arg-outfile7826640
Ref: 29077826640
Ref: library/json cmdoption-json-tool-sort-keys7826781
Ref: 29047826781
Ref: library/json cmdoption-json-tool-json-lines7826897
Ref: 29087826897
Ref: library/json cmdoption-json-tool-h7827007
Ref: 29097827007
Node: mailcap --- Mailcap file handling7827079
Ref: library/mailcap doc7827273
Ref: 290a7827273
Ref: library/mailcap mailcap-mailcap-file-handling7827273
Ref: 290b7827273
Ref: library/mailcap module-mailcap7827273
Ref: b07827273
Ref: library/mailcap mailcap findmatch7828240
Ref: 290c7828240
Ref: library/mailcap mailcap getcaps7830323
Ref: 290d7830323
Ref: mailcap --- Mailcap file handling-Footnote-17831161
Ref: mailcap --- Mailcap file handling-Footnote-27831227
Ref: mailcap --- Mailcap file handling-Footnote-37831276
Node: mailbox --- Manipulate mailboxes in various formats7831325
Ref: library/mailbox doc7831527
Ref: 290e7831527
Ref: library/mailbox mailbox-manipulate-mailboxes-in-various-formats7831527
Ref: 290f7831527
Ref: library/mailbox module-mailbox7831527
Ref: af7831527
Ref: mailbox --- Manipulate mailboxes in various formats-Footnote-17832418
Node: Mailbox objects7832484
Ref: library/mailbox id17832611
Ref: 29107832611
Ref: library/mailbox mailbox-objects7832611
Ref: 29117832611
Ref: library/mailbox mailbox Mailbox7832670
Ref: be87832670
Ref: library/mailbox mailbox Mailbox add7835472
Ref: be77835472
Ref: library/mailbox mailbox Mailbox remove7836259
Ref: 29127836259
Ref: library/mailbox mailbox Mailbox __delitem__7836295
Ref: 29177836295
Ref: library/mailbox mailbox Mailbox discard7836336
Ref: 29137836336
Ref: library/mailbox mailbox Mailbox __setitem__7836887
Ref: 29187836887
Ref: library/mailbox mailbox Mailbox iterkeys7837776
Ref: 29197837776
Ref: library/mailbox mailbox Mailbox keys7837811
Ref: 291a7837811
Ref: library/mailbox mailbox Mailbox itervalues7838002
Ref: 291b7838002
Ref: library/mailbox mailbox Mailbox __iter__7838039
Ref: 291c7838039
Ref: library/mailbox mailbox Mailbox values7838074
Ref: 291d7838074
Ref: library/mailbox mailbox Mailbox iteritems7838721
Ref: 291e7838721
Ref: library/mailbox mailbox Mailbox items7838757
Ref: 291f7838757
Ref: library/mailbox mailbox Mailbox get7839286
Ref: 29207839286
Ref: library/mailbox mailbox Mailbox __getitem__7839333
Ref: 29217839333
Ref: library/mailbox mailbox Mailbox get_message7839925
Ref: 29227839925
Ref: library/mailbox mailbox Mailbox get_bytes7840219
Ref: bea7840219
Ref: library/mailbox mailbox Mailbox get_string7840456
Ref: beb7840456
Ref: library/mailbox mailbox Mailbox get_file7840801
Ref: be97840801
Ref: library/mailbox mailbox Mailbox __contains__7841776
Ref: 29237841776
Ref: library/mailbox mailbox Mailbox __len__7841916
Ref: 29247841916
Ref: library/mailbox mailbox Mailbox clear7842005
Ref: 29257842005
Ref: library/mailbox mailbox Mailbox pop7842087
Ref: 29267842087
Ref: library/mailbox mailbox Mailbox popitem7842536
Ref: 29277842536
Ref: library/mailbox mailbox Mailbox update7843063
Ref: 29287843063
Ref: library/mailbox mailbox Mailbox flush7843789
Ref: 29297843789
Ref: library/mailbox mailbox Mailbox lock7844086
Ref: 29147844086
Ref: library/mailbox mailbox Mailbox unlock7844511
Ref: 29157844511
Ref: library/mailbox mailbox Mailbox close7844597
Ref: 292b7844597
Node: Maildir7844855
Ref: library/mailbox mailbox-maildir7844927
Ref: 292c7844927
Ref: library/mailbox maildir7844927
Ref: 292d7844927
Ref: library/mailbox mailbox Maildir7844970
Ref: cad7844970
Ref: library/mailbox mailbox Maildir list_folders7847814
Ref: 292f7847814
Ref: library/mailbox mailbox Maildir get_folder7847908
Ref: 29307847908
Ref: library/mailbox mailbox Maildir add_folder7848154
Ref: 29327848154
Ref: library/mailbox mailbox Maildir remove_folder7848317
Ref: 29337848317
Ref: library/mailbox mailbox Maildir clean7848565
Ref: 29357848565
Ref: library/mailbox mailbox Maildir add7848911
Ref: 29367848911
Ref: library/mailbox mailbox Maildir __setitem__7848948
Ref: 29377848948
Ref: library/mailbox mailbox Maildir update7848998
Ref: 29387848998
Ref: library/mailbox mailbox Maildir flush7849416
Ref: 29397849416
Ref: library/mailbox mailbox Maildir lock7849557
Ref: 293a7849557
Ref: library/mailbox mailbox Maildir unlock7849588
Ref: 293b7849588
Ref: library/mailbox mailbox Maildir close7849727
Ref: 293c7849727
Ref: library/mailbox mailbox Maildir get_file7849930
Ref: 293d7849930
Ref: Maildir-Footnote-17850467
Ref: Maildir-Footnote-27850515
Node: mbox7850559
Ref: library/mailbox mailbox-mbox7850642
Ref: 293e7850642
Ref: library/mailbox mbox7850642
Ref: 293f7850642
Ref: library/mailbox mailbox mbox7850679
Ref: 29167850679
Ref: library/mailbox mailbox mbox get_file7852096
Ref: 29407852096
Ref: library/mailbox mailbox mbox lock7852315
Ref: 29417852315
Ref: library/mailbox mailbox mbox unlock7852346
Ref: 29427852346
Ref: mbox-Footnote-17852928
Ref: mbox-Footnote-27852988
Ref: mbox-Footnote-37853040
Node: MH7853118
Ref: library/mailbox mailbox-mh7853199
Ref: 29437853199
Ref: library/mailbox mh7853199
Ref: 29447853199
Ref: library/mailbox mailbox MH7853232
Ref: 29457853232
Ref: library/mailbox mailbox MH list_folders7854679
Ref: 29477854679
Ref: library/mailbox mailbox MH get_folder7854773
Ref: 29487854773
Ref: library/mailbox mailbox MH add_folder7855016
Ref: 29497855016
Ref: library/mailbox mailbox MH remove_folder7855176
Ref: 294a7855176
Ref: library/mailbox mailbox MH get_sequences7855424
Ref: 294b7855424
Ref: library/mailbox mailbox MH set_sequences7855607
Ref: 294c7855607
Ref: library/mailbox mailbox MH pack7855851
Ref: 294d7855851
Ref: library/mailbox mailbox MH remove7856280
Ref: 294e7856280
Ref: library/mailbox mailbox MH __delitem__7856316
Ref: 294f7856316
Ref: library/mailbox mailbox MH discard7856357
Ref: 29507856357
Ref: library/mailbox mailbox MH lock7856572
Ref: 29517856572
Ref: library/mailbox mailbox MH unlock7856603
Ref: 29527856603
Ref: library/mailbox mailbox MH get_file7856984
Ref: 29537856984
Ref: library/mailbox mailbox MH flush7857182
Ref: 29547857182
Ref: library/mailbox mailbox MH close7857318
Ref: 29557857318
Ref: MH-Footnote-17857790
Ref: MH-Footnote-27857825
Node: Babyl7857870
Ref: library/mailbox babyl7857951
Ref: 29567857951
Ref: library/mailbox mailbox-babyl7857951
Ref: 29577857951
Ref: library/mailbox mailbox Babyl7857990
Ref: 29587857990
Ref: library/mailbox mailbox Babyl get_labels7859560
Ref: 295a7859560
Ref: library/mailbox mailbox Babyl get_file7860101
Ref: 295b7860101
Ref: library/mailbox mailbox Babyl lock7860627
Ref: 295c7860627
Ref: library/mailbox mailbox Babyl unlock7860658
Ref: 295d7860658
Ref: Babyl-Footnote-17861057
Ref: Babyl-Footnote-27861101
Node: MMDF7861179
Ref: library/mailbox mailbox-mmdf7861249
Ref: 295e7861249
Ref: library/mailbox mmdf7861249
Ref: 295f7861249
Ref: library/mailbox mailbox MMDF7861286
Ref: 29607861286
Ref: library/mailbox mailbox MMDF get_file7862538
Ref: 29627862538
Ref: library/mailbox mailbox MMDF lock7862757
Ref: 29637862757
Ref: library/mailbox mailbox MMDF unlock7862788
Ref: 29647862788
Ref: MMDF-Footnote-17863230
Ref: MMDF-Footnote-27863290
Node: Message objects7863333
Ref: library/mailbox mailbox-message-objects7863483
Ref: 29657863483
Ref: library/mailbox message-objects7863483
Ref: 29667863483
Ref: library/mailbox mailbox Message7863542
Ref: bec7863542
Ref: Message objects-Footnote-17865589
Node: MaildirMessage7865638
Ref: library/mailbox mailbox-maildirmessage7865724
Ref: 29677865724
Ref: library/mailbox maildirmessage7865724
Ref: 29687865724
Ref: library/mailbox mailbox MaildirMessage7865781
Ref: 292e7865781
Ref: library/mailbox mailbox MaildirMessage get_subdir7867614
Ref: 29697867614
Ref: library/mailbox mailbox MaildirMessage set_subdir7868131
Ref: 296a7868131
Ref: library/mailbox mailbox MaildirMessage get_flags7868300
Ref: 296b7868300
Ref: library/mailbox mailbox MaildirMessage set_flags7868774
Ref: 296c7868774
Ref: library/mailbox mailbox MaildirMessage add_flag7868884
Ref: 296d7868884
Ref: library/mailbox mailbox MaildirMessage remove_flag7869236
Ref: 296e7869236
Ref: library/mailbox mailbox MaildirMessage get_date7869589
Ref: 296f7869589
Ref: library/mailbox mailbox MaildirMessage set_date7869751
Ref: 29707869751
Ref: library/mailbox mailbox MaildirMessage get_info7869922
Ref: 29717869922
Ref: library/mailbox mailbox MaildirMessage set_info7870143
Ref: 29727870143
Node: mboxMessage7872903
Ref: library/mailbox mailbox-mboxmessage7873007
Ref: 29737873007
Ref: library/mailbox mboxmessage7873007
Ref: 29747873007
Ref: library/mailbox mailbox mboxMessage7873058
Ref: 27e27873058
Ref: library/mailbox mailbox mboxMessage get_from7874837
Ref: 29757874837
Ref: library/mailbox mailbox mboxMessage set_from7875066
Ref: 29767875066
Ref: library/mailbox mailbox mboxMessage get_flags7875600
Ref: 29777875600
Ref: library/mailbox mailbox mboxMessage set_flags7875954
Ref: 29787875954
Ref: library/mailbox mailbox mboxMessage add_flag7876251
Ref: 29797876251
Ref: library/mailbox mailbox mboxMessage remove_flag7876477
Ref: 297a7876477
Node: MHMessage7879440
Ref: library/mailbox mailbox-mhmessage7879542
Ref: 297b7879542
Ref: library/mailbox mhmessage7879542
Ref: 297c7879542
Ref: library/mailbox mailbox MHMessage7879591
Ref: 29467879591
Ref: library/mailbox mailbox MHMessage get_sequences7880558
Ref: 297d7880558
Ref: library/mailbox mailbox MHMessage set_sequences7880687
Ref: 297e7880687
Ref: library/mailbox mailbox MHMessage add_sequence7880801
Ref: 297f7880801
Ref: library/mailbox mailbox MHMessage remove_sequence7880937
Ref: 29807880937
Node: BabylMessage7882789
Ref: library/mailbox babylmessage7882891
Ref: 29817882891
Ref: library/mailbox mailbox-babylmessage7882891
Ref: 29827882891
Ref: library/mailbox mailbox BabylMessage7882946
Ref: 29597882946
Ref: library/mailbox mailbox BabylMessage get_labels7884315
Ref: 29837884315
Ref: library/mailbox mailbox BabylMessage set_labels7884404
Ref: 29847884404
Ref: library/mailbox mailbox BabylMessage add_label7884510
Ref: 29857884510
Ref: library/mailbox mailbox BabylMessage remove_label7884613
Ref: 29867884613
Ref: library/mailbox mailbox BabylMessage get_visible7884724
Ref: 29877884724
Ref: library/mailbox mailbox BabylMessage set_visible7884898
Ref: 29887884898
Ref: library/mailbox mailbox BabylMessage update_visible7885254
Ref: 29897885254
Node: MMDFMessage7887684
Ref: library/mailbox mailbox-mmdfmessage7887768
Ref: 298a7887768
Ref: library/mailbox mmdfmessage7887768
Ref: 298b7887768
Ref: library/mailbox mailbox MMDFMessage7887821
Ref: 29617887821
Ref: library/mailbox mailbox MMDFMessage get_from7889484
Ref: 298c7889484
Ref: library/mailbox mailbox MMDFMessage set_from7889713
Ref: 298d7889713
Ref: library/mailbox mailbox MMDFMessage get_flags7890247
Ref: 298e7890247
Ref: library/mailbox mailbox MMDFMessage set_flags7890601
Ref: 298f7890601
Ref: library/mailbox mailbox MMDFMessage add_flag7890898
Ref: 29907890898
Ref: library/mailbox mailbox MMDFMessage remove_flag7891124
Ref: 29917891124
Node: Exceptions<12>7894093
Ref: library/mailbox exceptions7894240
Ref: 29927894240
Ref: library/mailbox mailbox Error7894362
Ref: 29937894362
Ref: library/mailbox mailbox NoSuchMailboxError7894453
Ref: 29317894453
Ref: library/mailbox mailbox NotEmptyError7894756
Ref: 29347894756
Ref: library/mailbox mailbox ExternalClashError7894915
Ref: 292a7894915
Ref: library/mailbox mailbox FormatError7895225
Ref: 29947895225
Node: Examples<18>7895419
Ref: library/mailbox examples7895542
Ref: 29957895542
Ref: library/mailbox mailbox-examples7895542
Ref: 29967895542
Node: mimetypes --- Map filenames to MIME types7897820
Ref: library/mimetypes doc7898049
Ref: 29977898049
Ref: library/mimetypes mimetypes-map-filenames-to-mime-types7898049
Ref: 29987898049
Ref: library/mimetypes module-mimetypes7898049
Ref: b37898049
Ref: library/mimetypes mimetypes guess_type7898936
Ref: f6e7898936
Ref: library/mimetypes mimetypes guess_all_extensions7900252
Ref: 299a7900252
Ref: library/mimetypes mimetypes guess_extension7900813
Ref: 299b7900813
Ref: library/mimetypes mimetypes init7901513
Ref: 29997901513
Ref: library/mimetypes mimetypes read_mime_types7902473
Ref: f0d7902473
Ref: library/mimetypes mimetypes add_type7902848
Ref: 299d7902848
Ref: library/mimetypes mimetypes inited7903303
Ref: 299e7903303
Ref: library/mimetypes mimetypes knownfiles7903473
Ref: 299c7903473
Ref: library/mimetypes mimetypes suffix_map7903683
Ref: 299f7903683
Ref: library/mimetypes mimetypes encodings_map7904033
Ref: 29a07904033
Ref: library/mimetypes mimetypes types_map7904132
Ref: 29a17904132
Ref: library/mimetypes mimetypes common_types7904223
Ref: 29a27904223
Ref: mimetypes --- Map filenames to MIME types-Footnote-17904765
Ref: mimetypes --- Map filenames to MIME types-Footnote-27904833
Node: MimeTypes Objects7904904
Ref: library/mimetypes id17904999
Ref: 29a37904999
Ref: library/mimetypes mimetypes-objects7904999
Ref: 29a47904999
Ref: library/mimetypes mimetypes MimeTypes7905248
Ref: 29a57905248
Ref: library/mimetypes mimetypes MimeTypes suffix_map7905931
Ref: 29a87905931
Ref: library/mimetypes mimetypes MimeTypes encodings_map7906410
Ref: 29a97906410
Ref: library/mimetypes mimetypes MimeTypes types_map7906620
Ref: 29aa7906620
Ref: library/mimetypes mimetypes MimeTypes types_map_inv7906953
Ref: 29ab7906953
Ref: library/mimetypes mimetypes MimeTypes guess_extension7907300
Ref: 29ac7907300
Ref: library/mimetypes mimetypes MimeTypes guess_type7907484
Ref: 10297907484
Ref: library/mimetypes mimetypes MimeTypes guess_all_extensions7907656
Ref: 29ad7907656
Ref: library/mimetypes mimetypes MimeTypes read7907850
Ref: 29a67907850
Ref: library/mimetypes mimetypes MimeTypes readfp7908169
Ref: 29a77908169
Ref: library/mimetypes mimetypes MimeTypes read_windows_registry7908506
Ref: 29ae7908506
Node: base64 —— Base16、Base32、Base64、Base85 資料編碼7908852
Ref: library/base64 doc7909072
Ref: 29af7909072
Ref: library/base64 base64-base16-base32-base64-base85-data-encodings7909072
Ref: 29b07909072
Ref: library/base64 module-base647909072
Ref: e7909072
Ref: library/base64 base64 b64encode7910732
Ref: 29b17910732
Ref: library/base64 base64 b64decode7911280
Ref: f4f7911280
Ref: library/base64 base64 standard_b64encode7912122
Ref: 29b27912122
Ref: library/base64 base64 standard_b64decode7912293
Ref: 29b37912293
Ref: library/base64 base64 urlsafe_b64encode7912480
Ref: 29b47912480
Ref: library/base64 base64 urlsafe_b64decode7912818
Ref: 29b57912818
Ref: library/base64 base64 b32encode7913133
Ref: 29b67913133
Ref: library/base64 base64 b32decode7913277
Ref: 9627913277
Ref: library/base64 base64 b16encode7914265
Ref: 29b77914265
Ref: library/base64 base64 b16decode7914409
Ref: 29b87914409
Ref: library/base64 base64 a85encode7914890
Ref: 8297914890
Ref: library/base64 base64 a85decode7915845
Ref: 82a7915845
Ref: library/base64 base64 b85encode7916700
Ref: 82b7916700
Ref: library/base64 base64 b85decode7917048
Ref: 82c7917048
Ref: library/base64 base64 decode7917308
Ref: 29b97917308
Ref: library/base64 base64 decodebytes7917614
Ref: 187a7917614
Ref: library/base64 base64 decodestring7917838
Ref: 29ba7917838
Ref: library/base64 base64 encode7917955
Ref: 29bb7917955
Ref: library/base64 base64 encodebytes7918472
Ref: 18797918472
Ref: library/base64 base64 encodestring7918853
Ref: 29bc7918853
Ref: base64 —— Base16、Base32、Base64、Base85 資料編碼-Footnote-17919645
Ref: base64 —— Base16、Base32、Base64、Base85 資料編碼-Footnote-27919710
Ref: base64 —— Base16、Base32、Base64、Base85 資料編碼-Footnote-37919759
Ref: base64 —— Base16、Base32、Base64、Base85 資料編碼-Footnote-47919808
Ref: base64 —— Base16、Base32、Base64、Base85 資料編碼-Footnote-57919857
Ref: base64 —— Base16、Base32、Base64、Base85 資料編碼-Footnote-67919906
Ref: base64 —— Base16、Base32、Base64、Base85 資料編碼-Footnote-77919955
Ref: base64 —— Base16、Base32、Base64、Base85 資料編碼-Footnote-87920004
Ref: base64 —— Base16、Base32、Base64、Base85 資料編碼-Footnote-97920053
Ref: base64 —— Base16、Base32、Base64、Base85 資料編碼-Footnote-107920102
Node: binhex --- Encode and decode binhex4 files7920152
Ref: library/binhex doc7920376
Ref: 29bd7920376
Ref: library/binhex binhex-encode-and-decode-binhex4-files7920376
Ref: 29be7920376
Ref: library/binhex module-binhex7920376
Ref: 117920376
Ref: library/binhex binhex binhex7920798
Ref: 29bf7920798
Ref: library/binhex binhex hexbin7921068
Ref: 29c07921068
Ref: library/binhex binhex Error7921464
Ref: 29c17921464
Ref: binhex --- Encode and decode binhex4 files-Footnote-17921899
Node: 註解<2>7921964
Ref: library/binhex binhex-notes7922052
Ref: 29c27922052
Ref: library/binhex notes7922052
Ref: 29c37922052
Node: binascii --- Convert between binary and ASCII7922338
Ref: library/binascii doc7922557
Ref: 29c47922557
Ref: library/binascii binascii-convert-between-binary-and-ascii7922557
Ref: 29c57922557
Ref: library/binascii module-binascii7922557
Ref: 107922557
Ref: library/binascii binascii a2b_uu7923588
Ref: 29c67923588
Ref: library/binascii binascii b2a_uu7923836
Ref: 3727923836
Ref: library/binascii binascii a2b_base647924204
Ref: 29c77924204
Ref: library/binascii binascii b2a_base647924376
Ref: 5287924376
Ref: library/binascii binascii a2b_qp7924715
Ref: 29c87924715
Ref: library/binascii binascii b2a_qp7925010
Ref: 29c97925010
Ref: library/binascii binascii a2b_hqx7925776
Ref: 29ca7925776
Ref: library/binascii binascii rledecode_hqx7926062
Ref: 29cb7926062
Ref: library/binascii binascii rlecode_hqx7926592
Ref: 29cd7926592
Ref: library/binascii binascii b2a_hqx7926715
Ref: 29ce7926715
Ref: library/binascii binascii crc_hqx7926958
Ref: 29cf7926958
Ref: library/binascii binascii crc327927261
Ref: 29d07927261
Ref: library/binascii binascii b2a_hex7928041
Ref: 187c7928041
Ref: library/binascii binascii hexlify7928103
Ref: fc27928103
Ref: library/binascii binascii a2b_hex7929284
Ref: 187d7929284
Ref: library/binascii binascii unhexlify7929322
Ref: 10437929322
Ref: library/binascii binascii Error7929848
Ref: 9637929848
Ref: library/binascii binascii Incomplete7929949
Ref: 29cc7929949
Ref: binascii --- Convert between binary and ASCII-Footnote-17930562
Ref: binascii --- Convert between binary and ASCII-Footnote-27930611
Node: quopri --- Encode and decode MIME quoted-printable data7930660
Ref: library/quopri doc7930876
Ref: 29d17930876
Ref: library/quopri module-quopri7930876
Ref: dc7930876
Ref: library/quopri quopri-encode-and-decode-mime-quoted-printable-data7930876
Ref: 29d27930876
Ref: library/quopri quopri decode7931607
Ref: 187f7931607
Ref: library/quopri quopri encode7932136
Ref: 187e7932136
Ref: library/quopri quopri decodestring7932790
Ref: 29d37932790
Ref: library/quopri quopri encodestring7932985
Ref: 29d47932985
Ref: quopri --- Encode and decode MIME quoted-printable data-Footnote-17933432
Ref: quopri --- Encode and decode MIME quoted-printable data-Footnote-27933497
Ref: quopri --- Encode and decode MIME quoted-printable data-Footnote-37933546
Ref: quopri --- Encode and decode MIME quoted-printable data-Footnote-47933595
Ref: quopri --- Encode and decode MIME quoted-printable data-Footnote-57933644
Node: uu --- Encode and decode uuencode files7933693
Ref: library/uu doc7933855
Ref: 29d57933855
Ref: library/uu module-uu7933855
Ref: 1247933855
Ref: library/uu uu-encode-and-decode-uuencode-files7933855
Ref: 29d67933855
Ref: library/uu uu encode7934804
Ref: 4147934804
Ref: library/uu uu decode7935321
Ref: 18807935321
Ref: library/uu uu Error7936007
Ref: 29d77936007
Ref: uu --- Encode and decode uuencode files-Footnote-17936420
Node: Structured Markup Processing Tools7936481
Ref: library/markup doc7936661
Ref: 29d87936661
Ref: library/markup markup7936661
Ref: 29d97936661
Ref: library/markup structured-markup-processing-tools7936661
Ref: 29da7936661
Node: html --- HyperText Markup Language support7938193
Ref: library/html doc7938359
Ref: 29db7938359
Ref: library/html html-hypertext-markup-language-support7938359
Ref: 29dc7938359
Ref: library/html module-html7938359
Ref: 907938359
Ref: library/html html escape7938625
Ref: 9397938625
Ref: library/html html unescape7939092
Ref: 85f7939092
Ref: html --- HyperText Markup Language support-Footnote-17939789
Node: html parser --- Simple HTML and XHTML parser7939861
Ref: library/html parser doc7940090
Ref: 29dd7940090
Ref: library/html parser html-parser-simple-html-and-xhtml-parser7940090
Ref: 29de7940090
Ref: library/html parser module-html parser7940090
Ref: 927940090
Ref: library/html parser html parser HTMLParser7940466
Ref: 7c47940466
Ref: html parser --- Simple HTML and XHTML parser-Footnote-17941567
Node: Example HTML Parser Application7941637
Ref: library/html parser example-html-parser-application7941776
Ref: 29df7941776
Node: HTMLParser Methods7942982
Ref: library/html parser htmlparser-methods7943142
Ref: 29e07943142
Ref: library/html parser html parser HTMLParser feed7943269
Ref: 29e17943269
Ref: library/html parser html parser HTMLParser close7943542
Ref: 29e27943542
Ref: library/html parser html parser HTMLParser reset7943909
Ref: 29e37943909
Ref: library/html parser html parser HTMLParser getpos7944058
Ref: 29e47944058
Ref: library/html parser html parser HTMLParser get_starttag_text7944143
Ref: 29e57944143
Ref: library/html parser html parser HTMLParser handle_starttag7944716
Ref: 29e77944716
Ref: library/html parser html parser HTMLParser handle_endtag7945518
Ref: 29e87945518
Ref: library/html parser html parser HTMLParser handle_startendtag7945731
Ref: 29e67945731
Ref: library/html parser html parser HTMLParser handle_data7946150
Ref: 29e97946150
Ref: library/html parser html parser HTMLParser handle_entityref7946358
Ref: 29ea7946358
Ref: library/html parser html parser HTMLParser handle_charref7946668
Ref: 29eb7946668
Ref: library/html parser html parser HTMLParser handle_comment7947120
Ref: 29ec7947120
Ref: library/html parser html parser HTMLParser handle_decl7947652
Ref: 29ed7947652
Ref: library/html parser html parser HTMLParser handle_pi7947942
Ref: 29ee7947942
Ref: library/html parser html parser HTMLParser unknown_decl7948640
Ref: 29ef7948640
Node: Examples<19>7949008
Ref: library/html parser examples7949128
Ref: 29f07949128
Ref: library/html parser htmlparser-examples7949128
Ref: 29f17949128
Node: html entities --- Definitions of HTML general entities7952537
Ref: library/html entities doc7952740
Ref: 29f27952740
Ref: library/html entities html-entities-definitions-of-html-general-entities7952740
Ref: 29f37952740
Ref: library/html entities module-html entities7952740
Ref: 917952740
Ref: library/html entities html entities html57953121
Ref: a1a7953121
Ref: library/html entities html entities entitydefs7953604
Ref: 29f67953604
Ref: library/html entities html entities name2codepoint7953743
Ref: 29f47953743
Ref: library/html entities html entities codepoint2name7953863
Ref: 29f57953863
Ref: html entities --- Definitions of HTML general entities-Footnote-17954023
Ref: html entities --- Definitions of HTML general entities-Footnote-27954095
Node: XML 處理模組7954184
Ref: library/xml doc7954392
Ref: 29f77954392
Ref: library/xml module-xml7954392
Ref: 1347954392
Ref: library/xml xml7954392
Ref: 29f87954392
Ref: library/xml xml-processing-modules7954392
Ref: 29f97954392
Ref: XML 處理模組-Footnote-17955835
Node: XML vulnerabilities7955895
Ref: library/xml id17955998
Ref: 29fc7955998
Ref: library/xml xml-vulnerabilities7955998
Ref: 29fa7955998
Ref: XML vulnerabilities-Footnote-17960660
Ref: XML vulnerabilities-Footnote-27960723
Ref: XML vulnerabilities-Footnote-37960776
Ref: XML vulnerabilities-Footnote-47960829
Ref: XML vulnerabilities-Footnote-57960892
Ref: XML vulnerabilities-Footnote-67960939
Node: The defusedxml Package7960984
Ref: library/xml defusedxml-package7961087
Ref: 29fb7961087
Ref: library/xml the-defusedxml-package7961087
Ref: 29fd7961087
Ref: The defusedxml Package-Footnote-17961543
Node: xml etree ElementTree --- The ElementTree XML API7961588
Ref: library/xml etree elementtree doc7961783
Ref: 29fe7961783
Ref: library/xml etree elementtree dtd7961783
Ref: 29ff7961783
Ref: library/xml etree elementtree module-xml etree ElementTree7961783
Ref: 1387961783
Ref: library/xml etree elementtree xml-etree-elementtree-the-elementtree-xml-api7961783
Ref: 2a007961783
Ref: xml etree ElementTree --- The ElementTree XML API-Footnote-17962645
Node: Tutorial7962726
Ref: library/xml etree elementtree tutorial7962842
Ref: 2a017962842
Node: XML tree and elements7963293
Ref: library/xml etree elementtree xml-tree-and-elements7963379
Ref: 2a027963379
Node: Parsing XML7963957
Ref: library/xml etree elementtree elementtree-parsing-xml7964085
Ref: 2a037964085
Ref: library/xml etree elementtree parsing-xml7964085
Ref: 2a047964085
Node: Pull API for non-blocking parsing7966543
Ref: library/xml etree elementtree elementtree-pull-parsing7966678
Ref: 9197966678
Ref: library/xml etree elementtree pull-api-for-non-blocking-parsing7966678
Ref: 2a067966678
Node: Finding interesting elements7968575
Ref: library/xml etree elementtree finding-interesting-elements7968720
Ref: 2a097968720
Node: Modifying an XML File7969961
Ref: library/xml etree elementtree modifying-an-xml-file7970095
Ref: 2a0e7970095
Node: Building XML documents7973039
Ref: library/xml etree elementtree building-xml-documents7973172
Ref: 2a127973172
Node: Parsing XML with Namespaces7973541
Ref: library/xml etree elementtree parsing-xml-with-namespaces7973673
Ref: 2a147973673
Ref: Parsing XML with Namespaces-Footnote-17975984
Ref: Parsing XML with Namespaces-Footnote-27976036
Node: Additional resources7976088
Ref: library/xml etree elementtree additional-resources7976189
Ref: 2a157976189
Node: XPath support7976341
Ref: library/xml etree elementtree elementtree-xpath7976478
Ref: 41f7976478
Ref: library/xml etree elementtree xpath-support7976478
Ref: 2a167976478
Ref: XPath support-Footnote-17976842
Node: Example<10>7976878
Ref: library/xml etree elementtree example7976970
Ref: 2a177976970
Node: Supported XPath syntax7977989
Ref: library/xml etree elementtree supported-xpath-syntax7978081
Ref: 2a187978081
Node: Reference<2>7982003
Ref: library/xml etree elementtree reference7982148
Ref: 2a197982148
Node: Functions<6>7982226
Ref: library/xml etree elementtree elementtree-functions7982287
Ref: 2a1a7982287
Ref: library/xml etree elementtree functions7982287
Ref: 2a1b7982287
Ref: library/xml etree elementtree xml etree ElementTree canonicalize7982328
Ref: 2a1c7982328
Ref: library/xml etree elementtree xml etree ElementTree Comment7984698
Ref: 2a1d7984698
Ref: library/xml etree elementtree xml etree ElementTree dump7985381
Ref: 2a1e7985381
Ref: library/xml etree elementtree xml etree ElementTree fromstring7985844
Ref: 2a057985844
Ref: library/xml etree elementtree xml etree ElementTree fromstringlist7986201
Ref: b547986201
Ref: library/xml etree elementtree xml etree ElementTree iselement7986605
Ref: 2a207986605
Ref: library/xml etree elementtree xml etree ElementTree iterparse7986817
Ref: 94d7986817
Ref: library/xml etree elementtree xml etree ElementTree parse7988643
Ref: 2a217988643
Ref: library/xml etree elementtree xml etree ElementTree ProcessingInstruction7988985
Ref: 2a227988985
Ref: library/xml etree elementtree xml etree ElementTree register_namespace7989716
Ref: b557989716
Ref: library/xml etree elementtree xml etree ElementTree SubElement7990141
Ref: 2a137990141
Ref: library/xml etree elementtree xml etree ElementTree tostring7990709
Ref: 91a7990709
Ref: library/xml etree elementtree xml etree ElementTree tostringlist7991773
Ref: 91b7991773
Ref: library/xml etree elementtree xml etree ElementTree XML7993005
Ref: 2a1f7993005
Ref: library/xml etree elementtree xml etree ElementTree XMLID7993393
Ref: 2a237993393
Ref: Functions<6>-Footnote-17993866
Ref: Functions<6>-Footnote-27993907
Ref: Functions<6>-Footnote-37994212
Node: XInclude support7994517
Ref: library/xml etree elementtree elementtree-xinclude7994661
Ref: 2a247994661
Ref: library/xml etree elementtree xinclude-support7994661
Ref: 2a257994661
Ref: XInclude support-Footnote-17995021
Node: Example<11>7995061
Ref: library/xml etree elementtree id37995125
Ref: 2a267995125
Node: Reference<3>7996931
Ref: library/xml etree elementtree id47997054
Ref: 2a277997054
Node: Functions<7>7997296
Ref: library/xml etree elementtree elementinclude-functions7997381
Ref: 2a287997381
Ref: library/xml etree elementtree id57997381
Ref: 2a297997381
Ref: library/xml etree elementtree xml etree ElementTree xml etree ElementInclude default_loader7997422
Ref: 2a2a7997422
Ref: library/xml etree elementtree xml etree ElementTree xml etree ElementInclude include7997995
Ref: 2a2b7997995
Node: Element Objects7998597
Ref: library/xml etree elementtree element-objects7998710
Ref: 2a2c7998710
Ref: library/xml etree elementtree elementtree-element-objects7998710
Ref: 2a2d7998710
Ref: library/xml etree elementtree xml etree ElementTree Element7998763
Ref: ac97998763
Ref: library/xml etree elementtree xml etree ElementTree Element tag7999246
Ref: 2a2e7999246
Ref: library/xml etree elementtree xml etree ElementTree Element text7999388
Ref: 2a0c7999388
Ref: library/xml etree elementtree xml etree ElementTree Element tail7999410
Ref: 2a2f7999410
Ref: library/xml etree elementtree xml etree ElementTree Element attrib8000522
Ref: 2a308000522
Ref: library/xml etree elementtree xml etree ElementTree Element clear8001063
Ref: 2a318001063
Ref: library/xml etree elementtree xml etree ElementTree Element get8001262
Ref: 2a0d8001262
Ref: library/xml etree elementtree xml etree ElementTree Element items8001456
Ref: 2a328001456
Ref: library/xml etree elementtree xml etree ElementTree Element keys8001631
Ref: 2a338001631
Ref: library/xml etree elementtree xml etree ElementTree Element set8001779
Ref: 2a0f8001779
Ref: library/xml etree elementtree xml etree ElementTree Element append8001958
Ref: 2a108001958
Ref: library/xml etree elementtree xml etree ElementTree Element extend8002200
Ref: b568002200
Ref: library/xml etree elementtree xml etree ElementTree Element find8002454
Ref: 2a0b8002454
Ref: library/xml etree elementtree xml etree ElementTree Element findall8002882
Ref: 2a0a8002882
Ref: library/xml etree elementtree xml etree ElementTree Element findtext8003307
Ref: 2a348003307
Ref: library/xml etree elementtree xml etree ElementTree Element getchildren8003917
Ref: 2a358003917
Ref: library/xml etree elementtree xml etree ElementTree Element getiterator8004074
Ref: 2a368004074
Ref: library/xml etree elementtree xml etree ElementTree Element insert8004251
Ref: 2a378004251
Ref: library/xml etree elementtree xml etree ElementTree Element iter8004468
Ref: cec8004468
Ref: library/xml etree elementtree xml etree ElementTree Element iterfind8004963
Ref: b578004963
Ref: library/xml etree elementtree xml etree ElementTree Element itertext8005299
Ref: b588005299
Ref: library/xml etree elementtree xml etree ElementTree Element makeelement8005526
Ref: 2a388005526
Ref: library/xml etree elementtree xml etree ElementTree Element remove8005755
Ref: 2a118005755
Ref: Element Objects-Footnote-18008321
Node: ElementTree Objects8008364
Ref: library/xml etree elementtree elementtree-elementtree-objects8008478
Ref: 2a398008478
Ref: library/xml etree elementtree elementtree-objects8008478
Ref: 2a3a8008478
Ref: library/xml etree elementtree xml etree ElementTree ElementTree8008539
Ref: 91c8008539
Ref: library/xml etree elementtree xml etree ElementTree ElementTree _setroot8008892
Ref: 2a3b8008892
Ref: library/xml etree elementtree xml etree ElementTree ElementTree find8009147
Ref: 2a3c8009147
Ref: library/xml etree elementtree xml etree ElementTree ElementTree findall8009292
Ref: 2a3d8009292
Ref: library/xml etree elementtree xml etree ElementTree ElementTree findtext8009443
Ref: 2a3e8009443
Ref: library/xml etree elementtree xml etree ElementTree ElementTree getiterator8009610
Ref: 2a3f8009610
Ref: library/xml etree elementtree xml etree ElementTree ElementTree getroot8009792
Ref: 2a418009792
Ref: library/xml etree elementtree xml etree ElementTree ElementTree iter8009878
Ref: 2a408009878
Ref: library/xml etree elementtree xml etree ElementTree ElementTree iterfind8010154
Ref: 2a428010154
Ref: library/xml etree elementtree xml etree ElementTree ElementTree parse8010335
Ref: 2a438010335
Ref: library/xml etree elementtree xml etree ElementTree ElementTree write8010686
Ref: 91d8010686
Ref: ElementTree Objects-Footnote-18013442
Node: QName Objects8013747
Ref: library/xml etree elementtree elementtree-qname-objects8013865
Ref: 2a448013865
Ref: library/xml etree elementtree qname-objects8013865
Ref: 2a458013865
Ref: library/xml etree elementtree xml etree ElementTree QName8013914
Ref: 2a468013914
Node: TreeBuilder Objects8014428
Ref: library/xml etree elementtree elementtree-treebuilder-objects8014544
Ref: 2a478014544
Ref: library/xml etree elementtree treebuilder-objects8014544
Ref: 2a488014544
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder8014605
Ref: 2548014605
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder close8015724
Ref: 2a498015724
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder data8015892
Ref: 2a4a8015892
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder end8016062
Ref: b598016062
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder start8016201
Ref: 2a4b8016201
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder comment8016409
Ref: 2a4c8016409
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder pi8016609
Ref: 2a4d8016609
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder doctype8016924
Ref: 2c28016924
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder start_ns8017252
Ref: 2a4e8017252
Ref: library/xml etree elementtree xml etree ElementTree TreeBuilder end_ns8017650
Ref: 2a4f8017650
Ref: library/xml etree elementtree xml etree ElementTree C14NWriterTarget8017901
Ref: 2a508017901
Ref: TreeBuilder Objects-Footnote-18018448
Node: XMLParser Objects8018489
Ref: library/xml etree elementtree elementtree-xmlparser-objects8018613
Ref: 2a518018613
Ref: library/xml etree elementtree xmlparser-objects8018613
Ref: 2a528018613
Ref: library/xml etree elementtree xml etree ElementTree XMLParser8018670
Ref: 2538018670
Ref: library/xml etree elementtree xml etree ElementTree XMLParser close8019375
Ref: 2a548019375
Ref: library/xml etree elementtree xml etree ElementTree XMLParser feed8019637
Ref: 2a538019637
Ref: XMLParser Objects-Footnote-18021520
Node: XMLPullParser Objects8021825
Ref: library/xml etree elementtree elementtree-xmlpullparser-objects8021944
Ref: 2a558021944
Ref: library/xml etree elementtree xmlpullparser-objects8021944
Ref: 2a568021944
Ref: library/xml etree elementtree xml etree ElementTree XMLPullParser8022009
Ref: 9188022009
Ref: library/xml etree elementtree xml etree ElementTree XMLPullParser feed8022698
Ref: 2a078022698
Ref: library/xml etree elementtree xml etree ElementTree XMLPullParser close8022786
Ref: 2a578022786
Ref: library/xml etree elementtree xml etree ElementTree XMLPullParser read_events8023103
Ref: 2a088023103
Node: Exceptions<13>8024822
Ref: library/xml etree elementtree exceptions8024915
Ref: 2a588024915
Ref: library/xml etree elementtree xml etree ElementTree ParseError8024958
Ref: c118024958
Ref: library/xml etree elementtree xml etree ElementTree ParseError code8025287
Ref: 2a598025287
Ref: library/xml etree elementtree xml etree ElementTree ParseError position8025489
Ref: 2a5a8025489
Node: xml dom --- The Document Object Model API8025624
Ref: library/xml dom doc8025849
Ref: 2a5b8025849
Ref: library/xml dom module-xml dom8025849
Ref: 1358025849
Ref: library/xml dom xml-dom-the-document-object-model-api8025849
Ref: 2a5c8025849
Ref: xml dom --- The Document Object Model API-Footnote-18029314
Ref: xml dom --- The Document Object Model API-Footnote-28029390
Ref: xml dom --- The Document Object Model API-Footnote-38029456
Ref: xml dom --- The Document Object Model API-Footnote-48029503
Node: Module Contents<4>8029562
Ref: library/xml dom module-contents8029685
Ref: 2a5f8029685
Ref: library/xml dom xml dom registerDOMImplementation8029795
Ref: 2a608029795
Ref: library/xml dom xml dom getDOMImplementation8030241
Ref: 2a5d8030241
Ref: library/xml dom xml dom EMPTY_NAMESPACE8031148
Ref: 2a618031148
Ref: library/xml dom xml dom XML_NAMESPACE8031421
Ref: 2a628031421
Ref: library/xml dom xml dom XMLNS_NAMESPACE8031578
Ref: 2a638031578
Ref: library/xml dom xml dom XHTML_NAMESPACE8031764
Ref: 2a648031764
Ref: Module Contents<4>-Footnote-18032499
Ref: Module Contents<4>-Footnote-28032544
Ref: Module Contents<4>-Footnote-38032601
Node: Objects in the DOM8032639
Ref: library/xml dom dom-objects8032782
Ref: 2a658032782
Ref: library/xml dom objects-in-the-dom8032782
Ref: 2a668032782
Node: DOMImplementation Objects8037317
Ref: library/xml dom dom-implementation-objects8037418
Ref: 2a678037418
Ref: library/xml dom domimplementation-objects8037418
Ref: 2a718037418
Ref: library/xml dom xml dom DOMImplementation hasFeature8037774
Ref: 2a728037774
Ref: library/xml dom xml dom DOMImplementation createDocument8037959
Ref: 2a738037959
Ref: library/xml dom xml dom DOMImplementation createDocumentType8038485
Ref: 2a748038485
Node: Node Objects8038799
Ref: library/xml dom dom-node-objects8038925
Ref: 2a688038925
Ref: library/xml dom node-objects8038925
Ref: 2a758038925
Ref: library/xml dom xml dom Node nodeType8039042
Ref: 2a768039042
Ref: library/xml dom xml dom Node parentNode8039462
Ref: 2a778039462
Ref: library/xml dom xml dom Node attributes8039868
Ref: 2a788039868
Ref: library/xml dom xml dom Node previousSibling8040078
Ref: 2a798040078
Ref: library/xml dom xml dom Node nextSibling8040561
Ref: 2a7a8040561
Ref: library/xml dom xml dom Node childNodes8040824
Ref: 2a7b8040824
Ref: library/xml dom xml dom Node firstChild8040940
Ref: 2a7c8040940
Ref: library/xml dom xml dom Node lastChild8041074
Ref: 2a7d8041074
Ref: library/xml dom xml dom Node localName8041206
Ref: 2a7e8041206
Ref: library/xml dom xml dom Node prefix8041367
Ref: 2a7f8041367
Ref: library/xml dom xml dom Node namespaceURI8041532
Ref: 2a808041532
Ref: library/xml dom xml dom Node nodeName8041692
Ref: 2a818041692
Ref: library/xml dom xml dom Node nodeValue8042126
Ref: 2a828042126
Ref: library/xml dom xml dom Node hasAttributes8042357
Ref: 2a838042357
Ref: library/xml dom xml dom Node hasChildNodes8042454
Ref: 2a848042454
Ref: library/xml dom xml dom Node isSameNode8042552
Ref: 2a858042552
Ref: library/xml dom xml dom Node appendChild8043185
Ref: 2a868043185
Ref: library/xml dom xml dom Node insertBefore8043399
Ref: 2a878043399
Ref: library/xml dom xml dom Node removeChild8043746
Ref: 2a888043746
Ref: library/xml dom xml dom Node replaceChild8044040
Ref: 2a898044040
Ref: library/xml dom xml dom Node normalize8044260
Ref: 2a8a8044260
Ref: library/xml dom xml dom Node cloneNode8044483
Ref: 2a8b8044483
Node: NodeList Objects8044633
Ref: library/xml dom dom-nodelist-objects8044754
Ref: 2a698044754
Ref: library/xml dom nodelist-objects8044754
Ref: 2a8c8044754
Ref: library/xml dom xml dom NodeList item8045235
Ref: 2a8d8045235
Ref: library/xml dom xml dom NodeList length8045471
Ref: 2a8e8045471
Node: DocumentType Objects8046135
Ref: library/xml dom documenttype-objects8046260
Ref: 2a8f8046260
Ref: library/xml dom dom-documenttype-objects8046260
Ref: 2a6a8046260
Ref: library/xml dom xml dom DocumentType publicId8046893
Ref: 2a908046893
Ref: library/xml dom xml dom DocumentType systemId8047056
Ref: 2a918047056
Ref: library/xml dom xml dom DocumentType internalSubset8047229
Ref: 2a928047229
Ref: library/xml dom xml dom DocumentType name8047479
Ref: 2a938047479
Ref: library/xml dom xml dom DocumentType entities8047605
Ref: 2a948047605
Ref: library/xml dom xml dom DocumentType notations8047985
Ref: 2a958047985
Node: Document Objects8048361
Ref: library/xml dom document-objects8048488
Ref: 2a968048488
Ref: library/xml dom dom-document-objects8048488
Ref: 2a6b8048488
Ref: library/xml dom xml dom Document documentElement8048735
Ref: 2a978048735
Ref: library/xml dom xml dom Document createElement8048826
Ref: 2a988048826
Ref: library/xml dom xml dom Document createElementNS8049121
Ref: 2a998049121
Ref: library/xml dom xml dom Document createTextNode8049478
Ref: 2a9a8049478
Ref: library/xml dom xml dom Document createComment8049703
Ref: 2a9b8049703
Ref: library/xml dom xml dom Document createProcessingInstruction8049930
Ref: 2a9c8049930
Ref: library/xml dom xml dom Document createAttribute8050208
Ref: 2a9d8050208
Ref: library/xml dom xml dom Document createAttributeNS8050521
Ref: 2a9e8050521
Ref: library/xml dom xml dom Document getElementsByTagName8050915
Ref: 2a9f8050915
Ref: library/xml dom xml dom Document getElementsByTagNameNS8051097
Ref: 2aa08051097
Node: Element Objects<2>8051374
Ref: library/xml dom dom-element-objects8051493
Ref: 2a6c8051493
Ref: library/xml dom element-objects8051493
Ref: 2aa18051493
Ref: library/xml dom xml dom Element tagName8051634
Ref: 2aa28051634
Ref: library/xml dom xml dom Element getElementsByTagName8051778
Ref: 2aa38051778
Ref: library/xml dom xml dom Element getElementsByTagNameNS8051897
Ref: 2aa48051897
Ref: library/xml dom xml dom Element hasAttribute8052034
Ref: 2aa58052034
Ref: library/xml dom xml dom Element hasAttributeNS8052154
Ref: 2aa68052154
Ref: library/xml dom xml dom Element getAttribute8052324
Ref: 2aa78052324
Ref: library/xml dom xml dom Element getAttributeNode8052543
Ref: 2aa88052543
Ref: library/xml dom xml dom Element getAttributeNS8052670
Ref: 2aa98052670
Ref: library/xml dom xml dom Element getAttributeNodeNS8052934
Ref: 2aaa8052934
Ref: library/xml dom xml dom Element removeAttribute8053094
Ref: 2aab8053094
Ref: library/xml dom xml dom Element removeAttributeNode8053258
Ref: 2aad8053258
Ref: library/xml dom xml dom Element removeAttributeNS8053456
Ref: 2aae8053456
Ref: library/xml dom xml dom Element setAttribute8053671
Ref: 2aaf8053671
Ref: library/xml dom xml dom Element setAttributeNode8053769
Ref: 2ab08053769
Ref: library/xml dom xml dom Element setAttributeNodeNS8054119
Ref: 2ab28054119
Ref: library/xml dom xml dom Element setAttributeNS8054498
Ref: 2ab38054498
Node: Attr Objects8054740
Ref: library/xml dom attr-objects8054863
Ref: 2ab48054863
Ref: library/xml dom dom-attr-objects8054863
Ref: 2a6d8054863
Ref: library/xml dom xml dom Attr name8054978
Ref: 2ab58054978
Ref: library/xml dom xml dom Attr localName8055087
Ref: 2ab68055087
Ref: library/xml dom xml dom Attr prefix8055238
Ref: 2ab78055238
Ref: library/xml dom xml dom Attr value8055355
Ref: 2ab88055355
Node: NamedNodeMap Objects8055477
Ref: library/xml dom dom-attributelist-objects8055597
Ref: 2ab98055597
Ref: library/xml dom namednodemap-objects8055597
Ref: 2aba8055597
Ref: library/xml dom xml dom NamedNodeMap length8055716
Ref: 2abb8055716
Ref: library/xml dom xml dom NamedNodeMap item8055789
Ref: 2abc8055789
Node: Comment Objects8056276
Ref: library/xml dom comment-objects8056413
Ref: 2abd8056413
Ref: library/xml dom dom-comment-objects8056413
Ref: 2a6e8056413
Ref: library/xml dom xml dom Comment data8056585
Ref: 2abe8056585
Node: Text and CDATASection Objects8056800
Ref: library/xml dom dom-text-objects8056946
Ref: 2a6f8056946
Ref: library/xml dom text-and-cdatasection-objects8056946
Ref: 2abf8056946
Ref: library/xml dom xml dom Text data8057442
Ref: 2ac08057442
Node: ProcessingInstruction Objects8057934
Ref: library/xml dom dom-pi-objects8058079
Ref: 2a708058079
Ref: library/xml dom processinginstruction-objects8058079
Ref: 2ac18058079
Ref: library/xml dom xml dom ProcessingInstruction target8058291
Ref: 2ac28058291
Ref: library/xml dom xml dom ProcessingInstruction data8058456
Ref: 2ac38058456
Node: Exceptions<14>8058591
Ref: library/xml dom dom-exceptions8058698
Ref: 2ac48058698
Ref: library/xml dom exceptions8058698
Ref: 2ac58058698
Ref: library/xml dom xml dom DOMException8059377
Ref: 2ac68059377
Ref: library/xml dom xml dom DomstringSizeErr8059536
Ref: 2ac78059536
Ref: library/xml dom xml dom HierarchyRequestErr8059788
Ref: 2ac88059788
Ref: library/xml dom xml dom IndexSizeErr8059924
Ref: 2ac98059924
Ref: library/xml dom xml dom InuseAttributeErr8060063
Ref: 2ab18060063
Ref: library/xml dom xml dom InvalidAccessErr8060224
Ref: 2aca8060224
Ref: library/xml dom xml dom InvalidCharacterErr8060354
Ref: 2acb8060354
Ref: library/xml dom xml dom InvalidModificationErr8060711
Ref: 2acc8060711
Ref: library/xml dom xml dom InvalidStateErr8060822
Ref: 2acd8060822
Ref: library/xml dom xml dom NamespaceErr8060962
Ref: 2ace8060962
Ref: library/xml dom xml dom NotFoundErr8061168
Ref: 2aac8061168
Ref: library/xml dom xml dom NotSupportedErr8061396
Ref: 2acf8061396
Ref: library/xml dom xml dom NoDataAllowedErr8061535
Ref: 2ad08061535
Ref: library/xml dom xml dom NoModificationAllowedErr8061660
Ref: 2ad18061660
Ref: library/xml dom xml dom SyntaxErr8061823
Ref: 2ad28061823
Ref: library/xml dom xml dom WrongDocumentErr8061915
Ref: 2ad38061915
Ref: Exceptions<14>-Footnote-18064953
Node: Conformance8064998
Ref: library/xml dom conformance8065114
Ref: 2ad48065114
Ref: library/xml dom dom-conformance8065114
Ref: 2a5e8065114
Node: Type Mapping8065371
Ref: library/xml dom dom-type-mapping8065456
Ref: 2ad58065456
Ref: library/xml dom type-mapping8065456
Ref: 2ad68065456
Node: Accessor Methods8066281
Ref: library/xml dom accessor-methods8066366
Ref: 2ad78066366
Ref: library/xml dom dom-accessor-methods8066366
Ref: 2ad88066366
Node: xml dom minidom --- Minimal DOM implementation8068222
Ref: library/xml dom minidom doc8068456
Ref: 2ad98068456
Ref: library/xml dom minidom module-xml dom minidom8068456
Ref: 1368068456
Ref: library/xml dom minidom xml-dom-minidom-minimal-dom-implementation8068456
Ref: 2ada8068456
Ref: library/xml dom minidom xml dom minidom parse8069793
Ref: 2adb8069793
Ref: library/xml dom minidom xml dom minidom parseString8070360
Ref: 2adc8070360
Ref: xml dom minidom --- Minimal DOM implementation-Footnote-18072927
Ref: xml dom minidom --- Minimal DOM implementation-Footnote-28073001
Node: DOM Objects8073048
Ref: library/xml dom minidom dom-objects8073162
Ref: 2add8073162
Ref: library/xml dom minidom minidom-objects8073162
Ref: 2ade8073162
Ref: library/xml dom minidom xml dom minidom Node unlink8073397
Ref: 2adf8073397
Ref: library/xml dom minidom xml dom minidom Node writexml8074179
Ref: 2ae08074179
Ref: library/xml dom minidom xml dom minidom Node toxml8074956
Ref: 2ae18074956
Ref: library/xml dom minidom xml dom minidom Node toprettyxml8075594
Ref: 2ae28075594
Ref: DOM Objects-Footnote-18076154
Node: DOM Example8076553
Ref: library/xml dom minidom dom-example8076704
Ref: 2ae38076704
Ref: library/xml dom minidom id28076704
Ref: 2ae48076704
Node: minidom and the DOM standard8078744
Ref: library/xml dom minidom minidom-and-dom8078875
Ref: 2ae58078875
Ref: library/xml dom minidom minidom-and-the-dom-standard8078875
Ref: 2ae68078875
Node: xml dom pulldom --- Support for building partial DOM trees8081525
Ref: library/xml dom pulldom doc8081754
Ref: 2ae78081754
Ref: library/xml dom pulldom module-xml dom pulldom8081754
Ref: 1378081754
Ref: library/xml dom pulldom xml-dom-pulldom-support-for-building-partial-dom-trees8081754
Ref: 2ae88081754
Ref: library/xml dom pulldom xml dom pulldom PullDom8084478
Ref: 2aea8084478
Ref: library/xml dom pulldom xml dom pulldom SAX2DOM8084600
Ref: 2aec8084600
Ref: library/xml dom pulldom xml dom pulldom parse8084722
Ref: 2aed8084722
Ref: library/xml dom pulldom xml dom pulldom parseString8085312
Ref: 2aef8085312
Ref: library/xml dom pulldom xml dom pulldom default_bufsize8085462
Ref: 2af08085462
Ref: xml dom pulldom --- Support for building partial DOM trees-Footnote-18085775
Node: DOMEventStream Objects8085849
Ref: library/xml dom pulldom domeventstream-objects8085966
Ref: 2af18085966
Ref: library/xml dom pulldom id18085966
Ref: 2af28085966
Ref: library/xml dom pulldom xml dom pulldom DOMEventStream8086031
Ref: 27e8086031
Ref: library/xml dom pulldom xml dom pulldom DOMEventStream getEvent8086190
Ref: 2af38086190
Ref: library/xml dom pulldom xml dom pulldom DOMEventStream expandNode8086688
Ref: 2ae98086688
Ref: library/xml dom pulldom xml dom pulldom DOMEventStream reset8087408
Ref: 2af48087408
Node: xml sax --- Support for SAX2 parsers8087441
Ref: library/xml sax doc8087673
Ref: 2af58087673
Ref: library/xml sax module-xml sax8087673
Ref: 13c8087673
Ref: library/xml sax xml-sax-support-for-sax2-parsers8087673
Ref: 2af68087673
Ref: library/xml sax xml sax make_parser8088754
Ref: 102d8088754
Ref: library/xml sax xml sax parse8089241
Ref: fe68089241
Ref: library/xml sax xml sax parseString8089834
Ref: 7988089834
Ref: library/xml sax xml sax SAXException8091743
Ref: 2afc8091743
Ref: library/xml sax xml sax SAXParseException8092612
Ref: 2afa8092612
Ref: library/xml sax xml sax SAXNotRecognizedException8093020
Ref: 2afd8093020
Ref: library/xml sax xml sax SAXNotSupportedException8093319
Ref: 2afe8093319
Ref: xml sax --- Support for SAX2 parsers-Footnote-18094329
Ref: xml sax --- Support for SAX2 parsers-Footnote-28094405
Node: SAXException Objects8094440
Ref: library/xml sax sax-exception-objects8094533
Ref: 2aff8094533
Ref: library/xml sax saxexception-objects8094533
Ref: 2b008094533
Ref: library/xml sax xml sax SAXException getMessage8094673
Ref: 2b018094673
Ref: library/xml sax xml sax SAXException getException8094789
Ref: 2b028094789
Node: xml sax handler --- Base classes for SAX handlers8094899
Ref: library/xml sax handler doc8095107
Ref: 2b038095107
Ref: library/xml sax handler module-xml sax handler8095107
Ref: 13d8095107
Ref: library/xml sax handler xml-sax-handler-base-classes-for-sax-handlers8095107
Ref: 2b048095107
Ref: library/xml sax handler xml sax handler ContentHandler8095794
Ref: 2aeb8095794
Ref: library/xml sax handler xml sax handler DTDHandler8096035
Ref: 2b058096035
Ref: library/xml sax handler xml sax handler EntityResolver8096221
Ref: 2b068096221
Ref: library/xml sax handler xml sax handler ErrorHandler8096504
Ref: 2af98096504
Ref: library/xml sax handler xml sax handler feature_namespaces8096902
Ref: 2b078096902
Ref: library/xml sax handler xml sax handler feature_namespace_prefixes8097230
Ref: 2b088097230
Ref: library/xml sax handler xml sax handler feature_string_interning8097663
Ref: 2b098097663
Ref: library/xml sax handler xml sax handler feature_validation8098082
Ref: 2b0a8098082
Ref: library/xml sax handler xml sax handler feature_external_ges8098425
Ref: 2af88098425
Ref: library/xml sax handler xml sax handler feature_external_pes8098742
Ref: 2b0b8098742
Ref: library/xml sax handler xml sax handler all_features8099127
Ref: 2b0c8099127
Ref: library/xml sax handler xml sax handler property_lexical_handler8099195
Ref: 2b0d8099195
Ref: library/xml sax handler xml sax handler property_declaration_handler8099519
Ref: 2b0e8099519
Ref: library/xml sax handler xml sax handler property_dom_node8099881
Ref: 2b0f8099881
Ref: library/xml sax handler xml sax handler property_xml_string8100275
Ref: 2b108100275
Ref: library/xml sax handler xml sax handler all_properties8100548
Ref: 2b118100548
Ref: xml sax handler --- Base classes for SAX handlers-Footnote-18100778
Node: ContentHandler Objects8100852
Ref: library/xml sax handler content-handler-objects8100987
Ref: 2b128100987
Ref: library/xml sax handler contenthandler-objects8100987
Ref: 2b138100987
Ref: library/xml sax handler xml sax handler ContentHandler setDocumentLocator8101241
Ref: 2b148101241
Ref: library/xml sax handler xml sax handler ContentHandler startDocument8102322
Ref: 2b158102322
Ref: library/xml sax handler xml sax handler ContentHandler endDocument8102606
Ref: 2b168102606
Ref: library/xml sax handler xml sax handler ContentHandler startPrefixMapping8102980
Ref: 2b178102980
Ref: library/xml sax handler xml sax handler ContentHandler endPrefixMapping8104188
Ref: 2b188104188
Ref: library/xml sax handler xml sax handler ContentHandler startElement8104537
Ref: 2b198104537
Ref: library/xml sax handler xml sax handler ContentHandler endElement8105184
Ref: 2b1a8105184
Ref: library/xml sax handler xml sax handler ContentHandler startElementNS8105418
Ref: 2b1c8105418
Ref: library/xml sax handler xml sax handler ContentHandler endElementNS8106412
Ref: 2b1e8106412
Ref: library/xml sax handler xml sax handler ContentHandler characters8106691
Ref: 2b1f8106691
Ref: library/xml sax handler xml sax handler ContentHandler ignorableWhitespace8107726
Ref: 2b208107726
Ref: library/xml sax handler xml sax handler ContentHandler processingInstruction8108399
Ref: 2b218108399
Ref: library/xml sax handler xml sax handler ContentHandler skippedEntity8108865
Ref: 2b228108865
Node: DTDHandler Objects8109371
Ref: library/xml sax handler dtd-handler-objects8109537
Ref: 2b238109537
Ref: library/xml sax handler dtdhandler-objects8109537
Ref: 2b248109537
Ref: library/xml sax handler xml sax handler DTDHandler notationDecl8109662
Ref: 2b258109662
Ref: library/xml sax handler xml sax handler DTDHandler unparsedEntityDecl8109775
Ref: 2b268109775
Node: EntityResolver Objects8109919
Ref: library/xml sax handler entity-resolver-objects8110083
Ref: 2b278110083
Ref: library/xml sax handler entityresolver-objects8110083
Ref: 2b288110083
Ref: library/xml sax handler xml sax handler EntityResolver resolveEntity8110150
Ref: 2b298110150
Node: ErrorHandler Objects8110424
Ref: library/xml sax handler errorhandler-objects8110561
Ref: 2b2a8110561
Ref: library/xml sax handler sax-error-handler8110561
Ref: 2b2b8110561
Ref: library/xml sax handler xml sax handler ErrorHandler error8111208
Ref: 2b2c8111208
Ref: library/xml sax handler xml sax handler ErrorHandler fatalError8111583
Ref: 2b2d8111583
Ref: library/xml sax handler xml sax handler ErrorHandler warning8111775
Ref: 2b2e8111775
Node: xml sax saxutils --- SAX Utilities8112126
Ref: library/xml sax utils doc8112345
Ref: 2b2f8112345
Ref: library/xml sax utils module-xml sax saxutils8112345
Ref: 13e8112345
Ref: library/xml sax utils xml-sax-saxutils-sax-utilities8112345
Ref: 2b308112345
Ref: library/xml sax utils xml sax saxutils escape8112732
Ref: 2b318112732
Ref: library/xml sax utils xml sax saxutils unescape8113184
Ref: 2b328113184
Ref: library/xml sax utils xml sax saxutils quoteattr8113649
Ref: 2b338113649
Ref: library/xml sax utils xml sax saxutils XMLGenerator8114556
Ref: 2b348114556
Ref: library/xml sax utils xml sax saxutils XMLFilterBase8115408
Ref: 2b358115408
Ref: library/xml sax utils xml sax saxutils prepare_input_source8115831
Ref: 2b368115831
Ref: xml sax saxutils --- SAX Utilities-Footnote-18116318
Node: xml sax xmlreader --- Interface for XML parsers8116394
Ref: library/xml sax reader doc8116614
Ref: 2b378116614
Ref: library/xml sax reader module-xml sax xmlreader8116614
Ref: 13f8116614
Ref: library/xml sax reader xml-sax-xmlreader-interface-for-xml-parsers8116614
Ref: 2b388116614
Ref: library/xml sax reader xml sax xmlreader XMLReader8117114
Ref: 2aee8117114
Ref: library/xml sax reader xml sax xmlreader IncrementalParser8117211
Ref: 2b398117211
Ref: library/xml sax reader xml sax xmlreader Locator8118339
Ref: 2afb8118339
Ref: library/xml sax reader xml sax xmlreader InputSource8118673
Ref: 7978118673
Ref: library/xml sax reader xml sax xmlreader AttributesImpl8119442
Ref: 2b3b8119442
Ref: library/xml sax reader xml sax xmlreader AttributesNSImpl8120042
Ref: 2b3c8120042
Ref: xml sax xmlreader --- Interface for XML parsers-Footnote-18120800
Node: XMLReader Objects8120877
Ref: library/xml sax reader id18121012
Ref: 2b3d8121012
Ref: library/xml sax reader xmlreader-objects8121012
Ref: 2b3e8121012
Ref: library/xml sax reader xml sax xmlreader XMLReader parse8121139
Ref: 2b3a8121139
Ref: library/xml sax reader xml sax xmlreader XMLReader getContentHandler8121716
Ref: 2b3f8121716
Ref: library/xml sax reader xml sax xmlreader XMLReader setContentHandler8121819
Ref: 2b408121819
Ref: library/xml sax reader xml sax xmlreader XMLReader getDTDHandler8122008
Ref: 2b418122008
Ref: library/xml sax reader xml sax xmlreader XMLReader setDTDHandler8122103
Ref: 2b428122103
Ref: library/xml sax reader xml sax xmlreader XMLReader getEntityResolver8122276
Ref: 2b438122276
Ref: library/xml sax reader xml sax xmlreader XMLReader setEntityResolver8122379
Ref: 2b448122379
Ref: library/xml sax reader xml sax xmlreader XMLReader getErrorHandler8122677
Ref: 2b458122677
Ref: library/xml sax reader xml sax xmlreader XMLReader setErrorHandler8122776
Ref: 2b468122776
Ref: library/xml sax reader xml sax xmlreader XMLReader setLocale8122986
Ref: 2b478122986
Ref: library/xml sax reader xml sax xmlreader XMLReader getFeature8123358
Ref: 2b488123358
Ref: library/xml sax reader xml sax xmlreader XMLReader setFeature8123646
Ref: 2af78123646
Ref: library/xml sax reader xml sax xmlreader XMLReader getProperty8123941
Ref: 2b498123941
Ref: library/xml sax reader xml sax xmlreader XMLReader setProperty8124238
Ref: 2b4a8124238
Node: IncrementalParser Objects8124538
Ref: library/xml sax reader incremental-parser-objects8124697
Ref: 2b4b8124697
Ref: library/xml sax reader incrementalparser-objects8124697
Ref: 2b4c8124697
Ref: library/xml sax reader xml sax xmlreader IncrementalParser feed8124855
Ref: 2b4d8124855
Ref: library/xml sax reader xml sax xmlreader IncrementalParser close8124937
Ref: 2b4e8124937
Ref: library/xml sax reader xml sax xmlreader IncrementalParser reset8125182
Ref: 2b4f8125182
Node: Locator Objects8125450
Ref: library/xml sax reader id28125611
Ref: 2b508125611
Ref: library/xml sax reader locator-objects8125611
Ref: 2b518125611
Ref: library/xml sax reader xml sax xmlreader Locator getColumnNumber8125722
Ref: 2b528125722
Ref: library/xml sax reader xml sax xmlreader Locator getLineNumber8125831
Ref: 2b538125831
Ref: library/xml sax reader xml sax xmlreader Locator getPublicId8125936
Ref: 2b548125936
Ref: library/xml sax reader xml sax xmlreader Locator getSystemId8126036
Ref: 2b558126036
Node: InputSource Objects8126136
Ref: library/xml sax reader input-source-objects8126296
Ref: 2b568126296
Ref: library/xml sax reader inputsource-objects8126296
Ref: 2b578126296
Ref: library/xml sax reader xml sax xmlreader InputSource setPublicId8126357
Ref: 2b588126357
Ref: library/xml sax reader xml sax xmlreader InputSource getPublicId8126470
Ref: 2b598126470
Ref: library/xml sax reader xml sax xmlreader InputSource setSystemId8126584
Ref: 2b5a8126584
Ref: library/xml sax reader xml sax xmlreader InputSource getSystemId8126697
Ref: 2b5b8126697
Ref: library/xml sax reader xml sax xmlreader InputSource setEncoding8126811
Ref: 2b5c8126811
Ref: library/xml sax reader xml sax xmlreader InputSource getEncoding8127203
Ref: 2b5d8127203
Ref: library/xml sax reader xml sax xmlreader InputSource setByteStream8127303
Ref: 2b5e8127303
Ref: library/xml sax reader xml sax xmlreader InputSource getByteStream8127742
Ref: 2b5f8127742
Ref: library/xml sax reader xml sax xmlreader InputSource setCharacterStream8127956
Ref: 2b608127956
Ref: library/xml sax reader xml sax xmlreader InputSource getCharacterStream8128276
Ref: 2b618128276
Node: The Attributes Interface8128383
Ref: library/xml sax reader attributes-objects8128554
Ref: 2b1b8128554
Ref: library/xml sax reader the-attributes-interface8128554
Ref: 2b628128554
Ref: library/xml sax reader xml sax xmlreader Attributes getLength8128882
Ref: 2b638128882
Ref: library/xml sax reader xml sax xmlreader Attributes getNames8128964
Ref: 2b648128964
Ref: library/xml sax reader xml sax xmlreader Attributes getType8129048
Ref: 2b658129048
Ref: library/xml sax reader xml sax xmlreader Attributes getValue8129179
Ref: 2b668129179
Node: The AttributesNS Interface8129269
Ref: library/xml sax reader attributes-ns-objects8129412
Ref: 2b1d8129412
Ref: library/xml sax reader the-attributesns-interface8129412
Ref: 2b678129412
Ref: library/xml sax reader xml sax xmlreader AttributesNS getValueByQName8129745
Ref: 2b688129745
Ref: library/xml sax reader xml sax xmlreader AttributesNS getNameByQName8129845
Ref: 2b698129845
Ref: library/xml sax reader xml sax xmlreader AttributesNS getQNameByName8129974
Ref: 2b6a8129974
Ref: library/xml sax reader xml sax xmlreader AttributesNS getQNames8130101
Ref: 2b6b8130101
Node: xml parsers expat --- Fast XML parsing using Expat8130198
Ref: library/pyexpat doc8130375
Ref: 2b6c8130375
Ref: library/pyexpat module-xml parsers expat8130375
Ref: 1398130375
Ref: library/pyexpat xml-parsers-expat-fast-xml-parsing-using-expat8130375
Ref: 2b6d8130375
Ref: library/pyexpat xml parsers expat ExpatError8131428
Ref: c128131428
Ref: library/pyexpat xml parsers expat error8131635
Ref: 2b6f8131635
Ref: library/pyexpat xml parsers expat XMLParserType8131711
Ref: 2b708131711
Ref: library/pyexpat xml parsers expat ErrorString8131908
Ref: 2b728131908
Ref: library/pyexpat xml parsers expat ParserCreate8132029
Ref: 2b718132029
Ref: xml parsers expat --- Fast XML parsing using Expat-Footnote-18134462
Ref: xml parsers expat --- Fast XML parsing using Expat-Footnote-28134767
Node: XMLParser Objects<2>8134800
Ref: library/pyexpat id28134937
Ref: 2b738134937
Ref: library/pyexpat xmlparser-objects8134937
Ref: 2b748134937
Ref: library/pyexpat xml parsers expat xmlparser Parse8135047
Ref: 2b758135047
Ref: library/pyexpat xml parsers expat xmlparser ParseFile8135431
Ref: 2b768135431
Ref: library/pyexpat xml parsers expat xmlparser SetBase8135657
Ref: 2b778135657
Ref: library/pyexpat xml parsers expat xmlparser GetBase8136079
Ref: 2b7b8136079
Ref: library/pyexpat xml parsers expat xmlparser GetInputContext8136283
Ref: 2b7c8136283
Ref: library/pyexpat xml parsers expat xmlparser ExternalEntityParserCreate8136572
Ref: 2b7d8136572
Ref: library/pyexpat xml parsers expat xmlparser SetParamEntityParsing8137091
Ref: 2b808137091
Ref: library/pyexpat xml parsers expat xmlparser UseForeignDTD8137462
Ref: 2b818137462
Ref: library/pyexpat xml parsers expat xmlparser buffer_size8138510
Ref: 2b848138510
Ref: library/pyexpat xml parsers expat xmlparser buffer_text8138769
Ref: 2b858138769
Ref: library/pyexpat xml parsers expat xmlparser buffer_used8139218
Ref: 2b878139218
Ref: library/pyexpat xml parsers expat xmlparser ordered_attributes8139488
Ref: 2b7e8139488
Ref: library/pyexpat xml parsers expat xmlparser specified_attributes8139977
Ref: 2b7f8139977
Ref: library/pyexpat xml parsers expat xmlparser ErrorByteIndex8140780
Ref: 2b888140780
Ref: library/pyexpat xml parsers expat xmlparser ErrorCode8140863
Ref: 2b898140863
Ref: library/pyexpat xml parsers expat xmlparser ErrorColumnNumber8141091
Ref: 2b8a8141091
Ref: library/pyexpat xml parsers expat xmlparser ErrorLineNumber8141180
Ref: 2b8b8141180
Ref: library/pyexpat xml parsers expat xmlparser CurrentByteIndex8141670
Ref: 2b8c8141670
Ref: library/pyexpat xml parsers expat xmlparser CurrentColumnNumber8141756
Ref: 2b8d8141756
Ref: library/pyexpat xml parsers expat xmlparser CurrentLineNumber8141848
Ref: 2b8e8141848
Ref: library/pyexpat xml parsers expat xmlparser XmlDeclHandler8142258
Ref: 2b8f8142258
Ref: library/pyexpat xml parsers expat xmlparser StartDoctypeDeclHandler8142873
Ref: 2b828142873
Ref: library/pyexpat xml parsers expat xmlparser EndDoctypeDeclHandler8143432
Ref: 2b838143432
Ref: library/pyexpat xml parsers expat xmlparser ElementDeclHandler8143604
Ref: 2b908143604
Ref: library/pyexpat xml parsers expat xmlparser AttlistDeclHandler8143824
Ref: 2b918143824
Ref: library/pyexpat xml parsers expat xmlparser StartElementHandler8144734
Ref: 2b928144734
Ref: library/pyexpat xml parsers expat xmlparser EndElementHandler8145137
Ref: 2b938145137
Ref: library/pyexpat xml parsers expat xmlparser ProcessingInstructionHandler8145234
Ref: 2b948145234
Ref: library/pyexpat xml parsers expat xmlparser CharacterDataHandler8145354
Ref: 2b868145354
Ref: library/pyexpat xml parsers expat xmlparser UnparsedEntityDeclHandler8145782
Ref: 2b7a8145782
Ref: library/pyexpat xml parsers expat xmlparser EntityDeclHandler8146181
Ref: 2b978146181
Ref: library/pyexpat xml parsers expat xmlparser NotationDeclHandler8146932
Ref: 2b798146932
Ref: library/pyexpat xml parsers expat xmlparser StartNamespaceDeclHandler8147229
Ref: 2b988147229
Ref: library/pyexpat xml parsers expat xmlparser EndNamespaceDeclHandler8147513
Ref: 2b998147513
Ref: library/pyexpat xml parsers expat xmlparser CommentHandler8148042
Ref: 2b9a8148042
Ref: library/pyexpat xml parsers expat xmlparser StartCdataSectionHandler8148234
Ref: 2b958148234
Ref: library/pyexpat xml parsers expat xmlparser EndCdataSectionHandler8148477
Ref: 2b968148477
Ref: library/pyexpat xml parsers expat xmlparser DefaultHandler8148576
Ref: 2b9b8148576
Ref: library/pyexpat xml parsers expat xmlparser DefaultHandlerExpand8148867
Ref: 2b9c8148867
Ref: library/pyexpat xml parsers expat xmlparser NotStandaloneHandler8149113
Ref: 2b9d8149113
Ref: library/pyexpat xml parsers expat xmlparser ExternalEntityRefHandler8149641
Ref: 2b788149641
Node: ExpatError Exceptions8150703
Ref: library/pyexpat expaterror-exceptions8150860
Ref: 2b9e8150860
Ref: library/pyexpat expaterror-objects8150860
Ref: 2b6e8150860
Ref: library/pyexpat xml parsers expat ExpatError code8151001
Ref: 2b9f8151001
Ref: library/pyexpat xml parsers expat ExpatError lineno8151647
Ref: 2ba28151647
Ref: library/pyexpat xml parsers expat ExpatError offset8151771
Ref: 2ba38151771
Node: Example<12>8151909
Ref: library/pyexpat example8152072
Ref: 2ba48152072
Ref: library/pyexpat expat-example8152072
Ref: 2ba58152072
Node: Content Model Descriptions8153170
Ref: library/pyexpat content-model-descriptions8153333
Ref: 2ba68153333
Ref: library/pyexpat expat-content-models8153333
Ref: 2ba78153333
Ref: library/pyexpat module-xml parsers expat model8153333
Ref: 13b8153333
Node: Expat error constants8155176
Ref: library/pyexpat expat-error-constants8155319
Ref: 2ba88155319
Ref: library/pyexpat expat-errors8155319
Ref: 2ba98155319
Ref: library/pyexpat module-xml parsers expat errors8155319
Ref: 13a8155319
Ref: library/pyexpat xml parsers expat errors codes8155911
Ref: 2ba18155911
Ref: library/pyexpat xml parsers expat errors messages8156046
Ref: 2ba08156046
Ref: library/pyexpat xml parsers expat errors XML_ERROR_ASYNC_ENTITY8156197
Ref: 2baa8156197
Ref: library/pyexpat xml parsers expat errors XML_ERROR_ATTRIBUTE_EXTERNAL_ENTITY_REF8156256
Ref: 2bab8156256
Ref: library/pyexpat xml parsers expat errors XML_ERROR_BAD_CHAR_REF8156457
Ref: 2bac8156457
Ref: library/pyexpat xml parsers expat errors XML_ERROR_BINARY_ENTITY_REF8156652
Ref: 2bad8156652
Ref: library/pyexpat xml parsers expat errors XML_ERROR_DUPLICATE_ATTRIBUTE8156826
Ref: 2bae8156826
Ref: library/pyexpat xml parsers expat errors XML_ERROR_INCORRECT_ENCODING8156951
Ref: 2baf8156951
Ref: library/pyexpat xml parsers expat errors XML_ERROR_INVALID_TOKEN8157016
Ref: 2bb08157016
Ref: library/pyexpat xml parsers expat errors XML_ERROR_JUNK_AFTER_DOC_ELEMENT8157230
Ref: 2bb18157230
Ref: library/pyexpat xml parsers expat errors XML_ERROR_MISPLACED_XML_PI8157379
Ref: 2bb28157379
Ref: library/pyexpat xml parsers expat errors XML_ERROR_NO_ELEMENTS8157532
Ref: 2bb38157532
Ref: library/pyexpat xml parsers expat errors XML_ERROR_NO_MEMORY8157707
Ref: 2bb48157707
Ref: library/pyexpat xml parsers expat errors XML_ERROR_PARAM_ENTITY_REF8157819
Ref: 2bb58157819
Ref: library/pyexpat xml parsers expat errors XML_ERROR_PARTIAL_CHAR8157953
Ref: 2bb68157953
Ref: library/pyexpat xml parsers expat errors XML_ERROR_RECURSIVE_ENTITY_REF8158066
Ref: 2bb78158066
Ref: library/pyexpat xml parsers expat errors XML_ERROR_SYNTAX8158268
Ref: 2bb88158268
Ref: library/pyexpat xml parsers expat errors XML_ERROR_TAG_MISMATCH8158374
Ref: 2bb98158374
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNCLOSED_TOKEN8158494
Ref: 2bba8158494
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNDEFINED_ENTITY8158678
Ref: 2bbb8158678
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNKNOWN_ENCODING8158804
Ref: 2bbc8158804
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNCLOSED_CDATA_SECTION8158922
Ref: 2bbd8158922
Ref: library/pyexpat xml parsers expat errors XML_ERROR_EXTERNAL_ENTITY_HANDLING8159036
Ref: 2bbe8159036
Ref: library/pyexpat xml parsers expat errors XML_ERROR_NOT_STANDALONE8159107
Ref: 2bbf8159107
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNEXPECTED_STATE8159366
Ref: 2bc08159366
Ref: library/pyexpat xml parsers expat errors XML_ERROR_ENTITY_DECLARED_IN_PE8159429
Ref: 2bc18159429
Ref: library/pyexpat xml parsers expat errors XML_ERROR_FEATURE_REQUIRES_XML_DTD8159497
Ref: 2bc28159497
Ref: library/pyexpat xml parsers expat errors XML_ERROR_CANT_CHANGE_FEATURE_ONCE_PARSING8159803
Ref: 2bc38159803
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNBOUND_PREFIX8160076
Ref: 2bc48160076
Ref: library/pyexpat xml parsers expat errors XML_ERROR_UNDECLARING_PREFIX8160218
Ref: 2bc58160218
Ref: library/pyexpat xml parsers expat errors XML_ERROR_INCOMPLETE_PE8160379
Ref: 2bc68160379
Ref: library/pyexpat xml parsers expat errors XML_ERROR_XML_DECL8160493
Ref: 2bc78160493
Ref: library/pyexpat xml parsers expat errors XML_ERROR_TEXT_DECL8160605
Ref: 2bc88160605
Ref: library/pyexpat xml parsers expat errors XML_ERROR_PUBLICID8160741
Ref: 2bc98160741
Ref: library/pyexpat xml parsers expat errors XML_ERROR_SUSPENDED8160863
Ref: 2bca8160863
Ref: library/pyexpat xml parsers expat errors XML_ERROR_NOT_SUSPENDED8161087
Ref: 2bcb8161087
Ref: library/pyexpat xml parsers expat errors XML_ERROR_ABORTED8161239
Ref: 2bcc8161239
Ref: library/pyexpat xml parsers expat errors XML_ERROR_FINISHED8161351
Ref: 2bcd8161351
Ref: library/pyexpat xml parsers expat errors XML_ERROR_SUSPEND_PE8161597
Ref: 2bce8161597
Node: Internet Protocols and Support8161667
Ref: library/internet doc8161844
Ref: 2bcf8161844
Ref: library/internet internet8161844
Ref: 2bd08161844
Ref: library/internet internet-protocols-and-support8161844
Ref: 2bd18161844
Node: webbrowser --- Convenient Web-browser controller8164502
Ref: library/webbrowser doc8164666
Ref: 2bd28164666
Ref: library/webbrowser module-webbrowser8164666
Ref: 12a8164666
Ref: library/webbrowser webbrowser-convenient-web-browser-controller8164666
Ref: 2bd38164666
Ref: library/webbrowser webbrowser Error8166611
Ref: 2bd58166611
Ref: library/webbrowser webbrowser open8166739
Ref: 2bd48166739
Ref: library/webbrowser webbrowser open_new8167540
Ref: 2bd68167540
Ref: library/webbrowser webbrowser open_new_tab8167704
Ref: 2bd78167704
Ref: library/webbrowser webbrowser get8167876
Ref: 2bd88167876
Ref: library/webbrowser webbrowser register8168102
Ref: 2bd98168102
Ref: webbrowser --- Convenient Web-browser controller-Footnote-18174618
Ref: webbrowser --- Convenient Web-browser controller-Footnote-28174687
Node: Browser Controller Objects8174824
Ref: library/webbrowser browser-controller-objects8174935
Ref: 2bda8174935
Ref: library/webbrowser browser-controllers8174935
Ref: 2bdb8174935
Ref: library/webbrowser webbrowser controller open8175115
Ref: 2bdc8175115
Ref: library/webbrowser webbrowser controller open_new8175381
Ref: 2bdd8175381
Ref: library/webbrowser webbrowser controller open_new_tab8175606
Ref: 2bde8175606
Node: cgi --- Common Gateway Interface support8175821
Ref: library/cgi doc8176037
Ref: 2bdf8176037
Ref: library/cgi cgi-common-gateway-interface-support8176037
Ref: 2be08176037
Ref: library/cgi module-cgi8176037
Ref: 168176037
Ref: cgi --- Common Gateway Interface support-Footnote-18176692
Node: 簡介<10>8176754
Ref: library/cgi introduction8176870
Ref: 2be18176870
Ref: library/cgi cgi-intro8176901
Ref: 2be28176901
Node: Using the cgi module8178566
Ref: library/cgi id18178713
Ref: 2be38178713
Ref: library/cgi using-the-cgi-module8178713
Ref: 2be48178713
Node: Higher Level Interface8184599
Ref: library/cgi higher-level-interface8184748
Ref: 2be68184748
Ref: library/cgi cgi FieldStorage getfirst8187062
Ref: 2be78187062
Ref: library/cgi cgi FieldStorage getlist8187642
Ref: 2be58187642
Ref: Higher Level Interface-Footnote-18188222
Node: Functions<8>8188480
Ref: library/cgi functions8188630
Ref: 2be88188630
Ref: library/cgi functions-in-cgi-module8188630
Ref: 2be98188630
Ref: library/cgi cgi parse8188812
Ref: 2ee8188812
Ref: library/cgi cgi parse_multipart8189233
Ref: 2ef8189233
Ref: library/cgi cgi parse_header8190186
Ref: 2bea8190186
Ref: library/cgi cgi test8190335
Ref: 2beb8190335
Ref: library/cgi cgi print_environ8190518
Ref: 2bec8190518
Ref: library/cgi cgi print_form8190596
Ref: 2bed8190596
Ref: library/cgi cgi print_directory8190660
Ref: 2bee8190660
Ref: library/cgi cgi print_environ_usage8190740
Ref: 2bef8190740
Node: Caring about security8190854
Ref: library/cgi caring-about-security8191025
Ref: 2bf08191025
Ref: library/cgi cgi-security8191025
Ref: 2bf18191025
Node: Installing your CGI script on a Unix system8191810
Ref: library/cgi installing-your-cgi-script-on-a-unix-system8191992
Ref: 2bf28191992
Node: Testing your CGI script8194006
Ref: library/cgi testing-your-cgi-script8194188
Ref: 2bf38194188
Node: Debugging CGI scripts8194802
Ref: library/cgi debugging-cgi-scripts8194970
Ref: 2bf48194970
Node: Common problems and solutions8198103
Ref: library/cgi common-problems-and-solutions8198239
Ref: 2bf58198239
Node: cgitb --- Traceback manager for CGI scripts8199594
Ref: library/cgitb doc8199817
Ref: 2bf68199817
Ref: library/cgitb cgitb-traceback-manager-for-cgi-scripts8199817
Ref: 2bf78199817
Ref: library/cgitb module-cgitb8199817
Ref: 178199817
Ref: library/cgitb cgitb enable8201007
Ref: 2bf88201007
Ref: library/cgitb cgitb text8201939
Ref: 2bf98201939
Ref: library/cgitb cgitb html8202365
Ref: 2bfa8202365
Ref: library/cgitb cgitb handler8202791
Ref: 2bfb8202791
Ref: cgitb --- Traceback manager for CGI scripts-Footnote-18203422
Node: wsgiref --- WSGI Utilities and Reference Implementation8203486
Ref: library/wsgiref doc8203700
Ref: 2bfc8203700
Ref: library/wsgiref module-wsgiref8203700
Ref: 12d8203700
Ref: library/wsgiref wsgiref-wsgi-utilities-and-reference-implementation8203700
Ref: 2bfd8203700
Ref: wsgiref --- WSGI Utilities and Reference Implementation-Footnote-18205521
Ref: wsgiref --- WSGI Utilities and Reference Implementation-Footnote-28205570
Node: wsgiref util -- WSGI environment utilities8205607
Ref: library/wsgiref module-wsgiref util8205795
Ref: 1318205795
Ref: library/wsgiref wsgiref-util-wsgi-environment-utilities8205795
Ref: 2bfe8205795
Ref: library/wsgiref wsgiref util guess_scheme8206252
Ref: 2bff8206252
Ref: library/wsgiref wsgiref util request_uri8206874
Ref: 2c008206874
Ref: library/wsgiref wsgiref util application_uri8207194
Ref: 2c018207194
Ref: library/wsgiref wsgiref util shift_path_info8207458
Ref: 2c028207458
Ref: library/wsgiref wsgiref util setup_testing_defaults8209116
Ref: 2c038209116
Ref: library/wsgiref wsgiref util is_hop_by_hop8210798
Ref: 2c048210798
Ref: library/wsgiref wsgiref util FileWrapper8210965
Ref: 27f8210965
Ref: wsgiref util -- WSGI environment utilities-Footnote-18212230
Ref: wsgiref util -- WSGI environment utilities-Footnote-28212279
Ref: wsgiref util -- WSGI environment utilities-Footnote-38212328
Ref: wsgiref util -- WSGI environment utilities-Footnote-48212377
Ref: wsgiref util -- WSGI environment utilities-Footnote-58212426
Node: wsgiref headers -- WSGI response header tools8212475
Ref: library/wsgiref module-wsgiref headers8212722
Ref: 12f8212722
Ref: library/wsgiref wsgiref-headers-wsgi-response-header-tools8212722
Ref: 2c058212722
Ref: library/wsgiref wsgiref headers Headers8212984
Ref: 7948212984
Ref: library/wsgiref wsgiref headers Headers get_all8215250
Ref: 2c068215250
Ref: library/wsgiref wsgiref headers Headers add_header8215693
Ref: 2c078215693
Ref: wsgiref headers -- WSGI response header tools-Footnote-18216827
Node: wsgiref simple_server -- a simple WSGI HTTP server8216876
Ref: library/wsgiref module-wsgiref simple_server8217126
Ref: 1308217126
Ref: library/wsgiref wsgiref-simple-server-a-simple-wsgi-http-server8217126
Ref: 2c088217126
Ref: library/wsgiref wsgiref simple_server make_server8217720
Ref: 2c098217720
Ref: library/wsgiref wsgiref simple_server demo_app8218558
Ref: 2c0a8218558
Ref: library/wsgiref wsgiref simple_server WSGIServer8218993
Ref: 2c0b8218993
Ref: library/wsgiref wsgiref simple_server WSGIServer set_app8219747
Ref: 2c0d8219747
Ref: library/wsgiref wsgiref simple_server WSGIServer get_app8219898
Ref: 2c0e8219898
Ref: library/wsgiref wsgiref simple_server WSGIRequestHandler8220247
Ref: 2c0f8220247
Ref: library/wsgiref wsgiref simple_server WSGIRequestHandler get_environ8220864
Ref: 2c108220864
Ref: library/wsgiref wsgiref simple_server WSGIRequestHandler get_stderr8221376
Ref: 2c118221376
Ref: library/wsgiref wsgiref simple_server WSGIRequestHandler handle8221565
Ref: 2c128221565
Ref: wsgiref simple_server -- a simple WSGI HTTP server-Footnote-18221842
Ref: wsgiref simple_server -- a simple WSGI HTTP server-Footnote-28221891
Node: wsgiref validate --- WSGI conformance checker8221940
Ref: library/wsgiref module-wsgiref validate8222192
Ref: 1328222192
Ref: library/wsgiref wsgiref-validate-wsgi-conformance-checker8222192
Ref: 2c138222192
Ref: library/wsgiref wsgiref validate validator8223095
Ref: 2c148223095
Ref: wsgiref validate --- WSGI conformance checker-Footnote-18225312
Ref: wsgiref validate --- WSGI conformance checker-Footnote-28225361
Ref: wsgiref validate --- WSGI conformance checker-Footnote-38225410
Node: wsgiref handlers -- server/gateway base classes8225459
Ref: library/wsgiref module-wsgiref handlers8225673
Ref: 12e8225673
Ref: library/wsgiref wsgiref-handlers-server-gateway-base-classes8225673
Ref: 2c158225673
Ref: library/wsgiref wsgiref handlers CGIHandler8226064
Ref: 2c168226064
Ref: library/wsgiref wsgiref handlers IISCGIHandler8226714
Ref: 2c188226714
Ref: library/wsgiref wsgiref handlers BaseCGIHandler8228088
Ref: 2c178228088
Ref: library/wsgiref wsgiref handlers SimpleHandler8228952
Ref: 2c198228952
Ref: library/wsgiref wsgiref handlers BaseHandler8229869
Ref: fd18229869
Ref: library/wsgiref wsgiref handlers BaseHandler run8230228
Ref: 2c1a8230228
Ref: library/wsgiref wsgiref handlers BaseHandler _write8230572
Ref: 2c1b8230572
Ref: library/wsgiref wsgiref handlers BaseHandler _flush8230923
Ref: 2c1c8230923
Ref: library/wsgiref wsgiref handlers BaseHandler get_stdin8231138
Ref: 2c1d8231138
Ref: library/wsgiref wsgiref handlers BaseHandler get_stderr8231309
Ref: 2c1e8231309
Ref: library/wsgiref wsgiref handlers BaseHandler add_cgi_vars8231483
Ref: 2c1f8231483
Ref: library/wsgiref wsgiref handlers BaseHandler wsgi_multithread8232035
Ref: 2c208232035
Ref: library/wsgiref wsgiref handlers BaseHandler wsgi_multiprocess8232322
Ref: 2c218232322
Ref: library/wsgiref wsgiref handlers BaseHandler wsgi_run_once8232611
Ref: 2c228232611
Ref: library/wsgiref wsgiref handlers BaseHandler os_environ8232850
Ref: 2c238232850
Ref: library/wsgiref wsgiref handlers BaseHandler server_software8233353
Ref: 2c248233353
Ref: library/wsgiref wsgiref handlers BaseHandler get_scheme8233925
Ref: 2c268233925
Ref: library/wsgiref wsgiref handlers BaseHandler setup_environ8234284
Ref: 2c278234284
Ref: library/wsgiref wsgiref handlers BaseHandler log_exception8234950
Ref: 2c298234950
Ref: library/wsgiref wsgiref handlers BaseHandler traceback_limit8235456
Ref: 2c2a8235456
Ref: library/wsgiref wsgiref handlers BaseHandler error_output8235675
Ref: 2c2b8235675
Ref: library/wsgiref wsgiref handlers BaseHandler error_status8236749
Ref: 2c2c8236749
Ref: library/wsgiref wsgiref handlers BaseHandler error_headers8236951
Ref: 2c2d8236951
Ref: library/wsgiref wsgiref handlers BaseHandler error_body8237240
Ref: 2c2e8237240
Ref: library/wsgiref wsgiref handlers BaseHandler wsgi_file_wrapper8237575
Ref: 2c288237575
Ref: library/wsgiref wsgiref handlers BaseHandler sendfile8237780
Ref: 2c2f8237780
Ref: library/wsgiref wsgiref handlers BaseHandler origin_server8238362
Ref: 2c258238362
Ref: library/wsgiref wsgiref handlers BaseHandler http_version8238885
Ref: 2c308238885
Ref: library/wsgiref wsgiref handlers read_environ8239104
Ref: b3b8239104
Ref: wsgiref handlers -- server/gateway base classes-Footnote-18240010
Ref: wsgiref handlers -- server/gateway base classes-Footnote-28240059
Ref: wsgiref handlers -- server/gateway base classes-Footnote-38240108
Ref: wsgiref handlers -- server/gateway base classes-Footnote-48240157
Ref: wsgiref handlers -- server/gateway base classes-Footnote-58240206
Node: Examples<20>8240255
Ref: library/wsgiref examples8240415
Ref: 2c318240415
Node: urllib --- URL handling modules8242983
Ref: library/urllib doc8243208
Ref: 2c328243208
Ref: library/urllib module-urllib8243208
Ref: 11e8243208
Ref: library/urllib urllib-url-handling-modules8243208
Ref: 2c338243208
Ref: urllib --- URL handling modules-Footnote-18243789
Node: urllib request --- Extensible library for opening URLs8243852
Ref: library/urllib request doc8244073
Ref: 2c348244073
Ref: library/urllib request module-urllib request8244073
Ref: 1218244073
Ref: library/urllib request urllib-request-extensible-library-for-opening-urls8244073
Ref: 2c358244073
Ref: library/urllib request urllib request urlopen8244683
Ref: 7918244683
Ref: library/urllib request urllib request install_opener8248944
Ref: 2c3c8248944
Ref: library/urllib request urllib request build_opener8249395
Ref: 2c3d8249395
Ref: library/urllib request urllib request pathname2url8250510
Ref: 2c458250510
Ref: library/urllib request urllib request url2pathname8250807
Ref: 2c468250807
Ref: library/urllib request urllib request getproxies8251061
Ref: 2c478251061
Ref: library/urllib request urllib request Request8252216
Ref: 8fb8252216
Ref: library/urllib request urllib request OpenerDirector8256613
Ref: 2c3a8256613
Ref: library/urllib request urllib request BaseHandler8256833
Ref: 2c3e8256833
Ref: library/urllib request urllib request HTTPDefaultErrorHandler8256994
Ref: 2c408256994
Ref: library/urllib request urllib request HTTPRedirectHandler8257187
Ref: 2c418257187
Ref: library/urllib request urllib request HTTPCookieProcessor8257273
Ref: 2c498257273
Ref: library/urllib request urllib request ProxyHandler8257376
Ref: f808257376
Ref: library/urllib request urllib request HTTPPasswordMgr8258491
Ref: 2c4a8258491
Ref: library/urllib request urllib request HTTPPasswordMgrWithDefaultRealm8258609
Ref: 2c4b8258609
Ref: library/urllib request urllib request HTTPPasswordMgrWithPriorAuth8258851
Ref: 78f8258851
Ref: library/urllib request urllib request AbstractBasicAuthHandler8259236
Ref: e978259236
Ref: library/urllib request urllib request HTTPBasicAuthHandler8260577
Ref: 2c4e8260577
Ref: library/urllib request urllib request ProxyBasicAuthHandler8261042
Ref: 2c4f8261042
Ref: library/urllib request urllib request AbstractDigestAuthHandler8261383
Ref: f2c8261383
Ref: library/urllib request urllib request HTTPDigestAuthHandler8261794
Ref: 2c508261794
Ref: library/urllib request urllib request ProxyDigestAuthHandler8262648
Ref: 2c518262648
Ref: library/urllib request urllib request HTTPHandler8262990
Ref: 2c3f8262990
Ref: library/urllib request urllib request HTTPSHandler8263076
Ref: bad8263076
Ref: library/urllib request urllib request FileHandler8263398
Ref: 2c438263398
Ref: library/urllib request urllib request DataHandler8263462
Ref: 8fa8263462
Ref: library/urllib request urllib request FTPHandler8263548
Ref: 2c428263548
Ref: library/urllib request urllib request CacheFTPHandler8263608
Ref: 2c528263608
Ref: library/urllib request urllib request UnknownHandler8263738
Ref: 2c3b8263738
Ref: library/urllib request urllib request HTTPErrorProcessor8263829
Ref: 2c448263829
Ref: urllib request --- Extensible library for opening URLs-Footnote-18264711
Ref: urllib request --- Extensible library for opening URLs-Footnote-28264784
Ref: urllib request --- Extensible library for opening URLs-Footnote-38264835
Ref: urllib request --- Extensible library for opening URLs-Footnote-48264872
Ref: urllib request --- Extensible library for opening URLs-Footnote-58264921
Ref: urllib request --- Extensible library for opening URLs-Footnote-68264970
Node: Request Objects8265019
Ref: library/urllib request id18265156
Ref: 2c538265156
Ref: library/urllib request request-objects8265156
Ref: 2c548265156
Ref: library/urllib request urllib request Request full_url8265427
Ref: 8fd8265427
Ref: library/urllib request urllib request Request type8265710
Ref: 2c558265710
Ref: library/urllib request urllib request Request host8265758
Ref: 2c568265758
Ref: library/urllib request urllib request Request origin_req_host8265882
Ref: 2c578265882
Ref: library/urllib request urllib request Request selector8265974
Ref: 2c588265974
Ref: library/urllib request urllib request Request data8266135
Ref: 8fe8266135
Ref: library/urllib request urllib request Request unverifiable8266377
Ref: 2c598266377
Ref: library/urllib request urllib request Request method8266504
Ref: 8fc8266504
Ref: library/urllib request urllib request Request get_method8267191
Ref: ac68267191
Ref: library/urllib request urllib request Request add_header8267610
Ref: 2c488267610
Ref: library/urllib request urllib request Request add_unredirected_header8268209
Ref: 2c5a8268209
Ref: library/urllib request urllib request Request has_header8268341
Ref: 2c5b8268341
Ref: library/urllib request urllib request Request remove_header8268488
Ref: 9008268488
Ref: library/urllib request urllib request Request get_full_url8268665
Ref: 2c5c8268665
Ref: library/urllib request urllib request Request set_proxy8268819
Ref: 2c5d8268819
Ref: library/urllib request urllib request Request get_header8269078
Ref: 2c5e8269078
Ref: library/urllib request urllib request Request header_items8269250
Ref: 2c5f8269250
Ref: Request Objects-Footnote-18269606
Node: OpenerDirector Objects8269655
Ref: library/urllib request opener-director-objects8269820
Ref: 2c608269820
Ref: library/urllib request openerdirector-objects8269820
Ref: 2c618269820
Ref: library/urllib request urllib request OpenerDirector add_handler8269952
Ref: 2c628269952
Ref: library/urllib request urllib request OpenerDirector open8271516
Ref: 8ff8271516
Ref: library/urllib request urllib request OpenerDirector error8272206
Ref: 2c678272206
Node: BaseHandler Objects8273988
Ref: library/urllib request base-handler-objects8274165
Ref: 2c688274165
Ref: library/urllib request basehandler-objects8274165
Ref: 2c698274165
Ref: library/urllib request urllib request BaseHandler add_parent8274405
Ref: 2c6a8274405
Ref: library/urllib request urllib request BaseHandler close8274490
Ref: 2c6b8274490
Ref: library/urllib request urllib request BaseHandler parent8274874
Ref: 2c6c8274874
Ref: library/urllib request urllib request BaseHandler default_open8275025
Ref: 2c6d8275025
Ref: library/urllib request protocol-open8275704
Ref: 2c638275704
Ref: library/urllib request urllib request BaseHandler unknown_open8276076
Ref: 2c6e8276076
Ref: library/urllib request urllib request BaseHandler http_error_default8276494
Ref: 2c6f8276494
Ref: library/urllib request http-error-nnn8277307
Ref: 2c648277307
Ref: library/urllib request protocol-request8277811
Ref: 2c658277811
Ref: library/urllib request protocol-response8278231
Ref: 2c668278231
Node: HTTPRedirectHandler Objects8278828
Ref: library/urllib request http-redirect-handler8279010
Ref: 2c708279010
Ref: library/urllib request httpredirecthandler-objects8279010
Ref: 2c718279010
Ref: library/urllib request urllib request HTTPRedirectHandler redirect_request8279509
Ref: 2c728279509
Ref: library/urllib request urllib request HTTPRedirectHandler http_error_3018280601
Ref: 2c738280601
Ref: library/urllib request urllib request HTTPRedirectHandler http_error_3028280878
Ref: 2c748280878
Ref: library/urllib request urllib request HTTPRedirectHandler http_error_3038281063
Ref: 2c758281063
Ref: library/urllib request urllib request HTTPRedirectHandler http_error_3078281252
Ref: 2c768281252
Ref: HTTPRedirectHandler Objects-Footnote-18281486
Ref: HTTPRedirectHandler Objects-Footnote-28281535
Node: HTTPCookieProcessor Objects8281584
Ref: library/urllib request http-cookie-processor8281767
Ref: 2c778281767
Ref: library/urllib request httpcookieprocessor-objects8281767
Ref: 2c788281767
Ref: library/urllib request urllib request HTTPCookieProcessor cookiejar8281906
Ref: 2c798281906
Node: ProxyHandler Objects8282031
Ref: library/urllib request proxy-handler8282210
Ref: 2c7b8282210
Ref: library/urllib request proxyhandler-objects8282210
Ref: 2c7c8282210
Node: HTTPPasswordMgr Objects8282688
Ref: library/urllib request http-password-mgr8282876
Ref: 2c4c8282876
Ref: library/urllib request httppasswordmgr-objects8282876
Ref: 2c7d8282876
Ref: library/urllib request urllib request HTTPPasswordMgr add_password8283062
Ref: 2c7e8283062
Ref: library/urllib request urllib request HTTPPasswordMgr find_user_password8283415
Ref: 2c7f8283415
Node: HTTPPasswordMgrWithPriorAuth Objects8283795
Ref: library/urllib request http-password-mgr-with-prior-auth8283995
Ref: 2c4d8283995
Ref: library/urllib request httppasswordmgrwithpriorauth-objects8283995
Ref: 2c808283995
Ref: library/urllib request urllib request HTTPPasswordMgrWithPriorAuth add_password8284249
Ref: 2c818284249
Ref: library/urllib request urllib request HTTPPasswordMgrWithPriorAuth find_user_password8284669
Ref: 2c828284669
Ref: library/urllib request urllib request HTTPPasswordMgrWithPriorAuth update_authenticated8284834
Ref: 2c838284834
Ref: library/urllib request urllib request HTTPPasswordMgrWithPriorAuth is_authenticated8285036
Ref: 2c848285036
Node: AbstractBasicAuthHandler Objects8285218
Ref: library/urllib request abstract-basic-auth-handler8285423
Ref: 2c858285423
Ref: library/urllib request abstractbasicauthhandler-objects8285423
Ref: 2c868285423
Ref: library/urllib request urllib request AbstractBasicAuthHandler http_error_auth_reqed8285508
Ref: 2c878285508
Node: HTTPBasicAuthHandler Objects8286334
Ref: library/urllib request http-basic-auth-handler8286532
Ref: 2c888286532
Ref: library/urllib request httpbasicauthhandler-objects8286532
Ref: 2c898286532
Ref: library/urllib request urllib request HTTPBasicAuthHandler http_error_4018286611
Ref: 2c8a8286611
Node: ProxyBasicAuthHandler Objects8286774
Ref: library/urllib request proxy-basic-auth-handler8286973
Ref: 2c8b8286973
Ref: library/urllib request proxybasicauthhandler-objects8286973
Ref: 2c8c8286973
Ref: library/urllib request urllib request ProxyBasicAuthHandler http_error_4078287054
Ref: 2c8d8287054
Node: AbstractDigestAuthHandler Objects8287218
Ref: library/urllib request abstract-digest-auth-handler8287418
Ref: 2c8e8287418
Ref: library/urllib request abstractdigestauthhandler-objects8287418
Ref: 2c8f8287418
Ref: library/urllib request urllib request AbstractDigestAuthHandler http_error_auth_reqed8287507
Ref: 2c908287507
Node: HTTPDigestAuthHandler Objects8287890
Ref: library/urllib request http-digest-auth-handler8288091
Ref: 2c918288091
Ref: library/urllib request httpdigestauthhandler-objects8288091
Ref: 2c928288091
Ref: library/urllib request urllib request HTTPDigestAuthHandler http_error_4018288172
Ref: 2c938288172
Node: ProxyDigestAuthHandler Objects8288336
Ref: library/urllib request proxy-digest-auth-handler8288523
Ref: 2c948288523
Ref: library/urllib request proxydigestauthhandler-objects8288523
Ref: 2c958288523
Ref: library/urllib request urllib request ProxyDigestAuthHandler http_error_4078288606
Ref: 2c968288606
Node: HTTPHandler Objects8288771
Ref: library/urllib request http-handler-objects8288949
Ref: 2c978288949
Ref: library/urllib request httphandler-objects8288949
Ref: 2c988288949
Ref: library/urllib request urllib request HTTPHandler http_open8289010
Ref: 2c998289010
Node: HTTPSHandler Objects8289158
Ref: library/urllib request https-handler-objects8289325
Ref: 2c9a8289325
Ref: library/urllib request httpshandler-objects8289325
Ref: 2c9b8289325
Ref: library/urllib request urllib request HTTPSHandler https_open8289388
Ref: 2c9c8289388
Node: FileHandler Objects8289539
Ref: library/urllib request file-handler-objects8289706
Ref: 2c9d8289706
Ref: library/urllib request filehandler-objects8289706
Ref: 2c9e8289706
Ref: library/urllib request urllib request FileHandler file_open8289767
Ref: 2c9f8289767
Node: DataHandler Objects8290065
Ref: library/urllib request data-handler-objects8290230
Ref: 2ca08290230
Ref: library/urllib request datahandler-objects8290230
Ref: 2ca18290230
Ref: library/urllib request urllib request DataHandler data_open8290291
Ref: 2ca28290291
Ref: DataHandler Objects-Footnote-18290856
Node: FTPHandler Objects8290905
Ref: library/urllib request ftp-handler-objects8291074
Ref: 2ca38291074
Ref: library/urllib request ftphandler-objects8291074
Ref: 2ca48291074
Ref: library/urllib request urllib request FTPHandler ftp_open8291133
Ref: 2ca58291133
Node: CacheFTPHandler Objects8291287
Ref: library/urllib request cacheftp-handler-objects8291459
Ref: 2ca68291459
Ref: library/urllib request cacheftphandler-objects8291459
Ref: 2ca78291459
Ref: library/urllib request urllib request CacheFTPHandler setTimeout8291641
Ref: 2ca88291641
Ref: library/urllib request urllib request CacheFTPHandler setMaxConns8291740
Ref: 2ca98291740
Node: UnknownHandler Objects8291846
Ref: library/urllib request unknown-handler-objects8292026
Ref: 2caa8292026
Ref: library/urllib request unknownhandler-objects8292026
Ref: 2cab8292026
Ref: library/urllib request urllib request UnknownHandler unknown_open8292093
Ref: 2cac8292093
Node: HTTPErrorProcessor Objects8292190
Ref: library/urllib request http-error-processor-objects8292359
Ref: 2cad8292359
Ref: library/urllib request httperrorprocessor-objects8292359
Ref: 2cae8292359
Ref: library/urllib request urllib request HTTPErrorProcessor http_response8292434
Ref: 2caf8292434
Ref: library/urllib request urllib request HTTPErrorProcessor https_response8292910
Ref: 2cb08292910
Node: Examples<21>8293079
Ref: library/urllib request examples8293242
Ref: 2cb18293242
Ref: library/urllib request urllib-request-examples8293242
Ref: 2cb28293242
Ref: library/urllib request urllib-examples8298794
Ref: 2cb48298794
Node: Legacy interface8300287
Ref: library/urllib request legacy-interface8300451
Ref: 2cb58300451
Ref: library/urllib request urllib request urlretrieve8300682
Ref: 2cb68300682
Ref: library/urllib request urllib request urlcleanup8303342
Ref: 2cb78303342
Ref: library/urllib request urllib request URLopener8303500
Ref: 2c378303500
Ref: library/urllib request urllib request URLopener open8305001
Ref: 2cb98305001
Ref: library/urllib request urllib request URLopener open_unknown8305510
Ref: 2cba8305510
Ref: library/urllib request urllib request URLopener retrieve8305628
Ref: fcd8305628
Ref: library/urllib request urllib request URLopener version8307183
Ref: 2cb88307183
Ref: library/urllib request urllib request FancyURLopener8307501
Ref: 2c388307501
Ref: library/urllib request urllib request FancyURLopener prompt_user_passwd8309234
Ref: 2cbb8309234
Ref: Legacy interface-Footnote-18309780
Node: urllib request Restrictions8309829
Ref: library/urllib request urllib-request-restrictions8309972
Ref: 2cbc8309972
Node: urllib response --- Response classes used by urllib8312531
Ref: library/urllib request module-urllib response8312764
Ref: 1228312764
Ref: library/urllib request urllib-response-response-classes-used-by-urllib8312764
Ref: 2cbd8312764
Node: urllib parse --- Parse URLs into components8313312
Ref: library/urllib parse doc8313550
Ref: 2cbe8313550
Ref: library/urllib parse module-urllib parse8313550
Ref: 1208313550
Ref: library/urllib parse urllib-parse-parse-urls-into-components8313550
Ref: 2cbf8313550
Ref: urllib parse --- Parse URLs into components-Footnote-18314817
Node: URL Parsing8314888
Ref: library/urllib parse url-parsing8315015
Ref: 2cc08315015
Ref: library/urllib parse urllib parse urlparse8315188
Ref: 5ff8315188
Ref: library/urllib parse urllib parse parse_qs8322444
Ref: 2ec8322444
Ref: library/urllib parse urllib parse parse_qsl8324598
Ref: 2ed8324598
Ref: library/urllib parse urllib parse urlunparse8326602
Ref: 2cc28326602
Ref: library/urllib parse urllib parse urlsplit8327002
Ref: 5fe8327002
Ref: library/urllib parse urllib parse urlunsplit8331254
Ref: 2cc38331254
Ref: library/urllib parse urllib parse urljoin8331696
Ref: 7928331696
Ref: library/urllib parse urllib parse urldefrag8332989
Ref: be38332989
Ref: library/urllib parse urllib parse unwrap8334323
Ref: 2cc48334323
Ref: URL Parsing-Footnote-18334669
Ref: URL Parsing-Footnote-28334718
Ref: URL Parsing-Footnote-38334767
Ref: URL Parsing-Footnote-48334816
Ref: URL Parsing-Footnote-58334878
Node: Parsing ASCII Encoded Bytes8334927
Ref: library/urllib parse id18335087
Ref: 2cc58335087
Ref: library/urllib parse parsing-ascii-encoded-bytes8335087
Ref: be58335087
Node: Structured Parse Results8337204
Ref: library/urllib parse structured-parse-results8337364
Ref: 2cc68337364
Ref: library/urllib parse urlparse-result-object8337364
Ref: 2cc18337364
Ref: library/urllib parse urllib parse urllib parse SplitResult geturl8337780
Ref: 2cc78337780
Ref: library/urllib parse urllib parse DefragResult8338909
Ref: 2cc88338909
Ref: library/urllib parse urllib parse ParseResult8339166
Ref: 2cca8339166
Ref: library/urllib parse urllib parse SplitResult8339438
Ref: 2ccc8339438
Ref: library/urllib parse urllib parse DefragResultBytes8339844
Ref: 2cc98339844
Ref: library/urllib parse urllib parse ParseResultBytes8340103
Ref: 2ccb8340103
Ref: library/urllib parse urllib parse SplitResultBytes8340401
Ref: 2ccd8340401
Node: URL Quoting8340691
Ref: library/urllib parse url-quoting8340815
Ref: 2cce8340815
Ref: library/urllib parse urllib parse quote8341218
Ref: 4128341218
Ref: library/urllib parse urllib parse quote_plus8342558
Ref: be48342558
Ref: library/urllib parse urllib parse quote_from_bytes8343047
Ref: 2ccf8343047
Ref: library/urllib parse urllib parse unquote8343338
Ref: edc8343338
Ref: library/urllib parse urllib parse unquote_plus8343965
Ref: 2cd08343965
Ref: library/urllib parse urllib parse unquote_to_bytes8344300
Ref: 2cd18344300
Ref: library/urllib parse urllib parse urlencode8344716
Ref: 7908344716
Ref: URL Quoting-Footnote-18348513
Ref: URL Quoting-Footnote-28348562
Ref: URL Quoting-Footnote-38348611
Ref: URL Quoting-Footnote-48348648
Ref: URL Quoting-Footnote-58348697
Ref: URL Quoting-Footnote-68348746
Ref: URL Quoting-Footnote-78348795
Ref: URL Quoting-Footnote-88348844
Ref: URL Quoting-Footnote-98348893
Node: urllib error --- Exception classes raised by urllib request8348942
Ref: library/urllib error doc8349173
Ref: 2cd28349173
Ref: library/urllib error module-urllib error8349173
Ref: 11f8349173
Ref: library/urllib error urllib-error-exception-classes-raised-by-urllib-request8349173
Ref: 2cd38349173
Ref: library/urllib error whatwg8349173
Ref: 2cd48349173
Ref: library/urllib error urllib error URLError8349672
Ref: 2c398349672
Ref: library/urllib error urllib error URLError reason8349847
Ref: 2cd58349847
Ref: library/urllib error urllib error HTTPError8350106
Ref: 9018350106
Ref: library/urllib error urllib error HTTPError code8350460
Ref: 2cd68350460
Ref: library/urllib error urllib error HTTPError reason8350717
Ref: 2cd88350717
Ref: library/urllib error urllib error HTTPError headers8350816
Ref: 9028350816
Ref: library/urllib error urllib error ContentTooShortError8350977
Ref: 2cd98350977
Ref: urllib error --- Exception classes raised by urllib request-Footnote-18351374
Ref: urllib error --- Exception classes raised by urllib request-Footnote-28351445
Node: urllib robotparser --- Parser for robots txt8351494
Ref: library/urllib robotparser doc8351703
Ref: 2cda8351703
Ref: library/urllib robotparser module-urllib robotparser8351703
Ref: 1238351703
Ref: library/urllib robotparser urllib-robotparser-parser-for-robots-txt8351703
Ref: 2cdb8351703
Ref: library/urllib robotparser urllib robotparser RobotFileParser8352246
Ref: 5b28352246
Ref: library/urllib robotparser urllib robotparser RobotFileParser set_url8352420
Ref: 2cdc8352420
Ref: library/urllib robotparser urllib robotparser RobotFileParser read8352520
Ref: 2cdd8352520
Ref: library/urllib robotparser urllib robotparser RobotFileParser parse8352622
Ref: 10a68352622
Ref: library/urllib robotparser urllib robotparser RobotFileParser can_fetch8352698
Ref: 2cde8352698
Ref: library/urllib robotparser urllib robotparser RobotFileParser mtime8352918
Ref: 2cdf8352918
Ref: library/urllib robotparser urllib robotparser RobotFileParser modified8353152
Ref: 2ce08353152
Ref: library/urllib robotparser urllib robotparser RobotFileParser crawl_delay8353287
Ref: 2ce18353287
Ref: library/urllib robotparser urllib robotparser RobotFileParser request_rate8353693
Ref: 2ce28353693
Ref: library/urllib robotparser urllib robotparser RobotFileParser site_maps8354148
Ref: 103b8354148
Ref: urllib robotparser --- Parser for robots txt-Footnote-18355072
Node: http --- HTTP modules8355150
Ref: library/http doc8355336
Ref: 2ce38355336
Ref: library/http http-http-modules8355336
Ref: 2ce48355336
Ref: library/http module-http8355336
Ref: 938355336
Ref: library/http http HTTPStatus8356159
Ref: 6e78356159
Ref: http --- HTTP modules-Footnote-18356898
Node: HTTP status codes8356970
Ref: library/http http-status-codes8357045
Ref: 2ce58357045
Ref: library/http id18357045
Ref: 2ce68357045
Ref: HTTP status codes-Footnote-18370092
Ref: HTTP status codes-Footnote-28370176
Ref: HTTP status codes-Footnote-38370225
Ref: HTTP status codes-Footnote-48370274
Ref: HTTP status codes-Footnote-58370323
Ref: HTTP status codes-Footnote-68370372
Ref: HTTP status codes-Footnote-78370421
Ref: HTTP status codes-Footnote-88370470
Ref: HTTP status codes-Footnote-98370519
Ref: HTTP status codes-Footnote-108370568
Ref: HTTP status codes-Footnote-118370618
Ref: HTTP status codes-Footnote-128370668
Ref: HTTP status codes-Footnote-138370718
Ref: HTTP status codes-Footnote-148370768
Ref: HTTP status codes-Footnote-158370818
Ref: HTTP status codes-Footnote-168370868
Ref: HTTP status codes-Footnote-178370918
Ref: HTTP status codes-Footnote-188370968
Ref: HTTP status codes-Footnote-198371018
Ref: HTTP status codes-Footnote-208371068
Ref: HTTP status codes-Footnote-218371118
Ref: HTTP status codes-Footnote-228371168
Ref: HTTP status codes-Footnote-238371218
Ref: HTTP status codes-Footnote-248371268
Ref: HTTP status codes-Footnote-258371318
Ref: HTTP status codes-Footnote-268371368
Ref: HTTP status codes-Footnote-278371418
Ref: HTTP status codes-Footnote-288371468
Ref: HTTP status codes-Footnote-298371518
Ref: HTTP status codes-Footnote-308371568
Ref: HTTP status codes-Footnote-318371618
Ref: HTTP status codes-Footnote-328371668
Ref: HTTP status codes-Footnote-338371718
Ref: HTTP status codes-Footnote-348371768
Ref: HTTP status codes-Footnote-358371818
Ref: HTTP status codes-Footnote-368371868
Ref: HTTP status codes-Footnote-378371918
Ref: HTTP status codes-Footnote-388371968
Ref: HTTP status codes-Footnote-398372018
Ref: HTTP status codes-Footnote-408372068
Ref: HTTP status codes-Footnote-418372118
Ref: HTTP status codes-Footnote-428372168
Ref: HTTP status codes-Footnote-438372218
Ref: HTTP status codes-Footnote-448372268
Ref: HTTP status codes-Footnote-458372318
Ref: HTTP status codes-Footnote-468372368
Ref: HTTP status codes-Footnote-478372418
Ref: HTTP status codes-Footnote-488372468
Ref: HTTP status codes-Footnote-498372518
Ref: HTTP status codes-Footnote-508372568
Ref: HTTP status codes-Footnote-518372618
Ref: HTTP status codes-Footnote-528372668
Ref: HTTP status codes-Footnote-538372718
Ref: HTTP status codes-Footnote-548372768
Ref: HTTP status codes-Footnote-558372818
Ref: HTTP status codes-Footnote-568372868
Ref: HTTP status codes-Footnote-578372918
Ref: HTTP status codes-Footnote-588372968
Ref: HTTP status codes-Footnote-598373018
Ref: HTTP status codes-Footnote-608373068
Node: http client --- HTTP protocol client8373118
Ref: library/http client doc8373290
Ref: 2ce78373290
Ref: library/http client http-client-http-protocol-client8373290
Ref: 2ce88373290
Ref: library/http client module-http client8373290
Ref: 948373290
Ref: library/http client http client HTTPConnection8373983
Ref: 3978373983
Ref: library/http client http client HTTPSConnection8375531
Ref: 3988375531
Ref: library/http client http client HTTPResponse8377303
Ref: a168377303
Ref: library/http client http client parse_headers8377673
Ref: 10458377673
Ref: library/http client http client HTTPException8378608
Ref: 2ceb8378608
Ref: library/http client http client NotConnected8378756
Ref: 2cec8378756
Ref: library/http client http client InvalidURL8378841
Ref: 2ced8378841
Ref: library/http client http client UnknownProtocol8378991
Ref: 2cee8378991
Ref: library/http client http client UnknownTransferEncoding8379079
Ref: 2cef8379079
Ref: library/http client http client UnimplementedFileMode8379175
Ref: 2cf08379175
Ref: library/http client http client IncompleteRead8379269
Ref: 2cf18379269
Ref: library/http client http client ImproperConnectionState8379356
Ref: 2cf28379356
Ref: library/http client http client CannotSendRequest8379452
Ref: 2cf38379452
Ref: library/http client http client CannotSendHeader8379552
Ref: 2cf48379552
Ref: library/http client http client ResponseNotReady8379651
Ref: 2cf58379651
Ref: library/http client http client BadStatusLine8379750
Ref: 2cf68379750
Ref: library/http client http client LineTooLong8379922
Ref: 2cf78379922
Ref: library/http client http client RemoteDisconnected8380097
Ref: 6ea8380097
Ref: library/http client http client HTTP_PORT8380571
Ref: 2cf88380571
Ref: library/http client http client HTTPS_PORT8380668
Ref: 2cf98380668
Ref: library/http client http client responses8380768
Ref: 2cfa8380768
Ref: http client --- HTTP protocol client-Footnote-18381229
Ref: http client --- HTTP protocol client-Footnote-28381299
Ref: http client --- HTTP protocol client-Footnote-38381350
Node: HTTPConnection Objects8381399
Ref: library/http client httpconnection-objects8381523
Ref: 2cfb8381523
Ref: library/http client id18381523
Ref: 2cfc8381523
Ref: library/http client http client HTTPConnection request8381656
Ref: 5548381656
Ref: library/http client http client HTTPConnection getresponse8384430
Ref: 6e98384430
Ref: library/http client http client HTTPConnection set_debuglevel8384921
Ref: 2cfd8384921
Ref: library/http client http client HTTPConnection set_tunnel8385326
Ref: bb28385326
Ref: library/http client http client HTTPConnection connect8386335
Ref: 2cfe8386335
Ref: library/http client http client HTTPConnection close8386571
Ref: 2cff8386571
Ref: library/http client http client HTTPConnection blocksize8386656
Ref: 2d008386656
Ref: library/http client http client HTTPConnection putrequest8386935
Ref: 2d018386935
Ref: library/http client http client HTTPConnection putheader8387490
Ref: 2d028387490
Ref: library/http client http client HTTPConnection endheaders8387831
Ref: 5558387831
Ref: library/http client http client HTTPConnection send8389206
Ref: 2d038389206
Ref: HTTPConnection Objects-Footnote-18389470
Ref: HTTPConnection Objects-Footnote-28389518
Node: HTTPResponse Objects8389567
Ref: library/http client httpresponse-objects8389712
Ref: 2d048389712
Ref: library/http client id28389712
Ref: 2d058389712
Ref: library/http client http client HTTPResponse read8390117
Ref: 2d068390117
Ref: library/http client http client HTTPResponse readinto8390236
Ref: a178390236
Ref: library/http client http client HTTPResponse getheader8390427
Ref: 2d078390427
Ref: library/http client http client HTTPResponse getheaders8390824
Ref: 2d088390824
Ref: library/http client http client HTTPResponse fileno8390917
Ref: 2d098390917
Ref: library/http client http client HTTPResponse msg8391015
Ref: 2ce98391015
Ref: library/http client http client HTTPResponse version8391217
Ref: 2d0a8391217
Ref: library/http client http client HTTPResponse status8391335
Ref: 2d0b8391335
Ref: library/http client http client HTTPResponse reason8391406
Ref: 2c368391406
Ref: library/http client http client HTTPResponse debuglevel8391479
Ref: 2d0c8391479
Ref: library/http client http client HTTPResponse closed8391671
Ref: 2d0d8391671
Node: Examples<22>8391749
Ref: library/http client examples8391891
Ref: 2d0e8391891
Node: HTTPMessage Objects8394807
Ref: library/http client httpmessage-objects8394920
Ref: 2d0f8394920
Ref: library/http client id38394920
Ref: 2d108394920
Node: ftplib --- FTP protocol client8395135
Ref: library/ftplib doc8395317
Ref: 2d118395317
Ref: library/ftplib ftplib-ftp-protocol-client8395317
Ref: 2d128395317
Ref: library/ftplib module-ftplib8395317
Ref: 848395317
Ref: library/ftplib ftplib FTP8396852
Ref: 2f18396852
Ref: library/ftplib ftplib FTP_TLS8398326
Ref: a088398326
Ref: library/ftplib ftplib error_reply8400582
Ref: 2d148400582
Ref: library/ftplib ftplib error_temp8400696
Ref: 2d158400696
Ref: library/ftplib ftplib error_perm8400856
Ref: 2d168400856
Ref: library/ftplib ftplib error_proto8401016
Ref: 2d178401016
Ref: library/ftplib ftplib all_errors8401244
Ref: 2d188401244
Ref: ftplib --- FTP protocol client-Footnote-18401905
Ref: ftplib --- FTP protocol client-Footnote-28401970
Ref: ftplib --- FTP protocol client-Footnote-38402018
Node: FTP Objects8402067
Ref: library/ftplib ftp-objects8402169
Ref: 2d198402169
Ref: library/ftplib id18402169
Ref: 2d1a8402169
Ref: library/ftplib ftplib FTP set_debuglevel8402506
Ref: 2d1b8402506
Ref: library/ftplib ftplib FTP connect8402976
Ref: 2d1c8402976
Ref: library/ftplib ftplib FTP getwelcome8403984
Ref: 2d1d8403984
Ref: library/ftplib ftplib FTP login8404220
Ref: 2d1e8404220
Ref: library/ftplib ftplib FTP abort8404935
Ref: 2d1f8404935
Ref: library/ftplib ftplib FTP sendcmd8405079
Ref: 2d208405079
Ref: library/ftplib ftplib FTP voidcmd8405309
Ref: 2d218405309
Ref: library/ftplib ftplib FTP retrbinary8405688
Ref: 2d228405688
Ref: library/ftplib ftplib FTP retrlines8406374
Ref: 2d248406374
Ref: library/ftplib ftplib FTP set_pasv8407002
Ref: 2d258407002
Ref: library/ftplib ftplib FTP storbinary8407155
Ref: ca48407155
Ref: library/ftplib ftplib FTP storlines8407852
Ref: 2d268407852
Ref: library/ftplib ftplib FTP transfercmd8408323
Ref: 2d238408323
Ref: library/ftplib ftplib FTP ntransfercmd8409579
Ref: 2d278409579
Ref: library/ftplib ftplib FTP mlsd8409935
Ref: a0a8409935
Ref: library/ftplib ftplib FTP nlst8410631
Ref: a0b8410631
Ref: library/ftplib ftplib FTP dir8411050
Ref: a0c8411050
Ref: library/ftplib ftplib FTP rename8411693
Ref: 2d288411693
Ref: library/ftplib ftplib FTP delete8411798
Ref: 2d298411798
Ref: library/ftplib ftplib FTP cwd8412067
Ref: 2d2a8412067
Ref: library/ftplib ftplib FTP mkd8412152
Ref: 2d2b8412152
Ref: library/ftplib ftplib FTP pwd8412234
Ref: 2d2c8412234
Ref: library/ftplib ftplib FTP rmd8412330
Ref: 2d2d8412330
Ref: library/ftplib ftplib FTP size8412425
Ref: 2d2e8412425
Ref: library/ftplib ftplib FTP quit8412757
Ref: 2d2f8412757
Ref: library/ftplib ftplib FTP close8413169
Ref: 2d308413169
Ref: FTP Objects-Footnote-18413635
Ref: FTP Objects-Footnote-28413683
Node: FTP_TLS Objects8413732
Ref: library/ftplib ftp-tls-objects8413834
Ref: 2d318413834
Ref: library/ftplib ftplib FTP_TLS ssl_version8413979
Ref: 2d328413979
Ref: library/ftplib ftplib FTP_TLS auth8414094
Ref: 2d338414094
Ref: library/ftplib ftplib FTP_TLS ccc8414449
Ref: a098414449
Ref: library/ftplib ftplib FTP_TLS prot_p8414693
Ref: 2d138414693
Ref: library/ftplib ftplib FTP_TLS prot_c8414767
Ref: 2d348414767
Node: poplib --- POP3 protocol client8414845
Ref: library/poplib doc8415024
Ref: 2d358415024
Ref: library/poplib module-poplib8415024
Ref: d18415024
Ref: library/poplib poplib-pop3-protocol-client8415024
Ref: 2d368415024
Ref: library/poplib poplib POP38416139
Ref: 2d378416139
Ref: library/poplib poplib POP3_SSL8416880
Ref: bc68416880
Ref: library/poplib poplib error_proto8418621
Ref: b1c8418621
Ref: poplib --- POP3 protocol client-Footnote-18419270
Ref: poplib --- POP3 protocol client-Footnote-28419335
Ref: poplib --- POP3 protocol client-Footnote-38419384
Ref: poplib --- POP3 protocol client-Footnote-48419433
Ref: poplib --- POP3 protocol client-Footnote-58419482
Node: POP3 Objects8419544
Ref: library/poplib id18419645
Ref: 2d388419645
Ref: library/poplib pop3-objects8419645
Ref: 2d398419645
Ref: library/poplib poplib POP3 set_debuglevel8419879
Ref: 2d3a8419879
Ref: library/poplib poplib POP3 getwelcome8420350
Ref: 2d3b8420350
Ref: library/poplib poplib POP3 capa8420447
Ref: 8978420447
Ref: library/poplib poplib POP3 user8420640
Ref: 2d3c8420640
Ref: library/poplib poplib POP3 pass_8420764
Ref: 2d3d8420764
Ref: library/poplib poplib POP3 apop8420953
Ref: 2d3e8420953
Ref: library/poplib poplib POP3 rpop8421077
Ref: 2d3f8421077
Ref: library/poplib poplib POP3 stat8421202
Ref: 2d408421202
Ref: library/poplib poplib POP3 list8421340
Ref: 2d418421340
Ref: library/poplib poplib POP3 retr8421538
Ref: 2d428421538
Ref: library/poplib poplib POP3 dele8421707
Ref: 2d438421707
Ref: library/poplib poplib POP3 rset8421991
Ref: 2d448421991
Ref: library/poplib poplib POP3 noop8422072
Ref: 2d458422072
Ref: library/poplib poplib POP3 quit8422154
Ref: b1b8422154
Ref: library/poplib poplib POP3 top8422250
Ref: 2d468422250
Ref: library/poplib poplib POP3 uidl8422793
Ref: 2d478422793
Ref: library/poplib poplib POP3 utf88423083
Ref: 7378423083
Ref: library/poplib poplib POP3 stls8423294
Ref: 8988423294
Ref: POP3 Objects-Footnote-18424097
Ref: POP3 Objects-Footnote-28424146
Ref: POP3 Objects-Footnote-38424195
Node: POP3 Example8424244
Ref: library/poplib id28424345
Ref: 2d488424345
Ref: library/poplib pop3-example8424345
Ref: 2d498424345
Node: imaplib --- IMAP4 protocol client8424857
Ref: library/imaplib doc8425038
Ref: 2d4a8425038
Ref: library/imaplib imaplib-imap4-protocol-client8425038
Ref: 2d4b8425038
Ref: library/imaplib module-imaplib8425038
Ref: 988425038
Ref: library/imaplib imaplib IMAP48425703
Ref: 6108425703
Ref: library/imaplib imaplib IMAP4 error8426623
Ref: 2d4d8426623
Ref: library/imaplib imaplib IMAP4 abort8426763
Ref: 2d4e8426763
Ref: library/imaplib imaplib IMAP4 readonly8427022
Ref: 2d4f8427022
Ref: library/imaplib imaplib IMAP4_SSL8427376
Ref: a1c8427376
Ref: library/imaplib imaplib IMAP4_stream8429066
Ref: 2d4c8429066
Ref: library/imaplib imaplib Internaldate2tuple8429337
Ref: 2d508429337
Ref: library/imaplib imaplib Int2AP8429585
Ref: 2d518429585
Ref: library/imaplib imaplib ParseFlags8429731
Ref: 2d528429731
Ref: library/imaplib imaplib Time2Internaldate8429850
Ref: 2d538429850
Ref: imaplib --- IMAP4 protocol client-Footnote-18431189
Ref: imaplib --- IMAP4 protocol client-Footnote-28431255
Ref: imaplib --- IMAP4 protocol client-Footnote-38431304
Node: IMAP4 Objects8431353
Ref: library/imaplib id18431458
Ref: 2d548431458
Ref: library/imaplib imap4-objects8431458
Ref: 2d558431458
Ref: library/imaplib imaplib IMAP4 append8432962
Ref: 2d568432962
Ref: library/imaplib imaplib IMAP4 authenticate8433072
Ref: 2d578433072
Ref: library/imaplib imaplib IMAP4 check8433905
Ref: 2d588433905
Ref: library/imaplib imaplib IMAP4 close8433975
Ref: 2d598433975
Ref: library/imaplib imaplib IMAP4 copy8434166
Ref: 2d5a8434166
Ref: library/imaplib imaplib IMAP4 create8434284
Ref: 2d5b8434284
Ref: library/imaplib imaplib IMAP4 delete8434368
Ref: 2d5c8434368
Ref: library/imaplib imaplib IMAP4 deleteacl8434452
Ref: 2d5d8434452
Ref: library/imaplib imaplib IMAP4 enable8434568
Ref: 6ef8434568
Ref: library/imaplib imaplib IMAP4 expunge8434889
Ref: 2d5e8434889
Ref: library/imaplib imaplib IMAP4 fetch8435143
Ref: 2d5f8435143
Ref: library/imaplib imaplib IMAP4 getacl8435429
Ref: 2d608435429
Ref: library/imaplib imaplib IMAP4 getannotation8435589
Ref: 2d618435589
Ref: library/imaplib imaplib IMAP4 getquota8435796
Ref: 2d628435796
Ref: library/imaplib imaplib IMAP4 getquotaroot8435976
Ref: 2d638435976
Ref: library/imaplib imaplib IMAP4 list8436170
Ref: 2d648436170
Ref: library/imaplib imaplib IMAP4 login8436445
Ref: 2d658436445
Ref: library/imaplib imaplib IMAP4 login_cram_md58436584
Ref: 2d668436584
Ref: library/imaplib imaplib IMAP4 logout8436850
Ref: 2d678436850
Ref: library/imaplib imaplib IMAP4 lsub8437044
Ref: 2d688437044
Ref: library/imaplib imaplib IMAP4 myrights8437340
Ref: 2d698437340
Ref: library/imaplib imaplib IMAP4 namespace8437465
Ref: 2d6a8437465
Ref: library/imaplib imaplib IMAP4 noop8437560
Ref: 2d6b8437560
Ref: library/imaplib imaplib IMAP4 open8437626
Ref: 2d6c8437626
Ref: library/imaplib imaplib IMAP4 partial8438151
Ref: 2d718438151
Ref: library/imaplib imaplib IMAP4 proxyauth8438334
Ref: 2d728438334
Ref: library/imaplib imaplib IMAP4 read8438492
Ref: 2d6d8438492
Ref: library/imaplib imaplib IMAP4 readline8438614
Ref: 2d6e8438614
Ref: library/imaplib imaplib IMAP4 recent8438732
Ref: 2d738438732
Ref: library/imaplib imaplib IMAP4 rename8438893
Ref: 2d748438893
Ref: library/imaplib imaplib IMAP4 response8439007
Ref: 2d758439007
Ref: library/imaplib imaplib IMAP4 search8439171
Ref: 2d768439171
Ref: library/imaplib imaplib IMAP4 select8439852
Ref: 2d778439852
Ref: library/imaplib imaplib IMAP4 send8440153
Ref: 2d6f8440153
Ref: library/imaplib imaplib IMAP4 setacl8440372
Ref: 2d788440372
Ref: library/imaplib imaplib IMAP4 setannotation8440541
Ref: 2d798440541
Ref: library/imaplib imaplib IMAP4 setquota8440736
Ref: 2d7a8440736
Ref: library/imaplib imaplib IMAP4 shutdown8440916
Ref: 2d708440916
Ref: library/imaplib imaplib IMAP4 socket8441109
Ref: 2d7b8441109
Ref: library/imaplib imaplib IMAP4 sort8441201
Ref: 2d7c8441201
Ref: library/imaplib imaplib IMAP4 starttls8442161
Ref: baf8442161
Ref: library/imaplib imaplib IMAP4 status8442683
Ref: 2d7d8442683
Ref: library/imaplib imaplib IMAP4 store8442785
Ref: 2d7e8442785
Ref: library/imaplib imaplib IMAP4 subscribe8443980
Ref: 2d7f8443980
Ref: library/imaplib imaplib IMAP4 thread8444057
Ref: 2d808444057
Ref: library/imaplib imaplib IMAP4 uid8445190
Ref: 2d818445190
Ref: library/imaplib imaplib IMAP4 unsubscribe8445514
Ref: 2d828445514
Ref: library/imaplib imaplib IMAP4 xatom8445597
Ref: 2d838445597
Ref: library/imaplib imaplib IMAP4 PROTOCOL_VERSION8445807
Ref: 2d848445807
Ref: library/imaplib imaplib IMAP4 debug8445939
Ref: 2d858445939
Ref: library/imaplib imaplib IMAP4 utf8_enabled8446139
Ref: 6f08446139
Ref: IMAP4 Objects-Footnote-18446412
Ref: IMAP4 Objects-Footnote-28446461
Ref: IMAP4 Objects-Footnote-38446510
Ref: IMAP4 Objects-Footnote-48446559
Ref: IMAP4 Objects-Footnote-58446608
Ref: IMAP4 Objects-Footnote-68446657
Node: IMAP4 Example8446706
Ref: library/imaplib id28446811
Ref: 2d868446811
Ref: library/imaplib imap4-example8446811
Ref: 2d878446811
Node: nntplib --- NNTP protocol client8447299
Ref: library/nntplib doc8447481
Ref: 2d888447481
Ref: library/nntplib module-nntplib8447481
Ref: c18447481
Ref: library/nntplib nntplib-nntp-protocol-client8447481
Ref: 2d898447481
Ref: library/nntplib nntplib NNTP8449333
Ref: a318449333
Ref: library/nntplib nntplib NNTP_SSL8451297
Ref: baa8451297
Ref: library/nntplib nntplib NNTPError8452648
Ref: 2d8b8452648
Ref: library/nntplib nntplib NNTPError response8452891
Ref: 2d8c8452891
Ref: library/nntplib nntplib NNTPReplyError8453009
Ref: 2d8d8453009
Ref: library/nntplib nntplib NNTPTemporaryError8453127
Ref: 2d8e8453127
Ref: library/nntplib nntplib NNTPPermanentError8453252
Ref: 2d8a8453252
Ref: library/nntplib nntplib NNTPProtocolError8453377
Ref: 2d8f8453377
Ref: library/nntplib nntplib NNTPDataError8453538
Ref: 2d908453538
Ref: nntplib --- NNTP protocol client-Footnote-18453749
Ref: nntplib --- NNTP protocol client-Footnote-28453815
Ref: nntplib --- NNTP protocol client-Footnote-38453864
Ref: nntplib --- NNTP protocol client-Footnote-48453912
Ref: nntplib --- NNTP protocol client-Footnote-58453961
Node: NNTP Objects8454010
Ref: library/nntplib id18454120
Ref: 2d918454120
Ref: library/nntplib nntp-objects8454120
Ref: 2d928454120
Node: Attributes8454328
Ref: library/nntplib attributes8454406
Ref: 2d938454406
Ref: library/nntplib nntplib NNTP nntp_version8454449
Ref: 2d948454449
Ref: library/nntplib nntplib NNTP nntp_implementation8454710
Ref: 2d958454710
Ref: Attributes-Footnote-18454942
Node: Methods<3>8454991
Ref: library/nntplib methods8455069
Ref: 2d968455069
Ref: library/nntplib nntplib NNTP quit8455951
Ref: 2d978455951
Ref: library/nntplib nntplib NNTP getwelcome8456140
Ref: 2d988456140
Ref: library/nntplib nntplib NNTP getcapabilities8456377
Ref: 2d998456377
Ref: library/nntplib nntplib NNTP login8456842
Ref: 2d9a8456842
Ref: library/nntplib nntplib NNTP starttls8457464
Ref: bab8457464
Ref: library/nntplib nntplib NNTP newgroups8458259
Ref: 2d9b8458259
Ref: library/nntplib nntplib NNTP newnews8458932
Ref: 2d9c8458932
Ref: library/nntplib nntplib NNTP list8459309
Ref: 2d9d8459309
Ref: library/nntplib nntplib NNTP descriptions8460642
Ref: 2d9e8460642
Ref: library/nntplib nntplib NNTP description8461246
Ref: 2d9f8461246
Ref: library/nntplib nntplib NNTP group8461620
Ref: 2da08461620
Ref: library/nntplib nntplib NNTP over8462060
Ref: 2da18462060
Ref: library/nntplib nntplib NNTP help8464226
Ref: 2da38464226
Ref: library/nntplib nntplib NNTP stat8464386
Ref: 2da48464386
Ref: library/nntplib nntplib NNTP next8465061
Ref: 2da58465061
Ref: library/nntplib nntplib NNTP last8465161
Ref: 2da68465161
Ref: library/nntplib nntplib NNTP article8465261
Ref: 2da78465261
Ref: library/nntplib nntplib NNTP head8466375
Ref: 2da88466375
Ref: library/nntplib nntplib NNTP body8466615
Ref: 2da98466615
Ref: library/nntplib nntplib NNTP post8466855
Ref: 2daa8466855
Ref: library/nntplib nntplib NNTP ihave8467487
Ref: 2dab8467487
Ref: library/nntplib nntplib NNTP date8467769
Ref: 2dac8467769
Ref: library/nntplib nntplib NNTP slave8467943
Ref: 2dad8467943
Ref: library/nntplib nntplib NNTP set_debuglevel8468045
Ref: 2dae8468045
Ref: library/nntplib nntplib NNTP xhdr8468687
Ref: 2daf8468687
Ref: library/nntplib nntplib NNTP xover8469631
Ref: 2db08469631
Ref: library/nntplib nntplib NNTP xpath8470013
Ref: 2db18470013
Ref: Methods<3>-Footnote-18470355
Ref: Methods<3>-Footnote-28470404
Ref: Methods<3>-Footnote-38470453
Ref: Methods<3>-Footnote-48470502
Node: Utility functions<2>8470551
Ref: library/nntplib utility-functions8470661
Ref: 2db28470661
Ref: library/nntplib nntplib decode_header8470775
Ref: 2da28470775
Node: smtplib --- SMTP protocol client8471364
Ref: library/smtplib doc8471534
Ref: 2db38471534
Ref: library/smtplib module-smtplib8471534
Ref: ee8471534
Ref: library/smtplib smtplib-smtp-protocol-client8471534
Ref: 2db48471534
Ref: library/smtplib smtplib SMTP8472023
Ref: a868472023
Ref: library/smtplib smtplib SMTP_SSL8474399
Ref: a878474399
Ref: library/smtplib smtplib LMTP8476050
Ref: a888476050
Ref: library/smtplib smtplib SMTPException8476883
Ref: 8bc8476883
Ref: library/smtplib smtplib SMTPServerDisconnected8477122
Ref: 2db78477122
Ref: library/smtplib smtplib SMTPResponseException8477347
Ref: 2db88477347
Ref: library/smtplib smtplib SMTPSenderRefused8477709
Ref: 2db98477709
Ref: library/smtplib smtplib SMTPRecipientsRefused8477947
Ref: 2dba8477947
Ref: library/smtplib smtplib SMTPDataError8478217
Ref: 2dbb8478217
Ref: library/smtplib smtplib SMTPConnectError8478310
Ref: 2db58478310
Ref: library/smtplib smtplib SMTPHeloError8478428
Ref: 2dbc8478428
Ref: library/smtplib smtplib SMTPNotSupportedError8478512
Ref: f728478512
Ref: library/smtplib smtplib SMTPAuthenticationError8478649
Ref: 2dbd8478649
Ref: smtplib --- SMTP protocol client-Footnote-18479368
Ref: smtplib --- SMTP protocol client-Footnote-28479434
Ref: smtplib --- SMTP protocol client-Footnote-38479482
Ref: smtplib --- SMTP protocol client-Footnote-48479531
Ref: smtplib --- SMTP protocol client-Footnote-58479580
Ref: smtplib --- SMTP protocol client-Footnote-68479628
Node: SMTP Objects8479677
Ref: library/smtplib id18479779
Ref: 2dbe8479779
Ref: library/smtplib smtp-objects8479779
Ref: 2dbf8479779
Ref: library/smtplib smtplib SMTP set_debuglevel8479883
Ref: 7488479883
Ref: library/smtplib smtplib SMTP docmd8480231
Ref: 2dc08480231
Ref: library/smtplib smtplib SMTP connect8480887
Ref: ee08480887
Ref: library/smtplib smtplib SMTP helo8481578
Ref: 2dc18481578
Ref: library/smtplib smtplib SMTP ehlo8482044
Ref: 2dc28482044
Ref: library/smtplib smtplib SMTP ehlo_or_helo_if_needed8482943
Ref: 2dc48482943
Ref: library/smtplib smtplib SMTP has_extn8483291
Ref: 2dc38483291
Ref: library/smtplib smtplib SMTP verify8483492
Ref: 2dc58483492
Ref: library/smtplib smtplib SMTP login8483919
Ref: 2dc68483919
Ref: library/smtplib smtplib SMTP auth8485495
Ref: 7478485495
Ref: library/smtplib smtplib SMTP starttls8487738
Ref: a898487738
Ref: library/smtplib smtplib SMTP sendmail8489411
Ref: 7498489411
Ref: library/smtplib smtplib SMTP send_message8492880
Ref: 74a8492880
Ref: library/smtplib smtplib SMTP quit8494945
Ref: 2db68494945
Ref: SMTP Objects-Footnote-18495414
Ref: SMTP Objects-Footnote-28495462
Ref: SMTP Objects-Footnote-38495511
Ref: SMTP Objects-Footnote-48495560
Ref: SMTP Objects-Footnote-58495608
Ref: SMTP Objects-Footnote-68495656
Node: SMTP Example8495705
Ref: library/smtplib id28495807
Ref: 2dc78495807
Ref: library/smtplib smtp-example8495807
Ref: 2dc88495807
Ref: SMTP Example-Footnote-18497242
Node: smtpd --- SMTP Server8497290
Ref: library/smtpd doc8497455
Ref: 2dc98497455
Ref: library/smtpd module-smtpd8497455
Ref: ed8497455
Ref: library/smtpd smtpd-smtp-server8497455
Ref: 2dca8497455
Ref: smtpd --- SMTP Server-Footnote-18498457
Ref: smtpd --- SMTP Server-Footnote-28498521
Ref: smtpd --- SMTP Server-Footnote-38498561
Ref: smtpd --- SMTP Server-Footnote-48498610
Ref: smtpd --- SMTP Server-Footnote-58498659
Node: SMTPServer Objects8498708
Ref: library/smtpd smtpserver-objects8498816
Ref: 2dcb8498816
Ref: library/smtpd smtpd SMTPServer8498875
Ref: 6078498875
Ref: library/smtpd smtpd SMTPServer process_message8500733
Ref: 6088500733
Ref: library/smtpd smtpd SMTPServer channel_class8502615
Ref: 2dcc8502615
Ref: SMTPServer Objects-Footnote-18503201
Ref: SMTPServer Objects-Footnote-28503250
Ref: SMTPServer Objects-Footnote-38503299
Ref: SMTPServer Objects-Footnote-48503348
Node: DebuggingServer Objects8503397
Ref: library/smtpd debuggingserver-objects8503531
Ref: 2dcd8503531
Ref: library/smtpd smtpd DebuggingServer8503600
Ref: 2dce8503600
Node: PureProxy Objects8503803
Ref: library/smtpd pureproxy-objects8503939
Ref: 2dcf8503939
Ref: library/smtpd smtpd PureProxy8503996
Ref: 2dd08503996
Node: MailmanProxy Objects8504288
Ref: library/smtpd mailmanproxy-objects8504420
Ref: 2dd18504420
Ref: library/smtpd smtpd MailmanProxy8504483
Ref: 2dd28504483
Node: SMTPChannel Objects8504894
Ref: library/smtpd smtpchannel-objects8505000
Ref: 2dd38505000
Ref: library/smtpd smtpd SMTPChannel8505061
Ref: 6068505061
Ref: library/smtpd smtpd SMTPChannel smtp_server8506539
Ref: 2dd48506539
Ref: library/smtpd smtpd SMTPChannel conn8506640
Ref: 2dd58506640
Ref: library/smtpd smtpd SMTPChannel addr8506724
Ref: 2dd68506724
Ref: library/smtpd smtpd SMTPChannel received_lines8506856
Ref: 2dd78506856
Ref: library/smtpd smtpd SMTPChannel smtp_state8507074
Ref: 2dd88507074
Ref: library/smtpd smtpd SMTPChannel seen_greeting8507277
Ref: 2dd98507277
Ref: library/smtpd smtpd SMTPChannel mailfrom8507403
Ref: 2dda8507403
Ref: library/smtpd smtpd SMTPChannel rcpttos8507542
Ref: 2ddb8507542
Ref: library/smtpd smtpd SMTPChannel received_data8507690
Ref: 2ddc8507690
Ref: library/smtpd smtpd SMTPChannel fqdn8507896
Ref: 2ddd8507896
Ref: library/smtpd smtpd SMTPChannel peer8508037
Ref: 2dde8508037
Ref: SMTPChannel Objects-Footnote-18510482
Ref: SMTPChannel Objects-Footnote-28510531
Node: telnetlib --- Telnet client8510580
Ref: library/telnetlib doc8510756
Ref: 2ddf8510756
Ref: library/telnetlib module-telnetlib8510756
Ref: 1038510756
Ref: library/telnetlib telnetlib-telnet-client8510756
Ref: 2de08510756
Ref: library/telnetlib telnetlib Telnet8511758
Ref: 59c8511758
Ref: telnetlib --- Telnet client-Footnote-18513299
Ref: telnetlib --- Telnet client-Footnote-28513367
Ref: telnetlib --- Telnet client-Footnote-38513415
Node: Telnet Objects8513463
Ref: library/telnetlib id18513564
Ref: 2de38513564
Ref: library/telnetlib telnet-objects8513564
Ref: 2de48513564
Ref: library/telnetlib telnetlib Telnet read_until8513673
Ref: 2de58513673
Ref: library/telnetlib telnetlib Telnet read_all8514034
Ref: 2de68514034
Ref: library/telnetlib telnetlib Telnet read_some8514143
Ref: 2de78514143
Ref: library/telnetlib telnetlib Telnet read_very_eager8514327
Ref: 2de88514327
Ref: library/telnetlib telnetlib Telnet read_eager8514644
Ref: 2de98514644
Ref: library/telnetlib telnetlib Telnet read_lazy8514924
Ref: 2dea8514924
Ref: library/telnetlib telnetlib Telnet read_very_lazy8515221
Ref: 2deb8515221
Ref: library/telnetlib telnetlib Telnet read_sb_data8515500
Ref: 2dec8515500
Ref: library/telnetlib telnetlib Telnet open8515739
Ref: 2de18515739
Ref: library/telnetlib telnetlib Telnet msg8516311
Ref: 2ded8516311
Ref: library/telnetlib telnetlib Telnet set_debuglevel8516543
Ref: 2dee8516543
Ref: library/telnetlib telnetlib Telnet close8516721
Ref: 2de28516721
Ref: library/telnetlib telnetlib Telnet get_socket8516784
Ref: 2def8516784
Ref: library/telnetlib telnetlib Telnet fileno8516872
Ref: 2df08516872
Ref: library/telnetlib telnetlib Telnet write8516979
Ref: 2df18516979
Ref: library/telnetlib telnetlib Telnet interact8517445
Ref: 2df28517445
Ref: library/telnetlib telnetlib Telnet mt_interact8517547
Ref: 2df38517547
Ref: library/telnetlib telnetlib Telnet expect8517643
Ref: 2df48517643
Ref: library/telnetlib telnetlib Telnet set_option_negotiation_callback8518655
Ref: 2df58518655
Node: Telnet Example8518976
Ref: library/telnetlib id28519077
Ref: 2df68519077
Ref: library/telnetlib telnet-example8519077
Ref: 2df78519077
Node: uuid --- UUID objects according to RFC 41228519633
Ref: library/uuid doc8519836
Ref: 2df88519836
Ref: library/uuid module-uuid8519836
Ref: 1258519836
Ref: library/uuid uuid-uuid-objects-according-to-rfc-41228519836
Ref: 2df98519836
Ref: library/uuid uuid SafeUUID8520958
Ref: 2dfd8520958
Ref: library/uuid uuid SafeUUID safe8521009
Ref: 2dfe8521009
Ref: library/uuid uuid SafeUUID unsafe8521123
Ref: 2dff8521123
Ref: library/uuid uuid SafeUUID unknown8521217
Ref: 2e008521217
Ref: library/uuid uuid UUID8521355
Ref: 2618521355
Ref: library/uuid uuid UUID bytes8523317
Ref: 2e028523317
Ref: library/uuid uuid UUID bytes_le8523443
Ref: 2e038523443
Ref: library/uuid uuid UUID fields8523592
Ref: 2e048523592
Ref: library/uuid uuid UUID hex8525149
Ref: 2e058525149
Ref: library/uuid uuid UUID int8525224
Ref: 2e018525224
Ref: library/uuid uuid UUID urn8525283
Ref: 2e068525283
Ref: library/uuid uuid UUID variant8525358
Ref: 2e078525358
Ref: library/uuid uuid UUID version8525619
Ref: 2e0c8525619
Ref: library/uuid uuid UUID is_safe8525754
Ref: 4168525754
Ref: library/uuid uuid getnode8526004
Ref: 4178526004
Ref: library/uuid uuid uuid18526959
Ref: 4188526959
Ref: library/uuid uuid uuid38527309
Ref: 2dfa8527309
Ref: library/uuid uuid uuid48527476
Ref: 2dfb8527476
Ref: library/uuid uuid uuid58527533
Ref: 2dfc8527533
Ref: library/uuid uuid NAMESPACE_DNS8527833
Ref: 2e0d8527833
Ref: library/uuid uuid NAMESPACE_URL8527960
Ref: 2e0e8527960
Ref: library/uuid uuid NAMESPACE_OID8528058
Ref: 2e0f8528058
Ref: library/uuid uuid NAMESPACE_X5008528161
Ref: 2e108528161
Ref: library/uuid uuid RESERVED_NCS8528419
Ref: 2e088528419
Ref: library/uuid uuid RFC_41228528486
Ref: 2e098528486
Ref: library/uuid uuid RESERVED_MICROSOFT8528565
Ref: 2e0a8528565
Ref: library/uuid uuid RESERVED_FUTURE8528644
Ref: 2e0b8528644
Ref: uuid --- UUID objects according to RFC 4122-Footnote-18529021
Ref: uuid --- UUID objects according to RFC 4122-Footnote-28529084
Ref: uuid --- UUID objects according to RFC 4122-Footnote-38529133
Ref: uuid --- UUID objects according to RFC 4122-Footnote-48529182
Ref: uuid --- UUID objects according to RFC 4122-Footnote-58529231
Ref: uuid --- UUID objects according to RFC 4122-Footnote-68529280
Ref: uuid --- UUID objects according to RFC 4122-Footnote-78529329
Node: Example<13>8529378
Ref: library/uuid example8529469
Ref: 2e118529469
Ref: library/uuid uuid-example8529469
Ref: 2e128529469
Node: socketserver --- A framework for network servers8530728
Ref: library/socketserver doc8530932
Ref: 2e138530932
Ref: library/socketserver module-socketserver8530932
Ref: f18530932
Ref: library/socketserver socketserver-a-framework-for-network-servers8530932
Ref: 2e148530932
Ref: library/socketserver socketserver TCPServer8531291
Ref: 2e158531291
Ref: library/socketserver socketserver UDPServer8531763
Ref: 2e188531763
Ref: library/socketserver socketserver UnixStreamServer8532067
Ref: 2e198532067
Ref: library/socketserver socketserver UnixDatagramServer8532181
Ref: 2e1a8532181
Ref: socketserver --- A framework for network servers-Footnote-18534535
Node: Server Creation Notes8534606
Ref: library/socketserver server-creation-notes8534738
Ref: 2e1f8534738
Ref: library/socketserver socketserver ForkingMixIn8535572
Ref: 3da8535572
Ref: library/socketserver socketserver ThreadingMixIn8535610
Ref: 3db8535610
Ref: library/socketserver socketserver ForkingTCPServer8537092
Ref: 2e218537092
Ref: library/socketserver socketserver ForkingUDPServer8537134
Ref: 2e228537134
Ref: library/socketserver socketserver ThreadingTCPServer8537176
Ref: 2e238537176
Ref: library/socketserver socketserver ThreadingUDPServer8537220
Ref: 2e208537220
Node: Server Objects<2>8539508
Ref: library/socketserver server-objects8539672
Ref: 2e258539672
Ref: library/socketserver socketserver BaseServer8539723
Ref: a8e8539723
Ref: library/socketserver socketserver BaseServer fileno8540123
Ref: 2e288540123
Ref: library/socketserver socketserver BaseServer handle_request8540402
Ref: 2e1d8540402
Ref: library/socketserver socketserver BaseServer serve_forever8541010
Ref: a908541010
Ref: library/socketserver socketserver BaseServer service_actions8541658
Ref: a8f8541658
Ref: library/socketserver socketserver BaseServer shutdown8541962
Ref: 10228541962
Ref: library/socketserver socketserver BaseServer server_close8542248
Ref: 2e1e8542248
Ref: library/socketserver socketserver BaseServer address_family8542340
Ref: 2e2e8542340
Ref: library/socketserver socketserver BaseServer RequestHandlerClass8542548
Ref: 2e278542548
Ref: library/socketserver socketserver BaseServer server_address8542703
Ref: 2e268542703
Ref: library/socketserver socketserver BaseServer socket8543123
Ref: 2e2f8543123
Ref: library/socketserver socketserver BaseServer allow_reuse_address8543306
Ref: 2e308543306
Ref: library/socketserver socketserver BaseServer request_queue_size8543517
Ref: 2e318543517
Ref: library/socketserver socketserver BaseServer socket_type8544001
Ref: 2e328544001
Ref: library/socketserver socketserver BaseServer timeout8544189
Ref: 2e2c8544189
Ref: library/socketserver socketserver BaseServer finish_request8544692
Ref: 2e338544692
Ref: library/socketserver socketserver BaseServer get_request8544915
Ref: 2e298544915
Ref: library/socketserver socketserver BaseServer handle_error8545151
Ref: 6028545151
Ref: library/socketserver socketserver BaseServer handle_timeout8545600
Ref: 2e2d8545600
Ref: library/socketserver socketserver BaseServer process_request8546045
Ref: 2e2b8546045
Ref: library/socketserver socketserver BaseServer server_activate8546422
Ref: 2e178546422
Ref: library/socketserver socketserver BaseServer server_bind8546675
Ref: 2e168546675
Ref: library/socketserver socketserver BaseServer verify_request8546835
Ref: 2e2a8546835
Node: Request Handler Objects8547417
Ref: library/socketserver request-handler-objects8547572
Ref: 2e348547572
Ref: library/socketserver socketserver BaseRequestHandler8547641
Ref: 2e1b8547641
Ref: library/socketserver socketserver BaseRequestHandler setup8547996
Ref: 2e358547996
Ref: library/socketserver socketserver BaseRequestHandler handle8548197
Ref: 2e1c8548197
Ref: library/socketserver socketserver BaseRequestHandler finish8548907
Ref: 2e368548907
Ref: library/socketserver socketserver StreamRequestHandler8549192
Ref: 58c8549192
Ref: library/socketserver socketserver DatagramRequestHandler8549238
Ref: 2e248549238
Node: Examples<23>8549994
Ref: library/socketserver examples8550123
Ref: 2e378550123
Node: socketserver TCPServer Example8550328
Ref: library/socketserver socketserver-tcpserver-example8550446
Ref: 2e388550446
Node: socketserver UDPServer Example8553602
Ref: library/socketserver socketserver-udpserver-example8553748
Ref: 2e398553748
Node: Asynchronous Mixins8555365
Ref: library/socketserver asynchronous-mixins8555472
Ref: 2e3a8555472
Node: http server --- HTTP servers8557818
Ref: library/http server doc8558017
Ref: 2e3b8558017
Ref: library/http server http-server-http-servers8558017
Ref: 2e3c8558017
Ref: library/http server module-http server8558017
Ref: 978558017
Ref: library/http server http server HTTPServer8558827
Ref: 2c0c8558827
Ref: library/http server http server ThreadingHTTPServer8559183
Ref: 39b8559183
Ref: library/http server http server BaseHTTPRequestHandler8559730
Ref: a138559730
Ref: library/http server http server BaseHTTPRequestHandler client_address8560721
Ref: 2e3d8560721
Ref: library/http server http server BaseHTTPRequestHandler server8560860
Ref: 2e3e8560860
Ref: library/http server http server BaseHTTPRequestHandler close_connection8560926
Ref: 2e3f8560926
Ref: library/http server http server BaseHTTPRequestHandler requestline8561158
Ref: 2e418561158
Ref: library/http server http server BaseHTTPRequestHandler command8561470
Ref: 2e428561470
Ref: library/http server http server BaseHTTPRequestHandler path8561571
Ref: 2e438561571
Ref: library/http server http server BaseHTTPRequestHandler request_version8561842
Ref: 2e448561842
Ref: library/http server http server BaseHTTPRequestHandler headers8561975
Ref: 2cea8561975
Ref: library/http server http server BaseHTTPRequestHandler rfile8562399
Ref: 2e468562399
Ref: library/http server http server BaseHTTPRequestHandler wfile8562548
Ref: 2e478562548
Ref: library/http server http server BaseHTTPRequestHandler server_version8562974
Ref: 2e488562974
Ref: library/http server http server BaseHTTPRequestHandler sys_version8563258
Ref: 2e498563258
Ref: library/http server http server BaseHTTPRequestHandler error_message_format8563510
Ref: 2e4b8563510
Ref: library/http server http server BaseHTTPRequestHandler error_content_type8563868
Ref: 2e4c8563868
Ref: library/http server http server BaseHTTPRequestHandler protocol_version8564045
Ref: 2e4d8564045
Ref: library/http server http server BaseHTTPRequestHandler MessageClass8564505
Ref: 2e458564505
Ref: library/http server http server BaseHTTPRequestHandler responses8564734
Ref: 2cd78564734
Ref: library/http server http server BaseHTTPRequestHandler handle8565296
Ref: 2e508565296
Ref: library/http server http server BaseHTTPRequestHandler handle_one_request8565602
Ref: 2e408565602
Ref: library/http server http server BaseHTTPRequestHandler handle_expect_1008565806
Ref: 2e518565806
Ref: library/http server http server BaseHTTPRequestHandler send_error8566316
Ref: 8618566316
Ref: library/http server http server BaseHTTPRequestHandler send_response8567441
Ref: 2e528567441
Ref: library/http server http server BaseHTTPRequestHandler send_header8568244
Ref: 2e4e8568244
Ref: library/http server http server BaseHTTPRequestHandler send_response_only8568811
Ref: 2e4f8568811
Ref: library/http server http server BaseHTTPRequestHandler end_headers8569235
Ref: a148569235
Ref: library/http server http server BaseHTTPRequestHandler flush_headers8569531
Ref: a158569531
Ref: library/http server http server BaseHTTPRequestHandler log_request8569707
Ref: 2e548569707
Ref: library/http server http server BaseHTTPRequestHandler log_error8570010
Ref: 2e558570010
Ref: library/http server http server BaseHTTPRequestHandler log_message8570261
Ref: 2e568570261
Ref: library/http server http server BaseHTTPRequestHandler version_string8570756
Ref: 2e4a8570756
Ref: library/http server http server BaseHTTPRequestHandler date_time_string8570976
Ref: 2e538570976
Ref: library/http server http server BaseHTTPRequestHandler log_date_time_string8571370
Ref: 2e578571370
Ref: library/http server http server BaseHTTPRequestHandler address_string8571487
Ref: 2e588571487
Ref: library/http server http server SimpleHTTPRequestHandler8571717
Ref: 39a8571717
Ref: library/http server http server SimpleHTTPRequestHandler server_version8572275
Ref: 2e5b8572275
Ref: library/http server http server SimpleHTTPRequestHandler extensions_map8572433
Ref: 2e5c8572433
Ref: library/http server http server SimpleHTTPRequestHandler directory8572752
Ref: 2e5d8572752
Ref: library/http server http server SimpleHTTPRequestHandler do_HEAD8572965
Ref: 2e5a8572965
Ref: library/http server http server SimpleHTTPRequestHandler do_GET8573259
Ref: 2e598573259
Ref: library/http server http-server-cli8575673
Ref: 8628575673
Ref: library/http server http server CGIHTTPRequestHandler8576678
Ref: 2e5e8576678
Ref: library/http server http server CGIHTTPRequestHandler cgi_directories8577872
Ref: 2e5f8577872
Ref: library/http server http server CGIHTTPRequestHandler do_POST8578115
Ref: 2e608578115
Ref: http server --- HTTP servers-Footnote-18578694
Ref: http server --- HTTP servers-Footnote-28578764
Ref: http server --- HTTP servers-Footnote-38578813
Node: http cookies --- HTTP state management8578862
Ref: library/http cookies doc8579064
Ref: 2e618579064
Ref: library/http cookies http-cookies-http-state-management8579064
Ref: 2e628579064
Ref: library/http cookies module-http cookies8579064
Ref: 968579064
Ref: library/http cookies http cookies CookieError8580419
Ref: 2e638580419
Ref: library/http cookies http cookies BaseCookie8580583
Ref: 2e648580583
Ref: library/http cookies http cookies SimpleCookie8580973
Ref: 103d8580973
Ref: http cookies --- HTTP state management-Footnote-18581803
Ref: http cookies --- HTTP state management-Footnote-28581874
Ref: http cookies --- HTTP state management-Footnote-38581923
Ref: http cookies --- HTTP state management-Footnote-48581972
Ref: http cookies --- HTTP state management-Footnote-58582021
Node: Cookie Objects8582070
Ref: library/http cookies cookie-objects8582182
Ref: 2e668582182
Ref: library/http cookies id18582182
Ref: 2e678582182
Ref: library/http cookies http cookies BaseCookie value_decode8582233
Ref: 2e688582233
Ref: library/http cookies http cookies BaseCookie value_encode8582511
Ref: 2e698582511
Ref: library/http cookies http cookies BaseCookie output8582969
Ref: 2e6a8582969
Ref: library/http cookies http cookies BaseCookie js_output8583343
Ref: 2e6b8583343
Ref: library/http cookies http cookies BaseCookie load8583628
Ref: 2e658583628
Node: Morsel Objects8583916
Ref: library/http cookies id28584048
Ref: 2e6c8584048
Ref: library/http cookies morsel-objects8584048
Ref: 2e6d8584048
Ref: library/http cookies http cookies Morsel8584099
Ref: 4958584099
Ref: library/http cookies http cookies Morsel value8585417
Ref: 4938585417
Ref: library/http cookies http cookies Morsel coded_value8585474
Ref: 4948585474
Ref: library/http cookies http cookies Morsel key8585577
Ref: 4928585577
Ref: library/http cookies http cookies Morsel set8585631
Ref: 4968585631
Ref: library/http cookies http cookies Morsel isReservedKey8585746
Ref: 2e6e8585746
Ref: library/http cookies http cookies Morsel output8585863
Ref: 2e6f8585863
Ref: library/http cookies http cookies Morsel js_output8586209
Ref: 2e708586209
Ref: library/http cookies http cookies Morsel OutputString8586489
Ref: 2e718586489
Ref: library/http cookies http cookies Morsel update8586707
Ref: 7c98586707
Ref: library/http cookies http cookies Morsel copy8587004
Ref: 7c88587004
Ref: library/http cookies http cookies Morsel setdefault8587156
Ref: 2e728587156
Ref: Morsel Objects-Footnote-18587377
Ref: Morsel Objects-Footnote-28587426
Ref: Morsel Objects-Footnote-38587475
Ref: Morsel Objects-Footnote-48587524
Node: Example<14>8587573
Ref: library/http cookies cookie-example8587682
Ref: 2e738587682
Ref: library/http cookies example8587682
Ref: 2e748587682
Node: http cookiejar --- Cookie handling for HTTP clients8589334
Ref: library/http cookiejar doc8589551
Ref: 2e758589551
Ref: library/http cookiejar http-cookiejar-cookie-handling-for-http-clients8589551
Ref: 2e768589551
Ref: library/http cookiejar module-http cookiejar8589551
Ref: 958589551
Ref: library/http cookiejar http cookiejar LoadError8591121
Ref: 2e778591121
Ref: library/http cookiejar http cookiejar CookieJar8591484
Ref: 2c7a8591484
Ref: library/http cookiejar http cookiejar FileCookieJar8591961
Ref: 2e788591961
Ref: library/http cookiejar http cookiejar CookiePolicy8592697
Ref: 2e798592697
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy8592858
Ref: ff38592858
Ref: library/http cookiejar http cookiejar Cookie8594680
Ref: 2e7e8594680
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-18596380
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-28596453
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-38596502
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-48596551
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-58596600
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-68596649
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-78596698
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-88596747
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-98596796
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-108596845
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-118596895
Ref: http cookiejar --- Cookie handling for HTTP clients-Footnote-128596945
Node: CookieJar and FileCookieJar Objects8596995
Ref: library/http cookiejar cookie-jar-objects8597186
Ref: 2e7f8597186
Ref: library/http cookiejar cookiejar-and-filecookiejar-objects8597186
Ref: 2e808597186
Ref: library/http cookiejar http cookiejar CookieJar add_cookie_header8597463
Ref: 2e818597463
Ref: library/http cookiejar http cookiejar CookieJar extract_cookies8598377
Ref: 2e828598377
Ref: library/http cookiejar http cookiejar CookieJar set_policy8599608
Ref: 2e848599608
Ref: library/http cookiejar http cookiejar CookieJar make_cookies8599718
Ref: 2e858599718
Ref: library/http cookiejar http cookiejar CookieJar set_cookie_if_ok8600011
Ref: 2e868600011
Ref: library/http cookiejar http cookiejar CookieJar set_cookie8600142
Ref: 2e878600142
Ref: library/http cookiejar http cookiejar CookieJar clear8600297
Ref: 2e888600297
Ref: library/http cookiejar http cookiejar CookieJar clear_session_cookies8600808
Ref: 2e898600808
Ref: library/http cookiejar http cookiejar FileCookieJar save8601457
Ref: 2e8a8601457
Ref: library/http cookiejar http cookiejar FileCookieJar load8602316
Ref: 2e7a8602316
Ref: library/http cookiejar http cookiejar FileCookieJar revert8602880
Ref: 2e7b8602880
Ref: library/http cookiejar http cookiejar FileCookieJar filename8603285
Ref: 2e8b8603285
Ref: library/http cookiejar http cookiejar FileCookieJar delayload8603419
Ref: 2e8c8603419
Node: FileCookieJar subclasses and co-operation with web browsers8603837
Ref: library/http cookiejar file-cookie-jar-classes8604057
Ref: 2e7c8604057
Ref: library/http cookiejar filecookiejar-subclasses-and-co-operation-with-web-browsers8604057
Ref: 2e8d8604057
Ref: library/http cookiejar http cookiejar MozillaCookieJar8604285
Ref: 2e8e8604285
Ref: library/http cookiejar http cookiejar LWPCookieJar8605084
Ref: 2e8f8605084
Ref: FileCookieJar subclasses and co-operation with web browsers-Footnote-18605554
Node: CookiePolicy Objects8605603
Ref: library/http cookiejar cookie-policy-objects8605815
Ref: 2e908605815
Ref: library/http cookiejar cookiepolicy-objects8605815
Ref: 2e918605815
Ref: library/http cookiejar http cookiejar CookiePolicy set_ok8605968
Ref: 2e838605968
Ref: library/http cookiejar http cookiejar CookiePolicy return_ok8606300
Ref: 2e928606300
Ref: library/http cookiejar http cookiejar CookiePolicy domain_return_ok8606635
Ref: 2e938606635
Ref: library/http cookiejar http cookiejar CookiePolicy path_return_ok8608019
Ref: 2e948608019
Ref: library/http cookiejar http cookiejar CookiePolicy netscape8608477
Ref: 2e958608477
Ref: library/http cookiejar http cookiejar CookiePolicy rfc29658608547
Ref: 2e968608547
Ref: library/http cookiejar http cookiejar CookiePolicy hide_cookie28608619
Ref: 2e978608619
Ref: CookiePolicy Objects-Footnote-18609166
Ref: CookiePolicy Objects-Footnote-28609215
Node: DefaultCookiePolicy Objects8609264
Ref: library/http cookiejar default-cookie-policy-objects8609434
Ref: 2e988609434
Ref: library/http cookiejar defaultcookiepolicy-objects8609434
Ref: 2e998609434
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy blocked_domains8611751
Ref: 2e9a8611751
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy set_blocked_domains8611868
Ref: 2e9b8611868
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy is_blocked8611988
Ref: 2e9c8611988
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy allowed_domains8612136
Ref: 2e9d8612136
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy set_allowed_domains8612278
Ref: 2e9e8612278
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy is_not_allowed8612418
Ref: 2e9f8612418
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy rfc2109_as_netscape8612757
Ref: 2e7d8612757
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_domain8613341
Ref: 2ea08613341
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_rfc2965_unverifiable8613642
Ref: 2ea18613642
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_ns_unverifiable8614017
Ref: 2ea28614017
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_ns_domain8614163
Ref: 2ea38614163
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_ns_set_initial_dollar8614341
Ref: 2ea48614341
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy strict_ns_set_path8614493
Ref: 2ea58614493
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy DomainStrictNoDots8614814
Ref: 2ea68614814
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy DomainStrictNonDomain8615056
Ref: 2ea78615056
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy DomainRFC2965Match8615401
Ref: 2ea88615401
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy DomainLiberal8615635
Ref: 2ea98615635
Ref: library/http cookiejar http cookiejar DefaultCookiePolicy DomainStrict8615780
Ref: 2eaa8615780
Ref: DefaultCookiePolicy Objects-Footnote-18615930
Ref: DefaultCookiePolicy Objects-Footnote-28615979
Ref: DefaultCookiePolicy Objects-Footnote-38616028
Ref: DefaultCookiePolicy Objects-Footnote-48616077
Ref: DefaultCookiePolicy Objects-Footnote-58616126
Ref: DefaultCookiePolicy Objects-Footnote-68616175
Ref: DefaultCookiePolicy Objects-Footnote-78616224
Node: Cookie Objects<2>8616273
Ref: library/http cookiejar cookie-objects8616435
Ref: 2eab8616435
Ref: library/http cookiejar http cookiejar Cookie version8617204
Ref: 2eac8617204
Ref: library/http cookiejar http cookiejar Cookie name8617559
Ref: 2ead8617559
Ref: library/http cookiejar http cookiejar Cookie value8617614
Ref: 2eae8617614
Ref: library/http cookiejar http cookiejar Cookie port8617691
Ref: 2eaf8617691
Ref: library/http cookiejar http cookiejar Cookie path8617827
Ref: 2eb08617827
Ref: library/http cookiejar http cookiejar Cookie secure8617919
Ref: 2eb18617919
Ref: library/http cookiejar http cookiejar Cookie expires8618023
Ref: 2eb28618023
Ref: library/http cookiejar http cookiejar Cookie discard8618173
Ref: 2eb48618173
Ref: library/http cookiejar http cookiejar Cookie comment8618247
Ref: 2eb58618247
Ref: library/http cookiejar http cookiejar Cookie comment_url8618377
Ref: 2eb68618377
Ref: library/http cookiejar http cookiejar Cookie rfc21098618521
Ref: 2eb78618521
Ref: library/http cookiejar http cookiejar Cookie port_specified8618928
Ref: 2eb88618928
Ref: library/http cookiejar http cookiejar Cookie domain_specified8619104
Ref: 2eb98619104
Ref: library/http cookiejar http cookiejar Cookie domain_initial_dot8619210
Ref: 2eba8619210
Ref: library/http cookiejar http cookiejar Cookie has_nonstandard_attr8619463
Ref: 2ebb8619463
Ref: library/http cookiejar http cookiejar Cookie get_nonstandard_attr8619583
Ref: 2ebc8619583
Ref: library/http cookiejar http cookiejar Cookie set_nonstandard_attr8619751
Ref: 2ebd8619751
Ref: library/http cookiejar http cookiejar Cookie is_expired8619929
Ref: 2eb38619929
Ref: Cookie Objects<2>-Footnote-18620228
Ref: Cookie Objects<2>-Footnote-28620277
Ref: Cookie Objects<2>-Footnote-38620326
Ref: Cookie Objects<2>-Footnote-48620375
Node: Examples<24>8620424
Ref: library/http cookiejar examples8620550
Ref: 2ebe8620550
Ref: Examples<24>-Footnote-18622002
Node: xmlrpc --- XMLRPC server and client modules8622051
Ref: library/xmlrpc doc8622269
Ref: 2ebf8622269
Ref: library/xmlrpc xmlrpc-xmlrpc-server-and-client-modules8622269
Ref: 2ec08622269
Node: xmlrpc client --- XML-RPC client access8622771
Ref: library/xmlrpc client doc8622977
Ref: 2ec18622977
Ref: library/xmlrpc client module-xmlrpc client8622977
Ref: 1408622977
Ref: library/xmlrpc client xmlrpc-client-xml-rpc-client-access8622977
Ref: 2ec28622977
Ref: library/xmlrpc client xmlrpc client ServerProxy8623900
Ref: 2568623900
Ref: xmlrpc client --- XML-RPC client access-Footnote-18631671
Ref: xmlrpc client --- XML-RPC client access-Footnote-28631743
Ref: xmlrpc client --- XML-RPC client access-Footnote-38631837
Ref: xmlrpc client --- XML-RPC client access-Footnote-48631896
Ref: xmlrpc client --- XML-RPC client access-Footnote-58631955
Ref: xmlrpc client --- XML-RPC client access-Footnote-68632001
Node: ServerProxy Objects8632050
Ref: library/xmlrpc client id18632172
Ref: 2ec78632172
Ref: library/xmlrpc client serverproxy-objects8632172
Ref: 2ec88632172
Ref: library/xmlrpc client xmlrpc client ServerProxy system listMethods8632828
Ref: 2ec98632828
Ref: library/xmlrpc client xmlrpc client ServerProxy system methodSignature8632997
Ref: 2eca8632997
Ref: library/xmlrpc client xmlrpc client ServerProxy system methodHelp8634019
Ref: 2ecb8634019
Node: 日期時間物件8635091
Ref: library/xmlrpc client datetime-objects8635236
Ref: 2ecc8635236
Ref: library/xmlrpc client id28635236
Ref: 2ecd8635236
Ref: library/xmlrpc client xmlrpc client DateTime8635289
Ref: 2ec38635289
Ref: library/xmlrpc client xmlrpc client DateTime decode8635599
Ref: 2ece8635599
Ref: library/xmlrpc client xmlrpc client DateTime encode8635702
Ref: 2ecf8635702
Node: Binary Objects8636780
Ref: library/xmlrpc client binary-objects8636919
Ref: 2ed08636919
Ref: library/xmlrpc client id38636919
Ref: 2ed18636919
Ref: library/xmlrpc client xmlrpc client Binary8636970
Ref: 2ec48636970
Ref: library/xmlrpc client xmlrpc client Binary data8637188
Ref: 2ed28637188
Ref: library/xmlrpc client xmlrpc client Binary decode8637491
Ref: 2ed38637491
Ref: library/xmlrpc client xmlrpc client Binary encode8637636
Ref: 2ed48637636
Ref: Binary Objects-Footnote-18638885
Node: Fault Objects8638946
Ref: library/xmlrpc client fault-objects8639088
Ref: 2ed58639088
Ref: library/xmlrpc client id48639088
Ref: 2ed68639088
Ref: library/xmlrpc client xmlrpc client Fault8639137
Ref: 2ec58639137
Ref: library/xmlrpc client xmlrpc client Fault faultCode8639305
Ref: 2ed78639305
Ref: library/xmlrpc client xmlrpc client Fault faultString8639380
Ref: 2ed88639380
Node: ProtocolError Objects8640339
Ref: library/xmlrpc client protocol-error-objects8640484
Ref: 2ed98640484
Ref: library/xmlrpc client protocolerror-objects8640484
Ref: 2eda8640484
Ref: library/xmlrpc client xmlrpc client ProtocolError8640549
Ref: 2ec68640549
Ref: library/xmlrpc client xmlrpc client ProtocolError url8640827
Ref: 2edb8640827
Ref: library/xmlrpc client xmlrpc client ProtocolError errcode8640901
Ref: 2edc8640901
Ref: library/xmlrpc client xmlrpc client ProtocolError errmsg8640954
Ref: 2edd8640954
Ref: library/xmlrpc client xmlrpc client ProtocolError headers8641030
Ref: 2ede8641030
Node: MultiCall Objects8641767
Ref: library/xmlrpc client multicall-objects8641920
Ref: 2edf8641920
Ref: library/xmlrpc client xmlrpc client MultiCall8642103
Ref: 2ee08642103
Ref: MultiCall Objects-Footnote-18643809
Node: Convenience Functions8643992
Ref: library/xmlrpc client convenience-functions8644147
Ref: 2ee18644147
Ref: library/xmlrpc client xmlrpc client dumps8644212
Ref: 2ee28644212
Ref: library/xmlrpc client xmlrpc client loads8644923
Ref: 2ee38644923
Node: Example of Client Usage8645780
Ref: library/xmlrpc client example-of-client-usage8645952
Ref: 2ee48645952
Ref: library/xmlrpc client xmlrpc-client-example8645952
Ref: 2ee58645952
Node: Example of Client and Server Usage8647259
Ref: library/xmlrpc client example-of-client-and-server-usage8647401
Ref: 2ee68647401
Node: xmlrpc server --- Basic XML-RPC servers8647550
Ref: library/xmlrpc server doc8647757
Ref: 2ee88647757
Ref: library/xmlrpc server module-xmlrpc server8647757
Ref: 1418647757
Ref: library/xmlrpc server xmlrpc-server-basic-xml-rpc-servers8647757
Ref: 2ee98647757
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCServer8648438
Ref: 2eea8648438
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler8649954
Ref: 2eeb8649954
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCRequestHandler8650597
Ref: 2eec8650597
Ref: xmlrpc server --- Basic XML-RPC servers-Footnote-18651086
Node: SimpleXMLRPCServer Objects8651158
Ref: library/xmlrpc server simple-xmlrpc-servers8651292
Ref: 2eed8651292
Ref: library/xmlrpc server simplexmlrpcserver-objects8651292
Ref: 2eee8651292
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCServer register_function8651528
Ref: 2eef8651528
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCServer register_instance8652268
Ref: 2ef08652268
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCServer register_introspection_functions8653889
Ref: 2ef18653889
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCServer register_multicall_functions8654104
Ref: 2ef28654104
Ref: library/xmlrpc server xmlrpc server SimpleXMLRPCRequestHandler rpc_paths8654239
Ref: 2ef38654239
Node: SimpleXMLRPCServer Example8654652
Ref: library/xmlrpc server id18654741
Ref: 2ef48654741
Ref: library/xmlrpc server simplexmlrpcserver-example8654741
Ref: 2ee78654741
Node: CGIXMLRPCRequestHandler8659257
Ref: library/xmlrpc server cgixmlrpcrequesthandler8659425
Ref: 2ef58659425
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler register_function8659609
Ref: 2ef68659609
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler register_instance8660354
Ref: 2ef78660354
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler register_introspection_functions8661245
Ref: 2ef88661245
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler register_multicall_functions8661474
Ref: 2ef98661474
Ref: library/xmlrpc server xmlrpc server CGIXMLRPCRequestHandler handle_request8661619
Ref: 2efa8661619
Node: Documenting XMLRPC server8662212
Ref: library/xmlrpc server documenting-xmlrpc-server8662377
Ref: 2efb8662377
Ref: library/xmlrpc server xmlrpc server DocXMLRPCServer8662704
Ref: f7c8662704
Ref: library/xmlrpc server xmlrpc server DocCGIXMLRPCRequestHandler8663174
Ref: 2efc8663174
Ref: library/xmlrpc server xmlrpc server DocXMLRPCRequestHandler8663310
Ref: 2efd8663310
Node: DocXMLRPCServer Objects8663629
Ref: library/xmlrpc server doc-xmlrpc-servers8663797
Ref: 2efe8663797
Ref: library/xmlrpc server docxmlrpcserver-objects8663797
Ref: 2eff8663797
Ref: library/xmlrpc server xmlrpc server DocXMLRPCServer set_server_title8664233
Ref: 2f008664233
Ref: library/xmlrpc server xmlrpc server DocXMLRPCServer set_server_name8664425
Ref: 2f018664425
Ref: library/xmlrpc server xmlrpc server DocXMLRPCServer set_server_documentation8664649
Ref: 2f028664649
Node: DocCGIXMLRPCRequestHandler8664911
Ref: library/xmlrpc server doccgixmlrpcrequesthandler8665045
Ref: 2f038665045
Ref: library/xmlrpc server xmlrpc server DocCGIXMLRPCRequestHandler set_server_title8665496
Ref: 2f048665496
Ref: library/xmlrpc server xmlrpc server DocCGIXMLRPCRequestHandler set_server_name8665699
Ref: 2f058665699
Ref: library/xmlrpc server xmlrpc server DocCGIXMLRPCRequestHandler set_server_documentation8665934
Ref: 2f068665934
Node: ipaddress --- IPv4/IPv6 manipulation library8666207
Ref: library/ipaddress doc8666366
Ref: 2f078666366
Ref: library/ipaddress ipaddress-ipv4-ipv6-manipulation-library8666366
Ref: 2f088666366
Ref: library/ipaddress module-ipaddress8666366
Ref: a38666366
Ref: ipaddress --- IPv4/IPv6 manipulation library-Footnote-18667369
Node: Convenience factory functions8667437
Ref: library/ipaddress convenience-factory-functions8667568
Ref: 2f0a8667568
Ref: library/ipaddress ipaddress ip_address8667771
Ref: 2f0b8667771
Ref: library/ipaddress ipaddress ip_network8668350
Ref: 2f0e8668350
Ref: library/ipaddress ipaddress ip_interface8669057
Ref: 2f0f8669057
Node: IP Addresses8669908
Ref: library/ipaddress ip-addresses8670070
Ref: 2f128670070
Node: Address objects8670213
Ref: library/ipaddress address-objects8670320
Ref: 2f138670320
Ref: library/ipaddress ipaddress IPv4Address8670763
Ref: 2f0c8670763
Ref: library/ipaddress ipaddress IPv4Address version8671828
Ref: 2f158671828
Ref: library/ipaddress ipaddress IPv4Address max_prefixlen8671933
Ref: 2f168671933
Ref: library/ipaddress ipaddress IPv4Address compressed8672268
Ref: 2f178672268
Ref: library/ipaddress ipaddress IPv4Address exploded8672297
Ref: 2f188672297
Ref: library/ipaddress ipaddress IPv4Address packed8672783
Ref: 2f198672783
Ref: library/ipaddress ipaddress IPv4Address reverse_pointer8673017
Ref: 2f1a8673017
Ref: library/ipaddress ipaddress IPv4Address is_multicast8673557
Ref: 2f1b8673557
Ref: library/ipaddress ipaddress IPv4Address is_private8673721
Ref: 2f1c8673721
Ref: library/ipaddress ipaddress IPv4Address is_global8673933
Ref: 8718673933
Ref: library/ipaddress ipaddress IPv4Address is_unspecified8674172
Ref: 2f1d8674172
Ref: library/ipaddress ipaddress IPv4Address is_reserved8674323
Ref: 2f1e8674323
Ref: library/ipaddress ipaddress IPv4Address is_loopback8674418
Ref: 2f1f8674418
Ref: library/ipaddress ipaddress IPv4Address is_link_local8674567
Ref: 2f208674567
Ref: library/ipaddress ipaddress IPv6Address8674699
Ref: 2f0d8674699
Ref: library/ipaddress ipaddress IPv6Address compressed8675628
Ref: 2f218675628
Ref: library/ipaddress ipaddress IPv6Address exploded8675934
Ref: 2f228675934
Ref: library/ipaddress ipaddress IPv6Address packed8676208
Ref: 2f238676208
Ref: library/ipaddress ipaddress IPv6Address reverse_pointer8676233
Ref: 2f248676233
Ref: library/ipaddress ipaddress IPv6Address version8676267
Ref: 2f258676267
Ref: library/ipaddress ipaddress IPv6Address max_prefixlen8676293
Ref: 2f268676293
Ref: library/ipaddress ipaddress IPv6Address is_multicast8676325
Ref: 2f278676325
Ref: library/ipaddress ipaddress IPv6Address is_private8676356
Ref: 2f288676356
Ref: library/ipaddress ipaddress IPv6Address is_global8676385
Ref: 2f298676385
Ref: library/ipaddress ipaddress IPv6Address is_unspecified8676413
Ref: 2f2a8676413
Ref: library/ipaddress ipaddress IPv6Address is_reserved8676446
Ref: 2f2b8676446
Ref: library/ipaddress ipaddress IPv6Address is_loopback8676476
Ref: 2f2c8676476
Ref: library/ipaddress ipaddress IPv6Address is_link_local8676506
Ref: 2f2d8676506
Ref: library/ipaddress ipaddress IPv6Address is_site_local8676577
Ref: 2f2e8676577
Ref: library/ipaddress ipaddress IPv6Address ipv4_mapped8676920
Ref: 2f2f8676920
Ref: library/ipaddress ipaddress IPv6Address sixtofour8677189
Ref: 2f308677189
Ref: library/ipaddress ipaddress IPv6Address teredo8677476
Ref: 2f318677476
Ref: Address objects-Footnote-18677823
Ref: Address objects-Footnote-28677872
Ref: Address objects-Footnote-38677921
Ref: Address objects-Footnote-48678023
Ref: Address objects-Footnote-58678125
Ref: Address objects-Footnote-68678227
Ref: Address objects-Footnote-78678329
Ref: Address objects-Footnote-88678378
Ref: Address objects-Footnote-98678427
Ref: Address objects-Footnote-108678476
Ref: Address objects-Footnote-118678526
Ref: Address objects-Footnote-128678576
Ref: Address objects-Footnote-138678626
Ref: Address objects-Footnote-148678676
Ref: Address objects-Footnote-158678726
Ref: Address objects-Footnote-168678776
Node: Conversion to Strings and Integers8678826
Ref: library/ipaddress conversion-to-strings-and-integers8678954
Ref: 2f328678954
Node: Operators<3>8679496
Ref: library/ipaddress operators8679600
Ref: 2f338679600
Node: Comparison operators8679865
Ref: library/ipaddress comparison-operators8679963
Ref: 2f348679963
Node: Arithmetic operators8680336
Ref: library/ipaddress arithmetic-operators8680434
Ref: 2f358680434
Node: IP Network definitions8680937
Ref: library/ipaddress ip-network-definitions8681087
Ref: 2f368681087
Node: Prefix net mask and host mask8681797
Ref: library/ipaddress prefix-net-mask-and-host-mask8681909
Ref: 2f378681909
Node: Network objects8682579
Ref: library/ipaddress network-objects8682712
Ref: 2f388682712
Ref: library/ipaddress ipaddress IPv4Network8683171
Ref: 3a58683171
Ref: library/ipaddress ipaddress IPv4Network version8685586
Ref: 2f3a8685586
Ref: library/ipaddress ipaddress IPv4Network max_prefixlen8685612
Ref: 2f3b8685612
Ref: library/ipaddress ipaddress IPv4Network is_multicast8685744
Ref: 2f3c8685744
Ref: library/ipaddress ipaddress IPv4Network is_private8685775
Ref: 2f3d8685775
Ref: library/ipaddress ipaddress IPv4Network is_unspecified8685804
Ref: 2f3e8685804
Ref: library/ipaddress ipaddress IPv4Network is_reserved8685837
Ref: 2f3f8685837
Ref: library/ipaddress ipaddress IPv4Network is_loopback8685867
Ref: 2f408685867
Ref: library/ipaddress ipaddress IPv4Network is_link_local8685897
Ref: 2f418685897
Ref: library/ipaddress ipaddress IPv4Network network_address8686086
Ref: 2f428686086
Ref: library/ipaddress ipaddress IPv4Network broadcast_address8686257
Ref: 2f438686257
Ref: library/ipaddress ipaddress IPv4Network hostmask8686451
Ref: 2f448686451
Ref: library/ipaddress ipaddress IPv4Network netmask8686543
Ref: 2f458686543
Ref: library/ipaddress ipaddress IPv4Network with_prefixlen8686633
Ref: 2f468686633
Ref: library/ipaddress ipaddress IPv4Network compressed8686666
Ref: 2f478686666
Ref: library/ipaddress ipaddress IPv4Network exploded8686695
Ref: 2f488686695
Ref: library/ipaddress ipaddress IPv4Network with_netmask8686993
Ref: 2f498686993
Ref: library/ipaddress ipaddress IPv4Network with_hostmask8687121
Ref: 2f4a8687121
Ref: library/ipaddress ipaddress IPv4Network num_addresses8687251
Ref: 2f4b8687251
Ref: library/ipaddress ipaddress IPv4Network prefixlen8687340
Ref: 2f4c8687340
Ref: library/ipaddress ipaddress IPv4Network hosts8687418
Ref: 2f4d8687418
Ref: library/ipaddress ipaddress IPv4Network overlaps8688421
Ref: 2f4e8688421
Ref: library/ipaddress ipaddress IPv4Network address_exclude8688599
Ref: 2f4f8688599
Ref: library/ipaddress ipaddress IPv4Network subnets8689211
Ref: 79c8689211
Ref: library/ipaddress ipaddress IPv4Network supernet8690765
Ref: 79d8690765
Ref: library/ipaddress ipaddress IPv4Network subnet_of8691577
Ref: 2f508691577
Ref: library/ipaddress ipaddress IPv4Network supernet_of8691878
Ref: 2f518691878
Ref: library/ipaddress ipaddress IPv4Network compare_networks8692185
Ref: 2f528692185
Ref: library/ipaddress ipaddress IPv6Network8692868
Ref: 3a48692868
Ref: library/ipaddress ipaddress IPv6Network version8694664
Ref: 2f538694664
Ref: library/ipaddress ipaddress IPv6Network max_prefixlen8694690
Ref: 2f548694690
Ref: library/ipaddress ipaddress IPv6Network is_multicast8694722
Ref: 2f558694722
Ref: library/ipaddress ipaddress IPv6Network is_private8694753
Ref: 2f568694753
Ref: library/ipaddress ipaddress IPv6Network is_unspecified8694782
Ref: 2f578694782
Ref: library/ipaddress ipaddress IPv6Network is_reserved8694815
Ref: 2f588694815
Ref: library/ipaddress ipaddress IPv6Network is_loopback8694845
Ref: 2f598694845
Ref: library/ipaddress ipaddress IPv6Network is_link_local8694875
Ref: 2f5a8694875
Ref: library/ipaddress ipaddress IPv6Network network_address8694907
Ref: 2f5b8694907
Ref: library/ipaddress ipaddress IPv6Network broadcast_address8694941
Ref: 2f5c8694941
Ref: library/ipaddress ipaddress IPv6Network hostmask8694977
Ref: 2f5d8694977
Ref: library/ipaddress ipaddress IPv6Network netmask8695004
Ref: 2f5e8695004
Ref: library/ipaddress ipaddress IPv6Network with_prefixlen8695030
Ref: 2f5f8695030
Ref: library/ipaddress ipaddress IPv6Network compressed8695063
Ref: 2f608695063
Ref: library/ipaddress ipaddress IPv6Network exploded8695092
Ref: 2f618695092
Ref: library/ipaddress ipaddress IPv6Network with_netmask8695119
Ref: 2f628695119
Ref: library/ipaddress ipaddress IPv6Network with_hostmask8695150
Ref: 2f638695150
Ref: library/ipaddress ipaddress IPv6Network num_addresses8695182
Ref: 2f648695182
Ref: library/ipaddress ipaddress IPv6Network prefixlen8695214
Ref: 2f658695214
Ref: library/ipaddress ipaddress IPv6Network hosts8695242
Ref: 2f668695242
Ref: library/ipaddress ipaddress IPv6Network overlaps8695698
Ref: 2f678695698
Ref: library/ipaddress ipaddress IPv6Network address_exclude8695739
Ref: 2f688695739
Ref: library/ipaddress ipaddress IPv6Network subnets8695789
Ref: 2f698695789
Ref: library/ipaddress ipaddress IPv6Network supernet8695857
Ref: 2f6a8695857
Ref: library/ipaddress ipaddress IPv6Network subnet_of8695926
Ref: 2f6b8695926
Ref: library/ipaddress ipaddress IPv6Network supernet_of8695968
Ref: 2f6c8695968
Ref: library/ipaddress ipaddress IPv6Network compare_networks8696012
Ref: 2f6d8696012
Ref: library/ipaddress ipaddress IPv6Network is_site_local8696160
Ref: 2f6e8696160
Node: Operators<4>8696334
Ref: library/ipaddress id18696429
Ref: 2f6f8696429
Node: Logical operators8696735
Ref: library/ipaddress logical-operators8696822
Ref: 2f708696822
Node: Iteration<2>8697027
Ref: library/ipaddress iteration8697158
Ref: 2f718697158
Node: Networks as containers of addresses8697986
Ref: library/ipaddress networks-as-containers-of-addresses8698091
Ref: 2f728698091
Node: Interface objects8698549
Ref: library/ipaddress interface-objects8698715
Ref: 2f738698715
Ref: library/ipaddress ipaddress IPv4Interface8698864
Ref: 2f108698864
Ref: library/ipaddress ipaddress IPv4Interface ip8699282
Ref: 2f748699282
Ref: library/ipaddress ipaddress IPv4Interface network8699526
Ref: 2f758699526
Ref: library/ipaddress ipaddress IPv4Interface with_prefixlen8699780
Ref: 2f768699780
Ref: library/ipaddress ipaddress IPv4Interface with_netmask8700045
Ref: 2f778700045
Ref: library/ipaddress ipaddress IPv4Interface with_hostmask8700315
Ref: 2f788700315
Ref: library/ipaddress ipaddress IPv6Interface8700584
Ref: 2f118700584
Ref: library/ipaddress ipaddress IPv6Interface ip8701002
Ref: 2f798701002
Ref: library/ipaddress ipaddress IPv6Interface network8701023
Ref: 2f7a8701023
Ref: library/ipaddress ipaddress IPv6Interface with_prefixlen8701049
Ref: 2f7b8701049
Ref: library/ipaddress ipaddress IPv6Interface with_netmask8701082
Ref: 2f7c8701082
Ref: library/ipaddress ipaddress IPv6Interface with_hostmask8701113
Ref: 2f7d8701113
Node: Operators<5>8701284
Ref: library/ipaddress id28701350
Ref: 2f7e8701350
Node: Logical operators<2>8701612
Ref: library/ipaddress id38701681
Ref: 2f7f8701681
Node: Other Module Level Functions8702338
Ref: library/ipaddress other-module-level-functions8702499
Ref: 2f808702499
Ref: library/ipaddress ipaddress v4_int_to_packed8702644
Ref: 2f818702644
Ref: library/ipaddress ipaddress v6_int_to_packed8703116
Ref: 2f828703116
Ref: library/ipaddress ipaddress summarize_address_range8703423
Ref: 79e8703423
Ref: library/ipaddress ipaddress collapse_addresses8704304
Ref: 79f8704304
Ref: library/ipaddress ipaddress get_mixed_type_key8704870
Ref: 2f838704870
Node: Custom Exceptions8705467
Ref: library/ipaddress custom-exceptions8705602
Ref: 2f848705602
Ref: library/ipaddress ipaddress AddressValueError8705773
Ref: 2f148705773
Ref: library/ipaddress ipaddress NetmaskValueError8705873
Ref: 2f398705873
Node: Multimedia Services8705974
Ref: library/mm doc8706126
Ref: 2f858706126
Ref: library/mm mmedia8706126
Ref: 2f868706126
Ref: library/mm multimedia-services8706126
Ref: 2f878706126
Node: audioop --- Manipulate raw audio data8707143
Ref: library/audioop doc8707288
Ref: 2f888707288
Ref: library/audioop audioop-manipulate-raw-audio-data8707288
Ref: 2f898707288
Ref: library/audioop module-audioop8707288
Ref: d8707288
Ref: library/audioop audioop error8708177
Ref: 2f8a8708177
Ref: library/audioop audioop add8708304
Ref: 2f8b8708304
Ref: library/audioop audioop adpcm2lin8708633
Ref: 2f8c8708633
Ref: library/audioop audioop alaw2lin8708950
Ref: 2f8e8708950
Ref: library/audioop audioop avg8709209
Ref: 2f8f8709209
Ref: library/audioop audioop avgpp8709311
Ref: 2f908709311
Ref: library/audioop audioop bias8709515
Ref: 2f918709515
Ref: library/audioop audioop byteswap8709700
Ref: 8278709700
Ref: library/audioop audioop cross8709922
Ref: 2f928709922
Ref: library/audioop audioop findfactor8710053
Ref: 2f938710053
Ref: library/audioop audioop findfit8710462
Ref: 2f948710462
Ref: library/audioop audioop findmax8711070
Ref: 2f958711070
Ref: library/audioop audioop getsample8711425
Ref: 2f968711425
Ref: library/audioop audioop lin2adpcm8711541
Ref: 2f8d8711541
Ref: library/audioop audioop lin2alaw8712278
Ref: 2f978712278
Ref: library/audioop audioop lin2lin8712600
Ref: 2f988712600
Ref: library/audioop audioop lin2ulaw8713228
Ref: 2f998713228
Ref: library/audioop audioop max8713550
Ref: 2f9a8713550
Ref: library/audioop audioop maxpp8713677
Ref: 2f9b8713677
Ref: library/audioop audioop minmax8713786
Ref: 2f9c8713786
Ref: library/audioop audioop mul8713941
Ref: 2f9d8713941
Ref: library/audioop audioop ratecv8714165
Ref: 2f9e8714165
Ref: library/audioop audioop reverse8714741
Ref: 2f9f8714741
Ref: library/audioop audioop rms8714868
Ref: 2fa08714868
Ref: library/audioop audioop tomono8715055
Ref: 2fa18715055
Ref: library/audioop audioop tostereo8715315
Ref: 2fa28715315
Ref: library/audioop audioop ulaw2lin8715628
Ref: 2fa38715628
Node: aifc --- Read and write AIFF and AIFC files8718361
Ref: library/aifc doc8718552
Ref: 2fa48718552
Ref: library/aifc aifc-read-and-write-aiff-and-aifc-files8718552
Ref: 2fa58718552
Ref: library/aifc module-aifc8718552
Ref: 58718552
Ref: library/aifc aifc open8719823
Ref: 4608719823
Ref: library/aifc aifc aifc getnchannels8720866
Ref: 2fa68720866
Ref: library/aifc aifc aifc getsampwidth8720976
Ref: 2fa78720976
Ref: library/aifc aifc aifc getframerate8721070
Ref: 2fa88721070
Ref: library/aifc aifc aifc getnframes8721178
Ref: 2fa98721178
Ref: library/aifc aifc aifc getcomptype8721269
Ref: 2faa8721269
Ref: library/aifc aifc aifc getcompname8721470
Ref: 2fab8721470
Ref: library/aifc aifc aifc getparams8721705
Ref: 8208721705
Ref: library/aifc aifc aifc getmarkers8721913
Ref: 2fac8721913
Ref: library/aifc aifc aifc getmark8722238
Ref: 2fad8722238
Ref: library/aifc aifc aifc readframes8722379
Ref: 2fae8722379
Ref: library/aifc aifc aifc rewind8722602
Ref: 2faf8722602
Ref: library/aifc aifc aifc setpos8722739
Ref: 2fb08722739
Ref: library/aifc aifc aifc tell8722818
Ref: 2fb18722818
Ref: library/aifc aifc aifc close8722889
Ref: 8218722889
Ref: library/aifc aifc aifc aiff8723447
Ref: 2fb28723447
Ref: library/aifc aifc aifc aifc8723657
Ref: 2fb38723657
Ref: library/aifc aifc aifc setnchannels8723869
Ref: 2fb48723869
Ref: library/aifc aifc aifc setsampwidth8723974
Ref: 2fb58723974
Ref: library/aifc aifc aifc setframerate8724069
Ref: 2fb68724069
Ref: library/aifc aifc aifc setnframes8724172
Ref: 2fb78724172
Ref: library/aifc aifc aifc setcomptype8724392
Ref: 2fb88724392
Ref: library/aifc aifc aifc setparams8724885
Ref: 2fb98724885
Ref: library/aifc aifc aifc setmark8725229
Ref: 2fba8725229
Ref: library/aifc aifc aifc writeframes8725595
Ref: 8238725595
Ref: library/aifc aifc aifc writeframesraw8725831
Ref: 8228725831
Ref: aifc --- Read and write AIFF and AIFC files-Footnote-18726297
Node: sunau --- Read and write Sun AU files8726360
Ref: library/sunau doc8726547
Ref: 2fbb8726547
Ref: library/sunau module-sunau8726547
Ref: fb8726547
Ref: library/sunau sunau-read-and-write-sun-au-files8726547
Ref: 2fbc8726547
Ref: library/sunau sunau open8728093
Ref: 4778728093
Ref: library/sunau sunau openfp8728546
Ref: 4768728546
Ref: library/sunau sunau Error8728799
Ref: 2fbd8728799
Ref: library/sunau sunau AUDIO_FILE_MAGIC8728997
Ref: 2fbe8728997
Ref: library/sunau sunau AUDIO_FILE_ENCODING_MULAW_88729180
Ref: 2fbf8729180
Ref: library/sunau sunau AUDIO_FILE_ENCODING_LINEAR_88729224
Ref: 2fc08729224
Ref: library/sunau sunau AUDIO_FILE_ENCODING_LINEAR_168729269
Ref: 2fc18729269
Ref: library/sunau sunau AUDIO_FILE_ENCODING_LINEAR_248729315
Ref: 2fc28729315
Ref: library/sunau sunau AUDIO_FILE_ENCODING_LINEAR_328729361
Ref: 2fc38729361
Ref: library/sunau sunau AUDIO_FILE_ENCODING_ALAW_88729407
Ref: 2fc48729407
Ref: library/sunau sunau AUDIO_FILE_ENCODING_FLOAT8729546
Ref: 2fc58729546
Ref: library/sunau sunau AUDIO_FILE_ENCODING_DOUBLE8729588
Ref: 2fc68729588
Ref: library/sunau sunau AUDIO_FILE_ENCODING_ADPCM_G7218729631
Ref: 2fc78729631
Ref: library/sunau sunau AUDIO_FILE_ENCODING_ADPCM_G7228729678
Ref: 2fc88729678
Ref: library/sunau sunau AUDIO_FILE_ENCODING_ADPCM_G723_38729725
Ref: 2fc98729725
Ref: library/sunau sunau AUDIO_FILE_ENCODING_ADPCM_G723_58729774
Ref: 2fca8729774
Ref: sunau --- Read and write Sun AU files-Footnote-18730032
Node: AU_read Objects8730096
Ref: library/sunau au-read-objects8730210
Ref: 2fcb8730210
Ref: library/sunau id18730210
Ref: 2fcc8730210
Ref: library/sunau sunau AU_read close8730348
Ref: 2fcd8730348
Ref: library/sunau sunau AU_read getnchannels8730490
Ref: 2fce8730490
Ref: library/sunau sunau AU_read getsampwidth8730600
Ref: 2fcf8730600
Ref: library/sunau sunau AU_read getframerate8730680
Ref: 2fd08730680
Ref: library/sunau sunau AU_read getnframes8730757
Ref: 2fd18730757
Ref: library/sunau sunau AU_read getcomptype8730836
Ref: 2fd28730836
Ref: library/sunau sunau AU_read getcompname8730993
Ref: 2fd38730993
Ref: library/sunau sunau AU_read getparams8731232
Ref: 2fd48731232
Ref: library/sunau sunau AU_read readframes8731443
Ref: 2fd58731443
Ref: library/sunau sunau AU_read rewind8731688
Ref: 2fd68731688
Ref: library/sunau sunau AU_read setpos8731922
Ref: 2fd78731922
Ref: library/sunau sunau AU_read tell8732094
Ref: 2fd88732094
Ref: library/sunau sunau AU_read getmarkers8732384
Ref: 2fd98732384
Ref: library/sunau sunau AU_read getmark8732451
Ref: 2fda8732451
Node: AU_write Objects8732513
Ref: library/sunau au-write-objects8732627
Ref: 2fdb8732627
Ref: library/sunau id28732627
Ref: 2fdc8732627
Ref: library/sunau sunau AU_write setnchannels8732768
Ref: 2fdd8732768
Ref: library/sunau sunau AU_write setsampwidth8732847
Ref: 8e38732847
Ref: library/sunau sunau AU_write setframerate8732986
Ref: 2fde8732986
Ref: library/sunau sunau AU_write setnframes8733057
Ref: 2fdf8733057
Ref: library/sunau sunau AU_write setcomptype8733202
Ref: 2fe08733202
Ref: library/sunau sunau AU_write setparams8733369
Ref: 2fe18733369
Ref: library/sunau sunau AU_write tell8733591
Ref: 2fe28733591
Ref: library/sunau sunau AU_write writeframesraw8733784
Ref: 8e48733784
Ref: library/sunau sunau AU_write writeframes8733962
Ref: 8e58733962
Ref: library/sunau sunau AU_write close8734142
Ref: 2fe38734142
Node: wave --- Read and write WAV files8734388
Ref: library/wave doc8734563
Ref: 2fe48734563
Ref: library/wave module-wave8734563
Ref: 1288734563
Ref: library/wave wave-read-and-write-wav-files8734563
Ref: 2fe58734563
Ref: library/wave wave open8734993
Ref: 47b8734993
Ref: library/wave wave openfp8736033
Ref: 47a8736033
Ref: library/wave wave Error8736223
Ref: 2fe88736223
Ref: wave --- Read and write WAV files-Footnote-18736474
Node: Wave_read Objects8736537
Ref: library/wave id18736651
Ref: 2fe98736651
Ref: library/wave wave-read-objects8736651
Ref: 2fea8736651
Ref: library/wave wave Wave_read close8736788
Ref: 2fe68736788
Ref: library/wave wave Wave_read getnchannels8736980
Ref: 2feb8736980
Ref: library/wave wave Wave_read getsampwidth8737104
Ref: 2fec8737104
Ref: library/wave wave Wave_read getframerate8737186
Ref: 2fed8737186
Ref: library/wave wave Wave_read getnframes8737265
Ref: 2fee8737265
Ref: library/wave wave Wave_read getcomptype8737346
Ref: 2fef8737346
Ref: library/wave wave Wave_read getcompname8737464
Ref: 2ff08737464
Ref: library/wave wave Wave_read getparams8737628
Ref: 2ff18737628
Ref: library/wave wave Wave_read readframes8737841
Ref: 2ff28737841
Ref: library/wave wave Wave_read rewind8737974
Ref: 2ff38737974
Ref: library/wave wave Wave_read getmarkers8738207
Ref: 2ff48738207
Ref: library/wave wave Wave_read getmark8738276
Ref: 2ff58738276
Ref: library/wave wave Wave_read setpos8738469
Ref: 2ff68738469
Ref: library/wave wave Wave_read tell8738565
Ref: 2ff78738565
Node: Wave_write Objects8738646
Ref: library/wave id28738760
Ref: 2ff88738760
Ref: library/wave wave-write-objects8738760
Ref: 9108738760
Ref: library/wave wave Wave_write close8739692
Ref: 2fe78739692
Ref: library/wave wave Wave_write setnchannels8740019
Ref: 2ffb8740019
Ref: library/wave wave Wave_write setsampwidth8740100
Ref: 2ffc8740100
Ref: library/wave wave Wave_write setframerate8740188
Ref: 2ffd8740188
Ref: library/wave wave Wave_write setnframes8740365
Ref: 2ff98740365
Ref: library/wave wave Wave_write setcomptype8740621
Ref: 2ffe8740621
Ref: library/wave wave Wave_write setparams8740816
Ref: 2ffa8740816
Ref: library/wave wave Wave_write tell8741041
Ref: 2fff8741041
Ref: library/wave wave Wave_write writeframesraw8741240
Ref: 9118741240
Ref: library/wave wave Wave_write writeframes8741420
Ref: 9128741420
Node: chunk --- Read IFF chunked data8741985
Ref: library/chunk doc8742169
Ref: 30008742169
Ref: library/chunk chunk-read-iff-chunked-data8742169
Ref: 30018742169
Ref: library/chunk module-chunk8742169
Ref: 188742169
Ref: library/chunk chunk Chunk8743999
Ref: 30028743999
Ref: library/chunk chunk Chunk getname8745132
Ref: 30038745132
Ref: library/chunk chunk Chunk getsize8745265
Ref: 30048745265
Ref: library/chunk chunk Chunk close8745342
Ref: 30058745342
Ref: library/chunk chunk Chunk isatty8745712
Ref: 30068745712
Ref: library/chunk chunk Chunk seek8745778
Ref: 30078745778
Ref: library/chunk chunk Chunk tell8746226
Ref: 30088746226
Ref: library/chunk chunk Chunk read8746313
Ref: 30098746313
Ref: library/chunk chunk Chunk skip8746699
Ref: 300a8746699
Ref: chunk --- Read IFF chunked data-Footnote-18747072
Ref: chunk --- Read IFF chunked data-Footnote-28747136
Node: colorsys --- Conversions between color systems8747246
Ref: library/colorsys doc8747438
Ref: 300b8747438
Ref: library/colorsys colorsys-conversions-between-color-systems8747438
Ref: 300c8747438
Ref: library/colorsys module-colorsys8747438
Ref: 208747438
Ref: library/colorsys colorsys rgb_to_yiq8748423
Ref: 300d8748423
Ref: library/colorsys colorsys yiq_to_rgb8748531
Ref: 300e8748531
Ref: library/colorsys colorsys rgb_to_hls8748639
Ref: 300f8748639
Ref: library/colorsys colorsys hls_to_rgb8748747
Ref: 30108748747
Ref: library/colorsys colorsys rgb_to_hsv8748855
Ref: 30118748855
Ref: library/colorsys colorsys hsv_to_rgb8748963
Ref: 30128748963
Ref: colorsys --- Conversions between color systems-Footnote-18749273
Node: imghdr --- Determine the type of an image8749340
Ref: library/imghdr doc8749540
Ref: 30138749540
Ref: library/imghdr imghdr-determine-the-type-of-an-image8749540
Ref: 30148749540
Ref: library/imghdr module-imghdr8749540
Ref: 998749540
Ref: library/imghdr imghdr what8749903
Ref: 6f28749903
Ref: library/imghdr imghdr tests8751611
Ref: 30158751611
Ref: imghdr --- Determine the type of an image-Footnote-18752129
Node: sndhdr --- Determine type of sound file8752194
Ref: library/sndhdr doc8752402
Ref: 30168752402
Ref: library/sndhdr module-sndhdr8752402
Ref: ef8752402
Ref: library/sndhdr sndhdr-determine-type-of-sound-file8752402
Ref: 30178752402
Ref: library/sndhdr sndhdr what8753646
Ref: 74c8753646
Ref: library/sndhdr sndhdr whathdr8753948
Ref: 74d8753948
Ref: sndhdr --- Determine type of sound file-Footnote-18754315
Node: ossaudiodev --- Access to OSS-compatible audio devices8754380
Ref: library/ossaudiodev doc8754538
Ref: 30188754538
Ref: library/ossaudiodev module-ossaudiodev8754538
Ref: c78754538
Ref: library/ossaudiodev ossaudiodev-access-to-oss-compatible-audio-devices8754538
Ref: 30198754538
Ref: library/ossaudiodev ossaudiodev OSSAudioError8755413
Ref: 301a8755413
Ref: library/ossaudiodev ossaudiodev open8755929
Ref: 301b8755929
Ref: library/ossaudiodev ossaudiodev openmixer8757324
Ref: 301c8757324
Ref: ossaudiodev --- Access to OSS-compatible audio devices-Footnote-18757760
Node: Audio Device Objects8757808
Ref: library/ossaudiodev audio-device-objects8757948
Ref: 301d8757948
Ref: library/ossaudiodev ossaudio-device-objects8757948
Ref: 301e8757948
Ref: library/ossaudiodev ossaudiodev oss_audio_device close8758540
Ref: 301f8758540
Ref: library/ossaudiodev ossaudiodev oss_audio_device fileno8758770
Ref: 30208758770
Ref: library/ossaudiodev ossaudiodev oss_audio_device read8758877
Ref: 30218758877
Ref: library/ossaudiodev ossaudiodev oss_audio_device write8759191
Ref: 30228759191
Ref: library/ossaudiodev ossaudiodev oss_audio_device writeall8759703
Ref: 30238759703
Ref: library/ossaudiodev ossaudiodev oss_audio_device nonblock8760848
Ref: 30248760848
Ref: library/ossaudiodev ossaudiodev oss_audio_device getfmts8761021
Ref: 30258761021
Ref: library/ossaudiodev ossaudiodev oss_audio_device setfmt8763192
Ref: 30268763192
Ref: library/ossaudiodev ossaudiodev oss_audio_device channels8763565
Ref: 30278763565
Ref: library/ossaudiodev ossaudiodev oss_audio_device speed8763899
Ref: 30288763899
Ref: library/ossaudiodev ossaudiodev oss_audio_device sync8764645
Ref: 30298764645
Ref: library/ossaudiodev ossaudiodev oss_audio_device reset8764934
Ref: 302a8764934
Ref: library/ossaudiodev ossaudiodev oss_audio_device post8765204
Ref: 302b8765204
Ref: library/ossaudiodev ossaudiodev oss_audio_device setparameters8765623
Ref: 302c8765623
Ref: library/ossaudiodev ossaudiodev oss_audio_device bufsize8766692
Ref: 302d8766692
Ref: library/ossaudiodev ossaudiodev oss_audio_device obufcount8766798
Ref: 302e8766798
Ref: library/ossaudiodev ossaudiodev oss_audio_device obuffree8766938
Ref: 302f8766938
Ref: library/ossaudiodev ossaudiodev oss_audio_device closed8767169
Ref: 30308767169
Ref: library/ossaudiodev ossaudiodev oss_audio_device name8767267
Ref: 30318767267
Ref: library/ossaudiodev ossaudiodev oss_audio_device mode8767355
Ref: 30328767355
Node: Mixer Device Objects8767467
Ref: library/ossaudiodev id18767607
Ref: 30338767607
Ref: library/ossaudiodev mixer-device-objects8767607
Ref: 30348767607
Ref: library/ossaudiodev ossaudiodev oss_mixer_device close8767718
Ref: 30358767718
Ref: library/ossaudiodev ossaudiodev oss_mixer_device fileno8767925
Ref: 30368767925
Ref: library/ossaudiodev ossaudiodev oss_mixer_device controls8768168
Ref: 30378768168
Ref: library/ossaudiodev ossaudiodev oss_mixer_device stereocontrols8769144
Ref: 30388769144
Ref: library/ossaudiodev ossaudiodev oss_mixer_device reccontrols8769595
Ref: 30398769595
Ref: library/ossaudiodev ossaudiodev oss_mixer_device get8769830
Ref: 303a8769830
Ref: library/ossaudiodev ossaudiodev oss_mixer_device set8770331
Ref: 303b8770331
Ref: library/ossaudiodev ossaudiodev oss_mixer_device get_recsrc8770900
Ref: 303c8770900
Ref: library/ossaudiodev ossaudiodev oss_mixer_device set_recsrc8771067
Ref: 303d8771067
Node: 國際化8771470
Ref: library/i18n doc8771604
Ref: 303e8771604
Ref: library/i18n i18n8771604
Ref: 303f8771604
Ref: library/i18n internationalization8771604
Ref: 30408771604
Node: gettext --- Multilingual internationalization services8772122
Ref: library/gettext doc8772271
Ref: 30418772271
Ref: library/gettext gettext-multilingual-internationalization-services8772271
Ref: 30428772271
Ref: library/gettext module-gettext8772271
Ref: 898772271
Ref: gettext --- Multilingual internationalization services-Footnote-18773248
Node: GNU gettext API8773314
Ref: library/gettext gnu-gettext-api8773444
Ref: 30438773444
Ref: library/gettext gettext bindtextdomain8773988
Ref: 30448773988
Ref: library/gettext gettext bind_textdomain_codeset8774558
Ref: 2988774558
Ref: library/gettext gettext textdomain8774982
Ref: 30468774982
Ref: library/gettext gettext gettext8775226
Ref: dd28775226
Ref: library/gettext gettext dgettext8775493
Ref: 30478775493
Ref: library/gettext gettext ngettext8775630
Ref: 30488775630
Ref: library/gettext gettext dngettext8776338
Ref: 30498776338
Ref: library/gettext gettext pgettext8776490
Ref: 1d08776490
Ref: library/gettext gettext dpgettext8776539
Ref: 304a8776539
Ref: library/gettext gettext npgettext8776597
Ref: 304b8776597
Ref: library/gettext gettext dnpgettext8776659
Ref: 304c8776659
Ref: library/gettext gettext lgettext8777020
Ref: 2948777020
Ref: library/gettext gettext ldgettext8777060
Ref: 2958777060
Ref: library/gettext gettext lngettext8777109
Ref: 2968777109
Ref: library/gettext gettext ldngettext8777162
Ref: 2978777162
Ref: GNU gettext API-Footnote-18778604
Ref: GNU gettext API-Footnote-28779092
Node: Class-based API8779157
Ref: library/gettext class-based-api8779340
Ref: 304d8779340
Ref: library/gettext gettext find8779870
Ref: 304f8779870
Ref: library/gettext gettext translation8781316
Ref: 29b8781316
Ref: library/gettext gettext install8782741
Ref: 29c8782741
Ref: Class-based API-Footnote-18783834
Node: The NullTranslations class8783904
Ref: library/gettext the-nulltranslations-class8784016
Ref: 30548784016
Ref: library/gettext gettext NullTranslations8784461
Ref: 30528784461
Ref: library/gettext gettext NullTranslations _parse8784857
Ref: 30568784857
Ref: library/gettext gettext NullTranslations add_fallback8785174
Ref: 30558785174
Ref: library/gettext gettext NullTranslations gettext8785443
Ref: 30578785443
Ref: library/gettext gettext NullTranslations ngettext8785647
Ref: 30588785647
Ref: library/gettext gettext NullTranslations pgettext8785905
Ref: 30598785905
Ref: library/gettext gettext NullTranslations npgettext8786167
Ref: 305a8786167
Ref: library/gettext gettext NullTranslations lgettext8786444
Ref: 30508786444
Ref: library/gettext gettext NullTranslations lngettext8786487
Ref: 30518786487
Ref: library/gettext gettext NullTranslations info8787069
Ref: 305b8787069
Ref: library/gettext gettext NullTranslations charset8787239
Ref: 305c8787239
Ref: library/gettext gettext NullTranslations output_charset8787334
Ref: 2998787334
Ref: library/gettext gettext NullTranslations set_output_charset8787582
Ref: 29a8787582
Ref: library/gettext gettext NullTranslations install8787776
Ref: 30538787776
Node: The GNUTranslations class8789012
Ref: library/gettext the-gnutranslations-class8789164
Ref: 305d8789164
Ref: library/gettext gettext GNUTranslations8790666
Ref: 304e8790666
Ref: library/gettext gettext GNUTranslations gettext8790787
Ref: 305e8790787
Ref: library/gettext gettext GNUTranslations ngettext8791202
Ref: 305f8791202
Ref: library/gettext gettext GNUTranslations pgettext8792132
Ref: 30608792132
Ref: library/gettext gettext GNUTranslations npgettext8792612
Ref: 30618792612
Ref: library/gettext gettext GNUTranslations lgettext8793227
Ref: 30628793227
Ref: library/gettext gettext GNUTranslations lngettext8793270
Ref: 30638793270
Ref: The GNUTranslations class-Footnote-18793846
Node: Solaris message catalog support8793894
Ref: library/gettext solaris-message-catalog-support8794043
Ref: 30648794043
Node: The Catalog constructor8794292
Ref: library/gettext the-catalog-constructor8794407
Ref: 30658794407
Node: Internationalizing your programs and modules8795065
Ref: library/gettext internationalizing-your-programs-and-modules8795252
Ref: 30668795252
Ref: Internationalizing your programs and modules-Footnote-18798830
Ref: Internationalizing your programs and modules-Footnote-28798862
Node: Localizing your module8798905
Ref: library/gettext localizing-your-module8799044
Ref: 30678799044
Node: Localizing your application8799635
Ref: library/gettext localizing-your-application8799812
Ref: 30688799812
Node: Changing languages on the fly8800540
Ref: library/gettext changing-languages-on-the-fly8800716
Ref: 30698800716
Node: Deferred translations8801395
Ref: library/gettext deferred-translations8801535
Ref: 306a8801535
Node: Acknowledgements<9>8803771
Ref: library/gettext acknowledgements8803934
Ref: 306b8803934
Node: locale --- Internationalization services8804343
Ref: library/locale doc8804492
Ref: 306c8804492
Ref: library/locale locale-internationalization-services8804492
Ref: 306d8804492
Ref: library/locale module-locale8804492
Ref: aa8804492
Ref: library/locale locale Error8805220
Ref: 306e8805220
Ref: library/locale locale setlocale8805344
Ref: 200f8805344
Ref: library/locale locale localeconv8806529
Ref: 48f8806529
Ref: library/locale locale nl_langinfo8814819
Ref: 30728814819
Ref: library/locale locale CODESET8815338
Ref: 30738815338
Ref: library/locale locale D_T_FMT8815472
Ref: 30748815472
Ref: library/locale locale D_FMT8815668
Ref: 30758815668
Ref: library/locale locale T_FMT8815855
Ref: 30768815855
Ref: library/locale locale T_FMT_AMPM8816042
Ref: 30778816042
Ref: library/locale locale RADIXCHAR8816742
Ref: 30788816742
Ref: library/locale locale THOUSEP8816846
Ref: 30798816846
Ref: library/locale locale YESEXPR8816966
Ref: 307a8816966
Ref: library/locale locale NOEXPR8817352
Ref: 307b8817352
Ref: library/locale locale CRNCYSTR8817537
Ref: 307c8817537
Ref: library/locale locale ERA8817804
Ref: 307d8817804
Ref: library/locale locale ERA_D_T_FMT8818578
Ref: 307e8818578
Ref: library/locale locale ERA_D_FMT8818749
Ref: 307f8818749
Ref: library/locale locale ERA_T_FMT8818911
Ref: 30808818911
Ref: library/locale locale ALT_DIGITS8819073
Ref: 30818819073
Ref: library/locale locale getdefaultlocale8819207
Ref: 13658819207
Ref: library/locale locale getlocale8820412
Ref: 18f98820412
Ref: library/locale locale getpreferredencoding8820887
Ref: 3aa8820887
Ref: library/locale locale normalize8821744
Ref: 30848821744
Ref: library/locale locale resetlocale8822164
Ref: 30858822164
Ref: library/locale locale strcoll8822412
Ref: 30868822412
Ref: library/locale locale strxfrm8822729
Ref: 30888822729
Ref: library/locale locale format_string8823071
Ref: 3a98823071
Ref: library/locale locale format8823756
Ref: 46d8823756
Ref: library/locale locale currency8824206
Ref: 30898824206
Ref: library/locale locale str8824834
Ref: 308a8824834
Ref: library/locale locale delocalize8825021
Ref: 7108825021
Ref: library/locale locale atof8825195
Ref: 308b8825195
Ref: library/locale locale atoi8825334
Ref: 308c8825334
Ref: library/locale locale LC_CTYPE8825463
Ref: 30838825463
Ref: library/locale locale LC_COLLATE8825685
Ref: 30878825685
Ref: library/locale locale LC_TIME8825878
Ref: 308d8825878
Ref: library/locale locale LC_MONETARY8826028
Ref: 30718826028
Ref: library/locale locale LC_MESSAGES8826201
Ref: 308e8826201
Ref: library/locale locale LC_NUMERIC8826499
Ref: 306f8826499
Ref: library/locale locale LC_ALL8826815
Ref: 30828826815
Ref: library/locale locale CHAR_MAX8827240
Ref: 30708827240
Ref: locale --- Internationalization services-Footnote-18828091
Ref: locale --- Internationalization services-Footnote-28828156
Ref: locale --- Internationalization services-Footnote-38828205
Node: Background details hints tips and caveats8828254
Ref: library/locale background-details-hints-tips-and-caveats8828433
Ref: 308f8828433
Node: For extension writers and programs that embed Python8830631
Ref: library/locale embedding-locale8830845
Ref: 30908830845
Ref: library/locale for-extension-writers-and-programs-that-embed-python8830845
Ref: 30918830845
Node: Access to message catalogs8831643
Ref: library/locale access-to-message-catalogs8831807
Ref: 30928831807
Ref: library/locale locale-gettext8831807
Ref: 30938831807
Ref: library/locale locale gettext8831880
Ref: 30948831880
Ref: library/locale locale dgettext8831914
Ref: 30958831914
Ref: library/locale locale dcgettext8831957
Ref: 30968831957
Ref: library/locale locale textdomain8832011
Ref: 30978832011
Ref: library/locale locale bindtextdomain8832051
Ref: 30988832051
Node: 程式框架8832981
Ref: library/frameworks doc8833113
Ref: 30998833113
Ref: library/frameworks frameworks8833113
Ref: 309a8833113
Ref: library/frameworks program-frameworks8833113
Ref: 309b8833113
Node: turtle --- 龜圖學8833638
Ref: library/turtle doc8833770
Ref: 309c8833770
Ref: library/turtle module-turtle8833770
Ref: 1178833770
Ref: library/turtle turtle-turtle-graphics8833770
Ref: 309d8833770
Ref: turtle --- 龜圖學-Footnote-18834373
Node: 介紹8834438
Ref: library/turtle introduction8834557
Ref: 309e8834557
Node: Overview of available Turtle and Screen methods8838256
Ref: library/turtle overview-of-available-turtle-and-screen-methods8838439
Ref: 30a58838439
Node: Turtle methods8838618
Ref: library/turtle turtle-methods8838755
Ref: 30a68838755
Node: Methods of TurtleScreen/Screen8841833
Ref: library/turtle methods-of-turtlescreen-screen8841970
Ref: 30f68841970
Node: Methods of RawTurtle/Turtle and corresponding functions8843363
Ref: library/turtle methods-of-rawturtle-turtle-and-corresponding-functions8843598
Ref: 31158843598
Node: Turtle motion8843993
Ref: library/turtle turtle-motion8844126
Ref: 31168844126
Ref: library/turtle turtle forward8844173
Ref: 30a78844173
Ref: library/turtle turtle fd8844211
Ref: 30a88844211
Ref: library/turtle turtle back8844643
Ref: 30ab8844643
Ref: library/turtle turtle bk8844678
Ref: 30aa8844678
Ref: library/turtle turtle backward8844711
Ref: 30a98844711
Ref: library/turtle turtle right8845077
Ref: 30ac8845077
Ref: library/turtle turtle rt8845110
Ref: 30ad8845110
Ref: library/turtle turtle left8845570
Ref: 30ae8845570
Ref: library/turtle turtle lt8845602
Ref: 30af8845602
Ref: library/turtle turtle goto8846059
Ref: 30b08846059
Ref: library/turtle turtle setpos8846095
Ref: 30b18846095
Ref: library/turtle turtle setposition8846133
Ref: 30b28846133
Ref: library/turtle turtle setx8846894
Ref: 30b38846894
Ref: library/turtle turtle sety8847212
Ref: 30b48847212
Ref: library/turtle turtle setheading8847529
Ref: 30b58847529
Ref: library/turtle turtle seth8847570
Ref: 30b68847570
Ref: library/turtle turtle home8848380
Ref: 30b78848380
Ref: library/turtle turtle circle8848805
Ref: 30b88848805
Ref: library/turtle turtle dot8850184
Ref: 30b98850184
Ref: library/turtle turtle stamp8850728
Ref: 30ba8850728
Ref: library/turtle turtle clearstamp8851065
Ref: 30bb8851065
Ref: library/turtle turtle clearstamps8851569
Ref: 30bc8851569
Ref: library/turtle turtle undo8852143
Ref: 30bd8852143
Ref: library/turtle turtle speed8852466
Ref: 30be8852466
Node: Tell Turtle's state8853439
Ref: library/turtle tell-turtle-s-state8853605
Ref: 31188853605
Ref: library/turtle turtle position8853666
Ref: 30bf8853666
Ref: library/turtle turtle pos8853697
Ref: 30c08853697
Ref: library/turtle turtle towards8853867
Ref: 30c18853867
Ref: library/turtle turtle xcor8854414
Ref: 30c28854414
Ref: library/turtle turtle ycor8854692
Ref: 30c38854692
Ref: library/turtle turtle heading8854977
Ref: 30c48854977
Ref: library/turtle turtle distance8855223
Ref: 30c58855223
Node: Settings for measurement8855806
Ref: library/turtle settings-for-measurement8855970
Ref: 31198855970
Ref: library/turtle turtle degrees8856039
Ref: 30c68856039
Ref: library/turtle turtle radians8856657
Ref: 30c78856657
Node: Pen control8856980
Ref: library/turtle pen-control8857137
Ref: 311a8857137
Node: Drawing state8857263
Ref: library/turtle drawing-state8857346
Ref: 311b8857346
Ref: library/turtle turtle pendown8857395
Ref: 30c88857395
Ref: library/turtle turtle pd8857425
Ref: 30c98857425
Ref: library/turtle turtle down8857450
Ref: 30ca8857450
Ref: library/turtle turtle penup8857527
Ref: 30cb8857527
Ref: library/turtle turtle pu8857555
Ref: 30cc8857555
Ref: library/turtle turtle up8857580
Ref: 30cd8857580
Ref: library/turtle turtle pensize8857656
Ref: 30ce8857656
Ref: library/turtle turtle width8857696
Ref: 30cf8857696
Ref: library/turtle turtle pen8858148
Ref: 30d08858148
Ref: library/turtle turtle isdown8859996
Ref: 30d18859996
Node: Color control8860244
Ref: library/turtle color-control8860343
Ref: 311c8860343
Ref: library/turtle turtle pencolor8860392
Ref: 30d38860392
Ref: library/turtle turtle fillcolor8862011
Ref: 30d48862011
Ref: library/turtle turtle color8863528
Ref: 30d28863528
Node: Filling8864730
Ref: library/turtle filling8864836
Ref: 311d8864836
Ref: library/turtle turtle filling8864873
Ref: 30d58864873
Ref: library/turtle turtle begin_fill8865135
Ref: 30d68865135
Ref: library/turtle turtle end_fill8865230
Ref: 30d78865230
Node: More drawing control8865775
Ref: library/turtle more-drawing-control8865859
Ref: 311e8865859
Ref: library/turtle turtle write8866570
Ref: 30da8866570
Node: Turtle state8867321
Ref: library/turtle turtle-state8867466
Ref: 311f8867466
Node: Visibility8867553
Ref: library/turtle visibility8867631
Ref: 31208867631
Ref: library/turtle turtle hideturtle8867674
Ref: 30dd8867674
Ref: library/turtle turtle ht8867707
Ref: 30de8867707
Ref: library/turtle turtle showturtle8867962
Ref: 30db8867962
Ref: library/turtle turtle st8867995
Ref: 30dc8867995
Ref: library/turtle turtle isvisible8868087
Ref: 30df8868087
Node: Appearance8868364
Ref: library/turtle appearance8868442
Ref: 31218868442
Ref: library/turtle turtle shape8868485
Ref: 30e08868485
Ref: library/turtle turtle resizemode8869128
Ref: 30e18869128
Ref: library/turtle turtle shapesize8870057
Ref: 30e28870057
Ref: library/turtle turtle turtlesize8870147
Ref: 30e38870147
Ref: library/turtle turtle shearfactor8871124
Ref: 30e48871124
Ref: library/turtle turtle tilt8871787
Ref: 30e78871787
Ref: library/turtle turtle settiltangle8872221
Ref: 30e58872221
Ref: library/turtle turtle tiltangle8872755
Ref: 30e68872755
Ref: library/turtle turtle shapetransform8873471
Ref: 30e88873471
Ref: library/turtle turtle get_shapepoly8874487
Ref: 30e98874487
Node: Using events8874856
Ref: library/turtle using-events8875012
Ref: 31228875012
Ref: library/turtle turtle onrelease8875906
Ref: 30eb8875906
Ref: library/turtle turtle ondrag8876911
Ref: 30ec8876911
Node: Special Turtle methods8877780
Ref: library/turtle special-turtle-methods8877939
Ref: 31238877939
Ref: library/turtle turtle begin_poly8878006
Ref: 30ed8878006
Ref: library/turtle turtle end_poly8878147
Ref: 30ee8878147
Ref: library/turtle turtle get_poly8878336
Ref: 30ef8878336
Ref: library/turtle turtle clone8878736
Ref: 30f08878736
Ref: library/turtle turtle getturtle8878931
Ref: 30f18878931
Ref: library/turtle turtle getpen8878963
Ref: 30f28878963
Ref: library/turtle turtle getscreen8879225
Ref: 30f38879225
Ref: library/turtle turtle setundobuffer8879529
Ref: 30f48879529
Ref: library/turtle turtle undobufferentries8879960
Ref: 30f58879960
Node: Compound shapes8880118
Ref: library/turtle compound-shapes8880256
Ref: 31248880256
Ref: library/turtle compoundshapes8880256
Ref: 31258880256
Node: Methods of TurtleScreen/Screen and corresponding functions8881281
Ref: library/turtle methods-of-turtlescreen-screen-and-corresponding-functions8881483
Ref: 31278881483
Node: Window control8881963
Ref: library/turtle window-control8882098
Ref: 31288882098
Ref: library/turtle turtle bgcolor8882149
Ref: 30f78882149
Ref: library/turtle turtle bgpic8882556
Ref: 30f88882556
Ref: library/turtle turtle clear8883154
Ref: 30d98883154
Ref: library/turtle turtle clearscreen8883182
Ref: 30f98883182
Ref: library/turtle turtle reset8883664
Ref: 30d88883664
Ref: library/turtle turtle resetscreen8883692
Ref: 30fa8883692
Ref: library/turtle turtle screensize8884028
Ref: 30fb8884028
Ref: library/turtle turtle setworldcoordinates8884921
Ref: 30fc8884921
Node: Animation control8885889
Ref: library/turtle animation-control8886052
Ref: 31298886052
Ref: library/turtle turtle delay8886109
Ref: 30fd8886109
Ref: library/turtle turtle tracer8886542
Ref: 30fe8886542
Ref: library/turtle turtle update8887237
Ref: 30ff8887237
Node: Using screen events8887407
Ref: library/turtle using-screen-events8887569
Ref: 312a8887569
Ref: library/turtle turtle listen8887630
Ref: 31008887630
Ref: library/turtle turtle onkey8887863
Ref: 31018887863
Ref: library/turtle turtle onkeyrelease8887899
Ref: 31028887899
Ref: library/turtle turtle onkeypress8888507
Ref: 31038888507
Ref: library/turtle turtle onclick8889096
Ref: 30ea8889096
Ref: library/turtle turtle onscreenclick8889146
Ref: 31048889146
Ref: library/turtle turtle ontimer8890330
Ref: 31058890330
Ref: library/turtle turtle mainloop8890808
Ref: 31068890808
Ref: library/turtle turtle done8890839
Ref: 31078890839
Node: Input methods8891163
Ref: library/turtle input-methods8891336
Ref: 312b8891336
Ref: library/turtle turtle textinput8891385
Ref: e9b8891385
Ref: library/turtle turtle numinput8891833
Ref: e9c8891833
Node: Settings and special methods8892747
Ref: library/turtle settings-and-special-methods8892959
Ref: 312c8892959
Ref: library/turtle turtle mode8893038
Ref: 31088893038
Ref: library/turtle turtle colormode8894208
Ref: 31098894208
Ref: library/turtle turtle getcanvas8894842
Ref: 310a8894842
Ref: library/turtle turtle getshapes8895091
Ref: 310b8895091
Ref: library/turtle turtle register_shape8895283
Ref: 310c8895283
Ref: library/turtle turtle addshape8895336
Ref: 310d8895336
Ref: library/turtle turtle turtles8896285
Ref: 310e8896285
Ref: library/turtle turtle window_height8896449
Ref: 310f8896449
Ref: library/turtle turtle window_width8896584
Ref: 31108896584
Node: Methods specific to Screen not inherited from TurtleScreen8896716
Ref: library/turtle methods-specific-to-screen-not-inherited-from-turtlescreen8896906
Ref: 312d8896906
Ref: library/turtle screenspecific8896906
Ref: 312e8896906
Ref: library/turtle turtle bye8897047
Ref: 31118897047
Ref: library/turtle turtle exitonclick8897112
Ref: 31128897112
Ref: library/turtle turtle setup8897546
Ref: 31138897546
Ref: library/turtle turtle title8898860
Ref: 31148898860
Node: Public classes8899120
Ref: library/turtle public-classes8899289
Ref: 312f8899289
Ref: library/turtle turtle RawTurtle8899340
Ref: 30a28899340
Ref: library/turtle turtle RawPen8899378
Ref: 30a38899378
Ref: library/turtle turtle Turtle8899642
Ref: 30a48899642
Ref: library/turtle turtle TurtleScreen8899835
Ref: 309f8899835
Ref: library/turtle turtle Screen8900019
Ref: 30a18900019
Ref: library/turtle turtle ScrolledCanvas8900115
Ref: 30a08900115
Ref: library/turtle turtle Shape8900407
Ref: 31268900407
Ref: library/turtle turtle Shape addcomponent8901183
Ref: 31308901183
Ref: library/turtle turtle Vec2D8901785
Ref: 31178901785
Node: Help and configuration8902338
Ref: library/turtle help-and-configuration8902476
Ref: 31318902476
Node: How to use help8902668
Ref: library/turtle how-to-use-help8902801
Ref: 31328902801
Node: Translation of docstrings into different languages8905131
Ref: library/turtle translation-of-docstrings-into-different-languages8905308
Ref: 31338905308
Ref: library/turtle turtle write_docstringdict8905612
Ref: 31348905612
Node: How to configure Screen and Turtles8906635
Ref: library/turtle how-to-configure-screen-and-turtles8906788
Ref: 31358906788
Node: turtledemo --- Demo scripts8909567
Ref: library/turtle module-turtledemo8909715
Ref: 1188909715
Ref: library/turtle turtledemo-demo-scripts8909715
Ref: 31368909715
Node: Changes since Python 2 68915360
Ref: library/turtle changes-since-python-2-68915510
Ref: 31378915510
Node: Changes since Python 3 08916485
Ref: library/turtle changes-since-python-3-08916599
Ref: 31388916599
Node: cmd --- Support for line-oriented command interpreters8917806
Ref: library/cmd doc8917980
Ref: 31398917980
Ref: library/cmd cmd-support-for-line-oriented-command-interpreters8917980
Ref: 313a8917980
Ref: library/cmd module-cmd8917980
Ref: 1a8917980
Ref: library/cmd cmd Cmd8918456
Ref: 313b8918456
Ref: cmd --- Support for line-oriented command interpreters-Footnote-18919650
Node: Cmd Objects8919712
Ref: library/cmd cmd-objects8919834
Ref: 313d8919834
Ref: library/cmd id18919834
Ref: 313e8919834
Ref: library/cmd cmd Cmd cmdloop8919933
Ref: 313f8919933
Ref: library/cmd cmd Cmd onecmd8922502
Ref: 31428922502
Ref: library/cmd cmd Cmd emptyline8923099
Ref: 31458923099
Ref: library/cmd cmd Cmd default8923303
Ref: 31448923303
Ref: library/cmd cmd Cmd completedefault8923506
Ref: 31468923506
Ref: library/cmd cmd Cmd precmd8923734
Ref: 31438923734
Ref: library/cmd cmd Cmd postcmd8924219
Ref: 31418924219
Ref: library/cmd cmd Cmd preloop8924858
Ref: 31478924858
Ref: library/cmd cmd Cmd postloop8925058
Ref: 31488925058
Ref: library/cmd cmd Cmd prompt8925348
Ref: 31498925348
Ref: library/cmd cmd Cmd identchars8925414
Ref: 314a8925414
Ref: library/cmd cmd Cmd lastcmd8925506
Ref: 314b8925506
Ref: library/cmd cmd Cmd cmdqueue8925576
Ref: 314c8925576
Ref: library/cmd cmd Cmd intro8925824
Ref: 31408925824
Ref: library/cmd cmd Cmd doc_header8925975
Ref: 314d8925975
Ref: library/cmd cmd Cmd misc_header8926092
Ref: 314e8926092
Ref: library/cmd cmd Cmd undoc_header8926308
Ref: 314f8926308
Ref: library/cmd cmd Cmd ruler8926521
Ref: 31508926521
Ref: library/cmd cmd Cmd use_rawinput8926692
Ref: 313c8926692
Node: Cmd Example8927146
Ref: library/cmd cmd-example8927268
Ref: 31518927268
Ref: library/cmd id28927268
Ref: 31528927268
Node: shlex --- Simple lexical analysis8932611
Ref: library/shlex doc8932756
Ref: 31538932756
Ref: library/shlex module-shlex8932756
Ref: e98932756
Ref: library/shlex shlex-simple-lexical-analysis8932756
Ref: 31548932756
Ref: library/shlex shlex split8933277
Ref: 2198933277
Ref: library/shlex shlex join8933932
Ref: 2188933932
Ref: library/shlex shlex quote8934384
Ref: a788934384
Ref: library/shlex shlex shlex8935682
Ref: 57f8935682
Ref: shlex --- Simple lexical analysis-Footnote-18937910
Node: shlex Objects8937974
Ref: library/shlex id18938079
Ref: 31588938079
Ref: library/shlex shlex-objects8938079
Ref: 31598938079
Ref: library/shlex shlex shlex get_token8938183
Ref: 315a8938183
Ref: library/shlex shlex shlex push_token8938552
Ref: 315b8938552
Ref: library/shlex shlex shlex read_token8938640
Ref: 315d8938640
Ref: library/shlex shlex shlex sourcehook8938885
Ref: 315e8938885
Ref: library/shlex shlex shlex push_source8940431
Ref: 31608940431
Ref: library/shlex shlex shlex pop_source8940740
Ref: 31618940740
Ref: library/shlex shlex shlex error_leader8940945
Ref: 31628940945
Ref: library/shlex shlex shlex commenters8941680
Ref: 31558941680
Ref: library/shlex shlex shlex wordchars8941899
Ref: 31578941899
Ref: library/shlex shlex shlex whitespace8942591
Ref: 31648942591
Ref: library/shlex shlex shlex escape8942786
Ref: 31658942786
Ref: library/shlex shlex shlex quotes8942948
Ref: 31668942948
Ref: library/shlex shlex shlex escapedquotes8943230
Ref: 31678943230
Ref: library/shlex shlex shlex whitespace_split8943456
Ref: 31638943456
Ref: library/shlex shlex shlex infile8943975
Ref: 31568943975
Ref: library/shlex shlex shlex instream8944203
Ref: 31688944203
Ref: library/shlex shlex shlex source8944325
Ref: 315f8944325
Ref: library/shlex shlex shlex debug8944912
Ref: 31698944912
Ref: library/shlex shlex shlex lineno8945173
Ref: 316a8945173
Ref: library/shlex shlex shlex token8945266
Ref: 316b8945266
Ref: library/shlex shlex shlex eof8945380
Ref: 315c8945380
Ref: library/shlex shlex shlex punctuation_chars8945553
Ref: f818945553
Node: Parsing Rules8945957
Ref: library/shlex parsing-rules8946105
Ref: 316c8946105
Ref: library/shlex shlex-parsing-rules8946105
Ref: 316d8946105
Node: Improved Compatibility with Shells8948124
Ref: library/shlex improved-compatibility-with-shells8948250
Ref: 316e8948250
Ref: library/shlex improved-shell-compatibility8948250
Ref: 5808948250
Node: 以 Tk 打造 GUI8951093
Ref: library/tk doc8951228
Ref: 316f8951228
Ref: library/tk graphical-user-interfaces-with-tk8951228
Ref: 31708951228
Ref: library/tk tkinter8951228
Ref: 31718951228
Node: tkinter --- Python interface to Tcl/Tk8952896
Ref: library/tkinter doc8953030
Ref: 31738953030
Ref: library/tkinter module-tkinter8953030
Ref: 10d8953030
Ref: library/tkinter tkinter-python-interface-to-tcl-tk8953030
Ref: 31748953030
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-18955460
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-28955536
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-38955581
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-48955612
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-58955652
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-68955691
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-78955742
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-88955828
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-98955897
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-108955954
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-118955987
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-128956011
Ref: tkinter --- Python interface to Tcl/Tk-Footnote-138956071
Node: Tkinter Modules8956108
Ref: library/tkinter tkinter-modules8956229
Ref: 31758956229
Ref: library/tkinter tkinter Tk8957076
Ref: 31768957076
Ref: library/tkinter tkinter Tcl8957395
Ref: 31778957395
Node: Tkinter Life Preserver8958933
Ref: library/tkinter tkinter-life-preserver8959090
Ref: 31788959090
Node: How To Use This Section8959984
Ref: library/tkinter how-to-use-this-section8960103
Ref: 31798960103
Node: A Simple Hello World Program8961535
Ref: library/tkinter a-simple-hello-world-program8961654
Ref: 317a8961654
Node: A Very Quick Look at Tcl/Tk8962526
Ref: library/tkinter a-very-quick-look-at-tcl-tk8962697
Ref: 317b8962697
Node: Mapping Basic Tk into Tkinter8966049
Ref: library/tkinter mapping-basic-tk-into-tkinter8966228
Ref: 317d8966228
Ref: library/tkinter tkinter-basic-mapping8966228
Ref: 317c8966228
Node: How Tk and Tkinter are Related8968050
Ref: library/tkinter how-tk-and-tkinter-are-related8968217
Ref: 317f8968217
Node: Handy Reference8969489
Ref: library/tkinter handy-reference8969640
Ref: 31808969640
Node: Setting Options8969892
Ref: library/tkinter setting-options8969978
Ref: 31818969978
Ref: library/tkinter tkinter-setting-options8969978
Ref: 317e8969978
Node: The Packer8973169
Ref: library/tkinter the-packer8973278
Ref: 31828973278
Node: Packer Options8974924
Ref: library/tkinter packer-options8975043
Ref: 31838975043
Node: Coupling Widget Variables8975743
Ref: library/tkinter coupling-widget-variables8975870
Ref: 31848975870
Node: The Window Manager8978072
Ref: library/tkinter the-window-manager8978205
Ref: 31858978205
Node: Tk Option Data Types8979599
Ref: library/tkinter tk-option-data-types8979726
Ref: 31868979726
Node: Bindings and Events8982788
Ref: library/tkinter bindings-and-events8982916
Ref: 31878982916
Node: The index Parameter8985647
Ref: library/tkinter the-index-parameter8985761
Ref: 31888985761
Node: Images8987692
Ref: library/tkinter images8987778
Ref: 31898987778
Ref: Images-Footnote-18988711
Node: File Handlers8988745
Ref: library/tkinter file-handlers8988857
Ref: 318a8988857
Ref: library/tkinter tkinter-file-handlers8988857
Ref: 318b8988857
Ref: library/tkinter tkinter Widget tk createfilehandler8989799
Ref: 318c8989799
Ref: library/tkinter tkinter Widget tk deletefilehandler8990240
Ref: 318d8990240
Ref: library/tkinter tkinter READABLE8990328
Ref: 318e8990328
Ref: library/tkinter tkinter WRITABLE8990355
Ref: 318f8990355
Ref: library/tkinter tkinter EXCEPTION8990382
Ref: 31908990382
Node: tkinter ttk --- Tk themed widgets8990457
Ref: library/tkinter ttk doc8990640
Ref: 31918990640
Ref: library/tkinter ttk module-tkinter ttk8990640
Ref: 1108990640
Ref: library/tkinter ttk tkinter-ttk-tk-themed-widgets8990640
Ref: 31928990640
Ref: tkinter ttk --- Tk themed widgets-Footnote-18991701
Ref: tkinter ttk --- Tk themed widgets-Footnote-28991771
Node: Using Ttk8991824
Ref: library/tkinter ttk using-ttk8991923
Ref: 31938991923
Ref: Using Ttk-Footnote-18993071
Node: Ttk Widgets8993134
Ref: library/tkinter ttk ttk-widgets8993248
Ref: 31948993248
Node: Widget8994357
Ref: library/tkinter ttk widget8994470
Ref: 319b8994470
Node: Standard Options8994787
Ref: library/tkinter ttk standard-options8994880
Ref: 319c8994880
Node: Scrollable Widget Options8996552
Ref: library/tkinter ttk scrollable-widget-options8996667
Ref: 319d8996667
Node: Label Options8997785
Ref: library/tkinter ttk label-options8997905
Ref: 319e8997905
Node: Compatibility Options9000458
Ref: library/tkinter ttk compatibility-options9000566
Ref: 319f9000566
Node: Widget States9001085
Ref: library/tkinter ttk widget-states9001190
Ref: 31a19001190
Node: ttk Widget9002848
Ref: library/tkinter ttk ttk-widget9002923
Ref: 31a29002923
Ref: library/tkinter ttk tkinter ttk Widget9003110
Ref: 31989003110
Ref: library/tkinter ttk tkinter ttk Widget identify9003142
Ref: 31a39003142
Ref: library/tkinter ttk tkinter ttk Widget instate9003391
Ref: 31a49003391
Ref: library/tkinter ttk tkinter ttk Widget state9003741
Ref: 31a09003741
Node: Combobox9004135
Ref: library/tkinter ttk combobox9004244
Ref: 31a59004244
Node: Options9004939
Ref: library/tkinter ttk options9005014
Ref: 31a69005014
Node: Virtual events9007479
Ref: library/tkinter ttk virtual-events9007575
Ref: 31a79007575
Node: ttk Combobox9007755
Ref: library/tkinter ttk ttk-combobox9007835
Ref: 31a89007835
Ref: library/tkinter ttk tkinter ttk Combobox9007882
Ref: 31959007882
Ref: library/tkinter ttk tkinter ttk Combobox current9007916
Ref: 31a99007916
Ref: library/tkinter ttk tkinter ttk Combobox get9008198
Ref: 31aa9008198
Ref: library/tkinter ttk tkinter ttk Combobox set9008283
Ref: 31ab9008283
Node: Spinbox9008373
Ref: library/tkinter ttk spinbox9008484
Ref: 31ac9008484
Node: Options<2>9009244
Ref: library/tkinter ttk id19009324
Ref: 31ad9009324
Node: Virtual events<2>9011701
Ref: library/tkinter ttk id29011801
Ref: 31ae9011801
Node: ttk Spinbox9012009
Ref: library/tkinter ttk ttk-spinbox9012090
Ref: 31af9012090
Ref: library/tkinter ttk tkinter ttk Spinbox9012135
Ref: 4029012135
Ref: library/tkinter ttk tkinter ttk Spinbox get9012168
Ref: 31b09012168
Ref: library/tkinter ttk tkinter ttk Spinbox set9012252
Ref: 31b19012252
Node: Notebook9012341
Ref: library/tkinter ttk notebook9012455
Ref: 31b29012455
Node: Options<3>9012815
Ref: library/tkinter ttk id39012890
Ref: 31b39012890
Node: Tab Options9014060
Ref: library/tkinter ttk tab-options9014159
Ref: 31b49014159
Node: Tab Identifiers9016193
Ref: library/tkinter ttk tab-identifiers9016296
Ref: 31b69016296
Node: Virtual Events9016818
Ref: library/tkinter ttk id49016922
Ref: 31b89016922
Node: ttk Notebook9017066
Ref: library/tkinter ttk ttk-notebook9017146
Ref: 31b99017146
Ref: library/tkinter ttk tkinter ttk Notebook9017193
Ref: 31969017193
Ref: library/tkinter ttk tkinter ttk Notebook add9017227
Ref: 31ba9017227
Ref: library/tkinter ttk tkinter ttk Notebook forget9017518
Ref: 31bb9017518
Ref: library/tkinter ttk tkinter ttk Notebook hide9017662
Ref: 31bc9017662
Ref: library/tkinter ttk tkinter ttk Notebook identify9017978
Ref: 31bd9017978
Ref: library/tkinter ttk tkinter ttk Notebook index9018126
Ref: 31b79018126
Ref: library/tkinter ttk tkinter ttk Notebook insert9018307
Ref: 31be9018307
Ref: library/tkinter ttk tkinter ttk Notebook select9018694
Ref: 31bf9018694
Ref: library/tkinter ttk tkinter ttk Notebook tab9019014
Ref: 31c09019014
Ref: library/tkinter ttk tkinter ttk Notebook tabs9019366
Ref: 31c19019366
Ref: library/tkinter ttk tkinter ttk Notebook enable_traversal9019460
Ref: 31b59019460
Node: Progressbar9020293
Ref: library/tkinter ttk progressbar9020409
Ref: 31c29020409
Node: Options<4>9020850
Ref: library/tkinter ttk id59020932
Ref: 31c39020932
Node: ttk Progressbar9022774
Ref: library/tkinter ttk ttk-progressbar9022856
Ref: 31c49022856
Ref: library/tkinter ttk tkinter ttk Progressbar9022909
Ref: 31979022909
Ref: library/tkinter ttk tkinter ttk Progressbar start9022946
Ref: 31c59022946
Ref: library/tkinter ttk tkinter ttk Progressbar step9023220
Ref: 31c69023220
Ref: library/tkinter ttk tkinter ttk Progressbar stop9023373
Ref: 31c79023373
Node: Separator9023564
Ref: library/tkinter ttk separator9023680
Ref: 31c89023680
Node: Options<5>9023910
Ref: library/tkinter ttk id69023966
Ref: 31c99023966
Node: Sizegrip9024342
Ref: library/tkinter ttk sizegrip9024455
Ref: 31ca9024455
Node: Platform-specific notes9024805
Ref: library/tkinter ttk platform-specific-notes9024886
Ref: 31cb9024886
Node: Bugs9025144
Ref: library/tkinter ttk bugs9025225
Ref: 31cc9025225
Node: Treeview9025494
Ref: library/tkinter ttk treeview9025609
Ref: 31cd9025609
Node: Options<6>9026967
Ref: library/tkinter ttk id79027043
Ref: 31d19027043
Node: Item Options9029648
Ref: library/tkinter ttk item-options9029744
Ref: 31d29029744
Node: Tag Options9030915
Ref: library/tkinter ttk tag-options9031019
Ref: 31d39031019
Node: Column Identifiers9031744
Ref: library/tkinter ttk column-identifiers9031853
Ref: 31ce9031853
Node: Virtual Events<2>9032724
Ref: library/tkinter ttk id89032834
Ref: 31d49032834
Node: ttk Treeview9033731
Ref: library/tkinter ttk ttk-treeview9033814
Ref: 31d69033814
Ref: library/tkinter ttk tkinter ttk Treeview9033861
Ref: 2be9033861
Ref: library/tkinter ttk tkinter ttk Treeview bbox9033895
Ref: 31d79033895
Ref: library/tkinter ttk tkinter ttk Treeview get_children9034338
Ref: 31d89034338
Ref: library/tkinter ttk tkinter ttk Treeview set_children9034510
Ref: 31d99034510
Ref: library/tkinter ttk tkinter ttk Treeview column9034908
Ref: 31da9034908
Ref: library/tkinter ttk tkinter ttk Treeview delete9036320
Ref: 31db9036320
Ref: library/tkinter ttk tkinter ttk Treeview detach9036472
Ref: 31dc9036472
Ref: library/tkinter ttk tkinter ttk Treeview exists9036789
Ref: 31dd9036789
Ref: library/tkinter ttk tkinter ttk Treeview focus9036905
Ref: 31d59036905
Ref: library/tkinter ttk tkinter ttk Treeview heading9037104
Ref: 31de9037104
Ref: library/tkinter ttk tkinter ttk Treeview identify9038207
Ref: 31df9038207
Ref: library/tkinter ttk tkinter ttk Treeview identify_row9038450
Ref: 31e09038450
Ref: library/tkinter ttk tkinter ttk Treeview identify_column9038551
Ref: 31e19038551
Ref: library/tkinter ttk tkinter ttk Treeview identify_region9038718
Ref: 31e29038718
Ref: library/tkinter ttk tkinter ttk Treeview identify_element9039360
Ref: 31e39039360
Ref: library/tkinter ttk tkinter ttk Treeview index9039494
Ref: 31e49039494
Ref: library/tkinter ttk tkinter ttk Treeview insert9039628
Ref: 31e59039628
Ref: library/tkinter ttk tkinter ttk Treeview item9040527
Ref: 31e69040527
Ref: library/tkinter ttk tkinter ttk Treeview move9040911
Ref: 31e79040911
Ref: library/tkinter ttk tkinter ttk Treeview next9041355
Ref: 31e89041355
Ref: library/tkinter ttk tkinter ttk Treeview parent9041516
Ref: 31e99041516
Ref: library/tkinter ttk tkinter ttk Treeview prev9041673
Ref: 31ea9041673
Ref: library/tkinter ttk tkinter ttk Treeview reattach9041839
Ref: 31eb9041839
Ref: library/tkinter ttk tkinter ttk Treeview see9041947
Ref: 31ec9041947
Ref: library/tkinter ttk tkinter ttk Treeview selection9042209
Ref: 2bd9042209
Ref: library/tkinter ttk tkinter ttk Treeview selection_set9042454
Ref: 2bf9042454
Ref: library/tkinter ttk tkinter ttk Treeview selection_add9042656
Ref: 31ed9042656
Ref: library/tkinter ttk tkinter ttk Treeview selection_remove9042853
Ref: 31ee9042853
Ref: library/tkinter ttk tkinter ttk Treeview selection_toggle9043058
Ref: 31ef9043058
Ref: library/tkinter ttk tkinter ttk Treeview set9043280
Ref: 31f09043280
Ref: library/tkinter ttk tkinter ttk Treeview tag_bind9043651
Ref: 31f19043651
Ref: library/tkinter ttk tkinter ttk Treeview tag_configure9043927
Ref: 31f29043927
Ref: library/tkinter ttk tkinter ttk Treeview tag_has9044362
Ref: 31f39044362
Ref: library/tkinter ttk tkinter ttk Treeview xview9044653
Ref: 31cf9044653
Ref: library/tkinter ttk tkinter ttk Treeview yview9044755
Ref: 31d09044755
Node: Ttk Styling9044855
Ref: library/tkinter ttk ttk-styling9044953
Ref: 31f49044953
Ref: library/tkinter ttk ttkstyling9044953
Ref: 31999044953
Ref: library/tkinter ttk tkinter ttk Style9045546
Ref: 319a9045546
Ref: library/tkinter ttk tkinter ttk Style configure9045636
Ref: 31f59045636
Ref: library/tkinter ttk tkinter ttk Style map9046369
Ref: edb9046369
Ref: library/tkinter ttk tkinter ttk Style lookup9047640
Ref: 31f69047640
Ref: library/tkinter ttk tkinter ttk Style layout9048167
Ref: 31f79048167
Ref: library/tkinter ttk tkinter ttk Style element_create9049485
Ref: 31f99049485
Ref: library/tkinter ttk tkinter ttk Style element_names9051577
Ref: 31fa9051577
Ref: library/tkinter ttk tkinter ttk Style element_options9051688
Ref: 31fb9051688
Ref: library/tkinter ttk tkinter ttk Style theme_create9051800
Ref: 31fc9051800
Ref: library/tkinter ttk tkinter ttk Style theme_settings9052219
Ref: 31fd9052219
Ref: library/tkinter ttk tkinter ttk Style theme_names9053701
Ref: 31fe9053701
Ref: library/tkinter ttk tkinter ttk Style theme_use9053787
Ref: 31ff9053787
Ref: Ttk Styling-Footnote-19054090
Node: Layouts9054151
Ref: library/tkinter ttk layouts9054206
Ref: 31f89054206
Node: tkinter tix --- Extension widgets for Tk9055490
Ref: library/tkinter tix doc9055680
Ref: 32009055680
Ref: library/tkinter tix layout9055680
Ref: 32019055680
Ref: library/tkinter tix layouts9055680
Ref: 32029055680
Ref: library/tkinter tix module-tkinter tix9055680
Ref: 10f9055680
Ref: library/tkinter tix tkinter-tix-extension-widgets-for-tk9055680
Ref: 32039055680
Ref: tkinter tix --- Extension widgets for Tk-Footnote-19057614
Ref: tkinter tix --- Extension widgets for Tk-Footnote-29057684
Ref: tkinter tix --- Extension widgets for Tk-Footnote-39057720
Ref: tkinter tix --- Extension widgets for Tk-Footnote-49057773
Ref: tkinter tix --- Extension widgets for Tk-Footnote-59057850
Node: Using Tix9057907
Ref: library/tkinter tix using-tix9058013
Ref: 320a9058013
Ref: library/tkinter tix tkinter tix Tk9058052
Ref: 320b9058052
Node: Tix Widgets9059026
Ref: library/tkinter tix tix-widgets9059153
Ref: 320c9059153
Ref: Tix Widgets-Footnote-19059493
Node: Basic Widgets9059571
Ref: library/tkinter tix basic-widgets9059655
Ref: 320d9059655
Ref: library/tkinter tix tkinter tix Balloon9059702
Ref: 320e9059702
Ref: library/tkinter tix tkinter tix ButtonBox9059981
Ref: 320f9059981
Ref: library/tkinter tix tkinter tix ComboBox9060123
Ref: 32059060123
Ref: library/tkinter tix tkinter tix Control9060358
Ref: 32069060358
Ref: library/tkinter tix tkinter tix LabelEntry9060672
Ref: 32109060672
Ref: library/tkinter tix tkinter tix LabelFrame9060884
Ref: 32119060884
Ref: library/tkinter tix tkinter tix Meter9061187
Ref: 32129061187
Ref: library/tkinter tix tkinter tix OptionMenu9061341
Ref: 32139061341
Ref: library/tkinter tix tkinter tix PopupMenu9061435
Ref: 32149061435
Ref: library/tkinter tix tkinter tix Select9061684
Ref: 32159061684
Ref: library/tkinter tix tkinter tix StdButtonBox9061882
Ref: 32169061882
Ref: Basic Widgets-Footnote-19062055
Ref: Basic Widgets-Footnote-29062135
Ref: Basic Widgets-Footnote-39062217
Ref: Basic Widgets-Footnote-49062298
Ref: Basic Widgets-Footnote-59062378
Ref: Basic Widgets-Footnote-69062461
Ref: Basic Widgets-Footnote-79062544
Ref: Basic Widgets-Footnote-89062622
Ref: Basic Widgets-Footnote-99062705
Ref: Basic Widgets-Footnote-109062787
Ref: Basic Widgets-Footnote-119062867
Node: File Selectors9062953
Ref: library/tkinter tix file-selectors9063066
Ref: 32179063066
Ref: library/tkinter tix tkinter tix DirList9063115
Ref: 32189063115
Ref: library/tkinter tix tkinter tix DirTree9063376
Ref: 32199063376
Ref: library/tkinter tix tkinter tix DirSelectDialog9063637
Ref: 321a9063637
Ref: library/tkinter tix tkinter tix DirSelectBox9063894
Ref: 321b9063894
Ref: library/tkinter tix tkinter tix ExFileSelectBox9064237
Ref: 321c9064237
Ref: library/tkinter tix tkinter tix FileSelectBox9064569
Ref: 321d9064569
Ref: library/tkinter tix tkinter tix FileEntry9064902
Ref: 32089064902
Ref: File Selectors-Footnote-19065223
Ref: File Selectors-Footnote-29065303
Ref: File Selectors-Footnote-39065383
Ref: File Selectors-Footnote-49065471
Ref: File Selectors-Footnote-59065559
Ref: File Selectors-Footnote-69065645
Node: Hierarchical ListBox9065727
Ref: library/tkinter tix hierarchical-listbox9065842
Ref: 321e9065842
Ref: library/tkinter tix tkinter tix HList9065903
Ref: 32049065903
Ref: library/tkinter tix tkinter tix CheckList9066189
Ref: 321f9066189
Ref: library/tkinter tix tkinter tix Tree9066478
Ref: 32209066478
Ref: Hierarchical ListBox-Footnote-19066719
Ref: Hierarchical ListBox-Footnote-29066797
Ref: Hierarchical ListBox-Footnote-39066879
Node: Tabular ListBox9066956
Ref: library/tkinter tix tabular-listbox9067072
Ref: 32219067072
Ref: library/tkinter tix tkinter tix TList9067123
Ref: 32229067123
Ref: Tabular ListBox-Footnote-19067610
Node: Manager Widgets9067688
Ref: library/tkinter tix manager-widgets9067795
Ref: 32239067795
Ref: library/tkinter tix tkinter tix PanedWindow9067846
Ref: 32099067846
Ref: library/tkinter tix tkinter tix ListNoteBook9068154
Ref: 32249068154
Ref: library/tkinter tix tkinter tix NoteBook9068606
Ref: 32079068606
Ref: Manager Widgets-Footnote-19069014
Ref: Manager Widgets-Footnote-29069098
Ref: Manager Widgets-Footnote-39069183
Node: Image Types9069264
Ref: library/tkinter tix image-types9069377
Ref: 32259069377
Ref: Image Types-Footnote-19069989
Ref: Image Types-Footnote-29070065
Node: Miscellaneous Widgets9070143
Ref: library/tkinter tix miscellaneous-widgets9070262
Ref: 32269070262
Ref: library/tkinter tix tkinter tix InputOnly9070325
Ref: 32279070325
Ref: Miscellaneous Widgets-Footnote-19070527
Node: Form Geometry Manager9070609
Ref: library/tkinter tix form-geometry-manager9070708
Ref: 32289070708
Ref: library/tkinter tix tkinter tix Form9070854
Ref: 32299070854
Ref: Form Geometry Manager-Footnote-19071006
Node: Tix Commands9071083
Ref: library/tkinter tix tix-commands9071192
Ref: 322a9071192
Ref: library/tkinter tix tkinter tix tixCommand9071239
Ref: 322b9071239
Ref: library/tkinter tix tkinter tix tixCommand tix_configure9071746
Ref: 322c9071746
Ref: library/tkinter tix tkinter tix tixCommand tix_cget9072437
Ref: 322d9072437
Ref: library/tkinter tix tkinter tix tixCommand tix_getbitmap9072618
Ref: 322e9072618
Ref: library/tkinter tix tkinter tix tixCommand tix_addbitmapdir9073175
Ref: 322f9073175
Ref: library/tkinter tix tkinter tix tixCommand tix_filedialog9073715
Ref: 32319073715
Ref: library/tkinter tix tkinter tix tixCommand tix_getimage9074301
Ref: 32309074301
Ref: library/tkinter tix tkinter tix tixCommand tix_option_get9075097
Ref: 32329075097
Ref: library/tkinter tix tkinter tix tixCommand tix_resetoptions9075212
Ref: 32339075212
Ref: Tix Commands-Footnote-19076051
Node: tkinter scrolledtext --- Scrolled Text Widget9076123
Ref: library/tkinter scrolledtext doc9076288
Ref: 32349076288
Ref: library/tkinter scrolledtext module-tkinter scrolledtext9076288
Ref: 10e9076288
Ref: library/tkinter scrolledtext tkinter-scrolledtext-scrolled-text-widget9076288
Ref: 32359076288
Ref: library/tkinter scrolledtext tkinter scrolledtext ScrolledText frame9077254
Ref: 32369077254
Ref: library/tkinter scrolledtext tkinter scrolledtext ScrolledText vbar9077351
Ref: 32379077351
Ref: tkinter scrolledtext --- Scrolled Text Widget-Footnote-19077447
Node: IDLE<54>9077527
Ref: library/idle doc9077665
Ref: 32389077665
Ref: library/idle id19077665
Ref: 32399077665
Ref: library/idle idle9077665
Ref: 94f9077665
Ref: IDLE<54>-Footnote-19078695
Node: Menus9078759
Ref: library/idle menus9078840
Ref: 323a9078840
Node: File menu Shell and Editor9080122
Ref: library/idle file-menu-shell-and-editor9080225
Ref: 323b9080225
Node: Edit menu Shell and Editor9081512
Ref: library/idle edit-menu-shell-and-editor9081654
Ref: 323c9081654
Node: Format menu Editor window only9083395
Ref: library/idle format-menu9083538
Ref: 323f9083538
Ref: library/idle format-menu-editor-window-only9083538
Ref: 32409083538
Node: Run menu Editor window only9084907
Ref: library/idle run-menu-editor-window-only9085052
Ref: 32419085052
Ref: library/idle run-module9085131
Ref: 32429085131
Ref: library/idle run-custom9085623
Ref: 32449085623
Ref: library/idle check-module9085882
Ref: 32439085882
Ref: library/idle python-shell9086226
Ref: 32459086226
Node: Shell menu Shell window only9086288
Ref: library/idle shell-menu-shell-window-only9086431
Ref: 32469086431
Node: Debug menu Shell window only9086948
Ref: library/idle debug-menu-shell-window-only9087093
Ref: 32479087093
Node: Options menu Shell and Editor9088049
Ref: library/idle options-menu-shell-and-editor9088194
Ref: 32489088194
Node: Window menu Shell and Editor9089811
Ref: library/idle window-menu-shell-and-editor9089954
Ref: 324b9089954
Node: Help menu Shell and Editor9090146
Ref: library/idle help-menu-shell-and-editor9090273
Ref: 324c9090273
Node: Context Menus9090993
Ref: library/idle context-menus9091083
Ref: 324e9091083
Node: Editing and navigation9092257
Ref: library/idle editing-and-navigation9092373
Ref: 324f9092373
Ref: library/idle id29092373
Ref: 32509092373
Node: Editor windows9092598
Ref: library/idle editor-windows9092692
Ref: 32519092692
Node: Key bindings9093314
Ref: library/idle key-bindings9093438
Ref: 32529093438
Node: Automatic indentation9094826
Ref: library/idle automatic-indentation9094947
Ref: 32539094947
Node: Completions9095527
Ref: library/idle completions9095644
Ref: 323d9095644
Ref: library/idle id39095644
Ref: 32549095644
Node: Calltips9098291
Ref: library/idle calltips9098399
Ref: 323e9098399
Ref: library/idle id49098399
Ref: 32559098399
Node: Code Context9100021
Ref: library/idle code-context9100137
Ref: 324a9100137
Ref: library/idle id59100137
Ref: 32569100137
Node: Python Shell window9101025
Ref: library/idle python-shell-window9101144
Ref: 32579101144
Node: Text colors9102270
Ref: library/idle text-colors9102368
Ref: 32589102368
Node: Startup and code execution9103131
Ref: library/idle startup-and-code-execution9103262
Ref: 32599103262
Node: Command line usage9104393
Ref: library/idle command-line-usage9104498
Ref: 325a9104498
Node: Startup failure9105538
Ref: library/idle startup-failure9105669
Ref: 325b9105669
Node: Running user code9108856
Ref: library/idle running-user-code9108989
Ref: 325c9108989
Node: User output in Shell9111689
Ref: library/idle user-output-in-shell9111838
Ref: 325d9111838
Node: Developing tkinter applications9114924
Ref: library/idle developing-tkinter-applications9115084
Ref: 325e9115084
Node: Running without a subprocess9116333
Ref: library/idle running-without-a-subprocess9116464
Ref: 325f9116464
Node: Help and preferences9117837
Ref: library/idle help-and-preferences9117937
Ref: 32609117937
Node: Help sources9118084
Ref: library/idle help-sources9118181
Ref: 324d9118181
Ref: library/idle id69118181
Ref: 32619118181
Node: Setting preferences9119043
Ref: library/idle preferences9119162
Ref: 32499119162
Ref: library/idle setting-preferences9119162
Ref: 32629119162
Node: IDLE on macOS9120171
Ref: library/idle idle-on-macos9120288
Ref: 32639120288
Node: Extensions9120547
Ref: library/idle extensions9120636
Ref: 32649120636
Node: 其它的 GUI9120987
Ref: library/othergui doc9121071
Ref: 32659121071
Ref: library/othergui other-graphical-user-interface-packages9121071
Ref: 32669121071
Ref: library/othergui other-gui-packages9121071
Ref: 31729121071
Ref: 其它的 GUI-Footnote-19123483
Ref: 其它的 GUI-Footnote-29123533
Ref: 其它的 GUI-Footnote-39123585
Ref: 其它的 GUI-Footnote-49123614
Ref: 其它的 GUI-Footnote-59123668
Ref: 其它的 GUI-Footnote-69123698
Ref: 其它的 GUI-Footnote-79123729
Ref: 其它的 GUI-Footnote-89123784
Ref: 其它的 GUI-Footnote-99123843
Ref: 其它的 GUI-Footnote-109123882
Ref: 其它的 GUI-Footnote-119123916
Ref: 其它的 GUI-Footnote-129123952
Node: 開發工具9124005
Ref: library/development doc9124151
Ref: 32679124151
Ref: library/development development9124151
Ref: 32689124151
Ref: library/development development-tools9124151
Ref: 32699124151
Node: typing --- Support for type hints9125564
Ref: library/typing doc9125711
Ref: 326a9125711
Ref: library/typing module-typing9125711
Ref: 11a9125711
Ref: library/typing typing-support-for-type-hints9125711
Ref: 326b9125711
Ref: typing --- Support for type hints-Footnote-19127102
Ref: typing --- Support for type hints-Footnote-29127167
Ref: typing --- Support for type hints-Footnote-39127216
Ref: typing --- Support for type hints-Footnote-49127265
Ref: typing --- Support for type hints-Footnote-59127314
Ref: typing --- Support for type hints-Footnote-69127363
Ref: typing --- Support for type hints-Footnote-79127412
Ref: typing --- Support for type hints-Footnote-89127461
Ref: typing --- Support for type hints-Footnote-99127510
Node: Type aliases9127559
Ref: library/typing type-aliases9127657
Ref: 326f9127657
Node: NewType9128829
Ref: library/typing distinct9128944
Ref: 32709128944
Ref: library/typing newtype9128944
Ref: 32719128944
Ref: NewType-Footnote-19131820
Node: Callable9131869
Ref: library/typing callable9131980
Ref: 32729131980
Node: Generics9132636
Ref: library/typing generics9132766
Ref: 32739132766
Ref: library/typing id19132766
Ref: 32749132766
Node: User-defined generic types9133466
Ref: library/typing user-defined-generic-types9133600
Ref: 32759133600
Node: The Any type9136861
Ref: library/typing the-any-type9137018
Ref: 32769137018
Node: Nominal vs structural subtyping9139606
Ref: library/typing nominal-vs-structural-subtyping9139769
Ref: 32779139769
Ref: Nominal vs structural subtyping-Footnote-19141421
Ref: Nominal vs structural subtyping-Footnote-29141470
Ref: Nominal vs structural subtyping-Footnote-39141519
Node: Classes functions and decorators9141568
Ref: library/typing classes-functions-and-decorators9141710
Ref: 32789141710
Ref: library/typing typing TypeVar9141868
Ref: f269141868
Ref: library/typing typing Generic9143531
Ref: 326e9143531
Ref: library/typing typing Protocol9144239
Ref: 2409144239
Ref: library/typing typing Type9145223
Ref: 32799145223
Ref: library/typing typing Iterable9146940
Ref: 327a9146940
Ref: library/typing typing Iterator9147050
Ref: 327b9147050
Ref: library/typing typing Reversible9147161
Ref: 327c9147161
Ref: library/typing typing SupportsInt9147275
Ref: 2429147275
Ref: library/typing typing SupportsFloat9147360
Ref: 327d9147360
Ref: library/typing typing SupportsComplex9147449
Ref: 327e9147449
Ref: library/typing typing SupportsBytes9147542
Ref: 327f9147542
Ref: library/typing typing SupportsIndex9147631
Ref: 2439147631
Ref: library/typing typing SupportsAbs9147744
Ref: 32809147744
Ref: library/typing typing SupportsRound9147871
Ref: 32819147871
Ref: library/typing typing Container9148002
Ref: 32829148002
Ref: library/typing typing Hashable9148114
Ref: 32839148114
Ref: library/typing typing Sized9148199
Ref: 32849148199
Ref: library/typing typing Collection9148278
Ref: 5a79148278
Ref: library/typing typing AbstractSet9148442
Ref: 32859148442
Ref: library/typing typing MutableSet9148560
Ref: 32869148560
Ref: library/typing typing Mapping9148675
Ref: 32879148675
Ref: library/typing typing MutableMapping9148970
Ref: 32889148970
Ref: library/typing typing Sequence9149093
Ref: 32899149093
Ref: library/typing typing MutableSequence9149224
Ref: 328a9149224
Ref: library/typing typing ByteString9149345
Ref: 328b9149345
Ref: library/typing typing Deque9149717
Ref: 328c9149717
Ref: library/typing typing List9149880
Ref: 328d9149880
Ref: library/typing typing Set9150429
Ref: 328e9150429
Ref: library/typing typing FrozenSet9150680
Ref: 328f9150680
Ref: library/typing typing MappingView9150799
Ref: 32909150799
Ref: library/typing typing KeysView9150923
Ref: 32919150923
Ref: library/typing typing ItemsView9151058
Ref: 32929151058
Ref: library/typing typing ValuesView9151191
Ref: 32939151191
Ref: library/typing typing Awaitable9151310
Ref: 32949151310
Ref: library/typing typing Coroutine9151447
Ref: ef59151447
Ref: library/typing typing AsyncIterable9151974
Ref: 32969151974
Ref: library/typing typing AsyncIterator9152119
Ref: 32979152119
Ref: library/typing typing ContextManager9152270
Ref: 53a9152270
Ref: library/typing typing AsyncContextManager9152446
Ref: 32989152446
Ref: library/typing typing Dict9152637
Ref: 32999152637
Ref: library/typing typing DefaultDict9153002
Ref: 329a9153002
Ref: library/typing typing OrderedDict9153183
Ref: 329b9153183
Ref: library/typing typing Counter9153364
Ref: 329c9153364
Ref: library/typing typing ChainMap9153539
Ref: 329d9153539
Ref: library/typing typing Generator9153727
Ref: 32959153727
Ref: library/typing typing AsyncGenerator9154863
Ref: 329e9154863
Ref: library/typing typing Text9156125
Ref: 329f9156125
Ref: library/typing typing IO9156598
Ref: 32a09156598
Ref: library/typing typing TextIO9156620
Ref: 32a19156620
Ref: library/typing typing BinaryIO9156646
Ref: 32a29156646
Ref: library/typing typing Pattern9156866
Ref: 32a39156866
Ref: library/typing typing Match9156893
Ref: 32a49156893
Ref: library/typing typing NamedTuple9157246
Ref: 2819157246
Ref: library/typing typing TypedDict9159155
Ref: 23c9159155
Ref: library/typing typing ForwardRef9160952
Ref: 32a59160952
Ref: library/typing typing NewType9161309
Ref: 5aa9161309
Ref: library/typing typing cast9161624
Ref: 32a69161624
Ref: library/typing typing get_type_hints9161923
Ref: 30f9161923
Ref: library/typing typing get_origin9162572
Ref: 2449162572
Ref: library/typing typing get_args9162608
Ref: 2459162608
Ref: library/typing typing overload9163305
Ref: 32a79163305
Ref: library/typing typing final9164571
Ref: 23f9164571
Ref: library/typing typing no_type_check9165247
Ref: 32a89165247
Ref: library/typing typing no_type_check_decorator9165601
Ref: 32a99165601
Ref: library/typing typing type_check_only9165851
Ref: 32aa9165851
Ref: library/typing typing runtime_checkable9166524
Ref: 2419166524
Ref: library/typing typing Any9167248
Ref: 6579167248
Ref: library/typing typing NoReturn9167438
Ref: 32ab9167438
Ref: library/typing typing Union9167714
Ref: 10399167714
Ref: library/typing typing Optional9168679
Ref: 32ac9168679
Ref: library/typing typing Tuple9169369
Ref: 326c9169369
Ref: library/typing typing Callable9170007
Ref: 326d9170007
Ref: library/typing typing Literal9170771
Ref: 23d9170771
Ref: library/typing typing ClassVar9171635
Ref: 5a89171635
Ref: library/typing typing Final9172720
Ref: 23e9172720
Ref: library/typing typing AnyStr9173272
Ref: 32ad9173272
Ref: library/typing typing TYPE_CHECKING9173836
Ref: 5a99173836
Ref: Classes functions and decorators-Footnote-19174572
Ref: Classes functions and decorators-Footnote-29174621
Ref: Classes functions and decorators-Footnote-39174670
Ref: Classes functions and decorators-Footnote-49174719
Ref: Classes functions and decorators-Footnote-59174768
Ref: Classes functions and decorators-Footnote-69174817
Ref: Classes functions and decorators-Footnote-79174866
Ref: Classes functions and decorators-Footnote-89174915
Ref: Classes functions and decorators-Footnote-99174964
Ref: Classes functions and decorators-Footnote-109175013
Ref: Classes functions and decorators-Footnote-119175063
Ref: Classes functions and decorators-Footnote-129175113
Node: pydoc --- Documentation generator and online help system9175163
Ref: library/pydoc doc9175363
Ref: 32ae9175363
Ref: library/pydoc module-pydoc9175363
Ref: da9175363
Ref: library/pydoc pydoc-documentation-generator-and-online-help-system9175363
Ref: 32af9175363
Ref: pydoc --- Documentation generator and online help system-Footnote-19180223
Node: doctest --- Test interactive Python examples9180287
Ref: library/doctest doc9180485
Ref: 32b19180485
Ref: library/doctest doctest-test-interactive-python-examples9180485
Ref: 32b29180485
Ref: library/doctest module-doctest9180485
Ref: 679180485
Ref: doctest --- Test interactive Python examples-Footnote-19184593
Node: Simple Usage Checking Examples in Docstrings9184659
Ref: library/doctest doctest-simple-testmod9184838
Ref: 32b39184838
Ref: library/doctest simple-usage-checking-examples-in-docstrings9184838
Ref: 32b49184838
Node: Simple Usage Checking Examples in a Text File9186614
Ref: library/doctest doctest-simple-testfile9186814
Ref: 32b69186814
Ref: library/doctest simple-usage-checking-examples-in-a-text-file9186814
Ref: 32b79186814
Node: How It Works9189160
Ref: library/doctest doctest-how-it-works9189325
Ref: 32b99189325
Ref: library/doctest how-it-works9189325
Ref: 32ba9189325
Node: Which Docstrings Are Examined?9189978
Ref: library/doctest doctest-which-docstrings9190104
Ref: 32bb9190104
Ref: library/doctest which-docstrings-are-examined9190104
Ref: 32bc9190104
Node: How are Docstring Examples Recognized?9190947
Ref: library/doctest doctest-finding-examples9191111
Ref: 32bd9191111
Ref: library/doctest how-are-docstring-examples-recognized9191111
Ref: 32be9191111
Node: What's the Execution Context?9194199
Ref: library/doctest doctest-execution-context9194355
Ref: 32c29194355
Ref: library/doctest what-s-the-execution-context9194355
Ref: 32c39194355
Node: What About Exceptions?9195072
Ref: library/doctest doctest-exceptions9195202
Ref: 32c49195202
Ref: library/doctest what-about-exceptions9195202
Ref: 32c59195202
Ref: library/doctest option-flags-and-directives9199710
Ref: 32c79199710
Ref: What About Exceptions?-Footnote-19199747
Node: Option Flags9199951
Ref: library/doctest doctest-options9200062
Ref: 8419200062
Ref: library/doctest option-flags9200062
Ref: 32c89200062
Ref: library/doctest doctest DONT_ACCEPT_TRUE_FOR_19200678
Ref: 32c99200678
Ref: library/doctest doctest DONT_ACCEPT_BLANKLINE9201302
Ref: 32ca9201302
Ref: library/doctest doctest NORMALIZE_WHITESPACE9201755
Ref: 32bf9201755
Ref: library/doctest doctest ELLIPSIS9202245
Ref: dd69202245
Ref: library/doctest doctest IGNORE_EXCEPTION_DETAIL9202678
Ref: 32c69202678
Ref: library/doctest doctest SKIP9204705
Ref: 32cb9204705
Ref: library/doctest doctest COMPARISON_FLAGS9205215
Ref: 32cc9205215
Ref: library/doctest doctest REPORT_UDIFF9205387
Ref: dd79205387
Ref: library/doctest doctest REPORT_CDIFF9205543
Ref: dd89205543
Ref: library/doctest doctest REPORT_NDIFF9205703
Ref: dd99205703
Ref: library/doctest doctest REPORT_ONLY_FIRST_FAILURE9206167
Ref: 32cd9206167
Ref: library/doctest doctest FAIL_FAST9206746
Ref: 8429206746
Ref: library/doctest doctest REPORTING_FLAGS9207211
Ref: 32ce9207211
Ref: library/doctest doctest register_optionflag9207468
Ref: 32cf9207468
Node: Directives9207956
Ref: library/doctest directives9208056
Ref: 32d29208056
Ref: library/doctest doctest-directives9208056
Ref: 32c09208056
Ref: library/doctest grammar-token-directive9208281
Ref: 32d39208281
Ref: library/doctest grammar-token-directive-options9208345
Ref: 32d49208345
Ref: library/doctest grammar-token-directive-option9208418
Ref: 32d59208418
Ref: library/doctest grammar-token-on-or-off9208481
Ref: 32d69208481
Ref: library/doctest grammar-token-directive-option-name9208523
Ref: 32d79208523
Node: Warnings<2>9210425
Ref: library/doctest doctest-warnings9210504
Ref: 32d89210504
Ref: library/doctest warnings9210504
Ref: 32d99210504
Node: Basic API9212395
Ref: library/doctest basic-api9212527
Ref: 32da9212527
Ref: library/doctest doctest-basic-api9212527
Ref: 32b59212527
Ref: library/doctest doctest testfile9212910
Ref: 32b89212910
Ref: library/doctest doctest testmod9216840
Ref: dd59216840
Ref: library/doctest doctest run_docstring_examples9218584
Ref: 32dc9218584
Node: Unittest API9219560
Ref: library/doctest doctest-unittest-api9219692
Ref: 32dd9219692
Ref: library/doctest unittest-api9219692
Ref: 32de9219692
Ref: library/doctest doctest DocFileSuite9220462
Ref: 32df9220462
Ref: library/doctest doctest DocTestSuite9224184
Ref: 6d29224184
Ref: library/doctest doctest set_unittest_reportflags9227323
Ref: 32e19227323
Node: Advanced API9228513
Ref: library/doctest advanced-api9228645
Ref: 32e29228645
Ref: library/doctest doctest-advanced-api9228645
Ref: 32e39228645
Node: DocTest Objects9230786
Ref: library/doctest doctest-doctest9230874
Ref: 32e59230874
Ref: library/doctest doctest-objects9230874
Ref: 32e69230874
Ref: library/doctest doctest DocTest9230927
Ref: 32e09230927
Ref: library/doctest doctest DocTest examples9231344
Ref: 32e79231344
Ref: library/doctest doctest DocTest globs9231516
Ref: 32e89231516
Ref: library/doctest doctest DocTest name9231848
Ref: 32e99231848
Ref: library/doctest doctest DocTest filename9232038
Ref: 32ea9232038
Ref: library/doctest doctest DocTest lineno9232272
Ref: 32eb9232272
Ref: library/doctest doctest DocTest docstring9232547
Ref: 32ec9232547
Node: Example Objects9232743
Ref: library/doctest doctest-example9232861
Ref: 32ed9232861
Ref: library/doctest example-objects9232861
Ref: 32ee9232861
Ref: library/doctest doctest Example9232914
Ref: 32e49232914
Ref: library/doctest doctest Example source9233354
Ref: 32ef9233354
Ref: library/doctest doctest Example want9233595
Ref: 32f09233595
Ref: library/doctest doctest Example exc_msg9233943
Ref: 32f19233943
Ref: library/doctest doctest Example lineno9234425
Ref: 32f39234425
Ref: library/doctest doctest Example indent9234653
Ref: 32f49234653
Ref: library/doctest doctest Example options9234843
Ref: 32f59234843
Node: DocTestFinder objects9235236
Ref: library/doctest doctest-doctestfinder9235360
Ref: 32f69235360
Ref: library/doctest doctestfinder-objects9235360
Ref: 32f79235360
Ref: library/doctest doctest DocTestFinder9235425
Ref: 32db9235425
Ref: library/doctest doctest DocTestFinder find9236565
Ref: 32f89236565
Node: DocTestParser objects9238690
Ref: library/doctest doctest-doctestparser9238820
Ref: 32f99238820
Ref: library/doctest doctestparser-objects9238820
Ref: 32fa9238820
Ref: library/doctest doctest DocTestParser9238885
Ref: 32c19238885
Ref: library/doctest doctest DocTestParser get_doctest9239120
Ref: 32fb9239120
Ref: library/doctest doctest DocTestParser get_examples9239521
Ref: 32fc9239521
Ref: library/doctest doctest DocTestParser parse9239865
Ref: 32fd9239865
Node: DocTestRunner objects9240267
Ref: library/doctest doctest-doctestrunner9240397
Ref: 32fe9240397
Ref: library/doctest doctestrunner-objects9240397
Ref: 32ff9240397
Ref: library/doctest doctest DocTestRunner9240462
Ref: 32d19240462
Ref: library/doctest doctest DocTestRunner report_start9242571
Ref: 33009242571
Ref: library/doctest doctest DocTestRunner report_success9243076
Ref: 33019243076
Ref: library/doctest doctest DocTestRunner report_failure9243615
Ref: 33039243615
Ref: library/doctest doctest DocTestRunner report_unexpected_exception9244144
Ref: 33029244144
Ref: library/doctest doctest DocTestRunner run9244825
Ref: 33049244825
Ref: library/doctest doctest DocTestRunner summarize9245847
Ref: 33059245847
Node: OutputChecker objects9246278
Ref: library/doctest doctest-outputchecker9246378
Ref: 33069246378
Ref: library/doctest outputchecker-objects9246378
Ref: 33079246378
Ref: library/doctest doctest OutputChecker9246443
Ref: 32d09246443
Ref: library/doctest doctest OutputChecker check_output9246940
Ref: 33089246940
Ref: library/doctest doctest OutputChecker output_difference9247433
Ref: 33099247433
Node: Debugging9247754
Ref: library/doctest debugging9247881
Ref: 330a9247881
Ref: library/doctest doctest-debugging9247881
Ref: 330b9247881
Ref: library/doctest doctest script_from_examples9249980
Ref: 330e9249980
Ref: library/doctest doctest testsource9250965
Ref: 330f9250965
Ref: library/doctest doctest debug9251760
Ref: 330d9251760
Ref: library/doctest doctest debug_src9252848
Ref: 33119252848
Ref: library/doctest doctest DebugRunner9253720
Ref: 330c9253720
Ref: library/doctest doctest DocTestFailure9254498
Ref: 33139254498
Ref: library/doctest doctest DocTestFailure test9254858
Ref: 33149254858
Ref: library/doctest doctest DocTestFailure example9254978
Ref: 33159254978
Ref: library/doctest doctest DocTestFailure got9255058
Ref: 33169255058
Ref: library/doctest doctest UnexpectedException9255127
Ref: 33129255127
Ref: library/doctest doctest UnexpectedException test9255477
Ref: 33179255477
Ref: library/doctest doctest UnexpectedException example9255602
Ref: 33189255602
Ref: library/doctest doctest UnexpectedException exc_info9255687
Ref: 33199255687
Node: Soapbox9255845
Ref: library/doctest doctest-soapbox9255951
Ref: 331a9255951
Ref: library/doctest soapbox9255951
Ref: 331b9255951
Node: unittest --- 單元測試框架9259804
Ref: library/unittest doc9259983
Ref: 331c9259983
Ref: library/unittest module-unittest9259983
Ref: 11c9259983
Ref: library/unittest unittest-unit-testing-framework9259983
Ref: 331d9259983
Ref: unittest --- 單元測試框架-Footnote-19263149
Ref: unittest --- 單元測試框架-Footnote-29263226
Ref: unittest --- 單元測試框架-Footnote-39263319
Ref: unittest --- 單元測試框架-Footnote-49263352
Ref: unittest --- 單元測試框架-Footnote-59263416
Ref: unittest --- 單元測試框架-Footnote-69263474
Ref: unittest --- 單元測試框架-Footnote-79263504
Ref: unittest --- 單元測試框架-Footnote-89263532
Ref: unittest --- 單元測試框架-Footnote-99263562
Node: 簡單範例9263596
Ref: library/unittest basic-example9263729
Ref: 331f9263729
Ref: library/unittest unittest-minimal-example9263729
Ref: 33209263729
Node: 命令執行列介面 Command-Line Interface9266422
Ref: library/unittest command-line-interface9266596
Ref: 33229266596
Ref: library/unittest unittest-command-line-interface9266596
Ref: 33239266596
Node: 命令列模式選項9267987
Ref: library/unittest command-line-options9268089
Ref: 33259268089
Ref: library/unittest cmdoption-unittest-b9268198
Ref: cc89268198
Ref: library/unittest cmdoption-unittest-c9268476
Ref: cc99268476
Ref: library/unittest cmdoption-unittest-f9268784
Ref: ccb9268784
Ref: library/unittest cmdoption-unittest-k9268876
Ref: 33279268876
Ref: library/unittest cmdoption-unittest-locals9269590
Ref: 33289269590
Node: Test Discovery（測試探索）9269964
Ref: library/unittest test-discovery9270146
Ref: 33299270146
Ref: library/unittest unittest-test-discovery9270146
Ref: 33249270146
Ref: library/unittest cmdoption-unittest-discover-v9271074
Ref: 332a9271074
Ref: library/unittest cmdoption-unittest-discover-s9271139
Ref: 332b9271139
Ref: library/unittest cmdoption-unittest-discover-p9271244
Ref: 332c9271244
Ref: library/unittest cmdoption-unittest-discover-t9271349
Ref: 332d9271349
Node: Organizing test code9273079
Ref: library/unittest organizing-test-code9273239
Ref: 332f9273239
Ref: library/unittest organizing-tests9273239
Ref: 33219273239
Node: Re-using old test code9277995
Ref: library/unittest legacy-unit-tests9278159
Ref: 33319278159
Ref: library/unittest re-using-old-test-code9278159
Ref: 33329278159
Node: Skipping tests and expected failures9279701
Ref: library/unittest skipping-tests-and-expected-failures9279890
Ref: 33339279890
Ref: library/unittest unittest-skipping9279890
Ref: 33349279890
Ref: library/unittest unittest skip9282970
Ref: f859282970
Ref: library/unittest unittest skipIf9283116
Ref: 33379283116
Ref: library/unittest unittest skipUnless9283220
Ref: 33389283220
Ref: library/unittest unittest expectedFailure9283332
Ref: 33369283332
Ref: library/unittest unittest SkipTest9283550
Ref: 9089283550
Node: Distinguishing test iterations using subtests9284035
Ref: library/unittest distinguishing-test-iterations-using-subtests9284223
Ref: 33399284223
Ref: library/unittest subtests9284223
Ref: 9069284223
Node: Classes and functions9286515
Ref: library/unittest classes-and-functions9286692
Ref: 333a9286692
Ref: library/unittest unittest-contents9286692
Ref: 333b9286692
Node: Test cases9286894
Ref: library/unittest test-cases9286985
Ref: 333c9286985
Ref: library/unittest testcase-objects9286985
Ref: 333d9286985
Ref: library/unittest unittest TestCase9287028
Ref: 9049287028
Ref: library/unittest unittest TestCase setUp9288342
Ref: cd09288342
Ref: library/unittest unittest TestCase tearDown9288726
Ref: cd19288726
Ref: library/unittest unittest TestCase setUpClass9289506
Ref: 24d9289506
Ref: library/unittest unittest TestCase tearDownClass9289949
Ref: cce9289949
Ref: library/unittest unittest TestCase run9290401
Ref: ac39290401
Ref: library/unittest unittest TestCase skipTest9291025
Ref: 33359291025
Ref: library/unittest unittest TestCase subTest9291285
Ref: 9059291285
Ref: library/unittest unittest TestCase debug9291844
Ref: 102c9291844
Ref: library/unittest assert-methods9292085
Ref: 331e9292085
Ref: library/unittest unittest TestCase assertEqual9295932
Ref: bba9295932
Ref: library/unittest unittest TestCase assertNotEqual9296780
Ref: bbb9296780
Ref: library/unittest unittest TestCase assertTrue9296965
Ref: bb99296965
Ref: library/unittest unittest TestCase assertFalse9297016
Ref: ccc9297016
Ref: library/unittest unittest TestCase assertIs9297523
Ref: cd49297523
Ref: library/unittest unittest TestCase assertIsNot9297581
Ref: cd59297581
Ref: library/unittest unittest TestCase assertIsNone9297758
Ref: cd29297758
Ref: library/unittest unittest TestCase assertIsNotNone9297811
Ref: cd39297811
Ref: library/unittest unittest TestCase assertIn9297952
Ref: cdd9297952
Ref: library/unittest unittest TestCase assertNotIn9298014
Ref: cde9298014
Ref: library/unittest unittest TestCase assertIsInstance9298170
Ref: cd69298170
Ref: library/unittest unittest TestCase assertNotIsInstance9298231
Ref: cd79298231
Ref: library/unittest unittest TestCase assertRaises9300908
Ref: abf9300908
Ref: library/unittest unittest TestCase assertRaisesRegex9302620
Ref: ac09302620
Ref: library/unittest unittest TestCase assertWarns9303605
Ref: ac19303605
Ref: library/unittest unittest TestCase assertWarnsRegex9305317
Ref: ac29305317
Ref: library/unittest unittest TestCase assertLogs9306259
Ref: 90a9306259
Ref: library/unittest unittest TestCase records9307318
Ref: 33419307318
Ref: library/unittest unittest TestCase output9307458
Ref: 33429307458
Ref: library/unittest unittest TestCase assertAlmostEqual9310778
Ref: bbc9310778
Ref: library/unittest unittest TestCase assertNotAlmostEqual9310882
Ref: bbd9310882
Ref: library/unittest unittest TestCase assertGreater9311940
Ref: cd89311940
Ref: library/unittest unittest TestCase assertGreaterEqual9312003
Ref: cd99312003
Ref: library/unittest unittest TestCase assertLess9312071
Ref: cda9312071
Ref: library/unittest unittest TestCase assertLessEqual9312131
Ref: cdb9312131
Ref: library/unittest unittest TestCase assertRegex9312500
Ref: bb69312500
Ref: library/unittest unittest TestCase assertNotRegex9312559
Ref: 33439312559
Ref: library/unittest unittest TestCase assertCountEqual9313413
Ref: bb49313413
Ref: library/unittest type-specific-methods9314078
Ref: 33409314078
Ref: library/unittest unittest TestCase addTypeEqualityFunc9314396
Ref: ce69314396
Ref: library/unittest unittest TestCase assertMultiLineEqual9317144
Ref: cdc9317144
Ref: library/unittest unittest TestCase assertSequenceEqual9317563
Ref: ce29317563
Ref: library/unittest unittest TestCase assertListEqual9318192
Ref: ce09318192
Ref: library/unittest unittest TestCase assertTupleEqual9318257
Ref: ce19318257
Ref: library/unittest unittest TestCase assertSetEqual9318709
Ref: cdf9318709
Ref: library/unittest unittest TestCase assertDictEqual9319165
Ref: ce39319165
Ref: library/unittest other-methods-and-attrs9319527
Ref: 33459319527
Ref: library/unittest unittest TestCase fail9319618
Ref: 33469319618
Ref: library/unittest unittest TestCase failureException9319767
Ref: 33449319767
Ref: library/unittest unittest TestCase longMessage9320176
Ref: ccd9320176
Ref: library/unittest unittest TestCase maxDiff9320909
Ref: bb59320909
Ref: library/unittest unittest TestCase countTestCases9321585
Ref: 33479321585
Ref: library/unittest unittest TestCase defaultTestResult9321773
Ref: 333f9321773
Ref: library/unittest unittest TestCase id9322209
Ref: 33489322209
Ref: library/unittest unittest TestCase shortDescription9322410
Ref: 33499322410
Ref: library/unittest unittest TestCase addCleanup9323026
Ref: 2a39323026
Ref: library/unittest unittest TestCase doCleanups9323630
Ref: ccf9323630
Ref: library/unittest unittest TestCase addClassCleanup9324272
Ref: 24c9324272
Ref: library/unittest unittest TestCase doClassCleanups9324948
Ref: 334b9324948
Ref: library/unittest unittest IsolatedAsyncioTestCase9325654
Ref: 24e9325654
Ref: library/unittest unittest IsolatedAsyncioTestCase asyncSetUp9325864
Ref: 334c9325864
Ref: library/unittest unittest IsolatedAsyncioTestCase asyncTearDown9326310
Ref: 334d9326310
Ref: library/unittest unittest IsolatedAsyncioTestCase addAsyncCleanup9327162
Ref: 334e9327162
Ref: library/unittest unittest IsolatedAsyncioTestCase run9327326
Ref: 334f9327326
Ref: library/unittest unittest FunctionTestCase9329069
Ref: 33309329069
Node: Deprecated aliases9329581
Ref: library/unittest deprecated-aliases9329646
Ref: bbe9329646
Ref: library/unittest id19329646
Ref: 33509329646
Node: Grouping tests9332739
Ref: library/unittest grouping-tests9332864
Ref: 33519332864
Ref: library/unittest testsuite-objects9332864
Ref: 33529332864
Ref: library/unittest unittest TestSuite9332915
Ref: 6d39332915
Ref: library/unittest unittest TestSuite addTest9333863
Ref: 33539333863
Ref: library/unittest unittest TestSuite addTests9333989
Ref: 33549333989
Ref: library/unittest unittest TestSuite run9334371
Ref: 33559334371
Ref: library/unittest unittest TestSuite debug9334679
Ref: 33569334679
Ref: library/unittest unittest TestSuite countTestCases9334958
Ref: 33579334958
Ref: library/unittest unittest TestSuite __iter__9335128
Ref: 9679335128
Node: Loading and running tests9336572
Ref: library/unittest loading-and-running-tests9336678
Ref: 33589336678
Ref: library/unittest unittest TestLoader9336751
Ref: 7879336751
Ref: library/unittest unittest TestLoader errors9337246
Ref: 7869337246
Ref: library/unittest unittest TestLoader loadTestsFromTestCase9337710
Ref: 335a9337710
Ref: library/unittest unittest TestLoader loadTestsFromModule9338267
Ref: 7859338267
Ref: library/unittest unittest TestLoader loadTestsFromName9339762
Ref: ce49339762
Ref: library/unittest unittest TestLoader loadTestsFromNames9341547
Ref: 335c9341547
Ref: library/unittest unittest TestLoader getTestCaseNames9341838
Ref: 335b9341838
Ref: library/unittest unittest TestLoader discover9342047
Ref: 9099342047
Ref: library/unittest unittest TestLoader testMethodPrefix9344871
Ref: 335d9344871
Ref: library/unittest unittest TestLoader sortTestMethodsUsing9345157
Ref: 335e9345157
Ref: library/unittest unittest TestLoader suiteClass9345368
Ref: ce59345368
Ref: library/unittest unittest TestLoader testNamePatterns9345662
Ref: 335f9345662
Ref: library/unittest unittest TestResult9346371
Ref: ac49346371
Ref: library/unittest unittest TestResult errors9347234
Ref: 33609347234
Ref: library/unittest unittest TestResult failures9347461
Ref: 33619347461
Ref: library/unittest unittest TestResult skipped9347747
Ref: 33629347747
Ref: library/unittest unittest TestResult expectedFailures9347938
Ref: 33639347938
Ref: library/unittest unittest TestResult unexpectedSuccesses9348177
Ref: 33649348177
Ref: library/unittest unittest TestResult shouldStop9348339
Ref: 33659348339
Ref: library/unittest unittest TestResult testsRun9348470
Ref: 33679348470
Ref: library/unittest unittest TestResult buffer9348546
Ref: 33689348546
Ref: library/unittest unittest TestResult failfast9348990
Ref: 336b9348990
Ref: library/unittest unittest TestResult tb_locals9349170
Ref: 336c9349170
Ref: library/unittest unittest TestResult wasSuccessful9349313
Ref: 336d9349313
Ref: library/unittest unittest TestResult stop9349647
Ref: 33669349647
Ref: library/unittest unittest TestResult startTest9350612
Ref: 33699350612
Ref: library/unittest unittest TestResult stopTest9350717
Ref: 336a9350717
Ref: library/unittest unittest TestResult startTestRun9350858
Ref: ce89350858
Ref: library/unittest unittest TestResult stopTestRun9350981
Ref: ce99350981
Ref: library/unittest unittest TestResult addError9351102
Ref: 336f9351102
Ref: library/unittest unittest TestResult addFailure9351575
Ref: 33709351575
Ref: library/unittest unittest TestResult addSuccess9352039
Ref: 33719352039
Ref: library/unittest unittest TestResult addSkip9352187
Ref: 33729352187
Ref: library/unittest unittest TestResult addExpectedFailure9352489
Ref: 33739352489
Ref: library/unittest unittest TestResult addUnexpectedSuccess9352921
Ref: 33749352921
Ref: library/unittest unittest TestResult addSubTest9353233
Ref: 33759353233
Ref: library/unittest unittest TextTestResult9353909
Ref: 334a9353909
Ref: library/unittest unittest defaultTestLoader9354224
Ref: 33599354224
Ref: library/unittest unittest TextTestRunner9354479
Ref: 336e9354479
Ref: library/unittest unittest TextTestRunner _makeResult9356055
Ref: 33779356055
Ref: library/unittest unittest TextTestRunner run9356713
Ref: 33789356713
Ref: library/unittest unittest main9357080
Ref: 9079357080
Node: load_tests Protocol9359921
Ref: library/unittest load-tests-protocol9360002
Ref: 332e9360002
Node: Class and Module Fixtures9362663
Ref: library/unittest class-and-module-fixtures9362810
Ref: 333e9362810
Node: setUpClass and tearDownClass9364698
Ref: library/unittest setupclass-and-teardownclass9364827
Ref: 33799364827
Node: setUpModule and tearDownModule9365741
Ref: library/unittest setupmodule-and-teardownmodule9365870
Ref: 337a9365870
Ref: library/unittest unittest addModuleCleanup9366483
Ref: 24b9366483
Ref: library/unittest unittest doModuleCleanups9367057
Ref: 337b9367057
Node: Signal Handling9367666
Ref: library/unittest signal-handling9367783
Ref: 33269367783
Ref: library/unittest unittest installHandler9369015
Ref: 337c9369015
Ref: library/unittest unittest registerResult9369258
Ref: 337d9369258
Ref: library/unittest unittest removeResult9369750
Ref: 337e9369750
Ref: library/unittest unittest removeHandler9369970
Ref: cca9369970
Node: unittest mock --- mock object library9370358
Ref: library/unittest mock doc9370526
Ref: 337f9370526
Ref: library/unittest mock module-unittest mock9370526
Ref: 11d9370526
Ref: library/unittest mock unittest-mock-mock-object-library9370526
Ref: 33809370526
Ref: unittest mock --- mock object library-Footnote-19372086
Ref: unittest mock --- mock object library-Footnote-29372158
Node: Quick Guide9372196
Ref: library/unittest mock quick-guide9372304
Ref: 33819372304
Node: The Mock Class9377678
Ref: library/unittest mock the-mock-class9377807
Ref: 33859377807
Ref: library/unittest mock unittest mock Mock9378835
Ref: 24a9378835
Ref: library/unittest mock unittest mock Mock assert_called9382258
Ref: 5ad9382258
Ref: library/unittest mock unittest mock Mock assert_called_once9382552
Ref: 5ae9382552
Ref: library/unittest mock unittest mock Mock assert_called_with9383152
Ref: 10049383152
Ref: library/unittest mock unittest mock Mock assert_called_once_with9383542
Ref: 338c9383542
Ref: library/unittest mock unittest mock Mock assert_any_call9384157
Ref: 338d9384157
Ref: library/unittest mock unittest mock Mock assert_has_calls9384829
Ref: 338e9384829
Ref: library/unittest mock unittest mock Mock assert_not_called9385680
Ref: 7899385680
Ref: library/unittest mock unittest mock Mock reset_mock9386119
Ref: 5af9386119
Ref: library/unittest mock unittest mock Mock mock_add_spec9387254
Ref: 33909387254
Ref: library/unittest mock unittest mock Mock attach_mock9387585
Ref: 33919387585
Ref: library/unittest mock unittest mock Mock configure_mock9387884
Ref: 338b9387884
Ref: library/unittest mock unittest mock Mock __dir__9389124
Ref: 33939389124
Ref: library/unittest mock unittest mock Mock _get_child_mock9389463
Ref: 33959389463
Ref: library/unittest mock unittest mock Mock called9389869
Ref: 33969389869
Ref: library/unittest mock unittest mock Mock call_count9390166
Ref: 33979390166
Ref: library/unittest mock unittest mock Mock return_value9390494
Ref: 338a9390494
Ref: library/unittest mock unittest mock Mock side_effect9391297
Ref: 33889391297
Ref: library/unittest mock unittest mock Mock call_args9393764
Ref: f299393764
Ref: library/unittest mock unittest mock Mock call_args_list9395577
Ref: 33989395577
Ref: library/unittest mock unittest mock Mock method_calls9396615
Ref: 33929396615
Ref: library/unittest mock unittest mock Mock mock_calls9397349
Ref: 338f9397349
Ref: library/unittest mock unittest mock Mock __class__9398885
Ref: 339a9398885
Ref: library/unittest mock unittest mock NonCallableMock9399655
Ref: 33869399655
Ref: library/unittest mock unittest mock PropertyMock9402175
Ref: 339b9402175
Ref: library/unittest mock unittest mock AsyncMock9403550
Ref: 2499403550
Ref: library/unittest mock unittest mock AsyncMock assert_awaited9406405
Ref: 339c9406405
Ref: library/unittest mock unittest mock AsyncMock assert_awaited_once9407146
Ref: 339d9407146
Ref: library/unittest mock unittest mock AsyncMock assert_awaited_with9407717
Ref: 339e9407717
Ref: library/unittest mock unittest mock AsyncMock assert_awaited_once_with9408392
Ref: 339f9408392
Ref: library/unittest mock unittest mock AsyncMock assert_any_await9409123
Ref: 33a09409123
Ref: library/unittest mock unittest mock AsyncMock assert_has_awaits9409772
Ref: 33a19409772
Ref: library/unittest mock unittest mock AsyncMock assert_not_awaited9410871
Ref: 33a29410871
Ref: library/unittest mock unittest mock AsyncMock reset_mock9411052
Ref: 33a39411052
Ref: library/unittest mock unittest mock AsyncMock await_count9411288
Ref: 33a49411288
Ref: library/unittest mock unittest mock AsyncMock await_args9411731
Ref: 33a59411731
Ref: library/unittest mock unittest mock AsyncMock await_args_list9412346
Ref: f289412346
Ref: The Mock Class-Footnote-19413209
Node: Calling9413635
Ref: library/unittest mock calling9413721
Ref: 33a69413721
Node: Deleting Attributes9416962
Ref: library/unittest mock deleting-attributes9417090
Ref: 33a79417090
Ref: library/unittest mock id29417090
Ref: 33a89417090
Node: Mock names and the name attribute9417863
Ref: library/unittest mock mock-names-and-the-name-attribute9418013
Ref: 33a99418013
Node: Attaching Mocks as Attributes9418591
Ref: library/unittest mock attaching-mocks-as-attributes9418713
Ref: 33aa9418713
Node: The patchers9420569
Ref: library/unittest mock the-patchers9420721
Ref: 33ab9420721
Node: patch9421336
Ref: library/unittest mock patch9421411
Ref: 33ac9421411
Ref: library/unittest mock unittest mock patch9421613
Ref: 78d9421613
Node: patch object9430418
Ref: library/unittest mock patch-object9430512
Ref: 33ae9430512
Ref: library/unittest mock unittest mock patch object9430557
Ref: f649430557
Node: patch dict9432029
Ref: library/unittest mock patch-dict9432132
Ref: 33af9432132
Ref: library/unittest mock unittest mock patch dict9432175
Ref: fd49432175
Node: patch multiple9436277
Ref: library/unittest mock patch-multiple9436396
Ref: 33b19436396
Ref: library/unittest mock unittest mock patch multiple9436447
Ref: 33b29436447
Node: patch methods start and stop9439153
Ref: library/unittest mock patch-methods-start-and-stop9439276
Ref: 33b39439276
Ref: library/unittest mock start-and-stop9439276
Ref: 33b49439276
Ref: library/unittest mock unittest mock patch stopall9442006
Ref: 33b59442006
Node: patch builtins9442113
Ref: library/unittest mock id49442233
Ref: 33b69442233
Ref: library/unittest mock patch-builtins9442233
Ref: 33b79442233
Node: TEST_PREFIX9442554
Ref: library/unittest mock id59442670
Ref: 33b89442670
Ref: library/unittest mock test-prefix9442670
Ref: 33b09442670
Node: Nesting Patch Decorators9443553
Ref: library/unittest mock nesting-patch-decorators9443669
Ref: 33b99443669
Node: Where to patch9444586
Ref: library/unittest mock id69444729
Ref: 33ad9444729
Ref: library/unittest mock where-to-patch9444729
Ref: 33829444729
Node: Patching Descriptors and Proxy Objects9446495
Ref: library/unittest mock patching-descriptors-and-proxy-objects9446605
Ref: 33ba9446605
Ref: Patching Descriptors and Proxy Objects-Footnote-19447046
Node: MagicMock and magic method support9447128
Ref: library/unittest mock magicmock-and-magic-method-support9447273
Ref: 33bb9447273
Node: Mocking Magic Methods9447415
Ref: library/unittest mock magic-methods9447526
Ref: 33839447526
Ref: library/unittest mock mocking-magic-methods9447526
Ref: 33bc9447526
Ref: Mocking Magic Methods-Footnote-19451404
Ref: Mocking Magic Methods-Footnote-29451647
Node: Magic Mock9451772
Ref: library/unittest mock magic-mock9451883
Ref: 33bd9451883
Ref: library/unittest mock unittest mock MagicMock9452027
Ref: 78a9452027
Ref: library/unittest mock unittest mock NonCallableMagicMock9452495
Ref: 33879452495
Node: Helpers9455866
Ref: library/unittest mock helpers9455990
Ref: 33be9455990
Node: sentinel9456163
Ref: library/unittest mock sentinel9456231
Ref: 33bf9456231
Ref: library/unittest mock unittest mock sentinel9456270
Ref: 40f9456270
Node: DEFAULT9457431
Ref: library/unittest mock default9457512
Ref: 33c09457512
Ref: library/unittest mock unittest mock DEFAULT9457549
Ref: 33899457549
Node: call9457802
Ref: library/unittest mock call9457890
Ref: 33c19457890
Ref: library/unittest mock unittest mock call9457921
Ref: f7f9457921
Ref: library/unittest mock unittest mock call call_list9458457
Ref: 33c29458457
Ref: library/unittest mock calls-as-tuples9459411
Ref: 33999459411
Node: create_autospec9461031
Ref: library/unittest mock create-autospec9461115
Ref: 33c39461115
Ref: library/unittest mock unittest mock create_autospec9461168
Ref: f4e9461168
Node: ANY9462454
Ref: library/unittest mock any9462544
Ref: 33c49462544
Ref: library/unittest mock unittest mock ANY9462573
Ref: 33c59462573
Node: FILTER_DIR9463454
Ref: library/unittest mock filter-dir9463538
Ref: 33c69463538
Ref: library/unittest mock unittest mock FILTER_DIR9463581
Ref: 33949463581
Node: mock_open9465634
Ref: library/unittest mock mock-open9465727
Ref: 33c79465727
Ref: library/unittest mock unittest mock mock_open9465768
Ref: fcc9465768
Ref: mock_open-Footnote-19468551
Node: Autospeccing9468576
Ref: library/unittest mock auto-speccing9468672
Ref: 33849468672
Ref: library/unittest mock autospeccing9468672
Ref: 33c89468672
Ref: Autospeccing-Footnote-19478171
Node: Sealing mocks9478416
Ref: library/unittest mock sealing-mocks9478494
Ref: 33c99478494
Ref: library/unittest mock unittest mock seal9478543
Ref: 4109478543
Node: unittest mock --- getting started9479351
Ref: library/unittest mock-examples doc9479540
Ref: 33ca9479540
Ref: library/unittest mock-examples unittest-mock-getting-started9479540
Ref: 33cb9479540
Ref: library/unittest mock-examples getting-started9479648
Ref: 33cc9479648
Node: Using Mock9479715
Ref: library/unittest mock-examples using-mock9479820
Ref: 33cd9479820
Node: Mock Patching Methods9480236
Ref: library/unittest mock-examples mock-patching-methods9480347
Ref: 33ce9480347
Node: Mock for Method Calls on an Object9481899
Ref: library/unittest mock-examples mock-for-method-calls-on-an-object9482034
Ref: 33cf9482034
Node: Mocking Classes9483135
Ref: library/unittest mock-examples mocking-classes9483266
Ref: 33d09483266
Node: Naming your mocks9484259
Ref: library/unittest mock-examples naming-your-mocks9484374
Ref: 33d19484374
Node: Tracking all Calls9484806
Ref: library/unittest mock-examples tracking-all-calls9484942
Ref: 33d29484942
Node: Setting Return Values and Attributes9486348
Ref: library/unittest mock-examples setting-return-values-and-attributes9486496
Ref: 33d39486496
Node: Raising exceptions with mocks9488002
Ref: library/unittest mock-examples raising-exceptions-with-mocks9488167
Ref: 33d49488167
Node: Side effect functions and iterables9488547
Ref: library/unittest mock-examples side-effect-functions-and-iterables9488706
Ref: 33d59488706
Node: Mocking asynchronous iterators9489746
Ref: library/unittest mock-examples mocking-asynchronous-iterators9489912
Ref: 33d69489912
Node: Mocking asynchronous context manager9490485
Ref: library/unittest mock-examples mocking-asynchronous-context-manager9490655
Ref: 33d79490655
Node: Creating a Mock from an Existing Object9491557
Ref: library/unittest mock-examples creating-a-mock-from-an-existing-object9491688
Ref: 33d89491688
Node: Patch Decorators9493498
Ref: library/unittest mock-examples patch-decorators9493628
Ref: 33d99493628
Node: Further Examples9498890
Ref: library/unittest mock-examples further-examples9499001
Ref: 33da9499001
Ref: library/unittest mock-examples id19499001
Ref: 33db9499001
Node: Mocking chained calls9499629
Ref: library/unittest mock-examples mocking-chained-calls9499727
Ref: 33dc9499727
Node: Partial mocking9502838
Ref: library/unittest mock-examples partial-mocking9502971
Ref: 33dd9502971
Ref: Partial mocking-Footnote-19504979
Node: Mocking a Generator Method9505080
Ref: library/unittest mock-examples mocking-a-generator-method9505236
Ref: 33de9505236
Ref: Mocking a Generator Method-Footnote-19506362
Node: Applying the same patch to every test method9506686
Ref: library/unittest mock-examples applying-the-same-patch-to-every-test-method9506850
Ref: 33df9506850
Node: Mocking Unbound Methods9509164
Ref: library/unittest mock-examples mocking-unbound-methods9509335
Ref: 33e09509335
Node: Checking multiple calls with mock9511103
Ref: library/unittest mock-examples checking-multiple-calls-with-mock9511259
Ref: 33e19511259
Node: Coping with mutable arguments9512802
Ref: library/unittest mock-examples coping-with-mutable-arguments9512950
Ref: 33e29512950
Node: Nesting Patches9517110
Ref: library/unittest mock-examples nesting-patches9517260
Ref: 33e39517260
Node: Mocking a dictionary with MagicMock9519067
Ref: library/unittest mock-examples mocking-a-dictionary-with-magicmock9519224
Ref: 33e49519224
Node: Mock subclasses and their attributes9521872
Ref: library/unittest mock-examples mock-subclasses-and-their-attributes9522045
Ref: 33e59522045
Ref: Mock subclasses and their attributes-Footnote-19524177
Ref: Mock subclasses and their attributes-Footnote-29524350
Ref: Mock subclasses and their attributes-Footnote-39524408
Node: Mocking imports with patch dict9524495
Ref: library/unittest mock-examples mocking-imports-with-patch-dict9524689
Ref: 33e69524689
Node: Tracking order of calls and less verbose call assertions9527329
Ref: library/unittest mock-examples tracking-order-of-calls-and-less-verbose-call-assertions9527517
Ref: 33e79527517
Node: More complex argument matching9530855
Ref: library/unittest mock-examples more-complex-argument-matching9531003
Ref: 33e89531003
Ref: More complex argument matching-Footnote-19534052
Ref: More complex argument matching-Footnote-29534095
Node: 2to3 - 自動將 Python 2的程式碼轉成 Python 39534217
Ref: library/2to3 doc9534413
Ref: 33e99534413
Ref: library/2to3 to3-automated-python-2-to-3-code-translation9534413
Ref: 33ea9534413
Ref: library/2to3 to3-reference9534413
Ref: c7b9534413
Node: 使用 2to39535076
Ref: library/2to3 to3-using9535191
Ref: 33eb9535191
Ref: library/2to3 using-2to39535191
Ref: 33ec9535191
Node: Fixers9539440
Ref: library/2to3 fixers9539588
Ref: 33ee9539588
Ref: library/2to3 to3-fixers9539588
Ref: 33ed9539588
Ref: library/2to3 2to3fixer-apply9539839
Ref: 33ef9539839
Ref: library/2to3 2to3fixer-asserts9540005
Ref: 33f09540005
Ref: library/2to3 2to3fixer-basestring9542272
Ref: 33f19542272
Ref: library/2to3 2to3fixer-buffer9542350
Ref: 33f29542350
Ref: library/2to3 2to3fixer-dict9542561
Ref: 33f39542561
Ref: library/2to3 2to3fixer-except9543173
Ref: 33f49543173
Ref: library/2to3 2to3fixer-exec9543253
Ref: 33f59543253
Ref: library/2to3 2to3fixer-execfile9543350
Ref: 10289543350
Ref: library/2to3 2to3fixer-exitfunc9543547
Ref: 33f69543547
Ref: library/2to3 2to3fixer-filter9543663
Ref: 33f79543663
Ref: library/2to3 2to3fixer-funcattrs9543753
Ref: 33f89543753
Ref: library/2to3 2to3fixer-future9543937
Ref: 33f99543937
Ref: library/2to3 2to3fixer-getcwdu9544027
Ref: 33fa9544027
Ref: library/2to3 2to3fixer-has_key9544111
Ref: 33fb9544111
Ref: library/2to3 2to3fixer-idioms9544195
Ref: 33fc9544195
Ref: library/2to3 2to3fixer-import9544729
Ref: 33fd9544729
Ref: library/2to3 2to3fixer-imports9544821
Ref: 33fe9544821
Ref: library/2to3 2to3fixer-imports29544899
Ref: 33ff9544899
Ref: library/2to3 2to3fixer-input9545086
Ref: 34009545086
Ref: library/2to3 2to3fixer-intern9545173
Ref: 34019545173
Ref: library/2to3 2to3fixer-isinstance9545254
Ref: 34029545254
Ref: library/2to3 2to3fixer-itertools_imports9545556
Ref: 34039545556
Ref: library/2to3 2to3fixer-itertools9545804
Ref: 34049545804
Ref: library/2to3 2to3fixer-long9546059
Ref: 34059546059
Ref: library/2to3 2to3fixer-map9546124
Ref: 34069546124
Ref: library/2to3 2to3fixer-metaclass9546332
Ref: 34079546332
Ref: library/2to3 2to3fixer-methodattrs9546494
Ref: 34089546494
Ref: library/2to3 2to3fixer-ne9546637
Ref: 34099546637
Ref: library/2to3 2to3fixer-next9546720
Ref: 340a9546720
Ref: library/2to3 2to3fixer-nonzero9546917
Ref: 340b9546917
Ref: library/2to3 2to3fixer-numliterals9547001
Ref: 340c9547001
Ref: library/2to3 2to3fixer-operator9547080
Ref: 340d9547080
Ref: library/2to3 2to3fixer-paren9548765
Ref: 340e9548765
Ref: library/2to3 2to3fixer-print9548946
Ref: 340f9548946
Ref: library/2to3 2to3fixer-raise9549046
Ref: 34109549046
Ref: library/2to3 2to3fixer-raw_input9549325
Ref: 34119549325
Ref: library/2to3 2to3fixer-reduce9549407
Ref: 34129549407
Ref: library/2to3 2to3fixer-reload9549505
Ref: 10389549505
Ref: library/2to3 2to3fixer-renames9549592
Ref: 34139549592
Ref: library/2to3 2to3fixer-repr9549674
Ref: 34149549674
Ref: library/2to3 2to3fixer-set_literal9549762
Ref: 34159549762
Ref: library/2to3 2to3fixer-standarderror9549892
Ref: 34169549892
Ref: library/2to3 2to3fixer-sys_exc9549981
Ref: 34179549981
Ref: library/2to3 2to3fixer-throw9550138
Ref: 34189550138
Ref: library/2to3 2to3fixer-tuple_params9550226
Ref: 34199550226
Ref: library/2to3 2to3fixer-types9550351
Ref: 341a9550351
Ref: library/2to3 2to3fixer-unicode9550468
Ref: 341b9550468
Ref: library/2to3 2to3fixer-urllib9550539
Ref: 341c9550539
Ref: library/2to3 2to3fixer-ws_comma9550667
Ref: 341d9550667
Ref: library/2to3 2to3fixer-xrange9550782
Ref: 341e9550782
Ref: library/2to3 2to3fixer-xreadlines9550929
Ref: 341f9550929
Ref: library/2to3 2to3fixer-zip9551027
Ref: 34209551027
Node: lib2to3 - 2to3's library9551186
Ref: library/2to3 lib2to3-2to3-s-library9551314
Ref: 34219551314
Ref: library/2to3 module-lib2to39551314
Ref: a89551314
Ref: lib2to3 - 2to3's library-Footnote-19551647
Node: test --- Regression tests package for Python9551711
Ref: library/test doc9551926
Ref: 34229551926
Ref: library/test module-test9551926
Ref: 1069551926
Ref: library/test test-regression-tests-package-for-python9551926
Ref: 34239551926
Node: Writing Unit Tests for the test package9553353
Ref: library/test writing-tests9553528
Ref: 34249553528
Ref: library/test writing-unit-tests-for-the-test-package9553528
Ref: 34259553528
Node: Running tests using the command-line interface9558068
Ref: library/test regrtest9558243
Ref: 9329558243
Ref: library/test running-tests-using-the-command-line-interface9558243
Ref: 34269558243
Node: test support --- Utilities for the Python test suite9560181
Ref: library/test module-test support9560415
Ref: 1079560415
Ref: library/test test-support-utilities-for-the-python-test-suite9560415
Ref: 34279560415
Ref: library/test test support TestFailed9560925
Ref: 34289560925
Ref: library/test test support ResourceDenied9561142
Ref: 34299561142
Ref: library/test test support verbose9561433
Ref: 342b9561433
Ref: library/test test support is_jython9561649
Ref: 342c9561649
Ref: library/test test support is_android9561738
Ref: 342d9561738
Ref: library/test test support unix_shell9561816
Ref: 342e9561816
Ref: library/test test support FS_NONASCII9561913
Ref: 342f9561913
Ref: library/test test support TESTFN9562016
Ref: 34309562016
Ref: library/test test support TESTFN_UNICODE9562206
Ref: 34319562206
Ref: library/test test support TESTFN_ENCODING9562297
Ref: 34329562297
Ref: library/test test support TESTFN_UNENCODABLE9562390
Ref: 34339562390
Ref: library/test test support TESTFN_UNDECODABLE9562630
Ref: 34349562630
Ref: library/test test support TESTFN_NONASCII9562872
Ref: 34359562872
Ref: library/test test support IPV6_ENABLED9562992
Ref: 34369562992
Ref: library/test test support SAVEDCWD9563109
Ref: 34379563109
Ref: library/test test support PGO9563179
Ref: 34389563179
Ref: library/test test support PIPE_MAX_SIZE9563277
Ref: 34399563277
Ref: library/test test support SOCK_MAX_SIZE9563425
Ref: 343a9563425
Ref: library/test test support TEST_SUPPORT_DIR9563575
Ref: 343b9563575
Ref: library/test test support TEST_HOME_DIR9563697
Ref: 343c9563697
Ref: library/test test support TEST_DATA_DIR9563794
Ref: 343d9563794
Ref: library/test test support MAX_Py_ssize_t9563895
Ref: 343e9563895
Ref: library/test test support max_memuse9563993
Ref: 343f9563993
Ref: library/test test support real_max_memuse9564156
Ref: 34419564156
Ref: library/test test support MISSING_C_DOCSTRINGS9564328
Ref: 34429564328
Ref: library/test test support HAVE_DOCSTRINGS9564496
Ref: 34439564496
Ref: library/test test support TEST_HTTP_URL9564576
Ref: 34449564576
Ref: library/test test support ALWAYS_EQ9564685
Ref: 34459564685
Ref: library/test test support LARGEST9564801
Ref: 34469564801
Ref: library/test test support SMALLEST9564935
Ref: 34479564935
Ref: library/test test support forget9565137
Ref: 34489565137
Ref: library/test test support unload9565306
Ref: 34499565306
Ref: library/test test support unlink9565390
Ref: 344a9565390
Ref: library/test test support rmdir9565593
Ref: 344b9565593
Ref: library/test test support rmtree9565794
Ref: 344c9565794
Ref: library/test test support make_legacy_pyc9566091
Ref: 344d9566091
Ref: library/test test support is_resource_enabled9566424
Ref: 344e9566424
Ref: library/test test support python_is_optimized9566649
Ref: 344f9566649
Ref: library/test test support with_pymalloc9566775
Ref: 34509566775
Ref: library/test test support requires9566862
Ref: 342a9566862
Ref: library/test test support system_must_validate_cert9567227
Ref: 34519567227
Ref: library/test test support sortdict9567372
Ref: 34529567372
Ref: library/test test support findfile9567462
Ref: 34539567462
Ref: library/test test support create_empty_file9567832
Ref: 34549567832
Ref: library/test test support fd_count9567972
Ref: 34559567972
Ref: library/test test support match_test9568059
Ref: 34569568059
Ref: library/test test support set_match_tests9568172
Ref: 34579568172
Ref: library/test test support run_unittest9568285
Ref: 10489568285
Ref: library/test test support run_doctest9568945
Ref: 34589568945
Ref: library/test test support setswitchinterval9569410
Ref: 34599569410
Ref: library/test test support check_impl_detail9569634
Ref: 345a9569634
Ref: library/test test support check_warnings9570044
Ref: 345b9570044
Ref: library/test test support check_no_resource_warning9573074
Ref: 345e9573074
Ref: library/test test support set_memlimit9573336
Ref: 34409573336
Ref: library/test test support record_original_stdout9573492
Ref: 345f9573492
Ref: library/test test support get_original_stdout9573656
Ref: 34609573656
Ref: library/test test support strip_python_strerr9573827
Ref: 34619573827
Ref: library/test test support args_from_interpreter_flags9574082
Ref: 34629574082
Ref: library/test test support optim_args_from_interpreter_flags9574269
Ref: 34639574269
Ref: library/test test support captured_stdin9574449
Ref: 34649574449
Ref: library/test test support captured_stdout9574492
Ref: 34659574492
Ref: library/test test support captured_stderr9574536
Ref: fd79574536
Ref: library/test test support temp_dir9575259
Ref: 34669575259
Ref: library/test test support change_cwd9575700
Ref: 34679575700
Ref: library/test test support temp_cwd9576057
Ref: 34689576057
Ref: library/test test support temp_umask9576693
Ref: 34699576693
Ref: library/test test support transient_internet9576803
Ref: 346a9576803
Ref: library/test test support disable_faulthandler9577060
Ref: 346b9577060
Ref: library/test test support gc_collect9577192
Ref: 346c9577192
Ref: library/test test support disable_gc9577526
Ref: 346d9577526
Ref: library/test test support swap_attr9577670
Ref: 346e9577670
Ref: library/test test support swap_item9578250
Ref: 346f9578250
Ref: library/test test support wait_threads_exit9578828
Ref: 34709578828
Ref: library/test test support start_threads9578982
Ref: 34719578982
Ref: library/test test support calcobjsize9579136
Ref: 34729579136
Ref: library/test test support calcvobjsize9579306
Ref: 34739579306
Ref: library/test test support checksizeof9579479
Ref: 34749579479
Ref: library/test test support can_symlink9579648
Ref: 34759579648
Ref: library/test test support can_xattr9579771
Ref: 34769579771
Ref: library/test test support skip_unless_symlink9579883
Ref: 34779579883
Ref: library/test test support skip_unless_xattr9580012
Ref: 34789580012
Ref: library/test test support skip_unless_bind_unix_socket9580125
Ref: 34799580125
Ref: library/test test support anticipate_failure9580273
Ref: 347a9580273
Ref: library/test test support run_with_locale9580533
Ref: 347b9580533
Ref: library/test test support run_with_tz9580891
Ref: 347c9580891
Ref: library/test test support requires_freebsd_version9581051
Ref: 347d9581051
Ref: library/test test support requires_linux_version9581283
Ref: 347e9581283
Ref: library/test test support requires_mac_version9581510
Ref: 347f9581510
Ref: library/test test support requires_IEEE_7549581740
Ref: 34809581740
Ref: library/test test support requires_zlib9581847
Ref: 34819581847
Ref: library/test test support requires_gzip9581960
Ref: 34829581960
Ref: library/test test support requires_bz29582072
Ref: 34839582072
Ref: library/test test support requires_lzma9582182
Ref: 34849582182
Ref: library/test test support requires_resource9582294
Ref: 34859582294
Ref: library/test test support requires_docstrings9582417
Ref: 34869582417
Ref: library/test test support cpython_only9582538
Ref: 34879582538
Ref: library/test test support impl_detail9582639
Ref: 34889582639
Ref: library/test test support no_tracing9582867
Ref: 34899582867
Ref: library/test test support refcount_test9582995
Ref: 348a9582995
Ref: library/test test support reap_threads9583304
Ref: 348b9583304
Ref: library/test test support bigmemtest9583433
Ref: 348c9583433
Ref: library/test test support bigaddrspacetest9584178
Ref: 348d9584178
Ref: library/test test support make_bad_fd9584316
Ref: 348e9584316
Ref: library/test test support check_syntax_error9584473
Ref: 348f9584473
Ref: library/test test support check_syntax_warning9585025
Ref: 10089585025
Ref: library/test test support open_urlresource9585822
Ref: 34909585822
Ref: library/test test support import_module9585949
Ref: 34919585949
Ref: library/test test support import_fresh_module9586549
Ref: 34929586549
Ref: library/test test support modules_setup9588146
Ref: 34939588146
Ref: library/test test support modules_cleanup9588236
Ref: 34949588236
Ref: library/test test support threading_setup9588398
Ref: 34959588398
Ref: library/test test support threading_cleanup9588507
Ref: 34969588507
Ref: library/test test support join_thread9588716
Ref: 34979588716
Ref: library/test test support reap_children9588910
Ref: 34989588910
Ref: library/test test support get_attribute9589182
Ref: 34999589182
Ref: library/test test support bind_port9589342
Ref: 349a9589342
Ref: library/test test support bind_unix_socket9590270
Ref: 349b9590270
Ref: library/test test support catch_threading_exception9590437
Ref: fa89590437
Ref: library/test test support catch_unraisable_exception9591367
Ref: fb69591367
Ref: library/test test support find_unused_port9592249
Ref: 349c9592249
Ref: library/test test support load_package_tests9593555
Ref: 349d9593555
Ref: library/test test support fs_is_case_insensitive9594183
Ref: 349e9594183
Ref: library/test test support detect_api_mismatch9594329
Ref: 349f9594329
Ref: library/test test support patch9594794
Ref: 34a09594794
Ref: library/test test support run_in_subinterp9595128
Ref: 34a19595128
Ref: library/test test support check_free_after_iterating9595295
Ref: 34a29595295
Ref: library/test test support missing_compiler_executable9595442
Ref: 34a39595442
Ref: library/test test support check__all__9595762
Ref: 34a49595762
Ref: library/test test support TransientResource9597618
Ref: 34a59597618
Ref: library/test test support EnvironmentVarGuard9598075
Ref: 34a69598075
Ref: library/test test support EnvironmentVarGuard set9598525
Ref: 34a79598525
Ref: library/test test support EnvironmentVarGuard unset9598678
Ref: 34a89598678
Ref: library/test test support SuppressCrashReport9598795
Ref: 34a99598795
Ref: library/test test support CleanImport9599298
Ref: 34ac9599298
Ref: library/test test support DirsOnSysPath9599658
Ref: 34ad9599658
Ref: library/test test support SaveSignals9600150
Ref: 34ae9600150
Ref: library/test test support Matcher9600282
Ref: 34af9600282
Ref: library/test test support Matcher matches9600316
Ref: 34b09600316
Ref: library/test test support Matcher match_value9600435
Ref: 34b19600435
Ref: library/test test support WarningsRecorder9600580
Ref: 34b29600580
Ref: library/test test support BasicTestRunner9600756
Ref: 34b39600756
Ref: library/test test support BasicTestRunner run9600798
Ref: 34b49600798
Ref: library/test test support TestHandler9600878
Ref: 34b59600878
Ref: library/test test support FakePath9600985
Ref: 34b69600985
Ref: test support --- Utilities for the Python test suite-Footnote-19601269
Ref: test support --- Utilities for the Python test suite-Footnote-29601318
Ref: test support --- Utilities for the Python test suite-Footnote-39601367
Node: test support script_helper --- Utilities for the Python execution tests9601447
Ref: library/test module-test support script_helper9601628
Ref: 1089601628
Ref: library/test test-support-script-helper-utilities-for-the-python-execution-tests9601628
Ref: 34b79601628
Ref: library/test test support script_helper interpreter_requires_environment9601902
Ref: 34b89601902
Ref: library/test test support script_helper run_python_until_end9602865
Ref: 34b99602865
Ref: library/test test support script_helper assert_python_ok9603149
Ref: 34ba9603149
Ref: library/test test support script_helper assert_python_failure9603661
Ref: 34bb9603661
Ref: library/test test support script_helper spawn_python9604001
Ref: 34bc9604001
Ref: library/test test support script_helper kill_python9604312
Ref: 34bd9604312
Ref: library/test test support script_helper make_script9604466
Ref: 34be9604466
Ref: library/test test support script_helper make_zip_script9604773
Ref: 34bf9604773
Ref: library/test test support script_helper make_pkg9605140
Ref: 34c09605140
Ref: library/test test support script_helper make_zip_pkg9605331
Ref: 34c19605331
Node: Debugging and Profiling9605986
Ref: library/debug doc9606136
Ref: 34c29606136
Ref: library/debug debugging-and-profiling9606136
Ref: 34c39606136
Ref: library/audit_events audit-events9606594
Ref: 34c49606594
Node: Audit events table9607150
Ref: library/audit_events doc9607263
Ref: 34c59607263
Ref: library/audit_events audit-events-table9607263
Ref: 34c69607263
Ref: Audit events table-Footnote-19660403
Node: bdb --- Debugger framework9660452
Ref: library/bdb doc9660616
Ref: 34eb9660616
Ref: library/bdb bdb-debugger-framework9660616
Ref: 34ec9660616
Ref: library/bdb module-bdb9660616
Ref: f9660616
Ref: library/bdb bdb BdbQuit9660951
Ref: 34ed9660951
Ref: library/bdb bdb Breakpoint9661112
Ref: 34ee9661112
Ref: library/bdb bdb Breakpoint deleteMe9661981
Ref: 34ef9661981
Ref: library/bdb bdb Breakpoint enable9662203
Ref: 34f09662203
Ref: library/bdb bdb Breakpoint disable9662280
Ref: 34f19662280
Ref: library/bdb bdb Breakpoint bpformat9662359
Ref: 34f29662359
Ref: library/bdb bdb Breakpoint bpprint9662797
Ref: 34f39662797
Ref: library/bdb bdb Bdb9662968
Ref: c9d9662968
Ref: library/bdb bdb Bdb canonic9663752
Ref: 34f49663752
Ref: library/bdb bdb Bdb reset9664016
Ref: 34f59664016
Ref: library/bdb bdb Bdb trace_dispatch9664197
Ref: 34f69664197
Ref: library/bdb bdb Bdb dispatch_line9665621
Ref: 34f79665621
Ref: library/bdb bdb Bdb dispatch_call9666101
Ref: 34f99666101
Ref: library/bdb bdb Bdb dispatch_return9666588
Ref: 34fb9666588
Ref: library/bdb bdb Bdb dispatch_exception9667083
Ref: 34fd9667083
Ref: library/bdb bdb Bdb stop_here9667745
Ref: 34ff9667745
Ref: library/bdb bdb Bdb break_here9667962
Ref: 35009667962
Ref: library/bdb bdb Bdb break_anywhere9668238
Ref: 35019668238
Ref: library/bdb bdb Bdb user_call9668486
Ref: 34fa9668486
Ref: library/bdb bdb Bdb user_line9668729
Ref: 34f89668729
Ref: library/bdb bdb Bdb user_return9668943
Ref: 34fc9668943
Ref: library/bdb bdb Bdb user_exception9669129
Ref: 34fe9669129
Ref: library/bdb bdb Bdb do_clear9669317
Ref: 35029669317
Ref: library/bdb bdb Bdb set_step9669608
Ref: 35039669608
Ref: library/bdb bdb Bdb set_next9669684
Ref: 35049669684
Ref: library/bdb bdb Bdb set_return9669787
Ref: 35059669787
Ref: library/bdb bdb Bdb set_until9669883
Ref: 35069669883
Ref: library/bdb bdb Bdb set_trace9670060
Ref: 35079670060
Ref: library/bdb bdb Bdb set_continue9670225
Ref: 35089670225
Ref: library/bdb bdb Bdb set_quit9670404
Ref: 35099670404
Ref: library/bdb bdb Bdb set_break9670828
Ref: 350a9670828
Ref: library/bdb bdb Bdb clear_break9671185
Ref: 350b9671185
Ref: library/bdb bdb Bdb clear_bpbynumber9671361
Ref: 350c9671361
Ref: library/bdb bdb Bdb clear_all_file_breaks9671590
Ref: 350d9671590
Ref: library/bdb bdb Bdb clear_all_breaks9671755
Ref: 350e9671755
Ref: library/bdb bdb Bdb get_bpbynumber9671843
Ref: 350f9671843
Ref: library/bdb bdb Bdb get_break9672196
Ref: 35109672196
Ref: library/bdb bdb Bdb get_breaks9672319
Ref: 35119672319
Ref: library/bdb bdb Bdb get_file_breaks9672479
Ref: 35129672479
Ref: library/bdb bdb Bdb get_all_breaks9672623
Ref: 35139672623
Ref: library/bdb bdb Bdb get_stack9672835
Ref: 35149672835
Ref: library/bdb bdb Bdb format_stack_entry9673007
Ref: 35159673007
Ref: library/bdb bdb Bdb run9673600
Ref: 35169673600
Ref: library/bdb bdb Bdb runeval9673836
Ref: 35179673836
Ref: library/bdb bdb Bdb runctx9674070
Ref: 35189674070
Ref: library/bdb bdb Bdb runcall9674212
Ref: 2a09674212
Ref: library/bdb bdb checkfuncname9674384
Ref: 35199674384
Ref: library/bdb bdb effective9674820
Ref: 351a9674820
Ref: library/bdb bdb set_trace9675137
Ref: 351b9675137
Ref: bdb --- Debugger framework-Footnote-19675285
Node: faulthandler --- Dump the Python traceback9675347
Ref: library/faulthandler doc9675520
Ref: 351c9675520
Ref: library/faulthandler faulthandler-dump-the-python-traceback9675520
Ref: 351d9675520
Ref: library/faulthandler module-faulthandler9675520
Ref: 7d9675520
Node: Dumping the traceback9677560
Ref: library/faulthandler dumping-the-traceback9677688
Ref: 351e9677688
Ref: library/faulthandler faulthandler dump_traceback9677751
Ref: 6dd9677751
Node: Fault handler state9678047
Ref: library/faulthandler fault-handler-state9678222
Ref: 351f9678222
Ref: library/faulthandler faulthandler enable9678281
Ref: 54d9678281
Ref: library/faulthandler faulthandler disable9678951
Ref: 35219678951
Ref: library/faulthandler faulthandler is_enabled9679090
Ref: 35229679090
Node: Dumping the tracebacks after a timeout9679175
Ref: library/faulthandler dumping-the-tracebacks-after-a-timeout9679367
Ref: 35239679367
Ref: library/faulthandler faulthandler dump_traceback_later9679464
Ref: 6de9679464
Ref: library/faulthandler faulthandler cancel_dump_traceback_later9680476
Ref: 35249680476
Node: Dumping the traceback on a user signal9680598
Ref: library/faulthandler dumping-the-traceback-on-a-user-signal9680798
Ref: 35259680798
Ref: library/faulthandler faulthandler register9680895
Ref: 6dc9680895
Ref: library/faulthandler faulthandler unregister9681515
Ref: 35269681515
Node: Issue with file descriptors9681788
Ref: library/faulthandler faulthandler-fd9681961
Ref: 35209681961
Ref: library/faulthandler issue-with-file-descriptors9681961
Ref: 35279681961
Node: Example<15>9682429
Ref: library/faulthandler example9682555
Ref: 35289682555
Node: pdb --- The Python Debugger9683101
Ref: library/pdb doc9683268
Ref: 35299683268
Ref: library/pdb debugger9683268
Ref: 352a9683268
Ref: library/pdb module-pdb9683268
Ref: ca9683268
Ref: library/pdb pdb-the-python-debugger9683268
Ref: 352b9683268
Ref: library/pdb pdb run9686463
Ref: 33109686463
Ref: library/pdb pdb runeval9687153
Ref: 35309687153
Ref: library/pdb pdb runcall9687462
Ref: 35319687462
Ref: library/pdb pdb set_trace9687775
Ref: 3c79687775
Ref: library/pdb pdb post_mortem9688180
Ref: d4a9688180
Ref: library/pdb pdb pm9688469
Ref: 35329688469
Ref: library/pdb pdb Pdb9688811
Ref: 5719688811
Ref: library/pdb pdb Pdb run9690165
Ref: 35349690165
Ref: library/pdb pdb Pdb runeval9690231
Ref: 35359690231
Ref: library/pdb pdb Pdb runcall9690302
Ref: 35369690302
Ref: library/pdb pdb Pdb set_trace9690359
Ref: 35379690359
Ref: pdb --- The Python Debugger-Footnote-19690532
Ref: pdb --- The Python Debugger-Footnote-29690594
Node: Debugger Commands9690727
Ref: library/pdb debugger-commands9690808
Ref: 352c9690808
Ref: library/pdb id29690808
Ref: 35389690808
Ref: library/pdb pdbcommand-help9693074
Ref: 353b9693074
Ref: library/pdb pdbcommand-where9693467
Ref: 353c9693467
Ref: library/pdb pdbcommand-down9693657
Ref: 353d9693657
Ref: library/pdb pdbcommand-up9693796
Ref: 353e9693796
Ref: library/pdb pdbcommand-break9693932
Ref: 353f9693932
Ref: library/pdb pdbcommand-tbreak9694814
Ref: 35409694814
Ref: library/pdb pdbcommand-clear9695025
Ref: 35419695025
Ref: library/pdb pdbcommand-disable9695333
Ref: 35429695333
Ref: library/pdb pdbcommand-enable9695658
Ref: 35439695658
Ref: library/pdb pdbcommand-ignore9695748
Ref: 35449695748
Ref: library/pdb pdbcommand-condition9696141
Ref: 35459696141
Ref: library/pdb pdbcommand-commands9696434
Ref: 35469696434
Ref: library/pdb pdbcommand-step9698069
Ref: 352e9698069
Ref: library/pdb pdbcommand-next9698254
Ref: 352f9698254
Ref: library/pdb pdbcommand-until9698652
Ref: 354a9698652
Ref: library/pdb pdbcommand-return9699040
Ref: 35479699040
Ref: library/pdb pdbcommand-continue9699127
Ref: 352d9699127
Ref: library/pdb pdbcommand-jump9699227
Ref: 35489699227
Ref: library/pdb pdbcommand-list9699657
Ref: 35399699657
Ref: library/pdb pdbcommand-ll9700393
Ref: 354b9700393
Ref: library/pdb pdbcommand-args9700569
Ref: 354c9700569
Ref: library/pdb pdbcommand-p9700648
Ref: 88c9700648
Ref: library/pdb pdbcommand-pp9700919
Ref: 354d9700919
Ref: library/pdb pdbcommand-whatis9701082
Ref: 354e9701082
Ref: library/pdb pdbcommand-source9701159
Ref: 354f9701159
Ref: library/pdb pdbcommand-display9701284
Ref: 35509701284
Ref: library/pdb pdbcommand-undisplay9701539
Ref: 35519701539
Ref: library/pdb pdbcommand-interact9701753
Ref: 35529701753
Ref: library/pdb debugger-aliases9701980
Ref: 353a9701980
Ref: library/pdb pdbcommand-alias9701980
Ref: 35539701980
Ref: library/pdb pdbcommand-unalias9703077
Ref: 35549703077
Ref: library/pdb pdbcommand-!9703141
Ref: 35559703141
Ref: library/pdb pdbcommand-run9703583
Ref: 35569703583
Ref: library/pdb pdbcommand-restart9703614
Ref: 35579703614
Ref: library/pdb pdbcommand-quit9703953
Ref: 35499703953
Ref: library/pdb pdbcommand-debug9704047
Ref: 35589704047
Ref: library/pdb pdbcommand-retval9704246
Ref: 35599704246
Node: The Python Profilers9704347
Ref: library/profile doc9704528
Ref: 355a9704528
Ref: library/profile profile9704528
Ref: 355b9704528
Ref: library/profile the-python-profilers9704528
Ref: 355c9704528
Ref: The Python Profilers-Footnote-19704970
Ref: The Python Profilers-Footnote-29705036
Node: Introduction to the profilers9705101
Ref: library/profile introduction-to-the-profilers9705217
Ref: 355d9705217
Ref: library/profile profiler-introduction9705217
Ref: 355e9705217
Node: Instant User's Manual9706705
Ref: library/profile instant-user-s-manual9706867
Ref: 355f9706867
Ref: library/profile profile-instant9706867
Ref: 35609706867
Node: profile and cProfile Module Reference9713034
Ref: library/profile module-cProfile9713182
Ref: 289713182
Ref: library/profile profile-and-cprofile-module-reference9713182
Ref: 35659713182
Ref: library/profile module-profile9713293
Ref: d49713293
Ref: library/profile profile run9713387
Ref: 35669713387
Ref: library/profile profile runctx9714020
Ref: 35679714020
Ref: library/profile profile Profile9714420
Ref: 1bc9714420
Ref: library/profile profile Profile enable9715980
Ref: 35689715980
Ref: library/profile profile Profile disable9716087
Ref: 35699716087
Ref: library/profile profile Profile create_stats9716194
Ref: 356a9716194
Ref: library/profile profile Profile print_stats9716344
Ref: 356b9716344
Ref: library/profile profile Profile dump_stats9716508
Ref: 356c9716508
Ref: library/profile profile Profile run9716621
Ref: 356d9716621
Ref: library/profile profile Profile runctx9716705
Ref: 356e9716705
Ref: library/profile profile Profile runcall9716868
Ref: 29f9716868
Node: The Stats Class9717215
Ref: library/profile profile-stats9717374
Ref: 356f9717374
Ref: library/profile the-stats-class9717374
Ref: 35709717374
Ref: library/profile module-pstats9717506
Ref: d59717506
Ref: library/profile pstats Stats9717508
Ref: 35619717508
Ref: library/profile pstats Stats strip_dirs9718768
Ref: 35639718768
Ref: library/profile pstats Stats add9719592
Ref: 35719719592
Ref: library/profile pstats Stats dump_stats9720091
Ref: 35729720091
Ref: library/profile pstats Stats sort_stats9720478
Ref: 35629720478
Ref: library/profile pstats Stats reverse_order9725839
Ref: 35739725839
Ref: library/profile pstats Stats print_stats9726131
Ref: 35649726131
Ref: library/profile pstats Stats print_callers9727581
Ref: 35749727581
Ref: library/profile pstats Stats print_callees9728703
Ref: 35759728703
Node: What Is Deterministic Profiling?9729090
Ref: library/profile deterministic-profiling9729223
Ref: 35769729223
Ref: library/profile what-is-deterministic-profiling9729223
Ref: 35779729223
Node: Limitations9731017
Ref: library/profile limitations9731146
Ref: 35789731146
Ref: library/profile profile-limitations9731146
Ref: 35799731146
Node: Calibration9733017
Ref: library/profile calibration9733134
Ref: 357a9733134
Ref: library/profile profile-calibration9733134
Ref: 357b9733134
Node: Using a custom timer9734825
Ref: library/profile profile-timers9734922
Ref: 357c9734922
Ref: library/profile using-a-custom-timer9734922
Ref: 357d9734922
Node: timeit --- Measure execution time of small code snippets9737372
Ref: library/timeit doc9737577
Ref: 357e9737577
Ref: library/timeit module-timeit9737577
Ref: 10c9737577
Ref: library/timeit timeit-measure-execution-time-of-small-code-snippets9737577
Ref: 357f9737577
Ref: timeit --- Measure execution time of small code snippets-Footnote-19738308
Node: 基礎範例<2>9738373
Ref: library/timeit basic-examples9738506
Ref: 35829738506
Node: Python Interface9739785
Ref: library/timeit id19739948
Ref: 35849739948
Ref: library/timeit python-interface9739948
Ref: 35819739948
Ref: library/timeit timeit timeit9740069
Ref: 7769740069
Ref: library/timeit timeit repeat9740521
Ref: 35869740521
Ref: library/timeit timeit default_timer9741086
Ref: 35889741086
Ref: library/timeit timeit Timer9741280
Ref: 35859741280
Ref: library/timeit timeit Timer timeit9742719
Ref: 5a19742719
Ref: library/timeit timeit Timer autorange9743836
Ref: 5a09743836
Ref: library/timeit timeit Timer repeat9744568
Ref: 35879744568
Ref: library/timeit timeit Timer print_exc9745832
Ref: 35899745832
Node: 命令執行列介面9746418
Ref: library/timeit command-line-interface9746578
Ref: 358a9746578
Ref: library/timeit timeit-command-line-interface9746578
Ref: 35809746578
Ref: library/timeit cmdoption-timeit-n9746828
Ref: 358b9746828
Ref: library/timeit cmdoption-timeit-r9746912
Ref: 358c9746912
Ref: library/timeit cmdoption-timeit-s9747001
Ref: 358d9747001
Ref: library/timeit cmdoption-timeit-p9747103
Ref: 358e9747103
Ref: library/timeit cmdoption-timeit-u9747320
Ref: 358f9747320
Ref: library/timeit cmdoption-timeit-v9747461
Ref: 35909747461
Ref: library/timeit cmdoption-timeit-h9747559
Ref: 35919747559
Node: Examples<25>9748779
Ref: library/timeit examples9748914
Ref: 35929748914
Ref: library/timeit timeit-examples9748914
Ref: 35839748914
Node: trace --- Trace or track Python statement execution9752131
Ref: library/trace doc9752356
Ref: 35939752356
Ref: library/trace module-trace9752356
Ref: 1139752356
Ref: library/trace trace-trace-or-track-python-statement-execution9752356
Ref: 35949752356
Ref: trace --- Trace or track Python statement execution-Footnote-19753100
Ref: trace --- Trace or track Python statement execution-Footnote-29753164
Node: Command-Line Usage9753205
Ref: library/trace command-line-usage9753342
Ref: 35959753342
Ref: library/trace trace-cli9753342
Ref: 35969753342
Ref: library/trace cmdoption-trace-help9753696
Ref: 35979753696
Ref: library/trace cmdoption-trace-version9753752
Ref: 35989753752
Node: Main options9753972
Ref: library/trace main-options9754057
Ref: 35999754057
Ref: library/trace cmdoption-trace-c9754447
Ref: 359c9754447
Ref: library/trace cmdoption-trace-t9754712
Ref: 359b9754712
Ref: library/trace cmdoption-trace-l9754785
Ref: 359a9754785
Ref: library/trace cmdoption-trace-r9754881
Ref: 35a09754881
Ref: library/trace cmdoption-trace-trackcalls9755085
Ref: 35a19755085
Node: Modifiers9755193
Ref: library/trace modifiers9755294
Ref: 35a29755294
Ref: library/trace cmdoption-trace-f9755333
Ref: 359e9755333
Ref: library/trace cmdoption-trace-coverdir9755498
Ref: 359d9755498
Ref: library/trace cmdoption-trace-m9755694
Ref: 35a39755694
Ref: library/trace cmdoption-trace-s9755828
Ref: 35a49755828
Ref: library/trace cmdoption-trace-no-report9755988
Ref: 359f9755988
Ref: library/trace cmdoption-trace-g9756217
Ref: 35a59756217
Node: Filters9756344
Ref: library/trace filters9756424
Ref: 35a69756424
Ref: library/trace cmdoption-trace-ignore-module9756506
Ref: 35a79756506
Ref: library/trace cmdoption-trace-ignore-dir9756701
Ref: 35a89756701
Node: Programmatic Interface9756910
Ref: library/trace programmatic-interface9757047
Ref: 35a99757047
Ref: library/trace trace-api9757047
Ref: 35aa9757047
Ref: library/trace trace Trace9757112
Ref: 35ab9757112
Ref: library/trace trace Trace run9758024
Ref: 35ac9758024
Ref: library/trace trace Trace runctx9758272
Ref: 35ad9758272
Ref: library/trace trace Trace runfunc9758592
Ref: 2a19758592
Ref: library/trace trace Trace results9758788
Ref: 35ae9758788
Ref: library/trace trace CoverageResults9759103
Ref: 35af9759103
Ref: library/trace trace CoverageResults update9759268
Ref: 35b09759268
Ref: library/trace trace CoverageResults write_results9759392
Ref: 35b19759392
Node: tracemalloc --- Trace memory allocations9760428
Ref: library/tracemalloc doc9760588
Ref: 35b29760588
Ref: library/tracemalloc module-tracemalloc9760588
Ref: 1159760588
Ref: library/tracemalloc tracemalloc-trace-memory-allocations9760588
Ref: 35b39760588
Ref: tracemalloc --- Trace memory allocations-Footnote-19761926
Node: Examples<26>9761996
Ref: library/tracemalloc examples9762097
Ref: 35b49762097
Node: Display the top 109762246
Ref: library/tracemalloc display-the-top-109762341
Ref: 35b59762341
Node: Compute differences9763825
Ref: library/tracemalloc compute-differences9763964
Ref: 35b79763964
Node: Get the traceback of a memory block9766154
Ref: library/tracemalloc get-the-traceback-of-a-memory-block9766285
Ref: 35ba9766285
Node: Pretty top9768917
Ref: library/tracemalloc pretty-top9769020
Ref: 35bb9769020
Node: API9771407
Ref: library/tracemalloc api9771508
Ref: 35bc9771508
Node: Functions<9>9771679
Ref: library/tracemalloc functions9771752
Ref: 35bd9771752
Ref: library/tracemalloc tracemalloc clear_traces9771791
Ref: 35be9771791
Ref: library/tracemalloc tracemalloc get_object_traceback9771924
Ref: 116b9771924
Ref: library/tracemalloc tracemalloc get_traceback_limit9772329
Ref: 35c19772329
Ref: library/tracemalloc tracemalloc get_traced_memory9772651
Ref: 35c29772651
Ref: library/tracemalloc tracemalloc get_tracemalloc_memory9772855
Ref: 35c39772855
Ref: library/tracemalloc tracemalloc is_tracing9773051
Ref: 35c49773051
Ref: library/tracemalloc tracemalloc start9773282
Ref: 13549773282
Ref: library/tracemalloc tracemalloc stop9774480
Ref: 35bf9774480
Ref: library/tracemalloc tracemalloc take_snapshot9774912
Ref: 35c69774912
Node: DomainFilter9775610
Ref: library/tracemalloc domainfilter9775698
Ref: 35c89775698
Ref: library/tracemalloc tracemalloc DomainFilter9775743
Ref: 5a59775743
Ref: library/tracemalloc tracemalloc DomainFilter inclusive9775906
Ref: 35c99775906
Ref: library/tracemalloc tracemalloc DomainFilter domain9776203
Ref: 35ca9776203
Node: Filter9776305
Ref: library/tracemalloc filter9776386
Ref: 35cb9776386
Ref: library/tracemalloc tracemalloc Filter9776419
Ref: 35cc9776419
Ref: library/tracemalloc tracemalloc Filter domain9777249
Ref: 35cd9777249
Ref: library/tracemalloc tracemalloc Filter inclusive9777517
Ref: 35ce9777517
Ref: library/tracemalloc tracemalloc Filter lineno9777946
Ref: 35d09777946
Ref: library/tracemalloc tracemalloc Filter filename_pattern9778095
Ref: 35cf9778095
Ref: library/tracemalloc tracemalloc Filter all_frames9778206
Ref: 35d19778206
Node: Frame9778610
Ref: library/tracemalloc frame9778687
Ref: 35d39778687
Ref: library/tracemalloc tracemalloc Frame9778720
Ref: 35d49778720
Ref: library/tracemalloc tracemalloc Frame filename9778869
Ref: 35d59778869
Ref: library/tracemalloc tracemalloc Frame lineno9778929
Ref: 35d69778929
Node: Snapshot9778990
Ref: library/tracemalloc snapshot9779070
Ref: 35d79779070
Ref: library/tracemalloc tracemalloc Snapshot9779109
Ref: 35c79779109
Ref: library/tracemalloc tracemalloc Snapshot compare_to9779288
Ref: 35c59779288
Ref: library/tracemalloc tracemalloc Snapshot dump9780020
Ref: 35b89780020
Ref: library/tracemalloc tracemalloc Snapshot filter_traces9780162
Ref: 35de9780162
Ref: library/tracemalloc tracemalloc Snapshot load9780836
Ref: 35b99780836
Ref: library/tracemalloc tracemalloc Snapshot statistics9780968
Ref: 35b69780968
Ref: library/tracemalloc tracemalloc Snapshot traceback_limit9782173
Ref: 35d29782173
Ref: library/tracemalloc tracemalloc Snapshot traces9782389
Ref: 35df9782389
Node: Statistic9782681
Ref: library/tracemalloc statistic9782769
Ref: 35e49782769
Ref: library/tracemalloc tracemalloc Statistic9782810
Ref: 35e09782810
Ref: library/tracemalloc tracemalloc Statistic count9783035
Ref: 35dc9783035
Ref: library/tracemalloc tracemalloc Statistic size9783107
Ref: 35e19783107
Ref: library/tracemalloc tracemalloc Statistic traceback9783191
Ref: 35e29783191
Node: StatisticDiff9783320
Ref: library/tracemalloc statisticdiff9783405
Ref: 35e59783405
Ref: library/tracemalloc tracemalloc StatisticDiff9783454
Ref: 35d89783454
Ref: library/tracemalloc tracemalloc StatisticDiff count9783755
Ref: 35e69783755
Ref: library/tracemalloc tracemalloc StatisticDiff count_diff9783926
Ref: 35db9783926
Ref: library/tracemalloc tracemalloc StatisticDiff size9784145
Ref: 35da9784145
Ref: library/tracemalloc tracemalloc StatisticDiff size_diff9784338
Ref: 35d99784338
Ref: library/tracemalloc tracemalloc StatisticDiff traceback9784569
Ref: 35dd9784569
Node: Trace9784700
Ref: library/tracemalloc trace9784785
Ref: 35e79784785
Ref: library/tracemalloc tracemalloc Trace9784818
Ref: 35e39784818
Ref: library/tracemalloc tracemalloc Trace domain9785043
Ref: 35e89785043
Ref: library/tracemalloc tracemalloc Trace size9785318
Ref: 35e99785318
Ref: library/tracemalloc tracemalloc Trace traceback9785399
Ref: 35ea9785399
Node: Traceback9785528
Ref: library/tracemalloc traceback9785591
Ref: 35eb9785591
Ref: library/tracemalloc tracemalloc Traceback9785632
Ref: 4049785632
Ref: library/tracemalloc tracemalloc Traceback format9786345
Ref: 4059786345
Node: 軟體封裝與發布9787434
Ref: library/distribution doc9787595
Ref: 35ed9787595
Ref: library/distribution software-packaging-and-distribution9787595
Ref: 35ee9787595
Ref: 軟體封裝與發布-Footnote-19788318
Node: distutils --- Building and installing Python modules9788343
Ref: library/distutils doc9788507
Ref: 35ef9788507
Ref: library/distutils distutils-building-and-installing-python-modules9788507
Ref: 35f09788507
Ref: library/distutils module-distutils9788507
Ref: 399788507
Ref: distutils --- Building and installing Python modules-Footnote-19790388
Ref: distutils --- Building and installing Python modules-Footnote-29790441
Ref: distutils --- Building and installing Python modules-Footnote-39790470
Node: ensurepip --- Bootstrapping the pip installer9790507
Ref: library/ensurepip doc9790721
Ref: 35f19790721
Ref: library/ensurepip ensurepip-bootstrapping-the-pip-installer9790721
Ref: 35f29790721
Ref: library/ensurepip module-ensurepip9790721
Ref: 7a9790721
Ref: ensurepip --- Bootstrapping the pip installer-Footnote-19792120
Node: Command line interface9792169
Ref: library/ensurepip command-line-interface9792292
Ref: 35f39792292
Node: Module API9794069
Ref: library/ensurepip module-api9794192
Ref: 35f49794192
Ref: library/ensurepip ensurepip version9794299
Ref: 35f59794299
Ref: library/ensurepip ensurepip bootstrap9794457
Ref: 34cd9794457
Node: venv --- Creation of virtual environments9796234
Ref: library/venv doc9796444
Ref: 35f69796444
Ref: library/venv module-venv9796444
Ref: 1269796444
Ref: library/venv venv-creation-of-virtual-environments9796444
Ref: 35f79796444
Ref: venv --- Creation of virtual environments-Footnote-19797365
Ref: venv --- Creation of virtual environments-Footnote-29797426
Ref: venv --- Creation of virtual environments-Footnote-39797475
Node: Creating virtual environments9797598
Ref: library/venv creating-virtual-environments9797720
Ref: 35f89797720
Ref: library/venv venv-def9804678
Ref: 35f99804678
Ref: Creating virtual environments-Footnote-19807643
Ref: Creating virtual environments-Footnote-29807717
Ref: Creating virtual environments-Footnote-39807772
Ref: Creating virtual environments-Footnote-49807817
Ref: Creating virtual environments-Footnote-59807855
Node: API<2>9807904
Ref: library/venv api9808069
Ref: 35fd9808069
Ref: library/venv venv-api9808069
Ref: 7f79808069
Ref: library/venv venv EnvBuilder9808326
Ref: 90d9808326
Ref: library/venv venv EnvBuilder create9810019
Ref: 35fe9810019
Ref: library/venv venv EnvBuilder ensure_directories9811320
Ref: 35ff9811320
Ref: library/venv venv EnvBuilder create_configuration9811780
Ref: 36009811780
Ref: library/venv venv EnvBuilder setup_python9811924
Ref: 36019811924
Ref: library/venv venv EnvBuilder setup_scripts9812296
Ref: 36029812296
Ref: library/venv venv EnvBuilder post_setup9812451
Ref: 36039812451
Ref: library/venv venv EnvBuilder install_scripts9813435
Ref: 36049813435
Ref: library/venv venv create9814707
Ref: 90e9814707
Node: An example of extending EnvBuilder9815126
Ref: library/venv an-example-of-extending-envbuilder9815253
Ref: 36059815253
Ref: An example of extending EnvBuilder-Footnote-19825988
Node: zipapp --- Manage executable Python zip archives9826035
Ref: library/zipapp doc9826191
Ref: 36069826191
Ref: library/zipapp module-zipapp9826191
Ref: 1429826191
Ref: library/zipapp pip9826191
Ref: 36079826191
Ref: library/zipapp zipapp-manage-executable-python-zip-archives9826191
Ref: 36089826191
Ref: zipapp --- Manage executable Python zip archives-Footnote-19826963
Node: Basic Example9827028
Ref: library/zipapp basic-example9827159
Ref: 360b9827159
Node: 命令執行列介面<2>9827563
Ref: library/zipapp command-line-interface9827713
Ref: 360c9827713
Ref: library/zipapp zipapp-command-line-interface9827713
Ref: 36099827713
Ref: library/zipapp cmdoption-zipapp-o9828200
Ref: 360d9828200
Ref: library/zipapp cmdoption-zipapp-p9828703
Ref: 360e9828703
Ref: library/zipapp cmdoption-zipapp-m9828985
Ref: 360f9828985
Ref: library/zipapp cmdoption-zipapp-c9829410
Ref: 36109829410
Ref: library/zipapp cmdoption-zipapp-info9829691
Ref: 36119829691
Ref: library/zipapp cmdoption-zipapp-h9829900
Ref: 36129829900
Node: Python API9829974
Ref: library/zipapp python-api9830123
Ref: 36139830123
Ref: library/zipapp zipapp-python-api9830123
Ref: 360a9830123
Ref: library/zipapp zipapp create_archive9830211
Ref: 4229830211
Ref: library/zipapp zipapp get_interpreter9833978
Ref: 36149833978
Node: Examples<27>9834333
Ref: library/zipapp examples9834484
Ref: 36159834484
Ref: library/zipapp zipapp-examples9834484
Ref: 36169834484
Node: Specifying the Interpreter9835849
Ref: library/zipapp specifying-the-interpreter9836034
Ref: 36179836034
Ref: library/zipapp zipapp-specifying-the-interpreter9836034
Ref: 36189836034
Node: Creating Standalone Applications with zipapp9837241
Ref: library/zipapp creating-standalone-applications-with-zipapp9837455
Ref: 36199837455
Node: Making a Windows executable9839493
Ref: library/zipapp making-a-windows-executable9839617
Ref: 361a9839617
Node: Caveats9842732
Ref: library/zipapp caveats9842856
Ref: 361b9842856
Node: The Python Zip Application Archive Format9844646
Ref: library/zipapp the-python-zip-application-archive-format9844825
Ref: 361c9844825
Node: Python Runtime Services9846716
Ref: library/python doc9846880
Ref: 361d9846880
Ref: library/python python9846880
Ref: 361e9846880
Ref: library/python python-runtime-services9846880
Ref: 361f9846880
Node: sys --- System-specific parameters and functions9848238
Ref: library/sys doc9848421
Ref: 36209848421
Ref: library/sys module-sys9848421
Ref: fe9848421
Ref: library/sys sys-system-specific-parameters-and-functions9848421
Ref: 36219848421
Ref: library/sys sys abiflags9848780
Ref: 2659848780
Ref: library/sys sys addaudithook9849092
Ref: 34c79849092
Ref: library/sys sys argv9850650
Ref: c009850650
Ref: library/sys auditing9851535
Ref: e969851535
Ref: library/sys sys audit9851535
Ref: f2d9851535
Ref: library/sys sys base_exec_prefix9852928
Ref: 35fc9852928
Ref: library/sys sys base_prefix9853572
Ref: 30459853572
Ref: library/sys sys byteorder9854206
Ref: 16269854206
Ref: library/sys sys builtin_module_names9854462
Ref: 36229854462
Ref: library/sys sys call_tracing9854730
Ref: 36239854730
Ref: library/sys sys copyright9854997
Ref: 36249854997
Ref: library/sys sys _clear_type_cache9855105
Ref: 36259855105
Ref: library/sys sys _current_frames9855429
Ref: da09855429
Ref: library/sys sys breakpointhook9856296
Ref: 3189856296
Ref: library/sys sys _debugmallocstats9858190
Ref: 36269858190
Ref: library/sys sys dllhandle9858612
Ref: 36279858612
Ref: library/sys sys displayhook9858734
Ref: e649858734
Ref: library/sys sys dont_write_bytecode9860250
Ref: 36299860250
Ref: library/sys sys pycache_prefix9860647
Ref: 1579860647
Ref: library/sys sys excepthook9861616
Ref: e689861616
Ref: library/sys sys __breakpointhook__9862938
Ref: 362a9862938
Ref: library/sys sys __displayhook__9862971
Ref: 362b9862971
Ref: library/sys sys __excepthook__9863001
Ref: 362c9863001
Ref: library/sys sys __unraisablehook__9863030
Ref: 362d9863030
Ref: library/sys sys exc_info9863534
Ref: c649863534
Ref: library/sys sys exec_prefix9864747
Ref: 35fb9864747
Ref: library/sys sys executable9865669
Ref: 2759865669
Ref: library/sys sys exit9865970
Ref: ce79865970
Ref: library/sys sys flags9867619
Ref: b419867619
Ref: library/sys sys float_info9870567
Ref: fc69870567
Ref: library/sys sys float_repr_style9875520
Ref: c959875520
Ref: library/sys sys getallocatedblocks9876057
Ref: 8e79876057
Ref: library/sys sys getandroidapilevel9876690
Ref: 3f69876690
Ref: library/sys sys getcheckinterval9876861
Ref: e0d9876861
Ref: library/sys sys getdefaultencoding9877063
Ref: 36319877063
Ref: library/sys sys getdlopenflags9877204
Ref: e539877204
Ref: library/sys sys getfilesystemencoding9877514
Ref: 4fb9877514
Ref: library/sys sys getfilesystemencodeerrors9878892
Ref: 5999878892
Ref: library/sys sys getrefcount9879291
Ref: 36329879291
Ref: library/sys sys getrecursionlimit9879547
Ref: e7f9879547
Ref: library/sys sys getsizeof9879857
Ref: 35c09879857
Ref: library/sys sys getswitchinterval9880807
Ref: 36309880807
Ref: library/sys sys _getframe9880969
Ref: e699880969
Ref: library/sys sys getprofile9881614
Ref: d4c9881614
Ref: library/sys sys gettrace9881712
Ref: d4d9881712
Ref: library/sys sys getwindowsversion9882148
Ref: 59a9882148
Ref: library/sys sys get_asyncgen_hooks9884659
Ref: 36339884659
Ref: library/sys sys get_coroutine_origin_tracking_depth9885264
Ref: 3f79885264
Ref: library/sys sys hash_info9885612
Ref: 9269885612
Ref: library/sys sys hexversion9887297
Ref: 36359887297
Ref: library/sys sys implementation9888190
Ref: 9af9888190
Ref: library/sys sys int_info9890391
Ref: c269890391
Ref: library/sys sys __interactivehook__9891251
Ref: 8e99891251
Ref: library/sys sys intern9891794
Ref: c739891794
Ref: library/sys sys is_finalizing9892556
Ref: 7679892556
Ref: library/sys sys last_type9892733
Ref: c5f9892733
Ref: library/sys sys last_value9892757
Ref: 36379892757
Ref: library/sys sys last_traceback9892782
Ref: 35339892782
Ref: library/sys sys maxsize9893436
Ref: b489893436
Ref: library/sys sys maxunicode9893652
Ref: 9909893652
Ref: library/sys sys meta_path9894037
Ref: 5eb9894037
Ref: library/sys sys modules9895269
Ref: f2b9895269
Ref: library/sys sys path9895626
Ref: 48d9895626
Ref: library/sys sys path_hooks9896717
Ref: 9619896717
Ref: library/sys sys path_importer_cache9897008
Ref: 4a29897008
Ref: library/sys sys platform9897525
Ref: 2b29897525
Ref: library/sys sys prefix9899925
Ref: 35fa9899925
Ref: library/sys sys ps19900824
Ref: 135b9900824
Ref: library/sys sys ps29900842
Ref: 135c9900842
Ref: library/sys sys setcheckinterval9901318
Ref: 362f9901318
Ref: library/sys sys setdlopenflags9902087
Ref: a6b9902087
Ref: library/sys sys setprofile9902685
Ref: e429902685
Ref: library/sys sys setrecursionlimit9904822
Ref: e809904822
Ref: library/sys sys setswitchinterval9905598
Ref: bf09905598
Ref: library/sys sys settrace9906167
Ref: e439906167
Ref: library/sys sys set_asyncgen_hooks9910690
Ref: f2e9910690
Ref: library/sys sys set_coroutine_origin_tracking_depth9911790
Ref: 3f89911790
Ref: library/sys sys _enablelegacywindowsfsencoding9912603
Ref: 4fd9912603
Ref: library/sys sys stdin9913065
Ref: 3129913065
Ref: library/sys sys stdout9913085
Ref: 3139913085
Ref: library/sys sys stderr9913106
Ref: 3149913106
Ref: library/sys sys __stdin__9915999
Ref: 36399915999
Ref: library/sys sys __stdout__9916023
Ref: 1ca29916023
Ref: library/sys sys __stderr__9916048
Ref: 363a9916048
Ref: library/sys sys thread_info9917015
Ref: aa79917015
Ref: library/sys sys tracebacklimit9918464
Ref: 363b9918464
Ref: library/sys sys unraisablehook9918828
Ref: 22e9918828
Ref: library/sys sys version9920554
Ref: 5d89920554
Ref: library/sys sys api_version9920956
Ref: 363c9920956
Ref: library/sys sys version_info9921144
Ref: b1f9921144
Ref: library/sys sys warnoptions9921756
Ref: 41b9921756
Ref: library/sys sys winver9921975
Ref: 363d9921975
Ref: library/sys sys _xoptions9922413
Ref: 13569922413
Ref: library/sys c999923210
Ref: 362e9923210
Ref: sys --- System-specific parameters and functions-Footnote-19923417
Ref: sys --- System-specific parameters and functions-Footnote-29923466
Ref: sys --- System-specific parameters and functions-Footnote-39923515
Ref: sys --- System-specific parameters and functions-Footnote-49923564
Ref: sys --- System-specific parameters and functions-Footnote-59923616
Ref: sys --- System-specific parameters and functions-Footnote-69923665
Ref: sys --- System-specific parameters and functions-Footnote-79923714
Ref: sys --- System-specific parameters and functions-Footnote-89923763
Ref: sys --- System-specific parameters and functions-Footnote-99923812
Ref: sys --- System-specific parameters and functions-Footnote-109923861
Ref: sys --- System-specific parameters and functions-Footnote-119923911
Ref: sys --- System-specific parameters and functions-Footnote-129923961
Ref: sys --- System-specific parameters and functions-Footnote-139924011
Ref: sys --- System-specific parameters and functions-Footnote-149924061
Ref: sys --- System-specific parameters and functions-Footnote-159924111
Ref: sys --- System-specific parameters and functions-Footnote-169924191
Ref: sys --- System-specific parameters and functions-Footnote-179924241
Ref: sys --- System-specific parameters and functions-Footnote-189924291
Node: sysconfig --- Provide access to Python's configuration information9924341
Ref: library/sysconfig doc9924562
Ref: 363e9924562
Ref: library/sysconfig module-sysconfig9924562
Ref: ff9924562
Ref: library/sysconfig sysconfig-provide-access-to-python-s-configuration-information9924562
Ref: 363f9924562
Ref: sysconfig --- Provide access to Python's configuration information-Footnote-19925202
Node: Configuration variables9925270
Ref: library/sysconfig configuration-variables9925423
Ref: 36409925423
Ref: library/sysconfig sysconfig get_config_vars9925916
Ref: 96a9925916
Ref: library/sysconfig sysconfig get_config_var9926285
Ref: 9699926285
Node: Installation paths9926726
Ref: library/sysconfig installation-paths9926906
Ref: 36419926906
Ref: library/sysconfig sysconfig get_scheme_names9928881
Ref: 36429928881
Ref: library/sysconfig sysconfig get_path_names9929017
Ref: 36439929017
Ref: library/sysconfig sysconfig get_path9929154
Ref: cc39929154
Ref: library/sysconfig sysconfig get_paths9930361
Ref: bde9930361
Node: Other functions<3>9930982
Ref: library/sysconfig other-functions9931166
Ref: 36449931166
Ref: library/sysconfig sysconfig get_python_version9931217
Ref: bdd9931217
Ref: library/sysconfig sysconfig get_platform9931386
Ref: bdc9931386
Ref: library/sysconfig sysconfig is_python_build9932390
Ref: cc49932390
Ref: library/sysconfig sysconfig parse_config_h9932679
Ref: 36459932679
Ref: library/sysconfig sysconfig get_config_h_filename9933071
Ref: 36469933071
Ref: library/sysconfig sysconfig get_makefile_filename9933162
Ref: 36479933162
Node: Using sysconfig as a script9933251
Ref: library/sysconfig using-sysconfig-as-a-script9933408
Ref: 36489933408
Node: builtins --- Built-in objects9934481
Ref: library/builtins doc9934695
Ref: 36499934695
Ref: library/builtins builtins-built-in-objects9934695
Ref: 364a9934695
Ref: library/builtins module-builtins9934695
Ref: 139934695
Node: __main__ --- Top-level script environment9936184
Ref: library/__main__ doc9936360
Ref: 364b9936360
Ref: library/__main__ main-top-level-script-environment9936360
Ref: 364c9936360
Ref: library/__main__ module-__main__9936360
Ref: 19936360
Node: warnings --- Warning control9937254
Ref: library/warnings doc9937429
Ref: 364d9937429
Ref: library/warnings module-warnings9937429
Ref: 1279937429
Ref: library/warnings warnings-warning-control9937429
Ref: 364e9937429
Ref: warnings --- Warning control-Footnote-19939733
Node: Warning Categories9939800
Ref: library/warnings id19939911
Ref: 36529939911
Ref: library/warnings warning-categories9939911
Ref: 171e9939911
Node: The Warnings Filter9943879
Ref: library/warnings the-warnings-filter9944031
Ref: 36539944031
Ref: library/warnings warning-filter9944031
Ref: 13519944031
Node: Describing Warning Filters9946762
Ref: library/warnings describing-warning-filters9946875
Ref: 13529946875
Ref: library/warnings id29946875
Ref: 36549946875
Node: Default Warning Filter9948671
Ref: library/warnings default-warning-filter9948822
Ref: 36559948822
Ref: library/warnings id39948822
Ref: 36569948822
Node: Overriding the default filter9949882
Ref: library/warnings overriding-the-default-filter9949998
Ref: 36579949998
Ref: library/warnings warning-disable9949998
Ref: 36589949998
Node: Temporarily Suppressing Warnings9951433
Ref: library/warnings temporarily-suppressing-warnings9951583
Ref: 36599951583
Ref: library/warnings warning-suppress9951583
Ref: 365a9951583
Node: Testing Warnings9952601
Ref: library/warnings testing-warnings9952778
Ref: 365b9952778
Ref: library/warnings warning-testing9952778
Ref: 365c9952778
Node: Updating Code For New Versions of Dependencies9954842
Ref: library/warnings updating-code-for-new-versions-of-dependencies9955006
Ref: 365d9955006
Ref: library/warnings warning-ignored9955006
Ref: 33769955006
Node: Available Functions9956392
Ref: library/warnings available-functions9956566
Ref: 365e9956566
Ref: library/warnings warning-functions9956566
Ref: 365f9956566
Ref: library/warnings warnings warn9956625
Ref: e5d9956625
Ref: library/warnings warnings warn_explicit9957834
Ref: 5b59957834
Ref: library/warnings warnings showwarning9959001
Ref: 36519959001
Ref: library/warnings warnings formatwarning9959637
Ref: ff79959637
Ref: library/warnings warnings filterwarnings9960066
Ref: e0c9960066
Ref: library/warnings warnings simplefilter9960741
Ref: 345d9960741
Ref: library/warnings warnings resetwarnings9961175
Ref: 36509961175
Node: Available Context Managers9961441
Ref: library/warnings available-context-managers9961560
Ref: 36609961560
Ref: library/warnings warnings catch_warnings9961635
Ref: 345c9961635
Node: dataclasses --- Data Classes9962887
Ref: library/dataclasses doc9963073
Ref: 36619963073
Ref: library/dataclasses dataclasses-data-classes9963073
Ref: 36629963073
Ref: library/dataclasses module-dataclasses9963073
Ref: 309963073
Ref: dataclasses --- Data Classes-Footnote-19964734
Ref: dataclasses --- Data Classes-Footnote-29964804
Ref: dataclasses --- Data Classes-Footnote-39964853
Node: Module-level decorators classes and functions9964902
Ref: library/dataclasses module-level-decorators-classes-and-functions9965041
Ref: 36649965041
Ref: library/dataclasses dataclasses dataclass9965156
Ref: 3429965156
Ref: library/dataclasses dataclasses field9972122
Ref: 10039972122
Ref: library/dataclasses dataclasses Field9976386
Ref: 36659976386
Ref: library/dataclasses dataclasses fields9977180
Ref: 36669977180
Ref: library/dataclasses dataclasses asdict9977557
Ref: 36679977557
Ref: library/dataclasses dataclasses astuple9978353
Ref: 36689978353
Ref: library/dataclasses dataclasses make_dataclass9978887
Ref: 36699978887
Ref: library/dataclasses dataclasses replace9980410
Ref: e9d9980410
Ref: library/dataclasses dataclasses is_dataclass9981823
Ref: 366a9981823
Node: Post-init processing9982276
Ref: library/dataclasses post-init-processing9982439
Ref: 366b9982439
Node: Class variables9983439
Ref: library/dataclasses class-variables9983576
Ref: 366c9983576
Ref: Class variables-Footnote-19984126
Node: Init-only variables9984175
Ref: library/dataclasses init-only-variables9984308
Ref: 366d9984308
Node: Frozen instances9985519
Ref: library/dataclasses frozen-instances9985651
Ref: 366e9985651
Node: Inheritance<2>9986252
Ref: library/dataclasses inheritance9986390
Ref: 36709986390
Node: Default factory functions9987442
Ref: library/dataclasses default-factory-functions9987586
Ref: 36719987586
Node: Mutable default values9988264
Ref: library/dataclasses mutable-default-values9988408
Ref: 36729988408
Node: Exceptions<15>9990302
Ref: library/dataclasses exceptions9990412
Ref: 36739990412
Ref: library/dataclasses dataclasses FrozenInstanceError9990453
Ref: 366f9990453
Node: contextlib --- Utilities for with-statement contexts9990724
Ref: library/contextlib doc9990911
Ref: 36749990911
Ref: library/contextlib contextlib-utilities-for-with-statement-contexts9990911
Ref: 36759990911
Ref: library/contextlib module-contextlib9990911
Ref: 249990911
Ref: contextlib --- Utilities for with-statement contexts-Footnote-19991573
Node: Utilities9991642
Ref: library/contextlib utilities9991772
Ref: 36769991772
Ref: library/contextlib contextlib AbstractContextManager9991844
Ref: 5399991844
Ref: library/contextlib contextlib AbstractAsyncContextManager9992329
Ref: 37d9992329
Ref: library/contextlib contextlib contextmanager9992835
Ref: b839992835
Ref: library/contextlib contextlib asynccontextmanager9995786
Ref: 37c9995786
Ref: library/contextlib contextlib closing9996792
Ref: 36779996792
Ref: library/contextlib simplifying-support-for-single-optional-context-managers9997585
Ref: 36789997585
Ref: library/contextlib contextlib nullcontext9997585
Ref: 37a9997585
Ref: library/contextlib contextlib suppress9998693
Ref: 8319998693
Ref: library/contextlib contextlib redirect_stdout9999794
Ref: 6c79999794
Ref: library/contextlib contextlib redirect_stderr10001126
Ref: 6c610001126
Ref: library/contextlib contextlib ContextDecorator10001384
Ref: b8210001384
Ref: library/contextlib contextlib ExitStack10003779
Ref: 37b10003779
Ref: library/contextlib contextlib ExitStack enter_context10005644
Ref: 367a10005644
Ref: library/contextlib contextlib ExitStack push10006082
Ref: 367b10006082
Ref: library/contextlib contextlib ExitStack callback10006976
Ref: 2a610006976
Ref: library/contextlib contextlib ExitStack pop_all10007435
Ref: 367c10007435
Ref: library/contextlib contextlib ExitStack close10008489
Ref: 367d10008489
Ref: library/contextlib contextlib AsyncExitStack10008783
Ref: 37e10008783
Ref: library/contextlib contextlib AsyncExitStack enter_async_context10009145
Ref: 367f10009145
Ref: library/contextlib contextlib AsyncExitStack push_async_exit10009293
Ref: 368010009293
Ref: library/contextlib contextlib AsyncExitStack push_async_callback10009461
Ref: 2a710009461
Ref: library/contextlib contextlib AsyncExitStack aclose10009604
Ref: 367e10009604
Node: Examples and Recipes<2>10010182
Ref: library/contextlib examples-and-recipes10010371
Ref: 368110010371
Node: Supporting a variable number of context managers10010819
Ref: library/contextlib supporting-a-variable-number-of-context-managers10010978
Ref: 368210010978
Node: Catching exceptions from __enter__ methods10012020
Ref: library/contextlib catching-exceptions-from-enter-methods10012230
Ref: 368310012230
Node: Cleaning up in an __enter__ implementation10013378
Ref: library/contextlib cleaning-up-in-an-enter-implementation10013591
Ref: 368410013591
Node: Replacing any use of try-finally and flag variables10015494
Ref: library/contextlib replacing-any-use-of-try-finally-and-flag-variables10015712
Ref: 368510015712
Node: Using a context manager as a function decorator10018227
Ref: library/contextlib using-a-context-manager-as-a-function-decorator10018394
Ref: 368610018394
Ref: Using a context manager as a function decorator-Footnote-110020223
Node: Single use reusable and reentrant context managers10020272
Ref: library/contextlib single-use-reusable-and-reentrant-cms10020443
Ref: 83310020443
Ref: library/contextlib single-use-reusable-and-reentrant-context-managers10020443
Ref: 368710020443
Node: Reentrant context managers10021980
Ref: library/contextlib reentrant-cms10022127
Ref: 367910022127
Ref: library/contextlib reentrant-context-managers10022127
Ref: 368810022127
Node: Reusable context managers10023639
Ref: library/contextlib reusable-cms10023786
Ref: 368910023786
Ref: library/contextlib reusable-context-managers10023786
Ref: 368a10023786
Node: abc --- Abstract Base Classes10026456
Ref: library/abc doc10026639
Ref: 368b10026639
Ref: library/abc abc-abstract-base-classes10026639
Ref: 368c10026639
Ref: library/abc module-abc10026639
Ref: 410026639
Ref: library/abc abc ABC10027604
Ref: 81d10027604
Ref: library/abc abc ABCMeta10028448
Ref: 81e10028448
Ref: library/abc abc ABCMeta register10029225
Ref: 9d610029225
Ref: library/abc abc ABCMeta __subclasshook__10029891
Ref: 368d10029891
Ref: library/abc abc abstractmethod10032794
Ref: 9d310032794
Ref: library/abc abc abstractclassmethod10035890
Ref: 9d410035890
Ref: library/abc abc abstractstaticmethod10036588
Ref: 9d510036588
Ref: library/abc abc abstractproperty10037288
Ref: 9d210037288
Ref: library/abc abc get_cache_token10038659
Ref: 81c10038659
Ref: abc --- Abstract Base Classes-Footnote-110039081
Ref: abc --- Abstract Base Classes-Footnote-210039143
Ref: abc --- Abstract Base Classes-Footnote-310039192
Ref: abc --- Abstract Base Classes-Footnote-410039241
Node: atexit --- Exit handlers10039352
Ref: library/atexit doc10039532
Ref: 368e10039532
Ref: library/atexit atexit-exit-handlers10039532
Ref: 368f10039532
Ref: library/atexit module-atexit10039532
Ref: c10039532
Ref: library/atexit atexit register10040431
Ref: e8a10040431
Ref: library/atexit atexit unregister10041480
Ref: 369010041480
Node: atexit Example10042038
Ref: library/atexit atexit-example10042113
Ref: 369110042113
Ref: library/atexit id110042113
Ref: 369210042113
Node: traceback --- Print or retrieve a stack traceback10043474
Ref: library/traceback doc10043668
Ref: 369310043668
Ref: library/traceback module-traceback10043668
Ref: 11410043668
Ref: library/traceback traceback-print-or-retrieve-a-stack-traceback10043668
Ref: 369410043668
Ref: library/traceback traceback print_tb10044444
Ref: 77e10044444
Ref: library/traceback traceback print_exception10044984
Ref: 20b510044984
Ref: library/traceback traceback print_exc10046122
Ref: 369510046122
Ref: library/traceback traceback print_last10046286
Ref: 369610046286
Ref: library/traceback traceback print_stack10046611
Ref: 77f10046611
Ref: library/traceback traceback extract_tb10047145
Ref: 369710047145
Ref: library/traceback traceback extract_stack10047876
Ref: 369810047876
Ref: library/traceback traceback format_list10048177
Ref: 369910048177
Ref: library/traceback traceback format_exception_only10048684
Ref: 32f210048684
Ref: library/traceback traceback format_exception10049301
Ref: 369a10049301
Ref: library/traceback traceback format_exc10049899
Ref: 369b10049899
Ref: library/traceback traceback format_tb10050057
Ref: 35ec10050057
Ref: library/traceback traceback format_stack10050171
Ref: 369c10050171
Ref: library/traceback traceback clear_frames10050294
Ref: 8f610050294
Ref: library/traceback traceback walk_stack10050499
Ref: 77910050499
Ref: library/traceback traceback walk_tb10050805
Ref: 77a10050805
Ref: traceback --- Print or retrieve a stack traceback-Footnote-110051233
Node: TracebackException Objects10051301
Ref: library/traceback tracebackexception-objects10051442
Ref: 369e10051442
Ref: library/traceback traceback TracebackException10051680
Ref: 77b10051680
Ref: library/traceback traceback TracebackException __cause__10052066
Ref: 369f10052066
Ref: library/traceback traceback TracebackException __context__10052171
Ref: 36a010052171
Ref: library/traceback traceback TracebackException __suppress_context__10052290
Ref: 36a110052290
Ref: library/traceback traceback TracebackException stack10052406
Ref: 36a210052406
Ref: library/traceback traceback TracebackException exc_type10052496
Ref: 36a310052496
Ref: library/traceback traceback TracebackException filename10052571
Ref: 36a410052571
Ref: library/traceback traceback TracebackException lineno10052669
Ref: 36a510052669
Ref: library/traceback traceback TracebackException text10052767
Ref: 36a610052767
Ref: library/traceback traceback TracebackException offset10052856
Ref: 36a710052856
Ref: library/traceback traceback TracebackException msg10052973
Ref: 36a810052973
Ref: library/traceback traceback TracebackException from_exception10053054
Ref: 36a910053054
Ref: library/traceback traceback TracebackException format10053443
Ref: 36aa10053443
Ref: library/traceback traceback TracebackException format_exception_only10053997
Ref: 36ab10053997
Node: StackSummary Objects10054550
Ref: library/traceback stacksummary-objects10054720
Ref: 36ac10054720
Ref: library/traceback traceback StackSummary10054889
Ref: 77c10054889
Ref: library/traceback traceback StackSummary extract10054925
Ref: 369d10054925
Ref: library/traceback traceback StackSummary from_list10055756
Ref: 36ad10055756
Ref: library/traceback traceback StackSummary format10056065
Ref: 36ae10056065
Node: FrameSummary Objects10056682
Ref: library/traceback framesummary-objects10056844
Ref: 36af10056844
Ref: library/traceback traceback FrameSummary10057009
Ref: 77d10057009
Node: Traceback Examples10057755
Ref: library/traceback traceback-example10057888
Ref: 36b010057888
Ref: library/traceback traceback-examples10057888
Ref: 36b110057888
Node: __future__ --- Future statement definitions10063284
Ref: library/__future__ doc10063488
Ref: 36b210063488
Ref: library/__future__ future-future-statement-definitions10063488
Ref: 36b310063488
Ref: library/__future__ module-__future__10063488
Ref: 010063488
Ref: __future__ --- Future statement definitions-Footnote-110068688
Ref: __future__ --- Future statement definitions-Footnote-210068757
Ref: __future__ --- Future statement definitions-Footnote-310068806
Ref: __future__ --- Future statement definitions-Footnote-410068855
Ref: __future__ --- Future statement definitions-Footnote-510068904
Ref: __future__ --- Future statement definitions-Footnote-610068953
Ref: __future__ --- Future statement definitions-Footnote-710069002
Ref: __future__ --- Future statement definitions-Footnote-810069051
Ref: __future__ --- Future statement definitions-Footnote-910069100
Ref: __future__ --- Future statement definitions-Footnote-1010069149
Node: gc --- Garbage Collector interface10069199
Ref: library/gc doc10069386
Ref: 36b410069386
Ref: library/gc gc-garbage-collector-interface10069386
Ref: 36b510069386
Ref: library/gc module-gc10069386
Ref: 8610069386
Ref: library/gc gc enable10070313
Ref: 36b610070313
Ref: library/gc gc disable10070382
Ref: 36b710070382
Ref: library/gc gc isenabled10070453
Ref: 36b810070453
Ref: library/gc gc collect10070542
Ref: 22f10070542
Ref: library/gc gc set_debug10071175
Ref: 36b910071175
Ref: library/gc gc get_debug10071440
Ref: 36ba10071440
Ref: library/gc gc get_objects10071517
Ref: 1ce10071517
Ref: library/gc gc get_stats10071922
Ref: 85310071922
Ref: library/gc gc set_threshold10072612
Ref: 36bb10072612
Ref: library/gc gc get_count10073836
Ref: 36bc10073836
Ref: library/gc gc get_threshold10073959
Ref: 36bd10073959
Ref: library/gc gc get_referrers10074102
Ref: ea910074102
Ref: library/gc gc get_referents10075136
Ref: eaa10075136
Ref: library/gc gc is_tracked10075868
Ref: ca810075868
Ref: library/gc gc freeze10076690
Ref: 39110076690
Ref: library/gc gc unfreeze10077220
Ref: 39210077220
Ref: library/gc gc get_freeze_count10077375
Ref: 39310077375
Ref: library/gc gc garbage10077614
Ref: b4510077614
Ref: library/gc gc callbacks10078457
Ref: a0f10078457
Ref: library/gc gc DEBUG_STATS10079758
Ref: 36c010079758
Ref: library/gc gc DEBUG_COLLECTABLE10079901
Ref: 36c110079901
Ref: library/gc gc DEBUG_UNCOLLECTABLE10079987
Ref: b4610079987
Ref: library/gc gc DEBUG_SAVEALL10080353
Ref: 36bf10080353
Ref: library/gc gc DEBUG_LEAK10080545
Ref: 36c210080545
Ref: gc --- Garbage Collector interface-Footnote-110080789
Ref: gc --- Garbage Collector interface-Footnote-210080878
Node: inspect --- Inspect live objects10080927
Ref: library/inspect doc10081112
Ref: 36c310081112
Ref: library/inspect inspect-inspect-live-objects10081112
Ref: 36c410081112
Ref: library/inspect module-inspect10081112
Ref: a110081112
Ref: inspect --- Inspect live objects-Footnote-110082284
Node: Types and members10082350
Ref: library/inspect inspect-types10082467
Ref: 36c510082467
Ref: library/inspect types-and-members10082467
Ref: 36c610082467
Ref: library/inspect inspect getmembers10096102
Ref: 36c710096102
Ref: library/inspect inspect getmodulename10096714
Ref: 5f710096714
Ref: library/inspect inspect ismodule10097375
Ref: 36ca10097375
Ref: library/inspect inspect isclass10097465
Ref: 36cb10097465
Ref: library/inspect inspect ismethod10097602
Ref: 36cc10097602
Ref: library/inspect inspect isfunction10097716
Ref: 36cd10097716
Ref: library/inspect inspect isgeneratorfunction10097892
Ref: 102310097892
Ref: library/inspect inspect isgenerator10098174
Ref: 36cf10098174
Ref: library/inspect inspect iscoroutinefunction10098270
Ref: 6fd10098270
Ref: library/inspect inspect iscoroutine10098648
Ref: 6fc10098648
Ref: library/inspect inspect isawaitable10098830
Ref: 6fe10098830
Ref: library/inspect inspect isasyncgenfunction10099276
Ref: 102410099276
Ref: library/inspect inspect isasyncgen10099773
Ref: 36d010099773
Ref: library/inspect inspect istraceback10099997
Ref: 36d110099997
Ref: library/inspect inspect isframe10100093
Ref: 36d210100093
Ref: library/inspect inspect iscode10100181
Ref: 36d310100181
Ref: library/inspect inspect isbuiltin10100267
Ref: 36d410100267
Ref: library/inspect inspect isroutine10100401
Ref: 36d510100401
Ref: library/inspect inspect isabstract10100534
Ref: 36d610100534
Ref: library/inspect inspect ismethoddescriptor10100640
Ref: 36d710100640
Ref: library/inspect inspect isdatadescriptor10101521
Ref: 36d810101521
Ref: library/inspect inspect isgetsetdescriptor10102148
Ref: 36d910102148
Ref: library/inspect inspect ismemberdescriptor10102497
Ref: 36da10102497
Node: Retrieving source code10102857
Ref: library/inspect inspect-source10103032
Ref: 36db10103032
Ref: library/inspect retrieving-source-code10103032
Ref: 36dc10103032
Ref: library/inspect inspect getdoc10103099
Ref: 1d710103099
Ref: library/inspect inspect getcomments10103521
Ref: 32b010103521
Ref: library/inspect inspect getfile10103943
Ref: 10a810103943
Ref: library/inspect inspect getmodule10104175
Ref: f2a10104175
Ref: library/inspect inspect getsourcefile10104273
Ref: 36de10104273
Ref: library/inspect inspect getsourcelines10104508
Ref: 36df10104508
Ref: library/inspect inspect getsource10105116
Ref: eda10105116
Ref: library/inspect inspect cleandoc10105555
Ref: 36dd10105555
Node: Introspecting callables with the Signature object10105964
Ref: library/inspect inspect-signature-object10106146
Ref: 36e010106146
Ref: library/inspect introspecting-callables-with-the-signature-object10106146
Ref: 36e110106146
Ref: library/inspect inspect signature10106461
Ref: 56010106461
Ref: library/inspect inspect Signature10107851
Ref: 6f810107851
Ref: library/inspect inspect Signature empty10108865
Ref: 36e410108865
Ref: library/inspect inspect Signature parameters10108982
Ref: 36e210108982
Ref: library/inspect inspect Signature return_annotation10109465
Ref: 36e510109465
Ref: library/inspect inspect Signature bind10109673
Ref: 36e610109673
Ref: library/inspect inspect Signature bind_partial10109956
Ref: 36e710109956
Ref: library/inspect inspect Signature replace10110338
Ref: 36e310110338
Ref: library/inspect inspect Signature from_callable10111047
Ref: 6fb10111047
Ref: library/inspect inspect Parameter10111648
Ref: 6f910111648
Ref: library/inspect inspect Parameter empty10111990
Ref: 36e910111990
Ref: library/inspect inspect Parameter name10112118
Ref: 36ea10112118
Ref: library/inspect inspect Parameter default10112570
Ref: 36eb10112570
Ref: library/inspect inspect Parameter annotation10112758
Ref: 36ec10112758
Ref: library/inspect inspect Parameter kind10112943
Ref: 36ed10112943
Ref: library/inspect inspect Parameter kind description10115764
Ref: 36ee10115764
Ref: library/inspect inspect Parameter replace10116294
Ref: 36e810116294
Ref: library/inspect inspect BoundArguments10117359
Ref: 9ad10117359
Ref: library/inspect inspect BoundArguments arguments10117564
Ref: 36ef10117564
Ref: library/inspect inspect BoundArguments args10118301
Ref: 36f010118301
Ref: library/inspect inspect BoundArguments kwargs10118450
Ref: 36f110118450
Ref: library/inspect inspect BoundArguments signature10118597
Ref: 36f210118597
Ref: library/inspect inspect BoundArguments apply_defaults10118692
Ref: 6fa10118692
Ref: Introspecting callables with the Signature object-Footnote-110119691
Node: Classes and functions<2>10119740
Ref: library/inspect classes-and-functions10119921
Ref: 36f310119921
Ref: library/inspect inspect-classes-functions10119921
Ref: 36f410119921
Ref: library/inspect inspect getclasstree10119986
Ref: 36f510119986
Ref: library/inspect inspect getargspec10120563
Ref: 56110120563
Ref: library/inspect inspect getfullargspec10121489
Ref: 56210121489
Ref: library/inspect inspect getargvalues10123829
Ref: 7bd10123829
Ref: library/inspect inspect formatargspec10124334
Ref: 7bc10124334
Ref: library/inspect inspect formatargvalues10125448
Ref: 7be10125448
Ref: library/inspect inspect getmro10125918
Ref: 36f610125918
Ref: library/inspect inspect getcallargs10126280
Ref: 7bb10126280
Ref: library/inspect inspect getclosurevars10127616
Ref: a1e10127616
Ref: library/inspect inspect unwrap10128328
Ref: 86e10128328
Node: The interpreter stack10129058
Ref: library/inspect inspect-stack10129220
Ref: 36f710129220
Ref: library/inspect the-interpreter-stack10129220
Ref: 36f810129220
Ref: library/inspect inspect getframeinfo10131209
Ref: 36f910131209
Ref: library/inspect inspect getouterframes10131434
Ref: 70310131434
Ref: library/inspect inspect getinnerframes10131914
Ref: 70410131914
Ref: library/inspect inspect currentframe10132391
Ref: 36fa10132391
Ref: library/inspect inspect stack10132790
Ref: 70110132790
Ref: library/inspect inspect trace10133168
Ref: 70210133168
Node: Fetching attributes statically10133630
Ref: library/inspect fetching-attributes-statically10133810
Ref: 36fb10133810
Ref: library/inspect inspect getattr_static10134392
Ref: bd010134392
Node: Current State of Generators and Coroutines10136193
Ref: library/inspect current-state-of-generators-and-coroutines10136374
Ref: 36fc10136374
Ref: library/inspect inspect getgeneratorstate10136803
Ref: bcf10136803
Ref: library/inspect inspect getcoroutinestate10137212
Ref: 70010137212
Ref: library/inspect inspect getgeneratorlocals10138043
Ref: a1f10138043
Ref: library/inspect inspect getcoroutinelocals10138913
Ref: 6ff10138913
Node: Code Objects Bit Flags10139144
Ref: library/inspect code-objects-bit-flags10139320
Ref: 36fd10139320
Ref: library/inspect inspect-module-co-flags10139320
Ref: 36c810139320
Ref: library/inspect inspect CO_OPTIMIZED10139483
Ref: 36fe10139483
Ref: library/inspect inspect CO_NEWLOCALS10139570
Ref: 36ff10139570
Ref: library/inspect inspect CO_VARARGS10139715
Ref: 370010139715
Ref: library/inspect inspect CO_VARKEYWORDS10139823
Ref: 370110139823
Ref: library/inspect inspect CO_NESTED10139935
Ref: 370210139935
Ref: library/inspect inspect CO_GENERATOR10140029
Ref: 370310140029
Ref: library/inspect inspect CO_NOFREE10140204
Ref: 370410140204
Ref: library/inspect inspect CO_COROUTINE10140295
Ref: 370510140295
Ref: library/inspect inspect CO_ITERABLE_COROUTINE10140528
Ref: 370610140528
Ref: library/inspect inspect CO_ASYNC_GENERATOR10140839
Ref: 370710140839
Ref: Code Objects Bit Flags-Footnote-110141484
Ref: Code Objects Bit Flags-Footnote-210141533
Ref: Code Objects Bit Flags-Footnote-310141582
Node: Command Line Interface<3>10141631
Ref: library/inspect command-line-interface10141756
Ref: 370810141756
Ref: library/inspect inspect-module-cli10141756
Ref: 86d10141756
Ref: library/inspect cmdoption-inspect-details10142131
Ref: 370910142131
Node: site --- Site-specific configuration hook10142244
Ref: library/site doc10142386
Ref: 370a10142386
Ref: library/site module-site10142386
Ref: ec10142386
Ref: library/site site-site-specific-configuration-hook10142386
Ref: 370b10142386
Ref: site --- Site-specific configuration hook-Footnote-110148115
Node: Readline configuration10148178
Ref: library/site readline-configuration10148305
Ref: 370d10148305
Ref: library/site rlcompleter-config10148305
Ref: 8eb10148305
Node: Module contents<3>10148954
Ref: library/site module-contents10149115
Ref: 370e10149115
Ref: library/site site PREFIXES10149168
Ref: 370f10149168
Ref: library/site site ENABLE_USER_SITE10149249
Ref: 370c10149249
Ref: library/site site USER_SITE10149685
Ref: 134b10149685
Ref: library/site site USER_BASE10150237
Ref: 135d10150237
Ref: library/site site main10150808
Ref: 134c10150808
Ref: library/site site addsitedir10151141
Ref: 371010151141
Ref: library/site site getsitepackages10151345
Ref: bd810151345
Ref: library/site site getuserbase10151475
Ref: bd910151475
Ref: library/site site getusersitepackages10151715
Ref: bda10151715
Node: Command Line Interface<4>10152111
Ref: library/site command-line-interface10152241
Ref: 371110152241
Ref: library/site site-commandline10152241
Ref: 371210152241
Ref: library/site cmdoption-site-user-base10152789
Ref: 371310152789
Ref: library/site cmdoption-site-user-site10152869
Ref: 371410152869
Ref: Command Line Interface<4>-Footnote-110153478
Node: Custom Python Interpreters10153527
Ref: library/custominterp doc10153682
Ref: 371510153682
Ref: library/custominterp custom-python-interpreters10153682
Ref: 371610153682
Ref: library/custominterp custominterp10153682
Ref: 371710153682
Node: code --- Interpreter base classes10154324
Ref: library/code doc10154459
Ref: 371810154459
Ref: library/code code-interpreter-base-classes10154459
Ref: 371910154459
Ref: library/code module-code10154459
Ref: 1b10154459
Ref: library/code code InteractiveInterpreter10154877
Ref: 371a10154877
Ref: library/code code InteractiveConsole10155391
Ref: 180610155391
Ref: library/code code interact10155702
Ref: 371b10155702
Ref: library/code code compile_command10156450
Ref: 371d10156450
Ref: code --- Interpreter base classes-Footnote-110157734
Node: Interactive Interpreter Objects10157797
Ref: library/code interactive-interpreter-objects10157934
Ref: 371e10157934
Ref: library/code interpreter-objects10157934
Ref: 371f10157934
Ref: library/code code InteractiveInterpreter runsource10158017
Ref: 372010158017
Ref: library/code code InteractiveInterpreter runcode10159310
Ref: 372210159310
Ref: library/code code InteractiveInterpreter showsyntaxerror10159775
Ref: 372110159775
Ref: library/code code InteractiveInterpreter showtraceback10160255
Ref: 6ac10160255
Ref: library/code code InteractiveInterpreter write10160633
Ref: 372310160633
Node: Interactive Console Objects10160859
Ref: library/code console-objects10160996
Ref: 372410160996
Ref: library/code interactive-console-objects10160996
Ref: 372510160996
Ref: library/code code InteractiveConsole interact10161260
Ref: 372610161260
Ref: library/code code InteractiveConsole push10162096
Ref: 372710162096
Ref: library/code code InteractiveConsole resetbuffer10162797
Ref: 372810162797
Ref: library/code code InteractiveConsole raw_input10162912
Ref: 371c10162912
Node: codeop --- Compile Python code10163278
Ref: library/codeop doc10163413
Ref: 372910163413
Ref: library/codeop codeop-compile-python-code10163413
Ref: 372a10163413
Ref: library/codeop module-codeop10163413
Ref: 1d10163413
Ref: library/codeop codeop compile_command10164374
Ref: 372b10164374
Ref: library/codeop codeop Compile10165776
Ref: 372c10165776
Ref: library/codeop codeop CommandCompiler10166178
Ref: 372d10166178
Ref: codeop --- Compile Python code-Footnote-110166597
Node: 匯入模組10166662
Ref: library/modules doc10166818
Ref: 372e10166818
Ref: library/modules importing-modules10166818
Ref: 372f10166818
Ref: library/modules modules10166818
Ref: 373010166818
Node: zipimport --- Import modules from Zip archives10167550
Ref: library/zipimport doc10167691
Ref: 373110167691
Ref: library/zipimport module-zipimport10167691
Ref: 14410167691
Ref: library/zipimport zipimport-import-modules-from-zip-archives10167691
Ref: 373210167691
Ref: library/zipimport zipimport ZipImportError10169784
Ref: 373310169784
Ref: zipimport --- Import modules from Zip archives-Footnote-110170073
Ref: zipimport --- Import modules from Zip archives-Footnote-210170141
Ref: zipimport --- Import modules from Zip archives-Footnote-310170209
Ref: zipimport --- Import modules from Zip archives-Footnote-410170258
Ref: zipimport --- Import modules from Zip archives-Footnote-510170307
Ref: zipimport --- Import modules from Zip archives-Footnote-610170356
Node: zipimporter Objects10170405
Ref: library/zipimport id110170528
Ref: 373410170528
Ref: library/zipimport zipimporter-objects10170528
Ref: 373510170528
Ref: library/zipimport zipimport zipimporter10170651
Ref: 373610170651
Ref: library/zipimport zipimport zipimporter find_module10171123
Ref: 373710171123
Ref: library/zipimport zipimport zipimporter get_code10171553
Ref: 373810171553
Ref: library/zipimport zipimport zipimporter get_data10171737
Ref: 10bf10171737
Ref: library/zipimport zipimport zipimporter get_filename10172006
Ref: 373910172006
Ref: library/zipimport zipimport zipimporter get_source10172270
Ref: 373a10172270
Ref: library/zipimport zipimport zipimporter is_package10172566
Ref: 373b10172566
Ref: library/zipimport zipimport zipimporter load_module10172783
Ref: 373c10172783
Ref: library/zipimport zipimport zipimporter archive10173067
Ref: 373d10173067
Ref: library/zipimport zipimport zipimporter prefix10173197
Ref: 373e10173197
Node: Examples<28>10173601
Ref: library/zipimport examples10173724
Ref: 373f10173724
Ref: library/zipimport zipimport-examples10173724
Ref: 374010173724
Node: pkgutil --- Package extension utility10174404
Ref: library/pkgutil doc10174600
Ref: 374110174600
Ref: library/pkgutil module-pkgutil10174600
Ref: ce10174600
Ref: library/pkgutil pkgutil-package-extension-utility10174600
Ref: 374210174600
Ref: library/pkgutil pkgutil ModuleInfo10174885
Ref: 61210174885
Ref: library/pkgutil pkgutil extend_path10175038
Ref: 374310175038
Ref: library/pkgutil pkgutil ImpImporter10176708
Ref: 374410176708
Ref: library/pkgutil pkgutil ImpLoader10177395
Ref: 374510177395
Ref: library/pkgutil pkgutil find_loader10177712
Ref: 374610177712
Ref: library/pkgutil pkgutil get_importer10178269
Ref: 374710178269
Ref: library/pkgutil pkgutil get_loader10178773
Ref: 374810178773
Ref: library/pkgutil pkgutil iter_importers10179470
Ref: b1910179470
Ref: library/pkgutil pkgutil iter_modules10180158
Ref: 61110180158
Ref: library/pkgutil pkgutil walk_packages10180995
Ref: 49010180995
Ref: library/pkgutil pkgutil get_data10182564
Ref: 374910182564
Ref: pkgutil --- Package extension utility-Footnote-110183732
Ref: pkgutil --- Package extension utility-Footnote-210183798
Ref: pkgutil --- Package extension utility-Footnote-310183847
Ref: pkgutil --- Package extension utility-Footnote-410183896
Ref: pkgutil --- Package extension utility-Footnote-510183945
Ref: pkgutil --- Package extension utility-Footnote-610183994
Ref: pkgutil --- Package extension utility-Footnote-710184043
Ref: pkgutil --- Package extension utility-Footnote-810184092
Ref: pkgutil --- Package extension utility-Footnote-910184141
Ref: pkgutil --- Package extension utility-Footnote-1010184190
Ref: pkgutil --- Package extension utility-Footnote-1110184240
Ref: pkgutil --- Package extension utility-Footnote-1210184290
Ref: pkgutil --- Package extension utility-Footnote-1310184340
Ref: pkgutil --- Package extension utility-Footnote-1410184390
Node: modulefinder --- Find modules used by a script10184440
Ref: library/modulefinder doc10184637
Ref: 374b10184637
Ref: library/modulefinder module-modulefinder10184637
Ref: b510184637
Ref: library/modulefinder modulefinder-find-modules-used-by-a-script10184637
Ref: 374c10184637
Ref: library/modulefinder modulefinder AddPackagePath10185155
Ref: 374d10185155
Ref: library/modulefinder modulefinder ReplacePackage10185303
Ref: 374e10185303
Ref: library/modulefinder modulefinder ModuleFinder10185464
Ref: fe510185464
Ref: library/modulefinder modulefinder ModuleFinder report10186124
Ref: 375010186124
Ref: library/modulefinder modulefinder ModuleFinder run_script10186345
Ref: 374f10186345
Ref: library/modulefinder modulefinder ModuleFinder modules10186489
Ref: 375110186489
Ref: modulefinder --- Find modules used by a script-Footnote-110186710
Node: Example usage of ModuleFinder10186781
Ref: library/modulefinder example-usage-of-modulefinder10186893
Ref: 375310186893
Ref: library/modulefinder modulefinder-example10186893
Ref: 375210186893
Node: runpy --- Locating and executing Python modules10188264
Ref: library/runpy doc10188466
Ref: 375410188466
Ref: library/runpy module-runpy10188466
Ref: e310188466
Ref: library/runpy runpy-locating-and-executing-python-modules10188466
Ref: 375510188466
Ref: library/runpy runpy run_module10189501
Ref: 134010189501
Ref: library/runpy runpy run_path10192729
Ref: cb610192729
Ref: runpy --- Locating and executing Python modules-Footnote-110196991
Ref: runpy --- Locating and executing Python modules-Footnote-210197055
Ref: runpy --- Locating and executing Python modules-Footnote-310197104
Ref: runpy --- Locating and executing Python modules-Footnote-410197153
Ref: runpy --- Locating and executing Python modules-Footnote-510197202
Ref: runpy --- Locating and executing Python modules-Footnote-610197251
Ref: runpy --- Locating and executing Python modules-Footnote-710197300
Ref: runpy --- Locating and executing Python modules-Footnote-810197349
Node: importlib --- The implementation of import10197398
Ref: library/importlib doc10197578
Ref: 375610197578
Ref: library/importlib importlib-the-implementation-of-import10197578
Ref: 375710197578
Ref: library/importlib module-importlib10197578
Ref: 9b10197578
Ref: importlib --- The implementation of import-Footnote-110198317
Node: 簡介<11>10198395
Ref: library/importlib introduction10198506
Ref: 375810198506
Ref: 簡介<11>-Footnote-110200325
Ref: 簡介<11>-Footnote-210200377
Ref: 簡介<11>-Footnote-310200426
Ref: 簡介<11>-Footnote-410200475
Ref: 簡介<11>-Footnote-510200524
Ref: 簡介<11>-Footnote-610200573
Ref: 簡介<11>-Footnote-710200622
Ref: 簡介<11>-Footnote-810200671
Ref: 簡介<11>-Footnote-910200720
Ref: 簡介<11>-Footnote-1010200769
Ref: 簡介<11>-Footnote-1110200819
Ref: 簡介<11>-Footnote-1210200869
Ref: 簡介<11>-Footnote-1310200919
Node: Functions<10>10200969
Ref: library/importlib functions10201145
Ref: 375910201145
Ref: library/importlib importlib __import__10201184
Ref: 9b310201184
Ref: library/importlib importlib import_module10201492
Ref: b1810201492
Ref: library/importlib importlib find_loader10202809
Ref: 93c10202809
Ref: library/importlib importlib invalidate_caches10203785
Ref: 4a110203785
Ref: library/importlib importlib reload10204230
Ref: 39e10204230
Node: importlib abc -- Abstract base classes related to import10207449
Ref: library/importlib importlib-abc-abstract-base-classes-related-to-import10207647
Ref: 375a10207647
Ref: library/importlib module-importlib abc10207647
Ref: 9c10207647
Ref: library/importlib importlib abc Finder10208480
Ref: 9ba10208480
Ref: library/importlib importlib abc Finder find_module10208681
Ref: 375b10208681
Ref: library/importlib importlib abc MetaPathFinder10209128
Ref: 9b810209128
Ref: library/importlib importlib abc MetaPathFinder find_spec10209332
Ref: 46810209332
Ref: library/importlib importlib abc MetaPathFinder find_module10210090
Ref: 46710210090
Ref: library/importlib importlib abc MetaPathFinder invalidate_caches10210892
Ref: 375d10210892
Ref: library/importlib importlib abc PathEntryFinder10211298
Ref: 9b910211298
Ref: library/importlib importlib abc PathEntryFinder find_spec10211714
Ref: 46a10211714
Ref: library/importlib importlib abc PathEntryFinder find_loader10212356
Ref: 46910212356
Ref: library/importlib importlib abc PathEntryFinder find_module10213537
Ref: 94010213537
Ref: library/importlib importlib abc PathEntryFinder invalidate_caches10213797
Ref: 375e10213797
Ref: library/importlib importlib abc Loader10214077
Ref: 7c710214077
Ref: library/importlib importlib abc Loader create_module10214488
Ref: 55910214488
Ref: library/importlib importlib abc Loader exec_module10214906
Ref: 5e910214906
Ref: library/importlib importlib abc Loader load_module10215359
Ref: 5e810215359
Ref: library/importlib importlib abc Loader module_repr10218486
Ref: 94610218486
Ref: library/importlib importlib abc ResourceReader10218961
Ref: 34710218961
Ref: library/importlib importlib abc ResourceReader open_resource10220614
Ref: 375f10220614
Ref: library/importlib importlib abc ResourceReader resource_path10220881
Ref: 376010220881
Ref: library/importlib importlib abc ResourceReader is_resource10221123
Ref: 376110221123
Ref: library/importlib importlib abc ResourceReader contents10221343
Ref: 103f10221343
Ref: library/importlib importlib abc ResourceLoader10222217
Ref: 46b10222217
Ref: library/importlib importlib abc ResourceLoader get_data10222578
Ref: 374a10222578
Ref: library/importlib importlib abc InspectLoader10223262
Ref: 86510223262
Ref: library/importlib importlib abc InspectLoader get_code10223447
Ref: 86610223447
Ref: library/importlib importlib abc InspectLoader get_source10224029
Ref: 86a10224029
Ref: library/importlib importlib abc InspectLoader is_package10224608
Ref: 376210224608
Ref: library/importlib importlib abc InspectLoader source_to_code10224976
Ref: 6f410224976
Ref: library/importlib importlib abc InspectLoader exec_module10225611
Ref: 94410225611
Ref: library/importlib importlib abc InspectLoader load_module10225747
Ref: 94110225747
Ref: library/importlib importlib abc ExecutionLoader10225927
Ref: 376310225927
Ref: library/importlib importlib abc ExecutionLoader get_filename10226175
Ref: 376410226175
Ref: library/importlib importlib abc FileLoader10226718
Ref: 9bc10226718
Ref: library/importlib importlib abc FileLoader name10227211
Ref: 376510227211
Ref: library/importlib importlib abc FileLoader path10227291
Ref: 376610227291
Ref: library/importlib importlib abc FileLoader load_module10227357
Ref: 94210227357
Ref: library/importlib importlib abc FileLoader get_filename10227530
Ref: 376710227530
Ref: library/importlib importlib abc FileLoader get_data10227630
Ref: 376810227630
Ref: library/importlib importlib abc SourceLoader10227757
Ref: 376910227757
Ref: library/importlib importlib abc SourceLoader path_stats10228855
Ref: af110228855
Ref: library/importlib importlib abc SourceLoader path_mtime10229628
Ref: af010229628
Ref: library/importlib importlib abc SourceLoader set_data10230154
Ref: 376a10230154
Ref: library/importlib importlib abc SourceLoader get_code10230666
Ref: 376b10230666
Ref: library/importlib importlib abc SourceLoader exec_module10230795
Ref: 94510230795
Ref: library/importlib importlib abc SourceLoader load_module10230940
Ref: 94310230940
Ref: library/importlib importlib abc SourceLoader get_source10231129
Ref: 95e10231129
Ref: library/importlib importlib abc SourceLoader is_package10231262
Ref: 376c10231262
Ref: importlib abc -- Abstract base classes related to import-Footnote-110231707
Ref: importlib abc -- Abstract base classes related to import-Footnote-210231779
Ref: importlib abc -- Abstract base classes related to import-Footnote-310231828
Ref: importlib abc -- Abstract base classes related to import-Footnote-410231877
Ref: importlib abc -- Abstract base classes related to import-Footnote-510231926
Ref: importlib abc -- Abstract base classes related to import-Footnote-610231975
Node: importlib resources -- Resources10232024
Ref: library/importlib importlib-resources-resources10232256
Ref: 376d10232256
Ref: library/importlib module-importlib resources10232256
Ref: 9f10232256
Ref: library/importlib importlib resources Package10233593
Ref: 376e10233593
Ref: library/importlib importlib resources Resource10233948
Ref: 376f10233948
Ref: library/importlib importlib resources open_binary10234185
Ref: 377010234185
Ref: library/importlib importlib resources open_text10234704
Ref: 377110234704
Ref: library/importlib importlib resources read_binary10235415
Ref: 377210235415
Ref: library/importlib importlib resources read_text10235935
Ref: 377310235935
Ref: library/importlib importlib resources path10236636
Ref: eba10236636
Ref: library/importlib importlib resources is_resource10237351
Ref: 377410237351
Ref: library/importlib importlib resources contents10237670
Ref: 103e10237670
Ref: importlib resources -- Resources-Footnote-110238099
Ref: importlib resources -- Resources-Footnote-210238178
Ref: importlib resources -- Resources-Footnote-310238249
Ref: importlib resources -- Resources-Footnote-410238342
Ref: importlib resources -- Resources-Footnote-510238413
Node: importlib machinery -- Importers and path hooks10238489
Ref: library/importlib importlib-machinery-importers-and-path-hooks10238709
Ref: 377510238709
Ref: library/importlib module-importlib machinery10238709
Ref: 9d10238709
Ref: library/importlib importlib machinery SOURCE_SUFFIXES10239040
Ref: 377610239040
Ref: library/importlib importlib machinery DEBUG_BYTECODE_SUFFIXES10239204
Ref: 377710239204
Ref: library/importlib importlib machinery OPTIMIZED_BYTECODE_SUFFIXES10239452
Ref: 377910239452
Ref: library/importlib importlib machinery BYTECODE_SUFFIXES10239700
Ref: 377810239700
Ref: library/importlib importlib machinery EXTENSION_SUFFIXES10239970
Ref: 377a10239970
Ref: library/importlib importlib machinery all_suffixes10240140
Ref: 36c910240140
Ref: library/importlib importlib machinery BuiltinImporter10240570
Ref: 55a10240570
Ref: library/importlib importlib machinery FrozenImporter10241127
Ref: 95c10241127
Ref: library/importlib importlib machinery WindowsRegistryFinder10241534
Ref: 5ea10241534
Ref: library/importlib importlib machinery PathFinder10242005
Ref: 96010242005
Ref: library/importlib importlib machinery PathFinder find_spec10242321
Ref: 93f10242321
Ref: library/importlib importlib machinery PathFinder find_module10243483
Ref: 93e10243483
Ref: library/importlib importlib machinery PathFinder invalidate_caches10243681
Ref: 4a010243681
Ref: library/importlib importlib machinery FileFinder10244276
Ref: 9bb10244276
Ref: library/importlib importlib machinery FileFinder path10245580
Ref: 377b10245580
Ref: library/importlib importlib machinery FileFinder find_spec10245650
Ref: 7c610245650
Ref: library/importlib importlib machinery FileFinder find_loader10245829
Ref: 377c10245829
Ref: library/importlib importlib machinery FileFinder invalidate_caches10245970
Ref: 377d10245970
Ref: library/importlib importlib machinery FileFinder path_hook10246056
Ref: 377e10246056
Ref: library/importlib importlib machinery SourceFileLoader10246508
Ref: 9bd10246508
Ref: library/importlib importlib machinery SourceFileLoader name10246798
Ref: 377f10246798
Ref: library/importlib importlib machinery SourceFileLoader path10246885
Ref: 378010246885
Ref: library/importlib importlib machinery SourceFileLoader is_package10246948
Ref: 378110246948
Ref: library/importlib importlib machinery SourceFileLoader path_stats10247083
Ref: 378210247083
Ref: library/importlib importlib machinery SourceFileLoader set_data10247225
Ref: 378310247225
Ref: library/importlib importlib machinery SourceFileLoader load_module10247370
Ref: 5e610247370
Ref: library/importlib importlib machinery SourcelessFileLoader10247686
Ref: 9be10247686
Ref: library/importlib importlib machinery SourcelessFileLoader name10248156
Ref: 378410248156
Ref: library/importlib importlib machinery SourcelessFileLoader path10248237
Ref: 378510248237
Ref: library/importlib importlib machinery SourcelessFileLoader is_package10248302
Ref: 378610248302
Ref: library/importlib importlib machinery SourcelessFileLoader get_code10248434
Ref: 378710248434
Ref: library/importlib importlib machinery SourcelessFileLoader get_source10248576
Ref: 378810248576
Ref: library/importlib importlib machinery SourcelessFileLoader load_module10248721
Ref: 5e710248721
Ref: library/importlib importlib machinery ExtensionFileLoader10249012
Ref: 55b10249012
Ref: library/importlib importlib machinery ExtensionFileLoader name10249378
Ref: 378910249378
Ref: library/importlib importlib machinery ExtensionFileLoader path10249452
Ref: 378a10249452
Ref: library/importlib importlib machinery ExtensionFileLoader create_module10249516
Ref: 378b10249516
Ref: library/importlib importlib machinery ExtensionFileLoader exec_module10249697
Ref: 378c10249697
Ref: library/importlib importlib machinery ExtensionFileLoader is_package10249859
Ref: 378d10249859
Ref: library/importlib importlib machinery ExtensionFileLoader get_code10250049
Ref: 378e10250049
Ref: library/importlib importlib machinery ExtensionFileLoader get_source10250164
Ref: 378f10250164
Ref: library/importlib importlib machinery ExtensionFileLoader get_filename10250286
Ref: 86b10250286
Ref: library/importlib importlib machinery ModuleSpec10250400
Ref: 14cb10250400
Ref: library/importlib importlib machinery ModuleSpec name10251212
Ref: 19b910251212
Ref: library/importlib importlib machinery ModuleSpec loader10251317
Ref: 19b710251317
Ref: library/importlib importlib machinery ModuleSpec origin10251493
Ref: ebe10251493
Ref: library/importlib importlib machinery ModuleSpec submodule_search_locations10251843
Ref: 379010251843
Ref: library/importlib importlib machinery ModuleSpec loader_state10252005
Ref: 379110252005
Ref: library/importlib importlib machinery ModuleSpec cached10252127
Ref: 379210252127
Ref: library/importlib importlib machinery ModuleSpec parent10252254
Ref: 19bb10252254
Ref: library/importlib importlib machinery ModuleSpec has_location10252532
Ref: 379310252532
Ref: importlib machinery -- Importers and path hooks-Footnote-110252709
Ref: importlib machinery -- Importers and path hooks-Footnote-210252788
Ref: importlib machinery -- Importers and path hooks-Footnote-310252837
Ref: importlib machinery -- Importers and path hooks-Footnote-410252886
Node: importlib util -- Utility code for importers10252935
Ref: library/importlib importlib-util-utility-code-for-importers10253135
Ref: 379410253135
Ref: library/importlib module-importlib util10253135
Ref: a010253135
Ref: library/importlib importlib util MAGIC_NUMBER10253461
Ref: 86710253461
Ref: library/importlib importlib util cache_from_source10253699
Ref: 55c10253699
Ref: library/importlib importlib util source_from_cache10255586
Ref: 55d10255586
Ref: library/importlib importlib util decode_source10256198
Ref: 86910256198
Ref: library/importlib importlib util resolve_name10256464
Ref: 379510256464
Ref: library/importlib importlib util find_spec10257164
Ref: 93d10257164
Ref: library/importlib importlib util module_from_spec10258042
Ref: 6f510258042
Ref: library/importlib importlib util module_for_loader10258671
Ref: 94710258671
Ref: library/importlib importlib util set_loader10260415
Ref: 94810260415
Ref: library/importlib importlib util set_package10261021
Ref: 94910261021
Ref: library/importlib importlib util spec_from_loader10261416
Ref: 375c10261416
Ref: library/importlib importlib util spec_from_file_location10261858
Ref: 55e10261858
Ref: library/importlib importlib util source_hash10262319
Ref: 379610262319
Ref: library/importlib importlib util LazyLoader10262587
Ref: 55810262587
Ref: library/importlib importlib util LazyLoader factory10264061
Ref: 379810264061
Ref: importlib util -- Utility code for importers-Footnote-110264631
Ref: importlib util -- Utility code for importers-Footnote-210264704
Ref: importlib util -- Utility code for importers-Footnote-310264753
Ref: importlib util -- Utility code for importers-Footnote-410264802
Ref: importlib util -- Utility code for importers-Footnote-510264851
Ref: importlib util -- Utility code for importers-Footnote-610264900
Node: Examples<29>10264949
Ref: library/importlib examples10265093
Ref: 379910265093
Ref: library/importlib importlib-examples10265093
Ref: 379a10265093
Node: Importing programmatically10265358
Ref: library/importlib importing-programmatically10265478
Ref: 379b10265478
Node: Checking if a module can be imported10265709
Ref: library/importlib checking-if-a-module-can-be-imported10265870
Ref: 379c10265870
Node: Importing a source file directly10266655
Ref: library/importlib importing-a-source-file-directly10266812
Ref: 379d10266812
Node: Setting up an importer10267371
Ref: library/importlib setting-up-an-importer10267529
Ref: 379e10267529
Node: Approximating importlib import_module10269103
Ref: library/importlib approximating-importlib-import-module10269220
Ref: 379f10269220
Node: Using importlib metadata10270817
Ref: library/importlib metadata doc10270941
Ref: 37a010270941
Ref: library/importlib metadata module-importlib metadata10270941
Ref: 9e10270941
Ref: library/importlib metadata using10270941
Ref: 37a110270941
Ref: library/importlib metadata using-importlib-metadata10270941
Ref: 37a210270941
Ref: Using importlib metadata-Footnote-110272334
Ref: Using importlib metadata-Footnote-210272412
Ref: Using importlib metadata-Footnote-310272497
Ref: Using importlib metadata-Footnote-410272582
Ref: Using importlib metadata-Footnote-510272654
Ref: Using importlib metadata-Footnote-610272692
Node: Overview10272741
Ref: library/importlib metadata overview10272836
Ref: 37a310272836
Node: Functional API<2>10274258
Ref: library/importlib metadata functional-api10274375
Ref: 37a910274375
Node: Entry points10274627
Ref: library/importlib metadata entry-points10274723
Ref: 37a410274723
Ref: library/importlib metadata id110274723
Ref: 37aa10274723
Ref: Entry points-Footnote-110275803
Node: Distribution metadata10275914
Ref: library/importlib metadata distribution-metadata10276040
Ref: 37ab10276040
Ref: library/importlib metadata metadata10276040
Ref: 37a510276040
Ref: Distribution metadata-Footnote-110276524
Node: Distribution versions10276804
Ref: library/importlib metadata distribution-versions10276936
Ref: 37ac10276936
Ref: library/importlib metadata version10276936
Ref: 37a610276936
Node: Distribution files10277145
Ref: library/importlib metadata distribution-files10277281
Ref: 37ad10277281
Ref: library/importlib metadata files10277281
Ref: 37a710277281
Ref: Distribution files-Footnote-110278671
Node: Distribution requirements10278768
Ref: library/importlib metadata distribution-requirements10278874
Ref: 37ae10278874
Ref: library/importlib metadata requirements10278874
Ref: 37a810278874
Node: Distributions10279141
Ref: library/importlib metadata distributions10279280
Ref: 37af10279280
Ref: Distributions-Footnote-110280187
Node: Extending the search algorithm10280236
Ref: library/importlib metadata extending-the-search-algorithm10280349
Ref: 37b010280349
Node: Python Language Services10282116
Ref: library/language doc10282268
Ref: 37b110282268
Ref: library/language language10282268
Ref: 37b210282268
Ref: library/language python-language-services10282268
Ref: 37b310282268
Node: parser --- Access Python parse trees10283680
Ref: library/parser doc10283815
Ref: 37b410283815
Ref: library/parser module-parser10283815
Ref: c810283815
Ref: library/parser parser-access-python-parse-trees10283815
Ref: 37b510283815
Node: Creating ST Objects10289018
Ref: library/parser creating-st-objects10289140
Ref: 37bb10289140
Ref: library/parser creating-sts10289140
Ref: 37bc10289140
Ref: library/parser parser expr10289386
Ref: 37b610289386
Ref: library/parser parser suite10289719
Ref: 37b710289719
Ref: library/parser parser sequence2st10290054
Ref: 37b810290054
Ref: library/parser parser tuple2st10291466
Ref: 37bf10291466
Node: Converting ST Objects10291633
Ref: library/parser converting-st-objects10291785
Ref: 37c010291785
Ref: library/parser converting-sts10291785
Ref: 37c110291785
Ref: library/parser parser st2list10292099
Ref: 37b910292099
Ref: library/parser parser st2tuple10293171
Ref: 37ba10293171
Ref: library/parser parser compilest10293713
Ref: 37be10293713
Node: Queries on ST Objects10294874
Ref: library/parser queries-on-st-objects10295036
Ref: 37c210295036
Ref: library/parser querying-sts10295036
Ref: 37c310295036
Ref: library/parser parser isexpr10295408
Ref: 37c410295408
Ref: library/parser parser issuite10295889
Ref: 37c510295889
Node: Exceptions and Error Handling10296244
Ref: library/parser exceptions-and-error-handling10296395
Ref: 37c610296395
Ref: library/parser st-errors10296395
Ref: 37c710296395
Ref: library/parser parser ParserError10296690
Ref: 37bd10296690
Node: ST Objects10297848
Ref: library/parser id110298006
Ref: 37c810298006
Ref: library/parser st-objects10298006
Ref: 37c910298006
Ref: library/parser parser STType10298194
Ref: 37ca10298194
Ref: library/parser parser ST compile10298378
Ref: 37cb10298378
Ref: library/parser parser ST isexpr10298480
Ref: 37cc10298480
Ref: library/parser parser ST issuite10298544
Ref: 37cd10298544
Ref: library/parser parser ST tolist10298610
Ref: 37ce10298610
Ref: library/parser parser ST totuple10298727
Ref: 37cf10298727
Node: Example Emulation of compile10298846
Ref: library/parser example-emulation-of-compile10298966
Ref: 37d010298966
Node: ast --- Abstract Syntax Trees10300060
Ref: library/ast doc10300255
Ref: 37d110300255
Ref: library/ast ast-abstract-syntax-trees10300255
Ref: 37d210300255
Ref: library/ast module-ast10300255
Ref: 810300255
Ref: ast --- Abstract Syntax Trees-Footnote-110301200
Node: Node classes10301262
Ref: library/ast node-classes10301365
Ref: 37d410301365
Ref: library/ast ast AST10301410
Ref: 37d310301410
Ref: library/ast ast AST _fields10302230
Ref: 37d610302230
Ref: library/ast ast AST lineno10303029
Ref: 37d710303029
Ref: library/ast ast AST col_offset10303053
Ref: 37d810303053
Ref: library/ast ast AST end_lineno10303081
Ref: 37d910303081
Ref: library/ast ast AST end_col_offset10303109
Ref: 37da10303109
Node: Abstract Grammar10305359
Ref: library/ast abstract-grammar10305482
Ref: 37d510305482
Ref: library/ast id110305482
Ref: 37db10305482
Node: ast Helpers10311537
Ref: library/ast ast-helpers10311639
Ref: 37dc10311639
Ref: library/ast ast parse10311827
Ref: 1a210311827
Ref: library/ast ast literal_eval10313612
Ref: 4aa10313612
Ref: library/ast ast get_docstring10314461
Ref: 105a10314461
Ref: library/ast ast get_source_segment10314869
Ref: 1a110314869
Ref: library/ast ast fix_missing_locations10315315
Ref: 37dd10315315
Ref: library/ast ast increment_lineno10315769
Ref: ef310315769
Ref: library/ast ast copy_location10315995
Ref: 37de10315995
Ref: library/ast ast iter_fields10316227
Ref: 37df10316227
Ref: library/ast ast iter_child_nodes10316380
Ref: 37e010316380
Ref: library/ast ast walk10316556
Ref: 37e110316556
Ref: library/ast ast NodeVisitor10316820
Ref: 28210316820
Ref: library/ast ast NodeVisitor visit10317163
Ref: 37e210317163
Ref: library/ast ast NodeVisitor generic_visit10317449
Ref: 37e310317449
Ref: library/ast ast NodeTransformer10318281
Ref: 37e410318281
Ref: library/ast ast dump10320153
Ref: f9410320153
Ref: ast Helpers-Footnote-110321618
Ref: ast Helpers-Footnote-210321667
Ref: ast Helpers-Footnote-310321716
Ref: ast Helpers-Footnote-410321765
Ref: ast Helpers-Footnote-510321813
Ref: ast Helpers-Footnote-610321880
Ref: ast Helpers-Footnote-710321935
Ref: ast Helpers-Footnote-810321974
Node: symtable --- Access to the compiler's symbol tables10322011
Ref: library/symtable doc10322219
Ref: 37e510322219
Ref: library/symtable module-symtable10322219
Ref: fd10322219
Ref: library/symtable symtable-access-to-the-compiler-s-symbol-tables10322219
Ref: 37e610322219
Ref: symtable --- Access to the compiler's symbol tables-Footnote-110322801
Node: Generating Symbol Tables10322868
Ref: library/symtable generating-symbol-tables10323012
Ref: 37e710323012
Ref: library/symtable symtable symtable10323081
Ref: fcb10323081
Node: Examining Symbol Tables10323359
Ref: library/symtable examining-symbol-tables10323503
Ref: 37e910323503
Ref: library/symtable symtable SymbolTable10323570
Ref: 37e810323570
Ref: library/symtable symtable SymbolTable get_type10323673
Ref: 37ea10323673
Ref: library/symtable symtable SymbolTable get_id10323841
Ref: 37eb10323841
Ref: library/symtable symtable SymbolTable get_name10323919
Ref: 37ec10323919
Ref: library/symtable symtable SymbolTable get_lineno10324228
Ref: 37ed10324228
Ref: library/symtable symtable SymbolTable is_optimized10324359
Ref: 37ee10324359
Ref: library/symtable symtable SymbolTable is_nested10324474
Ref: 37ef10324474
Ref: library/symtable symtable SymbolTable has_children10324584
Ref: 37f010324584
Ref: library/symtable symtable SymbolTable has_exec10324764
Ref: 37f210324764
Ref: library/symtable symtable SymbolTable get_identifiers10324859
Ref: 37f310324859
Ref: library/symtable symtable SymbolTable lookup10324962
Ref: 37f410324962
Ref: library/symtable symtable SymbolTable get_symbols10325091
Ref: 37f610325091
Ref: library/symtable symtable SymbolTable get_children10325222
Ref: 37f110325222
Ref: library/symtable symtable Function10325316
Ref: 37f710325316
Ref: library/symtable symtable Function get_parameters10325442
Ref: 37f810325442
Ref: library/symtable symtable Function get_locals10325569
Ref: 37f910325569
Ref: library/symtable symtable Function get_globals10325678
Ref: 37fa10325678
Ref: library/symtable symtable Function get_nonlocals10325789
Ref: 37fb10325789
Ref: library/symtable symtable Function get_frees10325904
Ref: 37fc10325904
Ref: library/symtable symtable Class10326030
Ref: 37fd10326030
Ref: library/symtable symtable Class get_methods10326139
Ref: 37fe10326139
Ref: library/symtable symtable Symbol10326269
Ref: 37f510326269
Ref: library/symtable symtable Symbol get_name10326426
Ref: 37ff10326426
Ref: library/symtable symtable Symbol is_referenced10326501
Ref: 380010326501
Ref: library/symtable symtable Symbol is_imported10326607
Ref: 380110326607
Ref: library/symtable symtable Symbol is_parameter10326736
Ref: 380210326736
Ref: library/symtable symtable Symbol is_global10326835
Ref: 380310326835
Ref: library/symtable symtable Symbol is_nonlocal10326926
Ref: 101210326926
Ref: library/symtable symtable Symbol is_declared_global10327021
Ref: cbb10327021
Ref: library/symtable symtable Symbol is_local10327164
Ref: 380410327164
Ref: library/symtable symtable Symbol is_annotated10327266
Ref: 380510327266
Ref: library/symtable symtable Symbol is_free10327392
Ref: 380610327392
Ref: library/symtable symtable Symbol is_assigned10327529
Ref: 380710327529
Ref: library/symtable symtable Symbol is_namespace10327640
Ref: 380810327640
Ref: library/symtable symtable Symbol get_namespaces10328288
Ref: 380910328288
Ref: library/symtable symtable Symbol get_namespace10328389
Ref: 380a10328389
Node: symbol --- Constants used with Python parse trees10328564
Ref: library/symbol doc10328791
Ref: 380b10328791
Ref: library/symbol module-symbol10328791
Ref: fc10328791
Ref: library/symbol symbol-constants-used-with-python-parse-trees10328791
Ref: 380c10328791
Ref: library/symbol symbol sym_name10329460
Ref: 380d10329460
Ref: symbol --- Constants used with Python parse trees-Footnote-110329715
Node: token --- Constants used with Python parse trees10329780
Ref: library/token doc10329995
Ref: 380e10329995
Ref: library/token module-token10329995
Ref: 11110329995
Ref: library/token token-constants-used-with-python-parse-trees10329995
Ref: 380f10329995
Ref: library/token token tok_name10330709
Ref: 381010330709
Ref: library/token token ISTERMINAL10330927
Ref: 381110330927
Ref: library/token token ISNONTERMINAL10331012
Ref: 381210331012
Ref: library/token token ISEOF10331104
Ref: 381310331104
Ref: library/token token ENDMARKER10331233
Ref: 381410331233
Ref: library/token token NAME10331260
Ref: 381510331260
Ref: library/token token NUMBER10331282
Ref: 381610331282
Ref: library/token token STRING10331306
Ref: 381710331306
Ref: library/token token NEWLINE10331330
Ref: 381810331330
Ref: library/token token INDENT10331355
Ref: 381910331355
Ref: library/token token DEDENT10331379
Ref: 381a10331379
Ref: library/token token LPAR10331403
Ref: 381b10331403
Ref: library/token token RPAR10331458
Ref: 381c10331458
Ref: library/token token LSQB10331513
Ref: 381d10331513
Ref: library/token token RSQB10331568
Ref: 381e10331568
Ref: library/token token COLON10331623
Ref: 381f10331623
Ref: library/token token COMMA10331679
Ref: 382010331679
Ref: library/token token SEMI10331735
Ref: 382110331735
Ref: library/token token PLUS10331790
Ref: 382210331790
Ref: library/token token MINUS10331845
Ref: 382310331845
Ref: library/token token STAR10331901
Ref: 382410331901
Ref: library/token token SLASH10331956
Ref: 382510331956
Ref: library/token token VBAR10332012
Ref: 382610332012
Ref: library/token token AMPER10332067
Ref: 382710332067
Ref: library/token token LESS10332123
Ref: 382810332123
Ref: library/token token GREATER10332178
Ref: 382910332178
Ref: library/token token EQUAL10332236
Ref: 382a10332236
Ref: library/token token DOT10332292
Ref: 382b10332292
Ref: library/token token PERCENT10332346
Ref: 382c10332346
Ref: library/token token LBRACE10332404
Ref: 382d10332404
Ref: library/token token RBRACE10332461
Ref: 382e10332461
Ref: library/token token EQEQUAL10332518
Ref: 382f10332518
Ref: library/token token NOTEQUAL10332577
Ref: 383010332577
Ref: library/token token LESSEQUAL10332637
Ref: 383110332637
Ref: library/token token GREATEREQUAL10332698
Ref: 383210332698
Ref: library/token token TILDE10332762
Ref: 383310332762
Ref: library/token token CIRCUMFLEX10332818
Ref: 383410332818
Ref: library/token token LEFTSHIFT10332879
Ref: 383510332879
Ref: library/token token RIGHTSHIFT10332940
Ref: 383610332940
Ref: library/token token DOUBLESTAR10333002
Ref: 383710333002
Ref: library/token token PLUSEQUAL10333064
Ref: 383810333064
Ref: library/token token MINEQUAL10333125
Ref: 383910333125
Ref: library/token token STAREQUAL10333185
Ref: 383a10333185
Ref: library/token token SLASHEQUAL10333246
Ref: 383b10333246
Ref: library/token token PERCENTEQUAL10333308
Ref: 383c10333308
Ref: library/token token AMPEREQUAL10333372
Ref: 383d10333372
Ref: library/token token VBAREQUAL10333434
Ref: 383e10333434
Ref: library/token token CIRCUMFLEXEQUAL10333495
Ref: 383f10333495
Ref: library/token token LEFTSHIFTEQUAL10333562
Ref: 384010333562
Ref: library/token token RIGHTSHIFTEQUAL10333629
Ref: 384110333629
Ref: library/token token DOUBLESTAREQUAL10333697
Ref: 384210333697
Ref: library/token token DOUBLESLASH10333765
Ref: 384310333765
Ref: library/token token DOUBLESLASHEQUAL10333828
Ref: 384410333828
Ref: library/token token AT10333897
Ref: 384510333897
Ref: library/token token ATEQUAL10333950
Ref: 384610333950
Ref: library/token token RARROW10334009
Ref: 384710334009
Ref: library/token token ELLIPSIS10334067
Ref: 384810334067
Ref: library/token token COLONEQUAL10334128
Ref: 384910334128
Ref: library/token token OP10334190
Ref: 384a10334190
Ref: library/token token AWAIT10334210
Ref: 384b10334210
Ref: library/token token ASYNC10334233
Ref: 384c10334233
Ref: library/token token TYPE_IGNORE10334256
Ref: 384d10334256
Ref: library/token token TYPE_COMMENT10334285
Ref: 384e10334285
Ref: library/token token ERRORTOKEN10334315
Ref: 384f10334315
Ref: library/token token N_TOKENS10334343
Ref: 385010334343
Ref: library/token token NT_OFFSET10334369
Ref: 385110334369
Ref: library/token token COMMENT10334514
Ref: 385210334514
Ref: library/token token NL10334585
Ref: 385310334585
Ref: library/token token ENCODING10334867
Ref: 385410334867
Ref: token --- Constants used with Python parse trees-Footnote-110335934
Node: keyword --- Testing for Python keywords10335998
Ref: library/keyword doc10336204
Ref: 385510336204
Ref: library/keyword keyword-testing-for-python-keywords10336204
Ref: 385610336204
Ref: library/keyword module-keyword10336204
Ref: a710336204
Ref: library/keyword keyword iskeyword10336495
Ref: 165110336495
Ref: library/keyword keyword kwlist10336594
Ref: 385710336594
Ref: keyword --- Testing for Python keywords-Footnote-110336898
Node: tokenize --- Tokenizer for Python source10336964
Ref: library/tokenize doc10337169
Ref: 385810337169
Ref: library/tokenize module-tokenize10337169
Ref: 11210337169
Ref: library/tokenize tokenize-tokenizer-for-python-source10337169
Ref: 385910337169
Ref: tokenize --- Tokenizer for Python source-Footnote-110338116
Node: Tokenizing Input10338183
Ref: library/tokenize tokenizing-input10338306
Ref: 385a10338306
Ref: library/tokenize tokenize tokenize10338412
Ref: c6010338412
Ref: library/tokenize tokenize generate_tokens10339826
Ref: 103a10339826
Ref: library/tokenize tokenize untokenize10340591
Ref: 385b10340591
Ref: library/tokenize tokenize detect_encoding10341533
Ref: 1c8610341533
Ref: library/tokenize tokenize open10342527
Ref: 1c8510342527
Ref: library/tokenize tokenize TokenError10342692
Ref: 385c10342692
Ref: Tokenizing Input-Footnote-110343184
Ref: Tokenizing Input-Footnote-210343233
Node: Command-Line Usage<2>10343282
Ref: library/tokenize command-line-usage10343426
Ref: 385d10343426
Ref: library/tokenize tokenize-cli10343426
Ref: 385e10343426
Ref: library/tokenize cmdoption-tokenize-h10343688
Ref: 385f10343688
Ref: library/tokenize cmdoption-tokenize-e10343756
Ref: 386010343756
Node: Examples<30>10343954
Ref: library/tokenize examples10344073
Ref: 386110344073
Node: tabnanny --- Detection of ambiguous indentation10348567
Ref: library/tabnanny doc10348773
Ref: 386210348773
Ref: library/tabnanny module-tabnanny10348773
Ref: 10110348773
Ref: library/tabnanny tabnanny-detection-of-ambiguous-indentation10348773
Ref: 386310348773
Ref: library/tabnanny tabnanny check10349306
Ref: 386410349306
Ref: library/tabnanny tabnanny verbose10349744
Ref: 386510349744
Ref: library/tabnanny tabnanny filename_only10349901
Ref: 386610349901
Ref: library/tabnanny tabnanny NannyNag10350119
Ref: 386710350119
Ref: library/tabnanny tabnanny process_tokens10350281
Ref: 386810350281
Ref: tabnanny --- Detection of ambiguous indentation-Footnote-110350577
Node: pyclbr --- Python module browser support10350644
Ref: library/pyclbr doc10350852
Ref: 386910350852
Ref: library/pyclbr module-pyclbr10350852
Ref: d910350852
Ref: library/pyclbr pyclbr-python-module-browser-support10350852
Ref: 386a10350852
Ref: library/pyclbr pyclbr readmodule10351550
Ref: 116e10351550
Ref: library/pyclbr pyclbr readmodule_ex10352159
Ref: 116f10352159
Ref: pyclbr --- Python module browser support-Footnote-110353227
Node: 函式物件10353292
Ref: library/pyclbr function-objects10353406
Ref: 386b10353406
Ref: library/pyclbr pyclbr-function-objects10353406
Ref: 386c10353406
Ref: library/pyclbr pyclbr Function file10353561
Ref: 386d10353561
Ref: library/pyclbr pyclbr Function module10353645
Ref: 386e10353645
Ref: library/pyclbr pyclbr Function name10353736
Ref: 386f10353736
Ref: library/pyclbr pyclbr Function lineno10353795
Ref: 387010353795
Ref: library/pyclbr pyclbr Function parent10353887
Ref: 387110353887
Ref: library/pyclbr pyclbr Function children10354012
Ref: 387210354012
Node: Class Objects<2>10354154
Ref: library/pyclbr class-objects10354268
Ref: 387310354268
Ref: library/pyclbr pyclbr-class-objects10354268
Ref: 387410354268
Ref: library/pyclbr pyclbr Class file10354447
Ref: 387510354447
Ref: library/pyclbr pyclbr Class module10354525
Ref: 387610354525
Ref: library/pyclbr pyclbr Class name10354610
Ref: 387710354610
Ref: library/pyclbr pyclbr Class lineno10354663
Ref: 387810354663
Ref: library/pyclbr pyclbr Class parent10354752
Ref: 387910354752
Ref: library/pyclbr pyclbr Class children10354870
Ref: 387a10354870
Ref: library/pyclbr pyclbr Class super10355009
Ref: 387b10355009
Ref: library/pyclbr pyclbr Class methods10355344
Ref: 387c10355344
Node: py_compile --- Compile Python source files10355531
Ref: library/py_compile doc10355736
Ref: 387d10355736
Ref: library/py_compile module-py_compile10355736
Ref: d810355736
Ref: library/py_compile py-compile-compile-python-source-files10355736
Ref: 387e10355736
Ref: library/py_compile py_compile PyCompileError10356361
Ref: 387f10356361
Ref: library/py_compile py_compile compile10356487
Ref: 21610356487
Ref: library/py_compile py_compile PycInvalidationMode10360129
Ref: 388010360129
Ref: library/py_compile py_compile PycInvalidationMode TIMESTAMP10360549
Ref: 388210360549
Ref: library/py_compile py_compile PycInvalidationMode CHECKED_HASH10360828
Ref: 388110360828
Ref: library/py_compile py_compile PycInvalidationMode UNCHECKED_HASH10361071
Ref: 388310361071
Ref: library/py_compile py_compile main10361517
Ref: 388410361517
Ref: py_compile --- Compile Python source files-Footnote-110362379
Ref: py_compile --- Compile Python source files-Footnote-210362448
Ref: py_compile --- Compile Python source files-Footnote-310362497
Ref: py_compile --- Compile Python source files-Footnote-410362546
Ref: py_compile --- Compile Python source files-Footnote-510362595
Node: compileall --- Byte-compile Python libraries10362644
Ref: library/compileall doc10362847
Ref: 388510362847
Ref: library/compileall compileall-byte-compile-python-libraries10362847
Ref: 388610362847
Ref: library/compileall module-compileall10362847
Ref: 2110362847
Ref: compileall --- Byte-compile Python libraries-Footnote-110363507
Node: Command-line use10363576
Ref: library/compileall command-line-use10363698
Ref: 388710363698
Ref: library/compileall cmdoption-compileall-arg-directory10363849
Ref: 388810363849
Ref: library/compileall cmdoption-compileall-arg-file10363881
Ref: 388910363881
Ref: library/compileall cmdoption-compileall-l10364135
Ref: 388a10364135
Ref: library/compileall cmdoption-compileall-f10364291
Ref: 388b10364291
Ref: library/compileall cmdoption-compileall-q10364368
Ref: 388c10364368
Ref: library/compileall cmdoption-compileall-d10364558
Ref: 388d10364558
Ref: library/compileall cmdoption-compileall-x10364917
Ref: 388e10364917
Ref: library/compileall cmdoption-compileall-i10365096
Ref: 388f10365096
Ref: library/compileall cmdoption-compileall-b10365304
Ref: 389010365304
Ref: library/compileall cmdoption-compileall-r10365636
Ref: 389110365636
Ref: library/compileall cmdoption-compileall-j10365912
Ref: 389210365912
Ref: library/compileall cmdoption-compileall-invalidation-mode10366097
Ref: 389310366097
Ref: Command-line use-Footnote-110367758
Node: Public functions10367807
Ref: library/compileall public-functions10367929
Ref: 389410367929
Ref: library/compileall compileall compile_dir10367984
Ref: 37710367984
Ref: library/compileall compileall compile_file10371044
Ref: 6c010371044
Ref: library/compileall compileall compile_path10373139
Ref: 6c110373139
Ref: Public functions-Footnote-110374799
Ref: Public functions-Footnote-210374848
Node: dis --- Python bytecode的反組譯器10374897
Ref: library/dis doc10375101
Ref: 389510375101
Ref: library/dis dis-disassembler-for-python-bytecode10375101
Ref: 389610375101
Ref: library/dis module-dis10375101
Ref: 3810375101
Ref: dis --- Python bytecode的反組譯器-Footnote-110376459
Node: Bytecode analysis10376521
Ref: library/dis bytecode-analysis10376640
Ref: 389710376640
Ref: library/dis dis Bytecode10376878
Ref: 83c10376878
Ref: library/dis dis Bytecode from_traceback10377902
Ref: 83e10377902
Ref: library/dis dis Bytecode codeobj10378132
Ref: 389810378132
Ref: library/dis dis Bytecode first_line10378193
Ref: 389910378193
Ref: library/dis dis Bytecode dis10378287
Ref: 83d10378287
Ref: library/dis dis Bytecode info10378484
Ref: 389a10378484
Node: Analysis functions10378939
Ref: library/dis analysis-functions10379095
Ref: 389b10379095
Ref: library/dis dis code_info10379401
Ref: bd310379401
Ref: library/dis dis show_code10379927
Ref: 83710379927
Ref: library/dis dis dis10380378
Ref: 38910380378
Ref: library/dis dis distb10381785
Ref: 83810381785
Ref: library/dis dis disassemble10382170
Ref: 83910382170
Ref: library/dis dis disco10382229
Ref: 389c10382229
Ref: library/dis dis get_instructions10383105
Ref: 83b10383105
Ref: library/dis dis findlinestarts10383713
Ref: 389d10383713
Ref: library/dis dis findlabels10384190
Ref: 389e10384190
Ref: library/dis dis stack_effect10384358
Ref: 83f10384358
Ref: Analysis functions-Footnote-110384913
Node: Python Bytecode Instructions10384990
Ref: library/dis bytecodes10385147
Ref: 389f10385147
Ref: library/dis python-bytecode-instructions10385147
Ref: 38a010385147
Ref: library/dis dis Instruction10385381
Ref: 83a10385381
Ref: library/dis dis Instruction opcode10385449
Ref: 38a110385449
Ref: library/dis dis Instruction opname10385642
Ref: 38a310385642
Ref: library/dis dis Instruction arg10385710
Ref: 38a410385710
Ref: library/dis dis Instruction argval10385802
Ref: 38a510385802
Ref: library/dis dis Instruction argrepr10385889
Ref: 38a610385889
Ref: library/dis dis Instruction offset10385973
Ref: 38a710385973
Ref: library/dis dis Instruction starts_line10386057
Ref: 38a810386057
Ref: library/dis dis Instruction is_jump_target10386155
Ref: 38a910386155
Ref: library/dis opcode-NOP10386385
Ref: 38aa10386385
Ref: library/dis opcode-POP_TOP10386475
Ref: 38ab10386475
Ref: library/dis opcode-ROT_TWO10386539
Ref: 38ac10386539
Ref: library/dis opcode-ROT_THREE10386602
Ref: 38ad10386602
Ref: library/dis opcode-ROT_FOUR10386721
Ref: 2dd10386721
Ref: library/dis opcode-DUP_TOP10386871
Ref: 38ae10386871
Ref: library/dis opcode-DUP_TOP_TWO10386968
Ref: 38af10386968
Ref: library/dis opcode-UNARY_POSITIVE10387236
Ref: 38b010387236
Ref: library/dis opcode-UNARY_NEGATIVE10387299
Ref: 38b110387299
Ref: library/dis opcode-UNARY_NOT10387362
Ref: 38b210387362
Ref: library/dis opcode-UNARY_INVERT10387423
Ref: 38b310387423
Ref: library/dis opcode-GET_ITER10387484
Ref: 38b410387484
Ref: library/dis opcode-GET_YIELD_FROM_ITER10387546
Ref: 38b510387546
Ref: library/dis opcode-BINARY_POWER10387963
Ref: 38b610387963
Ref: library/dis opcode-BINARY_MULTIPLY10388031
Ref: 38b710388031
Ref: library/dis opcode-BINARY_MATRIX_MULTIPLY10388101
Ref: 38b810388101
Ref: library/dis opcode-BINARY_FLOOR_DIVIDE10388202
Ref: 38b910388202
Ref: library/dis opcode-BINARY_TRUE_DIVIDE10388277
Ref: 38ba10388277
Ref: library/dis opcode-BINARY_MODULO10388350
Ref: 38bb10388350
Ref: library/dis opcode-BINARY_ADD10388418
Ref: 38bc10388418
Ref: library/dis opcode-BINARY_SUBTRACT10388483
Ref: 38bd10388483
Ref: library/dis opcode-BINARY_SUBSCR10388553
Ref: 38be10388553
Ref: library/dis opcode-BINARY_LSHIFT10388620
Ref: 38bf10388620
Ref: library/dis opcode-BINARY_RSHIFT10388689
Ref: 38c010388689
Ref: library/dis opcode-BINARY_AND10388758
Ref: 38c110388758
Ref: library/dis opcode-BINARY_XOR10388823
Ref: 38c210388823
Ref: library/dis opcode-BINARY_OR10388888
Ref: 38c310388888
Ref: library/dis opcode-INPLACE_POWER10389229
Ref: 38c410389229
Ref: library/dis opcode-INPLACE_MULTIPLY10389307
Ref: 38c510389307
Ref: library/dis opcode-INPLACE_MATRIX_MULTIPLY10389387
Ref: 38c610389387
Ref: library/dis opcode-INPLACE_FLOOR_DIVIDE10389498
Ref: 38c710389498
Ref: library/dis opcode-INPLACE_TRUE_DIVIDE10389583
Ref: 38c810389583
Ref: library/dis opcode-INPLACE_MODULO10389666
Ref: 38c910389666
Ref: library/dis opcode-INPLACE_ADD10389744
Ref: 38ca10389744
Ref: library/dis opcode-INPLACE_SUBTRACT10389819
Ref: 38cb10389819
Ref: library/dis opcode-INPLACE_LSHIFT10389899
Ref: 38cc10389899
Ref: library/dis opcode-INPLACE_RSHIFT10389978
Ref: 38cd10389978
Ref: library/dis opcode-INPLACE_AND10390057
Ref: 38ce10390057
Ref: library/dis opcode-INPLACE_XOR10390132
Ref: 38cf10390132
Ref: library/dis opcode-INPLACE_OR10390207
Ref: 38d010390207
Ref: library/dis opcode-STORE_SUBSCR10390281
Ref: 38d110390281
Ref: library/dis opcode-DELETE_SUBSCR10390348
Ref: 38d210390348
Ref: library/dis opcode-GET_AWAITABLE10390434
Ref: 38d310390434
Ref: library/dis opcode-GET_AITER10390712
Ref: 38d410390712
Ref: library/dis opcode-GET_ANEXT10390904
Ref: 38d510390904
Ref: library/dis opcode-END_ASYNC_FOR10391080
Ref: 2e310391080
Ref: library/dis opcode-BEFORE_ASYNC_WITH10391529
Ref: 38d610391529
Ref: library/dis opcode-SETUP_ASYNC_WITH10391754
Ref: 38d710391754
Ref: library/dis opcode-PRINT_EXPR10391867
Ref: 38d810391867
Ref: library/dis opcode-SET_ADD10392103
Ref: 38d910392103
Ref: library/dis opcode-LIST_APPEND10392214
Ref: 38da10392214
Ref: library/dis opcode-MAP_ADD10392334
Ref: 2e510392334
Ref: library/dis opcode-RETURN_VALUE10392836
Ref: 38db10392836
Ref: library/dis opcode-YIELD_VALUE10392916
Ref: 38dc10392916
Ref: library/dis opcode-YIELD_FROM10392999
Ref: 38dd10392999
Ref: library/dis opcode-SETUP_ANNOTATIONS10393133
Ref: 62310393133
Ref: library/dis opcode-IMPORT_STAR10393429
Ref: 38de10393429
Ref: library/dis opcode-POP_BLOCK10393668
Ref: 38df10393668
Ref: library/dis opcode-POP_EXCEPT10393829
Ref: 38e010393829
Ref: library/dis opcode-POP_FINALLY10394162
Ref: 2e010394162
Ref: library/dis opcode-BEGIN_FINALLY10395100
Ref: 2de10395100
Ref: library/dis opcode-END_FINALLY10395376
Ref: 2e110395376
Ref: library/dis opcode-LOAD_BUILD_CLASS10396207
Ref: 38e210396207
Ref: library/dis opcode-SETUP_WITH10396375
Ref: 38e310396375
Ref: library/dis opcode-WITH_CLEANUP_START10397043
Ref: 2e210397043
Ref: library/dis opcode-WITH_CLEANUP_FINISH10397801
Ref: 38e110397801
Ref: library/dis opcode-STORE_NAME10398391
Ref: 38e510398391
Ref: library/dis opcode-DELETE_NAME10398645
Ref: 38e810398645
Ref: library/dis opcode-UNPACK_SEQUENCE10398793
Ref: 38e610398793
Ref: library/dis opcode-UNPACK_EX10398929
Ref: 38e910398929
Ref: library/dis opcode-STORE_ATTR10399432
Ref: 38ea10399432
Ref: library/dis opcode-DELETE_ATTR10399563
Ref: 38eb10399563
Ref: library/dis opcode-STORE_GLOBAL10399677
Ref: 38e710399677
Ref: library/dis opcode-DELETE_GLOBAL10399783
Ref: 38ec10399783
Ref: library/dis opcode-LOAD_CONST10399885
Ref: 38ed10399885
Ref: library/dis opcode-LOAD_NAME10399971
Ref: 38ee10399971
Ref: library/dis opcode-BUILD_TUPLE10400079
Ref: 38ef10400079
Ref: library/dis opcode-BUILD_LIST10400226
Ref: 38f010400226
Ref: library/dis opcode-BUILD_SET10400318
Ref: 38f110400318
Ref: library/dis opcode-BUILD_MAP10400408
Ref: 38f210400408
Ref: library/dis opcode-BUILD_CONST_KEY_MAP10400754
Ref: 61c10400754
Ref: library/dis opcode-BUILD_STRING10401067
Ref: 61b10401067
Ref: library/dis opcode-BUILD_TUPLE_UNPACK10401228
Ref: 38f310401228
Ref: library/dis opcode-BUILD_TUPLE_UNPACK_WITH_CALL10401469
Ref: 62210401469
Ref: library/dis opcode-BUILD_LIST_UNPACK10401749
Ref: 38f410401749
Ref: library/dis opcode-BUILD_SET_UNPACK10401983
Ref: 38f510401983
Ref: library/dis opcode-BUILD_MAP_UNPACK10402214
Ref: 38f610402214
Ref: library/dis opcode-BUILD_MAP_UNPACK_WITH_CALL10402470
Ref: 62010402470
Ref: library/dis opcode-LOAD_ATTR10402917
Ref: 38f710402917
Ref: library/dis opcode-COMPARE_OP10403009
Ref: 38f810403009
Ref: library/dis opcode-IMPORT_NAME10403141
Ref: 38f910403141
Ref: library/dis opcode-IMPORT_FROM10403538
Ref: 38fa10403538
Ref: library/dis opcode-JUMP_FORWARD10403774
Ref: 38fb10403774
Ref: library/dis opcode-POP_JUMP_IF_TRUE10403854
Ref: 38fc10403854
Ref: library/dis opcode-POP_JUMP_IF_FALSE10403999
Ref: 38fd10403999
Ref: library/dis opcode-JUMP_IF_TRUE_OR_POP10404146
Ref: 38fe10404146
Ref: library/dis opcode-JUMP_IF_FALSE_OR_POP10404348
Ref: 38ff10404348
Ref: library/dis opcode-JUMP_ABSOLUTE10404551
Ref: 390010404551
Ref: library/dis opcode-FOR_ITER10404627
Ref: 390110404627
Ref: library/dis opcode-LOAD_GLOBAL10404945
Ref: 390210404945
Ref: library/dis opcode-SETUP_FINALLY10405045
Ref: 390310405045
Ref: library/dis opcode-CALL_FINALLY10405241
Ref: 2df10405241
Ref: library/dis opcode-LOAD_FAST10405472
Ref: 390410405472
Ref: library/dis opcode-STORE_FAST10405591
Ref: 38e410405591
Ref: library/dis opcode-DELETE_FAST10405685
Ref: 390510405685
Ref: library/dis opcode-LOAD_CLOSURE10405768
Ref: 390610405768
Ref: library/dis opcode-LOAD_DEREF10406067
Ref: 390710406067
Ref: library/dis opcode-LOAD_CLASSDEREF10406253
Ref: 93310406253
Ref: library/dis opcode-STORE_DEREF10406485
Ref: 390810406485
Ref: library/dis opcode-DELETE_DEREF10406611
Ref: 390910406611
Ref: library/dis opcode-RAISE_VARARGS10406795
Ref: 390a10406795
Ref: library/dis opcode-CALL_FUNCTION10407220
Ref: 61e10407220
Ref: library/dis opcode-CALL_FUNCTION_KW10407811
Ref: 61f10407811
Ref: library/dis opcode-CALL_FUNCTION_EX10408649
Ref: 62110408649
Ref: library/dis opcode-LOAD_METHOD10409615
Ref: 4b210409615
Ref: library/dis opcode-CALL_METHOD10410107
Ref: 4b310410107
Ref: library/dis opcode-MAKE_FUNCTION10410638
Ref: 61d10410638
Ref: library/dis opcode-BUILD_SLICE10411325
Ref: 390b10411325
Ref: library/dis opcode-EXTENDED_ARG10411606
Ref: 390c10411606
Ref: library/dis opcode-FORMAT_VALUE10411943
Ref: 61a10411943
Ref: library/dis opcode-HAVE_ARGUMENT10412801
Ref: 390d10412801
Node: Opcode collections10413217
Ref: library/dis id110413347
Ref: 390e10413347
Ref: library/dis opcode-collections10413347
Ref: 38a210413347
Ref: library/dis dis opname10413492
Ref: 390f10413492
Ref: library/dis dis opmap10413579
Ref: 391010413579
Ref: library/dis dis cmp_op10413655
Ref: 391110413655
Ref: library/dis dis hasconst10413724
Ref: 391210413724
Ref: library/dis dis hasfree10413800
Ref: 391310413800
Ref: library/dis dis hasname10414136
Ref: 391410414136
Ref: library/dis dis hasjrel10414221
Ref: 391510414221
Ref: library/dis dis hasjabs10414306
Ref: 391610414306
Ref: library/dis dis haslocal10414392
Ref: 391710414392
Ref: library/dis dis hascompare10414474
Ref: 391810414474
Node: pickletools --- Tools for pickle developers10414551
Ref: library/pickletools doc10414702
Ref: 391910414702
Ref: library/pickletools module-pickletools10414702
Ref: cc10414702
Ref: library/pickletools pickletools-tools-for-pickle-developers10414702
Ref: 391a10414702
Ref: pickletools --- Tools for pickle developers-Footnote-110415493
Node: Command line usage<2>10415563
Ref: library/pickletools command-line-usage10415698
Ref: 391b10415698
Node: Command line options<3>10416649
Ref: library/pickletools command-line-options10416730
Ref: 391c10416730
Ref: library/pickletools cmdoption-pickletools-a10416793
Ref: 391d10416793
Ref: library/pickletools cmdoption-pickletools-o10416885
Ref: 391e10416885
Ref: library/pickletools cmdoption-pickletools-l10416981
Ref: 391f10416981
Ref: library/pickletools cmdoption-pickletools-m10417088
Ref: 392010417088
Ref: library/pickletools cmdoption-pickletools-p10417206
Ref: 392110417206
Node: Programmatic Interface<2>10417354
Ref: library/pickletools programmatic-interface10417489
Ref: 392210417489
Ref: library/pickletools pickletools dis10417556
Ref: 57510417556
Ref: library/pickletools pickletools genops10418381
Ref: 392310418381
Ref: library/pickletools pickletools optimize10418816
Ref: 1cc410418816
Node: Miscellaneous Services10419094
Ref: library/misc doc10419262
Ref: 392410419262
Ref: library/misc misc10419262
Ref: 392510419262
Ref: library/misc miscellaneous-services10419262
Ref: 392610419262
Node: formatter --- Generic output formatting10419545
Ref: library/formatter doc10419643
Ref: 392710419643
Ref: library/formatter formatter-generic-output-formatting10419643
Ref: 392810419643
Ref: library/formatter module-formatter10419643
Ref: 8210419643
Node: The Formatter Interface10421213
Ref: library/formatter formatter-interface10421346
Ref: 392910421346
Ref: library/formatter the-formatter-interface10421346
Ref: 392a10421346
Ref: library/formatter formatter AS_IS10421674
Ref: 392b10421674
Ref: library/formatter formatter formatter writer10422121
Ref: 392c10422121
Ref: library/formatter formatter formatter end_paragraph10422213
Ref: 392d10422213
Ref: library/formatter formatter formatter add_line_break10422366
Ref: 392e10422366
Ref: library/formatter formatter formatter add_hor_rule10422521
Ref: 392f10422521
Ref: library/formatter formatter formatter add_flowing_data10422840
Ref: 393010422840
Ref: library/formatter formatter formatter add_literal_data10423366
Ref: 393110423366
Ref: library/formatter formatter formatter add_label_data10423591
Ref: 393210423591
Ref: library/formatter formatter formatter flush_softspace10425024
Ref: 393310425024
Ref: library/formatter formatter formatter push_alignment10425295
Ref: 393410425295
Ref: library/formatter formatter formatter pop_alignment10425620
Ref: 393510425620
Ref: library/formatter formatter formatter push_font10425704
Ref: 393610425704
Ref: library/formatter formatter formatter pop_font10426091
Ref: 393710426091
Ref: library/formatter formatter formatter push_margin10426165
Ref: 393810426165
Ref: library/formatter formatter formatter pop_margin10426538
Ref: 393910426538
Ref: library/formatter formatter formatter push_style10426616
Ref: 393a10426616
Ref: library/formatter formatter formatter pop_style10426925
Ref: 393b10426925
Ref: library/formatter formatter formatter set_spacing10427198
Ref: 393c10427198
Ref: library/formatter formatter formatter assert_line_data10427293
Ref: 393d10427293
Node: Formatter Implementations10427657
Ref: library/formatter formatter-implementations10427819
Ref: 393e10427819
Ref: library/formatter formatter-impls10427819
Ref: 393f10427819
Ref: library/formatter formatter NullFormatter10428045
Ref: 394010428045
Ref: library/formatter formatter AbstractFormatter10428434
Ref: 394210428434
Node: The Writer Interface10428722
Ref: library/formatter the-writer-interface10428883
Ref: 394310428883
Ref: library/formatter writer-interface10428883
Ref: 394410428883
Ref: library/formatter formatter writer flush10429304
Ref: 394510429304
Ref: library/formatter formatter writer new_alignment10429397
Ref: 394610429397
Ref: library/formatter formatter writer new_font10429763
Ref: 394710429763
Ref: library/formatter formatter writer new_margin10430295
Ref: 394810430295
Ref: library/formatter formatter writer new_spacing10430631
Ref: 394910430631
Ref: library/formatter formatter writer new_styles10430721
Ref: 394a10430721
Ref: library/formatter formatter writer send_line_break10431061
Ref: 394b10431061
Ref: library/formatter formatter writer send_paragraph10431136
Ref: 394c10431136
Ref: library/formatter formatter writer send_hor_rule10431618
Ref: 394d10431618
Ref: library/formatter formatter writer send_flowing_data10431975
Ref: 394e10431975
Ref: library/formatter formatter writer send_literal_data10432281
Ref: 394f10432281
Ref: library/formatter formatter writer send_label_data10432717
Ref: 395010432717
Node: Writer Implementations10433029
Ref: library/formatter writer-implementations10433156
Ref: 395110433156
Ref: library/formatter writer-impls10433156
Ref: 395210433156
Ref: library/formatter formatter NullWriter10433414
Ref: 394110433414
Ref: library/formatter formatter AbstractWriter10433660
Ref: 395310433660
Ref: library/formatter formatter DumbWriter10433877
Ref: 395410433877
Node: MS Windows Specific Services10434244
Ref: library/windows doc10434410
Ref: 395510434410
Ref: library/windows ms-windows-specific-services10434410
Ref: 395610434410
Ref: library/windows mswin-specific-services10434410
Ref: 139b10434410
Node: msilib --- Read and write Microsoft Installer files10434946
Ref: library/msilib doc10435122
Ref: 395710435122
Ref: library/msilib module-msilib10435122
Ref: b610435122
Ref: library/msilib msilib-read-and-write-microsoft-installer-files10435122
Ref: 395810435122
Ref: library/msilib msilib FCICreate10436192
Ref: 395910436192
Ref: library/msilib msilib UuidCreate10436691
Ref: 395a10436691
Ref: library/msilib msilib OpenDatabase10436885
Ref: f1410436885
Ref: library/msilib msilib CreateRecord10437435
Ref: 395b10437435
Ref: library/msilib msilib init_database10437598
Ref: f1510437598
Ref: library/msilib msilib add_data10438167
Ref: 395d10438167
Ref: library/msilib msilib Binary10438739
Ref: 395e10438739
Ref: library/msilib msilib add_tables10438936
Ref: 395f10438936
Ref: library/msilib msilib add_stream10439275
Ref: 396010439275
Ref: library/msilib msilib gen_uuid10439433
Ref: 396110439433
Ref: msilib --- Read and write Microsoft Installer files-Footnote-110439909
Ref: msilib --- Read and write Microsoft Installer files-Footnote-210439983
Ref: msilib --- Read and write Microsoft Installer files-Footnote-310440046
Ref: msilib --- Read and write Microsoft Installer files-Footnote-410440126
Node: Database Objects10440206
Ref: library/msilib database-objects10440331
Ref: 396210440331
Ref: library/msilib id110440331
Ref: 396310440331
Ref: library/msilib msilib Database OpenView10440384
Ref: f1610440384
Ref: library/msilib msilib Database Commit10440540
Ref: 396410440540
Ref: library/msilib msilib Database GetSummaryInformation10440682
Ref: 396510440682
Ref: library/msilib msilib Database Close10440892
Ref: 3b310440892
Ref: Database Objects-Footnote-110441163
Ref: Database Objects-Footnote-210441243
Ref: Database Objects-Footnote-310441323
Ref: Database Objects-Footnote-410441403
Node: View Objects10441483
Ref: library/msilib id210441644
Ref: 396610441644
Ref: library/msilib view-objects10441644
Ref: 396710441644
Ref: library/msilib msilib View Execute10441689
Ref: 396810441689
Ref: library/msilib msilib View GetColumnInfo10441923
Ref: 396910441923
Ref: library/msilib msilib View Fetch10442154
Ref: 396a10442154
Ref: library/msilib msilib View Modify10442273
Ref: 396b10442273
Ref: library/msilib msilib View Close10442830
Ref: 396c10442830
Ref: View Objects-Footnote-110443061
Ref: View Objects-Footnote-210443141
Ref: View Objects-Footnote-310443221
Ref: View Objects-Footnote-410443301
Ref: View Objects-Footnote-510443381
Node: Summary Information Objects10443461
Ref: library/msilib summary-information-objects10443620
Ref: 396d10443620
Ref: library/msilib summary-objects10443620
Ref: 396e10443620
Ref: library/msilib msilib SummaryInformation GetProperty10443695
Ref: fc810443695
Ref: library/msilib msilib SummaryInformation GetPropertyCount10444292
Ref: 396f10444292
Ref: library/msilib msilib SummaryInformation SetProperty10444450
Ref: 397010444450
Ref: library/msilib msilib SummaryInformation Persist10444748
Ref: 397110444748
Ref: Summary Information Objects-Footnote-110445082
Ref: Summary Information Objects-Footnote-210445162
Ref: Summary Information Objects-Footnote-310445242
Ref: Summary Information Objects-Footnote-410445322
Node: Record Objects10445402
Ref: library/msilib id310445555
Ref: 397210445555
Ref: library/msilib record-objects10445555
Ref: 397310445555
Ref: library/msilib msilib Record GetFieldCount10445604
Ref: 397410445604
Ref: library/msilib msilib Record GetInteger10445741
Ref: 397510445741
Ref: library/msilib msilib Record GetString10445884
Ref: 397610445884
Ref: library/msilib msilib Record SetString10446024
Ref: 397710446024
Ref: library/msilib msilib Record SetStream10446192
Ref: 397810446192
Ref: library/msilib msilib Record SetInteger10446397
Ref: 397910446397
Ref: library/msilib msilib Record ClearData10446566
Ref: 397a10446566
Ref: Record Objects-Footnote-110446852
Ref: Record Objects-Footnote-210446932
Ref: Record Objects-Footnote-310447012
Ref: Record Objects-Footnote-410447092
Ref: Record Objects-Footnote-510447172
Node: Errors10447252
Ref: library/msilib errors10447389
Ref: 397b10447389
Ref: library/msilib msi-errors10447389
Ref: 397c10447389
Node: CAB Objects10447537
Ref: library/msilib cab10447677
Ref: 397d10447677
Ref: library/msilib cab-objects10447677
Ref: 397e10447677
Ref: library/msilib msilib CAB10447720
Ref: 397f10447720
Ref: library/msilib msilib CAB append10448082
Ref: 398010448082
Ref: library/msilib msilib CAB commit10448437
Ref: 398110448437
Node: Directory Objects10448647
Ref: library/msilib directory-objects10448792
Ref: 398210448792
Ref: library/msilib msi-directory10448792
Ref: 398310448792
Ref: library/msilib msilib Directory10448847
Ref: 398410448847
Ref: library/msilib msilib Directory start_component10449616
Ref: fc910449616
Ref: library/msilib msilib Directory add_file10450163
Ref: 398510450163
Ref: library/msilib msilib Directory glob10450681
Ref: 398610450681
Ref: library/msilib msilib Directory remove_pyc10450901
Ref: 398710450901
Ref: Directory Objects-Footnote-110451122
Ref: Directory Objects-Footnote-210451202
Ref: Directory Objects-Footnote-310451282
Ref: Directory Objects-Footnote-410451362
Node: Features<3>10451442
Ref: library/msilib features10451587
Ref: 398810451587
Ref: library/msilib id410451587
Ref: 398910451587
Ref: library/msilib msilib Feature10451624
Ref: 398a10451624
Ref: library/msilib msilib Feature set_current10452023
Ref: 398b10452023
Ref: Features<3>-Footnote-110452329
Node: GUI classes10452409
Ref: library/msilib gui-classes10452555
Ref: 398c10452555
Ref: library/msilib msi-gui10452555
Ref: 398d10452555
Ref: library/msilib msilib Control10452836
Ref: 398e10452836
Ref: library/msilib msilib Control event10453010
Ref: 398f10453010
Ref: library/msilib msilib Control mapping10453163
Ref: 399010453163
Ref: library/msilib msilib Control condition10453291
Ref: 399110453291
Ref: library/msilib msilib RadioButtonGroup10453436
Ref: 399210453436
Ref: library/msilib msilib RadioButtonGroup add10453635
Ref: 399310453635
Ref: library/msilib msilib Dialog10453911
Ref: 399410453911
Ref: library/msilib msilib Dialog control10454217
Ref: 399510454217
Ref: library/msilib msilib Dialog text10454586
Ref: 399610454586
Ref: library/msilib msilib Dialog bitmap10454709
Ref: 399710454709
Ref: library/msilib msilib Dialog line10454824
Ref: 399810454824
Ref: library/msilib msilib Dialog pushbutton10454929
Ref: 399910454929
Ref: library/msilib msilib Dialog radiogroup10455093
Ref: 399a10455093
Ref: library/msilib msilib Dialog checkbox10455273
Ref: 399b10455273
Ref: GUI classes-Footnote-110455639
Ref: GUI classes-Footnote-210455719
Ref: GUI classes-Footnote-310455799
Ref: GUI classes-Footnote-410455879
Ref: GUI classes-Footnote-510455959
Ref: GUI classes-Footnote-610456039
Ref: GUI classes-Footnote-710456119
Node: Precomputed tables10456199
Ref: library/msilib msi-tables10456325
Ref: 399c10456325
Ref: library/msilib precomputed-tables10456325
Ref: 399d10456325
Ref: library/msilib msilib schema10456538
Ref: 395c10456538
Ref: library/msilib msilib sequence10456755
Ref: 399e10456755
Ref: library/msilib msilib text10456990
Ref: 399f10456990
Node: msvcrt --- Useful routines from the MS VC++ runtime10457131
Ref: library/msvcrt doc10457350
Ref: 39a010457350
Ref: library/msvcrt module-msvcrt10457350
Ref: b710457350
Ref: library/msvcrt msvcrt-useful-routines-from-the-ms-vc-runtime10457350
Ref: 39a110457350
Node: File Operations10458356
Ref: library/msvcrt file-operations10458479
Ref: 39a210458479
Ref: library/msvcrt msvcrt-files10458479
Ref: 39a310458479
Ref: library/msvcrt msvcrt locking10458530
Ref: 34d010458530
Ref: library/msvcrt msvcrt LK_LOCK10459191
Ref: 39a410459191
Ref: library/msvcrt msvcrt LK_RLCK10459216
Ref: 39a510459216
Ref: library/msvcrt msvcrt LK_NBLCK10459457
Ref: 39a610459457
Ref: library/msvcrt msvcrt LK_NBRLCK10459483
Ref: 39a710459483
Ref: library/msvcrt msvcrt LK_UNLCK10459612
Ref: 39a810459612
Ref: library/msvcrt msvcrt setmode10459719
Ref: 39a910459719
Ref: library/msvcrt msvcrt open_osfhandle10459956
Ref: 34d110459956
Ref: library/msvcrt msvcrt get_osfhandle10460452
Ref: 34cf10460452
Node: Console I/O10460709
Ref: library/msvcrt console-i-o10460856
Ref: 39aa10460856
Ref: library/msvcrt msvcrt-console10460856
Ref: 39ab10460856
Ref: library/msvcrt msvcrt kbhit10460899
Ref: 39ac10460899
Ref: library/msvcrt msvcrt getch10460989
Ref: 39ad10460989
Ref: library/msvcrt msvcrt getwch10461468
Ref: 39ae10461468
Ref: library/msvcrt msvcrt getche10461578
Ref: 39af10461578
Ref: library/msvcrt msvcrt getwche10461723
Ref: 39b010461723
Ref: library/msvcrt msvcrt putch10461835
Ref: 39b110461835
Ref: library/msvcrt msvcrt putwch10461937
Ref: 39b210461937
Ref: library/msvcrt msvcrt ungetch10462059
Ref: 39b310462059
Ref: library/msvcrt msvcrt ungetwch10462268
Ref: 39b410462268
Node: Other Functions10462394
Ref: library/msvcrt msvcrt-other10462517
Ref: 39b510462517
Ref: library/msvcrt other-functions10462517
Ref: 39b610462517
Ref: library/msvcrt msvcrt heapmin10462568
Ref: 39b710462568
Node: winreg --- Windows registry access10462759
Ref: library/winreg doc10462975
Ref: 39b810462975
Ref: library/winreg module-winreg10462975
Ref: 12b10462975
Ref: library/winreg winreg-windows-registry-access10462975
Ref: 39b910462975
Ref: library/winreg exception-changed10463389
Ref: 39bb10463389
Node: Functions<11>10463620
Ref: library/winreg functions10463726
Ref: 39bc10463726
Ref: library/winreg id110463726
Ref: 39bd10463726
Ref: library/winreg winreg CloseKey10463810
Ref: 39be10463810
Ref: library/winreg winreg ConnectRegistry10464131
Ref: 34d610464131
Ref: library/winreg winreg CreateKey10464811
Ref: 34d710464811
Ref: library/winreg winreg CreateKeyEx10465760
Ref: 34d810465760
Ref: library/winreg winreg DeleteKey10467083
Ref: 34d910467083
Ref: library/winreg winreg DeleteKeyEx10467820
Ref: 34da10467820
Ref: library/winreg winreg DeleteValue10469271
Ref: 34db10469271
Ref: library/winreg winreg EnumKey10469636
Ref: 34de10469636
Ref: library/winreg winreg EnumValue10470291
Ref: 34df10470291
Ref: library/winreg winreg ExpandEnvironmentStrings10471545
Ref: 34e010471545
Ref: library/winreg winreg FlushKey10471893
Ref: 39c510471893
Ref: library/winreg winreg LoadKey10472713
Ref: 34e110472713
Ref: library/winreg winreg OpenKey10473903
Ref: 34e210473903
Ref: library/winreg winreg OpenKeyEx10473974
Ref: 39c810473974
Ref: library/winreg winreg QueryInfoKey10475025
Ref: 34e410475025
Ref: library/winreg winreg QueryValue10475918
Ref: 34e610475918
Ref: library/winreg winreg QueryValueEx10476792
Ref: 34e710476792
Ref: library/winreg winreg SaveKey10477665
Ref: 34e810477665
Ref: library/winreg winreg SetValue10478708
Ref: 34e910478708
Ref: library/winreg winreg SetValueEx10479884
Ref: 34ea10479884
Ref: library/winreg winreg DisableReflectionKey10481129
Ref: 34dc10481129
Ref: library/winreg winreg EnableReflectionKey10481758
Ref: 34dd10481758
Ref: library/winreg winreg QueryReflectionKey10482264
Ref: 34e510482264
Ref: Functions<11>-Footnote-110482765
Ref: Functions<11>-Footnote-210482839
Ref: Functions<11>-Footnote-310482916
Node: Constants<10>10482993
Ref: library/winreg constants10483131
Ref: 39cd10483131
Ref: library/winreg id210483131
Ref: 39ce10483131
Node: HKEY_* Constants10483313
Ref: library/winreg hkey-constants10483401
Ref: 39c010483401
Ref: library/winreg id310483401
Ref: 39cf10483401
Ref: library/winreg winreg HKEY_CLASSES_ROOT10483454
Ref: 39d010483454
Ref: library/winreg winreg HKEY_CURRENT_USER10483705
Ref: 39d110483705
Ref: library/winreg winreg HKEY_LOCAL_MACHINE10484008
Ref: 39c710484008
Ref: library/winreg winreg HKEY_USERS10484232
Ref: 39c610484232
Ref: library/winreg winreg HKEY_PERFORMANCE_DATA10484441
Ref: 39d210484441
Ref: library/winreg winreg HKEY_CURRENT_CONFIG10484708
Ref: 39d310484708
Ref: library/winreg winreg HKEY_DYN_DATA10484843
Ref: 39d410484843
Node: Access Rights10484935
Ref: library/winreg access-rights10485043
Ref: 39c210485043
Ref: library/winreg id410485043
Ref: 39d510485043
Ref: library/winreg winreg KEY_ALL_ACCESS10485154
Ref: 39d610485154
Ref: library/winreg winreg KEY_WRITE10485443
Ref: 39c110485443
Ref: library/winreg winreg KEY_READ10485596
Ref: 39c910485596
Ref: library/winreg winreg KEY_EXECUTE10485775
Ref: 39dc10485775
Ref: library/winreg winreg KEY_QUERY_VALUE10485847
Ref: 39d710485847
Ref: library/winreg winreg KEY_SET_VALUE10485935
Ref: 39cb10485935
Ref: library/winreg winreg KEY_CREATE_SUB_KEY10486026
Ref: 39d810486026
Ref: library/winreg winreg KEY_ENUMERATE_SUB_KEYS10486116
Ref: 39d910486116
Ref: library/winreg winreg KEY_NOTIFY10486216
Ref: 39da10486216
Ref: library/winreg winreg KEY_CREATE_LINK10486350
Ref: 39db10486350
Ref: Access Rights-Footnote-110486481
Node: 64-bit Specific10486558
Ref: library/winreg bit-access-rights10486623
Ref: 39dd10486623
Ref: library/winreg bit-specific10486623
Ref: 39de10486623
Ref: library/winreg winreg KEY_WOW64_64KEY10486742
Ref: 39c310486742
Ref: library/winreg winreg KEY_WOW64_32KEY10486879
Ref: 39df10486879
Ref: 64-bit Specific-Footnote-110487052
Node: Value Types10487124
Ref: library/winreg id510487207
Ref: 39e010487207
Ref: library/winreg value-types10487207
Ref: 39cc10487207
Ref: library/winreg winreg REG_BINARY10487302
Ref: 39e110487302
Ref: library/winreg winreg REG_DWORD10487362
Ref: 39e210487362
Ref: library/winreg winreg REG_DWORD_LITTLE_ENDIAN10487411
Ref: 39e310487411
Ref: library/winreg winreg REG_DWORD_BIG_ENDIAN10487543
Ref: 39e410487543
Ref: library/winreg winreg REG_EXPAND_SZ10487626
Ref: 39c410487626
Ref: library/winreg winreg REG_LINK10487755
Ref: 39e510487755
Ref: library/winreg winreg REG_MULTI_SZ10487813
Ref: f8810487813
Ref: library/winreg winreg REG_NONE10487979
Ref: 39e610487979
Ref: library/winreg winreg REG_QWORD10488035
Ref: 5b710488035
Ref: library/winreg winreg REG_QWORD_LITTLE_ENDIAN10488110
Ref: 39e710488110
Ref: library/winreg winreg REG_RESOURCE_LIST10488265
Ref: 39e810488265
Ref: library/winreg winreg REG_FULL_RESOURCE_DESCRIPTOR10488338
Ref: 39e910488338
Ref: library/winreg winreg REG_RESOURCE_REQUIREMENTS_LIST10488411
Ref: 39ea10488411
Ref: library/winreg winreg REG_SZ10488492
Ref: 39ca10488492
Ref: Value Types-Footnote-110488585
Node: Registry Handle Objects10488662
Ref: library/winreg handle-object10488778
Ref: 39ba10488778
Ref: library/winreg registry-handle-objects10488778
Ref: 39eb10488778
Ref: library/winreg winreg PyHKEY Close10489938
Ref: 39bf10489938
Ref: library/winreg winreg PyHKEY Detach10490076
Ref: 34e310490076
Ref: library/winreg winreg PyHKEY __enter__10490680
Ref: 39ec10490680
Ref: library/winreg winreg PyHKEY __exit__10490718
Ref: 39ed10490718
Node: winsound --- Sound-playing interface for Windows10491118
Ref: library/winsound doc10491274
Ref: 39ee10491274
Ref: library/winsound module-winsound10491274
Ref: 12c10491274
Ref: library/winsound winsound-sound-playing-interface-for-windows10491274
Ref: 39ef10491274
Ref: library/winsound winsound Beep10491624
Ref: 5b910491624
Ref: library/winsound winsound PlaySound10492010
Ref: 5bb10492010
Ref: library/winsound winsound MessageBeep10492580
Ref: 5ba10492580
Ref: library/winsound winsound SND_FILENAME10493183
Ref: 39f010493183
Ref: library/winsound winsound SND_ALIAS10493316
Ref: 39f110493316
Ref: library/winsound winsound SND_LOOP10494934
Ref: 39f310494934
Ref: library/winsound winsound SND_MEMORY10495121
Ref: 39f510495121
Ref: library/winsound winsound SND_PURGE10495485
Ref: 39f610495485
Ref: library/winsound winsound SND_ASYNC10495647
Ref: 39f410495647
Ref: library/winsound winsound SND_NODEFAULT10495743
Ref: 39f210495743
Ref: library/winsound winsound SND_NOSTOP10495866
Ref: 39f710495866
Ref: library/winsound winsound SND_NOWAIT10495946
Ref: 39f810495946
Ref: library/winsound winsound MB_ICONASTERISK10496106
Ref: 39f910496106
Ref: library/winsound winsound MB_ICONEXCLAMATION10496184
Ref: 39fa10496184
Ref: library/winsound winsound MB_ICONHAND10496269
Ref: 39fb10496269
Ref: library/winsound winsound MB_ICONQUESTION10496340
Ref: 39fc10496340
Ref: library/winsound winsound MB_OK10496419
Ref: 39fd10496419
Node: Unix Specific Services10496487
Ref: library/unix doc10496649
Ref: 39fe10496649
Ref: library/unix unix10496649
Ref: 39ff10496649
Ref: library/unix unix-specific-services10496649
Ref: 3a0010496649
Node: posix --- The most common POSIX system calls10497896
Ref: library/posix doc10498037
Ref: 3a0110498037
Ref: library/posix module-posix10498037
Ref: d210498037
Ref: library/posix posix-the-most-common-posix-system-calls10498037
Ref: 3a0210498037
Node: Large File Support10499237
Ref: library/posix large-file-support10499368
Ref: 3a0310499368
Ref: library/posix posix-large-files10499368
Ref: 3a0410499368
Node: Notable Module Contents10500419
Ref: library/posix notable-module-contents10500550
Ref: 3a0510500550
Ref: library/posix posix-contents10500550
Ref: 3a0610500550
Ref: library/posix posix environ10500751
Ref: 3a0710500751
Node: pwd --- The password database10501930
Ref: library/pwd doc10502117
Ref: 3a0810502117
Ref: library/pwd module-pwd10502117
Ref: d710502117
Ref: library/pwd pwd-the-password-database10502117
Ref: 3a0910502117
Ref: library/pwd pwd getpwuid10504394
Ref: 101c10504394
Ref: library/pwd pwd getpwnam10504498
Ref: 102f10504498
Ref: library/pwd pwd getpwall10504597
Ref: 3a0a10504597
Node: spwd --- The shadow password database10504908
Ref: library/spwd doc10505077
Ref: 3a0b10505077
Ref: library/spwd module-spwd10505077
Ref: f210505077
Ref: library/spwd spwd-the-shadow-password-database10505077
Ref: 3a0c10505077
Ref: library/spwd spwd getspnam10507371
Ref: 60310507371
Ref: library/spwd spwd getspall10507612
Ref: 3a0d10507612
Node: grp --- The group database10507930
Ref: library/grp doc10508112
Ref: 3a0e10508112
Ref: library/grp grp-the-group-database10508112
Ref: 3a0f10508112
Ref: library/grp module-grp10508112
Ref: 8b10508112
Ref: library/grp grp getgrgid10509656
Ref: 5e410509656
Ref: library/grp grp getgrnam10509994
Ref: 103010509994
Ref: library/grp grp getgrall10510168
Ref: 3a1010510168
Node: crypt --- Function to check Unix passwords10510461
Ref: library/crypt doc10510641
Ref: 3a1110510641
Ref: library/crypt crypt-function-to-check-unix-passwords10510641
Ref: 3a1210510641
Ref: library/crypt module-crypt10510641
Ref: 2910510641
Ref: crypt --- Function to check Unix passwords-Footnote-110511650
Node: Hashing Methods10511714
Ref: library/crypt hashing-methods10511834
Ref: 3a1310511834
Ref: library/crypt crypt METHOD_SHA51210512019
Ref: 3a1410512019
Ref: library/crypt crypt METHOD_SHA25610512208
Ref: 3a1510512208
Ref: library/crypt crypt METHOD_BLOWFISH10512367
Ref: 3a1610512367
Ref: library/crypt crypt METHOD_MD510512546
Ref: 3a1710512546
Ref: library/crypt crypt METHOD_CRYPT10512697
Ref: 60e10512697
Node: Module Attributes10512841
Ref: library/crypt module-attributes10512989
Ref: 3a1810512989
Ref: library/crypt crypt methods10513063
Ref: 3a1910513063
Node: Module Functions<2>10513236
Ref: library/crypt module-functions10513381
Ref: 3a1a10513381
Ref: library/crypt crypt crypt10513496
Ref: 3a1b10513496
Ref: library/crypt crypt mksalt10514989
Ref: 38110514989
Node: Examples<31>10515829
Ref: library/crypt examples10515948
Ref: 3a1c10515948
Node: termios --- POSIX style tty control10517089
Ref: library/termios doc10517277
Ref: 3a1d10517277
Ref: library/termios module-termios10517277
Ref: 10510517277
Ref: library/termios termios-posix-style-tty-control10517277
Ref: 3a1e10517277
Ref: library/termios termios tcgetattr10518254
Ref: 3a1f10518254
Ref: library/termios termios tcsetattr10518831
Ref: 3a2010518831
Ref: library/termios termios tcsendbreak10519323
Ref: 3a2110519323
Ref: library/termios termios tcdrain10519535
Ref: 3a2210519535
Ref: library/termios termios tcflush10519656
Ref: 3a2310519656
Ref: library/termios termios tcflow10519912
Ref: 3a2410519912
Node: Example<16>10520334
Ref: library/termios example10520417
Ref: 3a2510520417
Ref: library/termios termios-example10520417
Ref: 3a2610520417
Node: tty --- Terminal control functions10521176
Ref: library/tty doc10521355
Ref: 3a2710521355
Ref: library/tty module-tty10521355
Ref: 11610521355
Ref: library/tty tty-terminal-control-functions10521355
Ref: 3a2810521355
Ref: library/tty tty setraw10521778
Ref: 3a2910521778
Ref: library/tty tty setcbreak10522012
Ref: 3a2a10522012
Ref: tty --- Terminal control functions-Footnote-110522374
Node: pty --- Pseudo-terminal utilities10522436
Ref: library/pty doc10522622
Ref: 3a2b10522622
Ref: library/pty module-pty10522622
Ref: d610522622
Ref: library/pty pty-pseudo-terminal-utilities10522622
Ref: 3a2c10522622
Ref: library/pty pty fork10523257
Ref: 3a2d10523257
Ref: library/pty pty openpty10523670
Ref: 3a2e10523670
Ref: library/pty pty spawn10523947
Ref: 89d10523947
Ref: pty --- Pseudo-terminal utilities-Footnote-110525970
Ref: pty --- Pseudo-terminal utilities-Footnote-210526032
Node: Example<17>10526075
Ref: library/pty example10526156
Ref: 3a2f10526156
Node: fcntl --- The fcntl and ioctl system calls10527334
Ref: library/fcntl doc10527524
Ref: 3a3010527524
Ref: library/fcntl fcntl-the-fcntl-and-ioctl-system-calls10527524
Ref: 3a3110527524
Ref: library/fcntl module-fcntl10527524
Ref: 7e10527524
Ref: library/fcntl fcntl fcntl10528622
Ref: 26a010528622
Ref: library/fcntl fcntl ioctl10530064
Ref: de310530064
Ref: library/fcntl fcntl flock10532388
Ref: 34ce10532388
Ref: library/fcntl fcntl lockf10532893
Ref: d5710532893
Node: pipes --- Interface to shell pipelines10535612
Ref: library/pipes doc10535808
Ref: 3a3210535808
Ref: library/pipes module-pipes10535808
Ref: cd10535808
Ref: library/pipes pipes-interface-to-shell-pipelines10535808
Ref: 3a3310535808
Ref: library/pipes pipes Template10536357
Ref: 3a3410536357
Ref: pipes --- Interface to shell pipelines-Footnote-110536729
Node: Template Objects10536793
Ref: library/pipes id110536884
Ref: 3a3510536884
Ref: library/pipes template-objects10536884
Ref: 3a3610536884
Ref: library/pipes pipes Template reset10536976
Ref: 3a3710536976
Ref: library/pipes pipes Template clone10537069
Ref: 3a3810537069
Ref: library/pipes pipes Template debug10537157
Ref: 3a3910537157
Ref: library/pipes pipes Template append10537408
Ref: 3a3a10537408
Ref: library/pipes pipes Template prepend10538164
Ref: 3a3b10538164
Ref: library/pipes pipes Template open10538320
Ref: 3a3c10538320
Ref: library/pipes pipes Template copy10538528
Ref: 3a3d10538528
Node: resource --- Resource usage information10538630
Ref: library/resource doc10538827
Ref: 3a3e10538827
Ref: library/resource module-resource10538827
Ref: e110538827
Ref: library/resource resource-resource-usage-information10538827
Ref: 3a3f10538827
Ref: library/resource resource error10539312
Ref: 3a4010539312
Ref: resource --- Resource usage information-Footnote-110539574
Node: Resource Limits10539623
Ref: library/resource resource-limits10539737
Ref: 3a4110539737
Ref: library/resource resource RLIM_INFINITY10540616
Ref: 3a4210540616
Ref: library/resource resource getrlimit10540720
Ref: 3a4310540720
Ref: library/resource resource setrlimit10541012
Ref: 34aa10541012
Ref: library/resource resource prlimit10542168
Ref: 8a410542168
Ref: library/resource resource RLIMIT_CORE10543770
Ref: 34ab10543770
Ref: library/resource resource RLIMIT_CPU10544031
Ref: 3a4510544031
Ref: library/resource resource RLIMIT_FSIZE10544391
Ref: 3a4610544391
Ref: library/resource resource RLIMIT_DATA10544487
Ref: 3a4710544487
Ref: library/resource resource RLIMIT_STACK10544578
Ref: 3a4810544578
Ref: library/resource resource RLIMIT_RSS10544775
Ref: 3a4910544775
Ref: library/resource resource RLIMIT_NPROC10544893
Ref: 3a4a10544893
Ref: library/resource resource RLIMIT_NOFILE10544996
Ref: 3a4410544996
Ref: library/resource resource RLIMIT_OFILE10545110
Ref: 3a4b10545110
Ref: library/resource resource RLIMIT_MEMLOCK10545193
Ref: 3a4c10545193
Ref: library/resource resource RLIMIT_VMEM10545291
Ref: 3a4d10545291
Ref: library/resource resource RLIMIT_AS10545393
Ref: 3a4e10545393
Ref: library/resource resource RLIMIT_MSGQUEUE10545514
Ref: 8a510545514
Ref: library/resource resource RLIMIT_NICE10545703
Ref: 8a610545703
Ref: library/resource resource RLIMIT_RTPRIO10545900
Ref: 8a710545900
Ref: library/resource resource RLIMIT_RTTIME10546059
Ref: 8a810546059
Ref: library/resource resource RLIMIT_SIGPENDING10546316
Ref: 8a910546316
Ref: library/resource resource RLIMIT_SBSIZE10546490
Ref: 8aa10546490
Ref: library/resource resource RLIMIT_SWAP10546793
Ref: 8ab10546793
Ref: library/resource resource RLIMIT_NPTS10547178
Ref: 8ac10547178
Ref: Resource Limits-Footnote-110547393
Node: Resource Usage10547460
Ref: library/resource resource-usage10547574
Ref: 3a4f10547574
Ref: library/resource resource getrusage10547691
Ref: d9e10547691
Ref: library/resource resource getpagesize10552182
Ref: 3a5010552182
Ref: library/resource resource RUSAGE_SELF10552484
Ref: 3a5110552484
Ref: library/resource resource RUSAGE_CHILDREN10552684
Ref: 3a5210552684
Ref: library/resource resource RUSAGE_BOTH10552883
Ref: 3a5310552883
Ref: library/resource resource RUSAGE_THREAD10553080
Ref: 3a5410553080
Node: nis --- Interface to Sun's NIS Yellow Pages10553272
Ref: library/nis doc10553470
Ref: 3a5510553470
Ref: library/nis module-nis10553470
Ref: c010553470
Ref: library/nis nis-interface-to-sun-s-nis-yellow-pages10553470
Ref: 3a5610553470
Ref: library/nis nis match10553921
Ref: d9710553921
Ref: library/nis nis cat10554466
Ref: 3a5810554466
Ref: library/nis nis maps10554930
Ref: d9810554930
Ref: library/nis nis get_default_domain10555156
Ref: 3a5910555156
Ref: library/nis nis error10555299
Ref: 3a5710555299
Node: syslog --- Unix syslog library routines10555387
Ref: library/syslog doc10555537
Ref: 3a5a10555537
Ref: library/syslog module-syslog10555537
Ref: 10010555537
Ref: library/syslog syslog-unix-syslog-library-routines10555537
Ref: 3a5b10555537
Ref: library/syslog syslog syslog10556118
Ref: 34d510556118
Ref: library/syslog syslog openlog10556926
Ref: 34d310556926
Ref: library/syslog syslog closelog10558081
Ref: 34d210558081
Ref: library/syslog syslog setlogmask10558613
Ref: 34d410558613
Node: Examples<32>10559891
Ref: library/syslog examples10559979
Ref: 3a5c10559979
Node: Simple example10560047
Ref: library/syslog simple-example10560110
Ref: 3a5d10560110
Node: Superseded Modules10560622
Ref: library/superseded doc10560776
Ref: 3a5e10560776
Ref: library/superseded superseded10560776
Ref: 3a5f10560776
Ref: library/superseded superseded-modules10560776
Ref: 3a6010560776
Node: optparse --- Parser for command line options10561139
Ref: library/optparse doc10561282
Ref: 3a6110561282
Ref: library/optparse module-optparse10561282
Ref: c410561282
Ref: library/optparse optparse-parser-for-command-line-options10561282
Ref: 3a6210561282
Ref: optparse --- Parser for command line options-Footnote-110564170
Node: Background10564237
Ref: library/optparse background10564348
Ref: 3a6410564348
Ref: library/optparse optparse-background10564348
Ref: 3a6510564348
Node: Terminology10564833
Ref: library/optparse optparse-terminology10564921
Ref: 3a6610564921
Ref: library/optparse terminology10564921
Ref: 3a6710564921
Node: What are options for?10568725
Ref: library/optparse optparse-what-options-for10568856
Ref: 3a6810568856
Ref: library/optparse what-are-options-for10568856
Ref: 3a6910568856
Node: What are positional arguments for?10570537
Ref: library/optparse optparse-what-positional-arguments-for10570648
Ref: 3a6a10570648
Ref: library/optparse what-are-positional-arguments-for10570648
Ref: 3a6b10570648
Node: Tutorial<2>10571979
Ref: library/optparse optparse-tutorial10572114
Ref: 3a6c10572114
Ref: library/optparse tutorial10572114
Ref: 3a6d10572114
Node: Understanding option actions10574720
Ref: library/optparse optparse-understanding-option-actions10574821
Ref: 3a7210574821
Ref: library/optparse understanding-option-actions10574821
Ref: 3a7310574821
Node: The store action10575412
Ref: library/optparse optparse-store-action10575551
Ref: 3a7510575551
Ref: library/optparse the-store-action10575551
Ref: 3a7610575551
Node: Handling boolean flag options10577741
Ref: library/optparse handling-boolean-flag-options10577865
Ref: 3a7710577865
Ref: library/optparse optparse-handling-boolean-options10577865
Ref: 3a7810577865
Node: Other actions10578748
Ref: library/optparse optparse-other-actions10578870
Ref: 3a7910578870
Ref: library/optparse other-actions10578870
Ref: 3a7a10578870
Node: Default values10579288
Ref: library/optparse default-values10579396
Ref: 3a7d10579396
Ref: library/optparse optparse-default-values10579396
Ref: 3a7e10579396
Node: Generating help10581280
Ref: library/optparse generating-help10581400
Ref: 3a7f10581400
Ref: library/optparse optparse-generating-help10581400
Ref: 3a8010581400
Node: Grouping Options10585561
Ref: library/optparse grouping-options10585629
Ref: 3a8110585629
Ref: library/optparse optparse OptionGroup10585960
Ref: 3a8210585960
Ref: library/optparse optparse OptionParser get_option_group10589459
Ref: 3a8310589459
Node: Printing a version string10589735
Ref: library/optparse optparse-printing-version-string10589868
Ref: 3a8410589868
Ref: library/optparse printing-a-version-string10589868
Ref: 3a8510589868
Ref: library/optparse optparse OptionParser print_version10590752
Ref: 3a8610590752
Ref: library/optparse optparse OptionParser get_version10591132
Ref: 3a8810591132
Node: How optparse handles errors10591282
Ref: library/optparse how-optparse-handles-errors10591423
Ref: 3a8910591423
Ref: library/optparse optparse-how-optparse-handles-errors10591423
Ref: 3a8a10591423
Node: Putting it all together10593506
Ref: library/optparse optparse-putting-it-all-together10593613
Ref: 3a8b10593613
Ref: library/optparse putting-it-all-together10593613
Ref: 3a8c10593613
Node: Reference Guide10594531
Ref: library/optparse optparse-reference-guide10594672
Ref: 3a7b10594672
Ref: library/optparse reference-guide10594672
Ref: 3a8d10594672
Node: Creating the parser10595045
Ref: library/optparse creating-the-parser10595146
Ref: 3a8e10595146
Ref: library/optparse optparse-creating-parser10595146
Ref: 3a8f10595146
Ref: library/optparse optparse OptionParser10595291
Ref: 3a6310595291
Node: Populating the parser10598298
Ref: library/optparse optparse-populating-parser10598424
Ref: 3a9110598424
Ref: library/optparse populating-the-parser10598424
Ref: 3a9210598424
Node: Defining options10599710
Ref: library/optparse defining-options10599834
Ref: 3a9310599834
Ref: library/optparse optparse-defining-options10599834
Ref: 3a9410599834
Ref: library/optparse optparse OptionParser add_option10600243
Ref: 207910600243
Node: Option attributes10603128
Ref: library/optparse option-attributes10603254
Ref: 3a9610603254
Ref: library/optparse optparse-option-attributes10603254
Ref: 3a9710603254
Ref: library/optparse optparse Option action10603590
Ref: 3a6e10603590
Ref: library/optparse optparse Option type10603810
Ref: 3a6f10603810
Ref: library/optparse optparse Option dest10604024
Ref: 3a7010604024
Ref: library/optparse optparse Option default10604366
Ref: 3a9910604366
Ref: library/optparse optparse Option nargs10604557
Ref: 3a9b10604557
Ref: library/optparse optparse Option const10604787
Ref: 3a9c10604787
Ref: library/optparse optparse Option choices10604894
Ref: 3a9d10604894
Ref: library/optparse optparse Option callback10605015
Ref: 3a9e10605015
Ref: library/optparse optparse Option callback_args10605244
Ref: 3a9f10605244
Ref: library/optparse optparse Option callback_kwargs10605277
Ref: 3aa010605277
Ref: library/optparse optparse Option help10605438
Ref: 3a7110605438
Ref: library/optparse optparse Option metavar10605783
Ref: 3aa110605783
Node: Standard option actions10605985
Ref: library/optparse optparse-standard-option-actions10606116
Ref: 3a9510606116
Ref: library/optparse standard-option-actions10606116
Ref: 3aa210606116
Node: Standard option types10614203
Ref: library/optparse optparse-standard-option-types10614337
Ref: 3a9810614337
Ref: library/optparse standard-option-types10614337
Ref: 3aa310614337
Node: Parsing arguments<2>10615808
Ref: library/optparse optparse-parsing-arguments10615963
Ref: 3aa410615963
Ref: library/optparse parsing-arguments10615963
Ref: 3aa510615963
Node: Querying and manipulating your option parser10617333
Ref: library/optparse optparse-querying-manipulating-option-parser10617492
Ref: 3aa610617492
Ref: library/optparse querying-and-manipulating-your-option-parser10617492
Ref: 3aa710617492
Ref: library/optparse optparse OptionParser disable_interspersed_args10617801
Ref: 207a10617801
Ref: library/optparse optparse OptionParser enable_interspersed_args10618597
Ref: 3aa810618597
Ref: library/optparse optparse OptionParser get_option10618809
Ref: 3aa910618809
Ref: library/optparse optparse OptionParser has_option10618988
Ref: 3aaa10618988
Ref: library/optparse optparse OptionParser remove_option10619170
Ref: 3aab10619170
Node: Conflicts between options10619562
Ref: library/optparse conflicts-between-options10619711
Ref: 3aac10619711
Ref: library/optparse optparse-conflicts-between-options10619711
Ref: 3a9010619711
Node: Cleanup<2>10622175
Ref: library/optparse cleanup10622293
Ref: 3aad10622293
Ref: library/optparse optparse-cleanup10622293
Ref: 3aae10622293
Node: Other methods10622706
Ref: library/optparse optparse-other-methods10622790
Ref: 3aaf10622790
Ref: library/optparse other-methods10622790
Ref: 3ab010622790
Ref: library/optparse optparse OptionParser set_usage10622892
Ref: 3ab110622892
Ref: library/optparse optparse OptionParser print_usage10623187
Ref: 3a8710623187
Ref: library/optparse optparse OptionParser get_usage10623529
Ref: 3ab210623529
Ref: library/optparse optparse OptionParser set_defaults10623673
Ref: 3a9a10623673
Node: Option Callbacks10624843
Ref: library/optparse option-callbacks10624991
Ref: 3ab310624991
Ref: library/optparse optparse-option-callbacks10624991
Ref: 3a7c10624991
Node: Defining a callback option10626208
Ref: library/optparse defining-a-callback-option10626320
Ref: 3ab410626320
Ref: library/optparse optparse-defining-callback-option10626320
Ref: 3ab510626320
Node: How callbacks are called10628545
Ref: library/optparse how-callbacks-are-called10628694
Ref: 3ab610628694
Ref: library/optparse optparse-how-callbacks-called10628694
Ref: 3ab710628694
Node: Raising errors in a callback10631304
Ref: library/optparse optparse-raising-errors-in-callback10631462
Ref: 3ab810631462
Ref: library/optparse raising-errors-in-a-callback10631462
Ref: 3ab910631462
Node: Callback example 1 trivial callback10631933
Ref: library/optparse callback-example-1-trivial-callback10632104
Ref: 3aba10632104
Ref: library/optparse optparse-callback-example-110632104
Ref: 3abb10632104
Node: Callback example 2 check option order10632552
Ref: library/optparse callback-example-2-check-option-order10632744
Ref: 3abc10632744
Ref: library/optparse optparse-callback-example-210632744
Ref: 3abd10632744
Node: Callback example 3 check option order generalized10633302
Ref: library/optparse callback-example-3-check-option-order-generalized10633503
Ref: 3abe10633503
Ref: library/optparse optparse-callback-example-310633503
Ref: 3abf10633503
Node: Callback example 4 check arbitrary condition10634277
Ref: library/optparse callback-example-4-check-arbitrary-condition10634475
Ref: 3ac010634475
Ref: library/optparse optparse-callback-example-410634475
Ref: 3ac110634475
Node: Callback example 5 fixed arguments10635270
Ref: library/optparse callback-example-5-fixed-arguments10635456
Ref: 3ac210635456
Ref: library/optparse optparse-callback-example-510635456
Ref: 3ac310635456
Node: Callback example 6 variable arguments10636530
Ref: library/optparse callback-example-6-variable-arguments10636663
Ref: 3ac410636663
Ref: library/optparse optparse-callback-example-610636663
Ref: 3ac510636663
Node: Extending optparse10638768
Ref: library/optparse extending-optparse10638892
Ref: 3ac610638892
Ref: library/optparse optparse-extending-optparse10638892
Ref: 3a7410638892
Node: Adding new types10639229
Ref: library/optparse adding-new-types10639327
Ref: 3ac710639327
Ref: library/optparse optparse-adding-new-types10639327
Ref: 3ac810639327
Ref: library/optparse optparse Option TYPES10639616
Ref: 3ac910639616
Ref: library/optparse optparse Option TYPE_CHECKER10639772
Ref: 3aca10639772
Node: Adding new actions10642780
Ref: library/optparse adding-new-actions10642878
Ref: 3acb10642878
Ref: library/optparse optparse-adding-new-actions10642878
Ref: 3acc10642878
Ref: library/optparse optparse Option ACTIONS10643965
Ref: 3acd10643965
Ref: library/optparse optparse Option STORE_ACTIONS10644038
Ref: 3ace10644038
Ref: library/optparse optparse Option TYPED_ACTIONS10644124
Ref: 3acf10644124
Ref: library/optparse optparse Option ALWAYS_TYPED_ACTIONS10644210
Ref: 3ad010644210
Node: imp --- Access the import internals10647509
Ref: library/imp doc10647652
Ref: 3ad110647652
Ref: library/imp imp-access-the-import-internals10647652
Ref: 3ad210647652
Ref: library/imp module-imp10647652
Ref: 9a10647652
Ref: library/imp imp get_magic10648094
Ref: 86810648094
Ref: library/imp imp get_suffixes10648374
Ref: 3ad310648374
Ref: library/imp imp find_module10649101
Ref: 3ad710649101
Ref: library/imp imp load_module10651603
Ref: 3adb10651603
Ref: library/imp imp new_module10653464
Ref: 3adc10653464
Ref: library/imp imp reload10653702
Ref: c7510653702
Ref: library/imp imp cache_from_source10656931
Ref: 3add10656931
Ref: library/imp imp source_from_cache10657958
Ref: 3adf10657958
Ref: library/imp imp get_tag10658673
Ref: 3ade10658673
Ref: library/imp imp lock_held10659213
Ref: 3ae010659213
Ref: library/imp imp acquire_lock10660127
Ref: 3ae110660127
Ref: library/imp imp release_lock10660808
Ref: 3ae210660808
Ref: library/imp imp PY_SOURCE10661324
Ref: 3ad410661324
Ref: library/imp imp PY_COMPILED10661421
Ref: 3ad510661421
Ref: library/imp imp C_EXTENSION10661534
Ref: 3ad610661534
Ref: library/imp imp PKG_DIRECTORY10661655
Ref: 3ada10661655
Ref: library/imp imp C_BUILTIN10661762
Ref: 3ad810661762
Ref: library/imp imp PY_FROZEN10661863
Ref: 3ad910661863
Ref: library/imp imp NullImporter10661962
Ref: 9c010661962
Ref: library/imp imp NullImporter find_module10662357
Ref: 3ae310662357
Ref: imp --- Access the import internals-Footnote-110662830
Ref: imp --- Access the import internals-Footnote-210662892
Ref: imp --- Access the import internals-Footnote-310662941
Ref: imp --- Access the import internals-Footnote-410662990
Ref: imp --- Access the import internals-Footnote-510663039
Ref: imp --- Access the import internals-Footnote-610663088
Ref: imp --- Access the import internals-Footnote-710663137
Node: Examples<33>10663186
Ref: library/imp examples10663270
Ref: 3ae410663270
Ref: library/imp examples-imp10663270
Ref: 3ae510663270
Node: Undocumented Modules10664276
Ref: library/undoc doc10664399
Ref: 3ae610664399
Ref: library/undoc undoc10664399
Ref: 3ae710664399
Ref: library/undoc undocumented-modules10664399
Ref: 3ae810664399
Node: Platform specific modules10664846
Ref: library/undoc platform-specific-modules10664928
Ref: 3ae910664928
Node: Extending and Embedding the Python Interpreter10665319
Ref: extending/index doc10665489
Ref: 3aea10665489
Ref: extending/index extending-and-embedding-the-python-interpreter10665489
Ref: 3aeb10665489
Ref: extending/index extending-index10665489
Ref: 120210665489
Node: Recommended third party tools10666800
Ref: extending/index recommended-third-party-tools10666966
Ref: 3aec10666966
Ref: Recommended third party tools-Footnote-110667663
Ref: Recommended third party tools-Footnote-210667690
Ref: Recommended third party tools-Footnote-310667726
Ref: Recommended third party tools-Footnote-410667754
Ref: Recommended third party tools-Footnote-510667788
Node: Creating extensions without third party tools10667861
Ref: extending/index creating-extensions-without-third-party-tools10668089
Ref: 3aed10668089
Node: 以 C 或 C++ 擴充 Python10668702
Ref: extending/extending doc10668853
Ref: 3aee10668853
Ref: extending/extending extending-intro10668853
Ref: 3aef10668853
Ref: extending/extending extending-python-with-c-or-c10668853
Ref: 3af010668853
Ref: 以 C 或 C++ 擴充 Python-Footnote-110670774
Node: A Simple Example10670811
Ref: extending/extending a-simple-example10670932
Ref: 3af110670932
Ref: extending/extending extending-simpleexample10670932
Ref: 3af210670932
Ref: A Simple Example-Footnote-110674669
Node: Intermezzo Errors and Exceptions10674823
Ref: extending/extending extending-errors10674972
Ref: 3af410674972
Ref: extending/extending intermezzo-errors-and-exceptions10674972
Ref: 3af510674972
Node: Back to the Example10682086
Ref: extending/extending back-to-the-example10682272
Ref: 3afc10682272
Ref: extending/extending backtoexample10682272
Ref: 3afd10682272
Node: The Module's Method Table and Initialization Function10683930
Ref: extending/extending methodtable10684107
Ref: 3aff10684107
Ref: extending/extending the-module-s-method-table-and-initialization-function10684107
Ref: 3b0010684107
Ref: The Module's Method Table and Initialization Function-Footnote-110689524
Node: Compilation and Linkage10689573
Ref: extending/extending compilation10689762
Ref: 3b0310689762
Ref: extending/extending compilation-and-linkage10689762
Ref: 3b0410689762
Node: Calling Python Functions from C10691236
Ref: extending/extending calling-python-functions-from-c10691416
Ref: 3b0610691416
Ref: extending/extending callingpython10691416
Ref: 3b0710691416
Node: Extracting Parameters in Extension Functions10698088
Ref: extending/extending extracting-parameters-in-extension-functions10698287
Ref: 3b0b10698287
Ref: extending/extending parsetuple10698287
Ref: 3af310698287
Node: Keyword Parameters for Extension Functions10700969
Ref: extending/extending keyword-parameters-for-extension-functions10701162
Ref: 3b0c10701162
Ref: extending/extending parsetupleandkeywords10701162
Ref: 3b0d10701162
Node: Building Arbitrary Values10703879
Ref: extending/extending building-arbitrary-values10704044
Ref: 3b0e10704044
Ref: extending/extending buildvalue10704044
Ref: 3b0f10704044
Node: Reference Counts10706130
Ref: extending/extending refcounts10706278
Ref: 3b0810706278
Ref: extending/extending reference-counts10706278
Ref: 3b1010706278
Node: Reference Counting in Python10711051
Ref: extending/extending refcountsinpython10711156
Ref: 3b1110711156
Ref: extending/extending reference-counting-in-python10711156
Ref: 3b1210711156
Ref: Reference Counting in Python-Footnote-110713529
Ref: Reference Counting in Python-Footnote-210713653
Node: Ownership Rules10713828
Ref: extending/extending ownership-rules10713950
Ref: 3b1310713950
Ref: extending/extending ownershiprules10713950
Ref: 3b1410713950
Node: Thin Ice10716415
Ref: extending/extending thin-ice10716522
Ref: 3b1e10716522
Ref: extending/extending thinice10716522
Ref: 3b1f10716522
Node: NULL Pointers10719804
Ref: extending/extending null-pointers10719887
Ref: 3b2110719887
Ref: extending/extending nullpointers10719887
Ref: 3b2210719887
Ref: NULL Pointers-Footnote-110721504
Node: Writing Extensions in C++10721641
Ref: extending/extending cplusplus10721805
Ref: 3b2310721805
Ref: extending/extending writing-extensions-in-c10721805
Ref: 3b2410721805
Node: Providing a C API for an Extension Module10722525
Ref: extending/extending providing-a-c-api-for-an-extension-module10722664
Ref: 3b2510722664
Ref: extending/extending using-capsules10722664
Ref: cf610722664
Node: Defining Extension Types Tutorial10731520
Ref: extending/newtypes_tutorial doc10731720
Ref: 3b2910731720
Ref: extending/newtypes_tutorial defining-extension-types-tutorial10731720
Ref: 3b2a10731720
Ref: extending/newtypes_tutorial defining-new-types10731720
Ref: 3b2b10731720
Node: The Basics10732364
Ref: extending/newtypes_tutorial dnt-basics10732497
Ref: 3b2c10732497
Ref: extending/newtypes_tutorial the-basics10732497
Ref: 3b2d10732497
Ref: The Basics-Footnote-110741810
Node: Adding data and methods to the Basic example10741880
Ref: extending/newtypes_tutorial adding-data-and-methods-to-the-basic-example10742066
Ref: 3b3810742066
Ref: Adding data and methods to the Basic example-Footnote-110758328
Ref: Adding data and methods to the Basic example-Footnote-210758425
Node: Providing finer control over data attributes10758566
Ref: extending/newtypes_tutorial providing-finer-control-over-data-attributes10758778
Ref: 3b4310758778
Ref: Providing finer control over data attributes-Footnote-110768681
Node: Supporting cyclic garbage collection10769065
Ref: extending/newtypes_tutorial supporting-cyclic-garbage-collection10769256
Ref: 3b4510769256
Ref: Supporting cyclic garbage collection-Footnote-110779899
Node: Subclassing other types10780077
Ref: extending/newtypes_tutorial subclassing-other-types10780215
Ref: 3b4910780215
Node: Defining Extension Types Assorted Topics10785464
Ref: extending/newtypes doc10785666
Ref: 3b4c10785666
Ref: extending/newtypes defining-extension-types-assorted-topics10785666
Ref: 3b4d10785666
Ref: extending/newtypes new-types-topics10785666
Ref: 3b4e10785666
Ref: extending/newtypes dnt-type-methods10785763
Ref: 3b4f10785763
Node: Finalization and De-allocation10790196
Ref: extending/newtypes finalization-and-de-allocation10790331
Ref: 3b5010790331
Ref: Finalization and De-allocation-Footnote-110793473
Node: Object Presentation10793522
Ref: extending/newtypes object-presentation10793686
Ref: 3b5310793686
Node: Attribute Management10795340
Ref: extending/newtypes attribute-management10795491
Ref: 3b5710795491
Node: Generic Attribute Management10797045
Ref: extending/newtypes generic-attribute-management10797173
Ref: 3b3f10797173
Ref: extending/newtypes id110797173
Ref: 3b5810797173
Node: Type-specific Attribute Management10801431
Ref: extending/newtypes type-specific-attribute-management10801559
Ref: 3b5b10801559
Node: Object Comparison10803327
Ref: extending/newtypes object-comparison10803484
Ref: 3b5e10803484
Node: Abstract Protocol Support10805253
Ref: extending/newtypes abstract-protocol-support10805412
Ref: 3b6110805412
Node: Weak Reference Support10811080
Ref: extending/newtypes weak-reference-support10811238
Ref: 3b6710811238
Ref: extending/newtypes weakref-support10811238
Ref: 199410811238
Node: More Suggestions10813153
Ref: extending/newtypes more-suggestions10813277
Ref: 3b6910813277
Node: Building C and C++ Extensions10814246
Ref: extending/building doc10814455
Ref: 3b6b10814455
Ref: extending/building building10814455
Ref: 3b0510814455
Ref: extending/building building-c-and-c-extensions10814455
Ref: 3b6c10814455
Ref: extending/building c PyInit_modulename10814951
Ref: 3b6d10814951
Ref: Building C and C++ Extensions-Footnote-110816306
Node: Building C and C++ Extensions with distutils10816355
Ref: extending/building building-c-and-c-extensions-with-distutils10816509
Ref: 3b7010816509
Node: Distributing your extension modules10820474
Ref: extending/building distributing10820628
Ref: 3b7210820628
Ref: extending/building distributing-your-extension-modules10820628
Ref: 3b7310820628
Node: Building C and C++ Extensions on Windows10821479
Ref: extending/windows doc10821639
Ref: 3b7510821639
Ref: extending/windows building-c-and-c-extensions-on-windows10821639
Ref: 3b7610821639
Ref: extending/windows building-on-windows10821639
Ref: 13a110821639
Node: A Cookbook Approach10822910
Ref: extending/windows a-cookbook-approach10823051
Ref: 3b7710823051
Ref: extending/windows win-cookbook10823051
Ref: 3b7810823051
Ref: A Cookbook Approach-Footnote-110823674
Node: Differences Between Unix and Windows10823751
Ref: extending/windows differences-between-unix-and-windows10823923
Ref: 3b7910823923
Ref: extending/windows dynamic-linking10823923
Ref: 3b7a10823923
Node: Using DLLs in Practice10826846
Ref: extending/windows using-dlls-in-practice10826990
Ref: 3b7b10826990
Ref: extending/windows win-dlls10826990
Ref: 3b7c10826990
Node: Embedding the CPython runtime in a larger application10828545
Ref: extending/index embedding-the-cpython-runtime-in-a-larger-application10828735
Ref: 3b7d10828735
Node: 在其它 App 內嵌入 Python10829168
Ref: extending/embedding doc10829288
Ref: 3b7e10829288
Ref: extending/embedding embedding10829288
Ref: 3b7f10829288
Ref: extending/embedding embedding-python-in-another-application10829288
Ref: 3b8010829288
Node: Very High Level Embedding10831605
Ref: extending/embedding high-level-embedding10831750
Ref: 3b8310831750
Ref: extending/embedding very-high-level-embedding10831750
Ref: 3b8410831750
Node: Beyond Very High Level Embedding An overview10833513
Ref: extending/embedding beyond-very-high-level-embedding-an-overview10833681
Ref: 3b8510833681
Ref: extending/embedding lower-level-embedding10833681
Ref: 3b8610833681
Node: Pure Embedding10835400
Ref: extending/embedding id110835568
Ref: 3b8710835568
Ref: extending/embedding pure-embedding10835568
Ref: 3b8810835568
Node: Extending Embedded Python10840189
Ref: extending/embedding extending-embedded-python10840336
Ref: 3b8b10840336
Ref: extending/embedding extending-with-embedding10840336
Ref: 3b8c10840336
Node: Embedding Python in C++10842316
Ref: extending/embedding embedding-python-in-c10842494
Ref: 3b8d10842494
Ref: extending/embedding embeddingincplusplus10842494
Ref: 3b8e10842494
Node: Compiling and Linking under Unix-like systems10842866
Ref: extending/embedding compiling10843010
Ref: 3b8910843010
Ref: extending/embedding compiling-and-linking-under-unix-like-systems10843010
Ref: 3b8f10843010
Node: Python / C API 參考手冊10845190
Ref: c-api/index doc10845341
Ref: 3b9110845341
Ref: c-api/index c-api-index10845341
Ref: 120310845341
Ref: c-api/index python-c-api-reference-manual10845341
Ref: 3b9210845341
Node: 簡介<12>10846106
Ref: c-api/intro doc10846224
Ref: 3b9310846224
Ref: c-api/intro api-intro10846224
Ref: 3b9410846224
Ref: c-api/intro introduction10846224
Ref: 3b9510846224
Node: Coding standards10847759
Ref: c-api/intro coding-standards10847844
Ref: 3b9610847844
Ref: Coding standards-Footnote-110848283
Node: Include Files10848332
Ref: c-api/intro api-includes10848439
Ref: 3b9710848439
Ref: c-api/intro include-files10848439
Ref: 3b9810848439
Node: Useful macros10850964
Ref: c-api/intro useful-macros10851089
Ref: 3b9910851089
Ref: c-api/intro c Py_UNREACHABLE10851376
Ref: 42810851376
Ref: c-api/intro c Py_ABS10851767
Ref: 3b9a10851767
Ref: c-api/intro c Py_MIN10851861
Ref: 3b9b10851861
Ref: c-api/intro c Py_MAX10851974
Ref: 3b9c10851974
Ref: c-api/intro c Py_STRINGIFY10852087
Ref: 3b9d10852087
Ref: c-api/intro c Py_MEMBER_SIZE10852237
Ref: 3b9e10852237
Ref: c-api/intro c Py_CHARMASK10852379
Ref: 3b9f10852379
Ref: c-api/intro c Py_GETENV10852562
Ref: 3ba010852562
Ref: c-api/intro c Py_UNUSED10852747
Ref: 3ba110852747
Ref: c-api/intro c Py_DEPRECATED10852968
Ref: 3ba210852968
Ref: c-api/intro c PyDoc_STRVAR10853234
Ref: f3110853234
Ref: c-api/intro c PyDoc_STR10853815
Ref: 3ba310853815
Ref: Useful macros-Footnote-110854365
Ref: Useful macros-Footnote-210854414
Node: Objects Types and Reference Counts10854463
Ref: c-api/intro api-objects10854589
Ref: 3ba410854589
Ref: c-api/intro objects-types-and-reference-counts10854589
Ref: 3ba510854589
Node: Reference Counts<2>10855970
Ref: c-api/intro api-refcounts10856074
Ref: 3ba610856074
Ref: c-api/intro reference-counts10856074
Ref: 3ba710856074
Node: Reference Count Details10859778
Ref: c-api/intro api-refcountdetails10859857
Ref: 3ba810859857
Ref: c-api/intro reference-count-details10859857
Ref: 3ba910859857
Node: Types10867057
Ref: c-api/intro api-types10867161
Ref: 3bad10867161
Ref: c-api/intro types10867161
Ref: 3bae10867161
Node: Exceptions<16>10867639
Ref: c-api/intro api-exceptions10867767
Ref: 3baf10867767
Ref: c-api/intro exceptions10867767
Ref: 3bb010867767
Node: 嵌入式Python10873906
Ref: c-api/intro api-embedding10874016
Ref: 3bb210874016
Ref: c-api/intro embedding-python10874016
Ref: 3bb310874016
Node: Debugging Builds10877198
Ref: c-api/intro api-debugging10877285
Ref: 3bb810877285
Ref: c-api/intro debugging-builds10877285
Ref: 3bb910877285
Node: Stable Application Binary Interface10879749
Ref: c-api/stable doc10879901
Ref: 3bba10879901
Ref: c-api/stable stable10879901
Ref: 3bbb10879901
Ref: c-api/stable stable-application-binary-interface10879901
Ref: 3bbc10879901
Ref: Stable Application Binary Interface-Footnote-110881870
Node: The Very High Level Layer10881919
Ref: c-api/veryhigh doc10882073
Ref: 3bbd10882073
Ref: c-api/veryhigh the-very-high-level-layer10882073
Ref: 3bbe10882073
Ref: c-api/veryhigh veryhigh10882073
Ref: 3bbf10882073
Ref: c-api/veryhigh c Py_Main10883094
Ref: 4bc10883094
Ref: c-api/veryhigh c Py_BytesMain10884051
Ref: 17710884051
Ref: c-api/veryhigh c PyRun_AnyFile10884216
Ref: 3bc010884216
Ref: c-api/veryhigh c PyRun_AnyFileFlags10884439
Ref: 3bc210884439
Ref: c-api/veryhigh c PyRun_AnyFileEx10884679
Ref: 3bc310884679
Ref: c-api/veryhigh c PyRun_AnyFileExFlags10884906
Ref: 3bc110884906
Ref: c-api/veryhigh c PyRun_SimpleString10885471
Ref: 3b8110885471
Ref: c-api/veryhigh c PyRun_SimpleStringFlags10885696
Ref: 3bc510885696
Ref: c-api/veryhigh c PyRun_SimpleFile10886377
Ref: 3b8210886377
Ref: c-api/veryhigh c PyRun_SimpleFileEx10886600
Ref: 3bc610886600
Ref: c-api/veryhigh c PyRun_SimpleFileExFlags10886819
Ref: ecc10886819
Ref: c-api/veryhigh c PyRun_InteractiveOne10887511
Ref: 3bc710887511
Ref: c-api/veryhigh c PyRun_InteractiveOneFlags10887717
Ref: 3bc810887717
Ref: c-api/veryhigh c PyRun_InteractiveLoop10888477
Ref: 3bc410888477
Ref: c-api/veryhigh c PyRun_InteractiveLoopFlags10888685
Ref: 3bc910888685
Ref: c-api/veryhigh c PyOS_InputHook10889143
Ref: 3bca10889143
Ref: c-api/veryhigh c PyOS_ReadlineFunctionPointer10889624
Ref: 97110889624
Ref: c-api/veryhigh c PyParser_SimpleParseString10890643
Ref: 3bcb10890643
Ref: c-api/veryhigh c PyParser_SimpleParseStringFlags10890915
Ref: 3bcd10890915
Ref: c-api/veryhigh c PyParser_SimpleParseStringFlagsFilename10891176
Ref: 3bcc10891176
Ref: c-api/veryhigh c PyParser_SimpleParseFile10891693
Ref: 3bce10891693
Ref: c-api/veryhigh c PyParser_SimpleParseFileFlags10891935
Ref: 3bcf10891935
Ref: c-api/veryhigh c PyRun_String10892218
Ref: fb810892218
Ref: c-api/veryhigh c PyRun_StringFlags10892488
Ref: 3bd010892488
Ref: c-api/veryhigh c PyRun_File10893147
Ref: 3bd110893147
Ref: c-api/veryhigh c PyRun_FileEx10893459
Ref: 3bd310893459
Ref: c-api/veryhigh c PyRun_FileFlags10893757
Ref: 3bd410893757
Ref: c-api/veryhigh c PyRun_FileExFlags10894078
Ref: 3bd210894078
Ref: c-api/veryhigh c Py_CompileString10894663
Ref: 3bd510894663
Ref: c-api/veryhigh c Py_CompileStringFlags10894926
Ref: 3bd610894926
Ref: c-api/veryhigh c Py_CompileStringObject10895218
Ref: 3bd810895218
Ref: c-api/veryhigh c Py_CompileStringExFlags10896331
Ref: 3bd710896331
Ref: c-api/veryhigh c PyEval_EvalCode10896701
Ref: 3bd910896701
Ref: c-api/veryhigh c PyEval_EvalCodeEx10897021
Ref: 3bda10897021
Ref: c-api/veryhigh c PyFrameObject10897696
Ref: 97610897696
Ref: c-api/veryhigh c PyEval_EvalFrame10897859
Ref: 3bdb10897859
Ref: c-api/veryhigh c PyEval_EvalFrameEx10898092
Ref: 96c10898092
Ref: c-api/veryhigh c PyEval_MergeCompilerFlags10898773
Ref: 3bdc10898773
Ref: c-api/veryhigh c Py_eval_input10898963
Ref: 3bdd10898963
Ref: c-api/veryhigh c Py_file_input10899119
Ref: 3bde10899119
Ref: c-api/veryhigh c Py_single_input10899403
Ref: 3bdf10899403
Ref: c-api/veryhigh c PyCompilerFlags10899627
Ref: 2cd10899627
Ref: c-api/veryhigh c PyCompilerFlags cf_flags10900160
Ref: 3be010900160
Ref: c-api/veryhigh c PyCompilerFlags cf_feature_version10900226
Ref: 3be110900226
Ref: c-api/veryhigh c CO_FUTURE_DIVISION10900581
Ref: 3be210900581
Ref: The Very High Level Layer-Footnote-110900794
Node: 參照計數10900843
Ref: c-api/refcounting doc10900974
Ref: 3be310900974
Ref: c-api/refcounting countingrefs10900974
Ref: 3be410900974
Ref: c-api/refcounting reference-counting10900974
Ref: 3be510900974
Ref: c-api/refcounting c Py_INCREF10901091
Ref: 26610901091
Ref: c-api/refcounting c Py_XINCREF10901311
Ref: 26810901311
Ref: c-api/refcounting c Py_DECREF10901483
Ref: 26710901483
Ref: c-api/refcounting c Py_XDECREF10902593
Ref: 26910902593
Ref: c-api/refcounting c Py_CLEAR10902869
Ref: 3b4710902869
Node: 例外處理10904012
Ref: c-api/exceptions doc10904124
Ref: 3be610904124
Ref: c-api/exceptions exception-handling10904124
Ref: 3be710904124
Ref: c-api/exceptions exceptionhandling10904124
Ref: 364f10904124
Node: Printing and clearing10906424
Ref: c-api/exceptions printing-and-clearing10906521
Ref: 3be810906521
Ref: c-api/exceptions c PyErr_Clear10906578
Ref: 97010906578
Ref: c-api/exceptions c PyErr_PrintEx10906707
Ref: 3be910906707
Ref: c-api/exceptions c PyErr_Print10907395
Ref: f0e10907395
Ref: c-api/exceptions c PyErr_WriteUnraisable10907470
Ref: fc310907470
Node: Raising exceptions10908176
Ref: c-api/exceptions raising-exceptions10908298
Ref: 3bea10908298
Ref: c-api/exceptions c PyErr_SetString10908538
Ref: 3af610908538
Ref: c-api/exceptions c PyErr_SetObject10908946
Ref: 3af810908946
Ref: c-api/exceptions c PyErr_Format10909173
Ref: 7af10909173
Ref: c-api/exceptions c PyErr_FormatV10909622
Ref: 7ae10909622
Ref: c-api/exceptions c PyErr_SetNone10909911
Ref: 3beb10909911
Ref: c-api/exceptions c PyErr_BadArgument10910030
Ref: 3bec10910030
Ref: c-api/exceptions c PyErr_NoMemory10910281
Ref: 3afa10910281
Ref: c-api/exceptions c PyErr_SetFromErrno10910561
Ref: 3af710910561
Ref: c-api/exceptions c PyErr_SetFromErrnoWithFilenameObject10911439
Ref: 3bee10911439
Ref: c-api/exceptions c PyErr_SetFromErrnoWithFilenameObjects10911916
Ref: 3bef10911916
Ref: c-api/exceptions c PyErr_SetFromErrnoWithFilename10912308
Ref: 3bf010912308
Ref: c-api/exceptions c PyErr_SetFromWindowsErr10912647
Ref: 3bf110912647
Ref: c-api/exceptions c PyErr_SetExcFromWindowsErr10913417
Ref: 3bf210913417
Ref: c-api/exceptions c PyErr_SetFromWindowsErrWithFilename10913715
Ref: 3bf310913715
Ref: c-api/exceptions c PyErr_SetExcFromWindowsErrWithFilenameObject10914094
Ref: 3bf410914094
Ref: c-api/exceptions c PyErr_SetExcFromWindowsErrWithFilenameObjects10914442
Ref: 3bf510914442
Ref: c-api/exceptions c PyErr_SetExcFromWindowsErrWithFilename10914820
Ref: 3bf610914820
Ref: c-api/exceptions c PyErr_SetImportError10915164
Ref: 5fd10915164
Ref: c-api/exceptions c PyErr_SyntaxLocationObject10915615
Ref: 3bf710915615
Ref: c-api/exceptions c PyErr_SyntaxLocationEx10916019
Ref: 3bf810916019
Ref: c-api/exceptions c PyErr_SyntaxLocation10916308
Ref: 3bf910916308
Ref: c-api/exceptions c PyErr_BadInternalCall10916479
Ref: 3bfa10916479
Node: Issuing warnings10916775
Ref: c-api/exceptions issuing-warnings10916904
Ref: 3bfb10916904
Ref: c-api/exceptions c PyErr_WarnEx10917800
Ref: db610917800
Ref: c-api/exceptions c PyErr_SetImportErrorSubclass10918945
Ref: 5d010918945
Ref: c-api/exceptions c PyErr_WarnExplicitObject10919279
Ref: 3bfd10919279
Ref: c-api/exceptions c PyErr_WarnExplicit10919816
Ref: 3bfe10919816
Ref: c-api/exceptions c PyErr_WarnFormat10920203
Ref: 3bff10920203
Ref: c-api/exceptions c PyErr_ResourceWarning10920517
Ref: 5d110920517
Node: Querying the error indicator10920833
Ref: c-api/exceptions querying-the-error-indicator10920962
Ref: 3c0010920962
Ref: c-api/exceptions c PyErr_Occurred10921033
Ref: 3af910921033
Ref: c-api/exceptions c PyErr_ExceptionMatches10921829
Ref: 3bb110921829
Ref: c-api/exceptions c PyErr_GivenExceptionMatches10922107
Ref: 3c0110922107
Ref: c-api/exceptions c PyErr_Fetch10922504
Ref: 96f10922504
Ref: c-api/exceptions c PyErr_Restore10923424
Ref: 3b5110923424
Ref: c-api/exceptions c PyErr_NormalizeException10924417
Ref: fc410924417
Ref: c-api/exceptions c PyErr_GetExcInfo10925284
Ref: 3c0210925284
Ref: c-api/exceptions c PyErr_SetExcInfo10926036
Ref: 3c0310926036
Node: Signal Handling<2>10926844
Ref: c-api/exceptions signal-handling10926974
Ref: 3c0410926974
Ref: c-api/exceptions c PyErr_CheckSignals10927019
Ref: 3bed10927019
Ref: c-api/exceptions c PyErr_SetInterrupt10927683
Ref: 3c0510927683
Ref: c-api/exceptions c PySignal_SetWakeupFd10928077
Ref: d4b10928077
Node: Exception Classes10928736
Ref: c-api/exceptions exception-classes10928855
Ref: 3c0610928855
Ref: c-api/exceptions c PyErr_NewException10928904
Ref: c0510928904
Ref: c-api/exceptions c PyErr_NewExceptionWithDoc10929840
Ref: c0410929840
Node: Exception Objects10930241
Ref: c-api/exceptions exception-objects10930367
Ref: 3c0710930367
Ref: c-api/exceptions c PyException_GetTraceback10930416
Ref: 3c0810930416
Ref: c-api/exceptions c PyException_SetTraceback10930722
Ref: fc510930722
Ref: c-api/exceptions c PyException_GetContext10930895
Ref: 3c0910930895
Ref: c-api/exceptions c PyException_SetContext10931265
Ref: 3c0a10931265
Ref: c-api/exceptions c PyException_GetCause10931548
Ref: 3c0b10931548
Ref: c-api/exceptions c PyException_SetCause10931863
Ref: 3c0c10931863
Node: Unicode Exception Objects10932269
Ref: c-api/exceptions unicode-exception-objects10932395
Ref: 3c0d10932395
Ref: c-api/exceptions unicodeexceptions10932395
Ref: 3c0e10932395
Ref: c-api/exceptions c PyUnicodeDecodeError_Create10932542
Ref: 3c0f10932542
Ref: c-api/exceptions c PyUnicodeEncodeError_Create10932963
Ref: 3c1010932963
Ref: c-api/exceptions c PyUnicodeTranslateError_Create10933570
Ref: 3c1110933570
Ref: c-api/exceptions c PyUnicodeDecodeError_GetEncoding10934137
Ref: 3c1210934137
Ref: c-api/exceptions c PyUnicodeEncodeError_GetEncoding10934210
Ref: 3c1310934210
Ref: c-api/exceptions c PyUnicodeDecodeError_GetObject10934389
Ref: 3c1410934389
Ref: c-api/exceptions c PyUnicodeEncodeError_GetObject10934460
Ref: 3c1510934460
Ref: c-api/exceptions c PyUnicodeTranslateError_GetObject10934531
Ref: 3c1610934531
Ref: c-api/exceptions c PyUnicodeDecodeError_GetStart10934709
Ref: 3c1710934709
Ref: c-api/exceptions c PyUnicodeEncodeError_GetStart10934802
Ref: 3c1810934802
Ref: c-api/exceptions c PyUnicodeTranslateError_GetStart10934895
Ref: 3c1910934895
Ref: c-api/exceptions c PyUnicodeDecodeError_SetStart10935174
Ref: 3c1a10935174
Ref: c-api/exceptions c PyUnicodeEncodeError_SetStart10935266
Ref: 3c1b10935266
Ref: c-api/exceptions c PyUnicodeTranslateError_SetStart10935358
Ref: 3c1c10935358
Ref: c-api/exceptions c PyUnicodeDecodeError_GetEnd10935581
Ref: 3c1d10935581
Ref: c-api/exceptions c PyUnicodeEncodeError_GetEnd10935670
Ref: 3c1e10935670
Ref: c-api/exceptions c PyUnicodeTranslateError_GetEnd10935759
Ref: 3c1f10935759
Ref: c-api/exceptions c PyUnicodeDecodeError_SetEnd10936028
Ref: 3c2010936028
Ref: c-api/exceptions c PyUnicodeEncodeError_SetEnd10936116
Ref: 3c2110936116
Ref: c-api/exceptions c PyUnicodeTranslateError_SetEnd10936204
Ref: 3c2210936204
Ref: c-api/exceptions c PyUnicodeDecodeError_GetReason10936419
Ref: 3c2310936419
Ref: c-api/exceptions c PyUnicodeEncodeError_GetReason10936490
Ref: 3c2410936490
Ref: c-api/exceptions c PyUnicodeTranslateError_GetReason10936561
Ref: 3c2510936561
Ref: c-api/exceptions c PyUnicodeDecodeError_SetReason10936739
Ref: 3c2610936739
Ref: c-api/exceptions c PyUnicodeEncodeError_SetReason10936834
Ref: 3c2710936834
Ref: c-api/exceptions c PyUnicodeTranslateError_SetReason10936929
Ref: 3c2810936929
Node: Recursion Control10937158
Ref: c-api/exceptions recursion-control10937286
Ref: 3c2910937286
Ref: c-api/exceptions c Py_EnterRecursiveCall10937590
Ref: 3c2a10937590
Ref: c-api/exceptions c Py_LeaveRecursiveCall10938333
Ref: 3c2c10938333
Ref: c-api/exceptions c Py_ReprEnter10938880
Ref: 3c2d10938880
Ref: c-api/exceptions c Py_ReprLeave10939646
Ref: 3c2e10939646
Node: Standard Exceptions10939835
Ref: c-api/exceptions standard-exceptions10939965
Ref: 3c2f10939965
Ref: c-api/exceptions standardexceptions10939965
Ref: 3c3010939965
Ref: Standard Exceptions-Footnote-110953334
Node: Standard Warning Categories10953383
Ref: c-api/exceptions standard-warning-categories10953487
Ref: 3c3110953487
Ref: c-api/exceptions standardwarningcategories10953487
Ref: 3bfc10953487
Node: 工具10956618
Ref: c-api/utilities doc10956733
Ref: 3c3210956733
Ref: c-api/utilities id110956733
Ref: 3c3310956733
Ref: c-api/utilities utilities10956733
Ref: 3c3410956733
Node: 作業系統工具10957254
Ref: c-api/sys doc10957336
Ref: 3c3510957336
Ref: c-api/sys operating-system-utilities10957336
Ref: 3c3610957336
Ref: c-api/sys os10957336
Ref: 3c3710957336
Ref: c-api/sys c PyOS_FSPath10957381
Ref: 5d210957381
Ref: c-api/sys c Py_FdIsInteractive10957923
Ref: 3c3810957923
Ref: c-api/sys c PyOS_BeforeFork10958404
Ref: 43710958404
Ref: c-api/sys c PyOS_AfterFork_Parent10958923
Ref: 43810958923
Ref: c-api/sys c PyOS_AfterFork_Child10959535
Ref: 2ce10959535
Ref: c-api/sys c PyOS_AfterFork10960421
Ref: 43610960421
Ref: c-api/sys c PyOS_CheckStack10960827
Ref: 3c2b10960827
Ref: c-api/sys c PyOS_getsig10961209
Ref: 3c3c10961209
Ref: c-api/sys c PyOS_setsig10961516
Ref: 3c3d10961516
Ref: c-api/sys c Py_DecodeLocale10961873
Ref: 44110961873
Ref: c-api/sys c Py_EncodeLocale10963899
Ref: 44210963899
Node: 系統函式10965676
Ref: c-api/sys system-functions10965792
Ref: 3c4110965792
Ref: c-api/sys systemfunctions10965792
Ref: 3c4210965792
Ref: c-api/sys c PySys_GetObject10966079
Ref: 3c4310966079
Ref: c-api/sys c PySys_SetObject10966313
Ref: 3c4410966313
Ref: c-api/sys c PySys_ResetWarnOptions10966569
Ref: 3c4510966569
Ref: c-api/sys c PySys_AddWarnOption10966744
Ref: 4b810966744
Ref: c-api/sys c PySys_AddWarnOptionUnicode10966973
Ref: 4b710966973
Ref: c-api/sys c PySys_SetPath10967441
Ref: 3c4610967441
Ref: c-api/sys c PySys_WriteStdout10967705
Ref: 3c4710967705
Ref: c-api/sys c PySys_WriteStderr10968567
Ref: 3c4810968567
Ref: c-api/sys c PySys_FormatStdout10968735
Ref: 3c4910968735
Ref: c-api/sys c PySys_FormatStderr10969003
Ref: 3c4b10969003
Ref: c-api/sys c PySys_AddXOption10969197
Ref: 3c4c10969197
Ref: c-api/sys c PySys_GetXOptions10969501
Ref: 3c4d10969501
Ref: c-api/sys c PySys_Audit10969778
Ref: f3b10969778
Ref: c-api/sys c PySys_AddAuditHook10970877
Ref: 34c810970877
Ref: 系統函式-Footnote-110972724
Node: 行程（Process）控制10972773
Ref: c-api/sys process-control10972886
Ref: 3c4f10972886
Ref: c-api/sys processcontrol10972886
Ref: 3c5010972886
Ref: c-api/sys c Py_FatalError10972945
Ref: f8f10972945
Ref: c-api/sys c Py_Exit10973423
Ref: 61710973423
Ref: c-api/sys c Py_AtExit10973766
Ref: 3c5110973766
Node: 匯入模組<2>10974414
Ref: c-api/import doc10974539
Ref: 3c5210974539
Ref: c-api/import importing10974539
Ref: 3c5310974539
Ref: c-api/import importing-modules10974539
Ref: 3c5410974539
Ref: c-api/import c PyImport_ImportModule10974574
Ref: c7810974574
Ref: c-api/import c PyImport_ImportModuleNoBlock10975602
Ref: 9c610975602
Ref: c-api/import c PyImport_ImportModuleEx10976069
Ref: b2610976069
Ref: c-api/import c PyImport_ImportModuleLevelObject10976795
Ref: 3c5510976795
Ref: c-api/import c PyImport_ImportModuleLevel10977551
Ref: b2510977551
Ref: c-api/import c PyImport_Import10977957
Ref: d6410977957
Ref: c-api/import c PyImport_ReloadModule10978472
Ref: 3c5610978472
Ref: c-api/import c PyImport_AddModuleObject10978732
Ref: 3c5710978732
Ref: c-api/import c PyImport_AddModule10979557
Ref: 3b1a10979557
Ref: c-api/import c PyImport_ExecCodeModule10979791
Ref: 3c5810979791
Ref: c-api/import c PyImport_ExecCodeModuleEx10981565
Ref: 3c5910981565
Ref: c-api/import c PyImport_ExecCodeModuleObject10981950
Ref: 3c5b10981950
Ref: c-api/import c PyImport_ExecCodeModuleWithPathnames10982382
Ref: 3c5a10982382
Ref: c-api/import c PyImport_GetMagicNumber10983008
Ref: b2410983008
Ref: c-api/import c PyImport_GetMagicTag10983352
Ref: 3c5c10983352
Ref: c-api/import c PyImport_GetModuleDict10983657
Ref: 3c5d10983657
Ref: c-api/import c PyImport_GetModule10983893
Ref: 42610983893
Ref: c-api/import c PyImport_GetImporter10984238
Ref: 3c5e10984238
Ref: c-api/import c _PyImport_Init10984898
Ref: 3c5f10984898
Ref: c-api/import c PyImport_Cleanup10984999
Ref: 3c6010984999
Ref: c-api/import c _PyImport_Fini10985093
Ref: 3c6110985093
Ref: c-api/import c PyImport_ImportFrozenModuleObject10985192
Ref: 3c6210985192
Ref: c-api/import c PyImport_ImportFrozenModule10985783
Ref: 3c6310985783
Ref: c-api/import c _frozen10985988
Ref: 3c6410985988
Ref: c-api/import c PyImport_FrozenModules10986402
Ref: 22fc10986402
Ref: c-api/import c PyImport_AppendInittab10986804
Ref: 3b0210986804
Ref: c-api/import c _inittab10987345
Ref: 3c6610987345
Ref: c-api/import c PyImport_ExtendInittab10988002
Ref: 3c6510988002
Ref: 匯入模組<2>-Footnote-110988620
Node: Data marshalling support10988669
Ref: c-api/marshal doc10988806
Ref: 3c6710988806
Ref: c-api/marshal data-marshalling-support10988806
Ref: 3c6810988806
Ref: c-api/marshal marshalling-utils10988806
Ref: 3c6910988806
Ref: c-api/marshal c PyMarshal_WriteLongToFile10989553
Ref: 3c6a10989553
Ref: c-api/marshal c PyMarshal_WriteObjectToFile10989869
Ref: 3c6b10989869
Ref: c-api/marshal c PyMarshal_WriteObjectToString10990064
Ref: 3c6c10990064
Ref: c-api/marshal c PyMarshal_ReadLongFromFile10990389
Ref: 3c6d10990389
Ref: c-api/marshal c PyMarshal_ReadShortFromFile10990744
Ref: 3c6e10990744
Ref: c-api/marshal c PyMarshal_ReadObjectFromFile10991101
Ref: 3c6f10991101
Ref: c-api/marshal c PyMarshal_ReadLastObjectFromFile10991443
Ref: 3c7010991443
Ref: c-api/marshal c PyMarshal_ReadObjectFromString10992218
Ref: 3c7110992218
Node: Parsing arguments and building values10992624
Ref: c-api/arg doc10992770
Ref: 3c7210992770
Ref: c-api/arg arg-parsing10992770
Ref: 2d110992770
Ref: c-api/arg parsing-arguments-and-building-values10992770
Ref: 3c7310992770
Node: Parsing arguments<3>10993441
Ref: c-api/arg parsing-arguments10993559
Ref: 3c7410993559
Node: Strings and buffers10994274
Ref: c-api/arg strings-and-buffers10994365
Ref: 3c7510994365
Node: 數字11006515
Ref: c-api/arg numbers11006628
Ref: 3c7711006628
Node: Other objects11008733
Ref: c-api/arg other-objects11008840
Ref: 3c7911008840
Ref: c-api/arg o-ampersand11009592
Ref: 3c7a11009592
Node: API Functions11014109
Ref: c-api/arg api-functions11014201
Ref: 3c7b11014201
Ref: c-api/arg c PyArg_ParseTuple11014246
Ref: 26b11014246
Ref: c-api/arg c PyArg_VaParse11014538
Ref: 3c7c11014538
Ref: c-api/arg c PyArg_ParseTupleAndKeywords11014765
Ref: 5cf11014765
Ref: c-api/arg c PyArg_VaParseTupleAndKeywords11015355
Ref: ddf11015355
Ref: c-api/arg c PyArg_ValidateKeywordArguments11015651
Ref: 3c7d11015651
Ref: c-api/arg c PyArg_Parse11015950
Ref: f6a11015950
Ref: c-api/arg c PyArg_UnpackTuple11016538
Ref: e4b11016538
Node: Building values11018467
Ref: c-api/arg building-values11018585
Ref: 3c7e11018585
Ref: c-api/arg c Py_BuildValue11018634
Ref: 2cf11018634
Ref: c-api/arg c Py_VaBuildValue11026179
Ref: 3c7f11026179
Node: 字串轉換與格式化11026431
Ref: c-api/conversion doc11026563
Ref: 3c8011026563
Ref: c-api/conversion string-conversion11026563
Ref: 3c8111026563
Ref: c-api/conversion string-conversion-and-formatting11026563
Ref: 3c8211026563
Ref: c-api/conversion c PyOS_snprintf11026671
Ref: e4e11026671
Ref: c-api/conversion c PyOS_vsnprintf11026930
Ref: e4f11026930
Ref: c-api/conversion c PyOS_string_to_double11028618
Ref: c2811028618
Ref: c-api/conversion c PyOS_double_to_string11030334
Ref: 3c8311030334
Ref: c-api/conversion c PyOS_stricmp11031918
Ref: 3c8411031918
Ref: c-api/conversion c PyOS_strnicmp11032124
Ref: 3c8511032124
Node: Reflection11032360
Ref: c-api/reflection doc11032491
Ref: 3c8611032491
Ref: c-api/reflection id111032491
Ref: 3c8711032491
Ref: c-api/reflection reflection11032491
Ref: 3c8811032491
Ref: c-api/reflection c PyEval_GetBuiltins11032526
Ref: 3c8911032526
Ref: c-api/reflection c PyEval_GetLocals11032768
Ref: 3c8a11032768
Ref: c-api/reflection c PyEval_GetGlobals11032990
Ref: 3c8b11032990
Ref: c-api/reflection c PyEval_GetFrame11033214
Ref: 3c8c11033214
Ref: c-api/reflection c PyFrame_GetLineNumber11033409
Ref: cf011033409
Ref: c-api/reflection c PyEval_GetFuncName11033539
Ref: 3c8d11033539
Ref: c-api/reflection c PyEval_GetFuncDesc11033717
Ref: 3c8e11033717
Node: Codec registry and support functions11034077
Ref: c-api/codec doc11034175
Ref: 3c8f11034175
Ref: c-api/codec codec-registry11034175
Ref: 5f311034175
Ref: c-api/codec codec-registry-and-support-functions11034175
Ref: 3c9011034175
Ref: c-api/codec c PyCodec_Register11034262
Ref: 3c9111034262
Ref: c-api/codec c PyCodec_KnownEncoding11034537
Ref: 3c9211034537
Ref: c-api/codec c PyCodec_Encode11034745
Ref: 3c9311034745
Ref: c-api/codec c PyCodec_Decode11035224
Ref: 3c9411035224
Node: Codec lookup API11035787
Ref: c-api/codec codec-lookup-api11035933
Ref: 3c9511035933
Ref: c-api/codec c PyCodec_Encoder11036251
Ref: 3c9611036251
Ref: c-api/codec c PyCodec_Decoder11036407
Ref: 3c9711036407
Ref: c-api/codec c PyCodec_IncrementalEncoder11036562
Ref: 3c9811036562
Ref: c-api/codec c PyCodec_IncrementalDecoder11036781
Ref: 3c9911036781
Ref: c-api/codec c PyCodec_StreamReader11037000
Ref: 3c9a11037000
Ref: c-api/codec c PyCodec_StreamWriter11037234
Ref: 3c9b11037234
Node: Registry API for Unicode encoding error handlers11037468
Ref: c-api/codec registry-api-for-unicode-encoding-error-handlers11037614
Ref: 3c9c11037614
Ref: c-api/codec c PyCodec_RegisterError11037729
Ref: 3c9d11037729
Ref: c-api/codec c PyCodec_LookupError11038819
Ref: 3c9e11038819
Ref: c-api/codec c PyCodec_StrictErrors11039122
Ref: 3c9f11039122
Ref: c-api/codec c PyCodec_IgnoreErrors11039247
Ref: 3ca011039247
Ref: c-api/codec c PyCodec_ReplaceErrors11039404
Ref: 3ca111039404
Ref: c-api/codec c PyCodec_XMLCharRefReplaceErrors11039572
Ref: 3ca211039572
Ref: c-api/codec c PyCodec_BackslashReplaceErrors11039751
Ref: 3ca311039751
Ref: c-api/codec c PyCodec_NameReplaceErrors11039956
Ref: 7ad11039956
Node: 抽象物件層11040150
Ref: c-api/abstract doc11040275
Ref: 3ca411040275
Ref: c-api/abstract abstract11040275
Ref: 3b6211040275
Ref: c-api/abstract abstract-objects-layer11040275
Ref: 3ca511040275
Node: Object Protocol11040967
Ref: c-api/object doc11041058
Ref: 3ca611041058
Ref: c-api/object object11041058
Ref: 3ca711041058
Ref: c-api/object object-protocol11041058
Ref: 3ca811041058
Ref: c-api/object c Py_NotImplemented11041103
Ref: 3ca911041103
Ref: c-api/object c Py_RETURN_NOTIMPLEMENTED11041277
Ref: 3caa11041277
Ref: c-api/object c PyObject_Print11041489
Ref: 105111041489
Ref: c-api/object c PyObject_HasAttr11041862
Ref: 3cab11041862
Ref: c-api/object c PyObject_HasAttrString11042359
Ref: 3cad11042359
Ref: c-api/object c PyObject_GetAttr11042919
Ref: 3cac11042919
Ref: c-api/object c PyObject_GetAttrString11043250
Ref: 3b1511043250
Ref: c-api/object c PyObject_GenericGetAttr11043589
Ref: 3cae11043589
Ref: c-api/object c PyObject_SetAttr11044210
Ref: 3caf11044210
Ref: c-api/object c PyObject_SetAttrString11044704
Ref: 3cb111044704
Ref: c-api/object c PyObject_GenericSetAttr11045212
Ref: 3cb311045212
Ref: c-api/object c PyObject_DelAttr11045867
Ref: 3cb011045867
Ref: c-api/object c PyObject_DelAttrString11046107
Ref: 3cb211046107
Ref: c-api/object c PyObject_GenericGetDict11046365
Ref: 3cb411046365
Ref: c-api/object c PyObject_GenericSetDict11046637
Ref: 3cb511046637
Ref: c-api/object c PyObject_RichCompare11046908
Ref: 3b6011046908
Ref: c-api/object c PyObject_RichCompareBool11047535
Ref: f4c11047535
Ref: c-api/object c PyObject_Repr11048307
Ref: 96d11048307
Ref: c-api/object c PyObject_ASCII11048792
Ref: 3cb611048792
Ref: c-api/object c PyObject_Str11049274
Ref: 96e11049274
Ref: c-api/object c PyObject_Bytes11049808
Ref: 3cb711049808
Ref: c-api/object c PyObject_IsSubclass11050237
Ref: 7a311050237
Ref: c-api/object c PyObject_IsInstance11051201
Ref: 7a211051201
Ref: c-api/object c PyCallable_Check11052170
Ref: 3cb811052170
Ref: c-api/object c PyObject_Call11052369
Ref: 3b0a11052369
Ref: c-api/object c PyObject_CallObject11053012
Ref: 3b0911053012
Ref: c-api/object c PyObject_CallFunction11053482
Ref: 2d011053482
Ref: c-api/object c PyObject_CallMethod11054281
Ref: 3cba11054281
Ref: c-api/object c PyObject_CallFunctionObjArgs11055148
Ref: 3cb911055148
Ref: c-api/object c PyObject_CallMethodObjArgs11055680
Ref: fde11055680
Ref: c-api/object c _PyObject_Vectorcall11056223
Ref: 3cbb11056223
Ref: c-api/object c PY_VECTORCALL_ARGUMENTS_OFFSET11057643
Ref: 3cbe11057643
Ref: c-api/object c PyVectorcall_NARGS11058271
Ref: 3cbd11058271
Ref: c-api/object c _PyObject_FastCallDict11058522
Ref: 3cbf11058522
Ref: c-api/object c PyObject_Hash11059437
Ref: 3cc011059437
Ref: c-api/object c PyObject_HashNotImplemented11059767
Ref: d3611059767
Ref: c-api/object c PyObject_IsTrue11060112
Ref: 3cc111060112
Ref: c-api/object c PyObject_Not11060352
Ref: 3cc211060352
Ref: c-api/object c PyObject_Type11060584
Ref: 3cc311060584
Ref: c-api/object c PyObject_TypeCheck11061220
Ref: 3b6a11061220
Ref: c-api/object c PyObject_Size11061416
Ref: 3cc411061416
Ref: c-api/object c PyObject_Length11061469
Ref: 3cc511061469
Ref: c-api/object c PyObject_LengthHint11061779
Ref: 92d11061779
Ref: c-api/object c PyObject_GetItem11062212
Ref: 3bac11062212
Ref: c-api/object c PyObject_SetItem11062475
Ref: 3baa11062475
Ref: c-api/object c PyObject_DelItem11062820
Ref: 3cc611062820
Ref: c-api/object c PyObject_Dir11063052
Ref: 3cc711063052
Ref: c-api/object c PyObject_GetIter11063587
Ref: 3cc811063587
Ref: Object Protocol-Footnote-111063993
Ref: Object Protocol-Footnote-211064042
Node: Number Protocol11064091
Ref: c-api/number doc11064208
Ref: 3cc911064208
Ref: c-api/number number11064208
Ref: 3cca11064208
Ref: c-api/number number-protocol11064208
Ref: 3ccb11064208
Ref: c-api/number c PyNumber_Check11064253
Ref: 26c11064253
Ref: c-api/number c PyNumber_Add11064492
Ref: 3ccc11064492
Ref: c-api/number c PyNumber_Subtract11064740
Ref: 3ccd11064740
Ref: c-api/number c PyNumber_Multiply11064999
Ref: 3cce11064999
Ref: c-api/number c PyNumber_MatrixMultiply11065257
Ref: 7b311065257
Ref: c-api/number c PyNumber_FloorDivide11065568
Ref: 3ccf11065568
Ref: c-api/number c PyNumber_TrueDivide11065817
Ref: 3cd011065817
Ref: c-api/number c PyNumber_Remainder11066292
Ref: 3cd111066292
Ref: c-api/number c PyNumber_Divmod11066550
Ref: 3cd211066550
Ref: c-api/number c PyNumber_Power11066822
Ref: 3cd311066822
Ref: c-api/number c PyNumber_Negative11067283
Ref: 3cd411067283
Ref: c-api/number c PyNumber_Positive11067512
Ref: 3cd511067512
Ref: c-api/number c PyNumber_Absolute11067720
Ref: 3cd611067720
Ref: c-api/number c PyNumber_Invert11067948
Ref: 3cd711067948
Ref: c-api/number c PyNumber_Lshift11068183
Ref: 3cd811068183
Ref: c-api/number c PyNumber_Rshift11068452
Ref: 3cd911068452
Ref: c-api/number c PyNumber_And11068722
Ref: 3cda11068722
Ref: c-api/number c PyNumber_Xor11068981
Ref: 3cdb11068981
Ref: c-api/number c PyNumber_Or11069248
Ref: 3cdc11069248
Ref: c-api/number c PyNumber_InPlaceAdd11069505
Ref: 3cdd11069505
Ref: c-api/number c PyNumber_InPlaceSubtract11069822
Ref: 3cde11069822
Ref: c-api/number c PyNumber_InPlaceMultiply11070160
Ref: 3cdf11070160
Ref: c-api/number c PyNumber_InPlaceMatrixMultiply11070497
Ref: 7b411070497
Ref: c-api/number c PyNumber_InPlaceFloorDivide11070877
Ref: 3ce011070877
Ref: c-api/number c PyNumber_InPlaceTrueDivide11071226
Ref: 3ce111071226
Ref: c-api/number c PyNumber_InPlaceRemainder11071780
Ref: 3ce211071780
Ref: c-api/number c PyNumber_InPlacePower11072117
Ref: 3ce311072117
Ref: c-api/number c PyNumber_InPlaceLshift11072710
Ref: 3ce411072710
Ref: c-api/number c PyNumber_InPlaceRshift11073058
Ref: 3ce511073058
Ref: c-api/number c PyNumber_InPlaceAnd11073407
Ref: 3ce611073407
Ref: c-api/number c PyNumber_InPlaceXor11073735
Ref: 3ce711073735
Ref: c-api/number c PyNumber_InPlaceOr11074071
Ref: 3ce811074071
Ref: c-api/number c PyNumber_Long11074397
Ref: 26d11074397
Ref: c-api/number c PyNumber_Float11074650
Ref: 26e11074650
Ref: c-api/number c PyNumber_Index11074903
Ref: 3ce911074903
Ref: c-api/number c PyNumber_ToBase11075129
Ref: f3d11075129
Ref: c-api/number c PyNumber_AsSsize_t11075588
Ref: 3cea11075588
Ref: c-api/number c PyIndex_Check11076305
Ref: 101611076305
Node: Sequence Protocol11076531
Ref: c-api/sequence doc11076649
Ref: 3ceb11076649
Ref: c-api/sequence sequence11076649
Ref: 3cec11076649
Ref: c-api/sequence sequence-protocol11076649
Ref: 3ced11076649
Ref: c-api/sequence c PySequence_Check11076698
Ref: 3cee11076698
Ref: c-api/sequence c PySequence_Size11077106
Ref: 105211077106
Ref: c-api/sequence c PySequence_Length11077161
Ref: 3cef11077161
Ref: c-api/sequence c PySequence_Concat11077372
Ref: 3cf011077372
Ref: c-api/sequence c PySequence_Repeat11077636
Ref: 3cf111077636
Ref: c-api/sequence c PySequence_InPlaceConcat11077916
Ref: 3cf211077916
Ref: c-api/sequence c PySequence_InPlaceRepeat11078260
Ref: 3cf311078260
Ref: c-api/sequence c PySequence_GetItem11078619
Ref: 105311078619
Ref: c-api/sequence c PySequence_GetSlice11078858
Ref: 3cf411078858
Ref: c-api/sequence c PySequence_SetItem11079158
Ref: 105411079158
Ref: c-api/sequence c PySequence_DelItem11079655
Ref: 105511079655
Ref: c-api/sequence c PySequence_SetSlice11079865
Ref: 3cf511079865
Ref: c-api/sequence c PySequence_DelSlice11080141
Ref: 3cf611080141
Ref: c-api/sequence c PySequence_Count11080407
Ref: 3cf711080407
Ref: c-api/sequence c PySequence_Contains11080719
Ref: 3cf811080719
Ref: c-api/sequence c PySequence_Index11081012
Ref: 3cf911081012
Ref: c-api/sequence c PySequence_List11081255
Ref: 3cfa11081255
Ref: c-api/sequence c PySequence_Tuple11081568
Ref: 3cfb11081568
Ref: c-api/sequence c PySequence_Fast11081974
Ref: 3cfc11081974
Ref: c-api/sequence c PySequence_Fast_GET_SIZE11082656
Ref: 3cfe11082656
Ref: c-api/sequence c PySequence_Fast_GET_ITEM11083050
Ref: 3cff11083050
Ref: c-api/sequence c PySequence_Fast_ITEMS11083342
Ref: 3d0011083342
Ref: c-api/sequence c PySequence_ITEM11083744
Ref: 3d0111083744
Node: Mapping Protocol11084091
Ref: c-api/mapping doc11084211
Ref: 3d0211084211
Ref: c-api/mapping mapping11084211
Ref: 3d0311084211
Ref: c-api/mapping mapping-protocol11084211
Ref: 3d0411084211
Ref: c-api/mapping c PyMapping_Check11084368
Ref: 3d0511084368
Ref: c-api/mapping c PyMapping_Size11084745
Ref: 105611084745
Ref: c-api/mapping c PyMapping_Length11084799
Ref: 3d0611084799
Ref: c-api/mapping c PyMapping_GetItemString11085004
Ref: 3d0711085004
Ref: c-api/mapping c PyMapping_SetItemString11085333
Ref: 3d0811085333
Ref: c-api/mapping c PyMapping_DelItem11085694
Ref: 3d0911085694
Ref: c-api/mapping c PyMapping_DelItemString11085980
Ref: 3d0a11085980
Ref: c-api/mapping c PyMapping_HasKey11086221
Ref: 3d0b11086221
Ref: c-api/mapping c PyMapping_HasKeyString11086662
Ref: 3d0c11086662
Ref: c-api/mapping c PyMapping_Keys11087162
Ref: 43111087162
Ref: c-api/mapping c PyMapping_Values11087417
Ref: 43211087417
Ref: c-api/mapping c PyMapping_Items11087676
Ref: 43311087676
Node: Iterator Protocol11087994
Ref: c-api/iter doc11088112
Ref: 3d0d11088112
Ref: c-api/iter iterator11088112
Ref: 3d0e11088112
Ref: c-api/iter iterator-protocol11088112
Ref: 3d0f11088112
Ref: c-api/iter c PyIter_Check11088227
Ref: 101511088227
Ref: c-api/iter c PyIter_Next11088341
Ref: 3d1011088341
Node: Buffer Protocol11089305
Ref: c-api/buffer doc11089426
Ref: 3d1111089426
Ref: c-api/buffer buffer-protocol11089426
Ref: 3d1211089426
Ref: c-api/buffer bufferobjects11089426
Ref: 15ec11089426
Node: Buffer structure11091944
Ref: c-api/buffer buffer-structure11092041
Ref: 3d1411092041
Ref: c-api/buffer id111092041
Ref: 3d1511092041
Ref: c-api/buffer c Py_buffer11093112
Ref: b2011093112
Ref: c-api/buffer c Py_buffer buf11093137
Ref: 3d1711093137
Ref: c-api/buffer c Py_buffer obj11093604
Ref: 3d1911093604
Ref: c-api/buffer c Py_buffer len11094191
Ref: 3d1c11094191
Ref: c-api/buffer c Py_buffer readonly11094797
Ref: 3d1f11094797
Ref: c-api/buffer c Py_buffer itemsize11094973
Ref: 3d2011094973
Ref: c-api/buffer c Py_buffer format11095896
Ref: 3d2111095896
Ref: c-api/buffer c Py_buffer ndim11096229
Ref: 3d2411096229
Ref: c-api/buffer c Py_buffer shape11096833
Ref: 3d2311096833
Ref: c-api/buffer c Py_buffer strides11097386
Ref: 3d1811097386
Ref: c-api/buffer c Py_buffer suboffsets11097912
Ref: 3d2511097912
Ref: c-api/buffer c Py_buffer internal11098805
Ref: 3d2711098805
Node: Buffer request types11099186
Ref: c-api/buffer buffer-request-types11099306
Ref: 3d2811099306
Ref: c-api/buffer id211099306
Ref: 3d2911099306
Node: request-independent fields11099914
Ref: c-api/buffer request-independent-fields11100021
Ref: 3d2a11100021
Node: readonly format11100289
Ref: c-api/buffer readonly-format11100429
Ref: 3d2b11100429
Ref: c-api/buffer c PyBUF_WRITABLE11100480
Ref: 3d1e11100480
Ref: c-api/buffer c PyBUF_FORMAT11100814
Ref: 3d2211100814
Node: shape strides suboffsets11101396
Ref: c-api/buffer shape-strides-suboffsets11101529
Ref: 3d2c11101529
Ref: c-api/buffer c PyBUF_INDIRECT11102067
Ref: 3d2d11102067
Ref: c-api/buffer c PyBUF_STRIDES11102260
Ref: 3d2e11102260
Ref: c-api/buffer c PyBUF_ND11102444
Ref: 3d2f11102444
Ref: c-api/buffer c PyBUF_SIMPLE11102637
Ref: 3d1d11102637
Node: contiguity requests11102740
Ref: c-api/buffer contiguity-requests11102875
Ref: 3d3011102875
Ref: c-api/buffer c PyBUF_C_CONTIGUOUS11103485
Ref: 3d3111103485
Ref: c-api/buffer c PyBUF_F_CONTIGUOUS11103740
Ref: 3d3211103740
Ref: c-api/buffer c PyBUF_ANY_CONTIGUOUS11103997
Ref: 3d3311103997
Node: compound requests11104393
Ref: c-api/buffer compound-requests11104495
Ref: 3d3411104495
Ref: c-api/buffer c PyBUF_FULL11105371
Ref: 3d3611105371
Ref: c-api/buffer c PyBUF_FULL_RO11105703
Ref: 3d3711105703
Ref: c-api/buffer c PyBUF_RECORDS11106032
Ref: 3d3811106032
Ref: c-api/buffer c PyBUF_RECORDS_RO11106364
Ref: 3d3911106364
Ref: c-api/buffer c PyBUF_STRIDED11106690
Ref: 3d3a11106690
Ref: c-api/buffer c PyBUF_STRIDED_RO11107023
Ref: 3d3b11107023
Ref: c-api/buffer c PyBUF_CONTIG11107349
Ref: 3d3c11107349
Ref: c-api/buffer c PyBUF_CONTIG_RO11107682
Ref: 3d3d11107682
Node: Complex arrays11107876
Ref: c-api/buffer complex-arrays11108004
Ref: 3d2611108004
Node: NumPy-style shape and strides11108210
Ref: c-api/buffer numpy-style-shape-and-strides11108337
Ref: 3d3e11108337
Node: PIL-style shape strides and suboffsets11110217
Ref: c-api/buffer pil-style-shape-strides-and-suboffsets11110344
Ref: 3d3f11110344
Node: Buffer-related functions11111570
Ref: c-api/buffer buffer-related-functions11111669
Ref: 3d4011111669
Ref: c-api/buffer c PyObject_CheckBuffer11111738
Ref: 3d4111111738
Ref: c-api/buffer c PyObject_GetBuffer11112021
Ref: d2a11112021
Ref: c-api/buffer c PyBuffer_Release11112967
Ref: d5911112967
Ref: c-api/buffer c PyBuffer_SizeFromFormat11113346
Ref: 3d4211113346
Ref: c-api/buffer c PyBuffer_IsContiguous11113526
Ref: 3d3511113526
Ref: c-api/buffer c PyBuffer_GetPointer11113863
Ref: 3d4311113863
Ref: c-api/buffer c PyBuffer_FromContiguous11114100
Ref: 3d4411114100
Ref: c-api/buffer c PyBuffer_ToContiguous11114406
Ref: 3d4511114406
Ref: c-api/buffer c PyBuffer_FillContiguousStrides11114814
Ref: 3d4611114814
Ref: c-api/buffer c PyBuffer_FillInfo11115200
Ref: 3d1b11115200
Node: Old Buffer Protocol11116165
Ref: c-api/objbuffer doc11116260
Ref: 3d4711116260
Ref: c-api/objbuffer old-buffer-protocol11116260
Ref: 3d4811116260
Ref: c-api/objbuffer c PyObject_AsCharBuffer11117009
Ref: 3d4911117009
Ref: c-api/objbuffer c PyObject_AsReadBuffer11117481
Ref: 3d4a11117481
Ref: c-api/objbuffer c PyObject_CheckReadBuffer11117940
Ref: 3d4b11117940
Ref: c-api/objbuffer c PyObject_AsWriteBuffer11118383
Ref: 3d4c11118383
Node: Concrete Objects Layer11118813
Ref: c-api/concrete doc11118971
Ref: 3d4d11118971
Ref: c-api/concrete concrete11118971
Ref: 3d4e11118971
Ref: c-api/concrete concrete-objects-layer11118971
Ref: 3d4f11118971
Node: Fundamental Objects11119944
Ref: c-api/concrete fundamental11120046
Ref: 3d5111120046
Ref: c-api/concrete fundamental-objects11120046
Ref: 3d5211120046
Node: Type Objects<2>11120243
Ref: c-api/type doc11120338
Ref: 3d5311120338
Ref: c-api/type type-objects11120338
Ref: 3d5411120338
Ref: c-api/type typeobjects11120338
Ref: 3d5511120338
Ref: c-api/type c PyTypeObject11120381
Ref: 2d711120381
Ref: c-api/type c PyType_Type11120479
Ref: 3d5611120479
Ref: c-api/type c PyType_Check11120632
Ref: 3d5711120632
Ref: c-api/type c PyType_CheckExact11120844
Ref: 3d5811120844
Ref: c-api/type c PyType_ClearCache11121035
Ref: 3d5911121035
Ref: c-api/type c PyType_GetFlags11121156
Ref: 3d5a11121156
Ref: c-api/type c PyType_Modified11121637
Ref: 3d5c11121637
Ref: c-api/type c PyType_HasFeature11121892
Ref: 3d5d11121892
Ref: c-api/type c PyType_IS_GC11122081
Ref: 3d5e11122081
Ref: c-api/type c PyType_IsSubtype11122271
Ref: 3d5f11122271
Ref: c-api/type c PyType_GenericAlloc11122629
Ref: 27111122629
Ref: c-api/type c PyType_GenericNew11122971
Ref: 3b3711122971
Ref: c-api/type c PyType_Ready11123261
Ref: 3b3c11123261
Ref: c-api/type c PyType_GetSlot11123598
Ref: 92911123598
Node: Creating Heap-Allocated Types11124171
Ref: c-api/type creating-heap-allocated-types11124252
Ref: 3d6011124252
Ref: c-api/type c PyType_FromSpecWithBases11124409
Ref: 3d6211124409
Ref: c-api/type c PyType_FromSpec11125064
Ref: 2d211125064
Ref: c-api/type c PyType_Spec11125225
Ref: 3d6411125225
Ref: c-api/type c PyType_Spec PyType_Spec name11125298
Ref: 3d6511125298
Ref: c-api/type c PyType_Spec PyType_Spec basicsize11125438
Ref: 3d6611125438
Ref: c-api/type c PyType_Spec PyType_Spec itemsize11125490
Ref: 3d6711125490
Ref: c-api/type c PyType_Spec PyType_Spec flags11125696
Ref: 3d6811125696
Ref: c-api/type c PyType_Spec PyType_Spec slots11125948
Ref: 3d6911125948
Ref: c-api/type c PyType_Slot11126127
Ref: 3d6a11126127
Ref: c-api/type c PyType_Slot PyType_Slot slot11126260
Ref: 3d6b11126260
Ref: c-api/type c PyType_Slot PyType_Slot pfunc11127627
Ref: 3d7611127627
Node: The None Object11127812
Ref: c-api/none doc11127907
Ref: 3d7711127907
Ref: c-api/none noneobject11127907
Ref: 3d7811127907
Ref: c-api/none the-none-object11127907
Ref: 3d7911127907
Ref: c-api/none c Py_None11128226
Ref: 3afe11128226
Ref: c-api/none c Py_RETURN_NONE11128443
Ref: ddb11128443
Node: Numeric Objects11128631
Ref: c-api/concrete numeric-objects11128758
Ref: 3d7a11128758
Ref: c-api/concrete numericobjects11128758
Ref: 3d7b11128758
Node: 整數物件11128914
Ref: c-api/long doc11128999
Ref: 3d7c11128999
Ref: c-api/long integer-objects11128999
Ref: 3d7d11128999
Ref: c-api/long longobjects11128999
Ref: 3d7e11128999
Ref: c-api/long c PyLongObject11129277
Ref: 3d7f11129277
Ref: c-api/long c PyLong_Type11129389
Ref: 3d8011129389
Ref: c-api/long c PyLong_Check11129588
Ref: 3d8111129588
Ref: c-api/long c PyLong_CheckExact11129746
Ref: 3d8211129746
Ref: c-api/long c PyLong_FromLong11129914
Ref: 3afb11129914
Ref: c-api/long c PyLong_FromUnsignedLong11130449
Ref: 3d8311130449
Ref: c-api/long c PyLong_FromSsize_t11130660
Ref: 3d8411130660
Ref: c-api/long c PyLong_FromSize_t11130860
Ref: 3d8511130860
Ref: c-api/long c PyLong_FromLongLong11131051
Ref: 3d8611131051
Ref: c-api/long c PyLong_FromUnsignedLongLong11131250
Ref: 3d8711131250
Ref: c-api/long c PyLong_FromDouble11131475
Ref: 3d8811131475
Ref: c-api/long c PyLong_FromString11131673
Ref: 3d8911131673
Ref: c-api/long c PyLong_FromUnicode11132535
Ref: 3d8a11132535
Ref: c-api/long c PyLong_FromUnicodeObject11132933
Ref: 3d8b11132933
Ref: c-api/long c PyLong_FromVoidPtr11133155
Ref: 3d8c11133155
Ref: c-api/long c PyLong_AsLong11133401
Ref: 26a11133401
Ref: c-api/long c PyLong_AsLongAndOverflow11134028
Ref: c0211134028
Ref: c-api/long c PyLong_AsLongLong11134887
Ref: 3d8e11134887
Ref: c-api/long c PyLong_AsLongLongAndOverflow11135533
Ref: c0111135533
Ref: c-api/long c PyLong_AsSsize_t11136448
Ref: 3d8f11136448
Ref: c-api/long c PyLong_AsUnsignedLong11136834
Ref: 3d9011136834
Ref: c-api/long c PyLong_AsSize_t11137249
Ref: 3d9111137249
Ref: c-api/long c PyLong_AsUnsignedLongLong11137630
Ref: c2711137630
Ref: c-api/long c PyLong_AsUnsignedLongMask11138188
Ref: 3d9211138188
Ref: c-api/long c PyLong_AsUnsignedLongLongMask11138901
Ref: fbe11138901
Ref: c-api/long c PyLong_AsDouble11139652
Ref: 3d9311139652
Ref: c-api/long c PyLong_AsVoidPtr11140027
Ref: 3d8d11140027
Node: 布林物件11140456
Ref: c-api/bool doc11140585
Ref: 3d9411140585
Ref: c-api/bool boolean-objects11140585
Ref: 3d9511140585
Ref: c-api/bool boolobjects11140585
Ref: 3d9611140585
Ref: c-api/bool c PyBool_Check11140877
Ref: 3d9711140877
Ref: c-api/bool c Py_False11140978
Ref: 3d9811140978
Ref: c-api/bool c Py_True11141173
Ref: 3d9911141173
Ref: c-api/bool c Py_RETURN_FALSE11141366
Ref: ddd11141366
Ref: c-api/bool c Py_RETURN_TRUE11141490
Ref: ddc11141490
Ref: c-api/bool c PyBool_FromLong11141612
Ref: 3d9a11141612
Node: 浮點數（Floating Point）物件11141799
Ref: c-api/float doc11141938
Ref: 3d9b11141938
Ref: c-api/float floating-point-objects11141938
Ref: 3d9c11141938
Ref: c-api/float floatobjects11141938
Ref: 3d9d11141938
Ref: c-api/float c PyFloatObject11142020
Ref: 3d9e11142020
Ref: c-api/float c PyFloat_Type11142140
Ref: 3d9f11142140
Ref: c-api/float c PyFloat_Check11142349
Ref: 3da011142349
Ref: c-api/float c PyFloat_CheckExact11142510
Ref: 3da111142510
Ref: c-api/float c PyFloat_FromString11142681
Ref: 3da211142681
Ref: c-api/float c PyFloat_FromDouble11142888
Ref: 3da311142888
Ref: c-api/float c PyFloat_AsDouble11143064
Ref: 26f11143064
Ref: c-api/float c PyFloat_AS_DOUBLE11143651
Ref: 3da411143651
Ref: c-api/float c PyFloat_GetInfo11143819
Ref: d5c11143819
Ref: c-api/float c PyFloat_GetMax11144095
Ref: d5a11144095
Ref: c-api/float c PyFloat_GetMin11144221
Ref: d5b11144221
Ref: c-api/float c PyFloat_ClearFreeList11144346
Ref: 3da511144346
Node: Complex Number Objects11144481
Ref: c-api/complex doc11144599
Ref: 3da611144599
Ref: c-api/complex complex-number-objects11144599
Ref: 3da711144599
Ref: c-api/complex complexobjects11144599
Ref: 3da811144599
Node: Complex Numbers as C Structures11145032
Ref: c-api/complex complex-numbers-as-c-structures11145164
Ref: 3da911145164
Ref: c-api/complex c Py_complex11145447
Ref: 3c7811145447
Ref: c-api/complex c _Py_c_sum11145841
Ref: 3daa11145841
Ref: c-api/complex c _Py_c_diff11146015
Ref: 3dab11146015
Ref: c-api/complex c _Py_c_neg11146202
Ref: 3dac11146202
Ref: c-api/complex c _Py_c_prod11146375
Ref: 3dad11146375
Ref: c-api/complex c _Py_c_quot11146554
Ref: 3dae11146554
Ref: c-api/complex c _Py_c_pow11146844
Ref: 3daf11146844
Node: Complex Numbers as Python Objects11147151
Ref: c-api/complex complex-numbers-as-python-objects11147283
Ref: 3db011147283
Ref: c-api/complex c PyComplexObject11147368
Ref: 3db111147368
Ref: c-api/complex c PyComplex_Type11147490
Ref: 3db211147490
Ref: c-api/complex c PyComplex_Check11147701
Ref: 3db311147701
Ref: c-api/complex c PyComplex_CheckExact11147868
Ref: 3db411147868
Ref: c-api/complex c PyComplex_FromCComplex11148045
Ref: 3db511148045
Ref: c-api/complex c PyComplex_FromDoubles11148232
Ref: 3db611148232
Ref: c-api/complex c PyComplex_RealAsDouble11148421
Ref: 3db711148421
Ref: c-api/complex c PyComplex_ImagAsDouble11148537
Ref: 3db811148537
Ref: c-api/complex c PyComplex_AsCComplex11148658
Ref: d5d11148658
Node: Sequence Objects11149304
Ref: c-api/concrete sequence-objects11149429
Ref: 3db911149429
Ref: c-api/concrete sequenceobjects11149429
Ref: 3dba11149429
Node: Bytes Objects<2>11149840
Ref: c-api/bytes doc11149936
Ref: 3dbb11149936
Ref: c-api/bytes bytes-objects11149936
Ref: 3dbc11149936
Ref: c-api/bytes bytesobjects11149936
Ref: 3dbd11149936
Ref: c-api/bytes c PyBytesObject11150102
Ref: d2311150102
Ref: c-api/bytes c PyBytes_Type11150213
Ref: 3dbe11150213
Ref: c-api/bytes c PyBytes_Check11150410
Ref: d2411150410
Ref: c-api/bytes c PyBytes_CheckExact11150563
Ref: 3dbf11150563
Ref: c-api/bytes c PyBytes_FromString11150727
Ref: 3dc011150727
Ref: c-api/bytes c PyBytes_FromStringAndSize11151004
Ref: d2511151004
Ref: c-api/bytes c PyBytes_FromFormat11151345
Ref: 101011151345
Ref: c-api/bytes c PyBytes_FromFormatV11155189
Ref: 3dc111155189
Ref: c-api/bytes c PyBytes_FromObject11155418
Ref: 3dc211155418
Ref: c-api/bytes c PyBytes_Size11155601
Ref: 3dc311155601
Ref: c-api/bytes c PyBytes_GET_SIZE11155712
Ref: 3dc411155712
Ref: c-api/bytes c PyBytes_AsString11155850
Ref: 3dc511155850
Ref: c-api/bytes c PyBytes_AS_STRING11156461
Ref: 3dc611156461
Ref: c-api/bytes c PyBytes_AsStringAndSize11156604
Ref: 3dc711156604
Ref: c-api/bytes c PyBytes_Concat11157590
Ref: 3dc811157590
Ref: c-api/bytes c PyBytes_ConcatAndDel11158071
Ref: 3dc911158071
Ref: c-api/bytes c _PyBytes_Resize11158331
Ref: 104f11158331
Ref: Bytes Objects<2>-Footnote-111159199
Ref: Bytes Objects<2>-Footnote-211159329
Ref: Bytes Objects<2>-Footnote-311159459
Ref: Bytes Objects<2>-Footnote-411159589
Ref: Bytes Objects<2>-Footnote-511159719
Ref: Bytes Objects<2>-Footnote-611159849
Ref: Bytes Objects<2>-Footnote-711159979
Ref: Bytes Objects<2>-Footnote-811160109
Node: Byte Array Objects11160239
Ref: c-api/bytearray doc11160366
Ref: 3dca11160366
Ref: c-api/bytearray byte-array-objects11160366
Ref: 3dcb11160366
Ref: c-api/bytearray bytearrayobjects11160366
Ref: 3dcc11160366
Ref: c-api/bytearray c PyByteArrayObject11160421
Ref: 3dcd11160421
Ref: c-api/bytearray c PyByteArray_Type11160540
Ref: 3dce11160540
Node: Type check macros11160817
Ref: c-api/bytearray type-check-macros11160918
Ref: 3dcf11160918
Ref: c-api/bytearray c PyByteArray_Check11160971
Ref: 3dd011160971
Ref: c-api/bytearray c PyByteArray_CheckExact11161136
Ref: 3dd111161136
Node: Direct API functions11161312
Ref: c-api/bytearray direct-api-functions11161428
Ref: 3dd211161428
Ref: c-api/bytearray c PyByteArray_FromObject11161487
Ref: d2611161487
Ref: c-api/bytearray c PyByteArray_FromStringAndSize11161692
Ref: d2711161692
Ref: c-api/bytearray c PyByteArray_Concat11161940
Ref: 3dd311161940
Ref: c-api/bytearray c PyByteArray_Size11162127
Ref: 3dd411162127
Ref: c-api/bytearray c PyByteArray_AsString11162270
Ref: 3dd511162270
Ref: c-api/bytearray c PyByteArray_Resize11162502
Ref: 3dd611162502
Node: Macros11162636
Ref: c-api/bytearray macros11162726
Ref: 3dd711162726
Ref: c-api/bytearray c PyByteArray_AS_STRING11162827
Ref: 3dd811162827
Ref: c-api/bytearray c PyByteArray_GET_SIZE11162951
Ref: 3dd911162951
Node: Unicode物件與編碼11163075
Ref: c-api/unicode doc11163209
Ref: b2111163209
Ref: c-api/unicode unicode-objects-and-codecs11163209
Ref: 3dda11163209
Ref: c-api/unicode unicodeobjects11163209
Ref: 3ddb11163209
Node: Unicode Objects11163348
Ref: c-api/unicode unicode-objects11163446
Ref: 3ddc11163446
Ref: Unicode Objects-Footnote-111165113
Ref: Unicode Objects-Footnote-211165162
Node: Unicode Type11165211
Ref: c-api/unicode unicode-type11165312
Ref: 3ddd11165312
Ref: c-api/unicode c Py_UCS411165444
Ref: ad811165444
Ref: c-api/unicode c Py_UCS211165466
Ref: ad711165466
Ref: c-api/unicode c Py_UCS111165488
Ref: ad611165488
Ref: c-api/unicode c Py_UNICODE11165757
Ref: af311165757
Ref: c-api/unicode c PyASCIIObject11166084
Ref: ad911166084
Ref: c-api/unicode c PyCompactUnicodeObject11166112
Ref: ada11166112
Ref: c-api/unicode c PyUnicodeObject11166149
Ref: 3dde11166149
Ref: c-api/unicode c PyUnicode_Type11166458
Ref: 3ddf11166458
Ref: c-api/unicode c PyUnicode_Check11166766
Ref: 3de011166766
Ref: c-api/unicode c PyUnicode_CheckExact11166913
Ref: 3de111166913
Ref: c-api/unicode c PyUnicode_READY11167063
Ref: adb11167063
Ref: c-api/unicode c PyUnicode_GET_LENGTH11167573
Ref: ad111167573
Ref: c-api/unicode c PyUnicode_1BYTE_DATA11167812
Ref: ae011167812
Ref: c-api/unicode c PyUnicode_2BYTE_DATA11167870
Ref: ae111167870
Ref: c-api/unicode c PyUnicode_4BYTE_DATA11167928
Ref: ae211167928
Ref: c-api/unicode c PyUnicode_WCHAR_KIND11168389
Ref: ae411168389
Ref: c-api/unicode c PyUnicode_1BYTE_KIND11168424
Ref: ae511168424
Ref: c-api/unicode c PyUnicode_2BYTE_KIND11168459
Ref: ae611168459
Ref: c-api/unicode c PyUnicode_4BYTE_KIND11168494
Ref: ae711168494
Ref: c-api/unicode c PyUnicode_KIND11168734
Ref: ae311168734
Ref: c-api/unicode c PyUnicode_DATA11169050
Ref: adf11169050
Ref: c-api/unicode c PyUnicode_WRITE11169265
Ref: aea11169265
Ref: c-api/unicode c PyUnicode_READ11169828
Ref: ae811169828
Ref: c-api/unicode c PyUnicode_READ_CHAR11170104
Ref: ae911170104
Ref: c-api/unicode c PyUnicode_MAX_CHAR_VALUE11170408
Ref: aeb11170408
Ref: c-api/unicode c PyUnicode_ClearFreeList11170719
Ref: 3de211170719
Ref: c-api/unicode c PyUnicode_GET_SIZE11170833
Ref: afa11170833
Ref: c-api/unicode c PyUnicode_GET_DATA_SIZE11171259
Ref: afc11171259
Ref: c-api/unicode c PyUnicode_AS_UNICODE11171641
Ref: af611171641
Ref: c-api/unicode c PyUnicode_AS_DATA11171702
Ref: af911171702
Node: Unicode Character Properties11172761
Ref: c-api/unicode unicode-character-properties11172909
Ref: 3de311172909
Ref: c-api/unicode c Py_UNICODE_ISSPACE11173173
Ref: ec911173173
Ref: c-api/unicode c Py_UNICODE_ISLOWER11173317
Ref: 3de411173317
Ref: c-api/unicode c Py_UNICODE_ISUPPER11173460
Ref: 3de511173460
Ref: c-api/unicode c Py_UNICODE_ISTITLE11173604
Ref: 3de611173604
Ref: c-api/unicode c Py_UNICODE_ISLINEBREAK11173747
Ref: 3de711173747
Ref: c-api/unicode c Py_UNICODE_ISDECIMAL11173894
Ref: 3de811173894
Ref: c-api/unicode c Py_UNICODE_ISDIGIT11174032
Ref: 3de911174032
Ref: c-api/unicode c Py_UNICODE_ISNUMERIC11174166
Ref: 3dea11174166
Ref: c-api/unicode c Py_UNICODE_ISALPHA11174304
Ref: 3deb11174304
Ref: c-api/unicode c Py_UNICODE_ISALNUM11174449
Ref: 3dec11174449
Ref: c-api/unicode c Py_UNICODE_ISPRINTABLE11174596
Ref: 3ded11174596
Ref: c-api/unicode c Py_UNICODE_TOLOWER11175257
Ref: 3dee11175257
Ref: c-api/unicode c Py_UNICODE_TOUPPER11175443
Ref: 3def11175443
Ref: c-api/unicode c Py_UNICODE_TOTITLE11175629
Ref: 3df011175629
Ref: c-api/unicode c Py_UNICODE_TODECIMAL11175815
Ref: 3df111175815
Ref: c-api/unicode c Py_UNICODE_TODIGIT11176034
Ref: 3df211176034
Ref: c-api/unicode c Py_UNICODE_TONUMERIC11176247
Ref: 3df311176247
Ref: c-api/unicode c Py_UNICODE_IS_SURROGATE11176498
Ref: 3df411176498
Ref: c-api/unicode c Py_UNICODE_IS_HIGH_SURROGATE11176609
Ref: 3df511176609
Ref: c-api/unicode c Py_UNICODE_IS_LOW_SURROGATE11176730
Ref: 3df611176730
Ref: c-api/unicode c Py_UNICODE_JOIN_SURROGATES11176849
Ref: 3df711176849
Node: Creating and accessing Unicode strings11177075
Ref: c-api/unicode creating-and-accessing-unicode-strings11177237
Ref: 3df811177237
Ref: c-api/unicode c PyUnicode_New11177421
Ref: ad211177421
Ref: c-api/unicode c PyUnicode_FromKindAndData11177910
Ref: adc11177910
Ref: c-api/unicode c PyUnicode_FromStringAndSize11178365
Ref: 3df911178365
Ref: c-api/unicode c PyUnicode_FromString11179032
Ref: 3b8a11179032
Ref: c-api/unicode c PyUnicode_FromFormat11179214
Ref: 7d011179214
Ref: c-api/unicode c PyUnicode_FromFormatV11186436
Ref: 3c4a11186436
Ref: c-api/unicode c PyUnicode_FromEncodedObject11186668
Ref: 3dfa11186668
Ref: c-api/unicode c PyUnicode_GetLength11187428
Ref: ad011187428
Ref: c-api/unicode c PyUnicode_CopyCharacters11187581
Ref: acf11187581
Ref: c-api/unicode c PyUnicode_Fill11188054
Ref: b0011188054
Ref: c-api/unicode c PyUnicode_WriteChar11188529
Ref: ad511188529
Ref: c-api/unicode c PyUnicode_ReadChar11189088
Ref: ad411189088
Ref: c-api/unicode c PyUnicode_Substring11189410
Ref: ad311189410
Ref: c-api/unicode c PyUnicode_AsUCS411189729
Ref: add11189729
Ref: c-api/unicode c PyUnicode_AsUCS4Copy11190156
Ref: ade11190156
Ref: Creating and accessing Unicode strings-Footnote-111190532
Ref: Creating and accessing Unicode strings-Footnote-211190685
Ref: Creating and accessing Unicode strings-Footnote-311190838
Ref: Creating and accessing Unicode strings-Footnote-411190991
Ref: Creating and accessing Unicode strings-Footnote-511191144
Ref: Creating and accessing Unicode strings-Footnote-611191297
Ref: Creating and accessing Unicode strings-Footnote-711191450
Ref: Creating and accessing Unicode strings-Footnote-811191603
Ref: Creating and accessing Unicode strings-Footnote-911191756
Ref: Creating and accessing Unicode strings-Footnote-1011191909
Ref: Creating and accessing Unicode strings-Footnote-1111192063
Ref: Creating and accessing Unicode strings-Footnote-1211192217
Ref: Creating and accessing Unicode strings-Footnote-1311192371
Node: Deprecated Py_UNICODE APIs11192525
Ref: c-api/unicode deprecated-py-unicode-apis11192674
Ref: 3dfc11192674
Ref: c-api/unicode c PyUnicode_FromUnicode11193052
Ref: af411193052
Ref: c-api/unicode c PyUnicode_AsUnicode11194096
Ref: af711194096
Ref: c-api/unicode c PyUnicode_TransformDecimalToASCII11194991
Ref: b1411194991
Ref: c-api/unicode c PyUnicode_AsUnicodeAndSize11195542
Ref: af811195542
Ref: c-api/unicode c PyUnicode_AsUnicodeCopy11196274
Ref: afd11196274
Ref: c-api/unicode c PyUnicode_GetSize11196917
Ref: afb11196917
Ref: c-api/unicode c PyUnicode_FromObject11197301
Ref: 3dfd11197301
Ref: Deprecated Py_UNICODE APIs-Footnote-111197729
Node: Locale Encoding11197778
Ref: c-api/unicode locale-encoding11197909
Ref: 3dfe11197909
Ref: c-api/unicode c PyUnicode_DecodeLocaleAndSize11198043
Ref: 44311198043
Ref: c-api/unicode c PyUnicode_DecodeLocale11199207
Ref: 3dff11199207
Ref: c-api/unicode c PyUnicode_EncodeLocale11199481
Ref: 44411199481
Ref: Locale Encoding-Footnote-111200660
Ref: Locale Encoding-Footnote-211200709
Node: File System Encoding11200758
Ref: c-api/unicode file-system-encoding11200878
Ref: 3e0011200878
Ref: c-api/unicode c PyUnicode_FSConverter11201360
Ref: 5d311201360
Ref: c-api/unicode c PyUnicode_FSDecoder11202061
Ref: 5d411202061
Ref: c-api/unicode c PyUnicode_DecodeFSDefaultAndSize11202609
Ref: 3c4011202609
Ref: c-api/unicode c PyUnicode_DecodeFSDefault11203379
Ref: 3e0111203379
Ref: c-api/unicode c PyUnicode_EncodeFSDefault11203896
Ref: 105011203896
Ref: File System Encoding-Footnote-111204806
Ref: File System Encoding-Footnote-211204855
Node: wchar_t Support11204904
Ref: c-api/unicode wchar-t-support11205000
Ref: 3e0211205000
Ref: c-api/unicode c PyUnicode_FromWideChar11205106
Ref: af511205106
Ref: c-api/unicode c PyUnicode_AsWideChar11205468
Ref: 105711205468
Ref: c-api/unicode c PyUnicode_AsWideCharString11206273
Ref: 43d11206273
Node: Built-in Codecs11207334
Ref: c-api/unicode built-in-codecs11207467
Ref: 3e0311207467
Ref: c-api/unicode builtincodecs11207467
Ref: 3dfb11207467
Node: Generic Codecs11208891
Ref: c-api/unicode generic-codecs11208978
Ref: 3e0411208978
Ref: c-api/unicode c PyUnicode_Decode11209062
Ref: f7811209062
Ref: c-api/unicode c PyUnicode_AsEncodedString11209581
Ref: 3e0511209581
Ref: c-api/unicode c PyUnicode_Encode11210090
Ref: b0111210090
Node: UTF-8 Codecs11210830
Ref: c-api/unicode utf-8-codecs11210939
Ref: 3e0611210939
Ref: c-api/unicode c PyUnicode_DecodeUTF811211017
Ref: 3e0711211017
Ref: c-api/unicode c PyUnicode_DecodeUTF8Stateful11211315
Ref: 3e0811211315
Ref: c-api/unicode c PyUnicode_AsUTF8String11211811
Ref: b0411211811
Ref: c-api/unicode c PyUnicode_AsUTF8AndSize11212097
Ref: 42f11212097
Ref: c-api/unicode c PyUnicode_AsUTF811213017
Ref: 43011213017
Ref: c-api/unicode c PyUnicode_EncodeUTF811213278
Ref: b0311213278
Node: UTF-32 Codecs11213898
Ref: c-api/unicode utf-32-codecs11214006
Ref: 3e0911214006
Ref: c-api/unicode c PyUnicode_DecodeUTF3211214087
Ref: 3e0a11214087
Ref: c-api/unicode c PyUnicode_DecodeUTF32Stateful11215231
Ref: 3e0b11215231
Ref: c-api/unicode c PyUnicode_AsUTF32String11215851
Ref: 3e0c11215851
Ref: c-api/unicode c PyUnicode_EncodeUTF3211216180
Ref: b0511216180
Node: UTF-16 Codecs11217226
Ref: c-api/unicode utf-16-codecs11217334
Ref: 3e0d11217334
Ref: c-api/unicode c PyUnicode_DecodeUTF1611217415
Ref: 3e0e11217415
Ref: c-api/unicode c PyUnicode_DecodeUTF16Stateful11218639
Ref: 3e0f11218639
Ref: c-api/unicode c PyUnicode_AsUTF16String11219268
Ref: 3e1011219268
Ref: c-api/unicode c PyUnicode_EncodeUTF1611219597
Ref: b0611219597
Node: UTF-7 Codecs11220768
Ref: c-api/unicode utf-7-codecs11220884
Ref: 3e1111220884
Ref: c-api/unicode c PyUnicode_DecodeUTF711220962
Ref: 3e1211220962
Ref: c-api/unicode c PyUnicode_DecodeUTF7Stateful11221260
Ref: 3e1311221260
Ref: c-api/unicode c PyUnicode_EncodeUTF711221758
Ref: b0211221758
Node: Unicode-Escape Codecs11222590
Ref: c-api/unicode unicode-escape-codecs11222718
Ref: 3e1411222718
Ref: c-api/unicode c PyUnicode_DecodeUnicodeEscape11222825
Ref: 3e1511222825
Ref: c-api/unicode c PyUnicode_AsUnicodeEscapeString11223141
Ref: b0811223141
Ref: c-api/unicode c PyUnicode_EncodeUnicodeEscape11223455
Ref: b0711223455
Node: Raw-Unicode-Escape Codecs11223974
Ref: c-api/unicode raw-unicode-escape-codecs11224104
Ref: 3e1611224104
Ref: c-api/unicode c PyUnicode_DecodeRawUnicodeEscape11224223
Ref: 3e1711224223
Ref: c-api/unicode c PyUnicode_AsRawUnicodeEscapeString11224546
Ref: b0a11224546
Ref: c-api/unicode c PyUnicode_EncodeRawUnicodeEscape11224867
Ref: b0911224867
Node: Latin-1 Codecs11225450
Ref: c-api/unicode latin-1-codecs11225571
Ref: 3e1811225571
Ref: c-api/unicode c PyUnicode_DecodeLatin111225768
Ref: 3e1911225768
Ref: c-api/unicode c PyUnicode_AsLatin1String11226070
Ref: b0c11226070
Ref: c-api/unicode c PyUnicode_EncodeLatin111226365
Ref: b0b11226365
Node: ASCII Codecs11226939
Ref: c-api/unicode ascii-codecs11227055
Ref: 3e1a11227055
Ref: c-api/unicode c PyUnicode_DecodeASCII11227203
Ref: 3e1b11227203
Ref: c-api/unicode c PyUnicode_AsASCIIString11227502
Ref: b0e11227502
Ref: c-api/unicode c PyUnicode_EncodeASCII11227789
Ref: b0d11227789
Node: Character Map Codecs11228359
Ref: c-api/unicode character-map-codecs11228484
Ref: 3e1c11228484
Ref: c-api/unicode c PyUnicode_DecodeCharmap11228963
Ref: 3e1d11228963
Ref: c-api/unicode c PyUnicode_AsCharmapString11229785
Ref: 3e1e11229785
Ref: c-api/unicode c PyUnicode_EncodeCharmap11230435
Ref: b0f11230435
Ref: c-api/unicode c PyUnicode_Translate11231131
Ref: 3e1f11231131
Ref: c-api/unicode c PyUnicode_TranslateCharmap11231968
Ref: b1011231968
Node: MBCS codecs for Windows11232604
Ref: c-api/unicode mbcs-codecs-for-windows11232732
Ref: 3e2011232732
Ref: c-api/unicode c PyUnicode_DecodeMBCS11233092
Ref: 3e2111233092
Ref: c-api/unicode c PyUnicode_DecodeMBCSStateful11233389
Ref: 3e2211233389
Ref: c-api/unicode c PyUnicode_AsMBCSString11233852
Ref: b1211233852
Ref: c-api/unicode c PyUnicode_EncodeCodePage11234137
Ref: b1311234137
Ref: c-api/unicode c PyUnicode_EncodeMBCS11234531
Ref: b1111234531
Node: Methods & Slots11235141
Ref: c-api/unicode methods-slots11235240
Ref: 3e2311235240
Node: Methods and Slot Functions11235291
Ref: c-api/unicode methods-and-slot-functions11235400
Ref: 3e2411235400
Ref: c-api/unicode unicodemethodsandslots11235400
Ref: 3e2511235400
Ref: c-api/unicode c PyUnicode_Concat11235723
Ref: b2211235723
Ref: c-api/unicode c PyUnicode_Split11235889
Ref: 3e2611235889
Ref: c-api/unicode c PyUnicode_Splitlines11236352
Ref: 3e2711236352
Ref: c-api/unicode c PyUnicode_Join11236690
Ref: b2311236690
Ref: c-api/unicode c PyUnicode_Tailmatch11236915
Ref: aff11236915
Ref: c-api/unicode c PyUnicode_Find11237314
Ref: 3e2811237314
Ref: c-api/unicode c PyUnicode_FindChar11237850
Ref: 44511237850
Ref: c-api/unicode c PyUnicode_Count11238516
Ref: 3e2911238516
Ref: c-api/unicode c PyUnicode_Replace11238772
Ref: 3e2a11238772
Ref: c-api/unicode c PyUnicode_Compare11239122
Ref: afe11239122
Ref: c-api/unicode c PyUnicode_CompareWithASCIIString11239442
Ref: c0311239442
Ref: c-api/unicode c PyUnicode_RichCompare11239896
Ref: 3e2b11239896
Ref: c-api/unicode c PyUnicode_Format11240424
Ref: 3e2c11240424
Ref: c-api/unicode c PyUnicode_Contains11240648
Ref: 3e2d11240648
Ref: c-api/unicode c PyUnicode_InternInPlace11240951
Ref: 3e2e11240951
Ref: c-api/unicode c PyUnicode_InternFromString11241724
Ref: 3e2f11241724
Node: 元組（Tuple）物件11242101
Ref: c-api/tuple doc11242240
Ref: 3e3011242240
Ref: c-api/tuple tuple-objects11242240
Ref: 3e3111242240
Ref: c-api/tuple tupleobjects11242240
Ref: 3e3211242240
Ref: c-api/tuple c PyTupleObject11242301
Ref: 3c4e11242301
Ref: c-api/tuple c PyTuple_Type11242412
Ref: 3e3311242412
Ref: c-api/tuple c PyTuple_Check11242609
Ref: 3e3411242609
Ref: c-api/tuple c PyTuple_CheckExact11242751
Ref: 3e3511242751
Ref: c-api/tuple c PyTuple_New11242904
Ref: 3e3611242904
Ref: c-api/tuple c PyTuple_Pack11243067
Ref: 3e3711243067
Ref: c-api/tuple c PyTuple_Size11243423
Ref: 3e3811243423
Ref: c-api/tuple c PyTuple_GET_SIZE11243556
Ref: 3e3911243556
Ref: c-api/tuple c PyTuple_GetItem11243741
Ref: 3b1611243741
Ref: c-api/tuple c PyTuple_GET_ITEM11244023
Ref: 3e3a11244023
Ref: c-api/tuple c PyTuple_GetSlice11244217
Ref: 3e3b11244217
Ref: c-api/tuple c PyTuple_SetItem11244587
Ref: 3b1b11244587
Ref: c-api/tuple c PyTuple_SET_ITEM11245055
Ref: 3e3c11245055
Ref: c-api/tuple c _PyTuple_Resize11245535
Ref: e5011245535
Ref: c-api/tuple c PyTuple_ClearFreeList11246448
Ref: 3e3d11246448
Node: Struct Sequence Objects11246560
Ref: c-api/tuple struct-sequence-objects11246699
Ref: 3e3e11246699
Ref: c-api/tuple c PyStructSequence_NewType11247007
Ref: 3e3f11247007
Ref: c-api/tuple c PyStructSequence_InitType11247318
Ref: 92c11247318
Ref: c-api/tuple c PyStructSequence_InitType211247494
Ref: 92b11247494
Ref: c-api/tuple c PyStructSequence_Desc11247736
Ref: 42e11247736
Ref: c-api/tuple c PyStructSequence_Field11249316
Ref: 42d11249316
Ref: c-api/tuple c PyStructSequence_UnnamedField11250419
Ref: 3e4111250419
Ref: c-api/tuple c PyStructSequence_New11250528
Ref: 3e4011250528
Ref: c-api/tuple c PyStructSequence_GetItem11250747
Ref: 3e4211250747
Ref: c-api/tuple c PyStructSequence_GET_ITEM11251001
Ref: 3e4311251001
Ref: c-api/tuple c PyStructSequence_SetItem11251199
Ref: 3e4411251199
Ref: c-api/tuple c PyStructSequence_SET_ITEM11251541
Ref: 3e4511251541
Node: List（串列）物件11251769
Ref: c-api/list doc11251876
Ref: 3e4611251876
Ref: c-api/list list-objects11251876
Ref: 3e4711251876
Ref: c-api/list listobjects11251876
Ref: 3e4811251876
Ref: c-api/list c PyListObject11251935
Ref: 3cfd11251935
Ref: c-api/list c PyList_Type11252044
Ref: 3b4b11252044
Ref: c-api/list c PyList_Check11252241
Ref: 3e4911252241
Ref: c-api/list c PyList_CheckExact11252380
Ref: 3e4a11252380
Ref: c-api/list c PyList_New11252530
Ref: 3bab11252530
Ref: c-api/list c PyList_Size11253044
Ref: d8311253044
Ref: c-api/list c PyList_GET_SIZE11253214
Ref: 3e4b11253214
Ref: c-api/list c PyList_GetItem11253343
Ref: 3b1711253343
Ref: c-api/list c PyList_GET_ITEM11253752
Ref: 3e4c11253752
Ref: c-api/list c PyList_SetItem11253939
Ref: 3b1c11253939
Ref: c-api/list c PyList_SET_ITEM11254384
Ref: 3e4d11254384
Ref: c-api/list c PyList_Insert11254899
Ref: 3e4e11254899
Ref: c-api/list c PyList_Append11255206
Ref: 3e4f11255206
Ref: c-api/list c PyList_GetSlice11255463
Ref: 3e5011255463
Ref: c-api/list c PyList_SetSlice11255857
Ref: 3e5111255857
Ref: c-api/list c PyList_Sort11256322
Ref: 3e5211256322
Ref: c-api/list c PyList_Reverse11256507
Ref: 3e5311256507
Ref: c-api/list c PyList_AsTuple11256705
Ref: 3e5411256705
Ref: c-api/list c PyList_ClearFreeList11256903
Ref: 3e5511256903
Node: Container Objects11257038
Ref: c-api/concrete container-objects11257163
Ref: 3e5611257163
Ref: c-api/concrete mapobjects11257163
Ref: 3e5711257163
Node: 字典物件11257255
Ref: c-api/dict doc11257341
Ref: 3e5811257341
Ref: c-api/dict dictionary-objects11257341
Ref: 3e5911257341
Ref: c-api/dict dictobjects11257341
Ref: 3e5a11257341
Ref: c-api/dict c PyDictObject11257380
Ref: 3e5b11257380
Ref: c-api/dict c PyDict_Type11257480
Ref: 3e5c11257480
Ref: c-api/dict c PyDict_Check11257660
Ref: 3d5011257660
Ref: c-api/dict c PyDict_CheckExact11257789
Ref: 3e5d11257789
Ref: c-api/dict c PyDict_New11257938
Ref: 3e5e11257938
Ref: c-api/dict c PyDictProxy_New11258076
Ref: 3e5f11258076
Ref: c-api/dict c PyDict_Clear11258400
Ref: 3e6011258400
Ref: c-api/dict c PyDict_Contains11258506
Ref: 3e6111258506
Ref: c-api/dict c PyDict_Copy11258798
Ref: 3e6211258798
Ref: c-api/dict c PyDict_SetItem11258962
Ref: 3b1d11258962
Ref: c-api/dict c PyDict_SetItemString11259325
Ref: 3e6311259325
Ref: c-api/dict c PyDict_DelItem11259710
Ref: 3e6411259710
Ref: c-api/dict c PyDict_DelItemString11260037
Ref: 3e6511260037
Ref: c-api/dict c PyDict_GetItem11260325
Ref: 3b1811260325
Ref: c-api/dict c PyDict_GetItemWithError11260811
Ref: 3e6611260811
Ref: c-api/dict c PyDict_GetItemString11261176
Ref: 3b1911261176
Ref: c-api/dict c PyDict_SetDefault11261708
Ref: 3e6711261708
Ref: c-api/dict c PyDict_Items11262294
Ref: 3e6811262294
Ref: c-api/dict c PyDict_Keys11262469
Ref: 3e6911262469
Ref: c-api/dict c PyDict_Values11262642
Ref: 3e6a11262642
Ref: c-api/dict c PyDict_Size11262823
Ref: 3e6b11262823
Ref: c-api/dict c PyDict_Next11262985
Ref: 3e6c11262985
Ref: c-api/dict c PyDict_Merge11264888
Ref: 3e6d11264888
Ref: c-api/dict c PyDict_Update11265425
Ref: 3e6e11265425
Ref: c-api/dict c PyDict_MergeFromSeq211265839
Ref: 3e6f11265839
Ref: c-api/dict c PyDict_ClearFreeList11266519
Ref: 3e7011266519
Node: Set Objects11266654
Ref: c-api/set doc11266740
Ref: 3e7111266740
Ref: c-api/set set-objects11266740
Ref: 3e7211266740
Ref: c-api/set setobjects11266740
Ref: 3e7311266740
Ref: c-api/set c PySetObject11267521
Ref: 3e7411267521
Ref: c-api/set c PySet_Type11268154
Ref: 3e7511268154
Ref: c-api/set c PyFrozenSet_Type11268298
Ref: 3e7611268298
Ref: c-api/set c PySet_Check11268600
Ref: 3e7711268600
Ref: c-api/set c PyFrozenSet_Check11268732
Ref: 3e7811268732
Ref: c-api/set c PyAnySet_Check11268876
Ref: 3e7911268876
Ref: c-api/set c PyAnySet_CheckExact11269044
Ref: 3e7a11269044
Ref: c-api/set c PyFrozenSet_CheckExact11269223
Ref: 3e7b11269223
Ref: c-api/set c PySet_New11269377
Ref: db011269377
Ref: c-api/set c PyFrozenSet_New11269826
Ref: db111269826
Ref: c-api/set c PySet_Size11270360
Ref: db511270360
Ref: c-api/set c PySet_GET_SIZE11270665
Ref: 3e7c11270665
Ref: c-api/set c PySet_Contains11270794
Ref: db411270794
Ref: c-api/set c PySet_Add11271301
Ref: db211271301
Ref: c-api/set c PySet_Discard11272049
Ref: db311272049
Ref: c-api/set c PySet_Pop11272606
Ref: 3e7d11272606
Ref: c-api/set c PySet_Clear11272989
Ref: 3e7e11272989
Ref: c-api/set c PySet_ClearFreeList11273081
Ref: 3e7f11273081
Node: 函式物件<2>11273215
Ref: c-api/concrete function-objects11273337
Ref: 3e8011273337
Ref: c-api/concrete otherobjects11273337
Ref: 3e8111273337
Node: 函式（Function）物件11273522
Ref: c-api/function doc11273627
Ref: 3e8211273627
Ref: c-api/function function-objects11273627
Ref: 3e8311273627
Ref: c-api/function id111273627
Ref: 3e8411273627
Ref: c-api/function c PyFunctionObject11273745
Ref: 3e8511273745
Ref: c-api/function c PyFunction_Type11273819
Ref: 3e8611273819
Ref: c-api/function c PyFunction_Check11274034
Ref: 3e8711274034
Ref: c-api/function c PyFunction_New11274215
Ref: 3e8811274215
Ref: c-api/function c PyFunction_NewWithQualName11274766
Ref: 3e8911274766
Ref: c-api/function c PyFunction_GetCode11275236
Ref: 3e8a11275236
Ref: c-api/function c PyFunction_GetGlobals11275395
Ref: 3e8b11275395
Ref: c-api/function c PyFunction_GetModule11275561
Ref: 3e8c11275561
Ref: c-api/function c PyFunction_GetDefaults11275848
Ref: 3e8d11275848
Ref: c-api/function c PyFunction_SetDefaults11276076
Ref: 3e8e11276076
Ref: c-api/function c PyFunction_GetClosure11276351
Ref: 3e8f11276351
Ref: c-api/function c PyFunction_SetClosure11276578
Ref: 3e9011276578
Ref: c-api/function c PyFunction_GetAnnotations11276852
Ref: 3e9111276852
Ref: c-api/function c PyFunction_SetAnnotations11277066
Ref: 3e9211277066
Node: 實體方法物件11277344
Ref: c-api/method doc11277475
Ref: 3e9311277475
Ref: c-api/method instance-method-objects11277475
Ref: 3e9411277475
Ref: c-api/method instancemethod-objects11277475
Ref: 3e9511277475
Ref: c-api/method c PyInstanceMethod_Type11277724
Ref: 3e9611277724
Ref: c-api/method c PyInstanceMethod_Check11277910
Ref: 3e9711277910
Ref: c-api/method c PyInstanceMethod_New11278111
Ref: 3e9811278111
Ref: c-api/method c PyInstanceMethod_Function11278375
Ref: 3e9911278375
Ref: c-api/method c PyInstanceMethod_GET_FUNCTION11278557
Ref: 3e9a11278557
Node: Method Objects<2>11278761
Ref: c-api/method id111278877
Ref: 3e9b11278877
Ref: c-api/method method-objects11278877
Ref: 3e9c11278877
Ref: c-api/method c PyMethod_Type11279103
Ref: 3e9d11279103
Ref: c-api/method c PyMethod_Check11279301
Ref: 3e9e11279301
Ref: c-api/method c PyMethod_New11279476
Ref: 3e9f11279476
Ref: c-api/method c PyMethod_Function11279820
Ref: 3ea011279820
Ref: c-api/method c PyMethod_GET_FUNCTION11279989
Ref: 3ea111279989
Ref: c-api/method c PyMethod_Self11280179
Ref: 3ea211280179
Ref: c-api/method c PyMethod_GET_SELF11280337
Ref: 3ea311280337
Ref: c-api/method c PyMethod_ClearFreeList11280519
Ref: 3ea411280519
Node: Cell 物件11280632
Ref: c-api/cell doc11280745
Ref: 3ea511280745
Ref: c-api/cell cell-objects11280745
Ref: 3ea611280745
Ref: c-api/cell id111280745
Ref: 3ea711280745
Ref: c-api/cell c PyCellObject11281382
Ref: 3ea811281382
Ref: c-api/cell c PyCell_Type11281440
Ref: 3ea911281440
Ref: c-api/cell c PyCell_Check11281523
Ref: 3eaa11281523
Ref: c-api/cell c PyCell_New11281633
Ref: 3eab11281633
Ref: c-api/cell c PyCell_Get11281823
Ref: 3eac11281823
Ref: c-api/cell c PyCell_GET11281947
Ref: 3ead11281947
Ref: c-api/cell c PyCell_Set11282162
Ref: 3eae11282162
Ref: c-api/cell c PyCell_SET11282521
Ref: 3eaf11282521
Ref: c-api/code codeobjects11282781
Ref: 3eb011282781
Node: Code Objects<2>11282782
Ref: c-api/code doc11282869
Ref: 3eb111282869
Ref: c-api/code code-objects11282869
Ref: 3eb211282869
Ref: c-api/code c PyCodeObject11283074
Ref: 3eb311283074
Ref: c-api/code c PyCode_Type11283235
Ref: 3eb411283235
Ref: c-api/code c PyCode_Check11283380
Ref: 3eb511283380
Ref: c-api/code c PyCode_GetNumFree11283482
Ref: 3eb611283482
Ref: c-api/code c PyCode_New11283589
Ref: 27311283589
Ref: c-api/code c PyCode_NewWithPosOnlyArgs11284239
Ref: 27211284239
Ref: c-api/code c PyCode_NewEmpty11284790
Ref: cef11284790
Node: Other Objects11285143
Ref: c-api/concrete other-objects11285239
Ref: 3eb711285239
Node: 檔案（File）物件11285612
Ref: c-api/file doc11285711
Ref: 3eb811285711
Ref: c-api/file file-objects11285711
Ref: 3eb911285711
Ref: c-api/file fileobjects11285711
Ref: 3eba11285711
Ref: c-api/file c PyFile_FromFd11286312
Ref: 3ebb11286312
Ref: c-api/file c PyObject_AsFileDescriptor11287255
Ref: 3ebc11287255
Ref: c-api/file c PyFile_GetLine11287669
Ref: 3ebd11287669
Ref: c-api/file c PyFile_SetOpenCodeHook11288434
Ref: 1fec11288434
Ref: c-api/file c PyFile_WriteObject11289606
Ref: 3ebe11289606
Ref: c-api/file c PyFile_WriteString11289995
Ref: 3ebf11289995
Node: 模組物件模組11290201
Ref: c-api/module doc11290338
Ref: 3ec011290338
Ref: c-api/module module-objects11290338
Ref: 3ec111290338
Ref: c-api/module moduleobjects11290338
Ref: 3ec211290338
Ref: c-api/module c PyModule_Type11290387
Ref: 3ec311290387
Ref: c-api/module c PyModule_Check11290585
Ref: 3ec411290585
Ref: c-api/module c PyModule_CheckExact11290716
Ref: 3ec511290716
Ref: c-api/module c PyModule_NewObject11290867
Ref: 3ec611290867
Ref: c-api/module c PyModule_New11291452
Ref: 3ec711291452
Ref: c-api/module c PyModule_GetDict11291669
Ref: 3ec811291669
Ref: c-api/module c PyModule_GetNameObject11292256
Ref: 3ec911292256
Ref: c-api/module c PyModule_GetName11292572
Ref: 3eca11292572
Ref: c-api/module c PyModule_GetState11292741
Ref: 3ecb11292741
Ref: c-api/module c PyModule_GetDef11292978
Ref: 3ecd11292978
Ref: c-api/module c PyModule_GetFilenameObject11293212
Ref: 3ece11293212
Ref: c-api/module c PyModule_GetFilename11293636
Ref: 3ecf11293636
Node: Initializing C modules11294056
Ref: c-api/module initializing-c-modules11294155
Ref: 3ed011294155
Ref: c-api/module initializing-modules11294155
Ref: 3b6e11294155
Ref: c-api/module c PyModuleDef11294785
Ref: 3b4211294785
Ref: c-api/module c PyModuleDef m_base11295009
Ref: 3ed111295009
Ref: c-api/module c PyModuleDef m_name11295132
Ref: 3ed211295132
Ref: c-api/module c PyModuleDef m_doc11295213
Ref: 3ed311295213
Ref: c-api/module c PyModuleDef m_size11295380
Ref: 3ecc11295380
Ref: c-api/module c PyModuleDef m_methods11296330
Ref: 3ed411296330
Ref: c-api/module c PyModuleDef m_slots11296551
Ref: 3ed511296551
Ref: c-api/module c PyModuleDef m_reload11296925
Ref: 3ed611296925
Ref: c-api/module c PyModuleDef m_traverse11296978
Ref: 3ed711296978
Ref: c-api/module c PyModuleDef m_clear11297361
Ref: 3ed911297361
Ref: c-api/module c PyModuleDef m_free11297731
Ref: 3eda11297731
Ref: Initializing C modules-Footnote-111298267
Node: Single-phase initialization11298316
Ref: c-api/module single-phase-initialization11298437
Ref: 3edb11298437
Ref: c-api/module c PyModule_Create11298712
Ref: 3b0111298712
Ref: c-api/module c PyModule_Create211298993
Ref: 3edc11298993
Node: Multi-phase initialization11299694
Ref: c-api/module id111299859
Ref: 3edd11299859
Ref: c-api/module multi-phase-initialization11299859
Ref: 3b6f11299859
Ref: c-api/module c PyModuleDef_Init11301452
Ref: 3ede11301452
Ref: c-api/module c PyModuleDef_Slot11301899
Ref: 3edf11301899
Ref: c-api/module c PyModuleDef_Slot slot11301931
Ref: 3ee011301931
Ref: c-api/module c PyModuleDef_Slot value11302038
Ref: 3ee111302038
Ref: c-api/module c Py_mod_create11302260
Ref: 3ee211302260
Ref: c-api/module c create_module11302454
Ref: 3ee311302454
Ref: c-api/module c Py_mod_exec11303871
Ref: 3ed811303871
Ref: c-api/module c exec_module11304144
Ref: 3ee411304144
Ref: Multi-phase initialization-Footnote-111304429
Ref: Multi-phase initialization-Footnote-211304478
Node: Low-level module creation functions11304527
Ref: c-api/module low-level-module-creation-functions11304682
Ref: 3ee511304682
Ref: c-api/module c PyModule_FromDefAndSpec11305061
Ref: 7b011305061
Ref: c-api/module c PyModule_FromDefAndSpec211305437
Ref: 7b111305437
Ref: c-api/module c PyModule_ExecDef11306058
Ref: 7b211306058
Ref: c-api/module c PyModule_SetDocString11306237
Ref: 3ee611306237
Ref: c-api/module c PyModule_AddFunctions11306572
Ref: 3ee711306572
Node: Support functions11307256
Ref: c-api/module support-functions11307376
Ref: 3ee811307376
Ref: c-api/module c PyModule_AddObject11307662
Ref: f8311307662
Ref: c-api/module c PyModule_AddIntConstant11308577
Ref: 3ee911308577
Ref: c-api/module c PyModule_AddStringConstant11308872
Ref: 3eea11308872
Ref: c-api/module c PyModule_AddIntMacro11309231
Ref: 3eeb11309231
Ref: c-api/module c PyModule_AddStringMacro11309576
Ref: d5e11309576
Node: Module lookup11309686
Ref: c-api/module module-lookup11309785
Ref: 3eec11309785
Ref: c-api/module c PyState_FindModule11310204
Ref: 3eed11310204
Ref: c-api/module c PyState_AddModule11310686
Ref: 3eee11310686
Ref: c-api/module c PyState_RemoveModule11311582
Ref: 3eef11311582
Node: 迭代器（Iterator）物件11311788
Ref: c-api/iterator doc11311918
Ref: 3ef011311918
Ref: c-api/iterator id111311918
Ref: 3ef111311918
Ref: c-api/iterator iterator-objects11311918
Ref: 3ef211311918
Ref: c-api/iterator c PySeqIter_Type11312335
Ref: 3ef311312335
Ref: c-api/iterator c PySeqIter_Check11312567
Ref: 3ef511312567
Ref: c-api/iterator c PySeqIter_New11312676
Ref: 3ef411312676
Ref: c-api/iterator c PyCallIter_Type11312952
Ref: 3ef611312952
Ref: c-api/iterator c PyCallIter_Check11313158
Ref: 3ef811313158
Ref: c-api/iterator c PyCallIter_New11313269
Ref: 3ef711313269
Node: 修飾器物件11313697
Ref: c-api/descriptor doc11313821
Ref: 3ef911313821
Ref: c-api/descriptor descriptor-objects11313821
Ref: 3efa11313821
Ref: c-api/descriptor id111313821
Ref: 3efb11313821
Ref: c-api/descriptor c PyProperty_Type11313987
Ref: 3efc11313987
Ref: c-api/descriptor c PyDescr_NewGetSet11314088
Ref: 3efd11314088
Ref: c-api/descriptor c PyDescr_NewMember11314226
Ref: 3efe11314226
Ref: c-api/descriptor c PyDescr_NewMethod11314362
Ref: f3c11314362
Ref: c-api/descriptor c PyDescr_NewWrapper11314498
Ref: 3eff11314498
Ref: c-api/descriptor c PyDescr_NewClassMethod11314653
Ref: 3f0011314653
Ref: c-api/descriptor c PyDescr_IsData11314789
Ref: 3f0111314789
Ref: c-api/descriptor c PyWrapper_New11315032
Ref: 3f0211315032
Node: 切片物件11315132
Ref: c-api/slice doc11315242
Ref: 3f0311315242
Ref: c-api/slice id111315242
Ref: 3f0411315242
Ref: c-api/slice slice-objects11315242
Ref: 3f0511315242
Ref: c-api/slice c PySlice_Type11315283
Ref: 3f0611315283
Ref: c-api/slice c PySlice_Check11315430
Ref: 3f0711315430
Ref: c-api/slice c PySlice_New11315552
Ref: 3f0811315552
Ref: c-api/slice c PySlice_GetIndices11316050
Ref: 3f0911316050
Ref: c-api/slice c PySlice_GetIndicesEx11316770
Ref: 47d11316770
Ref: c-api/slice c PySlice_Unpack11318697
Ref: 43411318697
Ref: c-api/slice c PySlice_AdjustIndices11319271
Ref: 43511319271
Node: Ellipsis Object11319707
Ref: c-api/slice ellipsis-object11319820
Ref: 3f0a11319820
Ref: c-api/slice c Py_Ellipsis11319871
Ref: 3f0b11319871
Ref: c-api/memoryview memoryview-objects11320129
Ref: 3d1611320129
Node: MemoryView objects11320130
Ref: c-api/memoryview doc11320246
Ref: 3f0c11320246
Ref: c-api/memoryview id111320246
Ref: 3f0d11320246
Ref: c-api/memoryview c PyMemoryView_FromObject11320460
Ref: 3f0e11320460
Ref: c-api/memoryview c PyMemoryView_FromMemory11320832
Ref: ace11320832
Ref: c-api/memoryview c PyMemoryView_FromBuffer11321129
Ref: 3d1a11321129
Ref: c-api/memoryview c PyMemoryView_GetContiguous11321405
Ref: 3f0f11321405
Ref: c-api/memoryview c PyMemoryView_Check11321895
Ref: 3f1011321895
Ref: c-api/memoryview c PyMemoryView_GET_BUFFER11322092
Ref: 3f1111322092
Ref: c-api/memoryview c PyMemoryView_GET_BASE11322390
Ref: 3f1211322390
Node: 弱參照物件11322757
Ref: c-api/weakref doc11322869
Ref: 3f1311322869
Ref: c-api/weakref weak-reference-objects11322869
Ref: 3f1411322869
Ref: c-api/weakref weakrefobjects11322869
Ref: 3f1511322869
Ref: c-api/weakref c PyWeakref_Check11323168
Ref: 3f1611323168
Ref: c-api/weakref c PyWeakref_CheckRef11323273
Ref: 3f1711323273
Ref: c-api/weakref c PyWeakref_CheckProxy11323365
Ref: 3f1811323365
Ref: c-api/weakref c PyWeakref_NewRef11323455
Ref: 3f1911323455
Ref: c-api/weakref c PyWeakref_NewProxy11324231
Ref: 3f1a11324231
Ref: c-api/weakref c PyWeakref_GetObject11325015
Ref: 3f1b11325015
Ref: c-api/weakref c PyWeakref_GET_OBJECT11325521
Ref: 3f1c11325521
Node: Capsules<2>11325737
Ref: c-api/capsule doc11325846
Ref: 3f1d11325846
Ref: c-api/capsule capsules11325846
Ref: 3b2811325846
Ref: c-api/capsule id111325846
Ref: 3f1e11325846
Ref: c-api/capsule c PyCapsule11326011
Ref: c0c11326011
Ref: c-api/capsule c PyCapsule_Destructor11326457
Ref: 3f1f11326457
Ref: c-api/capsule c PyCapsule_CheckExact11326719
Ref: 3f2011326719
Ref: c-api/capsule c PyCapsule_New11326834
Ref: 3b2611326834
Ref: c-api/capsule c PyCapsule_GetPointer11327745
Ref: 3f2111327745
Ref: c-api/capsule c PyCapsule_GetDestructor11328208
Ref: 3f2211328208
Ref: c-api/capsule c PyCapsule_GetContext11328638
Ref: 3f2311328638
Ref: c-api/capsule c PyCapsule_GetName11329034
Ref: 3f2411329034
Ref: c-api/capsule c PyCapsule_Import11329427
Ref: 3b2711329427
Ref: c-api/capsule c PyCapsule_IsValid11330105
Ref: cf511330105
Ref: c-api/capsule c PyCapsule_SetContext11330873
Ref: 3f2511330873
Ref: c-api/capsule c PyCapsule_SetDestructor11331096
Ref: 3f2611331096
Ref: c-api/capsule c PyCapsule_SetName11331348
Ref: 3f2711331348
Ref: c-api/capsule c PyCapsule_SetPointer11331719
Ref: 3f2811331719
Node: 產生器物件11331980
Ref: c-api/gen doc11332094
Ref: 3f2911332094
Ref: c-api/gen gen-objects11332094
Ref: 3f2a11332094
Ref: c-api/gen generator-objects11332094
Ref: 3f2b11332094
Ref: c-api/gen c PyGenObject11332385
Ref: 3f2e11332385
Ref: c-api/gen c PyGen_Type11332462
Ref: 3f2f11332462
Ref: c-api/gen c PyGen_Check11332559
Ref: 3f3011332559
Ref: c-api/gen c PyGen_CheckExact11332683
Ref: 3f3111332683
Ref: c-api/gen c PyGen_New11332831
Ref: 3f2c11332831
Ref: c-api/gen c PyGen_NewWithQualName11333096
Ref: 3f2d11333096
Node: Coroutine Objects<2>11333510
Ref: c-api/coro doc11333638
Ref: 3f3211333638
Ref: c-api/coro coro-objects11333638
Ref: 7d211333638
Ref: c-api/coro coroutine-objects11333638
Ref: 3f3311333638
Ref: c-api/coro c PyCoroObject11333795
Ref: 3f3411333795
Ref: c-api/coro c PyCoro_Type11333873
Ref: 3f3511333873
Ref: c-api/coro c PyCoro_CheckExact11333971
Ref: 3f3611333971
Ref: c-api/coro c PyCoro_New11334121
Ref: 3f3711334121
Node: Context Variables Objects11334524
Ref: c-api/contextvars doc11334652
Ref: 3f3811334652
Ref: c-api/contextvars context-variables-objects11334652
Ref: 3f3911334652
Ref: c-api/contextvars contextvarsobjects11334652
Ref: 34011334652
Ref: c-api/contextvars contextvarsobjects-pointertype-change11334723
Ref: 4be11334723
Ref: c-api/contextvars c PyContext11335252
Ref: 3f3a11335252
Ref: c-api/contextvars c PyContextVar11335365
Ref: 3f3b11335365
Ref: c-api/contextvars c PyContextToken11335484
Ref: 3f3c11335484
Ref: c-api/contextvars c PyContext_Type11335588
Ref: 3f3d11335588
Ref: c-api/contextvars c PyContextVar_Type11335686
Ref: 3f3e11335686
Ref: c-api/contextvars c PyContextToken_Type11335796
Ref: 3f3f11335796
Ref: c-api/contextvars c PyContext_CheckExact11335934
Ref: 3f4011335934
Ref: c-api/contextvars c PyContextVar_CheckExact11336118
Ref: 3f4111336118
Ref: c-api/contextvars c PyContextToken_CheckExact11336308
Ref: 3f4211336308
Ref: c-api/contextvars c PyContext_New11336540
Ref: 3f4311336540
Ref: c-api/contextvars c PyContext_Copy11336708
Ref: 3f4411336708
Ref: c-api/contextvars c PyContext_CopyCurrent11336910
Ref: 3f4511336910
Ref: c-api/contextvars c PyContext_Enter11337105
Ref: 3f4611337105
Ref: c-api/contextvars c PyContext_Exit11337276
Ref: 3f4711337276
Ref: c-api/contextvars c PyContext_ClearFreeList11337503
Ref: 3f4811337503
Ref: c-api/contextvars c PyContextVar_New11337700
Ref: 3f4911337700
Ref: c-api/contextvars c PyContextVar_Get11338101
Ref: 3f4a11338101
Ref: c-api/contextvars c PyContextVar_Set11338722
Ref: 3f4b11338722
Ref: c-api/contextvars c PyContextVar_Reset11338987
Ref: 3f4c11338987
Ref: Context Variables Objects-Footnote-111339321
Node: DateTime 物件11339364
Ref: c-api/datetime doc11339463
Ref: 3f4d11339463
Ref: c-api/datetime datetime-objects11339463
Ref: 3f4e11339463
Ref: c-api/datetime datetimeobjects11339463
Ref: 3f4f11339463
Ref: c-api/datetime c PyDateTime_TimeZone_UTC11340022
Ref: 43b11340022
Ref: c-api/datetime c PyDate_Check11340230
Ref: 3f5011340230
Ref: c-api/datetime c PyDate_CheckExact11340418
Ref: 3f5111340418
Ref: c-api/datetime c PyDateTime_Check11340569
Ref: 3f5211340569
Ref: c-api/datetime c PyDateTime_CheckExact11340769
Ref: 3f5311340769
Ref: c-api/datetime c PyTime_Check11340928
Ref: 3f5411340928
Ref: c-api/datetime c PyTime_CheckExact11341116
Ref: 3f5511341116
Ref: c-api/datetime c PyDelta_Check11341267
Ref: 3f5611341267
Ref: c-api/datetime c PyDelta_CheckExact11341458
Ref: 3f5711341458
Ref: c-api/datetime c PyTZInfo_Check11341611
Ref: 3f5811341611
Ref: c-api/datetime c PyTZInfo_CheckExact11341805
Ref: 3f5911341805
Ref: c-api/datetime c PyDate_FromDate11341987
Ref: 3f5a11341987
Ref: c-api/datetime c PyDateTime_FromDateAndTime11342183
Ref: 3f5b11342183
Ref: c-api/datetime c PyDateTime_FromDateAndTimeAndFold11342491
Ref: 3f5c11342491
Ref: c-api/datetime c PyTime_FromTime11342856
Ref: 3f5d11342856
Ref: c-api/datetime c PyTime_FromTimeAndFold11343096
Ref: 3f5e11343096
Ref: c-api/datetime c PyDelta_FromDSU11343388
Ref: 3f5f11343388
Ref: c-api/datetime c PyTimeZone_FromOffset11343804
Ref: 43911343804
Ref: c-api/datetime c PyTimeZone_FromOffsetAndName11344076
Ref: 43a11344076
Ref: c-api/datetime c PyDateTime_GET_YEAR11344616
Ref: 3f6011344616
Ref: c-api/datetime c PyDateTime_GET_MONTH11344713
Ref: 3f6111344713
Ref: c-api/datetime c PyDateTime_GET_DAY11344826
Ref: 3f6211344826
Ref: c-api/datetime c PyDateTime_DATE_GET_HOUR11345139
Ref: 3f6311345139
Ref: c-api/datetime c PyDateTime_DATE_GET_MINUTE11345260
Ref: 3f6411345260
Ref: c-api/datetime c PyDateTime_DATE_GET_SECOND11345383
Ref: 3f6511345383
Ref: c-api/datetime c PyDateTime_DATE_GET_MICROSECOND11345501
Ref: 3f6611345501
Ref: c-api/datetime c PyDateTime_TIME_GET_HOUR11345827
Ref: 3f6711345827
Ref: c-api/datetime c PyDateTime_TIME_GET_MINUTE11345944
Ref: 3f6811345944
Ref: c-api/datetime c PyDateTime_TIME_GET_SECOND11346063
Ref: 3f6911346063
Ref: c-api/datetime c PyDateTime_TIME_GET_MICROSECOND11346177
Ref: 3f6a11346177
Ref: c-api/datetime c PyDateTime_DELTA_GET_DAYS11346506
Ref: 3f6b11346506
Ref: c-api/datetime c PyDateTime_DELTA_GET_SECONDS11346670
Ref: 3f6c11346670
Ref: c-api/datetime c PyDateTime_DELTA_GET_MICROSECONDS11346832
Ref: 3f6d11346832
Ref: c-api/datetime c PyDateTime_FromTimestamp11347069
Ref: 3f6e11347069
Ref: c-api/datetime c PyDate_FromTimestamp11347339
Ref: ff011347339
Node: Initialization Finalization and Threads11347597
Ref: c-api/init doc11347775
Ref: 3f6f11347775
Ref: c-api/init initialization11347775
Ref: 3f7011347775
Ref: c-api/init initialization-finalization-and-threads11347775
Ref: 3f7111347775
Node: Before Python Initialization11348277
Ref: c-api/init before-python-initialization11348420
Ref: 3f7211348420
Ref: c-api/init pre-init-safe11348420
Ref: 43f11348420
Node: Global configuration variables11350422
Ref: c-api/init global-conf-vars11350617
Ref: 3f7311350617
Ref: c-api/init global-configuration-variables11350617
Ref: 3f7d11350617
Ref: c-api/init c Py_BytesWarningFlag11351089
Ref: 4b911351089
Ref: c-api/init c Py_DebugFlag11351369
Ref: 3f7e11351369
Ref: c-api/init c Py_DontWriteBytecodeFlag11351597
Ref: 3f7f11351597
Ref: c-api/init c Py_FrozenFlag11351860
Ref: 3f8011351860
Ref: c-api/init c Py_HashRandomizationFlag11352079
Ref: 3f8111352079
Ref: c-api/init c Py_IgnoreEnvironmentFlag11352363
Ref: 4bd11352363
Ref: c-api/init c Py_InspectFlag11352603
Ref: 3f8211352603
Ref: c-api/init c Py_InteractiveFlag11352971
Ref: 3c3911352971
Ref: c-api/init c Py_IsolatedFlag11353049
Ref: 3f8311353049
Ref: c-api/init c Py_LegacyWindowsFSEncodingFlag11353317
Ref: 3c3e11353317
Ref: c-api/init c Py_LegacyWindowsStdioFlag11353697
Ref: 3f8411353697
Ref: c-api/init c Py_NoSiteFlag11354077
Ref: 3f8511354077
Ref: c-api/init c Py_NoUserSiteDirectory11354451
Ref: 3f8611354451
Ref: c-api/init c Py_OptimizeFlag11354711
Ref: 22fb11354711
Ref: c-api/init c Py_QuietFlag11354848
Ref: 3f8711354848
Ref: c-api/init c Py_UnbufferedStdioFlag11355033
Ref: 3f8811355033
Ref: c-api/init c Py_VerboseFlag11355240
Ref: 3f8911355240
Ref: Global configuration variables-Footnote-111355727
Ref: Global configuration variables-Footnote-211355776
Node: Initializing and finalizing the interpreter11355825
Ref: c-api/init initializing-and-finalizing-the-interpreter11356015
Ref: 3f8a11356015
Ref: c-api/init c Py_Initialize11356116
Ref: 43e11356116
Ref: c-api/init c Py_InitializeEx11357087
Ref: 3f8b11357087
Ref: c-api/init c Py_IsInitialized11357364
Ref: 3bb711357364
Ref: c-api/init c Py_FinalizeEx11357633
Ref: 5ce11357633
Ref: c-api/init c Py_Finalize11359764
Ref: cf211359764
Node: Process-wide parameters11359914
Ref: c-api/init process-wide-parameters11360118
Ref: 3f8d11360118
Ref: c-api/init c Py_SetStandardStreamEncoding11360179
Ref: 92a11360179
Ref: c-api/init c Py_SetProgramName11361292
Ref: f8e11361292
Ref: c-api/init c Py_GetProgramName11362204
Ref: 27711362204
Ref: c-api/init c Py_GetPrefix11362433
Ref: 3bb511362433
Ref: c-api/init c Py_GetExecPrefix11363204
Ref: 3bb611363204
Ref: c-api/init c Py_GetProgramFullPath11365371
Ref: 27611365371
Ref: c-api/init c Py_GetPath11365806
Ref: 3bb411365806
Ref: c-api/init c Py_SetPath11366514
Ref: 27411366514
Ref: c-api/init c Py_GetVersion11367723
Ref: 3f7b11367723
Ref: c-api/init c Py_GetPlatform11368283
Ref: 3f7a11368283
Ref: c-api/init c Py_GetCopyright11368870
Ref: 3f7911368870
Ref: c-api/init c Py_GetCompiler11369251
Ref: 3f7811369251
Ref: c-api/init c Py_GetBuildInfo11369632
Ref: d9f11369632
Ref: c-api/init c PySys_SetArgvEx11370040
Ref: bff11370040
Ref: c-api/init c PySys_SetArgv11372014
Ref: cf111372014
Ref: c-api/init c Py_SetPythonHome11372424
Ref: f8d11372424
Ref: c-api/init c Py_GetPythonHome11373016
Ref: 3f7c11373016
Ref: Process-wide parameters-Footnote-111373292
Node: Thread State and the Global Interpreter Lock11373361
Ref: c-api/init thread-state-and-the-global-interpreter-lock11373545
Ref: 3f8e11373545
Ref: c-api/init threads11373545
Ref: 3f8f11373545
Node: Releasing the GIL from extension code11375088
Ref: c-api/init releasing-the-gil-from-extension-code11375241
Ref: 3f9211375241
Node: Non-Python created threads11377118
Ref: c-api/init gilstate11377299
Ref: 3f9311377299
Ref: c-api/init non-python-created-threads11377299
Ref: 3f9411377299
Node: Cautions about fork11379057
Ref: c-api/init cautions-about-fork11379215
Ref: 3f9611379215
Ref: c-api/init fork-and-threads11379215
Ref: 3c3a11379215
Node: High-level API11381142
Ref: c-api/init high-level-api11381287
Ref: 3f9711381287
Ref: c-api/init c PyInterpreterState11381461
Ref: 2c311381461
Ref: c-api/init c PyThreadState11382030
Ref: 3f9011382030
Ref: c-api/init c PyEval_InitThreads11382268
Ref: c1711382268
Ref: c-api/init c PyEval_ThreadsInitialized11382943
Ref: dde11382943
Ref: c-api/init c PyEval_SaveThread11383330
Ref: c1611383330
Ref: c-api/init c PyEval_RestoreThread11383641
Ref: 2b511383641
Ref: c-api/init c PyThreadState_Get11384363
Ref: 3f9111384363
Ref: c-api/init c PyThreadState_Swap11384631
Ref: 3f9811384631
Ref: c-api/init c PyGILState_Ensure11384989
Ref: 2b711384989
Ref: c-api/init c PyGILState_Release11386714
Ref: 3f9511386714
Ref: c-api/init c PyGILState_GetThisThreadState11387200
Ref: 3f9911387200
Ref: c-api/init c PyGILState_Check11387587
Ref: 3f9a11387587
Ref: c-api/init c Py_BEGIN_ALLOW_THREADS11388316
Ref: 3b2011388316
Ref: c-api/init c Py_END_ALLOW_THREADS11388623
Ref: 2b611388623
Ref: c-api/init c Py_BLOCK_THREADS11388907
Ref: 3f9b11388907
Ref: c-api/init c Py_UNBLOCK_THREADS11389093
Ref: 3f9c11389093
Node: Low-level API11389309
Ref: c-api/init low-level-api11389426
Ref: 3f9d11389426
Ref: c-api/init c PyInterpreterState_New11389632
Ref: 34ca11389632
Ref: c-api/init c PyInterpreterState_Clear11389971
Ref: 34c911389971
Ref: c-api/init c PyInterpreterState_Delete11390259
Ref: 3f9e11390259
Ref: c-api/init c PyThreadState_New11390542
Ref: 3f9f11390542
Ref: c-api/init c PyThreadState_Clear11390840
Ref: f2411390840
Ref: c-api/init c PyThreadState_Delete11391006
Ref: 3fa011391006
Ref: c-api/init c PyInterpreterState_GetID11391262
Ref: 44011391262
Ref: c-api/init c PyInterpreterState_GetDict11391507
Ref: 3fa111391507
Ref: c-api/init c PyThreadState_GetDict11392012
Ref: 3fa211392012
Ref: c-api/init c PyThreadState_SetAsyncExc11392511
Ref: 43c11392511
Ref: c-api/init c PyEval_AcquireThread11393295
Ref: 2b411393295
Ref: c-api/init c PyEval_ReleaseThread11394393
Ref: 3fa311394393
Ref: c-api/init c PyEval_AcquireLock11394960
Ref: 2b311394960
Ref: c-api/init c PyEval_ReleaseLock11395996
Ref: c1511395996
Node: Sub-interpreter support11396313
Ref: c-api/init id111396500
Ref: 3fa411396500
Ref: c-api/init sub-interpreter-support11396500
Ref: 3c3b11396500
Ref: c-api/init c Py_NewInterpreter11397427
Ref: 3f8c11397427
Ref: c-api/init c Py_EndInterpreter11400437
Ref: 3fa711400437
Node: Bugs and caveats11401104
Ref: c-api/init bugs-and-caveats11401180
Ref: 3fa611401180
Node: Asynchronous Notifications11402789
Ref: c-api/init asynchronous-notifications11402953
Ref: 3fa811402953
Ref: c-api/init c Py_AddPendingCall11403198
Ref: cee11403198
Node: Profiling and Tracing11404852
Ref: c-api/init profiling11405018
Ref: 3fa911405018
Ref: c-api/init profiling-and-tracing11405018
Ref: 3faa11405018
Ref: c-api/init c Py_tracefunc11405697
Ref: 3fab11405697
Ref: c-api/init c PyTrace_CALL11407944
Ref: 3fac11407944
Ref: c-api/init c PyTrace_EXCEPTION11408332
Ref: 3fad11408332
Ref: c-api/init c PyTrace_LINE11408940
Ref: 3fae11408940
Ref: c-api/init c PyTrace_RETURN11409234
Ref: 3faf11409234
Ref: c-api/init c PyTrace_C_CALL11409385
Ref: 3fb011409385
Ref: c-api/init c PyTrace_C_EXCEPTION11409545
Ref: 3fb111409545
Ref: c-api/init c PyTrace_C_RETURN11409712
Ref: 3fb211409712
Ref: c-api/init c PyTrace_OPCODE11409865
Ref: 3fb311409865
Ref: c-api/init c PyEval_SetProfile11410197
Ref: e4011410197
Ref: c-api/init c PyEval_SetTrace11410749
Ref: e4111410749
Node: Advanced Debugger Support11411297
Ref: c-api/init advanced-debugger-support11411465
Ref: 3fb411411465
Ref: c-api/init advanced-debugging11411465
Ref: 3fb511411465
Ref: c-api/init c PyInterpreterState_Head11411605
Ref: e4411411605
Ref: c-api/init c PyInterpreterState_Main11411759
Ref: 3fa511411759
Ref: c-api/init c PyInterpreterState_Next11411869
Ref: e4511411869
Ref: c-api/init c PyInterpreterState_ThreadHead11412069
Ref: e4611412069
Ref: c-api/init c PyThreadState_Next11412311
Ref: e4711412311
Node: Thread Local Storage Support11412546
Ref: c-api/init thread-local-storage11412684
Ref: 3fb611412684
Ref: c-api/init thread-local-storage-support11412684
Ref: 3fb711412684
Node: Thread Specific Storage TSS API11413812
Ref: c-api/init thread-specific-storage-api11413945
Ref: 31c11413945
Ref: c-api/init thread-specific-storage-tss-api11413945
Ref: 3fb811413945
Ref: c-api/init c Py_tss_t11414328
Ref: 31d11414328
Ref: c-api/init c Py_tss_NEEDS_INIT11414770
Ref: 3fb911414770
Ref: Thread Specific Storage TSS API-Footnote-111415059
Node: Dynamic Allocation11415108
Ref: c-api/init dynamic-allocation11415213
Ref: 3fba11415213
Ref: c-api/init c PyThread_tss_alloc11415494
Ref: 3fbb11415494
Ref: c-api/init c PyThread_tss_free11415712
Ref: 3fbc11415712
Node: Methods<4>11416134
Ref: c-api/init methods11416239
Ref: 3fbe11416239
Ref: c-api/init c PyThread_tss_is_created11416545
Ref: 3fc211416545
Ref: c-api/init c PyThread_tss_create11416732
Ref: 3fc111416732
Ref: c-api/init c PyThread_tss_delete11417147
Ref: 3fbd11417147
Ref: c-api/init c PyThread_tss_set11417577
Ref: 3fbf11417577
Ref: c-api/init c PyThread_tss_get11417844
Ref: 3fc011417844
Node: Thread Local Storage TLS API11418079
Ref: c-api/init thread-local-storage-api11418212
Ref: 31b11418212
Ref: c-api/init thread-local-storage-tls-api11418212
Ref: 3fc311418212
Ref: c-api/init c PyThread_create_key11418829
Ref: 3fc411418829
Ref: c-api/init c PyThread_delete_key11418871
Ref: 3fc511418871
Ref: c-api/init c PyThread_set_key_value11418921
Ref: 97511418921
Ref: c-api/init c PyThread_get_key_value11418986
Ref: 3fc611418986
Ref: c-api/init c PyThread_delete_key_value11419040
Ref: 3fc711419040
Ref: c-api/init c PyThread_ReInitTLS11419096
Ref: 3fc811419096
Node: Python Initialization Configuration11419138
Ref: c-api/init_config doc11419309
Ref: 3fc911419309
Ref: c-api/init_config init-config11419309
Ref: 17e11419309
Ref: c-api/init_config python-initialization-configuration11419309
Ref: 3fca11419309
Ref: Python Initialization Configuration-Footnote-111421267
Node: PyWideStringList11421316
Ref: c-api/init_config pywidestringlist11421421
Ref: 3fcc11421421
Ref: c-api/init_config c PyWideStringList11421470
Ref: 16311421470
Ref: c-api/init_config c PyWideStringList_Append11421662
Ref: 17511421662
Ref: c-api/init_config c PyWideStringList_Insert11421876
Ref: 17611421876
Ref: c-api/init_config c PyWideStringList length11422315
Ref: 3fcd11422315
Ref: c-api/init_config c PyWideStringList items11422383
Ref: 3fce11422383
Node: PyStatus11422448
Ref: c-api/init_config pystatus11422573
Ref: 3fcf11422573
Ref: c-api/init_config c PyStatus11422606
Ref: 16211422606
Ref: c-api/init_config c PyStatus exitcode11422826
Ref: 3fd011422826
Ref: c-api/init_config c PyStatus err_msg11422921
Ref: 3fd111422921
Ref: c-api/init_config c PyStatus func11422993
Ref: 3fd211422993
Ref: c-api/init_config c PyStatus_Ok11423147
Ref: 17411423147
Ref: c-api/init_config c PyStatus_Error11423215
Ref: 16e11423215
Ref: c-api/init_config c PyStatus_NoMemory11423329
Ref: 17311423329
Ref: c-api/init_config c PyStatus_Exit11423437
Ref: 17011423437
Ref: c-api/init_config c PyStatus_Exception11423584
Ref: 16f11423584
Ref: c-api/init_config c PyStatus_IsError11423813
Ref: 17111423813
Ref: c-api/init_config c PyStatus_IsExit11423907
Ref: 17211423907
Ref: c-api/init_config c Py_ExitStatusException11423999
Ref: 17811423999
Node: PyPreConfig11424940
Ref: c-api/init_config pypreconfig11425083
Ref: 3fd311425083
Ref: c-api/init_config c PyPreConfig11425122
Ref: 16111425122
Ref: c-api/init_config c PyPreConfig_InitPythonConfig11425358
Ref: 16d11425358
Ref: c-api/init_config c PyPreConfig_InitIsolatedConfig11425544
Ref: 16c11425544
Ref: c-api/init_config c PyPreConfig allocator11425758
Ref: 3fd611425758
Ref: c-api/init_config c PyPreConfig configure_locale11426861
Ref: 3fd811426861
Ref: c-api/init_config c PyPreConfig coerce_c_locale11427073
Ref: 3fd911427073
Ref: c-api/init_config c PyPreConfig coerce_c_locale_warn11427253
Ref: 3fda11427253
Ref: c-api/init_config c PyPreConfig dev_mode11427371
Ref: 3fdb11427371
Ref: c-api/init_config c PyPreConfig isolated11427456
Ref: 3fdd11427456
Ref: c-api/init_config c PyPreConfig legacy_windows_fs_encoding11427541
Ref: 3fdf11427541
Ref: c-api/init_config c PyPreConfig parse_argv11427896
Ref: 3fe011427896
Ref: c-api/init_config c PyPreConfig use_environment11428212
Ref: 3fe111428212
Ref: c-api/init_config c PyPreConfig utf8_mode11428311
Ref: 3fe311428311
Node: Preinitialization with PyPreConfig11428398
Ref: c-api/init_config preinitialization-with-pypreconfig11428541
Ref: 3fe411428541
Ref: c-api/init_config c Py_PreInitialize11428662
Ref: 17a11428662
Ref: c-api/init_config c Py_PreInitializeFromBytesArgs11428796
Ref: 17c11428796
Ref: c-api/init_config c Py_PreInitializeFromArgs11429031
Ref: 17b11429031
Node: PyConfig11430800
Ref: c-api/init_config pyconfig11430960
Ref: 3fe511430960
Ref: c-api/init_config c PyConfig11430993
Ref: 16011430993
Ref: c-api/init_config c PyConfig_InitPythonConfig11431106
Ref: 16611431106
Ref: c-api/init_config c PyConfig_InitIsolatedConfig11431261
Ref: 16511431261
Ref: c-api/init_config c PyConfig_SetString11431420
Ref: 16b11431420
Ref: c-api/init_config c PyConfig_SetBytesString11431666
Ref: 16a11431666
Ref: c-api/init_config c PyConfig_SetArgv11431949
Ref: 16811431949
Ref: c-api/init_config c PyConfig_SetBytesArgv11432172
Ref: 16911432172
Ref: c-api/init_config c PyConfig_SetWideStringList11432428
Ref: 3fcb11432428
Ref: c-api/init_config c PyConfig_Read11432708
Ref: 16711432708
Ref: c-api/init_config c PyConfig_Clear11432923
Ref: 16411432923
Ref: c-api/init_config c PyConfig argv11433967
Ref: 3fe711433967
Ref: c-api/init_config c PyConfig base_exec_prefix11434364
Ref: 3fe811434364
Ref: c-api/init_config c PyConfig base_executable11434461
Ref: 3fe911434461
Ref: c-api/init_config c PyConfig base_prefix11434659
Ref: 3feb11434659
Ref: c-api/init_config c PyConfig buffered_stdio11434746
Ref: 3fec11434746
Ref: c-api/init_config c PyConfig bytes_warning11434953
Ref: 3fed11434953
Ref: c-api/init_config c PyConfig check_hash_pycs_mode11435272
Ref: 3fee11435272
Ref: c-api/init_config c PyConfig configure_c_stdio11435623
Ref: 3fef11435623
Ref: c-api/init_config c PyConfig dev_mode11435846
Ref: 3fdc11435846
Ref: c-api/init_config c PyConfig dump_refs11435937
Ref: 3ff011435937
Ref: c-api/init_config c PyConfig exec_prefix11436146
Ref: 3ff111436146
Ref: c-api/init_config c PyConfig executable11436233
Ref: 3fea11436233
Ref: c-api/init_config c PyConfig faulthandler11436317
Ref: 3ff211436317
Ref: c-api/init_config c PyConfig filesystem_encoding11436445
Ref: 3ff311436445
Ref: c-api/init_config c PyConfig filesystem_errors11436572
Ref: 3ff411436572
Ref: c-api/init_config c PyConfig hash_seed11436718
Ref: 3ff511436718
Ref: c-api/init_config c PyConfig use_hash_seed11436768
Ref: 3ff611436768
Ref: c-api/init_config c PyConfig home11437007
Ref: 3ff711437007
Ref: c-api/init_config c PyConfig import_time11437181
Ref: 3ff811437181
Ref: c-api/init_config c PyConfig inspect11437268
Ref: 3ff911437268
Ref: c-api/init_config c PyConfig install_signal_handlers11437379
Ref: ed811437379
Ref: c-api/init_config c PyConfig interactive11437469
Ref: 3ffa11437469
Ref: c-api/init_config c PyConfig isolated11437540
Ref: 3fde11437540
Ref: c-api/init_config c PyConfig legacy_windows_stdio11438090
Ref: 3ffc11438090
Ref: c-api/init_config c PyConfig malloc_stats11438442
Ref: 3ffd11438442
Ref: c-api/init_config c PyConfig pythonpath_env11438686
Ref: 3ffe11438686
Ref: c-api/init_config c PyConfig module_search_paths11438939
Ref: 3fff11438939
Ref: c-api/init_config c PyConfig module_search_paths_set11439002
Ref: 400011439002
Ref: c-api/init_config c PyConfig optimization_level11439289
Ref: 400211439289
Ref: c-api/init_config c PyConfig parse_argv11439571
Ref: 3fe611439571
Ref: c-api/init_config c PyConfig parser_debug11439826
Ref: 400311439826
Ref: c-api/init_config c PyConfig pathconfig_warnings11439988
Ref: 400411439988
Ref: c-api/init_config c PyConfig prefix11440254
Ref: 400511440254
Ref: c-api/init_config c PyConfig program_name11440331
Ref: 400611440331
Ref: c-api/init_config c PyConfig pycache_prefix11440487
Ref: 400711440487
Ref: c-api/init_config c PyConfig quiet11440684
Ref: 400811440684
Ref: c-api/init_config c PyConfig run_command11440839
Ref: 400911440839
Ref: c-api/init_config c PyConfig run_filename11440976
Ref: 400a11440976
Ref: c-api/init_config c PyConfig run_module11441102
Ref: 400b11441102
Ref: c-api/init_config c PyConfig show_alloc_count11441237
Ref: 400c11441237
Ref: c-api/init_config c PyConfig show_ref_count11441479
Ref: 400d11441479
Ref: c-api/init_config c PyConfig site_import11441737
Ref: 400e11441737
Ref: c-api/init_config c PyConfig skip_source_first_line11441836
Ref: 400f11441836
Ref: c-api/init_config c PyConfig stdio_encoding11441935
Ref: 401011441935
Ref: c-api/init_config c PyConfig stdio_errors11441985
Ref: 401111441985
Ref: c-api/init_config c PyConfig tracemalloc11442158
Ref: 401211442158
Ref: c-api/init_config c PyConfig use_environment11442274
Ref: 3fe211442274
Ref: c-api/init_config c PyConfig user_site_directory11442389
Ref: 3ffb11442389
Ref: c-api/init_config c PyConfig verbose11442511
Ref: 401311442511
Ref: c-api/init_config c PyConfig warnoptions11442594
Ref: 401411442594
Ref: c-api/init_config c PyConfig write_bytecode11443075
Ref: 401511443075
Ref: c-api/init_config c PyConfig xoptions11443294
Ref: 401611443294
Ref: PyConfig-Footnote-111443727
Node: Initialization with PyConfig11443776
Ref: c-api/init_config initialization-with-pyconfig11443924
Ref: 401711443924
Ref: c-api/init_config c Py_InitializeFromConfig11444029
Ref: 17911444029
Node: Isolated Configuration11446731
Ref: c-api/init_config init-isolated-conf11446891
Ref: 3fd511446891
Ref: c-api/init_config isolated-configuration11446891
Ref: 401811446891
Node: Python Configuration11447682
Ref: c-api/init_config init-python-config11447832
Ref: 3fd411447832
Ref: c-api/init_config python-configuration11447832
Ref: 401911447832
Ref: Python Configuration-Footnote-111449408
Ref: Python Configuration-Footnote-211449457
Node: Path Configuration11449506
Ref: c-api/init_config init-path-config11449644
Ref: 400111449644
Ref: c-api/init_config path-configuration11449644
Ref: 401a11449644
Node: Py_RunMain11453068
Ref: c-api/init_config py-runmain11453236
Ref: 401b11453236
Ref: c-api/init_config c Py_RunMain11453279
Ref: 17d11453279
Node: Multi-Phase Initialization Private Provisional API11453871
Ref: c-api/init_config multi-phase-initialization-private-provisional-api11454012
Ref: 401c11454012
Ref: c-api/init_config c _Py_InitializeMain11455193
Ref: 401d11455193
Ref: Multi-Phase Initialization Private Provisional API-Footnote-111457186
Ref: Multi-Phase Initialization Private Provisional API-Footnote-211457235
Node: 記憶體管理11457284
Ref: c-api/memory doc11457445
Ref: 401e11457445
Ref: c-api/memory memory11457445
Ref: 3fd711457445
Ref: c-api/memory memory-management11457445
Ref: 401f11457445
Node: 總覽<2>11457719
Ref: c-api/memory memoryoverview11457809
Ref: 402011457809
Ref: c-api/memory overview11457809
Ref: 402111457809
Node: Raw Memory Interface11461718
Ref: c-api/memory raw-memory-interface11461833
Ref: 402211461833
Ref: c-api/memory c PyMem_RawMalloc11462272
Ref: 97211462272
Ref: c-api/memory c PyMem_RawCalloc11462658
Ref: 7aa11462658
Ref: c-api/memory c PyMem_RawRealloc11463155
Ref: 97311463155
Ref: c-api/memory c PyMem_RawFree11463902
Ref: 3c3f11463902
Node: Memory Interface11464306
Ref: c-api/memory memory-interface11464429
Ref: 402311464429
Ref: c-api/memory memoryinterface11464429
Ref: 402411464429
Ref: c-api/memory c PyMem_Malloc11464920
Ref: 50a11464920
Ref: c-api/memory c PyMem_Calloc11465300
Ref: 7ab11465300
Ref: c-api/memory c PyMem_Realloc11465791
Ref: 97411465791
Ref: c-api/memory c PyMem_Free11466520
Ref: dae11466520
Ref: c-api/memory c PyMem_New11467016
Ref: 402511467016
Ref: c-api/memory c PyMem_Resize11467265
Ref: 402611467265
Ref: c-api/memory c PyMem_Del11467731
Ref: 402711467731
Node: Object allocators11468305
Ref: c-api/memory object-allocators11468433
Ref: 402811468433
Ref: c-api/memory c PyObject_Malloc11468838
Ref: 50d11468838
Ref: c-api/memory c PyObject_Calloc11469224
Ref: 7ac11469224
Ref: c-api/memory c PyObject_Realloc11469721
Ref: daf11469721
Ref: c-api/memory c PyObject_Free11470468
Ref: 50911470468
Node: Default Memory Allocators11470872
Ref: c-api/memory default-memory-allocators11471011
Ref: 136211471011
Ref: c-api/memory id111471011
Ref: 402911471011
Node: Customize Memory Allocators11473303
Ref: c-api/memory customize-memory-allocators11473447
Ref: 402a11473447
Ref: c-api/memory c PyMemAllocatorEx11473537
Ref: 7cf11473537
Ref: c-api/memory c PyMemAllocatorDomain11475350
Ref: 402b11475350
Ref: c-api/memory c PYMEM_DOMAIN_RAW11475445
Ref: 136311475445
Ref: c-api/memory c PYMEM_DOMAIN_MEM11475688
Ref: 50e11475688
Ref: c-api/memory c PYMEM_DOMAIN_OBJ11475918
Ref: 50c11475918
Ref: c-api/memory c PyMem_GetAllocator11476160
Ref: 3f7611476160
Ref: c-api/memory c PyMem_SetAllocator11476330
Ref: 3f7411476330
Ref: c-api/memory c PyMem_SetupDebugHooks11476975
Ref: 50f11476975
Node: The pymalloc allocator11479087
Ref: c-api/memory pymalloc11479223
Ref: 5c611479223
Ref: c-api/memory the-pymalloc-allocator11479223
Ref: 402c11479223
Node: Customize pymalloc Arena Allocator11480055
Ref: c-api/memory customize-pymalloc-arena-allocator11480148
Ref: 402d11480148
Ref: c-api/memory c PyObjectArenaAllocator11480256
Ref: 402e11480256
Ref: c-api/memory c PyObject_GetArenaAllocator11481262
Ref: 3f7711481262
Ref: c-api/memory c PyObject_SetArenaAllocator11481386
Ref: 3f7511481386
Node: tracemalloc C API11481510
Ref: c-api/memory tracemalloc-c-api11481631
Ref: 402f11481631
Ref: c-api/memory c PyTraceMalloc_Track11481701
Ref: 42911481701
Ref: c-api/memory c PyTraceMalloc_Untrack11482112
Ref: 42a11482112
Node: Examples<34>11482402
Ref: c-api/memory examples11482492
Ref: 403011482492
Ref: c-api/memory memoryexamples11482492
Ref: 403111482492
Node: Object Implementation Support11484403
Ref: c-api/objimpl doc11484551
Ref: 403211484551
Ref: c-api/objimpl newtypes11484551
Ref: 403311484551
Ref: c-api/objimpl object-implementation-support11484551
Ref: 403411484551
Node: Allocating Objects on the Heap11485054
Ref: c-api/allocation doc11485177
Ref: 403511485177
Ref: c-api/allocation allocating-objects11485177
Ref: 403611485177
Ref: c-api/allocation allocating-objects-on-the-heap11485177
Ref: 403711485177
Ref: c-api/allocation c _PyObject_New11485254
Ref: 403811485254
Ref: c-api/allocation c _PyObject_NewVar11485350
Ref: 403911485350
Ref: c-api/allocation c PyObject_Init11485479
Ref: 27011485479
Ref: c-api/allocation c PyObject_InitVar11485916
Ref: 403a11485916
Ref: c-api/allocation c PyObject_New11486205
Ref: 2d311486205
Ref: c-api/allocation c PyObject_NewVar11486648
Ref: 2d411486648
Ref: c-api/allocation c PyObject_Del11487373
Ref: e1b11487373
Ref: c-api/allocation c _Py_NoneStruct11487762
Ref: 403b11487762
Node: 通用物件結構11488077
Ref: c-api/structures doc11488224
Ref: 403c11488224
Ref: c-api/structures common-object-structures11488224
Ref: 403d11488224
Ref: c-api/structures common-structs11488224
Ref: 403e11488224
Ref: c-api/structures c PyObject11488797
Ref: 4bf11488797
Ref: c-api/structures c PyVarObject11489379
Ref: 403f11489379
Ref: c-api/structures c PyObject_HEAD11489761
Ref: c7711489761
Ref: c-api/structures c PyObject_VAR_HEAD11490023
Ref: 404111490023
Ref: c-api/structures c Py_TYPE11490327
Ref: 3b3011490327
Ref: c-api/structures c Py_REFCNT11490494
Ref: 3b2f11490494
Ref: c-api/structures c Py_SIZE11490667
Ref: 404011490667
Ref: c-api/structures c PyObject_HEAD_INIT11490837
Ref: 404211490837
Ref: c-api/structures c PyVarObject_HEAD_INIT11491056
Ref: 404311491056
Ref: c-api/structures c PyCFunction11491334
Ref: de011491334
Ref: c-api/structures c PyCFunctionWithKeywords11491775
Ref: 404411491775
Ref: c-api/structures c _PyCFunctionFast11491938
Ref: 404511491938
Ref: c-api/structures c _PyCFunctionFastWithKeywords11492084
Ref: 404611492084
Ref: c-api/structures c PyMethodDef11492253
Ref: e2011492253
Ref: c-api/structures METH_VARARGS11494207
Ref: e4d11494207
Ref: c-api/structures METH_FASTCALL11495136
Ref: fbd11495136
Ref: c-api/structures METH_NOARGS11496235
Ref: e1d11496235
Ref: c-api/structures METH_O11496634
Ref: e4c11496634
Ref: c-api/structures METH_CLASS11497223
Ref: e1e11497223
Ref: c-api/structures METH_STATIC11497496
Ref: e1f11497496
Ref: c-api/structures METH_COEXIST11497881
Ref: 404711497881
Ref: c-api/structures c PyMemberDef11498547
Ref: 42b11498547
Ref: c-api/structures c PyGetSetDef11502674
Ref: 42c11502674
Node: Type Objects<3>11504810
Ref: c-api/typeobj doc11504951
Ref: 404811504951
Ref: c-api/typeobj type-objects11504951
Ref: 404911504951
Ref: c-api/typeobj type-structs11504951
Ref: 3b3111504951
Node: Quick Reference11506180
Ref: c-api/typeobj quick-reference11506279
Ref: 404b11506279
Node: "tp slots"11506387
Ref: c-api/typeobj tp-slots11506467
Ref: 404c11506467
Ref: c-api/typeobj tp-slots-table11506467
Ref: 404d11506467
Ref: "tp slots"-Footnote-111519659
Ref: "tp slots"-Footnote-211519924
Node: sub-slots11520697
Ref: c-api/typeobj id311520799
Ref: 407411520799
Ref: c-api/typeobj sub-slots11520799
Ref: 405311520799
Node: slot typedefs11530984
Ref: c-api/typeobj slot-typedefs11531067
Ref: 40ae11531067
Ref: c-api/typeobj slot-typedefs-table11531067
Ref: 404e11531067
Node: PyTypeObject Definition11538867
Ref: c-api/typeobj pytypeobject-definition11538989
Ref: 40b111538989
Node: PyObject Slots11541814
Ref: c-api/typeobj pyobject-slots11541938
Ref: 40b211541938
Ref: c-api/typeobj c PyObject _ob_next11542360
Ref: 40b311542360
Ref: c-api/typeobj c PyObject _ob_prev11542408
Ref: 40b411542408
Ref: c-api/typeobj c PyObject ob_refcnt11543164
Ref: 40b511543164
Ref: c-api/typeobj c PyObject ob_type11543663
Ref: 40b611543663
Node: PyVarObject Slots11544756
Ref: c-api/typeobj pyvarobject-slots11544875
Ref: 40b711544875
Ref: c-api/typeobj c PyVarObject ob_size11544930
Ref: 40b811544930
Node: PyTypeObject Slots11545225
Ref: c-api/typeobj pytypeobject-slots11545340
Ref: 40b911545340
Ref: c-api/typeobj c PyTypeObject tp_name11545689
Ref: 3b5511545689
Ref: c-api/typeobj c PyTypeObject tp_basicsize11547400
Ref: 3b3311547400
Ref: c-api/typeobj c PyTypeObject tp_itemsize11547457
Ref: 3b3211547457
Ref: c-api/typeobj c PyTypeObject tp_dealloc11550112
Ref: 3b3911550112
Ref: c-api/typeobj c PyTypeObject tp_vectorcall_offset11552170
Ref: 3cbc11552170
Ref: c-api/typeobj c PyVectorcall_Call11553310
Ref: 40bc11553310
Ref: c-api/typeobj c PyTypeObject tp_getattr11554924
Ref: 3b5c11554924
Ref: c-api/typeobj c PyTypeObject tp_setattr11555651
Ref: 3b5d11555651
Ref: c-api/typeobj c PyTypeObject tp_as_async11556398
Ref: 405211556398
Ref: c-api/typeobj c PyTypeObject tp_repr11556939
Ref: 3b5411556939
Ref: c-api/typeobj c PyTypeObject tp_as_number11557894
Ref: 405511557894
Ref: c-api/typeobj c PyTypeObject tp_as_sequence11558301
Ref: 405611558301
Ref: c-api/typeobj c PyTypeObject tp_as_mapping11558718
Ref: 405711558718
Ref: c-api/typeobj c PyTypeObject tp_hash11559130
Ref: 3b6511559130
Ref: c-api/typeobj c PyTypeObject tp_call11560724
Ref: 3b6611560724
Ref: c-api/typeobj c PyTypeObject tp_str11561130
Ref: 3b5611561130
Ref: c-api/typeobj c PyTypeObject tp_getattro11562079
Ref: 3b5911562079
Ref: c-api/typeobj c PyTypeObject tp_setattro11562948
Ref: 3b5a11562948
Ref: c-api/typeobj c PyTypeObject tp_as_buffer11563948
Ref: 405c11563948
Ref: c-api/typeobj c PyTypeObject tp_flags11564354
Ref: 3d5b11564354
Ref: c-api/typeobj Py_TPFLAGS_HEAPTYPE11566252
Ref: 3d6311566252
Ref: c-api/typeobj Py_TPFLAGS_BASETYPE11566897
Ref: 3b4111566897
Ref: c-api/typeobj Py_TPFLAGS_READY11567170
Ref: 40c211567170
Ref: c-api/typeobj Py_TPFLAGS_READYING11567360
Ref: 40c311567360
Ref: c-api/typeobj Py_TPFLAGS_HAVE_GC11567559
Ref: 3b4811567559
Ref: c-api/typeobj Py_TPFLAGS_DEFAULT11568540
Ref: 3b3411568540
Ref: c-api/typeobj Py_TPFLAGS_METHOD_DESCRIPTOR11568920
Ref: 40c511568920
Ref: c-api/typeobj Py_TPFLAGS_LONG_SUBCLASS11569779
Ref: 40c611569779
Ref: c-api/typeobj Py_TPFLAGS_LIST_SUBCLASS11569820
Ref: 40c711569820
Ref: c-api/typeobj Py_TPFLAGS_TUPLE_SUBCLASS11569861
Ref: 40c811569861
Ref: c-api/typeobj Py_TPFLAGS_BYTES_SUBCLASS11569903
Ref: 40c911569903
Ref: c-api/typeobj Py_TPFLAGS_UNICODE_SUBCLASS11569945
Ref: 40ca11569945
Ref: c-api/typeobj Py_TPFLAGS_DICT_SUBCLASS11569989
Ref: 40cb11569989
Ref: c-api/typeobj Py_TPFLAGS_BASE_EXC_SUBCLASS11570030
Ref: 40cc11570030
Ref: c-api/typeobj Py_TPFLAGS_TYPE_SUBCLASS11570075
Ref: 40cd11570075
Ref: c-api/typeobj Py_TPFLAGS_HAVE_FINALIZE11570633
Ref: 2d911570633
Ref: c-api/typeobj _Py_TPFLAGS_HAVE_VECTORCALL11571002
Ref: 40ba11571002
Ref: c-api/typeobj c PyTypeObject tp_doc11571900
Ref: 3b3511571900
Ref: c-api/typeobj c PyTypeObject tp_traverse11572218
Ref: 36be11572218
Ref: c-api/typeobj c PyTypeObject tp_clear11575138
Ref: 3b5211575138
Ref: c-api/typeobj c PyTypeObject tp_richcompare11578471
Ref: 3b5f11578471
Ref: c-api/typeobj c Py_RETURN_RICHCOMPARE11580002
Ref: 42711580002
Ref: c-api/typeobj c PyTypeObject tp_weaklistoffset11581236
Ref: 3b6811581236
Ref: c-api/typeobj c PyTypeObject tp_iter11583025
Ref: e3511583025
Ref: c-api/typeobj c PyTypeObject tp_iternext11583505
Ref: e3611583505
Ref: c-api/typeobj c PyTypeObject tp_methods11584303
Ref: 3b4011584303
Ref: c-api/typeobj c PyTypeObject tp_members11584805
Ref: 3b3e11584805
Ref: c-api/typeobj c PyTypeObject tp_getset11585343
Ref: 3b4411585343
Ref: c-api/typeobj c PyTypeObject tp_base11585873
Ref: 3b4a11585873
Ref: c-api/typeobj c PyTypeObject tp_dict11587171
Ref: 3d6f11587171
Ref: c-api/typeobj c PyTypeObject tp_descr_get11588154
Ref: 406311588154
Ref: c-api/typeobj c PyTypeObject tp_descr_set11588452
Ref: 406511588452
Ref: c-api/typeobj c PyTypeObject tp_dictoffset11588849
Ref: 3d7411588849
Ref: c-api/typeobj c PyTypeObject tp_init11592113
Ref: 3b3d11592113
Ref: c-api/typeobj c PyTypeObject tp_alloc11593575
Ref: 3b3b11593575
Ref: c-api/typeobj c PyTypeObject tp_new11594266
Ref: 3b3611594266
Ref: c-api/typeobj c PyTypeObject tp_free11595836
Ref: 3b3a11595836
Ref: c-api/typeobj c PyTypeObject tp_is_gc11596526
Ref: 406b11596526
Ref: c-api/typeobj c PyTypeObject tp_bases11597683
Ref: 406c11597683
Ref: c-api/typeobj c PyTypeObject tp_mro11597937
Ref: 3d7011597937
Ref: c-api/typeobj c PyTypeObject tp_cache11598261
Ref: 3d7111598261
Ref: c-api/typeobj c PyTypeObject tp_subclasses11598404
Ref: 3d7211598404
Ref: c-api/typeobj c PyTypeObject tp_weaklist11598583
Ref: 3d7311598583
Ref: c-api/typeobj c PyTypeObject tp_del11598808
Ref: 406d11598808
Ref: c-api/typeobj c PyTypeObject tp_version_tag11598930
Ref: 406e11598930
Ref: c-api/typeobj c PyTypeObject tp_finalize11599111
Ref: 2d811599111
Ref: c-api/typeobj c PyTypeObject tp_allocs11600834
Ref: 406f11600834
Ref: c-api/typeobj c PyTypeObject tp_frees11600918
Ref: 407011600918
Ref: c-api/typeobj c PyTypeObject tp_maxalloc11600995
Ref: 407111600995
Ref: c-api/typeobj c PyTypeObject tp_prev11601100
Ref: 407211601100
Ref: c-api/typeobj c PyTypeObject tp_next11601249
Ref: 407311601249
Ref: PyTypeObject Slots-Footnote-111602087
Node: Heap Types11602136
Ref: c-api/typeobj heap-types11602225
Ref: 3d6111602225
Ref: c-api/typeobj id411602225
Ref: 40bd11602225
Node: Number Object Structures11603389
Ref: c-api/typeobj number-object-structures11603537
Ref: 40ce11603537
Ref: c-api/typeobj number-structs11603537
Ref: 40bf11603537
Ref: c-api/typeobj c PyNumberMethods11603602
Ref: d8611603602
Ref: c-api/typeobj c PyNumberMethods nb_add11606034
Ref: 3d6d11606034
Ref: c-api/typeobj c PyNumberMethods nb_subtract11606089
Ref: 407b11606089
Ref: c-api/typeobj c PyNumberMethods nb_multiply11606149
Ref: 407d11606149
Ref: c-api/typeobj c PyNumberMethods nb_remainder11606209
Ref: 407f11606209
Ref: c-api/typeobj c PyNumberMethods nb_divmod11606270
Ref: 408111606270
Ref: c-api/typeobj c PyNumberMethods nb_power11606328
Ref: 408211606328
Ref: c-api/typeobj c PyNumberMethods nb_negative11606386
Ref: 408411606386
Ref: c-api/typeobj c PyNumberMethods nb_positive11606445
Ref: 408511606445
Ref: c-api/typeobj c PyNumberMethods nb_absolute11606504
Ref: 408611606504
Ref: c-api/typeobj c PyNumberMethods nb_bool11606563
Ref: 408711606563
Ref: c-api/typeobj c PyNumberMethods nb_invert11606616
Ref: 408811606616
Ref: c-api/typeobj c PyNumberMethods nb_lshift11606673
Ref: 408911606673
Ref: c-api/typeobj c PyNumberMethods nb_rshift11606731
Ref: 408b11606731
Ref: c-api/typeobj c PyNumberMethods nb_and11606789
Ref: 408d11606789
Ref: c-api/typeobj c PyNumberMethods nb_xor11606844
Ref: 408f11606844
Ref: c-api/typeobj c PyNumberMethods nb_or11606899
Ref: 409111606899
Ref: c-api/typeobj c PyNumberMethods nb_int11606953
Ref: 409311606953
Ref: c-api/typeobj c PyNumberMethods nb_reserved11607007
Ref: 409411607007
Ref: c-api/typeobj c PyNumberMethods nb_float11607062
Ref: 409511607062
Ref: c-api/typeobj c PyNumberMethods nb_inplace_add11607118
Ref: 407a11607118
Ref: c-api/typeobj c PyNumberMethods nb_inplace_subtract11607181
Ref: 407c11607181
Ref: c-api/typeobj c PyNumberMethods nb_inplace_multiply11607249
Ref: 407e11607249
Ref: c-api/typeobj c PyNumberMethods nb_inplace_remainder11607317
Ref: 408011607317
Ref: c-api/typeobj c PyNumberMethods nb_inplace_power11607386
Ref: 408311607386
Ref: c-api/typeobj c PyNumberMethods nb_inplace_lshift11607452
Ref: 408a11607452
Ref: c-api/typeobj c PyNumberMethods nb_inplace_rshift11607518
Ref: 408c11607518
Ref: c-api/typeobj c PyNumberMethods nb_inplace_and11607584
Ref: 408e11607584
Ref: c-api/typeobj c PyNumberMethods nb_inplace_xor11607647
Ref: 409011607647
Ref: c-api/typeobj c PyNumberMethods nb_inplace_or11607710
Ref: 409211607710
Ref: c-api/typeobj c PyNumberMethods nb_floor_divide11607772
Ref: 409611607772
Ref: c-api/typeobj c PyNumberMethods nb_true_divide11607836
Ref: 409811607836
Ref: c-api/typeobj c PyNumberMethods nb_inplace_floor_divide11607899
Ref: 409711607899
Ref: c-api/typeobj c PyNumberMethods nb_inplace_true_divide11607971
Ref: 409911607971
Ref: c-api/typeobj c PyNumberMethods nb_index11608042
Ref: 409a11608042
Ref: c-api/typeobj c PyNumberMethods nb_matrix_multiply11608098
Ref: 409b11608098
Ref: c-api/typeobj c PyNumberMethods nb_inplace_matrix_multiply11608165
Ref: 409c11608165
Node: Mapping Object Structures11608240
Ref: c-api/typeobj mapping-object-structures11608399
Ref: 40cf11608399
Ref: c-api/typeobj mapping-structs11608399
Ref: 40c111608399
Ref: c-api/typeobj c PyMappingMethods11608466
Ref: 3b6411608466
Ref: c-api/typeobj c PyMappingMethods mp_length11608635
Ref: 409d11608635
Ref: c-api/typeobj c PyMappingMethods mp_subscript11608896
Ref: 409f11608896
Ref: c-api/typeobj c PyMappingMethods mp_ass_subscript11609261
Ref: 40a011609261
Node: Sequence Object Structures11609707
Ref: c-api/typeobj sequence-object-structures11609866
Ref: 40d011609866
Ref: c-api/typeobj sequence-structs11609866
Ref: 40c011609866
Ref: c-api/typeobj c PySequenceMethods11609935
Ref: 3b6311609935
Ref: c-api/typeobj c PySequenceMethods sq_length11610083
Ref: 3d6e11610083
Ref: c-api/typeobj c PySequenceMethods sq_concat11610394
Ref: 40a211610394
Ref: c-api/typeobj c PySequenceMethods sq_repeat11610666
Ref: 40a311610666
Ref: c-api/typeobj c PySequenceMethods sq_item11610952
Ref: 40a511610952
Ref: c-api/typeobj c PySequenceMethods sq_ass_item11611664
Ref: 40a611611664
Ref: c-api/typeobj c PySequenceMethods sq_contains11612124
Ref: 40a811612124
Ref: c-api/typeobj c PySequenceMethods sq_inplace_concat11612432
Ref: 40aa11612432
Ref: c-api/typeobj c PySequenceMethods sq_inplace_repeat11612952
Ref: 40ab11612952
Node: Buffer Object Structures11613485
Ref: c-api/typeobj buffer-object-structures11613642
Ref: 40d111613642
Ref: c-api/typeobj buffer-structs11613642
Ref: 3d1311613642
Ref: c-api/typeobj c PyBufferProcs11613707
Ref: 405d11613707
Ref: c-api/typeobj c PyBufferProcs bf_getbuffer11613939
Ref: 3d7511613939
Ref: c-api/typeobj c PyBufferProcs bf_releasebuffer11615837
Ref: 3c7611615837
Node: Async Object Structures11616955
Ref: c-api/typeobj async-object-structures11617104
Ref: 40d211617104
Ref: c-api/typeobj async-structs11617104
Ref: 40be11617104
Ref: c-api/typeobj c PyAsyncMethods11617186
Ref: 3d6c11617186
Ref: c-api/typeobj c PyAsyncMethods am_await11617568
Ref: 407511617568
Ref: c-api/typeobj c PyAsyncMethods am_aiter11617916
Ref: 407711617916
Ref: c-api/typeobj c PyAsyncMethods am_anext11618269
Ref: 407811618269
Node: Slot Type typedefs11618548
Ref: c-api/typeobj id511618685
Ref: 40b011618685
Ref: c-api/typeobj slot-type-typedefs11618685
Ref: 40d311618685
Ref: c-api/typeobj c allocfunc11618738
Ref: 406811618738
Ref: c-api/typeobj c destructor11619707
Ref: 404f11619707
Ref: c-api/typeobj c vectorcallfunc11619754
Ref: 40bb11619754
Ref: c-api/typeobj c freefunc11620054
Ref: 406a11620054
Ref: c-api/typeobj c newfunc11620126
Ref: 406911620126
Ref: c-api/typeobj c initproc11620229
Ref: 406711620229
Ref: c-api/typeobj c reprfunc11620328
Ref: 405411620328
Ref: c-api/typeobj c getattrfunc11620409
Ref: 405011620409
Ref: c-api/typeobj c setattrfunc11620540
Ref: 405111620540
Ref: c-api/typeobj c getattrofunc11620760
Ref: 405a11620760
Ref: c-api/typeobj c setattrofunc11620931
Ref: 405b11620931
Ref: c-api/typeobj c descrgetfunc11621191
Ref: 406411621191
Ref: c-api/typeobj c descrsetfunc11621308
Ref: 406611621308
Ref: c-api/typeobj c hashfunc11621409
Ref: 405811621409
Ref: c-api/typeobj c richcmpfunc11621490
Ref: 406011621490
Ref: c-api/typeobj c getiterfunc11621598
Ref: 406111621598
Ref: c-api/typeobj c iternextfunc11621681
Ref: 406211621681
Ref: c-api/typeobj c lenfunc11621769
Ref: 409e11621769
Ref: c-api/typeobj c getbufferproc11621819
Ref: 40ac11621819
Ref: c-api/typeobj c releasebufferproc11621886
Ref: 40ad11621886
Ref: c-api/typeobj c unaryfunc11621953
Ref: 407611621953
Ref: c-api/typeobj c binaryfunc11622004
Ref: 407911622004
Ref: c-api/typeobj c ternaryfunc11622068
Ref: 405911622068
Ref: c-api/typeobj c ssizeargfunc11622155
Ref: 40a411622155
Ref: c-api/typeobj c ssizeobjargproc11622221
Ref: 40a711622221
Ref: c-api/typeobj c objobjproc11622284
Ref: 40a911622284
Ref: c-api/typeobj c objobjargproc11622342
Ref: 40a111622342
Node: Examples<35>11622415
Ref: c-api/typeobj examples11622565
Ref: 40d411622565
Ref: c-api/typeobj typedef-examples11622565
Ref: 404a11622565
Node: Supporting Cyclic Garbage Collection11627902
Ref: c-api/gcsupport doc11628025
Ref: 40d511628025
Ref: c-api/gcsupport supporting-cycle-detection11628025
Ref: 40c411628025
Ref: c-api/gcsupport supporting-cyclic-garbage-collection11628025
Ref: 40d611628025
Ref: c-api/gcsupport c PyObject_GC_New11629353
Ref: 2d511629353
Ref: c-api/gcsupport c PyObject_GC_NewVar11629545
Ref: 2d611629545
Ref: c-api/gcsupport c PyObject_GC_Resize11629770
Ref: 40d711629770
Ref: c-api/gcsupport c PyObject_GC_Track11630041
Ref: e4911630041
Ref: c-api/gcsupport c PyObject_GC_Del11630732
Ref: e4811630732
Ref: c-api/gcsupport c PyObject_GC_UnTrack11630901
Ref: e4a11630901
Ref: c-api/gcsupport c visitproc11631568
Ref: 40af11631568
Ref: c-api/gcsupport c traverseproc11632116
Ref: 405e11632116
Ref: c-api/gcsupport c Py_VISIT11632856
Ref: 3b4611632856
Ref: c-api/gcsupport c inquiry11633437
Ref: 405f11633437
Node: API and ABI Versioning11633914
Ref: c-api/apiabiversion doc11634038
Ref: 40d811634038
Ref: c-api/apiabiversion api-and-abi-versioning11634038
Ref: 40d911634038
Ref: c-api/apiabiversion apiabiversion11634038
Ref: 363611634038
Ref: API and ABI Versioning-Footnote-111635989
Node: 發布 Python 模組11636061
Ref: distributing/index doc11636186
Ref: 40da11636186
Ref: distributing/index distributing-index11636186
Ref: 7fb11636186
Ref: distributing/index distributing-python-modules11636186
Ref: 40db11636186
Node: Key terms11637362
Ref: distributing/index key-terms11637476
Ref: 40dc11637476
Ref: Key terms-Footnote-111639408
Ref: Key terms-Footnote-211639433
Ref: Key terms-Footnote-311639462
Ref: Key terms-Footnote-411639494
Ref: Key terms-Footnote-511639530
Ref: Key terms-Footnote-611639583
Ref: Key terms-Footnote-711639621
Ref: Key terms-Footnote-811639674
Node: Open source licensing and collaboration11639723
Ref: distributing/index open-source-licensing-and-collaboration11639866
Ref: 40dd11639866
Ref: distributing/index wheel11639866
Ref: 40de11639866
Node: Installing the tools11640884
Ref: distributing/index installing-the-tools11641057
Ref: 40df11641057
Ref: Installing the tools-Footnote-111641962
Node: Reading the Python Packaging User Guide11642060
Ref: distributing/index publishing-python-packages11642204
Ref: 40e011642204
Ref: distributing/index reading-the-python-packaging-user-guide11642204
Ref: 40e111642204
Ref: Reading the Python Packaging User Guide-Footnote-111642609
Ref: Reading the Python Packaging User Guide-Footnote-211642679
Ref: Reading the Python Packaging User Guide-Footnote-311642773
Ref: Reading the Python Packaging User Guide-Footnote-411642875
Node: How do I ?11642935
Ref: distributing/index how-do-i11643050
Ref: 40e211643050
Ref: distributing/index the-pypirc-file11643050
Ref: 40e311643050
Node: choose a name for my project?11643310
Ref: distributing/index choose-a-name-for-my-project11643435
Ref: 40e411643435
Node: create and distribute binary extensions?11644019
Ref: distributing/index create-and-distribute-binary-extensions11644144
Ref: 40e511644144
Ref: create and distribute binary extensions?-Footnote-111644567
Node: 安裝 Python 模組11644640
Ref: installing/index doc11644751
Ref: 40e611644751
Ref: installing/index installing-index11644751
Ref: 7fa11644751
Ref: installing/index installing-python-modules11644751
Ref: 40e711644751
Node: Key terms<2>11645891
Ref: installing/index key-terms11645980
Ref: 40e811645980
Ref: Key terms<2>-Footnote-111648096
Ref: Key terms<2>-Footnote-211648121
Ref: Key terms<2>-Footnote-311648150
Ref: Key terms<2>-Footnote-411648182
Ref: Key terms<2>-Footnote-511648218
Node: Basic usage11648298
Ref: installing/index basic-usage11648409
Ref: 40e911648409
Ref: Basic usage-Footnote-111650066
Ref: Basic usage-Footnote-211650103
Node: How do I ?<2>11650152
Ref: installing/index how-do-i11650277
Ref: 40ea11650277
Node: install pip in versions of Python prior to Python 3 4?11650805
Ref: installing/index install-pip-in-versions-of-python-prior-to-python-3-411650961
Ref: 40eb11650961
Ref: install pip in versions of Python prior to Python 3 4?-Footnote-111651390
Node: install packages just for the current user?11651477
Ref: installing/index install-packages-just-for-the-current-user11651677
Ref: 40ec11651677
Node: install scientific Python packages?11651941
Ref: installing/index install-scientific-python-packages11652147
Ref: 40ed11652147
Ref: install scientific Python packages?-Footnote-111652654
Ref: install scientific Python packages?-Footnote-211652700
Node: work with multiple versions of Python installed in parallel?11652746
Ref: installing/index work-with-multiple-versions-of-python-installed-in-parallel11652900
Ref: 40ee11652900
Node: Common installation issues11653877
Ref: installing/index common-installation-issues11653982
Ref: 40ef11653982
Node: Installing into the system Python on Linux11654157
Ref: installing/index installing-into-the-system-python-on-linux11654288
Ref: 40f011654288
Node: Pip not installed11654855
Ref: installing/index pip-not-installed11655023
Ref: 40f111655023
Ref: Pip not installed-Footnote-111655297
Node: Installing binary extensions11655399
Ref: installing/index installing-binary-extensions11655516
Ref: 40f211655516
Ref: Installing binary extensions-Footnote-111656410
Ref: Installing binary extensions-Footnote-211656456
Node: Python HOWTOs11656505
Ref: howto/index doc11656615
Ref: 40f311656615
Ref: howto/index python-howtos11656615
Ref: 40f411656615
Node: Python 2 的程式碼移植到Python 311657459
Ref: howto/pyporting doc11657586
Ref: 40f511657586
Ref: howto/pyporting porting-python-2-code-to-python-311657586
Ref: 40f611657586
Ref: howto/pyporting pyporting-howto11657586
Ref: c8211657586
Ref: Python 2 的程式碼移植到Python 3-Footnote-111658457
Ref: Python 2 的程式碼移植到Python 3-Footnote-211658561
Ref: Python 2 的程式碼移植到Python 3-Footnote-311658607
Node: 簡短的說明11658671
Ref: howto/pyporting the-short-explanation11658779
Ref: 40f711658779
Ref: 簡短的說明-Footnote-111659898
Ref: 簡短的說明-Footnote-211659940
Ref: 簡短的說明-Footnote-311659999
Ref: 簡短的說明-Footnote-411660048
Ref: 簡短的說明-Footnote-511660088
Ref: 簡短的說明-Footnote-611660136
Ref: 簡短的說明-Footnote-711660173
Node: 詳細的11660203
Ref: howto/pyporting details11660311
Ref: 40f811660311
Node: 向下支援Python 2 6和更舊的版本11661785
Ref: howto/pyporting drop-support-for-python-2-6-and-older11661950
Ref: 40f911661950
Ref: 向下支援Python 2 6和更舊的版本-Footnote-111663271
Ref: 向下支援Python 2 6和更舊的版本-Footnote-211663308
Node: Make sure you specify the proper version support in your setup py file11663348
Ref: howto/pyporting make-sure-you-specify-the-proper-version-support-in-your-setup-py-file11663546
Ref: 40fa11663546
Ref: Make sure you specify the proper version support in your setup py file-Footnote-111664148
Node: 有好的測試覆蓋率11664185
Ref: howto/pyporting have-good-test-coverage11664370
Ref: 40fb11664370
Ref: 有好的測試覆蓋率-Footnote-111665050
Node: 瞭解Python 2 & 3的差異11665092
Ref: howto/pyporting learn-the-differences-between-python-2-311665228
Ref: 40fc11665228
Ref: 瞭解Python 2 & 3的差異-Footnote-111665854
Ref: 瞭解Python 2 & 3的差異-Footnote-211665889
Node: 更新你的程式碼11665945
Ref: howto/pyporting update-your-code11666090
Ref: 40fd11666090
Ref: 更新你的程式碼-Footnote-111668369
Ref: 更新你的程式碼-Footnote-211668428
Ref: 更新你的程式碼-Footnote-311668477
Ref: 更新你的程式碼-Footnote-411668536
Ref: 更新你的程式碼-Footnote-511668585
Node: Division11668622
Ref: howto/pyporting division11668720
Ref: 40fe11668720
Node: Text versus binary data11669776
Ref: howto/pyporting text-versus-binary-data11669933
Ref: 40ff11669933
Ref: Text versus binary data-Footnote-111676449
Node: Use feature detection instead of version detection11676486
Ref: howto/pyporting use-feature-detection-instead-of-version-detection11676626
Ref: 410011676626
Ref: Use feature detection instead of version detection-Footnote-111678329
Node: Prevent compatibility regressions11678373
Ref: howto/pyporting prevent-compatibility-regressions11678537
Ref: 410111678537
Ref: Prevent compatibility regressions-Footnote-111679879
Ref: Prevent compatibility regressions-Footnote-211679919
Ref: Prevent compatibility regressions-Footnote-311679968
Node: Check which dependencies block your transition11680027
Ref: howto/pyporting check-which-dependencies-block-your-transition11680228
Ref: 410211680228
Ref: Check which dependencies block your transition-Footnote-111681090
Node: Update your setup py file to denote Python 3 compatibility11681138
Ref: howto/pyporting update-your-setup-py-file-to-denote-python-3-compatibility11681351
Ref: 410311681351
Node: Use continuous integration to stay compatible11681865
Ref: howto/pyporting use-continuous-integration-to-stay-compatible11682076
Ref: 410411682076
Ref: Use continuous integration to stay compatible-Footnote-111683388
Node: Consider using optional static type checking11683425
Ref: howto/pyporting consider-using-optional-static-type-checking11683569
Ref: 410511683569
Ref: Consider using optional static type checking-Footnote-111684350
Ref: Consider using optional static type checking-Footnote-211684380
Node: 遷移延伸模組到 Python 311684421
Ref: howto/cporting doc11684587
Ref: 410611684587
Ref: howto/cporting cporting-howto11684587
Ref: c7c11684587
Ref: howto/cporting porting-extension-modules-to-python-311684587
Ref: 410711684587
Ref: howto/cporting why-python-3-exists11684587
Ref: 410811684587
Ref: 遷移延伸模組到 Python 3-Footnote-111685348
Ref: 遷移延伸模組到 Python 3-Footnote-211685399
Ref: 遷移延伸模組到 Python 3-Footnote-311685456
Ref: 遷移延伸模組到 Python 3-Footnote-411685483
Node: Curses Programming with Python11685530
Ref: howto/curses doc11685680
Ref: 410911685680
Ref: howto/curses cffi11685680
Ref: 410a11685680
Ref: howto/curses curses-howto11685680
Ref: 215611685680
Ref: howto/curses curses-programming-with-python11685680
Ref: 410b11685680
Node: What is curses?11686091
Ref: howto/curses what-is-curses11686222
Ref: 410c11686222
Ref: What is curses?-Footnote-111688778
Ref: What is curses?-Footnote-211688818
Ref: What is curses?-Footnote-311688861
Node: The Python curses module11688910
Ref: howto/curses the-python-curses-module11688986
Ref: 410d11688986
Node: Starting and ending a curses application11689815
Ref: howto/curses starting-and-ending-a-curses-application11689971
Ref: 410e11689971
Node: Windows and Pads11693234
Ref: howto/curses windows-and-pads11693390
Ref: 410f11693390
Node: Displaying Text11697936
Ref: howto/curses displaying-text11698062
Ref: 411011698062
Node: Attributes and Color11701843
Ref: howto/curses attributes-and-color11701915
Ref: 411111701915
Node: User Input11706470
Ref: howto/curses user-input11706600
Ref: 411211706600
Ref: User Input-Footnote-111710404
Node: For More Information11710444
Ref: howto/curses for-more-information11710550
Ref: 411311710550
Ref: For More Information-Footnote-111712049
Ref: For More Information-Footnote-211712086
Ref: For More Information-Footnote-311712149
Ref: For More Information-Footnote-411712193
Ref: For More Information-Footnote-511712254
Ref: For More Information-Footnote-611712306
Node: 修飾器 HowTo 指南11712380
Ref: howto/descriptor doc11712518
Ref: 411411712518
Ref: howto/descriptor descriptor-howto-guide11712518
Ref: 411511712518
Node: 摘要11712860
Ref: howto/descriptor abstract11712961
Ref: 411611712961
Node: Definition and Introduction11713474
Ref: howto/descriptor definition-and-introduction11713603
Ref: 411711713603
Node: Descriptor Protocol11714954
Ref: howto/descriptor descriptor-protocol11715100
Ref: 411811715100
Node: Invoking Descriptors<2>11716411
Ref: howto/descriptor invoking-descriptors11716548
Ref: 411911716548
Ref: Invoking Descriptors<2>-Footnote-111719544
Ref: Invoking Descriptors<2>-Footnote-211719612
Ref: Invoking Descriptors<2>-Footnote-311719684
Node: Descriptor Example11719764
Ref: howto/descriptor descriptor-example11719892
Ref: 411a11719892
Node: Properties11721294
Ref: howto/descriptor properties11721420
Ref: 411b11721420
Node: Functions and Methods11724147
Ref: howto/descriptor functions-and-methods11724287
Ref: 411c11724287
Node: Static Methods and Class Methods11726486
Ref: howto/descriptor static-methods-and-class-methods11726607
Ref: 411d11726607
Node: 函式編程 HOWTO11731201
Ref: howto/functional doc11731336
Ref: 411e11731336
Ref: howto/functional functional-programming-howto11731336
Ref: 411f11731336
Node: 簡介<13>11732111
Ref: howto/functional introduction11732197
Ref: 412011732197
Node: Formal provability11736897
Ref: howto/functional formal-provability11736981
Ref: 412211736981
Node: Modularity11738897
Ref: howto/functional modularity11739019
Ref: 412311739019
Node: Ease of debugging and testing11739426
Ref: howto/functional ease-of-debugging-and-testing11739543
Ref: 412411739543
Node: Composability11740280
Ref: howto/functional composability11740378
Ref: 412511740378
Node: Iterators<2>11741103
Ref: howto/functional functional-howto-iterators11741243
Ref: 412111741243
Ref: howto/functional iterators11741243
Ref: 412611741243
Node: Data Types That Support Iterators11744606
Ref: howto/functional data-types-that-support-iterators11744688
Ref: 412711744688
Node: Generator expressions and list comprehensions11746598
Ref: howto/functional generator-expressions-and-list-comprehensions11746741
Ref: 412811746741
Node: Generators<2>11751232
Ref: howto/functional generators11751381
Ref: 412911751381
Ref: Generators<2>-Footnote-111755241
Node: Passing values into a generator11755321
Ref: howto/functional passing-values-into-a-generator11755402
Ref: 412a11755402
Ref: Passing values into a generator-Footnote-111759397
Node: Built-in functions11759446
Ref: howto/functional built-in-functions11759570
Ref: 412b11759570
Ref: Built-in functions-Footnote-111763606
Node: The itertools module11763660
Ref: howto/functional the-itertools-module11763791
Ref: 412c11763791
Node: Creating new iterators11764536
Ref: howto/functional creating-new-iterators11764653
Ref: 412d11764653
Node: Calling functions on elements11767338
Ref: howto/functional calling-functions-on-elements11767482
Ref: 412e11767482
Node: Selecting elements11768299
Ref: howto/functional selecting-elements11768443
Ref: 412f11768443
Node: Combinatoric functions11769935
Ref: howto/functional combinatoric-functions11770067
Ref: 413011770067
Node: Grouping elements11772399
Ref: howto/functional grouping-elements11772504
Ref: 413111772504
Node: The functools module11774056
Ref: howto/functional the-functools-module11774210
Ref: 413211774210
Node: The operator module11777823
Ref: howto/functional the-operator-module11777899
Ref: 413311777899
Node: Small functions and the lambda expression11778713
Ref: howto/functional small-functions-and-the-lambda-expression11778884
Ref: 413411778884
Node: Revision History and Acknowledgements11781743
Ref: howto/functional revision-history-and-acknowledgements11781907
Ref: 413511781907
Node: References<2>11782686
Ref: howto/functional references11782800
Ref: 413611782800
Node: General11782906
Ref: howto/functional general11782987
Ref: 413711782987
Node: Python-specific11783928
Ref: howto/functional python-specific11784038
Ref: 413811784038
Ref: Python-specific-Footnote-111784509
Ref: Python-specific-Footnote-211784560
Ref: Python-specific-Footnote-311784613
Node: Python documentation11784666
Ref: howto/functional python-documentation11784760
Ref: 413911784760
Ref: Python documentation-Footnote-111785153
Ref: Python documentation-Footnote-211785202
Node: 如何使用 Logging 模組11785251
Ref: howto/logging doc11785380
Ref: 413a11785380
Ref: howto/logging logging-howto11785380
Ref: 413b11785380
Node: 基礎 Logging 指南11785727
Ref: howto/logging basic-logging-tutorial11785846
Ref: 413c11785846
Ref: howto/logging logging-basic-tutorial11785846
Ref: b7711785846
Node: 什麼時候使用 logging11786563
Ref: howto/logging when-to-use-logging11786672
Ref: 413d11786672
Node: A simple example11790571
Ref: howto/logging a-simple-example11790706
Ref: 413e11790706
Ref: howto/logging howto-minimal-example11790706
Ref: 413f11790706
Node: Logging to a file11791493
Ref: howto/logging logging-to-a-file11791631
Ref: 414011791631
Node: Logging from multiple modules11794144
Ref: howto/logging logging-from-multiple-modules11794287
Ref: 414111794287
Node: Logging variable data11795493
Ref: howto/logging logging-variable-data11795660
Ref: 414211795660
Node: Changing the format of displayed messages11796479
Ref: howto/logging changing-the-format-of-displayed-messages11796653
Ref: 414311796653
Node: Displaying the date/time in messages11797649
Ref: howto/logging displaying-the-date-time-in-messages11797812
Ref: 414411797812
Ref: Displaying the date/time in messages-Footnote-111798864
Node: Next Steps11798913
Ref: howto/logging next-steps11799026
Ref: 414511799026
Node: Advanced Logging Tutorial11799984
Ref: howto/logging advanced-logging-tutorial11800129
Ref: 414611800129
Ref: howto/logging logging-advanced-tutorial11800129
Ref: b7811800129
Node: Logging Flow11803520
Ref: howto/logging logging-flow11803610
Ref: 414711803610
Node: Loggers11803785
Ref: howto/logging loggers11803892
Ref: 414811803892
Node: Handlers11808173
Ref: howto/logging handler-basic11808278
Ref: 414911808278
Ref: howto/logging handlers11808278
Ref: 414a11808278
Node: Formatters11810346
Ref: howto/logging formatters11810463
Ref: 414c11810463
Ref: howto/logging logging logging Formatter __init__11810913
Ref: 414d11810913
Node: Configuring Logging11812601
Ref: howto/logging configuring-logging11812754
Ref: 414e11812754
Node: What happens if no configuration is provided11819317
Ref: howto/logging what-happens-if-no-configuration-is-provided11819493
Ref: 414f11819493
Node: Configuring Logging for a Library11820920
Ref: howto/logging configuring-logging-for-a-library11821068
Ref: 415011821068
Ref: howto/logging library-config11821068
Ref: 20fe11821068
Node: Logging Levels<2>11823500
Ref: howto/logging logging-levels11823639
Ref: 415111823639
Node: Custom Levels11826500
Ref: howto/logging custom-levels11826567
Ref: 20d111826567
Ref: howto/logging id111826567
Ref: 415211826567
Node: Useful Handlers11827282
Ref: howto/logging id211827428
Ref: 415311827428
Ref: howto/logging useful-handlers11827428
Ref: 414b11827428
Node: Exceptions raised during logging11831432
Ref: howto/logging exceptions-raised-during-logging11831596
Ref: 415411831596
Ref: howto/logging logging-exceptions11831596
Ref: 415511831596
Node: Using arbitrary objects as messages11832754
Ref: howto/logging arbitrary-object-messages11832915
Ref: 20c211832915
Ref: howto/logging using-arbitrary-objects-as-messages11832915
Ref: 415611832915
Node: Optimization11833529
Ref: howto/logging optimization11833649
Ref: 415711833649
Node: Logging Cookbook11837204
Ref: howto/logging-cookbook doc11837342
Ref: 415811837342
Ref: howto/logging-cookbook id111837342
Ref: 415911837342
Ref: howto/logging-cookbook logging-cookbook11837342
Ref: b7911837342
Node: Using logging in multiple modules11838966
Ref: howto/logging-cookbook using-logging-in-multiple-modules11839090
Ref: 415a11839090
Node: Logging from multiple threads11842664
Ref: howto/logging-cookbook logging-from-multiple-threads11842829
Ref: 415b11842829
Node: Multiple handlers and formatters11844576
Ref: howto/logging-cookbook multiple-handlers-and-formatters11844740
Ref: 415c11844740
Node: Logging to multiple destinations11846903
Ref: howto/logging-cookbook logging-to-multiple-destinations11847066
Ref: 415d11847066
Ref: howto/logging-cookbook multiple-destinations11847066
Ref: 415e11847066
Node: Configuration server example11849917
Ref: howto/logging-cookbook configuration-server-example11850080
Ref: 415f11850080
Node: Dealing with handlers that block11851642
Ref: howto/logging-cookbook dealing-with-handlers-that-block11851826
Ref: 416011851826
Node: Sending and receiving logging events across a network11855474
Ref: howto/logging-cookbook network-logging11855682
Ref: 416111855682
Ref: howto/logging-cookbook sending-and-receiving-logging-events-across-a-network11855682
Ref: 416211855682
Node: Adding contextual information to your logging output11861150
Ref: howto/logging-cookbook adding-contextual-information-to-your-logging-output11861374
Ref: 416311861374
Ref: howto/logging-cookbook context-info11861374
Ref: 20c511861374
Node: Using LoggerAdapters to impart contextual information11862456
Ref: howto/logging-cookbook using-loggeradapters-to-impart-contextual-information11862653
Ref: 416411862653
Node: Using objects other than dicts to pass contextual information11865801
Ref: howto/logging-cookbook using-objects-other-than-dicts-to-pass-contextual-information11865952
Ref: 416511865952
Node: Using Filters to impart contextual information11866411
Ref: howto/logging-cookbook filters-contextual11866608
Ref: 20ba11866608
Ref: howto/logging-cookbook using-filters-to-impart-contextual-information11866608
Ref: 416611866608
Node: Logging to a single file from multiple processes11870413
Ref: howto/logging-cookbook logging-to-a-single-file-from-multiple-processes11870603
Ref: 416711870603
Ref: howto/logging-cookbook multiple-processes11870603
Ref: 416811870603
Node: Using concurrent futures ProcessPoolExecutor11881033
Ref: howto/logging-cookbook using-concurrent-futures-processpoolexecutor11881162
Ref: 416911881162
Node: Using file rotation11882168
Ref: howto/logging-cookbook using-file-rotation11882342
Ref: 416a11882342
Node: Use of alternative formatting styles11884240
Ref: howto/logging-cookbook format-styles11884387
Ref: 416b11884387
Ref: howto/logging-cookbook use-of-alternative-formatting-styles11884387
Ref: 416c11884387
Node: Customizing LogRecord11891539
Ref: howto/logging-cookbook custom-logrecord11891710
Ref: 416d11891710
Ref: howto/logging-cookbook customizing-logrecord11891710
Ref: 416e11891710
Node: Subclassing QueueHandler - a ZeroMQ example11895623
Ref: howto/logging-cookbook subclassing-queuehandler-a-zeromq-example11895802
Ref: 416f11895802
Ref: howto/logging-cookbook zeromq-handlers11895802
Ref: 417011895802
Node: Subclassing QueueListener - a ZeroMQ example11897138
Ref: howto/logging-cookbook subclassing-queuelistener-a-zeromq-example11897337
Ref: 417111897337
Node: An example dictionary-based configuration11898457
Ref: howto/logging-cookbook an-example-dictionary-based-configuration11898675
Ref: 417211898675
Ref: An example dictionary-based configuration-Footnote-111900712
Ref: An example dictionary-based configuration-Footnote-211900798
Node: Using a rotator and namer to customize log rotation processing11900884
Ref: howto/logging-cookbook cookbook-rotator-namer11901098
Ref: 210a11901098
Ref: howto/logging-cookbook using-a-rotator-and-namer-to-customize-log-rotation-processing11901098
Ref: 417311901098
Node: A more elaborate multiprocessing example11901975
Ref: howto/logging-cookbook a-more-elaborate-multiprocessing-example11902201
Ref: 417411902201
Node: Inserting a BOM into messages sent to a SysLogHandler11911829
Ref: howto/logging-cookbook inserting-a-bom-into-messages-sent-to-a-sysloghandler11912024
Ref: 417511912024
Ref: Inserting a BOM into messages sent to a SysLogHandler-Footnote-111914191
Ref: Inserting a BOM into messages sent to a SysLogHandler-Footnote-211914240
Ref: Inserting a BOM into messages sent to a SysLogHandler-Footnote-311914299
Ref: Inserting a BOM into messages sent to a SysLogHandler-Footnote-411914348
Node: Implementing structured logging11914397
Ref: howto/logging-cookbook implementing-structured-logging11914588
Ref: 417611914588
Node: Customizing handlers with dictConfig11917322
Ref: howto/logging-cookbook custom-handlers11917522
Ref: 417711917522
Ref: howto/logging-cookbook customizing-handlers-with-dictconfig11917522
Ref: 417811917522
Node: Using particular formatting styles throughout your application11922715
Ref: howto/logging-cookbook formatting-styles11922919
Ref: 20b111922919
Ref: howto/logging-cookbook using-particular-formatting-styles-throughout-your-application11922919
Ref: 417911922919
Node: Using LogRecord factories11924920
Ref: howto/logging-cookbook using-logrecord-factories11925081
Ref: 417a11925081
Node: Using custom message objects11926057
Ref: howto/logging-cookbook using-custom-message-objects11926218
Ref: 417b11926218
Node: Configuring filters with dictConfig11928924
Ref: howto/logging-cookbook configuring-filters-with-dictconfig11929123
Ref: 417c11929123
Ref: howto/logging-cookbook filters-dictconfig11929123
Ref: 417d11929123
Node: Customized exception formatting11932088
Ref: howto/logging-cookbook custom-format-exception11932250
Ref: 417e11932250
Ref: howto/logging-cookbook customized-exception-formatting11932250
Ref: 417f11932250
Node: Speaking logging messages11934318
Ref: howto/logging-cookbook speaking-logging-messages11934505
Ref: 418011934505
Ref: howto/logging-cookbook spoken-messages11934505
Ref: 418111934505
Node: Buffering logging messages and outputting them conditionally11936665
Ref: howto/logging-cookbook buffered-logging11936869
Ref: 418211936869
Ref: howto/logging-cookbook buffering-logging-messages-and-outputting-them-conditionally11936869
Ref: 418311936869
Node: Formatting times using UTC GMT via configuration11942446
Ref: howto/logging-cookbook formatting-times-using-utc-gmt-via-configuration11942670
Ref: 418411942670
Ref: howto/logging-cookbook utc-formatting11942670
Ref: 418511942670
Node: Using a context manager for selective logging11944572
Ref: howto/logging-cookbook context-manager11944770
Ref: 418611944770
Ref: howto/logging-cookbook using-a-context-manager-for-selective-logging11944770
Ref: 418711944770
Node: A CLI application starter template11949352
Ref: howto/logging-cookbook a-cli-application-starter-template11949522
Ref: 418811949522
Ref: howto/logging-cookbook starter-template11949522
Ref: 418911949522
Node: A Qt GUI for logging11955505
Ref: howto/logging-cookbook a-qt-gui-for-logging11955621
Ref: 418a11955621
Ref: howto/logging-cookbook qt-gui11955621
Ref: 418b11955621
Ref: A Qt GUI for logging-Footnote-111964988
Ref: A Qt GUI for logging-Footnote-211965015
Ref: A Qt GUI for logging-Footnote-311965057
Node: 如何使用正規表達式11965097
Ref: howto/regex doc11965232
Ref: 418c11965232
Ref: howto/regex regex-howto11965232
Ref: 175511965232
Ref: howto/regex regular-expression-howto11965232
Ref: 418d11965232
Node: 簡介<14>11965669
Ref: howto/regex introduction11965767
Ref: 418e11965767
Node: Simple Patterns11967271
Ref: howto/regex simple-patterns11967403
Ref: 418f11967403
Node: Matching Characters11967898
Ref: howto/regex matching-characters11967994
Ref: 419011967994
Node: Repeating Things11972625
Ref: howto/regex repeating-things11972721
Ref: 419111972721
Node: Using Regular Expressions11977659
Ref: howto/regex using-regular-expressions11977799
Ref: 419211977799
Node: Compiling Regular Expressions11978292
Ref: howto/regex compiling-regular-expressions11978412
Ref: 419311978412
Node: The Backslash Plague11979629
Ref: howto/regex id111979776
Ref: 419411979776
Ref: howto/regex the-backslash-plague11979776
Ref: 419511979776
Node: Performing Matches11982662
Ref: howto/regex performing-matches11982805
Ref: 419611982805
Ref: Performing Matches-Footnote-111988706
Node: Module-Level Functions<2>11988778
Ref: howto/regex module-level-functions11988918
Ref: 419711988918
Node: Compilation Flags11990118
Ref: howto/regex compilation-flags11990231
Ref: 419811990231
Node: More Pattern Power11997411
Ref: howto/regex more-pattern-power11997553
Ref: 419a11997553
Node: More Metacharacters11997918
Ref: howto/regex id211998009
Ref: 419b11998009
Ref: howto/regex more-metacharacters11998009
Ref: 419911998009
Node: Grouping12002658
Ref: howto/regex grouping12002788
Ref: 419c12002788
Node: Non-capturing and Named Groups12006273
Ref: howto/regex non-capturing-and-named-groups12006404
Ref: 419d12006404
Node: Lookahead Assertions12011540
Ref: howto/regex lookahead-assertions12011654
Ref: 419e12011654
Node: Modifying Strings12015321
Ref: howto/regex modifying-strings12015453
Ref: 419f12015453
Node: Splitting Strings12016423
Ref: howto/regex splitting-strings12016521
Ref: 41a012016521
Node: Search and Replace12018845
Ref: howto/regex search-and-replace12018943
Ref: 41a112018943
Node: Common Problems12023437
Ref: howto/regex common-problems12023559
Ref: 41a212023559
Node: Use String Methods12023997
Ref: howto/regex use-string-methods12024095
Ref: 41a312024095
Node: match versus search12025812
Ref: howto/regex match-versus-search12025943
Ref: 41a412025943
Node: Greedy versus Non-Greedy12027571
Ref: howto/regex greedy-versus-non-greedy12027700
Ref: 41a512027700
Node: Using re VERBOSE12029623
Ref: howto/regex using-re-verbose12029724
Ref: 41a612029724
Node: Feedback12031251
Ref: howto/regex feedback12031347
Ref: 41a712031347
Node: Socket Programming HOWTO12032130
Ref: howto/sockets doc12032261
Ref: 41a812032261
Ref: howto/sockets socket-howto12032261
Ref: 26a112032261
Ref: howto/sockets socket-programming-howto12032261
Ref: 41a912032261
Node: Sockets12032859
Ref: howto/sockets sockets12032953
Ref: 41aa12032953
Node: History12034089
Ref: howto/sockets history12034140
Ref: 41ab12034140
Node: Creating a Socket12034715
Ref: howto/sockets creating-a-socket12034832
Ref: 41ac12034832
Node: IPC12038052
Ref: howto/sockets ipc12038109
Ref: 41ad12038109
Node: Using a Socket12038550
Ref: howto/sockets using-a-socket12038673
Ref: 41ae12038673
Node: Binary Data12044796
Ref: howto/sockets binary-data12044858
Ref: 41af12044858
Node: Disconnecting12045914
Ref: howto/sockets disconnecting12046040
Ref: 41b012046040
Node: When Sockets Die12047501
Ref: howto/sockets when-sockets-die12047567
Ref: 41b112047567
Node: Non-blocking Sockets12048446
Ref: howto/sockets non-blocking-sockets12048549
Ref: 41b212048549
Node: 如何排序12052363
Ref: howto/sorting doc12052480
Ref: 41b312052480
Ref: howto/sorting sorting-how-to12052480
Ref: 41b412052480
Ref: howto/sorting sortinghowto12052480
Ref: 160612052480
Node: 排序 基本12053075
Ref: howto/sorting sorting-basics12053159
Ref: 41b512053159
Node: Key Functions12053955
Ref: howto/sorting key-functions12054073
Ref: 41b612054073
Node: Operator Module Functions12055743
Ref: howto/sorting operator-module-functions12055863
Ref: 41b712055863
Node: 升冪與降冪12056922
Ref: howto/sorting ascending-and-descending12057061
Ref: 41b812057061
Node: Sort Stability and Complex Sorts12057575
Ref: howto/sorting sort-stability-and-complex-sorts12057731
Ref: 41b912057731
Ref: Sort Stability and Complex Sorts-Footnote-112059366
Ref: Sort Stability and Complex Sorts-Footnote-212059432
Node: The Old Way Using Decorate-Sort-Undecorate12059478
Ref: howto/sorting the-old-way-using-decorate-sort-undecorate12059654
Ref: 41ba12059654
Ref: The Old Way Using Decorate-Sort-Undecorate-Footnote-112061343
Node: The Old Way Using the cmp Parameter12061403
Ref: howto/sorting the-old-way-using-the-cmp-parameter12061559
Ref: 41bb12061559
Node: Odd and Ends12064035
Ref: howto/sorting odd-and-ends12064140
Ref: 41bc12064140
Node: Unicode HOWTO12065860
Ref: howto/unicode doc12065995
Ref: 41bd12065995
Ref: howto/unicode id112065995
Ref: 41be12065995
Ref: howto/unicode unicode-howto12065995
Ref: c4112065995
Node: Introduction to Unicode12066395
Ref: howto/unicode introduction-to-unicode12066501
Ref: 41bf12066501
Node: Definitions12066635
Ref: howto/unicode definitions12066724
Ref: 41c012066724
Node: Encodings12069741
Ref: howto/unicode encodings12069852
Ref: 41c112069852
Node: References<3>12073527
Ref: howto/unicode references12073618
Ref: 41c212073618
Ref: References<3>-Footnote-112074491
Ref: References<3>-Footnote-212074522
Ref: References<3>-Footnote-312074562
Ref: References<3>-Footnote-412074614
Ref: References<3>-Footnote-512074660
Ref: References<3>-Footnote-612074834
Ref: References<3>-Footnote-712074891
Node: Python's Unicode Support12074935
Ref: howto/unicode python-s-unicode-support12075082
Ref: 41c312075082
Node: The String Type12075451
Ref: howto/unicode the-string-type12075555
Ref: 41c412075555
Node: Converting to Bytes12078667
Ref: howto/unicode converting-to-bytes12078818
Ref: 41c512078818
Node: Unicode Literals in Python Source Code12080664
Ref: howto/unicode unicode-literals-in-python-source-code12080818
Ref: 41c612080818
Ref: Unicode Literals in Python Source Code-Footnote-112082925
Node: Unicode Properties12082974
Ref: howto/unicode unicode-properties12083126
Ref: 41c712083126
Ref: Unicode Properties-Footnote-112084865
Node: Comparing Strings12084934
Ref: howto/unicode comparing-strings12085075
Ref: 41c812085075
Node: Unicode Regular Expressions12087922
Ref: howto/unicode unicode-regular-expressions12088058
Ref: 41c912088058
Node: References<4>12089195
Ref: howto/unicode id212089305
Ref: 41ca12089305
Ref: References<4>-Footnote-112090093
Ref: References<4>-Footnote-212090188
Ref: References<4>-Footnote-312090240
Node: Reading and Writing Unicode Data12090309
Ref: howto/unicode reading-and-writing-unicode-data12090453
Ref: 41cb12090453
Node: Unicode filenames12094160
Ref: howto/unicode unicode-filenames12094294
Ref: 41cc12094294
Node: Tips for Writing Unicode-aware Programs12096732
Ref: howto/unicode tips-for-writing-unicode-aware-programs12096888
Ref: 41cd12096888
Node: Converting Between File Encodings12098253
Ref: howto/unicode converting-between-file-encodings12098399
Ref: 41ce12098399
Node: Files in an Unknown Encoding12099168
Ref: howto/unicode files-in-an-unknown-encoding12099314
Ref: 41cf12099314
Node: References<5>12100217
Ref: howto/unicode id312100347
Ref: 41d012100347
Ref: References<5>-Footnote-112100957
Ref: References<5>-Footnote-212101030
Ref: References<5>-Footnote-312101135
Node: Acknowledgements<10>12101203
Ref: howto/unicode acknowledgements12101314
Ref: 41d112101314
Node: 如何使用urllib套件取得網路資源12101840
Ref: howto/urllib2 doc12101978
Ref: 41d212101978
Ref: howto/urllib2 howto-fetch-internet-resources-using-the-urllib-package12101978
Ref: 41d312101978
Ref: howto/urllib2 urllib-howto12101978
Ref: 2cb312101978
Ref: 如何使用urllib套件取得網路資源-Footnote-112102447
Ref: 如何使用urllib套件取得網路資源-Footnote-212102502
Node: 簡介<15>12102578
Ref: howto/urllib2 introduction12102694
Ref: 41d412102694
Ref: 簡介<15>-Footnote-112104073
Ref: 簡介<15>-Footnote-212104146
Node: 從URL取得資源12104195
Ref: howto/urllib2 fetching-urls12104339
Ref: 41d512104339
Node: Data12106581
Ref: howto/urllib2 data12106656
Ref: 41d612106656
Ref: Data-Footnote-112109305
Node: Headers12109374
Ref: howto/urllib2 headers12109449
Ref: 41d712109449
Ref: Headers-Footnote-112110963
Ref: Headers-Footnote-212110995
Ref: Headers-Footnote-312111209
Ref: Headers-Footnote-412111333
Node: Handling Exceptions12111455
Ref: howto/urllib2 handling-exceptions12111604
Ref: 41d912111604
Node: URLError12112089
Ref: howto/urllib2 urlerror12112171
Ref: 41da12112171
Node: HTTPError12112725
Ref: howto/urllib2 httperror12112830
Ref: 41db12112830
Ref: HTTPError-Footnote-112113704
Node: Error Codes12113753
Ref: howto/urllib2 error-codes12113810
Ref: 41dc12113810
Ref: Error Codes-Footnote-112118563
Node: Wrapping it Up12118612
Ref: howto/urllib2 wrapping-it-up12118700
Ref: 41dd12118700
Node: Number 112118921
Ref: howto/urllib2 number-112118997
Ref: 41de12118997
Node: Number 212119621
Ref: howto/urllib2 number-212119697
Ref: 41df12119697
Node: info and geturl12120231
Ref: howto/urllib2 info-and-geturl12120382
Ref: 41d812120382
Ref: info and geturl-Footnote-112121268
Node: Openers and Handlers12121305
Ref: howto/urllib2 openers-and-handlers12121457
Ref: 41e012121457
Node: Basic Authentication12123103
Ref: howto/urllib2 id512123247
Ref: 41e112123247
Ref: Basic Authentication-Footnote-112126652
Node: Proxies12126725
Ref: howto/urllib2 proxies12126867
Ref: 41e212126867
Ref: Proxies-Footnote-112127895
Ref: Proxies-Footnote-212128202
Ref: Proxies-Footnote-312128275
Node: Sockets and Layers12128402
Ref: howto/urllib2 sockets-and-layers12128533
Ref: 41e312128533
Node: 註解<3>12129554
Ref: howto/urllib2 footnotes12129669
Ref: 41e412129669
Node: Argparse 教學12129751
Ref: howto/argparse doc12129897
Ref: 41e512129897
Ref: howto/argparse argparse-tutorial12129897
Ref: 41e612129897
Ref: howto/argparse id112129971
Ref: 202f12129971
Node: 概念12130550
Ref: howto/argparse concepts12130629
Ref: 41e712130629
Node: 基本用法12132403
Ref: howto/argparse the-basics12132509
Ref: 41e812132509
Node: 介紹位置參數12133741
Ref: howto/argparse introducing-positional-arguments12133859
Ref: 41e912133859
Node: 介紹選項參數12137014
Ref: howto/argparse introducing-optional-arguments12137153
Ref: 41ea12137153
Node: Short options12140118
Ref: howto/argparse short-options12140186
Ref: 41eb12140186
Node: 現在結合位置與選項參數12140939
Ref: howto/argparse combining-positional-and-optional-arguments12141090
Ref: 41ec12141090
Node: Getting a little more advanced12149341
Ref: howto/argparse getting-a-little-more-advanced12149480
Ref: 41ed12149480
Node: Conflicting options12151492
Ref: howto/argparse conflicting-options12151578
Ref: 41ee12151578
Node: 結論12154731
Ref: howto/argparse conclusion12154828
Ref: 41ef12154828
Node: ipaddress模組介紹12155038
Ref: howto/ipaddress doc12155164
Ref: 41f012155164
Ref: howto/ipaddress an-introduction-to-the-ipaddress-module12155164
Ref: 41f112155164
Ref: howto/ipaddress ipaddress-howto12155164
Ref: 2f0912155164
Node: Creating Address/Network/Interface objects12155867
Ref: howto/ipaddress creating-address-network-interface-objects12156020
Ref: 41f212156020
Node: A Note on IP Versions12156447
Ref: howto/ipaddress a-note-on-ip-versions12156573
Ref: 41f312156573
Node: IP Host Addresses12157356
Ref: howto/ipaddress ip-host-addresses12157508
Ref: 41f412157508
Node: Defining Networks12158691
Ref: howto/ipaddress defining-networks12158837
Ref: 41f512158837
Node: Host Interfaces12161191
Ref: howto/ipaddress host-interfaces12161311
Ref: 41f612161311
Node: Inspecting Address/Network/Interface Objects12162312
Ref: howto/ipaddress inspecting-address-network-interface-objects12162504
Ref: 41f712162504
Node: Networks as lists of Addresses12164850
Ref: howto/ipaddress networks-as-lists-of-addresses12165014
Ref: 41f812165014
Node: Comparisons<4>12165813
Ref: howto/ipaddress comparisons12165970
Ref: 41f912165970
Node: Using IP Addresses with other modules12166329
Ref: howto/ipaddress using-ip-addresses-with-other-modules12166504
Ref: 41fa12166504
Node: Getting more detail when instance creation fails12166935
Ref: howto/ipaddress getting-more-detail-when-instance-creation-fails12167087
Ref: 41fb12167087
Node: Argument Clinic How-To12169145
Ref: howto/clinic doc12169303
Ref: 41fc12169303
Ref: howto/clinic argument-clinic-how-to12169303
Ref: 41fd12169303
Node: The Goals Of Argument Clinic12170336
Ref: howto/clinic the-goals-of-argument-clinic12170456
Ref: 41fe12170456
Node: Basic Concepts And Usage12172814
Ref: howto/clinic basic-concepts-and-usage12172973
Ref: 41ff12172973
Node: Converting Your First Function12175404
Ref: howto/clinic converting-your-first-function12175550
Ref: 420012175550
Node: Advanced Topics12191658
Ref: howto/clinic advanced-topics12191771
Ref: 420212191771
Node: Symbolic default values12192737
Ref: howto/clinic symbolic-default-values12192888
Ref: 420312192888
Node: Renaming the C functions and variables generated by Argument Clinic12193518
Ref: howto/clinic renaming-the-c-functions-and-variables-generated-by-argument-clinic12193722
Ref: 420412193722
Node: Converting functions using PyArg_UnpackTuple12195385
Ref: howto/clinic converting-functions-using-pyarg-unpacktuple12195581
Ref: 420512195581
Node: Optional Groups12196126
Ref: howto/clinic optional-groups12196323
Ref: 420612196323
Node: Using real Argument Clinic converters instead of "legacy converters"12200377
Ref: howto/clinic using-real-argument-clinic-converters-instead-of-legacy-converters12200539
Ref: 420712200539
Ref: Using real Argument Clinic converters instead of "legacy converters"-Footnote-112209453
Node: Py_buffer12209502
Ref: howto/clinic py-buffer12209668
Ref: 420812209668
Node: Advanced converters12209984
Ref: howto/clinic advanced-converters12210106
Ref: 420912210106
Node: Parameter default values12211807
Ref: howto/clinic default-values12211942
Ref: 420112211942
Ref: howto/clinic parameter-default-values12211942
Ref: 420a12211942
Node: The NULL default value12212471
Ref: howto/clinic the-null-default-value12212626
Ref: 420b12212626
Node: Expressions specified as default values12213100
Ref: howto/clinic expressions-specified-as-default-values12213255
Ref: 420c12213255
Node: Using a return converter12215646
Ref: howto/clinic using-a-return-converter12215805
Ref: 420d12215805
Node: Cloning existing functions12218446
Ref: howto/clinic cloning-existing-functions12218585
Ref: 420e12218585
Node: Calling Python code12219905
Ref: howto/clinic calling-python-code12220044
Ref: 420f12220044
Node: Using a "self converter"12220959
Ref: howto/clinic using-a-self-converter12221098
Ref: 421012221098
Node: Writing a custom converter12222832
Ref: howto/clinic writing-a-custom-converter12222985
Ref: 421112222985
Node: Writing a custom return converter12226678
Ref: howto/clinic writing-a-custom-return-converter12226829
Ref: 421212226829
Node: METH_O and METH_NOARGS12227408
Ref: howto/clinic meth-o-and-meth-noargs12227561
Ref: 421312227561
Node: tp_new and tp_init functions12228132
Ref: howto/clinic tp-new-and-tp-init-functions12228292
Ref: 421412228292
Node: Changing and redirecting Clinic's output12229237
Ref: howto/clinic changing-and-redirecting-clinic-s-output12229391
Ref: 421512229391
Node: The #ifdef trick12240645
Ref: howto/clinic the-ifdef-trick12240808
Ref: 421612240808
Node: Using Argument Clinic in Python files12243582
Ref: howto/clinic using-argument-clinic-in-python-files12243696
Ref: 421712243696
Node: Instrumenting CPython with DTrace and SystemTap12244392
Ref: howto/instrumentation doc12244520
Ref: 421812244520
Ref: howto/instrumentation instrumentation12244520
Ref: 51112244520
Ref: howto/instrumentation instrumenting-cpython-with-dtrace-and-systemtap12244520
Ref: 421912244520
Node: Enabling the static markers12245710
Ref: howto/instrumentation enabling-the-static-markers12245850
Ref: 421a12245850
Node: Static DTrace probes12249993
Ref: howto/instrumentation static-dtrace-probes12250166
Ref: 421b12250166
Node: Static SystemTap markers12252603
Ref: howto/instrumentation static-systemtap-markers12252773
Ref: 421c12252773
Node: Available static markers12254818
Ref: howto/instrumentation available-static-markers12254985
Ref: 421d12254985
Node: SystemTap Tapsets12257522
Ref: howto/instrumentation systemtap-tapsets12257677
Ref: 421e12257677
Node: Examples<36>12259293
Ref: howto/instrumentation examples12259415
Ref: 421f12259415
Node: Python 常見問題12260738
Ref: faq/index doc12260836
Ref: 422012260836
Ref: faq/index faq-index12260836
Ref: 131d12260836
Ref: faq/index python-frequently-asked-questions12260836
Ref: 422112260836
Node: 常見Python問答集12261189
Ref: faq/general doc12261302
Ref: 422212261302
Ref: faq/general general-python-faq12261302
Ref: 422312261302
Node: 常見資訊12261405
Ref: faq/general general-information12261505
Ref: 422412261505
Node: 什麼是Python?12262382
Ref: faq/general what-is-python12262487
Ref: 422512262487
Ref: 什麼是Python?-Footnote-112263430
Node: 什麼是Python軟體基金會?12263482
Ref: faq/general what-is-the-python-software-foundation12263639
Ref: 422612263639
Node: 當使用Python時有任何版權限制嗎?12264222
Ref: faq/general are-there-copyright-restrictions-on-the-use-of-python12264393
Ref: 422712264393
Ref: 當使用Python時有任何版權限制嗎?-Footnote-112265244
Node: 為什麼Python被創造出來12265291
Ref: faq/general why-was-python-created-in-the-first-place12265461
Ref: 422812265461
Node: 什麼是Python擅長的事情12267746
Ref: faq/general what-is-python-good-for12267923
Ref: 422912267923
Ref: 什麼是Python擅長的事情-Footnote-112268795
Node: How does the Python version numbering scheme work?12268820
Ref: faq/general how-does-the-python-version-numbering-scheme-work12269000
Ref: 422a12269000
Ref: How does the Python version numbering scheme work?-Footnote-112270845
Node: 我如何拿到Python的原始碼12270894
Ref: faq/general how-do-i-obtain-a-copy-of-the-python-source12271077
Ref: 422b12271077
Ref: 我如何拿到Python的原始碼-Footnote-112271830
Node: 如何取得Python的相關文件12271873
Ref: faq/general how-do-i-get-documentation-on-python12272057
Ref: 422c12272057
Ref: 如何取得Python的相關文件-Footnote-112272603
Node: 我從來沒寫過程式，有沒有Python的教學12272634
Ref: faq/general i-ve-never-programmed-before-is-there-a-python-tutorial12272839
Ref: 422d12272839
Ref: 我從來沒寫過程式，有沒有Python的教學-Footnote-112273217
Node: 有沒有新手的群組或是郵件群組討論Python12273269
Ref: faq/general is-there-a-newsgroup-or-mailing-list-devoted-to-python12273484
Ref: 422e12273484
Ref: 有沒有新手的群組或是郵件群組討論Python-Footnote-112274345
Ref: 有沒有新手的群組或是郵件群組討論Python-Footnote-212274406
Node: How do I get a beta test version of Python?12274476
Ref: faq/general how-do-i-get-a-beta-test-version-of-python12274691
Ref: 422f12274691
Ref: How do I get a beta test version of Python?-Footnote-112275230
Node: How do I submit bug reports and patches for Python?12275267
Ref: faq/general how-do-i-submit-bug-reports-and-patches-for-python12275495
Ref: 423012275495
Ref: How do I submit bug reports and patches for Python?-Footnote-112276206
Ref: How do I submit bug reports and patches for Python?-Footnote-212276263
Node: Are there any published articles about Python that I can reference?12276300
Ref: faq/general are-there-any-published-articles-about-python-that-i-can-reference12276512
Ref: 423112276512
Node: 有沒有關於Python的書12277012
Ref: faq/general are-there-any-books-on-python12277221
Ref: 423212277221
Node: www python org 這個非營利組織位於哪裡12277558
Ref: faq/general where-in-the-world-is-www-python-org-located12277727
Ref: 423312277727
Ref: www python org 這個非營利組織位於哪裡-Footnote-112278008
Node: 為什麼要取名為Python12278036
Ref: faq/general why-is-it-called-python12278240
Ref: 423412278240
Ref: 為什麼要取名為Python-Footnote-112278645
Node: 我需要喜歡蒙提·派森的飛行馬戲團這個節目嗎12278696
Ref: faq/general do-i-have-to-like-monty-python-s-flying-circus12278843
Ref: 423512278843
Node: Python在真實世界12279001
Ref: faq/general python-in-the-real-world12279101
Ref: 423612279101
Node: Python穩定性如何12279476
Ref: faq/general how-stable-is-python12279588
Ref: 423712279588
Ref: Python穩定性如何-Footnote-112280619
Ref: Python穩定性如何-Footnote-212280668
Ref: Python穩定性如何-Footnote-312280710
Node: 有多少人使用Python12280760
Ref: faq/general how-many-people-are-using-python12280935
Ref: 423812280935
Node: 有沒有任何重要的案子使用Python完成開發12281417
Ref: faq/general have-any-significant-projects-been-done-in-python12281625
Ref: 423912281625
Ref: 有沒有任何重要的案子使用Python完成開發-Footnote-112282331
Ref: 有沒有任何重要的案子使用Python完成開發-Footnote-212282383
Ref: 有沒有任何重要的案子使用Python完成開發-Footnote-312282411
Ref: 有沒有任何重要的案子使用Python完成開發-Footnote-412282439
Node: 對於程式開發者Python對於未來有什麼期待12282470
Ref: faq/general what-new-developments-are-expected-for-python-in-the-future12282713
Ref: 423a12282713
Ref: 對於程式開發者Python對於未來有什麼期待-Footnote-112283270
Node: Is it reasonable to propose incompatible changes to Python?12283331
Ref: faq/general is-it-reasonable-to-propose-incompatible-changes-to-python12283589
Ref: 423b12283589
Ref: Is it reasonable to propose incompatible changes to Python?-Footnote-112284393
Node: Python對於入門的程式設計者而言是否為好的程式語言12284442
Ref: faq/general is-python-a-good-language-for-beginning-programmers12284637
Ref: 423c12284637
Ref: Python對於入門的程式設計者而言是否為好的程式語言-Footnote-112288511
Ref: Python對於入門的程式設計者而言是否為好的程式語言-Footnote-212288562
Node: 程式開發常見問答集12288624
Ref: faq/programming doc12288768
Ref: 423d12288768
Ref: faq/programming programming-faq12288768
Ref: 423e12288768
Node: 常見問題12289013
Ref: faq/programming general-questions12289111
Ref: 423f12289111
Node: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？12289547
Ref: faq/programming is-there-a-source-code-level-debugger-with-breakpoints-single-stepping-etc12289758
Ref: 424012289758
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-112291192
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-212291236
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-312291289
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-412291334
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-512291383
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-612291422
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-712291452
Ref: 是否有可以使用在程式碼階段 具有中斷點 步驟執行等功能的除錯器？-Footnote-812291509
Node: Are there tools to help find bugs or perform static analysis?12291552
Ref: faq/programming are-there-tools-to-help-find-bugs-or-perform-static-analysis12291831
Ref: 424112291831
Ref: Are there tools to help find bugs or perform static analysis?-Footnote-112292207
Ref: Are there tools to help find bugs or perform static analysis?-Footnote-212292239
Ref: Are there tools to help find bugs or perform static analysis?-Footnote-312292281
Ref: Are there tools to help find bugs or perform static analysis?-Footnote-412292311
Ref: Are there tools to help find bugs or perform static analysis?-Footnote-512292343
Node: How can I create a stand-alone binary from a Python script?12292384
Ref: faq/programming how-can-i-create-a-stand-alone-binary-from-a-python-script12292635
Ref: 424212292635
Ref: How can I create a stand-alone binary from a Python script?-Footnote-112294276
Ref: How can I create a stand-alone binary from a Python script?-Footnote-212294307
Ref: How can I create a stand-alone binary from a Python script?-Footnote-312294356
Node: Are there coding standards or a style guide for Python programs?12294408
Ref: faq/programming are-there-coding-standards-or-a-style-guide-for-python-programs12294589
Ref: 424312294589
Ref: Are there coding standards or a style guide for Python programs?-Footnote-112294863
Node: Core Language12294912
Ref: faq/programming core-language12295038
Ref: 424412295038
Node: 為什麼當變數有值時我得到錯誤訊息 UnboundLocalError12296375
Ref: faq/programming why-am-i-getting-an-unboundlocalerror-when-the-variable-has-a-value12296555
Ref: 424512296555
Node: Python 的區域變數和全域變數有什麼規則？12298402
Ref: faq/programming what-are-the-rules-for-local-and-global-variables-in-python12298673
Ref: 424612298673
Node: Why do lambdas defined in a loop with different values all return the same result?12299548
Ref: faq/programming why-do-lambdas-defined-in-a-loop-with-different-values-all-return-the-same-result12299800
Ref: 424712299800
Node: How do I share global variables across modules?12301709
Ref: faq/programming how-do-i-share-global-variables-across-modules12301965
Ref: 424812301965
Node: What are the "best practices" for using import in a module?12302768
Ref: faq/programming what-are-the-best-practices-for-using-import-in-a-module12302988
Ref: 424912302988
Node: Why are default values shared between objects?12305731
Ref: faq/programming why-are-default-values-shared-between-objects12305979
Ref: 424a12305979
Node: How can I pass optional or keyword parameters from one function to another?12308363
Ref: faq/programming how-can-i-pass-optional-or-keyword-parameters-from-one-function-to-another12308608
Ref: 424b12308608
Node: What is the difference between arguments and parameters?12309195
Ref: faq/programming faq-argument-vs-parameter12309441
Ref: 424c12309441
Ref: faq/programming what-is-the-difference-between-arguments-and-parameters12309441
Ref: 424d12309441
Node: Why did changing list 'y' also change list 'x'?12310131
Ref: faq/programming why-did-changing-list-y-also-change-list-x12310370
Ref: 424e12310370
Node: How do I write a function with output parameters call by reference ?12313772
Ref: faq/programming how-do-i-write-a-function-with-output-parameters-call-by-reference12314005
Ref: 424f12314005
Node: How do you make a higher order function in Python?12316410
Ref: faq/programming how-do-you-make-a-higher-order-function-in-python12316630
Ref: 425012316630
Node: How do I copy an object in Python?12318204
Ref: faq/programming how-do-i-copy-an-object-in-python12318410
Ref: 425112318410
Node: How can I find the methods or attributes of an object?12318817
Ref: faq/programming how-can-i-find-the-methods-or-attributes-of-an-object12319020
Ref: 425212319020
Node: How can my code discover the name of an object?12319334
Ref: faq/programming how-can-my-code-discover-the-name-of-an-object12319550
Ref: 425312319550
Node: What's up with the comma operator's precedence?12321166
Ref: faq/programming what-s-up-with-the-comma-operator-s-precedence12321380
Ref: 425412321380
Node: Is there an equivalent of C's "? " ternary operator?12321938
Ref: faq/programming is-there-an-equivalent-of-c-s-ternary-operator12322161
Ref: 425512322161
Node: Is it possible to write obfuscated one-liners in Python?12322752
Ref: faq/programming is-it-possible-to-write-obfuscated-one-liners-in-python12322991
Ref: 425612322991
Node: What does the slash / in the parameter list of a function mean?12324470
Ref: faq/programming faq-positional-only-arguments12324648
Ref: 15f812324648
Ref: faq/programming what-does-the-slash-in-the-parameter-list-of-a-function-mean12324648
Ref: 425712324648
Node: Numbers and strings12325748
Ref: faq/programming numbers-and-strings12325876
Ref: 425812325876
Node: How do I specify hexadecimal and octal integers?12326538
Ref: faq/programming how-do-i-specify-hexadecimal-and-octal-integers12326680
Ref: 425912326680
Node: Why does -22 // 10 return -3?12327313
Ref: faq/programming why-does-22-10-return-312327502
Ref: 425a12327502
Node: How do I convert a string to a number?12328263
Ref: faq/programming how-do-i-convert-a-string-to-a-number12328442
Ref: 425b12328442
Node: How do I convert a number to a string?12329754
Ref: faq/programming how-do-i-convert-a-number-to-a-string12329938
Ref: 425c12329938
Node: How do I modify a string in place?12330489
Ref: faq/programming how-do-i-modify-a-string-in-place12330682
Ref: 425d12330682
Node: How do I use strings to call functions/methods?12331538
Ref: faq/programming how-do-i-use-strings-to-call-functions-methods12331776
Ref: 425e12331776
Node: Is there an equivalent to Perl's chomp for removing trailing newlines from strings?12333401
Ref: faq/programming is-there-an-equivalent-to-perl-s-chomp-for-removing-trailing-newlines-from-strings12333643
Ref: 425f12333643
Node: Is there a scanf or sscanf equivalent?12334402
Ref: faq/programming is-there-a-scanf-or-sscanf-equivalent12334663
Ref: 426012334663
Node: What does 'UnicodeDecodeError' or 'UnicodeEncodeError' error mean?12335310
Ref: faq/programming what-does-unicodedecodeerror-or-unicodeencodeerror-error-mean12335479
Ref: 426112335479
Node: Performance<4>12335675
Ref: faq/programming performance12335812
Ref: 426212335812
Node: My program is too slow How do I speed it up?12336029
Ref: faq/programming my-program-is-too-slow-how-do-i-speed-it-up12336201
Ref: 426312336201
Ref: My program is too slow How do I speed it up?-Footnote-112339076
Ref: My program is too slow How do I speed it up?-Footnote-212339102
Node: What is the most efficient way to concatenate many strings together?12339167
Ref: faq/programming efficient-string-concatenation12339339
Ref: 426412339339
Ref: faq/programming what-is-the-most-efficient-way-to-concatenate-many-strings-together12339339
Ref: 426512339339
Node: Sequences Tuples/Lists12340309
Ref: faq/programming sequences-tuples-lists12340434
Ref: 426612340434
Node: How do I convert between tuples and lists?12341172
Ref: faq/programming how-do-i-convert-between-tuples-and-lists12341306
Ref: 426712341306
Node: What's a negative index?12342153
Ref: faq/programming what-s-a-negative-index12342346
Ref: 426812342346
Node: How do I iterate over a sequence in reverse order?12342926
Ref: faq/programming how-do-i-iterate-over-a-sequence-in-reverse-order12343118
Ref: 426912343118
Node: How do you remove duplicates from a list?12343467
Ref: faq/programming how-do-you-remove-duplicates-from-a-list12343679
Ref: 426a12343679
Node: How do you remove multiple items from a list12344507
Ref: faq/programming how-do-you-remove-multiple-items-from-a-list12344704
Ref: 426b12344704
Node: How do you make an array in Python?12345252
Ref: faq/programming how-do-you-make-an-array-in-python12345448
Ref: 426c12345448
Node: How do I create a multidimensional list?12346432
Ref: faq/programming faq-multidimensional-list12346633
Ref: 163612346633
Ref: faq/programming how-do-i-create-a-multidimensional-list12346633
Ref: 426d12346633
Ref: How do I create a multidimensional list?-Footnote-112347855
Node: How do I apply a method to a sequence of objects?12347885
Ref: faq/programming how-do-i-apply-a-method-to-a-sequence-of-objects12348126
Ref: 426e12348126
Node: Why does a_tuple[i] += ['item'] raise an exception when the addition works?12348320
Ref: faq/programming faq-augmented-assignment-tuple-error12348598
Ref: 148112348598
Ref: faq/programming why-does-a-tuple-i-item-raise-an-exception-when-the-addition-works12348598
Ref: 426f12348598
Node: I want to do a complicated sort can you do a Schwartzian Transform in Python?12351818
Ref: faq/programming i-want-to-do-a-complicated-sort-can-you-do-a-schwartzian-transform-in-python12352099
Ref: 427012352099
Node: How can I sort one list by values from another list?12352580
Ref: faq/programming how-can-i-sort-one-list-by-values-from-another-list12352777
Ref: 427112352777
Node: Objects12353987
Ref: faq/programming objects12354108
Ref: 427212354108
Node: What is a class?12355117
Ref: faq/programming what-is-a-class12355203
Ref: 427312355203
Node: What is a method?12355929
Ref: faq/programming what-is-a-method12356037
Ref: 427412356037
Node: What is self?12356346
Ref: faq/programming what-is-self12356521
Ref: 427512356521
Node: How do I check if an object is an instance of a given class or of a subclass of it?12356963
Ref: faq/programming how-do-i-check-if-an-object-is-an-instance-of-a-given-class-or-of-a-subclass-of-it12357140
Ref: 427712357140
Node: What is delegation?12358631
Ref: faq/programming what-is-delegation12358881
Ref: 427812358881
Node: How do I call a method defined in a base class from a derived class that overrides it?12360731
Ref: faq/programming how-do-i-call-a-method-defined-in-a-base-class-from-a-derived-class-that-overrides-it12360968
Ref: 427912360968
Node: How can I organize my code to make it easier to change the base class?12361653
Ref: faq/programming how-can-i-organize-my-code-to-make-it-easier-to-change-the-base-class12361930
Ref: 427a12361930
Node: How do I create static class data and static class methods?12362605
Ref: faq/programming how-do-i-create-static-class-data-and-static-class-methods12362849
Ref: 427b12362849
Node: How can I overload constructors or methods in Python?12364414
Ref: faq/programming how-can-i-overload-constructors-or-methods-in-python12364653
Ref: 427c12364653
Node: I try to use __spam and I get an error about _SomeClassName__spam12365560
Ref: faq/programming i-try-to-use-spam-and-i-get-an-error-about-someclassname-spam12365810
Ref: 427d12365810
Node: My class defines __del__ but it is not called when I delete the object12366603
Ref: faq/programming my-class-defines-del-but-it-is-not-called-when-i-delete-the-object12366854
Ref: 427e12366854
Node: How do I get a list of all instances of a given class?12368828
Ref: faq/programming how-do-i-get-a-list-of-all-instances-of-a-given-class12369064
Ref: 427f12369064
Node: Why does the result of id appear to be not unique?12369405
Ref: faq/programming why-does-the-result-of-id-appear-to-be-not-unique12369562
Ref: 428012369562
Node: Modules<2>12370454
Ref: faq/programming modules12370544
Ref: 428112370544
Node: How do I create a pyc file?12371074
Ref: faq/programming how-do-i-create-a-pyc-file12371195
Ref: 428212371195
Ref: How do I create a pyc file?-Footnote-112373777
Node: How do I find the current module name?12373826
Ref: faq/programming how-do-i-find-the-current-module-name12374011
Ref: 428312374011
Node: How can I have modules that mutually import each other?12374569
Ref: faq/programming how-can-i-have-modules-that-mutually-import-each-other12374783
Ref: 428412374783
Node: __import__ 'x y z' returns <module 'x'>; how do I get z?12376669
Ref: faq/programming import-x-y-z-returns-module-x-how-do-i-get-z12376939
Ref: 428512376939
Node: When I edit an imported module and reimport it the changes don't show up Why does this happen?12377229
Ref: faq/programming when-i-edit-an-imported-module-and-reimport-it-the-changes-don-t-show-up-why-does-this-happen12377435
Ref: 428612377435
Node: Design and History FAQ12378878
Ref: faq/design doc12379040
Ref: 428712379040
Ref: faq/design design-and-history-faq12379040
Ref: 428812379040
Node: Why does Python use indentation for grouping of statements?12380984
Ref: faq/design why-does-python-use-indentation-for-grouping-of-statements12381178
Ref: 428912381178
Node: Why am I getting strange results with simple arithmetic operations?12382880
Ref: faq/design why-am-i-getting-strange-results-with-simple-arithmetic-operations12383120
Ref: 428a12383120
Node: 為何浮點數運算如此不精確?12383297
Ref: faq/design why-are-floating-point-calculations-so-inaccurate12383511
Ref: 428b12383511
Node: 為何Python字串為不可變動12385012
Ref: faq/design why-are-python-strings-immutable12385226
Ref: 428c12385226
Node: Why must 'self' be used explicitly in method definitions and calls?12385801
Ref: faq/design why-must-self-be-used-explicitly-in-method-definitions-and-calls12386025
Ref: 428d12386025
Ref: faq/design why-self12386025
Ref: 427612386025
Node: Why can't I use an assignment in an expression?12388491
Ref: faq/design id212388786
Ref: 428e12388786
Ref: faq/design why-can-t-i-use-an-assignment-in-an-expression12388786
Ref: 127d12388786
Ref: Why can't I use an assignment in an expression?-Footnote-112389158
Node: Why does Python use methods for some functionality e g list index but functions for other e g len list ?12389207
Ref: faq/design why-does-python-use-methods-for-some-functionality-e-g-list-index-but-functions-for-other-e-g-len-list12389497
Ref: 428f12389497
Node: Why is join a string method instead of a list or tuple method?12390836
Ref: faq/design why-is-join-a-string-method-instead-of-a-list-or-tuple-method12391103
Ref: 429012391103
Node: How fast are exceptions?12392906
Ref: faq/design how-fast-are-exceptions12393122
Ref: 429112393122
Node: Why isn't there a switch or case statement in Python?12393935
Ref: faq/design why-isn-t-there-a-switch-or-case-statement-in-python12394193
Ref: 429212394193
Ref: Why isn't there a switch or case statement in Python?-Footnote-112395566
Node: Can't you emulate threads in the interpreter instead of relying on an OS-specific thread implementation?12395615
Ref: faq/design can-t-you-emulate-threads-in-the-interpreter-instead-of-relying-on-an-os-specific-thread-implementation12395894
Ref: 429312395894
Ref: Can't you emulate threads in the interpreter instead of relying on an OS-specific thread implementation?-Footnote-112396541
Node: 為何lambda表示式不能包含在敘述內12396597
Ref: faq/design why-can-t-lambda-expressions-contain-statements12396891
Ref: 429412396891
Node: Python可以被編譯成機器語言或C語言或其他種語言嗎?12397735
Ref: faq/design can-python-be-compiled-to-machine-code-c-or-some-other-language12397953
Ref: 429512397953
Ref: Python可以被編譯成機器語言或C語言或其他種語言嗎?-Footnote-112398374
Ref: Python可以被編譯成機器語言或C語言或其他種語言嗎?-Footnote-212398401
Ref: Python可以被編譯成機器語言或C語言或其他種語言嗎?-Footnote-312398432
Node: Python如何管理記憶體?12398467
Ref: faq/design how-does-python-manage-memory12398696
Ref: 429612398696
Ref: Python如何管理記憶體?-Footnote-112400354
Ref: Python如何管理記憶體?-Footnote-212400384
Node: 為何CPython不使用更多傳統的垃圾回收機制?12400412
Ref: faq/design why-doesn-t-cpython-use-a-more-traditional-garbage-collection-scheme12400635
Ref: 429712400635
Node: 當CPython結束時，為何所有的記憶體不會被釋放?12401507
Ref: faq/design why-isn-t-all-memory-freed-when-cpython-exits12401751
Ref: 429812401751
Node: Why are there separate tuple and list data types?12402458
Ref: faq/design why-are-there-separate-tuple-and-list-data-types12402683
Ref: 429912402683
Node: How are lists implemented in CPython?12403917
Ref: faq/design how-are-lists-implemented-in-cpython12404124
Ref: 429a12404124
Node: How are dictionaries implemented in CPython?12404865
Ref: faq/design how-are-dictionaries-implemented-in-cpython12405061
Ref: 429b12405061
Node: Why must dictionary keys be immutable?12406004
Ref: faq/design why-must-dictionary-keys-be-immutable12406210
Ref: 429c12406210
Node: 為何list sort 不是回傳排序過的串列?12410412
Ref: faq/design why-doesn-t-list-sort-return-the-sorted-list12410633
Ref: 429d12410633
Node: How do you specify and enforce an interface spec in Python?12411465
Ref: faq/design how-do-you-specify-and-enforce-an-interface-spec-in-python12411671
Ref: 429e12411671
Node: 為何沒有goto語法?12413996
Ref: faq/design why-is-there-no-goto12414208
Ref: 429f12414208
Node: Why can't raw strings r-strings end with a backslash?12415268
Ref: faq/design why-can-t-raw-strings-r-strings-end-with-a-backslash12415490
Ref: 42a012415490
Node: Why doesn't Python have a "with" statement for attribute assignments?12416591
Ref: faq/design why-doesn-t-python-have-a-with-statement-for-attribute-assignments12416852
Ref: 42a112416852
Node: Why are colons required for the if/while/def/class statements?12419029
Ref: faq/design why-are-colons-required-for-the-if-while-def-class-statements12419297
Ref: 42a212419297
Node: Why does Python allow commas at the end of lists and tuples?12420042
Ref: faq/design why-does-python-allow-commas-at-the-end-of-lists-and-tuples12420232
Ref: 42a312420232
Node: 函式庫和擴充功能的常見問題12421314
Ref: faq/library doc12421472
Ref: 42a412421472
Ref: faq/library library-and-extension-faq12421472
Ref: 42a512421472
Node: 常見函式問題12421715
Ref: faq/library general-library-questions12421836
Ref: 42a612421836
Node: How do I find a module or application to perform task X?12422328
Ref: faq/library how-do-i-find-a-module-or-application-to-perform-task-x12422509
Ref: 42a712422509
Ref: How do I find a module or application to perform task X?-Footnote-112423093
Ref: How do I find a module or application to perform task X?-Footnote-212423118
Node: 哪裡可以找到math py socket py regex py 等 原始檔案12423149
Ref: faq/library where-is-the-math-py-socket-py-regex-py-etc-source-file12423380
Ref: 42a812423380
Node: 我如何使Python script 執行在Unix ?12424147
Ref: faq/library how-do-i-make-a-python-script-executable-on-unix12424367
Ref: 42a912424367
Node: Is there a curses/termcap package for Python?12425782
Ref: faq/library is-there-a-curses-termcap-package-for-python12425988
Ref: 42aa12425988
Ref: Is there a curses/termcap package for Python?-Footnote-112426827
Ref: Is there a curses/termcap package for Python?-Footnote-212426886
Node: Is there an equivalent to C's onexit in Python?12426935
Ref: faq/library is-there-an-equivalent-to-c-s-onexit-in-python12427134
Ref: 42ab12427134
Node: Why don't my signal handlers work?12427354
Ref: faq/library why-don-t-my-signal-handlers-work12427499
Ref: 42ac12427499
Node: 一般性的工作12427823
Ref: faq/library common-tasks12427960
Ref: 42ad12427960
Node: 我如何測試Python程式12428147
Ref: faq/library how-do-i-test-a-python-program-or-component12428285
Ref: 42ae12428285
Node: How do I create documentation from doc strings?12430163
Ref: faq/library how-do-i-create-documentation-from-doc-strings12430351
Ref: 42af12430351
Ref: How do I create documentation from doc strings?-Footnote-112430727
Ref: How do I create documentation from doc strings?-Footnote-212430766
Node: How do I get a single keypress at a time?12430796
Ref: faq/library how-do-i-get-a-single-keypress-at-a-time12430948
Ref: 42b012430948
Node: Threads12431194
Ref: faq/library threads12431329
Ref: 42b112431329
Node: How do I program using threads?12431655
Ref: faq/library how-do-i-program-using-threads12431774
Ref: 42b212431774
Node: None of my threads seem to run why?12432207
Ref: faq/library none-of-my-threads-seem-to-run-why12432392
Ref: 42b312432392
Node: How do I parcel out work among a bunch of worker threads?12433941
Ref: faq/library how-do-i-parcel-out-work-among-a-bunch-of-worker-threads12434147
Ref: 42b412434147
Node: What kinds of global value mutation are thread-safe?12436747
Ref: faq/library what-kinds-of-global-value-mutation-are-thread-safe12436966
Ref: 42b512436966
Node: Can't we get rid of the Global Interpreter Lock?12438468
Ref: faq/library can-t-we-get-rid-of-the-global-interpreter-lock12438621
Ref: 42b612438621
Ref: Can't we get rid of the Global Interpreter Lock?-Footnote-112441308
Node: Input and Output12441368
Ref: faq/library input-and-output12441513
Ref: 42b712441513
Node: How do I delete a file? And other file questions12442141
Ref: faq/library how-do-i-delete-a-file-and-other-file-questions12442272
Ref: 42b812442272
Node: How do I copy a file?12443524
Ref: faq/library how-do-i-copy-a-file12443699
Ref: 42b912443699
Node: How do I read or write binary data?12443910
Ref: faq/library how-do-i-read-or-write-binary-data12444103
Ref: 42ba12444103
Node: I can't seem to use os read on a pipe created with os popen ; why?12445294
Ref: faq/library i-can-t-seem-to-use-os-read-on-a-pipe-created-with-os-popen-why12445504
Ref: 42bb12445504
Node: How do I access the serial RS232 port?12446025
Ref: faq/library how-do-i-access-the-serial-rs232-port12446260
Ref: 42bc12446260
Node: Why doesn't closing sys stdout stdin stderr really close it?12446572
Ref: faq/library why-doesn-t-closing-sys-stdout-stdin-stderr-really-close-it12446732
Ref: 42bd12446732
Node: Network/Internet Programming12447959
Ref: faq/library network-internet-programming12448106
Ref: 42be12448106
Node: What WWW tools are there for Python?12448563
Ref: faq/library what-www-tools-are-there-for-python12448722
Ref: 42bf12448722
Node: How can I mimic CGI form submission METHOD=POST ?12449306
Ref: faq/library how-can-i-mimic-cgi-form-submission-method-post12449528
Ref: 42c012449528
Node: What module should I use to help with generating HTML?12450618
Ref: faq/library what-module-should-i-use-to-help-with-generating-html12450844
Ref: 42c112450844
Ref: What module should I use to help with generating HTML?-Footnote-112451089
Node: How do I send mail from a Python script?12451141
Ref: faq/library how-do-i-send-mail-from-a-python-script12451376
Ref: 42c212451376
Node: How do I avoid blocking in the connect method of a socket?12452717
Ref: faq/library how-do-i-avoid-blocking-in-the-connect-method-of-a-socket12452889
Ref: 42c312452889
Ref: How do I avoid blocking in the connect method of a socket?-Footnote-112454143
Node: Databases12454183
Ref: faq/library databases12454338
Ref: 42c412454338
Node: Are there any interfaces to database packages in Python?12454499
Ref: faq/library are-there-any-interfaces-to-database-packages-in-python12454660
Ref: 42c512454660
Ref: Are there any interfaces to database packages in Python?-Footnote-112455168
Node: How do you implement persistent objects in Python?12455225
Ref: faq/library how-do-you-implement-persistent-objects-in-python12455386
Ref: 42c612455386
Node: Mathematics and Numerics12455787
Ref: faq/library mathematics-and-numerics12455905
Ref: 42c712455905
Node: How do I generate random numbers in Python?12456028
Ref: faq/library how-do-i-generate-random-numbers-in-python12456132
Ref: 42c812456132
Node: Extending/Embedding FAQ12457081
Ref: faq/extending doc12457248
Ref: 42c912457248
Ref: faq/extending extending-embedding-faq12457248
Ref: 42ca12457248
Node: Can I create my own functions in C?12458726
Ref: faq/extending can-i-create-my-own-functions-in-c12458867
Ref: 42cb12458867
Node: Can I create my own functions in C++?12459227
Ref: faq/extending id212459423
Ref: 42cc12459423
Node: Writing C is hard; are there any alternatives?12459810
Ref: faq/extending c-wrapper-software12460024
Ref: 42cd12460024
Ref: faq/extending writing-c-is-hard-are-there-any-alternatives12460024
Ref: 42ce12460024
Ref: Writing C is hard; are there any alternatives?-Footnote-112460793
Ref: Writing C is hard; are there any alternatives?-Footnote-212460819
Ref: Writing C is hard; are there any alternatives?-Footnote-312460886
Ref: Writing C is hard; are there any alternatives?-Footnote-412460914
Ref: Writing C is hard; are there any alternatives?-Footnote-512460972
Ref: Writing C is hard; are there any alternatives?-Footnote-612461008
Ref: Writing C is hard; are there any alternatives?-Footnote-712461064
Node: How can I execute arbitrary Python statements from C?12461103
Ref: faq/extending how-can-i-execute-arbitrary-python-statements-from-c12461337
Ref: 42cf12461337
Node: How can I evaluate an arbitrary Python expression from C?12461882
Ref: faq/extending how-can-i-evaluate-an-arbitrary-python-expression-from-c12462117
Ref: 42d012462117
Node: How do I extract C values from a Python object?12462432
Ref: faq/extending how-do-i-extract-c-values-from-a-python-object12462679
Ref: 42d112462679
Node: How do I use Py_BuildValue to create a tuple of arbitrary length?12463918
Ref: faq/extending how-do-i-use-py-buildvalue-to-create-a-tuple-of-arbitrary-length12464148
Ref: 42d212464148
Node: How do I call an object's method from C?12464355
Ref: faq/extending how-do-i-call-an-object-s-method-from-c12464623
Ref: 42d312464623
Node: How do I catch the output from PyErr_Print or anything that prints to stdout/stderr ?12465832
Ref: faq/extending how-do-i-catch-the-output-from-pyerr-print-or-anything-that-prints-to-stdout-stderr12466085
Ref: 42d412466085
Node: How do I access a module written in Python from C?12467298
Ref: faq/extending how-do-i-access-a-module-written-in-python-from-c12467557
Ref: 42d512467557
Node: How do I interface to C++ objects from Python?12468389
Ref: faq/extending how-do-i-interface-to-c-objects-from-python12468625
Ref: 42d612468625
Node: I added a module using the Setup file and the make fails; why?12469193
Ref: faq/extending i-added-a-module-using-the-setup-file-and-the-make-fails-why12469407
Ref: 42d712469407
Node: How do I debug an extension?12469757
Ref: faq/extending how-do-i-debug-an-extension12470009
Ref: 42d812470009
Node: I want to compile a Python module on my Linux system but some files are missing Why?12470560
Ref: faq/extending i-want-to-compile-a-python-module-on-my-linux-system-but-some-files-are-missing-why12470804
Ref: 42d912470804
Node: How do I tell "incomplete input" from "invalid input"?12471288
Ref: faq/extending how-do-i-tell-incomplete-input-from-invalid-input12471572
Ref: 42da12471572
Node: How do I find undefined g++ symbols __builtin_new or __pure_virtual?12477668
Ref: faq/extending how-do-i-find-undefined-g-symbols-builtin-new-or-pure-virtual12477978
Ref: 42db12477978
Node: Can I create an object class with some methods implemented in C and others in Python e g through inheritance ?12478366
Ref: faq/extending can-i-create-an-object-class-with-some-methods-implemented-in-c-and-others-in-python-e-g-through-inheritance12478613
Ref: 42dc12478613
Node: FAQ：在 Windows 使用 Python12479166
Ref: faq/windows doc12479333
Ref: 42dd12479333
Ref: faq/windows python-on-windows-faq12479333
Ref: 42de12479333
Ref: faq/windows windows-faq12479333
Ref: 42df12479333
Node: 在 Windows 作業系統裡我想執行 Python 程式，要怎麼做？12479892
Ref: faq/windows faq-run-program-under-windows12480080
Ref: 42e012480080
Ref: faq/windows how-do-i-run-a-python-program-under-windows12480080
Ref: 42e112480080
Node: How do I make Python scripts executable?12483659
Ref: faq/windows how-do-i-make-python-scripts-executable12483904
Ref: 42e212483904
Node: Why does Python sometimes take so long to start?12484466
Ref: faq/windows why-does-python-sometimes-take-so-long-to-start12484689
Ref: 42e312484689
Node: How do I make an executable from a Python script?12485568
Ref: faq/windows how-do-i-make-an-executable-from-a-python-script12485785
Ref: 42e412485785
Ref: How do I make an executable from a Python script?-Footnote-112486070
Ref: How do I make an executable from a Python script?-Footnote-212486122
Node: Is a * pyd file the same as a DLL?12486153
Ref: faq/windows is-a-pyd-file-the-same-as-a-dll12486372
Ref: 42e512486372
Node: How can I embed Python into a Windows application?12487365
Ref: faq/windows how-can-i-embed-python-into-a-windows-application12487599
Ref: 42e612487599
Node: How do I keep editors from inserting tabs into my Python source?12492117
Ref: faq/windows how-do-i-keep-editors-from-inserting-tabs-into-my-python-source12492364
Ref: 42e712492364
Ref: How do I keep editors from inserting tabs into my Python source?-Footnote-112493225
Node: How do I check for a keypress without blocking?12493274
Ref: faq/windows how-do-i-check-for-a-keypress-without-blocking12493462
Ref: 42e812493462
Node: 圖形化使用者界面常見問答集12493811
Ref: faq/gui doc12494013
Ref: 42e912494013
Ref: faq/gui graphic-user-interface-faq12494013
Ref: 42ea12494013
Node: 常見圖形化使用者界面 GUI 問題12494331
Ref: faq/gui general-gui-questions12494513
Ref: 42eb12494513
Node: What platform-independent GUI toolkits exist for Python?12494602
Ref: faq/gui what-platform-independent-gui-toolkits-exist-for-python12494846
Ref: 42ec12494846
Node: Tkinter12495305
Ref: faq/gui tkinter12495423
Ref: 42ed12495423
Ref: Tkinter-Footnote-112495892
Ref: Tkinter-Footnote-212495934
Node: wxWidgets12495961
Ref: faq/gui wxwidgets12496090
Ref: 42ef12496090
Ref: wxWidgets-Footnote-112496952
Node: Qt12496985
Ref: faq/gui qt12497111
Ref: 42ee12497111
Ref: Qt-Footnote-112497587
Ref: Qt-Footnote-212497646
Ref: Qt-Footnote-312497680
Ref: Qt-Footnote-412497744
Ref: Qt-Footnote-512497810
Node: Gtk+12497847
Ref: faq/gui gtk12497968
Ref: 42f012497968
Ref: Gtk+-Footnote-112498296
Ref: Gtk+-Footnote-212498346
Ref: Gtk+-Footnote-312498399
Node: Kivy12498427
Ref: faq/gui kivy12498550
Ref: 42f112498550
Ref: Kivy-Footnote-112498910
Node: FLTK12498936
Ref: faq/gui fltk12499077
Ref: 42f212499077
Ref: FLTK-Footnote-112499292
Ref: FLTK-Footnote-212499320
Node: 開放圖形庫 OpenGL12499358
Ref: faq/gui opengl12499486
Ref: 42f312499486
Ref: 開放圖形庫 OpenGL-Footnote-112499623
Node: What platform-specific GUI toolkits exist for Python?12499663
Ref: faq/gui what-platform-specific-gui-toolkits-exist-for-python12499883
Ref: 42f412499883
Ref: What platform-specific GUI toolkits exist for Python?-Footnote-112500337
Node: Tkinter questions12500378
Ref: faq/gui tkinter-questions12500533
Ref: 42f512500533
Node: How do I freeze Tkinter applications?12500797
Ref: faq/gui how-do-i-freeze-tkinter-applications12500948
Ref: 42f612500948
Node: Can I have Tk events handled while waiting for I/O?12501895
Ref: faq/gui can-i-have-tk-events-handled-while-waiting-for-i-o12502103
Ref: 42f712502103
Node: I can't get key bindings to work in Tkinter why?12502578
Ref: faq/gui i-can-t-get-key-bindings-to-work-in-tkinter-why12502740
Ref: 42f812502740
Node: 為什麼Python被安裝在我的機器上?常見問答集12503288
Ref: faq/installed doc12503450
Ref: 42f912503450
Ref: faq/installed why-is-python-installed-on-my-computer-faq12503450
Ref: 42fa12503450
Node: 什麼是Python?<2>12503697
Ref: faq/installed what-is-python12503863
Ref: 42fb12503863
Node: 為什麼Python被安裝在我的機器上?12504379
Ref: faq/installed why-is-python-installed-on-my-machine12504585
Ref: 42fc12504585
Node: 我能夠自行刪除Python嗎?12505505
Ref: faq/installed can-i-delete-python12505683
Ref: 42fd12505683
Node: Glossary12506414
Ref: glossary doc12506523
Ref: 42fe12506523
Ref: glossary glossary12506523
Ref: 120412506523
Ref: glossary id112506523
Ref: 42ff12506523
Ref: glossary term-012506548
Ref: 121d12506548
Ref: glossary term-112506711
Ref: 121e12506711
Ref: glossary term-2to312507105
Ref: 102712507105
Ref: glossary term-abstract-base-class12507524
Ref: b3812507524
Ref: glossary term-annotation12508361
Ref: 430112508361
Ref: glossary term-argument12508934
Ref: 152812508934
Ref: glossary term-asynchronous-context-manager12510366
Ref: 64612510366
Ref: glossary term-asynchronous-generator12510600
Ref: 150812510600
Ref: glossary term-asynchronous-generator-iterator12511325
Ref: 363412511325
Ref: glossary term-asynchronous-iterable12512075
Ref: 64512512075
Ref: glossary term-asynchronous-iterator12512298
Ref: 64a12512298
Ref: glossary term-attribute12512714
Ref: 430412512714
Ref: glossary term-awaitable12512914
Ref: 51e12512914
Ref: glossary term-bdfl12513111
Ref: 430512513111
Ref: glossary term-binary-file12513208
Ref: 1caa12513208
Ref: glossary term-bytes-like-object12513654
Ref: 5ed12513654
Ref: glossary term-bytecode12514631
Ref: 61912514631
Ref: glossary term-callback12515357
Ref: 25a712515357
Ref: glossary term-class12515475
Ref: 160712515475
Ref: glossary term-class-variable12515640
Ref: 430612515640
Ref: glossary term-coercion12515786
Ref: 430712515786
Ref: glossary term-complex-number12516425
Ref: 430812516425
Ref: glossary term-context-manager12517196
Ref: 56d12517196
Ref: glossary term-context-variable12517397
Ref: 430912517397
Ref: glossary term-contiguous12517855
Ref: 16ba12517855
Ref: glossary term-coroutine12518398
Ref: 1a712518398
Ref: glossary term-coroutine-function12518721
Ref: 64412518721
Ref: glossary term-cpython12519035
Ref: 143b12519035
Ref: glossary term-decorator12519284
Ref: 28412519284
Ref: glossary term-descriptor12519997
Ref: 160b12519997
Ref: glossary term-dictionary12520796
Ref: 430a12520796
Ref: glossary term-dictionary-comprehension12521002
Ref: 430b12521002
Ref: glossary term-dictionary-view12521348
Ref: 194a12521348
Ref: glossary term-docstring12521794
Ref: 15ba12521794
Ref: glossary term-duck-typing12522185
Ref: 430012522185
Ref: glossary term-eafp12522886
Ref: 1f5112522886
Ref: glossary term-expression12523332
Ref: 362812523332
Ref: glossary term-extension-module12523846
Ref: 430d12523846
Ref: glossary term-f-string12523974
Ref: 15c12523974
Ref: glossary term-file-object12524165
Ref: b4712524165
Ref: glossary term-file-like-object12524942
Ref: 1c6f12524942
Ref: glossary term-finder12525004
Ref: 14bf12525004
Ref: glossary term-floor-division12525395
Ref: 122312525395
Ref: glossary term-function12525771
Ref: 152712525771
Ref: glossary term-function-annotation12526079
Ref: 126212526079
Ref: glossary term-future12526677
Ref: 68812526677
Ref: glossary term-garbage-collection12527155
Ref: ecd12527155
Ref: glossary term-generator12527475
Ref: 9a712527475
Ref: glossary term-generator-iterator12527991
Ref: 45c12527991
Ref: glossary term-generator-expression12528389
Ref: 430e12528389
Ref: glossary term-generic-function12528770
Ref: 1cb12528770
Ref: glossary term-gil12529129
Ref: bef12529129
Ref: glossary term-global-interpreter-lock12529180
Ref: 50b12529180
Ref: glossary term-hash-based-pyc12530353
Ref: 430f12530353
Ref: glossary term-hashable12530567
Ref: 142e12530567
Ref: glossary term-idle12531482
Ref: 431012531482
Ref: glossary term-immutable12531660
Ref: 122712531660
Ref: glossary term-import-path12532004
Ref: 14c212532004
Ref: glossary term-importing12532343
Ref: 14b312532343
Ref: glossary term-importer12532464
Ref: 14c112532464
Ref: glossary term-interactive12532590
Ref: 431112532590
Ref: glossary term-interpreted12533012
Ref: 431212533012
Ref: glossary term-interpreter-shutdown12533505
Ref: 76812533505
Ref: glossary term-iterable12534239
Ref: bb112534239
Ref: glossary term-iterator12535436
Ref: 104012535436
Ref: glossary term-key-function12536658
Ref: 6e512536658
Ref: glossary term-keyword-argument12537829
Ref: 5c912537829
Ref: glossary term-lambda12537879
Ref: 36ce12537879
Ref: glossary term-lbyl12538112
Ref: 430c12538112
Ref: glossary term-list12538771
Ref: 431312538771
Ref: glossary term-list-comprehension12538954
Ref: 431412538954
Ref: glossary term-loader12539372
Ref: 14c012539372
Ref: glossary term-magic-method12539646
Ref: 431512539646
Ref: glossary term-mapping12539718
Ref: b3e12539718
Ref: glossary term-meta-path-finder12540085
Ref: 9b612540085
Ref: glossary term-metaclass12540382
Ref: 232f12540382
Ref: glossary term-method12541122
Ref: 430312541122
Ref: glossary term-method-resolution-order12541432
Ref: 160912541432
Ref: glossary term-module12541709
Ref: 14b212541709
Ref: glossary term-module-spec12541971
Ref: 363812541971
Ref: glossary term-mro12542137
Ref: 288312542137
Ref: glossary term-mutable12542189
Ref: 122f12542189
Ref: glossary term-named-tuple12542313
Ref: aa812542313
Ref: glossary term-namespace12543474
Ref: 431612543474
Ref: glossary term-namespace-package12544229
Ref: 14b812544229
Ref: glossary term-nested-scope12544551
Ref: 15f012544551
Ref: glossary term-new-style-class12545039
Ref: 1cb212545039
Ref: glossary term-object12545365
Ref: 431712545365
Ref: glossary term-package12545529
Ref: ebb12545529
Ref: glossary term-parameter12545802
Ref: 153012545802
Ref: glossary positional-only-parameter12546345
Ref: 2a812546345
Ref: glossary keyword-only-parameter12546745
Ref: 2ad12546745
Ref: glossary term-path-entry12548257
Ref: 14d412548257
Ref: glossary term-path-entry-finder12548411
Ref: 9b712548411
Ref: glossary term-path-entry-hook12548734
Ref: 14d612548734
Ref: glossary term-path-based-finder12548926
Ref: 14c512548926
Ref: glossary term-path-like-object12549061
Ref: 36f12549061
Ref: glossary term-pep12549694
Ref: 431812549694
Ref: glossary term-portion12550348
Ref: 14ba12550348
Ref: glossary term-positional-argument12550509
Ref: 5ca12550509
Ref: glossary term-provisional-api12550562
Ref: 34d12550562
Ref: glossary term-provisional-package12551562
Ref: 98512551562
Ref: glossary term-python-300012551621
Ref: 431912551621
Ref: glossary term-pythonic12551810
Ref: 431a12551810
Ref: glossary term-qualified-name12552450
Ref: 143012552450
Ref: glossary term-reference-count12553291
Ref: 3b2e12553291
Ref: glossary term-regular-package12553733
Ref: 14b712553733
Ref: glossary term-slots12553899
Ref: 379712553899
Ref: glossary term-sequence12554245
Ref: 122d12554245
Ref: glossary term-set-comprehension12555253
Ref: 431b12555253
Ref: glossary term-single-dispatch12555570
Ref: 1cc12555570
Ref: glossary term-slice12555721
Ref: 160512555721
Ref: glossary term-special-method12556046
Ref: 366312556046
Ref: glossary term-statement12556326
Ref: 1b9712556326
Ref: glossary term-text-encoding12556566
Ref: 160012556566
Ref: glossary term-text-file12556635
Ref: 12aa12556635
Ref: glossary term-triple-quoted-string12557157
Ref: 431c12557157
Ref: glossary term-type12557655
Ref: 431d12557655
Ref: glossary term-type-alias12557888
Ref: 431e12557888
Ref: glossary term-type-hint12558553
Ref: 430212558553
Ref: glossary term-universal-newlines12559139
Ref: 5f912559139
Ref: glossary term-variable-annotation12559513
Ref: 62412559513
Ref: glossary term-virtual-environment12560139
Ref: 131712560139
Ref: glossary term-virtual-machine12560448
Ref: 278912560448
Ref: glossary term-zen-of-python12560614
Ref: 431f12560614
Ref: Glossary-Footnote-112560876
Ref: Glossary-Footnote-212560925
Ref: Glossary-Footnote-312560974
Ref: Glossary-Footnote-412561023
Ref: Glossary-Footnote-512561072
Ref: Glossary-Footnote-612561121
Ref: Glossary-Footnote-712561170
Ref: Glossary-Footnote-812561219
Ref: Glossary-Footnote-912561268
Ref: Glossary-Footnote-1012561317
Ref: Glossary-Footnote-1112561356
Ref: Glossary-Footnote-1212561406
Ref: Glossary-Footnote-1312561456
Ref: Glossary-Footnote-1412561506
Ref: Glossary-Footnote-1512561538
Ref: Glossary-Footnote-1612561588
Ref: Glossary-Footnote-1712561638
Ref: Glossary-Footnote-1812561688
Ref: Glossary-Footnote-1912561738
Ref: Glossary-Footnote-2012561788
Ref: Glossary-Footnote-2112561838
Ref: Glossary-Footnote-2212561888
Ref: Glossary-Footnote-2312561938
Ref: Glossary-Footnote-2412561997
Ref: Glossary-Footnote-2512562047
Ref: Glossary-Footnote-2612562097
Ref: Glossary-Footnote-2712562147
Ref: Glossary-Footnote-2812562197
Ref: Glossary-Footnote-2912562247
Ref: Glossary-Footnote-3012562297
Ref: Glossary-Footnote-3112562347
Ref: Glossary-Footnote-3212562397
Ref: Glossary-Footnote-3312562447
Ref: Glossary-Footnote-3412562497
Ref: Glossary-Footnote-3512562547
Ref: Glossary-Footnote-3612562597
Node: 關於這些說明文件12562647
Ref: about doc12562747
Ref: 432012562747
Ref: about about-these-documents12562747
Ref: 432112562747
Ref: 關於這些說明文件-Footnote-112563594
Ref: 關於這些說明文件-Footnote-212563625
Ref: 關於這些說明文件-Footnote-312563674
Ref: 關於這些說明文件-Footnote-412563715
Node: Python 文件的貢獻者們12563756
Ref: about contributors-to-the-python-documentation12563845
Ref: 432212563845
Ref: Python 文件的貢獻者們-Footnote-112564249
Node: 處理 Bug12564310
Ref: bugs doc12564414
Ref: 432312564414
Ref: bugs dealing-with-bugs12564414
Ref: 432412564414
Ref: bugs reporting-bugs12564414
Ref: 3b9012564414
Node: 說明文件錯誤12564875
Ref: bugs documentation-bugs12564975
Ref: 432612564975
Ref: 說明文件錯誤-Footnote-112565915
Ref: 說明文件錯誤-Footnote-212566060
Ref: 說明文件錯誤-Footnote-312566105
Node: 使用 Python 議題追蹤12566181
Ref: bugs using-the-python-issue-tracker12566318
Ref: 432812566318
Ref: bugs using-the-tracker12566318
Ref: 432712566318
Ref: 使用 Python 議題追蹤-Footnote-112568681
Ref: 使用 Python 議題追蹤-Footnote-212568744
Node: 開始讓自己貢獻 Python12568828
Ref: bugs contributing-to-python12568938
Ref: 432512568938
Ref: bugs getting-started-contributing-to-python-yourself12568938
Ref: 432912568938
Ref: 開始讓自己貢獻 Python-Footnote-112569412
Ref: 開始讓自己貢獻 Python-Footnote-212569449
Node: 版權宣告12569525
Ref: copyright doc12569620
Ref: 432a12569620
Ref: copyright copyright12569620
Ref: 432b12569620
Ref: copyright core-mentorship-mailing-list12569620
Ref: 432c12569620
Node: 歷史與授權12570112
Ref: license doc12570229
Ref: 432e12570229
Ref: license history-and-license12570229
Ref: 432d12570229
Ref: license id112570229
Ref: 432f12570229
Node: History of the software12570426
Ref: license history-of-the-software12570570
Ref: 433012570570
Node: Terms and conditions for accessing or otherwise using Python12575109
Ref: license terms-and-conditions-for-accessing-or-otherwise-using-python12575317
Ref: 433112575317
Node: PSF LICENSE AGREEMENT FOR PYTHON 3 8 1112576486
Ref: license psf-license12576674
Ref: 433212576674
Ref: license psf-license-agreement-for-python-release12576674
Ref: 433512576674
Node: BEOPEN COM LICENSE AGREEMENT FOR PYTHON 2 012579355
Ref: license beopen-com-license-agreement-for-python-2-012579591
Ref: 433612579591
Node: CNRI LICENSE AGREEMENT FOR PYTHON 1 6 112582299
Ref: license cnri-license-agreement-for-python-1-6-112582546
Ref: 433712582546
Node: CWI LICENSE AGREEMENT FOR PYTHON 0 9 0 THROUGH 1 212586724
Ref: license cwi-license-agreement-for-python-0-9-0-through-1-212586995
Ref: 433812586995
Node: ZERO-CLAUSE BSD LICENSE FOR CODE IN THE PYTHON 3 8 11 DOCUMENTATION12588265
Ref: license bsd012588488
Ref: 433312588488
Ref: license zero-clause-bsd-license-for-code-in-the-python-release-documentation12588488
Ref: 433912588488
Node: Licenses and Acknowledgements for Incorporated Software12589292
Ref: license licenses-and-acknowledgements-for-incorporated-software12589468
Ref: 433a12589468
Ref: license otherlicenses12589468
Ref: 433412589468
Node: Mersenne Twister12590103
Ref: license mersenne-twister12590230
Ref: 433b12590230
Node: Sockets<2>12592504
Ref: license sockets12592668
Ref: 433c12592668
Node: Asynchronous socket services12594502
Ref: license asynchronous-socket-services12594667
Ref: 433d12594667
Node: Cookie management12595887
Ref: license cookie-management12596059
Ref: 433e12596059
Node: Execution tracing12597276
Ref: license execution-tracing12597451
Ref: 433f12597451
Node: UUencode and UUdecode functions12598711
Ref: license uuencode-and-uudecode-functions12598895
Ref: 434012598895
Node: XML Remote Procedure Calls12600477
Ref: license xml-remote-procedure-calls12600654
Ref: 434112600654
Node: test_epoll12602179
Ref: license test-epoll12602338
Ref: 434212602338
Node: Select kqueue12603598
Ref: license select-kqueue12603740
Ref: 434312603740
Node: SipHash2412605294
Ref: license siphash2412605441
Ref: 434412605441
Node: strtod and dtoa12606624
Ref: license strtod-and-dtoa12606765
Ref: 434512606765
Node: OpenSSL12608114
Ref: license openssl12608251
Ref: 434612608251
Node: expat12615798
Ref: license expat12615926
Ref: 434712615926
Node: libffi12617326
Ref: license libffi12617454
Ref: 434812617454
Node: zlib<3>12618797
Ref: license zlib12618927
Ref: 434912618927
Node: cfuhash12620160
Ref: license cfuhash12620292
Ref: 434a12620292
Node: libmpdec12622109
Ref: license libmpdec12622253
Ref: 434b12622253
Node: W3C C14N test suite12623817
Ref: license w3c-c14n-test-suite12623945
Ref: 434c12623945
Node: 發布 Python 模組（舊版）12625889
Ref: distutils/index doc12626026
Ref: 434d12626026
Ref: distutils/index distributing-python-modules-legacy-version12626026
Ref: 434e12626026
Ref: distutils/index distutils-index12626026
Ref: 7fd12626026
Ref: 發布 Python 模組（舊版）-Footnote-112627461
Node: An Introduction to Distutils12627527
Ref: distutils/introduction doc12627657
Ref: 434f12627657
Ref: distutils/introduction an-introduction-to-distutils12627657
Ref: 435012627657
Ref: distutils/introduction distutils-intro12627657
Ref: 435112627657
Node: Concepts & Terminology12628404
Ref: distutils/introduction concepts-terminology12628519
Ref: 435212628519
Ref: distutils/introduction distutils-concepts12628519
Ref: 435312628519
Node: A Simple Example<2>12629723
Ref: distutils/introduction a-simple-example12629873
Ref: 435412629873
Ref: distutils/introduction distutils-simple-example12629873
Ref: 435512629873
Node: General Python terminology12633724
Ref: distutils/introduction general-python-terminology12633882
Ref: 435712633882
Ref: distutils/introduction python-terms12633882
Ref: 435812633882
Node: Distutils-specific terminology12635873
Ref: distutils/introduction distutils-specific-terminology12636003
Ref: 435912636003
Ref: distutils/introduction distutils-term12636003
Ref: 435a12636003
Node: Writing the Setup Script12637152
Ref: distutils/setupscript doc12637327
Ref: 435b12637327
Ref: distutils/setupscript setup-script12637327
Ref: 435612637327
Ref: distutils/setupscript writing-the-setup-script12637327
Ref: 435c12637327
Node: Listing whole packages12640724
Ref: distutils/setupscript listing-packages12640842
Ref: 435e12640842
Ref: distutils/setupscript listing-whole-packages12640842
Ref: 435f12640842
Node: Listing individual modules12643298
Ref: distutils/setupscript listing-individual-modules12643453
Ref: 436012643453
Ref: distutils/setupscript listing-modules12643453
Ref: 436112643453
Node: Describing extension modules12644254
Ref: distutils/setupscript describing-extension-modules12644435
Ref: 436212644435
Ref: distutils/setupscript describing-extensions12644435
Ref: 436312644435
Node: Extension names and packages12646174
Ref: distutils/setupscript extension-names-and-packages12646298
Ref: 436512646298
Node: Extension source files12647397
Ref: distutils/setupscript extension-source-files12647550
Ref: 436612647550
Node: Preprocessor options12648946
Ref: distutils/setupscript preprocessor-options12649086
Ref: 436712649086
Node: Library options12652104
Ref: distutils/setupscript library-options12652235
Ref: 436812652235
Node: Other options12653213
Ref: distutils/setupscript other-options12653315
Ref: 436912653315
Node: Relationships between Distributions and Packages12654470
Ref: distutils/setupscript relationships-between-distributions-and-packages12654643
Ref: 436a12654643
Node: Installing Scripts12658021
Ref: distutils/setupscript distutils-installing-scripts12658189
Ref: 436b12658189
Ref: distutils/setupscript installing-scripts12658189
Ref: 436c12658189
Node: Installing Package Data12659283
Ref: distutils/setupscript distutils-installing-package-data12659430
Ref: 436d12659430
Ref: distutils/setupscript installing-package-data12659430
Ref: 436e12659430
Node: Installing Additional Files12661128
Ref: distutils/setupscript distutils-additional-files12661277
Ref: 436f12661277
Ref: distutils/setupscript installing-additional-files12661277
Ref: 437012661277
Node: Additional meta-data12663157
Ref: distutils/setupscript additional-meta-data12663309
Ref: 437112663309
Ref: distutils/setupscript meta-data12663309
Ref: 435d12663309
Ref: Additional meta-data-Footnote-112670615
Node: Debugging the setup script12670652
Ref: distutils/setupscript debug-setup-script12670768
Ref: 437212670768
Ref: distutils/setupscript debugging-the-setup-script12670768
Ref: 437312670768
Node: Writing the Setup Configuration File12671843
Ref: distutils/configfile doc12672020
Ref: 437412672020
Ref: distutils/configfile setup-config12672020
Ref: 437512672020
Ref: distutils/configfile writing-the-setup-configuration-file12672020
Ref: 437612672020
Ref: distutils/configfile distutils-build-ext-inplace12675231
Ref: 437712675231
Ref: Writing the Setup Configuration File-Footnote-112677686
Node: Creating a Source Distribution12677800
Ref: distutils/sourcedist doc12677981
Ref: 437912677981
Ref: distutils/sourcedist creating-a-source-distribution12677981
Ref: 437a12677981
Ref: distutils/sourcedist source-dist12677981
Ref: 437b12677981
Node: Specifying the files to distribute12680820
Ref: distutils/sourcedist manifest12680954
Ref: 3b7412680954
Ref: distutils/sourcedist specifying-the-files-to-distribute12680954
Ref: 437c12680954
Node: Manifest-related options12686889
Ref: distutils/sourcedist manifest-options12687023
Ref: 437e12687023
Ref: distutils/sourcedist manifest-related-options12687023
Ref: 437f12687023
Node: Creating Built Distributions12688118
Ref: distutils/builtdist doc12688281
Ref: 438012688281
Ref: distutils/builtdist built-dist12688281
Ref: 438112688281
Ref: distutils/builtdist creating-built-distributions12688281
Ref: 438212688281
Node: Creating RPM packages12695842
Ref: distutils/builtdist creating-rpm-packages12695964
Ref: 438312695964
Ref: distutils/builtdist creating-rpms12695964
Ref: 438412695964
Node: Creating Windows Installers12703538
Ref: distutils/builtdist creating-windows-installers12703695
Ref: 438512703695
Ref: distutils/builtdist creating-wininst12703695
Ref: 438612703695
Node: Cross-compiling on Windows12705918
Ref: distutils/builtdist cross-compile-windows12706083
Ref: 438712706083
Ref: distutils/builtdist cross-compiling-on-windows12706083
Ref: 438812706083
Node: The Postinstallation script12707765
Ref: distutils/builtdist postinstallation-script12707855
Ref: 438912707855
Ref: distutils/builtdist the-postinstallation-script12707855
Ref: 438a12707855
Ref: distutils/builtdist directory_created12708760
Ref: 438b12708760
Ref: distutils/builtdist file_created12708797
Ref: 438c12708797
Ref: distutils/builtdist get_special_folder_path12709146
Ref: 438d12709146
Ref: distutils/builtdist create_shortcut12710034
Ref: 438e12710034
Node: Vista User Access Control UAC12710749
Ref: distutils/builtdist vista-user-access-control-uac12710878
Ref: 438f12710878
Node: Distutils Examples12711333
Ref: distutils/examples doc12711485
Ref: 439012711485
Ref: distutils/examples distutils-examples12711485
Ref: 439112711485
Ref: distutils/examples id112711485
Ref: 439212711485
Ref: Distutils Examples-Footnote-112712369
Node: Pure Python distribution by module12712425
Ref: distutils/examples pure-mod12712558
Ref: 439312712558
Ref: distutils/examples pure-python-distribution-by-module12712558
Ref: 439412712558
Node: Pure Python distribution by package12714342
Ref: distutils/examples pure-pkg12714507
Ref: 439512714507
Ref: distutils/examples pure-python-distribution-by-package12714507
Ref: 439612714507
Node: Single extension module12718276
Ref: distutils/examples single-ext12718425
Ref: 439712718425
Ref: distutils/examples single-extension-module12718425
Ref: 439812718425
Node: Checking a package12719540
Ref: distutils/examples checking-a-package12719674
Ref: 439912719674
Ref: Checking a package-Footnote-112721321
Node: Reading the metadata12721361
Ref: distutils/examples reading-the-metadata12721463
Ref: 439a12721463
Node: Extending Distutils12723102
Ref: distutils/extending doc12723238
Ref: 439b12723238
Ref: distutils/extending docutils12723238
Ref: 439c12723238
Ref: distutils/extending extending-distutils12723238
Ref: 139e12723238
Ref: distutils/extending id112723238
Ref: 439d12723238
Node: Integrating new commands12724523
Ref: distutils/extending integrating-new-commands12724641
Ref: 439f12724641
Node: Adding new distribution types12727541
Ref: distutils/extending adding-new-distribution-types12727659
Ref: 43a012727659
Node: 指令參照12728113
Ref: distutils/commandref doc12728240
Ref: 43a112728240
Ref: distutils/commandref command-reference12728240
Ref: 43a212728240
Ref: distutils/commandref reference12728240
Ref: 43a312728240
Node: Installing modules the install command family12728744
Ref: distutils/commandref install-cmd12728895
Ref: 43a412728895
Ref: distutils/commandref installing-modules-the-install-command-family12728895
Ref: 43a512728895
Node: install_data12729221
Ref: distutils/commandref install-data12729339
Ref: 43a612729339
Ref: distutils/commandref install-data-cmd12729339
Ref: 43a712729339
Node: install_scripts12729462
Ref: distutils/commandref install-scripts12729580
Ref: 43a812729580
Ref: distutils/commandref install-scripts-cmd12729580
Ref: 43a912729580
Node: Creating a source distribution the sdist command12729704
Ref: distutils/commandref creating-a-source-distribution-the-sdist-command12729855
Ref: 43aa12729855
Ref: distutils/commandref sdist-cmd12729855
Ref: 437d12729855
Node: API參照12732614
Ref: distutils/apiref doc12732713
Ref: 43ab12732713
Ref: distutils/apiref api-reference12732713
Ref: 43ac12732713
Ref: distutils/apiref id112732713
Ref: 43ad12732713
Ref: API參照-Footnote-112738470
Node: distutils core --- Core Distutils functionality12738570
Ref: distutils/apiref distutils-core-core-distutils-functionality12738716
Ref: 43ae12738716
Ref: distutils/apiref module-distutils core12738716
Ref: 5412738716
Ref: distutils/apiref distutils core setup12739123
Ref: 3b7112739123
Ref: distutils/apiref distutils core run_setup12746032
Ref: 43b112746032
Ref: distutils/apiref distutils core Extension12748450
Ref: 436412748450
Ref: distutils/apiref distutils core Distribution12755866
Ref: 43af12755866
Ref: distutils/apiref distutils core Command12756375
Ref: 43b012756375
Ref: distutils core --- Core Distutils functionality-Footnote-112756575
Ref: distutils core --- Core Distutils functionality-Footnote-212756612
Node: distutils ccompiler --- CCompiler base class12756661
Ref: distutils/apiref distutils-ccompiler-ccompiler-base-class12756859
Ref: 43b212756859
Ref: distutils/apiref module-distutils ccompiler12756859
Ref: 3c12756859
Ref: distutils/apiref distutils ccompiler gen_lib_options12757352
Ref: 43b412757352
Ref: distutils/apiref distutils ccompiler gen_preprocess_options12757836
Ref: 43b512757836
Ref: distutils/apiref distutils ccompiler get_default_compiler12758500
Ref: 43b612758500
Ref: distutils/apiref distutils ccompiler new_compiler12758957
Ref: 43b712758957
Ref: distutils/apiref distutils ccompiler show_compilers12759751
Ref: 43b812759751
Ref: distutils/apiref distutils ccompiler CCompiler12759942
Ref: 43b312759942
Ref: distutils/apiref distutils ccompiler CCompiler add_include_dir12761380
Ref: 43b912761380
Ref: distutils/apiref distutils ccompiler CCompiler set_include_dirs12761688
Ref: 43ba12761688
Ref: distutils/apiref distutils ccompiler CCompiler add_library12762167
Ref: 43bb12762167
Ref: distutils/apiref distutils ccompiler CCompiler set_libraries12762960
Ref: 43bc12762960
Ref: distutils/apiref distutils ccompiler CCompiler add_library_dir12763261
Ref: 43bd12763261
Ref: distutils/apiref distutils ccompiler CCompiler set_library_dirs12763673
Ref: 43be12763673
Ref: distutils/apiref distutils ccompiler CCompiler add_runtime_library_dir12763920
Ref: 43bf12763920
Ref: distutils/apiref distutils ccompiler CCompiler set_runtime_library_dirs12764087
Ref: 43c012764087
Ref: distutils/apiref distutils ccompiler CCompiler define_macro12764379
Ref: 43c112764379
Ref: distutils/apiref distutils ccompiler CCompiler undefine_macro12764753
Ref: 43c212764753
Ref: distutils/apiref distutils ccompiler CCompiler add_link_object12765282
Ref: 43c312765282
Ref: distutils/apiref distutils ccompiler CCompiler set_link_objects12765567
Ref: 43c412765567
Ref: distutils/apiref distutils ccompiler CCompiler detect_language12766016
Ref: 43c512766016
Ref: distutils/apiref distutils ccompiler CCompiler find_library_file12766266
Ref: 43c612766266
Ref: distutils/apiref distutils ccompiler CCompiler has_function12766681
Ref: 43c712766681
Ref: distutils/apiref distutils ccompiler CCompiler library_dir_option12767089
Ref: 43c812767089
Ref: distutils/apiref distutils ccompiler CCompiler library_option12767250
Ref: 43c912767250
Ref: distutils/apiref distutils ccompiler CCompiler runtime_library_dir_option12767427
Ref: 43ca12767427
Ref: distutils/apiref distutils ccompiler CCompiler set_executables12767604
Ref: 43cb12767604
Ref: distutils/apiref distutils ccompiler CCompiler compile12769107
Ref: 43cd12769107
Ref: distutils/apiref distutils ccompiler CCompiler create_static_lib12771895
Ref: 43ce12771895
Ref: distutils/apiref distutils ccompiler CCompiler link12773181
Ref: 43cf12773181
Ref: distutils/apiref distutils ccompiler CCompiler link_executable12775843
Ref: 43d012775843
Ref: distutils/apiref distutils ccompiler CCompiler link_shared_lib12776339
Ref: 43d112776339
Ref: distutils/apiref distutils ccompiler CCompiler link_shared_object12776887
Ref: 43d212776887
Ref: distutils/apiref distutils ccompiler CCompiler preprocess12777459
Ref: 43d312777459
Ref: distutils/apiref distutils ccompiler CCompiler executable_filename12778352
Ref: 43d412778352
Ref: distutils/apiref distutils ccompiler CCompiler library_filename12778662
Ref: 43d512778662
Ref: distutils/apiref distutils ccompiler CCompiler object_filenames12779073
Ref: 43d612779073
Ref: distutils/apiref distutils ccompiler CCompiler shared_object_filename12779315
Ref: 43d712779315
Ref: distutils/apiref distutils ccompiler CCompiler execute12779516
Ref: 43d812779516
Ref: distutils/apiref distutils ccompiler CCompiler spawn12779806
Ref: 43da12779806
Ref: distutils/apiref distutils ccompiler CCompiler mkpath12779961
Ref: 43db12779961
Ref: distutils/apiref distutils ccompiler CCompiler move_file12780145
Ref: 43dd12780145
Ref: distutils/apiref distutils ccompiler CCompiler announce12780289
Ref: 43df12780289
Ref: distutils/apiref distutils ccompiler CCompiler warn12780401
Ref: 43e012780401
Ref: distutils/apiref distutils ccompiler CCompiler debug_print12780496
Ref: 43e112780496
Node: distutils unixccompiler --- Unix C Compiler12780691
Ref: distutils/apiref distutils-unixccompiler-unix-c-compiler12780887
Ref: 43e212780887
Ref: distutils/apiref module-distutils unixccompiler12780887
Ref: 6412780887
Node: distutils msvccompiler --- Microsoft Compiler12781654
Ref: distutils/apiref distutils-msvccompiler-microsoft-compiler12781849
Ref: 43e312781849
Ref: distutils/apiref module-distutils msvccompiler12781849
Ref: 6012781849
Node: distutils bcppcompiler --- Borland Compiler12782837
Ref: distutils/apiref distutils-bcppcompiler-borland-compiler12783033
Ref: 43e412783033
Ref: distutils/apiref module-distutils bcppcompiler12783033
Ref: 3b12783033
Node: distutils cygwincompiler --- Cygwin Compiler12783267
Ref: distutils/apiref distutils-cygwincompiler-cygwin-compiler12783464
Ref: 43e512783464
Ref: distutils/apiref module-distutils cygwinccompiler12783464
Ref: 5512783464
Node: distutils archive_util --- Archiving utilities12783846
Ref: distutils/apiref distutils-archive-util-archiving-utilities12784042
Ref: 43e612784042
Ref: distutils/apiref module-distutils archive_util12784042
Ref: 3a12784042
Ref: distutils/apiref distutils archive_util make_archive12784253
Ref: 43e712784253
Ref: distutils/apiref distutils archive_util make_tarball12785154
Ref: 43e812785154
Ref: distutils/apiref distutils archive_util make_zipfile12785931
Ref: 43e912785931
Node: distutils dep_util --- Dependency checking12786443
Ref: distutils/apiref distutils-dep-util-dependency-checking12786643
Ref: 43ea12786643
Ref: distutils/apiref module-distutils dep_util12786643
Ref: 5712786643
Ref: distutils/apiref distutils dep_util newer12786932
Ref: 43eb12786932
Ref: distutils/apiref distutils dep_util newer_pairwise12787270
Ref: 43ec12787270
Ref: distutils/apiref distutils dep_util newer_group12787590
Ref: 43ed12787590
Node: distutils dir_util --- Directory tree operations12788485
Ref: distutils/apiref distutils-dir-util-directory-tree-operations12788685
Ref: 43ee12788685
Ref: distutils/apiref module-distutils dir_util12788685
Ref: 5812788685
Ref: distutils/apiref distutils dir_util mkpath12788891
Ref: 43dc12788891
Ref: distutils/apiref distutils dir_util create_tree12789498
Ref: 43ef12789498
Ref: distutils/apiref distutils dir_util copy_tree12790057
Ref: 43f012790057
Ref: distutils/apiref distutils dir_util remove_tree12791525
Ref: 43f212791525
Ref: distutils dir_util --- Directory tree operations-Footnote-112791837
Node: distutils file_util --- Single file operations12791883
Ref: distutils/apiref distutils-file-util-single-file-operations12792097
Ref: 43f312792097
Ref: distutils/apiref module-distutils file_util12792097
Ref: 5d12792097
Ref: distutils/apiref distutils file_util copy_file12792294
Ref: 43f112792294
Ref: distutils/apiref distutils file_util move_file12793712
Ref: 43de12793712
Ref: distutils/apiref distutils file_util write_file12794110
Ref: 43f412794110
Node: distutils util --- Miscellaneous other utility functions12794295
Ref: distutils/apiref distutils-util-miscellaneous-other-utility-functions12794502
Ref: 43f512794502
Ref: distutils/apiref module-distutils util12794502
Ref: 6512794502
Ref: distutils/apiref distutils util get_platform12794740
Ref: 43f612794740
Ref: distutils/apiref distutils util convert_path12796446
Ref: 43f712796446
Ref: distutils/apiref distutils util change_root12796989
Ref: 43f812796989
Ref: distutils/apiref distutils util check_environ12797312
Ref: 43f912797312
Ref: distutils/apiref distutils util subst_vars12797729
Ref: 43fa12797729
Ref: distutils/apiref distutils util split_quoted12798543
Ref: 43cc12798543
Ref: distutils/apiref distutils util execute12799116
Ref: 43d912799116
Ref: distutils/apiref distutils util strtobool12799630
Ref: 43fb12799630
Ref: distutils/apiref distutils util byte_compile12799981
Ref: 43fc12799981
Ref: distutils/apiref distutils util rfc822_escape12801984
Ref: 43fd12801984
Ref: distutils util --- Miscellaneous other utility functions-Footnote-112802275
Ref: distutils util --- Miscellaneous other utility functions-Footnote-212802324
Ref: distutils util --- Miscellaneous other utility functions-Footnote-312802373
Ref: distutils util --- Miscellaneous other utility functions-Footnote-412802422
Node: distutils dist --- The Distribution class12802470
Ref: distutils/apiref distutils-dist-the-distribution-class12802674
Ref: 43fe12802674
Ref: distutils/apiref module-distutils dist12802674
Ref: 5912802674
Node: distutils extension --- The Extension class12802916
Ref: distutils/apiref distutils-extension-the-extension-class12803104
Ref: 43ff12803104
Ref: distutils/apiref module-distutils extension12803104
Ref: 5b12803104
Node: distutils debug --- Distutils debug mode12803323
Ref: distutils/apiref distutils-debug-distutils-debug-mode12803511
Ref: 440012803511
Ref: distutils/apiref module-distutils debug12803511
Ref: 5612803511
Node: distutils errors --- Distutils exceptions12803654
Ref: distutils/apiref distutils-errors-distutils-exceptions12803867
Ref: 440112803867
Ref: distutils/apiref module-distutils errors12803867
Ref: 5a12803867
Node: distutils fancy_getopt --- Wrapper around the standard getopt module12804367
Ref: distutils/apiref distutils-fancy-getopt-wrapper-around-the-standard-getopt-module12804581
Ref: 440212804581
Ref: distutils/apiref module-distutils fancy_getopt12804581
Ref: 5c12804581
Ref: distutils/apiref distutils fancy_getopt fancy_getopt12805279
Ref: 440312805279
Ref: distutils/apiref distutils fancy_getopt wrap_text12805935
Ref: 440512805935
Ref: distutils/apiref distutils fancy_getopt FancyGetopt12806041
Ref: 440412806041
Ref: distutils/apiref distutils fancy_getopt FancyGetopt getopt12806607
Ref: 440612806607
Ref: distutils/apiref distutils fancy_getopt FancyGetopt get_option_order12807215
Ref: 440712807215
Ref: distutils/apiref distutils fancy_getopt FancyGetopt generate_help12807465
Ref: 440812807465
Node: distutils filelist --- The FileList class12807751
Ref: distutils/apiref distutils-filelist-the-filelist-class12807970
Ref: 440912807970
Ref: distutils/apiref module-distutils filelist12807970
Ref: 5e12807970
Node: distutils log --- Simple PEP 282-style logging12808191
Ref: distutils/apiref distutils-log-simple-pep-282-style-logging12808381
Ref: 440a12808381
Ref: distutils/apiref module-distutils log12808381
Ref: 5f12808381
Node: distutils spawn --- Spawn a sub-process12808502
Ref: distutils/apiref distutils-spawn-spawn-a-sub-process12808707
Ref: 440b12808707
Ref: distutils/apiref module-distutils spawn12808707
Ref: 6112808707
Node: distutils sysconfig --- System configuration information12809046
Ref: distutils/apiref distutils-sysconfig-system-configuration-information12809247
Ref: 440c12809247
Ref: distutils/apiref module-distutils sysconfig12809247
Ref: 6212809247
Ref: distutils/apiref distutils sysconfig PREFIX12810090
Ref: 440d12810090
Ref: distutils/apiref distutils sysconfig EXEC_PREFIX12810184
Ref: 440e12810184
Ref: distutils/apiref distutils sysconfig get_config_var12810288
Ref: 440f12810288
Ref: distutils/apiref distutils sysconfig get_config_vars12810451
Ref: 441012810451
Ref: distutils/apiref distutils sysconfig get_config_h_filename12810903
Ref: 441112810903
Ref: distutils/apiref distutils sysconfig get_makefile_filename12811261
Ref: 441212811261
Ref: distutils/apiref distutils sysconfig get_python_inc12811637
Ref: 441312811637
Ref: distutils/apiref distutils sysconfig get_python_lib12812156
Ref: 441412812156
Ref: distutils/apiref distutils sysconfig customize_compiler12812959
Ref: 441512812959
Ref: distutils/apiref distutils sysconfig set_python_build12813627
Ref: 441612813627
Node: distutils text_file --- The TextFile class12813948
Ref: distutils/apiref distutils-text-file-the-textfile-class12814154
Ref: 441712814154
Ref: distutils/apiref module-distutils text_file12814154
Ref: 6312814154
Ref: distutils/apiref distutils text_file TextFile12814467
Ref: 441812814467
Ref: distutils/apiref distutils text_file TextFile open12818986
Ref: 441c12818986
Ref: distutils/apiref distutils text_file TextFile close12819139
Ref: 441b12819139
Ref: distutils/apiref distutils text_file TextFile warn12819309
Ref: 441912819309
Ref: distutils/apiref distutils text_file TextFile readline12819825
Ref: 441d12819825
Ref: distutils/apiref distutils text_file TextFile readlines12820509
Ref: 441e12820509
Ref: distutils/apiref distutils text_file TextFile unreadline12820722
Ref: 441a12820722
Node: distutils version --- Version number classes12821353
Ref: distutils/apiref distutils-version-version-number-classes12821563
Ref: 441f12821563
Ref: distutils/apiref module-distutils version12821563
Ref: 6612821563
Node: distutils cmd --- Abstract base class for Distutils commands12821676
Ref: distutils/apiref distutils-cmd-abstract-base-class-for-distutils-commands12821876
Ref: 442012821876
Ref: distutils/apiref module-distutils cmd12821876
Ref: 3d12821876
Ref: distutils/apiref distutils cmd Command12822088
Ref: 439e12822088
Node: Creating a new Distutils command12823163
Ref: distutils/apiref creating-a-new-distutils-command12823370
Ref: 442412823370
Ref: distutils/apiref distutils cmd Command initialize_options12824239
Ref: 442112824239
Ref: distutils/apiref distutils cmd Command finalize_options12824693
Ref: 442212824693
Ref: distutils/apiref distutils cmd Command run12825195
Ref: 442312825195
Ref: distutils/apiref distutils cmd Command sub_commands12825627
Ref: 442512825627
Node: distutils command --- Individual Distutils commands12826611
Ref: distutils/apiref distutils-command-individual-distutils-commands12826810
Ref: 442612826810
Ref: distutils/apiref module-distutils command12826810
Ref: 3e12826810
Node: distutils command bdist --- Build a binary installer12826937
Ref: distutils/apiref distutils-command-bdist-build-a-binary-installer12827174
Ref: 442712827174
Ref: distutils/apiref module-distutils command bdist12827174
Ref: 3f12827174
Node: distutils command bdist_packager --- Abstract base class for packagers12827303
Ref: distutils/apiref distutils-command-bdist-packager-abstract-base-class-for-packagers12827546
Ref: 442812827546
Ref: distutils/apiref module-distutils command bdist_packager12827546
Ref: 4212827546
Node: distutils command bdist_dumb --- Build a "dumb" installer12827711
Ref: distutils/apiref distutils-command-bdist-dumb-build-a-dumb-installer12827976
Ref: 442912827976
Ref: distutils/apiref module-distutils command bdist_dumb12827976
Ref: 4012827976
Node: distutils command bdist_msi --- Build a Microsoft Installer binary package12828115
Ref: distutils/apiref distutils-command-bdist-msi-build-a-microsoft-installer-binary-package12828394
Ref: 442a12828394
Ref: distutils/apiref module-distutils command bdist_msi12828394
Ref: 4112828394
Ref: distutils/apiref distutils command bdist_msi bdist_msi12828567
Ref: 442b12828567
Ref: distutils command bdist_msi --- Build a Microsoft Installer binary package-Footnote-112829011
Node: distutils command bdist_rpm --- Build a binary distribution as a Redhat RPM and SRPM12829081
Ref: distutils/apiref distutils-command-bdist-rpm-build-a-binary-distribution-as-a-redhat-rpm-and-srpm12829364
Ref: 442c12829364
Ref: distutils/apiref module-distutils command bdist_rpm12829364
Ref: 4312829364
Node: distutils command bdist_wininst --- Build a Windows installer12829557
Ref: distutils/apiref distutils-command-bdist-wininst-build-a-windows-installer12829821
Ref: 442d12829821
Ref: distutils/apiref module-distutils command bdist_wininst12829821
Ref: 4412829821
Node: distutils command sdist --- Build a source distribution12830032
Ref: distutils/apiref distutils-command-sdist-build-a-source-distribution12830268
Ref: 442e12830268
Ref: distutils/apiref module-distutils command sdist12830268
Ref: 5312830268
Node: distutils command build --- Build all files of a package12830403
Ref: distutils/apiref distutils-command-build-build-all-files-of-a-package12830645
Ref: 442f12830645
Ref: distutils/apiref module-distutils command build12830645
Ref: 4512830645
Node: distutils command build_clib --- Build any C libraries in a package12830782
Ref: distutils/apiref distutils-command-build-clib-build-any-c-libraries-in-a-package12831034
Ref: 443012831034
Ref: distutils/apiref module-distutils command build_clib12831034
Ref: 4612831034
Node: distutils command build_ext --- Build any extensions in a package12831193
Ref: distutils/apiref distutils-command-build-ext-build-any-extensions-in-a-package12831456
Ref: 443112831456
Ref: distutils/apiref module-distutils command build_ext12831456
Ref: 4712831456
Node: distutils command build_py --- Build the py/ pyc files of a package12831611
Ref: distutils/apiref distutils-command-build-py-build-the-py-pyc-files-of-a-package12831873
Ref: 443212831873
Ref: distutils/apiref module-distutils command build_py12831873
Ref: 4812831873
Ref: distutils/apiref distutils command build_py build_py12832034
Ref: 443312832034
Ref: distutils/apiref distutils command build_py build_py_2to312832083
Ref: 443412832083
Node: distutils command build_scripts --- Build the scripts of a package12832701
Ref: distutils/apiref distutils-command-build-scripts-build-the-scripts-of-a-package12832952
Ref: 443512832952
Ref: distutils/apiref module-distutils command build_scripts12832952
Ref: 4912832952
Node: distutils command clean --- Clean a package build area12833109
Ref: distutils/apiref distutils-command-clean-clean-a-package-build-area12833351
Ref: 443612833351
Ref: distutils/apiref module-distutils command clean12833351
Ref: 4b12833351
Node: distutils command config --- Perform package configuration12833795
Ref: distutils/apiref distutils-command-config-perform-package-configuration12834018
Ref: 443712834018
Ref: distutils/apiref module-distutils command config12834018
Ref: 4c12834018
Node: distutils command install --- Install a package12834159
Ref: distutils/apiref distutils-command-install-install-a-package12834396
Ref: 443812834396
Ref: distutils/apiref module-distutils command install12834396
Ref: 4d12834396
Node: distutils command install_data --- Install data files from a package12834515
Ref: distutils/apiref distutils-command-install-data-install-data-files-from-a-package12834773
Ref: 443912834773
Ref: distutils/apiref module-distutils command install_data12834773
Ref: 4e12834773
Node: distutils command install_headers --- Install C/C++ header files from a package12834934
Ref: distutils/apiref distutils-command-install-headers-install-c-c-header-files-from-a-package12835215
Ref: 443a12835215
Ref: distutils/apiref module-distutils command install_headers12835215
Ref: 4f12835215
Node: distutils command install_lib --- Install library files from a package12835398
Ref: distutils/apiref distutils-command-install-lib-install-library-files-from-a-package12835684
Ref: 443b12835684
Ref: distutils/apiref module-distutils command install_lib12835684
Ref: 5012835684
Node: distutils command install_scripts --- Install script files from a package12835849
Ref: distutils/apiref distutils-command-install-scripts-install-script-files-from-a-package12836134
Ref: 443c12836134
Ref: distutils/apiref module-distutils command install_scripts12836134
Ref: 5112836134
Node: distutils command register --- Register a module with the Python Package Index12836305
Ref: distutils/apiref distutils-command-register-register-a-module-with-the-python-package-index12836580
Ref: 443d12836580
Ref: distutils/apiref module-distutils command register12836580
Ref: 5212836580
Ref: distutils command register --- Register a module with the Python Package Index-Footnote-112836927
Node: distutils command check --- Check the meta-data of a package12836976
Ref: distutils/apiref distutils-command-check-check-the-meta-data-of-a-package12837169
Ref: 443e12837169
Ref: distutils/apiref module-distutils command check12837169
Ref: 4a12837169
Node: 安裝 Python 模組（舊版）12837511
Ref: install/index doc12837652
Ref: 443f12837652
Ref: install/index install-index12837652
Ref: 7fc12837652
Ref: install/index installing-python-modules-legacy-version12837652
Ref: 444012837652
Ref: 安裝 Python 模組（舊版）-Footnote-112838806
Node: 簡介<16>12838872
Ref: install/index inst-intro12838986
Ref: 444112838986
Ref: install/index introduction12838986
Ref: 444212838986
Node: Distutils based source distributions12839924
Ref: install/index distutils-based-source-distributions12840007
Ref: 444312840007
Ref: install/index inst-new-standard12840007
Ref: 444412840007
Node: Standard Build and Install12841294
Ref: install/index inst-standard-install12841439
Ref: 444512841439
Ref: install/index standard-build-and-install12841439
Ref: 444612841439
Node: Platform variations12841838
Ref: install/index inst-platform-variations12841949
Ref: 444712841949
Ref: install/index platform-variations12841949
Ref: 444812841949
Node: Splitting the job up12842864
Ref: install/index inst-splitting-up12843002
Ref: 444912843002
Ref: install/index splitting-the-job-up12843002
Ref: 444a12843002
Node: How building works12844306
Ref: install/index how-building-works12844447
Ref: 444b12844447
Ref: install/index inst-how-build-works12844447
Ref: 444c12844447
Node: How installation works12846172
Ref: install/index how-installation-works12846284
Ref: 444e12846284
Ref: install/index inst-how-install-works12846284
Ref: 444f12846284
Node: Alternate Installation12851082
Ref: install/index alternate-installation12851236
Ref: 445212851236
Ref: install/index inst-alt-install12851236
Ref: 445012851236
Node: Alternate installation the user scheme12852924
Ref: install/index alternate-installation-the-user-scheme12853068
Ref: 445312853068
Ref: install/index inst-alt-install-user12853068
Ref: 135e12853068
Node: Alternate installation the home scheme12855467
Ref: install/index alternate-installation-the-home-scheme12855665
Ref: 445412855665
Ref: install/index inst-alt-install-home12855665
Ref: 445512855665
Node: Alternate installation Unix the prefix scheme12857458
Ref: install/index alternate-installation-unix-the-prefix-scheme12857666
Ref: 445712857666
Ref: install/index inst-alt-install-prefix-unix12857666
Ref: 445812857666
Node: Alternate installation Windows the prefix scheme12861693
Ref: install/index alternate-installation-windows-the-prefix-scheme12861854
Ref: 445912861854
Ref: install/index inst-alt-install-prefix-windows12861854
Ref: 445a12861854
Node: Custom Installation12863121
Ref: install/index custom-installation12863278
Ref: 445b12863278
Ref: install/index inst-custom-install12863278
Ref: 445112863278
Node: Modifying Python's Search Path12870259
Ref: install/index inst-search-path12870345
Ref: 445612870345
Ref: install/index modifying-python-s-search-path12870345
Ref: 445c12870345
Node: Distutils Configuration Files12874067
Ref: install/index distutils-configuration-files12874237
Ref: 445d12874237
Ref: install/index inst-config-files12874237
Ref: 444d12874237
Node: Location and names of config files12874940
Ref: install/index inst-config-filenames12875071
Ref: 445e12875071
Ref: install/index location-and-names-of-config-files12875071
Ref: 445f12875071
Node: Syntax of config files12878996
Ref: install/index inst-config-syntax12879127
Ref: 437812879127
Ref: install/index syntax-of-config-files12879127
Ref: 446012879127
Node: Building Extensions Tips and Tricks12881041
Ref: install/index building-extensions-tips-and-tricks12881183
Ref: 446112881183
Ref: install/index inst-building-ext12881183
Ref: 446212881183
Node: Tweaking compiler/linker flags12881789
Ref: install/index inst-tweak-flags12881940
Ref: 446312881940
Ref: install/index tweaking-compiler-linker-flags12881940
Ref: 446412881940
Node: Using non-Microsoft compilers on Windows12885009
Ref: install/index inst-non-ms-compilers12885160
Ref: 446512885160
Ref: install/index using-non-microsoft-compilers-on-windows12885160
Ref: 446612885160
Node: Borland/CodeGear C++12885319
Ref: install/index borland-codegear-c12885447
Ref: 446712885447
Ref: Borland/CodeGear C++-Footnote-112887403
Ref: Borland/CodeGear C++-Footnote-212887514
Ref: Borland/CodeGear C++-Footnote-312887559
Node: GNU C / Cygwin / MinGW12887613
Ref: install/index gnu-c-cygwin-mingw12887741
Ref: 446812887741
Ref: GNU C / Cygwin / MinGW-Footnote-112888749
Ref: GNU C / Cygwin / MinGW-Footnote-212888829
Node: Older Versions of Python and MinGW12888930
Ref: install/index older-versions-of-python-and-mingw12889023
Ref: 446912889023
Ref: Older Versions of Python and MinGW-Footnote-112890687
Node: Python 模組索引12890752
Node: 索引12913334
Ref: 34cb14690385
Ref: 34cc14690415
Ref: using/cmdline audit_event_cpython_run_stdin_014690446
Ref: using/cmdline audit_event_cpython_run_file_014690477

End Tag Table


Local Variables:
coding: utf-8
End:
